summaryrefslogtreecommitdiff
path: root/help
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /help
Initial commit
Diffstat (limited to 'help')
-rw-r--r--help/LaTeX-FAQ-francaise/docs-francaises332
-rw-r--r--help/LaTeX-FAQ-francaise/part11852
-rw-r--r--help/LaTeX-FAQ-francaise/part22956
-rw-r--r--help/LaTeX-FAQ-francaise/part32487
-rw-r--r--help/LaTeX-FAQ-francaise/part42906
-rw-r--r--help/LaTeX-FAQ-francaise/part52443
-rw-r--r--help/LaTeX-FAQ-francaise/part62261
-rw-r--r--help/comp-fonts-FAQ/Finding_Fonts_for_Internationalization_FAQ614
-rw-r--r--help/comp-fonts-FAQ/[comp.text.tex]_Metafont:_All_fonts_available_in_.mf_format947
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Amiga_Info334
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Atari_Info157
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Diffs_from_last_posting231
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(1_6)1183
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(2_6)1143
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(3_6)1050
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(4_6)1027
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(5_6)1421
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(6_6)442
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_MS-DOS_Info629
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Macintosh_Info756
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_NeXT_Info538
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_OS_2_Info420
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Sun_Info176
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Unix_Info84
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Utilities542
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_Vendor_List835
-rw-r--r--help/comp-fonts-FAQ/comp.fonts_FAQ:_X11_Info250
-rw-r--r--help/comp.programming.literate_FAQ2639
-rw-r--r--help/ctan/CTAN-upload-addendum.html1515
-rw-r--r--help/ctan/ctan-web.data.gzbin0 -> 827310 bytes
-rw-r--r--help/de-tex-faq/part1775
-rw-r--r--help/de-tex-faq/part10584
-rw-r--r--help/de-tex-faq/part11784
-rw-r--r--help/de-tex-faq/part2758
-rw-r--r--help/de-tex-faq/part3886
-rw-r--r--help/de-tex-faq/part41022
-rw-r--r--help/de-tex-faq/part5998
-rw-r--r--help/de-tex-faq/part61117
-rw-r--r--help/de-tex-faq/part71047
-rw-r--r--help/de-tex-faq/part81253
-rw-r--r--help/de-tex-faq/part9658
-rw-r--r--help/es-tex-faq/FAQ-CervanTeX.html178
-rw-r--r--help/es-tex-faq/FAQ-CervanTeX.latin15447
-rw-r--r--help/es-tex-faq/FAQ-CervanTeX.pdf10575
-rw-r--r--help/es-tex-faq/FAQ-CervanTeX.sgml5055
-rw-r--r--help/es-tex-faq/FAQ-CervanTeX.tex6634
l---------help/greek1
-rw-r--r--help/index.doc1505
-rw-r--r--help/tex-macro-catalogue.el349
-rw-r--r--help/texlists.txt103
-rw-r--r--help/uk-tex-faq/CHANGES-3.16b55
-rw-r--r--help/uk-tex-faq/CHANGES-3.16c52
-rw-r--r--help/uk-tex-faq/CHANGES-3.1758
-rw-r--r--help/uk-tex-faq/CHANGES-3.1846
-rw-r--r--help/uk-tex-faq/CHANGES-3.1967
-rw-r--r--help/uk-tex-faq/CHANGES-3.19a44
-rw-r--r--help/uk-tex-faq/CHANGES-3.19c44
-rw-r--r--help/uk-tex-faq/CHANGES-3.19d34
-rw-r--r--help/uk-tex-faq/CHANGES-3.2040
-rw-r--r--help/uk-tex-faq/CHANGES-3.2147
-rw-r--r--help/uk-tex-faq/CHANGES-3.2245
-rw-r--r--help/uk-tex-faq/CHANGES-3.2350
-rw-r--r--help/uk-tex-faq/CHANGES-3.2441
-rw-r--r--help/uk-tex-faq/CHANGES-3.2547
-rw-r--r--help/uk-tex-faq/CHANGES-3.2659
-rw-r--r--help/uk-tex-faq/CHANGES-3.2743
-rw-r--r--help/uk-tex-faq/CHANGES-3.2866
-rw-r--r--help/uk-tex-faq/ChangeLog17802
-rw-r--r--help/uk-tex-faq/Makefile226
-rw-r--r--help/uk-tex-faq/Makefile-CTAN103
-rw-r--r--help/uk-tex-faq/README34
-rw-r--r--help/uk-tex-faq/archive.cfg13
-rw-r--r--help/uk-tex-faq/dirctan.tex990
-rw-r--r--help/uk-tex-faq/faq-adj-types.tex3671
-rw-r--r--help/uk-tex-faq/faq-backgrnd.tex1220
-rw-r--r--help/uk-tex-faq/faq-biblio.tex1468
-rw-r--r--help/uk-tex-faq/faq-bits+pieces.tex1174
-rw-r--r--help/uk-tex-faq/faq-docs.tex1305
-rw-r--r--help/uk-tex-faq/faq-dvi.tex148
-rw-r--r--help/uk-tex-faq/faq-fmt-conv.tex465
-rw-r--r--help/uk-tex-faq/faq-fonts.tex1316
-rw-r--r--help/uk-tex-faq/faq-getit.tex361
-rw-r--r--help/uk-tex-faq/faq-graphics.tex1035
-rw-r--r--help/uk-tex-faq/faq-how-do-i.tex4134
-rw-r--r--help/uk-tex-faq/faq-hyp+pdf.tex636
-rw-r--r--help/uk-tex-faq/faq-images.tex25
-rw-r--r--help/uk-tex-faq/faq-install.tex1021
-rw-r--r--help/uk-tex-faq/faq-intro.tex203
-rw-r--r--help/uk-tex-faq/faq-jot-err.tex2467
-rw-r--r--help/uk-tex-faq/faq-lab-ref.tex182
-rw-r--r--help/uk-tex-faq/faq-litprog.tex81
-rw-r--r--help/uk-tex-faq/faq-mac-prog.tex3724
-rw-r--r--help/uk-tex-faq/faq-projects.tex644
-rw-r--r--help/uk-tex-faq/faq-support.tex188
-rw-r--r--help/uk-tex-faq/faq-symbols.tex613
-rw-r--r--help/uk-tex-faq/faq-t-g-wr.tex467
-rw-r--r--help/uk-tex-faq/faq-texsys.tex488
-rw-r--r--help/uk-tex-faq/faq-the-end.tex167
-rw-r--r--help/uk-tex-faq/faq-wdidt.tex2142
-rw-r--r--help/uk-tex-faq/faq.cls93
-rw-r--r--help/uk-tex-faq/faq.sty1281
-rw-r--r--help/uk-tex-faq/faqfont.cfg4
-rw-r--r--help/uk-tex-faq/faqfont.cfg.cmfonts6
-rw-r--r--help/uk-tex-faq/faqfont.cfg.lmfonts19
-rw-r--r--help/uk-tex-faq/faqfont.cfg.mbvj11
-rw-r--r--help/uk-tex-faq/faqfont.cfg.ugm12
-rw-r--r--help/uk-tex-faq/filectan.tex107
-rw-r--r--help/uk-tex-faq/gather-faqbody.tex57
-rw-r--r--help/uk-tex-faq/install-CTAN48
-rw-r--r--help/uk-tex-faq/letterfaq.pdfbin0 -> 2933477 bytes
-rw-r--r--help/uk-tex-faq/letterfaq.tex64
-rw-r--r--help/uk-tex-faq/locations.mk17
-rw-r--r--help/uk-tex-faq/markup-syntax237
-rw-r--r--help/uk-tex-faq/newfaq.pdfbin0 -> 3094571 bytes
-rw-r--r--help/uk-tex-faq/newfaq.tex67
l---------help/virtual-fonts.knuth1
-rw-r--r--help/virtualfonts.txt233
-rw-r--r--help/wp-conv/GPL.txt341
-rw-r--r--help/wp-conv/bin/license.txt341
-rw-r--r--help/wp-conv/html2LaTeX.txt8
-rw-r--r--help/wp-conv/html2latex.html147
-rw-r--r--help/wp-conv/index.html106
-rw-r--r--help/wp-conv/ktbugs.html88
-rw-r--r--help/wp-conv/la2mml.html35
-rw-r--r--help/wp-conv/laola.html37
-rw-r--r--help/wp-conv/latex2rtf.html114
-rw-r--r--help/wp-conv/ltx2word.html97
-rw-r--r--help/wp-conv/mathtype.html56
-rw-r--r--help/wp-conv/pc2txtbl.html231
-rw-r--r--help/wp-conv/pctotex.html511
-rw-r--r--help/wp-conv/pubcomp.html108
-rw-r--r--help/wp-conv/readme.txt12
-rw-r--r--help/wp-conv/rtf2latex.html94
-rw-r--r--help/wp-conv/rtf2latex2e.html52
-rw-r--r--help/wp-conv/sciword.html129
-rw-r--r--help/wp-conv/texperf.html93
-rw-r--r--help/wp-conv/texport.html155
-rw-r--r--help/wp-conv/textopc.html430
-rw-r--r--help/wp-conv/tx2pctbl.html76
-rw-r--r--help/wp-conv/w2latex.html56
-rw-r--r--help/wp-conv/winw2ltx.html85
-rw-r--r--help/wp-conv/word2x.html72
-rw-r--r--help/wp-conv/wp2latex.html57
143 files changed, 127038 insertions, 0 deletions
diff --git a/help/LaTeX-FAQ-francaise/docs-francaises b/help/LaTeX-FAQ-francaise/docs-francaises
new file mode 100644
index 0000000000..cbe2e5ef26
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/docs-francaises
@@ -0,0 +1,332 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!news.imp.ch!fr.clara.net!heighliner.fr.clara.net!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:19 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [DOCFR] Liste des documents disponibles sur (La)TeX
+Message-ID: <faq-fctt-/home/bayartb/docfr/Manifest20010608133119@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-/home/bayartb/docfr/Manifest20010501143417@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 317
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23522 fr.usenet.reponses:20388
+
+Archive-name: fr/faq-latex-francaise/docs-francaises
+
+***********************************************************************
+* *
+* Liste des documents actuellement disponible *
+* *
+* List of the documents available nowadays *
+* *
+***********************************************************************
+
+Comment lire ce fichier / How to read this file
+
+macros/latex/contrib/supported/the-package :
+ Le titre du document
+ the-package (V. 1.23)
+ Author One <his mail if available>
+ Author two <his mail if available>
+ Trad. par: FMF, JPD
+ Relu par: BB
+
+Signifie / means:
+- Position exacte du document:
+ Exact position of the document in the directory tree:
+ macros/latex/contrib/supported/the-package
+- Titre franais du document (pas encore renseign):
+ French title of the document (not yet provided):
+ Le titre du document
+- Les auteurs du package:
+ The authors of the package:
+ Author One <his mail if available>
+ Author two <his mail if available>
+- Traduction en franais par FMF et JPD (voir a la fin du fichier)
+ French translation by FMF and JPD (see and the end of the file)
+- Relecture par BB
+ Proof-read by BB
+
+Les documents / The documents
+
+macros/latex/contrib/supported/caption :
+ Le package caption2
+ caption2 (V. 2.0)
+ Harald Axel Sommerfeldt <axel@hp1.ang-physik.uni-kiel.de>
+ Trad. par : JPFD
+ Relu par : FMF
+
+macros/latex/contrib/supported/bizcard :
+ bizcard : Un package LaTeX2e pour les cartes de visite
+ bizcard (V. 1.1)
+ Sebastian Marius Kirsch <skirsch@t-online.de>
+ Trad. par : BB
+ Relu par : JM
+
+macros/latex/contrib/supported/multirow :
+
+ multirow (V. 1.1)
+ Jerry Leichter <leichter@smarts.com,leichter@lrw.com>
+ Piet van Oostrum <piet@cs.uu.nl>
+ Trad. par : FMF
+ Relu par : BB
+
+/macros/latex/base :
+ Licence Publique du Projet LaTeX
+ LPPL (V. 1.2)
+ Projet LaTeX3 <www.latex-project.org>
+ Trad. par : NLN
+ Relu par : Aucun
+
+macros/latex/required/tools :
+ Une nouvelle criture des environnements tabular et array de LaTeX
+ array (V. 2.3m)
+ Frank Mittelbach,
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools :
+ Le package calc
+ calc (V. 4.1b)
+ Kresten Krab Thorup <krab@daimi.aau.dk>
+ Frank Jensen <fj@hugin.dk>
+ Chris Rowley
+ Trad. par : JPFD
+ Relu par : DB
+
+/macros/latex/contrib/supported/natbib/ :
+
+ natbib (V. 7.0a)
+ Patrick W Daly <daly@linmp.mpg.de>
+ Trad. par : JPFD,NLN
+ Relu par : Aucun
+
+macros/latex/required/tools :
+ Le package dcolumn
+ dcolumn (V. 1.05)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools :
+ Le package delarray
+ delarray (V. 1.01)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : JM
+
+macros/latex/required/tools :
+ Le package enumerate
+ enumerate (V. 3.00)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools :
+ Notes de bas de page en mode multi-colonne
+ ftnright (V. 1.1d)
+ Frank Mittelbach
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools/ :
+ Le package hhline
+ hhline (V. 2.03)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : JM
+
+macros/latex/required/tools :
+ Le package indentfirst
+ indentfirst (V. 1.03)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : BB
+
+macros/latex/required/tools :
+ Afficher les variables de mise en page
+ layout (V. 1.1k)
+ Kent McPherson,
+ Johannes Braams
+ Trad. par : JPFD, BB
+ Relu par : SLC
+
+macros/latex/required/tools :
+ Le package longtable
+ longtable (V. 4.09)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : FMF
+
+macros/latex/required/tools :
+ Le package showkeys
+ showkeys (V. 3.12)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools :
+ Le package rawfonts
+ rawfonts (V. 0.01)
+ Alan Jeffrey
+ Trad. par : JPFD
+ Relu par : FMF
+
+macros/latex/required/tools :
+ Le package tabularx
+ tabularx (V. 2.07)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : FMF
+
+macros/latex/required/tools :
+ Une extension de l'environnement theorem de LaTeX
+ theorem (V. 2.2c)
+ Frank Mittelbach
+ Trad. par : JPFD
+ Relu par : DB
+
+macros/latex/required/tools/ :
+ Le package varioref
+ varioref (V. 1.2a)
+ Frank Mittelbach
+ Trad. par : JPFD
+ Relu par : JM
+
+macros/latex/required/tools :
+ Une nouvelle dfinition des environnements LaTeX verbatim et verbatim*
+ verbatim (V. 1.5k)
+ Rainer Sch\"opf <Schoepf@Uni-Mainz.DE>,
+ Bernd Raichle <raichle@azu.Informatik.Uni-Stuttgart.DE>,
+ Chris Rowley <C.A.Rowley@open.ac.uk>
+ Trad. par : JPFD
+ Relu par : JPS
+
+macros/latex/required/tools :
+ Le package xr
+ xr (V. 5.02)
+ David Carlisle <carlisle@cs.man.ac.uk>,
+ Jean-Pierre Drucbert <Jean-Pierre.Drucbert@onecert.fr>
+ Trad. par : JPFD
+ Relu par : JPS
+
+macros/latex/required/tools :
+ Le package xspace
+ xspace (V. 1.06)
+ David Carlisle <carlisle@cs.man.ac.uk>
+ Trad. par : JPFD
+ Relu par : JPS
+
+macros/latex/contrib/supported/custom-bib :
+
+ makebst (V. 4.0-beta1)
+ Patrick W. Daly <daly@linmp.mpg.de>
+ Trad. par : JPFD, NLN
+ Relu par : Aucun
+
+macros/latex/required/psnfss :
+ Le package PSNFSS \textsf{adobe}
+ adobe (V. 7.2)
+ Sebastian Rahtz <S.Rahtz@elsevier.co.uk>
+ Trad. par : SLC
+ Relu par :
+
+macros/latex/contrib/supported/a4 :
+ Une option de style pour adapter les styles standard de document \LaTeX\
+ a4 (V. 1.2f)
+ Nico Poppelier <Poppelier@elsevier.nl>
+ Johannes Braams <JLBraams@cistron.nl>
+ Trad. par : SLC
+ Relu par : BB
+
+macros/latex/contrib/supported/SIunits :
+ Le package SIunits
+ SIunits (V. 0.06)
+ Marcel Heldoorn <m.heldoorn@physiology.medfac.leidenuniv.nl>
+ Trad. par : JPFD, NLN
+ Relu par :
+
+macros/latex/contrib/supported/Tabbing :
+ Le package Tabbing
+ Tabbing (V. 1.0)
+ Jean-Pierre F. Drucbert <drucbert@onecert.fr>
+ Trad. par : JPFD
+ Relu par : MG
+
+macros/latex/base :
+ \LaTeXe~pour les auteurs de classes et packages
+ clsguide (V. 1999.03.12)
+ LaTeX3 Project team
+ Trad. par : SLC
+ Relu par : BB
+
+macros/latex/base :
+ Options de configuration pour \LaTeXe
+ cfgguide (V. 1998.17.10)
+ LaTeX3 Project team
+ Trad. par : SLC
+ Relu par : FMF
+
+macros/latex/required/tools :
+ Un chantillonneur de polices
+ fontsmpl (V. 0.11)
+ Alan Jeffrey
+ Trad. par : DB
+ Relu par : Aucun
+
+macros/latex/base :
+ Modifier \LaTeX
+ modguide (V. modguide (V. 1995.12.12))
+ LaTeX3 Project team
+ Trad. par : SLC
+ Relu par : FMF, BB
+
+macros/latex/required/tools :
+ Le package somedefs
+ somedefs (V. 0.03)
+ Alan Jeffrey
+ Trad. par : DB
+ Relu par : BB
+
+macros/latex/contrib/supported/answers :
+ Le package answers
+ answers (V. 2.10)
+ Mike Piff
+ Trad. par : JPFD
+ Relu par : MG
+
+macros/latex/contrib/supported/appendix :
+ Le package appendix
+ appendix (V. 1.0)
+ Peter Wilson <peter.r.wilson@boeing.com>
+ Trad. par : JPFD
+ Relu par : MG
+
+macros/latex/contrib/supported/bbm :
+ Utilisation des fontes bbm dans un environnement mathmatique
+ bbm (V. 1.2)
+ Torsten Hilbrich <Torsten.Hilbrich@gmx.net>
+ Trad. par : JPFD
+ Relu par : DB
+
+
+quipe de traduction:
+FMF = Franoise Marre-Fournier <marre-fournier@unilim.fr>
+BB = Benjamin Bayart <bayartb@edgard.fdn.fr>
+JM = Julien Mudry <zeiram@deathsdoor.com>
+NLN = Nicolas Le Novre <nl223@cus.cam.ac.uk>
+JPFD = Jean-Pierre Drucbert
+JPS = Jean-Pierre Sutto
+MG = Mathieu Goutelle <goutelle@mail.dotcom.fr>
+DB = Denis Barbier <barbier@imacs.polytechnique.fr>
+GM = Georges Mariano
+SLC = Sebastien Le Callonnec <slecallo@eleve.emn.fr>
+JCC = Jean-Come Charpentier <Jean-Come.Charpentier@wanadoo.fr>
+
+Contributeurs:
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part1 b/help/LaTeX-FAQ-francaise/part1
new file mode 100644
index 0000000000..0b4691598b
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part1
@@ -0,0 +1,1852 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!oleane.net!oleane!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:17 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - parties 1 a 5
+Message-ID: <faq-fctt-p120010608133117@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p120010501143415@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 1844
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23521 fr.usenet.reponses:20387
+
+Archive-name: fr/faq-latex-francaise/part1
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+fr.comp.text.tex est un forum franais de discussion concernant
+TeX et LaTeX. comp.text.tex est son quivalent anglophone. Cette
+FAQ (recueil des questions les plus frquentes) est
+essentiellement compose partir de messages posts dans ces
+forums et de mon exprience personnelle.
+
+Je tiens souligner que cette FAQ LaTeX ne prtend pas tre
+correcte sur tous les points qu'elle nonce (j'essaie toutefois
+de tester un maximum de rponses mais je ne dispose pas
+toujours de tous les packages), ni mme complte. C'est
+pourquoi, je vous invite tous y contribuer par vos remarques.
+En outre, des exemples concis susceptibles d'illustrer l'une ou
+l'autre des rponses seront les bienvenus.
+
+Concernant l'volution de LaTeX2.09 en LaTeX2e, sachant que
+certains sites utilisent encore l'ancienne version (notamment
+pour travailler sur d'anciens documents utilisant des styles ou
+macros non compatibles avec LaTeX2e), cette FAQ prsente encore
+des aides pour LaTeX2.09. Cependant, il est entendu que ces
+dernires seront amenes disparatre.
+################################################################
+
+ FAQ LaTeX version 2.27 (08/06/2001)
+
+################################################################
+ (premire version : FAQ LaTeX version 1.0 (30/04/96))
+ (c) Copyright 1997 Marie-Paule Kluth
+ Tous droits rservs.
+
+Note (destine aux puristes) :
+Afin de ne pas tomber dans l'excs qui consiste traduire
+toutes les expressions anglo-saxonnes utilises dans LaTeX, en
+franais, on parlera, entre autres, dans ce qui suit de package
+et non d'extension, de viewer, du WEB, etc.
+
+Suite de nombreuses demandes, les accents ont t ajouts. Le
+programme `recode' de GNU est capable d'en gnrer une version
+sans les accents (recode latin1:flat faq_latex). Ceux qui ne
+possdent pas un tel programme peuvent me demander une version
+sans accents par e-mail.
+
+................................................................
+Pour toutes remarques, commentaires ou ajouts, contactez le
+mainteneur par e-mail : bayartb@edgard.fdn.fr
+................................................................
+
+Si vous dsirez, distribuer ce document par FTP ou sur le WEB,
+ou placer un pointeur vers ce dernier, merci de m'en informer
+par e-mail et de me communiquer l'adresse correspondante.
+
+ Redistribution for profit, or in altered content/format
+ prohibited without permission of the author.
+ Redistribution via printed book or CDROM expressly
+ prohibited without consent of the author. Any other
+ redistribution must include this copyright notice and
+ attribution.
+
+Bonne lecture.
+
+================================================================
+THMES ABORDES :
+================================================================
+
+[1] PRSENTATION
+----------------
+# 1.1 # Quelle est l'histoire de (La)TeX ?
+# 1.2 # Quels sont les principes de base de TeX ?
+# 1.3 # Quels sont les principes de base de LaTeX ?
+# 1.4 # Qu'est ce que le prambule du fichier source ?
+# 1.5 # Comment faire ses premiers pas ?
+# 1.6 # Comment sont gres les options de package ?
+# 1.7 # Quelle est la structure d'une page LaTeX ?
+# 1.8 # Quelles sont les commandes de compilation LaTeX ?
+# 1.9 # Quels sont les fichiers utiliss par LaTeX ?
+# 1.10 # A quoi correspondent les messages Overfull ?
+
+[2] DOCUMENTATION
+-----------------
+# 2.1 # Que puis-je lire sur TeX ?
+# 2.2 # Que puis-je lire sur LaTeX2.09 ?
+# 2.3 # Que puis-je lire sur LaTeX2e ?
+# 2.4 # Que puis-je lire sur AMS-LaTeX ?
+# 2.5 # Que puis-je lire sur la typographie ?
+# 2.6 # O trouver une bibliographie complte ?
+# 2.7 # Que puis-je lire sur les fontes ?
+
+[3] SITES WEB
+-------------
+# 3.1 # O trouver des infos sur le WEB ?
+# 3.2 # O trouver cette FAQ ?
+# 3.3 # Existe t'il des listes de discussion francophones ?
+# 3.4 # O trouver d'autres FAQs LaTeX ?
+
+[4] SOURCES TEX ET LATEX
+------------------------
+# 4.1 # O trouver les sources pour Unix ?
+# 4.2 # O trouver les sources pour VMS ?
+# 4.3 # O trouver les sources pour DOS, OS/2, Windows3.x/95/NT ?
+# 4.4 # O trouver les sources pour MacOS ?
+# 4.5 # O trouver d'autres sources ?
+
+[5] DITER LATEX
+----------------
+
+[6] GESTION DE LA MISE EN PAGE
+------------------------------
+# 6.1 # Comment modifier l'interligne d'un document ?
+# 6.2 # Comment grer un document recto-verso ?
+# 6.3 # Comment modifier le style des titres ?
+# 6.4 # Comment obtenir un document multicolonnes ?
+# 6.5 # Comment composer une brochure ?
+# 6.6 # Comment dfinir un format de document ?
+# 6.7 # Comment redfinir les marges d'un document ?
+# 6.8 # Comment changer l'orientation d'un document ?
+# 6.9 # Comment justifier verticalement un paragraphe ?
+# 6.10 # Comment modifier la commande \caption ?
+# 6.11 # Comment modifier un changement de page ?
+# 6.12 # Comment obtenir des colonnes parallles ?
+# 6.13 # Comment dfinir l'espace de dbut de paragraphe ?
+# 6.14 # Comment supprimer la date sur une page de titre ?
+# 6.15 # Comment mettre en valeur la premire lettre d'un chapitre ?
+# 6.16 # Comment prserver les tabulations en mode verbatim ?
+# 6.17 # Comment modifier les enttes de chapitre ?
+# 6.18 # Comment dfinir des tabulations ?
+# 6.19 # Comment obtenir des lettres accentues dans tabbing ?
+# 6.20 # Comment encadrer du texte ?
+# 6.21 # Comment grer des URL WWW ?
+# 6.22 # Comment mettre en page des exercices dont les solutions sont reportes dans un autre paragraphe ?
+# 6.23 # Comment positionner un objet dans une page ?
+# 6.24 # Comment lier le placement des flottants aux sections ?
+# 6.25 # Comment griser le fond (background) d'un paragraphe ?
+# 6.26 # Comment modifier l'espace inter-colonnes ?
+# 6.27 # Comment modifier les environnements de liste ?
+# 6.28 # Comment souligner plusieurs lignes ?
+# 6.29 # Comment raliser des onglets ?
+# 6.30 # Comment raliser des QCM ?
+# 6.31 # Comment modifier l'orientation des flottants ?
+# 6.32 # Comment faire rfrence plusieurs fois la mme note de bas de page ?
+# 6.33 # Comment viter les orphelins en dbut ou fin de page ?
+# 6.34 # Comment dfinir de nouveaux flottants ?
+# 6.35 # Comment utiliser la commande \caption hors d'un environnement flottant ?
+# 6.36 # Comment encadrer un objet flottant ?
+# 6.37 # Comment changer l'orientation d'un caption ?
+# 6.38 # Comment mettre en page un programme ?
+# 6.39 # Comment inclure le source d'un programme ?
+# 6.40 # Comment obtenir un espace inscable ?
+# 6.41 # Comment insrer une page blanche ?
+# 6.42 # Comment supprimer l'indentation des paragraphes ?
+# 6.43 # Comment modifier l'espacement entre caractres ?
+# 6.44 # Comment supprimer certaines coupures de mots ?
+# 6.45 # Comment mettre en forme des quations chimiques ?
+# 6.46 # Comment mettre en page un calendrier ?
+# 6.47 # Comment forcer un caption sur plusieurs lignes ?
+# 6.48 # Comment gnrer des barres de modification dans un document ?
+# 6.49 # Comment encadrer du texte verbatim ?
+# 6.50 # Comment crire du texte en forme de losange ou autre ?
+# 6.51 # Comment isoler les flottants par un trait horizontal ?
+# 6.52 # Comment insrer un espace vertical dans une page ?
+# 6.53 # Comment insrer un espace horizontal dans un texte ?
+# 6.54 # Comment dfinir un style de paragraphe ?
+# 6.55 # quoi sert la commande \stretch ?
+# 6.56 # Comment justifier un paragraphe gauche ou droite ?
+# 6.57 # Comment mettre en page des citations ?
+# 6.58 # Comment insrer un texte sans que LaTeX le mette en forme ?
+# 6.59 # Comment visualiser des espaces ?
+# 6.60 # Comment insrer du code LaTeX dans un document LaTeX ?
+# 6.61 # Comment crire du texte en couleurs ?
+# 6.62 # Comment construire un arbre ?
+# 6.63 # Comment mettre en page un pome ?
+# 6.64 # Comment aligner des paragraphes ?
+# 6.65 # Comment construire une liste d'lments ?
+# 6.66 # Comment faire une note dans une marge ?
+# 6.67 # Comment faire une page de garde ?
+# 6.68 # Comment utiliser \thanks dans chaque titre de chapitre ?
+# 6.69 # Comment mettre un rsum et un abstract dans un document ?
+# 6.70 # Comment dfinir de nouvelles couleurs ?
+# 6.71 # Comment placer des figures face face en recto-verso ?
+# 6.72 # Quelles sont les diffrences entre a4paper et letterpaper ?
+# 6.73 # Comment couper une chane de caractres ?
+# 6.74 # Comment modifier l'espace entre une figure et sa lgende ?
+
+[7] GESTION DES TABLEAUX
+------------------------
+# 7.1 # Comment faire un tableau ?
+# 7.2 # Comment grer les tableaux de plus d'une page ?
+# 7.3 # Comment modifier l'orientation d'un tableau ?
+# 7.4 # Comment nommer un tableau ?
+# 7.5 # Comment modifier l'paisseur des lignes d'un tableau ?
+# 7.6 # Comment griser des cellules d'un tableau ?
+# 7.7 # Comment changer la fonte d'une colonne ?
+# 7.8 # Comment crer des notes de bas de page dans un tableau ?
+# 7.9 # Comment crire un texte sur plusieurs colonnes ?
+# 7.10 # Comment passer certaines cellules en reverse vido ?
+# 7.11 # Comment fixer la largeur d'une colonne ?
+# 7.12 # Comment crire un texte sur plusieurs lignes ?
+# 7.13 # Comment diviser une cellule par une diagonale ?
+# 7.14 # Comment dfinir une colonne en mode mathmatique dans un tableau ?
+# 7.15 # Comment modifier le nombre de tableaux par page ?
+# 7.16 # Comment mettre deux tableaux cte cte ?
+# 7.17 # Comment dfinir un sparateur de colonne ?
+# 7.18 # Comment obtenir des lignes partielles dans un tableau ?
+# 7.19 # Comment viter que du texte de grande taille n'atteigne le cadre des cellules ?
+# 7.20 # Comment fixer la largeur d'un tableau ?
+# 7.21 # Comment tracer des traits discontinus ?
+# 7.22 # Comment fixer la taille et justifier une colonne ?
+# 7.23 # Comment faire une liste de tableaux ?
+
+[8] GESTION DES FIGURES
+-----------------------
+# 8.1 # Comment inclure une figure ?
+# 8.2 # Comment nommer une figure ?
+# 8.3 # Comment placer des figures cte cte ?
+# 8.4 # Comment modifier le nombre de figures par page ?
+# 8.5 # Comment superposer du texte sur des figures ?
+# 8.6 # Comment raliser des captures d'cran ?
+# 8.7 # Comment tracer une courbe ?
+# 8.8 # Comment est gr le positionnement des figures ?
+# 8.9 # Comment placer une lgende ct d'une figure ?
+# 8.10 # Comment insrer des figures dans multicol ?
+# 8.11 # Comment faire apparatre toutes les figures en fin de document ?
+# 8.12 # Comment insrer des images Mathematica ?
+# 8.13 # Comment modifier la taille d'une bounding box ?
+# 8.14 # Comment obtenir une figure avec un titre non numrot ?
+# 8.15 # Comment redfinir le style de caption ?
+# 8.16 # Comment fondre une image dans du texte ?
+# 8.17 # Comment raliser des diagrammes en btons ?
+# 8.18 # Comment faire un organigramme ?
+# 8.19 # Comment centrer une figure trs large ?
+# 8.20 # Comment passer de ps eps ?
+# 8.21 # Comment changer l'orientation d'une figure ?
+# 8.22 # Comment grer des sous-figures sur plusieurs pages ?
+# 8.23 # Comment gnrer une liste des figures d'un document ?
+# 8.24 # Comment faire une figure sous LaTeX ?
+# 8.25 # Comment mettre un commentaire ct d'une figure ?
+
+[9] INCLUSION DE FICHIERS
+-------------------------
+# 9.1 # Comment inclure des fichiers en mode verbatim ?
+# 9.2 # Comment grer un document par parties ?
+# 9.3 # Comment isoler une partie d'un fichier ps ou dvi ?
+# 9.4 # Comment inclure un fichier PICT ?
+# 9.5 # Comment spcifier un chemin pour les fichiers inclure ?
+
+[10] HAUTS ET BAS DE PAGES
+--------------------------
+# 10.1 # Comment dfinir les hauts et bas de page ?
+# 10.2 # Comment obtenir une note de bas de page ?
+# 10.3 # Comment mettre les notes de bas de page en fin de document ?
+# 10.4 # Comment rduire les rappels de titres dans un haut ou bas de page ?
+# 10.5 # Comment rfrencer une note de bas de page ?
+# 10.6 # Comment supprimer la numrotation des pages ?
+# 10.7 # Comment numroter les pages par rapport la dernire ?
+# 10.8 # Comment supprimer le trait de sparation des notes de bas de page ?
+# 10.9 # Comment modifier la numrotation des pages ?
+# 10.10 # Comment supprimer les enttes et bas de page de pages vierges ?
+# 10.11 # Comment grer des en-ttes avec des environnements verbatim multi-pages ?
+# 10.12 # Comment utiliser \footnote dans un titre ?
+# 10.13 # Comment placer les notes de bas de page les unes ct des autres ?
+# 10.14 # Comment rinitialiser le compteur de note de bas de page chaque page ?
+# 10.15 # Comment modifier le style des notes de bas de page ?
+# 10.16 # Comment utiliser le mode verbatim dans une note de bas de page ?
+# 10.17 # Comment viter qu'une note de bas de page s'tale sur plusieurs pages ?
+
+[11] LATEX, LE FRANAIS ET LES AUTRES LANGUES
+---------------------------------------------
+# 11.1 # Comment franciser un document LaTeX ?
+# 11.2 # Comment corriger les coupures de mots accentus ?
+# 11.3 # Comment utiliser les lettres accentues ?
+# 11.4 # Comment composer du texte en grec moderne ou classique ?
+# 11.5 # Comment composer du texte en hbreu moderne ou classique ?
+# 11.6 # Comment composer du texte en arabe ?
+# 11.7 # Comment dfinir les csures de groupes de mots conjugus avec un trait d'union ?
+
+[12] MATHMATIQUES
+------------------
+# 12.1 # Comment passer en mode mathmatique ?
+# 12.2 # Qu'est que AMS-LaTeX ?
+# 12.3 # Comment crire les symboles d'ensembles ?
+# 12.4 # Comment numroter les quations ?
+# 12.5 # Comment aligner des quations ?
+# 12.6 # Comment gnrer des vecteurs ?
+# 12.7 # Comment crire du texte en mode mathmatique ?
+# 12.8 # Comment ajuster la taille de dlimiteurs ?
+# 12.9 # Comment changer de fonte en mode mathmatique ?
+# 12.10 # Comment obtenir le L de la transforme de Laplace ?
+# 12.11 # Comment raliser un tableau en mode mathmatique ?
+# 12.12 # Comment obtenir d'autres symboles mathmatiques ?
+# 12.13 # Comment dfinir une fonction ?
+# 12.14 # Comment dfinir une matrice ?
+# 12.15 # Comment encadrer des formules ?
+# 12.16 # Comment ajuster la longueur d'une flche par rapport un texte ?
+# 12.17 # Comment obtenir des indices ou exposants gauche ?
+# 12.18 # Comment tracer des diagrammes commutatifs ?
+# 12.19 # Comment ajuster la taille de certains oprateurs ?
+# 12.20 # Comment mettre en page des algorithmes ?
+# 12.21 # Comment mettre en page des formules longues ?
+# 12.22 # Comment crer des units de mesure ?
+# 12.23 # Comment crire proprement a/b ?
+# 12.24 # Comment crer des notes de bas de page dans une formule mathmatique ?
+# 12.25 # Comment forcer le style d'un tableau displaystyle ?
+# 12.26 # Comment rduire les espaces grs par eqnarray ?
+# 12.27 # Comment rduire la taille des indices ?
+# 12.28 # Comment aligner des indices ?
+# 12.29 # Comment mettre en page des thormes ?
+# 12.30 # Comment changer la taille de la fonte ?
+# 12.31 # A quoi sert la commande \displaystyle ?
+# 12.32 # Comment aligner des donnes sur le point dcimal ?
+# 12.33 # Comment grer les espaces en mode mathmatique ?
+# 12.34 # Comment obtenir des accolades horizontales ?
+# 12.35 # Comment obtenir des points de suspensions ?
+# 12.36 # Comment mettre en page un systme d'quations ?
+# 12.37 # Comment mettre en page des diagrammes de Feynman ?
+# 12.38 # Comment obtenir une fraction ?
+# 12.39 # Comment obtenir une racine ?
+# 12.40 # Quels sont les dlimiteurs disponibles ?
+# 12.41 # Comment appeler les lettres grecques ?
+# 12.42 # Quels sont les accents mathmatique standards ?
+# 12.43 # Comment superposer deux symboles ?
+# 12.44 # Comment dfinir un nouvel oprateur ou symbole ?
+# 12.45 # Comment obtenir des lettres grecques en gras ?
+# 12.46 # Comment tracer un tableau de variations ?
+
+[13] RFRENCES CROISES
+------------------------
+# 13.1 # Quelles sont les commandes de base ?
+# 13.2 # Comment obtenir un renvoi une page ?
+# 13.3 # Comment obtenir des rfrences croises partir de plusieurs sources ?
+# 13.4 # Comment dfinir des liens hypertexte sous LaTeX ?
+# 13.5 # Comment faire rfrence ses propres compteurs ?
+
+[14] TABLE DES MATIRES
+-----------------------
+# 14.1 # Comment gnrer une table des matires ?
+# 14.2 # Comment gnrer plusieurs tables des matires ?
+# 14.3 # Comment ajouter une entre dans la table des matires ?
+# 14.4 # Comment changer le titre de la table des matires ?
+# 14.5 # Comment changer la profondeur de la table des matires ?
+# 14.6 # Comment grer des chapitres de prface, d'introduction, et de conclusion non numrots ?
+# 14.7 # Comment enlever le numrotation des pages de tdm ?
+
+[15] BIBLIOGRAPHIE SOUS LATEX
+-----------------------------
+# 15.1 # Comment construire une bibliographie ?
+# 15.2 # Comment grer plusieurs bibliographies ?
+# 15.3 # Comment changer de langue dans une bibliographie ?
+# 15.4 # Comment renvoyer une rfrence en note de bas de page ?
+# 15.5 # Comment faire rfrence un document ?
+# 15.6 # Comment grouper des rfrences multiples ?
+# 15.7 # Comment changer le titre de la bibliographie ?
+# 15.8 # Comment changer le style de la bibliographie ?
+# 15.9 # Comment construire une bibliographie partir de plusieurs fichiers .bib ?
+# 15.10 # Comment utiliser la commande \cite dans un \caption ?
+# 15.11 # Comment rfrencer une thse franaise ou un mmoire ?
+# 15.12 # Comment supprimer la virgule supplmentaire dans une liste d'auteurs ?
+# 15.13 # Comment configurer la commande \cite ?
+# 15.14 # Comment construire une liste d'auteurs ?
+# 15.15 # Comment spcifier un tri dans une bibliographie ?
+# 15.16 # Comment rfrencer les pages contenant des citations ?
+# 15.17 # O trouver des styles de bibliographie ?
+# 15.18 # Comment faire des rfrences croises ?
+# 15.19 # Comment citer une URL ?
+# 15.20 # Comment dfinir des initiales deux lettres ?
+# 15.21 # Comment conserver les majuscules dans les titres ?
+# 15.22 # Comment changer l'espace entre les item ?
+# 15.23 # Comment raliser des fiches de lecture ?
+# 15.24 # Comment utiliser la commande \cite dans un item ?
+# 15.25 # Comment gnrer l'expression et al automatiquement ?
+
+[16] INDEX
+----------
+# 16.1 # Quelles sont les commandes de base ?
+# 16.2 # Comment construire un index hirarchique ?
+# 16.3 # Quels sont les gnrateurs d'index ?
+# 16.4 # Comment changer le style de certains mots indexs ?
+# 16.5 # Comment changer le style des pages de rfrence ?
+# 16.6 # Comment rappeler certains mots dans un haut de page ?
+# 16.7 # Comment gnrer plusieurs index ?
+# 16.8 # Qu'est ce que IdXTeX ?
+# 16.9 # Qu'est ce que xindy ?
+
+[17] GLOSSAIRE
+--------------
+# 17.1 # Quelles sont les commandes de base ?
+# 17.2 # Quels sont les gnrateurs de glossaire ?
+
+[18] STYLES PRDFINIS
+----------------------
+# 18.1 # O trouver un style de thse ?
+# 18.2 # Comment faire son CV en LaTeX ?
+# 18.3 # O trouver un format de publication ?
+# 18.4 # O trouver un style de manuel de rfrence ?
+# 18.5 # O trouver un style de poster ?
+# 18.6 # Comment crer son propre style ?
+
+[19] CRATION DE TRANSPARENTS
+-----------------------------
+# 19.1 # Quels sont les packages et styles existants ?
+# 19.2 # Comment dfinir un contour pour des transparents ?
+# 19.3 # Comment inclure des commentaires dans les transparents ?
+# 19.4 # Comment modifier l'interligne sous seminar ?
+# 19.5 # Comment dfinir des en-ttes et pieds de pages ?
+# 19.6 # Comment modifier la taille du cadre d'un transparent ?
+# 19.7 # Comment empcher les figures de flotter ?
+# 19.8 # Comment grer la couleur avec seminar ?
+# 19.9 # Comment imprimer des transparents en miroir ?
+# 19.10 # Comment inclure une image de fond ?
+# 19.11 # Comment imprimer plusieurs transparents par page ?
+
+[20] LETTRES, MAILING ET FAXS
+-----------------------------
+# 20.1 # Comment structurer une lettre ?
+# 20.2 # Comment prparer un mailing ?
+# 20.3 # Comment faire des rfrences dans une lettre ?
+# 20.4 # Comment mettre en page un fax ?
+# 20.5 # Comment positionner une adresse pour une enveloppe fentre ?
+# 20.6 # Comment suppprimer la date sur une lettre ?
+# 20.7 # Comment inclure une figure dans une lettre ?
+
+[21] SYMBOLES ET LOGOS
+----------------------
+# 21.1 # O trouver des symboles lectroniques ?
+# 21.2 # Comment dessiner des circuits lectroniques ?
+# 21.3 # Quelles sont les polices de symboles sous LaTeX ?
+# 21.4 # Comment obtenir les symboles mle et femelle ?
+# 21.5 # Comment obtenir le symbole degr ?
+# 21.6 # O trouver des symboles astronomiques ?
+# 21.7 # O trouver une police de symboles phontiques ?
+# 21.8 # O trouver des oprateurs de logique floue ?
+# 21.9 # Comment obtenir le symbole de paragraphe ?
+# 21.10 # Comment obtenir le caractre 'registered' ?
+# 21.11 # O trouver le symbole trade-mark ?
+# 21.12 # Comment obtenir un underscore ?
+# 21.13 # O trouver le symbole radioactif ?
+# 21.14 # Comment obtenir le logo LaTeX ?
+# 21.15 # Comment obtenir le logo LaTeX2e ?
+# 21.16 # O trouver des chiffres entours ?
+# 21.17 # Comment obtenir le symbole numro ?
+# 21.18 # Comment obtenir les symboles pourcent et pourmille ?
+# 21.19 # Comment obtenir un e dans l'o ?
+# 21.20 # Quels sont les symboles rservs dans LaTeX ?
+# 21.21 # Comment obtenir des lettres cursives ?
+# 21.22 # Comment obtenir le logo AMS-(La)TeX ?
+# 21.23 # Quels sont les symboles par dfaut de LaTeX ?
+# 21.24 # Quels sont les diffrents tirets ?
+# 21.25 # Comment obtenir le symbole arobasse ?
+# 21.26 # Comment obtenir un backslash ?
+# 21.27 # Comment faire un carr plain de fin de dmonstration ?
+
+[22] MUSIQUE
+------------
+# 22.1 # Comment crire de la musique sous LaTeX ?
+# 22.2 # Comment convertir du midifile en MusicTeX ?
+# 22.3 # Existe-t'il une liste de discussion de musique ?
+# 22.4 # Comment diter un livre de chants ?
+# 22.5 # Comment mettre en page un programme de concert ?
+
+[23] CONVERSIONS DE FICHIERS
+----------------------------
+# 23.1 # Comment gnrer un fichier .ps partir d'un .dvi ?
+# 23.2 # Qu'est ce que le "Literate Programming" ?
+# 23.3 # Comment convertir du LaTeX en word ?
+# 23.4 # Comment convertir du word en LaTeX ?
+# 23.5 # Comment convertir du scribe en LaTeX ?
+# 23.6 # Comment convertir du WordPerfect en LaTeX ?
+# 23.7 # Comment convertir du LaTeX en RTF ?
+# 23.8 # Comment convertir du RTF en (La)TeX ?
+# 23.9 # Comment convertir du Excel en LaTeX ?
+# 23.10 # Comment convertir du HTML en LaTeX ?
+# 23.11 # Comment convertir du LaTeX en HTML ?
+# 23.12 # Comment convertir un fichier dvi en ascii ?
+# 23.13 # Comment convertir du WEB en LaTeX ?
+# 23.14 # Comment convertir du TeX en Framemaker ?
+# 23.15 # Comment enlever les balises LaTeX d'un document ?
+# 23.16 # Comment convertir du SGML en (La)TeX ?
+# 23.17 # Comment convertir du WinWord en LaTeX ?
+# 23.18 # Comment convertir un fichier 8 bits en fichier 7 bits ?
+# 23.19 # Comment convertir un fichier ChiWriter en TeX ?
+# 23.20 # O trouver une FAQ de convertisseurs (La)TeX/Traitement de texte ?
+# 23.21 # Comment convertir une image en police metafont ?
+# 23.22 # Comment convertir un fichier postscript en ascii ?
+# 23.23 # Comment convertir un fichier pdf en ascii ?
+# 23.24 # Comment convertir du LaTeX en PDF ?
+# 23.25 # Comment dfinir son propre format de sortie ?
+
+[24] PRVIEWERS ET VIEWERS
+--------------------------
+# 24.1 # O trouver un previewer ?
+# 24.2 # O trouver un viewer ?
+# 24.3 # Comment visualiser des fichiers non postscript sous xdvi ?
+
+[25] LOGICIELS DE DESSINS
+-------------------------
+# 25.1 # O trouver un logiciel de dessin ?
+# 25.2 # Comment inclure des formules Latex dans Xfig ?
+# 25.3 # Comment grer diffrents formats de figures ?
+
+[26] CORRECTEUR
+---------------
+# 26.1 # O trouver un correcteur orthographique ?
+# 26.2 # O trouver un vrificateur de syntaxe LaTeX ?
+
+[27] ASSOCIATIONS
+-----------------
+# 27.1 # Qu'est ce que l'association GUTenberg ?
+# 27.2 # Qu'est ce que l'association TUG ?
+# 27.3 # Qu'est ce que l'association AsTeX ?
+
+[28] FONTES
+-----------
+# 28.1 # Que signifient les sigles T1, mf, fd etc. ?
+# 28.2 # Quels sont les attributs d'une fonte ?
+# 28.3 # Comment utiliser une fonte ?
+# 28.4 # Comment changer la forme d'une fonte ?
+# 28.5 # Comment changer la taille d'une fonte ?
+# 28.6 # Comment modifier la fonte des numros de paragraphe ?
+# 28.7 # Comment modifier la fonte du mode verbatim ?
+# 28.8 # Comment raliser des changements de fontes relatifs ?
+# 28.9 # Comment mettre en vidence une portion de texte ?
+# 28.10 # O trouver des fontes ?
+# 28.11 # Comment suivre le chargement des fontes ?
+# 28.12 # Pourquoi MakeTeXPK est lanc alors que la fonte existe ?
+# 28.13 # Comment utiliser \textsc dans un titre en conservant le gras ?
+# 28.14 # Comment utiliser des fontes TrueType?
+
+[29] DIVERS
+-----------
+# 29.1 # A quoi sert la commande \par ?
+# 29.2 # Comment commenter une partie d'un source LaTeX ?
+# 29.3 # Comment utiliser LaTeX sur des petites machines ?
+# 29.4 # Comment visualiser des paramtres ?
+# 29.5 # Comment visualiser des compteurs ?
+# 29.6 # A quoi servent \makeatletter et \makeatother ?
+# 29.7 # Comment numroter les lignes d'un document ?
+# 29.8 # A quoi sert la commande \special ?
+# 29.9 # Comment raliser des calculs avec les variables LaTeX ?
+# 29.10 # O trouver une fonte 9pt ?
+# 29.11 # Comment automatiser les compilations LaTeX ?
+# 29.12 # Comment obtenir des cadres gris ?
+# 29.13 # Comment obtenir certaines abrviations ?
+# 29.14 # Comment grer les espaces aprs une macro ?
+# 29.15 # O trouver les notices d'utilisation des packages ?
+# 29.16 # Comment obtenir des listes d'objets flottants ?
+# 29.17 # Comment connatre les versions des fichiers utiliss lors d'une compilation ?
+# 29.18 # Pourquoi certaines commandes sont elles indpendantes ?
+# 29.19 # Comment installer un package ?
+# 29.20 # Comment gnrer des codes barres ?
+# 29.21 # Comment grer des abbrviations ?
+# 29.22 # Comment imprimer un fichier postscript sur une imprimante non postscript ?
+# 29.23 # Comment surcharger une commande dj existante ?
+# 29.24 # Comment reporter l'excution d'une commande la fin d'une page ?
+# 29.25 # Comment dfinir des scripts interactifs ?
+# 29.26 # Comment identifier une version provisoire ?
+# 29.27 # Comment obtenir des caractres barrs ?
+# 29.28 # A quoi sert la commande \ensuremath ?
+# 29.29 # A quoi servent les commandes \(re)newcommand ?
+# 29.30 # O trouver des hirondelles ?
+# 29.31 # Comment tracer des lignes ?
+# 29.32 # Comment imprimer le caractre ~ ?
+# 29.33 # Comment visualiser tous les caractres d'une fonte ?
+# 29.34 # A quoi sert % dans les macros ?
+# 29.35 # Comment inclure l'heure dans un document ?
+# 29.36 # Comment compter le nombre de mots d'un fichier ?
+# 29.37 # Comment rendre inactif un caractre ?
+# 29.38 # Comment utiliser le mode verbatim dans une commande ?
+# 29.39 # Comment redfinir la commande \year ?
+# 29.40 # Qu'est ce que la magnification ?
+# 29.41 # Comment sont grs les postscripts dans LaTeX ?
+# 29.42 # Pourquoi LaTeX n'accepte-t'il pas tous les formats d'image ?
+# 29.43 # A quoi sert la commande \(re)newenvironment ?
+# 29.44 # Comment rcuprer le nom du fichier compil ?
+# 29.45 # Comment grer des conditions de traitement dans un style ?
+# 29.46 # A quoi servent les commandes \setlength et \addtolength ?
+# 29.47 # Quelles sont les units de mesure de TeX ?
+# 29.48 # A quoi sert la commande \mbox ?
+# 29.49 # Comment obtenir des points de suspension ?
+# 29.50 # Comment dsactiver une ligature ?
+# 29.51 # Comment grer les versions d'un document ?
+# 29.52 # Comment changer certains titres ?
+# 29.53 # Comment insrer un code source dans un document ?
+# 29.54 # Comment tracer une ligne horizontale ?
+# 29.55 # Comment gnrer un espace invisible de taille donne ?
+# 29.56 # Qu'est ce qu'une correction italique ?
+# 29.57 # Quels sont les accents accessibles sous LaTeX ?
+# 29.58 # Comment crire dans un fichier pendant une compilation ?
+# 29.59 # Comment grer des compteurs ?
+# 29.60 # Quels sont les diffrents styles de compteurs ?
+# 29.61 # Comment programmer un traitement itratif ?
+# 29.62 # A quoi servent les commandes savebox ?
+# 29.63 # Comment rsoudre certaines incompatibilits de packages ?
+# 29.64 # Qu'est ce que Lollipop ?
+# 29.65 # J'ai un problme avec babel !
+# 29.66 # Qu'est ce que cette FAQ ?
+
+[30] REMERCIEMENTS ET CONTRIBUTIONS
+-----------------------------------
+
+================================================================
+[1] PRSENTATION
+================================================================
+
+# 1.1 # Quelle est l'histoire de (La)TeX ?
+------------------------------------------
+TeX (1978) est le formateur de texte de D. E. Knuth. A
+l'origine, Knuth a dvelopp TeX (en WEB cf. paragraphe 23.2)
+notamment pour raliser de beaux documents et crire des
+formules mathmatiques.
+
+LaTeX, crit par L. Lamport (1982), est un jeu de macros
+au-dessus de TeX, plus facile utiliser que ce dernier. Il
+propose notamment diffrents styles de document auxquels
+correspondent des classes de document et une grande diversit
+de macros qui rpondent divers besoins des auteurs. LaTeX a
+t conu pour rdiger des articles, des rapports, des thses ou
+des livres ou pour prparer des transparents. On peut insrer
+dans le texte, des dessins, des tableaux, des formules
+mathmatiques et des images sans avoir se soucier (ou presque)
+de leur mise en page. Les documents produits avec LaTeX et TeX
+sont d'une excellente qualit typographique.
+
+Plain TeX crit galement par D. E. Knuth, tait le premier jeu
+(minimal) de macros par dessus TeX. De mme Eplain, de K. Berry,
+est un jeu de macros intermdiaire entre TeX et LaTeX.
+
+Suite une large diffusion de LaTeX beaucoup d'extensions ont
+t cres par diffrents utilisateurs. Grce Murphy, ces
+extensions ont introduit un certain nombre d'incompatibilits
+et ont port atteinte la portabilit de LaTeX. C'est de cette
+situation qu'est n le projet de normalisation LaTeX3, sous la
+direction des gurus LaTeX : L. Lamport, F. Mittelbach, C.
+Rowley, R. Schopf et tant d'autres... Pour plus de dtails,
+consulter :
+http://www.latex-project.org/
+
+Toutefois, pour ne pas perturber les actuels utilisateurs de
+LaTeX, la version provisoire normalise s'appelle LaTeX2e (1994)
+et elle est compatible (dans la mesure du possible) avec les
+anciens standards. Ainsi tous les documents crits pour
+LaTeX2.09 peuvent tre compils sous LaTeX2e en mode "LaTeX2.09
+compatibility mode".
+
+Remarque : cette compatibilit sera amene disparatre au fur
+ et mesure des volutions vers LaTeX3.
+
+Les membres du projet LaTeX3 travaillent actuellement sur le
+futur LaTeX3. Autrement dit, LaTeX2e ne devrait plus beaucoup
+voluer.
+
+Il existe aussi omega, une extension 16 bits de TeX qui utilise
+unicode comme reprsentation interne et autorise ainsi la
+composition de textes multi-lingues dans les langues telles que
+l'arabe, le chinois ou les langues du continent indien. Pour
+plus de renseignements, vous pouvez consulter : les cahiers
+GUTenbeg, TUGboat, ftp://ftp.ens.fr/pub/tex/yannis/omega/,
+ftp://ftp.ens.fr/pub/tex/yannis/omega-babel/, ...
+
+Signalons galement NTS, un projet trs long terme qui vise
+d'abord enrichir TeX mais qui terme, n'en gardera que les
+concepts.
+
+# 1.2 # Quels sont les principes de base de TeX ?
+-------------------------------------------------
+Le principe de base de TeX est la bote ! TeX met tout dans des
+botes et l'assemblage de ces botes suivant des rgles donnes
+permet de mettre en page des documents.
+
+A l'origine, TeX a t conu aussi bien pour crer des documents
+d'une page de texte, que des documents de plusieurs centaines de
+pages contenant des formules mathmatiques, des tableaux, des
+figures, etc. TeX travaille donc comme un imprimeur sans subir
+les contraintes mcaniques inhrentes aux outils de ce dernier.
+Sa prcision est sans limite puisque son unit de base est le
+point et que les calculs qu'il suscite sont effectus par les
+ordinateurs.
+
+Un des avantages de TeX est qu'il possde une vision globale des
+choses. TeX ne se place pas uniquement au niveau du caractre
+que l'auteur frappe mais aussi au niveau du mot, de la ligne, du
+paragraphe, de la page ou du document dans son entier pour
+valuer ses critres de beaut. La dimension esthtique du
+document est ainsi prise en compte et gre de manire ce
+qu'elle soit maximale.
+
+Les critres de beaut utiliss dpendent le plus souvent des
+rgles typographiques attaches la langue ou au langage
+employ (mathmatiques par exemple), mais il peut galement,
+tout moment, prendre en compte les gots de l'auteur. TeX gre
+ainsi la ponctuation, les ligatures, les coupures de mots et
+les justifications verticales et horizontales.
+
+Un autre avantage de TeX est la facilit avec laquelle il donne
+accs toutes ces possibilits de composition. En mathmatiques
+par exemple, il offre une quantit incroyable de symboles et
+connat leurs conventions de mise en page (taille, fonte,
+espacement, etc).
+
+Un dernier avantage couvre tous les problmes de numrotation
+des paragraphes, de tables des matires, des figures, de
+rfrences croises, de bibliographie, d'index, etc, etc. Toutes
+ces aides de lecture sont gres automatiquement par TeX.
+L'auteur a peu s'en soucier, il n'a qu' les dclarer.
+
+En conclusion, vous n'avez qu' penser au contenu de votre
+document, TeX se charge du reste.
+
+# 1.3 # Quels sont les principes de base de LaTeX ?
+---------------------------------------------------
+LaTeX peut tre considr comme un langage de programmation
+volu dans le sens o il s'appuie sur TeX qui est un langage de
+plus bas niveau. Langage de programmation signifie galement que
+le document que l'on veut crer doit tre dcrit dans un fichier
+source (.tex) puis doit tre compil. Ainsi, le compilateur
+LaTeX prend en entre un fichier source crit en LaTeX et
+produit en sortie un fichier .dvi (device independent). Ce
+fichier peut ensuite tre converti en fichier postscript avant
+d'tre imprim. Les fichiers dvi et postscript peuvent tre
+visualiss l'cran l'aide de (pre)viewers.
+
+L'intrt du format dvi est qu'il permet TeX et LaTeX d'tre
+indpendants du matriel qui sera utilis pour la visualisation
+ou l'impression finale du document.
+
+Le fichier source (fichier.tex) doit comprendre un certain
+nombre de commandes (balises) LaTeX qui vont permettre au
+compilateur LaTeX de construire un fichier "device independent"
+(.dvi). La plupart des commandes LaTeX se caractrisent par le
+fait qu'elles commencent par un "backslash", que leurs
+arguments obligatoires apparaissent entre accolades ({ et }) et
+que leurs arguments optionnels apparaissent entre crochets ([ et
+]). La structure minimale d'un rapport est en LaTeX2e est la
+suivante :
+
+Exemple :
+\documentclass{classe}
+\begin{document}
+ Votre texte...
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : Le passage de LaTeX2.09 LaTeX2e se traduit dans
+ l'en-tte des documents par :
+
+ \documentclass[options]{class}
+ \usepackage{style}
+ \usepackage{package}
+
+ au lieu de :
+
+ \documentstyle[options,styles,packages]{class}
+
+ATTENTION toutefois, certains styles LaTeX2.09 ne seront pas
+reconnus par LaTeX2e.
+
+Les commandes LaTeX dcrivent ainsi la classe d'un document, sa
+structure, etc. Les principales classes de document disponibles
+sont : 'article', 'report', 'book', 'letter' et 'slides'. Il
+existe galement un certain nombre d'options qui permettent de
+modifier le style par dfaut d'une classe (le format a4, la
+taille de la fonte 12pt, etc). Ces classes et options
+permettent de disposer d'une structure de base pour un
+document, mais libre vous ensuite de dfinir vos propres
+structures grce aux styles offerts, aux packages disponibles
+notamment sur les sites CTAN (cf. paragraphe 3.1) et/ou vos
+propres macros TeX et LaTeX.
+
+L'intrieur d'un document de classe 'article', 'report' ou
+'book' est ensuite structur grce aux balises disponibles de
+type :
+\part{}, \chapter{}, \(sub)*section{}, etc. Les lettres et
+les transparents font appel d'autres structures particulires
+(cf. chapitres 19 et 20).
+
+Les informations prsentes dans ces structures peuvent tre
+mises sous diffrentes formes grce des environnements tels
+que tabular ou itemize.
+
+Exemple :
+\documentclass[12pt]{report}
+\usepackage{french}
+
+\title{Mon premier document {\LaTeX} \\
+ Qu'il est beau ! !}
+\author{C'est moi l'auteur.}
+
+\begin{document}
+
+\maketitle
+\tableofcontents
+
+\part{Une partie.}
+ \chapter{Un chapitre.}
+ Texte...
+ \section{Une section.}
+ Texte...
+ \section{Une autre section.}
+ Texte...
+ \subsubsection{Avec une sous-section.}
+ Texte...
+ \subsubsection{Plus une autre.}
+ \begin{table}[htbp]
+ \begin{center}
+ \begin{tabular}{|c||c|}
+ \hline
+ donn\'ees & donn\'ees \\
+ \hline
+ \end{tabular}
+ \caption{Titre table. \label{table-}}
+ \end{center}
+ \end{table}
+\part{Une courte deuxi\`eme partie.}
+Texte...
+\appendix
+\chapter{Et une annexe pour finir.}
+Texte...
+\begin{itemize}
+ \item bla bla 1
+ \item bla bla 2
+\end{itemize}
+\end{document}
+%%%% fin exemple %%%%
+
+# 1.4 # Qu'est ce que le prambule du fichier source ?
+------------------------------------------------------
+Les appels des packages ainsi que les dfinitions de
+nouvelles commandes sont placs dans le prambule du document
+LaTeX (i.e. entre les balises \documentstyle (LaTeX2.09) ou
+\documentclass (LaTeX2e) et la commande \begin{document}).
+
+# 1.5 # Comment faire ses premiers pas ?
+----------------------------------------
+En plus de la prsentation faite ci-dessus quelques notions
+supplmentaires sont utiles la comprhension de LaTeX.
+Celles-ci concernent essentiellement la saisie d'un texte.
+
+Lors que l'on dsire travailler dans une langue comportant des
+caractres accentus LaTeX propose des saisies un peu barbares
+surtout aux yeux des dbutants (\'{e} pour par exemple) mais
+qui permettent de conserver la portabilit du document ainsi
+saisi sur tous systmes (caractres cods sur 7 bits). En
+revanche l'utilisation de fontes contenant des caractres
+accentus (codes sur 8 bits) rduit cette portabilit (pour
+plus de dtails lire les questions 11.3 et 28.1).
+
+Autre remarque importante du point de vue de la gestion des
+espaces et des retours chariot inclus dans le fichier
+source (.tex) d'un document. LaTeX gre tout seul les espaces :
+il est inutile de taper plusieurs espaces de suite entre deux
+mots, ils seront transforms en un seul dans le fichier .dvi.
+
+En outre, UN retour chariot est considr comme un espace, sauf
+s'il est suivi d'un deuxime, il marque alors la fin d'un
+paragraphe et le prochain sera indent. On peut alors sauter
+autant de lignes que l'on veut dans le texte, cela n'a aucun
+effet supplmentaire. Un passage la ligne peut tre forc par
+\\ ou par \newline mais dans ce cas, la premire ligne du
+nouveau paragraphe ne sera pas indente. \\* empche un saut
+de page aprs le saut de ligne demand. La commande \par permet
+de commencer un nouveau paragraphe en laissant un espace
+vertical plus important et en indentant.
+
+Remarque : la commande \\[lgr]{} peut prendre comme paramtre une
+ longueur lgr pour augmenter localement un interligne.
+
+En LaTeX, tout ce qui suit un % n'est pas lu, jusqu'au prochain
+retour chariot. (Au passage le caractre % peut alors tre
+obtenu par \%.)
+
+# 1.6 # Comment sont gres les options de package ?
+----------------------------------------------------
+Quand on utilise plusieurs packages :
+\usepackage{package1,package2}
+et que l'on veut utiliser une option du package1 qui n'existe
+pas pour le package2, on peut crire :
+\usepackage[option1]{package1}
+\usepackage{pckge2}
+Cela vite un message du type "unknown option1 for pckge2" qui
+peut apparatre quand on crit
+\usepackage[option1]{package1,package2}.
+
+On peut galement crire :
+\documentclass[option1,gnagna]{article}
+\usepackage{pckge1,pckge2}
+qui permet de conserver l'ordre de chargement des packages mais
+pas celui dans lequel seront excutes les options par tel
+package. Les options de classe sont globales et descendent
+toutes les extensions charges si elles sont dfinies pour ces
+extensions (certaines options sont par nature globales comme
+draft, final, french, a4paper, dvips...).
+
+# 1.7 # Quelle est la structure d'une page LaTeX ?
+--------------------------------------------------
+La commande \layout du package 'layout' permet de visualiser la
+structure d'une page et ses diffrents paramtres. Globalement
+elle est compose du corps du texte, d'une entte et d'un pied
+de page. Des marges sont galement dfinies de chaque ct du
+corps du texte.
+
+Exemple :
+\documentclass{report}
+\usepackage{layout}
+\begin{document}
+\layout
+\end{document}
+%%%% fin exemple %%%%
+
+A chaque classe de documents sont associes diffrentes valeurs
+aux paramtres de mise en page. L'utilisateur peut galement
+redfinir ces valeurs de paramtres. Cela lui permet de grer sa
+propre mise en page. Cette FAQ donne un certain nombre de moyens
+dans ce but.
+
+Pour les documents devant tre imprims en recto-verso,
+\oddsidemargin dfinit la marge gauche des pages impaires
+(recto), et \evensidemargin la marge gauche des pages paires
+(verso). Pour les documents simple face, la commande
+\oddsidemargin suffit.
+
+Les principaux paramtres d'une page sont les suivants :
++ \textheight dfinit hauteur du texte.
++ \textwidth dfinit la largeur du texte.
++ \columnsep dfinit l'espace entre colonnes pour un document
+multi-colonnes.
++ \columnseprule dfinit la largeur de la ligne qui spare les
+colonnes d'un document multi-colonnes (par dfaut ce paramtre
+vaut 0pt i.e. pas de ligne).
++ \columnwidth dfinit la largeur d'une colonne. Ce paramtre
+est calcul automatiquement par LateX d'aprs \textwidth et
+\columnsep.
++ \linewidth dfinit la longueur de la ligne courante. Ce
+paramtre est gnralement utilis dans des environnements qui
+redfinissent les marges.
++ \evensidemargin dfinit un espace supplmentaire dans la marge
+gauche des pages paires des documents recto-verso.
++ \oddsidemargin dfinit cet espace pour les pages impaires d'un
+document recto-verso ou pour toutes les pages dans le cas d'un
+document recto uniquement.
++ \footskip dfinit la distance entre la dernire ligne du texte
+et la premire ligne du bas de page.
++ \headheight dfinit la hauteur de l'entte.
++ \headsep dfinit la distance entre la dernire ligne d'entte
+et la premire ligne du corps du document.
++ \topmargin dfinit un espace supplmentaire au dessus de
+l'entte.
++ \marginparpush dfinit l'espace vertical minimum entre deux
+notes de marge.
++ \marginparsep dfinit l'espace horizontal entre entre le corps
+du document et les notes de marge.
++ \marginparwidth dfinit la largeur des notes de marge.
++ \paperheight dfinit la hauteur du papier sur lequel le
+document sera imprim.
++ \paperwidth dfinit sa largeur.
+
+# 1.8 # Quelles sont les commandes de compilation LaTeX ?
+---------------------------------------------------------
+A partir d'un fichier source fichier.tex, pour gnrer un
+fichier fichier.dvi, il faut appliquer :
+ latex fichier.tex
+Lorsqu'une compilation choue sur une erreur, la ligne o est
+situe l'erreur est indique. L'emplacement de l'erreur dans la
+ligne est prcis par un retour la ligne. Une explication
+succincte de l'erreur est galement fournie.
+
++ La commande ? permet alors d'avoir un menu d'aide.
++ La commande h peut permettre d'avoir une explication plus
+dtaille de l'erreur sur laquelle LaTeX s'est arrt.
++ La commande return peut permettre de forcer la suite de la
+compilation.
++ La commande s permet de visualiser les messages d'erreur
+suivants.
++ La commande r permet de poursuivre la compilation sans arrt.
++ La commande q permet de continuer la compilation sans
+messages.
++ La commande i permet d'insrer quelque chose (une balise
+oublie par exemple) pour pouvoir poursuivre la compilation.
++ La commande e permet d'diter le fichier source.
++ La commande x permet d'abandonner la compilation.
++ Un chiffre de 1 9 permet d'ignorer les x prochains
+caractres du source.
+
+Lorsque la compilation se termine normalement, elle produit un
+fichier fichier.dvi qui peut tre visualis par un utilitaire
+tel que :
+ (UNIX) xdvi fichier.dvi
+
+A partir d'un fichier fichier.dvi, pour gnrer un fichier
+postscript, il faut utiliser un utilitaire tel que :
+ (UNIX) dvips fichier.dvi
+
+Le fichier fichier.ps alors gnr peut tre imprim. Par
+exemple : (UNIX) lpr -Pimprimante fichier.ps
+
+# 1.9 # Quels sont les fichiers utiliss par LaTeX ?
+----------------------------------------------------
+Il en existe diffrentes sortes :
++ les fichiers de compilation sont des .tex, .ltx, .toc, .lof,
+.lot, .idx, .ilg, .ind, .ist, .bbl, .bib, .blg, .bst, .aux,
+.dvi, .log, .texlog, .lis, .list, .ps,
++ les styles o macros sont dfinis dans des fichiers .cls,
+.clo, .dtx, .sty, .fmt,
++ les caractres sont dcrits dans des fichiers .tfm, .mf, .fd,
+.pk.
+
+# 1.10 # A quoi correspondent les messages Overfull ?
+-----------------------------------------------------
+Lorsque LaTeX n'arrive pas satisfaire tous ses critres de
+beaut, il peut avoir en violer un. Cette entorse est alors
+indique par un message de type :
+ Overfull \hbox (4.02349pt too wide) in paragraph at
+ lines 95-98
+qui prcise le type de dpassement, sa valeur et sa
+localisation.
+
+================================================================
+[2] DOCUMENTATION
+================================================================
+
+# 2.1 # Que puis-je lire sur TeX ?
+----------------------------------
+* "The TeXbook", de D. E. Knuth (Addison Wesley, 1984)
+
+* "Le petit livre de TeX", de R. Seroul, (Interditions, 1989)
+
+* "Introduction to TeX", de N. Schwarz (Addison Wesley, 1989)
+
+* "TeX for the beginner", de W. Snow (Addison Wesley, 1992)
+
+* "TeX for the impatient", de P. Abrahams, K. Berry et K.
+Hargreaves (Addison Wesley, 1990)
+
+* "The advanced TeX book", de D. Salomon (Springer Verlag,
+1995)
+
+* "La matrise de TeX et LaTeX", de T. Lachand-Robert (Masson,
+1995). Ce document peut tre trs utile ceux qui veulent
+programmer/comprendre/adapter des macros/packages TeX. Principalement
+orient vers TeX, quelques rares et courts passages propos
+de LaTeX.
+
+* "A TeX Primer for Scientists", de S. Sawyer et S. Krantz (CRC
+Press,1995)
+
+* "TeX by example: A Beginner's Guide", de A. Borde (Academic
+Press, 1992).
+
+* "TeX: The Program", de D. E. Knuth (Addison Wesley, 1986)
+
+* "TeX by Topic" de V. Eijkhout est complmentaire au TeX book.
+Il est disponible sur
+http://www.cs.utk.edu/~eijkhout/tbt.html.
+
+# 2.2 # Que puis-je lire sur LaTeX2.09 ?
+----------------------------------------
+* "LaTeX, a Document Preparation System", de L. Lamport
+(Addison Wesley, 1re dition)
+
+* "LaTeX reference manual", de L. Lamport (Addison Wesley)
+
+* "LaTeX, Manuel utilisateur simplifi", de C. Simian (CNRS)
+
+* "La matrise de TeX et LaTeX", de T. Lachand-Robert (Masson,
+1995)
+
+# 2.3 # Que puis-je lire sur LaTeX2e ?
+--------------------------------------
+* Le fichier usrguide.tex de la distribution LaTeX dcrit les
+changements entre LaTeX2.09 et LaTeX2e.
+
+* "LaTeX, a Document Preparation System", de L. Lamport
+(Addison Wesley, 1994- 2nde dition)
+
+* "The LaTeX companion", de M. Goossens, F. Mittelbach, et A.
+Samarin (Addison Wesley, 1994). Pour une prsentation plus
+complte, consulter : http://www.awl.com/cseng/
+
+* "A Guide to LaTeX2e, document preparation for beginners and
+advanced users", de H. Kopla & P.W. Daly (Addison Wesley, 1995)
+
+Remarque : trs bien pour qui cherche un guide trs complet. En
+ particulier, il met en permanence l'accent sur ce qui
+ est diffrent/spcifique entre LaTeX2e et LaTeX2.09.
+
+Une nouvelle version existe :
+"A Guide to LaTeX: Third Edition - Document Preparation For
+Beginners And Advanced Users", de H. Kopla & P.W. Daly
+(Addison Wesley, 1999). Pour une prsentation plus complte,
+consulter : http://www.awl.com/cseng/
+
+* "LaTeX guide pratique - version 2e", de C. Rolland, (Addison
+Wesley, 1995)
+
+Une nouvelle version existe :
+"LaTeX par la pratique", de C. Rolland (O'Reilly, 1999)
+Pour une prsentation plus complte,
+consulter : http://www.editions-oreilly.fr/catalogue/latex.html
+
+* "Joli manuel pour LaTeX2e", de B. Bayart. Ce
+manuel est disponible sur ftp://ftp.fdn.org/pub/CTAN/info/JMPL.ps.gz.
+
+* "LaTeX2e, un aperu", de M. Goossens au CERN disponible sur
+http://www.loria.fr/services/tex/.
+
+* "Apprends LaTeX", de M. Baudoin (manuel de l'ENSTA). Cette
+documentation est disponible sur le WEB par ftp sur
+ftp://ftp.agm-ita.ensta.fr/pub/babafou/.
+
+* "Essential LaTeX", de J. Warbrick. Ce document trs
+pdagogique permet de raliser un document LaTeX en quelques
+minutes. Il est disponible sur CTAN (cf. paragraphe 3.1).
+
+* M. Herrb a traduit en franais "The not so short introduction
+to LaTeX2e" de T. Oetiker. La version franaise est disponible
+par ftp sur ftp://ftp.laas.fr/pub/Logiciels/latex/flshort/ ou sur
+http://www.laas.fr/~matthieu/cours/latex2e/. Elle comprend
+quelque complments franais spcifiques.
+
+On y trouve:
+flshort2e.dvi.gz Le fichier DVI
+flshort2e.ps.gz Le fichier PostScript
+flshort2e.tar.gz Les sources LaTeX2e
+
+* "Objectif LaTeX", de V. Gramet et J.P. Regourd (Masson, 1995)
+
+* "The LaTeX Graphics Companion" de M. Goossens, S. Rahtz et F.
+Mittelbach (Addison Wesley, 1997). Pour une prsentation plus
+complte, consulter : http://www.awl.com/cseng/.
+
+* "The LaTeX Web Companion", de M. Goossens, S. Rahtz, E. Gurari
+et R. Moore (Addison Wesley, 1999). Pour une prsentation plus
+complte, consulter : http://www.awl.com/cseng/
+
+* TeX est intgralement document dans le TeX book. Quand on
+connat le TeXbook sur le bout des doigts, on peut lire source2e
+disponible l'adresse :
+http://www-fourier.ujf-grenoble.fr/~bouche/PDFtex/source2e.pdf.
+
+# 2.4 # Que puis-je lire sur AMS-LaTeX ?
+----------------------------------------
+* "Math into LaTeX: An Introduction to LaTeX and AMS-LaTeX" de
+G. Gratzer (Birkhauser, Boston, 1996).
+
+* Il existe galement une documentation "amsldoc.tex"
+disponible sur ftp://ftp.fdn.org/pub/CTAN/latex/packages/amslatex/math/.
+
+# 2.5 # Que puis-je lire sur la typographie ?
+---------------------------------------------
+* "Le dveloppement des caractres", de H. E. Meier, (Syntax
+Press, Cham, Suisse).
+
+* "Pour une smiologie de la typographie", de G. Blanchard,
+(dit par Remy Magermans en Belgique, vendu par "Rencontres de
+Lure", BP 533 71010 Macon cedex).
+Il s'agit de la partie "illustrations" de la thse de G.
+Blanchard avec quand mme un peu de texte... Le texte complet
+n'est disponible qu'en italien: "L'eredita Gutenberg",
+(Gianfranco Altieri Editore). Ouvrage fondamental...
+
+* "Manuel de typographie lmentaire", de Y. Perousseaux,
+(1995).
+
+* "La chose imprime", de Dreyfus et Richaudeau, (Retz, 1985).
+
+* Lexiques des rgles typographiques en usage l'imprimerie
+nationale, ISBN 2-11-081075-0 3me dition novembre 1990.
+
+* Voir galement les sites :
+http://www.csd.uwo.ca/staff/drraymon/typesetting.htm
+http://ksi.cpsc.ucalgary.ca/articles/DigitalJ/DigitalJc.html
+http://www.ucc.ie/info/TeX/papers/aston.html
+http://www.typearts.com/
+http://www.monotype.com/
+http://www.rwsa.com/menu.html
+
+* Il existe galement la lettre "The Newsletter of Digital
+Typography". Elle est disponible gratuitement par e-mail
+imprint@macline.com (mettre IMPRINT comme sujet).
+
+* "The Elements of Typographic Style" de R. Bringhurst.
+
+# 2.6 # O trouver une bibliographie complte ?
+-----------------------------------------------
+http://www.loria.fr/tex/texbib.html propose une bibliographie
+tenue jour.
+
+# 2.7 # Que puis-je lire sur les fontes ?
+-----------------------------------------
+* Il existe une FAQ comp.fonts disponible sur :
+http://www.ora.com/homepages/comp.fonts/FAQ/.
+
+* "Metafont", de Knuth D.E. (Addison Wesley Longman).
+
+* Voir galement la note sur les fontes PostScript sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/psnfss/psnfss2e.tex.
+================================================================
+[3] SITES WEB
+================================================================
+
+# 3.1 # O trouver des infos sur le WEB ?
+-----------------------------------------
+* CTAN ou Comprehensive TeX Archive Network
+Le systme CTAN se propose de rassembler diverses informations
+concernant TeX et son environnement suivant une organisation
+commune. En particulier, tous les sites dits CTAN ou leurs
+miroirs essaient de se synchroniser pour offrir des
+informations cohrentes. En voici quelques uns :
+
++ France :
+par ftp sur \ctan{} ou
+par ftp sur ftp://ftp.loria.fr/pub/ctan/ ou
+par ftp sur ftp://ftp.oleane.net/pub/CTAN/ (pas d'accs
+web. Supporte le "quote site exec" et le tar+gz en ligne)
+sur http://www.loria.fr/services/tex/ ou
+sur http://www.ens.fr/gut/.
+
++ Allemagne :
+par ftp sur ftp://ftp.dante.de/tex-archive/ ou
+par mail mail-server@ftp.dante.de ou
+sur http://www.dante.de/.
+
++ Grande-Bretagne
+par ftp sur ftp://ftp.tex.ac.uk/tex-archive/ ou
+par mail texserver@tex.ac.uk ou
+sur http://www.tex.ac.uk/UKTUG/home.html.
+
++ Pays-Bas :
+sur http://www.ntg.nl/ntg/ntg.html.
+
++ Espagne :
+sur http://gordo.us.es/Actividades/GUTH/.
+
++ tats-Unis :
+par ftp sur ftp://ftp.cdrom.com/pub/tex/ctan/ ou
+sur http://www.cdrom.com/pub/tex/ctan/.
+
+Une liste complte des sites CTAN peut tre trouve sur
+ftp://ftp.fdn.org/pub/CTAN/usergrps/info/usergrps.tex.
+
+ATTENTION (08/96) : Le serveur d'archives (La)TeX aux tats-Unis,
+ ftp.shsu.edu, n'tant plus jour par dfaut de
+ maintenance, il est fortement dconseill dsormais d'y
+ rcuprer des utilitaires (La)TeX. Il reste donc les 2
+ serveurs CTAN << de base >>, l'anglais et l'allemand,
+ ainsi que leurs fidles copies en France dont celle du
+ LORIA-CNRS Nancy : ftp://ftp.loria.fr.
+
+La plupart des sites CTAN offrent une fonctionnalit QUOTE
+SITE INDEX qui permet d'accder plus rapidement l'information
+que l'on recherche sous forme d'expression rgulire. En
+France, le mieux est de consulter :
+http://www.loria.fr/cgi-bin/ctan-index.
+
+Remarque : il existe une liste de diffusion des annonces CTAN :
+ CTAN-Ann@SHSU.edu. Pour s'y abonner, il faut envoyer
+ un mail listserv@SHSU.edu.
+
+* http://www.loria.fr/services/tex/ prsente le (La)TeX Navigator. On
+peut y trouver de nombreux pointeurs (sur des docs dont cette
+FAQ, des personnes, des packages, des outils LaTeX, des sites
+ftp, CTAN, ...) et de nombreuses informations concernant Tex,
+LaTeX, LaTeX2e, LaTeX3, AMS-LaTeX, BibTeX, SliTeX, ....
+
+* ftp://ftp.gutenberg.eu.org/pub/gut/ et
+http://www.gutenberg.eu.org/ proposent
+galement de nombreuses informations dont un certain nombre de
+distributions pour Mac, PC et stations. Ce site prsente
+galement un certain nombre d'archives et de publications dont
+notamment les lettres et les cahiers GUTenberg.
+
+* Le TeX macro index de D. M. Jones disponible par ftp
+anonyme sur ftp://theory.lcs.mit.edu/pub/tex/TeX-index
+recense un certain nombre de macros et styles LaTeX
+actuellement existants.
+
+* Autres sources d'informations (rsums de commandes, guides) :
++ http://www.sd.monash.edu.au/~timm/pub/guides/lshort2e.dvi
+prsente un guide rapide.
++ http://molscat.giss.nasa.gov/LaTeX/ prsente un sommaire des
+commandes LaTeX
++ http://www.tug.org/interest.html donne des pointeurs sur TeX,
+LaTeX et consorts.
++ Sur ftp://ftp.fdn.org/pub/CTAN/info/latex2e-help-texinfo.
+
+* Un catalogue des outils TeX et LaTeX, mis jour rgulirement
+est disponible sur :
+http://www.dit.csiro.au/~gjw/texpkgs.html.
+
+Ce catalogue prsente une liste des packages disponibles avec
+une courte description de chacun. Il est mirror par les sites
+CTAN sur ftp://ftp.fdn.org/pub/CTAN/help/Catalogue/. Une version gzip de ce catalogue
+est disponible sur :
+http://www.cdrom.com/pub/tex/ctan/help/Catalogue/catalogue.html.gz.
+
+Voici quelques exemples de sites :
++ CTAN amricain :
+http://www.cdrom.com/pub/tex/ctan/help/Catalogue/catalogue.html.
++ Noeud CTAN britannique :
+http://www.tex.ac.uk/tex-archive/help/Catalogue/catalogue.html.
++ Allemagne :
+ftp://ftp.dante.de/tex-archive/help/Catalogue/catalogue.html.
+
+* http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/LaTeX_intro.html
+prsente une introduction LaTeX2e et aux mathmatiques.
+
+# 3.2 # O trouver cette FAQ ?
+------------------------------
+* Cette FAQ sera mensuellement poste dans fr.comp.text.tex, dans
+fr.usenet.reponses et dans news.answers. Sa parution sera juste
+mentionne dans comp.text.tex.
+
+* Diverses versions de cette FAQ existent en html ou en
+postscript. Notez cependant que ce ne sont _pas_ les dernires
+versions. Rfrez vous au LaTeX Navigator :
+http://www.loria.fr/services/tex/divers.html et :
+http://www.limsi.fr/Individu/lebourqu/latex/FAQ-LaTeX.fr.txt.
+
+* Des versions html sont galement disponibles, sans tre jour,
+un grand merci leurs auteurs :
++ P. Girard
+http://www.crt.umontreal.ca/~lab_info/latex/faq-francaise/faq.html.
++ F. Torre
+http://www.lri.fr/Francais/Recherche/ia/stuff/FAQ-LaTeX.
++ R. Metrich
+http://www-ensimag.imag.fr/eleves/Renaud.Metrich/Unix/LaTeX.fr.html.
+
+* Elle est disponible sur ftp://ftp.fdn.org/pub/CTAN/help/LaTeX-FAQ-francaise/.
+
+* Elle est galement accessible sur le WEB :
++ http://www.loria.fr/tex/divers.html (LaTeX Navigator)
++ http://www.ams.org/tex/ (American Mathematical Society's TeX
+Resources pages)
++ par ftp sur ftp://ftp.inria.fr/faq/fr.comp.text.tex/
+(ce site possde entre autres un miroir du site rtfm.mit.edu)
++ par ftp sur
+ftp://ftp.univ-lyon1.fr/pub/faq/by-name/fr/faq-latex-francaise/
++ http://diwww.epfl.ch/~jmonzani/FAQ_LaTeX.html site de l'Ecole
+Polytechnique Federale de Lausanne
++ http://www.info.ucl.ac.be/~fp/texfaqfr.html.
+
+* Par ailleurs, elle est incluse dans certaines distributions
+Linux et aussi sur le CD-ROM AsTeX.
+
+# 3.3 # Existe t'il des listes de discussion francophones ?
+-----------------------------------------------------------
+* Il existe la liste gut@ens.fr (de l'association GUTenberg)
+dont les archives sont stockes sur :
+http://www.univ-rennes1.fr/LISTES/gut@ens.fr/arc/maillist.html
+et sur lesquelles on peut faire des recherches par auteurs,
+sujets, etc.
+
++ Pour s'inscrire, envoyer un mail:
+To: listserv@ens.fr
+From: votre_nom_d'utilisateur@votre.site
+Subject:
+
+subscribe gut Votre_Nom Votre_institution
+
++ Pour se dsabonner :
+mailto:listserv@ens.fr
+Subject:
+unsubscribe gut
+
+Voir aussi le site Web de GUTenberg, http://www.gutenberg.eu.org/.
+
+* Il existe galement la liste omega@ens.fr. Cette liste de
+diffusion concerne Omega, une extension de TeX dveloppe par
+John Plaice et Yannis Haralambous. Pour vous abonner, envoyer un
+courrier lectronique listserv@ens.fr, sans sujet ni
+signature, dont le corps du message contient exclusivement la
+ligne : subscribe omega PRENOM NOM
+
+* La liste de diffusion typographie est consacre aux
+problmes de composition, de typographie - franaise ou
+trangre - et de mise en pages, sans exclusive des techniques
+employes : du lettrage la main la composition numrique en
+passant par le plomb, du support papier la page cran, du
+ bon usage du Code typographique jusqu'aux normalisations du
+codage des caractres.
+
+Ses abonns ont en commun l'amour de la chose imprime, y
+compris sous ses formes modernes.
+Pour s'inscrire, envoyez
+ listserv@irisa.fr
+le message suivant :
+ SUBSCRIBE typographie
+
+# 3.4 # O trouver d'autres FAQs LaTeX ?
+----------------------------------------
+* http://www.cogs.susx.ac.uk/cgi-bin/texfaq2html
+* ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/text/tex/
+* sur :
+ftp://ftp.fdn.org/pub/CTAN/usergrps/uktug/faq/
+ftp://ftp.fdn.org/pub/CTAN/usergrps/dante/de-tex-faq/
+ftp://ftp.fdn.org/pub/CTAN/help/comp-fonts-FAQ/
+* Le cahier GUTenberg numro 23
+
+================================================================
+[4] SOURCES TEX ET LATEX
+================================================================
+
+# 4.1 # O trouver les sources pour Unix ?
+------------------------------------------
+* La distribution GUTenberg est disponible par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/. Elle est base sur
+MlTeX (adapt LaTeX2e), TeX, Metafont. Les binaires
+sont disponibles pour :
++ Sun4 sous solaris 2.x et SunOS 4.1.x
++ IBM RS6000 sous AIX 3 et 4
++ Silicon graphics sous irix4, 5 et 6
++ HP7xx sous Hpux9 et 10
++ HP9000 en Hpux 10
++ DECalpha sous OSF/1
++ DECstation 3100 sous Ultrix
++ PC sous Linux
++ PC i86 en Solaris 2
+
+* Diffrentes distributions source Unix de TeX sont disponibles
+sur ftp://ftp.fdn.org/pub/CTAN/systems/unix/.
+
+* La distribution teTeX pour Unix, Linux ou Irix est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/systems/unix/teTeX/distrib/. A l'origine,
+cette distribution a t dveloppe pour Linux. Il
+existe galement un package 'config' qui offre des fichiers de
+configuration de cette distribution disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/systems/unix/teTeX/contrib/.
+
+# 4.2 # O trouver les sources pour VMS ?
+-----------------------------------------
+* TeX pour VMS est disponible sur ftp://ftp.fdn.org/pub/CTAN/systems/vms/ puis Alpha/
+ou VAX/ suivant l'architecture utilise.
+
+* La distribution OpenVMS VAX et AXP de GUTenberg est disponible
+par ftp sur ftp://ftp.gutenberg.eu.org/pub/gut/. Elle
+s'appuie sur TeX et LaTeX2e.
+
+# 4.3 # O trouver les sources pour DOS, OS/2, Windows3.x/95/NT ?
+-----------------------------------------------------------------
+* Une distribution TeX pour PC, incluant LaTeX, BibTeX,
+previewers, et drivers est disponible par ftp anonyme sur
+ftp://vax.eedsp.gatech.edu/pub/TeX/.
+
+* emTeX de E. Mattes, pour PC sous MS-DOS, Windows ou OS/2, est
+disponible par ftp anonyme sur ftp://ftp.fdn.org/pub/CTAN/systems/msdos/emtex.
+Cette distribution inclut LaTeX, METAFONT, BibTeX, TeXcad... Il
+existe galement emtexgi sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/emtex-contrib/emtexgi/ qui est une interface
+Windows pour emTeX. Il existe une liste de discussion emTeX :
+majordomo@physik.tu-berlin.de.
+
+* Une version emTeX francise de M. Lavaud
+(Michel.Lavaud@univ-orleans.fr), distribue par AsTeX (cf.
+question 27.3) est disponible par ftp sur
+ftp://ftp.univ-orleans.fr/astex/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/PC/AsTeX/. L'installation de la nouvelle version 2.2 est
+entirement automatise, ainsi que la configuration des pilotes
+(dviscr, dviwin, dvips), GSview, Gnuplot et les interfaces
+TeXShell, MicroEmacs et MenuTeX. Il y a une fonction
+d'installation / desinstallation slective avec une vingtaine de
+types d'installation diffrents pour installer tout ou partie de
+la distribution, et plusieurs modes d'installation (ajouter,
+craser, mettre jour, dsinstaller, module par module).
+
+Il existe mme une liste de discussion AsTeX :
+astex@univ-orleans.fr. Pour s'inscrire, il faut envoyer le
+message HELP listserv@univ-orleans.fr.
+
+* 4AllTeX, trs complet, ncessite 4DOS (un remplacement de
+command.com) pour l'utilisation de ses .btm (.bat amliors).
+4AllTeX inclut une interface (TeXelmExtel) sous windows (TeX,
+LaTeX2e, BibTeX, makeindex, ...) Vous trouverez l'ensemble
+sur ftp://ftp.fdn.org/pub/CTAN/systems/.
+
+* gTeX sous MS-DOS et windows est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/gtex/. Son avantage est de fonctionner en 32bits
+ la fois sous Windows (3.x, 95 et NT) et sous Dos via un
+extender fourni. Cette distribution comprend micro-emacs,
+dviwin, etc.
+
+* Win32 MiKTeX de C. Schenk, pour windows 95 et NT, est
+une version compile de LaTeX2e (il supporte mme les longs
+noms de fichiers). MiKTeX est disponible par ftp sur
+ftp://ftp.fdn.org/pub/CTAN/systems/win32/miktex/.
+
+* DOS-GUT (distribution francise par GUTenberg) est disponible
+par ftp sur ftp://ftp.gutenberg.eu.org/pub/gut/PC/DOS-GUT/.
+Cette distribution est base sur gtex et web2c. Elle comprend
+l'diteur TeXshell, TeX, TeX-XeT, plain, LaTeX, babel,
+ArabicTeX, dviscr, dvips, metafont et GhostScript.
+
+Remarque : la distribution DOS-GUT n'est plus activement
+ dveloppe. Elle a t remplace par WIN-GUT.
+
+* WIN-GUT est une version intgre pour windows 3.1, 95 et NT
+par P. Legrand. Elle permet la composition de textes franais
+(soit avec babel, soit avec french), amricain et arabe
+(ArabicTeX). Elle comprend DVIWIN, dvips, micro-emacs
+
+* Il existe galement Y&Y TeX System pour Windows. Pour plus
+d'informations, vous pouvez consulter le site
+http://www.YandY.com/.
+
+* PCTeX pour DOS, Windows3.1 et Windows95/NT, qui est moins
+puissant que le prcdent mais qui est trs simple mettre en
+place. Pour plus de dtails, consulter http://www.pctex.com/.
+
+* EMTEXGI de A. Cottrell est une nouvelle distribution
+disponible
+http://www.wfu.edu/Academic-departments/Economics/ftp/emtexgi.html.
+
+* F. Popineau a port la version Unix de TeX (web2c 7, utilis
+par teTeX) sous Win32. Le but final tant de crer une
+distribution windows la plus proche possible de teTeX. Cette
+distribution s'appelle fpTeX.
+Pour plus de dtails, consultez: http://www.ese-metz.fr/~popineau/fptex/.
+
+Cette distribution est native Win32, un peu plus rapide que
+MikTeX, moins simple installer (encore que...), dispose d'un
+magnifique pr-visualiseur, windvi, et comporte e-TeX, PDFTeX,
+makeindex et latex2html (en bta).
+
+# 4.4 # O trouver les sources pour MacOS ?
+-------------------------------------------
+
+* La "Macintosh TeX/LaTeX Software Page" :
+http://www.esm.psu.edu/mac-tex/ est la page de rfrence pour
+les utilisateurs de TeX sous MacOS: les versions les plus
+rcentes de CMacTeX, OzTex, Direct-TeX Pro et de nombreux
+utilitaires (BibTex, MakeIndex, Excalibur (un correcteur
+orthographique pour LaTeX), Alpha...) sont disponibles sur cette
+page, qui est mise jour trs rgulirement.
+
+* Texture 2.1 est une version commerciale de TeX, dveloppe par
+Blue Sky Research. Pour plus d'informations, vous pouvez consulter
+le site http://www.bluesky.com/.
+
+* CMacTeX 3.3 shareware de de T. Kiffe, comprend TeX, Omega,
+pdftex, e-TeX, BibTeX, makeindex, metafont, metapost, deux
+previewer dvi, dvips, ps2pdf, un driver PostScript et quelques
+utilitaires de gestion de fontes. CMacTeX est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/mac/cmactex/.
+Pour plus de renseignements, consulter :
+http://www.kiffe.com/cmactex.html.
+
+* OzTex 4.0 de A. Trevorrow, est disponible par ftp sur
+ftp://ftp.fdn.org/pub/CTAN/systems/mac/oztex/.
+Cette distribution shareware ncessite 3,5 Mo de mmoire vive.
+Elle intgre un previewer dvi, BibTeX, makeindex, metafont,
+metapost, dvips ainsi que TtH (TeX to html, d'Hutchinson). Une
+version shareware de pdfTeX pour OzTeX a t dveloppe par
+T. Kiffe. PdfTeX pour OxTeX est disponible l'adresse
+http://www.kiffe.com/pdftexoz.html.
+
+* Direct-TeX Pro 2.1.2 de W. Ricken, est une distribution
+shareware qui possde un environnement intgr et multi-fentre
+trs pratique, modulable de surcrot. Elle intgre TeX--XeT
+3.14159 ainsi que Metafont 2.718, et tous les utilitaires qui
+permettent de passer en une passe d'un source (La)TeX au .ps
+final. Il y a mme un diteur intgr, quoique petit.
+Direct-TeX est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/mac/directtex/.
+Elle ncessite le systme 7 et 8Mo de mmoire vive.
+
+* Euro-Oztex de Y. Haralambous, est la distribution
+propose par GUTenberg. Cette version francise appelle une
+contribution shareware Trevorrow et Ricken. Elle est
+disponible par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/MAC/Euro-OzTeX/.
+
+Remarque : Euro-Oztex est une vieille version de la distribution
+ de GUTenberg. Elle utilisait OzTeX 1.7. Elle a t
+ remplace rcemment par Mac-GUT, qui elle utilise
+ CMacTeX.
+
+* Mac-GUT, base sur CMacTeX, est la distribution shareware
+propose par GUTenberg (donc francise). Elle n'est disponible
+ l'heure actuelle que sur le cd-rom TeX-Live distribu par
+GUTenberg ses adhrents. Pour plus de dtails, consulter :
+http://www.tug.org/texlive.html.
+
+# 4.5 # O trouver d'autres sources ?
+-------------------------------------
+* Atari
+TeX pour Atari ST est disponible par ftp sur
+ftp://atari.archive.umich.edu/atari/tex/ ou sur
+ftp://ifi.informatik.uni-stuttgart.de/pub/atari.st/tex/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/systems/atari/. Pour tous renseignements contacter
+atari@atari.archive.umich.edu par un mail "help".
+
+* Amiga
++ PasTeX, implmentation de TeX 3.1 et METAFONT 2.7 sont
+disponibles par ftp anonyme sur ftp://merlin.etsu.edu/ab20/AMIGA/
+ou sur ftp://forwiss.uni-passau.de/pub/amiga/tex/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/systems/amiga/.
+
++ On peut trouver galement PasTeX 1.4 sur les miroirs FTP
+aminet (sunsite.cnam.fr. ftp.grolier.fr, ftp.netnet.net, ...)
+dans le rpertoire /pub/aminet/text/tex/. PasTeX 1.4 est le
+portage de LaTeX2e. La distribution comprend galement dvips.
+
++ XFig est disponible dans /pub/aminet/gfx/edit/.
+
++ Ghostscript est disponible dans /pub/aminet/gfx/show/.
+
++ Une version LaTeX2e a galement t dveloppe l'ESIEE
+http://www.esiee.fr/~tex/Install/Amiga/index.html.
+
+* Tandy 6000
+Pour tous renseignements contacter Ken Yap
+(ken@syd.dit.csiro.au).
+
+* TOPS-20
+Une distribution TeX sur TOPS-20 est disponible par ftp
+anonyme sur ftp://ftp.math.utah.edu/pub/tex/pub/web/.
+
+================================================================
+[5] DITER LATEX
+================================================================
+
+Les diteurs ci-dessous sont classs par ordre alphabtique sur
+le nom, afin d'viter toute dispute sur la place de l'un ou
+l'autre.
+
+* Alpha est un diteur Macintosh shareware assez proche d'emacs.
+Il est disponible entre autres par ftp sur
+ftp://alpha.olm.net/pub/.
+
+Cet diteur est hautement configurable grce un langage de
+programmation intgr, Tcl. Il possde entre autres un mode
+LaTeX trs convivial. Alpha permet aussi une interaction avec le
+compilateur (Texture (commercial), CMACTEX, OzTex ou Direct-Tex)
+en lanant la compilation d'une combinaison de touches. La
+dernire version d'Alpha est la 7.2. Elle comprend la version 3.2
+des macros freeware Alpha LaTeX de T. Scavo.
+
+Pour plus de renseignements, voir http://alpha.olm.net/.
+
+* Cicero est un traitement de texte sous X11R6 et Motif2.0. Le
+package comprend des fontes X postscript, ghostscript, TeX
+(dvips) et Cicero. Pour plus de renseignements, consulter :
+http://zeus.informatik.uni-frankfurt.de/~weis/cicero.html.
+
+* Eddi4TeX, sous MS-DOS ou OS/2, est un diteur spcifiquement
+conu pour TeX, il offre la couleur, vrifie la syntaxe. Il
+est disponible sur ftp://ftp.fdn.org/pub/CTAN/systems/msdos/e4t/ ou dans
+ftp://ftp.fdn.org/pub/CTAN/systems/OS2/epmtex/.
+
+* (X-)Emacs est un diteur sous Unix qui offre en standard un
+mode d'dition, un peu fruste mais nanmoins pratique,
+facilitant la composition de documents (La)TeX. Une extension
+emacs, AUC-TeX (disponible sur ftp://ftp.fdn.org/pub/CTAN/support/auctex/ ou sur
+http://sunsite.auc.dk/auctex/), fournit de nombreuses facilits
+supplmentaires (indentation automatique, messages d'erreur en
+anglais comprhensible, gestion des documents multi-fichiers,
+etc.)
+
+Emacs reconnat automatiquement certaines extensions
+(tex,sty...) dans un nom de fichier, et active le mode en
+question automatiquement. Si votre fichier n'est pas reconnu
+comme un document (La)TeX, vous pouvez spcifier sur la premire
+ligne de votre fichier : % -*-latex-*-
+
+Les packages 'font-lock' et 'hilit19' ('hilit319' pour Xemacs)
+ou plus rcent 'font-latex' (bas sur font-lock), permettant de
+choisir les couleurs et les polices mettant en vidence la
+syntaxe d'un fichier, sont utilisables avec les modes (La)TeX.
+Pour plus de dtails, voir: ftp://ftp.fdn.org/pub/CTAN/support/ultratex/.
+
+Le package (standard) 'imenu' donne accs un menu listant les
+en-ttes de section du document, et permet de retrouver
+celles-ci facilement dans un grand document. Une extension ce
+mcanisme permet de mieux visualiser la structure du document,
+en indentant les sous-sections.
+
+* Funtek, de V. Vidal, sous X-Windows system et Motif, est un
+diteur texte orient LaTeX; il traite le source LaTeX page
+page, permet un accs aux symboles spciaux, et une construction
+de tableaux automatique. La version actuelle est une bta.
+
+* GNU emacs et AUCTeX peuvent galement tre utiliss sous
+MS-DOS ou OS/2.
+
+* JED est un clone multi-plateformes proche d'emacs. JED est en
+fait un emacs allg qui offre des facilits dans l'dition de
+fichier (La)TeX. Il tourne sous Unix/VMS/Dos/Win. Il est
+disponible http://space.mit.edu/~davis/.
+
+* LyX est un traitement de texte sous X11 qui offre une sortie
+LaTeX2e. Il est presque WYSIWYG. LyX prsente les avantages
+d'tre petit, rapide et gratuit. LyX est encore en dveloppement.
+Une version NON dfinitive est disponible http://www.lyx.org/ ou
+par ftp sur ftp://ftp.lip6.fr/pub/linux/sunsite/X11/xapps/editors/ ou
+par ftp sur ftp://ftp.lyx.org/pub/lyx/ ou sur le web par
+http://www.lehigh.edu/~dlj0/LyriX.html.
+Il existe galement une liste de discussion : lyx@lyx.org.
+
+Parmi les fonctionnalits, on trouve:
+- diteur d'quations,
+- diteur de tables,
+- inclusion d'images au format EPS,
+- correction d'orthographe,
+- etc.
+
+Les dernires docs sont disponibles par ftp sur
+ftp://ftp.lyx.org/pub/lyx/doc/.
+
+* MicroEmacs (inclu dans la distribution DOS-GUT), sous windows,
+permet d'diter et de grer des documents TeX.
+
+* NEdit est un diteur entirement conu sous X ds le dbut.
+Il offre des "look and feel" semblables aux diteurs qu'on
+trouve sur Windows et Mac, par ex, les touches de raccourcis
+standards sont Ctrl+X pour couper, Ctrl+C pour copier, Ctrl+V
+pour coller. Ainsi, les nouveaux utilisateurs immigrs des
+autres systme d'exploitation n'auront pas trop de mal
+radapter facilement NEdit. C'est un diteur trs
+configurable, par ex la police des caractres, les couleurs
+(enfin, parfois il faut tre un peu bidouilleur aussi :) ).
+C'est un diteur usage gnral. Il n'est pas seulement
+utile pour LaTeX.
+
+L'origine de cette discussion est de trouver un remplaant
+de Kedit pour Dos. Je suppose que ce programme a pas mal de
+fonctions qu'on ne trouve pas ailleurs, ni sous NEdit. Mais il
+est possible de programmer la plupart (si ce n'est pas tout) de
+ces fonctions sous NEdit l'aide de macro.
+
+(Ce message, de Seak Teng-Fong, seak.teng-fong@iname.com, a t
+abrg, pour le message complet, rfrez vous Message-ID:
+<3881E519.437B2409@iname.com>).
+
+Pour plus de dtails sur NEdit: http://www.nedit.org.
+NEdit est sous licence GPL.
+
+* Scientific Word pour windows est un diteur qui permet presque
+de visualiser un document LaTeX en WYSIWYG (What You See Is What
+You Get). Il facilite l'dition d'un document LaTeX en
+permettant une insertion aise des symboles, l'dition de
+tableaux, ... par le "mulot" ou par raccourcis clavier. Pour
+l'utiliser pleinement, il vaut mieux connatre LaTeX.
+
+Remarque : ce produit est commercial et cher.
+
+* STEAD "Sympathetic Tk-based Editor for Average Dummies"
+est un diteur de texte convivial pour Unix (ressemble
+ Alpha sur mac). Il est simple d'utilisation, contextuel et
+configurable.
+Recherche/remplacement pouvant utiliser les expressions rgulires -
+undo/redo multiniveau - colorisation - transformation possible de la
+slection (y compris rectangulaire) par une commande Unix - ...
+
+La particularit de cet diteur est qu'il est entirement interprt !
+En effet, il est crit en langage TCL et TK.
+Necessite l'ancienne version wish3.6 (sources et binaire fournis).
+
+Disponible sur : http://www.ensta.fr/~diam/stead/
+Contact: Maurice DIAMANTINI <diam@ensta.fr>
+
+* TeXnicCenter, crit par Sven Wiegand, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/win32/TeXnicCenter/. C'est un environnement
+de dveloppement intgr (IDE en anglais) LaTeX pour Windows
+distribu sous liscence GPL. L'interface est trs proche de celle
+que l'on peut trouver dans des outils du style de MS Visual Studio.
+Bien qu'encore l'tat de bta, il offre la coloration des mots cls,
+une gestion aise de larges projets, une vue structure des fichiers,
+des sections du document, des flottants et plein d'autres fonctionnalits
+fort intressantes. Le correcteur orthographique est prvu pour la
+prochaine bta. Pour plus d'infos, vous pouvez consulter sa page web :
+http://www.toolscenter.org/texniccenter/index.html.
+
+* TeXShell, crit par J. Schlegelmilch, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/texshell/ts271.zip. C'est un diteur Windows
+sous dos qui offre une coloration des mots cls LaTeX, une aide
+en ligne et d'autres petites fonctionnalits telles que les
+compilations associes des boutons. La distribution DOS-GUT
+utilise TeXshell et offre un MicroEmacs francis.
+
+Il existe galement TeXShell pour X Window system (Tcl/Tk)
+disponible par ftp sur
+ftp://sunsite.unc.edu/pub/Linux/apps/tex/.
+
+* ViM, dvelopp par Bram Moolenaar, dispose dans sa dernire
+version de la coloration syntaxique, l'instar d'emacs; noter
+cependant la lgret de ViM par rapport l'usine gaz
+GNUienne. Vous trouverez plus d'infos sur ViM sur
+http://www.vim.org/ ou par ftp sur ftp://ftp.vim.org/pub/vim/
+(galement reflt par ftp.lip6.fr).
+
+* WINEDT95,logiciel Shareware pour Windows 95, est un diteur
+avec menu TeX/LaTeX qui permet de reprer les commandes LaTeX et
+de compter les dlimiteurs. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/winedt/. Il est pourvu d'un correcteur
+orthographique.
+
+* wintex95 disponible sur ftp://ftp.fdn.org/pub/CTAN/systems/win32/wtex95/ est
+un diteur flexible offrant un coloriage automatique de la
+syntaxe LaTeX. Il offre galement une compltion automatique,
+et des palettes de symboles, un diteur de tableaux, des
+touches de raccourci, le lancement de programmes externes, etc.
+C'est un shareware.
+
+* Xcoral, diteur sous Unix offre des fonctionnalits de mme
+type que emacs mais non interactives. Il est disponible par ftp
+sur ftp://ftp.inria.fr/X/contrib-R5/clients/ ou sur
+ftp://ftp.x.org/contrib/.
+
+Xcoral est un diteur multi-fentres pour X Window System,
+offrant un certain nombre de facilits notamment pour crire
+des programmes perl, ada, fortran, C, C++, java ainsi que des
+documents LaTex ou HTML.
+
+Cet diteur comprend un interprteur Ansi C 'built-in' qui
+permet aux utilisateurs d'tendre ses fonctionnalits
+facilement. Un manuel d'aide complet index est disponible
+on-line.
+
+* X-Window Shell pour TeX (OpenLook ou Xaw/Xaw3d) disponible sur
+http://www.tm.bi.ruhr-uni-bochum.de/personal/marc/xtexshell.html.
+
+* xtem: une interface graphique offrant des fonctionnalits
+TeX/LaTeX disponible sur
+http://ftp.lrw.uni-bremen.de/xtem/xtem_texmenu.html.
+
+* D'autres diteurs sous dos, Mac et windows95 sont prsents
+dans http://www.jumbo.com/.
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part2 b/help/LaTeX-FAQ-francaise/part2
new file mode 100644
index 0000000000..6cec50fa9f
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part2
@@ -0,0 +1,2956 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!howland.erols.net!dispose.news.demon.net!demon!grolier!fr.usenet-edu.net!usenet-edu.net!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:17 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - partie 6
+Message-ID: <faq-fctt-p220010608133117@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p220010501143416@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 2947
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23525 fr.usenet.reponses:20391
+
+Archive-name: fr/faq-latex-francaise/part2
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+================================================================
+[6] GESTION DE LA MISE EN PAGE
+================================================================
+
+# 6.1 # Comment modifier l'interligne d'un document ?
+-----------------------------------------------------
+* Pour modifier l'espace interligne d'un document on peut
+utiliser la commande \linespread (solution non recommande).
+Par exemple, \linespread{1.6} permet de doubler l'intervalle
+par dfaut.
+
+* \renewcommand{\baselinestretch}{1.2} plac dans le
+prambule permet d'obtenir le mme rsultat pour tout le
+document.
+
+* Il existe galement les packages 'doublespace' (pour
+LaTeX2.09) et 'setspace' (pour LaTeX2e) disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex2.09/contrib/misc/ pour l'un et
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ ou
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/setspace/ pour l'autre.
+setspace.sty dfinit les environnements singlespace,
+onehalfspace et doublespace. L'utilisation de ces styles est
+recommande parce que plus robuste (gestion des tableaux, des
+notes de bas de page, ...).
+
+* Pour rduire l'interligne d'un paragraphe ( celui de small
+par exemple) sans modifier la taille de la fonte on peut
+utiliser \small{\normalsize texte interligne rduit}\par ou
+encore {\advance\baselineskip -1pt le texte \par}.
+
+* Localement, on peut galement utiliser la commande
+\baselineskip de la manire suivante :
+
+Exemple :
+{\setlength{\baselineskip}{1.2\baselineskip}
+Texte affect
+\par} %%% <= terminer le paragraphe
+%%%% fin exemple %%%%
+
+# 6.2 # Comment grer un document recto-verso ?
+-----------------------------------------------
+* LaTeX2e prvoit directement les options de classe twoside et
+openright.
+
+Exemple :
+\documentclass[twoside,openright]{report}
+%%%% fin exemple %%%%
+
+* En LaTeX 2.09 il faut passer twoside comme option de la
+commande documentstyle. Ensuite, pour forcer les enttes de
+chapitre commencer sur une page impaire, il faut inclure la
+commande \cleardoublepage avant chaque dbut de chapitre.
+
+Exemple :
+\documentstyle[twoside]{report}
+
+\begin{document}
+\cleardoublepage
+\chapter{Introduction.}
+ Texte.
+
+\cleardoublepage
+\chapter{Thse.}
+ Texte.
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Il existe galement la macro suivante qui redfinit la
+commande \cleardoublepage pour que les pages insres soient
+vides (i.e. sans entte ni bas de page).
+%%%% debut macro %%%%
+% whitecdp (formerly schulzrinne.sty) --provide for blank pages
+% between chapters
+% This redefinition of the \cleardoublepage command provides
+% for a special pagestyle for the "extra" pages which are generated
+% to ensure that the chapter opener is on a recto page.
+% The pagestyle is "chapterverso"; for many publishers, this should be
+% identical to "empty", so that's the default.
+\def\cleardoublepage{\clearpage
+ \if@twoside
+ \ifodd\c@page\else
+ \null\thispagestyle{chapterverso}\newpage
+ \if@twocolumn\null\newpage\fi
+ \fi
+ \fi
+ }%
+\def\ps@chapterverso{\ps@empty}%
+%%%% fin macro %%%%
+
+# 6.3 # Comment modifier le style des titres ?
+----------------------------------------------
+* Les dfinitions de \section, \sub(sub)section, etc, se
+trouvent dans les fichiers .cls (report.cls, article.cls,
+book.cls).
+
+ATTENTION : Il est vivement conseill de ne pas modifier
+ directement ces classes mais de redfinir
+ un fichier.sty avec les nouvelles commandes ou
+ d'utiliser \makeatletter et \makeatother.
+
+Exemple :
+La syntaxe de dfinition d'une nouvelle section est :
+\renewcommand\section{\@startsection {section}{1}{\z@}%
+ {-3.5ex \@plus -1ex \@minus -.2ex}%
+ {2.3ex \@plus.2ex}%
+ {\reset@font\Large\bfseries}}
+
+Explication :
++ La commande \@startsection permet de grer : la table des
+ matires, la numrotation des titres, les rfrences,
+ les titres des sections dans l'en-tte, etc...
++ {section} indique qu'il s'agit d'une section
++ {1} indique son niveau dans la table des matires
++ {\z@} indique son niveau d'indentation (zro)
++ {-3.5ex \@plus -1ex \@minus -.2ex} dfinit l'espace qui sera
+ ajout au dessus du titre
++ {2.3ex \@plus.2ex} dfinit l'espace qui sera ajout en dessous
+ du titre. Si ce nombre est ngatif alors il s'agit d'un
+ espacement horizontal, pour avoir des titres "en ligne",
+ comme a :
+ Titre de ma section. Nous allons parler... bla,
+ bla, bla...
++ \@plus et \@minus permettent de jouer sur l'lasticit de ces
+ espaces
++ {\reset@font\Large\bfseries} sont les commandes de mises en
+ forme du titre.
+%%%% fin exemple %%%%
+
+* Pour augmenter l'espace avant une section il suffit, par
+exemple, d'crire, dans le prambule du document :
+
+%%%% debut macro %%%%
+\makeatletter
+\renewcommand\section{\@startsection{section}{1}{\z@}%
+ {2cm \@plus -1ex \@minus -.2ex}%
+ {2.3ex \@plus.2ex}%
+ {\reset@font\Large\bfseries}}
+\makeatother
+%%%% fin macro %%%%
+
+* Le package 'sfheaders' de M. Loreti, ci dessous met les titres
+dans une fonte sans serif quelle que soit la classe de
+document utilise. Pour l'utiliser, il suffit de sauvegarder les
+macros suivantes dans un fichier SFheaders.sty et d'appeler
+\usepackage{SFheaders}.
+
+%%%% debut macro %%%%
+% Package: SFheaders.sty
+% Sans-Serif headers; modified from {book|report|article}.cls
+% defaults.
+% Last modified: MLO 1997-05-06
+%
+% Author: Maurizio Loreti, aka MLO or (HAM) I3NOO
+% Work: University of Padova - Department of Physics
+% Via F. Marzolo, 8 - 35131 PADOVA - Italy
+% EMail: loreti@padova.infn.it
+% WWW: http://wwwcdf.pd.infn.it/~loreti/mlo.html
+
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{sfheaders}[1997/05/06 Sans-Serif headers]
+
+\@ifclassloaded{article}{
+% Here if \documentclass{article}
+ \def\@part[#1]#2{%
+ \ifnum \c@secnumdepth >\m@ne
+ \refstepcounter{part}%
+ \addcontentsline{toc}{part}{\thepart\hspace{1em}#1}%
+ \else
+ \addcontentsline{toc}{part}{#1}%
+ \fi
+ {\parindent \z@ \raggedright
+ \interlinepenalty \@M
+ \normalfont
+ \ifnum \c@secnumdepth >\m@ne
+ \Large \sffamily \bfseries \partname~\thepart
+ \par\nobreak
+ \fi
+ \huge \sffamily \bfseries #2%
+ \markboth{}{}\par}%
+ \nobreak
+ \vskip 3ex
+ \@afterheading}
+ \def\@spart#1{%
+ {\parindent \z@ \raggedright
+ \interlinepenalty \@M
+ \normalfont
+ \huge \sffamily \bfseries #1\par}%
+ \nobreak
+ \vskip 3ex
+ \@afterheading}}
+{\@ifclassloaded{book}{
+% Here if \documentclass{book}
+ \def\@part[#1]#2{%
+ \ifnum \c@secnumdepth >-2\relax
+ \refstepcounter{part}%
+ \addcontentsline{toc}{part}{\thepart\hspace{1em}#1}%
+ \else
+ \addcontentsline{toc}{part}{#1}%
+ \fi
+ \markboth{}{}%
+ {\centering
+ \interlinepenalty \@M
+ \normalfont
+ \ifnum \c@secnumdepth >-2\relax
+ \huge \sffamily \bfseries \partname~\thepart
+ \par
+ \vskip 20\p@
+ \fi
+ \Huge \sffamily \bfseries #2\par}%
+ \@endpart}
+
+ \def\@spart#1{%
+ {\centering
+ \interlinepenalty \@M
+ \normalfont
+ \Huge \sffamily \bfseries #1\par}%
+ \@endpart}
+
+ \def\@makechapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright \normalfont
+ \ifnum \c@secnumdepth >\m@ne
+ \if@mainmatter
+ \huge \sffamily \bfseries \@chapapp\space \thechapter
+ \par\nobreak
+ \vskip 20\p@
+ \fi
+ \fi
+ \interlinepenalty\@M
+ \Huge \sffamily\ bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+
+ \def\@makeschapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright
+ \normalfont
+ \interlinepenalty\@M
+ \Huge \sffamily \bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+}{
+% Here if none of the above (\documentclass{report} ?)
+ \def\@part[#1]#2{%
+ \ifnum \c@secnumdepth >-2\relax
+ \refstepcounter{part}%
+ \addcontentsline{toc}{part}{\thepart\hspace{1em}#1}%
+ \else
+ \addcontentsline{toc}{part}{#1}%
+ \fi
+ \markboth{}{}%
+ {\centering
+ \interlinepenalty \@M
+ \normalfont
+ \ifnum \c@secnumdepth >-2\relax
+ \huge \sffamily \bfseries \partname~\thepart
+ \par
+ \vskip 20\p@
+ \fi
+ \Huge \sffamily \bfseries #2\par}%
+ \@endpart}
+
+ \def\@spart#1{%
+ {\centering
+ \interlinepenalty \@M
+ \normalfont
+ \Huge \sffamily \bfseries #1\par}%
+ \@endpart}
+
+ \def\@makechapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright \normalfont
+ \ifnum \c@secnumdepth >\m@ne
+ \huge \sffamily \bfseries \@chapapp\space \thechapter
+ \par\nobreak
+ \vskip 20\p@
+ \fi
+ \interlinepenalty\@M
+ \Huge \sffamily \bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+
+ \def\@makeschapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright
+ \normalfont
+ \interlinepenalty\@M
+ \Huge \sffamily \bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+}}
+
+\renewcommand{\section}{\@startsection {section}{1}{\z@}%
+ {-3.5ex \@plus -1ex \@minus -.2ex}%
+ {2.3ex \@plus.2ex}%
+ {\normalfont\Large\sffamily\bfseries}}
+
+\renewcommand{\subsection}{\@startsection{subsection}{2}{\z@}%
+ {-3.25ex\@plus -1ex \@minus -.2ex}%
+ {1.5ex \@plus .2ex}%
+ {\normalfont\large\sffamily\bfseries}}
+
+\renewcommand{\subsubsection}{\@startsection{subsubsection}{3}%
+ {\z@}%
+ {-3.25ex\@plus -1ex \@minus -.2ex}%
+ {1.5ex \@plus .2ex}%
+ {\normalfont\normalsize\sffamily\bfseries}}
+
+\renewcommand{\paragraph}{\@startsection{paragraph}{4}{\z@}%
+ {3.25ex \@plus1ex \@minus.2ex}%
+ {-1em}%
+ {normalfont\normalsize\sffamily\bfseries}}
+
+\renewcommand{\subparagraph}{\@startsection{subparagraph}{5}%
+ {\parindent}%
+ {3.25ex \@plus1ex \@minus .2ex}%
+ {-1em}%
+ {\normalfont\normalsize\sffamily\bfseries}}
+\endinput
+
+%%
+%% End of `SFheaders.sty'.
+%%%% fin macro %%%%
+
+* Le package 'fncychap' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fncychap/ propose un
+ensemble d'enttes de chapitre prdfinies.
+
+# 6.4 # Comment obtenir un document multicolonnes ?
+---------------------------------------------------
+* L'option standard twocolumn permet de prsenter un texte sur
+deux colonnes verticales.
+
+Exemple :
+\documentclass[twocolumn]{article}
+\usepackage{french}
+
+\begin{document}
+
+Voici un texte sur deux colonnes que \LaTeX n'quilibre pas
+par lui-mme (il remplit les colonnes les unes aprs les
+autres). L'espace entre les colonnes peut tre modifi comme
+indiqu plus loin. Une ligne de sparation des colonnes peut
+galement tre insre.
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Pour agir localement, on peut utiliser les commandes :
+\twocolumn[texte sur une colonne]{texte sur deux colonnes}
+puis \onecolumn{Texte sur une colonne} ou plus gnralement
+\twocolumn et \onecolumn.
+
+Pour une meilleure lisibilit du source, on peut galement
+utiliser les environnements correspondants.
+
+Exemple :
+\documentclass{article}
+\usepackage{french}
+
+\begin{document}
+
+Dans la classe article, le texte est, par dfaut, mis en page
+sur une seule colonne. Il est toutefois possible de passer
+temporairement sur deux colonnes.
+
+\twocolumn[Un titre sur une colonne, un peu long pour le
+prouver.]{Et voici enfin un texte sur deux colonnes~; comme
+promis~! Encore une fois, \LaTeX n'quilibre pas le
+remplissage des deux colonnes si bien qu'il est oblig pour
+chaque changement de colonnage de changer de page.}
+
+\onecolumn
+Ceci permet de repasser sur une colonne pour la suite du
+document.
+
+\begin{twocolumn}
+ Encore quelques mots sur deux colonnes. Mme si le texte est
+ trop court pour voir apparatre la deuxime colonne.
+\end{twocolumn}
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'multicol', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/, dfinit l'environnement
+multicols qui permet de redfinir localement le nombre de
+colonnes dsires (10 maximum). Lorsqu'une page n'est pas
+complte, le texte apparat rparti sur toutes les colonnes.
+Ainsi chaque changement de colonnage n'entrane plus un
+changement de page.
+
+Exemple :
+\documentclass{article}
+\usepackage{multicol}
+\usepackage{french}
+\setlength{\columnseprule}{0.5pt}
+\begin{document}
+
+\begin{multicols}{3}[Titre sur une seule colonne.]
+ 3~colonnes quilibres, 3~colonnes quilibres, 3~colonnes
+ quilibres, 3~colonnes quilibres
+\end{multicols}
+
+\begin{multicols}{2}[\section{Titre numrot.}]
+ blabla sur deux colonnes, c'est plus srieux. C'est le
+ style qui est gnralement utilis pour crire des
+ articles.
+\end{multicols}
+\end{document}
+%%%% fin exemple %%%%
+
+Pour ajouter un titre numrot qui apparaisse sur toute la
+largeur de la page, il faut utiliser l'option [\section{Titre.}]
+juste aprs \begin{multicols}{nb-col}.
+
+Remarques :
++ Pour qu'une ligne de sparation apparaisse entre les
+colonnes, il faut utiliser : \setlength{\columnseprule}{1pt}.
+
++ Pour redfinir la largeur de l'espace inter-colonnes, il faut
+utiliser \setlength{\columnsep}{30pt}.
+
+# 6.5 # Comment composer une brochure ?
+---------------------------------------
+* Pour redfinir un format de page, (par exemple un A4 pli en
+trois), il faut utiliser la commande \setlength. Il suffit de
+savoir quelles sont les longueurs prciser, le meilleur moyen
+pour ce faire est de les visualiser avec la commande \layout
+(dfinie par le package 'layout' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/).
+
+%%%% debut macro %%%%
+% (Th. Bouche)
+\ProvidesPackage{a6size}
+% rien a voir avec la taille : ajustement du \baselineskip
+\renewcommand\normalsize{%
+ \@setfontsize\normalsize\@xiipt{13.5}%
+ \abovedisplayskip 12\p@ \@plus3\p@ \@minus7\p@
+ \abovedisplayshortskip \z@ \@plus3\p@
+ \belowdisplayshortskip 6.5\p@ \@plus3.5\p@ \@minus3\p@
+ \belowdisplayskip \abovedisplayskip
+ \let\@listi\@listI}
+\renewcommand\small{%
+ \@setfontsize\small\@xipt{12.4}%
+ \abovedisplayskip 11\p@ \@plus3\p@ \@minus6\p@
+ \abovedisplayshortskip \z@ \@plus3\p@
+ \belowdisplayshortskip 6.5\p@ \@plus3.5\p@ \@minus3\p@
+ \def\@listi{\leftmargin\leftmargini
+ \topsep 9\p@ \@plus3\p@ \@minus5\p@
+ \parsep 4.5\p@ \@plus2\p@ \@minus\p@
+ \itemsep \parsep}%
+ \belowdisplayskip \abovedisplayskip}
+\normalsize
+
+\setlength\paperheight {148mm}%
+\setlength\paperwidth {105mm}%
+%\voffset-1cm
+%\hoffset-2cm
+\setlength{\topmargin}{-1.3cm}%
+\setlength{\oddsidemargin}{-.5cm}%
+\setlength{\evensidemargin}{-1cm}%
+\setlength{\marginparsep}{0\p@}%
+\setlength{\headsep}{0\p@}%
+% calcule la hauteur du texte en fonction du \baselineskip, pour
+% que les lignes soient places au mme niveau sur toutes les pages
+\setlength{\textheight}{\topskip}
+\addtolength{\textheight}{22\baselineskip}%
+\setlength{\textwidth}{7cm}%
+\setlength{\footskip}{23\p@}% (originellement : 48)
+%\setlength{\baselineskip}{13\p@}%
+%\setlength{\marginparwidth}{0\p@} %
+%\addtolength{\baselineskip}{.2\baselineskip}%
+\setlength{\parindent}{0\p@}
+%\addtolength{\headsep}{\headsep}
+%\setlength{\push@skip}{.2\textwidth}
+\newenvironment{page}{\vspace*{\stretch{1}}}
+{\vspace*{\stretch{2.5}}\newpage}
+\pagestyle{plain}
+%%%% fin macro %%%%
+
+Il faut ensuite oprer ce que les imprimeurs appellent une
+imposition : imprimer la page tant tel endroit de la x-ime
+feuille de telle sorte qu'il n'y ait plus qu' plier la liasse
+pour obtenir un livre prt tre reli. Cette tape est facile
+ raliser soit l'aide de dvidvi (mais qui n'autorise pas les
+rotations, ce qui peut en limiter l'intrt pour des formats
+spciaux) soit avec pstops :
+pstops "2:0L@.7(21cm,0)+1L@.7(21cm,14.85cm)" un.ps deux.ps
+disponible sur ftp://ftp.fdn.org/pub/CTAN/support/psutils/.
+
+* L'option a5paper de LaTeX2e permet galement de faire cela.
+Il faut ensuite utiliser dvidvi et dvips en -t landscape. dvips
+est disponible entre autres par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/sources/.
+
+* Le package 'a5booklet' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/a5booklet/.
+
+* Consulter galement le package '2up' pour LaTeX2e.
+
+* Le package 'poligraf' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/TeX-PS/cmyk-hax/ permet d'agir sur la mise en page
+d'un document avant impression.
+
+* psnup et psbook peuvent galement permettre de faire de la
+composition mais il vaut alors mieux travailler avec des polices
+postscript. Ces utilitaires sont accessibles via :
+http://www.dcs.ed.ac.uk/home/ajcd/psutils/.
+
+Exemple (J.A. Ferrez) :
+=================SNIP
+#!/bin/sh
+#
+# Turn a (clean) PS file into a booklet
+#
+# input on stdin or file in arg
+#
+# psbook -- reorder the pages
+# see -s option for _very_ large files
+# psnup -- scale and place two pages onto one
+# pstops -- reverse the odd pages for duplex printing
+#
+# outup on stdout
+#
+psbook $1 | psnup -2 | pstops "2:0,1U(21cm,29.7cm)"
+=================SNIP
+%%%% fin exemple %%%%
+
+* Le rsultat est possible galement en ne travaillant que sur
+le postscript : dvips -h twoup -t landscape fichier.dvi.
+
+* Sur PC on peut utiliser dvidrv.
+
+* Pour PC twoup fait cela, mais ce n'est pas du domaine public.
+
+# 6.6 # Comment dfinir un format de document ?
+-----------------------------------------------
+La structure d'une page LaTeX permet de nombreux ajustements :
++ \setlength{\textwidth}{??cm} permet de fixer la largeur du
+texte
++ \setlength{\textheight}{??cm} permet de fixer la hauteur du
+texte
++ \setlength{\oddsidemargin}{(-)??cm} permet de dfinir la
+marge gauche des pages impaires
++ \setlength{\evensidemargin}{(-)??cm} permet de dfinir la
+marge gauche des pages paires
++ \setlength{\topskip}{??cm} laisse un espace en haut de page
++ \setlength{\footskip}{??cm} laisse un espace en bas de page
++ \setlength{\headheight}{??cm} fixe la hauteur de l'entte
++ \addtolength{\topmargin}{(-)??cm}
++ \addtolength{\textheight}{(-)??cm}
+
+* Il existe galement les packages 'a4' et 'a4wide' disponibles
+respectivement sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/ntgclass/ et dans
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ qui permettent de
+redfinir les marges et largeur de texte.
+
+* Le package 'geometry' est plus flexible que les prcdents
+pour dfinir son propre format de page. Il dfinit de
+nouvelles variables de structure de la page. Il propose en
+outre un ensemble de formats par dfaut (a0paper, b5paper,
+legalpaper, ...).
+
+# 6.7 # Comment redfinir les marges d'un document ?
+----------------------------------------------------
+* Le package 'vmargin', de V. Kuhlmann, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/. Il permet facilement de
+redfinir globalement (pour tout le document) les marges d'un
+document par la commande :
+\setmarginsrb{1}{2}{3}{4}{5}{6}{7}{8}
+1 est la marge gauche
+2 est la marge en haut
+3 est la marge droite
+4 est la marge en bas
+5 fixe la hauteur de l'entte
+6 fixe la distance entre l'entte et le texte
+7 fixe la hauteur du pied de page
+8 fixe la distance entre le texte et le pied de page
+
+Vous pouvez galement utiliser des valeurs par dfaut en rapport
+avec le papier utilis, par exemple:
+\setpapersize{A4}
+
+* L'environnement changemargin dcrit ci-dessous permet de
+modifier localement les marges d'un document. Il prend deux
+arguments, la marge gauche et la marge droite (ces arguments
+peuvent prendre des valeurs ngatives).
+
+%%%% debut macro %%%%
+\newenvironment{changemargin}[2]{\begin{list}{}{%
+\setlength{\topsep}{0pt}%
+\setlength{\leftmargin}{0pt}%
+\setlength{\rightmargin}{0pt}%
+\setlength{\listparindent}{\parindent}%
+\setlength{\itemindent}{\parindent}%
+\setlength{\parsep}{0pt plus 1pt}%
+\addtolength{\leftmargin}{#1}%
+\addtolength{\rightmargin}{#2}%
+}\item }{\end{list}}
+%%%% fin macro %%%%
+
+Exemple :
+\begin{changemargin}{2cm}{-1cm}
+ Ceci permet d'augmenter la marge gauche de 2cm et de diminuer
+ celle de droite de 1cm.
+\end{changemargin}
+A comparer avec un texte qui occupe toute la largeur de la page,
+comme celui-ci.
+%%%% fin exemple %%%%
+
+* Le package 'geometry' permet de redfinir les marges d'un
+document ou de dfinir le layout de la page.
+
+Exemple 1 :
+\geometry{margin=5pt}
+quivalent
+\geometry{hmargin=5pt, vmargin=5pt}
+quivalent
+\geometry{margin={5pt,5pt}}
+%%%% fin exemple %%%%
+
+Exemple 2 :
+\documentclass{report}
+\usepackage{french}
+\usepackage{geometry}
+\geometry{scale=1.0, nohead}
+\begin{document}
+Ainsi, le texte apparat beaucoup plus haut dans une page.
+\end{document}
+%%%% fin exemple %%%%
+
+Exemple 3 :
+\documentclass{report}
+\usepackage{french}
+\begin{document}
+Voici une page normale pour comparer.
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'truncate' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ permet de fixer la
+largeur d'un texte.
+
+* Il existe galement le package 'typearea' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/script/.
+
+* L'environnement narrow, de K. Reckdahl, ci-dessous permet
+d'encapsuler des paragraphes de largeurs diffrentes.
+%%%% debut macro %%%%
+%-----------------------------------------------------------------
+% \begin{narrow}{1.0in}{0.5in} produces text which is narrowed
+% by 1.0 on left margin and 0.5 inches on right margin
+% \begin{narrow}{-1.0in}{-0.5in} produces text which is widened
+% by 1.0 on left margin and 0.5 inches on right margin
+% Narrow environments can be nested and are ended by \end{narrow}
+%-----------------------------------------------------------------
+\newenvironment{narrow}[2]{%
+ \begin{list}{}{%
+ \setlength{\topsep}{0pt}%
+ \setlength{\leftmargin}{#1}%
+ \setlength{\rightmargin}{#2}%
+ \setlength{\listparindent}{\parindent}%
+ \setlength{\itemindent}{\parindent}%
+ \setlength{\parsep}{\parskip}%
+ }%
+\item[]}{\end{list}}
+%%%% fin macro %%%%
+
+# 6.8 # Comment changer l'orientation d'un document ?
+-----------------------------------------------------
+* Globalement, pour passer en orientation paysage, il suffit de
+mettre l'option landscape dans \documentclass (LaTeX2e) ou dans
+\documentstyle (LaTeX2.09).
+
+Exemple :
+\documentclass[landscape]{report}
+\usepackage{french}
+\begin{document}
+Voici un document crit dans un sens non conventionnel.
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'lscape' de D. Carlisle (LaTeX2e), disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/, permet de changer
+localement d'orientation portrait vers paysage et vice versa. Il
+dfinit l'environnement landscape.
+
+Exemple :
+\documentclass[11pt]{report}
+\usepackage{lscape}
+
+\begin{document}
+
+\begin{landscape}
+ Un petit tour la campagne,~\ldots
+\end{landscape}
+
+et nous voici de retour dans la galerie, aprs un changement de
+page bien videmment.
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Il existe galement le package 'rotating' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/rotating/.
+
+Exemple (tir de la doc) :
+\newcount\wang
+\newsavebox{\wangtext}
+\newdimen\wangspace
+\def\wheel#1{\savebox{\wangtext}{#1}%
+\wangspace\wd\wangtext
+\advance\wangspace by 1cm%
+\centerline{%
+\rule{0pt}{\wangspace}%
+\rule[-\wangspace]{0pt}{\wangspace}%
+\wang=-180\loop\ifnum\wang<180
+\rlap{\begin{rotate}{\the\wang}%
+\rule{1cm}{0pt}#1\end{rotate}}%
+\advance\wang by 10 \repeat}}
+\wheel{Save the whale}
+%%%% fin exemple %%%%
+
+* Il existe aussi le programme docstrip disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/unpacked/docstrip.tex.
+
+* Pour le cas o vous auriez un fichier dvi en landscape, vous
+pouvez obtenir un fichier postscript propre en utilisant la
+commande:
+
+Exemple :
+dvips -t a4 -t landscape -o tmp.ps toto.dvi
+%%%% fin exemple %%%%
+
+# 6.9 # Comment justifier verticalement un paragraphe ?
+-------------------------------------------------------
+L'environnement vcenterpage ci-dessous permet de centrer
+verticalement un texte sur une page seule.
+
+%%%% debut macro %%%%
+\newenvironment{vcenterpage}
+{\newpage\vspace*{\fill}}
+{\vspace*{\fill}\par\pagebreak}
+%%%% fin macro %%%%
+
+Exemple :
+\begin{vcenterpage}
+ Texte qui apparait au milieu de la page.
+\end{vcenterpage}
+%%%% fin exemple %%%%
+
+# 6.10 # Comment modifier la commande \caption ?
+------------------------------------------------
+* Le package 'hangcaption', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/, dans lequel la commande
+\isucaption remplace la commande \caption, permet de modifier la
+mise en page de cette dernire. En particulier, il permet de
+dfinir \captionwidth.
+
+* Il existe galement les packages 'caption' et 'caption2'
+disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/caption/ qui permettent de
+modifier la commande \caption classique (largeur, style,
+fonte, ...).
+
+Exemples :
+\usepackage[small,hang]{caption2}
+\renewcommand{\captionfont}{\it \small}
+\renewcommand{\captionlabelfont}{\it \bf \small}
+\renewcommand{\captionlabeldelim}{ :}
+%%%% fin exemple %%%%
+
+Remarque : il est recommand d'utiliser 'caption2' plutt que
+ 'caption'.
+
+* Le package 'topcapt' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/misc/ dfinit la commande \topcaption qui
+permet de placer le texte de la commande caption au dessus du
+flottant auquel elle est rattache.
+
+* Le package 'french' de B. Gaulle propose la commande
+\unnumberedcaptions qui permet de supprimer la numrotation des
+flottants.
+
+* Pour avoir une prsentation du type :
+Figure 1. Voici le texte de la lgende d'une figure. Mais
+ lorsque la lgende est longue, elle se prsente
+ comme ceci.
+
+au lieu de :
+Figure 1. Voici le texte de la lgende d'une figure. Mais
+lorsque la lgende est longue, elle se prsente comme
+ceci.
+
+on peut utiliser \caption[texte]{\protect\parbox[t]{wd}{texte}}
+o wd est la largeur de la bote (cette largeur peut tre adapte
+ la taille de la figure automatiquement si la figure est
+elle-mme dans une boite dont on rcupre la largeur). \protect
+est absolument ncessaire pour viter une erreur. Le texte au
+dbut [texte] est celui qui apparatra dans la table des figures
+(il peut ventuellement tre plus court).
+
+Plus simplement, le package 'caption2' permet de faire la mme
+chose avec l'option hang.
+
+* La variable \figurename permet de redfinir le nom du titre de
+la figure. De mme pour \tablename et les tableaux.
+
+Exemple :
+\def\figurename{Croquis}
+%%%% fin exemple %%%%
+
+# 6.11 # Comment modifier un changement de page ?
+-------------------------------------------------
+* \newpage impose un changement brutal de page.
+
+* \pagebreak[n] o n reprsente l'autorit avec laquelle on veut
+changer de page (n compris entre 1 et 5). Cette commande garde
+la justification, 1 impose une contrainte faible, 5 impose une
+contrainte svre.
+
+* \nopagebreak[n] idem pour empcher une coupure de page.
+
+* \clearpage agit comme un \newpage mais libre le buffer de
+flottants.
+
+* \cleardoublepage fait la mme chose et force un redmmarrage
+sur une page impaire.
+
+* \enlargethispage{lgr} impose LaTeX2e de comprimer (lgr
+ngatif) ou d'expanser (lgr positif) le contenu d'une page.
+Ceci pour viter que la page suivante contienne trop peu de
+texte.
+
+Exemples :
+\enlargethispage{1cm} % ajoute un cm
+\enlargethispage{-2\baselineskip} % supprime deux lignes dans la
+ % page
+%%%% fin exemple %%%%
+
+Remarque : \enlargethispage*{lgr} donne une autorit plus grande
+ la commande \enlargethispage en l'obligeant agir
+ sur les espacements lastiques verticaux contenus
+ dans la page courante.
+
+* J.P. Drucbert donne ci-dessous un petit papier dcrivant un
+style block.sty bricol partir de macro de diverses origines
+(dont D. Arseneau, assez connu). Si vous passez LaTeX sur ce
+papier, block.sty sera cr. Les macros les plus intressantes
+sont \need{dim} et \lneed{N}, qui provoquent un saut de page
+s'il reste moins que la dimension dim (ou N fois \baselinskip)
+verticalement sur la page. Ce n'est pas parfait, mais cela m'a
+rendu des services.
+
+%%%% debut macro %%%%
+\begin{filecontents}{block.sty}
+\ifx\endBlock\undefined
+\def\block{\begingroup%
+\def\endblock{\egroup\endgroup}%
+\vbox\bgroup}%
+\long\def\Block{\begingroup%
+\def\endBlock{\unskip\egroup\endgroup}%
+\pagebreak[2]\vspace*{\parskip}\vbox\bgroup%
+\par\noindent\ignorespaces}
+\long\def\IBlock{\begingroup%
+\def\endIBlock{\unskip\egroup\endgroup}%
+\pagebreak[2]\vspace*{\parskip}\vbox\bgroup\par\ignorespaces}
+\def\need#1{\ifhmode\unskip\par\fi \penalty-100 \begingroup
+% preserve \dimen@, \dimen@i
+ \ifdim\prevdepth>\maxdepth \dimen@i\maxdepth
+ \else \dimen@i\prevdepth\fi
+ \kern-\dimen@i
+ \dimen@\pagegoal \advance\dimen@-\pagetotal % space left
+ \ifdim #1>\dimen@
+ \vfill\eject\typeout{WARNING- EJECT BY NEED}
+ \fi
+ \kern\dimen@i
+ \endgroup}
+\def\lneed#1{\need{#1\baselineskip}}
+% \begin{block} ... \end{block} delimite un bloc qui restera,
+% si possible, sur une seule page.
+\long\def\TBlock{\begingroup%
+\def\endTBlock{\unskip\egroup\endgroup}%
+\pagebreak[2]\vspace*{\parskip}\vtop\bgroup%
+\par\noindent\ignorespaces}
+\else
+\typeout{block.sty already loaded}
+\fi
+\endinput
+
+\def\need#1{\par \penalty-100 \begingroup
+% preserve \dimen@, \dimen@i
+ \ifdim\prevdepth>\maxdepth \dimen@i\maxdepth
+ \else \dimen@i\prevdepth\fi
+ \kern-\dimen@i
+ \dimen@\pagegoal \advance\dimen@-\pagetotal % space left
+ \ifdim #1>\dimen@ \vfil \eject \fi
+ \kern\dimen@i
+ \endgroup}
+\end{filecontents}
+
+\documentclass[12pt,a4paper]{article}
+\def\bs{\texttt{\char'134}}
+\parskip=12pt plus1pt minus0.5pt
+\usepackage[english,francais]{babel}
+\usepackage[T1]{fontenc}
+\usepackage[isolatin]{inputenc}
+\begin{document}
+\clearpage
+\section{Paquetage \texttt{block}}\label{BLOCK+}
+Ce paquetage offre divers outils permettant d'empcher qu'une
+rupture de page se produise un certain endroit.
+
+\subsection{Blocs Protgs}
+
+Vous pouvez protger une zone contre la rupture de page. Il
+suffit pour cela de la placer dans un environnement
+\texttt{Block} ou dans un environnement \texttt{IBlock}. Dans le
+premier cas (\texttt{Block}), le premier paragraphe se trouvant
+dans la zone ne sera pas indent, mais le sera dans le second
+cas (\texttt{IBlock}). Ceci est utile en particulier pour
+viter de sparer un texte et un exemple qui l'accompagne. Les blocs ainsi
+protgs doivent, bien entendu, rester assez petits. La syntaxe
+est (vous pouvez remplacer \texttt{Block} par \texttt{IBlock}):
+\begin{quote}\tt
+%\begin{tabular}{l}
+\bs begin\{Block\}\\
+\qquad\ldots\\
+zone protge\\
+\qquad\ldots\\
+\bs end\{Block\}
+%\end{tabular}
+\end{quote}
+
+Cette mthode, trs simple, a l'inconvnient de ne pas pouvoir
+s'appliquer lorsque la zone protger doit contenir une
+commande de sectionnement (c'est--dire du mme type que
+\verb|\section|), une note en bas de page, une note marginale ou
+un corps mobile (figure ou table). Dans ce cas, il faudra
+utiliser une des commandes du paragraphe suivant.
+
+\subsection{Rservations Verticales}
+Vous pouvez aussi demander de changer de page (ou de colonne, si votre
+document est sur deux colonnes) s'il ne reste pas verticalement assez
+de place sur la page. Deux commandes de rservation verticale sont
+disponibles: \verb|\need{|{\em dimension\/}\verb|}|, dont le paramtre est une
+longueur, et \verb|\lneed{|{\em nombre\/}\verb|}|, dont le paramtre est
+le nombre de lignes quivalant l'espace vertical demand (avec cette forme
+le paramtre est plus facile estimer).
+
+\end{document}
+%%%% fin macro %%%%
+
+* Pour viter les coupures de page (ou les coupures de colonnes
+avec multicol.sty) l'intrieur des \item dans une description
+(et d'ailleurs dans toute liste), solution simple sortie du
+TeXbook:
+\begin{description}\interlinepenalty 10000
+
+# 6.12 # Comment obtenir des colonnes parallles ?
+--------------------------------------------------
+Le package 'parallel' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/parallel/ permet d'obtenir
+deux colonnes dont l'une peut contenir la traduction de l'autre.
+
+# 6.13 # Comment dfinir l'espace de dbut de paragraphe ?
+----------------------------------------------------------
+* Il faut valoriser la variable \parindent.
+
+Exemple :
+\setlength{\parindent}{1cm}
+%%%% fin exemple %%%%
+
+* Pour agir localement, on peut utiliser \hspace*{lgr}.
+
+* Le package 'indentfirst' permet de forcer LaTeX indenter le
+premier paragraphe aprs une nouvelle section (indentation
+normalement non utilise en typographie franaise).
+
+# 6.14 # Comment supprimer la date sur une page de titre ?
+----------------------------------------------------------
+Il faut ajouter la commande \date{} dans le prambule du
+document.
+
+# 6.15 # Comment mettre en valeur la premire lettre d'un chapitre ?
+--------------------------------------------------------------------
+* Il faut utiliser le package 'dropcaps' de F. Lauwers.
+Il est disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/dropcaps/.
+Ce package est utilisable avec LaTeX2.09 et LaTeX2e.
+
+* Les packages 'initial' et 'initials' pour LaTeX2e sont
+disponibles sur CTAN. Le second que l'on peut trouver dans
+ftp://ftp.fdn.org/pub/CTAN/fonts/gothic/yinit/ fait appel des fontes yinit particulires.
+
+* Il existe galement un package 'drop' pour LaTeX2.09, mais
+compatible LaTeX2e, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/.
+
+Exemple :
+\documentclass[12pt,a4paper]{article}
+\usepackage{drop}
+\font\largefont=yinitas % fontes yinit
+begin{document}
+\drop{D}OES THERE EXIST a field with 4 elements?
+\end{document}
+%%%% fin exemple %%%%
+
+* 'bigdrop' accessible sur CTAN dans/CTAN/digests/ttn est une
+macro TeX compatible LaTeX.
+
+* Le package 'bigstart' pour LaTeX2.09 et LaTeX2e permet
+galement de faire cela.
+
+* Il existe galement le package 'picinpar' pour LaTeX2.09
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/picinpar/ et
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/4alltex/disk04/.
+
+* On peut galement dfinir sa propre macro :
+%%%% debut macro %%%%
+\font\capfont=cmbx12 at 24.87 pt % or yinit, or...?
+\newbox\capbox \newcount\capl \def\a{A}
+\def\docappar{\medbreak\noindent\setbox\capbox\hbox{%
+\capfont\a\hskip0.15em}\hangindent=\wd\capbox%
+\capl=\ht\capbox\divide\capl by\baselineskip\advance\capl by1%
+\hangafter=-\capl%
+\hbox{\vbox to8pt{\hbox to0pt{\hss\box\capbox}\vss}}}
+\def\cappar{\afterassignment\docappar\noexpand\let\a }
+%%%% fin macro %%%%
+
+Exemple :
+\cappar Il tait une fois un petit chaperon rouge qui avait une
+grand-mre qui habitait de l'autre ct de la foret. Un jour,
+alors que sa grand-mre tait malade, le petit chaperon rouge
+dcida de lui rendre visite~\ldots
+%%%% fin exemple %%%%
+
+* Un petit dernier, le package 'dropping' qui tend le
+package 'dropcaps' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/dropping/.
+
+Exemple :
+\dropping{3}{\itshape{} Voici} un exemple de ce que permet de
+faire le magnifique package dropping de M. Dahlgren. La commande
+\texttt{\\dropping} peut prendre en argument un mot comme c'est le cas ici
+ou une simple lettre.
+%%%% fin exemple %%%%
+
+* Le package 'french' de B. Gaulle propose galement la commande
+\lettrine.
+
+Exemple :
+\lettrine{UN jour,} mon prince~\ldots
+%%%% fin exemple %%%%
+
+* Le paquetage 'lettrine' de Daniel Flipo propose lui aussi la commande
+\lettrine, mais avec une diversit d'options inconnues french (nombre de
+lignes, forme, etc.) Tir de la doc:
+
+Exemple :
+\lettrine[lines=4, slope=-0.5em, lhang=0.5, nindent=0pt]{V}{oici}
+%%%% fin exemple %%%%
+
+* Le paquetage 'lettrine' de Daniel Flipo propose lui aussi la commande
+\lettrine, mais avec une diversit d'options inconnues french (nombre de
+lignes, forme, etc.) Tir de la doc:
+
+Exemple :
+\lettrine[lines=4, slope=-0.5em, lhang=0.5, nindent=0pt]{V}{oici}
+%%%% fin exemple %%%%
+
+# 6.16 # Comment prserver les tabulations en mode verbatim ?
+-------------------------------------------------------------
+* Le package 'moreverb' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/. Il propose notamment un
+environnement verbatimtab qui permet de conserver des
+tabulations.
+
+Exemple :
+\begin{verbatimtab}
+int pattern(char *p, int n, int m)
+{
+ int orig = current_position();
+ int new_pos;
+
+ goto_line(n);
+
+ if(p && forward_search(p) && (current_line()<m)){
+ new_pos = current_position();
+ goto_char(orig);
+ return(new_pos);
+ }
+ return(-1);
+}
+\end{verbatimtab}
+%%%% fin exemple %%%%
+
+* Il existe galement le package 'verbasef' (verbatim automatic
+segmentation of external files) disponible sur CTAN. Il utilise
+l'environnement figure.
+
+* On peut galement inclure les lignes suivantes dans le
+prambule du document :
+%%%% debut macro %%%%
+\makeatletter
+{\catcode`\^^I=\active
+\gdef\verbatim{\catcode`\^^I=\active\def^^I{\hspace*{4em}}%
+\@verbatim \frenchspacing\@vobeyspaces \@xverbatim}}
+\makeatother
+%%%% fin macro %%%%
+
+# 6.17 # Comment modifier les enttes de chapitre ?
+---------------------------------------------------
+Il faut modifier la macro makechapterhead.
+
+Ajouter, par exemple, dans le preambule :
+%%%% debut macro %%%%
+\makeatletter
+\def\@makechapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright \normalfont
+ \interlinepenalty\@M
+ \ifnum \c@secnumdepth >\m@ne
+ \Huge\bfseries \thechapter\quad
+ \fi
+ \Huge \bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+
+\def\@makeschapterhead#1{%
+ \vspace*{50\p@}%
+ {\parindent \z@ \raggedright
+ \normalfont
+ \interlinepenalty\@M
+ \Huge \bfseries #1\par\nobreak
+ \vskip 40\p@
+ }}
+\makeatother
+%%%% fin macro %%%%
+
+# 6.18 # Comment dfinir des tabulations ?
+------------------------------------------
+Il faut utiliser l'environnement tabbing qui permet de placer
+des marques d'alignement dans un texte.
+
+Exemple :
+\begin{tabbing}
+ Voici \= des \= marques \= de tabulation \\
+ \> la je m'aligne sur la premire \\
+ \> \> \> la sur la troisime \\
+ \hspace{3cm} \= \hspace{2cm} \= \kill
+ un \> autre \> exemple.
+\end{tabbing}
+%%%% fin exemple %%%%
+
+# 6.19 # Comment obtenir des lettres accentues dans tabbing ?
+--------------------------------------------------------------
+* Pour produire un \'{e} dans un environnement tabbing o la
+commande \' a t redfinie, il faut utiliser \a'{e} ou \a'e
+
+* Le style suivant de J.P. Drucbert permet de remplacer
+l'environnement standard tabbing par l'environnement Tabbing
+dans lequel les commandes \` \' \> \< \= \+ \- sont remplaces
+par \TAB` \TAB' \TAB> \TAB< \TAB= \TAB+ \TAB- ce qui permet de
+prserver les commandes d'accent (\' \` ou \=).
+
+%%%% debut macro %%%%
+\ProvidesPackage{Tabbing}[1996/01/16]
+\NeedsTeXFormat{LaTeX2e}[1995/12/01]
+\gdef\Tabbing{\lineskip \z@skip
+% \let\>\@rtab
+% \let\<\@ltab
+% \let\=\@settab
+% \let\+\@tabplus
+% \let\-\@tabminus
+% \let\`\@tabrj
+% \let\'\@tablab
+\def\TAB##1{\ifx ##1>\@rtab\else
+ \ifx ##1<\@ltab\else
+ \ifx ##1=\@settab\else
+ \ifx ##1+\@tabplus\else
+ \ifx ##1-\@tabminus\else
+ \ifx ##1`\@tabrj\else
+ \ifx ##1'\@tablab\else
+ \PackageError{Tabbing}%
+ {Bad argument ##1 for Tabbing
+ specification} \fi\fi\fi\fi\fi\fi\fi}
+ \let\\=\@tabcr
+ \global\@hightab\@firsttab
+ \global\@nxttabmar\@firsttab
+ \dimen\@firsttab\@totalleftmargin
+ \global\@tabpush\z@ \global\@rjfieldfalse
+ \trivlist \item\relax
+ \if@minipage\else\vskip\parskip\fi
+ \setbox\@tabfbox\hbox{\rlap{\indent\hskip\@totalleftmargin
+ \the\everypar}}\def\@itemfudge{\box\@tabfbox}%
+ \@startline\ignorespaces}
+\gdef\endTabbing{%
+ \@stopline\ifnum\@tabpush >\z@ \@badpoptabs \fi\endtrivlist}
+\endinput
+%%%% fin macro %%%%
+
+# 6.20 # Comment encadrer du texte ?
+------------------------------------
+* Une solution consiste dfinir un tableau d'une seule
+cellule.
+
+* On peut aussi utiliser :
+\fbox{
+\begin{minipage}{0.7\textwidth}
+ Texte...
+\end{minipage}
+}
+
+* On peut galement se dfinir son propre environnement.
+
+Exemple :
+\newsavebox{\fmbox}
+\newenvironment{fmpage}[1]
+ {\begin{lrbox}{\fmbox}\begin{minipage}{#1}}
+ {\end{minipage}\end{lrbox}\fbox{\usebox{\fmbox}}}
+
+Utilisation :
+\begin{fmpage}{3cm}
+ Texte encadrer dans une bote ne dpassant pas 3
+ centimtres de large.
+\end{fmpage}
+%%%% fin exemple %%%%
+
+* Il existe galement le package 'fancybox', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/others/seminar/inputs/, qui dfinit
+des fonctions telles que \shadowbox, \doublebox, \ovalbox,...
+
+Exemple :
+\shadowbox{Texte ombr.}
+\doublebox{Texte doublement encadr.}
+\ovalbox{Texte dans un cadre aux coins arrondis.}
+%%%% fin exemple %%%%
+
+* Le package 'boxedminipage' est un vieux style LaTeX2.09
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/.
+
+* Voir galement le package 'hh' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/hh/.
+
+* Le package 'niceframe' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/niceframe/ permet de
+dfinir des cadres pleine page.
+
+* Pour encadrer un texte pouvant s'tendre sur plusieurs pages,
+il existe le package 'eclbkbox' :
+%%%% debut macro %%%%
+% eclbkbox.sty by Hideki Isozaki, 1992
+% Date: May 28, 1993
+
+\newbox\bk@bxb
+\newbox\bk@bxa
+\newif\if@bkcont
+\newif\ifbkcount
+\newcount\bk@lcnt
+
+\def\breakboxskip{2pt}
+\def\breakboxparindent{1.8em}
+
+\def\breakbox{\vskip\breakboxskip\relax
+\setbox\bk@bxb\vbox\bgroup
+\advance\linewidth -2\fboxrule
+\advance\linewidth -2\fboxsep
+\hsize\linewidth\@parboxrestore
+\parindent\breakboxparindent\relax}
+
+% \@tempdimb: amount of vertical skip
+% between the first line (\bk@bxa) and the rest (\bk@bxb)
+\def\bk@split{%
+\@tempdimb\ht\bk@bxb % height of original box
+\advance\@tempdimb\dp\bk@bxb
+\setbox\bk@bxa\vsplit\bk@bxb to\z@ % split it
+\setbox\bk@bxa\vbox{\unvbox\bk@bxa}% recover height & depth of \bk@bxa
+\setbox\@tempboxa\vbox{\copy\bk@bxa\copy\bk@bxb}% naive concatenation
+\advance\@tempdimb-\ht\@tempboxa
+\advance\@tempdimb-\dp\@tempboxa}% gap between two boxes
+
+% \@tempdima: height of the first line (\bk@bxa) + fboxsep
+\def\bk@addfsepht{%
+ \setbox\bk@bxa\vbox{\vskip\fboxsep\box\bk@bxa}}
+
+\def\bk@addskipht{%
+ \setbox\bk@bxa\vbox{\vskip\@tempdimb\box\bk@bxa}}
+
+% \@tempdima: depth of the first line (\bk@bxa) + fboxsep
+\def\bk@addfsepdp{%
+ \@tempdima\dp\bk@bxa
+ \advance\@tempdima\fboxsep
+ \dp\bk@bxa\@tempdima}
+
+% \@tempdima: depth of the first line (\bk@bxa) + vertical skip
+\def\bk@addskipdp{%
+ \@tempdima\dp\bk@bxa
+ \advance\@tempdima\@tempdimb
+ \dp\bk@bxa\@tempdima}
+
+\def\bk@line{%
+ \hbox to \linewidth{\ifbkcount\smash{\llap{\the\bk@lcnt\ }}\fi
+ \vrule \@width\fboxrule\hskip\fboxsep
+ \box\bk@bxa\hfil
+ \hskip\fboxsep\vrule \@width\fboxrule}}
+
+\def\endbreakbox{\egroup
+\ifhmode\par\fi{\noindent\bk@lcnt\@ne
+\@bkconttrue\baselineskip\z@\lineskiplimit\z@
+\lineskip\z@\vfuzz\maxdimen
+\bk@split\bk@addfsepht\bk@addskipdp
+\ifvoid\bk@bxb % Only one line
+\def\bk@fstln{\bk@addfsepdp
+\vbox{\hrule\@height\fboxrule\bk@line\hrule\@height\fboxrule}}%
+\else % More than one line
+\def\bk@fstln{\vbox{\hrule\@height\fboxrule\bk@line}\hfil
+\advance\bk@lcnt\@ne
+\loop
+ \bk@split\bk@addskipdp\leavevmode
+\ifvoid\bk@bxb % The last line
+ \@bkcontfalse\bk@addfsepdp
+ \vtop{\bk@line\hrule\@height\fboxrule}%
+\else % 2,...,(n-1)
+ \bk@line
+\fi
+ \hfil\advance\bk@lcnt\@ne
+\if@bkcont\repeat}%
+\fi
+\leavevmode\bk@fstln\par}\vskip\breakboxskip\relax}
+
+\bkcountfalse
+%%%% fin macro %%%%
+
+L'encadrement du texte est obtenu par l'environnement breakbox.
+
+\bkcounttrue : les lignes sont numrotes.
+\bkcountfalse : elles ne le sont pas (dfaut).
+
+On peut emboter des environnements breakbox.
+
+# 6.21 # Comment grer des URL WWW ?
+------------------------------------
+* Il existe le package 'url' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ qui permet de grer les
+coupures des URL WWW un peu longues. Il est galement capable de
+grer les adresses e-mail, les liens hypertexte, les noms de
+directories. En outre, cet outil est paramtrable.
+
+Exemple :
+\usepackage{url}
+\urlstyle{sf}
+..
+\url{http://hostname/~username}
+%%%% fin exemple %%%%
+
+* Le package 'path' disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/eplain/
+offre les mmes possibilits.
+
+* La macro \discretionary permet galement de dire comment
+couper une chane de caractres :
+\discretionary{Avant la coupure}{aprs}{s'il n'y en a pas}
+
+Remarque : \- est dfini comme \discretionary {-}{}{}
+
+# 6.22 # Comment mettre en page des exercices dont les solutions sont reportes dans un autre paragraphe ?
+----------------------------------------------------------------------------------------------------------
+L'objectif ici est de pouvoir saisir dans le fichier source les
+textes des exercices suivis de leurs solutions, alors qu'au
+niveau de la mise en page du document, les solutions
+apparassent groupes dans un autre paragraphe/chapitre.
+
+* Le package 'answers', de M. Piff, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/answers/ permet galement de
+raliser ce genre d'exercice. Il permet entre autres :
++ d'avoir plusieurs types de solutions (ex: rponse numrique
+seule ou dtail),
++ d'inclure les solutions (l'une, l'autre ou les deux dans
+le cas prcit) dans le texte (aprs une marque spcifique
+si dsir),
++ mettre les solutions la fin,
++ ne pas mettre les solutions.
+
+Exemple :
+%%
+%% This is file `ansexam2.tex',
+%% generated with the docstrip utility.
+%%
+%% The original source files were:
+%%
+%% answers.dtx (with options: `ex2')
+%%
+\documentclass[12pt,a4paper]{article}
+\usepackage{answers}%\usepackage[nosolutionfiles]{answers}
+% def d'un environnement Exercise numerote
+\newtheorem{Exc}{Exercise}
+\newenvironment{Ex}{\begin{Exc}\normalfont}{\end{Exc}}
+% Trois types de solutions sont proposes
+\Newassociation{solution}{Soln}{test}
+\Newassociation{hint}{Hint}{test}
+\Newassociation{Solution}{sSol}{testtwo}
+\newcommand{\prehint}{~[Hint]}
+\newcommand{\presolution}{~[Solution]}
+\newcommand{\preSolution}{~[Homework]}
+% test
+\newcommand{\Opentesthook}[2]%
+ {\Writetofile{#1}{\protect\section{#1: #2}}}
+% introduction de la solution
+\renewcommand{\Solnlabel}[1]{\emph{Solution #1}}
+\renewcommand{\Hintlabel}[1]{\emph{Hint #1}}
+\renewcommand{\sSollabel}[1]{\emph{Solution to #1}}
+
+\begin{document}
+% gestion des fichiers contenant les solutions
+ \Opensolutionfile{test}[ans2]{Solutions}
+ \Writetofile{test}{\protect\subsection{Some Solutions}}
+ \Opensolutionfile{testtwo}[ans2x]
+ \Writetofile{testtwo}{%
+ \protect\subsection{Extra Solutions}}
+
+ % Exercices
+ \section{Exercises}
+ \begin{Ex}
+ An exercise with a solution.
+ \begin{solution}
+ This is a solution.
+ \relax{}
+ \end{solution}
+ \end{Ex}
+ \begin{Ex}
+ An exercise with a hint and a secret solution.
+ \begin{hint}
+ This is a hint.
+ \end{hint}
+ \begin{Solution}
+ This is a secret solution.
+ \end{Solution}
+ \end{Ex}
+ \begin{Ex}
+ An exercise with a hint.
+ \begin{hint}
+ This is a hint.
+ \end{hint}
+ \end{Ex}
+ % gestion des fichiers contenant les solutions
+ \Closesolutionfile{test}
+ \Readsolutionfile{test}
+ % \clearpage
+ \hrule
+ \Closesolutionfile{testtwo}
+ \Readsolutionfile{testtwo}
+\end{document}
+%%
+%% End of file `ansexam2.tex'.
+
+%%%% fin exemple %%%%
+
+* On peut galement trouver le package 'exam' sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/exams/.
+
+# 6.23 # Comment positionner un objet dans une page ?
+-----------------------------------------------------
+* Pour pouvoir positionner un objet aux coordonnes x,y par
+rapport au coin suprieur gauche d'une page, il suffit d'utiliser
+le package 'atxy' disponible par ftp sur
+ftp://ftp.univ-orleans.fr/pub/tex/PC/AsTeX/Paq_Base/ dans
+le fichier l209misc.zip.
+
+Exemple :
+\atxy(3cm,2.5cm) {toto adresse toto}
+\atxy(3cm,4cm) {date}
+%%%% fin exemple %%%%
+
+Remarque : petit dfaut, si le document ne contient que des
+ commandes \atxy il n'y a pas de dvi gnr. Il faut
+ donc ajouter n'importe quoi au dbut du document, ~
+ par exemple, pour que a marche.
+
+# 6.24 # Comment lier le placement des flottants aux sections ?
+---------------------------------------------------------------
+Pour lier la position des lments flottants aux limites de
+sections, D. Arseneau a dvelopp le package 'placeins'
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/. Ce
+package dfinit la commande \FloatBarrier qui force le placement
+des flottants avant son appel.
+
+# 6.25 # Comment griser le fond (background) d'un paragraphe ?
+--------------------------------------------------------------
+* Le package 'psboxit', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex2.09/contrib/misc/ et en particulier
+l'environnement "boxitpara" permet de faire cela.
+
+* Le package 'shadbox' disponible sur CTAN dans
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/shadbox/ permet de griser toute
+bote, texte, figure, ....
+
+* Le package 'shading' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/shading/ permet de griser un
+paragraphe.
+
+* De mme, le package 'shade', de P. Schmitt, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/.
+
+* On peut galement utiliser le package 'color'.
+
+Exemple :
+\colorbox[gray]{0.5}{some words}
+%%%% fin exemple %%%%
+
+# 6.26 # Comment modifier l'espace inter-colonnes ?
+---------------------------------------------------
+Il faut modifier la variable \columnsep.
+
+Exemple :
+\addtolength{\columnsep}{5mm}
+%%%% fin exemple %%%%
+
+# 6.27 # Comment modifier les environnements de liste ?
+-------------------------------------------------------
+* L'environnement list permet de dfinir son propre style de
+liste. Sa syntaxe est la suivante :
+\begin{list}{label}{mep}\end{list}
++ l'argument label permet de dfinir le symbole qui sera
+associ chaque lment de la liste.
++ mep permet de dfinir la mise en page des lments de la
+liste. Les paramtres utiliss pour dfinir cette mise en page
+sont les suivants :
+\topsep espace vertical supplmentaire (ajoute \parskip)
+ insr entre le texte prcdant la liste et le 1er objet
+ de la liste
+\partosep espace vertical supplmentaire insr devant la liste
+ si celle-ci est prcde d'une ligne blanche
+\itemsep espace vertical supplmentaire (ajout \parsep)
+ insr entre les lments d'une liste.
+
+Exemple :
+\newenvironment{maliste}%
+{ \begin{list}%
+ {$\bullet$}%
+ {\setlength{\labelwidth}{30pt}%
+ \setlength{\leftmargin}{35pt}%
+ \setlength{\itemsep}{\parsep}}}%
+{ \end{list} }
+
+Utilisation :
+\begin{maliste}
+ \item premier lment
+ \item deuxime lment
+ \begin{maliste}
+ \item petit 1
+ \item petit 2
+ \end{maliste}
+\end{maliste}
+%%%% fin exemple %%%%
+
+* Le petit bout de code ci-dessous, de M. Boyer
+(mboyer@robot.ireq.ca), dfinit les commandes :
++ \noitemsep pour supprimer tout espacement vertical entre les
+items des environnements \itemize, \enumerate et \description.
++ \doitemsep pour les remettre.
+Pour l'utiliser, il suffit de le sauvegarder dans un fichier
+.sty et de l'inclure dans son document par une commande
+\usepackage.
+
+%%%% debut macro %%%%
+%% ----------------------------------------------------
+%% Copyright (c) 1993 Hydro-Quebec mboyer@robot.ireq.ca
+%% ----------------------------------------------------
+
+%% Bring items closer together in list environments
+% Prevent infinite loops
+\let\orig@Itemize =\itemize
+\let\orig@Enumerate =\enumerate
+\let\orig@Description =\description
+% Zero the vertical spacing parameters
+\def\Nospacing{\itemsep=0pt\topsep=0pt\partopsep=0pt%
+\parskip=0pt\parsep=0pt}
+% Redefinition de art12.sty pour commencer a la marge de gauche
+%\leftmargini 1.2em % 2.5em
+
+\def\noitemsep{
+% Redefine the environments in terms of the original values
+\renewenvironment{itemize}{\orig@Itemize\Nospacing}{\endlist}
+\renewenvironment{enumerate}{\orig@Enumerate\Nospacing}{\endlist}
+\renewenvironment{description}{\orig@Description\Nospacing}%
+{\endlist}
+}
+
+\def\doitemsep{
+% Redefine the environments to the original values
+\renewenvironment{itemize}{\orig@Itemize}{\endlist}
+\renewenvironment{enumerate}{\orig@Enumerate}{\endlist}
+\renewenvironment{description}{\orig@Description}{\endlist}
+}
+%%%% fin macro %%%%
+
+* La macro ci-dessous de T. Murphy permet de remplacer les
+numros de l'environnement enumerate par des caractres grecs :
+%%%% debut macro %%%%
+\makeatletter
+\def\greek#1{\expandafter\@greek\csname c@#1\endcsname}
+\def\@greek#1{\ifcase#1\or$\alpha$\or$\beta$\fi}% as many as you
+% need
+\renewcommand{\theenumi}{\greek{enumi}}
+\makeatother
+%%%% fin macro %%%%
+
+* Les dfinitions suivantes :
+\renewcommand{\labelitemi}{\textbullet}
+\renewcommand{\labelitemii}{---}
+\renewcommand{\labelitemiii}{votre-label-pour-le-niveau-iii}
+\renewcommand{\labelitemiv}{votre-label-pour-le-niveau-iv}
+permettent de redfinir les caractres utiliss par
+l'environnement itemize pour ces diffrents niveaux
+d'encapsulation.
+
+Remarque : avec certains packages comme french, il faut placer
+ ces nouvelles dfinitions de commande aprs le
+ \begin{document}.
+
+De mme, utilisez \descriptionlabel pour changer le style des
+tiquettes de l'environment description.
+
+Exemple :
+\renewcommand\descriptionlabel[1]{\hspace\labelsep\normalfont%
+\itshape #1:}
+produit des tiquettes en italique, avec deux points :
+\begin{description}
+ \item[Carte matresse] As
+ \item[Carte matresse l'atout] Valet
+\end{description}
+%%%% fin exemple %%%%
+
+* Pour rduire globalement l'espace entre les items d'une liste
+on peut galement utiliser le bout de code suivant de M. Wooding
+%%%% debut macro %%%%
+\makeatletter
+\toks@\expandafter{\@listI}
+\edef\@listI{\the\toks@\setlength{\parsep}{1pt}}
+\makeatother
+%%%% fin macro %%%%
+
+* Le package 'mdwlist', de M. Wooding, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/mdwtools/ permet de
+redfinir certains paramtres de mise en page des listes qui ne
+sont pas faciles d'accs sous LaTeX.
+
+# 6.28 # Comment souligner plusieurs lignes ?
+---------------------------------------------
+Pour souligner un texte qui comprend des retours la ligne, il
+faut utiliser le package 'ulem' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/. Ce package redfinit en
+fait le mode emphasize. Les commandes \normalem et \ULforem
+permettent de passer du mode \emph classique au mode \emph
+soulign. En mode soulign, la commande devient paramtrable pour
+changer le style du soulign ou biffer des mots.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\usepackage[normalem]{ulem}
+\pagestyle{empty}
+\begin{document}
+
+\normalem
+Voici le mode "\emph{emphasize}" classique.
+
+\ULforem
+Voici le mode "\emph{emphasize}" soulign. \emph{Il permet
+galement de grer les retours la ligne tout en restant dans
+le style emphasize.}
+
+Les autres possibilits sont les suivantes~:
+\begin{itemize}
+ \item vagues~: \uwave{texte}
+ \item barr~: \sout{texte}
+ \item ray~: \xout{texte}
+\end{itemize}
+
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : \underline ne permet pas de grer les retours la
+ ligne du fait qu'il encapsule le texte pass en
+ argument dans une bote.
+
+# 6.29 # Comment raliser des onglets ?
+---------------------------------------
+* Pour insrer un carr noir, dcal vers le bas chaque
+nouveau chapitre, le long de la marge des pages de droite d'un
+document, on peut utiliser le package 'fancyhdr' ou
+'fancyheadings'. Ces packages sont disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fancyhdr/ et
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/.
+
+Remarque : On note toutefois qu'il est peu probable qu'une
+ imprimante puisse accder au ras de la marge. La
+ solution consiste alors dfinir un format de
+ document plus petit et utiliser le massicot.
+ Attention dans ce cas lors de la dfinition des
+ marges.
+
+* On peut galement utiliser le package 'onglet' dfini
+ci-dessous par B. Bayart. Celui-ci ncessite le package
+'everyshi' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/everyshi/.
+
+%%%% debut macro %%%%
+\ProvidesPackage{onglet}[1996/07/25 B. Bayart]
+\RequirePackage{everyshi}
+
+\newcounter{maxchapter}
+\newcounter{tmpa}
+\newlength{\basehauteur}
+\setlength{\basehauteur}{1cm}
+\newlength{\ajoutdroite}
+\newlength{\htcclv}
+\def\concatener{%
+ \setlength{\ajoutdroite}{\textheight}
+ \divide\ajoutdroite by \basehauteur
+ \setcounter{maxchapter}{\number\ajoutdroite}
+ \setcounter{tmpa}{\value{chapter}}
+ \addtocounter{tmpa}{-1}
+ \divide\value{tmpa} by\value{maxchapter}
+ \multiply\value{tmpa} by\value{maxchapter}
+ \advance\value{tmpa} by -\value{chapter}
+ \addtocounter{tmpa}{-1}
+ \setlength{\ajoutdroite}{\paperwidth}
+ \setlength{\htcclv}{\ht255}
+ \addtolength{\ajoutdroite}{-\wd255}
+ \addtolength{\ajoutdroite}{-1in}
+ \addtolength{\ajoutdroite}{-1.5cm}
+ \setbox255=\vbox{\hbox to \wd255{%
+ \box255%\relax
+ \rlap{\vbox to \htcclv{%
+ \vskip-\value{tmpa}\basehauteur
+ \hbox{%
+ \hskip\ajoutdroite\relax
+ \usebox{\laboite}%
+ }%
+ \vfill
+ }}%
+ \hfill}}%
+}
+\newsavebox{\laboite}
+\def\faireboite{\sbox{\laboite}%
+{\hbox to 1.5cm{\let\protect\relax
+\huge\thechapter\hfill\vrule height 1em depth 0pt width 5mm}}}
+
+\AtBeginDocument{\EveryShipout{\faireboite\concatener}}
+\endinput
+%%%% fin macro %%%%
+
+# 6.30 # Comment raliser des QCM ?
+-----------------------------------
+Il existe le package 'exam' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/exams/. Ce package permet
+entre autres de paramtrer les questions de manire ce que les
+propositions apparassent dans un ordre alatoire.
+
+Exemple :
+Combien le cheval possde t'il de pattes ?
+\begin{choice}[\random]
+ \baditem{deux pattes}
+ \baditem{quatres pattes}
+ \baditem{zro patte}
+\end{choice}
+%%%% fin exemple %%%%
+
+# 6.31 # Comment modifier l'orientation des flottants ?
+-------------------------------------------------------
+* Le package 'rotating' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/rotating/ offre deux
+environnements sidewaysfigure pour les figures et sidewaystable
+pour les tableaux. Les figures ou tableaux sont alors insrs sur
+une page spare.
+
+Exemple :
+\begin{sidewaystable}
+ \begin{tabular}{|c|c|}
+ \hline
+ Un & Deux \\
+ Trois & Quatre \\
+ \hline
+ \end{tabular}
+\end{sidewaystable}
+%%%% fin exemple %%%%
+
+* On peut galement utiliser l'environnement sideways du
+package 'rotating'. De la mme manire cet environnement gnre
+une page spare.
+
+Exemple :
+\begin{figure}
+ \begin{sideways}
+ \includegraphics{foobar.ps}
+ \end{sideways}
+\end{figure}
+%%%% fin exemple %%%%
+
+Remarque : il est frquent que les visualiseurs de fichiers dvi
+ ne sachent pas grer les changements d'orientation
+ l'intrieur d'un document. Il faut pour voir le
+ rsultat dfinitif utiliser un visualiseur de
+ postscript.
+
+# 6.32 # Comment faire rfrence plusieurs fois la mme note de bas de page ?
+-------------------------------------------------------------------------------
+* Il faut utiliser les commandes \footnotemark[] et
+\footnotetext[]{}. \footnotemark permet de grer le compteur de
+notes et \footnotetext permet d'insrer le texte correspondant
+en bas de page.
+
+Exemple :
+bla blabla\footnotemark[1] bla bla bla blablabla\footnotemark[2]
+bla bla bla bla blabla\footnotemark[1] bla.
+
+\footnotetext[1]{double bla}
+\footnotetext[2]{triple bla}
+%%%% fin exemple %%%%
+
+* Avec french, on peut utiliser la commande \refmark.
+
+Exemple :
+le vrai appel\footnote{C'est une note en bas de
+page\label{manote}} et le deuxieme appel\refmark{manote}
+%%%% fin exemple %%%%
+
+Remarque : Si vous n'utilisez pas french, cette macro \refmark
+ est dcrite dans le cahier Gutenberg numro 15, avril
+ 1993, page 52. Ce cahier est accessible l'URL :
+ http://www.gutenberg.eu.org/publications/.
+
+# 6.33 # Comment viter les orphelins en dbut ou fin de page ?
+---------------------------------------------------------------
+* Il suffit d'ajouter les lignes :
+%%%% debut macro %%%%
+\widowpenalty=10000
+\clubpenalty=10000
+\raggedbottom
+%%%% fin macro %%%%
+dans le prambule du document.
+
+* Pour agir localement, on peut galement utiliser la commande
+\enlargethispage (cf. question 6.11).
+
+# 6.34 # Comment dfinir de nouveaux flottants ?
+------------------------------------------------
+Le package 'float' de G. Williams, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/float/, permet de dfinir
+de nouveaux objets flottants. Il dfinit notamment des
+environnements permettant d'encadrer des objets ou de les sparer
+du reste du texte par des lignes horizontales.
+
+Exemple :
+\documentclass[11pt]{report}
+\usepackage{float}
+\usepackage{french}
+
+\floatstyle{ruled} % pour que mes flottants soient spars du
+ % texte par des lignes.
+\newfloat{important}{htbp}{loi}[section]
+ % important est le nom de mon nouvel environnement
+ % htbp sont les options de placement de mon flottant
+ % loi est l'extension du fichier qui sera utilise pour
+ % construire la liste de mes flottants
+ % section est le niveau duquel dependra la numerotation
+ % de mes flottants
+\floatname{important}{Important} % titre du caption
+
+\begin{document}
+
+\listof{important}{Liste des textes importants.} % titre de la
+ % liste de mes flottants.
+
+\chapter{Rgles de bases.}
+
+\section{Hommes clbres.}
+
+ Parmi les citations des hommes clbres dans le domaine que
+ nous tudions actuellement, il faut retenir celle de M.
+ Maxime rappele dans le cadre~\ref{imp-max}.
+
+ \begin{important}
+ M. Maxime a dit un jour~:
+ \begin{quote}
+ Chacun doit se faire ses propres raisons.
+ \end{quote}
+ \caption{Adage de M. Maxime.}
+ \end{important}
+
+ Notez que~\ldots
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.35 # Comment utiliser la commande \caption hors d'un environnement flottant ?
+---------------------------------------------------------------------------------
+* Pour pouvoir attacher un titre de style table un
+environnement non flottant (i.e. autre que figure ou table), il
+faut dfinir :
+%%%% debut macro %%%%
+\makeatletter
+\def\@captype{table}
+\makeatother
+%%%% fin macro %%%%
+
+Exemple :
+Texte sur les couleurs.
+
+\begin{itemize}
+ \item rouge
+ \item vert
+ \item bleu
+\end{itemize}
+\caption{Liste des couleurs primaires.}
+
+Texte.
+%%%% fin exemple %%%%
+
+* La macro suivante propose une autre possibilit pour obtenir
+un titre de style table :
+%%%% debut macro %%%%
+\makeatletter
+\def\captionof#1#2{{\def\@captype{#1}#2}}
+\makeatother
+%%%% fin macro %%%%
+
+Exemple :
+\begin{document}
+un texte
+
+\captionof{table}{\caption{un titre ici}\label{foo}}
+
+un autre texte
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'capt-of' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ dfinit la commande
+\captionof.
+
+# 6.36 # Comment encadrer un objet flottant ?
+---------------------------------------------
+* Il faut utiliser le package 'float' qui dfinit le style
+boxed. Ce package est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/float/. Voir la question
+6.34 pour un exemple plus complet.
+
+Exemple :
+Dans le prambule :
+\floatstyle{ruled}
+\newfloat{nom-flottant}{placement}{ext-fic}[numerotation]
+dans le corps du document :
+\begin{nom-flottant}
+
+\end{nom-flottant}
+%%%% fin exemple %%%%
+
+* Si le titre accompagnant le flottant peut tre l'extrieur
+du cadre dsir, on peut alors utiliser \fbox dans la
+dclaration du flottant.
+
+Exemple :
+\begin{table}
+ \begin{center}
+ \fbox{
+ \begin{tabular}{cll}
+ &1 case & 2 cases \\
+ &3 cases & 4 cases \\\hline
+ Total~: & 4 cases & 6 cases \\
+ \end{tabular}
+ }
+ \end{center}
+ \caption{Titre extrieur.}
+\end{table}
+%%%% fin exemple %%%%
+
+* M. Loreti propose galement le package 'bigbox' ci-dessous :
+%%%% debut macro %%%%
+% I like to put boxes around all of my figures and algorithms in
+% reports, and finally came up with my 'bigbox' environment. It
+% makes a box as wide as the current text and sets the stuff
+% inside with a narrower width.
+%
+% USAGE:
+%
+% \begin{figure} (or {table}, or {center}, or ...)
+% \begin{bigbox}
+% \begin{tabbing}
+% ...
+% \end{tabbing}
+% \end{bigbox}
+% \caption{XXX}
+% \end{figure}
+%
+%%% BIGBOX - environment
+%%%
+%%% TOM SHEFFLER
+%%% Carnegie Mellon, Aug 1990
+%%%
+%%% Make an environment for boxing a figure and setting it in
+%%% a narrower width.
+\newdimen\boxfigwidth % width of figure box
+
+\def\bigbox{\begingroup
+ % Figure out how wide to set the box in
+ \boxfigwidth=\hsize
+ \advance\boxfigwidth by -2\fboxrule
+ \advance\boxfigwidth by -2\fboxsep
+ \setbox4=\vbox\bgroup\hsize\boxfigwidth
+ % Make an invisible hrule so that the box is exactly this wide
+ \hrule height0pt width\boxfigwidth\smallskip%
+% Some environments like TABBING and other LIST environments
+% use this measure of line size - \LINEWIDTH=\HSIZE-\LEFTMARGIN-\RIGHTMARGIN?
+ \linewidth=\boxfigwidth
+}
+\def\endbigbox{\smallskip\egroup\fbox{\box4}\endgroup}
+%%%% fin macro %%%%
+
+Exemple :
+\documentclass[11pt]{report}
+\usepackage{graphics}
+\usepackage{bigbox}
+\usepackage{french}
+\pagestyle{empty}
+\begin{document}
+
+\begin{figure}
+ \begin{bigbox}
+ \includegraphics{../foobar.ps}
+ \end{bigbox}
+ \caption{Dessin.}
+\end{figure}
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.37 # Comment changer l'orientation d'un caption ?
+-----------------------------------------------------
+La commande \rotcaption fournie avec le package 'rotating'
+permet de changer l'orientation d'un caption.
+
+Exemple :
+\begin{figure}
+ \centering
+ \begin{minipage}[c]{1in}
+ \includegraphics[angle=90,width=\linewidth]{coco.ps}
+ \end{minipage}
+ \begin{minipage}
+ \rotcaption{Ma jolie figure coco}
+ \label{coco}
+ \end{minipage}
+\end{figure}
+%%%% fin exemple %%%%
+
+# 6.38 # Comment mettre en page un programme ?
+----------------------------------------------
+Les packages 'program' (disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/program/) et 'programs'
+permettent de mettre en reliefs des mots cls, d'utiliser des
+mathmatiques dans des algorithmes, etc.
+
+# 6.39 # Comment inclure le source d'un programme ?
+---------------------------------------------------
+Les packages 'lgrind' et 'listings' rpondent la question
+(disponibles sur ftp://ftp.fdn.org/pub/CTAN/support/lgrind/ et
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/listings/). Ils
+reconnaissent tous les 2 peu prs 40 langages diffrents.
+
+Le premier est compos d'un excutable, 'lgrind' qui permet de
+transformer le source en question, par exemple, monfichier.c, en
+monfichier.tex, que l'on inclut directement dans son fichier
+LaTeX, l'aide d'une commande approprie. L'inconvnient, est
+qu'videmment, il y a un fichier .tex qui est gnr en plus.
+
+Notes : - utiliser au-moins la version 3.6 ;
+ - on peut paramtrer lgrind avec le fichier lgrindef. Par
+ dfaut, l'auteur a jug utile de transformer la lettre
+ en $\alpha$. Il suffit donc de commenter cette
+ option la fin de ce fichier pour viter cela.
+
+Le deuxime ne ncessite pas de recompilation. On inclut
+directement le source, avec une commande adquate. Avec ce
+package, on peut mme dfinir son propre langage, le faire
+hriter d'un autre langage, avec des mots-cls spcifiques, etc.
+
+ noter que, moyennant quelques paramtres ajouter, il est tout
+ fait possible de faire en sorte que ces packages reconnaissent
+les fontes 8 bits. On peut lui faire comprendre par exemple, que
+lorsqu'il rencontre le caractre , il le transforme en
+$\mathonesuperior$.
+
+# 6.40 # Comment obtenir un espace inscable ?
+----------------------------------------------
+Le caractre ~ est interprt par LaTeX et permet d'obtenir un
+espace inscable.
+
+Exemple :
+Comme le montre l'exemple suivant~: $a + 2 = 0$.
+%%%% fin exemple %%%%
+
+# 6.41 # Comment insrer une page blanche ?
+-------------------------------------------
+* Pour forcer LaTeX laisser une page blanche dans un document,
+il faut utiliser successivement les trois commandes :
+\newpage
+\strut ou ~ ou \mbox{} ou \null
+\newpage
+
+Le principe est qu'il y ait quelque chose d'invisible sur la
+page blanche pour que LaTeX la prenne en compte.
+
+# 6.42 # Comment supprimer l'indentation des paragraphes ?
+----------------------------------------------------------
+* \noindent au dbut du texte permet de ne pas indenter un
+paragraphe.
+
+* Pour systmatiquement supprimer l'indentation du premier
+paragraphe d'une section par exemple, il faut redfinir la
+commande \section. Il faut que le 4me paramtre de
+\@startsection soit une distance ngative, pour qu'il n'y ait
+pas de retrait au premier paragraphe du texte qui suit :
+
+%%%% debut macro %%%%
+\makeatletter
+\renewcommand\section{\@startsection {section}{1}{\z@}%
+ {-3.5ex \@plus -1ex \@minus -.2ex}%
+%%%%%% ^^^^ (4eme parametre)
+ {2.3ex \@plus.2ex}%
+ {\normalfont\Large\bfseries}}
+\makeatother
+%%%% fin macro %%%%
+
+# 6.43 # Comment modifier l'espacement entre caractres ?
+---------------------------------------------------------
+* Le package 'letterspace' permet de modifier l'espacement entre
+mots ou caractres.
+
+* Le package 'trackin' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/tracking/ permet de jouer sur
+les espacements dans les mots ou les phrases pour les ajuster
+dans une longueur spcifie.
+
+# 6.44 # Comment supprimer certaines coupures de mots ?
+-------------------------------------------------------
+* Pour agir sur un mot particulier, il faut utiliser la commande
+\hyphenation.
+
+Exemple :
+Visualisation des coupures :
++\showhyphens{mousehole AlGaAs GaAs GaInP AlInP}
+
+ Underfull \hbox (badness 10000) detected at line 0
+ [] \OT1/cmr/m/n/10 mouse-hole Al-GaAs GaAs GaInP Al-InP
+
+Interdiction de certaines coupures :
++\hyphenation{AlGaAs GaAs GaInP AlInP}
++\showhyphens{mousehole AlGaAs GaAs GaInP AlInP}
+
+ Underfull \hbox (badness 10000) detected at line 0
+ [] \OT1/cmr/m/n/10 mouse-hole AlGaAs GaAs GaInP AlInP
+%%%% fin exemple %%%%
+
+* Moins propre mais tout aussi efficace, on peut inclure le mot
+ ne pas couper dans une hbox.
+
+Exemple :
+Mme quand il est en bout de ligne ce mot trs long n'est pas
+coup CeMotTrsLongNestPasCoup.
+
+Mme quand il est en bout de ligne ce mot trs long n'est pas
+coup \hbox{CeMotTrsLongNestPasCoup}.
+%%%% fin exemple %%%%
+
+* Pour empcher LaTeX de couper les mots dans un paragraphe il
+suffit de l'encadrer par les commandes \begin{sloppypar} et
+\end{sloppypar}.
+
+* Pour empcher LaTeX de couper les mots dans tout un document,
+il faut utiliser la commande \sloppy dans le prambule du
+document. On peut galement utiliser la dclaration :
+\hyphenpenalty 10000.
+
+* De manire globale, on peut aussi dclarer :
+\DeclareFontFamily{T1}{cmr}{\hyphenchar\font=-1}
+
+* Pour interdire la coupure de tous les mots commenant par une
+majuscule, il faut utiliser : \uchyph=0 dans le prambule du
+document.
+
+* On peut galement interdire la coupure des mots d'une langue
+particulire dans un document multilingues en utilisant l'astuce
+suivante : il suffit de crer un fichier de motifs de csures
+vide, par exemple pour le russe
+%%%% debut macro %%%%
+%%% ruhyph.tex %%%
+\patterns{}
+\endinput
+%%%%%%%%%%%%%%%%%%%
+%%%% fin macro %%%%
+et dans le fichier language.dat ajouter la ligne
+russian ruhyph.tex
+
+# 6.45 # Comment mettre en forme des quations chimiques ?
+----------------------------------------------------------
+* Le package 'ppchtex' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/context/ permet d'crire des formules chimiques.
+
+* Sur Mac ou PC, il existe MDL qui est une version freeware
+d'ISIS Draw qui permet de crer ses propres structures et de les
+sauver sous format eps. Pour plus de dtails, consulter
+http://www.mdli.com/prod/ioffer.html.
+
+* Il existe le package 'chemsym' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/chemsym/.
+
+* Le package 'XymTex' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/xymtex/ ou
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/xymtex/ permet de dfinir des
+structures chimiques.
+
+Remarques (F. Jacquet) :
++ XyMTeX est incompatible avec le package french de B. Gaulle.
+Pour utiliser les deux dans un mme document, il suffit de
+repasser en mode \english avant la macros puis \french aprs. Je
+ne sais pas comment cela fonctionne pour les \caption mais en
+thorie, a devrait marcher !
+AL: Vrifier la ralit de cette remarque par rapport au dernier french.
++ XyMTeX possde le gros dfaut de ne pas pouvoir faire de
+longues chanes aliphatiques si on ne sait pas programmer le
+nombre de points entre deux structures. Le plus simple dans ce
+cas est donc l'emploi de Xfig (ou autre).
++ On ne peut pas imbriquer les formules, ce qui gne
+considrablement son utilisation; en revanche, pour les
+cholestrol l'ensemble est trs puissant !
+
+# 6.46 # Comment mettre en page un calendrier ?
+-----------------------------------------------
+* Le package 'termcal' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/termcal/ permet de mettre
+en page un calendrier. Il permet de prciser quels jours doivent
+apparatre et d'insrer du texte soit rgulirement certaines
+dates soit des dates particulires.
+
+* Le package 'calendar ' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/plain/contrib/ propose un ensemble de macros pour
+mettre en page des calendriers.
+
+* Un autre package 'calendar' est galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/calendar/.
+
+* Il existe galement le package 'yplan97' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/yplan97/.
+
+# 6.47 # Comment forcer un caption sur plusieurs lignes ?
+---------------------------------------------------------
+Pour forcer un retour la ligne dans un caption, il faut
+utiliser \caption[text1]{text2 \\\hspace{\linewidth} text3}.
+
+Remarque : text1 est le texte qui apparatra dans la liste des
+figures ou des tableaux.
+
+# 6.48 # Comment gnrer des barres de modification dans un document ?
+----------------------------------------------------------------------
+Il suffit d'utiliser le package 'changebar' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/changebar/.
+
+Exemple :
+dans le prambule :
+\usepackage[outerbars]{changebar} % permet de positionner les
+ % barres en marge externe
+\setcounter{changebargrey}{20} % permet de fixer le niveau de
+ % gris des barres
+
+et dans le document :
+\begin{changebar}
+ texte..
+\end{changebar}
+
+ou
+
+ancien texte ancien texte ancien texte \cbstart nouveau
+texte nouveau texte nouveau texte \cbend ancien texte ancien
+texte ancien texte ancien texte
+%%%% fin exemple %%%%
+
+# 6.49 # Comment encadrer du texte verbatim ?
+---------------------------------------------
+* Le package 'moreverb' propose un environnement encadr.
+
+Exemple : \begin{boxedverbatim} La commande \LaTeX permet
+d'appeler le logo
+ LaTeX.
+\end{boxedverbatim}
+%%%% fin exemple %%%%
+
+# 6.50 # Comment crire du texte en forme de losange ou autre ?
+---------------------------------------------------------------
+Le package 'shapepar' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ dfinit des
+environnements losange, coeur, etc.
+
+Exemple :
+\diamondpar{mon paragraphe en forme de losange.}
+%%%% fin exemple %%%%
+
+# 6.51 # Comment isoler les flottants par un trait horizontal ?
+---------------------------------------------------------------
+* Pour que les flottants qui sont renvoys en dbut
+(respectivement en fin) de page soient isols du texte par un
+trait horizontal en dessous (respectivement au dessus), il faut
+activer les options suivantes dans le prambule du document :
+\let\topfigrule\hrule
+\let\botfigrule\hrule
+
+* Si leur comportement n'est pas satisfaisant, on peut le
+redfinir :
+\newcommand{\topfigrule}{%
+ \vspace*{3pt}\noindent\rule{\linewidth}{0.4pt}\vspace{-3.4pt}}
+\newcommand{\botfigrule}{%
+ \vspace*{3pt}\noindent\rule{\linewidth}{0.4pt}\vspace{-3.4pt}}
+
+# 6.52 # Comment insrer un espace vertical dans une page ?
+-----------------------------------------------------------
+Il suffit d'utiliser la commande \vspace et de prciser en
+argument la hauteur de l'espace voulu.
+
+Exemple :
+Texte avant.
+
+\vspace{2cm}
+
+Texte aprs.
+%%%% fin exemple %%%%
+
+Remarque : la commande \vspace* force l'insertion d'un espace
+ vertical mme si ce dernier se situe sur un
+ changement de page.
+
+# 6.53 # Comment insrer un espace horizontal dans un texte ?
+-------------------------------------------------------------
+De la mme manire que pour les espaces verticaux, il existe la
+commande \hspace pour insrer un espace horizontal dans un
+texte.
+
+Exemple :
+blabla bla \hspace{3cm} bli bli bli
+%%%% fin exemple %%%%
+
+Remarque : la commande \hspace* force l'insertion d'un espace
+ mme en dbut ou en fin de ligne.
+
+# 6.54 # Comment dfinir un style de paragraphe ?
+-------------------------------------------------
+* Pour agir de manire globale (sur tout le document), les
+paramtres de dfinition d'un paragraphe sont :
++ \parindent pour fixer la longueur des indentations
++ \parskip pour grer l'espace entre les paragraphes.
+
+Exemple :
+\setlength{\parindent}{1cm}
+\setlength{\parskip}{1ex plus 0.5ex minus 0.2ex}
+%%%% fin exemple %%%%
+
+* Pour forcer (supprimer) localement l'indentation d'un
+paragraphe, il existe la commande \(no)indent.
+
+# 6.55 # quoi sert la commande \stretch ?
+-------------------------------------------
+La commande \stretch{x} permet d'insrer un espace lastique qui
+va s'ajuster de manire forcer l'occupation de toute une
+ligne (en mode horizontal) ou de toute une page (en mode
+vertical). Le paramtre x est appel facteur d'lasticit, il
+intervient ds que plusieurs commandes \stretch sont appeles
+sur la mme ligne.
+
+Exemples :
++ bla\hspace{\stretch{1}} bla bla \hspace{\stretch{2}} bla bla
+bla
+
++ un texte normal \vspace{\stretch{1}} et un texte qui finit de
+remplir la ligne courante et qui se poursuit tout en bas de la
+page sur la dernire ligne.
+%%%% fin exemple %%%%
+
+# 6.56 # Comment justifier un paragraphe gauche ou droite ?
+---------------------------------------------------------------
+* Les environnements flushleft et flushright permettent de
+justifier gauche ou droite une portion de texte.
+
+Exemple :
+\begin{flushleft}
+ Texte align gauche. Texte align gauche. Texte align
+ gauche. Texte align gauche. Texte align gauche. Texte
+ align gauche. Texte align gauche. Texte align
+ gauche. Texte align gauche. Texte align gauche. Texte
+ align gauche.
+\end{flushleft}
+%%%% fin exemple %%%%
+
+* Il existe galement les commandes \raggedright et \raggedleft.
+
+Exemple :
+{\raggedleft
+Colle droite. Colle droite. Colle droite. Colle droite.
+Colle droite. Colle droite. Colle droite.
+
+Colle droite. Colle droite. Colle droite. Colle droite. Colle
+droite. Colle droite. }
+%%%% fin exemple %%%%
+
+* Le package 'ragged2e' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/ragged2e/ offre en plus des
+commandes (\Centering, \RaggedLeft, et \RaggedRight) et des
+environnements qui permettent de mieux grer les csures.
+
+# 6.57 # Comment mettre en page des citations ?
+-----------------------------------------------
+Il existe deux environnements de gestion des citations :
++ quote pour les citations courtes,
++ quotation pour les citations longues.
+
+Exemple :
+\begin{quote}
+ L'environnement \texttt{quote} n'indente pas ces paragraphes
+ par contre l'espace vertical entre ces derniers est suprieur
+ celui d'un texte standard.
+
+ La preuve~!
+\end{quote}
+
+\begin{quotation}
+ L'environnement \texttt{quotation} indente la premire ligne
+ de ses paragraphes et spare ses paragraphes d'un espace
+ vertical standard.
+
+ La preuve~!
+
+\end{quotation}
+
+Dans les deux cas les marges droite et gauche sont plus
+importantes que celles d'un texte standard.
+%%%% fin exemple %%%%
+
+# 6.58 # Comment insrer un texte sans que LaTeX le mette en forme ?
+--------------------------------------------------------------------
+L'environnement verbatim permet d'insrer un texte tel quel sans
+que LaTeX ne le traite. Il permet notamment de faire apparatre
+des commandes LaTeX.
+
+Exemple :
+\begin{verbatim}
+ La commande \LaTeX permet d'imprimer le logo LaTeX.
+\end{verbatim}
+%%%% fin exemple %%%%
+
+* La commande \verb?texte? permet de faire la mme chose
+localement. Le premier caractre ? permet de marquer le dbut du
+mode verbatim et le second en marque la fin. Il peut tre
+remplac par n'importe quel autre caractre sauf un espace ou *.
+
+# 6.59 # Comment visualiser des espaces ?
+-----------------------------------------
+* L'environnement verbatim* et la commande \verb* permettent de
+visualiser les espaces insrs dans un texte en les remplaant
+par un caractre spcial en forme de u.
+
+Exemple :
+Je mange \verb*? ? pomme.
+%%%% fin exemple %%%%
+
+* LaTeX propose la commande \textvisiblespace.
+
+* En TeX, c'est le caractre 32 de la fonte cmtt, qui est
+dfini dans le source du TeXBook par :
+\def\]{\leavevmode\hbox{\tt\char`\ }} % visible space
+
+Vous pouvez donc dfinir:
+\def\vs{\leavevmode\hbox{\tt\char`\ }} % visible space
+et \vs donnera ce fameux caractre.
+
+# 6.60 # Comment insrer du code LaTeX dans un document LaTeX ?
+---------------------------------------------------------------
+* Le package 'example' offre un environnement example qui permet en
+ne tapant qu'une seule fois le code d'avoir cte cte le code
+LaTeX et son rsultat aprs compilation.
+
+Exemple :
+\begin{example}
+ La commande \LaTeX permet d'appeler le logo LaTeX.
+\end{example}
+%%%% fin exemple %%%%
+
+* La solution la plus classique consiste faire :
+\hbox{\vtop{\hsize 0.5\hsize le permier texte}\vtop{\hsize
+0.5\hsize{\begin{verbatim} le mme texte \end{verbatim}}}}
+
+# 6.61 # Comment crire du texte en couleurs ?
+----------------------------------------------
+* Voir ce sujet le Cahier GUTenberg numro 16 (fvrier 1994,
+entirement consacr ce problme) et l'article de M. Goossens
+et M. Jouhet dans Cahier GUTenberg 21 (juin 1995, pages 30-52),
+accessible l'URL :
+http://www.gutenberg.eu.org/publications/.
+
+* Le package 'color' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/. Il permet de coloriser le
+texte ou le fond du document.
+
+Exemple :
+\textcolor{red}{Important}
+%%%% fin exemple %%%%
+
+* pstricks disponible sur ftp://ftp.fdn.org/pub/CTAN/graphics/pstricks/ est un
+ensemble de macros PostScript compatibles avec Plain
+TeX, LaTeX, AmSTeX, and AmS-LaTeX. Il comprend notamment
+des macros pour la colorisation, la gestion des graphiques, le
+dessin de camembert, d'arbres, etc.
+
+* Voir galement la question 6.25 : Comment griser le fond
+(background) d'un paragraphe ?
+
+# 6.62 # Comment construire un arbre ?
+--------------------------------------
+* Le package 'qobitree', est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/qobitree/.
+
+* Le package 'treesvr' est galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/treesvr/.
+
+Exemple :
+\begin{picture}(100,100)
+\setlength\unitlength{2mm}
+\branchlabels ABC % 012 is the default
+\root(2,10) 0. % root at absolute coordinate (2,10)
+ % its (internally used) label is 0
+ % the space before the 0 obligatory
+\branch2{16} 0:1,2. % node 0 has children 1 and 2
+ % the text "16" is written above it
+ % space optional, :,. obligatory
+\leaf{4}{$u_1$} 1. % node 1 is a leaf
+ % "4" written above, "$u_1$" at right
+\branch2{12} 2:3,7. % branch to node 3 goes up labeled A
+ \tbranch2{9} 3:4,5,6.
+ \leaf{4}{$u_3$}4.
+ \leaf{3}{$u_4$}5.
+ \leaf{2}{$u_5$}6.
+ \leaf{3}{$u_2$} 7.
+\end{picture}
+%%%% fin exemple %%%%
+
+* Le package 'treetex' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/trees/tree_tex/ permet de metttre en
+page des arbres sous LaTeX.
+
+* Les packages 'epic', 'eepic', 'ecltree' permettent de crer des
+arbres (les trois packages sont ncessaires pour une
+utilisation avec Latex2e pour garder la compatibilit avec
+Latex2.09).
+
+Exemple :
+\documentstyle[epic,eepic,ecltree]{article}
+\begin{document}
+
+\begin{bundle}{racine}
+\chunk{feuille 1}
+\chunk{feuille 2}
+\drawwith{\dottedline{3}}
+\chunk{feuille 3}
+\drawwith{\drawline}
+\chunk{feuille 4}
+\end{bundle}
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.63 # Comment mettre en page un pome ?
+------------------------------------------
+* Il existe l'environnement verse. Il gre les marges, les
+retours la ligne dans une strophe se font par \\ et les
+strophes sont spares par des lignes blanches.
+
+Exemple:
+\begin{verse}
+ J'ai un poney gris, \\
+ Qui galope travers la prairie.
+
+ Grignote, grignote dans ma main, \\
+ La carotte rousse du jardin.
+
+ Mes cousins ont un poney blanc, \\
+ Qui parcourt chemins et champs.
+\end{verse}
+%%%% fin exemple %%%%
+
+* Ci-dessous un exemple de style de JHB Nijhof
+(nijhojhb@aston.ac.uk) :
+
+Exemple :
+\documentstyle[a4,12pt]{article}
+
+\def\testline{\par\noindent\hbox to 0pt{\hss*\hss}\hfill
+\hbox to 0pt{\hss*\hss}\hfill\hbox to 0pt{\hss*\hss}\par}
+\def\centerstar{\par\medskip\noindent\hbox to\hsize%
+{\hss*\hss}\par\medskip}
+
+\newbox\poembox
+\newbox\widebox
+\newdimen\centerx
+\newcount\linecount
+\newdimen\poemleftmargin
+\def\newpoem{\setbox0=\box\poembox \setbox0=\box\widebox
+\linecount=0} % empty boxes
+\newpoem % probably not necessary
+\def\poemline#1{\setbox0=\hbox{\strut #1}%
+ \setbox\poembox=\vbox{\unvbox\poembox\copy0}%
+ \setbox\widebox=\hbox{\unhbox\widebox\copy0}%
+ \advance \linecount 1}
+\def\setpoem{% you'll want a clearpage here
+\centerx=\wd\widebox \divide\centerx\linecount \divide\centerx 2%
+%now centerx is the x of the center of gravity
+\poemleftmargin=0.5\hsize \advance \poemleftmargin-\centerx
+\noindent\kern\poemleftmargin\box\poembox
+\par
+\newpoem}
+
+\begin{document}
+
+\testline % for viewing the margins/ middle
+\poemline{Rozen verwelken}
+\poemline{schepen vergaan}
+\poemline{maar onze liefde}
+\poemline{zal blijven bestaan}
+\setpoem
+
+\centerstar
+
+\poemline{Rozen verwelken}
+\poemline{schepen vergaan}
+\poemline{maar onze liefde zal blijven bestaan}
+\setpoem
+
+\centerstar
+
+\poemline{Rozen verwelken, schepen vergaan}
+\poemline{maar onze liefde zal blijven bestaan}
+\setpoem
+
+\centerstar
+
+\poemline{Rozen verwelken}
+\poemline{\qquad schepen vergaan}
+\poemline{maar onze liefde}
+\poemline{\qquad zal blijven bestaan}
+\setpoem
+
+\centerstar
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.64 # Comment aligner des paragraphes ?
+------------------------------------------
+On peut utiliser la commande \parindent.
+
+Exemple :
+{\settowidth{\parindent}
+{Notes~:\ }
+
+\makebox[0pt][r]
+{Notes~:\ }La premire note pour dire que ...
+
+La seconde pour prciser que ...
+}
+%%%% fin exemple %%%%
+
+# 6.65 # Comment construire une liste d'lments ?
+--------------------------------------------------
+Il existe trois environnements de liste par dfaut :
++ l'environnement itemize
++ l'environnement description
++ l'environnement enumerate
+
+Exemples :
+\begin{itemize}
+ \item un lment
+ \item un autre lment
+\end{itemize}
+
+\begin{description}
+ \item[Genre] Le genre peut tre fminin ou masculin
+ \item[Nombre] Le nombre peut tre singulier ou pluriel
+\end{description}
+
+\begin{enumerate}
+ \item premier lment
+ \item deuxime lment
+\end{enumerate}
+%%%% fin exemple %%%%
+
+# 6.66 # Comment faire une note dans une marge ?
+------------------------------------------------
+On peut utiliser la commande \marginpar{note marge}.
+
+Exemple :
+La valeur du paramtre temps est fixe
+12~minutes\marginpar{AC}. En tenant compte de cette hypothse
+les rsultats obtenus sont les suivants~:
+
+~\ldots
+%%%% fin exemple %%%%
+
+Remarque : Pour inverser les notes dans les marges
+ (droite/gauche) il suffit de mettre dans le
+ prambule : \reversemarginpar.
+
+# 6.67 # Comment faire une page de garde ?
+------------------------------------------
+Les commandes permettant de dfinir une page de garde sont :
++ \title pour un titre
++ \author pour le ou les auteurs (dans ce dernier cas leurs noms
+sont spars par la commande \and)
++ \date pour la date
++ \thanks utilise dans l'une des commandes ci-dessus permet de
+faire rfrence une note de bas de page.
+
+La page de garde est ensuite gnre par la commande \maketitle
+appele dans le corps du document (gnralement juste aprs la
+balise \begin{document}).
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+
+\newlength{\larg}
+\setlength{\larg}{14.5cm}
+
+\title{
+{\rule{\larg}{1mm}}\vspace{7mm}
+\begin{tabular}{p{4cm} r}
+ & {\Huge {\bf {FAQ} \LaTeX{} franaise}} \\
+ & \\
+ & {\huge Pour dbutants et confirms}
+\end{tabular}\\
+\vspace{2mm}
+{\rule{\larg}{1mm}}
+\vspace{2mm} \\
+\begin{tabular}{p{11cm} r}
+ & {\large \bf Version 2.0} \\
+ & {\large \today}
+\end{tabular}\\
+\vspace{5.5cm}
+}
+\author{\begin{tabular}{p{13.7cm}}
+Marie-Paule Kluth
+\end{tabular}\\
+\hline }
+\date{}
+
+\begin{document}
+\maketitle
+
+Voici mon document.
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.68 # Comment utiliser \thanks dans chaque titre de chapitre ?
+-----------------------------------------------------------------
+Pour associer des remerciements dans chaque chapitre d'un thse,
+par exemple, il faut dfinir sa propre macro base de
+\footnote.
+
+Exemple (R. Fairbairns) :
+\documentclass{report}
+\usepackage{french}
+
+\newcommand\thankschapter[2]{%
+ % arg 1 is chapter title
+ % arg 2 is `thanks' text
+ \edef\savefootnote{\thefootnote}
+ \renewcommand\thefootnote{\fnsymbol{footnote}}
+ \chapter[#1]{#1\footnote[1]{#2}}
+ \renewcommand\thefootnote{\arabic{footnote}}
+ \setcounter{footnote}{\savefootnote}
+}
+\begin{document}
+\chapter{Prface.}{\textit{Un grand merci M. Nigaudon pour
+avoir accepter de prfacer ce livre.\\}}
+
+Ce livre traitant de \LaTeX,~\ldots
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 6.69 # Comment mettre un rsum et un abstract dans un document ?
+-------------------------------------------------------------------
+* Le package 'french' propose les environnements resume et
+abstract.
+
+Exemple (textes sur la mme page) :
+\documentclass{article}
+\usepackage{french}
+\pagestyle{empty}
+\begin{document}
+\begin{resume} rsum en franais \end{resume}
+ \english
+\begin{abstract} the same in english \end{abstract}
+ \french
+
+ Cet article~\ldots
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : \resume n'est qu'un alias de \abstract.
+
+Exemple (chaque rsum est sur une page spare) :
+\begin{english}
+ \begin{abstract}
+ english text
+ \end{abstract}
+\end{english}
+
+\begin{french}
+ \begin{abstract}
+ Texte franais
+ \end{abstract}
+\end{french}
+%%%% fin exemple %%%%
+
+* Le package 'babel' peut galement tre utilis.
+
+Exemple :
+\usepackage[francais,english]{babel}
+...
+\selectlanguage{francais}
+resume : je parle franais
+....
+\selectlanguage{english}
+abstract : I speak english
+....
+%%%% fin exemple %%%%
+
+* Autre solution qui ne permet toutefois pas d'avoir les deux
+textes sur la mme page :
+
+%%%% debut macro %%%%
+\renewcommand{\abstractname}{Rsum}
+\begin{abstract} rsum en franais \end{abstract}
+\renewcommand{\abstractname}{Abstract}
+\begin{abstract} the same in english \end{abstract}
+%%%% fin macro %%%%
+
+# 6.70 # Comment dfinir de nouvelles couleurs ?
+------------------------------------------------
+Il existe deux repres pour cela :
++ cyan, magent, yellow, black et la commande :
+\definecolor{nouveau_nom}{cmyk}{w,x,y,z}
+\newcmykcolor{le_nom_de_la_couleur}{w x y z}
+avec w,x,y,z entre 0.0 et 1.0
+
++ red,green, blue et la commande :
+\definecolor{nouveau_nom}{rgb}{a,b,c}
+ou : \newrgbcolor{le_nom_de_la_couleur}{a b c}
+avec a,b,c entre 0.0 et 1.0
+
++ il existe galement :
+\newhsbcolor{le_nom_de_la_couleur}{num1 num2 num3}
+qui permet de jouer sur le << hue >>, la saturation et la
+luminosit.
+
+# 6.71 # Comment placer des figures face face en recto-verso ?
+----------------------------------------------------------------
+Dans un document recto-verso, pour s'assurer qu'une figure
+apparaisse sur la page de gauche et une autre sur la page de
+droite en face, il faut utiliser le package 'dpfloat' disponible
+sur: http://weber.u.washington.edu/~fox/tex/dpfloat.html.
+
+# 6.72 # Quelles sont les diffrences entre a4paper et letterpaper ?
+--------------------------------------------------------------------
+L'option a4paper excute :
+ \setlength\paperheight {297mm}
+ \setlength\paperwidth {210mm}
+
+L'option par dfaut est letterpaper qui fait
+ \setlength\paperheight {11in}
+ \setlength\paperwidth {8.5in}
+
+Remarque (J. Kanze) : Il faut remarquer que la diffrence n'est
+ pas norme : les dfauts en mm sont 279x216. En fait,
+ sur le petit test que j'ai fait, les coupures de
+ lignes se trouvaient exactement aux mmes endroits --
+ en revanche, chaque page contenait bien quelques
+ lignes de plus avec a4paper.
+
+# 6.73 # Comment couper une chane de caractres ?
+--------------------------------------------------
+* Pour forcer la coupure d'une chane de caractres, il faut
+utiliser la commande \- l'endroit o la chane doit tre
+coupe.
+
+Exemple :
+Je dcide que le dernier mot de cette ligne soit coup en deux
+ici:~ do\-cumentation. N'est-ce pas beau~?
+%%%% fin exemple %%%%
+
+* Pour indiquer LaTeX comment couper certain mots, on peut
+utiliser la commande \hyphenation.
+
+Exemple :
+\hyphenation{do-cu-ment}
+Je dcide que le dernier mot de cette ligne soit coup en deux
+ici:~ documentation. N'est ce pas beau~?
+%%%% fin exemple %%%%
+
+# 6.74 # Comment modifier l'espace entre une figure et sa lgende ?
+-------------------------------------------------------------------
+Les deux variables qui dfinissent respectivement l'espace avant
+une lgende et l'espace aprs sont : \abovecaptionskip et
+\belowcaptionskip.
+
+Exemple de redimensionnement :
+\setlength\abovecaptionskip{0.25ex}
+%%%% fin exemple %%%%
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part3 b/help/LaTeX-FAQ-francaise/part3
new file mode 100644
index 0000000000..ff8ae0d913
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part3
@@ -0,0 +1,2487 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!news.imp.ch!fr.clara.net!heighliner.fr.clara.net!maredsous.noc.fr.clara.net!victor.teaser.fr!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:18 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - parties 7 a 11
+Message-ID: <faq-fctt-p320010608133118@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p320010501143416@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 2477
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23523 fr.usenet.reponses:20389
+
+Archive-name: fr/faq-latex-francaise/part3
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+================================================================
+[7] GESTION DES TABLEAUX
+================================================================
+
+# 7.1 # Comment faire un tableau ?
+----------------------------------
+En mode texte, il faut utiliser l'environnement tabular. Chaque
+colonne est ensuite dcrite par r, l ou c pour obtenir une
+colonne de texte justifi droite, gauche ou centr. Chaque
+dclaration de colonne peut tre dlimite par une sparation
+verticale : | ou rien. Une ligne horizontale entre deux lignes
+s'obtient par la commande \hline. Le contenu de chaque colonne
+est spar de celui de la suivante par le symbole &. Le
+changement de ligne est obtenu par la commande \\.
+
+Lorsque plusieurs colonnes adjacentes ont la mme dfinition, on
+peut grouper leurs dclarations avec la commande
+*{nb_colonnes}{dclaration}
+
+Exemple :
+\begin{tabular}{|*{2}{c|}l r|}
+ \hline
+ une & deux & trois & quatre \\
+ case centre & encore centre & gauche & droite \\
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.2 # Comment grer les tableaux de plus d'une page ?
+-------------------------------------------------------
+* Le package 'supertabular' permet de grer automatiquement (ou
+presque) les coupures de tableaux. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/supertabular/.
+Il calcule la longueur du tableau chaque \\ et vrifie si la
+fin de page est atteinte. Si oui, il coupe le tableau. Les
+commandes utiliser sont :
++ \tablefirsthead{...} pour dfinir le contenu de la premire
+occurrence de la tte du tableau. Cette commande est optionnelle.
++ \tablehead{...} pour dfinir le contenu de la tte des
+tableaux suivants.
++ \tabletail{...} dfinit le contenu de la ligne qui doit tre
+ajoute avant une coupure
++ \tablelasttail{...} dfinit le contenu de la dernire ligne
+du tableau. Cette commande est optionnelle.
++ \topcaption{...}, \bottomcaption{...} et \tablecaption{...}
+permettent de nommer un tableau soit au dbut ou la fin du
+tableau. \tablecaption{...} est l'option par dfaut.
+
+Exemple :
+\begin{center}
+ \tablefirsthead{\hline \multicolumn{1}{|c}{Nombre}
+ & \multicolumn{1}{c}{Nombre$^2$}
+ & Nombre$^4$
+ & \multicolumn{1}{c|}{Nombre!} \\ \hline}
+ \tablehead{\hline \multicolumn{4}{|l|}{\small\sl continued
+ from previous page}\\
+ \hline \multicolumn{1}{|c}{ Nombre}
+ & \multicolumn{1}{c}{Nombre$^2$}
+ & Nombre$^4$
+ & \multicolumn{1}{c|}{Nombre!} \\ \hline}
+ \tabletail{\hline\multicolumn{4}{|r|}{\small\sl Suite page
+ suivante~\ldots}\\\hline} \tablelasttail{\hline}
+ \bottomcaption{Fin.}
+ \par
+ \begin{supertabular}{| r@{\hspace{6.5mm}}|
+ r@{\hspace{5.5mm}}| r | r|}
+ 1 & 1 & 1 & 1 \\
+ 2 & 4 & 16 & 2 \\
+ 3 & 9 & 81 & 6 \\
+ 4 & 16 & 256 & 24 \\
+ 5 & 25 & 625 & 120 \\
+ 6 & 36 & 1296 & 720 \\
+ 7 & 49 & 2401 & 5040 \\
+ 8 & 64 & 4096 & 40320 \\
+ 9 & 81 & 6561 & 362880 \\
+ 10 & 100 & 10000 & 3628800 \\
+ 11 & 121 & 14641 & 39916800 \\
+ 12 & 144 & 20736 & 479001600 \\
+ 13 & 169 & 28561 & 6.22702080E+9 \\
+ 14 & 196 & 38416 & 8.71782912E+10\\
+ 15 & 225 & 50625 & 1.30767437E+12\\
+ 16 & 256 & 65536 & 2.09227899E+13\\
+ 17 & 289 & 83521 & 3.55687428E+14\\
+ 18 & 324 & 104976 & 6.40237370E+15\\
+ 19 & 361 & 130321 & 1.21645100E+17\\
+ 20 & 400 & 160000 & 2.43290200E+18\\
+ \hline
+ 1 & 1 & 1 & 1 \\
+ 2 & 4 & 16 & 2 \\
+ 3 & 9 & 81 & 6 \\
+ 4 & 16 & 256 & 24 \\
+ 5 & 25 & 625 & 120 \\
+ 6 & 36 & 1296 & 720 \\
+ 7 & 49 & 2401 & 5040 \\
+ 8 & 64 & 4096 & 40320 \\
+ 9 & 81 & 6561 & 362880 \\
+ 10 & 100 & 10000 & 3628800 \\
+ 11 & 121 & 14641 & 39916800 \\
+ 12 & 144 & 20736 & 479001600 \\
+ 13 & 169 & 28561 & 6.22702080E+9 \\
+ 14 & 196 & 38416 & 8.71782912E+10\\
+ 15 & 225 & 50625 & 1.30767437E+12\\
+ 16 & 256 & 65536 & 2.09227899E+13\\
+ 17 & 289 & 83521 & 3.55687428E+14\\
+ 18 & 324 & 104976 & 6.40237370E+15\\
+ 19 & 361 & 130321 & 1.21645100E+17\\
+ 20 & 400 & 160000 & 2.43290200E+18\\
+ \hline
+ 1 & 1 & 1 & 1 \\
+ 2 & 4 & 16 & 2 \\
+ 3 & 9 & 81 & 6 \\
+ 4 & 16 & 256 & 24 \\
+ 5 & 25 & 625 & 120 \\
+ \end{supertabular}
+\end{center}
+%%%% fin exemple %%%%
+
+* Le package 'longtable', de D. Carlisle, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/, fonctionne de la mme
+manire mais mieux et permet de dfinir une taille de tableau
+commune sur toutes les pages. Les commandes associes ce
+package sont \endfirsthead, \endhead, \endfoot et \endlastfoot.
+
+\begin{longtable}
+ {|p{0.2\linewidth}|p{0.2\linewidth}|p{0.2\linewidth}|}
+ \hline
+ Premiere colonne & Deuxieme & Troisieme \endfirsthead
+ \hline
+ Premiere & Deuxieme & Troisieme \\
+ \multicolumn{3}{|p{0.6666\linewidth}|}{Suite ... } \\
+ \endhead
+ \hline
+ \multicolumn{3}{|p{0.6666\linewidth}|}{Suite page suivante}
+ \\ \hline \endfoot \hline
+ \multicolumn{3}{|p{0.6666\linewidth}|}{C'est fini} \\
+ \hline
+ \endlastfoot \hline
+ 1 & 1 & 1 \\
+ 2 & 4 & 16 \\
+ 3 & 9 & 81 \\
+ 1 & 1 & 1 \\
+ 2 & 4 & 16 \\
+ 3 & 9 & 81 \\
+ 1 & 1 & 1 \\
+ 2 & 4 & 16 \\
+ 3 & 9 & 81 \\
+ 1 & 1 & 1 \\
+ 2 & 4 & 16 \\
+ 3 & 9 & 81 \\
+\end{longtable}
+
+au lieu de faire des calculs de largeurs de colonne, on peut
+aussi mettre un \setlongtables dans le prambule et dclarer
+ses tableaux comme l'habitude en \begin{longtable}{|c|c|c|}
+et LaTeX se charge du reste. Dans ce cas, l'ajustement des
+colonnes peut ncessiter plusieurs (jusqu' trois) compilations
+enchanes.
+
+* Le package 'ltxtable' de D. Carlisle, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/carlisle/ permet de
+profiter des fonctionnalits de tabularx et de longtable.
+
+# 7.3 # Comment modifier l'orientation d'un tableau ?
+-----------------------------------------------------
+* On peut utiliser la commande \rotatebox du package 'graphics'
+de D. Carlisle. Ce package est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/.
+
+Exemple :
+\rotatebox{90}{
+\begin{tabular}{|c|c|}
+ \hline
+ salut & coucou \\
+ \hline
+\end{tabular}
+}
+%%%% fin exemple %%%%
+
+* Le style 'lscape' de D. Carlisle marche aussi avec
+l'environnement longtable (du mme).
+
+* De mme l'environnement sidewaystable du package 'rotating'
+permet d'inclure des tableaux en mode landscape. Le sens de
+rotation peut tre chang par l'option counterclockwise.
+
+Exemple :
+\documentclass{report}
+\usepackage[counterclockwise]{rotating}
+\usepackage{french}
+\pagestyle{empty}
+\begin{document}
+\rotatebox{90}{
+\begin{tabular}{|c|c|}
+ \hline
+ vu & voir \\
+ de Latour & Van Gogh \\
+ \hline
+\end{tabular}
+}
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'rotfloat' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/rotfloat/ permet de grer
+la rotation des flottants.
+
+# 7.4 # Comment nommer un tableau ?
+-----------------------------------
+Pour pouvoir associer une lgende (\caption) un tableau, il
+suffit de l'encapsuler dans un environnement table.
+
+Exemple :
+\begin{table}[htbp]
+ \begin{center}
+ \begin{tabular}{|c|c|}
+ \hline
+ un & deux \\
+ \hline
+ trois & quatre \\
+ \hline
+ \end{tabular}
+ \caption{Nom du tableau. \label{table-nom}}
+ \end{center}
+\end{table}
+%%%% fin exemple %%%%
+
+# 7.5 # Comment modifier l'paisseur des lignes d'un tableau ?
+--------------------------------------------------------------
+* Pour obtenir des lignes horizontales fines ou paisses dans un
+tableau, il faut utiliser les commandes
+\setlength{\doublerulesep}{\arrayrulewidth} dans l'entte du
+document puis dans le tableau
+\\\hline pour une ligne fine
+\\\hline\hline pour une ligne paisse
+
+* Autre solution : la macro de A. Kessi (alain.kessi@psi.ch)
+
+%%%% debut macro %%%%
+\makeatletter
+\def\hlinewd#1{%
+\noalign{\ifnum0=`}\fi\hrule \@height #1 %
+\futurelet\reserved@a\@xhline}
+\makeatother
+%%%% fin macro %%%%
+
+Exemple :
+\begin{tabular}{|l|r|} \hline
+ premier & 1 \\ \hline
+ second & 2 \\ \hlinewd{5pt}
+ total & 3 \\ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+Mme chose pour les lignes verticales.
+%%%% debut macro %%%%
+ \begin{tabular}{@{\,\vrule width 5pt\,}c|c|}
+%%%% fin macro %%%%
+
+* Le package 'easytable' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ propose diffrents
+styles de lignes de sparation des cellules d'un tableau.
+
+# 7.6 # Comment griser des cellules d'un tableau ?
+--------------------------------------------------
+* Le package 'colortab' disponible par ftp sur
+ftp://ftp.princeton.edu/pub/tvz/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/graphics/pstricks/generic/ (accompagn de sa doc dans
+ftp://ftp.fdn.org/pub/CTAN/graphics/pstricks/origdoc/) permet de griser ou de mettre en
+couleur certaines parties de tableau.
+
+Remarque : colortab n'est pas actuellement maintenu par Van
+ Zandt et l'extension longtable, avec laquelle il
+ tait compatible, ne fonctionne plus.
+AL: c'est toujours vrai, a ?
+
+* Il est possible galement d'utiliser le package 'shade'
+disponible sur {macros/generic/}.
+
+* D. Carlisle propose galement le package 'colortbl' sur
+ftp://ftp.fdn.org/pub/CTAN/macros/contrib/supported/carlisle/. Ce package permet
+non seulement de grer de la couleur mais il est en outre
+compatible avec le package 'longtable'. Il ncessite les
+packages 'array' et 'color'.
+
+Exemple :
+\begin{tabular}{|>{\columncolor[gray]{.8}}l%
+|>{\color{white}\columncolor[gray]{.2}}r|}
+ \hline
+ UN & DEUX \\
+ TROIS & QUATRE \\
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.7 # Comment changer la fonte d'une colonne ?
+------------------------------------------------
+Pour prciser une fonte spcifique dans une colonne d'un
+tableau, on peut utiliser le package 'array'. Ce dernier est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/.
+
+Exemple :
+\begin{tabular}{>{\bfseries}l >{\slshape}r c}
+ gras & pench & normal \\
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.8 # Comment crer des notes de bas de page dans un tableau ?
+----------------------------------------------------------------
+* Il suffit d'encapsuler le tableau dans un environnement
+minipage et pour supprimer le trait de sparation des notes de
+bas de page de dclarer : \renewcommand{\footnoterule}{}.
+
+Exemple :
+\begin{minipage}[t]{5cm}
+ \renewcommand{\footnoterule}{} % permet de supprimer le
+ % trait de sparation
+ \begin{tabular}{|c|c|}
+ \hline
+ Air & Terre\footnote{Feu}\\
+ \hline
+ \end{tabular}
+\end{minipage}
+%%%% fin exemple %%%%
+
+Remarque : dans ce cas, la note apparat juste aprs le tableau,
+ dans l'environnement minipage.
+
+* On peut galement utiliser :
+\footnote[cptr]{texte.}
+toujours dans un environnement minipage, et grer soi-mme ses
+compteurs (cptr est un entier alors que les marques qui
+apparaissent dans le tableau sont les lettres de l'alphabet).
+
+Remarque : ici aussi la note apparat en dessous du tableau.
+
+* Il existe galement deux commandes spcifiques \footnotemark[]
+et \footnotetext[]{}. \footnotemark permet de grer le compteur
+de notes et \footnotetext permet d'insrer le texte
+correspondant en bas de page.
+
+Exemple :
+\begin{tabular}{|c|c|}
+ \hline
+ donnee1\footnotemark[1] & donnee2\footnotemark[2] \\
+ \hline
+\end{tabular}
+\footnotetext[1]{Note associ\'ee \`a la donn\'ee 1.}
+\footnotetext[2]{Note associ\'ee \`a la donn\'ee 2.}
+%%%% fin exemple %%%%
+
+Remarque : ici les notes apparaissent bien dans le bas de page.
+
+# 7.9 # Comment crire un texte sur plusieurs colonnes ?
+--------------------------------------------------------
+Il faut utiliser la commande :
+\multicolumn{nb_colonnes}{alignement}{Texte}
+
+Exemple :
+\begin{tabular}[b]{|l|c|}
+ \hline
+ \multicolumn{2}{|c|}{Texte sur 2 colonnes} \\
+ \hline \hline
+ donne1 & donne2 \\
+ A & B \\
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+Remarque : dans le cas o le nombre de colonnes couvrir est
+ gal 1, cette commande peut tre utilise pour
+ modifier l'alignement (c, l, r, |, etc) d'une
+ cellule.
+
+# 7.10 # Comment passer certaines cellules en reverse vido ?
+-------------------------------------------------------------
+Le package 'color' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/ permet entre autres de le
+faire. En fait, il permet de dfinir des couleurs de texte et de
+fond de page.
+
+Exemples :
+\tabcolsep=30pt
+\begin{tabular}{|c|c|c|}
+\hline
+1&&\\
+&\colorbox{black}{\strut{\color{white}Coucou}}&\\
+&&2\\
+\hline
+\end{tabular}
+
+ou (\LaTeXe)
+
+\newlength\Coucoulength
+\settowidth\Coucoulength{Coucou Coucou Coucou}
+
+\begin{tabular}{|c|c|c|}
+\hline
+1&Coucou Coucou Coucou &\\
+&\colorbox{black}{\makebox[\Coucoulength][c]{\color{white}Coucou}}
+&\\
+&&2\\
+\hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.11 # Comment fixer la largeur d'une colonne ?
+-------------------------------------------------
+* p{largeur} dans les descripteurs de colonne permet de fixer la
+largeur d'une colonne. Dans ce cas par dfaut le texte est
+justifi gauche. Les commandes \centering et \raggedright
+permettent respectivement de le centrer ou de le justifier
+droite.
+
+Exemple :
+\begin{center}
+ \begin{tabular}{|c|l|p{4cm}|r|}
+ \hline
+ centr & gauche & largeur fixe & droite \\
+ bla bla bla & bla bla bla & bla bla bla & bla bla bla \\
+ \hline
+ \end{tabular}
+\end{center}
+%%%% fin exemple %%%%
+
+* Avec le package 'array', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/, il faut utiliser l'option
+m{largeur}.
+
+* Le package 'easytable' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ permet facilement d'crire
+des tableaux dont les colonnes ont une largeur fixe.
+
+# 7.12 # Comment crire un texte sur plusieurs lignes ?
+-------------------------------------------------------
+Il existe le package 'multirow' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/. Il permet d'crire un texte
+cheval sur deux lignes.
+
+Exemple :
+\begin{table}[htbp]
+ \begin{center}
+ \begin{tabular}{|c|c||c|c|}
+ \hline
+ \multirow{2}{0.5cm}{k} & \multirow{2}{0.5cm}{$p_G$} &
+ \multicolumn{2}{c|}{test} \\
+ \cline{3-4}
+ & & DADWRD & RARWRD \\
+ \hline
+ 2 & $1$ & 90 n & 228 n \\
+ 3 & $p_d$ & 202 n & 449 n \\
+ 4 & $p_d^2$ & 424 n & 891 n \\
+ 5 & $p_d^3$ & 866 n & 1774 n \\
+ \hline
+ \end{tabular}
+ \caption{Nombre d'opration par cellule des tests
+ pseudo-alatoires de fautes de type k-coupling.
+ \label{table-compar}}
+ \end{center}
+\end{table}
+%%%% fin exemple %%%%
+
+# 7.13 # Comment diviser une cellule par une diagonale ?
+--------------------------------------------------------
+Il faut utiliser le package 'slashbox' disponible par ftp sur
+ftp://ftp.tohoku.ac.jp/pub/TeX/latex-styles/bear_collections/style-files/.
+
+Exemple (de la doc) :
+\begin{tabular}{|l||*{5}{c|}}\hline
+\backslashbox{Room}{Date}
+&\makebox[3em]{5/31}&\makebox[3em]{6/1}&\makebox[3em]{6/2}
+&\makebox[3em]{6/3}&\makebox[3em]{6/4}\\\hline\hline
+Meeting Room &&&&&\\\hline
+Auditorium &&&&&\\\hline
+Seminar Room &&&&&\\\hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.14 # Comment dfinir une colonne en mode mathmatique dans un tableau ?
+---------------------------------------------------------------------------
+Avec le package 'array' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/, il suffit de dclarer
+\begin{tabular}{>{$}c<{$}cc} pour avoir une colonne en mode
+mathmatique et deux colonnes de texte.
+
+# 7.15 # Comment modifier le nombre de tableaux par page ?
+----------------------------------------------------------
+cf. question 8.4.
+
+# 7.16 # Comment mettre deux tableaux cte cte ?
+---------------------------------------------------
+cf. question 8.3.
+
+# 7.17 # Comment dfinir un sparateur de colonne ?
+---------------------------------------------------
+@{symbole} entre deux descripteurs de colonnes permet de dfinir
+"symbole" comme sparateur de colonnes. Cela remplace |.
+
+Exemple :
+\begin{tabular}{|l @{\textbf{ est }} l|}
+ \hline
+ Le lion & froce. \\
+ Le chien & fidle. \\
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+# 7.18 # Comment obtenir des lignes partielles dans un tableau ?
+----------------------------------------------------------------
+La commande \cline{ColonneDebut-ColonneFin} est faite pour a.
+
+Exemple :
+\begin{center}
+ \begin{tabular}{|c|c|c||c|c|c|c|c|c|c||c|}
+ \hline \hline
+ a & b & c & d & e & f & g & h & i & j & k \\
+ \cline{1-4} \cline{6-6} \cline{8-9}
+ 1 & 2 & 3 & 4 & 5 & 6 & 7 & 8 & 9 & 10 & 11 \\
+ \hline
+ \end{tabular}
+\end{center}
+%%%% fin exemple %%%%
+
+# 7.19 # Comment viter que du texte de grande taille n'atteigne le cadre des cellules ?
+----------------------------------------------------------------------------------------
+* Il faut pour cela utiliser la commande \strut qui simule un
+objet vertical invisible, aprs le changement de fonte.
+
+Exemple :
+\begin{tabular}{|l|}
+ \hline
+ {\large HELLO} dfg \\
+ \hline
+\end{tabular}
+\begin{tabular}{|l|}
+ \hline
+ {\large\strut HELLO} dfg \\
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+* Il existe l'quivalent mathmatique : \mathstrut.
+
+* On peut galement agrandir la hauteur des lignes avec la
+commande \arraystretch :
+ \renewcommand{\arraystretch}{1.5}
+
+# 7.20 # Comment fixer la largeur d'un tableau ?
+------------------------------------------------
+* Le package 'tabularx' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/ permet de dfinir une largeur
+de tableau.
+
+* Le package 'easytable' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ permet facilement de
+fixer des largeur de colonnes ou de lignes.
+
+# 7.21 # Comment tracer des traits discontinus ?
+------------------------------------------------
+Il faut utiliser les packages 'hvdashln' et 'array'.
+
+Exemple :
+dans le prambule du document :
+\usepackage{hvdashln,array}
+\setlength{\hdashlinewidth}{.5pt}
+\setlength{\hdashlinegap}{2pt}
+
+dans le texte :
+\[
+\left[ \begin{array}{ccc@{}>{\vdashline}c}
+ a_1 & b_1 & c_1 & d_1 \\
+ a_2 & b_2 & c_2 & d_2 \\
+ a_3 & b_3 & c_3 & d_3 \\
+ a_4 & b_4 & c_4 & d_4
+\end{array} \right]
+\]
+%%%% fin exemple %%%%
+
+# 7.22 # Comment fixer la taille et justifier une colonne ?
+-----------------------------------------------------------
+Le problme qui se pose lorsqu'on utilise :
+\begin{tabular}{|>{\raggedright}p{0.33\textwidth}<{}|
+ >{\raggedleft}p{0.66\textwidth}<{}|}
+ A& \\
+ B&C \\
+\end{tabular}
+vient du fait que \\ est redfini par tabular et les commandes
+ragged. On ne peut donc plus utiliser \\ dans un texte.
+
+Il existe diffrentes solutions pour pallier ce problme :
+* on peut corriger ce problme en incluant les lignes suivantes
+dans le prambule du document :
+\makeatletter
+\newtoks\fintableau
+\let\fintableau\@arraycr
+\makeatother
+
+* avec le package 'array', il suffit d'utiliser
+la commande \tabularnewline[<vertical space>] la place de la
+commande \\.
+
+Exemple :
+\begin{tabular}{|r|r|>{\raggedleft}m{190pt}|}
+ \hline
+ col1 & col 2 & col3 \tabularnewline
+ une & deux & trois \\ quatre \tabularnewline
+ \hline
+\end{tabular}
+%%%% fin exemple %%%%
+
+* on peut galement inclure la nouvelle commande suivante dans
+le prambule du document :
+\newcommand\PreserveBackSlash[1]{\let\temp=\\#1\let\\=\temp}
+puis en utilisant :
+\begin{tabular}{|r|r|>{\PreserveBackSlash\raggedleft}m{190pt}|}
+
+# 7.23 # Comment faire une liste de tableaux ?
+----------------------------------------------
+Il suffit d'inclure la commande \listoftables l'endroit o
+l'on veut inclure cette liste. Sachant que cette liste fait
+rfrence aux pages o apparaissent les tableaux, il faut
+enchaner au moins deux compilations LaTeX pour que toutes les
+rfrences soient exactes.
+
+================================================================
+[8] GESTION DES FIGURES
+================================================================
+
+# 8.1 # Comment inclure une figure ?
+------------------------------------
+Remarque : A. K. Goel a crit un long document concernant les
+ problmes de gestion de figures et d'images dans
+ LaTeX. Ce dernier est disponible par ftp anonyme sur
+ ftp://math.uwaterloo.ca/pub/figsInLatex.ps.Z ou sur
+ ftp://ftp.fdn.org/pub/CTAN/info/figsinltx.ps
+
+ De mme, K. Reckdahl a crit "Using EPS Graphics in
+ LaTeX2e Documents". Ce document est disponible sur
+ ftp://ftp.fdn.org/pub/CTAN/info/epslatex.ps.
+
+* Sous LaTeX2e, il faut utiliser l'un des packages :
+'graphics' ou 'graphicx' et la commande \includegraphics. Cette
+commande accepte des options telles que dvips ou oztex (cf.
+documentation pour plus de dtails).
+Le package 'graphicx' a pour majeure diffrence avec 'graphics'
+d'en simplifier les commandes. Ces packages sont disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/. Pour plus de
+dtails, consulter http://www.loria.fr/services/tex/packages.html.
+
+Exemple :
+\begin{figure}[htbp]
+ \begin{center}
+ \includegraphics{images/fig1.ps}
+ \end{center}
+ \caption{\footnotesize blah blah blah}
+\end{figure}
+%%%% fin exemple %%%%
+
+La commande \includegraphics du package 'graphicx' peut prendre
+comme paramtres angle, width, height, scale, clip et draft.
+
+Exemple :
+\includegraphics[width=\linewidth, draft=true]{figure.eps}
+%%%% fin exemple %%%%
+
+* Sous LaTeX2.09, pour pouvoir appeler un fichier postscript,
+il suffit de mettre l'option epsf dans le \documentstyle.
+La figure peut ensuite tre appele par la commande
+\epsfbox{nom-figure.(e)ps}
+
+Une jolie faon d'inclure une figure dans un source LaTeX2.09
+est d'utiliser la macro :
+
+\begin{figure}[htbp]
+ \centerline{\epsfxsize=10cm \epsfbox{nom-figure.format}}
+ \caption{. \label{fig-}}
+\end{figure}
+
+* Il y a aussi le package 'epsfig' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/ (LaTeX2.09 mais utilisable
+avec LaTeX2e).
+
+Exemple :
+\begin{figure}[p]
+ \centerline{\epsfig{file=nom_figure.eps,
+ width=largeur,
+ height=hauteur}}
+ \caption{Titre.}
+ \label{nom_label}
+\end{figure}
+%%%% fin exemple %%%%
+
+* Une figure au format tex picture, tex picture + epic, tex
+picture + eepic, ... peut tre appele directement par une
+commande \input. En outre, si vous utilisez un format epic ou
+eepic, il faut penser rajouter 'epic' ou 'eepic' la ligne
+documentstyle ou d'inclure les packages 'epic' ou 'eepic'.
+
+# 8.2 # Comment nommer une figure ?
+-----------------------------------
+C'est la commande \caption qui permet de faire cela. Par dfaut
+le titre de la figure apparatra en dessous. Cf exemples
+ci-dessus. Pour que le titre apparaisse au-dessus, il faut
+redfinir les longueurs suivantes.
+
+Exemple :
+\setlength\abovecaptionskip{0pt}
+\setlength\belowcaptionskip{10pt}
+puis appeler :
+\begin{figure}
+\caption{... ... ...}
+\includegraphics{dessin.eps}
+\end{figure}
+%%%% fin exemple %%%%
+
+# 8.3 # Comment placer des figures cte cte ?
+------------------------------------------------
+* Sous LaTeX2e, il faut utiliser le package 'graphics' ou
+'graphicx' disponibles sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/.
+
+Exemples :
+\begin{figure}
+ \begin{minipage}[c]{.46\linewidth}
+ \includegraphics{figure1.format}
+ \end{minipage} \hfill
+ \begin{minipage}[c]{.46\linewidth}
+ \includegraphics{figure2.format}
+ \end{minipage}
+\end{figure}
+
+\begin{figure}
+\includegraphics[width=5cm]{fig1.eps}\hfill
+\includegraphics[width=5cm]{fig2.eps}
+\caption{Titre commun}\label{fig:somefiglabel}
+\end{figure}
+%%%% fin exemple %%%%
+
+* Une autre solution consiste mettre chaque figure dans une
+case d'un tableau.
+
+Exemple (avec le package graphics ou graphicx) :
+\begin{tabular}{cc}
+ \includegraphics{figure1.eps} &
+ \includegraphics{figure2.eps} \\
+\end{tabular}
+%%%% fin exemple %%%%
+
+* LaTeX2.09. Pour mettre des figures cte cte, il suffit
+d'encapsuler leur appel dans des minipages.
+
+Exemples :
++ avec le package 'epsf'
+\begin{minipage}[t]{.46\linewidth}
+ \center\epsfxsize= 5cm \epsfbox{fig1.eps}
+\end{minipage} % ne pas sauter de ligne
+\begin{minipage}[t]{.46\linewidth}
+ \center\epsfxsize= 5cm \epsfbox{fig2.eps}
+\end{minipage}
+
+ou si l'on veut attacher des titres aux figures :
+
++ avec le package 'epsfig'
+\begin{figure}
+ \begin{minipage}[b]{.46\linewidth}
+ \centering\epsfig{figure=fig1.ps,width=\linewidth}
+ \caption{premiere figure \label{fig1}}
+ \end{minipage} \hfill
+ \begin{minipage}[b]{.46\linewidth}
+ \centering\epsfig{figure=fig2.ps,width=\linewidth}
+ \caption{deuxieme figure \label{fig2}}
+ \end{minipage}
+\end{figure}
+%%%% fin exemple %%%%
+
+* Si l'on veut un seul titre pour plusieurs figures voir le
+package 'subfigure' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/subfigure/.
+
+Exemple :
+\begin{figure}[ht]
+\begin{center}
+ \subfigure[I]{\epsfig{figure=st1.ps,width=6.58cm}}\quad
+ \subfigure[II]{\epsfig{figure=st2.ps,width=5.0cm}}\\
+ \subfigure[III]{\epsfig{figure=st3.ps,width=5.0cm}}
+\end{center}
+\caption{Impermeable surface treatments}
+\label{fig:inf}
+\end{figure}
+%%%% fin exemple %%%%
+
+* Une autre possibilit pour obtenir un titre par figure est
+d'utiliser le package 'epslatex' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/info/.
+
+# 8.4 # Comment modifier le nombre de figures par page ?
+--------------------------------------------------------
+En fait, on ne peut agir que globalement sur le nombre de
+flottants autoris par page. Il n'y a pas de slection
+figure/tables/....
+
+Il arrive frquemment que lorsqu'un flottant dpasse 60% d'une
+page, LaTeX prfre changer de page plutt que d'utiliser les
+40% de l'espace restant.
+
+La commande \floatpagefraction permet de redfinir l'espace
+minimum que peuvent occuper des flottants. Cela permet de
+limiter le "blanc" sur une page contenant des flottants.
+
+Exemple :
+\renewcommand{\floatpagefraction}{.9}
+utilise avec la commande :
+\renewcommand{\textfraction}{.1}
+permet de dire que le texte peut n'occuper que 10% d'une
+page, et donc que des flottants peuvent occuper les 90% restant.
+%%%% fin exemple %%%%
+
+Il y a d'autres paramtres intressants :
+\setcounter{totalnumber}{4}
+qui dtermine le nombre de flottants autoriss par page,
+\renewcommand{\topfraction}{.8} et
+\renewcommand{\bottomfraction}{.8}
+qui indiquent la fraction maximum du haut ou du bas de la page
+que peuvent occuper des flottants.
+
+Remarque : Il est recommand de ne jamais mettre 100% comme
+ paramtre.
+
+# 8.5 # Comment superposer du texte sur des figures ?
+-----------------------------------------------------
+* PSFrag (disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/psfrag/) donne cette possibilit.
+La solution consiste en fait :
+1+ faire le graphique .ps AVEC des textes et lgendes MAIS
+approximatifs
+2+ utiliser PSfrag pour qu'il remplace les textes approximatifs
+par des textes << LaTeX >>
+(3-) l'criture << par dessus >> (le remplacement en fait) est
+fait par PSfrag.
+Pour plus de dtails, consulter le document "Using EPS Graphics
+in LaTeX2e Documents" disponible sur ftp://ftp.fdn.org/pub/CTAN/info/epslatex.ps.
+
+* On peut galement gnrer une courbe dans un fichier .eps,
+qui peux ensuite tre inclu dans un environnement "picture",
+dans lequel il est ensuite possible d'ajouter du texte avec des
+\put. Cela demande pas mal de mises au point.
+
+Exemple :
+\setlength\unitlength{1cm}
+\begin{picture}(10,10)
+\put(0,0){\includegraphics{mondessin.eps}}
+\put(10,10){Mon commentaire \LaTeX{} avec des $maths$}
+\end{picture}
+%%%% fin exemple %%%%
+
+Cette technique permet de conserver la puissance de LaTeX et
+d'avoir une typographie homogne mais elle a l'inconvenient
+d'tre assez lourde.
+
+* PSTricks est un ensemble de macros TeX, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/graphics/pstricks/, qui permet galement de faire cela. Il
+ncessite un gros investissement (il y a une centaine de pages
+de documentation). Cependant, si l'on se limite des commandes
+simples (comme par exemple crire un programme en C qui trace le
+dessin, avec simplement des points, des droites, et un peu de
+texte), la liste sommaire des commandes suffit (6 pages).
+
+* Xfig offre une autre solution. Aprs avoir inclu un fichier
+postscript gnr par un autre programme, on peut rajouter
+du texte ou des commandes LaTeX dessus.
+xfig -sp
+Sauvegarder comme "combined PS/LaTeX"
+
+* Metapost est un langage graphique trs proche de Metafont,
+mais qui gnre du postscript. Il permet de produire des figures
+avec du texte et est bien interfac avec TeX (Knuth
+l'utilise). Metapost est integr dans web2c 7.0. Metapost a
+dj t port sous MS-DOS et Mac (CMacTeX). Pour plus
+d'informations, vous pouvez consulter la page de D. Roegel :
+http://www.loria.fr/~roegel/metapost.html.
+
+* pstoedit permet galement de visualiser des fichiers
+postscript (sans bitmaps) et d'ajouter du texte ou des figures
+par dessus.
+
+# 8.6 # Comment raliser des captures d'cran ?
+-----------------------------------------------
+* Un outil trs utile pour effectuer des captures d'cran sous
+Unix est xv. xv est un diteur d'images crit par J. Bradley
+disponible sous unix. xv est capable de grer diffrents
+formats d'image (encodage PS, GIF, JPEG, TIFF,...). Il
+permet de visualiser des images et aussi de raliser des
+captures d'cran, soit partielles dfinies la souris, soit
+par fentre X Window. Il suffit ensuite de sauvegarder la
+saisie d'cran de xv en format postscript et de l'appeler sous
+LaTeX.
+
+xv est accessible par ftp sur ftp://ftp.lip6.fr/.
+
+* Sur PC il y a pcxdump disponible sur
+http://micros.hensa.ac.uk/. Le package 'verbtext', disponible sur
+CTAN, permet ensuite d'appeler la saisie ralise.
+
+* De mme, le package 'scrdumps' et l'utilitaire scr2tex.exe
+sous DOS permettent d'inclure des saisies d'cran dans un
+document LaTeX.
+
+# 8.7 # Comment tracer une courbe ?
+-----------------------------------
+* Xgraphic est un outil de trac de courbes simple
+d'utilisation (les options sont accessibles en interactif) mais
+limit aux courbes 2D. Il est disponible avec une doc franaise
+ http://blanche.polytechnique.fr/ et
+ftp://barbes.polytechnique.fr/pub/Xgraphic/.
+
+* xmgr marche galement trs bien.
+
+* GNUplot est disponible sous Unix, sous Dos, sous Windows et
+sous macOS
+(http://www.ee.gatech.edu/users/schooley/gnuplot.html). Il
+possde une sortie LaTeX (eepic). Il permet de tracer des
+courbes (2D et 3D) partir de valeurs ou d'une fonction. Les
+formats de sortie sont LaTeX ou postscript.
+
+En outre, sous Unix, il est possible de rcuprer des fichiers
+GNUplot exports par
+ set terminal fig
+ set output "graph.fig"
+puis de les modifier.
+
+La FAQ GNUplot est disponible
+http://www.uni-karlsruhe.de/~ig25/gnuplot-faq/.
+
+* Xy-pic compatible plain TeX, LaTeX2.09 et LaTeX2e permet de
+tracer des courbes, de raliser des diagrammes commutatifs, des
+automates, et plein d'autres choses. Pour plus de
+renseignements, consulter :
+ftp://ftp.mpce.mq.edu.au/pub/maths/TeX/ ou
+http://www.mpce.mq.edu.au/~ross/Xy-pic.html ou
+http://www.brics.dk/~krisrose/Xy-pic.html
+Le package 'xypic' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/diagrams/xypic/.
+
+* Sur PC grapher et surfer permettent galement de tracer des
+courbes et des surfaces (ils sont indpendants de LaTeX, mais
+une saisie d'cran est toujours possible).
+
+* Le package 'curves' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/curves/ permet de dfinir des
+courbes dans l'environnement picture.
+
+* Mathematica est galement utilisable pour tracer des courbes
+2D et 3D.
+
+# 8.8 # Comment est gr le positionnement des figures ?
+--------------------------------------------------------
+Comme mentionn prcdemment (8.1), il existe diffrentes
+options de placement des figures. Les plus classiques sont
+\begin{figure}[htbp] pour laisser LaTeX la possibilit de
+placer les figures suivant ses critres de beaut. (h) impose
+si possible le placement de la figure l'appel de la macro
+ci-dessus. Sinon la figure sera place en haut de la page
+suivante (t) ou en bas (b), voire sur une page seule (p).
+
+En revanche, pour forcer (dans la mesure du possible) LaTeX
+placer une figure l o elle a t appele, il faut utiliser le
+package 'float', de A. Lingnau, (\usepackage{float}) et l'option
+H (\begin{figure}[H]). Ce package permet de dfinir un tel
+placement par dfaut via la commande \floatplacement{figure}{H}.
+Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/float/. Voir la question 6.34
+pour un exemple d'utilisation de ce package.
+
+De mme l'utilisation du caractre ! devant une option de
+placement permet de forcer LaTeX2e effectuer son placement au
+plus tt (suivant l'option choisie).
+
+Remarque (D.Barbier) : si un flottant ne peut pas tre plac
+ avec les paramtres indiqus , celui-ci et tous les
+ flottants qui viennent aprs seront mis la fin du
+ chapitre (en fait, ils seront insrs grce la
+ commande \clearpage).
+
+Le package 'placeins' de D. Arsenau permet de mettre des
+garde-fous dans le texte. Par exemple, lorsqu'on place une
+figure en dur avec une commande du style :
+%%%% debut macro %%%%
+\makeatletter
+\newenvironment{figureH}{\begin{center}
+ \newcommand{\@captype}{figure}}{\end{center}}
+\makeatother
+%%%% fin macro %%%%
+l'utilisation de \FloatBarrier juste avant, permet de vider le
+buffer de flottants actuellement stocks.
+
+# 8.9 # Comment placer une lgende ct d'une figure ?
+--------------------------------------------------------
+* Pour placer une lgende ct d'une figure, il faut utiliser
+l'environnement minipage.
+
+Exemple (extrait du cahier GUTenberg 22 pour l'article sur
+esperluette) :
++ mettre dans le prambule :
+
+%%%% debut macro %%%%
+\newlength\jataille
+\newcommand{\figgauche}[3]%
+{\jataille=\textwidth\advance\jataille by -#1
+\advance\jataille by -.5cm
+\begin{minipage}[c]{#1}
+ \includegraphics[width=#1]{#2}
+\end{minipage}\hfill
+\begin{minipage}[c]{\jataille}
+ \footnotesize #3 \normalsize
+\end{minipage}}
+%%%% fin macro %%%%
+
++ puis utiliser :
+\figgauche{5cm}{totor.eps}{Titre.}
+
+* On peut galement utiliser des parbox.
+
+Exemple :
+\begin{figure}
+\parbox{7cm}{...figure}\parbox{7cm}{\caption{---}}
+\end{figure}
+%%%% fin exemple %%%%
+
+# 8.10 # Comment insrer des figures dans multicol ?
+----------------------------------------------------
+
+On ne peut insrer que des figures de la largeur de la page,
+et pas de la lageur d'une colonne, donc des figure* (resp.
+table*). Un flottant n'apparatra pas sur la page o il
+est defini, mais, au mieux, sur la page d'aprs. Le positionnement
+[h] n'a donc pas de sens.
+
+Exemple (avec le package 'graphicx') :
+\begin{figure*}
+ \includegraphics[width=3cm]{totor.eps}
+\end{figure*}
+%%%% fin exemple %%%%
+
+Remarque : dans ce cas la gestion de \caption semble ne pas tre
+ correcte.
+
+# 8.11 # Comment faire apparatre toutes les figures en fin de document ?
+-------------------------------------------------------------------------
+Le package 'endfloat', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/endfloat/, permet de
+reporter toutes les figures en fin de document.
+
+ATTENTION : les classes AMS ne dfinissent pas les
+ environnements figure* et table*. En
+ outre, le package 'endfloat' a le mauvais got de
+ supposer qu'ils sont dfinis. Un remde est de
+ faire :
+ \documentclass[a4paper,11pt]{amsart}
+ \newenvironment{figure*}{\figure}{\endfigure}
+ \usepackage{endfloat}
+
+# 8.12 # Comment insrer des images Mathematica ?
+-------------------------------------------------
+* Sous Unix ou sous DOS, il faut, partir de Mathematica,
+demander : Display["machin",truc]
+qui sauve l'image truc dans le fichier machin dans un Postscript
+embryonnaire, puis
+!psfix -epsf machin > machin.eps
+et on a un fichier EPS comme il faut.
+
+* Sous Windows, aprs avoir slectionn l'image dsire, il
+faut, dans le menu "Fichier" de Mathematica, "Exporter" vers un
+format qui peut tre .EPS (PostScript Encapsul). L'appel de ce
+fichier .eps sous LaTeX se fait alors de manire classique (cf.
+paragraphe 8.1).
+
+Il est galement possible d'extraire par copier/coller l'image
+(.WMF) et de l'envoyer vers Ghostscript pour Windows, et
+l-dedans de l'enregistrer dans un fichier PostScript. L'avantage
+de cette solution est qu'elle peut permettre de retravailler
+l'image (avant collage dans GS au moyen de CorelDraw, par
+exemple).
+
+A noter que Y&Y TeX system supporte les images WMF (Windows
+MetaFile) aussi bien que les TIFF ou EPSF. Mathematica est l'un
+des seuls logiciels pour Windows qui utilise un format WMF
+plutt que TIFF.
+
+* Dernire solution (multi-systme) : se servir du notebook
+intitul "GnuDisplay.m"(disponible sur MathSource chez Wolfram).
+Celui-ci permet d'exporter une image Mathematica en image
+GNUplot. Dans GNUplot, on peut alors exporter une image de deux
+faons :
++ vers un fichier ".mf" qui contient l'image sous forme de
+fonte. Avantage : on utilise MetaFont pour gnrer la fonte qui
+contiendra l'image et l'insrer dans le texte, ce qui permet sa
+prvisualisation immdiate par "dviscr", sans passer par "dvips"
+puis GhostScript ou GhostView ;
++ vers un fichier au format LaTeX eepic, que l'on insre
+facilement par la suite (commande \special).
+
+# 8.13 # Comment modifier la taille d'une bounding box ?
+--------------------------------------------------------
+En format eps (encapsulated postscript), la `bounding box`
+permet de prciser la taille d'une image. La syntaxe est la
+suivante :
+%%BoundingBox: 0 0 507 257
+Les coordonnes correspondent dans l'ordre :
+- coordonne horizontale du point en bas gauche de la figure;
+- coordonne verticale du point en bas gauche;
+- coordonne horizontale du point en haut droite;
+- coordonne verticale du point en haut droite.
+Les coordonnes verticales tant prises partir du bas, et
+celles horizontales partir de la gauche.
+
+De plus ces coordonnes sont exprimes en points PostScript,
+c'est--dire en soixante-douzime de pouce, i.e.:
+1 pt PS = 1/72 pouce = 2.54/72 cm.
+
+Malheureusement, il arrive parfois que la taille de la bounding
+box soit suprieure celle de la taille relle du dessin
+qu'elle contient (il n'y a pas de mise l'chelle). Le package
+'boxedepsf', de L. Siebenmann, offre les commandes \Trim qui
+permettent de rsoudre le probleme.
+
+A. J. Carr a adapt ce package LaTeX2e. Son package s'appelle
+'boxedeps'. Ce dernier est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/boxed/ ou sur
+ftp://matups.math.u-psud.fr/pub/TeX/Graphics.dir/ArtIntegration.dir/boxedeps.dir/.
+
+Exemple :
+\TrimTop{15pct}\BoxedEPSF{toto}
+avec pct = pourcentage de la hauteur.
+%%%% fin exemple %%%%
+
+# 8.14 # Comment obtenir une figure avec un titre non numrot ?
+----------------------------------------------------------------
+Il faut utiliser la commande \unnumberedcaption dont voici la
+dfinition :
+%%%% debut macro %%%%
+\makeatletter % <=== in a .sty file delete this
+
+\newcommand{\unnumberedcaption}%
+ {\@dblarg{\@unnumberedcaption\@captype}}
+
+\newcommand{\@unnumberedcaption}{}% undefined yet
+\long\def\@unnumberedcaption#1[#2]#3{\par
+ \addcontentsline{\csname ext@#1\endcsname}{#1}{%
+ % orig: \protect\numberline{\csname the#1\endcsname}%
+ %{\ignorespaces #2}
+ \protect\numberline{}{\ignorespaces #2}%
+ }%
+ \begingroup
+ \@parboxrestore
+ \normalsize
+ % orig: \@makecaption{\csname fnum@#1\endcsname}%
+ %{\ignorespaces #3}\par
+ \@makeunnumberedcaption{\ignorespaces #3}\par
+ \endgroup}
+
+% redefine \@makeunnumberedcaption (like \@makecaption)
+% for your own layout
+\newcommand{\@makeunnumberedcaption}[1]{%
+ \vskip\abovecaptionskip
+ \sbox\@tempboxa{#1}%
+ \ifdim \wd\@tempboxa >\hsize
+ #1\par
+ \else
+ \global \@minipagefalse
+ \hbox to\hsize{\hfil\box\@tempboxa\hfil}%
+ \fi
+ \vskip\belowcaptionskip}
+
+% for LaTeX 2.09 compatibility, define \above/belowcaptionskip:
+\@ifundefined{abovecaptionskip}{%
+ \newlength{\abovecaptionskip}%
+ \setlength{\abovecaptionskip}{10pt}%
+}{}
+\@ifundefined{belowcaptionskip}{%
+ \newlength{\belowcaptionskip}%
+ \setlength{\belowcaptionskip}{0pt}%
+}{}
+
+\makeatother % <=== in a .sty file delete this
+%%%% fin macro %%%%
+
+Remarque : le package 'french' V3,49 inclut cette macro.
+
+# 8.15 # Comment redfinir le style de caption ?
+------------------------------------------------
+* Par exemple pour changer la fonte de Figure : en gras, il
+faut utiliser :
+
+%%%% debut macro %%%%
+\makeatletter
+\renewcommand{\fnum@figure}{\small\textbf{\figurename~\thefigure}}
+\makeatother
+%%%% fin macro %%%%
+
+* Pour agir sur les espaces horizontaux de part et d'autre de la
+lgende d'un flottant, on peut utiliser caption2.sty, et dfinir
+la longueur \captionmargin qui sera insre gauche et droite
+de la lgende.
+
+# 8.16 # Comment fondre une image dans du texte ?
+-------------------------------------------------
+* Le package 'floatfig', de T. Kneser, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/floatfig/, permet d'entourer
+une figure de texte de manire trs efficace grce
+l'environnement floatingfigure. Ce package a t conu pour
+LaTeX2.09, pour des documents sans colonnes.
+
+Exemple :
+\begin{floatingfigure}[l]{4cm}
+ \includegraphics[width=4cm]{dessin}
+ \caption{Titre}
+\end{floatingfigure}
+%%%% fin exemple %%%%
+
+Remarque : le [l] du \begin{float...} sert mettre la figure
+ gauche. [r] permet de l'avoir droite, [p] la met
+ gauche sur une page de gauche et droite sur une
+ page de droite.
+
+* Le package 'floatflt', de T. Kneser et M. Dahlgren, disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/floatflt/, a t crit
+pour LaTeX2e. Il tend les possibilits de floatfig par de
+nombreuses options et est utilisable pour les figures et les
+tableaux.
+
+Exemple :
+\begin{floatingfigure}[options]{width of figure}
+ figure contents
+\end{floatingfigure}
+%%%% fin exemple %%%%
+
+* Le package 'picinpar' pour LaTeX2.09 est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/picinpar/ et sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/4alltex/disk04/. Il permet de dfinir un nombre
+de lignes avant lequel la figure pourra tre insre dans le
+texte. La taille de la figure dpend de son contenu, sa position
+est variable, et peut s'taler sur plusieurs paragraphes.
+
+ATTENTION : Ce package n'est pas compatible avec amstex.
+
+Exemple :
+\begin{window}[#lines before, l|r|c, picture contents, caption}
+ ... paragraph text ...
+\end{window}
+%%%% fin exemple %%%%
+
+* Mieux que le prcdent, le package 'picins' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/picins/ permet d'inclure des
+figures dans des paragraphes.
+
+Exemple :
+\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}
+ Paragraph text....
+%%%% fin exemple %%%%
+
+* Le package 'wrapfig' permet de dfinir la hauteur de la
+figure, celle-ci ci peut apparatre droite ou gauche dans le
+texte ou encore dans une marge. Ce package n'est pas compatible
+avec les environnements de liste.
+
+Exemple :
+\begin{wrapfigure}[height in lines]{l|r}[overhang]{width}
+ {figure, caption etc.}
+\end{wrapfigure}
+%%%% fin exemple %%%%
+
+* Le package 'flow' met obligatoirement la figure dans une bote
+avec un cadre et ne permet pas de dfinir de caption.
+
+Exemple :
+\flow[L|R]{paragraph text}{figure box}
+%%%% fin exemple %%%%
+
+* Le package 'window' de E. Schaluck, permet galement
+d'intgrer une figure dans un paragraphe mais il n'est plus
+maintenu. Il a t crit pour LaTeX2.09 mais il est compatible
+LaTeX2e.
+
+Exemple :
+\windowbox[toplines][inwindow: contents][ratio: l r]
+... paragraph text ... \par
+%%%% fin exemple %%%%
+
+Voici les rsultats d'un test comparatif effectu par P. van
+Oostrum :
+ A B C D E F G H I J K
+picinipar |+|+|+| |+|+| |+| | | |
+wrapfig |+|+|+|+| | |+|H|-|+| |
+flow |-|-|+| | | | |+| | | |
+floatfig |+|-|-|+| | |+| | |-| |
+floatflt |+|+|+|+| | |+| |-| |+|
+window |-|-|+| |+|+| |+| | | |
+picins |+|-|+|+| | | |+|+| | |
+
+avec :
+A: figure captions/counting/list of figures
+B: table captions/counting/list of tables
+C: Left/right possible (+ = both)
+D: Alternating left/right for twosided docs
+E: can be placed in the middle of text with twosided flowing
+F: possible to start after the beginning of paragraph
+G: can (more or less) float in the text
+H: auto detection of size of figure (H=height only)
+I: works with list environments
+J: works with twocolumn
+K: works with multicol
+
+Les meilleurs packages semblent tre :
+picins, floatflt et wrapfig.
+
+* Voici galement une macro de C. Mercat :
+
+%%%% debut macro %%%%
+\def\textdess#1#2 % #1={blabla} #2=\dessin{monbodessin}
+{\hbox{
+
+\setbox2=\hbox{#2} %c'est le dessin
+
+\count2=\wd2 %c'est la largeur du dessin.
+%\showthe\count2
+\multiply\count2 by-1
+\advance\count2 by\hsize %count2 vaut le reste de la page
+\advance\count2 by-2000000 %c'est pour la marge droite
+\count1=\count2
+\advance\count2 by-2000000 %c'est pour la marge du milieu
+\setbox1=\hbox to\count1sp{ %c'est le texte
+\vbox{\hsize=\count2sp %c'est la largeur
+#1
+}\hfill}
+\count1=\ht1 %c'est la hauteur
+\advance\count1 \dp1
+
+\count2=\ht2
+\advance\count0 \dp2
+
+\ifnum\count2<\count1 \count2=\count1 \fi
+%c'est la + grde des 2 hauteurs
+\vtop to \count2sp {\vfill \box1 \vfill}
+\vtop to \count2sp {\vfill \box2 \vfill}
+}}
+
+%%%% fin macro %%%%
+
+# 8.17 # Comment raliser des diagrammes en btons ?
+----------------------------------------------------
+Il existe le package 'bar', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/, qui offre un environnement
+barenv.
+
+# 8.18 # Comment faire un organigramme ?
+----------------------------------------
+Il existe plusieurs contributions (toutes assez anciennes),
+disponibles sur CTAN, ddies spcifiquement la ralisation
+de diffrents types d'organigrammes :
+* ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/nassflow/
+* ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/rail/
+* ftp://ftp.fdn.org/pub/CTAN/support/flow/
+A priori, le dernier est le plus volu et est bas sur un
+pr-processeur crit en langage C, ce qui fait qu'il offre une
+interface souple et puissante.
+
+# 8.19 # Comment centrer une figure trs large ?
+------------------------------------------------
+Le package 'bigcenter' ci-dessous permet de centrer des figures
+trs larges sans message d'erreur de type overful.
+
+%%%% debut macro %%%%
+%%% ----------debut de bigcenter.sty--------------
+
+%%% nouvel environnement bigcenter
+%%% pour centrer sur toute la page (sans overfull)
+
+\newskip\@bigflushglue \@bigflushglue = -100pt plus 1fil
+
+\def\bigcenter{\trivlist \bigcentering\item\relax}
+\def\bigcentering{\let\\\@centercr\rightskip\@bigflushglue%
+\leftskip\@bigflushglue
+\parindent\z@\parfillskip\z@skip}
+\def\endbigcenter{\endtrivlist}
+
+%%% ----------fin de bigcenter.sty--------------
+%%%% fin macro %%%%
+
+# 8.20 # Comment passer de ps eps ?
+-------------------------------------
+* S. Heiden :
+Pour faire ce travail de transformation il faut interprter TOUT
+le code PostScript d'un fichier PS (tre une imprimante PS en
+gros), identifier la bote englobante de ce qui est compos sur
+UNE page et insrer vers le dbut ou la fin du fichier PS
+original la fameuse ligne de la forme :
+ %%BoundingBox: 72 246 522 597
+qui renseigne les macros graphics, donc dvips, donc l'imprimante
+sur cette fentre de clipping.
+
+Syntaxe: %%BoundingBox: llx lly urx ury
+Qui sont deux points (lower left)(x,y) et (upper right)(x,y)
+dfinissant la fentre. Si on n'est pas, soi-meme, une
+imprimante PostScript on peut faire interprter le code PS
+original par une imprimante qui produira une page. On peut alors
+mesurer la bote englobante et la position de la figure dans la
+page (la portion de toner qui nous intresse) et composer la
+ligne %%BoundingBox en s'exprimant en points d'1/72 de pouces
+et sachant que le systme de coordonnes est :
+- en bas gauche de la page ;
+- vers la droite et vers le haut ;
+- lgrement dcal vers le centre. En effet, une imprimante
+n'imprime jamais sur le bord rel d'une page. Il y a une fentre
+de clipping systmatique matrielle plus petite que la page A4
+et centre. L'origine du systme correspond au coin de la
+feuille ; le dcalage du systme de coordonnes arrive surtout
+sur les coordonnes Y qui dpendent de l'avancement du papier
+contrairement aux X, cals par les bords (qui n'a pas connu de
+vieille imprimante LaserWriter pouvant louper de 5 cm le bord
+infrieur d'une feuille A4 ?-).
+
+Si on fait calculer et imprimer la bbox par l'imprimante (par le
+code de bbfig par ex.), ce problme ne se pose plus. Sans parler
+de ps2epsi qui est la meilleure solution mais alors il faut
+distinguer l'environnement de chaque systme d'exploitation (Unix,
+Mac, PC) et les outils correspondants.
+
+Remarque : Si on a plus d'une figure, que l'on s'intresse la
+ fort amazonnienne ou que l'on est un peu riche, on
+ peut acheter Adobe Distiller ou autre pour faire ce
+ genre de travail. Par ailleurs Ghostview peut jouer
+ le rle de l'imprimante si l'cran est correctement
+ calibr ( vrifier avec xdpyinfo et une rgle...).
+ En gros il faut un outil qui sait composer du
+ PostScript. Aprs, tout dpend de ce qu'il propose.
+
+Suggestions :
+- utiliser l'option "draft" pour que TeX visualise les botes
+englobantes des figures (calcules partir de %%BoundingBox).
+- gnrer du EPSF natif partir de l'outil de dessin plutt que
+de passer par PS->EPSF.
+
+* Le document "Using EPS graphics in LaTeX2e documents" de K.
+Reckdahl rpond galement cette question cf section 3.1
+Converting PS files to EPS.
+
+* ps2epsi, qui est livr avec GhostScript permet de convertir
+du postscript en postscript encapsul.
+
+# 8.21 # Comment changer l'orientation d'une figure ?
+-----------------------------------------------------
+* Le package 'rotfloat' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/rotfloat/ permet de grer la
+rotation des flottants.
+
+* On peut utiliser la commande \rotatebox du package 'graphics'
+de D. Carlisle. Ce package est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/.
+
+Exemple :
+\rotatebox{90}{
+\includegraphics{dessin1.eps}
+}
+%%%% fin exemple %%%%
+
+* La commande \includegraphics du package 'graphicx' peut prendre
+comme paramtre un angle de rotation.
+
+Exemple :
+\begin{figure}
+ \centering
+ \includegraphics[angle=90,width=\textwidth]{dessin.eps}
+\end{figure}
+%%%% fin exemple %%%%
+
+# 8.22 # Comment grer des sous-figures sur plusieurs pages ?
+-------------------------------------------------------------
+Un seul environnement figure ne peut pas s'tendre sur plusieurs
+pages, il faut donc grer le problme la main en instanciant
+les numros " la main".
+
+Exemple :
+\documentclass{article}
+\usepackage{graphicx,subfigure}
+\begin{document}
+
+ \begin{figure}
+ \centering
+ \subfigure[First Part]{%
+ \label{fig:graphics:a}% label for subfigure
+ \includegraphics[width=\textwidth]{box.eps}}%
+ \caption{Large Graphics}%
+ \label{fig:graphics}% label for figure
+ \end{figure}
+
+ \addtocounter{figure}{-1}
+ \begin{figure}
+ \addtocounter{subfigure}{1}
+ \centering
+ \subfigure[Second Part]{%
+ \label{fig:graphics:b}% label for subfigure
+ \includegraphics[width=\textwidth]{box.eps}}%
+ \caption{Large Graphics (con't)}%
+ \end{figure}
+
+\end{document}
+%%%% fin exemple %%%%
+
+# 8.23 # Comment gnrer une liste des figures d'un document ?
+--------------------------------------------------------------
+Il existe pour cela la commande \listoffigures. Elle collecte
+tous les numros de figures ainsi que leur titre et le numro
+de la page o elles apparaissent.
+
+Remarque : une bonne mise jour de cette liste ncessite au
+ moins deux compilations successives.
+
+# 8.24 # Comment faire une figure sous LaTeX ?
+----------------------------------------------
+* On distingue deux techniques majeures :
++ soit on utilise un logiciel de dessin et on inclut une figure
+sous un format dfini (en gnral PostScript ou Encapsulated
+PostScript). Pour une liste de logiciels, voir la question 25.1.
++ on utilise les commandes LaTeX disponibles. L'environnement
+picture permet ainsi de composer des figures comprenant du
+texte, des segments de droites, des cercles et des figures
+gomtriques.
+
+Les commandes LaTeX les plus courantes pour le dessin sont :
++ \put(x, y){objet}
++ multiput
++ \line(x,y){longueur}
++ \vector
++ \shortstack
++ \circle
++ \circle*
+
+Exemple :
+\begin{picture}(largeur, hauteur)
+ \put(0,0){\line(1,0){3}}
+ \put(0,3){\line(1,1){4}}
+\end{picture}
+%%%% fin exemple %%%%
+
+* Le package epic dfinit un ensemble de commandes plus
+complet que l'ensemble par dfaut de LaTeX. Il s'agit des
+commandes : \multiputlist, \matrixput, \grid, \dottedline,
+\dashline, \drawline, \jput, \picsquare et \putfile,
+ainsi que des environnements : dottedjoin, dashjoin et drawjoin.
+
+Exemple :
+\matrixput(0,0)(10,0){6}(0,10){3}{\circle{4}}
+\matrixput(2,0)(10,0){5}(0,10){3}{\line(1,0){6}}
+\matrixput(0,2)(10,0){6}(0,10){2}{\line(0,1){6}}
+%%%% fin exemple %%%%
+
+* PSTricks de T. Van Zandt propose un ensemble trs complet de
+macros TeX qui permettent de jouer avec des dessins
+(dessin, couleur, rotation, superposition, ...). L'ensemble
+PSTricks est compos de plusieurs packages : pstricks, pst-plot,
+multido, pst-node, pst-coil, gradient, colortab, textpath,
+charpath et pst2eps. Une documentation d'une centaine de page
+est galement fournie et ncessaire.
+
+ATTENTION : PSTricks fait appel des macros postscript qui ne
+ sont donc pas toujours visibles dans les previewer
+ de .dvi.
+
+Exemple :
+\psellipse(.5,0)(1.5,1)
+
+\parametricplot[plotstyle=dots,plotpoints=13]%
+ {-6}{6}{1.2 t exp 1.2 t neg exp}
+
+\psshadowbox{\textbf Grest!!}
+
+\pszigzag[coilarm=.5,linearc=.1{<->}(4,0)
+%%%% fin exemple %%%%
+
+# 8.25 # Comment mettre un commentaire ct d'une figure ?
+------------------------------------------------------------
+Pour mettre un commentaire ct d'une figure et pour que le
+texte soit centr verticalement par rapport la figure, il
+faut utiliser des \parbox.
+
+Exemple :
+\begin{tabular}{lc}
+$M=0{,}01$ & \parbox[c]{12cm}{\includegraphics[width=12cm]{fig6a.eps}} \\
+$M=0{,}1$ & \parbox[c]{12cm}{\includegraphics[width=12cm]{fig6b.eps}}
+% etc...
+\end{tabular}
+%%%% fin exemple %%%%
+================================================================
+[9] INCLUSION DE FICHIERS
+================================================================
+
+# 9.1 # Comment inclure des fichiers en mode verbatim ?
+-------------------------------------------------------
+* Le package 'verbatim', de R. Schopf, permet via la commande
+\verbatiminput, qui prend en argument un nom de fichier,
+d'inclure un fichier en mode verbatim. Ce package est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/distribs/ ou ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/.
+
+* L'environnement alltt du package du mme nom (package d J.
+Braams) permet la mme prouesse tout en gardant active
+l'interprtation des commandes LaTeX dont le nom commence par le
+caractre \ (le "backslash" reste actif). Il est disponible dans
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/misc/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/base/.
+
+Exemple :
+\begin{alltt}
+ Notez la diffrence subtile entre $f(x)$ et \(f(x)\) grce
+ l'utilisation du "backslash".
+\end{alltt}
+%%%% fin exemple %%%%
+
+* Les commandes \listinginput et \verbatimtabinput du package
+'moreverb' (disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/) permettent d'inclure des
+documents en mode verbatim avec ou sans numrotation des lignes
+du fichier inclu.
+
+Exemple :
+{
+\small
+\listinginput[5]{10}{totor.c}
+}
+Les paramtres [5] et {10} indiquent que la numrotation des
+lignes doit se faire de 5 en 5 en commenant 10.
+%%%% fin exemple %%%%
+
+* Il existe aussi le package 'verbtext' disponible sur CTAN.
+
+* Le package 'fancyvrb' est galement disponible sur CTAN.
+
+* Pour insrer du code lisp dans un document LaTeX, il existe le
+package 'lispcode' disponible par ftp sur
+ftp://ki-server.informatik.uni-wuerzburg.de/pub/tex/.
+
+* On peut aussi essayer le package 'verbasef' (verbatim
+automatic segmentation of external files) disponible sur CTAN.
+Il utilise l'environnement figure.
+
+* Encore un autre, le package 'cprog' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/ permet d'inclure des morceaux de
+code dans un document et de les grer comme des flottants.
+
+* Le package 'sverb' de M. Wooding propose un environnement
+listing.
+
+# 9.2 # Comment grer un document par parties ?
+-----------------------------------------------
+Pour travailler sur un gros document, il est plus agrable de le
+dcouper en plusieurs fichiers. Il y aura quoiqu'il en soit un
+fichier principal (celui qui comprend le prambule et les
+commandes \begin{document} et \end{document}).
+
+\input{fichier} permet d'inclure le fichier "fichier" dans le
+fichier principal. Cette commande ralise une importation pure
+et simple. Elle est plutt rserve l'importation de fichiers
+de macros.
+
+\include{chapitre} permet d'intgrer le fichier "chapitre.tex"
+dans le document principal en commenant une nouvelle page.
+Cette commande rinitialise la numrotation des titres. Utilise
+avec la commande \includeonly{chapitre}, cette commande mise
+dans le prambule, permet de ne recompiler le fichier principal
+que sur les parties indiques.
+
+Remarque : la commande \include ne permet pas d'intgrer un
+ fichier contenant lui-mme une commande \include.
+
+Exemple :
+\documentclass{report}
+\includeonly{chap1, chap3}
+\begin{document}
+\include{chap1}
+\include{chap2}
+\include{chap3}
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : avec le package 'french', pour que la numrotation
+ des chapitres ne soit pas rinitialise lorsqu'on
+ change de partie, il faut ajouter la commande
+ \noresetatpart en dbut de document aprs le
+ \begin{document}
+
+# 9.3 # Comment isoler une partie d'un fichier ps ou dvi ?
+----------------------------------------------------------
+Il faut utiliser un outil qui permet de dcouper en page :
++ un fichier postscript,
+* il s'agit des outils PSnup, PStoPS, PSSelect, qui ont t ports
+sur Mac, aussi bien pour MPW qu'en "stand-alone" (dans la
+distribution CMacTeX)
+* on peut galement utiliser ghostview (save marked pages)
+disponible par ftp sur
+ftp://iphthf.physik.uni-mainz.de/pub/gv/
+
++ un fichier dvi ?
+DVIDVI pour MPW (utilitaire qui fait bien d'autres choses que
+de dcouper) doit permettre de faire cela.
+
+# 9.4 # Comment inclure un fichier PICT ?
+-----------------------------------------
+On peut utiliser la commande \special{pictfile mondessin.pict}
+ou \put(0,0){\special{pict=Mondessin}}.
+
+# 9.5 # Comment spcifier un chemin pour les fichiers inclure ?
+-----------------------------------------------------------------
+* Il suffit d'utiliser la commande \import{chemin}{fichier}.
+Elle vite de prciser le chemin o se trouvent les fichiers
+appels par la commande \input chaque appel.
+
+%%%% debut macro %%%%
+% import.sty: allows input of a file from another directory:
+%
+% \import{path}{file}
+
+\def\import{\begingroup
+ \protected@edef\@tempa{\endgroup
+ \noexpand\@import{\@ifundefined{input@path}{}{\input@path}}%
+ {\@ifundefined{Ginput@path}{}{\Ginput@path}}}%
+ \@tempa}
+\def\@import#1#2#3#4{%
+ \def\input@path{{#3}#1}\def\Ginput@path{{#3}#2}%
+ \input{#4}%
+ \def\input@path{#1}\ifx\input@path\@empty \let\input@path\@undefined \fi
+ \def\Ginput@path{#2}\ifx\Ginput@path\@empty \let\Ginput@path\@undefined \fi
+}
+%%%% fin macro %%%%
+
+Exemple :
+\import{Chapitres/}{chapitre1}
+%%%% fin exemple %%%%
+
+* Pour les figures, la package 'graphicx' propose la commande
+\graphicspath utiliser en tte de document.
+
+Exemple :
+\graphicspath{{Chapitre1/gfx/}{Chapitre2/gfx/}}
+%%%% fin exemple %%%%
+
+* On peut galement modifier certaines variables
+d'environnement lorsqu'elles existent.
+
+Exemple (UNIX) :
+setenv TEXINPUTS= /home/figures/:"$TEXINPUTS"
+%%%% fin exemple %%%%
+
+================================================================
+[10] HAUTS ET BAS DE PAGES
+================================================================
+
+# 10.1 # Comment dfinir les hauts et bas de page ?
+---------------------------------------------------
+
+Remarque : lorsque le haut ou bas de page dfini est trop grand,
+ on voit apparatre des messages d'erreur du style
+ "Overfull \vbox". Il faut alors redimensionner la
+ longueur correspondante.
+
+ Exemple (dans le prambule) :
+ \addtolength{\headheight}{1.5pt}
+ %%%% fin exemple %%%%
+
+* Par dfaut, LaTeX offre la numrotation des pages en bas de
+page (style plain). Mais, il propose galement 3 autres styles
+de mise en page. Il s'agit des styles :
++ empty (hauts et bas de pages vides),
++ headings(la numrotation des pages apparat en haut ainsi que
+diffrentes informations suivant la classe de document), et
++ myheadings (les commandes \markboth et \markright permettent
+de dfinir les informations qui devront apparatre dans le haut
+de page. \markboth{entte gauche}{entte droite} s'utilise pour
+un document recto-verso alors que \markright{entte}
+s'applique toutes les pages d'un document en simple recto).
+
+L'appel d'un style pour tout le document se fait via la commande
+\pagestyle{style}. La commande \thispagestyle{} permet d'appeler
+un style sur une page particulire.
+
+Remarque : malgr une dclaration globale de style de page, il
+ se peut que des dclarations locales de style soient
+ galement ncessaires, puisque certaines commandes
+ LaTeX rinitialisent le style de la page sur laquelle
+ elles apparassent.
+
+* Le package 'fancyheadings', de P. van Oostrum, est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/fancyheadings/. Il est
+compatible LaTeX2.09 et LaTeX2e. Il permet de dfinir des enttes
+et des pieds de page relativement facilement. La dfinition des
+pages spciales se fait par : \thispagestyle{xxx} ou xxx peut
+tre fancy (utilise les dfinitions ci-dessous sur une page en
+respectant le style plain pour les autres ), plain (style TeX)
+ou fancyplain(permet de redfinir le style plain et donc de
+disposer de deux styles : fancy et plain). L'application d'un
+style toutes les pages d'un document s'obtient par
+\pagestyle{nom_style}.
+
+Les macros principales sont :
++ pour les enttes
+\lhead[paire gauche]{impaire gauche}
+\rhead[paire droit]{impaire droit}
+\chead{centre}
++ pour les pieds de page
+\lfoot[paire gauche]{impaire gauche}
+\rfoot[paire droit]{impaire droit}
+\cfoot{centre}
+
+On distingue les styles fancy et plain par :
+\lhead[\fancyplain{paire gauche plain}{paire gauche fancy}]
+{\fancyplain{paire gauche plain}{paire gauche fancy}}
+Le style par dfaut est alors plain.
+
+Ce package dfinit quatre nouvelles longueurs :
++ \headrulewidth
++ \footrulewidth
++ \plainheadrulewidth
++ \plainfootrulewidth
+
+Exemple :
+\documentclass{article}
+\usepackage{fancyheadings}
+\pagestyle{fancy}
+\usepackage{graphicx}
+\renewcommand{\sectionmark}[1]{\markboth{#1}{}}
+\renewcommand{\subsectionmark}[1]{\markright{#1}}
+\rfoot{\leftmark\\\rightmark}
+\lhead{\includegraphics[width=0.5cm]{foobar.ps}}
+
+\begin{document}
+
+ \section{Premire section.}
+ Intro.
+ \subsection{Sous-section.}
+ Texte.
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : sur certaines pages o le style de page est
+ rinitialis par certaines commandes (telles que
+ \tableofcontents), il faut reprciser le style voulu
+ via la commande \thispagestyle.
+
+Exemple :
+\addtocontents{toc}{\protect\thispagestyle{fancyplain}}
+%%%% fin exemple %%%%
+
+* Le package 'fancyhdr' est le successeur du package
+'fancyheadings' pour LaTeX2e. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fancyhdr/.
+
+# 10.2 # Comment obtenir une note de bas de page ?
+--------------------------------------------------
+* La commande \footnote{texte} permet trs facilement d'obtenir
+des notes de bas de page sans se proccuper de leur mise en
+page.
+
+* Le package 'ftn' disponible sur CTAN dans
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/ permet d'tendre la commande
+footnote tous les environnements non flottants.
+
+# 10.3 # Comment mettre les notes de bas de page en fin de document ?
+---------------------------------------------------------------------
+Le package 'endnotes', de J. Lavagnino, disponible sur CTAN
+permet de faire cela.
+
+# 10.4 # Comment rduire les rappels de titres dans un haut ou bas de page ?
+----------------------------------------------------------------------------
+Pour viter que des titres trop longs n'apparaissent dans les
+enttes ou les pieds de pages, il suffit de passer un titre
+plus court en option des commandes de structuration de
+document.
+
+Remarque : dans ce cas, ce sont les titres courts qui
+ apparatront dans la table des matires.
+
+Exemple :
+\documentclass{article}
+\usepackage{fancyheadings}
+\pagestyle{fancy}
+\usepackage{graphicx}
+\renewcommand{\sectionmark}[1]{\markboth{#1}{}}
+\renewcommand{\subsectionmark}[1]{\markright{#1}}
+\rfoot{\leftmark\\\rightmark}
+\lhead{\includegraphics[width=0.5cm]{foobar.ps}}
+
+\begin{document}
+
+ \section[Titre rsum.]{Un titre trop long pour les rappels.}
+ Intro.
+ \subsection{Sous-section.}
+ Texte.
+\end{document}
+%%%% fin exemple %%%%
+
+# 10.5 # Comment rfrencer une note de bas de page ?
+-----------------------------------------------------
+Il suffit simplement de dfinir un label l'intrieur de la
+commande \footnote et de la rfrencer par \ref.
+
+Exemple :
+bla bla bla\footnote{Notons que ce bla l\`a est diff\'erent des
+pr\'ec\'edents\label{footnote-bla}}...
+
+[...]
+
+..., comme l'indique la note~\ref{footnote-bla}, ...
+%%%% fin exemple %%%%
+
+# 10.6 # Comment supprimer la numrotation des pages ?
+------------------------------------------------------
+* Pour supprimer la numrotation des pages, il faut utiliser la
+commande \pagestyle{empty}. Si elle ne suffit pas, il faut en
+plus utiliser \thispagestyle{empty} sur les pages o la
+numrotation subsiste. Ce comportement se justifie par le
+fait que certaines commandes comme \tableofcontents ou \chapter
+rinitialisent le style de page sur laquelle ils apparaissent.
+
+* On peut galement redfinir le style plain empty
+\let\ps@plain=\ps@empty.
+
+* Le package 'nopageno' de D. Carlisle, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/carlisle/, de supprimer la
+numrotation de toutes les pages mme celles qui rinitialisent
+le style de page.
+
+# 10.7 # Comment numroter les pages par rapport la dernire ?
+----------------------------------------------------------------
+Pour pouvoir rfrencer les pages d'un document par rapport la
+dernire page (e.g. page 54/345), il faut utiliser le package
+'lastpage' (disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/lastpage/).
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\usepackage{lastpage}
+
+\makeatletter
+\renewcommand{\@evenfoot}%
+ {\hfil \upshape page {\thepage} de \pageref{LastPage}}
+\renewcommand{\@oddfoot}{\@evenfoot}
+\makeatother
+
+\begin{document}
+Texte.
+\end{document}
+%%%% fin exemple %%%%
+
+Si l'on ne dispose pas du package 'lastpage', on peut dfinir ce
+label " la main" en ajoutant \label{LastPage} juste avant
+\end{document} ou encore en utilisant la commande
+\AtEndDocument{\label{LastPage}} dans le prambule du document.
+
+# 10.8 # Comment supprimer le trait de sparation des notes de bas de page ?
+----------------------------------------------------------------------------
+Il suffit de mettre dans le prambule :
+\renewcommand{\footnoterule}{}
+
+# 10.9 # Comment modifier la numrotation des pages ?
+-----------------------------------------------------
+* Il faut modifier la commande \thepage.
+
+Exemple (P. van Oostrum) :
+\documentclass{report}
+\usepackage{french}
+
+\makeatletter
+\renewcommand{\thepage}{\thechapter-\arabic{page}}
+% chapter-page numbering
+\@addtoreset{page}{chapter}
+% reset page number when chapter is stepped
+% The next magic makes the page counter be reset to one rather
+% than zero
+\def\@stpelt#1{\global\csname c@#1\endcsname
+ \expandafter\ifx \csname#1\endcsname \page
+ \@ne
+ \else
+ \z@ \fi}
+\makeatother
+\begin{document}
+\chapter{Introduction}
+Texte.
+\end{document}
+%%%% fin exemple %%%%
+
+* Il existe galement le package ci-dessous de A. Kielhorn.
+%%%% debut macro %%%%
+%%
+%% This is page-per-chapter-package
+%% version 2.0
+%%
+%% Don't use it with refrep!
+%% Refrep has these commands already implemented
+%%
+%% This version forces openright!!
+%%
+%% Index-commands should work in chapters and appedices,
+%% they will not work as expected in the preface when the
+%% pagenumbering is not arabic. (MakeIndex can't sort roman-
+%% numbers)
+%%
+%% Bugs:
+%% The index is sortet according to the pagenumber
+%% without looking at the chapternumber.
+%% I don't think MakeIndex could handle that.
+%%
+
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{pagepc}[1995/05/13]
+
+\@ifundefined{chapter}
+{\PackageError{pagepc}{%
+ You can't number your pages per chapter\MessageBreak when you
+ have no chapters
+ }{%
+ Use ``report'' or ``book'' instead.
+ }
+}%
+{}
+
+%% Reset the pagecounter to 1 at the start of a new chapter
+%%
+\let\ppchapter=\@chapter
+\def\@chapter{\if@pageperchapter\setcounter{page}{1}\fi
+ \ppchapter}
+
+%% Force a pagebreak at the start of the appendix, otherwise
+%% the number of the page right before the appendix comes
+%% out wrong
+%%
+\let\ppappendix=\appendix
+\def\appendix{\if@pageperchapter\newpage\fi\ppappendix}
+
+\newif\if@pageperchapter \@pageperchapterfalse
+
+%% This command enables Page-per-Chapter, it is *not* on by
+%% default to allow roman pagenumbers in the preface
+%% (see sample-document)
+%%
+\newcommand{\pageperchapter}
+ {\@pageperchaptertrue
+ \@openrighttrue
+ % Remember old setting for chapter 0 = preface
+ \let\ppthepage=\thepage
+ % The new number needs more space
+ \renewcommand\@pnumwidth{2.55em}
+ % Here it comes :-)
+ \renewcommand\thepage{%
+ \ifnum \c@chapter = \z@
+ \ppthepage
+ \else
+ \thechapter\ -- \arabic{page}
+ \fi
+ }
+ }
+
+%% This is a hack to make MakeIndex happy :-(
+%% You can't use the |-form of an indexentry because
+%% it is used to store the chapternumber.
+%%
+\def\@wrindex#1{%
+ \ifnum \c@chapter = \z@
+ \protected@write\@indexfile{}%
+ {\string\indexentry{#1}{\arabic{page}}}%
+ % The above is wrong if pagenumbering!=arabic,
+ % but I think this is better than nothing.
+ \else
+ \protected@write\@indexfile{}%
+ {\string\indexentry{#1|ppc{\thechapter}}{\arabic{page}}}%
+ \fi
+ \endgroup
+ \@esphack
+}
+
+%% This prints the pagenumber in the index
+%%
+\def\ppc#1#2{#1 -- #2}
+
+\endinput
+%%%% fin macro %%%%
+
+* Pour changer la valeur du compteur de page, il suffit
+d'utiliser :
+\setcounter{page}{17}.
+
+# 10.10 # Comment supprimer les enttes et bas de page de pages vierges ?
+-------------------------------------------------------------------------
+Lorsqu'on utilise l'option 'openright' pour faire dbuter un
+nouveau chapitre sur une page de droite dans un document
+recto-verso, pour ne pas afficher les enttes et bas de page sur
+une page de gauche reste vierge, on peut utiliser la commande
+suivante (cf. LaTeX Companion) :
+
+\newcommand{\clearemptydoublepage}{%
+ \newpage{\pagestyle{empty}\cleardoublepage}}
+
+Il est alors ncessaire d'utiliser cette commande avant
+la commande \chapter.
+
+# 10.11 # Comment grer des en-ttes avec des environnements verbatim multi-pages ?
+-----------------------------------------------------------------------------------
+Le problme consiste inclure un fichier avec la commande
+\input dans un haut ou bas de page alors que le corps du
+document comprend des environnements verbatim qui s'talent sur
+plus d'une page. Dans ce cas, LaTeX au lieu d'interprter la
+commande \input fait un copier-coller du contenu du fichier
+appel par la commande \input (c'est comme s'il tait en mode
+verbatim au moment de traiter le \input).
+
+La solution consiste utiliser une bote via \savebox.
+
+Remarque : cela ne marche que si les informations imprimer ne
+ varient pas au fil des pages.
+
+Exemple :
+\newsavebox{\logo}
+\savebox{\logo}[2cm][c]{\input{logo-late.pstex_t}}
+%%%% fin exemple %%%%
+
+# 10.12 # Comment utiliser \footnote dans un titre ?
+----------------------------------------------------
+* Il faut utiliser la commande \protect.
+
+Exemple :
+ \section{Titre de section\protect\footnote{Commentaire sur
+ ce titre.}.}
+%%%% fin exemple %%%%
+
+ATTENTION : le problme dans ce cas est que la note apparatra
+ aussi bien dans l'en-tte si l'en-tte rappelle le
+ titre des sections que dans la table des matires.
+ Pour supprimer ces apparitions il faut alors
+ utiliser la mme technique que pour les titres
+ rsums :
+ \section[foo]{foo\protect\footnote{foooo}}
+
+* Il existe galement le package 'stblftnt' de R. Fairbairns
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ qui
+gre le problme nonc ci-dessus sans avoir rcrire tout
+le titre.
+
+# 10.13 # Comment placer les notes de bas de page les unes ct des autres ?
+------------------------------------------------------------------------------
+Il faut utiliser le package 'footnote', de R. Fairbairns,
+disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/footnote/ avec l'option para :
+\usepackage[para]{footnote}.
+
+# 10.14 # Comment rinitialiser le compteur de note de bas de page chaque page ?
+----------------------------------------------------------------------------------
+* Il faut utiliser le package 'footnote', de R. Fairbairns,
+disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/footnote/ avec l'option
+perpage : \usepackage[perpage]{footnote}
+
+* Le package 'footnpag' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/footnpag/ permet galement de
+faire cela.
+
+# 10.15 # Comment modifier le style des notes de bas de page ?
+--------------------------------------------------------------
+* Le package 'footmisc' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/footmisc/ permet de dfinir son
+propre style de note de bas de page.
+
+* Le package 'ftnright' de F. Mittelbach redfinit le placement
+des notes de bas de page dans un document multi-colonnes. Lors
+de l'utilisation de ce package, les notes de bas de page
+appeles dans une page seront runies et places la fin de la
+dernire colonne de cette page.
+
+Remarque : Lorsque plusieurs packages sont utiliss
+ simultanment dans un mme document, ftnright doit,
+ si possible, tre appel en dernier.
+
+# 10.16 # Comment utiliser le mode verbatim dans une note de bas de page ?
+--------------------------------------------------------------------------
+Par dfaut, le mode verbatim n'est pas accessible dans une note
+de bas de page (et de manire gnrale inutilisable dans un
+argument d'une autre commande).
+* On peut alors le forcer par :
+\DeclareRobustCommand\espacement{{\fontencoding{OT1}
+\selectfont \texttt{\char32}}}
+* ou utiliser
+\tt sous LaTeX2.09
+\texttt sous LaTeX2e
+
+# 10.17 # Comment viter qu'une note de bas de page s'tale sur plusieurs pages ?
+---------------------------------------------------------------------------------
+* La commande \samepage peut permettre de forcer LaTeX ne
+pas couper le contenu d'une note de bas de page.
+
+Exemple sans la commande :
+Texte texte texte (1). Texte texte texte (2). Texte texte texte
+(3). Texte texte texte (4). Texte texte texte (5). Un autre
+texte\footnote{Un long long long long long long long long long
+long long long long long long long long long long long long long
+long long long long long long long long long long long long long
+long long long long long commentaire sur cet autre texte.}.
+Texte texte texte (6). Texte texte texte (7). Texte texte texte
+(8). Texte texte texte (9). Texte texte texte (10). Texte texte
+texte (11). Texte texte texte (12). Texte texte texte (13).
+Texte texte texte (14). Texte texte texte (15). Texte texte
+texte (16). Texte texte texte (17). Texte texte texte (18).
+Texte texte texte (19). Texte texte texte (20). Texte texte
+texte (21). Texte texte texte (22).
+%%%% fin exemple %%%%
+
+Exemple avec :
+Texte texte texte (1). Texte texte texte (2). Texte texte texte
+(3). Texte texte texte (4). Texte texte texte (5). Un autre
+texte\samepage\footnote{Un long long long long long long long
+long long long long long long long long long long long long long
+long long long long long long long long long long long long long
+long long long long long long long commentaire sur cet autre
+texte.}. Texte texte texte (6). Texte texte texte (7). Texte
+texte texte (8). Texte texte texte (9). Texte texte texte (10).
+Texte texte texte (11). Texte texte texte (12). Texte texte
+texte (13). Texte texte texte (14). Texte texte texte (15).
+Texte texte texte (16). Texte texte texte (17). Texte texte
+texte (18). Texte texte texte (19). Texte texte texte (20).
+Texte texte texte (21). Texte texte texte (22).
+%%%% fin exemple %%%%
+
+* On peut galement utiliser une \parbox mais cela peut modifier
+la structure de la page (empitement du bas de page).
+
+Exemple :
+\footnote{\parbox[t]{0.94\linewidth}{This is a footnote ...}
+%%%% fin exemple %%%%
+
+* L'emploi de la commande \enlargethispage peut galement
+suffire.
+
+* Une solution plus globale (et non pas au cas par cas comme les
+solutions prcdentes) consiste redfinir la pnalit associe
+ \interfootnotelinepenalty. Cela permet de relcher le critre
+de beaut associ au placement des bas de page.
+
+Exemple :
+Mettre dans le prambule \interfootnotelinepenalty=10000.
+%%%% fin exemple %%%%
+
+Remarque : \raggedbottom permet en plus LaTeX de ne pas
+ s'inquiter si le corps de la note n'apparat pas
+ sur la mme page que son appel.
+
+================================================================
+[11] LATEX, LE FRANAIS ET LES AUTRES LANGUES
+================================================================
+
+# 11.1 # Comment franciser un document LaTeX ?
+----------------------------------------------
+* 'babel' version 3.6 disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/babel/, est un package de J. Braams.
+babel permet de composer des documents multilingues. Son appel
+sous LaTeX2e se fait par \usepackage[langue_1, langue_2, ...,
+langue_n]{babel}.
+
+Parmi les langues actuellement disponibles, on peut citer
+english, german, italian, french, franais. Le changement de
+langue se fait via la commande \selectlanguage.
+
+Exemple :
+\selectlanguage{spanish}
+%%%% fin exemple %%%%
+
+La langue par dfaut est la dernire de la liste passe en
+paramtre babel (langue_n dans l'exemple prcdent).
+
+Ce package est le plus courant sur le plan international mais il
+est souvent contest en France. On lui prfre alors le package
+'french'.
+
+* Le package 'french' de B. Gaulle est disponible par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/french/ ou sur
+ftp://ftp.loria.fr/pub/ctan/language/french/.
+
+Lors de l'installation, respectez les instructions d'installation
+accompagnant french.sty (une FAQ est galement disponible). Le
+fichier des motifs de csure est dsormais unique (frhyph.tex),
+que l'on travaille avec le codage de fontes T1 ou OT1 (avec
+option MlTeX).
+
+Vous pouvez galement utiliser la srie de commandes
+suivantes, gentiment envoyes par Denis Barbier:
+
+---------- citation ----------
+ make -f Makefile.unx ALLTEXPATH=/usr/share/texmf \
+ install-hyphen install-config install-base install-index
+ texhash
+
+Puis modifier le fichier /usr/share/texmf/web2c/fmtutil.cnf et
+ajouter
+la ligne ci-dessous:
+frlatex tex language.dat -mltex frlatex.ini
+
+Taper ensuite
+ fmtutil --byfmt frlatex
+ texlinks
+
+La commande pour compiler du LaTeX avec french est alors
+frlatex.
+------------- fin -------------
+
+Remarque : Dans un fichier source (.tex), il est conseill de
+ charger french aprs tous les autres packages.
+
+french prend notamment en charge la mise en page, la traduction
+des balises LaTeX visibles dans le document final (Chapitre,
+Table des matires, ...), ....
+
+ATTENTION : ces deux options (french et babel) ne sont pas
+ toujours parfaitement compatibles (les dernires
+ versions le sont french3,49 et babel 3.6).
+AL: A vrifier...
+
+ + \usepackage[francais]{babel} et
+ \usepackage[frenchb]{babel} font appel l'option
+ frenchb maintenue par D. Flipo.
+ + \usepackage[french]{babel} fait appel au package
+ french de B. Gaulle condition que french ait t
+ install (et plus particulirement french.ldf)
+ + les versions de tous ces packages sont trs
+ importantes (babel, frenchb, french) pour une bonne
+ coexistence. Une version 3.6 beta de Babel est sur
+ CTAN mais il parat qu'il y avait un problme avec
+ french. Babel 3.5e et french V3.46 collaborent assez
+ bien dans tous les sens.
+ + les fichiers de csure sont les mmes pour babel
+ et pour french.
+
+ATTENTION : les dernires distributions de french (V4 et
+ post) ne sont plus compatibles LaTeX 2.09 !
+
+# 11.2 # Comment corriger les coupures de mots accentus ?
+----------------------------------------------------------
+* Une solution consiste utiliser MlTeX (multilingual TeX).
+C'est le moteur TeX de M. Ferguson. Il permet en particulier de
+grer les coupures de mots accentus. Certaines des ides
+utilises dans ce moteur ont d'ailleurs t reprises par la
+suite dans TeX V3.
+
+* Suivant la fonte avec laquelle on travaille (i.e. suivant
+qu'elle dispose des caractres accentus ou non), il peut
+exister des problmes d'interaction entre les lettres accentues
+et les rgles de coupure des mots. En effet, l'utilisation d'une
+fonte 7 bits impose que les caractres accentus soient
+fabriqus par la macro \accent de TeX qui inhibe toute coupure
+pour la suite du mot.
+
+En LaTeX2e l'utilisation de fontes respectant la norme T1
+(codage de Cork + 8 bits) permet d'viter ces problmes. Il faut
+alors faire appel au package 'fontenc' :
+\usepackage[T1]{fontenc}
+Ce package ncessite que des fontes encodes T1 (suffisamment
+rcentes) aient t installes (fontes dc par exemple).
+
+Il faut en outre utiliser des modles de coupure de mot encodes
+T1. Il existe pour cela deux fichiers disponibles sur CTAN. Il
+s'agit des fichiers fr8hyph.dc (ou mieux f8hyph, beaucoup plus
+rcent) pour un codage 8 bits (fonte avec caractres accentus
+telle que dc) et fr7hyph (respectivement f7hyph) pour un codage
+7 bits (accents TeX). L'association GUTenberg propose galement
+de tels fichiers (cf. french paragraphe 11.1).
+
+* Il peut y avoir galement un problme de versions,
+l'algorithme de coupure des mots a chang entre les versions
+2.9 et 3.0. Ainsi si vous utilisez Tex V.3.0 ou plus, il faut
+veiller ce que les fichiers plain.tex et lplain.tex soient
+galement en version 3.0 ou plus.
+
+# 11.3 # Comment utiliser les lettres accentues ?
+--------------------------------------------------
+* Les accents disponibles sous LaTeX sont prsents la
+question 29.57.
+
+* Pour viter ces commandes barbares d'accentuation des
+caractres, on peut utiliser une fonte contenant toutes les
+lettres accentues ncessaires (code 8 bits). Si besoin, il faut
+prciser un codage d'entre via l'instruction :
+\usepackage[codage d'entre]{inputenc}
+
+L'option est rendue ncessaire par le fait que les codes de
+caractres au-del de 127 sont diffrents sous Dos, MacOS et
+Unix... Ainsi, le codage preciser est latin1 pour un systme
+Unix ou un PC sous Windows, applemac sous Mac adapt au franais
+ou encore cp850 pour le code-page 850 sur PC (sous MS-DOS). Il
+existe galement ansinew, cp438, latin2 selon les systmes.
+
+Exemple :
+\usepackage[applemac]{inputenc}
+%%%% fin exemple %%%%
+
+ATTENTION : inputenc.sty casse les efforts faits par mlTeX
+ lorsqu'on utilise les fontes codes OT1 (fontes CMR
+ ou PostScript).
+
+* mapcodes de M. Piotrowski autorise galement un grand nombre
+de codages de caractres (iso8859-1 (latin1), iso8859-2
+(latin2), ibm850 ou 852, hproman8, etc).
+
+# 11.4 # Comment composer du texte en grec moderne ou classique ?
+-----------------------------------------------------------------
+Il suffit d'utiliser l'option greek du package babel disponible sur CTAN. Son
+site primaire est ftp://obelix.ee.duth.gr/pub/TeX/. La version 1.0 fournie
+avec babel ne supporte pas les accents ni les marques de respirations par
+contre la toute nouvelle version 1.1 les supporte.
+
+On trouvera un fichier de csure de mots dans
+ftp://obelix.ee.duth.gr/pub/TeX/hyphen.greek.
+
+# 11.5 # Comment composer du texte en hbreu moderne ou classique ?
+-------------------------------------------------------------------
+Il suffit d'utiliser le package ArabTeX 3.05 disponible sur CTAN. Son site
+primaire est ftp://ftp.informatik.uni-stuttgart.de/pub/arabtex/.
+Ce package permet la vocalisation mais pas les marques de
+cantillation.
+
+Exemple:
+\documentclass{article}
+\usepackage{arabtex,hebtex}
+\setcode{standard}
+\sethebrew
+
+\begin{document}
+Voici du texte en hbreu
+\begin{arabtext}
+yOm tOb
+\end{arabtex}
+Fin du texte en hbreu
+\end{document}
+%%%% fin exemple %%%%
+
+# 11.6 # Comment composer du texte en arabe ?
+---------------------------------------------
+Il suffit d'utiliser le package ArabTeX 3.05 disponible sur CTAN. Son site
+primaire est ftp://ftp.informatik.uni-stuttgart.de/pub/arabtex/.
+
+# 11.7 # Comment dfinir les csures de groupes de mots conjugus avec un trait d'union ?
+-----------------------------------------------------------------------------------------
+(B. Gaulle) Par dfaut, TeX coupe tout mot compos l'endroit
+exact du trait d'union et uniquement cet endroit. Mais cela
+peut se modifier. Dans ce but, j'ai ajout french (V4,02) une
+commande \allowhyphens qui permet de laisser TeX le choix des
+autres coupures dans le mot.
+
+Remarque : la commande \hypenation ne permet pas d'intgrer un
+ trait d'union car ce caractre sert indiquer un
+ point de coupure et uniquement cela.
+
+Voici donc la solution :
+\showhyphens{{dfinissez\allowhyphens-le}
+donne alors comme points de coupure : d-fi-nis-sez-le
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part4 b/help/LaTeX-FAQ-francaise/part4
new file mode 100644
index 0000000000..36dd3e146d
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part4
@@ -0,0 +1,2906 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!howland.erols.net!cpk-news-hub1.bbnplanet.com!news.gtei.net!opentransit.net!proxad.net!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:18 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - parties 12 a 15
+Message-ID: <faq-fctt-p420010608133118@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p420010501143416@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 2894
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23524 fr.usenet.reponses:20390
+
+Archive-name: fr/faq-latex-francaise/part4
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+================================================================
+[12] MATHMATIQUES
+================================================================
+
+# 12.1 # Comment passer en mode mathmatique ?
+----------------------------------------------
+* Pour les mathmatiques en ligne, il faut utiliser :
+$ et $ ou
+\( et \) ou
+\begin{math} et \end{math}
+
+Exemple :
+Rsoudre l'quation~:
+$ 3 + 4 x = 0 $
+%%%% fin exemple %%%%
+
+* Pour les formules isoles, il faut utiliser les modes :
+ $$ et $$ ou
+ \[ et \] ou
+ \begin{displaymath} et \end{displaymath}.
+
+Exemple :
+Rsoudre l'quation~:
+$$
+3 + 4 x = 0
+$$
+%%%% fin exemple %%%%
+
+* Avec l'environnement \displaystyle, on peut quand mme avoir
+une formule de style isole dans le texte mais cela modifie
+localement les interlignes.
+
+Exemple :
+Texte texte texte texte texte texte texte texte texte texte
+texte texte texte texte texte texte texte texte texte texte
+texte texte texte texte texte texte texte texte texte texte
+$\displaystyle \sum_{i=0}^n u_i $ texte texte texte texte
+texte texte texte texte texte texte texte texte texte texte
+%%%% fin exemple %%%%
+
+* De mme, on peut utiliser $\sum\limits{i=0}^n u_i$.
+
+* Pour crire des mathmatiques sous LaTeX2e, les packages
+'amsmath', disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, et
+'amssymb' sont incontournables. En LaTeX2.09, on peut utiliser
+'amstex', disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/amstex/, 'amsby' et
+'amsopn' mais il faut savoir que amstex est obsolte.
+
+ATTENTION : en mode mathmatique, la gestion des espaces et des
+ retours la ligne est entirement prise en charge
+ par LaTeX (cf. question 12.33). En outre, les lignes
+ vides ne sont pas autorises.
+
+# 12.2 # Qu'est que AMS-LaTeX ?
+-------------------------------
+AMS-TeX est un terme utilis pour dsigner un ensemble de
+fichiers distribus par l'American Mathematical Society (AMS).
+AMS-LaTeX s'appuie sur TeX et LaTeX2e. AMS-LaTeX est
+principalement d a F. Mittelbach et R. Schopf. C'est un outil
+complmentaire LaTeX pour crire des mathmatiques (il devient
+d'ailleurs rapidement indispensable).
+
+Il existe une FAQ disponible sur
+ftp://ftp.fdn.org/pub/CTAN//macros/latex/packages/amslatex/math/amslatex.faq.
+
+Les packages proposs sont 'amsmath' (complet), 'amstext' (pour
+crire du texte en mode mathmatique), 'amsbsy' (pour les
+symboles gras), 'amsopn' (pour la dclaration d'oprateurs),
+'amsthm' (pour les environnements proof et theorem), 'amsintx'
+(pour tendre la syntaxe des sommes et intgrales), 'amscd'
+(pour les diagrammes commutatifs), 'amsxtra' et 'upref' (pour
+les rfrences croises).
+
+Ces packages sont disponibles par ftp sur
+ftp://e-math.ams.org/pub/tex/amslatex/. Il faut galement
+rcuprer les fontes associes dans
+ftp://e-math.ams.org/pub/tex/amsfonts/,
+ftp://e-math.ams.org/pub/tex/amsltx11/ et
+ftp://e-math.ams.org/pub/tex/amstex/. Sur CTAN, les
+rpertoires correspondants sont
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/amslatex/, ftp://ftp.fdn.org/pub/CTAN/fonts/amsfonts/,
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/amslatex/ et
+ftp://ftp.fdn.org/pub/CTAN/macros/amstex/. Il existe galement le site WEB
+http://www.ams.org/tex.
+
+# 12.3 # Comment crire les symboles d'ensembles ?
+--------------------------------------------------
+Un peu d'histoire (T. Bouche) : au temps jadis, dans les livres,
+les symboles d'ensemble taient imprims en gras pour qu'on les
+voie bien. Problme, comment, lorsque l'on crit sur un tableau
+noir, maintenir ce type de distinction ? En fait, au lieu
+d'craser la craie avec force sur le tableau pour largir un
+trait, on a dcid de le doubler. Ce qui est comique, c'est
+qu'en retour, les livres se sont mis copier l'usage des profs,
+et ont distingu le "gras" (bold), du "gras de tableau" qui est
+une fonte part (dessin normal barre redouble).
+
+* Les symboles mathmatiques d'ensemble et bien d'autres sont
+disponibles par dfaut dans les fontes AMS : famille msam
+(e.g., msam10 pour 10pt) et msbm. Ces fontes sont disponibles
+par ftp anonyme sur ftp://e-math.ams.org/pub/tex/amsfonts/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amsfonts/sources/symbols/. Pour avoir accs
+aux symboles, il faut alors utiliser les packages 'amsfonts' et
+'amssymb'.
+
+Exemple :
+soit on dfinit une commande spciale (dans le prambule):
+ \newcommand{\R}{\mathbb{R}}
+
+et on utilise :
+
+ $\R$
+
+soit on tape directement :
+
+ $\mathbb{R}$ (LaTeX2e) ou
+
+ ${\Bbb R}$ (LaTeX2.09)
+%%%% fin exemple %%%%
+
+* Si vous ne disposez pas des packages ams vous pouvez au grand
+dam de certains puristes utiliser les commandes :
++ pour les naturels :
+ \def\N{\mbox{I\hspace{-.15em}N}}
++ pour les entiers :
+ \def\Z{\mbox{Z\hspace{-.3em}Z}}
++ pour les reels :
+ \def\R\mbox{I\hspace{-.15em}R}}
++ pour les complexes :
+ \def\C{\mbox{l\hspace{-.47em}C}}
++ ...
+
+Il faut savoir dans ce cas que leur utilisation est limite :
+pas de mise en indice, exposant, etc.
+
+* C. Fiorio (fiorio@math.tu-berlin.de) propose galement un
+certain nombre de macros (LaTeX2e) :
+
+%%%% debut macro %%%%
+%
+%% Les ensembles de nombres
+%
+\def\nbR{\ensuremath{\mathrm{I\!R}}} % IR
+\def\nbN{\ensuremath{\mathrm{I\!N}}} % IN
+\def\nbF{\ensuremath{\mathrm{I\!F}}} % IF
+\def\nbH{\ensuremath{\mathrm{I\!H}}} % IH
+\def\nbK{\ensuremath{\mathrm{I\!K}}} % IK
+\def\nbL{\ensuremath{\mathrm{I\!L}}} % IL
+\def\nbM{\ensuremath{\mathrm{I\!M}}} % IM
+\def\nbP{\ensuremath{\mathrm{I\!P}}} % IP
+%
+% \nbOne : 1I : symbol one
+\def\nbOne{{\mathchoice {\rm 1\mskip-4mu l} {\rm 1\mskip-4mu l}
+{\rm 1\mskip-4.5mu l} {\rm 1\mskip-5mu l}}}
+%
+% \nbC : Nombres Complexes
+\def\nbC{{\mathchoice {\setbox0=\hbox{$\displaystyle\rm C$}%
+\hbox{\hbox to0pt{\kern0.4\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\textstyle\rm C$}\hbox{\hbox
+to0pt{\kern0.4\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptstyle\rm C$}\hbox{\hbox
+to0pt{\kern0.4\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptscriptstyle\rm C$}\hbox{\hbox
+to0pt{\kern0.4\wd0\vrule height0.9\ht0\hss}\box0}}}}
+%
+% \nbQ : Nombres Rationnels Q
+\def\nbQ{{\mathchoice {\setbox0=\hbox{$\displaystyle\rm
+Q$}\hbox{\raise
+0.15\ht0\hbox to0pt{\kern0.4\wd0\vrule height0.8\ht0\hss}\box0}}
+{\setbox0=\hbox{$\textstyle\rm Q$}\hbox{\raise
+0.15\ht0\hbox to0pt{\kern0.4\wd0\vrule height0.8\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptstyle\rm Q$}\hbox{\raise
+0.15\ht0\hbox to0pt{\kern0.4\wd0\vrule height0.7\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptscriptstyle\rm Q$}\hbox{\raise
+0.15\ht0\hbox to0pt{\kern0.4\wd0\vrule height0.7\ht0\hss}\box0}}}}
+%
+% \nbT : T
+\def\nbT{{\mathchoice {\setbox0=\hbox{$\displaystyle\rm
+T$}\hbox{\hbox to0pt{\kern0.3\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\textstyle\rm T$}\hbox{\hbox
+to0pt{\kern0.3\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptstyle\rm T$}\hbox{\hbox
+to0pt{\kern0.3\wd0\vrule height0.9\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptscriptstyle\rm T$}\hbox{\hbox
+to0pt{\kern0.3\wd0\vrule height0.9\ht0\hss}\box0}}}}
+%
+% \nbS : S
+\def\nbS{{\mathchoice
+{\setbox0=\hbox{$\displaystyle \rm S$}\hbox{\raise0.5\ht0%
+\hbox to0pt{\kern0.35\wd0\vrule height0.45\ht0\hss}\hbox
+to0pt{\kern0.55\wd0\vrule height0.5\ht0\hss}\box0}}
+{\setbox0=\hbox{$\textstyle \rm S$}\hbox{\raise0.5\ht0%
+\hbox to0pt{\kern0.35\wd0\vrule height0.45\ht0\hss}\hbox
+to0pt{\kern0.55\wd0\vrule height0.5\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptstyle \rm S$}\hbox{\raise0.5\ht0%
+\hboxto0pt{\kern0.35\wd0\vrule height0.45\ht0\hss}\raise0.05\ht0%
+\hbox to0pt{\kern0.5\wd0\vrule height0.45\ht0\hss}\box0}}
+{\setbox0=\hbox{$\scriptscriptstyle\rm S$}\hbox{\raise0.5\ht0%
+\hboxto0pt{\kern0.4\wd0\vrule height0.45\ht0\hss}\raise0.05\ht0%
+\hbox to0pt{\kern0.55\wd0\vrule height0.45\ht0\hss}\box0}}}}
+%
+% \nbZ : Entiers Relatifs Z
+\def\nbZ{{\mathchoice {\hbox{$\sf\textstyle Z\kern-0.4em Z$}}
+{\hbox{$\sf\textstyle Z\kern-0.4em Z$}}
+{\hbox{$\sf\scriptstyle Z\kern-0.3em Z$}}
+{\hbox{$\sf\scriptscriptstyle Z\kern-0.2em Z$}}}}
+%%%% fin macro %%%%
+
+Exemple :
+$ \nbN $ pour les entiers naturels
+%%%% fin exemple %%%%
+
+* Autres alternatives :
+en metafont:
++ les fontes 'bbold' d'A. Jeffrey (une sorte de Futura vraiment
+doubl par endroit, pas dtour - mais du coup pas du tout du
+mme style que les autres lettres du mode mathmatique)
+
+Exemple :
+\font\bbold=bbold12
+\newcommand{\R}{\mbox{\bbold R}}
+%%%% fin exemple %%%%
+
+en postscript (produits commerciaux)
++ dextor outline
++ Mathematical Pi (une sorte d'helvetica doubl par endroit)
+
+* Le package 'bbm' disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/cm/bbm/
+propose certaines variantes pour les fontes Computer Modern.
+
+# 12.4 # Comment numroter les quations ?
+------------------------------------------
+* Sous LaTeX2e, les options de classe leqno et fleqn permettent
+d'indiquer si les numros d'quations doivent apparatre
+droite ou gauche des quations.
+
+Exemple, pour que les numros apparassent gauche :
+\documentclass[leqno]{report}
+\begin{document}
+\begin{eqnarray}
+ x + 4 & = & 0 \\
+ 8 - y & = & 0
+\end{eqnarray}
+%%%% fin exemple %%%%
+
+* Pour supprimer la numrotation des quations, il suffit
+d'ajouter le caractre * aux noms des environnements d'quation.
+
+Exemple :
+\begin{eqnarray*}
+ x + 4 & = & 0 \\
+ 8 - y & = & 0
+\end{eqnarray*}
+%%%% fin exemple %%%%
+
+* Pour supprimer la numrotation d'une ligne particulire dans
+un groupe d'quations, il suffit d'utiliser la commande
+\nonumber (avant les \\). Avec amsmath, il faut utiliser \notag.
+
+* Pour rinitialiser le compteur d'quations dans chaque
+section, il faut inclure :
+%%%% debut macro %%%%
+\makeatletter
+\renewcommand\theequation{\thesection.\arabic{equation}}
+\@addtoreset{equation}{section}
+\makeatother
+%%%% fin macro %%%%
+dans le prambule.
+
+Remarque : dans ce cas, il ne faut pas mettre d'quation dans un
+ chapitre avant la premire section sous peine d'avoir
+ un numro du style 3.0.1.
+
+* Pour modifier le style de numrotation, il faut modifier la
+commande \theequation.
+
+Exemple 1 :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\renewcommand{\theequation}{\thesection \Alph{equation}}
+\begin{document}
+\chapter{Systmes d'quations.}
+ \section{ une variable.}
+ \begin{eqnarray}
+ x + 4 & = & 0 \\
+ x & = & 3
+ \end{eqnarray}
+ \section{ deux variables.}
+ \begin{eqnarray}
+ x + 4 & = & 0 \\
+ 8 - y & = & 0
+ \end{eqnarray}
+\end{document}
+%%%% fin exemple %%%%
+
+Exemple 2 (pour avoir les numros entre crochets) :
+\makeatletter
+\renewcommand{\@eqnnum}{{\normalfont\normalcolor\theequation}}
+\renewcommand{\theequation}{[\arabic{equation}]}
+\makeatother
+
+\begin{document}
+ \begin{eqnarray}
+ x + 4 & = & 0 \\
+ y - 2 & = & 0
+ \end{eqnarray}
+%%%% fin exemple %%%%
+
+* Avec le package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, la commande \numberwithin permet de
+numroter les quations suivant le paragraphe auquel elles
+appartiennent. Il faut alors appeler :
+\numberwithin{equation}{section} dans le prambule.
+
+* Les packages 'seceqn' et 'apeqnum' disponibles sur CTAN
+permettent pour le premier de numroter les quations par
+section et pour le second de numroter individuellement les
+quations dans les annexes.
+
+* Le package 'deleq' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/deleq/ permet de dfinir un label
+par groupe d'quations (4) en plus des labels individuels de
+type (4a), (4b), etc.
+
+* La commande \tag{xxx} du package 'amsmath' sous LaTeX2e permet
+de personnaliser la numrotation des quations.
+
+Exemple : pour permettre deux quations d'avoir le mme
+numro :
+\begin{equation}
+ x - y = 0
+ \label{equa}
+\end{equation}
+...
+\begin{equation}
+ x = y
+ \tag{\eqref{equa}}
+\end{equation}
+%%%% fin exemple %%%%
+
+Remarque : \eqref remplace \ref pour les quations : la fonte
+ utilise est toujours la mme (c'est plus beau).
+
+* Les environnements subequations (du package 'amsmath') et
+subeqnarray (du package 'subeqnarray') permettent de rfrencer
+diffrentes lignes d'un mme groupe d'quations par des indices
+(3.a), (3.b), etc.
++ Sous subequations, une rfrence une ligne particulire
+s'obtient alors par un \label plac sur cette ligne alors qu'une
+rfrence au systme d'quation s'obtient par un \label plac
+immdiatement aprs \begin{subequations}.
+
+Exemple :
+\begin{subequations} \label{E:gp}
+ \begin{gather}
+ x_1 x_2 + x_1^2 x_2^2 + x_3 \label{E:gp1} \\
+ x_1 x_3 + x_1^2 x_3^2 + x_2 \label{E:gp2} \\
+ x_1 x_2 x_3 \label{E:gp3}
+ \end{gather}
+\end{subequations}
+
+[...]
+
+Voir le systme~\ref{E-gp} et en particulier
+l'quation~\ref{E-gp2}.
+%%%% fin exemple %%%%
+
+Remarque : c'est le \\ qui incrmente le compteur des
+ sous-rfrences.
+
++ Sous subeqnarray une rfrence une ligne particulire se
+fait alors par \slabel au lieu de \label.
+
+# 12.5 # Comment aligner des quations ?
+----------------------------------------
+* Pour aligner des quations sur un signe de relation, il suffit
+sous LaTeX d'appeler l'environnement eqnarray avec ou sans la
+commande \lefteqn ou si l'on dispose du package
+'amsmath', disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/,
+d'utiliser un des environnements split, multline, align ou
+flalign.
+
+Exemples :
+
+\begin{align}
+ f(x) & = & x^2 + 8x + 16 \\
+ & = & (x+4)^2
+\end{align}
+
+\begin{eqnarray}
+ \lefteqn{x + 3y - 6z} \\
+ & = & -4a + 5b -7b \\
+ & = & -4a - 2b
+\end{eqnarray}
+
+\begin{align}
+ \begin{split}
+ A &= B + C + D + E + F + G \\
+ &\quad + H + I
+ \end{split} \\
+ F &= G + H
+\end{align}
+%%%% fin exemple %%%%
+
+ * L'environnement equationarray du package 'eqnarray' associe
+ les avantages des environnements eqnarray et array. Il n'est
+ pas limit en nombre de colonnes.
+
+* Pour produire le systme d'quations suivant :
+ x = y + z
+ x1 = y1 + z1
+on peut utiliser l'environnement alignat du package 'amsmath'.
+Toutefois, il faut noter que cet environnement est alors
+dtourn de son utilisation normale. En effet, ce dernier est
+prvu pour aligner des objets diffrents sur des colonnes
+alternativement justifies droite puis gauche. L'utilisation
+de colonnes vides permet alors de choisir la justification
+voulue. D'autre part l'utilisation de {} permet d'obtenir des
+espacements "normaux".
+
+Exemple :
+\begin{alignat}{2}
+ x & = y &&+ z\\
+ x_1 & = y_1 &&+ z_1
+\end{alignat}
+
+\begin{alignat}{5}
+ 10a& ={}& 3x&& 3y& +{}& 18z&& 2w&\\
+ 6a& ={}& 17x&& & +{}& 5z&& 19w&
+\end{alignat}
+%%%% fin exemple %%%%
+
+* Le package 'mathenv' disponible sur CTAN propose un ventail
+d'environnements mathmatiques pour aligner des entits en
+colonne.
+
+# 12.6 # Comment gnrer des vecteurs ?
+---------------------------------------
+* Il suffit d'utiliser le package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, et d'appeler la commande
+\overrightarrow.
+
+Exemple :
+Le vecteur $\overrightarrow{u}$
+%%%% fin exemple %%%%
+
+* On peut galement dfinir ses propres flches notamment pour
+rgler leur hauteur par rapport aux lettres qu'elles surmontent.
+La solution prsente ci-dessous utilise les packages 'amsmath',
+'amssymb' et 'xy' :
+%%%% debut macro %%%%
+\newcommand{\xyflecheverladroite}
+{\mbox{\xymatrix{*{\hphantom{OM}}\ar[]+L;[]+R}}}
+
+\newcommand{\ra}[1]
+{\mathchoice
+{\overset{\mbox{\xymatrix{*{\hphantom{\displaystyle #1}}
+\ar[]+L;[]+R}}}{\displaystyle #1}}%
+{\overset{\mbox{\xymatrix{*{\hphantom{\textstyle #1}}
+\ar[]+L;[]+R}}}{\textstyle #1}}%
+{\overset{\mbox{\xymatrix{*{\hphantom{\scriptstyle #1}}
+\ar[]+L;[]+R}}}{\scriptstyle #1}}%
+{\overset{\mbox{\xymatrix{*{\hphantom{\scriptscriptstyle #1}}
+\ar[]+L;[]+R}}}{\scriptscriptstyle #1}}% }
+
+%Pour changer la distance de la flche, on peut procder ainsi.
+%\renewcommand{\ra}[1]
+%{\overset{\raisebox{-1pt}{\mbox{\xymatrix{*{\hphantom{#1}}
+%\ar[]+L;[]+R}}}}{#1}}
+%%%% fin macro %%%%
+
+Exemples :
+$$ \ra{OM} $$
+$\ra{OM}$
+$\ra{OM_i}$
+$$ \ra{OM} _{\ra{OM}_{\ra{OM}}}$$
+%%%% fin exemple %%%%
+
+* Le package 'vector', de N. Efford, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/vector/. Il offre notamment
+un certain nombre de vecteurs utiles aux physiciens et des
+commandes automatiques d'numration des coordonnes.
+
+Exemple :
+$(\irvec[4]x)$
+
+$\bvec{y} = \left[ \cvec{y}{0}{3} \right]$
+%%%% fin exemple %%%%
+
+* Le package 'easyvector' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ permet de dfinir des
+vecteurs suivant une syntaxe de type C.
+
+# 12.7 # Comment crire du texte en mode mathmatique ?
+-------------------------------------------------------
+* La commande \text{xxx} du package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, permet d'inclure du texte dans
+une formule mathmatique sans que les accents et les espacements
+mathmatiques ne soient ncessaires.
+
+* La commande \textrm{xxx} du package 'amsmath' (ou amstext)
+permet en outre de prendre en compte la taille de la fonte
+courante.
+
+Exemple :
+La fonction~: $ f_{\textrm{tracage}} $ sert au trac de
+courbes.
+%%%% fin exemple %%%%
+
+* Il est galement possible d'utiliser la commande \mbox.
+
+Remarque : aucune de ces commandes ne gre les retours la
+ ligne en fin de ligne.
+
+# 12.8 # Comment ajuster la taille de dlimiteurs ?
+---------------------------------------------------
+* Pour ajuster la taille de dlimiteurs tels que les
+parenthses, les accolades, etc, il suffit d'utiliser les
+commandes \left et \right.
+
+Remarque : si l'on veut utiliser un seul dlimiteur (sans son
+ symtrique) il faut utiliser \right. en fermeture.
+
+Exemples :
+$\left( \frac{1}{2} \right)$
+
+$\left \{ \mathrm{et} \right \}$
+
+Rsoudre le systme~:
+\[
+\left \{
+\begin{array}{ccc}
+ x + y & = & 0 \\
+ x - y & = & 0
+\end{array}
+\right.
+\]
+%%%% fin exemple %%%%
+
+Remarque : Pour changer la taille des dlimiteurs de faon
+ relative la taille des donnes qu'ils encadrent,
+ c'est le paramtre \delimitershortfall qui est
+ utilis. Lorsqu'il vaut 0pt, les dlimiteurs qu'il
+ contrle sont au plus aussi grands que le contenu
+ qu'ils encadrent ; pour que les dlimiteurs puissent
+ tre plus grands que leur contenu, il faut donner une
+ valeur ngative \delimitershortfall.
+
+* Pour imposer son propre choix de taille de dlimiteurs
+notamment pour des dlimiteurs imbriqus, il existe les
+commandes \big, \Big, \bigg et \Bigg.
+
+Exemples :
+$\Big( (x+1) (x-1) \Big) ^{2}$
+
+$\big\{\Big\{\bigg\{\Bigg\{$
+%%%% fin exemple %%%%
+
+# 12.9 # Comment changer de fonte en mode mathmatique ?
+--------------------------------------------------------
+* Il faut utiliser les packages 'amsmath' ou 'amssymb' puis :
++ pour du gothique
+\frak{Texte} en LaTeX2.09
+\mathfrak{Texte} en LaTeX2e
+
++ pour du caligraphique gras :
+\boldsymbol{\mathcal{TEXTE}}
+on peut aussi gnrer tout l'alphabet correspondant :
+\DeclareSymbolFont{boldsymbols}{OMS}{cmsy}{b}{n}
+\DeclareSymbolFontAlphabet{\mathbfcal}{boldsymbols}
+puis utiliser la commande \mathbfcal
+
+Remarque : La commande \mathcal ne marche qu'avec des
+ majuscules.
+
++ pour du gras italique :
+\DeclareMathAlphabet\mbi{OML}{cmm}{b}{it}
+ou
+\DeclareSymbolFont{mathbold}{OML}{cmm}{b}{it}
+\DeclareMathSymbol{\biGamma}{\mathord}{mathbold}{0}
+
++ pour des symboles en gras :
+\boldsymbol{\alpha}
+ou
+\DeclareSymbolFont{mathbold}{OML}{cmm}{b}{it}
+\DeclareMathSymbol{\balpha}{\mathord}{mathbold}{11}
+
+Remarque : si cela ne marche pas, c'est que les caractres gras
+ correspondants n'existent pas. Il faut alors soit
+ utiliser la commande \pmb{...} soit utiliser un
+ package supplmentaire tel que 'amsbsy'. Il existe
+ par ailleurs des versions postscript de fontes AMS
+ disponibles sur CTAN.
+
+* Sous LaTeX2e, il existe un certain nombre de commandes de
+changement de fonte. Il s'agit de :
++ mathcal pour du calligraphique (argument en majuscule),
++ mathrm pour du roman,
++ mathbf pour du gras,
++ mathsf pour du sans serif,
++ mathtt pour du typewriter (machine crire),
++ mathnormal pour revenir la fonte par dfaut,
++ mathit pour de l'italique.
+
+* Pour crire toute une formule en gras, on peut aussi utiliser
+la commande \mathversion{xxx} de LaTeX2e. xxx peut valoir bold
+ou normal.
+
+Exemple :
+Une formule importante~:
+\mathversion{bold}
+$$\sum_{i=0}^n u_i + v_i$$
+
+Une formule moins importante~:
+\mathversion{normal}
+$$\sum_{i=0}^n v_i$$
+%%%% fin exemple %%%%
+
+* Le package 'bm' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/bm/ permet de bien grer les
+symboles mathmatiques en gras.
+
+# 12.10 # Comment obtenir le L de la transforme de Laplace ?
+-------------------------------------------------------------
+Pour obtenir le L de la transforme de Laplace, il faut
+utiliser le package 'mathrsfs' puis la commande
+\renewcommand{\L}{\mathscr{L}}.
+
+Remarque : ce package fait appel des fontes particulires
+ qu'il faut galement installer.
+
+# 12.11 # Comment raliser un tableau en mode mathmatique ?
+------------------------------------------------------------
+
+Il faut utiliser l'environnement array.
+
+Exemple :
+Rsultats~:
+\[
+\begin{array}{|c @=c|}
+ \hline
+ \alpha + \beta & 12 \\
+ \hline
+ \sqrt{\gamma} & 36 \\
+ \hline
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+# 12.12 # Comment obtenir d'autres symboles mathmatiques ?
+-----------------------------------------------------------
+* LaTeX propose un grand nombre de commandes de symboles.
+
++ pour les oprateurs binaires :
+ \pm \cap \diamond \oplus
+ \mp \cup \bigtriangleup \ominus
+ \times \uplus \bigtriangledown \otimes
+ \div \sqcap \triangleleft \oslash
+ \ast \sqcup \triangleright \odot
+ \star \vee \wedge \bigcirc
+ \dagger \setminus \amalg \circ
+ \ddagger \cdot \wr \bullet
+ \lhd \rhd \unlhd \unrhd
+
++ pour les oprateurs de relation :
+ \leq \geq \equiv \models
+ \prec \succ \sim \perp
+ \preceq \succeq \simeq \mid
+ \ll \gg \asymp \parallel
+ \subset \supset \approx \bowtie
+ \subseteq \supseteq \cong \Join
+ \sqsubset \sqsupset \neq \smile
+ \sqsubseteq \sqsupseteq \doteq \frown
+ \in \ni \propto
+ \vdash \dashv
+
++ pour les oprateurs flchs :
+ \leftarrow \longleftarrow \uparrow
+ \Leftarrow \Longleftarrow \Uparrow
+ \rightarrow \longrightarrow \downarrow
+ \Rightarrow \Longrightarrow \Downarrow
+ \leftrightarrow \longleftrightarrow \updownarrow
+ \Leftrightarrow \Longleftrightarrow \Updownarrow
+ \mapsto \longmapsto \nearrow
+ \hookleftarrow \hookrightarrow \searrow
+ \leftharpoonup \rightharpoonup \swarrow
+ \leftharpoondown \rightharpoondown \nwarrow
+ \rightleftharpoons \leadsto
+
++ autres oprateurs :
+ \sum \bigcap \bigodot
+ \prod \bigcup \bigotimes
+ \coprod \bigsqcup \bigoplus
+ \int \bigvee \biguplus
+ \oint \bigwedge
+
++ autres symboles :
+ \aleph \prime \forall \infty
+ \hbar \emptyset \exists \Box
+ \imath \nabla \neg \Diamond
+ \jmath \surd \flat \triangle
+ \ell \top \natural \clubsuit
+ \wp \bot \sharp \diamondsuit
+ \Re \| \backslash \heartsuit
+ \Im \angle \partial \spadesuit
+ \mho
+
+* Des symboles mathmatiques supplmentaires (en plus de ceux
+offerts par amsmath) sont disponibles dans les packages
+'stmaryrd' disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/stmaryrd/, et
+'yhmath' galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/yhmath/.
+
+# 12.13 # Comment dfinir une fonction ?
+----------------------------------------
+* Il existe un certain nombre de fonctions dfinies par dfaut.
+Il s'agit des fonctions :
+ \arccos \cos \csc \exp \ker \limsup \min \sinh
+ \arcsin \cosh \deg \gcd \lg \ln \Pr \sup
+ \arctan \cot \det \hom \lim \log \sec \tan
+ \arg \coth \dim \inf \liminf \max \sin \tanh
+
+* On peut utiliser la commande \mathop :
+\newcommand{\fonction}{\mathop{fonction}}
+Si on utilise en plus la commande \nolimits, on peut dterminer
+la gestion des indices et exposants de cette fonction.
+
+Exemple :
+\newcommand{\rad}{\mathop{\mathrm{rad}}}
+\newcommand{\radn}{\mathop{\mathrm{rad}}\nolimits}
+
+\begin{document}
+\[
+\alpha \rad_{t \rightarrow \infty} = 0
+\]
+
+\[
+\alpha \radn_{t \rightarrow \infty} = 0
+\]
+\newcommand{\rad}{\mathop{\mathrm{rad}}}
+\newcommand{\radn}{\mathop{\mathrm{rad}}\nolimits}
+
+\begin{document}
+\[
+\alpha \rad_{t \rightarrow \infty} = 0
+\]
+
+\[
+\alpha \radn_{t \rightarrow \infty} = 0
+\]
+\end{document}
+%%%% fin exemple %%%%
+
+* Sous LaTeX2e, le package 'amsopn' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/ et par ftp sur
+ftp://e-math.ams.org/pub/tex/amslatex/inputs/. Il permet
+de dclarer de nouvelles fonctions qui seront gres comme une
+fonction mathmatique (gestion de la fonte, disposition des
+indices et exposants, etc). Pour cela il faut dclarer une
+commande du type : \DeclareMathOperator{\fonction}{fonction} dans
+le prambule du document. Pour que les indices et exposants de la
+nouvelle fonction puissent tre gres comme ceux de la fonction
+\sum , il faut alors plutot utiliser \DeclareMathOperator*.
+
+* De mme, le package 'amstex' (LaTeX2.09) dfinit les commandes
+\operatorname et \operatornamewithlimits.
+
+Exemple :
+$\operatorname{rad}$
+%%%% fin exemple %%%%
+
+# 12.14 # Comment dfinir une matrice ?
+---------------------------------------
+* Il suffit de construire un tableau sans lignes avec
+l'environnement array.
+
+Exemple :
+\[
+\begin{array}{ccc}
+ x_{11} & \cdots & x_{1p} \\
+ \vdots & \ddots & \vdots \\
+ x_{n1} & \cdots & x_{np}
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+Pour encadrer cette matrice avec des dlimiteurs, cf.
+paragraphe 12.8.
+
+* Le package 'amsmath',disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, permet de dfinir une matrice de manire
+plus rapide qu'avec l'environnement array. Les environnements
+disponibles sont :
++ matrix,
++ pmatrix pour une matrice encadre par des parenthses,
++ bmatrix pour une matrice encadre par des crochets,
++ vmatrix pour une matrice encadre par des lignes verticales,
++ Vmatrix pour une matrice encadre par des doubles lignes
+verticales.
+
+Exemple :
+\[
+\begin{pmatrix}
+ a & b \\
+ c & d
+\end{pmatrix}
+\]
+%%%% fin exemple %%%%
+
+* Le package 'easybmat' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ permet facilement d'crire
+des matrices par bloc.
+
+* Le package 'easymat' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ facilite galement
+l'criture de matrices.
+
+# 12.15 # Comment encadrer des formules ?
+-----------------------------------------
+* Le package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, offre la commande \boxed.
+
+Exemple :
+$$\boxed{a=b}$$
+%%%% fin exemple %%%%
+
+* Il existe galement la commande \fbox.
+
+Remarque : Avec les environnements multi-lignes de AMSTeX (comme
+ multline ou split), il peut tre utile de les
+ encapsuler dans un math ou dans un displaymath.
+
+Exemple :
+\begin{equation}
+ \fbox{$
+ \begin{array}{rcl}
+ x + y + z & = & 0 \\
+ 2x + 2y + 2z & = & 0
+ \end{array}
+ $}
+\end{equation}
+%%%% fin exemple %%%%
+
+* Le package 'fancybox' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/seminar/inputs/ peut galement tre
+utile.
+
+Exemple :
+\linethickness{3pt}
+\Ovalbox{
+\begin{Beqnarray}
+ds^2&\,=\,& \displaystyle{\frac{\epsilon^{\prime 2}}{L^2}
+\frac{12N}{(N+1)(N+2)}}
+\end{Beqnarray}
+}
+%%%% fin exemple %%%%
+
+* Une dernire solution consiste mettre la formule dans un
+tableau d'une seule cellule.
+
+# 12.16 # Comment ajuster la longueur d'une flche par rapport un texte ?
+---------------------------------------------------------------------------
+Le package 'amsmath',disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, permet de gnrer des flches dont la
+longueur dpend de la longueur du texte qui est plac au dessus
+ou en dessous (ou de la chane la plus longue lorsqu'il y a la
+fois un texte au dessus et un autre en dessous).
+
+Exemple :
+$\xrightarrow[\text{au dessus}]{\text{en dessous}}$
+%%%% fin exemple %%%%
+
+# 12.17 # Comment obtenir des indices ou exposants gauche ?
+-------------------------------------------------------------
+* Les commandes \sideset \overset et \underset du
+package 'amsmath' permettent de placer du texte gauche, en
+haut ou en bas.
+
+Exemple, mettre dans le prambule :
+\newcommand{\transposee}[1]{{\vphantom{#1}}^{\mathit t}{#1}}
+
+puis, dans le corps du document :
+ \[
+\transposee{
+\begin{pmatrix}
+ a & b \\
+ c & d \\
+\end{pmatrix}
+}
+\]
+%%%% fin exemple %%%%
+
+Remarque : on peut galement utiliser \sideset qui ne marche
+ que pour les oprateurs :
+ \newcommand{\transposee}[1]{\sideset{^{\mathit{t}}}{}
+ {#1}}
+
+* A dfaut, on peut utiliser ${}_{j}H$ ou ${_jH}$
+
+* Le package 'chemsym' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/chemsym/ peut galement tre utile.
+
+# 12.18 # Comment tracer des diagrammes commutatifs ?
+-----------------------------------------------------
+* Xy-pic est un outil simple et puissant qui permet de raliser
+de tels diagrammes (cf. paragraphe 8.6).
+
+Exemple :
+\documentclass[a4paper,12pt]{article}
+\usepackage[all]{xy}
+\begin{document}
+ \[\xymatrix{
+ A \ar[d] \ar[r] \ar@{=}[rd] & B \ar[d] \\
+ C \ar[r] & D }
+\]
+\end{document}
+%%%% fin exemple %%%%
+
+* On peut galement utiliser le package 'amscd' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/amslatex/math/ ou plus
+gnralement le package 'amsmath' et l'environnement CD mais
+son offre est plus limite.
+
+Exemple 1 (amscd) :
+\[
+\begin{CD}
+ \mathcal{F} @>\otimes>> T\\
+ @VdrVlfV @ViVjV\\
+ \mathtt{f} @= t
+\end{CD}
+\]
+
+\[
+\begin{CD}
+d @>>> e @>>> f \\
+@AAA @. @AAA \\
+a @>>> b @>>> c
+\end{CD}
+\]
+%%%% fin exemple %%%%
+
+Exemple 2 (amsmath) :
+\[
+\begin{array}{ccccc}
+d & \longrightarrow & e & \longrightarrow &f \\
+\uparrow &&&& \uparrow \\
+a & \longrightarrow & b &\longrightarrow& c\\
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+Remarque : dans la dernire version de amscd, la syntaxe
+ @>Exp1>Exp2> utilise pour les flches extensibles a
+ t abandonne au profit des commandes \xleftarrow et
+ \xrightarrow.
+
+ Pour plus de dtails consultez :
+ + "\amslatex/ Version 1.2\\User's Guide", dans le
+ fichier "amsldoc.tex"
+ + "Differences between \amslatex/ version 1.1 and
+ \amslatex/ version 1.2", dans le fichier "diff12.tex".
+
+* Il existe le package 'cd' crit pour LaTeX2.09 par D.
+Hankerson. Ce package tend les capacits des fonction
+AMS-TeX. Les longueurs de texte s'ajustent avec la longueur des
+arguments.
+
+Exemple (doc package) :
+\documentstyle[12pt,cd]{article}
+\newcommand{\cdrl}{\cd\rightleftarrows}
+\newcommand{\cdlr}{\cd\leftrightarrows}
+\newcommand{\cdr}{\cd\rightarrow}
+\newcommand{\cdl}{\cd\leftarrow}
+\newcommand{\cdu}{\cd\uparrow}
+\newcommand{\cdd}{\cd\downarrow}
+\newcommand{\cdud}{\cd\updownarrows}
+\newcommand{\cddu}{\cd\downuparrows}
+\begin{document}
+\[\CD
+G \cdrl {\gamma}{\delta} H \cdr {}{\Delta} K \\
+\cd. \cdud {f}{g} \cd| {h}{k} \\
+0 \cdr {}{} G' \cd= {\beta}{} H' \endCD
+\]
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'catmac' dfinit un ensemble de macros pour tracer
+des diagrammes commutatifs. Il propose par dfaut un ensemble
+de formes mais permet galement via un certain nombre de
+macros prdfinies de composer ses propres formes.
+
+Exemple :
+\begin{center}
+ \resetparms
+ \square[A`B`C`D;f`g`h`k]
+\end{center}
+%%%% fin exemple %%%%
+
+ATTENTION : ce package n'est pas compatible avec le package
+ french qui rend le ; actif.
+
+# 12.19 # Comment ajuster la taille de certains oprateurs ?
+------------------------------------------------------------
+* Pour ajuster la taille de certains oprateurs, il faut
+utiliser le package 'exscale' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/base/.
+
+* Le package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/, donne la mme possibilit.
+
+# 12.20 # Comment mettre en page des algorithmes ?
+--------------------------------------------------
+* Les packages 'algorithms' et 'algorithmic' disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/algorithms/, ont t
+spcifiquement conus pour mettre en forme des algorithmes.
+
+* Il existe aussi le package 'alg' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/alg/.
+
+* Le package 'newalg' est galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/newalg/. Il propose un
+environnement algorithm qui par dfaut utilise le mode
+mathmatique et l'environnement array pour les alignements. La
+commande \text est galement disponible. Le package gre les
+instructions : if-then-else, for, while, repeat, switch et
+propose un certain nombre de macros telles que call, error,
+algkey, return, nil.
+
+Exemple :
+\begin{algorithm}{StrictSup}{x, y}
+ \begin{IF}{x > y}
+ \RETURN x
+ \ELSE
+ \ERROR{x leq y}
+ \end{IF}
+\end{algorithm}
+%%%% fin exemple %%%%
+
+# 12.21 # Comment mettre en page des formules longues ?
+-------------------------------------------------------
+L. Lamport dfinit certaines conventions dans sa page WEB :
+http://www.research.digital.com/SRC/personal/Leslie_Lamport/latex/latex.html.
+
+# 12.22 # Comment crer des units de mesure ?
+----------------------------------------------
+Le problme du mode mathmatique est qu'il change
+automatiquement de fonte et qu'il utilise une gestion
+particulire des espaces. Le mieux pour crire des units de
+mesures du type m/s sans avoir taper systmatiquement des
+barbarismes du type \rm\,m/s\mit ou \,\textrm{m}/\textrm{s} est
+de dfinir une commande spciale dans le prambule du document.
+
+Exemples :
+\newcommand{\units}[2]{#1\textrm{\thinspace #2}}
+cette commande ncessite le package 'amsmath'
+utilisation : \units{10}{m/s}
+
+ou plus rapide :
+\newcommand{\ms}[1]{\units{#1}{m/s}}
+utilisation : \ms{10}
+%%%% fin exemple %%%%
+
+# 12.23 # Comment crire proprement a/b ?
+-----------------------------------------
+Pour qu' l'impression le numrateur 'a' soit lgrement dcal
+vers le haut et vers la gauche et que le dnominateur 'b' soit
+lgrement dcal vers le bas et vers la droite, les deux tant
+plus petits que la fonte courante, il existe la commande \sfrac
+du package tugboat disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/tugboat/.
+
+# 12.24 # Comment crer des notes de bas de page dans une formule mathmatique ?
+--------------------------------------------------------------------------------
+* On peut utiliser directement la commande \footnote{} ou les
+commandes spcifiques \footnotemark[] et \footnotetext[]{}
+si l'on veut fixer soit mme les compteurs. \footnotemark permet
+de grer le compteur de notes et \footnotetext permet d'insrer
+le texte correspondant en bas de page.
+
+Exemple :
+\[
+Place_{libre}\footnotemark[1] +
+Place_{occup\acute ee}\footnotemark[2] +
+Place_{d\acute efaillante} =
+Capacit\acute e
+\]
+\footnotetext[1]{La place libre~\ldots}
+\footnotetext[2]{La place occup\' ee~\ldots}
+%%%% fin exemple %%%%
+
+# 12.25 # Comment forcer le style d'un tableau displaystyle ?
+---------------------------------------------------------------
+Le style par dfaut dans un "array" est textstyle. Pour viter
+d'avoir crire \displaystyle dans chaque cellule, on peut
+dclarer un tableau entirement en mode displaystyle via la
+macro:
+%%%% debut macro %%%%
+\newenvironment{disarray}%
+ {\everymath{\displaystyle\everymath{}}\array}%
+ {\endarray}
+%%%% fin macro %%%%
+
+# 12.26 # Comment rduire les espaces grs par eqnarray ?
+----------------------------------------------------------
+Il suffit d'inclure la macro suivante dans le prambule de votre
+document :
+
+%%%% debut macro %%%%
+\makeatletter
+\newlength{\earraycolsep}
+\setlength{\earraycolsep}{2pt}
+\def\eqnarray{\stepcounter{equation}\let\@currentlabel%
+\theequation
+\global\@eqnswtrue\m@th
+\global\@eqcnt\z@\tabskip\@centering\let\\\@eqncr
+$$\halign to\displaywidth\bgroup\@eqnsel\hskip\@centering
+$\displaystyle\tabskip\z@{##}$&\global\@eqcnt\@ne
+\hskip 2\earraycolsep \hfil$\displaystyle{##}$\hfil
+&\global\@eqcnt\tw@ \hskip 2\earraycolsep
+$\displaystyle\tabskip\z@{##}$\hfil
+\tabskip\@centering&\llap{##}\tabskip\z@\cr}
+\makeatother
+%%%% fin macro %%%%
+
+# 12.27 # Comment rduire la taille des indices ?
+-------------------------------------------------
+* Il faut utiliser la commande \DeclareMathSizes :
+\DeclareMathSizes{10}{10}{6}{5}
+\DeclareMathSizes{11}{11}{7}{5}
+\DeclareMathSizes{12}{12}{7}{5}
+Ces dclarations permettent de rduire la taille des indices des
+fontes 10pt, 11pt et 12pt.
+
+Exemple :
+\documentclass[12pt]{report}
+\usepackage{french}
+\pagestyle{empty}
+\DeclareMathSizes{12}{12}{7}{5}
+\begin{document}
+La capacit totale est dfinie par~:
+\[
+C_{libre} + C_{occup\acute ee} = C_{totale}
+\]
+\end{document}
+%%%% fin exemple %%%%
+
+* On peut aussi utiliser les commandes scriptstyle ou
+scriptscriptstyle.
+
+Exemple :
+$\rho_{AB}$
+$\rho_{\scriptstyle AB}$
+$\rho_{\scriptscriptstyle AB}$
+%%%% fin exemple %%%%
+
+* En utilisant les caractres romans, on peut appliquer la
+commande \small.
+
+Exemple :
+$\rho_{\textrm{\small AB}}$
+%%%% fin exemple %%%%
+
+# 12.28 # Comment aligner des indices ?
+---------------------------------------
+La commande \vphantom dfinit une bote invisible dont la
+hauteur est celle de son argument.
+
+Exemple :
+\[
+f_{\vphantom{\widehat{ef}} d} = f_{\widehat{ef}} \mathrm{\ au \
+lieu \ de~:} f_d = f_{\widehat{ef}}
+\]
+%%%% fin exemple %%%%
+
+# 12.29 # Comment mettre en page des thormes ?
+------------------------------------------------
+* LaTeX offre la commande
+\newtheorem{nom}[compteur]{texte}[section]
+o nom est une cl pour identifier le thorme, et
+texte le titre du thorme qui sera imprim. compteur permet de
+rfrencer un autre thorme pour obtenir la mme numrotation.
+section permet de prciser le niveau de numrotation voulu.
+
+Exemple :
+dans le prambule :
+\newtheorem{th-imp}{Thorme important}[section]
+\newtheorem{th-u}{Thorme}[subsection]
+
+dans le texte :
+
+\section{Introduction.}
+
+ \begin{th-imp} \label{label-th-AA}
+ BLA BLA
+ \end{th-imp}
+
+ \subsection{Bases.}
+
+ \begin{th-u} \label{label-th-aaa}
+ bla bla bla
+ \end{th-u}
+
+ \begin{th-u}
+ bla ble
+ \end{th-u}
+
+\section{Conclusion}
+
+ Le thorme important~\ref{label-th-AA} est apprendre par
+ c\oe{}ur, le thorme~\ref{label-th-aaa} peut tre utile.
+%%%% fin exemple %%%%
+
+* Il existe pour cela le package 'thmmarks' disponible
+http://www.informatik.uni-freiburg.de/~may/thmmarks.html.
+
+* Le package 'newthm' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/newthm/ permet de gnrer une liste
+des thormes apparaissant dans un document.
+
+* Les trois packages suivants permettent de dfinir son propre style.
+
+ ** Le package 'amsmath', disponible sur ftp://ftp.fdn.org/pub/CTAN//fonts/ams/amslatex/,
+ dfinit l'environnement proof en insrant un carr.
+ Des exemples de thormes se trouvent dans le fichier thmtest.tex
+
+ ** Le package 'theorem', disponible sur CTAN. Voir le fichier
+ theorem.dvi
+
+ ** Il existe galement le package 'ntheorem' disponible sur CTAN
+ ou sur
+ http://www.informatik.uni-freiburg.de/~may/Ntheorem/ntheorem.html
+ Il peut gnrer une liste des thoremes de la mme manire que
+ 'listoffigures', est compatible avec amsmath, permet d'ajouter des
+ symboles la fin d'un thoreme 'carr, q.e.d.), permet la rfrence
+ d'autres thoremes. Voir le fichier ntheorem.dvi
+
+** Voici un tableau rcapitulatif :
+
+ +------------------------------------+--------+---------+----------+
+ |Package | amsthm | theorem | ntheorem |
+ +------------------------------------+--------+---------+----------+
+ |Retour la ligne aprs le titre | x | x | x |
+ +------------------------------------+--------+---------+----------+
+ |Pas de numrotation d'un thoreme | x | | x |
+ +------------------------------------+--------+---------+----------+
+ |Position du numro du thoreme | | x | x |
+ +------------------------------------+--------+---------+----------+
+ |Style de la numrotation | | | x |
+ +------------------------------------+--------+---------+----------+
+ |Ponctuation aprs le titre (:,.,etc)| x | | x |
+ +------------------------------------+--------+---------+----------+
+ |Fonte du titre ou du corps | x | x | x |
+ +------------------------------------+--------+---------+----------+
+ |Indentation du titre | x | | |
+ +------------------------------------+--------+---------+----------+
+ |Espace vertical autour du thorme | x | x | x |
+ +------------------------------------+--------+---------+----------+
+
+# 12.30 # Comment changer la taille de la fonte ?
+-------------------------------------------------
+Voici une solution prsente par T. Bouche et S.A. Zaimi :
+
+Exemple :
+\documentclass{report}
+\def\mathtitre#1{
+\font\tenrm=cmr10 scaled \magstep#1
+\font\sevenrm=cmr7 scaled \magstep#1
+\font\fiverm=cmr5 scaled \magstep#1
+\font\teni=cmmi10 scaled \magstep#1
+\font\seveni=cmmi7 scaled \magstep#1
+\font\fivei=cmmi5 scaled \magstep#1
+\font\tensy=cmsy10 scaled \magstep#1
+\font\sevensy=cmsy7 scaled \magstep#1
+\font\fivesy=cmsy5 scaled \magstep#1
+\font\tenex=cmex10 scaled \magstep#1
+\textfont0=\tenrm \scriptfont0=\sevenrm \scriptscriptfont0=\fiverm
+\textfont1=\teni \scriptfont1=\seveni \scriptscriptfont1=\fivei
+\textfont2=\tensy \scriptfont2=\sevensy \scriptscriptfont2=\fivesy
+\textfont3=\tenex \scriptfont3=\tenex \scriptscriptfont3=\tenex
+}
+
+\begin{document}
+ {\mathtitre0 $$A+B=C^{B^A}$$}
+ {\mathtitre1 $$A+B=C^{B^A}$$}
+ {\mathtitre2 $$A+B=C^{B^A}$$}
+ {\mathtitre3 $$A+B=C^{B^A}$$}
+ {\mathtitre4 $$A+B=C^{B^A}$$}
+ {\mathtitre5 $$A+B=C^{B^A}$$}
+\end{document}
+%%%% fin exemple %%%%
+
+ATTENTION : il ne faut pas que le bloc en police \mathtitreXX
+ se trouve cheval sur deux pages... cela mettrait
+ le numro de page (et les en-ttes-pieds de page)
+ dans ladite police...
+
+# 12.31 # A quoi sert la commande \displaystyle ?
+-------------------------------------------------
+Elle permet de forcer LaTeX grer les indices et les exposants
+comme si il tait en mode mathmatique isol. Cela peut alors
+induire une modification locale de l'interligne courant.
+
+Exemple :
+Elle permet de forcer \LaTeX grer les indices et les
+exposants comme si il tait en mode mathmatique isol
+$\displaystyle{\sum_{i=0}^n x_i}$. Cela peut alors induire une
+modification locale de l'interligne courant. Ce texte contient
+un exemple probant. Le changement d'interligne est bien visible.
+%%%% fin exemple %%%%
+
+# 12.32 # Comment aligner des donnes sur le point dcimal ?
+------------------------------------------------------------
+* Le package 'dcolumn' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/ permet d'aligner les nombres d'un
+tableau par rapport leur point dcimal.
+
+* On peut galement utiliser un tableau avec une virgule comme
+sparateur de colonnes.
+
+Exemple :
+\[
+\begin{array}{r @{,} l}
+ 1&2 \\
+ 233&456 \\
+ x&y \\
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+# 12.33 # Comment grer les espaces en mode mathmatique ?
+----------------------------------------------------------
+Voici les diffrents espaces prdfinis :
+\! rduit l'espace par dfaut,
+\, donne un petit espace,
+\ suivit d'un espace, donne un espace de taille moyenne,
+\quad donne un espace moyen,
+\qquad donne un grand espace.
+
+Exemple :
+\[
+\begin{array}{l}
+ sin cos \\
+ sin \! cos \\
+ sin \, cos \\
+ sin \ cos \\
+ sin \quad cos \\
+ sin \qquad cos \\
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+# 12.34 # Comment obtenir des accolades horizontales ?
+------------------------------------------------------
+\overbrace et \underbrace.
+
+Exemple :
+\[
+\overbrace{f(x)}^{=0} + \underbrace{g(y)}_{=0} = 0
+\]
+%%%% fin exemple %%%%
+
+# 12.35 # Comment obtenir des points de suspensions ?
+-----------------------------------------------------
+En mode math, il existe diffrents types de points de suspension
+suivant leur orientation :
++ \ldots pour des points horizontaux sur la ligne d'criture
++ \cdots pour des points horizontaux au dessus de la ligne
+d'criture
++ \vdots pour des points verticaux
++ \ddots pour des points en diagonale
+
+Exemple :
+\[
+\begin{array}{ccc}
+ x_{11} & \cdots & x_{1p} \\
+ \vdots & \ddots & \vdots \\
+ x_{n1} & \cdots & x_{np}
+\end{array}
+\]
+%%%% fin exemple %%%%
+
+# 12.36 # Comment mettre en page un systme d'quations ?
+---------------------------------------------------------
+* On peut utiliser les commandes \left dlimiteur et \right.
+ classiques devant un tableau.
+
+Exemple :
+\[
+\left \{
+\begin{array}{c @{=} c}
+ x & \sin a \cos b \\
+ y & \sin a \sin b \\
+\end{array}
+\right.
+\]
+%%%% fin exemple %%%%
+
+* On peut utiliser le package 'mathenv', permettant de numroter le
+ systme ou chaque quation du systme, le compteur pouvant alors tre
+ personnalis.
+
+Exemples :
+
+% numrotation du systme
+\begin{System}
+ 2x + y = 6 \\
+ 3x + y = 7
+\end{System}
+
+%numrotation de chaque quation du systme
+\begin{EqSystem}
+ 2x + y = 6 \\
+ 3x + y = 7
+\end{EqSystem}
+%%%% fin exemple %%%%
+
+* On peut utiliser le package 'amsmath', permettant de placer des
+ alternatives conditionnelles.
+
+Exemple :
+\begin{equation*}
+ |x|=
+ \begin{cases}
+ -x & \text{si $x$ est impair} \\
+ x & \text{si $x$ est pair ou nul}
+ \end{cases}
+\end{equation*}
+%%%% fin exemple %%%%
+
+* Le package 'cases' disponible sur
+ ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ gre les systmes d'quations.
+
+Exemple :
+\begin{numcases}{|x|=}
+ x, & for $x \geq 0$\\
+ -x, & for $x < 0$
+\end{numcases}
+%%%% fin exemple %%%%
+
+* Voici une adaptation de ce package par J. Laurens :
+%%%% debut macro %%%%
+% fichier xtdeqnra.sty ver 1.0 Decembre 1997
+%
+% Copyright (C) 1997 by Jerome LAURENS
+%
+% Ces macros peuvent e^tre librement transmises, sans modification aucune
+% tant que cette notice est intacte.
+% Base' sur le paquetage cases.sty de D.Arseneau
+% et la commande \eqnarray de Leslie Lamport et de l'e'quipe LaTeX3.
+%
+% On rajoute un parame`tre optionnel a` l'environnement eqnarray qui
+% est un delimiteur gauche
+%
+% Exemple : source
+%
+% \begin{eqnarray}[\{]
+% x_1 & = & valeur_1 \\
+% x_2 & = & valeur_2 \\
+% x_3 & = & valeur_3
+% \end{eqnarray}
+%
+% Re'sultat
+%
+% / x_1 = valeur_1 (1)
+% |
+% < x_2 = valeur_2 (2)
+% |
+% \ x_3 = valeur_3 (3)
+%
+% Pour utiliser ce paquetage,
+% inclure "\usepackage{xtdeqnra}" apre`s \documentclass.
+%
+% On peut utiliser l'environnement subequations pour avoir (1a), (1b) et (1c)
+% - - - - -
+%
+
+\ProvidesPackage{xtdeqnra}[1997/12/05 version 1.0 ]
+
+% - sauvegarde de l'environnement eqnarray
+\let\x@eqnarray\eqnarray
+\let\endx@eqnarray\endeqnarray
+%
+% - environnement de remplacement
+\def\eqnarray{\@ifnextchar[%
+ {\let\endeqnarray\endy@eqnarray\y@eqnarray}
+ {\let\endeqnarray\endx@eqnarray\x@eqnarray}}
+%
+% - nouvel environnement avec un de'limiteur a` gauche
+\def\y@eqnarray[#1]%
+{ \gdef\@leftdelimiter{#1}
+ \displaymath
+ \setbox\tw@\vbox
+ \bgroup
+ \stepcounter{equation}%
+ \def\@currentlabel{\p@equation\theequation}%
+ \global\@eqnswtrue
+ \m@th
+ \everycr{}%
+ \tabskip\@centering
+ \let\\\@eqncr
+ \halign to\displaywidth
+ \bgroup
+ \hskip \@ne\arraycolsep
+ \hfil$\displaystyle
+ \tabskip\z@skip{##}$%
+ \@eqnsel
+ &\global\@eqcnt\@ne
+ \hskip \tw@\arraycolsep
+ \hfil${##}$\hfil
+ &\global\@eqcnt\tw@
+ \hskip\tw@\arraycolsep
+ $\displaystyle{##}$\hfil
+ \unskip\hfil
+ \tabskip\@centering% \unskip removes space if no explanations
+ &\global\@eqcnt\thr@@
+ \hb@xt@\z@\bgroup\hss##\egroup
+ \tabskip\z@skip
+ \cr
+}
+\def\endy@eqnarray{%
+ \@@eqncr
+ \egroup % end \halign, which does not contain brace
+ \global\advance\c@equation\m@ne
+ \unskip\unpenalty
+ \unskip\unpenalty
+ \setbox\z@\lastbox % grab last line
+ \nointerlineskip
+ \copy\z@ % then put it back
+ \setbox\z@\hbox{\unhbox\z@}%
+ \global\dimen@i\wd\z@
+ \egroup% end \vbox (box\tw@, box\z@ is restored to LHS)
+ \hbox to\displaywidth{%
+ \m@th % assemble the whole equation
+ \hskip\@centering
+ \hbox to\dimen@i{%
+ $\displaystyle%
+ \dimen@\ht\tw@
+ \advance\dimen@\dp\tw@ % get size of brace
+ \setbox\z@\hbox{$\mathord{\left\@leftdelimiter\vcenter
+to\dimen@{\vfil}\right.}$}%
+ \dimen@\wd\z@
+ \kern-\dimen@
+ \box\z@%
+ \n@space % make brace
+ $\hfil}
+ \hskip\@centering % finished first part (filled whole line)
+ \kern-\displaywidth$%
+ \vcenter{\box\tw@}$% overlay the alignment
+ }% end the \hbox
+ \enddisplaymath
+ \global\@ignoretrue
+}
+
+\endinput
+
+% fin du fichier xtdeqnra.sty
+%%%% fin macro %%%%
+
+* Le package 'delarray' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/ peut galement tre utilis dans
+ce but.
+
+# 12.37 # Comment mettre en page des diagrammes de Feynman ?
+------------------------------------------------------------
+Le package 'feynmf' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/feynmf/ permet de grer la mise
+en page de diagrammes de Feynman.
+
+# 12.38 # Comment obtenir une fraction ?
+----------------------------------------
+LaTeX propose la commande \frac{arg1}{arg2} dont l'argument arg1
+est le numrateur et arg2 dnominateur.
+
+Exemple :
+en formule~:
+$$\frac{\alpha}{6 + \sqrt{2}}$$
+ou dans le texte $\frac{\alpha}{6 + \sqrt{2}}$.
+%%%% fin exemple %%%%
+
+# 12.39 # Comment obtenir une racine ?
+--------------------------------------
+Il existe la commande \sqrt[n]{arg}, qui reprsente la racine
+nime de arg. [n] est un paramtre optionnel.
+
+Exemple :
+$$ \sqrt[3]{\sqrt{\sqrt[\gamma]{x+y}}} $$
+%%%% fin exemple %%%%
+
+# 12.40 # Quels sont les dlimiteurs disponibles ?
+--------------------------------------------------
+( ) [ ] \{ \}
+\uparrow \downarrow \updownarrow
+\Uparrow \Downarrow \Updownarrow
+\lfloor \rfloor \lceil \rceil
+\langle \rangle
+/ \backslash | \|
+
+# 12.41 # Comment appeler les lettres grecques ?
+------------------------------------------------
+Il suffit de faire prcder leur nom en toutes lettres d'un
+backslash :
++ minuscules :
+\alpha \beta \gamma \delta \epsilon \varepsilon \zeta \eta
+\theta \vartheta \iota \kappa \lambda \mu \nu \xi \pi \varpi
+\rho \varrho \sigma \varsigma \tau \upsilon \phi \varphi \chi
+\psi \omega
+
++ majuscules :
+\Gamma \Delta \Theta \Lambda \Xi \Pi \Sigma \Upsilon \Phi \Psi
+\Omega
+
+# 12.42 # Quels sont les accents mathmatique standards ?
+---------------------------------------------------------
+* Il en existe dix pour des lettres seules :
++ $\hat{a}$
++ $\check{a}$
++ $\breve{a}$
++ $\acute{a}$
++ $\grave{a}$
++ $\tilde{a}$
++ $\bar{a}$
++ $\vec{a}$
++ $\dot{a}$
++ $\ddot{a}$
+
+Remarque : pour placer un accent sur un i ou un j, il faut
+ utiliser les commandes \imath et \jmath qui
+ permettent de supprimer le point par dfaut.
+
+* Il en existe galement d'autres pour couvrir des ensembles de
+lettres :
++ $\widehat{abc}$
++ $\widetilde{def}$
++ $\overrightarrow{ghi}$
++ $\overline{jkl}$
++ $\underline{mno}$
++ $\overbrace{pqr}$
++ $\underbrace{stu}$
+
+# 12.43 # Comment superposer deux symboles ?
+--------------------------------------------
+Il existe pour cela la commande \stackrel{dessus}{dessous}
+
+Exemple :
+\[
+A \stackrel{\theta}{\Rightarrow} B
+\]
+%%%% fin exemple %%%%
+
+# 12.44 # Comment dfinir un nouvel oprateur ou symbole ?
+----------------------------------------------------------
+* Il existe pour cela la commande \DeclareMathOperator du
+package 'amsmath', disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/.
+Elle s'utilise dans le prambule.
+
+Exemple :
+\DeclareMathOperator{\init}{init}
+
+\[
+\init f = 0 \mathrm{\ au \ lieu \ de~:} init f = 0
+\]
+%%%% fin exemple %%%%
+
+* On peut galement utiliser \newcommand, toujours dans le
+prambule du document.
+
+Exemple :
+\newcommand{\affecte}{\mathrel{:=}}
+
+$x \affecte 0$
+
+$y \affecte 1$
+%%%% fin exemple %%%%
+
+* On peut utiliser \def.
+
+Exemple :
+\makeatletter
+\def\log{\mathop{\operator@font log}\nolimits}
+\makeatother
+
+$\log 28 = 1.447158$
+%%%% fin exemple %%%%
+
+* Pour dfinir un nouveau symbole de plusieurs caractres, il
+faut utiliser \mathit.
+
+# 12.45 # Comment obtenir des lettres grecques en gras ?
+--------------------------------------------------------
+* On peut utiliser le package 'amsmath', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/ams/amslatex/ :
+
+Exemple :
+...
+\usepackage{amsmath}
+...
+\begin{document}
+...
+$\boldsymbol{\alpha}$
+%%%% fin exemple %%%%
+
+* On peut galement utiliser le package 'bm' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/bm/.
+
+Exemple :
+...
+\usepackage{bm}
+...
+\begin{document}
+...
+$\bm{\alpha}$
+%%%% fin exemple %%%%
+
+# 12.46 # Comment tracer un tableau de variations ?
+---------------------------------------------------
+
+* Avec l'environnement array en mode mathmatiques (cf. question
+12.11).
+
+Exemple:
+$
+\begin{array}{|c|ccccr|}
+\hline
+x & -\infty & & 0 & & +\infty \\
+\hline
+f'(x) & 5 & + & 0 & - & -10 \\
+\hline
+ & & & 10 & & \\ % ligne des valeurs "max"
+f(x) & &\nearrow & &\searrow & \\ % flches
+& -\infty & & & & -10 \\ % ligne des valeurs "min"
+\hline
+\end{array}
+$
+%%%% fin exemple %%%%
+
+* On peut faire de plus jolies flches (redimensonnables) avec les commandes
+graphiques.
+
+Pour cela, il faut choisir une unit de longueur avant par:
+ \unitlength=1cm
+et remplacer par exemple \nearrow par (flches de 2cm de large et de haut)
+
+Exemple:
+\begin{minipage}{2cm}
+ \begin{picture}(2,2)
+ \put(0,0){\vector(1,1){2}}
+ \end{picture}
+\end{minipage}
+%%%% fin exemple %%%%
+
+================================================================
+[13] RFRENCES CROISES
+================================================================
+
+# 13.1 # Quelles sont les commandes de base ?
+---------------------------------------------
+* LaTeX permet de grer automatiquement des rfrences croises
+grce aux commandes suivantes :
+\label{} pour reprer la rfrence rappeler
+\ref{} pour faire appel la rfrence dcrite par la commande
+\label
+\pageref{} pour faire rfrence la page de la rfrence
+repere par la commande \label
+\cite{} pour faire rfrence un document cit en
+bibliographie.
+
+L'utilisation de ces commandes ncessite alors plusieurs (deux
+ trois) compilations successives, jusqu' ce que toutes les
+rfrences croises soient correctes.
+
+ATTENTION : pour les figures et les tables, la commande \label
+ doit se situer juste aprs un \caption ou en faire
+ partie pour que les rfrences soient correctes.
+
+ATTENTION : lorsque l'on travaille avec une version infrieure
+ 3.6 du package babel et l'option french, sachant que
+ cette dernire redfinit certains caractres de
+ ponctuation tels que :;?! pour grer automatiquement
+ les espaces, il ne faut pas les utiliser dans des
+ noms de label : \label{section:Introduction} est
+ interdit.
+
+Exemple :
+Remplir la table~\ref{table-add}, page~\pageref{table-add}
+\begin{table}[htbp]
+ \begin{center}
+ \begin{tabular}{c|c}
+ \hline
+ Question & Rponse \\
+ \hline
+ 1 + 12 & \\
+ 45 + 76 & \\
+ \end{tabular}
+ \caption{Additions. \label{table-add}}
+ \end{center}
+\end{table}
+%%%% fin exemple %%%%
+
+* Le package 'prettyref' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/prettyref/ permet de dfinir ses
+propres styles de rfrence.
+
+# 13.2 # Comment obtenir un renvoi une page ?
+-----------------------------------------------
+* Il suffit d'utiliser la commande \pageref prsente ci-dessus.
+
+* Le package 'varioref', de F. Mittelbach, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/, permet de n'appeler une
+rfrence de page que si l'objet flottant auquel elle se
+rattache n'est pas prsent sur la page courante. Pour cela, ce
+package dfinit la commande \vpageref qui ne fera apparatre le
+numro de la page rfrence que si ce n'est pas la page
+courante. Cette commande peut galement introduire des
+expressions du type "sur la page prcdente", "sur cette mme
+page", etc. Dans ce cas, on prcise la langue voulue en option
+lors de l'appel du package.
+
+Exemple:
+\documentclass{report}
+\usepackage{french}
+\usepackage[french]{varioref}
+
+\begin{document}
+Remplir la table~\ref{table-add}~\vpageref{table-add}
+\begin{table}[htbp]
+ \begin{center}
+ \begin{tabular}{c|c}
+ \hline
+ Question & Rponse \\
+ \hline
+ 1 + 12 & \\
+ 45 + 76 & \\
+ \end{tabular}
+ \caption{Additions. \label{table-add}}
+ \end{center}
+\end{table}
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : Ce package est incompatible avec les styles de page
+ sans numrotation (e.g. empty).
+
+# 13.3 # Comment obtenir des rfrences croises partir de plusieurs sources ?
+--------------------------------------------------------------------------------
+Le package 'xr', de D. Carlisle, permet de faire des rfrences
+d'un document l'autre. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/. Le document contenant les labels
+est appel dans le document contenant les rfrences via la
+commande \externaldocument. La commande
+\externaldocument[KEY]{DOCUMENT} permet mme de grer les
+rfrences de mme nom.
+
+Exemple :
+* fichier essai.tex :
+ \documentclass[a4paper,12pt]{book}
+
+ \begin{document}
+ \section{Ma section.\label{ma-sect}}
+ \end{document}
+
+* fichier essai-ass.tex :
+ \documentclass[11pt]{report}
+ \usepackage{xr}
+ \externaldocument{essai}
+
+ \begin{document}
+ Pour plus de dtails, voir le document \textit{essai},
+ paragraphe~\ref{ma-sect}
+ \end{document}
+%%%% fin exemple %%%%
+
+# 13.4 # Comment dfinir des liens hypertexte sous LaTeX ?
+----------------------------------------------------------
+* Le package 'hyperref' de S. Rahtz disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/hyperref/ permet de dfinir des
+liens hypertexte pour PDF. Il dfinit pour cela des commandes de
+type \ref{}.
+
+* Voir galement les packages 'hyper' et 'hyperlatex'
+disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/hyper/.
+
+* La distribution Y&Y TeX System supporte des liens en TeX
+debuggable dans le previewer qui seront automatiquement
+convertis en liens PDF pour Adobe.
+
+# 13.5 # Comment faire rfrence ses propres compteurs ?
+----------------------------------------------------------
+Lorsque l'on dfinit son propre environnement avec ses popres
+compteurs, pour que les commandes \label et \ref puissent les
+prendre en compte, il suffit d'utiliser \refstepcounter au
+lieu de \stepcounter pour incrmenter le compteur auquel on
+fait rfrence.
+
+================================================================
+[14] TABLE DES MATIRES
+================================================================
+
+# 14.1 # Comment gnrer une table des matires ?
+-------------------------------------------------
+* LaTeX propose la commande \tableofcontents appeler
+l'endroit o l'on veut insrer la table des matires.
+
+# 14.2 # Comment gnrer plusieurs tables des matires ?
+--------------------------------------------------------
+* Le package 'french' propose la commande sommaire[n] qui permet
+d'inclure une table des matire de niveau de profondeur n.
+
+Remarque : dans ce cas \tableofcontents reste utilisable.
+
+* Le package 'shorttoc' ci-dessous, de J.P. Drucbert, dfinit la
+commande \shorttableofcontents{TITRE}{NIVEAU}.
+
+Remarque : dans ce cas \tableofcontents reste galement
+ utilisable.
+
+%%%% debut macro %%%%
+%shorttoc.sty
+\ProvidesPackage{shorttoc}%
+[1995/01/04 v1.0 Short table of contents package (JPFD)]
+\def\@startshorttoc#1{\bgroup
+ \makeatletter
+ \@input{\jobname.#1}%
+ \global\@nobreakfalse \egroup}
+
+\def\shorttableofcontents#1#2{\bgroup\c@tocdepth=#2\@restonecolfalse
+ \if@twocolumn\@restonecoltrue\onecolumn\fi
+ \@ifundefined{chapter}%
+ {\section*{{#1}
+ \@mkboth{\uppercase{#1}}{\uppercase{#1}}}}%
+ {\chapter*{{#1}
+ \@mkboth{\uppercase{#1}}{\uppercase{#1}}}}%
+ \@startshorttoc{toc}\if@restonecol\twocolumn\fi\egroup}
+%%%% fin macro %%%%
+
+* Le package 'minitoc', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/minitoc/, permet de construire
+une minitable des matires au dbut de chaque chapitre sous les
+classes 'book' et 'report'. Pour l'utiliser, il faut appeler les
+commandes \dominitoc avant la commande \tableofcontents
+habituelle. La commande \faketableofcontents permet de ne garder
+que les tables des matires locales et remplace alors la
+commande \tableofcontents. La commande \minitoc doit tre
+appele aprs chaque commande de dbut de chapitre \chapter dans
+lequel on veut inclure une table locale. A chaque appel de
+minitoc correspond un fichier .mtc<n> o n est le numro du
+chapitre.
+
+Le compteur minitocdepth permet de fixer la profondeur des
+tables des matires dsires.
+
+Exemple :
+\documentclass{report}
+\usepackage{minitoc}
+\usepackage{french}
+\setcounter{minitocdepth}{1}
+\begin{document}
+
+\dominitoc
+\tableofcontents
+
+\chapter{Introduction.}
+\minitoc
+
+\section{Quelques rappels.}
+ Texte.
+
+ \subsection{La gravit.}
+
+ Texte sur la gravit.
+
+ \subsection{Loi de Newton.}
+
+ Deux corps s'attirent en raison inverse du carr
+ de leur distance et proportionnellement leur
+ masse.
+
+\section{Nouveaux thormes.}
+
+ Encore des rsultats.
+
+\section{Approfondissement.}
+
+ Toujours plus loin.
+
+pour ne faire apparatre que les titres de sections.
+\end{document}
+%%%% fin exemple %%%%
+
+Le bon fonctionnement des numrotations peut ncessiter jusqu'
+trois compilations enchanes.
+
+ATTENTION : minitoc sait faire:
++ les tables des matires (liste des figures/tables) par partie,
++ par chapitre (classe book et report) et,
++ par section (classe article).
+
+Par contre, il ne fait pas les tables des matires par section
+(et en dessous) pour les classes book et report, ni les tables
+des matires par sous-section (et en dessous) pour la classe
+article.
+
+# 14.3 # Comment ajouter une entre dans la table des matires ?
+----------------------------------------------------------------
+Pour ajouter un titre de paragraphe qui n'apparat pas par
+dfaut dans la table des matires, il faut utiliser la commande
+\addcontentsline{1}{2}{3} o :
+1 est l'extension du fichier contenant la table des matires
+gnralement 1 vaut toc,
+2 est un niveau dfini dans la table des matires; ce peut tre
+chapter, section, ... et,
+3 est le texte que l'on veut voir apparatre dans la table.
+
+Exemple :
+\bibliography{sdf}
+\addcontentsline{toc}{chapter}{Bibliographie.}
+%%%% fin exemple %%%%
+
+# 14.4 # Comment changer le titre de la table des matires ?
+------------------------------------------------------------
+On peut utiliser la commande :
+\renewcommand{\contentsname}{Contenu du document.}
+
+Remarque : suivant les packages utiliss, il faut placer cette
+ dfinition avant ou aprs le \begin{document}.
+
+# 14.5 # Comment changer la profondeur de la table des matires ?
+-----------------------------------------------------------------
+Les sections sont numrotes si leur profondeur est infrieure
+secnumdepth.
+
+Elles apparaissent dans la table des matires si leur profondeur
+est infrieure tocdepth.
+
+Il suffit de changer les valeurs de ces deux compteurs. Il peut
+alors tre ncessaire d'enchaner deux compilations LaTeX.
+
+Exemple :
+\documentclass[a4paper]{article}
+\usepackage{french}
+\pagestyle{empty}
+% Profondeur de \subsubsection = 3
+\setcounter{tocdepth}{3} % Dans la table des matieres
+\setcounter{secnumdepth}{3} % Avec un numero.
+
+\begin{document}
+\tableofcontents
+\vspace{.5cm}
+\hrule
+
+\part{Aaa.}
+\section{aaa.}
+ \subsection{bbb.}
+ \subsubsection{ccc.}
+\end{document}
+%%%% fin exemple %%%%
+
+# 14.6 # Comment grer des chapitres de prface, d'introduction, et de conclusion non numrots ?
+-------------------------------------------------------------------------------------------------
+* La classe book dfinit les commandes \frontmatter, \mainmatter
+et \backmatter qui permettent de faire cela.
+
+Exemple :
+\documentclass[a4paper,12pt,openany]{book}
+\usepackage{french}
+
+\def\TEXTE{Bla bla bla...}
+
+\begin{document}
+
+\frontmatter
+
+%\begin{abstract} Bla, bla... \end{abstract}
+
+\chapter{Prface} \TEXTE
+\chapter{Introduction} \TEXTE
+
+\mainmatter
+
+\chapter{Dbut} \TEXTE
+\chapter{Suite} \TEXTE
+\chapter{Fin} \TEXTE
+
+\appendix
+\chapter{Rsultats lmentaires}
+\chapter{Rsultats compliqus}
+
+\backmatter
+
+\chapter{Conclusion} \TEXTE
+
+\tableofcontents
+\end{document}
+%%%% fin exemple %%%%
+
+* L'autre solution consiste dfinir ses propres commandes
+\introduction, \preface, etc, partir des dfinitions
+de \chapter sans prendre en compte la numrotation.
+
+* On peut galement utiliser les commandes toiles et grer
+soit mme la table des matires et ventuellement les en-ttes
+et bas de page.
+
+Exemple :
+\chapter*{Intro}
+\addcontentsline{toc}{chapter}{Intro...}
+%%%% fin exemple %%%%
+
+# 14.7 # Comment enlever le numrotation des pages de tdm ?
+-----------------------------------------------------------
+Il suffit d'inclure les lignes suivantes dans le prambule du
+document :
+%%%% debut macro %%%%
+\makeatletter
+\def\addcontentsline@toc#1#2#3{%
+ \addtocontents{#1}{\protect\thispagestyle{empty}}%
+ \addtocontents{#1}{\protect\contentsline{#2}{#3}{\thepage}}}
+\def\addcontentsline#1#2#3{%
+ \expandafter\@ifundefined{addcontentsline@#1}%
+ {\addtocontents{#1}{\protect\contentsline{#2}{#3}{\thepage}}}
+ {\csname addcontentsline@#1\endcsname{#1}{#2}{#3}}}
+\makeatother
+%%%% fin macro %%%%
+
+================================================================
+[15] BIBLIOGRAPHIE SOUS LATEX
+================================================================
+
+# 15.1 # Comment construire une bibliographie ?
+-----------------------------------------------
+* Il existe deux techniques pour construire une bibliographie :
++ la premire consiste l'intgrer dans le corps mme du
+document (fichier.tex),
++ la seconde consiste la dfinir dans un fichier particulier
+(fichier.bib) puis l'appeler dans le corps du document.
+
+* Technique on-line :
+Il suffit d'appeler l'environnement thebibliography et de
+dfinir des bibitem.
+
+Exemple :
+\begin{thebibliography}{2}
+ \bibitem[label]{cle} Auteur, TITRE, editeur, annee
+ \bibitem[LAM94]{lam1} L. LAMPORT, {\it \LaTeX : A Document
+ preparation system, Addison-Wesley, 1994}
+\end{thebibliography}
+%%%% fin exemple %%%%
+
+[label] dfinit le label qui apparatra dans la bibliographie
+et dans le texte aprs appel de la commande \cite{cle}.
+
+* BibTeX permet de construire simplement une bibliographie. La
+technique consiste alors crire un ou plusieurs fichiers.bib
+qui seront appels dans le document source par la commande
+\bibliography{fichier1, fichier2,...}. BibTeX est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/biblio/bibtex.
+
+Le style de la bibliographie doit tre dfini par
+\bibliographystyle{xxx} avec xxx valant gnralement plain ou
+alpha, mais il existe aussi d'autres styles. La commande
+\bibliographystyle doit tre appele aprs \begin{document}.
+
+Le contenu d'un fichier.bib est un ensemble de dclarations du
+style :
+@ARTICLE{cle,
+author = "liste-noms-auteur",
+title = "titre-article",
+journal = "nom-journal",
+year = "annee-parution",
+}
+% OPTIONAL FIELDS
+% volume = "",
+% number = "",
+% pages = "",
+% month = "",
+% note = "",
+
+La syntaxe des diffrentes dclarations possibles peut se
+trouver dans toute bonne documentation LaTeX ou dans les menus
+des diteurs tels que emacs ou Alpha.
+
+Losqu'on utilise BibTeX, il faut alors enchaner plusieurs
+compilations pour que toutes les rfrences soient exactes.
+Gnralement, il faut excuter une passe LaTeX, une
+passe Bibtex et encore deux passes LaTeX.
+
+* Pour pouvoir inclure dans la bibliographie des rfrences
+des documents qui ne sont pas cits explicitement par une
+commande \cite, il suffit d'inclure la commande
+\nocite{la-ref-non-citee} avant la commande
+\bibliography{fichier_biblio}. Pour faire apparatre toutes les
+rfrences non cites sans toutes les numrer, on peut utiliser
+\nocite{*}.
+
+* BIBDB, disponible sur CTAN, est un gestionnaire de
+bibliographie BIBTEX, facile manipuler qui tourne sous DOS.
+
+* Bibview est un programme tournant sous X11 et permettant la
+saisie et la consultation de fichiers bibtex.
+
+# 15.2 # Comment grer plusieurs bibliographies ?
+-------------------------------------------------
+* Le package 'chapterbib' permet d'inclure une bibliographie
+par chapitre. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/cite/. Les bibliographies
+rparties peuvent alors apparatre comme section de ce chapitre
+grce la commande : \usepackage[sectionbib]{chapterbib}.
+
+* Le package 'bibunits', de A. Fernandez, permet de partager une
+bibliographie en plusieurs units, chacune attenante une
+section, ou un chapitre d'un article ou d'un livre donn.
+
+Exemple :
+
+////////////// fichier rapport.tex /////////////
+\documentclass[a4paper]{report}
+
+\usepackage{bibunits}
+\usepackage{french}
+
+\begin{document}
+\chapter{Algorithmes.}
+
+Prsentation d'algorithmes.
+
+\nocite*
+\bibliographystyle{alpha}
+\bibliography{alg}
+
+\chapter{Gomtrie.}
+
+Texte sur la gomtrie.
+
+\nocite*
+\bibliographystyle{plain}
+\bibliography{geom}
+\end{document}
+
+////////////// fichier alg.bib /////////////
+@UNPUBLISHED{algg,
+author = MPK,
+title = Algorithmes et rythmes,
+note = RAS,
+}
+
+////////////// fichier geom.bib /////////////
+@INBOOK{geomm,
+author = Me again,
+title = Principes de gomtrie,
+chapter = Les droites,
+publisher = Home publishing,
+year = 1997,
+}
+%%%% fin exemple %%%%
+
+* Le package 'bibtopics', de P. Basso, permet de contruire une
+bibliographie gnrale comportant des rubriques diverses
+(livres, articles, thses, ...) ou des sujets divers (physique,
+mathmatiques, ...). Il est disponible par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/contrib/.
+
+Remarque : pour les versions rcentes de LaTeX, il peut tre
+ ncessaire d'inclure les lignes :
+ \makeatletter
+ \let\if@openbib\iffalse
+ \makeatother
+ dans le prambule du document.
+
+* Voici un petit fichier 'multibib.sty' de V. Henn, cr en
+recopiant les dfinitions LaTeX des commandes relatives la
+gestion des bibliographies, et en les rendant paramtrables.
+
+Les commandes qui ont t dfinies sont :
+\newbibliographyGENE{biblio} pour dclarer une bibliographie
+ biblio.
+\citeGENE{biblio}{cl} pour appeler une rfrence.
+\bibliographystyleGENE{biblio-x}{alpha} pour dfinir le style de
+ biblio.
+\bibliographyGENE{biblio}{fichier-biblio1} pour faire
+ rfrence au fichier fichier-biblio1.bib qui contient
+ les rfrences.
+
+%%%% debut macro %%%%
+%% A sauver dans multibib.sty
+%%%%%% biblio generique %%%%%%%%
+
+\newcommand\newbibliographyGENE[1]{%
+\expandafter\expandafter\expandafter\newwrite\@nameuse{@#1aux}
+\immediate\expandafter\expandafter\openout\@nameuse{@#1aux}=#1.aux
+%\expandafter\expandafter\expandafter\show\@nameuse{@#1aux}
+}
+
+\def\citeGENE#1{\@ifnextchar [{\@tempswatrue\@citexGENE{#1}}%
+{\@tempswafalse\@citexGENE{#1}[]}}
+
+\def\@citexGENE#1[#2]#3{\if@filesw\immediate\expandafter%
+\expandafter\expandafter\write\@nameuse{@#1aux}{\string%
+\citation{#3}}\fi
+ \let\@citea\@empty
+ \@cite{\@for\@citeb:=#3\do
+ {\@citea\def\@citea{,\penalty\@m\ }%
+ \def\@tempa##1##2\@nil{\edef\@citeb{\if##1\space##2%
+ \else##1##2\fi}}%
+ \expandafter\@tempa\@citeb\@nil
+ \@ifundefined{b@\@citeb}{{\reset@font\bf ?}\@warning
+ {Citation `\@citeb' on page \thepage \space undefined}}%
+ \hbox{\csname b@\@citeb\endcsname}}}{#2}}
+
+\def\bibliographyGENE#1#2{\if@filesw\immediate\expandafter%
+\expandafter\expandafter\write\@nameuse{@#1aux}{\string%
+\bibdata{#2}}\fi
+ \@input{#1.bbl}}
+
+\def\bibliographystyleGENE#1#2{\if@filesw\immediate\expandafter%
+\expandafter\expandafter\write\@nameuse{@#1aux}
+ {\string\bibstyle{#2}}\fi}
+
+\def\nociteGENE#1#2{\@bsphack
+ \if@filesw\immediate\write\@nameuse{@#1aux}{\string%
+ \citation{#2}}\fi
+ \@esphack}
+%%%% fin macro %%%%
+
+Exemple d'utilisation :
+Les fichiers gene.bib et speci.bib contiennent respectivement
+une rfrence bibliographie de cl cle-gene et cle-speci.
+
+\documentclass{report}
+\usepackage{multibib}
+\usepackage{french}
+
+\begin{document}
+
+\newbibliographyGENE{Toto}
+\newbibliographyGENE{Titi}
+
+\chapter{Introduction.}
+ blabla bla \citeGENE{Toto}{cle-gene} et
+\citeGENE{Titi}{cle-speci} rebla rebla rebla
+
+\bibliographystyleGENE{Toto}{plain}
+\bibliographyGENE{Toto}{gene}
+
+\bibliographystyleGENE{Titi}{alpha}
+\bibliographyGENE{Titi}{speci}
+
+\end{document}
+
+il faut alors compiler de la manire suivante :
+latex fichier-source
+bibtex Toto
+bibtex Titi
+latex fichier-source
+latex fichier-source
+%%%% fin exemple %%%%
+
+# 15.3 # Comment changer de langue dans une bibliographie ?
+-----------------------------------------------------------
+* Il existe des versions francises des styles bibliographiques
+(fplain, falpha, fralpha, frealfullname...) qui ne sont pas
+parfaits mais qui peuvent tre modifis facilement. Voir la
+distribution GUTenberg.
+
+Exemple :
+\documentstyle{falpha}
+%%%% fin exemple %%%%
+
+* Sachant que les items d'une bibliographie sont des
+paragraphes, ils peuvent commencer par la spcification d'une
+langue. Si on utilise le package 'french', on dispose des
+commandes \french et \english et si l'on utilise le package
+'babel', il faut utiliser la commande \selectlanguage{} (cf.
+paragraphe 11.1).
+
+* Voir galement le package 'frbib' pour les bibliographies
+franaises.
+
+* Le package 'mlbib' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/mlbib/ permet de grer des
+bibliographies multilingues.
+
+# 15.4 # Comment renvoyer une rfrence en note de bas de page ?
+----------------------------------------------------------------
+* Pour remplacer une rfrence insre dans le texte par la
+commande \cite, par un appel une note de bas de page
+contenant une rfrence succinte un document (la rfrence
+dtaille apparaissant toujours dans la bibliographie), il faut
+redfinir la commande \cite dans le prambule du document par :
+%%%% debut macro %%%%
+\makeatletter
+\def\@cite#1#2{%
+ \footnote{#1\if@tempswa, #2\fi}}
+\makeatother
+%%%% fin macro %%%%
+
+Les informations reportes dans la note de bas de page
+dpendent du style de bibliographie choisi.
+
+* Le package 'overcite', de D. Arseneau, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/cite/. Il permet de faire
+rfrence des documents par un exposant.
+
+Le problme qui se pose alors est de distinguer les rfrences,
+des notes de bas de page. Si le document contient moins de 10
+notes de bas de page, on peut utiliser la commande
+\renewcommand{\thefootnote}{\fnsymbol{footnote}}. Sinon pour
+disposer de 10 notes de bas de page par page, il existe le
+package 'footnote' de R. Fairbairns disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/footnote/.
+
+Exemple :
+\usepackage[perpage,symbol]{footnote}
+%%%% fin exemple %%%%
+
+* Le package 'camel' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/camel/, propose diffrents
+styles de bibliographies renvoyant des notes de bas de page.
+
+* E. Domenjoud a galement crit le package 'footbib',
+disponible sur CTAN, qui permet de faire cela.
+Eric.Domenjoud@loria.fr.
+
+# 15.5 # Comment faire rfrence un document ?
+------------------------------------------------
+Il suffit d'utiliser la commande \cite avec en paramtre la cl
+du document (cf. paragraphe 15.1). La commande \cite peut
+prendre un texte en option.
+
+Exemple :
+Voir~: \cite[chapitre 1]{cle}.
+%%%% fin exemple %%%%
+
+# 15.6 # Comment grouper des rfrences multiples ?
+---------------------------------------------------
+* Le package 'cite' de D. Arseneau est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/cite/. Il permet de trier
+et de grouper les rfrences multiples. Par exemple, il permet
+automatiquement de gnrer [1-6] au lieu de lister [1, 2, 3, 4,
+5, 6].
+
+* Il existe galement les packages 'mcite' et 'rangecite' (pour
+LaTeX2.09) disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/mcite/ et dans
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/.
+
+# 15.7 # Comment changer le titre de la bibliographie ?
+-------------------------------------------------------
+Suivant la classe de document que l'on utilise (article,
+book, report, ...), il faut redfinir :
+\renewcommand{\bibname}{R\'ef\'erences}
+ou
+\renewcommand{\refname}{R\'ef\'erences}
+dans le prambule.
+
+Remarque : avec certains packages comme french, il faut placer
+ cette nouvelle dfinition de commande aprs le
+ \begin{document}.
+
+# 15.8 # Comment changer le style de la bibliographie ?
+-------------------------------------------------------
+* Il existe un certain nombre de style par dfaut (alpha,
+plain, unsrt, abbrrv) que l'on peut appeler par la commande
+\bibliographystyle{xxx} place aprs la commande
+\begin{document}.
+
+Remarque : Certains styles comme plain, acm ou apalike trient
+ alphabtiquement les rfrences d'une bibliographie
+ suivant le premier auteur de chaque rfrence.
+ D'autres comme alpha utilisent la premire lettre du
+ nom de chacun des auteurs multiples.
+
+* Il existe galement le package 'custom-bib' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/supported/custom-bib/ qui permet de
+dfinir ses propres styles sans avoir se plonger dans le
+language BibTeX. Le programme est interactif.
+
+* De mme le package 'natbib' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/natbib. Il
+permet entre autres de classer la bibliographie de plusieurs
+faons diffrentes, notamment par ordre alphabtique pour les
+auteurs, par l'anne de parution, etc.
+
+* Pour remplacer la numrotation [1] par 1., on peut utiliser la
+commande :
+\makeatletter
+\renewcommand{\@biblabel}[1]{\quad #1.}
+\makeatother
+
+* Pour supprimer toute numrotation, il faut utiliser de la mme
+manire :
+\makeatletter
+\renewcommand{\@biblabel}[1]{}
+\makeatother
+
+* Le package 'easybib' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/easy/ permet par une syntaxe
+simple de dfinir ses propres styles bibliographiques.
+
+# 15.9 # Comment construire une bibliographie partir de plusieurs fichiers .bib ?
+-----------------------------------------------------------------------------------
+Pour cela il existe le package 'biblist' de J. chrod, disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/biblist/.
+
+Exemple :
+\documentclass[12pt]{article}
+\usepackage{biblist}
+\begin{document}
+\nocite{*}
+\bibliographystyle{plain}
+\bibliography{bibfile1,bibfile2,...}
+\end{document}
+%%%% fin exemple %%%%
+
+# 15.10 # Comment utiliser la commande \cite dans un \caption ?
+---------------------------------------------------------------
+On peut mettre la commande \cite dans un \caption condition de
+la protger : \protect\cite.
+
+# 15.11 # Comment rfrencer une thse franaise ou un mmoire ?
+----------------------------------------------------------------
+Il faut dfinir de nouvelles rfrences. Pour cela, copier le
+fichier .bst dans un autre fichier .bst avec un nom diffrent
+et rechercher PhD thesis puis remplacer par Thse de doctorat.
+
+Exemple :
+FUNCTION {thesedoc}
+{ output.bibitem
+format.authors "author" output.check
+new.block
+format.btitle "title" output.check
+new.block
+"Th\`ese de Doctorat" format.thesis.type output.nonnull
+school "school" output.check
+address output
+format.date "year" output.check
+new.block
+note output
+fin.entry
+}
+%%%% fin exemple %%%%
+
+Idem pour les mmoires de DEA :
+
+FUNCTION {memdea}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ format.title "title" output.check
+ new.block
+ "M\'emoire de D.E.A." format.thesis.type output.nonnull
+ school "school" output.check
+ address output
+ format.date "year" output.check
+ new.block
+ note output
+ fin.entry
+}
+
+# 15.12 # Comment supprimer la virgule supplmentaire dans une liste d'auteurs ?
+--------------------------------------------------------------------------------
+Par dfaut, dans une liste d'auteurs le "et" qui introduit le
+dernier auteur est prcd d'une virgule. Pour la supprimer, il
+faut modifier la fonction format.names dans un nouveau fichier
+.bst de la manire suivante :
+
+%%%% debut macro %%%%
+FUNCTION {format.names}
+{ 's :=3D
+ #1 'nameptr :=3D
+ s num.names$ 'numnames :=3D
+ numnames 'namesleft :=3D
+ { namesleft #0 > }
+ { s nameptr "{ff~}{vv~}{ll}{, jj}" format.name$ 't :=3D
+ nameptr #1 >
+ { namesleft #1 >
+ { ", " * t * }
+ { namesleft #2 >
+ { "," * }
+ 'skip$
+ if$
+ t "others" =3D
+ { " et~al." * }
+ { " and " * t * }
+ if$
+ }
+ if$
+ }
+ 't
+ if$
+ nameptr #1 + 'nameptr :=3D
+ namesleft #1 - 'namesleft :=3D
+ }
+ while$
+}
+%%%% fin macro %%%%
+
+# 15.13 # Comment configurer la commande \cite ?
+------------------------------------------------
+* Le package 'cite' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/cite/ offre certaines
+possibilits.
+
+Exemple :
+\usepackage{cite}
+\renewcommand\citepunct{;\penalty999\ }
+%%%% fin exemple %%%%
+
+* Pour afficher une cl la place du label [??] dans le cas o
+LaTeX/BibTex ne trouve pas la cl spcifie dans la
+bibliographie, on peut utiliser la macro suivante :
+
+%%%% debut macro %%%%
+\def\@citex[#1]#2{%
+ \let\@citea\@empty
+ \@cite{\@for\@citeb:=#2\do
+ {\@citea\def\@citea{,\penalty\@m\ }%
+ \edef\@citeb{\expandafter\@firstofone\@citeb}%
+ \if@filesw\immediate\write\@auxout{\string\citation{\@citeb}}
+ \fi
+%%%% Ligne originale %%%%
+% \@ifundefined{b@\@citeb}{\mbox{\reset@font\bfseries ?}%
+%%%% Ligne modifie %%%%
+ \@ifundefined{b@\@citeb}{\mbox{\reset@font\bfseries \@citeb}%
+ \G@refundefinedtrue
+ \@latex@warning
+ {Citation `\@citeb' on page \thepage \space undefined}}%
+ {\hbox{\csname b@\@citeb\endcsname}}}}{#1}}
+%%%% fin macro %%%%
+
+# 15.14 # Comment construire une liste d'auteurs ?
+--------------------------------------------------
+Pour sparer les lments d'une liste d'auteurs, il faut
+utiliser "and".
+
+Exemple :
+Dewitt, D.J. and Naughton, J.
+%%%% fin exemple %%%%
+
+# 15.15 # Comment spcifier un tri dans une bibliographie ?
+-----------------------------------------------------------
+Il existe l'outil BibTool disponible sur
+ftp://ftp.fdn.org/pub/CTAN/biblio/bibtex/utils/bibtool/ ou sur
+http://www.aber.ac.uk/~dbt93/Downloads/bibtool/. BibTool est un
+outil de manipulation de bases de donnes BibTeX et il permet en
+particulier de spcifier diffrents ordres de tri pour une
+bibliographie.
+
+Exemples :
+* bibtool -s file.bib -o the_new_bibtex_file.bib
+pour trier suivant les auteurs et les titres
+* bibtool -s -- 'sort.format={%d(year)}' file.bib -o
+the_new_bibtex_file.bib
+pour trier par ordre croissant des annes de parution
+* bibtool -s -- 'sort.format={%s($type)%N(author)}' gn-publ.bib
+pour trier par classe de document et par auteur.
+
+L'appel du fichier ainsi tri se fait alors par exemple par :
+\documentclass{article}
+\begin{document}
+\nocite{*}
+\bibliographystyle{unsrt}
+\bibliography{the_new_bibtex_file}
+\end{document}
+%%%% fin exemple %%%%
+
+# 15.16 # Comment rfrencer les pages contenant des citations ?
+----------------------------------------------------------------
+Il faut utiliser le package 'backref' disponible sur CTAN.
+
+# 15.17 # O trouver des styles de bibliographie ?
+--------------------------------------------------
+* Le package 'biblist' de J. Schrod offre diffrents styles de
+bibliographie prdfinis. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/biblist/.
+
+* Le package 'apacite' est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/biblio/bibtex/contrib/.
+
+* Le package 'bbtbase' disponible sur CTAN propose des styles
+bibliographiques de base.
+
+* De nombreux autres styles sont disponibles sur CTAN.
+
+# 15.18 # Comment faire des rfrences croises ?
+-------------------------------------------------
+Il faut utiliser le champ crossref de bibtex.
+
+Exemple :
+@InProceedings{contejean96rta,
+ author = "Evelyne Contejean and Claude March\'e",
+ title = "{CiME: Completion Modulo $E$}",
+ crossref = "rta96",
+ pages = "416--419",
+ year = 1996,
+ note = "System Description",
+ ftp = "ftp://ftp.lri.fr/LRI/art/march/cime-rta96.ps.gz",
+ abstract = "http://www.lri.fr/~marche/cime-rta96.html"
+}
+
+@Proceedings{rta96,
+ title = "7th International Conference on ...",
+ booktitle = "7th International Conference on ...",
+ editor = "Harald Ganzinger",
+ publisher = SV,
+ year = 1996,
+ month = jul,
+ address = "New Brunswick, NJ, USA",
+ series = LNCS,
+ volume = 1103,
+}
+%%%% fin exemple %%%%
+
+ATTENTION : l'ordre de dclaration @InProceedings/@Proceedings
+ dans le fichier .bib est important.
+
+# 15.19 # Comment citer une URL ?
+---------------------------------
+* Le style harvard propose un champ URL. Il est disponible :
+http://www.arch.su.edu.au/~peterw/latex/harvard/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/harvard/.
+
+* Le style bibliographique 'utphys', de J. Distler, disponible
+http://xxx.lanl.gov/hypertex/bibstyles/ ajoute le champ eprint
+toutes les entres BibTeX classiques.
+
+* On peut galement utiliser la macro @MISC et mettre la
+rfrence URL dans le champ note.
+
+* M. Moreau propose la solution suivante :
+J'ai recupr le fichier falpha.bst auquel j'ai ajout :
+
+FUNCTION {format.url}
+{ url empty$
+ {"empty"}
+ { url emphasize }
+ if$
+}
+
+FUNCTION {onTheNet}
+{ output.bibitem
+ format.authors output
+ format.title "title" output.check
+ new.block
+ institution "institution" output.check
+ format.date output
+ new.block
+ format.url "url" output.check
+ fin.entry
+}
+
+Autrement dit, si on peut avoir des documents de type onTheNet avec
+pour entre obligatoire : title, institution, url et entre
+optionnelle : author, year, month, note. L'URL est indique en
+italique.
+
+# 15.20 # Comment dfinir des initiales deux lettres ?
+--------------------------------------------------------
+En franais, les prnoms commencant par Ch, Ph, Th... ont pour
+initiales leurs deux premires lettres (Ex : Philippe --> Ph.).
+Pour forcer BibTeX considrer ces groupes de lettres, il faut
+utiliser : {\relax Ph}ilippe. BibTeX prend alors tout le groupe
+{..} pour une lettre. La commande \relax est considre comme
+une commande d'accent qui est supprime lors du tri
+alphabtique. Elle est ncessaire car lorsqu'un groupe apparat
+dans un nom, BibTeX s'attend trouver une commande d'accent
+juste aprs l'accolade ouvrante.
+
+# 15.21 # Comment conserver les majuscules dans les titres ?
+------------------------------------------------------------
+Il suffit de mettre les majuscules entres accolades.
+
+# 15.22 # Comment changer l'espace entre les item ?
+---------------------------------------------------
+Il faut copier la dfinition de l'environnement thebibliography
+qui se trouve dans le fichier de style de la classe utilise
+(par exemple article.cls pour un article) dans un fichier de
+style (qui sera appel via une commande \usepackage) ou dans le
+prambule de votre document (entre \makeatletter, \makeatother).
+Il faut ensuite remplacer \newenvironment par \renewenvironment
+et modifier la dfinition en ajoutant \setlength{\itemsep}{0pt}
+aprs \list.
+
+# 15.23 # Comment raliser des fiches de lecture ?
+--------------------------------------------------
+* S. O. Genaud (genaud@galaad.u-strasbg.fr) a crit un petit
+logiciel de gestion des rfrences bibliographiques au format
+BibTeX, sous la forme d'une interface graphique. La version
+actuelle n'est peut tre pas exempte de tout bug. Elle tourne
+sur Linux, SunOS et Solaris avec la librairie xview.
+
+Pour rcuprer l'excutable ou avoir plus d'informations :
+http://icps.u-strasbg.fr/~genaud/FRM/
+
+Le programme bibfrm permet de lire un fichier BibTeX ou de crer
+un fichier de rfrences bibliographiques au format BibTeX et
+d'associer chaque rfrence un rsum. L'interface graphique
+permet de savoir immdiatement quels sont les champs optionnels
+et obligatoires pour un type de document donn. Le logiciel
+permet de parcourir les diffrentes rfrences du fichier, de
+faire une recherche sur une chane, de trier les rfrences par
+nom d'auteur, anne ou type de document. Pour chaque rfrence,
+un rsum peut tre saisi dans l'diteur de texte incorpor dans
+l'interface. Ce rsum peut tre envoy par mail une liste de
+diffusion prdfinie.
+
+* Le package 'abstbook' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ permet de mettre en page des
+catalogues de rsums.
+
+# 15.24 # Comment utiliser la commande \cite dans un item ?
+-----------------------------------------------------------
+Pour utiliser la commande \cite dans l'item d'un environnement
+description, il suffit de l'encadrer dans des accolades.
+
+Exemple :
+\item[{\cite[\S3.1]{Author1}}]
+%%%% fin exemple %%%%
+
+# 15.25 # Comment gnrer l'expression et al automatiquement ?
+--------------------------------------------------------------
+Voici une fonction "format.names" (tire de plain.bst) o V. Henn
+a rajout quelques lignes pour mettre un et al pour les auteurs
+de numro suprieurs 4. N'importe quel style biblio utilise une
+fonction avec une syntaxe similaire, il n'y a qu' insrer les
+nouvelles lignes dans la fonction format.names (juste avant la
+fin du while) du fichier biblio qui vous plat et le tour est
+jou...
+
+%%%% debut macro %%%%
+FUNCTION {format.names}
+{ 's :=
+ #1 'nameptr :=
+ s num.names$ 'numnames :=
+ numnames 'namesleft :=
+ { namesleft #0 > }
+ { s nameptr "{ff~}{vv~}{ll}{, jj}" format.name$ 't :=
+ nameptr #1 >
+ { namesleft #1 >
+ { ", " * t * }
+ { numnames #2 >
+ { "," * }
+ 'skip$
+ if$
+ t "others" =
+ { " et~al." * }
+ { " and " * t * }
+ if$
+ }
+ if$
+ } % fin du "si nameptr > 1"
+ 't % "si nameptr = 1"
+ if$
+ nameptr #1 + 'nameptr :=
+ namesleft #1 - 'namesleft :=
+
+% ------------------------------
+% si ce stade on se retrouve avec des noms placer et que
+% le pointeur nameptr est gal 4 alors il faut
+% 1. ajouter un "et al."
+% 2. ne pas prendre en compte les auteurs suivants : nameleft:=0
+ nameptr #4 = namesleft #0 > and
+ { " \emph{et~al.}" *
+ #0 'namesleft :=
+ }
+ 'skip$
+ if$
+% fin des ajouts
+% ------------------------------
+
+ }
+ while$ % tant qu'il reste des nom placer
+}
+%%%% fin macro %%%%
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part5 b/help/LaTeX-FAQ-francaise/part5
new file mode 100644
index 0000000000..7aa236b920
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part5
@@ -0,0 +1,2443 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!howland.erols.net!netnews.com!opentransit.net!proxad.net!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:18 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - parties 16 a 24
+Message-ID: <faq-fctt-p520010608133118@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p520010501143416@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 2432
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23526 fr.usenet.reponses:20392
+
+Archive-name: fr/faq-latex-francaise/part5
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+================================================================
+[16] INDEX
+================================================================
+
+# 16.1 # Quelles sont les commandes de base ?
+---------------------------------------------
+Pour permettre LaTeX (via un gnrateur d'index) de construire
+un index, il faut rfrencer dans le texte tous les mots que
+l'on souhaite y voir apparatre. La commande utiliser pour
+cela est \index. Elle permet la construction d'un fichier .idx
+dans lequel sont rpertories toutes les rfrences indiques
+dans le texte.
+
+Les entres de ce fichier sont ensuite tries dans un fichier
+nom_fichier.ind via la compilation :
+ makeindex fichier.idx
+qui sera inclut dans le source .tex par la commande \printindex
+ou \input{nom_fichier.ind}.
+
+Pour indiquer LaTeX qu'il doit construire un index, il faut
+galement ajouter la commande \makeindex dans le prambule du
+document.
+
+Remarque : compte tenu du temps pris pour gnrer un index, il
+ est conseill de ne faire apparatre la commande
+ \makeindex que lors des dernires compilations.
+
+Si les commandes de gnration d'index ne sont pas dfinies par
+dfaut, ou dans un package autre que makeidx (tel que french de
+B. Gaulle par exemple), il faut utiliser le package 'makeidx'
+(cas notamment de la commande \printindex).
+
+Remarque : Pour viter de rpter la commande \index dans un
+ texte o elle devrait apparatre souvent, on peut
+ utiliser les commandes \index{mot_a_indexer|(} au
+ dbut du texte et \index{mot_a_indexer|)} la fin.
+
+Pour plus de dtails, consulter
+ftp://ftp.fdn.org/pub/CTAN/indexing/makeindex/doc/makeindex.ps
+
+# 16.2 # Comment construire un index hirarchique ?
+---------------------------------------------------
+Pour construire un index plusieurs niveaux d'entre, il faut
+utiliser les commandes suivantes :
+\index{niveau1} comme prcdemment puis, pour faire apparatre
+un sous-thme de ce niveau, on appellera :
+\index{niveau1!niveau1.1}.
+
+Exemple :
+\documentclass{report}
+\usepackage{makeidx}
+\usepackage{french}
+\pagestyle{empty}
+\makeindex
+
+\begin{document}
+\chapter{Sports.}
+Le sport\index{Sport} c'est fantastique~!
+
+Mes sports prfrs sont~:
+\begin{itemize}
+ \item l'quitation\index{Sport!Equitation} et en particulier
+ les disciplines de dressage\index{Sport!Equitation!Dressage}
+ et de complet\index{Sport!Equitation!Complet}~:
+ \item l'escalade\index{Sport!Escalade} et surtout les
+ sorties en falaise~;
+ \item le judo\index{Sport!Judo}.
+\end{itemize}
+
+\printindex
+\end{document}
+%%%% fin exemple %%%%
+
+Ces fonctions sont disponibles dans le package 'index' ou
+(exclusif) 'french'.
+
+# 16.3 # Quels sont les gnrateurs d'index ?
+---------------------------------------------
+* makeindex, pour LaTeX sous Unix, Macintosh, MS-DOS ou OS/2 est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/indexing/makeindex/,
+ftp://ftp.fdn.org/pub/CTAN/systems/mac/macmakeindex.sit et dans les ditributions emTeX et
+gTeX.
+
+* texindex, fond sur sed pour LaTeX sous Unix, est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/support/texindex/.
+
+* idxtex, pour LaTeX sous VMS, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/indexing/glo+idxtex/.
+
+* texix pour TeX sur CMS et Macintosh.
+
+# 16.4 # Comment changer le style de certains mots indexs ?
+------------------------------------------------------------
+Il faut utiliser la commande :
+\index{mot_a_indexer@mot_reporte}
+
+Exemple :
+\documentclass{report}
+\usepackage{makeidx}
+\usepackage{french}
+\pagestyle{empty}
+\makeindex
+
+\begin{document}
+\chapter{Sports.}
+Le sport\index{Sport@\textbf{Sport}} c'est fantastique~!
+
+Mes sports prfrs sont~:
+\begin{itemize}
+ \item l'quitation\index{Sport@\textbf{Sport}!Equitation} et
+ en particulier les disciplines de
+ dressage\index{Sport@\textbf{Sport}!Equitation!Dressage} et de
+ complet\index{Sport@\textbf{Sport}!Equitation!Complet}~:
+ \item l'escalade\index{Sport@\textbf{Sport}!Escalade} et
+ surtout les sorties en falaise~;
+ \item le judo\index{Sport@\textbf{Sport}!Judo}.
+\end{itemize}
+
+\printindex
+\end{document}
+%%%% fin exemple %%%%
+
+# 16.5 # Comment changer le style des pages de rfrence ?
+----------------------------------------------------------
+Pour mettre en relief certains numros de rfrence par rapport
+ d'autres, on peut utiliser les macros suivantes :
++ pour appeler un numro de page en gras (LaTeX2e) :
+ \newcommand{\idb}[1]{\textbf{#1}}
++ pour appeler un numro de page en italique (LaTeX2.09) :
+ \newcommand{\idi}[1]{\it{#1}}
+
+La rfrence dans le texte se fait alors par :
+\index{mot_a_indexer|idb}
+
+# 16.6 # Comment rappeler certains mots dans un haut de page ?
+--------------------------------------------------------------
+Le package 'fancyhdr' (LaTeX2e) disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fancyhdr/ permet entre autres de
+faire apparatre le premier mot de la page en haut gauche de
+la page et le dernier en haut droite.
+
+# 16.7 # Comment gnrer plusieurs index ?
+------------------------------------------
+* Il faut utiliser le package 'index' (et, si ncessaire,
+charger le package 'french' aprs).
+
+* Il existe galement le package 'multind'.
+
+Remarque : french (3.45) fonctionne bien avec "multind", par
+ contre "multind" n'implmente pas toutes les
+ commandes d'index (notamment, le sparateur "!" ne
+ fonctionne pas).
+AL: toujours vrai ?
+
+# 16.8 # Qu'est ce que IdXTeX ?
+-------------------------------
+IdXTeX programme crit en C par R. Aurbach facilite la
+gnration d'index. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/indexing/glo+idxtex/.
+
+# 16.9 # Qu'est ce que xindy ?
+------------------------------
+xindy est un systme d'indexation. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/xindy/. Il est capable de grer diffrentes
+langues suivant diffrentes lettres (notamment les lettres
+accentues) et rgles de tri. Il est paramtrable en fonction de
+repres de localisation dans le document qui ne correspondent
+pas forcment un numro de page ou de paragraphe prdfini.
+
+Pour plus de dtails, consulter :
+http://www.iti.informatik.th-darmstadt.de/xindy/.
+
+================================================================
+[17] GLOSSAIRE
+================================================================
+
+# 17.1 # Quelles sont les commandes de base ?
+---------------------------------------------
+* La cration d'un glossaire avec le package 'french'
+s'apparente la cration d'un index. La commande d'insertion
+d'un mot dans le glossaire est \glossary, la commande de
+construction du fichier .glo est \makeglossary. L'insertion du
+glossaire dans le document source se fait par \glossaire et
+\input{fichier.glo}.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\makeglossary
+
+\begin{document}
+ Construisons un glossaire avec les abrviations suivantes :
+PS\glossary{[PS :] Pur Sang}, PSA\glossary{[PSA :] Pur Sang
+Arabe}, SF\glossary{[SF :] Selle Franais}, PP\glossary{[PP :]
+Paso Pruvien}\ldots
+
+\glossaire
+\input{fichier.glo}
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Pour trier un glossaire avec makeindex, il faut utiliser
+la commande :
+ (UNIX) makeindex -s style -o fichier.gls fichier.glo
+L'appel du glossaire se fait alors par la commande
+\printglossary.
+
+Remarque : un exemple de style gglo.ist est disponible sur
+ ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/nomencl/ ou dans
+ http://planck.plmsc.psu.edu/~boris/.
+
+# 17.2 # Quels sont les gnrateurs de glossaire ?
+--------------------------------------------------
+* Le programme "GloTeX" de R. Aurbach, utilise une base de
+donnes pour crer un glossaire. Il est donc possible d'utiliser
+la mme BD pour plusieurs documents, et ainsi d'avoir des
+glossaires cohrents (les mmes termes auront la mme
+dfinition). GloTeX est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/indexing/glo+idxtex/.
+
+* L'outil "GlossTeX", de V. Yavuz, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/glosstex/ est un gnrateur de glossaire, de liste
+d'acronymes ou d'autres listes. Il s'appuie sur LaTeX et
+MakeIndex. Il combine les fonctionnalits de GloTeX et nomencl.
+
+La construction du glossaire ncessite les compilations
+suivantes :
+latex, glosstex, makeindex et encore latex.
+
+Exemple :
+\documentclass{article}
+\usepackage{glosstex}
+\begin{document}
+This document is typeset using \LaTeX\glosstex{LaTeX}.
+ \section*{Glossary}
+ \printglosstex
+\end{document}
+%%%% fin exemple %%%%
+
+================================================================
+[18] STYLES PRDFINIS
+================================================================
+
+# 18.1 # O trouver un style de thse ?
+---------------------------------------
+* Le package 'thesis' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/thesis/ est une classe de thse
+base sur la classe report.
+
+* Le serveur loria prsente quelques exemples de styles de
+thses : http://www.loria.fr/services/tex/.
+
+* La classe 'thloria' de Denis Roegel (roegel@loria.fr)
+est disponible en http://www.loria.fr/~roegel/TeX/TL.html.
+Sa documentation peut aussi tre trouve en
+http://www.loria.fr/tex/guide.html.
+
+* Un autre exemple est disponible l'universit de Californie
+ou sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/ucthesis/.
+
+* utthesis est le package de l'universit du Texas. Il est
+disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/utthesis/.
+
+* Il existe galement le package 'uwthesis' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/uwthesis/ de l'universit
+de Washington.
+
+* Une classe de thse est galement disponible par ftp sur
+ftp://cat.rpi.edu/pub/tibbetts/thesis.zip.
+
+# 18.2 # Comment faire son CV en LaTeX ?
+----------------------------------------
+* Il existe deux packages : 'resume' et 'vita' disponibles sur
+CTAN. 'vita' se trouve sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/vita/.
+
+* Le package 'ESIEEcv' crit par B. Bayart offre un certain
+nombre d'environnements qui facilitent la mise en page type
+d'un CV. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/ESIEEcv/.
+
+Exemple :
+\begin{rubrique}{Titre de la rubrique.}
+ \begin{sousrubrique}
+ \Date{deb-fin}
+ \Duree{longue}
+ \Lieu{Ca c'est passe ici}
+ \Titre{Ce que j'ai fait}
+ \Descr{Quelques details}
+ \Apport{Ce que cela m'a apporte}
+ \Apport{et ca aussi}
+ \end{sousrubrique}
+ \begin{sousrubrique}
+ \Competence{Parlote}
+ \Descr{Bonne maitrise}
+ \end{sousrubrique}
+\end{rubrique}
+%%%% fin exemple %%%%
+
+Remarque : la largeur de la premire colonne peut tre modifie
+ par : \setlength{\largeurcolonne}{2.5cm}
+
+* Voici quelques macros qui peuvent tre utiles :
+Dans le prambule :
+%%%% debut macro %%%%
+% Definition des catgories de rubriques.
+\newcommand{\categorie}[1]{\vspace*{1cm}\noindent%
+ {\large\textsl{#1}\par}\vspace*{2pt}\hrule\vspace*{.5cm}}
+% On definit une colonne pour les dates
+\newlength{\duree}
+\settowidth{\duree}{\textbf{1985-1987}}
+% La seconde colonnes doit occuper le reste de la page
+\setlength{\duree}{-\duree}
+\addtolength{\duree}{\textwidth}
+
+% Definition des rubriques.
+\newcommand{\rubrique}[2]{\noindent{\textbf{#1\ \ }}%
+ \parbox[t]{\duree}{#2}}
+%%%% fin macro %%%%
+
+Utilisation :
+\categorie{Formation~:}
+\rubrique{1990--1992}{tudiant l'cole Machin. Cette cole
+propose un programme~\ldots.
+
+Major de promo.}
+
+\rubrique{1992--1993}{Spcialisation dans le domaine~\ldots.}
+
+\categorie{Exprience~:}
+\rubrique{1987-1988}{Stage ouvrier dans l'usine de carton de
+La Ville aux Cartons.}
+
+* Voici d'autres macros de JM Lasgouttes :
+%%%% debut macro %%%%
+%%%% cv document class
+%%%% Author: Jean-Marc Lasgouttes (Jean-Marc.Lasgouttes@inria.fr)
+%%%% Last modification: 29/11/1996
+%%%% WARNING: this documentclass is really a hack. Don't expect too much.
+
+%%% Basic usage:
+%% \leftheader[width]{text} : defines what should appear in the upper
+%% left of the first page. The optionnal argument `width' specifies
+%% the width of the header (default: 0.48\textwidth). `Text' may
+%% contain \\ to break lines.
+%% \rightheader[width]{text} like \leftheader, but for the right
+%% header.
+%% \makeheader: actually typesets the header.
+%%
+%% \section*{title}: gives a title for a new topic of the CV. The text
+%% is typeset in font \topicfont (by default Sans Serif
+%% semi-condensed bold).
+%% `topic' environment: begins an itemize-like environment where the
+%% argument of \item[] is typeset in font \itemfont (by default Sans
+%% serif). You can also use \\ just after \item[xxx] if the label is
+%% too large.
+%%
+%% The cv document class also has some primitive support for
+%% bibliography. You can use the `thebibliography' environment as
+%% usual (or directly BibTeX). It will provide text similar to the
+%% `topic' environment.
+
+%% Basic definition to have a real LaTeX document class
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesClass{cv}[1996/11/29 Curriculum vitae]
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+\ProcessOptions
+\LoadClass{article}
+
+%% The fonts used for headings
+\newcommand\topicfont{\normalfont\sffamily\fontseries{sbc}\selectfont}
+\newcommand\itemfont{\sffamily}
+
+%% stuff needed for the header
+\newcommand\cv@lh{}\newcommand\cv@rh{}
+\newcommand\cv@lh@l{\z@} \newcommand\cv@rh@l{\z@}
+\newcommand\leftheader[2][0.48\textwidth]{
+ \def\cv@lh@l{#1}
+ \def\cv@lh{#2}}
+\newcommand\rightheader[2][0.48\textwidth]{
+ \def\cv@rh@l{#1}
+ \def\cv@rh{#2}}
+\newcommand\makeheader{\par\noindent
+ \parbox[t]{\cv@lh@l}{\raggedright\cv@lh}
+ \hfill
+ \parbox[t]{\cv@rh@l}{\raggedright\cv@rh}\par\vspace*{2cm}}
+
+%% Redefine \section to use \topicfont
+\renewcommand\section{
+ \@startsection{section}{1}{\z@}
+ {-3.5ex \@plus -1ex \@minus -.2ex}
+ {2.3ex \@plus .2ex}{\topicfont}}
+
+%% Define the topic environment
+\newcommand\@topic@setup{
+ \setlength{\leftmargin}{2cm}
+ \setlength{\rightmargin}{0cm}
+ \setlength{\labelwidth}{1.5cm}
+ \renewcommand{\makelabel}[1]{\itemfont ##1\hfill}}
+\newenvironment{topic}
+ {\list{}{
+ \@topic@setup
+ \let\CV@cr=\\
+ \renewcommand\\{\hspace{0cm}\CV@cr}}}
+ {\endlist}
+
+%% Redefine the thebibliography environment to look like the topic
+%% environment. The argument of thebibliography is ignored
+\renewenvironment{thebibliography}[1]
+ {\section*{Publications}
+ \list{\@biblabel{\theenumiv}}{
+ \@topic@setup
+ \@openbib@code
+ \usecounter{enumiv}
+ \let\p@enumiv\@empty
+ \renewcommand\theenumiv{\@arabic\c@enumiv}}
+ \sloppy \clubpenalty 4000 \widowpenalty 4000 \sfcode`\.=\@m}
+ {\endlist}
+%%%% fin macro %%%%
+
+# 18.3 # O trouver un format de publication ?
+----------------------------------------------
+* Des classes et packages de format de publication dans les
+revues scientifiques telles que IEEE, IFAC, SIAM, SIGGRAPH, etc.,
+sont disponibles sur CTAN.
+
+Pour plus de renseignements sur les documents IEEE, consulter la
+page http://www.ieee.org/pubs/authors.html qui donne des
+rfrences de style pour LaTeX2.09 et LaTeX2e.
+
+* La classe paper, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/paper/, est drive de la classe
+article. Elle est mieux adapte pour la publication, notamment en
+termes de prsentation de la page, le choix des fontes. Elle
+dfinit un certain nombre de macros utiles.
+
+* De mme, la classe elsart est disponible sur CTAN. Cette classe
+est en outre trs bien documente.
+
+* On trouve galement une classe pour journaux d'Academic
+Press, que l'on peut trouver sur
+http://www.academicpress.com/www/journal/latex_a.htm.
+
+* Kluwer propose une classe sur http://www.wkap.nl/kaphtml.htm/STYLEFILES
+
+* Annual Reviews (uniquement pour Annual Review of Nuclear and Particle
+Science) fait de mme sur
+http://www.AnnualReviews.org/ibbin/ibGate.exe?LOADPAGE=%2fARI%2fauthors%2fauthors.htm
+
+* American Chemical Society, ne fournit, quant elle, qu'un "Guidelines"
+sur http://pubs.acs.org/instruct/texguide.html
+
+# 18.4 # O trouver un style de manuel de rfrence ?
+-----------------------------------------------------
+Il existe la classe 'refman' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/refman/.
+
+# 18.5 # O trouver un style de poster ?
+----------------------------------------
+* Il existe le package 'poster' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/poster/. Il permet entre autres d'imprimer un
+texte s'talant sur plusieurs pages avec des parties communes
+de manire pouvoir recoller les morceaux aprs.
+
+* G. Kettl propose galement un style de poster accompagn
+d'une documentation sur
+http://rphibm1.physik.uni-regensburg.de/cluster/software/tex/a0poster.html.
+
+# 18.6 # Comment crer son propre style ?
+-----------------------------------------
+Lorsque l'on veut modifier un style prdfini pour l'adapter
+ses besoins, il est conseill de crer son propre fichier .cls
+dans lequel seront runies les nouvelles commandes de mise en
+page.
+
+Ci-dessous un exemple de V. Henn pour dfinir son propre style
+d'article :
+
+%%%% debut macro %%%%
+%%% A sauver dans MonArticle.cls
+%%%
+%%% Format de style adapt de article.cls
+%%%
+%%% V.H. le 13 avril 1995
+%%%
+
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesClass{MonArticle}[1995/06/20 Article personnel]
+
+%%% Chargement de la classe article, avec transfert d'options
+\PassOptionsToClass{a4paper}{article} % format a4paper par dfaut
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+\ProcessOptions
+
+\LoadClass{article}
+
+%%% Chargement des Packages les plus courants
+\RequirePackage{frbib}
+\RequirePackage{general}
+\RequirePackage{fuzzy}
+\RequirePackage{bigcenter}
+\RequirePackage{traffic}
+\RequirePackage[dvips]{epsfig}
+\RequirePackage{epic}
+\RequirePackage{french}
+
+%%% Destination de l'article (propos pour une conf, une revue...)
+
+\def\Destination#1{\ifx{#1}{}\gdef\@Destination{}%
+\else\gdef\@Destination{#1}\fi}
+
+%%% Destination vide par dfaut
+
+\Destination{}
+
+%%% Auteur par dfaut, pour eviter de recopier a chaque fois
+
+\author{Vincent \fsc{Henn}\thanks{Laboratoire d'ingnierie
+circulation--transport, (Unit mixte \lsc{INRETS}--\lsc{ENTPE}),
+109, Avenue Salvador Allende, Case 24,
+F--69675 \fsc{Bron} Cedex, {\tt henn@inrets.fr}.}}
+%%%% fin macro %%%%
+
+Utilisation :
+\documentclass[a4paper,11pt]{MonArticle}
+
+\title{Exemple d'article}
+\Destination{IEEE}
+\begin{document}
+\maketitle
+
+\chapter{Introduction}
+
+Bla bla
+
+\end{document}
+
+================================================================
+[19] CRATION DE TRANSPARENTS
+================================================================
+
+# 19.1 # Quels sont les packages et styles existants ?
+------------------------------------------------------
+* La classe 'seminar', de T. van Zandt, offre de nombreuses
+possibilits et peu de modifications sont ncessaires pour
+pouvoir l'utiliser avec des documents initialement crits pour
+"slide". seminar est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/seminar/inputs/.
+
+Remarque : A l'origine, seminar.sty tait un package ;
+ aujourd'hui, il a volu en classe.
+
+La lecture du cahier GUTenberg no 16 disponible en ligne
+l'URL :
+http://www.gutenberg.eu.org/publications/publis.html
+peut tre utile. Voir galement la page
+http://tug.cs.umb.edu/applications/ ou
+http://www.tug.org/applications/Seminar/ qui prsente notamment
+une FAQ.
+
+* Le package 'cours' permet galement de raliser des
+transparents. Il permet, partir d'un fichier source de crer
+des transparents et de grer un syllabus. Cela fonctionne trs
+bien sous LaTeX2.09 et LaTeX2e (disponible sur les serveurs
+CTAN).
+
+* La classe 'foiltex', de J. Hafner, est pas mal du tout.
+Elle permet de dfinir des enttes et des pieds de page. Elle a
+t adapte LaTeX2e et est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/foiltex/.
+
+* La classe 'slides' est la classe de document fournie avec
+LaTeX en remplacement de SliTeX, la solution propose avec
+LaTeX2.09 et disparue avec lui.
+
+Exemple :
+\documentclass[a4paper]{slides}
+
+\begin{document}
+\begin{slide}
+Sous cet environnement slides, le texte est :
+\begin{itemize}
+ \item en gros caractres,
+ \item d'une fonte sans serif,
+ \item centr verticalement.
+\end{itemize}
+
+\end{slide}
+\end{document}
+%%%% fin exemple %%%%
+
+# 19.2 # Comment dfinir un contour pour des transparents ?
+-----------------------------------------------------------
+* Avec le package 'seminar', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/seminar/.
+
+Exemple :
+\slideframe[]{oval}
+%%%% fin exemple %%%%
+
+* Il existe galement le package 'fancybox', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/others/seminar/inputs/, qui dfinit
+des fonctions telles que \shadowbox, \doublebox, \ovalbox,...
+
+* On peut galement utiliser une commande \special (cf.
+paragraphe 29.8).
+
+Exemple :
+Cet exemple ncessite dvips et travaille sur un format a4. Il
+permet d'obtenir un fond jaune clair avec un cadre noir 1 cm
+du bord de la feuille et de dfinir deux zones de texte en
+vert.
+%%%% debut macro %%%%
+\special{
+ !userdict begin /bop-hook {gsave
+ 1 1 0.5 setrgbcolor clippath fill
+ 0 setlinecap 0 setlinejoin 2 setlinewidth 0 setgray
+ /Times-Bold findfont 10 scalefont setfont newpath
+ (Maurizio Loreti, 1996-02-25)
+ dup stringwidth pop neg 510 add 25 moveto
+ currentpoint 3 -1 roll 0 1 0 setrgbcolor show 0 setgray
+ moveto -6 3 rmoveto 28 28 28 814 15 arcto
+ 28 814 567 814 15 arcto 79 814 lineto 6 -3 rmoveto
+ 0 1 0 setrgbcolor
+ (CMS week at CERN)
+ show 0 setgray 6 3 rmoveto 567 814 567 28 15 arcto
+ 567 28 516 28 15 arcto 516 28 lineto stroke grestore}
+ def end
+}
+%%%% fin macro %%%%
+%%%% fin exemple %%%%
+
+# 19.3 # Comment inclure des commentaires dans les transparents ?
+-----------------------------------------------------------------
+* Dans l'environnement slide, l'environnement note permet de
+taper du texte qui sera imprim sur une page spare sans tre
+intgr dans un transparent. Cela permet l'auteur de taper
+ses notes personnelles sans qu'elles apparaissent dans un
+transparent.
+
+* Le package 'xcomment' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/seminar/src/ permet de grer
+l'inclusion ou non de certains commentaires.
+
+# 19.4 # Comment modifier l'interligne sous seminar ?
+-----------------------------------------------------
+Pour modifier l'espacement entre lignes l'intrieur des
+paragraphes (sous seminar), il faut utiliser le paramtre
+\slidestretch (cf. page 9 de la documentation de Seminar).
+
+Exemple :
+\documentclass[portrait]{seminar}
+\begin{document}
+\begin{slide*}
+ Ceci est le texte de la d\'eclaration que j'ai \`a vous
+ communiquer. Ceci est le texte de la d\'eclaration que j'ai
+ \`a vous communiquer. Ceci est le texte de la d\'eclaration
+ que j'ai \`a vous communiquer.
+\end{slide*}
+
+\def\slidestretch{0.5}
+\begin{slide*}
+ Ceci est le texte de la d\'eclaration que j'ai \`a vous
+ communiquer. Ceci est le texte de la d\'eclaration que j'ai
+ \`a vous communiquer. Ceci est le texte de la d\'eclaration
+ que j'ai \`a vous communiquer.
+\end{slide*}
+\end{document}
+%%%% fin exemple %%%%
+
+# 19.5 # Comment dfinir des en-ttes et pieds de pages ?
+---------------------------------------------------------
+Le package 'seminar' permet de dfinir des enttes et des pieds
+de pages.
+
+Exemple :
+\documentclass{seminar}
+\usepackage{french,enumerate}
+\newpagestyle{filets}%
+ {\hrulefill}% en haut
+ {\hrulefill\tiny\theslide}% en bas
+\slidepagestyle{filets}
+
+\begin{document}
+\begin{slide}
+ Voici les rsultats de notre socit pour les 5 derniers
+ trimestres :
+ \begin{enumerate}[Q1]
+ \item 120 MF
+ \item 123 MF
+ \item 145 MF
+ \item 143 MF
+ \item 193 MF
+ \end{enumerate}
+\end{slide}
+\end{document}
+%%%% fin exemple %%%%
+
+# 19.6 # Comment modifier la taille du cadre d'un transparent ?
+---------------------------------------------------------------
+Sous seminar, pour un changement local, il suffit de prciser
+les dimensions voules dans le \begin{slide} ou \begin{slide*}.
+
+Pour un changement global, il faut modifier les variables
+\slidewidth et \slideheight.
+
+Exemple :
+\documentclass[a4,portrait]{seminar}
+\usepackage{semcolor}
+
+\begin{document}
+% Cadre de la taille par defaut (en A4)
+\begin{slide*}
+ Texte ...
+\end{slide*}
+
+% Changement global de la taille du cadre
+\addtolength{\slidewidth}{1cm}
+\addtolength{\slideheight}{1cm}
+\begin{slide*}
+ Texte...
+\end{slide*}
+
+% Changement local de la taille du cadre
+% [hauteur,largeur] en mode portrait
+% [largeur,hauteur] en mode paysage
+\begin{slide*}[15cm,10cm]
+ Texte
+\end{slide*}
+
+% On revient a la taille prcdente
+\begin{slide*}
+ Texte...
+\end{slide*}
+\end{document}
+%%%% fin exemple %%%%
+
+# 19.7 # Comment empcher les figures de flotter ?
+--------------------------------------------------
+On peut forcer l'option par dfaut H :
+\usepackage{float}
+\newfloat{figure}{H}{lof} %Don't let them float by default
+\newfloat{table}{H}{lot}
+\floatname{figure}{\figurename}
+\floatname{table}{\tablename}
+
+# 19.8 # Comment grer la couleur avec seminar ?
+------------------------------------------------
+* L'exemple suivant montre comment paramtrer la couleur du
+fond.
+
+Exemple :
+\documentclass[a4,portrait]{seminar}
+\usepackage{semcolor}
+
+\newcommand{\SlideColours}[1]{%
+\slideframe[\psset{fillcolor=#1,fillstyle=solid}]{scplain}}
+
+\begin{document}
+\SlideColours{blue}
+ \begin{slide*}
+ Mon transparent avec un fond bleu.
+ \end{slide*}
+\end{document}
+%%%% fin exemple %%%%
+
+* Pour utiliser d'autres couleurs que celles prdfinies (black,
+blue, cyan, darkgray, gray, green, lightgray, magenta, red,
+white, yellow), il faut le faire via l'une des commandes de
+PSTricks dfinissant les couleurs (dans Seminar, par dfaut la
+couleur est en effet gre via PSTricks). PSTricks est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/graphics/pstricks/.
+
+Nanmoins, aujourd'hui il est conseill d'utiliser plutt
+l'extension standard 'color' de LaTeX pour ce faire.
+
+Exemple :
+\documentclass[a4,portrait]{seminar}
+
+% Pour utiliser l'extension standard "color" avec Seminar
+\usepackage[dvips]{pstcol}
+\usepackage{semcolor}
+
+\newcommand{\SlideColours}[1]{%
+\slideframe[\psset{fillcolor=#1,fillstyle=solid}]{scplain}}
+
+\definecolor{Bleu}{rgb}{0.,0.,1.}
+\definecolor{Rose}{rgb}{1.,0.75,0.8}
+
+\begin{document}
+\SlideColours{Bleu}
+ \begin{slide*}
+ Mon transparent avec un fond bleu.
+ \end{slide*}
+
+\SlideColours{Rose}
+ \begin{slide*}
+ Mon transparent avec un fond rose.
+ \end{slide*}
+\end{document}
+%%%% fin exemple %%%%
+
+* On peut galement composer un fond dgrad.
+
+Exemple :
+\documentclass[a4,portrait]{seminar}
+
+% To use the standard "color" package with Seminar
+\usepackage[dvips]{pstcol}
+\usepackage{semcolor}
+
+\usepackage{gradient}
+\definecolor{Gold}{rgb}{1.,0.84,0.}
+\slideframe[\psset{fillstyle=gradient,gradbegin=Gold,
+ gradend=yellow, gradmidpoint=0.5}]{scplain}
+\begin{document}
+ \begin{slide*}
+ Sympa le dgrad !
+ \end{slide*}
+\end{document}
+%%%% fin exemple %%%%
+
+# 19.9 # Comment imprimer des transparents en miroir ?
+------------------------------------------------------
+* Pour imprimer en miroir un document (pour faire de la
+photocomposition), il existe un prologue PostScript pour DVIPS
+que voici :
+
+%%%% debut macro %%%%
+%% A sauver dans miroir.pro
+% Pour imprimer des films transparents en miroir
+% Pascal PERICHON - Distribution PC-TeXMF 2.6 - (c) 1997
+userdict begin
+/bop-hook{
+ 210 2.834 mul
+ 0 translate
+ -1 1 scale
+}def end
+%%%% fin macro %%%%
+
+ Il s'utilise de la faon suivante :
+ dvips -hmiroir.pro
+
+Remarque : N'oubliez pas de mettre ce fichier dans la path
+ HEADERS de dvips (ou dans un chemin spcifi dans
+ config.ps pour l'inclusion des en-ttes).
+
+* Le package 'mirr' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/TeX-PS/ permet d'obtenir des fichiers miroir.
+
+# 19.10 # Comment inclure une image de fond ?
+---------------------------------------------
+* Le package 'seminar' permet d'inclure une image de fond.
+
+Exemple :
+\documentclass{seminar}
+\usepackage{semcolor}
+\usepackage{fancybox}
+\usepackage[dvips]{graphicx}
+
+\begin{document}
+
+\newslideframe{IMAGE}%
+{\boxput{\rput(1,0){\includegraphics[scale=0.4]{image.eps}}}{#1}}
+\slideframe*{IMAGE}
+
+\begin{slide}
+ My first word.
+\end{slide}
+
+\begin{slide}
+ My last word.
+\end{slide}
+
+\end{document}
+%%%% fin exemple %%%%
+
+* On peut galement utiliser l'environnement picture.
+
+Exemple :
+\setlength{\unitlength}{1in}
+\begin{picture}(0,0)
+ \put(-2.2,-6){\includegraphics[width=\textwidth]{bilder/sigel.eps}}
+\end{picture}
+%%%% fin exemple %%%%
+
+# 19.11 # Comment imprimer plusieurs transparents par page ?
+------------------------------------------------------------
+Pour cela, il existe le package '2up'.
+
+================================================================
+[20] LETTRES, MAILING ET FAXS
+================================================================
+
+# 20.1 # Comment structurer une lettre ?
+----------------------------------------
+* Il existe pour cela la classe letter. Celle-ci dfinit les
+commandes :
++ \address qui dfinit l'adresse de l'expditeur place, en haut
+ gauche de la premire page si l'on utilise une mise en page
+la franaise (\usepackage{french} par exemple), ou en haut
+droite dans le cas d'une mise en page anglo-saxonne (solution
+par dfaut),
++ \signature prpare la signature de l'auteur de la lettre.
+Celle-ci sera place en bas droite de la dernire page de la
+lettre,
++ \la commande \begin{letter} prend en argument le nom du
+destinataire,
++ les commandes \opening et \closing permettent respectivement
+d'ouvrir et de fermer la lettre gnralement par des formules de
+politesse.
++ la commande \makelabels utilise dans le prambule, permet de
+gnrer une liste des adresses des destinataires pour prparer
+un mailing,
++ un certain certain nombre d'autres commandes permet de gnrer
+des champs spcifiques tels que : pices jointes, postscriptum...
+
+De manire gnrale, le positionnement des diffrents champs
+dpend de la langue utilise dans la lettre.
+
+Remarque : lorsque plusieurs environnements letter sont utiliss
+ dans un mme source, ils produiront chacun une lettre.
+ Toutes ces lettres auront la mme adresse
+ d'expditeur et la mme signature.
+
+Exemple :
+\documentclass[11pt]{letter}
+
+\name{expediteur}
+\address{adresse \\ de l'expediteur}
+\signature{signature \\ de l'expediteur}
+
+\begin{document}
+\begin{letter}{le destinataire}
+ \opening{Cher destinataire,}
+
+ texte -- texte -- texte -- texte -- texte -- texte -- texte
+ -- texte -- texte -- texte -- texte -- texte -- texte --
+ texte -- texte -- texte -- texte -- texte -- texte -- texte
+ -- texte -- texte -- texte -- texte -- texte -- texte --
+ texte -- texte -- texte -- texte -- texte -- texte -- texte
+ -- texte -- texte --
+
+ \closing{Formule de politesse}
+ \ps{PS : j'ai oublie...}
+ \cc{Monsieur Truc.}
+ \encl{pieces jointes}
+\end{letter}
+\end{document}
+%%%% fin exemple %%%%
+
+ATTENTION : si l'on ajoute le package 'french' la disposition
+ des champs utiliss change puisque les lettres
+ anglo-saxonnes ne respectent pas la mme typographie
+ que les franaises.
+
+* La classe 'lettre' de D. Megevand est un outil trs
+bien fait et adaptable toutes les situations. Elle est
+disponible par ftp sur ftp://obsftp.unige.ch/pub/tex/macros/.
+
+Exemple (D. Mgevand) :
+\documentclass[11pt]{lettre}
+\usepackage{french}
+\begin{document}
+\begin{letter}{Mme Marie-Paule \textsc{Kluth}\\
+ Alcatel Alsthom Recherche\\
+ Route de Nozay\\
+ \textbf{F-91460 Marcoussis}}
+
+\signature{Denis Mgevand}
+\def\concname{Objet :~}
+\conc{FAQ de \TeX}
+
+\vref{A VOUS}
+\nref{DE MOI}
+
+\opening{Chre Madame,}
+Je vous remercie de citer ma classe lettre dans le \S20.1 de
+votre FAQ sur \TeX. Il est exact que l'on peut faire beaucoup de
+choses avec cette classe dans le domaine de la correspondance,
+notamment des lettres et des tlcopies (fax). On peut galement
+obtenir une page d'tiquettes avec les adresses des destinataires
+des lettres contenues dans le document.
+
+Tous les paramtres de mise-en-page, ainsi que les chanes
+"Concerne", "Cc", "PS", etc. peuvent tre facilement modifis.
+
+Cependant, le pointeur vers
+html(???)://obswww.unige.ch/pub/tex/macros ne conduit nulle part.
+Le pointeur ftp est correct. Pour la doc, il existe une version
+en HTML sur http://obswww.unige.ch/Manuels/letdoc2.31.html.
+
+Au \S20.3, vous parlez de classe 'lettre', ce qui est correct,
+mais l'exemple donn montre un \verb+\documentstyle+, et les
+commandes \verb+\signature+, \verb+\vref+ et \verb+\nref+ ne sont
+pas l'endroit specifi dans la doc. Cet exemple ne compilera
+pas, ou plutt ne donnera pas ce qui est attendu. Voici comme est
+structure cette lettre :
+\begin{verbatim}
+
+\documentclass[11pt]{lettre}
+[...]
+\end{verbatim}
+
+\closing{Meilleures salutations}
+\cc{ personne !}
+\end{letter}
+\end{document}
+%%%% fin exemple %%%%
+
+* La classe 'fribrief' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fribrief/ permet galement de
+mettre en page des lettres.
+
+* La classe 'akletter' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/akletter/ est une extension de
+la classe lettre classique. Elle permet notamment de dfinir sa
+propre entte et de grer la position de l'adresse pour des
+enveloppes fentre.
+
+* Le package 'newsletr' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/plain/contrib/newsletr/ offre un ensemble de macros pour
+mettre en page des lettres.
+
+# 20.2 # Comment prparer un mailing ?
+--------------------------------------
+* Le package 'mailing', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/mailing/ permet de crer
+plusieurs documents similaires avec des valeurs dfinies dans
+des bases externes (fichiers ou autres). Il ne fonctionne
+qu'avec la classe 'letter'.
+
+* Il existe galement le package 'envlab', de B. Veytsman
+(boris@plmsc.psu.edu), disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supoorted/envlab/. Il est
+aujourd'hui aux standards amricains mais doit tre tendu
+d'autres pays.
+
+* Le package 'labels' est galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/labels/.
+
+Exemple :
+\documentclass[12pt]{book}
+\usepackage{labels}
+\LabelCols=3
+\LabelRows=11
+\LeftBorder=8mm
+\RightBorder=4mm
+\TopBorder=2mm
+\BottomBorder=4mm
+%\LabelInfotrue
+
+\begin{document}
+
+%\footnotesize\sf
+\numberoflabels=3
+
+\addresslabel[\small\sf]
+{Me, Myself \& I\\
+SomePlace\\
+SomeCompany\\
+SomeStreet\\
+SomeTown, SomeZip}
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'adrlist' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/adrlist/ permet de grer des listes
+d'adresses.
+
+* Le package 'envbig' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/envbig/ permet d'imprimer des
+adresses sur des enveloppes.
+
+* Le package 'formlett' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/formlett.sty permet de grer des mailings.
+
+# 20.3 # Comment faire des rfrences dans une lettre ?
+-------------------------------------------------------
+* Dans la classe 'lettre' de D. Megevand, il existe les
+commandes \nref, pour les rfrences de l'expditeur et \vref
+pour celles du destinataire.
+
+Exemple :
+\documentclass[11pt]{lettre}
+\usepackage{french}
+
+\begin{document}
+\begin{letter}{Mme Marie-Paule \textsc{Kluth}}
+
+\signature{MPK}
+\vref{A VOUS}
+\nref{DE MOI}
+
+ \opening{Cher ami,}
+
+ Texte....
+
+ \closing{Sincrement.}
+ \encl{Pices jointes :}
+ \cc{copie Totor}
+\end{letter}
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'french' offre galement les commandes \yourref et
+\ourref.
+
+Exemple :
+\documentclass[a4]{letter}
+\usepackage{french}
+\signature{ma signature}
+
+\begin{document}
+\yourref{mon texte}
+\ourref{mon autre texte}
+\begin{letter}{le destinataire}
+ \opening{Cher Monsieur,}
+
+ Texte...
+ \closing{Salutations}
+ \encl{pieces jointes}
+ \cc{copie a M. Totor}
+\end{letter}
+\end{document}
+%%%% fin exemple %%%%
+
+# 20.4 # Comment mettre en page un fax ?
+----------------------------------------
+Le package 'fax' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/fax/ propose un ensemble de
+commandes pour prparer un fax.
+
+# 20.5 # Comment positionner une adresse pour une enveloppe fentre ?
+-----------------------------------------------------------------------
+La classe scrlettr.cls du package koma-script permet de faire
+cela.
+
+# 20.6 # Comment suppprimer la date sur une lettre ?
+----------------------------------------------------
+Sous la classe lettre disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/,
+il existe la commande \nodate.
+
+# 20.7 # Comment inclure une figure dans une lettre ?
+-----------------------------------------------------
+Il faut utiliser le package float et dclarer le type figure :
+\usepackage{float}
+\newfloat{figure}{htbp}{lof}
+
+================================================================
+[21] SYMBOLES ET LOGOS
+================================================================
+
+# 21.1 # O trouver des symboles lectroniques ?
+------------------------------------------------
+* Le package 'epic' disponible sur CTAN permet d'accder aux
+symboles lectroniques.
+
+* Il y a galement le package 'circ' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/diagrams/circ/ qui fait a.
+AL: incompatible avec french ou pas alors ?
+
+* Le package 'circuit_macros' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/graphics/circuit_macros.tar.gz permet de dfinir des
+circuts lectriques partir d'lments de base tels que des
+amplis, des transistors, et portes logiques ...
+
+# 21.2 # Comment dessiner des circuits lectroniques ?
+------------------------------------------------------
+* Certains packages sont disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/graphics/lcircuit/, ftp://ftp.fdn.org/pub/CTAN/graphics/circuit_macros/ et
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/diagrams/circ/.
+
+* Il existe galement des librairies xfig disponibles sur
+ftp://epb1.lbl.gov/xfig/.
+
+# 21.3 # Quelles sont les polices de symboles sous LaTeX ?
+----------------------------------------------------------
+Il y en a plusieurs que l'on peut trouver sur ftp://ftp.fdn.org/pub/CTAN/fonts/.
+
+dancers Des petits bonshommes styliss (dessins d'enfants)
+ qui se trmoussent dans tous les sens...
+dingbat Symboles Zapf dingbats
+bbding Symboles Zapf dingbats
+goblin On dirait des personnages (tranges) styliss...
+hands Des grosses mains pointant vers la gauche ou la
+ droite
+iching Yi-King. Avec des symboles chinois bizarres...
+karta Symboles bizarres (voir aussi niceframes.sty)
+knot noeuds
+wasy2 Symboles
+
+# 21.4 # Comment obtenir les symboles mle et femelle ?
+-------------------------------------------------------
+* Les polices "astrosym", "cmastro", "wasy" ou "wasy2"
+dfinissent ces caractres.
+
+* Voir galement le package 'genealogy' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/genealogy/.
+
+# 21.5 # Comment obtenir le symbole degr ?
+-------------------------------------------
+* En fait le symbole "degr" ne devrait pas tre confondu avec
+un << petit o en exposant >>. C'est un caractre dfinit :
++ en codage OT1, par \char23
++ en codage T1, par \char6
+
+En LaTeX2e,
+\DeclareTextSymbol{\degre}{T1}{6}
+\DeclareTextSymbol{\degre}{OT1}{23}
+dfiniront la commande \degre, que vous travailliez en codage
+OT1 (dfaut) ou T1 slectionn par \usepackage[T1]{fontenc}
+
+* Le package 'french' dfinit de cette manire la commande
+\degre.
+
+* Le package 'babel' dfinit lui \degre et \degres.
+
+* Le package 'textcomp', de S. Rahtz, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/psfonts/ts1/, bas sur les fontes DC 1.2 ou plus rcentes,
+disponibles sur ftp://ftp.fdn.org/pub/CTAN/fonts/dc/, dfinit les commandes
+\textdegree et \textcentigrade.
+
+* Le package 'inputenc' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/base/ fournit les commandes \textdegree et
+\mathdegree.
+
+* La solution qui consiste mettre dans le prambule (LaTeX2e) :
+\newcommand{\deg}{\ensuremath{^\circ}} ou
+\newcommand{\deg}{\ensuremath{^\circ}\xspace} en utilisant le
+package 'xspace' ou encore
+\newcommand{\deg}{\(\mathsurround=0pt{}^\circ\)}
+puis utiliser \deg en mode texte ou mathmatique,
+est donc viter.
+
+# 21.6 # O trouver des symboles astronomiques ?
+------------------------------------------------
+Il existe le package 'astro' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/astro/.
+
+# 21.7 # O trouver une police de symboles phontiques ?
+--------------------------------------------------------
+* Il existe le package 'phonetic' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/phonetic/.
+
+* La fonte ipa est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/ipa/.
+
+* La fonte tipa de F. Rei est galement disponible dans
+ftp://ftp.fdn.org/pub/CTAN/fonts/tipa/.
+
+# 21.8 # O trouver des oprateurs de logique floue ?
+-----------------------------------------------------
+* Il existe le package 'logic' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/logic/.
+
+* V. Henn (henn@inrets.fr) propose ses propres dfinitions
+(LaTeX2e). Sauvegarder les commandes suivantes dans un fichier
+'fuzzy.sty'. Ce package ncessite les packages 'amsfonts' et
+'xspace'.
+
+ATTENTION : Le fichier ci-dessous est perso, ce qui signifie :
+ 1. pas d'exhaustivit
+ 2. pas de garantie de solution optimale (en terme de
+ 'puret teX')
+ 3. pas de garantie de non bug
+ 4. ces oprateurs ne correspondent pas une norme
+ pour la notation : ce sont des choix perso (qui
+ correspondent plus ou moins l'usage)
+
+%%%% debut macro %%%%
+%%%
+%%% Format de style permettant d'utiliser directement un certain
+%%% nombre d'operateurs propres la logique floue. Ces
+%%% oprateurs sont gnralement surligns d'un tilde...
+%%%
+%%% V.H., le 12 avril 1995
+%%%
+
+\RequirePackage{amsfonts}
+\RequirePackage{xspace}
+
+\message{Oprateurs flous}
+
+\newcommand{\fmin}{\mathop{\flou{\min }}}
+\newcommand{\fmax}{\mathop{\flou{\max }}}
+\newcommand{\V}{\mathop{\mathrm V\kern 0pt}}
+\newcommand{\ET}{\mathrel{\mathrm{ET}}}
+\newcommand{\OU}{\mathrel{\mathrm{OU}}}
+\newcommand{\Sim}{\mathop{\mathrm S \kern 0pt}}
+\newcommand{\hauteur}{\mathop{\mathrm h\kern 0pt}}
+\newcommand{\card}[1]{\| #1 \|}
+\newcommand{\flou}[1]{\ensuremath{\widetilde{#1}}}
+\newcommand{\R}{\ensuremath{\Bbb{R}}}
+\newcommand{\cpp}{\ensuremath{\hbox{C}^{++}}\xspace}
+
+\newcommand{\Poss}{\mathop{\Pi}}
+%\newcommand{\Nec}{\mathop{{\cal{N}}}}
+\newcommand{\Nec}{\mathop{\mathrm N\kern 0pt}}
+
+\newcommand{\poss}{\operatoname{Poss}}
+\newcommand{\nec}{\operatoname{Nc}}
+
+\newcommand{\serie}[3]{%
+% #1 -> le nom de la variable
+% #2 -> l'indice de dbut
+% #3 -> l'indice de fin
+\ensuremath{{#1}_{#2},\ldots,{#1}_{#3}}}
+
+\newcommand{\DP}{\fsc{Dubois} et \fsc{Prade}\xspace}
+%%%% fin macro %%%%
+
+# 21.9 # Comment obtenir le symbole de paragraphe ?
+---------------------------------------------------
+Il suffit de taper \S.
+
+# 21.10 # Comment obtenir le caractre 'registered' ?
+-----------------------------------------------------
+* La commande \textregistered est disponible lorsqu'on utilise
+une fonte qui le permet (TS1 ou 8r, p. ex. DC).
+
+* Le package 'textcomp', de S. Rahtz, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/psfonts/ts1/ dfinit galement ce caractre.
+
+* Voici d'autres dfinitions :
+%%%% debut macro %%%%
+\def\Registered{\raisebox{1ex}{\kern-.1em\setbox\@tempboxa\hbox{%
+\footnotesize$\bigcirc$}\hbox
+to 0pt{\hbox
+to\wd\@tempboxa{\hss\tiny\textrm{R}\hss}\hss}\box\@tempboxa\kern-.1
+em}}
+%%%% fin macro %%%%
+
+* de Ulick Stafford (ulick.stafford@nd.edu)
+
+%%%% debut macro %%%%
+\def\registered{{\ooalign {\hfil\raise .05ex\hbox{\scriptsize
+R}\hfil\crcr\mathhexbox20D}}}
+%%%% fin macro %%%%
+
+* de Maurice Dohmen (m.dohmen@cs.tudelft.nl)
+
+%%%% debut macro %%%%
+\def\REgistered{{\ooalign
+{\hfil\raise.09ex\hbox{\tiny \sf R}\hfil\crcr\mathhexbox20D}}}
+%%%% fin macro %%%%
+
+* On peut galement utiliser le package 'amssymb', de J.
+Knappen (KNAPPEN@VKPMZD.kph.Uni-Mainz.DE) qui propose la
+commande \circledR.
+
+Exemple :
+\documentclass{article}
+\usepackage{amssymb}
+\usepackage{autredefs}
+\begin{document}
+\Registered
+
+\registered
+
+\REgistered
+
+\circledR
+\end{document}
+%%%% fin exemple %%%%
+
+* De Boris A. Veytsman <BAV2@psuvm.psu.edu> :
+
+%%%% debut macro %%%%
+\newcommand{\reg}{\textsuperscript{\textcircled{\textsc r}}}
+%%%% fin macro %%%%
+
+# 21.11 # O trouver le symbole trade-mark ?
+--------------------------------------------
+* Il suffit d'utiliser le package "pifont" puis de faire
+\Pisymbol{psy}{212} ou encore \Pisymbol{psy}{228}.
+
+* Avec des fontes TS1 (tc livres avec dc ou ec, ou sinon ps) :
+\usepackage{textcomp}
+\texttrademark
+
+# 21.12 # Comment obtenir un underscore ?
+-----------------------------------------
+Il suffit de taper \_.
+
+# 21.13 # O trouver le symbole radioactif ?
+--------------------------------------------
+Il est disponible dans le package 'karta' disponible sur CTAN.
+
+# 21.14 # Comment obtenir le logo LaTeX ?
+-----------------------------------------
+Il suffit d'appeler la commande \LaTeX.
+
+# 21.15 # Comment obtenir le logo LaTeX2e ?
+-------------------------------------------
+Le nouveau logo s'obtient par \LaTeXe.
+
+# 21.16 # O trouver des chiffres entours ?
+--------------------------------------------
+* Le package 'go' disponible sur ftp://ftp.fdn.org/pub/CTAN/fonts/go/ propose
+des chiffres blancs sur fond noir.
+
+* Le package 'pifont' propose galement des chiffres entours.
+
+* A dfaut, on peut construire ses propres symboles l'aide du
+package 'overlay' ci-dessous.
+
+%%%% debut macro %%%%
+% Dans TTN Vol3 Num 2 1994, Jeremy Gibbons propose une macro
+% \overlay qui permet de crer des symboles en superposant
+% d'autres symboles. Le symbole ainsi construit peut changer de
+% taille en fonction du style (display, script...)
+%
+%%% overlay.sty to overlay two symbols, respecting styles
+
+\def\loverlay#1#2{\mathpalette\@overlay{{#1}{#2}{}{\hfil}}}
+\def\overlay#1#2{\mathpalette\@overlay{{#1}{#2}{\hfil}{\hfil}}}
+\def\roverlay#1#2{\mathpalette\@overlay{{#1}{#2}{\hfil}{}}}
+ % calls to \@overlay look like
+ % \overlay\textstyle{{x}{y}{\hfil}{\hfil}}
+\def\@overlay#1#2{\@@overlay#1#2}
+ % strip brackets from 2nd arg, to get
+ % \@@overlay\textstyle{x}{y}{\hfil}{\hfil}
+\def\@@overlay#1#2#3#4#5{{%
+ \def\overlaystyle{#1}%
+ \setbox0=\hbox{\m@th$\overlaystyle#2$}%
+ \setbox1=\hbox{\m@th$\overlaystyle#3$}%
+ \ifdim \wd0<\wd1 \setbox2=\box1 \setbox1=\box0%
+ \setbox0=\box2\fi % \box0 is now the wider box
+ \rlap{\hbox to \wd0{#4\box1\relax#5}}\box0}}
+
+%%% fin du style overlay
+%%%% fin macro %%%%
+
+Utilisation : $\overlay{symbole1}{symbole2}$
+
+Exemple (V. Henn) :
+$ \overlay{\lower.6ex\hbox{$\overlaystyle\smile$}}
+ {\raise.6ex\hbox{$\overlaystyle
+ {\roverlay{\circ}{\cdot}}{\roverlay{\circ}{\cdot}}$}}
+$
+%%%% fin exemple %%%%
+
+# 21.17 # Comment obtenir le symbole numro ?
+---------------------------------------------
+* Le package 'french' propose la commande \numero.
+
+# 21.18 # Comment obtenir les symboles pourcent et pourmille ?
+--------------------------------------------------------------
+* Le symbole pourcent s'obtient symplement par la commande \%.
+
+* Le symbole pourmille est dfinit dans le package 'textcomp' via
+la commande \textperthousand.
+
+ATTENTION : ce package ncessite la disponibilit de fontes ec.
+
+* A dfaut, on peut construire soit mme le symbole :
+%%%% debut macro %%%%
+\newcommand{\promille}{%
+ \relax\ifmmode\promillezeichen
+ \else\leavevmode\(\mathsurround=0pt\promillezeichen\)\fi}
+\newcommand{\promillezeichen}{%
+ \kern-.05em%
+ \raise.5ex\hbox{\the\scriptfont0 0}%
+ \kern-.15em/\kern-.15em%
+ \lower.25ex\hbox{\the\scriptfont0 00}}
+%%%% fin macro %%%%
+
+* Autre solution :
+%%%% debut macro %%%%
+\newcommand{\promille}{%
+\def\pourmille{\hbox{$\,^0\!/_{00}$}}
+%%%% fin macro %%%%
+
+# 21.19 # Comment obtenir un e dans l'o ?
+-----------------------------------------
+Il faut appeler la commande \oe{}. Les accolades permettent
+d'isoler la commande dans un mot.
+
+# 21.20 # Quels sont les symboles rservs dans LaTeX ?
+-------------------------------------------------------
+Il s'agit des symboles : # $ % & ~ _ ^ \ { }.
+Pour les imprimer il faut donc utiliser des commandes savoir :
+\# \$ \% \& \_ \^{} \{ \}. Pour le caractre tilde voir la
+question 29.32, et pour le backslash, il faut appeler \backslash
+en mode mathmatique.
+
+# 21.21 # Comment obtenir des lettres cursives ?
+------------------------------------------------
+Il suffit d'utiliser la fonte caligraphique.
+
+Exemple :
+$\cal{ABCDEFGHIJKLMNOPQRSTUVWXYZ}$
+%%%% fin exemple %%%%
+
+# 21.22 # Comment obtenir le logo AMS-(La)TeX ?
+-----------------------------------------------
+
+Le logo AMS-TeX s'obtiens en appelant \AmS-\TeX et le logo
+AMS-LaTeX en appelant \AmS-\LaTeX.
+
+# 21.23 # Quels sont les symboles par dfaut de LaTeX ?
+-------------------------------------------------------
+Voici une liste des symboles les plus courants :
++ \dag, \ddag,
++ \S pour paragraphe,
++ \P,
++ \copyright,
++ \pounds pour le symbole de livre,
++ \oe, \OE pour e dans l'o,
++ \ae, \AE pour e dans l'a,
++ \aa, \AA,
++ \o, \O, pour le zro barr,
++ \l, \L pour un l barr,
++ \ss pour le double s allemand,
++ ?` pour un ? l'envers,
++ !` pour un ! l'envers.
+
+# 21.24 # Quels sont les diffrents tirets ?
+--------------------------------------------
+Il existe effectivement diffrents tirets sous LaTeX :
++ la commande - pour un trait d'union
++ la commande -- pour citer un intervalle
++ la commande --- pour un tiret de ponctuation.
+
+Exemple :
+Marie-Paule
+voir page 19--32
+entre deux thmes --- par exemple.
+%%%% fin exemple %%%%
+
+# 21.25 # Comment obtenir le symbole arobasse ?
+-----------------------------------------------
+Il existe diffrentes solutions qui doivent tre slectionnes
+en fonction de l'endroit o elles sont appeles : dans le texte,
+dans un titre dans une note de bas de page, ....
+
+%%%% debut macro %%%%
++ \def\at{\string@}
++ \edef\at{\string@}
++ \def\at{\char`@}
++ \chardef\at=`\@
+%%%% fin macro %%%%
+
+# 21.26 # Comment obtenir un backslash ?
+----------------------------------------
+Il existe diffrentes techniques :
++ $\backslash$ (produit un backslash mathmatique)
++ \textbackslash
++ {\tt\char`\\}
++ \verb+\+
+on peut galement dfinir une commande :
++ \newcommand{\bslash}{\texttt{\symbol{92}}}
++ \newcommand{\backslash}{\mbox{\char`\\}}
+
+# 21.27 # Comment faire un carr plain de fin de dmonstration ?
+----------------------------------------------------------------
+* Le package 'amssymb' propose la commande \blacksquare.
+
+* Voici deux macros proposes par S. Cirilli:
+%%%% debut macro %%%%
+\def\sqw{\hbox{\rlap{\leavevmode\raise.3ex\hbox{$\sqcap$}}$%
+\sqcup$}}
+\def\sqb{\hbox{\hskip5pt\vrule width4pt height6pt depth1.5pt%
+\hskip1pt}}
+
+% Rectangle noir:
+\def\qed{\ifmmode\hbox{\hfill\sqb}\else{\ifhmode\unskip\fi%
+\nobreak\hfil
+\penalty50\hskip1em\null\nobreak\hfil\sqb
+\parfillskip=0pt\finalhyphendemerits=0\endgraf}\fi}
+% Rectangle blanc:
+\def\cqfd{\ifmmode\sqw\else{\ifhmode\unskip\fi\nobreak\hfil
+\penalty50\hskip1em\null\nobreak\hfil\sqw
+\parfillskip=0pt\finalhyphendemerits=0\endgraf}\fi}
+%%%% fin macro %%%%
+================================================================
+[22] MUSIQUE
+================================================================
+
+# 22.1 # Comment crire de la musique sous LaTeX ?
+--------------------------------------------------
+* Le package 'MuTeX', crit par A. Steinbach et A. Schofer,
+permet d'crire de la musique. Il est disponible par ftp
+anonyme sur ftp://ftp.cs.ruu.nl/pub/TEX/MuTeX.tar.Z.
+
+* Un autre package encore plus performant est 'MusiXTeX' de
+D. Taupin (taupin@frups51.bitnet ou taupin@lps.u-psud.fr), R.
+Mitchell et A. Egler. Il permet d'crire des partitions pour
+orchestres ou de la musique polyphonique. Il est disponible par
+ftp anonyme sur ftp://rsovax.ups.circe.fr/musictex/ ou sur
+ftp://hprib.lps.u-psud.fr/pub/musixtex/, ou encore sur
+ftp://ftp.fdn.org/pub/CTAN/macros/musixtex/taupin/ ou ftp://ftp.fdn.org/pub/CTAN/macros/musixtex/egler/. La
+lecture du cahier GUTenberg 21 apporte beaucoup d'informations
+ce sujet. Voir http://www.ens.fr/gut/cahiers.html ou
+http://www.gutenberg.eu.org/publications/node7.html.
+A voir galement http://www.gmd.de/Misc/Music/ le site de
+W. Icking avec une mine d'informations, en particulier des
+pointeurs vers des partitions saisies en musixtex, etc.,
+
+Il existe une FAQ disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/musictex/FAQ/.
+
+Remarque : le programme abc2mtex d'aide l'utilisation de
+ MusiXteX peut galement tre utile, voir
+ http://www.gre.ac.uk/~c.walshaw/abc/
+
+# 22.2 # Comment convertir du midifile en MusicTeX ?
+-----------------------------------------------------
+* Music TeX, de M. Beigbeder et J.J. Girardot permet la
+conversion de midifiles en Music TeX.
+
+* midi2tex permet galement de traduire des fichiers de donnes
+midi. Il est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/midi2tex/.
+
+# 22.3 # Existe-t'il une liste de discussion de musique ?
+---------------------------------------------------------
+Il existe une liste de discussion consacre l'criture de
+musique en TeX. Pour s'y inscrire, il faut envoyer un mail
+"subscribe" mutex-request@gmd.de.
+
+Les articles posts sur cette liste sont archivs dans
+http://www.gmd.de/Mail/mutex-archive/.
+
+Consulter galement : http://www.gmd.de/Misc/Music/ ou
+ftp://ftp.gmd.de/music/.
+
+# 22.4 # Comment diter un livre de chants ?
+--------------------------------------------
+Il existe le package 'songbook' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/songbook/. Voir la page
+http://www.cyberus.ca/~crath/Misc/Songbook/index.html pour
+quelques exemples.
+
+# 22.5 # Comment mettre en page un programme de concert ?
+---------------------------------------------------------
+Le package 'concprog' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/concprog/ propose un certain
+nombre de macros pour prparer un programme de concert.
+
+================================================================
+[23] CONVERSIONS DE FICHIERS
+================================================================
+
+# 23.1 # Comment gnrer un fichier .ps partir d'un .dvi ?
+------------------------------------------------------------
+* dvips, de T. Rokicki, a l'avantage de savoir grer les
+"virtual fonts". Il est disponible par ftp anonyme :
+
++ pour unix sur ftp://labrea.stanford.edu/pub/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/dvips/.
+
++ pour VMS sur ftp://ftp.fdn.org/pub/CTAN/systems/vms/Alpha/ ou
+ftp://ftp.fdn.org/pub/CTAN/systems/vms/VAX suivant l'architecture utilise.
+
++ pour MSDOS sur ftp://monu1.cc.monash.edu.au/pub/dvips54.zip ou
+sur ftp://shape.mps.ohio-state.edu/pub/msdos/dvips/dvips54.zip ou
+sur ftp://ftp.fdn.org/pub/CTAN/systems/msdos/drivers/dvips/.
+
++ pour OS2 sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/dviware/dvips/dvips558.pc.
+
+* dvitops, pour unix, msdos, vms et primos, de J. Clark, est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/dviware/. dvitops ne gre pas les
+fontes virtuelles.
+
+* dvipsk, de K. Berry, est disponible sur ftp://ftp.fdn.org/pub/CTAN/dviware/.
+
+# 23.2 # Qu'est ce que le "Literate Programming" ?
+--------------------------------------------------
+Le "Literate Programming" est une approche de la programmation
+qui met en valeur le fait qu'un programme doit pouvoir tre lu
+aussi bien par une personne que par un compilateur. Les outils
+associs (disponibles dans les archives CTAN) vont ainsi
+permettre de gnrer des documents combinant du code source et
+du texte (souvent au format TeX). Ensuite, la documentation et
+le code source seront automatiquement extraits de ce document
+unique. Pour plus d'information sur ces techniques, consulter :
+http://www.ius.cs.cmu.edu/help/Programming/literate.html. Il
+existe galement une FAQ comp.programming.literate disponible
+sur ftp://ftp.fdn.org/pub/CTAN/help/comp.programming.literate_FAQ.
+
+Remarque : l'origine, D.E. Knuth a bas TeX sur un systme
+ de "programmation littraire" nomm Web. Le code
+ source en question tait du Pascal. Aujourd'hui o
+ l'on ne trouve quasiment plus de compilateurs
+ Pascal, il a fallu crire des outils de passage
+ au C. D'o l'outil Web2C actuellement utilis. La
+ plupart des distributions Unix utilisent Web2c
+ maintenu actuellement par Karl Berry.
+
+* WEB, est le premier outil/langage de literate programming. Il
+a t cr par D.E. Knuth, qui l'a d'ailleurs utilis pour
+crire TeX et metafont. WEB est une surcouche du langage
+pascal. Il offre un indexage et des rfrences croises
+automatiques pour les identificateurs et les procdures ainsi
+qu'un pretty printing du code. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/web/tweb/.
+
+* CWEB, de D.E. Knuth et S.Levy, est une rcriture de WEB en C.
+Cette application est simple d'accs et marche trs bien. Un
+clne de ce produit est CWEBx qui est un peu plus riche (donc
+plus compliqu mais sans excs). Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/web/c_cpp/cweb/.
+
+* FunnelWEB se prsente en tant que surcouche de n'importe quel
+langage, mais pour cette raison n'offre pas de "pretty-printing"
+du code. Il en existe une variante (FunnelWEB-AC) pouvant
+gnrer de la doc HTML, en plus de la doc TeX.
+
+Il prsente l'originalit par rapport aux autres d'avoir t
+rcrit de toutes pices, et non d'tre une branche de
+dveloppement spare de CWEB.
+
+Il semble par ailleurs que FunnelWEB soit le seul pouvoir
+donner l'utilisateur le contrle total l'octet prs de son
+fichier de sortie (utile pour les Makefiles, par exemple), mais
+peut paratre assez rigide un utilisateur habitu la
+puissance de fweb.
+
+Funnel WEB, est disponible sur ftp://ftp.fdn.org/pub/CTAN/web/funnelweb.
+
+* fweb (1.53), de J. Krommes, driv de CWEB, met disposition
+une FAQ sur http://www.arsc.sunyit.edu/fwebdocs/fweb.html et une
+DOC sur http://w3.pppl.gov/~krommes/fweb_toc.html.
+Cette application est trs complte, mais un peu difficile
+d'accs. Elle permet notamment de travailler en fortran (77 ou
+90), RATFOR (77 ou 90), C ou C++. Elle intgre entre autres un
+systme de gestion de macros trs complet, " la m4" (boucles,
+arguments variables, etc.), ainsi qu'un traducteur de RATFOR en
+Fortran, pour ceux qui n'auraient pas le compilateur adquat...
+
+Elle est l'une des rares utiliser LaTeX plutt que TeX en
+standard, ce qui permet d'utiliser toute la puissance de
+celui-ci...
+
+fweb est disponible sur ftp://ftp.fdn.org/pub/CTAN/web/fweb/.
+
+* noweb et nuweb sont plus lgers, plus fiables et trs
+utiliss. Ils mettent disposition des mcanismes pour gnrer
+des documents LaTeX ou du code source. Ils sont disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/web/noweb/ et ftp://ftp.fdn.org/pub/CTAN/web/nuweb/. Pour plus de dtails,
+consulter : http://www.cs.purdue.edu/homes/nr/noweb/.
+
+* SpiderWEB, de N. Ramsey, driv de CWEB, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/web/spiderweb/. SpiderWEB permet de grer la plupart
+des langages, tant que les blancs et les tabs ne sont pas
+critiques, tout en assurant le pretty-printing. Quelques heures
+suffisent pour ajouter un nouveau langage, sans avoir tout
+recompiler. Un certain nombre de langages sont supports dans la
+distribution (C, ADA, awk, etc.)
+
+* DOC++ est disponible :
+http://www.ZIB-Berlin.DE/VisPar/doc++/doc++.html
+Il se base sur les infos dans les commentaires. Il structure
+bien les classes, mais est un peu rigide au niveau des
+possibilits. Gnre du LaTeX ou du HTML.
+
+* wflman est disponible :
+ftp://ftp.keck.hawaii.edu/pub/wlupton/wflman-2.1.1.tar.Z
+gnrateur automatique de doc au choix LaTeX, RTF, man et HTML.
+
+# 23.3 # Comment convertir du LaTeX en word ?
+---------------------------------------------
+TeXport, de K-Talk permet de convertir vos fichier TeX
+et LaTeX en documents WordPerfect ou Microsoft Word. Il traite
+les styles de fontes, les notes de bas de page, les caractres
+grecs, les mathmatiques, les tableaux simples, les accents
+europens, ainsi que les commandes \def et \renewcommand.
+
+Ce logiciel est payant (et cher). Pour plus de dtails, voir :
+http://www.ktalk.com/.
+
+# 23.4 # Comment convertir du word en LaTeX ?
+---------------------------------------------
+*
+
+* Il y a l'outil "Publishing Companion" de K-Talk (voir
+http://www.ktalk.com/).
+
+* Wd2latex, pour MS-DOS, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/wd2latex/. Cet utilitaire parat somme toute assez
+rudimentaire.
+
+* Word2x disponible sur ftp://ftp.fdn.org/pub/CTAN/tools/word2x/ permet de
+convertir du Word 6.0 en texte ou en LaTeX.
+
+* Voir galement texcnven dans
+http://www.kfa-juelich.de/isr/1/texconv/pctotex.html.
+
+# 23.5 # Comment convertir du scribe en LaTeX ?
+-----------------------------------------------
+s2latex, de V. Jacobson, fait partie de la ditribution GUTenberg
+pour Unix. Celle-ci est disponible par ftp sur
+ftp://ftp.gutenberg.eu.org/pub/gut/distribunix/.
+
+# 23.6 # Comment convertir du WordPerfect en LaTeX ?
+----------------------------------------------------
+* wp2latex, de R.C. Houtepen, est disponible sur
+ftp://wuarchive.wustl.edu/mirrors/msdos/tex/ et sur
+ftp://ftp.fdn.org/pub/CTAN/support/wp2latex/. wp2latex a t crit pour PC en Turbo
+Pascal. Il travaille partir d'un document WordPerfect5.0. On
+note quelques limitations concernant les indices, la table des
+matires, les marges et les graphiques.
+
+* wp2latex, de G. Geers (glenn@qed.physics.su.oz.au), a t
+crit en C. Il devrait tre tendu WordPerfect 5.1. La version
+la plus rcente est disponible par ftp sur
+ftp://suphys.physics.su.oz.au/wp2latex/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/support/wp2latex/glenn/.
+
+* texperf est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/texperf/.
+
+# 23.7 # Comment convertir du LaTeX en RTF ?
+--------------------------------------------
+Le format RTF (Rich Text Format) correspond un format ASCII
+contenant des informations de formatage lisibles (entre autres)
+par Word pour DOS, Word pour Windows et Word pour Macintosh.
+Pour plus d'informations sur ce format, voir :
+ftp://ftp.primate.wisc.edu/pub/RTF/index.html ou
+ftp://ftp.lps.u-psud.fr/pub/doc/gc0165.zip et
+ftp://ftp.lps.u-psud.fr/pub/doc/gc1282.exe.
+
+* TeX2RTF, est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/tex2rtf/ ou
+par ftp sur ftp://ftp.aiai.ed.ac.uk/pub/packages/tex2rtf/.
+Il tourne sous SPARC Open Look, SPARC Motif et Windows3.1.
+TeX2RTF ne gre pas les formules mathmatiques ni les tableaux
+compliqus.
+
+* LaTeX2rtf, de F. Dorner et A. Granzer, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/latex2rtf/. Il s'appuie sur LaTeX 2.09. Une version
+est galement disponible sur
+ftp://ftp.lps.u-psud.fr/pub/ltx2rtf/ltx2rtf.zip.
+
+LaTeX2rtf produit du RTF avec la simple commande (sous DOS):
+ ltx2rtf srcltx.tex
+qui produit
+ srcltx.rtf
+
+ATTENTION : 1. a ne traite pas toutes les maths mais a traduit
+ du texte LaTeX pour tre relu en Word.
+ 2. L'excutable 386 est fourni mais il y a un
+ makefile qui compile le tout pour UNIX
+ 3. Les lettres accentues au codage 850 ne sont pas
+ traduites correctement, utiliser le codage 7bits
+ (\'e, \^i, etc).
+ 4. a utilise la numrotation automatique pour les
+ sections, les chapitres, etc. Mais les nombreux bugs
+ que j'ai dcouverts dans Word 6.0 rendent la
+ prsentation un peu alatoire.
+ 5. a traite les << et les >> pour les guillemets.
+ 6. a traite (sauf erreur) les commandes de
+ changements de polices de LaTeX2e du genre
+ \bfseries, \ttfamily, \sffamily, \slshape et les
+ tailles de polices.
+
+# 23.8 # Comment convertir du RTF en (La)TeX ?
+----------------------------------------------
+* rtf2TeX (Unix), de R. Lupton (rhl@astro.princeton.edu), est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/support/rtf2tex/.
+
+* rtf2latex (Unix), de E. Wechtl, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/rtf2latex/.
+
+* rtf2latex2e (Mac, Unix, Win), d'Ujwal Sathyam, est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/support/rtf2latex2e/.
+
+* w2latex, de J. Garmendia et J.L. Maltret, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/w2latex/. w2latex est un outil de conversion
+entre deux formats descripteurs de texte, permettant de
+traduire un document rdig sous certaines versions de
+Word pour obtenir du code LaTeX .
+
+* RTFLATEX, de D. Taupin, est capable de transcrire un fichier
+RTF en LaTeX et de lui associer des fichiers de macros (.sty).
+Toutefois, il ne traite pas encore les formules ni les tables.
+RTFLATEX est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/rtflatex/ ou par
+ftp sur ftp://hprib.lps.u-psud.fr/pub/rtflatex/.
+
+# 23.9 # Comment convertir du Excel en LaTeX ?
+----------------------------------------------
+* Le package 'Tabular', de A. Gjestland, est disponible par ftp
+sur ftp://ftp.ssh.no/pub/tabular/. Il existe deux versions
+Tabular4.xla pour Excel4 et Tabular5.xla pour Excel5. Une
+documentation est galement disponible : docu-tab.ps.Z. Vous
+pouvez aussi consulter la page WEB
+http://www.ssh.no/~ag/tabular/docu-tab.html. Pour tous
+renseignements, contacter l'auteur par e-mail : ag@hsh.no.
+
+* Il existe galement l'utilitaire Excel2LaTeX disponible sur le
+WEB
+http://www.informatik.uni-trier.de/CIP/marder/xl2latex.zip.
+
+# 23.10 # Comment convertir du HTML en LaTeX ?
+----------------------------------------------
+* http://www.w3.org/hypertext/WWW/Tools/html2things.html
+propose un certain nombre d'outils de conversion partir d'un
+document html.
+
+* html2latex, de N. Torkington, est disponible
+http://www.w3.org/hypertext/WWW/Tools/html2latex.html ou sur
+ftp://ftp.fdn.org/pub/CTAN/support/html2latex/. Cet outil semble assez limit. Il
+est bas sur le parser HTML de Mosaic (NCSA).
+
+* h2l, de J. Korpela, est disponible
+http://www.hut.fi/~jkorpela/h2l/. Il est un peu plus complet que
+le prcdent mais doit encore tre complt. Une documentation
+est galement prvue.
+
+Remarque : HTML tant la base du SGML, une autre solution (non
+ teste) serait d'utiliser un traducteur SGML->LaTeX.
+ Le systme 'linuxdoc-sgml' devrait pouvoir faire a
+ si on lui donne la DTD de la version d'HTML concerne
+ et les rgles de traduction. Pour plus de dtails
+ consulter le document disponible sur
+ ftp://ftp.loria.fr/pub/linux/sunsite/utils/text/linuxdoc-sgml-*.tar.gz
+
+* techexplorer disponible sur
+http://www.ics.raleigh.ibm.com/ics/techexp.htm est un Browser
+Hypermedia qui met en forme des documents scientifiques crits en
+LaTeX pour les prsenter sous forme HTML. Il gre notamment les
+expressions mathmatiques. Il est compatible avec les
+navigateurs Netscape 3.0 et avec MicroSoft Internet Explorer.
+Pour plus de dtails voir la mailing liste
+techexplorer@LISTSERV.NODAK.EDU.
+
+* Le package 'typehtml' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/carlisle/ permet de lire des
+fichiers HTML2 et les mathmatiques dans HTML3.0.
+
+# 23.11 # Comment convertir du LaTeX en HTML ?
+----------------------------------------------
+ Remarque : IDVI est un outil qui permet de prsenter des
+ documents WWW partir de sources LaTeX. IDVI
+ est une implmentation Java d'un viewer dvi qui
+ permet d'afficher des pages LaTeX sur le WEB et non
+ plus un document HTML. Pour plus de dtails,
+ consulter : http://www.geom.umn.edu/java/idvi/
+
+* LaTeX2HTML pour Windows 95, NT et UNIX, de N. Drakos (Perl),
+est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/latex2html/. Pour plus de
+dtails, consulter : http://saftsack.fs.uni-bayreuth.de/~latex2ht/.
+
+Remarque : le package 'html' permet d'insrer dans le source
+ LaTeX des commandes traites de manire spciale par
+ le convertisseur latex2html.
+
+Il existe galement une liste de discussion latex2html
+laquelle on peut s'abonner en envoyant un mail subscribe
+latex2html [<address>] majordomo@mcs.anl.gov
+
+La nouvelle version de LaTeX2HTML est la 96.1. Une documentation
+est disponible en ligne l'irisa dans
+/usr/local/doc/LaTeX/latex2html.ps.
+
+* Il est possible galement d'utiliser hyperlatex, qui produit
+des documents HTML plus jolis pour peu que votre source LaTeX
+suive certaines conventions. Pour plus de dtails, consulter :
+http://www.cs.ruu.nl/pub/SGI/IPE/Hyperlatex-1.4pl2.tar.gz ou
+encore sur ftp://ftp.fdn.org/pub/CTAN/support/hyperlatex/.
+
+ATTENTION : cet utilitaire ncessite l'utilisation de LaTeX2e et
+ de emacs.
+
+* A voir galement : OmniMark sur http://www.omnimark.com.
+
+* Il existe galement ltx2x disponible sur ftp://ftp.fdn.org/pub/CTAN/support/.
+
+* TeX4ht est un environnement configurable qui permet de
+gnrer des documents hypertextes. Pour plus de dtails, voir :
+http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html
+
+* HeVeA est un programme gratuit destin transformer un source
+LaTeX en HTML 4.0. Ce programme est disponible l'URL
+<http://para.inria.fr/~maranget/hevea>
+C'est un interprteur du langage TeX. Donc toutes les nouvelles macros,
+tous les environnements que l'on peut dfinir sont correctement interprts,
+que l'on peut charger des fichiers de style exotiques, etc. si l'on dsire
+obtenir un rsultat particulier dans la sortie HTML. HeVeA transforme
+les formules mathmatiques en HTML 4.0 pur (sans graphique) en utilisant
+la fonte symbole, des tags de positionnements fins et des tables.
+(Contribution de ric Brunet)
+
+* ltoh est un script perl paramtrable. Il sait grer diffrents
+types de macros, les tables, la plupart des caractres spciaux,
+etc. Pour plus de dtails, voir :
+http://www.best.com/~quong/ltoh/
+
+* mn de E. Gurari est un convertisseur plain TeX ou LaTeX vers
+HTML. Il est hautement configurable. Cet outil est disponible
+sur : http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html.
+
+* Webbuilder de MicroPress, est un diteur TeX qui permet de
+gnrer du code HTML. Il gre aussi bien les commandes TeX que
+les macros utilisateur. Tous les environnements mathmatiques,
+tables, notes de bas de page, table des matires, rfrences,
+listes, etc, sont grs. La plupart des documents LaTeX peuvent
+facilement tre convertis. Webbuilder est disponible sous Win95,
+NT, ou Win 3.1 (Win32s ncessaire). Pour plus de dtails et
+quelques exemples, consulter : http://www.micropress-inc.com/.
+Pour toutes questions crire support@micropress-inc.com.
+
+* TTH est un convertisseur TeX to HTML disponible sur :
+http://hutchinson.belmont.ma.us/tth/. Il gre les mathmatiques
+(il convertit les formules mathmatiques au lieu d'en faire des
+images) et reconnat les structures de document plain TeX et
+LaTeX qu'il convertit en hyperliens. TTH est rapide et portable.
+
+* Le package 'typehtml' de D. Carlisle permet de grer des
+documents HTML directement depuis le source LaTeX. Ce package
+est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/carlisle/.
+
+# 23.12 # Comment convertir un fichier dvi en ascii ?
+-----------------------------------------------------
+* dvi2tty est disponible sur ftp://ftp.fdn.org/pub/CTAN/dviware/dvi2tty/.
+
+* dvispell de la distribution EmTeX permet galement de
+convertir un fichier dvi en fichier texte.
+
+# 23.13 # Comment convertir du WEB en LaTeX ?
+---------------------------------------------
+SchemeWEB, de J. Ramsdell, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/web/schemeweb/.
+
+# 23.14 # Comment convertir du TeX en Framemaker ?
+--------------------------------------------------
+Framemaker dispose d'un filtre permettant d'importer des
+fichiers TeX.
+
+# 23.15 # Comment enlever les balises LaTeX d'un document ?
+-----------------------------------------------------------
+detex, disponible sur ftp://ftp.fdn.org/pub/CTAN/support/detex/, permet
+d'enlever toutes les commandes et squences de contrle LaTeX
+d'un document. Il existe sous Unix, Doc et Mac.
+
+ATTENTION : detex n'enlve que les macros, et pas leurs
+ arguments, ce qui donne des rsultats pas
+ toujours trs propres avec des documents LaTeX.
+
+# 23.16 # Comment convertir du SGML en (La)TeX ?
+------------------------------------------------
+Remarque : SGML = Standard Generic Markup Language
+ SGML est une norme de balisage de documents structurs
+
+ Pour plus de dtails, consulter :
+ http://www.gutenberg.eu.org/publicationsPS/19-sgml.ps.gz
+ http://www.sil.org/sgml/sgml.html
+ http://cals.debbs.ndhq.dnd.ca/french/bulletin/issue02/index.html (en franais !)
+
+* sgmlspm, de D. Megginson, (Perl) est disponible
+http://www.connection.co.uk/bob/sgml/SGMLSpm/sgmlspl/sgmlspl.html.
+
+* stil, de J. Schrod et C. Detig, (Common Lisp) est disponible
+par ftp sur ftp://ftp.th-darmstadt.de/pub/text/sgml/stil/.
+
+Ces deux outils s'appuient sur le parser nsgmls de J. Clark qui
+traduit du SGML en ESIS.
+
+* linuxdoc-sgml s'appuie aussi sur sgmls de J.Clark.
+
+* sgml2tex, de P. Flynn, sur PC est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/sgml2tex/.
+
+# 23.17 # Comment convertir du WinWord en LaTeX ?
+-------------------------------------------------
+* WINW2LTX, de A. Cottrell, est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/winw2ltx/english/ww2/ pour WinWord2, et
+ftp://ftp.fdn.org/pub/CTAN/support/winw2ltx/english/ww6/ pour WinWord6. Il ne traite ni les
+quations, ni les graphiques.
+
+# 23.18 # Comment convertir un fichier 8 bits en fichier 7 bits ?
+-----------------------------------------------------------------
+* B. Raichle a fourni un tel convertisseur parfaitement portable
+qui se prsente sous forme d'un programme ".tex" appel
+convert.tex. Celui-ci est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/language/typingtex/.
+
+Il existe galement une version modifie par L. Siebenmann dans
+/Convert-RaichleHacked.dir/ (interface modifie, ajout de
+quelques tables de transformation dont mac2dek.tbl ou pc2dek
+pour la conversion du Macintosh ou du PC vers la syntaxe
+classique de Knuth \'e, \c{c} etc.).
+
+* L'outil Tower of Babel (avec option TeX active), permet
+galement de raliser de telles conversions. Il est disponible
+par ftp sur ftp://ftp.lip6.fr/pub/mac/info-mac/text/tower-of-babel-13.hqx.
+
+* recode de F. Pinard est un programme unix (GNU) qui convertit
+tous types de fichiers texte. De nombreux formats sont supports
+(ASCIIs, EBCDIC, CDC, LaTeX, etc).
+
+Exemple :
+recode latin1:applemac <fichier>
+pour une conversion 7 bits vers 8 bits
+%%%% fin exemple %%%%
+
+* dans emacs, le package iso-cvt.el, peut convertir
+automatiquement un fichier cod 7 bits en fichier cod 8 bits
+(et rciproquement) lors de la lecture et de l'criture. Pour
+l'utiliser, ajouter (require iso-cvt) dans .emacs. Le fichier
+sera alors en 7 bits sur le disque.
+
+* De mme, il existe le package x-symbol pour (X)emacs. Pour
+plus de dtails, voir
+http://brahms.fmi.uni-passau.de/~wedler/x-symbol.html.
+
+* Il existe galement les utilitaires kb7to8/8to7 distribus
+avec 'french'.
+
+# 23.19 # Comment convertir un fichier ChiWriter en TeX ?
+---------------------------------------------------------
+chi2tex est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/chi2tex/. Il y a
+plusieurs versions du convertisseur, selon la version de
+ChiWriter convertir. A partir des versions 2 ou 3 cela ne
+marchait que pour des fichiers trs simples (pas plus d'un
+niveau d'exposant et d'indice, etc). Il est probable que le
+convertisseur de la version 4 marche beaucoup mieux : il fait
+une analyse syntaxique des formules, alors que les versions 2 et
+3 taient purement graphiques.
+
+# 23.20 # O trouver une FAQ de convertisseurs (La)TeX/Traitement de texte ?
+----------------------------------------------------------------------------
+* La FAQ de W. Hennings est disponible sur
+http://www.kfa-juelich.de/isr/1/texconv.html ou sur
+ftp://ftp.fdn.org/pub/CTAN/help/wp-conv/.
+
+Elle est galement poste toutes les semaines dans comp.text.tex.
+AL: Ceci ne semble plus tre le cas...
+
+* Voir galement la page http://www.wotsit.demon.co.uk/text.htm
+ou la page http://wotsit.simware.com/.
+
+# 23.21 # Comment convertir une image en police metafont ?
+----------------------------------------------------------
+C'est le programme bm2font qui permet de faire cela. Il est
+disponible sur CTAN. La documentation est aussi sur le LaTeX
+Navigator (http://www.loria.fr/services/tex/).
+
+Pour plus de dtails sur metafont il existe la liste
+metafont@ens.fr. Pour s'inscrire, envoyez
+ listserv@ens.fr
+le message :
+ SUBSCRIBE metafont nom de forme libre
+
+# 23.22 # Comment convertir un fichier postscript en ascii ?
+------------------------------------------------------------
+pstotext est un outil Unix freeware qui permet d'extraire du
+texte ascii d'un fichier postscript. Il utilise Ghostscript.
+pstotext est disponible
+http://www.research.digital.com/SRC/virtualpaper/pstotext.html.
+
+Sous Windows et OS/2 pstotext est accessible via l'outil GSview
+de R Lang (version 2.0 minimum). Voir
+http://www.cs.wisc.edu/~ghost/gsview/.
+
+Pour DOS, pstotext est disponible
+http://www.cs.ruu.nl/~piet/software.html.
+
+# 23.23 # Comment convertir un fichier pdf en ascii ?
+-----------------------------------------------------
+L'outil pstotext prsent la question prcdente permet
+galement d'extraire du texte ascii d'un fichier pdf.
+
+# 23.24 # Comment convertir du LaTeX en PDF ?
+---------------------------------------------
+Remarque : il vaut nettement mieux demander LaTeX de travailler
+ avec des polices PostScript, si l'on compte
+ transformer le document en PDF par la suite. Si vous
+ utilisez des polices rsolution fixe, le texte
+ aura une apparence on ne peut plus laide sur votre
+ cran.
+
+* L'utilitaire ps2pdf de ghostscript (version 4.01 au moins)
+permet de convertir des fichiers postscript au format PDF
+d'Adobe. Ghostscript version 4.02 est disponible par ftp sur
+ftp://ftp.cs.wisc.edu/pub/ghost/aladdin/.
+Sur mac, ps2pdf livr avec cmactex, ncessite l'installation de
+psview disponible par ftp sur ftp://ftp.lip6.fr/pub/mac/local/tex/cmactex/.
+
+* il existe une version prliminaire de PDFTeX (disponible pour
+faire des tests). PDFTeX est un moteur tex qui permet de
+produire directement un fichier PDF sans passer par DVI. Il
+dispose donc en natif d'un support pour les objets graphiques et
+les liens hypertextes. PDFTeX est disponible pour WinNT/Win95
+par ftp sur ftp://ftp.ese-metz.fr/pub/TeX/private/pdftex/.
+
+T. Bouche a cr une page w3 de prsentation de pdftex avec
+trois fichiers pdf crs de cette faon :
+http://www-fourier.ujf-grenoble.fr/~bouche/PDFtex/.
+
+Il existe galement une liste de discussion ce sujet :
+pdftex@tug.cs.umb.edu.
+
+* Adobe Acrobat Distiller permet avec des fontes simples de
+gnrer des fichiers PDF partir de postscripts. Dans ce cas,
+il vaut mieux utiliser des fontes de type1 car les bitmaps de
+tex sont trs trs mal rendus par acrobat reader. Pour plus de
+dtails consulter http://www.adobe.com/.
+
+* Netpbm est un paquet d'utilitaires domaine public permettant
+des manipulations d'images, en les convertissant en un format
+PPM (Portable PixMap), trs facile manipuler par programmes.
+Il est disponible pour MSDOS dans
+ftp://ftp.lps.u-psud.fr/pub/pc/netpbm/. Une version Win32
+(Win95, NT) est galement disponible sur tout site CTAN tel que
+ftp://ftp.fdn.org/pub/CTAN/systems/win32/web2c/.
+
+# 23.25 # Comment dfinir son propre format de sortie ?
+-------------------------------------------------------
+ltx2x disponible sur ftp://ftp.fdn.org/pub/CTAN/support/ltx2x/ permet de
+remplacer des commandes LaTeX par des commandes dfinies par
+l'utilisateur.
+
+================================================================
+[24] PRVIEWERS ET VIEWERS
+================================================================
+
+Les viewers et previewers prsents ci-dessous peuvent permettre
+entre autres de visualiser des documents .dvi et .ps.
+Toutefois, ils ne sont pas attachs LaTeX.
+
+# 24.1 # O trouver un previewer ?
+----------------------------------
+* dvipage pour SunView est disponible par ftp anonyme sur :
+ftp://archive.cis.ohio-state.edu/dviware/dvipage/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/dvipage/.
+
+* xtex pour X Window System disponible par ftp anonyme sur
+ftp://ftp.cs.colorado.edu/pub/cs/misc/SeeTeX/SeeTeX/SeeTeX-*.tar.Z
+ou sur ftp://ftp.fdn.org/pub/CTAN/dviware/seetex/.
+
+* dviapollo pour stations Apollo disponible par ftp anonyme sur
+ftp://alabrea.stanford.edu/pub/dviapollo.tar.Z ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/dviapollo/.
+
+* dvidis pour VAXstation sous VWS disponible par ftp anonyme sur
+ftp://src.doc.ic.ac.uk/packages/tex/dviware/dvidis/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/dvidis/.
+
+* xdvi pour X Window System disponible par ftp anonyme sur
+ftp://ftp.x.org/contrib/xdvi.tar.Z ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/xdvi/.
+
+* dviwin sous Windows est disponible sur CTAN.
+
+* xdvik de K. Berry est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/xdvik/.
+
+* dvitovdu pour Tektronix 4010 et autres terminaux sous Unix
+est disponible sur ftp://ftp.fdn.org/pub/CTAN/dviware/dvitovdu/.
+
+* texsgi pour SGI sous Irix disponible par ftp anonyme sur
+ftp://ftp.brl.mil/info-iris/tex/ ou sur
+ftp://ftp.fdn.org/pub/CTAN/dviware/texsgi/.
+
+# 24.2 # O trouver un viewer ?
+-------------------------------
+* Ghostscript, Ghostview et GSview pour PC, Mac et station de
+travail sont disponibles sur
+http://www.cs.wisc.edu/~ghost/index.html.
+
+* viewps de T. Kiffe est inclu dans la distribution CMacTeX
+disponible sur CTAN.
+
+* TrueTeX est un viewer pour PC sous windows.
+
+* gv est une interface base sur Ghostview et amliore. Les
+actions disponibles sont nombreuses et il est possible de
+lire un document sur cran. On dispose aussi de l'anti-aliasing
+et de zooms impressionnants sur les parties de la page que l'on
+veut. gv peut mme afficher des fichiers PDF si on dispose de
+la version de GhostScript adquate.
+
+Pour plus de dtails consulter :
+http://wwwthep.physik.uni-mainz.de/~plass/gv/ ou un site FTP :
+ftp://thep.physik.uni-mainz.de/pub/gv/.
+
+gv tourne sur les versions d'Unix les plus courantes, il faut
+nanmoins disposer du widget Xaw3d.
+
+# 24.3 # Comment visualiser des fichiers non postscript sous xdvi ?
+-------------------------------------------------------------------
+D. Barbier propose le script suivant pour inclure des fichier MPS
+gnrs pas Metapost.
+
+La dmarche retenue est de pomper dans le .ps toutes les
+dfinitions qui manquent ce pauvre xdvi. Par exemple, pour voir
+les dessins dans le fichier essai.tex, je fais :
+ makepro essai.tex
+Ce qui gnre essai.ps (s'il est vieux) et produit un fichier
+essai.pro. Il ne reste plus qu' mettre \special{header=essai.pro}
+avant le \begin{document} et le tour est jou. Quand on modifie
+le source (on rajoute des dessins), il suffit de relancer
+makepro, et de recompiler le document.
+
+Quelques remarques :
++ il faut une version de xdvi >= 20
++ on peut sans encombres utiliser plusieurs fois cette commande
+sur le mme fichier ;
++ pour faire le .ps final, il faut enlever
+\special{header=essai.pro} et recompiler ;
++ s'il y a des problmes d'chelle, essayer de modifier des paramtres
+dans la dfinition de fshow et fstore.
++ je travaille en 600dpi ;
+
+Comme je ne connais pas grand chose en PostScript, toutes les
+remarques seront les bienvenues. Par exemple, les paramtres
+dans fshow et fstore sont mis au pif. Quelles sont les bonnes
+valeurs ? Comment faire pour que Psfrag passe la moulinette ?
+Et bien d'autres choses.
+
+%%%% debut macro %%%%
+ #!/bin/sh
+ # D. Barbier 31/10/97 barbier@cmapx.polytechnique.fr
+ # Commande : makepro nom_de_fichier
+ # Usage : voir ci-dessous (ou taper makepro -h)
+
+ usage="Usage: `basename $0` nom[.tex]\n\
+ Cree un preambule \"nom\".pro qui permet l affichage
+ des fichiers non postscript (inclus par \"nom\") avec
+ xdvi (version 20 et plus).\n\
+ Les applications sont notamment l inclusion de fichiers
+ generes par Metapost."
+
+ case "$#:$1" in
+ 1:-h*|1:--h*) echo "$usage"; exit 0;;
+ 1:*) ;;
+ *) echo "$usage"; exit 1;;
+ esac
+
+ if test -r "$1" ; then
+ filetex=$1
+ file=`echo "$filetex" | sed -e 's/\.[^.]*$//'`
+ else
+ file=$1
+ filetex=$file.tex
+ if test ! -r "$filetex" ; then
+ echo "Erreur: le fichier $file n existe pas"
+ exit 1
+ fi
+ fi
+ filedvi=$file.dvi
+ fileps=$file.ps
+ filepro=$file.pro
+ rm -f $filepro
+
+ # On teste si la commande \special{header=...}
+ # est dans le fichier
+ # Autant ne faire qu'une compilation avant de
+ # voir le resultat
+ ligne="\\\\special{header=$filepro}"
+ if test -z "`grep $ligne $filetex`" ; then
+ echo "Rajouter la comande $ligne avant \\\\begin{document}"
+ exit 1
+ fi
+
+ echo "%!" > $filepro
+
+ # On ne compile le .tex que si necessaire. Il y a
+ # plusieurs possibilites pour voir la date de modification
+ # des fichiers :
+ # 1) utiliser newer fourni avec certaines distributions de TeX
+ # (je n'ai pas reussi a le faire marcher).
+ # 2) test (si l'option -nt est supportee)
+ # 3) creer un makefile.
+ # J'ai choisi cette derniere solution
+
+ echo "$filedvi: $filetex\n\tlatex $filetex\n\
+ $fileps: $filedvi\n\tdvips -o $fileps $filedvi\n" > .tmp$$
+
+ make -f .tmp$$ $fileps
+
+ rm -f .tmp$$
+
+ awk '
+ # Liste des preambules qu on veut utiliser
+ BEGIN {header["tex.pro"]=1;header["texps.pro"]=1}
+ /%%BeginProcSet:/ { if ( header[$2] == 1 ) {getline
+ while ( $1 != "%%EndProcSet" ) {print;getline}}}
+ /%%EndProlog/ {exit 0}
+ ' $fileps |
+ # On supprime la creation des dictionnaires.
+ sed -e 's%/TeXDict [[:digit:]]* dict \([[:alpha:]]*\)%%' \
+ -e 's%/SDict [[:digit:]]* dict \([[:alpha:]]*\)%%' \
+ >> $filepro
+
+ # Ce sont les commandes qui font l affichage.
+ # En remplacant les commandes de finclude.pro par celles-ci,
+ # ca a l air de marcher
+
+ cat << EOF >> $filepro
+ /fstore{TeXDict begin /VResolution 120 def /Resolution 120
+ def end
+ dup dict exch{dup 4 2 roll put}repeat def}bind def
+ /fshow{gsave 72 TeXDict /Resolution get div -72 TeXDict
+ /VResolution get div scale 1
+ 5 div dup scale get cvx exec show grestore}bind def
+ EOF
+
+ # Et la, ce sont les commandes de fontes
+ awk '
+ /TeXDict begin ([[:digit:]]* ){5}/ {i++}
+ /TeXDict begin ([[:digit:]]* ){5}/,/end/ {if (i==1) print}
+ /%%EndProlog/ {exit 0}
+ ' $fileps >> $filepro
+
+ echo "Fichier $filepro genere"
+
+ exit 0
+%%%% fin macro %%%%
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/LaTeX-FAQ-francaise/part6 b/help/LaTeX-FAQ-francaise/part6
new file mode 100644
index 0000000000..99454a01f6
--- /dev/null
+++ b/help/LaTeX-FAQ-francaise/part6
@@ -0,0 +1,2261 @@
+Path: tempo.univ-lyon1.fr!univ-lyon1.fr!howland.erols.net!newsfeed.skycache.com!Cidera!netnews.com!opentransit.net!proxad.net!teaser.fr!fdn.fr!edgard.fdn.fr!not-for-mail
+Date: 08 Jun 2001 13:31:18 +0200
+Newsgroups: fr.comp.text.tex,fr.usenet.reponses
+Subject: [FAQ] fr.comp.text.tex - parties 25 a 30
+Message-ID: <faq-fctt-p620010608133118@edgard.fdn.fr>
+X-Posted-By: poste.sh version 1.1
+From: bayartb@edgard.fdn.fr (Nono le robot)
+Supersedes: <faq-fctt-p620010501143417@edgard.fdn.fr>
+Expires: 08 Jul 2001 13:31:17 +0200
+Followup-To: poster
+Organization: French Data Network
+Approved: bayartb@edgard.fdn.fr
+Lines: 2251
+Xref: tempo.univ-lyon1.fr fr.comp.text.tex:23527 fr.usenet.reponses:20393
+
+Archive-name: fr/faq-latex-francaise/part6
+
+Author: Marie-Paule Kluth
+Posting-Frequency: mensuel (monthly)
+Version: 2.27
+
+================================================================
+ Cette FAQ, rdige initialement par MP Kluth est maintenant
+ tenue jour autant que possible par B. Bayart et
+ plusieurs volontaires (voir question [30]).
+================================================================
+
+================================================================
+[25] LOGICIELS DE DESSINS
+================================================================
+
+# 25.1 # O trouver un logiciel de dessin ?
+-------------------------------------------
+* Xfig est un logiciel de dessin disponible sur station de
+travail Unix sous X Window System. Il permet via des menus de
+manipuler des objets de faon interactive dans une fentre X
+Window. Il ncessite une souris trois boutons. Il est
+disponible par ftp anonyme sur ftp://epb1.lbl.gov/xfig
+ou sur ftp://ftp.fdn.org/pub/CTAN/graphics/xfig/.
+Son gros avantage est de permettre l'utilisation de
+commandes LaTeX (formules mathmatiques). Il est capable
+d'exporter une figure directement en format TeX ou de
+gnrer de l'encapsulated postscript (si l'on veut des
+zones grises ou des choses de ce type, il faut passer par
+un fichier postscript).
+
+* PSfrag permet galement de combiner du dessin et des textes
+LaTeX. Il ncessite LaTeX2e et le package 'graphics'. Il est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/psfrag/.
+
+* TeXcad, permet de crer des fichiers de dessin. Le principe
+est intressant puisque cet outil permet de dessiner l'aide de
+la souris et de menus et lui le transforme en commandes LaTeX.
+Il permet l'utilisation de la commande \special (cf. paragraphe
+29.8). TeXcad est disponible sur PC (il fait partie de la
+distribution emTeX) et sous Unix et Linux (on peut le trouver
+dans ftp://ftp.fdn.org/pub/CTAN/systems/unix/linux/).
+
+* Xy-pic permet de raliser des diagrammes commutatifs, des
+automates, et plein d'autres choses (cf. paragraphe 8.6).
+
+* xgraphic offre une trs bonne qualit de dessin. Il est
+disponible
+http://blanche.polytechnique.fr/XGRAPHICS/xgraphics.html.
+
+* tgif permet galement de dessiner des figures. Il est
+disponible http://bourbon.cs.columbia.edu:8001/tgif/.
+Il peut faire appel diffrentes librairies (cf.
+http://bourbon.cs.columbia.edu:8001/tgif/current.html) dont une
+LaTeX qui permet entre autres de grer des quations
+mathmatiques.
+
+* LaTeXcad sous Windows3.x et Windows '95 permet de convertir
+des figures en commandes LaTeX. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/msdos/latexcad/.
+
+* MetaPost que l'on peut trouver dans la distribution CMacTeX
+peut produire des figures PostScript. Les commandes MetaPost
+permettent entre autres d'obtenir directement des cercles, des
+segments et des courbes de Bezier ; en outre, on peut nommer des
+points en prcisant leurs coordonnes ou en indiquant les
+chemins l'intersection desquels ils se trouvent. MetaPost
+offre d'autres possibilits, bien dcrites dans le manuel qui
+l'accompagne.
+
+Pour plus de dtails,
+consulter http://www.loria.fr/~roegel/metapost.html.
+
+* Pagedraw sous Windows 3.1/95/NT permet de gnrer des fichiers
+postscript. Il est disponible sur ftp://ftp.fdn.org/pub/CTAN/graphics/pagedraw/.
+
+Remarque : Il y a un excellent diteur vectoriel GRATUIT sous
+ windows, nomm MayuraDraw (anciennement PageDraw)
+ et que l'on peut trouver sous
+ http://www.wix.com/PageDraw/
+
+ Avec Ps2ai, cet diteur permet d'importer des
+ fichiers ps (presque) quelconques, de les manipuler
+ et de les exporter au format pdf, eps, wmf, ai, ps,
+ bmp et tif.
+
+* Qfig est un logiciel de dessin sous DOS. Il gnre des
+fichiers PicTeX et EPIC. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/qfig/.
+
+* PovRay est un outil de ray-tracing. Il permet de manipuler
+des formes gomtriques, des plans, des textures des sources de
+lumires, etc. Consultez http://www.povray.org/.
+
+* Gimp est une application UNIX qui s'appuie sur X Window
+system. GIMP permet de manipuler des images pour faire des
+retouches sur des photos, des compositions d'images, etc. Pour
+plus de dtails, consultez :
+http://www.gimp.org/.
+A noter, gimp tourne aussi sous Windows.
+
+* Sous Windows 3.1/95/NT il existe galement Paint Shop Pro qui
+est shareware. Pour plus d'informations, consultez
+http://www.jasc.com/.
+
+* Le package 'mfpic' de T. E. Leathrum et G. Tobin permet
+galement de faire des dessins, directement dans le source. Son
+intrt est de rendre le document parfaitement portable sans
+aucun soucis de compatibilit de format, ni d'envoi de fichiers
+multiples.
+
+Le source d'un dessin mfpic doit tre compil par TeX puis
+MetaFont et TeX nouveau. Ce package est trs bien adapt pour
+des dessins mathmatiques et gomtriques. Les programmes
+offrent une complexit remarquable (for .. upto .., if .. then
+.. else .., calculs numriques, etc).
+
+Le principe de base du fonctionnement de mfpic est de crer une
+police de caractre, dont chaque caractre sera un dessin (d'o
+la ncessit de la compilation par Metafont, comme pour toute
+nouvelle police).
+
+Remarque (R. Roussillon) : Ce package mriterait d'tre plus
+ connu que ce qu'il est actuellement.
+
+Exemple :
+\polyline{(0,0),(1,2),(3,-1)}
+\arc[t]{(1,0),(1,1),(0.5,1)}
+%%%% fin exemple %%%%
+
+# 25.2 # Comment inclure des formules Latex dans Xfig ?
+-------------------------------------------------------
+* Il suffit de mettre le flag special au texte, de taper son
+texte LaTeX en incluant des commandes, d'exporter son fichier
+(toto.fig par exemple) en deux parties : Combined PS/LaTeX (PS
+part) Combined PS/LaTeX (LaTeX part) et de faire
+\input{toto.pstex_t}, en ayant bien sr charg au pralable
+le package 'epsfig' par la commande \usepackage{epsfig} place
+dans le prambule.
+
+* On peut utiliser galement tgif qui permet d'insrer du LaTeX
+dans les figures. Son fonctionnement est diffrent : le source
+est compil dans tgif mme, et le rsultat dvi est converti en
+Postscript et apparat dans la figure. Le positionnement dans la
+figure de l'lment compil est donc plus ais, mais il est
+assez contraignant de lancer LaTeX pour compiler chaque lment.
+
+# 25.3 # Comment grer diffrents formats de figures ?
+------------------------------------------------------
+* Sous Unix, Win95, Mac, VMS, l'outil ImageMagick, de J. Cristy,
+permet de convertir de nombreux formats d'image vers un autre.
+Il permet l'dition et la manipulation d'images. Pour plus de
+renseignements, consulter
+http://www.wizards.dupont.com/cristy/ImageMagick.html.
+ImageMagick est disponible par ftp sur
+ftp://ftp.wizards.dupont.com/pub/ImageMagick/.
+
+ImageMagick est galement disponible pour VMS par ftp sur
+ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms/ ou sur
+ftp://ftp.x.org/contrib/applications/vms/.
+
+* Transfig permet entre autres de convertir un fichier au format
+fig en format postscript.
+Il est disponible sur ftp://ftp.fdn.org/pub/CTAN/graphics/transfig/ ou
+sur ftp://ftp.x.org/contrib/applications/drawing_tools/transfig.
+
+* GraphicConverter sur mac (en anglais, franais ou allemand)
+est capable de lire pratiquement tous types de fichiers
+graphiques de toutes origines et de le sauvegarder dans un autre
+format dont EPSF. Le programme est shareware et est disponible
+sur info-mac.
+
+* tiff2ps (sous Unix), de S. Leffler, permet de convertir des
+images au format tiff en format ps. Disponible sur CTAN:
+ftp://ftp.fdn.org/pub/CTAN/support/pstools/tiff2ps.
+
+* GWSWIN11 ou Graphic Workshop pour Windows est disponible par
+ftp sur ftp://hprib.lps.u-psud.fr/pub/pc/utils/. Cet outil
+(shareware $40) permet de convertir du PCX, TIFF, JPEG, GIF,
+BMP, etc. Il sait convertir des fichiers niveaux de gris en
+fichier trams ("dithered" en anglais) utilisable pour
+l'impression sur des imprimantes noir-et-blanc comme nos
+imprimantes laser. Pour le tramage, il propose 7 algorithmes et
+la doc de 60 pages donne des conseils. Son tramage parat
+meilleur que celui d'ImageIn ou des scanners usuels.
+
+* Paint Shop Pro, outil pour PC, permet d'exporter des fichiers
+en postscript qui pourront tre appels directement sous LaTeX.
+Il est disponible http://www.jasc.com/index.html en shareware
+ou par ftp sur ftp://ftp.lip6.fr/pc/win95/desktop/psp*.zip ou
+dans ftp://ftp.lip6.fr/pc/simtelnet/win3/Graphics/psp*.zip.
+
+* L'utilitaire gif2eps disponible par ftp sur
+ftp://ftp.scn.rain.com/pub/graphics/.
+
+* Voir galement les pages http://wotsit.simware.com/ ou
+http://www.wotsit.demon.co.uk/text.htm pour des informations sur
+des convertisseurs.
+
+================================================================
+[26] CORRECTEUR
+================================================================
+
+# 26.1 # O trouver un correcteur orthographique ?
+--------------------------------------------------
+* ispell est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/ispell/ ou sur
+ftp://ftp.lip6.fr/pub/gnu/. Il peut tre associ au dictionnaire
+franais de M. Boyer disponible par ftp sur
+ftp://ftp.inria.fr/gnu/. ispell peut tre associ emacs (xemacs), NeXT.
+Pour plus de renseignements, consulter
+http://ficus-www.cs.ucla.edu/ficus-members/geoff/ispell.html.
+
+* Pour MS-DOS :
++ il existe amspell disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/amspell/ ou jspell dans ftp://ftp.fdn.org/pub/CTAN/support/jspell/.
++ Micropell (commercial) peut tre appel depuis PCTeX pour
+windows.
+
+* Pour Macintosh, Excalibur est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/systems/mac/support/excalibur/ avec plusieurs dictionnaires.
+Pour plus de dtails, voir :
+http://www.eg.bucknell.edu/~excalibr/excalibur.html.
+
+* Pour VMS, il existe vmspell disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/vmspell/.
+
+* On note galement le mode ispell-minor-mode de emacs, qui est
+capable de vrifier l'orthographe en ligne sans prendre en
+compte les commandes LaTeX.
+
+* La distribution Full VTeX [DOS/Win] inclut un correcteur
+orthographique (amricain, anglais, franais, allemand,
+hollandais et italien). Pour plus de dtails, consulter :
+http://www.micropress-inc.com/.
+
+* L'diteur textpad sous Win3.1x et Win95 est capable de
+supporter des textes LaTeX et comprend de nombreux
+dictionnaires. Pour plus de dtails, consulter :
+http://www.textpad.com/.
+
+* Le dictionnaire de R. Cougnenc peut s'utiliser en mode shell
+sous DOS comme sous Linux. Il contient 95 000 mots et 39 000
+codes postaux, et permet de vrifier trs rapidement une
+orthographe. Ce dictionnaire est disponible sur la page web de
+D. Trystram :
+http://www.starnet.fr/Homepages/dtrystram/index.html.
+
+# 26.2 # O trouver un vrificateur de syntaxe LaTeX ?
+------------------------------------------------------
+* TeX est un outil puissant disponible par ftp sur
+http://www.tex.ac.uk/.
+
+* lacheck, disponible avec la distribution AUC-TeX (mode (La)TeX
+pour emacs) est capable de vrifier la syntaxe LaTeX et de
+dtecter les erreurs les plus frquentes.
+
+* Le package 'syntonly' permet galement de vrifier la syntaxe
+LaTeX.
+
+Utilisation :
+ \documentclass[syntonly]{...}
+
+* ChkTeX, de J. T. Berger Thielemann (jensthi@ifi.uio.no), dont
+la version v1.5 est disponible sur ftp://ftp.fdn.org/pub/CTAN/support/chktex/.
+Il est capable de dtecter des erreurs typographiques dans
+LaTeX. Cet outil permet de s'affranchir de certaines
+constructions LaTeX non intuitives. Les binaires pour UNIX,
+Amiga, MSDOS et OS/2 sont disponibles.
+
+Quelques exemples de services :
++ pas d'espace ou assimil aprs/avant une parenthse
++ indique les espaces multiples qui ne sont pas quivalents un
+seul
++ gre la ponctuation en mode mathmatique
++ indique les espaces avant une note de bas de page
++ gre les fichiers inclus
++ dtecte les blancs avant une rfrence au lieu de ~
++ vrifie les couples de parenthses
++ gre l'espace aprs un passage en italique
++ ...
+
+Cet outil est configurable. Il supporte LaTeX209 et LaTeX2e.
+
+* Le package 'refcheck' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/refcheck/ permet de vrifier les
+rfrences d'un document.
+
+================================================================
+[27] ASSOCIATIONS
+================================================================
+
+# 27.1 # Qu'est ce que l'association GUTenberg ?
+------------------------------------------------
+L'association GUTenberg (loi 1901) a pour objectifs de
+regrouper les utilisateurs francophones de TeX, de favoriser
+les changes techniques permettant d'augmenter les possibilits
+d'impression et de publications scientifiques et d'offrir ses
+adhrents un certain nombre de services dont des distributions
+TeX et LaTeX francises. Le serveur d'archives de GUTenberg est
+herberg sur le serveur ftp anonyme :
+ftp://ftp.gutenberg.eu.org/pub/gut/ ou sur le WEB
+http://www.gutenberg.eu.org.
+
+GUTenberg publie la Lettre GUTenberg ainsi que les cahiers
+GUTenberg.
+
+Remarque : Le cahier 23 de GUTenberg est galement une FAQ
+ LaTeX.
+
+ATTENTION : la FAQ que vous tes en train de lire est
+ indpendante de l'association GUTenberg.
+
+# 27.2 # Qu'est ce que l'association TUG ?
+------------------------------------------
+TUG (TeX Users Group) est une organisation internationale dont
+un tiers des membres est europen. TUGboat est la lettre de ce
+groupe. Pour plus de renseignements, contacter tug@tug.org par
+mail ou consulter le site WEB http://www.tug.org/.
+
+# 27.3 # Qu'est ce que l'association AsTeX ?
+--------------------------------------------
+L'association AsTeX a comme objectif principal d'essayer de
+faire du travail utile au plus grand nombre, dans le domaine des
+logiciels scientifiques, et d'essayer de faire ce travail aussi
+bien que les diteurs privs, mais dans un esprit de service
+public.
+
+Cela passe par l'criture d'utilitaires d'installation et de
+configuration automatiss (pour que le dbutant en TeX/LaTeX
+n'ait pas lire 1000 pages de docs disparates, en anglais de
+surcrot, avant de pouvoir imprimer "Bonjour"), par l'criture
+de docs raisonnablement bien rdiges et agrables consulter,
+par des distributions sur disquettes bien prsentes. Cela passe
+galement par la traduction de docs originales dans un franais
+correct, etc.
+
+================================================================
+[28] FONTES
+================================================================
+
+# 28.1 # Que signifient les sigles T1, mf, fd etc. ?
+----------------------------------------------------
+Contribution de P. Pichaureau (ppichaur@grannus.u-strasbg.fr) :
+
+Voici une mise au point rapide, histoire que vous compreniez
+de quoi a parle.
+
+En 1990, lors d'une runion d'utilisateurs de TeX, Cork, il a
+t dcid de dvelopper une table d'encodage particulire pour
+les fontes de TeX. Cette table contient des signes diacritiques
+et un certains nombre de symboles qui permettent de composer des
+textes dans un bon nombre de langues europennes.
+
+Ce codage s'appelle T1 (parfois Cork encoding), et l'ancien
+codage de TeX s'appelle OT1 (Old T1). Les autres codages (U,
+etc.) concernent des polices particulires et/ou des polices qui
+ne respectent ni T1 ni OT1.
+
+Les fontes standard de TeX qui respectent ce codage
+s'appellent fontes EC (pour european coding, il me semble). Les
+fontes DC taient une pr-version des fontes EC. La phase de
+mise au point des fontes EC ayant dur un certain nombre
+d'annes, on s'y perd un peu.
+
+Les fontes TC (text companion) contiennent un certain nombre de
+caractres textuels utiliss en mode mathmatique. l'origine,
+Knuth prenait ces caractres dans les polices textes normales,
+mais cela pose des problmes si vous essayez d'utiliser d'autres
+polices de texte. C'est pour cela qu'on prfre maintenant les
+mettre part.
+
+a c'est pour les problmes de codage.
+
+Pour les pk, mf, etc. je refuse de rentrer dans les dtails,
+mais voici un rapide aperu de la question :
+
+fichiers mf -> sources metafont. partir de l, metafont gnre
+les fichiers tfm et pk.
+
+fichiers tfm -> mtriques des fontes. Contient la taille des
+caractres, les corrections d'espacement ventuelles, etc. TeX a
+imperativement besoin de ces fichiers pour compiler un
+document.
+
+fichiers pk -> polices au format bitmap. C'est ce qui est
+utilis pour la prvisualisation et l'impression (mme en
+PostScript, et ne me demandez pas pourquoi !).
+
+fichiers vf -> vf pour Virtual Font. Les fontes virtuelles ont
+t mises au point par Knuth pour vous permettre
+d'utiliser des fontes de provenance diverses. Les fichiers vf
+sont utiles lorsque vous essayez d'utiliser des fontes
+PostScript.
+
+fichiers fd -> description des fontes. a, c'est en rapport avec
+NFSS. Bon, l, je suis oblig de m'tendre.
+
+NFSS, c'est la manire dont LaTeX2e slectionne une fonte. LaTeX
+ne le faisait pas assez proprement, alors on a fait le mnage.
+Un fichier .fd dit LaTeX2e quels sont les fichiers .mf
+utiliser pour telle police, dans telle taille, dans telle
+famille, avec telle variation. C'est avec ce fichier que vous
+dites LaTeX2e de prendre la version sans serif dans tel
+fichier, la taille 9pt dans tel autre, et le gras dans ce
+troisime fichier.
+
+En tout tat de cause, tfm et fd sont indispensables la bonne
+marche de LaTeX2e. Les mf sont indispensables la creation des
+tfm et despk, et les pk sont indispensables la visualisation
+et l'impression.
+
+# 28.2 # Quels sont les attributs d'une fonte ?
+-----------------------------------------------
+Une fonte possde :
++ une famille (family) qui par dfaut vaut cmr
+ Autre valeurs : cmtt, cmss, cmdh, cmfib.
+
+ La famille correspond l'allure gnrale de la
+ fonte. cmtt pour les fontes machines crire
+ cmss pour les sans serifs, cmdh et cmfib pour
+ respectivement les polices dunhill et fibonacci.
+
++ un codage (encoding) qui par dfaut vaut OT1 (cf. question
+28.1)
+ Autres valeurs : T1, OML, OMS, ...
+
++ une srie (series) de valeur m par dfaut
+ Les autres valeurs sont obtenues par une combinaison
+ de deux attributs :
+ - un poids (qui correspond la graisse de la fonte) :
+ ul (ultral), el (extral), l (light), sl (semil), sb
+ (semib), b (bold), eb (extrab), ub (ultrab),
+ - une largeur : uc (ultrac), ec (extrac), c (condensed),
+ sc (semic), m (medium), sx (semix), x (expanded), ex
+ (extrax), ux (ultrax).
+
++ une forme (shape) dont la valeur par dfaut est n
+ Autres valeurs : n, it, sl, sc, ui, ol
+
+ La forme correspond aux diffrents variations
+ de la fonte : n pour normal, it pour italique,
+ sl pour pench (slanted), sc pour les petites
+ capitales (small capital).
+
++ une taille (size) qui vaut par dfaut 10pt. Lorsque deux
+valeurs sont prcises, la premire correspond effectivement
+la taille de la fonte et la seconde gnralement suprieure
+correspond aa la taille de l'interligne.
+
+# 28.3 # Comment utiliser une fonte ?
+-------------------------------------
+* Pour dclarer une fonte par dfaut dans un document, il
+existe les commandes \familydefault, \encodingdefault,
+\seriesdefault et \shapedefault.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\renewcommand{\familydefault}{cmtt}
+
+\begin{document}
+\begin{verbatim}
+\renewcommand{\familydefault}{cmtt}
+\end{verbatim}
+
+dans le prambule d'un document permet de slectionner la fonte
+computer moderne de type machine crire pour tout le corps du
+document.
+\end{document}
+%%%% fin exemple %%%%
+
+* En LaTeX2e, un certain nombre de packages permettent de faire
+appel une fonte particulire.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\usepackage{times}
+\begin{document}
+\begin{verbatim}
+\usepackage{times}
+\end{verbatim}
+
+dans le prambule d'un document permet de slectionner la fonte
+ times pour tout le corps du document.
+\end{document}
+%%%% fin exemple %%%%
+
+* A un niveau plus bas, dans la cration d'un style par
+exemple, la slection d'une fonte peut se faire de la manire
+suivante :
+\fontfamily{ccr}\fontencoding{T1}\fontseries{c}\fontshape{sl}%
+\fontsize{9}{11pt}\selectfont
+
+ou encore :
+
+\fontsize{14}{16pt}\usefont{OT1}{cmdh}{bc}{it}
+
+* Pour dfinir une commande de changement de fonte, on peut
+utiliser \DeclareFixedFont.
+
+Exemple :
+\DeclareFixedFont{\petitefonte}{\encodingdefault}%
+{\familydefault}{\seriesdefault}{\shapedefault}{6pt}
+\newcommand{\petit}{\petitefonte}
+%%%% fin exemple %%%%
+
+# 28.4 # Comment changer la forme d'une fonte ?
+-----------------------------------------------
+* En LaTeX2e, pour un changement ponctuel de fonte, un certain
+nombre de commandes sont disponibles par dfaut :
++ \textrm pour romain
++ \textsf pour sans srif
++ \texttt pour du type machine crire
++ \textmd pour une srie moyenne
++ \textbf pour du gras
++ \textup pour des lettres droites
++ \textit pour de l'italique
++ \textsl pour des lettres penches
++ \textsc pour des petites capitales
++ \textnormal pour la fonte par dfaut du document.
+
+Exemple :
+Un \textbf{bel} arbre.
+Un \textbf{\textit{trs bel}} arbre.
+%%%% fin exemple %%%%
+
+* Pour changer la fonte de tout un paragraphe, on utilisera
+plutt les commandes \rmfamily, \sffamily, \ttfamily, \bfseries,
+\mdseries, \itshape, \slshape, \upshape et \scshape.
+
+Remarque : si on utilise ces commandes sur un seul mot ou sur
+ un groupe de mot dans un paragraphe, alors l'espace
+ suivant une telle dclaration ne sera pas gr (il
+ vaut mieux dans ce cas utiliser les commandes
+ \textxx).
+
+Exemple :
+{\scshape BlaBla }
+ou
+\begin{itshape}
+ blabla
+\end{itshape}
+%%%% fin exemple %%%%
+
+# 28.5 # Comment changer la taille d'une fonte ?
+------------------------------------------------
+* Il existe les commandes \tiny, \scriptsize, \footnotesize,
+\small, \normalsize, \large, \Large, \LARGE, \huge, \Huge,
+classes dans l'ordre croissant de taille. Ces commandes sont
+prdfinies en fonction de la classe de votre document.
+
+Remarque : Le changement de taille de la fonte entrane
+automatiquement un changement de l'interligne.
+
+* Plus globalement, vous pouvez utiliser la commande \fontsize
+(cf. 28.3).
+
+# 28.6 # Comment modifier la fonte des numros de paragraphe ?
+--------------------------------------------------------------
+Pour modifier la fonte des numros de paragraphe, il faut
+redfinir seccntformat.
+
+Exemple (\LaTeXe) :
+\makeatletter
+\renewcommand\@seccntformat[1]{\texttt{\@nameuse{the#1}\quad}}
+\makeatother
+%%%% fin exemple %%%%
+
+# 28.7 # Comment modifier la fonte du mode verbatim ?
+-----------------------------------------------------
+* Le package 'verbatim' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/ permet de faire cela. Il est alors
+conseill d'utiliser des fontes aux normes T1.
+
+* L'environnement verbatimcmd du package 'moreverb', disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/, permet de
+garder les caractres backslash (\) et les accolades ({, et })
+actifs. On peut donc entre autres oprer des changements de
+fonte.
+
+* Pour changer la taille de la fonte du mode verbatim, il faut
+l'encapsuler dans des commandes de modification de taille.
+
+Exemple :
+Texte avant.
+
+\begin{small}
+\begin{verbatim}
+ Texte...
+\end{verbatim}
+\end{small}
+
+Texte aprs.
+%%%% fin exemple %%%%
+
+# 28.8 # Comment raliser des changements de fontes relatifs ?
+--------------------------------------------------------------
+* Le package 'relsize' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ permet de faire ce genre de
+choses. Les commandes offertes sont du type :
+
++ \relsize{n} permet d'augmenter (n positif) ou de diminuer (n
+ngatif) la taille de la fonte par rapport la taille courante.
+
+Exemple :
+Un \relsize{1}texte \relsize{2}de \relsize{3}toutes
+\relsize{-1}les \relsize{-4}tailles.
+%%%% fin exemple %%%%
+
++ \smaller == \relsize{-1}
+
++ \larger == \relsize{1}
+
++ avec un argument, on trouve :
+\textsmaller{text}, \textlarger{text}, \mathsmaller{A},
+\mathlarger{B}
+%%%% fin exemple %%%%
+
+* Le package 'scalefnt' de D. Carlisle disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/carlisle/ permet d'augmenter
+ou de diminuer suivant un facteur proportionnel, la taille de
+la fonte courante.
+
+Exemple :
+\scalefont{2} double la taille de la fonte courante
+\scalefont{.75} rduit de trois quarts la taille de la fonte
+courante.
+%%%% fin exemple %%%%
+
+# 28.9 # Comment mettre en vidence une portion de texte ?
+----------------------------------------------------------
+Utiliser la commande \emph. Cette commande est dfinie dans la
+classe de votre document, et sert spcifiquement mettre en
+vidence un mot, une expression ou toute une phrase. La plupart
+du temps, elle se contente de mettre en italique votre texte.
+
+# 28.10 # O trouver des fontes ?
+---------------------------------
+Sur CTAN bien sr, dans ftp://ftp.fdn.org/pub/CTAN/fonts/.
+
+# 28.11 # Comment suivre le chargement des fontes ?
+---------------------------------------------------
+Le package 'tracefnt' permet de suivre le chargement des fontes
+lors de la compilation d'un document. Ce package dfinit
+plusieurs options :
++ infoshow pour avoir des informations sur le chargement des
+polices,
++ errorshow permet de n'afficher que les erreurs,
+etc.
+
+# 28.12 # Pourquoi MakeTeXPK est lanc alors que la fonte existe ?
+------------------------------------------------------------------
+P. Terray :
+C'est un problme de mise jour de la base li kpathsea.
+Normalement, MakeTeXPK met jour la base "ls-R" de la TDS,
+chaque ajout de police. Si cette base n'est pas autorise pour
+tout le monde, ou si la variable TEXMF est mal rgle, dvips ou
+xdvi ne peuvent pas vrifier que cette police existe. Du coup,
+ils lancent MakeTeXPK pour la fabriquer. Et MakeTeXPK sachant
+par ailleurs o mettre la police, il vrifie qu'elle existe, et
+c'est pour a qu'il donne le message comme quoi elle existe
+dj.
+
+Les solutions (UNIX) :
+- vrifier que $TEXMF est bien rgle
+- ls-R, fichier qui se trouve dans le rpertoire texmf, doit
+tre autoris en lecture criture pour tout le monde
+- reconstruire la base ls-R avec la commande texhash (tout
+court).
+
+ATTENTION : il faut avoir les droits de gestionnaire
+LaTeX (ou root) pour excuter texhash.
+
+# 28.13 # Comment utiliser \textsc dans un titre en conservant le gras ?
+------------------------------------------------------------------------
+Remarque : les sc grasses n'existent pas dans les fontes de
+ Knuth. En revanche, elles existent dans les fontes
+ EC.
+
+Depuis les dernires modifications dans les fontes EC, la
+simple utilisation de ces fontes suffit activer les
+petites capitales grasses.
+
+# 28.14 # Comment utiliser des fontes TrueType?
+-----------------------------------------------
+
+Une source d'information ce sujet:
+http://www.radamir.com/tex/ttf-tex.htm
+
+================================================================
+[29] DIVERS
+================================================================
+
+# 29.1 # A quoi sert la commande \par ?
+---------------------------------------
+Elle permet de marquer explicitement la fin d'un paragraphe pour
+permettre LaTeX de le mettre en page. L'utilit de cette
+commande se justifie par le fait que LaTeX met en page un texte
+par paragraphe. Elle est, le plus souvent, utilise dans la
+dfinition de macros.
+
+# 29.2 # Comment commenter une partie d'un source LaTeX ?
+---------------------------------------------------------
+* Sous LaTeX2.09, il suffit d'utiliser l'environnement
+comment du package 'version'.
+
+Exemple :
+Un paragraphe qui intresse tout le monde et qui est donc
+visible par tout le monde.
+
+\begin{comment}
+ Un paragraphe qui n'intresse que moi et qui n'est visible
+ que dans le source de mon document.
+\end{comment}
+
+Un autre paragraphe qui intresse tout le monde.
+%%%% fin exemple %%%%
+
+* Un environnement comment est galement dfini dans le package
+'verbatim' compatible LaTeX2.09 et LaTeX2e.
+
+* Il est galement possible de mettre des parties d'un document
+source en commentaire grce l'environnement comment dfini
+dans le package 'comment' de V. Eijkhout. Ce package est
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/.
+
+* Sous emacs, il y a une commande `comment-region' qui fait a
+trs bien. Avec un argument, elle dcommente.
+
+* Classique et de bon got, l'valuation conditionnelle permet
+de mettre en commentaire sans se soucier de l'imbrication des
+accolades, moins puissant cependant que les packages qui crent
+un environnement comment:
+
+Exemple:
+\iffalse
+Ce passage est en commentaire.
+\fi
+%%%% fin exemple %%%%
+
+# 29.3 # Comment utiliser LaTeX sur des petites machines ?
+----------------------------------------------------------
+La capacit de TeX est limite de manire interne. Cela signifie
+que ce sont des variables de TeX qui fixent le nombre de
+variables (et la taille mmoire) maximal que TeX s'autorisera
+utiliser. Si vous utilisez plus de variables que prvu, TeX
+s'arrtera sur le message d'erreur :
+
+ sorry, TeX capacity exceeded.
+
+Tout ceci est destin << prserver >> votre machine, c'est
+dire empcher TeX d'utiliser la totalit de la mmoire de
+la machine, ce qui conduit la plupart du temps un plantage.
+
+Sur une station, aucun problme, mais sur un micro-ordinateur,
+les configurations peuvent-tre nombreuses. C'est pourquoi le
+TeX fournit en << standard >> sur les macs, par exemple, des
+variables fixes assez bas (on suppose que le Mac a une toute
+petite mmoire compare une station). Mais il existe
+galement un BigTeX, dont la seule diffrence avec le TeX
+normal est qu'il est autoris utiliser plus de mmoire (les
+variables en questions ont des valeurs plus importantes).
+
+Du coup, si votre micro a une configuration plutt muscle, vous
+pouvez compiler des documents plus gros, plus complexes, etc...
+
+Heureusement Kiffe a chang de stratgie et dans les futures
+versions des outils les paramtres internes seront
+configurables (en passant par ResEdit) et donc on dcidera
+soi-mme la << bigness >> de son TeX (cf. distributions emTeX
+et AsTeX). Pour changer les paramtres de compilation (pool size,
+stack, font mem, main mem etc.) cf. fichier
+emtex/doc/english/tex.doc, chapitre 6.
+
+La version 7.0 de web2c est configurable par le fichier
+texmf.cnf.
+
+Remarque : pour un gros document, il peut tre utile de le
+ dcouper en chapitres inclure par la commande
+ \include (cf. paragraphe 9.2 ).
+
+# 29.4 # Comment visualiser des paramtres ?
+--------------------------------------------
+Pour visualiser des paramtres spcifiques, il existe :
+* \showt\baselinestretch (n'importe o ou presque, donc
+affichage des ventuelles modifs, locales ou globales). Ou
+pour avoir le rsultat la vole :
+\message{Valeur de /baselinestretch = \the\baselinestretch}
+
+* Il existe aussi la commande \showthe. Celle-ci affiche les
+paramtres demands dans le log. En outre, pendant la
+compilation, elle affiche la valeur demande puis met LaTeX en
+attente. Il faut alors taper s ou <RC> pour continuer.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\begin{document}
+Texte.
+\showthe\baselineskip
+Texte.
+\end{document}
+%%%% fin exemple %%%%
+
+* Pour afficher une valeur l'cran lors de la compilation, il
+faut utiliser : \message{** Textwidth = \the\textwidth **}. Le
+message s'insre alors au milieu des milliers d'autres choses que
+LaTeX affiche : bien surveiller !
+
+* Il existe galement le package 'showkeys' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/package/tools/. Il modifie les commandes
+\label, \ref, \pageref, \cite et \bibitem de manire
+visualiser les paramtres internes utiliss.
+
+* Pour visualiser les paramtres d'une page, il faut utiliser la
+commande \layout du package 'layout'. Ce dernier est disponible
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/.
+
+* Pour visualiser des labels, il existe le package 'showlabels'
+disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/showlabels/. Les noms des labels
+utiliss par \label ou par la numrotation automatique des
+quations apparatront dans la marge du document. Ce package ne
+dfinit pas de commande particulire, il suffit d'appeler
+\usepackage{showlabels} dans le prambule du document. Dans le
+cas o des packages AMS sont utiliss, showlabels doit tre
+appel aprs. Les options [inner] ou [outer] ou [twocolumn]
+permettent de dfinir dans quelle marge vont apparatre les
+labels.
+
+Remarque : ce package n'est pas compatible avec les styles
+ multicolonnes ni avec l'option leqno.
+
+# 29.5 # Comment visualiser des compteurs ?
+-------------------------------------------
+Pour visualiser la valeur d'un compteur, il suffit de demander
+\immediate\write{16}{\the\nomducompteur}
+ou
+\message{\the\nomducompteur}
+
+# 29.6 # A quoi servent \makeatletter et \makeatother ?
+-------------------------------------------------------
+Le caractre "@" est spcial pour LaTeX, et ne peut pas tre
+utilis directement comme partie d'un nom de macro dans un
+document LaTeX. Pour utiliser certaines macros internes de LaTeX
+(celles qui contiennent un "@"), directement dans un document
+(au lieu d'utiliser un fichier .sty), il faut les encapsuler
+dans une macro dont le nom ne contient pas de "@". En outre,
+cette macro doit imprativement tre dclare dans le
+prambule du document, et tre encadre par les commandes
+\makeatletter et \makeatother.
+
+En fait ces commandes permettent d'indiquer LaTeX que l'on
+veut effectivement travailler sur ses commandes internes en le
+forant considrer le "@" (at) comme une lettre
+(makeatletter).
+
+ATTENTION : les commandes internes de LaTeX sont manipuler
+ avec prcaution.
+
+# 29.7 # Comment numroter les lignes d'un document ?
+-----------------------------------------------------
+* Le package 'lineno' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/lineno/ permet de numroter les
+lignes d'un document.
+
+* Il existe galement le package 'numline' de M. Jaegermann et
+J. Fortune, pour du texte essentiellement. Ce package est
+disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/numline/.
+
+* Pour numroter les lignes d'un document inclu en mode
+verbatim, il faut utiliser la commande \listinginput du package
+'moreverb' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/moreverb/.
+
+* Le package 'vruler' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/vrsion/ permet galement de
+numroter les lignes d'un document.
+
+# 29.8 # A quoi sert la commande \special ?
+-------------------------------------------
+La commande \special permet TeX d'envoyer des instructions
+particulires (non TeX) un driver sans les interprter. Les
+instructions ainsi passes sont gnralement dpendantes du
+driver qui lui, saura les interprter. L'utilisateur n'a en
+gnral pas se soucier de cette commande (\special), elle est
+gre par des packages tels que 'psfig' pour LaTeX2.09 ou
+'graphics' et 'graphicx' pour LaTeX2e.
+
+Remarque : \includegraphics est standard dans LaTeX2e et
+ indpendant de la plateforme alors que le format de
+ \special est dramatiquement dpendant de la
+ plateforme de travail. Seul, le \includegraphics
+ prserve l'aspect universel d'un document source et
+ donc l'esprit universel de TeX.
+
+# 29.9 # Comment raliser des calculs avec les variables LaTeX ?
+----------------------------------------------------------------
+* Pour pouvoir utiliser des expressions du type \truc * \machin
+dans une macro, il faut charger le package 'calc' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/calc/.
+
+Exemple :
+\setcounter{x}{3*\real{1.3}}
+%%%% fin exemple %%%%
+
+* Une autre solution consiste utiliser les commandes
+\addtolength\dim\dim, \divide \dim by \dim, etc.
+
+* Le package 'realcalc' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/realcalc/ permet de faire des calculs sur des
+rels.
+
+* Plus difficile utiliser, il y a aussi le package 'trig'.
+
+# 29.10 # O trouver une fonte 9pt ?
+------------------------------------
+* La classe de document 'amsart' disponible sur CTAN offre
+l'option 9pt.
+
+* De mme les classes 'extarticle' et 'extreport' sont
+disponibles
+http://www.informatik.uni-freiburg.de/~may/extsizes.html.
+
+* size9.clo de H. Steffani est disponible
+http://www.tu-chemnitz.de/~hfst/size9.clo.
+
+# 29.11 # Comment automatiser les compilations LaTeX ?
+------------------------------------------------------
+* latexmk est un script perl, disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/latexmk/, qui automatise la compilation d'un document
+LaTeX. Il tourne en dmon et relance une compilation
+chaque fois qu'un fichier source (.tex, .bib, \input, etc) est
+sauvegard. "latexmk fichier" lance latex/makeindex/bibtex autant
+de fois qu'il le faut pour que le dvi soit jour.
+
+* latexn disponible sur ftp://ftp.fdn.org/pub/CTAN/support/latexn est un script
+csh qui permet galement d'automatiser les compilations LaTeX.
+
+* Le package AUC-TeX sous emacs conseille l'utilisateur sur la
+prochaine opration effectuer (LaTeX, bibtex, makeindex, xdvi,
+etc.), en fonction des dpendances entre les diffrents
+fichiers.
+
+# 29.12 # Comment obtenir des cadres gris ?
+-------------------------------------------
+* Le package 'shade' disponible sur ftp://ftp.fdn.org/pub/CTAN/macro/generic/
+permet de tracer des cadres gris.
+
+* Le package 'psboxit', disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex2.09/contrib/misc/, permet d'obtenir du gris ou de
+la couleur.
+
+# 29.13 # Comment obtenir certaines abrviations ?
+--------------------------------------------------
+* Pour obtenir des abrviations dont certaines lettres doivent
+tre rehausses et de taille rduite, on peut utiliser les
+indices mathmatiques. Mais, ce n'est pas une technique
+recommandable.
+
+Exemple :
+M$^{\mathrm{lle}}$
+%%%% fin exemple %%%%
+
+* Le package 'babel' propose la commande \ieme pour les
+quantimes.
+
+* Le package 'french' de B. Gaulle, dfinit la commande \fup
+pour crire une chane de caractres en exposant, ainsi que les
+commandes \ier \iers \iere \iere \ieme \iemes pour les
+quantimes.
+
+Exemple :
+M\fup{lle}
+%%%% fin exemple %%%%
+
+Remarque : pour que la commande \fup suive les changements de
+ taille de fonte, il faut utiliser l'une des extensions
+ prvues cet effet, savoir les extensions
+ "smaller" et "relsize" (\usepackage{smaller,french}
+ par exemple). Une copie de l'extension smaller est
+ distribue depuis 94 avec la distribution des
+ fichiers du style french (sous le nom mysmall.sty).
+ En revanche, la surlvation ne tient pas compte de
+ l'inclinaison de la police.
+
+* Le package 'smaller' de D. Taupin est disponible par ftp sur
+ftp://ftp.lps.u-psud.fr/pub/latex/contrib/smaller.sty. Il
+propose galement une commande \fup qui dfinit smaller et
+l@rger pour tre compris par french.sty. Cette commande gre
+l'inclinaison des \sl et des \it.
+
+ATTENTION : le fup de B. Gaulle tant install au
+ \begin{document}, pour utiliser mon \fup modifi
+ avec french.sty, il faut aprs le \begin{document}
+ crire:
+ \makeatletter
+ \let\fup\f@up
+ \makeatother
+
+* On peut galement dfinir une nouvelle commande \abbr dans le
+prambule du document :
+\newcommand{\abbr}[1]{\raisebox{1ex}{\footnotesize #1}}
+Cette solution a l'avantage d'viter d'utiliser le mode
+mathmatique improprement.
+
+* Il existe aussi la commande \textsuperscript qui permet
+d'obtenir un exposant sans passer en mode mathmatique.
+
+# 29.14 # Comment grer les espaces aprs une macro ?
+-----------------------------------------------------
+* Pour forcer LaTeX introduire un espace aprs une macro, il
+suffit de faire suivre son appel d'un backslash (\).
+
+Exemple :
+texte \oe\ texte \oe, texte
+
+texte \oe texte \oe, texte
+%%%% fin exemple %%%%
+
+* Pour que LaTeX gre lui mme les espaces, il suffit d'utiliser
+systmatiquement les caractres {}.
+
+Exemple :
+texte \oe{} texte \oe{}, texte \oe{}uf
+%%%% fin exemple %%%%
+
+* On peut galement dfinir une macro TeX \keepspace :
+%%%% debut macro %%%%
+\def\keepspace{\ifnum\catcode`\ =10
+ \let\next\keepspacebis \else \let\next\relax \fi
+ \next}
+\def \keepspacebis{\obeyspaces
+ \afterassignment\keepspaceaux\let\next= }
+{\obeyspaces%
+\gdef\keepspaceaux{%
+\ifx \next\space\let\next\ignorespaces\fi%
+\catcode`\ =10\relax\next}}
+%%%%
+%%%% fin macro %%%%
+puis l'utiliser dans une autre dfinition de macro.
+
+Exemple :
+\newcommand{\macro}{\textit{blablabla}\keepspace}
+%%%% fin exemple %%%%
+
+* Le package 'xspace' intgre ces dfinitions qui lui permette
+de grer automatiquement l'espace aprs une macro suivant le
+contexte.
+
+Exemple :
+\documentclass{report}
+\usepackage{french,xspace}
+\pagestyle{empty}
+
+\newcommand{\macro}{aaaaa\xspace}
+
+\begin{document}
+\macro bbbb \macro, bbbb
+\end{document}
+%%%% fin exemple %%%%
+
+Remarque : noter que le package xspace est conforme aux rgles
+ de typographie anglo-saxones donc la gestion des
+ caractres de ponctuation composs tels que : o ; ne
+ sera pas correcte en franais. La solution consiste
+ alors utiliser le blanc inscable qui de toutes
+ faons est recommand dans ce cas : \macro~: blabla.
+ On peut galement se crer son propre package
+ 'fxspace'.
+
+# 29.15 # O trouver les notices d'utilisation des packages ?
+-------------------------------------------------------------
+Gnralement la notice d'utilisation d'un package est incluse
+dans le package lui mme (fichier .dtx). Il suffit alors de
+compiler ce fichier. Il existe galement le fichier doc
+disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/base/ qui dcrit comment
+exploiter ces notices.
+
+Si on lance "latex package.dtx" il sera produit le fichier
+package.sty ou package.cls correspondant et le fichier
+package.dvi de documentation de l'extension.
+
+# 29.16 # Comment obtenir des listes d'objets flottants ?
+---------------------------------------------------------
+Certaines sont disponibles par dfaut, il s'agit des listes de
+figures et de tables, il suffit alors d'appeler les commandes
+\listoffigures et \listoftables. D'autres sont lies certains
+packages. Par exemple, le package 'algorithms' de P. Williams
+offre la commande \listofalgorithms.
+
+Remarque : la mise jour de ces listes ncessite gnralement
+ plusieurs compilations LaTeX.
+
+Exemple :
+\documentclass{report}
+\usepackage{algorithm,algorithmic}
+
+\begin{document}
+
+\listofalgorithms
+
+\chapter{toto}
+
+\begin{algorithm}[h!tp]
+ \begin{algorithmic}[2]
+ \REQUIRE $T_1$ et $T_2$ doivent \^etre des tableaux de
+ valeurs additionnables, et doivent \^etre de la m\^eme
+ longueur $n$. \ENSURE $\forall 0\leq k< n \;\;
+ Result[k]=T_1[k]+T_2[k]$.
+ \FOR{$i\rightarrow 0$ to $n$}
+ \STATE $Result[i]\rightarrow T_1[i]+T_2[i]$
+ \ENDFOR
+ \end{algorithmic}
+ \caption{Somme terme \`a terme de deux tableaux3}
+ \label{algo-ex-3}
+\end{algorithm}
+[recopie en trois exemplaires]
+\end{document}
+%%%% fin exemple %%%%
+
+# 29.17 # Comment connatre les versions des fichiers utiliss lors d'une compilation ?
+---------------------------------------------------------------------------------------
+Il suffit d'utiliser la commande \listfiles.
+
+Exemple :
+\documentclass{report}
+\listfiles
+\usepackage{french}
+\usepackage{graphics}
+
+\begin{document}
+ texte ...
+\end{document}
+%%%% fin exemple %%%%
+
+# 29.18 # Pourquoi certaines commandes sont elles indpendantes ?
+-----------------------------------------------------------------
+Les commandes LaTeX de type verbatim sont particulires du fait
+qu'elles changent les codes de catgorie de leurs arguments. De
+ce fait, elles ne sont plus compatibles avec d'autres commandes
+et ne doivent pas tre appeles par ces dernires. Certains
+caractres spciaux doivent alors tre obtenus par \texttt.
+
+Exemple :
+\texttt{\char`\\}
+%%%% fin exemple %%%%
+
+On peut galement utiliser l'environement lrbox de LaTeX2e pour
+sauver le texte qui doit apparatre en verbatim dans une bote
+et ensuite utiliser cette bote.
+
+# 29.19 # Comment installer un package ?
+----------------------------------------
+Lorsqu'il s'agit d'un package conu pour LaTeX2e et utilisant
+les procdures et outils dfinis dans ce cadre, c'est simple :
+un package est fourni avec deux (ou plus, pour les packages plus
+complexes) fichiers, package.ins et package.dtx
+
+Il faut commencer par excuter "latex package.ins" pour crer
+le(s) fichier(s) de commandes lui(eux)-mme(s) (typiquement
+package.sty) puis "latex package.dtx" pour gnrer la
+documentation, avec si besoin construction d'un index :
+makeindex -s gind.ist -o package.ind package.idx, et d'un
+glossaire : makeindex -s gglo.ist -o package.gls package.glo.
+
+Ces fichiers doivent ensuite tre dclars dans une variable
+d'environnement afin d'tre rendus visibles.
+
+Exemple (UNIX) :
+TEXINPUTS=.:/usr/local/TEX/texmf/tex:/users/ADMIN/NG/LATEX:
+/users/home/kluth/Section-equit/Modele
+%%%% fin exemple %%%%
+
+Remarques :
+* on ne peut videmment gnrer la documentation en premier,
+parce qu'elle aura toujours besoin du fichiers des commandes ;
+* si l'on ne veut obtenir que la documentation <<utilisateur>>,
+il faut ajouter la ligne "\OnlyDescription" dans le fichier
+package.dtx, avant la ligne "\DocInput{package.dtx}". Sinon on
+obtient aussi le listage comment du code, ce dont on peut ne
+pas vouloir se soucier et qui peut tre volumineux pour les
+packages importants.
+
+Nanmoins, il est clair que ce mode d'organisation et de
+distribution n'est que le mode encourag par l'quipe de
+dveloppement de LaTeX et n'est en rien une obligation. Un bon
+nombre de packages disponibles ne le suit d'ailleurs pas (!),
+pour diverses raisons (packages qui se veulent utilisables aussi
+bien avec Plain TeX qu'avec LaTeX, << vieux >> packages crits
+pour LaTeX2.09, packages crits par des personnes qui veulent
+faire << comme a leur plait >>, etc.)... Dans ces diffrents
+cas, il faut << aller y voir de plus prs >> pour comprendre
+l'organisation choisie.
+
+C'est justement le cas pour slashbox (!) : un seul fichier .sty
+est fourni. Il faut l'diter pour extraire le fichier de
+documentation qui se trouve aprs la ligne 80 "\endinput".
+
+*Pour WINDOWS :
+1/ copier le fichier package.ins dans un rpertoire
+temporaire et le compiler avec LaTeX ;
+2/ dplacer le fichier package.sty dans un rpertoire visible par
+LaTeX, soit commun tous les utilisateurs, soit local,
+soit personnel :
+-- pour fpTeX, ce sont respectivement les rpertoires (dclars
+l'installation de fpTeX) ./texmf/tex/latex/lerepertoiredemonpackage (
+crer si besoin), ./texmf.local/tex/latex/lerepertoiredemonpackage ( crer
+si besoin), HOME/texmf/tex/latex/lerepertoiredemonpackage ( crer si
+besoin) ;
+-- pour MikTeX, ce sont les mmes rpertoires mais le rpertoire local est
+./localtexmf/ et que le HOME ne semble pas tre prvu :
+[FMF : je ne suis pas sre de ce dernier point]
+3/ reconstruire la base de donnes des packages (rebuild ls-R filenames
+databases pour fpTeX, refresh filename database pour MikTeX).
+
+# 29.20 # Comment gnrer des codes barres ?
+--------------------------------------------
+* Il existe les packages 'ean' et 'code128' disponibles sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/ean/ et ftp://ftp.fdn.org/pub/CTAN/macros/generic/code128/.
+
+* De mme les packages 'envelopes' et 'labels' sont disponibles
+sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/envlab/.
+
+* On peut galement trouver le package 'barcodes' sur
+ftp://ftp.fdn.org/pub/CTAN/fonts/barcodes/.
+
+# 29.21 # Comment grer des abbrviations ?
+-------------------------------------------
+* Le package 'abbrevs' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/monster/ permet automatiquement
+de remplacer des abbrviations par leur formule dveloppe
+notamment lors d'un premier appel.
+
+* Le package 'acronym' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/acronym/ permet de s'assurer que
+tous les acronymes utiliss dans un document apparaissent au
+moins une fois sous une forme dveloppe.
+
+# 29.22 # Comment imprimer un fichier postscript sur une imprimante non postscript ?
+------------------------------------------------------------------------------------
+alladin est un excellent programme qui permet d'imprimer du
+postscript sur peu prs n'importe quelle imprimante. Cet outil
+est disponible par ftp sur ftp://ftp.lip6.fr/pub/ghost/aladdin/.
+
+Remarque : on ne peut pas dire que ce soit d'une trs grande
+ facilit d'installation, mais une fois que ce mauvais
+ moment est pass, on ne peut plus s'en passer :-)
+
+# 29.23 # Comment surcharger une commande dj existante ?
+----------------------------------------------------------
+* Pour pouvoir ajouter des dfinitions sur une commande
+prdfinie sans la rcrire compltement, il faut utiliser la
+commande \let.
+
+Exemple :
+\let\standardsection=\section
+\def\section{\newpage\standardsection}
+%%%% fin exemple %%%%
+
+* Il existe aussi la commande expandafter.
+
+Exemples :
+\toks0 \expandafter{\section}
+\edef\section{\noexpand\newpage\the\toks0 }
+
+\expandafter\def\expandafter\section\expandafter{\expandafter%
+\newpage\section}
+%%%% fin exemple %%%%
+
+* Le package 'babel' propose galement la commande \addto.
+
+# 29.24 # Comment reporter l'excution d'une commande la fin d'une page ?
+---------------------------------------------------------------------------
+Il existe pour cela le package 'afterpage' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/tools/.
+
+Exemple :
+\afterpage{\clearpage}
+%%%% fin exemple %%%%
+
+# 29.25 # Comment dfinir des scripts interactifs ?
+---------------------------------------------------
+Le package 'dialogl' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/dialogl/ permet de dfinir des
+scripts LaTeX intractifs.
+
+# 29.26 # Comment identifier une version provisoire ?
+-----------------------------------------------------
+* Le package 'draftcopy' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/draftcopy/ permet par exemple
+d'crire le mot DRAFT en gris en diagonale sur toutes ou
+certaines pages d'un document. Il permet galement de faire
+moins voyant.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\usepackage{draftcopy}
+\begin{document}
+Voici une version provisoire de mon texte. Pourriez-vous la
+relire et me faire part de vos commentaires avant la fin de
+la semaine?
+
+Merci d'avance.
+
+\paragraph{Proposition.}
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire --
+Texte provisoire -- Texte provisoire -- Texte provisoire
+
+\end{document}
+%%%% fin exemple %%%%
+
+* Le package 'drafthead' galement disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex209/contrib/misc/ permet lui de n'agir que sur les
+en-ttes des documents.
+
+* On peut galement utiliser la macro :
+%%%% debut macro %%%%
+\special{
+! userdict begin /bop-hook{
+stroke
+gsave 240 100 translate
+65 rotate /Times-Roman findfont 220 scalefont setfont
+0 0 moveto 0.9 setgray (DRAFT) show grestore
+}def end}
+dans le prambule de son document.
+%%%% fin macro %%%%
+
+* Le package 'prelim2e' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/prelim2e/ offre galement un
+marquage des versions prliminaires d'un document.
+
+# 29.27 # Comment obtenir des caractres barrs ?
+-------------------------------------------------
+* Le package 'ulem' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/other/misc/ permet de
+barrer des caractres.
+
+Exemple :
+\sout{je barre tout}
+%%%% fin exemple %%%%
+
+# 29.28 # A quoi sert la commande \ensuremath ?
+-----------------------------------------------
+La commande \ensuremath assure que son argument sera imprim en
+mode mathmatique quel que soit le mode courant.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\newcommand{\mc}{\ensuremath{(\alpha, \beta)}}
+\begin{document}
+Le couple \mc\ dfinit par $\mc = x+y, x-y$, ...
+\end{document}
+%%%% fin exemple %%%%
+
+# 29.29 # A quoi servent les commandes \(re)newcommand ?
+--------------------------------------------------------
+La commande \newcommand permet l'utilisateur de dfinir ses
+propres commandes. La commande \renewcommand permet de
+redfinir des commandes LaTeX dj existantes. Elle s'utilise
+dans le prambule du document :
+ \newcommand{nom_commande}[nb_arguments]{dfinition}
+nb_arguments dfinit le nombre d'arguments de la nouvelle
+commande LaTeX. Il est compris entre 0 et 9. Ils sont
+rfrencs par #no_argument dans la dfinition.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+\pagestyle{empty}
+\newcommand{\be}{\begin{enumerate}}
+\newcommand{\ee}{\end{enumerate}}
+\newcommand{\bold}[1]{\textbf{#1}}
+\begin{document}
+\bold{Faites votre choix~:}
+\be
+\item premier choix~: A
+\item deuxime choix~: B
+\item troisime choix~: C
+\ee
+\end{document}
+%%%% fin exemple %%%%
+
+Remarques : La commande \providecommand permet de ne prendre en
+ compte la nouvelle commande que si elle n'existe pas
+ dj.
+
+ Pour dfinir un argument optionnel, on utilise la
+ syntaxe :
+ \newcommand{nom}[nb_arg][defaut]{definition}
+ defaut permet de prciser une valeur par dfaut de
+ la variable qui sera utilise en l'absence
+ d'argument. L'argument optionnel ne peut tre que
+ #1.
+
+# 29.30 # O trouver des hirondelles ?
+--------------------------------------
+On peut trouver la package 'cropmark' sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/.
+
+# 29.31 # Comment tracer des lignes ?
+-------------------------------------
+* On peut mettre la dfinition suivante dans le prambule du
+document :
+\def\ligne#1{\leaders\hrule height #1\linethickness \hfill}
+puis utiliser :
+\ligne{5}
+dans le texte.
+
+* Il existe galement la commande \rule qui prend en premier
+argument, la longueur horizontale du trait et, en deuxime, son
+paisseur. Elle possde galement un argument optionnel qui
+permet de positionner la ligne trae par rapport la ligne
+d'criture.
+
+Exemple :
+\rule[0.5ex]{\textwidth}{0.1mm}
+%%%% fin exemple %%%%
+
+* On peut aussi utiliser les commandes \hrule pour des lignes
+horizontales et \vrule pour des lignes verticales.
+
+# 29.32 # Comment imprimer le caractre ~ ?
+-------------------------------------------
+* LaTeX2e fournit la commande \textasciitilde sous fonte T1.
+Sous OT1, il faut dfinir
+\ProvideTextCommand{\textasciitilde}{OT1}{\~{}}.
+
+* Il est possible de passer par le mode verbatim via la commande
+\verb$~$.
+
+* On peut aussi dfinir sa propre commande :
+\def\mytilde{\raisebox{-.8ex}{\~~}\hspace{-0.15em}}
+
+* \~{} permet galement d'obtenir un tilde.
+
+* Une autre solution consiste utiliser $\sim$.
+
+* Autre solution, utiliser : \char`\~
+
+Remarque : la premire solution est de loin la meilleure.
+
+# 29.33 # Comment visualiser tous les caractres d'une fonte ?
+--------------------------------------------------------------
+Le plus simple consiste utiliser :
+latex nfssfont
+nfssfont.tex est un fichier disponible sur CTAN.
+
+Il faut ensuite donner le nom de la fonte examiner par
+exemple cmr10 puis construire la table des caractres en
+utilisant la commande \table. Cela permet de construire un
+fichier .dvi contenant les codes de tous les caractres.
+
+L'appel d'un symbole se fait alors via la commande \symbol{x} o
+x est le code associ au caractre voulu (c'est un entier
+compris entre 0 et 255).
+
+On peut galement utiliser \char"<octal> ou \char^^<hexa>
+ou encore \char<decimal> mais ces commandes sont moins robustes.
+
+# 29.34 # A quoi sert % dans les macros ?
+-----------------------------------------
+Le % en fin de ligne d'une macro permet d'indiquer LaTeX que
+la dfinition qu'il est en train de lire continue la ligne
+suivante. De manire gnrale, les espaces aprs une macro sont
+ignors, mais pas aprs les accolades. Ce caractre permet de
+s'assurer que des espaces non voulus ne seront pas pris en
+compte. Ainsi, il est prudent de mettre un % aprs chaque
+accolade qui se trouve en fin de ligne.
+
+# 29.35 # Comment inclure l'heure dans un document ?
+----------------------------------------------------
+* La macro dcrite ci-dessous, inclure dans le prambule de
+votre document, dfinit la commande \timenow :
+
+%%%% debut macro %%%%
+\makeatletter
+\def\timenow{\@tempcnta\time
+ \@tempcntb\@tempcnta
+ \divide\@tempcntb60
+ \ifnum10>\@tempcntb0\fi\number\@tempcntb
+ \multiply\@tempcntb60
+ \advance\@tempcnta-\@tempcntb
+ :\ifnum10>\@tempcnta0\fi\number\@tempcnta}
+\makeatother
+%%%% fin macro %%%%
+
+* Le package 'time' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/generic/time.sty permet d'inclure l'heure courante
+dans un document.
+
+* En ajoutant la macro suivante de H. Hanche-Olsen dans le
+prambule de son document, on peut via la commande
+%%%% debut macro %%%%
+\isodayandtime obtenir la date et l'heure courante :
+\begingroup
+\count0=\time \divide\count0by60 % Hour
+\count2=\count0 \multiply\count2by-60 \advance\count2by\time
+% Min
+\def\2#1{\ifnum#1<10 0\fi\the#1}
+\xdef\isodayandtime{\the\year-\2\month-\2\day\space\2{\count0}:%
+\2{\count2}}
+\endgroup
+%%%% fin macro %%%%
+
+Autre exemple d'utilisation (qui ncessite dvips) :
+%%%% debut macro %%%%
+\special{!userdict begin /bop-hook
+ {gsave -90 rotate -780 560 moveto 1.0 0.7 0.7 setrgbcolor
+ % 0.8 setgray
+ 106 45 {dup mul exch dup mul add 1.0 exch sub} setscreen
+ /Times-Roman findfont 25 scalefont setfont (DRAFT
+ \isodayandtime) show grestore} def}
+%%%% fin macro %%%%
+
+* On peut galement utiliser la macro \time qui donne l'heure
+en minutes. Pour afficher l'heure en heures et minutes, il faut
+les calculer puis les afficher avec la macro \the.
+
+Exemple 1 :
+\documentclass{article}
+\usepackage{french}
+\pagestyle{empty}
+\begin{document}
+Cette compilation a dmarr \the\time\ minutes aprs minuit
+le \today.
+\end{document}
+%%%% fin exemple %%%%
+
+Exemple 2 :
+\usepackage{calc}
+\newcounter{hours}\newcounter{minutes}
+\newcommand{\printtime}{%
+ \setcounter{hours}{\time/60}%
+ \setcounter{minutes}{\time-\value{hours}*60}%
+ \thehours :\theminutes}
+%%%% fin exemple %%%%
+
+* Il existe galement le package 'heure' de T. Bouche donn
+ci-dessous :
+%%%% debut macro %%%%
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{heure}
+[1996/6/11v0.1 affiche le jour et l'heure de production d'un
+document]
+\newif\if@heure@fin\@heure@finfalse
+\newif\if@heure@final\@heure@finalfalse
+\DeclareOption{fin}{\@heure@fintrue}
+\DeclareOption{final}{\@heure@finaltrue}
+\DeclareOption{draft}{}
+\ProcessOptions
+%%% dfinition de hours prise dans testfont
+\newcount\m \newcount\n
+\def\hours{\n=\time \divide\n 60
+ \m=-\n \multiply\m 60 \advance\m \time
+ \twodigits\n\ :\ \twodigits\m}
+\def\twodigits#1{\ifnum #1<10 0\fi \number#1}
+%%%%%%% Tant que a n'est pas dfinitif.
+\if@heure@final\else
+\AtBeginDocument{\begin{center}%
+ {\bfseries\itshape\large Version du \today\ \hours }%
+\end{center}}
+\fi
+\if@heure@fin
+\AtEndDocument{%
+ \begin{flushright}%
+ \small \itshape (Le \today\ \hours )\hspace*{3em}%
+ \end{flushright}}
+\fi
+\endinput
+%%%% fin macro %%%%
+
+Utilisation :
+Il suffit de passer fin, final ou draft en option de classe.
+
+Exemple 1 :
+\documentclass[11pt,draft]{article}
+\usepackage{heure}
+
+\begin{document}
+Voici le rsum de notre exprience avec le Brome~:
+
+Bla bla bla.
+\end{document}
+%%%% fin exemple %%%%
+
+Exemple 2 :
+\documentclass[11pt,fin]{article}
+\usepackage{heure}
+
+\begin{document}
+Voici le rsum de notre exprience avec le Brome~:
+
+Bla bla bla.
+\end{document}
+%%%% fin exemple %%%%
+
+Exemple 3 :
+\documentclass[11pt,final]{article}
+\usepackage{heure}
+
+\begin{document}
+Voici le rsum de notre exprience avec le Brome~:
+
+Bla bla bla.
+\end{document}
+%%%% fin exemple %%%%
+
+# 29.36 # Comment compter le nombre de mots d'un fichier ?
+----------------------------------------------------------
+A priori, il n'y a pas de solution simple ce problme :
+* A partir du fichier source .tex, il faut enlever toutes les
+commandes LaTeX avec un utilitaire tel que detex (disponible sur
+ftp://ftp.fdn.org/pub/CTAN/support/detex/) puis utiliser un autre utilitaire tel
+que wc sous UNIX.
+
+* On peut galement travailler partir du fichier .dvi en
+appliquant dvitty (ou dvi2tty).
+
+ATTENTION : aucune de ces mthodes n'est idale comme l'indique
+ l'essai comparatif de T. Bouche :
+ detex -i grfguide.tex | wc -w donne 4420
+ dvitty grfguide.dvi |wc -w donne 4524
+ wc -w grfguide.tex donne 4539
+ ps2ascii grfguide.ps |wc -w donne 5066
+
+# 29.37 # Comment rendre inactif un caractre ?
+-----------------------------------------------
+La commande \string permet de dsactiver un caractre rendu
+actif par une macro.
+
+Exemple :
+En franais le : est rendu actif pour que \LaTeX gre lui-mme
+l'espace mettre avant. En revanche, dans une URL ou une
+adresse mail cet espace est superflu. On utilise donc :
+mailto\string:moi.meme@chez.mon.site
+%%%% fin exemple %%%%
+
+# 29.38 # Comment utiliser le mode verbatim dans une commande ?
+---------------------------------------------------------------
+LaTeX2e fournit l'environnement lrbox.
+
+Exemple :
+\documentclass{article}
+\usepackage{alltt}
+\pagestyle{empty}
+
+% ---------------
+\newsavebox{\inverbatim}
+\begin{lrbox}{\inverbatim}%
+\noindent\begin{minipage}{\linewidth}
+\begin{alltt}
+ 1
+ -8 + 7 Sqrt[2] ArcTanh[-------]
+ Sqrt[2]
+\end{alltt}
+\end{minipage}%
+\end{lrbox}% box
+% ------------------------------------
+
+\begin{document}
+\noindent
+L'expression : \usebox{\inverbatim} dmontre au paragraphe
+prcdent prend ici tout son sens.
+
+En effet l'expression \usebox{\inverbatim} permet\ldots
+\end{document}
+%%%% fin exemple %%%%
+
+# 29.39 # Comment redfinir la commande \year ?
+-----------------------------------------------
+Pour ne faire apparatre que deux chiffres au lieu de quatre, il
+faut utiliser :
+\newcommand{\ignoretwo}[2]{}
+\newcommand{\shortyear}{\expandafter\ignoretwo\the\year}
+dans le prambule du document.
+
+# 29.40 # Qu'est ce que la magnification ?
+------------------------------------------
+* La commande magnification permet de faire un zoom d'un
+document.
+
+Exemple :
+\mag=1440
+\documentclass{...}
+%%%% fin exemple %%%%
+
+* On peut galement travailler sur le fichier postscript via
+dvips avec l'option -x nombre o nombre vaut par exemple 1200
+pour un agrandissement de 20%.
+
+* De la mme manire, le package 'scale' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/scale/ permet de modifier
+l'chelle d'un document avant impression.
+
+# 29.41 # Comment sont grs les postscripts dans LaTeX ?
+---------------------------------------------------------
+P. Perichon :
+TeX/LaTeX + DVIPS procdent en 2 temps :
+* Lorsque l'on a une figure PostScript (EPS : Encapsulated
+PostScrit), on met les commandes ncessaires dans son source
+(fichier .tex) pour dire TeX/LaTeX que l'on veut cette figure
+ telle place dans son document avec telles dimensions (en
+incluant la bonne extension : graphicx, psfig, epsfig) .
+
+Lors de la phase d'interprtation du code TeX/LaTeX,
+l'interprte TeX/LaTeX va seulement consulter dans le fichier
+externe contenant la figure les dimensions/proportions de
+l'image (les fameuses bounding box chres au PostScript
+Encapsul).
+
+En fin de course, dans le fichier DVI on aura le nom et les
+dimensions de l'image mais PAS CELLE-CI (qui est toujours
+externe). Donc si on visualise juste le fichier DVI, on voit
+l'emplacement de l'image mais pas cette dernire (en particulier
+la commande \psdraft gnre un cadre genre \fbox{...} aux
+dimensions de l'image l'emplacement de celle-ci).
+
+* Dans un deuxime temps, la commande DVIPS, transformera le
+fichier DVI en PostScript et incluera ce moment les fichiers
+images EPS. Donc si on visualise/imprime le fichier PostScript,
+on voit le texte et les images.
+
+* Toutefois, certains visualiseurs DVI, par exemple XDVI sous
+UNIX pour ne pas le citer, dtectent quelque chose du genre :
+ PSfile="toto.eps" llx=0 lly=-1 urx=57 ury=29 rwi=4252
+dans le fichier DVI, et appellent gentiment GostScript/GhostView
+qui vont prparer une image bitmap que le visualiseur DVI
+s'empressera de montrer (quand a marche : avec psfig.sty pas de
+problme, mais avec l'extension graphicx...). Mais d'autres
+visualiseurs, comme DVIWIN, ne savent pas que faire d'un fichier
+PS.
+
+DVI signifie DeVice Independent : ceci est un format de document
+indpendant du systme d'impression. Donc non li un langage
+de description de page utilis en interne par une quelconque
+imprimante (PostScript, PCL, HPGL, Windows GDI, ...). Il suffit
+aprs d'utiliser un convertisseur qui transforme le DVI en
+quelque chose que comprend votre imprimante (PostScript, HPGL,
+PCL, ...). Cette mthode permet d'imprimer sur n'importe quel
+type d'imprimante (il suffit d'avoir le bon convertisseur). Mais
+hlas en DVI, il n'a point t prvu d'y mettre une image (le
+problme n'est en effet pas simple). D'o l'utilisation de fichier
+EPS.
+
+# 29.42 # Pourquoi LaTeX n'accepte-t'il pas tous les formats d'image ?
+----------------------------------------------------------------------
+P. Perichon :
+Le problme est le suivant : un fichier DVI + image TIFF, GIF,
+TGA,... comment faire digrer tout a par votre imprimante ????
+Le fichier DVI peut se faire convertir en un langage
+d'impression comprhensible par votre imprimante... mais vos
+formats d'images... faudrait-il en plus prvoir un systme de
+conversion de TIFF, GIF, TGA, ... vers le langage d'impression
+de votre imprimante (Alladin avec GhostScript/GhostView propose
+quelques filtres, mais bon). A part quelques langages de
+description de pages comme PostScript et un ou deux autres qui
+pratiquent une compatibilit ascendante quant aux versions du
+langage qu'ils utilisent, les autres fabricants d'imprimantes
+changent de langage quasiment chaque modle ou srie
+d'imprimante (impossible de tenir jour autant de
+convertisseurs).
+
+Pour tout cela le langage PostScript (PS et EPS) nous rend
+grandement service en nous simplifiant la vie (et pour d'autres
+raisons aussi). C'est peut-tre un peu plus lourd manipuler,
+mais plus simple pour tout le monde de convertir vos images en
+EPS. De plus, si vous ne disposez pas d'imprimante PostScript,
+GhostScript/GhostView se chargera d'interprter le fichier PS
+(texte + images), fabriquera une bitmap la bonne rsolution et
+pourra l'envoyer votre imprimante via votre pilote
+d'impression. Tout cela automatis dans une bonne distribution
+est transparent l'utilisateur.
+
+Pour plus de dtails, consulter le grfguide disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/packages/graphics/ et le document epslatex
+disponible sur ftp://ftp.fdn.org/pub/CTAN/info/.
+
+# 29.43 # A quoi sert la commande \(re)newenvironment ?
+-------------------------------------------------------
+Les commandes \newenvironment et \renewenvironment permettent de
+dfinir des actions qui seront appliques entre les commandes
+\begin{mon_environnement} et \end{mon_environnement}. Ces
+commandes doivent tre appeles dans le prambule du document
+suivant la syntaxe :
+ \newenvironment{nom}[nb_arg]{avant}{aprs}
+avant et aprs sont les actions qui auront lieu l'entre et
+la sortie du nouvel environnement.
+
+Exemple :
+\documentclass{report}
+\usepackage{french}
+
+\newenvironment{Relief}[1]
+{\mbox{\Large{\uppercase{#1}}}}
+
+\begin{document}
+\begin{Relief}
+ {Il}~tait une fois~\ldots
+\end{Relief}
+\begin{Relief}
+ {U}n jour peut tre~\ldots
+\end{Relief}
+%%%% fin exemple %%%%
+
+# 29.44 # Comment rcuprer le nom du fichier compil ?
+-------------------------------------------------------
+Pour rcuprer le nom du fichier compil et l'afficher lors
+d'une compilation, il faut utiliser la commande \jobname.
+
+Exemple :
+Le fichier source est \texttt{\jobname.tex}.
+%%%% fin exemple %%%%
+
+# 29.45 # Comment grer des conditions de traitement dans un style ?
+--------------------------------------------------------------------
+Le package 'ifthen' disponible sur ftp://ftp.fdn.org/pub/CTAN/macros/latex/base/
+permet d'implmenter des traitements conditionnels tels que
+\ifthenelse et \whiledo.
+
+# 29.46 # A quoi servent les commandes \setlength et \addtolength ?
+-------------------------------------------------------------------
+Ces deux commandes permettent de modifier la longueur de
+certains paramtres.
+
+Exemples :
++ \setlength{nom_parametre}{longueur}
++ \addtolength{nom_parametre}{longueur}
+%%%% fin exemple %%%%
+
+# 29.47 # Quelles sont les units de mesure de TeX ?
+----------------------------------------------------
+TeX comprend six units de mesure :
++ pt point = 0,35 mm
++ mm millimtre
++ ex correspond la hauteur d'un x dans la fonte courante
++ em correspond la largeur d'un m dans la fonte courante
++ cm centimtre
++ in pouce = 2,54 cm
+
+# 29.48 # A quoi sert la commande \mbox ?
+-----------------------------------------
+La commande \mbox permet LaTeX de considrer son argument
+comme une seule entit. Elle peut ainsi empcher la coupure
+d'un mot ou d'un groupe de mots.
+
+Exemple :
+Mon numro de tlphone est le~\mbox{01 69 63 12 68}.
+%%%% fin exemple %%%%
+
+# 29.49 # Comment obtenir des points de suspension ?
+----------------------------------------------------
+La commande \ldots permet d'obtenir trois points de suspension
+espacs correctement.
+
+# 29.50 # Comment dsactiver une ligature ?
+-------------------------------------------
+Pour dsactiver une ligature, il faut introduire {} ou une
+\mbox{} entre les lettres ligatures.
+
+Exemple :
+comparez effacer, ef{}facer et ef\mbox{}facer
+%%%% fin exemple %%%%
+
+# 29.51 # Comment grer les versions d'un document ?
+----------------------------------------------------
+* Pour les versions provisoires, voir la question 29.26.
+
+* Il existe le package 'vrsion' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/vrsion/ qui permet via la
+commande \version d'inclure un numro de version dans un
+document LaTeX. Ce numro est incrment chaque compilation.
+
+* On peut galement se reporter la question 29.35 pour inclure
+le jour et l'heure de compilation dans un document.
+
+# 29.52 # Comment changer certains titres ?
+-------------------------------------------
+Il suffit de renommer les variables suivantes :
+ \def\refname{R\'ef\'erences}%
+ \def\abstractname{R\'esum\'e}%
+ \def\bibname{Bibliographie}%
+ \def\prefacename{Pr\'eface}%
+ \def\chaptername{Chapitre}%
+ \def\appendixname{Annexe}%
+ \def\contentsname{Table des mati\`eres}%
+ \def\listfigurename{Table des figures}%
+ \def\listtablename{Liste des tableaux}%
+ \def\indexname{Index}%
+ \def\figurename{{\scshape Fig.}}%
+ \def\tablename{{\scshape Tab.}}%
+ \def\partname{\protect\@Fpt partie}%
+ \def\@Fpt{{\ifcase\value{part}\or Premi\`ere\or Deuxi\`eme\or
+ Troisi\`eme\or Quatri\`eme\or Cinqui\`eme\or Sixi\`eme\or
+ Septi\`eme\or Huiti\`eme\or Neuvi\`eme\or Dixi\`eme\or
+ Onzi\`eme\or Douzi\`eme\or Treizi\`eme\or Quatorzi\`eme\or
+ Quinzi\`eme\or Seizi\`eme\or Dix-septi\`eme\or
+ Dix-huiti\`eme\or Dix-neuvi\`eme\or Vingti\`eme\fi}}%
+ \space\def\thepart{}}%
+ \def\pagename{page}%
+ \def\seename{{\emph{voir}}}%
+ \def\alsoname{{\emph{voir aussi}}}%
+ \def\enclname{P.~J. }%
+ \def\ccname{Copie \`a }%
+ \def\headtoname{}%
+ \def\proofname{D\'emonstration}% for AMS-LaTeX
+
+Remarque : lorsque certains changements de noms sont dj grs
+ par un package (french par exemple) il faut placer
+ les dfinitions ci-dessus aprs le \begin{document}.
+
+# 29.53 # Comment insrer un code source dans un document ?
+-----------------------------------------------------------
+* Le package 'listings' disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/latex/contrib/supported/listings/ permet de grer la
+mise en page de code source avec notamment la mise en relief de
+mots cls.
+
+* La distribution GUTenberg contient un package du nom de
+'lgrind' (executable+lgrind.sty) qui, entre autres (C, C++,
+Pascal, BASIC, Modula-2, Fortran, RATFOR, Yacc, PostScript,
+Prolog, MLisp, Icon, LaTeX, Perl, CSH, Bourne Shell, assembler,
+68000 assembler, asm68, VMS assembler, ISP, LDL, Linda, MODEL,
+MatLab, Russell), formatte du code C++ en LaTeX. Ce programme
+disponible sur CTAN permet partir de code source C de gnrer
+du code LaTeX respectant l'indentation. Ce package est galement
+disponible sur ftp://ftp.fdn.org/pub/CTAN/support/lgrind/.
+
+* wflman disponible par ftp sur
+ftp://ftp.keck.hawaii.edu/pub/wlupton/wflman-2.2.2.tar.gz
+peut aussi tre utile.
+
+* Il existe galement DOC++ qui peut crer une documentation
+HTML ou LaTeX partir des infos ajoutes dans les commentaires
+du code C++. Pour plus de dtails, voir :
+http://www.ZIB-Berlin.DE/VisPar/doc++/doc++.html
+
+* Le package 'tgrind', qui vient avec un .sty et une moulinette
+permet de transformer un .c en .tex
+
+* Le package 'c++2latex' sous license GNU est capable de
+convertir des fichiers C, C++ et JAVA en LaTeX2e. Les lignes
+peuvent tre numrotes.
+
+* Le package 'cprog' disponible sur CTAN permet de formater des
+programmes C en TeX.
+
+* Le package 'c2ltx', de M. Plugge
+(plugge@biv7.sr.fh-mannheim.de), appartient la famille de
+convertisseurs cvt2ltx. Il numrote les lignes, traduit != en
+$\neq$ , gre les commentaires, les en-ttes de procdures, etc.
+Il supporte plusieurs fichiers d'entre et gre automatiquement
+les changements de section et la gnration d'index. Une
+documentation est disponible par ftp sur
+ftp://axp3.sr.fh-mannheim.de/cvt2latex/cvt2ltx.zip.
+Ce package sera bientt disponible sur CTAN.
+AL: il y est, peut tre, non ?
+
+# 29.54 # Comment tracer une ligne horizontale ?
+------------------------------------------------
+* Pour obtenir une ligne centre par rapport la mi-hauteur au
+dessus de la ligne d'criture, on peut utiliser ceci :
+\hbox{\raisebox{0.4em}{\vrule depth 0pt height 0.4pt width 1cm}
+Toto}
+
+# 29.55 # Comment gnrer un espace invisible de taille donne ?
+----------------------------------------------------------------
+Il existe pour cela la commande \phantom. Celle-ci gnre un
+espace invisible de la mme longueur que son argument.
+
+Exemple :
+Complte les mots qui manquent dans le texte suivant~:
+
+Le petit chaperon \phantom{rouge} se promne~\ldots.
+%%%% fin exemple %%%%
+
+# 29.56 # Qu'est ce qu'une correction italique ?
+------------------------------------------------
+Pour que LaTeX puisse grer correctement le passage d'une fonte
+italique une fonte droite, il peut tre utile d'utiliser la
+commande \/. Cela permet d'augmenter lgrement l'espace qui
+spare la dernire lettre en italique, de la premire lettre
+droite.
+
+Exemple :
+Un \textit{cheval}\/ file au galop.
+%%%% fin exemple %%%%
+
+# 29.57 # Quels sont les accents accessibles sous LaTeX ?
+---------------------------------------------------------
+Les accents accessibles sous LaTeX sont les suivants :
++ \`{a} ou \`a accent grave
++ \'{e} ou \'e accent aigu
++ \^{i} ou \^i accent circonflexe
++ \"{o} ou \"o trema
++ \~{u} ou \~u tilde
++ \={o} ou \=o surlign
++ \.{o} ou \.o point
++ \u{o}
++ \v{o}
++ \H{o} trema hongrois
++ \t{oo}
++ \c{c} cdille
++ \d{o} point en dessous
++ \b{o} souslign
+
+# 29.58 # Comment crire dans un fichier pendant une compilation ?
+------------------------------------------------------------------
+* On dispose pour cela des commandes \write et \newwrite.
+
+Exemple :
+\newwrite\test
+\openout\test=toto
+\write\test{Je m'appelle Paul}
+\write\test{\noexpand\thesection}
+\closeout\test
+\bye
+%%%% fin exemple %%%%
+
+Remarque : \noexpand permet d'inclure des commandes LaTeX sans
+ qu'elles soient interprtes.
+
+* Le package 'french' propose la commande
+\originaloutput[fichier]{texte} pour crire le "texte", tel
+qu'il est fourni, dans le "fichier". Dans ce cas, les caracteres
+actifs de french sont automatiquement desactivs. C'est donc
+l'equivalent de \immediate\write\fichier{texte}.
+
+* Le package 'sverb' disponible sur CTAN propose
+l'environnement verbwrite.
+
+Exemple :
+\begin{verbwrite}{fichier.tmp}
+ Ce texte va tre sauv dans le fichier fichier.tmp.
+\end{verbwrite}
+%%%% fin exemple %%%%
+
+# 29.59 # Comment grer des compteurs ?
+---------------------------------------
+Un certain nombre de compteurs sont prdfinis dans LaTeX, il
+s'agit :
++ des compteurs de structuration du document : part, chapter,
+section, subsection, subsubsection, paragraph, subparagraph,
++ du compteur de page,
++ du compteur d'quation,
++ du compteur de figure,
++ du compteur de tables,
++ des compteur de notes : footnote et mpfootnote,
++ et des compteurs de liste : enumi, enumii, enumiii et enumiv.
+
+Pour dfinir son propre compteur, il faut utiliser la commande
+\newcounter{nv_cptr}[ref_cptr]. Lorsque qu'un compteur dj
+existant est pass en argument (ref_cptr), le nouveau compteur
+nv_cptr sera rinitialis chaque incrment (via \stepcounter
+ou \refstepcounter) du compteur ref_cptr.
+
+Par dfaut, la valeur d'un nouveau compteur est 0. La commande
+\setcounter{cptr}{val} permet de lui donner une autre valeur. On
+peut galement incrmenter la valeur d'un compteur via la
+commande \addtocounter{cptr}{val}. La valeur d'un compteur peut
+tre rcupre, dans un calcul par exemple, grce la commande
+\value{cptr}.
+
+\stepcounter{cptr} permet d'incrmenter le compteur cptr et de
+rinitialiser tous les compteurs lis par rfrence (argument
+ref_cptr de la commande \newcounter). La commande
+\refstepcounter{cptr} permet en outre de mettre jour la valeur
+courante du compteur qui pourrait tre appel par un \ref.
+
+\thecptr, o cptr est le nom d'un compteur, permet d'afficher sa
+valeur.
+
+Exemple :
+\newcounter{section}
+\newcounter{subsection}[section]
+%%%% fin exemple %%%%
+
+# 29.60 # Quels sont les diffrents styles de compteurs ?
+---------------------------------------------------------
+Il en existe six prdfinis :
++ \arabic{cptr} pour un nombre arabe,
++ \roman{cptr} pour un nombre romain minuscule,
++ \Roman{cptr} pour un nombre romain majuscule,
++ \alph{cptr} pour une lettre minuscule,
++ \Alph{cptr} pour une lettre majuscule,
++ \fnsymbol{cptr} pour un symbole.
+
+Exemple :
+\renewcommand{\thesection}{\Roman{section}}
+\renewcommand{\thesubsection}{\thesection.\roman{subsection}}
+%%%% fin exemple %%%%
+
+# 29.61 # Comment programmer un traitement itratif ?
+-----------------------------------------------------
+Le package 'multido' propose une commande \multido qui est une
+boucle TeX. Sa syntaxe est la suivante :
+ \multido{variables}{nbiteration}{code}
+Le code sera ainsi rpt nbiteration fois. Les dclarations de
+variables sont spares par des virgules. Un dclaration prend
+la forme :
+ variable = valeurinitiale + increment
+Elle est utile notamment pour le dessin de figures.
+
+Exemple (doc package) :
+\setlength{\unitlength}{1cm}
+\small
+\begin{picture}(8,1)(0,-.5)
+ \put(0,0){\vector(1,0){8}}
+ \multido{\i=0+1, \n=0+0.25}{8}{%
+ \put(\i,-.1){\line(0,1){.2}}
+ \put(\i,-.2){\makebox(0,0)[t]{\n}}}
+\end{picture}
+%%%% fin exemple %%%%
+
+# 29.62 # A quoi servent les commandes savebox ?
+------------------------------------------------
+Il existe les commandes :
++ \newsavebox{ma_boite} pour dclarer une bote
++ \sbox{ma_boite}{contenu} pour remplir ma_boite
++ \savebox{ma_boite}[lagr][pos]{contenu} pour remplir une
+bote de largeur lagr et de position pos
++ \usebox{ma_boite} pour appeler le contenu de ma_boite
++ lrbox est l'environnement quivalent sbox
+
+Exemple :
+\newsavebox{\maboite}
+\sbox{\maboite}{\textbf{Alcatel Alsthom Recherche}}
+\usebox{maboite} se situe Marcoussis. Je travaille
+\usebox{maboite} depuis~\ldots...
+%%%% fin exemple %%%%
+
+# 29.63 # Comment rsoudre certaines incompatibilits de packages ?
+-------------------------------------------------------------------
+Il arrive parfois lorsque plusieurs packages sont utiliss
+simultanment que des macros diffrentes portent le mme nom, ou
+que certaines macros perturbent le fonctionnement d'autres
+macros. Dans certains cas le problme peut se rsoudre en
+changeant l'ordre d'appel des packages.
+
+Exemple (J.P. Drucbert) :
+Le paquetage psboxit dfinit des commandes \psboxit qui
+engendrent \special{ps: ...}. Le problme vient de ce
+deux-points. Si vous chargez psboxit.sty AVANT babel (option
+french), pas de problme, le deux-points est un caractre
+ordinaire (other) lors de la dclaration de la macro \psboxit et
+donc le \special crira bien un ":".
+
+Par contre si psboxit.sty est charg APRES babel (option
+french), le deux-points est alors un caractre actif au moment
+de la dclaration de la macro \psboxit, et le \special n'crira
+pas un deux-points, mais un espace inscable (en fait une macro
+interne de babel) et un :, d'o les erreurs. C'est un cas
+classique de catcodes pas trs bien grs (en fait psboxit.sty
+devrait sauver le catcode de : , donner la catgorie other au
+caractre :, dfinir \psboxit, puis restaurer le catcode).
+%%%% fin exemple %%%%
+
+# 29.64 # Qu'est ce que Lollipop ?
+----------------------------------
+C'est un jeu de macro de V. Eijkhout, destin faciliter
+l'criture de macros TeX. Il est disponible sur
+ftp://ftp.fdn.org/pub/CTAN/macros/lollipop/.
+
+# 29.65 # J'ai un problme avec babel !
+---------------------------------------
+En tentant d'utiliser babel, j'obtiens l'erreur suivante:
+
+! Undefined control sequence.
+\add@accent ...l \mathchardef \accent@spacefactor
+ \spacefactor }\accent #1 #...
+l.3 \begin{document}
+
+Le problme est connu et a t corrig par babel le 19 aot 1999. Si vous ne
+pouvez pas mettre jour votre paquetage de babel, utilisez le cache-bogue
+suivant, mettre dans le prambule (donation de Javier Bezos):
+
+\makeatletter
+\let\accent@spacefactor\relax
+\makeatother
+
+Vous pouvez galement ajouter la ligne suivante dans vos enttes:
+\usepackage{t1enc}
+
+En effet, le problme ne se manifeste pas en codage T1.
+
+# 29.66 # Qu'est ce que cette FAQ ?
+-----------------------------------
+- quelques 660 url, dont:
+ - plus de 390 url sur ctan;
+ - et quelques 270 url externes;
+- quelques litres de caf;
+- beaucoup de sueur;
+- de nombreux CDs uss.
+================================================================
+[30] REMERCIEMENTS ET CONTRIBUTIONS
+================================================================
+
+Je [mpk] remercie vivement les personnes qui ont contribu de prs
+ou de loin l'laboration de cette FAQ. Je remercie galement
+les personnes qui me soutiennent et m'encouragent.
+
+Je [bb] tiens remercier les personnes qui m'ont envoy des patchs
+ou des correctifs sur cette faq, et qui ont vrai dire beaucoup
+plus travaill que moi.
+
+La liste des contributions ci-aprs se veut aussi complte que
+possible. Si vous avez t oubli, n'hsitez pas me contacter.
+
+Contributions [ depuis le 15/07/99 ]
+- Arnaud Launay
+- Antoine Chambert-Loir
+- Maurice Diamantini
+- Philippe Pham
+- Frdric Petit
+- Jean-Dominique Orvoen
+- ric Depardieu
+- Benot Rivet
+- Nadine Manset
+- Nicolas Corrard
+- Denis Roegel
+- Julien Mudry
+- Franois Lesage
+- Vincent Lefvre
+- Jean Dezert
+- Stphane Pion
+- Jean-Baptiste Marchand
+- Andr Allavena
+
+--
+Benjamin Bayart
+bayartb@edgard.fdn.fr
diff --git a/help/comp-fonts-FAQ/Finding_Fonts_for_Internationalization_FAQ b/help/comp-fonts-FAQ/Finding_Fonts_for_Internationalization_FAQ
new file mode 100644
index 0000000000..1828a35505
--- /dev/null
+++ b/help/comp-fonts-FAQ/Finding_Fonts_for_Internationalization_FAQ
@@ -0,0 +1,614 @@
+Path: senator-bedfellow.mit.edu!faqserv
+From: mike@vlsivie.tuwien.ac.at
+Newsgroups: comp.std.internat,comp.software.international,comp.fonts,comp.windows.x,comp.os.ms-windows.programmer.misc,comp.answers,news.answers
+Subject: Finding Fonts for Internationalization FAQ
+Supersedes: <internationalization/font-faq_883655130@rtfm.mit.edu>
+Followup-To: comp.std.internat,comp.software.international,comp.fonts,comp.windows.x,comp.os.ms-windows.programmer.misc
+Date: 30 Jan 1998 11:16:52 GMT
+Organization: TU Wien
+Lines: 595
+Approved: news-answers-request@MIT.EDU
+Expires: 13 Mar 1998 11:15:31 GMT
+Message-ID: <internationalization/font-faq_886158931@rtfm.mit.edu>
+NNTP-Posting-Host: penguin-lust.mit.edu
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+Summary: This FAQ discusses finding fonts for various character sets.
+X-Last-Updated: 1997/01/15
+Originator: faqserv@penguin-lust.MIT.EDU
+Xref: senator-bedfellow.mit.edu comp.std.internat:7638 comp.software.international:6800 comp.fonts:70480 comp.windows.x:120738 comp.os.ms-windows.programmer.misc:133372 comp.answers:29876 news.answers:122020
+
+Archive-name: internationalization/font-faq
+Posting-Frequency: monthly
+Version: 0.5
+
+ International Fonts,
+ Fonts for ISO 8859-X
+
+
+
+DISCLAIMER: THE AUTHOR MAKES NO WARRANTY OF ANY KIND WITH REGARD TO
+THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+
+If you have any further information about *free* fonts which may be
+useful to others, please use the following URL to add a font to the
+FAQ
+ http://www.vlsivie.tuwien.ac.at/mike/fonts
+
+Please try to fill out the form as accurately as you can!
+
+This document only covers fonts which are available free of charge,
+via the internet. This is NOT a free advertisement for commercial
+font founderies. (So if you are a commercial foundery, don't bother
+me about including pointers to your commercial products!)
+
+Unfortunately archives move a lot, appear or disappear. I cannot keep
+track of everything, so please let me know if you find errors. Also,
+since the material changes so often, formatting is not always up to
+snuff. (This is distributed in the hope that it will be useful, not to
+win any editing prizes...)
+
+1. Which coding should I use for accented characters?
+Use the internationally standardized ISO-8859-X character sets to type
+accented characters.
+
+8859-1 is also used by MS-Windows (Actually, MS-Windows
+uses UNICODE (ISO 10646) truncated to 8 bit, which gives an equivalent
+encoding.), VMS and (practically all) UNIX implementations. MS-DOS
+uses a different character set and is not compatible with this
+character set. (It can, however, be translated to this format with
+various tools. See section 7.)
+
+ISO 8859-1 supports the following languages:
+Afrikaans, Catalan, Danish, Dutch, English, Faeroese, Finnish, French,
+German, Galician, Irish, Icelandic, Italian, Norwegian, Portuguese,
+Spanish and Swedish.
+
+(It has been called to my attention that Albanian can be written with
+ISO 8859-1 also. However, from a standards point of view, ISO 8859-2
+is the appropriate character set for Balkan countries.)
+
+ISO 8859-1 is just one part of the ISO-8859 standard, which specifies
+several character sets, e.g.:
+8859-1 Europe, Latin America
+8859-2 Eastern Europe
+8859-3 SE Europe
+8859-4 Scandinavia (mostly covered by 8859-1 also)
+8859-5 Cyrillic
+8859-6 Arabic
+8859-7 Greek
+8859-8 Hebrew
+8859-9 Latin5, same as 8859-1 except for Turkish instead of Icelandic
+8859-10 Latin6, for Eskimo/Scandinavian languages
+
+For an overview of these fonts, see
+http://www.cs.tu-berlin.de/~czyborra/charsets/
+
+
+
+2. Font conversions
+
+Most of the font formats discussed here can be converted to the other
+formats in this FAQ. For information on how to achieve this check out
+the font FAQ posted regularly in comp.fonts and the comp.font www
+home page at http://jasper.ora.com:8080/comp.fonts.
+
+
+
+3. Availability for the X Window System
+
+An overview of the ISO 8859-X fonts is available at
+http://www.cs.tu-berlin.de/~czyborra/charsets. You can also down-load
+these fonts as bdf fonts to install on your X window system.
+
+8859-1
+X Windows has several ISO 8859-1 character sets in the standard
+distribution (those whose names end in iso8859-1). If you are using
+X11R5, note that some fonts are labeled as ISO compliant fonts which
+they are not.
+
+
+8859-2
+The X11R6 release contains a font for this cxharacter set. More fonts
+can be found at URLs
+<ftp://ftp.vszbr.cz/pub/X11-fonts/ISO_8859-2> X11
+<ftp://ftp.tarki.hu/pub/font/> various operation systems
+<ftp://almos.vein.hu/ssa/kbd_es_font/> mostly Unix/X11
+<ftp://ftp.vma.bme.hu/pub/ssa/kbd_es_font/> (mirror of almos)
+<ftp://ftp.tarki.hu/pub/ssa/kbd_es_font/> mostly Unix/X11
+
+ftp://ftp.vse.cz/pub/386-unix/linux/Czech/czech-0.12.tar.gz has X
+fonts for 8859-2 and Linux support for the Czech language.
+
+
+8859-3
+You can find fonts for 8859-3 at URL
+ftp://ftp.stack.urc.tue.nl/pub/esperanto/fonts.dir. Not all the fonts
+are Latin-3. At least "adobe3.tar.gz" and "l3-tiparoj.tar.gz" contain
+Latin-3 BDF fonts.
+
+Also, there are fonts at URL
+ftp://ftp.vszbr.cz/pub/X11-fonts/ISO_8859-3.
+
+
+8859-4 through 8859-10
+You can find fonts for these character sets at URL
+ftp://ftp.vszbr.cz/pub/X11-fonts.
+
+
+8859-5
+Check out the ftp://nic.funet.fi/pub/culture/russian/comp/fonts
+(esp. subdirectories .../fonts and .../xwin). It has a host of
+Russian fonts. Also, check out the fonts in
+ftp://cs.umd.edu/pub/cyrillic/xwin_fonts. This archive contains ISO
+8859-5, Koi8 and Alt fonts (Alt is very popular on PCs.). If you use
+emacs, russian.el allows you to use one font for the buffer and
+another for the display.
+More fonts for Cyrillic scripts can be found at
+http://www.crec.mipt.ru/russify/index.html
+
+
+8859-6
+ISO 8859-6 fonts (insofar as glyph-encoded fonts can represent an
+abstract character set) are available from ftp://leb.net/pub/reader/unix/fonts.
+
+
+8859-7
+a set of Helvetica and Courier fonts can be found at
+ftp://ftp.ntua.gr/pub/fonts/X11.
+
+Additional Unix fonts for Greek are available via
+http://www.hri.org/fonts/unix
+
+
+8859-8
+Several fonts for this character set family can be found in the
+metamail package. The `metamail' package is available via anonymous
+ftp from thumper.bellcore.com in /pub/nsb. These fonts are in bdf
+format and can be found in <metamail-root>/src/fonts. You will also
+need software which supports right-to-left writing, such as the MULE
+system for emacs. Information about MULE can be found on
+ftp.vlsivie.tuwien.ac.at in /pub/8bit/MULE.
+
+Fonts can also be found at
+http://ourworld.compuserve.com/homepages/Jonathan_Rosenne/hebfont.htm
+
+
+8859-10
+There are a couple versions of an ISO_8859-10 font for X, the first
+version of which was based on the ECMA-144 standard and its depictions
+of the characters. The second version of this font was a revision of
+the first to improve the appearance of certain accented characters,
+and to modify the appearance of some of the Latin-6-specific characters
+to reflect their appearances from what printed material the author
+could find.
+
+ Both of these BDF font files can be found by anonymous FTP
+ftp://ccsun.tuke.sk/pub/
+
+These fonts should also end up at the X Consortium ftp server
+eventually.
+
+
+
+Other Fonts
+
+Languages Character set Font
+Thai TIS620 <MULE-root>/fonts/ETL.tar.gz
+Vietnamese VISCII ftp://media.mit.edu/pub/Vietnet/Viscii/Unix/X.tar.Z
+Vietnamese VISCII <MULE-root>/fonts/ETL.tar.gz
+Arabic MULE-ETL <MULE-root>/fonts/ETL.tar.gz
+Persian MULE-ETL <MULE-root>/fonts/ETL.tar.gz
+Persian ? ftp://tehran.stanford.edu
+IPA MULE-ETL <MULE-root>/fonts/ETL.tar.gz
+
+MULE-ETL is a MULE-specific character set, IPA stands for
+International Phonetic Alphabet. <MULE-root> refers to the root where
+you have installed MULE (MULE is a MULtilingual Enhancement to GNU
+Emacs). More information on MULE and the MULE package can be found on
+ftp://etlport.etl.go.jp/pub/mule.
+
+
+
+4. DOS
+IBM code page 819 is the same as ISO 8859-1. I believe that 850 is the
+code page that has all of the characters in different positions.
+
+IBM code page 912 is the same as ISO 8859-2, but 852 is the one that
+comes with (all versions of) DOS, which has all of ISO 8859-2's
+characters in different positions.
+
+
+Alternatively, you can reconfigure your MS-DOS PC to use publicly
+available, free ISO-8859-X code pages. Check out the anonymous ftp
+archive ftp.uni-erlangen.de, which contains data on how to do this
+(and other ISO-related stuff) in /pub/doc/ISO/charsets. The README
+file contains an index of the files you need.
+
+
+
+5. MS-Windows
+
+There are different Windows code pages, just as there are different
+DOS code pages. The one used for western European languages is 1252,
+which is a superset of ISO 8859-1 (1252 makes use of the control
+characters from 0x80 to 0x9F). Similarly, 1250 is a superset of ISO
+8859-2. (Some characters actually seem to have changed character code
+position, so it is not fully compatible!)
+
+" Unfortunately, there are significant diffrences between ISO 8859-2
+and the Windoze CP1250. While most of the characters are identical,
+there are maybe a dozen that appear in different positions in CP1250
+when viewing an iso-8859-2-encoded text, so once cannot say that it is
+truly a superset -- some translations still need to be done.
+
+ The problem will be noticed if using, say, Netscape2.x for Windows
+and viewing a page which is delivered with ISO-8859-2 MIME charset tagging,
+when one has selected a CE (CP1250) font. The present beta versions of
+Netscape2.0 do not incorporate translation, nor do they recognize any
+Central European MIME charsets other than ISO-8859-2 and an unregistered
+Mac charset."
+
+There are also versions for Arabic, Greek, Hebrew, and Turkish,
+corresponding to ISO 8859-6, -7, -8, and -9. (The encoding of
+Cyrillic may be non-ISO-8859.)
+
+Latin-3
+"ftp://ftp.stack.urc.tue.nl/pub/esperanto/fonts.dir/lat3pttf.zip"
+contains several TTF fonts in Latin-3, as well as some keyboard
+utilities for MS-Windows.
+
+Greek Fonts
+http://www.hri.org/fonts This is part of the Hellenic Resources
+Network web site and contains a host of information and free
+material(fonts, software) for use with Greek character sets.
+
+Hebrew fonts (8859-8)
+http://www1.snunit.k12.il/heb.html
+http://ourworld.compuserve.com/homepages/Jonathan_Rosenne/hebfont.htm
+
+IPA International Phonetic Alphabet fonts
+ftp.sil.org will get you to the Summer Institute of Linguistics, who
+have IPA fonts in both T1 and TT.
+
+
+Various fonts
+ftp.uni-paderborn.de:/pub/windows/Cica/demo/accentwm.zip
+
+This is a demo version of Accent. But after installing (and deleting)
+the demo you still have four TrueType fonts: East European (Latin 2),
+Greek, Cyrillic, Turkish (Latin 5).
+
+
+Geaorgian Fonts
+http://www.clinet.fi/~bpg/grfntdoc.html
+
+Tibetan Font & Keyboard Software for PC's
+(Christopher J Fynn <cfynn@sahaja.demon.co.uk>)
+My TibKey software (a context sensitive Tibetan Keyboard for
+Windows 3.1x and '95), and one of my Tibetan fonts in TrueType
+format, along with associated documentation can be found at:
+
+ftp://coombs.anu.edu.au/coombspapers/otherarchives/
+asian-studies-archives/tibetan-archives/tibet-software/
+tibkey-windows/zipped/TIBKEY.ZIP
+
+ftp://unix.hensa.ac.uk/mirrors/uunet/doc/papers/coombspapers/
+otherarchives/asian-studies-archives/tibetan-archives/
+tibet-software/tibkey-windows/zipped/TIBKEY.ZIP
+
+ftp://ftp.niif.spb.su/pub/tibet/software/windows/tibkey10.zip
+
+This software and font will allow you to enter Tibetan in most
+Windows applications. Freeware.
+
+
+Bengali Font
+A shareware Bengali TrueType font for Windows, available by FTP is at
+URL ftp://ftp.cica.indiana.edu/pub/pc/win3/fonts/sgaon.zip
+
+
+Indic Languages
+Roman Fonts with diacritics for transliterating Indic languages
+(Hindi, Sanskrit, Nepali, Bengali, etc., etc.):
+
+1.===
+> I have spent some hours recently making up a CS (Computer
+> Sanskrit) version of Adobe's font "Utopia". It is quite a nice
+> font, perhaps a little more of a "book-face" than the Bitstream
+> Charter that has been available for some time in CS encoding.
+>
+> The Utopia font is a professionally designed typeface which has
+> been officially released by Adobe Inc. for free distribution.
+>
+> I have made the following files available:
+>
+> adobe-utopia-font-CS-encoding-PS-10.zip
+> adobe-utopia-font-CS-encoding-PS-10.readme
+> and
+> adobe-utopia-font-CS-encoding-TTF-10.zip
+> adobe-utopia-font-CS-encoding-TTF-10.readme
+> adobe-utopia-font-CS-encoding-TTF-10.readme
+>
+> by anonymous ftp from
+> ftp.bcc.ac.uk in /pub/users/ucgadkw/indology/software
+>
+> or via your web browser at URL
+> http://www.ucl.ac.uk/~ucgadkw/indology.html
+> (follow the links to INDOLOGY supplementary gopher -- software)
+
+2. ===
+
+> ftp://ftp.shore.net/members/india/
+>
+> In the fonts directory you will be able to find Bitstream Charter
+> in Postscript (type 1) format, and some Macintosh True Type Fonts with
+> all the diacritics for Devanagari.
+
+
+
+Pinyin Fonts for Windows
+Pinyin TT fonts are availble at
+http://www.ucalgary.ca/~pcchang/dchu/font/index.html
+
+
+Egyptian Hieroglyphics
+There is a computer-assisted Egyptology centre at the University of
+Utrecht's Faculty of Theology. They have a WWW site offering
+hieroglyphics fonts for both Mac and PC (TrueType). About 900 glyphs
+are included. Their URL is http://131.211.68.206/ccer/ccer.htm
+
+
+Vietnamese
+VISCII TrueType/Type1 in ftp://media.mit/edu/pub/Vietnet/Viscii/Win3/
+(vnfont1.zip, vnfont2.zip, t1font1x.exe, pdfot1.zip ...)
+ftp://coombs.anu.edu.au/coombspapers/otherarchives/asian-studies-archives/vietnam-archives/viet-lang-software/viet-fonts/mit-viet-fonts/
+ftp://unix.hensa.ac.uk/mirrors/uunet/doc/papers/coombspapers/otherarchives/asian-studies-archives/vietnam-archives/viet-lang-software/viet-fonts/mit-viet-fonts/
+
+
+Cyrillic
+http://www.cica.indiana.edu/cgi-bin/checkftp or
+ftp://ftp.cica.indiana.edu
+ftp://oak.oakland.edu/win3/fonts
+ftp://ftp.techno.ru/pub/msdos/koi8/
+http://sunsite.oit.unc.edu/sergei/cysoft.html
+http://www.pitt.edu/~mapst57/rus/russian.html
+
+
+Chinese True Type
+
+unknown encoding and whether simplified/traditional:
+ftp://oanet1.csie.ntu.edu.tw/ntuttf/CHINESE/NTU_FS.ZIP
+ftp://oanet1.csie.ntu.edu.tw/ntuttf/CHINESE/NTU_KAI.ZIP
+ftp://oanet1.csie.ntu.edu.tw/ntuttf/CHINESE/NTU_LI.ZIP
+ftp://oanet1.csie.ntu.edu.tw/ntuttf/CHINESE/NTU_TW.ZIP
+
+these are traditional Chinese for the Mac encoded in BIG5
+ftp://ftp.nctu.edu.tw//Chinese/ifcss/software/fonts/big5/mac/...
+ .../NTU_black_medium.sit.bin.gz
+ .../NTU_funSung.sit.bin.gz
+ .../NTU_kai.sit.bin.gz
+ .../NTU_lei.sit.bin.gz
+ .../NTU_ming_medium.sit.bin.gz
+ .../NTU_round_heavy.sit.bin.gz
+ .../NTU_round_medium.sit.bin.gz
+ .../NTU_thin.sit.bin.gz
+
+Korean (Hangul) Type 1 font
+http://shiva.snu.ac.kr/~setup/index.html
+also has a hangul to PS converter (h2ps)
+
+ftp://ftp.kaist.ac.kr/pub/hangul/font has an extensive set of X11 and
+PS fonts. At the same archive, there's another Hangul to PS translator
+hpscat in /incoming/hangul and /pub/hangul/print.(KAIST archive is
+mirrored at ftp://under3.kisa.org in the US,ftp://ftp.nuri.net in Korea
+and ftp://ftp.linguistik.uni-erlangen.de/pub/Hangul in Germany). Hangul
+fonts for TeX are available at CTAN archives(e.g ftp://ftp.dante.de and
+ftp://ftp.ctan.ac.uk) throughout the world in ~ctan-archive/font/korean
+where there are PS,metafont and PK images of several typefaces. 31 sets
+of Hangul fonts for TeX are also available at ftp://math-ftp.kaist.ac.kr
+(mirrored at ftp://ftp.kaist.ac.kr/pub/hangul/tex/htex ). On top
+of that, X11 R5 or later comes with three Hangul fonts in BDF format.
+
+
+Others
+Check out the Yamada library on http://babel.uoregon.edu/
+
+
+6. Printing
+
+6.1 Adobe PS fonts
+
+To print text files on Postscript printers, you first have to
+translate them to Postscript programs. A number of utility programs
+exist which can perform this job.
+
+A very popular filter to perform this job is a2ps, which support files
+in ISO 8859-1 encoding when invoked with the -8 switch. There are a
+number of variants fopund on the net which support other encodings,
+such as Cyrillic.
+
+An alternative is to use the GNU enscript (genscript) program, which
+supports multiple character sets in one binary. genscript is found
+on the GNU mirror next to you.
+
+Alas, these filters rely on your Postscript fonts containing all the
+right characters. While most any font available today supports the
+full Latin1 set, East Block users are less fortunate. Most fonts
+found in printers do not support all their special characters. Two
+solutions exist:
+
+* you can download a font which does support all the right characters
+(the IBM Courier font which is publically available (e.g., in the
+X11R6 distributio contains all the required characters)
+
+* or you can assemble your own special characters. Note that most any
+Adobe font contains all the required accents marks, so all you have to
+do is tell the printer to put the right accent mark on the right
+character....
+
+So far, so good. The principle is simple though the job does require
+considerable Postscript experience if you have to start from scratch.
+Alternatively, you can pick up all the tools you need to assemble your
+very own font from ftp://ftp.dcs.ed.ac.uk/pub/jec/programs/ogonkify.tar.gz
+which will take care of all the low-level Postscript stuff so that
+indeed all you have to say is how to put what accent mark where.
+
+6.1.1 IPA Adobe Type1
+* IPA fonts can be found on ftp://ftp.sil.org
+
+
+6.2 Printing with MULE
+To print various characters supported by Mule, we provide a
+program `m2ps' which will be installed automatically while
+installing mule (just as etags, emacsclient). `m2ps'
+converts Mule's text to PostScript by using BDF files for
+getting glyphs of characters.
+
+This utility allows printing of all character sets supported by either
+your X11 distribution or found in the MULE distribution.
+
+
+
+7. Latex
+
+For ISO 8859-1, you should use the inputenv package with the latin1
+option:
+\usepackage[latin1]{inputenc}
+
+If you use pre 2e version of Latex, use isolatin.sty or isolatin1.sty
+instead. These are available from URL
+ftp://ftp.vlsivie.tuwien.ac.at/pub/8bit.
+
+The ISO 8859-2 character set (ex-East Block), is supported by
+`latin2.sty': latin2.sty is available by ftp from the host
+ftp.uni-stuttgart.de as `/pub/tex/macros/latex/contrib/latin2.sty'.
+
+
+If you need a Fraktur font, check out
+ftp://ftp.vlsivie.tuwien.ac.at/pub/tex/fraktur which contains a TeX/MF
+fraktur font.
+
+Vietnamese VISCII
+At ftp://media.mit.edu/pub/Vietnet/Viscii/Unix/...
+(Also contains groff fonts in .../groff_font.tar.Z)
+
+
+
+8. ISO 10646
+Everson Mono is a simple, elegant, monowidth font. I designed it
+primarily to make glyphs available in support of _all_ the non-Han
+characters in the Basic Multilingual Plane of ISO/IEC 10646-1
+(BMP = Unicode, if you prefer), though I hope that users may find
+it a pleasant alternative to Courier and Monaco for general
+purposes, e-mail, and so forth. I have found it quite legible at
+sizes as small as 4 points. It is lighter and a bit looser than
+Courier.
+
+At the present time, these glyphs are available in 8-bit font
+modules. However, I have configured the font editor I use (Altsys'
+excellent Fontographer) to output TrueType fonts with correct
+16-bit hex addresses, and the PostScript fonts with name unique,
+unambiguous aliases to 10646. The first half of each fonts is
+ASCII (Table 1, Basic Latin); I have had to resort to this
+(arguably wasteful) method of encoding because many applications
+display a font in its own face, rather than simply by name,
+potentially rendering the font name illegible. As 16-bit
+compatible technology becomes more available, I will be reencoding
+these glyphs to more convenient formats. (On the other hand, you
+could consider all these to be micro-subsets of 10646, and since
+subsets have to include Table 1, they're all conformant....)
+
+Everson Mono is also available in all Macintosh character set
+formats, suitable for use with Apple's WorldScript technology.
+
+Everson Mono is available as PostScript and TrueType fonts in
+Macintosh and PC formats, and as PostScript fonts in NeXT and Sun
+formats. Hand-tooled bitmaps for alphabetic characters are
+available in 9-, 10-, and 12-point sizes; hand-tooled 12-point
+bitmaps only may be available for some of the symbol characters.
+
+Everson Mono fonts are available by anonymous ftp at:
+
+dkuug.dk /CEN/TC304/EversonMono10646
+midir.ucd.ie /mgunn/everson/EversonMono10646
+ftp.nada.kth.se /pub/i18n/ucs/EversonMono10646
+
+The most current version will always be on the Danish server.
+
+As of this announcement (1995-06-05) only the Macintosh (TT/PS),
+NeXT (PS), and Sun (PS) formats are available. The PC (TT/PS)
+fonts are not yet available because I am still trying to figure
+out just how the draconian xxxxxxxx.yyy naming conventions are
+supposed to work for all these outline and bitmap files. I will
+upload them as soon as I can. After that then each set of new
+Everson Mono fonts will be uploaded in all four formats.
+
+Another Unicode char set is at
+ftp://ftp.ifcss.org/pub/software/fonts/unicode/bdf/uni16m.bdf.gz
+
+
+USE
+xfed, bdftopcf, mkfontdir, fs, xset fp+ [fontpath], xset fp rehash
+
+SEE ALSO
+http://www.iss.nus.sg/RND/MLP/Projects/MASS/ftp_index.html
+ftp://ifcss.org/pub/software/fonts/unicode/bdf/
+http://www.stonehand.com/unicode.html
+
+
+9. Character Set Names
+A list of official character set names (for MIME and other internet
+purposes) can be found as RFC 1345 on ftp.uu.net.
+
+
+
+10. Other sources for fonts
+The Multiplingual PC Directory discusses internet font sites under URL
+http://www.knowledge.co.uk/xxx/mpcdir/inetsite.htm. The fonts indexed
+there come in various fromats, but most can be adapted to whatever is
+needed by referring to the conversion methods described in the
+comp.fonts FAQ (URL http://jasper.ora.com:8080/comp.fonts).
+
+The Internet font archive is at
+http://jasper.ora.com/Internet-Font-Archive.html
+
+
+
+11. Home location
+11.1 www
+You can find this and other i18n documents under URL
+http://www.vlsivie.tuwien.ac.at/mike/i18n.html.
+
+The comp.fonts home page is at http://jasper.ora.com:8080/comp.fonts.
+
+11.2 ftp
+This document is available via anonymous ftp from
+ftp.vlsivie.tuwien.ac.at as /pub/8bit/i18n-fonts.
+
+
+-----------------
+
+Copyright 1994,1995,1996 Michael Gschwind (mike@vlsivie.tuwien.ac.at)
+
+This document may be copied for non-commercial purposes, provided this
+copyright notice appears. Publication in any other form requires the
+author's consent. (Distribution or publication with a product requires
+the author's consent, as does publication in any book, journal or
+other work.)
+
+Dieses Dokument darf unter Angabe dieser urheberrechtlichen
+Bestimmungen zum Zwecke der nicht-kommerziellen Nutzung beliebig
+vervielfltigt werden. Die Publikation in jeglicher anderer Form
+erfordert die Zustimmung des Autors. (Verteilung oder Publikation mit
+einem Produkt erfordert die Zustimmung des Autors, wie auch die
+Verffentlichung in Bchern, Zeitschriften, oder anderen Werken.)
+
+Michael Gschwind, PhD, Institut f. Technische Informatik, TU Wien
+snail: Treitlstrae 1-182-2 || A-1040 Wien || Austria
+email: mike@vlsivie.tuwien.ac.at PGP key available via www (or email)
+www : URL:http://www.vlsivie.tuwien.ac.at/mike/mike.html
+phone: +(43)(1)58801 8156 fax: +(43)(1)586 9697
+
diff --git a/help/comp-fonts-FAQ/[comp.text.tex]_Metafont:_All_fonts_available_in_.mf_format b/help/comp-fonts-FAQ/[comp.text.tex]_Metafont:_All_fonts_available_in_.mf_format
new file mode 100644
index 0000000000..ec0877539e
--- /dev/null
+++ b/help/comp-fonts-FAQ/[comp.text.tex]_Metafont:_All_fonts_available_in_.mf_format
@@ -0,0 +1,947 @@
+Newsgroups: comp.text.tex,comp.fonts,comp.answers,news.answers
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!newsxfer3.itd.umich.edu!news-peer.sprintlink.net!news-sea-19.sprintlink.net!news-in-west.sprintlink.net!news.sprintlink.net!Sprint!newsfeed.direct.ca!news.uunet.ca!gts!lethe!geac!sq!lee
+From: lee@sq.com (Liam Quin)
+Subject: [comp.text.tex] Metafont: All fonts available in .mf format
+Message-ID: <liamfaq-mf1-59@sq.com>
+Followup-To: poster
+Summary: .mf files are font outlines that you can use with mf to
+ generate pk or gf format TeX bitmap fonts.
+Supersedes: <liamfaq-mf1-58@sq.com>
+Reply-To: lee@sq.com (Liam R. E. Quin)
+Organization: SoftQuad Inc., Toronto, Canada
+Date: Thu, 24 Jul 1997 22:06:30 GMT
+Approved: news-answers-request@MIT.EDU
+Expires: Sun, 24 Aug 1997 02:49:16 GMT
+Lines: 931
+Xref: senator-bedfellow.mit.edu comp.text.tex:118789 comp.fonts:63880 comp.answers:27244 news.answers:108108
+
+Archive-name: fonts-faq/metafont-list
+Last-Modified: Mar 20 12:37
+
+Summary of Metafont Fonts Available (Approximate Digest Format)
+
+This list includes all known fonts available in metafont format, whether
+public domain or not. Archive sites for ftp are listed where known.
+There is also a BITNET archive at LISTSERV@UBVM.CC.BUFFALO.EDU.
+
+Please note that I don't use TeX, and can't answer questions about it.
+
+Many of the files are listed as being on a ctan archive.
+The CTAN servers are
+ ftp.dante.de (129.206.100.192), and
+ ftp.tex.ac.uk (128.232.1.87).
+
+These are mirrored at various places, although I don't have a list;
+README.mirrors in CTAN:/tex-archive is a good source.
+ South African Mirror: ftp.ee.up.ac.za
+ Please tell me (lee@sq.com) about others.
+
+There is no North American CTAN archive right now.
+Robin Fairbairns sent me the following note on behalf of the CTAN team:
+ I suggest you try ftp.cdrom.com instead; the CTAN root there is
+ /pub/tex/ctan; quote site index there doesn't work -- you'll have to
+ use ftp.tex.ac.uk or ftp.dante.de for that.
+
+ Rest assured that the CTAN team is trying very hard to find an
+ alternative CTAN site in N America.
+
+
+Note on BLACKBOX:
+ The blackbox archive has gone, but ftp.bcc.ac.uk is trying
+ to replace it, so try that machine.
+
+Finally, too many people have helped with this list to give individual
+acknowledgements -- or the file would be twice as large! -- but please
+do know that people's help is really appreciated.
+
+I always welcome additions to this list, although it may take me a while
+to add them to the list, I'm afraid. If you don't see your addition after
+a couple of months, please feel free to send it again!
+
+Subject: Contents
+
+ About Metafont International Phonetic Alphabet (IPA)
+ AMS Irish
+ APL Japanese
+ Arabic Klingon
+ Armenian Korean
+ ASCII Malayam
+ Astrological Malvern
+ Bar Code Mongolian
+ Blackboard Bold Music
+ Calligraphic OCR (Optical Character Recognition)
+ Chess Old English
+ Chinese Oriya
+ Cirth Pandora
+ Committee Pica
+ Computer Modern Pointing Hands
+ Concrete Punk
+ Courier Ransom
+ Croatian Glagolitic Recycle Symbol
+ Cyrillic Romanized Indic
+ Duerer Sanskrit
+ Devanagari Sauter
+ Dingbats Script
+ Euler Soyombo
+ Fraktur Symbol
+ Genealogy Tamil
+ Georgian Telegu
+ Greek Tengwar
+ Hebrew Thai
+ Helvetica Times
+ Hershey Unitary Beginners' Script
+ Hindi Vietnamese
+ Hieroglyphic Waldi Symbol Font
+
+
+Subject: About Metafont
+
+Metafont is a programming language for describing fonts. It was written
+by Donald Knuth and is documented in
+ Computers & Typesetting/C: The METAFONTbook
+ Knuth, Donald E.
+ Addison Wesley, 1986
+ ISBN 0-201-13445-4, or 0-201-13444-6 (soft cover)
+ Library access: Z250.8.M46K58, or 686.2'24, or 85-28675.
+
+A font written in Metafont is actually a computer program which, when run,
+will generate a bitmap (`raster') for a given typeface at a given size,
+for some particular device.
+
+In order to use a metafont format font, you'll need to have metafont, or
+a program such as mf2ps. See the comp.fonts FAQ for more information.
+
+
+Subject: AMS
+
+The American Mathematical Society collection of Metafont fonts contains:
+[1] AMS Euler -- a calligraphic font, designed by Herman Zapf for the AMS.
+ It is designed for mathematical use, not as a text face. The fonts are
+ Fraktur, Script, Cursive (an upright italic), Math extension.
+ (see TUGboat Vol.10, No. 1)
+ Most of the Euler fonts use the plain base, not the cm base. You
+ should build these using virmf, or at least with a version of Metafont
+ that does not have cmbase pre-loaded. Any Errors reported when building
+ some of the samller sizes can be ignored. (see also under Euler)
+
+[2] AMS extra maths symbols (msam, msbm)
+
+[3] AMS computer modern extensions -- providing some of the CM fonts at
+ extra point-sizes.
+
+[4] AMS Cyrillic (this is the same as University of Washington Cyrillic)
+
+There is also some documentation.
+
+You can get them from the AMS directly:
+ftp: e-math.ams.org /pub/tex/amsfonts/sources
+ftp: e-math.ams.org /pub/tex/amsfonts/doc
+Any (infrequent) changes to these fonts happen on e-math first.
+
+ftp: CTAN in tex-archive/fonts/amsfonts
+
+
+Subject: APL
+
+Fonts for the APL (A Programming Language) programming language.
+
+These were described in tugboat (Vol 8 No. 3, pp.275-278)
+ftp: power.eee.ndsu.nodak.edu apl-tex-font/27-Jul-90
+
+ftp: ctan: tex-archive/fonts/apl/*
+ftp: power.eee.ndsu.nodak.edu apl-tex-font/27-Jul-90
+
+
+Subject: Arabic
+
+Prof. Klaus Lagally's <lagally@informatik.uni-stuttgart.de> ArabTeX is
+a LaTeX extension for high-quality arabic writing.
+
+ftp: ftp.informatik.uni-stuttgart.de
+ftp: ftp.dante.de
+ftp: ctan: pub/archive/language/arabtex/mfinput
+
+
+Subject: Armenian
+
+ftp: ctan: pub/archive/fonts/armenian/*
+
+
+Subject: ASCII
+
+The `ascii' font is based on the public domain Courier font donated by IBM to
+the X Consortium. This font contains the IBM graphics characters, which are
+in the first 32 positions, but covers only 7-bit ASCII. It was created by
+R. Ramasubramanian, R. W. D. Nickalls and M. A. Reed; see TUGboat Vol 15 No. 2.
+[there doesn't seem to be a .mf file for this, though]
+
+ftp: ctan: tex-archive/fonts/ascii/*
+
+
+Subject: Astrological
+
+Symbols for the planets and the signs of the zodiac.
+
+ftp: ctan: tex-archive/fonts/astro
+
+astrofonts.tar.Z contains several Metafont files from Lars Alexandersson
+<larsa@math.chalmers.se>.
+ftp: hilbert.maths.utas.edu.au
+
+See also Waldi Symbols
+
+
+Subject: Bar Code
+
+Dimitri Vulis's barcode font
+ftp: ctan: tex-archive/fonts/barcodes/barcodes.mf
+
+
+Subject: Blackboard Bold
+
+Used for Real Numbers (R), Natural, Complex, etc.
+ftp: labrea.stanford.edu pub/tex/fonts/bbb*.mf
+
+A set of capitals is included in the AMS symbol fonts (see AMS fonts).
+bbold.mf is Alan Jeffrey's blackboard bold font, and contains both
+upper and lower case.
+ftp: ctan: tex-archive/fonts/bbold/*
+
+There are serifed Blackbord bold fonts by D. Taupin, containing the full
+cm character set in
+ftp: ctan: tex-archive/fonts/bbm
+
+Olaf Kummer <kummer@informatik.uni-hamburg.de> wrote another
+Blackboard Bold font, intended to be very close in appearance to the
+original Computer Modern fonts. The characters have serifs.
+
+ftp: ctan: /pub/tex/fonts/doublestroke/*
+
+
+Subject: Calligraphic
+
+twcal is a calligraphic font with many ligatures and alternate letter-forms,
+and includes TeX macros.
+
+ftp: ftp.dante.de
+
+Subject: Chess
+
+ftp: ftp.cs.ruu.nl pub/TEX/chess.tar.Z
+by Piet Tutelaers; described in TUGboat.
+
+Some chess typesetting macros were posted to comp.tex.tex on July 31st 1990.
+ftp: ctan: tex-archive/fonts/chess/*
+
+There is also a font of pieces for chinese chess from
+mailto:richer@ERE.UMontreal.CA (Richer Jacques)
+
+
+Subject: Chinese
+
+Poor Man's TeX generates Chinese Metafont characters
+ftp: BLACKBOX (see introduction); cd pub/poorman (??)
+
+Poor Man's TeX Chinese has been extended to support Big5 format;
+pre-generated 300dpi Simplified and Traditional GB fonts are available for ftp.
+
+ftp: crl.nmsu.edu ; pub/misc/pmtex-1.1.tar.Z
+ftp: crl.nmsu.edu ; pub/chinese/fonts/pmt-{300dpi,tfm}
+
+ChTeX is a set of macros and fonts for typesetting Chinese under TeX.
+It only supports PostScript, and requires a modivied dvi2ps. You write
+your article with PinYin.
+Included are source, fonts, VMS binary for 5.2, DOS binary, etc. There is
+also support for X-Windows; contact mliesher@nmsu.edu (Mark Leisher).
+
+ftp: crl.nmsu.edu ; pub/chinese/{dvi2ps-3.2,ChTeX-1.1}.tar.Z
+ftp neon.stanford.edu ; ChTeX.tar.Z
+
+Subject: Cirth
+
+This is a Tolkien font based on Anglo-Saxon `Futharc' runes.
+Julian Bradfield has versions of both Tengwar [q.v.] and Cirth runes.
+
+ftp: ftp.dcs.ed.ac.uk export/jcb/Elvish.tar.Z
+ftp: (or the individual files instead in the same directory)
+Janet-niftp: uk.ac.ed.lfcs user=ftp pass=user80 export/jcb/Elvish.tar.Z
+ftp: They are also available for ftp on aston.
+
+There is also a cirth font by Jo Jaquinta, Trinity College, Dublin:
+
+ftp: lanczos.maths.tcd.ie jaymin/mf/cirth
+mail: info-serv@lanczos.maths.tcd.ie - send a one-line mail message containing
+mail: HELP in the text of the message. This may be called "infoserv" now.
+
+
+Subject: Committee
+
+This was produced during a workshop tutorial given by Donald Knuth.
+This is said (by Don Hosek, whom I trust in such things) to be hard-wired
+for the APS typesetter... It is described in Tugboat Vol. 5 No. 2 (Nov. 84).
+
+ftp: ctan: tex-archive/committee/*
+
+
+Subject: Computer Modern
+
+Computer Modern is Donald Knuth's font family used for his later
+`Art of Computer Programming' books. It contains
+ cmr -- computer modern roman
+ cmmi -- computer modern maths italic
+ cmti -- computer modern text italic
+ cmb -- computer modern bold
+ cmss -- computer modern sans serif
+ Cmtt -- computer modern typewriter
+ cmvtt -- computer modern variable-spaced typewriter
+and several variations on each of the above (e.g. bold extended...).
+There are also some experimental fonts, such as cmff, a `funny' font, and
+cmfib, a font based on Fibonacci numbers.
+
+These are all included in a standard TeX distribution.
+
+ftp: ctan: tex-archive/cm/mf/*
+There is also a very large and probably very complete collection in
+ftp: ctan: tex-archive/fonts/cm/*
+
+If all else fails, you can try:
+ftp: labrea.stanford.edu cd pub/tex/cm
+
+Many TeX ftp archive sites also give access to the bitmaps (pk files),
+although you usually have to get them all at once.
+
+There is also a reparameterised version of CM by John Sauter, which makes
+it easy to generate fonts at desired sizes-- this is especially useful for
+non-TeX users.
+
+ftp: ctan: tex-archive/cm/sauter/*
+See also: Sauter
+
+There is also a Pica typewriter font -- italic and bold come out with
+straight and wavy underlines (respectively), however. This is in
+ftp: ctan: tex-archive/fonts/cmpica/*
+
+Versions of these fonts suitable for use with an X Windows previewer (xtex
+and SeeTeX) are available from
+ftp: UNKNOWN [was foobar.colorado.edu] pub/SeeTeX
+
+A variant of CMTT with 8-bit characters for the Mac is available for US$20
+from yannis.haralambous@omega.citilille.fr -- this is called MACTT.
+Mf source is included. (Note: the price might be out of date!)
+
+
+Subject: Concrete
+
+This font was designed for Donald Knuth's Concrete Mathematics book.
+It looks a little like a cross between American Typewriter and Computer
+Modern Roman. There are Roman and Italic faces.
+
+See Tugboat Vol 10 No. 3, pp. 31-36, "typesetting concrete", by Don. Knuth;
+an erratum was published in Tugboat Vol 10 No. 3, p. 342.
+
+ftp: ctan: tex-archive/fonts/concrete/*
+
+
+Subject: Courier
+
+See Fonts: ASCII
+
+
+Subject: Croatian Glagolitic
+
+Darko Zubrinic <darko.zubrinic@etf.uni-zg.ac.mail.yu> described this in
+"The Exotic Croatian Glagolitic Alphabet" (TUGboat Vol. 13 No. 4 pp 470--471).
+See also Fonts: Cyrillic
+
+
+Subject: Cyrillic
+
+There are several Cyrillic (Russian-Alphabet) fonts:
+ Tom Ridgeway's Cyrillic fonts
+ WN-Cyrillic
+ ifve (which I'm told has better letterforms than WN but only
+ covers Russian)
+
+the wncy* fonts are part of the amsfonts package:
+ftp: e-math.ams.org:/ams/amsfonts/sources/cyrillic
+ftp: ctan: tex-archive/fonts/ams/amsfonts/sources/cyrillic/*
+
+There is a mailing list, rustex-l, for discussion of typesetting
+Cyrilic-based languages. To subscribe, send mail to listserv@ubvm.bitnet
+containing the text
+ SUBSCRIBE RUSTEX-L <your name here>
+or mail Dimitri Vulis, dlv@bwalk.dm.com
+
+Alexander Harin has put together a set of fonts using the alternative
+Russian font encoding, widely used on MS-DOS in Russia. This includes:
+[1] *.mf and *.tfm files for cmcyr fonts by A.Samarin and N.Glonti (modified);
+[2] Virtual fonts *.vf by A.Harin which have the standard TeX 7-bit encoding
+ and use the top half of the 8-bit space for the cmcyr fonts in the
+ alternative encoding, and
+[3] style macros.
+
+the fonts:
+ftp: ctan: tex-archive/fonts/cmcyralt
+
+the LaTeX 2.09 NFSS1 style:
+ftp: ctan: tex-archive/macros/latex209/contrib/cmcyralt
+
+the LaTeX 2e style:
+ftp: ctan: tex-archive/macros/latex/contrib/other/cmcyralt
+
+
+Subject: Duerer
+
+Based on the 16th Century drawings of Albrecht Duerer -- see, for example,
+his ``The Painter's Manual'' published in Fac Simile by Abaris Books, and
+reprinted in part by Dover as `On the Just Formation of Letters'.
+Hoenig's article was in TUGboat Vol 11 No. 14.
+
+Upper case letters only.
+
+ftp: ctan: tex-archive/fonts/duerer/*
+
+
+Subject: Devanagari
+
+(this is a font for use with Sanskrit, Hindi, etc.)
+Created by Frans Velthuis <velthuis@hgrrug5.bitnet> in 1987/88:
+ftp: ctan: tex-archive/language/devanagari/*
+
+Also available as part of his Devanagari transliteration package:
+ftp: june.cs.washington.edu tex/devnag.tar.Z, or devnag.zip
+
+You could also try, these, although I don't know if they are the same:
+ftp: BLACKBOX (see introduction):/pub/indic/outlines/vnagari.*
+
+
+Charles Wikner <WIKNER@nacdh4.nac.ac.za> SKT Sanskrit font:
+
+This is a complete Sanskrit font with accents, Vedic anusvaara,
+jihvaamuuliiya etc.; i-hooks connect to consonants correctly. Indic languages
+other than Sanskrit are not supported. The skt-series of fonts are written
+in METAFONT and include feint, normal and bold weights, together with
+slant and upright styles. It uses an ANSI-C pre-processor to convert the
+encoded input; the same encoding scheme is also used to provide two types of
+transliterated output, normal and technical. The font and supporting files
+are designed for use with LaTeX2e.
+
+ftp: ctan: tex-archive/language/sanskrit/*
+
+PostSript documentation is available together with samples:
+ftp: ftp.nacdh4.nac.ac.za/wikner/sktdoc.ps600.
+
+
+See Also: Fonts: Tamil, Romanized Indic
+
+
+Subject: Dingbats
+
+By Doug Henderson.
+ftp: ctan: tex-archive/fonts/dingbat/*
+See Also: Washington Symbol Font
+
+Eberhard Matthes' TeX for MSDOS (emTeX) has an additional font emsy, which
+contains a few (5 or so) Dingbats-type characters (e.g. a lock).
+
+
+Fonts: Ethiopian (Amharic, Geez)
+
+There is an Amharic font in Metafont. See TUGboat vol 10(3), p.352;
+You can find it in /tex-archive/lanaguges/ethiopia/ethtex/disk8.
+EthTeX is a package that enable users to typeset documents in Ethiopian
+Script and Ge'ez in additon to the standard features.
+
+ftp: ftp.shsu.edu; cd tex-archive/languages/ethiopia/ethtex
+ftp.tex.ac.uk; cd tex-archive/languages/ethiopia/ethtex
+ftp.dante.de; cd tex-archive/languages/ethiopia/ethtex
+
+
+Subject: Euler
+
+Designed by Herman Zapf for the American Mathematical Society (the AMS).
+
+ftp: e-math.ams.org /pub/tex/amsfonts/sources/euler
+
+See also: AMS
+
+
+Subject: Fraktur
+
+Yannis Haralambous' Gothic Fonts (described in TUGBoat 12.1) are in
+the following directories:
+ftp: ctan: tex-archive/fonts/gothic/yfrak
+ftp: ctan: tex-archive/fonts/gothic/ygoth
+ftp: ctan: tex-archive/fonts/gothic/yinit
+ftp: ctan: tex-archive/fonts/gothic/yinitas
+ftp: ctan: tex-archive/fonts/gothic/yswab
+
+See Also: Old English
+
+
+Subject: Genealogy
+
+`gen' : genealogy symbols, by Don Knuth
+
+ftp: CTAN systems/knuth/local/cm/gen10.mf
+
+`drgen' : genealogy symbols, by Denis B. Roegel <Denis.Roegel@loria.fr>
+
+ drgen has no original drawings, but gathers in one
+ font the symbols from Knuth's `gen' font, plus
+ some symbols from the `wasy' font (male and female).
+
+ftp: CTAN: fonts/genealogy
+
+
+Subject: Georgian
+
+Alan Stanier has written what he describes as a `rough version' of the
+mxedruli alphabet, as used in the Georgian Republic.
+ftp: ftp.tex.ac.uk; pub/archive/fonts/georgian
+
+A more plsished version was written by Johannes Heinecke and
+is in the same directory (?).
+
+
+Subject: Greek
+
+Brian Hamilton Kelly's Greek font:
+ftp: xydeco.siemens.com greek*
+
+Sylvio Levy's Greek font:
+ftp: CTAN tex-archives/fonts/greek/levy
+ftp: CTAN tex-archives/fonts/greek/yannis
+ftp: CTAN tex-archives/fonts/greek/kd
+(KD is the most comprehensive and is derived from Levy.)
+
+Also the Sylvio Levy `gr' greek family, for both Modern and Classical Greek.
+This includes roman, typewriter and bold, plus TeX macros.
+
+Brian Hamilton Kelly's cmgr family
+Yannis Haramboulos' rgr family
+
+ftp: UNKNOWN;
+
+James K. Tauber's Greek Metafont `MELANOS'
+
+Melanos differs from other Greek Metafonts in that the diacritics are placed
+after the letter they apply to, making it easier to use Greek texts based on
+the CATSS/CCAT/TLG system of transliteration. CATSS/CCAT/TLG files can be
+made compatible with MELANOS by changing "\" to "`" and "|" to "!"
+This (0.2) is still an early release with a simple mono-width sans
+serif style.
+
+ftp: tartarus.uwa.edu.au; cd /pub/jtauber/melanos
+
+
+see also Malvern
+
+
+Subject: Hebrew
+
+A number of Hebrew fonts are available, with and without vowels. Those
+include the fonts Jerusalem, TelAviv, OldJaffa and DeadSea, Joel M. Hoffman's
+HCLASSIC (joel@exc.com), Jacques Goldberg's REDIS, Shalom fonts and more.
+
+Some or all of the fonts are available in an 8-bit encoding; the Metafont
+files have names ending in "_newcode.mf". These are:
+Jerusalem, TelAviv, OldJaffa, DeadSea, redis{8,9,10,12,17}, rediss{8,9,10}.
+
+
+Jerusalem, TelAviv, OldJaffa and DeadSea are the "regular" fonts in most
+applications. Jerusalem is the default; DeadSea is a darker font; TelAviv is
+a sort of sans-serif font; OldJaffa is a narrow font.
+
+REDIS (redis*) contains a full set of Hebrew letters in a "sans-serif"
+style, and selected punctuation.
+
+Hclassic, dclassic, hcaption and dcaption have a companion slanted form, and
+provide Biblical-style letters along with full vocalization capabilities
+(i.e. vowels, called in Hebrew NIKUD). The fonts dclassic and dcaption are a
+modified version of hclassic and hcaption, in that they contain, apart from
+the original characters and vowels, also digits and special symbols copied
+from the font DeadSea.
+
+Usage is described in the guide classic_guide (available in noa.huji.ac.il
+in tex/tex_guides).
+
+ShalomScript10, ShalomStick10 and ShalomOldStyle10 are three variations of
+a Hebrew font with "vowels". Three fonts + vowels are available:
+ShalomScript10.mf, ShalomStick10.mf and ShalomOldStyle.mf.
+Usage is described in Shalom.readme.
+
+
+Carmel and carmel slanted (crml10, crmlsl10) are bold fonts written by
+Dr. Samy Zafrany of the Technion, Haifa, for headers and for emphasized text.
+
+All of the Hebrew fonts can be found at the archive for Hebrew TeX files:
+
+ftp: noa.huji.ac.il; cd tex/fonts
+
+
+Subject: Helvetica
+
+Produced by the Metafoundry and sold commercially.
+The Metafoundry is no longer extant, and the sources to these and their other
+fonts are not available. Email me if you need more information; Rick Tobin
+is on the net, but the connection is unreliable.
+
+Subject: Hershey
+
+The Hershey fonts were designed for use by plotters, and published in 1972.
+These fonts are of relatively low typographic quality, but are useful on
+devices with lower resolution.
+
+ftp: cs.uoregon.edu
+ftp: science.utah.edu
+
+There may be a Hershey to MF converter at mims-iris.waterloo.edu called
+xhershey. Ken Yap wrote it and `played around with a few novelty fonts
+before deciding the Hershey quality wasn't worth it,' he tells me.
+
+Subject: Hindi
+
+See Also: Fonts: Devanagari, Sanskrit, Tamil
+
+Subject: Hieroglyphic
+
+Created by Serge Rosmorduc (rosmord@inf.enst.fr).
+ftp: ftp.tex.ac.uk; directory /tex-archive/fonts/hieroglyph
+
+
+Subject: International Phonetic Alphabet (IPA)
+
+Used by linguists, and also in some dictionaries. It's designed to go
+with Computer Modern. From WSU.
+The csli version has been extended by Emma Pease (emma@csli.stanford.edu) to
+include hooked D, B and K, and probably more.
+
+ftp: ctan: tex-archive/fonts/tsipa/doc/*
+ftp: ctan: tex-archive/fonts/wsuipa/*
+ftp: cougar.csc.wsu.edu; directory: text1.wsuipa
+ftp: csli.stanford.edu; file: Phonetic.tar.Z
+
+There is a mailing list for linguists who use TeX: ling-tex-request@ifi.uio.no
+
+
+Subject: Irish
+
+Ivan A Derzhanski's Irish fonts:
+ftp: ftp.dante.de in /soft/tex/fonts/eiad; read file Leigh_me first.
+
+Jo Jaquinta's (half-?) Uncial
+ftp: clr.nmsu.edu in CLR/multiling/gaelic/fonts/half-uncial.tar.gZ
+ftp: ftp.cc.utexas.edu in source/tex/fonts/uncial
+
+
+
+Subject: Japanese
+
+Metafont for 61 Japanese fonts is available from many sources, including:
+
+ftp: SIMTEL (tenex) tex/jemtex2.zip
+ftp: wuarchive (binary) file mirrors/msdos/tex/jemtex2.zip
+ftp: utsun (binary) file TeX/jawatex/*
+
+Pregenerated Kanji fonts at 300dpi are available --
+ftp: crl.nmsu.edu ; pub/japanese/fonts/pmt-{tfm,300dpi}/*
+See Also: Fonts, Chinese
+
+
+Subject: Klingon
+
+This is a font from the television series `Star Trek', metafonted by
+Khoros sutai-Makpai
+c/o Karl Guenter Wuensch
+hz225wu@unidui.uni-duisburg.de
+(this account is shared with Micaela "Stayka" Pantke,
+so don't be alarmed if the mailer inserts her address)
+
+ftp: ftp.dante.de /pub/soft/tex/fonts/klinz/*
+
+Subject: Korean
+
+Poor Man's TeX (see under Fonts: Chinese) has been extended to support Hangul.
+Pregenerated fonts only are available:
+ftp: crl.nmsu.edu ; pub/korean/pmtex-korean-fonts.tar.Z
+
+See Also: Fonts, Chinese
+
+Subject: Malayam
+
+Malayalam-TeX is a package to typeset Malayalam with TeX (*), in both the
+traditional and reformed script. There's a free and a commercial version.
+The demo includes pk fonts at 300dpi, but not the .mf files. The commercial
+package costs DFL 75, which doesn't sound very much.
+
+ftp: archive.cs.ruu.nl:/pub/TEX/FONTS/MalayalamTeX-v1.0.tar.Z
+
+
+Subject: Malvern
+
+A sans-serif font by P. Damian Cugley (Damian.Cugley@comlab.ox.ac.uk).
+The latest version is 1.2 (October 1994).
+This family contains a sans-serif Greek alphabet, using
+conventions based on Levy's original Greek fonts and Dryllerakis' GreekTeX.
+The package includes support files for LaTeX 2e, LaTeX 2.09 and plain TeX.
+
+ftp: CTAN: tex-archive/fonts/malvern
+
+
+Subject: Mongolian
+
+Infosystem Mongolei distributes "Soyombo for LaTeX", together with an
+introduction to the Soyombo script still sometimes used in Mongolia.
+
+http://userpage.fu-berlin.de/~corff/im/Soyombo/overview.Soyombo.html
+
+
+Subject: Music
+
+MuTeX is a basic music package for TeX. It seems to be the same as mtex,
+but with documentation in English rather than (or as well as) German.
+
+ftp: stolaf.edu /pub/MuTeX.tar.Z /pub/MuTeX_doc.Z
+ftp: suned.zoo.cs.yale.edu [128.36.21]
+ftp: cs.ubc.edu src/MuTeX/MuTeX.tar.Z (slow)
+ftp: wuarchive.wustl.edu: /mirrors/msdos/tex/mutex.arc
+
+In Europe,
+ftp: ftp.cs.ruu.nl in subdirectory pub/TEX
+ftp: mtex.tar.Z (sources, including metafont sources and documentation)
+ftp: mtexfonts.tar.Z (300dpi pk files)
+These are also available in Europe by mail-server. Send mail to
+mail-server@cs.ruu.nl with HELP in the subject and the body and probably
+the .signature as well :-)
+
+MUSICTEX is another package with some more fonts, but French documentation
+ftp: 130.84.128.100 username-MUSICTEX password=ANY
+[I don't think this archive exists anymore..... -- Lee]
+
+This may or may not be the same as MusicTeX:
+ftp: qed.rice.edu pub/musictex.tar.Z
+
+
+Subject: OCR (Optical Character Recognition)
+
+OCR A (this is not the font for printing on cheques)
+ftp: ctan: tex-archive/fonts/ocr-a/*
+
+
+Subject: Old English
+
+Note On Terminology:
+ Old English is a language spoken by the Anglo-Saxons in Britain up
+ until the first half or so of the 12th century. It is used to refer
+ to fonts used for setting the Old English language.
+ The term `Old English' is also used to mean the Black Letter fonts
+ used by mediaeval scribes, and called Gothic. Unfortunately, some
+ American typefounding companies use `Gothic' to mean `sans-serif'.
+ Both the Anglo-Saxon character sets and the ornamental Black Letter
+ fonts are listed here.
+
+Julian Bradfield's font for typesetting Old English in TeX -- this supplies
+extra characters for Computer Modern. The extra characters are eth, Eth,
+Thorn, thorn, yogh, Yogh and Polish ogonek. There are two styles of thorn,
+but I note that there is no wynn. You may have to create an empty file, or
+rename a file -- I forget exactly what I had to do. Some of these characters
+can also be found in the International Phonetic Alphabet font as well, but
+Julian's are much more convenient for working with Old English.
+
+Yannis' Fraktur fonts include ygoth, which can be used as
+an Old English Black Letter.
+
+ftp: ctan: tex-archive/fonts/gothic/ygoth
+
+
+Subject: Oriya
+
+Sabita Panigrahi is working on Oriya (one of the modern Indian scripts),
+but this is not yet available.
+
+Subject: Pandora
+
+This is a little like Palatino, annd includes a sans-serif variant.
+It is not yet of production quality, unfortunately.
+
+ftp: gatekeeper.dec.com; cd tex82/MFcontrib/metafonts/pandora
+ftp: ctan: tex-archive/fonts/pandora/*
+mail: (N. N. Billawa) sun!metamarks!nm
+mail: (Tom Tatlow) tatlow@dash.enet.dec.com or tom@math.mit.edu
+
+Subject: Pica
+
+There is also a Pica typewriter font -- italic and bold come out with
+straight and wavy underlines (respectively), however.
+ftp: ctan: tex-archive/cmpica/*
+
+
+Subject: Pointing Hands
+
+Various manual extremities, designed by Georgia Tobin
+ftp: ctan: tex-archive/fonts/hands/*
+
+Subject: Punk
+
+A punK hAndWritten fOnT...
+For writing on walls, perhaps. The lower case is simply a smaller
+version of the upper case.
+ftp: ctan: tex-archive/fonts/punk/*
+
+Subject: Ransom
+
+This isn't a Metafont font, but you can get the gf, pk and tfm files at
+10.300 size from:
+ftp: ctan: tex-archive/fonts/ransom/*
+
+Subject: Recycle Symbol
+
+ftp: ctan: tex-archive/fonts/ransom/*
+
+Subject: Romanized Indic
+
+The font wnri by Tom Ridgeway can be found on
+ftp.bcc.ac.uk:/public/users/ucgadkw/indology
+
+See Also: Fonts: Devanagari
+
+
+Subject: Sanskrit
+(see Fonts: Devanagari; Fonts: Romanized Indic)
+
+
+Subject: Sauter
+
+This is a rework of Computer Modern by John Sauter. The outlines are the
+same, as far as I know, but it is much easier to generate the various fonts.
+
+ftp: ctan: tex-archive/cm/sauter/*
+
+
+Subject: Script
+
+Ralph Smith's formal script - rasmith@ucsd.edu
+See TeXhax 92 #16.
+ftp: ctan: tex-archive/fonts/rsfs/*
+
+Subject: Soyombo
+
+See Mongolian, above.
+
+
+Subject: Symbol
+
+There are varions fonts with special symbols, including:
+A recycling symbol:
+ftp: ctan: tex-archive/fonts/recycle/*
+
+The stmary symbol font:
+ftp: ctan: tex-archive/fonts/stmary/*
+
+
+
+Subject: Tamil
+
+(Tamil is an Indian script)
+An unfinished version of Washington Tamil is available from the University
+of Washington, and is included on their Unix TeX distribution in directory:
+TeX3.14/MFcontrib/metafonts/washington/tamil together with supporting software.
+ftp: BLACKBOX (see introduction) pub/wntml
+
+Avinash Chopde's (avinash@acm.org) ITRANS package (a pre-processor for TeX)
+supports Hindi, Marathi, Sanskrit (Devanagari), Tamil, Telugu, Bengali.
+It includes a PostScript (Type 3) font for Devanagari, and a Metafont Tamil
+font (wntml).
+ftp: Unix: cs.duke.edu in dist/sources/itrans32.tar.Z
+ftp: MS/DOS: oak.oakland.edu pub/msdos/tex/itrans32.zip
+ftp: PostScript printer ready docs are in itransps.tar.Z or itransps.zip.
+
+T. Govindaraj (tg@chmsr.gatech.edu) has created a Palladam Tamil font;
+ftp: isye.gatech.edu nights & weekends only
+Bala Swaminathan's Thiruppaavai files are also there.
+
+
+See Also: Devanagari, Oriya
+
+
+Subject: Telegu
+
+(Telegu is an Indian script)
+Andhra Pradesh, Lakshmankumar Mukkavilli and Lakshmi Mukkavilli's TeluguTeX
+includes a Telugu font in MF format and also a transliteration scheme for TeX.
+
+ftp: ctan: tex-archive/languages/telugu/
+ftp: ftp.cs.ruu.nl:/pub/TEX/FONTS/TeluguTeX.tar.gz
+
+
+Subject: Tengwar
+
+There are at least two Tengwar fonts,
+Mike Urban's:
+ftp: ctan: tex-archive/fonts/tengwar/*
+
+Julian Bradfield <jcb@lfcs.edinburgh.ac.uk> also has both Tengwar and a
+prototype version of Cirth runes.
+See Fonts: Cirth for details.
+
+Subject: Thai
+
+There are at least three Thai fonts around. The rmit font is a little tricky
+to make, as it needs to be in a directory called ``thai2'', because it
+refers to files called "../thai2/name". USL makes easily.
+The third Thai font is by Dr. Robert Batzinger and associates at the United
+Bible Societies in Southeast Asia. I know no more than this.
+
+ftp: ctan: tex-archive/fonts/thai/rmit/*
+ftp: ctan: tex-archive/fonts/thai/usl/*
+
+Subject: Times
+
+Formerly produced by the Metafoundry, which is no longer operating.
+Pk (binary) files may be available commercialy; Georgina Tobin works as a
+Metafont consultant and has since done more work on Times.
+See Also: Fonts: Helvetica
+
+Subject: Unitary Beginners' Script
+
+I know very little about this, sorry.
+ftp: tex-archive/fonts/va
+
+
+Subject: Vietnamese
+
+This test package includes tfm and pk fonts at 10 point roman and italic.
+I understand that you need TeX 3.0 or later to use this, and drivers that
+cope with fonts containing more than 128 characters.
+
+ftp: BLACKBOX (see introduction) cd /pub/testviet
+Since testviet is unavailable, you should probably look at viet-std instead:
+
+A large collection of Vietnamese Mf (and PK) fonts is available; these fonts
+follow the Viet-Std VISCII 1.1 font encoding specification.
+
+ftp: media.mit.edu, directory /pub/Vietnet/Viscii/Tex, files
+ftp: vncmr.pk.tar.Z and vncmr.mf.tar.Z; the encoding report is
+ftp: under /pub/Vietnet/Viet-std.
+
+Subject: Waldi Symbol Font
+
+A (compatible) superset of the standard LaTeX symbol font designed by Roland
+Waldi, at the University of Karlruhe in Germany.
+
+ftp: forwiss.uni-passau.de; pub/unix/text/TeX/dhdurz1/wasy.zoo
+ftp: ftp.cs.ruu.nl; ATARI-ST/tex/wasy.arc
+
+
+End of Font List
+
+$Id: mf1.faq,v 1.68 97/03/20 12:37:28 lee Exp $
+
+
+
+--
+Liam Quin | lq-text freely available Unix text retrieval
+liamquin at interlog.com | FAQs: Metafont fonts, OPEN LOOK UI, OpenWindows
+ | xfonttool (Unix xfontsel in XView)
++1 416 594 9646 (home) | the barefoot programmer
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Amiga_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Amiga_Info
new file mode 100644
index 0000000000..49ef248971
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Amiga_Info
@@ -0,0 +1,334 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Amiga Info
+Supersedes: <font-faq-13_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:18 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 311
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-13_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48310 comp.answers:20524 news.answers:79245
+
+Archive-name: fonts-faq/part13
+Version: 2.1.5
+
+Subject: 8. Amiga Information
+
+ Daniel Amor contributes the following sections:
+
+ Font Concepts
+ =============
+
+ The Amiga is able to use two different concepts of fonts. First of all
+ there are the bitmap fonts. These fonts are created by drawing a letter
+ pixel for pixel onto the screen. The advantage is that they look good
+ at small sizes, but are not very good for printout. Also they don't
+ look very good when you change their size. Therefore you have to
+ recreate the font for each size. Second there are the vector fonts.
+ They are created by curves which are stored as mathematical formula.
+ This has the advantage that changing the sizes does not effect the
+ output. But this only applies for larger sizes and print-outs. Vector
+ fonts also use less memory.
+
+ Amiga Font Formats
+ ==================
+
+ 1. Agfa IntelliFont (suffix: .type or .lib) is the native font format
+ on the Amiga. You can use it in any application and it can be
+ converted to the standard bitmap format using the system
+ utilities `IntelliFont' (OS 3.x) or `Fountain' (OS 2.x).
+
+ 2. Postscript Type 1 fonts can be used within many applications, it
+ can be used in every word processor and DTP program. There are
+ two versions of the Type 1 format: Binary and ASCII (suffix:
+ .pfb & .pfa). The Amiga software uses the Binary format, but you
+ can easily convert them with TypeSmith or some PD software
+ products (z.B. PFB2PFA) . In Addition to the files mentioned
+ above, there are the metrics files with the suffixes .afm or
+ .pfm. They contain information about the size (width) of the
+ letters and most programs expect this file to be in the same
+ directory as the font file.
+
+ 3. Postscript Type 3 fonts (suffix: .ps or nothing) are not often
+ used on the Amiga, but some applications do support this font
+ format (e.g. PageStream). There are also some download
+ utilities from PD sources available.
+
+ 4. Truetype fonts (suffix: .ttf) are not very common on the Amiga,
+ there is one word processor supporting this format (Wordworth
+ 3.0). Due to the lower quality of the format, Amiga users tend
+ to use higher quality for their DTP, DTV and word processing...
+ There are also two formats: Mac & Windows available. The Amiga
+ software is able to use the Windows format.
+
+ 5. DMF fonts is the privat format of PageStream (suffix: .dmf), since
+ PageStream is the market leader in DTP programs on the Amiga, so
+ this format is very common!
+
+ 6. Bitmap fonts (suffix: .font and numbers in a directory by the name
+ of the font, sometimes .otag when converted from IntelliFont)
+ were used in the OS 1.x, but have been replaced by the superior
+ IntelliFont Format in OS 2.0. Under 2.0 or higher you still are
+ able to use the bitmap fonts for small sizes, but for printouts
+ you should use the IntelliFont format or any other vector font
+ format mentioned above.
+
+ 7. Colour Bitmap fonts (same suffixes as Bitmap Fonts, but the
+ numbers have in addition a C, e.g. 35C) are also very common on
+ the Amiga, they are mainly used for DTV applications, like the
+ Video Toaster and Scala.
+
+ Frequently Requested Amiga Fonts
+ ================================
+
+ 1. First place to look for fonts is the AMINET archive. This is the
+ biggest archive of Amiga software and there you will find also
+ quite a lot of fonts. The Aminet consists of many mirrors
+ around the world. Here are some of them:
+
+ 1. ftp.wustl.edu,
+
+ 2. ftp.luth.se,
+
+ 3. ftp.eunet.ch,
+
+ 4. ftp.uni-paderborn.de,
+
+ 5. ftp.doc.ic.ac.uk.
+
+ Just log in as ftp and go to the directory
+
+ /pub/aminet/text/font.
+
+ 2. Another good ftp server to look is the CICA-server:
+
+ 1. ftp.cica.indiana.edu
+
+ To this server are also some mirrors around the world available.
+
+ 3. Also a good place to look for is the following WWW server:
+
+ 1. http://www.ora.com/homepages/comp.fonts/ifa
+
+ 4. Another good place is the Fresh Fonts I CD-ROM, there you will
+ almost certainly find some nice fonts. The CD is available from
+
+ 1. Fred Fish / Amiga Library Services (orders@amigalib.com)
+
+ 2. Stefan Ossowski / Schatztruhe GmbH
+
+ The CD is for free when buying another CD from that company.
+
+ You can also access the HTML pages on the CD under the following
+ address:
+
+ 1. http://macke.gris.informatik.uni-tuebingen.de:4711/~damor/
+
+ Commercial Font Sources
+ =======================
+
+ Commercial fonts can be obtained from a number of different companies,
+ including the large font houses: Adobe, Font Haus, Font Company,
+ Bitstream, and Monotype. At these companies, fonts cost about $40 for a
+ single face, and must be purchased in packages. Adobe, Bitstream, and
+ Monotype also sell pre-designated type collections for slightly lower
+ prices.
+
+ There are also a lot of PD reseller who have a vast quantity of fonts,
+ check out your local Amiga magazin for more information.
+
+ Please consult the vendor list for a more complete list of vendors.
+
+ Non-Latin fonts on the Amiga
+ ============================
+
+ Due to the really bad information policy by C= there was actually no
+ information about non-latin fonts. But still it is possible to use them,
+ without difficulty. You just have to get yourself some additional
+ files. First of all you need the non-latin font files. There is a
+ large selection of them on the Fresh Fonts CD-ROM mentioned above. In
+ order to use the non-latin font files, you have to get yourself the
+ appropriate keymap file, this will remap the keys on the keyboard to
+ the appropriate letters of the foreign alphabet, e.g. in order to use
+ a Russian font, you should set the russian keymap file in the
+ preferences (via PREFS/INPUT).
+
+ Not only that you can write with a non-latin alphabet, you can also
+ localize your workbench. How about a Greek workbench or a Hebrew
+ workbench? Have a look into the AMINET archive (mentioned above) for
+ these files!
+
+ In addition to this you can easily use Hebrew & Arabic in any word
+ processor incl. writing from right-to-left! This can be easily done
+ by setting the kerning value to negative values (like this the cursor
+ moves left and not right) and moving the characters into the negativ
+ part! You can get fonts from me with this feature!
+
+ Amiga Font Installation
+ =======================
+
+ The installation of Postscript, DMF and Truetype fonts is described by
+ the application that use them. Please refer to the manuals of the
+ software packages.
+
+ The installation of IntelliFonts is very easy. Just start `IntelliFont'
+ (OS 3.x) or `Fountain' (OS 2.x) and follow the guidelines from within
+ the program.
+
+ In order to install bitmap fonts, either copy them to the logical device
+ FONTS: or assign the directory with your bitmap fonts:
+
+ ASSIGN Fonts: <your_directory> ADD
+
+ Right after this you can start your application and use them. When using
+ non-latin fonts, don't forget to set the appropriate keymap file!
+
+ Amiga Font Utilities
+ ====================
+
+ 1. IntelliFont
+
+ IntelliFont is the system program by OS 3.x which lets you install
+ Agfa IntelliFonts and converts them to bitmap fonts. The program
+ is located in the drawer `SYS:System/'. For more information
+ read your Workbench 3.x manual.
+
+ 2. Fountain
+
+ Is the preceding program to IntelliFont and comes with the now
+ obsolete OS 2.x. Please read the section about Fountain in your
+ Workbench 2.x manual.
+
+ 3. PFB2PFA
+
+ This neat little utility lets you convert Postscript Binary files
+ to Postscript ASCII files. This is needed in order to use DOS &
+ Amiga Adobe Type 1 fonts on the Mac!
+
+ 4. CacheFont
+
+ This great program caches the fontlist for you, in order to save a
+ huge amount of time. The program looks for all fonts available
+ on the system and creates a special cache-file on disk.
+
+ 5. TypeSmith
+
+ This is the best font converter on the Amiga, besides this
+ function it is also a full blown font editor (see below) :-).
+ The program is able to convert between:
+
+ 1. Truetype
+
+ 2. DMF
+
+ 3. Adobe (Type 1 & 3)
+
+ 4. IntelliFont
+
+ 5. Bitmap (Amiga, Adobe, DMF)
+
+ Making Outline Fonts
+ ====================
+
+ This is very, very difficult. Many people imagine that there are
+ programs that will simply convert pictures into fonts for them. This is
+ not the case; most fonts are painstakingly created by drawing curves
+ that closely approximate the letterforms. In addition, special rules
+ (which improve hinting, etc.) mandate that these curves be drawn in
+ specific ways. Even designing, or merely digitizing, a simple font can
+ take hundreds of hours.
+
+ The easiest way of learning how to create fonts, is to have a look at
+ existing fonts and try to change some letters.
+
+ Given that, there are two major programs used for font design on the
+ Amiga, TypeSmith 2.5 ($150) and FontDesigner ($100). These programs
+ will allow you to import scanned images, and then trace them with
+ drawing tools. The programs will then generate Adobe type 1, 3,
+ TrueType, AGFA Intellifont, DMF and Bitmap fonts for either the
+ Amiga, the Macintosh or the IBM PC. They will also generate automatic
+ hinting. They also open previously constructed outline fonts,
+ allowing them to be modified, or converted into another format.
+
+ As far as I know, there are no shareware programs that allows you to
+ generate outline fonts.
+
+ There are also two programs for creating bitmap fonts. Personal Fonts
+ Maker and Calligrapher. The second one has not been updated for several
+ years, but it still is a good tool to work with. The first Program was
+ created by adding some features to a good bitmap paint program
+ (Personal Paint).
+
+ There are some shareware tools to create bitmap fonts which you can
+ convert to outline (vector) fonts with TypeSmith.
+
+ Problems and Possible Solutions
+ ===============================
+
+ 1. Pagestream does not recognize your newly installed font.
+
+ This happens when you have two fonts with the same ID. The
+ solution is to load such a font into a font editor and enter a
+ new ID for one of the fonts. Still it might happen that you
+ choose another one, that has already been used by!
+
+ 2. Your application does not find the IntelliFont.
+
+ This happens when you haven't set the locigal device FONTS: to
+ your drawer. You can change this by typing the following
+ command into your SHELL or add this line to your
+ `S:User-Startup' file:
+
+ ASSIGN Fonts: <your_drawer> ADD
+
+ 3. You're using a non-latin font and the wrong characters appear when
+ typing.
+
+ This happens when you forget to set the appropriate keymap file.
+ Enter the Prefs directory and start the program `INPUT'. There
+ you can choose your keymap file.
+
+ Adobe Type 1 fonts for the Amiga
+ ================================
+
+ Darrell Leland contributes the following information:
+
+ There are now three high end DTP packages for the Amiga that can
+ directly or indirectly use Adobe Type 1 Fonts or AGFA Compugraphic
+ fonts. The best of the lot in both my and Amiga World's opinions is
+ SoftLogik's Pagestream, currently in version 2.2 but about to go to
+ version 3.0. Pagestream can take Adobe fonts in MS-DOS format directly
+ with no format conversion needed. All you have to do is get them on an
+ Amiga format disk, which is very easy using the new version of
+ Commodore's Workbench operating system. Pagestream has import modules
+ for MacWrite, Adobe Illustrator, and every other format in the universe
+ (seems like). It is generally a very stable and well behaved program
+ with a lot of features. I haven't had a chance to see 3.0 yet, but they
+ are claiming it's going to be a real killer. We shall see. It does color
+ seps, twists and rotates fonts, etc. Pagestream's job has been made
+ easier with Commodore's (about time) release of their own Postscript
+ printer drivers and Preferences postscript printer control tools.
+
+ SoftLogik also sells a program called Typesmith, which is (at last!) a
+ structured font maker/editor for the Amiga. Typesmith will work with
+ both formats mentioned above plus SoftLogik's own font format, which I
+ get the impression they are discontinuing in favor of Postscript. They
+ also sell ArtExpression, a very nice structured drawing package that
+ does everything I can think of. I understand SoftLogik has also been
+ getting several Mac and PC font makers to make Amiga fonts for them too.
+ They even have a program system that allows programs to publish to other
+ programs, sort of like in Mac System 7.0. They are lisencing it out to
+ any Amiga developer who pays a paltry sum to lisence it.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Atari_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Atari_Info
new file mode 100644
index 0000000000..4e7152e40a
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Atari_Info
@@ -0,0 +1,157 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Atari Info
+Supersedes: <font-faq-14_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:24 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 134
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-14_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48311 comp.answers:20525 news.answers:79246
+
+Archive-name: fonts-faq/part14
+Version: 2.1.5
+
+Subject: 9. Atari ST/TT/Falcon Information
+
+ Erlend Nagel contributed the following information about the Atari
+ ST/TT/Falcon.
+
+Subject: 9.1. SpeedoGDOS
+
+ SpeedoGDOS is similar to ATM.
+
+ Fonts included with SpeedoGDOS 4.x
+ ==================================
+
+ 14 fonts are included with SpeedoGDOS 4.x.
+
+ Bitstream Cooper Black, Dutch 801 Roman, Dutch 801 Bold, Dutch 801
+ Italic, Dutch 801 Bold Italic, Monospace 821, More Wingbats SWC, Park
+ Avenue, Swiss 721, Swiss 721 Bold, Swiss 721 Italic, Swiss 721 Bols
+ Italic, Symbol Monospaced, and VAG Rounded
+
+ Fonts included with SpeedoGDOS 5.x
+ ==================================
+
+ 24 fonts are included with SpeedoGDOS 5.x. All fonts included with
+ SpeedoGDOS 4.x plus the following:
+
+ American Garamond Roman, American Garamond Bold, American Garamond
+ Italic, American Garamond Bold Italic, AD LIB Regular, Allegro Regular,
+ Amelia Regular, and Cataneo Bold
+
+Subject: 9.2. Atari File Formats
+
+ Atari Font formats
+ ==================
+
+ The standard Atari OS in ROM does not support any type of fonts. To use
+ different fonts in applications, either the application has to have
+ built-in support for some font format, or an add-on program is needed.
+ This add-on program is called a GDOS, a Graphical Device Operating
+ System. There are many different versions of GDOS.
+
+ The earliest versions of GDOS supported only GEM bitmap fonts (*.FNT).
+ These versions include GDOS, AMC-GDOS (Atari), G-plus (Codehead) and
+ Font-GDOS (Atari again). Font-GDOS (available for free) added caching
+ to the font-manager, so not all fonts need to reside in memory at the
+ same time.
+
+ FontGDOS and FSM-GDOS were develloped in parallel and are both
+ successors of Atari-GDOS (1.x). The FSM stands for Font Scaling
+ Manager and allowed vector fonts to be used. FSM-GDOS was only
+ included with Wordflair II and G-Man. FSM-GDOS also still supported GEM
+ bitmap fonts. The font format is the QMS/Imagen format.
+
+ After FSM-GDOS, Atari introduced SpeedoGDOS 4.0, using Speedo font
+ scaling technology licensed from Bitstream. 14 fonts are included with
+ this version (see 1.15). SpeedoGDOS 4.0 and 4.1 can use GEM bitmap,
+ Atari encrypted and commercially encrypted Speedo fonts. As of version
+ 4.2 also the publicly available X11 Speedo fonts can be used.
+ SpeedoGDOS offers improved speed and reliability over FSM-GDOS, as well
+ as track- and pair-kerning.
+
+ Recently Compo Software introduced SpeedoGDOS 5.x which supports GEM
+ bitmap, Speedo, Truetype and Type 1 fonts. Included are 22 Speedo fonts
+ (see 1.15).
+
+ For more information about the GDOS format, consult the GDOS FAQ:
+ ftp://ftp.cs.tu-berlin.de/pub/atari/Gdos/gdosi??e.txt. The "??" is the
+ version number; as of 01 Mar 95, the versions are: 24 in English and 25
+ in German. A LaTeX version of the German edition is also available.
+
+ Also recently introduced was NVDI 3.0 by Behne & Behne, which supports
+ GEM bitmap, Speedo and Truetype fonts. The biggest difference when
+ compared to SpeedoGDOS 5.x is the improved speed, because NVDI is
+ written in Assembler instead of C. Only 2 fonts are included with NVDI
+ 3.0.
+
+ These fonts are transparent to programs. There are a few other options
+ that require support by the program using the fonts. Two major font
+ formats are supported in this way on the Atari, namely
+ Signum!2/Signum!3 fonts and Calamus fonts.
+
+ The Signum!2 font format is a bitmapped font format supported by many
+ wordprocessors and some drawing packages. Amazing print quality on
+ 9-needle printers. Many high quality designs are available in Signum!2
+ and Signum!3 format (Mostly German), especially for some special
+ languages like Polish. There are also many PD fonts available in this
+ format.
+
+ The Calamus (*.CFN) format was introduced by DMC, in their Calamus DTP
+ program that uses soft-RIPping. The Calamus font format has no hinting
+ since it is meant to be used on very high resolution type setting
+ machines. Also supported by Digital Art's (DA's) software. Many
+ professional designs are available in this format, as well as a lot of
+ PD fonts.
+
+ Atari Font Format Extensions
+ ============================
+
+ File formats specific to the Atari platform:
+
+ * .E24
+
+ Bitmapped Signum!2 screen font.
+
+ * .L30
+
+ Bitmapped Signum!2 printer font for Laser and Deskjet printers.
+
+ * .OTL
+
+ Vector font table used by FSM-GDOS.
+
+ * .P9
+
+ Bitmapped Signum!2 printer font for Hi-Res 9-needle printers
+ (214*196 dpi).
+
+ * .P24
+
+ Bitmapped Signum!2 printer font for 24-needle printers.
+
+ * .QFM
+
+ Vector font used by FSM-GDOS.
+
+Subject: 9.3. Frequently Requested Atari Fonts
+
+ Some fonts, including a few Speedo fonts are available from various
+ archives. The most important Atari archive is atari.archive.umich.edu.
+
+ Most fonts can be had from PD/Shareware distributors around the world...
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Diffs_from_last_posting b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Diffs_from_last_posting
new file mode 100644
index 0000000000..1f5eb8b481
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Diffs_from_last_posting
@@ -0,0 +1,231 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Diffs from last posting
+Supersedes: <font-faq-diffs_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:46 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 208
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-diffs_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48315 comp.answers:20529 news.answers:79250
+
+Archive-name: fonts-faq/diffs
+Version: 2.1.5
+Diffs-from: comp.fonts FAQ v2.1.4
+Diff-tool: diff -c2
+
+diff -c2 v2.1.4/font-faq.1 v2.1.5/font-faq.1
+*** v2.1.4/font-faq.1 Sat Nov 25 12:49:00 1995
+--- v2.1.5/font-faq.1 Wed Aug 14 07:39:04 1996
+***************
+*** 2,11 ****
+ ----------------------------------------------------------------------
+ The comp.fonts FAQ
+! Version 2.1.4.
+! November 25, 1995
+ Compiled by Norman Walsh
+
+ Copyright (C) 1992-95 by Norman Walsh <norm@ora.com>. The previous
+! version was 2.1.3.
+
+ Portions of the OS/2 section are Copyright (C) 1993 by David J.
+--- 2,11 ----
+ ----------------------------------------------------------------------
+ The comp.fonts FAQ
+! Version 2.1.5.
+! August 13, 1996
+ Compiled by Norman Walsh
+
+ Copyright (C) 1992-95 by Norman Walsh <norm@ora.com>. The previous
+! version was 2.1.4.
+
+ Portions of the OS/2 section are Copyright (C) 1993 by David J.
+***************
+*** 145,162 ****
+
+ This FAQ is a work in progress. If you have any suggestions, I would be
+! delighted to hear them.
+
+ This FAQ is maintained in TeXinfo format. A Perl script constructs the
+! postable FAQ from the TeXinfo sources. TeX DVI, PostScript, Emacs Info,
+! plain text, and HTML versions of this FAQ are available from
+! jasper.ora.com in /pub/comp.fonts/FAQ. A "Gopher" server is also
+! maintained at shsu.edu which can provide interactive access to the FAQ.
+
+! The FAQ is also available from The comp.fonts Home Page on the World
+! Wide Web:
+
+! http://jasper.ora.com/comp.fonts
+
+! This is also the site for The Internet Font Archive.
+
+ The posted version of the FAQ is organized in a quasi-digest format so
+--- 145,164 ----
+
+ This FAQ is a work in progress. If you have any suggestions, I would be
+! delighted to hear them. After many months of inactivity, I hope to
+! begin a major update on the FAQ. Please send in your comments. And
+! thanks for being patient.
+
+ This FAQ is maintained in TeXinfo format. A Perl script constructs the
+! postable FAQ from the TeXinfo sources. The FAQ is also available from
+! The comp.fonts Home Page on the World Wide Web:
+
+! http://www.ora.com/homepages/comp.fonts/
+
+! This is also the site for The Internet Font Archives.
+
+! TeX DVI, PostScript, Emacs Info, plain text, and HTML versions of this
+! FAQ are available from the web at
+! http://www.ora.com/homepages/comp.fonts/FAQ.html. FTP access to these
+! archives has been temporarily suspended.
+
+ The posted version of the FAQ is organized in a quasi-digest format so
+diff -c2 v2.1.4/font-faq.13 v2.1.5/font-faq.13
+*** v2.1.4/font-faq.13 Sat Nov 25 12:49:06 1995
+--- v2.1.5/font-faq.13 Wed Aug 14 07:39:07 1996
+***************
+*** 95,99 ****
+ 3. Also a good place to look for is the following WWW server:
+
+! 1. http://jasper.ora.com/Internet-Font-Archive.html
+
+ 4. Another good place is the Fresh Fonts I CD-ROM, there you will
+--- 95,99 ----
+ 3. Also a good place to look for is the following WWW server:
+
+! 1. http://www.ora.com/homepages/comp.fonts/ifa
+
+ 4. Another good place is the Fresh Fonts I CD-ROM, there you will
+diff -c2 v2.1.4/font-faq.16 v2.1.5/font-faq.16
+*** v2.1.4/font-faq.16 Sat Nov 25 12:49:07 1995
+--- v2.1.5/font-faq.16 Wed Aug 14 07:39:08 1996
+***************
+*** 10,15 ****
+ Subject: 11.1. How do I convert AFM files to PFM files
+
+! You can get afm2pfm and pfm2afm files from jasper.ora.com in the
+! directory /pub/pfm2afm.
+
+ Subject: 11.2. PS2PK
+--- 10,15 ----
+ Subject: 11.1. How do I convert AFM files to PFM files
+
+! You can get afm2pfm and pfm2afm files from
+! http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+ Subject: 11.2. PS2PK
+***************
+*** 304,315 ****
+
+ If you are using ftp, you will need either the name of the host or the
+! Internet number. For example, to connect to jasper, listed as ftp:
+! jasper.ora.com [198.112.208.14] you will need to type something like
+
+! ftp jasper.ora.com
+
+ If that doesn't work, try using the number:
+
+! ftp 198.112.208.14
+
+ If that doesn't work, on Unix systems you can use nslookup (it's
+--- 304,315 ----
+
+ If you are using ftp, you will need either the name of the host or the
+! Internet number. For example, to connect to ftp.ora.com, listed as
+! ftp: ftp.ora.com [198.112.208.11] you will need to type something like
+
+! ftp ftp.ora.com
+
+ If that doesn't work, try using the number:
+
+! ftp 198.112.208.11
+
+ If that doesn't work, on Unix systems you can use nslookup (it's
+diff -c2 v2.1.4/font-faq.3 v2.1.5/font-faq.3
+*** v2.1.4/font-faq.3 Sat Nov 25 12:49:02 1995
+--- v2.1.5/font-faq.3 Wed Aug 14 07:39:04 1996
+***************
+*** 405,410 ****
+
+ [ed: additional bibliographic information appears in the file
+! "Additional-bibliography" on jasper.ora.com:/comp.fonts. I have not
+! yet had time to integrate this bibliographic information into the FAQ]
+
+ Subject: 1.19. Font Encoding Standards
+--- 405,411 ----
+
+ [ed: additional bibliographic information appears in the file
+! "Additional-bibliography" on
+! http://www.ora.com/homepages/comp.fonts/FAQ.html. I have not yet had
+! time to integrate this bibliographic information into the FAQ]
+
+ Subject: 1.19. Font Encoding Standards
+diff -c2 v2.1.4/font-faq.7 v2.1.5/font-faq.7
+*** v2.1.4/font-faq.7 Sat Nov 25 12:49:04 1995
+--- v2.1.5/font-faq.7 Wed Aug 14 07:39:05 1996
+***************
+*** 455,460 ****
+ distributed in PC format, however. Again, the font will have to
+ be reencoded for Windows. Appropriate AFM files for this font can
+! be obtained from: jasper.ora.com:/pub/norm/comp.fonts. The file
+! is called IBM-Courier-PC8-SymbolSet-AFMs.zip.
+
+ Many of these mac fonts are available in files that are either entitled
+--- 455,460 ----
+ distributed in PC format, however. Again, the font will have to
+ be reencoded for Windows. Appropriate AFM files for this font can
+! be obtained from:
+! http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+ Many of these mac fonts are available in files that are either entitled
+diff -c2 v2.1.4/font-faq.8 v2.1.5/font-faq.8
+*** v2.1.4/font-faq.8 Sat Nov 25 12:49:04 1995
+--- v2.1.5/font-faq.8 Wed Aug 14 07:39:06 1996
+***************
+*** 50,55 ****
+ font will have to be reencoded for Windows. Appropriate AFM files
+ for this font can be obtained from:
+! jasper.ora.com:/pub/norm/comp.fonts. The file is called
+! IBM-Courier-PC8-SymbolSet-AFMs.zip.
+
+ Lee Cambell suggests the following alternative:
+--- 50,54 ----
+ font will have to be reencoded for Windows. Appropriate AFM files
+ for this font can be obtained from:
+! http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+ Lee Cambell suggests the following alternative:
+***************
+*** 262,269 ****
+
+ REFONT
+! refont14.zip in /pub/norm/mac-font-tools on jasper.ora.com
+
+ BMAP2AFM
+! bm2af02.zip in /pub/norm/mac-font-tools on jasper.ora.com
+
+ XBIN converts Mac "BinHex"ed files back into binary format. BinHex is
+--- 261,270 ----
+
+ REFONT
+! refont14.zip from
+! http://www.ora.com/homepages/comp.fonts/FAQ-tools.html
+
+ BMAP2AFM
+! bm2af02.zip from
+! http://www.ora.com/homepages/comp.fonts/FAQ-tools.html
+
+ XBIN converts Mac "BinHex"ed files back into binary format. BinHex is
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(1_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(1_6)
new file mode 100644
index 0000000000..63c2297721
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(1_6)
@@ -0,0 +1,1183 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (1/6)
+Supersedes: <font-faq-1_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:08 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 1161
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48298 comp.answers:20512 news.answers:79233
+
+Archive-name: fonts-faq/part1
+Version: 2.1.5
+
+ Frequently Asked Questions About Fonts
+ ----------------------------------------------------------------------
+ The comp.fonts FAQ
+ Version 2.1.5.
+ August 13, 1996
+ Compiled by Norman Walsh
+
+ Copyright (C) 1992-95 by Norman Walsh <norm@ora.com>. The previous
+ version was 2.1.4.
+
+ Portions of the OS/2 section are Copyright (C) 1993 by David J.
+ Birnbaum. All rights reserved. Reproduced here by permission.
+
+ Permission is granted to make and distribute verbatim copies of this
+ document provided the copyright notice and this permission notice are
+ preserved on all copies.
+
+Subject: Table of Contents
+
+ 1. General Information
+ 1.1. Font Houses
+ 1.2. What's the difference between all these font formats?
+ 1.3. What about "Multiple Master" fonts?
+ 1.4. Is there a methodology to describe and classify typefaces?
+ 1.5. What is the "f" shaped "s" called?
+ 1.6. What about "Colonial" Typefaces?
+ 1.7. What is "Point Size"?
+ 1.8. Where can I get ... fonts.
+ 1.9. Where can I get fonts for non-Roman alphabets?
+ 1.10. What about fonts with the International Phonetic Alphabet (IPA) s...
+ 1.11. How can I convert my ... font to ... format?
+ 1.12. Are fonts copyrightable?
+ 1.13. Typeface Protection
+ 1.14. File Formats
+ 1.15. Ligatures
+ 1.16. Built-in Fonts
+ 1.17. Glossary
+ 1.18. Bibliography
+ 1.19. Font Encoding Standards
+ 1.20. PostScript
+ 1.21. TrueType
+ 1.22. Unicode
+ 1.23. Can I Print Checks with the MICR Font?
+ 1.24. Rules of Thumb
+ 1.25. Acknowledgements
+ 1.26. A Brief Introduction to Typography
+ 1.27. A Brief History of Type
+ 1.28. The Role of National Orthography in Font Design
+ 1.29. Interesting Fonts
+ 1.30. Pronounciation of Font Names
+ 1.31. What is it?
+ 1.32. Equivalent Font Names
+ 1.33. Digital Type Design Tools
+ 1.34. Type Design Firms
+ 1.35. What does `lorem ipsum dolor' mean?
+ 2. Macintosh Information
+ 2.1. Macintosh Font formats
+ 2.2. Frequently Requested Mac Fonts
+ 2.3. Commercial Font Sources
+ 2.4. Mac Font Installation
+ 2.5. Mac Font Utilities
+ 2.6. Making Outline Fonts
+ 2.7. Problems and Possible Solutions
+ 2.8. Creating Mac screen fonts
+ 3. MS-DOS Information
+ 3.1. Frequently Requested MS-DOS fonts
+ 3.2. MS-DOS Font Installation
+ 3.3. What exactly are the encodings of the DOS code pages?
+ 3.4. MS-DOS Font Utilities
+ 3.5. Converting fonts under MS-DOS
+ 3.5.1. Converting Mac Type 1 fonts to MS-DOS format
+ 3.5.2. Converting PC Type 1 and TrueType fonts to Mac format
+ 3.5.3. Converting PC Type 1 fonts into TeX PK bitmap fonts
+ 3.5.4. Converting TeX PK bitmaps into HP LaserJet softfonts (and vice...
+ 3.5.5. TrueType to HP LaserJet bitmap softfonts (HACK!)
+ 3.6. MS-DOS Screen Fonts (EGA/VGA text-mode fonts)
+ 4. OS/2 Information
+ 4.1. Preliminaries
+ 4.2. Fonts under DOS
+ 4.3. Windows
+ 4.4. Differences between Windows and OS/2
+ 4.5. Installation under Windows and Win-OS/2
+ 4.6. FontSpecific PostScript Encoding
+ 4.7. AdobeStandardEncoding
+ 4.8. AdobeStandardEncoding under Windows (and Win-OS/2)
+ 4.9. AdobeStandardEncoding under OS/2
+ 4.10. Consequences for OS/2 users
+ 4.11. Advice to the user
+ 4.12. OS/2 2.1 and beyond
+ 5. Unix Information
+ 6. Sun Information
+ 6.1. Fonts Under Open Windows
+ 6.1.1. Does OpenWindows support Type 1 PostScript fonts?
+ 6.1.2. Improving font rendering time
+ 6.1.3. Making bitmap fonts for faster startup
+ 6.1.4. Converting between font formats (convertfont, etc.)
+ 6.1.5. Xview/OLIT fonts at 100 dpi
+ 6.2. Where can I order F3 fonts for NeWSprint and OpenWindows?
+ 7. NeXT Information
+ 7.1. Tell me about NeXTstep fonts
+ 7.2. Tell me more about NeXTstep fonts
+ 7.3. Porting fonts to the NeXT
+ 7.4. Font availability
+ 7.5. Why can I only install 256 fonts on my NeXT?
+ 8. Amiga Information
+ 9. Atari ST/TT/Falcon Information
+ 9.1. SpeedoGDOS
+ 9.2. Atari File Formats
+ 9.3. Frequently Requested Atari Fonts
+ 10. X11 Information
+ 10.1. Getting X11
+ 10.2. Historical Notes about X11
+ 10.3. X11 Font Formats
+ 10.4. X11 Font Server
+ 10.5. Fonts and utilities for X11
+ 11. Utilities Information
+ 11.1. How do I convert AFM files to PFM files
+ 11.2. PS2PK
+ 11.3. TeX Utilities
+ 11.4. MFPic
+ 11.5. fig2MF
+ 11.6. GNU Font Utilities
+ 11.7. Font Editors
+ 11.8. The T1 Utilities
+ 11.9. Where to get bitmap versions of the fonts
+ 11.10. Converting between font formats
+ 11.11. Getting fonts by FTP and Mail
+ 11.12. MetaFont to PostScript Conversion
+ 11.13. How to use Metafont fonts with Troff
+ 11.14. PKtoBDF / MFtoBDF
+ 11.15. PKtoPS
+ 11.16. PKtoSFP / SFPtoPK
+ 11.17. PostScript to MetaFont
+ 11.18. Mac Bitmaps to BDF Format
+ 12. Vendor Information
+
+Subject: 1. General Information
+
+ Many FAQs, including this one, are available by anonymous ftp from
+ rtfm.mit.edu in the directory pub/usenet/news.answers. Each posted
+ section of the FAQ is archived under the name that appears in the
+ "Archive-name" header at the top of the article. If you are unable to
+ access rtfm.mit.edu via ftp, you can get the FAQs via email. Send the
+ message "help" to mail-server@rtfm.mit.edu.
+
+ This FAQ is a work in progress. If you have any suggestions, I would be
+ delighted to hear them. After many months of inactivity, I hope to
+ begin a major update on the FAQ. Please send in your comments. And
+ thanks for being patient.
+
+ This FAQ is maintained in TeXinfo format. A Perl script constructs the
+ postable FAQ from the TeXinfo sources. The FAQ is also available from
+ The comp.fonts Home Page on the World Wide Web:
+
+ http://www.ora.com/homepages/comp.fonts/
+
+ This is also the site for The Internet Font Archives.
+
+ TeX DVI, PostScript, Emacs Info, plain text, and HTML versions of this
+ FAQ are available from the web at
+ http://www.ora.com/homepages/comp.fonts/FAQ.html. FTP access to these
+ archives has been temporarily suspended.
+
+ The posted version of the FAQ is organized in a quasi-digest format so
+ that it is easy to find the questions you are interested in. All
+ questions that appear in the table of contents can be found by searching
+ for the word "Subject:" followed by the question number.
+
+ The "TeXinfo" distribution from the Free Software Foundation contains a
+ program called "Info" that can be used to read the Info version of the
+ FAQ in a hypertext manner. The "TeXinfo" distribution can be obtained
+ from prep.ai.mit.edu in the /pub/gnu directory. At the time of this
+ writing, texinfo-2.16.tar.gz is the most recent version. Info files
+ can also be read in hypertext form by GNU Emacs.
+
+ Future versions of the FAQ will make more use of the hypertext
+ capabilities provided by the Info format. At present, the FAQ is
+ organized as a simple tree. A plain ASCII, postable version of the FAQ
+ will always be maintained.
+
+ All trademarks used in this document are the trademarks of their
+ respective owners.
+
+ Standard disclaimers apply.
+
+Subject: 1.1. Font Houses
+
+ This section will be expanded on in the future. It contains notes about
+ various commercial font houses.
+
+ Adobe Systems, Inc.
+ ===================
+
+ Adobe Systems Incorporated develops, markets, and supports computer
+ software products and technologies that enable users to create, display,
+ print, and communicate electronic documents. Adobe licenses its
+ technology to major computer and publishing suppliers, and markets a
+ line of type and application software products.
+
+ Compugraphic
+ ============
+
+ See "Miles, Agfa Division"
+
+ designOnline(tm)
+ ================
+
+ Home of Alphabets, Inc., designOnline is the online resource for
+ design. The majority of the interactivity is happening on [their]
+ FirstClass server, currently available by dialup and across the
+ Internet.
+
+ Miles, Agfa Division
+ ====================
+
+ Compugraphic which was for a while the Compugraphic division of Agfa,
+ is now calling itself "Miles, Agfa Division" (yes, the Miles drug
+ company), since CG's off-shore parent Agfa has been absorbed by Miles.
+ So typographically speaking, Compugraphic, CG, Agfa, A-G ag, and Miles
+ all refer to the same company and font library. Their proprietary fonts
+ are still CG Xyz, but the name is Miles Agfa.
+
+ Quadrat Communications
+ ======================
+
+ Quadrat Communications is a digital type foundry based in Toronto,
+ Ontario, Canada. [David Vereschagin] began creating and designing type
+ a few years ago, intrigued by the new possibilities presented by
+ Altsys's Fontographer software. [His] first project was the plain style
+ of Clear Prairie Dawn, a sans serif text face, which took three years
+ to complete. As well as designing [his] own faces, [he's] also
+ available for the creation of custom faces.
+
+Subject: 1.2. What's the difference between all these font formats?
+
+ This question is not trivial to answer. It's analogous to asking what
+ the difference is between various graphics image file formats. The
+ short, somewhat pragmatic answer, is simply that they are different
+ ways of representing the same "information" and some of them will work
+ with your software/printer and others won't.
+
+ At one level, there are two major sorts of fonts: bitmapped and outline
+ (scalable). Bitmapped fonts are falling out of fashion as various
+ outline technologies grow in popularity and support.
+
+ Bitmapped fonts represent each character as a rectangular grid of
+ pixels. The bitmap for each character indicates precisely what pixels
+ should be on and off. Printing a bitmapped character is simply a
+ matter of blasting the right bits out to the printer. There are a
+ number of disadvantages to this approach. The bitmap represents a
+ particular instance of the character at a particular size and
+ resolution. It is very difficult to change the size, shape, or
+ resolution of a bitmapped character without significant loss of quality
+ in the image. On the other hand, it's easy to do things like shading
+ and filling with bitmapped characters.
+
+ Outline fonts represent each character mathematically as a series of
+ lines, curves, and 'hints'. When a character from an outline font is
+ to be printed, it must be 'rasterized' into a bitmap "on the fly".
+ PostScript printers, for example, do this in the print engine. If the
+ "engine" in the output device cannot do the rasterizing, some front end
+ has to do it first. Many of the disadvantages that are inherent in the
+ bitmapped format are not present in outline fonts at all. Because an
+ outline font is represented mathematically, it can be drawn at any
+ reasonable size. At small sizes, the font renderer is guided by the
+ 'hints' in the font; at very small sizes, particularly on
+ low-resolution output devices such as screens, automatically scaled
+ fonts become unreadable, and hand-tuned bitmaps are a better choice (if
+ they are available). Additionally, because it is rasterized "on
+ demand," the font can be adjusted for different resolutions and 'aspect
+ ratios'.
+
+ Werenfried Spit adds the following remark:
+
+ Well designed fonts are not scalable. I.e. a well designed 5pt font is
+ not simply its 10pt counterpart 50% scaled down. (One can verify this
+ by blowing up some small print in a copier and compare it with large
+ print; or see the example for computer modern in D.E. Knuth's TeXbook.)
+ Although this fact has no direct implications for any of the two
+ methods of font representation it has an indirect one: users and word
+ processor designers tend to blow up their 10pt fonts to 20pt or scale
+ them down to 5pt given this possibility. Subtle details, but well...
+
+ LaserJet .SFP and .SFL files, TeX PK, PXL, and GF files, Macintosh
+ Screen Fonts, and GEM .GFX files are all examples of bitmapped font
+ formats.
+
+ PostScript Type 1, Type 3, and Type 5 fonts, Nimbus Q fonts, TrueType
+ fonts, Sun F3, MetaFont .mf files, and LaserJet .SFS files are all
+ examples of outline font formats.
+
+ Neither of these lists is even close to being exhaustive.
+
+ To complicate the issue further, identical formats on different
+ platforms are not necessarily the same. For example Type 1 fonts on
+ the Macintosh are not directly usable under MS-DOS or Unix, and
+ vice-versa.
+
+ It has been pointed out that the following description shows signs of
+ its age (for example, the eexec encryption has been thoroughly hacked).
+ I don't dispute the observation and I encourage anyone with the
+ knowledge and time to submit a more up to date description.
+
+ It has further been suggested that this commentary is biased toward
+ Kingsley/ATF. The omission of details about Bitstream (and possibly
+ Bauer) may be considered serious since their software lies inside many
+ 3rd-party PostScript interpreters.
+
+ The moderators of this FAQ would gladly accept other descriptions/
+ explanations/viewpoints on the issues discussed in this (and every
+ other) section.
+
+ [Ed Note: Liam R. E. Quin supplied many changes to the following
+ section in an attempt to bring it up to date. Hopefully it is a better
+ reflection of the state of the world today (12/07/92) than it was in
+ earlier FAQs]
+
+ Henry Schneiker <reachable electronically?> wrote the following
+ description of the differences between several scalable font
+ technologies:
+
+ ((( semi-quote )))
+
+ There has been a lot of confusion about font technologies in recent
+ times, especially when it comes to Type 1 versus Type 3 fonts, "hints,"
+ PostScript compatibility, encryption, character regularizing, kerning,
+ and the like.
+
+ * Encryption (eexec)
+
+ All fonts produced with Adobe's font technology are protected
+ through data encryption. The decryption is provided by the `eexec'
+ (encrypted execute) PostScript operator and, until recently, was
+ only present in Adobe's licensed PostScript.
+
+ Adobe has published the details of the Type 1 font format in the
+ `Black Book', Adobe Type 1 Font Format (version 1.1), Adobe
+ Systems Inc., 1990. The encryption was mainly used because of
+ font copyright problems; unencrypted fonts can also be used, but
+ these tend to use an efficient binary encoding, also in documented
+ the Type 1 book, and so are still not readable PostScript.
+
+ * Type 1, Type 3, and Type 5 font formats
+
+ There are generally three font formats used in Adobe PostScript
+ printers: Type 1, Type 3, and Type 5. Type 1 fonts are Adobe's
+ downloadable format. Type 3 fonts are third-party downloadable
+ format. Type 5 fonts are the ROM-based fonts that are part of your
+ printer.
+
+ There is no functional difference between a Type 1, Type 3, or
+ Type 5 font. A Type 3 font can do anything a Type 1 or Type 5 font
+ can do. The only real difference between them is where the
+ `BuildChar' routine comes from. For Type 1 and Type 5 fonts it's
+ built into the printer. For Type 3 fonts it's built into the font.
+ In other words, anything a Type 1 font can do a Type 3 font can
+ also do.
+
+ [Ed note: the reverse is not true. Type3 fonts can do things that
+ Type1 fonts cannot. But they aren't hinted...]
+
+ When PostScript is asked to generate a character, PostScript looks
+ in the font's dictionary for FontType. If FontType is 1 or 5
+ PostScript executes an internal routine that knows how to
+ interpret the font data stored in CharStrings. If FontType is 3
+ PostScript executes the routine BuildChar from the font's
+ dictionary to interpret the font data (often stored in
+ CharStrings).
+
+ However, each BuildChar routine is written to read data formatted
+ in a method convenient to the vendor. Adobe, Altsys, Bitstream, and
+ Kingsley/ATF all format their font data differently and, hence,
+ have different BuildChar routines.
+
+ [Ed note: relative hard disk efficiency of Kingsley vs. Adobe fonts
+ deleted on 12/07/92]
+
+ Type 5 fonts are special in that they often include hand-tuned
+ bitmaps for the commonly used sizes, such as 10- and 12-point.
+ Other sizes are generated from the outlines in normal fashion.
+
+ Don't confuse Type 1, Type 3, and Type 5 fonts with Bitstream's
+ Type A, Type B, Type C, and Type F. They are not the same and
+ serve only to confuse the issue.
+
+ * Resolution `hints'
+
+ When a character is described in outline format the outline has
+ unlimited resolution. If you make it ten times as big, it is just
+ as accurate as if it were ten times as small.
+
+ However, to be of use, we must transfer the character outline to a
+ sheet of paper through a device called a raster image processor
+ (RIP). The RIP builds the image of the character out of lots of
+ little squares called picture elements (pixels).
+
+ The problem is, a pixel has physical size and can be printed only
+ as either black or white. Look at a sheet of graph paper. Rows and
+ columns of little squares (think: pixels). Draw a large `O' in the
+ middle of the graph paper. Darken in all the squares touched by the
+ O. Do the darkened squares form a letter that looks like the O you
+ drew? This is the problem with low resolution (300 dpi). Which
+ pixels do you turn on and which do you leave off to most accurately
+ reproduce the character?
+
+ All methods of hinting strive to fit (map) the outline of a
+ character onto the pixel grid and produce the most
+ pleasing/recognizable character no matter how coarse the grid is.
+
+ [Ed note: deleted some paragraphs that are no longer true. Times
+ change...]
+
+ * Optical Scaling
+
+ Optical Scaling modifies the relative shape of a character to
+ compensate for the visual effects of changing a character's size.
+ As a character gets smaller, the relative thickness of strokes,
+ the size of serifs, the width of the character, the
+ inter-character spacing, and inter-line spacing should increase.
+ Conversely, as a character gets larger, the relative thickness,
+ widths, and spacing should decrease.
+
+ Contrast this with linear scaling, in which all parts of a
+ character get larger or smaller at the same rate, making large
+ characters look wide and heavy (strokes are too thick, serifs are
+ too big) while small characters look thin and weak.
+
+ * Kerning
+
+ As applied to PostScript fonts, kerning refers to kern pairs. A
+ kern pair specifies two characters (e.g., A and V) and the
+ distance to move the second character relative to the first. The
+ typical use of a kern pair is to remove excessive space between a
+ pair of characters. However, it may also be used to add space.
+
+ * PostScript clones
+
+ There are currently several printer manufacturers on the market
+ with PostScript clones. To be viable, a PostScript clone must
+ comply with the `red book' (PS Language Reference Manual).
+
+ In order to avoid paying royalties to Adobe, and because Adobe's
+ Type 1 font format was originally proprietary, many PostScript
+ interpreters use some other font format. Sun uses F3, and some
+ other vendors use Bitstream's Speedo format, for example. The
+ only real problem this causes is that the widths of characters
+ (the `font metrics') may vary from Adobe's, so that programs that
+ assume the Adobe character widths will produce poor quality
+ output. Bitstream fonts used to be particularly bad in the early
+ days, but they and most or all of the other vendors have solved
+ those problems.
+
+ * Apple TrueType [Ed note: formerly "Royal (`sfnt')"] format and
+ System 7
+
+ Apple's new System 7.0 supports a new format of outline font that
+ will allow high-quality characters of any size to be displayed on
+ the screen. TrueType stores font outlines as B-spline curves
+ along with programmed resolution hints. B-spline curves are faster
+ to compute and easier to manipulate than the Bezier curves used in
+ PostScript.
+
+ Adobe is not going to support Apple's new format by converting the
+ Adobe/Linotype library to B-spline format. There are two reasons
+ for this: First, there is no support for font encryption (yes, the
+ hooks are there, but nothing is implemented). Second, Adobe does
+ not want to dilute PostScript and its font library. However, the
+ Macintosh is too big a market to simply turn away from. Therefore,
+ Adobe will provide its Font Manager to display its own fonts on
+ the Mac screen. Apple ships Adobe's ATM for this purpose.
+
+ ((( unquote )))
+
+Subject: 1.3. What about "Multiple Master" fonts?
+
+ Multiple Master Fonts are an extension to the Adobe font format.
+ providing the ability to interpolate smoothly between several "design
+ axes" from a single font. Design axes can include weight, size, and
+ even some whacko notions like serif to sans serif. Adobes' first
+ Multiple Master Font was Myriad - a two-axis font with WEIGHT (light to
+ black) on one axis, and WIDTH (condensed to expanded) along the other
+ axis. In the case of Myriad, there are four "polar" designs at the
+ "corners" of the design space. The four designs are light condensed,
+ black condensed, light expanded, and black expanded.
+
+ Given polar designs, you can set up a "weight vector" which
+ interpolates to any point within the design space to produce a unique
+ font for a specific purpose. So you can get a "more or less condensed,
+ somewhat black face".
+
+ Multiple Master Fonts can be used on any PostScript printer. Multiple
+ Master Fonts need a new PostScript operator known as makeblendedfont.
+ The current crop of Multiple Master Fonts supply an emulation of this
+ operator so the printer doesn't need this operator.
+
+ A short tutorial on Multiple Master Fonts and makeblendedfont appears
+ in PostScript by Example, by Henry McGilton and Mary Campione,
+ published by Addison-Wesley.
+
+ Danny Thomas contributes that there are a few PostScript interpreter
+ (version)s which have bugs that appear with the emulation of the
+ makeblendedfont operator used to support Multiple Master fonts. There
+ weren't many exhibiting this problem, though it may have happened even
+ with one Adobe interpreter.
+
+Subject: 1.4. Is there a methodology to describe and classify typefaces?
+
+ There is a standard, Panose, but it is mostly ignored by typographers
+ (not because it's bad, just because they don't need it). The Panose
+ system is documented, among other places, in the Microsoft Windows 3.1
+ Programmer's Reference from Microsoft Press.
+
+ The ISO also has a scheme, but it is not Panose.
+
+ At least one book by a respected authority, Alexander Lawson, Printing
+ Types: An Introduction, describes another, less rigorous system [ed: of
+ his own], which is exposited in "An Introduction" and used without
+ exposition in his later "Anatomy of a Typeface".
+
+ There is another book, Rookledges International Typefinder, which has a
+ very complete system that uses tell-tales of individual glyphs as well
+ as overall style to index most known faces right in the book.
+
+ J. Ben Leiberman has another book on type face description.
+
+ Terry O'Donnell adds the following comments:
+
+ The current ISO system was initiated (I believe) by Archie Provan of
+ RIT--a successor to Mr. Lawson. Whereas in typographic practice or
+ teaching--only a high level classification is necessary - times have
+ changed and the current ISO system aims to accomplish something beyond
+ the high level. A major goal is to aid software to help users make
+ selections. For example, a naive user might ask for all fonts on a font
+ server which have a Roman old style appearance. Another goal would be
+ to help users with multi-lingual text: a user creating a document in
+ English using e.g. Baskerville wants to know what Arabic or Japanese
+ language font on his system/file server would harmonize well with the
+ Baskerville. It is not all in place yet--but the more detailed ISO
+ classes--and the current addition of non-latin typefaces--are an
+ attempt to address this issue.
+
+ A second goal is to help with the font substitution problem. Neither
+ ISO or Panose address the metrics issues in font substitution--but both
+ might aid software in picking the nearest style of available available
+ fonts.
+
+Subject: 1.5. What is the "f" shaped "s" called?
+
+ Both the "f" with half a crosbar (roman) and the integral sign (italic)
+ are called long-S.
+
+Subject: 1.6. What about "Colonial" Typefaces?
+
+ Why does colonial printing have that "Colonial" feel?
+ =====================================================
+
+ Colonial type was either very roughly treated by moist salt air on the
+ crossing and in colonial port cities, or was copied locally by tacky
+ techniques (such as driving used foundry type into soft lead to make
+ very soft deformable matrices), and the paper was very rough, which
+ abrades both the serifs and the hairlines. So except for the best work
+ done with new, european types, the serifs were much smaller, even
+ broken off, than the original founder/punchcutter intended. Thins
+ could be abraded by rough paper to nothingness, esp after humid salt
+ air had leached the hardener out of the alloy.
+
+ Peter Honig contributes the following alternative explanation of the
+ roughness of colonial types:
+
+ The roughness of early fonts was caused by several factors: Type was
+ quite expensive and was used for many years (even if somewhat damaged).
+ Also, printing presses would only be set up to print one side of one
+ folio at a time, so you would not need to set more than a couple of
+ pages at once. This meant that the printer did not need as many copies
+ of each character, however, each character got used very frequently.
+ The early casting techniques did not produce as perfect or consistant
+ examples as we have today. That is, the face of a character might not
+ be quite planar with the page, or its sides might not be quite
+ parallel. Lastly, the inks of the past were not as advanced those of
+ today.
+
+ What fonts are good for mock-colonial uses?
+ ===========================================
+
+ For example, what fonts have the following features: old-style figures
+ (non-lining numbers), the long s character, slightly irregular shapes
+ (a la type produced by colonial printers), and a decent complement of
+ ligatures. And what about free or cheap faces like this?
+
+ I don't know if any exist with all of 1-5. As I believe you get what
+ you pay for, especially in fonts, I haven't looked at free and
+ cheap-copy fonts.
+
+ Microsoft's expansion set for their Win3.1 optional fonts has Garamond
+ Expert & Expert Extensions, which has a good complement of ligatures
+ and I think I remember it having the long ess too. I forget about
+ OSFigs; it should tho'. Monotype's metal faces "16th Century Roman"
+ and "Poliphilus" may be available in digital; if so, they imitate early
+ presswork with early and are very close to what one wants.
+
+ "A commercial supplier [not yet sampled] is Image Club Graphics in
+ Calgary (1-800-661-9410). It is called Caslon Antique. It is supplied
+ as both roman and italic, together, for $25. They advertise in
+ MacWorld/MacUser/MacBlah. I am unable to tell from abcDEF123 if the
+ numerals are old-style, but I think not. Ligatures? long-S? Not yet
+ known. Guillemots, though, are there. ... Letraset, circa 1977,
+ showing a Caslon Antique with modern numerals, no ligatures, and only
+ UKPounds and German ss extensions." [Ike Stoddard]
+
+ NB: Caslon Antique is not a Caslon per se: "The last Caslon to mention
+ is that ubiquitous but unrelated Caslon Antique, which possesses no
+ similarity whatsoever to the original. This old reprobate was
+ introduced by Barnhart Brothers of Chicago under the name Fifteenth
+ Century. Its negative reception lasted until about 1918, when, with a
+ simple name change to Caslon Antique, it became the most commonly
+ selected type for reproductions of colonial American printing. It is
+ now seen in everything from liquor advertisments to furniture
+ commercials" [Lawson, 1990,Anatomy]
+
+ Miles Agfa (Compugraphic) has always had a Caslon Antique; I don't know
+ if it is available for TrueType or Type 1, but Agfa has been doing
+ TrueType bundles at reasonable prices. [wdr]
+
+ Peter Honig contributes the following suggestions:
+
+ Name Year Irreg. Long S OSfig Comment ---
+ --- ----- ----- ---- ------
+
+ * Poliphilus A cleaned-up reproduction of type from 1499. It's only
+ slightly irregular and does not contain the long S, but does have
+ old style figures. From Italy, founded by Francesco Griffo.
+
+ * Old Claude An exact reproduction of Garamond from 1532. It is
+ irregular and does not contain the long S, but it does have old
+ style figures. From France, founded by Claude Garamond.
+
+ * Blado An exact reproduction of type from 1539. It is irregular
+ and does not contain the long S, but it does have old style
+ figures. From Italy, founded by Antinio Blado (designed by
+ Ludovico delgi Arrighi).
+
+ * Van Dijck An exact reproduction of type from the 1660s. It is
+ irregular and does not contain the long S, but it does have old
+ style figures. From Holland, founded by Van Dijck.
+
+ * Adobe Caslon A cleaned-up reproduction of type from the 1720s. It
+ isn't irregular but it does contain the long S, old style figures,
+ and several ligatures. From England, founded by William Caslon.
+
+ Blado, Poliphilus, and Van Dijck are available from Monotype. Adobe
+ Caslon is available from Adobe. Old Claude is available from Letter
+ Perfect. In my opinion, Old Claude is font that is worthy of close
+ attention. Although it lacks the long S, it is VERY accurately
+ reproduced. Although Adobe Caslon is not irregular, it has a great set
+ of authentic ornaments from the Renaissance and Baroque. It is also the
+ only set that I am aware of, that has the long S and its ligatures.
+
+ [Bill Troop notes: I do not believe that Monotype ever had a font called
+ 16th Century Roman. You are thinking of a private face created by Paul
+ Hayden-Duensing for his private press based on old Italian punches. It
+ is very rough indeed, but I can assure you no Colonial printer had a
+ typeface as stylish.
+
+ Poliphilus does indeed exist in digital form, and is fairly faithful,
+ but again is far too stylish to give the proper feel of US Colonial
+ printing. Nor is Antique Caslon, so called, anything to do with the
+ Caslon types used by American printers-except those who used this bogus
+ type at the end of the 19th century.
+
+ Monotype Bell is a faithful copy of a font that was actually used in
+ the US, but it is far more modern than the Caslon types. Nobody has yet
+ done a really authentic Caslon, and it is a curious fact, but none of
+ the Caslon revivals, in any of metal, photo, or digital formats, has
+ ever been based on the best Caslon sizes. I have been toying with such
+ a revival.
+
+ Monotype Van Dijk can hardly be called a faithful copy of a metal font;
+ the outlines are far more regular, for instance, than what Monotype did
+ for Bell. In addition, the less interesting forms of the lower case f
+ and f-ligatures were chosen for the digital version, and the alternate
+ f was not supplied. That makes it a very uninteresting font to use in
+ digital form. In addition, the italic has been unbelievably badly
+ spaced in the digital version. (Harry Carter complained about the
+ spacing in the 13pt Roman in the metal version.)
+
+ For anyone wishing to recreate the feel of early-to-mid 18th century
+ printing, a battered, sensitive revival of Caslon would be desirable.
+ The Giampa version is interesting, but is based on a poor model. ]
+
+ What fonts could a colonial printer have had?
+ =============================================
+
+ According to D.B.Updike in the classic reference "Printing Types: Their
+ History, Forms & Use", he indicates that most colonial work was with
+ types of the Caslon Old Style fonts and cheap copies of same in the
+ 18th C. Before that, it would have been the older Dutch & English
+ faces, almost always lagging English tastes. If you can find the
+ Oxford Fell types, they are classic Dutch-as-used-by-englishmen.
+ Anything with a Dutch moniker and the Oldstyle adjective is probably
+ ok; Van Dijck if you find it, say (died 1673).
+
+ Ben Franklin recommended Caslon faces. But these were not available in
+ England before 1720, first full broadside in 1734. Lawson declares that
+ the first printing of the Declaration of Independance was in Caslon.
+
+ Wilson's Scotch Modern was the "modern" font that surfaced in quantity
+ in america. If the Scotch Roman your vendor has is sort-of like-Bodoni
+ but nicer than his Bodoni, that's it. It wasn't available until late
+ 1700s, though.
+
+Subject: 1.7. What is "Point Size"?
+
+ This article was constructed from a posting by William D. Ricker from
+ Sep 1992.
+
+ In general terms, point size is a relative measure of the size of a
+ font. It used to have a more concrete meaning in the "old days" of
+ typeography.
+
+ In the world of Photo-typesetters and digital fonts, the distance from
+ the top of the tallest ascender to the bottom of the longest descender
+ is only an approximate lower bound on the point size of a font; in the
+ Old days, it was almost always a firm lower bound, and there was warning
+ on the exception.
+
+ Point-size is the measure of default or minimum inter-baseline
+ distance; inter line distance in absense of leading, a/k/a "set solid".
+ If you don't know if the text was set solid or leaded, you can't tell
+ the point-size with a measuring glass unless you know if the type design
+ includes built-in space betweed adjacent, set-solid lines.
+
+ Exceptions to the points size equals ascender to descender size rule:
+
+ * In metal, there was usually a little room between the highest and
+ lowest corners of the face and the body size, so that the Matrix
+ was completely molding the face and not relying on the mold-body
+ to form a vertical side to the printing face--since a bevel or
+ beard is desirable for impression and strength.
+
+ * If the designer of a face thinks it should always be set leaded,
+ s/he may choose to include the minimal leading in the design, in
+ which case it is included in the base point size, and no capital,
+ lowercase-ascender, or lowercase-descender will get very near the
+ edges.
+
+ * In some faces the capitals are taller than the ascenders, and
+ others vice versa. (Vertical sticks on capitals are called stems,
+ not ascenders.) A minimum point size estimate would normally be
+ the height of the font's "envelope", to borrow from
+ Avionics/Aeronautics.
+
+ * The point size of a "Titling Face" may not include descenders; in
+ which case the Q's tail hangs off the body as a vertical kern.
+ Such a face in metal usually has "Titling" in the name, although
+ sometimes the fact that only capitals are available is all the
+ hint given.
+
+ ([William D. Ricker's] metal font of Ray Shaded, cast on a Monotype
+ Display caster, has "vertical kerns" if you will: the hanging
+ shaded tail of the Q and some punctuation below the 24pt body,
+ because it has no lower-case. It might be better described as
+ being 36/24, thirty-six point type cast on a twenty-four point
+ body, since the cap A is about the height and density of a
+ Ultrabold 36pt A in many other fonts. It would be called 36/24
+ Caps if a lowercase had been cast on a 36 point body, but since
+ only UC was ever cut, as UC-only titling, it was standardly issued
+ and refered to as a 24 point titling--much to the confusion of
+ non-cognoscenti.)
+
+ * The Continental Point, a/k/a the Didot point, (and its Pica Em
+ equivalent, the Cicero) is just a hair longer. 15 Ciceros=16
+ Picas, 15 Didots=16 Points. So type which is imported or cast
+ from imported matrices has been, and still is, cast on the next
+ size larger body in anglo-american points. So an 11D/12 or 12D/14
+ type will look larger than a similar 12pt font but smaller than a
+ simlar 14pt font, by about a point of fixed built-in leading that
+ the designer didn't intend. What happened when these faces were
+ converted to photo and digital composition, I don't know. (I
+ could find out.) Probably some were scaled to American sizes
+ proportionally from the european masters, some copied from the
+ American castings with built-in leading to ease conversion, and
+ some were probably done both ways at different conversion houses.
+
+ Net result: unless you know it's Adobe Times Roman or whatever and just
+ want to know what point size & leading options were, you can't measure
+ the size with a definition and an optical micrometer. The defnition is
+ embodied/manifested in the typesetting "hardware", even if it is
+ software, not the product.
+
+ Knuth's Assertion
+ =================
+
+ What about Knuth's assertion that point size is "a more-or-less
+ arbitrary number that reflects the size of type [a font] is intended to
+ blend with"?
+
+ That statement is true only in the context of MetaFonts. MetaFonts
+ (and this definition) are perfectly adequate for Knuth's purposes but
+ not fully descriptive of all of typography. And definitely not
+ conformant to established usage.
+
+ This is not meant to condemn heterodoxy, but just to warn that while the
+ ASCII markup notations in Knuth's "Second Great Work" [TeX and MetaFont]
+ are even more widely disseminated than his wonderful coinage of
+ mathematical notations in "The First Great Work" [The Art of Computer
+ Programming, volumes I, II, and III], MetaFont has not been accepted as
+ an encoding for all useful fonts for the future, and the defintions of
+ font characteristics in MetaFont context must be taken with a large
+ grain of salt when used with fonts outside the MetaFont font-generation
+ paradigm.
+
+ Knuth's quotation, when applied to a (non-MetaFont) font designer,
+ overstates the arbitrariness of the design choice; the designer was
+ stating in the old days that you'd need a saw, a file, or a caster with
+ his matrices if you wanted to use negative leading to set his type
+ closer than he wanted to see it set; and today, in Photo/digital
+ composition, the designer is either indicating the opinion of the
+ original metal-head or his own design advice as to what the minimum
+ distance between adjacent baselines should be.
+
+ Also, point size is very poor predictor of blending, except in a
+ mechanical sense in terms of not-overflowing the same rectangles. Some
+ faces to blend in the same line with 12 point type will need to be
+ 10/12 or 14/12, due to differences in the way they fill the space.
+ (The overall leading should fit the body type.) Harmony and contrast of
+ overall color, shape, style, etc. are much more important considerations
+ for blending than body-size. (For two types to work together, there
+ must be sufficient harmonies between them to work together and
+ sufficent contrasts to be easily distinguished. See Carl Dair's books.)
+
+ If one wants to understand usage of typographical terms in the general
+ milieu, the Chicago Manual of Style's appendix on Typesetting for
+ Authors is a good capsule presentation of history and terminology; if
+ one wants the nitty-gritty on how digital type does, or at least
+ should, differ and be treated differently from just copies of metal,
+ see Richard Rubinstein, Digital Typography, MIT Press. On type in
+ general, consult D.B. Updike in a library (out of print), or
+ A(lexander) S. Lawson (who covers electronic type in his latest
+ revision!).
+
+Subject: 1.8. Where can I get ... fonts.
+
+ Before I go any farther, let me extol the virtues of the Archie servers.
+ If you need to find something on the net, and you have any idea what it
+ might be called, Archie is the place to go. In North America, telnet to
+ "archie.rutgers.edu" and login as "archie". There are many other
+ servers around the world, any Archie server can give you a list of other
+ servers. There are better documents than this to describe Archie and
+ you should be able to find them from the above starting point. If you
+ have trouble, feel free to ask norm (via Email please, no need to
+ clutter comp.fonts with a query about Archie ;-).
+
+ In addition to the telnet option, several archie clients exist including
+ a very nice X11 implementation (Xarchie).
+
+ * Adobe Type 1 Fonts in MS-DOS/Unix Format:
+
+ ftp.cica.indiana.edu:/pub/pc/win3/fonts
+
+ ftp.cica.indiana.edu:/pub/pc/win3/fonts/atm
+
+ archive.umich.edu:/msdos/mswindows/fonts
+
+ * Adobe Type 1 Fonts in Mac Format:
+
+ mac.archive.umich.edu:/mac/system.extensions/font/type1
+
+ sumex-aim.stanford.edu:/info-mac/font
+
+ * Adobe Type 3 Fonts in Mac Format:
+
+ mac.archive.umich.edu:/mac/system.extensions/font/type3
+
+ * TrueType fonts in MS-DOS Format:
+
+ ftp.cica.indiana.edu:/pub/pc/win3/fonts/truetype
+
+ * TrueType fonts in Mac Format:
+
+ mac.archive.umich.edu:/mac/system.extensions/font/truetype
+
+ * TeX PK/PXL/GF fonts:
+
+ The TeX community has its own support groups that can provide
+ better answers to this question. The canonical list of MetaFont
+ fonts is posted occasionally to comp.text.tex. The comp.text.tex
+ newsgroup (or the Info-TeX mailing list, if you do not have access
+ to news) are good places to start. Email norm if you need more
+ specific information.
+
+ * LaserJet bitmap fonts:
+
+ wuarchive.wustl.edu:/mirrors/msdos/laser
+
+ Also on other simtel20 mirrors...
+
+ If you know of other archive sites (the above list is no where near
+ complete) or other formats that are available on the net, please let us
+ know.
+
+ The sites above represent places where shareware and public domain fonts
+ are available. Many, many typefaces are not available in shareware
+ form. And many shareware faces are less than adequate for a variety of
+ reasons, particularly at small sizes. It seems to be the consensus of
+ the comp.fonts community that "you get what you pay for." If you need a
+ professional quality font, you should probably buy it from a
+ professional.
+
+ The list of font vendors in Appendix A (annotated with information about
+ non-Roman alphabets) was contributed by Masumi Abe. Masumi was Adobe's
+ Manager of Typographic Marketing for Asia. He has since left Adobe.
+
+ Many font CDs are now available which offer many fonts for a low
+ cost/font.
+
+Subject: 1.9. Where can I get fonts for non-Roman alphabets?
+
+ As mentioned above, the list of font vendors is annotated with
+ information about non-Roman alphabets. Commercially, Masumi suggests
+ that Linguists' Software is the current [ed: as of 7/92] leading
+ supplier of non-Roman fonts.
+
+ Ian Tresman contributes:
+
+ The Multilingual PC Directory is a source guide to multilingual and
+ foreign language software, including fonts, for PCs. Over a hundred
+ different languages are included, from Arabic to Hieroglyphics to Zulu.
+ A 1200 word description is available from the publishers, Knowledge
+ Computing, email: 72240.3447@compuserve.com.
+
+Subject: 1.10. What about fonts with the International Phonetic Alphabet (IPA) symbols?
+
+ I summarized Scott Brumage's recent post for the FAQ:
+
+ Shareware or free (PostScript Type 1 and/or TrueType):
+ ======================================================
+
+ * TechPhon
+
+ Seems to lack some characters and has no zero-offset characters
+ (for accents).
+
+ * PalPhon
+
+ A phonetic font which you can get by anonymous ftp from
+ mac.archive.umich.edu. It is called PalPhon. There are actually
+ two fonts: the basic PalPhon and one with additional accents and
+ symbols called PalPi. The package includes some documents on using
+ the fonts as well.
+
+ * SIL-IPA
+
+ SIL-IPA is a set of scalable IPA fonts containing the full
+ International Phonetic Alphabet with 1990 Kiel revisions. Three
+ typefaces are included:
+
+ * SIL Doulos (similar to Times)
+
+ * SIL Sophia (similar to Helvetica)
+
+ * SIL Manuscript (monowidth)
+
+ Each font contains all the standard IPA discrete characters and
+ non-spacing diacritics as well as some suprasegmental and
+ puncuation marks. Each font comes in both PostScript Type 1 and
+ TrueType formats. The fonts are also available for Microsoft
+ Windows.
+
+ These fonts were designed by the Printing Arts Department of the
+ Summer Institute of Linguistics, Dallas, Texas.
+
+ Shareware or free (TeX):
+ ========================
+
+ METAFONT sources of the phonetic symbols developed by
+ Tokyo-Shoseki-Printing and Sanseido are available. The font contains
+ all of IPA (Internatioanl Phonetic Alphabet) symbols.
+
+ You can get phonetic symbols METAFONT (named TSIPA) from
+
+ ftp.foretune.co.jp:/pub/tools/TeX/Fonts
+
+ The IP address for ftp.foretune.co.jp is 133.123.1.2.
+
+ Commercial:
+ ===========
+
+ Linguist's Software Adobe (ITC Stone Phonetic [#255], Times Phonetic
+ [#278])
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 1.11. How can I convert my ... font to ... format?
+
+ Conversion from one bitmapped format to another is not generally too
+ difficult. Conversion from one scalable format to another is very
+ difficult. Several commercial software packages claim to perform these
+ tasks, but none has been favorably reviewed by the comp.fonts community.
+
+ Converting Between TrueType and Adobe Type 1 Formats
+ ====================================================
+
+ This section was constructed from postings by Primoz Peterlin and Bert
+ Medley in Sep 1993.
+
+ There are several commercial tools that will convert between these
+ formats. There are no shareware or free tools that will do the job.
+ See also "Why do converted fonts look so bad?".
+
+ FontMonger by Ares Software
+ ---------------------------
+
+ Performs conversion between Adobe Type 1, Adobe Type 3 and TrueType
+ formats in both PC-DOS and Mac flavours, as well as simple glyph
+ editing. Currently at version 1.0.7, patches available via CompuServe.
+ Available for Mac and MS Windows. Commercial product, price \$60-80.
+
+ Alltype by Atech Software
+ -------------------------
+
+ Performs font conversion. A stable product, being on a market for a
+ while. Available for PC-DOS/MS Windows only. Commercial product.
+ Atech is supposedly leaving the business.
+
+ Fontographer by Altsys Co.
+ --------------------------
+
+ Comprehensive package, allowing creation of fonts as well as conversion
+ between formats. Available for Mac and MS Windows. Commercial
+ product, price cca. \$270 (PC version).
+
+ Metamorphosis by Altsys Co.
+ ---------------------------
+
+ Available for Mac. Commercial product. More info needed.
+
+ Converting Between Other Scalable Formats
+ =========================================
+
+ Many of the programs in the preceding section claim to be able to
+ convert between other formats as well. And there are probably other
+ commercial programs as well. However, as several people have noted,
+ conversion from one scalable format to another is a bad idea. If the
+ original font was well hinted, the converted font will not be. Of
+ course, if the original was poorly hinted, maybe it won't matter much.
+
+ In an effort to settle a long-running and oft-asked question, I'll be
+ blunt: as of today [6/93], THERE ARE NO NON-COMMERCIAL PROGRAMS WHICH
+ WILL CONVERT FROM ONE SCALABLE FORMAT TO ANOTHER. Not from TrueType to
+ PostScript Type 1, Type 3, Type 5, or any other scalable PostScript
+ format. Not from PostScript Type 1 to TrueType. Not to or from
+ Intellifont. Not to or from Sun F3 format.
+
+ For specific conversions, check the platform specific parts of the FAQ.
+ Most of the conversions discussed require platform specific tools.
+
+ Here is a summary of the conversions discussed (and the section in
+ which they appear):
+
+ Mac Type 1 PostScript
+ To PC Type 1 PostScript (MS-DOS). To TrueType (commercial).
+
+ PC Type 1 PostScript
+ To Mac Type 1 PostScript (Mac, commercial). To TrueType
+ (commercial). To TeX PK (MS-DOS).
+
+ TrueType
+ To Type 1 PostScript (Mac and MS-DOS, commercial). To HP LaserJet
+ bitmaps (MS-DOS, hack!).
+
+ TeX PK
+ To HP LaserJet bitmap softfonts (MS-DOS).
+
+ HP LaserJet bitmap softfonts
+ To TeX PK (MS-DOS).
+
+ In addition, Adobe ships a copy of Adobe Font Foundry with all of its
+ fonts which can convert Type 1 fonts into HP LaserJet softfonts.
+
+ Why Do Converted Fonts Look So Bad?
+ ===================================
+
+ This section was constructed from postings by Mark Hastings and David
+ Glenn in Aug 1993.
+
+ With all commercially available conversion tools, converting fonts
+ between scalable formats almost always results in a font inferior to
+ the original. (The rare case where a converted font is not inferior to
+ the original occurs only when the original is a cheap knock-off, and
+ the automatic hinting of the conversion program is better than
+ automatic hinting used in the original!)
+
+ David Glenn contributes the following analysis:
+
+ There are a few probable [reasons why converted fonts, especially screen
+ fonts, look inferior to the original]. First off, any font that's
+ converted uses a converting algorithm which will make an exact copy at
+ best. Because no currently available converter even comes close to
+ copying faithfully the manual tweaks and hinting in a font file, you
+ often end up with poor screen fonts and poor output. The only reason
+ that printed output from the converted font looks markedly better than
+ the screen font is that the printed output is at a higher resolution.
+ The converter achieves better results on the higher resolutions because
+ hinting is less important at higher resolutions. Screen fonts are
+ incredibly complex to make well. You have very few pixels to represent
+ a very aesthetic and distinct design. That's why at small sizes almost
+ all typefaces look alike--how do you represent a graceful concave side
+ on the letter "L" for Optima with only 12 pixels in height and one in
+ width? You can't. And that's why most fonts look similar at 10pt,
+ unless they're hand hinted by typograhers.
+
+ One thing that may come into play when fonts are converted between
+ platforms, for example between PC/Windows format and Mac format, is that
+ fonts are hinted down to a certain number of pixels per em. On a Mac
+ screen (72 dpi) there is a one-to-one correspondence between the ppem
+ and the point size of a font. Under windows, the usual VGA screen is
+ 96dpi and fonts that look good at 8 or 9 pt under windows might look
+ like crap on a Mac 'cuz the fonts weren't hinted below 10 or 11ppem.
+ Also, the conversion programs may have made the appearance worse at
+ some sizes than others.
+
+ Whenever you convert fonts from one platform to the other keep in mind
+ that:
+
+ * Your license with the type foundry may or may not allow this.
+
+ * The font may or may not have the correct character sets in it.
+
+ * The TT font file may or may not have all the tables necessary.
+
+ * Your converter may make it so ugly that you don't want to use it...
+
+ Smoothing Bitmaps
+ =================
+
+ This section was constructed from postings by Jason Lee Weiler and
+ Piercarlo Antonio Grandi
+
+ Enlarging bitmapped images is easy, but enlarging them without creating
+ very jagged edges is much more demanding. There are several
+ possibilities.
+
+ * If you are interested in programming your own solution, the
+ comp.graphics FAQ will provide pointers to a number of resources
+ that can get you started.
+
+ * If the bitmaps are in a standard format, the 'xv' tool (an X11
+ picture viewing tool) includes magnify and smooth functions that
+ may perform adequately.
+
+ * Commercial tools like Adobe Illustrator, Corel Draw, and many
+ others include tracing functions that can translate some bitmaps
+ into acceptable outlines (which can be enlarged without
+ jaggedness).
+
+ * The GNU Font Utilities include a tracing tool that may be helpful.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(2_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(2_6)
new file mode 100644
index 0000000000..2d6e85aa0a
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(2_6)
@@ -0,0 +1,1143 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (2/6)
+Supersedes: <font-faq-2_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:14 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 1120
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-2_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48299 comp.answers:20513 news.answers:79234
+
+Archive-name: fonts-faq/part2
+Version: 2.1.5
+
+Subject: 1.12. Are fonts copyrightable?
+
+ This topic is hotly debated at regular intervals on comp.fonts. Terry
+ Carroll. provides the following analysis of current [ed: as of 6/92]
+ legislation and regulation regarding fonts and copyrights in the United
+ States. Terry is "Editor in Chief" of Volume 10 of the Santa Clara
+ Computer and High Technology Law Journal. Members of the comp.fonts
+ community are encouraged to submit other materials that add clarity to
+ the issue.
+
+ It has been pointed out that this section deals primarily font copyright
+ issues relevant to the United States and that this situation is not
+ universal. For example, in many parts of Europe typeface designs are
+ protectable.
+
+ "First, the short answer in the USA: Typefaces are not copyrightable;
+ bitmapped fonts are not copyrightable, but scalable fonts are
+ copyrightable. Authorities for these conclusions follow.
+
+ Before we get started, let's get some terminology down:
+
+ A typeface is a set of letters, numbers, or other symbolic characters,
+ whose forms are related by repeating design elements consistently
+ applied in a notational system and are intended to be embodied in
+ articles whose intrinsic utilitarian function is for use in composing
+ text or other cognizable combinations of characters.
+
+ A font is the computer file or program that is used to represent or
+ create the typeface.
+
+ Now, on to the legal authorities:
+
+ Volume 37 of the Code of Federal Regulations specifies this about the
+ copyrightability of typefaces:
+
+ "The following are examples of works not subject to copyright and
+ applications for registration of such works cannot be entertained: . . .
+ typeface as typeface" 37 CFR 202.1(e).
+
+ The regulation is in accordance with the House of Representatives report
+ that accompanied the new copyright law, when it was passed in 1976:
+
+ "The Committee has considered, but chosen to defer, the possibility of
+ protecting the design of typefaces. A 'typeface' can be defined as a
+ set of letters, numbers, or other symbolic characters, whose forms are
+ related by repeating design elements consistently applied in a
+ notational system and are intended to be embodied in articles whose
+ intrinsic utilitarian function is for use in composing text or other
+ cognizable combinations of characters. The Committee does not regard
+ the design of typeface, as thus defined, to be a copyrightable
+ 'pictorial, graphic, or sculptural work' within the meaning of this bill
+ and the application of the dividing line in section 101." H. R. Rep.
+ No. 94-1476, 94th Congress, 2d Session at 55 (1976), reprinted in 1978
+ U.S. Cong. and Admin. News 5659, 5668.
+
+ It's also in accordance with the one court case I know of that has
+ considered the matter: Eltra Corp. V. Ringer, 579 F.2d 294, 208 USPQ 1
+ (1978, C.A. 4, Va.).
+
+ The U.S. Copyright Office holds that a bitmapped font is nothing more
+ than a computerized representation of a typeface, and as such is not
+ copyrightable:
+
+ "The [September 29, 1988] Policy Decision [published at 53 FR 38110]
+ based on the [October 10,] 1986 Notice of Inquiry [published at 51 FR
+ 36410] reiterated a number of previous registration decisions made by
+ the [Copyright] Office. First, under existing law, typeface as such is
+ not registerable. The Policy Decision then went on to state the
+ Office's position that 'data that merely represents an electronic
+ depiction of a particular typeface or individual letterform' [that is, a
+ bitmapped font] is also not registerable." 57 FR 6201.
+
+ However, scalable fonts are, in the opinion of the Copyright Office,
+ computer programs, and as such are copyrightable:
+
+ "... the Copyright Office is persuaded that creating scalable typefonts
+ using already-digitized typeface represents a significant change in the
+ industry since our previous [September 29, 1988] Policy Decision. We
+ are also persuaded that computer programs designed for generating
+ typeface in conjunction with low resolution and other printing devices
+ may involve original computer instructions entitled protection under the
+ Copyright Act. For example, the creation of scalable font output
+ programs to produce harmonious fonts consisting of hundreds of
+ characters typically involves many decisions in drafting the
+ instructions that drive the printer. The expression of these decisions
+ is neither limited by the unprotectable shape of the letters nor
+ functionally mandated. This expression, assuming it meets the usual
+ standard of authorship, is thus registerable as a computer program." 57
+ FR 6202."
+
+Subject: 1.13. Typeface Protection
+
+ [This article first appeared in TUGboat 7:3 (October 1986), pp. 146-151.
+ Reproduced with permission.]
+
+ Preamble
+ ========
+
+ The main question of typeface protection is: "Is there anything there
+ worth protecting?" To that the answer must certainly be: "Yes." Typeface
+ designs are a form of artistic and intellectual property." To
+ understand this better, it is helpful to look at who designs type, and
+ what the task requires.
+
+ Who makes type designs?
+ -----------------------
+
+ Like other artistic forms, type is created by skilled artisans. They
+ may be called type designers, lettering artists, punch-cutters,
+ calligraphers, or related terms, depending on the milieu in which the
+ designer works and the technology used for making the designs or for
+ producing the type.
+
+ ("Type designer" and "lettering artist" are self-explanatory terms.
+ "Punch-cutter" refers to the traditional craft of cutting the master
+ image of a typographic letter at the actual size on a blank of steel
+ that is then used to make the matrix from which metal type is cast.
+ Punch-cutting is an obsolete though not quite extinct craft. Seeking a
+ link to the tradition, modern makers of digital type sometimes use the
+ anachronistic term "digital punch-cutter". "Calligrapher" means
+ literally "one who makes beautiful marks". The particular marks are
+ usually hand-written letters, though calligraphers may design type, and
+ type designers may do calligraphy.)
+
+ It usually takes about seven years of study and practice to become a
+ competent type designer. This seems to be true whether one has a Ph.D.
+ in computer science, a high-school diploma, or no academic degree. The
+ skill is acquired through study of the visual forms and practice in
+ making them. As with geometry, there is no royal road.
+
+ The designing of a typeface can require several months to several years.
+ A family of typefaces of four different styles, say roman, italic, bold
+ roman, and bold italic, is a major investment of time and effort. Most
+ type designers work as individuals. A few work in partnership (Times
+ Roman(R), Helvetica(R), and Lucida(R) were all, in different ways, the
+ result of design collaboration). In Japan, the large character sets
+ required for a typeface containing Kanji, Katakana, and Hiragana induce
+ designers to work in teams of several people.
+
+ Although comparisons with other media can only be approximate, a
+ typeface family is an accomplishment on the order of a novel, a feature
+ film screenplay, a computer language design and implementation, a major
+ musical composition, a monumental sculpture, or other artistic or
+ technical endeavors that consume a year or more of intensive creative
+ effort. These other creative activities can be protected by copyright
+ or other forms of intellectual property protection. It is reasonable
+ to protect typefaces in the same way.
+
+ The problem of plagiarism
+ -------------------------
+
+ A lack of protection for typeface designs leads to plagiarism, piracy,
+ and related deplorable activities. They are deplorable because they
+ harm a broad range of people beyond the original designers of the type.
+ First, most type plagiarisms are badly done. The plagiarists do not
+ understand the nature of the designs they are imitating, are unwilling
+ to spend the necessary time and effort to do good work, and
+ consequently botch the job. They then try to fob off their junk on
+ unsuspecting users (authors, editors, and readers). Without copyright,
+ the original designer cannot require the reproducer of a type to do a
+ good job of reproduction. Hence, type quality is degraded by
+ unauthorized copying.
+
+ Secondly, without protection, designs may be freely imitated; the
+ plagiarist robs the original designer of financial compensation for the
+ work. This discourages creative designers from entering and working in
+ the field. As the needs of typography change (on-line documents and
+ laser printing are examples of technical and conceptual changes) new
+ kinds of typefaces are required. Creative design in response to such
+ needs cannot flourish without some kind of encouragement for the
+ creators. In a capitalist society, the common method is property rights
+ and profit. In a socialist (or, in the past, royalist) society, the
+ state itself might employ type artists. France, as a monarchy and as a
+ republic, has had occasional state sponsorship of typeface design over
+ the past 400 years. The Soviet Union has sponsored the design of new
+ typefaces, not only in the Cyrillic alphabet, but also in the other
+ exotic scripts used by various national groups in the Soviet Union.
+
+ Those who would justify plagiarism often claim that the type artists do
+ not usually receive a fair share of royalties anyway, since they have
+ usually sold their designs to some large, exploitive corporation. It
+ is true that type designers, like many artists, are often exploited by
+ their "publishers", but plagiarism exacerbates the problem. Plagiarism
+ deprives the designer of decent revenues because it diverts profits to
+ those who merely copied the designs. Plagiarism gives the manufacturer
+ yet another excuse to reduce the basic royalty or other fee paid for
+ typeface designs; the theme song is that the market determines the
+ value of the design and cheap rip-offs debase the value of a face. For
+ those interested in the economic effects of piracy, it is clear that
+ plagiarism of type designs ultimately hurts individual artists far more
+ than it hurts impersonal corporations.
+
+ Kinds of protection for type
+ ----------------------------
+
+ There are five main forms of protection for typefaces:
+ * Trademark
+
+ * Copyright
+
+ * Patent
+
+ * Trade Secret
+
+ * Ethics
+
+ Trademark
+ .........
+
+ A trademark protects the name of a typeface. In the U.S., most
+ trademarks are registered with the U.S. Patent and Trademark Office.
+ The R in a circle (R) after a trademark or tradename indicates U.S.
+ registration. The similarly placed TM indicates that a trademark is
+ claimed, even if not yet officially registered. However, a trademark may
+ be achieved through use and practice, even without registration. Owners
+ of trademarks maintain ownership by use of the trademark and by
+ litigation to prevent infringement or unauthorized use of the trademark
+ by others.
+
+ As a few examples of registered typeface trademarks, there are Times
+ Roman (U.S. registration 417,439, October 30, 1945 to Eltra
+ Corporation, now part of Allied); Helvetica (U.S. registration 825,989,
+ March 21, 1967, also to Eltra-Allied), and Lucida (U.S. reg. 1,314,574
+ to Bigelow & Holmes). Most countries offer trademark registration and
+ protection, and it is common for a typeface name to be registered in
+ many countries. In some cases the registrant may be different than the
+ originator. For example, The Times New Roman (Times Roman) was
+ originally produced by the English Monotype Corporation. In England and
+ Europe, most typographers consider the design to belong to Monotype,
+ but the trademark was registered by Linotype (Eltra-Allied) in the
+ U.S., as noted above.
+
+ Trademark protection does not protect the design, only the name.
+ Therefore, a plagiarism of a design is usually christened with a
+ pseudonym which in some way resembles or suggests the original
+ trademark, without actually infringing on it. Resemblance without
+ infringement can be a fine distinction.
+
+ Some pseudonyms for Times Roman are: "English Times", "London", Press
+ Roman, "Tms Rmn". Some for Helvetica are "Helios", "Geneva",
+ "Megaron", "Triumvirate". So far, there seem to be none for Lucida.
+ There are generic typeface classifications used by typographers and type
+ historians to discuss styles, trends, and categories of design.
+ Occasionally these apparently innocuous classification systems are
+ employed by plagiarists to devise generic pseudonyms, such as "Swiss
+ 721" for Helvetica, and "Dutch 801" for Times Roman. It is not certain
+ whether this usage of a generic classification is more for
+ clarification or for obfuscation. In general, the proper tradename is a
+ better indicator of identity, quality, and provenance in typefaces than
+ a generic name. Some people believe that the same is true for other
+ commodities such as wine, where taste is important.
+
+ A trademark usually consists of both a proprietary and a generic part.
+ For example, in the name "Lucida Bold Italic", "Lucida" is the
+ proprietary trademark part and "Bold Italic" is the generic part. The
+ generic word "type" is usually understood to be a part of the name,
+ e.g. "Lucida Bold Italic type". Sometimes a firm will append its name
+ or a trademarked abbreviation of it to the typeface name, to achieve a
+ greater degree of proprietary content, e.g. "B&H Lucida Bold Italic".
+
+ A related matter is the use of the name of a type's designer. A firm
+ that ethically licenses a typeface will often cite the name of the
+ designer-- e.g. Stanley Morison (with Victor Lardent) for Times Roman,
+ Max Miedinger (with Edouard Hoffmann) for Helvetica, Charles Bigelow
+ and Kris Holmes for Lucida. Although a person's name is not usually a
+ registered trademark, there are common law restrictions on its use.
+ The marketing of plagiarized type designs generally omits the names of
+ the designers.
+
+ Although Trademark is an incomplete kind of protection, it is used
+ effectively (within its limitations) to prevent the theft of type names.
+ Certain traditional typeface names, usually the surnames of illustrious
+ designers like Garamond, Caslon, Baskerville, Bodoni, and others have
+ become generic names in the public domain. Trademark protection of
+ such names requires the addition of some proprietary word(s), as with
+ these hypothetical creations, "Acme New Garamond", or "Typoluxe
+ Meta-Baskerville".
+
+ Copyright
+ .........
+
+ Copyright of typefaces can be divided into two parts: copyright of the
+ design itself; and copyright of the font in which the design is
+ implemented. In the U.S., typeface designs are currently not covered by
+ copyright. This is a result of reluctance by the copyright office to
+ deal with a complex field; by lobbying against copyright by certain
+ manufacturers whose profits were based on typeface plagiarism; by a
+ reluctance of Congress to deal with the complex issues in the recent
+ revision of the copyright law.
+
+ The reluctance of Americans to press for typeface copyright may have
+ been influenced by a feeling that typeface plagiarism was good for U.S.
+ high-tech businesses who were inventing new technologies for printing,
+ and plagiarizing types of foreign origin (Europe and England). If the
+ situation becomes reversed, and foreign competition (from Japan,
+ Taiwan, and Korea) threatens to overcome American technological
+ superiority in the laser printer industry, then American firms may do
+ an about-face and seek the protection of typeface copyright to help
+ protect the domestic printer industry. Such a trend may already be seen
+ in the licensing of typeface trademarks by Adobe, Hewlett-Packard, IBM,
+ Imagen, and Xerox in the U.S. laser printer industry.
+
+ In Germany, where typeface design has always been a significant part of
+ the cultural heritage, and where typefounding has remained an important
+ business, there are more than one kind of copyright-like protections for
+ typefaces. Certain long-standing industrial design protection laws have
+ been used to protect typeface designs in litigation over royalties and
+ plagiarisms. Further, there is a recent law, the so-called
+ "Schriftzeichengesetz" enacted in 1981, that specifically protects
+ typeface designs. New designs are registered, as is done with
+ copyright in most countries. This law only protects new, original
+ designs. It is available to non-German designers and firms. Therefore,
+ some type firms and designers routinely copyright new designs in West
+ Germany. This gives a degree of protection for products marketed in
+ Germany. Since multinational corporations may find it cheaper to
+ license a design for world-wide use rather than deal with a special case
+ in one country, the German law does encourage licensing on a broader
+ scale than would initially seem to be the case.
+
+ France, like Germany, has ratified an international treaty for
+ protection of typefaces. This 1973 Vienna treaty will become
+ international law when four nations ratify it. So far, only France and
+ West Germany have done so, and thus a design must be protected
+ separately in each country. Even when the treaty becomes law, it will
+ take effect only in those countries that have ratified it. The treaty
+ was principally the work of the late Charles Peignot, a French
+ typefounder, and John Dreyfus, an English typographer and typographic
+ scholar. Presently, typefaces may be registered for protection in
+ France under a 19th century industrial design protection law.
+
+ In the U.S., there continues to be some movement for typeface design
+ protection. A proposed bill that would protect the designs of useful
+ articles, like type, has been in committee for a few years. It seems to
+ be going nowhere.
+
+ Digital (as opposed to analog) fonts may be protected by copyright of
+ digital data and of computer programs. It has been established that
+ computer software is copyrightable. Therefore, software that embodies a
+ typeface, e.g. a digital font, is presumably also protected. There is
+ some objection to this kind of copyright, on the grounds that the
+ ultimate output of the program or the result of the data (i.e. a
+ typeface design) is not copyrightable. However, the current belief
+ expressed by the National Commission on New Technological Use of
+ Copyrighted Works is that software is copyrightable even if its function
+ is to produce ultimately a non-copyrightable work. Hence, typefaces
+ produced by Metafont or PostScript(R), two computer languages which
+ represent fonts as programs, are presumably copyrightable. Typefaces
+ represented as bit-map data, run-length codes, spline outlines, and
+ other digital data formats, may also be copyrightable. Some firms do
+ copyright digital fonts as digital data. % The copyright office is
+ currently reviewing %this practice to determine if it is acceptable.
+
+ Note that the designs themselves are still not protected in the U.S. A
+ plagiarist could print out large sized letters (say, one per page) on an
+ Apple LaserWriter, using a copyrighted PostScript digital font, and then
+ redigitize those letters by using a scanner or a font digitizing program
+ and thus produce a new digital font without having copied the program or
+ digital data, and thus without infringing the copyright on the font. The
+ quality of the imitation font would usually be awful, but it wouldn't
+ violate copyright. Of course, the plagiarist would usually need to
+ rename the font to evade trademark infringement. [As I write these
+ words, I have the guilty feeling that I have just provided a recipe for
+ type rip-off, but others have obviously thought of just such a
+ scheme--John Dvorak has even proposed something like it in one of his
+ columns.]
+
+ Design Patent
+ .............
+
+ The designs of typefaces may be patented in the U.S. under existing
+ design patent law. Many designs are patented, but type designers
+ generally don't like the patent process because it is slow, expensive,
+ and uncertain. Nevertheless, some types do get patented, and it is a
+ form of potential protection. Note that this is Design Patent--the
+ typeface doesn't have to be a gizmo that does something, it merely has
+ to be unlike any previous typeface. The drawback here is that most
+ attorneys and judges are not aware that there are more than two or
+ three typefaces: say, handwriting, printing, and maybe blackletter.
+ Therefore, litigating against infringement is an educational as well as
+ a legal process. It is easy to see that typeface theft is more subtle
+ than knocking over a liquor store; it may not be illegal and the
+ returns may be greater.
+
+ Protections like design patent are available in many other countries,
+ but there is not an international standard (to my knowledge) so the
+ situation must be examined on a country by country basis.
+
+ Invention Patent
+ ................
+
+ Methods of rendering typefaces can be patented as mechanical or
+ electronic inventions. For example, the old hot-metal Linotype
+ machinery was protected by various patents, as was the IBM Selectric
+ typewriter and type ball. IBM neglected to trademark the typeface
+ names like Courier and Prestige, so once the patents had lapsed, the
+ names gradually fell into the public domain without IBM doing anything
+ about it (at the time, and for a dozen years or so, IBM was distracted
+ by a major U.S. anti-trust suit). Most students of the type protection
+ field believe that those names are probably unprotectable by now,
+ though IBM could still presumably make a try for it if sufficiently
+ motivated.
+
+ There is currently a noteworthy development regarding a patent for
+ outline representation of digital type as arcs and vectors, with special
+ hardware for decoding into rasters. This patent (U.S. 4,029,947, June
+ 14, 1977; reissue 30,679, July 14, 1981) is usually called the Evans &
+ Caswell patent, after its inventors. It was originally assigned to
+ Rockwell, and in 1982, Rockwell sued Allied Linotype for infringement.
+ Allied settled out of court, having paid an amount rumored to be in the
+ millions. Rockwell sold the patent, along with other typographic
+ technology, to Information International, Inc. (III), which then sued
+ Compugraphic for infringement. According to the Seybold Report, a
+ respected typographic industry journal, Compugraphic recently settled
+ out of court for 5 million dollars. Although many experts believe the
+ patent to be invalid because of several prior inventions similar in
+ concept, it nevertheless seems to be a money-maker in corporate
+ litigation. The Seybold Report has speculated on which firms III would
+ litigate against next. Among the candidates suggested by the Seybolds
+ was Apple for its LaserWriter, which uses outline fonts. Since the
+ entire laser printer industry and the typesetting industry is moving
+ toward outline font representation, Apple is certainly not alone. The
+ Seybolds further speculate on whether the difference between
+ character-by-character CRT typesetting and raster-scan laser typesetting
+ and printing would be legally significant in such a case. Ultimately,
+ some firm will hold out for a court judgement, and the matter will be
+ decided. %Although the Evans & Caswell patent doesn't have much to do
+ with %typeface copyright per se, it does make many font vendors nervous.
+
+ Trade Secret
+ ............
+
+ Given that typeface designs have relatively little copyright protection
+ in the U.S., they are often handled as trade secrets. The secret must
+ apply to the digital data or programs only, because the images
+ themselves are ultimately revealed to the public as printed forms. It
+ is much more difficult to reconstruct the formula of Coca-Cola from its
+ taste than it is to reconstruct the design of Helvetica from its look
+ on the page. The exact bitmap or spline outline of a digital font is
+ usually not reconstructable from the printed image, although CRT screen
+ fonts at usual resolutions (60-120 dots per inch) may be reconstructed
+ by patient counting and mapping of bits off a screen display. Typeface
+ licenses often contain stipulations that the digital data will be
+ encrypted and confidential. Just as a firm will protect the secret of
+ a soft drink recipe, so a type firm will protect the exact nature of
+ its digital data.
+
+ Ethics
+ ......
+
+ Some typographers are motivated by higher principles than greed,
+ profit, expediency, and personal interest. Idealists afflicted with
+ concepts of ethical behavior and a vision of typography as a noble art
+ may find it distasteful to use plagiarized types. Some graphic
+ designers insist on using typefaces with bona-fide trademarks, both to
+ ensure that the type will be of high quality, and to encourage
+ creativity and ethics in the profession. A consequence of plagiarism
+ that is sometimes overlooked is a general erosion of ethics in an
+ industry. If it is okay to steal typeface designs, then it may be okay
+ to purloin other kinds of data, to falsify one's resume, to
+ misrepresent a product, and so forth. Most professional design
+ organizations attempt to promote ethical standards of professional
+ behavior, and personal standards may extend to avoidance of plagiarism.
+
+ The Association Typographique Internationale (ATypI) is an international
+ organization of type designers, type manufacturers, and letterform
+ educators. Its purpose is to promote ethical behavior in the industry,
+ advancement of typographic education, communication among designers, and
+ other lofty aims. Members of ATypI agree to abide by a moral code that
+ restricts plagiarism and other forms of depraved behavior (pertaining to
+ typography). These are noble goals, but some members (especially
+ corporate members) of ATypI, confronted with the pressures and
+ opportunities of commercial reality, nevertheless plagiarize typefaces
+ of fellow members, the moral code notwithstanding. Since ATypI is a
+ voluntary organization, there is very little that can be done about
+ most such plagiarism. Some years back, a world-famous type designer
+ resigned %the noted type designer Hermann Zapf from the ATypI Board of
+ Directors in protest over the organization's flaccid attitude toward
+ plagiarists among its ranks. He has since agreed to sit on the board
+ again, but criticism of the organization's inability to prevent type
+ rip-offs by its own members, not to mention by non-members, continues
+ to be heard. Moderates in ATypI believe that a few morals are better
+ than none. It is not clear whether their philosophical stance derives
+ from Plato, Hobbes, or Rousseau.
+
+ Given the general attitude of users toward copyrighted video and
+ software, it is doubtful that ethical considerations will hinder most
+ end-users' attitude to plagiarized type fonts. A desire to have the
+ fashionable "label" or trademark may be a greater motivation toward the
+ use of bona-fide fonts than an ethical consideration.
+
+ Further reading
+ ---------------
+
+ "The State of the Art in Typeface Design Protection", Edward Gottschall,
+ Visible Language, Vol. XIX, No. 1, 1985 (a special issue on "The
+ Computer and the Hand in Type Design"--proceedings of a conference held
+ at Stanford University in August, 1983).
+
+ Der Schutz Typographischer Schriftzeichen, by Guenter Kelbel. Carl
+ Heymans Verlag KG, Cologne, 1984. (A learned account, in juridical
+ German prose, of the significance of the Vienna Treaty of 1973 and the
+ West German Schriftzeichengesetz of 1981.)
+
+ Disclaimer
+ ----------
+
+ These notes were originally prepared at the request of Brian Reid, for
+ informal distribution. They are based on the author's review of
+ available literature on the subject of typeface protection, and on
+ personal experience in registering types for trademark, copyright, and
+ patent. However, they are %While they result from careful research, no
+ claim is made for accuracy; not legal advice. If one is contemplating
+ protecting or plagiarizing a typeface, and seeks legal opinion, it is
+ advisable to consult an attorney. The term "plagiarize" (and words
+ derived from it) is used here in its dictionary sense of "to take and
+ use as one's own the ideas of another" and does not mean that the
+ practice of typeface plagiarism is illegal, as that is determined by
+ the laws of a particular country.
+
+ The author is a professor of digital typography as well as a
+ professional designer of original digital typefaces for electronic
+ printers and computer workstations. He therefore has an obvious bias
+ toward the inculcation of ethical standards and the legal protection of
+ artistic property. Other commentators might have a different
+ perspective.
+
+Subject: 1.14. File Formats
+
+ Many different kinds of files are available on the net. These files
+ contain many different kinds of data for many different architectures.
+ Frequently, the extension (trailing end) of a filename gives a good
+ clue as to the format of its contents and the architecture that it was
+ created on.
+
+ In order to save space, most files on the net are compressed in one way
+ or another. Many compression/decompression programs exist on multiple
+ architectures.
+
+ Multiple files and directories are often combined into a single
+ `archive' file. Many archive formats perform compression automatically.
+
+ File Format Extensions
+ ======================
+
+ * .tar
+
+ Unix `tape archive' format. Tar files can contain multiple files
+ and directories. Unlike most archiving programs, tar files are
+ held together in a wrapper but are not automatically compressed by
+ tar.
+
+ * .Z
+
+ Unix `compress' format. Compression doesn't form a wrapper around
+ multiple files, it simply compresses a single file. As a result,
+ you will frequently see files with the extension .tar.Z. This
+ implies that the files are compressed tar archives.
+
+ * .z .gz
+
+ GNU zip format. GNU zip doesn't form a wrapper around multiple
+ files, it simply compresses a single file. As a result, you will
+ frequently see files with the extension .tar.z or .tar.gz. This
+ implies that the files are compressed tar archives. Do not confuse
+ GNU Zip and PKZip or GNU Zip and Unix compress, those are three
+ different programs!
+
+ * .hqx
+
+ Macintosh `BinHex' format. In order to reliably transfer Mac files
+ from one architecture to another, they are BinHex encoded. This
+ is actually an ascii file containing mostly hexadecimal digits.
+ It is neither a compression program nor an archive format.
+
+ * .sit
+
+ Macintosh `Stuffit' archive.
+
+ * .cpt
+
+ Macintosh `Compactor' archive.
+
+ Like the .tar.Z format that is common among Unix archives,
+ Macintosh archives frequently have the extensions .sit.hqx or
+ .cpt.hqx indicating a BinHex'ed archive.
+
+ * .arc
+
+ PC `arc' archive. This is an older standard (in PC terms, at
+ least) and has gone out of fashion.
+
+ * .zip
+
+ PC `zip' archive. This is the most common PC archive format today.
+
+ * .arj
+
+ PC `arj' archive.
+
+ * .zoo
+
+ PC `zoo' archive
+
+ * .lzh
+
+ PC `lha/lharc' archive.
+
+ * .uue
+
+ `UUencoding' format. In order to reliably transfer binary data
+ across architectures (or through email), they are frequently
+ uuencoded. This is actually an ascii file. It is neither a
+ compression program nor an archive format.
+
+ Font Formats
+ ============
+
+ Just as the are many, many archive formats, there are many different
+ font formats. The characteristics of some of these formats are
+ discussed below. Once again, the file extension may help you to
+ determine the font type. (On the Mac, the resource TYPE field is
+ (probably) a better indicator).
+
+ * PostScript Type 1 Fonts:
+
+ Postscript Type 1 fonts (Also called ATM (Adobe Type Manager)
+ fonts, Type 1, and outline fonts) contains information, in outline
+ form, that allows a postscript printer, or ATM to generate fonts
+ of any size. Most also contain hinting information which allows
+ fonts to be rendered more readable at lower resolutions and small
+ type sizes.
+
+ * PostScript Type 3 Fonts:
+
+ Postscript type 3 fonts are an old outline font format that is not
+ compatible with ATM. Most developers have stopped using this
+ format except in a few special cases, where special type 3
+ characteristics (pattern fills inside outlines, for example) have
+ been used.
+
+ * TrueType Fonts:
+
+ Truetype fonts are a new font format developed by Microsoft with
+ Apple. The rendering engine for this font is built into system 7
+ and an init, the Truetype init, is available for system 6 (freeware
+ from Apple). It is also built into MS Windows v3.1. Like
+ PostScript Type 1 and Type 3 fonts, it is also an outline font
+ format that allows both the screen, and printers, to scale fonts to
+ display them in any size.
+
+ * Bitmap Fonts:
+
+ Bitmap fonts contain bitmaps of fonts in them. This a picture of
+ the font at a specific size that has been optimized to look good
+ at that size. It cannot be scaled bigger without making it look
+ horrendously ugly. On the Macintosh, bitmap fonts also contain
+ the kerning information for a font and must be installed with both
+ type 1 and type 3 fonts. Their presence also speeds the display
+ of commonly used font sizes.
+
+ Font Format Extensions
+ ======================
+
+ * .afm
+
+ Adobe Type 1 metric information in `ascii' format (human parsable)
+
+ * .bco
+
+ Bitstream compressed outline
+
+ * .bdf
+
+ Adobe's Bitmap Distribution Format. This format can be converted
+ to the platform specific binary files required by the local X
+ Windows server. This is a bitmap font format distributed in ASCII.
+
+ * .bez
+
+ Bezier outline information
+
+ * .cfn
+
+ Calamus Font Notation. Vector font format, without hinting, but
+ with greater accuracy when compared to Type 1 fonts. Used by a.o.
+ Calamus (Atari, Windows NT), a DTP program with Soft RIP.
+
+ * .chr
+
+ Borland stroked font file
+
+ * .ff, .f3b, .fb
+
+ Sun formats. More info when I know more...
+
+ * .fli
+
+ Font libraries produced by emTeX fontlib program. Used by emTeX
+ drivers and newer versions of dvips.
+
+ * .fnt
+
+ Bitmapped GEM font in either Motorola or Intel format.
+
+ * .fon
+
+ An MS-Windows bitmapped font.
+
+ * .fot
+
+ An MS-Windows kludge for TrueType fonts. The fot file points to
+ the actual TrueType font (in a ttf file).
+
+ * .gf
+
+ Generic font (the output of TeX's MetaFont program (possibly
+ others?))
+
+ * .mf
+
+ TeX MetaFont font file (text file of MetaFont commands)
+
+ * .pfa
+
+ Adobe Type 1 Postscript font in ASCII format (PC/Unix) I believe
+ that this format is suitable for directly downloading to your
+ PostScript printer (someone correct me if I'm wrong ;-)
+
+ * .pfb
+
+ Adobe Type 1 PostScript font in "binary`' format (PC/Unix) Note:
+ this format is not suitable for downloading directly to your
+ PostScript printer. There are utilities for conversion between
+ PFB and PFA (see the utilities section of the FAQ).
+
+ * .pfm
+
+ Printer font metric information in Windows format
+
+ * .pk
+
+ TeX packed bitmap font file (also seen as .###pk where ### is a
+ number)
+
+ * .pl
+
+ TeX `property list' file (a human readable version of .tfm)
+
+ * .ps
+
+ Frequently, any PostScript file. With respect to fonts, probably
+ a Type3 font. This designation is much less `standard' than the
+ others. Other non-standard extensions are .pso, .fon, and .psf
+ (they are a mixture of type 1 and type 3 fonts).
+
+ * .pxl
+
+ TeX pixel bitmap font file (obsolete, replaced by .pk)
+
+ * .sfl
+
+ LaserJet bitmapped softfont, landscape orientation
+
+ * .sfp
+
+ LaserJet bitmapped softfont, portrait orientation
+
+ * .sfs
+
+ LaserJet scalable softfont
+
+ * .spd
+
+ Vector font in Speedo format.
+
+ * .tdf
+
+ Vector font type definitions for Speedo fonts.
+
+ * .tfm
+
+ TeX font metric file. Also an HP Tagged Font Metric file.
+
+ * .ttf
+
+ An MS-Windows TrueType font.
+
+ * .vf
+
+ TeX virtual font which allows building of composite fonts (a
+ character can be composed of any sequence of movements, characters
+ (possibly from multiple fonts) rules and TeX specials)
+
+ * .vpl
+
+ TeX `property list' (human readable) format of a .vf
+
+Subject: 1.15. Ligatures
+
+ A ligature occurs where two or more letterforms are written or printed
+ as a unit. Generally, ligatures replace characters that occur next to
+ each other when they share common components. Ligatures are a subset
+ of a more general class of figures called "contextual forms."
+ Contextual forms describe the case where the particular shape of a
+ letter depends on its context (surrounding letters, whether or not it's
+ at the end of a line, etc.).
+
+ One of the most common ligatures is "fi". Since the dot above a
+ lowercase 'I' interferes with the loop on the lowercase 'F', when 'f'
+ and 'i' are printed next to each other, they are combined into a single
+ figure with the dot absorbed into the 'f'.
+
+ An example of a more general contextual form is the greek lowercase
+ sigma. When typesetting greek, the selection of which 'sigma' to use
+ is determined by whether or not the letter occurs at the end of the
+ word (i.e., the final position in the word).
+
+ * Amanda Walker provides the following discussion of ligatures:
+
+ Ligatures were originally used by medieval scribes to conserve
+ space and increase writing speed. A 14th century manuscript, for
+ example, will include hundreds of ligatures (this is also where
+ "accents" came from). Early typefaces used ligatures in order to
+ emulate the appearance of hand-lettered manuscripts. As
+ typesetting became more automated, most of these ligatures fell
+ out of common use. It is only recently that computer based
+ typesetting has encouraged people to start using them again
+ (although 'fine art' printers have used them all along).
+ Generally, ligatures work best in typefaces which are derived from
+ calligraphic letterforms. Also useful are contextual forms, such
+ as swash capitals, terminal characters, and so on.
+
+ A good example of a computer typeface with a rich set of ligatures
+ is Adobe Caslon (including Adobe Caslon Expert). It includes:
+
+ Upper case, lower case, small caps, lining numerals, oldstyle
+ numerals, vulgar fractions, superior and inferior numerals, swash
+ italic caps, ornaments, long s, and the following ligatures:
+
+ ff fi fl ffi ffl Rp ct st Sh Si Sl SS St (where S=long s)
+
+ [Ed: Another common example is the Computer Modern Roman typeface
+ that is provided with TeX. this family of fonts include the ff,
+ fi, fl, ffi, and ffl ligatures which TeX automatically uses when
+ it finds these letters juxtaposed in the text.]
+
+ While there are a large number number of possible ligatures,
+ generally only the most common ones are actually provided. In
+ part, this is because the presence of too many alternate forms
+ starts reducing legibility. A case in point is Luxeuil Miniscule,
+ a highly-ligatured medieval document hand which is completely
+ illegible to the untrained eye (and none too legible to the
+ trained eye, either :)).
+
+ * Don Hosek offers the following insight into ligatures:
+
+ Ligatures were used in lead type, originally in imitation of
+ calligraphic actions (particularly in Greek which retained an
+ excessive number of ligatures in printed material as late as the
+ 19th century), but as typefaces developed, ligatures were retained
+ to improve the appearance of certain letter combinations. In some
+ cases, it was used to allow certain letter combinations to be more
+ closely spaced (e.g., "To" or "Vo") and were referred to as
+ "logotypes". In other cases, the designs of two letters were merged
+ to keep the overall spacing of words uniform. Ligatures are
+ provided in most contemporary fonts for exactly this reason.
+
+ * Liam Quin makes the following observations:
+
+ The term ligature should only be used to describe joined letters in
+ printing, not letters that overlap in manuscripts.
+
+ Many (not all) accents came from the practice of using a tilde or
+ other mark to represent an omitted letter, so that for example the
+ Latin word `Dominus' would be written dns, with a tilde or bar over
+ the n. This is an abbreviation, not a ligature.
+
+ Most ligatures vanished during the 15th and 16th Centuries. It was
+ simply too much work to use them, and it increased the price of
+ book production too much.
+
+ [Ed: there is no "complete" set of ligatures.]
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 1.16. Built-in Fonts
+
+ * PostScript printers (and Adobe Type Manager) with 13 fonts have:
+
+ Courier, Courier-Bold, Courier-BoldOblique, Courier-Oblique,
+ Helvetica, Helvetica-Bold, Helvetica-BoldOblique,
+ Helvetica-Oblique, Symbol, Times-Bold, Times-BoldItalic,
+ Times-Italic, Times-Roman
+
+ * Postscript printers with 17 fonts have:
+
+ Courier, Courier-Bold, Courier-BoldOblique, Courier-Oblique,
+ Helvetica, Helvetica-Bold, Helvetica-BoldOblique, Helvetica-Narrow,
+ Helvetica-Narrow-Bold, Helvetica-Narrow-BoldOblique,
+ Helvetica-Narrow-Oblique, Helvetica-Oblique, Symbol, Times-Bold,
+ Times-BoldItalic, Times-Italic, Times-Roman
+
+ * Postscript printers with 35 fonts have:
+
+ All of the above, plus the following:
+
+ ZapfChancery-MediumItalic, ZapfDingbats, AvantGarde-Book,
+ AvantGarde-BookOblique, AvantGarde-Demi, AvantGarde-DemiOblique,
+ Bookman-Demi, Bookman-DemiItalic, Bookman-Light,
+ Bookman-LightItalic, NewCenturySchlbk-Bold,
+ NewCenturySchlbk-BoldItalic, NewCenturySchlbk-Italic,
+ NewCenturySchlbk-Roman, Palatino-Bold, Palatino-BoldItalic,
+ Palatino-Italic, Palatino-Roman
+
+ * HP LaserJet printers (II, IIP)
+
+ Courier 10, Courier 12, LinePrinter 16.66, ...
+
+ * HP LaserJet printers (III, IIIP)
+
+ All of the above, plus the following:
+
+ Scalable Times Roman and Scalable Univers using Compugraphic's
+ Intellifont hinted font format.
+
+ * HP LaserJet IV printers
+
+ All of the above, plus the following scalable (Intellifont) faces:
+
+ Courier, Courier Bold, Courier Italic, Courier Bold Italic, CG
+ Times, CG Times Bold, CG Times Italic, CG Times Bold Italic CG
+ Omega, CG Omega Bold, CG Omega Italic, CG Omega Bold Italic
+ Coronet, Clarendon Condensed Univers Medium, Univers Bold, Univers
+ Medium Italic, Univers Bold Italic Univers Medium Condensed,
+ Univers Bold Condensed, Univers Medium Condensed Italic, Univers
+ Bold Condensed Italic Antique Olive, Antique Olive Bold, Antique
+ Olive Italic Garamond Antiqua, Garamond Halbfett, Garamond Kursiv,
+ Garamond Kursiv Halbfett Marigold, Albertus Medium, Albertus Extra
+ Bold Arial, Arial Bold, Arial Italic, Arial Bold Italic Times New,
+ Times New Bold, Times New Italic, Times New Bold Italic Symbol,
+ Wingdings, Letter Gothic, Letter Gothic Bold, Letter Gothic Italic
+
+ * SPARCPrinters
+
+ The basic 35 fonts plus four scaled faces of each of Bembo, Gill
+ Sans, Rockwell, Lucida, Lucida Bright, Sans and Typewriter, giving
+ a total of 57 fonts, all in the F3 format.
+
+Subject: 1.17. Glossary
+
+ [ I ripped this right out of the manual I wrote for Sfware. If you have
+ comments, improvements, suggestions, please tell me... ]
+
+ anti-aliasing
+ [ed: this is an 'off-the-cuff' definition, feel free to clarify it
+ for me ;-) ]
+
+ On low-resolution bitmap devices (where ragged, ugly characters
+ are the norm) which support more than two colors, it is possible
+ to provide the appearance of higher resolution with anti-aliasing.
+ Anti-aliasing uses shaded pixels around the edges of the bitmap
+ to give the appearance of partial-pixels which improves the
+ apparent resolution.
+
+ baseline
+ The baseline is an imaginary line upon which each character rests.
+ Characters that appear next to each other are (usually) lined up so
+ that their baselines are on the same level. Some characters extend
+ below the baseline ("g" and "j", for example) but most rest on it.
+
+ bitmap
+ A bitmap is an array of dots. If you imagine a sheet of graph paper
+ with some squares colored in, a bitmap is a compact way of
+ representing to the computer which squares are colored and which
+ are not.
+
+ In a bitmapped font, every character is represented as a pattern of
+ dots in a bitmap. The dots are so small (300 or more dots-per-inch,
+ usually) that they are indistinguishable on the printed page.
+
+ character
+ (1) The smallest component of written language that has semantic
+ value. Character refers to the abstract idea, rather than a
+ specific shape (see also glyph), though in code tables some form
+ of visual representation is essential for the reader's
+ understanding. (2) The basic unit of encoding for the Unicode
+ character encoding, 16 bits of information. (3) Synonym for "code
+ element". (4) The English name for the ideographic written
+ elements of Chinese origin.
+
+ download
+ Downloading is the process of transferring information from one
+ device to another. This transferral is called downloading when the
+ transfer flows from a device of (relatively) more power to one of
+ (relatively) less power. Sending new fonts to your printer so that
+ it "learns" how to print characters in that font is called
+ downloading.
+
+ font
+ A particular collection of characters of a typeface with unique
+ parameters in the 'Variation vector', a particular instance of
+ values for orientation, size, posture, weight, etc., values. The
+ word font or fount is derived from the word foundry, where,
+ originally, type was cast. It has come to mean the vehicle which
+ holds the typeface character collection. A font can be metal,
+ photographic film, or electronic media (cartridge, tape, disk).
+
+ glyph
+ (1) The actual shape (bit pattern, outline) of a character image.
+ For example, an italic 'a' and a roman 'a' are two different glyphs
+ representing the same underlying character. In this strict sense,
+ any two images which differ in shape constitute different glyphs.
+ In this usage, "glyph" is a synonym for "character image", or
+ simply "image". (2) A kind of idealized surface form derived from
+ some combination of underlying characters in some specific
+ context, rather than an actual character image. In this broad
+ usage, two images would constitute the same glyph whenever they
+ have essentially the same topology (as in oblique 'a' and roman
+ 'a'), but different glyphs when one is written with a hooked top
+ and the other without (the way one prints an 'a' by hand). In
+ this usage, "glyph" is a synonym for "glyph type," where glyph is
+ defined as in sense 1.
+
+ hints
+ When a character is described in outline format the outline has
+ unlimited resolution. If you make it ten times as big, it is just
+ as accurate as if it were ten times as small.
+
+ However, to be of use, we must transfer the character outline to a
+ sheet of paper through a device called a raster image processor
+ (RIP). The RIP builds the image of the character out of lots of
+ little squares called picture elements (pixels).
+
+ The problem is, a pixel has physical size and can be printed only
+ as either black or white. Look at a sheet of graph paper. Rows and
+ columns of little squares (think: pixels). Draw a large `O' in the
+ middle of the graph paper. Darken in all the squares touched by the
+ O. Do the darkened squares form a letter that looks like the O you
+ drew? This is the problem with low resolution (300 dpi). Which
+ pixels do you turn on and which do you leave off to most accurately
+ reproduce the character?
+
+ All methods of hinting strive to fit (map) the outline of a
+ character onto the pixel grid and produce the most
+ pleasing/recognizable character no matter how coarse the grid is.
+
+ kerning
+ (noun): That portion of a letter which extends beyond its width,
+ that is, the letter shapes that overhang - the projection of a
+ character beyond its sidebearings.
+
+ (verb): To adjust the intercharacter spacing in character groups
+ (words) to improve their appearance. Some letter combinations
+ ("AV" and "To", for example) appear farther apart than others
+ because of the shapes of the individual letters.
+
+ Many sophisticated word processors move these letter combinations
+ closer together automatically.
+
+ outline font/format
+ See 'scalable font'
+
+ point
+ The (more or less) original point system (Didot) did have exactly
+ 72 points to the inch. The catch is that it was the French
+ imperial inch, somewhat longer than the English inch, and it went
+ away in the French revolution. What most people now think of as
+ points were established by the United States Typefounders
+ Association in 1886. This measure was a matter of convenience for
+ the members of the Association, who didn't want to retool any more
+ than they had to, so it had no relationship to the inch. By that
+ date, people realized that the inch was an archaic measure anyway;
+ the point was set to be 1/12 of a pica, and an 83-pica distance
+ was made equal to 35 centimeters. (Talk about arbitrary!)
+
+ Thus the measure of 72.27/in. is just an approximation. Of course,
+ when PostScript was being written, it was necessary to fit into an
+ inch-measured world. For the sake of simplicity PostScript defined
+ a point as exactly 1/72". With the prevalance of DTP, the
+ simplified point has replaced the older American point in many
+ uses. Personally, I don't see that it matters one way or the
+ other; all that counts is that there's a commonly-understood unit
+ of measurement that allows you to get the size you think you want.
+ That is, after all, the point ;)
+
+ scalable font
+ A scalable font, unlike a bitmapped font, is defined mathematically
+ and can be rendered at any requested size (within reason).
+
+ softfont
+ A softfont is a bitmapped or scalable description of a typeface or
+ font. They can be downloaded to your printer and used just like
+ any other printer font. Unlike built-in and cartridge fonts,
+ softfonts use memory inside your printer. Downloading a lot of
+ softfonts may reduce the printers ability to construct complex
+ pages.
+
+ symbol set
+ The symbol set of a font describes the relative positions of
+ individual characters within the font. Since there can only be 256
+ characters in most fonts, and there are well over 256 different
+ characters used in professional document preparation, there needs
+ to be some way to map characters into positions within the font.
+ The symbol set serves this purpose. It identifies the "map" used
+ to position characters within the font.
+
+ typeface
+ The features by which a character's design is recognized, hence
+ the word face. Within the Latin language group of graphic shapes
+ are the following forms: Uncial, Blackletter, Serif, Sans Serif,
+ Scripts, and Decorative. Each form characterizes one or more
+ designs. Example: Serif form contains four designs called Old
+ Style, Transitional, Modern, and Slab Serif designs. The typeface
+ called Bodoni is a Modern design, while Times Roman is a
+ Transitional design.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(3_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(3_6)
new file mode 100644
index 0000000000..e10e39ce48
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(3_6)
@@ -0,0 +1,1050 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (3/6)
+Supersedes: <font-faq-3_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:20 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 1027
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-3_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48300 comp.answers:20514 news.answers:79235
+
+Archive-name: fonts-faq/part3
+Version: 2.1.5
+
+Subject: 1.18. Bibliography
+
+ Editors note: the following books have been suggested by readers of
+ comp.fonts. They are listed in no particular order. I have lost the
+ citations for some of the submissions. If you wrote a review that
+ appears below and you aren't credited, please let norm know.
+
+ I have decided that this is the best section for pointers to other font
+ resources (specs and other documents, for example). These appear after
+ the traditional bibliographic entries. As usual I will happily accept
+ entries for this section. As of 9/92, the only files listed are the
+ TrueType font information files available from Microsoft.
+
+ Bill Ricker contributed the following general notes:
+
+ The Watson-Guptill, Godine, and Dover publishers all have many
+ typography titles. Godine and Dover tend to be excellent; W-G tends
+ toward 'how-to' books which are good for basics and juried Annuals of
+ job work.
+
+ Hermann Zapf and his Design Philosophy, Society of Typographic Arts,
+ Chicago, 1987.
+
+ On Stone -- The Art and Use of Typography on the Personal Computer,
+ Sumner Stone, Bedford Arts, 1991.
+
+ Of the Just Shaping of Letters, Albrecht Durer, isbn 0-486-21306-4.
+
+ First published in 1525 as part of his theoretical treatise on applied
+ geometry, "The Art of Measurment".
+
+ Champ Flevry, Geofroy Troy.
+
+ First published in 1529 Troy attempts, in this book, to design an ideal
+ Roman alphabet upon geometrical and aesthetic principles.
+
+ The Alphabet & Elements of Lettering, Frederic W. Goudy, isbn
+ 0-486-20792-7. Revised 1942 edition.
+
+ This very interesting book looks at the history of letter shapes as
+ well font design.
+
+ The Mac is Not a Typewriter, Robin Williams, Peachpit Press.
+
+ A good, clear explanation of what typography is, and how to get it from
+ your computer. Mac-specific, but full of excellent general advice. I
+ think there's also a PC version. Available at most computer bookstores
+
+ Rhyme and Reason: A Typographic Novel, Erik Spiekermann, H. Berthold AG,
+ ISBN 3-9800722-5-8.
+
+ Printing Types (2 vols), Daniel Berkely Updike, Dover Press.
+
+ Affordable edition of the most readable history of type, lots of
+ illustrations.
+
+ Notes: Both the Dover and Harvard U. P. editions were 2 volumes. The
+ Dover editions were paperback and the Harvard hardback. It appears
+ that the Dover edition is out of print. Collectible HUP editions are
+ not cheap although later HUP editions may be had. Most libraries have
+ later HUP and Dover editions. If someone knows of a source, please
+ pass it along.
+
+ The Art of Hand Lettering, Helm Wotzkow, Dover Press, reprint from 1952.
+
+ Looking Good In Print, Roger C. Parker, Ventana Press, ISBN:
+ 0-940087-32-4.
+
+ Well, as a beginner's book, [it] isn't bad. I can't say that I agree
+ with the author's tastes all the time, but he at least gives some good
+ examples. Also there are some nice _Publish_-style makeovers. Don
+ Hosek <dhosek@ymir.claremont.edu>
+
+ Book Design: A Practical Introduction, Douglas Martin, Van Nostrand
+ Reinhold, New York: 1989. 206pp.
+
+ Along with Jan White's book (see below), this provides a fairly
+ complete guide to book design. Martin's book is somewhat more
+ conservative in outlook and also reflects his UK background. Don Hosek
+ <dhosek@ymir.claremont.edu>
+
+ Digital Typography: An Introduction to Type and Composition for Computer
+ System Design, Richard Rubinstein, Addison-Wesley, Reading,
+ Massachusetts: 1988. 340pp.
+
+ An interesting, technological approach to typography which is worth
+ reading although not necessarily always worth believing. A not
+ insubstantial portion of the text is dedicated to representing type on
+ a CRT display and Rubinstein devotes some time to expressing
+ characteristics of typography numerically. Don Hosek
+ <dhosek@ymir.claremont.edu>
+
+ Graphic Design for the Electronic Age, Jan V. White, Watson-Guptill
+ Publications, New York: 1988. 212pp.
+
+ A good handbook for document design. In a well-organized approach,
+ White covers the principles for laying out most of the typographics
+ features of a technical document. White is a bit overeager to embrace
+ sans-serif types and in places his layout ideas seem a bit garish, but
+ it's still a quite worthwhile book. Don Hosek
+ <dhosek@ymir.claremont.edu>
+
+ Xerox Publishing Standards: A Manual of Style and Design, Watson-Guptill
+ Publications, New York: 1988. 400pp.
+
+ Overall, a disappointing book. It is divided into four sections of
+ widely varying intent: "Publishing Process," "Document Organization,"
+ "Writing and Style" and "Visual Design." None of them is really
+ adequate for the task and all are highly centered on the Xerox method
+ for publishing. As a guide to Xerox' process, it succeeds, but as a
+ manual for general use, it falls far short. In print. Don Hosek
+ <dhosek@ymir.claremont.edu>
+
+ Methods of Book Design (3rd edition), Hugh Williamson, Yale University
+ Press, New Haven: 1983. 408pp.
+
+ It is a bit out-of-date as regards technology, but on issues relating
+ purely to design it is comprehensive and definitive. Well, I suppose
+ it could be argued that printing technology influences design - e.g.
+ some types look fine in metal but lousy in digital imagesetting - and
+ therefore a book that is out-of-date in technology can't really be
+ "definitive" in matters of design either. In any event, _Methods_ is
+ more than adequate for a beginner's needs. My paper-bound copy (ISBN
+ 0-300-03035-5) was \$13.95; cheap at twice the price! Cameron Smith
+ <cameron@symcom.math.uiuc.edu>
+
+ The Thames & Hudson Manual of typography, Rauri McLean, Thames & Hudson
+
+ An excellent book if you start getting more interested in type. Look
+ for Rauri McLean's other books after this one... Liam R.E. Quin
+ <lee@sq.com>
+
+ Typography and Why it matters, Fernand Baudin.
+
+ There is no better introduction than [it]. It's not a primer on
+ subjects such as "what does Avant Garde look like," or "This is a good
+ font for books." It is a good primer on the things you need to know
+ before the rest should be considered. He's a lovely writer, to boot.
+
+ [My copy is at work, so I may have munged the title-look up Baudin in
+ "Books in Print" and improvise :-)]
+
+ Ari Davidow <ari@netcom.com>
+
+ Better Type, Betty Binns
+
+ It's definitely not a lightweight beginner's introduction, but I've
+ found [it] to be indispensable. It's a large-format hardcover, but you
+ can find it remaindered for cheap if you look around. The book goes
+ into great detail about how factors like line spacing, line length,
+ point size, and design of typeface (evenness of stroke weight,
+ x-height, etc.) affect readability. When you've gotten the basics out
+ of the way and want to learn more about the fine nuances of type color,
+ this book is an absolute must. David Mandl <dmandl@bilbo.shearson.com>
+
+ Printing Types: An Introduction..., S. Lawson, (revised) 1990
+
+ I'd also recommend Alexander S. Lawson's books especially /Printing
+ Types: An Intro.../ (revised), 1990, which includes electronic types
+ now. Bill Ricker <wdr@world.std.com>
+
+ Tally of Types, Stanley Morrison, Cambridge University Press.
+
+ A keepsake for CUP on the Monotype fonts he'd acquired for them when he
+ was Type Advisor to both Brit.Monotype & CUP (Cambridge University
+ Press, Cambs.UK), which discusses his hindsight on some of the great
+ revival fonts and some of the better new fonts. Bill Ricker
+ <wdr@world.std.com>
+
+ Chicago Manual of Style, University of Chicago Press, 1982;
+ ISBN 0-226-10390-0.
+
+ The chapter on Design and Typography is most directly relevant, but
+ there are a lot of hints scattered all through the Chicago Manual on
+ making your words more readable and your pages more attractive. Stan
+ Brown <brown@ncoast.org>
+
+ X Window System Administrator's Guide (O'Reilly X Window System Guides,
+ volume 8), O'Reilly
+
+ It gives advice about setting up fonts, etc. Liam Quin <lee@sq.com>
+
+ How Bodoni intended his types to look Bodoni, Giambattista. Fregi e
+ Majuscole Incise e Fuse de ... Bodoni, Harvard University Library
+ (repr).
+
+ Inexpensive collectible, reproduced as a keepsake by the Houghton
+ Library at Harvard. [wdr]
+
+ The Elements of Typographic Style, Robert Bringhurst, Hartley & Marks
+ 0-88179-033-8 pbk \$15, Z246.B74 1992 0-88179-110-5 cloth, \$25.
+
+ A typography for desktop publishers who want to absorb some style.
+ Informed by the historical european tradition and the desktop
+ advertising, tempered by oriental yin-yang and examples. A page-turner
+ with repeat-read depth.
+
+ The only book I've seen that discusses page proportions that admits
+ there are more than three ways that describes how to find one that
+ feels good for your page. [wdr]
+
+ Hermann Zapf on the cover-blurb: "All desktop typographers should study
+ this book. ... I wish to see this book become the Typographers' Bible."
+
+ Printing It, Clifford Burke, Ballantine, 0-345-02694-2.
+
+ Manual for the hobby letterpress printer. [wdr]
+
+ Twentieth Century Type Designers, Sebastian Carter, Taplinger, 1987.
+
+ Discusses the talented adaptators of old faces to machine caster and
+ film/laser, as well as the designers of new works. Indexed? [wdr]
+
+ Design with Type, Carl Dair, University of Toronto Press, 0-8020-1426-7.
+
+ In print again (or still?); the ISBN above may be stale.
+
+ A great introduction to the issues of practicality and taste that
+ confront the users of type. A prized possession. I only regret that the
+ book does not include among the excerpts from his Westvaco pamphlets
+ the Seven Don'ts of Typography. [wdr]
+
+ Typography 6: The Annual of the Type Directors Club, Susan Davis, ed.,
+ Watson-Guptill, 0-8230-5540-x.
+
+ Specimens of Type Faces in the U.S. G.P.O., John J. Deviny, director.,
+ US G.P.O.
+
+ Practice of Typography: Plain Printing Types, Theodore Low De Vinne,
+ Century Co./DeVinne Press.
+
+ One of the earlier critical studies, in four volumes of which this is
+ my personal favorite, and still a classic reference. If one wants to
+ understand 18th and 19th century typography in context, this writer
+ lived the transition from eclectic to standard sizes, and comments
+ with taste. [wdr]
+
+ An Essay on Typography, Eric Gill, Godine, 0-87923-762-7.
+
+ The Alphabet and Elements of Lettering, Frederic W. Goudy, Dorset Press
+ (Marboro Books), 0-88029-330-6
+
+ Lovely. A wonderful way to learn Goudy's taste.
+
+ Stanley Morison Displayed, Herbert Jones, Frederick Muller Ltd / W,
+ 0-584-10352-2.
+
+ Lovely. A wonderful way to learn Morrison's taste.
+
+ Printing Types: An Introduction..., Alexander S. Lawson et. al., Beacon
+ 1971,?Godine? 1990; (2nd Ed includes electronic types now)
+
+ "Good introduction to comparisons of typefaces, with a detailed history
+ and a key family or face of each general category. Denounces rigid
+ indexes of type faces." [wdr]
+
+ Anatomy of a Typeface, Alexander Lawson, Godine, 0-87923-333-8,
+ Z250.L34 1990
+
+ Deep description of the authors' favorite exemplar and its influences
+ and relatives in each type category. It follows, without explicating,
+ the category system developed in the prior book. [wdr]
+
+ Types of Typefacs and how to recognize them, J. Ben Lieberman,
+ Sterling, 1968
+
+ "This isn't very good really, but it does give lots of examples of the
+ main categories." [Liam] [Old bibliographies praised this one, but I
+ haven't seen it so I can't comment.- wdr]
+
+ Tally of Types (& other titles), Stanley Morrison, Cambridge U. Press.
+
+ A keepsake for CUP on the Monotype fonts he'd acquired for them when he
+ was Type Advisor to both Brit. Monotype & CUP (Cambridge University
+ Press, Cambs.UK), which discusses his hindsight on some of the great
+ revival fonts and some of the better new fonts. [wdr]
+
+ Rookledge's International Type Finder 2nd, Perfect, Christopher and
+ Gordon Rookledge, Ed Moyer Bell Ltd / Rizzoli, 1-55921-052-4,
+ Z250.P42 [1st Ed was NY: Beil 1983]
+
+ "Lg. trade pb. Indexed by stylistic & characteristic features. Shows
+ A-Z, a-z, 0-9 in primary figures, whether lining or ranging.
+ Particularly distinctive sorts are marked for ease of comparison.
+ Separate tables collect the distinctive characters for assistance in
+ identifying a sample." [wdr]
+
+ English Printers' Ornaments, Henry R. Plomer, Burt Franklin
+
+ Paragraphs on Printing, Bruce Rogers, [Rudge] Dover, 0-486-23817-2
+
+ Digital Typography: An Introduction to Type and Composition for
+ Computer System Design, Richard Rubinstein, Addison-Wesley, Reading,
+ Massachusetts: 1988. 340pp.
+
+ For people who are disappointed with how the type looks on the laser,
+ this book explains the subleties of that medium and of the screen that
+ others miss. This is a study of the Human Factors of computer
+ typographic systems. [wdr]
+
+ The Case for Legibility, John Ryder, The Bodley Head, 0-370-30158-7,
+ Z250.A4
+
+ The Solotype Catalog of 4,147 Display typefaces, Dan X. Solo, Dover,
+ 0-486-27169-2, Z250.5.D57S654 19
+
+ "Working catalog of a specialty Graphics Arts shop. They use
+ proprietary optical special effects techniques to get Desktop
+ Publishing effects, and more, without the laser-printer grain. Great
+ listing of 19th Century Decorated Types - probably the largest
+ collection in the world. Prices to order headlines from them are NOT
+ cheap however. Their services are for professional or serious hobby
+ use only. Solo's previous Dover books show some number of complete
+ alphabets of a general peculiar style; this one shows small fragments
+ of his entire usable collection, important as an index. (According to
+ private correspondence, they have more faces that have not yet been
+ restored to usable condition.) Not well indexed, but indexed." [wdr]
+
+ Stop Stealing Sheep & find out how type works, Erik Spiekermann & E.M.
+ Ginger., Adobe Press, 1993
+
+ Introductory, motivational. If you wonder why there are so many type
+ faces in the world, this is the book for you! [Liam] [The title refers
+ to the old joke: "A man who would letterspace lowercase would also
+ steal sheep." [wdr]]
+
+ The Art & Craft of Handmade Paper, Vance Studley, Dover, 0-486-26421-1,
+ TS1109.S83 1990
+
+ Letters of Credit, Walter Tracey, Godine Press
+
+ "I can't recommend this too highly. It's not as introductory as the
+ Sheep Book, but conveys a feeling of love and respect for the letter
+ forms, and covers a lot of ground very, very well." [Liam]
+
+ Printing Types: Their History, Forms & Use, Daniel Berkely Updike,
+ Harvard University Press, reprint by Dover.
+
+ The standard reference. Tour-de-force history of type and type-styles.
+ A trifle conservative in its biases, but typography is conservative for
+ good reason: readability. Check the addenda for his final words on
+ newer faces. [wdr]
+
+ 1. I believe the Dover edition to be 3 vols Pbk; both the collectable
+ and later Harvard U.P. editions were two vols hbk.
+
+ 2. I am informed by my bookseller & Books In Print that the Dover
+ edition is out of print. *sigh* If a source be known, let me know.
+ Collectible HUP eds are not cheap, although later HUP eds may be had.
+ Most libararies have later HUP or Dover eds. [wdr]
+
+ Modern Encyclopedia of Typefaces, 1960-90, Lawrence W. Wallis, Van
+ Nostrand Reinhold, 0-442-30809-4, Z250.W238 1990
+
+ "Gives examples of most typefaces, almost all digital, designed &
+ distributed in the last 30 years. Cross indexed by foundry and
+ designer, and sources and looks-likes. Some historical bits. Shows
+ full a-z,A-Z,0-9, a few points (punctuation); and 0-9 again if both
+ lining and oldstyle supplied. Only complaint is that it omits small
+ caps even from what few fonts have 'em and the accented characters, of
+ which most have some but too few. List \$25." [wdr]
+
+ About Alphabets: Some Marginal Notes on Type Design, Hermann Zapf, MIT
+ Press, 0-262-74003-6
+
+ Hermann Zapf & His Design Philosophy, Hermann Zapf, Society of
+ Typographic Arts, Chicago
+
+ "Anything about, by, or vaguely connected with Hermann Zapf is probably
+ worth reading several times :-)" [Liam]
+
+ Manuale Typographicum, Hermann Zapf, MIT Press, 0-262-74004-4
+
+ There are two books of this title (portrait and landscape); this is
+ the only mass-market edition of either. Both are Zapf's selections of
+ interesting typographical quotations in his inimitable display
+ typography. [wdr]
+
+ Microsoft Windows 3.1 Programmer's Reference, Microsoft Press.
+
+ Documents the Panose system of typeface classification. Probably
+ contains a general discussion of TrueType under MS Windows 3.1.
+
+ Introduction to Typography, 3rd ed, Faber, London, 1962.
+
+ A very good introduction for any beginner. Also discusses things like
+ illustrations and cover design, although not in great detail.
+
+ Simon was a purist, as the editor of the 3rd edition remarks. He did
+ not mention phototypesetting in his original edition, but some
+ observations on its uses and abuses have since been added. Anders
+ Thulin <ath@linkoping.trab.se>
+
+ Eve Damaziere contributes:
+
+ Twentieth Century Type, Lewis Blackwell, Calmann & King, London (GB),
+ 1992. Chez Flammarion (1993 - 256 p.) pour l'edition francaise (french
+ edition).
+
+ It's a very intelligent account of the history of type in our century,
+ and its links to art, technics and politics (history). Lots of
+ pictures, too. At the end of it, a "description and classification of
+ types", from the 15th century up to now : the author follows the
+ classification of Maximilien Vox (1952), a french graphist.
+
+ [ed: additional bibliographic information appears in the file
+ "Additional-bibliography" on
+ http://www.ora.com/homepages/comp.fonts/FAQ.html. I have not yet had
+ time to integrate this bibliographic information into the FAQ]
+
+Subject: 1.19. Font Encoding Standards
+
+ What is a character set?
+ ========================
+
+ A character set is a collection of symbols in a specific order. Some
+ common character sets are ASCII and ISO Latin 1.
+
+ What is an encoding vector?
+ ===========================
+
+ The term "encoding vector" is most frequently heard in the context of
+ PostScript fonts. An encoding vector embodies a particular character
+ set, it is simply the list of all the characters in the character set
+ in the order in which they occur.
+
+ Most font technologies limit a particular encoding to 256 characters;
+ an Adobe Type 1 font, for example, may contain an arbitrary number of
+ characters, but no single encoding vector can contain more than 256.
+
+ Some common encodings are:
+
+ * Adobe Standard Encoding - the default encoding of many PS Type1
+ fonts
+
+ * Apple Standard Encoding - the default encoding on a Mac
+
+ * US ASCII - seven bit ASCII
+
+ * ISO Latin-1 - an eight bit multi-national character
+ set encoding
+
+ * Cork Encoding - the TeX community's eight bit standard
+
+ * FC - an eight bit encoding for African
+ languages
+
+ * TeX text - the TeX community's seven bit defacto
+ standard (CMR)
+
+ Where can I get them?
+ =====================
+
+ You can get tables showing the layout of many standard character sets
+ from the Kermit distribution (via anonymous ftp from
+ watsun.cc.columbia.edu in /kermit/charsets.
+
+Subject: 1.20. PostScript
+
+ What About PostScript UNIQUEIDs?
+ ================================
+
+ This section was constructed from a posting by Johannes Schmidt-Fischer
+ in Jun 1993.
+
+ All PostScript Type 1 fonts should contain a UniqueId. This is a
+ number which should be, as the name suggests, unique (at least among
+ the fonts that you download to the printer at any given time).
+
+ There are many PostScript fonts on the 'Net which have identical
+ UniqeIds. If two of these fonts are downloaded to the same printer at
+ the same time, attempts to use either font may cause the wrong
+ characters to be printed.
+
+ In a nutshell, the reason that the wrong characters may be printed is
+ that the printer may be storing the rendered glyphs in its font cache,
+ addressed by UniqueID. So, if two fonts, /Foo and /Bar, both have
+ UniqueID=5 and /Foo's 10pt "A" is currently in the cache, a request for
+ /Bar's 10pt "A" will cause the wrong character to be printed. Rather
+ than rendering /Bar's "A" from its (correct and unambiguous) outline,
+ the printer will note that the cache contains a 10pt "A" for font 5 and
+ will copy it from the cache (resulting in /Foo's "A" printing for /Bar).
+
+ Adobe's "Red Book" contains a detailed discussion of this topic.
+
+ Can a Type 1 Font Be Shaded?
+ ============================
+
+ David Lemon contributes:
+
+ There are three ways to get grey into a font. The first is to make a
+ series of Type 1 fonts, each of which will be used for a single shade
+ of grey (or other color). The user then sets copies of the characters
+ on top of each other, selecting each and setting it to the shade
+ desired. It's a bit inconvenient (and won't work in a word processor)
+ but it gets full resolution, good hinting and gives the user lots of
+ control. This is the approach Adobe has used in its "chromatic" fonts
+ (as in Adobe Wood Type 3 and Copal) and is viable for both Type 1 and
+ TrueType formats.
+
+ As an alternative, the designer can approximate shades of grey in the
+ characters by using many little dots (a sort of halftone effect) or
+ lines (as in cross-hatching). This leads to pretty complex characters,
+ which may choke some rasterizers, and won't hint well. As with the
+ first method, this is viable (more or less) for both Type 1 and
+ TrueType.
+
+ The third method is more direct but limited. In this approach, the
+ designer/producer creates the shades of grey in a font-editing program.
+ The limitation is that such a font must be written in Type 3, which is
+ a generalized PostScript format (Type 1 and TrueType recognize only
+ solid shapes). Such a font won't be supported by ATM, so your screen
+ display will suffer and you'll be restricted to PostScript printers. On
+ the plus side, your greys will be rendered at the full resolution of
+ the printer you use.
+
+Subject: 1.21. TrueType
+
+ George Moore announces the following information regarding TrueType
+ fonts:
+
+ "I am pleased to announce that there is now one central location for all
+ official Microsoft TrueType information available on the Internet. The
+ 9 files listed below are available for anonymous ftp access on
+ ftp.microsoft.com in the /developr/drg/TrueType-Info directory. The
+ most important of those files is the TrueType Font Files
+ Specifications, a 400 page book which describes in excruciating detail
+ how to build a TrueType font. Other information is also available in
+ the same directory and other files will be added from time to time.
+
+ For those people who do not have ftp access to the Internet can find the
+ same information available for downloading on Compuserve in the
+ Microsoft developer relations forum (GO MSDR) in the TrueType library.
+
+ Please be aware that the TrueType specifications is a copyrighted work
+ of Microsoft and Apple and can not be resold for profit.
+
+ TrueType developer information files on ftp.microsoft.com:
+
+ 1. ttspec1.zip, ttspec2.zip, and ttspec3.zip
+
+ The TrueType Specification:
+
+ These three compressed files contain the "TrueType Font Files
+ Specifications", a 400 page book complete with illustrations which
+ details how to construct a TrueType font from scratch (or build
+ a tool to do so), the TrueType programming language, and the
+ complete format of each sub-table contained in the .TTF file.
+ These documents are stored in Word for Windows 2.0 format and
+ require Windows 3.1 for printing. See the "readme.doc" (in
+ ttspec1.zip) for printing instructions. Requires 2.5MB of disk
+ space after uncompression.
+
+ This manual is a superset of the similar specifications from Apple
+ and has added information specific to Windows that is not
+ present in the Apple version.
+
+ 2. ttfdump.zip
+
+ An MS-DOS executable which will dump the contents of a TrueType
+ font out in a human-readable fashion. It allows you to dump the
+ entire font, or just specific sub-tables. This tool, combined
+ with the specifications above, allows very effective debugging
+ or exploration of any TrueType font. For example, to dump the
+ contents of the 'cmap' (character code to glyph index mapping)
+ table, enter:
+
+ ttfdump fontname.ttf -tcmap -nx
+
+ Entering "ttfdump" with no options will give you a help message.
+
+ 3. ttfname.zip
+
+ Example C source code on how to parse the contents of a TrueType
+ font. Although this particular example will open up the file
+ and locate the font name contained within the 'name' table, it
+ could be readily adapted to parse any other structure in the
+ file. This compressed zip file also contains many useful
+ include files which have pre-defined structures set up for the
+ internal tables of a TrueType font file. This code may be
+ useful for developers who wish to parse the TrueType data stream
+ returned by the GetFontData() API in Windows 3.1.
+
+ 4. tt-win.zip
+
+ A 31 page Word for Windows 2.0 document which is targeted for the
+ Windows developer who is interested in learning about some of the
+ capabilities TrueType adds to Windows 3.1. Contains many
+ illustrations.
+
+ 5. embeddin.zip
+
+ A text file which describes all of the information necessary for a
+ Windows developer to add TrueType font embedding capabilities to
+ their application. Font embedding allows the application to
+ bundle the TrueType fonts that were used in that document and
+ transport it to another platform where the document can be
+ viewed or printed correctly.
+
+ 6. tt-talk.zip
+
+ The TrueType Technical Talks 1 and 2. These text files describe
+ some of the things that are happening with TrueType behind the
+ scenes in Windows 3.1. The first document walks the reader
+ through all of the steps that occur from when the user first
+ presses the key on the keyboard until that character appears on
+ the screen (scaling, hinting, drop out control, caching and
+ blitting). The second talk describes one of the unique features
+ of TrueType called non-linear scaling which allows the font
+ vendor to overcome some of the physical limitations of low
+ resolution output devices.
+
+ 7. lucida.zip
+
+ This text file contains useful typographic information on the 22
+ Lucida fonts which are contained in the Microsoft TrueType Font
+ Pack for Windows. It gives pointers on line-layout, mixing and
+ matching fonts in the family and a little history on each
+ typeface. This information was written by the font's designers,
+ Chuck Bigelow & Kris Holmes."
+
+Subject: 1.22. Unicode
+
+ [ed: This is a summary of the Unicode info I've gleaned from the net
+ recently, the whole Unicode issue needs to be addressed better by the
+ FAQ...someday... someday...I'll get to reorganize the whole thing]
+
+ What Is Unicode?
+ ================
+
+ Charles A. Bigelow notes:
+
+ The authors of the Unicode standard emphasize the fact that Unicode is a
+ character encoding, not a glyph encoding. This might seem like a
+ metaphysical distinction, in which characters have some "semantic"
+ content (that is, they signify something to literates) and and glyphs
+ are particular instantiations or renderings of characters--Plato talked
+ about this kind of stuff--but in practice it means that most ligatures
+ are not represented in Unicode, nor swash variants, nor figure variants
+ (except for superior and inferior, which are semantically distinct from
+ baseline figures), and so on.
+
+ For further information, consult The Unicode Standard: Worldwide
+ Character Encoding Version 1.0, Vol. 1 (alphabets & symbols) and Vol 2.
+ (Chinese, Japanese, Korean characters), by The Unicode Consortium,
+ Addison Wesley Publishing Co, 1991, ISBN 0-201-56788-1, 0-201-60845-6.
+
+ What is the Unicode Consortium?
+ ===============================
+
+ The Unicode Consortium is an international body responsible for
+ maintaining the Unicode standard. Their email address is
+ <unicode-inc@unicode.org>
+
+ To obtain more information on Unicode or to order their printed material
+ and/or diskettes contact:
+
+ Steven A. Greenfield
+
+ Unicode Office Manager
+
+ 1965 Charleston Road
+
+ Mountain View, CA 94043
+
+ Tel. 415-966-4189
+
+ Fax. 415-966-1637
+
+ Unicode Editing
+ ===============
+
+ James Matthew Farrow contributes:
+
+ I use `sam' for all by text editing. It is X editor based on an editor
+ for the blit called jim. Papers describing sam as well as a
+ distribution of sam itself are available for ftp from research.att.com.
+ The sam there is a Unix port of the Plan 9 version. Plan 9 is a full
+ unicode operating system, even around before NT! The libraries sam is
+ built upon therefore support 16 bit wide characters. The graphics
+ library, supplied with it at present does not. However they may be
+ planning to distribute a new version which does soon. The library just
+ plugs in replacing the library that comes with sam. No modification is
+ necessary. Character are stored using the utf-2 encoding.
+
+ All of the files I had before I started working with sam were 7 bit
+ ascii so no conversion was needed. Now I have ditched xterm in favour
+ of 9term: a terminal emulator in the style of 81/2 (the Plan 9
+ interface). This lets me type Unicode characters on the command line,
+ as part of filenames, in mail, wherever and most Unix utilities cope
+ without modification. This is about to be released. I'm looking for
+ beta testers. ;-)
+
+ Is a special keyboard required?
+ -------------------------------
+
+ No. ASCII Characters are typed as normal. Common characters above
+ 0x7f are typed using two letter abbreviations. The table is similar to
+ the troff special character codes, e.g, Alt-12 gives you a 1/2, Alt-'e
+ gives you e acute, Alt-bu a bullet and so on. This table is hardwired
+ into the library at present but is trivial to change. Other codes are
+ accessed by typing their hex value, for instance the smiley is
+ Alt-X263a (0x263a being a smiley character in the Unicode character
+ set).
+
+ Is roman-to-Unicode conversion available?
+ -----------------------------------------
+
+ All normal 7 bit ascii characters are encoded as themselves so no
+ translation is needed. There are conversion routines in the library
+ (runetochar and chartorune) which will do the conversion and it should
+ be pretty simple to convert files already in another format. You would
+ have to write something to do the transliteration yourself. A small
+ patch to the system would let you enter different language `modes' for
+ text entry.
+
+ Are there PostScript or TrueType fonts available?
+ =================================================
+
+ Apparently there is a version of the Lucida fonts by Bigelow and Holmes
+ which support Unicode. This is the information I have on them.
+
+ [ed: quoting another source]
+
+ [Windows NT] will ship with a Unicode TrueType font containing
+ approximately 1,500 characters. The font is called "Lucida Sans
+ Unicode" and was specifically designed by Bigelow and Holmes for
+ Microsoft to contain the following Unicode sets:
+
+ ASCII
+ Latin 1
+ European Latin
+ Extended Latin
+ Standard Phonetic
+ Modifier Letters
+ Generic Diacritical
+ Greek
+ Cyrillic
+ Extended Cyrillic
+ Hebrew
+ Currency Symbols
+ Letterlike Symbols
+ Arrows
+ Mathematical Operators
+ Super & Subscript
+ Form & Chart Components
+ Blocks
+ Geometric Shapes
+ Miscellaneous Technical
+ Miscellaneous Dingbats
+
+ The bitmap fonts which comes with the utf version of the libXg graphics
+ library (the library upon which sam is built) support a sparse subset
+ of the full character set. That is, only a few of them have glyphs at
+ present. A font editor such as xfedor would let you add more. The list
+ of those currently available is pretty much as the above list.
+
+ I use 9term and sam as a matter of course now and have for several
+ months. I enjoy the convenience of putting special characters and
+ accented characters in my mail as well as being able to do some
+ phonetic work all in the one terminal/editor suite.
+
+Subject: 1.23. Can I Print Checks with the MICR Font?
+
+ This comes up all the time: standard ordinary laser toner is magnetic
+ and will be read by the banks. The gotcha is that standard laser toner
+ rubs off in the *very* high-speed sorting equipment that are used, and
+ this makes read rates drop low and the banks will hate you.
+
+ I researched check printers for a customer, and was surprised to find
+ this. The Troy(tm) printers he bought are basically stock Ricoh
+ engines that have slightly tighter paper handling (for registration),
+ plus they add a proprietary Teflon-type powder coating on the output
+ path to coat the checks.
+
+ I saw some examples of checks printed with and without this special
+ coating after running through something like 40 passes through check
+ processing equipment, and the one without the coating was a mess. These
+ require special handling that the banks do *not* like. Apparently,
+ they go after companies that issue these kinds of checks with special
+ processing fees.
+
+Subject: 1.24. Rules of Thumb
+
+ It is difficult to set out guidelines for font usage, because almost
+ any rule can be brilliantly broken under the right circumstances.
+
+ * General guidelines:
+
+ * Never lose track of the kind of work you're doing. An effect
+ that would ruin a newsletter might be just the thing for a
+ record cover. Know when you can safely sacrifice legibility
+ for artistic effect.
+
+ * Keep in mind the final reproduction process you'll be using.
+ Some effects (like reversed type, white on black) can be hard
+ to read off an ordinary 300-dpi laser, but will work if
+ finals are done on a high-resolution printer, such as a
+ Linotronic. Will the pages be photocopied? Offset? Onto rough
+ paper, shiny paper? All these factors can and should
+ influence your choice of fonts and how you use them.
+
+ * Running some comparative tests is a good idea. Better to blow
+ off a few sheets of laser paper now than to see a problem
+ after thousands of copies are made.
+
+ * No one can teach you font aesthetics; it must be learned by
+ example. Look at beautiful magazines, posters, books with
+ wide eyes, so that you can see how it's done. Examine ugly
+ printed matter critically and consider why it's hard to read.
+
+ * Good rules of thumb:
+
+ * If you need a condensed font, find one that was designed that
+ way, rather than scaling an existing font down to a
+ percentage. Any scaling distorts a font's design; excessive
+ scaling interferes with legibility - this goes for widening
+ as well as narrowing. Extended faces do exist, although they
+ aren't as common as condensed ones.
+
+ * Many people feel that bold or italic type, or type in ALL
+ CAPS, is more legible: "This is the most important part of
+ the newsletter, let's put it in bold." In fact, legibility
+ studies show that such type is actually harder to read in
+ bulk. Keep the text in a normal style and weight, and find
+ another way to emphasize it - box it, illustrate it, run it
+ in color, position it focally.
+
+ * Too much reverse type - white on black - is hard on the eyes.
+ It can be a nice effect if used sparingly. Don't reverse a
+ serif font, though - its details will tend to fill in. Stick
+ to reversing bold sans-serifs, and remember to space them out
+ a bit more than usual.
+
+ * It is always safest to use a plain serif font for large
+ amounts of text. Because Times is widely used, it doesn't
+ mean it should be avoided. Fonts like Palatino, Times,
+ Century Old Style are deservedly popular because people can
+ read a lot of text set in such faces without strain.
+
+ Don't expect anyone to read extensive text set in a condensed
+ font.
+
+ * As point size gets bigger, track tighter, and (if the
+ software allows) reduce the spacebands as well. A spaceband
+ in a headline size (anything over 14 point) should be about
+ as wide as a letter "i".
+
+ * If you only have a few large headlines, hand-kerning the
+ type, pair by pair, can make the end result much more
+ pleasing. Besides, working with fonts this closely makes
+ them familiar.
+
+ * Column width and justification are major elements in design.
+ The narrower the column, the smaller the type can be; wide
+ rows of small type are very hard to read. Often it's a better
+ idea to set narrow columns flush left rather than justified,
+ otherwise large gaps can fall where hyphenation isn't
+ possible.
+
+ * Use curly quotes.
+
+ * Don't put two spaces at the end of a line (. ) instead of (.
+ ) when using a proportionally spaced font.
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 1.25. Acknowledgements
+
+ The moderators would like to express their gratitude to the whole
+ community for providing insightful answers to innumerable questions. In
+ particular, the following people (listed alphabetically) have
+ contributed directly to this FAQ (apologies, in advance, if anyone has
+ been forgotten):
+
+ Masumi Abe <abe@keleida.com>
+
+ Glenn Adams <glenn@metis.COM>
+
+ Daniel Amor <daniel.amor@student.uni-tuebingen.de>
+
+ Borris Balzer <borris@boba.rhein-main.DE>
+
+ Charles A. Bigelow <bigelow@cs.stanford.edu>
+
+ David J. Birnbaum <djbpitt@pitt.edu>
+
+ Tim Bradshaw <tim.bradshaw@edinburgh.ac.UK>
+
+ Morgan S. Brilliant <???>
+
+ Arlen Britton <arlenb@mcad.edu>
+
+ Stan Brown <brown@ncoast.org>
+
+ Scott Brumage <brumage@mailer.acns.fsu.edu>
+
+ Lee Cambell <elwin@media.mit.edu>
+
+ Terry Carroll <tjc50@juts.ccc.amdahl.com>
+
+ Gerd Castan <G.Castan@physik.uni-stuttgart.de>
+
+ Ari Davidow <ari@netcom.com>
+
+ Eve Damaziere <bortzmeyer@cnam.fr> (c/o Stephane Bortzmeyer)
+
+ Lawrence D'Oliveiro <ldo@waikato.ac.nz>
+
+ Pat Farrell <pfarrell@cs.gmu.edu>
+
+ James Matthew Farrow <matty@cs.su.oz.au>
+
+ Stephen Friedl <friedl@mtndew.Tustin.CA.US>
+
+ Peter J. Gentry <peter@utas.artsci.utoronto.ca>
+
+ Yossi Gil <yogi@techunix.technion.ac.IL>
+
+ Timothy Golobic <an314@cleveland.Freenet.EDU>
+
+ Kesh Govinder <govinder@ph.und.ac.za>
+
+ Piercarlo Antonio Grandi <pcg@decb.aber.ac.uk>
+
+ Robert Green <rag5@cornell.edu>
+
+ Rick Heli <Rick.Heli@Eng.Sun.COM>
+
+ Jeremy Henderson <jeremy@castle.ed.ac.uk>
+
+ Henry ??? <henry@trilithon.COM>
+
+ Gary <Gocek.Henr801C@Xerox.COM>
+
+ Berthold K.P. Horn <bkph@ai.mit.edu>
+
+ Peter Honig <peterh@macsch.com>
+
+ Don Hosek <dhosek@quixote.com>
+
+ Bharathi Jagadeesh <bjag@nwu.edu>
+
+ Chang Jin-woong <jwjang@krissol.kriss.re.kr>
+
+ Darrell Leland <dleland@nmsu.edu>
+
+ David Lemon <lemon@adobe.com>
+
+ Jon <jgm@cs.brown.EDU>
+
+ ??? <vkautto@snakemail.hut.FI>
+
+ ??? <robertk@lotatg.lotus.COM>
+
+ Otto Makela <otto@jybox.jyu.fi>
+
+ David Mandl <dmandl@bilbo.shearson.com>
+
+ Kate McDonnell <C_MCDON@pavo.concordia.ca>
+
+ George Moore <georgem@microsoft.com>
+
+ Robert Morris <ram@claude.cs.umb.EDU>
+
+ Stephen Moye <SMOYE@BROWNVM.brown.edu>
+
+ Erlend Nagel <error@stack.urc.tue.nl>
+
+ Terry O'Donnell <odonnell@mv.us.adobe.COM>
+
+ Rick Pali <Rick_Pali@f328.n163.z1.jammys.net>
+
+ Sean Palmer <sean.palmer@delta.com>
+
+ Jon Pastor <pastor@VFL.Paramax.COM>
+
+ PenDragon <REGY116@cantva.canterbury.ac.nz>
+
+ Stephen Peters <speters@us.oracle.COM>
+
+ Bill Phillips <wfp@world.std.com>
+
+ Thomas W. Phinney <75671.2441@compuserve.com>
+
+ Jim Reese <Jim.Rees@umich.edu>
+
+ Bill Ricker <wdr@world.std.com>
+
+ Liam Quin <lee@sq.com>
+
+ Henry Schneiker <?>
+
+ Tom Scott <tims@megatek.com>
+
+ Bill Shirley <bshirley@gleap.jpunix.COM>
+
+ Cameron Smith <cameron@symcom.math.uiuc.edu>
+
+ Daniel S. Smith <dsmith@jericho.mc.com>
+
+ Frank F. Smith <ffs1@cornell.edu>
+
+ Werenfried Spit <SPIT@vm.ci.uv.ES>
+
+ Anthony Starks <ajs@merck.com>
+
+ Ike Stoddard <stoddard@draper.com>
+
+ Danny Thomas <vthrc@mailbox.uq.oz.au>
+
+ Anders Thulin <ath@linkoping.trab.se>
+
+ Ian Tresman <72240.3447@compuserve.com>
+
+ Bill Troop <biltroop@ix.netcom.com>
+
+ Erik-Jan Vens <E.J.Vens@icce.rug.nl>
+
+ Amanda Walker <amanda@visix.com>
+
+ Jason Lee Weiler <weilej@nuge110.its.rpi.edu>
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(4_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(4_6)
new file mode 100644
index 0000000000..ccc090f2f2
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(4_6)
@@ -0,0 +1,1027 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (4/6)
+Supersedes: <font-faq-4_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:26 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 1004
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-4_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48303 comp.answers:20517 news.answers:79238
+
+Archive-name: fonts-faq/part4
+Version: 2.1.5
+
+Subject: 1.26. A Brief Introduction to Typography
+
+ Space, time, and bandwidth are too limiting to provide a complete
+ introduction to typography in this space. I'd be very willing to make
+ one available for anonymous ftp, if you want to write one, but I'm not
+ going to write it-I have neither the time nor the expertise. However,
+ the following description of Times, Helvetica, and Courier will suffice
+ for a start. For more information, several books on typography are
+ listed in the bibliography.
+
+ Comments by Laurence Penney:
+ ============================
+
+ Laurence Penney offers the following description of Times, Helvetica,
+ and Courier:
+
+ Times is a typeface designed in the 1930s for the Times newspaper in
+ London and is now used widely in books, magazines and DTP. Its design
+ is based on the typographical principles evolved since Roman times
+ (upper case) and the 16th century (lower case). It is called a
+ TRANSITIONAL typeface, after the typefaces of the 17th century which it
+ resembles. Like all typefaces designed for typesetting large
+ quantities of text, it is proportionally spaced: the i takes about a
+ third the width of an M. Personally I don't like Times too much and
+ prefer the more elegant Garamond and Baskerville, but these will
+ probably cost you money... Note: The Transitionals came after the Old
+ Styles (like Garamond) and before the Moderns (like Bodoni).
+
+ Helvetica is an example of a SANS-SERIF typeface. These first appeared
+ in the late 19th century in Germany and flourished in the 1920s and
+ 30s, when they were regarded as the future of typography. It's more a
+ geometric design than the humanist design of Gill Sans, but less
+ geometric than Avant Garde and Futura. To my mind it lacks elegance,
+ and Adrian Frutiger's Univers shows how this kind of typeface should be
+ done. (Just compare the B, R, Q, a, g of Univers and Helvetica to see
+ what I mean - and don't you just love Univers's superbly interpreted
+ ampersand ?!) Helvetica is one of the few fonts that is improved by its
+ BOLD version.
+
+ Another interesting approach to sans-serif is Optima, by Hermann Zapf,
+ which keeps the stroke-weight variations which sans-serifs usually
+ reject. Use sans-serif fonts for the same applications as Times, above,
+ but where you're less concerned with elegance, and more with a
+ functional appearance - they're generally reckoned to be slightly less
+ legible than good serifed fonts. They're also very suitable for display
+ work.
+
+ Courier is a typeface derived from typewriter styles. It should ONLY be
+ used when you want to simulate this effect (e.g. when writing letters
+ Courier usually appears "friendlier" than Times). Like all typewriter
+ fonts, it is MONOSPACED (characters all have the same width) and is
+ thus suitable for typesetting computer programs. However there are
+ nicer looking monospace fonts than Courier (which has oversize serifs),
+ that still remain distinct from the text fonts like Times and
+ Helvetica. A good one is OCR-B, designed by Frutiger. Note that
+ monospaced fonts are less economical on space than proportional fonts.
+
+ [ed: Following the original posting of this message, Laurence Penny and
+ Jason Kim discussed the issue privately. The following summary of
+ their discussion may serve to clarify some of the more subtle points.
+ My thanks to Laurence and Jason for allowing me to include this in the
+ FAQ.]
+
+ -----------------------------
+
+ LP-1> The Transitionals came after the Old Styles (like Garamond) and
+ before the Moderns (like Bodoni).
+
+ JK> Not necessarily true! Ideologically, yes, but not chronologically.
+ I believe, for example, that Bodoni predates New Century Schoolbook or
+ some such typeface.
+
+ LP-2> What I meant by "X came after Y" was "the first examples of X
+ appeared after the first examples of Y" - it's called precis. Some
+ people still make steam trains, but you can still say "Steam engines
+ came before diesels." This is chronological, not ideological in my book.
+
+ -----------------------------
+
+ LP-1> Another interesting approach to sans-serif is Optima, by Hermann
+ Zapf, which keeps the stroke-weight variations which sans-serifs
+ usually reject. Use sans-serif fonts for the same applications as
+ Times, above, but where you're less concerned with elegance, and more
+ with a functional appearance - they're generally reckoned to be
+ slightly less legible than good seriffed fonts. They're also very
+ suitable for display work.
+
+ JK> Slightly? I have several textbooks typeset by utter fools and they
+ are a pain in the ass (and eyes) to read! Please don't encourage anyone
+ to use Optima (or any sans serif fonts for that matter) "for the same
+ applications as Times," which, need I remind you, was designed for
+ *newspaper* work!!
+
+ LP-2> OK, maybe I was a little over-generous to Univers, Helvetica,
+ etc., but I think variation is extremely important in typography. Have
+ you ever read the British magazine "CAR" ? That uses Helvetica light (I
+ think) in a very legible and attractive way, IMO. I agree, though,
+ Optima is crappy for text, but it's a very valuable experiment and
+ looks beautiful when printed in high quality for titling, etc. And yes,
+ *books* in Helvetica are generally awful.
+
+ -----------------------------
+
+ JK> Serifs have been scientifically shown to be a *lot* easier on the
+ reader, as they guide the eyes along the lines.
+
+ LP-2> In all tests I've seen the serifs have always won the day, but
+ only with certain seriffed fonts, and fonts like Univers aren't far
+ behind. The "tracking" advantage for serif fonts is reduced when you're
+ talking about narrow newspaper/magazine columns.
+
+ -----------------------------
+
+ JK> You wrote a pretty short and partial history of type. Why ignore
+ the roots of type (blackletter) as well as the climax (moderns-give an
+ explanation) and subsequent 'post-modern' revivals?
+
+ LP-2> I was just talking about the place the 3 most common DTP types
+ hold in the history of typography, and a few associated pitfalls. It
+ wasn't meant as a "history of typography" at all. Please feel free to
+ provide such a history yourself.
+
+ JK> I think any short list of specific faces is incomplete without
+ mention of Palatino, the most popular Old Style revival in existence.
+
+ LP-2> Do you? To my mind Palatino is grossly over used. You must agree
+ it looks bad for dense text. It isn't a proper "oldstyle revival" at
+ all, more of a "calligraphic interpretation" of it. Zapf designed it as
+ a display face, and wasn't too concerned about lining up the serifs
+ (check out the "t"). And it just *has* to be printed on 1200dpi devices
+ (at least) to look good in small sizes. OK then, maybe a short list is
+ incomplete without a caution NOT to use Palatino...
+
+ JK> Also, if this is meant to be a "quick history/user guide for those
+ fairly new to using fonts on desktop publishing systems," then I would
+ recommend more directions about the proper uses of certain faces (e.g.,
+ Goudy for shaped text, Peignot for display *only*) and styles (e.g.,
+ italics for editorial comments, all-caps for basically nothing).
+
+ LP-2> Okay, okay. I was only sharing a few ideas, not trying to write a
+ book. Surely you agree that the 3 typefaces I chose are by far the most
+ commonly used and abused these days? I don't think a discussion of
+ Goudy or Peignot fits in very well here, unless we're hoping to make a
+ very wide-ranging FAQL. Regarding styles: first, italics are used
+ principally for *emphasis* (rather than bold in running text); second,
+ all good books have a few small caps here and there, don't they? - all
+ mine do...
+
+ JK> Sorry if I come across as critical. I think the idea of making a
+ FAQL is a good one, as is your effort. We just have to make sure it
+ doesn't give any newbies the wrong impressions and further perpetuate
+ the typographical morass we're facing today.
+
+ LP-2> Sorry if I come across as defensive, but I stand by what I said
+ and object to the suggestion that I am "perpetuating the typographical
+ morass". (I don't know if you really intended this - apologies if you
+ didn't.)
+
+ Comments by Don Hosek:
+ ======================
+
+ Don Hosek offers the following additional notes:
+
+ The "Times" in most printers is actually a newer version of the font
+ than Monotype's "Times New Roman" which it is originally based on.
+ Walter Tracy's _Letters of Credit_ gives an excellent history of the
+ face which was based on Plantin and in the original cutting has metrics
+ matching the original face almost exactly. Another interesting note
+ about the face is that it is almost a completely different design in
+ the bold: this is due to the fact that old-styles are difficult to
+ design as a bold. Incidentally, the classification of Times as a
+ transitional is not firm. It likely is placed there by some type
+ taxonomists (most notably Alexander Lawson) because of the bold and a
+ few minor features. Others, myself included, think of it as a old
+ style. The typeface listed in the Adobe catalog as Times Europa was a
+ new face commissioned in 1974 to replace the old Times (whose 50th
+ birthday was this past October 3rd).
+
+ Hermann Zapf is not particularly pleased with any of the
+ phototypesetting versions of Optima. As a lead face, Optima is very
+ beautiful. His typeface "World", used in the World Book Encyclopedia is
+ one recutting for photocomp which improves the font somewhat. He is on
+ record as saying that if he had been asked, he would have designed a
+ new font for the technology.
+
+Subject: 1.27. A Brief History of Type
+
+ Thomas W. Phinney contributes the following discussion of the history
+ of type(1):
+
+ Foreword
+ ========
+
+ It is difficult to cover all the developments and movements of
+ typography in a short space. My separation of evolving technologies
+ from the development of typefaces is an artificial one--designs and the
+ technology used to create them are not truly separable--but perhaps it
+ is conceptually useful.
+
+ Where names of typefaces are used, I attempt to use the original name:
+ there are often clones with very similar names.
+
+ I shall update, clarify and correct this essay periodically, and will be
+ happy to credit contributors. I can be e-mailed on CompuServe at
+ 75671,2441 (Internet: 75671.2441@compuserve.com).
+
+ Type Technology--The Four Revolutions
+ =====================================
+
+ Gutenberg (ca. 1450-1480) & The Impact of Printing
+ --------------------------------------------------
+
+ Before the printing press, books were produced by scribes (at first,
+ primarily based in monasteries, although by the 12th century there were
+ many lay copiers serving the university market). The process of writing
+ out an entire book by hand was as labor-intensive as it sounds (try it
+ some time): so much so that a dozen volumes constituted a library, and a
+ hundred books was an awe- inspiring collection.
+
+ This remained true until the invention of movable type, the perfection
+ of which is attributed to Johannes Gutenberg (although the Chinese had
+ it several centuries earlier, and a Dutch fellow named Coster may have
+ had some crude form a decade earlier). Gutenberg, although a man of
+ vision, did not personally profit from his invention. He worked for over
+ a decade with borrowed capital, and his business was repossessed by his
+ investors before the first mass-produced book was successfully
+ printed--the Gutenberg Bible of 1454, printed in Mainz by Fust and
+ Schoeffer.
+
+ Gutenberg's basic process remained unchanged for centuries. A punch made
+ of steel, with a mirror image of the letter is struck into a piece of
+ softer metal. Molten metal is poured into this, and you get type. The
+ type is put into a matrix to form the page of text, inked, then pressed
+ into paper.
+
+ Within several decades typesetting technology spread across Europe.
+ The speed with which it did so is impressive: within the first fifty
+ years, there were over a thousand printers who set up shops in over two
+ hundred European cities. Typical print runs for early books were in the
+ neighborhood of two hundred to a thousand books.
+
+ Some of these first printers were artisans, while others were just
+ people who saw an opportunity for a quick lira/franc/pound. The modern
+ view of a classical era in which craftsmanship predominated appears
+ unjustified to scholars: there has always been fine craft, crass
+ commercialism, and work that combines both.
+
+ To those who have grown up with television, radio, magazines, books,
+ movies, faxes and networked computer communications it is difficult to
+ describe just how much of a revolution printing was. It was the first
+ mass medium, and allowed for the free spread of ideas in a completely
+ unprecedented fashion. The Protestant Reformation might not have
+ occurred, or might have been crushed, without the ability to quickly
+ create thousands of copies of Luther's Theses for distribution.
+
+ Many groups sought to control this new technology. Scribes fought
+ against the introduction of printing, because it could cost them their
+ livelihoods, and religious (and sometimes secular) authorities sought to
+ control what was printed. Sometimes this was successful: for centuries
+ in some European countries, books could only be printed by government
+ authorized printers, and nothing could be printed without the approval
+ of the Church. Printers would be held responsible rather than authors
+ for the spread of unwanted ideas, and some were even executed. But this
+ was a largely futile struggle, and most such restraints eventually
+ crumbled in the western world.
+
+ Industrial Revolution: Steam, Line-casting & Automated Punch-cutting (start 1870-95; end 1950-65)
+ -------------------------------------------------------------------------------------------------
+
+ Amazingly, the printing press and the science of typecutting had only
+ minor refinements from the late 1500s to the late 1800s. Towards the
+ end of this period, the industrial revolution brought major innovations
+ in printing technology. Rotary steam presses (steam 1814, rotary 1868)
+ replaced hand- operated ones, doing the same job in 16 per cent of the
+ time; photo-engraving took over from handmade printing plates.
+
+ Typesetting itself was transformed by the introduction of line-casting
+ machines, first Ottmar Mergenthaler's Linotype (1889), and then the
+ Monotype machine. Essentially, line-casting allowed type be chosen,
+ used, then recirculate back into the machine automatically. This not
+ only introduced a huge labor savings in typesetting, (again, on the
+ order of the 85% reduction in printing time), but also rendered
+ obsolete the huge masses of metal type created by the previously
+ existing type foundries.
+
+ While typesetting and printing speeds increased phenomenally, so did the
+ speed of punchcutting. In 1885, Linn Boyd Benton (then of Benton, Waldo
+ & Company, Milwaukee) invented a pantographic device that automated the
+ previously painstaking process of creating punches. His machine could
+ scale a drawing to the required size, as well as compressing or
+ expanding the characters, and varying the weight slightly to compensate
+ for the larger or smaller size-- this last being a crude form of the
+ "optical scaling" done by skilled typographers making versions of the
+ same font for different sizes. In optical scaling, the thickest strokes
+ retain the same relative thickness at any size, but the thinnest
+ strokes are not simply scaled up or down with the rest of the type, but
+ made thicker at small sizes and thinner at large display sizes, so as
+ to provide the best compromise between art and readability.
+
+ The economic impact of all these advances on the type industry cannot be
+ overstated. For example, in the United States, the majority of type
+ foundries escaped a bankruptcy bloodbath in 1892 by merging into a
+ single company, called American Type Founders (ATF). Ultimately
+ twenty-three companies merged into ATF, making it far and away the
+ dominant American type foundry.
+
+ Also around this time, the "point" measurement system finally reached
+ ascendancy. In the earlier days of printing, different sizes of type had
+ simply been called by different names. Thus, "Brevier" was simply the
+ British name for 8-point type of any style. Unfortunately, these names
+ were not standardized internationally; 8-point type was called "Petit
+ Texte" by the French and "Testino" by the Italians. Such a naming
+ system also allowed wonderful confusion, such as "English" referring
+ both to blackletter type, and a 14-point size; "English English" was
+ thus a 14-point blackletter!
+
+ Pierre Simon Fournier had first proposed a comprehensive point system in
+ 1737, with later refinements, but what was ultimately adopted was the
+ later version developed by Francois Ambroise Didot. This put
+ approximately 72 points to the inch (and now exactly 72 points to the
+ inch on most computer- based typesetting systems).
+
+ Photocomposition (Intertype et. al., start 1950-60, end 1975-85)
+ ----------------------------------------------------------------
+
+ The first photocomposition devices (the French "Photon" and Intertype's
+ Fotosetter) made their debuts as early as 1944, but didn't really catch
+ on until the early 1950s. Typeface masters for photocomposition are on
+ film; the characters are projected onto photo-sensitive paper. Lenses
+ are used to adjust the size of the image, scaling the type to the
+ desired size. In some senses this technology was an "improvement,"
+ allowing new freedoms, such as overlapping characters. However, it
+ also pretty much eliminated optical scaling (see 2.2, above), because
+ in the rush to convert fonts to the new format, usually only one design
+ was used, which was directly scaled to the desired size.
+
+ Digital (start 1973-83)
+ -----------------------
+
+ The earliest computer-based typesetters were a hybrid between the above-
+ mentioned photocomposition machines and later pure digital output. They
+ each had their own command language for communicating with output
+ devices. Although these machines had advantages, they also had
+ problems. None of these early command languages handled graphics well,
+ and they all had their own formats for fonts. However, some of these
+ devices are still in service as of 1995, for use in production
+ environments which require more speed and less flexibility (phone
+ books, newspapers, flight schedules, etc.).
+
+ In the late 1980s PostScript gradually emerged as the de facto standard
+ for digital typesetting. This was due to a variety of reasons,
+ including its inclusion in the Apple Laserwriter printer and its
+ powerful graphics handling. When combined with the Macintosh (the
+ first widely used computer with a what-you-see-is-what-you-get display)
+ and PageMaker (the first desktop publishing program), the seeds were
+ all sown for the current dominance of computer-based typesetting.
+
+ Most high-end typesetting still involves printing to film, and then
+ making printing plates from the film. However, the increasing use of
+ high- resolution printers (600-1200 dots per inch) makes the use of
+ actual printing presses unnecessary for some jobs. And the next step
+ for press printing is the elimination of film altogether, as is done by
+ a few special systems today, in which the computer can directly create
+ printing plates.
+
+ Today, although PostScript predominates, there are a variety of
+ competing page description languages (PostScript, HP PCL, etc.), font
+ formats (Postscript Type One and Multiple Master, Truetype and Truetype
+ GX) computer hardware platforms (Mac, Windows, etc.) and desktop
+ publishing and graphics programs. Digital typesetting is commonplace,
+ and photocomposition is at least dying, if not all but dead. Digital
+ typefaces on computer, whether Postscript or some other format, are
+ generally outline typefaces, which may be scaled to any desired size
+ (although optical scaling is still an issue).
+
+ There has been considerable economic fallout from all this in
+ typography. Although some digital type design tools are beyond the
+ price range of the "average" user, many are in the same price range as
+ the mid- to high-end graphics and desktop publishing programs. This,
+ combined with the introduction of CD-ROM typeface collections, has
+ moved digital type away from being an expensive, specialized tool,
+ towards becoming a commodity. As a result of both this and the brief
+ photocomposition interregnum, the previously established companies have
+ undergone major shakeups, and even some major vendors, such as American
+ Type Founders, have failed to successfully make the digital transition,
+ and gone bankrupt instead (although at this time ATF appears to be
+ undergoing a resurrection). More recently, even major digital type
+ foundries have-dare one say foundered?-on the shoals of ubiquitous
+ cheap typefaces (even a licensing deal with Corel Corp seems to have
+ been insufficient to save URW).
+
+ Although there is a new accessibility of type design tools for hobbyists
+ and professional graphic artists, the decreasing value of individual
+ typefaces has resulted in a decrease in the number of working type
+ designers per se (both independents and company-employed).
+
+ Type Forms Through the Centuries
+ ================================
+
+ One must keep in mind that although typefaces may have come into use at
+ a particular point in time, they often continued in general use far
+ beyond that time. Even after the rise of old style typefaces in the
+ late 1500s, the blackletter type was commonly used for setting text for
+ several centuries (well into the 1900s in Germany). With later
+ interpretations of earlier forms being relatively common, the *style*
+ of a given typeface may belong to a quite different period from that of
+ the typeface itself! Further, many typefaces have very complex
+ histories: a type could have been originally designed in metal at one
+ time, reworked by someone else later, made into a phototypesetting face
+ by another person, and then later created in digital form by yet
+ another designer--who might have been working off of any of the above
+ as the basis of their work.
+
+ The classification system used here (old style, transitional, modern,
+ sans serif, slab serif, etc.) has the virtues of being both simple and
+ widely used. However, the precision and artistic accuracy of this
+ system is perhaps dubious: see Robert Bringhurst's Elements of
+ Typographic Style or his article in the first issue of Serif magazine
+ for a more thorough system.
+
+ In discussing the differences between type, one must refer to a number
+ of technical terms. For illustrations of these terms, see also the
+ downloadable graphics file TYPHS_72.GIF or TYPHS300.GIF. The numbers
+ refer to the dots per inch of the graphic when scaled to a full page:
+ 72 dpi is a low resolution suitable for screen viewing, while 300 dpi
+ is better-suited to laser printing. With any luck, both should be
+ available for FTP or download from the same site as this file. If so,
+ you would be well advised to refer to these pictures for illustrations
+ of both these terms and the differences between different categories of
+ typefaces. If you are a newcomer to typography, some sort of visual
+ reference is essential to understand the differences between fonts
+ explained here. Your options include: the aforementioned graphics
+ files; type samples from a book, manual or font vendor's catalog; or
+ simply viewing or printing out the fonts you have available on your
+ computer system, if you have a reasonable variety.
+
+ Definitions
+ -----------
+
+ Contrast: The degree of difference between the thick and thin strokes in
+ a font (if any).
+
+ Stress (axis): The angle at which contrast occurs, usually ranging from
+ vertical to a somewhat back-slanted diagonal. This can best be noted by
+ looking at, for example, the letter "O" and noting if the bottom left is
+ thicker than the top left, and the top right is thicker than the bottom
+ right. If this difference exists, the letter has diagonal stress. If
+ the two halves of the "O" are a mirror image of each other, with the
+ sides thicker than the top/bottom, then the letter has vertical stress.
+ If the top and bottom of the "O" are the same thickness as the sides,
+ there is neither contrast nor stress.
+
+ Serifs: Those "finishing strokes" or "fillips" going off the ending
+ lines of a letter. For example, when the number "1" or the letter "i"
+ are drawn with a bar across the bottom, the two halves of the bar are
+ serifs. If the serif is joined to the letter by a slight flaring out,
+ it is said to be "bracketed."
+
+ Early Letterforms
+ -----------------
+
+ Although writing itself can be traced back to several millennia B.C., to
+ Egyptian hieroglyphics and Sumerian cuneiform inscriptions, modern
+ letter forms have their most immediate heritage in Roman inscriptions
+ from around 50- 120 AD, such as the one on the base of Trajan's Column
+ in the Roman Forum (114 AD, digital version by Twombly for Adobe, 1989).
+
+ Although early Latin writing was heavily influenced by these chiseled-
+ in-stone letterforms, over the centuries it evolved into a variety of
+ other shapes, including uncials and the related Carolingian script. It
+ is through this period of the sixth to tenth centuries that we see the
+ development of the lower case (minuscule) letter as a different shape
+ from the upper case (capital).
+
+ Type forms similar to what we now think of as "normal" letter shapes
+ evolved from the Carolingian (or Caroline) minuscule. The Carolingian
+ letters are so-called because of their adoption by the Emperor
+ Charlemagne (late 10th century) as a standard for education. Digital
+ revivals of these exist, such as Carol Twombly's Charlemagne (1989).
+
+ By the fifteenth century, italics also existed, in the form of a cursive
+ script which had developed in Rome and Florence. However, italics at
+ this time were a completely separate entity from the upright
+ letterforms, as they remained in the early days of printing.
+
+ Blackletter
+ -----------
+
+ The first printed types exemplify what most people think of as medieval
+ or "old English" lettering, with ornate capitals, roughly diamond-shaped
+ serifs, and thick lines. As a group, these typefaces are called
+ "blackletter." They evolved from the Carolingian by a gradual movement
+ towards narrowing and thickening of lines.
+
+ The general sort of blackletter used by Gutenberg in his first Bible is
+ called textura (a shareware digital version of Gutenberg's bible face is
+ available, called "Good City Modern"). The other sorts of blackletter
+ are fraktur, bastarda and rotunda. Probably the most common blackletter
+ revival typefaces in use today are Cloister Black (M.F. Benton, 1904,
+ from J.W. Phinney) and Fette Fraktur.
+
+ It is worth noting that although these typefaces seem very hard to read
+ to us today, this is due as much to familiarity as to any objective
+ lesser clarity. Fraktur was in use in Germany well into the 1900s,
+ though it was gradually being superseded by Roman typefaces. The Nazis
+ at first fostered a return to Fraktur, then outlawed it as a "Jewish
+ typeface" in 1940.
+
+ Studies from mid-century found that people can read blackletter with a
+ speed loss of no more than 15%. However, there is subjectively more
+ effort involved. Blackletter is today most appropriate for display or
+ headline purposes, when one wants to invoke the feeling of a particular
+ era.
+
+ Old Style Typefaces: Centaur, Bembo, Jenson, Garamond, Caslon
+ -------------------------------------------------------------
+
+ E.P. Goldschmidt, as explained by Stanley Morison, claimed that "the
+ supersession of black-letter was not due to any 'technical advance,' it
+ was the visible expression of a changed attitude of mind." The
+ Renaissance was typified by an obsession with things "classical," in
+ the Greco-Roman sense, which had major implications for typography. The
+ neo-classical letterforms were somewhat more condensed than the
+ Carolingian shapes, but much rounder and more expanded than the
+ blackletter.
+
+ Old style type is generally considered "warm" or friendly, thanks to
+ its origins in Renaissance humanism. The main characteristics of old
+ style typefaces are low contrast with diagonal stress, and cove or
+ "bracketed" serifs (serifs with a rounded join to the stem of the
+ letter). The earliest (Venetian or Renaissance) old style typefaces
+ (originally 15th-16th Century) have very minimal contrast, and a sloped
+ cross-bar on the lower-case "e." One such is Bruce Rogers' Centaur
+ (1916), based on Jenson. Similarly, Monotype's Bembo (1929) is based on
+ the work of Francesco Griffo, circa 1499.
+
+ Italics at this point were still independent designs, and were generally
+ used completely separately; a whole book could be set in italics.
+ Probably the most famous italic of the period is Arrighi's (1524),
+ which may be seen today as the italic form of Centaur. Likewise, the
+ italic form of Bembo is based on the italic of Tagliente (also 1524).
+
+ Later or baroque old style type (17th Century) generally has more
+ contrast, with a somewhat variable axis, and more slope of italic. The
+ most common examples are the types of Garamond and Caslon, many variant
+ revivals of which exist in digital form.
+
+ Transitional Type: Baskerville, Fournier
+ ----------------------------------------
+
+ "Transitional" type is so-called because of its intermediate position
+ between old style and modern. The distinguishing features of
+ transitional typefaces include vertical stress and slightly higher
+ contrast than old style typefaces, combined with horizontal serifs. The
+ most influential examples are Philippe Grandjean's "Romain du Roi" for
+ the French Crown around 1702, Pierre Simon Fournier's work circa 1750,
+ and John Baskerville's work from 1757 onwards. Although today we
+ remember Baskerville primarily for his typeface designs, in his own
+ time people were much more impressed by his printing, which used an
+ innovative glossy paper and wide margins.
+
+ Later transitional types begin to move towards "modern" designs.
+ Contrast is accentuated, and serifs are more flattened. Current
+ examples of such are based on originals from approximately 1788-1810,
+ and are dominated by British isles designers, such as Richard Austin
+ (Bell, 1788), William Martin (Bulmer) and Miller & Richard (Scotch
+ Roman).
+
+ For currently available examples of transitional type, there are many
+ types which bear Baskerville's name, descending from one or another of
+ his designs. Less common today is P.S. Fournier's work, although
+ several versions of it are available in digital or metal form. Although
+ Scotch Roman has been a very common face in metal type usage since
+ Monotype's 1920 revival, it is not a common digital face. Bell, on the
+ other hand, is included in a Microsoft Font Pack, and Bulmer has
+ received more attention since its revival by Monotype in late 1994.
+
+ Modern Type: Didot, Bodoni, Walbaum
+ -----------------------------------
+
+ "Modern" typefaces are distinguishable by their sudden-onset vertical
+ stress and strong contrast. Modern serifs and horizontals are very thin,
+ almost hairlines. Although they are very striking, these typefaces are
+ sometimes criticized as cold or harsh, and may not be quite as readable
+ for very extensive text work, such as books.
+
+ A number of designers, perhaps semi-independently, created the first
+ modern typefaces in the late 1700s and early 1800s. One of the first,
+ and ultimately the most influential, was Giambattista Bodoni, of Parma,
+ Italy. Ironically, historians of type often relate the development of
+ the "modern" letterforms to a then-current obsession with things
+ Roman--in this case the strong contrast and sharp serifs of classical
+ Roman inscriptions. Although similar interests
+
+ Today, the most common "modern" typefaces are the dozens of
+ reinterpretations of Bodoni's work (which itself evolved over time).
+ One of the most successful reinterpretations is the 1994 ITC Bodoni by
+ Stone et. al., featuring three different optical sizes. Although little
+ is seen of Didot, a reinterpretation by J.E. Walbaum (ca. 1800) sees
+ occasional use.
+
+ Sans Serif & Slab Serif
+ -----------------------
+
+ These type forms made their first appearances around 1815-1817. Both are
+ marked by simpler letterforms with (usually) relatively uniform stroke
+ weight, lacking significant contrast, often geometric in underlying
+ design.
+
+ The earliest forms of sans and slab typefaces tended to be heavy, often
+ monolithic, display faces, but there quickly evolved a wide range of
+ styles. Although the earliest designs are not much used today, their
+ descendants are common enough.
+
+ Sans Serif (a.k.a. Gothic or Grotesque)
+ .......................................
+
+ Sans serif letters have no serifs, as the name suggests. The low
+ contrast and absence of serifs makes most sans typefaces harder to
+ follow for general reading. They are fine for a sentence, passable for
+ a paragraph, but are difficult to use well in, say, the text of a book.
+ The terminology of sans serif types can be confusing: essentially,
+ gothic or grotesque are both generic names for sans serif (although
+ Letter Gothic, confusingly, is more of a slab serif type).
+
+ In sans serif faces, the italics are often, although not always, simply
+ a sloped (mechanically obliqued) version of the roman letters, making
+ them totally subordinate to the roman.
+
+ By far the most common sans is Helvetica (1951, Miedinger), despite
+ being abhorred by many typographers. Helvetica does have the advantage
+ of coming in a huge range of weights and widths, which makes it
+ versatile, and its ubiquitous character makes it easy to match. Other
+ general-purpose sans serifs include Univers (Frutiger, 1952+), Arial
+ (Monotype), Franklin Gothic (M.F. Benton, 1903) and Frutiger (Frutiger,
+ 1975).
+
+ Sprouting from the Art Deco movement in the 1920s and 30s (see Art
+ Deco), radical geometrical shapes began to be used as the basis for
+ sans serif designs.
+
+ There are a few other common sans faces which do not fall cleanly into
+ the above categories. Eric Gill's 1928 Gill Sans has an almost
+ architectural quality, and its greater contrast and humanistic design
+ makes it better-suited than most sans serif typefaces to setting bodies
+ of text. The same can perhaps be said of a number of late 20th Century
+ humanistic sans faces (see below)
+
+ Slab Serif (Egyptian)
+ .....................
+
+ These faces have block-like rectangular serifs, sticking out
+ horizontally or vertically, often the same thickness as the body
+ strokes. There is some debate about the origin of slab serif
+ typefaces: did they originate by somebody adding serifs to a sans face,
+ or were they conceived independently?
+
+ But even if they had a separate genesis as a family, it is certainly the
+ case that many of the most common and popular slab serif forms have been
+ created by adding slab serifs to sans faces by the same designer (e.g.
+ Adrian Frutiger's 1977 Glypha from his Univers, Herb Lubalin's 1974
+ Lubalin Graph from his Avant Garde). Other slab serif faces include
+ Berthold City (Trump, 1930), Memphis (Weiss, 1930), Serifa (Frutiger,
+ 1968) and Silica (Stone, 1990).
+
+ The Clarendons or Ionics are an offspring of the slab serif typefaces in
+ which the serifs are bracketed. These are often used in newspaper work,
+ because their sturdy serifs hold up well under adverse printing
+ conditions. The most famous member of this sub-family is Century
+ Schoolbook (M.F. Benton, 1924-35).
+
+ Decorative & Display Type
+ -------------------------
+
+ Fat Faces
+ .........
+
+ The "Fat Face" types were an offshoot of the moderns, intended for
+ display purposes (that is, to be attention-getting for use in large
+ sizes, particularly advertising). The first such types appeared from
+ 1810-1820. They further exaggerated the contrast of modern typefaces,
+ with slab-like vertical lines and extra emphasis of any vertical
+ serifs, which often acquired a wedge shape. Bodoni Ultra, Normande and
+ Elephant are all examples of fat face types which are closely based on
+ early to mid-19th Century originals, and are available in digital form.
+
+ Wood Type
+ .........
+
+ Wood type answered some of the needs of display advertising during the
+ industrial revolution. It derives its name from the fact that instead of
+ being made of metal, the type is carved from wood, cut perpendicular to
+ the grain. It is distinguished by strong contrasts, an overall dark
+ color, and a lack of fine lines. It may be unusually compressed or
+ extended. Many wood types have an "Old West" feel, because they are most
+ strongly associated with America in the 1870-1900 period. Some of the
+ wood types most widely available today are those in an Adobe pantheon
+ released in 1990, which includes Cottonwood, Ironwood and Juniper
+ (Buker, Lind & Redick).
+
+ Script, Brush, Italic & Freehand
+ ................................
+
+ Script typefaces are based on handwriting; but often this is handwriting
+ with either a flexible steel nib pen, or a broad-edged pen, and is thus
+ unlike modern handwriting.
+
+ Some common scripts based on steel nib styles include Shelley (Carter,
+ 1972), Coronet (Middleton, 1937-38), and Snell Roundhand (Carter, 1965,
+ based on Snell ca. 1694).
+
+ Script faces based more on the broad-edged tradition include the
+ contemporary Park Avenue (Smith, 1933).
+
+ There are also monoline scripts, which lack significant contrast in the
+ letter strokes. One such is Freestyle Script.
+
+ Brush typefaces look as if they were drawn with that instrument, which
+ most of them were, at least in the original design from which the
+ metal/film/digital face was created. Some of them resemble sign-painting
+ lettering, such as Balloon (Kaufmann, 1939), Brush Script (Smith,
+ 1942), and Dom Casual (Dom, 1952).
+
+ Brushwork can also be the basis for script, as with Present Script
+ (Sallaway, 1974) and Mistral (Excoffon, 1953)
+
+ Although modern typography typically relegates the italic to a second-
+ class citizenship subordinate to the roman, there are still some italic
+ typefaces designed as such in their own right. The best known is
+ doubtless Zapf Chancery (Zapf, 1979). Others include Medici Script
+ (Zapf, 1974) and Poetica (Slimbach, 1992).
+
+ Art Nouveau
+ ...........
+
+ The late Victorian era, from 1880 to World War I, was characterized by
+ this ornamental style of art, with its organic, asymmetrical, intricate
+ and flowing lines. This "Art Nouveau" (French, meaning "new art")
+ produced similarly distinctive typography, which saw a revival during
+ the 1960s.
+
+ There are a fair number of digital revivals of art nouveau faces,
+ although few are widely used. Some of the more common digital art
+ nouveau typefaces are Arnold Boecklin (Weisert, 1904), Artistik,
+ Desdemona, Galadriel and Victorian.
+
+ Art Deco
+ ........
+
+ If Art Nouveau was about finding beauty in organic intricacy, Art Deco
+ was perhaps about finding beauty in geometric simplicity. First
+ appearing in the 1920s and 30s, Art Deco made a comeback in the 1970s
+ and 80s as well.
+
+ Almost by definition, Art Deco meant sans serif type. The most common
+ such face is Avant Garde (1974, Lubalin), which is striking but hard to
+ read at length. A more graceful geometric sans is Futura (Renner,
+ 1927-39). There are also more quirky faces in this category, such as
+ Kabel (Koch, 1927-30). A recent popular Art Deco display face is ITC
+ Anna (1991?).
+
+ Synthesis
+ ---------
+
+ Many of the most interesting typefaces of the twentieth century does not
+ fit any of the above categories, or at least not easily. The reason is
+ that they reflect not merely a single style, but cumulative experience,
+ and the merger of different styles. This is perhaps true even of that
+ most mundane of typefaces, Times New Roman (Lardent/Morison, 1931),
+ which has old style, transitional and modern elements.
+
+ Synthesis and Serif Type
+ ........................
+
+ Although there are many practitioners of this synthesis, the most famous
+ is Hermann Zapf. His Palatino (1948) and Zapf Renaissance (1987) are
+ modern typefaces with the spirit of Renaissance letterforms. Melior
+ (1952), Zapf Book (1976), and Zapf International (1977) all reflect an
+ obsession with the super-ellipse, a rectangulated circle, as the basis
+ for letter shapes.
+
+ There have also been many modern revivals of old style which, while
+ close to old style in spirit, are not direct revivals of a specific
+ original, and show modern influences in the proportions or
+ lettershapes. These include the Granjon-inspired Galliard (Carter, 1978)
+ and Minion (Slimbach, 1989).
+
+ Synthesis and Sans Serif Type
+ .............................
+
+ After 1950, many designers began to explore a wide range of starting
+ points as the basis for sans serif designs. Aldo Novarese's Eurostile
+ (1964-5) takes sans serif forms and distorts them towards square and
+ rectangular shapes. Zapf's 1958 Optima is a masterful blend of sans
+ serif shapes with Roman and calligraphic influences. Shannon (Holmes &
+ Prescott Fishman, 1981) is a sans serif based on celtic manuscript
+ proportions. Several designers have reinterpreted ancient Greek
+ lettering for a modern sans serif alphabet: most popularly Carol
+ Twombly's Lithos (1989), and most recently Matthew Carter's Skia GX
+ (1994). Koch's Neuland (1930?) has a rough-hewn strength. Hans Eduard
+ Meier's Syntax (1969) is one of the earliest sans typefaces which
+ clearly echo renaissance roman letterforms. More recent sans faces
+ often draw on a humanistic background, from Spiekerman's Meta to
+ Vereschagin's Clear Prairie Dawn.
+
+ "Grunge" Typography
+ ...................
+
+ The most recent typographic wave is one which has sometimes been called
+ grunge typography, after the musical movement originating in Seattle.
+ Although it is far too early to judge the ultimate impact of grunge, I
+ see the form as the merger of the industrial functionalist movement
+ called Bauhaus (contemporary with Art Deco, named after the
+ architectural school) with the wild, nihilistic absurdism of Dadaism.
+ Grunge, like many typographic/artistic movements before it, is a
+ rebellion; but this rebellion denies not only the relevance of anything
+ previous, but sometimes even the relevance of legibility itself, in the
+ belief that the medium *is* the message.
+
+ As grunge type designer Carlos Segura of T-26 says, "Typography is
+ beyond letters. Some fonts are so decorative, they almost become
+ 'visuals' and when put in text form, they tell a story beyond the
+ words-a canvas is created by the personality of the collection of words
+ on the page."
+
+ Grunge typefaces and typography are seen in magazines such as RayGun.
+ Some examples of grunge typography are the work of Barry Deck (Template
+ Gothic, Cyberotica, Truth), Nguyen's Droplet, Goren's Morire and Lin's
+ Tema Cantante.
+
+ Sources
+ =======
+
+ Published Sources:
+ ------------------
+
+ Although much of this information is based on prior knowledge, I also
+ actively consulted the following publications:
+
+ Bauermeister, Benjamin. A Manual of Comparative Typography. Van
+ Nostrand Reinhold Co., New York, NY: 1988. ISBN 0-442-21187-2.
+
+ Bringhurst, Robert. The Elements of Typographic Style. Hartley &
+ Marks, Vancouver, BC: 1992. ISBN 0-88179-033-8. The modern classic in
+ the field.
+
+ Byers, Steve. The Electronic Type Catalog. Bantam Books, New York:
+ 1991. ISBN 0-553-35446-9.
+
+ Eisenstein, Elizabeth L. The Printing Press as an Agent of Change.
+ Cambridge University Press, New York: 1979. ISBN 0-521-29955-1.
+
+ Harper, Laurel. "Thirstype: Quenching a Type Craving" in How: the
+ Bottomline Design Magazine, vol. 10, #1, Jan-Feb 1995. Although not
+ usually a thrilling magazine, had several pieces on typography in this
+ issue (see Segura, below).
+
+ Letraset Canada Limited. Letraset Product Manual. Letraset, Markham,
+ Ontario, Canada: 1985.
+
+ Meggs, Philip B. "American Type Founders Specimen Book & Catalog 1923"
+ in Print Magazine, vol. 48 #1, Jan-Feb 1994. Contains some interesting
+ info on the effects of industrialization on the type industry.
+
+ Sutton, James & Bartram, Alan. An Atlas of Typeforms. Percy, Lund,
+ Humphries & Co., Hertfordshire, UK: 1968. ISBN 1-85326-911-5.
+
+ Morison, Stanley & Day, Kenneth. The Typographic Book: 1450-1935.
+ University of Chicago Press, Chicago: 1963.
+
+ Segura, Carlos & Nelson, Lycette. "Typography in Context: Never Take a
+ Font at Face Value" in How: the Bottomline Design Magazine, vol. 10,
+ #1, Jan-Feb 1995.
+
+ Tracy, Walter. Letters of Credit: a View of Type Design. David R.
+ Godine Co.: 1986.
+
+ Updike, Daniel Berkeley. Printing Types: Their History, Forms & Use.
+ Harvard Press: 1962.
+
+ Zapf, Hermann. "The Expression of Our Time in Typography" in Heritage
+ of the Graphic Arts. R.R. Bowker Company, New York: 1972. ISBN
+ 0-8352-0213-5.
+
+ Personal Contributions:
+ -----------------------
+
+ In addition to written sources, which are identified above, I would like
+ to thank the following for their helpful comments and corrections (any
+ errors are, of course, my responsibility): Robert Hemenway, Mary Jo
+ Kostya, and Dan Margulis
+
+ ---------- Footnotes ----------
+
+ (1) Version 1.02 14 Apr 1995
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 1.28. The Role of National Orthography in Font Design
+
+ This article was constructed from postings by Anders Thulin, Charles A.
+ Bigelow, and "fieseler" from Jan 1994.
+
+ An open question: what role does national orthography play in the
+ asthetics of a given font?
+
+ Given that uppercase letters occur more frequently in German than in
+ English, are German font designs better for typesetting German (because
+ the designer is more concious of the relationship between capitals and
+ lowercase)? Similarly, are French designs better for typesetting French
+ because the designer is more atuned to the appearance of accents?
+
+ Speaking of accents, there are apparently fonts in which the dots over
+ the "i" and "j" are not at the same height as the dieresis over
+ accented vowels. (Does anyone have an example of this?) Surely this is
+ an error that a designer accustomed to working with accented letters is
+ unlikely to make?
+
+Subject: 1.29. Interesting Fonts
+
+ There's no end of interesting fonts, so this is really just a catch-all
+ category.
+
+ Highway Gothic
+ ==============
+
+ Kibo (James Parry) provides the following discussion of Highway Gothic:
+
+ Highway Gothic is The Font Company's name for their interpretation of
+ the font used on most official road signs in the United States. (The
+ Font Company added a lowercase to most styles.)
+
+ I don't think it has an official name. There is a government
+ publication which shows the fonts (revised in the seventies to make the
+ heights metric); I got a copy of it once, from a library specializing in
+ transportation, and digitized Series E(M) (normal-width bold caps with
+ lowercase, the only USDOT font with lowercase) for a special project. I
+ don't think the specs have changed since the seventies.
+
+ Besides E(M) with lowercase, there is a slightly lighter alphabet
+ without lowercase, and three condensed styles. I recall there was also
+ a set of really distorted letters for use in painting vehicle lanes,
+ plus a few symbols for bike paths etc. The alphabets included letters
+ and digits only--any periods or hyphens you see on signs are apparently
+ unofficial.
+
+ Where can I get extravagant initial caps?
+ =========================================
+
+ Don Hosek writes:
+
+ I doubt that most decorated initials can be made to work in the type 1
+ format because of their complexity. Color only makes things worse.
+
+ One of the best choices for medieval and renaissance decorated alphabets
+ hasn't been mentioned yet: BBL Typographic (they have an ad on p. 39 of
+ Serif 1). A demo disk is available for \$10, B&W alphabets are \$50 each
+ and full color alphabets are \$60.
+
+ BBL Typographic
+ 137 Narrow Neck Road
+ Katoomba, NSW 2780
+ AUSTRALIA
+ 011-61-47-826111
+ 011-61-47-826144 FAX
+
+ also distributed by:
+
+ Medieval & Renaissance Texts & Studies
+ LN G99
+ State University of New York
+ Birmingham, NY 13902-6000
+
+ I know the work only from the Serif ad, but it's gorgeous there (even
+ nicer in color, although they decided not to spend the extra money for
+ color in their ad... only a select few in Katoomba & Claremont have seen
+ the ad in full color). Of course Serif-related disclaimers apply.
+
+ Jon Pastor contributes:
+
+ Check out the Aridi initials, color EPS initials, available on the
+ Monotype CD (and, presumably, on the Adobe CD as well, although they
+ don't advertise this; Monotype did, in a recent mailing).
+
+ To which Don Hosek amends:
+
+ The Aridi initials are part of the Type Designers of the World
+ collection and are available on the MT CD but not the Adobe CD. Adobe
+ has their own line of decorated initials available on their CD. Also
+ see the catalogs from FontHaus, FontShop and Precision Type.
+
+ If you want something really unique, why not hire a calligrapher. It
+ may be cheaper than you think.
+
+ Robert Green adds:
+
+ Although they might not be on the Adobe CD, the Fall 1994 Font &
+ Function advertises an Adobe "Initial Caps" collection of decorative
+ initial caps designed by Marwan Aridi.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(5_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(5_6)
new file mode 100644
index 0000000000..6cfb952e80
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(5_6)
@@ -0,0 +1,1421 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (5/6)
+Supersedes: <font-faq-5_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:33 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 1398
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-5_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48302 comp.answers:20516 news.answers:79237
+
+Archive-name: fonts-faq/part5
+Version: 2.1.5
+
+Subject: 1.30. Pronounciation of Font Names
+
+ Below each of the following font names, a suggested English
+ pronounciation is given. This information was collected from a
+ (relatively) long discussion on comp.fonts. If you disagree, or have
+ other suggestions, please let me know.
+
+ Arnold Boecklin
+ ===============
+
+ "Ar" as in car, "nold" as in "old" with an "n" on the front. "Boeck"
+ is tricker. The "oe" is actually an umlaut "o" in German, and the
+ closest sound to most English speakers is an "er". So try "Berklin" if
+ you want to come close to the original. Otherwise, just say "Boklin",
+ with a long o, like in "boat".
+
+ Benguiat
+ ========
+
+ Ben-Gat. This according to an ITC brochure.
+
+ Courier
+ =======
+
+ I would pronounce Courier not like Jim Courier, but the French way:
+ Ku-rie, where "Ku" is pronounced like "coo", only short, and "rie" is
+ pronounced "ree-eh".
+
+ Didot
+ =====
+
+ Stressed at the last syllable. "Dee-DOOH" (not nasal).
+
+ Fette Fraktur
+ =============
+
+ "Fet" as in "get" with a "te" that rhymes with "way". "Frak" rhymes
+ with "mock", and "tur" with "tour".
+
+ Fenice
+ ======
+
+ Feh-nee'-chey
+
+ Garamond
+ ========
+
+ "Gara-": Use a french "r" instead of an english one. Both "a"s are
+ pronounced like the "u" in the word "up". "-mond": the last syllable is
+ stressed, and you don't pronounce the "n" and "d", but the whole "ond"
+ is a nasal "o". Hold your nose closed and say "Ooh", then you get the
+ right sound. The "ant" in "Avant-Garde" is very similar to this sound,
+ it is a nasal situated between "a" and "o".
+
+ Helvetica
+ =========
+
+ Hell-veh'-ti-ka
+
+ Koch Roman
+ ==========
+
+ Pronounced like scottish `Loch', but with K instead of L.
+
+ LaTeX
+ =====
+
+ Lamport lists lah'-tech, lah-tech', lay'-tech and lay'-tecks as valid
+ on p.4. Last I talked to him he'd settled into lay'-tech which has
+ always been my pronunciation as well. Somewhere, I heard that LL does
+ explicitly rule out L.A.-tech, but he's from northern California which
+ explains a lot.
+
+ Mos Eisley
+ ==========
+
+ moss eyes-lee
+
+ Novarese
+ ========
+
+ No-vahr-ay'-zay
+
+ Palatino
+ ========
+
+ pa-la-TEEN-oh
+
+ Peignot
+ =======
+
+ There's some contention here, suggested pronouncations:
+
+ pay-nyoh'
+
+ "P" like "P" in `Post", "ei" like "a" in "fan", "gn" like "n" in "noon"
+ plus "y" in "yes", "ot" - long, closed "o" (I don't know English
+ examples), stressed.
+
+ "P" like "P" in `Post", "ei" like "a" in "many", "gn" like "n" in
+ "noon" plus "y" in "yes", "ot" - long, closed "o" (I don't know English
+ examples), stressed.
+
+ Sabon
+ =====
+
+ Sah-bon'
+
+ TeX
+ ===
+
+ Rhymes with Blech, (as in "Blech, that tasted awfull!")
+
+ Veljovic
+ ========
+
+ Vel'-yo-vitch
+
+ Zapf
+ ====
+
+ Like "tsapf". The "a" is pronounced like a short version of the well
+ known tongue-depresser vowel "aaahhh". Perhaps a better English analogy
+ would be the "o" in "hop" or "hops".
+
+Subject: 1.31. What is it?
+
+ This section identifies common names for several glyphs.
+
+ The "@" Character
+ =================
+
+ The "at" sign or "commercial at" sign. In the past, it has also meant
+ "each" or "each at". Consider the following example supplied by Clive
+ Burton:
+
+ Unit Extended
+ Qnty Unit Item Price Price
+ 12 reams bond paper @ 5.50 66.00
+
+ Here' "@" means each at or simply each.
+
+ PostScript calls this the "at" sign.
+
+ The "#" Character
+ =================
+
+ This mark has several common names: 'hash', 'hatch', 'pound sign', and
+ 'octothorp' among them. The name "pound sign" is an Americanism that
+ causes some confusion in countries that use the pound for currency.
+
+ It was also noted that the # is a medieval abbreviation for Latin
+ "numerus" - it is a cursive 'n' with a horizontal slash through it,
+ much modified and abstracted.
+
+ One possible derivation of the name "octothorp" was provided by Charles
+ Bigelow:
+
+ ... old English "thorp" meant 'hamlet' or 'village' (I'm not sure
+ of the difference, except maybe hamlet is smaller, as its apparent
+ diminutive suffix would suggest), and is derived from a much older
+ Indo-European word *treb- for 'dwelling', which turns out to mean
+ 'beam' or 'timber' in Latin "trabs", winding up as "trave" in
+ Anglo-Latin, like "architrave" - the beam resting on a column, or
+ "trab-" as in "trabecula" - a small supporting beam or bar. As
+ Voltaire said, etymology is a science in which the vowels count
+ for nothing and the consonants for very little.
+
+ So, maybe "octothorp" means "8-beams", which makes a kind of sense
+ if we take the 8 projections to be the thorps, or trabs or traves.
+ Though it's only a "quadrathorp" if we think that the beams
+ connect.
+
+ Another explanation has it that the octothorp is a "thorp" surrounded
+ by eight cultivated fields.
+
+ Both of these etymologies received some skepticism amongst the readers
+ who commented on comp.fonts.
+
+ PostScript calls this the "numbersign".
+
+Subject: 1.32. Equivalent Font Names
+
+ Morgan S. Brilliant, Jon Pastor, and Frank F. Smith have each
+ contributed to the following list of equivalent font names.
+
+ The following table shows trade/common names and the equivalent names
+ used by other vendors. The vendor or trademark holder's name is shown
+ in parenthesis following each typeface name.
+
+ Aachen Bold (Letraset)
+ Aardvark (Corel)
+
+ Activa (Bitstream, Inc.)
+ Kuenstler 480
+
+ Ad Lib
+ Adelaide (Corel)
+
+ Adsans (Linotype AG and/or its subsidiaries)
+ Humanist 970
+
+ Akzidenz Grotesk (H. Berthold AG)
+ Gothic 725
+
+ Albertus (Monotype Corporation plc)
+ Flareserif 821
+
+ Aldine 401 (Monotype Corporation plc)
+ Bembo
+
+ Aldine 721 (Monotype Corporation plc)
+ Plantin
+
+ Algerian (S. Blake)
+ Algiers (Corel)
+
+ Allegro
+ Alto (Corel)
+
+ Amelia (VGC)
+ Amy (Corel)
+
+ Americana (ATF)
+ Amherst (Corel)
+
+ Antique Olive (Fonderie Olive)
+ Incised 901
+
+ Arnold Bocklin
+ Arabia (Corel)
+
+ Arquitectura (IC)
+ Architecture (Corel)
+
+ Avant Garde (ITC)
+ Avalon (Corel)
+
+ Badloc (IC)
+ Bedrock (Corel)
+
+ Balloon (ATF)
+ Bassoon (Corel)
+
+ Bamboo (ATF)
+ Bard (Corel)
+
+ Bauhaus (ITC)
+ Bahamas (Corel)
+
+ Bauhaus Heavy (ITC)
+ BahamasHeavy (Corel)
+
+ Bauhaus Light (ITC)
+ BahamasLight (Corel)
+
+ BeeBopp (IC)
+ Beehive (Corel)
+
+ Bembo (Monotype Corporation plc)
+ Aldine 401
+
+ Benguit (ITC)
+ Bangkok (Corel)
+
+ Bernhard Tango (VGC)
+ BallroomTango (Corel)
+
+ Bisque (VGC)
+ Brisk (Corel)
+
+ Bitstream Arrust Black BT (Bitstream)
+ Bitstream Arrus Black BT (WordPerfect)
+
+ Block (H. Berthold AG)
+ Gothic 821
+
+ Bodoni Campanile (Ludlow Industries (UK) Ltd.)
+ Modern 735
+
+ Bodoni Poster
+ Bodnoff (Corel)
+
+ Book Jacket (VGC)
+ Brochure (Corel)
+
+ Bookman (ITC)
+ Brooklyn (Corel)
+
+ Broadway (ATF)
+ Bravo (Corel)
+
+ Broadway Engraved (ATF)
+ BravoEngraved (Corel)
+
+ Brody (ATF)
+ Briquet (Corel)
+
+ Brush 445 (H. Berthold AG)
+ Palette
+
+ Brush 738
+ Bison
+
+ Brush Script (ATF)
+ Banff (Corel)
+
+ Busorama (ITC)
+ Bosanova (Corel)
+
+ Buster (Letraset)
+ Busker (Corel)
+
+ Cable (Linotype AG and/or its subsidiaries)
+ Geometric 231
+
+ Calligraphic 421 (Linotype AG and/or its subsidiaries)
+ Codex
+
+ Calligraphic 810 (Linotype AG and/or its subsidiaries)
+ Diotima
+
+ Carolus Roman
+ Carleton (Corel)
+
+ Carta (Adobe)
+ GeographicSymbols (Corel)
+
+ Cartoon
+ Cancun (Corel)
+
+ Cascade (Linotype AG and/or its subsidiaries)
+ Freehand 471
+
+ Cascade Script (Adobe)
+ Castanet (Corel)
+
+ Casino (IC)
+ Carino (Corel)
+
+ Caslon (ATF)
+ Casablanca (Corel)
+
+ Caslon Antique (ATF)
+ CasablancaAntique (Corel)
+
+ Caslon Open Face
+ CasperOpenFace (Corel)
+
+ Caslon Openfacce (Bitstream)
+ Caslon Openface (WordPerfect)
+
+ Centaur (Monotype Corporation plc)
+ Venetian 301
+
+ Century Old Style
+ CenturionOld (Corel)
+
+ Champagne (IC)
+ Campaign (Corel)
+
+ Charlemagne (Adobe)
+ Charlesworth (Corel)
+
+ Choc (Letraset)
+ Chalk (Corel)
+
+ Choc (Fonderie Olive)
+ Staccato 555
+
+ City (H. Berthold AG)
+ Square Slabserif 711
+
+ Codex (Linotype AG and/or its subsidiaries)
+ Calligraphic 421
+
+ Comic Book (IC)
+ Cosmic (Corel)
+
+ Comic Book Two (IC)
+ CosmicTwo (Corel)
+
+ Cooper Black
+ Cupertino (Corel)
+
+ CopperPlate Gothic (VGC)
+ CopperPot (Corel)
+
+ Coronet (Ludlow Industries (UK) Ltd.)
+ Ribbon 131
+
+ Cottonwood (Adobe)
+ Cottage (Corel)
+
+ Croissant (Letraset)
+ Crescent (Corel)
+
+ Decorative 035 (Tetterode Nederland (Lettergieterij Amsterdam))
+ Profil
+
+ Delphin
+ Dauphin (Corel)
+
+ Diotima (Linotype AG and/or its subsidiaries)
+ Calligraphic 810
+
+ Dom Casual
+ DawnCastle (Corel)
+
+ Dutch 801 (Linotype AG and/or its subsidiaries)
+ Times Roman
+
+ Dutch 801 (Montype Corporation plc)
+ Times Roman
+
+ Electra (Linotype AG and/or its subsidiaries)
+ Transitional 521
+
+ Elektrik (VGC)
+ Eklektic (Corel)
+
+ Englische Screibschrift (H. Berthold AG)
+ English 157
+
+ English 157 (H. Berthold AG)
+ Englische Screibschrift
+
+ Enviro (Letraset)
+ Envision (Corel)
+
+ Eras (ITC)
+ Erie (Corel)
+
+ Eras Black (ITC)
+ ErieBlack (Corel)
+
+ Eras Contour (ITC)
+ ErieContour (Corel)
+
+ Eras Light (ITC)
+ ErieLight (Corel)
+
+ Estro (ATF)
+ Expo (Corel)
+
+ Eurostile (Adobe)
+ Euromode (Corel)
+
+ Eurostile (Linotype AG and/or its subsidiaries)
+ Square 721
+
+ Exotic 350 (Linotype AG and/or its subsidiaries)
+ Peignot
+
+ Fairfield (Linotype AG and/or its subsidiaries)
+ Transitional 551
+
+ Fette Fraktur (ITC)
+ Frankenstein (Corel)
+
+ Firenze (ITC)
+ Florence (Corel)
+
+ Flareserif 821 (Monotype Corporation plc)
+ Albertus
+
+ Formal Script 421 (Bitstream, Inc.)
+ Mermaid
+
+ Formal Script 421 (Linotype AG and/or its subsidiaries)
+ Ondine
+
+ Franfurt (TFCo)
+ FrankHighlight (Corel)
+
+ Frankfurt (TFCo)
+ FrankHighlight (Corel)
+
+ Franklin Gothic (ITC)
+ FrankfurtGothhic (Corel)
+
+ Franklin Gothic Heav (ITC)
+ FrankfurtGothicHeavy (Corel)
+
+ Freehand 471 (Linotype AG and/or its subsidiaries)
+ Cascade
+
+ Freehand 521 (Ludlow Industries (UK) Ltd.)
+ Mandate
+
+ Freehand 575
+ Jefferson
+
+ Freehand 591
+ Bingham Script
+
+ Freestyle Script (Letraset)
+ Freeport (Corel)
+
+ Fritz Quadrata (ITC)
+ France (Corel)
+
+ Frutiger (Linotype AG and/or its subsidiaries)
+ Humanist 777
+
+ Futura 2 (FTNSA)
+ Fujiyama2 (Corel)
+
+ Futura Black (Bauer)
+ FujiyamaBlack (Corel)
+
+ Futura Cnd Extra Bol (FTNSA)
+ FujiyamaExtraBold (Corel)
+
+ Futura Cnd Extra Bold (FTNSA)
+ FujiyamaExtraBold (Corel)
+
+ Futura Cnd Light (FTNSA)
+ FujiyamaLight (Corel)
+
+ Futura Condensed (FTNSA)
+ Fujiyama (Corel)
+
+ Gallia
+ Galleria (Corel)
+
+ Garamond (ITC)
+ Gatineau (Corel)
+
+ Garamond, American
+ Garamond No. 3
+
+ Garamond, Classic (Linotype AG and/or its subsidiaries)
+ Sabon
+
+ Garamond, Elegant (Linotype AG and/or its subsidiaries)
+ Granjon
+
+ Garamond, Italian (Officine Simoncini s.p.a.)
+ Simoncini Garamond
+
+ Garamond, Original (Linotype AG and/or its subsidiaries)
+ Stempel Garamond
+
+ Geometric 231 (Linotype AG and/or its subsidiaries)
+ Cable
+
+ Geometric 415 (Linotype AG and/or its subsidiaries)
+ Metro
+
+ Geometric 706 (Linotype AG and/or its subsidiaries)
+ Neuzeit Grotesk
+
+ Geometric SlabSerif 703 Light (Bitstream)
+ GeometricSlabSerif703Light (WordPerfect)
+
+ Geometric Slabserif 703 (Linotype AG and/or its subsidiaries)
+ Memphis
+
+ Geometric Slabserif 712 (Monotype Corporation plc)
+ Rockwell
+
+ Geometric Slabserif 712 (Bitstream, Inc.)
+ Slate
+
+ Gill Sans (Monotype Corporation plc)
+ Humanist 521
+
+ Gill Sans Ultra Bold (Monotype)
+ GillbertUltraBold (Corel)
+
+ Glasnost (C&G)
+ Czar (Corel)
+
+ Glyphic Series (VGC)
+ Glacier (Corel)
+
+ Gold Rush (ATF)
+ GoldMine (Corel)
+
+ Gothic 725 (H. Berthold AG)
+ Akzidenz Grotesk
+
+ Gothic 821 (H. Berthold AG)
+ Block
+
+ Goudy Old Style
+ GoldenOldStyle (Corel)
+
+ Granjon (Linotype AG and/or its subsidiaries)
+ Garamond, Elegant
+
+ Graphik (IC)
+ Griffon (Corel)
+
+ Graphik Shadow (IC)
+ GriffonShadow (Corel)
+
+ Hairpin (VGC)
+ Harpoon (Corel)
+
+ Hammersmith (Bitstream, Inc.)
+ Humanist 521
+
+ Hanseatic (Linotype AG and/or its subsidiaries)
+ Swiss 924
+
+ Harlow (Letraset)
+ Hollow (Corel)
+
+ Hebrew (Letraset)
+ Alefbet (Corel)
+
+ Helv. Cnd. Black (Linotype)
+ SwitzerlandCondBlack (Corel)
+
+ Helv. Cond. Light (Linotype)
+ SwitzerlandCondLight (Corel)
+
+ Helvetica
+ Arial (Microsoft)
+
+ Helvetica (Linotype AG and/or its subsidiaries)
+ Swiss 721
+
+ Helvetica (Linotype)
+ Switzerland (Corel)
+
+ Helvetica Black (Linotype)
+ SwitzerlandBlack (Corel)
+
+ Helvetica Condensed (Linotype)
+ SwitzerlandCond (Corel)
+
+ Helvetica Inserat (Linotype)
+ SwitzerlandInserat (Corel)
+
+ Helvetica Light (Linotype)
+ SwitzerlandLight (Corel)
+
+ Helvetica Narrow (Linotype)
+ SwitzerlandNarrow (Corel)
+
+ Hobo
+ HomewardBound (Corel)
+
+ Honda (ITC)
+ Heidelberg (Corel)
+
+ Humanist 521 (Monotype Corporation plc)
+ Gill Sans
+
+ Humanist 521 (Bitstream, Inc.)
+ Hammersmith
+
+ Humanist 777 (Linotype AG and/or its subsidiaries)
+ Frutiger
+
+ Humanist 970 (Linotype AG and/or its subsidiaries)
+ Adsans
+
+ Incised 901 (Fonderie Olive)
+ Antique Olive
+
+ Incised 901 (Bitstream, Inc.)
+ Provence
+
+ Industrial 736 (Societea Nebiolo)
+ Torino
+
+ Informal 011 (Linotype AG and/or its subsidiaries)
+ Neuland
+
+ Ionic No. 5 (Linotype AG and/or its subsidiaries)
+ News 701
+
+ Ironwood (Adobe)
+ Ireland (Corel)
+
+ Juniper (Adobe)
+ Jupiter (Corel)
+
+ Kabel Bold
+ KabanaBold (Corel)
+
+ Kabel Book (ITC)
+ KabanaBook (Corel)
+
+ Kaufmann (Kingsley/ATF)
+ Koala (Corel)
+
+ Korinna (ITC)
+ Korinthia (Corel)
+
+ Kuenstler 480 (Bitstream, Inc.)
+ Activa
+
+ Kuenstler 480 (Linotype AG and/or its subsidiaries)
+ Trump Medieval
+
+ Kunstler Script (Linotype)
+ Kastler (Corel)
+
+ L.C.D. (Letraset)
+ LiquidCrystal (Corel)
+
+ Lapidary 333 (Monotype Corporation plc)
+ Perpetua
+
+ Letter Gothic
+ Monospaced (Corel)
+
+ Linoscript (Linotype)
+ Linus (Corel)
+
+ Linotext (Linotype)
+ Lincoln (Corel)
+
+ Lithos (Adobe)
+ Lithograph (Corel)
+
+ Lithos Light (Adobe)
+ LithographLight (Corel)
+
+ Machine (ITC)
+ Motor (Corel)
+
+ Mandate (Ludlow Industries (UK) Ltd.)
+ Freehand 521
+
+ Melior (Linotype AG and/or its subsidiaries)
+ Zapf Elliptical 711
+
+ Memphis (Linotype AG and/or its subsidiaries)
+ Geometric Slabserif 703
+
+ Mermaid (Bitstream, Inc.)
+ Formal Script 421
+
+ Mermaid (Bitstream)
+ Merlin (Corel)
+
+ Metro (Linotype AG and/or its subsidiaries)
+ Geometric 415
+
+ Micr (IC)
+ Keypunch (Corel)
+
+ Mistral (M.Olive)
+ Mystical (Corel)
+
+ Mistral (Fonderie Olive)
+ Staccato 222
+
+ Modern 735 (Ludlow Industries (UK) Ltd.)
+ Bodoni Campanile
+
+ Monospace 821
+ Helvetica Monospaced
+
+ Neuland (Linotype AG and/or its subsidiaries)
+ Informal 011
+
+ Neuland
+ Newfoundland (Corel)
+
+ Neuzeit Grotesk (Linotype AG and/or its subsidiaries)
+ Geometric 706
+
+ New Baskerville (ITC)
+ Nebraska (Corel)
+
+ New Century Schoolbo
+ NewBrunswick (Corel)
+
+ New Century Schoolbook
+ NewBrunswick (Corel)
+
+ New Yorker (IC)
+ NewOrder (Corel)
+
+ New Yorker Engraved (IC)
+ NewOrderEngraved
+
+ News 701 (Linotype AG and/or its subsidiaries)
+ Ionic No. 5
+
+ Nuptial Script
+ Nuance (Corel)
+
+ Ondine (Linotype AG and/or its subsidiaries)
+ Formal Script 421
+
+ Optima (Linotype)
+ Ottawa (Corel)
+
+ Optima (Linotype AG and/or its subsidiaries)
+ Zapf Humanist 601
+
+ P.T.Barnum (Bitstream)
+ BigTop (Corel)
+
+ Paintbrush (IC)
+ Palette (Corel)
+
+ Palatino (Linotype)
+ PalmSprings (Corel)
+
+ Palatino (Linotype AG and/or its subsidiaries)
+ Zapf Calligraphic
+
+ Palette (H. Berthold AG)
+ Brush 445
+
+ Paper Clip (VGC)
+ Pipeline (Corel)
+
+ Parisian (Kingsley/ATF)
+ Paragon (Corel)
+
+ Park Avenue (ATF)
+ Paradise (Corel)
+
+ Peignot (Linotype AG and/or its subsidiaries)
+ Exotic 350
+
+ Peignot (Linotype)
+ Penguin (Corel)
+
+ Peignot Light (Linotype)
+ PenguinLight (Corel)
+
+ Pepita (Monotype)
+ Pepper (Corel)
+
+ Perpetua (Monotype Corporation plc)
+ Lapidary 333
+
+ Plantin (Monotype Corporation plc)
+ Aldine 721
+
+ Plaza (Letraset)
+ Playwright (Corel)
+
+ Ponderosa (Adobe)
+ Posse (Corel)
+
+ Post Antiqua (H.Berthold AG)
+ ProseAntique (Corel)
+
+ Poster Bodoni
+ Bodoni-WP (WordPerfect)
+
+ Present Script (Linotype)
+ President (Corel)
+
+ Princetown (TFCo)
+ Indiana (Corel)
+
+ Princetown (TFCo)
+ IndianaSolid (Corel)
+
+ Profil (Tetterode Nederland (Lettergieterij Amsterdam))
+ Decorative 035
+
+ Provence (Bitstream, Inc.)
+ Incised 901
+
+ Pump Triline (Letraset)
+ PowerLine (Corel)
+
+ Quicksilver (D.Morris)
+ Quantum (Corel)
+
+ Revival 565
+ Berling
+
+ Revue (Letraset)
+ Renfrew (Corel)
+
+ Ribbon 131 (Ludlow Industries (UK) Ltd.)
+ Coronet
+
+ Rockwell (Monotype Corporation plc)
+ Geometric Slabserif 712
+
+ Sabon (Linotype AG and/or its subsidiaries)
+ Garamond, Classic
+
+ Simoncini Garamond (Officine Simoncini s.p.a.)
+ Garamond, Italian
+
+ Slate (Bitstream, Inc.)
+ Geometric Slabserif 712
+
+ Slogun (ZSoft)
+ Shogun (Corel)
+
+ Sonata (Adobe)
+ MusicalSymbols (Corel)
+
+ Souvenir (ITC)
+ Southern (Corel)
+
+ Square 721 (Linotype AG and/or its subsidiaries)
+ Eurostile
+
+ Square Slabserif 711 (H. Berthold AG)
+ City
+
+ Squire (M.Neugebauer)
+ Scribe (Corel)
+
+ Staccato 222 (Fonderie Olive)
+ Mistral
+
+ Staccato 555 (Fonderie Olive)
+ Choc
+
+ Stempel Garamond (Linotype AG and/or its subsidiaries)
+ Garamond, Original
+
+ Stencil
+ Stamp (Corel)
+
+ Stop (Nebiolo)
+ Scott (Corel)
+
+ Surf Style (ITC)
+ Surreal (Corel)
+
+ Swiss 721 (Linotype AG and/or its subsidiaries)
+ Helvetica
+
+ Swiss 911
+ Helvetica Compressed
+
+ Swiss 921
+ Helvetica Inserat
+
+ Swiss 924 (Linotype AG and/or its subsidiaries)
+ Hanseatic
+
+ Symbol (ITC)
+ GreekMathSYmbols (Corel)
+
+ Symbol (ITC)
+ GreekMathSymbols (Corel)
+
+ Tekton (Adobe)
+ Technical (Corel)
+
+ Thor (VGC)
+ Viking (Corel)
+
+ Thunderbird
+ ThunderBay (Corel)
+
+ Tiffany (ITC)
+ Timpani (Corel)
+
+ Tiffany Heavy (ITC)
+ TimpaniHeavy (Corel)
+
+ Time (Linotype)
+ Toronto (Corel)
+
+ Times Roman (Linotype AG and/or its subsidiaries)
+ Dutch 801
+
+ Times Roman (Monotype Corporation plc)
+ Dutch 801
+
+ Torino (Societea Nebiolo)
+ Industrial 736
+
+ Traffic (T.Hultgren)
+ Trafalgar (Corel)
+
+ Transitional 521 (Linotype AG and/or its subsidiaries)
+ Electra
+
+ Transitional 551 (Linotype AG and/or its subsidiaries)
+ Fairfield
+
+ Trump Medieval (Linotype AG and/or its subsidiaries)
+ Kuenstler 480
+
+ Umbra (Kingsley/ATF)
+ Umbrella (Corel)
+
+ Univers (Linotype AG and/or its subsidiaries)
+ Zurich
+
+ Univers Black (Linotype)
+ USABlack (Corel)
+
+ Univers Light (Linotype)
+ USALight (Corel)
+
+ University Roman (Letraset)
+ Unicorn (Corel)
+
+ Uptight (ITC)
+ Uptown (Corel)
+
+ VAG Rounded
+ Vogue (Corel)
+
+ Venetian 301 (Monotype Corporation plc)
+ Centaur
+
+ Vivaldi (VGC)
+ Vivienne (Corel)
+
+ Zapf Calligraphic (Linotype AG and/or its subsidiaries)
+ Palatino
+
+ Zapf Chancery (ITC)
+ ZurichCalligraphic (Corel)
+
+ Zapf Dingbats (ITC)
+ Dixieland (Corel)
+
+ Zapf Elliptical 711 (Linotype AG and/or its subsidiaries)
+ Melior
+
+ Zapf Humanist 601 (Linotype AG and/or its subsidiaries)
+ Optima
+
+ Zurich (Linotype AG and/or its subsidiaries)
+ Univers
+
+ Zurich (Linotype AG and/or its subsidiaries)
+ Univers
+
+ Some fonts are published by several vendors using the same name. This
+ table shows the typeface name and the vendors that supply it. Generally
+ this means that one vendor licensed the face from another.
+
+ Augsburger Initials
+ The Font Bureau, Inc., Microsoft
+
+ Baskerville Old Face
+ URW, Microsoft
+
+ Bell MT
+ Monotype, Microsoft
+
+ Bell MT Bold
+ Monotype, Microsoft
+
+ Bell MT Italic
+ Monotype, Microsoft
+
+ Bernhard Modern BT
+ Bitstream, WordPerfect
+
+ Bernhard Modern Bold BT
+ Bitstream, WordPerfect
+
+ Bernhard Modern Bold Italic BT
+ Bitstream, WordPerfect
+
+ Bernhard Modern Italic BT
+ Bitstream, WordPerfect
+
+ Bitstream Arrus BT
+ Bitstream, WordPerfect
+
+ Bitstream Arrus BT Bold
+ Bitstream, WordPerfect
+
+ Bitstream Arrus BT Bold Italic
+ Bitstream, WordPerfect
+
+ Bitstream Arrus BT Italic
+ Bitstream, WordPerfect
+
+ BitstreamArrus Black BT Italic
+ Bitstream, WordPerfect
+
+ Blackletter 686 BT
+ Bitstream, WordPerfect
+
+ Braggadocio
+ Monotype, Microsoft
+
+ BriemScript
+ Gunnlaugur SE Briem, Microsoft
+
+ Britannic Bold
+ URW, Microsoft
+
+ Brush 738 BT
+ Bitstream, WordPerfect
+
+ Castellar
+ Monotype, Microsoft
+
+ Centaur
+ Monotype, Microsoft
+
+ CommonBullets
+ Corel, Corel
+
+ Contemporary Brush
+ Filmotype, Microsoft
+
+ Contemporary Brush B
+ Filmotype, Microsoft
+
+ Desdemona
+ The Font Bureau, Inc., Microsoft
+
+ Eckmann
+ URW, Microsoft
+
+ Edda
+ The Font Bureau, Inc., Microsoft
+
+ Elephant
+ Carter & Cone Type Inc., Microsoft
+
+ Elephant Italic
+ Carter & Cone Type Inc., Microsoft
+
+ Engravers' Gothic BT
+ Bitstream, WordPerfect
+
+ Eurostile
+ URW, Microsoft
+
+ Eurostile Bold
+ URW, Microsoft
+
+ Futura Bold
+ URW, Microsoft
+
+ Futura Medium
+ URW, Microsoft
+
+ Futura Oblique
+ URW, Microsoft
+
+ GeometricSlabSerifLight Italic
+ Bitstream, WordPerfect
+
+ Gill Sans Ultra Bold
+ Monotype, Microsoft
+
+ Gradl
+ The Font Bureau, Inc., Microsoft
+
+ Harrington
+ The Font Bureau, Inc., Microsoft
+
+ Humanist 521 Condensed BT
+ Bitstream, WordPerfect
+
+ Humanist 521 Condensed Bold BT
+ Bitstream, WordPerfect
+
+ Humanist 521 Light BT
+ Bitstream, WordPerfect
+
+ Humanist 521 Light Italic BT
+ Bitstream, WordPerfect
+
+ Impact
+ Monotype, Microsoft
+
+ Keystroke
+ Corel, Corel
+
+ Kids
+ Corel, Corel
+
+ Memorandum
+ ITC, Corel
+
+ Mistral
+ URW, Microsoft
+
+ New Caledonia
+ Linotype-Hell AG, Microsoft
+
+ New Caledonia Bold
+ Linotype-Hell AG, Microsoft
+
+ New Caledonia Italic
+ Linotype-Hell AG, Microsoft
+
+ Old English Text MT
+ Monotype, Microsoft
+
+ Onyx
+ Monotype, Microsoft
+
+ Onyx BT
+ Bitstream, WordPerfect
+
+ OzHandicraft BT
+ Bitstream, WordPerfect
+
+ Parade
+ Filmotype, Microsoft
+
+ Peignot Medium
+ URW, Microsoft
+
+ Playbill
+ URW, Microsoft
+
+ Ransom
+ The Font Bureau, Inc., Microsoft
+
+ Ransom Bold
+ The Font Bureau, Inc., Microsoft
+
+ Ransom Bold Italic
+ The Font Bureau, Inc., Microsoft
+
+ Ransom Italic
+ The Font Bureau, Inc., Microsoft
+
+ Ribbon 131 BT
+ Bitstream, WordPerfect
+
+ Shelley Volante BT
+ Bitstream, WordPerfect
+
+ Stencil
+ URW, Microsoft
+
+ Stop
+ URW, Microsoft
+
+ Swiss 721 Black Extended BT
+ Bitstream, WordPerfect
+
+ Wide Latin
+ URW, Microsoft
+
+ Wingdings 2
+ Bigelow & Holmes, Inc., Microsoft
+
+ Wingdings 3
+ Bigelow & Holmes, Inc., Microsoft
+
+ The following table summarizes typeface names for which no equivalent
+ name is known. The vendor is listed for each font. Many of these
+ fonts are builtin to the HP LaserJet line of printers.
+
+ AdineKirnberg
+ shareware
+
+ Albertus Extra Bold
+ Hewlett-Packard
+
+ Albertus Medium
+ Hewlett-Packard
+
+ American-Uncial-Normal
+ shareware
+
+ Antique Olive
+ Hewlett-Packard
+
+ Antique Olive Bold
+ Hewlett-Packard
+
+ Antique Olive Italic
+ Hewlett-Packard
+
+ Broadway-WP
+ WordPerfect
+
+ BroadwayEngraved-WP
+ WordPerfect
+
+ CG Omega
+ Hewlett-Packard
+
+ CG Omega Bold
+ Hewlett-Packard
+
+ CG Omega Bold Italic
+ Hewlett-Packard
+
+ CG Omega Italic
+ Hewlett-Packard
+
+ CG Times
+ Hewlett-Packard
+
+ CG Times Bold
+ Hewlett-Packard
+
+ CG Times Bold Italic
+ Hewlett-Packard
+
+ CG Times Italic
+ Hewlett-Packard
+
+ Century-WP
+ WordPerfect
+
+ Clarendon Condensed
+ Hewlett-Packard
+
+ CommercialScript-WP
+ WordPerfect
+
+ CooperBlack
+ WordPerfect
+
+ Coronet Italic
+ Hewlett-Packard
+
+ Eurostile-WP
+ WordPerfect
+
+ Garamond Antiqua
+ Hewlett-Packard
+
+ Garamond Halbfett
+ Hewlett-Packard
+
+ Garamond Kursiv
+ Hewlett-Packard
+
+ Garamond Kursiv Halbfett
+ Hewlett-Packard
+
+ Hobo-WP
+ WordPerfect
+
+ Letter Gothic
+ Hewlett-Packard
+
+ Letter Gothic Bold
+ Hewlett-Packard
+
+ Letter Gothic Italic
+ Hewlett-Packard
+
+ Marigold
+ Hewlett-Packard
+
+ MurrayHill-WP
+ WordPerfect
+
+ OldEnglish-WP
+ WordPerfect
+
+ OldTown-WP
+ WordPerfect
+
+ Stencil-WP
+ WordPerfect
+
+ Symbol
+ Microsoft
+
+ Times New Roman
+ Microsoft
+
+ Univers
+ Hewlett-Packard
+
+ Univers Italic
+ Hewlett-Packard
+
+ Univers Bold
+ Hewlett-Packard
+
+ Univers Bold Italic
+ Hewlett-Packard
+
+ Univers Condensed
+ Hewlett-Packard
+
+ Univers Condensed Bold
+ Hewlett-Packard
+
+ Univers Condensed Bold Italic
+ Hewlett-Packard
+
+ Univers Condensed Italic
+ Hewlett-Packard
+
+ Wingdings
+ Microsoft
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(6_6) b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(6_6)
new file mode 100644
index 0000000000..7fc133c16a
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_General_Info_(6_6)
@@ -0,0 +1,442 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: General Info (6/6)
+Supersedes: <font-faq-6_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:39 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 419
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-6_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48301 comp.answers:20515 news.answers:79236
+
+Archive-name: fonts-faq/part6
+Version: 2.1.5
+
+Subject: 1.33. Digital Type Design Tools
+
+ This article was constructed from a posting by Charles A. Bigelow in
+ Jun 1994 and a posting by Clive Bruton in Jan 1995.
+
+ How do the various digital type designing tools compare?
+ ========================================================
+
+ Charles A. Bigelow contributes:
+
+ Kris Holmes and I use Ikarus and IkarusM, on the Macintosh, for most of
+ our work. We also use Fontographer from time to time. Both are good
+ tools. We have not tried TypeDesigner. We have tried FontStudio, but
+ don't use it.
+
+ IkarusM and Fontographer user interfaces are different (modulo the Mac
+ interface). IkarusM displays all "on-curve" points, treating the curves
+ as Hermite splines, which it converts to Beziers when making Type1 or
+ Type3 fonts, and to quadratic B-splines when making TrueType fonts.
+ On-curve points are helpful because they are intuitively more like what
+ a naive user would expect--to change a curve, change a point on its
+ contour. Fontographer uses bezier on-curve and off-curve control
+ points. While these take a little more getting used-to, experienced
+ users have no problems manipulating curves by moving around the
+ off-curve control points.
+
+ Fontographer uses curve fitting of scanned input and/or mouse
+ manipulation of points to get started on outlines. IkarusM uses
+ graphics tablet input from drawn (or photographed) artwork or mouse
+ manipulation to get started.
+
+ Both provide auto-hinting capabilities (IkarusM just included this in
+ version 3.0), but I haven't compared the quality of hinting between the
+ applications. Both provide automatic kerning capabilities, but again I
+ haven't compared the quality carefully. IkarusM itself doesn't do
+ kerning, but version 3.0 comes with Kernus, a separate auto-kerning
+ system.
+
+ Fontographer has more "goodies" in terms of the the different kinds of
+ output of fonts and screen fonts for different platforms (indeed, we
+ prefer it for making BDF bitmaps for UNIX platforms), and in the "finer
+ points" so to speak, of manipulating control points, whereas IkarusM
+ has more internal accuracy of resolution and more geometric symmetry
+ manipulation tools.
+
+ Fontographer has auto-tracing capability, for fitting outlines to
+ scanned images, whereas IkarusM needs a separate program, LinusM to do
+ that. However, LinusM adds several capabilities that Fontographer does
+ not provide.
+
+ I have forgotten the current list price for Fontographer (sorry, but
+ I'm sure a Fontographer user or someone from Altsys can provide it; is
+ it around \$250 - \$300?). IkarusM + Kernus + LinusM is around \$900,
+ but one should check with the URW office in Nashua, NH, to be certain
+ of that figure and of what is included.
+
+ There are many other differences between the programs, and perhaps other
+ users will want to point them out.
+
+ Which would I choose? Well, I have them both. Kris Holmes and I have
+ produced over 75 typefaces with Ikarus, though some of those were with
+ Ikarus on VAX or Sun. We are comfortable with Ikarus and feel that it
+ provides the highest level of precision and control, which for our
+ professional purposes is what we most value. Nevertheless, we find
+ Fontographer to be very good tool and continually buy the updates and
+ test it and use it for various things when we feel that it is superior
+ to Ikarus in particular respects. The best thing would be to test them
+ both, but unfortunately, one's preference for one or the other might
+ not manifest itself until one has gained more experience.
+
+ Disclaimer: We pay the standard prices and purchase our copies of
+ IkarusM and Fontographer and their upgrades, figuring that font tool
+ developers deserve to be paid for their work, just like font designers.
+ Bigelow & Holmes has font licensing arrangements with URW, the
+ developers of Ikarus, but we are not paid by them.
+
+ What about FontStudio?
+ ======================
+
+ [Editors note: This seems like valuable information for the FAQ, which
+ is why I've included it in a mostly wholesale fashion as Clive posted
+ it. In general, I'm not a big fan of anonymous contributions, but in
+ this case I've chosen to look the other way ;-). In particular, I've
+ made no attempt to disambiguate the personal pronouns in this section!]
+
+ Clive Bruton contributes the following:
+
+ I will now do a mini compendium of all my comments as FontStudio's chief
+ promoter, along with all the other people who support my view.
+
+ Sorry to those who are not credited, but others wish to remain
+ anonymous.
+
+ The following snippets are not necessarily in chronological order, names
+ have been changed to protect the guilty!
+
+ Is FontStudio Still Being Marketed?
+ -----------------------------------
+
+ Well it's one of those questions isn't it, it is certainly advertised in
+ the UK and as far as I know still supported by Letraset UK, but as you
+ have probably seen in comp.fonts there has been some debate over the
+ relative merits of FontStudio vs Fontographer, my arguement suitably
+ backed-up by ...., and there is certainly some doubt over its imediate
+ future.
+
+ Personally I'd like to see it re-launched, if only because the market
+ needs some stimulation in order to produce ground-breaking products, and
+ one App/Vendor (Fontographer/Altsys) doesn't make for healthy
+ competition, as we've seen with Quark getting fat and lazy over their
+ upgrades for XPress with no perceived threat from PageMaker (that should
+ change real soon).
+
+ However it (FS) retails in the UK for \$195.00 as opposed to
+ Fontographers \$295.00, the current version is 2.0, as it has been for
+ over two years, but then again there have been no bug fixes for it, no
+ need!
+
+ I am sure that you could buy it in the US via Letraset directly, if you
+ wanted to. As far as marketing goes, I have just received a software
+ brochure from Camalot (UK software vendor) that partly showcases the
+ full Letraset range, and FontStudio is in there with the rest.
+
+ If you can't get it in the States, I'm sure I can arrange for it to be
+ shipped to you.
+
+ What About Bitmap Generation?
+ -----------------------------
+
+ FontStudio's advantage is that they call the ATM API to get
+ ATM-generated bitmaps. Fontographer generates their own--and the
+ results are much heavier and more messy.
+
+ Yes, you're right, I did know, FS has 3 options on this, its own
+ generation, which like Fontographers are rather heavy, ATM's which are
+ just about perfect, and True Type, which from memory--since I only
+ tried it a couple of times--tend to be a bit quirky.
+
+ FontStudio is Better [than Fontographer]?
+ -----------------------------------------
+
+ Could you elaborate on that? Why do you suppose that FontStudio
+ disappeared, and Fontographer is still around? Not being belligerent or
+ challenging you, since I'm totally unfamiliar with FontStudio--but
+ Altsys is not exactly a Goliath compared to Letraset, in terms of the
+ size of the company or the depth of its pockets, and I'm curious why
+ such a good product from a big font vendor disappeared.
+
+ I'll chime in here if that's OK. I'm very glad FontStudio came along;
+ Fontographer was resting on its laurels until it got serious
+ competition. Many people prefer FontStudio's drawing interface (which is
+ like Illustrator's) to Fontographer's (which is, unsurprisingly, like
+ Freehand's). There are other parts to the interface debate as well, like
+ zoom factors, dialog complexity, and so forth, although much of it may
+ be a matter of taste.
+
+ XXXXXXXXXXXXXXX was one of FontStudio's beta sites, and they used a lot
+ of our advice, so it's not accidental that our designers still tend to
+ use it until it's time to move the fonts over to the SPARCs. I use it
+ when I'm playing with designs at home.
+
+ It looks like Letraset didn't know how to promote what it had. It's
+ worth noting that they'yre divesting themselves of their other graphics
+ apps, not just FontStudio. At any rate, the biggest hurdle was that
+ Fontographer had a four-year head start, capturing the hearts of nearly
+ everyone who was serious about making fonts. Nobody wants to relearn an
+ app, so the competition has to be darned good to get people to switch.
+ It has happened (witness XPress vs PageMaker) but it's not easy.
+ Another problem was that Letraset didn't develop FontStudio, they
+ bought it. They and the developers (now Ares, the FontMonger people)
+ didn't get along well, and that led to a painfully slow upgrade
+ process. Altsys got themselves in gear, and started adding features
+ right & left, outdoing FontStudio on nearly every count (technically,
+ not necessarily in terms of user experience).
+
+ I can only agree with what XXX has said above, plus...
+
+ Just some more background info on FontStudio/Letraset. Unfortunately
+ Letraset never seemed to get the knack of selling software, some
+ examples of this are, Letraset were originally the distributors of Adobe
+ products in the UK - a job that is now carried out by Principal, they
+ also had a full complement of other Mac software - which seems to have
+ reverted to its authors or disappeared alltogether, it has recently
+ released the first commercially available Plug-In for Illustrator, a
+ derivative of LetraStudio, to allow the creation of pespective and
+ envelope effects - who knows about this?
+
+ Back to the FontStudio/Fontographer debate, I have tried to use
+ Fontographer, but as discussed above, the interface is just awful (as an
+ aside, does anyone like FreeHand 4.0's interface?), FontStudios use of
+ colour, pop-up menus, and general look and feel is completely at home
+ alongside XPress and Illustrator, where as Fontographer, well... isn't!
+
+ All the buzzers and bells are there in Fontographer, but can you really
+ take seriously a program that won't allow you to draught your own
+ bitmaps! (Yeah I have heard about ATM, that's not the point).
+
+ Also, and I won't lay the blame solely at the door of Altsys, whenever
+ I get asked to sort out a problem font, it's always been created with
+ Fontographer. Now whether that is down to Altsys Fontographer (AF)
+ trying to things that aren't exactly kosher (like using even/odd rule
+ instead of winding), or the skill of the digitisers who did the work
+ I've never been able to fathom, but it's usually fixed by importing into
+ FontStudio (FS) and re-saving.
+
+ I hope that Ares do something with FS, otherwise sooner or later I am
+ going to need a new program (I have found a minor screen draw problem
+ when used with System 7.5, I've yet to try it on a PowerMac [anyone
+ wants me to, I can send you results]), I have already looked around, and
+ seem a lot more likely to buy Ikarus M than AF, it's really that bad.
+
+ I would also like to comment on XXX's point about XPress/PageMaker, I
+ hope that Adobe can make a real killer of PM, and reverse that trend,
+ XPress>PM that'll be the way to go!
+
+ Just to take Xpress' name in vain again (I don't hate the program, just
+ the smug bastards that want to charge me \$190.00 to get a native
+ version, and only a native version - Adobe has got the right attitude
+ there!) "XPress" is to "Word for Windows", what "FontStudio" is to
+ "Fontographer".
+
+ QED. Maybe not!
+
+ If all those in favour send me a *YAY* (addressed to
+ typonaut@d-supp.demon.co.uk) and someone sends me e-addresses for Ares
+ and Letraset, then I will forward them your support, who knows Altsys
+ may even decide to pack the whole Fontographer game in, and Adobe can
+ relaunch FontStudio!
+
+Subject: 1.34. Type Design Firms
+
+ Although it has been a long time coming, it seems only natural that the
+ comp.fonts FAQ should provide a brief summary of what the various type
+ design firms are producing.
+
+ Carter & Cone Type, Inc.
+ ========================
+
+ This description was constructed from postings by Don Hosek, Erik-Jan
+ Vens, and David Lemon in Sep, 1993.
+
+ Carter & Cone Type Inc.
+ 2155 Massachusetts Avenue
+ Cambridge, MA 02140
+ 617-576-0398 or 800-952-2129
+ 617-354-4146 FAX
+
+ We begin with Carter & Cone not because I think they should be first,
+ but because I already have a few articles about them (I probably saved
+ the articles more because they were about Galliard, which I have a
+ fondness for, than anything else). Please contribute summaries about
+ other foundries (even the foundries themselves are encouraged to
+ contribute, althought I'd appreciate it if the advertising overtones
+ were kept to a dull roar ;-).
+
+ Galliard
+ --------
+
+ [Editors note: With appologies to C&C, I have the following snippet:
+
+ >> the designer. He's in business for himself now as half of Carter &
+ >> Cone (800 952 2129 voice), and he's worked Galliard over yet again.
+ >> Should be cool. Support your local type designer.
+
+ Which half of C&C does this refer to?]
+
+ Don Hosek says:
+
+ The specimen sheets arrived in the mail today (along with the newest
+ Font & Function). Carter & Cone has three faces: ITC Galliard [CC]
+ which is a family of 11 fonts. The bad news is that assignments of
+ characters into expert sets and basic fonts is non-standard (the basic
+ font is missing fi and fl). The good news is that the fonts are quite
+ inexpensive. The whole set can be purchased for \$150. The font is a
+ single weight only (if bold is strictly necessary, Bitstream Galliard
+ Bold is consistent in height and can be mixed. On the other hand,
+ designers need to learn to avoid the crutch of bold face on their
+ pages). It is possible to purchase just those parts of the package
+ which are needed. Those able to mix fonts on their own might be able to
+ get a decent selection for less than \$150.
+
+ Sophia
+ ------
+
+ Don continues,
+
+ The second font is Sophia which is a kind of quirky all-caps display
+ face. It features a number of upper case ligatures [!] and has a kind
+ of Greek-Turkish feel to it (not suprising, really: the face is based
+ in 6th c. Constantinople letterforms). When I first saw this, I didn't
+ like it, but it does grow on one. The price on this is \$60.
+
+ Mantinia
+ --------
+
+ Finally, Don concludes,
+
+ The third font is Mantinia which is a more traditional display roman
+ with some interesting features: e.g., more uppercase ligatures and an
+ alphabet with superior caps in place of lower case (the La of LaTeX
+ could be typeset without kerns or raises using this alphabet). Again,
+ this took some growing on one, but I'm more accepting of this (and can
+ even imagine using it for real work). The price on this is \$60.
+
+Subject: 1.35. What does `lorem ipsum dolor' mean?
+
+ `Lorem ipsum dolor' is the first part of a nonsense paragraph sometimes
+ used to demonstrate a font. It has been well established that if you
+ write anything as a sample, people will spend more time reading the
+ copy than looking at the font. The "gibberish" below is sufficiently
+ like ordinary text to demonstrate a font but doesn't distract the
+ reader. Hopefully.
+
+ Rick Pali submits the following from Before and After Magazine, Volume
+ 4 Number 2.:
+
+ [quote]
+
+ After telling everyone that Lorem ipsum, the nonsensical text that
+ comes with PageMaker, only looks like Latin but actually says nothing, I
+ heard from Richard McClintock, publication director at the
+ Hampden-Sydney College in Virginia, who had enlightening news:
+
+ "Lorem ipsum is latin, slightly jumbled, the remnants of a passage from
+ Cicero's _de Finibus_ 1.10.32, which begins 'Neque porro quisquam est
+ qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit...'
+ [There is no one who loves pain itself, who seeks after it and wants to
+ have it, simply because it is pain.]. [de Finibus Bonorum et Malorum,
+ written in 45 BC, is a treatise on the theory of ethics very popular in
+ the Renaisance.]
+
+ "What I find remarkable is that this text has been the industry's
+ standard dummy text ever since some printed in the 1500s took a galley
+ of type and scambled it to make a type specemin book; it has survived
+ not only four centuries of letter-by-letter resetting but even the leap
+ into electronic typesetting, essentially unchanged except for an
+ occational 'ing' or 'y' thrown in. It's ironic that when the
+ then-understood Latin was scrambled, it became as incomprehensible as
+ Greek; the phrase 'it's Greek to me' and 'greeking' have common semantic
+ roots!"
+
+ [unquote]
+
+ One Example of Lorem Ipsum Dolor
+ ================================
+
+ Lorem ipsum dolor sit amet, consectetaur adipisicing elit, sed do
+ eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad
+ minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip
+ ex ea commodo consequat. Duis aute irure dolor in reprehenderit in
+ voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur
+ sint occaecat cupidatat non proident, sunt in culpa qui officia
+ deserunt mollit anim id est laborum Et harumd und lookum like Greek to
+ me, dereud facilis est er expedit distinct. Nam liber te conscient to
+ factor tum poen legum odioque civiuda. Et tam neque pecun modut est
+ neque nonor et imper ned libidig met, consectetur adipiscing elit, sed
+ ut labore et dolore magna aliquam makes one wonder who would ever read
+ this stuff? Bis nostrud exercitation ullam mmodo consequet. Duis aute
+ in voluptate velit esse cillum dolore eu fugiat nulla pariatur. At vver
+ eos et accusam dignissum qui blandit est praesent luptatum delenit
+ aigue excepteur sint occae. Et harumd dereud facilis est er expedit
+ distinct. Nam libe soluta nobis eligent optio est congue nihil impedit
+ doming id Lorem ipsum dolor sit amet, consectetur adipiscing elit, set
+ eiusmod tempor incidunt et labore et dolore magna aliquam. Ut enim ad
+ minim veniam, quis nostrud exerc. Irure dolor in reprehend incididunt
+ ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud
+ exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
+ Duis aute irure dolor in reprehenderit in voluptate velit esse
+ molestaie cillum. Tia non ob ea soluad incommod quae egen ium improb
+ fugiend. Officia deserunt mollit anim id est laborum Et harumd dereud
+ facilis est er expedit distinct. Nam liber te conscient to factor tum
+ poen legum odioque civiuda et tam. Neque pecun modut est neque nonor
+ et imper ned libidig met, consectetur adipiscing elit, sed ut labore et
+ dolore magna aliquam is nostrud exercitation ullam mmodo consequet.
+ Duis aute in voluptate velit esse cillum dolore eu fugiat nulla
+ pariatur. At vver eos et accusam dignissum qui blandit est praesent.
+ Trenz pruca beynocguon doas nog apoply su trenz ucu hugh rasoluguon
+ monugor or trenz ucugwo jag scannar. Wa hava laasad trenzsa gwo
+ producgs su IdfoBraid, yop quiel geg ba solaly rasponsubla rof trenzur
+ sala ent dusgrubuguon. Offoctivo immoriatoly, hawrgasi pwicos asi
+ sirucor.Thas sirutciun applios tyu thuso itoms ghuso pwicos gosi
+ sirucor in mixent gosi sirucor ic mixent ples cak ontisi sowios uf Zerm
+ hawr rwivos. Unte af phen neige pheings atoot Prexs eis phat eit sakem
+ eit vory gast te Plok peish ba useing phen roxas. Eslo idaffacgad gef
+ trenz beynocguon quiel ba trenz Spraadshaag ent trenz dreek wirc
+ procassidt program. Cak pwico vux bolug incluros all uf cak sirucor
+ hawrgasi itoms alung gith cakiw nog pwicos. Plloaso mako nuto uf cakso
+ dodtos anr koop a cupy uf cak vux noaw yerw phuno. Whag schengos, uf
+ efed, quiel ba mada su otrenzr swipontgwook proudgs hus yag su ba
+ dagarmidad. Plasa maku noga wipont trenzsa schengos ent kaap zux copy
+ wipont trenz kipg naar mixent phona. Cak pwico siructiun ruos nust
+ apoply tyu cak UCU sisulutiun munityuw uw cak UCU-TGU jot scannow.
+ Trens roxas eis ti Plokeing quert loppe eis yop prexs. Piy opher
+ hawers, eit yaggles orn ti sumbloat alohe plok. Su havo loasor cakso
+ tgu pwuructs tyu InfuBwain, ghu gill nug bo suloly sispunsiblo fuw
+ cakiw salo anr ristwibutiun. Hei muk neme eis loppe. Treas em wankeing
+ ont sime ploked peish rof phen sumbloat syug si phat phey gavet peish
+ ta paat ein pheeir sumbloats. Aslu unaffoctor gef cak siructiun gill bo
+ cak spiarshoot anet cak GurGanglo gur pwucossing pwutwam. Ghat dodtos,
+ ig pany, gill bo maro tyu ucakw suftgasi pwuructs hod yot tyubo
+ rotowminor. Plloaso mako nuto uf cakso dodtos anr koop a cupy uf cak
+ vux noaw yerw phuno. Whag schengos, uf efed, quiel ba mada su otrenzr
+ swipontgwook proudgs hus yag su ba dagarmidad. Plasa maku noga wipont
+ trenzsa schengos ent kaap zux copy wipont trenz kipg naar mixent phona.
+ Cak pwico siructiun ruos nust apoply tyu cak UCU sisulutiun munityuw
+ uw cak UCU-TGU jot scannow. Trens roxas eis ti Plokeing quert loppe
+ eis yop prexs. Piy opher hawers, eit yaggles orn ti sumbloat alohe
+ plok. Su havo loasor cakso tgu pwuructs tyu.
+
+ [This version was found on CompuServe. It differs from other versions I
+ have seen in print, increasingly so as you go along. It almost looks
+ computer-generated, doesn't it?]
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_MS-DOS_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_MS-DOS_Info
new file mode 100644
index 0000000000..aa5039f6e6
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_MS-DOS_Info
@@ -0,0 +1,629 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: MS-DOS Info
+Supersedes: <font-faq-8_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:49 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 606
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-8_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48306 comp.answers:20520 news.answers:79241
+
+Archive-name: fonts-faq/part8
+Version: 2.1.5
+
+Subject: 3. MS-DOS Information
+
+ The easiest way to get outline fonts under MS-DOS is with Microsoft
+ Windows 3.x or OS/2 2.x.
+
+ Microsoft Windows 3.0 with Adobe Type Manager (ATM) and OS/2 2.0
+ support PostScript Type1 fonts.
+
+ Microsoft Windows 3.1 supports TrueType fonts natively.
+
+ Bitmap fonts are available in a variety of formats: most formats are
+ designed with the printer in mind and not the display since (prior to
+ graphical environments like Windows, GEM, and OS/2) the majority of
+ work under MS-DOS was done with a character-based interface.
+
+Subject: 3.1. Frequently Requested MS-DOS fonts
+
+ Many fonts are available at various archives. The biggest font archive
+ for MS-DOS format fonts is ftp.cica.indiana.edu. Note: you can use any
+ Mac format Type1 font on your PC by converting it to PC format with the
+ free/shareware as described below.
+
+ The following fonts are in Type 1 format for MS-DOS. Some are also
+ available in TrueType format.
+
+ * Hebrew
+
+ ShalomScript, ShalomOldStyle, ShalomStick
+
+ * Japanese
+
+ Shorai
+
+ * Star Trek
+
+ Crillee, TNG monitors
+
+ * IBM OEM Line Drawing Characters
+
+ Try Adobe PrestigeElite or Adobe LetterGothic. They have all the
+ characters you want, but the `line draw' characters are unencoded
+ -- you will need tools to reencode the outline font itself and
+ make a new PFM metric files.
+
+ Or try IBMExtended from Impramatur Systems in Cambridge, Mass. It
+ already is encoded using IBM OEM encoding (some DOS code page).
+
+ The IBM version of Courier distributed freely under the X11
+ Consortium also contains the appropriate characters. Again, the
+ font will have to be reencoded for Windows. Appropriate AFM files
+ for this font can be obtained from:
+ http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+ Lee Cambell suggests the following alternative:
+
+ Line Drawing characters are also available on ftp sites as
+ gc0651.exe which is a self-expanding archive. It is on cica (and
+ mirrors thereof). From the text file that comes with it, it looked
+ like it was distributed by Microsoft. I printed some text in the
+ normal A-z range and it looked identical to the truetype Courier
+ font distributed with Windows. Perhaps it is an upgrade to that
+ font. I didn't try the linedraw glyphs, so I can't say how they
+ look.
+
+Subject: 3.2. MS-DOS Font Installation
+
+ If you have any information that you feel belongs in this section, it
+ would be greatly appreciated.
+
+ * Windows
+
+ * Pat Farrell contributes the following description of font
+ installation under Windows.
+
+ Installing Fonts into Windows:
+
+ This only covers Windows 3.1 with ATM. Font is a four-letter
+ word in Windows versions prior to 3.1 due to the distinctions
+ between screen fonts and printer fonts. The upgrade price of
+ Windows 3.1 is justified by the integration of TrueType into
+ the package and the inclusion of useful fonts for all
+ printers.
+
+ Commercial fonts usually have installation instructions with
+ their manuals. The approach may differ from the method used
+ for PD and shareware fonts.
+
+ To install PD and shareware fonts in Windows 3.1:
+
+ 1. Copy the fonts onto a suitable scratch area (i.e. a
+ floppy, or any temporary area of your hard disk.
+
+ 2. Execute "Control Panel" by double-clicking on the icon
+ in the Windows Program Manager's "main" group.
+
+ 3. Double-click on the Fonts icon.
+
+ 4. Double-click on the "Add" button.
+
+ 5. Select the scratch directory holding the new fonts.
+
+ 6. A list of the fonts will be displayed. You can manually
+ select the fonts you like, or you can use the
+ "Select All" button.
+
+ 7. Make sure the "Copy Fonts to Windows Directory"
+ check-box is checked. This will copy the fonts
+ from the scratch area to your Windows directory.
+
+ 8. Click on the "Ok" button.
+
+ * Special notes for Windows applications:
+
+ Word for Windows (W4W) stores font/printer information in its
+ own initialization files. After you add new fonts, you have
+ to tell W4W that the printer can use the new fonts. Do this
+ by selecting "Printer Setup" from the W4W main "File" menu
+ item, click on the "Setup" button, and then click on two "Ok"
+ buttons to back out of the setup mode.
+
+ * Note concerning Windows 3.1 upgrade:
+
+ There are two upgrade packages available from Microsoft for
+ Win3.1. There is the standard version which contains
+ TrueType support, and about six font families (Times New
+ Roman, Arial, Courier, Symbols, Wingdings, etc.). It costs
+ something like $50 (US). The second version contains a number
+ of TrueType fonts that includes equivalents for the 35
+ standard Postscript fonts. This adds an additional $50, which
+ is a pretty good value. However, if you plan on buying
+ Microsoft's PowerPoint, it includes the same additional
+ fonts/typefaces. So you can save money by not buying the
+ fonts twice.
+
+ * More about Windows
+
+ * [Q:] Why are don't the TrueType fonts that come with
+ Microsoft products (Word-for-Windows, PowerPoint,
+ Windows 3.1 TrueType Font Pack, etc.) display and
+ print properly on my system?
+
+ * [A:] The font matching algorithm in Win3.1 is fairly
+ simplistic. If you install lots of TrueType fonts,
+ the algorithm can get confused. In this case, "lots"
+ is more than 50 or so.
+
+ * According to Luann Vodder who supports Microsoft Word on
+ CompuServ:
+
+ "There is a procedure which Windows must go through when an
+ application requests a font. Each font contains a list of
+ attributes such as Family, FaceName, Height, Width,
+ Orientation, Weight, Pitch, etc. When an application
+ requests a font, it fills out a logical font for Windows
+ containing the necessary attributes, then starts going
+ through a font mapping algorithm to determine which of the
+ installed fonts most closely matches the requested (logical)
+ font. Penalties are applied against fonts whose attributes
+ do not match the logical font, until the fonts with the
+ fewest penalties are determined. If there is a "tie",
+ Windows may need to rely on the order of the fonts in the
+ WIN.INI file to determine the "winner".
+
+ If the fonts you want are in your WIN.INI file, and show up in
+ Windows' Control Panel, then try moving them higher in your
+ WIN.INI file with a file edittor such as SYSEDIT."
+
+ * Kesh Govinder suggested the following warning:
+
+ CAUTION: While many Windows 3.1 users would like to have many
+ TrueType fonts at their disposal (and they are many available
+ in the PD) a word of caution. A large number (>50) TT fonts
+ will slow down your windows startup time. This occurs as
+ every installed font is listed in the win.ini file, and
+ Windows has to go through the entire file before starting up.
+ While this may not affect most users, it will especially
+ affect users of CorelDraw!, so be warned.
+
+ * Other Programs
+
+ It is an unfortunate fact that almost all MS-DOS programs do things
+ differently. Your best bet is to read the manual that comes with
+ the program you want to use.
+
+Subject: 3.3. What exactly are the encodings of the DOS code pages?
+
+ DOS uses `code pages' for `IBM OEM' encoding of fonts. There are six
+ code pages supplied with DOS 5.0:
+
+ 437 (English)
+ 850 (Multilingual - Latin I)
+ 852 (Slavic - Latin II)
+ 860 (Portugal)
+ 863 (Canadian French)
+ 865 (Nordic)
+
+ (The character code range 0 - 127 is the same in all code pages).
+
+ The problem is that MS idea of how to define what a code page is, is to
+ show a low resolution print out of the glyphs! Which is fine for the
+ letters of the alphabet, numerals and the obvious punctuation marks,
+ but worthless for accents (is it `cedilla' or `ogonek'? is it `caron'
+ or `breve'?) and many other characters. For example, 249 is a small
+ dot, while 250 is a slightly larger dot. Is one of these supposed to
+ be `bullet' (which already occurs at 7)? Or is one of them maybe
+ supposed to be `middot' or `dotcentered'? Is 228 supposed to be
+ `Sigma' or `summation'. Is 225 supposed to be `beta' or `germandbls'?
+ Etc etc
+
+ And what is the character that looks like `Pt' in code position 158?
+
+ Anyway, surely there is a table somewhere that defines precisely what
+ these encodings are supposed to be. That is, a table that gives for
+ each code number the name and/or a description of the character.
+
+Subject: 3.4. MS-DOS Font Utilities
+
+ * PS2PK
+
+ PS2PK allows you to convert PostScript Type1 fonts into bitmap
+ fonts. The bitmap files produced are in TeX PK format.
+
+ * PKtoSFP
+
+ PKtoSFP allows you to convert TeX PK fonts into HP LaserJet
+ softfonts.
+
+ * PFBDir/PFBInfo
+
+ PFBDir and PFBInfo format and display the "headers" in a binary
+ Type1 font.
+
+Subject: 3.5. Converting fonts under MS-DOS
+
+Subject: 3.5.1. Converting Mac Type 1 fonts to MS-DOS format
+
+ Converting Macintosh Type1 fonts into PC Type1 fonts can be done using
+ purely free/shareware tools. I've outlined the procedure below. Make
+ sure you read the "readme" files that accompany many fonts. Some font
+ authors specifically deny permission to do cross-platform conversions.
+
+ The tools you need
+ ==================
+
+ XBIN
+ xbin23.zip in /pub/msdos/mac on oak.oakland.edu (or other
+ mirrors)
+
+ UNSIT
+ unsit30.zip in /pub/msdos/mac on oak.oakland.edu
+
+ UNSITI
+ unsiti.exe in /pub/onset/util on ftp.std.com
+
+ Peter Gentry indicates that this program can extract SIT
+ archives that use the newer compression techniques that unsit
+ doesn't recognize.
+
+ UNCPT
+ ext-pc.zip in /pub/pc/win3/util on ftp.cica.indiana.edu
+
+ REFONT
+ refont14.zip from
+ http://www.ora.com/homepages/comp.fonts/FAQ-tools.html
+
+ BMAP2AFM
+ bm2af02.zip from
+ http://www.ora.com/homepages/comp.fonts/FAQ-tools.html
+
+ XBIN converts Mac "BinHex"ed files back into binary format. BinHex is
+ the Mac equivalent of UUencoding, it translates files into ascii
+ characters so that mailers can send them around without difficulty. It
+ also aids in cross platform copying too, I'm sure. BinHexed files
+ generally have filenames of the form "xxx.yyy.HQX".
+
+ UNSIT explodes "Stuffit" archives. Stuffit archives generally have
+ filenames of the form "xxx.SIT". UNSIT will ask if you want to
+ seperate resource and data forks. Yes, you do. There has been some
+ confusion about whether or not you want headers. I'm inclined to
+ conclude that it can be made to work either way. Personally, I say no.
+
+ UNCPT explodes "Compactor" archives. The ext-pc implementation is
+ called "extract" and does not require windows (even thought it's in the
+ windows section on cica). Compactor archives generally have filenames
+ of the form "xxx.CPT".
+
+ REFONT converts Mac type1 fonts into PC type1 fonts. It also converts
+ Mac TrueType fonts to PC TrueType format. And vice-versa.
+
+ BMAP2AFM constructs AFM files from the metric information contained in
+ Mac screen fonts (.bmap files). The screen font files do not have any
+ standard name (although they frequently have the extension .bmap). The
+ screen fonts have file type "FFIL" which, in combination with some
+ common sense, is usually sufficient to identify them.
+
+ I've listed the tools that I've used and the sites that are reasonable
+ for me to retrieve them from. It's probably a good idea to check with
+ archie for closer sites if you're not in North America. These tools
+ run under MS-DOS. XBIN and UNSIT can also be run under Unix.
+
+ How to do it?
+ =============
+
+ Collect the Mac fonts from the archive or BBS of your choice. Most of
+ these files will be in BinHexed format. As a running example, I'm
+ going to use the imaginary font "Plugh.cpt.hqx". When I download this
+ font to my PC, I would use the name "PLUGH.CPX". The actual name you
+ use is immaterial.
+
+ Run XBIN on PLUGH.CPX. This will produce PLUGH.DAT, PLUGH.INF, and
+ PLUGH.RSR. The data fork of the Mac file (the .DAT file) is the only
+ one of interest to us, you can delete the others.
+
+ If the original file had been "Plugh.sit.hqx", we would be using the
+ UNSIT program. Since I chose a .cpt file for this example, I'm going
+ to run UNCPT.
+
+ Run UNCPT on PLUGH.DAT. You want to extract the AFM file (if present),
+ the documentation or readme file (if present), and the Type1 outline
+ file. The AFM and README files will be in the data fork of the archive
+ file. The Type1 outline will be in the resource fork. The AFM and
+ README files have Mac "TEXT" type. The Type1 outline file has "LWFN"
+ type. I'm not trying to describe this part in a step-by-step fashion.
+ Use the docs for UNCPT and UNSIT as a guide. If you got this far you
+ probably won't have much difficulty. If you do, drop me a line and
+ I'll try to help.
+
+ If the font does not contain an AFM file, extract the screen font.
+ Screen fonts frequently have the extension .bmap and are "FFIL" type
+ files. Use Bmap2AFM to construct an AFM from the screen font. If the
+ archive _does_ contain an AFM file, it's safe to bet that the author's
+ AFM will be better than the one created by Bmap2AFM.
+
+ Finally, run REFONT on the Type1 outline that you extracted above. The
+ result should be an appropriate PC type1 outline. REFONT will create a
+ PFM file for you from the AFM file, if you desire.
+
+ Remember to register your shareware...
+
+ Other comments
+ ==============
+
+ vkautto@snakemail.hut.FI makes the following observations:
+
+ * UNCPT is easier to use than UNSIT
+
+ * UNCPT has to be run twice. I usually do it like this
+
+ extract *.cpt -f
+
+ extract *.cpt -f -r
+
+ * When using "unsit30" you probably want the outline file with the
+ MacHeader and the others without it. I think that REFONT
+ requires it but I am not sure.
+
+ * REFONT works usually ok. You want a PFA (ASCII) file which is
+ directly usable on NeXT (you may need to convert carriage-returns
+ to newlines but I am not sure if it is necessary).
+
+ The biggest problem is with the .afm files that are completely
+ missing or generated by the tools that don't do their job
+ properly.
+
+ * BMAP2AFM requires some extra files (ie. other than bmap2afm.exe) to
+ work properly.
+
+Subject: 3.5.2. Converting PC Type 1 and TrueType fonts to Mac format
+
+ Refont
+ ======
+
+ Refont (version 1.4) can convert (in both directions) between PC and Mac
+ formats of Type1 and TrueType fonts. Note: it _cannot_ convert
+ _between_ formats, only architectures. The procedure described above
+ outlines how to convert a Mac archive into PC format so that you can
+ get at the data. Presumably, the process can be reversed so that you
+ can get at the data on the Mac side as well. Unfortunately, I don't
+ have a Mac so I can't describe the process in detail.
+
+ Font Manipulation Package
+ =========================
+
+ The Y\&Y Font Manipulation package can convert PFA/B files into Mac
+ format and AFM files into Mac screen fonts.
+
+Subject: 3.5.3. Converting PC Type 1 fonts into TeX PK bitmap fonts
+
+ The release of PS2PK by Piet Tutelaers is a godsend to those of us
+ without PostScript printers. PS2PK converts PC/Unix format Type 1 fonts
+ into TeX PK files. Used in conjunction with the AFM2TFM utility for
+ creating TeX metric files, this allows almost anyone to use Type 1
+ PostScript fonts. PS2PK is distributed under the GNU License and has
+ been made to run under MS-DOS with DJGPP's free GNU C compiler. The PC
+ version requires a 386 or more powerful processor. Check with Archie
+ for a source near you.
+
+ Note: if TeX PK files are not directly usable for you, there seems to
+ be a fair possibility that LaserJet softfonts would be useful. If so,
+ check below for instructions on converting TeX PK files to LaserJet
+ softfonts.
+
+Subject: 3.5.4. Converting TeX PK bitmaps into HP LaserJet softfonts (and vice-versa)
+
+ There is some possibility that someone will yell 'conflict of interest'
+ here, but I don't think so. I wrote the following utilities:
+
+ PKtoSFP: convert TeX PK files to LaserJet (bitmapped) softfonts
+
+ SFPtoPK: convert LaserJet (bitmapped) softfonts to TeX PK files
+
+ But they are completely free, so I don't gain anything by "advertising"
+ them here. These are MS-DOS platform solutions only. If you know of
+ other solutions, I would be happy to list them.
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 3.5.5. TrueType to HP LaserJet bitmap softfonts (HACK!)
+
+ If you have the tools, the following suggestion does work, but it isn't
+ easy and it hasn't been automated. To be honest, I haven't really
+ tested it.
+
+ If you are using Windows 3.1, get a LaserJet printer driver (you don't
+ need the printer, just the driver). Using the LaserJet driver, direct
+ output to a file and print a simple file containing all the letters you
+ want in the softfont in the font that you are converting. When the
+ print job has completed, the output file will contain, among other
+ things, a LaserJet softfont of the TrueType font you selected. If you
+ know the LaserJet format, you can grab it out of there.
+
+ I didn't say it was easy ;-)
+
+ This method will not work with ATM [ed: as of 7/92] because ATM does
+ not construct a softfont; it downloads the whole page as graphics.
+
+ Here is an overview of the LaserJet bitmap softfont format. It should
+ help you get started. If you have any questions, ask norm. If anyone
+ wants to write better instructions... ;-)
+
+ Many details are omitted from this description. They are thoroughly
+ discussed in the HP Technical Reference for each model of laser printer.
+ I recommend purchasing the Tech Ref. If you have additional questions
+ and do not plan to purchase the Tech Ref (or do not wish to wait for its
+ arrival), you can ask norm.
+
+ An HP LaserJet softfont can occur almost anywhere in the output stream
+ destined for the printer. In particular, it does _not_ have to be
+ wholly contiguous within the output file. In fact, fonts can be
+ "intermixed" at will. The following "pieces" make up a font:
+
+ A begin font descriptor command (followed by the descriptor) and a
+ series of begin character descriptor commands (followed by their
+ associated data). When a new character descriptor is encountered, it
+ is added to the current font (which may change between descriptors).
+
+ In the discussion that follows, the following notational conventions
+ are followed:
+
+ Key elements are surrounded by quotation marks. The quotation marks
+ are not part of the element. Spaces within the element are for clarity
+ only, they are not part of the element. All characters (except ESC and
+ #, described below, are literal and must be entered in the precise case
+ shown).
+
+ ESC means the escape character, ASCII character number 27 decimal.
+
+ # means any decimal number. The meaning of the number is described in
+ the commentary for that element.
+
+ * What is a font descriptor?
+
+ A font descriptor begins with a font descriptor command and is
+ followed immediately by the data for the descriptor. Font
+ descriptors define data global to the font. In general, more
+ recent printers are less strict about these parameters than older
+ printers.
+
+ * What is the font descriptor command?
+
+ "ESC ) s # W"
+
+ In this command, # is the number of bytes in the descriptor. The
+ first element of the descriptor indicates how many of these bytes
+ should be interpreted as the font descriptor (the remaining bytes
+ are commentary only-to the printer, at least). This area is
+ frequently used for copyright information, for example, although
+ some systems insert kerning data into this area.
+
+ * What is the font descriptor data?
+
+ The data is:
+
+ UI Font descriptor size
+ UB Descriptor format
+ UB Font type
+ UI Reserved (should be 0)
+ UI Baseline distance
+ UI Cell width
+ UI Cell height
+ UB Orientation
+ B Spacing
+ UI Symbol set
+ UI Pitch
+ UI Height
+ UI xHeight
+ SB Width Type
+ UB Style
+ SB Stroke Weight
+ UB Typeface LSB
+ UB Typeface MSB
+ UB Serif Style
+ SB Underline distance
+ UB Underline height
+ UI Text Height
+ UI Text Width
+ UB Pitch Extended
+ UB Height Extended
+ UI Cap Height
+ UI Reserved (0)
+ UI Reserved (0)
+ A16 Font name
+ ?? Copyright, or any other information
+
+ UI = unsigned integer, SI = signed integer, UB = unsigned byte, SB
+ = signed byte, B = boolean, and A16 =sixteen bytes of ASCII.
+
+ After the font name, ?? bytes of extra data may be inserted. These
+ bytes pad the descriptor out to the length specified in the begin
+ font descriptor command.
+
+ Note: integers are always in big-endian order (MSB first).
+
+ * What is a character descriptor?
+
+ A character descriptor describes the character specific info and
+ the layout of the bitmap. Newer printers can accept compressed
+ character bitmaps.
+
+ * What is a character descriptor command?
+
+ "ESC * c # E"
+
+ The # is the length of the descriptor, in bytes.
+
+ * What is the character descriptor data?
+
+ UB Format
+ B Continuation
+ UB Descriptor size
+ UB Class
+ UB Orientation
+ SI Left offset
+ SI Top offset
+ UI Character width
+ UI Character height
+ SI Delta X
+ ?? Character (bitmap) data.
+
+ Although older printers cannot accept characters that include
+ continuations, newer printers can. If the "continuation" field is
+ 1, the character bitmap data begins immediately after that byte and
+ the remaining fields _are not_ present.
+
+ * Ok, now I understand the data, what do I look for in the output
+ stream?
+
+ ESC * c # D
+ defines the font number (remember the number).
+
+ ESC ) s # W
+ defines the font descriptor (as described above).
+
+ ESC * c # E
+ specifies the character code (the #, in this case).
+ The next character descriptor maps to this position in
+ the font. Characters do not have to appear in
+ any particular order.
+
+ ESC ( s # W
+ defines the character descriptor (as described above).
+
+ Remember, these can occur in any order. Experimentation with the
+ particular driver you are using may help you restrict the number of
+ different cases that you have to be prepared for.
+
+ Please report your experiences using this method to norm (both to
+ satisfy his own curiosity and to help improve the FAQ).
+
+Subject: 3.6. MS-DOS Screen Fonts (EGA/VGA text-mode fonts)
+
+ Editors note: the following description was mercilessly stolen from
+ comp.archives on 02SEP92. It was originally Yossi Gil's
+ posting.
+
+ FNTCOL14.ZIP contains more than 200 text mode fonts for EGA/VGA
+ displays. It includes fonts in different sizes for Hebrew, Greek,
+ Cyrillic, math symbols and various type styles including smallcaps and
+ script.
+
+ It is available at borg.poly.edu:/pub/reader/dos/fntcol14.zip
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Macintosh_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Macintosh_Info
new file mode 100644
index 0000000000..7e32790be4
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Macintosh_Info
@@ -0,0 +1,756 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Macintosh Info
+Supersedes: <font-faq-7_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:44 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 733
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-7_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48304 comp.answers:20518 news.answers:79239
+
+Archive-name: fonts-faq/part7
+Version: 2.1.5
+
+Subject: 2. Macintosh Information
+
+Subject: 2.1. Macintosh Font formats
+
+ Bitmap Fonts
+ ============
+
+ Bitmap fonts: on the Macintosh, bitmap fonts also contain the kerning
+ information for a font and must be installed with both type 1 and type
+ 3 fonts. Their presence also speeds the display of commonly used font
+ sizes.
+
+ PostScript Type 1
+ =================
+
+ Postscript Type 1 fonts can be installed on the Macintosh only by using
+ accompanying bitmapped fonts.
+
+ PostScript Type 3
+ =================
+
+ Postscript Type 3 fonts are installed on the Macintosh in the same way
+ that Type 1 fonts are.
+
+ TrueType
+ ========
+
+ Truetype fonts: no bitmapped font is necessary with this type, though
+ commonly used sizes are often supplied.
+
+ QuickDraw GX
+ ============
+
+ This section was constructed from postings by Charles A. Bigelow, Peter
+ Moller, David Opstad, and Michael Wang from Sep 93.
+
+ What is it?
+ -----------
+
+ QuickDraw GX (QDGX) is the new Mac OS engine for handling screen
+ presentation. It has many advantages over older engines, among them the
+ ability to get ligatures, swashes etc. on the fly. QDGX is also a
+ 16-bit font format that allows for example users in Korea to run their
+ machines in their native tounge as well as write.
+
+ How is it related to Unicode?
+ -----------------------------
+
+ Although QDGX is a 16-bit encoding, it is "orthogonal" to Unicode
+ Unicode, to use a jargon term. A TrueType font, GX or otherwise, can be
+ encoded using the Unicode standard, but that isn't necessary. However, a
+ TrueType font, and especially a GX font, can contain glyphs for which
+ there is no unique Unicode encoding, e.g. the 'fi' ligature, or a swash
+ 'a' with a trailing curlicue. TrueType GX fonts, however, contain
+ additional information and structure that allows the QDGX system to
+ properly substitute variant glyphs for certain characters in the text.
+ For the above examples, QDGX will, if requested, look for the sequence
+ 'f' + 'i' and substitute the 'fi' ligature, or look for 'a' at the end
+ of a line and substitute the glyph 'a-trailing curlicue'.
+
+ It is really quite charming to see this happen, and it makes the font
+ [...] a clever, trained circus dog that does tricks than a simple font.
+ The GX fonts begin to show an additional personality beyond the image of
+ the glyphs. In fact, the font can contain a state machine that controls
+ the substitution process--in effect, a computer program. There is
+ provision for another state machine controlling kerning as well, to get
+ around the problems that can arise with simple pair-based kerning.
+
+ David Opstad contributes the following:
+
+ The bidirectional text reordering algorithm defined in Unicode is fully
+ implemented in GX (in fact, during our testing of GX we uncovered some
+ problems with the Unicode specification!) Also, and most unfortunately,
+ since Unicode is the product of an international committee process there
+ were certain compromises that were made in the design, so there really
+ are Unicode character codes for certain ligatures and contextual forms
+ (e.g. the "Basic Glyphs for Arabic Language" codes starting at U+FE70).
+ Note, however, that GX does not use these; we do Arabic contextual
+ processing the same way we do Roman contextual processing. Indeed, it
+ is this uniformity of approach that is, I believe, one of GX's main
+ strengths.
+
+ One of my greatest hopes (that keeps me going after having worked on
+ getting GX done for over five years now) is that we're going to see a
+ real renaissance of fonts and creativity in font designs. GX finally
+ gets us back to the elegance of calligraphy, with the repeatability and
+ precision of the computer.
+
+ What about rotation?
+ --------------------
+
+ QDGX supports full 3X3 transformations (including perspective) on all
+ objects in the graphics system, including text. Anti-aliasing is not
+ included in GX 1.0, but we're looking at it for future versions.
+
+ Is QDGX limited to TrueType fonts?
+ ----------------------------------
+
+ Michael Wang contributes:
+
+ Just to clarify, the component of QuickDraw GX that deals with font
+ features like automatic ligature substitution is called the Line Layout
+ Manager (which I'll abbreviate as LLM), and LLM features are
+ independent of scaler technology. In other words, a Type 1 font can
+ have all of the LLM features that a TrueType font can have under
+ QuickDraw GX.
+
+ In fact, Apple and Adobe bundle a GX version of ATM with the QuickDraw
+ GX release along with a Type 1 GX version of Tekton Regular which
+ includes lots of additional glyphs and supports most of the LLM
+ features. If you are a Macintosh developer, there are beta GX versions
+ of ATM and Tekton that you can play around with on the QuickDraw GX
+ 1.0b1 release that is part of the WWDC CD.
+
+ Lawrence D'Oliveiro contributes:
+
+ One implication of GX for font installation is that Type 1 fonts no
+ longer come in "bitmap" vs "screen" versions that live in separate
+ files: under QuickDraw GX, they live in "sfnt" resources, and install no
+ differently from TrueType fonts.
+
+ As of 1 Mar 95, QuickDraw GX 1.0.1 is the current release.
+
+Subject: 2.2. Frequently Requested Mac Fonts
+
+ Greek Fonts
+ ===========
+
+ This section was constructed from a posting by John Amanatides in Jan
+ 1995.
+
+ There are three ways to get Greek out of a Mac. Approach one is to
+ simply use the Symbol font; this solution is the easiest but Symbol
+ doesn't have accents and you cannot easily exchange files with friends
+ in Greece. Approach two is go all the way and install Apple's Greek
+ system software on your Mac. It would make it identical to a machine
+ sold in Greece and is really only an option for the diehards. Approach
+ three is to just get a Greek keyboard driver and Greek typefaces. This
+ article talks mostly about approach three while it does also mention the
+ others.
+
+ First some background. Until the early '80s the Greek alphabet included
+ quite a lot of different diacritical marks. Thus if you are interested
+ in classical Greek you will need to get a polytonic version of the
+ typeface. Modern Greek now only uses accents, simplifying the use of
+ the alphabet and this is normally what you will get when you ask for a
+ Greek typeface.
+
+ There are several encodings of the Greek alphabet. ISO-8859-7 is the
+ most standard. It is an 8-bit encoding that uses the regular 7-bit
+ ASCII standard in the lower 128 positions and Greek in the upper 128.
+ Unfortunately, Apple did not use it (sigh). Apple's encoding is
+ slightly different in the upper 128 positions. All modern Greek
+ typefaces for the Mac seem to use this encoding and if you use it you
+ can exchange files with your friends in Greece (and use Greek
+ dictionaries!). If you are interested in classical Greek things become
+ a little trickier. I don't know if there is a standard but Linguist's
+ Software's (see below) encoding seems to be the most popular.
+
+ Sources of Greek Fonts for the Mac
+ ----------------------------------
+
+ Apple
+ .....
+
+ You can go all the way with Apple and get their Greek system software
+ but getting it is non-trivial. In North America the only way to get it
+ seems to be to get the "Apple Developer Mailing" from APDA. Designed
+ for developers, you get a CD mailed to you monthly. The CD contains
+ the most recent worldwide Mac system software along with a lot of other
+ stuff. It costs \$250 US and you get updates for a year. The Greek
+ system software contains TrueType versions of GrCourier, GrHelvetica,
+ GrTimes and several bitmap versions of some of Apple's other typefaces
+ along with the Greek keyboard driver.
+
+ APDA 800-282-2732 US
+ 800-637-0029 Canada
+ 716-871-6555
+
+ A second place to get Greek system software is in Greece. Apple's
+ distributor is:
+
+ Rainbow Computer S.A.
+ Elia Eliou 75
+ Neos Kosmos, Athens
+ Greece 117 44
+ 30-1-9012892 Voice
+ 30-1-9012540 FAX
+
+ Just because you have the Greek system software doesn't mean you have
+ to install the whole system; you can just take the Greek typefaces and
+ the Greek keyboard driver and use them with your current system
+ software.
+
+ Note: Linguists' Software (see below) also market version 6.0.3 of the
+ Greek operating system.
+
+ Linotype-Hell
+ .............
+
+ Linotype sells a variety of Type1 Greek typefaces in both modern and
+ polytonic versions and in a variety of weights/styles: Times,
+ Helvetica, Baskerville, New Century Schoolbook and Souvenir. The
+ easiest way to purchase them is to get Linotype's CD of locked
+ typefaces (a new one is coming out in Dec. '94). The CD costs \$49 US
+ and comes with 4 free fonts. A Greek keyboard driver comes with the
+ typefaces. Linotype can be reached at:
+
+ Linotype-Hell Company
+ 425 Oser Avenue
+ Hauppage, NY, 11788
+ USA
+ 800-633-1900
+ 516-434-3616 FAX
+
+ These typefaces are also distributed by FontShop (see below) Note: the
+ new CD works on both a Mac and a PC and when you unlock a typeface you
+ unlock for both systems.
+
+ FontShop
+ ........
+
+ FontShop is an international chain of stores which supplies a wide
+ variety of typefaces to both professionals and the rest of us. Their
+ North American address is:
+
+ FontShop Canada Limited
+ 510 Front Street West
+ Toronto, Ontario
+ Canada M5V 3H3
+ 800-363-6687
+ 416-348-0916 FAX
+
+ Monotype
+ ........
+
+ Monotype offers two Greek typefaces on their locked CD: Times New Roman
+ Greek and Arial Greek. Each typeface comes in four weights/styles.
+ Their CD lists for \$49 and you get 8 free fonts (just enough for both
+ of their Greek typefaces :-). You can reach Monotype at:
+
+ Monotype Typography Inc.
+ Suite 2630, 150 South Wacker Drive
+ Chicago, IL, 60606
+ USA
+ 800-MONOTYP (800-666-6897)
+ 312-855-9475 FAX
+
+ These typefaces are also distributed by FontShop. Note: you get a 5 CPU
+ license.
+
+ Linguist's Software
+ ...................
+
+ Linguist's Software has typefaces for over 250 world languages and
+ gives several options for those interested in Greek. First, you can
+ purchase the Greek operating system for the Mac version 6.0.3. This
+ includes GrTimes and GrHelvetica (Type 3) as well as several bit-mapped
+ system fonts. Second, you can purchase their modern Greek typefaces
+ Olympus and Philippi (Times and Helvetica clones) in four
+ weights/styles and in both Type1 and TrueType along with a keyboard
+ driver for System 7. Finally, they have their own TrueType and Type1
+ typefaces in the LaserGreek package. These are of particular interest
+ to Greek scholars since they include extra diacritics for ancient/N.T.
+ Greek. This package now includes a Uncail typeface. LaserGreek: \$99;
+ Modern Greek + keyboard driver: \$99; LaserGreek + GreekOS: \$139;
+ LaserGreek + Modern Greek + keyboard driver: \$139.
+
+ Linguist's Software
+ PO Box 580
+ Edmonds, WA 98020-0580
+ USA
+ 206-775-1130
+ 206-771-5911 FAX
+
+ Ecological Linguistics
+ ......................
+
+ Ecological Linguistics also provides typfaces for a wide variety of
+ world languages. They have a polytonic version of Times (GreekTimes)
+ in their GreekClassical package and monotonic versions of Times and
+ Helvetica (GkTimes, GkHelvetica) in four weights/styles in their
+ GreekModern package. Both the GreekClassical and GreekModern packages
+ are \$60 US each and come with a keyboard driver.
+
+ Ecological Linguistics
+ P.O. Box 15156
+ Washington, D.C., 20003
+ U.S.A.
+ 202-546-5862
+
+ MacCampus
+ .........
+
+ MacCampus of Germany provides Greek and other Eastern European
+ typefaces. The Greek typefaces come in two flavors: those that are
+ based on the modern Greek keyboard layout and those based on the Symbol
+ font layout. MacCampus provides a keyboard driver so that you can use
+ the former type on non-Greek Macs.
+
+ The typefaces available are:
+
+ Modern Greek (Greek layout): Olympia (Helvetica clone) and Tiryns
+ (Times clone) in 4 weights/styles
+
+ Classical Greek (extra diacritics, Symbol layout): Agora Times,
+ Parmenides (light, sans-serif)
+
+ MacCampus
+ C. Kempgen
+ An den Weihern 18
+ D-96135 Stegaurach
+ Germany
+ (0951) 296739
+ (0951) 296425 FAX
+
+ MacCampus typefaces are distributed by FontShop.
+
+ Font World
+ ..........
+
+ Another Greek typeface distributor is Font World. They also sell a
+ variety of Eastern European typefaces. They provide a package of
+ keyboard drivers for a variety of different world languages. The
+ modern Greek typefaces are: FW Palace GK (Palatino?), FW Baskerfield
+ GK, FW Peace GK (sans serif) & condensed version, FW Pithos GK
+ (Lithos?), FW Stencil GK, FW Textbook GK, FW Tourist GK (Souvenir) and
+ FW World GK (Times?). They come in a variety of weights/styles and go
+ for about \$100-\$200.
+
+ Font World, Inc.
+ 2021 Scottsville Road,
+ Rochester, NY 12623
+ USA
+ 716-235-6861
+ 716-235-6950 FAX
+
+ SkepsiS
+ .......
+
+ SkepsiS is a Greek publishing company that is heavily into Macs. They
+ have created and sell several nice typefaces in several weights/styles:
+ Corfu (New Century Schoolbook?), Ithaca (Souvenir?), Rhodes
+ (University?), Mykonos (Courier?), Paros (Antique Olive?), Samos
+ (modern serif), GtcFutura (Futura?), Naxos (Eurostile?), Ios (?) The
+ cost for a package containing the above is 60,000 drachmas.
+
+ SkepsiS Ltd
+ El. Benizelou 184
+ T.K. 176 75, Kallithea
+ Athens, Greece
+ 30-1-952-2086
+ 30-1-952-2088 FAX
+
+ Magenta
+ .......
+
+ Magenta is a Greek company that sells typefaces for Macs and PCs.
+ Their catalog lists over 70 typefaces with names like MgBodoni,
+ MgOptima, MgAvantGarde, etc in a variety of weights/styles. Most are
+ modern Greek but they also have a few classical typefaces. Each
+ typeface family goes for about 8,500 drachmas.
+
+ Magenta Ltd
+ Antimaxou 17
+ 115 28 Athens
+ Greece
+ 30-1-722-9292 phone/FAX
+
+ Note, I have tried to contact Magenta recently and have gotten no
+ response.
+
+ Fronteiras
+ ..........
+
+ Fonteiras is a German company that produces non-roman typefaces. They
+ have 26 Greek typefaces, display and text, both polytonic and
+ monotonic. Some of the families include clones of Dynamo, Stencil,
+ Broadway, Revue, Futura Black, Lithos, Industria, Insignia, Palatino,
+ Helvetica, Times, etc. Packages go for about \$150-\$200 US and include
+ a Greek keyboard driver. The monotonic typfaces have kerning tables and
+ some have real italics. (Most other vendors only have obliques.)
+
+ Fronteiras
+ Luisenstr. 22
+ D-60316 Franfurt
+ Germany
+ 49-069-4980498 phone/FAX
+ 100443.1305@compuserve.com
+
+ Freeware/Shareware
+ ..................
+
+ There is a free classical Greek typeface called Ismini that is available
+ on the net at:
+
+ mac.archive.umich.edu:mac/system.extensions/font/type1/ismini.cpt.hqx
+
+ Unfortunately, I don't think it uses the same encoding as Linguist's
+ Software.
+
+ Other Fonts
+ ===========
+
+ Many fonts are available at various archives. The king of Macintosh
+ font archives is mac.archive.umich.edu. On mac.archive.umich.edu, the
+ fonts are located in the following folders:
+
+ /mac/system.extensions/font/type1
+ /mac/system.extensions/font/type3
+ /mac/system.extensions/font/truetype
+
+ The following fonts are in Type 1 format for the Macintosh. Some are
+ also available in TrueType format.
+
+ * Tamil
+
+ Paladam, T. Govindram
+
+ * Hebrew
+
+ ShalomScript, ShalomOldStyle, ShalomStick, Jonathan Brecher
+
+ * Japanese
+
+ Shorai (Hirigana, with application)
+
+ * Star Trek
+
+ StarTrekClassic, Star TrekClassicMovies, StarTrekTNGCrille,
+ StarTrekTNG Titles, TNG monitors, StarFleet, Klinzai (Klingon font)
+
+ * Command-key symbol
+
+ Chicago (TrueType or bitmap, key: Ctrl-Q), Chicago Symbols
+ (Type3, key: 1), EncycloFont (Type3, key: d)
+
+ * Astrologic/Astronomic symbols
+
+ Hermetica (Type1), InternationalSymbols (Type 3, Mars and Venus
+ only), MortBats (Type3), Zodiac (bitmap)
+
+ * IBM OEM Line Drawing Characters
+
+ Try Adobe PrestigeElite or Adobe LetterGothic. They have all the
+ characters you want, but the `line draw' characters are unencoded
+ -- you will need tools to reencode the outline font itself and
+ make a new PFM metric files.
+
+ Or try IBMExtended from Impramatur Systems in Cambridge, Mass. It
+ already is encoded using IBM OEM encoding (some DOS code page).
+
+ The IBM version of Courier distributed freely under the X11
+ Consortium also contains the appropriate characters. It is
+ distributed in PC format, however. Again, the font will have to
+ be reencoded for Windows. Appropriate AFM files for this font can
+ be obtained from:
+ http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+ Many of these mac fonts are available in files that are either entitled
+ xxxx.sit or xxxx.cpt. xxxx.sit files are Stuffit archives. xxxx.cpt
+ files are Compact Pro archives. StuffitLite (shareware $25) and Compact
+ Pro (shareware $25) are available at the standard ftp sites.
+ Uncompressors for these programs (free) are also available at the
+ archive sites. Check the utilities/compression utilities folders.
+
+Subject: 2.3. Commercial Font Sources
+
+ Commercial fonts can be obtained from a number of different companies,
+ including the large font houses: Adobe, Font Haus, Font Company,
+ Bitstream, and Monotype. At these companies, fonts cost about $40 for a
+ single face, and must be purchased in packages. Adobe, Bitstream, and
+ Monotype also sell pre-designated type collections for slightly lower
+ prices.
+
+ Image Club sells a wide selection of fonts for about $50 for a 4 font
+ family.
+
+ Other, cheaper companies sell fonts of lesser quality, including
+ KeyFonts, which sells a set of 100 fonts for $50 and Casady & Green's
+ Fluent Laser Fonts, a set of 79 fonts for $99. Casady & Greene also
+ sells Cyrillic language fonts in Times, Bodoni, and Helvetica sell for
+ about $40 for each 4 font family.
+
+ Foreign language fonts, ranging from Egyptian hieroglyphics to Cyrillic
+ can be obtained from Ecological Linguistics.
+
+ Please consult the vendor list for a more complete list of vendors.
+
+Subject: 2.4. Mac Font Installation
+
+ * System 7
+
+ Install the fonts by opening the suitcase containing the bitmap
+ file and dropping the fonts into your system suitcase, located
+ inside your system folder. You will need to quit all other
+ applications before doing this. For a TrueType font, the icon for
+ the font will have a stack of "A"s in it, instead of just one.
+ Dropping it into your system suitcase will make all sizes of the
+ font available. For Postscript type 1 fonts, you also need to
+ place the printer font in the extensions folder in your system
+ folder. If you are using ATM you need to place these fonts in the
+ root level of your system folder (not inside another folder).
+ Using Suitcase, a font management utility, you can avoid
+ cluttering your system folder with printer fonts.
+
+ You can make new suitcases of fonts (generally not needed, but
+ used by those who use Suitcase) by using Font DA mover. It
+ operates the same as in system 6, except that the most recent
+ version must be used.
+
+ * System 6
+
+ Bitmap fonts can be installed using Font DA mover to move the
+ fonts, located inside suitcases, into your system. You will need
+ to restart your computer to make these fonts available. Printer
+ fonts must be placed in the system folder, not inside any other
+ folder.
+
+ Truetype fonts can be used with system 6 if you get the Truetype
+ init. Then the fonts can be installed in your system with Font DA
+ mover. Suitcase can also be used under system 6.
+
+Subject: 2.5. Mac Font Utilities
+
+ * SUITCASE
+
+ Suitcase is a nifty little system extension that lets you avoid
+ having to install fonts into your system. In system 6, it means
+ that you can avoid restarting your system every time you want to
+ install a new font.
+
+ In system 7, Suitcase lets you avoid quitting all applications
+ before making fonts available. Some programs, like Quark Xpress
+ will automatically update their font list when you open a new
+ suitcase, allowing much more flexibility in opening and closing
+ font suitcases and making different sets of fonts available.
+
+ Suitcase appears in your Apple menu in both system 7 and 6 and
+ allows you to open suitcases, as though they were files, thus
+ making the fonts contained in them accessible to programs.
+
+ In addition, when suitcase is installed, printer fonts can be
+ stored with the bitmap suitcases they correspond to, instead of
+ having to drop them into your system folder.
+
+ The most recent version of Suitcase is compatible with TrueType.
+ Suitcase is about $54 from the mail order places.
+
+ * Carpetbag
+
+ A shareware program with functionality equivalent to Suitcase.
+
+ * MASTER JUGGLER
+
+ Does similar things
+
+ * ATM
+
+ Adobe Type Manager is an Init and Control panel allows accurate
+ screen display, at any size of PostScript type 1 fonts. It's
+ function is replicated with Truetype (but for different outline
+ font format). With it installed, you can print fonts of any size
+ to non-PostScript printers. When using ATM, printer fonts must
+ either be stored with the bitmap files opened with suitcase (when
+ using Suitcase), or they must be stored in the root level of the
+ system folder (with System 7.0, printer fonts must be stored in
+ the Extension folder if you are not using Suitcase). ATM is now
+ available, with the System 7.0 upgrade, as well as directly from
+ adobe with 4 Garamond fonts.
+
+ ATM is not built into System 7.1 as previously expected. With
+ System 7.1, printer fonts must be stored in the Fonts folder if
+ you are not using Suitcase.
+
+ If you are using version 7.x prior to 7.1, the following hack
+ allows you to have a Font folder (if you don't use Suitcase):
+
+ Open the second 'DCOD' resource from the ATM 68020/030 file. Do an
+ ASCII search for the string "extn" and change it to "font" (it's
+ case sensitive). Save, close, and Reboot.
+
+ This process should work for 68000 machines using the proper ATM
+ file instead.
+
+ * Super ATM
+
+ This is a utility that will create fonts, on the fly, that match
+ the metrics of any Adobe-brand fonts you don't have. It does a
+ remarkably good job of mimicry because it uses two "generic"
+ Multiple Master typefaces, serif and sans serif to simulate the
+ appearance of the missing typefaces. (There is a 1.4 megabyte
+ database file that allows Super ATM to simulate the fonts that
+ aren't there.) You also get Type On Call (a CD-ROM), which has
+ locked outline fonts, and unlocked screen font for all but the
+ most recent faces in the Adobe Type library.
+
+ * TTconverter
+
+ A shareware accessory available at the usual archives will convert
+ Truetype fonts for the IBM into Macintosh format.
+
+ * reAdobe
+
+ Converts text (PFA) format PostScript Type 1 fonts into Mac format.
+
+ * unAdobe
+
+ Converts Mac format PostScript Type 1 fonts into text (PFA) format.
+
+ * Microsoft Font Pack
+
+ If you work with a mixture of Macs and PCs running Windows 3.1,
+ this is a good deal; 100 TrueType fonts compromising the Windows
+ 3.1 standard set and the two Font Packs for Windows. This includes
+ various display fonts, the Windows Wingdings font, and the Lucida
+ family.
+
+ A variety of programs, for example, Font Harmony, etc. will allow you
+ to change the names and ID numbers of your fonts.
+
+ Fontmonger and Metamorphosis will let you convert fonts among several
+ formats (type 1 and 3 and Truetype for the Mac and PC), as well as
+ letting you extract the font outlines from the printer fonts.
+
+Subject: 2.6. Making Outline Fonts
+
+ This is very, very difficult. Many people imagine that there are
+ programs that will simply convert pictures into fonts for them. This is
+ not the case; most fonts are painstakingly created by drawing curves
+ that closely approximate the letterforms. In addition, special rules
+ (which improve hinting, etc.) mandate that these curves be drawn in
+ specific ways. Even designing, or merely digitizing, a simple font can
+ take hundreds of hours.
+
+ Given that, there are two major programs used for font design on the
+ Macintosh, Fontographer ($280) and FontStudio ($400). These programs
+ will allow you to import scanned images, and then trace them with
+ drawing tools. The programs will then generate type 1, 3, TrueType and
+ Bitmap fonts for either the Macintosh or the IBM PC. They will also
+ generate automatic hinting. They also open previously constructed
+ outline fonts, allowing them to be modified, or converted into another
+ format.
+
+ As far as I know, there are no shareware programs that allow you to
+ generate outline fonts.
+
+Subject: 2.7. Problems and Possible Solutions
+
+ 1. Another font mysteriously appears when you select a certain font
+ for display.
+
+ This is often the result of a font id conflict. All fonts on the
+ Macintosh are assigned a font id, an integer value. When two fonts
+ have the same id, some programs can become confused about the
+ appropriate font to use. Microsoft word 4.0 used font id's to
+ assign fonts, not their names. Since id's can be different on
+ different computers, a word document's font could change when it
+ was moved from one computer to another. Other signs of font id
+ problems are inappropriate kerning or leading (the space between
+ lines of text). Some font ID problems can be resolved by using
+ Suitcase, which will reassign font ID's for you, as well as saving
+ a font ID file that can be moved from computer to computer to keep
+ the id's consistent. Font ID problems can also be solved with
+ several type utilities, which will allow you to reassign font
+ id's. Most newer programs refer to fonts correctly by name
+ instead of id number, which should reduce the frequency of this
+ problem.
+
+ 2. When using a document written in MSWord 5.0, the font mysteriously
+ changes when you switch from your computer at home to work, or
+ vice versa.
+
+ This is the result of a bug in MSWord 5.0. The MSWord 5.0 updater,
+ which can be found at the info-mac archives at sumex (in the demo
+ folder), will fix this bug.
+
+Subject: 2.8. Creating Mac screen fonts
+
+ Creating Mac screen fonts from Type 1 outlines
+ ==============================================
+
+ Peter DiCamillo contributes the following public domain solution:
+
+ BitFont is a program which will create a bitmapped font from any font
+ which can be drawn on your Macintosh. In addition to standard
+ bitmapped fonts, it works with Adobe outline fonts when the Adobe Type
+ Manager is installed, and works with TrueType? fonts. BitFont will
+ also tell you how QuickDraw will draw a given font (bitmapped, ATM, or
+ TrueType) and can create a text file describing a font and all its
+ characters.
+
+ BitFont was written using MPW C version 3.2. It is in the public
+ domain and may be freely distributed. The distribution files include
+ the source code for BitFont.
+
+ Berthold K.P. Horn contributes the following solution.
+
+ This is a commercial solution. A font manipulation package from Y&Y
+ includes:
+
+ AFMtoPFM, PFMtoAFM, AFMtoTFM, TFMtoAFM, AFMtoSCR, SCRtoAFM, TFMtoMET,
+ PFBtoPFA, PFAtoPFB, MACtoPFA, PFBtoMAC, REENCODE, MODEX, DOWNLOAD,
+ SERIAL, and some other stuff I forget.
+
+ To convert PC Type 1 fonts to Macintosh use PFBtoMAC on the outline
+ font itself; then use AFMtoSCR to make the Mac `screen font'
+ (repository of metric info). You may need to use PFMtoAFM to first make
+ AFM file.
+
+ To convert Macintosh font to PC Type 1, use MACtoPFA, followed by
+ PFAtoPFB. Then run SCRtoAFM on screen font to make AFM file. Finally,
+ run AFMtoPFM to make Windows font metric file.
+
+ Y&Y are the `TeX without BitMaps' people (see ad in TUGboat):
+
+ Y&Y makes DVPSONE, DVIWindo, and fonts, for use with TeX mostly, in
+ fully hinted Adobe Type 1 format.
+
+ Y&Y, Inc., 45 Walden Street, Concord MA 01742 USA
+
+ (800) 742-4059
+
+ (508) 371-3286 (voice)
+
+ (508) 371-2004 (fax)
+
+ Mac Screen fonts can be constructed from outline fonts using
+ Fontographer, as well.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_NeXT_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_NeXT_Info
new file mode 100644
index 0000000000..e59e68039f
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_NeXT_Info
@@ -0,0 +1,538 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: NeXT Info
+Supersedes: <font-faq-12_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:12 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 515
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-12_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48309 comp.answers:20523 news.answers:79244
+
+Archive-name: fonts-faq/part12
+Version: 2.1.5
+
+Subject: 7. NeXT Information
+
+ If you have any suggestions for this section, please forward your
+ suggestions to norm.
+
+Subject: 7.1. Tell me about NeXTstep fonts
+
+ NeXTstep fonts are Adobe Type 1 fonts stored in ASCII (PFA) format.
+ There are several rules about how fonts must be installed before they
+ work.
+
+ I'd like to thank Henry for rewriting this section.
+
+ Basic Format
+ ============
+
+ NeXTstep fonts live in one of three folders:
+
+ /NextLibrary/Fonts
+ Contains system fonts. In general, you will not install any
+ new fonts here.
+
+ /LocalLibrary/Fonts
+ Contains fonts which are accessible to every user on a system
+ or a network.
+
+ ~/Library/Fonts
+ (where ~ is your home folder) means fonts which are private to
+ a specific user.
+
+ A NeXTstep font is actually a folder containing various components of
+ the font. Components are:
+
+ * the outline font file - REQUIRED
+
+ * the font metrics (AFM) file - REQUIRED
+
+ * one or more screen font (bitmap) files - OPTIONAL
+
+ Font Folder and Font Filename Requirements
+ ==========================================
+
+ The name of the folder containing a font and the name of the font file
+ itself must follow strict rules - the names can NOT be any old name you
+ like. For a font to work correctly, the base folder and font filename
+ MUST BE THE SAME as the name of the outline font. This is usually the
+ same as the value of the FontName field in the AFM file or the value of
+ the /FontName key in the actual font itself. Suppose you have a font
+ called Headhunter. The Headhunter font must live within a folder called
+
+ Headhunter.font
+
+ within one of the three folders mentioned above. Within the
+ Headhunter.font folder, you must have the two files
+
+ Headhunter ( the outline file )
+ Headhunter.afm ( the AFM file )
+
+ If you have a bitmap file for Headhunter, it must live in a file
+
+ Headhunter.bepf ( the bitmap file )
+
+ Variations such as Bold, Italic, etc., should be their own font files
+ in their own folder. So if you have a font called Headhunter-Bold, you
+ need to create a folder called
+
+ Headhunter-Bold.font
+
+ within one of the three folders mentioned above. Within the
+ Headhunter.font folder, you must have the two files
+
+ Headhunter-Bold ( the outline file )
+ Headhunter-Bold.afm ( the AFM file )
+
+ If you have a bitmap file for Headhunter, it must live in a file
+
+ Headhunter-Bold.bepf ( the bitmap file )
+
+ For NeXTstep 1.0 ONLY, you also need to take the following steps:
+ -----------------------------------------------------------------
+
+ * If they do not already exist, create the following folders:
+
+ * ~/Library/Fonts/outline
+
+ * ~/Library/Fonts/afm
+
+ * ~/Library/Fonts/bitmap
+
+ * In each of these folders, create a symbolic link to the
+ corresponding component file in each font.
+
+ For NeXTstep 2.0 and up:
+ ------------------------
+
+ The font description is taken from the font folder itself, so you don't
+ need to do this. It may be beneficial to simply create these folders
+ and put nothing in them, but I'm not sure it matters.
+
+ Certain "old" applications which haven't upgraded to the NeXTstep 2.0
+ scheme of fonts may depend on these folders being present.
+
+ The last step is to get the system to recognize the new font(s). You
+ may have noticed the existence of three files in the Fonts folder:
+ .fontdirectory, .fontlist, and .afmcache. These are files the system
+ looks at to see which fonts exist.
+
+ The easiest way to update them is to simply start up an application and
+ open the font panel. It should recognize that the update time stamp on
+ the Fonts folder has changed, and update the files accordingly. It is
+ probably a good idea to simply delete the three above files beforehand.
+
+ You should get a message window saying "incorporating information on
+ new fonts. Please wait (this may take xx seconds)". Your new fonts
+ should be available now.
+
+ If this does not work, you can update them manually. Open up a Terminal
+ shell and go to your Fonts folder. At the prompt, type two commands:
+
+ buildafmdir
+ cacheAFMData afm (the parameter is the <afm dir>)
+
+ The new fonts will not work if the cacheAFMData command is not run, and
+ since it is an undocumented command, it is a common culprit.
+
+ [ed: the cacheAFMData step may not be required in 3.0 OS]
+
+ I believe this is true. Looks like the PasteBoard Services runs
+ cacheAFMData in 3.0.
+
+ You should now be able to see and preview your fonts in the font panel.
+
+ If you are still having problems with your font, such as the <<
+ Unusable font >> message, consult NeXTAnswers. There are some useful
+ suggestions for debugging faulty fonts there. It is also always
+ helpful to look at existing fonts to see how they are installed.
+
+ One note on the NeXTAnswers. Supposedly there are only a few discrete
+ values which are allowed to appear in the weight field of the font:
+ "Ultra Light", "Thin", "Light", "Extra Light", "Book", "Regular",
+ "Plain", "Roman", "Medium", "Demi", "Demi-Bold", "Semi-Bold", "Bold",
+ "Extra Bold", "Heavy", "Heavyface", "Black", "Ultra", "UltraBlack",
+ "Fat", "ExtraBlack", and "Obese". However, I have a few fonts where
+ this is not the case ("standard" is a common entry) and have had no
+ problems as of yet. But it would probably be wiser to be on the safe
+ side.
+
+ See below for a definitive list.
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 7.2. Tell me more about NeXTstep fonts
+
+ Outline files should be in PFA or hexadecimal ASCII format. The font
+ name should be taken either from the outline (font) file or the AFM
+ file. In both case the name is given after the word "FontName" at the
+ beginning of the file)
+
+ As a matter of fact, fonts don't strictly HAVE to be in all hexadecimal
+ ASCII format. The eexec portion of the font can be in binary if you
+ wish, and in fact some Mac->NeXTstep or PFB->NeXTstep font converters
+ simply strip off the Mac/PFB storage format headers and leave the
+ binary sections as binary.
+
+ However, if you wish to send such a font across a serial channel to a
+ PostScript printer, you will need some way to unpack the binary eexec
+ portion to seven-bit ASCII before sending the font.
+
+ Converted Fonts After Conversion
+ --------------------------------
+
+ After conversion they are just like any other freeware or shareware
+ font that you can get in NeXTstep-format from the archives. That's just
+ outline and AFM files but no bitmapped screen fonts. So small point
+ size means poor resolution on screen but they most of should print OK
+ if they are any good ( = usually made with Fontographer).
+
+ About Conversion Utilities
+ --------------------------
+
+ NeXTstep utilities
+ ..................
+
+ * unfont
+
+ You can find a package, named something like
+ pcATMfont2NeXT.tar.Z, from NeXT archives (cs.orst.edu)
+ that converts PC fonts to NeXT format (PFB -> PFA).
+
+ The most useful tool for me has been "unfont" which
+ converts the .pfb (binary outline) font to ASCII outline
+ font.
+
+ I usually use it like this
+
+ $ unfont new_font.pfb >NewFont
+
+ If the conversion was successful all I have to after that is
+ maybe to rename the font correctly and move the outline file
+ in the correct .font folder.
+
+ * Opener.app
+
+ Opener seems to be a very useful application since it can
+ open several kinds file packages on NeXTstep that are
+ common on other platforms. E.g. ".sit", ".hqx", ".zoo",
+ ".zip", ".z", etc.
+
+ I haven't used it a lot but looks very promising.
+
+ * T1utils-1.1
+
+ This is collection of command-line programs that manipulate
+ PS Type 1 fonts and one of them can also do the PFB->PFA
+ conversion (t1ascii?).
+
+ Basic unarchiving of Mac and PC files.
+
+ On your Unix machine:
+
+ xbin
+ Converts .hqx to:
+ .data
+ Rename and transfer to PC (or use opener.app on NeXT?)
+
+ .info
+ Discard
+
+ .rsrc
+ Discard
+
+ unzip
+ Converts .zip to:
+ .inf
+ Discard
+
+ .wfn
+ Discard
+
+ .pfm
+ Discard (unless it can generate a better AFM file)
+
+ everything else
+ Transfer to NeXT On a PC:
+
+ xbin
+ Converts .hqx to:
+ .data
+ Rename and transfer to PC (or use opener.app on NeXT?)
+
+ .info
+ Discard
+
+ .rsrc
+ Discard
+
+ extract -f ...
+ Converts .cpt to:
+ file with no extension
+ This is usually the outline font. Refont and transfer to
+ NeXT.
+
+ .afm
+ Transfer to NeXT.
+
+ .pfm
+ Discard (unless it can generate a better AFM file)
+
+ .bma
+ Discard if you have an AFM file.
+
+ unsit30 -eb ...
+ Converts .sit to:
+ file with no extension
+ This is usually the outline font. Refont and transfer to
+ NeXT.
+
+ .afm
+ Transfer to NeXT.
+
+ .pfm
+ Discard (unless it can generate a better AFM file)
+
+ .bma
+ Discard if you have an AFM file.
+
+ refont
+ Converts outline formats from Mac to NeXT format (PFA).
+
+ pkunzip
+ Converts .zip to:
+ .inf
+ Discard
+
+ .wfn
+ Discard
+
+ .pfm
+ Discard (unless it can generate a better AFM file)
+
+ everything else
+ Transfer to NeXT On a NeXT
+
+ Opener.app
+ Converts archive formats (.sit, .hqx, .zip) to NeXT format.
+
+ unfont
+ Converts PFB files to NeXT format.
+
+ afm
+ Converts AFM files to NeXT format AFM files (CR/LF hackery)
+
+ Installation
+ ------------
+
+ There are scripts (installfont) available that can handle the
+ installation process but here is how you do it manually.
+
+ * .font
+
+ After all that you have to create the .font folder, move the
+ outline and .afm files there and start fighting with the strangely
+ formatted .afm file. The most common problems are font name
+ mismatch between outline and AFM files (family name is incorrect
+ or too long, etc) and missing fields (ex. no ItalicAngle entry) in
+ the AFM file.
+
+ * buildafmdir AND cacheAFMData
+
+ buildafmdir puts its complains to Console but cacheAFMData put
+ them on stdout or stderr (ie. Terminal Window).
+
+ PARSE ERRORS ----------- "Parse error 10000011 ..." comes from
+ mismatch between of CharMetrics declared in the .afm and actually
+ found. I haven't been able to figure out the other strange parse
+ errors.
+
+ buildafmdir in the 3.0 release has the limitation of not being
+ able to install more that 255 fonts in any one font folder. This
+ is supposed to be fixed in 3.1.
+
+ * The Dreaded <<Unusable Font>> Message
+
+ <<Unusable Font>> appears in the font panel when you have run
+ buildafmdir and it finds things it thinks are wrong with the AFM
+ file. Errors can also be generated by parsing routines inside the
+ PasteBoard Services.
+
+ <<Unusable Font>> almost NEVER has anything to do with the font
+ itself, since buildafmdir doesn't actually look inside the font.
+ Errors in the font due to faulty conversion will likely show up at
+ the time the PostScript server actually attempts to define the
+ font or render characters from the font.
+
+ The only error I have ever seen from a converted font was the
+ results of a naive Macintosh to PFA converter, which didn't
+ understand that the POST resources in a Macintosh format Type 1
+ font do not have to be in order, nor do the POST resources all
+ have to be contiguous - they can be interspersed with other
+ resources. The results were that a comment resource ended up in
+ the middle of the eexec section of the font and the PostScript
+ interpreter threw out lots of errors.
+
+ <<Unusable Font>> almost ALWAYS occurs because there is something
+ wrong with the AFM file you installed. Here is a partial list of
+ problems that can occur with AFM files:
+
+ * Carriage-return characters (^M) at ends of lines.
+
+ This happens when you get incomplete translations from PC
+ files, which use carriage-return-line-feed combinations at
+ ends of lines.
+
+ Solution: edit away the carriage returns. Make sure the
+ lines are terminated only by line-feed characters.
+
+ * Spaces or tabs at ends of lines.
+
+ Fixed in NeXTstep 3.1.
+
+ * Missing fields.
+
+ NeXTstep DEMANDS that certain fields be present in the AFM
+ file. Required fields are: FontName, FullName, FamilyName,
+ Weight, EncodingScheme, and ItalicAngle. If any of these
+ fields are missing, you will get the <<Unusable Font>>
+ message.
+
+ Solution: fill in the required fields.
+
+ * Incorrect Weight field.
+
+ buildafmdir accepts only a certain set of values for the
+ Weight field. Acceptable values are: "Ultra Light", "Thin",
+ "Light", "Extra Light", "Book", "Regular", "Plain", "Roman",
+ "Medium", "Demi", "Demi-Bold", "Semi-Bold", "Bold", "Extra
+ Bold", "Heavy", "Heavyface", "Black", "Ultra", "UltraBlack",
+ "Fat", "ExtraBlack", and "Obese".
+
+ * Character information count mismatches.
+
+ AFM files contain several sets of information which are
+ introduced by a "Startxxxxx nnn" line where the xxxxx is the
+ name of the section (such as StartCharMetrics) and nnn is the
+ purported number of lines of information of this type to
+ follow. Sad to say, many many AFM files supplied by vendors
+ and others are such that the actual number of lines of data
+ do not match the number stated on the Startxxxxx line. When
+ this error occurs in the AFM file, buildafmdir emits a Parse
+ Error message to the console and the font will be marked
+ unusable. The parse error messages from buildafmdir is of
+ the form:
+
+ Parse error nnnnnnnn xx yy
+
+ where nnnnnnnn is the error number, xx is the number of lines
+ of information claimed to exist, and yy is the number of
+ lines actually read. The nnnnnnnn are are:
+
+ 10000011 mismatch in the StartCharMetrics section
+ 10000012 mismatch in the StartTrackKern section
+ 10000013 mismatch in the StartKernPairs section
+ 10000014 mismatch in the StartComposites section
+ 10000015 mismatch in a composite character specification
+
+ I have converted many fonts from the Berkeley Macintosh User
+ Group CD ROM and fully half of the supplied AFM files are
+ incorrect.
+
+ * Other AFM file errors.
+
+ Parse error numbers 10000001 through 10000010 means some kinds of
+ syntax errors in the AFM data file. Any of these errors mean that
+ the AFM file is truly hosed.
+
+Subject: 7.3. Porting fonts to the NeXT
+
+ Porting PC/Unix Type 1 Fonts
+ ============================
+
+ You must have the .pfb and .afm files
+
+ A PC Adobe font is stored in binary format, so the first step is to
+ convert it to ascii.
+
+ There are a couple of utilities out there which can do this. I think
+ t1utils can do it, and there is a nice utility called pcATMfont2Next
+ which has a couple of tools to do this (unfont and pfb2ps). Look for
+ the file pcATMfont2Next.tar.Z; it is available on many ftp sites.
+
+ Also, since NeXTstep run on Unix, there is the customary problem of
+ converting the CRs (carriage returns) that PCs use to the LFs
+ (Linefeeds) that Unix uses. The easiest way to do this is to use tr to
+ delete the octal for the CR character from both the .afm and outline
+ file. The command to do this is:
+
+ tr -d '\015' < inputfile > outputfile
+
+ The unfont program will do this automatically when it converts the .pfb
+ file, but pfb2ps does not. I'm not sure if t1utils' utility does or not.
+
+ Once you have the outline file, you can go ahead and install it by the
+ process outlined above.
+
+ Otto J. Makela (otto@jyu.fi) posted a terrific cshell script to
+ comp.fonts, which automates just about everything for you. It converts
+ the .pfb to ASCII format, extracts the name from the FontName field,
+ creates the font folder, copies in the component files with the correct
+ name, and runs buildafmdir and cacheAFMData when done. A newer version
+ of this script is now available from the standard NeXT step archives
+ (Sonata, etc.).
+
+ Porting Mac Type 1 Fonts
+ ========================
+
+ A variety of programs and scripts exist to convert Macintosh format
+ Type 1 fonts to UNIX format. Their ability to do a complete job
+ varies. Common traps which naive font converters fall into are:
+
+ * not dealing with Macintosh POST which are out of order.
+
+ * not dealing with Macintosh POST which are interspersed with other
+ resources.
+
+ * not dealing at all with POST Type 4 resources where the font
+ program starts in resource fork of the file but the remainder of
+ the data is in the data fork.
+
+ Most naive converters we've looked at have this problem. This
+ means that most Type 3 fonts won't convert at all.
+
+ * not dealing with MacBinary headers.
+
+Subject: 7.4. Font availability
+
+ [ The archive site at sonata.purdue.edu seems to have disappeared. ]
+
+Subject: 7.5. Why can I only install 256 fonts on my NeXT?
+
+ Included to NS3.0 there's a new 'buildafm'-routine (for non-NeXTers:
+ 'buildafm' is a shell script which announces a new font to the
+ computer) at /usr/bin/buildafmdir. The new one only allows to install
+ about 256 fonts. Running the new 'buildafmdir' to install a new font
+ surpresses every font above this number. Workaround: Re-install the
+ 'old buildafmdir' from NS2.1 at /usr/bin/buildafmdir and everything
+ should be fine!
+
+ (thanks to: Rob Parkhill and d'Art Computers/Germany d'art)
+
+ [ed: and my thanks to Borris Balzer for sending this to me]
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_OS_2_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_OS_2_Info
new file mode 100644
index 0000000000..745535ca00
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_OS_2_Info
@@ -0,0 +1,420 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: OS/2 Info
+Supersedes: <font-faq-9_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:34:55 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 397
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-9_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48305 comp.answers:20519 news.answers:79240
+
+Archive-name: fonts-faq/part9
+Version: 2.1.5
+
+Subject: 4. OS/2 Information
+
+ [ed: Except as otherwise noted, the entire OS/2 section of the
+ comp.fonts FAQ List is derived from the "Draft OS/2 Font FAQ" posted by
+ David J. Birnbaum.]
+
+ This section if the FAQ is Copyright (C) 1993 by David J. Birnbaum.
+ All Rights Reserved. Reproduced here by permission.
+
+ [ed: Since this section of the FAQ is wholly derived from David's
+ document, some sections contain information repeated elsewhere in the
+ comp.fonts FAQ.]
+
+ David Birnbaum's Introduction
+ =============================
+
+ 4 June 1993
+
+ A couple of weeks ago I posted an inquiry to comp.fonts,
+ comp.os.os2.misc, and the OS2-L ListServ concerning some apparent
+ peculiarities in the way OS/2 handles font files. These "peculiarities"
+ actually reflect regular, systematic differences in OS/2, Windows, and
+ DOS font handling, which are not conveniently described in end-user
+ documentation. This posting is intended to spare others some of the
+ confusion I encountered as a result of this paradigm shift.
+
+ This is the first (draft) distribution of this document and corrections
+ and suggestions are welcome. I am grateful to Henry Churchyard, Marc L.
+ Cohen, Bur Davis and Kamal Mansour for helpful discussions; they are
+ not, of course, responsible for any misinterpretation I may have
+ inflicted on their comments.
+
+Subject: 4.1. Preliminaries
+
+ Character: an informational unit consisting of a value (usually a byte)
+ and roughly corresponding to what we think of as letters, numbers,
+ punctuation, etc.
+
+ Glyph: a presentational unit corresponding roughly to what we think of
+ as letters, numbers, punctuation, etc.
+
+ Character vs glyph: Glyph and character are not necessarily the same;
+ the character <a> may be mapped to a Times Roman Lower Case <a> glyph
+ in one font and to a Helvetica Lower Case <a> glyph in another font.
+ Change of glyphs normally means a change in style of presentation,
+ while change in characters normally means a change in information.
+ There are gray areas and the definitions provided above are general,
+ approximate, and imprecise.
+
+ Character set: an inventory of characters with certain assigned values.
+ ASCII is a 7-bit character set that specifies which "character cell"
+ (byte value) corresponds to which informational unit.
+
+ Code Page: essentially synonymous with character set.
+
+ Font: A collection of glyphs. A specific font may be isomorphic with a
+ specific character set, containing only glyphs corresponding to
+ characters in that set, with these glyphs mapped to the same byte
+ values as the characters they are intended to represent. PostScript
+ fonts often contain additional (unmapped) characters. Most importantly,
+ PostScript fonts may sometimes be remapped by an operating environment,
+ which is what leads to the disorienting cross-environment mismatch that
+ spurred my original posting.
+
+ Fonts may be bitmapped or outline in format; a bitmapped format
+ corresponds to a particular size and weight for a particular device or
+ device resolution, while a single outline font is used to generate
+ multiple sizes as needed. Within an outline font system, different
+ weights (bold, semibold, italic, etc.) may be encoded as separate font
+ resources (separate outline files used to generate the glyphs) or may
+ all be generated from a single outline (slanting characters to make
+ "italics," fattening them for "bold," etc.).
+
+Subject: 4.2. Fonts under DOS
+
+ I used a large assortment of fonts under DOS for intricate multilingual
+ work. My setup at that time consisted of a library of bitmapped fonts
+ that could be sent to my HP LaserJet II printer, as well as a set of
+ fixed-size, fixed-width screen fonts that were supported by my Hercules
+ Graphics Card Plus (not the same as Hercules Graphics; the "Plus"
+ included an ability to store 3072 screen glyphs and display any of
+ these together, while standard character-mode displays were normally
+ limited to 256 or 512 such entities).
+
+ Using XyWrite as a word processor, I would enter a "Mode" command to
+ change fonts and character sets simultaneously; this would make
+ different sets of screen glyphs available at the keyboard and would
+ insert a font-change command for my printer into the text stream. The
+ "Mode" and font-change commands were not displayed on the screen. The
+ result was not WYSIWYG, since I was limited to fixed-width screen
+ display and since I had far more printer glyphs available than the 3072
+ limit imposed by my video card; I used a brightness attribute to
+ indicate bold, I used the same screen font for different sizes of
+ printer fonts, etc. This worked and worked well, in that I could see
+ (for example) Russian, Greek, English, Polish, and other characters
+ simultaneously on the screen and I could print documents combining them.
+
+ Architecturally, what was going on was that the character sets (code
+ pages) and fonts were entirely isomorphic and were hard- coded. If I
+ put a particular Russian letter into cell 246 of my screen and printer
+ fonts, that character was always there, and any strategy that would let
+ me access this cell (remapped keyboards, numeric keypad) was guaranteed
+ always to find the same character.
+
+Subject: 4.3. Windows
+
+ I recently began using PostScript fonts in Windows with AmiPro as my
+ word processor. These fonts came with printed cards indicating the
+ glyph mappings; I could look at the card and it would tell me that a
+ specific character lived in cell 246, and if I entered Alt-0246 at the
+ numeric keypad that glyph would appear on the screen. If I loaded the
+ font into Fontographer for Windows, these glyphs would be arrayed in
+ cells according to the map provided by Adobe with the fonts.
+ Fontographer also revealed that these fonts had other, "unmapped"
+ glyphs assigned to cells above 255.
+
+ Given what appeared to be a hard correspondence among what I saw in
+ Fontographer, what was printed in Adobe's maps, and what was displayed
+ when I entered something at the keyboard, I naively assumed that
+ PostScript fonts were operating much like my bitmapped fonts under DOS.
+ There were some obvious differences, the primary one being that glyphs
+ of different sizes were all drawn from the same font resource files
+ under PostScript, but it appeared as if a glyph lived in a certain cell.
+
+Subject: 4.4. Differences between Windows and OS/2
+
+ This assumption was incorrect; PostScript fonts can be subdivided into
+ two types, one of which observes hard and invariant encodings similar
+ to those that apply to my bitmapped fonts, while the other represents a
+ completely different font mapping strategy. This difference became
+ apparent only when I attempted to share PostScript fonts between
+ Windows and OS/2 and got some unexpected results.
+
+ A PostScript font under Windows involves two files, a PFB (PostScript
+ Font Binary) file, which contains the PostScript instructions needed to
+ draw each glyph and some mapping information, and a PFM (Printer Font
+ Metrics) file, which encodes width and kerning information. A
+ PostScript font under OS/2 also uses the same PFB file, but instead of
+ the PFM file it uses an AFM (Adobe Font Metrics) file. The AFM and PFM
+ files contain much of the same basic information (although the AFM file
+ is somewhat more complete); the most important differences are in
+ format (AFM is plain text, PFM is binary) and use (OS/2 uses AFM,
+ Windows uses PFM).
+
+Subject: 4.5. Installation under Windows and Win-OS/2
+
+ The OS/2 2.0 Font Palette tool (see below for changes to be introduced
+ with 2.1) by default installs fonts (both PFB and AFM files) into the
+ "\os2\dll" directory. Win-OS/2 by default installs PFB files into
+ "\psfonts" and PFM files into "\psfonts\pfm". These defaults can be
+ changed; since OS/2 and Win-OS/2 use the same PFB files, the user can
+ save disk space by allowing these to be shared (through installing into
+ the same directory, e.g., install OS/2 fonts into the "\psfonts"
+ directory instead of "\os2\dll".) Note that fonts must be intalled and
+ removed through the Font Palette; if you copy, move, or delete a font
+ file without using the Font Palette, the system configuration files are
+ not updated and all hell breaks loose.
+
+ Deleting fonts from Win-OS/2 causes the system to update the win.ini
+ file to remove references to the font, but does not delete any files
+ physically. Deleting fonts from the OS/2 Font Palette updates the
+ os2.ini configuration file and physically deletes the AFM and PFB files
+ from the disk. This means that if you are sharing PFB files between
+ OS/2 and Win-OS/2, you can delete a Win-OS/2 font without hurting
+ native OS/2 operations, since the PFB reamins installed where OS/2
+ thinks it is. But if you delete an OS/2 font using the Font Palette,
+ the PFB file is erased from the disk even though the win.ini file is
+ not updated, so that Win-OS/2 thinks it is still there.
+
+Subject: 4.6. FontSpecific PostScript Encoding
+
+ Every PFB file contains an "encoding vector"; this is a plain text line
+ embedded near the head of the PFB file. Encoding vectors are of two
+ types: AdobeStandardEncoding and everything else. Adobe usually uses
+ the label "FontSpecific" for fonts that are not encoded according to
+ AdobeStandardEncoding, and I use it as a cover term here for any such
+ font.
+
+ If you look at the readable plain text information at the head of a
+ FontSpecific type font, it includes a range of text that begins:
+
+ /Encoding 256 array
+
+ followed by a bunch of lines, each of which includes a number (which
+ corresponds to a cell in the font layout) and the name of the glyph
+ that lives in that cell. The unreadable binary data below this array
+ specification lists the name of each glyph and the PostScript
+ instructions for how the glyph is to be drawn. There may be PostScript
+ code for drawing glyphs that are not included in the mapping array, but
+ only glyphs mentioned in the array specification are available to
+ applications.
+
+ FontSpecific type fonts are comparable to the bitmapped fonts I used
+ under DOS. Each character physically is assigned to a specific cell
+ within the font file and operating environments are not allowed to
+ remap these. The glyph in cell 246 will be the same in both Windows and
+ OS/2.
+
+Subject: 4.7. AdobeStandardEncoding
+
+ AdobeStandardEncoding is a specific mapping of certain glyphs to
+ certain cells; in this respect it resembles FontSpecific encoding.
+ Because it is standardized, the array is not spelled out in the PFB
+ file; the line
+
+ /Encoding StandardEncoding def
+
+ tells Adobe Type Manager (ATM, either the Windows and Win-OS/2 version
+ or the native OS/2 version) that the encoding is "standard," and the
+ environments are expected to know what this standard is without having
+ the array spelled out in each font file.
+
+ Although AdobeStandardEncoding is a real mapping, there is an
+ importance difference between it and various FontSpecific mappings:
+ operating environments are expected to remap AdobeStandardEncoding
+ fonts according to their own requirements. That is, although
+ AdobeStandardEncoding does assign glyphs to cells, no operating
+ environment actually uses these assignments and any environment remaps
+ the glyphs before rendering them. Confusion arises because Windows and
+ OS/2 remap such fonts in different ways.
+
+Subject: 4.8. AdobeStandardEncoding under Windows (and Win-OS/2)
+
+ An AdobeStandardEncoding font under Windows is remapped according to a
+ character map (code page) that MicroSoft calls Windows ANSI (can other
+ code pages be installed in Windows?). This determines which character
+ resides in which cell and the font is remapped so that glyphs and
+ characters will correspond. Since Fontographer for Windows is a Windows
+ application, it displays glyphs not in the cells in which they live
+ according to AdobeStandardEncoding, but in the cells to which they get
+ reassigned under the remapping to Windows ANSI. There is nothing
+ explicit in the PFB file that associates these characters with the
+ specific cells in which they appear under Windows.
+
+Subject: 4.9. AdobeStandardEncoding under OS/2
+
+ OS/2 operates within a set of supported code pages; two system- wide
+ code pages are specified in the config.sys file and an application is
+ allowed to switch the active code page to any supported code page (not
+ just these two). DeScribe, for example, currently operates in code page
+ (CP) 850, which includes most letters needed for western European Latin
+ alphabet writing. CP 850 does not contain typographic quotes, en- and
+ em-dashes, and other useful characters. It does contain the IBM
+ "pseudographics," which are useful for drawing boxes and lines with
+ monospaced fonts.
+
+ When the user inputs a value (through the regular keyboard or the
+ numeric keypad), the application checks the active CP, looks up in an
+ internal table the name of the character that lives in that cell within
+ that CP, and translates it into a unique number that corresponds to one
+ of the 383 glyphs supported by OS/2 (the union of all supported code
+ pages). This number is passed to PM-ATM (the OS/2 ATM implementation),
+ which translate the glyph number into the glyph name that PostScript
+ fonts expect and searches the font for that name. The system never
+ looks at where a glyph is assigned under the AdobeStandardEncoding
+ array; rather, it scans the font looking for the character by name and
+ gives it an assignment derived from the active code page. This is the
+ remapping that OS/2 performs on AdobeStandardEncoding type fonts.
+
+ As a result, a situation arises where, for example, <o+diaeresis> is
+ mapped to cell 246 under Windows ANSI but to cell 148 under CP 850.
+ Using the identical PFB file, this glyph is accessed differently in the
+ two operating environments.
+
+Subject: 4.10. Consequences for OS/2 users
+
+ If your font has a FontSpecific encoding, there are no unexpected
+ consequences; the same glyphs will show up at the same locations in
+ both Windows (Win-OS/2) and native OS/2. Regardless of what the active
+ code page is, if the font has a FontSpecific encoding OS/2 goes by cell
+ value; a specific glyph is hard-coded to a specific cell and OS/2 will
+ give you whatever it finds there, even if what it finds disagrees with
+ what the active code page would normally predict. In other words,
+ FontSpecific encoding means "ignore the mapping of the active code page
+ and rely on the mapping hard-coded into the font instead."
+
+ If your font has an AdobeStandardEncoding encoding, the following
+ details obtain:
+
+ 1) The same PFB file may have glyphs that are accessible in one
+ environment but not another. For example, if DeScribe thinks it is
+ operating in CP 850, there is no access to typographic quotes, even if
+ those do occur in the PFB file and even if Windows can find them in the
+ same exact font file. DeScribe could switch code pages, but if the
+ application isn't set up to do so (and DeScribe currently isn't), those
+ characters are absolutely inaccessible to the user.
+
+ 2) If the active code page includes a character that isn't present in
+ the font, OS/2 has to improvise. For example, AdobeStandardEncoding
+ fonts do not normally include the IBM pseudographics, yet the user who
+ inputs the character value for one of these sends the system off to
+ look for it. As described above, OS/2 first checks the active font for
+ the glyph name that corresponds to that character and, if it finds it,
+ displays it. If the glyph isn't found, OS/2 looks to the system Symbol
+ font. This is not reported back to the user in DeScribe; if I have
+ Adobe Minion active (AdobeStandardEncoding, no information anywhere in
+ the font files for pseudographics) and input a pseudographic character,
+ DeScribe tells me it is still using Adobe Minion, even though it has
+ fetched the character it displays and prints from the Symbol font, a
+ different font resource file.
+
+Subject: 4.11. Advice to the user
+
+ OS/2's code page orientation provides some advantages, in that it
+ separates the character set (code page) mapping from the encoded font
+ mapping. The main inconvenience isn't a loss of function, but a
+ disorientation as users become accustomed to the new paradigm.
+
+ If you need a glyph that you know is in your PFB file but that isn't in
+ the active code page (and if you can't change code pages within your
+ application), you can't get at it in OS/2 without tampering with the
+ font files. To tamper, you can use font manipulation tools to
+ redesignate the PFB file as FontSpecific ("Symbol" character set to
+ Fontographer). If you then map the glyphs you need into one of the
+ lower 256 cells (with some limitations), they will be accessible in all
+ environments. The Fontographer manual does not explain what the
+ "Symbol" character encoding label really does, it just tells you not to
+ use it except for real symbol fonts. In fact you should use it for any
+ font that will not correspond in inventory to the code page supported
+ by your application, which means any non-Latin fonts.
+
+ You do not have to recode all your fonts, and you wouldn't normally
+ want to do so, since Fontographer hinting is not nearly as good as
+ Adobe's own hand-tuning and regenerating a font regenerates the hints.
+ All you have to do is make sure you have one FontSpecific type font
+ installed that includes your typographic quotes, etc. for each typeface
+ you need. Within DeScribe, you can then write a macro that will let you
+ switch fonts, fetch a character, and switch back, thereby allowing you
+ to augment any group of fonts with a single, shared set of typographic
+ quotes (or whatever) that you put in a single FontSpecific font.
+ Alternatively, OS/2 also supports CP 1004, which does contain
+ typographic quotes and other characters used for high-quality
+ typography, but the user may not be able to convince an application to
+ invoke this code page if it was not designed to do so.
+
+ You can have any number of FontSpecific fonts installed, which means
+ that there is a mechanism for dealing with unsupported character sets
+ (code pages).
+
+ You can also tinker with the font files to try to trick the operating
+ system. For example, using Fontographer or other utilities, you can
+ change the name assigned to a glyph description within the PFB file. If
+ you want to use AdobeStandardEncoding and you want to see a specific
+ glyph at a specific cell when DeScribe thinks it's using CP 850, you
+ have to make sure that the name assigned to the description of that
+ glyph is what DeScribe expects to find. OS/2 doesn't care whether, say,
+ <o+diaeresis> really looks like <o> with two dots over it, as long as
+ it bears the right name.
+
+ This second approach is obviously far more complex and provides much
+ more opportunity for error. Its advantage is that OS/2 does not support
+ case conversion and sorting (other than in machine order) for
+ unsupported code pages, since these operations depend on character
+ names. Keeping supported names from supported code pages while changing
+ the artwork is one way to maintain order and case correspondences while
+ increasing the range of glyphs actually supported. I have not
+ experimented with this approach, since the use I would get out of the
+ adding functionality (over the FontSpecific encoding approach) is not
+ worth the amount of effort required.
+
+Subject: 4.12. OS/2 2.1 and beyond
+
+ OS/2 2.1 will change some aspects of font handling. First, OS/2 2.0
+ GA+SP has a bug that can cause OS/2 to crash when an AFM file with more
+ than 512 kern pairs is read. This is fixed in 2.1. (This bug is
+ separate from a design limitation in MicroSoft Windows that causes
+ large kern tables to be read incorrectly. This problem is still under
+ investigation; watch this space for a report.)
+
+ Fonts in 2.1 will be installed by default into the "\psfonts" directory,
+ so that they will normally be shared with Win-OS/2 fonts. (The user will
+ still be able to specify a directory; all that will change is the
+ default). The user will also be able to instruct the Font Palette not to
+ delete font files when fonts are uninstalled, so as to avoid clobbering
+ a Win-OS/2 font by removing it from native OS/2 use through the Font
+ Palette (although the default will still be to delete the physical font
+ files).
+
+ OS/2 will stop using AFM files and will replace these with OFM files, a
+ binary metrics file (different from PFM) that OS/2 will compile from
+ the AFM file during font installation. This will speed font loading,
+ since the system will not have to parse a plain text metrics file.
+ Additionally, the OS/2 PostScript printer driver used to install its
+ own, large font files, but will now use the OFM and PFB files, thereby
+ saving 50k-200k of disk space per installed font outline.
+
+ IBM's long-term goal is to replace the 383-entity inventory of
+ supported glyphs with Unicode. This is very much a long-term goal and
+ there is not even a hint of when it might become available. It has its
+ own problems, stemming from the fact that Unicode is essentially a
+ character standard and glyph and character inventories may differ is
+ assorted ways, but it will be a significant step in the proverbial
+ right direction.
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Sun_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Sun_Info
new file mode 100644
index 0000000000..dc39d65580
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Sun_Info
@@ -0,0 +1,176 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Sun Info
+Supersedes: <font-faq-11_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:06 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 153
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-11_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48307 comp.answers:20521 news.answers:79242
+
+Archive-name: fonts-faq/part11
+Version: 2.1.5
+
+Subject: 6. Sun Information
+
+ Someone mailed a file of Sun-related font tips. Unfortunately, I cannot
+ find the file. If you have any suggestion for this section (or if you
+ are the person that mailed me the other list), please forward your
+ suggestions to norm.
+
+ [ Note: much of this information is obsolete, based on the
+ SunOS4/Solaris2.1 server. The Solaris 2.3 and later servers are based
+ on the standard X11R5 server but with Display PostScript added, so you
+ can do Type 1 in the "normal" way (fontdir+mkpsres) ]
+
+Subject: 6.1. Fonts Under Open Windows
+
+ The following information regarding fonts under Open Windows was donated
+ by Liam R.E. Quin from the Open Windows FAQ.
+
+Subject: 6.1.1. Does OpenWindows support Type 1 PostScript fonts?
+
+ Type 1 fonts are supported starting with the NeWSprint 2.0 and Solaris
+ 2.0 (OpenWindows 3.0.1) releases.
+
+ There are also 57 F3 format fonts supplied with OpenWindows which are
+ fully hinted. Documentation on the F3 font format and the F3 font
+ interpreter, TypeScaler, is available from Sun.
+
+Subject: 6.1.2. Improving font rendering time
+
+ Although the Sun type renderer (TypeScaler) is pretty fast, it's not as
+ fast as loading a bitmap. You can pre-generate bitmap fonts for sizes
+ that you use a lot, and you can also alter and access the font cache
+ parameters. If you have a lot of memory you might want to increase
+ the font cache size.
+
+ $ psh -i
+ Welcome to X11/NeWS Version3 <--- psh will say this at you
+ currentfontmem = % type this line ...
+ 300 % ... my server was using 300 Kbytes
+ 1024 setfontmem
+ % Just to check:
+ currentfontmem =
+ 1024
+
+ See pp. 328ff of the NeWS 3.0 Programmer's Guide. You need to say psh
+ -i so that the PostScript packages are loaded - see the psh man page.
+
+ You could also add the following line to your $HOME/.openwin-init file
+ to perform this task every time you start OpenWindows:
+
+ echo 1024 setfontmem | psh -i > /dev/null 1>&2
+
+Subject: 6.1.3. Making bitmap fonts for faster startup
+
+ Sun supports the F3 scalable outline format. These descriptions are
+ stored in .f3b files. The makeafb program is used to create a bitmap
+ font at a particular size which is stored in a .afb file, which is an
+ Adobe ASCII format for font bitmaps. X11/NeWS really prefers a binary
+ format though for speed and other reasons, so convertfont is used to
+ "compile" the font into a font binary or .fb file.
+
+ Once this is done, X11/NeWS needs to understand the relationship between
+ the .f3b file and all the bitmaps which are based on it. Thus, the
+ bldfamily program makes these correlations and stores the data in the
+ font family or .ff file.
+
+ bldfamily also builds a global list of all fonts stored in the working
+ directory, writing the results out to the file Families.list. If one
+ wishes to create font aliases, these can be added to the Synonyms.list
+ file by hand and bldfamily will then add them to Families.list for you.
+ X11/NeWS uses Families.list to construct the font list it advertises
+ to applications.
+
+ To go from F3 to BDF, use makeafb to generate a bitmap font in .afb
+ format. Then use one of convertfont's many options to change to this
+ to .bdf format and from there it should be clear.
+
+ $ mkdir $HOME/myfonts
+ $ cd $HOME/myfonts
+ $ makeafb -20 -M $OPENWINHOME/lib/fonts/Bembo.f3b
+ Creating Bembo20.afb
+ $ convertfont -b Bembo20.afb
+ Bembo20.afb->./Bembo20.fb
+ Chars parameter greater than number of characters supplied.
+ $ ls
+ Bembo20.afb Bembo20.fb Synonyms.list
+ $ bldfamily
+ * Bembo ./Bembo.ff (Encoding: latin)
+ cat: ./Compat.list: No such file or directory
+ $ xset +fp `pwd`
+ $ xset fp rehash
+
+ If you want the server to see your new font directory every time, add
+ this directory to your FONTPATH environment variable in one of your
+ start-up files, e.g. .login or .profile.
+
+Subject: 6.1.4. Converting between font formats (convertfont, etc.)
+
+ You can also use F3 fonts with an X11 server, by converting them to a
+ bitmap (X11 bdf format) first. Your license restricts use of these
+ fonts on another machine, and unless you have NeWSPrint you shouldn't
+ use them for printing. Having said all that... you can use makeafb
+ and convertfont to generate bdf files that you can compile with
+ bdftosnf or bdftopcf.
+
+ Use mftobdf (from the SeeTeX distribution) to convert TeX PK fonts to
+ X11 BDF format, which you can then use with either X11 or OpenWindows.
+
+Subject: 6.1.5. Xview/OLIT fonts at 100 dpi
+
+ There aren't any. More precisely, the various text fonts, such as
+ Lucida Typewriter Sans, are available at 100 dpi, and in fact are
+ scalable under OpenWindows. The glyph fonts used to be bitmaps, which
+ don't scale very well, but starting with OpenWindows 3.2, the OpenLook
+ UI glyph fonts are provided in scalable format as well.
+
+Subject: 6.2. Where can I order F3 fonts for NeWSprint and OpenWindows?
+
+ 600 F3 fonts are available for unlocking from Printer's Palette, a CD
+ available with NeWSprint 2.0.
+
+ In addition, F3 fonts are available from the following sources:
+
+ Linotype AG Linotype Company
+ Mergenthaler Allee 55-75 425 Oser Avenue
+ 6236 Eschborn Germany Hauppague, NY 11788
+ 49/(61 96) 4031 (800) 336-0045
+ FAX 011/49/6196-982185 FAX 516-434-2055
+ attn: F3 Font Production attn: F3 Font Production
+
+ Monotype Plc. Monotype Typography
+ Salfords Redhill RH1 5JP 53 W. Jackson Boulevard Suite 504
+ England Chicago, IL 60604
+ 44/(737) 765959 (800) 666-6893
+ FAX 011/44/737-769243 FAX (312) 939-0378
+ attn: F3 Font Production attn: F3 Font Production
+
+ U R W U R W
+ Harksheider Strasse 102 One Tara Boulevard Suite 210
+ D2000 Hamburg Germany Nashua, NH 03062
+ 49/(40) 606050 (603) 882-7445
+ 49/(40) 60605148 (603) 882-7210
+ attn: F3 Font Production attn: F3 Font Production
+
+ Bigelow & Holmes Autologic
+ P. O. Box 1299 1050 Rancho Conejo Boulevard
+ Menlo Park, CA 94026 Newbury Park, CA 91320
+ 415/326-8973 (800)235-1843, or (805)498-9611 in CA
+ FAX (415) 326-8065 FAX (805) 499-1167
+ attn: F3 Font Production attn: F3 Font Production
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Unix_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Unix_Info
new file mode 100644
index 0000000000..a2b9c6295f
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Unix_Info
@@ -0,0 +1,84 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Unix Info
+Supersedes: <font-faq-10_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:00 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 61
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-10_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48308 comp.answers:20522 news.answers:79243
+
+Archive-name: fonts-faq/part10
+Version: 2.1.5
+
+Subject: 5. Unix Information
+
+ See also the 'utilities' section for more information. Most of the
+ utilities described in that section run under Unix.
+
+ The bulk of this section was contributed by Johannes Schmidt-Fischer in
+ Jun 1993.
+
+ Unix Font Formats
+ =================
+
+ Most printers attached to Unix hosts are PostScript printers. As a
+ consequence, most Unix users are also using PostScript fonts. If you
+ are not using a PostScript printer, you need a front-end, like
+ GhostScript, to convert the PostScript into a format compatible with
+ your printer.
+
+ There is no Unix specific Postscript Type 1 format. The most often used
+ (and most easily usable) format is Adobe's PFA format. The other often
+ used format is PFB format. The PFB format is more compact (by about
+ 50%), but in order to use it you need make sure that your font
+ downloading tools are prepared to convert PFB to PFA on fly.
+
+ Postscript Type 3 fonts are no problem, they can be handled the same
+ way as Type 1 fonts.
+
+ Most Unix tools expect to get character metric information from AFM
+ files. You may have difficulty using fonts collected off of the 'Net
+ if they do not include AFM files
+
+ Font Installation
+ =================
+
+ Application
+ -----------
+
+ It depends. (Well, what did you expect me to say? ;-)
+
+ Printer using an ExitServer
+ ---------------------------
+
+ Convert PFB fonts into PFA format if necessary and then send them to
+ printer inside a wrapper like so:
+
+ %!PS-Adobe-2.0 ExitServer Job
+ serverdict begin 0 exitserver % 0: substitute your password
+ ... % font in PFA-format
+ %%EOF
+
+ Or include them directly in your print job:
+
+ %!PS-Adobe-2.0
+ ... % font in PFA-format
+ ... % other initialisation
+ %%Page: 1 i % beginning of your job...
+ ... % ...
+ %%EOF
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Utilities b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Utilities
new file mode 100644
index 0000000000..576662e47c
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Utilities
@@ -0,0 +1,542 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Utilities
+Supersedes: <font-faq-16_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:35 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 519
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-16_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48313 comp.answers:20527 news.answers:79248
+
+Archive-name: fonts-faq/part16
+Version: 2.1.5
+
+Subject: 11. Utilities Information
+
+ I have just started collecting information about font utilities. I
+ will gladly add any information that you can pass my way. Please send
+ your submissions to norm.
+
+ I would appreciate it if you could include a paragraph or so of
+ description and the appropriate site/filename for retrieval.
+
+Subject: 11.1. How do I convert AFM files to PFM files
+
+ You can get afm2pfm and pfm2afm files from
+ http://www.ora.com/homepages/comp.fonts/FAQ-tools.html.
+
+Subject: 11.2. PS2PK
+
+ PS2PK is a utility for converting Type1 postscript fonts into TeX PK
+ files. The source code is distributed and it has been compiled for
+ both *nix boxes and MS-DOS based machines.
+
+ Here is the original announcement:
+
+ Ps2pk-1.2 available
+ -------------------
+ (June 1992)
+
+ Version 1.2 of ps2pk is now available on:
+ ftp.urc.tue.nl (address: 131.155.2.79)
+ directory: /pub/tex
+ files: ps2pk12.README ( 1k) This file
+ ps2pk12.tar.Z (391k) Sources
+ ps2pk386.zip (232k) MSDOS executables
+ utopia.tar.Z (342k) Adobe Utopia font family
+ courier.tar.Z (207k) IBM Courier font family
+
+ For people having difficulties in handling UNIX `.tar.Z' format I
+ have made some UNIX tools (only executables) available in:
+ directories: /pub/unixtools/dos
+ /pub/unixtools/vms
+
+ See the system specific TARZ file for some help.
+
+ Ftp.urc.tue.nl can not handle E-mail requests. But sites are free
+ to put the ps2pk12 stuff on any server that can.
+
+ When do you need ps2pk?
+ =======================
+
+ Ps2pk is a tool that converts a PostScript type1 font into a corres-
+ ponding TeX PK font. The tool is especially interesting if you want to
+ use fully hinted type1 fonts in your DVI previewer (instead of the
+ unhinted type1 fonts currently used in GhostScript) or on a printer
+ that has no PostScript interpreter.
+
+ In order to use the ps2pk generated fonts your driver and previewer need
+ to support virtual fonts. The reason is that PostScript fonts and TeX
+ fonts do have a different font encoding and handle ligatures in a
+ different way. With virtual fonts the PostScript world (encoding +
+ ligatures) can be mapped to the old style TeX world on which the current
+ plain macro packages still are based (despite the fact that TeX3.0 can
+ handle 8bits).
+
+ It is also possible to use the ps2pk generated PK fonts directly
+
+Subject: 11.3. TeX Utilities
+
+ There are many TeX font utilities. For TeX related questions, I direct
+ you to comp.text.tex or the Info-TeX mailing list. I will happily list
+ any utilities here that the comp.fonts public feels should be present.
+ I am listing MetaFont because it is the obvious font-specific component
+ of TeX and PKtoSFP because it allows anyone to use PS2PK to create
+ LaserJet softfonts.
+
+ Liam R. E. Quin is the original author of the MetaFont section. It has
+ been hacked at a bit by norm to make it fit the tone of the comp.fonts
+ FAQ. Assume that norm is responsible for any errors, not Liam.
+
+ MetaFont
+ ========
+
+ About MetaFont:
+ ---------------
+
+ Metafont is a programming language for describing fonts. It was
+ written by Donald Knuth and is documented in
+
+ Computers & Typesetting/C: The METAFONTbook
+ Knuth, Donald E.
+ Addison Wesley, 1986
+ ISBN 0-201-13445-4, or 0-201-13444-6 (soft cover)
+ Library access: Z250.8.M46K58, or 686.2'24, or 85-28675.
+
+ A font written in MetaFont is actually a computer program which, when
+ run, will generate a bitmap (`raster') for a given typeface at a given
+ size, for some particular device.
+
+ What do you need in order to use the fonts:
+ -------------------------------------------
+
+ You cannot print the MetaFont fonts directly (unless you want a listing
+ of the program, that is). Instead, you must generate a bitmap font and
+ use that to print something.
+
+ If you are using TeX, the sequence of steps is something like this:
+
+ MF to MetaFont to GF
+ Convert a MetaFont program into a bitmapped font. Also produces a
+ TFM file.
+
+ MF to MetaFont to TFM
+ Covnert a MetaFont program into a TFM file. Also produces a
+ GF bitmapped font.
+
+ GF to GFtoPK to PK
+ Convert a GF bitmapped font into a compressed PK font.
+
+ TEX + TFM to TeX to DVI
+ Produce a device independent output file.
+
+ DVI + PK to dvi driver to output format
+ Produce a device-specific output file (or preview).
+
+ The above steps are idealized. In reality, you have to make sure that
+ the fonts get installed in the correct places and you may have to
+ adjust description files, etc. The friendly folks on comp.text.tex can
+ probably get it staightened out for you if you can't find a local guru.
+
+ If you are not using TeX, it's almost impossible to predict. At some
+ point in the above sequence, you'll insert some other conversion
+ program and proceed differently. Here, for example, is how you might
+ use TeX fonts with WordPerfect and a LaserJet printer.
+
+ PK to PKtoSFP to SFP
+ Convert a TeX PK file into an HP LaserJet softfont.
+
+ SFP to SFP2Auto to TFM
+ Make HP AutoFont Tagged Font Metric file.
+
+ SFP + HP AutoFont TFM to PTR to Installed in WP
+ Install the new font in WordPerfect.
+
+ Use WordPerfect as you normally would.
+
+Subject: 11.4. MFPic
+
+ MFpic is a macro package for including pictures in TeX documents. The
+ idea behind this package is to have Metafont do the actual drawing, and
+ store the pictures in a font that TeX can include in the document. The
+ macros have been designed so that the user should never have to learn
+ Metafont to use these macros--the TeX macros actually write the
+ Metafont file for you.
+
+Subject: 11.5. fig2MF
+
+ Briefly, fig2MF uses the mfpic macros to create formatted, commented MF
+ code from the fig graphics language. This means that programs like xfig
+ can be used as interactive font creation tools. I wrote fig2MF so that
+ I could portably illustrate TeX documents, but I suppose one could use
+ it to design letterforms as well.
+
+ The package consists of a single C source code file, modified mfpic
+ macros, documentation, and sample fig files. It is available at the
+ shsu archives.
+
+Subject: 11.6. GNU Font Utilities
+
+ Here is a brief description of the programs included:
+
+ * imageto extracts a bitmap font from an image in PBM or IMG format,
+ or converts the image to Encapsulated PostScript.
+
+ * xbfe is a hand-editor for bitmap fonts which runs under X11.
+
+ * charspace adds side bearings to a bitmap font.
+
+ * limn fits outlines to bitmap characters.
+
+ * bzrto converts a generic outline font to Metafont or PostScript.
+
+ * gsrenderfont renders a PostScript outline font at a particular
+ point size and resolution, yielding a bitmap font.
+
+ * fontconvert can rearrange or delete characters in a bitmap font,
+ filter them, split them into pieces, combine them, etc., etc.
+
+ * imgrotate rotates or flips an IMG file.
+
+ We need volunteers to help create fonts for the GNU project. You do not
+ need to be an expert type designer to help, but you do need to know
+ enough about TeX and/or PostScript to be able to install and test new
+ fonts. Example: if you know neither (1) the purpose of TeX utility
+ program `gftopk' nor (2) what the PostScript `scalefont' command does,
+ you probably need more experience before you can help.
+
+ If you can volunteer, the first step is to compile the font utilities.
+ After that, contact me [ed: Karl Berry] (karl@gnu.ai.mit.edu). I will
+ get you a scanned type specimen image. The manual explains how to use
+ these utilities to turn that into a font you can use in TeX or
+ PostScript.
+
+ You can get the source by ftp from any GNU archive site.
+
+ You can also order tapes with GNU software from the Free Software
+ Foundation (thereby supporting the GNU project); send mail to
+ gnu@prep.ai.mit.edu for the latest prices and ordering information, or
+ retrieve the file DISTRIB from a GNU archive.
+
+ This is Info file compfont.info, produced by Makeinfo-1.55 from the
+ input file FAQ.texinfo.
+
+Subject: 11.7. Font Editors
+
+ * Editors for BDF fonts
+
+ There is a bdf font editor that comes with HP/Apollo workstations.
+ It's called 'edfont'. It's not the best but it works.
+
+ Gary reports:
+
+ The standard X distribution for X11R5 contains "xfed", which
+ allows you to play with BDF fonts. "xfedor" has a more elaborate
+ user interface, and is available on most contrib directories.
+
+ The last time I tried:
+
+ "xfedor" couldn't handle BDF files with more than 256 characters.
+
+ "xfed" aborts if the BDF file contains a COMMENT line with no other
+ text. The workaround is to edit the BDF file, to put text after
+ the word COMMENT. A single blank space is sufficient. For some
+ reason, the standard BDF files included in the X release contain
+ blank spaces on the otherwise empty COMMENT lines. It was
+ probably easier to add the space to the COMMENT lines of every BDF
+ file than it was to fix the lex code for xfed. :-)
+
+ * Editors for PK fonts
+
+ The GNU font utilities include an X-based editor called Xbfe which
+ edits bitmapped fonts under X.
+
+ Eberhard Mattes' emTeX includes PKedit.
+
+Subject: 11.8. The T1 Utilities
+
+ This is a snippet from the README file for I. Lee Hetherington's
+ t1utils package:
+
+ t1utils is a collection of simple type-1 font manipulation programs.
+ Together, they allow you to convert between PFA (ASCII) and PFB
+ (binary) formats, disassemble PFA or PFB files into human-readable
+ form, reassemble them into PFA or PFB format. Additionally you can
+ extract font resources from a Macintosh font file (ATM/Laserwriter).
+
+Subject: 11.9. Where to get bitmap versions of the fonts
+
+ There are archives containing the bitmaps of many of these fonts at
+ various sizes and resolutions. The fonts must have been generated for
+ the correct print engine: e.g. write-white or write-black. The
+ archives generally hold only the sizes used by TeX. These are
+ `magstep' sizes, and are not exact point sizes. It is probably better
+ to generate them from the Metafont sources yourself if you can.
+
+ The best place to look for raster fonts was almost certainly:
+ mims-iris.waterloo.edu
+
+ but it isn't any more, the fonts have all gone. Let me know if you
+ find them elsewhere. Most people seem to have moved to using
+ PostScript fonts or Bitstream ones instead now.
+
+ Some other sites are:
+
+ ftp.cica.indiana.edu
+ mac.archive.umich.edu
+ ftp.shsu.edu
+ ftp.tex.ac.uk
+ ftp.dante.de
+
+ The occasional posting of ftp sites to comp.misc and comp.archives
+ lists these and several other sites.
+
+Subject: 11.10. Converting between font formats
+
+ Conversions to and from pbm and pk format were posted to comp.text.tex
+ and to alt.sources on the 9th of August, 1990 by Angus Duggan. The
+ program is pbmtopk, and there are also at least two patches.
+
+ Chris Lewis' psroff package includes a program to go from pk both to
+ the HP LaserJet and to PostScript.
+
+ John McClain <ophelp@tamvenus.bitnet> has some conversion programs for
+ various graphics formats to/and from pk files.
+
+ A PC program, CAPTURE, turns HPGL files into PK format, US$130 from
+ Micro Programs Inc., 251 Jackson Ave., Syosset, NY 11791 U.S.A.
+
+ Metaplot can take pen-plotter files and prouce metafont files. Note:
+ Pat Wilcox is no longer at Ohio State.
+
+ Kinch Computer Company sell .pk fonts derived from PostScript fonts.
+ Kinch Computer Co., 501 S. Meadow St.Ithaca, NY 14850 U.S.A.
+ telephone: +1 607 273 0222; fax: +1 607 273 0484
+
+Subject: 11.11. Getting fonts by FTP and Mail
+
+ If you are using ftp, you will need either the name of the host or the
+ Internet number. For example, to connect to ftp.ora.com, listed as
+ ftp: ftp.ora.com [198.112.208.11] you will need to type something like
+
+ ftp ftp.ora.com
+
+ If that doesn't work, try using the number:
+
+ ftp 198.112.208.11
+
+ If that doesn't work, on Unix systems you can use nslookup (it's
+ usually /usr/etc/nslookup) to find the host number - it might have
+ changed. Type the entire host name, and after a few seconds nslookup
+ will give you the address. Of course, if you have nslookup installed,
+ the first form will probably work...
+
+ Once you have connected, you will need to go to the appropriate
+ directory, lists its contents, and retrieve the files.
+
+ Most of the machines listed here run Unix, and you use "ls" and "cd" to
+ list files and to change directories. On machines that run VMS, you
+ will have to put square brackets around directory names, like [this].
+
+ Remember that although Metafont sources are text files, pk fonts are
+ not ASCII, and you will have to use binary mode for them. In general,
+ use text mode for README files and *.mf files, and binary mode for
+ other font files. Files ending in .Z are compressed binary files - you
+ will need to use binary mode, and then uncompress the files when you
+ get them.
+
+ There is an ftp-by-mail BITNET service, BITFTP, for BITNET users.
+
+ Before getting large files by mail, please remember to get permission
+ from all intervening sites. Ask your site administrator, who can send
+ mail to Postmaster at each site on the way if necessary.
+
+Subject: 11.12. MetaFont to PostScript Conversion
+
+ There are (I believe) three programs that perform this task. At least
+ one of them is called "mf2ps". If you have any more information about
+ these tools, please let me know.
+
+ Chang Jin-woong reports that he found the "mf2ps" package with Archie.
+ It is written by Shimon Yanai <yanai@israearn.bitnet> and Daniel M.
+ Berry <dberry@cs.technion.ac.il>. The source programs are written in
+ Pascal.
+
+ MetaFog, a commercial conveter by Richard Kinch, is available on request
+ to TrueTeX owners.
+
+Subject: 11.13. How to use Metafont fonts with Troff
+
+ If, when you run troff, you get the message `typesetter busy', you have
+ the original Ossanna-troff, also called otroff. Chris Lewis has a
+ package which will let you use TeX fonts with troff - it's called
+ psroff, and comes with documentation.
+
+ ftp: gatekeeper.dec.com (16.1.0.2) pub/misc/psroff-3.0
+ ftp: ftp.cs.toronto.edu [128.100.1.105] pub/psroff-3.0/*
+
+ If, when you run troff, you get something like this:
+
+ x T 300
+ x res 300 1 1
+
+ you have ditroff. This is sometimes called titroff or psroff. In this
+ case, you will probably need to do the following:
+
+ 1. convert the font to your printer's format
+
+ 2. generate a width table for the font
+
+ 3. add the font to the DESC file for the appropriate device
+
+ 4. arrange for troff to download the font
+
+ 5. tell troff about the font by running `makedev DESC' in the
+ right place.
+
+ If, when you run troff, you get something like this:
+
+ X hp(SCM)(CM)(AF)(AD) 300 1 1
+ Y P default letter 2550 3300 0 0 90 90 2460 3210
+
+ you have sqtroff:
+
+ 1. convert the font to your printer's format
+
+ 2. generate a width table for the font
+
+ 3. add the font to the DESC file for the appropriate device
+
+ 4. put the font in the appropriate raster directory
+
+ 5. tell sqtroff about the font by running `sqmakedev DESC' or
+ `sqinstall'.
+
+ In each case, you should be able to get help from your vendor.
+
+ Note that Chris Lewis' psroff package has software to make width tables
+ for troff from pk files.
+
+Subject: 11.14. PKtoBDF / MFtoBDF
+
+ From the SeeTeX distribution, programs to help previewers under X11.
+ They convert TeX PK files into X11 BDF fonts (which can be further
+ converted into one or more server native formats).
+
+Subject: 11.15. PKtoPS
+
+ Included in the psroff distribution, this utility converts PK fonts
+ into PostScript fonts (bitmaps, I presume). If you have any more
+ information about these tools, please let me know.
+
+Subject: 11.16. PKtoSFP / SFPtoPK
+
+ Convert fonts from TeX PK format to HP LaserJet softfont (bitmap)
+ format.
+
+Subject: 11.17. PostScript to MetaFont
+
+ ps2mf started out as a way of creating bitmaps via MF for TeX. Only,
+ when I had just finished it, Piet Tutelaers came with ps2pk. This was a
+ far superior way runtime-wise. He uses the IBM X11-R5 fontutilities
+ library, which is extremely ugly code. But, it works. So, to generate
+ bitmaps, I suggest everyone use ps2pk.
+
+ To generate a MF outline description, ps2mf is *the* tool. Yannis
+ Haralambous has just started a project where he wants to create
+ meta-ized fonts for MF from Postscript descriptions. ps2mf does the
+ basic conversion. This project wants to revive the use of MF for it is
+ a truly beautiful program with enormous possiblities.
+
+ The following information comes from the README file for ps2mf:
+
+ This is pfb2mf. It is a copyleft program. See the file COPYING for more
+ details. I suggest that for the translation of Type-One to readable
+ PostScript you use I. Lee Hetherington's Type-1-Utils. You can find
+ these somewhere on obelix.icce.rug.nl in pub/erikjan.
+
+ If you find any bugs, please do report.
+
+ If you have any complaints, please do report.
+
+ Now for some info about the different stages. This package contains
+ four programs:
+
+ * pfb2pfa
+
+ * pfa2chr
+
+ * chr2ps
+
+ * ps2mf
+
+ pfb2pfa
+ =======
+
+ pfb2pfa will decompress an IBM (!) Postscript type 1 fontfile into
+ readable and downloadable hexadecimal data.
+
+ The resulting file still contains two layers of encryption:
+
+ * eexec encryption
+
+ * charstring encryption
+
+ pfa2chr
+ =======
+
+ pfa2chr will do an eexec-decryption of a readable hexadecimal font file
+ to a fontfile with encrypted charstrings.
+
+ chr2ps
+ ======
+
+ chr2ps will perform a charstring-decryption of a font file with
+ encrypted charstrings to fontfile with postscript commands for type 1
+ fonts.
+
+ With a "-" as filename, these programs will read from <stdin> and write
+ to <stdout>. This way you can pipe the results, as in:
+
+ pfb2pfa garmnd - | pfa2chr - - | chr2ps - garmnd
+
+ This will create a garmnd.ps from garmnd.pfb without explicitely
+ creating the intermediate files.
+
+ These previous stages can be replaced by (when using Lee Hetherington's
+ type-1-utils):
+
+ t1disasm garmnd.pfb garmnd.ps
+
+ ps2mf
+ =====
+
+ This last stage will convert to a MetaFont program with the use of the
+ corresponding .afm file and a mapping configuration file. It can
+ convert to an ordinary form with Bezier controlpoints. It can also
+ generate a curl specification. For this last option specifify -C.
+
+Subject: 11.18. Mac Bitmaps to BDF Format
+
+ I [ed: who?] have posted a program which I hacked together for
+ extracting all NFNT and FONT resources from a MacBinary form of a
+ standard Mac file and dumping the fonts as Adobe BDF files. It has only
+ been compiled and tested on a Sun system to date. It can be fetched
+ from METIS.COM, /pub/mac2bdf.c.
+
+ I wrote this tool to be able to use Mac Bitmaps under X Windows and
+ OpenWindows (which take Adobe BDF format files).
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_Vendor_List b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Vendor_List
new file mode 100644
index 0000000000..b862f72394
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_Vendor_List
@@ -0,0 +1,835 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: Vendor List
+Supersedes: <font-faq-17_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:40 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 812
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-17_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48314 comp.answers:20528 news.answers:79249
+
+Archive-name: fonts-faq/part17
+Version: 2.1.5
+
+Subject: 12. Vendor Information
+
+ Type/Font Vendors
+ =================
+
+ The following list is based on information from Masumi Abe, Norm Walsh
+ and many others. I (Don Hosek) have been calling vendors and attempting
+ to make sure information is up to date. I have removed a number of
+ vendors who do not sell fonts. Fonts bundled with applications (e.g.,
+ the bitmap fonts which are part of Quicken) are not considered enough
+ to merit inclusion in the list. Also, a number of the vendors on the
+ list actually were selling various printing software but no fonts per
+ se and were likewise removed. Finally, some companies seem to have
+ disappeared, most likely gone out of business. I've indicated the
+ verification date of any information which appears on the list. I would
+ appreciate aid in contacting those companies which are listed as
+ unverified (particularly companies outside the US). Please send updates
+ and corrections to me at dhosek@pitzer.edu
+
+ Achtung Entertainment TrueType (shareware) for Macs, 300+
+ 508 N. College Ave. #215 fonts. HyperCard demo disk $3.00
+ Bloomington, IN 47404 (refundable/order)
+ no phone number
+
+ ADH Software (Mac)
+ P.O. Box 67129
+ Los Angeles, CA 90067
+
+ Adobe Systems Incorporated : Type 1 (Mac, PC)
+ 1585 Charleston Rd. : Originals, designs licensed from
+ P.O. Box 7900 : Linotype, Monotype, Berthold, and
+ Mountain View, CA 94039-7900 : others
+ (415) 961-4400
+ (800) 344-8335
+ Verified: 16 Feb 1994
+
+ Agfa Division, Miles Inc. : Type 1 Truetype, (PC, Mac),
+ 90 Industrial Way : Intellifont (PC), Compugraphic
+ Wilmington, MA 01887 : typesetter fonts. Originals,
+ (800) 424-TYPE : fonts licensed from Adobe.
+ (508) 657-0232
+ FAX: (508) 657-8568
+ Verified: 17 Feb 1994
+
+ Allotype Typographics : Downloadable Fonts (Mac)
+ 1600 Packard Rd. Suite #5 Kadmos (Greek)
+ Ann Arbor, MI 48104 Czasy & Szwajcarskie
+ (313) 663-1989 Demotiki
+
+ Alphabets, Inc. : Type 1, TrueType (PC, Mac)
+ P.O. Box 5448 : New and licensed designs
+ Evanston, IL 60204-5448
+ (800) 326-8973
+ (708) 328-2733
+ Verified: 9 Feb 1994
+
+ Alphatype Corp.
+ 220 Campus Dr., Suite 103
+ Arlington Heights, IL 60004
+ (708) 259-6800
+
+ Altsys Corporation, : FONTastic Fonts,
+ 269 West Renner Road, : Fontographer Fonts (Mac)
+ Richardson,
+ Texas 75080.
+ (214) 680-2060.
+
+ Artworx Software Co. (Mac)
+ 1844 Penfield Rd. Hebrew Typefaces
+ Penfield, NY 14526
+ (716) 385-6120
+ (800) 828-6573
+
+ Architext, Inc. (HP/IBM)
+ 121 Interpark Blvd. Suite 1101
+ San Antonio, TX 78216
+ (512) 490-2240
+
+ Asiagraphics Technology Ltd. (Mac)
+ 9A GreatMany Centre Chinese, Japanese, Korean, Thai
+ 109 Queen's Road East
+ Wanchai, Hong Kong
+ (5) 8655-225
+ Fax: (5) 8655-250
+ Modem: (5) 865-4816
+
+ Autologic, Inc. (Mac)
+ 1050 Rancho Conejo Blvd.
+ Newbury Park, CA 91320
+ (805) 498-9611
+
+ Azalea Software, Inc.
+ PO Box 16745
+ Seattle WA 98116-0745 USA
+ 800 48-ASOFT 206 932.4030 206 937.5919 FAX
+ azalea@igc.org
+
+ Bear Rock Technologies,
+ 4140 Mother Lode,
+ Shingle Springs,
+ California 95682-8038.
+ (916) 672-0244
+
+ Berthold of North America
+ 7711 N. Merrimac Avenue
+ Niles, IL 60648
+ (708) 965-8800
+
+ Bitstream, Inc.
+ Athenaeum House
+ 215 First St.
+ Cambridge, MA 02142
+ (617) 497-6222
+ (800) 237-3335
+
+ A representative of Bitstream sent the following correction to me.
+
+ Bitstream offers:
+
+ **1100 PostScript Type 1 fonts for the Mac & PC. (These can
+ be ordered direct from Bitstream or thru several resellers.)
+ ** Bitstream Type Treasury - the Bitstream Type Library for
+ the Mac (Type 1 format) on CD ROM.
+
+ ** Bitstream Type Essentials-a series of 4 Typeface Packages
+ for PC & Mac that were selected to work well for different
+ jobs (Letters, Memos & Faxes; Newsletters, Brochures &
+ Announcements; Spreadsheets, Graphs & Presentations;
+ Headlines).
+
+ **Bitstream Typeface Packages for the PC - 52 packages (most
+ with 4 faces each) that include a total of over 200 faces,
+ with mutiple font formats in each package (Bitstream Speedo,
+ Type 1, Bitstream Fontware)
+
+ ** Bitstream TrueType Font Packs 1 & 2 for Microsoft Windows
+ ** Bitstream PostScript Font Packs 1 & 2 for the PC **
+ Bitstream FaceLift for Windows ** Bitstream FaceLift for
+ WordPerfect - both are font scaling/font management
+ utilities.
+
+ ** Bitstream MakeUp for Windows - a type manipulation/
+ special effects program.
+
+ ** Bitstream Li'l Bits - a new product line of novelty fonts
+ in TrueType format for Windows 3.1. The first release began
+ shipping last week and includes The Star Trek Font Pack, The
+ Flintstones Font Pack and The Winter Holiday Font Pack.
+
+ We offer OEM customers an extensive range of non-latin type
+ (as you have noted in the current listing), but these faces
+ are not currently available to individual end-users.
+
+ We also offer font-scaling and rasterizing technology to OEM
+ customers.
+
+ Blaha Software/Janus Associates : Big Foot (Mac) (HP/IBM)
+ 991 Massachusetts Ave.
+ Cambridge, MA 02138
+ (617) 354-1999
+
+ Blue Sky Research : Type 1 (Mac)
+ 534 SW Third Avenue, #816 : Computer Modern in PostScript
+ Portland, OR 97204
+ (800) 622-8398
+
+ Carter & Cone
+
+ Casady & Greene, Inc. : Fluent Fonts, Fluent Laser Fonts (Mac)
+ 26080 Carmel Rancho Blvd. #202 Russian/Ukranian/Bulgarian/Serbian
+ P.O. Box 223779 Cyrillic, Greek, Hebrew, Kana, Polish
+ Carmel, CA 93922 Glasnost
+ (408) 484-9228
+ (800) 331-4321 -------------no longer valid
+ (800) 851-1986 (California)-no longer valid
+
+ Caseys' Page Mill (Mac)
+ 6528 S. Oneida Court
+ Englewood, CO 80111
+ (303) 220-1463
+
+ Castle Systems : (Truetype, Type1) (Mac, IBM)
+ 1306 Lincoln Avenue : Revivals of art deco faces,
+ San Ragael, CA 94901-2165 : calligraphy, variations of
+ (415) 459-6495 : existing designs
+
+ Century Software (MacTography) font developer for MacTographyc
+ 702 Twinbrook Parkway : LaserFonts (Mac)
+ Rockville, MD 20851
+ (301) 424-1357
+
+ Callifonts
+ P.O. Box 224891
+ Dallas, TX 75222
+ (214) 504-8808
+
+ Coda Music Software
+ 1401 E. 79th St.
+ Mineapolis, MN 55425-1126
+ (612) 854-1288
+ (800) 843-1337
+
+ Compugraphic Corporation (Mac) (HP/IBM)
+ Type Division
+ 90 Industrial Way
+ Wilmington, MA 01887
+ (800) 622-8973 (U.S.)
+ (800) 533-9795 (Canada)
+
+ Computer EdiType Systems (HP/IBM)
+ 509 Cathedral Parkway, Ste. 10A
+ New York, NY 10025
+ (212) 222-8148
+
+ Computer Peripherals, Inc. : JetWare (HP/IBM)
+ 2635 Lavery Ct. #5
+ Newbury Park, CA 91320
+ (805) 499-5751
+
+ Computer Prod. Unlimited (Mac)
+ 78 Bridge St.
+ Newburgh, NY 12550
+ (914) 565-6262
+
+ Coniglio Communications
+ 124 Woodside Green #2B
+ Stamford, CT 06905-4918
+ (203) 975-8111
+ coniglio@aol.com; citycenter@aol.com
+
+ Conographic Corp. (Mac) (HP/IBM)
+ 17841 Fitch
+ Irvine, CA 92714
+ (714) 474-1188
+
+ Corel Systems Corp. (HP/IBM)
+ 1600 Carling Ave.
+ Ottawa, Ontario, CANADA KIZ 7M4
+ (613) 728-8200
+
+ Data Transforms (HP/IBM)
+ 616 Washington St.
+ Denver, CO 80203
+ (303) 832-1501
+
+ Devonian International software Co. (Mac)
+ P.O. Box 2351 Cyrillic
+ Montclair, CA 91763
+ (714) 621-0973
+
+ Digi-Fonts (HP/IBM)
+ 528 Commons Drive Greek, Cyrillic
+ Golden, Colorado 80401
+ (303) 526-9435
+ Fax: (303) 526-9501
+
+ Digital Type Systems (DTS) (HP/IBM)
+ 38 Profile Circle
+ Nashua, NH 03063
+ (603) 880-7541
+
+ Dubl-Click Software, Inc. : World Class Fonts (Mac)
+ 9316 Deering Ave.
+ Chatsworth, CA 91311
+ (818) 700-9525
+
+ Ecological Linguistics (Mac)
+ P.O. Box 15156 Cyrillic, Greek
+ Washington, DC 20003
+ (202) 546-5862
+
+ The Electric Typographer : Type 1 and TrueType (Mac & PC)
+ 2216 Cliff Dr. : Original designs
+ Santa Barbara, CA 93109
+ (805) 966-7563
+ Verified: 9 Feb 1994
+
+ EmDash : EmDash Fonts (Mac)
+ P.O. Box 8256
+ Northfield, IL 60093
+ (312) 441-6699
+
+ The Font Company
+ 12629 N. Tatum Boulevard
+ Suite 210
+ Phoenix, AZ 85032
+ (602) 996-6606
+
+ The Font Factory (HP/IBM)
+ 2400 Central Parkway
+ Ste. J-2
+ Houston, TX 77092
+
+ FontCenter (HP/IBM)
+ 509 Marin St., #121
+ Thousand Oaks, CA 91360
+ (805) 373-1919
+
+ Font FunHouse CD-ROM (PC/Mac)
+ Wayzata
+ PO Box 807
+ Grand Rapids, Minnesota 55744
+ (800) 735-7321
+
+ FontHaus North America (United States)
+ 1375 King's Hwy East
+ Fairfield, CT 06430
+ (800) 942-9110 or (203) 367-1993
+ (203) 367-1860 Fax
+
+ FontHaus UK (Faces Ltd.)
+ 44-127-638-888
+ 349 Yorktown Road
+ College Town, Camberley
+ Surrey GU15 4PX
+ UK
+
+ FontHaus Australia (Lasermaster Aus. Pty. Ltd.)
+ 61-3-747-9301
+ #31 Rosina Drive
+ Melton, Victoria 3337
+ Australia
+
+ FontHaus France (Signum Art)
+ 33-1-48-89-6046
+ Fax: 33-1-48-89-6045
+ 94 avenue Victor Hugo
+ 94100 Saint Maur des Fosses
+ France
+
+ FontHaus Germany (Elsner & Flake)
+ 49-40-39-88-3988
+ Friedensallee 44
+ 22765 Hamburg
+ Germany
+
+ FontHaus Sweden (FontBolaget)
+ 46-8-16-81-00
+ Tulegatan 15 A
+ 113 53 Stockholm
+ Sweden
+
+ FontHaus is a manufacturer of typefaces and a licensed reseller for
+ Adobe, Monotype, Bitstream, Elsner+Flake, Giampa Textware,
+ Treacyfaces, Panache Graphics, and others around the world.
+
+ FontHaus discounts most Adobe fonts up to 40% off list price, and
+ have CD-ROM discs available so you can buy individual fonts instead
+ of entire families. All their fonts are available in Macintosh Type
+ 1; most are also available in PC format; and a growing number are in
+ TrueType format. In addition, some type manufacturers support other
+ platforms through thier CD-ROM font libraries (i.e. Monotype for Mac,
+ PC, or NeXT). Contact them regarding availability for the fonts and
+ formats you want.
+
+ FontHaus ships internationally and also has several agents overseas,
+ although these agents may not have everything available as the main
+ office here in the US.
+
+ Rhyscon Systems (Canada)
+ PO Box 245 Clarkson PO
+ Mississauga Ontario L51 3Y1
+ 416 278 2600
+ 416 278 3298 Fax
+
+ TypoGabor (France)
+ 5, rue de 8 Mai 1945
+ 92586 Clichy (Paris)
+ 33 1 4739 6600
+ 33 1 4739 0638 Fax
+
+ Elsner+Flake Fontinform GmbH (German)
+ Friedensallee 44
+ D-22765 Hamburg
+ 49 40 3988 3988
+
+ Signus Limited (Britain)
+ South Bank TechnoPark
+ 90 London Road
+ London SE1 6LN
+ 71 922 8805
+ 71 261 0411 Fax
+
+ Font Bolajet (Sweden, Finland, Norway)
+ Kungstengaten 18
+ 113 57 Stockholm
+ 46.8.16.81.00
+
+ Font World (Mac)
+ 2021 Scottsville Rd. Cyrillic, Hebrew
+ Rochester, NY 14623-2021
+ (716) 235-6861
+
+ Genny Software R&D (Mac)
+ P.O. Box 5909
+ Beaumont, TX 77706
+ (409) 860-5817
+
+ Gradco Systems Inc.
+ 7 Morgan
+ Irvine, CA 92718
+ (714) 770-1223
+
+ Handcraftedfonts Co.
+ Box 14013
+ Philadelphia, PA 19122-0013
+ Tel/Fax: 215-634-0634
+
+ Our fonts are licensed to Monotype Typography, ITC DesignPalette,
+ International TypeFounders, Precision Type and Phil's Fonts.
+
+ Hewlett-Packard (HP/IBM)
+ P.O. Box 15
+ Boise, ID 83707
+ (208) 323-6000
+
+ ICOM Simulations, Inc.
+ 648 S. Wheeling Rd.
+ Wheeling, IL 60090
+ (312) 520-4440
+ (880) 877-4266
+
+ Image Club Graphics, Inc. : (Mac & PC)
+ 729-24th Ave. SE
+ Calgary, AB
+ T2G 5K8
+ Canada
+ (800) 661-9410
+ (403) 262-8008 (Canada)
+
+ Image Processing Systems :Turbofonts (HP/IBM)
+ 6409 Appalachian Way, Box 5016
+ Madison, WI 53705
+ (608) 233-5033
+
+ Invincible Software (Mac)
+ 9534 Burwick
+ San Antonio, TX 78230
+ (512) 344-4228
+
+ Kabbalah Software
+ 8 Price Drive
+ Edison, NJ 08817
+ (908) 572-0891
+ (908) 572-0869 Fax
+
+ Hebrew fonts for PC and Mac. While I am part owner, so I am biased,
+ we have been reviewed in the October 27 1992 issue of PC Mag as
+ having high-quality fonts.
+
+ Keller Software (HP/IBM)
+ 1825 Westcliff Dr.
+ Newport Beach, CA 92600
+ (714) 854-8211
+
+ Kensington Microware Ltd. (Mac)
+ 251 Park Ave. S
+ New York, NY 10010
+ (212) 475-5200
+
+ Kingsley/ATF Type Corp. (Mac)
+ 200 Elmora Ave.
+ Elizabeth, NJ 07202
+ (201) 353-1000
+ (800) 289-TYPE
+
+ Laser Technologies International : Lenord Storch Soft Fonts
+ 15403 East Alondra Blvd. (HP/IBM)
+ La Mirada, CA 90638
+ (714) 739-2478
+
+ LaserMaster Corp. : LM Fonts (HP/IBM)
+ 7156 Shady Oak Rd.
+ Eden Prairie, MN 55344
+ (612) 944-9330
+ (800) LMC-PLOT
+ Fax: (612) 944-0522
+
+ LeBaugh Software Corp : LeFont (HP/IBM)
+ 2720 Greene Ave.
+ Onaha, NE 68147
+ (800) 532-2844
+
+ Letraset USA : LetraFont (Mac)
+ 40 Eissenhower Dr.
+ Paramus, NJ 07653
+ (201) 845-6100
+ (800) 634-3463
+
+ Linguists' Software, Inc. (Bitmap, Type 1, Truetype) (Mac, IBM)
+ P.O.Box 580 Fonts for numerous alphabets. Not all
+ Edmonds, WA 98020-0580 fonts available in all languages.
+ (206) 775-1130 They support ~50 languages.
+ Fax: (206) 771-5911
+ Verified: 16 Feb 1994
+
+ Linotype Company (Mac)
+ 425 Oser Ave.
+ Hauppauge, NY 11788
+ (800) 842-9721 (US)
+ (516) 434-2706 (FAX)
+
+ MacTography
+ 326-D North Stonestreet Ave.
+ Rockville, MD 20850
+ (301) 424-3942
+
+ Megatherium Enterprises : Mac The Linguist 2 (Mac)
+ P.O. Box 7000-417
+ Redondo Beach, CA 90277
+ (310) 545-5913
+
+ Metro Software, Inc. (HP/IBM)
+ 2509 N. Cambell Ave., Ste. 214
+ Tucson, AZ 85719
+ (602) 299-7313
+
+ Microcosm
+ 819 Devon Court
+ San Diego, CA 92109
+ 619-488-4462
+ 619-488-3087 fax
+ email: Tom Wright <wright@siggraph.org>
+
+ Provides fonts for resale to (mostly Unix & MS-DOS) software companies
+ & hardware comapnies in its own portable file format together with
+ portable C font rendering code. Pricing plans include royalty-free
+ option & end-user site licenses. Standard Type-1 & TrueType formats
+ also supplied. Font files from your artwork available too.
+
+ Modern Graphics :Organic Fonts (Mac)
+ P.O. Box 21366
+ Indianapolis, IL 46221
+ (317) 253-4316
+
+ Monotype Typography Inc.
+ Suite 504-53 West Jackson Blvd.
+ Chicago, IL 60604
+ (312) 855-1444
+ (800) MONOTYPE
+
+ Network Technology Corp. : LaserTEX Font Library (HP/IBM)
+ 6825 Lamp Post Lane
+ Alexandria, VA 22306
+ (703) 765-4506
+
+ Nippon Information Science Ltd. (NIS) (Mac)
+ Sumire Bldg. 4F
+ 5-4-4 Koishikawa
+ Bunkyo-ku, Tokyo 112
+ Japan
+ (03) 945-5955
+
+ Olduvai Corporation : Art Fonts (Mac)
+ 7520 Red Road, Suite A
+ South Miami, FL 33143
+ (305) 665-4665
+ (800) 822-0772 (FL)
+
+ Page Studio Graphics : PIXymbols (Mac)
+ 3175 N. Price Rd. #1050
+ Chandler, AZ 85224
+ (602) 839-2763
+
+ Paperback Software : KeyCap Fonts
+ 2830 9th St.
+ Berkeley, CA 94710
+ (415) 644-2116
+
+ PenUltimate Fonts : Vernacular type for Mac and PC
+ 14101 Walters Rd. #805 : Custom font design
+ Houston, TX 77014
+ Houston, TX 77014
+ E-Mail: PenUltimte@aol.com Send $2 for catalog
+
+ Prosoft (HP/IBM)
+ 7248 Bellair Ave., P.O. Box 560
+ North Hollywood, CA 91605
+ (818) 764 3131
+
+ Qume Corp. (HP/IBM)
+ 2350 Qume Dr.
+ San Jose, CA 95131
+ (800) 223-2479
+
+ Ragnarok Font Line: Scriptorium Font Library
+ POB 140333 120+ original calligraphic, display
+ Austin, TX 78714 and art font designs. SASE for catalog.
+ (512) 472-6535 $15 for 12 font sampler disk. Specify
+ Macintosh or PC preference when ordering.
+
+ R.M.C. : PrintR fonts (HP/IBM)
+ 12046 Willowood Dr.
+ Woodbridge, VA 22192
+ (703) 494-2633
+
+ Richard Beatty Designs : Type 1 and TrueType (PC, Mac)
+ 2312 Laurel Park Highway : 45 fonts decorative elements
+ Hendersonville, NC 28739 : 270 alphabets, 50 original
+ (704) 696-8316 : rest translated from lead and
+ Verified: 9 Feb 1994 : phototype. Goudy a specialty
+
+ S. Anthony Studios : Fonts Vol. 1
+ 889 DeHaro Street
+ San Francisco, CA 94107
+
+ Scholar's Press : (Mac)
+ P.O. Box 15399 : 2 Greek fonts
+ Atlanta, GA 30333-0399
+ (404) 727-2320
+ FAX: (404) 727-2348
+ Verified: 9 Feb 1994
+
+ Scriptorium Font Library
+ (See Ragnarok)
+
+ SoftCraft, Inc.
+ 16 North Carrol St., Suite 220
+ Madison, WI 53703
+ (608) 257-3300
+ FAX: (608) 257-6733
+ Verified: 9 Feb 1994
+
+ Software Complement : (TrueType, Type 1) (Mac, IBM, Next)
+ 8 Penn Ave. : Designer of fonts for Cassidy & Greene
+ Metamoras, PA 18336 : Custom logos and signatures.
+ (717) 491-2492
+ FAX: (717) 491-2443
+ Applelink: SOFTCOMP
+ CompuServe: 70244,3214
+ Verified: 16 Feb 1994
+
+ Straightforward : ZFont (HP/IBM)
+ 15000 Halldale Ave.
+ Gardena, CA 90249
+ (310) 324-8827
+
+ SWFTE International (HP/IBM)
+ Box 5773
+ Wilmington, DE 19808
+ (800) 237-9383
+
+ SystemSoft America, Inc. : Kanji
+ P.O. Box 4260
+ Vero Beach, FL 32964
+
+ Typographics Ltd. : Typo
+ 46, Hehalutz St.
+ Jerusalem 96222
+ Israel
+
+ U-Design, Inc. : TrueType, Type1 (Mac & PC)
+ 270 Farmington Avenue : Originals, licensed designs clones
+ Hartford, CT 06105
+ (203) 278-3648
+ BBS: (203) 525-5117
+ FAX: (203) 278-3003
+ Verified: 9 Feb 1994
+
+ The Underground Phont Archive (TrueType,Shareware)
+ 395 Kaymar Dr.
+ Amherst, NY 14228
+ USA.
+
+ Varityper, Inc. : (Mac)
+ 11 Mt. Pleasant Ave.
+ East Hanover, NJ 07936
+ (800) 631-8134 (US except NJ)
+ (201) 887-8000 ext. 999 (NJ)
+
+ VS Software : HP Bitmaps (PC)
+ P.O. Box 6158 : CG, ITC and original fonts
+ Little Rock, AR 72216
+ (501) 376-2083
+ Verified: 9 Feb 1994
+
+ Weaver Graphics : HP Bitmaps (PC only),
+ 5165 S. Hwy A1A : Adobe Type 1, Truetype (PC and Mac)
+ Melbourne Beach, FL 32951 : Mostly clone fonts, some originals
+ (407) 728-4000
+ Fax: (407) 728-5978
+ Verified: 9 Feb 1994
+
+ Wu Corp. : FeiMa (Mac) Chinese wordprocessor
+ 46 West Avon Rd.
+ Avon, CT 06001
+ (203) 673-4796
+
+ Y&Y, Inc. : Type 1 format, Mac, PC, Unix
+ 45 Walden Street : Computer Modern, Lucida Bright
+ Concord, MA 01742 : AMS, LaTeX/SliTeX, MathTime
+ (800) 742-4059 : Lucida Sans Typewriter etc
+ (508) 371-3286
+ Fax: (508) 371-2004
+ 71172.524@compuserve.com
+
+ ZSoft Corp. : Soft Type
+ 450 Franklin Rd. Suite 100
+ Marietta, GA 30067
+ (404) 428-0008
+ Fax: (404) 427-1150
+
+ Clip Art Vendors
+ ================
+
+ This section was submitted by Dmitry S. Simanenkov in Aug, 1993.
+
+ Although not directly related to type, a list of clip art vendors seems
+ to compliment the list of type/font vendors.
+
+ 3G Graphics, Inc. eps borders, simbols for MAC
+ 114 Second Ave.South, Suite 104
+ Edmonds, WA 98020
+ (206) 774-3518
+ (206) 771-8975
+
+ ArtBytes Hi-Fi Borders for security
+ Ozerkova 51-2-13 paper, stock, certificate etc.
+ Peterburg bitmap & eps, CorelDraw
+ 198903 IBM & MAC
+ Russia
+ simon@dc1.phys.samson.spb.su
+
+ ArtBeats
+ 20083
+ San Bernardino, CA, 92406
+ (800) 444-9392
+ (714) 881-1200
+
+ Best Impression
+ 3844 W. Channel Islands Blvd.
+ Suite. 234
+ Oxnard, CA 93035
+ (805) 984-9748
+
+ Dynamic Graphics, Inc.
+ Designers Club, Creative Art
+ 6000 N. Forest Park Dr.
+ Peoria, IL 61656-1901
+ (800) 255-8800
+ (309) 688-8800
+ (309) 688-5873
+
+ FM Waves
+ 70 Derby Alley
+ San Francisco, CA 94102
+ (800) 487-1234
+ (415) 474-7464
+
+ Grafx Associates Borders
+ 12811
+ Tucson, AZ 85732-2811
+ (800) 628-2149
+
+ Kinetic Presentation, Inc.
+ 250 Distillery Commons
+ Louisville, KY 40206
+ (502) 583-1679
+
+ Metro Image Base, Inc.
+ 18623 Ventura Blvd
+ Suite 210
+ Tarzana, CA 91356
+ (800) 525-1552
+ (818) 881-1997
+
+ Micrografx, Inc.
+ 1303 Arapaho Rd.
+ Richardson, TX 75081
+ (800) 733-3729
+ (214) 234-1769
+
+ Migraph, Inc.
+ 200 S.333 Rd. Suite 220
+ Federal Way, WA 98003
+ (800) 223-3729
+ (206) 838-4677
+
+ Multi-Ad Service, Inc.
+ 1720 W. Detweiller Dr.
+ Peoria, IL 61615
+ (800) 447-1950
+ (309) 692-1530
+
+ Qualitas Trading Co.
+ 6907 Norfolk Rd.
+ Berkley, CA 94705
+ (510) 848-8080
+
+ RT Computer Graphics
+ 2257 Calle Cacique
+ Santa Fe, NM 87505
+
+ Stephen & Associates
+ 8681 N. Magnolia Ave Suite E
+ Santee, CA 92071-4456
+ (619) 562-5803
+
+ Studio Advertising Art
+ 43912
+ Las Vegas, NV 89116
+ (800) 453-1860
+ (702) 641-7041
+
+ Sun Shine CD-ROM, Visual Delights
+ 4351
+ Austin, TX 78765
+ (512) 453-2334
+
diff --git a/help/comp-fonts-FAQ/comp.fonts_FAQ:_X11_Info b/help/comp-fonts-FAQ/comp.fonts_FAQ:_X11_Info
new file mode 100644
index 0000000000..41c5906cda
--- /dev/null
+++ b/help/comp-fonts-FAQ/comp.fonts_FAQ:_X11_Info
@@ -0,0 +1,250 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.mathworks.com!zombie.ncsc.mil!newsgate.duke.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!news3.near.net!amber.ora.com!not-for-mail
+From: norm@ora.com (Norman Walsh)
+Newsgroups: comp.fonts,comp.answers,news.answers
+Subject: comp.fonts FAQ: X11 Info
+Supersedes: <font-faq-15_817479312@ora.com>
+Followup-To: poster
+Date: 14 Aug 1996 10:35:29 -0400
+Organization: O'Reilly and Associates, Inc.
+Lines: 227
+Sender: norm@ruby.ora.com
+Approved: news-answers-request@MIT.Edu
+Distribution: world
+Expires: 27 Sep 1996 14:34:08 GMT
+Message-ID: <font-faq-15_840033248@ora.com>
+References: <font-faq-1_840033248@ora.com>
+Reply-To: norm@ora.com (Norman Walsh)
+NNTP-Posting-Host: ruby.ora.com
+Summary: This posting answers frequently asked questions about fonts.
+ It addresses both general font questions and questions that
+ are specific to a particular platform.
+X-Web-Homepage: http://www.ora.com/homepages/comp.fonts/
+Xref: senator-bedfellow.mit.edu comp.fonts:48312 comp.answers:20526 news.answers:79247
+
+Archive-name: fonts-faq/part15
+Version: 2.1.5
+
+Subject: 10. X11 Information
+
+ This section needs a lot of work. At the time of this release, I'm not
+ in a position to write it so I'm leaving it basically blank. Even if
+ you don't have time to write it, if you know what should be in this
+ section, please forward it to norm.
+
+Subject: 10.1. Getting X11
+
+ The standard location for X software is ftp.x.org.
+
+Subject: 10.2. Historical Notes about X11
+
+ The X Window System has been in widespread use through releases 3, 4,
+ and now 5 of X Version 11.
+
+ Fonts weren't really treated by the X Consortium very well until X11
+ release 5 (X11R5). In X11R3 and X11R4, the default format used by the X
+ servers was called SNF (server normal format). Basically the font was
+ formatted on disk in such a way that the X server could quickly read and
+ use it (it was basically a memory-dump). The important element of the
+ SNF format is that it was not a portable format: it depended on the
+ architecture of the machine running the server (little endian vs. big
+ endian, for example) and as a consequence you needed different directory
+ structures for different systems on your network. On top of that,
+ several systems vendors implemented their own font format, making font
+ portability even more difficult.
+
+ With X11R5, two things changed: the font service protocol was defined as
+ a standard and interoperable way for an X server to obtain fonts
+ (independent of their format, origin, or current location on disk) and
+ the default format for storing fonts was changed from SNF to PCF
+ (Portable Compiled Font). PCF is a format originally developed by DEC.
+ Its primary advantage is that it is not architecture dependent. That
+ is, if you compile a font to PCF format on different systems, then you
+ may end up having two different PCF files, but each system will be able
+ to read the other's file correctly.
+
+Subject: 10.3. X11 Font Formats
+
+ There are many different font formats that can play a role in an X11
+ system configuration. The following table summarizes some of the
+ common formats:
+
+ * BDF
+
+ The Bitmap Distribution Format (BDF) is the standard format for
+ distribution of fonts. It is an ASCII format so it can easily be
+ edited it with your favourite editor or E-mailed to other users.
+ As the name suggests, it stores bitmap fonts only.
+
+ Another virtue of the BDF format is that most font format
+ converters convert to or from this format. Means if you want to go
+ from format A to format B, neither of which is BDF, then you are
+ likely to convert A to BDF, then BDF to B.
+
+ The BDF format is defined by Adobe. A document describing the
+ format is available by ftp from Adobe's file server at
+ "ps-file-server@adobe.com". It is also available in the standard X
+ distribution. Look under ../X11R4(5)/mit/hardcopy/BDF. This
+ document is also reproduced in any text describing the X standard.
+
+ * SNF
+
+ The Server Normal Format (SNF) is an older format for bitmap
+ fonts. The format is X Server and host dependent. This means that
+ if you have two SNF files, their actual format may be different.
+ Also, if you have an "snftobdf" utility, it may not be able to
+ read font files from other systems. Convert to BDF format before
+ you move it off the host system.
+
+ Snftobdf is one utility that can generate a BDF file from a SNF
+ file. It was part of the X11R4 contrib release. To compile under
+ X11R5, you need some of the X11R4 snf include files.
+
+ * PCF
+
+ The Portable Compiled Font (PCF) format is a binary format for
+ bitmap fonts. The binary contains sufficient information to be
+ readable by other systems.
+
+ * PHIGS
+
+ These fonts are only applicable in PEX environments. PHIGS fonts
+ don't really have any relationship to the normal X font mechanism.
+
+ * DWF
+
+ The DECWindows Fonts (DWF) are bitmap fonts.
+
+ * Intellifont
+
+ These are HP scalable fonts.
+
+ * PFA/PFB
+
+ These are Adobe Type 1 PostScript fonts.
+
+ They can be used in X11R5 based X servers and font servers because
+ IBM has donated a renderer for this format to the X Consortium.
+ The renderer can be found on the X11R5 contrib, and on ftp.x.org.
+
+ * Speedo
+
+ This is a format from Bitstream, Inc. Bitstream has also donated a
+ font renderer to the X Consortium, and a couple of fonts.
+
+ I have been told that in order to use commercial fonts from
+ BitStream, you must patch the renderer somewhat to make it use the
+ right decryption code for the font.
+
+ * FB
+
+ These are Sun X11/NeWS format bitmap fonts used by the Sun
+ OpenWindows system.
+
+ You can use "convertfont" which comes with OpenWindows to convert
+ to/from BDF.
+
+ * F3/F3B
+
+ This is the scalable Sun Folio format, also used by OpenWindows.
+
+ You can use "convertfont" to convert to (not from) BDF.
+
+Subject: 10.4. X11 Font Server
+
+ X11 Release 5
+ =============
+
+ With X11 Release 5, the X Consortium has created a network-based
+ standard font protocol. As a user of the X Window System, you have an X
+ server on your desktop, which does the interface between the hardware
+ (screen, mouse, keyboard), and the X network protocol. This X server
+ needs fonts. Before X11R5, the only way it could get to those fonts
+ was to make font directories readable for the X server on that host,
+ either by NFS-mounting or by copying.
+
+ With the X Font Service protocol, you just tell your X server that it
+ must use the services of a font server, which is a daemon process
+ sitting on a host on your network. The font server is a program which
+ talks a standardized protocol on the network, and which is capable of
+ reading several font formats.
+
+ The font server sources are modular, such that it is easy to add a
+ renderer for an additional font format to the existing code. This is
+ obviously also the intention: the X Consortium provides the core
+ technology, and supposes that all systems vendors will add font
+ renderers for their proprietary formats to the code, and then ship that
+ to their customers.
+
+ If you have a multi-vendor environment, then you are supposed to run a
+ font server on every host that carries the font files. Then all of the
+ X servers on your network can put all the fonts they need in their font
+ path. Automatically, IBM fonts will be requested from the font server
+ on an IBM host, DEC fonts from a DEC host, etc.
+
+ Other benefits of using font server technology include the ability of
+ the font server to implement caching, provide for fault-tolerant setup,
+ etc.
+
+ A final example of the good use of the font server is the combination
+ of a font server with a Type 1 font renderer. As mentioned above, IBM
+ donated a Type 1 font renderer which can easily be built into the X
+ font server. As the Type 1 font format, and the ATM format are the same,
+ it is perfectly possible to use commercial ATM fonts with the X Window
+ System. See also /contrib/fonts/lib/font/Type1/ in the X11
+ distribution.
+
+ X11 Release 6
+ =============
+
+ The X11R6 font server is very similar to the X11R5 server described
+ above. Under X11R6, the font server has been renamed to xfs and the
+ Type 1 rendering engine is now incorporated into the base
+ distribution--it is no longer a contributed package.
+
+Subject: 10.5. Fonts and utilities for X11
+
+ Here's a quick list of possible steps to get from "what you got" to X:
+
+ * Mac format bitmaps:
+
+ No idea. If you know how to read a Mac format bitmap file on some
+ other platform, please tell norm.
+
+ * PC format bitmaps:
+
+ Conversion to BDF is possible from TeX PK format and LaserJet
+ softfont format. Other conversions are also within the realm of
+ possibility. Feel free to ask norm for more information if you
+ have a specific conversion in mind.
+
+ * TeX PK format bitmaps:
+
+ PKtoBDF gets us directly to BDF format from here.
+
+ * Mac format postscript:
+
+ Under MS-DOS, conversion to PC format postscript allows the font to
+ be accessed with PS2PK (under *nix or MS-DOS). See above for TeX
+ PK to X conversions.
+
+ * PC/Unix format PostScript
+
+ Conversion to TeX PK with PS2PK allows you to get to BDF
+ (indirectly).
+
+ * XtoBDF, getbdf, FStoBDF
+
+ XtoBDF and getbdf are two public-domain applications which are
+ capable of asking an X server to give them all it knows about a
+ given font. They then print the BDF representation of that font on
+ stdout.
+
+ You can use these if you have an X server that can read some font
+ file, but nothing else can.
+
+ FStoBDF is distributed with X11R5.
+
+ If you use one of these programs, you may actually be converting a
+ scalable font into a bitmap font, but converting a bitmap font to a
+ scalable one is not currently possible.
+
diff --git a/help/comp.programming.literate_FAQ b/help/comp.programming.literate_FAQ
new file mode 100644
index 0000000000..9cf2fe5283
--- /dev/null
+++ b/help/comp.programming.literate_FAQ
@@ -0,0 +1,2639 @@
+Path: senator-bedfellow.mit.edu!dreaderd!not-for-mail
+Message-ID: <literate-programming-faq_1075625008@rtfm.mit.edu>
+Supersedes: <literate-programming-faq_1074244461@rtfm.mit.edu>
+Expires: 1 Mar 2004 08:43:28 GMT
+X-Last-Updated: 2000/03/16
+From: thompson@shelob.ce.ttu.edu
+Organization: Texas Tech University, Lubbock, Texas, USA
+Newsgroups: comp.programming.literate,comp.answers,news.answers
+Subject: comp.programming.literate FAQ
+Followup-To: comp.programming.literate
+Reply-To: thompson@shelob.ce.ttu.edu
+Approved: news-answers-request@MIT.Edu
+Summary: Literate Programming FAQ
+Distribution: world
+Originator: faqserv@penguin-lust.MIT.EDU
+Date: 01 Feb 2004 08:43:46 GMT
+Lines: 2618
+NNTP-Posting-Host: penguin-lust.mit.edu
+X-Trace: 1075625026 senator-bedfellow.mit.edu 574 18.181.0.29
+Xref: senator-bedfellow.mit.edu comp.programming.literate:5657 comp.answers:56121 news.answers:265541
+
+Archive-name: literate-programming-faq
+Last-modified: 2000/03/15
+Version: 1.3.1
+
+The Literate Programming FAQ
+ David B. Thompson <thompson@shelob.ce.ttu.edu>
+ Version: 1.3.1, Mar 15, 2000
+
+ The purpose of this document is two-fold: First, there is a need to
+ present a basic description of literate programming and how applica-
+ tion of literate programming principles can improve the resulting
+ code. Second, there is a need to present a list of tools available
+to
+ iterate programmers. Hopefully, this document will meet both needs.
+ ____________________________________________________________________
+__
+
+ Table of Contents
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 1. Welcome
+
+ 1.1 Disclaimer
+ 1.2 Copyright
+ 1.3 What's New?
+ 1.4 What's Needed?
+
+ 2. Introduction
+
+ 3. How do I get the FAQ?
+
+ 3.1 Literate Programming FAQ
+
+ 4. Is there a newsgroup?
+
+ 5. What internet nodes are of interest to literate programmers?
+
+ 5.1 Web Ring
+ 5.2 The Literate Programming Archive (LPA)
+ 5.3 Comprehensive TeX Archive Network (CTAN)
+
+ 6. What is Literate Programming?
+
+ 7. How do I begin literate programming?
+
+ 8. Important and Actively-Supported Tools
+
+ 8.1 CWEB
+ 8.2 CWEBx3.0
+ 8.3 FWEB
+ 8.4 noweb
+ 8.5 nuweb
+ 8.6 ProTeX
+
+ 9. Unsupported Tools
+
+ 9.1 AFTWEB (Almost Free Text WEB)
+ 9.2 APLWEB
+ 9.3 CLiP
+ 9.4 mCWEB
+ 9.5 FunnelWeb
+ 9.6 FunnelWeb 3.0AC
+ 9.7 LEO
+ 9.8 Literate Programmer's Workshop (LPW)
+ 9.9 MapleWEB
+ 9.10 Matlabweb
+ 9.11 RWEB
+ 9.12 SchemeWEB
+ 9.13 SpideryWEB
+ 9.14 WEB
+ 9.15 WinWordWEB
+
+ 10. Are there other tools I should know about?
+
+ 10.1 C2LaTeX
+ 10.2 c2cweb
+ 10.3 c2man
+ 10.4 cnoweb
+ 10.5 dpp
+ 10.6 Fold2Web
+ 10.7 Funnelweb Mode
+ 10.8 noweb.el
+ 10.9 noweb-outline.el
+ 10.10 nuweb.el
+ 10.11 Web mode
+
+ 11. What other resources are available?
+
+ 11.1 TeX Resources
+
+ 12. Are there any code examples?
+
+ 13. Bibliographies
+
+ 14. Other Opinions about Literate Programming
+
+ 14.1 van Ammers
+ 14.2 Ramsey
+ 14.3 My (Dave Thompson's) Experience
+ 14.4 Others
+
+ 15. How to anonymously ftp
+
+ 16. Acknowledgements
+
+ 17. End notes
+
+
+
+ ____________________________________________________________________
+__
+
+ 1. Welcome
+
+ Information contained in this document is the best available at
+ preparation. The original file was dated October 15, 1993 (just for
+ historical purposes).
+
+
+ 1.1. Disclaimer
+
+ This FAQ is presented with no warranties or guarantees of ANY KIND
+ including correctness or fitness for any particular purpose. The
+ author of this document has attempted to verify correctness of the
+ data contained herein; however, slip-ups can and do happen. If you
+ use this data, you do so at your own risk.
+
+
+ 1.2. Copyright
+
+ Copyright 1993-2000 by David B. Thompson. All rights reserved
+ worldwide. Permission is granted to copy this document for free
+ distribution so long as it remains intact and unmodified. For other
+ arrangements, contact the author/maintainer via email:
+ <thompson@shelob.ce.ttu.edu>
+
+
+
+ 1.3. What's New?
+
+
+ o Updated dpp entry. See Section ``dpp''
+
+ o Added noweb-outline.el entry. See section ``noweb-outline.el''
+
+
+ 1.4. What's Needed?
+
+
+ o I've checked some of the links to software. If anyone finds the
+ FAQ useful, please let me know if the links are active or dead
+when
+ you're surfing.
+
+ o Some authors have disappeared. If you know one of them, or are
+an
+ author (and wish to remain in contact ;), then please provide
+ current contact information.
+
+ o I could use some feedback on the state of the FAQ. It's about as
+ complete as I know how to make it.
+
+
+
+ 2. Introduction
+
+ Literate programming is a phrase coined by Donald Knuth to describe
+ the approach of developing computer programs from the perspective
+of a
+ report or prose. The focus, then, is on description (and
+ documentation) of the approach in human-readable form. This is in
+ contrast to the normal approach of focusing on the code.
+
+ This document is for new and experienced users of literate
+programming
+ tools. The purpose is to explain the concept of literate
+programming
+ and to provide a resource for locating resources of interest to
+ literate programmers and those interested in literate programming.
+
+ The Literate Programming (LitProg) Frequently Asked Questions (FAQ)
+ list is maintained by Dave Thompson <thompson@shelob.ce.ttu.edu>.
+
+ Comments and constructive criticisms are welcome. Direct flames to
+ /dev/null (or nul if you're a msdos user! ;-) If you find an error,
+ please report it. I'm particularly interested in establishing the
+ locations of generally available literate programming tools. If you
+ are the author of such a tool and wish to have it included in this
+ list, please send email.
+
+ Please note this is a work-in-progress. It is not complete, and
+ probably will never be complete. Nevertheless, the information
+ contained herein may be useful to some. Use it as it is intended.
+
+
+
+ 3. How do I get the FAQ?
+
+ 3.1. Literate Programming FAQ
+
+ You have many ways to get a current copy of this FAQ. One is to use
+ anonymous ftp (if you don't know how, see a later section in this
+FAQ)
+ to connect to one of the ``Comprehensive TeX Arvchive Network''
+sites
+ or the Literate Programming Archive and retrieve a copy of the file.
+ Open an ftp connection to one of the CTAN sites and retrieve the
+file
+ help/comp.programming.literate_FAQ.
+
+ Cesar Bellardini cballard@santafe.com.ar prepared a translation of
+the
+ FAQ into Spanish. It's available at
+
+ (For more information on CTAN and the literate programming archive,
+ see the section below entitled ``Internet Nodes of Interest to
+ Literate Programmers''.)
+
+
+
+ 4. Is there a newsgroup?
+
+ One of the most important resources is the literate programming
+ newsgroup, comp.programming.literate. Because of the amount of
+ spamming and unrelated posts, the newsgroup is now moderated. You
+can
+ read this newsgroup using your standard reader.
+
+
+ 5. What internet nodes are of interest to literate programmers?
+
+ The principal nodes of interest to literate programmers are the
+ Literate Programming Archive (LPA hereafter) and the CTAN
+ (Comprehensive TeX Archive Network).
+
+
+
+ 5.1. Web Ring
+
+
+ There is a web ring for literate programming. It is at the URL
+ www.webring.org/cgi-bin/webring?ring=litprog;list
+
+
+
+ 5.2. The Literate Programming Archive (LPA)
+
+ The Literate Programming Archive (LPA) is:
+
+ o Node: ftp.th-darmstadt.de [130.83.55.75]
+
+ o Directory: /pub/programming/literate-programming
+
+ o Notes: Fastest response during off-U.S. [yep] business hours.
+
+ However, the LPA seems to be defunct in that no files are available
+in
+ the /pub directory. If anyone knows anything about the status of
+the
+ LPA, please send email.
+
+
+
+ 5.3. Comprehensive TeX Archive Network (CTAN)
+
+ Participating hosts in the Comprehensive TeX Archive Network are
+(from
+ the file CTAN.sites):
+
+ o ftp.dante.de (Mainz, Germany)
+
+ o anonymous ftp /tex-archive (/pub/tex /pub/archive)
+
+ o Gopher: gopher.dante.de
+
+ o e-mail ftpmail@dante.de
+
+ o WWW www.tex.ac.uk
+
+ o Administrator: <ftpmaint@dante.de>
+
+ o ftp.tex.ac.uk (Cambridge, UK)
+
+ o anonymous ftp /tex-archive (/pub/tex /pub/archive)
+
+ o Gopher: gopher.tex.ac.uk
+
+ o NFS mountable from nfs.tex.ac.uk:/public/ctan/tex-archive
+
+ o WWW www.tex.ac.uk
+
+ o Administrator: <ctan-uk@tex.ac.uk>
+
+ o ctan.tug.org (Boston, Massachusetts, USA)
+
+ o anonymous ftp /tex-archive (/pub/archive)
+
+
+ o WWW ctan.tug.org
+
+ o Administrator: <ctan@tug.org>
+
+ The pointer, ftp://ftp.cdrom.com/pub/tex/ctan/CTAN.sites, is
+directed
+ to the official list of CTAN archive sites and their mirrors.
+
+
+
+ 6. What is Literate Programming?
+
+ Literate programming is the combination of documentation and source
+ together in a fashion suited for reading by human beings. In fact,
+ literate programs should be enjoyable reading, even inviting!
+(Sorry
+ Bob, I couldn't resist!) In general, literate programs combine
+source
+ and documentation in a single file. Literate programming tools then
+ parse the file to produce either readable documentation or
+compilable
+ source. The WEB style of literate programming was created by D.E.
+ Knuth during the development of his TeX typsetting software.
+
+ All the original work revolves around a particular literate
+ programming tool called WEB. Knuth says:
+
+ The philosophy behind WEB is that an experienced system pro-
+ grammer, who wants to provide the best possible documenta-
+ tion of his or her software products, needs two things
+ simultaneously: a language like TeX for formatting, and a
+ language like C for programming. Neither type of language
+ can provide the best documentation by itself; but when both
+ are appropriately combined, we obtain a system that is much
+ more useful than either language separately.
+
+
+
+ The structure of a software program may be thought of as a
+ web that is made up of many interconnected pieces. To docu-
+ ment such a program we want to explain each individual part
+ of the web and how it relates to its neighbours. The typo-
+ graphic tools provided by TeX give us an opportunity to
+ explain the local structure of each part by making that
+ structure visible, and the programming tools provided by
+ languages such as C or Fortran make it possible for us to
+ specify the algorithms formally and unambigously. By combin-
+ ing the two, we can develop a style of programming that max-
+ imizes our ability to perceive the structure of a complex
+ piece of software, and at the same time the documented pro-
+ grams can be mechanically translated into a working software
+ system that matches the documentation.
+
+
+ See Section ``Other Opinions'' for some additional thoughts on
+ literate programming.
+
+
+
+ 7. How do I begin literate programming?
+
+ I've given considerable thought as to what should be in this section
+ of the FAQ. This is probably the most important section of this
+ document. My suggestion is that you review Section ``Supported
+ Tools'' and Section ``Unsupported Tools'' to choose a system
+ appropriate for the kind of development you do. Then, use the
+manual
+ that accompanies the system to determine how it complements your
+ development style.
+
+
+ Both Eric van Ammers, Section ``van Ammers'', and Norman Ramsey,
+ Section ``Ramsey'', wrote some thoughts on literate programming.
+I've
+ included these thoughts in Section ``Other Opinions'' below.
+
+ I started with a pretty-printing tool, Section ``cnoweb'', as a test
+ of the utility of interweaving significant documentation with code.
+ My experience is detailed in Section ``Thompson''.
+
+ Wayne Sewell's (1989) Weaving a Program: Literate Programming in
+WEB.
+ Van Nostrand Reinhold, ISBN 0-442-31946-0 (pbk). This book focuses
+ on using Knuth's web system.
+
+ I've read D. E. Knuth's collection of articles (1992) entitled
+ Literate Programming. Center for the Study of Language and
+ Information, Stanford University, ISBN 0-937073-80-6 (pbk). This
+book
+ gives insight into Knuth's thoughts as he developed the web system
+of
+ literate programming (and TeX for typesetting). However, it does
+not
+ document methods for literate programming.
+
+ Some talk exists in the newsgroup/mailing list for a Usenet
+University
+ course in literate programming. I'm sure discussion of this topic
+ will be welcomed. (1Feb2000: Note this thread has been dead for a
+ long, long time. I wish someone would pick it up.)
+
+
+
+ 8. Important and Actively-Supported Tools
+
+ I have selected a few of the tools from my list that appear to be
+most
+ actively supported. Inclusion here does not imply endorsement;
+ exclusion does not imply lack of quality.
+
+
+ 8.1. CWEB
+
+
+ Developer:
+ Silvio Levy and D.E. Knuth
+
+ Version:
+ 3.5
+
+ Hardware:
+ Unix systems (dos and amiga ports available)
+
+ Languages:
+ C and C++
+
+ Formatter:
+ Plain TeX and LaTeX.
+
+ Availability:
+ Anonymous ftp from:
+
+ o ftp://labrea.stanford.edu:/pub/cweb
+
+ o LPA:/c.c++
+
+ o CTAN:/web/c_cpp/cweb
+
+ o DOS version is no longer available.
+
+ o Win32 version www.literateprogramming.com
+
+ o Amiga version from Aminet:dev/c.
+
+ o Mac port of CTANGLE in LPA:/machines/mac
+
+ o LaTeX support in LPA:/c.c++
+
+ Readme:
+ Bundled with above
+
+ Description:
+ No description provided.
+
+ Support:
+ Bugs to <levy@math.berkeley.edu>
+
+
+ 8.2. CWEBx3.0
+
+
+ Developer:
+ Marc van Leeuwen
+
+ Version:
+ 3.04
+
+ Hardware:
+ Any system using ASCII code
+
+ Languages:
+ ANSI C
+
+ Formatter:
+ Plain TeX
+
+ Availability:
+ Anonymous ftp from:
+
+ o wwwmathlabo.univ-poitiers.fr/~maavl/CWEBx/
+
+ Readme:
+ Bundled with above
+
+ Brief description:
+ A modified implementation of CWEB, with some extensions.
+ Provides a mode for full compatibility with Levy/Knuth CWEB.
+The
+ most significant extras are:
+
+ o Typedef declarations affect formatting througout source file
+
+ o Include files are scanned for typedef definitions
+
+ o Flexible selection of layout style
+
+ o Possibility to refer to sections using symbolic labels
+
+ o CTANGLE detects unbalanced braces and parentheses
+
+ o CWEAVE can be made to report syntax errors more easily
+
+ o Some additional mechanisms to avoid formatting problems
+
+ o New and modular set of grammar rules, based on ANSI C syntax
+
+ o Possibility to suppress #line directives
+
+ o A new manual
+
+
+ Support:
+ bugs and remarks to maavl@mathlabo.univ-poitiers.fr
+
+
+ 8.3. FWEB
+
+
+ Developer:
+ John A. Krommes
+
+ Version:
+ 1.62
+
+ Hardware:
+ Unix, VMS, and DOS platforms (anything with ANSI C)
+
+ Languages:
+ C, C++, Fortran-77, Fortran-90, Ratfor, TeX; also, a anguage-
+ independent mode.
+
+ Formatter:
+ LaTeX. Plain TeX may work, but is no longer supported.
+
+ Availability:
+ Anonymous ftp from:
+
+ o ftp.pppl.gov/pub/fweb
+
+ o CTAN:/web/fweb
+
+ o msdos version on ftp.ppl.gov site
+
+ Readme:
+ In bundle with above.
+
+ Description:
+ It also has a well-developed user's manual and its own FAQ
+(see
+ above). Beginning with 1.40, documentation is maintained in
+gnu
+ texinfo format. It runs on most platforms: VMS, PC, UNIX, and
+ pretty much anything that the GNU C compiler (GCC) is
+supported
+ for.
+
+ Features:
+
+ o Processes multiple languages during a single run (so one can
+mix
+ C and Fortran, for example).
+
+ o Language-independent mode (v1.40).
+
+ o Ability to turn off pretty-printing (v1.40).
+
+ o Built-in Ratfor translator.
+
+ o Built-in macro preprocessor (closely follows ANSI C, with
+ extensions).
+
+ o A style file that allows the user to adjust many parameters
+and
+ behavior patterns of FWEB.
+
+ o Various operator-overloading features that provide additional
+ pretty-printing capabilities to languages such as C++ and
+ Fortran-90.
+
+ o Numerous miscellaneous features and command-line options.
+
+
+ Support:
+ Bug reports and suggestions to krommes@princeton.edu Online
+ documentation is available at
+ w3.pppl.gov/%7ekrommes/fweb_toc.html
+
+
+ 8.4. noweb
+
+
+ Developer:
+ Norman Ramsey <nr@eecs.harvard.edu>
+
+ Version:
+ 2.9a
+
+ Hardware:
+ Unix and DOS platforms (DOS binaries available for v2.7).
+
+ Languages:
+ All programming languages, singly or in combination.
+Automatic
+ indexing for C, Icon, Pascal, Standard ML, TeX, Yacc
+
+ Formatter:
+ Plain TeX, LaTeX, and HTML formatters. Will convert LaTeX to
+ HTML automatically.
+
+ Availability:
+ Anonymous ftp from:
+
+ o CTAN:/web/noweb
+
+ o LPA:/independent
+
+ o Last recourse, use ftp.cs.virginia.edu:pub/nr
+
+ Readme:
+ With bundle above, or see the noweb home page:
+ www.eecs.harvard.edu/~nr/noweb Those without http access can
+ consult ``Literate Programming Simplified,'' IEEE Software,
+ September 1994, pp97-105, or ``Literate Programming Using
+ Noweb,'' Linux Journal, October 1997, pp64-69.
+
+
+ Description:
+ Noweb is designed to meet the needs of literate programmers
+ while retaining the simplest possible input format. Its
+primary
+ advantages are simplicity, extensibility, and language-
+ independence. Noweb uses 5 control sequences to WEB's 27.
+The
+ noweb manual is only 3 pages; an additional page explains how
+to
+ customize its LaTeX output. Noweb works ``out of the box''
+with
+ any programming language, and supports TeX, latex, and HTML
+back
+ ends. A back end to support full hypertext or indexing takes
+ about 250 lines; a simpler one can be written in 40 lines of
+ awk. Unlike WEB, Noweb does not have prettyprinting built in,
+ but there are several third-party extensions that provide
+ prettyprinting, includeing dpp, pretzel, and nwpp.
+
+
+ Noweb supports indexing and identifier cross-reference,
+ including hypertext ``hot links.'' noweb includes a simple,
+ efficient LaTeX-to-HTML converter, so you can use hypertext
+ browsers on your legacy documents. Noweb can also process
+nuweb
+ programs, so you can use noweb to convert a standard nuweb
+ program to HTML with one command.
+
+
+ Support:
+ email to the author
+
+
+ 8.5. nuweb
+
+
+ Developer:
+ Preston Briggs: <preston@cs.rice.edu>
+
+ Version:
+ 0.87
+
+ Hardware:
+ Unix systems: Sparcs, RS/6000s, HPs; (!) MSDOS and Amiga.
+
+ Languages:
+ Any programming language or combination of programming
+ languages.
+
+ Formatter:
+ Latex
+
+ Availability:
+ Anonymous ftp from:
+
+ o Unix: CTAN:/web/nuweb
+
+ o DOS: CTAN:/web/nuweb-pc
+
+ o LPA:/independent
+
+ o Amiga: CTAN:/web/nuweb/nuweb_ami
+
+ o Amiga: wuarchive.wustl.edu/pub/aminet
+
+ Readme:
+ Send mail to <preston@cs.rice.edu>
+
+
+ Description:
+ A single program that takes a web file written in a
+combination
+ of latex and any programming language(s) and produces a latex
+ file that can be pretty printed and a set of files containing
+ code for compilation/interpretation by the appropriate
+language
+ processors.
+
+
+ Strengths include speed, simplicity, multiple languages, nice
+ indices and cross-references, latex. Doesn't require any
+ special macros or macro files.
+
+
+ Drawbacks: latex-dependent, no code pretty printing, harder to
+ make indices than cweb.
+
+
+ More good stuff: nice support for make, doesn't reformat
+source
+ files, so they're easy to debug. Lots of control without too
+ much effort. That is, it doesn't do too much!
+
+
+ Future directions... Very little change planned, except
+perhaps
+ refinements in the indexing software.
+
+
+ Support:
+ Hack it yourself or send e-mail to <preston@cs.rice.edu>
+
+
+ 8.6. ProTeX
+
+
+ Developer:
+ Eitan Gurari <gurari@cis.ohio-state.edu>
+
+ Version:
+ ProTeX 1.5, AlProTeX 2.3
+
+ Hardware:
+ Any platform with (La)TeX
+
+ Languages:
+ Any language
+
+ Formatter:
+ TeX or LaTeX
+
+ Availability:
+ Anonymous ftp from:
+
+ o www.cis.ohio-state.edu/~gurari/systems.html
+
+ o LPA:/independent
+
+ Readme:
+ With bundle above
+
+ Description:
+
+ o Easy to use
+
+ o Extensible
+
+ o Language independent
+
+ o Multiple output files
+
+ o Fast (single compilation provides output and dvi files)
+
+ o Option for XHTML and pdf files
+
+ o No installation is needed besides copying the files (written
+in
+ TeX) Introduction of main features and examples on web site
+ above. Complete manual in Eitan M. Gurari, "TeX and LaTeX:
+ Drawing and Literate Programming", McGraw-Hill, 1994
+
+ Support:
+ <gurari@cis.ohio-state.edu>
+
+
+
+ 9. Unsupported Tools
+
+
+
+ 9.1. AFTWEB (Almost Free Text WEB)
+
+
+ Developer:
+ Todd A. Coram
+
+ Version:
+ 4.6
+
+ Hardware:
+ Linux, Unix, MSDOS Any system with Perl, and a C++ compiler
+with
+ STL (such as gcc 2.7.2).
+
+ Languages:
+ Any (C/C++ support supplied)
+
+ Formatter:
+ LaTeX or HTML by way of AFT.
+
+ Availability:
+ www.mindspring.com/~coram/aft.html
+
+ Readme:
+ Bundled with above.
+
+
+ Brief description:
+ AFTWEB uses a CWEB-like syntax. It uses AFT for documentation
+ markup (AFT is a minimalistic, yet powerful, markup language
+ with very few commands). AFTWEB was written in AFTWEB (using
+ C++) and the weaved document is available online (as HTML) at
+ the URL listed above.
+
+
+ Support for C and C++ is supplied. You can easily support
+other
+ languages (such as Java and Perl) by writing a new language
+ description file.
+
+
+ The markup language AFT is very easy to learn and is available
+ at the same URL as AFTWEB.
+
+
+ Support:
+ Bugs to tcoram@pobox.com
+
+
+ 9.2. APLWEB
+
+
+ Developer:
+ Christoph von Basum
+
+ Version:
+ Unknown
+
+ Hardware:
+ MSDOS
+
+ Languages:
+ IBM APL2 and STSC APL
+
+ Formatter:
+ Plain TeX
+
+ Availability:
+ Anonymous ftp from: watserv1.uwaterloo.ca:/languages/apl/aplwe
+b
+
+ Readme:
+ At above ftp location.
+
+
+ Description:
+ None available.
+
+ Support:
+ Unknown
+
+ Note:
+ The status of this particular package is unknown. It's at the
+ ftp site, but other than that I can't say. Last known email
+ address of developer is CvB@erasmus.hrz.uni-bielefeld.de.
+
+
+ 9.3. CLiP
+
+
+ Developer:
+ E.W. van Ammers and M.R. Kramer
+
+ Versions:
+ 2.0 and 2.4b (DOS only)
+
+ Platform:
+ Vax/VMS, Unix, DOS
+
+ Languages:
+ Any programming language
+
+ Formatter:
+ Any formatter (TeX, LaTeX, Troff, Runoff, HTML, etc) or any
+ wordprocessor including WYSIWYG systems (Word Perfect,
+WinWord,
+ Ami Pro, Word Pro, etc.)
+
+ Availability:
+ Anonymous ftp from:
+
+ o ftp://sun01.info.wau.nl:/CLIP/ms_dos
+
+ o ftp://sun01.info.wau.nl:/CLIP/ms_dos_24b
+
+ o ftp://sun01.info.wau.nl:/CLIP/vax_vms
+
+ o ftp://sun01.info.wau.nl:/CLIP/unix
+
+ o CTAN:/web/clip
+
+ o LPA:/machines/ms-dos
+
+ o LPA:/machines/vax
+
+ Readme:
+ With bundle above
+
+ Description:
+ CLiP does not use explicit commands to perform the extraction
+ process. Rather it recognizes pseudostatements written as
+ comments in the programming language in question. CLiP
+ distinguishes pseudostatements from ordinary comments because
+ the former comply with a particular style. This style can be
+ adjusted to suit virtually any programming language. The CLiP
+ approach to LP makes the system extremely versatile. It is
+ independent of programming language and text processing
+ environment. We designed CLiP to be compatible with hypertext
+ systems as well. Some hypertext examples are at:
+
+ o ftp://sun01.info.wau.nl/clip/html/queens.htm
+
+ o ftp://sun01.info.wau.nl/clip/html/pal1.htm
+
+ Features:
+
+ o CLiP imposes virtually no limitations on the text-processing
+ system used to produce the documentation. If the
+text-processor
+ supports these items you can
+
+ o structure the documentation according to your own taste.
+
+ o include drawings, pictures, tables etc.
+
+ o disclose your documentation my means of X-ref tables, Indexes,
+ Table of contents, Table of tables, Table of figures, etc.
+
+ o typeset the documented code.
+
+ o Extracts any number of modules from a maximum of 64 source
+ files.
+
+ o No pretty-printing. Code from the source files is copied "as
+is"
+ to the module.
+
+ o Appearance of code segments in the documentation matches those
+ of the modules to ease the identification of code segments.
+
+ o Supports partially specified data types.
+
+ o Comprehensive user manual (preliminary version) and technical
+ description.
+
+ o No automatic generation of a X-ref table for program
+ identifiers.
+
+ Support:
+ Bugs, problems and assistance by e-mail to
+ <Eric.vanAmmers@user.info.wau.nl>
+
+
+ 9.4. mCWEB
+
+
+ Developer:
+ Markus Oellinger
+
+ Version:
+ 1.0
+
+ Hardware:
+ Unix
+
+ Languages:
+ C/C++
+
+ Formatter:
+ plain TeX
+
+ Availability:
+ anonymous ftp from ist.tu-
+ graz.ac.at:/pub/utils/litprog/mcweb/mcweb.tgz
+
+ Readme:
+ at same location
+
+ Description:
+ This is mCWEB 1.0, a descendant of the CWEB system of
+structured
+ documentation by Donald E. Knuth and Silvio Levy. It adds
+some
+ features that are indispensable when working in a team. mCWEB
+ regards a project of a book consisting of several chapter
+files.
+ By means of import and export commands, it automatically
+manages
+ all relationships between the chapters of a book and to other
+ books.
+
+
+ Interface documentation is now also part of mCWEB. It is
+ extracted into a second TeX file. This makes it possible to
+ define well known interfaces between the individual parts of a
+ project that will be implemented by different persons.
+
+
+ In addition, mCWEB parses C header files to find out about all
+ the datatypes defined there.
+
+
+ mCWEB comes with a full completely rewritten user manual and
+is
+ compatible with CWEB.
+
+
+ Support:
+ Institute of Software Technology, moell@ist.tu-graz.ac.at
+
+
+ 9.5. FunnelWeb
+
+
+ Developer:
+ Ross N. Williams ross@ross.net
+
+ Version:
+ V3.2 (May 1999).
+
+ Hardware:
+ MS-DOS, MacOS, Win32, OpenVMS, Solaris, Red Hat Linux, BSD/OS,
+ FreeBSD, Digital Unix, IRIX.
+
+ Status:
+ Open Source GNU.
+
+ Languages:
+ No restrictions.
+
+ Formatter:
+ Generates TeX and/or HTML
+
+ Web:
+ www.ross.net/funnelweb/
+
+ Availability:
+ ftp.ross.net/clients/ross/funnelweb/
+
+ Readme:
+ With bundle above.
+
+
+ Description:
+ FunnelWeb is a production-quality literate-programming tool
+that
+ emphasises simplicity and reliability. Everything about
+ FunnelWeb, from the simplicity of its language to the
+ comprehensive tutorial in the user's manual, has been designed
+ to make this as simple, as practical, and as usable a tool as
+ possible.
+
+ Features:
+
+ o Provides a simple macro preprocessor facility.
+
+ o Generates typeset documentation in TeX and/or HTML formats.
+
+ o Runs on a wide range of platforms.
+
+ o Portable C source code distributed under GNU licence.
+
+ o Comprehensively documented online:
+
+ o www.ross.net/funnelweb/tutorial/
+
+ o www.ross.net/funnelweb/reference/
+
+ o www.ross.net/funnelweb/developer/
+
+ o Programming-language independent.
+
+ o Mature and essentially bug-free (released 1992).
+
+ o Can generate multiple output files.
+
+ o Allows complete control over the output text.
+
+ o Also useful for generating web sites!
+
+
+ Support:
+ No formal support available. Mailing list maintained with
+about
+ 50 subscribers. Informal assistance available from mailing
+ list.
+
+
+ 9.6. FunnelWeb 3.0AC
+
+
+ Developer:
+ Enhanced by A.B.Coates coates@physics.uq.edu.au from FunnelWeb
+ v3.0 by Ross N. Williams ross@guest.adelaide.edu.au
+
+ Version:
+ 3.0AC
+
+ Hardware:
+ MSDOS, Mac, VMS, Sun, OSF/1, Linux, Sys.V, OS/2.
+
+ Languages:
+ No restrictions.
+
+ Formatter:
+ Tex, LaTeX, or HTML.
+
+ Availability:
+ Anonymous ftp from
+ ftp.physics.uq.oz.au:/pub/funnelwebAC30.tar.gz
+
+ Readme:
+ With bundle above; for FunnelWeb manual see WWW page
+ www.physics.uq.oz.au:8001/people/coates/funnelweb.html
+
+
+ Description:
+ FunnelWeb 3.0AC is an enhanced version of FunnelWeb (see the
+ entry for FunnelWeb). FunnelWeb is designed to be typesetter
+ independent, though FunnelWeb v3.0 only supports (La)TeX as
+the
+ typesetter. FunnelWeb 3.0AC also supports HTML, and creates
+ appropriate hypertext links within the document among the code
+ sections. FunnelWeb 3.0AC also supports automatic and manual
+ insertion of line directives, so that compiler errors can be
+ flagged back to the original FunnelWeb source file. FunnelWeb
+ 3.0AC is completely compatible with FunnelWeb v3.0 sources
+(with
+ one minor exception; see the file README.ABC which comes with
+ the FunnelWeb 3.0AC distribution).
+
+
+ Support:
+ Supported by A.B.Coates coates@physics.uq.edu.au, subject to
+the
+ time constraints imposed by his thesis.
+
+
+ 9.7. LEO
+
+
+ Developer:
+ Edward K. Ream edream@mailbag.com
+
+ Version:
+ 1.0
+
+ Hardware:
+ Windows
+
+ Languages:
+ Unknown
+
+ Formatter:
+ Unknown
+
+ Availability:
+ Contact the author or see
+ www.mailbag.com/users/edream/front.html
+
+ Readme:
+ Unknown
+
+ Description:
+ See web site.
+
+ Support:
+ Unknown.
+
+
+ 9.8. Literate Programmer's Workshop (LPW)
+
+
+ Developer:
+ Norbert Lindenberg
+
+ Version:
+ 1.1
+
+ Hardware:
+ Apple Macintosh
+
+ Languages:
+ C++, Object Pascal & others
+
+ Formatter:
+ self-contained WYSIWYG system
+
+ Availability:
+ Anonymous ftp from:
+
+ o CTAN:/web/lpw
+
+ o ftp.apple.com:/pub/literate.prog
+
+ Readme:
+ With bundle above. Also comes with 38-page manual.
+
+
+ Description:
+ The Literate Programming Workshop is an environment for the
+ integrated development of program source text and
+documentation
+ in combined documents. It consists of a WYSIWYG word processor
+ based on a style sheet approach, a mechanism to extract parts
+of
+ the text in a document, and a project management system that
+ handles multi-document projects. The system is designed to be
+ used in conjunction with the Macintosh Programmer's Workshop:
+it
+ prepares raw source text for the MPW compilers, accepts MPW
+ error messages, and shows them in the context of the original
+ documents. Automatic indexing and hypertext features allow for
+ easy access to both source text and documentation.
+
+
+ LPW is shareware.
+
+
+ Support:
+ Bugs, problems, and questions to lpw@aol.com
+
+
+ 9.9. MapleWEB
+
+
+ Developer:
+ Unknown
+
+ Version:
+ Unknown
+
+ Hardware:
+ Unknown
+
+ Languages:
+ Maple
+
+ Formatter:
+ Unknown
+
+ Availability:
+ Anonymous ftp from CTAN/maple/mapleweb
+
+ Readme:
+ Unknown
+
+ Description:
+ None
+
+ Support:
+ Unknown
+
+
+
+
+
+ 9.10. Matlabweb
+
+
+ Developer:
+ Mark Potse
+
+ Version:
+ 2.09
+
+ Hardware:
+ any, but only Unix tested & supported
+
+ Languages:
+ Matlab
+
+ Formatter:
+ Plain TeX and LaTeX.
+
+ Availability:
+ Anonymous ftp from the CTAN archives,
+
+ Readme:
+ Bundled with above
+
+
+ Description:
+ CWEB-like literate programming system for the Matlab language.
+ Created with a modified version of the Spider system. Several
+ more or less language-specific features:
+
+ o macros with multiple arguments
+
+ o comments and verbatim comments
+
+ o strings can be formatted as code, with help for nested
+strings,
+ e.g. for callbacks in user interface programming.
+
+ o string arguments for macros, that get inserted in strings in
+the
+ replacement text
+
+ o "@f foo TeX" works as in recent versions of CWEB
+
+ Support:
+ not guaranteed. Try M.Potse@amc.uva.nl, comments are welcome.
+
+
+ 9.11. RWEB
+
+
+ Developer:
+ Unknown
+
+ Version:
+ Unknown
+
+ Hardware:
+ Unknown
+
+ Languages:
+ Unknown
+
+ Formatter:
+ Unknown
+
+ Availability:
+ Anonymous ftp from CTAN
+ Readme:
+ Unknown
+
+ Description:
+ Web generator in AWK.
+
+ Support:
+ Unknown
+
+
+ 9.12. SchemeWEB
+
+
+ Developer:
+ John D. Ramsdell
+
+ Version:
+ 2.1
+
+ Hardware:
+ Unix and DOS platforms
+
+ Languages:
+ Any dialect of Lisp.
+
+ Formatter:
+ LaTeX.
+
+ Availability:
+ The Unix version is in the Scheme Repository and it is
+available
+ via anonymous ftp from:
+
+ o cs.indiana.edu:/pub/scheme-repository/utl/schemeweb.sh
+
+ o CTAN:/tex-archive/web/schemeweb
+
+ o The DOS version is part of the PCS/Geneva Scheme system which
+is
+ available via anonymous ftp from: cui.unige.ch:/pub/pcs
+
+ Readme:
+ In bundle with above.
+
+ Description:
+ SchemeWEB is a Unix filter that allows you to generate both
+Lisp
+ and LaTeX code from one source file. The generated LaTeX code
+ formats Lisp programs in typewriter font obeying the spacing
+in
+ the source file. Comments can include arbitrary LaTeX
+commands.
+ SchemeWEB was originally developed for the Scheme dialect of
+ Lisp, but it can easily be used with most other dialects.
+
+ Support:
+ Bug reports to ramsdell@mitre.org.
+
+
+ 9.13. SpideryWEB
+
+
+ Developer:
+ Norman Ramsey <nr@eecs.harvard.edu>
+
+ Version:
+ Unknown
+
+ Hardware:
+ Unix and DOS platforms
+
+ Languages:
+ Most Algol-like languages, including C, Ada, Pascal, Awk, and
+ many others.
+
+ Formatter:
+ Plain TeX and latex for text formatters.
+
+ Availability:
+ Anonymous ftp from CTAN.
+
+ Readme:
+ In distribution.
+
+
+ Description:
+ A system for building language-dependent WEBs. Spider is
+frozen;
+ no further development is planned.
+
+
+ Support:
+ Bug reports to spider-bugs@oracorp.com.
+
+
+ 9.14. WEB
+
+
+ Developer:
+ Donald Knuth
+
+ Version:
+ 4.4 (apparently)
+
+ Hardware:
+ Any TeX system should have it.
+
+ Languages:
+ Pascal
+
+ Formatter:
+ TeX (of course! ;-)
+
+ Availability:
+ Distributed with TeX systems. Also avaliable in source form
+ from labrea.stanford.edu/tex/web.
+
+ Readme:
+ Unknown
+
+ Documentation:
+ Available from labrea.stanford.edu/tex/web/webman.tex
+
+ Description:
+ This is the original software that started it all. The
+original
+ TeX processor was written in WEB.
+
+ Support:
+ None known.
+
+
+ 9.15. WinWordWEB
+
+
+ Developer:
+ Lee Wittenberg leew@pilot.njin.net
+
+
+ Version:
+ Unknown
+
+ Hardware:
+ Needs Microsoft Word for Windows, v.2.x, and, of course, MS-
+ Windows 3.x.
+
+ Languages:
+ Any programming language.
+
+ Formatter:
+ Word for Windows 2.x for text formatting and file maintenance.
+
+ Availability:
+ samson.kean.edu:pub/leew
+
+ Readme:
+ WORDWEB.DOC in the downloadable package describes the system.
+
+ Description:
+ WinWordWEB is a set of a Word for Windows macros (plus a
+ paragraph style) that provide a crude literate programming
+ environment. The ``look and feel'' of the system is based on
+ Norman Ramsey's noweb, but can easily be modified to suit
+ individual tastes.
+
+ Support:
+ None. WinWordWEB was written as a prototype to see if a
+WYSIWYG
+ literate programming system was possible. It is intended as a
+ jumping off point for future work by others. However, the
+system
+ is surprisingly usable as it stands, and the author is
+ interested in hearing from users (satisfied and dissatisfied).
+
+
+ Anyone interested in actively supporting (and improving) the
+ product should contact the author via email.
+
+
+
+ 10. Are there other tools I should know about?
+
+ Follows is a list of some not-quite-literate-programming tools.
+Some
+ term these pretty-printers. Others may call them literate
+programming
+ tools. In any event, they don't seem to be quite in the same
+category
+ as the tools listed above, so I'll include them here.
+
+
+ 10.1. C2LaTeX
+
+
+ Developer:
+ John D. Ramsdell
+
+ Version:
+ Unknown
+
+ Hardware:
+ Unix
+
+ Languages:
+ C
+
+ Formatter:
+ LaTeX but it's easy to change the formatter.
+
+
+ Availability:
+ Anonymous ftp from omnigate.clarkson.edu:/pub/tex/tex-
+ programs/c2latex.
+
+ Readme:
+ Absent. Documentation is in the C source for c2latex.
+
+ Description:
+ C2latex provides simple support for literate programming in C.
+ Given a C source file in which the comments have been written
+in
+ LaTeX, c2latex converts the C source file into a LaTeX source
+ file. It can be used to produce typeset listings of C
+programs
+ and/or documentation associated with the program.
+
+ C2latex produces LaTeX source by implementing a small number
+of
+ rules. A C comment that starts at the beginning of a line is
+ copied unmodified into the LaTeX source file. Otherwise, non-
+ blank lines are surrounded by a pair of formatting commands
+ (\begin{flushleft} and \end{flushleft}), and the lines are
+ separated by \\*. Each non-blank line is formatted using
+LaTeX's
+ \verb command, except comments within the line are formatted
+in
+ an \mbox.
+
+ Support:
+ Send bug reports to ramsdell@mitre.org.
+
+
+ 10.2. c2cweb
+
+
+ Developer:
+ Werner Lemberg
+
+ Version:
+ 1.5
+
+ Hardware:
+ DOS, OS/2, Unix (gcc) - CWEB source included
+
+ Languages:
+ C, C++
+
+ Formatter:
+ TeX
+
+ Availability:
+ Anonymous ftp from CTAN:/web/c_cpp/c2cweb
+
+ Readme:
+ In distribution.
+
+ Description:
+ c2cweb will transform plain C or C++ code into a CWEB file to
+ get a pretty formatted output. A modified CWEAVE (which
+ transforms the CWEB file into a TeX file, see below) is
+included
+ also.
+
+ Support:
+ Werner Lemberg <a7971428@unet.univie.ac.at>
+
+
+ 10.3. c2man
+
+
+ author:
+ Graham Stoney <greyham@research.canon.oz.au>
+ language:
+ C, nroff, texinfo, latex, html
+
+ version:
+ 2.0 patchlevel 33
+
+ parts:
+ documentation generator (C -> nroff -man, -> texinfo, ->latex,
+ -> html)
+
+ location:
+ ftp from
+
+ o any comp.sources.misc archive, in volume42 (the version in the
+ comp.sources.reviewed archive is obsolete)
+
+ o dnpap.et.tudelft.nl/pub/Unix/Util/ c2man-2.0.*.tar.gz
+
+ o Australia archie.au/usenet/comp.sources.misc/volume42
+ c2man-2.0/*
+
+ o N.America ftp://ftp.wustl.edu/usenet/comp.sources.misc/volume4
+2/
+ c2man-2.0/*
+
+ o Europe: ftp://ftp.irisa.fr/News/comp.sources.misc/volume42/
+ c2man-2.0/*
+
+ o Japan:
+ ftp://ftp.iij.ad.jp/pub/NetNews/comp.sources.misc/volume42/
+ c2man-2.0/*
+
+ Patches:
+ lth.se/pub/netnews/sources.bugs/volume93/sep/c2man*
+
+ description:
+ c2man is an automatic documentation tool that extracts
+comments
+ from C source code to generate functional interface
+ documentation in the same format as sections 2 & 3 of the Unix
+ Programmer's Manual. It requires minimal effort from the
+ programmer by looking for comments in the usual places near
+the
+ objects they document, rather than imposing a rigid function-
+ comment syntax or requiring that the programmer learn and use
+a
+ typesetting language. Acceptable documentation can often be
+ generated from existing code with no modifications.
+
+ conformance:
+ supports both K&R and ISO/ANSI C coding styles
+
+ features:
+
+ o generates output in nroff -man, TeXinfo, LaTeX or HTML format
+
+ o handles comments as part of the language grammar
+
+ o automagically documents enum parameter & return values
+
+ o handles C (/* */) and C++ (//) style comments
+
+ o doesn't handle C++ grammar (yet)
+
+ requires:
+ yacc/byacc/bison, lex/flex, and nroff/groff/texinfo/LaTeX.
+
+ ports:
+ Unix, OS/2, MSDOS, VMS.
+
+ portability:
+ very high for unix, via Configure
+
+ status:
+ actively developed; contributions by users are encouraged.
+
+ discussion:
+ via a mailing list: send "subscribe c2man <Your Name>" (in the
+ message body) to listserv@research.canon.oz.au
+
+ help:
+ from the author and other users on the mailing list:
+ c2man@research.canon.oz.au
+
+ announcements:
+ patches appear first in comp.sources.bugs, and then in
+ comp.sources.misc.
+
+ updated:
+ 1994/10/07
+
+
+ 10.4. cnoweb
+
+
+ Developer:
+ Jim Fox
+
+ Version:
+ 1.4 (January 4, 1991)
+
+ Hardware:
+ Anything with C and TeX.
+
+ Languages:
+ C
+
+ Formatter:
+ Plain TeX.
+
+ Availability:
+ Anonymous ftp from:
+
+ o CTAN
+
+ o LPA:/c.c++
+
+ Readme:
+ Unknown, cnoweb.tex contains documentation.
+
+ Description:
+ cnoweb is as it's name describes: write C, not web. No
+tangling
+ or weaving is implemented. Documentation (between standard /*
+ */ delimiteres) is written in TeX. cnoweb provides
+typesetting
+ of documentation, an table of contents of routines, and
+pretty-
+ printing of C source.
+
+ Support:
+ None known.
+
+
+ 10.5. dpp
+
+
+ Developer:
+ Dan Schmidt <dfan@alum.mit.edu>
+ Version:
+ 0.2.1
+
+ Hardware:
+ Any platform with Perl 5
+
+ Languages:
+ C/C++ (Java soon), under noweb
+
+ Formatter:
+ LaTeX
+
+ Availability:
+ www.dfan.org/real/dpp.nw
+
+ Readme:
+ www.dfan.org/real/dpp.html
+
+ Support:
+ email to the author <dfan@alum.mit.edu>
+
+ Description:
+ dpp is a C/C++ prettyprinter for noweb. Its output is
+extremely
+ similar to that of CWEB, but it respects the indentation and
+ line breaks of the source file.
+
+ Features include:
+
+ o user-defined keywords
+
+ o the ability to turn prettyprinting off for specified output
+ files (e.g., makefiles)
+
+ o the option to typeset comments in TeX, or not
+
+ o prettyprinting of quoted code, in documentation or chunk names
+
+ o the ability to undo whitespace hand-formatting that looks good
+ monospaced but awful in a proportional font
+
+
+
+ 10.6. Fold2Web
+
+
+ Developer:
+ Bernhard Lang lang@tu-harburg.d400.de
+
+ Version:
+ V0.8
+
+ Hardware:
+ MSDOS
+
+ Languages:
+ All (must allow comment lines)
+
+ Formatter:
+ LaTeX
+
+ Availability:
+ Anonymous ftp from: kirk.ti1.tu-harburg.de (134.28.41.50)
+ /pub/fold2web/readme /pub/fold2web/fold2web.zip
+
+ Readme:
+ In distribution
+ Description:
+ The idea behind the Fold2Web tool is the following: A
+programmer
+ can write his program source with a folding editor and later
+map
+ the folded source files automatically to WEB-files. The
+ generated WEB-files can then be modified by inserting required
+ documentations.
+
+
+ The advantage by starting program developement with original
+ sources is to get short design cycles during the compile/debug
+ steps. By using a folding editor the global structuring
+ information can be already captured in folds during this
+ developement phase. Fold information is typically stored in
+ comment lines and thus will not affect the efficiency of the
+ compile/debug design cycle.
+
+
+ Some folding editors and a folding mode for the emacs are
+ available (e.g. see our FUE folding editor for MSDOS machines
+ which is a modified micro emacs. Pick it at kirk in directory
+ /pub/fold2web).
+
+
+ After reaching a stable version of a program source its time
+to
+ convert the source file to a WEB-file and do the program
+ documentation. Fold2Web is written to convert folded source
+ text of any programming language to nuweb files. The folded
+ structure is kept by mapping folds to scraps. Fold markers
+which
+ differ between languages due to different ways of specifying
+ comments can be configured for each language.
+
+
+ Good results can also achived when given but poor documented
+ program sources have to be modified. Such sources can be
+folded
+ using a folding editor to extract the global structures. This
+ offers a global view to the program structures and help to
+ understand its functionality. Furthermore the program code is
+ not affected, only comment lines are inserted. Once folded the
+ program source can be automatically translated to a WEB
+document
+ using the above tool.
+
+
+ Support:
+ email to lang@tu-harburg.d400.de
+
+
+ 10.7. Funnelweb Mode
+
+
+ Developer:
+ Daniel Simmons simmdan@kenya.isu.edu
+
+ Version:
+ Unknown
+
+ Availability:
+ www.miscrit.be/~ddw
+
+
+ Description:
+ The other day I did a quick hack to nuweb.el as included with
+ the nuweb distribution so as to make a funnelweb-mode.el.
+I've
+ only used it briefly, and I'm sure that it can be improved
+quite
+ a bit. I've been thinking about adding support for folding on
+ sections, a pull-down menu to select macro definitions (like
+the
+ recent functions posted to gnu.emacs.sources for a C function
+ definition pull-down menu) and some kind of tags support for
+ funnelweb.
+
+
+ Support:
+ Unknown
+
+
+ 10.8. noweb.el
+
+
+ Developer:
+ Bruce Stephens (no email contact)
+
+ Version:
+ Unknown.
+
+ Availability:
+ Lost
+
+ Description:
+ This is a very simple mode I just hacked up. There's a lot
+ wrong with it, but I thought others may be interested, even as
+ it stands. It *requires* text properties, and assumes those
+ used in GNU Emacs 19.22; it'll quite likely work with Lucid
+ Emacs, but I haven't tried it.
+
+
+ I use it with auctex8.1 and cc-mode 3.229, both of which are
+ loaded separately (I think my emacs is dumped with them, in
+ fact).
+
+
+ The idea is to have one mode (which calls itself c-mode, but
+ actually has LaTeX-mode keybindings) generally (this means
+that
+ the code is hilighted nicely), and have the code chunks use a
+ different keymap.
+
+ Support:
+ Unknown
+
+
+ 10.9. noweb-outline.el
+
+
+ Developer:
+ Dan Schmidt dfan@alum.mit.edu
+
+ Version:
+ 0.0.3
+
+ Hardware:
+ Any platform with Emacs
+
+ Languages:
+ noweb
+
+ Availability:
+ www.dfan.org/real/noweb-outline.el
+
+ Readme:
+ www.dfan.org/real/noweb-outline.html
+
+ Support:
+ email to the author, dfan@alum.mit.edu
+
+ Description:
+ noweb-outline.el is a mode for Emacs that allows you to easily
+ navigate the chunk tree of a noweb program.
+
+
+ One of the problems with literate programming is that it's
+easy
+ to lose track of how your tangled source file (the one that
+the
+ compiler actually sees) is structured. In noweb-outline-mode,
+ you can interactively explore the tree of chunks you are
+ creating, giving you the big picture as well as the small.
+ Enough description; it would take more time for me to explain
+it
+ than for you to just go ahead and try it out.
+
+
+ noweb-outline.el is currently in an alpha state (I've worked
+on
+ it for only a couple of days), but it is already very useful.
+A
+ nice file to use to try it out is example/wc.nw in the noweb
+ distribution.
+
+
+ 10.10. nuweb.el
+
+
+ Developer:
+ Dominique de Waleffe ddw@acm.org
+
+ Version:
+ 1.99
+
+ Availability:
+ Anonymous ftp from CTAN
+
+
+ Description:
+ Provides a major mode extending Auctex for editing nuweb
+files.
+ Main features (in 2.0):
+
+ o Edit scrap bodies in a separate buffer in a different mode
+ (selected using emacs defaults for files, specific indication
+ -*-mode-*-, or a buffer-local variable)
+
+ o Extends Auctex commands so that nuweb is called before LaTeX,
+
+ o Easy navigation on scrap definition and use points.
+
+ o Now creates an imenu (C-M-mouse1) with user index entries,
+macro
+ definition positions and file definition positions.
+
+
+ Support:
+ Email to ddw@acm.org
+
+
+ 10.11. Web mode
+
+
+ Developer:
+ Bart Childs bart@cs.tamu.edu
+
+ Version:
+ Unknown
+
+ Tools supported:
+ web, fweb, cweb, funnelweb
+
+
+ Availability:
+ Anonymous ftp ftp.cs.tamu.edu:pub/tex-web/web/EMACS.web-mode
+ thrain.anu.edu.au:pub/web/EMACS.web-mode
+
+ Description:
+ This version works with versions 18 and 19 of Emacs to be best
+ of my knowledge. I have cleaned up a number of documentation
+ items ... In the same directory is wm_refcard.tex which is an
+ edited version of the famous one to include some web-mode
+ commands.
+
+
+ The files limbo* are related to its use and notice that half
+ them have an uppercase L in them for LaTeX. The setup is
+based
+ upon the fact that we (I am not alone here) primarily use FWEB
+ for C and Fortran programming.
+
+
+ We are using version 1.40 of FWEB although John Krommes warns
+ that it is not mature and the manual is not yet updated. The
+ info files are! We are using LaTeX almost exclusively. That
+ will likely change and we will revert to version 1.30 if the
+ final form of 1.40 cannot return to the simple section numbers
+ and avoid the HORRIBLE LATEX 0.1.7.2.4.6 type section numbers.
+
+ Support:
+ Unknown
+
+
+ 11. What other resources are available?
+
+ 11.1. TeX Resources
+
+ Another resource of interest to literate programmers is the
+ comp.text.tex newsgroup. If you're using (La)TeX as your
+typsetting
+ system and have access to internet, then you should investigate this
+ resource.
+
+ Another reason the TeX resources should be important is that so many
+ of the literate programming tools rely on either plain TeX or LaTeX
+as
+ their text formatter. (La)TeX software systems exist for most
+ computing platforms. These systems can be found on CTAN and other
+ major archive sites. Use archie to find them or simply ftp to one
+of
+ the CTAN sites and browse.
+
+
+
+ 12. Are there any code examples?
+
+ Examples of web programs are included with the FWEB, CWEB, and noweb
+ distributions. nuweb is written in itself.
+
+ Cameron Smith converted the K&R calculator program into a literate
+ program. It can be retrieved by anonymous ftp from:
+
+ niord.shsu.edu [192.92.115.8] directory kr-cweb-sample as
+ krcwsamp.zip
+ or from
+ LPA/Documentation
+
+
+ Ross Williams has released a funnelweb example. You can retrieve
+this
+ file from node ftp.adelaide.edu.au [129.127.40.3] as
+
+ /pub/funnelweb/examples/except.*
+
+ This file should be on CTAN as well.
+
+ Lee Wittenberg has posted a few litprog examples. They are
+available
+ via anonymous ftp from:
+
+ ftp://samson.kean.edu/pub/leew/samples.LP
+
+
+ The Stanford GraphBase is a large collection of programs by Don
+Knuth
+ for doing all kinds of computations and games with graphs; it is
+writ-
+ ten in (Levy/Knuth) CWEB. More details in the distribution. It is
+ available via anonymous ftp from:
+
+ labrea.stanford.edu:/pub/sgb
+
+
+
+
+
+ 13. Bibliographies
+
+ Nelson Beebe has collected an extensive bibliography treating
+literate
+ programming. His work is available for anonymous ftp from
+ ftp://ftp.math.utah.edu/pub/tex/bib/index.html#litprog. Be sure to
+ look around this site; there are many things of interest to user of
+ TeX resources as well as literate programmers.
+
+ Although I have not verified this, LPA is an alternate source for
+ these files. Note that they are updated frequently (Nelson says
+ several times each week), so be sure to get a fresh copy before
+ extensive use. Joachim Schrod indicates that these files may be
+ updated daily and can be retrieved via anonymous ftp at
+ LPA/documentation.
+
+
+
+ 14. Other Opinions about Literate Programming
+
+
+
+ 14.1. van Ammers
+
+ An author (Eric W. van Ammers) wrote me a short article treating his
+ opinions on literate programming.
+
+ First observation on LP
+
+ About 90% of the disussion on this list is about problems with
+ applying some WEB-family member to a particular programming language
+ or a special documentation situation. This is ridiculous, I think.
+ Let me explain shortly why.
+
+ Lemma 1:
+
+ I have proposed for many years that programming has nothing to do
+with
+ programming langauges, i.e. a good programmer makes good programs in
+ any language (given some time to learn the syntax) and a bad
+ programmer will never make a good program, no matter the language he
+ uses (today many people share this view, fortunately).
+
+ Lemma 2:
+
+ Literate Programming has (in a certain way not yet completely
+ understood) to do with essential aspects of programming.
+
+
+ Conclusion 1:
+
+ A LP-tool should be independent of programming language.
+
+ Lemma 3:
+
+ It seems likely that the so called BOOK FORMAT PARADIGM [ref. 1]
+plays
+ an important role in making literate programs work.
+
+ Lemma 4:
+
+ There are very many documentation systems currently being used to
+ produce documents in the BOOK FORMAT.
+
+ Conclusion 2:
+
+ A LP-tool should be independent of the documentation system that the
+ program author whishes to use.
+
+ My remark some time ago that we should discuss the generic
+properties
+ of an LP-tool was based on the above observation.
+
+ References:
+
+ [1] Paul W. Oman and Curtus Cook. ``Typographical style is more than
+ cosmetic.'' CACM 33, 5, 506-520 (May 1990)
+
+ Second observation on LP
+
+ The idea of a literate program as a text book should be extendend
+even
+ further. I would like to see a literate program as an (in)formal
+ argument of the correctness of the program.
+
+ Thus a literate program should be like a textbook on mathematicics.
+ A
+ mathematical textbook explains a theory in terms of lemma and
+ theorems. But the proofs are never formal in the sense that they are
+ obtaind by symbol manipulation of a proof checker. Rather the proofs
+ are by so called ``informal rigour'', i.e. by very precise and
+ unambiguous sentences in a natural language.
+
+ Eric W. van Ammers <ammers@rcl.wau.nl>
+
+
+
+ 14.2. Ramsey
+
+ Another author (Norman Ramsey) wrote me and asked that his opinions
+be
+ included in the FAQ. What follows are Norman's comments verbatim.
+
+ I see it's time for the ``how is literate programming different from
+ verbose commenting'' question. Perhaps David Thompson will get this
+ into the FAQ. Alert! What follows are my opinions. In no way do I
+ claim to speak for the (fractious) literate-programming community.
+
+ How is literate programming different from verbose commenting?
+
+ There are three distinguishing characteristics. In order of
+ importance, they are:
+
+ 1. flexible order of elaboration
+
+ 2. automatic support for browsing
+
+ 3. typeset documentation, especially diagrams and mathematics
+
+
+ Flexible order of elaboration means being able to divide your source
+ program into chunks and write the chunks in any order, independent
+of
+ the order required by the compiler. In principle, you can choose
+the
+ order best suited to explaining what you are doing. More subtly,
+this
+ discipline encourages the author of a literate program to take the
+ time to consider each fragment of the program in its proper sphere,
+ e.g., not to rush past the error checking to get to the ``good
+ parts.'' In its time and season, each part of the program is a good
+ part. (This is the party line; your mileage may vary.)
+
+ I find the reordering most useful for encapsulating tasks like input
+ validation, error checking, and printing output fit for humans ---
+all
+ tasks that tend to obscure ``real work'' when left inline.
+Reordering
+ is less important when using languages like Modula-3, which has
+ exceptions and permits declarations in any order, than when using
+ languages like C, which has no exceptions and requires declaration
+ before use.
+
+ Automatic support for browsing means getting a table of contents,
+ index, and cross-reference of your program. Cross-reference might
+be
+ printed, so that you could consult an index to look up the
+definition
+ of an identifier `foo'. With good tools, you might get a printed
+ mini-index on every page if you wanted. Or if you can use a
+hypertext
+ technology, cross-reference might be as simple as clicking on an
+ identifier to reach its definition.
+
+ Indexing is typically done automatically or `semi-automatically',
+the
+ latter meaning that identifier definitions are marked by hand.
+ Diligently done semi-automatic indexes seem to be best, because the
+ author can mark only the identifiers he or she considers important,
+ but automatic indexing can be almost as good and requires no work.
+ Some tools allow a mix of the two strategies.
+
+ Some people have applied literate-programming tools to large batches
+ of legacy code just to get the table of contents, index, and cross-
+ reference.
+
+ I don't use diagrams and mathematics very often, but I wouldn't want
+ to have to live without them. I have worked on one or two projects
+ where the ability to use mathematical formulae to document the
+program
+ was indispensible. I also wouldn't like to explain some of my
+ concurrent programs without diagrams. Actually I write almost all
+of
+ my literate programs using only sections headers, lists, and the
+ occasional table.
+
+
+ >Wouldn't it be easier to do one's literate programming using
+ >a wysiwyg word processor (e.g. Word for Windows) and
+ >indicate what is source code by putting it in a different
+ >font?
+
+
+
+ The data formats used in wysiwyg products are proprietary, and they
+ tend to be documented badly if at all. They are subject to change
+at
+ the whim of the manufacturer. (I'll go out on a limb and say there
+are
+ no significant wysiwyg tools in the public domain. I hope the
+Andrew
+ people will forgive me.) These conditions make it nearly impossible
+to
+ write tools, especially tools that provide automatic indexing and
+ cross-reference support. The CLiP people have a partial solution
+that
+ works for tools that can export text --- they plant tags and
+ delimiters throughout the document that enable the reordering
+ transformation (``tangling'').
+
+ People use TeX, roff, and HTML because free implementations of these
+ tools are widely available on a variety of platforms. TeX and HTML
+ are well documented, and TeX and roff are stable. TeX is the most
+ portable. I think I have just answered the FAQ ``how come all these
+ tools use TeX, anyway?'' :-)
+
+ Norman Ramsey
+
+
+
+ 14.3. My (Dave Thompson's) Experience
+
+ In contrast to Eric's and Norman's comments, I'd like to interject
+ from an anecdotal perspective.
+
+ I first ran across the idea of literate programming in 1992 while
+ poking around George Greenwade's TeX archive (at niord.shsu.edu) and
+ stumbling on some of the tools. My first experience was tinkering
+ with cnoweb, see Section ``cnoweb''. I used cnoweb to document a
+ simple Bernoulli equation toy I built (in C) while working on a one-
+ dimensional hydrodynamic model (in Fortran). I was convinced that
+ literate programming had promise (although cnoweb really qualifies
+as
+ a pretty-printing tool).
+
+ After reading Sewell's book, I kept hunting through the tools
+ available until I found things that worked for me. (More here as I
+ have time to develop the story.)
+
+
+
+ 14.4. Others
+
+ I recently received email from Dave Johnson <scope@faroc.com.au>
+about
+ his work developing language independent techniques. The web site
+is
+ www.dscope.com.au.
+
+
+
+ 15. How to anonymously ftp
+
+ Pretty much everything mentioned here is available by anonymous FTP.
+ FAQ lists cross-posted to news.answers and rec.answers can be gotten
+ from rtfm.mit.edu [18.181.0.24], under /pub/usenet/news.answers or
+ under /pub/usenet/more.specific.group.name
+
+ "anonymous FTP" is just a way for files to be stored where anyone
+can
+ retrieve them over the Net. For example, to retrieve the latest
+ version of the literate programming FAQ, do the following:
+
+ > ftp rtfm.mit.edu /* connect to the site; message
+follows */
+ > anonymous /* type this when it asks for your
+name */
+ > <your email address> /* type your address as the
+password */
+ > cd /pub/usenet /* go to the directory you want to
+be */
+ > cd comp.programming.literate /* one level down (no slash).
+ */
+ > dir /* look at what's there
+ */
+ > get literate-progamming-faq /* get the file; case-sensitive
+ */
+ > quit /* stop this mysterious thing
+ */
+
+
+ If your FTP program complains that it doesn't know where the site
+you
+ want to use is, type the numerical address instead of the sitename:
+
+ > ftp 18.181.0.24 /* connect with numerical address */
+
+
+ If you don't have ftp access, send e-mail to mail-server@rtfm.mit.ed
+u
+ with the single word "help" in the body of the message.
+
+ Getting binary files (executables, or any compressed files) is only
+ slightly more difficult. You need to set binary mode inside FTP
+ before you transfer the file.
+
+ > binary /* set binary transfer mode */
+ > ascii /* set back to text transfer mode */
+
+
+ FAQs and spoiler lists are generally ascii files; everything else is
+ generally binary files.
+
+ Some common extensions on binary files in archive sites are:
+
+ .Z Compressed; extract with uncompress
+ .tar.Z Compressed 'tape archive'; uncompress then untar or
+tar -xvf
+ .gz or .z Gnu gzip; use gunzip (available from
+prep.gnu.ai.mit.edu)
+ .sit (Mac) StufIt archive
+ .zip Extract with Zip or Unzip
+ .zoo Yet another archive/compress program
+ .lhe (Amiga) ?
+ .lzh Lha archive program.
+ .arj (PC) Arj archive program.
+ .exe (PC) Sometimes self-extracting archives-just execute
+them.
+ .uue or .UUE Transfer as text file; use uudecode to convert to
+binary
+ .hqx (Mac) BinHex format; transfer in text mode
+
+
+ Generic help can be found in the FAQs of comp.binaries. <your_sys-
+ tem_type> for how to transfer, extract, and virus-check binary
+files.
+ (At rtfm.mit.edu)
+
+ If you can't FTP from your site, use one of the following
+ftp-by-mail
+ servers:
+
+ ftpmail@decwrl.dec.com
+ ftpmail@src.doc.ic.ac.uk
+ ftpmail@cs.uow.edu.au
+ ftpmail@grasp.insa-lyon.fr
+
+
+ For complete instructions, send a message reading "help" to the
+ server.
+
+ If you don't know exactly what you're looking for, or exactly where
+it
+ is, there are programs and servers that can help you. For more
+info,
+ send e-mail to mail-server@rtfm.mit.with with the body of the
+message
+ reading send usenet/news.answers/finding-sources
+
+
+ Thanks to Aliza R. Panitz (the "buglady") for this text. I copied
+it
+ verbatim from her post on faq-maintainers with only minor
+ modifications.
+
+
+
+ 16. Acknowledgements
+
+ This document would not have happened without the help of many
+people.
+ George Greenwade was instrumental in establishing the original
+mailing
+ list way back in the early '90's (when I first became involved).
+ Marcus Speh started one of the early ftp sites and was an active
+ participant. Among them are, Rob Beezer, Joachim Schrod, Piet van
+ Oostrum, Ross N. Williams, Nelson H. F. Beebe, and Andrew Johnson.
+We
+ wouldn't have literate programming if it wasn't for Donald Knuth and
+ TeX. Certainly, we wouldn't be where we are without the tool
+ developers (all credited in their entries above).
+ Cesar Bellardini cballard@santafe.com.ar deserves thanks for
+ translating the FAQ into Spanish.
+
+ A special thanks to Aliza R. Panitz for the text describing how to
+ execute an anonymous ftp for files of interest.
+
+ Any omissions from these acknowledgements should be considered an
+ accident on my part. Furthermore, participants in the
+ comp.programming.literate newsgroup all contributed in various
+ fashions. Thank all of you.
+
+
+
+ 17. End notes
+
+ This document remains in a state of evolution (although I'm a strict
+ creationist! <grin>). I'm working on the SGML version to improve
+ formatting of the resulting documents. I'm also reorganizing the
+FAQ
+ to improve its usability. Comments are solicited for such
+ improvements. Omission of a particular tool should not be
+considered
+ a snub in any sense--simply an error or oversight on my part.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/help/ctan/CTAN-upload-addendum.html b/help/ctan/CTAN-upload-addendum.html
new file mode 100644
index 0000000000..7673be2cbd
--- /dev/null
+++ b/help/ctan/CTAN-upload-addendum.html
@@ -0,0 +1,1515 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <title>Additional Information for CTAN Uploaders</title>
+ <!--
+ <link rel="stylesheet" type="text/css" href="tugstyle.css" />
+ -->
+ <link rel="stylesheet" type="text/css" href="https://www.tug.org/tugstyle.css" />
+ <meta name="author" content="Petra R&uuml;be-Pugliese" />
+ <meta name="date" content="2019-04-22" />
+ <meta http-equiv="content-type" content="text/html; charset=us-ascii" />
+ <style type="text/css">
+ .highlight { color:navy;}
+ .abstandoben { margin-top:1em;}
+ .kleinerabstandoben { margin-top:0.8ex;}
+ </style>
+ </head>
+
+ <body>
+
+ <!-- ======================================================== -->
+
+ <h1>
+ Additional Information for CTAN Uploaders
+ </h1>
+
+ <p>
+ Before studying these <em>additional</em>
+ notes,
+ you should have read and understood
+ the following
+ <a id="basictexts">basic texts</a>:
+ </p>
+
+ <ol style="list-style-type:lower-alpha;">
+ <li>
+ CTAN&apos;s help page
+ &ldquo;<a href="https://ctan.org/help/upload-pkg">How can I upload a package?</a>&rdquo;,
+ </li>
+ <li>
+ the
+ <a href="https://tug.org/texlive/pkgcontrib.html">
+ TeX Live instructions</a>, and
+ </li>
+ <li>
+ the corresponding
+ <a href="http://www.tex.ac.uk/FAQ-uploads.html">
+ article of the UK TeX FAQ</a>.
+ </li>
+ </ol>
+
+ <p>
+ The following paper tries to give some
+ <a href="#backgroundinfo">background information about CTAN itself</a>,
+ followed by a list of more aspects we ask you keep in mind when
+ <a href="#uploadpreparation">preparing your upload</a>,
+ some hints about
+ <a href="#uploading">how to use the upload form</a>
+ and finally information about
+ <a href="#furtherprocessing">what will happen to your
+ submission</a>
+ once it has arrived at our place.
+ </p>
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <h2>
+ <a id="backgroundinfo">Some background information</a>
+ </h2>
+
+ <h3>
+ <a id="networkstructure">Structure of the network</a>
+ </h3>
+
+ <p>
+ The
+ <span class="highlight">Comprehensive TeX Archive Network</span>
+ consists of
+ <a id="centralserver">
+ <span class="highlight">a central server</span>
+ </a>
+ at Cologne in Germany and a great number of
+ <a href="http://dante.ctan.org/mirmon/">mirrors</a>
+ all over the world.
+ </p>
+ <p>
+ All these servers should in principle present
+ the same content
+ &ndash;
+ an ideal that is of course regularly disturbed
+ with every installation of a new upload;
+ but every mirror should synchronize with
+ the central server once every day,
+ so that the approximation to that ideal is
+ indeed quite close.
+ </p>
+
+ <h3>
+ <a id="archivestructure">Structure of the archive</a>
+ </h3>
+
+ <p>
+ The greater part of the archive
+ is taken up by what we refer to as the
+ <a id="unpackedtree"></a>
+ &ldquo;<a href="http://mirror.ctan.org/">unpacked tree</a>&rdquo;.
+ It is meant for being visited by means of a
+ <span class="highlight">browser</span>.
+ To make this not too painful an experience,
+ the individual subtrees of this part of the
+ archive are required to be
+ <a id="flatstructure">
+ <em>as &ldquo;flat&rdquo; as possible</em>,
+ </a>
+ i.e. they should contain as few directory levels
+ as possible,
+ regardless of the position of the individual files
+ in a &ldquo;real&rdquo; TeX system.
+ <br/>
+ We do however not impose any definite
+ upper limit on the number of directory levels
+ in a package&apos;s layout
+ as there seems to be no upper bound to
+ packages&apos; complexity.
+ Please <a href="#ctanemail">contact</a> the CTAN team
+ for advice if your package is very complex
+ and you are in doubt about how best to arrange
+ your material.
+ </p>
+ <p>
+ In addition to this there is what we call the
+ <a id="installtree"></a>
+ &ldquo;<a href="http://mirror.ctan.org/install/">install tree</a>&rdquo;,
+ which is a collection of
+ <a href="https://tug.org/texlive/pkgcontrib.html#advanced">
+ <tt>.tds.zip</tt> files</a>.
+ </p>
+ <p>
+ Please note that
+ <a id="unpackednecessary">
+ every package on the archive
+ <em>must</em> be present in the
+ &ldquo;unpacked&rdquo; part.
+ </a>
+ The <tt>.tds.zip</tt> files are optional additions
+ that may be useful for big and complex packages,
+ but are in no way required by the CTAN team,
+ whereas we <em>do not accept</em>
+ uploads that contain nothing but
+ a <tt>.tds.zip</tt> file.
+ </p>
+
+ <h3>
+ <a id="urls">URLs</a>
+ </h3>
+
+ <p>
+ There are many ways of referring to
+ CTAN packages on the internet,
+ but our <em>preferred</em>,
+ <a id="canonicalurls1">
+ &ldquo;canonical&rdquo; ones
+ </a>
+ are of the following form:
+ </p>
+
+ <ol style="list-style-type:lower-alpha;">
+ <li>
+ <tt style="font-weight:bold;">https://ctan.org/pkg/&hellip;</tt>
+ (where the &ldquo;&hellip;&rdquo; equal the
+ &ldquo;<a href="#packageids">package id</a>&rdquo;)
+ if you are interested in <em>information about</em>
+ the package, and
+ </li>
+
+ <li>
+ <tt style="font-weight:bold;">http://mirror.ctan.org/&hellip;</tt>
+ (where the &ldquo;&hellip;&rdquo; equal the &ldquo;path&rdquo;
+ to the package&apos;s files on the archive)
+ if you are interested in the package itself.
+ </li>
+ </ol>
+
+ <p>
+ <a id="tex-archive-deprecated">
+ In particular, URLs containing the string
+ &ldquo;<tt>tex-archive</tt>&rdquo;
+ are generally &ldquo;suspicious&rdquo;,
+ </a>
+ because they usually refer to the
+ <a href="#centralserver">central server</a>,
+ and we try desperately to redirect
+ download demands from the
+ central server to the mirrors.
+ Moreover, the individual servers and their addresses
+ may change over the times,
+ whereas these &ldquo;canonical URLs&rdquo;
+ are intended to be permanent.
+ </p>
+
+ <h3>
+ <a id="ctanteam">The CTAN team</a>
+ </h3>
+
+ <p>
+ At the moment, the following persons
+ (in alphabetical order)
+ take care of CTAN:
+ </p>
+
+ <ul>
+ <li>
+ <strong>Erik Braun</strong>
+ (upload management),
+ </li>
+ <li>
+ <strong>Ina Dau</strong>
+ (upload management),
+ </li>
+ <!--
+ <li>
+ <strong>Robin Fairbairns</strong>
+ (Catalogue specialist),
+ </li>
+ -->
+ <li>
+ <strong>Manfred Lotz</strong>
+ (upload management),
+ </li>
+ <li>
+ <strong>Gerd Neugebauer</strong>
+ (web developer),
+ </li>
+ <li>
+ <strong>Petra R&uuml;be-Pugliese</strong>
+ (upload management),
+ </li>
+ <li>
+ <strong>Rainer Sch&ouml;pf</strong>
+ (system administration
+ and supervision of mirrors),
+ </li>
+ <li>
+ <strong>Joachim Schrod</strong>
+ (system administration).
+ </li>
+ </ul>
+
+ <p>
+ All these people are acting
+ as <em>volunteers</em>
+ in their spare time;
+ so please do not get impatient
+ if your request does not receive
+ an immediate answer:
+ they may be held up by
+ &ldquo;real life&rdquo; problems
+ or a sudden inrush of other uploads.
+ </p>
+
+
+
+ <h3>
+ <a id="ctanemail">Email address</a>
+ </h3>
+
+ <p>
+ All CTAN-related correspondence should
+ be directed
+ <em>in English</em>
+ to
+ <tt style="font-weight:bold;">ctan (at) ctan (dot) org</tt>,
+ the common email address of
+ all &ldquo;CTAN people&rdquo;,
+ <!--
+ concerned with upload management or system administration,
+ -->
+ rather than to an individual maintainer.
+ This way
+ (a) the whole team is informed about what is going on
+ and
+ (b) you are more likely to receive a fairly <em>quick</em>
+ response to your enquiry.
+ (Always consider that no CTAN member can be available
+ all the time.)
+ </p>
+ <p>
+ <a id="nohtmlmails">
+ Please take care
+ that the emails you send to this address
+ are
+ </a>
+ <strong>plain text</strong> only,
+ <strong>without</strong> any
+ <strong>HTML</strong> part,
+ because
+ HTML mails are held in CTAN&apos;s spam filter
+ and it may take some time until
+ a postmaster comes along to set them free.
+ (If you are using gmail,
+ you can select
+ &ldquo;plain text mode&rdquo;
+ clicking on the &ldquo;more options&rdquo;
+ triangle in the bottom right corner of the window
+ where you are composing your message.
+ Also, your &ldquo;gmails&rdquo; will <em>always</em>
+ be sent in plain text mode when you access
+ google&apos;s webmail via the &ldquo;basic HTML view&rdquo;
+ interface.)
+ </p>
+
+ <p>
+ <a id="alwaysusetheuploadform">
+ <strong>Never </strong>try to
+ </a>
+ <strong>upload</strong>
+ (or re-upload)
+ <strong>by email</strong>,
+ <strong>
+ always use the
+ <a href="https://ctan.org/upload">upload form</a></strong>,
+ for the following reasons:
+ (a)
+ The many recipients of these emails
+ are generally not happy to see their
+ mailboxes bloated with software contributions,
+ (b)
+ email attachments end up on the wrong computer
+ and we have to perform an
+ additional file transfer,
+ and
+ (c)
+ uploads via the
+ <a href="https://ctan.org/upload">upload form</a>
+ very conveniently generate a number of automated mails
+ that help us with the documentation of our activities
+ and can be easily converted to acknowledgement mails
+ and announcements.
+ </p>
+
+ <p>
+ <a id="nobigattachments"></a>
+ More generally,
+ <strong>no big attachments</strong>
+ should be sent to this email address,
+ mainly because of argument (a)
+ in the preceding paragraph.
+ </p>
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <h2>
+ <a id="uploadpreparation">
+ More requirements on your upload &hellip;
+ </a>
+ </h2>
+
+ <ol>
+ <li>
+ <a id="filenames">
+ <strong>
+ Conditions on filenames:
+ </strong>
+ </a>
+ <ol style="list-style-type:lower-alpha;">
+ <li class="kleinerabstandoben">
+ Filenames should
+ <span class="highlight">no</span>t
+ contain any
+ <a id="nospaces">
+ <span class="highlight">spaces</span>,
+ </a>
+ <span class="highlight">tabs</span>,
+ <span class="highlight">newlines</span>,
+ or other whitespace characters
+ because filenames with whitespaces in them
+ can make work on a UNIX command line
+ extremely awkward.
+ </li>
+ <li class="kleinerabstandoben">
+ Filenames should
+ <span class="highlight">no</span>t
+ contain any
+ <a id="onlyascii">
+ <span class="highlight">non-ascii</span>
+ </a>
+ characters, for portability reasons.
+ </li>
+ <li class="kleinerabstandoben">
+ Filenames should
+ <span class="highlight">no</span>t
+ contain any characters that have a
+ <a id="nounixspecialcharacters">
+ <span class="highlight">special meaning
+ for UNIX shells</span>
+ (or other systems),
+ </a>
+ such as exclamation and question marks,
+ asterisks, ampersands,
+ slashes, backslashes, pipe symbols,
+ dollar signs,
+ any sort of brackets, and parentheses.
+ </li>
+ <li class="kleinerabstandoben">
+ Filenames should
+ <a id="noinvisiblefiles">
+ <span class="highlight">not start with a dot</span>
+ </a>
+ (&ldquo;invisible files&rdquo; in UNIX-like
+ operating systems).
+ </li>
+ <li class="kleinerabstandoben">
+ <a id="uniquefilenames">
+ <span class="highlight">
+ Unique filenames:
+ </span>
+ </a>
+ This topic has been dealt with in detail
+ in two of the three
+ &ldquo;<a href="#basictexts">basic texts</a>&rdquo;
+ mentioned above, especially with regard to
+ &ldquo;runtime files&rdquo;.
+ &mdash;
+ Let&apos;s add here
+ (a)
+ that uniqueness of filenames over the whole archive
+ would indeed be our ideal
+ (that is of course impossible to achieve &ndash;
+ think of standardised names like &ldquo;README&rdquo;
+ and &ldquo;Makefile&rdquo;!);
+ but nevertheless that ideal should
+ at least be <em>approached</em> as closely as possible.
+ In particular,
+ we strongly recommend uniqueness of filenames
+ <em>within every single package</em>.
+ Ambiguity is never a good thing,
+ and it may prove harmful in unexpected situations.
+ <br />
+ (b) Let us remind you that there are operating
+ systems unable to distinguish between
+ <tt>myfile</tt> and
+ <tt>MyFile</tt>.
+ That&apos;s why we check for &ldquo;identical filenames&rdquo;
+ after converting everything to &ldquo;lowercase&rdquo;.
+ </li>
+ <li class="kleinerabstandoben">
+ You may however be pleased
+ to learn that we have not been asking for
+ MS-DOS-style
+ <a id="eightplusthree"></a>
+ <a href="https://en.wikipedia.org/wiki/8.3_filename">
+ 8.3 filenames</a>
+ for a long time <tt>;-)</tt>
+ </li>
+ </ol>
+ </li>
+
+ <li class="abstandoben">
+ <a id="packageids">
+ <strong>
+ Conditions on package ids:
+ </strong>
+ </a>
+ <br/>
+ Every CTAN package is uniquely identified by its
+ &ldquo;<span class="highlight">package id</span>&rdquo;,
+ which appears, for instance, as the last part in URLs
+ like
+ <a href="https://ctan.org/pkg/geometry">https://ctan.org/pkg/geometry</a>
+ (here &ldquo;geometry&rdquo; is the package&apos;s
+ <em>id</em>.)
+ <ol style="list-style-type:lower-alpha;">
+ <li class="kleinerabstandoben">
+ <a id="packageidslikefilenames"></a>
+ Of course, all the
+ <a href="#filenames">conditions on filenames</a>
+ described above
+ also apply to package ids.
+ </li>
+ <li class="kleinerabstandoben">
+ <a id="packageidrestriction"></a>
+ Moreover, package ids have to be all
+ <span class="highlight">lowercase</span>,
+ and they must
+ <span class="highlight">not start with a digit</span>.
+ <br/>
+ (To ease some of the harshness of this particular rule,
+ <span class="highlight">package <a id="packagenames"><em>names</em></a></span>
+ have been introduced which can be seen
+ at the beginning of the title line of their
+ &ldquo;CTAN home page&rdquo;.
+ For instance, at the top of
+ <a href="https://ctan.org/pkg/arsclassica">https://ctan.org/pkg/arsclassica</a>
+ you see &ldquo;ArsClassica&rdquo;,
+ at the top of
+ <a href="https://ctan.org/pkg/mathtype">https://ctan.org/pkg/mathtype</a>
+ you see &ldquo;MathType&rdquo;,
+ at the top of
+ <a href="https://ctan.org/pkg/one2many">https://ctan.org/pkg/one2many</a>
+ you see &ldquo;12many&rdquo;, etc.
+ Of course, the CTAN team <em>prefer</em>,
+ for the sake of simplicity, to have
+ &ldquo;package name = package id&rdquo;,
+ but small variants like CamelCase are accepted
+ for the &ldquo;names&rdquo;.)
+ </li>
+ <li class="kleinerabstandoben">
+ CTAN and TeX Live have a preference for
+ <a id="hyphenvsunderscore"><span class="highlight">hyphens</span></a>
+ in package ids, rather than underscores.
+ There are at the moment (April 2019)
+ 1195 Catalogue entries with a hyphen in their name vs.
+ 10 with an underscore.
+ You will therefore have to give <em>very</em> good reasons
+ if you want us to accept the 11th package
+ with an underscore in its id <tt>;-)</tt> .
+ </li>
+ <li class="kleinerabstandoben">
+ <a id="l3names">
+ Package ids starting with
+ &ldquo;<tt><span class="highlight">l3</span></tt>&rdquo;
+ </a>
+ are reserved for official LaTeX Project
+ <tt>expl3</tt> packages.
+ Package authors are encouraged to consider using
+ &ldquo;<tt>l<u>t</u>3...</tt>&rdquo; for third-party
+ <tt>expl3</tt> packages.
+ </li>
+ <li class="kleinerabstandoben">
+ New packages and bundles should
+ <a id="noauthornames">
+ <span class="highlight">not</span> be
+ <span class="highlight">named after their authors</span>,
+ </a>
+ but after the purpose they are serving,
+ because they may later be taken over by
+ other maintainers.
+ (We know that there are a few
+ well established CTAN packages
+ that do not fulfill this rule;
+ but that comes under
+ &ldquo;protection of vested rights&rdquo;,
+ and we have now learned from history.)
+ </li>
+ <li class="kleinerabstandoben">
+ In the same way,
+ <a id="nocrypticids">
+ &ldquo;<span class="highlight">cryptic</span>&rdquo;
+ </a>
+ package ids like
+ &ldquo;acs&rdquo;,
+ &ldquo;mxd&rdquo;,
+ &ldquo;tpx&rdquo;, or
+ &ldquo;tcvn&rdquo;
+ are nowadays strongly
+ <span class="highlight">discouraged</span>.
+ Modern package ids should as best as possible
+ convey to the average user an idea of what
+ the package is about.
+ </li>
+ </ol>
+ </li>
+
+ <li class="abstandoben">
+ <a id="versionnumber"></a>
+ <a id="versionidentifier">
+ <strong>
+ Version identifier:
+ </strong>
+ </a>
+ <br />
+ Every submission of every CTAN package has to contain a
+ &ldquo;<span class="highlight">version identifier</span>&rdquo;
+ that permits to distinguish this version
+ of the package from earlier or later ones.
+ (Mind that what counts here are the actual
+ <em>installations</em> on the archive;
+ submissions that were for some reason refused
+ and never installed may be neglected.)
+
+ This identifier should of course coincide
+ with the one you will later enter into
+ the &ldquo;Version&rdquo; field of the
+ <a href="https://ctan.org/upload">upload form</a>.
+ <br />
+ This version identifier may consist of
+ <ol style="list-style-type:lower-roman;">
+ <li>
+ Either (only) a version
+ <span class="highlight">number</span>,
+ i.e. something like
+ &ldquo;1.0&rdquo;, or
+ &ldquo;3.0.17&rdquo;, or
+ &ldquo;2.1a&rdquo;,
+ </li>
+ <li>
+ or (only) a version
+ <span class="highlight">date</span>,
+ preferably in YYYY-MM-DD or YYYY/MM/DD notation, like
+ &ldquo;2018-12-06&rdquo; or
+ &ldquo;2018/12/06&rdquo;,
+ </li>
+ <li>
+ or a string consisting of <em>both</em>
+ the aforementioned data.
+ </li>
+ </ol>
+ For
+ <span class="highlight">simple LaTeX packages</span>,
+ the optional argument of
+ the <tt>\ProvidesPackage</tt>
+ or <tt>\ProvidesClass</tt>
+ command of the <tt>.sty</tt> or <tt>.cls</tt> file
+ should be a good place
+ where to put this information.
+ <br />
+ For <span class="highlight">bundles</span>
+ that consist of various files
+ with possibly different version identifiers
+ of their own,
+ the whole bundle should be marked
+ with a &ldquo;bundle version identifier&rdquo; referring to
+ the bundle <em>as a whole</em>.
+ A good way to achieve this
+ is &ldquo;tagging&rdquo;
+ the bundle with the date of the latest
+ change of <em>any</em> of its files.
+ Put this &ldquo;tag&rdquo;
+ into a place where it is easy to find,
+ such as
+ the latest entry of a <tt>Changes</tt> file,
+ a <tt>VERSION</tt> file,
+ or an easily accessible place
+ (preferably: the top part)
+ in the
+ <a href="#readme"><tt>README</tt></a> file.
+ <br/>
+ Please note that in our mind the
+ <span class="highlight">documentation</span>
+ is considered <em>part of</em> the &ldquo;package&rdquo;.
+ So even if &ldquo;only&rdquo; a tiny detail of
+ the documentation
+ (and nothing whatever in the &ldquo;runtime files&rdquo;!)
+ has changed,
+ the version number, if it is part of the version identifier,
+ has to increase at least slightly.
+ </li>
+
+ <li class="abstandoben">
+ <a id="lowredundancy">
+ <strong>
+ Low redundancy:
+ </strong>
+ </a>
+ <br />
+ Because of the well known disadvantages
+ of redundancy
+ &ndash;
+ especially the risk of inconsistency!
+ &ndash;
+ we try to keep it as low as possible
+ on the unpacked archive.
+ In particular &hellip;
+ <ol style="list-style-type:lower-alpha;">
+ <li class="kleinerabstandoben">
+ &hellip;
+ we do not wish to hold
+ identical copies of one and the same file
+ <a id="noduplicatefiles">
+ (&ldquo;<span class="highlight">duplicate files</span>&rdquo;)
+ </a>
+ in different places,
+ such as for instance
+ <tt>README</tt> and <tt>doc/README</tt>.
+ <br />
+ If you <em>really</em> think you need
+ copies of a file in other places,
+ then please replace these copies
+ with symbolic links (a.k.a. symlinks or softlinks)
+ pointing to the &ldquo;original&rdquo; file.
+ &mdash;
+ Beware:
+ When packing your upload file with <tt>zip</tt>,
+ you will have to call it
+ with the <tt>--symlinks</tt> option
+ (or something equivalent, depending on
+ your particular zip program)
+ if you do not want the symlink to be replaced
+ by a copy of the original file again!
+ <br />
+ (Mind that this request concerns only the
+ <a href="#unpackedtree">unpacked part</a>
+ and that a similar recommendation does <em>not</em>
+ hold for the contents of <tt>.tds.zip</tt> files:
+ <tt>.tds.zip</tt> files are supposed to be unpacked
+ without problems on <em>arbitrary</em> platforms, and this
+ cannot be guaranteed if they contain symbolic
+ links!)
+ </li>
+
+ <li class="kleinerabstandoben">
+ &hellip;
+ we do not wish to hold files
+ that can be easily
+ <a id="nogeneratedfiles">
+ &ldquo;<span class="highlight">generated</span>&rdquo;
+ (&ldquo;<span class="highlight">derived</span>&rdquo;)
+ </a>
+ from other files contained in the submission.
+ <!--
+ <br />
+ -->
+ The standard examples of this are
+ <tt>.cls</tt>, <tt>.sty</tt>, <tt>.clo</tt>,
+ <tt>.fd</tt> or similar LaTeX files,
+ when they can be generated from their
+ <tt>.dtx</tt> source in a straightforward way.
+ <!--
+ <br />
+ Exceptions to this rule , when they cannot
+ be generated in a straightforward way;
+ example: <tt>jsclasses</tt>,
+ which needs a specially customized TeX system.
+ -->
+ <br />
+ <a id="keeppdffiles"></a>
+ The <em>exception</em> to this rule are
+ the <tt>.pdf</tt> files of the documentation:
+ We do indeed wish to keep these,
+ ready for immediate access by visitors,
+ alongside with their sources.
+ <br />
+ <a id="readmeunpacked"></a>
+ The same holds for
+ <a href="#readme">README files</a>
+ in cases where these, too,
+ can be generated from other sources:
+ We always want the
+ <span class="highlight">README unpacked</span>,
+ as a convenient starting point
+ for inspecting the package.
+ </li>
+ </ol>
+ </li>
+
+ <li class="abstandoben">
+ <a id="noauxfiles">
+ <strong>
+ No auxiliary files:
+ </strong>
+ </a>
+ <br />
+ This concerns operating system specific
+ data (like <tt>__MACOSX</tt> directories and
+ <tt>.DS_Store</tt> files),
+ <tt>.git</tt>,
+ <tt>.gitignore</tt>,
+ <tt>.hgignore</tt>,
+ <tt>.hgtags</tt>,
+ editor backup files
+ (<tt>.backup</tt>,
+ <tt>.bak</tt>,
+ <tt>.sav</tt>,
+ <tt>.~</tt>,
+ &hellip;),
+ as well as &ldquo;leftovers&rdquo;
+ from TeX &amp; friends and other programs
+ (<tt>.aux</tt>,
+ <tt>.log</tt>,
+ <tt>.acn</tt>,
+ <tt>.acr</tt>,
+ <tt>.alg</tt>,
+ <tt>.bbl</tt>,
+ <tt>.bcf</tt>,
+ <tt>.blg</tt>,
+ <tt>.brf</tt>,
+ <tt>.cb</tt>,
+ <tt>.cb2</tt>,
+ <tt>.ent</tt>,
+ <tt>.fdb_latexmk</tt>,
+ <tt>.fff</tt>,
+ <tt>.fls</tt>,
+ <tt>.fmt</tt>,
+ <tt>.fot</tt>,
+ <tt>.gaux</tt>,
+ <tt>.glog</tt>,
+ <tt>.gtex</tt>,
+ <tt>.ilg</tt>,
+ <tt>.ind</tt>,
+ <tt>.idx</tt>,
+ <!-- This is indeed a user-supplied config file:
+ <tt>.ist</tt>,
+ -->
+ <tt>.glo</tt>,
+ <tt>.lg</tt>,
+ <tt>.loa</tt>,
+ <tt>.lod</tt>,
+ <tt>.lof</tt>,
+ <tt>.lol</tt>,
+ <tt>.los</tt>,
+ <tt>.lot</tt>,
+ <tt>.lox</tt>,
+ <tt>.nav</tt>,
+ <tt>.out</tt>,
+ <tt>.pre</tt>,
+ <tt>.pyg</tt>,
+ <tt>.snm</tt>,
+ <tt>.soc</tt>,
+ <tt>.toc</tt>,
+ <tt>.vrb</tt>,
+ <tt>.cpt</tt>,
+ <tt>.dvi</tt>,
+ <tt>.glg</tt>,
+ <tt>.gls</tt>,
+ <tt>.glsdefs</tt>,
+ <tt>.idv</tt>,
+ <tt>.maf</tt>,
+ <tt>.mlf</tt>,
+ <tt>.mlt</tt>,
+ <tt>.mtc</tt>,
+ <tt>.nlg</tt>,
+ <tt>.nlo</tt>,
+ <tt>.nls</tt>,
+ <tt>.spl</tt>,
+ <tt>.thm</tt>,
+ <tt>.tmb</tt>,
+ <tt>.tmp</tt>,
+ <tt>.tuc</tt>,
+ <tt>.upa</tt>,
+ <tt>.upb</tt>,
+ <tt>.o</tt>,
+ <tt>.sta</tt>,
+ <tt>.swp</tt>,
+ <tt>.tdo</tt>,
+ <tt>.trc</tt>,
+ <tt>.ttt</tt>,
+ <tt>.url</tt>,
+ <tt>.w18</tt>,
+ <tt>.xdv</tt>,
+ <tt>.xref</tt>,
+ <tt>.4ct</tt>,
+ <tt>.4tc</tt>,
+ <tt>.run.xml</tt>,
+ <tt>.pdfsync</tt>,
+ <tt>.synctex</tt>,
+ <tt>.synctex.gz</tt>,
+ and potentially others we have
+ not yet encountered):
+ Please leave them out of your upload!
+ <br/>
+ <a id="howtoavoidrubbish"></a>
+ Note for <tt>git</tt> users wishing to keep exported
+ <tt>.zip</tt> files &ldquo;git rubbish free&rdquo;:
+ This can be achieved by creating, adding and committing
+ a <tt>.gitattributes</tt> file containing lines like
+ the following:
+ <pre>
+ .gitignore export-ignore
+ .gitattributes export-ignore
+ </pre>
+ Hint for Mac OSX users:
+ A user told us that &ldquo;it is possible to tell
+ Mac OSX&apos;s <tt>tar</tt> command line executable
+ to avoid polluting the archive with OSX specific
+ files, by setting the environment variable
+ <tt>COPYFILE_DISABLE</tt> (to whatever value).&rdquo;
+ <!-- Didier Verna, Tue, 07 Mar 2017 13:48:01 +0100 -->
+ </li>
+
+ <li class="abstandoben">
+ <a id="noemptyfiles">
+ <strong>
+ No empty files or directories:
+ </strong>
+ </a>
+ <br />
+ We tend to consider empty files and
+ directories as &ldquo;rubbish&rdquo;.
+ If you feel otherwise and wish to conserve
+ such files for systematic reasons,
+ we recommend filling them with some
+ comment (in the case of &ldquo;regular files&rdquo;)
+ or a placeholder file (in the case of directories)
+ explaining their purpose.
+ <br />
+ If this is not possible
+ because the program using these files would get
+ disturbed by comments or &ldquo;dummy files&rdquo;,
+ please mention this in the
+ &ldquo;Administrative notes&rdquo; field
+ of the
+ <a href="https://ctan.org/upload">upload form</a>
+ so that we can make a note of this exception
+ and do not bother you with unnecessary complaints.
+ </li>
+
+ <li class="abstandoben">
+ <a id="filepermissions">
+ <strong>
+ File permissions:
+ </strong>
+ </a>
+ <ol style="list-style-type:lower-alpha;">
+ <li class="kleinerabstandoben">
+ Only files that are truly
+ <span class="highlight">executable</span>
+ (like Shell, Perl, Python, Ruby, and other scripts)
+ should be marked as such.
+ An &ldquo;executable&rdquo;
+ README or <tt>.tex</tt> file does not make any sense.
+ </li>
+ <li class="kleinerabstandoben">
+ Files submitted to CTAN are obviously meant
+ for <em>publication</em>.
+ This implies that they should be
+ &ldquo;<span class="highlight">world readable</span>&rdquo;.
+ (In fact, exaggerated &ldquo;privacy&rdquo;
+ of file permissions can lead to serious
+ complications in the installation process.)
+ </li>
+ </ol>
+ </li>
+
+ <li class="abstandoben">
+ <a id="crlf">
+ <strong>
+ Line terminators of text files:
+ </strong>
+ </a>
+ <br />
+ This paragraph is about
+ <a id="textfiles">
+ &ldquo;<span class="highlight">text files</span>&rdquo;
+ </a>
+ (like
+ <tt>.txt</tt>,
+ <tt>.tex</tt>,
+ <tt>.sty</tt>,
+ <tt>.cls</tt>,
+ <tt>.dtx</tt>,
+ <tt>.fd</tt>,
+ <tt>.bib</tt>,
+ <tt>.c</tt>,
+ or any other file that can be edited
+ with a text editor)
+ as opposed to
+ &ldquo;<span class="highlight">binary files</span>&rdquo;
+ (such as
+ <tt>.gif</tt>,
+ <tt>.jpg</tt>,
+ <tt>.wav</tt>,
+ <tt>.mp3</tt>,
+ <tt>.ogg</tt>,
+ <tt>.tfm</tt>,
+ <tt>.pdf</tt>,
+ <tt>.doc</tt>,
+ <tt>.xls</tt>,
+ <tt>.exe</tt>,
+ and a multitude of others).
+ <br />
+ The problem with such text files is
+ that different operating systems have different ways
+ of marking the
+ <span class="highlight">line endings</span>
+ within them:
+ Whereas Microsoft systems describe a line ending
+ in the good old typewriter fashion
+ by a &ldquo;carriage return&rdquo; character
+ followed by a &ldquo;line feed&rdquo; character,
+ UNIX type operating systems have always omitted
+ the &ldquo;carriage return&rdquo;,
+ and modern Mac OS X systems do it the same way.
+ <br />
+ As CTAN&apos;s servers are running on
+ UNIX-like operating systems,
+ the CTAN team have decided
+ that all text files on the archive
+ should have suitable &ldquo;linefeed only&rdquo;
+ line terminators.
+ <br />
+ Now, if you are a Windows user,
+ you need not be alarmed,
+ as there is an easy way to comply with this wish,
+ with hardly any inconvenience for yourself:
+ If you pack your upload file with a
+ <a id="goodzipprogram">
+ <span class="highlight">&ldquo;good zip program&rdquo;</span>,
+ </a>
+ this will mark all text files with a special
+ &ldquo;flag&rdquo; (or &ldquo;tag&rdquo;)
+ that will permit CTAN&apos;s <tt>unzip</tt> program
+ to recognize these text files and perform the
+ necessary conversions
+ (in this case: omitting the unwanted
+ &ldquo;carriage return&rdquo; characters)
+ <em>automatically</em> <tt>:-)</tt>
+ <br />
+ <a id="badzipprograms"></a>
+ Unfortunately, not all zip programs are
+ &ldquo;good zip programs&rdquo; <tt>:-(</tt>
+ <br />
+ In particular,
+ <span class="highlight">7zip</span>,
+ the GNOME archive manager,
+ the <tt>Compress</tt> facility
+ accessible via the <tt>File</tt> menu
+ in Mac OS X&apos;s <tt>Finder</tt>,
+ and the feature that permits
+ to export zip files directly from
+ <span class="highlight">git</span>
+ repositories
+ do not seem to have the desired property.
+ (Please correct us if there has been recently
+ some positive development we are not aware of
+ by writing us an <a href="#ctanemail">email</a>!)
+ <br />
+ <a id="gitandcrlf"></a>
+ However,
+ <span class="highlight">git</span>
+ users may want to have a look at the
+ <tt>.gitattributes</tt> file
+ for the configuration of file types
+ and line endings!
+ <br />
+ <span class="highlight">
+ Known
+ <a id="goodzipprogramnames">
+ &ldquo;good zip programs&rdquo;
+ </a>
+ </span>
+ are
+ the Windows7ff. builtins,
+ WinZip,
+ Windows &ldquo;Total Commander&rdquo;,
+ and the zippers from
+ <a href="http://www.info-zip.org/">
+ info-zip.org</a>.
+ <br />
+ Mac users in need of a &ldquo;good zip program&rdquo;
+ may either turn to
+ <a href="http://www.yellowmug.com/yemuzip/">
+ YemuZip</a>
+ or the standard <tt>zip</tt> command on their
+ command line
+ (which is in fact the info-zip tool that is
+ also present in Linux systems).
+ The command line <tt>zipinfo</tt> utility
+ is extremely useful for checking
+ zip archives once they have been created.
+ <br />
+ <a id="tarnotxtvsbintags"></a>
+ Unfortunately, <b><tt>tar</tt></b> does <em>not</em>
+ offer the &ldquo;tagging&rdquo; feature in question.
+ <br />
+ Finally, there are two
+ <span class="highlight">exceptions</span>
+ to what has been said before:
+ <ol style="list-style-type:lower-alpha;">
+ <li class="kleinerabstandoben">
+ <em>If</em> your upload contains any
+ <tt>.bat</tt> or
+ <tt>.cmd</tt> or
+ <tt>.nsh</tt> or
+ other typical DOS/Windows files,
+ and <em>if</em> you wish to preserve
+ their CR+LF line endings,
+ please drop us a line to that effect
+ in the &ldquo;Administrative notes
+ (to the CTAN maintainers)&rdquo; field
+ of our
+ <a href="https://ctan.org/upload">upload page</a>,
+ and we will take care that this is done.
+ </li>
+ <li class="kleinerabstandoben">
+ <a id="nocrlfintdszip"></a>
+ All the <tt>.tds.zip</tt> files
+ we offer on the archive
+ are supposed to have nothing but
+ UNIX style line terminators inside
+ as well as the necessary .zip flags
+ for unpacking them in the best possible
+ way on any operating system.
+ That&apos;s why we wish <tt>.tds.zip</tt> files
+ to be submitted in exactly that way.
+ (<em>If</em> there should really be a problem
+ that prevents you from complying with this
+ requirement, we <em>may</em> find a way
+ to correct this shortcoming at our end,
+ but we would of course much prefer not
+ to have to resort to any such manipulations.)
+ </li>
+ </ol>
+ </li>
+
+ <li class="abstandoben">
+ <a id="canonicalurls2">
+ <strong>
+ &ldquo;Canonical&rdquo; URLs in documentation:
+ </strong>
+ </a>
+ <br />
+ Please make sure when writing (or revising)
+ your documentation
+ that TeX software on CTAN archives
+ is referred to using our
+ <a href="#urls">preferred &ldquo;canonical&rdquo; URLs</a>
+ described
+ <a href="#urls">above</a>
+ rather that URLs pointing to individual CTAN servers.
+ </li>
+
+ <li class="abstandoben">
+ <a id="readme">
+ <strong>
+ Rules about <tt>README</tt> files:
+ </strong>
+ </a>
+ <ol style="list-style-type:lower-alpha;">
+ <li>
+ Every package shall be accompanied
+ by a README file giving a short
+ introduction to the package&apos;s purpose
+ as well as significant data like
+ author&apos;s name and contact,
+ license etc.
+ </li>
+ <li>
+ Its name can be either
+ <tt>README</tt> or
+ <tt>README.txt</tt> or
+ <tt>README.md</tt>,
+ but no other variants are permitted
+ at the moment.
+ </li>
+ <li>
+ Its contents must be easily readable using
+ the UNIX <tt>more</tt> or <tt>less</tt> commands
+ or an arbitrary editor.
+ </li>
+ <li>
+ It should be written in
+ <span class="highlight">English</span>
+ or at least comprise a short
+ abstract in English.
+ </li>
+ <li>
+ The encoding should be
+ <span class="highlight">ascii</span>
+ or
+ <span class="highlight">utf-8</span>
+ without BOM (byte order mark).
+ </li>
+ <li>
+ It has to be placed at the top level
+ of the
+ <a href="#unpackedtree">unpacked package</a>
+ (but in the <tt>doc/&hellip;/</tt> directory of
+ a possible <tt>.tds.zip</tt> file).
+ </li>
+ </ol>
+ </li>
+
+ <!--
+ I think we will omit the following part altogether,
+ at least for the time being ...
+ <li class="abstandoben">
+ <a id="tdsequalunpacked">
+ <strong>
+ Identical files in <tt>.tds.zip</tt> and outside:
+ </strong>
+ </a>
+ <br />
+ Some general remarks &hellip;
+ <br />
+ -->
+ <!--
+ In particular, Vincent Bela&iuml;che, in an
+ email dated Mon, 15 Sep 2014 22:35:43 +0200,
+ Subject: Re: Lettre,
+ asks me to add the following sentence to
+ these additional instructions:
+ -->
+ <!--
+ If you do not use DTX, and you are documenting your
+ sty/cls files with docTeX comments, then unpacked zip
+ and .tds.zip may contain either the files with docTeX
+ comments included, or with them stripped out ; you
+ must however be consistent and have the same files in
+ both the unpacked zip and in the .tds.zip.
+ -->
+ <!--
+ But I do not really understand this at the moment.
+ His problems seem to be due to a very idiosyncratic
+ way of packaging his files ...
+ -->
+ <!--
+ <br />
+ Needs a good zip program, see above!
+ </li>
+ -->
+
+ <!--- template
+ <li class="abstandoben">
+ <a id="aaaa">
+ <strong>
+ AAAA
+ </strong>
+ </a>
+ <br />
+ </li>
+ -->
+ </ol>
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <h2>
+ <a id="uploading">Uploading to CTAN</a>
+ </h2>
+
+ <p>
+ When you feel convinced that you have done
+ all you can to comply with the requirements
+ described up to now,
+ you may go on to package your submission
+ using either <tt>zip</tt> or <tt>tar</tt>,
+ as described on our
+ <a href="https://ctan.org/help/upload-pkg">help page</a>.
+
+ &ndash;
+
+ <a id="topdirofzipfile"></a>
+ Do not forget the
+ <span class="highlight">top level directory</span>
+ of the upload file
+ (&ldquo;<tt>my-package/</tt>&rdquo; in the examples).
+ It simplifies our installation process
+ and makes it more secure.
+
+ &ndash;
+
+ <a id="zippreferred"></a>
+ Please opt for a
+ <a href="#goodzipprogram">good zip program</a>
+ (instead of <tt>tar</tt> or <em>any</em>
+ zip program)
+ if you are not one hundred percent sure
+ that none of your
+ <a href="#textfiles">text files</a>
+ contains any
+ &ldquo;Microsoft style&rdquo; line terminators!
+ </p>
+
+ <p>
+ <a id="hintforupdates"></a>
+ If you want to submit an
+ <span class="highlight">update</span> to
+ a package that is already on CTAN,
+ we recommend you to go first to its
+ &ldquo;CTAN homepage&rdquo;
+ (<tt>https://ctan.org/pkg/&lt;package_id&gt;</tt>)
+ and <em>then</em> click on the &ldquo;Upload&rdquo;
+ button.
+ You will find that
+ some of the more tedious fields
+ have already been filled in
+ with information from our Catalogue
+ <tt>:-)</tt>
+ &nbsp;
+ But please do not forget to
+ <span class="highlight">
+ update the version field!
+ </span>
+ </p>
+
+ <p>
+ <a id="authorsemail"></a>
+ Please pay also particular attention
+ to what you enter into the
+ <span class="highlight">
+ &ldquo;Your email&rdquo;
+ </span>
+ field:
+ In fact,
+ we ask maintainers to use
+ <span class="highlight">
+ always the same email address
+ </span>
+ when contacting the CTAN team.
+ In particular, given
+ the (improbable, but not completely unreal)
+ danger of
+ unauthorized uploaders
+ overwriting &ldquo;good&rdquo; packages,
+ we will refuse to install an update
+ if it is not submitted using
+ an email address known to the CTAN team.
+ &mdash;
+ BTW:
+ Whenever you plan to <em>change</em>
+ your &ldquo;CTAN upload email address&rdquo;,
+ do not forget to drop a line to
+ <a href="#ctanemail">ctan (at) ctan (dot) org</a>,
+ still using the <em>old</em> address,
+ and asking us to register the new one.
+ </p>
+
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <h2>
+ <a id="furtherprocessing">What will happen next &hellip;</a>
+ </h2>
+
+ <ul style="list-style-type:circle;">
+ <li class="kleinerabstandoben">
+ Every upload will be
+ <span class="highlight">unpacked</span> and
+ <span class="highlight">checked</span>
+ by an upload manager.
+ </li>
+ <li class="kleinerabstandoben">
+ <span class="highlight">Small deficiencies</span>
+ will be
+ <span class="highlight">corrected</span>
+ immediately by that person.
+ You will receive
+ <span class="highlight">feedback</span>
+ about this and be asked to apply
+ the same sort of change(s) to your own file(s)
+ before your next upload.
+ </li>
+ <li class="kleinerabstandoben">
+ If there is a
+ <span class="highlight">non-trivial problem</span>
+ we cannot or do not
+ want to resolve on our own, we will ask back and the
+ installation process will be momentarily stalled until
+ we receive an answer to our question.
+ In some cases even a re-upload may become necessary.
+ </li>
+ <li class="kleinerabstandoben">
+ After installation of the package on the archive
+ (i.e.: on our
+ <a href="#centralserver">central server</a>)
+ the corresponding <tt>.xml</tt> source file of the
+ <span class="highlight">Catalogue entry</span>
+ will either have to be created
+ &ldquo;from scratch&rdquo; (for new packages)
+ or be updated (in all other cases;
+ mostly only the version field,
+ sometimes the copyright line(s) or details
+ about the pointers to the documentation).
+ Please use the &ldquo;Administrative notes
+ (to the CTAN maintainers)&rdquo; field
+ in the
+ <a href="https://ctan.org/upload">upload form</a>
+ if you wish us to perform any other changes.
+ </li>
+ <li class="kleinerabstandoben">
+ When all of this has been done,
+ we will send an
+ <span class="highlight">email</span>
+ to the
+ <a href="#authorsemail">address</a>
+ you entered into the
+ &ldquo;Your email&rdquo; field of the
+ <a href="https://ctan.org/upload">upload form</a>.
+ </li>
+ <li class="kleinerabstandoben">
+ It may take a few hours until the
+ <span class="highlight">Catalogue page</span>
+ of the website
+ has been regenerated from the source file,
+ and up to 24 hours
+ until the new files have arrived
+ on all the
+ <span class="highlight">mirrors</span>
+ worldwide.
+ </li>
+ <li class="kleinerabstandoben">
+ If your upload is a new one or
+ if you have requested an announcement,
+ the message to
+ <span class="highlight">CTAN-Announce</span>
+ will be posted
+ if possible shortly after
+ the end of that 24 hour delay.
+ There may however be a further delay due to
+ the maintainer&apos;s working hours
+ or other engagements at that time.
+ If the message has not appeared
+ after more than 48 hours,
+ you should write a message to
+ <tt>ctan (at) ctan (dot) org</tt>
+ to enquire if anything has gone wrong.
+ </li>
+ <li class="kleinerabstandoben">
+ It is always helpful if you
+ <span class="highlight">check</span> what you see
+ at the URLs indicated in the acknowledgement mail
+ around 24 hours after installation and
+ <span class="highlight">inform us</span>
+ about any possible flaws in the presentation.
+ </li>
+ </ul>
+
+ <p>
+ <a id="patience"></a>
+ Please
+ <span class="highlight">
+ do not re-upload when you do not hear from us
+ <em>at once</em>!
+ </span>
+ There may have been a sudden inrush of uploads
+ and/or maintainers may have been kept from
+ attending to your upload by
+ &ldquo;real&rdquo; work,
+ family matters,
+ technical problems,
+ holidays,
+ illness,
+ or other causes.
+ If you still haven&apos;t heard from us after let&apos;s say
+ three or four days,
+ <em>and</em> have checked your spam folder to no avail,
+ you may enquire by email to
+ <tt>ctan (at) ctan (dot) org</tt>
+ (remember: No HTML mail please, because of the spam trap!).
+ </p>
+
+ <p>
+ <span class="highlight">Thanks</span>
+ for your perseverance
+ and <span class="highlight">good luck</span>
+ with your submission!
+ </p>
+
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <h2>
+ <a id="authoridanduseraccount" style="font-size:smaller">
+ Some additional information about author ids and user accounts</a>
+ </h2>
+
+ <p>
+ Every author/maintainer of a CTAN package is registered
+ in the database that is used for the administration
+ of <em>the archive itself</em>
+ with an <span class="highlight">author id</span>
+ that is assigned in the following way:
+ </p>
+ <p>
+ As a general rule,
+ the author id equals the author&apos;s family name,
+ downcased and with non-ascii characters
+ converted to ascii.
+ For instance, new author Benjamin Bl&uuml;mchen
+ would receive the author id &ldquo;bluemchen&rdquo;.
+ </p>
+ <p>
+ If however another author of the same family name
+ is already registered, the newer author&apos;s id will be modfied
+ using the first letter(s) of his or her given name.
+ For instance, if at a later time <em>Hildegard</em> Bl&uuml;mchen
+ were to join us as an author, she would be registered
+ as &ldquo;bluemchen-h&rdquo;.
+ </p>
+ <p>
+ These <em>author</em> ids must not be confused with the names
+ of the <span class="highlight"><em>user</em> accounts</span>
+ on the CTAN <span class="highlight"><em>website</em></span>:
+ The names of these user accounts can be chosen relatively
+ freely, as long as uniqueness is assured.
+ </p>
+ <p>
+ A relation between a person&apos;s author id and their
+ CTAN website user account can be established via the
+ <a href="#authorsemail">email address</a>.
+ In our webmaster&apos;s own words:
+ </p>
+ <blockquote>
+ Once you are logged into the CTAN site and visit the page
+ <a href="https://ctan.org/user/settings">https://ctan.org/user/settings</a>
+ (link in the upper right corner), you will find the section
+ &ldquo;CTAN Contributor Confirmation&rdquo; where you can
+ confirm the relation between the author id and the
+ current account by setting the check-mark.
+ In the same way you can remove the relation by unchecking.
+ <br/>
+ This feature is offered when one of the known email addresses
+ in the author database matches the email address of the account
+ (which can be edited on the same page).
+ </blockquote>
+
+
+ <!-- ======================================================== -->
+ <hr/>
+
+ <!-- To be activated when file is put into SVN:
+ <p>
+ $LastChangedDate$
+ </p>
+ Until then: -->
+ Last updated: 2019-04-22
+ </body>
+</html>
diff --git a/help/ctan/ctan-web.data.gz b/help/ctan/ctan-web.data.gz
new file mode 100644
index 0000000000..016d00ee8b
--- /dev/null
+++ b/help/ctan/ctan-web.data.gz
Binary files differ
diff --git a/help/de-tex-faq/part1 b/help/de-tex-faq/part1
new file mode 100644
index 0000000000..24f70828f7
--- /dev/null
+++ b/help/de-tex-faq/part1
@@ -0,0 +1,775 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.rediris.es!newsmi-us.news.garr.it!NewsITBone-GARR!news.mailgate.org!newsfeed.stueberl.de!news-mue1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 1 of 11)
+Supersedes: <de-tex-faq-1-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:14 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 747
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975394 885 134.100.9.52 (19 Sep 2003 12:43:14 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:14 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117399 de.answers:9376 news.answers:258265
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part1
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 1 ---
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+ Dieser Text enthlt hufig gestellte Fragen und passende Antworten zum
+ Textsatzsystem TeX und zu DANTE e.V.
+ Er kann ber beliebige Medien frei verteilt werden, solange er
+unverndert bleibt (inklusive dieses Hinweises). Die Autoren bitten bei
+ Verteilung ber gedruckte Medien, ber Datentrger wie CD-ROM u.. um
+ Zusendung von mindestens drei Belegexemplaren.
+ Anregungen, Ergnzungen, Kommentare und Bemerkungen zur FAQ senden Sie
+ bitte per E-Mail an `detexfaq@dante.de'
+------------------------------------------------------------------------
+
+
+Inhalt
+
+
+ 1 Allgemeines
+
+ 1.1 ber diese FAQ
+ 1.2 CTAN, das `Comprehensive TeX Archive Network'
+ 1.3 Newsgroups und Diskussionslisten
+
+ 2 Anwendervereinigungen, Tagungen, Literatur
+
+ 2.1 DANTE e.V.
+ 2.2 Anwendervereinigungen
+ 2.3 Tagungen (*)
+ 2.4 Literatur (*)
+
+ 3 Textsatzsystem TeX - bersicht
+
+ 3.1 Grundlegendes
+ 3.2 Welche TeX-Formate gibt es? Was ist LaTeX?
+ 3.3 Welche TeX-Weiterentwicklungen gibt es?
+
+ 4 Textsatzsystem TeX - Bezugsquellen
+
+ 4.1 Wie bekomme ich ein TeX-System?
+ 4.2 TeX-Implementierungen (*)
+ 4.3 Editoren, Frontend-/GUI-Programme (*)
+
+ 5 TeX, LaTeX, Makros etc. (I)
+
+ 5.1 LaTeX - Grundlegendes
+ 5.2 LaTeX - Probleme beim Umstieg von LaTeX 2.09
+ 5.3 (Silben-)Trennung, Absatz-, Seitenumbruch
+ 5.4 Seitenlayout, Layout allgemein, Kopf- und Fuzeilen (*)
+
+ 6 TeX, LaTeX, Makros etc. (II)
+
+ 6.1 Abbildungen und Tafeln
+ 6.2 Tabellen
+ 6.3 Funoten, Endnoten etc. (*)
+ 6.4 Grafiken, Bilder, Farbe und andere Effekte (*)
+
+ 7 TeX, LaTeX, Makros etc. (III)
+
+ 7.1 Gliederung, Inhalts-, Abbildungs- und andere Verzeichnisse
+ 7.2 Literaturzitate, Literaturverzeichnis, BibTeX (*)
+ 7.3 \verb-Anweisung, verbatim- und Kommentar-Umgebungen (+)
+ 7.4 Zerbrechliche Anweisungen in `moving arguments'
+
+ 8 TeX, LaTeX, Makros etc. (IV)
+
+ 8.1 Verschiedene Zeichen
+ 8.2 Mathematischer Formelsatz (*)
+ 8.3 Chemischer Struktur- und Formelsatz
+ 8.4 Notensatz (*)
+ 8.5 Verschiedenes (+)
+
+ 9 METAFONT und Schriften
+
+ 9.1 METAFONT und METAFONT-Hilfsprogramme
+ 9.2 Schriften - allgemein (*)
+ 9.3 TrueType-Schriften
+
+ 10 METAFONT und Schriften (Fortsetzung)
+
+ 10.1 Die Computer-Modern-Schriften und ihre Nachfolger (+)
+ 10.2 Alternativen zu den Computer-Modern-Schriften (*)
+ 10.3 Sonderschriften
+
+ 11 Tools und Utilities
+
+ 11.1 Tools zur Manipulation von dvi-Dateien
+ 11.2 Syntax-Checker
+ 11.3 Dokument-Konverter von bzw. in das (La)TeX-Markup-Format (*)
+ 11.4 TeX-Benutzungsoberflchen und Editoren (*)
+ 11.5 dvi-Treiber - Druckertreiber und Previewer
+ 11.6 Zeichenprogramme
+
+
+------------------------------------------------------------------------
+Neu hinzugekommene Abschnitte oder Abschnitte mit neuen Fragen und
+Antworten sind durch ein Plus-Zeichen (+), Abschnitte mit genderten
+Fragen und Antworten sind durch ein Sternchen (*) markiert. Geringfgige
+Textnderungen durch Korrektur von Ausdrucks- oder Rechtschreibfehlern
+sind nicht markiert.
+
+
+1 Allgemeines
+
+
+1.1 ber diese FAQ
+
+
+1.1.1 Entstehung und Erstellung
+
+Diese deutschsprachige FAQ (``frequently asked questions'' = Liste mit
+hufig gestellten Fragen und Antworten) wurde durch die in der Newsgroup
+`de.comp.text.tex' regelmig auftauchenden Fragen ``Was ist DANTE
+e.V.?'', ``Was ist ``Die TeXnische Komdie''?'', ``Wie kann ich Mitglied
+werden?'', ``Was kostet eine Mitgliedschaft?'' geboren. Aus diesem Grund
+besteht ein Teil der FAQ aus Fragen ber DANTE e.V. und den
+entsprechenden Antworten. Aus der ca. 14KB groen, zweiteiligen ersten
+Version vom 6. November 1995 ist innerhalb von zwei Monaten zuerst eine
+vier-, dann eine achtteilige, ca. 90KB groe FAQ-Liste entstanden, die
+ab Oktober 1996 auf elf Teile angewachsen ist und mittlerweile eine
+Gre von ca. 280KB Text erreicht.
+Bis 1998 wurde die FAQ nur als reine Textversion gepflegt und
+verffentlicht. Im Oktober 1997 hat Rolf Niepraschk den Text der FAQ zur
+weiteren Verarbeitung mit Hyperlatex umgesetzt, so da daraus sowohl
+eine Textversion der FAQ als auch Versionen in HTML- und anderen
+Formaten generiert werden kann. Die Hyperlatex-Eingabe wurde in den
+Folgemonaten von Fehlern befreit und erste Testversionen ab Februar 1998
+verffentlicht. In dieser Zeit erfolgte die Pflege der offiziellen
+Textversion und der Test-Hyperlatex-Quelle parallel. Im April 1999 stand
+schlielich die 50. Ausgabe dieser FAQ der ffentlichkeit in
+verschiedenen Formaten zur Verfgung, die aus einer einzigen
+Hyperlatex-Quelle erzeugt wurden.
+Die DVI-, PostScript- und PDF-Versionen werden mit einem blichen
+teTeX-System erzeugt. Fr die PDF-Version kommt pdfTeX zusammen mit dem
+Paket `hyperref' zum Einsatz. Als Dokumentklasse finden die
+Koma-Script-Klassen Verwendung.
+Aus derselben Eingabequelle erstellt Hyperlatex die HTML-Version. Die
+leider sehr beschrnkten Mglichkeiten von Hyperlatex zur Generierung
+eines Stichwortverzeichnisses wurden von einem der Autoren der FAQ
+erweitert, da der Index fr eine FAQ hilfreiche Dienste leisten kann.
+Die Textversion wurde bis Version 57 (November 1999) mit Lynx aus einer
+speziell angepaten HTML-Version erstellt. Im Dezember 1999 wechselten
+wir mit Version 58 von Lynx auf html2text, das auch HTML-Tabellen
+verarbeiten kann.
+Um diese Vielzahl von Zielformaten zu ermglichen, besteht die
+Eingabequelle der FAQ aus einer Menge von Treiberdateien, die fr jedes
+Format die notwendigen Deklarationen und Makro-Definitionen enthalten
+und den eigentlichen Dateien mit den Fragen und Antworttexten. Das
+Stichwortverzeichnis wird durch entsprechend definierte
+Markup-Anweisungen fr Pakete, Klassen, Schriften etc. automatisch und
+durch viele weitere von uns manuell vorgenommene Eintragungen generiert.
+
+1.1.2 Erscheinungsweise
+
+Die Textversion der FAQ wird regelmig zur Monatsmitte in die
+Newsgroups `de.comp.text.tex', `de.answers' und `news.answers'
+verschickt. Die FAQ besteht aus mehreren Teilen, wobei jeder Teil ohne
+News-Header nicht lnger als ca. 32KB ist.
+
+1.1.3 Copyright
+
+Copyright 1995-2003 B. Raichle, R. Niepraschk, Th. Hafner
+Dieser Text kann ber beliebige Medien frei verteilt werden, solange er
+vollstndig und unverndert bleibt (zusammen mit diesem Hinweis). Die
+Autoren bitten allerdings bei Verteilung ber gedruckte Medien, ber
+Datentrger wie CD-ROM u.a. um Zusendung von mindestens drei
+Belegexemplaren.
+In diesem Werk werden eingetragene Warenzeichen, Handelsnamen und
+Gebrauchsnamen verwendet. Auch wenn diese nicht als solche
+gekennzeichnet sind, gelten die entsprechenden Schutzbestimmungen.
+
+1.1.4 Archivierung
+
+Eine Kopie kann man ber das World-Wide-Web (WWW) in
+ http://www.dante.de/faq/de-tex-faq/
+finden.
+Da die FAQ in die Newsgroups `de.answers' und `news.answers' verschickt
+wird, kann man die neueste Version in dem weltweiten FAQ-Archiv
+ftp://rtfm.mit.edu/pub/usenet/news.answers/de-tex-faq/ und allen
+Spiegeln dieses Archivs, u.a. den ftp-Servern des CTAN (siehe Abschnitt
+1.2) in CTAN: help/de-tex-faq/, finden. Die Dateien auf diesen
+ftp-Servern kann man sich auch mit Hilfe eines ftp-Mailer ber E-Mail
+zuschicken lassen (siehe Frage 1.2.4).
+
+1.1.5 Verwendete Abkrzungen
+
+Wird im Zusammenhang mit ftp-Adressen
+ CTAN: XXX
+geschrieben, so ist dies als
+ ftp://ftp.dante.de/tex-archive/XXX
+zu lesen. Statt ftp.dante.de kann auch jeder andere CTAN-Server
+verwendet werden, wobei im Interesse einer geringeren Belastung des
+Internet in Deutschland bevorzugt der deutsche CTAN-Server oder einer
+seiner deutschen Spiegel genutzt werden sollte (siehe Frage 1.2).
+
+1.1.6 Verwendete Kodierung:
+
+Die Autoren schreiben den Text in ISO Latin-1 (ISO 8859-1) und
+verschicken ihn mit entsprechendem MIME-Mail-Header, so da er von
+korrekt konfigurierten Programmen problemlos und automatisch in andere
+Kodierungen konvertiert werden kann.
+Erhalten Sie diesen Text mit unlesbaren Umlauten und trgt ein
+fehlerhaft konfiguriertes Gateway die Schuld daran, knnten Sie dies zum
+Anla nehmen, die Verwalter der Gateways zu berreden, deren
+Konfiguration zu korrigieren. Und bitte vorher berprfen, ob nicht die
+eigene Software, beispielsweise der eigene Newsreader an den unlesbaren
+Umlauten Schuld trgt! Einen Artikel mit fehlerhaft kodierten Umlauten
+kann man mit Hilfsprogrammen, wie `recode' (in jedem guten GNU-Archiv zu
+finden) oder `charconv' in vielen Fllen korrigieren. Dazu folgt hier
+eine Referenzliste der Umlaute und des scharfen s:
+
+ Ae Oe Ue ae oe ue ss ('e 'i 'o)
+ ( )
+
+
+1.1.7 Mitwirkende an dieser FAQ
+
+Aktiv mitgewirkt haben bisher:
+ Bernd Raichle, Thomas Hafner, Luzia Dietsche, Ulrik Vieth, Matthias G.
+ Berberich, Olaf Kummer, Michael Wolf, Martin Schrder, Markus Kohm,
+ Marion Neubauer, em, Petra Humann, Ulrich Kuckert, Martin Mattel,
+Wilfried Hennings, Karl Eichwalder, Anselm Lingnau, Jrg Knappen, Werner
+ Icking, Heinz Kusznier, Alexander Bugl, Jrgen Dollinger, Tilmann B,
+ Sebastian Kirsch, Ralph Schleicher, Marcus Otto, Ralf Grtner, Rolf
+ Herzog, Reinhard Zierke, Klaus Hppner, Rainer Dorsch, Marcus Ohlhaut,
+ Gnter Partosch, Andreas Schlechte, Heiko Nock, Tilman Raible, Hartmut
+Goebel, Werner Liebscher, Lutz Pogrell, Hartmut Schirmer, Andreas Frick,
+ Tobias Burnus, Walter Schmidt, Christine Waigl, Helmut Geyer, Karl F.
+ Banke, Heinrich Goetzger, Peter Wyzlic, Rolf Niepraschk, Bjrn Lorenz,
+ Ronald G. Wichern, Thomas Behrens, Thomas Neumann, Stefan Ulrich,
+ Christoph Wutzke, Jrg Schulz, Klaus Dahlenberg, Axel Reichert, Karl
+ Heinz Marbaise, Karsten Tinnefeld, Schorsch Slickers, Martin Sander,
+Thomas Pothmann, Hans Steffani, Werner Lemberg, Colin Marquardt, Michael
+ Streichsbier, Daniel Bchner, Thorsten Hansen, Michael Fischer von
+ Mollard, Norbert Roth, Thomas Henlich, Jens Berger, Jan Theofel, Arash
+ Esbati, Stephan Lehmke, Jrgen Gbel, Heiko Oberdiek, Thomas Lotze,
+ Martin Vaeth, Philipp Lehman, Peter Schuller, Frank Kster.
+Herzlichen Dank fr die bisher eingesandten Fragen und Korrekturen! Wir
+hoffen, da wir niemanden vergessen haben. Dank auch an diejenigen, die
+uns etwas geschickt haben, die ihre Einsendung jedoch noch nicht in
+dieser FAQ wiederfinden. Wir bitten um Verstndnis, da wir leider nie
+die notwendige Zeit haben, sofort alle Einsendungen zu bearbeiten.
+
+1.1.8 Ihre Mitarbeit ist erwnscht!
+
+Eine FAQ ist nie fertiggestellt; es gibt immer etwas zu tun:
+
+* Korrekturlesen
+ Finden Sie falsche, fehlerhafte oder fehlende Querbezge oder Verweise
+ auf ftp-Server, Literatur u.., korrigieren Sie fehlerhafte oder
+ unvollstndige Antworten, verbessern Sie Rechtschreib- und
+ Ausdrucksfehler.
+* Neuerungen/Updates
+ berprfen und ergnzen Sie die Listen, wie beispielsweise die
+ bersicht der verfgbaren TeX-CD-ROM-Angebote, der
+ TeX-Implementierungen etc. Stimmen die Angaben, gibt es neuere
+ Versionen oder neue Angebote, sind Angebote veraltet bzw. vom Markt
+ genommen worden?
+* Erweiterungen
+ Haben Sie eine neue Frage und die dazugehrige Antwort? Haben Sie
+ einen Vorschlag, wie man eine Antwort krzer bzw. knapper formulieren
+ kann? Hinweise auf andere FAQ, Artikel, bersichten etc.
+
+Bitte senden Sie uns _keine_ Fragen ohne Antworten! Wir bekommen relativ
+hufig Fragen zu verschiedenen Dingen zugeschickt, da einige Leser
+hoffen, da wir diese beantworten knnen. Meist lautet unsere Antwort:
+``Wende Dich an `de.comp.text.tex' oder eine der vielen anderen
+Newsgroups oder Diskussionslisten!''. Es ist auch keine Lsung, uns dann
+zu bitten, diese Frage weiterzuleiten - das kann jeder ebensogut selbst
+tun.
+Anregungen, Ergnzungen, Korrekturen, Verbesserungsvorschlge, neue
+Fragen und Antworten senden Sie bitte per E-Mail an
+ `detexfaq@dante.de'
+Danke schon jetzt im voraus!
+ Bernd Raichle
+ Rolf Niepraschk
+ Thomas Hafner
+
+1.2 CTAN, das `Comprehensive TeX Archive Network'
+
+
+1.2.1 Was ist CTAN?
+
+CTAN steht fr `Comprehensive TeX Archive Network'. Dies ist ein Verbund
+von z.Z. drei Rechnern im Internet. Hierauf ist fast alles, was mit TeX
+zu tun hat, zu finden. Die Server gleichen ihre Dateien untereinander
+ab, so da Sie auf jedem der drei Rechner dieselben Dateien finden
+knnen. Dadurch ist es gleichgltig, wo Sie die Dateien holen. Sie
+sollten aber bedenken, da es am gnstigsten ist, die Dateien bei dem
+Server zu holen, der Ihnen am nchsten ist. Dies ist fr den
+deutschsprachigen Raum der von DANTE e.V. finanzierte ftp-Server
+
+ ftp.dante.de /tex-archive/ (Mainz)
+
+Die beiden anderen ftp-Server sind
+
+ ftp.tex.ac.uk /tex-archive/ (Cambridge, UK)
+ ctan.tug.org /tex-archive/ (Vermont, USA)
+
+Diese drei Rechner sind auch ber die Namen `dante.ctan.org',
+`cam.ctan.org' und `tug.ctan.org' erreichbar.
+Neben diesen drei Rechnern, die das Rckgrat des CTAN bilden, existieren
+viele weitere ftp-Server, die den kompletten CTAN-Inhalt oder Teile
+davon `spiegeln'. Die aktuelle Liste dieser ftp-Server finden Sie in der
+Datei ``CTAN.sites'' auf einem der CTAN-Server im Verzeichnis
+``/tex-archive/''. Im deutschsprachigen Raum sind dies u.a. (Stand:
+Juli 2000):
+
+ ftp.univie.ac.at /packages/tex/ (Wien, A)
+ gd.tuwien.ac.at /publishing/tex/CTAN/ (Wien, A)
+ sunsite.cnlab-switch.ch /mirror/tex (Zrich,
+ CH)
+ ftp.uni-augsburg.de /pub/tex/ctan/ (Augsburg)
+ ftp.uni-bielefeld.de /pub/tex/
+ (Bielefeld)
+ ftp.tu-chemnitz.de /pub/tex/ (Chemnitz)
+ ftp.gwdg.de /pub/dante/
+ (Gttingen)
+ ftp.informatik.uni-hamburg.de /tex-archive (Hamburg)
+ ftp.uni-mainz.de /tex-archive (Mainz)
+ ftp.mpi-sb.mpg.de /pub/tex/mirror/ftp.dante.de/
+ (Saarbrcken)
+ ftp.uni-stuttgart.de /pub/tex/
+ (Stuttgart)
+
+
+1.2.2 Wieso liegen auch Dateien, die zu einem Paket gehren, auf CTAN
+als Einzeldateien und nicht in gepackten Archivdateien?
+
+Die ftp-Server des CTAN und einige der ftp-Server, die den Inhalt von
+CTAN spiegeln, sind in der Lage, alle Dateien eines Verzeichnisses
+zusammenzupacken und `on-the-fly' zu komprimieren. Um herauszufinden,
+welche Archivarten der von Ihnen benutzte Server untersttzt, lesen Sie
+die Mitteilung, die Sie erhalten, wenn Sie den Server direkt ansprechen.
+Mchte man alle Dateien des Verzeichnisses
+``tex-archive/macros/latex/base/'' bekommen, reicht es, in das
+bergeordnete Verzeichnis zu wechseln und eine der Endungen ``.tar'',
+``.tar.gz'' oder ``.zip'' an den Namen des Verzeichnisses zu hngen. Um
+alle Dateien im Verzeichnis als tar- oder ZIP-Datei zu erhalten:
+
+ local> ftp ftp.dante.de
+ user: ftp
+ logging in anonymously ...
+ Guest login ok, send your complete e-mail address as password.
+ password: *****************
+ ftp> cd tex-archive/macros/latex
+ ftp> bin
+ ftp> get base.tar.gz
+
+oder
+
+ ftp> get base.zip
+
+Bei Verwendung eines WWW-Browsers durch Eingabe der Adresse (URL)
+
+ ftp://ftp.dante.de/tex-archive/macros/latex/base.tar.gz
+
+oder
+
+ ftp://ftp.dante.de/tex-archive/macros/latex/base.zip
+
+
+1.2.3 Wie suche ich auf CTAN nach der Datei `XYZ'? Ich kann ein Paket
+mit Endung `.sty' nicht finden.
+
+Um nach einer Datei zu suchen, die im Namen beispielsweise `multicol'
+enthlt, kann man bei den ftp-Servern des CTAN (und einigen
+Spiegel-ftp-Server) in der ftp-Sitzung die Anweisung
+
+ ftp> quote site index multicol
+
+eingeben. Der Suchbegriff ist dabei ein regulrer Ausdruck, d.h. alle
+besonderen Zeichen, wie das Zeichen `.', mssen mit einem doppelten
+Backslash gequotet werden. Will man beispielsweise nach der Datei
+``caption.sty'' suchen, so sollte man
+
+ ftp> quote site index /caption\\.
+
+eingeben. Der fhrende Slash `/' und abschlieende gequotete Punkt `.'
+schrnkt die Ergebnisliste stark ein. Auerdem fhrt die Suche nach
+LaTeX-Paketen mit `.sty' nicht immer zum Ziel, da neuere Pakete meist in
+docstrip-Archivdateien mit der Dateiendung `.dtx' eingepackt vorliegen.
+Weitere Informationen findet man auf CTAN in den Dateien
+``README.archive-features'' und ``README.site-commands''.
+Eine hnliche Mglichkeit, per WWW-Browser nach Dateien auf CTAN zu
+suchen, bieten die Adressen
+ http://www.dante.de/cgi-bin/ctan-index
+und
+ http://www.ctan.org/find.html
+
+1.2.4 Wie kann ich ohne Internet-Anschlu auf CTAN zugreifen?
+
+Falls Sie keinen Internet-Anschlu haben, knnen Sie auf den ftp-Server
+auch ber E-Mail mit Hilfe eines sogenannten `ftp-Mailer' zugreifen.
+Beachten Sie bitte, da bei unachtsamer Nutzung sehr groe Datenmengen
+verschickt werden knnen und die dazu notwendigen Ressourcen
+(bertragungszeit, Speicherplatz) zur Verfgung stehen mssen. Auerdem
+sollten Sie daran denken, da eventuell die Betreiber von
+`Zwischenknoten', ber die Ihre E-Mail weitergeleitet wird, fr Ihre
+bertragene Datenmenge mitzahlen mssen! Die Nutzung eines ftp-Mailer
+ist im Maus-Netz nicht gestattet.
+Weitere Informationen ber den ftp-Mailer und die zu benutzenden
+Anweisungen erhalten Sie mit einer E-Mail an `ftpmail@dante.de' mit dem
+Inhalt ``help''.
+
+1.3 Newsgroups und Diskussionslisten
+
+
+1.3.1 Was ist `de.comp.text.tex'?
+
+`de.comp.text.tex' ist die Newsgroup im deutschsprachigen Teil des
+Usenet (bitte nicht mit Internet verwechseln!) zur Diskussion ber TeX
+und verwandte Themen. Die Newsgroup `de.comp.text.tex' wird durch
+sogenannten Import auch in anderen Netzen angeboten. Um entsprechende
+Rcksichtname (kurze Postings, keine Binrdateien etc.) wird gebeten.
+Weiterhin sollte auf folgendes geachtet werden:
+
+* Verwendung einer korrekten Absenderadresse.
+* Keinen Text in HTML-Kodierung sondern nur in Textformat versenden
+ (kann leicht in den blichen Mail-Programmen so eingestellt werden).
+* Keine ``Visitenkarten'' anhngen.
+* Signaturangaben auf 4 Zeilen beschrnken und mit der Zeile ``-- ''
+ einleiten.
+* Die Verwendung von Umlauten und scharfem s in der Subject-Zeile
+ vermeiden.
+* Bei Antworten sollte man die Subject-Zeile standardgem mit `Re: '
+ einleiten und nicht, wie man es leider immer hufiger sieht, mit
+ bersetzungen wie `AW: ' oder durchnumerierten Konstruktionen
+ `Re[2]: '.
+
+Weitere ntzliche Hinweise enthlt die Newsgroup `de.newusers.infos'
+sowie die WWW-Seite ``Wie zitiere ich im Usenet?''.
+
+Wie zitiere ich im Usenet?: http://learn.to/quote
+
+
+
+1.3.2 Was ist TeX-D-L?
+
+TeX-D-L ist eine E-Mail-Diskussionsliste, die zur Kommunikation zwischen
+Benutzern des Satzsystems TeX vor ber einem Jahrzehnt eingerichtet
+wurde. Die Diskussionssprache ist Deutsch.
+Man kann sich auf dieser Liste mit einer E-Mail an
+ `listserv@listserv.dfn.de'
+eintragen. Diese Mail sollte die Zeile
+
+ subscribe tex-d-l <Vorname> <Nachname>
+
+enthalten, wobei man fr <Vorname> <Nachname> den eigenen Namen angeben
+mu. Die Liste kann man verlassen, indem man in einer E-Mail die Zeile
+``unsubscribe tex-d-l'' an die Adresse `listserv@listserv.dfn.de'
+schickt. Eine kurze Befehlsbersicht ber die Bedienmglichkeiten des
+Programms, das die Liste verwaltet, erhlt man mit der Zeile ``help'',
+eine lngere Beschreibung mit ``info''.
+Die Beitrge zur Liste sind in Teilen unter CTAN: info/digests/tex-d-l/
+archiviert. Mit der Zeile ``index TEX-D-L'' erhlt man eine Liste von
+Archiven lterer Beitrge, die mit ``get filename NAME'' angefordert
+werden knnen.
+Listenbeitrge ab 1998 sind ber die URL
+http://www.listserv.dfn.de/archives/tex-d-l.html zugnglich. Von dieser
+Seite hat man auch die Mglichkeit, sich mittels WWW-Browser in die
+Liste ein- oder auszutragen.
+Fr die Art der versendeten E-Mails gilt ebenso das im vorigen Abschnitt
+zur Newsgroup `de.comp.text.tex' gesagte.
+
+1.3.3 Was ist ``#tex''?
+
+``#tex'' ist ein Channel im _Internet Relay Chat_ (IRC), in dem
+interaktiv ber TeX, LaTeX und Konsorten diskutiert wird. Meist wird
+deutsch gesprochen, Diskussionen auf englisch sind jedoch kein Problem.
+Der Channel ist im allgemeinen rund um die Uhr besetzt, wenn auch nicht
+immer mit der gleichen Aktivitt.
+
+1.3.4 Gibt es noch weitere interessante Diskussionslisten zum Satzsystem
+TeX?
+
+Ja - solche, die sich nur mit dem Satzsystem TeX beschftigen oder auf
+eine bestimmte Implementierung, Verteilung oder einen bestimmten Teil
+konzentrieren. In allen unten genannten Diskussionslisten ist, falls im
+Kommentar nichts Gegenteiliges steht, Englisch die gemeinsame Sprache.
+In die nachstehenden Diskussionslisten trgt man sich wie folgt ein:
+Falls die Verwaltungsadresse vom Typ `listserv@...' ist, so trgt man
+sich mit einer Mail mit `subscribe <Listenname> <Vorname> <Nachname>' an
+die angegebene Verwaltungsadresse ein. Fr Verwaltungsadressen des Typs
+`majordomo@...' mu die Angabe des eigenen <Vornamen> und <Nachnamen>
+unterbleiben, in Ihrer Mail sollte also nur die Zeile `subscribe
+<Listenname>' stehen.
+Aus einer Liste kann man sich mit der Mail `unsubscribe <Listenname>' an
+die Verwaltungsadresse `listserv@...' bzw. `majordomo@...' austragen.
+Achtung: Diese Anweisungen nicht an die Listenadresse selbst schreiben,
+da man sich damit nicht austrgt; im Gegenteil wrde Ihre Mail dann an
+_alle_ Listenteilnehmer weiterverteilt werden!
+
+Allgemeine Listen ber das Satzsystem TeX
+
+
+* CTAN-Ann - Ankndigungen zu Neuerwerbungen und nderungen auf CTAN
+ (`majordomo@dante.de').
+* TeX-Euro - europische TeX-Diskussionsliste
+ (`listserv@urz.uni-heidelberg.de').
+* TeXhax - TeX-Diskussionsliste in Digest-Form
+ (`TeXhax-Request@tex.ac.uk' - subscribe texhax); wird u.a. unter
+ http://www.tex.ac.uk/tex-archive/digests/hyper/ und
+ CTAN: info/digests/texhax/ archiviert.
+* Ling-TeX - Linguistik und TeX (`Ling-TeX-request@ifi.uio.no')
+ siehe auch: http://www.ifi.uio.no/~dag/ling-tex.html.
+
+
+Formate und Makropakete
+
+
+* LaTeX-L - ber die Entwicklung von LaTeX3, jedoch _nicht_ fr Fragen
+ zu LaTeX! (`listserv@urz.uni-heidelberg.de')
+* ntg-context - ConTeXt-Forum: Fragen, Ankndigungen, Fehler
+ (`majordomo@ntg.nl')
+* ntg-ppchtex - Chemischer Formelsatz mit PPCHTeX (`majordomo@ntg.nl')
+* pstricks - ber PSTricks, ein TeX-Makro-Paket, welches die Nutzung
+ vieler Mglichkeiten der PostScript-Sprache in einer TeX-Syntax
+ anbietet (`pstricks-request@mail.tug.org' oder ber
+ http://www.tug.org/cgi-bin/lwgate/pstricks).
+* mutex - Notensatz unter TeX mit MuTeX, MusicTeX, MusiXTeX, etc.
+ (`majordomo@gmd.de'); wird unter http://www.gmd.de/Mail/mutex-archive/
+ archiviert.
+* xindy - ber Xindy, den Makeindex-Nachfolger
+ (`xindy-request@iti.informatik.tu-darmstadt.de').
+* latex2html - ber LaTeX2HTML, einen Konverter nach HTML
+ (`majordomo@tug.org' und http://tug.org/mailman/listinfo/latex2html);
+ wird unter http://www.xray.mpe.mpg.de/mailing-lists/latex2html/
+ archiviert.
+
+
+TeX-Implementierungen und -Verteilungen
+
+
+* tetex-announce - teTeX Users: nur Ankndigungen, keine Diskussion,
+ besonders geeignet fr diejenigen, die ohnehin schon genug Mail
+ bekommen, bzw. Fragen und Antworten lieber in Newsgroups wie
+ `de.comp.text.tex' diskutieren mchten
+ (`majordomo@informatik.uni-hannover.de')
+* tetex - Ankndigungen, Fragen und Antworten zu teTeX
+ (`majordomo@informatik.uni-hannover.de')
+* tetex-pretest - Fragen und Antworten zur neuesten, noch nicht
+ offiziellen Version von teTeX (`majordomo@informatik.uni-hannover.de')
+* fptex - Ankndigungen, Fragen und Antworten zu fpTeX (Win32)
+ (`majordomo@tug.org' und http://tug.org/mailman/listinfo/fptex/)
+* miktex - Ankndigungen, Fragen und Antworten zu MikTeX (Win32)
+ (`majordomo@dsts.dk')
+* 4TeX - 4TeX/4allTeX: eine TeX-Workbench fr MS-DOS-Rechner
+ (`listserv@nic.surfnet.nl').
+* emtex-user - Diskussionen ber emTeX (`Majordomo@Physik.TU-Berlin.de')
+* oztex-info - ber OzTeX, ein TeX-System fr Apple Macintosh
+ (`majordomo@maths.adelaide.edu.au').
+* oztex-announce - OzTeX: nur Ankndigungen neuer Versionen
+ (`majordomo@maths.adelaide.edu.au').
+* ntex - NTeX, a TeX System for Linux and other Unix Systems
+ (`ntex-request@machnix.mathematik.uni-stuttgart.de')
+* tex-k - Support fr web2c/kpathsea/xdvik/dvipsk/dviljk Users
+ (`majordomo@tug.org' und http://tug.org/mailman/listinfo/tex-k/)
+* lyx-users - Support fr Nutzer von LyX, einer WYSIWYG-hnlichen
+ Oberflche, das LaTeX als Satzsystem verwendet
+ `lyx-users-request@kde.org')
+* lyx-announce - Ankndigungen zu Neuerungen bei LyX
+ (`majordomo@via.ecp.fr')
+* lyx - Diskussion zur Weiterentwicklung von LyX
+ (`majordomo@via.ecp.fr')
+* klyx - Support fr Nutzer von KLyx, einer Lyx-Implementierung, die an
+ den KDE-Desktop angepat ist (`klyx-request@kde.org')
+* ntg-vtex - Diskussionen zum kommerziellen TeX-System `VTeX';
+ (`majordomo@ntg.nl')
+
+
+Erweiterungen an TeX
+
+
+* NTS-L - ber die Idee eines ``New Typesetting System'', eines
+ Nachfolgers des TeX-Systems (`listserv@urz.uni-heidelberg.de').
+* Omega - ber Omega, ein weiterer TeX-Nachfolger (`listserv@ens.fr' -
+ SUBscribe omega).
+* pdftex - ber die Entwicklung und Benutzung von PDFTeX
+ (`majordomo@tug.org' und http://tug.org/mailman/listinfo/pdftex/).
+* ntg-toekomsttex- Liste der niederlndischen `TeX future group', in der
+ ber Erweiterungen am TeX-System diskutiert wird
+ (`majordomo@let.uu.nl').
+
+
+METAFONT, METAPOST und Schriften
+
+
+* Metafont - ber METAFONT, METAPOST und Meta-Fonts (`listserv@ens.fr' -
+ SUBscribe metafont).
+* Metapost - ber METAPOST
+ (http://www.ntg.nl/mailman/listinfo/metapost).
+* tex-fonts - (`tex-fonts-request@math.utah.edu', nicht mehr erreichbar)
+* fontinst - (`fontinst-request@cogs.susx.ac.uk')
+* math-font-discuss - (`math-font-discuss-request@cogs.susx.ac.uk')
+
+
+Umfeld
+
+
+* typo-l - ber Typografie (`listserv@irlearn.ucd.ie')
+* sgml-l - ber SGML (`listserv@urz.uni-heidelberg.de')
+
+und vieles mehr. Eine bersicht der bei der TUGbeheimateten
+Diskussionslisten gibt es auf der WWW-Seite
+http://tug.org/mailman/listinfo/.
+
+1.3.5 Gibt es noch weitere interessante Newsgroups zum Satzsystem TeX?
+
+Ja - solche, die sich nur mit dem Satzsystem TeX beschftigen oder die
+auf das engere und weitere Umfeld, wie beispielsweise Schriften,
+PostScript, Design, Desktop Publishing (DTP) etc. eingehen. In allen
+unten genannten Newsgroups ist, wenn im Kommentar nichts Gegenteiliges
+steht, Englisch die gemeinsame Sprache.
+
+Allgemeine Listen ber das Satzsystem TeX
+
+
+* `comp.text.tex' - das Gegenstck zu `de.comp.text.tex' im
+ internationalen Bereich.
+
+
+Umfeld
+
+
+* `comp.fonts'
+* `comp.programming.literate'
+* `comp.lang.postscript'
+* `comp.text.sgml'
+* `comp.text.xml'
+
+und vieles mehr.
+
+1.3.6 Gibt es noch weitere FAQ-Listen?
+
+
+* UK TUG TeX FAQ - ``Your 100+x Questions answered'' (in englisch).
+ Von der UK TUG wurde die frhere FAQ der Newsgroup `comp.text.tex' zur
+ Verffentlichung in `Baskerville' (siehe Frage 2.2.2) neu bearbeitet
+ und stark ergnzt. Die FAQ ist im dvi-, ps- und pdf-Format, jedoch
+ nicht immer in der neuesten Version, in CTAN: help/uk-tex-faq/ zu
+ finden. Auerdem gibt es eine HTML-Version, die nach Begriffen
+ durchsucht werden kann.
+* LaTeX-FAQ der Newsgroup `fr.comp.text.tex' (in franzsisch).
+ Diese FAQ wird monatlich gepostet und ist ca. 150KB gro. Sie wird
+ (noch) nicht nach `news.answers' gepostet, man kann sie daher nicht in
+ den FAQ-Archiven finden. ber WWW und CTAN ist jedoch eine Kopie
+ verfgbar.
+* PDFTeX-FAQ (in englisch),
+ Oft gestellte Fragen zu PDFTeX, einer Modifikation von TeX, welche in
+ der Lage ist, Dateien im _Portable Document Format_ der Firma Adobe zu
+ erzeugen.
+* Seminar-FAQ (in englisch).
+ Oft gestellte Fragen zum LaTeX-Paket `seminar', welches eine Vielzahl
+ von Mglichkeiten zum Erstellen von Folien bietet.
+* PPCHTeX-FAQ (in deutsch).
+ Oft gestellte Fragen zum PPCHTeX-Paket, welches chemischen Formelsatz
+ mit TeX ermglicht.
+
+
+UK TUG TeX http://www.tex.ac.uk/cgi-bin/texfaq2html?introduction=yes
+FAQ:
+ CTAN: help/uk-tex-faq/
+LaTeX-FAQ http://www.loria.fr/tex/divers.html
+franaise:
+ CTAN: help/LaTeX-FAQ-francaise/
+PDFTeX-FAQ: http://www.tug.org/applications/pdftex/
+Seminar-FAQ: http://www.tug.org/applications/Seminar/
+PPCHTeX-FAQ: http://www.ntg.nl/context/document.htm
+
+
+
+1.3.7 Was sollte ich gelesen haben, bevor ich eine Frage in
+`de.comp.text.tex' oder der Diskussionsliste TeX-D-L stelle?
+
+Zuerst: Die Kenntnis der `Netiquette' wird vorausgesetzt; sie ist in
+`de.newusers.infos', `de.newusers.questions' oder ersatzweise bei Ihrem
+Provider zu erhalten (siehe auch
+http://www.netservice.ch/german/netiquette_ger.html).
+Die Abschnitte `Bcherliste' und `frei verfgbare (La)TeX-Einfhrungen'
+(siehe Abschnitte 2.4.1 und 2.4.2) enthalten einige Empfehlungen fr
+Bcher und kostenfrei erhltliche Einfhrungen und bersichten, die sehr
+viele der hufig gestellten Fragen beantworten. Wenn Sie sich vorlufig
+keine Bcher zulegen wollen, sollten Sie dieses Angebot der kostenfrei
+erhltlichen Artikel nutzen!
+Jedes TeX-System enthlt einen Satz Dokumentation, in dem meist nur sehr
+kurz ein berblick ber das Satzsystem TeX gegeben wird, bevor auf
+spezifische Besonderheiten dieses TeX-Systems eingegangen wird. Bevor
+Sie Fragen zu Problemen mit diesem speziellen System stellen, sollten
+Sie sicherstellen, ob diese nicht schon durch die mitgelieferte
+Dokumentation beantwortet werden. Fr einige TeX-Systeme, wie
+beispielsweise emTeX, 4TeX/4allTeX (beide OS/2, MS-DOS, Windows), teTeX,
+NTeX, web2c/kpathsea (Unix/Linux u.a.) gibt es eigene Diskussionslisten.
+Haben Sie ein spezielles Problem mit einem dieser Systeme, sollten Sie
+Ihre Frage in der zugehrigen Diskussionsliste stellen.
+Bei Problemen mit LaTeX sollten Sie vorher auf alle Flle den `User
+Guide' gelesen haben, der als Datei ``usrguide.tex'' jedem LaTeX-Paket
+beiliegen mu und die Neuerungen von LaTeX2e beschreibt. Auch die
+anderen im LaTeX-Paket enthaltenen `Guides' enthalten wertvolle
+Informationen ber das sogenannte NFSS zur Schriftauswahl und Einbindung
+neuer Schriften (`LaTeX2e font selection', Datei ``fntguide.tex''), die
+Erstellung und nderung von Klassen und Paketen (`LaTeX2e for class and
+package writers', Datei ``clsguide.tex''), die Konfiguration
+(`Configuration options for LaTeX2e', Datei ``cfgguide.tex'') und
+erlaubten nderungen und Anpassungen (`Modifying LaTeX2e', Datei
+``modguide.tex''), weitere Pakete und Neuerungen (`LaTeX News', Dateien
+``ltnews*.tex'').
+Fr LaTeX finden Sie auerdem noch sehr viele Informationen und Hinweise
+auf Makro-Pakete im Buch `Der LaTeX-Begleiter' von Goossens, Mittelbach
+und Samarin (siehe Frage 2.4.1) bzw. dem englischen Original `The LaTeX
+Companion'. Schlagen Sie bitte zuerst dort nach - Sie werden
+feststellen, da sich dadurch sehr viele Fragen beantworten lassen.
+Neben dem Buch `The LaTeX Companion' gibt es auch `The LaTeX Graphics
+Companion', in dem Sie wertvolle Hinweise zu Graphikeinbindung,
+PostScript-Graphiken, Verwendung von Farbe, der Einbindung von
+PostScript-Schriften und Paketen wie XY-Pic oder PSTricks nachlesen
+knnen.
+Finden Sie in der verfgbaren Literatur keine Antwort, vergessen Sie
+nicht, in Ihrer Frage an die Newsgroup bzw. die Diskussionsliste auch
+Ihr Rechnersystem, Betriebssystem, Name der TeX-Implementierung bzw.
+-Verteilung, Version der verwendeten Programme, Makros u.. zu nennen.
+Halten Sie Ihre Frage kurz. Geben Sie ein kurzes, aber vollstndiges
+Eingabebeispiel, das nur auf die notwendigsten Dateien zugreift.
+Entfernen Sie beispielsweise in einem LaTeX-Dokument prinzipiell _alle_
+Pakete; belassen Sie dabei nur die Pakete, mit denen Ihr Problem
+auftritt; verwenden Sie mglichst nur Standard- oder weit verbreitete
+Pakete. Fgen Sie am Beginn Ihres (Minimal)-Dokuments die Anweisung
+\listfiles ein, so dass in der Protokolldatei alle verwendeten Pakete
+mit den Versionsnummern aufgefhrt werden. So kann man Ihr Problem mit
+mglichst geringem Aufwand nachvollziehen, und damit erhht sich die
+Wahrscheinlichkeit, da Ihre Frage auch beantwortet wird!
+
+--- DE-TeX-FAQ Ende Teil 1 ---
diff --git a/help/de-tex-faq/part10 b/help/de-tex-faq/part10
new file mode 100644
index 0000000000..4cae778072
--- /dev/null
+++ b/help/de-tex-faq/part10
@@ -0,0 +1,584 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!npeer.de.kpn-eurorings.net!news-kar1.dfn.de!news-ber1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 10 of 11)
+Supersedes: <de-tex-faq-10-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:19 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 555
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-10-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975399 894 134.100.9.52 (19 Sep 2003 12:43:19 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:19 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117407 de.answers:9384 news.answers:258273
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part10
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 10 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+10 METAFONT und Schriften (Fortsetzung)
+
+
+10.1 Die Computer-Modern-Schriften und ihre Nachfolger (+)
+
+
+10.1.1 Gibt es die CM-Fonts auch als PostScript-(Type-1)-Schriften?
+
+Die Knuth'sche Computer-Modern-(CM)-Familie, die zustzlichen
+LaTeX-CM-Fonts und die AmS-Fonts zum mathematischen Formelsatz wurden
+von Bluesky und Y&Y ins Type-1-Format umgesetzt und der ffentlichkeit
+frei verwendbar zur Verfgung gestellt. Die in diesem `Bluesky'-Paket
+noch fehlenden Schriften, wie einige AmS-Fonts, die Logo- und
+Manual-Fonts, sind inzwischen ebenso im Type-1-Format verfgbar.
+
+Bluesky: CTAN: fonts/cm/ps-type1/bluesky/
+AmS-Fonts: CTAN: fonts/amsfonts/ps-type1/
+Logo: CTAN: fonts/mflogo/ps-type1/hoekwater/
+Manual: CTAN: fonts/manual/ps-type1/hoekwater/
+
+
+
+10.1.2 Wie kann ich die CM-Fonts mit beliebigen Schriftgren verwenden?
+
+Das Paket `type1cm' von David Carlisle enthlt genderte
+Font-Deklaratonen fr die CM-Schriften, in denen die blichen festen
+Grenabstufungen durch Bereiche abgedeckt werden. Seine Verwendung ist
+vorzugsweise in Verbindung mit Type-1-Fonts sinnvoll; ansonsten werden
+mglicherweise sehr viele oder sehr groe Pixelfonts erzeugt und
+gespeichert
+
+type1cm: CTAN: macros/latex/contrib/type1cm/
+
+
+
+10.1.3 Was sind EC- und TC-Schriften?
+
+Mit `EC' und `TC' bezeichnet man Fonts mit dem Aussehen von Knuths
+CM-Schriften, aber einem Zeichenvorrat entsprechend der `europischen'
+T1- und TS1-Kodierung. Die EC-Schriften sind ebenso stabil wie die
+CM-Schriften, d.h. die .tfm-Dateien dieser Schriftfamilien werden sich
+nicht mehr ndern.
+
+10.1.4 Wie kann ich mit LaTeX die neuen EC/TC-Schriften verwenden?
+
+Um mit LaTeX die EC-Schriften ohne viel Aufwand benutzen zu knnen,
+bentigt man die LaTeX-Version vom Dezember 1996 oder neuer. Mit dieser
+muss nurmehr in der Prambel die Zeile \usepackage[T1]{fontenc}
+eingefgt werden.
+Um die zustzlichen Textsymbole der TC-Fonts nutzen zu knnen, ist das
+Paket `textcomp' zu laden: \usepackage{textcomp}.
+
+10.1.5 Gibt es die zu den EC-Schriften gehrenden Schriften fr den
+mathematischen Formelsatz?
+
+Nein, leider noch nicht. Zur Zeit existiert ein gemeinsames
+LaTeX3-/TUG-Technical-Working-Group-(TWG)-Projekt; Barbara Beeton,
+Herausgeberin des TUGboat und Mitarbeiterin bei der American
+Mathematical Society (AmS), ist Vorsitzende dieser TWG. Die
+Arbeitsgruppe hat die nicht-triviale Aufgabe, alle bentigten
+mathematischen Zeichen zusammenzutragen und entsprechende
+Schriftkodierungen festzulegen. Informationen ber die bisher
+erarbeiteten Konzepte kann man in http://www.tug.org/twg/mfg finden.
+
+10.1.6 Wieso werden bei Verwendung von EC-Schriften noch die alten
+CM-Schriften geladen? Ich dachte, dass die EC- die CM-Schriften
+vollstndig ersetzen knnen?
+
+Da noch keine mathematischen Schriften speziell fr die EC-Schriften
+existieren, werden die der CM-Schriften verwendet. Die CM-Textschriften
+enthalten jedoch die groen griechischen Buchstaben fr den
+mathematischen Formelsatz, so dass auch weiterhin diese Textschriften
+zustzlich zu den EC-Textschriften geladen werden mssen.
+
+10.1.7 Gibt es die EC- und TC-Fonts auch im PostScript-(Type-1)-Format?
+
+Bis vor einiger Zeit gab es die EC/TC-Schriften nicht im Type-1-Format;
+inzwischen existieren jedoch mehrere kommerzielle und freie Versionen:
+MicroPress Inc. bietet smtliche 666 Schriftschnitte der EC- und
+TC-Schriften im Type-1-Format kommerziell an.
+Kostenlos verfgbar sind zwei weitere Sammlungen von Type-1-Fonts:
+`CM-Super' von Vladimir Volovich und `Tt2001' von Szab Pter.
+`CM-Super' enthlt auch die Computer-Modern-Schriften mit kyrillischem
+Zeichensatz (LH-Fonts). Momentan weisen beide Sammlungen noch geringe
+qualitative Mngel auf.
+Die kommerzielle Schriftfamilie `EM' von Y&Y enthlt zwar alle Lettern
+der EC-Schriften, jedoch unterscheiden sich die Metriken von den
+Original-EC-Schriften; auerdem werden betrchtlich weniger verschiedene
+Entwurfsgren benutzt. Man erhlt daher einen anderen Umbruch, so dass
+sie keinen wirklichen Ersatz darstellen. Andererseits sind sie, im
+Gegensatz zu den originalen EC-Fonts, auch mit Anwendungen aus der
+nicht-TeX-Welt verwendbar (`ATM-kompatibel').
+Sollte keines der genannten Pakete verfgbar sein, kann man als
+`Notlsung' zu den AE- oder ZE-Fonts greifen (siehe Frage 10.1.8).
+
+EC-Type-1 http://www.micropress-inc.com/fonts/ecfonts/ecmain.htm
+(MicroPress):
+CM-Super: CTAN: fonts/ps-type1/cm-super/
+Tt2001: CTAN: fonts/ps-type1/ec/
+ http://www.inf.bme.hu/~pts/textrace/
+EM (Y&Y): http://www.yandy.com/em.htm
+
+
+
+10.1.8 Was sind die `AE'- und `ZE'-Schriften?
+
+Ein nicht ganz vollwertiger Ersatz von EC-Schriften im Type-1-Format
+besteht darin, spezielle _virtuelle Fonts_ zu benutzen. Diese virtuellen
+Fonts stellen (fast) den kompletten T1-Zeichensatz bereit, greifen
+letztlich auf die OT1-kodierten CM-Fonts zurck, und da letztere in
+praktisch jedem TeX-System im Type-1-Format verfgbar sind, bekommt man
+somit auch einen Ersatz fr die EC-Schriften im Type-1-Format.
+Allerdings unterscheiden sich die Metriken und die verfgbaren
+Entwurfsgren von den echten EC-Fonts, so dass sich ein anderer Umbruch
+ergibt.
+Solche virtuellen Schriften sind unter den Namen `Almost-European' (AE)
+und `ZE' verfgbar. Man beachte aber, dass nicht _alle_ Zeichen des
+T1-Encodings bereitgestellt werden. Auch wird nur der T1-Zeichenvorrat
+simuliert, nicht aber TS1, so dass die Textcompanion-Symbole wie z.B.
+`\textmu' nicht verfgbar sind. Fr einige der fehlenden Zeichen gibt es
+Ersatzlsungen. So erhlt man die mit den AE-Schriften nicht
+darstellbaren franzsischen Anfhrungszeichen durch zustzliches
+Einbinden des Paketes `aeguill'. Es extrahiert franzsische `Guillemets'
+aus anderen Schriften, vorzugsweise aus den `PL'-Schriften, einer
+polnischen Variante der CM-Schriften mit einigen zustzlichen
+europischen Zeichen. Die PL-Schriften liegen als METAFONT- und als
+PostScript-Type-1-Schriften vor, die dieselben Metrikdateien verwenden.
+Um sie in ihrer Kodierung OT4 benutzen zu knnen, mssen die
+dazugehrigen Fontdefinitionsdateien aus dem Bndel `platex' installiert
+sein. Optional kann das Paket `aeguill' aber auch auf andere,
+standardmig vorhandene Fonts, zurckgreifen.
+
+ae: CTAN: fonts/ae/
+ze: CTAN: fonts/zefonts/
+aeguill: CTAN: macros/latex/contrib/aeguill/
+PL-Schriften (Type-1): CTAN: language/polish/plpsfont/
+platex: CTAN: macros/latex/contrib/platex/
+
+
+
+10.1.9 Ich erhalte die Meldung `LaTeX Font Warning: Some font shapes
+were not available, defaults substituted'. Was hat das zu bedeuten? (+)
+
+Bei LaTeX ist es mglich, Kombinationen von Schriftattributen
+anzufordern, die bei der verwendeten Schrift nicht verfgbar sind. So
+wird beispielsweise bei der Kombination von ``Kapitlchen'' und `Fett'
+in der Standard-Codierung OT1 mit CM-Fonts:
+
+ \documentclass{article}
+ \begin{document}
+ \textsc{Test \textbf{Test}}
+ \end{document}
+
+von LaTeX folgende Warnung gemeldet:
+
+ LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined
+ (Font) using `OT1/cmr/bx/n' instead on input line 4.
+
+Diese Warnung besagt, dass in der Codierung OT1 in der Familie cmr
+(Roman) und der `Font series' bx (Fett) kein `Font shape' sc
+(Kapitlchen) verfgbar ist und stattdessen `Font shape' n (Normal)
+verwendet wird.
+Immer, wenn LaTeX solche Ersetzungen vornimmt, meldet es fr alle
+Ersetzungen zusammen am Schluss noch `LaTeX Font Warning: Some font
+shapes were not available, defaults substituted', weil Meldungen am Ende
+des LaTeX-Laufs nicht so leicht bersehen werden.
+Welche Ersetzung LaTeX vornimmt, ist in den .fd-Dateien definiert.
+Nheres dazu ist in dem LaTeX-Standarddokument `selection: Kurzname im
+Text, fntguide/fntguide.html: Paketname selection: Kurzname im Text,
+html/fntguide/fntguide.html: Paketname LaTeX2e font selection' zu
+finden.
+
+10.1.10 Was kann ich tun, wenn ich eine Meldung ber eine nicht
+vorhandene Schriftkombination erhalte? (+)
+
+Grundstzlich gibt es in diesem Fall nur zwei Mglichkeiten. Zum einen
+kann man natrlich nach Schriften suchen, bei denen die gewnschte
+Kombination vorhanden ist. So sind beispielsweise fette Kapitlchen in
+der Standardschrift CM nicht vorhanden, in den EC-Fonts hingegen sehr
+wohl. Fgt man daher im Beispiel aus Frage Frage 10.1.9 die Zeile
+
+ \usepackage[T1]{fontenc}
+
+ein, so verschwindet die Meldung.
+Alternativ kann man auf die entsprechende Kombination schlicht
+verzichten. In einigen Fllen gengt es daszu, die Warnung schlicht zu
+ignorrieren. Man kann aber auch die Notwendigkeit der Kombination
+beseitigen. Hat man beispielsweise serifenlose berschriften
+voreingestellt, bentigt jedoch unbedingt Kapitlchen in den
+berschriften, so hat man das Problem, dass es sehr wenige Schriften mit
+serifenlosen Kapitlchen gibt. Eine einfache Lsung besteht nun darin,
+die Voreinstellung der berschriften in eine Serifenschrift zu ndern.
+Viele unterschiedliche Warnungen ber nicht vorhandene
+Schriftkombinationen knnen auch ein Hinweis sein, dass versucht wird,
+bermig viele Schriften zu kombinieren. Aus typografischer Sicht
+knnte die Eliminierung der Kombinationen eine gute Lsung sein. Man
+sollte nmlich nie zu viele Schriftarten miteinander kombinieren.
+
+10.2 Alternativen zu den Computer-Modern-Schriften (*)
+
+
+10.2.1 Wie kann ich die PostScript-Basisschriften (Times, Helvetica
+usw.) mit LaTeX verwenden?
+
+Die Pakete und Metrikdateien des `PSNFSS'-Bndels untersttzen die
+Verwendung der 35 PostScript-Basisschriften mit LaTeX. `PSNFSS' ist
+Bestandteil jedes LaTeX-Systems.
+
+ Times:
+ Das Paket `mathptmx' deklariert `Times' als Grundschrift und ldt
+ dazu passende Mathematikschriften, die aus verschiedenen frei
+ verfgbaren Fonts (z.B. `Symbol') zusammengesetzt sind.
+
+ Palatino:
+ Die Pakete `mathpazo' und `mathpple' legen `Palatino' als
+ Grundschrift fest und laden dazu passende Mathematikschriften, die
+ aus frei verfgbaren Fonts zusammengesetzt sind. Im Wesentlichen
+ unterscheiden sich die Pakete durch das Aussehen der griechischen
+ Buchstaben und einiger mathematischer Symbole; das ltere
+ Paket`mathpple' greift dafr vor allem auf (modifizierte)
+ Euler-Fonts zurck, whrend `mathpazo' ein neu entworfenes
+ mathematisches Alphabet `Pazo' verwendet.
+
+ Helvetica:
+ Das Paket `helvet' legt `Helvetica' als serifenlose Schrift fest.
+
+ Courier:
+ Das Paket `courier' legt `Courier' als Schreibmaschinenschrift
+ fest.
+
+ ZapfDingbats
+ und andere Symbolschriften werden vom Paket `pifont' untersttzt.
+
+Weitere Pakete untersttzen die Schriftfamilien `NewCenturySchoolbook',
+`Bookman', `AvantGarde' und `ZapfChancery'. PSNFSS untersttzt auch die
+Verwendung der Schriftfamilien `Bitstream Charter' und `Adobe Utopia'.
+Sie gehren nicht zu den Base35-Fonts, sind aber kostenlos verfgbar und
+sollten standardmig Bestandteil jedes LaTeX-Systems sein.
+Siehe die Dokumentation zu PSNFSS (`Using common PostScript fonts with
+LaTeX').
+
+psnfss: CTAN: macros/latex/required/psnfss
+
+
+
+10.2.2 Wie kann ich ein ganzes Dokument in serifenloser Schrift (z.B.
+Helvetica) setzen? (*)
+
+Die Anweisung
+
+ \renewcommand{\familydefault}{\sfdefault}
+
+in der Prambel legt serifenlose Schrift als Grundschrift fr das
+gesamte Dokument fest; das ist diejenige Schriftfamilie, die sonst mit
+der Anweisung `\sffamily' gewhlt wrde. Per Voreinstellung ist das
+`CM-Sans'. Mchte man diese gegen `Helvetica' austauschen, ist
+zustzlich das Paket `helvet' (siehe Frage 10.2.1) zu laden:
+
+ \renewcommand{\familydefault}{\sfdefault}
+ \usepackage{helvet}
+
+Beachte, dass in beiden Fllen LaTeXs Mathematikschriften _nicht_
+gendert werden! Die fr den Mathematiksatz voreingestellten Schriften
+der CM-Familie harmonieren jedoch nur schlecht mit `CM-Sans' und
+berhaupt nicht mit `Helvetica', so dass die genannten Lsungen
+untauglich sind, falls auch mathematische Formeln zu setzen sind.
+Es gibt berhaupt nur zwei serifenlose Schriftfamilien, die fr TeX
+geeignete Mathematikschriften (inkl. der AmS-Symbole) enthalten. Beide
+werden zusammen mit Makropaketen fr die Verwendung mit LaTeX verteilt:
+
+ CM-Bright:
+ Eine aus den CM-Fonts abgeleitete Schriftfamilie; heller und
+ weniger ``aufdringlich'' als `CM-Sans'. Sie ist auf CTAN sowohl im
+ Metafont- als auch im PostScript-Format erhltlich. Die Schriften
+ im Type-1-Format gehren teilweise zur Sammlung CM-Super (siehe
+ Frage 10.1.7), die restlichen wurden von H.~Harders (`hfbright')
+ zur Verfgung gestellt. Ein vollstndiges Paket der
+ CM-Bright-Fonts im Type-1-Format wird auch kommerziell von der Fa.
+ MicroPress Inc. angeboten.
+
+ HV-Math:
+ Eine Helvetica-`Clone', mit erweitertem Zeichensatz und
+ Mathematikschriften; im Type-1-Format von MicroPress Inc.
+ erhltlich.
+
+Die Schriftfamilie `Arial' ist lediglich eine Nachahmung der
+`Helvetica', mit geringen Unterschieden bei den Zeichenformen. Sie wird
+von vielen Programmen als Ersatz fr die echte Helvetica verwendet, z.T.
+ohne dass dies vom Anwender zu beeinflussen ist. Mit TeX kann und sollte
+man stets `Helvetica' oder `HV-Math' verwenden, siehe oben!
+
+CM-Bright: CTAN: fonts/cmbright/
+ CTAN: fonts/ps-type1/cm-super/
+ CTAN: fonts/ps-type1/hfbright/
+ http://www.micropress-inc.com/fonts/
+HV-Math: http://www.micropress-inc.com/fonts/
+
+
+
+10.2.3 Welche anderen als die CM-Schriften sind mit LaTeX ohne groen
+Aufwand verwendbar?
+
+Vergleichsweise problemlos lassen sich mit LaTeX solche Schriften
+einsetzen, die komplett mit allen ntigen TeX-spezifischen Metriken und
+Makrodateien verteilt werden (bzw. in blichen TeX-Distributionen
+vorhanden sind). Idealerweise sollten auerdem dazu passende
+Mathematikschriften vorhanden sein.
+
+Schriftfamilien mit Mathematikfonts
+
+
+ Times:
+ Siehe Frage 10.2.1. Neben den vom Paket `mathptmx' verwendeten
+ Mathematikschriften gibt es auch kommerzielle, die eine deutlich
+ hhere Qualitt aufweisen: `TM-Math' (MicroPress, enthlt auch
+ zustzliche Textsymbole und die AmS-Symbolfonts), `MathTime' und
+ `MathTimePro' (Y&Y).
+
+ Palatino:
+ Siehe Frage 10.2.1. Neben den von dem Paketen `mathpple' und
+ `mathpazo' verwendeten Mathematikschriften gibt es noch die
+ kommerziellen `PA-Math'-Fonts (MicroPress) mit deutlich besserer
+ Qualitt und zustzlichen Textsymbolen.
+
+ LucidaBright:
+ Eine umfangreiche Schrift-`Sippe', bestehend aus Roman-,
+ Sansserif- und Schreibmaschinen-Schriften, zahlreichen Sonder- und
+ Zierschriften und allen Mathematikfonts fr Verwendung mit
+ plainTeX oder LaTeX, einschl. der AmS-Symbole. Nur im
+ Type-1-Format. Kommerziell erhltlich bei Y&Y.
+
+ Concrete:
+ Eine serifenbetonte Antiqua-Schrift; die Grundschrift von Donald
+ Knuths Buch `Concrete Mathematics'; aus der CM-Familie abgeleitet.
+ Enthlt neben Textfonts auch alle Mathematikschriften fr (La)TeX
+ inkl. der AmS-Symbole. Im Metafont-Format kostenlos und
+ Bestandteil der meisten TeX-Systeme; im Type-1-Format von
+ MicroPress vertrieben. LaTeX-Paket: `ccfonts'
+
+ CM-Bright:
+ siehe Frage 10.2.2.
+
+ Helvetica/HV-Math:
+ siehe Frage 10.2.2.
+
+ BA-Math:
+ Eine Antiqua-Schrift im Stil der `Baskerville', mit
+ Mathematikschriften fr LaTeX; Type-1-Format. Erhltlich bei
+ MicroPress.
+
+ IF-Math:
+ Eine Tekton-`Clone' mit Mathematikschriften fr LaTeX;
+ Type-1-Format. Erhltlich bei MicroPress.
+
+
+Schriftfamilien ohne Mathematikfonts
+
+
+ AvantGarde, Bookman, Charter, Helvetica, NewCenturySchoolbook, Utopia:
+ Die Verwendung dieser Schriftfamilien wird durch die Pakete des
+ PSNFSS-Bndels untersttzt, siehe Frage 10.2.1.
+
+ LucidaBrightSO:
+ Die wichtigsten Textschriften der LucidaBright-Familie (_nicht_
+ die Mathematikschriften!) sind auch als Bestandteil von
+ `StarOffice' 5.2 verfgbar. Im Gegensatz zur Variante von Y&Y
+ (siehe oben) enthalten sie neben den lateinischen auch kyrillische
+ Zeichenstze und sind kostenlos erhltlich.
+
+ Pandora:
+ Frei verfgbare, speziell fr die Verwendung mit (La)TeX
+ entworfene Schriftfamilie mit Roman-, Sansserif- und
+ Schreibmaschinen-Schriften. Etwas auffllig und verspielt. Nur mit
+ OT1-Zeichensatz, nur im Metafont-Format.
+
+ Malvern:
+ Frei verfgbare, speziell fr TeX entworfene Familie von
+ serifenlosen Schriften. Nur mit OT1- und T1-Zeichensatz verfgbar,
+ keine TS1-Kodierung; nur im Metafont-Format.
+
+ Litaraturnaya:
+ Schriftfamilie mit lateinischen und kyrillischen Zeichenstzen.
+ Nur Type-1-Format. Kostenlos erhltlich.
+
+
+Generische Mathematikfonts
+
+
+ Die Mathematikschriften TM-Math, MathTime, MathTimePro
+ (siehe oben) wurden ursprnglich fr die Verwendung mit der
+ `Times' entworfen, lassen sich aber auch mit hnlichen
+ Schriftfamilien verwenden; dies wird auch von den dazu gehrenden
+ Makropaketen untersttzt.
+
+ LucidaNewMath
+ Die zu LucidaBright (siehe oben) gehrenden Mathematikschriften
+ lassen sich auch mit anderen Schriftfamilien kombinieren. Ein
+ entsprechendes Makropaket `lucbmath' wird zusammen mit den
+ Schriften ausgeliefert.
+
+ Die mathematischen Euler-Fonts
+ wurden ursprnglich fr die Verwendung mit der Schriftfamilie
+ Concrete entworfen (die inzwischen eigene Mathematikfonts bekommen
+ hat).
+ Die Euler-Fonts lassen sich sehr gut auch mit ganz anderen
+ Textschriften als Concrete kombinieren. Sie passen insbesondere
+ gut zu verschiedenen Renaissance-Antiquas (z.B. Garamond, Sabon,
+ Minion, Palatino). Dies wird durch das neuere Paket `eulervm' und
+ dazu gehrende virtuelle Fonts untersttzt.
+ Die LaTeX-Pakete `euler' und `beton' stellten eine ad-hoc-Lsung
+ fr die Kombination Concrete/Euler dar, die die Typografie vom
+ Donald Knuths Buch `Concrete Mathematics' in LaTeX nachbildet; sie
+ sind veraltet und sollten nicht mehr verwendet werden.
+
+
+MicroPress: http://www.micropress-inc.com/fonts/
+Y&Y: http://www.yandy.com/
+Concrete: CTAN: fonts/concrete/
+ CTAN: fonts/ecc/
+ CTAN: fonts/concmath/
+Pandora: CTAN: fonts/pandora/
+Anpassungen zu
+LucidaBright aus ftp://ftp.ftp.vsu.ru/pub/tex/font-packs/lucidaso/
+StarOffice:
+Literaturnaya: ftp://ftp.vsu.ru/pub/tex/font-packs/literat/
+eulervm: CTAN: fonts/eulervm/
+
+
+
+10.2.4 Wo finde ich TeX-Anpassungen fr handelsbliche Type-1-Fonts?
+
+Auerhalb der Welt von TeX existiert ein riesiges Angebot an
+digitalisierten Schriften. Um sie auch mit (La)TeX verwenden zu knnen
+bentigt man zustzlich zu den eigentlichen Fonts TeX-spezifische
+Metrik-, Font-Map- und .fd-Dateien. Falls man diese nicht selbst
+erstellen kann oder will (siehe Frage 9.2.2), kann man auf vorgefertigte
+Anpassungen zurckgreifen.
+
+psfonts: CTAN: fonts/psfonts
+(z.T. veraltet und nur mangelhaft dokumentiert)
+Walter Schmidt: Schriften fr TeX: http://home.vr-web.de/was/fonts.html
+
+
+
+10.3 Sonderschriften
+
+
+10.3.1 Gibt es eine Schnschrift/Handschrift?
+
+Mit `calligra' gibt es eine kalligraphische Schrift (nur im
+Metafont-Format), eine schn ausgefhrte Schmuckschrift. Eine weitere
+Schnschrift (ebenfalls im Metafont-Format) ist die `twcal', die
+ursprnglich auf der vereinfachten Ausgangsschrift `va' basiert, jedoch
+durch viele nderungen und Ligaturen weichere, durchgezogene bergnge
+erhalten hat. Mit den Paketen `calligra' und `twcal' gibt es
+LaTeX-Anpassungen fr beide gleichnamigen Schriften.
+Zu den PostScript-Standardfonts gehrt der `normale' Schnitt der Schrift
+`ZapfChancery'. Metriken und Makrodateien dafr gehren zum
+PSNFSS-Bndel, siehe Frage 10.2.1.
+Im Type-1-Format ist die Schrift `BrushScriptX' kostenlos verfgbar. Sie
+hnelt der kommerziellen Schrift BrushScript von Adobe. Zusammen mit dem
+Font wird ein passendes Makropaket verteilt.
+Ebenfalls im Type-1-Format ist die Schrift `Augie' als Freeware
+erhltlich, zusammen mit den ntigen Anpassungen zur Verwendung mit TeX;
+sie ist aus einer typischen amerikanischen Schlerhandschrift
+abgeleitet.
+
+calligra: CTAN: fonts/calligra/
+twcal: CTAN: fonts/twcal/
+(METAFONT-Quellen und Paket fr LaTeX 2.09)
+ CTAN: macros/latex/contrib/gene/fundus/
+(Paket fr LaTeX)
+BrushScriptX: CTAN: fonts/brushscr/
+Augie: CTAN: fonts/augie/
+
+
+
+10.3.2 Ich suche eine Stterlin, Fraktur, Schwabacher, Gotische Schrift.
+
+Yannis Haralambous hat einen Satz dieser altdeutschen Schriften auf der
+Tagung EuroTeX'91 in Cork/Irland vorgestellt. Neben den reinen
+Brotschriften hat er auch noch mit der Schrift `yinit' groe Initialen
+als Schmuckschrift hinzugefgt. Die Einbindung dieser Schriften ist fr
+LaTeX2e im Paket `oldgerm', das Bestandteil von `mfnfss' ist, enthalten.
+Mit dem Paket `yfonts' existiert eine Alternative, die mit german.sty
+funktioniert und diese Schriften trotz ihrer unkonventionellen Kodierung
+in LaTeX2e einbindet; ein Makro ermglicht es, einen Absatz mit einer
+eingezogenen Zierinitiale zu schmcken.
+Zu der Stterlin-Schrift `suet14' und ihrer schrggestellten Variante
+`schwell' wurde in der Newsgroup de.comp.tex (dem damaligen Vorgnger
+von `de.comp.text.tex') angemerkt: ``Die Fonts sehen wirklich klasse
+aus. Allerdings hat das kleine `a' keinen Kringel (Schleifchen) rechts
+oben, was es nach Brockhaus und alten Schulunterlagen haben sollte. Auch
+das `k' scheint etwas abzuweichen.''
+
+Y.H.: CTAN: fonts/gothic/yfrak/
+ CTAN: fonts/gothic/yswab/
+ CTAN: fonts/gothic/ygoth/
+ CTAN: fonts/gothic/yinit/
+mfnfss: CTAN: macros/latex/contrib/mfnfss
+yfonts: CTAN: macros/latex/contrib/yfonts
+cmfrak: CTAN: fonts/gothic/cmfrak/
+sueterlin/schwell: CTAN: fonts/gothic/sueterlin/
+
+
+
+10.3.3 Gibt es die lateinische bzw. die vereinfachte Ausgangsschrift,
+mit der man das Schreiben in der ersten Klasse begonnen hat?
+
+
+la: CTAN: fonts/la/
+va: CTAN: fonts/va/
+
+
+
+10.3.4 Gibt es eine Schrift mit Medivalziffern/Minuskelziffern? Wie
+kann ich alle Zahlen in einem Dokument mit Medivalziffern setzen?
+
+Medivalziffern erhlt man in Plain-TeX durch \oldstyle{1234567890}, in
+LaTeX mit \oldstylenums{1234567890}, da TeXs Math-Italic-Schriften diese
+Ziffernform bereits enthalten.
+Will man alle Zahlen in einem Dokument in Medivalziffern ausgeben, ohne
+diese explizit mit `\oldstyle' bzw. `\oldstylenums' auszeichnen zu
+mssen, so bentigt man spezielle Text-Fonts, in denen die meist
+blichen Versalziffern durch Medivalziffern ersetzt wurden. Dies ist
+z.B. in den ECO-Schriften der Fall, die auf den EC-Schriften basieren
+und die als ``virtuelle Schriften'' die Ziffernformen ersetzen.
+
+ECO-Fonts: CTAN: fonts/eco/
+
+
+
+--- DE-TeX-FAQ Ende Teil 10 ---
diff --git a/help/de-tex-faq/part11 b/help/de-tex-faq/part11
new file mode 100644
index 0000000000..695c312192
--- /dev/null
+++ b/help/de-tex-faq/part11
@@ -0,0 +1,784 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!npeer.de.kpn-eurorings.net!newsfeed.freenet.de!news-lei1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 11 of 11)
+Supersedes: <de-tex-faq-11-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:19 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 755
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-11-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975399 895 134.100.9.52 (19 Sep 2003 12:43:19 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:19 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117409 de.answers:9386 news.answers:258275
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part11
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 11 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+11 Tools und Utilities
+
+
+11.1 Tools zur Manipulation von dvi-Dateien
+
+
+11.1.1 Ich mchte durch doppelseitigen Druck und entsprechende Faltung
+eine Broschre in DIN A5 mit Hilfe von DIN A4-Bgen erstellen.
+
+Mit `dvidvi' oder `dvibook' lassen sich die Seiten in einer dvi-Datei so
+umordnen, da auf einem Papierbogen die entsprechenden Seiten
+doppelseitig gedruckt werden knnen. Neben diesen
+dvi-Manipulationsprogrammen knnen auch einige dvi-Gertetreiber die
+Seiten so gedreht und sortiert ausgeben, da man diese zu einer
+Broschre bzw. die einzelnen Bogenpckchen zu einem dickeren Buch binden
+kann. Beispiele fr solche Treiber sind `dvidrv' (emTeX-Paket, OS/2 und
+MS-DOS) `dvi_dot' (MultiTeX-Paket, Atari ST), DVI 3.xx (Atari ST).
+Hilfreich ist hierbei neben der Fhigkeit, die Seiten entsprechend
+anzuordnen, da man die Signaturgre, d.h. die Gre eines Heftchens,
+ber einen Parameter angeben kann (Bsp: `section-count' bei den
+emTeX-Treibern). Verwendet man PostScript, so kann man mit `psbook' (aus
+den PostScript-Utilities) statt der Seiten in der dvi-Datei auch die
+Seiten in der aus der dvi-Datei erzeugten PostScript-Datei umordnen.
+Dabei sollte man darauf achten, da die PostScript-Dateien sogenannte
+`strukturierte Kommentare' enthalten, da `psbook', andere
+PostScript-Utilities und beispielsweise auch `ghostview' diese
+Kommentare bentigen, um den Vorspann und die einzelnen Seiten
+voneinander trennen zu knnen. In `dvips' darf man die Option -N (`No
+structured comments') daher _nicht_ verwenden!
+Lsungsbeispiel mit `dvidvi' und `dvips':
+
+ # Vorderseiten:
+ dvidvi -m '4:-1,2(148.5mm,0mm)' datei.dvi tmp1.dvi
+ dvips -t landscape tmp1.dvi
+ #
+ # Rueckseiten:
+ dvidvi -m '4:-3,0(148.5mm,0mm)' datei.dvi tmp2.dvi
+ dvips -t landscape tmp2.dvi
+ #
+ # danach zuerst die Vorderseiten in `tmp1.ps' ausdrucken, diese in
+ # den Drucker so einlegen, dass die letzte Vorderseite zuerst
+ # eingezogen wird, und dann die Rueckseiten in `tmp2.ps' ausdrucken.
+
+Lsungsbeispiel mit `psbook', `pstops' und `dvips':
+Damit `dvips' auch weiterverarbeitbare PostScript-Seiten im
+DIN A5-Format erzeugen kann, mu in die `dvips'-Konfigurationsdatei
+``config.ps'' noch folgender Eintrag hinzugefgt werden:
+
+ @ A5 148.5mm 210mm
+ @+ %%PaperSize: A5
+ @+ ! %%DocumentPaperSizes: A5
+
+Anschlieend knnen die folgenden Anweisungen abgesetzt werden:
+
+ # Ausgabe im Hochformat in DIN A5
+ dvips -t a5 -o tmp.ps datei.dvi
+
+und nach dem Erzeugen der A5-groen Seiten anschlieend
+
+ # Sortieren der Seiten der PS-Datei, Signaturgroesse: je 16 Seiten
+ # ergibt 4 Boegen (doppelseitig und gefaltet)
+ psbook -s16 tmp.ps tmp-sorted.ps
+ # Zusammenfassen von 4 Seiten auf ein DIN A4-Blatt
+ pstops '4:0L(21cm,0)+1L(21cm,14.85cm),2R(0,29.7cm)+3R(0,14.85cm)' \
+ tmp-sorted.ps datei.ps
+
+Die Vernderung von ``config.ps'' und die Option -t a5 beim Aufruf von
+`dvips' kann entfallen, wenn das Programm `psresize' verwendet wird:
+
+ # Ausgabe im Hochformat (in DIN A5)
+ dvips -o tmp-in.ps datei.dvi
+ # Korrigiere Papiergroessenangabe von A4 auf A5
+ psresize -Pa4 -pa5 tmp-in.ps tmp.ps
+
+Man beachte, da unter manchen Betriebssystemen die Hochkommata
+entfallen oder durch doppelte Hochkommata ersetzt werden mssen. Der
+Backslash am Ende der letzten Anweisung zeigt an, da diese und die
+nachfolgende Zeile zusammengehren!
+
+dvidvi: CTAN: dviware/dvidvi/
+dvibook: CTAN: dviware/dvibook/
+psbook: CTAN: support/psutils/
+psresize: CTAN: support/psutils/
+(unterhalb von CTAN: systems findet man Binaries dieser Programme fr
+verschiedene Systeme)
+Print Output as Booklet: http://www.lyx.org/help/PS/ps.php#booklet
+
+
+
+11.1.2 Ich mchte aus einer bereits fertigen, jedoch fr DIN A4
+formatierte Broschre durch Verkleinerung, doppelseitigen Druck und
+entsprechende Faltung eine Broschre in DIN A5 erstellen.
+
+In Frage 11.1.1 wurden bereits entsprechende Programme vorgestellt, mit
+denen die Manipulationen durchgefhrt werden knnen. Im Unterschied zu
+der dort vorgestellten Lsung sind nun die Seiten zustzlich von DIN A4
+auf DIN A5 zu verkleinern. Diese Skalierung ist typographisch nicht
+empfehlenswert; eine Layout-nderung und Neuformatierung der Vorlage auf
+DIN A5, um eine Skalierung zu vermeiden, wre besser.
+Lsungsbeispiel mit `dvidvi' und `dvips':
+
+ # Vorderseiten:
+ dvidvi -m '4:-1,2(148.5mm,0mm)' datei.dvi tmp1.dvi
+ dvips -t landscape -x 707 tmp1.dvi
+ #
+ # Rueckseiten:
+ dvidvi -m '4:-3,0(148.5mm,0mm)' datei.dvi tmp2.dvi
+ dvips -t landscape -x 707 tmp2.dvi
+ #
+ # danach zuerst die Vorderseiten in `tmp1.ps' ausdrucken, diese in
+ # den Drucker so einlegen, dass die letzte Vorderseite zuerst
+ # eingezogen wird, und dann die Rueckseiten in `tmp2.ps' ausdrucken.
+
+Lsungsbeispiel mit `psbook', `pstops' und `dvips':
+
+ # Ausgabe im Querformat und auf DIN A5 (= 1/sqrt{2}) verkleinert
+ dvips -t landscape -x 707 -o tmp.ps datei.dvi
+ # Sortieren der Seiten der PS-Datei, Signaturgroesse: je 16 Seiten
+ # ergibt 4 Boegen (doppelseitig und gefaltet)
+ psbook -s16 tmp.ps tmp-sorted.ps
+ # Zusammenfassen auf eine DIN A4-Seite
+ pstops '2:0(.744cm,.744cm)+1(.744cm,-14.106cm)' tmp-sorted.ps datei.ps
+
+Man beachte, da unter manchen Betriebssystemen die Hochkommata
+entfallen oder durch doppelte Hochkommata ersetzt werden mssen.
+
+11.1.3 Wenn ich A5-Seiten auf A4-Bgen anordne, warum erscheint das
+Ergebnis immer stark verschoben?
+
+In Frage 11.1.1 und Frage 11.1.2 wurde bereits vorgestellt, wie
+normalerweise eine Broschre in DIN A5 erstellt werden kann. Dabei kann
+jedoch das Problem auftreten, dass das Ergebnis stark verschoben ist und
+deshalb nicht auf einen Papierbogen passt. Dieser Effekt tritt auf, wenn
+durch ein Paket das Papersize-Special in die DVI-Datei geschrieben wird.
+Dies geschieht beispielsweise beim Paket `geometry' bei Verwendung der
+Option `dvips' oder beim Paket `typearea' aus dem KOMA-Script-Paket bei
+Verwendung der Option `dvips' oder der Option `pagesize'.
+Die Lsung fr das Problem ist in diesem Fall ganz einfach. Verzichten
+Sie auf die entsprechende Option und gehen Sie dann wie in den Antworten
+beschrieben vor.
+Wenn Sie eine DVI-Datei erhalten und feststellen wollen, ob ein
+entsprechendes Special enthalten ist, knnen Sie das mit Hilfe des
+Programms `dvitype' erreichen. Gibt `dvitype' unmittelbar nach der Zeile
+
+ <nn>: begin of page1
+
+eine Zeile
+
+ <nn>: xxx 'papersize=597.50793pt,845.04694pt'
+
+aus, dann ist ein solches Special enthalten und das Problem wird
+auftreten. <nn> ist dabei ein Zahlwert, der von Datei zu Datei
+unterschiedlich sein kann. Obige Werte hinter ``papersize='' sind
+natrlich vom eingestellten Papierformat abhngig.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+geometry: CTAN: macros/latex/contrib/geometry/
+
+
+
+11.1.4 Wie kann ich bei doppelseitigem Druck jede zweite Seite umgedreht
+drucken lassen?
+
+Doppelseitige Drucker geben die zweite Seite meist ber die lngere
+Kante gewendet aus, so da hintere Seite eines Papierblattes ``falsch
+herum'' gedruckt wird. Mit einem PostScript-fhigen Drucker und dem
+Programm `pstops' (aus den PostScript-Utilities) kann dies problemlos
+korrigiert werden, indem jede zweite Seite mit der Option `U'
+(upside-down) auf den Kopf gestellt wird:
+
+ pstops '2:0,1U(21cm,29.7cm)' datei.ps datei-2r.ps
+
+Will man wie in Frage 11.1.1 oder Frage 11.1.2 Broschren erstellen,
+sind die dort gezeigten Verfahren durchzufhren. Anschlieend ist dann
+obige Zeile auf das Ergebnis anzuwenden.
+
+pstops: CTAN: support/psutils/
+
+
+
+11.1.5 Ist es mglich, zwei dvi-Dateien zu einer zusammenzumontieren?
+Kann ich einzelne Seiten aus einer dvi-Datei in eine dvi-Datei
+schreiben?
+
+`dviconcat', das im `dvibook'-Paket enthalten ist, hngt dvi-Dateien
+aneinander. Mit `dviselect' aus demselben Paket kann man einzelne Seiten
+bzw. Folgen von Seiten aus einer dvi-Datei extrahieren.
+
+dvibook: CTAN: dviware/dvibook/
+
+
+
+11.1.6 Eine vorhandene PostScript-Datei enthlt Grafiken, die ich fr
+einen anderen Zweck wiederverwenden will. Was kann ich tun?
+
+Das Programm `psrip' kann in vielen Fllen enthaltene EPS-Grafiken aus
+einer PostScript-Datei extrahieren.
+
+psrip: CTAN: support/psrip/
+
+
+
+11.2 Syntax-Checker
+
+
+11.2.1 Ich mchte ein LaTeX-Dokument mglichst schnell auf Fehler
+berprfen.
+
+In LaTeX gibt es das Paket `syntonly', das durch die Anweisung
+`\syntaxonly' in der Dokumentprambel einige LaTeX-Interna so
+umdefiniert, da kein oder nur sprlich dvi-Code erzeugt und so der
+bersetzungslauf beschleunigt wird. Dabei werden weiterhin die meisten
+Fehler, insbesonders syntaktische, von TeX gemeldet. Jedoch knnen auch
+weitere Fehler gemeldet werden, wenn Makros von den intern jetzt nicht
+mehr erzeugten Strukturen abhngen. `syntonly' bentigt die tfm-Datei
+fr den Font `dummy'.
+
+syntonly: CTAN: macros/latex/base/
+dummy: CTAN: fonts/amsfonts/sources/dummy.mf
+ CTAN: fonts/amsfonts/tfm/dummy.tfm
+
+
+
+11.2.2 Gibt es auch noch Syntax-Checker, die schneller sind?
+
+Externe Syntax-Checker, wie `lacheck', `ChkTeX' oder `texchk', sind
+schneller, jedoch kann es vorkommen, da sie z.B. bei
+`verbatim'-hnlichen Umgebungen sehr viele Fehler melden, obwohl keine
+existieren. Meist ignorieren diese Programme auch \input- und
+\include-Anweisungen, so da die einzelnen Dokumentdateien separat
+getestet werden mssen. Sie sind jedoch schnell und ideal zum Finden von
+Fehlern durch inkorrekte Schachtelung von Gruppen/Umgebungen.
+
+lacheck: CTAN: support/lacheck/
+ C/lex-Source von `lacheck' (war frher
+ im AucTeX-Paket enthalten).
+ChkTeX: CTAN: support/chktex/
+ Sources und Binaries fr verschiedene
+ Architekturen.
+texchk: CTAN: obsolete/systems/msdos/4alltex.zip
+disk05/texcheck.zip enthalten. Binary ist im emTeX- und damit auch im
+Der Quelltext wurde in der 4allTeX-Paket in disk05/texcheck.zip
+Newsgroup `comp.sources.unix' enthalten. Der Quelltext wurde in der
+verteilt.: link) Newsgroup `comp.sources.unix' verteilt.
+
+
+11.3 Dokument-Konverter von bzw. in das (La)TeX-Markup-Format (*)
+
+
+11.3.1 Ich habe ein Dokument fr XYZ vorliegen und mchte es in (La)TeX
+umwandeln. Gibt es ein Konvertierungsprogramm?
+
+Fr relativ viele Dokumentformate gibt es Programme, die diese in eine
+(La)TeX-Eingabedatei mit entsprechendem Markup umwandeln. Leider knnen
+die meisten dieser Programme nur eine a) unvollstndige Konvertierung
+durchfhren, b) ein (La)TeX-Dokument mit schlechtem Markup erzeugen oder
+c) brechen mit Fehlern ab oder strzen im schlimmsten Fall ab. Dies
+liegt an unterschiedlichen Grnden, wie z.B. daran, da die
+Markup-Mglichkeiten des anderen Programms nicht mchtig genug sind oder
+da das Dateiformat nicht offiziell dokumentiert vorliegt und daher nur
+unvollstndig und fehlerhaft `re-engineered' wurde. Es ist daher besser,
+wenn Sie nicht allzu viel von diesen Konvertierungsprogrammen erwarten
+und sich darauf einstellen, da Sie noch nacharbeiten mssen.
+Konvertierungsprogramme, die (La)TeX-Dokumente erzeugen, existieren fr
+Word, WordPerfect, RTF, SGML, HTML, troff, Scribe u.v.m.
+
+11.3.2 Ich habe ein (La)TeX-Dokument vorliegen und mchte es in eine
+Form fr XYZ umwandeln. Gibt es ein Konvertierungsprogramm?
+
+Es existieren relativ viele Konvertierungsprogramme, um ein
+LaTeX-Dokument in eine Form zu wandeln, um das Dokument oder Teile
+daraus in anderen Programmen weiterzuverwenden. Auch hier mu man mehr
+oder weniger Abstriche machen, wenn ein Dokument a) nicht strukturiert
+eingegeben und konsistent mit LaTeX-Markup versehen wurde, b) spezielle
+LaTeX-Pakete und -Erweiterungen verwendet, c) mathematische Formeln,
+Tabellen und Grafiken mit der `picture'-Umgebung enthlt oder d) das
+Konvertierungsprogramm spezielle Markup-Deklarationen bentigt. Sie
+mssen daher auch hier entweder das entstandene Ergebnis nachbearbeiten
+oder ihr LaTeX-Dokument vorher entsprechend anpassen.
+Konvertierungsprogramme, die aus (La)TeX-Dokumenten ein anderes Format
+erzeugen, existieren fr RTF (Word/WordPerfect), gewhnlichen
+ASCII-Text, HTML, Portable Document Format (PDF) von Adobe u.v.m..
+
+11.3.3 Konvertierungsprogramme fr MS Word (for Windows), WordPerfect
+(for Windows), allgemein fr `Rich Text Format' (RTF) sowie fr weitere
+Formate?
+
+LaTeX zwingt den Autor, sein Dokument in strukturierter Form einzugeben,
+whrend Textverarbeitungsprogramme wie Word und WordPerfect auch die
+unstrukturierte Eingabe eines Dokuments erlauben, was leider auch die
+meisten Autoren tun. Daher ist es nur sehr schwer und mit viel Aufwand
+mglich, ein unstrukturiertes Dokument automatisch in eine strukturierte
+LaTeX-Eingabe umzusetzen. Fr die Textverarbeitungsprogramme existieren
+jedoch auch sogenannte Dokumentvorlagen. Werden vom Autor eines
+Dokuments die zustzlichen Strukturierungsmglichkeiten einer solchen
+Dokumentvorlage `sauber' und konsistent verwendet, ist eine automatische
+Umsetzung in eine klar strukturierte LaTeX-Eingabedatei ber einen
+`internen' Konverter (z.B. durch Makros des Textverarbeitungsprogrammes)
+mglich.
+Eine bersicht ber eine Vielzahl von Konvertierungsprogrammen zwischen
+(La)TeX-Dokumenten und RTF-/Word/WP-Dokumenten hat Wilfried Hennings in
+seiner FAQ unter
+ http://www.tug.org/utilities/texconv/
+verffentlicht, die man auch unter
+ CTAN: help/wp-conv/
+finden kann. Im folgenden sind diese Programme daher nur knapp
+aufgezhlt.
+
+ RTF/Word/WordPerfect => LaTeX (nichtkommerziell):
+
+ * RTF (Word/WordPerfect) => LaTeX:
+
+ o rtf2TeX CTAN: support/rtf2tex/
+ o rtf2LaTeX http://members.home.net/setlur/rtf2latex2e/,
+ CTAN: support/rtf2latex/
+ o rtfLaTeX CTAN: support/rtflatex/
+ o w2latex CTAN: support/w2latex/
+ o wvLaTeX http://wvware.sourceforge.net/
+ o GNU UnRTF http://www.geocities.com/tuorfa/unrtf.html
+
+ * WinWord 2.0 und 6.0 => LaTeX:
+
+ o WINW2LTX CTAN: support/winw2ltx/ (Dokumentvorlagen, interner
+ Konverter!)
+
+ * WordPerfect => LaTeX:
+
+ o WP2LaTeX CTAN: support/wp2latex/
+ o TeXPerfect CTAN: support/texperf/
+ o WP2x
+
+ * Word => LaTeX:
+
+ o word_tex CTAN: support/word_tex/ (Dokumentvorlagen, interner
+ Konverter!)
+ o WORD2TeX http://www.word2tex.com/, CTAN: support/word2tex/
+ o WD2LaTeX
+ o CATDOC CTAN: support/catdoc/
+ o Word2x CTAN: tools/word2x
+ o W2T http://www.fi.muni.cz/~nygryn/w2t/
+
+ * Word => HTML:
+
+ o wvHtml http://wvware.sourceforge.net/
+ o GNU UnRTF http://www.geocities.com/tuorfa/unrtf.html
+
+ * Word => Text/PostScript:
+
+ o AntiWord http://www.winfield.demon.nl/index.html
+ o wvText http://wvware.sourceforge.net/
+
+
+
+ RTF/Word/WordPerfect => LaTeX (kommerziell):
+
+ * Word/WordPerfect => (La)TeX:
+
+ o ``Publishing Companion'' von K-Talk Communications Inc.
+ URL: http://www.ktalk.com
+
+ * RTF => LaTeX:
+
+ o Scientific Word/Scientific WorkPlace (enthlt RTF inkl. math
+ => LaTeX) von TCI Software Research
+
+ * Math => Plain-TeX:
+
+ o MathType Formeleditor von Design Science
+ URL: http://www.mathtype.com/mathtype/
+
+
+
+ Excel-Tabellen => LaTeX (nichtkommerziell):
+
+ * Excel2Latex
+ http://www.jam-software.com/software.html
+ CTAN: support/excel2latex
+ * xl2Latex
+ CTAN: support/xl2latex/
+ * Tabular
+ http://www.hsh.no/~ag/tabular/ (nicht mehr erreichbar)
+
+
+ LaTeX => RTF/Word/WordPerfect (nichtkommerziell):
+
+ * LaTeX => RTF, Windows Help RTF, HTML, wxHelp
+
+ o TeX2RTF 1.47 CTAN: support/tex2rtf/
+ URL: ftp://ftp.aiai.ed.ac.uk/pub/packages/tex2rtf/
+ http://web.ukonline.co.uk/julian.smart/tex2rtf/
+
+ * LaTeX => RTF
+
+ o latex2rtf
+ CTAN: support/latex2rtf/
+
+
+
+ LaTeX => RTF/Word/WordPerfect (kommerziell):
+
+ * TeX/LaTeX => WordPerfect/Word
+
+ o TexPort
+ URL: http://www.ktalk.com
+ o tex2doc
+ URL:
+ http://webplanet.lion.cc/jupiter/320094/software/Tex2doc.html
+
+
+
+ LaTeX => Framemaker (nicht kommerziell):
+
+ Framemaker => LaTeX (nicht kommerziell):
+ URL: http://www.cs.stir.ac.uk/~kjt/software/framemaker/
+
+
+11.3.4 Konvertierungsprogramme zwischen HTML und LaTeX?
+
+Eine bersicht ber eine Vielzahl von Konvertierungsprogrammen zwischen
+(La)TeX- und HTML-Dokumenten hat Gnter Partosch in seiner Liste
+```Gleichzeitiges' Publizieren in HTML und LaTeX'' unter
+http://www.uni-giessen.de/~g029/TeX/converters.html verffentlicht.
+
+11.3.5 Konvertierungsprogramme von (La)TeX in einfaches Textformat?
+
+Da das Ergebnis eines TeX-Laufs ein druckreifes Dokument darstellt, bei
+dem ein geflliges Aussehen durch unterschiedliche Schriftarten und
+-kodierungen u.a. ereicht wird, ist die Reduktion auf das einfache
+Textformat nicht so einfach, wie man vielleicht glaubt. Die folgenden
+Wege fhren zu einem Endergebnis, welches mehr oder weniger die zugrunde
+liegende Formatierung erahnen lt:
+
+* `dvi2tty'
+ Ein dvi-Treiber, der das Ergebnis auf alphanumerischen Terminals
+ darstellen oder in eine Datei ausgeben kann.
+* `catdvi'
+ Ein dvi-Treiber, der wie `dvi2tty' Text liefert. Baut auf der
+ kpathsea-Bibliothek von Web2C auf und luft damit nur auf
+ Betriebssystemen, auf denen diese existiert.
+* `ps2ascii'
+ Bestandteil des Programmpaketes `Ghostscript'. Erfordert die vorherige
+ Wandlung der dvi-Datei nach PostScript.
+* `pstotext'
+ Benutzt ebenfalls Ghostscript zur Wandlung, wobei bessere Ergebnisse
+ als mit `ps2ascii' erzielt werden.
+* `pdftotext'
+ Bestandteil des Programmpaketes `Xpdf'. Erfordert die vorherige
+ Erzeugung einer pdf-Datei. Es werden recht gute Ergebnisse erzielt.
+* LaTeX => HTML => txt
+ Vorherige Wandlung der LaTeX-Datei nach HTML (siehe Frage 11.3.4). Die
+ Wandlung vom HTML- in das Textformat kann mit Hilfe eines Web-Browsers
+ (z.B. `lynx') oder mit anderen speziellen Konvertierungsprogrammen
+ geschehen.
+ Fr die DE-TeX-FAQ wird `html2text' zur Wandlung von HTML- in
+ Textdateien verwendet. Diese Programm liegt im Quellcode vor und die
+ Formatierung der verschiedenen HTML-Konstrukte lt sich durch eine
+ Style-Konfigurationsdatei anpassen. Fr DOS existiert mit `htmstrip'
+ ein hnliches Programm.
+
+
+dvi2tty: CTAN: nonfree/dviware/dvi2tty/
+catdvi: http://www.iki.fi/gaia/programs/catdvi/
+ps2ascii: CTAN: support/ghostscript/
+pstotext: http://www.research.digital.com/SRC/virtualpaper/
+pdftotext: CTAN: support/xpdf/
+pdftotext/Xpdf: http://www.foolabs.com/xpdf/
+html2text: http://userpage.fu-berlin.de/~mbayer/tools/html2text.html
+ ftp://ftp.ibiblio.org/pub/linux/apps/www/converters/
+htmstrip: http://www.erols.com/waynesof/
+
+
+
+11.3.6 Wie kann ich Excel-Diagramme, Powerpoint-Zeichnungen oder andere
+Windows-Bilder mit LaTeX verwenden? (*)
+
+Adobe stellt fr Windows PostScript-Druckertreiber zur Verfgung. Damit
+hat man die Mglichkeit, ein Dokument als EPS abzuspeichern, auch wenn
+das Windows-Programm keinen EPS-Export vorsieht. Frage 6.4.1 fhrt aus,
+wie man EPS-Bilder in LaTeX-Dokumente einbindet. Sollten die wie oben
+angegeben erzeugten EPS-Bilder fehlerhafte Abmessungen aufweisen, so
+kann der Tip in Frage 6.4.6 helfen. Weitere Informationen zum
+Drucker-Treiber fr Windows 95/98 und NT/2000/XP, sowie zu den
+Einstellungen des Drucker-Treibers ber eine PPD-Datei, gibt es auf dem
+Adobe-Web-Server.
+Es empfiehlt sich, zusammen mit dem PostScript-Druckertreiber auch die
+Adobe PPD-Dateien herunterzuladen. Diese enthalten eine Acrobat
+Distiller PPD-Datei, die fr die Erstellung von EPS-Dateien optimiert
+ist, welche nicht direkt auf einem bestimmten Drucker ausgegeben werden
+sollen, sondern zur Weiterverarbeitung (einschlielich PDF-Erstellung)
+gedacht sind.
+
+Printer Drivers for http://www.adobe.com/support/downloads/pdrvwin.htm
+Windows:
+Erstellen von
+EPS-Grafiken unter CTAN: info/german/grafik/eps_anleitung.html
+Windows:
+
+
+
+11.4 TeX-Benutzungsoberflchen und Editoren (*)
+
+
+11.4.1 Emacs: Wie kann ich erreichen, da fr deutsche Texte das
+Doublequote nicht durch `` bzw.'' ersetzt wird?
+
+In vielen, wenn auch nicht allen Fllen erkennt AucTeX, eine
+empfehlenswerte Erweiterung des Emacs-TeX-Mode, durch die Verwendung des
+Pakets `german' in der Dokumentprambel, da dieses Verhalten
+ausgeschaltet werden soll. Falls nicht, kann man zwei Doublequotes
+eingeben, um einen einzelnen Doublequote zu erhalten.
+Einfacher ist es, wenn man dieses Verhalten abschaltet oder ndert.
+Beispielsweise in dem man in die Startup-Datei ``.emacs'' die Zeilen
+
+ (add-hook 'TeX-mode-hook
+ (function (lambda ()
+ ;;
+ ;; 1. besondere Behandlung fuer dt. Texte (u.a. fuer ")
+ (TeX-run-style-hooks "german") ;; nur AucTeX
+ ;;
+ ;; 2. gesonderte Behandlung von " ganz abschalten
+ ; (local-set-key "\"" 'self-insert-command)
+ ;;
+ ;; 3. je ein " statt ``...'' einfuegen:
+ ; (setq TeX-open-quote "\"")
+ ; (setq TeX-close-quote "\"")
+ ;;
+ ;; 4. "`..."' statt ``...'' einfuegen:
+ ; (setq TeX-open-quote "\"`")
+ ; (setq TeX-close-quote "\"'")
+ )))
+
+einfgt und je nach Wunsch eine der vier Varianten auskommentiert lt.
+Ab AucTeX v9.x kann man auch in der Datei ``.emacs'' einfach
+
+ (setq TeX-quote-after-quote t)
+
+schreiben, um dieses Verhalten abzuschalten.
+Achtung: Fr den TeX-Mode der Standard-Emacs-Verteilung mu der Teil
+`TeX-' in den Symbolen als `tex-' kleingeschrieben werden. Einige
+Erweiterungen funktionieren nur mit AucTeX.
+
+11.4.2 Emacs: Ich will direkt Umlaute verwenden knnen, jedoch sollten
+diese in `\"a' oder `"a' umgewandelt werden, damit ich sie problemlos
+weitergeben kann.
+
+Die Emacs-Library-Datei `iso-cvt' wandelt automatisch beim Laden und
+Speichern eines Textes die Umlaute von bzw. in die entsprechenden TeX-
+bzw. German-Style-Makro-Notation. Folgendes Code-Schnipsel funktioniert
+nur mit AucTeX und einer neueren Version der Library-Datei `iso-cvt'.
+
+ (require 'iso-cvt)
+ (add-hook 'LaTeX-mode-hook
+ (function (lambda ()
+ ;; Setze Anfuehrungszeichen etc. fuer Style german
+ (TeX-run-style-hooks "german")
+ ;;
+ ;; Lade Buffer und wandle nach ISO Latin-1:
+ (format-encode-buffer 'plain)
+ ;; Speichere Buffer in "gtex" = german.sty-Notation ("a etc.):
+ (format-decode-buffer 'gtex))))
+
+Will man das entgegengesetzte Verhalten, soll also Emacs bei Eingabe
+eines Umlauts statt des einzelnen Umlautzeichens direkt die aus mehreren
+Zeichen bestehende TeX-Makro-Notation erzeugen, so kann man dies durch
+nderung der entsprechenden `Key-Map' erreichen. Beispielsweise durch
+folgenden unvollstndig gezeigten Code:
+
+ (add-hook 'TeX-mode-hook
+ (function (lambda ()
+ (local-set-key [228]
+ (function (lambda () (interactive)
+ (insert "\"a")
+ ;; oder
+ ; (insert "\\\"a")
+ )))
+ ;; weitere Zuweisungen mit analogem Aufbau
+ ;; fuer die anderen Umlaute und das scharfe s
+ )))
+
+Wenn man dies verwendet, wre es noch ratsam, mit etwas zustzlichem
+Emacs-Lisp-Code beim Lschen eines so erzeugten `Umlautes' nicht nur ein
+Zeichen, sondern alle Zeichen des kompletten Makros zu entfernen.
+Achtung: Fr den TeX-Mode der Standard-Emacs-Verteilung mu statt des
+Symbols `TeX-mode-hook' das kleingeschriebene Symbol `tex-mode-hook'
+verwendet werden. Einige Erweiterungen funktionieren nur mit AucTeX.
+
+11.4.3 Emacs: Wie kann ich Symbole leichter eingeben oder anschaulicher
+bei der Eingabe darstellen? (*)
+
+Das Paket x-symbol zeigt unter XEmacs oder Emacs 21 sehr viele Symbole
+in einer Semi-WYSIWYG-Darstellung. Zustzlich erweitert es die Mens, so
+dass man in diesen nach Symbolen suchen kann.
+
+x-symbol: http://x-symbol.sourceforge.net
+
+
+
+11.5 dvi-Treiber - Druckertreiber und Previewer
+
+
+11.5.1 Wieso zeigt Xdvi das polnische L oder fr \sqrt[n]{2} das `n'
+nicht an, obwohl es beim Ausdruck auf einem Drucker korrekt vorhanden
+ist?
+
+Xdvi sollte in diesem Fall die Warnung ``Note: overstrike characters may
+be incorrect.'' ausgeben. Bei Zeichen, die aus mehreren, bereinander
+gesetzten Einzelzeichen erzeugt werden, lscht Xdvi zur schnelleren
+Ausgabe Teile des bzw. der darunterliegenden Einzelzeichen. In den
+Manual-Seiten zu Xdvi findet man dazu mehr im Abschnitt zu den Optionen
+`-thorough/-copy'. (Nicht vergessen: Xdvi ist nur ein Previewer fr
+niedrigstauflsende Ausgabegerte mit ca. 90-100dpi!)
+Mit `xdvi +copy file.dvi' (oder mit `-thorough -nogrey') sollte man das
+`n' in obiger Wurzel erhalten, ohne diese Optionen erscheint nur die
+Wurzel. Die gleiche Wirkung erreicht man mit dem Eintrag `XDvi*thorough:
+true' in der Datei `XDvi' (X-Resource-Datei). Diese Datei befindet sich
+bei der teTeX-Distribution im Verzeichnis ``.../texmf/xdvi/'' bzw. sonst
+in ``.../lib/X11/app-defaults/''.
+
+11.5.2 Benutze ich Ghostscript 4.0 zur Anzeige von PostScript-Grafiken
+in Xdvi erhalte ich den Fehler `/undefinedfilename in --file--'.
+Abhilfe?
+
+Dies ist ein inzwischen gut bekannter Fehler. Die momentan einfachste
+Abhilfe besteht darin, mindestens Version 4.03 oder neuer zu benutzen.
+Ist dies nicht mglich, kann man in der Zwischenzeit an die
+Ghostscript-Datei `gs_init.ps' die Zeile
+
+ $error /newerror false put
+
+anhngen. In kurzer Zeit drfte auch eine neue xdvi-Version erscheinen
+(bzw. ist schon erschienen), die diesen Fehler beseitigt.
+
+11.5.3 Wieso weisen Satzbelichter meine mit `dvips' oder den `psutils'
+erzeugten PostScript-Dateien mit der Meldung zurck, da diese kein
+korrektes PostScript konform zu DSC 3.0 wren?
+
+Kommentare in einer PostScript-Datei sollen den Konventionen fr
+`Structured Comments', den sogenannten `Document Structuring
+Conventions' (DSC), gengen. ltere Versionen von `dvips' und den
+Programmen `pstops', `psbook', `psselect' etc. der PostScript-Utilities
+erzeugen jedoch beispielsweise einen nicht ganz korrekten Kommentar fr
+`%%Pages:'. Hier darf nur _eine_ einzige Zahl folgen, die die Seitenzahl
+angibt. ltere Versionen von `dvips' und der PostScript-Utilities geben
+jedoch noch eine zweite Zahl aus, so da Software, die den `Document
+Structuring Conventions' Version 3.0 strikt folgt, solche
+PostScript-Dateien, die mit
+
+ %!PS-Adobe-3.0
+
+beginnen, als fehlerhaft zurckweist.
+
+11.5.4 Wie kann ich mein Dokument so nach PostScript wandeln, da alle
+Seiten gespiegelt erzeugt werden?
+
+Durch die Option -h kann man mit `dvips' noch zustzlichen
+PostScript-Code in einer sogenannten Header-Datei hinzuladen. Zum
+Spiegeln smtlicher Seiten existiert die Header-Datei ``mirr.hd'', die
+man durch
+
+ dvips -h mirr.hd document.dvi
+
+hinzuladen kann. Eine weitere in grerem Mae treiberunabhngige
+Mglichkeit, da auf den Paketen `graphics' und `color' basierend, bietet
+das LaTeX-Paket `crop'. Neben der Spiegelung von Seiten mit der
+Paketoption `mirror' knnen diese mit der Option `invert' auch
+invertiert, also wei auf schwarz, ausgegeben werden.
+
+mirr.hd: CTAN: macros/generic/TeX-PS/mirr.hd
+crop: CTAN: macros/latex/contrib/crop/
+
+
+
+11.5.5 Was kann ich tun, wenn mein Drucker Teile meines Dokuments, die
+sich weit am unteren Blattrand befinden, nicht druckt?
+
+Zuerst ist zu prfen, ob mglicherweise ein falsches Papierformat
+eingestellt ist. Der Druck vom Ergebnis des folgenden LaTeX-Aufrufs
+
+ latex testpage
+
+ist ein guter Test, um falsche Druckereinstellungen herauszufinden.
+Fllt dieser Test zufriedenstellend aus, kann versucht werden, das
+Problem dadurch zu lsen, da die betreffenden Seiten kopfstehend an den
+Drucker geschickt werden. Mit den beiden folgenden Verfahren kann man
+kopfstehende Seiten unter Verwendung von PostScript erzeugen.
+
+ pstops "U(210mm,297mm)" original.ps kopfstehend.ps
+
+oder im LaTeX-Dokument
+
+ \usepackage[rotate]{crop}[2000/02/02]
+
+
+pstops: CTAN: support/psutils
+crop: CTAN: macros/latex/contrib/crop/
+
+
+
+11.6 Zeichenprogramme
+
+
+11.6.1 Wie bringe ich `XFig' dazu, beim Exportieren von Graphiken nach
+(La)TeX Formeln nicht auszukommentieren, sondern so zu bernehmen?
+
+ber das Men `Text Flags' (ab `XFig' Version 3) mu man fr diese Texte
+das sogenannte Special-Flag setzen, damit diese ohne jede nderung in
+die (La)TeX-Datei exportiert werden. Dies kann man bei schon
+gezeichneten Textobjekten auch nachtrglich ber den Menpunkt `Edit'
+ndern.
+Das Special-Flag kann man auch beim Aufruf von `XFig' ber die Option
+`-spec[ialtext]' oder ber die X11-Resource `Fig*specialtext' setzen.
+Dies bewirkt, da fr _neue_ Textobjekte standardmig das Special-Flag
+gesetzt wird.
+
+11.6.2 Warum funktioniert das DOS-Programm `TeXCad' nicht mehr auf
+meinem neuen Rechner?
+
+Es kann an einem Fehler in der Unit CRT des zum Kompilieren verwendeten
+`Borland Pascal 7' liegen, der sich bei schnellen Prozessoren im Abbruch
+mit der Fehlermeldung
+
+ Runtime error 200 at XXX:YYYY
+
+uert. Nhere Informationen dazu und Wege zur Abhilfe finden sich unter
+dem Stichwort ``tppatch''.
+
+tppatch: http://www.brain.uni-freiburg.de/~klaus/pascal/runerr200/download.html
+ ftp://ftp.heise.de/ct/ctsi/bppatch.zip
+ ftp://ftp.heise.de/ct/ctsi/ctbppat.zip
+
+
+
+--- DE-TeX-FAQ Ende Teil 11 ---
diff --git a/help/de-tex-faq/part2 b/help/de-tex-faq/part2
new file mode 100644
index 0000000000..35b4f7489c
--- /dev/null
+++ b/help/de-tex-faq/part2
@@ -0,0 +1,758 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.rediris.es!newsmi-us.news.garr.it!NewsITBone-GARR!news.mailgate.org!newsfeed.icl.net!newsfeed.fjserv.net!proxad.net!newsfeed.stueberl.de!news-mue1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 2 of 11)
+Supersedes: <de-tex-faq-2-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:15 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 729
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-2-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975395 886 134.100.9.52 (19 Sep 2003 12:43:15 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:15 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117400 de.answers:9377 news.answers:258266
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part2
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 2 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+2 Anwendervereinigungen, Tagungen, Literatur
+
+
+2.1 DANTE e.V.
+
+
+2.1.1 Was ist DANTE e.V.?
+
+DANTE e.V. steht fr Deutschsprachige Anwendervereinigung TeX. Dies ist
+der Zusammenschlu von deutschsprachigen TeX-Anwendern, TeXies,
+TeXnikern und sonstigen TeX-Arbeitern in einer Gemeinschaft. Der Verein
+wurde am 14. April 1989 in Heidelberg gegrndet, ist in das
+Vereinsregister eingetragen (e.V.) und vom Finanzamt als gemeinntzig
+anerkannt worden.
+
+2.1.2 Wie erreiche ich DANTE e.V.?
+
+
+Post: DANTE, Deutschsprachige Anwendervereingung TeX e.V.
+ Postfach 101840
+ 69008 Heidelberg
+ Telefon: (06221) 29766
+ Fax: (06221) 167906
+E-Mail: `dante@dante.de'
+
+Am einfachsten geht es via E-Mail, da sich unter der angegebenen
+Telefonnummer in den meisten Fllen ein Anrufbeantworter meldet.
+
+2.1.3 Welchen Zweck hat DANTE e.V.?
+
+Dazu sagt die Satzung:
+Zweck des Vereins ist es, alle Interessenten in geeigneter Weise bei der
+Anwendung von TeX-Software zu untersttzen, insbesondere durch
+Erfahrungsaustausch mit den Anwendern. Ferner soll die weitere
+Entwicklung von TeX untersttzt werden. Hierzu gehren
+
+ 1. die Beratung und Zusammenarbeit mit Anwendern der TeX-Software,
+ 2. die Unterbreitung von Mitgliedervorschlgen fr zuknftige
+ Versionen und Komponenten der TeX-Software,
+ 3. die Zusammenarbeit mit anderen nationalen und internationalen
+ Benutzerorganisationen,
+ 4. die Frderung von Literatur, die TeX betrifft,
+ 5. die Vertretung nationaler Belange in der TeX Users Group,
+ 6. die Organisation von Schulungen.
+
+
+2.1.4 Wieso sollte ich Mitglied bei DANTE e.V. werden?
+
+Natrlich wird niemand gezwungen, bei DANTE e.V. Mitglied zu werden. Es
+sollte aber bedacht werden, da die Dienstleistungen von DANTE e.V. nur
+erbracht werden knnen, weil es Leute gibt, die DANTE e.V. untersttzen.
+Neben diesem eher ideellen Grund hat eine Mitgliedschaft bei DANTE e.V.
+auch sehr reelle Grnde:
+
+* Informationen aus erster Hand durch
+
+ o die viermal im Jahr erscheinende Mitgliedszeitschrift ``Die
+ TeXnische Komdie'',
+ o _elektronische_ Medien in Form von E-Mail-Diskussionslisten wie
+ TeX-D-L, die archiviert ber WWW-, FTP-Server oder die
+ Software-Verteilung bezogen werden knnen,
+ o den WWW-Server von DANTE e.V., erreichbar ber http://www.dante.de/.
+
+* Bezug von Software, wie kompletten TeX-Systemen fr Ihr Rechnersystem,
+ von Makropaketen und Schriften ber
+
+ o das CTAN (Comprehensive TeX Archive Network), an dessen Aufbau und
+ Verwaltung Mitglieder von DANTE e.V. mageblich beteiligt waren und
+ sind und dessen deutscher Knoten von DANTE e.V. finanziert wird,
+ o eine Software-Verteilung auf CD-ROM, darunter der CD-ROM-Satz mit
+ einer Kopie des CTAN-Servers und der CD ,,TeX Live'', die man im
+ Rahmen einer Mitgliedschaft zustzlich bekommt.
+
+* Beratung und Schulung, wie beispielsweise
+
+ o Tutorien im Rahmen der halbjhrlich stattfindenden
+ Mitgliederversammlung bzw. Tagung,
+ o Beraterkreis fr TeXnische Fragen,
+ o Kurse fr Anfnger und Fortgeschrittene (auf Anfrage).
+
+* Kontaktmglichkeiten ber
+
+ o nationale und internationale Tagungen,
+ o TeX-Tagungen und Mitgliederversammlungen (halbjhrlich),
+ o regionale Stammtische (monatlich).
+
+* usw.
+
+Einige dieser Leistungen knnen auch von Nicht-Mitgliedern genutzt
+werden. In der Regel stehen sie jedoch nur Mitgliedern im vollen Umfang
+zur Verfgung!
+
+2.1.5 Wie werde ich Mitglied?
+
+Mitglied bei DANTE e.V. zu werden, ist einfach: Mitgliedsantrag
+ausfllen und unterschrieben an
+ DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+ Postfach 101840
+ D-69008 Heidelberg
+schicken. Den Mitgliedsbeitrag sollten Sie auf das auf dem Antrag
+angegebene Konto berweisen. Bitte keine andere DANTE e.V. gehrende
+Kontonummer verwenden, dies wrde die Bearbeitung verzgern! Nach dem
+Eingang Ihres Antrags und des Mitgliedsbeitrags erhalten Sie eine
+Besttigung Ihrer Mitgliedschaft, eine Vereinssatzung und, soweit
+vorrtig, die bisher verschickten Ausgaben der Mitgliedszeitschrift des
+Jahrgangs mit weitereb Zusatzleistungen (CD-ROM etc.) und weitere
+Informationen.
+Einen Mitgliedsantrag erhalten Sie
+
+* als PDF- oder als PostScript-Datei per
+ http://www.dante.de/dante/antrag/, per CTAN: usergrps/dante/antrag.pdf
+ bzw. CTAN: usergrps/dante/antrag.ps oder
+* per Post: Fordern Sie ber die oben genannte Adresse der
+ Geschftsstelle ein Antragsformular an.
+
+Der Mitgliedsbeitrag gilt fr das laufende Kalenderjahr (1.1.-31.12.)
+und betrgt
+
+* Einzelbeitrag fr Privatpersonen: 45 Euro
+* Ermigter Einzelbeitrag fr Schler/innen, Studierende,
+ Rentner/innen, Arbeitslose, Zivil- und Wehrdienstleistende
+ (entsprechende Bescheinigung notwendig!): 30 Euro
+* fr Institutionen des ffentlichen Rechts und Forschungseinrichtungen:
+ 65 Euro
+* fr Firmen, die TeX anwenden: 150 Euro
+* fr Firmen, die Produkte in Verbindung mit TeX anbieten: 250 Euro
+
+
+2.1.6 Ich habe den Mitgliedsantrag vor zwei bis drei Wochen abgeschickt,
+den Beitrag gleich danach auf das Konto berwiesen und bisher noch
+nichts erhalten. Ist diese Wartezeit normal?
+
+Nein, ein Mitgliedsantrag wird normalerweise zgig bearbeitet, sobald
+der Antrag per Post im Bro von DANTE e.V. eintrifft und berprft
+werden konnte, da der Mitgliedsbeitrag auf dem angegebenen Konto
+eingegangen ist. Bei einer ermigten Mitgliedschaft ist darauf zu
+achten, da die entsprechenden Bescheinigungen fr das jeweilige
+Kalenderjahr beigelegt wurden. Vor und nach Feiertagen und zu den
+blichen Urlaubszeiten sollte man jedoch bitte etwas geduldiger sein, da
+das Bro whrend dieser Zeiten unbesetzt sein kann.
+
+2.2 Anwendervereinigungen
+
+
+2.2.1 Gibt es weitere TeX-Anwendervereinigungen?
+
+Neben DANTE e.V. gibt es noch weitere TeX-Anwendervereinigungen. Als
+erstes ist hier die TUG zu nennen, die internationale `TeX Users Group'.
+Sie ist die erste und damit die lteste TeX-Anwendervereinigung.
+ TeX Users Group
+ 1466 NW Front Avenue
+ Suite 3141
+ Portland, OR 97209-2820, USA
+ Tel.: +1 503 223-9994
+ Fax: +1 503 223-3960
+ E-Mail: `tug@mail.tug.org'
+Weitere Informationen ber die TUG finden Sie auf CTAN im Verzeichnis
+CTAN: usergrps/tug/ oder dem WWW-Server http://www.tug.org/.
+Neben TUG und DANTE e.V. gibt es weitere nationale
+Anwendervereinigungen. Als Auswahl seien folgende Vereine genannt:
+
+ NTG Nederlandstalige TeX Gebruikersgroep (Niederlande)
+ GUST Grupa Uzytkownikw Systemu TeX (Polen)
+ GUTenberg Groupe francophone des Utilisateurs de TeX
+ (franzsischsprachige Lnder)
+ CsTUG Ceskoslovensk sdruzen uzivatelu TeXu
+ (Tschechische/Slowakische Republik)
+ UK TUG UK TeX Users' Group (Grobritannien)
+
+ber einige dieser nationalen Anwendervereinigungen knnen Sie weitere
+Informationen, Antragsformulare, Ankndigungen u.. auf CTAN in den
+Verzeichnissen CTAN: usergrps/ finden.
+Auerdem finden Sie ber die Seite http://www.dante.de/ weitere
+Informationen zu DANTE e.V., TUG, Verweise zu den WWW-Seiten der anderen
+TeX-Anwendervereinigungen, einen Tagungs- und Veranstaltungskalender und
+vieles mehr.
+
+2.2.2 Mitgliedszeitschriften der Anwendervereinigungen
+
+Jede der ``groen'' TeX-Anwendervereinigungen gibt eine
+Mitgliedszeitschrift und Vereinsnachrichten heraus:
+
+* ``Die TeXnische Komdie''
+ Mitgliedszeitschrift von DANTE e.V., erscheint vierteljhrlich,
+ deutsch.
+* TUGboat
+ Mitgliedszeitschrift der TUG, erscheint vierteljhrlich (ein Band ist
+ Konferenzband der TUG-Konferenz), englisch, enthlt viele informative
+ Artikel ber TeX, METAFONT und Fonts.
+* TeX and TUG News (TTN) - Erscheinen eingestellt.
+ Ehemalig separat herausgegebene Vereinsnachrichten der TUG, erschien
+ vierteljhrlich, englisch, enthlt aktuellere Informationen ber
+ Vereinsinterna, Tips, Berichte etc.; nach Ausgabe Vol. 4 No. 2 ist TTN
+ in TUGboat integriert.
+* MAPS (Minutes and APendiceS)
+ Mitgliedszeitschrift der NTG, erscheint halbjhrlich, niederlndisch
+ und englisch, enthlt hufig Vorabdrucke und Nachdrucke aus anderen
+ Mitgliedszeitschriften, wie TUGboat, Baskerville etc.
+* Baskerville
+ Mitgliedszeitschrift der UK TUG, erscheint 4-6mal jhrlich (eine
+ Ausgabe ist die UK TUG TeX FAQ), englisch, enthlt einige Nachdrucke
+ aus anderen Zeitschriften und Proceedings.
+* Cahiers GUTenberg
+ Verffentlichung von GUTenberg, erscheint 2-3mal jhrlich,
+ franzsisch; die Cahiers sind nicht im Mitgliedsbeitrag enthalten,
+ sondern knnen und mssen extra abonniert werden.
+* Lettre GUTenberg
+ Vereinsnachrichten von GUTenberg, erscheint 2-3mal jhrlich,
+ franzsisch.
+
+
+2.3 Tagungen (*)
+
+
+2.3.1 Veranstaltungen
+
+Die TeX-Anwendervereinigungen fhren regelmig Tagungen, Tutorien,
+Mitgliederversammlungen etc. durch:
+
+* DANTE e.V.
+ Jhrliche Tagung, Mitgliederversammlung und Tutorien (3 bis 3 1/2
+ Tage) im Frhjahr; meist im Februar oder Mrz.
+ Jhrliche Mitgliederversammlung mit Tutorien (1 bis 1 1/2 Tage) im
+ Herbst; meist im September oder Oktober.
+* Europische Anwendervereinigungen
+ Jhrliche europische Tagung; meist im September; entfllt im
+ allgemeinen in den Jahren, in denen die TUG in Europa eine Tagung
+ ausrichtet.
+* TUG
+ Jhrliche weltweite Tagung; meist Ende Juli, Anfang August; im Wechsel
+ an einem Ort der Westkste der USA, der Ostkste und in Europa.
+
+Auch Personen, die noch nicht Mitglied bei einer Anwendervereinigung
+sind, knnen an den Tagungen teilnehmen.
+Tutorien, die DANTE e.V. vor oder nach einer Mitgliederversammlung
+durchfhrt, sind frei und knnen kostenlos besucht werden.
+
+2.3.2 Veranstaltungskalender (*)
+
+Im folgenden finden Sie eine Auswahl der in nchster Zeit stattfindenden
+Tagungen im TeX-Umfeld. Die WWW-Seite
+ http://www.dante.de/events/
+enthlt genauere Hinweise und Informationen.
+
+03.-05.03.2004: DANTE 2004 - ``15 Jahre DANTE e.V.''
+ 30. Mitgliederversammlung von DANTE e.V.
+ Universitt Darmstadt
+01.-03.05.2004(?) BachoTeX 2004
+ Bachotek, nahe Brodnica, Polen
+30.08.-01.09.2004: TUG 2004 - 25th annual meeting of TUG
+ Xanthi, Griechenland
+Herbst 2004 31. Mitgliederversammlung von DANTE e.V.
+
+
+2.4 Literatur (*)
+
+
+2.4.1 Bcherliste (*)
+
+Es wird hier nur eine kleine Auswahl von hauptschlich deutschsprachigen
+Bchern vorgestellt, die weder den Anspruch erhebt, vollstndig noch
+objektiv zu sein.
+
+* Detig, Christine: Der LaTeX Wegweiser.
+ MITP-Verlag, 1997, ISBN 3-8266-0256-0, 29,80 DM
+ Anm.: Leicht verstndliche Einfhrung in LaTeX mit den wichtigsten
+ LaTeX-Erweiterungspaketen und Hilfswerkzeugen, fr Anfnger. _Die
+ Auflage ist vergriffen, Restexemplare sind in modernen Antiquariaten
+ noch erhltlich._
+* Knappen, Jrg: Schnell ans Ziel mit LaTeX2e.
+ Oldenbourg-Verlag, 1997, ISBN 3-486-24199-0, 48,-- DM
+ Anm.: Enthlt Kapitel ber Feinheiten des Text- und Formelsatzes sowie
+ einen Index vom Formelsymbol bis zu Befehlsnamen, fr Anfnger und
+ Fortgeschrittene.
+* Knuth, Donald E.: The TeXbook (englisch).
+ Addison-Wesley, Reading, Massachusetts, 1996, ISBN 0-201-13447-0, ISBN
+ 0-201-13448-9 (Softcover)
+ Anm.: _Das_ Standardwerk ber TeX, nicht fr LaTeX-Anfnger, da es TeX
+ und dessen Programmierung sehr genau beschreibt.
+* Lamport, Leslie: Das LaTeX-Handbuch.
+ Addison-Wesley-Verlag, 1995, ISBN 3-89319-826-1, 69,90 DM
+ Anm.: _Die_ LaTeX-Referenz, fr Anfnger.
+* Goossens, Michel u.a.: Der LaTeX-Begleiter.
+ Addison-Wesley-Verlag, Nachdruck 2000, ISBN 3-82731-689-8, 79,90 DM
+ Anm.: Die Auflage des Jahres 2000 mit neuer ISBN entspricht der aus
+ dem Jahre 1995. Tips, Tricks, viele LaTeX-Makropakete, fr
+ Fortgeschrittene und fortgeschrittene Anfnger, aufgrund des
+ Titelbildes das sog. `Bernhardiner-Buch'; Kapitel 8 der englischen
+ Fassung ``Higher Mathematics'' liegt in einer berarbeiteten Fassung
+ auf CTAN: info/companion-rev/ch8.ps bzw.
+ CTAN: info/companion-rev/ch8.pdf vor.
+* Goossens, Michel; Rahtz, Sebastian; Mittelbach, Frank: The LaTeX
+ Graphics Companion (englisch).
+ Addison-Wesley-Longman-Verlag, 1997, ISBN 0-201-85469-4
+ Anm.: Ergnzt den LaTeX-Begleiter um alles, was mit Graphikeinbindung,
+ Farbe und PostScript-Schriften zu tun hat.
+* Goossens, Michel; Rahtz, Sebastian et al.: The LaTeX Web Companion:
+ Integrating TeX, HTML und XML (englisch).
+ Addison-Wesley-Longman-Verlag, 1999, ISBN 0-201-43311-7, ca. 68,-- DM
+ Anm.: Enthlt eine Beschreibung von pdfTeX mit `hyperref', die
+ Konverter LaTeX2HTML und TeX4ht, das Browser-Plugin techexplorer und
+ eine grere Abhandlung ber die Markup-Sprachen HTML, SGML, XML und
+ deren zugehrige Style-Sheet-Sprachen.
+* Goossens, Michel; Rahtz, Sebastian: Mit LaTeX ins Web: Elektronisches
+ Publizieren mit TeX, HTML und XML.
+ Addison-Wesley-Longman-Verlag, 2000, ISBN 3-8273-1629-4, 89,90,-- DM
+ Anm.: Deutsche bersetzung von ``The LaTeX Web Companion''.
+* Klckl, Ingo: LaTeX2e, Tips und Tricks.
+ dpunkt-Verlag, Heidelberg, 2000, ISBN 3-932588-37-1, 79,-- DM
+ http://www.dpunkt.de/buecher/3-932588-37-1.html
+ Anm.: Das Buch fllt die Lcke zwischen den existierenden
+ LaTeX-Einfhrungen bzw. -Referenzen und `Der LaTeX-Begleiter', wenn
+ man wissen will, wie man selbst Anpassungen durchfhrt. Ein Kapitel
+ besteht aus der bersicht fast aller auf CTAN vorhandener Schriften.
+* Gnther, Karsten: LaTeX Ge-Packt.
+ MITP-Verlag, 2002, ISBN 3-8266-0785-6, 14,94 Euro
+ Anm.: Umfangreiche Referenz fr LaTeX2e im Kompaktformat, vorwiegend
+ fr Anwender mit Vorkenntnissen, enthlt auch Hinweise auf ntzliche
+ TeX-Befehle und KOMA-Script.
+* Dalheimer, Matthias Kalle: LaTeX kurz und gut.
+ O'Reilly, Kln, 1. Auflage, 1998, ISBN 3-89721-204-8, 12,80 DM
+ Anm.: Eine Kurzreferenz auf 64 Seiten, gut strukturiert mit allen
+ hufig bentigten LaTeX-Anweisungen, als Ergnzung zu ausfhrlicherer
+ Literatur gut geeignet.
+* Abdelhamid, Rames: Das Vieweg LaTeX2e Buch.
+ Vieweg-Verlag Wiesbaden, 1995, ISBN 3-528-25145-X, 52,-- DM
+ Anm.: Fr Anfnger.
+* Gnther, Karsten: Einfhrung in LaTeX2e - Lehrbuch und Referenz.
+ dpunkt-Verlag, Heidelberg, 1996, ISBN 3-920993-36-5, 68,-- DM
+* Katzenbeisser, Stefan: Von der Idee zum Dokument - Einfhrung in TeX
+ und LaTeX.
+ Oldenbourg-Verlag, 2. Auflage, 1997, ISBN 3-486-24182-6, 68,-- DM
+* Maurer: Textverarbeitung mit LaTeX2e unter Unix.
+ Carl Hanser Verlag, Mnchen, ISBN 3-446-18909-2, 49,80 DM
+* Schwarz, Stefan; Potucek, Rudolf: Das TeXikon - Referenzhandbuch fr
+ TeX, LaTeX und LaTeX2e.
+ Addison-Wesley-Verlag, 1997, ISBN 3-89319-690-0, 69,90 DM
+* Heilmann, Axel: LaTeX-Vademecum, Ein Kompaktfhrer fr Einsteiger und
+ Fortgeschrittene.
+ Springer-Verlag, ISBN 3-540-60522-3, 38,-- DM
+ Anm.: Kleines und praktisches Nachschlagewerk, kann und will nicht den
+ LaTeX-Begleiter ersetzen, ist aber eine gute Ergnzung.
+* Sowa, Friedhelm: TeX/LaTeX und Graphik, ein berblick ber die
+ Verfahren.
+ Springer-Verlag, 1994, ISBN 3-540-56468-3, 39,-- DM
+ Anm.: Der `Nothelfer', wenn es um TeX und Graphik geht.
+* Schwarz, Norbert: Einfhrung in TeX incl. Version 3.0.
+ Addison-Wesley-Verlag, 3. berarbeitete Auflage, Nachdruck 1993, ISBN
+ 3-89319-345-6, 69,-- DM
+ Anm.: TeX und Plain-TeX, kein LaTeX(!), fr Fortgeschrittene.
+* Kopka, Helmut: LaTeX, Band 1: Einfhrung.
+ Addison-Wesley-Verlag, 2. Auflage, 2000, ISBN 3-8273-1557-3, 79,90 DM
+ Anm.: Ab der 2. Auflage auch LaTeX2e, im Anhang gute Befehlsbersicht,
+ fr Anfnger.
+* Kopka, Helmut: LaTeX, Band 2: Ergnzungen.
+ Addison-Wesley-Verlag, 2. berarbeitete Auflage, 1997, ISBN
+ 3-8273-1229-9, 69,90 DM
+ Anm.: Name sagt alles, die 1. Auflage enthielt noch
+ LaTeX2e-Einfhrung.
+* Kopka, Helmut: LaTeX, Band 3: Erweiterungen.
+ Addison-Wesley-Verlag, 1996, ISBN 3-89319-666-8, 69,90 DM
+ Anm.: Interna von LaTeX2e und 2.09 sowie Low-Level-TeX-Befehle.
+* Kopka, Helmut und Daly, Patrick W.: A Guide to LaTeX2e (englisch).
+ Addison-Wesley-Verlag, 2. Aufl., 1995, ISBN 0-201-42777-X, ca. ??? DM
+ Anm.: Englische bersetzung des ``Kopka'' mit vielen berarbeitungen
+ und Anpassungen fr englischsprachige Benutzer.
+* Grtzer, George: An Introduction to LaTeX and AmS-LaTeX (englisch).
+ Birkhuser-Verlag, Boston, 1996, 2nd Printing, 1997, ISBN
+ 0-8176-3805-9, $58,50
+ Anm.: Ausfhrliche Darstellung von AmS-LaTeX und AmS-Fonts, dadurch
+ auch fr anspruchsvollen Formelsatz.
+
+Hinweise: Als LaTeX-Anfnger sollte man sich ein ausfhrliches Lehrbuch
+(z.B. `Detig', `Abdelhamid', `Knappen', `Lamport', `Kopka'/Band 1,
+`Kopka/Daly') besorgen. Frei verfgbare Literatur, wie die
+LaTeX2e-Kurzbeschreibung (siehe Frage 2.4.2), reicht Anfngern mit
+Computer-Vorkenntnissen eventuell auch aus. Sobald man als
+LaTeX-Anwender die ersten Schritte gemacht hat, sind der
+`LaTeX-Begleiter' und der `LaTeX Graphics Companion' eine wahre
+Fundgrube. Mu oder will man sein eigenes TeX-System selbst installieren
+und verwalten, gibt der wenn auch mittlerweile veraltete `Walsh' eine
+gute Erklrung und bersicht der einzelnen Teile des Textsatzsystems TeX
+und darber hinaus viele Hinweise und eine Auswahl, was es sonst noch an
+Umgebungen, Hilfsprogrammen, Schriften etc. gibt.
+Das Standardwerk fr TeX-Anfnger und alle Makroautoren ist Knuths `The
+TeXbook', das man sich auch zulegen sollte, wenn man zuerst mit Hilfe
+des in Deutsch geschriebenen `Schwarz (N.)' einsteigen will.
+
+2.4.2 Frei verfgbare Einfhrungen in (La)TeX, METAFONT und verwandte
+Themen (*)
+
+Diese Dokumente sind von den Autoren als (La)TeX-Eingabedateien auf CTAN
+zur freien Verfgung gestellt worden. Sie finden diese und weitere
+Dokumente meist im Verzeichnis CTAN: info/. Folgende Liste stellt eine
+kleine Auswahl dar:
+
+* Schmidt, Walter; Knappen, Jrg; Partl, Hubert et al.:
+ LaTeX2e-Kurzbeschreibung
+ CTAN: info/lshort/german/
+ Anm.: Zum Einstieg in LaTeX vllig ausreichend, fr Anfnger.
+* Oetiker, Tobias: The Not So Short Introduction to LaTeX2e
+ CTAN: info/lshort/english/
+ Anm.: Basierte auf der LaTeX-Kurzbeschreibung, etwas ausfhrlicher. In
+ englischer Sprache, bersetzt in weitere Sprachen.
+* Eijkhout, Victor: TeX by Topic, A TeXnician's reference.
+ Electronic version 1.0, Dezember 2001
+ http://www.cs.utk.edu/~eijkhout/texbytopic.pdf
+ Anm.: Eine gegenber dem TeXbook andere Herangehensweise, wie man TeX,
+ dessen primitiven Anweisungen und Parameter und die inneren Ablufe
+ erklrt. Empfehlenswert.
+* Schwarz, Norbert: Einfhrung in TeX.
+ http://www.ruhr-uni-bochum.de/www-rz/schwanbs/TeX/
+ Anm.: PDF-Version der gedruckten 3. Auflage von 1991.
+* Abrahams, Paul W.,; Hargreaves, Kathryn A.; Berry, Karl: TeX for the
+ impatient.
+ Free (GFDL) edition version 1.0, 2001 (Original: Addison-Wesley, 1990)
+
+ CTAN: info/impatient/
+ Anm.: Buch ber TeX und Plain-TeX, nicht LaTeX.
+* Walsh, Norman: Making TeX Work.
+ Free version, 2002 (Original: O'Reilly&Associates Inc., 1994, ISBN
+ 1-56592-051-1)
+ CTAN: info/makingtexwork/
+ Anm.: Gute Einfhrung und bersicht; Fundgrube fr Tools, Makropakete,
+ Schriften; teilweise mit genauerer Beschreibung.
+* Greenberg, Harvey J.: A Simplified Introduction to LaTeX
+ http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html
+ CTAN: info/simplified-latex/simplified-intro.ps
+ Anm.: Ausfhrliche Einfhrung in LaTeX zu Textsatz, Mathematiksatz,
+ Grafikeinbindung, BibTeX und vielen anderen Themen. In englischer
+ Sprache.
+* Partl, Hubert; Kielhorn, Axel: Layout-nderungen mit LaTeX
+ CTAN: macros/latex/contrib/refman/
+ Anm.: Wie verndere ich X? Anhand von Beispielen aus `refman.sty'.
+* Schrod, Joachim: The Components of TeX (englisch)
+ CTAN: info/components-of-TeX/
+ Anm.: bersicht ber die Teile und der von diesen Teilen angefaten
+ Dateien eines TeX-Systems; fr LaTeX 2.09 geschrieben, aber immer noch
+ fr LaTeX2e ntzlich.
+* Warbrick, Jon: Essential LateX (englisch)
+ CTAN: info/latex-essential/
+ Anm.: LaTeX 2.09, ganz kurz gefat.
+* Doob, Michael: A Gentle Introduction to TeX (englisch)
+ CTAN: info/gentle/
+ Anm.: Kurzbeschreibung von TeX, nicht LaTeX!
+* Tobin, Geoffrey: METAFONT for Beginners (englisch)
+ CTAN: info/metafont-for-beginners.tex
+ Anm.: Enthlt das Wichtigste, um mit METAFONT aus vorhandenen
+ mf-Sources Fonts zur Nutzung mit TeX zu generieren.
+* Reckdahl, Keith: Using Imported Graphics in LaTeX2e (englisch)
+ CTAN: info/epslatex.ps
+ CTAN: info/epslatex.pdf
+ Anm.: Was Sie schon immer ber die Einbindung von
+ Encapsulated-PostScript-(EPS)-Bildern, BoundingBox, die Benutzung des
+ `graphics'-Pakets und weiterer LaTeX-Umgebungen und -Pakete wie
+ `PSfrag' wissen wollten.
+* Jrgens, Manuela: LaTeX - eine Einfhrung und ein bichen mehr ...
+ Fern-Uni Hagen, 2000
+ ftp://ftp.fernuni-hagen.de/pub/pdf/urz-broschueren/broschueren/a0260003.pdf
+
+ Anm.: Einstiegsbroschre in LaTeX.
+* Jrgens, Manuela: LaTeX - Fortgeschrittene Anwendungen (oder: Neues
+ von den Hobbits)
+ Fern-Uni Hagen, 1995
+ ftp://ftp.fernuni-hagen.de/pub/pdf/urz-broschueren/broschueren/a0279510.pdf
+
+ Anm.: Ergnzungen zur Einstiegsbroschre.
+* Jrgens, Manuela: Verschlungene Anwendungen. Das X-Team: Xtem XEmacs
+ LaTeX2eAucTeX
+ Fern-Uni Hagen, 1995
+ ftp://ftp.fernuni-hagen.de/pub/pdf/urz-broschueren/broschueren/a0029502.pdf
+* Banning, Ralf; Groeneveld, Heiko A.: Textsatz und Layout mit LaTeX.
+ Eberhard-Karls-Universitt Tbingen, Zentrum fr Datenverarbeitung,
+ 1995
+ http://www.uni-tuebingen.de/zdv/schriften/latex-kurs.html
+ Anm.: Sehr ausfhrliche Hinweise zum Einstieg in LaTeX.
+* Lamprecht, Heiner: LaTeX2e - Eine Einfhrung. 1999.
+ http://agenda21.ggi.uni-tuebingen.de/heiner/latex/
+* Text Processing using LaTeX (englisch)
+ http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/
+ Anm.: Sehr ausfhrliche Beschreibungen und Verweise zu LaTeX und
+ verwandten Themen.
+* Computersatz mit LaTeX2e. Kurzeinfhrung.
+ Katholische Universitt Eichsttt, 1996
+ http://www.ku-eichstaett.de/urz/schriften/ltx2e.pdf
+* Makeindex. Sachregister erstellen mit LaTeX2e.
+ Katholische Universitt Eichsttt, 1998
+ http://www.ku-eichstaett.de/urz/schriften/makeidx.pdf
+* Banning, Ralf; Groeneveld, Heiko A.: Textsatz und Layout mit LaTeX.
+ Eberhard-Karls-Universitt Tbingen, Zentrum fr Datenverarbeitung.
+ http://www.uni-tuebingen.de/zdv/schriften/latex-kurs.html
+* Gonzato, Guido: LaTeX for Word Processor Users. 2001.
+ CTAN: info/latex4wp/latex4wp.pdf
+* Flynn, Peter: Beginner's LaTeX. 2001.
+ http://www.silmaril.ie/downloads/documents/beginlatex.pdf
+* Vo, Herbert: Mathmode. 2003.
+ http://www.perce.de/LaTeX/math/Mathmode-TeX.pdf
+ Anm.: Eine Einfhrung in den Mathematiksatz unter Bercksichtigung von
+ AmS-LaTeX.
+
+Neben diesen Dokumenten, die noch zum Druck gedacht sind, gibt es
+vermehrt auch nicht zum Druck gedachte `Online-Quellen':
+
+* Hypertext Help with LaTeX
+
+ o http://www.giss.nasa.gov/latex/
+ o http://www-ti.informatik.uni-tuebingen.de/~frech/latex/
+
+* LaTeX2e Help
+
+ o CTAN: info/latex2e-help-texinfo/latex2e.html
+ o http://xm1.net.free.fr/kile/latexhelp.html
+
+* David Bausum: TeX Primitive Control Sequences
+
+ o http://www.tug.org/utilities/plain/cseq.html
+
+* Literaturverzeichnis zu TeX & Co.
+
+ o http://www.loria.fr/services/tex/english/texbib.html
+
+* Online tutorials on LaTeX (Indian TeX Users Group)
+
+ o http://www.tug.org.in/tutorial/tutorials.html
+
+* bersicht zu vielen TeX- und verwandten Themen (``Open Directory
+ Project'').
+
+ o http://dmoz.org/Computers/Software/Typesetting/
+
+* Links2Go - TeX and LaTeX
+
+ o http://www.links2go.com/topic/TeX_and_LaTeX
+
+* WebRing: TeX word processor system users and friends
+
+ o http://nav.webring.yahoo.com/hub?ring=texlatex&list
+
+* Tim Love: LaTeX maths and graphics
+
+ o http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/latex_maths+pix/latex_maths+pix.html
+
+* Tim Love: Advanced LaTeX
+
+ o http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/latex_advanced/latex_advanced.html
+
+* Ado Haarer, Grit Segner: MakeIndex - ein Indexprozessor fr LaTeX
+
+ o http://www.lrz-muenchen.de/services/software/textverarbeitung/makeindex/
+
+
+
+2.4.3 Typographie
+
+
+Bcher:
+
+
+* Tschichold, Jan: Erfreuliche Drucksachen durch gute Typographie: eine
+ Fibel fr jedermann.
+ Maro-Verlag, Augsburg, 2. Auflage 1992, ISBN 3-87512-403-0, 32,-- DM
+ Anm.: allgemeiner berblick, Elementarkenntnisse.
+* Tschichold, Jan: Ausgewhlte Aufstze ber Fragen der Gestalt des
+ Buches und der Typographie.
+ Birkhuser-Verlag, Basel, 2. Auflage 1987, ISBN 3-7643-1946-1,
+ 39,80 DM
+ Anm.: Eines der wichtigsten Bcher ber typographische Prinzipien beim
+ Buchsatz, Sammlung von Tschicholds `klassischen' Artikel.
+* Tschichold, Jan: Die neue Typographie.
+ Brinkmann und Bose, 3. Auflage 1995, ISBN 3-922660-23-1, 80,-- DM
+* Aicher, Otl: Typographie.
+ Ernst-Verlag, Ldenscheid, 1988, ISBN 3-433-03090-6
+* Spiekermann, Erik: Ursache & Wirkung: ein typografischer Roman.
+ Verlag H. Schmidt, Mainz, faksimilierter Nachdruck, 1994, ISBN
+ 3-87439-307-0, 38,-- DM
+* Simoneit, Manfred: Typographisches Gestalten.
+ Polygraph-Verlag, Frankfurt/M., 4. Auflage, 1993, ISBN 3-87641-253-6,
+ 256 S., 144,-- DM
+* Luidl, Philipp: Typografie.
+ Schltersche Verlagsanstalt, 6. Auflage, 1989, ISBN 3-87706-290-3, 146
+ S., 79,-- DM
+* Weidemann, Kurt: Wo der Buchstabe das Wort fhrt.
+ Cantz-Verlag, Ostfildern, 2. Auflage, 1997, ISBN 3-89322-521-8,
+ 168,-- DM
+ Anm.: _Sehr empfehlenswert_. Grundstzliches ber das Thema.
+* Willberg, Hans Peter; Forssman, Friedrich: Erste Hilfe in Typographie:
+ Ratgeber fr Gestaltung mit Schrift.
+ Verlag H. Schmidt, Mainz, 1999, ISBN 3-87439-474-3, 24,80 DM
+ Anm.: _Sehr empfehlenswert_ und preiswert ist dieses Buch und sollte
+ daher als Erstausstattung nicht fehlen, da knapp und praktisch erste
+ Hilfe in Typographie gegeben wird.
+* Willberg, Hans Peter; Forssman, Friedrich: Lesetypographie.
+ Verlag H. Schmidt, Mainz, 1997, ISBN 3-87439-375-5, 168,-- DM
+ Anm.: Handbuch, das Anregungen geben will, Lsungsmglichkeiten fr
+ typographische Probleme vergleichend vorstellt; eher fr jemand, der
+ schon Grundkenntnisse hat.
+* Gulbins, Jrgen; Kahrmann, Christine: Mut zur Typographie: Ein Kurs
+ fr Desktop-Publishing.
+ Springer-Verlag, 2. , erweiterte und berarbeitete Auflage, 2000, ISBN
+ 3-540-67541-8, 79,-- DM
+ Anm.: Fr Anfnger sehr gut geeignet, auch als Nachschlagewerk.
+* Bringhurst, Robert: The Elements of Typographic Style.
+ Hartley & Marks, 2. Auflage, 1996, ISBN 0-88179-132-6, ??? DM
+ Anm.: _Sehr empfehlenswert_, sagt kurz und knapp das Wesentliche und
+ weist auf viele Fehler hin.
+* Peter Rechenberg: Technisches Schreiben.
+ Hanser Verlag, 1. Auflage, 2002, ISBN 3-446-21944-7, 19,90 DM
+
+
+Sonstiges:
+
+
+* Charles Poynton: Typography and Design.
+ http://www.inforamp.net/~poynton/Poynton-typo-design.html
+ Anm.: Verweise und Hinweise zu Fragen der Typografie (in englischer
+ Sprache).
+* Luc Devroye: General links on typography.
+ http://cgm.cs.mcgill.ca/~luc/fonts.html
+ Anm.: Eine Vielzahl von Verweisen zu Typografie und Schriften. (meist
+ in englischer Sprache).
+* Markus Kuhn: Metric Typographic Units.
+ http://www.cl.cam.ac.uk/~mgk25/metric-typo.html
+ Anm.: Erklrungen zu typographischen Maeinheiten (in englischer
+ Sprache).
+* Charles Hedrick, New Brunswick Computing Services, Rutgers, The State
+ University of New Jersey.
+ http://www.nbcs.rutgers.edu/~hedrick/typography/
+ Anm.: 30-seitige (englische) Einfhrung in gute Typografie. PDF-Datei
+ in den Schriften Aldus, Minion, Janson, Warnock, Documenta und bald
+ auch Palatino, Adobe Garamond und ITC New Baskerville erhltlich. Auch
+ ein Werkzeug zur Konvertierung von OpenType-Schriften in
+ Expert-Type-1-Schriften ist dort fr Windows frei erhltlich.
+* Axel Reichert: Typografie - Gestaltung einer Beispielklasse.
+ CTAN: info/german/typografie/
+ Anm.: Ausgehend von Grundlagen der Typografie wird an einer
+ Beispielklasse deren Umsetzung gezeigt. Tutorium auf der Tagung
+ DANTE'99.
+* Axel Reichert: Satz von Tabellen.
+ CTAN: info/german/tabsatz/
+ Anm.: Anhand vieler Beispiele und der Verwendung von Zusatzpaketen
+ werden viele Feinheiten beim Satz von Tabellen erlutert. Tutorium auf
+ der Tagung DANTE'99.
+* Psychologie, Uni Regensburg: Textsatz, eine Kurzanleitung.
+ http://pc1521.psychologie.uni-regensburg.de/student2001/Textsatz.html
+ Anm.: Ein paar grundstzliche Dinge und Warnungen.
+* Marion Neubauer: Mikrotypographie-Regeln.
+ http://www.dante.de/dante/DTK/dtk96_4/dtk96_4_neubauer_feinheiten.html
+ http://www.dante.de/dante/DTK/dtk97_1/dtk97_1_neubauer_feinheiten.html
+* Yannis Haralambous: Drucksatz in gebrochenen Schriften.
+ http://genepi.louis-jean.com/omega/dante2000.pdf
+* FAQ: Typografie & Co
+ http://www.spic.de/webtypo/faq-typografie.html (nicht mehr erreichbar)
+ Anm.: (Noch) mit Vorsicht zu genieen, enthlt aber einige brauchbare
+ Dinge und Links.
+* EUR-OP: Interinstitutionelle Regeln fr Verffentlichungen.
+ Amt fr amtliche Verffentlichungen der Europischen Gemeinschaften,
+ Luxembourg.
+ http://eur-op.eu.int/code/de/de-000500.htm
+ Anm.: Enthlt Richtlinien zum Schriftsatz und fr deutschsprachige
+ Verffentlichungen in der EU.
+
+
+2.4.4 Schriftenkataloge
+
+
+* Sauthoff, Daniel u.a.: Schriften erkennen: eine Typologie der
+ Satzschriften fr Studenten, Grafiker, Setzer, Kunsterzieher und alle
+ PC-User.
+ Verlag H. Schmidt, Mainz, Neuausgabe, 1996, ISBN 3-87439-373-9,
+ 24,80 DM
+ Anm.: Grundlage, Geschichte und einfacher Einstieg in die
+ Klassifikation von Schriften, fr Einsteiger.
+* Dinkel, Christina: Fchen in Brunos Suppe: ``Schriften erkennen'' fr
+ Kinder.
+ Verlag H. Schmidt, Mainz, 1999. ISBN 3-87439-479-4, 24,80 DM
+ Anm.: Eine spielerische, nicht nur fr Kinder geeignete Einfhrung in
+ die Welt der Schriften anhand einer Geschichte.
+* Kern, Michael; Koch, Sieghart (Hrsg.): berSicht.
+ Verlag H. Schmidt, Mainz, 1991, ISBN 3-87439-230-9, 429 S., 148,-- DM
+ Anm.: 3 Indizes: Blindtextprobe, Zeichenvorrat der Schriften,
+ Buchstabenverzeichnis (alle ``M'' auf einen Blick).
+
+
+2.4.5 Ich hab im Buch ``Der LaTeX-Begleiter'' bzw. ``The LaTeX
+Companion'' ein interessantes Paket gefunden. Wo kann ich es auf CTAN
+finden?
+
+Die Datei ``companion.ctan'' zhlt alle im Buch erwhnten Pakete auf.
+
+companion.ctan: CTAN: info/companion.ctan
+
+
+
+2.4.6 Mich interessiert, wie einige der Grafik-Beispiele im Buch ``The
+LaTeX Graphics Companion'' erzeugt wurden. Wo kann ich deren Quelltext
+herbekommen?
+
+Die Mehrzahl der Beispiele sind auf CTAN im Verzeichnis CTAN: info/lgc
+zu finden. Die Beispiele des Kapitels zu `PSTricks'sind auch Bestandteil
+dessen Dokumentation.
+
+lgc: CTAN: info/lgc
+PSTricks: CTAN: graphics/pstricks/doc/test-pst.tex
+
+
+
+--- DE-TeX-FAQ Ende Teil 2 ---
diff --git a/help/de-tex-faq/part3 b/help/de-tex-faq/part3
new file mode 100644
index 0000000000..cd88f0ba7d
--- /dev/null
+++ b/help/de-tex-faq/part3
@@ -0,0 +1,886 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.rediris.es!irazu.switch.ch!switch.ch!news-fra1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 3 of 11)
+Supersedes: <de-tex-faq-3-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:15 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 857
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-3-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975396 887 134.100.9.52 (19 Sep 2003 12:43:16 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:16 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117402 de.answers:9379 news.answers:258268
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part3
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 3 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+3 Textsatzsystem TeX - bersicht
+
+
+3.1 Grundlegendes
+
+
+3.1.1 Was ist TeX?
+
+TeX ist ein Textsatzsystem, das von Prof. Dr. Donald E. Knuth entwickelt
+wurde.
+Der Unterschied zu einer Textverarbeitung ist, da hier Text nicht nur
+verarbeitet, sondern auch gesetzt wird. Dies wird beispielsweise durch
+das tiefergestellte E in dem Logo von TeX symbolisiert. Diese
+Mglichkeit wird in dem vorliegenden Text durch das
+kleingeschriebene `e' angedeutet. Auerdem dient die Schreibweise TeX
+zur Unterscheidung von TEX.
+Aussprache: TeX wird nicht so ausgesprochen, wie es geschrieben wird!
+Aufgrund der griechischen Wurzel `tau epsilon chi' spricht man das `X'
+in TeX wie ein ch- oder k-Laut, niemals wie ein `x'. Man spricht: `tech'
+wie in Technik.
+Persnliche Informationen ber Donald E. Knuth, ber seine Plne und
+wichtige Hinweise fr die Benutzer von TeX und Leser seiner Bcher kann
+man auf Knuths WWW-Seite
+ http://www-cs-faculty.stanford.edu/~knuth/
+finden.
+
+3.1.2 Was ist METAFONT?
+
+METAFONT ist wie TeX von Prof. Dr. Donald E. Knuth entwickelt worden. Es
+erlaubt die Beschreibung einer Schrift oder einer Schriftfamilie durch
+ein Programm, den sogenannten Meta-Font. Aus diesem Meta-Font kann
+METAFONT nach Wahl verschiedener Parameter Schriften generieren, die TeX
+verwenden kann.
+Um mit TeX zu arbeiten, ist METAFONT nicht zwingend erforderlich. Es ist
+auch mglich, beispielsweise mit PostScript-Schriften zu arbeiten. TeX
+bentigt von einer Schrift nur die Mae der einzelnen Zeichen und
+weitere schriftabhngige Parameter, wie beispielsweise die Breite eines
+Wortzwischenraumes. Diese Informationen entnimmt TeX einer
+TeX-Font-Metric-(tfm)-Datei.
+METAPOSTist ein aus METAFONT abgeleitetes Programm zum Erstellen von
+PostScript-Zeichnungen (siehe Frage 9.1.4).
+
+3.1.3 Worin besteht der Unterschied zwischen IniTeX und VirTeX bzw.
+zwischen IniMF und VirMF? Was ist eine sogenannte Format-, was eine
+Base-Datei?
+
+IniTeX und VirTeX sind beides Varianten des Programmes TeX, wobei IniTeX
+Code fr zustzliche Initialisierungsroutinen und erweiterte
+Datenstrukturen enthlt, um beispielsweise Trennmusterdateien zu laden
+und in kompakter Form wieder abzuspeichern oder eine Formatdatei zu
+erzeugen. IniTeX wird dazu verwendet, die TeX-internen Datenstrukturen
+zu initialisieren - daher der Name -, grere Makropakete wie LaTeX,
+Schriftdateien und Trennmuster zu laden und in einer kompakten, schnell
+wieder ladbaren Form, in der sogenannten Formatdatei, abzuspeichern.
+Formatdateien haben die Dateinamensendung `.fmt' und den Vorgang, eine
+Formatdatei mit IniTeX zu erzeugen, nennt man auch `ein Format dumpen'.
+Die zustzlichen Routinen und Datenstrukturen sind beim normalen
+Gebrauch von TeX nicht notwendig, so da diese in der VirTeX-Variante
+nicht vorhanden sind. Dadurch kann man in VirTeX, dem `virgin' oder
+jungfrulichem TeX, Speicherplatz sparen oder diesen fr andere Zwecke
+einzusetzen. VirTeX wird in den meisten TeX-Implementierungen unter dem
+Namen `tex' aufgerufen, IniTeX entweder als ``initex'' oder ber eine
+spezielle Kommandozeilenoption wie ``tex -i'' oder ``tex -ini''.
+Analog zu IniTeX und VirTeX gibt es auch von METAFONT zwei
+Programmvarianten namens IniMF und VirMF. Statt Formatdatei heit die
+von IniMF erzeugte Datei Basedatei und besitzt die Dateinamensendung
+`.base' (oder `.bas').
+Der Aufbau der Format- und Basedateien ist nicht standardisiert! Er ist
+sowohl von der Implementierung, von der TeX- und MF-Version als auch fr
+dieselbe TeX- und MF-Version von verschiedenen Compile-Zeit-Parametern
+abhngig. Diese Dateien sollen von TeX bzw. MF mglichst schnell geladen
+werden knnen, so da Implementierer hier betriebssystem- und
+implementierungsabhngige Optimierungen vornehmen knnen.
+
+3.1.4 Was ist eine dvi-Datei, was ist ein dvi-Treiber, was ist der
+DVI-Treiberstandard?
+
+TeX erzeugt als wichtigste Ausgabe eine dvi-Datei. Das Akronym `dvi'
+steht fr `DeVice-Independent', d.h. der interpretierte Inhalt dieser
+Datei kann auf fast jedem mglichen Ausgabegert ausgegeben werden. Ein
+dvi-Treiber, ein spezielles Programm, liest eine dvi-Datei und wandelt
+die in ihr enthaltenen Informationen in Steuerinformationen fr einen
+speziellen Drucker (z.B. in PostScript oder in PCL) oder zur Anzeige am
+Bildschirm fr ein spezielles Fenstersystem (wie X11) oder
+Bildschirmtreiber.
+Besonders hervorzuheben ist an TeX, da _jede_ TeX-Implementierung fr
+dieselbe Eingabe (also Dokument, verwendete Makros, Schriften,
+Trennmuster etc.) _unabhngig_ vom Ausgabegert und dessen Auflsung
+_immer_ dieselbe dvi-Datei erzeugt. TeX whlt also immer denselben
+Absatz- und Seitenumbruch und dieselbe Plazierung von Zeichen, Linien
+usw. auf der Seite.
+dvi-Dateien enthalten alle Informationen, die zum Ausdruck oder zur
+Anzeige der erzeugten Seiten notwendig sind. Jedoch sind in einer
+dvi-Datei nicht die tatschlichen Lettern der verwendeten Schriften und
+das mit \special-Anweisungen eingebunde Material, wie Grafiken,
+enthalten. Diese mssen vom dvi-Treiber aus anderen Quellen, wie z.B.
+pk-Dateien bei Schriften, gelesen und an das Ausgabegert geschickt
+werden. dvi-Dateien verwenden die TeX-interne Zeichenkodierung. So liegt
+beispielsweise der Argumenttext einer \special-Anweisung in der
+dvi-Datei als eine in ASCII kodierte Zeichenkette vor.
+Die dokumentierte Source des Programms `dvitype' dient gleichzeitig als
+Referenzbeschreibung des dvi-Formats. Eine bessere, weil mit den
+Mindestanforderungen an einen dvi-Treiber versehene Referenz ist der
+ DVI-Treiberstandard, Level 0
+den man in CTAN: dviware/driv-standard/level-0/ finden kann. In diesem
+Standard findet man im Anhang neben einer Kopie der dvi-Beschreibung aus
+`dvitype' noch die entsprechenden Beschreibungen des tfm-, gf- und
+pk-Formates. Weitere Papiere, Berichte, Vorschlge etc. findet man in
+CTAN: dviware/driv-standard/papers/.
+Als ein Projekt der NTG-Future-Group (siehe Diskussionsliste 1.3.4)
+laufen unter dem Titel ``DVI3 a new DVI standard'' Arbeiten zur
+Vervollkommnung und Weiterentwicklung des DVI-Standards. Nhere
+Informationen findet man unter http://dvi3.tiepmiep.dk/ und
+http://userpage.fu-berlin.de/~burnus/dviview/.
+
+3.1.5 Wozu dienen Dateien mit der Namensendung `.xyz'?
+
+Die einzelnen Programme und TeX-Formate des Textsatzsystems TeX
+verwenden sehr viele Dateien mit unterschiedlichen Namensendungen. Damit
+auch ein Anfnger relativ schnell einen berblick erhlt, folgt hier
+eine Auflistung der hufigsten bzw. wichtigsten Dateinamensendungen,
+sortiert nach Programmen, TeX-Formaten und weitverbreiteten
+Implementierungen.
+
+ (Plain-)TeX:
+
+
+ .tex
+ Standarddateinamensendung fr alle Arten von
+ TeX-Eingabedateien, einige Makropakete wie LaTeX verwenden
+ andere Namensendungen, um zwischen Dokument- und den
+ notwendigen Makrodefinitionsdateien zu unterscheiden
+
+ .fmt
+ TeX-Formatdatei (siehe Frage 3.1.3)
+
+ .dvi
+ TeX-Ausgabedatei, enthlt formatiertes Dokument (siehe Frage
+ 3.1.4)
+
+ .pool, .poo
+ `String-Pool'-Datei, wird von IniTeX oder IniMF bentigt.
+
+ .log
+ Protokolldatei eines TeX- oder MF-Laufs.
+
+ .lis
+ Protokolldatei eines TeX- oder MF-Laufs unter dem
+ Betriebssystem OpenVMS.
+
+
+ METAFONT, Fonts und Tools:
+
+
+ .mf
+ MF-Eingabedatei
+
+ .base
+
+ .bas
+ MF-Formatdatei (siehe Frage 3.1.3)
+
+ .tfm
+ MF-Ausgabe: TeX Font Metric (siehe Frage 9.1.2)
+
+ .*gf
+ MF-Ausgabe: `generic font' (siehe Frage 9.1.2)
+
+ .*pk
+ `packed raster' (siehe Frage 9.1.2)
+
+ .*pxl
+ `pixel' (siehe Frage 9.1.2): veraltetes, durch
+ `.*pk'-Dateien abgelstes Font-Bitmap-Format
+
+ .pl
+ `property list', lesbare Darstellung der in einer tfm-Datei
+ enthaltenen Informationen
+
+ .vf
+ `virtual font' (siehe Frage 9.1.3)
+
+ .vpl
+ `virtual font property list' (siehe Frage 9.1.3)
+
+
+ METAPOST:
+
+
+ .mp
+ METAPOST-Eingabedatei
+
+ .mem
+ METAPOST-Formatdatei (analog zu .fmt bzw. .base)
+
+ .mps
+ METAPOST-Ausgabedatei; eine eps-Datei, die aufgrund ihrer
+ bekannten und einfachen Struktur mit Hilfe von TeX-Makros in
+ das pdf-Format wandelbar ist.
+
+ .mpx
+ METAPOST-Eingabedatei, entstanden durch Aufruf von
+ `DVItoMP'.
+
+
+ Omega:
+
+
+ .otp
+ `Omega translation process', definiert Umkodierungsfilter
+
+ .ocp
+ `Omega compiled process', compilierte Version einer
+ .otp-Datei
+
+ .ofm
+ `Omega TeX font metric', erweiterte Version des .tfm-Formats
+ fr Omega
+
+ .opl
+ `Omega property list', lesbare Darstellung einer .ofm-Datei
+
+ .ovf
+ `Omega virtual font', erweiterte Version des .vf-Formats
+
+ .ovp
+ `Omega virtual font property list', lesbare Darstellung
+ einer .ovf-Datei
+
+
+ BibTeX:
+
+ .bst
+ BibTeX-Style, enthlt Anweisungen an BibTeX, wie die
+ Literaturangaben aus der .bib-Datei in die .bbl-Datei
+ geschrieben werden sollen
+
+ .bib
+ BibTeX-Datenbank
+
+ .blg
+ Protokolldatei eines BibTeX-Laufs
+
+ .bbl
+ BibTeX-Ausgabe, meist in einer Form, die von LaTeX
+ eingelesen werden kann
+
+
+ MakeIndex:
+
+
+ .ist
+ MakeIndex-Style, enthlt Anweisungen, wie aus den Eintrgen
+ in der .idx/.glo-Datei die .ind/.gls-Datei generiert werden
+ soll
+
+ .idx
+ Index-Datei, enthlt die unsortierten Indexeintrge
+
+ .ind
+ MakeIndex-Ausgabe: fertig erstellter Index
+
+ .glo
+ Glossar-Datei, enthlt analog zur .idx-Datei die
+ unsortierten Glossareintrge
+
+ .gls
+ MakeIndex-Ausgabe: fertig erstelltes
+ Wrterverzeichnis/Glossar
+
+ .ilg
+ Protokolldatei eines MakeIndex-Laufs
+
+
+ Texinfo (TeX-Format):
+
+
+ .texi
+
+ .texinfo
+
+ .txi
+ GNU-Texinfo-Dokumentquelldatei
+
+
+ docstrip-Archive (nicht nur fr LaTeX-Makropakete verwendbar):
+
+
+ .dtx
+ docstrip-Archivdatei (siehe Frage 5.1.3), kann mit dem in
+ TeX geschriebenem Programm `docstrip' entpackt werden.
+ (docstrip: CTAN: macros/latex/base/docstrip.dtx und
+ CTAN: macros/latex/base/docstrip.ins)
+ Historisch: Diese Archive hatten anfnglich die Namensendung
+ .doc
+
+ .ins
+ Instruktionsdatei zum Entpacken eines docstrip-Archivs
+ (siehe Frage 5.1.3); zum Entpacken reicht der Aufruf ``tex
+ filename.ins'', manchmal auch ``latex filename.ins'';
+ nheres bitte der mitgelieferten Dokumentation entnehmen!
+
+ .drv
+ `Treiber'-Datei, fr einige .dtx-Dateien zur Formatierung
+ der Dokumentation mit LaTeX verwendet
+
+ .fdd
+ docstrip-Archiv der LaTeX-.fd-Dateien
+
+ .mbs
+ docstrip-Archiv der Master-Bibliography-BibTeX-Styles des
+ Pakets `custom-bib' (siehe Frage 7.2.2)
+
+
+ LaTeX (TeX-Format):
+
+
+ .aux
+ Hilfsdatei, enthlt Querverweise etc.
+
+ .toc
+ Inhaltsverzeichnis
+
+ .lof
+ Verzeichnis der Abbildungen
+
+ .lot
+ Verzeichnis der Tafeln
+
+ .ltx
+ Dokumentquelldatei, alternativ zur Namensendung .tex (auch
+ fr LaTeX-Kernel-Dateien)
+
+ .cls
+
+ .clo
+ TeX-Eingabedatei mit Definitionen fr die Dokumentenklasse
+ und die entsprechenden Klassen-Optionen
+
+ .sty
+ TeX-Eingabedatei mit Definitionen eines LaTeX-Pakets; in
+ LaTeX 2.09 wurde diese Namensendung sowohl fr Styles (in
+ 2e: Klassen) als auch Style-Options (in 2e: Pakete) benutzt
+
+ .fd
+ TeX-Eingabedatei mit Font-Definition, enthlt Tabellen, mit
+ denen die LaTeX-Spezifikation einer Schrift mittels
+ Encoding, Family, Series und Shape auf den Namen einer
+ .tfm-Datei abgebildet wird. Der Name der .fd-Datei besteht
+ aus Encoding und Family.
+
+ .def
+ Runtime-Module des LaTeX-Kernels, die bei Bedarf geladen
+ werden (``latex209.def'' fr Kompatibilittsmodus,
+ ``slides.def'' fr SliTeX), ebenso fr einige Pakete, wie
+ beispielsweise fr `inputenc', `fontenc' und `graphics'.
+
+ .cfg
+ TeX-Eingabedatei mit Konfigurationsinformation
+
+ .ldf
+ TeX-Eingabedatei mit der Language-Definition fr eine
+ Sprache mit ihren Dialekten des babel-Pakets. (Historisch:
+ in lteren Babel-Versionen in .sty-Dateien)
+
+
+ MusiXTeX, PMX, M-Tx:
+
+
+ .mx1
+ MusiXTeX-Ausgabe der 1. Phase als Eingabe fr das Programm
+ MusiXFLX, das den Zeilenumbruch der Noten herstellt
+
+ .mx2
+ MusiXFLX-Ausgabe als Eingabe fr die 2. MusiXTeX-Phase
+
+ .mxl
+ MusiXFLX-Log-Datei
+
+ .pmx
+ PMX-Eingabedaten
+
+ .mtx
+ M-Tx-Eingabedaten
+
+
+ PostScript-Schriften:
+
+
+ .afm
+ Adobe Font Metric, in lesbarer ASCII-Darstellung
+
+ .pfm
+ Printer Font Metric, in Windows-Darstellung
+
+ .pfa
+ PostScript-Type-1-Schriftschnittprogramm in ASCII-Format,
+ enthlt das Type-1-Programm zum Zeichnen jeder Letter
+
+ .pfb
+ PostScript-Type-1-Schriftschnittprogramm in Binrformat
+
+
+ TeX-Implementierungen und Gertetreiber:
+
+
+ .tcp
+ TeX-Code-Page-Definition (emTeX).
+
+ .tcx
+ TeX-Code-Page-Definition (web2c v7.0, noch im Teststadium!)
+
+ .enc
+ Encoding-Dateien fr PostScript-Schriften (dvips)
+
+ .map
+ Zuordnungstabellen fr Fontnamen
+
+
+Eine zwangslufig unvollstndige Liste von Dateinamensendungen kann man
+auch im Buch `Der LaTeX-Begleiter' bzw. `LaTeX Companion' und im Buch
+`Making TeX Work' (siehe Frage 2.4.1) und in `The Components of TeX' von
+Joachim Schrod (siehe Frage 2.4.2) finden.
+
+3.1.6 Welche TeX-/METAFONT-/METAPOST-Versionen sind aktuell?
+
+Derzeit sind die folgenden Versionen aktuell:
+
+TeX: 3.14159 (seit Mrz 1995)
+plain.tex: 3.1415926 (seit August 1998)
+
+METAFONT: 2.7182 (seit August 1998)
+plain.mf: 2.71 (seit Juni 1993)
+
+METAPOST: 0.641 (seit Mrz 1998) (?)
+dvitomp.web: 0.64 (seit Januar 1998)
+plain.mp: 0.64 (seit Januar 1998)
+
+CM-Fonts: - (wichtige nderungen 1992,
+ kleinere nderungen Mrz 1995,
+ kleinere nderungen August 1998)
+
+tangle.web 4.4 (seit Februar 1993)
+weave.web 4.4 (seit Januar 1992)
+webmac.tex 4.1 (seit Mai 1990)
+
+Neue Versionen von TeX und METAFONT werden von Donald E. Knuth nur noch
+in immer grer werdenden zeitlichen Abstnden erstellt, so da man
+ltere Versionen auf alle Flle durch die neueste Version ersetzen
+sollte.
+Leider hat Knuth fr die CM-Fonts keine Versionsnummer vergeben, so da
+es schwieriger ist, die Versionen mit den meist nur geringen nderungen
+auseinanderzuhalten. Da Knuth umfangreichere nderungen an den CM-Fonts
+im Frhjahr 1992 durchgefhrt hat, sollte man alle lteren
+CM-Font-Versionen auf die neue Version bringen. Erkennbar sind die alten
+Versionen beispielweise am horizontalen Querstrich am Fu des groen
+kalligraphischen T `$\mathcal{T}$' (bzw. `${\cal T}$'), der in der neuen
+Version fehlt oder an der rundlicheren, s-frmigeren Form des kleinen
+Deltas `$\delta$', da in neueren Versionen der obere Bogen nun etwas
+winkliger ausgefhrt wurde. Die aktuelle Version der CM-Font-Dateien
+erkennt man an folgenden Zeilen:
+
+ % THIS IS THE OFFICIAL COMPUTER MODERN SOURCE FILE cmr10.mf BY D E
+ KNUTH.
+ % IT MUST NOT BE MODIFIED IN ANY WAY UNLESS THE FILE NAME IS CHANGED!
+
+ACHTUNG: TeX-Pakete, wie emTeX, vergeben meist noch eine eigene
+Versionsnummer fr TeX und MF. Man sollte die oben angegebene,
+offizielle Versionsnummer nicht mit diesen verwechseln.
+
+3.1.7 Was ist TDS, die `TeX Directory Structure'?
+
+Hauptfunktion von TDS ist die Festlegung einer Grundstruktur fr ein
+TeX-System. In dieser kann TeX samt Hilfswerkzeugen, Makropaketen, Fonts
+etc. systematisch geordnet und damit fr _alle_ Installationen und
+Systeme gleich und einheitlich untergebracht werden. Somit knnen
+implementierungsunabhngige Teile beispielsweise auch ber NFS-Mounts
+oder von CD-ROM fr alle Systeme zur Verfgung gestellt werden. Die von
+TDS festgelegte Grundstruktur ist offen, kann also jederzeit fr weitere
+Applikationen erweitert werden.
+Der TDS-Standard richtet sich primr an TeX-Systemadministratoren und
+Personen, die TeX-Distributionen zusammenstellen. Wenn Entwickler eines
+TeX-Pakets von einer generell gltigen Verzeichnisstruktur ausgehen
+knnen, kann auch die Installation eines Pakets leichter automatisiert
+oder zumindest mit sehr przisen Anweisungen versehen werden. Fr
+Endbenutzer ist eine solche wohldefinierte Systemstruktur ebenfalls von
+Interesse, wenn sie sich mit der Ausstattung des Systems, das sie
+benutzen, nher vertraut machen wollen.
+Der aktuelle TDS-Vorschlag ist in verschiedenen Dateiformaten (DVI,
+PostScript, HTML, Texinfo etc.) in CTAN: tds/ zu finden. Eine
+exemplarische Implementierung des Standards stellt die CD-ROM ``TeX
+Live'' dar.
+
+TDS: CTAN: tds/
+
+
+
+3.2 Welche TeX-Formate gibt es? Was ist LaTeX?
+
+
+3.2.1 Was ist ein (TeX-)Format?
+
+Das Programm TeX besteht aus einem Teil, mit dem Text und mathematische
+Formeln gesetzt, Abstze umbrochen und alles zu Seiten zusammenmontiert
+wird, und aus einem Makroprozessor. Dieser Makroprozessor stellt eine
+mchtige, wenn auch fr die meisten eine eher ungewohnte
+Programmiermglichkeit dar, mit der man den sehr einfachen Befehlssatz
+von TeX durch eigene benutzerfreundlichere Makros ergnzen kann. Einen
+abgeschlossenen Satz von solchen Makros nennt man Format. Eine
+Formatdatei ist eine mit IniTeX durch `Dumpen' erzeugte Datei, die diese
+Makros enthlt (siehe Frage 3.1.3). Meist wird der Formatname auch fr
+das Programm VirTeX verwendet, wenn man die zugehrige Formatdatei ldt,
+so da man bei Verwendung des Formatnamens diese Mehrdeutigkeit bedenken
+sollte.
+Ohne vom Benutzer definierte Makros besitzt TeX nur ca. 300 primitive
+`control sequences'. Davon sind ungefhr die Hlfte Anweisungen, die
+andere Hlfte Parameter. Fr einen Autor sind diese Anweisungen alleine
+zu einfach und drftig, so da es ratsam ist, als Autor mchtigere und
+damit einfacher benutzbare Anweisungen in Form von Makros zu verwenden.
+
+3.2.2 Was ist Plain-TeX?
+
+Donald E. Knuth hat fr TeX ein Makropaket namens Plain-TeX erstellt und
+diese Makros im Buch `The TeXbook' beschrieben. Dabei stellt Plain-TeX
+einen minimalen Satz an Makros dar, um TeX sinnvoll verwenden zu knnen.
+Zustzlich enthlt Plain-TeX einige Makros, wie `\beginsection' oder
+`\proclaim', die man als Beispiel fr komplexere Anweisungen ansehen
+kann.
+Wenn jemand sagt, da er ``TeX programmiert'', so meint er
+normalerweise, da er in TeX und den Plain-TeX-Makros programmiert.
+
+3.2.3 Was ist LaTeX, LaTeX2e und LaTeX 2.09?
+
+LaTeX ist ein in den Jahren 1982-1986 von Leslie Lamport geschriebenes
+Makropaket fr TeX. Es erlaubt dem Autor eines Dokuments, die einzelnen
+Teile gem ihrer logischen Bedeutung, wie z.B. `berschrift',
+`Aufzhlung', `Aufzhlungspunkt' usw., zu markieren. Anhand dieser
+Markierungen, dem sogenannten `Markup' oder der Text-Auszeichnung, kann
+(La)TeX das Dokument unter Verwendung eines vorgefertigten Layouts in
+Buchdruck-Qualitt setzen und mittels sogenannter Gerte-Treiber
+ausdrucken.
+Fast 10 Jahre war LaTeX in der Version 2.09 aktuell, wobei es zuletzt
+immer mehr inkompatible Erweiterungen gab. Seit dem Juni 1994 ist
+LaTeX2e die aktuelle Version. Diese wurde regelmig im Juni und
+Dezember jeden Jahres auf den neuesten Stand gebracht. Ab Juni 2000 gibt
+es nurmehr einmal jhrlich eine neue Version.
+Wenn in dieser FAQ von LaTeX die Rede ist, so ist immer LaTeX2e und
+nicht LaTeX 2.09 gemeint.
+
+3.2.4 Welche (La)TeX-Makropakete gibt es?
+
+Es gibt mehrere unterschiedlich umfangreiche und gewartete bersichten
+ber (La)TeX-Makropakete, die im folgenden ohne Wertung aufgezhlt
+werden:
+
+* The LaTeX Catalogue
+ CTAN: help/Catalogue/catalogue.html
+* (La)TeX Navigator
+ http://tex.loria.fr
+* LaTeX-Paketliste von Harald Axel Sommerfeldt
+ http://www.axel-sommerfeldt.de/latex/
+* Liste von Kerstin Schiebel
+ http://www.gsi.de/computing/TeX/latexsty.html
+* Die Bcher ``Der LaTeX-Begleiter'', ``The LaTeX Companion'' und ``The
+ LaTeX Graphics Companion'' stellen viele Pakete vor. Diese bersicht
+ kann jedoch naturgem nicht aktuell und vollstndig sein.
+
+
+3.2.5 Was ist AmS-TeX, AmS-LaTeX und LAMSTeX? Was sind die AmS-Fonts?
+
+AmS-TeX ist ein in den Jahren 1983-1985 von Michael D. Spivak fr die
+American Mathematical Society (AmS) geschriebenes Makropaket, das auf
+Plain-TeX basiert. Es erweitert Plain-TeX um sehr viele fr den
+mathematischen Formelsatz notwendige Konstrukte. Dieses Makropaket wird
+im Buch `The Joy of TeX' von Michael Spivak (2. Auflage, AmS, 1990, ISBN
+0-821-82997-1) beschrieben.
+Mit der weiteren Verbreitung von LaTeX entwickelt die AmS seit 1990
+mehrere auf LaTeX basierende Makropakete, die unter dem Namen AmS-LaTeX
+zusammemgefat werden. Diese LaTeX-Pakete stellen einem Autor einen
+Groteil der in AmS-TeX enthaltenen Konstrukte zur Verfgung.
+LAMSTeX nennt sich Michael Spivaks Anpassung von AmS-TeX an LaTeX, die
+jedoch nur einen sehr kleinen Nutzerkreis hat und nicht weit verbreitet
+ist.
+Fr den mathematischen Formelsatz fehlen den von Donald E. Knuth
+erstellten Schriften weitere dringend notwendige Zeichen. Diese werden
+durch die AmS-Fonts zur Verfgung gestellt, die u.a. weitere
+CM-Schriften, Euler-, `msam'-, `msbm'- und kyrillische Schriften
+enthalten.
+
+3.2.6 Was ist Texinfo?
+
+Texinfo ist ein Dokumentationssystem, das zur Dokumentation der
+GNU-Sofware verwendet wird. Die Dokumentation wird dabei in einer
+Quelldatei mit der Dateinamensendung `.texi' (oder `.txi' bzw.
+`.texinfo') abgelegt, aus der einerseits sogenannte `info'-Dateien,
+einem on-line mit dem GNU-Emacsoder dem Programm `info' lesbarer
+Hypertext, erzeugt werden knnen. Andererseits stellt die Quelldatei
+eine TeX-Datei dar, zu deren Formatierung mit Plain-TeX zu Beginn das
+Texinfo-Makropaket ``texinfo.tex'' automatisch hinzugeladen wird. Mit
+den Programmen `makeinfo' (aus dem Paket Texinfo seit Version 4.0) und
+`texi2html' ist die Konvertierung nach HTML mglich. Texinfo basiert auf
+Plain-TeX.
+
+Texinfo: http://www.texinfo.org
+ CTAN: macros/texinfo
+
+
+
+3.2.7 Was ist ConTeXt?
+
+ConTeXt ist ein von Hans Hagen geschriebenes Makropaket fr TeX. Es
+erlaubt, hnlich wie LaTeX, das Erstellen von Texten mit Hilfe von
+Strukturmakros (berschrift u..). Bei der Erstellung wurde auf eine
+leichte Benutzbarkeit und Flexibilitt geachtet, zudem wird die
+Erstellung interaktiver Texte untersttzt. Eine Besonderheit ist die
+multilinguale Schnittstelle, die z.B. niederlndisch, englisch und
+deutsch untersttzt, sowie das Setzen von multilingualen Unterschriften
+(`Tabelle' statt `Table' u..).
+
+ConTeXt: http://www.pragma-ade.nl/
+ http://www.ntg.nl/context/
+ CTAN: macros/context/
+Berend de Boer:
+LaTeX in proper http://www.xs4all.nl/~nederwar/tex/LaTeX2ConTeXt.pdf
+ConTeXt::
+
+
+
+3.3 Welche TeX-Weiterentwicklungen gibt es?
+
+
+3.3.1 Was ist TeX-XeT bzw. TeX--XeT?
+
+Donald E. Knuth und Pierre MacKay entwickelten eine TeX-Erweiterung
+namens TeX-XeT, die es erlaubt, Texte, die von links nach rechts
+geschrieben werden, mit Texten, die von rechts nach links (Bsp:
+arabisch, hebrisch) geschrieben werden, beliebig zu mischen. TeX-XeT
+erzeugt jedoch sogenannte ivd-Dateien, d.h. dvi-Dateien mit zustzlichen
+dvi-Codes, die von blichen dvi-Treibern nicht verstanden werden und
+damit zu Fehlern oder zum Abbruch des dvi-Treibers fhren. Diese
+ivd-Dateien bentigen daher spezielle dvi-Treiber oder sie knnen mit
+dem Programm `ivd2dvi' in gewhnliche dvi-Dateien konvertiert werden.
+Die TeX-nderungen fr TeX-XeT wurden in einem Artikel in TUGboat 8,
+1987 (S. 14-15) verffentlicht.
+TeX--XeT ist eine TeX-XeT-Reimplementierung von Peter Breitenlohner. Im
+Unterschied zu TeX-XeT erzeugt TeX--XeT gewhnliche dvi-Dateien, die
+somit von jedem dvi-Treiber gelesen werden knnen. Die neueste
+verbesserte Version von TeX--XeT ist seit Version 1 Bestandteil von
+e-TeX (siehe Frage 3.3.4).
+
+TeX--XeT: CTAN: systems/knuth/tex--xet/
+ivd2dvi: CTAN: dviware/ivd2dvi/
+
+
+
+3.3.2 Was ist MLTeX?
+
+MLTeX ist eine TeX-Erweiterung von Michael J. Ferguson, die es
+ermglicht, da auch mit den blichen CM-Schriften Trennmuster mit
+akzentuierten Zeichen verwendet und damit Wrter mit akzentuierten
+Zeichen getrennt werden knnen. In Standard-TeX ist dies nicht mglich,
+da es notwendig ist, da die verwendete Schriften diese akzentuierten
+Zeichen enthalten (siehe Frage 5.3.2). In MLTeX wird vorgegaukelt, da
+die akzentuierten Zeichen in den Schriften existieren, diese aber dann
+durch sogenannte `character substitutions', die mit dem neuen Primitiv
+\charsubdef definiert werden, durch tatschlich in der Schrift
+vorhandene Zeichen zusammengebaut. Bei Verwendung von T1-kodierten
+Schriften, wie z.B. die EC-Schriften, ist MLTeX nicht mehr notwendig.
+MLTeX hat sich aus verschiedenen Grnden hauptschlich im
+franzsischsprachigen Raum verbreitet. Aktuell ist Version 2.2 vom
+Dezember 1995 von Bernd Raichle, der die weitere Pflege von MLTeX
+bernommen hat. ltere Versionen haben verschiedene Programmfehler, die
+u.a. zu Problemen fhren, falls MLTeX mit nichtlateinischen Schriften
+(z.B. mit ArabTeX) verwendet wird. Mit ``mltextst.tex'' gibt es eine
+Testdatei, um eine MLTeX-Implementierung auf die bekannten Fehler zu
+testen.
+Zur einfachen Nutzung der Fhigkeiten von MLTeX unter LaTeX gibt es seit
+Dezember 1998 das LaTeX-Paket `mltex'.
+
+MLTeX: CTAN: systems/generic/mltex/
+mltextst.tex: CTAN: systems/generic/mltex/mltextst.tex
+mltex: CTAN: macros/latex/contrib/mltex
+
+
+
+3.3.3 Was ist NTS?
+
+TeX, METAFONT und die anderen Programme von Prof. Knuth wurden von ihm
+in ihrem jetzigen Zustand eingefroren. Es werden nur noch Fehler
+entfernt, jedoch wird es keine grundlegenden nderungen und
+Weiterentwicklungen dieser Programme geben. Momentan gibt es mehrere
+Projekte, die die Weiterentwicklung des Textsatzsystems TeX zum Ziel
+haben.
+`NTS' (oder das `New Typesetting System') wird von der NTS-Gruppe unter
+Leitung von Phil Taylor geplant. NTS ist eine radikale Neuentwicklung
+eines Textsatzsystems, das jedoch weiterhin einen
+TeX-Kompatibilittsmodus haben wird. Die Realisierung von NTS ist
+langfristig ber mehrere Jahre angelegt, da hierzu grere Ressourcen
+notwendig sind und erst beschafft werden mssen.
+Momentan wird eine erste Version von NTS in der Programmiersprache Java
+implementiert. Diese Version wird vollstndig TeX-kompatibel sein und
+noch keine Erweiterungen besitzen, jedoch durch die modularere
+Programmierung leichter erweiterbar sein. Dieser erste Prototyp soll bis
+Mitte 2000 fertiggestellt sein, im Frhjahr 2000 liefen bereits alle
+Teile auer denjenigen, die den Tabellensatz bewerkstelligen. Die
+endgltige Version wurde im Mai 2001 an die TeX-Welt verteilt.
+Weitergehendes existiert momentan nur als Konzept und in Form einer
+Liste von Anforderungen und Erweiterungswnschen.
+
+NTS: http://nts.tug.org/
+
+
+
+3.3.4 Was ist e-TeX? Was ist Eetex?
+
+Unter dem Namen `e-TeX' (extended/enhanced TeX) wird unter der Leitung
+von Peter Breitenlohner TeX um dringend bentigte Erweiterungen ergnzt.
+Ein wichtiges Ziel von e-TeX ist dabei, weiterhin 100% kompatibel zu TeX
+zu bleiben, solange die Erweiterungen nicht benutzt werden. Die
+Entwicklung basiert auf dem aktuellen TeX-Quellcode in einem durch
+WEB-Konstrukte erweiterten Standard-Pascal, so da dies und die genannte
+Zielsetzung gewisse Beschrnkungen, wie der Verzicht auf eine dynamische
+Speicherverwaltung, auferlegt, was grundlegende Neuerungen in e-TeX
+anbelangt. Die erste Version von e-TeX wurde im Oktober 1996 auf der
+Mitgliederversammlung von DANTE e.V. in Hamburg verffentlicht. Fertig
+benutzbare Implementierungen sind u.a. fr VMS, MS-DOS (PublicTeX),
+Windows 95/NT (Win32-Web2c), Amiga (AmiWeb2C) und Unix (Web2c v7.x mit
+Patches zur Integration von e-TeX) verfgbar.
+Eetex ist die ``Spielwiese'' der NTG-Future-Group (siehe
+Diskussionsliste 1.3.4). Diese TeX-Erweiterung basiert auf e-TeX,
+erweitert dieses jedoch um weitere vorgeschlagene Primitive. Das
+Programm ist jedoch weder stabil noch fehlerfrei, sondern dient dazu,
+Erweiterungsvorschlge in einem Prototypen auszutesten. Die erste
+Version enthlt Primitive zur leichteren und schnelleren Verarbeitung
+von Listen und einen speziellen SGML-Lesemodus. Das Programm wird
+momentan nur fertig fr MS-DOS, Windows 95 und Linux verteilt.
+
+e-TeX: CTAN: systems/e-tex/
+Eetex: http://www.elvenkind.com/~taco/eetex/
+
+
+
+3.3.5 Was ist Omega?
+
+Omega ist neben NTS/e-TeX das zweite Projekt, das sich mit der
+Weiterentwicklung von TeX beschftigt.
+`Omega' wird von John Plaice und Yannis Haralambous entwickelt und ist
+Anfang Dezember 1995 in einer zweiten Version verffentlicht worden. Als
+Basis von Omega dient der Quellcode von TeX und METAFONT, wobei beide
+Programme um die Mglichkeit erweitert wurden, intern Zeichen in UNICODE
+zu reprsentieren (pro Zeichen 16 bit statt 8 bit). Durch die Verwendung
+von UNICODE und von sogenannten Ein- und Ausgabe-Filtern wird eine
+Anpassung an verschiedene Sprachen sehr einfach. So kann beispielsweise
+durch Wahl von entsprechenden Filtern ein Dokument sehr einfach in
+arabischer Schrift gesetzt werden, in der ein einzelnes Zeichen abhngig
+vom Kontext in bis zu vier mglichen Darstellungen gesetzt wird.
+
+Omega: http://omega.cse.unsw.edu.au/
+ CTAN: systems/omega/
+
+
+
+3.3.6 Was ist pdfTeX?
+
+`pdfTeX', das vormals TeX2PDF hie, ist eine TeX-Variante, mit der man
+sowohl die blichen DVI-Dateien als auch direkt Dateien in Adobes
+Portable-Document-Format, kurz PDF, erzeugen kann. Um die zustzlichen
+Mglichkeiten, wie Hyperlinks, Anmerkungen etc., die PDF bietet, auch
+nutzen zu knnen, wurden weitere PDF-Primitive dem Makroprogrammierer
+zur Verfgung gestellt. Das Makropaket `hyperref' untersttzt pdfTeX,
+wobei die Benutzung von pdfTeX automatisch erkannt wird, aber auch durch
+die Option `pdftex' angegeben werden kann.
+pdfTeX wurde von Hn Th Thnh entwickelt und Ende Februar 1997 in
+ersten Testversionen verffentlicht. Seitdem weist pdfTeX eine gute
+Stabilitt auf. Es wurden jedoch seitdem Funktionen hinzugefgt, die
+dazu fhrten, da sich Details auf Makroebene nderten. Dies fhrt dazu,
+da ltere Versionen von Makropaketen fr pdfTeX nicht mehr fehlerfrei
+mit neueren pdfTeX-Versionen laufen.
+
+pdfTeX: http://www.tug.org/applications/pdftex/
+pdfTeX: http://freshmeat.net/projects/pdftex/
+ CTAN: systems/pdftex/
+ (Source fr Web2c v7.x, Binaries fr einige Systeme)
+hyperref: CTAN: macros/latex/contrib/hyperref
+hyperref http://www.tug.org/applications/hyperref/
+(aktuell):
+thumbpdf: CTAN: support/thumbpdf/
+TeX and Solving Font Problems
+PDF:
+ http://web.mit.edu/etheses/www/tex/texpdf.html
+AcroTeX: Hinweise zu LaTeX und PDF
+ http://www.math.uakron.edu/~dpstory/acrotex.html
+Einfhrung ftp://ftp.fernuni-hagen.de/pub/pdf/urz-broschueren/unplugged/pdftex.dante01.pdf
+in pdfTeX:
+Timothy van
+Zandt's http://zandtwerk.insead.fr/tex2pdf.html
+notes:
+Creating
+quality
+Adobe PDF http://www.adobe.com/support/techdocs/543e.htm
+files from
+TeX with
+DVIPS:
+PDF
+Reference
+Manual, http://partners.adobe.com/asn/developer/PDFS/TN/PDFSPEC.PDF
+Version
+1.3:
+Thomas
+Feuerstack:
+Acrobat/PDF ftp://ftp.fernuni-hagen.de/pub/pdf/urz-broschueren/unplugged/AcS01.pdf
+...eine
+Einfhrung:
+Udo
+Schuermann:
+Linux http://ringlord.com/publications/latex-pdf-howto/
+LaTeX-PDF
+HOW-TO:
+
+
+
+3.3.7 Was ist `ant'?
+
+`ant', geschrieben von Achim Blumensath, ist ein Scheme-basierter Ersatz
+fr TeX, der nicht mit dem Ziel vollstndiger Kompatibilitt, sondern
+dem eines flexiblen und sauberen Designs entwickelt wurde.
+Bei der aktuellen Version handelt es sich um einen pre-alpha Prototyp,
+der als Diskussionsgrundlage und als Testumgebung fr neue
+Satzalgorithmen dienen soll.
+
+ant: http://www-mgi.informatik.rwth-aachen.de/~blume/Download.html
+
+
+
+--- DE-TeX-FAQ Ende Teil 3 ---
diff --git a/help/de-tex-faq/part4 b/help/de-tex-faq/part4
new file mode 100644
index 0000000000..7a10909aee
--- /dev/null
+++ b/help/de-tex-faq/part4
@@ -0,0 +1,1022 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!aanews.merit.edu!news.cc.uic.edu!news.uchicago.edu!logbridge.uoregon.edu!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 4 of 11)
+Supersedes: <de-tex-faq-4-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:16 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 993
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-4-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975396 888 134.100.9.52 (19 Sep 2003 12:43:16 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:16 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117401 de.answers:9378 news.answers:258267
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part4
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 4 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+4 Textsatzsystem TeX - Bezugsquellen
+
+
+4.1 Wie bekomme ich ein TeX-System?
+
+Es gibt verschiedene Wege, wie Sie ein TeX-System beziehen knnen. Falls
+Sie die notwendige Untersttzung (durch Hotline, Schulungen, Updates
+u..) sicherstellen wollen oder mssen, sollten Sie sich an einen
+kommerziellen Anbieter wenden.
+Beachten Sie bei den nachfolgenden Angeboten bitte, da Sie bei frei
+verfgbaren TeX-Versionen, Programmen und Schriften, die `Shareware'
+sind, geringe Lizenzgebhren an die Autoren zu entrichten haben.
+Auerdem drfen einige Programme, Makrodateien, Schriften etc. nicht
+oder nur nach Lizenzierung oder einer individuellen Freigabe durch den
+Autor zu kommerziellen Zwecken eingesetzt oder vertrieben werden.
+An frei verfgbare TeX-Implementierungen knnen Sie per
+
+ 1. ftp oder WWW (Internet),
+ 2. E-Mail,
+ 3. Modem/Telefon,
+ 4. CD-ROM oder
+ 5. als Bestandteil eines anderen Software-Paketes
+
+kommen. Als Mitglied bei DANTE e.V. stehen Ihnen noch weitere und evtl.
+gnstigere Angebote zur Auswahl (siehe Frage 4.1.7).
+
+4.1.1 Wie bekomme ich ein TeX-System ber ftp/Internet und E-Mail?
+
+CTAN, das `Comprehensive TeX Archive Network', und dessen `Spiegel'
+knnen ber ftp oder durch den ftp-Mailer auch ber E-Mail erreicht
+werden (siehe Abschnitt 1.2).
+
+4.1.2 Wie bekomme ich ein TeX-System ber Modem/Telefon?
+
+Teile des CTAN-Inhalts knnen Sie in vielen Mailbox-Netzen auf einigen
+`Knoten' erhalten, die ein TeX-Archiv anbieten. Informieren Sie sich
+bitte bei anderen Benutzern des entsprechenden Mailbox-Netzes oder einer
+Ansprechperson fr dieses Netz.
+
+4.1.3 Wie bekomme ich ein TeX-System auf CD-ROM?
+
+Mittlerweile sind verschiedene CD-ROM-Angebote mit TeX-Software ber
+CD-ROM-Versender und in immer mehr Buchhandlungen zu finden. Bei
+TeX-CD-ROMs kann man grob zwei Typen unterscheiden:
+
+* CD-ROMs, die einen kompletten Abzug oder Teile des CTAN-Inhalts
+ enthalten (einzelne oder mehrere CD-ROMs; meist komprimiert und
+ gepackt, damit auf eine CD-ROM mehr pat und weil Datei- und
+ Verzeichnisnamen auf ISO-9660-CD-ROM nicht beliebig lang sein und nur
+ eine beschrnkte Menge von Zeichen enthalten drfen),
+* CD-ROMs, die eine Ready-to-Run-Installation eines mehr oder weniger
+ kompletten TeX-Systems enthalten, das sogar ohne Installation von der
+ CD-ROM selbst lauffhig ist.
+
+Weiter sollte man auf die Aktualitt des Inhalts achten und auf die
+mitgelieferte teils knappe, teils sehr ausfhrliche Dokumentation.
+Besonders bei Ready-To-Run-Installationen ist letztere sehr wichtig!
+ Achtung: teilweise werden noch alte Auflagen von CD-ROMs (ohne einen
+krftigen Preisnachla) verkauft. CD-ROMs mit CTAN-Kopien, deren Inhalt
+ lter als ein Jahr ist, sollte man liegenlassen!
+Die bersichten in Frage 4.1.4 und Frage 4.1.5 sind aus den gesammelten
+Postings entstanden und erheben weder den Anspruch auf Korrektheit,
+Vollstndigkeit, noch auf Aktualitt. `Stand' gibt bei CTAN-Abzgen
+nicht das Erscheinungsdatum, sondern, soweit mglich, das Datum des
+Abzuges an. Neue CD-ROM-Angebote, Korrekturen der kurzen
+Inhaltsbeschreibungen, Preise u.. bitte an `detexfaq@dante.de'!
+
+4.1.4 Wie bekomme ich ein TeX-System auf CD-ROM, das leicht
+installierbar oder sogar direkt von CD-ROM lauffhig ist?
+
+Folgende CD-ROMs bieten ein aktuelles, leicht installierbares TeX-System
+fr bestimmte Betriebssysteme an:
+
+* CD `TeX Live'
+ 5. Auflage, Einzel-CD mit Dokumentation
+
+ Stand: Juni 2000 (fr Version 5c)
+ ISBN: ISBN 3-931253-63-5
+ Preis: fr Mitglieder von DANTE e.V. ist ein Exemplar frei,
+ sonst 29,90 DM fr alle bei Lehmanns Fachbuchhandlung
+ URL: http://www.tug.org/texlive.html,
+ http://www.dante.de/software/cdrom/, http://www.lob.de?flag=dan
+
+ Diese CD wird fr Mitglieder der TUG, UK TUG und DANTE e.V. zusammen
+ mit der Mitgliedszeitschrift als Bonus ausgeliefert. Mitglieder von
+ DANTE e.V. erhielten ein Exemplar mit Ausgabe 2/2000 der
+ Mitgliedszeitschrift.
+ Enthlt von CD-ROM lauffhiges TeX-System fr viele Unix-Plattformen
+ (Linux, Solaris 2.7, IBM RS 6000 AIX 4.2, HP9000 HPUX 10.20 u.v.m.),
+ fr Windows 95, 98, 2000 und NT und mit Binaries fr METAPOST, e-TeX,
+ PDFTeX und Omega, basierend auf dem teTeX-Paket 1.0 und web2c 7.3.1,
+ mit sehr vielen Makro-/Schrift-Paketen einschlielich Dokumentation.
+ Zustzlich ist die Original-Verteilung von emTeX bzw. emTeXTDS (OS/2,
+ MS-DOS) neben vielen weiteren Programmquellen auf der CD-ROM. Als
+ Standard des CD-ROM-Dateisystems wurde ISO 9660 mit den Rock-Ridge-
+ und Joliet-Erweiterungen benutzt, so da der nach dem
+ TeX-Directory-Standard (TDS) geordnete TeX-Baum durch die langen
+ Dateinamen in gemischter Gro-Klein-Schreibung einfacher verwendet
+ werden kann - auch fr andere Plattformen!
+* 4allTeX - The ultimate TeX resource
+ 5. Auflage, Doppel-CD und ausfhrliches englisches Handbuch
+
+ Stand: Mitte 1999
+ Preis ber die NTG: 5 Euro fr die Doppel-CD
+ 25 Euro fr das Handbuch
+ URL: http://4tex.ntg.nl/
+
+ Enthlt von CD-ROM lauffhiges fpTeX, dem Web2c fr Win32, eine groe
+ Anzahl von TeX-Forma- und Font-Dateien, Ghostscript und viele weitere
+ Zusatzprogramme, sowie Dokumentationen in den Formaten HTML, PS und
+ PDF. Die CD-ROM ist durch die 4allTeX-Workbench, einer integrierter
+ Benutzungsoberflche, sehr einfach zu installieren und zu bedienen.
+ Mitglieder von DANTE e.V. knnen die 5. Auflage der 4allTeX-CD zum
+ Preis von 3,-- DM ber den Verein anfordern.
+
+
+4.1.5 Wie bekomme ich zu TeX-Software auf CD-ROM, die mglichst alles
+rund um TeX enthlt?
+
+Folgende CD-ROMs enthalten einen aktuellen Abzug von CTAN (siehe
+Abschnitt 1.2). Auf CTAN und damit auch auf diesen CD-ROMs findet man
+fr die meisten Betriebssysteme auch installierbare TeX-Systeme (siehe
+Frage 4.2.1). Im Unterschied zu den CD-ROMs mit leicht installierbaren
+TeX-Systeme wird man bei den CD-ROMs mit CTAN-Abzug nicht zu den
+Installationsprogrammen geleitet.
+
+* TeX-Software, Comprehensive TeX Archive Network (CTAN)
+ Dreier-CD
+
+ Stand: September 2000
+ ISBN: ISBN 3-931253-66-X
+ Preis: 39,90 DM fr alle bei Lehmanns Fachbuchhandlung
+ URL: http://www.dante.de/software/cdrom/, http://www.lob.de?flag=dan
+
+ Enthlt fast kompletten CTAN-Abzug unkomprimiert auf drei CDs. Fr
+ Mitglieder von DANTE e.V. lag ein Exemplar der Ausgabe 3/2000 der
+ Mitgliedszeitschrift kostenlos bei.
+ Die 4. Auflage des CTAN-Abzugs auf drei CDs vom Mai 1999 ging jedem
+ Mitglied von DANTE e.V. mit Ausgabe 3/1999 der Mitgliedszeitschrift im
+ Rahmen der Mitgliedschaft zu. Mit Ausgabe 4/1997 gab es die 3. Auflage
+ vom 25. Januar 1998 unter dem Namen ``TeX/LaTeX - CTAN-CD von DANTE
+ e.V.'' als Dreier-CD-Satz, mit Ausgabe 3/1996 und 2/1997 gab es die
+ 2. Auflage des CTAN-Abzugs vom 14. Dezember 1996 als Doppel-CD und
+ eine Update-CD mit den nderungen des CTAN-Inhalts zwischen Dezember
+ 1996 und dem 12. Mai 1997.
+
+
+4.1.6 Wie bekomme ich ein TeX-System ... aus anderen Software-Paketen?
+
+Teilweise enthalten verschiedene Software-Pakete bereits eine lauffhige
+TeX-Implementierung. So ist z.B. bei jedem Linux ein komplettes
+TeX-System enthalten.
+
+4.1.7 Wie bekomme ich ein TeX-System als Mitglied von DANTE e.V.?
+
+Als Mitglied bei DANTE e.V. stehen Ihnen folgende weitere Angebote zur
+Auswahl (siehe Frage 2.1.4, wenn Sie wissen wollen, wie Sie Mitglied
+werden knnen):
+
+* CTAN:
+
+ o Falls Sie Zugriff auf das Internet haben, so knnen Sie direkt auf
+ CTAN zugreifen (siehe Abschnitt 1.2).
+
+* CD-ROM:
+
+ o CTAN-CD von DANTE e.V.: Die 5. Auflage der Dreier-CD mit dem
+ CTAN-Abzug von September 2000 erhielt jedes Mitglied von DANTE e.V.
+ mit Ausgabe 3/2000, die vorherige 4. Auflage vom Mai 1999 mit
+ Ausgabe 3/1999 der Mitgliederzeitschrift.
+ Diese CD ist auerdem ber Lehmanns Fachbuchhandlung
+ (http://www.lob.de?flag=dan) fr 39,90 DM zu erhalten.
+ o CD `TeX Live': Mitglieder von DANTE e.V. erhielten ein Exemplar der
+ 5. Auflage (Version 5c, Juni 2000) mit Ausgabe 2/2000, ein Exemplar
+ der 4. Auflage (April 1999) mit Ausgabe 2/1999 der
+ Mitgliedszeitschrift.
+ Diese CD ist auerdem ber Lehmanns Fachbuchhandlung
+ (http://www.lob.de?flag=dan) fr 29,90 DM zu erhalten.
+ o 4allTeX - The ultimate TeX resource: Mitglieder von DANTE e.V.
+ erhielten ein Exemplar der 4. Auflage (Dezember 1997) dieser CD-ROM
+ mit Ausgabe 1/1998 der Mitgliedszeitschrift. Exemplare der
+ 5. Auflage (Sommer 1999) knnen Mitglieder fr 3,-- DM beim Verein
+ anfordern.
+ o CTAN/3 - Das TeX-/LaTeX-Archiv von DANTE e.V.: ... ist veraltet
+ (November 1995) und wird nicht mehr angeboten.
+
+* Disketten und andere Medien per Post:
+
+ o Fr Mitglieder ohne Internet-Anschluss bietet DANTE e.V. den Service
+ an, TeX-Software per Disketten oder auf anderen Medien zu verteilen.
+
+
+Auerdem hat DANTE e.V. fr einige Shareware-Angebote Sonderregelungen
+fr seine Mitglieder vereinbart. So wurde beispielsweise fr das
+TeX-Paket `OzTeX' fr MacOS-Rechner die Shareware-Gebhren pauschal fr
+alle Mitglieder bezahlt.
+
+4.2 TeX-Implementierungen (*)
+
+
+4.2.1 Ich suche fr das Betriebssystem XYZ ein mglichst komplettes,
+leicht installierbares TeX-System. (*)
+
+Auf CTAN findet man TeX-Systeme teils fertig installierbar, teils nur
+als Sources in den Verzeichnissen unter ``systems/''. Einige Systeme
+kann man auch auf CD-ROMs finden (siehe Frage 4.1), davon sind einige
+sehr einfach installierbar und dokumentiert, also fr Anfnger ideal. Da
+es der Platz hier nicht zult, auf alle Systeme genauer einzugehen,
+folgt in den Abschnitten 4.2.4ff eine unvollstndige Aufzhlung fr
+verschiedene Betriebssysteme mit einer sehr knappen Beschreibung.
+
+4.2.2 Unix (einschlielich Linux) (*)
+
+
+ web2c:
+ CTAN: systems/web2c/
+ unvollstndiges System, enthlt `nur' den Quellcode der
+ wichtigsten Programme eines TeX-Systems ((ML)TeX, METAFONT,
+ METAPOST, TeX+MF+WEB-Tools, BibTeX, dvicopy u.v.a.); TeX-System
+ ist mit Hilfe von `web2c' relativ einfach auf alle Systeme mit
+ C-Compiler und Unix-hnlicher C-Library portierbar, wobei die
+ aktuelle Version 7.2 schon Amiga-, OS/2- und Windows
+ NT-Untersttzung enthlt.
+
+ teTeX:
+ CTAN: systems/unix/teTeX/2.0/
+ vollstndiges System, ber Skripte automatisch und sehr einfach
+ compilier- und installierbar, fr viele weitverbreitete
+ Unix-Systeme demnchst auch fertige Binaries verfgbar, teTeX v2.0
+ basiert auf der `web2c' Version 7.4.5.
+ Ab der 4. Auflage der CD-ROM `TeX Live' findet man eine Variante
+ von teTeX, die auf web2c v7.3 basiert, in einer von der CD-ROM
+ lauffhigen Version fr viele Unix-Versionen!
+ Eine bequeme Mglichkeit, teTeX mittels WWW-Browser fr diverse
+ Unix-Versionen zu laden, bietet die Seite
+ http://theory.uwinnipeg.ca/search/tetex.html
+
+ NTeX:
+ CTAN: systems/unix/ntex
+ http://www.langbein.org/software/ntex/
+ vollstndiges System, enthlt viele landessprachliche Anpassungen,
+ auch fr weniger verbreitete Sprachen, in neueren Versionen werden
+ neben Linux auch andere Plattformen untersttzt. NTeX v1.x enthlt
+ unrechtmig vernderte, inkompatible CM-Schriften, daher
+ mglichst sofort auf v2.3.2 umsteigen! Das System wurde seit
+ August 1998 nicht mehr gendert.
+
+ VTeX/Lnx:
+ http://www.micropress-inc.com/linux/
+ CTAN: systems/vtex/
+ Ein TeX-System, das unmittelbar PDF- oder PostScript-Ausgabe
+ erzeugt; es ist kostenlos erhltlich und enthlt ein komplettes
+ LaTeX. VTeX/Lnx luft nur unter Linux (x86), nicht unter anderen
+ Unix-Varianten.
+
+
+4.2.3 Windows 3.x/95/98/NT/2000 (*)
+
+
+ fpTeX (Win32-Web2c, auch ``teTeX fr Windows'' genannt):
+ CTAN: systems/win32/fptex/, http://www.fptex.org
+ Basiert auf Web2c Version 7.x. In der aktuellen Version, die auch
+ ab der 6. Auflage der CD-ROM ``TeX Live'' enthalten ist, luft die
+ Installation sehr komfortabel entweder ber eine
+ Standard-Installation oder ber ein ausfhrliches Paketauswahlmen
+ ab. Auf Wunsch werden auch der PostScript-Interpreter
+ Ghostscript/GSView, die Editoren Emacs oder WinEdt sowie weitere
+ ntzliche Software wie die Grafikbibliothek ImageMagick
+ installiert. Weitere Informationen finden sich in der Datei
+ CTAN: systems/win32/fptex/docs/fptex.pdf oder ber die oben
+ angegebene fpTeX-Homepage.
+
+ MikTeX:
+ CTAN: systems/win32/miktex/
+ Fr Windows 95 und NT (auch Versionen fr Power-PC), genaueres
+ unter http://www.miktex.org/ und
+ http://www.esat.kuleuven.ac.be/~minten/NTTeXing/NTTeXing.html
+ sowie im Dokument ``LaTeX, Emacs etc. for your PC''
+ http://www.math.auc.dk/~dethlef/Tips/introduction.html.
+ Eine Installationsbeschreibung eines TeX-Gesamtsystems aus MikTeX,
+ Ghostview und WinEdt fr Einsteiger findet man unter
+ http://www.dante.de/help/documentation/miktex/ und
+ CTAN: info/german/MiKTeX-WinEdt-TrueType-Anleitung/latex.htm Zu
+ MikTeX, Ghostview und Emacs u.a. findet man hier Informationen:
+ http://www.math.auc.dk/~dethlef/Tips/introduction.html
+ LaTeX - ein komplettes Setup unter Windows:
+ http://www.joachimschlosser.de/Informatik/Tips/latexsystem.html
+
+ WinEmTeX (ehemals: tex4win; emTeX fr Windows):
+ http://ipe.et.uni-magdeburg.de/~werner/winemtex.htm
+ Komplette TeX-Distribution fr Windows mit allen notwendigen
+ Teilen des emTeX-Paketes zusammen mit Ghostscript und dem Editor
+ WinEdit von Wilson Windowware, durch Installations-Skript sofort
+ funktionsfhig installierbar; durch Skriptsprache des Editors sind
+ alle TeX-Funktionen (bersetzen, Vorschau usw.) per Menu oder
+ Tastaturkrzel aufrufbar, Syntax-Hervorhebung durch Farbe;
+ integrierte BibTeX-Oberflche, kontextsensitive LaTeX-Hilfe,
+ automatische Fontgenerierung; momentan nur Dokumentation in
+ deutsch. (Die unregistrierte Shareware-Version des Editors ist auf
+ Textlngen von 1000 Zeilen beschrnkt!)
+
+ emTeX:
+ siehe OS/2, MS-DOS
+
+ web2c 7.0 (DJGPP-Port):
+ siehe OS/2, MS-DOS
+
+ BaKoMa TeX:
+ CTAN: nonfree/systems/win32/bakoma/
+ Shareware; vollstndiges TeX-System mit integrierter Umgebung,
+ untersttzt skalierbare Schriften (OpenType, TrueType, PostScript
+ Type-1 und Type-3 inkl. Multiple-Master-Fonts), enthlt
+ erweiterten BaKoMa-Schriftensatz.
+
+ TrueTeX:
+ http://idt.net/~truetex/
+ Kommerzielles TeX-System
+
+ Y&Y TeX:
+ http://www.YandY.com/
+ Kommerzielles TeX-System
+
+ VTeX:
+ http://www.micropress-inc.com/
+ Kommerzielles TeX-System
+
+ Scientific Word/Scientific WorkPlace:
+ Kommerzielles TeX-System fr Windows, Pseudo-WYSIWYG.
+
+
+4.2.4 OS/2, MS-DOS
+
+
+ emTeX:
+ CTAN: systems/msdos/emtex/
+ CTAN: obsolete/systems/msdos/4alltex.zip
+ Vollstndiges System mit vielen Tools, leicht installierbar, viele
+ Erweiterungen (z.B. GUI) von fremden Autoren verfgbar; findet man
+ auf der CD-ROM `4allTeX' in einer von der CD-ROM lauffhigen
+ Version!
+
+ emTeX/TDS:
+ CTAN: systems/os2/emtex-contrib/emtexTDS/
+ Auf emTeX basierende TeX-Distribution fr OS/2, aufgebaut gem
+ dem TDS-Standard. Ein Installationsskript richtet ein
+ betriebsfhiges (La)TeX mit zustzlichen Paketen, Schriften,
+ Anpassung an zahlreiche Sprachen und Untersttzung fr PostScript
+ ein. Die Installation bentigt zustzlich Teile des emTeX-Pakets.
+ Dokumentation in Deutsch und Englisch.
+
+ PubliC (e-)TeX/MF/MP:
+ CTAN: systems/msdos/dostp22/
+ Minimal-Ausstattung an Programmen, Makros und Fonts, dafr voll
+ TDS-kompatibel, enthlt e-TeX, leicht installierbar.
+
+ SbTeX:
+ CTAN: systems/msdos/sbtex/
+
+ web2c-OS/2:
+ CTAN: systems/os2/web2c-6.1/
+ Portierung des `web2c-6.1'-Pakets (siehe Frage 4.2.2, Unix) fr
+ OS/2 (ab Version 2.0), unvollstndiges System, enthlt `nur' den
+ Kern eines TeX-Systems.
+
+ web2c:
+ http://archiv.leo.org/pub/comp/os/dos/gnu/djgpp/v2apps/tex/
+ Portierung von web2c 7.0 fr MS-DOS, basiert auf gcc-Portierung
+ von D.J. Delorie, bentigt Teile des DJGPP-Runtime-Pakets, das
+ auch auf OS/2 und Windows 95/NT luft.
+
+ OS/2 TeX:
+ http://www.tu-darmstadt.de/~kleinboe/g_os2tex.html
+ Shareware (Registrierungsgebhr 70,-- DM), einfach zu
+ installierendes System mit eigenem Installationsprogramm,
+ TeX-Shell mit einfachem Syntax-Highlighting, PM DVI-Previewer,
+ Schriftarten-Server, untersttzt jeden installierten
+ OS/2-Druckertreiber.
+
+ 4allTeX Workbench:
+ siehe Frage 4.3.4
+
+ VTeX/2:
+ http://www.micropress-inc.com/os2/
+ CTAN: systems/vtex/
+ Ein TeX-System, das unmittelbar PDF- oder PostScript-Ausgabe
+ erzeugt; es ist kostenlos erhltlich und enthlt ein komplettes
+ LaTeX. VTeX/2 luft nur unter OS/2, nicht unter MS-DOS und ist
+ nicht identisch mit VTeX fr Windows.
+
+
+4.2.5 OpenVMS
+
+
+ DECUS-TeX:
+ CTAN: systems/OpenVMS/
+ Dieses Verzeichnis enthlt Zip-Archive der Quellen sowie der
+ vorkompilierten Images fr OpenVMS (Alpha und VAX). Makrodateien,
+ Schriften etc. sind aus den anderen Teilen (macros/, fonts/,
+ languages/) des CTAN-Archivs zu besorgen.
+ DECUS-TeX ist eine vollstndige, Ready-to-Run-Verteilung fr
+ OpenVMS (Alpha und VAX). Die Images sind dieselben, wie sie auch
+ von CTAN erhltlich sind. Daneben enthlt die Verteilung die
+ gngigen Formate (Plain, LaTeX, AmS-TeX), sowie XDVI, DVIPS,
+ TEXINDEX und einige andere Programme. Weiterhin sind alle
+ Standard-Schriften (CM, LaTeX, AmS-TeX, EC) enthalten. Der gesamte
+ Umfang betrgt ca. 200MB (inkl. Quellen). DECUS-TeX kann von DECUS
+ Mnchen e.V., Freischtzstr. 91, 81927 Mnchen gegen einen
+ Unkostenbeitrag auf folgenden Medien bezogen werden: Magnetband
+ 6250Bpi, TK50, DAT.
+ DECUS Mnchen e.V. hat die Distribution an DECUS U.S. zur Aufnahme
+ in die DECUS-Library weitergegeben, die seit einiger Zeit zweimal
+ jhrlich auf CD erscheint. Darberhinaus hat DECUS U.S. die
+ Distribution an Compaq (vormals DEC) als Beitrag fr die
+ Freeware-CD weitergeben. Die Freeware-Version unterscheidet siuch
+ nur in dem `Packaging' von der DECUS-Version; auf der Freeware-CD
+ ist _ein_ ZIP-Archiv (VMS-Version von Unzip ist notwendig)
+ vorhanden, whrend DECUS vier Save-Sets verteilt.
+ Die aktuelle Freeware-CD (4.0, Stand Dezember 2000) wird an Kunden
+ zusammen mit der `Consolidated Binary Distribution' ausgeliefert.
+ Daneben ist der Inhalt der Freeware-CD im Internet auf dem
+ WWW-Server von Compaq verfgbar. Einstiegspunkt ist beispielsweise
+ http://www.openvms.compaq.com/.
+
+
+4.2.6 Apple MacOS
+
+Eine gute bersicht ber alle Implementierungen von TeX-Systemen und
+Teilen davon (BibTeX etc.) sowie von Editoren und weiteren Tools fr
+MacOS findet man unter http://www.esm.psu.edu/mac-tex/
+
+ OzTeX:
+ CTAN: systems/mac/oztex/
+ CTAN: nonfree/systems/mac/oztex-german/
+ OzTeX-Homepage: http://www.trevorrow.com/oztex/
+ Teils Shareware, bitte mitgelieferte README-Dateien beachten!
+ (OzTeX-Shareware-Gebhr wurde fr Mitglieder von DANTE e.V.
+ bereits pauschal bezahlt.)
+
+ CMacTeX:
+ CTAN: nonfree/systems/mac/cmactex/
+ CMacTeX-Homepage: http://www.kiffe.com/cmactex.html
+ Shareware. Beruht auf Web2c-7.x. Enthlt u.a. e-TeX, Omega,
+ pdfTeX, 8Bit-BibTeX, untersttzt PS-Schriften wahlweise im pfb-,
+ pfa- oder Mac-Format.
+
+ DirectTeX:
+ CTAN: nonfree/systems/mac/directtex/
+ Teils Shareware, bitte mitgelieferte README-Dateien beachten!
+
+ Textures:
+ Kommerzielles TeX-System, Pseudo-WYSIWYG
+
+
+4.2.7 MacOS X (Unix)
+
+
+ teTeX fr MacOS X:
+ http://www.rna.nl/tex.html,
+ ftp://ftp.nluug.nl/pub/comp/maxosx/tex-gs/,
+ http://darkwing.uoregon.edu/~koch/texshop/tetex.tar.gz
+ vollstndiges teTeX-System (siehe Beschreibung unter Unix/Linux)
+ mit Installationsanleitung und graphischem Frontend TeXShop.
+ TeXShop: http://darkwing.uoregon.edu/~koch/texshop/texshop.html
+
+
+4.2.8 BeOS (Intel/PowerPC):
+
+
+Ausfhrbare Programme - TeX (Web2C http://www.bebits.com/app/1130
+7.2):
+DVI Viewer: http://www.bebits.com/app/1129
+Be-PDF: http://www.bebits.com/app/159
+ http://www.frbug.org/pdf/
+Ghostscript: http://www.bebits.com/app/797
+ http://anobject.com/jehamby/Code/
+
+
+
+4.2.9 Plan 9
+
+
+ TeX fr Plan 9 from Bell Labs:
+ http://plan9.bell-labs.com/plan9dist/TeX.html
+ TeX-System fr Plan 9. Dieses System enthlt die Quellen,
+ ausfhrbare Programme fr x86, Schriften und alle Anpassungen.
+
+
+4.2.10 Amiga
+
+
+ AmiWeb2C:
+ CTAN: systems/amiga/amiweb2c/
+ beruht auf Web2c-7.2, enthlt METAPOST 0.641, e-TeX v2.0,
+ Omega 1.5 und pdfTeX 0.12; das System wird mangels Zeit vom Autor
+ nicht mehr weiterentwickelt.
+
+ PasTeX:
+ CTAN: systems/amiga/pastex/
+ vollstndiges TeX-System; wegen Zeitmangel des Autors nicht mehr
+ weiterentwickelt.
+
+ AmigaTeX:
+ http://www.radicaleye.com
+ kommerzielles TeX-System; ist laut Auskunft auf der angegebenen
+ WWW-Seite nicht mehr verfgbar.
+
+
+4.2.11 Atari ST
+
+
+ Lindner-TeX/Birkhahn-MF:
+ CTAN: systems/atari/lindner-tex/
+
+ CS-TeX:
+ CTAN: systems/atari/cs-tex/
+ veraltetes TeX-System von 1992, neuere Version als MultiTeX
+ kommerziell vertrieben (jedoch mittlerweile auch veraltet)
+
+
+4.2.12 NeXT:
+
+
+ TeX for NEXTSTEP/OpenStep:
+ http://www.mathi.uni-heidelberg.de/~flight/stepTeX/
+
+
+4.2.13 AtheOS:
+
+
+ teTeX:
+ http://www.atheos.cx/download/list.php3?full_desc
+ ftp://atheos.sourceforge.net/pub/atheos/packages/
+ TeX-System fr AtheOS (Binr-Distribution).
+
+
+4.3 Editoren, Frontend-/GUI-Programme (*)
+
+
+4.3.1 Welche Editoren soll ich verwenden? Gibt es graphische
+Benutzungsoberflchen, die den Aufruf der einzelnen Programme
+vereinfachen oder automatisieren?
+
+Grundstzlich sollte man den Editor verwenden, mit dem man am besten
+arbeiten kann. Denn: Man verbringt die meiste Zeit im Editor, nicht nur
+zum Erstellen von (La)TeX-Dokumenten, sondern beim Erstellen jedes
+Textes.
+Die Listen in den folgenden Abschnitten stellen eine unvollstndige
+Auswahl von verfgbaren Bedienumgebungen und Editoren mit
+(La)TeX-Untersttzung dar. Fr die nicht explizit genannten Systeme (wie
+Atari ST) gibt es ebenso an diese Systeme angepate Bedienumgebungen.
+
+4.3.2 Unix (einschlielich Linux) (*)
+
+
+ `Emacs' mit AUCTeX-Mode:
+ Unter X11 und GNU-Emacs 19.* oder 20.* (bzw. XEmacs) hat man
+ Mens, Klammerungstest, sehr mchtige Eingabe-Shortcuts, mit
+ `font-lock' Hervorhebung durch Farbe, Syntax-Check, Aufruf von
+ TeX, Previewer und weiterer Tools etc.
+
+ `xtem':
+ Eine in Tcl/Tk geschriebene, unter X11 laufende Bedienoberflche,
+ von der aus die wichtigsten Programme eines TeX-Systems integriert
+ werden knnen; leicht konfigurierbar und wegen Verwendung von Tcl
+ auch selbst relativ einfach erweiterbar.
+
+ `FTE' - Editor fr Windows 95/98/NT, OS/2, DOS, Linux:
+ Nhere Beschreibung siehe unter `Windows 3.*/95/98/NT'.
+
+ `NEdit':
+ X-Window/MOTIF-basierter Editor mit Syntax-Hervorhebung fr
+ zahlreiche Programmiersprachen darunter auch LaTeX, BibTeX und
+ LyX. Weniger mchtig als Emacs, aber z.B. fr Windows-Umsteiger
+ leichter zu bedienen. Zustzlich zur standardmigen
+ LaTeX-Untersttzung bietet das Paket `NEdit-LaTeX-Extensions'
+ weitere ntzliche Hilfen (AUCTeX-hnlich).
+
+ `Glimmer':
+ An den Gnome-Desktop angepater Editor mit Syntax-Hervorhebung fr
+ zahlreiche Programmiersprachen, darunter auch LaTeX.
+
+ `Kile':
+ Bedienoberflche/Editor mit Syntax-Hervorhebung,
+ Strukturdarstellung, integriertem DVI-Betrachter u.v.a.. Angepat
+ an die KDE-Oberflche (X-Window).
+
+ `Ktexmaker2':
+ Wird jetzt unter dem Namen `Kile' weiterentwickelt.
+
+ `Tk LaTeX Editor':
+ Ein auf Tk basierender Editor mit Syntax-Hervorhebung und vielen
+ anderen Hilfsmittel. Ist vermutlich auf verschiedenen
+ Rechnerplattformen nutzbar.
+
+
+AUCTeX: CTAN: support/auctex/
+S. Kamphausen: XEmacs - Die http://www.skamphausen.de/xemacs/
+Deutschsprachige Einleitung:
+xtem: CTAN: support/xtem_texmenu/
+NEdit: http://nedit.org/
+ CTAN: support/NEdit-LaTeX-Extensions/
+ ftp://humbolt.geo.uu.nl/pub/mirror/NEdit/
+Glimmer: http://glimmer.sourceforge.net/
+Ktexmaker2: http://xm1.net.free.fr/linux/
+Kile: http://xm1.net.free.fr/kile/
+Tk LaTeX Editor: http://conero.lrn.ru/index.php?module=soft
+
+
+
+4.3.3 Windows 3.*/95/98/NT
+
+
+ `NTemacs' - GNU-Emacs mit AUCTeX-Mode fr Win32:
+
+ http://www.gnu.org/software/emacs/windows/ntemacs.html
+ http://www.esat.kuleuven.ac.be/~minten/NTTeXing/NTTeXing.html
+
+
+ enthlt eine FAQ zum GNU-Emacs unter Win32 und Hinweise zur
+ Installation eines vollstndigen TeX-Systems einschlielich eines
+ an TeX angepaten GNU-Emacs unter Win32.
+
+ `WinEdt' - Editor fr Windows 3.11/95/98/NT:
+ Shareware, hat Syntax-Highlighting, stellt Templates etc. fr
+ LaTeX bereit; ist sehr gut auf Nutzerbedrfnisse anzupassen,
+ Support durch den Autor.
+
+ `TeX for Windows' - LaTeX-Editor fr Windows 95/98/NT:
+ Freeware, Formel-Editor, untersttzt LaTeX und BibTeX, Aufruf von
+ LaTeX, dviwin, dvips, ghostview, ...
+
+ `FTE' - Editor fr Windows 95/98/NT, OS/2, DOS, Linux:
+ Frei verfgbar, Syntax-Highlighting; untersttzt neben LaTeX
+ etliche weitere Programmiersprachen. Vielseitig konfigurierbar.
+
+ `WinTeX 2000' - TeX Editor fr Windows 95/98/NT:
+ Hat Office 98 Look-and-Feel, Syntax-Highlighting,
+ Auto-Spell-Check, Thesaurus, BibTeX-Editor, Code-Templates.
+
+ `TeXnicCenter' - Editor und Oberflche fr Windows 95/98/NT:
+ Frei verfgbar (GPL), bietet vielfltige Mglichkeiten, u.a.
+ Syntax-Highlighting, Strukturansicht, Templates, ber Mens
+ vollstndig konfigurierbar.
+
+ `Tcltexed' - Editor und Oberflche:
+ Frei verfgbar (GPL), programmiert unter Verwendung von Tcl/Tk und
+ damit unabhngig vom verwendeten Betriebssytem. Bietet
+ Syntax-Highlighting und gestattet es, externe Programme
+ einzubinden.
+
+ `WinShell':
+ Programm frei verfgbar, Quellen nicht. Untersttzt mehrere
+ Sprachen (englisch, deutsch, franzsisch), Projekte, mehrere
+ Dokumente, Start mit Kommandozeilenargumente, Syntax-Highlighting,
+ Einbindung externer Programme, Lesen von Unix-Dateien u.a.
+
+
+WinEdt: CTAN: nonfree/systems/win32/winedt/
+TeX for http://maitai.wsi.tu-muenchen.de/wheller/
+Windows:
+ (nicht mehr erreichbar)
+FTE: http://fte.sourceforge.net/
+WinTeX 2000: CTAN: nonfree/systems/win32/wintex2000/
+ http://www.tex-tools.de/main.html
+TeXnicCenter: CTAN: systems/win32/TeXnicCenter/
+ http://www.ToolsCenter.org/products/texniccenter/
+Tcltexed: CTAN: support/tcltexed/
+ http://studweb.studserv.uni-stuttgart.de/studweb/users/phy/phy10932/tcltexed.htm
+WinShell: http://www.winshell.de
+
+
+Unter http://home.nexgo.de/itsfd/texwin.htm ist eine bersicht von Free-
+und Shareware-Programmen zum Bearbeiten von TeX-, LaTeX- und
+BibTeX-Dateien zu finden.
+
+4.3.4 MS-DOS
+
+
+ `GNU-Emacs' mit AUCTeX-Mode:
+ einen vollwertigen GNU Emacs 19.34 mit Pull-Down-Mens,
+ Mausuntersttzung und Faces gibt es auch fr MS-DOS; nhere
+ Beschreibung siehe `Unix' (Frage 4.3.2).
+
+ `4allTeX Workbench':
+ Bietet eine einfache, ausreichende Umgebung, in die man sehr
+ einfach den eigenen Editor und andere Programme einbinden kann
+ (nur bis 4. Auflage auch fr MS-DOS; auf der CD-ROM bzw. im Paket
+ `4allTeX').
+
+ `Eddi4TeX':
+ Ist ein spezieller Editor mit Klammerungstest, Syntax-Checks,
+ Online-Hilfe, Hervorhebung durch Farbe etc., der durch eine
+ umfangreiche Makrosprache angepat und erweitert werden kann.
+
+ `TeXshell':
+ Ist eine einfache, einfach anpabare Umgebung, in die der eigene
+ Editor eingebunden werden kann.
+
+ `FTE':
+ Ein Editor fr Windows 95/98/NT, OS/2, DOS, Linux. Nhere
+ Beschreibung siehe unter `Windows 3.*/95/98/NT'.
+
+
+4allTeX: CTAN: obsolete/systems/msdos/4alltex.zip
+ (oder auf CD-ROM)
+Eddi4TeX: CTAN: systems/msdos/e4t/
+TeXshell: CTAN: systems/msdos/texshell/
+
+
+
+4.3.5 OS/2
+
+
+ `GNU-Emacs' mit AUCTeX-Mode:
+ Einen vollwertigen GNU Emacs 19.33 mit Pull-Down-Mens,
+ Mausuntersttzung und Faces gibt es auch fr OS/2; nhere
+ Beschreibung siehe unter `Unix'.
+
+ `EPM' (`Erweiterter Editor', ist bei OS/2 dabei):
+ PM-Anwendung, z.T. schon an TeX angepat (z.B.
+ Syntax-Highlighting). Zustzliche Pakete erweitern den Editor zu
+ einer integrierten TeX-Umgebung und sind fr emTeX vorbereitet:
+
+ * epmTeX: Menuntersttzung fr TeX, DVI-Treiber usw.,
+ LaTeX-Syntaxassistent, vielfltige Optionen.
+ * EPM TeX Front End: weiterentwickelte, neuere Variante von
+ epmTeX, untersttzt PostScript, einfache Installation und
+ Handhabung, deutschsprachige Anleitung.
+
+
+ `FSS TeXeditor':
+ WPS/PM-Programm, fr die Verwendung von emTeX (optional zusammen
+ mit dvips/Ghostscript) vorkonfiguriert, verwaltet mehrere
+ TeX-Konfigurationen, mehrere Dateifenster, TeX-Befehle ber Mens
+ verfgbar, Textbausteine, eigene Makros erstellbar etc. (Freeware)
+
+ `FTE' - Editor fr Windows 95/98/NT, OS/2, DOS, Linux:
+ Nhere Beschreibung siehe unter `Windows 3.*/95/98/NT'.
+
+
+epmTeX: CTAN: systems/os2/epmtex/
+EPM TeX Front End: CTAN: systems/os2/epmtfe/
+FSS TeXeditor: CTAN: systems/os2/texed/
+
+
+
+4.3.6 Apple MacOS:
+
+Eine gute bersicht ber alle Implementierungen von TeX-Systemen, Teilen
+davon (BibTeX etc.) sowie von Editoren und weiteren Tools fr MacOS
+findet man unter http://www.esm.psu.edu/mac-tex/
+
+ `Alpha':
+ Ist ein Texteditor mit sehr guter Untersttzung fr LaTeX.
+
+ `iTeXMac':
+ Ist Texteditor und Bedienoberflche zu TeX (teTeX-basierend). Es
+ ist frei verfgbar (GPL).
+
+
+Alpha: CTAN: nonfree/systems/mac/support/alpha/
+ (im Unterverzeichnis ``contrib/'' findet man viele
+ ntzliche Dinge und Anpassungen fr Alpha)
+iTeXMac: http://www.u-bourgogne.fr/monge/j.laurens/iTeXMac/
+
+
+
+4.3.7 BeOS (Intel/PowerPC):
+
+
+ `TexEdit':
+ TeX-syntax-coloring text editor.
+
+
+TexEdit: http://www.beatjapan.org/mirror/www.be.com/beware/Productivity/TexEdit.html
+
+
+
+4.3.8 Amiga:
+
+
+ `MEmacs':
+ Ist eine abgespeckte Amiga-Version des GNU-Emacs, die im OS-Paket
+ enthalten ist.
+
+ `GoldED' v6.x:
+ Editor, der TeX- bzw. LaTeX-Befehle entsprechend erkennt und viele
+ Hilfestellungen und Arbeitserleichterungen liefert, ber eine
+ leistungsfhige ARexx-Schnittstelle kann TeX bzw. LaTeX,
+ DVI-Previewer und Druckertreiber per Mausklick angesteuert werden.
+
+
+GoldED: http://www.members.tripod.com/golded
+
+
+
+4.3.9 Gibt es ein WYSIWYG-Frontend fr TeX? Ist damit ein interaktives
+Gestalten mglich?
+
+Schon seit Jahren gibt es `Textures'auf MacOS-Rechner. Mit `Scientific
+Word/Workplace' kam vor einiger Zeit ein quivalent fr Windows (PC) auf
+den Markt. Beide Systeme haben gemein, da sie kommerziell vertrieben
+werden und da Dokumente, Fonts u.. mit wenigen Einschrnkungen mit
+anderen TeX-Systemen ausgetauscht werden knnen.
+
+ Lyx:
+ `Lyx' verwendet und legt Dokumente in normalen Textdateien ab. Es
+ verwendet einen eigenen Markup-Stil mit eigenen
+ Markup-Anweisungen, die als LaTeX-Paket in der Datei ``lyx.sty''
+ mitgeliefert werden. Lyx-Dokumente knnen deshalb auch mit (La)TeX
+ bersetzt und Teile daraus in eigene Dokumente eingebunden werden.
+ Vorhandene TeX-Dateien knnen durch einen Import-Filter eingelesen
+ werden. Ebenso knnen Lyx-Dateien nach TeX, PDF, PostScript und
+ ASCII exportiert werden. Lyx gibt es fr Unix/linux, Win32, OS/2
+ und MacOS X. Mehr Informationen, Source bzw. Binaries fr `Lyx'
+ und der bentigten Bibliothek `XForms' ber
+
+ http://www.lyx.org/
+ ftp://ftp.lyx.org/pub/lyx/
+
+
+ Seit April 1998 gibt es eine an den KDE Desktop (Unix) angepate
+ Variante unter dem Namen `KLyx', die mit KDE ausgeliefert wird,
+ jedoch nicht mit Lyx identisch ist.
+
+ TeXmacs:
+ `TeXmacs' ist ein Texteditor mit WYSIWYG-hnlicher Darstellung
+ unter Beibehaltung logischer Strukturen. Einige der Funktionen
+ sind denen des Editors Emacs nachempfunden, wobei die Bedienung
+ erheblich einfacher ist. `TeXmacs' ist auf Systemen mit X-Window
+ lauffhig und fertige Binaries fr Linux und Solaris sind
+ verfgbar. Zur Darstellung werden direkt TeX-Fonts verwendet.
+ Auerdem existiert eine Schnittstelle zu dem
+ Computer-Algebrasystem pari.
+
+ http://www.math.u-psud.fr/~anh/TeXmacs/TeXmacs.html
+ CTAN: systems/unix/TeXmacs
+
+
+
+ e:doc:
+ `e:doc' ist ein Wordprocessor, der eine WYSIWYG-hnliche
+ Darstellung bei Beibehaltung logischer Strukturen bietet. Er ist
+ unter Verwendung von `Perl' und `Tk' geschrieben und somit auf den
+ meisten Betriebssystemen lauffhig. Derzeit ist das Projekt in
+ einer frhen Phase.
+
+ http://members.magnet.at/hfbuch/edoc/
+
+
+
+ THOT:
+ `THOT' ist ein Editor, der es gestattet, ein Dokument anhand
+ seiner Struktur einzugeben bzw. zu modifizieren. Numerierung,
+ Referenzen, Index, Rechtschreibkorrektur u.a. werden untersttzt.
+ Ausgabeformate sind PostScript, LaTeX or HTML. Das Programm ist
+ frei verfgbar und kann unter Betriebssystemen mit
+ X-Window-Oberflche genutzt werden.
+
+ http://www.inrialpes.fr/opera/Thot.en.html
+
+
+
+ Cicero:
+ `Cicero' ist ein Wordprocessor, der in C++ in Verbindung mit
+ TCL/TK geschrieben ist und unter X-Window luft, Ausgabe kann in
+ LaTeX und mit SGML-Tools aka Linuxdoc-SGML erfolgen. Luft unter
+ Linux, evtl. auch auf anderen Unix-Systemen. Cicero ist momentan
+ noch im Entwicklungsstadium. Mehr Informationen auf der WWW-Seite
+
+ http://zeus.informatik.uni-frankfurt.de/~weis/cicero.html
+
+
+
+ SciTeXt:
+ `SciTeXt' ist ein Wordprocessor, der zu Anfang der Entwicklung
+ unter X/Motif lief. Zur Zeit wird das Programm nach Java portiert
+ und soll somit auf den meisten Rechnersystem lauffhig sein.
+ Aufgrund des sehr frhen Entwicklungsstadiums ist noch keine
+ verwendbare Version verfgbar. Mehr Informationen auf der
+ WWW-Seite
+
+ http://www.uni-paderborn.de/~SciTeXt/
+ (Seit 1997 unverndert.)
+
+
+
+
+4.3.10 Gibt es bequeme Editoren fr
+BibTeX-Literaturdatenbankdateien? (*)
+
+Die folgende Liste mit einigen Editoren und Frontend-Programme, zur
+Eingabe und Manipulation von BibTeX-Literaturdatenbanken, ist noch sehr
+unvollstndig:
+
+ `GNU-Emacs'/`XEmacs' mit BibTeX-Mode:
+ Der Editor Emacs ist fr Unix, MS-DOS, OS/2, Win32, Amiga und
+ MacOS verfgbar. Quellenangaben in Abschnitt 4.3.
+
+ `BibGene':
+ Eine BibTeX-kompatible Literaturverwaltung fr MacOS. Importiert
+ Dateien im BibTeX-Format, exportiert BibTeX-, LaTeX-, RTF- und
+ HTML-Dateien.
+
+ `bibview':
+ Fr Linux und andere Unix-Versionen.
+
+ `Pybliographer':
+ Python/PyGTK-basiert, daher fr Linux, andere Unix-Versionen und
+ sonstige Betriebssysteme, auf denen Python und PyGTK verfgbar
+ ist. Liest und schreibt auch die Formate Ovid, Refer und hat eine
+ direkte Schnittstelle zu Medline. Deutsche Sprachanpassung,
+ aufgrund interner bersetzung ohne LaTeX-Kenntnisse nutzbar.
+
+ `SIXPACK':
+ Zum Editieren, Konvertieren (BibTeX-Format, refer, endnote, tib,
+ medline, html u.v.a.) und Verwalten von Literaturreferenzen. Fr
+ Linux und andere Unix-Versionen.
+
+ `gBib':
+ Literaturverwaltung angepat an den Gnome-Desktop und LyX (siehe
+ Abschnitt 4.3.9). Fr Linux und andere Unix-Versionen.
+
+ `tkbibtex':
+ Auf Tcl/Tk basierender Editor und Browser fr BibTeX-Dateien.
+ Verwendbar unter jedem Betriebssystem mit installiertem Tcl/Tk.
+
+ `BibDB':
+ BibDB ist ein Programm zum Erzeugen und Verwalten von
+ Literaturreferenzen. BibDB verwendet das BibTeX-Format. Es
+ existieren Versionen fr DOS und Windows.
+
+ `Barracuda':
+ Barracuda ist ein Verwaltungsprogramm fr BibTeX-Dateien. Es
+ bentigt die Qt-Bibliotheken, die unter Linux verfgbar sind.
+
+ `scatman':
+ Mit dem Programm `scatman' lassen sich Literaturdatenbanken
+ erstellen und in das BibTeX-Format exportieren. Auch der
+ umgekehrte Weg ist mglich. Das Programm ist Shareware und luft
+ unter Win32.
+
+ `synapsen':
+ Das Tool `synapsen' ist ein in Java geschriebener, hypertextueller
+ Zettelkasten mit einer umfassenden BibTeX-Schnittstelle.
+
+ `JBibtexManager':
+ Ein ebenfalls in Java geschriebenes und damit
+ plattformunabhngiges frei verfgbares Programm.
+
+
+Ralph Sontag:
+BibTeX-Frontends http://archiv.tu-chemnitz.de/pub/2001/0013/data/
+unter Unix:
+bibview: CTAN: biblio/bibtex/utils/bibview-2.0/
+BibGene: http://www.ics.uci.edu/~eppstein/bibs/bibgene
+Pybliographer: http://www.gnome.org/pybliographer/
+ ftp://ftp.gnome.org:21/pub/GNOME/stable/sources/pyblio/
+SIXPACK: http://www.santafe.edu/~dirk/sixpack/
+gBib: http://gbib.seul.org/
+tkbibtex: http://www.cat.csiro.au/cmst/staff/pic/tkbibtex.html
+BibDB: http://www.mackichan.com/BibDB/default.htm
+ CTAN: support/bibdb/
+Barracuda: http://barracuda.sourceforge.net/
+scatman: http://www.ifs.tuwien.ac.at/~aschatt/
+synapsen: http://www.verzetteln.de/synapsen/
+JBibtexManager: http://csb.stanford.edu/nbatada/JBibtexManager/
+
+
+
+--- DE-TeX-FAQ Ende Teil 4 ---
diff --git a/help/de-tex-faq/part5 b/help/de-tex-faq/part5
new file mode 100644
index 0000000000..348d40755d
--- /dev/null
+++ b/help/de-tex-faq/part5
@@ -0,0 +1,998 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.rediris.es!irazu.switch.ch!switch.ch!news-fra1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 5 of 11)
+Supersedes: <de-tex-faq-5-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:16 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 969
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-5-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975397 889 134.100.9.52 (19 Sep 2003 12:43:17 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:17 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117403 de.answers:9380 news.answers:258269
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part5
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 5 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+5 TeX, LaTeX, Makros etc. (I)
+
+
+5.1 LaTeX - Grundlegendes
+
+
+5.1.1 Was bentige ich, wenn ich von LaTeX 2.09 auf LaTeX2e umsteigen
+bzw. eine neuere LaTeX-Version installieren will?
+
+Grundstzlich sollte man sich beim Umstieg von 2.09 oder beim Update
+einer lteren 2e-Version immer die komplette LaTeX-Distribution im
+Verzeichnis ``base'' besorgen und installieren, nie einzelne Dateien
+oder nur einzelne Class-Dateien. Nach dem Entpacken der Distribution und
+Installation der einzelnen Dateien ist ein neues Format zu generieren.
+Die Anleitung ``install.txt'' enthlt genauere Informationen und
+wichtige Hinweise - bitte durchlesen!
+
+ Notwendig:
+
+
+ * alle Dateien im Verzeichnis ``base''.
+ * alle Zusatzpakete wie `graphics' und damit alle Dateien in den
+ Verzeichnissen unter dem Verzeichnis ``required''.
+ * die zustzlichen CM-Schriften `cmmib' und `cmbsy' in den
+ Designgren 5, 6, 7, 8 und 9 Punkt.
+
+
+ Optional, da schon in ``base'' enthalten:
+
+
+ * Will man sich, insbesondere auf langsameren Rechnern, das
+ Entpacken der dtx-Dateien in ``base'' sparen, bentigt man noch
+ zustzlich die Dateien im Verzeichnis ``unpacked''.
+ * Ebenso befindet sich im Verzeichnis ``doc'' die schon
+ formatierte Dokumentation, also die Dateien
+ ``base/???guide.tex''.
+
+
+
+base: CTAN: macros/latex/base/
+ CTAN: macros/latex/required/
+line/lcircle/lasy: CTAN: fonts/latex/mf/
+ CTAN: fonts/latex/tfm/
+cmmib/cmbsy: CTAN: fonts/amsfonts/sources/extracm/
+ CTAN: fonts/amsfonts/tfm/
+ oder
+ CTAN: fonts/cm/sauter/
+optional: CTAN: macros/latex/unpacked/
+ CTAN: macros/latex/doc/
+
+
+
+5.1.2 Ich habe gehrt, da es fr meine LaTeX-Versionen Patches gibt.
+Welche Dateien bentige ich, was mu ich tun?
+
+Fr jeden LaTeX-Patch bentigt man immer zumindest die Datei
+``patches.txt''
+. Sie beschreibt genau, welche weitere Dateien man noch zu einem
+_kompletten_ Patch bentigt. In vielen Fllen gibt es neben der Datei
+``ltpatch.ltx''
+, die LaTeX-Kernel-Patches enthlt, noch neue Versionen weiterer
+Dateien! Nheres in
+``patches.txt''
+.
+Nachdem man die Dateien geholt und installiert hat, mu ein neues Format
+erstellt und installiert werden, damit die Patches in ``ltpatch.ltx''
+aktiv werden. Zur Kontrolle: Danach sollte beim Formatieren eines
+Dokuments nach der Meldung `LaTeX2e <1999/06/01>' noch der Zusatz `patch
+level X' erscheinen, wobei `X' mit dem installierten Patch
+bereinstimmen mu.
+
+patches.txt: CTAN: macros/latex/base/patches.txt
+
+
+
+5.1.3 Was kann ich mit einer Datei mit Endung `.dtx' anfangen? Bentige
+ich dazu auf alle Flle LaTeX?
+
+Dateien mit `.dtx' sind sogenannte `docstrip archive files', also ein
+Archiv, aus dem man mit dem Programm `docstrip' verschiedene Dateien
+entpacken kann. Zum Entpacken bentigen Sie nur die Datei
+``docstrip.tex''
+ oder
+``docstrip.dtx''
+ und das Programm TeX. ``docstrip.tex'' knnen Sie mit LaTeX 2.09,
+LaTeX2e und auch mit Plain-TeX verwenden.
+Wie Sie eine `.dtx'-Datei entpacken mssen, sollten Sie aus einer
+Beschreibung zu Beginn der `.dtx'-Datei oder einer separaten
+README-Datei entnehmen knnen. Existiert eine gleichnamige Datei mit
+Endung `.ins', so knnen Sie in den meisten Fllen das `.dtx'-Archiv
+``file.dtx'' mit ``tex file.ins'' entpacken. In der Regel erzeugt dieser
+Aufruf eine oder mehrere `.sty'-Dateien sowie weitere Hilfs- und
+Beispieldateien. Nheres entnehmen Sie bitte der Beschreibung des
+Archivs.
+Die Dokumentation eines Pakets und der Makros sind ebenso in einem
+`.dtx'-Archiv enthalten. Zum Formatieren dieser Dokumentation bentigen
+Sie jedoch ein installiertes LaTeX2e - fr einige ltere Archive reicht
+auch noch das alte LaTeX 2.09. blicherweise kann die Dokumentation
+(`.dvi'-Datei) durch ``latex file.dtx'' oder ``latex file.drv'' erzeugt
+werden.
+Ein Befehlsindex eines Paketes kann i.d.R. durch
+
+ makeindex -s gind.ist file
+
+und einen anschlieenden erneuten LaTeX-Lauf erzeugt werden.
+Bei der Erzeugung der Dokumentation wird der dokumentierte Quellcode
+meist nicht aufgenommen; um ihn einzuschlieen, kann vor dem LaTeX-Lauf
+im aktuellen Verzeichnis eine Datei ``ltxdoc.cfg'' angelegt werden, die
+die folgende Zeile enthlt:
+
+ \AtBeginDocument{\AlsoImplementation}
+
+Nheres ist, falls vorhanden, der mitgelieferten Beschreibung des
+Archivs zu entnehmen.
+Hinweis: Mit LaTeX ab Dezember 1995 wurde eine Version des Tool
+``docstrip.dtx'' verteilt, das gleichzeitig mehrere Dateien aus einem
+Archiv entpacken kann und damit um einiges schneller ist. Deshalb lohnt
+es sich, wenn Sie eine ltere Version benutzen, diese durch die neue
+Version zu ersetzen.
+
+docstrip: CTAN: macros/latex/base/docstrip.dtx
+ CTAN: macros/latex/base/docstrip.ins
+ (Bestandteil von LaTeX, kann aber auch mit Plain-TeX
+ verwendet
+ werden!)
+
+
+5.1.4 Wie installiert man am besten ein neues Paket, eine neue Klasse
+oder eine neue Schrift in einem bestehenden TeX-System?
+
+Aktuelle TeX-Systeme legen alle Dateien in einer hierarchischen Struktur
+gem dem TeX-Directory-Structure-Standard (TDS, siehe Frage 3.1.7) an.
+Das Wurzelverzeichnis eines solchen Baumes lautet meist ``texmf''. Unter
+teTeX, fpTeX und anderen TeX-Systemen werden die Suchpfade in der Datei
+``texmf.cnf'' angegeben, deren Ort man mit ``kpsewhich texmf.cnf''
+herausfinden kann.
+Fr nachtrglich installierte Pakete empfiehlt es sich, diese in einer
+eigenen lokalen Verzeichnishierarchie zu installieren (beispielsweise
+unter dem Verzeichnis ``texmf.local'', siehe Variable TEXMFLOCAL in
+``texmf.cnf'').
+Besteht ein LaTeX-Paket nach dem eventuell notwendigen Entpacken der
+dtx-Dateien aus einer Einzeldatei, so wird diese in der TDS-Hierarchie
+in ``texmf.local/tex/latex/misc/'' abgelegt. Gehren zu dem Paket
+mehrere sty-, cls-, fd- oder hnliche Dateien, so werden diese in ein
+neu erzeugtes Verzeichnis unter ``texmf.local/tex/latex/_Paketname_''
+verschoben.
+Schriften, Dokumentation, BibTeX-Dateien, dvips-Konfigurationsdateien
+u.. werden analog gem TDS in entsprechende Unterverzeichnisse unter
+``texmf.local'' verschoben. Nheres sollte in der README-Datei des
+Pakets erlutert sein.
+Zum Abschluss darf man nicht vergessen, die sogenannte
+_Filename-Database_ auf den aktuellen Stand zu bringen, da sonst die neu
+installierten Dateien nicht gefunden werden. Nheres finden Sie in der
+Dokumentation Ihres TeX-Systems und unter Frage 8.5.10.
+Einige TeX-Systeme bieten ein Konfigurations-Werkzeug, um zustzliche
+Pakete nachtrglich zu installieren oder vorhandene Pakete zu
+aktualisieren. Unter fpTeX geht dies ber das Setup-Men, unter MikTeX
+verwendet man das Options-Tool. Beide sorgen nach der nderung
+automatisch fr die Aktualisierung der Dateinamens-Datenbank.
+
+Managing a one-person TeX http://www.ctan.org/installationadvice/
+system:
+
+
+
+5.1.5 Wie gehe ich am besten vor, wenn ich eine bestehende LaTeX-Klasse
+ndern bzw. an meine eigenen Vorgaben anpassen will?
+
+Statt von einer bestehenden Klasse wie ``article.cls'' eine Kopie unter
+eigenem Namen, hier als Beispiel ``detexfaq.cls'', anzulegen, empfiehlt
+es sich, eine schon bestehende Klasse zu laden und anschlieend alle
+notwendigen nderungen durchzufhren. Hierzu bietet LaTeX eine Reihe von
+Mglichkeiten, die in der Dokumentation fr Klassen-Autoren
+``clsguide.tex'' beschrieben sind. Als einfaches Beispiel htte damit
+die neue Klasse ``detexfaq.cls'', in der als Standard-Optionen
+`11pt,a4paper' verwendet werden und die beiden Pakete `german' und
+`remreset' bereits implizit geladen werden, folgendes Aussehen:
+
+ %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% CUT HERE
+ %% detexfaq.cls -- DE-TeX-FAQ's modified ``article.cls''
+ \NeedsTeXFormat{LaTeX2e}\relax
+ \ProvidesClass{detexfaq}[2000/05/11 Article Class from DE-TeX-FAQ]
+ %% Lade nun ``article.cls'', wobei als Default-Optionen ``11pt'' und
+ %% A4-Papierformat als Default gesetzt werden (fuer diese muss
+ explizit
+ %% eine Deklaration hier vorhanden sein) und alle weiteren vom Autor
+ %% gegebenen Optionen einfach `durchgereicht' werden:
+ \DeclareOption{a4paper}{\PassOptionsToClass{\CurrentOption}{article}}
+ \DeclareOption{11pt}{\PassOptionsToClass{\CurrentOption}{article}}
+ \DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+ \ExecuteOptions{a4paper,11pt}
+ \ProcessOptions\relax
+ \LoadClass{article}
+ %% Ab hier kann man Aenderungen an den Makros der geladenen Klasse
+ %% durchfuehren (bitte mit \renewenvironment oder \renewcommand!),
+ %% Pakete hinzuladen und/oder eigene Anweisungen und Umgebungen
+ %% definieren:
+ \RequirePackage{german}
+ \RequirePackage{remreset}
+ %% Schliesslich wird die Klassendatei `sauber' beendet':
+ \endinput
+ %% End of ``detexfaq.cls''
+ %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% CUT HERE
+
+Diese Vorgehensweise hat einige Vorteile. So bleibt die eigene
+Klassendatei relativ klein und enthlt nur die notwendigen nderungen
+und Ergnzungen. ndert sich an der verwendeten Klasse etwas, z.B.
+werden Fehler korrigiert, so sind in den meisten Fllen keinerlei
+nderung an der eigenen Klassendatei zum Nachvollziehen dieser
+nderungen notwendig. Daneben dokumentiert man explizit, von welcher
+Klasse und Versionsnummer man als Basis ausgegangen ist, zumal diese
+Klasse und alle geladenen Pakete mit ihren Versionsnummern bei einem im
+Dokumentkopf eingefgten \listfiles auftauchen.
+
+clsguide.tex: CTAN: macros/latex/base/
+
+
+
+5.1.6 Wie kann ich unter LaTeX eine Anweisung mit optionalem Parameter
+definieren?
+
+In LaTeX kann man mit den Anweisungen \newcommand, \renewcommand,
+\newenvironment und \renewenvironment eigene Anweisungen und Umgebungen
+definieren, die einen optionalen Parameter als erstes Argument besitzen.
+Nhere Informationen finden sich in der Dokumentation fr Autoren
+``usrguide.tex''.
+
+usrguide.tex: CTAN: macros/latex/base/
+
+
+
+5.1.7 Wie erkenne ich bei einer Anweisung mit optionalem Parameter, ob
+dieser vom Autor angegeben wurde?
+
+Mit Hilfe des im Paket `ifthen' definierten Vergleichs \equal kann man
+das optionale Argument mit dem voreingestellten Wert vergleichen. Das
+folgende Beispiel geht davon aus, da der voreingestellte Wert leer sein
+soll:
+
+ \usepackage{ifthen}
+ \newcommand{\meineanweisung}[2][]{% #1 = optional, #2 = notwendig
+ \ifthenelse{\equal{#1}{}}{%
+ % Autor hat kein oder leeres optionales Argument angegeben
+ }{%
+ % Autor hat optionales Argument angegeben
+ }}
+
+
+ifthen: CTAN: macros/latex/base/
+
+
+
+5.1.8 Wie kann ich in LaTeX eine Anweisung mit mehr als einem optionalen
+Parameter definieren?
+
+Mit \newcommand kann man nur ein Makro mit einem einzigen optionalen
+Parameter definieren. Will man ein Makro mit mehr als einem optionalen
+Parameter definieren, so mu man hierzu mehrere Makros mit jeweils einem
+optionalen Parameter definieren, die den Wert des Parameters
+zwischenspeichern und das nchste Makro aufrufen.
+Hier ist ein Beispiel fr ein Makro \cubic[a][b][c]{d} mit drei
+optionalen Argumenten:
+
+ \newcommand{\erstesargument}{}
+ \newcommand{\zweitesargument}{}
+
+ \newcommand{\cubic}[1][a]{% erstes optionales Argument
+ \begingroup % Definitionen von \...argument lokal halten
+ \renewcommand{\erstesargument}{#1}% opt. Argument speichern
+ \cubicZwei}
+ \newcommand{\cubicZwei}[1][b]{% zweites optionales Argument
+ \renewcommand{\zweitesargument}{#1}% opt. Argument speichern
+ \cubicDrei}
+ \newcommand{\cubicDrei}[2][c]{% drittes opt. + notwendiges Argument
+ \({\erstesargument}x^3+{\zweitesargument}x^2+#1x+#2\)%
+ \endgroup}
+
+Eine weitere Mglichkeit bietet das Paket `twoopt':
+
+ \newcommandtwoopt{\Cmd}[3][DefaultA][DefaultB]{Args: #1, #2, #3}
+
+In Anlehnung an die Standard-LaTeX-Definitionen existieren auch die
+Anweisungen \renewcommandtwoopt und \providecommandtwoopt.
+
+twoopt: CTAN: macros/latex/contrib/oberdiek/
+
+
+
+5.1.9 Wie kann ich innerhalb des optionalen Arguments einer Anweisung
+zustzliche eckige Klammern, beispielsweise die eines optionalen
+Arguments einer anderen Anweisung, verwenden?
+
+Im Unterschied zu den geschwungenen Klammern {...}, die immer paarweise
+und korrekt geschachtelt werden mssen, sucht LaTeX bei eckigen Klammern
+einfach nach der nchsten schlieenden eckigen Klammer ], ohne auf
+korrekte Schachtelung dieser Klammern zu achten. Um dies zu verhindern,
+mu man einfach innerhalb der eckigen Klammern [...] ein geschweiftes
+Klammerpaar einfgen, wie dies hier als Beispiel fr \twocolumn gezeigt
+wird:
+
+ \twocolumn[{ ... \sqrt[3]{x^2} ... }]
+
+
+5.2 LaTeX - Probleme beim Umstieg von LaTeX 2.09
+
+
+5.2.1 Anweisungen wie \tenrm, \twlrm, \fivrm etc., die von einigen
+Paketen wie PiCTeX verwendet werden, sind nicht mehr definiert. Was mu
+ich da ndern?
+
+Diese Namen fr Schriften wurden nie dokumentiert und sollten im alten
+LaTeX 2.09 nur LaTeX-intern verwendet werden. Da das Fontauswahlschema
+namens NFSS2 in LaTeX2e komplett neu geschrieben wurde, sind diese
+ehemals internen Namen nicht mehr vorhanden. Es ist daher am besten,
+diese alten Pakete so umzuschreiben, da diese internen Schriftnamen
+nicht mehr verwendet werden. In der Zwischenzeit kann man mit Hilfe des
+Paketes `rawfonts' diese Namen nachdefinieren, wie z.B. mit
+
+ \usepackage[only,fivrm]{rawfonts}
+
+fr PiCTeX.
+
+rawfonts.sty: CTAN: macros/latex/required/
+
+
+
+5.2.2 Beim Umstieg von LaTeX 2.09 mit NFSS (Version 1) auf LaTeX2e
+ndert sich auch das Verhalten der Anweisungen \rm, \bf, \it etc. auf
+das Verhalten des Original-LaTeX 2.09. Wie bekomme ich das alte
+inkompatible Verhalten von NFSS Version 1?
+
+Mit dem Paket `newlfont' erhlt man das Verhalten von NFSS v1, ohne da
+man in den meisten Fllen das Dokument ndern mu:
+
+ \usepackage{newlfont}
+
+Fr neue Dokumente sollte man jedoch besser gleich die neuen Anweisungen
+\textrm{...}, \textbf{...}, \textit{...} etc. verwenden. Diese
+Anweisungen haben darber hinaus den Vorteil, da eine eventuell
+notwendige `italic correction' automatisch eingefgt wird.
+
+newlfont.sty: CTAN: macros/latex/required/
+
+
+
+5.2.3 Einige mathematische Symbole (\Box, \lhd, \leadsto, \Join, \mho,
+\sqsubset etc.) sind nicht mehr definiert - wieso?
+
+Die LaTeX-Symbolschriften `lasy10' und `lasyb10' enthalten nur sehr
+wenige relativ selten benutzte Symbole. Daher werden diese Schriften in
+LaTeX2e nicht mehr standardmig geladen, sondern mssen vom Benutzer
+durch Laden von `latexsym' aktiviert werden:
+
+ \usepackage{latexsym}
+
+
+5.2.4 Kann es sein, da es in LaTeX2e den Parameter \footheight und die
+internen Parameter \@maxsep und \@dblmaxsep nicht mehr gibt? Gibt es
+einen Ersatz?
+
+Der Parameter \footheight und die internen Parameter \@maxsep und
+\@dblmaxsep wurden in LaTeX 2.09 nie ausgewertet. Deshalb wurden sie in
+LaTeX2e entfernt, um die dadurch gesparten Lngenregister fr andere
+Zwecke einsetzen zu knnen. Zur Anpassung von alten Dokumentstilen an
+LaTeX2e kann man daher eine Zuweisung an diese Parameter einfach
+ersatzlos streichen.
+
+5.2.5 Mit lteren Dokumentklassen bekomme ich den Fehler `! Undefined
+control sequence.' oder `! LaTeX Error: \mit undefined.' fr die
+Schriften \mit und \cal. Wieso?
+
+Bis LaTeX2e <1994/12/01> wurden \cal und \mit im Kernel definiert. Weil
+diese Definitionen aber in jeder Standard-Dokumentklasse durch robustere
+Varianten ersetzt werden, hat das LaTeX-Team beschlossen, \cal und \mit
+nicht mehr im Kernel vorzudefinieren. Damit ist es aber erforderlich,
+da alle Dokumentklassen, die \cal und \mit nicht definieren oder mit
+\renewcommand umdefinieren, angepat werden mssen. Bei den
+Standard-Dokumentklassen hat das niemand bemerkt, da die notwendigen
+Anpassungen dieser Dateien automatisch mit einer neuen LaTeX-Version
+mitinstalliert werden.
+
+5.3 (Silben-)Trennung, Absatz-, Seitenumbruch
+
+
+5.3.1 Wie kann ich LaTeX an die neue deutsche Rechtschreibung anpassen?
+Gibt es Trennmuster fr die neuen Trennregeln?
+
+Die ``alten'' Trennmuster wurden von Hand so angepat, da die neuen
+Trennregeln beachtet werden, wobei die Trennung weiterhin eher nach
+Wortherkunft und nicht nach strikter Silbentrennung, die ebenfalls
+erlaubt ist, erfolgt. Diese Trennmuster sind in der Datei
+``dehyphn.tex'' (vormals ``gnhyph01.tex'') verfgbar. Um diese
+Trennmuster nutzen zu knnen, bentigt man ``german.sty'' ab
+Version 2.5e.
+
+dehyphn: CTAN: language/hyphenation/dehyphn.tex
+german.sty: CTAN: language/german/
+
+
+
+5.3.2 Warum trennt (La)TeX Worte mit Umlauten nicht oder nicht korrekt?
+
+Wie TeX Worte mit Umlauten trennt, hngt davon ab, ob die verwendete
+Schrift Umlaute als eigene Lettern enthlt und ob man auf diese Lettern
+durch entsprechende Paket-Deklarationen beim Setzen eines Textes auch
+zugreift.
+Bei den alten CM-Schriften mu TeX Umlaute aus einem Buchstaben und
+einem Akzent zusammenbasteln, da diese keine Lettern fr Umlaute
+enthalten. Diese Akzent-Konstruktion irritiert TeXs Trennalgorithmus,
+und so trennt TeX nur den Wortteil bis zum ersten Umlaut. Im Paket
+`german' und _einigen_ Babel-Versionen wird durch einen aus dem TeXbook
+(Anhang D, S. 394, \allowhyphens) entnommenen Trick erreicht, da alle
+Wortteile zwischen den Umlauten einzeln getrennt werden. Bei dieser
+Vorgehensweise werden nicht alle Trennstellen gefunden oder es treten
+teilweise falsche Trennungen (Bsp.: "ubert-ragen statt "uber-tra-gen)
+auf.
+Abhilfe schaffen nur Schriften, die die Umlaute und andere akzentuierte
+Zeichen als einzelne Lettern enthalten. Ein Beispiel hierfr sind alle
+T1-kodierten Schriften, darunter die EC-Schriftfamilie (siehe Frage
+10.1.3) und die T1-kodierten PostScript-Schriften. Unter neueren
+Versionen von LaTeX und `german.sty' bzw. Babel lassen sich T1-kodierte
+Schriften recht einfach durch die Deklaration
+
+ \usepackage[T1]{fontenc}
+
+in der Prambel des Dokuments verwenden.
+
+5.3.3 Wie kann ich Trennungsausnahmen mit Umlauten in \hyphenation
+verwenden?
+
+Auch hier gilt, da man in \hyphenation in den Trennungsausnahmen nur
+Zeichen verwenden kann, fr die auch Lettern in der momentan benutzten
+Schrift existieren (siehe Frage 5.3.2). Da mit CM-Schriften die Umlaute
+aus zwei Lettern zusammengesetzt werden mssen, kann man fr Wrter mit
+Umlauten keine Trennungsausnahmen angeben. Erst bei Verwendung von
+T1-kodierten Schriften, wie der EC-Schriftfamilie, oder auch von
+Schriften in einer entsprechenden anderen Kodierung, die eigene Lettern
+fr Umlaute enthalten, kann man Trennungsausnahmen angeben.
+Hier ist ein einfaches Beispiel (`german.sty' ist hier nur zum
+Umschalten auf die deutschen Trennmuster ``dehypht.tex'' notwendig):
+
+ \documentclass{article}
+ \usepackage{german}
+ \usepackage[T1]{fontenc}
+ \hyphenation{Ver-st\"ar-ker-aus-gang}
+ \begin{document}
+ \showhyphens{Verst\"arkerausgang}
+ % ohne Trennausnahme: Ver-st^^e4r-ke-r-aus-gang
+ % mit Trennausnahme: Ver-st^^e4r-ker-aus-gang
+ \end{document}
+
+
+5.3.4 Wie kann ich `Hurenkinder' (engl. widows), also einzelne Zeilen
+eines Absatzes am Kopf von Buchseiten, bzw.
+`Schusterjungen/Waisenkinder' (engl. clubs), einzelne Absatzzeilen auf
+der Seite unten, verhindern?
+
+TeX kennt die Parameter \widowpenalty und \clubpenalty, mit denen man
+die `Strafpunkte' festlegen kann, falls ein Hurenkind bzw. ein
+Schusterjunge beim Seitenumbruch entstehen sollte. Auerdem gibt es noch
+den Parameter \displaywidowpenalty fr Hurenkinder nach einer
+abgesetzten mathematischen Formel. Da TeX den Wert 10000 als unendlich
+groe Strafe interpretiert, kann man mit den Zeilen
+
+ \clubpenalty = 10000
+ \widowpenalty = 10000 \displaywidowpenalty = 10000
+
+Hurenkinder und Schusterjungen komplett unterdrcken. (Das Paket
+`schuster' enthlt genau diese Zeilen.)
+Man sollte jedoch bedenken, da man bei einem Satzspiegel mit fester
+Hhe (\flushbottom) und registerhaltigem Satz Hurenkinder und
+Schusterjungen nur schwerlich verhindern kann - insbesondere wenn man
+dies bei zweiseitigem Druck fr jede Doppelseite beachten mu. Hier ist
+es oft besser, die einzelne Zeile zuzulassen oder zu versuchen, einen
+Absatz durch geringfgige Umformulierung eine Zeile lnger oder krzer
+zu machen.
+Weiterhin gibt es die Mglichkeit, Abstze, die schon sehr voll sind,
+mit \looseness=1 um eine Zeile zu dehnen oder Abstze, die recht leer
+sind, mit \looseness=-1 um eine Zeile zu krzen. Manchmal fhrt dies
+jedoch zu merklichen nderungen des Grauwerts des Absatzes. (Achtung:
+Der Wert von \looseness gilt auerhalb von Listen-Umgebungen nur fr den
+aktuellen Absatz. Innerhalb einer Listen-Umgebung mu die Zuweisung
+zusammen mit \par durch eine Gruppe lokal gehalten werden {\looseness=1
+\par}, wenn die nderung nur fr einen Absatz gelten soll.)
+
+5.3.5 Wie mu in LaTeX die Datei ``hyphen.cfg'' aussehen, um die
+deutschen Trennmuster ``dehypht.tex'' (vormals ``ghyph31.tex'') in das
+LaTeX-Format einzubinden?
+
+Eine Anleitung zur Installation der deutschen Trennmuster enthlt
+``gerdoc'', die Kurzbeschreibung des German-Styles vom Mai 1997. Diese
+Anleitung beschreibt auch die Installation der Trennmuster in Plain-TeX
+und LaTeX 2.09. Beispiel von ``hyphen.cfg'' fr LaTeX:
+
+ %% Konfigurationsdatei -- Trennmuster: `hyphen.cfg'
+ \message{== Loading hyphenation patterns:}
+
+ \chardef\l@USenglish=\language
+ \chardef\l@english=\l@USenglish %% british english als `Dialekt'
+ \input hyphen
+
+ \newlanguage\l@german \language=\l@german
+ \chardef\l@austrian=\l@german
+ \input dehypht
+
+ \newlanguage\l@ngerman \language=\l@ngerman
+ \input dehyphn
+
+ %% weitere Sprachen nach folgendem Schema:
+ % \newlanguage\l@SPRACHE \language=\l@SPRACHE
+ % \chardef\l@DIALEKT=\l@SPRACHE
+ % \input SPRACHhyphen
+
+ %% Default-Trennmuster: USenglish
+ \language=\l@USenglish \lefthyphenmin=2 \righthyphenmin=3
+ \endinput
+
+_Hinweis:_ Einige Distributionen benutzen stillschweigend die Datei
+``hyphen.cfg'' aus dem Babel-Paket. Auerdem wurde meist ``hyphen.tex''
+in ``ushyph1.tex'' umbenannt, um unter dem Namen ``hyphen.tex'' die
+Datei ``hyphen.cfg'' aus Babel auch fr Plain-TeX einbinden zu knnen.
+In diesem Fall fhrt ein ``\input hyphen'', wie im obigen Beispiel
+beschrieben, zu einer Endlosschleife!
+
+gerdoc: CTAN: language/german/gerdoc.tex
+
+
+
+5.3.6 Wieso werden Texte in `typewriter'-Schriften nicht getrennt? Gibt
+es eine Mglichkeit, da doch getrennt werden kann?
+
+TeX trennt nur, wenn die aktuell verwendete Schrift einen Divis
+(Trennungsstrich) besitzt. Dazu ist jeder Schrift ein Divis durch den
+Parameter \hyphenchar<font> zugeordnet, der bei den meisten Schriften
+auf den Wert `\-, also auf das Zeichen ``-'', gesetzt ist. Bei den
+`typewriter'-Schriften ist dieser Wert aber auf -1 gesetzt, d.h. auf ein
+nicht vorhandenes Zeichen. Damit ist die Trennung fr diese Schriften
+unterdrckt, was in den meisten Fllen auch sinnvoll ist.
+Will man dennoch, da TeX einen in `typewriter' gesetzten Textteil
+automatisch trennt, so mu man den \hyphenchar fr diese Schriften auf
+`\- setzen. Dies geht in LaTeX am einfachsten, wenn man die Anweisung
+\ttfamily umdefiniert:
+
+ \newcommand{\origttfamily}{}% sollte noch nicht definiert sein!
+ \let\origttfamily=\ttfamily % alte Definition von \ttfamily sichern
+ \renewcommand{\ttfamily}{\origttfamily \hyphenchar\font=`\-}
+
+Man knnte alternativ dazu auch die Dateien ``*cmtt*.fd'' ndern und die
+Anweisung \hyphenchar\font\m@ne in \DeclareFontFamily entfernen. Dies
+ist jedoch nicht ratsam, wenn man Texte an andere weitergeben will, da
+man dann nicht vergessen darf, die so genderten `*.fd'-Dateien
+mitzugeben.
+Fr LaTeX 2.09 (oder analog auch fr Plain-TeX) mu das Makro \tt
+umdefiniert werden:
+
+ \newcommand{\origtt}{}
+ \let\origtt=\tt
+ \renewcommand{\tt}{\origtt \hyphenchar\font=`\-}
+
+Wichtiger Hinweis: TeX kann eine Schrift unter unterschiedlichen Namen
+laden, wobei TeX alle diese Schriften nur ein einziges Mal ldt und fr
+die anderen Schriften nur `Aliases' anlegt. Daher gibt es
+\hyphenchar<font> nur einmal pro `echten' Font und \hyphenchar<font> ist
+wie auch \fontdimen<font> ein besonderer Parameter: Alle Zuweisungen an
+\hyphenchar<font> werden _immer_ global ausgefhrt. Auerdem sieht sich
+TeX diesen Parameter erst am Absatzende beim Umbruch dieses Absatzes an,
+so da mit obiger nderung nicht mglich ist, die Trennung fr einen in
+`typewriter' gesetzten Textteil zu ermglichen, fr einen anderen im
+selben Absatz zu verbieten.
+Eine weitere Methode, Trennungen fr `typewriter'-Schriften zu erlauben,
+bietet das Paket `hyphenat':
+
+ \usepackage[htt]{hyphenat}
+
+Darber hinaus kann es auch benutzt werden, um Trennung selektiv zu
+erlauben oder zu verbieten.
+
+hyphenat: CTAN: macros/latex/contrib/hyphenat/
+
+
+
+5.3.7 Warum trennt LaTeX Wrter mit Bindestrich nicht bzw. nur am
+Bindestrich, auch wenn die Trennausnahmeliste diese enthlt?
+
+TeX fgt nach dem aktuellen Trennzeichen implizit (fast) immer einen
+sogenannten \discretionary ein, der wie \- eine explizite Trennstelle
+angibt. Da sowohl \- als auch \discretionary dazu fhren, da die
+Trennung in den brigen Wortteilen unterdrckt wird, werden solche
+Wrter auer am Trennstrich nicht mehr getrennt. Dieses eigenwillige
+Verhalten von TeX ist fr Sprachen, in denen wenige Bindestriche
+verwendet werden, gnstig und sinnvoll, da zustzliche Trennungen in
+solchen Wrtern meist die Lesbarkeit erschweren.
+Um Wrter mit Bindestrichen dennoch zu trennen, existieren zwei
+Mglichkeiten: Man gibt im Dokumenttext bei diesen Wrtern, insbesondere
+wo schlecht getrennt werden kann, mit \- oder "- weitere mgliche
+Trennstellen vor oder man verwendet "= anstelle des Bindestrichs.
+Nheres ist hierzu der Dokumentation des Paketes `german' zu entnehmen.
+Die andere Mglichkeit, die bislang nur von Experten umgesetzt werden
+kann, besteht bei Schriften, die eine zweite Letter fr einen
+Bindestrich besitzen. Fr diese Schriften kann man diese zweite Letter
+als Trennstrich deklarieren. Zusammen mit den zustzlichen Trennmustern
+in ``hypht1.tex'' ist damit eine automatische Trennung von Wrtern mit
+Bindestrichen und deren Aufnahme in die Trennausnahmeliste mglich.
+
+german.sty: CTAN: language/german/
+hypht1.tex: CTAN: language/hyphenation/hypht1.tex
+
+
+
+5.4 Seitenlayout, Layout allgemein, Kopf- und Fuzeilen (*)
+
+
+5.4.1 Gibt es neben den Standard-LaTeX-Klassen auch Klassen mit einem
+`europischeren' Design?
+
+Die NTG hat verschiedene Klassenentwickelt, die im Vergleich zum Layout
+der Standard-LaTeX-Klassen kleinere berschriften und eine
+einheitlichere Einrckung der Abstze und Listen definieren.
+Das KOMA-Script-Paket enthlt ebenfalls Klassen (`scrartcl', `scrreprt',
+`scrbook' und `scrlettr'), die die Standardklassen ersetzen. Es wurden
+dort eine Vielzahl von nderungen eingefhrt, die ein gnstigeres
+Aussehen bewirken. So wird z.B. der Satzspiegel besser an das
+Papierformat angeglichen. Nhere Einzelheiten enthlt die ausfhrliche
+Beschreibung in der beigefgten Datei ``scrguide.dvi''.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+NTG-Klassen: CTAN: macros/latex/contrib/ntgclass/
+
+
+
+5.4.2 Ich suche eine Klasse fr Briefe, die weitgehend die verschiedenen
+DIN-Normen und deutschen Gepflogenheiten bercksichtigt.
+
+Unter LaTeX 2.09 ist `dinbrief' weit verbreitet, der von anderen Autoren
+auch fr LaTeX2e verfgbar gemacht wurde. Darber hinaus findet man im
+KOMA-Script-Paket die Klasse `scrlettr' und es gibt mit `g-brief' und
+`akletter' noch weitere Beispiele fr angepate Klassen.
+
+dinbrief: CTAN: macros/latex/contrib/dinbrief/
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+g-brief: CTAN: macros/latex/contrib/g-brief/
+akletter: CTAN: macros/latex/contrib/akletter/
+ (Anm.: `akletter' hie in frheren Version `myletter', ein
+ schlechter,
+ weil hufig gewhlter Name.)
+
+
+5.4.3 Gibt es eine bequemere Mglichkeit, ein Seitenlayout anzugeben,
+als dadurch, Parameter, wie \textheight, einzeln zu verndern?
+
+Mit dem Paket `typearea' aus dem KOMA-Script-Paket kann man den Anteil
+des Textbereichs an der Gesamtseite abhngig von der Schriftgre nach
+Tschicholds (siehe Frage 2.4.2) n-Teilungder Seite berechnen lassen
+
+ \documentclass[a4paper,11pt]{...} % Ausgangspapiergroesse
+ % BCOR1cm: zusaetzlich 1cm Rand fuer die Bindung.
+ % DIV10: fuer 11pt-Schrift wird 10-Teilung verwendet, bei `oneside'
+ % nimmt der Text 7/10 der Restseite ein.
+ \usepackage[BCOR1cm]{typearea}
+
+Die Verteilung der Rnder erfolgt dabei automatisch nach typographischen
+Gesichtspunkten. Diverse Papiergren sowie Hoch- und Querformat werden
+untersttzt, zustzliche Formate knnen definiert werden, und auch die
+Option `twoside' wird korrekt behandelt. Ausfhrliche Informationen dazu
+findet man in der beigefgten Datei ``scrguide.dvi''.
+Mit diesem Paket, das einem die Berechnung eines wohldefinierten
+Satzspiegels abnehmen kann, kann man auch die LaTeX-Parameter fr den
+Textbereich durch eine einfache Schnittstelle setzen:
+
+ \documentclass[a4paper]{...} % Ausgangspapiergroesse
+ \usepackage{typearea}
+ \areaset[1cm]% % Zusaetzlicher Rand fuer die Bindung
+ {18cm}{25cm} % Textbreite und Hoehe
+
+Neben `typearea' gibt es mit `vmargin' und `geometry' drei weitere
+Pakete, mit denen man die LaTeX-Parameter leichter setzen kann. Bei
+`vmargin' haben die Makroaufrufe eine festgelegte Parameterreihenfolge,
+`geometry' dagegen benutzt das Paket `keyval', mit dem die Parameter in
+beliebiger Reihenfolge angegeben werden knnen:
+
+ \usepackage{geometry}
+ \geometry{left=1.5cm,textwidth=18cm,top=1.5cm,textheight=25cm}
+
+
+ \usepackage{vmargin}
+ \setpapersize{A4}
+ \setmargins{1.5cm}{1.5cm}% % linker & oberer Rand
+ {18cm}{25cm}% % Textbreite und -hoehe
+ {12pt}{25pt}% % Kopfzeilenhoehe und -abstand
+ {0pt}{30pt}% % \footheight (egal) und Fusszeilenabstand
+
+Eine gute Mglichkeit der visuellen Kontrolle des Ergebnisses bietet das
+Paket `layouts'.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+script: CTAN: macros/latex209/contrib/script/
+geometry: CTAN: macros/latex/contrib/geometry/
+vmargin: CTAN: macros/latex/contrib/vmargin/
+layouts: CTAN: macros/latex/contrib/layouts
+
+
+
+5.4.4 Wieso ist mit der Klasse `book' oder mit der Klassenoption
+`twoside' der innere Rand kleiner als der uere?
+
+Bei doppelseitiger Formatierung werden die Seitenrnder so gewhlt, da
+sie nicht fr eine einzelne Seite sondern fr eine aufgeschlagene
+Doppelseite passen. Bei dieser bilden die Rnder der beiden Seiten drei
+vertikale weie Streifen (links auen, mittig, rechts auen), die gleich
+breit sein sollen. Da der mittlere Streifen aus den Rndern zweier
+Seiten gebildet wird, sind diese auch nur halb so breit. Aus diesem
+Grund legt man unter LaTeX die Werte fr \evensidemargin und
+\oddsidemargin, also fr den linken Rand der geraden (linken) und den
+der ungeraden (rechten) Seite, entsprechend fest. Nheres findet sich
+u.a. in der Dokumentation der KOMA-Script-Klassen.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+
+
+
+5.4.5 Gibt es einen einfachen Weg, die Seitennummer als `Seite 1 von 16'
+anzugeben?
+
+Mit dem Paket `lastpage' erhlt man durch ``\pageref{LastPage}'' eine
+Referenz auf die Seitennummer der letzten Seite. Das Paket `count1to'
+bietet mit ``\pageref{TotalPages}'' eine Referenz auf die Gesamtzahl der
+Seiten. Selbiges leistet das Paket `totpages', wobei man mit
+``\ref{TotPages}'' die Gesamtzahl aller Seiten, mit
+``\pageref{TotPages}'' die Seitennummer der letzten Seite erhalten kann.
+Diese `pageref'-Anweisungen knnen unter Zuhilfenahme des Paketes
+`fancyhdr' oder des Paketes `scrpage' aus dem KOMA-Script-Paket in der
+Form `\thepage{} von \pageref{LastPage}' in die Kopf- oder Fuzeilen
+eingefgt werden.
+
+lastpage: CTAN: macros/latex/contrib/lastpage/
+count1to: CTAN: macros/latex/contrib/ms/
+totpages: CTAN: macros/latex/contrib/totpages/
+fancyhdr: CTAN: macros/latex/contrib/fancyhdr/
+Kurzbeschreibung: CTAN: info/german/fancyhdr/
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+
+
+
+5.4.6 Wie kann ich den Kolumnentitel, die Kopfzeile der Seite, oder die
+Fuzeile nach meinen Wnschen gestalten, z.B. mit einem Strich versehen?
+
+Mit dem Paket `scrpage' und den Klassen aus dem KOMA-Script-Paket oder
+mit dem Paket `fancyhdr' kann man die Kopf- und Fuzeile einer Seite
+fast beliebig festlegen. Beide Pakete enthalten eine ausfhrliche
+Dokumentation, die auch auf andere Probleme eingeht und dafr Lsungen
+und Tips hat.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+fancyhdr: CTAN: macros/latex/contrib/fancyhdr/
+Kurzbeschreibung: CTAN: info/german/fancyhdr/
+
+
+
+5.4.7 Wie kann ich einem zweispaltig gesetzten Text (Klassenoption
+`twocolumn') eine beide Spalten bergreifende berschrift und
+Zusammenfassung voransetzen?
+
+Will man nur mit \maketitle eine berschrift mit den Autorenangaben
+einspaltig in voller Breite ber beide Spalten setzen, so verwendet man
+die Klassenoption `twocolumn' und ndert sonst nichts, da dies bei den
+Standard-Klassen und den meisten anderen Klassen automatisch vorgesehen
+ist.
+Soll jedoch zustzlich zur berschrift noch weiterer Text wie eine
+Zusammenfassung einspaltig gesetzt werden, mu man auf die Klassenoption
+`twocolumn' verzichten und stattdessen die Anweisung \twocolumn
+verwenden. Diese hat ein optionales Argument, in der man diejenigen
+Textteile angibt, die einspaltig ber die gesamte Breite gesetzt werden
+sollen. Da die Anweisung \maketitle und die Umgebung `abstract' jedoch
+nicht einfach im optionalen Argument von \twocolumn verwendet werden
+kann, mu man zu einem kleinen, leider nicht ganz sauberen Trick mit
+\csname@twocolumnfalse\endcsname greifen.
+
+ \documentclass[...]{article}
+ ...
+ \begin{document}
+ \twocolumn[{\csname @twocolumnfalse\endcsname
+ \maketitle
+ \begin{abstract}
+ ...
+ \end{abstract}
+ }]
+ ...
+ \end{document}
+
+Innerhalb des optionalen Arguments von \twocolumn funktionieren leider
+keine Funoten und damit tauchen auch fr die Anweisung \thanks in der
+Autorenliste keine Funoten auf. Werden diese bentigt, mu man sie von
+Hand mit \footnotetext nach dem optionalen Argument setzen.
+
+5.4.8 Wie kann ich verhindern, da der Beginn eines Absatzes eingezogen
+wird? Ich will Abstze stattdessen mit zustzlichem Durchschu
+markieren. (*)
+
+Meist kommt auf diese Frage
+ \setlength{\parskip}{\baselineskip} \setlength{\parindent}{0pt}
+als Antwort, jedoch fgt LaTeX \parskip auch an verschiedenen anderen
+Pltzen ein, u.a. auch zu Beginn und am Ende einer Liste und zwischen
+den Listenelementen. Dies kann man mit dem Paket `parskip' von Hubert
+Partl zum Teil verhindern, wenn auch nicht komplett.
+Weitergehende Lsungen finden sich in den KOMA-Script- und NTG-Klassen.
+Die KOMA-Script-Klassen kennen die Klassenoption `parskip' und
+verschiedene Varianten davon. Zu den NTG-Klassen gehren `artikel3',
+`rapport3' und `boek3', die ebenfalls ein Layout ohne Absatzeinzug und
+mit zustzlichen Durchschu bieten.
+Ob man nun den Beginn eines neuen Absatzes mit einem Einzug oder mit
+einem zustzlichen Durchschu markiert, ist immer wieder Anla zu mehr
+oder weniger ausgiebigen Diskussionen. Um einen weitverbreiteten Irrtum
+auszurumen: Der einzuglose Satz hat im ``deutschen Buchsatz'' keine
+Tradition. Einzugloser Satz, ob nun mit oder ohne zustzlichen
+Durchschu, ist im Zeitungs- und Zeitschriftensatz weit verbreitet, so
+da er manchen vertrauter erscheint als der traditionelle Buchsatz mit
+Einzug. Letztendlich sollte man bei der Wahl, ob mit oder ohne Einzug,
+an den Leser denken; wie einfach dieser einen neuen Absatz, den Beginn
+eines neuen Teils der niedergeschriebenen Gedankenfolge, immer klar und
+deutlich erkennen kann.
+
+parskip.sty: CTAN: macros/latex/contrib/misc/parskip.sty
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+NTG-Klassen: CTAN: macros/latex/contrib/ntgclass/
+
+
+
+5.4.9 Wie kann ich den Durchschu meines Dokuments vergrern, wenn ich
+beispielsweise ein Dokument mit 1,5- oder 2-fachem Zeilenabstand
+abliefern soll?
+
+Abgesehen davon, da man eine solch starke Vergrerung des
+Zeilenabstand vermeiden sollte, hilft das Paket `setspace':
+
+ \usepackage{setspace}
+ \doublespacing % doppelzeilig oder
+ %\onehalfspacing % anderthalbzeilig
+
+
+setspace: CTAN: macros/latex/contrib/setspace/
+
+
+
+5.4.10 Wieso bekomme ich mit \pagestyle{empty} dennoch eine Seitennummer
+auf der ersten Seite mit dem Artikeltitel?
+
+Fast alle LaTeX-Klassen definieren die Anweisung \maketitle so, da fr
+diese Seite mit \thispagestyle auf den Seitenstil `plain' umgeschalten
+wird. \thispagestyle berschreibt damit den gewhlten Seitenstil fr
+diese eine Seite. Um dies zu verhindern, mu man entweder eine besser
+geeignete Klasse whlen, die Definition in der Klasse ndern oder
+folgenden Trick anwenden: _Direkt_ nach der Anweisung \maketitle wird
+\thispagestyle{empty} eingefgt. Alternativ kann das Paket `nopageno'
+verwendet werden.
+
+nopageno: CTAN: macros/latex/contrib/carlisle/nopageno.sty
+
+
+
+5.4.11 Wie kann ich mein gesamtes LaTeX-Dokument im Querformat setzen?
+
+Zu diesem Zweck ist bei der Dokumentenklasse die Klassen-Option
+`landscape' anzugeben. Zustzlich mu dem verwendeten dvi-Treiber die
+nun vom Standard abweichende Seitengre mitgeteilt werden. Im Falle von
+`dvips' kann man dies statt per Kommandozeilenoption mit Hilfe des
+Pakets `geometry' erreichen.
+
+ \usepackage[dvips]{geometry}
+
+
+geometry: CTAN: macros/latex/contrib/geometry/
+
+
+
+5.4.12 Wie kann ich Teile meines Dokumentes im Querformat setzen?
+
+Dokumentteile knnen nur gedreht werden, wenn dies auch vom verwendeten
+dvi-Gertetreiber untersttzt wird. In den meisten Fllen bedeutet dies,
+da die dvi-Datei nach PostScript zu konvertieren ist. Zum Betrachten
+und Ausdrucken ist ein PostScript-Viewer wie beispielsweise `gv' oder
+`gsview' unter Verwendung von `Ghostscript' geeignet.
+Das LaTeX-Bundle `graphics' enthlt das Paket `lscape', das eine
+`landscape'-Umgebung zur Verfgung stellt. Der Inhalt dieser Umgebung
+wird um 90 Grad gegen den Uhrzeigersinn gedreht und auf eine eigene
+Seite plaziert. Zu Beginn und am Ende der Umgebung wird ein \clearpage
+ausgefhrt:
+
+ \usepackage{lscape}
+ % etc.
+ \begin{landscape}
+ \begin{figure}
+ gedrehte Abbildung
+ \caption{gedrehte Unterschrift}
+ \end{figure}
+ % evtl. noch weitere Abbildungen/normaler Text/etc.
+ \end{landscape}
+ % etc.
+
+Wird ein Dokument mit solcherart gedrehten Seiten per pdfLaTeX zu einer
+pdf-Datei kompiliert, wre es wnschenswert, wenn die gedrehten Seiten
+bei Betrachtung mit `Acrobat Reader' in aufrechter Schrift, also um
+90 Grad gedreht, dargestellt wrden. In diesem Fall ist das Paket
+`pdflscape' zu verwenden, das wiederum das Paket `lscape' ldt und um
+entsprechende PDF-Anweisungen ergnzt:
+
+ \usepackage{pdflscape}
+ % ...
+
+Will man nicht ganze Seiten drehen oder stren die implizit ausgefhrten
+\clearpage-Anweisungen, so kann man auch nur die Anweisung \rotatebox
+aus dem Paket `graphics' verwenden:
+
+ \usepackage{graphics} % oder `graphicx'
+ % etc.
+ \begin{figure}
+ \rotatebox{90}{%
+ \begin{minipage}{.6\textheight}
+ gedrehte Abbildung
+ \caption{gedrehte Unterschrift}
+ \end{minipage}%
+ }
+ \end{figure}
+
+Das Paket `rotating' bietet statt der einfachen \rotatebox-Anweisung mit
+all ihren Nachteilen (Stichwort: `verbatim'!) die Umgebungen `rotate',
+`turn' und `sideways', innerhalb der man (fast) beliebigen Text
+plazieren kann. Fr den Spezialfall, da eine Abbildung bzw. Tafel wie
+mit der Umgebung `landscape' eine komplette Seite fllt und um 90 Grad
+gegen den Uhrzeigersinn gedreht werden soll, gibt es die den `figure'-
+und `table'- entsprechenden `sidewaysfigure'- und
+`sidewaystable'-Umgebungen. Auerdem ist eine ltere Version dieses
+Pakets auch fr LaTeX 2.09 verfgbar.
+Mehr ber diese Pakete findet man in der Dokumentation ``grfguide.tex''
+des `graphics'-Bundle, der mit `rotating' mitgelieferten Dokumentation
+und dem Buch `Der LaTeX-Begleiter' (siehe Frage 2.4.1) sowie in Keith
+Reckdahls Artikel `Using Imported Graphics in LaTeX2e' (siehe Frage
+2.4.2).
+
+lscape: CTAN: macros/latex/required/graphics/
+pdflscape: CTAN: macros/latex/contrib/oberdiek/
+rotating: CTAN: macros/latex/contrib/rotating
+epslatex: CTAN: info/epslatex.ps
+ CTAN: info/epslatex.pdf
+
+
+
+--- DE-TeX-FAQ Ende Teil 5 ---
diff --git a/help/de-tex-faq/part6 b/help/de-tex-faq/part6
new file mode 100644
index 0000000000..7c4ae54e2f
--- /dev/null
+++ b/help/de-tex-faq/part6
@@ -0,0 +1,1117 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!aanews.merit.edu!news.cc.uic.edu!news.uchicago.edu!yellow.newsread.com!netaxs.com!newsread.com!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 6 of 11)
+Supersedes: <de-tex-faq-6-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:17 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 1088
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-6-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975397 890 134.100.9.52 (19 Sep 2003 12:43:17 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:17 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117404 de.answers:9381 news.answers:258270
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part6
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 6 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+6 TeX, LaTeX, Makros etc. (II)
+
+
+6.1 Abbildungen und Tafeln
+
+
+6.1.1 Wieso werden die meisten meiner Abbildungen an das Ende des
+Kapitels oder Dokuments verschoben?
+
+Das optionale Argument der `figure'- oder `table'-Umgebung _schrnkt_
+die Plazierungsmglichkeiten auf die angegebenen Orte ein. Mit dem
+optionalen Argument gibt man also _nicht_, wie oft flschlich geglaubt
+und weiterverbreitet wird, die Plazierung fr weitere Orte an. Deshalb
+nie Plazierungsangaben nur auf [h] einschrnken, sondern mindestens
+einen weiteren Ort mit angeben! Grund: Kann die Abbildung nicht `h'ier
+plaziert werden, darf sie nirgendwo anders gesetzt werden und wird nach
+hinten an das Ende des Kapitels bzw. des Dokuments geschoben. Da LaTeX
+die Reihenfolge der Abbildungen bzw. der Tafeln nicht verndert, werden
+alle nachfolgenden Abbildungen bzw. Tafeln mit dieser nicht plazierbaren
+Abbildung oder Tafel nach hinten verschoben. Genau dasselbe kann
+passieren, wenn die Plazierungsbeschrnkung mit [p] angegeben wird, das
+Bild kleiner als \floatpagefraction ist und das nchste Bild nicht
+zusammen mit diesem auf eine Seite pat. Ebenso bei einer Beschrnkung
+auf [t] und einem Bild, das grer als \topfraction ist, dto. fr [b]
+und \bottomfraction.
+Tip: Lassen Sie zu Beginn das optionale Argument der `figure'- oder
+`table'-Umgebung weg - es ist nicht ohne Grund ein _optionales_ Argument
+dieser Umgebungen! Fgen Sie spter fr eine Endfassung Ihres Dokuments
+nur an den Stellen ein optionales Argument mit
+Plazierungseinschrnkungen ein, wenn z.B. eine bestimmte Abbildung oder
+Tafel auf einer eigenen Seite oder auf einer Seite oben erscheinen
+sollte.
+Weitere Hinweise finden Sie in
+
+* Axel Reichert: ``Gleitobjekte - die richtige Schmierung''
+ CTAN: info/german/gleitobjekte/
+* Axel Reichert: ``Satz von Tabellen''
+ CTAN: info/german/tabsatz/
+* Piet van Oostrum: ``Floats in LaTeX''
+ http://www.cs.ruu.nl/~piet/floats/
+
+
+6.1.2 Wie kann ich die Default-Plazierungseinschrnkungen ndern? Ich
+mchte meine Abbildungen auch `h'ier plazieren, ohne jedesmal das
+optionale Argument angeben zu mssen.
+
+In LaTeX werden diese Angaben, die sogenannten `float placement
+specifier' fr die `figure'- und `table'-Umgebungen, in den Makros
+\fps@figure und \fps@table abgelegt. Durch die Redefinitionen
+
+ \renewcommand{\fps@figure}{htbp}
+ \renewcommand{\fps@table}{htbp}
+
+(diese Zeilen mit \makeatletter ... \makeatother klammern oder in eine
+sty-Datei schreiben, siehe auch Frage 8.5.1) fgt man noch die
+`h'ier-Plazierung hinzu.
+Die Standard-LaTeX-Klassen setzen die Default-Plazierungen auf `tbp',
+untersagen also die `h'ier-Plazierung einer Abbildung bzw. Tafel. Dies
+ist in den meisten Fllen auch sinnvoll, da Abbildungen und Tafeln nur
+dazu dienen, die Aussagen im Text durch beispielsweise eine
+anschaulichere Darstellung oder kompakte bersicht zu untersttzen. Die
+Abbildung oder Tafel ist damit _nicht_ integraler Bestandteil des
+Textes, sondern ein dem Text noch zustzlich zugeordneter Bestandteil
+des Dokuments. Daher sollten diese den Text nicht unterbrechen, was eine
+`h'ier-Plazierung zweifellos tun wrde. Somit ist der Default `tbp' in
+den meisten Fllen sinnvoll.
+
+6.1.3 Wie mu ich die `float'-Parameter ndern, so da die Abbildungen
+und Tafeln gnstiger innerhalb eines Abschnitts verteilt werden?
+
+Der Plazierungsalgorithmus von LaTeX erledigt diese Aufgabe eigentlich
+sehr gut, wenn man einmal selbst durchzuspielen versucht, wohin man
+selbst unter den gegebenen Bedingungen und Wechselwirkungen eine
+Abbildung oder eine Tafel hinsetzen bzw. schieben wrde. Ist man mit dem
+Ergebnis dennoch nicht ganz zufrieden, kann man einmal folgendes
+probieren:
+Zuerst sollte man die Plazierungsbeschrnkungen an allen `figure'- und
+`table'-Umgebungen entfernen. Anschlieend kann man die Parameter des
+Plazierungsalgorithmus ndern:
+Eine oder mehrere Abbildungen kommen erst auf eine eigene Seite, eine
+sogenannte `float page', wenn diese mindestens 60% der Seite einnehmen.
+Damit gibt es weniger `float pages', die nur halbvoll sind.
+Empfehlenswert ist ein Wert zwischen 50% und 80%, je nachdem wie viele
+Abbildungen existieren, wie gro und wie unterschiedlich gro diese
+Abbildungen sind.
+
+ \renewcommand{\floatpagefraction}{.6}% vorher: .5
+
+Von einer Seite mu neben den Abbildungen, die `h'ere, `t'op und
+`b'ottom plaziert werden, noch mindestens 15% Text erscheinen. Diesen
+Wert sollte man nicht zu klein whlen, um nicht nur Seiten zu erzeugen,
+bei denen man den Text suchen mu. Bei vielen Bildern lieber den Wert
+von \floatpagefraction kleiner whlen. Empfehlenswert ist ein Wert
+zwischen 10% und 30%.
+
+ \renewcommand{\textfraction}{.15} % vorher: .2
+
+Maximaler Anteil der Seite, die fr Abbildungen, die `t'op bzw. `b'ottom
+plaziert werden, verwendet werden darf. Diese Werte sollte man nicht zu
+gro whlen, bei vielen Abbildungen lieber den Wert von
+\floatpagefraction kleiner whlen. Insbesondere \bottomfraction sollte
+man klein halten, da Abbildungen gewhnlich auf einer Seite oben
+vermutet werden. Empfehlenswert sind Werte zwischen 50% und 85% fr
+\topfraction und 20% bis 50% fr \bottomfraction. Einer dieser beiden
+Werte sollte stets grer als \floatpagefraction sein! (\topfraction
+sollte nie auf 1.0, \textfraction nie auf 0.0 gesetzt werden!)
+
+ \renewcommand{\topfraction}{.8} % vorher: .7
+ \renewcommand{\bottomfraction}{.5} % vorher: .3
+
+Maximale Anzahl der Abbildungen und Tafeln, die auf einer Seite `t'op
+bzw. `b'ottom bzw. insgesamt auf der Seite plaziert werden. Hat man
+viele kleine Abbildungen sollte man diese Werte erhhen. Will man
+Abbildungen mglichst auf eine `float page' setzen, sollte man
+`topnumber' und `bottomnumber' auf 0 setzen und \floatpagefraction bis
+auf 0.01 erniedrigen.
+
+ \setcounter{topnumber}{3} % vorher: 2
+ \setcounter{bottomnumber}{1} % vorher: 1
+ \setcounter{totalnumber}{5} % vorher: 3
+
+Im zweispaltigen Textsatz knnen Abbildungen und Tafeln nur oben auf der
+Seite plaziert werden, so da es hierfr nur zwei weitere Parameter
+gibt, die den Parametern \floatpagefraction und \topfraction fr
+einspaltigen Satz entsprechen. Werden Abbildungen oben plaziert, so
+knnen Abbildungen und Tafeln ber beide Spalten maximal \dbltopfraction
+Platz einnehmen. Schlielich gibt \dblfloatpagefraction eine Untergrenze
+an, ab der erst eine eigene `float page' probiert wird.
+
+ \renewcommand{\dbltopfraction}{.8} % vorher: .7
+ \renewcommand{\dblfloatpagefraction}{.6}% vorher: .5
+
+Nachdem man mit den genderten Plazierungsparametern ein
+zufriedenstellendes Ergebnis erzielt hat, kann man durch gezielten
+Einsatz des optionalen Arguments der `figure'- bzw. `table'-Umgebung
+einzelne ungnstig plazierte Abbildungen und Tafeln entsprechend
+verschieben. Hierbei sollte man nur die nicht erwnschte Plazierung
+entfernen, also z.B. [bp] angeben, falls eine `t'op-Plazierung ungnstig
+ist.
+Die Bedeutung dieser Parameter wird anschaulich in bildlicher Form in
+dem Artikel `The layouts package: User manual' (`layman') von Peter R.
+Wilson beschrieben. Die fr die verwendete Dokumentenklasse geltenden
+Werte knnen mit dem zugehrigen LaTeX-Paket `layouts' angezeigt und
+einfach testweise gendert werden. `layouts' zeigt darberhinaus auch
+viele weitere fr das Layout eines Dokumentes wichtigen Parameter an.
+
+layouts: CTAN: macros/latex/contrib/layouts
+layman: CTAN: macros/latex/contrib/layouts/layman.tex
+
+
+
+6.1.4 Wie kann ich die Fehlermeldung `! LaTeX Error: Too many
+unprocessed floats.' vermeiden?
+
+LaTeX reserviert fr alle `floats', also die Flieumgebungen `figure'-
+und `table'-Umgebungen, eines Dokuments 18 sogenannte
+Insertion-Registertupel. Wenn eine Flieumgebung nicht sofort auf eine
+Seite plaziert werden kann, wird es in eines dieser Register
+zwischengespeichert. Mssen mehr als 18 Flieumgebungen
+zwischengespeichert werde, erhlt man diese Fehlermeldung. Es gibt vier
+Mglichkeiten, wieso dies geschieht:
+
+ 1. Meist stehen die optionalen Argumente der `figure'- oder
+ `table'-Umgebung im Widerspruch zu den Plazierungsparametern oder
+ letztere sind zu restriktiv eingestellt. Beispielsweise kann eine
+ `figure', die hher als der Parameter \topfraction ist und aufgrund
+ des optionalen Arguments [t] nur oben plaziert werden darf, nicht
+ auf eine Seite gesetzt werden. Aus diesem Grund sollte man den
+ optionalen Parameter _nicht_ setzen und wenn, dann _alle_ auer den
+ nicht gewnschten Plazierungsorte angeben.
+ 2. Werden die Parameter \...fraction ungnstig gesetzt, so kann es
+ ebenfalls sein, dass einige Flieumgebungen nicht auf eine Seite
+ gesetzt werden knnen. Nheres findet sich in Frage 6.1.1 und in
+ Keith Reckdahls Artikel `Using Imported Graphics in LaTeX2e'
+ (epslatex).
+ 3. In einigen wenigen Fllen, wo sehr viele Flieumgebungen und viele
+ mit \marginpar eingefgte Marginalen, die die gleichen Register
+ teilen, verwendet werden, sind mehr als 18 Register notwendig. Hier
+ kann das Paket `morefloats' weiterhelfen, dass deren Zahl auf 36
+ erhht. Leider hat man dadurch 18 Savebox-, Zhler-, Lngen- und
+ Glue-Register weniger, so da man jetzt evtl. auf den Fehler `No
+ room for a new ...' stt.
+ 4. Bestehen Textteile nur aus Flieumgebungen ohne oder mit nur wenig
+ Text, versagt LaTeX Plazierungsalgorithmus, da hier nichts ist, in
+ denen sie ``flieen'' knnen. In diesen Fllen gibt es folgende
+ Abhilfen:
+
+ 1. Schreiben Sie mehr erluternden Text oder verteilen Sie die
+ Flieumgebungen besser im existierenden Text.
+ 2. Fgen Sie die Anweisung \clearpage zwischen einige
+ Flieumgebungen, um LaTeX zu zwingen, alle gespeicherten
+ Flieumgebungen auf eigene Seiten zu setzen. Diese Lsung ist
+ mit Arbeit verbunden, da meist mehrere Versuche notwendig
+ sind, um nur wenig gefllte Seiten zu vermeiden und diese bei
+ nderungen wiederholt werden mssen. \afterpage{\clearpage}
+ ist etwas besser, aber auch hier mu man manuell nacharbeiten,
+ um nur teilgefllte Seiten zu vermeiden.
+ 3. Wenn kein Text vorhanden ist, in der die Flieumgebungen
+ flieen knnen, so sollte man besser nicht-flieende
+ Umgebungen verwenden.
+
+
+
+epslatex: CTAN: info/epslatex.ps
+ CTAN: info/epslatex.pdf
+morefloats: CTAN: macros/latex/contrib/misc/morefloats.sty
+
+
+
+6.1.5 Wie kann ich es erreichen, da zwei Abbildungen nicht auf
+verschiedenen Seiten, sondern mglichst direkt untereinander plaziert
+werden?
+
+In eine einzige `figure'- bzw. `table'-Umgebung knnen auch mehrere
+Abbildungen oder Tafeln gesetzt und mit eigenen Unterschriften versehen
+werden:
+
+ \begin{figure}
+ erstes Bild
+ \caption{erstes Bild}
+ \vspace{\floatsep} % zusaetzlicher Abstand zwischen zwei `floats'
+ zweites Bild
+ \caption{zweites Bild}
+ \end{figure}
+
+Alle Abbildungen oder Tafeln einer Umgebung werden dann nicht mehr
+getrennt. Aus diesem Grund sollte man auch darauf achten, da eine
+`figure'- oder `table'-Umgebung durch zu viele Abbildungen und Tafeln
+nicht zu hoch wird.
+
+6.1.6 Wie kann ich in einer Abbildung zwei Bilder nebeneinander setzen?
+
+Man kann zum Beispiel zwei `minipage'-Umgebungen verwenden, wobei man
+dann auch mit deren optionalem Argument die Ausrichtung der beiden
+Bilder angeben kann:
+
+ \begin{figure}
+ \begin{minipage}[b]{.4\linewidth} % [b] => Ausrichtung an \caption
+ Bild links
+ \caption{Bildunterschrift links}
+ \end{minipage}
+ \hspace{.1\linewidth}% Abstand zwischen Bilder
+ \begin{minipage}[b]{.4\linewidth} % [b] => Ausrichtung an \caption
+ Bild rechts
+ \caption{Bildunterschrift rechts}
+ \end{minipage}
+ \end{figure}
+
+Ein sehr viel bequemerer Weg, um mehrere zusammengehrende Abbildungen
+oder Tafeln in einer Float-Umgebung zu setzen, bietet das Paket
+`subfigure'. Hierzu stellt das Paket die Anweisungen \subfigure und
+\subtable zur Verfgung. Die Formatierung der Einzelabbildungen lt
+sich sehr leicht anpassen.
+
+subfigure: CTAN: macros/latex/contrib/subfigure/
+
+
+
+6.1.7 Wie kann ich eine Abbildung (`figure') und eine Tafel (`table')
+nebeneinander setzen?
+
+Verwendet man statt der Anweisung \caption die im Paket `capt-of'
+definierte Anweisung \captionof, so ist es mglich, eine eigentlich zu
+einer anderen Flieumgebung gehrige Beschriftung zu erreichen. Wie hier
+gezeigt
+
+ \usepackage{capt-of}
+ ...
+ \begin{figure}
+ \begin{minipage}{.5\linewidth}
+ Abbildung
+ \caption{Abbildung}
+ \end{minipage}%
+ \begin{minipage}{.5\linewidth}
+ Tafel
+ \captionof{table}{Tafel}
+ % auch: \captionof{table}[Eintrag im Verzeichnis]{Tafel}
+ \end{minipage}
+ \end{figure}
+
+kann man eine Abbildung und eine Tafel nebeneinander setzen, wobei die
+Unterschriften auch in das jeweilige Verzeichnis gelangen. Die Anweisung
+\captionof ist auch geeignet, um nichtgleitende Abbildungen mit einer
+Bildunterschrift zu versehen.
+
+capt-of: CTAN: macros/latex/contrib/misc/capt-of.sty
+
+
+
+6.1.8 Wie kann ich mehrere zusammengehrige Abbildungen bzw. Tafeln
+entsprechend mit 1a, 1b etc. numerieren?
+
+Das Paket `subfigure' bietet die Anweisungen \subfigure und \subtable
+an, mit der man dies innerhalb der gewohnten `figure'- oder
+`table'-Umgebung erreichen kann.
+
+subfigure: CTAN: macros/latex/contrib/subfigure/
+
+
+
+6.1.9 Gibt es bei der Option `twocolumn' die Mglichkeit, Abbildungen
+(`figure') und Tafeln (`table') ber beide Spalten, also die gesamte
+Textbreite einer Seite zu setzen?
+
+Statt `figure'- die `figure*'-, statt `table'- die `table*'-Umgebung
+verwenden.
+
+6.1.10 Wieso bekomme ich Fehlermeldungen, wenn ich eine
+`figure'-Umgebung in andere Umgebungen oder Anweisungen einfge?
+
+Eine `figure'- oder `table'-Umgebung ist ein sogenannter `float', d.h.
+der Inhalt ``fliet'' an eine andere Stelle. Deshalb darf diese Umgebung
+nicht innerhalb einer anderen, wie `minipage', \parbox o.. verwendet
+werden. Die Eingabe
+
+ \begin{minipage}{5cm} %% FALSCH!
+ \begin{figure}
+ Bild
+ \caption{text}
+ \end{figure}
+ \end{minipage}
+
+ist daher falsch und erzeugt den in der Frage genannten Fehler. Korrekt
+und auch logisch einsichtiger ist es, wenn man den Inhalt der
+`figure'-Umgebung in eine `minipage' packt, also diese _in_ die
+`figure'-Umgebung setzt:
+
+ \begin{figure}
+ \begin{minipage}{5cm} %% KORREKT!
+ Bild
+ \caption{text}
+ \end{minipage}
+ \end{figure}
+
+
+6.1.11 Wie kann ich das Layout der Bildunterschriften (\caption)
+verndern?
+
+LaTeX verwendet die interne Anweisung \@makecaption{Bild Nr}{Text}, um
+die Bildunterschrift inkl. Bildnummer zu setzen. Indem man diese
+Anweisung verndert, die in der Dokumentklasse definiert wird, kann man
+das Layout ndern. Will man nur die Bildnummer (z.B. ``Abbildung 1'')
+ndern, so reicht es oftmals aus, die interne Anweisung \fnum@figure
+bzw. fr Tafeln \fnum@table entsprechend umzudefinieren.
+Zur Vereinfachung gibt es einige leicht zu verwendende Pakete: `caption'
+bzw. `caption2' haben viele Optionen; diese Pakete ermglichen die
+Variation der Schriftart und -gre und des Layouts (zentriert,
+berhngend, Absatz mit Einrckung usw.). Beispiel:
+
+ \usepackage[bf]{caption2}
+ \renewcommand{\captionfont}{\small\itshape}
+
+fr einen etwas kleineren und kursiv gesetzten Unterschriftentext, wobei
+die Bildnummer weiterhin fett gesetzt wird.
+Um die Benennung zu ndern, wenn man also statt ``Abbildung''
+beispielsweise ``Abb.'' verwenden mchte, erreicht man dies durch
+
+ \renewcommand{\figurename}{Abb.}
+
+Im Falle einer Tafel mu analog dazu \tablename umdefiniert werden.
+(Achtung: Bitte weitere Hinweise in Frage Frage 8.5.9 beachten!)
+Wollen Sie die Zhlweise der Abbildungs- bzw. Tabellennumerierung
+ndern, so beachten Sie auch Frage Frage 8.5.2.
+Speziellere Lsungen existieren natrlich auch oder sind teilweise in
+einigen Dokumentklassen enthalten. So enthalten die NTG-und
+KOMA-Script-Klassen beispielsweise Anweisungen, um alle Fonts (Sections,
+Captions, Running Heads) zu verndern.
+
+epslatex: CTAN: info/epslatex.ps
+ CTAN: info/epslatex.pdf
+caption/caption2: CTAN: macros/latex/contrib/caption
+NTG-Klassen: CTAN: macros/latex/contrib/ntgclass
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+hangcaption: CTAN: macros/latex209/contrib/misc/hangcaption.sty
+isucaption: CTAN: macros/latex209/contrib/misc/isucaption.sty
+
+
+
+6.1.12 Wie kann ich die Unterschriften (\caption) neben eine Abbildung
+oder eine Tafel setzen?
+
+Zu diesem Zweck ist das Paket `sidecap' gedacht.
+
+sidecap: CTAN: macros/latex/contrib/sidecap
+
+
+
+6.1.13 Wie kann ich Abbildungen oder Tafeln, die nicht innerhalb einer
+`figure'- oder `table'-Umgebung stehen, dennoch mit einer
+Bildunterschrift (Legende) versehen?
+
+Keith Reckdahls Artikel `Using Imported Graphics in LaTeX2e' (epslatex)
+enthlt die Beschreibung eines entsprechenden Tricks. Das Paket
+`capt-of' (siehe auch Frage 6.1.7) implementiert diesen und stellt eine
+entsprechende Anweisungen zum Satz von Legenden fr nicht-gleitende
+Abbildungen zur Verfgung.
+
+capt-of: CTAN: macros/latex/contrib/misc/capt-of.sty
+
+
+
+6.1.14 Wie kann man neue Typen von Gleitumgebungen (`floats') z.B. fr
+weitere Arten von Tafeln oder Programm-Code erzeugen?
+
+Prinzipiell mu man fr einen neuen Typ von Gleitumgebung einige Makros
+definieren. Beispielsweise sind fr die zu definierenden Umgebungen
+`faqtable' und `faqtable*' die folgenden Anweisungen (in eine .sty-Datei
+schreiben, da interne Anweisungen!) notwendig,
+
+ \newcounter{faqtable}[section]
+ %\renewcommand{\thefaqtable}{\thesection.\arabic{table}}
+ %% \thefaqtable wird bereits durch \newcounter definiert
+ \renewcommand{\fps@faqtable}{tp} % nicht `h' bzw. `b'
+ \renewcommand{\ftype@faqtable}{4} % type is a power of two!
+ \renewcommand{\ext@faqtable}{lot} % Endung der Hilfsdatei
+ \renewcommand{\fnum@faqtable}{FAQ-Tabelle~\thefaqtable}
+ \newenvironment{faqtable}{\@float{faqtable}}{\end@float}
+ \newenvironment{faqtable*}{\@dblfloat{faqtable}}{\end@dblfloat}
+
+wobei damit noch keine Anpassungen des Inhaltsverzeichnisses, ein
+eigenes Inhaltsverzeichnis oder sonstige Anpassungen des Layouts
+durchgefhrt sind. Mehr Informationen dazu findet man im Buch `Der
+LaTeX-Begleiter' (siehe Frage 2.4.1).
+Sehr viel einfacher geht dies mit dem Paket `float', mit dem z.B. obiges
+auch der normale LaTeX-Benutzer mit der simplen Anweisung
+ \newfloat{faqtable}{tp}{lot}[section]
+definieren kann. Daneben sind auch schon einige `float'-Layouts
+vordefiniert und knnen ebenso einfach verwendet werden.
+
+float: CTAN: macros/latex/contrib/float
+
+
+
+6.1.15 Abbildungen und Tafeln sollen _immer_ nach dem ersten Verweis auf
+sie gesetzt werden. Wie? Es ist mglich, da LaTeX sie vor der
+Abschnittsberschrift plaziert. Wie unterbinde ich das?
+
+Mit dem LaTeX-Paket `flafter', das Bestandteil jeder LaTeX-Verteilung
+ist, werden Abbildungen und Tafeln nie vor dem Text plaziert, in dem sie
+im Dokument angegeben werden. Damit LaTeX sie also nie vor dem ersten
+Verweis plaziert, schiebt man die entsprechende `figure'- bzw.
+`table'-Umgebung einfach hinter die erste \ref- bzw. \pageref-Anweisung.
+
+flafter: CTAN: macros/latex/base/
+ CTAN: macros/latex/unpacked/
+
+
+
+6.1.16 Gibt es eine einfache Mglichkeit, eine Abbildung oder Tafel
+innerhalb des normalen Textes zu setzen, sie also mit dem normalen Text
+umflieen zu lassen?
+
+Hierfr gibt es mittlerweile eine groe Anzahl von Paketen mit
+unterschiedlichen Beschrnkungen und Vor- und Nachteilen, die Piet van
+Oostrum in einer Liste, die er unregelmig nach `comp.text.tex' postet,
+aufzhlt:
+ `flow', `floatflt' (fr LaTeX2e, Vorgnger `floatfig' ist fr LaTeX
+ 2.09), `picinpar' (veraltet), `picins', `window', `wrapfig'.
+Empfohlen werden: `picins' (funktioniert auch in Listen-Umgebungen),
+`floatflt' und `wrapfig' (untersttzen neben `figure'- auch
+`table'-Umgebungen), da diese am meisten knnen und die wenigsten Fehler
+aufweisen.
+
+picins: CTAN: macros/latex209/contrib/picins
+floatflt: CTAN: macros/latex/contrib/floatflt
+wrapfig: CTAN: macros/latex/contrib/wrapfig/
+
+
+
+6.1.17 Wieso erhalte ich bei einigen Abbildungen falsche Querverweise,
+obwohl ich doch die \label-Anweisung innerhalb der `figure'-Umgebung
+verwendet habe?
+
+Die \label-Anweisung mu _nach_ der Anweisung folgen, die fr die
+Numerierung und damit auch fr die `Verankerung' des Verweises sorgt.
+Solche Verankerungsanweisungen sind z.B. \section oder \caption, die
+`figure'-Umgebung dagegen ist keine. Daher mu das \label _nach_ der
+entsprechenden \caption folgen:
+
+ \begin{figure}
+ ... Abbildung ...
+ \caption{Dies ist eine Abbildung}
+ \label{fig:beispielabbildung}
+ \end{figure}
+
+
+6.1.18 Wie kann ich erreichen, da Abbildungen oder Tafeln, die alleine
+auf einer sonst leeren Seite plaziert werden, bndig mit der
+Seitenoberkante statt vertikal zentriert erscheinen?
+
+Fr die Zentrierung von Float-Objekten sind die internen Lngenparameter
+\@fptop, \@fpsep und \@fpbot verantwortlich. Um die vertikale
+Zentrierung aufzuheben, ist daher \@fptop im Dokumentkopf oder in einer
+eigenen Paketdatei auf eine unflexible Lnge zu setzen:
+
+ \setlength{\@fptop}{0pt}
+
+(Bitte beachten, da \@fptop ein interner Parameter ist und auerhalb
+einer Paketdatei mit \makeatletter/\makeatother geklammert werden mu.)
+Diese nderung gilt dann fr _alle_ Float-Objekte, also sowohl
+Abbildungen als auch Tafeln.
+
+6.2 Tabellen
+
+
+6.2.1 Wie kann ich erreichen, da sich eine Tabelle ber mehrere Seiten
+erstreckt?
+
+Zu diesem Zweck gibt es die beiden Pakete `longtable' und `supertabular'
+sowie `ltxtable', welches die Mglichkeiten von `longtable' und
+`tabularx' in sich vereinigt.
+`longtable' benutzt auf jeder Seite die gleiche Spaltenbreite, whrend
+`supertabular' auf jeder Seite die Spaltenbreite neu berechnet.
+`supertabular' funktioniert im Gegensatz zu `longtable' auch mit der
+Klassenoption `twocolumn'. `tabularx' ist nicht direkt fr mehrseitige
+Tabellen gedacht, sondern zum Austreiben einer Tabelle auf eine
+bestimmte Breite. Eine mehrseitige Tabelle kann mit `ltxtable' auf eine
+bestimme Breite ausgetrieben werden, wofr auch die Pakete `longtable'
+und `tabularx' erforderlich sind.
+
+longtable: CTAN: macros/latex/required/tools/
+tabularx: CTAN: macros/latex/required/tools/
+supertabular: CTAN: macros/latex/contrib/supertabular
+ltxtable: CTAN: macros/latex/contrib/carlisle
+
+
+
+6.2.2 Wie kann ich einzelne Felder oder grere Bereiche einer Tabelle
+farbig oder grau hinterlegen?
+
+Zu diesem Zweck gibt es die beiden Pakete `colortbl' und `colortab'.
+Nhere Hinweise sind den beiliegenden Dokumentationen oder dem Buch
+``The LaTeX Graphics Companion'' (siehe Frage 2.4.1) zu entnehmen.
+
+colortbl: CTAN: macros/latex/contrib/carlisle
+colortab: CTAN: macros/generic/colortab/
+
+
+
+6.2.3 Wie kann ich erreichen, da sich eine Tabelle ber die gesamte
+Spalten- bzw. Textbreite (oder ber eine andere vorgegebene Breite)
+erstreckt?
+
+Zu diesem Zweck gibt es das Paket `tabularx' sowie `ltxtable', welches
+die Mglichkeiten von `longtable' und `tabularx' in sich vereinigt.
+`tabularx' ermglicht das Austreiben einer Tabelle auf eine bestimmte
+Breite. Hierzu wird ein neuer Spaltentyp `X' definiert, der sich wie
+eine `p'-Spalte verhlt, ohne da man jedoch die Breite explizit angeben
+mu. Stattdessen wird von `tabularx' die fr alle `X'-Spalten zur
+Verfgung stehende Gesamtbreite berechnet und jeder `X'-Spalte ein
+entsprechender Bruchteil davon zugewiesen. Eine mehrseitige Tabelle kann
+mit `ltxtable' auf eine bestimme Breite ausgetrieben werden, wofr auch
+die Pakete `longtable' und `tabularx' erforderlich sind.
+
+tabularx: CTAN: macros/latex/required/tools/
+ltxtable: CTAN: macros/latex/contrib/carlisle
+
+
+
+6.2.4 Wie kann ich erreichen, da Zahlen in einer Tabelle am
+Dezimaltrennzeichen ausgerichtet werden?
+
+Die LaTeX-Pakete `dcolumn' und `rccol' (erfordert `fltpoint') sind dazu
+geeignet. Letzteres gestattet auch das Runden der Zahlen.
+
+dcolumn: CTAN: macros/latex/required/tools/
+rccol: CTAN: macros/latex/contrib/rccol/
+
+
+
+6.2.5 Wie kann ich in einer tabular-Umgebung eine Spalte speziell
+setzen, ohne dies in jedem Eintrag zu wiederholen?
+
+Das Paket `array' erweitert die Umgebungen `array' und `tabular' um
+weitere Deklarationen, wie >, <, !, m oder p, in der Tabellenprambel.
+So wird bei ``>{text}'' der Teil ``text'' direkt vor die folgende Spalte
+eingefgt, so da beispielsweise nach
+
+ \begin{tabular}{c>{\scshape}cc}
+
+die zweite der drei Spalten in Kapitlchen gesetzt wird.
+
+array: CTAN: macros/latex/required/
+
+
+
+6.2.6 Wieso kann ich in einer tabular-Umgebung die letzte Spalte nicht
+mit \raggedright linksbndig setzen?
+
+\raggedright definiert die Anweisung \\ um, die in den Umgebungen
+`tabular' und `array' zur Markierung des Zeilenendes benutzt wird. In
+LaTeX2e und den Paketen `array' und `longtable' existiert daher seit
+Dezember 1994 die neue Anweisung \tabularnewline, die man fr diesen
+Zweck anstelle von \\ verwenden kann.
+Fr andere Pakete und ltere Versionen kann man auch folgenden Trick aus
+dem Buch `Der LaTeX-Begleiter' (siehe Abschnitt 2.4.1) anwenden:
+
+ \newcommand{\PreserveBackslash}[1]{%
+ \let\temp=\\#1\let\\=\temp}
+
+Statt einem einfachen \raggedright verwendet man in einer Tabelle dann
+\PreserveBackslash{\raggedright}.
+Ebenfalls ntzlich ist in diesem Zusammenhang die folgende Zeile
+
+ \usepackage[NewCommands]{ragged2e}
+
+zu Beginn des Dokuments. Damit wird eine bessere Trennung innerhalb
+eines mittels \raggedright linksbndig mit rechtem Flatterrand gesetzten
+Absatzes bewirkt.
+
+ragged2e: CTAN: macros/latex/contrib/ms/
+
+
+
+6.2.7 Wie erreiche ich, da mit `tabular' erstellte Tabellen bndig mit
+dem linken Rand gesetzt werden?
+
+Zwischen den Spalten einer `tabular', aber auch links von der ersten und
+rechts von der letzten Spalte, wird blicherweise ein Zwischenraum der
+Breite \tabcolsep eingefgt. Um diesen zu unterdrcken, mu man in die
+Tabellenprambel die Anweisung ``@{}'' einfgen, also beispielsweise
+
+ \begin{tabular}{@{}ll@{}}
+ ... % ^^^ ^^^
+ \end{tabular}
+
+Die Anweisung ``@{text}'' sorgt dafr, da ``text'' _statt_ eines
+Spaltenzwischenraums eingefgt wird. ``@{}'' unterdrckt also, da
+zwischen zwei Spalten Zwischenraum eingefgt wird. Daran sollte man auch
+bei \multicolumn-Anweisungen denken, die sich ber die erste bzw. letzte
+Spalte etwa einer dreispaltigen Tabelle erstrecken:
+
+ \multicolumn{2}{@{}l}{Spalten 1 und 2} & bla \\
+
+bzw.
+
+ bla & \multicolumn{2}{l@{}}{Spalten 2 und 3} \\
+
+
+6.3 Funoten, Endnoten etc. (*)
+
+
+6.3.1 Die Funoten sollen gesammelt am Ende des Kapitels erscheinen.
+
+
+endnotes: CTAN: macros/latex/contrib/misc/endnotes.sty
+
+
+
+6.3.2 Ich mchte meine Funoten auf jeder Seite neu beginnend
+durchzhlen, d.h. auf jeder Seite soll mit `1' begonnen werden.
+
+
+footnpag: CTAN: macros/latex/contrib/footnpag
+
+
+
+6.3.3 Ich mchte den maximal von den Funoten eingenommenen Platz auf 10
+Zeilen beschrnken. Wie?
+
+Das Lngenregister \dimen\footins gibt die maximale Hhe der Box mit den
+Funoten fr eine Seite an. Nach
+
+ \setlength{\dimen\footins}{10\baselineskip}
+
+wird dieser Platz von normalerweise 8 Inch (ca. 20,5 cm) auf ca. 10
+Zeilen beschrnkt.
+
+6.3.4 Wie erreiche ich eine andere Formatierung der Funoten?
+
+Mit dem Paket `footmisc' von Robin Fairbairns (hatte bis Januar 1998
+noch den Namen `footnote') kann man sehr einfach einige andere
+Formatierungen auswhlen. Ansonsten findet man im Buch `Der
+LaTeX-Begleiter' nhere Informationen.
+
+footmisc: CTAN: macros/latex/contrib/footmisc/
+
+
+
+6.3.5 Wie erhalte ich eine Funote innerhalb einer `figure' oder
+`table'? Es erscheint zwar eine Markierung, aber kein Funotentext. (*)
+
+In Gleitumgebungen funktionieren keine Funoten, da diese mitgleiten
+mten, was ohne sehr viel Aufwand nicht mglich ist. Abhilfe kann man
+dadurch schaffen, da man Funoten innerhalb einer \caption vermeidet
+und den Funotentext in die Unterschrift mit einbindet. Ansonsten kann
+man die Abbildung oder Tafel in eine `minipage'-Umgebung einklammern, so
+da der Funotentext mit in die Gleitumgebung gesetzt wird und somit
+mitgleiten kann. Die dann meist strende Abgrenzungslinie kann man mit
+\renewcommand{\footnoterule}{} innerhalb der `minipage'-Umgebung
+vermeiden.
+
+ \begin{figure}
+ \begin{minipage}{\linewidth}
+ \renewcommand{\footnoterule}{}
+ ... Abbildung mit \footnote{...} ...
+ \end{minipage}
+ \caption{ ... }
+ \end{figure}
+
+Eine weitere Mglichkeit bietet das Paket `threeparttable':
+
+ \begin{figure}
+ \begin{threeparttable}
+ Abbildung oder Tabelle mit Fu"snote\tnote{1}
+ \medskip
+ \begin{tablenotes}\footnotesize
+ \item[1] Wichtiger Fu"snotentext...
+ \end{tablenotes}
+ \end{threeparttable}
+ \caption{ ... }
+ \end{figure}
+
+
+threeparttable: CTAN: macros/latex/contrib/misc/threeparttable.sty
+
+
+
+6.3.6 Wie kann ich Funoten in mehreren Gruppen getrennt voneinander auf
+einer Seite erscheinen lassen?
+
+Das Paket `manyfoot' erlaubt die Deklaration zustzlicher
+Funotenebenen, die zudem noch auf zwei Arten gesetzt werden knnen.
+
+manyfoot: CTAN: macros/latex/contrib/ncctools/
+
+
+
+6.3.7 Wie erreiche ich, da meine Funoten nicht am Text ``hngen''
+sondern unten auf der Seite gesetzt werden?
+
+Das Paket `footmisc' bietet mit der Option `bottom' einen Weg, wenn
+durch die Deklaration \raggedbottom die Seitenhhe flattert. In diesem
+Fall setzt LaTeX die Funote mit etwas vertikalen Abstand
+(\skip\footins) an den Text, so da die Funoten ebenso mitflattern.
+Funoten werden normalerweise am Fue des Flietextes und nicht der
+Seite gesetzt, also _oberhalb_ einer eventuell vorhandenen unten
+plazierten Flieumgebung. Mit dem Paket `stfloats' werden die Funoten
+an die Unterkante des Satzspiegels verschoben.
+
+footmisc: CTAN: macros/latex/contrib/footmisc/
+stfloats: CTAN: macros/latex/contrib/sttools/
+
+
+
+6.3.8 Wie kann ich eine Funote in einer Kapitel- oder
+Abschnittsberschrift setzen?
+
+Wie in Frage 7.4.2 erlutert, mssen zerbrechliche Anweisungen wie
+\footnote in einem `moving argument' mit \protect geschtzt werden, also
+beispielsweise
+
+ \section{Titel des Abschnitts\protect\footnote{Fasse dich kurz!}}
+
+Bei Funoten ist dies jedoch nicht sinnvoll, da diese dann auch im
+Inhaltsverzeichnis und im lebenden Kolumnentitel auftauchen wrde. Hier
+ist es besser, das optionale Argument der berschriftsanweisungen zu
+verwenden:
+
+ \section[Titel des Abschnitts]%
+ {Titel des Abschnitts\footnote{Fasse dich kurz!}}
+
+
+6.4 Grafiken, Bilder, Farbe und andere Effekte (*)
+
+
+6.4.1 Wie kann ich Grafiken in mein (La)TeX-Dokument einfgen? (*)
+
+Die LaTeX-Pakete `graphics' bzw. `graphicx' definieren die Anweisung
+\includegraphics, welche einen einfachen Weg darstellt, die Einbindung
+von Grafiken in ein LaTeX-Dokument in einer weitgehend
+systemunabhngigen Syntax vorzunehmen. Die frher fr denselben Zweck
+verwendeten Anweisungen \psfig, \epsfig, \epsfbox usw. (enthalten in den
+Paketen `psfig', `epsf' und `epsfig') sollten nicht mehr verwendet
+werden, da sie teilweise fehlerhaft sind, nur fr ausgewhlte Treiber
+funktionieren und auch nicht weiterentwickelt werden.
+Neben \includegraphics werden weitere ntzliche Befehle zum Skalieren
+und Rotieren definiert. Die Gre der Grafik, die von LaTeX bentigt
+wird, um entsprechend Platz fr die Grafik zu lassen, wird bei
+Encapsulated-PostScript-(EPS-)Dateien direkt aus dem
+`BoundingBox'-Kommentar in der EPS-Datei gelesen. Bei anderen,
+insbesondere bei binr vorliegenden Grafikformaten wie `gif' oder `pcx'
+kann die Gre in einer begleitenden Textdatei bzw. im optionalen
+Argument der Anweisung \includegraphics angegeben werden. Mit dem
+Paketparameter `draft' des Paketes `graphics' kann man LaTeX
+veranlassen, in die dvi-Datei nur einen Rahmen in der Gre der Grafik
+statt des Verweises auf die Grafikdatei einzufgen, was das Betrachten
+beschleunigt und zum Korrekturlesen manchmal hilfreich ist.
+Die Grafikinformation kann bei EPS-Dateien sowohl als Vektoren als auch
+in Form von Angaben zur Position der einzelnen Grapkikpunkte
+(Pixelgrafik) enthalten sein. Wenn mglich, sollte man immer
+Vektorgrafiken bevorzugen, da sie ohne Qualittsverluste skaliert werden
+knnen. Ist man, wie bei gescannten Bildern, auf Pixelgrafiken
+angewiesen, so sollte man zur Vermeidung von Qualittsverlusten darauf
+achten, da die Auflsung der Grafik derjenigen des Druckers entspricht.
+Man bedenke auch, da Grautne nur mit besser auflsenden Ausgabegerten
+(mind. 600dpi, besser mehr) gut wiedergegeben werden.
+Um vorhandene Pixelgrafiken nach EPS zu wandeln, kann man die
+Exportfunktion etlicher Grafikprogramme nutzen. Es gibt darberhinaus
+die beiden Programme `jpeg2ps' und `tiff2ps', die sehr kompakte
+EPS-Dateien erzeugen. Sie erfordern Ausgabegerte, die `PostScript
+Level 2' beherrschen, wie beispielsweise alle modernen PS-Drucker und
+neue Ghostscript-Versionen. Alternativ kann man zur Konvertierung von
+JPEG nach EPS auch `imgtops2' verwenden, das in der EPS-Ausgabe
+DCT-Kompression nutzt und so sehr kompakte EPS-Dateien erzeugt. Zur
+Konvertierung von Pixelgrafiken, die im Format PNG, aber auch TIFF, JPEG
+und Netpbm vorliegen, in EPS fr Gerte mit PostScript Level 1, 2
+oder 3, gibt es das Programm `bmeps', fr TIFF auch `tif2eps', das
+Ghostscript voraussetzt. Ein weiteres Programm, welches eine Vielzahl
+von Grafikformaten konvertieren kann, ist `convert', das Bestandteil der
+Programmsammlung `ImageMagick' ist. Es steht ebenfalls fr viele
+Betriebssysteme zur Verfgung. Da die meisten dvi-Preview-Programme
+enthaltene EPS-Grafiken nicht darstellen knnen, empfiehlt es sich, die
+dvi-Datei nach PostScript zu wandeln und dann ein
+PostScript-Preview-Programm (`gv', `gsview', `ghostview', `Ghostscript'
+etc.) zu verwenden.
+Sehr ausfhrliche und gut verstndliche Hinweise zu diesem Thema enthlt
+Keith Reckdahls Artikel `Using Imported Graphics in LaTeX2e' (epslatex)
+und das Buch `The LaTeX Graphics Companion' von Michel Goossens u.a.
+sowie `TeX/LaTeX und Graphik, ein berblick ber die Verfahren' von
+Friedhelm Sowa (siehe Abschnitte 2.4.1 und 2.4.2).
+
+graphics/graphicx: CTAN: macros/latex/required/graphics/
+graphicx CTAN: macros/plain/graphics/
+(Plain-TeX):
+epslatex (Keith CTAN: info/epslatex.ps
+Reckdahl):
+ CTAN: info/epslatex.pdf
+Graphics and Colour
+with LaTeX (Patrick http://www.linmpi.mpg.de/~daly/latex/grf.htm
+W. Daly):
+LaTeX2e und Grafik
+(Sebastian http://www.loh-fi.de/howto/latex.htm
+Lohmeier):
+jpeg2ps: http://www.pdflib.com/jpeg2ps/
+ CTAN: nonfree/support/jpeg2ps/
+imgtops2: http://www.cs.washington.edu/homes/dougz/postscript/imgtops2/
+tiff2ps: CTAN: graphics/tiff/
+tif2eps: CTAN: support/pstools/tif2eps/
+bmeps: CTAN: support/bmeps/
+gif2eps: http://www.zib.de/Visual/software/
+ImageMagick: http://www.imagemagick.org/
+
+
+
+6.4.2 Wie kann ich erreichen, da anstelle der Grafiken nur leerer Platz
+in der Gre der Grafiken im LaTeX-Dokument erscheint?
+
+Mit der Option `draft' der Pakete `graphics' bzw. `graphicx'
+
+ \usepackage[draft]{graphicx}
+
+erreicht man, da statt der Grafiken nur ein Rahmen in Gre der Grafik
+gezeichnet wird. Zustzlich wird der Name der einzufgenden Datei in
+diesen Rahmen geschrieben.
+Tip: Verwendet man die Option `draft' in der Klassendeklaration, so gilt
+diese auch fr das Paket `graphicx'. Diese globale Option kann jedoch
+mit der Paketoption `final' wieder berschrieben werden.
+Will man weder Rahmen noch Dateinamen erhalten, so kann man das Paket
+`crop' in der folgenden Weise nutzen:
+
+ \usepackage[nographics]{crop}[2001/10/07]
+
+Den gegenteiligen Effekt erreicht man mit der Paketoption `notext'.
+
+crop: CTAN: macros/latex/contrib/crop/
+
+
+
+6.4.3 Wie kann ich mit TeX farbigen Text setzen?
+
+Das LaTeX-Bundle `graphics' enthlt das Paket `color', das Befehle zur
+Verfgung stellt, mit denen man Textteile einfrben, eine Box oder den
+Hintergrund einer Seite farbig hinterlegen kann. Dies funktioniert
+natrlich nur, wenn das Ausgabegert (Drucker, Bildschirm) dazu in der
+Lage ist und der dvi-Treiber die dazu notwendige Funktionalitt hat,
+entsprechende \special-Anweisungen mit den Farbbefehlen auszuwerten.
+Um das Paket `color' an verschiedene Ausgabegerte und dvi-Treiber
+anzupassen, mu eine entsprechende Definitionsdatei fr den jeweiligen
+Treiber vorhanden sein bzw. noch erstellt werden. Auf jedem System
+sollte in der Datei ``color.cfg'' eine dvi-Treiber-Definition als
+Default angegeben sein. Das Paket `color' lt sich dann wie folgt
+verwenden:
+
+ \usepackage{color}
+
+Will man in einem Dokument einen vom Standard abweichenden dvi-Treiber
+verwenden, so kann man den Namen der dvi-Treiber-Definition als
+Paket-Option angeben:
+
+
+ \usepackage[dvips]{color}
+
+erzeugt eine dvi-Datei mit Farb-\special-Anweisungen fr den
+dvi-PostScript-Treiber `dvips'. Danach kann man die entstehende
+dvi-Datei auch mit anderen dvi-Treibern bersetzen bzw. ausdrucken,
+jedoch werden in den meisten Fllen die Farb-\special-Anweisungen nicht
+erkannt und mit einer Warnung ignoriert.
+Eine genauere Beschreibung der einzelnen Anweisungen und der vorhandenen
+Definitionsdateien findet man in der Anleitung `grfguide' im Paket
+`graphics'.
+
+graphics/color: CTAN: macros/latex/required/graphics/
+
+
+
+6.4.4 Bei mit `XFig' erstellten und exportierten Zeichnungen erhalte ich
+bei der Einbindung in LaTeX den Fehler, da \SetFigFont nicht definiert
+ist. Was ist falsch?
+
+Das Programm `fig2dev', das XFig zum Wandeln und Exportieren von
+Fig-Bildern aufruft, hat in den Versionen vor Version 3.1pl1 einen
+Fehler, der dazu fhrt, da das Makro \SetFigFont nicht immer definiert
+ist. Nach einem Update des Paketes `Transfig', welches `fig2dev'
+enthlt, verschwindet der Fehler. Kann man auf den Update nicht warten,
+bietet sich auch als Einfachstlsung die Definition
+\newcommand{\SetFigFont}[3]{} in der Dokumentprambel an.
+
+transfig/fig2dev: CTAN: graphics/transfig/
+
+
+
+6.4.5 Bei Verwendung von PiCTeX erhalte ich die Meldung `No room for a
+new \dimen'. Wie kann ich das vermeiden?
+
+PiCTeX verwendet sehr viele von TeXs Zhler- und Lngenregistern und
+wenn noch weitere Pakete hinzugeladen werden, die ebenso Register
+bentigen, gehen die jeweils 256 vorhandenen, von denen LaTeX bereits
+nicht wenige bentigt, aus. Die erste Lsung besteht in der Verwendung
+des ConTeXt-Moduls `m-pictex' von Hans Hagen, das beim Laden von PiCTeX
+dafr sorgt, da statt Lngen- an einigen Stellen Glue-Register
+verwendet werden. Eine alternative Lsung besteht in der Verwendung des
+Paketes `pictexwd', eines von Andreas Schrell vernderten PiCTeX, das
+weniger Lngenregister benutzt.
+Eine weitere Lsungsmglichkeit besteht darin, die grere Anzahl an
+Registern zu nutzen, die e-TeX zur Verfgung stellt. Verwendet man LaTeX
+(Aufruf: elatex), mu das Paket `etex' vor PiCTeX geladen werden, um von
+e-TeX zu profitieren.
+
+m-pictex.tex, m-pictex.sty: CTAN: macros/context/cont-tmf.zip
+pictexwd: CTAN: graphics/pictex/addon/
+etex.sty ist momentan nur in teTeX und fpTeX enthalten.
+
+
+
+6.4.6 Was kann ich tun, wenn eine Grafik im EPS-Format beim Einfgen in
+ein LaTeX-Dokument Probleme bereitet?
+
+Nicht selten erzeugen Grafikprogramme beim Speichern der Ergebnisse im
+PostScript-Code keine oder eine fehlerhafte Boundingbox-Kommentarzeile.
+Diese Angabe ist jedoch beim Einfgen der Grafik in ein LaTeX-Dokument
+unbedingt erforderlich, da sonst der bentigte Platz nicht korrekt
+berechnet werden kann. Der im folgenden testweise eingefgte Rahmen
+zeigt die Gre der Boundingbox in Relation zur Grafik:
+
+ \usepackage{graphicx}
+ % ...
+ \begin{figure}
+ \setlength{\fboxsep}{-\fboxrule}\fbox{\includegraphics{dateiname}}
+ \end{figure}
+
+Ist die Boundingbox-Zeile fehlerhaft, kann folgendermaen vorgegangen
+werden:
+
+ Manuelle Korrektur:
+
+ Man lade die EPS-Datei in einen PostScript-Viewer und notiere sich
+ die Koordinaten der linken unteren (ll,lr) und der rechten oberen
+ (ul,ur) Ecke des interessierenden Teils der Grafik, wobei die
+ Maeinheit bp (big points) verwendet werden mu. Diese Werte fge
+ man mit Hilfe eines ASCII-Editors im Anschlu an die Zeile
+ ``%!PS-Adobe ...'' am Anfang der EPS-Datei hinzu bzw. korrigiere
+ die vorhandene Angabe entsprechend:
+
+ %%BoundingBox: ll lr ul ur
+
+ Statt des Eintrags in die EPS-Datei knnen die Werte auch als
+ optionale Parameter der `\includegraphics'-Anweisung angegeben
+ werden:
+
+ \includegraphics[bb= ll lr ul ur]{dateiname}
+
+
+ Automatische Korrektur:
+
+ Man verwende das Programm `epstool' in der folgenden Weise:
+
+ epstool -b -c -oausgabedatei.eps eingabedatei.eps
+
+ In der Datei ``eingabedatei.eps'' befinde sich die fehlerhafte
+ Grafik, danach enthlt ``ausgabedatei.eps'' die korrigierte
+ Grafik. `epstool' erfordert die vorherige Installation des
+ PostScript-Interpreters `Ghostscript'.
+ Alternativ dazu kann versucht werden, das Problem unter Verwendung
+ des Programms `epstopdf' zu lsen:
+
+ epstopdf --nogs --outfile=ausgabedatei.eps eingabedatei.eps
+
+ Liegt die Grafik in Form einer einseitigen PostScript-Datei vor,
+ kann man mit Hilfe des Programms `ps2eps' versuchen, diese in eine
+ EPS-Datei mit korrekter BoundingBox-Angabe umzuwandeln:
+
+ ps2eps eingabedatei.ps
+
+ `ps2eps' erfordert ebenfalls das Programm `Ghostscript' sowie
+ `perl'.
+
+Sollte trotz korrekter Angabe der BoundingBox ein ungnstiges Ergebnis
+entstehen, kann es daran liegen, da die EPS-Datei flschlicherweise
+PostScript-Anweisungen enthlt, die auch den Bereich auerhalb der
+BoundingBox verndern. Mit der Option [clip] der Anweisung
+`\includegraphics' wird die Ausgabe auf den Bereich der BoundingBox
+beschrnkt.
+
+epstool/gsview: ftp://support/ghostscript/ghostgum/
+epstopdf: http://www.tug.org/applications/pdftex/
+ps2eps: CTAN: support/ps2eps/
+Ghostscript (GPL): CTAN: support/ghostscript/gnu/
+Ghostscript (AFPL): CTAN: nonfree/support/ghostscript/aladdin/
+
+
+
+6.4.7 Warum werden Pixelgrafiken in pdf-Dateien, die ich mit pdfTeX
+erzeugt habe, verzerrt oder mit falschen Farben dargestellt?
+
+Vermutlich ist die Ursache die veraltete fehlerhafte
+pdfTeX-Version 0.13d. Abhilfe schafft die Verwendung einer aktuellen
+Version (z.B. 0.14f oder neuer). Bei dieser Gelegenheit empfiehlt es
+sich, die im Zusammenhang mit dem LaTeX-Paket `graphicx' wichtige Datei
+``pdftex.def'' und das LaTeX-Paket `hyperref' ebenfalls zu erneuern.
+
+pdftex.def: http://www.tug.org/applications/pdftex/
+~: CTAN: macros/latex/required/graphics
+hyperref: CTAN: macros/latex/contrib/hyperref/
+~: http://www.tug.org/applications/hyperref/
+
+
+
+6.4.8 Wie kann ich unter Windows Bilder, Grafiken etc. mit LaTeX
+verwenden?
+
+Um Bilder u.. aus Windows-Programmen in LaTeX einzubinden, sollte man
+diese im EPS-Format in eine Datei drucken. Da es mit den EPS-Dateien,
+die die Standard-EPS-Druckertreiber unter Windows erzeugen, immer wieder
+zu Problemen kommt, sollte man stattdessen die PostScript-Druckertreiber
+von Adobe installieren (siehe Frage 11.3.6).
+Damit die EPS-Datei nun problemlos und korrekt unter LaTeX mit der
+Anweisung \includegraphics eingebunden werden kann, ist die
+Bounding-Box-Angabe in der Datei zu bestimmen und eventuell zu
+korrigieren (siehe Frage 6.4.6).
+
+6.4.9 Woher kann ich eine Dokumentation zum (La)TeX-Paket `pictex'
+bekommen?
+
+Leider ist die Originaldokumentation nur kuflich von der Firma
+``Personal TeX, Inc.'' zu erhalten. Ersatzweise kann man die frei
+verfgbare Dokumentation zu dem Programm `mathspic' verwenden.
+`mathspic' ist ein unter DOS/Windows verwendbares Filterprogramm zum
+vereinfachten Erstellen von PiCTeX-Grafiken.
+
+Personal TeX, Inc.: http://www.pctex.com
+mathspic: CTAN: graphics/pictex/mathspic/mpicm21.pdf
+
+
+
+--- DE-TeX-FAQ Ende Teil 6 ---
diff --git a/help/de-tex-faq/part7 b/help/de-tex-faq/part7
new file mode 100644
index 0000000000..cfb6fe8ec8
--- /dev/null
+++ b/help/de-tex-faq/part7
@@ -0,0 +1,1047 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!aanews.merit.edu!news.cc.uic.edu!news.uchicago.edu!yellow.newsread.com!netaxs.com!newsread.com!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-ber1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 7 of 11)
+Supersedes: <de-tex-faq-7-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:17 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 1018
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-7-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975397 891 134.100.9.52 (19 Sep 2003 12:43:17 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:17 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117405 de.answers:9382 news.answers:258271
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part7
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 7 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+7 TeX, LaTeX, Makros etc. (III)
+
+
+7.1 Gliederung, Inhalts-, Abbildungs- und andere Verzeichnisse
+
+
+7.1.1 Beim Formatieren von \tableofcontents erhalte ich sehr viele
+Meldungen mit ``overfull \hbox''. Woran liegt das?
+
+Die Seitennummer wird in eine Box der Breite \@pnumwidth gesetzt. Der in
+den Standardklassen hierfr verwendete Wert von 1.55em kann in manchen
+Situationen (Seitennummer>=1000, breiterer Font) zu klein sein. Abhilfe:
+
+ \renewcommand{\@pnumwidth}{2em}% statt `2em' evtl. groesserer Wert
+
+Eventuell mu man dann auch den Wert im Makro \@tocrmarg anpassen. Da
+man ein internes Makro ndert, ist diese Anweisung in eine .sty-Datei
+oder mit \makeatletter ... \makeatother geklammert in die
+Dokumentprambel zu schreiben.
+Lngere Abschnittsnummern knnen eine andere Ursache dieses Fehlers
+sein. Hier mu man in den Definitionen der Makros \l@<type>, wie z.B.
+\l@section, im Aufruf des Makros \@dottedtocline das dritte Argument
+entsprechend vergrern. Nheres hierzu im Buch ``Der LaTeX-Begleiter''
+(siehe Frage 2.4.1).
+
+7.1.2 Bei einem Artikel mit sehr vielen Abschnitten und Unterabschnitten
+``klebt'' die berschrift im `toc' direkt hinter der Abschnittsnummer.
+Kann man den Platz verbreitern?
+
+In der Datei der verwendeten Klasse wird das Aussehen einer Zeile in den
+Verzeichnissen durch ein Makro namens `\l@<typ>' festgelegt. Fr eine
+\subsection ist dies das Makro \l@subsection, das z.B. in
+``article.cls'' durch
+
+ \newcommand{\l@subsection}{\@dottedtocline{2}{1.5em}{2.3em}}
+
+definiert ist. Die Lnge 1.5em gibt an, wie breit der Einschub vom
+linken Rand ist, die Lnge 2.3em, wie breit der Platz fr die
+Abschnittsnummer sein soll. Will man diese vergrern, kann man dies
+beispielsweise mit
+
+ \renewcommand{\l@subsection}{\@dottedtocline{2}{1.5em}{3.3em}}
+
+in einer .sty-Datei oder mit \makeatletter ... \makeatother geklammert
+in der Dokumentprambel. Mehr dazu findet man im Buch ``Der
+LaTeX-Begleiter'' (siehe Frage 2.4.1).
+Sehr viel einfacher geht dies mit dem Paket `tocloft', das einem die
+volle Kontrolle ber die Formatierung der einzelnen Verzeichnisse
+erlaubt. Es bentigt noch das Paket `stdclsdv'.
+
+tocloft: CTAN: macros/latex/contrib/tocloft
+stdclsdv: CTAN: macros/latex/contrib/stdclsdv
+
+
+
+7.1.3 Warum werden die durch \subsubsection angegebenen Abschnitte nicht
+mehr numeriert?
+
+Jeder Gliederungsebene ist in LaTeX eine Nummer zugeordnet:
+
+-1 part 1 section 3 subsubsection 5 subparagraph
+ 0 chapter 2 subsection 4 paragraph
+
+Bei der Klasse `article' existiert der Befehl \chapter nicht, und \part
+erhlt die Nummer 0 zugeordnet.
+Die Gliederungsebene, bis zu der numeriert wird, legt der Zhler
+`secnumdepth' fest. Die Standardklassen setzen diesen Zhler auf den
+Wert 2, also bis \subsection. Um auch fr tieferliegende Ebenen eine
+Numerierung zu erhalten, mu der Zhler entsprechend erhht werden. Mit
+\setcounter{secnumdepth}{4} werden die berschriften der Ebenen bis
+\paragraph mit einer Nummer versehen, auch wenn dies nur in den
+allerwenigsten Fllen sinnvoll ist.
+Um die Numerierung von berschriften im Dokument vollstndig zu
+verhindern, mu man den Zhler `secnumdepth' auf den Wert -2 gesetzt
+werden. Ein Inhaltsverzeichnis wird dennoch erzeugt, da dies durch den
+Zhler `tocdepth' gesteuert wird.
+
+7.1.4 Wie erreiche ich, da Abschnittsberschriften ein anderes Aussehen
+bekommen?
+
+Die LaTeX-Anweisungen \section, \subsection etc. werden in den
+Klassendateien wie z.B. ``article.cls'' definiert. (In LaTeX 2.09 wurden
+sie dagegen in den Hilfsdateien wie z.B. ``art10.sty'' definiert.) Die
+Definitionen verwenden dabei die allgemeinere Anweisung \@startsection,
+in deren sechstem Argument man Formatieranweisungen angeben kann. Zur
+nderung kopiert man sich die Definition aus ``article.cls'' bzw. die
+entsprechende Klassendatei in eine .sty-Datei, ndert \newcommand (bzw.
+\def) zu \renewcommand und fgt die Anweisung \centering zu den
+bestehenden Formatieranweisungen hinzu:
+
+ \renewcommand{\section}{%
+ \@startsection {section}{1}{\z@}%
+ {-3.5ex plus -1ex minus -.2ex}%
+ {2.3ex plus.2ex}%
+ {\normalfont\Large\bfseries \centering}}
+
+Man vergesse nicht, diese Definition mit \makeatletter ... \makeatother
+zu klammern oder in eine .sty-Datei zu schreiben!
+Mit dem Paket `titlesec' knnen Abschnittsberschriften noch einfacher
+angepat werden. Beispielsweise erhlt man mit
+
+ \usepackage{titlesec}
+ \titleformat{\section}%
+ {\normalfont\Large\bfseries \filcenter}%
+ {\thesection}%
+ {1em}%
+ {}%
+
+eine Zentrierung der \section-berschriften. Hierbei wurde \filcenter,
+eine spezielle Anweisung des Pakets verwendet, jedoch kann auch
+\centering verwendet werden. Die Anweisung \titleformat hat ein
+optionales Argument, mit dem man beispielsweise wie bei \paragraph
+eingebettete oder in den Rand ragende berschriften erhalten kann.
+Abstnde zwischen berschrift und Text werden mit der Anweisung
+\titlespacing vorgegeben.
+Ebenso erleichtert das Paket `sectsty' die nderung der
+Abschnittsberschriften in den LaTeX-Standardklassen.
+Bei Verwendung einer aktuellen Version der -Klassen lassen sich
+beispielweise die Schriftart, die Ausrichtung sowie weiteres ebenfalls
+leicht anpassen.
+
+titlesec: CTAN: macros/latex/contrib/titlesec
+sectsty: CTAN: macros/latex/contrib/sectsty
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+
+
+
+7.1.5 Warum werden die durch \subsubsection angegebenen Abschnitte nicht
+mehr ins Inhaltsverzeichnis aufgenommen?
+
+Ebenso wie der Zhler `secnumdepth' die Gliederungsebene festlegt, bis
+zu der Abschnitte numeriert werden, legt der Zhler `tocdepth' die
+Gliederungsebene fest, bis zu der Abschnitte in das Inhaltsverzeichnis
+aufgenommen werden. Beispielsweise werden nach der Anweisung
+\setcounter{tocdepth}{4} alle Abschnitte einschlielich der
+\paragraph-Ebene in das Inhaltsverzeichnis aufgenommen (siehe dazu Frage
+7.1.3). Diese Anweisung mu in der Prambel, auf jeden Fall vor
+\tableofcontents verwendet werden.
+
+7.1.6 Wie kann ich verhindern, da z.B. \subsection usw. im Anhang in
+das Inhaltsverzeichnis aufgenommen werden?
+
+Der Zhler `tocdepth' wird nur beim \tableofcontents ausgewertet, also
+nur beim Satz und nicht bei der Erstellung der .toc-Datei. Daher hat
+eine nderung von `tocdepth' nach dem Befehl \appendix keine Wirkung.
+Stattdessen mu man dafr sorgen, da die nderung von `tocdepth' mit
+\addtocontents in die .toc-Datei gelangt:
+
+ \documentclass{article}
+ %
+ \newcommand{\settocdepth}[1]{%
+ \addtocontents{toc}{\protect\setcounter{tocdepth}{#1}}}
+ %
+ \begin{document}
+ \tableofcontents
+ \section{Abschnitt}
+ \subsection{Unterabschnitt}
+ blabla
+ %
+ \appendix
+ \settocdepth{1}
+ %
+ \section{Abschnitt}
+ \subsection{Unterabschnitt}
+ \subsubsection{Unterunterabschnitt}
+ blabla
+ \end{document}
+
+
+7.1.7 Wie kann ich erreichen, da Literatur-, Abbildungs-, Tabellen- und
+sonstige Verzeichnisse in das Inhaltsverzeichnis mit aufgenommen werden?
+
+Diese Verzeichnisse werden normalerweise nicht in das Inhaltsverzeichnis
+aufgenommen. Wenn dies dennoch notwendig ist oder erwnscht wird, kann
+man es am einfachsten mit den Dokumentklassen des KOMA-Script-Paketes
+erreichen, da diese Klassen die hierfr gedachten Optionen `liststotoc',
+`bibtotoc' bzw. `bibtotocnumbered' und `idxtotoc' kennen.
+Bei Verwendung anderer Klassen kann eventuell das Paket `tocbibind'
+weiterhelfen. Ansonsten knnte man als letzte Lsung unmittelbar vor die
+Anweisungen \bibliography, \listoftables, \listoffigures und \printindex
+die Anweisungen
+
+ \clearpage
+ \addcontentsline{toc}{section}{\refname}
+
+schreiben. Statt \refname ist evtl. \bibname bzw. \listtablename,
+\listfigurename oder \indexname einzusetzen; `section' kann bei
+Verwendung der Dokumentklassen `report' und `book' durch `chapter'
+ersetzt werden. Auerdem mu bei Verwendung der Klassenoption `twoside',
+die bei `book' voreingestellt ist, \clearpage durch \cleardoublepage
+ersetzt werden.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+tocbibind: CTAN: macros/latex/contrib/tocbibind/
+
+
+
+7.1.8 Wie kann ich die Formatierung der automatisch erzeugten Inhalts-,
+Abbildungs- und Tabellenverzeichnisse ndern?
+
+Mit dem Paket `titletoc', das zusammen mit dem Paket `titlesec' verteilt
+und dokumentiert wird, kann man sehr frei die Formatierung der
+Inhaltsverzeichniseintrge ndern. Daneben gibt es noch das Paket
+`tocloft', mit dem man ebenso die Formatierung des Inhalts-, Abbildungs-
+und Tabellenverzeichnisses anpassen kann.
+
+titletoc/titlesec: CTAN: macros/latex/contrib/titlesec/
+tocloft: CTAN: macros/latex/contrib/tocloft/
+
+
+
+7.1.9 Wie kann ich mit \ref nicht nur die Abschnittsnummer, sondern auch
+den Text einer Abschnittsberschrift erhalten?
+
+Das Paket `titleref' stellt hierzu die Anweisung \titleref, der analog
+zu \ref und \pageref den Text einer Abschnittsberschrift oder
+Abbildungsunterschrift liefert. Hierzu mu die Anweisung \label _nach_
+den Abschnittsanweisungen und \caption erfolgen und darf _nicht_ im
+Argument angegeben werden.
+Im `hyperref'-Bndel existiert mit `nameref' ein weiteres Paket, das
+diese Funktionalitt anbietet.Dieses definiert die Anweisung \nameref.
+Insbesondere im Zusammenhang mit der Erzeugung von pdf-Dateien sollte
+diese Lsung bevorzugt werden.
+
+titleref: CTAN: macros/latex/contrib/misc/titleref.sty
+nameref: CTAN: macros/latex/contrib/hyperref/
+
+
+
+7.1.10 Wie kann ich in einem Stichwortverzeichnis oder einem
+Literaturverzeichnis noch Text zwischen die berschrift und die
+Verzeichnisliste bekommen?
+
+Hierfr mu man die Umgebung `thebibliography' bzw. `theindex'
+umdefinieren. Man kopiert sich dazu die Definition dieser Umgebungen aus
+der Klassendatei in eine eigene Paketdatei, ersetzt die Anweisung
+\newenvironment durch \renewenvironment. Anschlieend fgt man zwischen
+der berschrift, die mit \section oder \chapter erzeugt wird und der
+Listen-Umgebung die Anweisungen
+
+ \renewenvironment{\thebibliography}[1]{%
+ \section*{\refname
+ \@mkboth{\MakeUppercase\refname}{\MakeUppercase\refname}}%
+ % vvvv--- neu
+ \thebibliographyhook
+ \renewcommand{\thebibliographyhook}{}% Hook ruecksetzen
+ % ^^^^--- neu
+ \list{\@biblabel{\arabic{enumiv}}}%
+ ...
+
+wie hier fr `thebibliography' gezeigt, ein.
+Fr das Stichwortverzeichnis werden diese Zeilen, diesmal mit
+\theindexhook, in die entsprechend zu ndernde Definition der Umgebung
+`theindex' eingefgt. Bei dieser mu man darauf achten, die beiden
+Zeilen _in_ das optionale Argument der Anweisung \twocolumn einzufgen,
+wenn der Text ber beide Spalten gehen soll.
+Schlielich werden diese ``Haken'' mit der neuen Definition
+
+ \newcommand{\thebibliographyhook}{} % Standard-Wert: kein Text
+ \newcommand{\theindexhook}{} % Standard-Wert: kein Text
+
+auf einen Wert gesetzt, der das bisherige Verhalten nicht verndert.
+Will man nun zustzlichen Text einfgen, so wird der jeweilige Hook
+direkt vor dem entsprechenden Verzeichnis per \renewcommand auf den
+gewnschten Text gesetzt.
+Von Version 2.6c an bieten die Dokumentklassen des KOMA-Script-Paketes
+einen noch einfacheren Weg mit den Anweisungen `\setbibpreamble' und
+`\setindexpreamble'.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+
+
+
+7.1.11 Wie kann ich mehrere Verzeichnisse in der Art des
+Stichwortverzeichnisses, z.B. ein zustzliches Autorenverzeichnis,
+anlegen?
+
+Zu diesem Zweck geeignet sind die LaTeX-Pakete `camel' und `multind'.
+
+camel: CTAN: macros/latex/contrib/camel/
+multind: CTAN: macros/latex209/contrib/misc/multind.sty
+
+
+
+7.1.12 In meinem LaTeX-Dokument fehlen die Eintrge im Inhalts-,
+Tabellen- und Abbildungsverzeichnis, obwohl die Dateien .toc, .lot bzw.
+.lof vorhanden sind. Ich benutze das Paket `fancybox'.
+
+Diese Besonderheit verschwindet mit einer aktuelleren Version des
+Paketes `fanycbox', mindestens Version 1.3. Um sicherzustellen, da man
+eine einigermaen aktuelle Version bentzt, kann man beim Laden des
+Pakets das Datum angeben:
+
+ \usepackage{fancybox}[2000/09/19]
+
+
+fancybox: CTAN: macros/latex/contrib/fancybox/
+
+
+
+7.1.13 Wie mache ich alle Labels von Querverweisen sichtbar und wie
+erhalte ich eine Liste dieser Labels?
+
+Mit dem Paket `showkeys' aus dem `tools'-Bndel werden alle Querverweise
+im Dokument als Marginalien gesetzt.
+Eine Liste der Labels eines Dokuments erhlt man mit Hilfsdokument
+``lablst.tex'', das zu Beginn den Namen des Dokuments, die
+Dokumentklasse als auch die durch Kommata getrennte Liste aller
+verwendeten Pakete erfrgt. Dieses Hilfsdokument liegt jeder
+LaTeX-Verteilung bei.
+
+lablst.tex: CTAN: macros/latex/base/
+showkeys: CTAN: macros/latex/required/tools/
+
+
+
+7.1.14 Wie kann ich erreichen, dass Referenzen in einem LaTeX-Dokument,
+das ich nach PDF umwandle, als _Hyperlinks_ angezeigt werden, und kann
+man auch _Bookmarks_ (Lesezeichen) automatisch entsprechend dem
+Inhaltsverzeichnis erstellen lassen?
+
+All dies und vieles mehr wird automatisch von dem Paket `hyperref'
+erledigt. Neben der automatischen Erzeugung von _Hyperlinks_ und
+_Bookmarks_ stellt das Paket zustzliche Befehle zur Verfgung, mit
+denen Benutzer ihren Dokumenten weitere Hypertext-Elemente hinzufgen
+knnen. Auch das Setzen bestimmter PDF-Dokumenteigenschaften
+(Autorinformationen, Seitenbergnge) und die ``Steuerung'' des
+`acroread' aus einem Dokument heraus sind mit dem Paket mglich.
+
+hyperref: CTAN: macros/latex/contrib/hyperref/
+hyperref (beta-Version): http://www.tug.org/applications/hyperref/
+
+
+
+7.1.15 Um PDF zu erzeugen, binde ich das Paket `hyperref' ein, aber beim
+Betrachten mit `acroread' werden keine _Hyperlinks_ und auch keine
+_Bookmarks_ angezeigt. Seltsamerweise zeigen `xdvi' bzw. `yap' bei
+Betrachten der dvi-Datei korrekte _Hyperlinks_ an.
+
+Da es sehr viele Methoden gibt, LaTeX-Dokumente in PDF zu wandeln, wobei
+die dafr verwendeten Programme jeweils eine andere Notation verwenden,
+wie Links angegeben werden, ist `hyperref' auf die Verwendung von
+`Treibern' angeweisen, die fr jede Methode der PDF-Erstellung
+festlegen, wie Links spezifiziert werden.
+Wird kein Treiber explizit angegeben (als Paketoption; die Dokumentation
+erklrt, wie das geht), so muss `hyperref' raten, welcher Treiber zu
+verwenden ist. Wird pdfTeX zur bersetzung verwendet, so wird
+automatisch der passende Treiber verwendet; bei Benutzung von LaTeX ist
+der Standardtreiber jedoch fast immer `hypertex', was beispielsweise von
+`xdvi' und `yap' verstanden wird, jedoch zur Umwandlung in PDF
+ungeeignet ist.
+Wenn dieser (falsche) Treiber verwendet wird, so ist in der
+Protokolldatei die Zeile
+
+
+ *hyperref using default driver hypertex*
+
+zu finden.
+In diesem Fall mu entweder ein Treiber explizit als Paketoption
+angegeben werden (Vorsicht, dies kann dazu fhren, da nun die
+bersetzung mit pdfTeX nicht mehr funktioniert!), oder es mu ein
+passender Standardtreiber eingestellt werden.
+Hierfr eignet sich die Datei ``hyperref.cfg'', die von `hyperref'
+automatisch nachgeladen wird, wenn sie (an passender Stelle) existiert.
+Ob eine solche Datei existiert und geladen wird, ist aus der
+Protokolldatei ersichtlich.
+Wenn man PDF mit LaTeX, `dvips' und Acrobat Distiller erstellt, ist der
+korrekte Treiber `dvips'. Diesen legt man als Standardtreiber fest,
+indem man der Datei ``hyperref.cfg'' die folgenden Zeilen hinzufgt
+(bzw. eine Datei mit diesem Inhalt neu erstellt):
+
+ \@ifundefined{pdfoutput}{%
+ \let\pdfoutput=\@undefined
+ \ExecuteOptions{dvips}%
+ }{}%
+
+
+7.1.16 Wieso werden, wenn ich unter Verwendung des Pakets `hyperref' auf
+dem Umweg ber PostScript pdf-Dateien erzeuge (mit `ps2pdf' oder `Adobe
+Acrobat Distiller'), pltzlich alle Texte, die als Links dienen,
+insbesondere die Abschnittsberschriften im Inhaltsverzeichnis nicht
+mehr umbrochen?
+
+Das Paket `hyperref' kennt die Option `breaklinks', die festlegt, ob
+Links umbrochen werden drfen. Diese Option ist bei Verwendung von
+pdfLaTeX automatisch aktiv, bei `dvips' oder `ps2pdf' aber nicht, da der
+im letzteren Fall verwendete pdfmark-Mechanismus einen Umbruch von Links
+nicht zult. Es ist in diesem Fall also auf keinen Fall mglich, den
+Umbruch von Links ``verlustfrei'' zuzulassen. Eine saubere Lsung dieses
+Dilemmas besteht zur Zeit ausschlielich in der Verwendung eines
+Systems, das den Linkumbruch erlaubt, wie etwa pdfTeX oder VTeX.
+Man knnte die Paketoption `breaklinks' bei `hyperref' auch direkt
+angeben, mu dann aber damit leben, da die im Umbruchfall erstellten
+Links nicht oder nur eingeschrnkt funktionieren.
+Ein total kaputtes Inhaltsverzeichnis kann man weiterhin durch Angabe
+der Option `linktocpage' vermeiden, die bewirkt, da die Links im
+Inhaltsverzeichnis den Seitenangaben statt den Abschnittstiteln
+unterlegt werden.
+
+7.1.17 Wie erstelle ich ein Glossar?
+
+Um ein Wortverzeichnis mit Erklrungen oder im weiteren Sinne ein
+Verzeichnis von benutzten Begriffen mit Erklrungen, wie beispielsweise
+von Formelzeichen oder von Abkrzungen, zu erstellen, bietet LaTeX mit
+den Anweisungen \makeglossary und \glossary die Mglichkeit, Eintrge
+vorzunehmen. Jedoch verbleibt es beim Autor, diese Eintrge zu sortieren
+und zu formatieren.
+Um die Eintrge zu sortieren wird meist `makeindex', `xindy' oder
+BibTeX, eventuell ergnzt um ein Zusatzprogramm, verwendet. Zur
+Formatierung und zur leichteren oder differenzierteren Eingabe verwendet
+man ein entsprechendes LaTeX-Paket.
+Das Paket `nomencl' ist entstanden, um Verzeichnisse von Formelzeichen
+anzulegen, kann aber darberhinaus noch mehr. Datenbanken mit
+Abkrzungen etc. verwaltet das Paket `gloss' mit Hilfe von BibTeX. Das
+Tool `glosstex' erstellt automatisch ein Glossar, ein
+Abkrzungsverzeichnis oder ganz allgemein sortierte Listen. Es
+kombiniert die Funktionalitt von `acronym', `nomencl' und `glotex' und
+kann ebenfalls Datenbanken verwalten. Mit dem Paket `makeglos' kann in
+ein Dokument ein Glossar eingebunden werden, das beispielsweise mit
+`makeindex' oder `xindy' erstellt wurde. Dieses Paket ist weniger
+umfangreich als `glosstex'.
+
+nomencl: CTAN: macros/latex/contrib/nomencl
+gloss: CTAN: macros/latex/contrib/gloss
+glosstex: CTAN: support/glosstex/
+acronym: CTAN: macros/latex/contrib/acronym
+glotex: CTAN: indexing/glo+idxtex/
+makeglos: CTAN: macros/latex/contrib/makeglos
+
+
+
+7.2 Literaturzitate, Literaturverzeichnis, BibTeX (*)
+
+
+7.2.1 Wie kann ich im Text mit dem Autor/Jahreszahl o.. zitieren?
+
+Hierfr gibt es eine grere Anzahl von Paketen, wie `natbib', `theapa'
+oder `cite', die dies erlauben.
+
+natbib: CTAN: macros/latex/contrib/natbib/
+theapa: CTAN: macros/latex209/contrib/theapa/
+cite: CTAN: macros/latex/contrib/cite/
+
+
+
+7.2.2 Wie kann ich das BibTeX-Stylefile xyz.bst so abndern, da an
+Stelle X ein/kein Komma/Punkt erscheint, da der Eintrag Y anders
+formatiert wird etc.?
+
+Die Programmiersprache von BibTeX, in der die .bst-Dateien geschrieben
+sind, ist in der Datei ``btxhak.tex'' beschrieben, die jedem
+BibTeX-Paket beiliegen sollte. Bevor man diese fr die meisten
+ungewohnte Sprache lernt, sollte man zuerst berprfen, ob die eigenen
+Wnsche schon durch das Paket `custom-bib' abgedeckt werden knnen.
+Dieses Paket enthlt ein mengesteuertes, in TeX selbst geschriebenes
+Erzeugungsprogramm, das aus einer Master-bst-Datei eine bst-Datei mit
+den ausgewhlten Eigenschaften erzeugt.
+
+custom-bib: CTAN: macros/latex/contrib/custom-bib/
+btxdoc/btxhak: CTAN: biblio/bibtex/distribs/doc/
+
+
+
+7.2.3 Gibt es ans Deutsche angepate .bst-Dateien? (*)
+
+Ja, zum Beispiel kann man mit dem in Frage 7.2.2 genannten Paket
+`custom-bib' .bst-Dateien fr verschiedene Sprachen, darunter auch
+Deutsch, generieren.
+Unter http://www.fh-hamburg.de/pers/Lorenzen/bibtex/ findet man in den
+Dateien ``abbrvdin.zip'', ``alphadin.zip'', ``plaindin.zip'',
+``unsrtdin.zip'' und ``natdin.zip'' an DIN angepate
+BibTeX-Style-Dateien. ``natdin.bst'' ermglicht
+Verfasser-Jahr-Zitierweisen zusammen mit DIN-Zitierstandard. Der
+BibTeX-Style ``dinat.bst'' ist eine verbesserte Versionen von
+``natdin.bst''.
+
+Online-Tutorial: http://www.din1505.informationskompetenz.net/
+dinat: CTAN: biblio/bibtex/contrib/german/dinat/
+
+
+Auerdem gibt es folgende angepate .bst-Dateien und -Pakete (ohne
+Gewhr, unvollstndig, Reihenfolge ist _keine_ Wertung):
+
+abstyles: CTAN: biblio/bibtex/contrib/abstyles/
+germbib: CTAN: biblio/bibtex/contrib/germbib/
+geralpha: CTAN: obsolete/biblio/bibtex/contrib/geralpha/
+
+
+
+7.2.4 Wie kann ich statt der eckigen Klammern [1] im Text bzw. im
+Literaturverzeichnis hochgestellte Ziffern, runde Klammern (1) oder
+Schrgstriche /1/ verwenden?
+
+Fr die Form der Labels im Text ist die interne Anweisung \@cite, fr
+die Form im Literaturverzeichnis die interne Anweisung \@biblabel
+anzupassen. Deren Standarddefinitionen lauten:
+
+ \newcommand{\@cite}[2]{[{#1\if@tempswa , #2\fi}]}
+ \newcommand{\@biblabel}[1]{[#1]}
+
+Will man statt der eckigen Klammern Schrgstriche, so lauten die
+Redefinitionen
+
+ \renewcommand{\@cite}[2]{/{#1\if@tempswa , #2\fi}/}
+ \renewcommand{\@biblabel}[1]{/#1/}
+
+Nicht vergessen: Redefinitionen von internen Anweisungen (= enthalten
+ein `@' im Namen) mssen entweder in ein .sty-File geschrieben oder in
+der Prambel des Dokuments durch \makeatletter ... \makeatother
+geklammert werden!
+Die Pakete `cite' und `overcite' definieren Befehle, wie \citeleft und
+\citeright, die die Klammern erzeugen und die der Benutzer mit
+\renewcommand sehr einfach umdefinieren kann. Nach
+
+ \usepackage{cite}
+ \renewcommand{\citeleft}{(}
+ \renewcommand{\citeright}{)}
+
+bekommt man statt eckiger Klammern [1] runde Klammern (1).
+Das Paket `overcite' erlaubt es auerdem, Zitatstellen im Text mit
+hochgestellten Ziffern zu markieren.
+
+cite, overcite: CTAN: macros/latex/contrib/cite/
+
+
+
+7.2.5 Wie erreiche ich, da innerhalb eines \cite im Dokumenttext
+umbrochen werden darf?
+
+Das Paket `cite' definiert die Zitieranweisung von LaTeX so um, da ein
+Zeilenumbruch mglich ist.
+
+cite: CTAN: macros/latex/contrib/cite/
+
+
+
+7.2.6 Wie kann ich verhindern, da die Wrter im Titel eines
+.bib-Eintrages kleingeschrieben werden?
+
+Entweder den Titel komplett oder alle gro zu schreibenden Wrter
+einzeln noch einmal klammern, also in der .bib-Datei statt
+
+ title = {Fragen und Antworten}
+
+einfach
+
+ title = {{Fragen und Antworten}}
+
+oder
+
+ title = {{Fragen} und {Antworten}}
+
+eingeben.
+Eine alternative Lsung (oder besser: Ergnzung der Klammerung) ist die
+nderung oder Verwendung einer entsprechend genderten bst-Datei, in der
+bei der Formatierung des Titels und anderer Teile eines Eintrages die
+BibTeX-Anweisung `change.case$' _nicht_ ausgefhrt wird. Dies sollte bei
+den an das Deutsche angepaten bst-Dateien (siehe Frage 7.2.3) bereits
+der Fall sein, im Paket `custom-bib' (siehe Frage 7.2.2) kann die
+Umwandlung ber einen Menpunkt ausgewhlt werden.
+
+7.2.7 Bei Labels wie [Rai95], die aus Teilen des Autorennamens gebildet
+werden, treten Fehler bei Autorennamen mit Umlauten auf; wie kann ich
+das verhindern?
+
+Damit BibTeX die Konstruktion `\"a' fr Umlaute als ein einzelnes
+Zeichen korrekt erkennen kann, mu der Umlaut mit einer zustzlichen
+Klammerung im Eintrag in der .bib-Datei eingegeben werden, also als
+`{\"a}' oder `{\ss}'. Tip: BibTeX-Dokumentation in ``btxdoc'' lesen!
+
+btxdoc: CTAN: biblio/bibtex/distribs/doc/
+
+
+
+7.2.8 Kann ich Umlaute direkt in einer .bib-Datei verwenden?
+
+Jein. Einige neuere BibTeX-Implementierungen erlauben die Ein- und
+Ausgabe von Umlauten und anderen akzentuierten Zeichen. Will man diese
+Dateien jedoch an Personen mit anderen Rechnersystemen und anderen
+BibTeX-Implementierungen weitergeben, sollte man sich auf die
+Standard-Kodierung mit `{\"a}' etc. beschrnken.
+Im Schlssel eines Verweises, also dem Argument von \cite, ebenso wie im
+Schlssel eines .bib-Eintrages, also dem ersten Wort des Eintrags, darf
+man _keine Umlaute_ verwenden. Hier sollte man sich auf die 26 Klein-
+und 26 Grobuchstaben, die 10 Ziffern und die Satzzeichen beschrnken.
+Der Grund liegt darin, da dieser Schlssel von (La)TeX an BibTeX
+bergeben werden mu und ein Schlssel mit Umlauten auf diesem Wege
+eventuell zu einer anderen Zeichenkette expandiert werden kann, die im
+BibTeX-Lauf mit keinem Schlssel in der .bib-Datei bereinstimmt.
+Dadurch kann dann der Eintrag von BibTeX bzw. von (La)TeX nicht gefunden
+werden.
+
+8-Bit-BibTeX: CTAN: biblio/bibtex/8-bit/
+
+
+
+7.2.9 Wie kann ich erreichen, da mehrere Zitate [5,3,1,7,6] zu
+[1,3,5-7] sortiert und zusammengefat werden?
+
+Je nach Art der bevorzugten Darstellung der Zitate im Text erreicht man
+dies mit den Paketen `cite' oder `overcite' sowie `natbib' (Optionen:
+``numbers,sort&compress''). Sollen im endgltigen Dokument die Zitate
+unter Verwendung des Pakets `hyperref' anklickbar werden, ist die
+letztgenannte Lsung zu bevorzugen. Ergnzend kann das Paket `hypernat'
+benutzt werden, um auch die Wirkung der `hyperref'-Optionen `backref'
+und `pagebackref' in diesem Fall sicherzustellen.
+
+cite, overcite: CTAN: macros/latex/contrib/cite/
+natbib: CTAN: macros/latex/contrib/natbib/
+hypernat: CTAN: macros/latex/contrib/misc/
+
+
+
+7.2.10 Wie kann man in einem Dokument verschiedene Abschnitte mit
+eigenen Literaturverzeichnissen versehen?
+
+Die Pakete `chapterbib' und `bibunits' erlauben es, mehrere
+Literaturverzeichnisse in einem Dokument zu verwenden, solange diese in
+eigenen Abschnitten stehen. Bei `chapterbib' mu jeder der Abschnitte in
+einer getrennt mit \include{...} einzubindenden Datei stehen. Beide
+Pakete (`bibunits' ab Version 2.1) arbeiten problemlos mit anderen
+Paketen wie `natbib' zusammenarbeitet.
+
+chapterbib: CTAN: macros/latex/contrib/cite/
+bibunits: CTAN: macros/latex/contrib/bibunits/
+
+
+
+7.2.11 Wie kann man ein thematisch untergliedertes Literaturverzeichnis
+erstellen?
+
+Das Paket `bibtopic', vormals `bibtopics', ermglicht die
+Untergliederung eines Literaturverzeichnisses, wobei allerdings die
+.bib-Datenbankdatei entsprechend der Gliederung in mehrere Dateien
+aufgeteilt werden mu. Ein alternatives Paket ist `multibib', bei dem
+die Aufteilung der .bib-Datenbankdatei nicht ntig ist.
+
+bibtopic: CTAN: macros/latex/contrib/bibtopic/
+multibib: CTAN: macros/latex/contrib/multibib/
+
+
+
+7.2.12 Wie kann ich in einer BibTeX-Datenbank WWW- oder ftp-Quellen, die
+als URL vorliegen, zitieren?
+
+Die Quellen knnen mit den blichen BibTeX-Styles auf unterschiedliche
+Art und Weise zitiert werden. Eine Variante ist
+
+ @manual{KEITH,
+ author = "Keith Reckdahl",
+ title = "Using Imported Graphics in \LaTeXe\ Documents",
+ year = "1997",
+ month = dec,
+ note = "CTAN: \url{tex-archive/info/epslatex.ps}"}
+
+und eine weitere
+
+ @misc{GRANT,
+ author = "Michael C. Grant and David Carlisle",
+ title = "The PSFrag system, version~3",
+ year = "1996",
+ month = nov,
+ howpublished = "CTAN: \url{tex-archive/macros/latex/contrib/%
+ supported/psfrag/pfgguide.tex}"}
+
+In beiden Fllen wird das LaTeX-Paket `url' verwendet, um den Umbruch
+der Adressen zu erreichen (siehe Frage 7.3.10). Auf dieses Paket kann
+verzichtet werden, wenn bereits das Paket `hyperref', mindestens
+Version 6.70s (2000-08-31) oder aktueller, benutzt wird.
+Wird das `hyperref' _nicht_ verwendet, so solle man das Prozentzeichen
+am Zeilenende entfernen, da dann das Paket `url' dieses dann mit
+ausgeben wrde.
+Wird das Paket `jurabib' verwendet, so kann man auch einfach wie folgt
+zitieren:
+
+ @manual{KEITH,
+ author = "Keith Reckdahl",
+ title = "Using Imported Graphics in \LaTeXe\ Documents",
+ year = "1997",
+ month = dec,
+ url = "ftp://ftp.dante.de/tex-archive/info/epslatex.ps"}
+
+
+url: CTAN: macros/latex/contrib/misc/url.sty
+hyperref: CTAN: macros/latex/contrib/hyperref/
+jurabib: http://www.jurabib.org/
+
+
+
+7.2.13 Gibt es einen Weg, da \cite gleich die komplette Literaturstelle
+liefert?
+
+Dies geht zwar nicht direkt mit der Anweisung \cite, aber im Paket
+`bibentry', das `natbib' beiliegt, gibt es die Anweisung \bibentry, die
+die vollstndige Literaturangabe liefert. Nheres ist der mitgelieferten
+Dokumentation zu entnehmen. Eine Alternative bietet das Paket
+`inlinebib', das man allerdings nur mit dem beigefgten
+``inlinebib.bst'' verwenden kann. Auch das Paket `jurabib' ist in der
+Lage, z.B. mittels \fullcite oder der Option ``citefull=all'' bzw.
+``citefull=first'' eine vollstndige Literaturstelle zu liefern. Es kann
+jedoch nur mit den `jurabib'-eigenen BibTeX-Stil ``jurabib'' verwendet
+werden.
+
+bibentry: CTAN: macros/latex/contrib/natbib/
+inlinebib: CTAN: biblio/bibtex/contrib/inlinebib/
+jurabib: http://www.jurabib.org/
+~: CTAN: macros/latex/contrib/jurabib/
+
+
+
+7.2.14 Wie kann ich mit Kurzformen von Autor und Titel zitieren oder
+zwischen Kurz- und Langformen wechseln?
+
+Das Paket `jurabib' bietet dazu die Eintragsfelder juraauthor und
+juratitle an, in die man die zu verwendende Kurzform des Autors bzw. des
+Titels eintrgt. Es bietet auch die Option ``citefull=first'', mit dem
+bei Erstnennung eines Werkes eine vollstndige Literaturstelle
+erscheint, bei den weiteren Zitaten erscheinen jedoch nur noch die
+angegebenen Kurzformen. Werden keine Kurzformen angegeben, werden sie
+(grtenteils) von `jurabib' generiert. Auch `inlinebib' bietet Felder
+fr Kurzformen an.
+
+inlinebib: CTAN: biblio/bibtex/contrib/inlinebib/
+jurabib: CTAN: macros/latex/contrib/jurabib/
+
+
+
+7.2.15 Wie kann ich die Eintrge in @phdthesis mit ``Diplomarbeit'' oder
+hnlicher Klassifikation auszeichnen?
+
+Im einfachsten Fall kann man die Art der These durch die Eigenschaft
+type eberschreiben, also mit type="Dissertation". Soll als
+Standard-Wert etwas anderes verwendet werden, so mu man die .bst-Datei
+anpassen.
+
+7.3 \verb-Anweisung, verbatim- und Kommentar-Umgebungen (+)
+
+
+7.3.1 Wieso kann ich \verb nicht im Argument einer anderen Anweisung wie
+\footnote, \parbox u.. verwenden? Wieso geht dies mit LaTeX2e nicht
+mehr, obwohl es mit LaTeX 2.09 ging?
+
+Dies ging in LaTeX 2.09 auch nur, solange innerhalb des Arguments von
+\verb keine Zeichen mit besonderer Bedeutung verwendet wurden. Fr diese
+Flle htte ein einfaches {\tt ...} auch ausgereicht. Die Eingabe
+``\footnote{\verb+\cite+}'' liefert auch mit LaTeX 2.09 Fehler mit einer
+sehr kryptischen Fehlermeldung, deshalb wird diese falsche Benutzung in
+LaTeX2e mit der aussagekrftigeren Fehlermeldung `! LaTeX Error: \verb
+illegal in command argument.' verhindert.
+Benutzt man das Paket `fancyvrb' und verwendet man in der Prambel des
+Dokuments die von diesem Paket definierte Anweisung \VerbatimFootnotes,
+so knnen, anders als in Standard-LaTeX, innerhalb von Funoten
+\verb-Anweisungen verwendet werden.
+
+fancyvrb: CTAN: macros/latex/contrib/fancyvrb
+
+
+
+7.3.2 Wieso bekomme ich die Fehlermeldung `! LaTeX Error: \verb ended by
+end of line.', wenn ich im Argument von \verb in der Eingabe ein
+Zeilenende habe?
+
+LaTeX 2.09 war bei \verb sehr viel toleranter und hat den Zeilenwechsel
+innerhalb des Arguments von \verb erlaubt, obwohl dies keinen Sinn
+macht, da \verb nur fr kurze Textstcke gedacht ist und im formatierten
+Ergebnis kein Zeilenumbruch sichtbar wurde.
+Aus diesen Grnden wird nun in LaTeX2e ein eventuell vorhandenes
+Zeilenende im Argument von \verb als Fehler gemeldet. Dies hat den
+Vorteil, da ein versehentlich vergessenes Argumentendezeichen sehr frh
+erkannt und mit einer sinnvoller Fehlermeldung angezeigt werden kann.
+Als Seiteneffekt kann hierdurch auch die Verwendung von \verb im
+Argument einer anderen Anweisung erkannt und angezeigt werden.
+Eine Abhilfe ist sehr einfach mglich, indem man in der Eingabe einen
+Zeilenwechsel im Argument von \verb vermeidet.
+
+7.3.3 Wie kann ich eine eigene `verbatim'-Umgebung definieren?
+
+Die intuitive Definition
+ \newenvironment{myverbatim}{%
+ \begin{verbatim}%
+ }{%
+ \end{verbatim}%
+ }
+einer solchen Umgebung ist nicht mglich, da `verbatim' `festverdrahtet'
+nach der Zeichenkette `\end{verbatim}' sucht, so da die neue Umgebung
+das `\end{myverbatim}' nicht als Ende erkennen kann.
+Um dennoch `verbatim'-hnliche Umgebungen definieren zu knnen, gibt es
+mehrere Pakete:
+
+* `alltt' belt die drei Zeichen \, { und } in ihrer besonderen
+ Bedeutung, ist daher keine vollstndige verbatim-Umgebung.
+* `verbatim' (von Rainer Schpf et al.) erlaubt die Definition eigener
+ `verbatim'-Umgebungen, wie z.B.
+ \newenvironment{myverbatim}{%
+ \verbatim % <== nicht \begin{verbatim} !
+ }{%
+ \endverbatim % <== nicht \end{verbatim} !
+ }
+* `moreverb' und `fancyvrb' enthalten weitere Umgebungen, die
+ unterschiedliche `verbatim'-hnliche Umgebungen vordefiniert enthalten
+ oder mit denen man solche definieren kann.
+
+
+alltt: CTAN: macros/latex/base/
+ CTAN: macros/latex/unpacked/
+ CTAN: macros/latex209/contrib/misc/alltt.sty
+verbatim: CTAN: macros/latex/required/tools/
+moreverb: CTAN: macros/latex/contrib/moreverb
+fancyvrb: CTAN: macros/latex/contrib/fancyvrb
+
+
+
+7.3.4 Wie kann ich Programm-Code in mein LaTeX-Dokument einbinden?
+
+Neben der Mglichkeit, kurze Abschnitte `verbatim' einzubinden, gibt es
+verschiedene Tools, die automatisch LaTeX-Code mit den entsprechenden
+Syntaxhervorhebungen erzeugen:
+
+* `listings'
+ Reine LaTeX-Lsung; untersttzt viele Programmiersprachen; in neueren
+ Versionen kann `listings' zustzlich einige der Mglichkeiten des
+ Pakets `fancyvrb' nutzen.
+* `lgrind'
+ C-Programm und LaTeX-Style, fr LaTeX2e; untersttzt sehr viele
+ Programmiersprachen.
+* `tiny_c2l'
+ lex-Programm und LaTeX-Style; untersttzt neben C auch C++ und Java;
+ kann berlange Zeilen umbrechen.
+
+
+listings: CTAN: macros/latex/contrib/listings/
+lgrind: CTAN: nonfree/support/lgrind/
+tiny_C2l: CTAN: support/tiny_c2l/
+
+
+
+7.3.5 Wie kann ich den Inhalt einer Datei innerhalb einer
+`verbatim'-Umgebung darstellen?
+
+`verbatim' (von Rainer Schpf et al.) stellt fr diese Zwecke die
+Anweisung \verbatiminput{Dateiname} zur Verfgung. Die Pakete `moreverb'
+und `fancyvrb' stellen weitere Anweisungen und Umgebungen zur Verfgung.
+
+verbatim: CTAN: macros/latex/required/tools/
+moreverb: CTAN: macros/latex/contrib/moreverb
+fancyvrb: CTAN: macros/latex/contrib/fancyvrb
+
+
+
+7.3.6 Wie erreiche ich, dass innerhalb einer `verbatim'-Umgebung Umlaute
+und andere Sonderzeichen zu sehen sind? (+)
+
+Zu diesem Zweck ist es ntig, die Art der Kodierung dieser Zeichen
+anzugeben. Siehe dazu Frage 8.5.3.
+
+7.3.7 Wie kann ich Zeilennummern zu meinem Text hinzufgen?
+
+Zu diesem Zweck gibt es die beiden LaTeX-Pakete `lineno' und `numline'.
+Handelt es sich um Programmcode, der numeriert werden soll, sind jedoch
+die in Frage 7.3.4 genannten Lsungen zu bevorzugen.
+
+lineno: CTAN: macros/latex/contrib/lineno
+numline: CTAN: macros/latex/contrib/numline
+
+
+
+7.3.8 Gibt es eine Kommentarumgebung, mit der ich grere Textteile
+auskommentieren kann?
+
+Um Teile eines Textes auszukommentieren, kann man entweder zwei sehr
+einfache TeX-Konstrukte verwenden, oder man bedient sich spezieller
+Pakete, die unterschiedlich mchtige Kommentar-Umgebungen anbieten.
+Zu den einfachen Konstrukten, die TeX selbst anbietet, zhlt zum einen
+die Einklammerung des zu ignorierenden Textes mit den TeX-Primitiven
+\iffalse ... \fi:
+
+ \iffalse
+ Kommentartext, wird sehr schnell ueberlesen
+ \fi
+
+Hier sollten im Kommentartext keine \if...-, \else- und \fi-Tokens (bzw.
+diese mssen korrekt geschachtelt sein), keine `outer'-Makros oder
+unerlaubte Zeichen auftauchen, da diese zu einem Fehler oder vielleicht
+zu doch nicht auskommentierten Textteilen fhren knnen.
+Ein anderes, einfaches Verfahren ist die Verwendung eines Makros, wobei
+der auszukommentierende Text in dessen Argument geschrieben wird:
+
+ \newcommand{\kommentar}[1]{}
+ % ...
+ \kommentar{%
+ Kommentartext, wird als Argument gelesen und ignoriert
+ }%
+
+Auch hier sollten die oben genannten Tokens nicht im Kommentartext
+auftauchen, auerdem darf der Kommentartext nicht zu lang sein, da sonst
+TeXs `main memory' berlaufen knnte.
+Spezielle Kommentarumgebungen beseitigen diese Einschrnkungen - und
+haben meist selbst eigene Einschrnkungen. `verbatim' aus dem
+`tools'-Bndel definiert eine sehr einfache Umgebung namens `comment',
+die man jedoch nicht schachteln kann. Weiterhin gibt es noch `xcomment'
+(von Timothy van Zandt), eine speziell an die Erfordernisse des Paketes
+`seminar' angepate und abgespeckte Version des `verbatim'. Mit
+`comment' (von Victor Eijkhout) kann man neue Kommentarumgebungen
+definieren, die mit \includecomment- und \excludecomment-Deklarationen
+aus- und eingeblendet werden knnen.
+
+verbatim: CTAN: macros/latex/required/tools/
+xcomment: CTAN: macros/latex/contrib/seminar/inputs/xcomment.sty
+comment: CTAN: macros/latex/contrib/comment/
+
+
+
+7.3.9 Wie kann ich mehrere Versionen eines Textes erstellen oder
+bedingte Textteile verwenden?
+
+Auf der einen Seite kann man die in Frage 7.3.8 beschriebenen
+Kommentarumgebungen entsprechend verwenden. Daneben gibt es mit den
+Paketen `version', `optional' und dem bereits erwhnten `comment'
+Erweiterungen, mit denen man ber Flags im Dokumentkopf Textteile
+bedingt ein- oder ausblenden kann.
+
+version: CTAN: macros/latex/contrib/misc/version.sty
+optional: CTAN: macros/latex/contrib/misc/optional.sty
+comment: CTAN: macros/latex/contrib/comment/
+
+
+
+7.3.10 Ich will \verb z.B. fr Dateinamen, E-Mail-Adressen und URL
+verwenden. Wie schaffe ich es, da innerhalb von \verb an geeigneten
+Stellen getrennt wird?
+
+Fr einige Anwendungen, wo man evtl. \verb benutzen knnte, gibt es auch
+spezielle Lsungen, die fr den Anwendungszweck besser geeignet sind. So
+gibt es beispielsweise die Pakete `url' und `path' fr Dateinamen,
+E-Mail- und WWW-Adressen, bei denen nur an bestimmten Stellen umbrochen
+werden darf, dies aber bereits automatisch geschieht.
+
+url: CTAN: macros/latex/contrib/misc/url.sty
+path: CTAN: macros/latex/contrib/misc/path.sty
+
+
+
+7.4 Zerbrechliche Anweisungen in `moving arguments'
+
+
+7.4.1 Was sind `fragile commands'/zerbrechliche Anweisungen, was sind
+`moving arguments'?
+
+Der Text, den ein Autor im Argument von Anweisungen wie \caption,
+\section etc. angibt, kann an mehreren Stellen in einem Dokument gesetzt
+werden. Der Argumenttext von \section wird z.B. als Kapitelberschrift
+gesetzt und taucht evtl. nochmals im Inhaltsverzeichnis oder im
+Seitenkopf bzw. -fu auf. Diese Argumente nennt man `moving arguments',
+da sie vom Platz, wo ein Autor sie angibt, auch zu anderen Stellen
+verschoben werden.
+Die korrekte Ausfhrung von `zerbrechlichen Anweisungen' hngt intern
+von Zuweisungen ab. Innerhalb eines `moving argument' werden diese
+Zuweisungen jedoch nicht durchgefhrt, so da solche Anweisungen
+`zerbrechen'. Zu den zerbrechlichen Anweisungen zhlen unter anderem
+\cite, \ref, \pageref fr Literatur- und Querverweise, \footnote,
+\footnotemark, die Anweisungen \small, \large etc. zur Wahl der
+Schriftgre, mathematische Formelzeichen wie \sqrt, \notin, \overbrace
+und viele mehr (siehe Frage 7.4.2, Bemerkung am Ende).
+
+7.4.2 Wie kann ich innerhalb des Arguments von \caption, \section etc.
+Anweisungen wie \cite, \ref, \pageref oder \footnote verwenden, ohne
+Fehler wie `! Argument of \@sect has an extra }.' oder `! Use of
+\@chapter doesn't match its definition.' zu erhalten?
+
+Zerbrechliche Befehle wie \cite mssen im `moving argument' der
+Anweisung \caption mit \protect geschtzt werden, d.h. statt
+
+ \caption{Bildunterschrift~\cite{PartlKnappen95}}
+
+ist ein \protect direkt und _ohne_ geschweifte Klammern vor die zu
+schtzende Anweisung zu setzen:
+
+ \caption{Bildunterschrift~\protect\cite{PartlKnappen95}}
+
+Anweisungen wie \caption, \section etc. haben auerdem noch die
+Mglichkeit, in einem optionalen Argument den zu `verschiebenden
+Argumenttext' anzugeben. Das heit, obiges knnte auch in
+
+ \caption[Bildunterschrift]%
+ {Bildunterschrift~\cite{PartlKnappen95}}
+
+umformuliert werden. Jetzt ist das optionale Argument in []-Klammern das
+`moving argument', in dem Sie zerbrechliche Anweisungen mit \protect
+schtzen mssen!
+Beginnend mit LaTeX von Dezember 1995 sind Anweisungen wie \cite und
+Anweisungen mit optionalem Argument, wie \sqrt, nicht mehr zerbrechlich
+und bentigen damit kein \protect mehr. Dennoch sollten Sie diese
+Anweisungen weiterhin mit \protect schtzen, wenn Sie Ihre Dokumente
+anderen zukommen lassen wollen.
+
+--- DE-TeX-FAQ Ende Teil 7 ---
diff --git a/help/de-tex-faq/part8 b/help/de-tex-faq/part8
new file mode 100644
index 0000000000..5319dc5915
--- /dev/null
+++ b/help/de-tex-faq/part8
@@ -0,0 +1,1253 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news-out.cwix.com!newsfeed.cwix.com!skynet.be!skynet.be!newsfeed00.sul.t-online.de!t-online.de!news-lei1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 8 of 11)
+Supersedes: <de-tex-faq-8-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:18 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 1224
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-8-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975398 892 134.100.9.52 (19 Sep 2003 12:43:18 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:18 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117408 de.answers:9385 news.answers:258274
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part8
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 8 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+8 TeX, LaTeX, Makros etc. (IV)
+
+
+8.1 Verschiedene Zeichen
+
+
+8.1.1 Wie bekomme ich ein Gradzeichen?
+
+Das Gradzeichen erhlt man am einfachsten mit LaTeX mittels
+
+ \newcommand{\grad}{\ensuremath{^\circ}}
+
+Da die Anweisung \ensuremath in LaTeX 2.09 nicht existiert, mu man hier
+den konventionellen Weg whlen (der auch in LaTeX2e funktioniert):
+
+ \newcommand{\grad}{\mbox{\(\mathsurround=0pt{}^\circ\)}}
+
+Hat man schon die `Text-Companion'-Schrift der EC-Schriftfamilie
+installiert, kann man mit dem Paket `textcomp', das seit Dezember 1997
+Bestandteil von LaTeX ist, auf ein Gradzeichen mit \textdegree und auf
+ein fertig zusammengesetztes Grad-Celsius-Zeichen mit \textcelsius
+zugreifen. In der mittlerweile veralteten Testversion von `textcomp'
+mute statt \textcelsius noch \textcentigrade verwendet werden.
+
+ec/tc-fonts: CTAN: fonts/ec/
+
+
+
+8.1.2 Wo finde ich ein Promillezeichen? Ich mchte endlich 1,1Promille
+statt 0,11\% eingeben knnen.
+
+Die beste Lsung bietet die in den Text-Companion-(tc)-Schriften der
+EC-Schriftfamilie vorhandene Letter fr ein Promillezeichen, da sie auch
+von der Form zum blichen Prozentzeichen der Schrift passt:
+
+ \usepackage{textcomp}
+ \textperthousand
+
+Falls man die Text-Companion-Schriften nicht verwenden will, kann man
+alternativ die Schrift `wasy' verwenden, in der ebenso eine Letter fr
+ein Promillezeichen existiert:
+
+ \usepackage{wasysym}
+ \permil
+
+Sind beide Schriften nicht verfgbar, kann man folgende, in ``Die
+TeXnische Komdie'' vom Dezember 1993 erschienene Lsung verwenden, die
+auf der TeXbook-Lsung zu bung 11.6, S. 67 und 311, basiert (an LaTeX2e
+angepat [br]):
+
+ \newcommand{\promille}{%
+ \relax\ifmmode\promillezeichen
+ \else\leavevmode\(\mathsurround=0pt\promillezeichen\)\fi}
+ \newcommand{\promillezeichen}{%
+ \kern-.05em%
+ \raise.5ex\hbox{\the\scriptfont0 0}%
+ \kern-.15em/\kern-.15em%
+ \lower.25ex\hbox{\the\scriptfont0 00}}
+
+Die zustzliche \(..\)-Umgebung im Makro \promille ist fr LaTeX2e
+zwingend notwendig, da sonst in einigen Fllen Zeichen fehlen knnten.
+(Man knnte auch die Anweisung \ensuremath aus LaTeX2e verwenden.)
+Leider pat das erzeugte Promillezeichen von der Form her nicht zum
+Prozentzeichen.
+
+textcomp: CTAN: macros/latex/base/
+ec/tc-fonts: CTAN: fonts/ec/
+wasysym: CTAN: macros/latex/contrib/wasysym/
+wasy: CTAN: fonts/wasy2/
+ CTAN: fonts/wasy2/ps-type1/hoekwater/
+
+
+
+8.1.3 Ich bentige einen liegenden bzw. gedrehten `dagger' oder ein
+hnliches liegendes Zeichen. Wie?
+
+Entweder sucht man nach einem fertigen Font mit einem solchen Symbol
+oder ndert die Quelle eines Fonts, falls dieser beispielweise als
+METAFONT-Datei vorliegt, und fgt in die Quelle eine Operation zum
+Drehen eines Zeichens ein.
+Falls der dvi-Gertetreiber in der Lage ist, Teile der Ausgabe zu drehen
+(wie die meisten PostScript-Treiber), kann man unter LaTeX die Anweisung
+\rotatebox aus dem `graphicx'-Package verwenden:
+
+ \rotatebox[origin=c]{90}{\(\dagger\)}
+
+
+graphicx: CTAN: macros/latex/required/graphics/
+
+
+
+8.1.4 Wie erzeuge ich ein Zeichen fr `trademark' (TM), `registered
+trademark' (R) oder `copyright' (C)?
+
+Diese Zeichen durch Box-Konstruktionen zusammenzubauen, ergibt in den
+meisten Fllen sehr unbefriedigende Ergebnisse. Unter LaTeX hat man mit
+der Anweisung \textcircled{<Zeichen>} eine sehr einfache Mglichkeit
+dafr, jedoch erhlt man nur fr einzelne Zeichen, wie fr das `c' im
+Copyright-Zeichen \copyright, ein einigermaen gutes Ergebnis. Eine
+erste Nherung fr das Trademark-Zeichen (TM) ist
+\DeclareRobustCommand{\trademark}{\ensuremath{^{\mathrm{TM}}}}.
+Sehr viel einfacher und besser sind die fertigen Zeichen, wie
+\texttrademark, aus den `Text-Companion'-Fonts `tc...' aus dem
+`EC'-Schrift-Paket. Unter LaTeX gibt es zur einfachen Einbindung das
+`textcomp'-Package.
+Beginnend mit LaTeX von Dezember 1995 gibt es standardmig neben der
+Definition fr das Copyright-Zeichen auch Definitionen fr die Zeichen
+`trademark' und `registered trademark' (\texttrademark,
+\textregistered). Seit LaTeX vom Dezember 1997 ist das Paket `textcomp'
+in der LaTeX-Verteilung enthalten.
+
+tc-Fonts: CTAN: fonts/ec/
+Liste der tc-Fonts: CTAN: info/symbols/text/
+
+
+
+8.1.5 Wie kann man ein nicht kursives griechisches mu erzeugen?
+
+In den Text-Companion-Fonts befindet sich ein aufrechtes mu, das man
+beispielsweise fr Mengenangaben bentigt.
+
+ \usepackage{textcomp} % seit 1997/12/01 in der Standardverteilung
+ \textmu
+
+
+8.1.6 Wie bekomme ich das Whrungssymbol fr den Euro?
+
+Die `Text-Companion'-Fonts enthalten das Euro-Symbol, wobei dieses nicht
+der offiziell festgelegten Version entspricht.
+
+ \usepackage{textcomp}
+ \texteuro
+ {\sffamily\texteuro}
+
+Ebenso kann man sich notfalls ein eigenes, ebenso nicht konformes
+Euro-Symbol zusammensetzen:
+
+ \newcommand\euro{{\sffamily C%
+ \makebox[0pt][l]{\kern-.70em\mbox{--}}%
+ \makebox[0pt][l]{\kern-.68em\raisebox{.25ex}{--}}}}
+
+Mit dem Paket `eurosym' gibt es einen Satz an Fonts mit dem Euro-Symbol,
+das der offiziell festgelegten Form des Symbols entspricht. Mitgeliefert
+wird ein LaTeX-Paket zur Einbindung, so da man mit \euro ein
+offizielles zur Schriftgre passendes Euro-Symbol erhlt. Abweichend
+von der offiziellen Vorgabe wird es, um ein besseres Schriftbild zu
+erreichen, auch fett und schrg gesetzt.
+Dieselbe Anweisung \euro untersttzt auch das Paket `europs'. Es
+erfordert die bei Adobe verfgbaren PostScript-Fonts mit dem
+Euro-Symbol. Daneben existiert mit dem Paket `eurosans' eine weitere
+LaTeX-Einbindung, das das Euro-Symbol aus der von Adobe erstellten
+PostScript-Font-Familie `EuroSans' verwendet.
+Daneben enthlt auch die im PostScript-Type-1-Format vorliegende Schrift
+`Martin Vogels Symbole (marvosym)' ein Euro-Symbol. In dieser Schrift
+ist auerdem jeweils ein Euro-Symbol, das zu den Schriften Times,
+Helvetica und Courier pat, enthalten.
+
+ \usepackage{marvosym} % bei der Schrift enthalten
+ \EUR
+ \EURtm \EURhv \EURcr
+
+Und auch das Paket `China2e', mit dem chinesische Kalendersymbole
+erzeugt werden knnen, enthlt Fonts mit dem Euro-Symbol, das man mit
+der Anweisung \Euro bekommt.
+Desweiteren kann im Zusammenhang mit der Verwendung von Euro-Symbolen
+das Paket `euro' sehr hilfreich sein. Es bietet vielfltige
+Mglichkeiten der Umrechnung von Euro in andere Whrungen und umgekehrt.
+Verwendet man das Paket `mathpazo' bekommt man ein Eurozeichen, welches
+auf die Grundschrift `Palatino' abgestimmt ist.
+
+ \usepackage{mathpazo}
+ \ppleuro
+
+
+eurosym: CTAN: fonts/eurosym/
+europs: CTAN: fonts/euro/latex/europs/
+ http://www.adobe.com/
+eurosans: CTAN: fonts/euro/latex/eurosans/
+marvosym: CTAN: fonts/psfonts/marvosym/
+china2e: CTAN: macros/latex/contrib/china2e/
+euro: CTAN: macros/latex/contrib/euro/
+mathpazo: CTAN: fonts/mathpazo/
+Walter Schmidt: Wie bekomme http://home.vr-web.de/was/x/latexeuro.pdf
+ich...:
+
+
+
+8.1.7 Wie bekomme ich ein Entspricht-Symbol?
+
+Ein Entspricht-Symbol kann man sich entweder mit
+
+ \newcommand{\entspricht}{\mathrel{\widehat{=}}}
+
+oder mit
+
+ \newcommand{\entspricht}{\stackrel{\scriptscriptstyle\wedge}{=}}
+
+definieren. Die Anweisung \mathrel{}, die in \stackrel implizit bereits
+enthalten ist, sorgt dafr, da korrekte Abstnde vor und nach einem so
+definierten Symbol verwendet werden.
+
+8.1.8 Wie bekomme ich das Symbol fr Durchmesser?
+
+Die einfachste Lsung ist \O{}. Empfehlenswerter ist jedoch ein Symbol
+aus den AmS-Schriften:
+
+ \usepackage{amssymb}
+ \(\varnothing\)
+
+
+AmS-Fonts: CTAN: fonts/amsfonts/
+amssymb: CTAN: fonts/amsfonts/latex/
+
+
+
+8.1.9 Wie kann ich ``\'', ``<'', ``>'' und weitere Sonderzeichen im Text
+benutzen?
+
+Die Zeichen, die in LaTeX eine besondere Bedeutung haben, und andere
+Sonderzeichen muten frher mehr oder weniger kompliziert erzeugt werden
+oder man mute auf den Formelsatz ausweichen. Unter LaTeX2e gibt es nun
+einfachere Anweisungen, wobei man eine LaTeX-Version vom Dezember 1995
+oder neuer verwenden sollte. Unter anderem sind folgende Symbole
+definiert:
+
+Text-Anweisung Formelsatz Symbol oder Symbol-Beschreibung
+\textbackslash \backslash \
+\textbar \mid |
+\textless < <
+\textgreater > >
+\textasciicircum \hat ^
+\textasciitilde \tilde ~
+\textbullet \bullet gefllter Kreis auf halber Hhe
+\textperiodcentered \cdot
+\textvisiblespace (n.v.) sichtbares Leerzeichen
+
+Nheres findet man in der Datei ``usrguide.tex'' (``LaTeX2e for
+authors'').
+
+usrguide: CTAN: macros/latex/base/usrguide.tex
+
+
+
+8.1.10 Wie bekomme ich die Symbole fr Laplace-, Fourier- und
+Z-Transformation?
+
+Das LaTeX-Paket `trfsigns' bietet diese Symbole.
+
+trfsigns: CTAN: macros/latex/contrib/trfsigns
+
+
+
+8.1.11 Wie kann ich einen _Smiley_ und einen _Frownie_ setzen?
+
+Eine einfache Version erhlt man mit
+
+ \newcommand{\frownie}{\texttt{:-(}}
+ \newcommand{\smiley}{\texttt{;-)}}
+
+und mit dem Paket `wasysym' kann man die Symbole aus den Schriften
+`wasy' mit den Anweisungen \smiley und \frownie bekommen.
+
+wasysym: CTAN: macros/latex/contrib/wasysym/
+wasy: CTAN: fonts/wasy2/
+ CTAN: fonts/wasy2/ps-type1/hoekwater/
+
+
+
+8.1.12 Das Zeichen := sieht schlecht aus, wie kann ich erreichen, da
+der Doppelpunkt in seiner Hhe zum Gleichheitszeichen pat?
+
+Mit der Konstruktion \mathrel{\mathop{:}} lt sich der Doppelpunkt auf
+der mathematischen Achse zentrieren, die auch die Mitte des
+Gleichheitszeichens bestimmt.
+Mit dem folgenden Makro von Donald Arseneau wird der Doppelpunkt im
+mathematischen Modus generell umgestellt:
+
+ \mathchardef\ordinarycolon\mathcode`\:
+ \mathcode`\:=\string"8000
+ \begingroup \catcode`\:=\active
+ \gdef:{\mathrel{\mathop\ordinarycolon}}
+ \endgroup
+
+
+8.2 Mathematischer Formelsatz (*)
+
+
+8.2.1 Fr Zahlenbereiche mchte ich die Symbole fr N, Z, Q, R, C mit
+Doppelstrich verwenden. Wie bekomme ich diese Zeichen?
+
+Ursprnglich wurden diese Symbole mit fetten Buchstaben geschrieben. Da
+dies mit Kreide auf einer Tafel (`blackboard') sehr umstndlich wre,
+hat man die Schreibweise mit den Doppelstrichen erfunden. Die einfachste
+Mglichkeit ist daher, die Symbole einfach fett zu drucken, also
+\mathbf{N} (bzw. {\bf N} in Plain-TeX und LaTeX 2.09).
+Bevorzugt man die Darstellung mit Doppelstrichen, dann ist man in der
+Regel mit den Mengenzeichen aus den AmS-Symbolschriften gut bedient:
+Nach Laden des Pakets `amssymb' steht mit der Anweisung \mathbb ein
+mathematisches Alphabet fr Mengenzeichen zur Verfgung, beispielsweise
+\mathbb{N} fr die Menge der natrlichen Zahlen. Man beachte, dass nur
+die Grobuchstaben verfgbar sind, sowie ein k mit Doppelstrich durch
+die Anweisung \Bbbk. AmS-Symbole stehen teilweise auch fr andere als
+die voreingestellten CM-Mathematikschriften zur Verfgung; man beachte
+die Dokumentation zur jeweiligen Schriftfamilie.
+Es gibt aber auch folgende Schriften, die Buchstaben mehr oder weniger
+so wie `an der Tafel geschrieben' enthalten:
+
+* `bbold' (von Alain Jeffrey)
+ ohne Serifen, zwei dnne Striche, vollstndiger Zeichensatz.
+* `mathbbol' (von Jrg Knappen)
+ definiert AmS-(La)TeXs \mathbb-Anweisung so um, da statt der
+ Original-AmS- die `bbold'-Schriften verwendet werden.
+* `doublestroke' (von Olaf Kummer)
+ mit Serifen (ein dicker und ein dnner Strich) und in neuer Version
+ ohne Serifen (gleichmige Dicke), nur Grobuchstaben und 1, k, h.
+* `bbm' (von Gilles F. Robert)
+ sollte allen Wnschen gerecht werden, alle Varianten, wie fett, mit
+ oder ohne Serifen etc.
+* `mathpazo'
+ enthlt die Symbole I, C, N, Q, R und Z, abgestimmt auf die Schrift
+ `Palatino' (Beispiel in CTAN: fonts/mathpazo/pazotest.pdf.
+
+Die Auswahl einer dieser Schriften ist reine Geschmackssache. Eine Hilfe
+dazu bietet die bersicht in der PostScript-Datei ``blackboard.ps''. Man
+beachte, dass nur die eingangs genannten AmS-Symbole sowie die Schrift
+`mathpazo' im Type-1-Format verfgbar sind; alle anderen gibt es bisher
+nur im METAFONT-Format.
+
+amssymb: CTAN: fonts/amsfonts/latex/
+bbold: CTAN: fonts/bbold/
+mathbbol: CTAN: macros/latex/contrib/jknappen/
+doublestroke: CTAN: fonts/doublestroke/
+bbm: CTAN: fonts/cm/bbm/
+ CTAN: fonts/cm/sauter/holin/bbm/
+ CTAN: macros/latex/contrib/bbm
+blackboard.ps: CTAN: info/symbols/blackboard/blackboard.ps
+mathpazo: CTAN: fonts/mathpazo
+
+
+
+8.2.2 Fr Lagrange-Dichten htte ich gern ein geschwungenes L;
+\mathcal{L} ist nicht das, was ich wnsche!
+
+Schreibschriftbuchstaben fr den Mathematiksatz (nur Grobuchstaben)
+sind in den `rsfs'-Schriften (Ralph Smith Formal Script) enthalten. Sie
+knnen mit dem Paket `mathrsfs' und dem Befehl \mathscr{L} eingebunden
+werden. Das Paket `calrsfs' ergibt Schreibschriftbuchstaben anstelle der
+kalligraphischen Buchstaben mit dem Befehl \mathcal{L}.
+
+rsfs: CTAN: fonts/rsfs/
+ CTAN: fonts/cm/sauter/holin/rsfs/b-rsfs.mf
+mathrsfs: CTAN: macros/latex/contrib/jknappen/
+calrsfs: CTAN: macros/latex/contrib/calrsfs/
+
+
+
+8.2.3 Ich suche das Zeichen ... fr den Formelsatz, und kann es nicht in
+den Standard-Fonts finden?
+
+Zeichen, die in den CM-Fonts fehlen, sind mit wirklich sehr groer
+Wahrscheinlichkeit in den AmS-Fonts `msam' oder `msbm' vorhanden. Die
+Einbindung in LaTeX erfolgt mit dem Paket `amsfonts', die Einbindung in
+Plain-TeX mit ``\input amssym.tex''. Nhers dazu siehe auch
+``amsfndoc.tex''.
+Eine umfassende bersicht von Symbolen mit Angabe der Bezugsquellen
+enthlt ``The Comprehensive LaTeX Symbol List'' von Scott Pakin.
+
+amsfonts: CTAN: fonts/amsfonts/
+amssym: CTAN: fonts/amsfonts/plaintex/amssym.tex
+amsfndoc.tex: CTAN: fonts/amsfonts/doc/amsfndoc.tex
+symbols: CTAN: info/symbols/
+comprehensive: CTAN: info/symbols/comprehensive/
+
+
+
+8.2.4 Warum fgt TeX in einer mathematischen Formel hinter einem
+Dezimalkomma einen kleinen Zwischenraum ein?
+
+Die meisten TeX-Makropakete und -Formate gehen davon aus, da man einen
+Dezimalpunkt statt eines -kommas verwendet. Fr den Dezimalpunkt, der in
+einer mathematischen Formel die Bedeutung eines `Ordinary'-Symbols hat,
+wird daher zwischen Ziffern kein zustzlicher Zwischenraum eingefgt.
+Das Komma hat in Formeln die Bedeutung eines `Punctuation'-Symbols, man
+kann es daher als Trennzeichen in einer Aufzhlung verwenden, da TeX mit
+einem kleinen Zwischenraum dafr sorgt, da Formeln wie `f(x, y)' gut
+aussehen.
+Das Problem des falschen Abstandes fr ein Dezimalkomma kann man auf
+verschiedene Arten beheben. Fr einzelne Flle mag es reichen, das Komma
+einfach mit {...} zu klammern, da geklammerte Formelteile diesselben
+Abstnde wie ein `Ordinary'-Symbol bekommen:
+
+ $\pi = 3{,}1415\ldots$
+
+Eine andere Methode erklrt das Komma zu einem `Ordinary'-Symbol statt
+eines Trennzeichens:
+
+ %%%% alte Definition:
+ %% \mathcode`\,="613B
+ %%%% neue Definition:
+ \mathcode`\,="013B
+
+und wenn man statt der \mathcode-Zuweisung die Anweisung
+\DeclareMathSymbol in LaTeX verwendet:
+
+ %%%% alte Definition:
+ %% \DeclareMathSymbol{,}{\mathpunct}{letters}{"3B}
+ %%%% neue Definition:
+ \DeclareMathSymbol{,}{\mathord}{letters}{"3B}
+
+Der Preis hierfr ist natrlich, da in `f(x,y)' der zustzliche
+Zwischenraum fehlt. Aber auch das lt sich in den Griff bekommen:
+Das Paket `icomma' ndert die Definition des Kommazeichen so, da es im
+mathematischen Modus zwischen `3,1415' und `f(x, y)' unterscheiden kann:
+Steht hinter dem Komma ein Leerzeichen, ist das Trennzeichen mit etwas
+Abstand gemeint, ansonsten das Dezimalkomma. Im Unterschied zu hnlichen
+Lsungen funktioniert diese Paket mit beliebigen Mathematik-Fonts.
+Mit dem Paket `ziffer' ist das Leerzeichen nach dem Komma, um Mengen
+oder Argumente zu kennzeichnen, bis auf einige Ausnahmen nicht
+notwendig, so dass bestehende Texte nicht verndert werden mssen.
+
+icomma: CTAN: macros/latex/contrib/was/
+ziffer: CTAN: macros/latex/contrib/misc/ziffer.sty
+
+
+
+8.2.5 AmS-LaTeX: Was ist der Unterschied zwischen dem Paket `amstex' und
+`amsmath'?
+
+Dies wird in der Datei ``diffs-m.txt'' des AmS-LaTeX-Packages erlutert:
+In AmS-LaTeX Version 1.0 und 1.1, beide nur fr LaTeX 2.09, war `amstex'
+das Hauptpaket, das mehr oder weniger direkt aus Michael Spivaks
+AmS-TeX-Makros entstanden ist. AmS-LaTeX Version 1.2 fr LaTeX2e enthlt
+nun neben `amstex' ein neues Paket namens `amsmath', das nun unabhngig
+von `amstex' weiterentwickelt werden kann. `amstex' kann dadurch
+eingefroren werden, so da alte Dokumente weiterhin unverndert
+formatiert werden knnen. Fr neue Dokumente sollte man `amsmath'
+verwenden, da nur noch dieses Paket untersttzt und weiterentwickelt
+wird. Die Unterschiede zwischen `amsmath' und `amstex' sind der
+Dokumentation in der Datei ``diffs-m.txt'' zu entnehmen.
+
+amslatex: CTAN: macros/latex/required/amslatex/
+AmS-LaTeX: http://www.ams.org/tex/amslatex.html
+The amsmath http://www.ams.org/tex/amsmath.html
+package:
+diffs-m.txt: CTAN: macros/latex/required/amslatex/math/diffs-m.txt
+
+
+
+8.2.6 Wieso bekomme ich mit AmS-LaTeX, wenn ich eigene Umgebungen, die
+`equation', `gather' `align', `alignat', `flalignat' oder `split'
+verwenden, Fehlermeldungen?
+
+Mit AmS-LaTeX funktionieren Definitionen wie
+
+ \newenvironment{myalign}{\begin{align}}{\end{align}}
+ \newcommand{\ba}{\begin{align}}
+ \newcommand{\ea}{\end{align}}
+
+nicht mehr, weil diese Umgebungen zuerst die komplette Formel einlesen
+mssen, da die Satzalgorithmen so geschrieben sind, da diese Formel
+mehrmals durchlaufen werden mu.
+Damit man dennoch eigene Umgebungen definieren kann, ist statt
+\begin{align} die Anweisung \align, statt \end{align} die Anweisung
+\endalign in der Definition zu verwenden:
+
+ \newenvironment{myalign}{\align}{\endalign}
+
+Die Definition von Abkrzungsmakros fr diese Umgebungen, wie oben
+gezeigt, ist zwar mit einem Trick mglich. Jedoch sollten Umgebungen
+grundstzlich auch als solche im Dokument erkennbar sein, so da von
+solchen Abkrzungsmakros abgeraten und der Trick nicht verraten wird.
+Nheres findet man in der Datei ``technote.tex'', das Teil der
+Dokumentation von AmS-LaTeX ist.
+
+technote.tex: CTAN: macros/latex/required/amslatex/math/technote.tex
+
+
+
+8.2.7 AmS-Fonts: Ein altes Dokument benutzt die Fonts `msxm' und `msym'.
+Wo kann ich diese finden?
+
+Die Fonts `msxm' und `msym' sind veraltet und wurden vor einigen Jahren
+durch die Fonts namens `msam' und `msbm' ersetzt. Beide Fonts sind im
+AmS-Font-Paket enthalten.
+Selbst wenn man die Quellprogramme fr die beiden veralteten Fonts
+`msxm' und `msym' htte, knnte man aus diesen keine gf- oder pk-Dateien
+erzeugen, da die Fonts `msxm' und `msym' mit dem Vorgnger des aktuellen
+METAFONT-Programmes namens `MF79' in der Sprache `SAIL' geschrieben
+waren. Aus diesem Grund wurden die beiden Fonts auch nur als pxl- oder
+pk-Dateien verteilt.
+Als Ersatz gibt es mit `msx2mas' einen Satz virtueller Fonts fr `msxm'
+und `msym', die die Symbole der vorhandenen Schriften `msam' und `msbm'
+verfgbar machen.
+
+msxm/msym: CTAN: fonts/vf-files/msx2msa/
+
+
+
+8.2.8 Das Integral- und Summationszeichen ist fr Dokumente, die in 11pt
+oder gar 12pt gesetzt sind, zu klein.
+
+Den Math-Extension-Font `cmex10', aus dem die `groen' Symbole stammen,
+sollte man nicht einfach vergrern, da einige Parameter dieses
+besonderen Fonts den mathematischen Formelsatz in TeX bestimmen. Da es
+bisher fr 11pt und 12pt keine speziellen Math-Extension-Fonts gibt,
+verwendet LaTeX fr alle Schriftgren den 10pt-Font `cmex10'.
+Mit dem Paket `exscale' verwendet LaTeXs skalierte `cmex10'-Fonts und
+pat die Anweisungen \big, \bigg etc. entsprechend an.
+
+exscale: CTAN: macros/latex/base/
+
+
+
+8.2.9 Wie vermeide ich den Fehler `! Double superscript.', den ich fr
+$a^b^c$ erhalte?
+
+Der Term a hoch b hoch c ist nicht eindeutig, da er entweder als (a^b)^c
+oder als a^(b^c) interpretiert werden kann. Anstatt nun eine
+mglicherweise falsche Interpretation des Terms anzunehmen, meldet TeX
+obigen Fehler. Diesen mu man durch explizite Klammerung ${a^b}^c$ bzw.
+$a^{b^c}$ auflsen, was dann zu Unterschieden in den Schriftgren
+fhrt.
+Das gleiche Problem stellt sich auch bei mehrfacher Indizierung $a_b_c$,
+wo man die Mehrdeutigkeit ebenso durch Klammerung auflsen mu.
+
+8.2.10 Wie setzt man physikalische Einheiten, etwa Lngenangaben? (*)
+
+Es gelten einigen Grundregeln, von denen die meisten das Paket `units'
+automatisch korrekt erledigt:
+
+* In wissenschaftlichen Werken werden Einheiten aufrecht und vor allem
+ bei lngeren Ausdrcken, etwa $F = 400\,\mathrm{kN}$, im Mathe-Modus
+ gesetzt.
+* Falls die Integration etwa in einen halbfetten Textteil wichtiger als
+ die physikalische Korrektheit ist, sollte Textmodus, etwa \textbf{...
+ 3\,m ...}, verwendet werden. Hinweis: Der Unterschied zwischen Text-
+ und Mathemodus wird deutlicher, wenn man mittels
+ \renewcommand{\familydefault}{cmss} eine Serifenlose verwendet.
+* Zwischen Zahl und Dimension findet kein Zeilenumbruch statt.
+* Als Abstand zwischen Zahl und Dimension whlt man \,. Dagegen sehen
+ die Richtlinien des Springer-Verlags ~ als Abstand vor.
+* Einheiten werden _nicht_ in eckige Klammern, wie etwa [N], gesetzt.
+ Die richtige Schreibweise ist $[F] = \mathrm{N}$.
+* In Tabellen stehen Einheiten in runden Klammern in einer eigenen Zeile
+ im Tabellenkopf, nicht etwa in jeder Zelle:
+
+ =========================
+ Erhoehte Reduktion Druck
+ bei Rolle 44
+ (mm) (MPa)
+ -------------------------
+ 5 8
+ ...
+
+
+Mehr Formatierungsoptionen, beispielsweise fr den Abstand zwischen
+Mazahl und Einheit, und sehr viele Makros fr Einheiten (z.B. Ohm,
+Hertz) bietet das Paket `SIunits'. Darin ist auerdem eine ausfhrliche
+Errterung der SI-Einheiten enthalten. Zahlen und Einheiten werden von
+diesem Paket jedoch in der meist serifenbehafteten Mathematikschrift
+gesetzt, auch wenn eine serifenlose Brotschrift verwendet wird. Dieses
+Problem lst das Paket `fancyunits', das das Paket `SIunits' fast ohne
+nderung eines bestehenden Dokuments ersetzen kann.
+
+units: CTAN: macros/latex/contrib/units
+SIunits: CTAN: macros/latex/contrib/SIunits
+fancyunits: http://tina.nat.uni-magdeburg.de/heiko/LaTeX/Tips_und_Tricks/fancyunits
+
+
+
+8.2.11 Wie erhalte ich kursive groe griechische Buchstaben?
+
+Whrend im mathematischen Modus fr kleine griechische Buchstaben kursiv
+als richtige Schreibweise gewhlt wird, erscheinen groe griechische
+Buchstaben senkrecht. Das Paket `fixmath' ndert dies bei den
+blicherweise verwendeten CM-Schriften. Die Pakete zur Benutzung anderer
+mathematischer Schriften haben teilweise eine Option, die dazu fhrt,
+da groe griechische Buchstaben ebenfalls kursiv gesetzt werden. Hierzu
+bitte die Dokumentation der jeweiligen Pakete durchlesen.
+
+fixmath: CTAN: macros/latex/contrib/was/
+
+
+
+8.3 Chemischer Struktur- und Formelsatz
+
+
+8.3.1 Wie kann ich chemische Strukturformeln mit LaTeX setzen?
+
+Die folgenden Pakete sind eine unvollstndige Auswahl (Freiwillige?!).
+Ob sie unter LaTeX2e, LaTeX 2.09 oder Plain-TeX verwendbar sind, mu,
+falls dies nicht vermerkt ist, selbst getestet werden.
+
+* PPCHTeX: Typesetting Chemical Formulas in TeX, von Hans Hagen und A.F.
+ Otten
+ Auf PiCTeX oder PSTricks basierendes Paket, mittlerweile das
+ flexibelste und umfangreichste Paket. PPCHTeX ist fr das TeX-Format
+ ConTeXt entwickelt worden, kann aber auch mit Plain-TeX und LaTeX (2e
+ und 2.09) eingesetzt werden. Eine ltere Version ist in den
+ Proceedings of the 9th European TeX Conference EuroTeX'95, Arnhem,
+ S. 197-222 und TUGboat 17(1), Mrz 1996, S. 54-66 beschrieben. Fr
+ PPCHTeX gibt es eine mail-basierte Diskussionsliste (siehe Frage
+ 1.3.4).
+* XymTeX: A Macro Package for Typsetting Chemical Structural Formulas,
+ von Shinsaku Fujita
+ Dieses System ist nach PPCHTeX das umfangreichste. Es verwendet
+ vorgefertigte Moleklklassen, in denen die Atompositionen vom Anwender
+ belegt werden knnen. Durch die `Kondensation' solcher Klassen lassen
+ sich so ziemlich alle denkbaren Molekle zaubern. Ohne Handbuch, das
+ 127 Seiten besitzt, und Zeit aber eher unbrauchbar, weil sehr
+ kompliziert. Eine Beschreibung findet sich auch in der TUGboat 16(1),
+ S. 81-88.
+* Chemstruct: Chemische Strukturformeln mit TeX, von Michael Ramek
+ Hier gibt man im wesentlichen von einem Bezugsatom ausgehend die Art
+ und die Himmelsrichtung der Bindung an und gelangt so recht schnell zu
+ brauchbaren Ergebnissen. So hangelt man sich von Atom zu Atom...
+ (Handbuch mit 18 Seiten).
+* ChemTeX: Typesetting Chemical Equations using LaTeX
+ Scheint auch mit Moleklklassen zu arbeiten, wenn auch lngst nicht so
+ komplex wie XymTeX, damit anwendungsfreundlicher, aber auch nur fr
+ einen begrenzten Satz an Strukturen geeignet... (Handbuch mit
+ 42 Seiten).
+* Chemsym: Chemical Symbols, von Mats Dahlgren
+ Vereinfacht die Eingabe und den Satz von chemischen Summenformeln und
+ Reaktionsgleichungen, indem Anweisungen fr den Satz der Elemente
+ inklusive Hoch- und Tiefstellung und eine groe Menge von chemischen
+ Symbolen vordefiniert werden. Fr LaTeX2e, mit Dokumentation.
+* streeTeX: One more Macro Package for typesetting Structural Formulae
+ with LaTeX
+ streeTeX, ein Kunstwort aus `structure' und `tree', verwendet
+ emTeX-Specials zum Zeichnen der Molekle. Moleklbindungen werden
+ dabei von einem Atom ausgehend in 12 verschiedene Richtungen
+ gezeichnet. Auerdem knnen NMR-Massenspektren gezeichnet werden.
+ (Handbuch mit 20 Seiten, englisch oder russisch)
+* OCHEM
+ OCHEM ist ein Paket fr den Satz chemischer Strukturformeln und
+ Reaktionsschemata. Es besteht aus einem Perl-Script, das in einer
+ speziellen Sprache formulierte Reaktionen in LaTeX- oder
+ PostScript-Graphiken konvertiert, die automatisch in ein Dokument
+ eingebunden werden knnen. Elemente eines Schemas sind Formeln, die
+ lineare, verzweigte oder konvergente Reaktionsketten bilden und
+ automatisch angeordnet werden. Elemente einer Formel sind Bindungen
+ (Richtung/Lnge), Textsymbole und Ringe bzw. allgemeine Strukturen.
+ Die Beschreibung erfolgt teilweise nach geometrischen Gesichtspunkten,
+ teilweise durch abstrakte Befehle. (Handbuch mit vielen Seiten und
+ Beispielen)
+
+Daneben gibt es noch Programme wie ChemDraw, ChemWindow o.., bei denen
+man die erstellte Strukturformel als PS-Datei ausgeben und dann in
+(La)TeX einbinden kann.
+
+PPCHTeX: http://www.pragma-ade.nl/ppchtex.htm
+ CTAN: macros/context/cont-ppc.zip
+PPCHTeX-Datenbank: http://www.walram.de/ppchtex/
+XymTeX: CTAN: macros/latex/contrib/xymtex/
+chemstruct: CTAN: macros/latex209/contrib/chemstruct/
+chemtex: CTAN: macros/latex209/contrib/chemtex/
+chemsym: CTAN: macros/latex/contrib/chemsym/
+streeTeX: CTAN: macros/latex/contrib/streetex/
+OCHEM: CTAN: support/ochem/
+
+
+
+8.3.2 Bei der Verwendung des Paketes `chemtex' mit LaTeX2e erhalte ich
+bei der Zuweisung \textfont1=\tenrm einen Fehler. Abhilfen?
+
+\tenrm ist ein alter, nur intern in LaTeX 2.09 zu verwendender Name
+eines Font (siehe auch Frage 5.2 ``LaTeX2e - Probleme beim Umstieg'').
+Mit dem Paket `rawfonts' kann man diese Namen (nach-)definieren:
+
+ \usepackage[only,tenrm]{rawfonts}
+
+
+rawfonts: CTAN: macros/latex/required/
+
+
+
+8.3.3 Das Makro \chemical, das u.a. auch in Helmut Kopka, ``LaTeX - eine
+Einfhrung'' beschrieben wird, funktioniert nicht. Was mu man ndern?
+
+Der im Makro (das aus dem TeXbook stammt!) verwendete Name \tensy des
+Math-Symbol-Font ist nur in Plain-TeX und LaTeX 2.09 definiert. LaTeX2e
+ldt darber hinaus die fr den mathematischen Formelsatz notwendigen
+Fonts erst zu Beginn der ersten zu setzenden Formel, so da man auch
+durch Nachdefinition mit Hilfe des Paketes `rawfonts' in bestimmten
+Situationen einen Fehler bekommen kann.
+Hier ist eine fr LaTeX2e verwendbare Definition von \chemical (die man
+in eine .sty-Datei schreiben oder mit \makeatletter ... \makeatother
+klammern mu):
+
+ %% Anpassung an LaTeX(2e) von Bernd Raichle
+ \DeclareRobustCommand{\chemical}[1]{%
+ {\(\m@th
+ \edef\resetfontdimens{\noexpand\)%
+ \fontdimen16\textfont2=\the\fontdimen16\textfont2
+ \fontdimen17\textfont2=\the\fontdimen17\textfont2\relax}%
+ \fontdimen16\textfont2=2.7pt \fontdimen17\textfont2=2.7pt
+ \mathrm{#1}%
+ \resetfontdimens}}
+
+
+8.4 Notensatz (*)
+
+
+8.4.1 Wie kann ich mit TeX Noten setzen? (*)
+
+Notensatz mit TeX begann vor vielen Jahren mit dem Paket MuTeX, mit dem
+einstimmiger Notensatz mglich war. Auf dessen Basis entwickelte Daniel
+Taupin MusicTeX, das durch Ergnzungen insbesondere von Ross Mitchell
+und Andreas Egler zu MusiXTeX wurde. Von Egler gibt es auch noch eine
+Testversion namens OpusTeX. Die MuTeX-Entwicklung wurde schon vor der
+endgltigen Fertigstellung eingestellt. MusicTeX wird gewartet, MusiXTeX
+wird gewartet und weiterentwickelt.
+MuTeX, MusicTeX und MusiXTeX sind auf CTAN verfgbar. Neue Benutzer
+sollten ausschlielich MusiXTeX verwenden und mglichst auch einen der
+Prprozessoren wie beispielsweise `PMX' oder speziell fr Chor- und
+Liedsatz `M-Tx'. Zu diesen drei Paketen gibt es in LaTeX geschriebene
+Dokumentation: MusiXTeX 116 Seiten, PMX 18 Seiten, M-Tx 34 Seiten.
+Ein weiteres Projekt, welches sich mit dem Notensatz befat, ist
+`LilyPond'.
+
+MusicTeX: CTAN: macros/musictex/
+MusiXTeX: CTAN: macros/musixtex
+MuTeX,
+MusicTeX http://icking-music-archive.sunsite.dk/
+und
+MusiXTeX:
+~: http://icking-music-archive.sunsite.dk/software/indexmt6.html
+LilyPond: http://www.cs.uu.nl/~hanwen/lilypond/
+GuitarTeX: http://guitartex.sourceforge.net
+
+
+
+8.4.2 Wer kann mir bei Fragen zu Notensatz mit TeX helfen?
+
+Hilfe findet man oft in der MuTeX-Mailing-Liste (siehe Frage 1.3.4).
+
+8.5 Verschiedenes (+)
+
+
+8.5.1 Ich erhalte die Fehlermeldung `! You can't use \spacefactor in
+vertical mode.' oder `Command \@ already defined.'. Mache ich etwas
+falsch?
+
+In den meisten Fllen liegt die Schuld an der Verwendung oder
+Neudefinition eines Makros beginnend mit \@, also einem At-Zeichen `@'
+am Anfang des Namens, in einem Dokument. Das At-Zeichen `@' ist aber
+nicht als Bestandteil eines Makronamens innerhalb des Dokuments erlaubt.
+Beispielsweise tritt der Fehler bei der Definition
+
+ \renewcommand{section}{%
+ \@startsection {section}{1}{\z@}{-3.5ex plus-1ex minus-.2ex}%
+ {2.3ex plus.2ex}{\normalfont\Large\bfseries}}
+
+in der Dokumentprambel auf.
+Vermeiden kann man diesen Fehler, indem man die Definition in eine
+.sty-Datei verschiebt oder in der Prambel mit \makeatletter ...
+\makeatother klammert, wie beispielsweise
+
+ \makeatletter
+ \@removefromreset{footnote}{chapter}
+ \makeatother
+
+
+8.5.2 Wie kann ich erreichen, da ein Zhler bei Erhhung eines anderen
+Zhlers zurckgesetzt bzw. nicht zurckgesetzt wird?
+
+Mit der Deklaration \@addtoreset{equation}{section} kann man erreichen,
+da der Gleichungszhler immer dann auf Null zurckgesetzt wird, wenn
+der Abschnittszhler erhht wird. Diese Deklaration wird implizit
+aufgerufen, wenn man in der Deklaration des Gleichungszhlers das
+optionale Argument verwendet, also \newcounter{equation}[section]. Soll
+das Gegenteil erreicht werden, so wird das Paket `remreset' bentigt,
+das die Deklaration \@removefromreset implementiert, mit der man durch
+\@removefromreset{equation}{section} obiges nachtrglich wieder
+rckgngig machen kann.
+Einfacher geht es mit den Anweisungen \counterwithin und
+\counterwithout, die das Paket `chngcntr' definiert. Beispiel:
+
+ \counterwithin{equation}{section}
+
+Nheres ist der Beschreibung am Ende der Datei ``chngcntr.sty'' zu
+entnehmen.
+
+remreset: CTAN: macros/latex/contrib/carlisle/remreset.sty
+chngcntr: CTAN: macros/latex/contrib/misc/chngcntr.sty
+
+
+
+8.5.3 Kann ich auch auf meinem System Umlaute und andere Sonderzeichen
+direkt mit der Tastatur in mein LaTeX-Dokument eingeben?
+
+Ja. Zu diesem Zweck dient das Standard-LaTeX-Paket `inputenc'. Es setzt
+die leider nicht standardisierten Zeichen mit einem Code>127 in eine
+einheitliche fr TeX verstndliche Kodierung um. Damit dies so wie
+gewnscht erfolgt, mu als Paketoption die zutreffende Kodierung des
+jeweiligen Betriebssystems angegeben werden:
+ \usepackage[Kodierung]{inputenc}
+Die folgenden Angaben und weitere sind fr `Kodierung' mglich:
+
+latin1 - Die meisten Unix-Systeme und VMS.
+ansinew - Windows 3.x, 9x, NT. Unwesentliche
+ Abweichungen zu `latin1'.
+cp437de - MSDOS.
+cp850 - OS/2, auch mit MSDOS, falls
+ explizit
+die Codepage IBM-850 benutzt wird.
+applemac - Apple-Macintosh.
+
+Dokumente, die unter Verwendung von `inputenc' geschrieben sind, knnen
+trotz unterschiedlicher Zeichenkodierung in den meisten Fllen auch auf
+fremden Systemen bersetzt werden. Eine Mischung unterschiedlicher
+Kodierungen ist allerdings nicht mglich. Siehe dazu auch
+
+8.5.4 Wie kann ich Umlaute in Texinfo-Dokumenten verwenden? Gibt es eine
+deutsche/internationalisierte Version von Texinfo?
+
+Mit der aktuellen Version 4.0 knnen Umlaute mit dem Makro @" (Bsp:
+@"A), Akzente mit @' (Bsp: @'e) usw. eingegeben werden. Darberhinaus
+existieren auch die Lettern wie @ss{}, die Ligaturen @AE{}, @ae{}, @OE{}
+und @oe{}, die Lettern mit Ring @AA{} und @aa{}, die durchgestrichenen
+Lettern @O{} und @o{} und einige mehr.
+Die Untersttzung auch der deutschen Sprache ist in neueren Versionen
+bereits enthalten.
+
+ http://texinfo.org
+
+
+
+8.5.5 Wie kann ich die Fehlermeldung `Text line contains an invalid
+character' abstellen, die ich unter emTeX bekomme, sobald ich Umlaute
+verwende?
+
+Um Umlaute verwenden zu knnen, mu man unter emTeX eine Formatdatei
+``8-bit clean'' erzeugen, da sonst alle Zeichen mit Code>127 auf das
+Zeichen 127 (= ^^?) abgebildet werden, das in TeX normalerweise als
+`invalid' deklariert ist. ``8-bit clean'' werden Formatdateien mit
+
+ makefmt 8bit ...
+
+(bzw. `tex -i -8 ...') erstellt.
+
+8.5.6 Wie kann man mit LaTeX Serienbriefe erstellen?
+
+Die Klasse `scrlettr' des KOMA-Script-Paketes und die Klasse `akletter',
+beide zur Erstellung von Briefen gedacht, untersttzen die Erstellung
+von Serienbriefen. Neben diesen gibt es mit den LaTeX-Paketen `mailing',
+`textmerg', `finder', `formletter' und `tk_Brief' noch weitere Pakete
+fr Serienbriefe.
+Fr eine kleinere Anzahl von Serienbriefen kann man den Text des Briefes
+auch in einem Makro mit \newcommand definieren, wobei man die fr jeden
+Empfnger unterschiedlichen Textteile diesem Makro als Parameter
+bergibt. Anschlieend wird dieses Makro dann mehrmals mit jeweiliger
+Anrede, Name, Strae, Ort usw. aufgerufen.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+akletter: CTAN: macros/latex/contrib/akletter/
+mailing: CTAN: macros/latex/contrib/mailing/
+textmerg: CTAN: macros/latex/contrib/textmerg/
+finder: CTAN: macros/latex209/contrib/letters/finder/
+formletter: CTAN: macros/generic/formlett/
+tk_Brief: http://www.deres-mueller.de/tk_Brief/
+
+
+
+8.5.7 Wie kann ich in LaTeX mehrere `enumerate'-Umgebungen verwenden,
+ohne da der Zhler immer wieder zurckgesetzt wird?
+
+Mit dem im Paket `mdwlist' enthaltenen Anweisungen \suspend{enumerate}
+und \resume{enumerate} kann der Zhler fr die Aufzhlungspunkte
+entsprechend gesetzt werden.
+Das `expdlist' bietet mit der Anweisung \listpart die Mglichkeit, in
+Listen Einschbe einzuflechten. Bentigt man mehrere zusammengehrige
+Aufzhlungslisten nur wegen dieser Einschbe, so ist dieses Paket die
+bessere Lsung.
+
+mdwlist: CTAN: macros/latex/contrib/mdwtools/
+expdlist: CTAN: macros/latex/contrib/expdlist/
+
+
+
+8.5.8 Wie kann ich den Dateinamen meines LaTeX-Dokuments innerhalb des
+Dokuments ausgeben?
+
+Man verwende
+
+ \jobname.tex
+
+fr diesen Zweck. Eine portable Lsung, um auch das Verzeichnis, in dem
+sich die Datei befindet, zu erhalten, existiert nicht.
+
+8.5.9 Meine Versuche, \figurename, \tablename o.. bei Verwendung des
+Pakets `babel' umzudefinieren, milingen. Was kann ich tun?
+
+Die naheliegende Lsung
+
+ \renewcommand{\figurename}{Abb.}
+ \renewcommand{\tablename}{Tab.}
+
+funktioniert so mit dem Paket `german', wenn danach die Sprache nicht
+gewechselt wird.
+Das Paket `babel' schaltet jedoch erst zu Beginn des Dokuments auf die
+gewhlte Sprache um. In diesem Fall werden dann \figurename und
+\tablename auf die in `babel' definierten Standardwerte `Abbildung' bzw.
+`Tabelle' gesetzt. Mit folgender Definition kann das Problem gelst
+werden:
+
+ \usepackage[german]{babel}
+
+ \addto\captionsgerman{%
+ \renewcommand{\figurename}{Abb.}%
+ \renewcommand{\tablename}{Tab.}%
+ }
+
+Bei Verwendung der neuen deutschen Rechtschreibung ist entsprechend
+
+ \usepackage[ngerman]{babel}
+
+ \addto\captionsngerman{%
+ \renewcommand{\figurename}{Abb.}%
+ \renewcommand{\tablename}{Tab.}%
+ }
+
+einzufgen.
+
+8.5.10 Ich habe neue Dateien zu dem TeX-Baum hinzugefgt, wieso werden
+sie von TeX bzw. LaTeX nicht gefunden?
+
+Um die Suche nach Dateien zu beschleunigen, verwenden einige TeX-Systeme
+eine Datenbank mit den Dateinamen im TeX-Baum. Werden neue Dateien
+hinzugefgt oder Dateien entfernt, so mu man bei diesen Systemen die
+Datenbank auf den aktuellen Stand bringen.
+Unter teTeX oder fpTeX geht das durch Aufruf von ``mktexlsr'' oder
+``texconfig rehash''; in lteren Versionen mu man ``texhash''
+verwenden.
+Unter MikTeX sollte man fehlende Komponenten ber das
+MikTeX-Options-Tool installieren, das automatisch die Datenbank der
+Dateinamen auf den aktuellen Stand bringt. Um diese Datenbank fr den
+TeXMF- und den lokalen Verzeichnisbaum in allen sonstigen Fllen zu
+aktualisieren, klickt man auf `Start', `Programme', `MikTeX', `MikTeX
+Options' und dort auf der Registerkarte `Roots' auf `Refresh FNDB' oder
+man ruft in der MS-DOS-Eingabeaufforderung ``initexmf -u'' auf.
+
+8.5.11 Wenn ich versuche, mit der Anweisung \tracingall Fehler in meinem
+LaTeX-Dokument zu finden, erhalte ich viele unntze Informationen. Kann
+man das ndern?
+
+Bei Verwendung des LaTeX-Pakets `trace' werden viele dieser oft unntzen
+Informationen unterdrckt. Mit den enthaltenen Anweisungen \traceon und
+\traceoff lassen sich die zu untersuchenden Bereiche weiter
+einschrnken. Besonders gnstige Ergebnisse werden mit eLaTeX erzielt
+(siehe Frage 3.3.4). Nheres ist in der Paketbeschreibung nachzulesen.
+
+trace: http://www.latex-project.org/code/experimental/trace/
+
+
+
+8.5.12 Wieso bekomme ich bei einem Acute-Akzentzeichen oder einem
+Anfhrungszeichen eine Fehlermeldung statt des gewnschten Zeichens?
+
+Bei der Eingabe eines Apostrophzeichens fr \'e, "' oder '' kommt es bei
+Benutzung einer entsprechenden Tastaturbelegung immer wieder vor, da
+man statt des Apostrophs (Code 29 in ASCII) auf der Tastatur das hnlich
+aussehende Akzentzeichen (Code 180 in ISO Latin-1) verwendet.
+
+8.5.13 Wie kann ich den blichen Absatzeinzug auch innerhalb von
+`minipage' bzw. `\parbox' erhalten?
+
+Die blichen Einstellungen von LaTeX sind derart, da innerhalb einer
+`minipage' oder einer `\parbox' Abstze ohne Einzug und mit vertikalem
+Abstand gesetzt werden. Will man dies ndern, so kann man fr
+Einzelflle die entsprechenden Lngenregister anpassen:
+
+ \begin{minipage}{...}
+ \setlength{\parindent}{1em}
+ \setlength{\parskip}{0pt}
+ ...
+ \end{minipage}
+
+Soll diese nderung fr alle Umgebungen einheitlich erfolgen, so ist
+eine der beiden internen Anweisungen `\@minipagerestore' oder
+`\@parboxrestore' zu ndern. `\@minipagerestore' wirkt nur auf
+`minipage'-Umgebungen, whrend `\@parboxrestore' neben `minipage' auch
+auf `\parbox' als auch auf andere Umgebungen und Anweisungen (wie
+Flieumgebungen, `\caption', `\marginpar', Funoten) wirkt. Folgendes
+Beispiel zeigt die nderung von `\@minipagerestore', wobei man diese
+Zeilen in eine .sty-Datei oder mit \makeatletter ... \makeatother
+geklammert in die Dokumentprambel schreiben mu:
+
+ \newcommand{\orig@minipagerestore}{}
+ \let\orig@minipagerestore=\@minipagerestore
+ \renewcommand{\@minipagerestore}{%
+ \orig@minipagerestore
+ \setlength{\parindent}{1em}%
+ \setlength{\parskip}{0pt}%
+ }
+
+
+8.5.14 Wie kann ich die Schriftgre relativ zur aktuell verwendeten
+eine Stufe kleiner oder grer whlen?
+
+Mit dem Paket `relsize' kann man die Schriftgre um einige Stufen
+kleiner oder grer als die aktuell verwendete whlen. Hierzu dienen die
+Anweisungen \smaller, \larger oder \relsize{n} bzw. \textsmaller{text},
+\textlarger{text} und \mathsmaller{formel}, \mathlarger{formel}.
+Will man die Schriftgre aller Funoten, Bildunterschriften oder
+berschriften um eine Stufe kleiner oder grer whlen, so ist es besser
+die Makros fr Funoten, Unterschriften bzw. berschriften entsprechend
+abzundern. Dies kann sehr einfach mit Paketen wie `footmisc',
+`caption2', `titlesec' oder `sectsty', die an anderer Stelle erwhnt
+werden, erfolgen.
+
+relsize: CTAN: macros/latex/contrib/misc/relsize.sty
+
+
+
+8.5.15 Wie verwende ich (La)TeX zusammen mit METAPOST?
+
+Der Artikel ``Some Experiences in Running METAFONT and METAPOST'' von
+Peter Wilson beschreibt die Verwendung von METAPOST in LaTeX.
+
+Peter Wilson:
+Some CTAN: info/metafp.pdf
+Experiences...:
+~: CTAN: info/metafp.ps
+Vincent
+Zoonekynd: http://www.math.jussieu.fr/~zoonek/LaTeX/Metapost/metapost.html
+Mtapost
+exemples:
+~: CTAN: info/metapost/examples/
+
+
+
+8.5.16 Wie kann ich ein LaTeX-Makro umdefinieren und dabei auf dessen
+bisherige Bedeutung zugreifen?
+
+Die einfache Vorgehensweise eine vorhandene Anweisung \foo durch
+beispielsweise
+
+ \renewcommand{\foo}[1]{%
+ ... tue was ... \foo{#1} ... nochmal was ...}
+
+funktioniert nicht, da sich \foo immer wieder selbst (rekursiv) aufrufen
+wrde, man also eine Endlosschleife htte. Um diese zu vermeiden, mu
+man zuerst die Bedeutung des Makro \foo unter einem anderen Makronamen
+retten und diesen dann in der neuen Definition verwenden:
+
+ % Die Originaldefinition des Makros unter einem neuen Namen retten.
+ % Sicherstellen, dass der neue Name bislang undefiniert ist:
+ \newcommand{\origfoo}{}
+ % Originaldefinition unter neuem Namen merken:
+ \let\origfoo=\foo
+ %
+ % Makro nun neu definieren:
+ \renewcommand{\foo}[1]{%
+ ... tue was ...
+ \origfoo{#1}%
+ ... nochmal was ...}
+
+
+8.5.17 Wie kann ich ein Zeichen hoch- oder tiefstellen, ohne den
+Mathematikmodus zu benutzen?
+
+Fr das Hochstellen von Zeichen ohne Einschaltung des Mathematikmodus
+bietet LaTeX die Anweisung \textsuperscript an.
+Mit den folgenden Definitionen, die analog der Definiton von
+\textsuperscript sind, erhlt man eine entsprechende Anweisung
+\textsubscript zum Tiefstellen von Zeichen:
+
+ \DeclareRobustCommand*\textsubscript[1]{%
+ \@textsubscript{\selectfont#1}}
+ \newcommand{\@textsubscript}[1]{%
+ {\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
+
+Da diese Definitionen LaTeX-interne Anweisungen verwenden, mssen sie in
+eine Paketdatei oder in \makeatletter ... \makeatother geklammert
+werden.
+Die Pakete `subscript' und `lhelp' sowie die aktuelle Version der
+KOMA-Script-Klassen enthalten bereits diese Definition und ist daher
+einer eigenen Definition vorzuziehen.
+
+subscript: CTAN: macros/latex/contrib/fragments/subscript.sty
+lhelp: CTAN: macros/latex/contrib/lhelp
+
+
+
+8.5.18 Wie kann ich das aktuelle Datum oder die aktuelle Uhrzeit in mein
+Dokument einbauen?
+
+Die Anweisung \today liefert die sprachabhngig formatierte Darstellung
+des aktuellen Datums, beispielsweise ,,September 19, 2003''.
+Das Paket `scrtime' des KOMA-Script-Paketes stellt die Anweisung
+\thistime zur Verfgung, mit der die aktuelle Uhrzeit in der Form hh:mm
+ausgegeben wird.
+Im Buch ,,Der LaTeX-Begleiter'' bei der Beschreibung des Paket `calc'
+findet man als Anwendungsbeispiel eine von KOMA-Script unabhngige
+Lsung, die wie \thistime das TeX-Register \time auswertet.
+Eine komfortable Lsung zur unterschiedlichen Datumsdarstellung bietet
+das Paket `isodate'. Hier werden neben der ``alten'' und ``neuen''
+deutschen Darstellung auch sterreichische, US-englische, franzsische,
+dnische und norwegische Formate untersttzt.
+Fr Uhrzeiten und Uhrzeitbereichen in unterschiedlicher Darstellung
+dient das Paket `uhrzeit'.
+
+KOMA-Script: CTAN: macros/latex/contrib/koma-script/
+isodate: CTAN: macros/latex/contrib/isodate/
+uhrzeit: CTAN: macros/latex/contrib/uhrzeit/
+
+
+
+8.5.19 Wie kann ich das Aussehen von Listenumgebungen, speziell deren
+vertikale Abstnde, auf einfache Weise verndern?
+
+Die Pakete `mdwlist', `paralist' und `expdlist' bieten verschiedene
+Mglichkeiten, das Aussehen von Listen zu beeinflussen. Dabei knnen
+sowohl die Einrckungstiefen und vertikale Abstnde als auch das
+Aussehen der Marken bei `description'-artige Listen angepat werden.
+Auerdem stehen vordefinierte kompakte Listen, bei `paralist' auch
+innerhalb des flieenden Textes, zur Verfgung.
+
+mdwlist: CTAN: macros/latex/contrib/mdwtools/
+paralist: CTAN: macros/latex/contrib/paralist/
+expdlist: CTAN: macros/latex/contrib/expdlist/
+
+
+
+8.5.20 Wie kann ich den Wert eines Lngenregister im Text oder in der
+Protokollausgabe anzeigen lassen?
+
+Leider bietet LaTeX hier keine Anweisungen an, aber man kann sich
+dennoch einfacher TeX-Mittel bedienen. Der Wert eines Lngenregister
+\laenge wird in der Protokollausgabe mit \showthe\laenge ausgegeben; zur
+Ausgabe wird der Formatierlauf unterbrochen und kann mit _Return_
+fortgesetzt werden. Fr die Anzeige im Text ist die Anweisung
+\the\laenge hilfreich, die zum Wert des Lngenregisters expandiert.
+Beide Anweisungen geben den Wert in Punkten an, fr andere Einheiten mu
+selbst umgerechnet werden. Zum Umrechnen eignet sich das Paket
+`printlen'.
+
+printlen: CTAN: macros/latex/contrib/misc/printlen.sty
+
+
+
+8.5.21 Wie kann ich mit LaTeX Bildschirmprsentationen erzeugen?
+
+Es gibt etliche meist auf dem PDF-Format basierende Lsungen. Einen
+guten berblick bietet die folgende Adresse.
+
+Michael Wiedmann:
+Screen http://www.miwie.org/presentations/presentations.html
+Presentation
+Tools:
+
+
+
+8.5.22 Welche veralteten oder ungnstigen LaTeX-Pakete und
+LaTeX-Anweisungen sollte ich meiden? (+)
+
+Die in der folgenden unvollstndige Aufstellung unter ``zu ersetzen
+durch'' gemachten Angaben sollten, auch wenn sie hier nicht nher
+begrndet werden knnen, befolgt werden. Es handelt sich _nicht_
+vorrangig um formale Grnde, die diesen Empfehlungen zugrunde liegen. Im
+Zweifelsfall ziehe man geeignete Dokumentationen zu Rate.
+
+veraltetes/ungnstiges Paket zu ersetzen durch
+a4, a4wide Klassenoption a4paper
+caption caption2
+doublespace setspace
+epsfig, epsf graphicx
+fancyheadings fancyhdr
+floatfig, picinpar picins, floatflt, wrapfig
+umlaut inputenc
+\usepackage{isolatin1} \usepackage[latin1]{inputenc}
+natdin dinat
+scrlettr scrlettr2
+scrpage scrpage2
+\usepackage{t1enc} \usepackage[T1]{fontenc}
+times oder pslatex mathptmx, helvet, courier
+palatino mathpazo, helvet, courier
+\usepackage[ngerman]{babel} Nur eines der beiden Pakete ist sinnvoll.
+\usepackage{ngerman}
+
+
+
+veraltete/ungnstige Anweisung zu ersetzen durch
+\it, \rm, \bf \itshape, \rmfamily, \bfseries
+ \textit{...}, \textrm{...}, \textbf{...}
+Texthervorhebung mit: \emph{...} (_oft so gemeint_)
+\textit{...}
+\parindent0pt \setlength{\parindent}{0pt}
+center-Umgebung innerhalb \centering
+von figure-Umgebungen
+\\, um im Flietext einen Leerzeile oder \par
+Absatz zu beginnen
+\usepackage[treiber] \usepackage{graphicx}
+{graphicx} (_meistens mglich_)
+\includegraphics \includegraphics{dateiname}
+{dateiname.endung} (_meistens mglich_)
+$$...$$ \begin{displaymath}...\end{displaymath}
+
+
+--- DE-TeX-FAQ Ende Teil 8 ---
diff --git a/help/de-tex-faq/part9 b/help/de-tex-faq/part9
new file mode 100644
index 0000000000..e1754623c5
--- /dev/null
+++ b/help/de-tex-faq/part9
@@ -0,0 +1,658 @@
+Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!npeer.de.kpn-eurorings.net!news-kar1.dfn.de!news-ham1.dfn.de!news.uni-hamburg.de!not-for-mail
+From: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+Newsgroups: de.comp.text.tex,de.answers,news.answers
+Subject: TeX, LaTeX, DANTE e.V.: FAQ - Fragen und Antworten (Part 9 of 11)
+Supersedes: <de-tex-faq-9-1020876881@dante.de>
+Followup-To: de.comp.text.tex
+Date: 19 Sep 2003 14:43:18 +0200
+Organization: DANTE, Deutschsprachige Anwendervereinigung TeX e.V.
+Lines: 629
+Approved: news-answers-request@MIT.EDU
+Distribution: world
+Expires: 03 Nov 2003 13:43:13 MET
+Message-ID: <de-tex-faq-9-1063975393@dante.de>
+References: <de-tex-faq-1-1063975393@dante.de>
+Reply-To: dantefaq@dante.de (DE-TeX-FAQ-Maintainer)
+NNTP-Posting-Host: sun.dante.de
+Mime-Version: 1.0
+Content-Type: text/plain; charset=ISO-8859-1
+Content-Transfer-Encoding: 8bit
+X-Trace: rzsun03.rrz.uni-hamburg.de 1063975398 893 134.100.9.52 (19 Sep 2003 12:43:18 GMT)
+X-Complaints-To: usenet@news.uni-hamburg.de
+NNTP-Posting-Date: 19 Sep 2003 12:43:18 GMT
+Summary: This posting contains a list of Frequently Asked Questions
+ (and their answers) about the typesetting system TeX and
+ about DANTE e.V., the german-speaking TeX users group.
+ It is in German and uses the ISO Latin-1 character set.
+Keywords: FAQ TYPESETTING TeX USERGROUP DANTE
+Xref: senator-bedfellow.mit.edu de.comp.text.tex:117406 de.answers:9383 news.answers:258272
+
+Posted-By: auto-faq 3.3 (Perl 5.008)
+Archive-name: de-tex-faq/part9
+Posting-Frequency: monthly
+Copyright-Notice: siehe Abschnitt 1.1/see Section 1.1
+URL: http://www.dante.de/faq/de-tex-faq/
+
+--- DE-TeX-FAQ Beginn Teil 9 ---
+
+
+
+ Fragen und Antworten (FAQ) ber das Textsatzsystem TeX und DANTE,
+ Deutschsprachige Anwendervereinigung TeX e.V.
+
+
+ Bernd Raichle, Rolf Niepraschk und Thomas Hafner
+
+
+ Version 72 vom September 2003
+
+------------------------------------------------------------------------
+
+
+9 METAFONT und Schriften
+
+
+9.1 METAFONT und METAFONT-Hilfsprogramme
+
+
+9.1.1 Was ist ein Meta-Font?
+
+Um die einzelnen Zeichen einer Schrift, eines Font, auf Papier zu
+bringen, mu man wissen, an welchen Stellen das Papier mit Druckerfarbe
+geschwrzt werden soll und an welchen nicht. Diese Information kann auf
+verschiedene Arten reprsentiert werden: Die einfachste Form ist die
+`Bitmap' bzw. `Pixelmap', d.h. jedes Zeichen wird gerastert und fr
+jeden einzelnen Punkt im Raster (= Pixel) wird abgespeichert, ob diese
+Stelle geschwrzt werden soll. Eine Bitmap-Reprsentation hat jedoch den
+Nachteil, da man diese nicht ohne weiteres vergrern, verkleinern oder
+die Rasterung an eine andere Auflsung eines Ausgabegerts anpassen
+kann, da man in den meisten Fllen unerwnschte Seiteneffekte bekommt
+(Stufen, Moir-Effekte, dnnere Linien verschwinden bei Verkleinerung,
+als regelmige oder unregelmige Muster sichtbare Rasterung u..).
+Man verwendet zur Beschreibung der Ausmae und der Form eines Zeichens
+daher besser eine rasterungs-, also auflsungsunabhngige
+Reprsentation. Dazu gibt es nun mehrere Verfahren:
+In METAFONT legt man Linienzge durch Punkte und durch diese Punkte
+festgelegte Spline-Kurven fest und zieht diese mit einem vorher
+definierten `Pinsel' nach. Durch die Form und die Lage des verwendeten
+Pinsels knnen mit denselben Kurven sehr unterschiedliche Zeichenformen
+erzeugt werden. Nachdem das Zeichen aus einzelnen Kurvenzgen definiert
+und mit unterschiedlichen Pinseln gezeichnet wurde, rastert METAFONT die
+dadurch eingefrbten Flchenteile und erzeugt daraus einen Font in Form
+einer Bitmap. Da METAFONT zur Programmierung einer solchen
+Font-Beschreibung eine Programmiersprache definiert, kann ein
+Font-Designer einer Font-Beschreibung beliebig viele Parameter mitgeben,
+die die Form und Ausmae der einzelnen Zeichen der erzeugten Schrift in
+unterschiedlichen Richtungen verndern. Wegen dieser Mglichkeit, aus
+einer einzigen Beschreibung durch Wahl verschiedener Parameter viele
+verschiedene Schriften erzeugen zu knnen, nennt man diese
+Font-Beschreibungen auch `Meta-Font'. Man kann also durch Wahl der in
+einem Meta-Font definierten Parameter unterschiedliche Fonts in
+verschiedenen Gren erzeugen. Durch Angabe der gewnschten Auflsung
+und weiterer Parameter des Ausgabegerts kann wiederum fr einen solchen
+Font eine optimal an das jeweilige Ausgabegert angepate
+Bitmap-Wiedergabe dieses Fonts erzeugt werden.
+Neben dieser von METAFONT verwendeten Beschreibung eines Fonts in Form
+von mit Pinseln gezeichneten Spline-Kurven kann man die Form eines
+Zeichens auch durch die Angabe des Umrisses der zu schwrzenden Flche
+beschreiben. Auch hier werden wiederum Spline-Kurven zur Beschreibung
+der Umrisse eines Zeichens verwendet. Diese Beschreibung in Form eines
+sogenannten `Outline' wird beispielsweise in PostScript-Schriften
+verwendet.
+
+9.1.2 Was sind tfm-, pl-, gf-, pk-, pxl-Dateien?
+
+Neben dem Aussehen der einzelnen Zeichen in einem Font werden noch
+weitere Informationen ber jedes einzelne Zeichen und ber
+schrift-globale Parameter bentigt: Von jedem Zeichen mu TeX die
+Ausmae in Form von Breite, Hhe und Tiefe in Bezug zur Grundlinie
+wissen. Zu bildende Ligaturen (z.B. f+f => ff), das Kerning zwischen
+zwei Zeichen (z.B. Unterschneidung bei `Ta') und beispielsweise der zu
+verwendende Wortabstand sind weitere Informationen, die ber einen Font
+abgelegt sein mssen, da sie von TeX bentigt werden.
+Diese Informationen liest TeX aus der `TeX Font Metric' oder kurz
+tfm-Datei. Die Programme `pltotf' und `tftopl' wandeln die Informationen
+in einer tfm-Datei in eine lesbare Form, die `Property List' oder kurz
+pl-Datei um.
+In den gf- (Generic Font), pxl- (Pixel) und pk- (Packed Pixel) Dateien
+sind die Bitmap-Reprsentationen jedes Zeichens einer Schrift abgelegt.
+Da pk- und pxl-Dateien genau dieselben Informationen enthalten, die
+pxl-Dateien jedoch mehr Platz bentigen, werden diese heutzutage nicht
+mehr verwendet und untersttzt. Mit den Programmen `gftopk' und `pktogf'
+knnen die Bitmap-Reprsentationen ineinander umgewandelt werden. Da
+gf-Dateien in der Lage sind, in einer Bitmap neben den einzelnen Pixeln
+noch weitere Informationen zu enthalten (z.B. `special'-Anweisungen),
+knnen bei dieser Umwandlung Informationen verloren gehen. Da jedoch nur
+sehr wenige Programme und Gertetreiber diese zustzlichen Informationen
+verwenden und die pk-Darstellung viel kompakter ist, sind gf-Dateien
+normalerweise nur fr METAFONT wichtig.
+METAFONT erzeugt aus einer mf-Source eine tfm-Datei mit der
+auflsungs_un_abhngigen `TeX Font Metric' und eine auflsungsabhngige
+gf-Datei. Aus der gf-Datei wird blicherweise mit `gftopk' eine pk-Datei
+erzeugt.
+TeX verwendet nur die Informationen in der tfm-Datei, die Bitmap in der
+gf- bzw. der pk-Datei wird von TeX _nicht_ gelesen. Ein Gertetreiber,
+der eine dvi-Datei druckt oder darstellt, verwendet die pk-Dateien und
+in einigen Fllen auch die tfm-Datei.
+
+9.1.3 Was sind virtuelle Fonts, was vpl-, vf-Dateien?
+
+Ein virtueller Font ist, wie der Name schon sagt, eine Schrift, die
+keine real (in Form einer Bitmap) existierenden Zeichen enthlt.
+Stattdessen wird in einem virtuellen Font auf andere Schriften und die
+dort enthaltene Zeichen verwiesen. Durch diesen `Trick' kann man
+beispielsweise die Kodierung der Zeichen in einer Schrift umdefinieren
+oder eine Schrift aus Zeichen mehrerer Schriften zusammensetzen, um so
+z.B. einzelne Zeichen durch andere zu ersetzen. Darber hinaus kann man
+in virtuellen Fonts auch einzelne Zeichen aus mehreren Zeichen
+zusammensetzen, indem man beispielsweise fertig akzentuierte Zeichen aus
+dem entsprechenden Akzent- und Basiszeichen bildet. Eine weitere
+Anwendung fr virtuelle Fonts ist die Verwendung einer Ersatzschrift fr
+eine nicht verfgbare Schrift, die dieser mglichst nahekommt und
+dieselben TeX-Font-Metric-Informationen besitzt.
+Eine vf-Datei enthlt die Definition eines solchen virtuellen Fonts in
+binrer, sehr kompakter Form. Dieser vf-Datei mu eine tfm-Datei
+zugeordnet sein, in der TeX die `TeX Font Metric' fr diese Schrift
+finden kann. Eine vpl-Datei ist eine fr den Menschen lesbare
+Darstellung der vf- und tfm-Datei in Form von `Property Lists'. Mit dem
+Programm `vptovf' kann aus einer vpl-Datei eine vf- und die zugehrige
+tfm-Datei erzeugt werden, mit `vftovp' bekommt man aus diesen beiden
+Dateien wieder die vpl-Datei.
+TeX `wei' nichts von virtuellen Fonts. TeX liest keine vf-Dateien,
+sondern bentigt nur die zugehrige tfm-Datei, aus der nicht ersichtlich
+ist, ob dies ein `realer' oder ein virtueller Font ist. vf-Dateien
+werden nur von den Gertetreibern verwendet. Fr Treiber, die (noch)
+keine virtuellen Fonts untersttzen, kann das Programm `dvicopy'
+verwendet werden, um eine dvi-Datei in eine dvi-Datei umzuwandeln, in
+der alle virtuellen Fonts `aufgelst' worden sind, also nur noch `reale'
+Fonts verwendet werden. Achtung: Die meisten verfgbaren virtuellen
+Fonts sind unabhngig vom Ausgabegert, sie knnen jedoch auch abhngig
+vom Ausgabegert sein!
+
+9.1.4 Was ist METAPOST?
+
+METAPOST ist ein aus METAFONT abgeleitetes Programm zum Erstellen von
+PostScript-Zeichnungen, das von John Hobby, einem ehemaligen Mitarbeiter
+von Donald E. Knuth, entwickelt wurde. Die METAPOST-Sprache ist sehr eng
+verwandt mit METAFONT, untersttzt aber einige zustzliche Features, wie
+beispielsweise das Beschriften von Abbildungen in TeX ber einen
+Prprozessor (dies setzt den dvi-Treiber `dvips' voraus).
+Um eine Zeichnung zu erstellen, muss man ein METAPOST-Programm schreiben
+und compilieren. Diese Arbeitsweise hnelt METAFONT, ist somit eben ganz
+anders als die sonst gewohnten Grafik-/Malprogramme. METAPOST ist dafr
+aber gut fr berechnete Zeichnungen geeignet oder zum Plotten von
+Funktionen oder Datenwerten. Knuth benutzt es selbst fr Zeichnungen in
+seinen Bchern. Das Programm ist erst seit Anfang 1995 frei erhltlich,
+vorher nur nach Abschlu eines `non-disclosure agreement'.
+Implementierungen von METAPOST existieren mittlerweile fr sehr viele
+Plattformen:
+
+* Web2c: CTAN: systems/web2c/
+ Web2c enthlt ab Version 7.0 METAPOST-Sources, wobei Web2c
+ mittlerweile neben Unix auch Amiga, OS/2 und Windows 95/98/NT und BeOS
+ untersttzt.
+* teTeX: CTAN: systems/unix/teTeX/
+ Ab teTeX Version 0.4 ist METAPOST enthalten.
+* Amiga: CTAN: systems/amiga/amiweb2c/ (Andreas Scherer)
+ Siehe auch Web2c.
+* OS2: Siehe Web2c.
+* Windows 95/NT: Siehe Web2c.
+* DOS: CTAN: systems/msdos/metapost/ (Piet van Oostrum)
+ pat zu emTeX
+ CTAN: systems/msdos/dostp22/ (Peter Breitenlohner)
+ integriert in PubliC-(e-)TeX/MF/MP, TDS-kompatibel
+* MacOS: CTAN: nonfree/systems/mac/cmactex/ (Tom Kiffe)
+
+Seit Mrz 2000 ist fr METAPOST auch der graphische Editor `Metagraf'
+ffentlich verfgbar, der gerade entwickelt wird. Er ist in Java
+geschrieben und somit auf vielen Betriebssystem lauffhig.
+
+METAPOST: http://cm.bell-labs.com/who/hobby/MetaPost.html
+ CTAN: graphics/metapost/
+Peter Wilson:
+Some CTAN: info/metafp.pdf
+Experiences...:
+ CTAN: info/metafp.ps
+Hans Hagen: http://www.pragma-ade.com/pragma-ade/general/manuals/beta/metafun-p.pdf
+metafun:
+Denis Roegel:
+The metaobj
+tutorial and http://www.loria.fr/~roegel/TeX/momanual.pdf
+reference
+manual:
+METAOBJ: CTAN: graphics/metapost/contrib/macros/metaobj/
+Metagraf: http://w3.mecanica.upm.es/metapost/metagraf.html
+
+
+
+9.1.5 Was ist MFT?
+
+`mft' ist ein Programm, das aus METAFONT-Quellcode eine TeX-Datei
+erzeugt, mit der dieser Quellcode schn formatiert erscheint. Damit es
+wirklich schn aussieht, sind zustzliche Kommentare im Quellcode
+notwendig. Nur sehr wenige Autoren von METAFONT verwenden `mft'.
+
+9.1.6 Beim bersetzen einer mf-Datei erhalte ich immer eine gf-Datei mit
+Endung `.2602gf' (bzw. `.260' bei Filesystemen, die nur drei Zeichen als
+Datei-Extension zulassen). Wieso?
+
+Zur Erzeugung einer Schrift fr ein bestimmtes Ausgabegert bentigt
+METAFONT eine Beschreibung in Form einer `Mode Definition' (kurz:
+`mode_def'), in der u.a. die Auflsung des Ausgabegerts festgelegt
+wird. METAFONT wird meist mit
+
+ mf \mode:=<Mode-Name>; mag:=<Magnification>; input <Font-Filename>
+
+aufgerufen (unter Unix Quote-Zeichen ' um die Argumente im
+METAFONT-Aufruf nicht vergessen!), wobei mit <Mode-Name> der Namen einer
+solchen `mode_def' anzugeben ist. Wird kein `mode' angegeben oder ist
+<Mode-Name> unbekannt, verwendet METAFONT den Proof-Mode, der einen
+Korrekturabzug der Schrift erstellt. Damit die Zeichen in diesem
+Korrekturabzug gro genug sind, verwendet METAFONT dazu die Auflsung
+2602dpi (= `dots per inch'). Falls dies nicht erwnscht war, sollte man
+berprfen, ob der `mode' korrekt gesetzt wurde, ob <Mode-Name>
+beispielsweise korrekt angegeben wurde (Schreibfehler!) und ob
+<Mode-Name> bei der Erstellung der base-Datei (`Dumpen' der Datei
+``plain.mf'') mit `mode_def' definiert wurde.
+
+9.1.7 Wozu bentige ich fr jeden Druckertyp eine andere Anpassung in
+Form einer `mode_def'? Wo finde ich fr den Drucker XYZ eine solche
+Anpassung?
+
+Jedes Ausgabegert hat unterschiedliche Charakteristiken. Zum einen
+unterscheiden sie sich in der Auflsung, zum anderen beispielsweise auch
+in der Gre eines gezeichneten Pixels. So wird bei einem
+Tintenstrahldrucker im Vergleich zu einem Laserdrucker in den meisten
+Fllen ein einzelner Punkt etwas grer ausfallen. Sehr groe
+Unterschiede treten prinzipbedingt beim Vergleich von sogenannten
+`schwarz'- und `wei'-schreibenden Laserdruckern auf. Auch wird beim
+Schnitt zweier Kurven (z.B. in der Mitte des Zeichens `X') die
+geschwrzte Flche etwas grer ausfallen, da die Druckerfarbe abhngig
+vom Druckprinzip und vom Druckwerk mehr oder weniger ineinander
+verlaufen kann. Damit METAFONT all diese und weitere Eigenschaften eines
+Ausgabegerts bei der Erzeugung der Bitmap-Rasterung eines Zeichens in
+Betracht ziehen kann, werden die einzelnen Parameterwerte fr ein
+Ausgabegert in einer `Mode Definition' mit der Anweisung `mode_def'
+abgelegt.
+Da die Erstellung einer neuen `Mode Definition' fr ein Ausgabegert
+einiges an Arbeit (Testdruck, berprfen, anpassen, Testdruck usw.)
+bedeutet, wurden von Karl Berry alle bisher fr verschiedene
+Ausgabegerte gefundenen `Mode Definitions' in der Datei ``modes.mf''
+gesammelt. Da ``modes.mf'' neben den `Mode Definitions' noch dafr
+sorgt, da man verschiedene Informationen (z.B. `coding scheme') ber
+einen Font setzen kann und diese korrekt abgelegt werden, ist diese
+Datei jedem empfohlen.
+
+modes.mf: CTAN: fonts/modes/modes-3.5.mf
+(Hinweis: Seit Februar 2002 gibt es die Version 3.5 mit
+Voreinstellungen fr neuere Drucker)
+
+
+
+9.1.8 Kann ich aus einer vorhandenen tfm-Datei die mf-Source erzeugen?
+Gibt es dafr ein Programm?
+
+Nein. tfm-Dateien enthalten keine Bitmap- oder hnliche Information ber
+das Aussehen der Zeichen in einer Schrift. Daher kann aus einem tfm-File
+weder eine pk-Datei noch die mf-Source restauriert werden.
+Es ist jedoch mglich, aus einer pk- und der tfm-Datei einer Schrift
+eine mf-Source zu erstellen. Dabei ist das entstehende Resultat jedoch
+kein _Meta_-Font mehr, sondern `nur' noch ein mf-Programm fr genau
+diese Schrift. Das Ergebnis ist je nach Aufwand mehr oder weniger gut
+und verlangt in den meisten Fllen noch einiges an Handarbeit, so da
+sich der Aufwand nur in seltenen Fllen lohnt.
+
+9.1.9 Wie kann ich nur die tfm-Dateien einer Schrift erzeugen?
+
+In der Datei ``modes.mf'' ist dafr die Mode-Definition `nullmode'
+gedacht, in der neben der tfm- zwar auch eine gf-Datei erzeugt wird,
+jedoch in einer Auflsung von 101dpi, so da dies schneller als mit
+300dpi oder 600dpi geschieht.
+
+9.2 Schriften - allgemein (*)
+
+
+9.2.1 Gibt es eine Schrift XYZ? Wo finde ich diese?
+
+Als erste Informationsquelle sollte man die Liste ``metafont-list'' der
+verfgbaren METAFONT-Schriften nach der gesuchten Schrift durchsehen.
+Diese Liste enthlt eine kurze Beschreibung und Klassifikation der
+meisten Schriften, die man auf CTAN im Verzeichnis ``CTAN: fonts/''
+finden kann.
+Beschrnkt man sich nicht nur auf in METAFONT-Quellen vorhandene
+Schriften, kann man auch Schriften in PostScript-Type-1- oder
+Type-3-Form, PCL-Schriften u.a. auf verschiedenen ftp-Servern finden.
+Existieren fr diese Schriften Font-Metriken, die man in eine tfm-Datei
+umwandeln kann, sind sie sehr einfach unter (La)TeX verwendbar (evtl.
+nach Umkodierung mittels virtueller Fonts). Verschiedene Programme dafr
+findet man auf CTAN im Verzeichnis ``CTAN: fonts/utilities/'', fertige
+Anpassungen findet man fr weitverbreitete Schriften ebenso unter
+``CTAN: fonts/''.
+
+metafont-list: CTAN: info/metafont-list
+Liste de fontes
+au format MF sur http://www.math.jussieu.fr/~zoonek/LaTeX/MF/liste.html
+les archives
+CTAN:
+Zeichenstze und http://www.loria.fr/services/tex/german/fontes.html
+Symbole:
+dpunkt-Verlag: http://www.dpunkt.de/produkte/latex/fonts/
+Adobe Type http://www.adobe.com/type/
+Library:
+symbols: CTAN: info/symbols/
+comprehensive: CTAN: info/symbols/comprehensive/
+Luc Devroye: Font http://cgm.cs.mcgill.ca/~luc/fonts.html
+Pages:
+
+
+
+9.2.2 Wie installiere ich mit `dvips' eine neue PostScript-Schrift, so
+da ich diese unter (La)TeX verwenden kann?
+
+Schritt 0 - Dokumentation lesen:
+Zuerst sollte man sich die Dokumentation zum `dvips' durchlesen. Diese
+beschreibt die wichtigsten Schritte, auch wenn die dort beschriebenen
+Dateinamen und die Kodierungen fr die PS-Schriften veraltet sind (gilt
+zumindest fr die Dokumentation bis `dvips' Version 5.58). Auerdem
+sollte man `Filenames for TeX fonts' von Karl Berry in der Version 2.0
+(oder neuer) durchlesen, in dem ein fr alle TeX-Systeme verwendbares,
+einheitliches Namensschema beschrieben wird.
+Schritt 1 - TeX-Anpassungen besorgen oder selbst generieren:
+Gibt es auf CTAN im `psfonts'-Verzeichnis bereits fertige Anpassungen?
+Wenn ja, sollte man diese verwenden. Wenn nein, sollte man sich das Tool
+`fontinst' besorgen, mit dem man relativ einfach aus der mit dem
+PostScript-Font mitgelieferten afm-Datei die notwendigen virtuellen
+Fonts (vf-Dateien) mit den entsprechenden Fontkodierungen und
+Font-Definitions-(fd)-Dateien fr LaTeX erzeugen lassen kann. Fr
+Textschriften sollten zumindest vf-Dateien fr OT1-Kodierung, besser
+auch noch fr T1-Kodierung erzeugt werden.
+Schritt 2 - PS- und TeX-Font-Dateien installieren:
+Nach Schritt 1 sollten beispielsweise fr die Schrift `URW Antiqua
+Regular Roman Condensed' bzw. nach Berrys Namenschema `uaqr...c...'
+folgende Dateien vorhanden sein:
+
+* PS-Schrift und zugehrige Font-Metrik: uaqr8ac.{pfb,afm}
+* virtueller Font, zugehrige TeX-Font-Metriken und PS-Reencoding:
+ uaqr8rc.{vpl,vf,tfm} TeX Base-1 Encoding (unkodiert,
+ Adobe-Std.-Encoding)
+ uaqr7tc.{vpl,vf,tfm} TeX-Text-/OT1-/CM-Encoding (`7-bit')
+ uaqr8tc.{vpl,vf,tfm} Cork-TeX-Text-/T1-/EC-Encoding (`8-bit')
+ 8r.enc PS-Reencoding, in `fontname' enthalten
+* LaTeX-Font-Definition-Files:
+ ot1uaq.fd (vormals: OT1uaq.fd)
+ t1uaq.fd (vormals: T1uaq.fd)
+ ts1uaq.fd
+ antiqua.sty
+
+und noch einige weitere Dateien fr die `slanted'- und `small
+caps'-Varianten, die man mit `fontinst' erzeugen kann.
+Diese Dateien werden nun in folgende Verzeichnisse gelegt:
+ *.fd, *.sty => TEXINPUTS (TeX)
+ *.tfm => TEXFONTS bzw. `T'-Eintrag (TeX + dvips)
+ *.vf => `V'-Eintrag oder VFFONTS (dvips)
+ *.pfb/pfa => `H'-Eintrag oder DVIPSHEADERS (dvips)
+Schritt 3 - Map-Datei des PS-Fonts fr `dvips' erzeugen:
+Map-Datei fr `dvips' erzeugen, in der die Zuordnung des Font-Namens in
+TeX zu dem in PS verwendeten festgelegt wird und evtl. die zu ladenden
+pfb-/pfa- und PS-Reencoding-Dateien angegeben werden. In unserem
+Beispiel enthlt die Map-Datei `uaq.map' die Zeile
+
+ uaqr8rc URWAntiquaT-RegularCondensed "TeXBase1Encoding ReEncodeFont"
+ <8r.enc <uaqr8ac.pfb
+
+(dies mu eine einzige Zeile sein, sie wurde hier nur umbrochen, um eine
+zu lange Zeile zu vermeiden!) und evtl. noch Zeilen fr weitere
+Schriften und Varianten.
+Diese Map-Datei in ein Verzeichnis legen, in dem `dvips' nach
+PS-Header-Dateien sucht (Umgebungsvariable DVIPSHEADERS bzw. `H'-Eintrag
+in ``config.ps'').
+Schritt 4 - `dvips'-Konfigurationsdatei anpassen:
+Konfigurationsdatei ``config.ps'' des `dvips' ndern: Die in Schritt 3
+erstellte Map-Datei durch die in ``config.ps'' neu einzutragende Zeile
+
+ p +uaq.map
+
+zustzlich zur Standard-Map-Datei ``psfonts.map'' laden. (ltere
+`dvips'-Versionen verstehen das `+' nicht; bei diesen mu man den Inhalt
+der Map-Datei ``uaq.map'' an die Datei ``psfonts.map'' anhngen und die
+obige Zeile in ``config.ps'' ist wegzulassen.) Auerdem sollte man noch
+berprfen, ob das Verzeichnis, in dem die Map-Datei und die
+pfb-/pfa-Dateien zu finden sind, im Suchpfad nach PS-Header-Dateien
+enthalten ist (DVIPSHEADERS bzw. `H'-Eintrag in ``config.ps'').
+Schritt 5 - Anpassungen testen und verwenden:
+Mit LaTeX kann man unsere Beispielschrift einfach mittels des Pakets
+`antiqua' verwenden, da diese Schrift damit als `\rmdefault'-Schrift
+verwendet wird. Ohne dieses Package kann man auch durch die Anweisung
+`\usefont'{OT1}{uaq}{m}{n} diese Schrift kurz austesten. LaTeX mte
+dazu die fd- und tfm-Dateien finden und einlesen knnen. `dvips' benutzt
+dann die angepate Konfigurationsdatei, die virtuellen Schriften
+``uaqr*.vf'', die Map-Datei ``uaq.map'', die eigentliche PS-Schrift
+``uaqr8ac.pfb'' und schlielich noch ``8r.enc''.
+Fr die PostScript-Schriften, die standardmig mit den meisten
+PostScript-fhigen Druckern mitgeliefert werden, als auch fr einige
+freie Schriften und die Lucida-Schriftfamilie existiert in Form von
+`psnfss' eine Menge von LaTeX-Paketen.
+Unter Plain-TeX kann man diese Schrift relativ einfach z.B. durch die
+Anweisung \font\rmantiqua=uaqr7tc laden und anschlieend verwenden. Zur
+Verwendung der T1-kodierten Variante ``uaqr8tc'' sind, wie bei der
+Verwendung der EC-Schriften unter Plain-TeX, noch einige Anpassungen
+notwendig.
+Unter LaTeX 2.09 gilt dasselbe wie fr Plain-TeX, nur sollte man hier
+besser \newfont{\rmantiqua}{uaqr7tc} verwenden. Will man diese Schrift
+und deren Varianten statt den CM-Schriften in einem Dokument verwenden,
+so sind grere nderungen notwendig, die den Rahmen dieser FAQ sprengen
+wrden. Am einfachsten ist ein Umstieg auf eine aktuelle LaTeX-Version!
+
+dvips.tex: CTAN: dviware/dvips/
+fontname: CTAN: info/fontname/
+8r.enc: CTAN: info/fontname/8r.enc
+psfonts: CTAN: fonts/psfonts/
+ CTAN: fonts/psfonts/urw/antiqua/
+ (unsere Beispielschrift)
+fontinst: CTAN: fonts/utilities/fontinst/
+ http://www.tug.org/applications/fontinst/
+psnfss: CTAN: macros/latex/required/psnfss
+ CTAN: info/installing_psnfss_on_emtex.pdf
+PostScript Type
+1 fonts (Nelson http://www.math.utah.edu/~beebe/fonts/postscript-type-1-fonts.html
+Beebe):
+Walter Schmidt:
+Schriften fr http://home.vr-web.de/was/fonts.html
+TeX:
+Tobias
+Regenbrecht:
+Integration von http://www.regenbrecht.net/psfonts/psfonts_tetex.html
+PostScript-Fonts
+in LaTeX2e:
+
+
+
+9.2.3 Warum sind die Buchstaben in meiner pdf-Datei von schlechter
+Qualitt? (*)
+
+Schriften in pdf-Dateien werden mit schlechter Qualitt dargestellt (und
+evtl. auch gedruckt), wenn sie in der pdf-Datei als Bitmaps enthalten
+sind, also nicht in Form von Vektorfonts. Um das zu verhindern, ist auf
+folgende Punkte zu achten:
+
+* Es drfen im Dokument nur solche Schriften verwendet werden, die im
+ Format Type-1 (PostScript) oder TrueType vorhanden sind. Welche das
+ sind, sollte aus der Dokumentation des TeX-Systems hervorgehen.
+ Schriften, die ausschlielich im Metafont-Format existieren, knnen
+ hingegen in pdf-Dateien nur in Form von Bitmaps benutzt werden, sind
+ also nach Mglichkeit zu vermeiden.
+* Wenn Schriften sowohl im Metafont-Format als auch als Type-1 oder
+ TrueType vorliegen, dann mssen die beteiligten Programme so
+ konfiguriert sein, dass sie nicht die Metafont-Version verwenden. In
+ aktuellen TeX-Distributionen ist das zumindest fr pdfTeX
+ normalerweise der Fall.
+
+Die hufigsten Fehlerquellen sind:
+
+* Es werden die EC- und TC-Fonts benutzt, ohne dass diese im
+ Type-1-Format vorliegen. Abhilfe: EC/TC-Fonts im Type-1-Format
+ beschaffen und installieren (siehe Frage 10.1.7) oder stattdessen die
+ AE-Fonts verwenden (siehe ebenfalls Frage 10.1.8)
+* Wenn die pdf-Datei auf dem Weg ber `dvips' und nachfolgende
+ Umwandlung ins pdf-Format erzeugt wurde, dann hat `dvips' die
+ CM-Schriften im Metafont-Format und damit in einer Bitmap-Version
+ verwendet, obwohl diese auch als Type-1 existieren. Dies ist hufig
+ das voreingestellte Verhalten von `dvips'. Abhilfe: `dvips' mit einer
+ passenden Option aufrufen, so dass alle vorhandenen Type-1-Fonts auch
+ tatschlich verwendet werden. Wie diese Option lautet, hngt von
+ jeweiligen TeX-System ab; beachten Sie dessen Dokumentation! Mit
+ vielen Systemen funktioniert:
+
+
+ dvips -Ppdf -G0
+
+ Beachten Sie dabei, dass CM-Schriften oft fr bestimmte mathematische
+ Symbole bentigt werden, auch wenn die Grundschrift eines Dokuments
+ nicht Computer-Modern ist, z.B. mit Paketen wie `mathptmx'.
+* Die pdf-Datei wurde aus PostScript durch Umwandlung mit dem Programm
+ `Ghostscript' erzeugt, wobei eine ltere Version (< 6.51) zum Einsatz
+ kam. Diese Programmversionen wandeln aber (fast) alle Fonts (auch
+ Vektorfonts!) in Bitmaps um. Sie sind als veraltet anzusehen und
+ sollten durch eine neuere Version (6.51 oder besser) ersetzt werden,
+ die mit Vektorfonts umgehen kann.
+
+
+Ghostscript: CTAN: nonfree/support/ghostscript/
+Fonts in LaTeX: Item,
+www.mamster.net/tex/latex-fontfaq-amster-burton.pdf:
+WWW-Link Fonts in LaTeX: Item, http://www.mamster.net/tex/latex-fontfaq-amster-burton.pdf
+http://www.mamster.net/tex/latex-fontfaq-amster-burton.pdf:
+link) Matthew Amster-Burton: The Sooper-Simple Guide to
+Type 1 Fonts in LaTeX:
+
+
+
+9.2.4 In einer mit `dvips' erzeugten PostScript-Datei fehlen die
+Ligaturen und andere Zeichen.
+
+Dieses Problem kann auftreten, wenn die .ps-Datei unter Verwendung der
+dvips-Option -Ppdf erzeugt wurde. Abhilfe: Ergnzen Sie beim Aufruf von
+dvips die Option -G0:
+
+ dvips -Ppdf -G0 ...
+
+Hintergrund: Die Option -Ppdf manipuliert u.a. den Zeichensatz der
+verwendeten Schriften, um einen potentiellen Fehler des `Acrobat Reader'
+4.0 zu umgehen. Das ist jedoch nur dann berhaupt relevant, wenn die
+.ps-Datei spter in PDF umgewandelt wird, und es funktioniert auerdem
+nur bei Fonts mit 128 Zeichen (z.B. CM); mit anderen Fonts fhrt es
+dazu, dass Zeichen verloren gehen. Mit der zustzlichen Option -G0 wird
+dieses Verhalten abgestellt. Version 4.0 des Acrobat Reader ist
+mittlerweile veraltet und drfte wegen zahlreicher Mngel sowieso kaum
+noch verwendet werden, so dass es wenig Sinn macht, sie weiterhin zu
+bercksichtigen.
+Vorsicht: Es sind auch Implementierungen von `dvips' im Umlauf, mit
+denen das beschriebene Verhalten schon ohne die Option -Ppdf auftritt.
+Die zustzliche Option -G0 behebt das Problem dann ebenfalls.
+
+9.2.5 Warum werden mit der Suchfunktion des Programms `Acrobat Reader'
+keine Worte gefunden, die Umlaute enthalten?
+
+Ein Voraussetzung dafr ist die Verwendung von T1-kodierten Schriften.
+Die oftmals gnstige Lsung mit dem Paket `ae'
+
+ \usepackage{ae}
+
+um auf die `CM'-Schriften in T1-Kodierung zugreifen zu knnen, versagt
+leider hinsichtlich der Umlaute und anderer akzentuierter Buchstaben, da
+diese auch bei Verwendung dieses Paketes intern aus mehreren Lettern
+zusammengesetzt werden. Um das Problem zu umgehen, sollte man Schriften
+in T1-Kodierung verwenden, in denen die Umlaute tatschlich enthalten
+sind, wie etwa die EC-Fonts (Type1-Versionen; Frage 10.1.7) oder die
+PostScript-Basisfonts (siehe Frage 10.2.1).
+
+9.3 TrueType-Schriften
+
+
+9.3.1 Wie kann ich TrueType-Schriften in LaTeX verwenden?
+
+TeX bzw. LaTeX bentigt von jeder Schrift, egal in welchem Format sie
+vorliegt, nur die tfm-Dateien einer Schrift. Erst der Treiber fr das
+Ausgabegert bentigt die Schrift selbst und hier ist es vom Treiber
+abhngig, in welchem Format die Schrift vorliegen darf. Historisch kommt
+fast jeder Treiber mit PK-Dateien bzw. METAFONT-Dateien, aus denen
+PK-Dateien erzeugt werden knnen, zurecht. Ebenso ist die Untersttzung
+von PS-Schriftformaten weit verbreitet.
+Erzeugt man mit pdfTeX PDF-Dateien, so kann pdfTeX TrueType-Schriften
+direkt verwenden und einbetten.
+Sonst gibt es, wie oben erwhnt, prinzipiell drei Mglichkeiten:
+
+* `ttf2pk':
+ Dieses Programm konvertiert beliebige TrueType-Schriften (auch
+ asiatische!) in PK-Dateien. `ttf2pk' bernimmt dabei analog zu
+ `gsftopk' bei PS-Schriften das _Rendering_ fr Anwendungen, die
+ TrueType-Schriften nicht untersttzen. Quellcode, Dokumentation etc.
+ findet man im FreeType-Paket: http://www.freetype.org/projects.html
+ MikTeX und fpTeX enthalten bereits Binaries; die neuesten
+ teTeX-Distributionen ab Version 1.0 haben Untersttzung fr `ttf2pk'
+ in den Skripten (man mu also nur `ttf2pk' kompilieren).
+* TTF => PS-Fonts:
+ Auch hier gibt es mehrere Anstze.
+
+ o `ttf2pfb':
+ Konvertiert TrueType-Fonts (auch asiatische!) in Type-1
+ PostScript-Schriften. Nachteile: Untersttzung von Komposit-TTFs
+ derzeit nur beschrnkt mglich; auerdem geht das Hinting (d.h. die
+ Anpassung an kleine Schriftgren) verloren.
+ http://www.freetype.org/projects.html
+ o `ttf2pt1':
+ `ttf2pt1' kann asiatische Fonts bzw. Fonts mit mehr als 256 Glyphen
+ behandeln, wobei die allgemeine Beschrnkung, da ein
+ Encoding-Vektor nur 256 Elemente haben kann, jedoch davon unabhngig
+ besteht; kann auch Metriken im .afm-Format erzeugen, so da
+ Kerning-Informationen nicht verlorengehen.
+ http://www.netspace.net.au/~mheath/ttf2pt1/
+ o TTF => PS-Fonts im Type-42-Format:
+ Erzeugt eine `Wrapper-Datei' um den TrueType-Font. `Ghostscript' und
+ neuere PS-Interpreter haben ein eingebautes TrueType-Modul, welches
+ das Type-42-Format verstehen kann - allerdings ist der
+ TrueType-Rasterer von lteren Ghostscript-Versionen eher schlecht.
+ (Das Programm kann vermutlich keine asiatische Fonts bzw. Fonts mit
+ mehr als 256 Glyphen behandeln.)
+
+ Prinzipiell geht bei der Konvertierung von TrueType-Schriften nach
+ Type-1 das _Hinting_ verloren. Nhere Informationen hierzu findet man
+ in den Texten http://www.truetype.demon.co.uk/ttandt1.htm und
+ http://www.truetype.demon.co.uk/tthints.htm.
+* `ttf2mf':
+ [nie verwendet; kann vermutlich asiatische Fonts bzw. Fonts mit mehr
+ als 256 Glyphen nicht behandeln.]
+ CTAN: nonfree/support/ttf2mf/
+
+Weitere Informationen findet man unter den folgenden URLs:
+
+FreeType: http://www.freetype.org
+Otfried Cheong: Using TrueType http://www.cs.uu.nl/~otfried/Pdftex/
+fonts in PdfLaTeX:
+
+
+Zur Verwendung oder Integration von `ttf2pk' findet man weiteres unter
+den folgenden URLs:
+
+Damir Rakityansky:
+Using TrueType
+fonts with TeX http://www.radamir.com/tex/ttf-tex.htm
+(LaTeX) and pdfTeX
+(pdfLaTeX):
+Damir Rakityansky
+(dt. .):
+Benutzung von CTAN: info/german/MiKTeX-WinEdt-TrueType-Anleitung/ttf.htm
+TrueType-Schriften
+unter TeX...:
+ttf2tex: CTAN: support/ttf2tex/
+
+
+Zur Konvertierung von TrueType-Schriften in eine PS-Schrift findet man
+mehr unter der folgenden URL:
+
+Harald Harders: Using TrueType fonts with CTAN: info/TrueType/index.html
+teTeX and dvips:
+
+
+
+--- DE-TeX-FAQ Ende Teil 9 ---
diff --git a/help/es-tex-faq/FAQ-CervanTeX.html b/help/es-tex-faq/FAQ-CervanTeX.html
new file mode 100644
index 0000000000..e4f1f0ab5e
--- /dev/null
+++ b/help/es-tex-faq/FAQ-CervanTeX.html
@@ -0,0 +1,178 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <TITLE>FAQ de CervanTeX</TITLE>
+ <LINK HREF="FAQ-CervanTeX-1.html" REL=next>
+
+
+</HEAD>
+<BODY>
+<A HREF="FAQ-CervanTeX-1.html">Pgina siguiente</A>
+Pgina anterior
+ndice general
+<HR>
+<H1>FAQ de CervanTeX</H1>
+
+<H2>CervanTeX</H2> Versi&oacute;n 1.97 de 2006-05-09 (15:12:22)
+
+<HR>
+<EM> Esta es la lista de preguntas y respuestas frecuentes del grupo de usuarios
+ hispanohablantes de TeX/LaTeX CervanTeX. Est&aacute; basada en las
+ preguntas que se repiten con frecuencia en los distintos foros y en
+ algunas contribuciones adicionales interesantes. Aunque todas ellas son
+ preguntas razonables, especialmente para un ne&oacute;fito, resulta un poco
+ <EM>repetitivo</EM> verlas aparecer continuamente en los distintos foros de
+ discusi&oacute;n sobre TeX/LaTeX. Por esta raz&oacute;n se han intentado reunir en
+ esta FAQ. Se ruega echarle un vistazo antes de preguntar en la lista de
+ correo o en el grupo de noticias cosas que ya se han preguntado y
+ respondido m&uacute;ltiples veces y que est&aacute;n en esta FAQ.
+ </EM>
+<HR>
+<P>
+<H2><A NAME="toc1">1.</A> <A HREF="FAQ-CervanTeX-1.html">Qu&eacute; son TeX y sus programas hermanos?</A></H2>
+
+<UL>
+<LI><A NAME="toc1.1">1.1</A> <A HREF="FAQ-CervanTeX-1.html#ss1.1">Qu&eacute; es TeX?</A>
+<LI><A NAME="toc1.2">1.2</A> <A HREF="FAQ-CervanTeX-1.html#ss1.2">Por qu&eacute; debo asegurarme de usar TeX 3.X?</A>
+<LI><A NAME="toc1.3">1.3</A> <A HREF="FAQ-CervanTeX-1.html#ss1.3">Si TeX es tan bueno, por qu&eacute; es gratuito?</A>
+<LI><A NAME="toc1.4">1.4</A> <A HREF="FAQ-CervanTeX-1.html#ss1.4">Qu&eacute; es LaTeX?</A>
+<LI><A NAME="toc1.5">1.5</A> <A HREF="FAQ-CervanTeX-1.html#ss1.5">Qu&eacute; es LaTeX2e?, Por qu&eacute; debo usarlo si me va bien con el otro (LaTeX209)?</A>
+<LI><A NAME="toc1.6">1.6</A> <A HREF="FAQ-CervanTeX-1.html#ss1.6">Qu&eacute; son los paquetes de la AMS (AMS-TeX, AMS-LaTeX)?</A>
+<LI><A NAME="toc1.7">1.7</A> <A HREF="FAQ-CervanTeX-1.html#ss1.7">Qu&eacute; es METAFONT?</A>
+</UL>
+<P>
+<H2><A NAME="toc2">2.</A> <A HREF="FAQ-CervanTeX-2.html">Qu&eacute; ventajas e inconvenientes tiene TeX/LaTeX?</A></H2>
+
+<UL>
+<LI><A NAME="toc2.1">2.1</A> <A HREF="FAQ-CervanTeX-2.html#ss2.1">Ventajas frente a otros procesadores.</A>
+<LI><A NAME="toc2.2">2.2</A> <A HREF="FAQ-CervanTeX-2.html#ss2.2">Inconvenientes o m&aacute;s bien, cu&aacute;les son las cr&iacute;ticas m&aacute;s habituales?</A>
+</UL>
+<P>
+<H2><A NAME="toc3">3.</A> <A HREF="FAQ-CervanTeX-3.html">Qu&eacute; documentaci&oacute;n hay disponible sobre TeX/LaTeX?</A></H2>
+
+<UL>
+<LI><A NAME="toc3.1">3.1</A> <A HREF="FAQ-CervanTeX-3.html#ss3.1">Tutoriales de LaTeX en castellano.</A>
+<LI><A NAME="toc3.2">3.2</A> <A HREF="FAQ-CervanTeX-3.html#ss3.2">Libros en castellano</A>
+<LI><A NAME="toc3.3">3.3</A> <A HREF="FAQ-CervanTeX-3.html#ss3.3">Tutoriales en otros idiomas</A>
+<LI><A NAME="toc3.4">3.4</A> <A HREF="FAQ-CervanTeX-3.html#ss3.4">Libros en otros idiomas</A>
+<LI><A NAME="toc3.5">3.5</A> <A HREF="FAQ-CervanTeX-3.html#ss3.5">Revistas.</A>
+</UL>
+<P>
+<H2><A NAME="toc4">4.</A> <A HREF="FAQ-CervanTeX-4.html">Que elementos intervienen al procesar un documento con LaTeX?</A></H2>
+
+<UL>
+<LI><A NAME="toc4.1">4.1</A> <A HREF="FAQ-CervanTeX-4.html#ss4.1">El documento fuente: C&oacute;mo creo un documento con LaTeX, lo proceso, lo veo y lo imprimo? </A>
+<LI><A NAME="toc4.2">4.2</A> <A HREF="FAQ-CervanTeX-4.html#ss4.2">Qu&eacute; es un archivo DVI?</A>
+<LI><A NAME="toc4.3">4.3</A> <A HREF="FAQ-CervanTeX-4.html#ss4.3">Qu&eacute; es un conversor (driver)?</A>
+<LI><A NAME="toc4.4">4.4</A> <A HREF="FAQ-CervanTeX-4.html#ss4.4">Qu&eacute; son los archivos <CODE>.pk</CODE>?</A>
+<LI><A NAME="toc4.5">4.5</A> <A HREF="FAQ-CervanTeX-4.html#ss4.5">Qu&eacute; son los archivos <CODE>.tfm</CODE>?</A>
+<LI><A NAME="toc4.6">4.6</A> <A HREF="FAQ-CervanTeX-4.html#ss4.6">Qu&eacute; son los tipos (fuentes) CM?</A>
+<LI><A NAME="toc4.7">4.7</A> <A HREF="FAQ-CervanTeX-4.html#ss4.7">Qu&eacute; son los tipos (fuentes) EC/DC?</A>
+<LI><A NAME="toc4.8">4.8</A> <A HREF="FAQ-CervanTeX-4.html#ss4.8">Qu&eacute; son los tipos (fuentes) virtuales?</A>
+<LI><A NAME="toc4.9">4.9</A> <A HREF="FAQ-CervanTeX-4.html#ss4.9">Qu&eacute; son las &oacute;rdenes <CODE>\special</CODE>?</A>
+<LI><A NAME="toc4.10">4.10</A> <A HREF="FAQ-CervanTeX-4.html#ss4.10">Qu&eacute; es el postscript y el postscript encapsulado (archivos <CODE>.eps</CODE>)?</A>
+<LI><A NAME="toc4.11">4.11</A> <A HREF="FAQ-CervanTeX-4.html#ss4.11">Qu&eacute; es el formato <CODE>pdf</CODE>?</A>
+<LI><A NAME="toc4.12">4.12</A> <A HREF="FAQ-CervanTeX-4.html#ss4.12">Qu&eacute; son los paquetes en LaTeX?</A>
+<LI><A NAME="toc4.13">4.13</A> <A HREF="FAQ-CervanTeX-4.html#ss4.13">Qu&eacute; son los archivos <CODE>.dtx</CODE>?</A>
+</UL>
+<P>
+<H2><A NAME="toc5">5.</A> <A HREF="FAQ-CervanTeX-5.html">C&oacute;mo consigo LaTeX y otros programas relacionados?</A></H2>
+
+<UL>
+<LI><A NAME="toc5.1">5.1</A> <A HREF="FAQ-CervanTeX-5.html#ss5.1">Distribuciones TeX/LaTeX</A>
+<LI><A NAME="toc5.2">5.2</A> <A HREF="FAQ-CervanTeX-5.html#ss5.2">Editores de texto que trabajan especialmente bien con LaTeX</A>
+</UL>
+<P>
+<H2><A NAME="toc6">6.</A> <A HREF="FAQ-CervanTeX-6.html">Preguntas espec&iacute;ficas para el LaTeX en castellano</A></H2>
+
+<UL>
+<LI><A NAME="toc6.1">6.1</A> <A HREF="FAQ-CervanTeX-6.html#ss6.1">C&oacute;mo puedo usar TeX en castellano? o Qu&eacute; es lo m&iacute;nimo que hay que saber para escribir en castellano con TeX/LaTeX?</A>
+<LI><A NAME="toc6.2">6.2</A> <A HREF="FAQ-CervanTeX-6.html#ss6.2">Con LaTeX, c&oacute;mo puedo escribir los acentos y dem&aacute;s caracteres extendidos?</A>
+<LI><A NAME="toc6.3">6.3</A> <A HREF="FAQ-CervanTeX-6.html#ss6.3">Puedo compartir mis archivos LaTeX en los que he escrito los acentos directamente?</A>
+<LI><A NAME="toc6.4">6.4</A> <A HREF="FAQ-CervanTeX-6.html#ss6.4">Por qu&eacute; cuando se selecciona texto en Adobe Reader o xpdf, desde un documento PDF generado con LaTeX, las letras acentuadas y e&ntilde;es no se copian bien?</A>
+<LI><A NAME="toc6.5">6.5</A> <A HREF="FAQ-CervanTeX-6.html#ss6.5">C&oacute;mo cambiar los literales que produce LaTeX?</A>
+<LI><A NAME="toc6.6">6.6</A> <A HREF="FAQ-CervanTeX-6.html#ss6.6">C&oacute;mo hacer que LaTeX parta correctamente las palabras en castellano?</A>
+<LI><A NAME="toc6.7">6.7</A> <A HREF="FAQ-CervanTeX-6.html#ss6.7">Acerca de <CODE>spanish.sty</CODE></A>
+<LI><A NAME="toc6.8">6.8</A> <A HREF="FAQ-CervanTeX-6.html#ss6.8">C&oacute;mo puedo indicar la abreviatura de los ordinales?</A>
+<LI><A NAME="toc6.9">6.9</A> <A HREF="FAQ-CervanTeX-6.html#ss6.9">C&oacute;mo forzar sangr&iacute;a despu&eacute;s de las cabeceras?</A>
+<LI><A NAME="toc6.10">6.10</A> <A HREF="FAQ-CervanTeX-6.html#ss6.10">C&oacute;mo puedo escribir las funciones matem&aacute;ticas en espa&ntilde;ol?</A>
+<LI><A NAME="toc6.11">6.11</A> <A HREF="FAQ-CervanTeX-6.html#ss6.11">Qu&eacute; verificadores ortogr&aacute;ficos puedo utilizar para espa&ntilde;ol?</A>
+<LI><A NAME="toc6.12">6.12</A> <A HREF="FAQ-CervanTeX-6.html#ss6.12">C&oacute;mo utilizo BibTeX en castellano?</A>
+<LI><A NAME="toc6.13">6.13</A> <A HREF="FAQ-CervanTeX-6.html#ss6.13">C&oacute;mo genero un &iacute;ndice alfab&eacute;tico con la ordenaci&oacute;n correcta en castellano?</A>
+</UL>
+<P>
+<H2><A NAME="toc7">7.</A> <A HREF="FAQ-CervanTeX-7.html">Que es...?</A></H2>
+
+<UL>
+<LI><A NAME="toc7.1">7.1</A> <A HREF="FAQ-CervanTeX-7.html#ss7.1">Qu&eacute; es el CTAN (<EM>Comprehensive TeX Archive Network</EM>).</A>
+<LI><A NAME="toc7.2">7.2</A> <A HREF="FAQ-CervanTeX-7.html#ss7.2">Qu&eacute; es el esquema de codificaci&oacute;n de Cork?</A>
+<LI><A NAME="toc7.3">7.3</A> <A HREF="FAQ-CervanTeX-7.html#ss7.3">Qu&eacute; es babel?</A>
+<LI><A NAME="toc7.4">7.4</A> <A HREF="FAQ-CervanTeX-7.html#ss7.4">Qu&eacute; son eTeX, eLaTeX y <EM>omega</EM>?</A>
+<LI><A NAME="toc7.5">7.5</A> <A HREF="FAQ-CervanTeX-7.html#ss7.5">Qu&eacute; es RevTeX?</A>
+<LI><A NAME="toc7.6">7.6</A> <A HREF="FAQ-CervanTeX-7.html#ss7.6">Qu&eacute; es una <CODE>box</CODE> y cu&aacute;ndo conviene utilizarlas?</A>
+</UL>
+<P>
+<H2><A NAME="toc8">8.</A> <A HREF="FAQ-CervanTeX-8.html">C&oacute;mo hago ...?</A></H2>
+
+<UL>
+<LI><A NAME="toc8.1">8.1</A> <A HREF="FAQ-CervanTeX-8.html#ss8.1">C&oacute;mo y d&oacute;nde instalo nuevos paquetes o archivos de estilo?</A>
+<LI><A NAME="toc8.2">8.2</A> <A HREF="FAQ-CervanTeX-8.html#ss8.2">C&oacute;mo personalizo el aspecto del documento?</A>
+<LI><A NAME="toc8.3">8.3</A> <A HREF="FAQ-CervanTeX-8.html#ss8.3">Listas al gusto de cada cual.</A>
+<LI><A NAME="toc8.4">8.4</A> <A HREF="FAQ-CervanTeX-8.html#ss8.4">Referencias cruzadas, &iacute;ndices, bibliograf&iacute;as y tablas de materias.</A>
+<LI><A NAME="toc8.5">8.5</A> <A HREF="FAQ-CervanTeX-8.html#ss8.5">C&oacute;mo introduzco dibujos, diagramas e im&aacute;genes en LaTeX?</A>
+<LI><A NAME="toc8.6">8.6</A> <A HREF="FAQ-CervanTeX-8.html#ss8.6">Figuras, tablas y elementos flotantes</A>
+<LI><A NAME="toc8.7">8.7</A> <A HREF="FAQ-CervanTeX-8.html#ss8.7">C&oacute;mo giro un elemento en un documento LaTeX?</A>
+<LI><A NAME="toc8.8">8.8</A> <A HREF="FAQ-CervanTeX-8.html#ss8.8">C&oacute;mo escribo algunos s&iacute;mbolos?</A>
+<LI><A NAME="toc8.9">8.9</A> <A HREF="FAQ-CervanTeX-8.html#ss8.9">C&oacute;mo convierto mis documentos a LaTeX y desde LaTeX?</A>
+<LI><A NAME="toc8.10">8.10</A> <A HREF="FAQ-CervanTeX-8.html#ss8.10">C&oacute;mo rehago los formatos de TeX y LaTeX?</A>
+<LI><A NAME="toc8.11">8.11</A> <A HREF="FAQ-CervanTeX-8.html#ss8.11">C&oacute;mo llamo a un editor desde TeX/LaTeX?</A>
+<LI><A NAME="toc8.12">8.12</A> <A HREF="FAQ-CervanTeX-8.html#ss8.12">Algunas cosillas matem&aacute;ticas.</A>
+<LI><A NAME="toc8.13">8.13</A> <A HREF="FAQ-CervanTeX-8.html#ss8.13">C&oacute;mo hago cuadernillos, tr&iacute;pticos y documentos con formatos especiales?</A>
+<LI><A NAME="toc8.14">8.14</A> <A HREF="FAQ-CervanTeX-8.html#ss8.14">C&oacute;mo puedo preparar una exposici&oacute;n utilizando LaTeX?</A>
+<LI><A NAME="toc8.15">8.15</A> <A HREF="FAQ-CervanTeX-8.html#ss8.15">Algunas cosas que a veces se piden para mandar un documento a la imprenta.</A>
+<LI><A NAME="toc8.16">8.16</A> <A HREF="FAQ-CervanTeX-8.html#ss8.16">Algunas cuestiones adicionales, o menos FAQ</A>
+<LI><A NAME="toc8.17">8.17</A> <A HREF="FAQ-CervanTeX-8.html#ss8.17">He encontrado un error en LaTeX C&oacute;mo lo notifico?</A>
+</UL>
+<P>
+<H2><A NAME="toc9">9.</A> <A HREF="FAQ-CervanTeX-9.html">Por qu&eacute; no consigo ...?</A></H2>
+
+<UL>
+<LI><A NAME="toc9.1">9.1</A> <A HREF="FAQ-CervanTeX-9.html#ss9.1">Por qu&eacute; no salen las im&aacute;genes en mi documento?</A>
+<LI><A NAME="toc9.2">9.2</A> <A HREF="FAQ-CervanTeX-9.html#ss9.2">Por qu&eacute; no salen los caracteres acentuados si yo los escribo bien?</A>
+<LI><A NAME="toc9.3">9.3</A> <A HREF="FAQ-CervanTeX-9.html#ss9.3">Por qu&eacute; no encuentro el archivo babelbst.tex cuando uso <EM>custom-bib</EM>?</A>
+<LI><A NAME="toc9.4">9.4</A> <A HREF="FAQ-CervanTeX-9.html#ss9.4">Por qu&eacute; a veces no me da el mismo resultado o incluso errores al procesar un documento en dos sistemas distintos?</A>
+</UL>
+<P>
+<H2><A NAME="toc10">10.</A> <A HREF="FAQ-CervanTeX-10.html">Preguntas que se van quedando obsoletas</A></H2>
+
+<UL>
+<LI><A NAME="toc10.1">10.1</A> <A HREF="FAQ-CervanTeX-10.html#ss10.1">Qu&eacute; es <CODE>FTC</CODE>?</A>
+<LI><A NAME="toc10.2">10.2</A> <A HREF="FAQ-CervanTeX-10.html#ss10.2">Qu&eacute; es ML-TeX?</A>
+</UL>
+<P>
+<H2><A NAME="toc11">11.</A> <A HREF="FAQ-CervanTeX-11.html">Informaci&oacute;n sobre LaTeX en castellano</A></H2>
+
+<UL>
+<LI><A NAME="toc11.1">11.1</A> <A HREF="FAQ-CervanTeX-11.html#ss11.1">El Grupo de Usuarios de TeX Hispanohablantes (CervanTeX)</A>
+<LI><A NAME="toc11.2">11.2</A> <A HREF="FAQ-CervanTeX-11.html#ss11.2">La lista <CODE>es-tex</CODE> </A>
+<LI><A NAME="toc11.3">11.3</A> <A HREF="FAQ-CervanTeX-11.html#ss11.3">Las listas <CODE>spanish-tex</CODE> y <CODE>sptex</CODE></A>
+<LI><A NAME="toc11.4">11.4</A> <A HREF="FAQ-CervanTeX-11.html#ss11.4">El grupo de noticias <CODE>es.comp.lenguajes.tex</CODE></A>
+<LI><A NAME="toc11.5">11.5</A> <A HREF="FAQ-CervanTeX-11.html#ss11.5">El grupo de noticias <CODE>es.eunet.spanish-tex</CODE></A>
+</UL>
+<P>
+<H2><A NAME="toc12">12.</A> <A HREF="FAQ-CervanTeX-12.html">Meta-preguntas (preguntas sobre esta FAQ):</A></H2>
+
+<UL>
+<LI><A NAME="toc12.1">12.1</A> <A HREF="FAQ-CervanTeX-12.html#ss12.1">Cu&aacute;l es la historia de esta FAQ?</A>
+<LI><A NAME="toc12.2">12.2</A> <A HREF="FAQ-CervanTeX-12.html#ss12.2">Qui&eacute;n coordina actualmente la FAQ?</A>
+<LI><A NAME="toc12.3">12.3</A> <A HREF="FAQ-CervanTeX-12.html#ss12.3">Agradecimientos</A>
+<LI><A NAME="toc12.4">12.4</A> <A HREF="FAQ-CervanTeX-12.html#ss12.4">D&oacute;nde encuentro la versi&oacute;n m&aacute;s reciente de esta FAQ?</A>
+<LI><A NAME="toc12.5">12.5</A> <A HREF="FAQ-CervanTeX-12.html#ss12.5">D&oacute;nde puedo encontrar otras FAQ, aunque sea en otros idiomas?</A>
+</UL>
+<HR>
+<A HREF="FAQ-CervanTeX-1.html">Pgina siguiente</A>
+Pgina anterior
+ndice general
+</BODY>
+</HTML>
diff --git a/help/es-tex-faq/FAQ-CervanTeX.latin1 b/help/es-tex-faq/FAQ-CervanTeX.latin1
new file mode 100644
index 0000000000..95ecd25106
--- /dev/null
+++ b/help/es-tex-faq/FAQ-CervanTeX.latin1
@@ -0,0 +1,5447 @@
+ FAQ de CervanTeX
+ CervanTeX
+ Versin 1.97 de 2006-05-09 (15:12:22)
+
+ Esta es la lista de preguntas y respuestas frecuentes del grupo de
+ usuarios hispanohablantes de TeX/LaTeX CervanTeX. Est basada en las
+ preguntas que se repiten con frecuencia en los distintos foros y en
+ algunas contribuciones adicionales interesantes. Aunque todas ellas
+ son preguntas razonables, especialmente para un nefito, resulta un
+ poco repetitivo verlas aparecer continuamente en los distintos foros
+ de discusin sobre TeX/LaTeX. Por esta razn se han intentado reunir
+ en esta FAQ. Se ruega echarle un vistazo antes de preguntar en la
+ lista de correo o en el grupo de noticias cosas que ya se han pregun-
+ tado y respondido mltiples veces y que estn en esta FAQ.
+
+ ______________________________________________________________________
+
+ ndice general
+
+
+
+ 1. Qu son TeX y sus programas hermanos?
+ 1.1 Qu es TeX?
+ 1.2 Por qu debo asegurarme de usar TeX 3.X?
+ 1.3 Si TeX es tan bueno, por qu es gratuito?
+ 1.4 Qu es LaTeX?
+ 1.5 Qu es LaTeX2e?, Por qu debo usarlo si me va bien con el otro (LaTeX209)?
+ 1.6 Qu son los paquetes de la AMS (AMS-TeX, AMS-LaTeX)?
+ 1.7 Qu es METAFONT?
+
+ 2. Qu ventajas e inconvenientes tiene TeX/LaTeX?
+ 2.1 Ventajas frente a otros procesadores.
+ 2.2 Inconvenientes o ms bien, cules son las crticas ms habituales?
+
+ 3. Qu documentacin hay disponible sobre TeX/LaTeX?
+ 3.1 Tutoriales de LaTeX en castellano.
+ 3.2 Libros en castellano
+ 3.3 Tutoriales en otros idiomas
+ 3.4 Libros en otros idiomas
+ 3.5 Revistas.
+
+ 4. Que elementos intervienen al procesar un documento con LaTeX?
+ 4.1 El documento fuente: Cmo creo un documento con LaTeX, lo proceso, lo veo y lo imprimo?
+ 4.2 Qu es un archivo DVI?
+ 4.3 Qu es un conversor (driver)?
+ 4.4 Qu son los archivos .pk?
+ 4.5 Qu son los archivos .tfm?
+ 4.6 Qu son los tipos (fuentes) CM?
+ 4.7 Qu son los tipos (fuentes) EC/DC?
+ 4.8 Qu son los tipos (fuentes) virtuales?
+ 4.9 Qu son las rdenes \special?
+ 4.10 Qu es el postscript y el postscript encapsulado (archivos .eps)?
+ 4.11 Qu es el formato pdf?
+ 4.12 Qu son los paquetes en LaTeX?
+ 4.13 Qu son los archivos .dtx?
+
+ 5. Cmo consigo LaTeX y otros programas relacionados?
+ 5.1 Distribuciones TeX/LaTeX
+ 5.1.1 Distribuciones libres o shareware
+ 5.1.2 Distribuciones comerciales
+ 5.2 Editores de texto que trabajan especialmente bien con LaTeX
+
+ 6. Preguntas especficas para el LaTeX en castellano
+ 6.1 Cmo puedo usar TeX en castellano? o Qu es lo mnimo que hay que saber para escribir en castellano con TeX/LaTeX?
+ 6.2 Con LaTeX, cmo puedo escribir los acentos y dems caracteres extendidos?
+ 6.2.1 Mediante rdenes LaTeX
+ 6.2.2 Directamente mediante el paquete inputenc
+ 6.2.3 Cmo introducir acentos en modo matemtico?
+ 6.3 Puedo compartir mis archivos LaTeX en los que he escrito los acentos directamente?
+ 6.4 Por qu cuando se selecciona texto en Adobe Reader o xpdf, desde un documento PDF generado con LaTeX, las letras acentuadas y ees no se copian bien?
+ 6.5 Cmo cambiar los literales que produce LaTeX?
+ 6.6 Cmo hacer que LaTeX parta correctamente las palabras en castellano?
+ 6.6.1 Qu configuraciones (o patterns) existen para la particin de palabras?
+ 6.6.2 Cmo activo el patrn de particin de palabras para el castellano?
+ 6.6.3 A pesar de que he activado los patrones de particin de palabras del castellano, hay una palabra que se me resiste
+ 6.6.4 Mi TeX no parte las palabras que tienen acentos. Por qu?
+ 6.7 Acerca de spanish.sty
+ 6.7.1 Dnde se puede obtener la documentacin de spanish en castellano?
+ 6.7.2 Cmo cambio los nombres de las secciones de bibliografa, ndice, etc... que pone spanish.sty?
+ 6.7.3 Por qu spanish.sty pone los meses en minscula?
+ 6.7.4 Por qu el spanish de babel reemplaza el punto decimal por una coma?
+ 6.7.5 Por qu spanish.sty pone los nmeros romanos siempre en mayscula?
+ 6.7.6 Por qu spanish.sty acenta la I de ndice?
+ 6.7.7 Por qu spanish para babel dice cuadro en lugar de tabla?
+ 6.7.8 Cmo consigo que babel y spanish.sty no utilicen los atajos de teclado NUNCA?
+ 6.8 Cmo puedo indicar la abreviatura de los ordinales?
+ 6.9 Cmo forzar sangra despus de las cabeceras?
+ 6.10 Cmo puedo escribir las funciones matemticas en espaol?
+ 6.11 Qu verificadores ortogrficos puedo utilizar para espaol?
+ 6.12 Cmo utilizo BibTeX en castellano?
+ 6.12.1 Utilizar estilos adaptables (los abstyles)
+ 6.12.2 Utilizar el paquete custom-bib
+ 6.13 Cmo genero un ndice alfabtico con la ordenacin correcta en castellano?
+
+ 7. Que es...?
+ 7.1 Qu es el CTAN (Comprehensive TeX Archive Network).
+ 7.2 Qu es el esquema de codificacin de Cork?
+ 7.3 Qu es babel?
+ 7.4 Qu son eTeX, eLaTeX y omega?
+ 7.5 Qu es RevTeX?
+ 7.6 Qu es una box y cundo conviene utilizarlas?
+
+ 8. Cmo hago ...?
+ 8.1 Cmo y dnde instalo nuevos paquetes o archivos de estilo?
+ 8.1.1 Dnde buscar un paquete nuevo y qu traer
+ 8.1.2 Qu es cada uno de los archivos que traigo?
+ 8.1.3 Extrayendo archivos de estilo de los .dtx y .ins
+ 8.1.4 Dnde colocar nuevos archivos de estilo?
+ 8.1.5 Activando ramas locales y personales del rbol de directorios LaTeX global
+ 8.1.6 Rehaciendo la base de datos de archivos instalados
+ 8.1.7 Cmo verifico los directorios en los que TeX busca archivos de estilo?
+ 8.2 Cmo personalizo el aspecto del documento?
+ 8.2.1 Cmo cambio la fuente de un documento o instalo nuevas?
+ 8.2.2 Puedo utilizar una fuente TrueType como Arial en LaTeX?
+ 8.2.3 Incluyendo subdocumentos TeX/LaTeX en el documento
+ 8.2.4 Cmo evito que salga la palabra captulo en las cabeceras de captulo?
+ 8.2.5 Cmo cambio la cabecera de captulo por otra ms a mi gusto?
+ 8.2.6 Quiero una seccin no numerada, pero que aparezca en la tabla de materias.
+ 8.2.7 No me funciona \subsubsubsection.
+ 8.2.8 Cmo quito los encabezados que LaTeX pone automticamente en las pginas blancas?
+ 8.2.9 Cmo quito los encabezados, pies o la numeracin de las pginas?
+ 8.2.10 Cmo pongo encabezados o pies de pgina a mi gusto?
+ 8.2.11 Cmo hago que LaTeX y TeX no partan nunca las palabras?
+ 8.2.12 Cmo ajusto los mrgenes de un documento LaTeX?
+ 8.2.13 Cmo obtengo un documento apaisado?
+ 8.2.14 Cmo ajusto el espaciado en el documento LaTeX?
+ 8.3 Listas al gusto de cada cual.
+ 8.3.1 Cmo ajusto el espaciado en una lista?
+ 8.3.2 Cmo cambio el tipo de numeracin en las listas numeradas?
+ 8.3.3 Quiero mostrar un smbolo distinto en las listas itemize
+ 8.3.4 Puedo ajustar la separacin entre texto y listas?
+ 8.3.5 Cmo interrumpir una lista numerada con un comentario y continuar despus con la numeracin correcta?
+ 8.3.6 Puedo hacer listas en paralelo?
+ 8.4 Referencias cruzadas, ndices, bibliografas y tablas de materias.
+ 8.4.1 Hay alguna herramienta de gestin de bases de datos bibliogrficas en BibTeX?
+ 8.4.2 Cmo introduzco la bibliografa o el ndice en la tabla de materias?
+ 8.4.3 Cmo pongo el ndice con su contenido al principio de cada captulo?
+ 8.4.4 Cmo aado bibliografa al final de cada captulo en LaTeX?
+ 8.4.5 Cmo divido la bibliografa por temas en LaTeX?
+ 8.4.6 Cmo cito una pgina de una referencia bibliogrfica?
+ 8.4.7 Cmo cito una url con BibTeX?
+ 8.4.8 Cmo colapso una serie de citas consecutivas?
+ 8.4.9 Cmo hago una referencia cruzada a un documento externo?
+ 8.4.10 Afinando el aspecto de la tabla de materias o listas de figuras y tablas.
+ 8.5 Cmo introduzco dibujos, diagramas e imgenes en LaTeX?
+ 8.5.1 Dibujando con TeX
+ 8.5.2 Introduciendo figuras postscript encapsulado en LaTeX
+ 8.5.3 Introduciendo imgenes en mapa de bits en LaTeX.
+ 8.5.4 Inclusin de una imagen desde un PDF con mltiples pginas.
+ 8.5.5 Introduciendo cdigo y figuras postscript en pdfTeX
+ 8.5.6 Cmo coloco un fragmento TeX en una figura?
+ 8.6 Figuras, tablas y elementos flotantes
+ 8.6.1 Cmo puedo poner una figura rodeada de texto?
+ 8.6.2 Cmo puedo poner una figura a dos columnas?
+ 8.6.3 Cmo consigo un mayor control de la posicin de figuras y dems elementos flotantes?
+ 8.6.4 Puedo poner una figura en una tabla?
+ 8.6.5 Cmo colocar dos figuras o tablas juntas de distintas formas?,
+ 8.6.6 Puedo poner un pie en tablas y figuras que no flotan?,
+ 8.6.7 Cmo hago para incluir elementos flotantes grandes o numerosos sin que den errores o se vayan al final?
+ 8.7 Cmo giro un elemento en un documento LaTeX?
+ 8.8 Cmo escribo algunos smbolos?
+ 8.9 Cmo convierto mis documentos a LaTeX y desde LaTeX?
+ 8.9.1 Cmo obtengo un documento PDF a partir de mi documento TeX?
+ 8.9.2 Cmo obtengo una versin texto a partir de un documento PDF?
+ 8.9.3 Cmo obtengo un documento html a partir de mi documento TeX?
+ 8.9.4 Convirtiendo a LaTeX desde otros formatos
+ 8.10 Cmo rehago los formatos de TeX y LaTeX?
+ 8.11 Cmo llamo a un editor desde TeX/LaTeX?
+ 8.12 Algunas cosillas matemticas.
+ 8.12.1 Cmo escribo un nmero con periodo utilizando LaTeX?
+ 8.12.2 Cmo puedo hacer para que la etiqueta de una ecuacin p.ej. (3.5) contenga adems el nmero de la seccin actual p.ej. (3.1.5)
+ 8.12.3 Cmo hay que hacer para lograr la N, R de doble trazo con que se representan los nmeros naturales, reales, etc...
+ 8.12.4 Puedo forzar que una frmula tenga el mismo nmero que otra?
+ 8.12.5 Puedo escribir smbolos matemticos en negrita?
+ 8.12.6 Puedo rotar una ecuacin?
+ 8.12.7 Algunas preguntas matemticas de breve respuesta.
+ 8.13 Cmo hago cuadernillos, trpticos y documentos con formatos especiales?
+ 8.13.1 Cmo hago cuadernillos con TeX o LaTeX?
+ 8.13.2 Cmo hago trpticos con LaTeX?
+ 8.13.3 Puedo preparar un pster con TeX/LaTeX?
+ 8.13.4 Puedo hacer libretos y cartulas de CD con LaTeX?
+ 8.14 Cmo puedo preparar una exposicin utilizando LaTeX?
+ 8.14.1 Haciendo transparencias con LaTeX
+ 8.14.2 Haciendo una presentacin con LaTeX
+ 8.14.2.1 beamer
+ 8.14.3 Ms informacin sobre presentaciones
+ 8.15 Algunas cosas que a veces se piden para mandar un documento a la imprenta.
+ 8.15.1 Sacando la imagen especular de un archivo (es decir, con todo al revs).
+ 8.15.2 Sacando el archivo en negativo (es decir, blanco sobre negro).
+ 8.15.3 Marcas de corte.
+ 8.16 Algunas cuestiones adicionales, o menos FAQ
+ 8.17 He encontrado un error en LaTeX Cmo lo notifico?
+
+ 9. Por qu no consigo ...?
+ 9.1 Por qu no salen las imgenes en mi documento?
+ 9.2 Por qu no salen los caracteres acentuados si yo los escribo bien?
+ 9.3 Por qu no encuentro el archivo babelbst.tex cuando uso custom-bib?
+ 9.4 Por qu a veces no me da el mismo resultado o incluso errores al procesar un documento en dos sistemas distintos?
+
+ 10. Preguntas que se van quedando obsoletas
+ 10.1 Qu es FTC?
+ 10.2 Qu es ML-TeX?
+
+ 11. Informacin sobre LaTeX en castellano
+ 11.1 El Grupo de Usuarios de TeX Hispanohablantes (CervanTeX)
+ 11.1.1 Qu es CervanTeX?
+ 11.1.2 Cmo puedo entrar en contacto con el grupo de usuarios?
+ 11.2 La lista es-tex
+ 11.2.1 Cmo funciona la lista es-tex?
+ 11.2.2 Cuando contesto a alguien de la lista, quin recibe la respuesta? El que mand el mensaje o la lista entera?
+ 11.2.3 Se archiva en algn sitio la lista es-tex?
+ 11.2.4 Recibo correo de muchas listas. Cmo puedo filtrar lo que venga de la lista es-tex?
+ 11.2.5 Cmo es que hay tanta gente de fuera de Espaa en la lista?
+ 11.3 Las listas spanish-tex y sptex
+ 11.3.1 Se archiva en algn sitio la lista spanish-tex?
+ 11.3.2 Se archiva en algn sitio la lista sptex?
+ 11.4 El grupo de noticias es.comp.lenguajes.tex
+ 11.5 El grupo de noticias es.eunet.spanish-tex
+
+ 12. Meta-preguntas (preguntas sobre esta FAQ):
+ 12.1 Cul es la historia de esta FAQ?
+ 12.2 Quin coordina actualmente la FAQ?
+ 12.3 Agradecimientos
+ 12.4 Dnde encuentro la versin ms reciente de esta FAQ?
+ 12.5 Dnde puedo encontrar otras FAQ, aunque sea en otros idiomas?
+
+
+ ______________________________________________________________________
+
+ 1. Qu son TeX y sus programas hermanos?
+
+ 1.1. Qu es TeX?
+
+ TeX es un sistema de composicin de textos de alta calidad creado por
+ Donald E. Knuth, dirigido en particular a aqullos textos que
+ contienen una gran cantidad de expresiones matemticas. No debe
+ pensarse en TeX como un procesador de palabras del tipo WYSIWYG, un
+ archivo tex es un archivo ASCII donde est el texto que deseamos
+ imprimir junto con determinadas instrucciones sobre como debe ser
+ tratado, que debe ser procesado por un compilador (el programa TeX).
+ ste devuelve un archivo que es independiente de la plataforma y que
+ es el que finalmente se transformar al lenguaje de impresora y se
+ imprimir.
+
+
+ Para escribir TeX Knuth desarroll un sistema de programacin
+ ilustrada denominado WEB. Las fuentes WEB de TeX estn disponibles
+ gratuitamente, lo mismo que herramientas para convertir el original en
+ WEB en un programa que pueda compilarse y un texto que pueda
+ imprimirse. El sistema WEB proporciona herramientas para compilar TeX
+ en distintos sistemas operativos.
+
+ TeX en s es un procesador de macros, con una alta capacidad de
+ programacin. Utilizar TeX puro reviste una cierta dificultad, por lo
+ que Knuth suministr una serie de macros para TeX a las que se
+ denomin plain TeX. Estas macros son el conjunto mnimo de macros que
+ se pueden utilizar de forma eficaz con TeX e incluyen algunos ejemplos
+ de uso de rdenes TeX de alto nivel. Cuando alguien afirma programar
+ en TeX normalmente se refiere a que lo hace en plain TeX
+
+
+ 1.2. Por qu debo asegurarme de usar TeX 3.X?
+
+ Bueno, hace unos aos (en el ***), diversas personas (y la existencia
+ de ML-TeX :-) convencieron a Knuth de que el soporte que TeX
+ proporcionaba a otros idiomas era insuficiente. As que lo modific de
+ la siguiente manera:
+
+ Soporte total a los 8 bits. TeX puede ahora leer los 256
+ diferentes cdigos. Los nuevos caracteres son cdigos utilizables
+ como cualquier otro. Antes haba algo, pero no bastante. Ahora
+ podemos hacer que ^^e1 sea la .
+
+ TeX soporta ahora 256 tablas de particin simultneamente. Puedes
+ escribir:
+
+ ... there is a difference between especially and {\lan-
+ guage\spanish especialmente} in that...
+
+
+ y TeX compondr el prrafo con las reglas de ingls, menos especial-
+ mente que lo har con las del castellano.
+
+
+
+ Dos nuevas macros \lefthyphenmin y \righthyphenmin que controlan el
+ tamao del trozo mnimo que se puede dejar al partir palabras.
+ Previamente estaban fijos a 2 y 3, respectivamente.
+
+ Pero lo fundamental es que TeX 2.X no existe ya. Hay que cambiar
+ tarde o temprano. No hay parches ni arreglos para TeX 2.X.
+
+ Por cierto, la versin actual es la 3.14159, y la versin actual de
+ METAFONT es la 2.718. La ltima versin de TeX ser la versin pi
+ (como ltima voluntad de Donald Knuth), y ya no habr ms cambios.
+ Y el ltimo METAFONT ser versin e.
+
+
+ 1.3. Si TeX es tan bueno, por qu es gratuito?
+
+ Porque Knuth lo decidi as, y no parece molestarle que otros ganen
+ dinero vendiendo productos y servicios basados en TeX. De hecho,
+ aunque algunas herramientas que se usan junto a TeX se ofrecen bajo la
+ GNU General Public License (Copyleft), TeX en s ni siquiera tiene esa
+ restriccin. La nica restriccin impuesta por Knuth es que debe dar
+ el mismo resultado en todas las implementaciones, para garantizar la
+ absoluta portabilidad de los documentos escritos con TeX.
+
+ Algunas empresas ofrecen implementaciones comerciales de TeX/LaTeX con
+ elementos propios (vase la seccin ``Implementaciones comerciales'')
+
+
+ 1.4. Qu es LaTeX?
+
+ LaTeX es un paquete de macros para TeX, originalmente escrito por
+ Leslie Lamport para proporcionar un sistema de procesamiento de
+ documentos ms simple de uso que TeX, pero con toda su potencia. LaTeX
+ proporciona una serie de rdenes para describir la estructura del
+ documento, de forma que el usuario final no deba pensar mucho en la
+ presentacin. Mediante distintas clases de documentos y paquetes
+ adicionales, el mismo documento puede producirse con muchos diferentes
+ aspectos.
+
+
+ 1.5. Qu es LaTeX2e?, Por qu debo usarlo si me va bien con el otro
+ (LaTeX209)?
+
+ LaTeX2e es la nueva versin estndar de LaTeX, preparada y mantenida
+ por el equipo del proyecto LaTeX3. Es la versin actual de LaTeX y
+ est disponible desde cualquier punto CTAN, en
+
+
+
+ CTAN:macros/latex
+
+
+
+ Desde que es oficial, LaTeX = LaTeX2e y el otro ahora se llama LaTeX
+ 2.09 y est obsoleto.
+
+ LaTeX2e es compatible hacia atrs con LaTeX209, pero incluye toda una
+ serie de caractersticas nuevas.
+
+ Hay una razn de peso para no usar LaTeX 2.09: Solamente LaTeX est
+ mantenido, lo cual quiere decir (entre otras cosas) que si encontramos
+ un error hay gente a quien decrselo y puede que lo arreglen, mientras
+ que si tenemos problemas con LaTeX 2.09 nadie nos har caso, porque
+ LaTeX 2.09 ya no va a cambiar jams.
+
+
+ 1.6. Qu son los paquetes de la AMS (AMS-TeX, AMS-LaTeX)?
+
+ AMS-TeX es un paquete de macros para TeX. Escrito originalmente por
+ Michael Spivak para la Sociedad Americana de Matemticas (AMS) entre
+ 1983 y 1985. Est basado en plain TeX, pero proporciona ms medios
+ para producir frmulas matemticas de aspecto profesional con menor
+ esfuerzo por parte de los autores, con un gran cuidado en aspectos
+ como el tamao y la posicin de las frmulas. Entre los aspectos
+ tratados se encuentran las ecuaciones de ms de una lnea, la
+ numeracin de ecuaciones, los puntos de elipsis, las matrices, los
+ acentos dobles, sub y superndices en varios niveles, as como otras
+ cosas.
+
+ Segn fue aumentando la popularidad de LaTeX la AMS desarroll AMS-
+ LaTeX, que consiste en una coleccin de clases y paquetes para LaTeX
+ que ofrece a los autores la funcionalidad de AMS-TeX.
+
+
+ 1.7. Qu es METAFONT?
+
+ Donald Knuth escribi METAFONT al mismo tiempo que TeX. Mientras TeX
+ define la colocacin de los elementos en una pgina, METAFONT define
+ cmo son estos elementos, sus tamaos y cmo se crean.
+
+ El lenguaje utilizado por METAFONT para definir tipos permite
+ describir distintas cosas, la geometra del grafo, las propiedades del
+ elemento de impresin, informacin adicional que permita distinguir
+ entre distintos tamaos del mismo tipo, o diferencias entre dos tipos
+ que pertenecen a la misma o distinta familia.
+
+ Aunque Knuth y otros han diseado un buen nmero de tipos utilizando
+ METAFONT, el diseo de tipos en general y en particular con METAFONT
+ es un rea muy especializada que nunca deber abordar el usuario
+ normal. Simplemente METAFONT deber estar instalado para cuando TeX
+ quiera generar copias de nuevos tipos.
+
+
+ 2. Qu ventajas e inconvenientes tiene TeX/LaTeX?
+
+ 2.1. Ventajas frente a otros procesadores.
+
+ Adems de las ventajas que aqu se describen, en la pgina
+ http://www.cudenver.edu/~hgreenbe/courses/texinfo/wordvslatex.html se
+ recopilan (en ingls) buen numero de mensajes con una informacin
+ detallada de las razones que han llevado a toda una serie de personas
+ a utilizar LaTeX
+
+ Funciona y es estable y multiplataforma.
+ Tan simple como eso, LaTeX no se cuelga, el formato de los
+ archivos es mucho ms estable que en otros procesadores y
+ cualquier cambio es primero profundamente meditado y despus
+ profusamente documentado, existen implementaciones para
+ distintas plataformas y en todas el resultado es exactamente el
+ mismo (si se tienen los mismos estilos y tipos, claro).
+
+
+ Alta calidad en la edicin de ecuaciones.
+ Esta es siempre la razn ltima por la que un usuario cientfico
+ se inclina hacia LaTeX. Este procesador ajusta los tamaos de
+ parntesis, integrales, subndices y superndices, alinea los
+ elementos de las matrices, construye cajas, etc.
+
+
+ LaTeX permite redactar fcilmente documentos estructurados.
+ A travs de distintas clases de documento y de su conjunto de
+ macros, LaTeX posibilita escribir textos dividindolos en
+ captulos, secciones, subsecciones, controlando en todo momento
+ la numeracin y las referencias cruzadas. Construye ndices de
+ contenidos, tablas o figuras. Ajusta los tamaos y tipos de
+ letras segn la parte del documento en que se hallen.
+
+
+ Facilidad en la construccin de macros y rdenes.
+ A poco de comenzar a usar este procesador, el usuario se
+ encuentra definiendo o redefiniendo rdenes para que stas se
+ ajusten a sus preferencias personales. Por ejemplo, es posible
+ que una determinada expresin aparezca repetidas veces en el
+ texto. Nada mas fcil que definir una orden que reemplace a todo
+ un bloque. O bien, es posible que no guste la forma en que LaTeX
+ numera las pginas. Una redefinicin al principio del documento
+ permite cambiar esto.
+
+
+ Se escribe en ASCII.
+ Esto, que al principio puede parecer un inconveniente (ya que
+ implica teclear mucho ms) se torna en ventaja al cabo del
+ tiempo. Por un lado permite incrementar la velocidad de
+ escritura (pues no hay que andar utilizando ratn o mens), por
+ otro facilita el uso de cualquier editor de texto (no contiene
+ caracteres de control) y permite su transmisin por correo
+ electrnico (puede escribirse en ASCII de 7 bits). Esto hace que
+ muchas revistas cientficas admitan artculos escritos en LaTeX,
+ enviados por e-mail. Ellos lo procesan en el lugar de destino,
+ hacen los cambios necesarios y lo imprimen.
+
+
+ Es gratis
+ Pues eso. Para ver porqu vase la seccin ``Porqu TeX es
+ gratis?''. A pesar de ello, existen tambin implementaciones
+ comerciales.
+
+
+
+ 2.2. Inconvenientes o ms bien, cules son las crticas ms habit-
+ uales?
+
+
+ Es muy difcil.
+ A diferencia de los procesadores visuales o WYSIWYG, que pueden
+ usarse casi desde el primer da con resultados aceptables, LaTeX
+ requiere un periodo de aprendizaje antes de conseguir los
+ primeros frutos. Incluso cuando ya se es un usuario medio o
+ avanzado, siempre es conveniente tener cerca un manual o un
+ LaTeXperto, al que preguntarle.
+
+ Este proceso de iniciacin consiste principalmente en aprenderse
+ las rdenes esenciales. Despus le siguen rdenes secundarias.
+
+ Ms tarde, puede uno aprender a programar en este lenguaje.
+ Llegado ese punto se puede dar el siguiente salto, atacar el
+ plain-TeX o incluso el TeX, para introducir rdenes de muy bajo
+ nivel, pero esto muy rara vez lo necesitar un usuario normal.
+ Estas dos ultimas fases slo son precisas si uno est interesado
+ en los intrngulis del sistema y los intrngulis de LaTeX se le
+ quedan cortos.
+
+ La contrapartida de este esfuerzo es que cuando se trabaja con
+ LaTeX y se compara el resultado con lo obtenido con otros
+ procesadores, la salida de stos ltimos parece "poco seria" en
+ cuanto se exigen frmulas matemticas. Algo como los dientes,
+ que duelen al salir, pero luego se hacen imprescindibles.
+
+ No se ven los resultados hasta que se compila el archivo.
+ Una de las decepciones que sufre el usuario novato es que no ve
+ los frutos de su trabajo hasta que compila. Como suelen aparecer
+ errores de compilacin, esto suele ser frustrante (aparte de
+ conllevar una prdida de tiempo). La nica solucin es armarse
+ de paciencia. Con el tiempo, los errores disminuyen y,
+ simultneamente, se aprende a procesar de cabeza, por lo que no
+ se necesita hacer una visualizacin para saber como va a quedar.
+
+ De todas formas, LaTeX no est especialmente dirigido a los
+ aspectos puramente estticos de cada pgina en concreto, sino a
+ los estructurales del documento. Si uno est interesado
+ estrictamente en la esttica (por ejemplo, porque trabaja en la
+ autoedicin), LaTeX no es el procesador adecuado. ste basa la
+ belleza de los documentos creados ms en la claridad, en el buen
+ criterio y en una esttica agradable que en la posibilidad de
+ hacer fcilmente diseos rebuscados para cada pgina.
+
+ Existen, no obstante, soluciones intermedias entre LaTeX y los
+ procesadores WYSIWYG. As, el TeXtures de los Mac, el xdvi de
+ las X-Window bajo Unix o los dviwin, yap o winview de los PC's
+ permiten mantener en pantalla el archivo que se est editando y
+ la visualizacin del ltimo, lo cual facilita la correccin de
+ los documentos.
+
+
+ No permite introducir imgenes.
+ Esta acusacin habitual no es en absoluto cierta. Simplemente
+ hay que ser conscientes de los medios de visualizacin e
+ impresin de que disponemos y obrar en consecuencia. Vase la
+ seccin ``Introduciendo figuras en LaTeX''
+
+
+ Lo que no debe olvidarse nunca es que tanto TeX como LaTeX estn
+ pensados como lenguajes de composicin de documentos, no de
+ autoedicin. A cada cual lo suyo.
+
+
+ No tiene variedad de tipos (fuentes)
+ Es cierto que los tipos CM originalmente desarrollados por Knuth
+ son limitados en cantidad y variedad, por lo que a medida que
+ LaTeX se difunda han aumentado las demandas de ms tipos para
+ usos diversos. Aunque el crecimiento es todava lento, existe
+ una gran cantidad de tipos disponibles en el CTAN en:
+
+
+
+ CTAN:fonts
+
+
+
+ En las versiones para salidas postscript si es posible el uso de
+ cualquier tipo, pero no se garantiza que las ecuaciones mantengan
+ la calidad requerida.
+
+
+ 3. Qu documentacin hay disponible sobre TeX/LaTeX?
+
+ Adems de las referencias que aqu se citan, puede consultarse la
+ seccin de manuales en las pginas de CervanTeX,
+ http://www.cervantex.org/manuales.php
+
+
+
+ 3.1. Tutoriales de LaTeX en castellano.
+
+
+ Una descripcin de LaTeX
+ Toms Bautista (bautista _AT_ cma.ulpgc.es) ha escrito un
+ documento titulado Una descripcin de LaTeX (basado inicialmente
+ en LaTeX-Kurzbeschreibung, de H. Partl, E. Schlegl e I. Hyna),
+ donde se han introducido algunas notas especficas de la
+ implementacin del estilo spanish.sty desarrollado por J.
+ Snchez. Este documento se encuentra en CTAN (en
+ CTAN:documentation/short/spanish) y la versin ms actualizada
+ est siempre en
+
+ ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/
+
+
+ Apuntes. Manual de LaTeX
+ Preparado en Chile y disponible en
+ http://cipres.cec.uchile.cl/~admcons/manuales/latex.html
+
+
+ Bases de datos bibliogrficos, LaTeX y el idioma espaol
+ Luis Seidel
+
+ Acerca del uso de BibTeX en castellano. Disponible en postscript
+ en la pgina del autor y en formato pdf en la Universidad de la
+ Rioja:
+
+ http://feynman.faii.etsii.upm.es/~seidel/bibliogr.ps
+
+
+ ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf
+
+ Curso de LaTeX
+ Kjetil Halvorsen. Transparencias de un curso de LaTeX
+ disponibles en
+
+
+ ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip
+
+
+ Recetario para LaTeX
+ por Aristarco. Disponible en http://recetariolatex.cjb.net
+
+
+ Referencias rpidas de LaTeX
+ por Fernando Arbeiza. Disponible en
+ http://www.loarco.homelinux.org/lqref-es
+
+
+ 3.2. Libros en castellano
+
+
+ Iniciacin a LaTeX2e
+ Javier Sanguino Botella, Addison-Wesley (1997)
+
+
+ Composicin de textos cientficos con LaTeX.
+ G. Valiente. Edicions UPC, Barcelona, 1997
+
+
+ LaTeX, primeros pasos.
+ F. Ortegn Gallego. Editorial Masson, Barcelona 1.992. (Sobre
+ LaTeX 2.09)
+
+
+ LaTeX, una imprenta en sus manos.
+ Bernardo Cascales Salinas, Pascual Lucas Saorn, Jose Manuel
+ Mira Ros, Antonio Pallars Ruiz y Salvador Snchez-Pedreo
+ Guilln. Aula Documental de Investigacin, Madrid, 2000.
+
+
+ El libro de LaTeX.
+ Bernardo Cascales, Pascual Lucas, Jos Manuel Mira, Antonio
+ Pallars y Salvador Snchez-Pedreo. Prentice Hall, Madrid,
+ 2003.
+
+
+ El universo LaTeX.
+ Rodrigo De Castro. Facultad de Ciencias, Universidad Nacional de
+ Colombia, Bogot, 2003.
+
+
+ 3.3. Tutoriales en otros idiomas
+
+
+ A Gentle Introduction to TeX
+ de Michael Dobb, disponible en CTAN:documentation/gentle. Es un
+ excelente tutorial de introduccin al plain-TeX en ingls.
+
+ Una referencia clsica de TeX
+
+ Simplified Introduction to LaTeX
+ de Harvey J. Greenberg, disponible en
+ CTAN:documentation/simplified-latex/latex.ps (versin
+ postscript) y la versin ms reciente en
+ http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html. Basado
+ en un curso para pregraduados.
+
+
+ LaTeX: from quick and dirty to style and finesse
+ Escrito por Tony Roberts, se encuentra disponible en la
+ Universidad de Southern Queensland (Australia)
+ http://www.sci.usq.edu.au/staff/robertsa/LaTeX/ con una rplica
+ en Estados Unidos http://ricardo.ecn.wfu.edu/LaTeX/.
+
+
+ LaTeX for Word Processor Users
+ Escrito por Guido Gonzato, es un tutorial LaTeX pensado
+ especficamente para usuarios de procesadores de texto. Est
+ disponible en CTAN:info/latex4wp
+
+
+ l2tabu
+ Escrito por Mark Trettin, es un tutorial sobre lo que no debe
+ hacer un usuario de LaTeX2e. Disponible en el CTAN como un
+ archivo pdf, http://www.ctan.org/tex-archive/info/l2tabu/.
+ Contiene una lista de rdenes y paquetes obsoletos que no deben
+ utilizarse bajo LaTeX2e, as como otros errores habituales.
+
+ Online tutorials on LaTeX
+ del grupo de usuarios de TeX de la India, disponible en
+ http://www.tug.org.in/tutorials.html.
+
+
+ 3.4. Libros en otros idiomas
+
+
+ A Guide to LaTeX
+ H. Kopka y P.W. Daly, Addison-Wesley Professional (2004)
+
+ Probablemente, el mejor manual existente sobre LaTeX. Contiene
+ una gua completa de rdenes, abundantes ejemplos e informacin
+ adicional. (Incluye las dos versiones en uso de LaTeX, LaTeX2e y
+ la ms antigua, LaTeX2.09).
+
+
+ The LaTeX Companion.
+ Frank Mittelbach, Michel Goossens, Johannes Braams, David
+ Carlisle, Chris Rowley, Addison Wesley Professional (2004).
+
+ Este manual sirve de ampliacin del anterior. Es una
+ recopilacin e informacin sobre los llamados paquetes
+ (packages), conjuntos de macros que distintos autores han puesto
+ a disposicin pblica.
+
+
+ The LaTeX Web Companion: Integrating TeX, HTML, and XML
+ Michel Goossens, Sebastian Rahtz, Eitan M. Gurari, Ross Moore
+ y Robert S. Sutor, Addison Wesley Professional (1999).
+
+ Publicando documentos en la WWW mediante LaTeX
+
+
+ LaTeX--A Document preparation system
+ L. Lamport (dos ediciones) Addison-Wesley (1985 y 1994).
+
+ Durante mucho tiempo este fue "el libro" del LaTeX. Escrito por
+ el mismo autor del programa, contiene todo lo esencial para
+ introducirse en este procesador, si bien resulta un tanto
+ insuficiente para usuarios avanzados. La primera edicin
+ corresponde a la versin antigua del programa (LaTeX209, hoy
+ obsoleta) y la segunda al LaTeX2e.
+
+
+ The LaTeX Graphics Companion
+ M. Goossens, S. Rahtz y F. Mittelbach, Addison-Wesley (1997).
+
+ Un extenso manual acerca de cmo ilustrar documentos con TeX y
+ postscript.
+
+
+ The TeXbook
+ D.E. Knuth, Addison-Wesley (1986).
+
+ Este es "el libro" para los que quieren conocer las entraas de
+ TeX. Contiene todo sobre el lenguaje TeX, escrito por el mismo
+ autor del programa. Es un libro completo y ameno pero
+ absolutamente incomprensible para los novatos. El archivo fuente
+ en TeX de este libro est disponible para aquellos que desean
+ conocer los trucos que el autor emple a la hora de escribirlo
+ (algunos verdaderamente complejos).
+
+
+ Knuth proporciona el cdigo fuente con fines didcticos, no para
+ que se imprima. De hecho, si se intenta TeXearlo entrar en un
+ bucle infinito que dice que eso no debe hacerse. Aunque no es
+ complicado hacer que deje de ocurrir, sera ilegal hacerlo...
+ :-)
+
+
+ TeX by Topic, A TeXnician's Reference
+ de Victor Eijkhout, editado por Addison-Wesley (1992) y
+ disponible en http://www.eijkhout.net/tbt/,
+
+ es otro de los libros clsico sobre TeX (no LaTeX) que puede
+ descargarse gratis (y legalmente) en un pdf.
+
+ TeX for the Impatient
+ de Karl Berry, tambin est disponible en CTAN:info/impatient/
+ de forma libre.
+
+
+ Making TeX work
+ de Norman Walsh, editado por O'Reilly (ISBN: 156592-051-1), pero
+ actualmente descatalogado. Sin embargo est disponible de forma
+ libre en http://makingtexwork.sourceforge.net/mtw/. Aunque
+ algunas cosas estn obsoletas, (de hecho todava se refiere a
+ LaTeX 2.09), tanto su contenido como sus fuentes pueden an ser
+ de utilidad.
+
+
+
+ 3.5. Revistas.
+
+
+ The PracTeX Journal
+ Una revista de TeX on-line y gratuita. Disponible en
+ http://dw.tug.org/pracjourn/.
+
+
+ 4. Que elementos intervienen al procesar un documento con LaTeX?
+
+ 4.1. El documento fuente: Cmo creo un documento con LaTeX, lo pro-
+ ceso, lo veo y lo imprimo?
+
+ Como hemos dicho TeX/LaTeX es realmente un lenguaje de programacin de
+ textos. En el documento fuente original se introduce el texto a
+ procesar junto con una serie de rdenes especificando cmo debe ser
+ procesado ste. Este paso se realiza con el editor de texto favorito
+ del autor, aunque hay algunos editores de texto que estn, mejor
+ adaptados, o totalmente integrados para su uso con TeX/LaTeX -- vase
+ ``editores para TeX'' --. Pongamos por ejemplo que el documento creado
+ es documento.tex.
+
+ Una vez terminado el documento fuente (documento.tex), ste se procesa
+ mediante TeX si se han utilizado las rdenes de plain-TeX o LaTeX si
+ se han utilizado las rdenes de LaTeX. Se corrigen los posibles
+ errores de sintaxis y se repite el proceso hasta que stos se han
+ eliminado. Como resultado del procesamiento se tiene un archivo
+ independiente del dispositivo, o DVI (documento.dvi).
+
+
+ 4.2. Qu es un archivo DVI?
+
+ Un archivo DVI es el archivo resultante de procesar el texto fuente a
+ travs de TeX. Su forma no depende del dispositivo que se vaya a
+ utilizar para verlo/imprimirlo. Un archivo DVI est pensado para ser
+ ledo por un conversor que produzca una salida adecuada para una
+ determinada impresora, o para un determinado visualizador en la
+ pantalla del ordenador. Los archivos DVI utilizan una codificacin
+ interna de TeX, de forma que un documento fuente debe producir
+ exactamente el mismo archivo DVI, con independencia de la
+ implementacin de TeX que se utiliza para producirlo.
+
+ Un archivo DVI contiene toda la informacin necesaria para imprimir o
+ ver el resultado, excepto los tipos o su aspecto concreto (aunque
+ contiene sus medidas) o informacin que se introducir mediante una
+ orden \special -- vase ``Qu son los \special?''.
+
+
+
+ 4.3. Qu es un conversor (driver)?
+
+ Un conversor es un programa que toma su entrada de un archivo DVI y
+ produce un archivo que puede enviarse a una impresora o una salida
+ directa a una pantalla.
+
+ Estos conversores normalmente son especficos a cada impresora o
+ lenguaje de impresora. Por ejemplo, una impresora postscript entender
+ siempre la salida de un conversor postscript, pero en general no de
+ otros formatos.
+
+ Al igual que el archivo DVI, el conversor necesita informacin sobre
+ los tipos que puede encontrar en distintos lugares.
+
+
+ 4.4. Qu son los archivos .pk ?
+
+ Los archivos .pk (cuyo nombre viene de packed raster) contienen tipos
+ de letra en forma de mapa de bits. METAFONT produce una salida en mapa
+ de bits en un formato no comprimido denominado .gf, que es convertido
+ a .pk mediante una utilidad denominada gftopk. Para cada diseo de
+ letra, tamao, peso y familia es necesario un archivo .pk distinto, e
+ incluso para distintos dispositivos de salida. Como consecuencia de
+ sto se guardan en una estructura compleja de directorios, o en
+ libreras de tipos, para normalizar el acceso a las mismas.
+
+
+ 4.5. Qu son los archivos .tfm ?
+
+ tfm es la abreviatura de TeX font metric, mtrica de los tipos TeX.
+ Los archivos .tfm guardan la informacin acerca de los tamaos de los
+ caracteres en cada tipo, as como las ligaduras y desplazamientos
+ dentro de cada tipo. Se necesita un archivo .tfm para cada tipo
+ utilizado por TeX, es decir para cada diseo, peso y familia, aunque
+ uno valga para todas las magnificaciones. TeX utiliza los archivos
+ .tfm para componer la pgina, pero en general los conversores no los
+ necesitan.
+
+
+ 4.6. Qu son los tipos (fuentes) CM?
+
+ Los tipos CM son los tipos originalmente creados por Donald E. Knuth.
+ Cuando desarroll TeX, lo acompa de este conjunto completo de tipos
+ de alta calidad. Estos tipos eran independientes de la impresora
+ utilizada (ya que eran tratados como grficos) lo que produca la
+ misma calidad en cualquier sitio. Con el tiempo, estos tipos (los
+ Computer Modern o CM) se convirtieron en la firma del procesador, que
+ permita identificar un documento a primera vista.
+
+
+ 4.7. Qu son los tipos (fuentes) EC/DC?
+
+ Son fuentes del tipo de las Computer Modern, pero con 256 caracteres,
+ que cubren las necesidades de casi todas las lenguas habladas en
+ Europa y algunas otras que utilizan el alfabeto latino. Su nombre
+ viene de European Computer Modern Fonts. Dichas fuentes contienen
+ caracteres acentuados siguiendo el esquema de codificacin de Cork.
+ Han estado durante bastante tiempo en periodo de pruebas y durante ese
+ tiempo se llamaban DC. Ya se distribuyen normalmente al pblico en
+ general, con el nombre EC, y a partir de ese momento las DC se
+ consideran obsoletas.
+
+ Estas fuentes ya estn presentes en las distribuciones modernas de
+ TeX/LaTeX, pero en caso de que se trabaje con una distribucin antigua
+ pueden conseguirse en:
+
+ CTAN:fonts/ec/ready-mf
+
+
+
+ y los archivos tfm para LaTeX estn en
+
+
+ CTAN:fonts/ec/tfm
+
+
+
+ Si tenemos tipos de Cork (PostScript, DC, etc.) y queremos utilizar
+ esta codificacin en las fuentes de salida se debe introducir en el
+ prembulo del documento la lnea
+
+
+ \usepackage[T1]{fontenc}
+
+
+
+ 4.8. Qu son los tipos (fuentes) virtuales?
+
+ Los tipos (fuentes) virtuales proporcionan a TeX una forma de trabajar
+ con algo ms complejo que los caracteres individuales definidos en un
+ tipo. En un tipo virtual se definen a partir de elementos simples de
+ los tipos normales, elementos ms complejos que TeX considerar como
+ si fueran elementos de un tipo normal (tienen sus tamaos y su archivo
+ .tfm de mtrica), pero que en realidad el procesador del DVI compondr
+ a partir de distintos elementos constituyentes para formar a partir de
+ ellos el elemento complejo descrito en el tipo virtual. De esta forma
+ es posible remapear caracteres, hacer un tipo compuesto con elementos
+ tomados de distintos tipos o en general construir elementos muy
+ complejos a partir de elementos simples de los distintos tipos. Por
+ ejemplo se utilizan tipos virtuales para remapear tipos postscript.
+
+ TeX en s no ve los tipos virtuales, nicamente trabaja con las
+ mtricas que le da el tipo virtual en su .tfm como si se tratara de
+ tipos normales.
+
+
+ 4.9. Qu son las rdenes \special ?
+
+ TeX proporciona una forma de expresar cosas que los conversores pueden
+ hacer, pero de las que TeX no sabe nada. Por ejemplo TeX no sabe cmo
+ introducir figuras postscript en un documento o cmo cambiar el color
+ del texto impreso, pero algunos conversores s saben cmo hacerlo.
+
+ Para ello TeX proporciona la orden \special. TeX simplemente entiende
+ la orden como correcta y la pasa con sus argumentos al archivo DVI,
+ sin hacer nada de lo que en ella se dice. Es el conversor el que debe
+ interpretar la orden y hacer lo que se le pide.
+
+ La sintaxis de los \special es fuertemente dependiente del dispositivo
+ de salida y en general no es vlida para distintos dispositivos.
+ LaTeX2e proporciona paquetes estndar de grficos (graphics, graphicx)
+ y manejo de color (color), que hacen ms fcil la inclusin de
+ grficos, rotacin, reescalado y cambios de color --Vase la seccin
+ ``Introducir grficos con LaTeX''.
+
+
+
+ 4.10. Qu es el postscript y el postscript encapsulado (archivos
+ .eps )?
+
+ PostScript (PS) es un lenguaje de programacin para describir pginas.
+ Como lenguaje estructurado permite la programacin (tiene estructuras
+ de control y bucles), y recuerda el lenguaje de programacin FORTH.
+ Originalmente fue desarrollado por Adobe. Existen varios intrpretes
+ de PostScript que permiten la visualizacin de este formato. El ms
+ extendido es Ghostscript (GS), de Aladdin, del que puede obtenerse
+ informacin en http://www.cs.wisc.edu/~ghost/index.html y en
+ http://www.aladdin.com cuando acaben de construirla. El formato PS se
+ basa en describir cada pgina desde un origen de coordenadas que se
+ sita en la esquina inferior izquierda de la pgina. PS permite, sin
+ embargo, redefinir el origen, de forma que se puede recomenzar la
+ descripcin de un bloque de una pgina desde un origen arbitrario.
+
+ PS encapsulado (EPS) es el formato estndar para importar y exportar
+ archivos PS en cualquier tipo de entornos. Usualmente es un archivo
+ que contiene una sola pgina que describe una figura. El archivo EPS
+ est especialmente pensado para incluirlo en otros archivos PS, y es
+ como cualquier otro archivo PS con algunas restricciones. La FAQ de
+ PostScript puede alcanzarse en
+ http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html,
+ de donde est tomado mucho de lo anterior.
+
+
+ 4.11. Qu es el formato pdf ?
+
+ PDF (Portable Document Format) es, como su nombre indica, un formato
+ de archivos transportable entre distintas plataformas, creado por
+ Adobe y especialmente diseado para visualizar documentos tal y como
+ se han diseado. Permite usar colores, grficos, seguir enlaces e
+ imprimir pero, fundamentalmente, permite ver en la pantalla los
+ documentos, siendo un formato compacto. Es muy similar a PS, pero no
+ tiene capacidades de programacin. En relacin con TeX, PDF es un
+ formato que sustituye al DVI -- ver la pregunta ``Qu es DVI?'' -- en
+ la salida de TeX. En la web hay informacin abundante sobre PDF en
+ http://www.pdfzone.com/webring/. Los visualizadores de PDF ms
+ recomendables son Adobe Reader (antes Acrobat Reader), de Adobe,
+ gratuito (http://www.adobe.com), xpdf
+ http://www.foolabs.com/xpdf/home.html y Ghostview
+ http://www.cs.wisc.edu/~ghost/index.html.
+
+
+ 4.12. Qu son los paquetes en LaTeX?
+
+ Escribir un documento a base de primitivas TeX puede resultar
+ extremadamente engorroso. LaTeX utiliza las primitivas de TeX para
+ definir otro conjunto de comandos ms amigable, para las tareas ms
+ habituales (definir captulos, tablas, listas enumeradas...). No
+ obstante, LaTeX no incluy nuevos comandos de alto nivel para
+ cualquier tarea imaginable, sino que se hizo extensible a base de
+ paquetes, de forma que hay un cuerpo de LaTeX y unos aadidos en forma
+ de paquetes. Un paquete es un fichero que contiene ms cdigo, que se
+ incluye en el prembulo del documento (con \usepackage{nombre-
+ de_paquete}),y que define nuevos comandos basndose, ya sea en las
+ primitivas de TeX o en los comandos previamente definidos por LaTeX.
+
+ La distribucin de TeX/LaTeX instalada en el sistema ya incluir una
+ buena cantidad de paquetes listos para su uso. Sin embargo, pueden
+ aadirse nuevos paquetes -- vase ``Instalacin de paquetes''.
+
+
+
+ 4.13. Qu son los archivos .dtx ?
+
+ Tanto LaTeX2e como muchos de los paquetes de macros se escriben en un
+ lenguaje de programacin ilustrada, con cdigo y documentacin en el
+ mismo fichero. Este formato, conocido como doc se debe a Frank
+ Mittelbach. El fichero que contiene las fuentes comentadas suele tener
+ la extensin .dtx y normalmente debe aligerarse de la documentacin
+ antes de su uso como macro, o correr LaTeX sobre el fichero para
+ producir una versin maquetada de la documentacin. Habitualmente se
+ suministra un fichero .ins para facilitar esto, que utiliza el paquete
+ docstrip. Pueden incluirse varios paquetes dentro de un mismo fichero
+ .dtx. Para ms informacin acerca de cmo extraer el contenido de un
+ fichero .dtx vase ``extraer de un .dtx''.
+
+ LaTeX no utiliza los ficheros .dtx una vez procesados para producir
+ los .sty o .cls, por lo que no es estrictamente necesario tenerlos
+ instalados, aunque puede ser recomendable, ya que son siempre la
+ principal fuente de informacin sobre el paquete.
+
+
+ 5. Cmo consigo LaTeX y otros programas relacionados?
+
+ 5.1. Distribuciones TeX/LaTeX
+
+ En principio se podra coger todo el sistema elemento a elemento y
+ ponerlo todo en comn. Sin embargo, para que sto funcione
+ correctamente, el tiempo requerido y la complejidad del trabajo son
+ grandes. Por esta razn algunas personas o empresas ya lo han hecho y
+ lo ofrecen preparado en lo que se denominan distribuciones.
+
+ Se entiende por distribucin un conjunto de binarios y paquetes de
+ macros LaTeX junto con otras utilidades adicionales, empaquetados de
+ forma coherente y organizada, para que trabajen en comn de la forma
+ ms eficiente posible. Hay distribuciones de libre distribucin,
+ shareware (se puede distribuir y probar, pero si se quiere usar
+ regularmente es necesario pagar el registro) y otras de distribucin
+ comercial. Aunque algunas de las distribuciones comerciales tienen
+ caractersticas adicionales sobre las distribuciones libres, a veces
+ es al contrario. Aunque algunas distribuciones estn disponibles para
+ distintos sistemas operativos, lo ms habitual es que estn limitadas
+ a un sistema operativo.
+
+ Las distribuciones libres o shareware pueden conseguirse en el CTAN --
+ vase ``Qu es el CTAN?'' --, o a travs de los CD-ROM editados por
+ distintos grupos de usuarios de LaTeX, mientras que las comerciales se
+ consiguen a travs de sus respectivos distribuidores o directamente si
+ no los hay.
+
+ Para buscar distribuciones para los distintos sistemas operativos, la
+ estructura de un nodo CTAN es siempre la misma. Existe un directorio
+ tex-archive del cual cuelga un rbol de directorios. En particular,
+ existe un directorio systems, del que penden las distintas
+ implementaciones. Existen versiones para
+
+
+ Atari
+ Amiga
+ UNIX
+ VMS
+ Os2
+ Windows NT
+ Mac
+ MS-DOS
+
+
+
+ No es necesario tener una acceso de red para acceder al CTAN. El grupo
+ de usuarios alemanes de TeX (DANTE) ha hecho una recopilacin en CD-
+ ROM del contenido del CTAN. Las edicin de 1999 y posteriores se han
+ distribuido a travs del grupo de usuarios CervanTeX. Para mayor
+ informacin se puede consultar la pgina web del grupo CervanTeX
+
+
+ 5.1.1. Distribuciones libres o shareware
+
+
+ Unix
+ teTeX es, para sistemas Unix la eleccin ms multiplataforma. Se
+ puede encontrar en CTAN:systems/unix/teTeX y contiene por un
+ lado una serie de archivos que no dependen del sistema operativo
+ y por otro lado binarios para toda una serie de sistemas
+ operativos Unix.
+
+
+ Linux
+ Aunque lo que se acaba de decir de Unix es tambin vlido para
+ Linux, recalcar adems que en las principales distribuciones de
+ Linux vienen paquetes de teTeX listos para instalar y utilizar
+ sin apenas esfuerzo.
+
+ Antes tambin haba otra distribucin denominada NTeX. Es
+ necesario tener un especial cuidado y no utilizar la incluida en
+ el CD-ROM de Slackware'96, que inclua una versin de las
+ fuentes CM que no respetaba las condiciones de distribucin y
+ cambiaba la mtrica respecto de las estndar sin cambiar el
+ nombre, rompiendo la portabilidad de los documentos. En la
+ prctica este aviso debe estar ya obsoleto.
+
+
+ Mac
+ Los Macs modernos ya no utilizan el sistema operativo clsico
+ sino uno basado en *BSD unix (Mac OS X), con una capa grfica
+ que no son las X-Window (pero que tambin se pueden poner).
+
+ Por este motivo muchas aplicaciones unix clsicas se han
+ adaptado con facilidad a Mac OS X, entre ellas teTeX. La pgina
+ http://www.rna.nl/tex.html tiene una gran cantidad de
+ informacin sobre el uso de TeX en Mac OS X, incluyendo un
+ instalador de teTeX. Se necesita un editor que se comunique bien
+ con TeX, como los que se mencionan ms adelante. Otras pginas
+ muy interesantes son http://www.esm.psu.edu/mac-tex/default.html
+ y http://latex.yauh.de/index_en.html.
+
+ Para Mac clsicos sigue existiendo OzTeX. ste es una versin
+ shareware de TeX para los ordenadores Macintosh clsicos.
+ Incluye un visualizador de dvi y un conversor a postscript. Est
+ disponible en CTAN:non-free/systems/mac/oztex. Su pgina
+ original est en http://www.trevorrow.com/oztex/
+
+
+ DOS/OS2
+ emTeX es, para sistemas DOS la distribucin ms extendida. Puede
+ encontrarse en CTAN:systems/msdos/emtex, aunque desde hace
+ tiempo no se ven versiones nuevas. gTeX era otra distribucin
+ para DOS, pero recientemente ha sido retirada de CTAN a peticin
+ de su creador. Tambin est emTeX-TDS, que no es ms que un
+ rbol de archivos de estilo para TeX/LaTeX preparado para ser
+ utilizado con los binarios de emTeX.
+
+
+ Win32
+
+ MikTeX de Christian Schenk es tambin una distribucin
+ completa independiente de teTeX. tiene su propio visualizador
+ yap que permite imprimir, aunque tambin se incluye dvips.
+ Est disponible en CTAN:systems/win32/miktex. Si se tiene
+ conexin de red, las ltimas versiones permiten traer e
+ instalar paquetes sobre la marcha segn se van necesitando.
+ Para obtener informacin sobre la instalacin de un sistema
+ LaTeX (mikTeX) en Windows puede consultarse la pgina
+ http://www.udlap.mx/~ma108907/latex/winlatex.html.
+
+ XEmTeX, de Fabrice Popineau, es una distribucin integrada de
+ TeX, LaTeX, ConTeXt, Xemacs y otros programas para Windows.
+ Todos los programas han sido compilados de forma nativa para
+ optimizar el rendimiento bajo Windows. Se suministra
+ configurado para que funcione nada ms instalarse. Su pgina
+ es http://www.fptex.org/
+
+ fpTeX de Fabrice Popineau era una versin de teTeX para
+ Windows. Sin embargo, su autor lo ha dejado de lado para
+ concentrarse en XEmTeX. De momento sigue disponible en
+ CTAN:systems/win32/fptex, pero ya no est mantenido.
+
+
+ 5.1.2. Distribuciones comerciales
+
+
+ Windows
+
+ Scientific WordScientific Word/WorkPlace/Notebook ofrece una
+ forma de trabajo tipo casi WYSIWYG con un procesador TeX en
+ segundo plano. Ms informacin en
+ http://www.sciword.demon.co.uk/. Incluye TrueTeX. Aunque
+ proporciona un entorno amistoso para la escritura de
+ documentos, en algunos casos integrado con maple para
+ realizar clculos simblicos, es muy rgido cuando es
+ necesario salirse de los estilos estndar proporcionados con
+ SW y no es fcil compartir archivos LaTeX generados con SW
+ con otras personas que no lo usen, porque necesitan una serie
+ de paquetes especficos. Adems, los argumentos opcionales de
+ algunas macros dan error en SW, aunque dependiendo de uso que
+ se le de, sto puede no aparecer. A pesar de todo, puede ser
+ til para una persona que no quiere hacer cosas complicadas.
+
+
+ 5.2. Editores de texto que trabajan especialmente bien con LaTeX
+
+
+ Unix
+
+ GNU emacs o xemacs utilizado en combinacin con el paquete
+ AUCTeX (disponible en CTAN:support/auctex) o como un paquete
+ ya incluido en muchas distribuciones) proporciona mens
+ desplegables y secuencias de control para las estructuras
+ habituales, verifica sintaxis y la muestra coloreada, permite
+ llamar a TeX y a los conversores desde el editor y mucho ms.
+ Complejo, pero muy potente. Joaqun Ataz ha escrito un manual
+ para su uso con LaTeX, Creacin de ficheros LaTeX con GNU
+ Emacs, disponible en CTAN:info/spanish/guia-atx/guia-atx.pdf
+
+ kile Trabaja sobre cualquier plataforma con KDE instalado y
+ segn la documentacin, hasta en OS-X... Tiene opciones para
+ compilacin y conversiones con una nica pulsacin de tecla,
+ se pueden personalizar las rdenes y se integra con cualquier
+ visualizador dvi, ps o pdf que tengamos. Disponible en la
+ mayor parte de las distribuciones Linux y en
+ http://kile.sourceforge.net.
+ Mac
+ Para Mac OS X hay algunos editores que se entienden bien con TeX
+
+ TeXShop Muy majo y en castellano. Se encuentra en
+ http://www.uoregon.edu/~koch/texshop/.
+
+ iTeXMac Tiene ms cosas, pero es ms lento y hay muchos
+ mensajes de "an no implementado". Se encuentra en
+ http://itexmac.sourceforge.net/.
+
+ DOS/OS2
+ TeXshell es un entorno de trabajo simple y fcilmente
+ personalizable que puede ser utilizado con el editor favorito de
+ cada uno. Tambin cuenta con un editor propio que permite seguir
+ los errores de la compilacin fcilmente aunque no soporta
+ archivos de ms de 64K. Aunque puede particularizarse a otras
+ distribuciones, viene muy preconfigurado para emTeX.
+
+ Win32
+
+ winedt es un paquete shareware del que se suele oir hablar
+ bien. Proporciona un entorno de trabajo desde el que llamar a
+ los distintos programas y un editor potente y bien
+ configurado
+
+ Winshell es un programa libre de prestaciones menores, pero
+ que puede ser ms que suficiente para muchos usuarios.
+
+ TeXnic Center es tambin un buen entorno de trabajo para
+ Win32. Est disponible en CTAN en
+ CTAN:systems/win32/TeXnicCenter/
+
+
+ Otros programas que no son editores completos, pero que ayudan a la
+ edicin son:
+
+ LaTable
+ es un ayudante de creacin de tablas que permite generar el
+ cdigo LaTeX necesario para la creacin de una tabla. La tabla
+ se disea en un entorno visual muy cmodo y la herramienta
+ genera el cdigo LaTeX que se incorpora al documento con un
+ simple copy-paste. Tambin permite guardar las tablas generadas
+ para su posterior modificacin. Todava tiene detalles, pero
+ cuenta con muchas opciones bastante tiles, y genera un cdigo
+ relativamente limpio... adems, aunque es un programa Win32
+ funciona bien en Linux usando el emulador Wine. Disponible en
+ http://www.g32.org/latable/. Es freeware de uso, pero sus
+ fuentes no estn disponibles.
+
+
+ TeXaide
+ para quienes sigan pensando que las ecuaciones se deben hacer
+ con diseadores ... (se consiguen mucho mejores resultados a
+ mano, pero no faltan quienes abandonan LaTeX cuando se enfrentan
+ a las ecuaciones. Segn los que lo han probado, el cdigo que
+ genera no es en ocasiones muy limpio, pero suele funcionar bien.
+ Es un programa Win32 que tambin funciona en Linux usando el
+ emulador Wine. Disponible en
+ http://www.dessci.com/en/products/texaide/.
+
+
+ 6. Preguntas especficas para el LaTeX en castellano
+
+
+
+ 6.1. Cmo puedo usar TeX en castellano? o Qu es lo mnimo que hay
+ que saber para escribir en castellano con TeX/LaTeX?
+
+ En realidad, no es necesario nada adicional que no est ya incluido en
+ las distribuciones ms habituales. El problema normalmente se reduce a
+ tres cosas:
+
+ 1. Introduccin de caracteres acentuados. Vanse las respuestas a las
+ preguntas ``mediante rdenes LaTeX'', ``Cmo introducir
+ directamente los caracteres extendidos?'' y ``acentos en modo
+ matemtico''
+
+ 2. Literales en castellano. Vase la respuesta a la pregunta ``Cmo
+ cambiar los literales que LaTeX produce?''.
+
+ 3. Patrones de particin de palabras (silabeo o guionado). Vase
+ ``patrones de guionado'' donde se explica cmo hacer que TeX parta
+ las palabras siguiendo las reglas del espaol.
+
+
+ 6.2. Con LaTeX, cmo puedo escribir los acentos y dems caracteres
+ extendidos?
+
+ 6.2.1. Mediante rdenes LaTeX
+
+ Cuando no hay ms remedio, los caracteres extendidos se escriben as:
+
+
+ ==> \'a ==> \'A ==> \~n ==> ?`
+ ==> \'e ==> \'E ==> \~N ==> !`
+ ==> \'\i{} ==> \'I ==> \"u
+ ==> \'o ==> \'O ==> \"U
+ ==> \'u ==> \'U
+
+
+
+ Sin embargo, sto normalmente no es necesario. Vase la respuesta a la
+ pregunta ``Introducir directamente los caracteres extendidos''
+
+
+ 6.2.2. Directamente mediante el paquete inputenc
+
+ El paquete inputenc permite escribir directamente en la pgina de
+ cdigos habitual, convirtindose internamente el texto introducido a
+ texto LaTeX, de acuerdo con las diferentes tablas de equivalencia para
+ las distintas pginas de cdigos y de forma completamente transparente
+ al usuario.
+
+ Si somos usuarios de UNIX, debemos poner al principio de nuestro
+ documento (en lo que se denomina el prembulo, entre \documentclass...
+ y \begin{document}) lo siguiente:
+
+
+ \usepackage[latin1]{inputenc}
+
+
+
+ si la codificacin es iso-8889-1 (tambin conocida como latin1).
+
+ Si la codificacin es utf-8, como en muchas distribuciones recientes
+ de Linux:
+
+
+
+ \usepackage[utf8]{inputenc}
+
+
+
+ pero si la instalacin es antigua, debe utilizarse el paquete ucs (en
+ muchas distribuciones se le llama latex-ucs, aunque carga ucs.sty):
+
+
+ \usepackage{ucs}
+ \usepackage[utf-8]{inputenc}
+
+
+
+ Si trabajamos con MS-Windog hay que usar cp1252 (que es casi el
+ latin1)
+
+
+ \usepackage[cp1252]{inputenc}
+
+
+
+ (ansinew es una variante obsoleta). Si trabajamos con DOS, hay que
+ poner esto:
+
+
+ \usepackage[cp850]{inputenc}
+
+
+
+ y si somos de Macintosh, esto otro:
+
+
+ \usepackage[applemac]{inputenc}
+
+
+
+ (aunque hay editores de Mac que guardan como latin1 o utf8).
+
+ Por lo tanto, el mtodo recomendado para utilizar caracteres de 8 bits
+ en TODAS las plataformas en LaTeX2e es escribir:
+
+
+ \usepackage[tipo]{inputenc}
+
+
+
+ para decir qu pgina de cdigos de entrada usamos.
+
+ Ni este mtodo ni el que se menciona en ``acentos LaTeX'' son vlidos
+ en modo matemtico.
+
+
+ 6.2.3. Cmo introducir acentos en modo matemtico?
+
+ Para introducir acentos en modo matemtico no hay ms remedio que
+ hacerlo mediante rdenes LaTeX, pero en este caso son distintas de las
+ de la seccin ``acentos LaTeX''. Por ejemplo mx se escribira en modo
+ matemtico como m\acute{a}x y como \tilde{n}. Si se quiere un acento
+ sobre una i, tanto spanish para babel como el paquete dotlessi
+ (CTAN:macros/latex/contrib/supported/bezos/dotlessi.sty) proporcionan
+ la orden \dotlessi; por ejemplo, mn se escribira
+ m\acute{\dotlessi}n.
+
+
+ spanish.sty ya proporciona algunas de estas palabras acentuadas, por
+ ejemplo, despus de cargar el paquete babel con la opcin spanish
+ mediante \usepackage[spanish]{babel}, $\min a$ permite escribir la
+ palabra acentuada. Tambin proporciona un \dotlessi que complementa a
+ \imath.
+
+
+ 6.3. Puedo compartir mis archivos LaTeX en los que he escrito los
+ acentos directamente?
+
+ Si los caracteres acentuados estn escritos mediante rdenes LaTeX
+ pueden compartirse sin problemas, ya que se utiliza nicamente
+ codificacin de 7 bits.
+
+ Si introduzco las letras acentuadas directamente como en ``utilizando
+ inputenc'', tendr dos posibles problemas:
+
+ 1. Me servir para otros ordenadores que utilicen una pgina de
+ cdigos diferente?, pues la segunda mitad del conjunto de
+ caracteres es distinta de unos a otros.
+
+ 2. Podr enviarlo por correo electrnico?, pues solamente acepta 7
+ bits.
+
+ Cmo se soluciona esto? Con GNU recode, con MIME, o con las dos
+ cosas, segn el caso.
+
+ 1. Si simplemente se quiere procesar el documento, s que servir para
+ otros ordenadores: Ejemplo: Si nosotros tenemos Unix y alguien que
+ usa Macintosh nos da (en disquete) un archivo con los cdigos del
+ Mac, nuestro LaTeX lo entender y lo procesar bien si lleva la
+ llamada a inputenc, dando el resultado correcto, aunque no podamos
+ ver correctamente el texto original con nuestro editor de texto.
+
+ Si queremos adems modificar el documento o simplemente ver bien o
+ simplemente ver bien el texto sin procesar original, necesitaremos
+ convertirlo a la pgina de cdigos que se utilice en nuestro
+ ordenador. Para ello recurriremos a GNU recode escribiendo:
+
+
+ recode applemac:latin1 archivo.tex
+
+
+
+ que nos convierte el documento de la pgina de cdigos applemac a la
+ latin1. Si ahora modificamos la lnea del inputenc para que ponga
+ latin1 en lugar de applemac todo funciona exactamente igual que antes
+ en cuanto al resultado. Magia! Dnde encontrar fuentes o binarios
+ precompilados de recode? En los siguientes lugares:
+
+
+ fuentes
+ En cualquier rplica del archivo GNU, en el directorio recode.
+
+ DOS
+ ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos_only o en el
+ mismo lugar en cualquier rplica del archivo simtel.
+
+ DOS32
+ ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/ o en el
+ mismo lugar en cualquier rplica del archivo simtel.
+ win32
+ http://www.weihenstephan.de/~syring/win32/UnxUtils.html
+
+ unix
+ En caso de no tener directamente binarios precompilados, suele
+ ser sencillo compilar el programa a partir de las fuentes para
+ cada sistema unix concreto.
+
+
+ 2. Para evitar problemas con el correo, siempre se puede convertir el
+ documento a formato LaTeX antes de mandarlo por correo. Despus de
+ todo, la mayora de lo que se escribe es para uno mismo, no para
+ mandarlo por correo. Ejemplo: Si alguien tiene un Mac, para enviar
+ algo por correo debe en primer lugar hacer una copia del documento
+ (pues GNU recode machaca el original). Con la copia se puede hacer:
+
+
+ recode -d applemac:latex archivo.tex
+
+
+
+ y ya podemos enviar el archivo.tex resultante por correo.
+
+ Supongamos que el receptor trabaja con Unix, tendra que escribir:
+
+
+ recode -d latex:latin1 archivo.tex
+
+
+
+ y cambiar el inputenc, en su caso.
+
+ En cualquier caso, si es posible, es mucho mejor enviar el archivo
+ directamente con acentos utilizando el estndar MIME con quoted-
+ printable, de esta forma llega el archivo con los acentos intactos an
+ usando los canales habituales de 7 bits. Naturalmente debemos ponernos
+ de acuerdo con el receptor del mensaje para que l tambin tenga un
+ programa que acepte MIME, pero dado que es un estndar, todo el mundo
+ debera acabar tenindolo.
+
+ Nota al margen: recode 3.4 no transforma correctamente de 850 a iso,
+ porque no convierte bien los retornos de carro. A partir de la versin
+ 3.4.1 se supone que lo hace correctamente. Si la versin de recode que
+ tenemos es la problemtica, se puede usar la opcin -a de unzip para
+ corregir los retornos de carro. Si nuestro documento no tiene
+ maysculas acentuadas, se puede usar la opcin ibmpc:l1 (ibmpc es
+ sinnimo de 437).
+
+
+ 6.4. Por qu cuando se selecciona texto en Adobe Reader o xpdf,
+ desde un documento PDF generado con LaTeX, las letras acentuadas y
+ ees no se copian bien?
+
+ El problema aparece cuando se utiliza un tipo de letra que no utiliza
+ la codificacin T1, y desaparece cuando se usa.
+
+
+ El tipo por omisin de LaTeX es el Computer Modern que no contiene
+ vocales acentuadas. Cuando el texto usa por ejemplo , LaTeX crea esta
+ letra juntando dos caracteres, una a y un acento agudo. El aspecto en
+ pantalla y en papel es el correcto, pero al seleccionar ese texto en
+ el Acrobat Reader, lo que se obtiene es la secuencia 'a.
+
+
+ Otros tipos de letra s contienen una letra , y si se usa este tipo y
+ se indica a LaTeX que use la codificacin T1, la seleccin de texto en
+ Reader ya funcionar bien. As que el problema se soluciona siguiendo
+ estos pasos:
+
+ Indicarle a LaTeX que use la codificacin T1. Esto se logra
+ mediante un \usepackage[T1]{fontenc}.
+
+ Disponer de una fuente que realmente use esa codificacin.
+
+ Si ponemos \usepackage[T1]{fontenc} sin ms en un documento,
+ entonces LaTeX cambia el tipo por omisin, y en vez de Computer
+ Modern, usar European Computer Modern (EC). Si este tipo est
+ instalado, el PDF se generar sin problemas y el asunto de
+ seleccionar texto quedar arreglado. Pero aparecer otro problema,
+ y es que normalmente los tipos EC que vienen instaladas en las
+ distribuciones de LaTeX vienen slo en formato PK, que es un
+ formato que despus se ve muy mal en el Reader (como borroso y
+ descolocado).
+
+ Para esto la solucin tpica sola ser usar el paquete ae, el cual
+ instala un tipo virtual, que aparentemente usa la codificacin T1
+ (para que LaTeX quede contento), pero que en realidad usa las fuentes
+ CM en vez de las EC (para poder usar los tipos postscript en vez de
+ los PK y as tener un PDF que se vea bien con el Reader). Sin embargo
+ esta solucin hace que el problema de la seleccin de texto
+ reaparezca, ya que, aunque desde el punto de vista de LaTeX los tipos
+ ae usan codificacin T1, la realidad es que en el PDF final no lo
+ usa, y la sigue siendo una combinacin de a y ' (como no poda ser
+ de otra forma, ya que la fuente CM no tiene el carcter ).
+
+ As que en este caso el truco de usar el paquete ae no sirve, y no
+ queda ms remedio que recurrir a un tipo que realmente use la
+ codificacin T1, como los tipos Postscript estndar (Times-Roman,
+ Palatino, etc.)
+
+ Existe una versin postscript de los tipos EC, cuyo desarrollo tiene
+ lugar junto al del lenguaje de descripcin musical lilypond y estn
+ disponibles en http://www.lilypond.org/download/fonts/. Asimismo los
+ tipos cm-super, disponibles en CTAN:fonts/ps-type1/cm-super/ tambin
+ aceptan la codificacin T1.
+
+ Resumiendo, la solucin es bien buscar y usar los tipos EC o alguno
+ que utilice la codificacin T1, o si no compensa el esfuerzo utilizar
+ directamente los tipos Postscript estndar. Para ello basta aadir al
+ prembulo del documento
+
+
+ \usepackage{times} % Usar tipo Times-Roman
+ \usepackage[T1]{fontenc} % Usar la codificacin T1
+
+
+
+ Con esto ya funcionar lo de cortar y pegar desde el Reader, aunque
+ utilizando otro tipo de letra con otra mtrica que puede cambiar la
+ maquetacin. En vez de times tambin pueden utilizarse palatino o
+ bookman, dependiendo de los gustos.
+
+
+ 6.5. Cmo cambiar los literales que produce LaTeX?
+
+ Cuando Lamport hizo el LaTeX original, proporcion una serie de
+ estilos estndar como ejemplo de uso. Estos estilos se hicieron muy
+ populares, principalmente porque todas las instalaciones de LaTeX los
+ tienen. Sin embargo, estos estilos utilizan unos convenios muy
+ particulares y es fcil que un usuario desee cambiarlos. Algo
+ especialmente molesto para el uso en castellano de los estilos
+ estndar, es que generan determinados ttulos (p.ej. Contents,
+ Bibliography, etc.) en ingls, lo que hace inaceptable su uso.
+
+ Aunque era posible crear versiones modificadas para otros idiomas, se
+ extendi la idea de internacionalizar dichos estilos. Por ejemplo,
+ donde pona la palabra Contents se ha cambiado por \contentsname y se
+ define aparte el valor de esta macro.
+
+ Esta es la forma en que funciona LaTeX2e actualmente. De esta manera,
+ es posible continuar usando los mismos estilos estndar en diferentes
+ idiomas, simplemente redefiniendo el valor de estas macros en el
+ documento o en un estilo aparte, por ejemplo con
+
+
+ \renewcommand{\contentsname}{Tabla de materias}
+
+
+
+ Un paquete de estilos que hace esto es babel -- Vase ``Qu es
+ babel?''. Cuando se quieren hacer estos cambios en un documento que
+ utiliza babel con spanish.sty hay que proceder de una forma un poco
+ distinta. Vase ``Modificando los literales de spanish.sty''
+
+
+ 6.6. Cmo hacer que LaTeX parta correctamente las palabras en
+ castellano?
+
+ 6.6.1. Qu configuraciones (o patterns) existen para la particin de
+ palabras?
+
+ Lo primero que hay que decir es que la particin en castellano es algo
+ mucho ms complejo de lo que pudiera parecer a simple vista. Aunque el
+ espaol es un lenguaje muy regular, tiene ciertas anomalas que
+ convierten este tema en un campo minado. Hay dos conclusiones bsicas:
+ 1) No es posible encontrar el 100% de los cortes legales y 2) no es
+ deseable. Para empezar, la Academia permite partir tanto por
+ componentes (sub-ur-ba-no) como silbicamente (su-bur-ba-no). Adems
+ el concepto de slaba es en algunos casos confuso y la etimologa
+ tampoco ayuda (Ej: su-bli-me, a pesar de derivar de sub-limis, contra
+ sub-li-mi-nal). Sin mencionar que los conceptos de diptongo e hiato
+ distan mucho de estar claros. Este ltimo caso viene a carecer de
+ importancia, pues libros de estilo consultados prescriben ignorar los
+ hiatos al partir palabras. El siguiente comentario de Fernando M.
+ Fournon Gonzlez-Barcia es interesante para ilustrar los problemas:
+
+ "La RAL dice que es POTESTATIVO lo de la separacin por pre-
+ fijos. Al menos en el esbozo, que si somos puristas y nos
+ atenemos a la nica gramtica vlida, la del 31, casi ni
+ eso."
+
+
+
+ "Creo que, estticamente, lo mejor es no partir nunca, salvo
+ cuando la cosa vaya a quedar muy fea (esta recomendacin
+ tambin la hace la RAL), como hace el LaTeX, y entonces par-
+ tir lo ms conservadoramente posible. Si para los poqusimos
+ casos en que un prrafo se pone pesado y en vez de partir
+ subur-bano hay que hacer sub-urbano, pues ..., que se haga a
+ mano, no?."
+
+
+
+ "Otra cosa es que al partir surjan vocablos malsonantes.
+ Esto S que debera de comprobarlo cualquier separador de
+ palabras, pues normalmente es muy difcil detectarlos a sim-
+ ple vista (si es que hay tiempo para releer nuestros propios
+ artculos). O sea, que antes que una lista de prefijos, sug-
+ erira la creacin de una lista de tacos y cacofonas
+ varias. :-)"
+
+
+ Es decir, lo mejor es evitar cualquier caso conflictivo en los
+ patrones (patterns) de uso general. Localmente puede hacerse los que
+ se quiera, usando excepciones o introducindolos a mano, por ejemplo.
+
+ Al da de hoy existen 4 tablas diferentes de particin:
+
+ Los producidos en 1986 por Armando Jinich, Mara Garza y Max Daz
+ de Aurion Tecnologa, Mxico. Estn en el dominio pblico desde
+ 1990. Pueden encontrarse en:
+
+ ftp://ftp.dante.de/tex-archive/language/spanish/old/sil-
+ aba.tex
+
+
+ Estos patrones han sido producidos a partir de las reglas de la
+ gramtica. Actualmente no soportan explcitamente acentos. Max Daz es
+ actualmente max _AT_ east.aurora.com
+
+ Los producidos por Manuel Vzquez de la Universidad de Zaragoza,
+ que puede ser localizado en (vazquez _AT_ cc.unizar.es). Estos
+ patrones estn basados en la gramtica.
+
+ Los que distribuye Arbortext producidos por Sistemas Grficos y
+ Audiovisuales de Chihuahua. Mxico. Estos estn generados a partir
+ de un diccionario. Soportan acentos.
+
+ Los producidos por Julio Snchez, que pueden obtenerse en:
+
+
+ CTAN:language/spanish/hyphen
+
+
+
+ Estos soportan una variedad de opciones, incluido el soporte de acen-
+ tos, tanto como ligaduras como con el cdigo IS 8859/1 (ISO Latin1)
+ para ML-TeX o TeX 3.X. Adems, son los actualmente recomendados por
+ CervanTeX.
+
+
+ 6.6.2. Cmo activo el patrn de particin de palabras para el
+ castellano?
+
+ Para activar el patrn de particin para el castellano es necesario
+ tener babel -- Vase ``Qu es babel?'' -- instalado y generar el
+ formato cargando el patrn de separacin en slabas en castellano.
+ Esto podemos hacerlo de la siguiente manera
+
+
+ Para TeX y LaTeX: Cambiando el archivo language.dat
+
+ Editar el archivo language.dat. Dependiendo de la
+ distribucin de TeX utilizada este archivo puede estar en
+ distintos lugares. Por ejemplo en teTeX el rbol de TeX parte
+ de TEXMF=/usr/share/texmf y el archivo en cuestin est en
+ TEXMF/tex/generic/config/language.dat. En al caso de
+ Debian/GNU-Linux, est en /etc/texmf/language.dat y el otro
+ es un enlace a ste.
+
+ Borrar el % que est al principio de la linea spanish. Si mal
+ no recuerdo viene preparado con silabeo en alemn, si no lo
+ quieren pongan un % adelante. Tambin viene predefinido
+ ingls (o alguna de sus variantes, por ejemplo american).
+ ste debe estar siempre definido as que no debe
+ desactivarse.
+
+ Es conveniente tambin verificar que la lnea con
+ nohyphenation est activada (sin el comentario). sto es muy
+ til cuando se quiere desactivar la particin de palabras.
+
+ En caso de tener el MikTeX, la operacin es la misma, pero el
+ archivo language.dat est en TEXMF\tex\generic\hyphen\local o
+ en TEXMF\tex\generic\config donde TEXMF representa el punto
+ del que parte el rbol de directorios TeX
+
+ teTeX tiene la utilidad texconfig que invocada como
+
+
+ # texconfig hyphen latex
+
+
+
+ lanza un editor para cambiar el fichero language.dat y que, al
+ cerrar el editor, genera los formatos automticamente, por lo
+ que no es necesario hacer el paso siguiente explcitamente.
+
+
+ Para LaTeX.
+ Una vez hecho lo anterior no es necesario ms que rehacer los
+ formatos -- Vase ``Cmo rehacer los formatos?'' --. Entonces
+ cuando se llame a babel con la opcin spanish, ste se encargar
+ de utilizar los patrones de guionado en castellano.
+
+
+ Para plain-TeX
+ Por omisin, cuando el initex crea el formato, carga el archivo
+ hyphen.tex que contiene las reglas de silabeo en ingls. Para
+ activarlo tambin en plain-TeX se debe copiar el archivo
+ hyphen.cfg como hyphen.tex en algn sitio que en el camino de
+ bsqueda de TeX est antes del hyphen.tex que viene como parte
+ de plain-TeX y asegurarse que existe el archivo ushyph1.tex (que
+ realmente es el mismo que el hyphen.tex original, pero con otro
+ nombre). Este paso no es necesario si slo se quiere la
+ particin de palabras para LaTeX y se va a utilizar babel, pero
+ tampoco sobra.
+
+ Para los usuarios de teTeX los archivos estn en
+ TEXMF/tex/config/babel/hyphen.cfg y el hyphen.tex original en
+ TEXMF/tex/generic/hyphen/hyphen.tex
+
+
+ Para los usuarios de MikTeX, los archivos estn en
+ TEXMF/generic/hyphen/hyphen.cfg y
+ TEXMF/generic/hyphen/hyphen.tex
+
+ En caso de no conseguirse hacer lo anterior tambin puede
+ sustituirse el archivo hyphen.tex por el hyphen.cfg, pero debe
+ tenerse cuidado al actualizar la distribucin de no
+ sobreescribir el hyphen.tex con al que venga con la distribucin
+ nueva.
+
+ Entonces es necesario reconstruir el formato como se indica en
+ ``Cmo rehacer los formatos?''.
+
+ Cuando se quiere usar el silabeo en castellano, hay que agregar
+ en el archivo .tex, al principio, una linea que diga \language1
+ si el castellano es el segundo lenguaje (no sinnimo) del
+ language.dat (\language0 correspondera al ingls americano)
+
+
+ 6.6.3. A pesar de que he activado los patrones de particin de pal-
+ abras del castellano, hay una palabra que se me resiste
+
+ Aunque los patrones de particin de palabras intentan abarcar el mayor
+ nmero de casos posible, siempre puede quedar alguna palabra
+ recalcitrante. Tambin puede ocurrir que la particin sea correcta,
+ pero no deseable a los ojos del autor del documento. En este caso hay
+ dos posibilidades:
+
+ Si la palabra es poco frecuente y slo falla en muy pocas
+ ocasiones. En este caso es preferible decirle directamente a la
+ palabra en el lugar donde aparece, dnde se le permite partirse,
+ mediante \-. Por ejemplo:
+
+
+ fotorrefractivo y electroptico --> foto\-rre\-frac\-tivo y elec\-tro\-ptico
+
+
+
+ Si es una palabra frecuente que es una potencial causa de problemas
+ en el documento. En este caso es preferible definir en el prembulo
+ del documento cmo se permite la particin de esta palabra de forma
+ global para todo el documento, mediante \hyphenation. Por ejemplo:
+
+
+ \hyphenation{foto-rre-frac-tivo,elec-tro-ptico}
+
+
+
+ 6.6.4. Mi TeX no parte las palabras que tienen acentos. Por qu?
+
+ El primitivo \accent detiene la particin. Es posible ayudar a TeX
+ invocando la siguiente macro despus de un acento:
+
+
+ \def\allowhyphens{\penalty10000 \hskip0pt}
+
+
+
+ spanish.sty lo hace automticamente en caso necesario. En cualquier
+ caso, lo mejor es usar fuentes con las letras acentuadas como por
+ ejemplo las descritas en ``DC/EC'', o ML-TeX, y patrones de particin
+ que contemplen esto.
+
+
+ 6.7. Acerca de spanish.sty
+
+ Los archivos para escribir en castellano con babel (spanish.*) los
+ cre y mantuvo durante mucho tiempo Julio Snchez. Ahora esos archivos
+ los mantiene Javier Bezos y desde hace tiempo son oficiales en la
+ estructura de babel. Es posible que alguna distribucin de LaTeX an
+ utilice los archivos antiguos y que haya algunas diferencias respecto
+ de lo que aqu se describe. La actualizacin est ms que recomendada.
+
+ 6.7.1. Dnde se puede obtener la documentacin de spanish en castel-
+ lano?
+
+ La documentacin de spanish que se incluye al componer user.drv est
+ en ingls, pero el archivo spanish.dtx tambin la incluye en
+ castellano. Basta con componer este archivo y obtendremos un detallado
+ manual como spanish.dvi.
+
+ La versin ms reciente del manual de spanish.sty se encuentra en
+ http://perso.wanadoo.es/jbezos/archive/spanish.pdf. Debe tenerse
+ cuidado con las versiones, pues puede referirse a una versin muy
+ posterior a la que se encuentra instalada en el sistema.
+
+
+ 6.7.2. Cmo cambio los nombres de las secciones de bibliografa,
+ ndice, etc... que pone spanish.sty ?
+
+ Si no importa que este cambio no siga las caractersticas de babel y
+ spanish de cambio de idioma sobre la marcha, etc.., se puede hacer de
+ la misma forma que en la seccin ``Cmo cambiar los literales que
+ produce LaTeX?'' poniendo las definiciones despus de llamar a babel.
+ El problema de este mtodo es que no est bien integrado con babel y
+ por ese lado puede dar problemas, ya babel activa algunos cambios al
+ llegarse al \begin{document}.
+
+ Si embargo existe una forma ms elegante e integrada con spanish y
+ babel. En el prembulo del documento hay que aadir lo siguiente, por
+ ejemplo, para cambiar Bibliografa por Referencias y Tabla por Cuadro
+
+
+ \addto\captionsspanish{%
+ \def\bibname{Referencias}%
+ \def\tablename{Cuadro}%
+ }
+
+
+
+ Y as con todos los nombres necesarios. La lista de nombres est en
+ los dos lugares siguientes
+
+
+ TEXMF/tex/generic/babel/spanish.ldf
+ TEXMF/tex/generic/babel/spanish.tex
+
+
+
+ Nunca deben modificarse los ficheros spanish.ldf y spanish.tex direc-
+ tamente, ya que el documento resultante ya no sera universal, al
+ procesarlo en un sistema distinto dara distinto resultado, y no sera
+ posible acompaar el documento original con los archivos de estilo
+ modificados puesto que la LPPL (la licencia bajo la que se distribuye
+ LaTeX) no permite la distribucin de versiones modificadas de stos
+ bajo el mismo nombre.
+
+
+ 6.7.3. Por qu spanish.sty pone los meses en minscula?
+
+ Ese es el uso aceptado en la actualidad. Documentos de la propia RAL
+ lo hacen as. El Mara Moliner tambin. Vase la siguiente cita del
+ Mara Moliner, 1990,
+
+ "7. Aunque entre los preceptos de la G.R.A. figura el de
+ escribir con mayscula los nombres de los meses, de los das
+ de la semana y de las estaciones, [...] ha dejado
+ decididamente de usarse la letra mayscula en uno y otro de
+ estos casos"
+
+
+
+ 6.7.4. Por qu el spanish de babel reemplaza el punto decimal por
+ una coma?
+
+ Por tres razones: 1) porque las normas internacionales establecen que
+ ha de usarse coma para los decimales, excepto en aquellos pases cuya
+ tradicin hace preferible el punto (la propia ISO usa coma en sus
+ informes); 2) porque el punto decimal en Espaa carece de fuerza legal
+ y slo la coma es oficialmente vlida, y 3) porque la coma es el nico
+ signo usado en la vida diaria. Probablemente, la situacin es similar
+ en otros pases, salvo Mxico.
+
+ Se puede cambiar el comportamiento predefinido con la orden
+ \decimalpoint o \spanishdecimal{.} en el prembulo, despus de cargar
+ babel. En unas pocas materias, como el anlisis nmerico o la
+ estadstica, es necesario distinguir la coma decimal de la coma para
+ separar datos; en este caso se puede aumentar el espaciado de estas
+ ltimas con:
+
+
+ \makeatletter
+ \def\es@decimal{{\mathchar"613B}}
+ \mathcode`,="8000
+ \begingroup
+ \catcode`,=13
+ \gdef,{\mkern2mu\mathchar"613B\mkern8mu}
+ \endgroup
+ \makeatother
+
+
+
+ (Se pueden probar otros valores en lugar de 2 [antes] y 8 [despus].
+ La unidad mu de TeX es para matemticas [aprox. 1/18 em].)
+
+
+ 6.7.5. Por qu spanish.sty pone los nmeros romanos siempre en
+ mayscula?
+
+ Realmente no son maysculas, sino versalitas (small caps). En la
+ tradicin tipogrfica espaola no se utilizan los nmeros romanos en
+ minsculas, que se sustituyen por las versalitas. Por este motivo, el
+ autor de spanish para babel, lo ha incluido en ste.
+
+
+ 6.7.6. Por qu spanish.sty acenta la I de ndice?
+
+ As lo han sostenido los tratadistas ms importantes sobre ortografa
+ y tipografa desde hace ms de un siglo: << La maysculas deben llevar
+ la tilde que les corresponda >> (Sanmart, 1907). La RAE finalmente lo
+ ha considerado normativo en su ortografa de 1999: <<El empleo de las
+ maysculas no exime de poner tilde cuando as lo exijan las reglas de
+ acentuacin >> (p. 31).
+
+
+ 6.7.7. Por qu spanish para babel dice cuadro en lugar de tabla?
+
+ Tal y como se indica en el manual, el ingls table y el espaol tabla
+ son falsos amigos. Para ser ms precisos, podemos reproducir lo que
+ dice el Diccionario acadmico:
+
+
+ Cuadro [...] 10. m. Conjunto de nombres, cifras u otros
+ datos presentados grficamente, de manera que se advierta la
+ relacin existente entre ellos.
+
+ Tabla [...] 12. f. Cuadro o catlogo de nmeros de especie
+ determinada, dispuestos en forma adecuada para facilitar los
+ clculos. Tabla de multiplicar, de logaritmos, astronmica.
+
+
+ El ingls table tiene un sentido mucho ms general que el que tiene el
+ espaol tabla, y as tendramos tabla de logaritmos y tabla de multi-
+ plicar frente a cuadro de reyes medievales y cuadro de aminocidos
+ esenciales. En este aspecto el espaol tiene ms riqueza y precisin
+ que el ingls.
+
+ En fin, cuadro es todava la forma ms frecuente, la ms castellana y
+ tradicional, y la preferida por los mejores tipgrafos (Morato,
+ Martnez Sicluna, Martnez de Sousa, etc.). Nada impide, por supuesto,
+ redefinir el nombre si resultara que todos los cuadros de un documento
+ son tablas, tal y como describe el manual y esta FAQ.
+
+
+ 6.7.8. Cmo consigo que babel y spanish.sty no utilicen los atajos
+ de teclado NUNCA?
+
+ Este ha sido un problema muy frecuente con babel y spanish, que ha
+ dado como consecuencia que, por ejemplo, en las bibliografas nombres
+ como "J.N. Apellido" aparecieran como "J.. Apellido". Para
+ solucionar este problema, spanish ofrece ahora la orden
+ \deactivatetilden que elimina el uso de ~ para la ee, al tiempo que
+ preserva su funcin de espacio sin divisin (la orden \shorthandoff de
+ babel cancela ambos usos). El estilo spanish tambin proporciona ms
+ facilidades para desactivar otras abreviaciones, que estn descritas
+ en spanish.dtx, por ejemplo \deactivatequoting en el prembulo.
+
+ Sin embargo sto y el que funcione correctamente ha cambiado mucho
+ entre distintas versiones de babel lo que hace que a veces los
+ documentos creados con una versin de babel no sean directamente
+ portables a otros sistemas. Aunque es recomendable actualizarse a la
+ ltima versin de spanish y babel en todos los ordenadores implicados,
+ en caso de no poderse hacer, la siguiente lnea (en LaTeX2e) en el
+ prembulo del documento elimina los atajos de teclado
+
+
+ \AtBeginDocument{\gdef~{\nobreakspace{}}\catcode`\"=12}
+
+
+
+ til para documentos que se utilizarn en distintos ordenadores,
+ alguno de ellos con versiones antiguas de babel o spanish.
+
+
+ 6.8. Cmo puedo indicar la abreviatura de los ordinales?
+
+ En LaTeX2e pueden utilizarse la rdenes \textordfeminine y
+ \textordmasculine; por ejemplo, para abreviar Mara, escribimos
+ M.\textordfeminine. Una variacin de estas macros ha sido incorporada
+ a spanish.sty versin 3.0 y extendida en la versin 4.0. Se invocan
+ como "a y "o, respectivamente, con la posibilidad de usar \sptext para
+ casos como 1\sptext{er}.
+
+
+
+ 6.9. Cmo forzar sangra despus de las cabeceras?
+
+ El objetivo de esa sangra (indentation para los que no estn al
+ tanto) es marcar claramente la separacin de los prrafos. Como tal,
+ es superflua despus de una cabecera. Hay otros sitios en los que, no
+ slo es superflua, sino que es confusa, como despus de un texto que
+ ya va sangrado (entorno quote, \[ \], un array, etc.) Sin embargo, es
+ esencialmente una cuestin de gusto.
+
+ Modificarlo en un estilo es bastante fcil. La mayora de las
+ secciones, etc. en LaTeX son algo as como (en art10.sty):
+
+
+ \def\section{\@startsection {section}{1}{\z@}{-3.5ex plus
+ -1ex minus -.2ex}{2.3ex plus .2ex}{\Large\bf}}
+ \def\subsection{\@startsection{subsection}{2}{\z@}{-3.25ex plus
+ -2ex minus -.2ex}{1.5ex plus .2ex}{\large\bf}}
+
+
+
+ El cuarto parmetro, si es negativo, indica que no se debe sangrar en
+ el primer prrafo tras la cabecera. Cmbiese a positivo.
+
+ Hay otro procedimiento para estilos que ya estn escritos y consiste
+ en decir:
+
+
+ \let\@afterindentfalse\@afterindenttrue
+ \@afterindenttrue
+
+
+
+ Esta solucin es la proporcionada en indentfirst.sty por David
+ Carlisle.
+
+
+ 6.10. Cmo puedo escribir las funciones matemticas en espaol?
+
+ Comentario: Hay gente que discute el que las funciones vayan en
+ espaol y lleve acento el lm, mx, etc. Argumentan que los nombres
+ vienen del latn y all no haba acentos (y que en ingls tambin
+ vienen del latn, lo cual, por ejemplo, es claramente incierto con
+ gcd). El caso es que en todos los libros tradicionales en castellano
+ se escriba lm y mx con acento. Si ltimamente no se hace es
+ precisamente porque TeX (en ingls) no lo tiene as. Todava estamos a
+ tiempo de no cometer ese error:
+
+ El caso ms comn es el del seno que, en plain TeX, basta definirlo
+ como
+
+
+ \def\sen{\mathop{\rm sen}\nolimits} % Sustituye a \sin
+
+
+
+ Anlogamente,
+
+
+
+ \def\mcd{\mathop{\rm mcd}\nolimits} % Sustituye a \gcd
+
+ \def\senh{\mathop{\rm senh}\nolimits} % Sustituye a \sinh
+
+ \def\arcsen{\mathop{\rm arcsen}\nolimits} % Ni el arcsin ni el
+ % arccos originales dejan espacio entre arc y sin o cos.
+
+
+
+ Cuando la funcin en espaol tiene algn acento (sobre todo en la i),
+ es ms complicado:
+
+
+ \def\max{\mathop{\rm m\acute ax}}
+
+ \def\min{\mathop{\rm m\acute\mathchar"7010n}}
+
+ \def\inf{\mathop{\rm \acute\mathchar"7010nf}}
+
+ \def\lim{\mathop{\rm l\acute\mathchar"7010m}}
+
+ \def\limsup{\mathop{\rm l\acute\mathchar"7010m\, sup}} % El limsup
+ % y el liminf originales dejan espacio entre lim y sup o inf.
+
+ \def\liminf{\mathop{\rm l\acute\mathchar"7010m\, inf}}
+
+
+
+ Por ltimo, adaptndolas de su definicin original (ver pg. 361 del
+ TeXbook) para poner el acento en las dos posibilidades de uso de mod
+ hacemos:
+
+
+ \def\bmod{\mskip-\medmuskip \mkern5mu
+ \mathbin{\rm m\acute od} \penalty900 \mkern5mu
+ \mskip-\medmuskip}
+ \def\pmod#1{\allowbreak \mkern18mu ({\rm m\acute od}\,\,#1)}
+
+
+
+ En LaTeX se puede hacer de forma similar pero usando \newcommand o
+ \renewcommand en lugar de \def.
+
+
+ 6.11. Qu verificadores ortogrficos puedo utilizar para espaol?
+
+
+ ispell
+ ispell es un verificador ortogrfico de uso libre que funciona
+ en UNIX, aunque hay un port para emx en fase beta --que funciona
+ o debe funcionar tanto en DOS (con 386 o superior) como en OS/2
+ 2.x o en OS/2 Warp.
+
+ Para ispell existe lo siguiente:
+
+
+ Ficheros de afijos para espaol:
+
+ URL: ftp://ftp.dante.de/tex-archive/language/spanish/ispell
+ ARCHIVO: castellano.aff.gz
+ COMENTARIOS: diccionario y parche elisp disponible en el mismo lugar.
+ Vanse los archivos LEEME o README.
+
+ URL: http://www.datsi.fi.upm.es/~coes
+ ARCHIVOS: espa~nol.tar.gz
+ COMENTARIOS: incluye espa~nol.aff, lista de palabras,instrucciones
+ y patrones de guionado para TeX en espaol.
+
+
+ Diccionarios compatibles con ispell:
+
+ URL: ftp://ftp.dante.de/tex-archive/language/spanish/ispell
+ ARCHIVOS: palabras.sq.gz
+ COMENTARIOS: archivo de afijos y parche elisp disponible en el mismo
+ lugar. Vanse los archivos LEEME o README.
+
+
+
+ URLs: http://www.datsi.fi.upm.es/~coes
+ ARCHIVOS: espa~nol.tar.gz
+ COMENTARIOS: incluye espa~nol.aff, lista de palabras,instrucciones,
+ y patrones de guionado para TeX en espaol.
+
+
+ El que hay en ftp.dante.de es de Julio Snchez y el que hay en
+ http://www.datsi.fi.upm.es/~coes es de Santiago Rodrguez srodri
+ _AT_ fi.upm.es y Jess Carretero jesus _AT_ fi.upm.es
+
+ Dependiendo de como se haya creado el diccionario de castellano
+ es posible que deba llamarse a ispell como
+
+
+ ispell -t -T latin1 -d espanol fichero.tex
+
+
+
+ especificando explcitamente la codificacin.
+
+
+ Excalibur
+ Para Macintosh, existe un verificador ortogrfico de documentos
+ LaTeX (y plain TeX) llamado Excalibur. Es gratis, aunque el
+ copyright es del autor, Rick Zaccone (zaccone _AT_
+ bucknell.edu).
+
+ Excalibur puede conseguirse por ftp annimo en
+ ftp://sol.eg.bucknell.edu/pub/mac.
+
+ Juan Luis Varona (jvarona _AT_ dmc.unirioja.es) ha creado un
+ diccionario con 292342 palabras (versin de septiembre de 1999)
+ que funciona con Excalibur. Est realizado en formato de 7 bits,
+ y la la reconoce nicamente como \'{\i}. Pero puede
+ modificarse si se desea. La versin ms reciente puede
+ encontrarse en ftp://tex.unirioja.es/pub/tex/dict-mac
+
+ Asimismo, en la direccin mencionada para Excalibur, en el
+ directorio Excalibur-dictionaries, se encuentran disponibles los
+ diccionarios de los distintos idiomas. El diccionario espaol
+ puede encontrarse tambin en CTAN en
+
+
+ CTAN:systems/mac/support/excalibur/Spanish_Dictionary.sit.hqx
+
+
+
+ 4spell
+ 4spell es un verificador ortogrfico para Windows (32 bits) que
+ se distribuye bajo una licencia libre (concretamente la GPL) y
+ tiene un diccionario de castellano. Puede encontrarse en
+ CTAN:support/4spell
+
+ Winedt
+ El diccionario de Juan Luis Varona tambin se ha adaptado para
+ su uso con el verificador ortogrfico del entorno winedt para
+ Windows. Est disponible en
+
+ ftp://tex.unirioja.es/pub/tex/dict-win
+
+
+ amspell
+ amspell es un verificador ortogrfico para DOS. El diccionario
+ de Juan Luis Varona tambin se ha adaptado para ser utilizado
+ con amspell. La versin para amspell est disponible en
+
+ ftp://tex.unirioja.es/pub/tex/dict-pc
+
+
+ y amspell en
+
+
+ CTAN:support/amspell
+
+
+
+ 6.12. Cmo utilizo BibTeX en castellano?
+
+ Para esto hay dos aproximaciones,
+
+ 6.12.1. Utilizar estilos adaptables (los abstyles )
+
+ Para que BibTeX funcione en espaol, Toms Bautista ha modificado con
+ babel una familia adaptable de estilos de BibTeX (tambin llamadas
+ abstyles).
+
+ Con las abstyles se tiene la ventaja de utilizar un nico estilo, de
+ forma que el idioma de las referencias nicamente depende del elegido
+ con babel. De este modo, si por h o por b, en cierto momento no se
+ quiere el documento en ingls, sino por ejemplo en espaol o en
+ alemn, slo habra que cambiar la opcin que corresponde en babel y
+ no tambin el estilo puesto dentro del \bibliographystyle{estilo}.
+
+ Adems, con las abstyles slo es necesario un aplain.bst preparado
+ para distintos idiomas, segn lo elegido en babel. Estn disponibles
+ en CTAN:biblio/bibtex/contrib/abstyles-babel/.
+
+ 6.12.2. Utilizar el paquete custom-bib
+
+ El paquete custom-bib (disponible en
+ CTAN:macros/latex/contrib/supported/custom-bib/) permite crear estilos
+ bibliogrficos a medida, con una amplia serie de opciones y de
+ idiomas. Para utilizarlo, una vez desempaquetado debe hacerse
+
+
+ latex makebst.tex
+
+
+
+ y responder a las (muchas) preguntas que se formulan. Es conveniente
+ leerse previamente la documentacin para ser consciente de qu se est
+ preguntando en cada momento, ya que muchas de las preguntas no son
+ obvias. El documento de Luis Seidel -- Vase la seccin ``Tutoriales
+ en castellano'' -- es una ayuda interesante al respecto.
+
+ El paquete spanish proporciona el fichero esbst.tex que es el que debe
+ usarse como babelbst.tex para las adaptaciones al castellano. Si la
+ distribucin es antigua, este fichero puede estar prcticamente vaco
+ y tener como nico efecto que no aparezca un mensaje de error. En este
+ caso es conveniente copiar el archivo esbst.tex de una versin
+ reciente de spanish al directorio donde se va a utilizar el estilo
+ .bst, con el nombre babelbst.tex, ya que es el nombre con que lo
+ espera el estilo .bst creado.
+
+ 6.13. Cmo genero un ndice alfabtico con la ordenacin correcta en
+ castellano?
+
+ El problema con que uno se encuentra al utilizar makeindex es que no
+ ordena correctamente las palabras con caracteres acentuados, ya que
+ por ejemplo ordena la como \'a que es lo que TeX escribe al archivo
+ de ndice y salvo que fuera la ms reciente versin de makeindex de 8
+ bits ni siquiera las reconocera si estuvieran escritas directamente
+ al archivo de ndice como palabras acentuadas. A pesar de las
+ limitaciones mencionadas para los idiomas que no pueden describirse
+ mediante la tabla de caracteres de 7 bits, es posible utilizar
+ makeindex en idiomas como el castellano. Para solucionar este problema
+ hay varias aproximaciones:
+
+ Decir a makeindex cmo debe ordenar la palabra acentuada
+ Por ejemplo, para los acentos o para la se introducira la
+ entrada al ndice como
+
+
+ \index{optica@ptica}
+ \index{indice@ndice}
+ \index{can^^ffa@caa}
+
+
+
+ y para una palabra compuesta como por ejemplo en
+
+
+ \index{optica electromagnetica@ptica electromagntica}
+
+
+
+ Utilizar el paquete esindex
+ esindex es un paquete desarrollado por Javier Bezos para
+ facilitar la escritura de ndices correctamente alfabetizados en
+ castellano. Su nica orden es \esindex que convierte su
+ argumento a una forma adecuada. Por ejemplo,
+
+
+ \esindex{ca'n'on}
+
+
+
+ equivale a
+
+
+ \index{can^^ffon@ca'n'on}
+
+ Es necesario usar babel y que los acentos estn escritos en forma
+ de abreviaciones ('a, 'e, etc.). El paquete utiliza ciertas rdenes
+ internas de babel por lo su funcionamiento puede cambiar con ver-
+ siones distintas a la 3.6.
+
+ Hay que sealar que con este paquete no se crea en el ndice una
+ entrada propia para la palabras que empiezan por ee, sino que tan
+ slo se aaden al final de la ene. En el rarsimo caso de que
+ hubiera palabras que empiezan por ee habra que modificar el
+ archivo .ind a mano. Este paquete puede encontrarse en
+
+
+ CTAN:macros/latex/contrib/supported/bezos/
+
+
+
+ Utilizar xindy
+ xindy es un sistema de indexacin desarrollado por Roger Kehr,
+ del Instituto de Informtica Terica de Darmstadt, que puede
+ ser configurado fcilmente para adaptarse a las normas
+ ortogrficas de distintos idiomas, cada uno de ellos con un
+ alfabeto distinto y con unas reglas de ordenacin tambin
+ distintas. xindy puede definir, para cada carcter del alfabeto,
+ dnde debe ser ste ordenado (reglas de ordenacin), as como a
+ qu carcter o cadena es equivalente (reglas de equivalencia).
+ Permite incluso definir reglas de ordenacin de distinto nivel
+ que pueden ser aplicadas de forma sucesiva. Este paquete puede
+ encontrarse en /CTAN:indexing/xindy/ y su pgina web est en
+
+ http://www.iti.informatik.tu-darmstadt.de/xindy/
+
+
+ Existen unos archivos de estilo para utilizar xindy en castellano
+ en la pgina anterior y la versin ms reciente, incluyendo bina-
+ rios para linux se puede encontrar en el directorio
+ http://www.aq.upm.es/~agmartin/linux/store/xindy, con tgz para
+ libc5 (xindy-2.0.1.tgz) y libc6 (xindyg21-2.1.tgz) Uno de los esti-
+ los (es-mkidx.xdy) ordena segn las reglas modernas del castellano
+ mientras que el otro (es-tridx.xdy) ordena segn las reglas ya
+ obsoletas, con ch y ll. Su uso es algo distinto del habitual en
+ makeindex
+
+
+ xindy -f tex2xindy estilo.xdy tu_archivo.idx
+
+
+
+ donde tex2xindy es un filtro que convierte sobre la marcha del for-
+ mato habitual de los .idx al formato especial que utiliza xindy,
+ estilo.xdy puede ser cualquiera de los dos mencionados (u otro
+ cualquiera para otro idioma o particularizado por el autor del doc-
+ umento) y tu_archivo.idx es el que crea LaTeX a partir de las lla-
+ madas a \index.
+
+
+ 7. Que es...?
+
+ 7.1. Qu es el CTAN ( Comprehensive TeX Archive Network ).
+
+ Son las abreviaturas de Comprehensive TeX Archive Network (Red del
+ Archivo Completo de TeX). Son tres servidores de FTP que almacenan
+ prcticamente todo lo relacionado con el TeX. Sus nodos son:
+
+ ftp.dante.de (Alemania)
+
+ ftp.tex.ac.uk (Reino Unido)
+
+ ftp.shsu.edu (Estados Unidos)
+
+ Tambin se puede acceder mediante gopher o WWW con otros nombres, y
+ existen interfaces de acceso como
+
+ http://www.ucc.ie/cgi-bin/ctan
+
+
+ que muestra una serie de rplicas del CTAN, y permite hacer bsquedas
+ en ellas.
+
+ En los tres casos el material de TeX est en el directorio /tex-
+ archive. Cada uno es un mirror o rplica de los otros dos: Los tres
+ contienen lo mismo (con un da de diferencia a lo ms, en teora).
+ Por lo tanto conviene conectarse al que que nos caiga ms cerca. Dado
+ que siempre hay que ir a /tex-archive, se puede omitir dicho
+ directorio y darse por supuesto. Por ejemplo, si alguien nos dice que
+ LaTeX se encuentra en CTAN:macros/latex quiere decir que podemos
+ encontrarlo por ejemplo en el directorio
+
+
+ ftp://ftp.dante.de/tex-archive/macros/latex
+
+
+
+ Nota: Desde hace tiempo, ftp.shsu.edu funciona tan mal que los man-
+ tenedores del CTAN han decidido (20 de junio de 1996) no considerarlo
+ ya ms un nodo del CTAN. Para los usuarios de Amrica, se recomienda
+ usar la siguiente rplica:
+
+ ftp://ftp.cdrom.com/pub/tex/ctan
+
+
+ En Espaa existe una rplica del CTAN en
+
+ ftp://ftp.rediris.es/mirror/tex-archive
+
+
+ aunque no se actualiza con la misma rapidez que los nodos del CTAN.
+
+
+
+ 7.2. Qu es el esquema de codificacin de Cork?
+
+ Es el cdigo acordado en la reunin del TUG 1990 en Cork, el llamado
+ TeX 256 international character set que es, al menos en lo que se
+ refiere al castellano, compatible con ML-TeX, ISO Latin Alphabet 1 (IS
+ 8859/1) y el DEC Multinational Character Set. Que adems, es el de las
+ fuentes DC/EC. Esto significa que es posible utilizar en entrada los
+ caracteres acentuados directamente (por ejemplo con compose en Sun o
+ terminales VTxxx (xxx >= 200).
+
+
+ 7.3. Qu es babel?
+
+ Babel es un conjunto de estilos escritos por Johannes L. Braams que:
+
+ Proporciona macros tiles para la produccin de documentos en una
+ veintena de idiomas, incluido el espaol.
+
+
+ Pblico y en evolucin. Esto significa la posibilidad de enviar
+ documentos a otros sin tener que intercambiar macros primero y que
+ estas macros se actualizan en funcin de las necesidades.
+
+ La posibilidad de cambiar de idioma a mitad de documento, para, por
+ ejemplo, citar en otro idioma y tener disponibles las macros
+ especficas de ese idioma.
+
+ Puede ser utilizado en plain TeX tambin.
+
+ Adems, babel convive cmodamente con otros estilos. Por ejemplo,
+ artikel1.sty usa parte de la ayuda de babel. Es fcil escribir
+ estilos que combinen con babel. Si tu estilo lo escribes usando
+ para los literales las macros que babel define, lo tendrs sin
+ ningn esfuerzo adicional para una veintena de idiomas. Es cierto
+ que la probabilidad de que uses serbo-croata es escasa, pero hay
+ francs, portugus, italiano, alemn, etc. Los convenios de babel
+ derivan del trabajo realizado por Hubert Partl. Estilos escritos de
+ forma compatible con el trabajo de Partl, deben funcionar con babel
+ en principio. De hecho, es ya estndar este convenio en las
+ versiones de LaTeX posteriores a octubre de 1991.
+
+ Babel puede conseguirse en:
+
+
+ CTAN:languages/babel
+
+
+
+ 7.4. Qu son eTeX, eLaTeX y omega ?
+
+ eTeX es una extensin de TeX con nuevas primitivas y algunas
+ correcciones en el cdigo de TeX para mejorar (an ms si cabe) sus
+ capacidades tipogrficas. Es slo un paso intermedio para NTS, que
+ ser el nombre definitivo. eLaTeX es una versin de LaTeX para eTeX,
+ que en realidad es exactamente igual en su funcionamiento, slo que
+ los archivos de formato de TeX y eTeX no son compatibles.
+
+ omega es similar en concepto, aunque distinto en realizacin, ya que
+ utiliza preprocesadores integrados con TeX. Adems, funciona con
+ unicode y permite escribir en cualquier lengua conocida (o por
+ conocer). lambda es una versin de LaTeX para omega, y se puede decir
+ lo mismo que sobre eLaTeX.
+
+ Ambas son prescindibles si slo quieres usar TeX; pero ambas son
+ imprescindibles si quieres ir ms all en tipografa.
+
+
+ 7.5. Qu es RevTeX?
+
+ RevTeX es un conjunto de macros y estilos en LaTeX realizado por la
+ Sociedad Americana de Fsica, la Sociedad Americana de ptica, y el
+ Instituto Americano de Fsica. Sirve para componer artculos y
+ resmenes para muchas revistas de estas sociedades y algunas otras.
+ Las ventajas son las de LaTeX (texto en ASCII que puede enviarse por
+ e-mail y entre distintas plataformas, archivos reducidos, ms
+ importancia al contenido y la estructura que a la esttica, frmulas
+ matemticas impecables, manejo sofisticado de referencias y citas,
+ etc.) y las de estar especficamente desarrollado para artculos de
+ una revista cientfica. As, es muy fcil preparar preprints que se
+ asemejan mucho al resultado final y donde es muy fcil calcular el
+ nmero de pginas. Es inmediato preparar separatas en formato PDF.
+
+
+ Debe procurarse utilizar al menos la versin RevTeX 4, ya que RevTeX
+ 3.1 no es del todo compatible con LaTeX (hay que modificar algo las
+ tablas, por ejemplo).
+
+ Se puede encontrar ms informacin en la pgina Web del Instituto
+ Americano de Fsica (en la seccin de publicaciones, programa
+ Compuscript)
+
+ http://www.aip.org
+
+
+
+ 7.6. Qu es una box y cundo conviene utilizarlas?
+
+ Realmente esta es una pregunta ms especializada. Una box es una forma
+ de guardar informacin para reutilizarla despus. Por ejemplo, se
+ podra guardar un logo con informacin con
+
+
+ \newsavebox{\logo}
+ \sbox{\logo}{\includegraphics{logo.eps}}
+
+
+
+ y luego utilizarla con \usebox{\logo}. La diferencia con usar
+
+
+ \newcommand{\logo}{\includegraphics{logo.eps}}
+
+
+
+ y luego poner \logo cada vez que se utilice es la siguiente:
+
+ Lo que hay en un box ya est hecho y compuesto. Lo que hay en una
+ macro son ordenes que se ejecutan cuando se usa la macro, y por tanto
+ no se componen hasta ese momento. Cuando es necesario utilizar muchas
+ veces la definicin sale ms rentable usar un savebox ya que el
+ recuadro usado contiene siempre exactamente lo mismo y de esta forma,
+ no se llama a \includegraphics en cada pagina, sino tan solo una vez.
+ Sin embargo, una box no admite argumentos como lo hace una macro.
+
+
+ 8. Cmo hago ...?
+
+ 8.1. Cmo y dnde instalo nuevos paquetes o archivos de estilo?
+
+ Este proceso constar en general de los pasos que se describen a
+ continuacin: traer el nuevo paquete, extraer los ficheros de estilo
+ si es necesario, colocarlos en el sitio apropiado y rehacer la base de
+ datos.
+
+
+ 8.1.1. Dnde buscar un paquete nuevo y qu traer
+
+ Normalmente los paquetes nuevos se encontrarn en el ``CTAN'', aunque
+ en ocasiones estarn en otros lugares. En general, se debe descargar
+ el directorio completo del paquete o el archivo comprimido que lo
+ contiene. Esto no es necesario cuando se quiere descargar un archivo
+ de estilo de uno de los directorios misc, que tienen contribuciones al
+ CTAN en forma de archivos de estilo individuales completos en s
+ mismos. En este caso bastara con descargar el archivo individual
+ correspondiente.
+
+ 8.1.2. Qu es cada uno de los archivos que traigo?
+
+ Un paquete pequeo puede estar compuesto nicamente de un archivo de
+ estilo .sty (por ejemplo paquete.sty) con las instrucciones de uso
+ incluidas como comentarios en el mismo, en un archivo separado o bien
+ en un archivo README.
+
+ Sin embargo, es ms frecuente encontrar el paquete en forma de un par
+ de archivos paquete.ins y paquete.dtx, escritos para ser utilizados
+ con el sistema doc de LaTeX. Los archivos de estilo deben extraerse de
+ stos. Si hay un README adicional debe leerse ste previamente.
+
+
+ 8.1.3. Extrayendo archivos de estilo de los .dtx y .ins
+
+ En el sistema doc el manual de usuario y el cdigo del paquete
+ documentado se encuentran en el archivo .dtx, mientras que el archivo
+ .ins contiene instrucciones LaTeX acerca de la extraccin del cdigo
+ del archivo .dtx. Para extraer los distintos archivos debe seguirse el
+ siguiente procedimiento:
+
+ Correr LaTeX sobre paquete.ins. Esto extraer uno o ms archivos
+ (normalmente un paquete.sty, pero dependiendo del paquete pueden
+ generarse ms archivos).
+
+ Correr LaTeX sobre paquete.dtx para obtener el manual de usuario y
+ posiblemente una versin comentada del cdigo del paquete.
+
+ Correr de nuevo LaTeX sobre paquete.dtx. sto resolver las
+ referencias y generar una tabla de materias si el archivo original
+ lo pide as.
+
+ Si LaTeX da el error "No file paquete.ind" significa que no
+ encontr el archivo fuente para el ndice de rdenes. Para generar
+ el ndice basta hacer
+
+
+ makeindex -s ind.ist paquete
+
+
+
+ y correr de nuevo LaTeX.
+
+ Imprimir y leer paquete.dvi.
+
+ A veces se proporciona el manual de usuario separadamente del
+ archivo .dtx. En este caso es recomendable procesarlo despus de
+ hacer lo anterior, ya que puede necesitar elementos del paquete que
+ est describiendo.
+
+
+ 8.1.4. Dnde colocar nuevos archivos de estilo?
+
+ En primer lugar TeX buscar archivos en el directorio actual. Salvo
+ que se trate de una prueba o de archivos muy relacionados con el
+ documento que se est preparando, es conveniente colocarlos en un
+ lugar de acceso ms general.
+
+ El lugar exacto en el que deben colocarse los nuevos archivos de
+ estilo depende de la distribucin TeX que se est utilizando.
+ Asumiendo que se utiliza una de las distribuciones modernas que son
+ conformes al TDS (por ejemplo, teTeX, fpTeX o mikTeX) hay una serie de
+ normas que deben tenerse en cuenta
+
+
+ 1. Instalar siempre los nuevos archivos personales en una rama texmf
+ local del rbol global o en una rama personal, dependiendo de si
+ son archivos para uso comn en la mquina o nicamente para el
+ usuario. De esta forma puede actualizarse el rbol oficial sin
+ tocar los archivos locales o personales. Para la rama local, el
+ directorio raz local tendr un nombre del tipo:
+
+
+ teTeX: /usr/share/texmf.local/
+ fpTeX: c:\fptex\texmf.local\
+ mikTeX: c:\localtexmf\
+
+
+
+ que puede cambiar dependiendo de las opciones dadas durante la insta-
+ lacin. Por simplicidad en lo que sigue le denominaremos $TEXMFLOCAL.
+
+ 2. En la rama local, reproducir la estructura de directorios de la
+ rama principal. Estos son unos ejemplos de dnde deberan colocarse
+ archivos de distintas extensiones:
+
+
+ .sty, .cls o .fd: $TEXMFLOCAL/tex/latex/<paquete>/
+ .dvi, .ps o .pdf: $TEXMFLOCAL/doc/latex/<paquete>/
+ .bib: $TEXMFLOCAL/doc/bibtex/bib
+ .bst: $TEXMFLOCAL/doc/bibtex/bst
+ .tfm: $TEXMFLOCAL/fonts/tfm/<suministrador>/<fuente>/
+ .vf: $TEXMFLOCAL/fonts/vf/<suministrador>/<fuente>/
+ .afm: $TEXMFLOCAL/fonts/afm/<suministrador>/<fuente>/
+ .pfb: $TEXMFLOCAL/fonts/type1/<suministrador>/<fuente>/
+ .ttf: $TEXMFLOCAL/fonts/truetype/<suministrador>/<fuente>/
+
+
+
+ donde paquete, fuente y suministrador dependen de cada archivo indi-
+ vidual de cada paquete.
+
+ La rama personal suele estar en un subdirectorio texmf del directorio
+ de usuario, pero puede cambiar. En ella tambin es necesario
+ reproducir la estructura de directorios de la rama principal.
+ Dependiendo de la distribucin y/o de las opciones de configuracin
+ puede ser necesario rehacer la base de datos cuando se aaden o quitan
+ elementos.
+
+
+ 8.1.5. Activando ramas locales y personales del rbol de directorios
+ LaTeX global
+
+ A menudo la rama local del rbol global no est activada por omisin y
+ es necesario activarla:
+
+ teTeX y fpTeX;
+ En primer lugar es necesario localizar el archivo de
+ configuracin texmf.conf. ste puede estar en
+ /etc/texmf/texmf.conf, /etc/texmf.conf o
+ /usr/share/texmf/web2c/texmf.conf, dependiendo de la
+ distribucin. Aunque no siempre es necesario, en la primera
+ lnea del archivo borrar la palabra original.
+
+ Jugando adecuadamente con texmf.cnf, donde estn los caminos de
+ bsqueda, se configura sin problemas. Para activar una lnea
+ debe quitarse el carcter de comentario % al principio de la
+ lnea, para desactivarla aadir el carcter % al principio de la
+ lnea. Cuando se activa una lnea debe desactivarse la que antes
+ haca esa funcin, si la haba. Por ejemplo, si se tienen los
+ archivos de la distribucin bajo /usr/share/texmf/, archivos
+ locales bajo /usr/share/local.texmf y archivos personales bajo
+ ~/texmf, las lneas del texmf.cnf que lo haran son
+
+
+ TEXMFMAIN = /usr/share/texmf
+
+
+
+ para la rama principal, que viene activada por omisin. Para las
+ ramas local y personal se aadira (o se quitara el comentario de
+ la misma) una lnea del tipo
+
+
+ TEXMFLOCAL = /usr/share/texmf.local
+ HOMETEXMF = $HOME/texmf
+
+
+
+ que normalmente vienen comentadas. Finalmente se seleccionara
+
+
+ TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}
+
+
+
+ que las junta todas. Como se ha dicho antes, en la estructura de
+ las ramas local y personal debe clonarse la estructura de la rama
+ principal y como se dice en la seccin siguiente debe correrse tex-
+ hash (o mktexlsr) despus de hacer los cambios para rehacer la base
+ de datos de archivos. Para la rama personal puede ser necesario
+ rehacer la base de datos como usuario.
+
+ El fichero de configuracin est extensamente comentado con
+ explicaciones de la funcin de cada una de las posibles lneas.
+
+
+ 8.1.6. Rehaciendo la base de datos de archivos instalados
+
+ El paso final consiste en decirle a LaTeX que hay una serie de nuevos
+ archivos que debe ser capaz de encontrar. En la mayor parte de los
+ sistemas LaTeX libres recientes se mantiene una base de datos de
+ archivos instalados, para posibilitar una bsqueda ms rpida. En
+ estos sistemas es necesario actualizar esta base de datos cada vez que
+ se instalan nuevos archivos, mediante los programas suministrados con
+ este fin en la distribucin.
+
+ teTeX, fpTeX
+ Correr
+
+
+ texhash
+
+
+
+ web2c
+ En cualquier distribucin web2c reciente texhash debiera
+ funcionar. Si no es as, probar con
+
+
+
+ mktexlsr
+
+
+
+ MikTeX
+ En una distribucin MikTeX anterior a la v2.0, hacer con los
+ menes desplegables:
+
+
+ Start-> Programs-> MikTeX-> Maintenance-> Refresh filename database
+
+
+
+ o en una ventana DOS
+
+
+ initexmf -update-fndb
+
+
+
+ En una distribucin MikTeX mayor o igual que la v2.0, hacer con los
+ menes desplegables
+
+
+ Start-> Programs-> MikTeX 2-> MikTeX Options
+
+
+
+ y pulsar el botn "Update filename database".
+
+
+ 8.1.7. Cmo verifico los directorios en los que TeX busca archivos
+ de estilo?
+
+ La respuesta ms general sera mirando los archivos de configuracin,
+ pero si se trata de un TeX que utiliza las rutinas kpathsearch de Karl
+ Berry, es mucho ms sencillo
+
+
+ % kpsepath tex
+
+
+
+ responder con la lista de los directorios en los que busca. Una
+ doble barra (//) indica que se busca recursivamente en los subdirecto-
+ rios del que pone. Es decir, que si los paquetes particulares estn
+ en ~/texmf/tex/latex/lo-que-sea, o en ~/texmf/tex/mas-paquetes los
+ encontrar.
+
+
+ 8.2. Cmo personalizo el aspecto del documento?
+
+ 8.2.1. Cmo cambio la fuente de un documento o instalo nuevas?
+
+ Pues depende de la fuente que se quiera usar. Normalmente hay paquetes
+ de estilo que lo hacen automticamente. Por ejemplo, si pretendes usar
+ la familia de Times, usa el paquete times poniendo en el prembulo
+ \usepackage{times}. Otra familia disponible es lucida-bright, que
+ puedes cargar con el paquete lucidabr. Si miras estos archivos
+ (times.sty o lucidabr.sty) puedes aprender la forma de usar una
+ fuente, y copiarlo para otros tipos.
+ Hay muchos tipos de letras ya preparados as: times, helvetica (arial
+ est casi clonado de esta), courier, la letra gtica se llama oldgerm,
+ griego...
+
+ Un segundo paso es ir al CTAN para ver si alguien ha preparado un
+ paquete con el tipo deseado.
+
+ En el peor de los casos en el que no est preparado, puede crearse
+ manualmente un paquete a partir de los tipos originales en formato
+ Type-1, aunque no es un proceso inmediato. Ms informacin en
+ CTAN:info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf.
+
+
+ 8.2.2. Puedo utilizar una fuente TrueType como Arial en LaTeX?
+
+ A veces se piden tipos de letra que no estn disponibles directamente
+ en LaTeX como Arial. El tipo de letra Arial es TrueType, y este
+ formato no es soportado directamente por LaTeX. Desde pdflatex s es
+ posible usar tipos TrueType, pero antes hay que crear unos cuantos
+ archivos auxiliares que necesita TeX. El proceso no es sencillo. Est
+ descrito en http://www.radamir.com/tex/ttf-tex.htm
+
+ Recientemente ha aparecido otro documento que explica cmo convertir
+ los tipos TrueType en tipos PostScript, y cmo usar estos tipos
+ convertidos desde latex->dvips. El documento se encuentra disponible
+ en CTAN:info/TrueType/ y est orientado a un sistema tetex, por lo que
+ es posible que no funcione bajo windows/miktex.
+
+ El tipo de letra helvetica es muy parecido al tipo Arial y s est
+ disponible bajo LaTeX. Basta con aadir en el prembulo del documento
+
+
+ \renewcommand{\rmdefault}{phv}
+ \renewcommand{\sfdefault}{phv}
+
+
+
+ pero si hay frmulas matemticas stas seguiran utilizando los tipos
+ computer modern por lo que quedarn feas en medio del texto en hel-
+ vetica.
+
+
+ 8.2.3. Incluyendo subdocumentos TeX/LaTeX en el documento
+
+ Pueden incluirse subdocumentos TeX/LaTeX en un documento mediante las
+ rdenes \input e \include. \input{otro_documento} lo incluir en el
+ lugar en el que se introduce la orden, mientras que
+ \include{otro_documento} siempre abrir una pgina nueva al incluir el
+ documento. Sin embargo, \include permite incluir documentos de forma
+ selectiva mediante la orden \includeonly, mientras que \input no lo
+ permite. As, la orden \includeonly{doca,docc} en el prembulo har
+ que se incluyan nicamente los documentos doca y docc, a pesar de que
+ tambin docb tenga un \include,
+
+
+ ...
+ \includeonly{doca,docc}
+ \begin{document}
+ ...
+ \include{doca}
+ \include{docb}
+ \include{docc}
+ ...
+
+
+ 8.2.4. Cmo evito que salga la palabra captulo en las cabeceras de
+ captulo?
+
+ Cuando se usa spanish-babel basta con poner en el prembulo, despus
+ de haberse cargado babel
+
+
+ \addto{\captionsspanish}{\def\chaptername{}}
+
+
+
+ y queda eliminada la palabra Captulo. Si no se usa babel basta con
+ poner en el prembulo \def\chaptername{}. Realmente esto es un caso
+ particular de cambio de literales, que se trata en las secciones
+ ``literales'' y ``Cambio de nombre de secciones''
+
+
+ 8.2.5. Cmo cambio la cabecera de captulo por otra ms a mi gusto?
+
+ Hay dos formas, redefiniendo las rdenes que hacen las cabeceras, o
+ utilizando un paquete hecho que facilite el trabajo. Un paquete que
+ permite hacer cosas muy elaboradas con las cabeceras de los captulos
+ es titlesec, disponible en
+ CTAN:macros/latex/contrib/supported/titlesec
+
+
+ 8.2.6. Quiero una seccin no numerada, pero que aparezca en la tabla
+ de materias.
+
+ Por ejemplo, suponiendo que se trate de una lista de smbolos,
+
+
+ \section*{Lista de smbolos}
+ \addcontentsline{toc}{section}{Lista de smbolos}
+
+
+
+ Lo mismo para otros elementos (subseccin,...).
+
+
+ 8.2.7. No me funciona \subsubsubsection .
+
+ \subsubsubsection no existe, en los estilos estndar es \paragraph
+ quien hace ese papel.
+
+
+ 8.2.8. Cmo quito los encabezados que LaTeX pone automticamente en
+ las pginas blancas?
+
+ Si se quiere controlar cundo se quiere o no este comportamiento en
+ cada pgina con este problema, se puede definir una nueva orden,
+
+
+ \newcommand{\clearemptydoublepage}{\newpage{\pagestyle{empty}\cleardoublepage}}
+
+
+
+ y teclear \clearemptydoublepage cada vez que quieras continuar el
+ texto en una pagina impar.
+
+ Cuando se quiere que esto ocurra automticamente hay que redefinir la
+ orden \cleardoublepage como sugiere la documentacin del paquete
+ fancyhdr,
+ \makeatletter
+ \def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else
+ \vspace*{\fill}
+ \thispagestyle{empty}
+ \newpage
+ \if@twocolumn\hbox{}\newpage\fi\fi\fi}
+ \makeatother
+
+
+
+ Cuando se utiliza el paquete titlesec de Javier Bezos para definir
+ formatos propios de cabeceras y pies de pagina, la opcin de paquete
+ clearempty ya hace el trabajo:
+
+
+ \usepackage[<tus_opciones>,clearempty]{titlesec}
+
+
+
+ Otra posibilidad es utilizar el paquete nextpage,
+
+
+ \usepackage{nextpage}
+ ...
+ \cleartooddpage[\thispagestyle{empty}]
+ \chapter{...}
+
+
+
+ 8.2.9. Cmo quito los encabezados, pies o la numeracin de las
+ pginas?
+
+ La opcin \pagestyle{empty} quitar los encabezados y pies de todas
+ las pginas posteriores a aqulla en la que se invoca. La opcin
+ \thispagestyle{empty} quitar los encabezados y los pies de pgina en
+ la pgina donde se invoca esta orden.
+
+ Cuando lo que se quiere es eliminar nicamente el nmero de pgina, en
+ general no es conveniente utilizar \renewcommand{\thepage}{} porque
+ eso suprime todos los nmeros de pgina, incluidos los de los ndices
+ o las remisiones. Por tanto, hay que evitarla siempre que se pueda y
+ optar por soluciones mejor construidas y especficas a cada caso, como
+ utilizar una definicin personal de cabeceras que pueda activarse a
+ voluntad para ciertas pginas.
+
+
+ 8.2.10. Cmo pongo encabezados o pies de pgina a mi gusto?
+
+ La forma ms habitual es utilizar el paquete fancyhdr. Por ejemplo,
+ con pies
+
+
+
+ \documentclass{book}
+ \usepackage{fancyhdr}
+ \lfoot{titulo a la izquierda}
+ \rfoot{titulo a la derecha}
+ \cfoot{titulo al centro}
+ \pagestyle{fancy}
+ \begin{document}
+ \chapter{A title}
+ \thispagestyle{fancy} %opcional
+ \newpage
+ \section{a section}
+ \end{document}
+
+
+
+ pero titlesec tambin permite un amplio control del estilo de pgina.
+
+
+ 8.2.11. Cmo hago que LaTeX y TeX no partan nunca las palabras?
+
+ Para LaTeX si se ha cargado el paquete babel basta con la orden
+
+
+ \hyphenrules{nohyphenation}
+
+
+
+ Por supuesto el patrn nohyphenation debe de estar activado en lan-
+ guage.dat y el formato creado con l (Vanse ``Cmo activo el patrn
+ de particin de palabras para el castellano?'' y ``Cmo rehacer los
+ formatos?'').
+
+ Para TeX hay que hacer las cosas de otra forma. Una forma de conseguir
+ que TeX no corte casi nunca, (y as de paso se evita que corte mal) es
+ poner:
+
+
+ \pretolerance=2000
+ \tolerance=3000
+
+
+
+ al principio. Si se quiere que sto ocurra nicamente en un prrafo o
+ en una regin, debe encerrarse lo anterior y la regin deseada entre
+ llaves,
+
+
+ {\pretolerance=2000
+ \tolerance=3000
+ el prrafo o regin
+ }
+
+
+
+ sto puede utilizarse tambin para LaTeX
+
+
+ 8.2.12. Cmo ajusto los mrgenes de un documento LaTeX?
+
+ Quizs la forma ms cmoda sea utilizar el paquete geometry, que se
+ encuentra disponible en CTAN:macros/latex/contrib/supported/geometry.
+ Por ejemplo
+ \documentclass[a4paper, 10pt]{article}
+ \usepackage[a4paper,left=3cm,right=2cm]{geometry}
+
+
+
+ crea una pgina A4 con margen de 3cm a la izquierda y 2cm a la
+ derecha, sin ms complicaciones.
+
+ Otra cosa mucho ms complicada es cmo cambiar los mrgenes dentro de
+ un documento, en vez de hacerlo en el prembulo como lo hace el
+ paquete geometry. Un caso especial se tiene cuando se quiere alargar
+ un poco una pgina para que quepa un poco ms de texto y as evitar
+ situaciones poco estticas. Para sto, LaTeX2e proporciona la orden
+ \enlargethispage{distancia} donde se aumenta el tamao vertical de la
+ pgina en la distancia especificada.
+
+ A pesar de esa dificultad, puede utilizarse el paquete chngpage, que
+ proporciona rdenes para cambiar el aspecto de la pgina en el medio
+ de un documento (por ejemplo, hacerla ms estrecha o ms ancha, ms
+ corta o ms larga, e incluso desplazarla horizontal o verticalmente),
+ aunque no permite cambios dentro de un prrafo.
+
+
+ 8.2.13. Cmo obtengo un documento apaisado?
+
+ Cuando se quiere sacar la totalidad del documento apaisada, hay que
+ decirle a TeX que las dimensiones horizontal y vertical estn
+ cambiadas, comenzando el documento con la opcin landscape, algo del
+ tipo
+
+
+ \documentclass[landscape,a4]{article}
+
+
+
+ donde la clase de documento puede ser tambin cualquier otra como
+ slides. Esto intercambia las distancias horizontal y vertical, pero no
+ rota el documento final para que se ajuste a la posicin de la hoja.
+ Para ello se puede utilizar el dvips, por ejemplo en la forma sigu-
+ iente
+
+
+ dvips -ta4 -tlandscape tu_archivo -o tu_archivo.ps
+
+
+
+ donde -tlandscape gira la salida. La opcin -ta4 es a menudo conve-
+ niente si se utiliza papel a4, para que el giro se haga de forma ade-
+ cuada.
+
+
+ 8.2.14. Cmo ajusto el espaciado en el documento LaTeX?
+
+ Para ajustar el espaciado entre lneas en un documento LaTeX2e se
+ recomienda utilizar el paquete setspace, que se cargar en el
+ prembulo. Las rdenes \singlespacing, \onehalfspacing, y
+ \doublespacing colocadas en el prembulo establecen el espaciado
+ global del documento. Pueden establecerse valores intermedios mediante
+ la orden \setstretch{baselinestretch} en el prembulo. El valor por
+ omisin es espaciado simple. Asimismo se definen tres entornos con los
+ mismos nombres que las rdenes anteriores para cambios del espaciado
+ en regiones del documento (respecto del espaciado estndar en ese
+ momento, doublespacing empezar un entorno de espaciado doble que el
+ espaciado en ese momento, si es doble lo har an mayor).
+
+ Para un documento LaTeX209 puede utilizarse el paquete doublespace.
+
+ La forma ms cmoda de controlar el espaciado entre prrafos es
+ mediante el paquete parskip.
+
+
+ 8.3. Listas al gusto de cada cual.
+
+ 8.3.1. Cmo ajusto el espaciado en una lista?
+
+ La distancia entre los elementos es la suma de los valores de \parsep
+ (que es tambin la distancia entre prrafos dentro de un mismo
+ elemento) e \itemsep. Si slo se quiere cambiar la distancia entre
+ elementos pero no entre prrafos de un mismo elemento, basta con dar
+ un nuevo valor a la distancia \itemsep.
+
+ Es un espacio elstico, es decir, adems de con
+ \setlength{\itemsep}{1cm} se puede definir con algo como
+
+
+ \itemsep= 4pt plus 2pt minus 1pt
+
+
+
+ donde 4pt sera el espacio normal, 2pt lo mximo que podra estirarse
+ y 1pt lo mximo que podra encogerse.
+
+ El valor de \itemsep se restablece con cada \begin{itemize} (o la
+ lista de que se trate), y se hace igual a \parsep, por lo que hay que
+ modificarlo dentro de la lista, por ejemplo.
+
+
+
+ {\topsep=-15pt \parsep=-15pt \partopsep=-15pt
+ \begin{enumerate}\itemsep=-5pt
+ \item{ Pruebas de interespaciado}
+ \item{ Pruebas de interpaginado}
+ \item{ Pruebas de espaciado}
+ \end{enumerate}}
+
+
+
+ Puede hacerse que la separacin sea nula, mediante \setlength{\item-
+ sep}{-\parsep}
+
+ Hacer el cambio para todas las listas es algo ms complejo, pero una
+ forma de hacerlo sera redefinir \itemize (y lo mismo para las dems
+ listas) en la forma
+
+
+
+ \let\olditemize\itemize
+ \def\itemize{\olditemize\itemsep=0pt }
+
+
+
+ donde en este caso se ha puesto un valor de 0pt a \itemsep en todas
+ las listas enumeradas.
+
+
+
+ 8.3.2. Cmo cambio el tipo de numeracin en las listas numeradas?
+
+ Por ejemplo, para que escriba los elementos de primer nivel con
+ nmeros como 1 y los de segundo nivel con nmeros en la forma 1.1
+
+
+ \renewcommand{\theenumii}{\arabic{enumii}}
+ \renewcommand{\labelenumii}{\theenumi .\theenumii .}
+
+
+
+ Si algn paquete que ests usando redefine los \theenum, como el
+ babel-spanish, entonces debes asegurate que LaTeX eliga tus parametros
+ colocando las rdenes anteriores entre:
+
+
+ \AtBeginDocument{%
+ comandos aqui..
+ }
+
+
+
+ 8.3.3. Quiero mostrar un smbolo distinto en las listas itemize
+
+ Dentro de un itemize, puede especificarse en cada \item un parmetro
+ opcional, que es el smbolo que se mostrar (en lugar del topo por
+ defecto), por ejemplo, \item[$\odot$], y si se quieren cambiar todos,
+ con el mismo ejemplo,
+
+
+ \renewcommand{\item}{\item[$\odot$]}
+
+
+
+ o, mediante el paquete paralist,
+
+
+ \usepackage{paralist}
+ ...
+ \begin{itemize}[$\star$]
+ \item ...
+ \item ...
+ \end{itemize}
+
+
+
+ Tambin puede utilizarse el paquete pifont, as:
+
+
+ \usepackage{pifont}
+ \begin{Pilist}{pzd}{248}
+ \item bla
+ \item bla bla
+ \item bla
+ \end{Pilist}
+
+
+
+ El entorno Pilist es anlogo a itemize, pero en lugar del bullet usa
+ el caracter que se le pida de la fuente que se le pida. En el ejemplo
+ anterior, se usa el carcter con cdigo 248 de la fuente pzd que tiene
+ gran cantidad de simbolos adecuados para itemize.
+
+
+ 8.3.4. Puedo ajustar la separacin entre texto y listas?
+
+ Con el paquete enumitem, en CTAN:macros/latex/contrib/bezos/.
+
+
+ 8.3.5. Cmo interrumpir una lista numerada con un comentario y con-
+ tinuar despus con la numeracin correcta?
+
+ Entre las mdwtools hay un paquete llamado mdwlist que permite hacer
+ eso:
+
+
+ \begin{enumerate}
+ \item ...
+ \item ...
+ \suspend{enumerate}
+ Texto...
+ \resume{enumerate}
+ \item ...
+ \item ...
+ \end{enumerate}
+
+
+
+ Disponible en CTAN:macros/latex/contrib/supported/mdwtools/
+
+
+ 8.3.6. Puedo hacer listas en paralelo?
+
+ Para crear listas numeradas o por elementos de la forma
+
+
+ 1. Primer elemento 2. Segundo elemento 3. Tercer elemento
+ 4. Cuarto elemento 5. Quinto elemento 6. Sexto elemento
+
+
+
+ puede utilizarse el paquete paralist (disponible en
+ CTAN:macros/latex/contrib/supported/paralist) o bien el paquete multi-
+ col. Tambin existe el paquete multienumerate (CTAN:macros/latex/con-
+ trib/supported/multenum) y el entorno shortenumerate del paquete
+ shortlst (CTAN:macros/latex/contrib/supported/shortlst) destinado a
+ listas de elementos cortos.
+
+
+ 8.4. Referencias cruzadas, ndices, bibliografas y tablas de mate-
+ rias.
+
+ 8.4.1. Hay alguna herramienta de gestin de bases de datos bibli-
+ ogrficas en BibTeX ?
+
+ S, existen varias, por ejemplo
+
+ bibtex.el
+ Modo BibTeX para emacs. Normalmente viene incluido con emacs,
+ pero tambin se puede obtener de su pgina principal
+ http://www.ida.ing.tu-bs.de/people/dirk/bibtex/
+
+ Winbibdb y bibdb
+ ambos excelentes y disponibles en CTAN:support/bibdb con su
+ pgina base en http://www.mackichan.com/BibDB/default.htm
+
+ bibtool
+ disponible en CTAN:bibtex/utils/bibtool/ con su pgina principal
+ en http://bibtool.sourceforge.net/
+
+ jabref
+ http://jabref.sourceforge.net/ es una interfaz grfica escrita
+ en java para manejar bases de datos bibliogrficas. Necesita
+ Java >= 1.4.2
+
+
+ 8.4.2. Cmo introduzco la bibliografa o el ndice en la tabla de
+ materias?
+
+ La forma ms cmoda es utilizar el paquete tocbibind, que se encuentra
+ disponible en CTAN:macros/latex/contrib/supported/tocbibind y en la
+ mayor parte de las distribuciones, pero tambin puede hacerse a mano
+ con por ejemplo \addcontentsline{toc}{chapter}{\bibname} en la
+ definicin correspondiente.
+
+
+ 8.4.3. Cmo pongo el ndice con su contenido al principio de cada
+ captulo?
+
+ Con el paquete minitoc
+
+
+ 8.4.4. Cmo aado bibliografa al final de cada captulo en LaTeX?
+
+ Puede hacerse usando el paquete chapterbib. Para hacerlo de esta forma
+ debe estructurarse el documento en un archivo raz desde el que se
+ incluyen las distintas secciones que estn en archivos separados del
+ raz, incluir al final de cada uno de stos las rdenes de
+ bibliografa y procesar con bibtex los .aux de cada una de estas
+ partes. Si adems se quiere que no haya un salto de pgina al comenzar
+ la bibliografa en cada captulo, debe utilizarse la opcin
+ sectionbib.
+
+ Otro paquete que permite una cosa similar es bibunits
+
+
+ 8.4.5. Cmo divido la bibliografa por temas en LaTeX?
+
+ Los paquetes multibib y bibtopic permiten dividir una bibliografa
+ global en partes separadas para los distintos temas. El primero
+ requiere el uso de rdenes especficas para las citas bibliogrficas,
+ mientras que el segundo requiere dividir el archivo de bibliografa.
+
+
+ 8.4.6. Cmo cito una pgina de una referencia bibliogrfica?
+
+ Mediante algo del tipo
+
+
+ \cite[pg.~29]{gar98}
+
+
+
+ donde gar98 sera la etiqueta BibTeX para la cita deseada.
+
+
+
+ 8.4.7. Cmo cito una url con BibTeX ?
+
+ En los estilos bibliogrficos estndar de BibTeX no hay un tipo para
+ las url, aunque es posible que en una futura versin de BibTeX s lo
+ haya.
+
+ En tanto esa versin aparece la forma ms sencilla consiste en
+ utilizar el campo howpublished del tipo misc. Una entrada de ese tipo
+ tendra la forma
+
+
+ @misc{...,
+ ...,
+ howpublished = "\url{http://...}"
+ }
+
+
+
+ Tambin puede ocurrir que un artculo, informe o incluso libro se
+ encuentre disponible tambin en la web. En este caso se podra hacer
+ algo del tipo
+
+
+ @techreport{...,
+ ...,
+ note = "Tambin disponible como \url{http://...}"
+ }
+
+
+
+ donde se supone que se ha utilizado el paquete url, disponible en
+ CTAN:macros/latex/contrib/other/misc/url.sty/, lo que es muy recomend-
+ able para estas referencias por diversas razones.
+
+
+ 8.4.8. Cmo colapso una serie de citas consecutivas?
+
+ O cmo puedo hacer que aparezca una citacin bibliogrfica mltiple
+ consecutiva, por ejemplo, [1,2,3,4,5] como [1-5]? El paquete cite,
+ disponible en CTAN:macros/latex/contrib/supported/cite y en teTeX
+ permite hacer precisamente eso.
+
+
+ 8.4.9. Cmo hago una referencia cruzada a un documento externo?
+
+ Para hacer referencias cruzadas entre documentos se puede usar el
+ paquete xr, de David Carlisle, disponible en las distribuciones
+ habituales y en CTAN:macros/latex209/contrib/misc/xr.sty. Su uso es
+ como sigue,
+
+
+ ...
+ \usepackage{xr} %Referencias a otros documentos
+ ...
+ \externaldocument{miotrodocumento}
+ ...
+
+
+
+ Una vez hecho esto las referencias se declaran como si de un nico
+ documento se tratase.
+
+
+ 8.4.10. Afinando el aspecto de la tabla de materias o listas de fig-
+ uras y tablas.
+
+
+ Cmo controlar hasta qu nivel se incluye un elemento en la tabla
+ de materias?
+ En general, con
+
+
+
+ \setcounter{tocdepth}{X}
+
+
+
+ en el prembulo se controla hasta que nivel se incluir en el
+ ndice general, siendo X un nmero. Con 3 se incluye hasta \subsub-
+ section, con 2 hasta \subsection. sto permite cambiar el valor
+ definido por omisin en el estilo utilizado.
+
+ El ttulo del captulo, figura o tabla se solapa con su nmero si
+ ste
+ tiene muchos dgitos" Para las listas de figuras y tablas la
+ separacin se define en \l@figure} o \l@table, por ejemplo
+ book.cls lo hace as para las figuras
+
+
+ \newcommand*\l@figure{\@dottedtocline{1}{1.5em}{2.3em}}
+
+
+
+ En un estilo o en el prembulo entre makeatletter/makeatother
+ pueden redefinirse sus valores cambiando el ltimo nmero. Por
+ ejemplo, en el prembulo
+
+
+ \makeatletter
+ \renewcommand*{\l@figure}{\@dottedtocline{1}{1.5em}{3.3em}}
+ \renewcommand*{\l@table}{\@dottedtocline{1}{1.5em}{2.8em}}
+ \makeatother
+
+
+
+ Para las entradas de la tabla de materias sera necesario cambiar
+ los valores de \l@section, \l@subsection, \l@subsubsection,
+ \l@paragraph o \l@subparagraph de una forma anloga. Para los
+ captulos la cosa es ms problemtica porque se cambian ms cosas.
+
+ El paquete tocloft permite controlar detalles del diseo tipogrfico
+ de las tablas de materias y de las listas de figuras y tablas, aunque
+ su internacin con otros paquetes como titlesec no est
+ suficientemente probada.
+
+
+ 8.5. Cmo introduzco dibujos, diagramas e imgenes en LaTeX?
+
+ Hay dos formas de dibujar en TeX, mediante el uso de funciones
+ primitivas TeX bien directamente (muy duro) o a travs de alguno de
+ los paquetes de ms alto nivel que proveen de funciones que
+ internamente utilizan esas primitivas, pero que a un usuario se le
+ representan como funciones de dibujo normales en un cierto lenguaje, o
+ bien incluyendo grficos realizados mediante aplicaciones externas,
+ como es el caso de grficos en postscript encapsulado o en mapa de
+ bits.
+ El problema en este segundo caso es que los datos del grfico deben
+ darse en el documento mediante rdenes \special -- Vase ``Qu son
+ los \special'' -- y que stas rdenes son en general distintas para
+ los distintos conversores (drivers) a los formatos de impresin o
+ visualizacin. Para evitar al usuario tener que utilizar directamente
+ los \special se pueden utilizar paquetes de ms alto nivel que,
+ dependiendo de los conversores transforman sus rdenes a los \special
+ correspondientes. Si se quiere obtener el resultado final en pdf hay
+ una serie de limitaciones que hay que tener en cuenta, vase ``Cmo
+ obtengo un documento PDF a partir de mi documento TeX?''
+
+ Para ello se puede utilizar el paquete graphics, que est entre los
+ paquetes adicionales del LaTeX2e (disponible en
+ CTAN:macros/latex/required/graphics/). Dependiendo de las opciones
+ deseadas se le llama como graphics (menos potente) o graphicx (ms
+ potente y recomendado). Un paquete ms antiguo es psfig que en la
+ prctica ha sido sustituido en LaTeX2e por graphics que es el paquete
+ oficial de introduccin de grficos externos en LaTeX2e. Sin embargo,
+ si se usa LaTeX 209 ser necesario usar psfig (disponible en
+ CTAN:graphics/psfig)
+
+ Tambin es necesario tener un conversor de DVI al lenguaje de
+ impresora que soporte esos \special, lo que limita los formatos
+ grficos soportados. En particular es especialmente interesante que
+ soporten el formato .eps (postscript encapsulado), lo que hacen el
+ dvips y los conversores que vienen con OzTeX o TeXtures. La mayor
+ parte de los visualizadores de DVI no mostrarn correctamente estas
+ figuras, sino slo su espacio. En cualquier caso, es conveniente leer
+ primero la documentacin del paquete graphics o alguna de las
+ referencias que se dan a continuacin.
+
+ Existe en el CTAN documentacin muy interesante acerca de este tema.
+ El documento de Anik K. Goel (CTAN:info/figsinltx.ps) trata de
+ diferentes formas de generar figuras y de incluirlas con psfig para
+ LaTeX 209. El documento de Keith Reckdahl (CTAN:info/epslatex.pdf)
+ est ms dirigido al trabajo en LaTeX2e y a las figuras .eps. Una
+ referencia excelente sobre el tema es el LaTeX Graphics Companion, de
+ M. Goossens, S. Rahtz y F. Mittelbach, vase la seccin ``Libros en
+ otros idiomas''.
+
+
+ 8.5.1. Dibujando con TeX
+
+ Existen una serie de formas de dibujar con TeX en vez de importar
+ archivos externos. Desde el simple uso del entorno picture, incluso
+ con mejoras como las proporcionadas por epic a dibujos sofisticados
+ (aunque lentos) con las macros PicTeX. Dependiendo de lo que se quiere
+ hacer alguno de los siguientes sistemas puede ser el ms til:
+
+ pstricks
+ Disponible en CTAN:graphics/pstricks, que da acceso a la
+ potencia de postscript desde TeX mediante un uso sofisticado de
+ los \special. Necesita un conversor a postscript bueno (como
+ p.ej. dvips), est bien documentado y da buenos resultados.
+
+
+ pgf
+ pgf (portable graphics format) es un paquete de macros TeX para
+ crear dibujos. Su uso recuerda a pstricks y, aunque es menos
+ potente que ste, tiene la ventaja de que es compatible tanto
+ con dvips como con pdfTeX.
+
+
+ MetaPost
+ Toda la potencia de METAFONT, pero generando figuras postscript
+ en vez de tipos. Para ms informacin en castellano sobre
+ metapost puede consultarse la pgina
+ http://w3.mecanica.upm.es/metapost y para ver algunos ejemplos
+ de lo que se puede hacer con metapost, pueden seguirse los
+ enlaces citados en http://ltx.blogspot.com/2003/09/ms-recursos-
+ metapost.html.
+
+ A partir de la versin 3.7.1 del paquete grfico gnuplot ste ya
+ permite exportar sus resultados en formato metapost. gnuplot
+ est disponible en CTAN:graphics/gnuplot.
+
+ pdfLaTeX tambin trata metapost nativamente mediante el uso de
+ \convertMPtoPDF. La sintaxis es
+
+
+
+ \convertMPtoPDF {nombre} {escala x} {escala y}
+
+
+
+ Si el nombre del grfico incluido tiene la extensin .mps \include-
+ graphics llama internamente a esta orden de forma transparente al
+ usuario y no es necesario incluirla de forma explcita.
+
+ El grfico MP as incluido se puede manipular sin problema con los
+ comandos habituales de graphicx: rotatebox, resizebox, scalebox,
+ etc...
+
+ Los archivos metapost pueden editarse con un editor de texto y
+ conocimiento del lenguaje metapost, pero tambin est disponible el
+ editor grfico Metagraf para METAPOST, que se encuentra en fase
+ avanzada de desarrollo. Est escrito en Java y por tanto funciona
+ bajo distintos sistemas operativos. Se encuentra disponible en la
+ misma pgina anterior, http://w3.mecanica.upm.es/metapost.
+
+
+ El programa pstoedit permite pasar de postscript a otros formatos
+ editables, entre ellos metapost, aunque es posible que en el cambio
+ se pierdan elementos del dibujo original.
+
+ MfPic
+ Disponible en CTAN:graphics/mfpic. Este paquete genera cdigo
+ METAFONT a partir de macros TeX como las habituales. No da toda
+ la potencia de METAFONT, pero es bastante ms cmodo.
+
+
+ draTeX
+ de Eitan Gurari. Disponible en CTAN:macros/generic. Un paquete
+ de macros del tipo de PicTeX, pero mucho ms manejable y menos
+ necesitado de recursos de ordenador.
+
+
+
+ 8.5.2. Introduciendo figuras postscript encapsulado en LaTeX
+
+ Un ejemplo de documento en el que se incluye una figura postscript
+ externa utilizando el paquete graphicx sera (se supone que se utiliza
+ el conversor dvips)
+
+
+
+ ...
+
+ \usepackage[dvips]{graphicx}
+
+ ...
+
+ \begin{figure}
+ \centering
+ \includegraphics[width=10cm]{imagen.eps}
+ \caption{Esto es una imagen}
+ \label{fig:prueba}
+ \end{figure}
+
+ ...
+
+
+
+ que incluira la figura imagen.eps con una anchura de 10cm. Ntese que
+ el que LaTeX haya procesado sin problemas no implica que se vaya a ver
+ con el visualizador ni que se vaya a imprimir a una impresora, ya que
+ para ello los conversores correspondientes deben saber cmo hacerlo
+ (P.ej., dvips sabe como incluir figuras postscript y si se ha compi-
+ lado con esa opcin algunos tipos de mapas de bits). Asimismo es con-
+ veniente usar \centering en vez del entorno center, ya que este ltimo
+ no es para centrar texto, sino para componer un poco aparte texto cen-
+ trado, con blancos antes y despus. Si se usa center en un figure
+ habr algo de espacio adicional que no debera estar ah. Adems,\cen-
+ tering se puede usar tambin como entorno, si fuera necesario
+ (\begin{centering} ... \end{centering}). Si se desea cambiar la sepa-
+ racin con centering pueden cambiarse \textfloatsep (para b y t) e
+ \intextsep (para h) con \setlength.
+
+ Para contener el gasto en espacio de disco que supone usar PostScript,
+ el paquete graphicx permite que las figuras que se van a incluir estn
+ comprimidas con gzip, puesto que entiende los sufijos .eps.gz y
+ .ps.gz. Para que LaTeX sepa el tamao de la figura que est en el
+ archivo, debe existir otro con extensin .eps.bb o .ps.bb con la
+ Bounding Box (medidas de la caja) de la figura en PostScript, que se
+ puede obtener de ese mismo archivo (es una de las primeras lneas) o
+ usando algn programa como psbb, distribuido con las utilidades groff
+ de GNU (http://www.gnu.org).
+
+
+ 8.5.3. Introduciendo imgenes en mapa de bits en LaTeX.
+
+ En este caso la lnea del \includegraphics... anterior se convertira
+ en
+
+
+ \includegraphics[0,0][101mm,50mm]{figura.pcx}
+
+
+
+ donde suponemos que el conversor soporta este formato. Se le ha dicho
+ especficamente el tamao de la figura, ya que si no fuera as, se
+ obtendran distintos resultados al imprimirla en impresoras de dis-
+ tinta resolucin.
+
+
+ 8.5.4. Inclusin de una imagen desde un PDF con mltiples pginas.
+
+ Puede hacerse con el paquete graphicx
+
+
+ \includegraphics[page=6]{archivo}
+
+
+
+ o con el paquete pdfpages,
+
+
+ \usepackage{pdfpages}
+ ...
+ \begin{document}
+ \includepdf[pages={3-7,9}]{/path/to/other.pdf}
+ \end{document}
+
+
+
+ 8.5.5. Introduciendo cdigo y figuras postscript en pdfTeX
+
+ PDFTeX -- vase la pregunta ``Cmo obtengo un documento PDF a
+ partir de mi documento TeX?'' -- no permite la inclusin directa ni de
+ cdigo ni de figuras PostScript. Pueden incluirse figuras en PDFTeX
+ siempre que stas estn en alguno de los formatos JPEG, PDF PNG
+ (Vanse en el prrafo siguiente las extensiones por omisin que se
+ esperan para cada formato). Parece que el soporte para formato TIFF se
+ ha eliminado a partir de la versin 1.10a de pdfTeX, por lo que aunque
+ se vuelva a poner es preferible utilizar alguno de los formatos
+ anteriores. Existen utilidades para convertir de PostScript
+ encapsulado a PDF y PNG (Distiller de Adobe (http://www.adobe.com)
+ para PDF y ghostscript -- gs --
+ (http://www.cs.wisc.edu/~ghost/index.html) para convertir a PDF o a
+ PNG). Para este ltimo se tienen dos programas que lo utilizan y hacen
+ de intermediario con el usuario, ps2pdf, incluido en ghostscript y
+ epstopdf (disponible en CTAN:usergrps/uktug/baskerville/epstopdf, e
+ incluido al menos en teTeX) para conversin directa entre los formatos
+ .eps y .pdf
+
+ Aunque no de forma directa, el paquete tex4pdf, disponible en
+ CTAN:macros/latex/contrib/ps2pdf permite incluir figuras y cdigo
+ postscript (figuras pstricks y eps, cadenas psfrag, reescalados
+ postscript) en un documento procesado con pdflatex, pero necesita
+ versiones recientes de los paquetes preview, ifpdf e ifvtex y del
+ sistema TeX/LaTeX, as como adaptar el documento LaTeX para su uso.
+ Tambin pueden utilizarse, con mejor o peor fortuna otros mecanismos
+ (Vase ``Cmo obtengo un documento PDF a partir de mi documento
+ TeX?'')
+
+ Para incluir una figura en PDFTeX se deben seguir los mismos pasos que
+ para incluir una figura PostScript encapsulado en LaTeX. Cuando la
+ figura se tiene en dos formatos distintos, uno para pdfLaTeX y otro
+ para LaTeX/dvips, es recomendable omitir la extensin del archivo
+ (.ps, .eps, .ps.gz, .eps.gz para PostScript y .jpg, .tif, .pdf, o .png
+ para PDFTeX). De esta forma el paquete graphicx tomar el archivo
+ adecuado segn se est usando LaTeX o PDFLaTeX.
+
+
+ 8.5.6. Cmo coloco un fragmento TeX en una figura?
+
+ Esencialmente hay dos formas, mediante los paquetes psfrag y overpic,
+
+ psfrag
+ permite sustituir cadenas de texto en el grfico postscript por
+ cadenas de texto TeX. Para ello la cadena de texto a sustituir
+ debe estar en el archivo postscript de forma explcita
+ utilizando alguno de los tipos postscript en vez de dibujada
+ mediante lneas. Es decir, en el archivo postscript debe
+ aparecer (cadena) donde cadena es la cadena de texto a
+ sustituir. Esta cadena debe estar compuesta preferentemente de
+ caracteres los alfanumricos a-zA-Z0-9, aunque puede funcionar
+ en algunos otros casos. Para usarlo se cargara el paquete en el
+ prembulo:
+
+
+ \usepackage{psfrag}
+
+
+
+ y dentro de un begin-end que englobe la figura o utilizando llaves
+ (para que su efecto no se extienda a otras figuras salvo que se
+ quiera) se incluira
+
+
+ \psfrag{cadena_original}{cadena_sustituta}
+
+
+
+ por cada una de las cadenas a sustituir.
+
+
+ Este sistema NO funciona directamente con pdfLaTeX salvo que se
+ utilice vtex. Vase ``Cmo obtengo un documento PDF a partir
+ de mi documento TeX?''. Del mismo modo, las cadenas sustituidas no
+ se ven correctamente en los visores de dvi habituales, sino slo
+ cuando se ha pasado a postscript. Puede hacerse funcionar con
+ pdfLaTeX de forma indirecta mediante el paquete ps4pdf o programas
+ como tex2pdf.
+
+
+ overpic
+ El paquete overpic permite colocar cualquier tipo de texto sobre
+ una figura e incluso figuras sobre figuras. Tiene dos formas de
+ introducir las coordenadas, absolutas en % de la figura
+ original, y relativas, en % de la figura reescalada. Asimismo
+ cuenta con una excelente documentacin.
+
+
+ \usepackage{overpic}
+
+
+
+ 8.6. Figuras, tablas y elementos flotantes
+
+
+ 8.6.1. Cmo puedo poner una figura rodeada de texto?
+
+ Para ello existen distintas opciones, mediante los paquetes
+
+ wrapfig (CTAN:macros/latex/contrib/other/misc/wrapfig.sty) Contiene
+ wraptable, para hacer lo mismo con tablas.
+
+ floatflt (CTAN:macros/latex/contrib/other/floatflt/)
+
+ picins (CTAN:macros/latex209/contrib/picins/), que tambin puede
+ utilizarse con tablas.
+
+ picinpar (CTAN:macros/latex209/contrib/picinpar)
+
+ todos ellos disponibles en el CTAN. Para casos sencillos un simple
+ parbox o una minipage pueden hacer un buen trabajo.
+
+
+ 8.6.2. Cmo puedo poner una figura a dos columnas?
+
+ Usando el entorno figure* en vez de figure, para que LaTeX sepa que
+ ese elemento flotante es de doble ancho. Si no, lo considera de ancho
+ normal, y la imagen que se mete dentro, simplemente no cabe y se sale
+ por el otro lado, ocultando el texto de la otra columna.
+
+
+ 8.6.3. Cmo consigo un mayor control de la posicin de figuras y
+ dems elementos flotantes?
+
+ Para ello puede utilizarse el paquete float,
+ (CTAN:macros/contrib/supported/float, que aade nuevas funcionalidades
+ al comportamiento normal de los elementos flotantes como figuras y
+ tablas.
+
+
+ 8.6.4. Puedo poner una figura en una tabla?
+
+ Por qu no?,
+
+
+ ...
+ \usepackage{graphcix}
+ ...
+ \begin{tabular}{ccc}
+ \includegraphics{fig1} &
+ \includegraphics{fig2} &
+ ...
+
+
+
+ 8.6.5. Cmo colocar dos figuras o tablas juntas de distintas for-
+ mas?,
+
+ Es posible colocar en LaTeX dos figuras o tablas en paralelo, cada una
+ con su pie, as como dos figuras juntas en posicin arbitraria o
+ superpuestas dentro de un entorno figure.
+
+ Dependiendo de lo que se quiera, puede hacerse bien mediante el
+ paquete subfigure o mediante un entorno minipage (Vase epslatex.ps).
+ subfigure permite numerar las figuras como (a), ... y tener un pie
+ comn a las subfiguras ms pies individuales para cada subfigura y
+ minipage mantiene los pies normales e independientes para cada figura.
+ Por ejemplo, con minipage,
+
+
+ \usepackage{capt-of}
+ ...
+ \begin{figure}
+ \begin{minipage}{.5\linewidth}
+ Figure
+ \caption{Foo}
+ \end{minipage}%
+ \begin{minipage}{.5\linewidth}
+ Table
+ \captionof{table}{Too}
+ \end{minipage}
+ \end{figure}
+
+ El uso del paquete capt-of (Vase "Puedo poner un pie en tablas y
+ figuras que no flotan?") sera necesario en este caso ya que los dos
+ elementos son distintos, una figura y una tabla, pero no sera nece-
+ sario si los dos fueran figuras o los dos tablas.
+
+ Si lo que se quiere es simplemente colocar dos figuras juntas adems
+ de lo anterior sin \caption puede utilizarse algo como
+
+
+ \setlength{\unitlengtth}{1cm}\begin{picture}(12,6)
+ \put(0,0){\includegraphics[width=6cm]{figura1.ps}}
+ \put(6,0){\includegraphics[width=6cm]{figura2.ps}}
+ \end{picture}
+
+
+
+ As las figuras se colocan como uno quiera e incluso puede hacerse que
+ una figura se superponga sobre otra (como si fueran fotos en una
+ mesa).
+
+
+ 8.6.6. Puedo poner un pie en tablas y figuras que no flotan?,
+
+ A veces se desea colocar figuras y tablas en un lugar preciso y para
+ ello se prescinde de los entornos figure y table. Sin embargo tambin
+ se desea poder usar \caption para no perder la numeracin y la
+ referencia en la lista de figuras y tablas.
+
+ Un equivalente a la orden \caption llamado \captionof puede ser
+ utilizado fuera de entornos flotantes (figure y table) si se hace uso
+ del paquete capt-of. Su sintaxis es \captionof{tipo}[pie corto]{pie
+ largo} donde el pie corto es el opcional que ir a la tabla de
+ figuras/tablas y el tipo es figura/tabla.
+
+ La llamada en el documento sera del tipo
+
+
+ \centerline{\includegraphics{mi grafica}}
+ \captionof{figure}{Esta es mi grafica}
+
+
+
+ para una figura, mientras que para una tabla se puede usar algo del
+ tipo:
+
+
+ \begin{center}
+ \begin{tabular}{*2l}\hline\hline
+ uno & dos\\
+ tres & cuatro\\\hline
+ \end{tabular}
+ \end{center}
+ \captionof{table}{Esto es una tabla} % se puede incluir dentro del entorno center.
+
+
+
+ 8.6.7. Cmo hago para incluir elementos flotantes grandes o
+ numerosos sin que den errores o se vayan al final?
+
+ Las clases article, report y book estndar son muy exigentes en cuanto
+ a sus "consideraciones estticas" para poner grficos flotantes en una
+ pgina. El caso es que sto slo es til cuando hay pocos objetos
+ flotantes, pero si hay muchos, esta exigencia es contraproducente. Lo
+ que acaba pasando es que LaTeX no encuentra lugares adecuados para
+ poner los grficos y los acaba mandando todos al final o dando
+ errores. Afortunadamente, los parmetros que controlan todo sto son
+ fcilmente configurables y para mejorar las cosas basta copiar y pegar
+ los que vienen en amsart.cls, que son mucho mas flexibles,
+
+
+
+ \setcounter{topnumber}{4}
+ \setcounter{bottomnumber}{4}
+ \setcounter{totalnumber}{4}
+ \setcounter{dbltopnumber}{4}
+ \renewcommand{\topfraction}{.97}
+ \renewcommand{\bottomfraction}{.97}
+ \renewcommand{\textfraction}{.03}
+ \renewcommand{\floatpagefraction}{.9}
+ \renewcommand{\dbltopfraction}{.97}
+ \renewcommand{\dblfloatpagefraction}{.9}
+ \setlength{\floatsep}{12pt plus 6pt minus 4pt}
+ \setlength{\textfloatsep}{15pt plus 8pt minus 5pt}
+ \setlength{\intextsep}{12pt plus 6pt minus 4pt}
+ \setlength{\dblfloatsep}{12pt plus 6pt minus 4pt}
+ \setlength{\dbltextfloatsep}{15pt plus 8pt minus 5pt}
+
+
+
+ Cuando se quiere hacer para una nica figura puede utilizarse el
+ paquete afterpage, por ejemplo en
+
+
+ \usepackage{afterpage}
+ ...
+ \begin{figure}
+ \includegraphics{figura-muy-grande}
+ \end{figure}
+ \afterpage{\clearpage}
+
+
+
+ la figura grande pasar a la pgina siguiente (donde quedar sola), en
+ lugar de irse al final del documento.
+
+
+ 8.7. Cmo giro un elemento en un documento LaTeX?
+
+ Para giros sencillos, el paquete graphicx contiene las orden
+ \rotatebox que permite conseguir giros de elementos de texto o incluso
+ de elementos ms complejos. Sin embargo, cuando se quieren rotar
+ elementos complejos es recomendable aprovechar las posibilidades del
+ paquete rotating (disponible en
+ CTAN:macros/latex/contrib/supported/rotating). Este paquete permite
+ girar casi cualquier tipo de elemento, incluyendo figuras o tablas
+ completas con sus cabeceras, mediante los entornos sideways,
+ sidewaystable y sidewaysfigure. Por ejemplo,
+
+
+
+ \documentclass{article}
+ \usepackage{rotating}
+ \begin{document}
+ \begin{sideways}
+ \begin{tabular}....
+
+ \end{tabular}
+ \end{sideways}
+ \end{document}
+
+
+
+ Hay que tener en cuenta que en todos estos casos se modifica el
+ postscript, por lo que los resultados no se ven correctamente con xdvi
+ ni funcionan bien con pdflatex.
+
+
+ 8.8. Cmo escribo algunos smbolos?
+
+
+ Cmo obtener el smbolo del euro?
+ Utilizando el paquete eurofont de CTAN. Contiene instrucciones
+ acerca de su uso con LaTeX. La notacin de entrada normal es
+ \EUR{1,50}. Tambin puede utilizarse el paquete textcomp y la
+ macro \texteuro.
+
+ Cmo escribir los grados en LaTeX?
+ Para obtener un resultado de mejor calidad que con ^\circ puede
+ utilizarse la orden \textdegree del paquete textcomp.
+
+ Cmo encerrar un caracter en un crculo?
+ Utilizando la orden \textcircled{...}
+
+ Cmo escribir la barra invertida?
+ Como texto: \textbackslash. Como matemticas: \backslash. Como
+ cdigo: \verb|\|
+
+ Cmo escribir un espacio en blanco visible?
+ Utilizando la orden \textvisiblespace
+
+ Cmo escribir el smbolo del sombrerito de la ?
+ Utilizando la orden \textasciitilde
+
+
+ 8.9. Cmo convierto mis documentos a LaTeX y desde LaTeX?
+
+ Existe una FAQ especfica acerca de las conversiones entre formatos
+ TeX y de otros procesadores de textos, que se archiva en CTAN:help/wp-
+ conv/wp-conv.zip.
+
+
+ 8.9.1. Cmo obtengo un documento PDF a partir de mi documento TeX?
+
+ Existen distintas formas de producir PDF usando (La)TeX.
+
+ A partir del PS -- ver la pregunta ``Qu es PostScript?'' --,
+ usando Distiller (de Adobe) o ghostscript, en este ltimo caso, se
+ recomienda usar una versin posterior a la 5.53, que mejora el PDF
+ generado (lo hace ms compacto). Se pueden perder los enlaces y
+ algunas caractersticas de PDF (las anotaciones). Las
+ distribuciones de ghostscript suelen venir con un pequeo programa
+ llamado ps2pdf que hace la transformacin llamando a ghostscript
+ con los parmetros adecuados.
+
+
+ A partir de DVI, usando dvipdfm, (CTAN:dviware/dvipdfm), que genera
+ PDF de alta calidad, insertando los grficos y permitiendo
+ anotaciones y enlaces. Su pgina raz es
+ http://odo.kettering.edu/dvipdfm, pero tiene una serie de
+ restricciones que deben consultarse en el manual.
+
+ Usando pdfTeX, que procesa el archivo fuente de TeX y genera PDF
+ directamente. Acompaado por el paquete hyperref, es de la mxima
+ utilidad en la generacin de documentos que mantienen la calidad de
+ composicin de textos de TeX y permiten cierta interaccin. pdfTeX
+ est an en desarrollo, pero permite generar PDF para casi todos
+ los documentos -- para ver los detalles y limitaciones en la
+ inclusin de figuras y cdigo postscript, vase la seccin
+ ``Introduciendo figuras y cdigo postscript en pdfTeX'' --. Las
+ versiones de desarrollo pueden encontrarse en:
+ http://www.fi.muni.cz/~thanh/download/. Informacin adicional est
+ disponible en http://www.tug.org/interest.html#projects.
+
+ Cuando el documento de entrada no contiene nicamente texto
+ TeX/LaTeX sino tambin figuras en postscript encapsulado o utiliza
+ paquetes que mediante cdigo postscript cambian el texto
+ (rotaciones, reescalados, sustitucin de cadenas) o dibujan, las
+ cosas son un poco ms complicadas ya que pdfTeX no lo soporta
+ directamente. El camino dvi->ps->pdf que se ha sealado antes debe
+ funcionar pero pueden perderse por el camino algunas
+ caractersticas del pdf. Otros caminos alternativos pasan por
+ convertir sobre la marcha a pdf las figuras y efectos postscript.
+ Esto puede hacerse, con ms o menos limitaciones de distintas
+ formas:
+
+ Utilizando tex2pdf, disponible en
+ http://developer.berlios.de/cvs/?group_id=57. La idea es que
+ tex2pdf procesa cada grafico que emplea sustituciones de psfrag y
+ luego lo convierte a pdf. Para grficos que no se encuentran en
+ minipages, tablas, funciona relativamente bien. La ltima versin
+ cvs de tex2pdf soporta preliminarmente psfrag y pstricks (este
+ ultimo a traves de ps4pdf), sin embargo, de momento el proyecto
+ parece parado,
+
+ vTeX es una distribucin comercial de TeX que da salida .pdf
+ directamente y soporta inclusin de figuras .eps, as como el uso
+ de psfrag y de algunos otros paquetes que utilizan postscript de
+ alto nivel. Existen versiones para linux y OS/2 gratuitas,
+ disponibles en
+
+ http://www.micropress-inc.com/linux/
+
+ http://www.micropress-inc.com/os2/
+
+ y en CTAN:systems/vtex. La versin para Windows es comercial
+ http://www.micropress-inc.com
+
+ Utilizando el paquete pdftricks, disponible en
+ CTAN:macros/latex/contrib/pdftricks, que intenta extender el poder
+ del paquete pstricks a pdfLaTeX.
+
+ Utilizando el paquete ps4pdf, disponible en
+ CTAN:macros/latex/contrib/ps4pdf. Vase ``Introduciendo cdigo y
+ figuras postscript en <em/pdfTeX''
+
+
+ 8.9.2. Cmo obtengo una versin texto a partir de un documento PDF?
+
+ La forma ms sencilla es mediante el Adobe Reader (antes Acrobat
+ Reader) -- vase ``El formato pdf'' -- utilizando la herramienta
+ Obtener texto que se encuentra a la izquierda en el Adobe Reader.
+ 8.9.3. Cmo obtengo un documento html a partir de mi documento TeX?
+
+ En la pgina http://www.mayer.dial.pipex.com/tex.htm se comentan
+ diferentes programas de conversin de LaTeX a html con ejemplos del
+ resultado de las distintas conversiones. Los ms conocidos son
+
+ HEVEA
+ es un conversor de LaTeX a html bastante completo, que convierte
+ los smbolos sin utilizar grficos (aunque puede requerir un
+ poco de configuracin del navegador). Disponible en
+ http://para.inria.fr/~maranget/hevea/. Tiene versiones para
+ Linux, Solaris y Windows aunque es posible compilarlo para otros
+ sistemas operativos a partir del cdigo fuente.
+
+ TTH
+ es otro conversor de LaTeX a html que tambin convierte las
+ ecuaciones en vez de representarlas como imgenes. Disponible en
+ http://hutchinson.belmont.ma.us/tth/. Tiene versiones para
+ Linux, Mac y Windows aunque es posible compilarlo para otros
+ sistemas operativos a partir del cdigo fuente. Utiliza
+ grficos.
+
+ TeX4ht
+ es otro conversor a distintos sistemas de hipertexto, disponible
+ en http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html. Tiene
+ versiones para Linux, Mac y Windows aunque es posible compilarlo
+ para otros sistemas operativos a partir del cdigo fuente.
+
+ latex2html
+ es quizs el ms antiguo de los conversores, escrito en perl y
+ utiliza grficos.
+
+
+ 8.9.4. Convirtiendo a LaTeX desde otros formatos
+
+
+ WordPerfect
+ El programa wp2latex (disponible en CTAN:support/wp2latex) ha
+ sido recientemente actualizado por Jaroslav Fojtik y ahora est
+ disponible tanto para DOS como para Unix.
+
+
+ Rich Text Format (RTF)
+ Hay dos conversores disponibles, rtf2tex de Robert Lupton
+ (disponible en CTAN:support/rtf2tex) y rtf2latex, de Erwin
+ Wechtl (disponible en CTAN:support/rtf2latex), para TeX y LaTeX
+ respectivamente.
+
+
+ Microsoft Word
+ Aunque hay un programa de conversin (wd2latex, disponible en
+ CTAN:dviware/wd2latex), se recomienda convertir el documento a
+ RTF y utilizar uno de los conversores de RTF mencionados.
+
+ Tambin hay un par de conversores comerciales, word2tex y
+ tex2word.
+
+
+
+ 8.10. Cmo rehago los formatos de TeX y LaTeX?
+
+ Los formatos de TeX son archivos que contienen las macros bsicas
+ precompiladas para obtener una mayor eficiencia. Para rehacer un
+ formato es necesario utilizar la orden initex (Este nombre cambia para
+ algunas distribuciones, por ejemplo para emTeX es tex -i). Como
+ muestra, para rehacer el formato plain se hara
+ initex plain \dump
+
+
+
+ Con eso se tiene el archivo plain.fmt; ya slo queda reemplazarlo
+ donde estuviera el original y listo.
+
+ Para hacerlo por ejemplo para eplain se habra hecho initex plain, y
+ cuando aparece * se introducira \input eplain y despus cuando
+ vuelve a aparecer * se introducira \dump, as tendra un formato con
+ eplain y no habra que estar ponindolo con \input.
+
+ Cuando deben incluirse distintos archivos en el formato, a menudo es
+ ms cmodo utilizar una archivo que los llame a todos. Por ejemplo,
+ para eplain se podra haber creado el archivo eplain.ini con las
+ lneas
+
+
+ \input plain
+ \input eplain
+ \dump
+
+
+
+ y se habra rehecho el formato con initex eplain.ini.
+
+ En la mayor parte de las distribuciones modernas no es necesario
+ rehacer los formatos como se ha dicho antes, sino que hay herramientas
+ que ayudan a ello. As, por ejemplo en teTeX despus de configurar los
+ distintos parmetros del formato (idioma, tamaos de memoria...) al
+ salir se rehace automticamente el formato, o en mikTeX donde hay un
+ elemento en un men desplegable para rehacer los formatos ( o desde
+ una ventana DOS initexmf --dump).
+
+
+ 8.11. Cmo llamo a un editor desde TeX/LaTeX?
+
+ Dando el valor adecuado a la variable de entorno TEXEDIT
+
+
+ SET TEXEDIT=tu_editor +%d %s
+
+
+
+ en el autoexec.bat o similares o
+
+
+ export TEXEDIT=tu_editor +%d %s
+
+
+
+ para bash y similares
+
+
+ 8.12. Algunas cosillas matemticas.
+
+ 8.12.1. Cmo escribo un nmero con periodo utilizando LaTeX?
+
+ Para escribir un periodo (el acento breve invertido que indica la
+ repeticin de cifras decimales y que se pone encima de la parte
+ peridica del nmero) la solucin ms elegante consiste en utilizar
+ el paquete yhmath de Yannis Haralambous, disponible en
+ CTAN:macros/latex/contrib/supported/yhmath. Este paquete permite
+ indicar periodos de longitud arbitraria mediante un acento matemtico
+ \wideparen que hace precisamente ese papel.
+
+ El paquete yhmath necesita un tipo especial que viene con el paquete y
+ adems el paquete amsmath, por lo que para uso espordico o no tan
+ exigente puede bastar una definicin como la siguiente
+
+
+ \def\periodo#1{\mathop{\vbox{\ialign{##\crcr\noalign{\kern3pt}%
+ \ensuremath{\braceld\leaders\vrule\hfill\bracerd}%
+ \crcr\noalign{\kern3pt\nointerlineskip}%
+ \ensuremath{\hfill\displaystyle{#1}\hfill}\crcr}}}\limits}
+
+
+
+ Existe otro paquete denominado tipa, disponible en CTAN:/fonts/tipa.
+ ste es un sistema para trabajar con alfabetos fonticos, que propor-
+ ciona la orden \texttoptiebar{'caracter'} donde 'caracter' obviamente
+ es un numero(s) o una letra(s).
+
+
+ 8.12.2. Cmo puedo hacer para que la etiqueta de una ecuacin p.ej.
+ (3.5) contenga adems el nmero de la seccin actual p.ej. (3.1.5)
+
+ La respuesta se puede encontrar en Lamport seccin 6.3 y en el
+ Companion seccin 8.6 (Este captulo del Companion est actualizado en
+ CTAN:info/companion-rev/). LaTeX define y mantiene unos cuantos
+ contadores; uno de ellos es equation. Para generar una etiqueta
+ impresa, LaTeX ejecuta una orden cuyo nombre se forma aadiendo \the
+ al comienzo del nombre del contador adecuado. Por ejemplo, un nmero
+ de ecuacin se genera con la orden \theequation.
+
+ Para cambiar la numeracin de ecuaciones de modo que se indique el
+ captulo, la seccin y un nmero correlativo dentro de la seccin
+ haramos:
+
+
+ \renewcommand{\theequation}{\thesection.\arabic{equation}}
+
+
+
+ El problema es que ahora tendramos que volver a poner a cero el con-
+ tador de ecuaciones al comienzo de cada seccin o captulo. Una
+ solucin sencilla es incluir en el prembulo (entre un \makeatletter y
+ un \makeatother) lo siguiente:
+
+
+ \@addtoreset {equation}{section}
+
+
+
+ Esto har que automticamente se ponga el contador equation a 1 cuando
+ se encuentre un nuevo \section.
+
+
+ 8.12.3. Cmo hay que hacer para lograr la N, R de doble trazo con
+ que se representan los nmeros naturales, reales, etc...
+
+ Una forma que funciona incluso en plain TeX y que no requiere cargar
+ tipos adicionales es con definiciones del tipo
+
+
+ \def\CC{{\rm C\kern-.18cm\vrule width.6pt height 6pt depth-.2pt \kern.18cm}}
+ \def\NN{{\mathop{{\rm I}\kern-.2em{\rm N}}\nolimits}}
+ \def\PP{{\mathop{{\rm I}\kern-.2em{\rm P}}\nolimits}}
+ \def\RR{{\mathop{{\rm I}\kern-.2em{\rm R}}\nolimits}}
+ \def\RRt{{\fa I}\kern-.2em{\fa R}}
+ %% This version of \RR can be used in the title of the paper
+ \def\ZZ{{\mathop{{\rm Z}\kern-.28em{\rm Z}}\nolimits}}
+
+
+
+ Tambin es posible utilizar el tipo mathbb incluido con las amsfonts.
+ stas se cargaran en el prembulo con
+
+
+ \usepackage{amsfonts}
+ \usepackage[mathscr]{euscript}
+
+
+
+ y se llamaran como \mathbb{C}, etc...
+
+ Otra alternativa es el uso de los tipos bbm. Estos de cargan en el
+ prembulo con
+
+
+ \usepackage{bbm}
+
+
+
+ de forma que $\mathbbm{N, Z, R, Q, I, C}$ dara el correspondiente
+ smbolo.
+
+
+ 8.12.4. Puedo forzar que una frmula tenga el mismo nmero que otra?
+
+ S mediante el paquete amsmath y la orden \tag. Por ejemplo,
+
+
+ \begin{equation}\label{1}
+ 1+1=2.
+ \end{equation}
+ \begin{equation}
+ 1+1=2.\tag{\ref{1}}
+ \end{equation}
+
+
+
+ 8.12.5. Puedo escribir smbolos matemticos en negrita?
+
+ Pues no es nada elemental. Sin tipos especiales no. Inicialmente no se
+ consider necesario que las letras griegas pudieran representar
+ vectores y no se incluyeron tipos con ellas. La solucin pasa por usar
+ amstex y los tipos euler (ms en concreto eurb).
+
+ Tambin puede utilizarse el paquete amsmath. As,
+
+
+ \usepackage{amsmath}
+ \begin{document}
+ $\boldsymbol{H}$
+ \end{document}
+
+ Si algn smbolo de alguna fuente no cambia a negrita con esta orden,
+ puede tambin utilizarse, con el mismo paquete, $\pmb{H}$.
+
+
+ 8.12.6. Puedo rotar una ecuacin?
+
+ Puede utilizarse ls orden rotatebox del paquete graphicx, pero hay que
+ meter la ecuacin en un parbox, por ejemplo, utilizando el entorno
+ align, del paquete amsmath,
+
+
+ \rotatebox{35}{
+ \parbox{4cm}{
+ \begin{align*}
+ (la ecuacion)
+ \end{align*}
+ }
+ }
+
+
+
+ 8.12.7. Algunas preguntas matemticas de breve respuesta.
+
+
+ Cmo se escriben los nmeros combinatorios (por ejemplo N sobre
+ k)?
+ \binom{N}{k}, disponible en el paquete amsmath.
+
+
+ Cmo represento un tensor con sus ndices?
+ Puede probarse con el paquete tensind, disponible en
+ CTAN:/macros/latex/contrib/supported/bezos/.
+
+
+ Cmo cancelar elementos en una ecuacin en LaTeX
+ Mediante el paquete cancel
+
+
+ Cul es la instruccin para poner el producto vectorial?
+ \times o \wedge, segn la forma que prefieras (cruz y angulito,
+ respectivamente).
+
+
+ Qu smbolos estn disponibles para LaTeX?
+ Adems de los smbolos bsicos de LaTeX muchos otros smbolos
+ estn disponibles a travs de distintos paquetes. Una excelente
+ referencia a todos los smbolos disponibles se encuentra en
+ CTAN:tex-archive/info/symbols/comprehensive
+
+
+
+ 8.13. Cmo hago cuadernillos, trpticos y documentos con formatos
+ especiales?
+
+ 8.13.1. Cmo hago cuadernillos con TeX o LaTeX?
+
+ Para hacer cuadernillos estrictamente con TeX o LaTeX se pueden
+ utilizar las utilidades para manipular .dvi (disponibles en
+ CTAN:dviware/dvibook) o utilizar el paquete quire (disponible en
+ CTAN:macros/generic/midnight). Ambos permiten hacer cuadernillos, pero
+ en ambos casos es necesario tener los tipos para los distintos tamaos
+ antes y despus, y dan problemas con facilidad cuando se incluyen
+ grficos externos.
+
+ El mtodo ms recomendable es utilizar las psutils, un conjunto de
+ utilidades para manejar archivos postscript. Aunque el ejemplo est
+ para un unix, tambin estn disponibles para DOS, lo nico que en vez
+ de mandarlo a la cola de impresora se mandara a un archivo que
+ despus se imprimira con ghostscript/ghostview.
+
+ Para Unix por ejemplo, si se colocan adecuadamente las hojas en la
+ impresora
+
+
+ psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -o | lpr
+
+
+
+ imprimira las caras impares del librillo (cada una de ellas con dos
+ pginas reducidas y correctamente ordenadas). Se sacan las hojas, se
+ ordenan adecuadamente y se colocan adecuadamente en la impresora y
+
+
+ psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -e | lpr
+
+
+
+ imprimira las caras pares del librillo, y ya est, se tiene un lib-
+ rillo perfecto. La utilidad pstops tambin permite hacer todo eso
+ directamente, pero con unas opciones mucho ms crpticas.
+
+ psbook tambin permite definir el tamao del pliego, cuando el libro
+ va a constar de distintos pliegos cosidos, cada uno de ellos de un
+ nmero de pginas. Por ejemplo,
+
+
+ $ psbook -s 16 manualA4.ps
+
+
+
+ reordenara las pginas para hacer pliegos de 16 pginas, y su salida
+ se pasara despus por psnup y psselect. El comportamiento por omisin
+ consiste en hacer un nico pliego.
+
+
+ 8.13.2. Cmo hago trpticos con LaTeX?
+
+ El paquete leaflet nos permite construir trpticos. Realmente slo
+ modifica los mrgenes de la pgina completa para dividirla en tres
+ reas. El resultado al compilar es un documento con 6 pginas como
+ mximo, en el que cada pgina tiene el texto escrito en una columna
+ estrecha a la izquierda y el resto de la pgina est en blanco. Este
+ documento an no est finalizado y debe ser postprocesado. El
+ postproceso lo hace un script (que viene incluido en el paquete), que
+ se ocupa de llamar a pstops (que debe estar instalado) y que es quien
+ junta tres pginas en una, colocndolas en el orden apropiado para que
+ al imprimir a doble cara el resultado sea tres pginas por cara, y de
+ modo que al doblar en tres quede en el orden correcto de lectura.
+ Puesto que pstops funciona sobre ficheros postscript (.ps), el
+ documento original debe ser procesado con dvips (no sirve usar
+ pdflatex).
+
+
+ 8.13.3. Puedo preparar un pster con TeX/LaTeX?
+
+ Por una parte existe un paquete llamado a0poster
+ (CTAN:macros/latex/contrib/supported/a0poster) y por otra existe una
+ alternativa basada en un programa C llamado poster
+ (CTAN:support/poster). Este ltimo distribuye el texto en pginas A4
+ que pueden unirse para hacer un pster grande.
+
+
+ 8.13.4. Puedo hacer libretos y cartulas de CD con LaTeX?
+
+ S, con el paquete cd-cover, disponible en
+ CTAN:macros/latex/contrib/cd-cover. Eso s, a la hora de imprimir hay
+ que decirlo que lo haga en apaisado.
+
+
+ 8.14. Cmo puedo preparar una exposicin utilizando LaTeX?
+
+ 8.14.1. Haciendo transparencias con LaTeX
+
+ En primer lugar se tiene la clase de documento slides, que forma parte
+ de LaTeX2e. Adems, existen varios paquetes preparados para hacer
+ transparencias. Los ms clsicos son
+
+ seminar (CTAN:macros/latex/contrib/other/seminar)
+
+ foiltex (CTAN:macros/latex/contrib/supported/foiltex).
+
+ 8.14.2. Haciendo una presentacin con LaTeX
+
+ Tambin es posible generar directamente las transparencias en formato
+ .pdf ``Qu es el formato pdf?'' utilizando los paquetes pdfslide
+ (CTAN:macros/latex/contrib/supported/pdfslide) y pdfscreen
+ (CTAN:macros/latex/contrib/supported/pdfscreen), quedando las
+ presentaciones preparadas para ser proyectadas desde un ordenador.
+ Otra alternativa consiste en utilizar la clase de documento foils
+ (parte de foiltex) y pdflatex, utilizando posteriormente el
+ postprocesador ppower4 (http://www-sp.iti.informatik.tu-
+ darmstadt.de/software/ppower4/index.html) para tratar el archivo pdf
+ obtenido. Un ejemplo de presentacin realizada con este sistema es la
+ de Luis Seidel al EGUTH99, disponible en
+ ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb
+
+
+ 8.14.2.1. beamer
+
+ Una opcin que se est haciendo muy popular es la clase beamer,
+ disponible en http://latex-beamer.sourceforge.net/. Aparte del propio
+ manual puede encontrarse una gua rpida en
+ http://www.geocities.com/kijoo2000/beamer.html.
+
+ Con beamer se distribuye otro paquete independiente para la inclusin
+ de objetos multimedia en los documentos PDF creados mediante pdftex.
+
+ nicamente se requiere en el prembulo:
+
+
+ \usepackage{multimedia}
+
+
+
+ y la inclusin (pero no la incrustacin) de ficheros de vdeo AVI o
+ QuickTime es tan fcil como:
+
+
+
+ \movie[width=60mm,height=45mm,borderwidth=0.5mm]{Ttulo}}{fichero.avi}\\
+ \movie[width=60mm,height=45mm,poster,showcontrols]{}{fichero.mov}\\
+
+ as como para audio (estos s que pueden ser incrustables):
+
+
+
+ \sound[inlinesound,samplingrate=22050,encoding=muLaw,bitspersample=8,
+ channels=2,label=misonido]{}{fichero.au}\\
+
+ \hyperlinksound[]{misonido}{\includegraphics[width=10mm]{inicio.png}}
+ \hyperlinkmute{\includegraphics[width=10mm]{paro.png}}\\
+
+
+
+ 8.14.3. Ms informacin sobre presentaciones
+
+ La pgina web http://www.math.uakron.edu/~dpstory/pdf_demos.html
+ enumera una serie de macros de LaTeX y otros programas utilizados para
+ hacer presentaciones tipo PowerPoint.
+
+
+ Otra fuente de informacin acerca de las posibilidades de
+ presentaciones basadas en TeX y PDF, es la pgina
+ http://www.cds.caltech.edu/caltex/2000/ de Ross Moore, que incluye
+ fuentes de documentos, ejemplos,enlaces,...
+
+ Otra interesante pgina es http://www.miwie.org/presentations/, de
+ Michael Wiedmann, que contiene una enumeracin de distintos sistemas y
+ se ejemplos de cada uno. No slo cubre la presentacin en PDF, sino
+ tambin en HTML y otros formatos. Para cada solucin, muestra un
+ ejemplo, pros y contras.
+
+ Para presentaciones en pster vase la seccin ``psters''.
+
+
+ 8.15. Algunas cosas que a veces se piden para mandar un documento a
+ la imprenta.
+
+ La forma en que se debe mandar un documento a la imprenta no es nica,
+ sino que depende del tipo de proceso de impresin por el que vaya a
+ pasar el documento. En buena parte de los casos debiera bastar con
+ enviar un archivo postscript normal con el documento. Sin embargo, a
+ veces se pide el documento con caractersticas especiales como las que
+ a continuacin se tratan,
+
+
+ 8.15.1. Sacando la imagen especular de un archivo (es decir, con todo
+ al revs).
+
+
+ Con LaTeX puede hacerse utilizando el paquete crop, en la forma
+
+
+ \usepackage[mirror]{crop}
+
+
+
+ La reflexin especular se puede hacer directamente en el postscript,
+ en las tres formas siguientes (si se tiene una distribucin completa y
+ actual como teTeX)
+
+
+ dvips <archivo dvi> -h mirr.hd
+ dvips <archivo dvi> -Pmirr
+ dvips <archivo dvi> -Pmirrorprint
+
+ Realmente las dos primeras son la misma, pero llamadas de distinta
+ forma (config.mirr llama a mirr.hd). crop y mirr.hd estn disponible
+ en muchas distribuciones y adems pueden encontrarse en
+ CTAN:macros/latex/contrib/supported/crop/ y CTAN:macros/generic/TeX-
+ PS/mirr.hd
+
+
+ 8.15.2. Sacando el archivo en negativo (es decir, blanco sobre
+ negro).
+
+ Para sacar el archivo en negativo puede utilizarse el paquete crop,
+ cargndolo como
+
+
+ \usepackage[invert]{crop}
+
+
+
+ 8.15.3. Marcas de corte.
+
+ Para hacer los cortes, o marcas de corte (las lneas que sealan por
+ donde deber cortar la guillotina) puede utilizarse el paquete crop al
+ que se acaba de hacer referencia. Dentro de las midnight macros
+ (disponibles en CTAN:macros/generic/midnight se puede utilizar quire
+ que tambin permite hacer marcas de corte.
+
+
+ 8.16. Algunas cuestiones adicionales, o menos FAQ
+
+
+ Cmo evito que se pegue el texto despus de una orden?
+ Es decir, como evitar que si se escribe algo como \LaTeX es ...
+ aparezca como LaTeXes ... con el texto pegado. Para ello hay
+ varias formas, algunas ms elegantes que otras. Las ms
+ sencillas son escribirlo bien como \LaTeX{} es ... o como
+ \LaTeX\ es .... Sin embargo esto no resulta demasiado elegante,
+ aunque es inevitable cuando se utiliza con rdenes predefinidas.
+ Cuando estas rdenes estn definidas por el autor del documento,
+ resulta muy cmodo utilizar el paquete xspace, parte de las
+ herramientas bsicas de LaTeX2e. La forma de uso es simple, debe
+ incluirse en el prembulo del documento la llamada al paquete,
+ \usepackage{xspace} y al definir la orden se hace como
+
+
+ \newcommand{\mycommand}{palabra\xspace}
+
+
+
+ De este modo cualquier llamada a \mycommand incluir el espacio en
+ blanco si es necesario, y no lo har si no es necesario.
+
+
+
+ Es posible poner en el margen derecho o izquierdo una imgen?
+ Para colocar una figura en el margen:
+
+
+ \marginpar{\includegraphics{icono}}
+
+
+
+ Puedo hacer referencias cruzadas a notas a pie de pgina, incluso
+ desde otras notas a pie de pgina?
+ Perfectamente, con \label puesto dentro de la nota al pie
+ (\footnote{\label{f1}Texto} y \ref puesto en su lugar
+ (\footnote{Esta nota hace referencia a la nota \ref{f1} de la
+ pgina \pageref{f1}}). Mediante \label se establece la
+ referencia al ltimo contador incrementado, en este caso el de
+ las notas al pie.
+
+ Naturalmente, hasta que no est la segunda nota, con su \label
+ correspondiente, el \ref que se ha puesto en la primera no
+ tendr valor asignado, y al componer el texto parcial, en lugar
+ del nmero de la nota aparecern los tpicos smbolos de
+ interrogacin de cerrar.
+
+
+
+ Puedo acumular las notas a pie de pgina al final del captulo?
+ S, utilizando el paquete endnotes.
+
+
+
+ Cmo conseguir que la llamada a la nota de pie de pgina no sea un
+ nmero, sino una letra?
+ Por ejemplo con
+
+
+ \renewcommand{\thefootnote}{\itshape\alph{footnote}}
+
+
+
+ (Las llamadas con letras deben ser con cursiva, y se suelen reser-
+ var para cuadros y similares.)
+
+
+
+ Puedo escribir notas a pie de pgina en el margen?
+
+
+ \marginpar{\footnotemark}\footnotetext{Texto de la nota}
+
+
+
+ Puedo escribir notas a pie de pgina en los ttulos de seccin?
+ S, pero \footnote debe ser protegido como \protect\footnote.
+ sto tiene un problema adicional, saldr el smbolo de la nota a
+ pie de pgina en la tabla de materias. El paquete footmisc con
+ la opcin stable permite hacerlo de una forma ms adecuada.
+
+
+ Puedo tener ms control sobre la posicin de las notas a pie de
+ pgina?
+ El paquete yafoot permite un mayor control soble las notas a pie
+ de pgina, mediante tres ficheros de estilo, pfnote.sty para
+ confinar las notas a pie en una pgina, fnopos.sty para
+ controlar su posicin y dblfnote para hacerlas a doble columna.
+
+
+
+ Cmo saco un listado bonito de un programa en un documento LaTeX?
+ Ms bonito que utilizar verbatim queda con cualquiera de los
+ paquetes listings, lgrind o fancyvrb
+
+
+
+ Cmo colorear texto en LaTeX?
+ Algunos ejemplillos para empezar a colorear texto
+
+
+ ...
+ \usepackage{color}
+ ...
+ \begin{document}
+ ...
+ \textcolor[rgb]{1,0,0}{soy un texto que quedara en color rojo}
+ \textcolor[rgb]{1,1,0}{yo soy un texto en amarillo}
+ \textcolor[rgb]{0,0,1}{hola, soy azul}
+ \textcolor[rgb]{0,1,1}{soy azul celeste}
+ \textcolor[rgb]{1,0,1}{yo soy rosa}
+ \textcolor[rgb]{0,1,0}{yo verde claro}
+ \textcolor[rgb]{0.5,0,0}{marron}
+ \textcolor[rgb]{0,0.5,0.5}{azul verdoso}
+ \textcolor[rgb]{1,1,1}{soy blanco}
+
+
+
+ etc, etc, etc...
+
+ rgb significa red green blue y corresponde a una forma de
+ especificar el color. El numero entre corchetes indica cunto
+ (R)ed, (G)reen, y (B)lue corresponde al color del texto. Existen
+ otras maneras ms complicadas pero sta est bien para empezar.
+
+
+ Cmo colorear celdas en LaTeX?
+ Utilizando el paquete colortbl (junto con el paquete graphicx)
+ Algo como
+
+
+ \multicolumn{1}{>{\columncolor[gray]{0.8}}c}{text}
+
+
+
+ debe colorear una celda.
+
+
+
+ Cmo centrar elementos ms grandes que el ancho de lnea?
+ Por ejemplo, para una figura puede hacerse de la forma
+ siguiente:
+
+
+ \begin{center}
+ \makebox[0cm][c]{\includegraphics{tufigura.eps}}
+ \end{center}
+
+
+
+ o en general,
+
+
+
+ \begin{center}
+ \makebox[0cm][c]{
+ Material tabular, o cualquier otra cosa.
+ }
+ \end{center}
+
+
+
+ Si se desea usar el entorno table, para poder poner el correspondi-
+ ente \caption, la cosa se complica un poco ya que \makebox no
+ admite un entorno flotante como table en su interior:
+
+
+ \begin{center}
+ \begin{table}
+ \centering\makebox[0cm[c]{
+ \begin{tabular}{|c|c|}
+ ...... ....
+ \end{tabular}
+ }
+ \caption{Texto}
+ \end{table}
+ \end{center}
+
+
+
+ Tambin puede colocarse un pie dentro del \makebox, pero se nece-
+ sita un poco ms de trabajo (Vase "Puedo poner un pie en tablas y
+ figuras que no flotan?")
+
+
+
+ Cmo obtener el tamao de una tabla?
+ Una posibilidad consiste en fabricar la tabla dentro de un
+ savebox con el entorno lrbox y luego medirlo con \widthof, etc.
+ del paquete calc. Si se usa longtable, este procedimiento no
+ funciona, ya que se extiende por varias pginas. Sin embargo
+ longtable precisamente escribe la longitud de cada fila de la
+ tabla en el fichero .aux, por lo que se podra recuperar desde
+ all. En concreto, longtable escribe la definicin de una macro
+ \LT@<num>, donde <num> es un nmero de orden correlativo de cada
+ entorno longtable (en romano y en minsculas) que contiene las
+ longitudes de cada columna.
+
+
+
+ Cmo cambiar el grosor que tienen definido por omisin las lneas
+ que separan las columnas y filas dentro de tablas?
+ Por ejemplo con renewcommand{\arrayrulewidth}{1.1pt}
+
+
+
+ Puedo hacer que una celda de una tabla est dividida en dos por
+ una
+ diagonal?" Puede utilizarse el paquete slashbox, disponible en
+ CTAN:macros/latex/contrib/other/slashbox
+
+
+
+ Cmo aadir al texto el nmero de pgina actual?
+ En principio, podra pensarse que bastara con usar la orden
+ \thepage. Sin embargo, debido a cmo TeX va componiendo los
+ prrafos el resultado puede ser incorrecto, ya que primero
+ ejecuta todas las macros segn va componiendo el prrafo y hasta
+ que no est terminado no decide en que pgina van sus lneas. Si
+ el prrafo ocupa dos pginas, es muy probable que la pgina sea
+ incorrecta.
+
+
+ Para sincronizar correctamente la pgina con su nmero hay que
+ usar algn mecanismo que s permita conocer la pgina correcta,
+ como el de las referencias con \label y \pageref. El siguiente
+ cdigo es una modificacin de uno incluido en el LaTeX
+ Companion:
+
+
+ \usepackage{ifthen}
+ \newcounter{pl}
+ \newcommand\pcheck{%
+ \stepcounter{pl}%
+ \label{pl-\thepl}%
+ \ifthenelse{\isodd{\pageref{pl-\thepl}}}{impar}{par}}
+ \begin{document}
+ Esta pgina es \pcheck. \newpage
+ Esta pgina es \pcheck.
+ \end{document}
+
+
+
+ Cmo saber el nmero de pginas de un documento para utilizarlo en
+ el mismo?
+ El paquete lastpage lo resuelve de forma adecuada (necesitar un
+ par de compilaciones). Mediante su uso pueden construirse
+ expresiones del tipo pgina 1 de 10 (con pgina \thepage{} de
+ \pageref{LastPage}).
+
+
+
+ Cmo evitar que una url muy larga se me desborde por la derecha?
+ Utilizando el paquete url. Est pensado precisamente para eso,
+ para dividir los urls por puntos adecuados que no afecten a su
+ legibilidad, como por ejemplo en las barras separadoras de
+ directorio.
+
+
+
+ Como se escribe parte de un texto a 2 columnas?
+ Por ejemplo, utilizando el paquete multicol.
+
+
+
+ Como hacer que la clase report comience ndice y captulos en
+ pginas impares?
+ Con la opcin openright. Por ejemplo
+
+
+ \documentclass[12pt,a4paper,openright]{report}
+
+
+
+ Cmo hacer buen postscript o pdf?
+ Puede utilizarse testflow. Es un paquete de diagnsticos que da
+ bastante informacin til para producir buen postscript y/o pdf
+ en un sistema TeX. Se encuentra disponible en
+ CTAN::/macros/latex/contrib/supported/IEEEtran/testflow
+
+
+ 8.17. He encontrado un error en LaTeX Cmo lo notifico?
+
+ Para notificar errores o problemas se escribe latex latexbug y se
+ enva el informe as generado a latex-bugs _AT_ rus.uni-stuttgart.de.
+ Se recomienda previamente leerse las distintas FAQ y pedir ayuda en
+ los distintos foros acerca del problema, y slo entonces, cuando se
+ est seguro que el problema es de LaTeX2e mandar el informe de error.
+
+
+ 9. Por qu no consigo ...?
+
+ 9.1. Por qu no salen las imgenes en mi documento?
+
+ La misin de TeX/LaTeX no es entender de grficos. As que cuando se
+ encuentra con uno, este simplemente deja el hueco apropiado, da una
+ indicacin del grfico que hay que insertar (usando un comando
+ \special) y continua procesando el documento.
+
+ No todos los conversores soportan todos los formatos grficos, en el
+ caso de un formato incompatible, el conversor deja el hueco y no
+ representa el grfico. Es conocido que los visualizadores de DVI en
+ pantalla no suelen representar bien todos los grficos PS.
+
+ Para solucionar esto, use otro conversor que si soporte dichos
+ grficos (por ejemplo use dvips y visualice con gs)
+
+ Vanse ``Qu son los \special?'', ``Qu es un conversor (driver)?'',
+ ``Introduciendo figuras en LaTeX'' para ms informacin.
+
+
+ 9.2. Por qu no salen los caracteres acentuados si yo los escribo
+ bien?
+
+ En primer lugar debe echarse un vistazo a seccin ``cmo puedo
+ escribir los acentos y dems caracteres extendidos?''.
+
+ Cuando la entrada de caracteres mediante inputenc no funciona,
+ especialmente en un sistema Linux, suele ser debido a que por omisin
+ en algunos sistemas Linux, el fichero se guarda como utf-8, por lo que
+ deben seguirse las instrucciones para utf-8 que all se detallan. Un
+ sntoma habitual es que saque y otros caracteres acentuados como A
+ con ~ seguida de otro caracter extrao.
+
+ Otras posibilidades seran cambiar la codificacin del fichero con una
+ herramienta como recode o iconv antes de procesarlo con LaTeX o, si se
+ guarda por omisin como utf-8, decirle explcitamente si es posible,
+ al editor, la codificacin en debe leer y guardar el fichero en
+ cuestin. Por ejemplo, para {x}emacs, una primera lnea con % -*-
+ coding: iso-8859-1 -*- hara que el fichero se leyera y guardara
+ siempre como latin1. Para otros editores debe consultarse la
+ documentacin para saber si es posible y cmo.
+
+
+ 9.3. Por qu no encuentro el archivo babelbst.tex cuando uso custom-
+ bib ?
+
+ La intencin del autor del paquete era que las lenguas de babel
+ proporcionaran ese archivo, de ah su nombre. Sin embargo, en la
+ prctica pocas lenguas lo proporcionan, aunque entre ellas est
+ spanish. El archivo esbst.tex fue pensado para que se pueda utilizar
+ como el babelbst.tex que esperan los estilos creados (Vase ``BibTeX
+ en castellano, custom-bib'').
+ 9.4. Por qu a veces no me da el mismo resultado o incluso errores
+ al procesar un documento en dos sistemas distintos?
+
+ O dicho con otras palabras, no se supone que una de las bondades de
+ LaTeX es que el fuente es portable al igual que el dvi?
+
+ La respuesta es que lo anterior es cierto, pero con matices. Lo que es
+ portable y universal es el lenguaje TeX. Sus comandos primitivos (los
+ que TeX tiene definidos intrnsecamente) son utilizables en cualquier
+ mquina. No obstante, como escribir documentos a base de primitivas
+ puede resultar extremadamente engorroso, LaTeX define otro conjunto de
+ comandos ms amigable, para las tareas ms habituales. Algunos de
+ stos estn en el cuerpo de LaTeX y otros en paquetes adicionales --
+ vase ``paquetes en LaTeX''.
+
+ De este modo, para que un documento sea portable y universal, no basta
+ con que TeX est instalado en ambas mquinas. Debe tenerse adems el
+ conjunto de macros LaTeX (y a ser posible en la misma versin), y el
+ conjunto de todos los paquetes que el documento use (tambin a ser
+ posible en la misma versin). Si las versiones no coinciden pueden
+ producirse efectos secundarios indeseados, aunque esto, por suerte, no
+ es muy frecuente, pues salvo algunas excepciones (babel, la ms
+ notable) los paquetes intentan mantener la "compatibilidad hacia
+ atrs" (es decir, que las nuevas versiones se comporten de la misma
+ forma que lo hacan las antiguas).
+
+
+ 10. Preguntas que se van quedando obsoletas
+
+ 10.1. Qu es FTC ?
+
+ FTC es un filtro que genera las particiones para el castellano.
+ Adems, simplifica enormemente la introduccin de acentos. Est
+ descrito en:
+
+
+ @ARTICLE(pepe:wds
+ ,AUTHOR= "Jos{\'e} A. Ma{\~n}as"
+ ,TITLE= "{Word Division in Spanish}"
+ ,JOURNAL= "Comm. ACM"
+ ,YEAR= 1987
+ ,volume= 30
+ ,number= 7
+ ,pages= "612--616"
+ ,month= "July"
+ )
+
+
+
+ Puede conseguirse en:
+
+ ftp://ftp.dit.upm.es/pub/pepe/ftc
+
+
+
+ 10.2. Qu es ML-TeX?
+
+
+ ML-TeX es un conjunto de parches para el WEB de TeX (hubo tambin
+ versiones para TeX 2.X) que permiten manejar realmente 256 caracteres
+ internamente y, mediante el primitivo \charsubdef, reconstruir esos
+ caracteres mediante combinaciones de otros. Knuth copi masivamente de
+ ML-TeX para el TeX 3.X y spanish.sty usa ideas sacadas de ah. ML-TeX
+ es la mejor solucin, si no se dispone de fuentes extendidas. TeX 3.X
+ incorpora muchas de las ideas de Ferguson, pero no todas. Los parches
+ para ML-TeX con TeX 3.0 son mucho ms pequeos que los antiguos.
+
+ Si somos usuarios de DOS, emTeX incorpora ya ML-TeX sin ms que usar
+ -ml en la lnea de comando al crear el formato.
+
+ Si somos usuarios de UNIX, es muy posible que tengamos compilador de C
+ (al menos GCC) y podemos aplicar los cambios nosotros mismos con el
+ web2c de Karl Berry.
+
+
+ 11. Informacin sobre LaTeX en castellano
+
+ 11.1. El Grupo de Usuarios de TeX Hispanohablantes (CervanTeX)
+
+ 11.1.1. Qu es CervanTeX?
+
+ CervanTeX es el grupo de usuarios de TeX hispanohablantes, y forma
+ parte de los grupos locales asociados al TeX User Group.
+
+ La asociacin CervanTeX busca intercambiar experiencias sobre TeX y
+ sobre sus aplicaciones, y promoverlo de forma adecuada en el mbito
+ hispanohablante.
+
+ Estos fines se desarrollan mediante la discusin y la colaboracin en
+ el desarrollo de aplicaciones de TeX y programas asociados; la
+ promocin y el fomento de publicaciones relacionadas con TeX; la
+ organizacin de cursos, congresos y seminarios; y la colaboracin e
+ intercambio con todo tipo de sociedades, instituciones y editoriales
+ cientficas.
+
+
+ 11.1.2. Cmo puedo entrar en contacto con el grupo de usuarios?
+
+
+ En este momento la Junta Directiva de CervanTeX est formada por
+
+
+ PRESIDENTE: Juan Luis Varona presidente@cervantex.org
+ SECRETARIO: Roberto Herrero secretario@cervantex.org
+ TESORERO: Enrique Melndez tesorero@cervantex.org
+ VOCALES: Luis Sanjun y Javier Bezos
+
+
+
+ La pgina WWW del grupo CervanTeX se encuentra en:
+
+ http://www.cervantex.org
+
+
+ con informacin ms especfica sobre las actividades del grupo en
+
+ http://www.cervantex.org/actividades.php
+
+
+ La direccin postal del grupo es
+
+
+ CervanTeX
+ Apartado de correos 60118 AP
+ E-28080 Madrid
+ Espaa
+
+
+
+ 11.2. La lista es-tex
+
+
+ 11.2.1. Cmo funciona la lista es-tex ?
+
+ La lista es-tex es el foro principal de discusin en este idioma. Se
+ trata de una lista cerrada, por lo que es necesario suscribirse a la
+ misma para enviar y recibir mensajes. Aunque es independiente del
+ grupo CervanTeX, gran parte de los suscriptores de la lista son
+ miembros del grupo y viceversa. CervanTeX recomienda a todas las
+ personas interesadas en TeX en espaol la suscripcin a esta lista.
+
+
+ Para suscribirse, debe enviarse un mensaje a
+ LISTSERV@LISTSERV.REDIRIS.ES que tenga en el cuerpo del mismo
+
+ subscribe ES-TEX
+
+
+ Para enviar un mensaje a la lista una vez suscrito:
+
+
+ mail ES-TEX@LISTSERV.REDIRIS.ES
+
+
+
+ Es muy recomendable que los principiantes con las Listas de
+ Distribucin lean el documento sobre Correcto Uso de las Listas de
+ Distribucin que se encuentra en:
+
+ http://www.rediris.es/list/list-moral.html.
+
+
+ y no est de ms la lectura del documento Cmo hacer preguntas de man-
+ era inteligente, disponible en
+
+ http://www.sindominio.net/ayuda/preguntas-inteligentes.html
+
+ http://www.catb.org/~esr/faqs/smart-questions.html.
+
+
+ Para darse de baja de la lista ES-TEX debe enviarse a LISTSERV@LIST-
+ SERV.REDIRIS.ES un mensaje que contenga en el cuerpo
+
+
+ unsubscribe ES-TEX
+
+
+
+ Existen otras muchas opciones, para obtener un listado de las mismas
+ debe enviarse a LISTSERV@LISTSERV.REDIRIS.ES un mensaje que contenga
+ en el cuerpo
+
+
+ HELP
+
+
+
+ siendo especialmente interesantes las opciones (NO)MAIL, que regula si
+ se recibe un mensaje por cada contribucin a ES-TEX, (NO)REPRO que
+ regula si se reciben los mensajes enviados por uno mismo y (NO)ACK que
+ regula si se recibe confirmacin de distribucin. Para todas ellas se
+ enva un mensaje que contenga en el cuerpo set ES-TEX opcion, por
+ ejemplo
+
+
+ set ES-TEX ACK
+ set ES-TEX NOACK
+
+
+
+ Para obtener informacin sobre el uso de las listas de RedIris tambin
+ puede visitarse la pgina http://www.rediris.es/list/utiliza-
+ cion.es.html o sobre listserv en general (en ingls)
+ http://www.rediris.es/list/doc/user.html o ver la gua de referencia
+ (tambin en ingls) http://www.rediris.es/list/comandos/info-ref-
+ card.html
+
+ Por favor, NO mandar peticiones de suscripcin o des-suscripcin a la
+ propia lista (es-tex).
+
+
+ 11.2.2. Cuando contesto a alguien de la lista, quin recibe la
+ respuesta? El que mand el mensaje o la lista entera?
+
+ Por omisin, se contesta a la lista entera, salvo que el remitente
+ incluya un campo Reply-To explcito.
+
+
+ 11.2.3. Se archiva en algn sitio la lista es-tex ?
+
+ S, en http://listserv.rediris.es/archives/es-tex.html
+
+
+ 11.2.4. Recibo correo de muchas listas. Cmo puedo filtrar lo que
+ venga de la lista es-tex ?
+
+ Todo lo que viene de es-tex tiene actualmente un campo de la forma:
+
+
+ Sender: Usuarios hispanohablantes de TeX <ES-TEX@LISTSERV.REDIRIS.ES>
+
+
+
+ Si utilizamos un filtro llamado procmail (es software libre), podemos
+ poner las siguientes tres lneas en el archivo de configuracin .proc-
+ mailrc:
+
+
+ :0
+ * ^Sender:.*<ES-TEX@LISTSERV.REDIRIS.ES>
+ spanish-tex
+
+
+
+ y todo lo que venga de es-tex se ir solito al archivo spanish-tex.
+
+
+ Es posible que algunos clientes de correo que permitan filtrado de los
+ mensajes a partir de sus cabeceras puedan intentar verificar si el
+ campo Sender contiene <ES-TEX@LISTSERV.REDIRIS.ES> o algo parecido,
+ pero eso debe comprobarse en cada caso.
+
+
+
+ 11.2.5. Cmo es que hay tanta gente de fuera de Espaa en la lista?
+
+ El tema previsto de esta lista era el uso de TeX para la produccin de
+ documentos en castellano, no para discutir en castellano acerca de TeX
+ ni el uso de TeX en Espaa. Esto no es rgido, pero no pretende ser
+ una lista espaola. No se excluyen tampoco discusiones acerca de las
+ otras lenguas espaolas (cataln, euskera, gallego, ingls, :-) pero
+ gran parte de la audiencia no estar interesada.
+
+
+ 11.3. Las listas spanish-tex y sptex
+
+ ATENCIN. Las listas spanish-tex y sptex estn obsoletas. En su lugar
+ debe utilizarse la lista es-tex. Vase ``lista es-tex''.
+
+
+ 11.3.1. Se archiva en algn sitio la lista spanish-tex ?
+
+ Antiguamente, en la siguiente direccin se archivaban los mensajes de
+ la lista spanish-tex
+
+ http://majordomo.eunet.es/listserv/spanish-tex/
+
+
+ junto con las instrucciones de acceso a la lista. Sin embargo, hace
+ tiempo que no est operativa.
+
+
+ 11.3.2. Se archiva en algn sitio la lista sptex ?
+
+ S, en http://www2.cica.es/ListasD/sptex/, al menos temporalmente.
+
+
+ 11.4. El grupo de noticias es.comp.lenguajes.tex
+
+ Una fuente de informacin alternativa es el grupo de noticias
+ es.comp.lenguajes.tex, aunque tiene bastante menos trfico que la
+ lista de correo. Este es el grupo de noticias principal sobre TeX en
+ espaol.
+
+
+ 11.5. El grupo de noticias es.eunet.spanish-tex
+
+ Antes exista una pasarela (gateway) entre la lista y el grupo de
+ noticias es.eunet.spanish-tex, pero actualmente no funciona. Adems
+ este grupo ya no es de acceso general, sino que es propio de la red
+ eunet.
+
+
+ 12. Meta-preguntas (preguntas sobre esta FAQ):
+
+ 12.1. Cul es la historia de esta FAQ?
+
+ La primera versin de esta FAQ se la debemos a Julio Snchez que
+ recopil preguntas y respuestas a partir de las discusiones habidas en
+ la lista spanish-tex.
+
+ Posteriormente Santiago Vila (sanvila _AT_ unex.es) se hizo cargo de
+ la FAQ, aadiendo ms preguntas y pasndola a texinfo.
+
+ Ms recientemente, Agustn Martn (agustin.martin _AT_ hispalinux.es)
+ se ha hecho cargo de ella en el 99 y la ha pasado a SGML, con la misma
+ intencin con la que Santiago la pas a texinfo, extraer de forma
+ sencilla versiones en distintos formatos.
+
+
+ Esta lista de preguntas y respuestas est muy verde, y actualmente
+ sigue siendo algo catica. Se ruega algo de intolerancia activa, es
+ decir, siempre que se vea algo mal, comunquese al coordinador de la
+ FAQ. Se aceptan cambios, correcciones (incluso ortogrficas o de
+ estilo), adiciones, etc. Ni Julio Snchez ni Santiago Vila se hacen
+ cargo en este momento de la FAQ, as que por favor no le mandis las
+ preguntas a ellos, sino a la persona que en este momento se hace cargo
+ de la FAQ.
+
+
+ 12.2. Quin coordina actualmente la FAQ?
+
+ El coordinador actual y a quien deben enviarse las sugerencias acerca
+ de esta FAQ es: Agustn Martn Domingo, agustin.martin _AT_
+ hispalinux.es
+
+ Se ruega especificar en la cabecera del mensaje FAQ-CervanTeX. Por
+ favor, para dudas generales dirigirse a la lista de correo o al foro
+ de noticias. Utilizar esta direccin exclusivamente para asuntos
+ relacionados con la FAQ.
+
+
+ 12.3. Agradecimientos
+
+ Para hacer esta FAQ se han utilizado, adems de los originales de
+ Julio Snchez y Santiago Vila las FAQ del grupo de noticias
+ comp.text.tex y la New TeX FAQ, versin de la anterior realizada por
+ el grupo de usuarios de TeX del Reino Unido. La versin html de esta
+ FAQ con un buscador CGI (http://www.tex.ac.uk/cgi-bin/texfaq2html)
+ tambin ha sido de gran ayuda. Asimismo se han utilizado multitud de
+ mensajes de las listas de correo y grupos de noticias relacionados con
+ TeX a cuyos autores agradezco sus ideas y contribuciones.
+
+ Fernando M. Fournon Gonzlez Barcia (furny _AT_ wd.estec.nl) y Jess
+ M. Gonzlez Barahona (jgb _AT_ gsyc.inf.uc3m.es) han proporcionado las
+ citas de las publicaciones de la Real Academia y del diccionario de
+ Mara Moliner. La seccin acerca de las funciones matemticas en
+ castellano se la debemos a Juan Luis Varona (jvarona _AT_
+ dmc.unirioja.es) y las de postscript y PDF a Enrique Melendez Asensio
+ . Adems se han tomado muchos elementos (buena parte de las secciones
+ de libros en ingls y de ventajas y desventajas de LaTeX) de las
+ pgina sobre LaTeX de Antonio Gonzlez, de la Universidad de Sevilla
+ (http://www.esi.us.es/~gonfer/tex.html) y otros cuantos de la pgina
+ de Martn Pavn (http://mate.dm.uba.ar/~mpavon/tex.html)
+
+
+ 12.4. Dnde encuentro la versin ms reciente de esta FAQ?
+
+ La versin ms reciente de esta FAQ est disponible en el directorio
+
+ http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX/
+
+
+ en una amplia variedad de formatos. Se puede acceder a travs de la
+ pgina
+
+ http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX-
+ main.html
+
+
+
+ 12.5. Dnde puedo encontrar otras FAQ, aunque sea en otros idiomas?
+
+ Adems de la FAQ en castellano existen FAQ en otros idiomas que, si se
+ salva la barrera del lenguaje pueden ser de utilidad adicional. Sin
+ duda en ellas existen elementos que podran entrar bien en esta FAQ,
+ as que todo aquel que vea una pregunta de gran inters que est en
+ una de ellas y no en la FAQ en castellano est invitado a traducirla y
+ envirsela al responsable de esta FAQ. Las FAQ en otros idiomas ms
+ interesantes son las siguientes
+
+ El grupo de usuarios de TeX/LaTeX del Reino Unido mantiene una
+ excelente FAQ en ingls que puede encontrarse en CTAN en el
+ directorio CTAN:usergrps/uktug/faq. La pgina web de la UK-FAQ
+ http://www.tex.ac.uk/cgi-bin/texfaq2html tiene adems un buscador
+ CGI para facilitar las consultas. Existe una muy interesante FAQ
+ visual, es decir, un documento donde aparecen destacado ciertos
+ elementos con hiperenlaces a la FAQ inglesa. Realmente merece la
+ pena echarle un vistazo. Se encuentra en http://www.ctan.org/tex-
+ archive/info/visualFAQ/visualFAQ.pdf
+
+ Asimismo, el grupo alemn DANTE de usuarios de TeX/LaTeX mantiene
+ su FAQ (en alemn) que puede encontrarse en el CTAN en el
+ directorio CTAN:help/de-tex-faq.
+
+ Aunque congelada desde hace algn tiempo, existe una FAQ en francs
+ en CTAN:help/LaTeX-FAQ-francaise
+
+
+
diff --git a/help/es-tex-faq/FAQ-CervanTeX.pdf b/help/es-tex-faq/FAQ-CervanTeX.pdf
new file mode 100644
index 0000000000..9e8998a08f
--- /dev/null
+++ b/help/es-tex-faq/FAQ-CervanTeX.pdf
@@ -0,0 +1,10575 @@
+%PDF-1.4
+5 0 obj
+<< /S /GoTo /D (section.1) >>
+endobj
+8 0 obj
+(\277Qu\351 son TeX y sus programas hermanos? )
+endobj
+9 0 obj
+<< /S /GoTo /D (subsection.1.1) >>
+endobj
+12 0 obj
+(\277Qu\351 es TeX? )
+endobj
+13 0 obj
+<< /S /GoTo /D (subsection.1.2) >>
+endobj
+16 0 obj
+(\277Por qu\351 debo asegurarme de usar TeX 3.X? )
+endobj
+17 0 obj
+<< /S /GoTo /D (subsection.1.3) >>
+endobj
+20 0 obj
+(Si TeX es tan bueno, \277por qu\351 es gratuito? )
+endobj
+21 0 obj
+<< /S /GoTo /D (subsection.1.4) >>
+endobj
+24 0 obj
+(\277Qu\351 es LaTeX? )
+endobj
+25 0 obj
+<< /S /GoTo /D (subsection.1.5) >>
+endobj
+28 0 obj
+(\277Qu\351 es LaTeX2e?, \277Por qu\351 debo usarlo si me va bien con el otro \(LaTeX209\)? )
+endobj
+29 0 obj
+<< /S /GoTo /D (subsection.1.6) >>
+endobj
+32 0 obj
+(\277Qu\351 son los paquetes de la AMS \(AMS-TeX, AMS-LaTeX\)? )
+endobj
+33 0 obj
+<< /S /GoTo /D (subsection.1.7) >>
+endobj
+36 0 obj
+(\277Qu\351 es METAFONT? )
+endobj
+37 0 obj
+<< /S /GoTo /D (section.2) >>
+endobj
+40 0 obj
+(\277Qu\351 ventajas e inconvenientes tiene TeX/LaTeX? )
+endobj
+41 0 obj
+<< /S /GoTo /D (subsection.2.1) >>
+endobj
+44 0 obj
+(Ventajas frente a otros procesadores. )
+endobj
+45 0 obj
+<< /S /GoTo /D (subsection.2.2) >>
+endobj
+48 0 obj
+(Inconvenientes o m\341s bien, \277cu\341les son las cr\355ticas m\341s habituales? )
+endobj
+49 0 obj
+<< /S /GoTo /D (section.3) >>
+endobj
+52 0 obj
+(\277Qu\351 documentaci\363n hay disponible sobre TeX/LaTeX? )
+endobj
+53 0 obj
+<< /S /GoTo /D (subsection.3.1) >>
+endobj
+56 0 obj
+(Tutoriales de LaTeX en castellano. )
+endobj
+57 0 obj
+<< /S /GoTo /D (subsection.3.2) >>
+endobj
+60 0 obj
+(Libros en castellano )
+endobj
+61 0 obj
+<< /S /GoTo /D (subsection.3.3) >>
+endobj
+64 0 obj
+(Tutoriales en otros idiomas )
+endobj
+65 0 obj
+<< /S /GoTo /D (subsection.3.4) >>
+endobj
+68 0 obj
+(Libros en otros idiomas )
+endobj
+69 0 obj
+<< /S /GoTo /D (subsection.3.5) >>
+endobj
+72 0 obj
+(Revistas. )
+endobj
+73 0 obj
+<< /S /GoTo /D (section.4) >>
+endobj
+76 0 obj
+(\277Que elementos intervienen al procesar un documento con LaTeX? )
+endobj
+77 0 obj
+<< /S /GoTo /D (subsection.4.1) >>
+endobj
+80 0 obj
+(El documento fuente: \277C\363mo creo un documento con LaTeX, lo proceso, lo veo y lo imprimo? )
+endobj
+81 0 obj
+<< /S /GoTo /D (subsection.4.2) >>
+endobj
+84 0 obj
+(\277Qu\351 es un archivo DVI? )
+endobj
+85 0 obj
+<< /S /GoTo /D (subsection.4.3) >>
+endobj
+88 0 obj
+(\277Qu\351 es un conversor \(driver\)? )
+endobj
+89 0 obj
+<< /S /GoTo /D (subsection.4.4) >>
+endobj
+92 0 obj
+(\277Qu\351 son los archivos .pk? )
+endobj
+93 0 obj
+<< /S /GoTo /D (subsection.4.5) >>
+endobj
+96 0 obj
+(\277Qu\351 son los archivos .tfm? )
+endobj
+97 0 obj
+<< /S /GoTo /D (subsection.4.6) >>
+endobj
+100 0 obj
+(\277Qu\351 son los tipos \(fuentes\) CM? )
+endobj
+101 0 obj
+<< /S /GoTo /D (subsection.4.7) >>
+endobj
+104 0 obj
+(\277Qu\351 son los tipos \(fuentes\) EC/DC? )
+endobj
+105 0 obj
+<< /S /GoTo /D (subsection.4.8) >>
+endobj
+108 0 obj
+(\277Qu\351 son los tipos \(fuentes\) virtuales? )
+endobj
+109 0 obj
+<< /S /GoTo /D (subsection.4.9) >>
+endobj
+112 0 obj
+(\277Qu\351 son las \363rdenes "026E30F special? )
+endobj
+113 0 obj
+<< /S /GoTo /D (subsection.4.10) >>
+endobj
+116 0 obj
+(\277Qu\351 es el postscript y el postscript encapsulado \(archivos .eps\)? \040)
+endobj
+117 0 obj
+<< /S /GoTo /D (subsection.4.11) >>
+endobj
+120 0 obj
+(\277Qu\351 es el formato pdf? )
+endobj
+121 0 obj
+<< /S /GoTo /D (subsection.4.12) >>
+endobj
+124 0 obj
+(\277Qu\351 son los paquetes en LaTeX? )
+endobj
+125 0 obj
+<< /S /GoTo /D (subsection.4.13) >>
+endobj
+128 0 obj
+(\277Qu\351 son los archivos .dtx? )
+endobj
+129 0 obj
+<< /S /GoTo /D (section.5) >>
+endobj
+132 0 obj
+(\277C\363mo consigo LaTeX y otros programas relacionados? )
+endobj
+133 0 obj
+<< /S /GoTo /D (subsection.5.1) >>
+endobj
+136 0 obj
+(Distribuciones TeX/LaTeX )
+endobj
+137 0 obj
+<< /S /GoTo /D (subsubsection.5.1.1) >>
+endobj
+140 0 obj
+(Distribuciones libres o shareware )
+endobj
+141 0 obj
+<< /S /GoTo /D (subsubsection.5.1.2) >>
+endobj
+144 0 obj
+(Distribuciones comerciales )
+endobj
+145 0 obj
+<< /S /GoTo /D (subsection.5.2) >>
+endobj
+148 0 obj
+(Editores de texto que trabajan especialmente bien con LaTeX )
+endobj
+149 0 obj
+<< /S /GoTo /D (section.6) >>
+endobj
+152 0 obj
+(Preguntas espec\355ficas para el LaTeX en castellano )
+endobj
+153 0 obj
+<< /S /GoTo /D (subsection.6.1) >>
+endobj
+156 0 obj
+(\277C\363mo puedo usar TeX en castellano? o \277Qu\351 es lo m\355nimo que hay que saber para escribir en castellano con TeX/LaTeX? )
+endobj
+157 0 obj
+<< /S /GoTo /D (subsection.6.2) >>
+endobj
+160 0 obj
+(Con LaTeX, \277c\363mo puedo escribir los acentos y dem\341s caracteres extendidos? \040)
+endobj
+161 0 obj
+<< /S /GoTo /D (subsubsection.6.2.1) >>
+endobj
+164 0 obj
+(Mediante \363rdenes LaTeX \040)
+endobj
+165 0 obj
+<< /S /GoTo /D (subsubsection.6.2.2) >>
+endobj
+168 0 obj
+(Directamente mediante el paquete inputenc )
+endobj
+169 0 obj
+<< /S /GoTo /D (subsubsection.6.2.3) >>
+endobj
+172 0 obj
+(\277C\363mo introducir acentos en modo matem\341tico? )
+endobj
+173 0 obj
+<< /S /GoTo /D (subsection.6.3) >>
+endobj
+176 0 obj
+(\277Puedo compartir mis archivos LaTeX en los que he escrito los acentos directamente? )
+endobj
+177 0 obj
+<< /S /GoTo /D (subsection.6.4) >>
+endobj
+180 0 obj
+(\277Por qu\351 cuando se selecciona texto en Adobe Reader o xpdf, desde un documento PDF generado con LaTeX, las letras acentuadas y e\361es no se copian bien? )
+endobj
+181 0 obj
+<< /S /GoTo /D (subsection.6.5) >>
+endobj
+184 0 obj
+(\277C\363mo cambiar los literales que produce LaTeX?)
+endobj
+185 0 obj
+<< /S /GoTo /D (subsection.6.6) >>
+endobj
+188 0 obj
+(\277C\363mo hacer que LaTeX parta correctamente las palabras en castellano?)
+endobj
+189 0 obj
+<< /S /GoTo /D (subsubsection.6.6.1) >>
+endobj
+192 0 obj
+(\277Qu\351 configuraciones \(o patterns\) existen para la partici\363n de palabras?)
+endobj
+193 0 obj
+<< /S /GoTo /D (subsubsection.6.6.2) >>
+endobj
+196 0 obj
+(\277C\363mo activo el patr\363n de partici\363n de palabras para el castellano?)
+endobj
+197 0 obj
+<< /S /GoTo /D (subsubsection.6.6.3) >>
+endobj
+200 0 obj
+(A pesar de que he activado los patrones de partici\363n de palabras del castellano, hay una palabra que se me resiste)
+endobj
+201 0 obj
+<< /S /GoTo /D (subsubsection.6.6.4) >>
+endobj
+204 0 obj
+(Mi TeX no parte las palabras que tienen acentos. \277Por qu\351?)
+endobj
+205 0 obj
+<< /S /GoTo /D (subsection.6.7) >>
+endobj
+208 0 obj
+(Acerca de spanish.sty)
+endobj
+209 0 obj
+<< /S /GoTo /D (subsubsection.6.7.1) >>
+endobj
+212 0 obj
+(\277D\363nde se puede obtener la documentaci\363n de spanish en castellano? )
+endobj
+213 0 obj
+<< /S /GoTo /D (subsubsection.6.7.2) >>
+endobj
+216 0 obj
+(\277C\363mo cambio los nombres de las secciones de bibliograf\355a, \355ndice, etc... que pone spanish.sty? )
+endobj
+217 0 obj
+<< /S /GoTo /D (subsubsection.6.7.3) >>
+endobj
+220 0 obj
+(\277Por qu\351 spanish.sty pone los meses en min\372scula?)
+endobj
+221 0 obj
+<< /S /GoTo /D (subsubsection.6.7.4) >>
+endobj
+224 0 obj
+(\277Por qu\351 el spanish de babel reemplaza el punto decimal por una coma?)
+endobj
+225 0 obj
+<< /S /GoTo /D (subsubsection.6.7.5) >>
+endobj
+228 0 obj
+(\277Por qu\351 spanish.sty pone los n\372meros romanos siempre en may\372scula?)
+endobj
+229 0 obj
+<< /S /GoTo /D (subsubsection.6.7.6) >>
+endobj
+232 0 obj
+(\277Por qu\351 spanish.sty acent\372a la I de \315ndice?)
+endobj
+233 0 obj
+<< /S /GoTo /D (subsubsection.6.7.7) >>
+endobj
+236 0 obj
+(\277Por qu\351 spanish para babel dice cuadro en lugar de tabla?)
+endobj
+237 0 obj
+<< /S /GoTo /D (subsubsection.6.7.8) >>
+endobj
+240 0 obj
+(\277C\363mo consigo que babel y spanish.sty no utilicen los atajos de teclado NUNCA?)
+endobj
+241 0 obj
+<< /S /GoTo /D (subsection.6.8) >>
+endobj
+244 0 obj
+(\277C\363mo puedo indicar la abreviatura de los ordinales? )
+endobj
+245 0 obj
+<< /S /GoTo /D (subsection.6.9) >>
+endobj
+248 0 obj
+(\277C\363mo forzar sangr\355a despu\351s de las cabeceras? )
+endobj
+249 0 obj
+<< /S /GoTo /D (subsection.6.10) >>
+endobj
+252 0 obj
+(\277C\363mo puedo escribir las funciones matem\341ticas en espa\361ol? )
+endobj
+253 0 obj
+<< /S /GoTo /D (subsection.6.11) >>
+endobj
+256 0 obj
+(\277Qu\351 verificadores ortogr\341ficos puedo utilizar para espa\361ol?)
+endobj
+257 0 obj
+<< /S /GoTo /D (subsection.6.12) >>
+endobj
+260 0 obj
+(\277C\363mo utilizo BibTeX en castellano?)
+endobj
+261 0 obj
+<< /S /GoTo /D (subsubsection.6.12.1) >>
+endobj
+264 0 obj
+(Utilizar estilos adaptables \(los abstyles\) )
+endobj
+265 0 obj
+<< /S /GoTo /D (subsubsection.6.12.2) >>
+endobj
+268 0 obj
+(Utilizar el paquete custom-bib )
+endobj
+269 0 obj
+<< /S /GoTo /D (subsection.6.13) >>
+endobj
+272 0 obj
+(\277C\363mo genero un \355ndice alfab\351tico con la ordenaci\363n correcta en castellano?)
+endobj
+273 0 obj
+<< /S /GoTo /D (section.7) >>
+endobj
+276 0 obj
+(\277Que es...?)
+endobj
+277 0 obj
+<< /S /GoTo /D (subsection.7.1) >>
+endobj
+280 0 obj
+(\277Qu\351 es el CTAN \(Comprehensive TeX Archive Network\).)
+endobj
+281 0 obj
+<< /S /GoTo /D (subsection.7.2) >>
+endobj
+284 0 obj
+(\277Qu\351 es el esquema de codificaci\363n de Cork?)
+endobj
+285 0 obj
+<< /S /GoTo /D (subsection.7.3) >>
+endobj
+288 0 obj
+(\277Qu\351 es babel?)
+endobj
+289 0 obj
+<< /S /GoTo /D (subsection.7.4) >>
+endobj
+292 0 obj
+(\277Qu\351 son eTeX, eLaTeX y omega?)
+endobj
+293 0 obj
+<< /S /GoTo /D (subsection.7.5) >>
+endobj
+296 0 obj
+(\277Qu\351 es RevTeX?)
+endobj
+297 0 obj
+<< /S /GoTo /D (subsection.7.6) >>
+endobj
+300 0 obj
+(\277Qu\351 es una box y cu\341ndo conviene utilizarlas? \040)
+endobj
+301 0 obj
+<< /S /GoTo /D (section.8) >>
+endobj
+304 0 obj
+(\277C\363mo hago ...?)
+endobj
+305 0 obj
+<< /S /GoTo /D (subsection.8.1) >>
+endobj
+308 0 obj
+(\277C\363mo y d\363nde instalo nuevos paquetes o archivos de estilo?)
+endobj
+309 0 obj
+<< /S /GoTo /D (subsubsection.8.1.1) >>
+endobj
+312 0 obj
+(D\363nde buscar un paquete nuevo y qu\351 traer)
+endobj
+313 0 obj
+<< /S /GoTo /D (subsubsection.8.1.2) >>
+endobj
+316 0 obj
+(\277Qu\351 es cada uno de los archivos que traigo?)
+endobj
+317 0 obj
+<< /S /GoTo /D (subsubsection.8.1.3) >>
+endobj
+320 0 obj
+(Extrayendo archivos de estilo de los .dtx y .ins)
+endobj
+321 0 obj
+<< /S /GoTo /D (subsubsection.8.1.4) >>
+endobj
+324 0 obj
+(\277D\363nde colocar nuevos archivos de estilo? )
+endobj
+325 0 obj
+<< /S /GoTo /D (subsubsection.8.1.5) >>
+endobj
+328 0 obj
+(Activando ramas locales y personales del \341rbol de directorios LaTeX global )
+endobj
+329 0 obj
+<< /S /GoTo /D (subsubsection.8.1.6) >>
+endobj
+332 0 obj
+(Rehaciendo la base de datos de archivos instalados )
+endobj
+333 0 obj
+<< /S /GoTo /D (subsubsection.8.1.7) >>
+endobj
+336 0 obj
+(\277C\363mo verifico los directorios en los que TeX busca archivos de estilo? )
+endobj
+337 0 obj
+<< /S /GoTo /D (subsection.8.2) >>
+endobj
+340 0 obj
+(\277C\363mo personalizo el aspecto del documento? )
+endobj
+341 0 obj
+<< /S /GoTo /D (subsubsection.8.2.1) >>
+endobj
+344 0 obj
+(\277C\363mo cambio la fuente de un documento o instalo nuevas? )
+endobj
+345 0 obj
+<< /S /GoTo /D (subsubsection.8.2.2) >>
+endobj
+348 0 obj
+(\277Puedo utilizar una fuente TrueType como Arial en LaTeX? )
+endobj
+349 0 obj
+<< /S /GoTo /D (subsubsection.8.2.3) >>
+endobj
+352 0 obj
+(Incluyendo subdocumentos TeX/LaTeX en el documento )
+endobj
+353 0 obj
+<< /S /GoTo /D (subsubsection.8.2.4) >>
+endobj
+356 0 obj
+(\277C\363mo evito que salga la palabra cap\355tulo en las cabeceras de cap\355tulo?)
+endobj
+357 0 obj
+<< /S /GoTo /D (subsubsection.8.2.5) >>
+endobj
+360 0 obj
+(\277C\363mo cambio la cabecera de cap\355tulo por otra m\341s a mi gusto?)
+endobj
+361 0 obj
+<< /S /GoTo /D (subsubsection.8.2.6) >>
+endobj
+364 0 obj
+(Quiero una secci\363n no numerada, pero que aparezca en la tabla de materias.)
+endobj
+365 0 obj
+<< /S /GoTo /D (subsubsection.8.2.7) >>
+endobj
+368 0 obj
+(No me funciona "026E30F subsubsubsection.)
+endobj
+369 0 obj
+<< /S /GoTo /D (subsubsection.8.2.8) >>
+endobj
+372 0 obj
+(\277C\363mo quito los encabezados que LaTeX pone autom\341ticamente en las p\341ginas blancas? )
+endobj
+373 0 obj
+<< /S /GoTo /D (subsubsection.8.2.9) >>
+endobj
+376 0 obj
+(\277C\363mo quito los encabezados, pies o la numeraci\363n de las p\341ginas? )
+endobj
+377 0 obj
+<< /S /GoTo /D (subsubsection.8.2.10) >>
+endobj
+380 0 obj
+(\277C\363mo pongo encabezados o pies de p\341gina a mi gusto? )
+endobj
+381 0 obj
+<< /S /GoTo /D (subsubsection.8.2.11) >>
+endobj
+384 0 obj
+(\277C\363mo hago que LaTeX y TeX no partan nunca las palabras?)
+endobj
+385 0 obj
+<< /S /GoTo /D (subsubsection.8.2.12) >>
+endobj
+388 0 obj
+(\277C\363mo ajusto los m\341rgenes de un documento LaTeX?)
+endobj
+389 0 obj
+<< /S /GoTo /D (subsubsection.8.2.13) >>
+endobj
+392 0 obj
+(\277C\363mo obtengo un documento apaisado?)
+endobj
+393 0 obj
+<< /S /GoTo /D (subsubsection.8.2.14) >>
+endobj
+396 0 obj
+(\277C\363mo ajusto el espaciado en el documento LaTeX?)
+endobj
+397 0 obj
+<< /S /GoTo /D (subsection.8.3) >>
+endobj
+400 0 obj
+(Listas al gusto de cada cual.)
+endobj
+401 0 obj
+<< /S /GoTo /D (subsubsection.8.3.1) >>
+endobj
+404 0 obj
+(\277C\363mo ajusto el espaciado en una lista?)
+endobj
+405 0 obj
+<< /S /GoTo /D (subsubsection.8.3.2) >>
+endobj
+408 0 obj
+(\277C\363mo cambio el tipo de numeraci\363n en las listas numeradas?)
+endobj
+409 0 obj
+<< /S /GoTo /D (subsubsection.8.3.3) >>
+endobj
+412 0 obj
+(Quiero mostrar un s\355mbolo distinto en las listas itemize)
+endobj
+413 0 obj
+<< /S /GoTo /D (subsubsection.8.3.4) >>
+endobj
+416 0 obj
+(\277Puedo ajustar la separaci\363n entre texto y listas?)
+endobj
+417 0 obj
+<< /S /GoTo /D (subsubsection.8.3.5) >>
+endobj
+420 0 obj
+(\277C\363mo interrumpir una lista numerada con un comentario y continuar despu\351s con la numeraci\363n correcta?)
+endobj
+421 0 obj
+<< /S /GoTo /D (subsubsection.8.3.6) >>
+endobj
+424 0 obj
+(\277Puedo hacer listas en paralelo?)
+endobj
+425 0 obj
+<< /S /GoTo /D (subsection.8.4) >>
+endobj
+428 0 obj
+(Referencias cruzadas, \355ndices, bibliograf\355as y tablas de materias.)
+endobj
+429 0 obj
+<< /S /GoTo /D (subsubsection.8.4.1) >>
+endobj
+432 0 obj
+(\277Hay alguna herramienta de gesti\363n de bases de datos bibliogr\341ficas en BibTeX? )
+endobj
+433 0 obj
+<< /S /GoTo /D (subsubsection.8.4.2) >>
+endobj
+436 0 obj
+(\277C\363mo introduzco la bibliograf\355a o el \355ndice en la tabla de materias?)
+endobj
+437 0 obj
+<< /S /GoTo /D (subsubsection.8.4.3) >>
+endobj
+440 0 obj
+(\277C\363mo pongo el \355ndice con su contenido al principio de cada cap\355tulo?)
+endobj
+441 0 obj
+<< /S /GoTo /D (subsubsection.8.4.4) >>
+endobj
+444 0 obj
+(\277C\363mo a\361ado bibliograf\355a al final de cada cap\355tulo en LaTeX?)
+endobj
+445 0 obj
+<< /S /GoTo /D (subsubsection.8.4.5) >>
+endobj
+448 0 obj
+(\277C\363mo divido la bibliograf\355a por temas en LaTeX?)
+endobj
+449 0 obj
+<< /S /GoTo /D (subsubsection.8.4.6) >>
+endobj
+452 0 obj
+(\277C\363mo cito una p\341gina de una referencia bibliogr\341fica?)
+endobj
+453 0 obj
+<< /S /GoTo /D (subsubsection.8.4.7) >>
+endobj
+456 0 obj
+(\277C\363mo cito una url con BibTeX?)
+endobj
+457 0 obj
+<< /S /GoTo /D (subsubsection.8.4.8) >>
+endobj
+460 0 obj
+(\277C\363mo colapso una serie de citas consecutivas?)
+endobj
+461 0 obj
+<< /S /GoTo /D (subsubsection.8.4.9) >>
+endobj
+464 0 obj
+(\277C\363mo hago una referencia cruzada a un documento externo?)
+endobj
+465 0 obj
+<< /S /GoTo /D (subsubsection.8.4.10) >>
+endobj
+468 0 obj
+(Afinando el aspecto de la tabla de materias o listas de figuras y tablas. )
+endobj
+469 0 obj
+<< /S /GoTo /D (subsection.8.5) >>
+endobj
+472 0 obj
+(\277C\363mo introduzco dibujos, diagramas e im\341genes en LaTeX?)
+endobj
+473 0 obj
+<< /S /GoTo /D (subsubsection.8.5.1) >>
+endobj
+476 0 obj
+(Dibujando con TeX)
+endobj
+477 0 obj
+<< /S /GoTo /D (subsubsection.8.5.2) >>
+endobj
+480 0 obj
+(Introduciendo figuras postscript encapsulado en LaTeX)
+endobj
+481 0 obj
+<< /S /GoTo /D (subsubsection.8.5.3) >>
+endobj
+484 0 obj
+(Introduciendo im\341genes en mapa de bits en LaTeX.)
+endobj
+485 0 obj
+<< /S /GoTo /D (subsubsection.8.5.4) >>
+endobj
+488 0 obj
+(Inclusi\363n de una imagen desde un PDF con m\372ltiples p\341ginas.)
+endobj
+489 0 obj
+<< /S /GoTo /D (subsubsection.8.5.5) >>
+endobj
+492 0 obj
+(Introduciendo c\363digo y figuras postscript en pdfTeX \040)
+endobj
+493 0 obj
+<< /S /GoTo /D (subsubsection.8.5.6) >>
+endobj
+496 0 obj
+(\277C\363mo coloco un fragmento TeX en una figura?)
+endobj
+497 0 obj
+<< /S /GoTo /D (subsection.8.6) >>
+endobj
+500 0 obj
+(Figuras, tablas y elementos flotantes)
+endobj
+501 0 obj
+<< /S /GoTo /D (subsubsection.8.6.1) >>
+endobj
+504 0 obj
+(\277C\363mo puedo poner una figura rodeada de texto?)
+endobj
+505 0 obj
+<< /S /GoTo /D (subsubsection.8.6.2) >>
+endobj
+508 0 obj
+(\277C\363mo puedo poner una figura a dos columnas?)
+endobj
+509 0 obj
+<< /S /GoTo /D (subsubsection.8.6.3) >>
+endobj
+512 0 obj
+(\277C\363mo consigo un mayor control de la posici\363n de figuras y dem\341s elementos flotantes?)
+endobj
+513 0 obj
+<< /S /GoTo /D (subsubsection.8.6.4) >>
+endobj
+516 0 obj
+(\277Puedo poner una figura en una tabla?)
+endobj
+517 0 obj
+<< /S /GoTo /D (subsubsection.8.6.5) >>
+endobj
+520 0 obj
+(\277C\363mo colocar dos figuras o tablas juntas de distintas formas?, )
+endobj
+521 0 obj
+<< /S /GoTo /D (subsubsection.8.6.6) >>
+endobj
+524 0 obj
+(\277Puedo poner un pie en tablas y figuras que no flotan?, )
+endobj
+525 0 obj
+<< /S /GoTo /D (subsubsection.8.6.7) >>
+endobj
+528 0 obj
+(\277C\363mo hago para incluir elementos flotantes grandes o numerosos sin que den errores o se vayan al final?)
+endobj
+529 0 obj
+<< /S /GoTo /D (subsection.8.7) >>
+endobj
+532 0 obj
+(\277C\363mo giro un elemento en un documento LaTeX?)
+endobj
+533 0 obj
+<< /S /GoTo /D (subsection.8.8) >>
+endobj
+536 0 obj
+(\277C\363mo escribo algunos s\355mbolos?)
+endobj
+537 0 obj
+<< /S /GoTo /D (subsection.8.9) >>
+endobj
+540 0 obj
+(\277C\363mo convierto mis documentos a LaTeX y desde LaTeX?)
+endobj
+541 0 obj
+<< /S /GoTo /D (subsubsection.8.9.1) >>
+endobj
+544 0 obj
+(\277C\363mo obtengo un documento PDF a partir de mi documento TeX? \040)
+endobj
+545 0 obj
+<< /S /GoTo /D (subsubsection.8.9.2) >>
+endobj
+548 0 obj
+(\277C\363mo obtengo una versi\363n texto a partir de un documento PDF?)
+endobj
+549 0 obj
+<< /S /GoTo /D (subsubsection.8.9.3) >>
+endobj
+552 0 obj
+(\277C\363mo obtengo un documento html a partir de mi documento TeX? \040)
+endobj
+553 0 obj
+<< /S /GoTo /D (subsubsection.8.9.4) >>
+endobj
+556 0 obj
+(Convirtiendo a LaTeX desde otros formatos)
+endobj
+557 0 obj
+<< /S /GoTo /D (subsection.8.10) >>
+endobj
+560 0 obj
+(\277C\363mo rehago los formatos de TeX y LaTeX?)
+endobj
+561 0 obj
+<< /S /GoTo /D (subsection.8.11) >>
+endobj
+564 0 obj
+(\277C\363mo llamo a un editor desde TeX/LaTeX?)
+endobj
+565 0 obj
+<< /S /GoTo /D (subsection.8.12) >>
+endobj
+568 0 obj
+(Algunas cosillas matem\341ticas.)
+endobj
+569 0 obj
+<< /S /GoTo /D (subsubsection.8.12.1) >>
+endobj
+572 0 obj
+(\277C\363mo escribo un n\372mero con periodo utilizando LaTeX?)
+endobj
+573 0 obj
+<< /S /GoTo /D (subsubsection.8.12.2) >>
+endobj
+576 0 obj
+(\277C\363mo puedo hacer para que la etiqueta de una ecuaci\363n p.ej. \(3.5\) contenga adem\341s el n\372mero de la secci\363n actual p.ej. \(3.1.5\) )
+endobj
+577 0 obj
+<< /S /GoTo /D (subsubsection.8.12.3) >>
+endobj
+580 0 obj
+(\277C\363mo hay que hacer para lograr la N, R de doble trazo con que se representan los n\372meros naturales, reales, etc...)
+endobj
+581 0 obj
+<< /S /GoTo /D (subsubsection.8.12.4) >>
+endobj
+584 0 obj
+(\277Puedo forzar que una f\363rmula tenga el mismo n\372mero que otra?)
+endobj
+585 0 obj
+<< /S /GoTo /D (subsubsection.8.12.5) >>
+endobj
+588 0 obj
+(\277Puedo escribir s\355mbolos matem\341ticos en negrita?)
+endobj
+589 0 obj
+<< /S /GoTo /D (subsubsection.8.12.6) >>
+endobj
+592 0 obj
+(\277Puedo rotar una ecuaci\363n?)
+endobj
+593 0 obj
+<< /S /GoTo /D (subsubsection.8.12.7) >>
+endobj
+596 0 obj
+(Algunas preguntas matem\341ticas de breve respuesta.)
+endobj
+597 0 obj
+<< /S /GoTo /D (subsection.8.13) >>
+endobj
+600 0 obj
+(\277C\363mo hago cuadernillos, tr\355pticos y documentos con formatos especiales? \040)
+endobj
+601 0 obj
+<< /S /GoTo /D (subsubsection.8.13.1) >>
+endobj
+604 0 obj
+(\277C\363mo hago cuadernillos con TeX o LaTeX?)
+endobj
+605 0 obj
+<< /S /GoTo /D (subsubsection.8.13.2) >>
+endobj
+608 0 obj
+(\277C\363mo hago tr\355pticos con LaTeX?)
+endobj
+609 0 obj
+<< /S /GoTo /D (subsubsection.8.13.3) >>
+endobj
+612 0 obj
+(\277Puedo preparar un p\363ster con TeX/LaTeX? \040)
+endobj
+613 0 obj
+<< /S /GoTo /D (subsubsection.8.13.4) >>
+endobj
+616 0 obj
+(\277Puedo hacer libretos y car\341tulas de CD con LaTeX? )
+endobj
+617 0 obj
+<< /S /GoTo /D (subsection.8.14) >>
+endobj
+620 0 obj
+(\277C\363mo puedo preparar una exposici\363n utilizando LaTeX? )
+endobj
+621 0 obj
+<< /S /GoTo /D (subsubsection.8.14.1) >>
+endobj
+624 0 obj
+(Haciendo transparencias con LaTeX )
+endobj
+625 0 obj
+<< /S /GoTo /D (subsubsection.8.14.2) >>
+endobj
+628 0 obj
+(Haciendo una presentaci\363n con LaTeX )
+endobj
+629 0 obj
+<< /S /GoTo /D (subsubsection.8.14.3) >>
+endobj
+632 0 obj
+(M\341s informaci\363n sobre presentaciones )
+endobj
+633 0 obj
+<< /S /GoTo /D (subsection.8.15) >>
+endobj
+636 0 obj
+(Algunas cosas que a veces se piden para mandar un documento a la imprenta.)
+endobj
+637 0 obj
+<< /S /GoTo /D (subsubsection.8.15.1) >>
+endobj
+640 0 obj
+(Sacando la imagen especular de un archivo \(es decir, con todo al rev\351s\).)
+endobj
+641 0 obj
+<< /S /GoTo /D (subsubsection.8.15.2) >>
+endobj
+644 0 obj
+(Sacando el archivo en negativo \(es decir, blanco sobre negro\).)
+endobj
+645 0 obj
+<< /S /GoTo /D (subsubsection.8.15.3) >>
+endobj
+648 0 obj
+(Marcas de corte.)
+endobj
+649 0 obj
+<< /S /GoTo /D (subsection.8.16) >>
+endobj
+652 0 obj
+(Algunas cuestiones adicionales, o menos FAQ)
+endobj
+653 0 obj
+<< /S /GoTo /D (subsection.8.17) >>
+endobj
+656 0 obj
+(\277He encontrado un error en LaTeX \277C\363mo lo notifico? )
+endobj
+657 0 obj
+<< /S /GoTo /D (section.9) >>
+endobj
+660 0 obj
+(\277Por qu\351 no consigo ...?)
+endobj
+661 0 obj
+<< /S /GoTo /D (subsection.9.1) >>
+endobj
+664 0 obj
+(\277Por qu\351 no salen las im\341genes en mi documento? )
+endobj
+665 0 obj
+<< /S /GoTo /D (subsection.9.2) >>
+endobj
+668 0 obj
+(\277Por qu\351 no salen los caracteres acentuados si yo los escribo bien? )
+endobj
+669 0 obj
+<< /S /GoTo /D (subsection.9.3) >>
+endobj
+672 0 obj
+(\277Por qu\351 no encuentro el archivo babelbst.tex cuando uso custom-bib?)
+endobj
+673 0 obj
+<< /S /GoTo /D (subsection.9.4) >>
+endobj
+676 0 obj
+(\277Por qu\351 a veces no me da el mismo resultado o incluso errores al procesar un documento en dos sistemas distintos?)
+endobj
+677 0 obj
+<< /S /GoTo /D (section.10) >>
+endobj
+680 0 obj
+(Preguntas que se van quedando obsoletas)
+endobj
+681 0 obj
+<< /S /GoTo /D (subsection.10.1) >>
+endobj
+684 0 obj
+(\277Qu\351 es FTC?)
+endobj
+685 0 obj
+<< /S /GoTo /D (subsection.10.2) >>
+endobj
+688 0 obj
+(\277Qu\351 es ML-TeX?)
+endobj
+689 0 obj
+<< /S /GoTo /D (section.11) >>
+endobj
+692 0 obj
+(Informaci\363n sobre LaTeX en castellano)
+endobj
+693 0 obj
+<< /S /GoTo /D (subsection.11.1) >>
+endobj
+696 0 obj
+(El Grupo de Usuarios de TeX Hispanohablantes \(CervanTeX\))
+endobj
+697 0 obj
+<< /S /GoTo /D (subsubsection.11.1.1) >>
+endobj
+700 0 obj
+(\277Qu\351 es CervanTeX?)
+endobj
+701 0 obj
+<< /S /GoTo /D (subsubsection.11.1.2) >>
+endobj
+704 0 obj
+(\277C\363mo puedo entrar en contacto con el grupo de usuarios?)
+endobj
+705 0 obj
+<< /S /GoTo /D (subsection.11.2) >>
+endobj
+708 0 obj
+(La lista es-tex )
+endobj
+709 0 obj
+<< /S /GoTo /D (subsubsection.11.2.1) >>
+endobj
+712 0 obj
+(\277C\363mo funciona la lista es-tex?)
+endobj
+713 0 obj
+<< /S /GoTo /D (subsubsection.11.2.2) >>
+endobj
+716 0 obj
+(Cuando contesto a alguien de la lista, \277qui\351n recibe la respuesta? \277El que mand\363 el mensaje o la lista entera? )
+endobj
+717 0 obj
+<< /S /GoTo /D (subsubsection.11.2.3) >>
+endobj
+720 0 obj
+(\277Se archiva en alg\372n sitio la lista es-tex? )
+endobj
+721 0 obj
+<< /S /GoTo /D (subsubsection.11.2.4) >>
+endobj
+724 0 obj
+(Recibo correo de muchas listas. \277C\363mo puedo filtrar lo que venga de la lista es-tex? )
+endobj
+725 0 obj
+<< /S /GoTo /D (subsubsection.11.2.5) >>
+endobj
+728 0 obj
+(\277C\363mo es que hay tanta gente de fuera de Espa\361a en la lista? )
+endobj
+729 0 obj
+<< /S /GoTo /D (subsection.11.3) >>
+endobj
+732 0 obj
+(Las listas spanish-tex y sptex )
+endobj
+733 0 obj
+<< /S /GoTo /D (subsubsection.11.3.1) >>
+endobj
+736 0 obj
+(\277Se archiva en alg\372n sitio la lista spanish-tex? )
+endobj
+737 0 obj
+<< /S /GoTo /D (subsubsection.11.3.2) >>
+endobj
+740 0 obj
+(\277Se archiva en alg\372n sitio la lista sptex? )
+endobj
+741 0 obj
+<< /S /GoTo /D (subsection.11.4) >>
+endobj
+744 0 obj
+(El grupo de noticias es.comp.lenguajes.tex )
+endobj
+745 0 obj
+<< /S /GoTo /D (subsection.11.5) >>
+endobj
+748 0 obj
+(El grupo de noticias es.eunet.spanish-tex )
+endobj
+749 0 obj
+<< /S /GoTo /D (section.12) >>
+endobj
+752 0 obj
+(Meta-preguntas \(preguntas sobre esta FAQ\): )
+endobj
+753 0 obj
+<< /S /GoTo /D (subsection.12.1) >>
+endobj
+756 0 obj
+(\277Cu\341l es la historia de esta FAQ? )
+endobj
+757 0 obj
+<< /S /GoTo /D (subsection.12.2) >>
+endobj
+760 0 obj
+(\277Qui\351n coordina actualmente la FAQ? )
+endobj
+761 0 obj
+<< /S /GoTo /D (subsection.12.3) >>
+endobj
+764 0 obj
+(Agradecimientos )
+endobj
+765 0 obj
+<< /S /GoTo /D (subsection.12.4) >>
+endobj
+768 0 obj
+(\277D\363nde encuentro la versi\363n m\341s reciente de esta FAQ? )
+endobj
+769 0 obj
+<< /S /GoTo /D (subsection.12.5) >>
+endobj
+772 0 obj
+(\277D\363nde puedo encontrar otras FAQ, aunque sea en otros idiomas? )
+endobj
+773 0 obj
+<< /S /GoTo /D [774 0 R /Fit ] >>
+endobj
+776 0 obj <<
+/Length 3184
+/Filter /FlateDecode
+>>
+stream
+x\ݏB y)6nvWH׿3")SL{$ѐ3pH/(,Y^R+=@󗯘{-ċ4[՛fn{RnV:{;t|s3[UEqլ})J~PDR{+FXa,x_zw3;h +
+IQHw# VpRp%X%1aCZ\~3fUշB 4+:c]rJ--UsgMpBM1ۖBYUy]^s[=6۲͟쥭]5gnxsV]VgLvM]i_Սc=汼s
+# 9ګUa:רkMU (,hA=4+ #t΀Bo'(SyoӁ HyRCJe &
+xaNobnGR|
+y(#ӐDDWn,X(U.G+76Z,XK,6Κ< 0Zh=V55<,eÒTzvo8O{'~zjU=95
+"L¸σiDwn -\ݾ:m ST,i(rI4
+#[&
+_I)!uS](J@d]%?1}f^Mġ#xN SC
+@xDB,'Ms&17s?<5eav`G}[Gjq#w.LK@Q}wC5*x9B{3peH4⻚g vBΈҊ߃!P8R<\QVgz;'ͲUV]@f1&8Peȹƽ~QH)1*9WQiz"\_*E unvU\[m,[j[/}C챼;<'XjBSP|s>~XL`1)k eXLrX qd\5U)Ym<j֕]=/9tĤN3XPhկ̘} uf ɏƝϘ7s<>mں\.}
+
+w8Q{
+XdF*)F12}Lk:6#\!d. Do|u}7$1B]da:12,*xl%Dt4Gt 3P.5a9KX<<qU<ƣ
+)G;B (R&]!4ԯ G2.~%bY |"A(RJxTg}AѿL?_oYendstream
+endobj
+774 0 obj <<
+/Type /Page
+/Contents 776 0 R
+/Resources 775 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 792 0 R 793 0 R 794 0 R 795 0 R 796 0 R 797 0 R 801 0 R 802 0 R 803 0 R 804 0 R 805 0 R 806 0 R 807 0 R 808 0 R 809 0 R 810 0 R 811 0 R 812 0 R 813 0 R 814 0 R 815 0 R 816 0 R 820 0 R ]
+>> endobj
+792 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 525.6706 271.6627 537.1972]
+/Subtype /Link
+/A << /S /GoTo /D (section.1) >>
+>> endobj
+793 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 506.9492 168.5306 517.9379]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.1) >>
+>> endobj
+794 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 488.173 290.1139 499.1617]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.2) >>
+>> endobj
+795 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 469.3968 280.958 480.3854]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.3) >>
+>> endobj
+796 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 450.6206 174.5719 461.6092]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.4) >>
+>> endobj
+797 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 431.8443 426.1967 442.833]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.5) >>
+>> endobj
+801 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 413.0681 355.1262 424.0568]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.6) >>
+>> endobj
+802 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 394.3767 205.3793 405.2806]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.7) >>
+>> endobj
+803 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 365.4983 297.3427 377.0249]
+/Subtype /Link
+/A << /S /GoTo /D (section.2) >>
+>> endobj
+804 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 346.8616 259.1366 357.7656]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.2.1) >>
+>> endobj
+805 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 328.0854 380.0715 338.9893]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.2.2) >>
+>> endobj
+806 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 299.207 322.1495 310.7337]
+/Subtype /Link
+/A << /S /GoTo /D (section.3) >>
+>> endobj
+807 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 280.4856 246.8997 291.4743]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.1) >>
+>> endobj
+808 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 263.8514 193.5831 272.6981]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.2) >>
+>> endobj
+809 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 245.0752 221.6475 253.9219]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.3) >>
+>> endobj
+810 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 226.299 207.71 235.1457]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.4) >>
+>> endobj
+811 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 207.5228 149.3493 216.3695]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.5) >>
+>> endobj
+812 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 176.5871 370.0166 187.7402]
+/Subtype /Link
+/A << /S /GoTo /D (section.4) >>
+>> endobj
+813 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 157.8657 485.7327 168.8544]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.1) >>
+>> endobj
+814 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 139.1743 213.7479 150.0782]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.2) >>
+>> endobj
+815 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 120.3981 235.7751 131.302]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.3) >>
+>> endobj
+816 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 101.6218 225.4537 112.5258]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.4) >>
+>> endobj
+820 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 82.8456 231.4313 93.7496]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.5) >>
+>> endobj
+777 0 obj <<
+/D [774 0 R /XYZ 72 793.9346 null]
+>> endobj
+778 0 obj <<
+/D [774 0 R /XYZ 72 760.4491 null]
+>> endobj
+791 0 obj <<
+/D [774 0 R /XYZ 72 547.5674 null]
+>> endobj
+775 0 obj <<
+/Font << /F30 781 0 R /F31 784 0 R /F34 787 0 R /F35 790 0 R /F11 800 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+824 0 obj <<
+/Length 3724
+/Filter /FlateDecode
+>>
+stream
+x\K6ϯQSAxJymgkSV!UqWHm
+dSx'N25O
+&&wn̷7B;lYf/6^=C_~.(fE:L5!
+-vz]}d8%1֨-C@UxoyS-.F6aeYPI,pM筍ߵai2"[1`u0zC?f{?j9nj-~~2D΂iz0 ِܼ0HeT)#hBuZ"{>SBjBּ5'+$:JMt@bv!nv&*
+e$V5*
+a%gv`|*x}[t_u&
+OUxbEXZ+k7 6$. &Y~ nr
+hu>EErφ"5(1
+~VY7TYffxEs&Wq[6xRkKHy,W[af-S_ S):7[A lG*cLj3o;,}j'<߬ꝫwy .qS}jb\` lba*Nh8o)ᕙbpZZ !yhΩ.$ٺ_!t: -X[M7Ha)EA zXaFU1WaE<p
+ea,2Lz[C
+)݄߳KeZxp:'X Ywit!9zСR@D! bZ{J[>4&omI,%-"ȻY )rQYR
+zyZ[VݜS
+wRs uK*WL
+T+LHzdQKaQsb/#1Qe䭵5xH&Ja)2&*iq?S=azs&X1r Fr&KS-EI`uR~. &4$,"mSQb"'EE[CXuxe=1Lǡ:'l!Ϋ. mjE=Kn!?{d t4|(&ݝ= _Ll-؃gwL\w,;_,pJ/VѫP=XE 3 >ȏL.L\ykP]O.rjMEr f
+_m.֛?>8OpcWΟ7Ɲ}Wvg9sBFb 8̡i
+endobj
+823 0 obj <<
+/Type /Page
+/Contents 824 0 R
+/Resources 822 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 826 0 R 827 0 R 828 0 R 829 0 R 833 0 R 834 0 R 835 0 R 836 0 R 837 0 R 838 0 R 839 0 R 843 0 R 844 0 R 845 0 R 846 0 R 847 0 R 848 0 R 849 0 R 850 0 R 851 0 R 852 0 R 853 0 R 854 0 R 855 0 R 856 0 R 857 0 R 858 0 R 859 0 R 860 0 R 861 0 R 862 0 R 863 0 R 864 0 R 865 0 R 866 0 R 867 0 R 868 0 R ]
+>> endobj
+826 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 747.3333 246.9923 758.2373]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.6) >>
+>> endobj
+827 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 728.5571 260.8303 739.4611]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.7) >>
+>> endobj
+828 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 709.7809 265.8014 720.6849]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.8) >>
+>> endobj
+829 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 690.6709 251.4662 702.626]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.9) >>
+>> endobj
+833 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 672.2285 379.4542 683.1324]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.10) >>
+>> endobj
+834 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 653.4523 213.7177 664.3562]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.11) >>
+>> endobj
+835 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 634.5913 243.473 645.58]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.12) >>
+>> endobj
+836 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 615.8999 231.4313 626.8038]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.13) >>
+>> endobj
+837 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 587.0215 322.7152 598.5481]
+/Subtype /Link
+/A << /S /GoTo /D (section.5) >>
+>> endobj
+838 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 568.3001 215.4809 579.2888]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.5.1) >>
+>> endobj
+839 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 551.646 278.9025 560.5125]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.5.1.1) >>
+>> endobj
+843 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 532.8897 253.2089 541.7363]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.5.1.2) >>
+>> endobj
+844 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 511.9714 352.6124 522.9601]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.5.2) >>
+>> endobj
+845 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 483.1778 295.9549 494.7044]
+/Subtype /Link
+/A << /S /GoTo /D (section.6) >>
+>> endobj
+846 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 464.4564 540.9963 475.4451]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.1) >>
+>> endobj
+847 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 450.8275 198.7939 461.8162]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.1) >>
+>> endobj
+848 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 432.0513 419.8397 443.04]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.2) >>
+>> endobj
+849 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 413.2751 241.3212 424.2638]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.1) >>
+>> endobj
+850 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 394.5836 317.8659 405.4876]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.2) >>
+>> endobj
+851 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 375.8074 338.638 386.7114]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.3) >>
+>> endobj
+852 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 356.9465 450.2648 367.9352]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.3) >>
+>> endobj
+853 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 338.255 540.9963 349.1589]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.4) >>
+>> endobj
+854 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 324.6261 331.2058 335.5301]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.4) >>
+>> endobj
+855 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 305.7652 303.2379 316.7539]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.5) >>
+>> endobj
+856 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 286.989 394.7835 297.9776]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.6) >>
+>> endobj
+857 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 268.2975 427.2648 279.2014]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.1) >>
+>> endobj
+858 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 249.5213 408.9933 260.4252]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.2) >>
+>> endobj
+859 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 230.7451 540.9963 241.649]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.3) >>
+>> endobj
+860 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 217.1162 210.5196 228.0201]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.3) >>
+>> endobj
+861 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 198.2552 378.043 209.2439]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.4) >>
+>> endobj
+862 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 180.1865 219.1977 190.4677]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.7) >>
+>> endobj
+863 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 160.7876 421.6163 171.6915]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.1) >>
+>> endobj
+864 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 142.0114 540.9963 152.9153]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.2) >>
+>> endobj
+865 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 129.0052 215.4022 139.2864]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.2) >>
+>> endobj
+866 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 109.6063 368.6958 120.5102]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.3) >>
+>> endobj
+867 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 90.8301 429.3671 101.734]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.4) >>
+>> endobj
+868 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 72.0539 451.146 82.9578]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.5) >>
+>> endobj
+825 0 obj <<
+/D [823 0 R /XYZ 72 793.9346 null]
+>> endobj
+822 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+871 0 obj <<
+/Length 3748
+/Filter /FlateDecode
+>>
+stream
+xY7W axp"d'<XzÉ뷨&)HU˚8AɪXVQUWRW\15nKO?jB]Q"k˪_ %\֬Z^ImÛտB-֤r%}uw߅uuzЎOW_򛛟YJ-e@NT8obuJRT[)(a^}~B?$*QDڰ(\41DZ{n̿-7owB1`khͼ~f5߼!1 L^U,o?묻ͧߎm'!\H^fR#ξƨAO1Q
+:'8Adz>n[@rӬ0Hq?9E?뜶@%U؜ 5plճLF1%KC*QJQF6bćz>H|[MݪoͶ] ɶp7
+غCsnSWaNyr"DY^øꐓFT*"fHyiXjy2G~'P7_'wN H(-ûZ%u Z<],U U3U%dFB\3­aMXa7oV֞q]d^h;GHs@q/ ytsASEݗ,_Ib Y~3,O'`EE*Ve{ucC?s1%TKC*l<bGbl^{v&5Zz4Ͷ[N=[J[ 5Q 1j5NsVxa̡4'K<BYq*xhWm߭Zג^an^ΐ&f_z֮"nnD2|]Z R#Ɛ\ ^c`GG^j80 0#^%Kŧxk[I2*$Zm !cf0D[D֐6J4`9i-ozCdv.9CFw7~ ZAe|\sݾiW;o>[0#\jmJB' /M]2&ҭW"RkW$_pq#Cg ^jqy`<aVI<j2{Ux $kM[:E;?SG 'ngjL%К'5%ٺJ[GQAjD)PK}֟"nBw@_^id
+/EqdPAvԜn VZe>19}m9畗pUx)
+K y9'8߄ È7?cuC乇1mEňQ_FxQ!`%8$''EmaR}iJ "5nHȈjSGRJ4Ajq =GO.[처.</meb*J
+&˪~%g|<s$i;,H@!(׸
+A%}PyiH*WpFx^GznՔIݯ#d=e,ݼ]ÕEqK b
+T2GR37fobyiX8&jNEMD̪ fn4aWlqM)@UimR#4M3lb8';zN=s$f,j7^M'7Lt֦˘-GL##d[Ԉq@gWQ;*n2^X(@F
+T}_x8vw8Üi F4T4:g0 p}>jۀ)aSVB(R
+.vɤf7{eY[,g]7]NYWtjԞyWR#fw B÷y#P=x
+LT,z!q!7569@4j<c=gHE=zs/p>y] %7V_bZd
+endobj
+870 0 obj <<
+/Type /Page
+/Contents 871 0 R
+/Resources 869 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 873 0 R 874 0 R 875 0 R 876 0 R 877 0 R 878 0 R 879 0 R 880 0 R 881 0 R 882 0 R 883 0 R 884 0 R 885 0 R 886 0 R 887 0 R 888 0 R 889 0 R 890 0 R 891 0 R 892 0 R 893 0 R 894 0 R 895 0 R 896 0 R 897 0 R 898 0 R 899 0 R 900 0 R 901 0 R 902 0 R 903 0 R 904 0 R 905 0 R 906 0 R 907 0 R 908 0 R ]
+>> endobj
+873 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 747.3333 338.2305 760.4341]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.6) >>
+>> endobj
+874 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 728.5571 375.6294 739.4611]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.7) >>
+>> endobj
+875 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 709.7809 492.4007 720.6849]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.8) >>
+>> endobj
+876 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 691.0047 325.3079 701.9086]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.8) >>
+>> endobj
+877 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 672.2285 304.775 683.1324]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.9) >>
+>> endobj
+878 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 653.4523 357.656 664.3562]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.10) >>
+>> endobj
+879 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 634.6761 350.2941 645.58]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.11) >>
+>> endobj
+880 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 615.8151 259.5878 626.8038]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.12) >>
+>> endobj
+881 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 597.1237 303.4993 608.0276]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.12.1) >>
+>> endobj
+882 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 578.3475 281.0849 589.2514]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.12.2) >>
+>> endobj
+883 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 559.5713 416.7342 570.4752]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.13) >>
+>> endobj
+884 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 530.9669 133.8776 541.846]
+/Subtype /Link
+/A << /S /GoTo /D (section.7) >>
+>> endobj
+885 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 512.0163 340.9322 522.9601]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.1) >>
+>> endobj
+886 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 493.28 291.5152 504.1839]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.2) >>
+>> endobj
+887 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 474.5038 171.1576 485.4077]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.3) >>
+>> endobj
+888 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 455.6428 244.0343 466.6315]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.4) >>
+>> endobj
+889 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 436.8666 181.8405 447.8553]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.5) >>
+>> endobj
+890 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 418.1752 305.453 429.0791]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.6) >>
+>> endobj
+891 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 389.5708 156.2938 400.8234]
+/Subtype /Link
+/A << /S /GoTo /D (section.8) >>
+>> endobj
+892 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 370.6601 354.2892 381.564]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.1) >>
+>> endobj
+893 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 351.8839 314.9978 362.7878]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.1) >>
+>> endobj
+894 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 333.1077 321.5626 344.0116]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.2) >>
+>> endobj
+895 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 314.3315 346.7184 325.2354]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.3) >>
+>> endobj
+896 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 295.5553 314.4792 306.4592]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.4) >>
+>> endobj
+897 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 276.6943 441.6974 287.683]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.5) >>
+>> endobj
+898 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 260.0601 347.5844 268.9068]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.6) >>
+>> endobj
+899 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 239.1419 429.0114 250.1306]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.7) >>
+>> endobj
+900 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 220.4504 298.4489 231.3544]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.2) >>
+>> endobj
+901 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 201.6742 384.6255 212.5782]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.1) >>
+>> endobj
+902 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 182.8133 377.8478 193.802]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.2) >>
+>> endobj
+903 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 164.0371 367.0918 175.0258]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.3) >>
+>> endobj
+904 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 145.3456 427.1251 156.2495]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.4) >>
+>> endobj
+905 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 126.5694 397.5565 137.4733]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.5) >>
+>> endobj
+906 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 107.7932 444.8291 118.6971]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.6) >>
+>> endobj
+907 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 88.6832 312.5276 100.6383]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.7) >>
+>> endobj
+908 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 70.156 493.3834 81.1447]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.8) >>
+>> endobj
+872 0 obj <<
+/D [870 0 R /XYZ 72 793.9346 null]
+>> endobj
+869 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+911 0 obj <<
+/Length 3543
+/Filter /FlateDecode
+>>
+stream
+x]Y6~_n OO3 E2yPG-Y"MTcѝm\d*Ajh?,+ ' V7yyv_jI/<w79F!'Ln7?:.0} 1ȖW7{eWSÛ<?߾To~qw@K=Z8ɩ.wK*Zn8)rT{sB5;"fU]~inDZ#k #߾fEkjswz߿]nvݛj=+w|;K[vêjYݲ\w%}]rmW&
+e 5j$>H.#<؜Q% p@7PQ9K͒YT$bn֋MNhXr>/{]vM-4QL̗!PJ NCI?*>
+;΂p A(Yt,&|"{h2AS<g&nYy[Ex_ux۽t?gHX&~#?_[*}leD1E0T%o VI<=AL4u45dCA,t@6e!oK 7wT.C꿙AH?Q},FqI! 2bR%˥P6TYγ
+dBY9R|4'HLc"Q܎,RT"9~Z-$`
+
+ R%!,_ ,
+I.չF]/ff"Qg
+r;NGQ x9ISy#=~<Ucj훲f\\fi`]@;c*k7cDsj6Z練l $"劔{\I <|"@qܦx@#%ۑY
+/pm1j`j[Np.r_Qy? ٷ>PC/!\fC
+H=5F_"~-gUF6Tie kLib)2o6asH08E4h )2څ4a`RSy@O:SjH5wm
+oiUc7|~e-6 \
+aKcE^dgc޶-vn<g3I!oZڤkiv= jTۼᮿJLkM*2_ὲT ݋ iF Ŧa^ .˱+%aT:qbw4vF!Gs͖М0<0ǂ0J8MLx<!v<
+<T+Huj#SOecmM.u϶M nۖTHv% fzʍSA *A ˡmJ!@)@]*,Uvm?8z^f
+w}?Ӄ>&h >2A4M
+\2p46<|:7I͋QЉYGh肴iOHRfOi0 ^̐Ѯ@My.I%s{ˮHgn[[(O{M^K؎84 ix3RML3'F&9T:To5\am:po&=ba^<]z-ׄ0t%xu+~V+<zŬ
+E;$uIqD ̟g6Y8 /9Pz.xGB A=6B[GfQo[vVW`wOCO׳0~^ṙKG ֊|ENwD E*@Q܎PQc^u1)[2 u> ɸeUnGc?obd
+FbG3̗$ztH4?!aBzC !v0E!sdvrZ Q2[{ (
+82 rٓ);T $qgAQ=!6 et+\[T,ҞFyӔ pW
+endobj
+910 0 obj <<
+/Type /Page
+/Contents 911 0 R
+/Resources 909 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 913 0 R 914 0 R 915 0 R 916 0 R 917 0 R 918 0 R 919 0 R 920 0 R 921 0 R 922 0 R 923 0 R 924 0 R 925 0 R 926 0 R 927 0 R 928 0 R 929 0 R 930 0 R 931 0 R 932 0 R 933 0 R 934 0 R 935 0 R 936 0 R 937 0 R 938 0 R 939 0 R 940 0 R 941 0 R 942 0 R 943 0 R 944 0 R 945 0 R 946 0 R 947 0 R 948 0 R 949 0 R ]
+>> endobj
+913 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 747.3333 414.4431 758.2373]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.9) >>
+>> endobj
+914 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 728.5571 369.6221 739.4611]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.10) >>
+>> endobj
+915 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 709.6962 381.4579 720.6849]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.11) >>
+>> endobj
+916 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 690.92 352.9417 701.9086]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.12) >>
+>> endobj
+917 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 672.2285 307.0972 683.1324]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.13) >>
+>> endobj
+918 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 653.3675 347.0237 664.3562]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.2.14) >>
+>> endobj
+919 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 634.6761 222.6338 645.58]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.3) >>
+>> endobj
+920 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 615.8999 301.5573 626.8038]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.1) >>
+>> endobj
+921 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 597.1237 390.9311 608.0276]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.2) >>
+>> endobj
+922 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 578.7211 361.9097 589.2514]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.3) >>
+>> endobj
+923 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 559.5713 335.4297 570.4752]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.4) >>
+>> endobj
+924 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 540.795 540.9963 551.699]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.5) >>
+>> endobj
+925 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 529.1038 198.8835 538.0701]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.5) >>
+>> endobj
+926 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 508.39 269.996 519.2939]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.3.6) >>
+>> endobj
+927 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 489.6137 367.5981 500.5177]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.4) >>
+>> endobj
+928 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 470.7976 464.5377 481.7415]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.1) >>
+>> endobj
+929 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 452.0613 415.2695 462.9653]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.2) >>
+>> endobj
+930 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 433.2851 425.2428 444.1891]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.3) >>
+>> endobj
+931 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 414.4242 385.2002 425.4129]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.4) >>
+>> endobj
+932 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 395.648 340.6975 406.6366]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.5) >>
+>> endobj
+933 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 376.9565 363.2358 387.8604]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.6) >>
+>> endobj
+934 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 358.1404 279.1253 369.0842]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.7) >>
+>> endobj
+935 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 339.4041 332.5906 350.308]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.8) >>
+>> endobj
+936 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 320.6279 388.8002 331.5318]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.9) >>
+>> endobj
+937 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 301.8517 423.5782 312.7556]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.4.10) >>
+>> endobj
+938 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 282.9907 350.6399 293.9794]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.5) >>
+>> endobj
+939 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 264.2145 220.426 275.2032]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.1) >>
+>> endobj
+940 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 245.4383 358.0922 256.427]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.2) >>
+>> endobj
+941 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 226.6621 342.8695 237.6508]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.3) >>
+>> endobj
+942 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 207.9706 390.6726 218.8746]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.4) >>
+>> endobj
+943 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 189.1545 351.4034 200.0984]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.5) >>
+>> endobj
+944 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 170.4182 334.8829 181.3221]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.6) >>
+>> endobj
+945 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 151.642 255.5797 162.5459]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.6) >>
+>> endobj
+946 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 132.8658 338.7486 143.7697]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.1) >>
+>> endobj
+947 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 114.0896 334.4844 124.9935]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.2) >>
+>> endobj
+948 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 95.3134 494.4324 106.2173]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.3) >>
+>> endobj
+949 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 76.5372 294.9031 87.4411]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.4) >>
+>> endobj
+912 0 obj <<
+/D [910 0 R /XYZ 72 793.9346 null]
+>> endobj
+909 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+952 0 obj <<
+/Length 3607
+/Filter /FlateDecode
+>>
+stream
+x]r6+ޏU*I&Iы`Kl7S2١L P.ݯBy4YaGVa0.W ~Ae o?WkFh冬.⧋b)׶k 2W^\|5+{FRzj֎/o}_][kK[.D+[3:15gN;Bk:Yk71' -sDXǵ'҆EhڧD]]/oRodw5'ݶ[WeWo;T/ԯvǛ69~wg0Ñ2ie h3 QAgQ>o){KsqYTrD#[PK fr2zIkkO}O5@u"#]κj t46o-iÎ}D= A
+GB]ϺDGoبJ cuu;7U_Mv7twu;] Dj⶯E]B]wΟ5t~;ԭ/>+ ڌ~EegRmh嵴 Ohv/ujcKC1O
+{~#xKzI^i=ra4BWZڹkH8n[筢$F'E sۦ#C|xW7z\gjc`X튄/
+S:,Bz0{1#N%[]S;$+A+9L}Fā”=jMfa0B,QX^ڨ]TTꐎOTF:)uԻu߼Bol}wÄ{ig򻌂KDXM F M7S>'.tB\4Pٓ&n0kNwݵW_}QW@Wrzru'zr=g܅.n?#^a*JX>rRb~kg1B$bQKhb*<?摔#j'ES>ˡno;p>_Di㣡K>wMRJ1 V 1!%OBJП4  uqD`HIIJO߯aqav'tz9J"Ix9HQN?igt+/m\Eށ8;a+hxސuj;TK(pғ@K؟Ӵ<R!Ze0 䞖4n7[8!Nfw>M A=&z%vf߇;H%R
+՗`}#/rJ_mu7j>8ꞃgEaQĥ=D¢ĤaT‚`L˜ \aY+oeEp!7am_U}w8u J^%D Fp)n4V~ڃx =+k$--KIh.vp0E]VaQBmWRO!O%+-U
+[![-CLr3G'=yiyV
+#nIiǐuR4AP
+5 ʖhEDEwQDE 0Qr(ⴷZ
+z`3h
+endobj
+951 0 obj <<
+/Type /Page
+/Contents 952 0 R
+/Resources 950 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 954 0 R 955 0 R 956 0 R 957 0 R 958 0 R 959 0 R 960 0 R 961 0 R 962 0 R 963 0 R 964 0 R 965 0 R 966 0 R 967 0 R 968 0 R 969 0 R 970 0 R 971 0 R 972 0 R 973 0 R 974 0 R 975 0 R 976 0 R 977 0 R 978 0 R 979 0 R 980 0 R 981 0 R 982 0 R 983 0 R 984 0 R 985 0 R 986 0 R 987 0 R 988 0 R 989 0 R 990 0 R 991 0 R ]
+>> endobj
+954 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 747.3333 395.9223 758.2373]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.5) >>
+>> endobj
+955 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 728.5571 362.9872 739.4611]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.6) >>
+>> endobj
+956 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 709.7809 540.9963 720.6849]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.7) >>
+>> endobj
+957 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 696.152 200.5872 707.056]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.6.7) >>
+>> endobj
+958 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 677.2911 310.1725 688.2798]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.7) >>
+>> endobj
+959 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 658.5996 247.2812 669.5036]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.8) >>
+>> endobj
+960 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 639.7387 340.854 650.7273]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.9) >>
+>> endobj
+961 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 620.9625 414.6062 631.9511]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.1) >>
+>> endobj
+962 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 602.271 404.2024 613.1749]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.2) >>
+>> endobj
+963 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 583.41 414.606 594.3987]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.3) >>
+>> endobj
+964 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 564.6338 312.3243 575.6225]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.4) >>
+>> endobj
+965 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 545.8576 288.9949 556.8463]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.10) >>
+>> endobj
+966 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 527.0814 283.7444 538.0701]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.11) >>
+>> endobj
+967 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 508.39 231.2211 519.2939]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.12) >>
+>> endobj
+968 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 489.529 369.7188 500.5177]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.1) >>
+>> endobj
+969 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 470.8375 540.9963 481.7415]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.2) >>
+>> endobj
+970 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 457.2087 271.66 468.1126]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.2) >>
+>> endobj
+971 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 438.4324 540.9963 449.3364]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.3) >>
+>> endobj
+972 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 425.5208 230.9826 435.7075]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.3) >>
+>> endobj
+973 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 406.0274 401.6516 416.9313]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.4) >>
+>> endobj
+974 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 387.2511 342.0847 398.1551]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.5) >>
+>> endobj
+975 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 368.4749 252.562 379.3789]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.6) >>
+>> endobj
+976 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 349.6987 347.4748 360.6027]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.12.7) >>
+>> endobj
+977 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 330.9225 413.0079 341.8265]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.13) >>
+>> endobj
+978 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 312.0616 317.279 323.0502]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.13.1) >>
+>> endobj
+979 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 293.2854 274.8153 304.274]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.13.2) >>
+>> endobj
+980 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 274.5091 315.0474 285.4978]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.13.3) >>
+>> endobj
+981 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 255.7329 350.8793 266.7216]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.13.4) >>
+>> endobj
+982 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 236.9567 338.7849 247.9454]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.14) >>
+>> endobj
+983 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 218.1805 284.7479 229.1692]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.14.1) >>
+>> endobj
+984 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 199.4043 294.9897 210.393]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.14.2) >>
+>> endobj
+985 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 180.7129 298.7778 191.6168]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.14.3) >>
+>> endobj
+986 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 161.9367 420.0222 172.8406]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.15) >>
+>> endobj
+987 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 143.1604 428.8094 154.0644]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.15.1) >>
+>> endobj
+988 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 124.3842 388.7007 135.2882]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.15.2) >>
+>> endobj
+989 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 107.6653 208.8461 116.512]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.15.3) >>
+>> endobj
+990 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 86.8318 294.962 97.7358]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.16) >>
+>> endobj
+991 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 67.9709 326.2022 78.9595]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.17) >>
+>> endobj
+953 0 obj <<
+/D [951 0 R /XYZ 72 793.9346 null]
+>> endobj
+950 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+994 0 obj <<
+/Length 3005
+/Filter /FlateDecode
+>>
+stream
+x\[o6~ϯc\*j_ۢ]
+4}PlMFme${{(4%JG3y-:9x.$G%YI΅Jֻ4y_]QsG-/@\D&/)a"J(l~KYA+L$4q{/Lb*}=;N忾嫛_o, BqRlUr7'E*2] NЬ̓ǯF=Vb`˲oXz]77+7︤}_Bc]@ML$a'"<j$塴΀U`
+LZ\a :l4Ĺ` ^ Hȸ)dg
+)oW]@TjFD$Ip@!$DA PPE*-<}NtNXZ7!Ԅ@ m~Fg3lnPm޿6UYuuA8ֆlH=22sMŕTÂBvkPVn{gIpںLw-uEP戃C-X4tnF@ntuy@v\eꯚ|6vr 9nos
+✞Y`7=\]*ӗeΐ[4Z[󤃄(J@C2)ոC-KMlhď%av\jX⒰3?7H4'ZjU-zy 9A
+Qi͎(/%Z-)l':qP Z3 655֌!$|ɡI\J*<̓e/*2=olUSP)P}s.o-)艦l!o>?=՗ԭLviޕrjS1NLMO'Qk/
+a+f=LQlL)I,brb >a2o*KSAONbTsvա U
+29'*N3PJPsl`m`O嘩!,|So-<˅e&XbiQq;߸-ǭ]4eSiG[ ÍK)y΂'Nȩ<08ԂEɆfz0I, a$ŌZVar./'ޥ&rWcȃX7q< _I4Z?6Q%O<ĕmH' ~<̓,_ /齋ٚ73Hi„p<-'a9LfDL&^qP 3Mgth23qırXO\,Q=OW ܦb6 !t;iZ0yQI Q3G@g4XO3|i<_Gi"3f9(4H 5,j0٘!$4gsKY,Ʋ[Ll.C&B|jRd]
+c|D8K!X$lM5L(9H>!1E:"]F/c
+ GX偌򂡳4ɴ9KT'n⦊ͳmO`jK{GHf+1~=:vY/oō?s4LI=r2pQl_7TjCdmh޺g\~򣺩FK/3f`xkHp֡FQZЄ潇.>CY:ci?4\1$
+YF_A8mTA>¸=
+xvmU'Z
+(T, 46DSd)-wE~iwfcs&:/\P>KBU¡4? eʉUbi,E*#*U9R,, 7x ۈsޭ-F“%jSջbxJJBu&w9, 1*b v,e@T&s_Zendstream
+endobj
+993 0 obj <<
+/Type /Page
+/Contents 994 0 R
+/Resources 992 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 821 0 R
+/Annots [ 996 0 R 997 0 R 998 0 R 999 0 R 1000 0 R 1001 0 R 1002 0 R 1003 0 R 1004 0 R 1005 0 R 1006 0 R 1007 0 R 1008 0 R 1009 0 R 1010 0 R 1011 0 R 1012 0 R 1013 0 R 1014 0 R 1015 0 R 1016 0 R 1017 0 R 1018 0 R 1019 0 R 1020 0 R 1021 0 R 1022 0 R 1023 0 R 1024 0 R 1025 0 R 1026 0 R ]
+>> endobj
+996 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 747.4678 188.2036 758.7204]
+/Subtype /Link
+/A << /S /GoTo /D (section.9) >>
+>> endobj
+997 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 728.5571 313.6718 739.4611]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.9.1) >>
+>> endobj
+998 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 709.7809 378.1192 720.6849]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.9.2) >>
+>> endobj
+999 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 691.0047 390.8123 701.9086]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.9.3) >>
+>> endobj
+1000 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 672.2285 540.9963 683.1324]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.9.4) >>
+>> endobj
+1001 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 660.6569 185.3037 669.5036]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.9.4) >>
+>> endobj
+1002 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 629.9952 263.4106 640.8743]
+/Subtype /Link
+/A << /S /GoTo /D (section.10) >>
+>> endobj
+1003 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 611.0846 167.5115 621.9885]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.10.1) >>
+>> endobj
+1004 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 592.2236 184.3013 603.2123]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.10.2) >>
+>> endobj
+1005 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 563.43 250.0476 574.9566]
+/Subtype /Link
+/A << /S /GoTo /D (section.11) >>
+>> endobj
+1006 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 544.7085 355.7399 555.6972]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.1) >>
+>> endobj
+1007 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 525.9323 226.4432 536.921]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.1.1) >>
+>> endobj
+1008 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 507.2409 376.5262 518.1448]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.1.2) >>
+>> endobj
+1009 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 490.4671 181.3096 499.3686]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.2) >>
+>> endobj
+1010 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 469.6885 280.4272 480.5924]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.1) >>
+>> endobj
+1011 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 450.9123 540.9963 461.8162]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.2) >>
+>> endobj
+1012 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 439.3407 202.7686 448.1873]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.2) >>
+>> endobj
+1013 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 418.5072 318.6631 429.4111]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.3) >>
+>> endobj
+1014 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 399.731 491.0654 410.6349]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.4) >>
+>> endobj
+1015 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 380.9548 387.5841 391.8587]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.2.5) >>
+>> endobj
+1016 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 362.1785 258.7988 373.0825]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.3) >>
+>> endobj
+1017 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 343.4023 348.5511 354.3063]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.3.1) >>
+>> endobj
+1018 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [108.8618 324.6261 312.6856 335.5301]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.11.3.2) >>
+>> endobj
+1019 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 305.8499 321.3343 316.7539]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.4) >>
+>> endobj
+1020 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 287.0737 315.3567 297.9776]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.5) >>
+>> endobj
+1021 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 258.4693 280.0184 269.3484]
+/Subtype /Link
+/A << /S /GoTo /D (section.12) >>
+>> endobj
+1022 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 239.5587 244.8701 250.4626]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.12.1) >>
+>> endobj
+1023 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 220.7824 265.3335 231.6864]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.12.2) >>
+>> endobj
+1024 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 202.0062 181.4089 212.9102]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.12.3) >>
+>> endobj
+1025 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 183.23 335.45 194.134]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.12.4) >>
+>> endobj
+1026 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [85.9477 164.4538 376.0078 175.3578]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.12.5) >>
+>> endobj
+995 0 obj <<
+/D [993 0 R /XYZ 72 793.9346 null]
+>> endobj
+992 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1029 0 obj <<
+/Length 3930
+/Filter /FlateDecode
+>>
+stream
+xڽr6]_1-'q:^gTB]rChkR4F}7F$UWinDnd]=_\(?,W0
+_\0 )<S?#r]DI:śF,װu"1}}sw&^$nFMZXNӟ[kuܸUXfuΓ>a<]Moy#:nK=vgbBՄPgBI, iS.ߌg# 2T$
+PYIseD3f}O*2Tx`}jCmQfy`B1}뺲Ǻp&R@|Մvζ]U0Z)K&PWidRXmupO'1Emme7-iA+a/__\q%m}(/upOWDxvw.H"Nm<uI :ago%E#?hj>{ /ތO$+|5;!dc#4s+wܕxʬ 5aQaؔ-a[/I8k6&ѰkԷ^1)=x3͑ ']DPˊ'Ǻ1qtr6 pq62- CۉoR`LAN PTcQ 14HcwY8Яtzx_5m8alVJ kwD :LBoiO+W^(=kZ;w\Q-&F.eХŽ,6ж-7(ƨLd"p f
+`۶* <J܁1tRh*ae[Kt
+y^
+:_z[ @:޹ݾ
+@5^U 5qSbZ8!ri~6>*/xí(t$`7)dc:D%NB–a28PYgPW#B9ҢoKrmIcϟnH˂b*S`!RH
+0ͽw[R\Gp'@`H庠)D'ɢ| ys}sponSm0*SvtF?~vg]z'S,_-'Q<e0I.^U ''A7zDFIJƅ$v
+j C&G5Vo?l?Y;١҆K,' ך\,~~?N \Y7w}083Rūy <Wߊ׾6U Ѻv/KؒCEf*x FQ0iWL@bί+u/A$Sr~ftFߖXT;`-F)ډD_`/=*N"2~s46zB]>8 d>-V9
+G-W oao3k78>Tg:h#.i~EpЧ_Vi΋PDaA?lx,ְ?#F0k1M
+O2l%D*j)5L >ŠGKmO?~Uچr ĥA;I# 2Admgendstream
+endobj
+1028 0 obj <<
+/Type /Page
+/Contents 1029 0 R
+/Resources 1027 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+/Annots [ 1031 0 R ]
+>> endobj
+1031 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [519.0784 81.5293 540.9963 92.5179]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.5.1.2) >>
+>> endobj
+1030 0 obj <<
+/D [1028 0 R /XYZ 72 793.9346 null]
+>> endobj
+6 0 obj <<
+/D [1028 0 R /XYZ 72 760.4491 null]
+>> endobj
+10 0 obj <<
+/D [1028 0 R /XYZ 72 736.4086 null]
+>> endobj
+14 0 obj <<
+/D [1028 0 R /XYZ 72 475.3468 null]
+>> endobj
+18 0 obj <<
+/D [1028 0 R /XYZ 72 204.488 null]
+>> endobj
+1027 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1035 0 obj <<
+/Length 3172
+/Filter /FlateDecode
+>>
+stream
+x]oݿbѧ5h>45qZ$wi!@.cil+ǞJCVhsNz9f&?I&U+m6Eso+fY"p?ě#gbx#siK}u{De,r'HowW| @4w[]8޾iV%z/x;t- jQj̍L<чLhhpE{X=m7|Q1cTY$b{\M&:Ua?"ʓDm$Y}xE!y~ͼ&4Xx2&J$^Mh#$*qc ' H߭)kb
+ "l'D %f#^.t~F|HKCVE2SGfG+SR<ǖntG/f[:6! FP&X\Z4[,OzZ[7=HWǎz1^s6}Z/eFYH(F~BEFfg nM Jj/ɶD{s-o:T͡vOơfHWRHZXWHz3cWZ ##uGfZL/+;3.ik5W!Q*JKע;Jc@z-=p8^aw{?t}ø]HUǬı.,3ӌ#>
+M^d ڠk
+C$$^W\H.(I ;z]#oĠT~_0 jsJ!
+)!ߨHcE;o܆z'g 4bii˸d$j6<GxǼKcf uP1s5̅=w4TF\Ng گU:ևiBe]P&t<f"R2}q`]#
+f1F.-@CX+|٢}z3uy" Tœi S$w7S+*Wڒy@-lkC܄#Uҙz*o~VjV" =.ޜ‚]VϷVq*P۪%t4JEn5%OVLǀ9QeBSpԅ&tqʪcetAOCQ\5||kKH$ PplHµ>| C
+C7T+!0ř"ܐ!:淁IB.0۞- -]N
+f0X?0[X'<Ae:nu|oֲxqJbdfu;hl
+c:;< /ϑ?EWЛ9`A6\Y>-8]k[0~]h2ŅDmh<ּi9r`qR0y+
+endobj
+1034 0 obj <<
+/Type /Page
+/Contents 1035 0 R
+/Resources 1033 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+>> endobj
+1036 0 obj <<
+/D [1034 0 R /XYZ 72 793.9346 null]
+>> endobj
+22 0 obj <<
+/D [1034 0 R /XYZ 72 760.4491 null]
+>> endobj
+26 0 obj <<
+/D [1034 0 R /XYZ 72 653.7428 null]
+>> endobj
+30 0 obj <<
+/D [1034 0 R /XYZ 72 457.7581 null]
+>> endobj
+34 0 obj <<
+/D [1034 0 R /XYZ 72 296.0896 null]
+>> endobj
+1033 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F58 1039 0 R /F11 800 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1042 0 obj <<
+/Length 3393
+/Filter /FlateDecode
+>>
+stream
+xڽ]o6ݿb@V%R%mK/kD
+FM_Ev-;z盫61M6֥Ku)_(7;̍o*@"#t(Nm:Cx{ӼvEN;+w
+7.Mm(5N88cmr ;
+t#;:pCQu<cVD51r_u,\<B
+p !n0=0FX)x> J e$R2*i
+r:|9"5\n=d}*6JU\`[ŀ@9%`rKĢ jn#1ʯ,y3cgDlL0QA,;n1hM$Y6AC 2FA\nd&HAfOp}vDq`%#d",""Ydq9T,
+a rBI#l5ZI26p%ٔ4*?sk\,8H*ϊkǚ
+6R"[*K5`6A;>)9Tjtwx gG^te6dM!rHDÙra˜mMK*5y[ <u_"Ɔ/ CĀr>5DHbP W*|aU%owQ2kwO
+C_O!4+ͷE"2uzB('
+r=tEd.߸DῼZԘ2qe9ˣ8WfwnV߇# y6cE̋=8kg7`MwTj-}1CI>&I陏mUjB C |
+T-9yjD>CȌBɚ;-fS" J&68Fbm%}
+XeB)-$m{y.D8XI2T<$o:ʃm?%4*oá(')ZbnӏҮendstream
+endobj
+1041 0 obj <<
+/Type /Page
+/Contents 1042 0 R
+/Resources 1040 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+/Annots [ 1044 0 R 1045 0 R ]
+>> endobj
+1044 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [301.1087 690.0137 580.6977 700.9176]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cudenver.edu/~hgreenbe/courses/texinfo/wordvslatex.html)>>
+>> endobj
+1045 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [278.9314 185.4079 293.3772 196.3965]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.1.3) >>
+>> endobj
+1043 0 obj <<
+/D [1041 0 R /XYZ 72 793.9346 null]
+>> endobj
+38 0 obj <<
+/D [1041 0 R /XYZ 72 760.4491 null]
+>> endobj
+42 0 obj <<
+/D [1041 0 R /XYZ 72 736.4086 null]
+>> endobj
+46 0 obj <<
+/D [1041 0 R /XYZ 72 158.2897 null]
+>> endobj
+1040 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1048 0 obj <<
+/Length 3730
+/Filter /FlateDecode
+>>
+stream
+xڽ˒>_Kz$%Kjv\vv]q<#qfRKz @Iݣ}T" Eڤzȣ8 7fQ.LmAC
+js,4/~a}"sv}
+IQmk5 pߟMf`lE}X
+?Od!Z'Ů&d"'S5<e O6(ܱZ
+
+({]=eywV"D.!$_9BD m鏤Jy 5睂אcOąJGgy_V]uWy Ha
+B)E軱]:80 ,<G#L~M+Q(t=p
+_~ր۾0-dDx'ʊj:Tt4j
+/h|ZN{L !Mnb
+3xۉL8A"rQ0Gљ!-b)g)˷Zq'JܳqJd˨?wL}B7&2 ɓDjkmqdg]ePpIafb"L@ڭECA&6HasLL=%Ґ""XĮ|~&]_P=!c;j管FoP[v(D)М`C1ܶȔ(%aTXԄ>M)3ߝ}RT=b@h;8?* tNwga.JD{5' j%Jeq'ײ(1"Y |Tm}%!^[Bb,y\pC!}`j/nA18W᫣ƇNVZXuq ]%\Xv:UbIHple.\?5tg̔xm4IS1Elc &2xc_ݞOw)]I&g:>5i$A[N𷡒N$
+őft(MZq +L<5_޶Я(+m=`ܢgѴc|2$Uȓ@C_tqX#Qri;fD dqWp24;O
+fkHgrbH%TK.d"_..|{=
+gTuczJp3+U
+-{ke -3_?I&^H •<͌'||C,(Lpٳw%(`EDp .Zwς$ʉ@*`Oy<&#z5Xendstream
+endobj
+1047 0 obj <<
+/Type /Page
+/Contents 1048 0 R
+/Resources 1046 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+/Annots [ 1050 0 R 1051 0 R ]
+>> endobj
+1050 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [423.1654 349.1467 437.6112 360.0507]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.5) >>
+>> endobj
+1051 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 94.13 231.9787 105.0339]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cervantex.org/manuales.php)>>
+>> endobj
+1049 0 obj <<
+/D [1047 0 R /XYZ 72 793.9346 null]
+>> endobj
+50 0 obj <<
+/D [1047 0 R /XYZ 72 163.4333 null]
+>> endobj
+1046 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1054 0 obj <<
+/Length 3026
+/Filter /FlateDecode
+>>
+stream
+xZ[6~_a 4$MӴf:B#k<*d%HʒE۳ 4K1\H0'3EgJ3d{ghn<[Bg$_l Bo/0:"̶\F%e ,UZn/VArv0Z9Cx~Gc,TLmZ4q1
+?ޕEv.vIAlIՒwbZ٠+V,2% a5bi'xًbHpyz1r LS*fd12n{aޓ]Pۄ(,0D,c),ځP
+wSKK J"c$3֡-baec)}&N4]8<vi62mZ7Y^Jq;]\d#
+D G9GO8iU{źˆF>T?N6γ/0+t>C&
+:0IZ%f+Kb?{ *INd?Zң]RrR;B4lWMW62[n^+9`a&+FCl6Jo>HZL5n 8.˭FCu2ʭ? }b^WVCJ4,+gb_OK bCW
+5aA
+S")#2*HN*M(0 hy{N".O/X r(*~y!LmmgE*;{oVUL'JsZ@K<|aUBkwB˻jc C 'Ν^ ®¾G'k*ƒ*^Dc%RC
++WegM\CP ngk+ ho>B;:mT@W[e&?!HhS羵,NGH*U2"'iz
+i.i(z
+r`더mwlq6[-$);)3 RB$J %ʔ^Uwa+:c vgAEljM¬4kA+\V&|Nmݥ ]T ?dݕ<}(E^i`č;ا~e)[˟׀J[nmfl^pV2^dL *[m?#!d|n1
+ tDt}w~kY$Nw^*
+%io`#\cG1b)BA!"3ş̟?E !)Uvi$`mP!6NـkMI7
+endobj
+1053 0 obj <<
+/Type /Page
+/Contents 1054 0 R
+/Resources 1052 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+/Annots [ 1056 0 R 1057 0 R 1058 0 R 1059 0 R 1060 0 R 1061 0 R 1062 0 R ]
+>> endobj
+1056 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 631.4098 339.5142 642.3137]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/)>>
+>> endobj
+1057 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [238.1357 593.8045 464.6629 604.7084]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://cipres.cec.uchile.cl/~admcons/manuales/latex.html)>>
+>> endobj
+1058 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 508.4143 296.6348 519.3182]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://feynman.faii.etsii.upm.es/~seidel/bibliogr.ps)>>
+>> endobj
+1059 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 491.3362 272.7851 502.2402]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf)>>
+>> endobj
+1060 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 436.653 274.2793 447.5569]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip)>>
+>> endobj
+1061 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [211.8444 399.0477 320.6449 409.9516]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://recetariolatex.cjb.net)>>
+>> endobj
+1062 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [246.4247 361.4425 414.4429 372.3464]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.loarco.homelinux.org/lqref-es)>>
+>> endobj
+1055 0 obj <<
+/D [1053 0 R /XYZ 72 793.9346 null]
+>> endobj
+54 0 obj <<
+/D [1053 0 R /XYZ 72 760.4491 null]
+>> endobj
+58 0 obj <<
+/D [1053 0 R /XYZ 72 348.3507 null]
+>> endobj
+1052 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F58 1039 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1065 0 obj <<
+/Length 3173
+/Filter /FlateDecode
+>>
+stream
+xZY6~_'Jp˖cO&]Dr$:)d뷛
+l
+
+Ma:Y`~g:%2 pJzkdWv,`$™Z~+z<Mn|?M-;o;lElQz'<ލ~i+t%]rƂm~}5aaH<d =.x)"П?-_HˮGB_.r!U!o wdODI:aAP%ډYob=BEniGNI.`ѧp:aJq,+Z(ɐO(S%nbQԭ ۝i>O( |X#L(hѧG`tѮ|,r7Qպej }"8;jdG}`k&> htfOߤF'i,VyZ?G {33A SRXyqgWdk#Cc2$R}U+vSߢ$i,#˦MA%(CBx> lW[v@F 3L.}Ka,S$dihi0Up+`Gf>0~ȵ.L(ޕJ#ێaiP\w"Ě#u&7+O,'%4.@_}@&B>%P6cn鉀P+et+~k_>)$_%s3Vl{…jj>MEe1W@ rlwTQp9tp-AU@4˶RMwEUWQjGikm<I =|A$X0#O*Árm)g}Cωr0ԔDM H)LfyݬzU46Ylmv~@d{; * ?N(ѕ <`) ^κӥEu3n,(q'#Lj4tX
+(l%!Yf?=ֱ}<e}ۀUY+'lczT\6ɫۡ.NGӟUOtj};_FnzZ|@Z}l.UR"<_kTtHY8cA[ϭ%OK ~a$s qA('Mc T@fP\9#:Ö!`Oǣ LQG;GpIE;g vhqcÆM 9!I{:)Z:eP838 7 )u]MDtza2L5n0a%FiI^r쥵nb6.yHo-(B2ᩩ][KLT]v$֦ [0,T 4 ?7Ţ9JF0S> 8SF}#3^ g@䪎hd12 &Eć7<ܺNA/Yb/Q%1~ilGn;de{6:JtGi~nj]HH5Z1cWG]9cg`HL`^/Ci0,{TerBڳQ>4t<(^B1}$ma[1¯.3`WvpPJ!@x&c:Ey0XR\ZO_XG$4nٹAB&|o{NQ[by|+"K21}R@(kP; >RbUYR;Ӻ>;hYuEPfﺬ,J;P⁶x{ܖ&[ojȒ=N_uGq
+(=шƑY[贛?Y
+ 7U_?0d
+c,шAs{]6bxb؃#爒إa?C_)l0
+n!AfNzPm(>Lwgt!`J*uܗk3٣wIGпF?U]Roxת
+K.\x>OlJsu <`V#*X-f5I0/U:^lw'|뒣1)A|&֧aa;LV{YG.5|K@'n߼]{~z
+0xqYgg&P105a:Et^gMTy\ /m1Ǐ'qbN|-̷':}`P;C
+endobj
+1064 0 obj <<
+/Type /Page
+/Contents 1065 0 R
+/Resources 1063 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1032 0 R
+/Annots [ 1067 0 R 1068 0 R 1069 0 R 1070 0 R 1071 0 R 1072 0 R 1073 0 R 1074 0 R 1075 0 R 1076 0 R ]
+>> endobj
+1067 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [272.4537 621.2961 504.2923 632.2]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html)>>
+>> endobj
+1068 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 554.8253 289.4423 565.7293]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.sci.usq.edu.au/staff/robertsa/LaTeX/)>>
+>> endobj
+1069 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [235.9141 537.2114 374.1642 548.1153]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://ricardo.ecn.wfu.edu/LaTeX/)>>
+>> endobj
+1070 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [226.007 431.5278 403.5195 442.4317]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ctan.org/tex-archive/info/l2tabu/)>>
+>> endobj
+1071 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [317.6799 378.6012 461.6582 389.5899]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tug.org.in/tutorials.html)>>
+>> endobj
+1072 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 301.1153 337.1541 312.0193]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.awprofessional.com/title/0321173856)>>
+>> endobj
+1073 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 217.0307 540.9963 227.9346]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.awprofessional.com/title/0201362996)>>
+>> endobj
+1074 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 203.7754 153.2449 214.3057]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.awprofessional.com/title/0201362996)>>
+>> endobj
+1075 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 132.946 540.9963 143.85]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.awprofessional.com/titles/0201433117)>>
+>> endobj
+1076 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 119.6907 141.6187 130.2211]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.awprofessional.com/titles/0201433117)>>
+>> endobj
+1066 0 obj <<
+/D [1064 0 R /XYZ 72 793.9346 null]
+>> endobj
+62 0 obj <<
+/D [1064 0 R /XYZ 72 760.4491 null]
+>> endobj
+66 0 obj <<
+/D [1064 0 R /XYZ 72 365.0272 null]
+>> endobj
+1063 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1079 0 obj <<
+/Length 3445
+/Filter /FlateDecode
+>>
+stream
+xZs6B/f,xDܤ.3M?$l3H_"%ZVw8"KpoE"H/EW&Sq׋~0}s1eR eb{4 6o/~VYSIjQFJ_\\})(7w9n:EZhi7vkn:۬xXVmfe6k<'{5ѿ[|+f&)%b BG|!XpKU.#d[(О8!LĵL/Fwha'p9.f-< U"@.J2R1',iǤhSc
+ (Ϝ$ ^cҘ<[cDc_{M:>}˚+mg
+Ұmv#p%iJX̥\8ӛ}Dq x nhG#mQ-{ˢ(ۺZ{|+{9xvv)A`cɏLU^MZK.}PYv {mx35 əҊ_|f7{S6+g3Τ8Dֽ)gNĊߏ؂+KgŊ+*n#;ŸnHpr[[.{5}mKAà'"LK8 6na4ˍ'+M]yٴ(7K ( SO- mMyrO.sIeHp7ADG@z>^fY3-;ޫ5XnmCCe,QlWW ķߏPiC'R8 OF盳05x癘|CK#;K/8w1
+h4[?jO!M
+]ܹsTC?9w?c?0%ЌCg]eA%
+|fC 7 ,dvbѐ=LE'wVHjIrz R_BK`]4vQAUt,24Iz[P|R9Klg6B#&IoR($Ujjy>5aXVNT*p+{@m/*b.-M= Pi-}E7Iś2
+ZǖN,Vvj
+83Ov渄V<O
+=0K={I( Pyvy"۴Qh?cя7~/X\stMZj]O .
+\:C[YHCO3 n_o8>uG nlM`& em8%|3*Yq"(
+]9z
+Z
+Qyfb]„Ї:zF.^P6SF^菽Hx^X'8I/;P,78}h@Q\K7
+MȈJk#4(2D%6 TFp ?@5
+^
+FrS ^UENq8d
+&Q:9T~Xrp&Mh=L%edCO>8 fMxvlePxYb-4J
+H[gƖQR͸L|]u5a$XG/a>nD $D዆$/58F q[>|m+oDh[rx?},Z~0O
+H5 ]6
+endobj
+1078 0 obj <<
+/Type /Page
+/Contents 1079 0 R
+/Resources 1077 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1081 0 R 1082 0 R 1083 0 R 1084 0 R 1085 0 R 1086 0 R ]
+>> endobj
+1081 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 729.7194 336.2973 740.6233]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aw.com/catalog/academic/product/1,4096,0201529831,00.html)>>
+>> endobj
+1082 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 632.0059 354.0601 642.9098]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aw.com/catalog/academic/product/1,4096,0201854694,00.html)>>
+>> endobj
+1083 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 575.179 246.0964 586.0829]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aw.com/catalog/academic/product/1,4096,0201134470,00.html)>>
+>> endobj
+1084 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [382.9716 432.5937 495.5778 443.4977]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.eijkhout.net/tbt/)>>
+>> endobj
+1085 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [244.3876 322.925 419.7281 333.829]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://makingtexwork.sourceforge.net/mtw/)>>
+>> endobj
+1086 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [306.3621 218.0119 418.2215 229.0006]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://dw.tug.org/pracjourn/)>>
+>> endobj
+1080 0 obj <<
+/D [1078 0 R /XYZ 72 793.9346 null]
+>> endobj
+70 0 obj <<
+/D [1078 0 R /XYZ 72 284.1505 null]
+>> endobj
+74 0 obj <<
+/D [1078 0 R /XYZ 72 203.3171 null]
+>> endobj
+78 0 obj <<
+/D [1078 0 R /XYZ 72 166.3499 null]
+>> endobj
+1077 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F11 800 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1090 0 obj <<
+/Length 3407
+/Filter /FlateDecode
+>>
+stream
+xڽ]ܶ~>2(=e4uڤv2AW}JNgE 
+)uf y Т2->@`XTJǷbR i9I0(Ln>R't-+ʊ413+ʄulٷM|U]/NMivh<WP}b?YVSCFǑ7<lL i8b TeyXL&϶&isN$؂: d¹?[Vf'} { } X[p*S㨇;Z
+{v:{F> DrEKX7I&M1a<Bou
+>n||lh)vG+'RGȷSeEHL[](\AELG|<\ ~0?eCM~D}߳Gcf=ٖ. ]:MdzC15? d 1H/n+uc3 nEx
+'`l.䌡_ͥ_ȓB9Pΰ$IW+pxѵϸ";] vjHnڱj- <
+€v8!x*W,KO@J^rt_CG! @4 Vɴ};LAyƃ1xHRrqLaG 0v]Rd-Hu\bfA,mAhꊁEcQ'zsGPv:ǩ|&<ñ
+xq} 2Aư@fd}8IP(ˮ&*H8; '@N,2/Ze rw4HIѪ/3K 50] gy"\nٹA5Z
+n!x `C}=qT}:; 6b mYrS90CȃEgLɮƥI‚_V'VMTgj]<x-xC_0Gi9*coVߺ
+6]3
+DfwD=^uBL<1<(gQ,Շpg _])2*Dؒ;1jg#@`,T=
+V eP_S]f뗡!O|,٩:ǧh= nc>DP!TT4G+)|Z)To7MBm$gƏTawdV8A \o[5x!2svt̢^\ _^IZ _>i[vV܇,kJY80ɦw2kͼ8pn/֞X|v&"IZ޶g*>p-**$y,ṋH=DSJ> WJvsaKcC$%pk}ޣ{B&M^yIr^yX[XDfS(}l2К{Tˆ+DuLlhﺁO0f D
+ei
+0wvdzMT֩J^1)nbd.bFU赝DIYDX0(IՠAΠYPZII'jg&h!9ӂ,# ZT]jdq'Sh\{ʗR{$1˵Db\:O
+I
+c^9gaUA7\W+|5
+H(P dWx!OYcM MPl5I
+HfzVBDqus˴g:FU~Gz
+HOd+ӳ ҋ#=y؄ Q'Ehnph fٵZ<e8pt_<mz
+endobj
+1089 0 obj <<
+/Type /Page
+/Contents 1090 0 R
+/Resources 1088 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1092 0 R 1093 0 R ]
+>> endobj
+1092 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [312.1552 747.2486 326.601 758.2373]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.5.2) >>
+>> endobj
+1093 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [526.5504 512.2767 540.9963 524.2318]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.9) >>
+>> endobj
+1091 0 obj <<
+/D [1089 0 R /XYZ 72 793.9346 null]
+>> endobj
+82 0 obj <<
+/D [1089 0 R /XYZ 72 660.8244 null]
+>> endobj
+86 0 obj <<
+/D [1089 0 R /XYZ 72 485.3111 null]
+>> endobj
+90 0 obj <<
+/D [1089 0 R /XYZ 72 359.9532 null]
+>> endobj
+94 0 obj <<
+/D [1089 0 R /XYZ 72 244.556 null]
+>> endobj
+98 0 obj <<
+/D [1089 0 R /XYZ 72 131.2162 null]
+>> endobj
+1088 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1099 0 obj <<
+/Length 3352
+/Filter /FlateDecode
+>>
+stream
+xڽZo$ _F|Hm'Mp)8A;#&ٛE"Y}=~X(9&SТq)^H6;o/^m*`"q? rswW?);Xe("AIxN6@IU{Xz.ʲ&{SI=vhKmն-MCGɷ]ieb+''e}ﶕ"9nK l:%Pnk_H(flwȶA{UuEnf_̂Lr!3hGG&sq{t ~Ԃ;d9HL X4睌MEjN@AZ}DdtUSy04ue*8T۞C=֝5)' Xñb;G߄-F\wH-R?t -=JypHgxa(퇺f
+\HɌ*عp qJTص'xyWE(Nx f`{
+;*im v]&؋NJ~qsvV* \B\
+YeI RqO"Jcjpd+=ҋW(Ҕ0WF}GbX`/llU$Vclj:7CnAN}w4D{"iupY
+felsi`XYx6
+rqX<Rik
+qSoP =gNV)w ~Vu)v
+t.-"rEZP`M/J@K mqd{}S2>z\>PzP\OXg nsT<͂ظ~}b?t se)A[0
+JA 7j40>-Q|3&d pϕZ]ʤ"v
+R=;|^&6ԩ:$H]賈,@1C1AHğ0L|K\ J޿>efQ뀞5$ȨGC盁QvBDgܛ+
+u-*CH H<Q+CzW_ʭ' ^=j<,y?m M…l\PHNutCThU?빪GXQ. uhG϶W&f>Aa#mҋ{bgбH
+)53L\yuc!S9̋P J ֠E T- _AjN% K0p%ڳk+ֽ;O(Pacj. ƲbZ&hܱ1;'E{)=Q=E< 3_{ïDgwfz)LV H`&~cnoo
+@x.&U&X^ݖs_(Y83[MfYv4ۙ>,[;T|{15lmg;גnX5abugc7Hl@,Tt 9{xksS^lRD9j be*Hg[Յsy*P 'Ա^f<݃nj0!"R&Zhl"0+A ɗ0LJ 5=!X:1\(>[JE$<>tUy]sٝ'r e.}3ntOc=_"ACzld<,Z(>TK<`<_8-kP.H(JkR*Γ9fxO<@H ` EdF8|8gcc)ǽ S o|Yዂ~
+tfUUG̞Ԛ"bjJ^3t_q)@w?~@),wǩ7kqNǰs]D%Q݉?*/oDˍIxV=`ĮD0#www`-Eg*;=xK9bKWaqNtuQ ԡjE \Y2F;!nXpٮXQ2^g%(Dp?-@kGrMͬ:rq4CLL"O}"0t~e
+endobj
+1098 0 obj <<
+/Type /Page
+/Contents 1099 0 R
+/Resources 1097 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1101 0 R ]
+>> endobj
+1101 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [71.0037 67.9004 85.4496 78.8891]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.5) >>
+>> endobj
+1100 0 obj <<
+/D [1098 0 R /XYZ 72 793.9346 null]
+>> endobj
+102 0 obj <<
+/D [1098 0 R /XYZ 72 720.4981 null]
+>> endobj
+106 0 obj <<
+/D [1098 0 R /XYZ 72 437.8193 null]
+>> endobj
+110 0 obj <<
+/D [1098 0 R /XYZ 72 248.4846 null]
+>> endobj
+1097 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R /F83 1096 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1104 0 obj <<
+/Length 4209
+/Filter /FlateDecode
+>>
+stream
+xڽ]oܸݿbѧ5ECR_\[mJZ=Gw3JZ쇢`!9s#7(Dv?^I6;WWWI,7_P'rs6O*;eʼnHtbp_ݾUfÌ[-w&(i(w EUo:u_2~) V=HmK[ 7n0Ȳ"Td
+xIwtz2yE̲v'; ]/'(>IBGqn¦E܄xǾ?ׯlE։e"n?*8 n:'X- U,K"~zw5W)YwS/V]aRJ-$JƑ01 ^ yB8:!Eݒf޹BRpʶJAuow-<sv)k-0o?Ԧ-5m^԰JG
+4n`/Y7piR.]1pU\4D[E w}'| WwUZ9Zt Łqz:"pUc7=M/a Mzp8d\}VOhj@pZ\#}*_> oY+ĕRi
+CK*ʝ%nrA`
+$Aq3gK"v{r}-xLLE8wc؝Cqy_(s[^b+MFJ'}^<n:a{Xw{= omYn/P dAX/C+B%s~Xsf+2bFRsǙ. s Qr4^l{vo٧ZȋZtP*$
+qpx'BG楌̈NXźk9]pRec@*sZ&n""/־&7E]M +lxh wNGgvZ$A]d@dJ9ms9/%Ed$DC#K]?vjp-ڀ_ۈ$BzqqHfD"|.|ѰS
+.@?5H$X v DY
+"vWn\Mq\R@xܝ%b)?O]x㫱
+DX_sn_~I@^|P勦5fm&G"'
+ E[@rXE}hڶ' w#i⯌C4Mg%W9sHV1%1T.`rбEsa/k<3q2Jcy|Hl
+Ry
+\<OU31.
+۴I7B4@nscp96C/dMt47F׉zNt3fk2fA|BWC&V0< Nׯ/EaH7?f4yGwL1ŔgdYeZZX~硱FٕNW!2*M1],Of\u 
+%
+#AkU
+mjYQ[уBK÷ßy)s\!*j"+`30Ř73kC`˄2y0_ q"W˹2 {&P
+[_0H`? "9i I^鄕 b]< kQddc `zMMͷE'ڻgbk\N[wp "0 bo˿A\âH8aXL|h=e$z:<n}hZ7+d!;bqMj6/e:|Lct ~==ʏ
+qnv{Gڂ"@~R2"*{,#A;<lqz@L_QجX04k f7 J:-/JM_jfjA<{`ؒ Zx xdsvCAT!r? E\Nd 8ӁT!|z W|q#lUyz$;/]V,qQA(}0Mq
+endobj
+1103 0 obj <<
+/Type /Page
+/Contents 1104 0 R
+/Resources 1102 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1106 0 R 1107 0 R 1108 0 R 1109 0 R 1110 0 R 1111 0 R 1112 0 R 1113 0 R 1114 0 R ]
+>> endobj
+1106 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 667.3168 239.3505 678.2208]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cs.wisc.edu/~ghost/index.html)>>
+>> endobj
+1107 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [90.3711 648.5406 188.5718 659.4446]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aladdin.com)>>
+>> endobj
+1108 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [206.843 542.8438 480.5732 553.7477]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html)>>
+>> endobj
+1109 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [360.664 413.4957 375.1098 424.4844]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.2) >>
+>> endobj
+1110 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [285.1733 399.9515 424.3202 410.8555]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.pdfzone.com/webring/)>>
+>> endobj
+1111 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [417.6684 386.3227 510.3301 397.2266]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.adobe.com)>>
+>> endobj
+1112 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 372.6938 235.9036 383.5977]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.foolabs.com/xpdf/home.html)>>
+>> endobj
+1113 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [289.283 372.6938 457.6298 383.5977]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cs.wisc.edu/~ghost/index.html)>>
+>> endobj
+1114 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [277.3185 197.3964 291.7643 208.3004]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.1) >>
+>> endobj
+1105 0 obj <<
+/D [1103 0 R /XYZ 72 793.9346 null]
+>> endobj
+114 0 obj <<
+/D [1103 0 R /XYZ 72 760.4491 null]
+>> endobj
+118 0 obj <<
+/D [1103 0 R /XYZ 72 517.6982 null]
+>> endobj
+122 0 obj <<
+/D [1103 0 R /XYZ 72 359.1197 null]
+>> endobj
+126 0 obj <<
+/D [1103 0 R /XYZ 72 183.8224 null]
+>> endobj
+1102 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F83 1096 0 R /F41 842 0 R /F14 832 0 R /F39 819 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1117 0 obj <<
+/Length 3062
+/Filter /FlateDecode
+>>
+stream
+xڭZKs8W(WY"ȽLecjyĻ`H )%@mg|
+jBZ<pK;~(U㋺k} TTT+ %C7ף1A'l )[[Xfa#;Wf*e.=nanDp.'Ra]ثe#Rڵ}XFۏ]} ?U
+Ȱ7J?T*TdY>Z/C7O\.j )
+Fjw[XaoO܂L-Z#0JAn밠̄s) FYgf/ߨTN߈l5kn;n<h
+`L>)th~<]Q &a̞3塨V nj2i;xV%pBKD :UPphn[%u[
+Y}) gl
+:&ZRW.ė5AaSAxzBڐ@Kq~X.aR_1= :
+Vþ.0P:A9"J"-%vb=٣G#O4£kRW]u%^ x&Da%g\ x^Fq|/J#~VF5
+:&-8'![c
+|e,@`7shH-V]Dr}zn܉&v, ?
+`pf4wBzW c%,c1))0sn.ܲt*2,9 . {0bF0R倯3jkE=`-_[ r0bHc1';е<S'CC%"i9!Vհx
+}ĉ.Nܶ]o.S^D+ 0k^m((d9nFGxExσ|u88mKU v|6Kl!th%oܧ v0/$R$/0}Zi'tp /Psj(_kI%fz Qӕ'.t'wvx\zk2L[%IDaf4k,6X(|˙A?L& S+B%L<
+&([x3),@~Yt0Mu{8sp gSKAuK,-1L' 3endstream
+endobj
+1116 0 obj <<
+/Type /Page
+/Contents 1117 0 R
+/Resources 1115 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1119 0 R 1120 0 R ]
+>> endobj
+1119 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [122.0221 734.078 143.9399 744.6084]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.1.3) >>
+>> endobj
+1120 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [381.8616 456.5742 396.3075 467.4781]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.1) >>
+>> endobj
+1118 0 obj <<
+/D [1116 0 R /XYZ 72 793.9346 null]
+>> endobj
+130 0 obj <<
+/D [1116 0 R /XYZ 72 672.9756 null]
+>> endobj
+134 0 obj <<
+/D [1116 0 R /XYZ 72 635.9237 null]
+>> endobj
+138 0 obj <<
+/D [1116 0 R /XYZ 72 188.9281 null]
+>> endobj
+1115 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F85 1123 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1126 0 obj <<
+/Length 4490
+/Filter /FlateDecode
+>>
+stream
+x[Ysܸ~跴Rj"/&g<tNũ[lspGs&e\S7l$G7mDsnU?91L6%UB+|$ M7+fyua̲S&Zh#՟@Mj7?\dl?1^)oɶ軱s.y3RJ1"mIffqBNHnAvd Nixk$ZEGOͶh?nUɋǭ.וRr&p
+!ͫ70aO^ vK
+{I4W%3s+UٶVz*F>m*|H,'B)3v]sdߌj刪8%_>qAm!Ȍ]]͏̨Ҏ8TE`˪jiTn9MZC!o`+;koG9IY$e=NC`vF&cDM%$yf0*RWY2`띞"fЧJ
++%a5xw?Tn=
+
+\AU u@ Jԣ JmzP7/
+[^zR]T{|{RVWmU]p$Nzp3TVb ƀά\^<-hDh! c &ʒdjkLC`_1IeKlORcȘ݄F5`ʼncDRo,?p̯ƟIYi6`Q2}6 nu
+Й1YH&v
+5O? |w&vL!S't ;$2[l}ckKך"3[au&qi(y?5%*M쎫wawǤ'0H%_%=i$ IO~*Gyd$lSpOPalc?=J[=-LhO,3 =O%UT뎟kZP@ O Fgv1ASD di#g6
+_q`Rqc$M,Ud0t^l'<~
+%@KTzL`Hj=@r@MjrŠ+v`v|N57/QD*:
+) azݲC$y6nę&?O'mN01lzEc Ld*S=f9Q\5eJ_PˉPс0[gX(f7?ݜ7OFC]T'Pj]ώμ0Қ1̙wMnߥZ>jv:$5.^-u90H{\o;[nm\]0ðz2@{
+\
+@DFT0H
+"׵[`s81%N>l2soYf_fWvo@w)DCx`yUTT!m& AQxBkb {m:J>2tQgMAP^u CLb{x_Q4J.{y63@%q|ܣ}00<2wTP(O (gKh%,-4Ac̲Df?=7C&_7@G3X F8/Jb2^{T;۱ɰWOhUW?SϏ8aۡ@,ZIIuʚ }p_c_?ϱ4=Oawp  tGv!K:yѼV;ͳɩICpOBAj
+endobj
+1125 0 obj <<
+/Type /Page
+/Contents 1126 0 R
+/Resources 1124 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1087 0 R
+/Annots [ 1128 0 R 1129 0 R 1130 0 R 1131 0 R 1132 0 R 1133 0 R 1134 0 R ]
+>> endobj
+1128 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [137.9624 591.1192 245.7071 602.0231]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.rna.nl/tex.html)>>
+>> endobj
+1129 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [181.9666 546.2475 366.2533 557.1514]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.esm.psu.edu/mac-tex/default.html)>>
+>> endobj
+1130 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [374.2234 546.2475 512.902 557.1514]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://latex.yauh.de/index_en.html)>>
+>> endobj
+1131 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [391.6204 501.3758 525.3975 512.2797]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.trevorrow.com/oztex/)>>
+>> endobj
+1132 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 294.3124 332.2419 305.2163]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.udlap.mx/~ma108907/latex/winlatex.html)>>
+>> endobj
+1133 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [128.6176 235.8118 216.5272 246.7157]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.fptex.org/)>>
+>> endobj
+1134 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [363.7922 95.9497 501.1858 106.9384]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.sciword.demon.co.uk/)>>
+>> endobj
+1127 0 obj <<
+/D [1125 0 R /XYZ 72 793.9346 null]
+>> endobj
+142 0 obj <<
+/D [1125 0 R /XYZ 72 177.366 null]
+>> endobj
+1124 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1137 0 obj <<
+/Length 3900
+/Filter /FlateDecode
+>>
+stream
+xZYo6~h i񒨼,f'rMv d w˶ԫcf:~XEYRb1FW,ůR"UVIEM/T{!9ZmYh."aR'W eR_؅Byqsϡ I\*RZv5W>nw(ZWI(u\|OH'qZ)T^ dOjaMV- (lPil|`Nx5G\)RuR@&g\k2uo̗Kkeap"śa1gl1x)pʘUba#O'oDuXxvYC>M``3h
+fһIr ׅYDdz04(XCt5RKC? c= ԱpNMD"\"fD$(X"#DtQ;b!eJc^^IDZʥ !oZ'_Jsƴoꊿ'|EULUeTM$;N|<P{m(RۺDjq+۫0<g@<tWzҏiV>~~Z>6u @17MpvQHXDJ]~#DHx+EjW&V}[Sf m9-@zɶcC.`f4ta28 MͥkAq'ob],l'eDux<Ad}=ziI d:Tyu6t
+`OnYl]XJZp7&F4k0R
+&&#PovEWx基z/P2Yd% dHHz<
+Z*ƒk3
+hW*|OGo-WW?}uo Br DAdsnXʍ- 1%irG/ytMqv@"o=+d^!`m]?\uvGZ+
+;z] ‡7tu_Qۦ -M"]<3=հ $c˒u hdS֩[ypL ـcK'( 6!h8>>d"Ky:q8%9Ecı72
+_\Î
+,*@UYvZ\Kmd\JpzH-2g7 UeWXږ0?(]E+j17yEoo6 <gBfEt~&H8PlnmrЗK2c0evEumg:h)%ƺr.)nBE*{S6ln"EgdpCqE]sϐdj5]3:XyԒgzqb+ȧBS?Mb:tT%8Qv2U$@ӟ'53} zEws0emv8҉Is^Ix^ʈhK 8ҏ "8ύhN-@ӈ3wF6\I[dLh!k^8Pn /nj-B |BUV6Ry4ϨS0@|i3T,3
+a=ٮBk>?P1
+i&H{AWiPm_f .mWK\7 )m{Q1la59 shyd
+up*uK2 wVI) i.6s!>fó1AHp2!ӆKxP1qzAٟ'lbaǽ IJ؅[d˙)zFO1nⶌPY&ωb >x 2z4nx/JA1@]6'
+aS 3qn0,\ ٱ߅](L:wPcEu<ȼ$yD!CHKƺJO#aԼP6qCz@ZzP)PŮv&2hzC^/?bBiIxv+":HIYUg4%W{%,mBjwdb\^=k0`g ;/G]@qig%
+z 9#19`oٺ6 _A#9{:0hD\[$Af8UwTPBj`;7
+P03 Ë4|SBȆn iJ&T7yuo,]W5^y[%,tOo0OVSt+*Pb՝y:@9T-tkplU;+Ak/=ciW|m+d#QGftR#$`ߩ#U"{!ԛBdoB$]0})1h o^ z%զf߰r9GifW}['m>C`g4ބ/k#ُ8Wendstream
+endobj
+1136 0 obj <<
+/Type /Page
+/Contents 1137 0 R
+/Resources 1135 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1139 0 R 1140 0 R 1141 0 R 1142 0 R ]
+>> endobj
+1139 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [269.5377 497.8293 374.2836 508.7332]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://kile.sourceforge.net)>>
+>> endobj
+1140 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [332.7403 436.3951 493.0778 447.4086]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.uoregon.edu/~koch/texshop/)>>
+>> endobj
+1141 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [170.9386 405.609 294.9021 416.5129]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://itexmac.sourceforge.net/)>>
+>> endobj
+1142 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [107.8057 67.9851 219.665 78.8891]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.g32.org/latable/)>>
+>> endobj
+1138 0 obj <<
+/D [1136 0 R /XYZ 72 793.9346 null]
+>> endobj
+146 0 obj <<
+/D [1136 0 R /XYZ 72 693.0782 null]
+>> endobj
+1135 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1146 0 obj <<
+/Length 3110
+/Filter /FlateDecode
+>>
+stream
+xڵZmܶ~b/ny|
+gퟅZAO“D\ooknpEצ;^(uO)/B!os?^ᄇli"&2*VPqHwG%iڌl%A
+.Z#g|m֜
+(Ls|# 20MpYβR4\+wj׮u0u&RC^kO5O6/L^܋ۦu_5!SET4C֚ ԭgof^P0muaܸ׃i7V7u_ծb'x@5aulG' G#Zi9q6#':djQ'h%D}a[SUnZG;kEfTߙkֻ{U^WRv[[m@7BPIĶy붠O?cor(#gJ|SG8԰tvmuQ L=T[p)6גZp״K>?3Yڎi2uY?iMvPLX/ewh2qΓH|;)L((pyBF ߌ#FBŽ'߿NԚlM%)oAcۡn1ݞ
+5j*IXTZ*)JIba@\H;ڍ0b>dc%đd4%*H+T$đ\
+b@s@At 4xRQ ɔ J2X=st=SWؾ{sB2JY d5㾴^ϣ/\Щ<}瞕ߣI2H|QPB=Ƌkf N]5]іeHn@X5' wonDCʀIATRZlh
+(@ qEd,J<-]`b嫺(1XEXSXīA
+93 YS/!Og<} Q`!c'6f
+gKH*Xv"i.e,#hIr0Pz7 c[
+g7]bfSkHWHf땽{c}_yOb,He b}eK)Ȗ q.ІU!s0;I^atd)d'+[j"u[M GD'U.PpuK=jjdFMd>JIcl sΠ)I$W0"x3<2:Ø7]s.
+ဈ!D26@Ӹ)ЎD:ݘ
+O-ereV|>3eOk:R]bSƨH뺩;Oڡ*</bbzp`#6y$}wf{r'{!D*c{
+|9U63@_"Uhr J,fQ_QƹPiBq* c
+b_xySxR *# 7v6k=x2bH)>cO7g)J`?:xx
+,L
+(;E>8)̻j
+.JrwC4 t7[،&<FHgX8Auo sG H|a6=Ǟ; .r4Ff︊@n[3~@8^ZmKPU(g12)7109%ExzLfP{w]Q57s>2"U!h~OfcwIqAO(p&B0os>;srgx+Dj"Nv3 t<9Iכ9˘#7RY 9ſAُLWNOf[x.ʂ`Gl~نN %:joGX0܊}[\U$MԈV"u
+endobj
+1145 0 obj <<
+/Type /Page
+/Contents 1146 0 R
+/Resources 1144 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1148 0 R 1150 0 R 1151 0 R 1152 0 R 1154 0 R 1156 0 R 1157 0 R ]
+>> endobj
+1148 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 675.5604 272.5457 686.4643]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.dessci.com/en/products/texaide/)>>
+>> endobj
+1150 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [410.3128 522.8054 432.2306 533.7941]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.1) >>
+>> endobj
+1151 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [95.9104 509.2612 117.8282 520.1652]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.2) >>
+>> endobj
+1152 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [365.7955 509.2612 387.7133 520.1652]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.3) >>
+>> endobj
+1154 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [319.8478 488.2906 334.2936 499.2793]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.5) >>
+>> endobj
+1156 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [351.0583 467.4894 372.9761 478.3933]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.1) >>
+>> endobj
+1157 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [403.5656 268.0843 425.4834 278.9882]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.2) >>
+>> endobj
+1147 0 obj <<
+/D [1145 0 R /XYZ 72 793.9346 null]
+>> endobj
+150 0 obj <<
+/D [1145 0 R /XYZ 72 661.1864 null]
+>> endobj
+154 0 obj <<
+/D [1145 0 R /XYZ 72 624.1345 null]
+>> endobj
+1149 0 obj <<
+/D [1145 0 R /XYZ 72 543.2011 null]
+>> endobj
+1153 0 obj <<
+/D [1145 0 R /XYZ 72 506.629 null]
+>> endobj
+1155 0 obj <<
+/D [1145 0 R /XYZ 72 485.6583 null]
+>> endobj
+158 0 obj <<
+/D [1145 0 R /XYZ 72 440.5226 null]
+>> endobj
+162 0 obj <<
+/D [1145 0 R /XYZ 72 412.2361 null]
+>> endobj
+166 0 obj <<
+/D [1145 0 R /XYZ 72 241.5758 null]
+>> endobj
+1144 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F85 1123 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1160 0 obj <<
+/Length 2978
+/Filter /FlateDecode
+>>
+stream
+xڵZYo~ׯ ?H't v
+a|eȜWUEr
+.matx="r&UŸ24W_8n<BŘp=<nԛRN+xkU@l|Ǭ͒
+ONOQv$^~ÄeaE^"`N#hWsgn뺻\;۫ioiZ{_MOu޷KkTJ&ܖ9!:yQIZ'v_N{atNBAeY0LA`&-yYH/S
+
+6>
+9,?Y>O@U 0sZzMaO!9;H
+00vy|Ǿ]4*7Soql
+huQ""0
+H ^(쁗Z\/`}㭝ô綐elF;=h?aY􉋝5z1>tl'0 ; qN.hv88N[}pȜCWSUKYULsD3g
+3E9\ h2gHy]
+aה0c^ %tDprIu7*ĮqXj)kx-;5 ;S(9XҺzlr#Դq 2lƭÖxgBy)<EgTxEtg@fګfEm;'BDqX^t~ (>(@Q8K P+OI"$+_u gzu)r+M1Qz̾i_S fαM:9{Ļ=4rT4BeQHs!ۉ2NԊ )}xD_ )=W9!~/9,4E4vՋJJ)M)Ȧjן~?ثJG7>k{ګRE0C7MY-`8.&K̈A?
+=67FqG㦾a:kA{)00L
+fe],3Sqk,xRS
+b>INCB->Ǝ!v28i+BFRۇq|Lo;'K+!@)
+HeY%ũK h
++dcJd:bEqXU?[_zZ|I\9l}CxV
+2+DXbU29})dytvIfAysg<-sUEGX#oUt#zѸgfRjUoF ͱ|Z_
+1$xMLZϟp}v>JZ#Һ 1v84fΘVth#n;
+ ^DljBRڸ `a~^7~QLv!8'`QҜWM˲D󪳘xn7Qϭ>3xvT@䮊z;|d\ ]>Tv^NLBd!#-_࿊*endstream
+endobj
+1159 0 obj <<
+/Type /Page
+/Contents 1160 0 R
+/Resources 1158 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1162 0 R 1163 0 R 1164 0 R ]
+>> endobj
+1162 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [234.5288 382.5876 256.4466 393.5763]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.1) >>
+>> endobj
+1163 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [233.0842 310.1353 255.002 321.124]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.1) >>
+>> endobj
+1164 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [301.1977 129.7993 323.1155 140.7033]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.2.2) >>
+>> endobj
+1161 0 obj <<
+/D [1159 0 R /XYZ 72 793.9346 null]
+>> endobj
+170 0 obj <<
+/D [1159 0 R /XYZ 72 369.0376 null]
+>> endobj
+174 0 obj <<
+/D [1159 0 R /XYZ 72 209.4155 null]
+>> endobj
+1165 0 obj <<
+/D [1159 0 R /XYZ 72 121.7432 null]
+>> endobj
+1166 0 obj <<
+/D [1159 0 R /XYZ 72 86.5687 null]
+>> endobj
+1158 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1169 0 obj <<
+/Length 3458
+/Filter /FlateDecode
+>>
+stream
+xَ}b6 pWz1[1bXIp!iÞJaūU,šM6YIE)۫dﯨ[N6;X%Wl*
+\n`&eͻ>TnSrIyVnRdǃ.︔wIJ?{PrmLJHR #,!NH.
+,H‹"tNiT;z4dSEC]aeLOd,r;e񔷽]7sY8Z6DHY"5϶+a$qB_K7ן,5ȫ~Koxƺ>T(&M"*VTsA١g
+J
+&ej(tkvC[MM`˒퇹փ; }G5J۪/gq_-2c=qA&sOTz|ag^װE
+o/$egҝn ¤ؾ˷vB5{`svs0;v^> y<wL0W`0GW C}53zFqHKCU_yNu3\r7f}醒LfbehH`H rcM#%H.h ɀۢt 3!@(6 MnmZUX
+Jg0ÎpJ1V<'mAfR~AVÁ5wN5 1>C_)C` lT1L,M}z;z_wu+U=sO^zٔtm_C:lfS<1|Ds&ˍͲ-#0'lp& ڡ;Z'RzRsBISꡉ4PXyیcwK3Dߵ[b~1J`Aua=70.yX.S"20_a ˡ3
+:'PR.Ig4(/fx.sم8++69(D L#iÖeiBS|ѨD'a|,7AEj/:gp ɭ
+P/q;eU$a,s_RBhT'Hq (b*%Sm*C?8GaB
+"X-2w4A;X*U
+$/8:!pS~i;Q kT4
+o,֗ƒ0xxZ49?Y C%X1z9ΓWo>(wB4e T*SB8$KrB߹
+tui$82߄"9
+g Ml0bmpK!0Γ:λ<z<#Dm1/75{LvT5C}^}Q_IkЙ }{bt] hؑر_)
+s.saL5 &ZS"5){uVƢ[0Tv]?<e$+T<i3D{(ؿ"V|IN+S/VuaV_5)1XcN;=f@]4vM@[أj
+tL>57_gp7܇co X<buMsaG\)=&i۝ݔ-c]X#bpwSW^/ 0Ԡȭ1P\T j5QtTr+
+ Zϳ\8O^]bSq~6j,
+1 J$s+`YqګHM&sԽzNP1ͥ-_*j8@yIGS:bT.?ڷRV< )9{)2^< K&+?}v|z>%I&2:/G^<.c:E|l}ñ8a1]#!@H>nR~B9 D+Wg'L)7{.Z9*InDbVщ (X|}P4dž
+2W5' &Z5?F-|h[e55N*`Ȳߋ1c*[fDBLS_7i#J7oPCβ|sĢc]S>$xoZ_S,8˃{Gk
+i\j }i/̙( ZGy Bґ D[Xve(GeĀ-4N`h{t{71;B7j梧hAx.;L,FeێHRT%<ե.\Ћ.lRP$˧|Z״)ry}B ${}_|Yxo
+ZY8]$Qw4mBblfm|`j,c٬wy\9vEF
+endobj
+1168 0 obj <<
+/Type /Page
+/Contents 1169 0 R
+/Resources 1167 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1172 0 R 1173 0 R 1174 0 R ]
+>> endobj
+1172 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 498.432 335.1501 509.336]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos_only)>>
+>> endobj
+1173 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 449.9451 322.4181 460.849]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/)>>
+>> endobj
+1174 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 401.4581 356.8889 412.362]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.weihenstephan.de/~syring/win32/UnxUtils.html)>>
+>> endobj
+1170 0 obj <<
+/D [1168 0 R /XYZ 72 793.9346 null]
+>> endobj
+1171 0 obj <<
+/D [1168 0 R /XYZ 72 739.4745 null]
+>> endobj
+1175 0 obj <<
+/D [1168 0 R /XYZ 72 350.0747 null]
+>> endobj
+1167 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1178 0 obj <<
+/Length 4127
+/Filter /FlateDecode
+>>
+stream
+x[ݏܶb_HJqӺ0A'k9ZIчK3!W;4 PHr~3]b] Spw]nwhLc?]|C+ae}0Q&vH~rH,Ȣ,ƑxwP]Yq]~!R{s1.2fLZ0>/.N,Q)N#Tq$v2Lک~grTGa;̺]c]Ills*˒ݬ(M]M|a8հ]TB 磌:`üc!,82:`EZ&Kj[,)oʖCuMQTmSh~[j+e{ý5yixd|s)(Pjjd?xWv%0MAA.hH7E~}ɽyuEڌ+L2{eƽVZkxd|;CW<Men0)qۛڜXfs_Svƪ~O<Vw+lYTi2KCԹ[GYW5l.
+
+ZluZl$r"d+(AAhMIKRT L}ǽ OY$YDIPV(8wsIPTHGAt7ET
+5hIb!Q&F.9E;M$V
+:*gvqÙ wطV锵Z\$뤜
++2%LjbFk&[shx;Qzc
+::S5.$1b@~ALlȕ/qnwERJҕRfl>pXn {N.[ss(S'F7CCm fbNf!K&~UYJkw!wPpo64&<jM.M,MDSfC2G,R\L9HV9NA*A}ՏНG 
+V@cؑ
+D0
+H+cL2(eR S M"RlHLN V m4EJUTK kH@_}389;B|qOт~,@,%ú(Q,2*&>ӀE(CWHV%''᠊[z.ı AKeHV6iT)(30Ҁ
+2
+Ή&D9'}[rR.m$jKV*:gNa+B5j/fnCsk1']gU@eDA1Jj
+ {`'Z\-Sa>7b\ya&l-6e,_GWX
+Ϭ%x@2X.O@^P|9Дh l|/!
+Nf8|۞&[cո3Jc@{.OQ(4SJS9),)#^Ez^b++uۺn]oV<p1;5c/Eۚ{8̒ Y
+=c
+n[0-,‰NKaxОF
+=I80xn S3͐aD1s3
+I/o+B 9ؿ@eQ\Eyձjl_ b
+!P'ةXK[6a"ǗO=Z/ݓ8#9<UmUT'C#dBcFoACW`:WҩV|Zu|d#}YQfIm$!
+ZJBaVmp{{L/ {cfo|v=rGBMEՊ7
+]ޏUAO_p{}c1UM;
+My_T p;>nՙHN[>Ӿr4spJkb>Ɋwm=.G3ůfR-F|#1vv-3^4`NwŞW]y8?Mv ruOދp-nJ5Ë vy )<_Vk{xOC SOݸ{\.[x"@ڂV aendstream
+endobj
+1177 0 obj <<
+/Type /Page
+/Contents 1178 0 R
+/Resources 1176 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1180 0 R ]
+>> endobj
+1180 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [198.6646 346.155 363.9731 357.0589]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.lilypond.org/download/fonts/)>>
+>> endobj
+1179 0 obj <<
+/D [1177 0 R /XYZ 72 793.9346 null]
+>> endobj
+178 0 obj <<
+/D [1177 0 R /XYZ 72 760.4491 null]
+>> endobj
+182 0 obj <<
+/D [1177 0 R /XYZ 72 194.4391 null]
+>> endobj
+1176 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1183 0 obj <<
+/Length 3734
+/Filter /FlateDecode
+>>
+stream
+xڭZYo6~hX iQ%pNvf `KAEԖ dad.~Ex7I@eAoCgZHog?m
+ SafzSqUv.I3Y+}qsvUm'݂mwmu:L#oko(<?w|{7M$Hqd*Be>mu5 Tzf7#AM}8kTefp L~z*?JcNC9D켪,c}"
+WchwAo-J/}%ygMՏ:lsW%0Zuڡk,ʶ6z#.i ,ϪbVX)\ɁSOY-B%tb?耶ʪ8پk;>T=zh+íJ<Sep,Z6NeQ*Zm8C_dt8[!
+
+7h0 r1]' \@ycVaQ t:y=?]mMEb'♵ɻVMJU\D$`=ڮvC l866d z;saR<X$J…98 u4P6~w EyQJ1x7f!
+J,̨L>AV1njӀ^,wch5Hͱ7 Zɹ uF;dJ'qN@gظ B(v4\_!y?\y#vV̭.Uq93(ZN[Y,_2fm>Fh#[+\/Ϊ%xHLo@ A6|a5(ۏf3Ի30,H~=DGAzm R7fn{Xf]i?Ws燼rq@$%iKXUy4hBB㭣ro@~d?BX֦A@q
+qGhi`'m%=ph>Ȭz|2z[I]BÜe56CdX#rr&79& z6(nsWyBϞQpfSZh@A1f *t\o.: @$s#FfW3azpEN}`&%8%CP^AmRK[z1n
+-|;novM'rY/+=v7{v=w*s/A-: @ >=Z#nR%xش 0Un[n<[c(j4?
+yc'@}g(SG20y{3ń<Kٹtx%bd
+78?J00Hoe
+hmi6 iVB]W'LRJO[^Vn-:>nJ )iM%in |rpH<1|=ʒB7E)AJN7#08%]P@u5`1l?Trh7d~d?i0[
+mP]U+2r0ah.z
+|pI]F㶑E߸-VU~:i[V&WqGf{#?U[oWp_⬋~MI:s#9q:ߵŘ_ (ӯW`Ϊgx 2S?'W{Aʷ3z*
+nk_gi,$jQ.~SVƷf&@ <O<w"{^+W3P7瘁v@;TІk;1=D[ӌ}Um @ד]q >Wtak/R/K8Z 6mE
+L/F+9*pxsy UW*ްAb#콽mU\%>g)cb*H|kMD,6 v?@ՙ7z@`fi:Ӝx":Ky>p9Gw]4X^Q09f rcg"I0L^mO/j\
+?zu+׬e m%;
+endobj
+1182 0 obj <<
+/Type /Page
+/Contents 1183 0 R
+/Resources 1181 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1143 0 R
+/Annots [ 1185 0 R 1186 0 R 1187 0 R ]
+>> endobj
+1185 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [290.6401 623.285 305.086 634.1889]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.3) >>
+>> endobj
+1186 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [519.0784 609.6561 540.9963 620.5601]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.2) >>
+>> endobj
+1187 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 102.8129 375.6284 113.7169]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex)>>
+>> endobj
+1184 0 obj <<
+/D [1182 0 R /XYZ 72 793.9346 null]
+>> endobj
+186 0 obj <<
+/D [1182 0 R /XYZ 72 582.6332 null]
+>> endobj
+190 0 obj <<
+/D [1182 0 R /XYZ 72 554.262 null]
+>> endobj
+1181 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F11 800 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1190 0 obj <<
+/Length 4035
+/Filter /FlateDecode
+>>
+stream
+x[ܶO@Q`)RIܠ&%0nWS6ֵᐔ˽ۤhEp8͌ -:OYl]%-4}]wXAQ;do&s JfƿW\V0J2W鋻ۿj-wogJ%e=4C_Je/oR$X}ᄆd,שix3$_\ةq9)S21Մ!v<P,svi +ʺ.ǧ% e2
+ir=
+%S&1Xe)3"}ݣ+o
++LܒUz^Cta0O4Syy?A凮mp-Ӷ/6Ы`nȶ+vH;TkDP4~j=yQLԘꇮg} %fz$w/w֬
+ZOz6UUK׻qS~P=
+cD,_[Ft+\G-On:m'Tu6EWNe^pźl`عg7ܧ?@5;bz:|s
+tP~R(c("&UQ9Mj/D䍄<I€ ^-!85
+˻g~e{(m/}6k*ȕ
+UP;O5؂:$UojBohN @sp%^üCW> D,T6f&;WdQm
++8OӉd)*;|Q U3r6#<_/_șF[!y6Ť5mA
+~P4ZNpD,r]脨ٚV/7BdGt#+9*(`i*<|m?0ӯN)_fd*͟/}{%ٴhUP?rlTdm?lZw"ֳ`Ek#:zm
+ظ.leMnizj}0*,I(ei0j@CC-?v>ůȼ*kX"WV1s(]yՄ(~w˒ejGF(U
+â0.ixn+b
+PS:W%ۯajc*م7JȦD"
+om`~L&ނ4-͊jc3N)M[!-5ܪ˅F0*&j
+sӞ{_"G\3q2hud4͚
+4Ha qԞ
+o+gpX(u)k
+bB 7m
+p+?'q2l(xtZ6ـOäYb|: X!I ulut~fZ8m:^T:E)MxF
+I%85OT[ﮚ}u&`JTkyqMm
+RIY|A2/4(GS 21̸Db
+L󻿚 ,?LuϮv[y0bBi˝6~N``w1+)`*;2:+
+D`r!fRQ:ZR: }?Əj,xzZ*>7qQ@1TOOƏ|u`2Lv(_q3)>4hj[5E`@d.*ԴtlxNQQ0>u'DoSƒ5Yc9OS))ԈG"Hb V]eZY,I VU['{?+\Inh&xBpqd}|Zj2}f }PWiKQendstream
+endobj
+1189 0 obj <<
+/Type /Page
+/Contents 1190 0 R
+/Resources 1188 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+/Annots [ 1192 0 R 1193 0 R ]
+>> endobj
+1192 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [411.1145 549.179 425.5603 560.083]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.3) >>
+>> endobj
+1193 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [437.2281 202.4422 456.6552 213.3461]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.10) >>
+>> endobj
+1191 0 obj <<
+/D [1189 0 R /XYZ 72 793.9346 null]
+>> endobj
+194 0 obj <<
+/D [1189 0 R /XYZ 72 594.4126 null]
+>> endobj
+1188 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F83 1096 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1197 0 obj <<
+/Length 3152
+/Filter /FlateDecode
+>>
+stream
+xڽ]ܶ~>^Z(Cǽ0lm@ۓp ;j]پ
+xnU|mXˆ`ӄ/SiE}xe6COkD_HEg+gJDuX-N]n@c ۮWM^Os}MK ]㺪໼;$ *.t!2=κo TFw/,q" 4
+-͚ȧ/._ gςţV %D3c:*3ĺ&
+ [k';Z =BK#)zA9{؏U#?apy3
++d0 K8 '1ciz"nU.a/dsWcCgD/|وg]L
+2(Zx Dl0yO-Oҧ\)L5m_=-;p0M8(g=3W͙+1uQ f
+g5\7NEKGszGr=H}}0a<MrƋ
+I] t< [F.wu:xhʀtU;'(
+{[Ğw\Y@Qjsn-^ :}O2J'U!'ڮ*2ľ-^>'
+')i@.r b~1!ݏ^x4@; E0qG Oh-g+F.Q8ܯy<NȆIN?3͇ٹm+iW0ql!OPbܐӰ-Ǯ=b hg>j-GU7c'@$y{ CT7eD10Lsӗar*9o<{󲯄hۇ-۵^Eo{,sMpk͑DG$6VO8O&0q;7x}c-ֆ_e:d* %"?{osq`/-rMdP,*2 {0n--NR<紘;l=*UUP<ɴ}R]!!ߎ//MT!I4[czp7Ej"oΪ_ŜڏSC@xwzM艀ay{A
+3inVōe(*t '`ipB(zqcJu,Zf@0cTӚsBs)vB
+f}|ʅX<Sm@˵
+y ܑ<^ ?Q&UR%(\?#eѫw 5^pa B?'o akq,vxkpdN{#G
+ط񛱮ZjIoasX<|,ZQ}|&ŃuXF(>Soaljf{ &8{W;Lkm|ǯ,0W?k r3*(! u62L
+endobj
+1196 0 obj <<
+/Type /Page
+/Contents 1197 0 R
+/Resources 1195 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+/Annots [ 1199 0 R 1200 0 R ]
+>> endobj
+1199 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [349.3372 639.976 368.7643 650.8799]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.10) >>
+>> endobj
+1200 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [254.9916 226.6648 269.4375 237.6535]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.7) >>
+>> endobj
+1198 0 obj <<
+/D [1196 0 R /XYZ 72 793.9346 null]
+>> endobj
+198 0 obj <<
+/D [1196 0 R /XYZ 72 581.5302 null]
+>> endobj
+202 0 obj <<
+/D [1196 0 R /XYZ 72 352.4137 null]
+>> endobj
+206 0 obj <<
+/D [1196 0 R /XYZ 72 213.0907 null]
+>> endobj
+1195 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1203 0 obj <<
+/Length 3345
+/Filter /FlateDecode
+>>
+stream
+xڭko6{~Š X}(mZ\4xo7[)R~LI8˔DR$ŗGnMnLLxgߟI6;L#[)`gY*7K BM}ԿTg?kIJ*$D1}}sv6
+e3tRJ! b|Co;QtVB)^hҒeAZ^Q
+ym?5@r DqN`:6;D$%2|T:4/''
+
+C"8I4 PLEL?hk~2p[z{w6/٪
+R8WlZF8 9e|\a[BK7|
+_Om93 ?[K<|A* cN[ $:Dp>3<q֍
+#FC
+g-%v)H|#Fh{HN0C"McI ,Xu*B!d'W%57
+=blVe[17
+
+{A9 k[yĐNL2)[SBwtv5CI/
+@/M^($M9);=!g#ƱvW@ _U+[f 0(D f)&*ǘd"/?=
+ dOCt(8X|
+ˮYI/<a6Kw/a
+"' L~-c[TZL{] bq}ǒ,]>Cb\?g7cnuLCcOa=ђdR )R((UO䝛s{,k!`hCKxym 8\iWW_\$>Ti|5/zMx*qs}u]{ Y$dkHtCW&Oc$QR66߲ '.t0Eqlqv& 9:䝍3u'<sY$*ֲHX
+ܥ?خB%v4|exOGkI Tb\`-k0}Ѷ-0VO734Cכ
+}Ta2wUwgn=0\4dKfss_8ӣs61;[2D1W$EO.J-`JiY(o1IKiר'
+ N/ =߾V ,Jt47m؀J<V/h%^UBzA}^ Ȋ7;b }Xvuy'ىV;>f7'Wj&λ8Xٶs~s:|?i4Rd*_HIAc:3˸RC/cN]6* |jEj0$KBjFuzT4p+g'hcvp7{s͓{L¸+8yV%}1ό_Loz{(B9z6E|c:r(,8 )<!
+ׇ1l iᅛxڂO,i)< vjdfhe<$HQߋw u?t<ls|9,q4chm*
+1L`<
+>pqfjAh9g
+ ?n/ 6`jM8k/ ]i(Zi5-xeK ۖ?&^x -Hk=wD' #/endstream
+endobj
+1202 0 obj <<
+/Type /Page
+/Contents 1203 0 R
+/Resources 1201 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+/Annots [ 1205 0 R 1206 0 R ]
+>> endobj
+1205 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [336.1269 675.7984 540.9963 686.7023]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://perso.wanadoo.es/jbezos/archive/spanish.pdf)>>
+>> endobj
+1206 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [283.1155 576.2085 297.5613 587.1972]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.5) >>
+>> endobj
+1204 0 obj <<
+/D [1202 0 R /XYZ 72 793.9346 null]
+>> endobj
+210 0 obj <<
+/D [1202 0 R /XYZ 72 760.4491 null]
+>> endobj
+214 0 obj <<
+/D [1202 0 R /XYZ 72 637.2529 null]
+>> endobj
+218 0 obj <<
+/D [1202 0 R /XYZ 72 311.7839 null]
+>> endobj
+222 0 obj <<
+/D [1202 0 R /XYZ 72 186.5503 null]
+>> endobj
+1201 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F83 1096 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1209 0 obj <<
+/Length 2955
+/Filter /FlateDecode
+>>
+stream
+xڽ]6} Oj߽^ܶ &8Uj[[)ߏ)==A2)IC#w.WE'ٮjϢߝIFG @DogD},? rמ%Y>g?T.E^L)}otLeW7+9^կ8Hh?nJLuU*@tW{6(@62.E&rDʳz:{'iŲWl6UfG\zD*w /,NG#H:ѝc~r/JJ ԅ[Uk._*q>i \p\A:':Np Xaq=H}i\˳TըOUǖa63Zn ͽs7*qaSL`րљ7*Ý]p&@Wq]@+2*Ju_"%8nY
+Ti tPJZ}H(wXU+#,٢dW2NZcc
+Z5 gmo[?d͇r'EErm>F#A;NDE;}4?) ͍P Be"OEi'fx޻ku0wc;W^77 xQ3EEkݍfxC4'crx#qlkӚ08Q"/P*"%H
+ǔs+/Uw=끨2dBBwí YGN$s!ahh(F-De ִwtFmd"EfH#Οn08+8'p` ޝtoA77d^LUA`hhC yq2Ix=ZQˎF(V*bƌ{tJ ka F:wpp?N풩}?)d
+s Sjh1 {`tC@cŐ˵/o12~L\kHg 4Ce:+Ƒr%dl֎Ch]yiuW-hx' 'i>i>>bϋ 8.AM輢GU{G}|'{C8@7SYa &HT1Nf1#{lܗttҩRϼhu|9Gʀ5]ua猗q9a6> |ɰV!qBL
+ Ui_!,L!\E/u~DM,K`xtV9֦SV`\s /ca1DO@]8Qr˄2I>eBB+_6̼k  Y1n[ފi,LIwO A
+ K}g1M90 [uD%5*%dj~4^T :tI_o"$M_^!s
+|
+7k!J.wX,Z,U^d2@- YX۩RPc ܾcou(v
+eFa0 "$IRjN^@xtyz5<r 5X&}xg=sHa4@a7uIJ3o[j5I*
+ hoV%Z%endstream
+endobj
+1208 0 obj <<
+/Type /Page
+/Contents 1209 0 R
+/Resources 1207 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+>> endobj
+1210 0 obj <<
+/D [1208 0 R /XYZ 72 793.9346 null]
+>> endobj
+226 0 obj <<
+/D [1208 0 R /XYZ 72 567.0662 null]
+>> endobj
+230 0 obj <<
+/D [1208 0 R /XYZ 72 482.6447 null]
+>> endobj
+234 0 obj <<
+/D [1208 0 R /XYZ 72 380.8533 null]
+>> endobj
+238 0 obj <<
+/D [1208 0 R /XYZ 72 140.7059 null]
+>> endobj
+1207 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F83 1096 0 R /F41 842 0 R /F11 800 0 R /F85 1123 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1213 0 obj <<
+/Length 3098
+/Filter /FlateDecode
+>>
+stream
+xko"րWERSrm\
+©Aw&9?{P;D1HB.gcST2HaoK_Eu~>6qmv%yjHUS7FfR9ߵpg=VDH&:Hh{)\ ʞmOo{WD4b[|,jydLmSwk'XłuSRG&F}2Jxo;tiͶ[DOõ
+E"@>8CWh`e"6Aweq9i۱n#:=&6ʣ,K|KvaIb2 8~hi`
+O@e[>նp̓EPcltggKN
+ aw}D7c|!q`7'OI {*A@=G[W?ٮd[猪{+wqcL<ʳLI {XY*2m(Z:,h֡bGBɶ|UF s|_: -IQu*>5}u+'c8ĸ,O&oxL-q'd@- *0y,O
+ޢS;s]ͪ)AtKKLH5d32z^H@Y~圀DGPT0̺Q*AϼYYYK̍='o9 |g::'VkpB.gc 9t !(cŽj[>7 ;<TpRQTγ ߠjmo}ujD΂P&ISvDda|" e7>>O+4\lU Z[AK$ʲu/kd߹ eV$BE(rȾ*G_[FEqDo-)>1Pe4Zj}fgBU ub^&̿+ֽB<{*.oA+O*"j QyZI<߬`ƞK)̔2X*a@hө=ҝ^@ZXc5A\D;b;FO!9 'ߏrᦫ )}U~ܤ0Ԙӂ&]@0$@k24QlL% @
+)d)DG2Ba{dd * jy ]4&Dk)~{5jl(c6rK!,>rQ<yxzYOp_ 6N Hx7wQ>==&\L--谱?<=='ܿy\<_G/lDK^fB\ `zvTt6Zj%A!P_ᗃ+ďcSNm1ݸ_Ew 9~:9;]ӛjm6qtU]hgϹX*.•թ:ߊčp O,/,!$ҍ\^^֕5;O#) |v>aC-Q
+xu.C7K0.m nyshVI+%N"=T]?M
+`,jNJ Tv/Uqtp ܖ]CwQ %PMӥ0ްh+&&+Ͷ#!
+9*o>w"uMw1'-J]]n%;i` _n6khM{ۆppv{ LOMi}".!c@3#<{"#lV5:Н=.񜮛}!: "u9- 5]I/*.2ؿ'Oydxbx\:ۺOs OOxaWHp2 o\+ >TסCV$ל1|'endstream
+endobj
+1212 0 obj <<
+/Type /Page
+/Contents 1213 0 R
+/Resources 1211 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+>> endobj
+1214 0 obj <<
+/D [1212 0 R /XYZ 72 793.9346 null]
+>> endobj
+242 0 obj <<
+/D [1212 0 R /XYZ 72 580.8529 null]
+>> endobj
+246 0 obj <<
+/D [1212 0 R /XYZ 72 478.5135 null]
+>> endobj
+250 0 obj <<
+/D [1212 0 R /XYZ 72 157.3451 null]
+>> endobj
+1211 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1217 0 obj <<
+/Length 2130
+/Filter /FlateDecode
+>>
+stream
+xڭYo6B D zֽb_ݤ~-VWWnCdI``Rpf83!? cboS\`o v{>LF?/~{ t#}(W\ r=aBqՏLx0َI~[h %+[,}*"m q1ݸуMfOZLEJ a1'EXTzaHpyFyqJO8㟬:iA6sYVVQ`.aEsMu!1X"ܤe[iיioYH6+du=T=
+0#:dp͡lߘr8U QI ?Ymڀ]n' bm,-L٨AF͛eU"/RM+A<('<0(ֺ%񨖮<[i.:lZUBϐa`"ia9|P:vN\Ix08lט@\-5tRʬΏ[!
+d6@ ! iGsL ?h:"h[/` *o IU -d[K?z껬 oiOͧ4f v}^O01iTNͫR, 0.,Alh&9e4*62TOϸj?!W֛3Abf~Va-PS8R
+իJ#JLѥ6VgCH-lur2"HИ<Kd-;W€qG<1 mQ)FP%L|7LCfO55lq9;&E֥(:Sb
+(f,RiREڦSYJl)\{c|B$Ӥ/^vwDk'<L"l
+3X봕&OXW d|2R5]Il=!
+BP`8lk [jC 9L?r~OmlfRI?tz{TD +*;ZH<p(JXR-a||
+FŶ=_@(IZ5_֛}|pr]zY:P^~|׿.9bn$5«oWn1._zBե)<e6{ݣ(d
+endobj
+1216 0 obj <<
+/Type /Page
+/Contents 1217 0 R
+/Resources 1215 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1194 0 R
+>> endobj
+1218 0 obj <<
+/D [1216 0 R /XYZ 72 793.9346 null]
+>> endobj
+254 0 obj <<
+/D [1216 0 R /XYZ 72 244.2565 null]
+>> endobj
+1215 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1221 0 obj <<
+/Length 3052
+/Filter /FlateDecode
+>>
+stream
+xZm۶~*͘ k_xαk_LL'tt$RK_P|IviK`Y$D ͐f\Fq8aP b?] 6 ##5\*xw~VZz}H*ۑכ-cM$jmۢIeL^d![`B|}!R7W__vH2i'EXh-;ÐXE@ڈEZniD:MlKҭGaPe^e\\^&uN:*fR]( QPj&M0 0[ze6,x4VSoN ;Jv뛡jd4 s  t_J@sd=꩚$$5Rg;%*NoK=] jB655iK70nc_z}7
+ejMSIZNXHBDcFN $QGC),_0 QU<((Ge^*/Y첾=@BD
+ӶM
+|Wn$8O=(^K ?z
+x@@;* I0CaߵۥX87QCҢv]Ktx{ūHBQdv Gə|x(!1
+Ž@?]~cG[(
+Զ=L1gv'8:;4yq?0mo,Rqb^$@#1>>w41sޖ>mɛ._#Xг 9cHz|ù,<lwWj]ƎT
+Ecd]3q;(BG&4Tt 9K`
+sMл Mѵ'?6Wb0HX7v-لMS&nr?qu9mCq7PϏK 4 [zT[V?O $a8,*&/utc"t7TCw
+z8)6>i 7l&{u퍓.ja7%51J(^8Pdr^[ƶ6I 48]@{~f&
+&7E(xA~cЙ(8y8.a =
+GQs2|EJP5,;d .b1t"n蹩YXܻ9 aԶ<YT.t/nҏKXC[vdr@V:{st;O*X[|-sc~Z
+ \&:a7K%@K)oHY{΍ùwh,;%2LYݐe&G;B
+'IաtV~5;~tpW7
+endobj
+1220 0 obj <<
+/Type /Page
+/Contents 1221 0 R
+/Resources 1219 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1223 0 R 1224 0 R 1225 0 R 1226 0 R 1227 0 R 1228 0 R 1229 0 R ]
+>> endobj
+1223 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [269.737 745.8239 400.5947 761.4453]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.datsi.fi.upm.es/~coes)>>
+>> endobj
+1224 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [268.4917 610.493 399.3494 626.1144]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.datsi.fi.upm.es/~coes)>>
+>> endobj
+1225 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [385.2935 552.5554 516.1511 563.4593]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.datsi.fi.upm.es/~coes)>>
+>> endobj
+1226 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [291.1767 417.2523 426.4779 428.1562]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://sol.eg.bucknell.edu/pub/mac)>>
+>> endobj
+1227 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [107.8057 359.6915 255.6094 370.5954]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/dict-mac)>>
+>> endobj
+1228 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 177.4112 278.9221 188.3151]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/dict-win)>>
+>> endobj
+1229 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 107.6691 273.3829 118.573]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/dict-pc)>>
+>> endobj
+1222 0 obj <<
+/D [1220 0 R /XYZ 72 793.9346 null]
+>> endobj
+1219 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1233 0 obj <<
+/Length 3300
+/Filter /FlateDecode
+>>
+stream
+xڕZ[o~ط,R-/IrZ q
+{_GItX˹94fW T@lj$0ilW5 $ssŷ*NW;EN 8ݯͱ(K%c'Ni[#0\s?2-砒$Rmp~V JZUItӉZVRxE1dБ5^mC&Ȍ6åjWh,Bu^mwi3"˓a:ުZ>ϧ:s¾w_gWi ե-VRi3BPq"x}+[f+
+*ggDr$f</NOWT
+qˇRdOY2#MDgFlKG!e'1x4te=}#ӗ5m)8WNt(6+'bLg&Z'IB^m""wC8<R(bъb-Z`q8[?ib ԫV!=@݇}rs-T~Sβ]M
+h{
+jEP^$+HY ?C8-/"2G<CטsaP& $6Sx*b`)'M
+1c4R)-wr;K ꇄ=|TaLIpk׻ns,]GX1|my_'eTb,ɄĈ0gÔ11`BfO: ՠDi ¡xb
+ۃ_e0JO6-M%ejzXEF.;l[p`=nwْU/9֬ b
+?<+w;|vJ^pB-/\k=i͹]Ov['u:jEԅxTX
+pBmT$a,*^n7wTDU7UO^xɌh1j4wSWGኻ&4(Q!US 
+xL³nD~o_Okmb#- 6 r&Ya/с}jbw,e2\&X 3'vYrsxl{>\8| 2nE榤A+˴BDEa
+B5w.
+|W/PK>G |E^
+H$\m-ٿv?endstream
+endobj
+1232 0 obj <<
+/Type /Page
+/Contents 1233 0 R
+/Resources 1231 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1235 0 R ]
+>> endobj
+1235 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [206.8528 391.5682 221.2986 402.4721]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.1) >>
+>> endobj
+1234 0 obj <<
+/D [1232 0 R /XYZ 72 793.9346 null]
+>> endobj
+258 0 obj <<
+/D [1232 0 R /XYZ 72 760.4491 null]
+>> endobj
+262 0 obj <<
+/D [1232 0 R /XYZ 72 708.2583 null]
+>> endobj
+266 0 obj <<
+/D [1232 0 R /XYZ 72 543.714 null]
+>> endobj
+270 0 obj <<
+/D [1232 0 R /XYZ 72 304.7024 null]
+>> endobj
+1231 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F85 1123 0 R /F41 842 0 R /F14 832 0 R /F39 819 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1238 0 obj <<
+/Length 3409
+/Filter /FlateDecode
+>>
+stream
+xڭZmo6_ߺ\MһE۸@=ZE+zI7!Zޤŗ!93<C._%WXedT؟%hjFs?dg SPIP9_Tjb:{s8Vd&g5[WВtuq=b:c$Ke?|#tvco]|2ZiIX K4g.FJNʹQJz$RF,Q&H5'qJ%3JeRu=_`Zy 3BH2\rzh*Wm7֯.e*/.Ҍ%dq>"fJm
+# Ư;ٶmjkZ{mqwkk S9Oֶ
+iBQ uC\1؝eDlW\j^[m38L!?Cy¡dѡQ//傔,)9'!\;g2 \*dS2G-lM_׵+p U(TUXTGj!BՄ@ Xs=h0.LfZ7.Ltp`c]\`utl/f`Yp0I 〉*Nx3%#4Plѫ P>{9, 5 *l6BзCIF}I.fD[ߝhm-<p8$?-Hs2,tkN;hq(фCJ }lVU#on2)*ARza<,[N6Aн
+_j&Bok*t~ː0Za|$5U
+\lm}Xb\3dv+D7Q
+@4@[9TwJ8P-nNI倁S9E~oᴊ$B;_M0U@jH0\Ig9OD _m6ݶ{zʫm7nB0}*\UƳPyJGP LF^z"U<p1{l'Sț&yہs{8hD'<C Ss0 mݶ^āwӓ1F^B.3:h"mѯvB p/]##GL%pw}80@Z+EPce0 t4$M] ^
+t h@W+%HЧ,!`a'qTXjD6gT/ՠkD@H(#K- ft uJ62A1ó#$O;&CE]*0ԋe '.F
+)-TךR"zAcl1$}\3 !3Uo@΃$7}CB>(͎ꂨQ
+RUN:yN .zxJEk0J)ȍG͔uD#l3m/L޶^mC>
+!7Akb  q1:޾E0fKG̩sȩGCoNkBb-&tLS5 ,o_w d!eLvIk⹰ *+^pLx1򖍈BpdlEz(R26!APs0@7ݒX|FUۉ(|y dFiʴT܌OQ҈%_Afȳy`T?VqCYlt "e;4P!_bz+|{"MRAyz=}P@66-
+A=
+͒В/gg4̆8a -$KbLhvQf/P/U=$+4E\ .ila_o]p]0k]0>9|{3_#nh; *|[W&T8 g<UtfX9KYwb?~vmg~m1D>[]O_:)uA3fOl#
+y߱^0:%)7#鵹%M#r{[ӭ䂶oî.^߹M; endstream
+endobj
+1237 0 obj <<
+/Type /Page
+/Contents 1238 0 R
+/Resources 1236 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1240 0 R 1241 0 R 1242 0 R ]
+>> endobj
+1240 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 377.7342 327.8381 388.6382]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.iti.informatik.tu-darmstadt.de/xindy/)>>
+>> endobj
+1241 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 329.1454 297.8905 340.0493]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aq.upm.es/~agmartin/linux/store/xindy)>>
+>> endobj
+1242 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 67.9851 144.9361 78.8891]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.dante.de)>>
+>> endobj
+1239 0 obj <<
+/D [1237 0 R /XYZ 72 793.9346 null]
+>> endobj
+274 0 obj <<
+/D [1237 0 R /XYZ 72 190.9375 null]
+>> endobj
+278 0 obj <<
+/D [1237 0 R /XYZ 72 154.614 null]
+>> endobj
+1236 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F85 1123 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1245 0 obj <<
+/Length 2750
+/Filter /FlateDecode
+>>
+stream
+xZYo7~ׯ@i6>  (^' Dy)>}ȯ*=jK Ch"YWU
+֦c}}#R%,pHsvOd=xL$\"EQ$`%@>Yݎ $ UN%ȕ/j/K఍<Q~S x
+pXo6\?1Sp0|5e@6#g2aq̓!b!Zyc,ha’$
+x*ɇW,P*zۑ (ˮyMyBi6X \$ZW7ŵPs`rY: ]n9oR#k˦oꦺiMwNۭ]o܂[rz;TͩP*T&& U9g
+@_ӝF2}v?~Dj͆,cewwY{"d_l;R=q*={yt}3E[ZCYdzTPI&J>*܃^\8`3V`Rw̚/d'!'
+i/Bp.Ѭѷƶ5y[iB 1q)@!3N)NIH&߮NMfyњoڢq+T+vmv_|0 .,2~sMìݸCPATEnZ7vad;ʆxu<F@XP`QQ늆+
+-1}A?P֪@oNǓBy3bzQ0܄j恺Dɣ7ݎTORlD1'nA_,
+cD=^}Q
+@!
+endobj
+1244 0 obj <<
+/Type /Page
+/Contents 1245 0 R
+/Resources 1243 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1247 0 R 1248 0 R 1249 0 R 1250 0 R 1251 0 R ]
+>> endobj
+1247 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 747.3333 147.2774 758.2373]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.tex.ac.uk)>>
+>> endobj
+1248 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 725.7343 146.0519 736.6383]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.shsu.edu)>>
+>> endobj
+1249 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 672.2417 233.9511 683.1456]
+/Subtype/Link/A<</Type/Action/S/URI/URI( http://www.ucc.ie/cgi-bin/ctan)>>
+>> endobj
+1250 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 465.8426 242.7581 476.7466]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.cdrom.com/pub/tex/ctan)>>
+>> endobj
+1251 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 412.35 257.2831 423.2539]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.rediris.es/mirror/tex-archive)>>
+>> endobj
+1246 0 obj <<
+/D [1244 0 R /XYZ 72 793.9346 null]
+>> endobj
+282 0 obj <<
+/D [1244 0 R /XYZ 72 372.0296 null]
+>> endobj
+286 0 obj <<
+/D [1244 0 R /XYZ 72 270.024 null]
+>> endobj
+1243 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1254 0 obj <<
+/Length 3558
+/Filter /FlateDecode
+>>
+stream
+xڽZo6_kˈ!mA>\\^+H;!,'+ XpDp&?I&$ˤқxm@fi̱󗋟~60}{1|*ihTߏ`]f,SY#}ysⵌ7@Bonfr?mvh{+^Dmm7|SDl(As )"ưT+7oI2aB 7{[-Ԟ+oKmߗ"޾6[)} ?mӷMG4et:6'SxIe6 &B/g+κaED4:C+/TaTj\x%*ӟ(҉bȱ)8f%"\竎&/+lqؗ-eu+o5qwub$)a*y9 6.| ~UT64h6/C1I))TK1F&ym]"ޕ5e}vwmke^6 lCmDP׾Loˢl]Co^ڶᢐSj˪,LA=a0
+waQXvv`kM%|j<5ә+"l<5u~+cӴp$XKoԍcuޥݶqG /_ jfVjiE"p&-lEٛw )tzZXoipa'DoQzp4>Ai^dO/ Y3H9`*5 <T` $\^ bU ujKT6W|}ҽJ8@3!9ѕU3GV/oi%2u JR%q%pl7n)aq@wg GXS[6mϯaڹ<˸ D*q,Ip~NlqެN֨X
+b@F휿A hO?%}3J'w<~'3 Ks/$1Pν $S%/"c ̪^;+A$!LMAkyt32βB#:
++Hc?P8/5ĺѳK@}:]mm{9^s796}״p(
+F) G:ǀLdO,:t|29A
+Q.ΘY;>SLlB%8Vswə̼./)W財T:p
+$)JN~f*eY<~D0e`8bUy"e“$6l5ixER?Ԅ{\?/XO
+i"S;5}R|>޼ l`W(a){J7$So!A'6WB.ە
+y?M|{‡70ajCP!~Zf 2Z!  0k5v^4y;9: Ca2~IUFJDVJOhZmSU(ҼJs/0/ abԓcfve+++/7X$YK^pX5t0cѾsN^pgCS@P_lk<l8-vqTc!Sk"=ᧇ:NweU1awOlvׯ/_PFsh֬yWjzs2/=s
+ŨY #ǭ"xVsecSd^s 68\N5[.UWBU=7))1h| 4
+G
+@=1u
+>AyAD~V ˓LiWa^65OZqZL+P3S|&Qj. w6S؇~pN8db2ߏ|#O_xÇKo)O r9֓* [nZfH%2΢D$>ҟJ0ZѭŐ'!g7mBɤ|RA=f3M)xF, 0zj RԄ7z-ṗ!򗔼`EB#뎅b.d^iip*K~L[C୵
+先De];ѯ|{p=WRK\D r W UJ*! /TC>}:rrj3-U1:#T&͸[YPXN2~fOx1+4K E5V6KנK) +J:z3t67 wk#$xf;dQHK,
+endobj
+1253 0 obj <<
+/Type /Page
+/Contents 1254 0 R
+/Resources 1252 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1256 0 R ]
+>> endobj
+1256 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 233.5376 187.8449 244.4415]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.aip.org)>>
+>> endobj
+1255 0 obj <<
+/D [1253 0 R /XYZ 72 793.9346 null]
+>> endobj
+290 0 obj <<
+/D [1253 0 R /XYZ 72 622.0042 null]
+>> endobj
+294 0 obj <<
+/D [1253 0 R /XYZ 72 454.3276 null]
+>> endobj
+298 0 obj <<
+/D [1253 0 R /XYZ 72 219.9635 null]
+>> endobj
+1252 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F85 1123 0 R /F83 1096 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1259 0 obj <<
+/Length 3109
+/Filter /FlateDecode
+>>
+stream
+xڽZo_(ҽ׋[ HM
+y%Viw3JZK>p/j&ܘxcr%rM60 fY*q׋~6%}w$?ЉDrHt:ŧF.;Xeg\I"\*~&M641nVr>pK˟oNr)I3)`ed4\\ߌҤIwHRr!n
+:tWy&]t$|jב2!T o"n.n4"$o(:@s8TuUp,6WC嚃{mvY&䛝̄1:+}Y NF\CamG&S-wMnRy̶?ܪDbxdxբ? @
+|Y,@>漷Eo5^1S=?/i6%/(ޒ9C)WcZ(]
+ܷ^h*
+Gz}uA9Dk7w6 SimPV`7PaC_. W+ pRImkf䀹ft@e@W\M@Nj0sp*@#8 T4?NRő~7}4_<4p)N,2ԑeejQgFi2W-H+vh&hU8V <S޶峨#E2LAw%3liU-%3:QmdGj%0sC7qOWOhA]p}̶a0&BdNxqu><$ ?<tlhx0@VOB2SEd@ŊC
+8lm"ĂA0 ǵ\j4l&ah~>;:vr'@~1ԃKigqoHcg`Zw-MYƢen+F<Hj9G)}0BG.T_1iчwO=i }SG^=DؔLctt I/D<=5ǂ`3(7N8#fNS]UI3UuSjeuXg)&$(щYT<UCNCR EDĎEbҀD<%HQrz9Ǿ"'{d;#! ?/;p,\Z%
+Hiypv"EQGzzX<IHh[s:Yn>qV V.pXÕF
+7-r@Wy*F@ǗF; GHъ+p{nL,hSwm{C
+KʕSGTkMLߢO D~
+b C v iQ.fn U5c{Rz\[Oߖjtp;"n\][0k-o1Q7 ,i"Z?,mf7_VR6&^V
+lK+:@XhK|EYa^<*Јq+EX4
+?/OU((c\h@gWd j6cz qB=H,ML}umV )lǖ0XfEH^!k*7 ) tY<P)|`򞯐HN_X* &Za>Kj#<s܎i<)t>yoFא $Jc>\>GPJ7KȒ@o T1(Y!Pzϗ;E]OOS'%,
+-?M' 3endstream
+endobj
+1258 0 obj <<
+/Type /Page
+/Contents 1259 0 R
+/Resources 1257 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1230 0 R
+/Annots [ 1261 0 R ]
+>> endobj
+1261 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [298.767 503.867 313.2128 514.771]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.7.1) >>
+>> endobj
+1260 0 obj <<
+/D [1258 0 R /XYZ 72 793.9346 null]
+>> endobj
+302 0 obj <<
+/D [1258 0 R /XYZ 72 661.6258 null]
+>> endobj
+306 0 obj <<
+/D [1258 0 R /XYZ 72 622.9111 null]
+>> endobj
+310 0 obj <<
+/D [1258 0 R /XYZ 72 549.1405 null]
+>> endobj
+314 0 obj <<
+/D [1258 0 R /XYZ 72 435.9992 null]
+>> endobj
+318 0 obj <<
+/D [1258 0 R /XYZ 72 304.0817 null]
+>> endobj
+1257 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1264 0 obj <<
+/Length 2908
+/Filter /FlateDecode
+>>
+stream
+xڭ]ܶ~>HNES 򠕸gZiǗ_r( )rf8o"7ؤyX&xm`763q_~6
+
+=mdgo#[@H2 +$@<bY"`ǙpC7A2և_ :,*F8{E
+xcMr&7o{ jĩmңf: D$X#$,@NaQzH<*WԃO}wnƱhOTu(nGOJ Uz KG|MC}kG=sb{^}shVP1hIrx[Dd!?}9Nc4OElƁp{I'{zŽvrlbXh_7}c,cn1)
++yDUvMW:p|<GnYaqS."*bޢe4qLOw
+0_MKOO]hn
+cٵN=r2JҞ!Eޘ1н=&#?kJtD)}(J{nu+i"cۈW2ާFJr<cx"ZU 1:([;Kz<B5A10/Sjo6A'eEr,2FtZ*z] x*ݷLk>ա돚
+2w?c"HXGO hSs1Fm9Kx.^MNW
+ gUdv;%dD Ƚ=~Ncbáj!N3vm՟*ISͅ Yσ%8Ayq$<֧iEU=@$X&<MqBn`޻~7|*z5+3*$cg Foy,'@‰Kt`0P;|`pJށ"7?2`C)ҼaAhb6/-p;RO6*v?3C45A348^2q;wU_WPF)&/@
+7̌_g@&>^Kx+ViN>4
+^^Uud J@t:Ȝ)-}bQ9BPf#
+MIV=T،=B-r͊EYEꈇz[,1\_km-s
+V恹LVN?bq%N*|t9dJȮJfZb1h.] DJMh±||^vWʸ$7E^,Y
+^+g"ÿ9e2l B1oZs2ת(+ CK %%׌|\` uqm
+7)a|Ǟr(F \<x$={XA
+"'ucދwd&eEU2; 3U"BqYSk0o MujĒNJ5XGp4vr{R]" u맺 ]B:WCk?
+endstream
+endobj
+1263 0 obj <<
+/Type /Page
+/Contents 1264 0 R
+/Resources 1262 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+>> endobj
+1265 0 obj <<
+/D [1263 0 R /XYZ 72 793.9346 null]
+>> endobj
+322 0 obj <<
+/D [1263 0 R /XYZ 72 674.7879 null]
+>> endobj
+1266 0 obj <<
+/D [1263 0 R /XYZ 72 562.9363 null]
+>> endobj
+1267 0 obj <<
+/D [1263 0 R /XYZ 72 423.3159 null]
+>> endobj
+326 0 obj <<
+/D [1263 0 R /XYZ 72 196.3295 null]
+>> endobj
+1262 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F85 1123 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1271 0 obj <<
+/Length 2568
+/Filter /FlateDecode
+>>
+stream
+xڽkoܸ!րmεAҤp\*6n3VZk(Xp8{
+pergrK#u,!AMKɮ7Us3B-mmk+`Xݶ-cFiai>5JnvneZ{|r1e E"cNr|&
+&S5_Q& z̕+oSp^:mԿˈ _V#)(
+śu;JD)V`4z \#xk7%MӕKăf3T*3nF-D=W7ƒǔ``>emM&.bpʔ"t PETh"wU:˶41yiE)H:|rPQA{'HD
+B Iz24l
+R[Zր= >;!]|0rd6+ $mAEq<fql_HH<RJ/NRr!V٤"<E1O>rW.[,6wXCfZJKoz&4н_bcY
+c9X~FcM4|)Ǐ5 Ǧ,+̝6 q&ڙJ/Dn?d
+s'ocM\o6^
++WkT!gm4O4=Am8|BTrZCIxvGrIA>#M8IƦ[=й"lhUʶ
+bFx>Dd ϗm`WYa> ˥>,MZ4>4O٧G;6& T[Q;:6Pg-DXIN@jNcM8ek Ȧ7ɗh\评a\]Ce1LE?zM mfyݦrMQ +?3Ej{'̐P.L()w~)A\sA?;V4++X][Aa\זf{Sq݇裞Ud.P[bi]],,
+2 >/Lendstream
+endobj
+1270 0 obj <<
+/Type /Page
+/Contents 1271 0 R
+/Resources 1269 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+>> endobj
+1272 0 obj <<
+/D [1270 0 R /XYZ 72 793.9346 null]
+>> endobj
+330 0 obj <<
+/D [1270 0 R /XYZ 72 442.8843 null]
+>> endobj
+1269 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1275 0 obj <<
+/Length 3255
+/Filter /FlateDecode
+>>
+stream
+xڽZ[~_^`M"RTZ')4M  ,{#K.g ;!eK'PXp8oFG8TLL%fUo
+ôLswN+A%Cٔ]^S/_uٵ ȡ&CV 0vyQě;p*RhC>~dž~IXxxEM6a6v5O+u`$V_ t AQYj6s~8S_t]
+~(1^yWSӲ^n^߅X<y-F^@׍,[
+loV5l 8v V],Pc %9pou?>. xQ4
+{ v
+&d,ݝӧ KmrF9i~9{|0h9;:"c?ԵE9
+aOiq 8l$/dg7%R~ SCVT (完SiY)7,Iu:yf
+IFO"Q|>>UY`˄ai3=JX_m).:S=mV%ąq!LPTY&$#Bp8m o;vSW`{.**.)j˩v>
+`4P [:B6~g2
+~.b5sDb>V=& -qxV" pl
+^ܬYWX*E=
+SШb/0E7#DhGXm<j7V?c!xXyMԎSb#8hxQ7TeT0 5>猼><U#($NK>:qX8HV Q
+:x=z8H
+endobj
+1274 0 obj <<
+/Type /Page
+/Contents 1275 0 R
+/Resources 1273 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+/Annots [ 1277 0 R ]
+>> endobj
+1277 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 290.504 230.0653 301.4079]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.radamir.com/tex/ttf-tex.htm)>>
+>> endobj
+1276 0 obj <<
+/D [1274 0 R /XYZ 72 793.9346 null]
+>> endobj
+334 0 obj <<
+/D [1274 0 R /XYZ 72 760.4491 null]
+>> endobj
+338 0 obj <<
+/D [1274 0 R /XYZ 72 615.6375 null]
+>> endobj
+342 0 obj <<
+/D [1274 0 R /XYZ 72 586.9723 null]
+>> endobj
+346 0 obj <<
+/D [1274 0 R /XYZ 72 377.2867 null]
+>> endobj
+1273 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R /F85 1123 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1280 0 obj <<
+/Length 2544
+/Filter /FlateDecode
+>>
+stream
+xڭio{~?:/i=)P`(dIѱLӒL'v0H>? RIIXZ=߮F-lfOWV{
+%Lfx0WTW?_lmD25]"Vw3:zZߓ4p~W$\z`Lg )5"4շwЛ<o5v
+' 2$@2F@?1Zfݾ-Z5Cۥ;M
+s$-It5[<Rn>:J$2&$qI
+H+~)mS=t CGP0lMPܰLJ`FfZK@ڣA&FdB(ashu8+S5Z9rL!@q9 1ΐY1K J`iʌ2>4M9t ΩiF?ʬ.ޞs鞦)\QOYHcREfF
+޼:>mxc{a/8~>oK
+6a=Xx97Ey7|ʶ_^='T]5V 3a=fJ(jJƣ}hf:c:c?F#0͉ bdelf@+_ fz3Ҕ7G2}Fz5!aqi
+.T6FF<ٍX֧JQFH"ͬ4q
+ϏG[<В{*/ViBNI$PL^¬9p ԼtAi]Y iF>k٬}}=n}^sY u[0*ں.VEsTr(a{!l+NvjRޝ5gcr-f~iTo<v LBu.9|PV<}Qcn^UiFzSsM 忙l"z=E[wfgezԹM_Aj;fq2`wxmd݊b4*f{(pmuHh17زdV*[dB Ar_n>|:/Aq,]7 fUv/ˏcL6)86;*~nP[E,z}X]ɻNLq%0!-M`*CezׂZ: B|r|a|a Wj }{υHe|L dWgqPj{F mhyEu<f*5}^ywG;@+3JVJ96w*F<`
+endobj
+1279 0 obj <<
+/Type /Page
+/Contents 1280 0 R
+/Resources 1278 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+/Annots [ 1282 0 R 1283 0 R ]
+>> endobj
+1282 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [419.8815 419.4507 434.3273 430.3546]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.5) >>
+>> endobj
+1283 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [482.0302 419.4507 503.948 430.3546]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.7.2) >>
+>> endobj
+1281 0 obj <<
+/D [1279 0 R /XYZ 72 793.9346 null]
+>> endobj
+350 0 obj <<
+/D [1279 0 R /XYZ 72 760.4491 null]
+>> endobj
+354 0 obj <<
+/D [1279 0 R /XYZ 72 530.4589 null]
+>> endobj
+358 0 obj <<
+/D [1279 0 R /XYZ 72 392.8766 null]
+>> endobj
+362 0 obj <<
+/D [1279 0 R /XYZ 72 307.2757 null]
+>> endobj
+366 0 obj <<
+/D [1279 0 R /XYZ 72 185.4797 null]
+>> endobj
+370 0 obj <<
+/D [1279 0 R /XYZ 72 126.5536 null]
+>> endobj
+1278 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1286 0 obj <<
+/Length 2029
+/Filter /FlateDecode
+>>
+stream
+xڭYo_
+8E̊")JE^XhoEH]Iq3|Ȳ-%[4`y#keHxU?V/G-,⯫uDVYJ_agt]xAee leg9xߙXL'ݙwMJn"6?ݳfhGͧN8qI'##NfQWuޢ[i<G@XvQG&dl0bg ɢ$YT(=e_sSת)8+Z] >~9zB>vGK2lz16N (V'g^[nm,!Bי񌳩W hɜ38&yإ
+톊~v_:nUi@Z;UP~}ƵC9$e !(zKFD"R"%tP cCIsh7ăøemܬzS3N2WnzOM }EqSn,L[f)QJXW^uLG:= Ų q}KI4
+PTyۿ9(зg`
+uHgpzEfIId&CD"{0u<J -G,Wjv0MCCIٌ{v9sOlp*[gPj
+;.>c۪A֍!nSA\ g^Q[O޸v@ל
+ES<6>a׾ &TE %xq=9:G6JR>r<p`Z&)XOء-g:
+x\JHeȯTA,|*t",,//u"şoΕ9o|ρRGo=?\D7Źj$%l.* 9endstream
+endobj
+1285 0 obj <<
+/Type /Page
+/Contents 1286 0 R
+/Resources 1284 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+>> endobj
+1287 0 obj <<
+/D [1285 0 R /XYZ 72 793.9346 null]
+>> endobj
+374 0 obj <<
+/D [1285 0 R /XYZ 72 433.5935 null]
+>> endobj
+378 0 obj <<
+/D [1285 0 R /XYZ 72 273.9482 null]
+>> endobj
+1284 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1290 0 obj <<
+/Length 2635
+/Filter /FlateDecode
+>>
+stream
+xڽYoܸbOkA|E8h-U+)z\ 96i8c8g~3&4W,W: 9/M&3#p|.8y&6gRbsI;O\v.r __2Id[qpiF%\{{cq&c\
+vFFZ"ŷד4FϞy9EWk@Y. ID%2CzW8KoeDN
+܏BgA{lTQ45U5\?UՍP֖K
+.]1%L?!GOʐ)ds~"bl]#F*aBoa*lA %BoY_ӹZ ^uaC}mg5k cX)3\ z)vv.1SkQRꅶĊfdQ[Z&ʟVdvZ2-lNۗu^ɶlw)$ޓF<歽㷶dQ]t{W$S$Ll#Xwr\݌c|69'ɴ-jF(}޻S?M١l_nWe', t;m?#8!(MpCT|07LX쿲}&2C{w*
+0{LeĜpb՗693ƨg;P)36~q,g3O6٥ϮKhހ0".L1A+$3 @YۘL:{mt 
+ wd =4(
+mT0bI I)[c t0ʒ&1(_6^
+wG4ZB-Y4e뚣5+A-B]s 4"llHSV\@*aձ
+G7ZSdӂ'b D>Ou|/8<mS@۳04d]Bo-sPC
+,CLOew_bs+biɭ4jw CP!X ݀(U,D.-< {4t^{ùDdK {
+p{;f@4V_9%\$G ,m >*YLToj@T H.P%
+MлMqb.EyX邊9JJ)Nh~9.GG(9d?J<J|(Sk| 9E'^q~i1{5SIdR,C|k! s{U;PazzR~fo
+׊r-R"%Rs;:u-{o֊(>Šɀz
+8f o(L (}eK 2_̆ǽ,_X]EAެ^BUPKQE
+endobj
+1289 0 obj <<
+/Type /Page
+/Contents 1290 0 R
+/Resources 1288 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1268 0 R
+/Annots [ 1292 0 R 1293 0 R ]
+>> endobj
+1292 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [106.135 622.7173 128.0528 633.6212]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.6.2) >>
+>> endobj
+1293 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [411.45 622.7173 430.8771 633.6212]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.10) >>
+>> endobj
+1291 0 obj <<
+/D [1289 0 R /XYZ 72 793.9346 null]
+>> endobj
+382 0 obj <<
+/D [1289 0 R /XYZ 72 733.7813 null]
+>> endobj
+386 0 obj <<
+/D [1289 0 R /XYZ 72 395.1217 null]
+>> endobj
+390 0 obj <<
+/D [1289 0 R /XYZ 72 152.4004 null]
+>> endobj
+1288 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F11 800 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1296 0 obj <<
+/Length 2842
+/Filter /FlateDecode
+>>
+stream
+xڽZKܸϯh>%,6`1냁"д4=rԢVR;CMi3A|X,V}jcor-27ts0M7;,n~n* %RloP¥f̊Pio~,eB-BI~ǿ
+g =Wl rSn?<GqE!?'"IR\(H
+s5p.e+uؠȤ2]Uhܖo7OǺ:
+Syo>
+:/Tm!7`z) ._6U=&$)20djM7u)êFfn߄N
+X ;#fyw8n*e(eW]tg90v"l "D8e$<`IsCc=E(KEL"F{>II5 H8EF) ԭX/T7t8urXs4~ޤjtvWJ.La
+
+C֕U v*Y',O20 [h*Xؗ
+p>࿅O?om"BF~HG
+zyXjd*$d&j
+c&N;X֘f8xVk'Ǻjor钐De
+C[ {c
+fXC
+cN 0Ȅg,dl4!n+x:x}gѡ
+j;l2X/Z.,Kz}éi?<q@™vkچQg_O k"m Q %6/m6,;ҋ0Te3Ǻъd,kHWtvʁI5[":I
+)Xt/S8eF+=z`܍:puM-nt=;:u
+!:/.
+rEfXȞ}ʜk}3͛V#S@!m$?S.g?$/45IlL-'ZcZw,{* ++a!\nGd%+oGcoGQ%r7\oOޔcӅ6m:JlLe7">T yJ,kmf D:%3MP bi8ӳ'`nox'ó$NN x\o
+^@ LVEn* I`;,ydFv.IƁ
+tk~ ޤ,hczI 'tDXe89sbJy
+_'KHBԵ늁iIe8K8-qǽ-fTB8᳦he3paiR ? @;bCS#brZjM9g} "&6R"%U1e
+*NgO~;(2D'~Bk`6'R}G$^k<b
+&gh 6yQ_#$%
+endobj
+1295 0 obj <<
+/Type /Page
+/Contents 1296 0 R
+/Resources 1294 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+>> endobj
+1297 0 obj <<
+/D [1295 0 R /XYZ 72 793.9346 null]
+>> endobj
+394 0 obj <<
+/D [1295 0 R /XYZ 72 646.4298 null]
+>> endobj
+398 0 obj <<
+/D [1295 0 R /XYZ 72 468.8546 null]
+>> endobj
+402 0 obj <<
+/D [1295 0 R /XYZ 72 440.8122 null]
+>> endobj
+1294 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1301 0 obj <<
+/Length 1862
+/Filter /FlateDecode
+>>
+stream
+xڭXKo6C
+x/÷\$M E >sJ=$_:6 j8Pd!넮qΫ^ۊi¤N~^}0ˆ(OɺZqGzz7J.D(婰^](LÅB&k&YlTO>B?o>^D
+a0
+\<2l^]r
+y1eNE0Fk`}J
+ݱ]8TBR(W7aBq_~XYt!BbS6w ,Dj^i}_,+ YLש:r<{ٿ{S۟ I#=}
+ X `ߪ6kչ<
+S~8}TR)M'|Ӌ@9S)N=<PcU|wL尕 I͆\X`ɳڳPT@DE*Ҙ,i'{L! q8q))!7M^9_2Kyq؅w X`]{$'|^,ضŞ=ᮥy߀Hry25 0=)?<[dIGM>.LN8א&f~õvPZ6ezU2'0ơW0Tyζ qy>)`JBD9)EH[3HK$piVfZy*Gh.YO׷D-6ph<X;[mn_
+
+Q?Wp
+*|s׭; SEf-턀vdNXЙT^%u:o8v $vq JO}GM;DaA(_YQ
+endobj
+1300 0 obj <<
+/Type /Page
+/Contents 1301 0 R
+/Resources 1299 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+>> endobj
+1302 0 obj <<
+/D [1300 0 R /XYZ 72 793.9346 null]
+>> endobj
+406 0 obj <<
+/D [1300 0 R /XYZ 72 733.4255 null]
+>> endobj
+410 0 obj <<
+/D [1300 0 R /XYZ 72 533.3777 null]
+>> endobj
+414 0 obj <<
+/D [1300 0 R /XYZ 72 150.4709 null]
+>> endobj
+1299 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F85 1123 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1305 0 obj <<
+/Length 2099
+/Filter /FlateDecode
+>>
+stream
+xڽYmܶ~b? E- p Z-oO^66gP$uij@P܇p3C`#nRŐb\no0&L3/ `UF6l.3RݼqҒ$R\ f&60"f~Nl3K[nduKBzxH a2lqadn^&o_sbP"d;w2KY*e3讻֗3v*=6ZwɽmE@!JlygGO\o L ʭRƽDf(bi&7 aHL)ڮۑl!9VQi{8Ue<\RcOCV}1YOV_-Uyڈ5"c&[ 2@3FBwQ%
+QOP[,in}CJ0aĒ* Q%
+oI.dbb~LQqԵʢbHJ{ex|o#G? E$p²x>~?M3N,HMo9
+XQ|oހkڈ<b{㈯7܊Tnr`f8ށԯY*ScZܗ|$$<ب&$re"Ӷm(gS[
+endobj
+1304 0 obj <<
+/Type /Page
+/Contents 1305 0 R
+/Resources 1303 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+/Annots [ 1307 0 R 1308 0 R 1309 0 R 1310 0 R ]
+>> endobj
+1307 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [133.8177 246.7082 323.1955 257.6122]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ida.ing.tu-bs.de/people/dirk/bibtex/)>>
+>> endobj
+1308 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 193.8664 287.2705 204.7703]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.mackichan.com/BibDB/default.htm)>>
+>> endobj
+1309 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [416.7956 154.6535 537.6011 165.5574]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://bibtool.sourceforge.net/)>>
+>> endobj
+1310 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 115.4405 211.7146 126.3445]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://jabref.sourceforge.net/)>>
+>> endobj
+1306 0 obj <<
+/D [1304 0 R /XYZ 72 793.9346 null]
+>> endobj
+418 0 obj <<
+/D [1304 0 R /XYZ 72 760.4491 null]
+>> endobj
+422 0 obj <<
+/D [1304 0 R /XYZ 72 542.3274 null]
+>> endobj
+426 0 obj <<
+/D [1304 0 R /XYZ 72 379.8005 null]
+>> endobj
+430 0 obj <<
+/D [1304 0 R /XYZ 72 349.7008 null]
+>> endobj
+1303 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F85 1123 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1313 0 obj <<
+/Length 2386
+/Filter /FlateDecode
+>>
+stream
+xYn}W4 i"QZ Hv
+H4UY& s7R!1)iDhz$Y$_$v6(TpREEG3X:wJ,yW6ID[5(B
+{:R&BVbgt& `+j?u6$3,U^:q`K< r.iHd| 16Vv
+W*0RP3t+Bc
+lF,Wqtb#mf)'5kA9RTZS$O^\MlM0;4[֕a9CeVσ?O?t1AU$%9J' ;|{RlJQ\CinͶ ݎ9ZlȾ:ҴsmKR&ȐSǟ2 F \ЦNǵܥv_MVPE*vG녜q[]h, d" G=w -i Kp:Pi*!:֡u*Jc}`"p刼x-1Y1P,U%OQ k<,<dyᙟ]"[piLua$҅XsIR2.C,@r+Zy|+*'wsއs,fhb,C)88W8K\N
+Ҏ츚!Hul-q;qAiRz
+`
+D$v{8+
+/!W<߭_E*@j BkG ,ky \a`CYY$L .K۽*=3FpD#%Udip2.ãMN`\m%`.x(&w5Uy`W<`Cdm8$ϓ@x++̴%mӌה˜,MK3sۍFpՎn2Ogp& rrwp]?D 44GDž>W9񱆼A%67ud5N ; 4^p4$ ldZZ-ͱ"FR
+endobj
+1312 0 obj <<
+/Type /Page
+/Contents 1313 0 R
+/Resources 1311 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+>> endobj
+1314 0 obj <<
+/D [1312 0 R /XYZ 72 793.9346 null]
+>> endobj
+434 0 obj <<
+/D [1312 0 R /XYZ 72 760.4491 null]
+>> endobj
+438 0 obj <<
+/D [1312 0 R /XYZ 72 667.3717 null]
+>> endobj
+442 0 obj <<
+/D [1312 0 R /XYZ 72 608.5242 null]
+>> endobj
+446 0 obj <<
+/D [1312 0 R /XYZ 72 490.0139 null]
+>> endobj
+450 0 obj <<
+/D [1312 0 R /XYZ 72 403.9087 null]
+>> endobj
+454 0 obj <<
+/D [1312 0 R /XYZ 72 292.6644 null]
+>> endobj
+1311 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R /F83 1096 0 R /F85 1123 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1317 0 obj <<
+/Length 2293
+/Filter /FlateDecode
+>>
+stream
+xڭYmo_!P@*վ/y@\Ӵ}hz. ·5P/$;Qҹ@`$w33CPtrr ㆄid&؁Џ7<##spŇ旛G-Xe<V_oogb#Ǚ 6Ul߬6T~wW?&2E0S V27ooGkWp8hJbT&Q[NF pZ&"a&X!)%[b׽)[sh]۽(R" p
+y+98Nxfʿwz_1Aj?+CSU+k{wG[X;&iS46LmmDÍ5V#9^v:lQЗUUh*=hxI攄`$l$I&zŭU7ɛ"G8Syx~鶕m}[oѴ}[0um*!rFCk In
+I\eoLዿi wmtp(Ѵ.8
+$ @/5~QΡFB'g}˚SVOg!F桽caL;h՗*(<Y
+:X҄P5k隭Z|`xO6+Q-V䄂PJ(TNp2N9auOs® IÜfv &PNyዷ!9ňLz$QCɥrso &'b2.a@R^`%r~ !\Al^3Ŝ9qߘ0튀O զqHv
+aZ !]CL(yam
+6l {rPE{չS8D1Q\(pˌkCz3&>LmZ]G2MEƒ2 eD
+2,S:gaMQ/o66bpoʦNB)Xz>]2pC?_E
+͘ID|*c:6a@ɯT*Ô`Io[xqf=L2bng;Z}(?jDkmBw
+_lEQ 5V$fًzj$4q# =2`}h*z-*xI<뜠sH@B""GoOp(T49s!wh,+O}IFp7+T<E*oPt0V
+@LN1r{F$gP(fnKF#=f[
+li,?]fv
+f +m2Vvr1ϿWD#쓉Cendstream
+endobj
+1316 0 obj <<
+/Type /Page
+/Contents 1317 0 R
+/Resources 1315 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+>> endobj
+1318 0 obj <<
+/D [1316 0 R /XYZ 72 793.9346 null]
+>> endobj
+458 0 obj <<
+/D [1316 0 R /XYZ 72 655.9047 null]
+>> endobj
+462 0 obj <<
+/D [1316 0 R /XYZ 72 569.7994 null]
+>> endobj
+466 0 obj <<
+/D [1316 0 R /XYZ 72 397.0509 null]
+>> endobj
+1315 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1321 0 obj <<
+/Length 4363
+/Filter /FlateDecode
+>>
+stream
+x[[s䶱~ׯPI`
+-*mp GMT`*t&\mA-Pk!ŏXr-}ݵ;穦P7v3fqj Y9~bGy/`ґu'[LLؕmw?f
+k.t-*/z,ږ%fj̟86ǵ|HBo&wC2,VKOgF0DRS%r ɹvMlЦ~G L;Vv!NdRX+˨G.E8"m\[pz T_J)CL]G_iuip^2Y^Zګ\W5wir5}t[ꙓƟzRGrD҂3CN4jm 匄 h8o7\\JuK lA?pT]U
+)WTEځ Tl $*3C!9X MA~[q"/ITq?J5sP*yUPH #nkb7SaöN7O}͂-m
+ڂaYjY'qLE0cL# 3e &ye!IHJS?f 2"ilK! lwlȫLÚӎB(l*[=Mg
+.D=ԀQbNeR@-l3oN w
+$#p#&fGQ|aC?я?z-Œ1苖
+j`"=hM 7ry4e ;~ FAU}-)VPrIцj ms-bçL:Z>,Π|O}2:Q$I;C^1{.aK~V p
+% Xj3wſ1sذC mVIHF" $2׼ 4(uv gm; zC{C]ԉu̝<)50VƐ&H 
+;}4bC5f(j*Z1=H#f@mǩusk><Iiz r?4]᳼ECǚ4Mkđj\ 쪑y^= N_e0"9L!<e>(zp߬ @\/Ck a{';D8w
+zb6{'!7vtOfC
+/oeq6hS֤T<
+M
+endobj
+1320 0 obj <<
+/Type /Page
+/Contents 1321 0 R
+/Resources 1319 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1298 0 R
+/Annots [ 1323 0 R 1324 0 R 1325 0 R ]
+>> endobj
+1323 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [158.2976 529.3344 172.7434 541.2896]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.9) >>
+>> endobj
+1324 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [211.5357 475.068 233.4535 486.0567]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.1) >>
+>> endobj
+1325 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [203.0171 255.2775 217.463 266.1814]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.3.4) >>
+>> endobj
+1322 0 obj <<
+/D [1320 0 R /XYZ 72 793.9346 null]
+>> endobj
+470 0 obj <<
+/D [1320 0 R /XYZ 72 664.1338 null]
+>> endobj
+474 0 obj <<
+/D [1320 0 R /XYZ 72 241.7034 null]
+>> endobj
+1319 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1328 0 obj <<
+/Length 3102
+/Filter /FlateDecode
+>>
+stream
+xڭZYoF~ׯ@lX,l`'ڵ`šFtx#OU:, }t؊?*NIViyFW{Xm¦V 78v@%2l'L(2aLF:LgO-X'$“u}vP+Xx;zaf(]8FD7[$69I*M܌i.GnϾ S
+ˮ^D$QBG^a1a=;7TQGtt 4uۛ"lH`nZ>O;rW问p]"*lC vY'O_1&MXm99\-Idz5Y-7J̴vOuGs6KߚvM׷y-BkxM֫-^ub)PLeYfUMgUGXgnY7
+㞟QwC/GҺlL[La?7A*M4;҈D*(Kxd5YmAQ\I*Vt"\i^h;ZF@zsꮻ~~/c6({½K%1덆:y"vi"̪.7X㯿\obFHԺLZSRZӅCKۼ<әҗ.+禼u꼲x,j{AjT޸+ƫe8"ې
+RfԐ)I]L_uʜ(a3f&8RhV
+BMyDoMb* I_ւWmLyHlqOd V6U6#3N5LG|T]CލЪQ
+2DDhs^ʚ -Yi`)Ds)W*$QS rʅU]Bϲ.5b8yXZ| -g$apgs@
+tOw
++-|W}_Ђ+g
+
+ L"zր3XvU,$ȭX%ٽՁl&.޸MK=u
+>bK(
+v+G|E5Q4x f( `Da]nDwMǟi^ 8(j?OK \ɾCLi>ƨ$(?zAQWG-E _,7ll(-$0c[9|,i~}JZ&t
+¬T87@oDIǎo5:x(C=2{.MC87Qr,t~ʊby̠o|+{P2+ĉ©* Љ4M]0|$4iwᇇ~m_<ٰv)Q|rJذ ,]IF 5@pRBP Rq%%J#Kql DLGcr
+qlڢ^iߩ/jh
+e
+endobj
+1327 0 obj <<
+/Type /Page
+/Contents 1328 0 R
+/Resources 1326 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+/Annots [ 1330 0 R 1331 0 R 1332 0 R ]
+>> endobj
+1330 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [313.2827 680.8626 461.1063 691.7666]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://w3.mecanica.upm.es/metapost)>>
+>> endobj
+1331 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 649.6198 335.0803 660.5237]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html)>>
+>> endobj
+1332 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [199.2715 442.8353 347.0952 453.7393]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://w3.mecanica.upm.es/metapost)>>
+>> endobj
+1329 0 obj <<
+/D [1327 0 R /XYZ 72 793.9346 null]
+>> endobj
+478 0 obj <<
+/D [1327 0 R /XYZ 72 292.3348 null]
+>> endobj
+1326 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1336 0 obj <<
+/Length 3716
+/Filter /FlateDecode
+>>
+stream
+xڽZY6~_G7f  Abym,9<'o%=,bXWEXdrŌbs1_a|w|A^qM.3Xt?̲rÌ6 rK,ta"eήW {eW:+ع+^
+ĈNrU`fdpsu&k^xk9LjĤ4]d*c(e"򬤦+L4S fY5Tu*I
+˺'ݩ+O3♧L,wKŮlXy#ӧMSf+'mID7FPCٻ'A&d*EfHt!Xd"B*:Ѱ8ld/܃\|1!1'cnʾض@_塰darRˬTju)RڗDx-'dYvDF* Tg'MEOwfYPu)fev =Ǣs[-iOUkLtp}lmU6nue_qw]=Oݵb Lf8ݾ%<upn/׹(8̘:o8Œd}r L&%D{8V53X=n*TVgCuKA> Cq,S"zг`Dm '-hB}5MrD\
+'IQYW6@
+g슎nmXǡu@0j/^
+5нX0Y mXéU1×2c9>c-t>wrW5.,-!OƂ@e&#w18ODlMtOoNS6Mdq&0jnjkihڹvA[- "mi4X\eWb1 "yMȜh
+P
+ b3ɳLarp
+c+G_u}L20O &IS Nlv*meMkc&a6㿏x^AtUqd*?a#vz땅_7gMSV:|ewr&Zm1uƍa
+ĢcwI]
+S2ie"c
+ox%LFpݔE^1!ٺkX15tw]ݡFu죶
+XL>9YC鍳^аyG1nc3ݖ̥9GxZ]ٟ{lQl6y]L>4iplO>E-~9Zs;ҭl~z9\u<>m쫚%;٦~IqZ{vRj
+F8wq #( ޷O,`B} +0K@i@4zSf :f^(V76ؕkx ũ.ݜ,lK˶ݜ0ޖY}Q|}X ۡm}1 LgsN
+^ͷ_^;`ǖ1&.D/Q&0[8-ə
+w="6lizlR-⤮+Z3nwe\? ;^=םEyzeDs{kiFug"c)u_^|+
+Ztw5醾U
+G{*kj ;ʑJ/ls&k˱ O8ȗeʺظ,Nh&L,ĉlc)ݗͦ8Be7 N ?{u6=y> )Os#/N):?aQW>
+aۮe @ <"yKp5ҽ+P0i=E@7yҩH3}[m$TO`4cAFE;ConJ B[L% R&)~ *`
+ sܧ^Ҍ>(UL3ETendstream
+endobj
+1335 0 obj <<
+/Type /Page
+/Contents 1336 0 R
+/Resources 1334 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+/Annots [ 1338 0 R 1339 0 R 1340 0 R 1341 0 R ]
+>> endobj
+1338 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [443.2547 525.771 523.0151 536.675]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.gnu.org)>>
+>> endobj
+1339 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [187.249 155.2181 209.1668 166.2067]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.1) >>
+>> endobj
+1340 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [397.2081 87.1584 489.8698 98.0623]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.adobe.com)>>
+>> endobj
+1341 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [162.2965 73.5295 330.6432 84.4334]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cs.wisc.edu/~ghost/index.html)>>
+>> endobj
+1337 0 obj <<
+/D [1335 0 R /XYZ 72 793.9346 null]
+>> endobj
+482 0 obj <<
+/D [1335 0 R /XYZ 72 512.197 null]
+>> endobj
+486 0 obj <<
+/D [1335 0 R /XYZ 72 387.3638 null]
+>> endobj
+490 0 obj <<
+/D [1335 0 R /XYZ 72 201.7468 null]
+>> endobj
+1334 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R /F85 1123 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1344 0 obj <<
+/Length 3498
+/Filter /FlateDecode
+>>
+stream
+xڽZm_
+x5W|KR (k(f>dIᐲ}nq Xp8噡*?J*$ˤW&Z/7G /7?
+ &b*KWhDL7*NC# IҌe*7HXīŏntE|(con7BGfc_-pNJ,HsaF7HRD\ gʭۍz(mmk|NESg5MO<qa(>P[<}Yۢ4]捧pFMeR:LۋxZ8@'`DvΫCY4~zV,ND6]K/)a K|X`QdOՆK4sfYl|tT}|Zfi1gB&Ow_z?*{a}!3#&k⏘t~v:'
+O8Yq΢E Ƴ8qc݈bjÂ1B99
+=?t UME[׶K4ʚl=t+><5 zy<Θ2h%^:ܘe&a* -b ;]Ib_jHuCo;}Z50wKS&Q<[߫31=绰D{qE j]Wf ]?k<SL( Nv(ƫUىJERQ$vy9hS:G5)J`a]>>ufG:kTl1T`x]4vM7k
+򹮿
+bpJd5Ȋ_V!ϥuY'ق g2M|:RsKE#gKF8OGv.и@,"נ< o)uSS18Dx:,1ph@-, hG
+ y3%z+8+g qyLHNx _%l HY @\h:R}j "' ;o{
+`뀩!Uo|w?w>ũ^BR/_L-FZtsN"y E"kTB `NR4|-(Aah(c,ׇ}Y jMFdϷH}fo ~c.2unқDTAq7L)QKufHv+C}B2
+rD $U b lj@@T<-H I>zS!$tY0%6etӀ\
+C6@poVss u
+xZTH`F{lW{Y Jo7UALg3C(Zp6,B&qKP4!ib b4#X^( fX|"E'N/T&<ۮ-%^Y<88@ plKx?mT lNW
+BuwF_ JEݱ!/TNd1mn%߁7V'W
+Cjzdhjwrڨ.Q_eNx8(7 \L5J'hu?ёJ
+:;ҷ}){-r:0S h:BSû2o<||WjƗޝw Mmy!.R1IfPqTI*z!
+1~OuX9<K汿_W2z fK:<#q|kKohrVPt~ xy~j9[>FLdE*y*˾!,Se `/8o<ԅq3yk5CuC'7]
+Qvzg6c}f4B˰S$g@!}5<)aendstream
+endobj
+1343 0 obj <<
+/Type /Page
+/Contents 1344 0 R
+/Resources 1342 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+/Annots [ 1346 0 R 1347 0 R ]
+>> endobj
+1346 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [175.3113 646.6991 197.2291 657.6878]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.1) >>
+>> endobj
+1347 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [437.4222 300.3167 459.34 311.3054]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.9.1) >>
+>> endobj
+1345 0 obj <<
+/D [1343 0 R /XYZ 72 793.9346 null]
+>> endobj
+494 0 obj <<
+/D [1343 0 R /XYZ 72 559.8333 null]
+>> endobj
+498 0 obj <<
+/D [1343 0 R /XYZ 72 159.7829 null]
+>> endobj
+502 0 obj <<
+/D [1343 0 R /XYZ 72 130.9644 null]
+>> endobj
+1342 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1350 0 obj <<
+/Length 2200
+/Filter /FlateDecode
+>>
+stream
+xڽY[oܸ~3UئIEQlE>pfd[.I9h42=N ࡨCs>*lA[hF#dtq`5]epot.(&g@ - .kвֹ!F;P x=z2'tyõ~s#2Q5Wtyoˆ`'6IPhƍGף5Jҳ>яDʜ"Y,lA0+I2T~0b%39FIN}31Ï݊PHh2S!"VAkm]_Uv(>]mfU;U]۫ߖwJyryT iL.Fe~ɉsqKWTE*̀4GKvG`EG3X3A2'-:* \_
+=Cg7}K)kAz$@&! Zm:{~dV} ~I?qBfhMUg$cT:Ӆ
+#AI(Fp'R.ڠwSإP"ϔAL9vz0tzBkh{2HԀ}
+(!n}JR;gص h-Y~^䒙d?ފ +\}51~u6(6|6{@5g g' L/Ԩ.Z06ic\ն
+\eoY!k+OOf ׬CU@GS,O
+aʹd%féVA<L`NdiBuO#n 4iӱeVd{r4ϕe ^.Qns+m7 e[ڷ="ܶ9%ԓu~\y0۱uM]Qf")Wi[@V+L HHM4P> /u}D[ݼ?OCT6<>w>1 g64rl!)oeVV,*Fl]
+sΐоq6&uX)NW4Nsp@e
+CIftO29%gʏ4
+9E| Gɍmc_(wpߖNek[ly*==n(Z6+r?BeOuK'sk3謁ƹy:Svk!ab֏!
+#x|x<p$RhdgcpFNUqYƝMnaIYiTQnʴEF5bk54J{ҞdvA'9o< ?ȇP*'+'i{/\Wt`g:JG֥mxnQhSu+ԁ{"7`]>~`J
+VEitř3YN|*!C8+(
+]nKPLO Hޯe^"/#Q8[M t75\1 AX?kۧd@ъ?w켵JF
+endobj
+1349 0 obj <<
+/Type /Page
+/Contents 1350 0 R
+/Resources 1348 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+>> endobj
+1351 0 obj <<
+/D [1349 0 R /XYZ 72 793.9346 null]
+>> endobj
+506 0 obj <<
+/D [1349 0 R /XYZ 72 616.2971 null]
+>> endobj
+510 0 obj <<
+/D [1349 0 R /XYZ 72 532.3597 null]
+>> endobj
+514 0 obj <<
+/D [1349 0 R /XYZ 72 457.9366 null]
+>> endobj
+518 0 obj <<
+/D [1349 0 R /XYZ 72 301.1394 null]
+>> endobj
+1348 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1354 0 obj <<
+/Length 2589
+/Filter /FlateDecode
+>>
+stream
+xڭkoܸ"@ug"iC>[R\3VZqDp8 r#On2
+:N7Bl
+{ Ѝ
+4[G
+'v??llkO<<!X+R]>hJ \e3Vvߙ}]OiyD?=-)soV(.]pӚV1IlC4W`z
+n]x3MX3ew`۲m "&ܛ HE`BFJl)ԯI1<xKLCa]ű$"(@I8 \ks0[q4I
+B;xޫiW
+ܽFq"ؘn^9K."X99 tY7
+ުh;ٺp_Wݱb]7Lro:=*WSgV;@g]0\[$0g 1'd&[L]x4~H0|O2S=#C0 dr@yO fw*!\ص 3OBh.W&EʀwB NrHeQOZFGB!u?kTOFqB+3[xXZ-kWX|PC#)]ו/e^C?p de7TSu|Ľҧ">K7{ܶ&"wS4@8m4 Tu gJ  nb~
+WI_M]>9=6m<(7:Ec;ZS[z4=Ɠs2), |3#Y%BjvouxS%B|3_m9xN1 lʂn@;fs*בΓd7]42 q
+`ooxǭx $
+77ϐY34zXܥC _IϏʼ<3b);D94AD1]xf|%?endstream
+endobj
+1353 0 obj <<
+/Type /Page
+/Contents 1354 0 R
+/Resources 1352 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+>> endobj
+1355 0 obj <<
+/D [1353 0 R /XYZ 72 793.9346 null]
+>> endobj
+522 0 obj <<
+/D [1353 0 R /XYZ 72 509.2597 null]
+>> endobj
+526 0 obj <<
+/D [1353 0 R /XYZ 72 195.8079 null]
+>> endobj
+1352 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1358 0 obj <<
+/Length 1754
+/Filter /FlateDecode
+>>
+stream
+xڵXKo6.`Ѥ(JT/A$-H
+9p%zT= ER]KӤ0`1~\GINRR\Y7LrFՇxFQ+t0
+Us)VWZ$<Ei20ďÆm0\Iƴ dxs+zx4qiBQ"#z}5z" (x8'@XȌwԖ+$ tm8 MPR:8Mh.}˝lуٖ9QpN~NKKȼNߴ"򫑕U~0Ytp@ihJ?eVu>MEW~r6,6pDV6!om+CXTwOal{Q?{g/*c;_R?Ɯw笺ad@h`U0qeWhfZ4¶5iV*=}^NIߩB-o@^^v:M SSԕbq[7{OT?]q,h$˺pyeufSu{8Em|/gATwrÍ󐋀SUV7UYkEPU\ eVQdt}@sVHqȳY:ӊFv_WஒPVs= S].1Vw߲pՈlQ}|'xu֗F.lM
+11n%d2{l h>e?;F oLc!"%9WDjp;3a<FQz/fs0Eӻ-11sL]*SE ӧC]1u0pLfPm7GC@cBp
+8eM EqSg\,`l?'| j p̰ Ohr'q] %u!?Yrʝ
+endobj
+1357 0 obj <<
+/Type /Page
+/Contents 1358 0 R
+/Resources 1356 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1333 0 R
+>> endobj
+1359 0 obj <<
+/D [1357 0 R /XYZ 72 793.9346 null]
+>> endobj
+530 0 obj <<
+/D [1357 0 R /XYZ 72 407.4914 null]
+>> endobj
+534 0 obj <<
+/D [1357 0 R /XYZ 72 114.2781 null]
+>> endobj
+1356 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1362 0 obj <<
+/Length 3896
+/Filter /FlateDecode
+>>
+stream
+xڽ[_6Oa^+")\zzi=h^Jr %^o"9Ο H_0dL^% tdLq_s434&Ҝ/WBzw8
+VY,gy+_wWI-aeƮW*I1>H-Jdh71wdTe,F8RHsnFɓ{^!jJAN5F 2~6k`PtY+;J5N"IY-uC I ¾%-:˗?0Z[~EQM-ʮ44=EÛذ!d<qf@f!"e
+~gI{aPq J)L,'6CgזiT%< nn-@"pj#2Opi~,BbMLq0u,xC}}nj{Ϯ #k/W? ^[[tm唩$P1Ʒ 8˰#ֆ%<3 `Q#D)U\ߔ}UU
+ϥu051.2XKN'*3[QǶIdV,VrfVyn J>)@T<c`-uvh_xbo+}=X۹ޖێ [WkqD4H$ zA(UĢꊈX $ވ!u|.?HलX,#<ijr~)xb·)YjR1x-`7gQoiO*j#A^ƸvWCͭqgk-}ݞڈ,
+} ʘ|\G&p|J#
++5wB(ϞAmK3N x`c޷Zޅqp.&[&J?*Ajf`u9BYY@dJƮ
+F8O |eׇ $qwآm
+R
+*9"dN@K[ DfB,Ġ¨f
+ӿ|'i8PGįc~ 5Kc6! ?]x_
+P9/SF\)hUٸZ-h:X"8zZOYIur\ɏ;4c+WnC~0
+! 6. ܵ!wvRenK:.Xb%XP _9(M=F*D.#-b}C3I
+ ֛}g~$~FDr H@ :p.'4SK {_M_$'R
+ҳ bQ]ZFˆo*yH>;HdLmVr\9mj߄|c2zq3U
+I5jjJeJm;J,h[> 
+&_ mONv 8UG 4<K㿘( 1k/ޖz ,^׽3yPp 1ή,{qX&=ahFOJ`'j{_PU;Smnhzzu\eKڢ_Polw5h:
+* NK',Ix%+<*`uMCpLo2 y:4?)?#9x$y$jHwj@rX5 mQ`*vOþqQ_0ZI} Lxf#=TI[!G
+Jo4CyQ|0ucI2Gvt*ut5h}W#}! ?ۑ@㗘4‘_8d>|%_*xtlBu𧥙H%KPBӁ;endstream
+endobj
+1361 0 obj <<
+/Type /Page
+/Contents 1362 0 R
+/Resources 1360 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+/Annots [ 1364 0 R 1365 0 R 1366 0 R 1367 0 R 1368 0 R ]
+>> endobj
+1364 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [232.5506 367.9674 251.9777 378.8713]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.10) >>
+>> endobj
+1365 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [362.373 278.6372 494.3367 289.5411]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://odo.kettering.edu/dvipdfm)>>
+>> endobj
+1366 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [206.7522 189.2223 228.67 200.211]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.5) >>
+>> endobj
+1367 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [222.3836 175.6782 384.2648 186.5821]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.fi.muni.cz/~thanh/download/)>>
+>> endobj
+1368 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [107.8057 162.0493 274.7376 172.9532]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tug.org/interest.html#projects)>>
+>> endobj
+1363 0 obj <<
+/D [1361 0 R /XYZ 72 793.9346 null]
+>> endobj
+538 0 obj <<
+/D [1361 0 R /XYZ 72 513.3886 null]
+>> endobj
+542 0 obj <<
+/D [1361 0 R /XYZ 72 439.7832 null]
+>> endobj
+1360 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F14 832 0 R /F39 819 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1372 0 obj <<
+/Length 3492
+/Filter /FlateDecode
+>>
+stream
+xڽZ?z3-D)h\Kڤ6
+%$_mo&Gp8E хb ss.6d?P7,V0In~5Ylۛ<#!LtiT7?-̲UV*I.r3f IY{qeەL=S{}sb2Y>;"|yݷ0$dF8innH.yX NXJ),@<uS$ N(zh1 b5,S3AJ$$ Lp˪TJC!O)s-KaO̤#}Bt-CSu='4!v9[ W:z6"o\9V%ymU6}r6?讀r-hB$੮*(Ǭ+}[mZRwQGN,De0׋N,m]t:-Uɔe![d"][' 4' CMw?nʦ6<C62MA/iPC4Y"l3P>ۙ+
+ުwi%!=MF G B&>kе }gFRߒlmT<3{GlAؔD
+\(Dӥ
+r̟#Y[`2a/3FzA.+(; Bj@߼9ONW e;5&VNi^NM7lǺWg;]oʪrD,lN A
+(?Ze(Q% \ZyH~vQEr۶ؗ>)ҟwh""dĔ<<l3AfGF9*?;a|S
+Q`1D!Uj;7gF(vvy@Y2srhx(s2Ji(iTcGA2cU;! s:T+$]?51e8fQ:81G.kwq i$yΦڣ62H[o8 +x=4x-O :Z \_[[hѹK0J/@ ‥Zӯ/D*Gy،.RmYv}xzU%hJn)£
+<Y<Kw jRԗ`-_h<۾yƜ& yrܦJ܅[/o`g enOsNٝ 9#aHqHRu TQ Fw]R?<Qd82@&Q#Xۊ#v_3rHs Yd\<+U;hĤ=-KfQ
+ 8Ƴ= d]@2g F̷p LXd~2`E)aIzNDqrC3^o~A.{h_ (` e<uMC7CR, r֥V& o 7s4Rى+O)$#Sٸ'OAN83Ahr}w71x}M ξ`"4*Kj5$} r{2͘Q#,D BAl<<:ɲStabvҋTns çBwTQ:,*U../"FM)B=rw &,4nsj~L_^/Ga
+endobj
+1371 0 obj <<
+/Type /Page
+/Contents 1372 0 R
+/Resources 1370 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+/Annots [ 1374 0 R 1375 0 R 1376 0 R 1377 0 R 1378 0 R 1379 0 R 1380 0 R 1381 0 R 1382 0 R 1383 0 R 1384 0 R ]
+>> endobj
+1374 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [231.1642 747.3333 411.6057 758.2373]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://developer.berlios.de/cvs/?group_id=57)>>
+>> endobj
+1375 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 635.9909 271.9283 646.8949]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.micropress-inc.com/linux/)>>
+>> endobj
+1376 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [117.8282 618.377 265.2834 629.2809]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.micropress-inc.com/os2/)>>
+>> endobj
+1377 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [378.7781 596.778 506.8563 607.6819]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.micropress-inc.com)>>
+>> endobj
+1378 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [500.9834 539.9511 522.9012 550.855]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.5.5) >>
+>> endobj
+1379 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [405.0305 467.4748 424.4577 478.3787]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.11) >>
+>> endobj
+1380 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [125.8208 394.9137 293.7394 405.9023]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.mayer.dial.pipex.com/tex.htm)>>
+>> endobj
+1381 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [390.7545 323.3804 535.1112 334.2843]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://para.inria.fr/~maranget/hevea/)>>
+>> endobj
+1382 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [156.0691 243.2808 302.8168 254.1847]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://hutchinson.belmont.ma.us/tth/)>>
+>> endobj
+1383 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [457.1815 190.439 540.9963 201.3429]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)>>
+>> endobj
+1384 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 176.8101 231.6895 187.714]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)>>
+>> endobj
+1373 0 obj <<
+/D [1371 0 R /XYZ 72 793.9346 null]
+>> endobj
+546 0 obj <<
+/D [1371 0 R /XYZ 72 512.6634 null]
+>> endobj
+550 0 obj <<
+/D [1371 0 R /XYZ 72 440.2718 null]
+>> endobj
+1370 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1387 0 obj <<
+/Length 3053
+/Filter /FlateDecode
+>>
+stream
+xZm۸_ۘE6i{mqnN/>YNLyM P,9< e(.4[hÉB-6Eo.hx\,rÏb B/
+"LI Lh/*Ms?Q0Za$篸\@bjqu;jò$,55WWk&彽 -BW?^h2%)03$5\\^MHQ<5
+SlP*5Dʴ
+ZjX"JR5_ZRyFTy߮Xj3NOAk'؀B. 5Y*lk.=)Fc+Tc9*u!m]}T~ 5ET^^ݮadI"٨U/5z# |sZf<ئ2z 9'Z p0ʉb8k;{y?!x}?54`b m7`!gzj4a e(VAfӷO)a ϮZ@ )ȹP d\Rٸp/jeز8Fc8[ow^?<$Q2;
+?[pQհ*<8nYn?0޲! )˸5j8F~s؍kF(t>)D֬̅''(RR=@!ʵѢџHxϕ[7zy9|;܏tt9tFd͹V2Y|΅S+0',AU-I;?ă4o>!8)I33S
+*7!mb}hzRI*H6 EJ ~~9OQL6quʥnNF^@O͡bFc>&dL'OILv9?3Ia2ȹ} Yw*/!
+hFgF3M2kءA9KZ239NIrz\}'Y%D.B1⮱u YY}4 )1hJE~e( <2x:C:(AC<
+-
+
+,h1C`i{Է!o'kH48r'vw ?FlTX³BdXI9z#Lj I 'S;ѳS8Rú5SayMs4U|6%yq*:xREbw]4'Nozh4Qm5U].{W}^RXO:TIT$# fl+ W6
+ަ0F_X
+3 OF"}8lm;TM˞. =7kIq$ %Th9(6l)_j#I _ɰ; > EãͥyIֻBjܺ7sik'mk)^۪Vl !!A6xrAK;cSWc;o /!ʘ?=)!rOqCy8ơ  YJpĦJN)n~f]S! [A0L_ϔǃ!;:ʣ>x;ͬ'm k /KQ Q"9/O٣@hj[hX7u-|x;Swk۝2
+-
+_46m|_.G iE
+ * H<O(&)+A?EW~Kb{}tE۪Նx6㒺;IJMl2yF!g)KO}'<fQ"37
+endobj
+1386 0 obj <<
+/Type /Page
+/Contents 1387 0 R
+/Resources 1385 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+>> endobj
+1388 0 obj <<
+/D [1386 0 R /XYZ 72 793.9346 null]
+>> endobj
+554 0 obj <<
+/D [1386 0 R /XYZ 72 760.4491 null]
+>> endobj
+558 0 obj <<
+/D [1386 0 R /XYZ 72 559.8631 null]
+>> endobj
+562 0 obj <<
+/D [1386 0 R /XYZ 72 212.1906 null]
+>> endobj
+1385 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1391 0 obj <<
+/Length 2924
+/Filter /FlateDecode
+>>
+stream
+xڭkoܸAqkKmj u}]ѶrzE&q p\Fk Ip\"͕U,6IN$olf',
+8I <DrQDIO㱬*rGyqurO/
+
+'R<Co BȒ!,eum@\nڡ*hkɱA0SA
+e+Ib
+"HŒ8HGS82Lӊj I `h@LeP  J3"[8>RH4e{Q%E +N0hEuάV*"D'@.R
+,T.&O)y3ًo~o
+l9a;]Go#sWD
+s/# GKC*od`z@o]m9n Z~]K%?}x8W-]IF+IIOW :
+V4,~[@!^> Kx*3Qv@_]a 7G;Jl!
+"ukpm#8mg& 9m0^W7zmFK+KZ6l@ Dp-8M EFXcN{FI=h"8X5\K|i*}\q;ng%!) APLHc5:%F!xiV`Ba˩`0p>sVt9R(%T%/Yi;O1 d>qy6kG^Kfw
+.^] 3rWe W!/OA_,g=Kv,w{Fg"n-B xi`LR\ F)}[y.jwf *4 |i&)LVd0ONh^thq]:8V6@pG.M*0  zBTFE^ͫ(ݯ5 ZuIM #;;۳hmf̆ȝ*?,]~Ro;c&O7mߛ
+BS /a3h**x{dMLq YO_q6Ey8\E҃}
+*S!<gmA!ggXxq>JqxӺʜB
+}MuGWBfڷ\icYw"؏ݙXn[ЭB2*ôżۿw̅{C-֦&.3y}6:>#!ǑKBwjN5nAeendstream
+endobj
+1390 0 obj <<
+/Type /Page
+/Contents 1391 0 R
+/Resources 1389 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+>> endobj
+1392 0 obj <<
+/D [1390 0 R /XYZ 72 793.9346 null]
+>> endobj
+566 0 obj <<
+/D [1390 0 R /XYZ 72 760.4491 null]
+>> endobj
+570 0 obj <<
+/D [1390 0 R /XYZ 72 741.3348 null]
+>> endobj
+574 0 obj <<
+/D [1390 0 R /XYZ 72 493.1834 null]
+>> endobj
+578 0 obj <<
+/D [1390 0 R /XYZ 72 201.9398 null]
+>> endobj
+1389 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1395 0 obj <<
+/Length 1902
+/Filter /FlateDecode
+>>
+stream
+xڭYY~ׯЃNlA,6]=OE4yx=濧M֌ R]_aK
+2($AL]a frdxy]f@˂ XPƒ-EnQ,/~l@&DN]B.a'v76z#)](N.^_p
+dLHFF2Aŏ62ڼA͔¨,c(шa(qd}zҷykf_tueΌwLޙyVouff=QwtaD2`Ip7GK3oJ#~M!<pZE^] HBp 0o1]r *>ݚPEE_XŒ]~`*Ȑ;O=ۭG'bi*-< JkNZP 'A'C%$`56`W\.D*w#CD &M|f&h|џ0C|Ih<R9*]
+8ң?2Ǐmgx@ıfXLX>pC׀{]ݔc{큘Jy cK(5h/=|/صpV;ovَH$ 1
+] ͨ]ڕF]݌ hB
+iʾNW3]˼uPu'"^!^359̡Qߣr5Z?ƚD}NtR0ˆ΅Z5LW>Abbޟq*ڵ塨o<9CBoGitr\}^v] W8j KVWى%3 1ܻ4zZXryτ)H!l<Rm-$KDnJ{66 ~*pUf*SvVSu f=v81\'*dvXKjmЩnU[!qh};[ACii;:Hf^V0j4iNQ0]njəiZbRO[}yZegUo:feiQۥ%#Qt_yfwtG%t%0,mt{D
+\lPS{ug|9c0c3߆OW͟SHuތvJ|Y\f}lss)ow|}{,c>Motp2z۸~eRĊ=W$LBt붆|c^@MG'ݜ*̆To='ik{֟}}S+:*%i"VB%4_ZʱilZ |k,d8K#.Z3N:ь*Mbj@No>#"N91C
+nlq W?I$P^=)0)AhcTfܚݰc5?A:oӬ_FH,t۫)\!\>8'tU+f<!q%
+˕C
+$ pjKcb\+F*G|<9z* -g~ze)#J71tN$Q/'mdB)kHn6+çzcY:^[t %":Ga-|.0=9:#lendstream
+endobj
+1394 0 obj <<
+/Type /Page
+/Contents 1395 0 R
+/Resources 1393 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+>> endobj
+1396 0 obj <<
+/D [1394 0 R /XYZ 72 793.9346 null]
+>> endobj
+582 0 obj <<
+/D [1394 0 R /XYZ 72 571.7997 null]
+>> endobj
+586 0 obj <<
+/D [1394 0 R /XYZ 72 429.1736 null]
+>> endobj
+590 0 obj <<
+/D [1394 0 R /XYZ 72 225.5071 null]
+>> endobj
+1393 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1399 0 obj <<
+/Length 2908
+/Filter /FlateDecode
+>>
+stream
+xڽZmoܸ_a xiQ_/8\8
+YJv^8 9.I`Qh>y_xeI*W"Zm8?U B?]D,4_}iWTjx{˨elXf5oXAafEXM,cc?nM|)EJ`fT$#xu;FY7(K+Z\3k,fs<\ kf
+Ww\.yn9;6I*q`YTY^h3
+дhI+mא!]⽱ }EowE":4-zgM4=|86<Q f-NML,r"DhkM3_:e -Ze$eJI؆Tؖ"_T:/E\o5mӖε(ӧ?Mpa&-c#z.D(D=dvoCh<!*LwXL$=o()eƒ8ʬ1ogi.ivM#&(As l@z`N/?_mDOװu7 ,7a4
+HE줊g_L*/Nׅ>- d(z)3)V
+CŰFp7<DoFQb-٣8g^,SYo'4(pcIx/a*{E',V҇ Cx3{q;)Vu׷CC(d9>东_`w^k.ϛ7JLw"bUٮ`v ,QZTDhʭ GYR Х-z#M&;EQl|FEvޞ#îR]O )y1pCp&D
+3}zY8*b3>`0(7T=^pA, )i{
+b" _89b knc3`Tr7HT\݃pڪ] vcnH2_:+t*
+(
+ӑYBȲv眼˻Yw .PƅX@!dr0 >=ΉB8֚|BւSs2F:+T☋y|[s ys@j5iDg*399·j/
+k(^q͘WKȉ.sw1=F&\
+EGU!$cUfڰHLmPh7 fHq` -ᡮ>].@}T {Յ8NMET6mS9/]@W\-h-O;u4{R@fY4Qܥ*sk|EondQ4/Նӡ]jɪ}5׋5P<R$ޡ<׶Tك1f-!'V %$Hf˳:q\ɯ
+C=\'!ݤ,xx5.(xR4|5hSqIeYQ˕xv@ꌟ[,iʚ6G41`0DYL%Q:@<*&bhjGq5rblZ8kH}sG(wx7n 9 ?
+endobj
+1398 0 obj <<
+/Type /Page
+/Contents 1399 0 R
+/Resources 1397 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1369 0 R
+>> endobj
+1400 0 obj <<
+/D [1398 0 R /XYZ 72 793.9346 null]
+>> endobj
+594 0 obj <<
+/D [1398 0 R /XYZ 72 760.4491 null]
+>> endobj
+598 0 obj <<
+/D [1398 0 R /XYZ 72 508.3198 null]
+>> endobj
+602 0 obj <<
+/D [1398 0 R /XYZ 72 479.6547 null]
+>> endobj
+1397 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1403 0 obj <<
+/Length 3470
+/Filter /FlateDecode
+>>
+stream
+xZYo6~hSfD%L, ΃,qlM-Ex_U,RMe{&0`IdU,|dbRpln :Ͽ$
+u0 B&|4?\|7ϲ.,WƙyuR "\[qU5rd{-͵L塽 l[L<IiIi.^h<buq5ʋ% 3Oz쯥X@-e{ob&ey& ᚳ4MFDz=ӝ 6]Dvdvuh&<D?isSʹ0<N34;mW60f2x=hlq$Ҏ+ DbZqSP!PEOuO}5}o`4@nT~C[^u6Z*_rG+ϳGYc,isI8(rv
+TuU8fgր a \ ~n
+Hʍ[XFAG\)$]\o?ly(>6NN%k} )h]ߦ}X2-nc) 7EFlý<7Mq,[Fo/iӋk TI9O.ޢ-6QKo퉶k@̨Y<O}~?ˁFzNtB h>Ti3ru_zqpl *ꊰ.jj.9h>#č6ւa!~ NRX7B?yv۹kO/+/|(R+
+2-P/CHO2fKWa/ ~dqxD7V@*a<YwRΜ|PBEZ<#@H`&eS)] *v,[@n"ə| ݾu, Z|`^W <`5Jf aHlݠ4#DB3zE εo>aƾSi"2,\ <FeXz) ^ڱ-VC^E
+bҢ#%w;]y ;ȤS2٤CɅI;𠒯\)`aIE4e\kxjM.1L޺X/xo&gMSxӽ#(YBMUxƠ*i>4ueWa`i"Wlj}1"߾kPLyMʤ#`R|EYм*FW(o`
+ij5k'cgʻ@>N΁#q) TeRJ,נ':䩯&9\ݼ(&tg]\h.3I`Y=
+7 Z>@m<}0+ĢtR t򗎢 8sLN
+D/qhKپp;H[TtZѤ#Tp>8<*B@S"q~w,~Z%-a <`8k_lkEY
+)c?sQeyΣ8%Fͥiw1 ${Zw
+/ HJ)c3!kb.5^%cۈ ;/>⡝Btİ1鹄(P * K!-}Qh 5kq*B;#-<}/uAdՕ[ӏ^چt}2\[ۖ[~߶hsVCgLD/H Or2U:q2oos
+
+]<R/Z=CB3&4B.{)4B [潿ÄUp?Q<_b4}eIsM{ YRb!"^Cr>e8>={~d 59HuMي1F~wQ_>endstream
+endobj
+1402 0 obj <<
+/Type /Page
+/Contents 1403 0 R
+/Resources 1401 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+/Annots [ 1405 0 R 1406 0 R 1407 0 R 1408 0 R 1410 0 R 1411 0 R ]
+>> endobj
+1405 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [402.6861 261.4465 422.1133 272.3505]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.11) >>
+>> endobj
+1406 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [412.5298 206.931 540.9963 217.8349]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html)>>
+>> endobj
+1407 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 193.3021 244.0529 204.2061]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html)>>
+>> endobj
+1408 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [332.4903 179.6732 520.5432 190.5772]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb)>>
+>> endobj
+1410 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 132.7953 214.8825 143.6992]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://latex-beamer.sourceforge.net/)>>
+>> endobj
+1411 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 119.1664 270.7723 130.0704]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.geocities.com/kijoo2000/beamer.html)>>
+>> endobj
+1404 0 obj <<
+/D [1402 0 R /XYZ 72 793.9346 null]
+>> endobj
+606 0 obj <<
+/D [1402 0 R /XYZ 72 760.4491 null]
+>> endobj
+610 0 obj <<
+/D [1402 0 R /XYZ 72 612.9536 null]
+>> endobj
+614 0 obj <<
+/D [1402 0 R /XYZ 72 526.9458 null]
+>> endobj
+618 0 obj <<
+/D [1402 0 R /XYZ 72 454.5669 null]
+>> endobj
+622 0 obj <<
+/D [1402 0 R /XYZ 72 426.1957 null]
+>> endobj
+626 0 obj <<
+/D [1402 0 R /XYZ 72 306.8395 null]
+>> endobj
+1409 0 obj <<
+/D [1402 0 R /XYZ 72 166.1967 null]
+>> endobj
+1401 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1415 0 obj <<
+/Length 2357
+/Filter /FlateDecode
+>>
+stream
+xڭYmo_6`3(д^v۽۠-
+Zblv%Q'JI 7YM>,@$5ë$\%AU^],j/S.~Px
+Ggl u(xr?hOHc{$$)uSjuaBu%LLFvz'rO쨯%ISXI[t;N5F4КՎOǪ=S<^nS#7 ߌx0})?I¤>Ilܢ&yL-kFSSOkrKK`@o8ws҃L:,Jg2̱Sv24lYJɦ2S Kih TLnPS/6
+&bJWJXAm1͈2܂Bj=Dcܣzhaxd&zvs 6gkahÅAcNhpGѻuGžg% +e/n? OP͍`ǽF(05 Oߖ%wgy|tC0H59s8Ϲ`l"`|)L&Yh
+oͯUD-endstream
+endobj
+1414 0 obj <<
+/Type /Page
+/Contents 1415 0 R
+/Resources 1413 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+/Annots [ 1417 0 R 1418 0 R 1419 0 R 1420 0 R ]
+>> endobj
+1417 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.1441 496.3201 352.1071 507.224]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.math.uakron.edu/~dpstory/pdf_demos.html)>>
+>> endobj
+1418 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [71.0037 445.1388 232.9646 456.0427]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cds.caltech.edu/caltex/2000/)>>
+>> endobj
+1419 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [178.7052 407.5863 326.5389 418.4903]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.miwie.org/presentations/)>>
+>> endobj
+1420 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [257.5919 361.5524 284.4911 372.4563]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.8.13.3) >>
+>> endobj
+1416 0 obj <<
+/D [1414 0 R /XYZ 72 793.9346 null]
+>> endobj
+630 0 obj <<
+/D [1414 0 R /XYZ 72 542.3696 null]
+>> endobj
+634 0 obj <<
+/D [1414 0 R /XYZ 72 347.9783 null]
+>> endobj
+638 0 obj <<
+/D [1414 0 R /XYZ 72 245.9727 null]
+>> endobj
+1413 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1423 0 obj <<
+/Length 3306
+/Filter /FlateDecode
+>>
+stream
+xڵn6_ا6KdALvx֮I<Vm" U,źt]el\JV;
+;9wMnk=?o-j{;L}׏mLvg2"2aδ;wr]5$7hJM%a`4  ݖަMힺj]<V4Yul-
+ӻa\(( 7ڹGG7i'u﹔ pn0sTw`uٵfi>,a寧;uQil7"K=if AϞ;hH*S
+͈
+raoL~~8r}(c;
+㪮!{7ȹ:uTD;w l%rTh6Kh:#X8MP{Xu|f7t4~BHd7C9h[F+ǥf_-2HrQ pYH0 0vdl4G0[ljOn]duI)A96f5$&MRD,B, |*)/G <˕.B<$VuAabb:du[3#0ŭ"՝?'
+M
+'lփ:L}X ;HU? D}u]ԱW}Ţж@x:%(xV Ԅ
+S F&vU m.qxWٳ
+JzL1@ξah^7`NhΠ*O;7,Oe~,g& d\Y&0kKW%sbK|bvgWD0(:60A]O@Q'ż%ad
+`{:`C +=
+ͼ9W:Ie-]fP8K` Ti0Hֻ
+hksC3BeJWLdsV=m!<cX6Yت7B;zo%~ !d%vg2n!Cs)Ck0K ^x9GԖ!ܙvЛb 6LgXEjh]=3Lg 9|4j{$5;` ?iԷz4m %}XzvW"}r C\f]UGCZB*9rd Zmc=:\3=}f!Sp|6ړ2RV}P)+\S3zqWT-::aT~<;cE˜iS9o.O|4W$Sh8C.
+=VܽS] E5G/! f7l5
+endobj
+1422 0 obj <<
+/Type /Page
+/Contents 1423 0 R
+/Resources 1421 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+>> endobj
+1424 0 obj <<
+/D [1422 0 R /XYZ 72 793.9346 null]
+>> endobj
+642 0 obj <<
+/D [1422 0 R /XYZ 72 706.7595 null]
+>> endobj
+646 0 obj <<
+/D [1422 0 R /XYZ 72 624.4818 null]
+>> endobj
+650 0 obj <<
+/D [1422 0 R /XYZ 72 537.8584 null]
+>> endobj
+1421 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1427 0 obj <<
+/Length 2379
+/Filter /FlateDecode
+>>
+stream
+xYo_GYKCpw(Yb+{3wl3NݢQh83 M хb qq.&YlaꗓdQя7 %!Ldt܈Tכ_&.ketF2I͟fR.N+/5]$Y3vStk&c#Bw~NtIHM8쌌R47&iHVaĉŨh
+ R sbI)'Zp4T<![hf@xJ5LD:S.zӚߋi<hnlD50wiҚQQ|(˨(O[yZ?m>Lfc`3b-/_٧@{S&}e <sSE"QѣD9U;'k'ʟh6lU&OsAU׃L Oִߝk2FDJuh&B1[zp|QȂV20q>1/q uh㋇-4QBrDÓ+\q?Sޥ p쪲ѥs4]8(D+ ;T>IK6Ga4`p8IJ$!}-p-w=~Gr[`L&H 1IPvBA,$'=t@F
+p[o /ڼ^! "̲{(MWwnyn?_oEw^]ioH
+"gl|,><|DK§_(s"Q1̉δ j4(L_w6h PKjF
+=ѽ
+ٕo\ 4JbaǵBPԩ4u6ʳ"Bj
+ X۬wvABb6^Is
+=xˋ9X1‹@<گ!ÁUr< ݓk9>wrg/:þ_b_>=v|ѣۼu PlEG諳]?&[2oWs2i33gӇꖷHw`Ҿk¢!óPnovSsB;J̕f,M;YQ(Rci&!=me+<֫JN)jiJBֽYg G4\=&A=𻮵ݼ+aJXr$P;Sx9{?U;R}-E9L6WHŕSbgw KWxgO5%K8Ӄ5Vy{\&<]#S*
+ 2YPP?Pz!2" 
+o^ U<dA<d`PYx3
+iv4>W{6J&zh/FJendstream
+endobj
+1426 0 obj <<
+/Type /Page
+/Contents 1427 0 R
+/Resources 1425 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+>> endobj
+1428 0 obj <<
+/D [1426 0 R /XYZ 72 793.9346 null]
+>> endobj
+1425 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1431 0 obj <<
+/Length 2730
+/Filter /FlateDecode
+>>
+stream
+xڵZ[ݶ~_q)
+"EE
+l'"ەݝ`̿)/x* QH &$`Bd2Lꋟ.5s9.\Ej9x,v׷+9w{I.)$7!I:![p$v\I}RPx #NIe Kax},D
+nMd&P$+ <cDLfua\ɴKݎbU1Jȁyiݧwl޿+k-ҧ^?r<N46 nF
+K7H}H<VڞEVY$X״ɾ5]
+U_2QZW8QNe2cnPd7N'c*>}piT`mŒ7$,|`
+UpsW/vl^v}xQ"rgb=eeȿ4i$Qh6MzJڋigmkε)ڠC$# g>fD)_2$ybUKTs.#j̨q<!jtRލ Db܁9{pT*a§kD` U3yb&{qؒ:|AF=m˜W{˙,_>?܆'$`{抔RI:ٚzal}֟Q*KWlח92q,ݟ']i]ݕ wa\Mx.F1"XQu=RfT(TYƍ.$'Ԕ nhJco,UrZ'9
+4ӢSTX1ܧ97ئ߀`lYN(N@eIi"aAs-쎣jci1OS͹R-}:Y3CN/(EAo?s4T ef% 8Pz\=
+ F<J]0U)/ O`rtvמ+Fnvsߕ`"_y;%u2fc(x*'6y\e`G$O10z</4X $T$EЌST2ʿi2Vo}:A-`KS-tDMhJ)ftQ~xVyNA|\pf!EC1IN,?>򄪮-o[\+{=vW#IxJR6W'nKG
+pʲӒ*
+f(z*-Vtr~S
+a\V9PwBMbH AK-7CP:S8$]t ړ"$5}`Q7纛=$ 048s tp*ƬP3s]?? .1!1vQ)C8=ɉB>K'7̥zK]wІѶWXLtvnx̬2`~{1p)f-'+R,i?i 2,Іhi2wB:e}+c/M0>n}++ +KFF"D
+-g%UܭA4A6RA3⧡#`$#3))$PzexZ*YIX g["mptdDn;0ÀFs}/ǾB
+{Z\UoOvvq@IƮR~: 0qq-]hIi,{} z/AI\ GRmtnxQE)J"0 :Csp ^,_'^Imܿ^jfRlrG%hiC~
+:kun/sW4 ^jX I~^
+.%]+4 *( ros?yMw9cySLMWw1B799]ܤ{$͎ZOs;R0
+k j@3Kw1/yu$2{}OYrp.m$XF9@<sj
+endobj
+1430 0 obj <<
+/Type /Page
+/Contents 1431 0 R
+/Resources 1429 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+>> endobj
+1432 0 obj <<
+/D [1430 0 R /XYZ 72 793.9346 null]
+>> endobj
+1429 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1435 0 obj <<
+/Length 2851
+/Filter /FlateDecode
+>>
+stream
+xڭZobQ |/5uqVQkVZ˾(DrDP6)ߤ ɦ<~2`1S ?g3JdGPe63daМ;1Svi\
+w7Bm`&~M6';E9n8qEOB1vYv~@
+`O9L*I_NJA(› Rf|%A}x[2&H&JHDDo2`fy2q)7 p˄bA^7AEulDzQO}sBŗTCV8]f*OlF϶%N7@ȇn~CU}᪃_nS}q۽SՕA(X0VH~{ʸ!kS; @VK,$`}p͆nNꍑ^H;Uzԍw[̲l*f9?~?`.<}u* BY_EZ8rh$
+`VҌyi
+39=+
+ZTʎ*Rz,#Ba;F}eݵnjuUnd&@ҜprXA
+0Ճx?z=*؂X݉![ ׄ#N?er&X.2" h 7
+je` 9$Ŗ`,!^g)u8;cӹ>۪DәLF6^4dT7!cG0D{& <c^cIB&oF*Շ45!T14nDϸj-Atx;C׃ߋ5rg Cre"m<2,seV.ywc#1:9M'X>'Iџ^PLQ'+pNH\EO4
+k'rIxטECBMٱ1b\W!Gp)5DTF*y6 Ǵ%E6 ߷(Je^;(}ú%I7E!\W ):~F3):c[-&
+&g"OvPZ&,ud"S\Gۭ=!.i=~Xx"X)e6@4$ Qެq@9e(,3Nin }9uHX[k8(WQƌ%";`
+vz7U_YBJB.8?+CHsnx:dA
+^kWؔ9;`8G4#K_2LLm34{I`2<gbN'6@1T4ńl,05cݎay*&Z<N$4r[wm!,9eiy}
+!,ܴsd0 7I$PiO$࿷X $ ,ۨPȬd,6 |. _^$ƃn먚-PȦ3L!92ny
+[^ lyJLn2R#I"dbbNJ ^*?u)gd}@qOkIHZRq * Hao =!rA-{۳tm{ ߽qg3ȼ[dXlI:v5)<X~-b}f OsH)'@$xm
+Y
++S~/7YR/FLN ٛOr'x>ؤP~k-&uB n,rp~+⦰'ҕusӮB
+G*\VH(y"Box}s@-=E FM8^n]$
+
+endobj
+1434 0 obj <<
+/Type /Page
+/Contents 1435 0 R
+/Resources 1433 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1412 0 R
+>> endobj
+1436 0 obj <<
+/D [1434 0 R /XYZ 72 793.9346 null]
+>> endobj
+654 0 obj <<
+/D [1434 0 R /XYZ 72 350.9002 null]
+>> endobj
+658 0 obj <<
+/D [1434 0 R /XYZ 72 249.2084 null]
+>> endobj
+662 0 obj <<
+/D [1434 0 R /XYZ 72 210.4938 null]
+>> endobj
+1433 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R /F14 832 0 R /F83 1096 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1439 0 obj <<
+/Length 3830
+/Filter /FlateDecode
+>>
+stream
+xڽZY~_! F>xX;vÈI`РHfǿ>u5ER80 =]]쮮hvN.6Fo#z$4͏?*H/4Aj6Ǜ J|yw8fI q/o 7@lqqk݅Zo߶&CgΆzPK'Foz=dVO490Qd)ynIa7BV4޻d5@ȥgvGd7RqQ@HEf*ڒGkӚTqiPqj-Jm%ѶjdL06lR`bw*2>r:Wx俲qYB
+FHU~yL[΍hbN zC)cܱ[@3 +""{FC
+&9%O7&Nȑg}J:=><`OMNLj
+ v8B!x
+1NgUȇ1E' v>.⽚|3==n^wd>w<O*+u)+|3f/blJ"U} WW}QơJfb:>Cn_(DrZH0p\,txl d h|(|;+b] Yt
+{պEbcr Uv:3~ 9ņФvc탰cïRcDou<:˖]X+}sapbwcPcI DžVoy=dhX [q ƀe+!p懯к&v:NM-|c YZiZcH䏨~^q0p1e39b0Y>UT4^: -U'uYlD %{3[^m/nN !
+?^
+-U…)}:
+::1:a3uF]D}CAv>oHf{Zra 4ib椸XhjXżJ7|Z$Hʃ@^@0
+h/h0m_=^xkSYxu ]y<Ur'`q 灇i BJ
+endobj
+1438 0 obj <<
+/Type /Page
+/Contents 1439 0 R
+/Resources 1437 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1441 0 R 1442 0 R 1443 0 R 1444 0 R 1445 0 R 1446 0 R ]
+>> endobj
+1441 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [103.1676 746.9995 117.6134 758.9547]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.9) >>
+>> endobj
+1442 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [222.5228 746.9995 236.9687 758.9547]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.3) >>
+>> endobj
+1443 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [373.634 746.9995 388.0799 758.9547]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.8.5) >>
+>> endobj
+1444 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [274.2046 672.5855 288.6505 683.4894]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.6.2) >>
+>> endobj
+1445 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [419.2107 437.6253 446.1098 448.5292]
+/Subtype /Link
+/A << /S /GoTo /D (subsubsection.6.12.2) >>
+>> endobj
+1446 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [187.7546 259.9717 207.1817 270.9604]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.4.12) >>
+>> endobj
+1440 0 obj <<
+/D [1438 0 R /XYZ 72 793.9346 null]
+>> endobj
+666 0 obj <<
+/D [1438 0 R /XYZ 72 722.1877 null]
+>> endobj
+670 0 obj <<
+/D [1438 0 R /XYZ 72 512.428 null]
+>> endobj
+674 0 obj <<
+/D [1438 0 R /XYZ 72 410.796 null]
+>> endobj
+678 0 obj <<
+/D [1438 0 R /XYZ 72 158.441 null]
+>> endobj
+682 0 obj <<
+/D [1438 0 R /XYZ 72 121.7836 null]
+>> endobj
+1437 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F14 832 0 R /F39 819 0 R /F41 842 0 R /F85 1123 0 R /F83 1096 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1450 0 obj <<
+/Length 2607
+/Filter /FlateDecode
+>>
+stream
+xڭY6/gkF|JJqn6nt\u~eWI~C)ˎ:a8ofh:b6SNR.,+ϢΨfKL$k4giBg`&R:+τJ 8{{e ,$%H\΀]qeN)Y,e͟Ww &uS,W%Ѽ͂&sëů/OEҘ''(4IfD2eŰn7'RDl9Zvm.`nb&$iFx2v(tUx?Jy
+Į9[]q蕥]@#JRԙ%(ߪn8ؘ6k*<>b$Lġ+GA%ʟ
+|7KR]~~yd3;æ Sp!e`}TG߼?o)3rAR;q]?Z>\7|ۼp۝/ ߽yuq]e常|9WA &$uїƯ$/צk%;5mMQ\*)못l9
+8Ks) fOuVWYP9yӚ/;B'hslԛqx\7|FwGlѮ_?1 X "DQjB&9Md $3P@i:nYr|yDQBTc)qf#?L 1gR ;0$
+:
+?. zQ& }qr[z6
+rF[6M'6e,7J;`RW7*SЌrX~h.JHx%s5d b֙#"|AGKJ4\359 ~tH(<dY1V>wF_s7k2% $] kvZA 4MCs`VPxoHk0Ǫ;WD`9 ːK2:I'F"| 9
+'`Kg M#LMs<)b|RlL( )}vPK :MaL@
+9^BAeiu O, (ma3>
+wj2ԼGe)޵{ڑ;G|9?U|]f
+`01g+L{6g+%6l 5T0CME<fͲ)PJ( я)iWhuC}/Rk%Kh>pW„QEg
+F8y~#8HOS8gNnl=jIAQjH Gϑ:D
+$R̗m f0~Bu9=,LC#I%$PvZӄӱ n£"~ +[XMb{ұ6.p„:-7ol
+cpj{@w dG+zk(HJoLC;p-0@p[yi{vTvm@(Pڢ-NzYv Pv] @B6,Q&Kج#}l߿E@àNA>ȶeh <z8ږ,Fܹ(2U>PH)5z!SPyGbظBe}}
+lI7.[
+endobj
+1449 0 obj <<
+/Type /Page
+/Contents 1450 0 R
+/Resources 1448 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1452 0 R ]
+>> endobj
+1452 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 556.5679 275.4369 565.6751]
+/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.dit.upm.es/pub/pepe/ftc)>>
+>> endobj
+1451 0 obj <<
+/D [1449 0 R /XYZ 72 793.9346 null]
+>> endobj
+686 0 obj <<
+/D [1449 0 R /XYZ 72 542.9939 null]
+>> endobj
+690 0 obj <<
+/D [1449 0 R /XYZ 72 360.6523 null]
+>> endobj
+694 0 obj <<
+/D [1449 0 R /XYZ 72 323.6004 null]
+>> endobj
+698 0 obj <<
+/D [1449 0 R /XYZ 72 296.3791 null]
+>> endobj
+702 0 obj <<
+/D [1449 0 R /XYZ 72 146.0625 null]
+>> endobj
+1448 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F14 832 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1455 0 obj <<
+/Length 2362
+/Filter /FlateDecode
+>>
+stream
+xڽY]s6}4I /jɸ6@QÌD*${@$Ѳf288A4HY*NIϢ>n9
+B,ʘOgK>P_& g"l~AK]T*n
+Ecγ Z:\ڎ_f$p&d Itmt޽^}Tvx :H2&dwit|˶ǗHA2B$C,,8anٓq;Ya1Շݼ<?4'$")'&:('Q' 'l$"u^YwGT6o\؛΁6Xei9,o b-u8F@ J"9!N؋}KA66GMS8g\'EnAH~uMմDjCKr;8}3 eFcۋMVұl^+GIDËc:f!Cg˺Xd(͆ 8fDc=/ śF]nV2aUH@#=[
+u谗6@v^
+
+(,V{͒)u;gaf
+x49)2T̽o{JoaXb;%/w.ѕO9u2oM_Tn#^UСM:c\o^V{2 F. 6rY5ECtsnN~_lE>T "R\7O9ROX \,$/"ced`_|ϸb5jgoK;&
+ ރӿ.}r8uc!k~[oqOZSj0bH7,s=d *?No_ٲHa7u3t!3jFASIOIqq o\.ytSnbc߄va 2|
+e<M}~g}jqӴ?(G.QP|0~,Sa ԥD>ltE1g=x PiwM_ {14CAӌ8ao`$X.
+(<a;atྃ
+51Ѯk(KH*'[*_牖j?3
+endobj
+1454 0 obj <<
+/Type /Page
+/Contents 1455 0 R
+/Resources 1453 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1457 0 R 1458 0 R 1459 0 R 1460 0 R 1461 0 R ]
+>> endobj
+1457 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 669.0134 213.9968 679.9173]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cervantex.org)>>
+>> endobj
+1458 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 615.6797 278.7731 626.5836]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cervantex.org/actividades.php)>>
+>> endobj
+1459 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 235.9558 295.4691 246.8598]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.rediris.es/list/list-moral.html)>>
+>> endobj
+1460 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 192.8373 379.4341 203.7412]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.sindominio.net/ayuda/preguntas-inteligentes.html)>>
+>> endobj
+1461 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [132.7721 179.2084 337.3821 190.1124]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.catb.org/~esr/faqs/smart-questions.html)>>
+>> endobj
+1456 0 obj <<
+/D [1454 0 R /XYZ 72 793.9346 null]
+>> endobj
+706 0 obj <<
+/D [1454 0 R /XYZ 72 513.2223 null]
+>> endobj
+710 0 obj <<
+/D [1454 0 R /XYZ 72 486.5915 null]
+>> endobj
+1453 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F83 1096 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1464 0 obj <<
+/Length 2800
+/Filter /FlateDecode
+>>
+stream
+xڭYmoܸ_wYE
+m4n|hIuJ$pH+'9`K#r8όĊßXhSR'lW0 j F \|/|ũYblᔭ6)KTNT+Idu06y-laumVD֛mkۍ0_o~홰TK{
+.X,YE4rgKbnV -bzB&[عddQx2EUٺyqĒT |Usݎv>-l$!)ȁ'J+P\veQ hPdFm/꾠FmY`Fva(&@DG㊿y ?^]^@,/hCAFPYZJ<-}iOf3[ʚo˭S6%RV 2c~01 W xlowt1%xb<Ȯw?]ob~s3 ؜ ׭^`NU?2yX')`g_v>-\(RD+H%C
+*l\h|\.Ja(݇+{v㞞NⱬZ1*E\i=DE|;>T(?&Qky 7bEw*gDa=H 9'f4R}-*#v<}?mEBY?VbG㙟Hp~}By]p%q\N=v yJτ}цRxQrx
+~ S }^&bqW("k@Wwc wl/k$L`:aT% (cRS` aa#8`R o/m=Kf:.k 7.-۹)4bQ P$ ߖb&!& [@[ pDU(>@C~uD)?P:Ԓ_tWzAHh0C%LǷhoG;ۻ=XPT :C.mJ$fR#2H)T萴쭨Ef?Q8^%=z.TW-.do45~LH@8%۸.էRl o ;*+f٠fijP7s4=)gN(Te_6K"t9}ڰ񒧨g=eHA,bzhMJb
+ Óo AtI
+N4֡9-qV2+[*&@Mfznp)g\Kcnp̷bū2p
+BPFM#_+a[!Oxˈ
+3
+^ /C_W"QK^t鸪#T6'zuHEv9`6)
+;ZA1ke
+endobj
+1463 0 obj <<
+/Type /Page
+/Contents 1464 0 R
+/Resources 1462 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1466 0 R 1467 0 R 1468 0 R 1469 0 R ]
+>> endobj
+1466 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 638.2624 272.7143 649.1663]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.rediris.es/list/utilizacion.es.html)>>
+>> endobj
+1467 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [247.2511 620.6485 404.4093 631.5524]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.rediris.es/list/doc/user.html)>>
+>> endobj
+1468 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [281.3929 603.0345 496.0847 613.9385]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.rediris.es/list/comandos/info-refcard.html)>>
+>> endobj
+1469 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [96.1891 454.0968 271.5984 465.0007]
+/Subtype/Link/A<</Type/Action/S/URI/URI( http://listserv.rediris.es/archives/es-tex.html)>>
+>> endobj
+1465 0 obj <<
+/D [1463 0 R /XYZ 72 793.9346 null]
+>> endobj
+714 0 obj <<
+/D [1463 0 R /XYZ 72 571.8465 null]
+>> endobj
+718 0 obj <<
+/D [1463 0 R /XYZ 72 499.3702 null]
+>> endobj
+722 0 obj <<
+/D [1463 0 R /XYZ 72 440.5227 null]
+>> endobj
+726 0 obj <<
+/D [1463 0 R /XYZ 72 192.3123 null]
+>> endobj
+1462 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F41 842 0 R /F39 819 0 R /F83 1096 0 R /F11 800 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1472 0 obj <<
+/Length 2491
+/Filter /FlateDecode
+>>
+stream
+xYo6b?4$K9IО}uQVV$_3|h%V| o^4Pco%Qɪ+9WO&Sp_\Qm>C)8 qrHRET$Bn`$Ì-dwnߙ^N펥[s^wt{O%]7躦k)}gXʾvx`"*<# C2/J)E(cDIM%/#wSFܕQpJTL1E{<拿쬔Tq剟Vƍd,Ig4
+x
+ WJlb""i%}R-ܿ`5mk^o~~O
+._JJriwAH6PS? 5&!x
+s'OV`!K34Y^[)P)8B"LZD BSOYr~)?~*+SCIxF? r. Gg zZCgV;
+: ȴ4ޅ׻$s$:K<ЏG[2=njtPJJ<QZkAHfZpE; &h4tn,yeC7IC/+*,9`VҌX҄$E?5`mهJ(B4,eCR3EhahOH|iݵ@iKe ӪN~,6,T!n":ʧ@ٻtA>k;٥a KIx\-,&iQ(RZ!fvk`6^C Q1XLAF7*??B\
+]/
+endobj
+1471 0 obj <<
+/Type /Page
+/Contents 1472 0 R
+/Resources 1470 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1474 0 R 1475 0 R 1476 0 R 1477 0 R ]
+>> endobj
+1474 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[1 0 0]
+/Rect [499.1453 721.8324 518.5725 734.8435]
+/Subtype /Link
+/A << /S /GoTo /D (subsection.11.2) >>
+>> endobj
+1475 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 622.6097 299.7731 633.5136]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://majordomo.eunet.es/listserv/spanish-tex/)>>
+>> endobj
+1476 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [96.1891 537.0159 238.055 547.9198]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www2.cica.es/ListasD/sptex/)>>
+>> endobj
+1477 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [325.1977 475.897 414.751 486.8009]
+/Subtype/Link/A<</Type/Action/S/URI/URI(file:es.comp.lenguajes.tex)>>
+>> endobj
+1473 0 obj <<
+/D [1471 0 R /XYZ 72 793.9346 null]
+>> endobj
+730 0 obj <<
+/D [1471 0 R /XYZ 72 760.4491 null]
+>> endobj
+734 0 obj <<
+/D [1471 0 R /XYZ 72 695.0031 null]
+>> endobj
+738 0 obj <<
+/D [1471 0 R /XYZ 72 582.2893 null]
+>> endobj
+742 0 obj <<
+/D [1471 0 R /XYZ 72 523.4419 null]
+>> endobj
+746 0 obj <<
+/D [1471 0 R /XYZ 72 448.6093 null]
+>> endobj
+750 0 obj <<
+/D [1471 0 R /XYZ 72 372.8254 null]
+>> endobj
+754 0 obj <<
+/D [1471 0 R /XYZ 72 336.1681 null]
+>> endobj
+1470 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F83 1096 0 R /F41 842 0 R /F39 819 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1480 0 obj <<
+/Length 3677
+/Filter /FlateDecode
+>>
+stream
+x]o6ݿbw+J"EmrI4n)
+YJFq_3R+ie;89Q3|8 YFr.?]p<XTW9 Y(ς(E$/ x/V KDN?\]l_b̈́5~;6zW]n@돾m}M@Kir&w*G4DB1?CIĹxq5!"Qiy1Dq*@|JFS Pɋ2f]]u,pT8 y1_[=>hk5<#HVbFWY
+ N)9GZeAE3lV7I 7uc!ڪ
+T F_,IMLH1#Yٷ
+$22(~P[2͊ufU h5G?Zt8 MyBOQ[4 J:
+SSp&Rhq
+UDY!K2J|oecF%n#ݸ=fk ﺨJ~s$5:JΨ%-
+WSZ1"uڦ.OE'ъ =)F] =X: З]tgU)R
+?烸xz'}ƊYx
+8$>&Ƥ;QB.E4n->7Rw |qgڥ8`Q1*L6tbZYq5\%e藟%|u#xr}f D9Ζsqa]Ň2 /tހ6c](Ҳ3z==ejyhq{^L?*ozR#F?tDz)k
+mo vkfI5 O{@v>tatt;EBc%ţf#CzB> Oִ ˕#Otb,u:uuC\@>HQVE)[z;
+
+NJGnx9T&˃Mc9 X>`i/E/2}Z_(/,ޱC@N7{b)&5hG/3 8sP
+tBr֛V|
+endobj
+1479 0 obj <<
+/Type /Page
+/Contents 1480 0 R
+/Resources 1478 0 R
+/MediaBox [0 0 595.2756 841.8898]
+/Parent 1447 0 R
+/Annots [ 1482 0 R 1483 0 R 1484 0 R 1485 0 R 1486 0 R 1487 0 R 1488 0 R 1489 0 R ]
+>> endobj
+1482 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [334.1914 588.3178 500.8945 599.2217]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tex.ac.uk/cgi-bin/texfaq2html)>>
+>> endobj
+1483 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [385.0521 474.0546 535.1275 485.0433]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.esi.us.es/~gonfer/tex.html)>>
+>> endobj
+1484 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [258.8079 460.5105 419.6529 471.4144]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://mate.dm.uba.ar/~mpavon/tex.html)>>
+>> endobj
+1485 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 377.5241 338.548 388.4281]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX/)>>
+>> endobj
+1486 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [110.8543 331.997 379.7828 342.901]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX-main.html)>>
+>> endobj
+1487 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 180.8662 262.6135 191.7702]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tex.ac.uk/cgi-bin/texfaq2html)>>
+>> endobj
+1488 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [441.4704 153.6085 540.9963 164.5124]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf)>>
+>> endobj
+1489 0 obj <<
+/Type /Annot
+/Border[0 0 0]/H/I/C[0 1 1]
+/Rect [95.9104 139.9796 251.834 150.8835]
+/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf)>>
+>> endobj
+1481 0 obj <<
+/D [1479 0 R /XYZ 72 793.9346 null]
+>> endobj
+758 0 obj <<
+/D [1479 0 R /XYZ 72 760.4491 null]
+>> endobj
+762 0 obj <<
+/D [1479 0 R /XYZ 72 663.1205 null]
+>> endobj
+766 0 obj <<
+/D [1479 0 R /XYZ 72 447.8326 null]
+>> endobj
+770 0 obj <<
+/D [1479 0 R /XYZ 72 319.3191 null]
+>> endobj
+1478 0 obj <<
+/Font << /F35 790 0 R /F31 784 0 R /F39 819 0 R /F41 842 0 R >>
+/ProcSet [ /PDF /Text ]
+>> endobj
+1490 0 obj <<
+/Type /Encoding
+/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozenge/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]
+>> endobj
+1122 0 obj <<
+/Length1 1642
+/Length2 9970
+/Length3 532
+/Length 10844
+/Filter /FlateDecode
+>>
+stream
+xwePݲn$@ Np ݃;wwA]}w}j{ݺSNk=Ow߮ZtT*l&Pc4ƞ
+vvO
+ i(H">)0gPR ,cvwhg|*]7US{[}mV 2wL%F>-yB\'Vuy5U r7r__1y8fz^0<@qMXUpʲw.{{[OQ7IYRQ_M%(r #׷c=Q1۱CCL MAB<GR|ע#k
+zv RԤ:6N|#h#`7j4M&mCЌ'{*R/!>Z d%Y};ʕP%abl@Vb<_[m1M"MojG'QN~zR+n;$)fZIi[BLz_l(.K5] ޾"&4f
+5I6䌘K}&]sT8磥}[ؽ^-i$|Ǧޫ+oDT=d 9)}s{^T~ɤ1CׄwO{P2Y}]5z#w"zoDn0Gx
+9UJj5G{Y]UD D .Ȏc~#QF 7`s1(~ZD
+'A z{AcX :8i*0i愔F=Y61I
+OF2UXSry9)|dZאw|
+3X~ku
+u׃_w䈽{)}"<D?_lT4;i2{#=!L̺PNȥ@(~1z <j4t,'FT7NTҽۑ\~!l"<:71ix}@a$6FBKc,h&ُ㺥@]׃)Œ;hڭd:!ȷӂm K*-=4v_\ tze]Uyƪ0_?v-jg /ſ}EID
+kJ3>Uu鬺\͒=TY5,H(%&\"2kpʣف1,N୫) (6F$JD:S}gI8u_]%gG\boH[0<4ʰrKk.'#|7<%]sҌ<? x)?YIByۧ=Hrhgl}H߸HQeٯan `xYQd}\1fw;S!bY|×9[a YRPʪ#=% O $ r#!k9j٘nHL>gj)B&I_0SI>ikNײE;[UJ9q;%O|7amDz/R.s;r@mzdhM fGMW"'3ɜ[vTO.F(VcLN%TTGU}][?4o:l>o#I z %%\e!ć } D7S|^I:}t
+Uh~'s޳FΠQԪSiq|)j0g/R7$F:f|
+ 3QU`CL*~e|Jro*g@8!D"'X\]TW-ٕܰra>mwXeMs2S_{֐$\3N=O ed
+O>DyR~4,OZO&r2\&Y<vP{şA}ثkB4|L_wl?!tιAС.2IyQҖ[)av8={^WKL<?ɡ筶YɩqVo9z@
+KB\Coz1H;U_;D^iq?qOc$HCa<7{Էٖ4 'rF
+GD!*VȝMk z}m-.6x߈/;GwB|P=އOĶoZLGD  ?<ye$O
+t^R]^gX JHVT%J4ҷ+ϿW(*LLf(RöuBWO#B/T%3Pt
+g |MI<Y< /|)sBɦaȟkY^" 2}rAga3º{P"MCܮI.}ZJ܂CA{RՀ}9uDZrO{,wgxRV;&)(w0|{p OIqfht<睇!~j_duc-qm^NNꔐ_Hg5GaE,d UEUs/cÅV g ˔ ψspҁ[DtCVbd^3#Ӱi.墍Lޫס_5qAfOh'm#^EOtqdIvj#hjn`'}at>W,hUq"q5R#=Qc0S A{7glӨdC bTTz
+JuJoJ5Z[c5e`mf=n܊cʭȊK/'#C)kӽ?n_SP߂e"HcaߨbtԥhUO&M!c\
+rkTy1v1?|ҵo55WPy{j"az%DPs9Eei V2vohjY>٫K7~fa( nA+fiZJ#CMa
+J
+ZuhJ)eVя1Hz^Ⱥ|nt
+ x TࣼQxJV:vI=R}@hj̾ʗx ȵŝӚ_Nz#ȧlX|0uʠKQ b}\|Ƴ4DCM F!鿻*(~8)K`<Y`~<qpl}̷|
+0JmI"#ߘ"^}.|cAv6|E!I$G0\P%DZ5ն?rt
+3j``;7dzجBo ;>R%Y,m+f'.v1=ej^n
+KE$D!
+/tc} +0].1.ϣ3 a5hoL1R.kӋr-MhAfKfGHg1P~@Y~Fm44f]D>]iP%#c֕[浣K6Ų![6+W^%#j鲫-5
+FKlD_[퐮Nwv|wg2f Co"~fd'/&|ŷj'H$"`+cOZh}BB?-{@s:~Z~53?VEt#–0LI)# x>xDQ
+wGN7 /%Le+~MTD!]G'/vҤi[
+LЮ&fu&K*ޮ#QHL,DPr?zې}\ӡ)'usE`k[{_k+VkIE9{DRJ@B#r0B'Byl2CF,.wĂ_mSZg8wH? *Z%f蠽A>iC+2Tz\ծٲ4tޑ
+mLK[6Km6| cC4ON4 0} a= ݗY4~>Ry+y~™=:LLV)n@Q K rEYmxqiÓ,&FuF>mٳqr%L$JYhQma׽M;0D0^Y3;{5m8y.z,SX;*5SYSpo;ޙǏ,urvSֵ4Y99)rVP|DNZ5W92l=l!z!$8sŢԮSؒ
+2dH9ΧK@L*[%UK^U~@+m_PGnt6M`'&D9xL '4uar7ś!bޭ4%u(ZR]+ "׹*Gnat(|"{nuqΓȷ'xڷ+Δ[R{V'ngƮD,1? gTjdX(rPk`(5nm6a\#̱zIk3\L[uEDwV\xt=tOɠ:my1Yqn;q' IF:GJ(1giFH20<}iŶs);[ 4}ΆL!}~ %Z6\4tC ^khH
+J,'AۭrCʿC{>|:򲿮n׬Q(ƸeF[j۽ϴ?Sj׹qKhKY~쭣:갾Bys4 $
+\]~²,iAI* t@a-+ٖtHm
+L$Ne4E31C쮧b@R&#;Q%wi-H[g`D>,=P'XW;<wc
+P6z2>rD9ӆD9r _Qо|U:H:UcG#U$#$a`I`t%l KQ v*~1l)#6zS-fRIxhHVK*Yؽ 7n$(J1݁El<[tiWbr8شQE
+'|=@ķ>Q/slȺ9`l/zV-y{{myy"?*ƫijlnK}_Դݺwc6yN"'A`<uJ'{_1J|G2 v cʘJYFvܟ~#JǦ<Z<kU~в E|~Y,qt-i!LVSV /0 Bs+ Q#5+k %q߂y&xK-( <̥zǫ d*smڒQ1ϐ)}|tJtXe`GY7",W-~;3uN\ޠpUn r{gt٘nΛ\{^&Տx+f[4Oo{>rcKAЉVe.g ɶ&|I9GZ|%6zQ/Ajأ {=; vjJFg
+q^e\}ga) 8};]$@2kIOiR: 6
+OguH>񈏦%S7tQ8HQu!N'R5Tӣ8$<YY~%٫A؄j"oJnYeׄm$:5Qt D#_^:Ƣ5 Qw'8Ŕsx*5Z"*6L9Qpz0\9asYjV9={մ~G;_Nhb}
+XpŨGMH՚բh+F5Bpܛò*Hbx8^.S(} 3St?\G F HιXigTf-ZΆ:dϴH|7a? +0n-3 endstream
+endobj
+1123 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 45
+/LastChar 122
+/Widths 1491 0 R
+/BaseFont /XGIASM+NimbusRomNo9L-MediItal
+/FontDescriptor 1121 0 R
+>> endobj
+1121 0 obj <<
+/Ascent 688
+/CapHeight 688
+/Descent -209
+/FontName /XGIASM+NimbusRomNo9L-MediItal
+/ItalicAngle -15.3
+/StemV 120
+/XHeight 462
+/FontBBox [-200 -324 996 964]
+/Flags 4
+/CharSet (/hyphen/semicolon/A/B/C/E/N/T/X/a/b/c/d/e/f/g/h/i/k/l/m/n/o/p/r/s/t/u/v/w/x/y/z)
+/FontFile 1122 0 R
+>> endobj
+1491 0 obj
+[333 0 0 0 0 0 0 0 0 0 0 0 0 0 333 0 0 0 0 0 667 667 667 0 667 0 0 0 0 0 0 0 0 722 0 0 0 0 0 611 0 0 0 667 0 0 0 0 0 0 0 0 500 500 444 500 444 333 500 556 278 0 500 278 778 556 500 500 0 389 389 278 556 444 667 500 444 389 ]
+endobj
+1095 0 obj <<
+/Length1 1606
+/Length2 9470
+/Length3 532
+/Length 10311
+/Filter /FlateDecode
+>>
+stream
+xtePݖ.!@p 84Xp ݂4; =%7gԹku%YZڛDYAd
+9Xy.
+ yQ9OA! 4[M@^ 4Xxxx)
+@-:
+d2,AJ?Ҋ:_d9jXC8Ɵ-,k,f;jzme-U@t>]v,eS6FW81;,#fˮk,Ε00wS}%B5A
+߁+)<ǰӍ] ďY_L(a -jL!U<+G`^,u~tA_Ǖ<GQljY&?K+)w6s w}F21T8F"~QN9ʙ B`o~~@ϫ韌7tfvQ-lJa(.H ˽t"]iG"v~x9se׸û
+‡Lr8|ۛMH`{G3p)uW
+7cI "k~J@"M|Wp8ՐvrF1:"F
+_@j8kQ̛wV hEM'CqOMy0, %7L;B~Ad. nPBlQ$tK^,n4U~N6CRK]ԛyÅAGj~4qVc[2#! s³g#OSfqh8.SteHK.H-wo积%c\|[e?άV ;ᐽ=JYl̷]Cvh|y"9;ߏ?Ĉ>3v1^uz͙Ku,s˿ڀfSbR/'2k * ~le\IqۜQ3E9#K yHRxu$f'7"G<.};b; 85Ń;KBBfPUӦ?-}$к5Λ
+zc촋uﺩz S ]?NaSqVTwFذdrmyt[DA g4_lwRlʳXJqwzgݍ}Lkmg8%aP0$|1qp5D^nY Ȧ@W]q/ Y­k7Պ>gT[}z6bb\٠W>VL( Y6IX!YdWn+^)<DT<e$jP^My>N )kjO{[
+G\;_T%|q EEuc+ST.8Qc9o#`!PqMJ :a֏٢"5~h_oUm~AH:V8Ϊ^~ly}-Gc_Gm'K1O43| TpK_1܌`qudAî( \9nYr?(R -<e1~boa˗ Lu e0+ toE0rЬz%o> Δe y`ֲnC{2e&| JZII%a baHE_12YH6}D5&J pdY:O_3L WQRsb9ֆbð6>8.~ 2##]}1 a;ڮȺ's3mFw).k(+(>cmw=W-袞!Z_CJ6Y@mh=ɺ~f/r=H7K<ZI#9Xrxp}w~Ao2D&o&C?30zlfN5CpЙQ2Ku[J:!ҹs
+-kg~8- ZfYU<4Z
+u
+yxub7!4!ak
+VmQ[ ri
+q3#/'W,v_tgyv^3W#F$]T$?\,qi N%c/ ?=:dϞŚ}?JN-GX3?~<>6v;h)sU%ѦPrҐARF5?ыxש\:F0/LrCbn
+`.Nۗ-mA՘Եl~]u5mAH.H{K%~)T|ʂ=?h7rfg&YvQ<츳銸gqbPMiJ&D'm%[I8NCz=5 K$OK< H@܄jf-ՕۇQ{f ad lrf?賊i. 2bJS~#A!&YY -CCArӝ 8 ^LylWӳ1>45_xo{k\gy:^ kn1yO3hLy`B\4kXZpwܜ@ফ.j<:[c 'Î|ǝq !Dž318=y<}s$!J =E EzqbVYq%CtK5$A~
+Tal#ª—'Kܷ1@/s2Ct~k#/?6;~+ z8.
+k
+@ _,S?:",E)͆J+>v70Q;RY%fuŦ=/fӭ!Y
+.&Rh%)pdso˶}Ea#tI齱B41i6B l7K\Q@iΠUs9v.[ yBkf/\ڊΦ
+ɵ@j-@Q9@y.U:-iLSӛ pXB)2S?u ע~etn݊V"R5HU
+uf|CrU,rEwi.5C~q|R(vdL.wuRIUia9pt,.!dCC8?~U4Gn׷(ϣ }d9
+Rr4cSCQzQ=?E*
+ҥIXf^
+J8ŒK˞+
+āŷUCsmkg$A}3VP69*vr FytW'(l˪ytT
+hnﯿg f
+8=2TGّ,juܱGb񬗝G)J~ðrIj~ @,=kN'JRIs gk?ﶮ"4칞VP[rrRz7II]<'9"zncLJ[b ~0}t<FGF։gz9d$"naWc[<cOQA]zM󇱥l3X" L@EZ7q) #lj䣽$qs-w]E Aln %ͮs@
+ME$bqᵒp\UGcA^z†޵qAҌJGJD߁=y).YHLаyd?S˟P ܩ =2<) (N2Grˍ|L'"2;iڃ!?Q4J/5} F.6IXT"C2_wn%r L |_Zl{=db$a*LPz=?sNFqMKH=n5lQEo4w'gߤ_ϷQ4.3pL3$癀usxR'g*<KJC2L$^juo*ee@
+EneNR>Wgin.f['ѵY}C9%L  6$m:**LVE8NJ(D4 j1nQϸKF !WߋIt%d 7/J_+藭lD8CCͮʍpl{1ܫ`'2#)S$F3YC(9A?=MoKKĸi\M-7OŴ3DfoS0JsOnU*9!fr!9BЕD˲8-d- fAJ,% Ċ?odI+Qyq8IU+X%!v |yg}x{fh$M4^,Е񎿹갮#h?]g[g}خk50Q'?-crG[_GW
+"v8,q .V3֙w4UR~)_ ,܅!B#nBR[6/tR9cY2JgIvwlǽ_ؒiaTE=q>BYGe?qע-#X<Ut(.铒 \y|D'Vg}P W\Gs«=J)";fXrrj_f쎋M<m^>bU_$nc|ZcK1ǸNjt+SȒP["S/F<*dlzw%%]8ʪsV)PP:W!\<Q;J 7ӥܜYV`tVUE WG%T?*Ɗs<YLU2=X%jwI4 +y[_)JkTR6љtD(ۉߨΏ($ۺ(
+T'\ $'Ix~k|2C%^GYuբΗޘʺ|qvS߮ sO,Z*N8g0Gmq
+\1@/񛳟8c^:Ϟ<|Ұ ðoPC=9V}óW39#GuRK><nowNЫ_McF
+獩P8Q}jƠA'0iF?W(J=B6|Ӭ\Z<p1T6 o.
+/rjޢ\<.T;5- ϽIdQ}aZe'[DT=Oave9|Ҵcl`YQ/R=ѧ\IWmTn!#Q
+kv81 JSlnc*LSX(y]_*Jɔ ")3jr]ӈi$֤#}i买f]}YZ_m5LG̟X!w2 sVvE+MRlN2'x`R xdTݿ"&2۱OAm7F] Fc"{_п[ i4[_uu=VrE7qۥPrN=TP iABR_QPB[ye༇;Ō; f _0И
+ҍ7:7i+A<wfh$4K~TJ)oY4>甽[$oH !əv+Ab܊Ƒ勅Z?`f4qMmbendstream
+endobj
+1096 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 45
+/LastChar 121
+/Widths 1492 0 R
+/BaseFont /QMERYG+NimbusMonL-Bold
+/FontDescriptor 1094 0 R
+>> endobj
+1094 0 obj <<
+/Ascent 623
+/CapHeight 552
+/Descent -126
+/FontName /QMERYG+NimbusMonL-Bold
+/ItalicAngle 0
+/StemV 101
+/XHeight 439
+/FontBBox [-43 -278 681 871]
+/Flags 4
+/CharSet (/hyphen/period/C/F/T/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/r/s/t/u/x/y)
+/FontFile 1095 0 R
+>> endobj
+1492 0 obj
+[600 600 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 600 0 0 600 0 0 0 0 0 0 0 0 0 0 0 0 0 600 0 0 0 0 0 0 0 0 0 0 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 0 0 600 600 ]
+endobj
+1038 0 obj <<
+/Length1 755
+/Length2 1136
+/Length3 532
+/Length 1693
+/Filter /FlateDecode
+>>
+stream
+xTiTWF"(4C^
+Oϙ_sޟ~;.l8xNlfbL |1> ]ekϱ_g\"'! ̜+ [(Fc'"C(BQ$WvH~D̠
++;g&RԶw4V9|fҸx5y6r膣w┦ݷmj-GpE@wi^d8u?--HXUf]Т٘yط~<),.h0) ~s^p_ZfSƉWaphϣ1,t5 K?+e3ks+Fq^aPRyPFɚX})%-֑N[Y#}HS}o>nKltR5lV7US0iSՉ깔PrAU*L7*=ڸx%JxK|S[w(ZP>7;{~k;<5\/o䚗eI
+ηuTC^G7ߝR8v.GghװYGrD66d{O^)~
+ʼҥL|VqN7elW9m>3xfwFW\1r{݂$>ldWoQ]Gk:f rrrko\()M*cwI(] #I1j̗Yc,ڋas ɓ oniў U ʆ9#ef7Ռ/"eX7IשP?> ' 'H\'hdendstream
+endobj
+1039 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1493 0 R
+/FirstChar 34
+/LastChar 34
+/Widths 1494 0 R
+/BaseFont /MULMFK+CMMIB10
+/FontDescriptor 1037 0 R
+>> endobj
+1037 0 obj <<
+/Ascent 694
+/CapHeight 686
+/Descent -194
+/FontName /MULMFK+CMMIB10
+/ItalicAngle -14.04
+/StemV 113
+/XHeight 444
+/FontBBox [-15 -250 1216 750]
+/Flags 4
+/CharSet (/epsilon)
+/FontFile 1038 0 R
+>> endobj
+1494 0 obj
+[529 ]
+endobj
+1493 0 obj <<
+/Type /Encoding
+/Differences [ 0 /.notdef 34/epsilon 35/.notdef]
+>> endobj
+841 0 obj <<
+/Length1 1647
+/Length2 15806
+/Length3 532
+/Length 16688
+/Filter /FlateDecode
+>>
+stream
+xڬce]%<iۨmg%O6+mҶmҶJy߾}{?c+fD+9$J ¦@ {;Ff^=
+U〣uXۉ
+`ၣ
+
+'%/@ݢ;
+b^q}(ɬq7p &̭
+{.ya'ܡ> { |8,HugUwq{r ϔH;]&oN+{r+Svl ;/pHL;A;o;E@w%Uu/1+a`Q fO閐%ąQ{c̭buɟs002aNJG7.Hv|GQ!a@ZG
+ T#_P֝\ 軕ɿ<%zo?NtLv8>2_)<υPpp19ཿaƼ"g4uH0F3orqߐ\כ
+V`V$*T]3~>lm7x1즀{"τlQ975dҠ"kk=[<z$ˮUķHf4eHЫt~>SR?5\ ngJEI*u4g}9hyy0,.F;/rl{s=k8
+" :1(/@M<8*٬? PGpr B
+>qׯY¸Y\92+JiɫDgsU
+3]83Y: κh[fqօ=SKa2PZzN״:4 iIy@Iy:`/A;M1/T?%iDä^q"A&{=xP[R -
+ fp"`mghxOfCU?YI8P'eds]|o+f_O Ø?v {k@B':Z8B%TCxWX+
+s@g^+hrSb[e'ň*h4zݞ\yIYD'@U<mCSSEFN"
+l&@$u{(`ŃR1`o@DMN2Zw̼TEZّ
+_kDq>!.@1ۥa'rV`9H x8pT3W19ukK3 EQbwXK[ ? jj*mw$B [&Siɳ*
+^ ?ngFpl>\< =Ɖ=Z׉wGFӬY`AcM$~ ;+*F/{:ǻHZD!T|Xpb7
+7}2vclf큥S5/Kkpwyn&cߩl
+nf=H[qˆֳ5N> "y[訏MR'jO3O&^NjGfFՈ_Nj[0KMЋP>jˈ{A,Oo 섳͐Mg/Ԟ9iۚ dm d|֚J\<V`{dZJ/HQ[VrT۳aִT;.S$OFme?[6)|3]ab̖K
+検"ۮgeg7Gp KyC((ZJ>P3Tura+4X5Ѓm$ZղP2/Z\Pŝz7&oCkn \X옫d&wYV+lG)dž47K%OgaӁil<9#K/̑V)WHzx, $,e=8e${%B,^܃-(I@*1sOJ!ŵ֧rYMfO&hC`,@QPɫuuv
+D{'ᦀl~L YIDY:#bRM ORHz`n赈1|;D t=)lE/NO,UwR+Yb;}\7zI2əq݆OHOp.hN2$ hBb9؅r bO*3ٙMw6B=1d
+4YeВ g,=?P|"BseWI*fWK,`tiO1ۡ6mPJFqw8,~r
+íl E)-T/a;[ 1>/1`3{TŶ{7>T"[ Yָ/xҩ&&<Xƭ5][€Z #[(W;N5g T,d*ar0V Ήj)ui(Z$wJq⯚:7V!ȃNDTl)n9 qun#,J2y?cZiR[g!=яUfDI6"'n\Ҕ /ΚgƼ ]G?,% >ҿD
+0戈$cRDR5"fvx< `6!{Bv4`Ig\ NS+\yaw}SGf
+J2 1wCr3UpY!*j;OrT5Z
++2xPD/E#=B}b gzqǙi
+
+t*K(մ:]tԗ>H SwH)״ii rM5<*_UmQC^DnohtNj*C_`b
+L,$ f)SN(fs\&ot6hڰq V;sKdHu. AvܯPje5ezƁo43og>xhis 3SRQ*" `PZ A0޹k³<MĊG [P lWZī;5_2XP/!1fG24XQo![Iu-0qo؅%ìpbN_[y0XcyDV<j{_*פ@xI^iJ+x]kxAM@W?#:[41z 8ġZ2إ;'5*1,6AfdmtgC:5yQ Aw>@* =*{yCanE?=X Xznc6>vZnSۑA$Tp 1G`qQԘ70T$&
+. [zDba\%G }LD`~h_NȏIooJ'^o\m)ip^a3N1E8+c 6[(yk~(^\Ђ3V%眯)^zNXiOYlGBVea)tJqs b*?e,xl؀zU&6T@ݓ%T?9 OON=4yiv\;W_8;94Q567iEL?q ~ dG, Nؽpeoe'^H=~+3j?ϑ_E,-zVnkS/:U.rQ!N4JdSb/> pS!Rs):T镟,B|
+Q$v^( AEn d EL=qI.kY P]պH{ f2eORD)ؗ=F U<pr˹ Vv$(U%;I3eq{bpyVBl&µc1wUTo^رFv7zLC6_!v'3Y%Nb+>3ё;QWc<熰=[N}F?v4ܻK޷zV\m{<.?>*4h3 ;M4M|H<ߕ5|]9eM2=ʪd]ȐBqEFޟSv_j m2 /,akn7c.>P~su>Sx7j:ƺ OI/L5, Z[(L~"M'*M]1cչ0 ﷺJXigHcU=m8[`ۛ=dAn/~*٠{/%4gxJ5۸|) 7wt "fK%:XV׳zYhSC7pyaL>[%[%~ehTxbM<@H۪-bF>#y(ϦnL$pZĥ_45AmСsE棺P KOnl;(#pW˔fy)]ǝQD (S"-7Ƒ UJxi%/)&
+3|sݨqy9]QCF7쥍91?v(jruy]L&tij1w֯I6\0o@Z!蓜y7Æt䇣t6<^nUCB>XYY{F})!STH*uW,t#(X\mX:e"$<$D˜nt5o~e)l_&,.vwڴ',SĚUcZVa.·^4İu
+FD/m$v(q._ؿz|O䦞 ^cukc{PivrY߭-+ɲ:uDB
+7g:0d[6NKhƺw2F3!+8T6wUOq㹅y'W:p[;z8k
+w4:9@L ͟E4ߛ9~W^|7s"b=]4}>Dˆ@֊2vnvL 0StI 5#}U N(f{kӂtr5f)3 8"7"Cnb.%%.et t%$b5-^|[]PD"2ty޷{ mVsB3m$"^'Ds'xYuE35B+[3ǒ!8^KQ)=5^n:z ɇod%@e6Vƈ(e =jfr1S@
+3Wލ$'Gl^1)-(z\Fm0Iݡ䔝UCWI4/|(}0&)s=d< #ęYͬb'MaMCH׮ Z3h>2XE{]ϴH 3o=
+
+
+ogj V[qQhMC0v&_ 0D~=9  Uݞ\~ e_#7!.>F7
+t1- 0|uÇcqj%{QƴOcVMӦF*.ktd]vgh^܎4E6+dLU-x|$xJ#B㵼ZT& 6UڃֶF;T$x2`flXʚ~\#J$*1omRo²(u&`XϮG`q3~']K[Œ+N!KEXR;8
+@U5.ǁJi{VpuAX$=y`BSv)'wpRm&? A/O%Y9xrߔ>b~q鳢 >ֵr $#1-z `kH3Ţ&S))Ljʃ1)
+6۟㇜]/-q# '"`K=rlTm5OT8dH+{E> o~4,hh] irTyձNn
+]һ3q%vOఏ"p`9P7++ G(XǗP {7Ex1B .xĥ%ҭ˲C2Ȼ{qZVoR b_K_
+W7&vsx*){՞2Rw%BAs3"Z4m&(sl$qa9ncq!KƎPS
+pZ^R ӆmumطl}\0]K!+285NɌ[(F cl+mL헿IeXϜ,][jl`~*4xZXvϭk>\H!g%)ܧ*C1Ez@li]>n3Ѽz< a
+”XPX< 7]V 8}B
+O3YFZ_d 4 1wfC p1dH͛8ˍLZ8$odr|7sk٨ZFPs\ S A(U
+`|w$&Ɨy!rG]dٔ;,vrzHs ;|&2N.5K#X߬瘹:Qb2Z=Л.1F0-R}js{Efz+ts)+%v]-KpfF&2g{Nς\]$مNT xTGL&jLC~/OfzЃ%yPIq?F?r!]T4rR w%|K钐6#a"9_dZShW:5 /jf(EtC5-FxZ`qZT 7)# /lY*s8P\~w3JIT%= s* v6lSVҋRW+-ݴZ3;4|Pwrt~?%%ae%i
+lT-R t@0ng_a]Z!)<RBdm`"@#VAo`/\*i~Ǖm`" *Y2@|Qx{~Oׅkg._?.].o2,ǭֵgJx;8."zJ1f%~[=.`uܣރ8p ˷n gOsvA1{TS[|SZt'جR~Xֹy+x_+aƞp_A8#~:ތHpH1C丅Q:QQA$p{bьہW i[mcT"KL .X>F<cw"̤0~<V,̼Ƿ7lx1-/ ql
+Yنw-LG./ŵGv9SL~E(#>8Tx6c(> 3g[|a61ReDʆH)}JS+GTVUZ6A"}a쾴
+妝vuwO֤v=yn{ݷ(ODiҧ
+4EװwhřJh"bڥ
+:HY7g&cݔF zR
+s~ڗ,>{z3: ҍ7{0N]rsެBG5,$߾q%'B+W)I)mK05OkPW1+V4^t䀔խsŔ挃5Ŋ'Ү<au.k']|֭cLxV~)*LETrG/r:\;Q<
+mZ~dB=lx'&aK[ɾKm:'xBi Sg7
+֮ig6⹅/II*cNRNwHpZ
+~:ao./w._$$S
+S[Upb= qOI1x%?tbq8:vk,% bvb"Pn7}#!zn@
+~`M&GTdmGMHV+W+e} ٩蜍 dyLX
+>-#mL868z N0~F/"F<_"Wk ߃z5'%e4FTVI? |p/9ÚD{> *K(NK1S:pSA<>Lk@A~}քJ .5n0-ìgݗ'm
+| 2v>5_A9T8Ǚ@dƪI?`|C_d登p3h=a??X,ՅcYPBIW؄՚W
+@Nrp+,ȇ0K;b.ϮnO:%Rf!t<a)f酱AFgsa,JGn<ȰN45/t~LC2-.tᏏ=c
+&bLc/߮B/$\[GjuS*VNŋu`Cp߬l}
+9
+Mo:SƢ`iol[/Wv@z
+<\Sc༊=WwXGՁչĸ1K:tWm
+gwljuXmi@+!M*8uAQMg2FI*ϺNK Vzi?};z3OTq'^HĐ~ Gk6_Oss#]#i'D․7ZD ؐ̾3QNG69*D*Z.t⩥u:%XxځhycTć~dv;E^4 D^]0VbI]"@އ
+cvĪ%v=3Ӕ,f%*1Ly7)@ DFz&4Zy_mBgkuՎTGV=w4FlܙY+qi'^y5=u>S fϒJa>]=BnxN6g~QslI$&5'u9u6[Gɏ#ihlH;>}-S|D:-,2cks cÃЍhc染oͻ`B2rhN=#F$}?1IR !<s%Dɭx<Qd46#Y~̊z~P4 _Wv$ue͌}r*<"`ߖʺ⏣KRyAaWI73|dh#zir>,yqGfHb8L UkBgN?,
+@UHBXvRcQ"l'krX]X m??u̕<q9h&!h 4ߐF
+j
+ wO7so%?H I X"PG@Eã֮OO>a:[B;֘/Z2B@尙B}N4&ȑU"۞Bw#2BΪ8O
+e) h C:Gywm:p JpܺFCs-sQ7=rd>Uu,Oza+̈܊&hYyxk-RWH(q<4ݹԻW%npMce:q377 7,M)R}4lr뜅ԑ,M1$T< 7 K%Zn”('צFJ T$)2^dC$]Fu7E*(=f?,>OU_C< =灁b ЕZm@t_A]f &
+`SanbY5{@T'9(I?miU KUA4K>&I -cZD=+e'z`.#,]hi‘0_@\ zi}3[DHaEEq.oug { R-m>`Sj}1$D&
+ר€ĢĢl.
+endobj
+842 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 2
+/LastChar 243
+/Widths 1495 0 R
+/BaseFont /AHAHNC+NimbusRomNo9L-ReguItal
+/FontDescriptor 840 0 R
+>> endobj
+840 0 obj <<
+/Ascent 669
+/CapHeight 669
+/Descent -193
+/FontName /AHAHNC+NimbusRomNo9L-ReguItal
+/ItalicAngle -15.5
+/StemV 78
+/XHeight 441
+/FontBBox [-169 -270 1010 924]
+/Flags 4
+/CharSet (/fi/fl/quotedbl/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/four/five/six/A/B/C/D/E/F/G/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/Oacute/aacute/eacute/ntilde/oacute)
+/FontFile 841 0 R
+>> endobj
+1495 0 obj
+[500 500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 420 0 0 0 0 0 333 333 0 0 250 333 250 278 500 500 500 0 500 500 500 0 0 0 0 0 0 0 0 0 0 611 611 667 722 611 611 722 0 333 444 667 556 833 667 722 611 722 611 500 556 722 611 833 611 556 0 0 0 0 0 500 0 500 500 444 500 444 278 500 500 278 278 444 278 722 500 500 500 500 389 389 278 500 444 667 444 444 389 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 722 0 0 0 0 0 0 0 0 0 0 0 0 0 500 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 500 0 500 ]
+endobj
+831 0 obj <<
+/Length1 837
+/Length2 1118
+/Length3 532
+/Length 1710
+/Filter /FlateDecode
+>>
+stream
+xkXe5$r
+yWEewXօGmAUՆe`wg`7#HrQK\J bRɔ%c}i˜9y?ǂha+.%!
+'JUER ᨄb#J*'rQ"0hB0TIiIER!8X%{F 9%
+DD.+
+eߔ%˹N%`LJnVPz]=Cc%Sm,Q?2) 0ذLFmn`R
+->zMwUa&3:);l5.Ϩ[􃗻5R#\6?j~^=1cڦ0ۿ4Eqwjx\ZSmg:麙i}ms> Do\/3&o˥ PSq׎m`u[RcB +պmiOOi|3;FklkT؛ gǟ x3ݔZ؞\#jU~-_|Q,=})2Wfّ,< YsgE NQdhp=ں)];nErz~qѤ%bwg+w3k5Wػ˄C>- ~f77u77-غ¤AS`(ozh?C4ƹ50N!kMay˕! j9yXe&oݔ| ]wٹ_+xVw/Ě~|i XgeŒҷ>U-k;gkTwrqݯΡ.|]zc͏S/ޞ_q!W|)ۮ=2nlL>*,˚?5̿k"E=Xu~\d0d"r5/tm ҌYenRWt7R <:隋-qY =Wbia^~ﴇI<Dƒ.[MԐu:%Wݲ0uy`cv]KOۻ'GWd~u-m"./$& hRJ[US1z##n}f^WxC#6/s~֢VM7t.qY9~!_WI܁; z;ϩ5?ŗ?ٰ3<הѰ{{p@l*ǯ0,3Db[Zšw_>QT^nvL[jvH ^1TDVܡӛ>P  1
+$.H٦ endstream
+endobj
+832 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1496 0 R
+/FirstChar 15
+/LastChar 110
+/Widths 1497 0 R
+/BaseFont /JMSYJQ+CMSY10
+/FontDescriptor 830 0 R
+>> endobj
+830 0 obj <<
+/Ascent 750
+/CapHeight 683
+/Descent -194
+/FontName /JMSYJQ+CMSY10
+/ItalicAngle -14.035
+/StemV 85
+/XHeight 431
+/FontBBox [-29 -960 1116 775]
+/Flags 4
+/CharSet (/bullet/braceleft/braceright/bar/backslash)
+/FontFile 831 0 R
+>> endobj
+1497 0 obj
+[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 0 0 278 0 0 0 500 ]
+endobj
+1496 0 obj <<
+/Type /Encoding
+/Differences [ 0 /.notdef 15/bullet 16/.notdef 102/braceleft/braceright 104/.notdef 106/bar 107/.notdef 110/backslash 111/.notdef]
+>> endobj
+818 0 obj <<
+/Length1 1612
+/Length2 20822
+/Length3 532
+/Length 21731
+/Filter /FlateDecode
+>>
+stream
+xڬchͲ%Zm۶m۶m۵˶m۵.v9}{Oc2"rƌ"%TP472sec"5ruU25w%kd"%v25t1t1"P75!15&`b"`"%wt4p!PUR/?!Fw7S{[S;MM \,L ,mL 4% (T ML m\l, d,MM) l 034gXƖz:!p0utvN`L`dh.v6&k7!'}],\fU7O Cr;[u؛47vZ9zȔo`Nlig_ hL LlL;U'Vv+qtq61bdonsK;(E̞vWs3uW(ʿ$ Ml< LL͠]$SO[ovs3;
+.f6;/_ELZFXX[zLL_E^EDP^U?E)E/QZ!$dAM21M/Z8Yzh-_V#jgloϬ(ڙemWj}ޘ;*=+å=otJD{x4ԡI0־?=b.ysPh͆/
+?d5&YAAJFI'@@Sw\qLK?aV4fY1-׏5|
+k&NfMZ(B_7@DL- H$=
+j~!>d$pE(fR;޺4Lbm@(~?q 4B7}^MF^ȩ[:4%o]\\r>^?Nr6II"c ;߅Z4O<Vn[ ʞRW3S+%7 M]A YQ9eRt
+?fق"~',Z$E-u[IjQZ7`eoJțgG
+SX2')`M`9+[8 5zlribUR~m>Ĵ`gMMJ|w~/ f2"U(R5.\;bA@0 э_o"V\c}M͔8{bmvtI%i#Vh?#0!&g-LA-e7H C "ܖU􈠵BԵGAZSe3z1}Brx\Q]l!W$~ZLj Ӟ&c@Gr;+IB=[PJ+F;i^Dk`_&EfC_3'~f a|6OV=n-lGE'Ulǹ&%`^>QA(Wm|,^|#f
+#ö+
+uqY{Ij'~bGR5<MDa⥤VȗD;RQRONɬ2qSjϺG @z8 Fwr,Pi ,SM[YXN^uUjxNq#(O+#zQqSADqՔ"^@e kNvy$3IGŇ:%C9$iC_A8e5
+iM)v9x0v1pLob~Y2-YKp5X6 [;82pDēJ ~Qr @ĭ:QH9
+歀7~\:"T=h$=/[)k;X[ʖ t?o­\8f%!^FߥBkx!Et3# dE˯-$'˃"7@Z%yZ2[ШW in}^k@-'!aa?q蝑&tۨ+Vl)pE3jBKUfr>ä
+ </ |ŗΔ.>q
+Ŧb+攝rӟYwep)'+0wh-vf ږ+/dvͿb/P[AlĘ=G5*)?|sjQNF_lǶOp$RǡQ85l0' ykK&0'sA&U0 !XNPKOS]?ӆn;%Fbmf#5<ޱwg7>XL~tgD$(ǑddS5Gۤ!UwsMq~7@{=z h?;UC_ENcѕ*Uo +Ajy8{hmpCq@bB l*r-eBiv9@wq٢t_6ڱC`Z @ʉuΟ2 i;!@Ej΂O*Kh{"$'kSxqT#Hs+7a
+BEiHB.RS6 JpBtzdԦM5WGѯ>n6$, oR*23@'
+GxkL`1w;S+[PqMc\;K| \Tiwsɇh-'; v]
+s
+KZi0btcBt;A\0+
+'$x/\h ge6w{ij(咆˷Zw#چuai?fUv9ҩv!1dzU!ӈ~DcpV3;z}vap+l}Й@]-?# v7X 24>"j5u`F!)~d.KEqJee+],tdbtGfa72^yZ<Dl2 } t>-Q"%Ccig*/
+S~Yӯj;5 ,lϿkJ(u{yU-茂PN$C~yFӽnwI
+w4c.f
+=&p>>Þ-C隞&^"&.oe |0*zDZ Qe5TD>#-
+$fx+x 5ޢu17wvdrEF <(3V~o#҃z/^ mt+ uK}҉1~L(IB|*xQ+BñpL SXzƣa \k9R m\Vch< UqP⪧+ $
+կ:Uud :akyP@M+]#UxþRs`ImB.m_^#vb{6fp1@T.Hq68T)r SY<]ysuGʱI}QWx~4ot"'USуmR1a0 ɉߟzQ茣]LmʴcG~
++UxղL?ޏ56zM0 Y㖉ԯhx|q}\;&~8AXŠ-wˠ?w6Ni}86 ĭAƃ5-s&)N蘩lgptܤ4~x3 Vy6hp?/![Dg7VB"H!=w$Ѷ}!>Jp,Z!ɉMA#S<$ r#!ʋ/[vmd˄ɺq/h]RrhY;
+6db4E
+Jb>+
+Y֤rka6}ֶ1_]ikP7Q~K)Ka Іv!3y<>?qHX
+p:h8c UK*C5S$UAF]e.C盦Ui#.mcEĖk[0r`K<Tde,Ӫ#;į:YhL:痕#O.V'-zfU
+%{SNj'm`5޷;2\ /c0Cŏsr\G^fl9 A4xle%_~DXy7֧\}CrjlLV=(d(0-K$~_sX| h*1LH0?o X<p*m"Ѯ^}#\;!Rłr܄ 6|:7,g5*r ?yAplar0clO }Ҁs3EC潩A0
+)HXHx6? ,|2]Mc.L*k_P"k漏Vjo_c#9
+K-{wBt)93½R*i4'4Hu^rd
+lF yT@~w肝5_B=
+>sR"
+k‡oһ u;Stg]xr/a=hd@ܶ/ƶO VuLm(NzaʤRѠ2ꞠMudY|<r#Rcm;&
+J?]<Ěý<f$]:]YM;zS-m|s|dz vT
+l $j{
+g>FaRn'j}tn2h;! p/zf7%(A9Gw6jV:F`cItcd \vg1;!{fqnn2ЗVfb# u & ,=7ݪ71@:q
+ {ոobX}+ZEad;-ELeH0U$MXAҬm=$"\)\
+iw
+#.ZM(@΋
+p5gHOehǡ4W|/n>ۥyfFSVXM,X 3>48@Z@eRpmgTDi5ǐO-#O<X/cU9*Bk+%mߨsiMVdqw_-Rg™jQdfvGjJQ
+Fށ/
+F`-VkoxKXB$7"D9 _ <<Om87K=?RAM%přiKeŠ~OK
+fiCKJ'
+@< Ma͡!E}]
+Tnj`QN }&Td4
+dž!b]?o3"jlem\)؝Isq, 0B$7zBc,/cI/MTf3F0dOB~
+A6w0lu;]@<K'/^pzEǕE:QjUi8WLa$B,AyM!%I)<Z5,u>$x )ɼx-sVQҪB,&S wtLl W@ <=m.h?ڄ+wa4~@R1 4dxQE*M]_g5Tb[G;# N>ײ}l*S:'@V̻;OF;u>ƞ ԍǶTUh=LDyJ뻇8][0/ !a3y "ߊD{͏HIBnu
+"SP2]3֚IFL:MXv}t8S\mbX2]k/tSaPy4N Ƣjw#D+-`|l/S{\Wz vk?G/ܼ\Bm3 x?N`>_G/3enrVVlv@AB!P ^)7(\7*OrV0y LJq c'IWɝ)x q<Z]()$xc6YH秣C'c Z3o<nTn${t݉A&NM)9
+Ԛf^ʹ޲rƠSX *7.64S+_TC0JPLɹ'ļASyh}חꜩ%:Cy^B;Y dO{A$I7 Uqʏ׺ R[
+Yv@O^d$3ZdgIA#{b9>qv}FCZsi*@AQ @_cU9,(xbj5+**7'RlLRa|fL&t2)B,̅o3QFoFbko{9k6Zx.* CΘZ \Kz[79Ac7
+'g؄9ܸ]n -T u&ƵM԰c]q{EF8xՎeL5GUo ̎a\ZMh˷OV&jvWLLMuFw
+endw%<q
+opT5k¿Ake^eO@ShJ+ō!r7Tt=׫vzǤ#pd?Έ{\gԪ C˾FǙ&jvn+W+J=(&Betj_*ko\.+Tޥt%3<T0+
+nPJIInkih?~`[<aN-=}'\ Ә-Ez=.nND\Iơ͵SlO'YCW8(I/4D[Tf(UA}e9|sxhA(:1T?Nvcqt[
+&Ltk\m*+f_岟{ÝQnG.}ҟyfP"8hr/(w'A_߈-w%D^:6s:DЫW͐z_"/A-\ʟqDmVJi-}~JF~F̝A7gƹNRa#<>zg";\jRqzf!OבӃ^('=ɡ,li"=yE
+y@tΉ+ qOusk5@`Lqu|8vW`a2IZŪgL؀!,OQa:ײS{Vk,}o\)Ʃ_Kb<ia M{R (@?y+ӛfw$|-*Gza_Z/ m9Çf![z".ݿ5C ph\D&͟&+#nyf'=|oT29;௅P $5|a;[sMy|VS&q%tDwk9?OfKRU`^ΤjvP/ڍNXVPzhen1_ qQiiG&EٛT:0N|2wCwѯn:B󺂗q-5S(ѣ'VHK>Gk7P/xELrNs>-=zu3M6k+>5D cq}z48
+K M3{
+L:>.BfMw* Z 3!d$3V4'
+W'Ltk/Bwj%L2
+ڒu-&],@.t:Xַ,{e%DַZ(/N n}5zzn R/ة,8Lj'Ig*ok-cwp䎭piabʤ Ct$ LXϿl%%4|婇}ׂ{'v*׽jg9k_*/ڧ5߶MKN
+B8Wi!lyK;}}[O..wG^m-hË'SbxSƯ Y̅$>Dּb62{T=k֘G#C
+܃d.ɞn3ǃl=e"E2fh9kHʆ- ͎"e]c+[,u?>*FO{Zo^^
+m aJ  "E<yNx|C)!a#;LJTfIsgZ4}AӸF7:U0ҺkJ#?!lSi06}$WIQ&Q&bJUMwOBy\+qk
+5WX(us-6<{P]v.NlN~&{ ]| uB7(7!Y{Fȏ#~7Rl"]iJԉb }!m~9Tޙ7-XM9[F/5L~#b%pQ<X;VGATMT_rWTfh<c3΢"Y)<>!Zմ e<!fl^'%V$9絖( +F~&{X{Gǯ3ׇk塰:UC&Ja wB*`*mg*.!!3&X )&\+&}0Xh@8Ï6y|3>8Jk.e$Fq(.E[Lwd`?HJ
+9Pk#x̠=PI>)Ҥ
+j\/+ J3uYEe81N Q'`oVnF9
+ MA|9j^mC<?c%^);Q7T[w+SSHKІU! 6VnWJ H]aj'Y{˳
+ܚāRewfSGR%ͬ|j-Df֣f% <dş1)Px,%_:'`;m!r G_\%؂|aȫd Õݽf"ų$q&aQIԤ/+m
+;,& ٬TqhnJœ㹘n1\Q|_2KOmt_8mlH̎W8OcfX?33R A'*}Up*ؗ5n]z);<#_Z$f܁lMWk킛vO~#U!}Ziza$
+}6V9n1d9,V8w<Q i͡#_.j("QWg6p;i
+% ƵGS4G0:"~,Q6E{Y֜M~ /C|S)|U]gcn"yFtE#:"pnecʱ;;h9fcK\3 I.wCZEk6?}v/UFg{P~銝Ǭ%2ceǃ<xՒ~p?'5Ti+LӞ+,16iƽjܵ!ޤǃnq;5T[/@Y~s, 4ĉȣRr
+۟ jɺiIB Z7L8bhICEn,^h~΅sme1*f5CþT:]8!k{xmQ[e3}BGST 9‰X^4tPLE[>Net5w򗳚i^Mhg68T u q0]f B|iPe2Utju0%;8 <{.`Ǎ\K&Zxצ-<uZcD.L?=NkUB"n
+8%.!*yт1yܠ߰
+,`"`0m6Edgt8zjqA;MK´+lA mltߔ"
+k>Jei_)3:gqւ4bMegu]!{Z7t7uwuڎ6;%w KE}Z-'}lQK6r:'jGaTlZ^eyPmtC~ۺs\uRꟘö<<9hۆe-6@+82ٝzܸs<喿_\ڗ-#H}tI`pB,`蕦]񁥀2\,%&
+.IjA_*^1Dlm|
+^E@FI޳>Uxz\n:fck3]Sfz1DO/ԩak [yb*uCN,E8E?&6E[S~@_PU^x;;@mtz=.ZBSD6\xTA^%vꯍ^~p WnWA &qT+Hǰm+COyTMlp,ꕐc9T )g]?m^9h.
+n7ʼݮL˅mr+k8ZǴXfYv5VU0q@h$=d7OŒuZ$fy/55'd6 %M"Sk0d
+2rÝE*?iՖiJfFԌCfRS]1<HS[Lq>H*-j<~=Y|-DT/R4DX,CwlG?)E%Gإ+55˰#_Ruf2i~ . W3_`x#$yԹ <(fD-E&x Vb]q(ݎdMaD=ƣd-핿5J{VBNBaI
+Mu,:ՁfLޓT |P<z;lp GmueT$:F!WKW=0 D/:3;76}0PȱWq*b?K"]9k"c ]OVW"{}Vm,d LdF"&,>N8wݷB05M-Zy3[s_eDiJRi꺎%I
++*rƞTlJi pSgRQ`Y[ǹJ5\3fr(3M<uPUO-yK>ۺDkOgPyxK,_ੑax}{_"`ҜHAA3D٢Oĵ%m 2cz3͎&֐BOu~/!GL7Կ sLo&#[J>e-2~B[j(I?v/z55No$Qx
+kX"6Dx2qݲ8f.-frQH<ɺJҒwV-?ɾ
+endobj
+819 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 33
+/LastChar 252
+/Widths 1498 0 R
+/BaseFont /TDAOUA+NimbusMonL-Regu
+/FontDescriptor 817 0 R
+>> endobj
+817 0 obj <<
+/Ascent 625
+/CapHeight 557
+/Descent -147
+/FontName /TDAOUA+NimbusMonL-Regu
+/ItalicAngle 0
+/StemV 41
+/XHeight 426
+/FontBBox [-12 -237 650 811]
+/Flags 4
+/CharSet (/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/less/equal/greater/question/at/A/B/C/D/E/F/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/circumflex/tilde/exclamdown/questiondown/Aacute/Eacute/Iacute/Ntilde/Oacute/Uacute/Udieresis/agrave/aacute/eacute/iacute/ntilde/oacute/uacute/udieresis)
+/FontFile 818 0 R
+>> endobj
+1498 0 obj
+[600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 0 0 0 0 0 0 0 0 600 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 600 0 0 0 0 0 0 0 0 600 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 600 0 600 0 0 0 0 0 0 0 600 0 0 0 600 0 0 0 600 0 600 0 0 0 0 0 0 600 0 600 0 0 0 600 600 0 0 0 0 0 0 0 600 0 0 0 600 0 0 0 600 0 600 0 0 0 0 0 0 600 0 600 ]
+endobj
+799 0 obj <<
+/Length1 791
+/Length2 1369
+/Length3 532
+/Length 1948
+/Filter /FlateDecode
+>>
+stream
+xR{<TnKe$3hf! (YkX̬5eqf(.K7Q!*)I;E[:E)JMlPT^;?k}}6A"_x
++kwDx)p_^}F gԅBI+k+ +,L,S&{DhC@Lb2'\Ќ<Nn{~筬ڊ"Όzҙ=!stDn/9Y{m8$!xOb`nsH7?++<"O~=QcYW򂜜 I,w?[} #0m:l`3?"c[ђ/͛53l+~Zi *ok#9-܎ %X~¯ !jlڇm3ST{Sm1V{FMp0k)kr%0XD?2vp LXr*?v?hśîm ?nX$
+?vGM*vէ]2=$0g l(ճ5nhwh^Ii M9}):SpuCӂOۻC΅Vj֔r|,#18l]ch)Z3-vB>B}p>tR$hU
+endobj
+800 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1499 0 R
+/FirstChar 34
+/LastChar 62
+/Widths 1500 0 R
+/BaseFont /FULBEB+CMMI10
+/FontDescriptor 798 0 R
+>> endobj
+798 0 obj <<
+/Ascent 694
+/CapHeight 683
+/Descent -194
+/FontName /FULBEB+CMMI10
+/ItalicAngle -14.04
+/StemV 72
+/XHeight 431
+/FontBBox [-32 -250 1048 750]
+/Flags 4
+/CharSet (/epsilon/less/greater)
+/FontFile 799 0 R
+>> endobj
+1500 0 obj
+[466 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 778 0 778 ]
+endobj
+1499 0 obj <<
+/Type /Encoding
+/Differences [ 0 /.notdef 34/epsilon 35/.notdef 60/less 61/.notdef 62/greater 63/.notdef]
+>> endobj
+789 0 obj <<
+/Length1 1626
+/Length2 16997
+/Length3 532
+/Length 17927
+/Filter /FlateDecode
+>>
+stream
+xڬct-Tl[+m*ضm۶*b[Tlbz>|{sOk裏ǜJf&@){;FV&>YV< k焧w$]|
+`cS<@.
+t
+`dea%8ڙ'R<W My@KhE
+KG AyHP]^bLiA>Rn2PF$ӓ[pZH S {!e1 |T~x]q$e "0HF찜&,<Æì/ >2:p6^mSp.v|3p 1RsuA;6mB21vzqe_kf}B)ybݸG N\,Zv]L>lyzw>BU$8a#ޖ! ^8r${D[SU(%SqJH%o%,){qMVv/jR!~ɌKYVIȶu4M½{utXS>Ë S'J-#TTC-/%Rtjƅr;-=h+bWPźxFЋQkr3g? yHF-GF_
+^s^迉IT+Ǵ a>N(9
+KfS&/\VPfH 0ajIr2]U1"U:h%o*'At36<0 vQYqx= WHw0Ncdz@~O(ӳx(&o A 0sBz+N[*S5"uNFp_\8P2Oc*5n!sbm5;I5]@O||e BiO%1`͏(I\̇
+z8!wZ^_qB+k!5)ȅUҶC(溝Go1y_8o+ُ򸸩4|Wn1nz:z2,hs‹c p&]䕖4@+OYndž``U H?iHt1 С =43^c.SRGpBt+ tmFjc31bM(Flt4'ɅΏ,q>8gPKuaj*[^"J@i?lzc'v(W8m׷}~KZ~M? '@b jnCZ ~\sQ~5XVԆlqdƄWܑr -iD27(WK1,Wp+|ʼn<oHʠX`ݴފehJ*0w]ȝ͵gCOY@ϱv3%3!@QbTM@b)q٨S<Z7LcWFq IL=tE!֏j:-,-?|e`CO2~1N8XNЦ5`ZUMqwA"gǝ#D}d7mQ(H~D ?PP ѥ4[ўoAG(H-=cK}~b57+$ rn}20y.!(l'q4f0SqA
+r
+* ҒZccD29 6]n6ɿT3|K:`"ClLn7p호lp)E5aODA:7(Bz8yn_{&fTVv ] Hl/
+SAMLVW+FK<OSĿuX>Rb3>f7g.R'Rɸ{7ƕ\FKCO!ꎮ[4 LQ@`>y:
+S ЃLEPCtBs0ޯ R!>[.GqĒO]=C}!O \ [ftnDc!W#JiK/;?>Q .I uz̺4r"ΐvyƞg̬' >3
+]JzL&g❓ Ur3'bhx#X+K&j+z7ܢwk( >2١+Z
+k+%+h6g
+L7qeYgu 8X@5xctׇ
+c= "\A~L'a3ӥAz1-b=fQ~B,"p~rLvKjL" Mnku˄KtsKv!/h7Ewv+k;p+HcS ;8s*L5%/[]>xc^%M
+^c<ăSjVj&*,f+* 2-*쳗Gt/;ufw 5l8}C۶gಧfWkW=>XL{L(-g3:9I4c_CWK@5L˽daGQ* B<Bj|F`uTlpa}3 WJ_ea2r^3LHlWHOIRy}W]w2Xd&$t<j~f+Q8ALhU+'}š4Hp;(n9深!S
+}!\ wI Thz|sFE
+eBқ#"Ê%ۄȐoH&n\껼>)Y=+F&X|q(ڔQ_"S!Z;AK.;&߰7tkn
+]G3*y[G%|;>5Bd!_:|rjZӈ10w] Io]*ȎDߪn fk)"\.hcifȫ)؇;§V.0Pٝ
+ZO∧!:by;沽~~M?h9Otiax|jLsF/)x<Nim}O/VtL 3Α\L޳4DGIco@%@+[3+ )Dκt8w$ FuW~ʝz闉,c;6T&>0!XNܥ0Z&(.ܖj}vun:nSM6}qH,S ʑ0c=cqHry].;Uf$֨.㷞DY:B3*8RVk@(pAik8mkEH[|ZW7v\^e. a]Qgi!gƤݶRq#s: 6bg҅=~v)wýHI@:G籆gq8XnV[csVM
+Y҄027xøaz3fJNt>T%ąͰFtI@Wu>ꝺ$&,||FG€DNWqAmT?b
+
+3EMSոp/IY*l~t:t|Ki6)4"1_>~I'oo|w֍Wہ'EEܹ"Z*hg&^;qt/G|#ާ3IB-2,}RLa7 SVLDJ<M1(Ӈjt#ӌTsylͺUPha@Fv|?~ϑtܼtqNV.(sE817t d_̃$\u*5{2INdt
+3m|tk뇢7_QR9ϧ?+JM5|Q@Z :;aSa<J!~ᵅ^
+$/ qe-UZ)R (<Fog0_D\@^M]HTŗZ sR86xJ@g8kjRc-\bvX9؟ߎѦU^K^g5?ղ`uK?eڵbV#q}㣰ZZ_ 705N:!.ixh/
+{/h'R X3'X$J搒Wږq_5!U1 kx!(\th/Lb|5!!=7er8^ݞEB6Qbo?E]vm[³J?f]
+:љ:L GGXF|9j_a@wȮN+Njcc^ju庚:iVW5\:I>X>н7zPH%!zo业b`Z6Gba~Ih;ʡCâL??k^0}>E?_ab/KKGWx5V5 ewQa ͹4*3!Ǫ}),}=f :m }f#[6:6)} ֺĞ8~HG$K|=·Y(s@?/%;|KFȳZc|Bɧs'=Z9\6v݂\x!0>L8[Jܩ:ςV.a(GkEaN&U"3V'+,O*4,r \ozp<\0]!*'uܮbw"SPìUOBkPhn=$֚shU"n˒b(p ya/LQU)鎳>{&!耎>H´RuPҭb{}(6iX$Q
+$k1k̑a˕bt:x+ żqz3{wb?{Nų&%=\4?kPl|򬿿PX[$ŤVlaZ׍Z9F* Ce䳝V19 JMQ`ar=MKDhXs4w_jet7-&h~H5\=XT⠁~( ^TϜ# loy~u$H{ \N&Md*şgi
+m0=Иo"WxhJOLIe!{ؖRс
+ZK8sq넉+Qb[ )dA7TNw(IVd4Z;K g=;%+hJ'(w7w.$3!khs-@,Z~? |w1`טV6ˈ7 &":2frO\7wJ"|/e^m=h2p]%zcS6i_˶=Y"֜ڠ+ݬ#Y"rKK[v*3>Q0Xe k\*Sn 7kO3R*nZ&T2bU"! cIG)SD^UKm糶 :^f/W`4[ I<KKFkHPKa'ԉb,LXLGylv>|ThSp֊ȵ+1'qReoPSӬ<RZ l[:zfyq2&e>åYehiyW!@X=.E3$7S9Ϝǯ/#Hf#}?N~E OA֎RL#
+2[[(ʉNt
+R~4ݔY140BR?ⴳ=Σ^i~ t=,*. !YhJS$ ."°U-ayfor"rSK- 6/YS: CLx5leAD2!C8oCGooܽY{[(Ĉ!>=G>?l"Y;ɢ$T4Ały]M~twuc8ה"ܧNK^SPǻQĶI)Q+,rd #NGV֊SJ&G#W2w|{*n 4}sk={[t9ܜ)MPIB1
+\,D;* e; .J:f[. ^]Xf<z*vy1X~]rAu5Յy_!eMDŽ25>NˣLz7jEJ
+ZgSg*oeݾCa  *]_BLleF hiϙؗӐ<n87'ZRϙFٍbE\C8
+:-ta܊؅ yӉ, */W|#Q#R6 i8ᆣUe>M`I)# SP?_ݷB5vn
+P.UWL3:A-]:qZ5At݀}y;W_ا tu[&5!Z&wvI .H)LD~v+*Tu}$0ɳR܅
+:URTz;
+7
+ )!
+ 1KL{ 5
+xwpf{m $zS*bV4Ix9o Y9H
++A<_EvѱHϡ!ƌM}5s+5ǼY9bY;z>wLeYSJ~]c؛zҋt(rr64!%$4T;ރd¢*7B-?N-|!5GMv[D#ٙ[H^4nQ0Cw
+,e!J(ҁ_kGˉ@ßK%\\}SMei]D3M Zt 8w\ߛi3B.<
+Ϩh
+
+9p
+[_(t'Ix19Bѝ\($.z q6n'X̂^'?!rT98\V53|sX%zMzϫ #vpyhj_v.M&nv| Tlʬ`lx(8\U[i|jD,;s9~3_*'gCfjRHMg(UY!{܌mײh`0Oe}yGh4]ҁ6@?6D9'\!y.{妘}fkHcIVտU%8Q||Z7jww|hI4r ^N.=
+x2MҨru2%r &c2Gol#d')7l9 d(.n֘YLa+yUlHX9')mF?H>' ǣybS;FR"y4seUO~J`?aHR!_; =a%0Uq˨J";_ni*ƛط#4 e>? vbtmb KdV7j K;|z!|c$SŊ`GfۿeYou- su"=AUګ"HA$>#j)pD[ċD 1
+l7j ;ŗZ ŘR67y(t|P
+=} fJ崢PHb,1'TwUQXZQ˘fl=+'fU햹54["Qu0*r_[9{X*ʉpTsٟ1c8jRR܋vP77Cѽ'cDT> d,s͍,hw}/q\j3w|qS$n@/'70} NZd&\9B8}R;J<|_}!r4 5`J䃾 wS ;˛O\yPlOgNOcuDimD,/Oq~`,7!dǜͽI6y[L#yZuu *Hc"Pnw"mڴ+ >V@ߢUUih^<ac#hؔz/ׁNO
+[X*kh 'VF`q~)~@U Uҳ
+j*ŀl≤%
+MsJt*z"saXLbq6敱%"T#)w OGeUNaBuݘMNP {:ϯ>"aOxEg/ǿ^MD}ORzdI
+3iP"S=+g3I%6vsJ/p?E<ZNu/Hx$?_6w-ϤH}:z)/*R[}ol[R,}փ!41۶ߌ?$(&b?ո.bfu
+’r2Qr$WXg<cD!<o2WO(4W3j:kW"/Ak;h`d\\g?ˬIUx1i1hΐ5hE:m?L;3xB~rd:
+Ko G7E ͋:o3|2
+-v.ۻʦ+4cm۱ϥ EV (8t59YHv\Q!T<c%CfJ8~oҰ7:_8C$\H|36t\eIJtr8olmCѴl]"j3ݻo&/qROjQCvYB)r Iip9Ps󍽉NgIi}Ի@DK`zkw
+NʖVPt^ǖ.=+zCYM&,]eO"/Ⱦ}Fc2=,(qN+Xǐj|3Y ULНg.X_S=C==ɤ$W%2t#V-9
+Bvz~hA'RnH:,ָ^h3pLUb{a~t-_u=]q"IPF匿6<,}
+a֥mx)a<X-0eJ0F6j5R1b'YJ}*\;}JYD`v}W{_ZMo
+;3u?_Q(t:0qaeFz18)yC9䯽ԡ$.]or#*ѱ(] ZBZ)ʭI&'h&CS#FkQAˋ,pH$h WV׶y??
++W"
+$cX(:|wc[ji(uvS=6`p
+rGl'
+Mk|<k9DF[s^FittXxȸrdXEcP;o$
+dм؞"FaVE?&A
+ʈOX&^z\uʚ-jTr\7.Ns8 cE<gNՙQ6F75ӫ,x ֙N@CQ: Qf}/")l1 IA5 vɓZ2aTwS}K-Dx!S2H$埊+Ǵ"X.j.z /LjCFfXz.
+endobj
+790 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 2
+/LastChar 250
+/Widths 1501 0 R
+/BaseFont /SKDWMR+NimbusRomNo9L-Medi
+/FontDescriptor 788 0 R
+>> endobj
+788 0 obj <<
+/Ascent 690
+/CapHeight 690
+/Descent -209
+/FontName /SKDWMR+NimbusRomNo9L-Medi
+/ItalicAngle 0
+/StemV 140
+/XHeight 461
+/FontBBox [-168 -341 1000 960]
+/Flags 4
+/CharSet (/fi/fl/quoteright/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/question/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/Q/R/S/T/U/V/W/X/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/questiondown/Iacute/aacute/eacute/iacute/ntilde/oacute/uacute)
+/FontFile 789 0 R
+>> endobj
+1501 0 obj
+[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 333 333 0 0 250 333 250 278 500 500 500 500 500 500 500 500 500 500 333 0 0 0 0 500 0 722 667 722 722 667 611 778 778 389 500 0 667 944 722 778 611 778 722 556 667 722 722 1000 722 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 556 278 333 556 278 833 556 500 556 556 444 389 333 556 500 722 500 500 444 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 0 0 0 0 0 0 0 0 0 0 0 0 0 389 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 0 0 0 0 0 0 0 444 0 0 0 278 0 0 0 556 0 500 0 0 0 0 0 0 556 ]
+endobj
+786 0 obj <<
+/Length1 1199
+/Length2 2549
+/Length3 544
+/Length 3348
+/Filter /FlateDecode
+>>
+stream
+xWW\Sٷ)J(Dp
+><o~+
+ط1:PG0'AppȾaK"}VE
+1$TV&* +lz˖یor/޿D ~
+2V%jqwεIG93:Lc\ /x~B2;cRMX͋;+ 1x玴利䐭諵UύѶŞS$`|3
+W#y:<"= {\GÂE'^(Cyq&$wDs…dWH[jag_B-(?NrtS19i'D_L|;m h÷O2mZ)R88ae3pP{v튴Z^ywTXQ]7ntv//+~*ʾl+.wQH7,>%3}<nFqCcl39q-cV'OKccĄAYrIpFT 2Mwd;ܚ{
++ z5З7\*M%w(?rB{6KG
+A4u]rMVh|V_`Z՚,wʖ;tWԶ-_RhQ:(@M>R߃m^UsKEyl. v&ht9/`P荨g=0.V3[tjzkr12QUVoYR=;&.okI/.푐 }'EFU\)kOm=lb4ާhxrx;"< 1-]N_RâY)WQdY*5ڦɰS/j &Oۗ6?8֚|y}PF7Us~aszN&hʶduuMG?H(tzVj0}VVIU&m$pt|ݟ "m_<)ae\Ma$,/y"1*!!=K.*B7,su_87Vj31XU/f&@}SHWpz\~Ysb=mJ3KHKCNmI^-*vNcM1,m-X k,؏o2\
+qb\ٍk|Ѧ1ܶd7K}R _2 SfN7+B|3!i,=AGi 
+!&jjs{{*>6*ߗ}6A!Ϊ!Aa mׅ>{D ֛J?:v/{ёxEEvNCIz3\9G{T¤ܝ bo`JL1A""m]{.kݷ'o&L;byB<UxOe~65֓a_5iAuȼS\܏.
+ws@ 4}
+K]¹.37N,U:x[IK."۱@K|v Xi+f}}2- j S.kgr2V~sF--'1n&LFlXTUT=dj0dPd30c,jO7YHeMyAtqZy), A_$uw0c\O?)J ?}G/&;WdgTe]3ChfңcyqWj<*lç ~67X\
+yM 3K9OL7clT<]XFK˵t% CRl޺EwbKoH?rW`X*cI=-*/u,4Sn? , P/ ,$
+Ҙ?ڻ
+endobj
+787 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 101
+/LastChar 118
+/Widths 1502 0 R
+/BaseFont /YCPTHY+NimbusSanL-ReguItal
+/FontDescriptor 785 0 R
+>> endobj
+785 0 obj <<
+/Ascent 712
+/CapHeight 712
+/Descent -213
+/FontName /YCPTHY+NimbusSanL-ReguItal
+/ItalicAngle -12
+/StemV 88
+/XHeight 523
+/FontBBox [-178 -284 1108 953]
+/Flags 4
+/CharSet (/e/i/o/p/r/t/v)
+/FontFile 786 0 R
+>> endobj
+1502 0 obj
+[556 0 0 0 222 0 0 0 0 0 556 556 0 333 0 278 0 500 ]
+endobj
+783 0 obj <<
+/Length1 1630
+/Length2 20395
+/Length3 532
+/Length 21288
+/Filter /FlateDecode
+>>
+stream
+xڬctf]&vX6+N*Nv*تبضm۶}zc5q5$J*&vF@ ;[gzf&2WGA!4t3t
+:vT@5 % TPHm
+6;wEcm1?ygk ?I;m_j-pp(Y8L _r5[-/j+?T-l!*/]ʟQJC[R\X2T;Ϊsۙ?0""v
+_b2[U3TCBe1<%D46ՕFJ@CeƑ<1ƐxX(' OnPxK!9LrȚAHh#2mNtod'0\C#g.d s
+i:bQ g<zB Bw{(̭PtOº!~N=a)gEVߥ@tG{J-mKd .B8!Í vXن"+Y#jadyQ 9.L9Hi<n{$H:ZM9.'nbT̵ PšM]#1&umD
+JgQ:4)V^cxpI顓`t<g=qH+`8(aAuZ+ћGyy`?-(|(cpm(U\x% Ҫe̍{TYK~ EZ1COh_9Dxu9[a:aN4\
+;Jp8aZxIl( -eIpfuuc#TT$[}te#3R(̌
+:X& (v_IK?1~fc5RIA`Ҥ Pf٦QM9CLvCG8EQ.M̡]K& f!~[ ,<r]CHpbsMǵtjcb<!Rwoŋ)y%dŴ/aH>.D>bˀffo%]ES24m&-ʹf_;^'MHm|Fֻ.7JA%{->7i\̀!;yC.klaKXJrCh~N-.Yy'dJnrPr&@Y#ܥ2RؕYjv5)%8S\ϔ7Oe'Dk <Q˕+tAW)=pвI {m4uBNm;*,kvKnO81wv?5j QN-'٣!En\bhE#@ 99y&+
+}tqc |86j(^ǎ]sZe6%I MW:
+
+J rSq# H+ϐC1Ur\x`V'Ҹm%j̒Hҩ)ttj}XJKE9#pmzo/#
+"t0KIr>x&hV|+8X7I0-+VX7Qc6Uj(V70 m|~ r1Qf^8sJ/|pMP@a+D=8>mF_5Sw^
+{{2Ae &]B0Cٛ_q<}4+@+C#*"Ƞw&HyRG2Iۓ3g=z }-B"ye0 6C8+ %aǩAJ)Ք=1+?k\goB#
+3v|9MDUݠyydˁWg9aInx<㟯qp'?<2jv1hw÷R*<6_Icor'{CB|fOtk74+<!VҿEl G~YJ& VEeCpaX]-*~:- 2"B<A)!9";DoP Ⅶw }#E>my%LBa #hvE`rY@)qUH3c{I4/
+&+;,q Zbx4|% J6 _-֏~ۥIJ2:kd<4چTsVy;Ęs ].uZ.+wbIIEKn8 I#{(I.iߢrתWKTFQ!<-Kd (tċe`RiŖeGa(*˼e
+WvPPGN;LY@eUb~\upٚ LmwU咄S+:1qV])f j,k"ܖƊ]*J^3r/Ԛw}f> :Ci7XRd* 喊Sg'4R;pRC9±2%@?=u^Mf߆H1~KPn~ƣ O|e&OQ<䶶YR|$XR<K-2OKҮkGp!-XI_exK+102õ#g6-bhuQr՝zF8 h4
+S۝zJsir 8M14JH3E-#'n otHDMiCQ*X1O1d/}c~˭PwK <'0dg-y+Yp4 Qz˳R_X!H+IS= c3g|5a
+7Ki[o7lA\"X߇ǿV|Cb2#ZCQYl;oU;le"{.˺:~9P
+6?{X^/\{0Y^?* jq$ vG`D8‘;溭˭] ^2citGӫ} yc$~jS0iVO^番bv&͎.^ɂY}plh'B򉑮E]+Qz9+|?P;x:f~b+b
+Rp9"nǀR鿡EV99Ѳ}0 't_372kyQH*FkQ([DW{k&YJn2\;S'2}m{r +po#ry%bQ22%M$lҿަv/*o[T] U%,\q^lGfsε"^̰%>[8K~WxU; 7*I-R>UQ##E=LˉGo:-xt&<n2W4-·-,n/R#?U
+PEY  5˔hRIgF*[۟M[!, 1 <W 4''1?;WqǙ?DE /D@om3Jiu/J&^oH;fwAJRw]w˦z7d"(#1U) t7i}Ap=jRڷ,-"zUp$[2^[ijIѷ.S.ߝJ34Wu"w[J7㶪r43KiD8d#7
+ھ۔5SjNNL߯?GEvS*J;O5:0b$?v=rF:(yd DTkb'vF!gNjG FP}Qٓu{k4|>rڨܹﳋD+c@`kǵ^I*1Ʃ
+R]uX yr(rya*o|kU?zX08ghl,̄‘t21|p dͫձ?R0$pL Mۦ(>wCYojb
+?-24* ;Z|\k#* uݤa6W,B-u+"Oâ bIXqy;xwfÒ7~|Gǩe<fݕgA_=<PѴ'ed aϠ3Ufpf%fW6-cg=Ah Zټ,0nCe">T+D@J3 蚀zx:Z/lfQ?\f,4j"uv&KaxsQzQJE<t*f>=3@T\qY b
+
+11*"q +_FA"g΍v'l6삩T.f4< jT+mn6"@2v M[(8H@xen7U*_Qp$<H*[t Pmzʼn⥻Wd@׋ R+S`%8
+c5I~hZtWdȲ񭡣 mN8%L C,8sgy#v">F=cQʼ@[g3440EC3FMTU:?j8'/T,3(ɭYDSYB=] gW}q[U{k׌ˇ9hb]Ewr|Vh0 D;(+j,%eei1΃Z^m$/+ow!.w}nɟ9x#.bqBfRk]Rt]K<`޾#,Ȫ&mz1|!9DTo ^`u,`9=F?"/Mm+
+,So]J2--{=b(O߿ xQ*6qbS)rV!E}x|ύڒ9$'o'>GdWGdŠ[hjBܛrn(4QE‚) XpŰ3+-Hsq rBT~{S$,W
+7.̞
+r볇'
+dtpTT%6͔ϔ?TK6R+#qduFZaNJ";as5(SZ'WoT-qj)LĘɾk僇R
+olF( ؕ6T*Cz1$L?m
+M|膁hYkɮzK:y4c*ovjRf2ۻ_XAH(C?r'7 ,}9˗&HsC[,c:=cºlOfTxt;64j|NT?0؋Td*=xrQfAI:#AU(U93p Q
+a<Xz%h%v˞FKw Mcݣ,~.m\bzWLf޷t6yq`|}%&tLb<iYwZ~r19//a7C0 qg}f޳#퇂pXruMT   h
+sCgş2`ZCo!{%HtAx )|ZXhf jp;}3@ņCڤ#C5
+$o
+n wf XbH2aSoc* ޽UW=;"oiQsh '2 xW/[ۗL9_/Ĵ`RƁCr?6N
+Ϡގ~ivɌi`Y]*TQ{ Ё77ц'̕k,.~r9’⒮_ejBWnPB9 GVڤB%Z+ma-(w :Ac';zҁ6KX9QW/VcχRVؿYFa{׹dItr~1Z&\J8cҀKPx`fKԫ ɤ$'\/Gyܵ ǩ/MP8
+-0:r|a艱(v+6>H<?8 ':G
+$)htJ}t3_1k3db*Ay٤RAp'mh4npXCKB貋E7ĆQVYrM턍儂2R3Z f 7jIat&C|=SᛳyQNr NLk%VDZLS1{HfwMZ3p4a_-h*CkZ1Dbh﨎TȨ@5gn6"bzc,h`ιe!Hs
+I _=% l؂o.=`Ed ,$Iؐ^:VlU}
+o|$Fֵ|ꜷM' ]}g^3U[nY?K%wEl<X 'dfjZ}2[UawTV;b'Rs}z7M|I 7?:&Kg~̗iΗueG=' !vRKm2v_ꉫI:RܯiL$l_oma*dł-|/- &ON 5N,Ԟm KCY(Wy~r! N+֩,b;P9E2 c\W!g(\¼uwM?>lvDQ&R81͡B%Q";o R*"p%u!k[L5oDp`M!+u'UHk^DpR~pPsz;ZQ* j:V8r
+'Zۋ=,^g}Si%܍L^ eYհ|&□1.rAPq(叼2`0+ lFҥa̮hnn@HXtCYPԷ,7?]q~e#<7I3&9rULA<fl3%z{:{˭xby
+lt^,!V_S=(.=RI=%O1a)~.Ybvx-ip*E VjǛ 7D^c!<x'^b+}< Δ8E/IWrk$dś\խ*93 =$|<QN}q v U@p3MOrU%xm\0V9+vj1σ'ҪCpU\oY)Zum&rב}lP{"L p._PM>kU <dn~h-#@]yB]N'̲O-.(r||U,[!VkqAM;{I7S3G>1aD|PȔ*r8o85ikR t{\Ԛ
+6 SYe'aZ=RE0l`HZm`D:op)qw_T6In@0hIh 6Ap|ZPk*Ʈ) /JV z^6[bXZidf O/é/@DWdYJiEx1([z{jܠ+Nt
+zAIcNsW{\\?QmC`S%{HǍ5ן^G4n><nCȧaCs٭wk
+sьřy>T5dnE}|R݅4"J-g~wӠH2~6(UӫI?ȶtF7]q.Wn$"dlf5Ӂ<c&\׉H]ܤq^fcG=?Z<4x|\޹*
+S9GnY_]6(r# OiAh= ㋾±^fCM `_eT7,}8'\v'^:ȯ;iTݵ8Wк؜Y(;TT`d[K"fW,'=9cYMT`s$K",^dꡲe8 MX&70mfs-W)Rڕ#hEG
+c_yިFH]]}jn<xok4
+Z۷(_5}H:2k ,.4әB-XG[ g+">*l {&"CVH%M|Tc^K:טb7)CxHq#(|7sS25I?f@s!XҿT&G&ZIP
+}ܟ*2%AJаqW?f7A!zKywWY -lV`b`\,^7#Rӳ+iIN[M*mc>ͺΆUnLQshUZe|TDm{\
+h(WXd~@Y<}H}v,8Y?\aiӎr P5bapv.Dvnuχ '|j -QN-ZRMFYiKN@ZF,-Y͌J{OG7Z5~B
+S!ƃ*
+J׷hfy-b^YfL a|baHR!2=n5\X3i ga_;,B\`[l=vss.9v:Mp w.z! t4tU' YVsIe%V]K/Ta(&-9^TaZm
+q%iƜE8*wLGZ#ʟD }FF.ʟ ȱNG?-Ɏ[g"]V(q@ǷK>O}Cq;yXA0AUu:-?G{tBN K[BBڟ/cS *rX؊KHcSkF> ˆ4,ǎΠġfIyZCavONݙ$`mFcffD% ֪yqCSZ \BiuOwL%jk.oX^};vTѝm }AUT&#ltrdwseh w4^[ WF8EލK6$bZ
+m'B 8 MRMb;syTU ^}l7oWαc5iHn+*{kKyQ)] cR9W6wA­o5rӻg% Fo)"&PYF0K,MCo , pRzdSxKynsќ{ܝs(0InJKnrϢJ8O[7u~`66T.n@+?kdZd:fw|<Pee^YD4,Щ)>G!-h=OdbtСjGa&'Y<Up{Li h|CRHs-}ߗGU92v5R\<Ii aj#cuH GAz {Q.:Iε^u+P!0+ T˙Nدg':+:I%>itkER0{J+saU6Լ[y 0N_O5JmYFk+e7ུI^vtLOM ۬^;(f4
+[ DMb4)_,ɀM OS9\\Z['>mX*@Ja@Iڈs0/lS[VZ&F[usq1ҥoh]2ok E1
+0#
+=0 Fv {su/ XQU$[3^/8G!T]|ʗOqRۼg7 Pg\8Yu]M~6xmPjɞߙ~-$[ .q"y}WMBlT =<5-Ww87` W1IfO.-IWvuN',#
+qL7slzBK"əe`2&^La
+|nOp~١ JgVC&S.F (ZU.z(P#Cޜڨ(vD;%9P@*an0U
+9M|29 `ϢFO AIkW|4:ղ΁ψeQ=ρ&)*Gݮ Gl߰۽#?I!ECɆAOS.q¢FÎ @Aw
+D(QS׬
+&Rf-ek┭ |]p6ī<I\镫G "s3$etl3heQ\-bHh6MQ^5 Q RCE3,|c8|B_¸ P"R#cGHo"N+Wo4yGYm}:˳.L[GTfNoMl1-OT{a~'Ba,΂E/.8n͂`U wft3}}e ɗq,}s%u ~Nk>!'v2uxܺA"7>S4!wGp"xA.-FN;Dž}җbWy0dZ['Icn2N&VKo<DafT%EPwW>DB[<؎nusv.;\ĝ9^q<BGM<KA]W l'^20OOn eJJk2;CS㒤QVAyR߈Jȧp l.F<~w .2dIkgac=2[0W(S\ k!"%eow^?GA]*b
+h~@ez@EeNq`w
+2=rD`K?Jp"jDf3-kpO76nI펴ܧC2o)y[$Ae%#m6FGJ ԪqY;J~<;xϛާc}f-Rw`Sau)y RjSaԣ̴M"dv'l/?UN)3<,j@Z񁪜`9hoFR|2'U،&|l:C 10 P@
+?OA={5_q}
+I=J6hՇS#Ջin,@ :Q\; Wm_@s$ HU~|P <L6BZ%@` 
+) !d9IaC[3`翣{4q^5H,o^ !\|/Y.D.nAb'0BjEl]nkFz}2j( TQ9Ӽ},sy'䣖z <w<W2ĦllBfN]ė. a>|9c-j.q0hd|D l^ET%a|D14AպuZ^3F$8_,`[v. w6By=S\s
+Ld^X35RcjznmX+0N
+||:3
+&kI2M<f
+b❨7̊s+N|횋<Xg6d#gE z(-Q--l:r ?Ju'VpX5ƴAs F25y;gUyf̖/>lR'5xŻlOޚRQ>gȀO-OY`k2t,˴sq,|B@!SN&o%"|Hy3"cU[8snR-ߎh-jv ނg*^pFԖf)?{ ::G`Bvz:rD<W1TR­W)v!ŕ{qΊ2 2t󱺹,﹮&$-Ţsv0`qP7]'})`/Қ6o ,{/t9`!]eD$|X*@YU]6YyK9 8&㌓J1#52+`
+M/5c8D}a+0{; SuRM7ؖ 2СP{(k@LHnz3 Qolﺞp~Rs{5 %7 vXDY檇kVkU&ߝcoS e[pAYƸ:޵=B<(_j{>̄}ƠϘŒ(f䇙2NC)G ?c{GR[HBGƌ!Ѳ--/>hU
+endobj
+784 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 2
+/LastChar 250
+/Widths 1503 0 R
+/BaseFont /HWZGED+NimbusRomNo9L-Regu
+/FontDescriptor 782 0 R
+>> endobj
+782 0 obj <<
+/Ascent 678
+/CapHeight 651
+/Descent -216
+/FontName /HWZGED+NimbusRomNo9L-Regu
+/ItalicAngle 0
+/StemV 85
+/XHeight 450
+/FontBBox [-168 -281 1000 924]
+/Flags 4
+/CharSet (/fi/fl/exclam/quotedbl/numbersign/percent/quoteright/parenleft/parenright/asterisk/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/tilde/exclamdown/questiondown/Eacute/Iacute/Ntilde/Oacute/Uacute/aacute/eacute/iacute/ntilde/oacute/uacute)
+/FontFile 783 0 R
+>> endobj
+1503 0 obj
+[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 500 0 833 0 333 333 333 500 0 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 0 564 0 444 0 722 667 667 722 611 556 722 722 333 389 722 611 889 722 722 556 722 667 556 611 722 722 944 722 722 611 333 0 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 0 333 0 0 0 0 0 0 0 0 333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 0 0 611 0 0 0 333 0 0 0 722 0 722 0 0 0 0 0 0 722 0 0 0 0 0 0 444 0 0 0 0 0 0 0 444 0 0 0 278 0 0 0 500 0 500 0 0 0 0 0 0 500 ]
+endobj
+780 0 obj <<
+/Length1 1166
+/Length2 7917
+/Length3 544
+/Length 8731
+/Filter /FlateDecode
+>>
+stream
+xzUX-PCwww/VH $+Ž8(n-PܝBeܳϹO~7y59Xs= gȣ
+%zp+F. pCnn.0
+ll g {5'
+(qF)*$yĄ<"(!"wzz@/I = v|%O00
+F O
+ -
+@
+v8s0;NnxƄzD{ DnuP8~w%7([iHjXJb;/&1I(1z$!o$)U[=%>ksYQb0K]w] j
+l9 Ǻ.3N᩸lI*ډ_*⋼ SA֞RXjzЭ@DSms qqbs FhG\x21eǁJi&R΅>\c'M*fgz4=I괍@16Pf}u#ߍM7zV -? ;zD]|bIքnpZzT\f |8Kز̨lcDVxWvZH5j[!w T_8/p&1Qt7PzpH_Z
+r  }VFBnF,
+\'i
+/KwMx{^ucDל,6!3cc"-BH-]
+ n w]Nw^ȷ#~O5y}]iʖՊo4j>u'C=z /
+k#WN݃ [L+6zfH&VRkZkQdT3: ?+E[\ĥs%]I
+_Xlh%)~
+tw<|&KҴFI1I+^B[˷
+Y")</}jO-ń/ǰ7YOh-5oiEмfO72rWWGD'Ž!O&y`DYGKZM۹o\픨k#~J'۾~;)Toӈ#;p~&@zuk@]j^^V)rNO:&S fEtRbO I- =oSZHR8QTԝKIzoY@`sZ:  k4AOboZ/:1*C\ɂ=Sy(n?
+b_z;}JA5m
+ɉ~ o]/vdlYxfGV#6n4+B36aAEW+l%^O:g:i1[>K
+\҉'!`~VA(K'l.GOW.,I7'KJ,4|l~l
+sNGwnߐ$[/vHJ}Vr)8c~!ֆE|'nӗK i8W\Xt.-odb_a},~l)O<d^K$j^<]2P^R0:^(_^e
+|W]!ȸM98YTҵ'GFJ#ҹ皹SEg5 :%"+
+6 n+~q$Rھi}_M5rF]H.rটFR*d眲eӓĆӦoalznqƼ4Ï{S'v=!n[^#~fl)<%&9Wx ujoM}9j٩j>JyG
+oMSfj|OIfG; M>z5mbLL>Ǖw>GvL.;bl[f`pt:tDzg=?T13?R]jbO
+tXPjcGCb*"aaj{ XVhmv1rW: eE86hHlTƸ)"#dSظ^ Q8.fĆ8Ծ'~e[*̽ûXr{ab|P!ndG@h=@RPT¼>.`* 0e5_z R =USϴIq-|5c$Ŏ:ǿo~) w8œU=J&-MWkv܁:yX̴HxM9E-GJl'NDm&[2WMJHP%D?v u)/K>~lyCq.9`MG0ݡT%G(Pycʎ9҆/#ұ6yΌIݾ/Ŧ'2AP#-sr!Lvj 5+YP@^ڊToTi5tM/u_vb:M c{w'rK[tu=dđ3q '_7s_rf%Zozw*?q޹M5[<nEQmޑP~b3Ypn=G,4[4X.#-BU$B`|; :&W1kߜh]XjPvd) dD|q'
+7NSKFh﨟^.nᧉU&Si)~=GD`LWP%:19Ճu,L#Qt!D?Orɟrr(Ҵ}iwj_jʵ$ 2VG5Hc\XyWU4%mXzm= ċ0}Rn$ )הhXvz6.WCe)6
+3oXQF쿨-4#evgnUVeqXUy6:cɅ=)R콗ޜuMڎ8k+O"&4(7jڡ 6&W̙z_|wõ=A!! cV^R.WmRen 4EclUFTEuÇCƗ*Od990u@dxM-|[54V/=kG}lM}2ebnz!^9BbN|B#Mؐk$&,%o= cf}HZ!W]rhڏO#JN;zaDI-*jKRj%ɒՖ[] o>J
+B_ﳺuna:WfvAniYCvKy^*qw_ OCkRL]aJ`/d`b9e,23@;3?XO>jb"BC{ IWl
+U&
++`eS,+]2*Tak˲Ŋ㽑^u:j1Ɨ.UVV)@ʑ䵵"HK&A+ww54
+asK
+ITT? Tg&UlSV
+ ќ 2A_eR\}3S 5L@ z7 {^~NSS:@ȵ77DqЂ~K.<ۈ{\
+vopA3[Aum?Mw2 jr>][iϗ`6Х0ɛ
+-*p]yJ0
+x/&廃e#_*ЗjjеCr-Hءې'ScT}abf
+*6fߴOkN_ws5Nz~e=~2\NGm;^fN;w$oH=t4"\m ͵sh=X;|.0jp!ǎ#Yu}O/@-qS Q煴] :>^X}[o`J7t쐨FrXNgGZAٻrlλz {D)W6b{+Ei3L:' Kc\N-Oعp$wH/0:Kendstream
+endobj
+781 0 obj <<
+/Type /Font
+/Subtype /Type1
+/Encoding 1490 0 R
+/FirstChar 2
+/LastChar 250
+/Widths 1504 0 R
+/BaseFont /TRECTP+NimbusSanL-Regu
+/FontDescriptor 779 0 R
+>> endobj
+779 0 obj <<
+/Ascent 712
+/CapHeight 712
+/Descent -213
+/FontName /TRECTP+NimbusSanL-Regu
+/ItalicAngle 0
+/StemV 85
+/XHeight 523
+/FontBBox [-174 -285 1001 953]
+/Flags 4
+/CharSet (/fi/comma/period/slash/A/C/E/F/L/P/Q/S/T/X/a/b/c/d/e/f/g/h/i/l/m/n/o/p/q/r/s/t/u/v/y/z/aacute/oacute/uacute)
+/FontFile 780 0 R
+>> endobj
+1504 0 obj
+[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 278 278 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 667 0 722 0 667 611 0 0 0 0 0 556 0 0 0 667 778 0 667 611 0 0 0 667 0 0 0 0 0 0 0 0 556 556 500 556 556 278 556 556 222 0 0 222 833 556 556 556 556 333 500 278 556 500 0 0 500 500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 556 0 0 0 0 0 0 556 ]
+endobj
+821 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [774 0 R 823 0 R 870 0 R 910 0 R 951 0 R 993 0 R]
+>> endobj
+1032 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [1028 0 R 1034 0 R 1041 0 R 1047 0 R 1053 0 R 1064 0 R]
+>> endobj
+1087 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [1078 0 R 1089 0 R 1098 0 R 1103 0 R 1116 0 R 1125 0 R]
+>> endobj
+1143 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [1136 0 R 1145 0 R 1159 0 R 1168 0 R 1177 0 R 1182 0 R]
+>> endobj
+1194 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [1189 0 R 1196 0 R 1202 0 R 1208 0 R 1212 0 R 1216 0 R]
+>> endobj
+1230 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1505 0 R
+/Kids [1220 0 R 1232 0 R 1237 0 R 1244 0 R 1253 0 R 1258 0 R]
+>> endobj
+1268 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1263 0 R 1270 0 R 1274 0 R 1279 0 R 1285 0 R 1289 0 R]
+>> endobj
+1298 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1295 0 R 1300 0 R 1304 0 R 1312 0 R 1316 0 R 1320 0 R]
+>> endobj
+1333 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1327 0 R 1335 0 R 1343 0 R 1349 0 R 1353 0 R 1357 0 R]
+>> endobj
+1369 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1361 0 R 1371 0 R 1386 0 R 1390 0 R 1394 0 R 1398 0 R]
+>> endobj
+1412 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1402 0 R 1414 0 R 1422 0 R 1426 0 R 1430 0 R 1434 0 R]
+>> endobj
+1447 0 obj <<
+/Type /Pages
+/Count 6
+/Parent 1506 0 R
+/Kids [1438 0 R 1449 0 R 1454 0 R 1463 0 R 1471 0 R 1479 0 R]
+>> endobj
+1505 0 obj <<
+/Type /Pages
+/Count 36
+/Parent 1507 0 R
+/Kids [821 0 R 1032 0 R 1087 0 R 1143 0 R 1194 0 R 1230 0 R]
+>> endobj
+1506 0 obj <<
+/Type /Pages
+/Count 36
+/Parent 1507 0 R
+/Kids [1268 0 R 1298 0 R 1333 0 R 1369 0 R 1412 0 R 1447 0 R]
+>> endobj
+1507 0 obj <<
+/Type /Pages
+/Count 72
+/Kids [1505 0 R 1506 0 R]
+>> endobj
+1508 0 obj <<
+/Type /Outlines
+/First 7 0 R
+/Last 751 0 R
+/Count 12
+>> endobj
+771 0 obj <<
+/Title 772 0 R
+/A 769 0 R
+/Parent 751 0 R
+/Prev 767 0 R
+>> endobj
+767 0 obj <<
+/Title 768 0 R
+/A 765 0 R
+/Parent 751 0 R
+/Prev 763 0 R
+/Next 771 0 R
+>> endobj
+763 0 obj <<
+/Title 764 0 R
+/A 761 0 R
+/Parent 751 0 R
+/Prev 759 0 R
+/Next 767 0 R
+>> endobj
+759 0 obj <<
+/Title 760 0 R
+/A 757 0 R
+/Parent 751 0 R
+/Prev 755 0 R
+/Next 763 0 R
+>> endobj
+755 0 obj <<
+/Title 756 0 R
+/A 753 0 R
+/Parent 751 0 R
+/Next 759 0 R
+>> endobj
+751 0 obj <<
+/Title 752 0 R
+/A 749 0 R
+/Parent 1508 0 R
+/Prev 691 0 R
+/First 755 0 R
+/Last 771 0 R
+/Count -5
+>> endobj
+747 0 obj <<
+/Title 748 0 R
+/A 745 0 R
+/Parent 691 0 R
+/Prev 743 0 R
+>> endobj
+743 0 obj <<
+/Title 744 0 R
+/A 741 0 R
+/Parent 691 0 R
+/Prev 731 0 R
+/Next 747 0 R
+>> endobj
+739 0 obj <<
+/Title 740 0 R
+/A 737 0 R
+/Parent 731 0 R
+/Prev 735 0 R
+>> endobj
+735 0 obj <<
+/Title 736 0 R
+/A 733 0 R
+/Parent 731 0 R
+/Next 739 0 R
+>> endobj
+731 0 obj <<
+/Title 732 0 R
+/A 729 0 R
+/Parent 691 0 R
+/Prev 707 0 R
+/Next 743 0 R
+/First 735 0 R
+/Last 739 0 R
+/Count -2
+>> endobj
+727 0 obj <<
+/Title 728 0 R
+/A 725 0 R
+/Parent 707 0 R
+/Prev 723 0 R
+>> endobj
+723 0 obj <<
+/Title 724 0 R
+/A 721 0 R
+/Parent 707 0 R
+/Prev 719 0 R
+/Next 727 0 R
+>> endobj
+719 0 obj <<
+/Title 720 0 R
+/A 717 0 R
+/Parent 707 0 R
+/Prev 715 0 R
+/Next 723 0 R
+>> endobj
+715 0 obj <<
+/Title 716 0 R
+/A 713 0 R
+/Parent 707 0 R
+/Prev 711 0 R
+/Next 719 0 R
+>> endobj
+711 0 obj <<
+/Title 712 0 R
+/A 709 0 R
+/Parent 707 0 R
+/Next 715 0 R
+>> endobj
+707 0 obj <<
+/Title 708 0 R
+/A 705 0 R
+/Parent 691 0 R
+/Prev 695 0 R
+/Next 731 0 R
+/First 711 0 R
+/Last 727 0 R
+/Count -5
+>> endobj
+703 0 obj <<
+/Title 704 0 R
+/A 701 0 R
+/Parent 695 0 R
+/Prev 699 0 R
+>> endobj
+699 0 obj <<
+/Title 700 0 R
+/A 697 0 R
+/Parent 695 0 R
+/Next 703 0 R
+>> endobj
+695 0 obj <<
+/Title 696 0 R
+/A 693 0 R
+/Parent 691 0 R
+/Next 707 0 R
+/First 699 0 R
+/Last 703 0 R
+/Count -2
+>> endobj
+691 0 obj <<
+/Title 692 0 R
+/A 689 0 R
+/Parent 1508 0 R
+/Prev 679 0 R
+/Next 751 0 R
+/First 695 0 R
+/Last 747 0 R
+/Count -5
+>> endobj
+687 0 obj <<
+/Title 688 0 R
+/A 685 0 R
+/Parent 679 0 R
+/Prev 683 0 R
+>> endobj
+683 0 obj <<
+/Title 684 0 R
+/A 681 0 R
+/Parent 679 0 R
+/Next 687 0 R
+>> endobj
+679 0 obj <<
+/Title 680 0 R
+/A 677 0 R
+/Parent 1508 0 R
+/Prev 659 0 R
+/Next 691 0 R
+/First 683 0 R
+/Last 687 0 R
+/Count -2
+>> endobj
+675 0 obj <<
+/Title 676 0 R
+/A 673 0 R
+/Parent 659 0 R
+/Prev 671 0 R
+>> endobj
+671 0 obj <<
+/Title 672 0 R
+/A 669 0 R
+/Parent 659 0 R
+/Prev 667 0 R
+/Next 675 0 R
+>> endobj
+667 0 obj <<
+/Title 668 0 R
+/A 665 0 R
+/Parent 659 0 R
+/Prev 663 0 R
+/Next 671 0 R
+>> endobj
+663 0 obj <<
+/Title 664 0 R
+/A 661 0 R
+/Parent 659 0 R
+/Next 667 0 R
+>> endobj
+659 0 obj <<
+/Title 660 0 R
+/A 657 0 R
+/Parent 1508 0 R
+/Prev 303 0 R
+/Next 679 0 R
+/First 663 0 R
+/Last 675 0 R
+/Count -4
+>> endobj
+655 0 obj <<
+/Title 656 0 R
+/A 653 0 R
+/Parent 303 0 R
+/Prev 651 0 R
+>> endobj
+651 0 obj <<
+/Title 652 0 R
+/A 649 0 R
+/Parent 303 0 R
+/Prev 635 0 R
+/Next 655 0 R
+>> endobj
+647 0 obj <<
+/Title 648 0 R
+/A 645 0 R
+/Parent 635 0 R
+/Prev 643 0 R
+>> endobj
+643 0 obj <<
+/Title 644 0 R
+/A 641 0 R
+/Parent 635 0 R
+/Prev 639 0 R
+/Next 647 0 R
+>> endobj
+639 0 obj <<
+/Title 640 0 R
+/A 637 0 R
+/Parent 635 0 R
+/Next 643 0 R
+>> endobj
+635 0 obj <<
+/Title 636 0 R
+/A 633 0 R
+/Parent 303 0 R
+/Prev 619 0 R
+/Next 651 0 R
+/First 639 0 R
+/Last 647 0 R
+/Count -3
+>> endobj
+631 0 obj <<
+/Title 632 0 R
+/A 629 0 R
+/Parent 619 0 R
+/Prev 627 0 R
+>> endobj
+627 0 obj <<
+/Title 628 0 R
+/A 625 0 R
+/Parent 619 0 R
+/Prev 623 0 R
+/Next 631 0 R
+>> endobj
+623 0 obj <<
+/Title 624 0 R
+/A 621 0 R
+/Parent 619 0 R
+/Next 627 0 R
+>> endobj
+619 0 obj <<
+/Title 620 0 R
+/A 617 0 R
+/Parent 303 0 R
+/Prev 599 0 R
+/Next 635 0 R
+/First 623 0 R
+/Last 631 0 R
+/Count -3
+>> endobj
+615 0 obj <<
+/Title 616 0 R
+/A 613 0 R
+/Parent 599 0 R
+/Prev 611 0 R
+>> endobj
+611 0 obj <<
+/Title 612 0 R
+/A 609 0 R
+/Parent 599 0 R
+/Prev 607 0 R
+/Next 615 0 R
+>> endobj
+607 0 obj <<
+/Title 608 0 R
+/A 605 0 R
+/Parent 599 0 R
+/Prev 603 0 R
+/Next 611 0 R
+>> endobj
+603 0 obj <<
+/Title 604 0 R
+/A 601 0 R
+/Parent 599 0 R
+/Next 607 0 R
+>> endobj
+599 0 obj <<
+/Title 600 0 R
+/A 597 0 R
+/Parent 303 0 R
+/Prev 567 0 R
+/Next 619 0 R
+/First 603 0 R
+/Last 615 0 R
+/Count -4
+>> endobj
+595 0 obj <<
+/Title 596 0 R
+/A 593 0 R
+/Parent 567 0 R
+/Prev 591 0 R
+>> endobj
+591 0 obj <<
+/Title 592 0 R
+/A 589 0 R
+/Parent 567 0 R
+/Prev 587 0 R
+/Next 595 0 R
+>> endobj
+587 0 obj <<
+/Title 588 0 R
+/A 585 0 R
+/Parent 567 0 R
+/Prev 583 0 R
+/Next 591 0 R
+>> endobj
+583 0 obj <<
+/Title 584 0 R
+/A 581 0 R
+/Parent 567 0 R
+/Prev 579 0 R
+/Next 587 0 R
+>> endobj
+579 0 obj <<
+/Title 580 0 R
+/A 577 0 R
+/Parent 567 0 R
+/Prev 575 0 R
+/Next 583 0 R
+>> endobj
+575 0 obj <<
+/Title 576 0 R
+/A 573 0 R
+/Parent 567 0 R
+/Prev 571 0 R
+/Next 579 0 R
+>> endobj
+571 0 obj <<
+/Title 572 0 R
+/A 569 0 R
+/Parent 567 0 R
+/Next 575 0 R
+>> endobj
+567 0 obj <<
+/Title 568 0 R
+/A 565 0 R
+/Parent 303 0 R
+/Prev 563 0 R
+/Next 599 0 R
+/First 571 0 R
+/Last 595 0 R
+/Count -7
+>> endobj
+563 0 obj <<
+/Title 564 0 R
+/A 561 0 R
+/Parent 303 0 R
+/Prev 559 0 R
+/Next 567 0 R
+>> endobj
+559 0 obj <<
+/Title 560 0 R
+/A 557 0 R
+/Parent 303 0 R
+/Prev 539 0 R
+/Next 563 0 R
+>> endobj
+555 0 obj <<
+/Title 556 0 R
+/A 553 0 R
+/Parent 539 0 R
+/Prev 551 0 R
+>> endobj
+551 0 obj <<
+/Title 552 0 R
+/A 549 0 R
+/Parent 539 0 R
+/Prev 547 0 R
+/Next 555 0 R
+>> endobj
+547 0 obj <<
+/Title 548 0 R
+/A 545 0 R
+/Parent 539 0 R
+/Prev 543 0 R
+/Next 551 0 R
+>> endobj
+543 0 obj <<
+/Title 544 0 R
+/A 541 0 R
+/Parent 539 0 R
+/Next 547 0 R
+>> endobj
+539 0 obj <<
+/Title 540 0 R
+/A 537 0 R
+/Parent 303 0 R
+/Prev 535 0 R
+/Next 559 0 R
+/First 543 0 R
+/Last 555 0 R
+/Count -4
+>> endobj
+535 0 obj <<
+/Title 536 0 R
+/A 533 0 R
+/Parent 303 0 R
+/Prev 531 0 R
+/Next 539 0 R
+>> endobj
+531 0 obj <<
+/Title 532 0 R
+/A 529 0 R
+/Parent 303 0 R
+/Prev 499 0 R
+/Next 535 0 R
+>> endobj
+527 0 obj <<
+/Title 528 0 R
+/A 525 0 R
+/Parent 499 0 R
+/Prev 523 0 R
+>> endobj
+523 0 obj <<
+/Title 524 0 R
+/A 521 0 R
+/Parent 499 0 R
+/Prev 519 0 R
+/Next 527 0 R
+>> endobj
+519 0 obj <<
+/Title 520 0 R
+/A 517 0 R
+/Parent 499 0 R
+/Prev 515 0 R
+/Next 523 0 R
+>> endobj
+515 0 obj <<
+/Title 516 0 R
+/A 513 0 R
+/Parent 499 0 R
+/Prev 511 0 R
+/Next 519 0 R
+>> endobj
+511 0 obj <<
+/Title 512 0 R
+/A 509 0 R
+/Parent 499 0 R
+/Prev 507 0 R
+/Next 515 0 R
+>> endobj
+507 0 obj <<
+/Title 508 0 R
+/A 505 0 R
+/Parent 499 0 R
+/Prev 503 0 R
+/Next 511 0 R
+>> endobj
+503 0 obj <<
+/Title 504 0 R
+/A 501 0 R
+/Parent 499 0 R
+/Next 507 0 R
+>> endobj
+499 0 obj <<
+/Title 500 0 R
+/A 497 0 R
+/Parent 303 0 R
+/Prev 471 0 R
+/Next 531 0 R
+/First 503 0 R
+/Last 527 0 R
+/Count -7
+>> endobj
+495 0 obj <<
+/Title 496 0 R
+/A 493 0 R
+/Parent 471 0 R
+/Prev 491 0 R
+>> endobj
+491 0 obj <<
+/Title 492 0 R
+/A 489 0 R
+/Parent 471 0 R
+/Prev 487 0 R
+/Next 495 0 R
+>> endobj
+487 0 obj <<
+/Title 488 0 R
+/A 485 0 R
+/Parent 471 0 R
+/Prev 483 0 R
+/Next 491 0 R
+>> endobj
+483 0 obj <<
+/Title 484 0 R
+/A 481 0 R
+/Parent 471 0 R
+/Prev 479 0 R
+/Next 487 0 R
+>> endobj
+479 0 obj <<
+/Title 480 0 R
+/A 477 0 R
+/Parent 471 0 R
+/Prev 475 0 R
+/Next 483 0 R
+>> endobj
+475 0 obj <<
+/Title 476 0 R
+/A 473 0 R
+/Parent 471 0 R
+/Next 479 0 R
+>> endobj
+471 0 obj <<
+/Title 472 0 R
+/A 469 0 R
+/Parent 303 0 R
+/Prev 427 0 R
+/Next 499 0 R
+/First 475 0 R
+/Last 495 0 R
+/Count -6
+>> endobj
+467 0 obj <<
+/Title 468 0 R
+/A 465 0 R
+/Parent 427 0 R
+/Prev 463 0 R
+>> endobj
+463 0 obj <<
+/Title 464 0 R
+/A 461 0 R
+/Parent 427 0 R
+/Prev 459 0 R
+/Next 467 0 R
+>> endobj
+459 0 obj <<
+/Title 460 0 R
+/A 457 0 R
+/Parent 427 0 R
+/Prev 455 0 R
+/Next 463 0 R
+>> endobj
+455 0 obj <<
+/Title 456 0 R
+/A 453 0 R
+/Parent 427 0 R
+/Prev 451 0 R
+/Next 459 0 R
+>> endobj
+451 0 obj <<
+/Title 452 0 R
+/A 449 0 R
+/Parent 427 0 R
+/Prev 447 0 R
+/Next 455 0 R
+>> endobj
+447 0 obj <<
+/Title 448 0 R
+/A 445 0 R
+/Parent 427 0 R
+/Prev 443 0 R
+/Next 451 0 R
+>> endobj
+443 0 obj <<
+/Title 444 0 R
+/A 441 0 R
+/Parent 427 0 R
+/Prev 439 0 R
+/Next 447 0 R
+>> endobj
+439 0 obj <<
+/Title 440 0 R
+/A 437 0 R
+/Parent 427 0 R
+/Prev 435 0 R
+/Next 443 0 R
+>> endobj
+435 0 obj <<
+/Title 436 0 R
+/A 433 0 R
+/Parent 427 0 R
+/Prev 431 0 R
+/Next 439 0 R
+>> endobj
+431 0 obj <<
+/Title 432 0 R
+/A 429 0 R
+/Parent 427 0 R
+/Next 435 0 R
+>> endobj
+427 0 obj <<
+/Title 428 0 R
+/A 425 0 R
+/Parent 303 0 R
+/Prev 399 0 R
+/Next 471 0 R
+/First 431 0 R
+/Last 467 0 R
+/Count -10
+>> endobj
+423 0 obj <<
+/Title 424 0 R
+/A 421 0 R
+/Parent 399 0 R
+/Prev 419 0 R
+>> endobj
+419 0 obj <<
+/Title 420 0 R
+/A 417 0 R
+/Parent 399 0 R
+/Prev 415 0 R
+/Next 423 0 R
+>> endobj
+415 0 obj <<
+/Title 416 0 R
+/A 413 0 R
+/Parent 399 0 R
+/Prev 411 0 R
+/Next 419 0 R
+>> endobj
+411 0 obj <<
+/Title 412 0 R
+/A 409 0 R
+/Parent 399 0 R
+/Prev 407 0 R
+/Next 415 0 R
+>> endobj
+407 0 obj <<
+/Title 408 0 R
+/A 405 0 R
+/Parent 399 0 R
+/Prev 403 0 R
+/Next 411 0 R
+>> endobj
+403 0 obj <<
+/Title 404 0 R
+/A 401 0 R
+/Parent 399 0 R
+/Next 407 0 R
+>> endobj
+399 0 obj <<
+/Title 400 0 R
+/A 397 0 R
+/Parent 303 0 R
+/Prev 339 0 R
+/Next 427 0 R
+/First 403 0 R
+/Last 423 0 R
+/Count -6
+>> endobj
+395 0 obj <<
+/Title 396 0 R
+/A 393 0 R
+/Parent 339 0 R
+/Prev 391 0 R
+>> endobj
+391 0 obj <<
+/Title 392 0 R
+/A 389 0 R
+/Parent 339 0 R
+/Prev 387 0 R
+/Next 395 0 R
+>> endobj
+387 0 obj <<
+/Title 388 0 R
+/A 385 0 R
+/Parent 339 0 R
+/Prev 383 0 R
+/Next 391 0 R
+>> endobj
+383 0 obj <<
+/Title 384 0 R
+/A 381 0 R
+/Parent 339 0 R
+/Prev 379 0 R
+/Next 387 0 R
+>> endobj
+379 0 obj <<
+/Title 380 0 R
+/A 377 0 R
+/Parent 339 0 R
+/Prev 375 0 R
+/Next 383 0 R
+>> endobj
+375 0 obj <<
+/Title 376 0 R
+/A 373 0 R
+/Parent 339 0 R
+/Prev 371 0 R
+/Next 379 0 R
+>> endobj
+371 0 obj <<
+/Title 372 0 R
+/A 369 0 R
+/Parent 339 0 R
+/Prev 367 0 R
+/Next 375 0 R
+>> endobj
+367 0 obj <<
+/Title 368 0 R
+/A 365 0 R
+/Parent 339 0 R
+/Prev 363 0 R
+/Next 371 0 R
+>> endobj
+363 0 obj <<
+/Title 364 0 R
+/A 361 0 R
+/Parent 339 0 R
+/Prev 359 0 R
+/Next 367 0 R
+>> endobj
+359 0 obj <<
+/Title 360 0 R
+/A 357 0 R
+/Parent 339 0 R
+/Prev 355 0 R
+/Next 363 0 R
+>> endobj
+355 0 obj <<
+/Title 356 0 R
+/A 353 0 R
+/Parent 339 0 R
+/Prev 351 0 R
+/Next 359 0 R
+>> endobj
+351 0 obj <<
+/Title 352 0 R
+/A 349 0 R
+/Parent 339 0 R
+/Prev 347 0 R
+/Next 355 0 R
+>> endobj
+347 0 obj <<
+/Title 348 0 R
+/A 345 0 R
+/Parent 339 0 R
+/Prev 343 0 R
+/Next 351 0 R
+>> endobj
+343 0 obj <<
+/Title 344 0 R
+/A 341 0 R
+/Parent 339 0 R
+/Next 347 0 R
+>> endobj
+339 0 obj <<
+/Title 340 0 R
+/A 337 0 R
+/Parent 303 0 R
+/Prev 307 0 R
+/Next 399 0 R
+/First 343 0 R
+/Last 395 0 R
+/Count -14
+>> endobj
+335 0 obj <<
+/Title 336 0 R
+/A 333 0 R
+/Parent 307 0 R
+/Prev 331 0 R
+>> endobj
+331 0 obj <<
+/Title 332 0 R
+/A 329 0 R
+/Parent 307 0 R
+/Prev 327 0 R
+/Next 335 0 R
+>> endobj
+327 0 obj <<
+/Title 328 0 R
+/A 325 0 R
+/Parent 307 0 R
+/Prev 323 0 R
+/Next 331 0 R
+>> endobj
+323 0 obj <<
+/Title 324 0 R
+/A 321 0 R
+/Parent 307 0 R
+/Prev 319 0 R
+/Next 327 0 R
+>> endobj
+319 0 obj <<
+/Title 320 0 R
+/A 317 0 R
+/Parent 307 0 R
+/Prev 315 0 R
+/Next 323 0 R
+>> endobj
+315 0 obj <<
+/Title 316 0 R
+/A 313 0 R
+/Parent 307 0 R
+/Prev 311 0 R
+/Next 319 0 R
+>> endobj
+311 0 obj <<
+/Title 312 0 R
+/A 309 0 R
+/Parent 307 0 R
+/Next 315 0 R
+>> endobj
+307 0 obj <<
+/Title 308 0 R
+/A 305 0 R
+/Parent 303 0 R
+/Next 339 0 R
+/First 311 0 R
+/Last 335 0 R
+/Count -7
+>> endobj
+303 0 obj <<
+/Title 304 0 R
+/A 301 0 R
+/Parent 1508 0 R
+/Prev 275 0 R
+/Next 659 0 R
+/First 307 0 R
+/Last 655 0 R
+/Count -17
+>> endobj
+299 0 obj <<
+/Title 300 0 R
+/A 297 0 R
+/Parent 275 0 R
+/Prev 295 0 R
+>> endobj
+295 0 obj <<
+/Title 296 0 R
+/A 293 0 R
+/Parent 275 0 R
+/Prev 291 0 R
+/Next 299 0 R
+>> endobj
+291 0 obj <<
+/Title 292 0 R
+/A 289 0 R
+/Parent 275 0 R
+/Prev 287 0 R
+/Next 295 0 R
+>> endobj
+287 0 obj <<
+/Title 288 0 R
+/A 285 0 R
+/Parent 275 0 R
+/Prev 283 0 R
+/Next 291 0 R
+>> endobj
+283 0 obj <<
+/Title 284 0 R
+/A 281 0 R
+/Parent 275 0 R
+/Prev 279 0 R
+/Next 287 0 R
+>> endobj
+279 0 obj <<
+/Title 280 0 R
+/A 277 0 R
+/Parent 275 0 R
+/Next 283 0 R
+>> endobj
+275 0 obj <<
+/Title 276 0 R
+/A 273 0 R
+/Parent 1508 0 R
+/Prev 151 0 R
+/Next 303 0 R
+/First 279 0 R
+/Last 299 0 R
+/Count -6
+>> endobj
+271 0 obj <<
+/Title 272 0 R
+/A 269 0 R
+/Parent 151 0 R
+/Prev 259 0 R
+>> endobj
+267 0 obj <<
+/Title 268 0 R
+/A 265 0 R
+/Parent 259 0 R
+/Prev 263 0 R
+>> endobj
+263 0 obj <<
+/Title 264 0 R
+/A 261 0 R
+/Parent 259 0 R
+/Next 267 0 R
+>> endobj
+259 0 obj <<
+/Title 260 0 R
+/A 257 0 R
+/Parent 151 0 R
+/Prev 255 0 R
+/Next 271 0 R
+/First 263 0 R
+/Last 267 0 R
+/Count -2
+>> endobj
+255 0 obj <<
+/Title 256 0 R
+/A 253 0 R
+/Parent 151 0 R
+/Prev 251 0 R
+/Next 259 0 R
+>> endobj
+251 0 obj <<
+/Title 252 0 R
+/A 249 0 R
+/Parent 151 0 R
+/Prev 247 0 R
+/Next 255 0 R
+>> endobj
+247 0 obj <<
+/Title 248 0 R
+/A 245 0 R
+/Parent 151 0 R
+/Prev 243 0 R
+/Next 251 0 R
+>> endobj
+243 0 obj <<
+/Title 244 0 R
+/A 241 0 R
+/Parent 151 0 R
+/Prev 207 0 R
+/Next 247 0 R
+>> endobj
+239 0 obj <<
+/Title 240 0 R
+/A 237 0 R
+/Parent 207 0 R
+/Prev 235 0 R
+>> endobj
+235 0 obj <<
+/Title 236 0 R
+/A 233 0 R
+/Parent 207 0 R
+/Prev 231 0 R
+/Next 239 0 R
+>> endobj
+231 0 obj <<
+/Title 232 0 R
+/A 229 0 R
+/Parent 207 0 R
+/Prev 227 0 R
+/Next 235 0 R
+>> endobj
+227 0 obj <<
+/Title 228 0 R
+/A 225 0 R
+/Parent 207 0 R
+/Prev 223 0 R
+/Next 231 0 R
+>> endobj
+223 0 obj <<
+/Title 224 0 R
+/A 221 0 R
+/Parent 207 0 R
+/Prev 219 0 R
+/Next 227 0 R
+>> endobj
+219 0 obj <<
+/Title 220 0 R
+/A 217 0 R
+/Parent 207 0 R
+/Prev 215 0 R
+/Next 223 0 R
+>> endobj
+215 0 obj <<
+/Title 216 0 R
+/A 213 0 R
+/Parent 207 0 R
+/Prev 211 0 R
+/Next 219 0 R
+>> endobj
+211 0 obj <<
+/Title 212 0 R
+/A 209 0 R
+/Parent 207 0 R
+/Next 215 0 R
+>> endobj
+207 0 obj <<
+/Title 208 0 R
+/A 205 0 R
+/Parent 151 0 R
+/Prev 187 0 R
+/Next 243 0 R
+/First 211 0 R
+/Last 239 0 R
+/Count -8
+>> endobj
+203 0 obj <<
+/Title 204 0 R
+/A 201 0 R
+/Parent 187 0 R
+/Prev 199 0 R
+>> endobj
+199 0 obj <<
+/Title 200 0 R
+/A 197 0 R
+/Parent 187 0 R
+/Prev 195 0 R
+/Next 203 0 R
+>> endobj
+195 0 obj <<
+/Title 196 0 R
+/A 193 0 R
+/Parent 187 0 R
+/Prev 191 0 R
+/Next 199 0 R
+>> endobj
+191 0 obj <<
+/Title 192 0 R
+/A 189 0 R
+/Parent 187 0 R
+/Next 195 0 R
+>> endobj
+187 0 obj <<
+/Title 188 0 R
+/A 185 0 R
+/Parent 151 0 R
+/Prev 183 0 R
+/Next 207 0 R
+/First 191 0 R
+/Last 203 0 R
+/Count -4
+>> endobj
+183 0 obj <<
+/Title 184 0 R
+/A 181 0 R
+/Parent 151 0 R
+/Prev 179 0 R
+/Next 187 0 R
+>> endobj
+179 0 obj <<
+/Title 180 0 R
+/A 177 0 R
+/Parent 151 0 R
+/Prev 175 0 R
+/Next 183 0 R
+>> endobj
+175 0 obj <<
+/Title 176 0 R
+/A 173 0 R
+/Parent 151 0 R
+/Prev 159 0 R
+/Next 179 0 R
+>> endobj
+171 0 obj <<
+/Title 172 0 R
+/A 169 0 R
+/Parent 159 0 R
+/Prev 167 0 R
+>> endobj
+167 0 obj <<
+/Title 168 0 R
+/A 165 0 R
+/Parent 159 0 R
+/Prev 163 0 R
+/Next 171 0 R
+>> endobj
+163 0 obj <<
+/Title 164 0 R
+/A 161 0 R
+/Parent 159 0 R
+/Next 167 0 R
+>> endobj
+159 0 obj <<
+/Title 160 0 R
+/A 157 0 R
+/Parent 151 0 R
+/Prev 155 0 R
+/Next 175 0 R
+/First 163 0 R
+/Last 171 0 R
+/Count -3
+>> endobj
+155 0 obj <<
+/Title 156 0 R
+/A 153 0 R
+/Parent 151 0 R
+/Next 159 0 R
+>> endobj
+151 0 obj <<
+/Title 152 0 R
+/A 149 0 R
+/Parent 1508 0 R
+/Prev 131 0 R
+/Next 275 0 R
+/First 155 0 R
+/Last 271 0 R
+/Count -13
+>> endobj
+147 0 obj <<
+/Title 148 0 R
+/A 145 0 R
+/Parent 131 0 R
+/Prev 135 0 R
+>> endobj
+143 0 obj <<
+/Title 144 0 R
+/A 141 0 R
+/Parent 135 0 R
+/Prev 139 0 R
+>> endobj
+139 0 obj <<
+/Title 140 0 R
+/A 137 0 R
+/Parent 135 0 R
+/Next 143 0 R
+>> endobj
+135 0 obj <<
+/Title 136 0 R
+/A 133 0 R
+/Parent 131 0 R
+/Next 147 0 R
+/First 139 0 R
+/Last 143 0 R
+/Count -2
+>> endobj
+131 0 obj <<
+/Title 132 0 R
+/A 129 0 R
+/Parent 1508 0 R
+/Prev 75 0 R
+/Next 151 0 R
+/First 135 0 R
+/Last 147 0 R
+/Count -2
+>> endobj
+127 0 obj <<
+/Title 128 0 R
+/A 125 0 R
+/Parent 75 0 R
+/Prev 123 0 R
+>> endobj
+123 0 obj <<
+/Title 124 0 R
+/A 121 0 R
+/Parent 75 0 R
+/Prev 119 0 R
+/Next 127 0 R
+>> endobj
+119 0 obj <<
+/Title 120 0 R
+/A 117 0 R
+/Parent 75 0 R
+/Prev 115 0 R
+/Next 123 0 R
+>> endobj
+115 0 obj <<
+/Title 116 0 R
+/A 113 0 R
+/Parent 75 0 R
+/Prev 111 0 R
+/Next 119 0 R
+>> endobj
+111 0 obj <<
+/Title 112 0 R
+/A 109 0 R
+/Parent 75 0 R
+/Prev 107 0 R
+/Next 115 0 R
+>> endobj
+107 0 obj <<
+/Title 108 0 R
+/A 105 0 R
+/Parent 75 0 R
+/Prev 103 0 R
+/Next 111 0 R
+>> endobj
+103 0 obj <<
+/Title 104 0 R
+/A 101 0 R
+/Parent 75 0 R
+/Prev 99 0 R
+/Next 107 0 R
+>> endobj
+99 0 obj <<
+/Title 100 0 R
+/A 97 0 R
+/Parent 75 0 R
+/Prev 95 0 R
+/Next 103 0 R
+>> endobj
+95 0 obj <<
+/Title 96 0 R
+/A 93 0 R
+/Parent 75 0 R
+/Prev 91 0 R
+/Next 99 0 R
+>> endobj
+91 0 obj <<
+/Title 92 0 R
+/A 89 0 R
+/Parent 75 0 R
+/Prev 87 0 R
+/Next 95 0 R
+>> endobj
+87 0 obj <<
+/Title 88 0 R
+/A 85 0 R
+/Parent 75 0 R
+/Prev 83 0 R
+/Next 91 0 R
+>> endobj
+83 0 obj <<
+/Title 84 0 R
+/A 81 0 R
+/Parent 75 0 R
+/Prev 79 0 R
+/Next 87 0 R
+>> endobj
+79 0 obj <<
+/Title 80 0 R
+/A 77 0 R
+/Parent 75 0 R
+/Next 83 0 R
+>> endobj
+75 0 obj <<
+/Title 76 0 R
+/A 73 0 R
+/Parent 1508 0 R
+/Prev 51 0 R
+/Next 131 0 R
+/First 79 0 R
+/Last 127 0 R
+/Count -13
+>> endobj
+71 0 obj <<
+/Title 72 0 R
+/A 69 0 R
+/Parent 51 0 R
+/Prev 67 0 R
+>> endobj
+67 0 obj <<
+/Title 68 0 R
+/A 65 0 R
+/Parent 51 0 R
+/Prev 63 0 R
+/Next 71 0 R
+>> endobj
+63 0 obj <<
+/Title 64 0 R
+/A 61 0 R
+/Parent 51 0 R
+/Prev 59 0 R
+/Next 67 0 R
+>> endobj
+59 0 obj <<
+/Title 60 0 R
+/A 57 0 R
+/Parent 51 0 R
+/Prev 55 0 R
+/Next 63 0 R
+>> endobj
+55 0 obj <<
+/Title 56 0 R
+/A 53 0 R
+/Parent 51 0 R
+/Next 59 0 R
+>> endobj
+51 0 obj <<
+/Title 52 0 R
+/A 49 0 R
+/Parent 1508 0 R
+/Prev 39 0 R
+/Next 75 0 R
+/First 55 0 R
+/Last 71 0 R
+/Count -5
+>> endobj
+47 0 obj <<
+/Title 48 0 R
+/A 45 0 R
+/Parent 39 0 R
+/Prev 43 0 R
+>> endobj
+43 0 obj <<
+/Title 44 0 R
+/A 41 0 R
+/Parent 39 0 R
+/Next 47 0 R
+>> endobj
+39 0 obj <<
+/Title 40 0 R
+/A 37 0 R
+/Parent 1508 0 R
+/Prev 7 0 R
+/Next 51 0 R
+/First 43 0 R
+/Last 47 0 R
+/Count -2
+>> endobj
+35 0 obj <<
+/Title 36 0 R
+/A 33 0 R
+/Parent 7 0 R
+/Prev 31 0 R
+>> endobj
+31 0 obj <<
+/Title 32 0 R
+/A 29 0 R
+/Parent 7 0 R
+/Prev 27 0 R
+/Next 35 0 R
+>> endobj
+27 0 obj <<
+/Title 28 0 R
+/A 25 0 R
+/Parent 7 0 R
+/Prev 23 0 R
+/Next 31 0 R
+>> endobj
+23 0 obj <<
+/Title 24 0 R
+/A 21 0 R
+/Parent 7 0 R
+/Prev 19 0 R
+/Next 27 0 R
+>> endobj
+19 0 obj <<
+/Title 20 0 R
+/A 17 0 R
+/Parent 7 0 R
+/Prev 15 0 R
+/Next 23 0 R
+>> endobj
+15 0 obj <<
+/Title 16 0 R
+/A 13 0 R
+/Parent 7 0 R
+/Prev 11 0 R
+/Next 19 0 R
+>> endobj
+11 0 obj <<
+/Title 12 0 R
+/A 9 0 R
+/Parent 7 0 R
+/Next 15 0 R
+>> endobj
+7 0 obj <<
+/Title 8 0 R
+/A 5 0 R
+/Parent 1508 0 R
+/Next 39 0 R
+/First 11 0 R
+/Last 35 0 R
+/Count -7
+>> endobj
+1509 0 obj <<
+/Names [(Doc-Start) 778 0 R (Item.1) 1149 0 R (Item.2) 1153 0 R (Item.3) 1155 0 R (Item.4) 1165 0 R (Item.5) 1166 0 R (Item.6) 1171 0 R (Item.7) 1175 0 R (Item.8) 1266 0 R (Item.9) 1267 0 R (page.1) 777 0 R (page.10) 1049 0 R (page.11) 1055 0 R (page.12) 1066 0 R (page.13) 1080 0 R (page.14) 1091 0 R (page.15) 1100 0 R (page.16) 1105 0 R (page.17) 1118 0 R (page.18) 1127 0 R (page.19) 1138 0 R (page.2) 825 0 R (page.20) 1147 0 R (page.21) 1161 0 R (page.22) 1170 0 R (page.23) 1179 0 R (page.24) 1184 0 R (page.25) 1191 0 R (page.26) 1198 0 R (page.27) 1204 0 R (page.28) 1210 0 R (page.29) 1214 0 R (page.3) 872 0 R (page.30) 1218 0 R (page.31) 1222 0 R (page.32) 1234 0 R (page.33) 1239 0 R (page.34) 1246 0 R (page.35) 1255 0 R (page.36) 1260 0 R (page.37) 1265 0 R (page.38) 1272 0 R (page.39) 1276 0 R (page.4) 912 0 R (page.40) 1281 0 R (page.41) 1287 0 R (page.42) 1291 0 R (page.43) 1297 0 R (page.44) 1302 0 R (page.45) 1306 0 R (page.46) 1314 0 R (page.47) 1318 0 R (page.48) 1322 0 R (page.49) 1329 0 R (page.5) 953 0 R (page.50) 1337 0 R (page.51) 1345 0 R (page.52) 1351 0 R (page.53) 1355 0 R (page.54) 1359 0 R (page.55) 1363 0 R (page.56) 1373 0 R (page.57) 1388 0 R (page.58) 1392 0 R (page.59) 1396 0 R (page.6) 995 0 R (page.60) 1400 0 R (page.61) 1404 0 R (page.62) 1416 0 R (page.63) 1424 0 R (page.64) 1428 0 R (page.65) 1432 0 R (page.66) 1436 0 R (page.67) 1440 0 R (page.68) 1451 0 R (page.69) 1456 0 R (page.7) 1030 0 R (page.70) 1465 0 R (page.71) 1473 0 R (page.72) 1481 0 R (page.8) 1036 0 R (page.9) 1043 0 R (section*.1) 791 0 R (section*.2) 1409 0 R (section.1) 6 0 R (section.10) 678 0 R (section.11) 690 0 R (section.12) 750 0 R (section.2) 38 0 R (section.3) 50 0 R (section.4) 74 0 R (section.5) 130 0 R (section.6) 150 0 R (section.7) 274 0 R (section.8) 302 0 R (section.9) 658 0 R (subsection.1.1) 10 0 R (subsection.1.2) 14 0 R (subsection.1.3) 18 0 R (subsection.1.4) 22 0 R (subsection.1.5) 26 0 R (subsection.1.6) 30 0 R (subsection.1.7) 34 0 R (subsection.10.1) 682 0 R (subsection.10.2) 686 0 R (subsection.11.1) 694 0 R (subsection.11.2) 706 0 R (subsection.11.3) 730 0 R (subsection.11.4) 742 0 R (subsection.11.5) 746 0 R (subsection.12.1) 754 0 R (subsection.12.2) 758 0 R (subsection.12.3) 762 0 R (subsection.12.4) 766 0 R (subsection.12.5) 770 0 R (subsection.2.1) 42 0 R (subsection.2.2) 46 0 R (subsection.3.1) 54 0 R (subsection.3.2) 58 0 R (subsection.3.3) 62 0 R (subsection.3.4) 66 0 R (subsection.3.5) 70 0 R (subsection.4.1) 78 0 R (subsection.4.10) 114 0 R (subsection.4.11) 118 0 R (subsection.4.12) 122 0 R (subsection.4.13) 126 0 R (subsection.4.2) 82 0 R (subsection.4.3) 86 0 R (subsection.4.4) 90 0 R (subsection.4.5) 94 0 R (subsection.4.6) 98 0 R (subsection.4.7) 102 0 R (subsection.4.8) 106 0 R (subsection.4.9) 110 0 R (subsection.5.1) 134 0 R (subsection.5.2) 146 0 R (subsection.6.1) 154 0 R (subsection.6.10) 250 0 R (subsection.6.11) 254 0 R (subsection.6.12) 258 0 R (subsection.6.13) 270 0 R (subsection.6.2) 158 0 R (subsection.6.3) 174 0 R (subsection.6.4) 178 0 R (subsection.6.5) 182 0 R (subsection.6.6) 186 0 R (subsection.6.7) 206 0 R (subsection.6.8) 242 0 R (subsection.6.9) 246 0 R (subsection.7.1) 278 0 R (subsection.7.2) 282 0 R (subsection.7.3) 286 0 R (subsection.7.4) 290 0 R (subsection.7.5) 294 0 R (subsection.7.6) 298 0 R (subsection.8.1) 306 0 R (subsection.8.10) 558 0 R (subsection.8.11) 562 0 R (subsection.8.12) 566 0 R (subsection.8.13) 598 0 R (subsection.8.14) 618 0 R (subsection.8.15) 634 0 R (subsection.8.16) 650 0 R (subsection.8.17) 654 0 R (subsection.8.2) 338 0 R (subsection.8.3) 398 0 R (subsection.8.4) 426 0 R (subsection.8.5) 470 0 R (subsection.8.6) 498 0 R (subsection.8.7) 530 0 R (subsection.8.8) 534 0 R (subsection.8.9) 538 0 R (subsection.9.1) 662 0 R (subsection.9.2) 666 0 R (subsection.9.3) 670 0 R (subsection.9.4) 674 0 R (subsubsection.11.1.1) 698 0 R (subsubsection.11.1.2) 702 0 R (subsubsection.11.2.1) 710 0 R (subsubsection.11.2.2) 714 0 R (subsubsection.11.2.3) 718 0 R (subsubsection.11.2.4) 722 0 R (subsubsection.11.2.5) 726 0 R (subsubsection.11.3.1) 734 0 R (subsubsection.11.3.2) 738 0 R (subsubsection.5.1.1) 138 0 R (subsubsection.5.1.2) 142 0 R (subsubsection.6.12.1) 262 0 R (subsubsection.6.12.2) 266 0 R (subsubsection.6.2.1) 162 0 R (subsubsection.6.2.2) 166 0 R (subsubsection.6.2.3) 170 0 R (subsubsection.6.6.1) 190 0 R (subsubsection.6.6.2) 194 0 R (subsubsection.6.6.3) 198 0 R (subsubsection.6.6.4) 202 0 R (subsubsection.6.7.1) 210 0 R (subsubsection.6.7.2) 214 0 R (subsubsection.6.7.3) 218 0 R (subsubsection.6.7.4) 222 0 R (subsubsection.6.7.5) 226 0 R (subsubsection.6.7.6) 230 0 R (subsubsection.6.7.7) 234 0 R (subsubsection.6.7.8) 238 0 R (subsubsection.8.1.1) 310 0 R (subsubsection.8.1.2) 314 0 R (subsubsection.8.1.3) 318 0 R (subsubsection.8.1.4) 322 0 R (subsubsection.8.1.5) 326 0 R (subsubsection.8.1.6) 330 0 R (subsubsection.8.1.7) 334 0 R (subsubsection.8.12.1) 570 0 R (subsubsection.8.12.2) 574 0 R (subsubsection.8.12.3) 578 0 R (subsubsection.8.12.4) 582 0 R (subsubsection.8.12.5) 586 0 R (subsubsection.8.12.6) 590 0 R (subsubsection.8.12.7) 594 0 R (subsubsection.8.13.1) 602 0 R (subsubsection.8.13.2) 606 0 R (subsubsection.8.13.3) 610 0 R (subsubsection.8.13.4) 614 0 R (subsubsection.8.14.1) 622 0 R (subsubsection.8.14.2) 626 0 R (subsubsection.8.14.3) 630 0 R (subsubsection.8.15.1) 638 0 R (subsubsection.8.15.2) 642 0 R (subsubsection.8.15.3) 646 0 R (subsubsection.8.2.1) 342 0 R (subsubsection.8.2.10) 378 0 R (subsubsection.8.2.11) 382 0 R (subsubsection.8.2.12) 386 0 R (subsubsection.8.2.13) 390 0 R (subsubsection.8.2.14) 394 0 R (subsubsection.8.2.2) 346 0 R (subsubsection.8.2.3) 350 0 R (subsubsection.8.2.4) 354 0 R (subsubsection.8.2.5) 358 0 R (subsubsection.8.2.6) 362 0 R (subsubsection.8.2.7) 366 0 R (subsubsection.8.2.8) 370 0 R (subsubsection.8.2.9) 374 0 R (subsubsection.8.3.1) 402 0 R (subsubsection.8.3.2) 406 0 R (subsubsection.8.3.3) 410 0 R (subsubsection.8.3.4) 414 0 R (subsubsection.8.3.5) 418 0 R (subsubsection.8.3.6) 422 0 R (subsubsection.8.4.1) 430 0 R (subsubsection.8.4.10) 466 0 R (subsubsection.8.4.2) 434 0 R (subsubsection.8.4.3) 438 0 R (subsubsection.8.4.4) 442 0 R (subsubsection.8.4.5) 446 0 R (subsubsection.8.4.6) 450 0 R (subsubsection.8.4.7) 454 0 R (subsubsection.8.4.8) 458 0 R (subsubsection.8.4.9) 462 0 R (subsubsection.8.5.1) 474 0 R (subsubsection.8.5.2) 478 0 R (subsubsection.8.5.3) 482 0 R (subsubsection.8.5.4) 486 0 R (subsubsection.8.5.5) 490 0 R (subsubsection.8.5.6) 494 0 R (subsubsection.8.6.1) 502 0 R (subsubsection.8.6.2) 506 0 R (subsubsection.8.6.3) 510 0 R (subsubsection.8.6.4) 514 0 R (subsubsection.8.6.5) 518 0 R (subsubsection.8.6.6) 522 0 R (subsubsection.8.6.7) 526 0 R (subsubsection.8.9.1) 542 0 R (subsubsection.8.9.2) 546 0 R (subsubsection.8.9.3) 550 0 R (subsubsection.8.9.4) 554 0 R]
+/Limits [(Doc-Start) (subsubsection.8.9.4)]
+>> endobj
+1510 0 obj <<
+/Kids [1509 0 R]
+>> endobj
+1511 0 obj <<
+/Dests 1510 0 R
+>> endobj
+1512 0 obj <<
+/Type /Catalog
+/Pages 1507 0 R
+/Outlines 1508 0 R
+/Names 1511 0 R
+/PageMode /UseOutlines
+/OpenAction 773 0 R
+>> endobj
+1513 0 obj <<
+/Author()/Title()/Subject()/Creator(LaTeX with hyperref package)/Producer(pdfeTeX-1.21a)/Keywords()
+/CreationDate (D:20060510141706+02'00')
+/PTEX.Fullbanner (This is pdfeTeX using libpoppler, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4)
+>> endobj
+xref
+0 1514
+0000000001 65535 f
+0000000002 00000 f
+0000000003 00000 f
+0000000004 00000 f
+0000000000 00000 f
+0000000009 00000 n
+0000087387 00000 n
+0000507574 00000 n
+0000000054 00000 n
+0000000117 00000 n
+0000087444 00000 n
+0000507502 00000 n
+0000000167 00000 n
+0000000205 00000 n
+0000087502 00000 n
+0000507416 00000 n
+0000000256 00000 n
+0000000323 00000 n
+0000087560 00000 n
+0000507330 00000 n
+0000000374 00000 n
+0000000442 00000 n
+0000091181 00000 n
+0000507244 00000 n
+0000000493 00000 n
+0000000533 00000 n
+0000091239 00000 n
+0000507158 00000 n
+0000000584 00000 n
+0000000694 00000 n
+0000091297 00000 n
+0000507072 00000 n
+0000000745 00000 n
+0000000826 00000 n
+0000091355 00000 n
+0000506999 00000 n
+0000000877 00000 n
+0000000920 00000 n
+0000095623 00000 n
+0000506874 00000 n
+0000000966 00000 n
+0000001039 00000 n
+0000095681 00000 n
+0000506800 00000 n
+0000001090 00000 n
+0000001147 00000 n
+0000095739 00000 n
+0000506726 00000 n
+0000001198 00000 n
+0000001300 00000 n
+0000100271 00000 n
+0000506600 00000 n
+0000001346 00000 n
+0000001425 00000 n
+0000105197 00000 n
+0000506526 00000 n
+0000001476 00000 n
+0000001530 00000 n
+0000105255 00000 n
+0000506439 00000 n
+0000001581 00000 n
+0000001621 00000 n
+0000110943 00000 n
+0000506352 00000 n
+0000001672 00000 n
+0000001719 00000 n
+0000111001 00000 n
+0000506265 00000 n
+0000001770 00000 n
+0000001813 00000 n
+0000116175 00000 n
+0000506191 00000 n
+0000001864 00000 n
+0000001893 00000 n
+0000116233 00000 n
+0000506062 00000 n
+0000001939 00000 n
+0000002024 00000 n
+0000116291 00000 n
+0000505988 00000 n
+0000002075 00000 n
+0000002189 00000 n
+0000120501 00000 n
+0000505901 00000 n
+0000002240 00000 n
+0000002289 00000 n
+0000120559 00000 n
+0000505814 00000 n
+0000002340 00000 n
+0000002398 00000 n
+0000120617 00000 n
+0000505727 00000 n
+0000002449 00000 n
+0000002501 00000 n
+0000120675 00000 n
+0000505640 00000 n
+0000002552 00000 n
+0000002605 00000 n
+0000120732 00000 n
+0000505551 00000 n
+0000002656 00000 n
+0000002717 00000 n
+0000124727 00000 n
+0000505460 00000 n
+0000002769 00000 n
+0000002833 00000 n
+0000124786 00000 n
+0000505368 00000 n
+0000002885 00000 n
+0000002953 00000 n
+0000124845 00000 n
+0000505276 00000 n
+0000003005 00000 n
+0000003073 00000 n
+0000131271 00000 n
+0000505184 00000 n
+0000003126 00000 n
+0000003225 00000 n
+0000131330 00000 n
+0000505092 00000 n
+0000003278 00000 n
+0000003328 00000 n
+0000131389 00000 n
+0000505000 00000 n
+0000003381 00000 n
+0000003439 00000 n
+0000131448 00000 n
+0000504922 00000 n
+0000003492 00000 n
+0000003546 00000 n
+0000135346 00000 n
+0000504790 00000 n
+0000003593 00000 n
+0000003671 00000 n
+0000135405 00000 n
+0000504672 00000 n
+0000003723 00000 n
+0000003768 00000 n
+0000135464 00000 n
+0000504593 00000 n
+0000003825 00000 n
+0000003879 00000 n
+0000141785 00000 n
+0000504514 00000 n
+0000003936 00000 n
+0000003983 00000 n
+0000146900 00000 n
+0000504435 00000 n
+0000004035 00000 n
+0000004115 00000 n
+0000151713 00000 n
+0000504301 00000 n
+0000004162 00000 n
+0000004235 00000 n
+0000151772 00000 n
+0000504222 00000 n
+0000004287 00000 n
+0000004439 00000 n
+0000152010 00000 n
+0000504090 00000 n
+0000004491 00000 n
+0000004599 00000 n
+0000152069 00000 n
+0000504011 00000 n
+0000004656 00000 n
+0000004706 00000 n
+0000152128 00000 n
+0000503918 00000 n
+0000004763 00000 n
+0000004825 00000 n
+0000156109 00000 n
+0000503839 00000 n
+0000004882 00000 n
+0000004956 00000 n
+0000156168 00000 n
+0000503746 00000 n
+0000005008 00000 n
+0000005115 00000 n
+0000165701 00000 n
+0000503653 00000 n
+0000005167 00000 n
+0000005347 00000 n
+0000165760 00000 n
+0000503560 00000 n
+0000005399 00000 n
+0000005471 00000 n
+0000170526 00000 n
+0000503428 00000 n
+0000005523 00000 n
+0000005618 00000 n
+0000170585 00000 n
+0000503349 00000 n
+0000005675 00000 n
+0000005778 00000 n
+0000175436 00000 n
+0000503256 00000 n
+0000005835 00000 n
+0000005934 00000 n
+0000179407 00000 n
+0000503163 00000 n
+0000005991 00000 n
+0000006128 00000 n
+0000179466 00000 n
+0000503084 00000 n
+0000006185 00000 n
+0000006269 00000 n
+0000179525 00000 n
+0000502952 00000 n
+0000006321 00000 n
+0000006362 00000 n
+0000183730 00000 n
+0000502873 00000 n
+0000006419 00000 n
+0000006515 00000 n
+0000183789 00000 n
+0000502780 00000 n
+0000006572 00000 n
+0000006700 00000 n
+0000183848 00000 n
+0000502687 00000 n
+0000006757 00000 n
+0000006835 00000 n
+0000183907 00000 n
+0000502594 00000 n
+0000006892 00000 n
+0000006987 00000 n
+0000187327 00000 n
+0000502501 00000 n
+0000007044 00000 n
+0000007143 00000 n
+0000187386 00000 n
+0000502408 00000 n
+0000007200 00000 n
+0000007276 00000 n
+0000187445 00000 n
+0000502315 00000 n
+0000007333 00000 n
+0000007417 00000 n
+0000187504 00000 n
+0000502236 00000 n
+0000007474 00000 n
+0000007578 00000 n
+0000191094 00000 n
+0000502143 00000 n
+0000007630 00000 n
+0000007709 00000 n
+0000191153 00000 n
+0000502050 00000 n
+0000007761 00000 n
+0000007840 00000 n
+0000191212 00000 n
+0000501957 00000 n
+0000007893 00000 n
+0000007984 00000 n
+0000193806 00000 n
+0000501864 00000 n
+0000008037 00000 n
+0000008129 00000 n
+0000202569 00000 n
+0000501732 00000 n
+0000008182 00000 n
+0000008243 00000 n
+0000202628 00000 n
+0000501653 00000 n
+0000008301 00000 n
+0000008366 00000 n
+0000202687 00000 n
+0000501574 00000 n
+0000008424 00000 n
+0000008475 00000 n
+0000202745 00000 n
+0000501495 00000 n
+0000008528 00000 n
+0000008638 00000 n
+0000207241 00000 n
+0000501362 00000 n
+0000008685 00000 n
+0000008719 00000 n
+0000207300 00000 n
+0000501283 00000 n
+0000008771 00000 n
+0000008851 00000 n
+0000211471 00000 n
+0000501190 00000 n
+0000008903 00000 n
+0000008975 00000 n
+0000211530 00000 n
+0000501097 00000 n
+0000009027 00000 n
+0000009067 00000 n
+0000215730 00000 n
+0000501004 00000 n
+0000009119 00000 n
+0000009175 00000 n
+0000215789 00000 n
+0000500911 00000 n
+0000009227 00000 n
+0000009268 00000 n
+0000215848 00000 n
+0000500832 00000 n
+0000009320 00000 n
+0000009400 00000 n
+0000219616 00000 n
+0000500698 00000 n
+0000009447 00000 n
+0000009488 00000 n
+0000219675 00000 n
+0000500580 00000 n
+0000009540 00000 n
+0000009628 00000 n
+0000219734 00000 n
+0000500501 00000 n
+0000009685 00000 n
+0000009752 00000 n
+0000219793 00000 n
+0000500408 00000 n
+0000009809 00000 n
+0000009879 00000 n
+0000219852 00000 n
+0000500315 00000 n
+0000009936 00000 n
+0000010004 00000 n
+0000223225 00000 n
+0000500222 00000 n
+0000010061 00000 n
+0000010129 00000 n
+0000223404 00000 n
+0000500129 00000 n
+0000010186 00000 n
+0000010284 00000 n
+0000226424 00000 n
+0000500036 00000 n
+0000010341 00000 n
+0000010412 00000 n
+0000230327 00000 n
+0000499957 00000 n
+0000010469 00000 n
+0000010567 00000 n
+0000230386 00000 n
+0000499824 00000 n
+0000010619 00000 n
+0000010689 00000 n
+0000230445 00000 n
+0000499745 00000 n
+0000010746 00000 n
+0000010829 00000 n
+0000230504 00000 n
+0000499652 00000 n
+0000010886 00000 n
+0000010966 00000 n
+0000233884 00000 n
+0000499559 00000 n
+0000011023 00000 n
+0000011094 00000 n
+0000233943 00000 n
+0000499466 00000 n
+0000011151 00000 n
+0000011254 00000 n
+0000234002 00000 n
+0000499373 00000 n
+0000011311 00000 n
+0000011404 00000 n
+0000234061 00000 n
+0000499280 00000 n
+0000011461 00000 n
+0000011558 00000 n
+0000234120 00000 n
+0000499187 00000 n
+0000011615 00000 n
+0000011676 00000 n
+0000234179 00000 n
+0000499094 00000 n
+0000011733 00000 n
+0000011848 00000 n
+0000236673 00000 n
+0000499001 00000 n
+0000011905 00000 n
+0000012003 00000 n
+0000236732 00000 n
+0000498908 00000 n
+0000012061 00000 n
+0000012143 00000 n
+0000240175 00000 n
+0000498815 00000 n
+0000012201 00000 n
+0000012283 00000 n
+0000240234 00000 n
+0000498722 00000 n
+0000012341 00000 n
+0000012418 00000 n
+0000240293 00000 n
+0000498629 00000 n
+0000012476 00000 n
+0000012538 00000 n
+0000243599 00000 n
+0000498550 00000 n
+0000012596 00000 n
+0000012670 00000 n
+0000243658 00000 n
+0000498418 00000 n
+0000012722 00000 n
+0000012771 00000 n
+0000243717 00000 n
+0000498339 00000 n
+0000012828 00000 n
+0000012893 00000 n
+0000246043 00000 n
+0000498246 00000 n
+0000012950 00000 n
+0000013038 00000 n
+0000246102 00000 n
+0000498153 00000 n
+0000013095 00000 n
+0000013174 00000 n
+0000246161 00000 n
+0000498060 00000 n
+0000013231 00000 n
+0000013307 00000 n
+0000249533 00000 n
+0000497967 00000 n
+0000013364 00000 n
+0000013498 00000 n
+0000249592 00000 n
+0000497888 00000 n
+0000013555 00000 n
+0000013610 00000 n
+0000249651 00000 n
+0000497755 00000 n
+0000013662 00000 n
+0000013754 00000 n
+0000249710 00000 n
+0000497676 00000 n
+0000013811 00000 n
+0000013919 00000 n
+0000252561 00000 n
+0000497583 00000 n
+0000013976 00000 n
+0000014077 00000 n
+0000252620 00000 n
+0000497490 00000 n
+0000014134 00000 n
+0000014235 00000 n
+0000252679 00000 n
+0000497397 00000 n
+0000014292 00000 n
+0000014387 00000 n
+0000252738 00000 n
+0000497304 00000 n
+0000014444 00000 n
+0000014521 00000 n
+0000252797 00000 n
+0000497211 00000 n
+0000014578 00000 n
+0000014664 00000 n
+0000252856 00000 n
+0000497118 00000 n
+0000014721 00000 n
+0000014777 00000 n
+0000255628 00000 n
+0000497025 00000 n
+0000014834 00000 n
+0000014906 00000 n
+0000255687 00000 n
+0000496932 00000 n
+0000014963 00000 n
+0000015046 00000 n
+0000255746 00000 n
+0000496853 00000 n
+0000015104 00000 n
+0000015198 00000 n
+0000261088 00000 n
+0000496721 00000 n
+0000015250 00000 n
+0000015335 00000 n
+0000261147 00000 n
+0000496642 00000 n
+0000015392 00000 n
+0000015429 00000 n
+0000265335 00000 n
+0000496549 00000 n
+0000015486 00000 n
+0000015559 00000 n
+0000270247 00000 n
+0000496456 00000 n
+0000015616 00000 n
+0000015687 00000 n
+0000270305 00000 n
+0000496363 00000 n
+0000015744 00000 n
+0000015832 00000 n
+0000270364 00000 n
+0000496270 00000 n
+0000015889 00000 n
+0000015968 00000 n
+0000274689 00000 n
+0000496191 00000 n
+0000016025 00000 n
+0000016095 00000 n
+0000274748 00000 n
+0000496059 00000 n
+0000016147 00000 n
+0000016204 00000 n
+0000274807 00000 n
+0000495980 00000 n
+0000016261 00000 n
+0000016333 00000 n
+0000277445 00000 n
+0000495887 00000 n
+0000016390 00000 n
+0000016460 00000 n
+0000277504 00000 n
+0000495794 00000 n
+0000016517 00000 n
+0000016634 00000 n
+0000277563 00000 n
+0000495701 00000 n
+0000016691 00000 n
+0000016751 00000 n
+0000277622 00000 n
+0000495608 00000 n
+0000016808 00000 n
+0000016898 00000 n
+0000280649 00000 n
+0000495515 00000 n
+0000016955 00000 n
+0000017034 00000 n
+0000280708 00000 n
+0000495436 00000 n
+0000017091 00000 n
+0000017221 00000 n
+0000282913 00000 n
+0000495343 00000 n
+0000017273 00000 n
+0000017344 00000 n
+0000282972 00000 n
+0000495250 00000 n
+0000017396 00000 n
+0000017456 00000 n
+0000288272 00000 n
+0000495118 00000 n
+0000017508 00000 n
+0000017587 00000 n
+0000288331 00000 n
+0000495039 00000 n
+0000017644 00000 n
+0000017735 00000 n
+0000294458 00000 n
+0000494946 00000 n
+0000017792 00000 n
+0000017882 00000 n
+0000294517 00000 n
+0000494853 00000 n
+0000017939 00000 n
+0000018031 00000 n
+0000298034 00000 n
+0000494774 00000 n
+0000018088 00000 n
+0000018149 00000 n
+0000298093 00000 n
+0000494681 00000 n
+0000018202 00000 n
+0000018269 00000 n
+0000298152 00000 n
+0000494588 00000 n
+0000018322 00000 n
+0000018388 00000 n
+0000301527 00000 n
+0000494456 00000 n
+0000018441 00000 n
+0000018493 00000 n
+0000301586 00000 n
+0000494377 00000 n
+0000018551 00000 n
+0000018633 00000 n
+0000301645 00000 n
+0000494284 00000 n
+0000018691 00000 n
+0000018861 00000 n
+0000301704 00000 n
+0000494191 00000 n
+0000018919 00000 n
+0000019063 00000 n
+0000304057 00000 n
+0000494098 00000 n
+0000019121 00000 n
+0000019211 00000 n
+0000304116 00000 n
+0000494005 00000 n
+0000019269 00000 n
+0000019346 00000 n
+0000304175 00000 n
+0000493912 00000 n
+0000019404 00000 n
+0000019456 00000 n
+0000307534 00000 n
+0000493833 00000 n
+0000019514 00000 n
+0000019586 00000 n
+0000307593 00000 n
+0000493701 00000 n
+0000019639 00000 n
+0000019745 00000 n
+0000307652 00000 n
+0000493622 00000 n
+0000019803 00000 n
+0000019869 00000 n
+0000312833 00000 n
+0000493529 00000 n
+0000019927 00000 n
+0000019987 00000 n
+0000312892 00000 n
+0000493436 00000 n
+0000020045 00000 n
+0000020116 00000 n
+0000312951 00000 n
+0000493357 00000 n
+0000020174 00000 n
+0000020251 00000 n
+0000313010 00000 n
+0000493225 00000 n
+0000020304 00000 n
+0000020387 00000 n
+0000313069 00000 n
+0000493146 00000 n
+0000020445 00000 n
+0000020499 00000 n
+0000313128 00000 n
+0000493053 00000 n
+0000020557 00000 n
+0000020616 00000 n
+0000316793 00000 n
+0000492974 00000 n
+0000020674 00000 n
+0000020737 00000 n
+0000316852 00000 n
+0000492842 00000 n
+0000020790 00000 n
+0000020884 00000 n
+0000316911 00000 n
+0000492763 00000 n
+0000020942 00000 n
+0000021039 00000 n
+0000320655 00000 n
+0000492670 00000 n
+0000021097 00000 n
+0000021181 00000 n
+0000320714 00000 n
+0000492591 00000 n
+0000021239 00000 n
+0000021275 00000 n
+0000320773 00000 n
+0000492498 00000 n
+0000021328 00000 n
+0000021391 00000 n
+0000329994 00000 n
+0000492419 00000 n
+0000021444 00000 n
+0000021525 00000 n
+0000330053 00000 n
+0000492286 00000 n
+0000021572 00000 n
+0000021622 00000 n
+0000330112 00000 n
+0000492207 00000 n
+0000021674 00000 n
+0000021751 00000 n
+0000335464 00000 n
+0000492114 00000 n
+0000021803 00000 n
+0000021897 00000 n
+0000335523 00000 n
+0000492021 00000 n
+0000021949 00000 n
+0000022043 00000 n
+0000335581 00000 n
+0000491942 00000 n
+0000022095 00000 n
+0000022235 00000 n
+0000335639 00000 n
+0000491809 00000 n
+0000022283 00000 n
+0000022342 00000 n
+0000335697 00000 n
+0000491730 00000 n
+0000022395 00000 n
+0000022433 00000 n
+0000338989 00000 n
+0000491651 00000 n
+0000022486 00000 n
+0000022527 00000 n
+0000339048 00000 n
+0000491518 00000 n
+0000022575 00000 n
+0000022635 00000 n
+0000339107 00000 n
+0000491400 00000 n
+0000022688 00000 n
+0000022766 00000 n
+0000339166 00000 n
+0000491321 00000 n
+0000022824 00000 n
+0000022868 00000 n
+0000339225 00000 n
+0000491242 00000 n
+0000022926 00000 n
+0000023008 00000 n
+0000343075 00000 n
+0000491110 00000 n
+0000023061 00000 n
+0000023097 00000 n
+0000343134 00000 n
+0000491031 00000 n
+0000023155 00000 n
+0000023212 00000 n
+0000347231 00000 n
+0000490938 00000 n
+0000023270 00000 n
+0000023413 00000 n
+0000347290 00000 n
+0000490845 00000 n
+0000023471 00000 n
+0000023541 00000 n
+0000347349 00000 n
+0000490752 00000 n
+0000023599 00000 n
+0000023710 00000 n
+0000347408 00000 n
+0000490673 00000 n
+0000023768 00000 n
+0000023858 00000 n
+0000351137 00000 n
+0000490541 00000 n
+0000023911 00000 n
+0000023962 00000 n
+0000351196 00000 n
+0000490462 00000 n
+0000024020 00000 n
+0000024095 00000 n
+0000351255 00000 n
+0000490383 00000 n
+0000024153 00000 n
+0000024222 00000 n
+0000351314 00000 n
+0000490290 00000 n
+0000024275 00000 n
+0000024338 00000 n
+0000351373 00000 n
+0000490211 00000 n
+0000024391 00000 n
+0000024453 00000 n
+0000351432 00000 n
+0000490092 00000 n
+0000024501 00000 n
+0000024566 00000 n
+0000351491 00000 n
+0000490013 00000 n
+0000024619 00000 n
+0000024679 00000 n
+0000357312 00000 n
+0000489920 00000 n
+0000024732 00000 n
+0000024794 00000 n
+0000357371 00000 n
+0000489827 00000 n
+0000024847 00000 n
+0000024883 00000 n
+0000357430 00000 n
+0000489734 00000 n
+0000024936 00000 n
+0000025022 00000 n
+0000357489 00000 n
+0000489655 00000 n
+0000025075 00000 n
+0000025164 00000 n
+0000028480 00000 n
+0000032622 00000 n
+0000025216 00000 n
+0000032448 00000 n
+0000032506 00000 n
+0000486851 00000 n
+0000477827 00000 n
+0000486679 00000 n
+0000476460 00000 n
+0000454875 00000 n
+0000476285 00000 n
+0000454578 00000 n
+0000450931 00000 n
+0000454400 00000 n
+0000449747 00000 n
+0000431523 00000 n
+0000449572 00000 n
+0000032564 00000 n
+0000028798 00000 n
+0000028953 00000 n
+0000029113 00000 n
+0000029272 00000 n
+0000029431 00000 n
+0000029591 00000 n
+0000431086 00000 n
+0000428855 00000 n
+0000430923 00000 n
+0000029750 00000 n
+0000029910 00000 n
+0000030070 00000 n
+0000030225 00000 n
+0000030385 00000 n
+0000030545 00000 n
+0000030699 00000 n
+0000030859 00000 n
+0000031019 00000 n
+0000031179 00000 n
+0000031336 00000 n
+0000031496 00000 n
+0000031651 00000 n
+0000031811 00000 n
+0000031971 00000 n
+0000032130 00000 n
+0000427399 00000 n
+0000405373 00000 n
+0000427226 00000 n
+0000032290 00000 n
+0000487761 00000 n
+0000043042 00000 n
+0000036563 00000 n
+0000032759 00000 n
+0000042984 00000 n
+0000036993 00000 n
+0000037153 00000 n
+0000037313 00000 n
+0000037473 00000 n
+0000404735 00000 n
+0000402741 00000 n
+0000404571 00000 n
+0000037632 00000 n
+0000037793 00000 n
+0000037954 00000 n
+0000038112 00000 n
+0000038273 00000 n
+0000038428 00000 n
+0000038588 00000 n
+0000401642 00000 n
+0000384653 00000 n
+0000401463 00000 n
+0000038753 00000 n
+0000038919 00000 n
+0000039079 00000 n
+0000039234 00000 n
+0000039394 00000 n
+0000039554 00000 n
+0000039712 00000 n
+0000039878 00000 n
+0000040044 00000 n
+0000040209 00000 n
+0000040369 00000 n
+0000040528 00000 n
+0000040688 00000 n
+0000040848 00000 n
+0000041007 00000 n
+0000041173 00000 n
+0000041339 00000 n
+0000041504 00000 n
+0000041669 00000 n
+0000041834 00000 n
+0000041994 00000 n
+0000042160 00000 n
+0000042326 00000 n
+0000042491 00000 n
+0000042657 00000 n
+0000042821 00000 n
+0000053335 00000 n
+0000046994 00000 n
+0000043166 00000 n
+0000053277 00000 n
+0000047416 00000 n
+0000047582 00000 n
+0000047748 00000 n
+0000047914 00000 n
+0000048074 00000 n
+0000048233 00000 n
+0000048393 00000 n
+0000048552 00000 n
+0000048713 00000 n
+0000048880 00000 n
+0000049047 00000 n
+0000049208 00000 n
+0000049362 00000 n
+0000049522 00000 n
+0000049680 00000 n
+0000049840 00000 n
+0000050000 00000 n
+0000050160 00000 n
+0000050319 00000 n
+0000050474 00000 n
+0000050633 00000 n
+0000050799 00000 n
+0000050965 00000 n
+0000051131 00000 n
+0000051297 00000 n
+0000051462 00000 n
+0000051628 00000 n
+0000051794 00000 n
+0000051954 00000 n
+0000052120 00000 n
+0000052285 00000 n
+0000052451 00000 n
+0000052617 00000 n
+0000052783 00000 n
+0000052949 00000 n
+0000053114 00000 n
+0000063676 00000 n
+0000057082 00000 n
+0000053459 00000 n
+0000063618 00000 n
+0000057512 00000 n
+0000057678 00000 n
+0000057845 00000 n
+0000058012 00000 n
+0000058177 00000 n
+0000058344 00000 n
+0000058511 00000 n
+0000058669 00000 n
+0000058835 00000 n
+0000059001 00000 n
+0000059167 00000 n
+0000059333 00000 n
+0000059497 00000 n
+0000059662 00000 n
+0000059825 00000 n
+0000059985 00000 n
+0000060151 00000 n
+0000060317 00000 n
+0000060483 00000 n
+0000060649 00000 n
+0000060814 00000 n
+0000060980 00000 n
+0000061146 00000 n
+0000061311 00000 n
+0000061477 00000 n
+0000061644 00000 n
+0000061804 00000 n
+0000061969 00000 n
+0000062134 00000 n
+0000062300 00000 n
+0000062466 00000 n
+0000062632 00000 n
+0000062798 00000 n
+0000062957 00000 n
+0000063123 00000 n
+0000063289 00000 n
+0000063454 00000 n
+0000074214 00000 n
+0000067474 00000 n
+0000063787 00000 n
+0000074156 00000 n
+0000067912 00000 n
+0000068078 00000 n
+0000068244 00000 n
+0000068410 00000 n
+0000068573 00000 n
+0000068733 00000 n
+0000068893 00000 n
+0000069052 00000 n
+0000069218 00000 n
+0000069383 00000 n
+0000069546 00000 n
+0000069712 00000 n
+0000069873 00000 n
+0000070034 00000 n
+0000070193 00000 n
+0000070359 00000 n
+0000070526 00000 n
+0000070690 00000 n
+0000070857 00000 n
+0000071023 00000 n
+0000071190 00000 n
+0000071357 00000 n
+0000071523 00000 n
+0000071690 00000 n
+0000071851 00000 n
+0000072017 00000 n
+0000072183 00000 n
+0000072350 00000 n
+0000072517 00000 n
+0000072678 00000 n
+0000072845 00000 n
+0000073011 00000 n
+0000073178 00000 n
+0000073339 00000 n
+0000073506 00000 n
+0000073673 00000 n
+0000073839 00000 n
+0000073997 00000 n
+0000082893 00000 n
+0000077384 00000 n
+0000074299 00000 n
+0000082835 00000 n
+0000077793 00000 n
+0000077948 00000 n
+0000078108 00000 n
+0000078268 00000 n
+0000078428 00000 n
+0000078589 00000 n
+0000078750 00000 n
+0000078907 00000 n
+0000079069 00000 n
+0000079231 00000 n
+0000079386 00000 n
+0000079548 00000 n
+0000079715 00000 n
+0000079883 00000 n
+0000080045 00000 n
+0000080213 00000 n
+0000080381 00000 n
+0000080548 00000 n
+0000080716 00000 n
+0000080883 00000 n
+0000081051 00000 n
+0000081213 00000 n
+0000081381 00000 n
+0000081549 00000 n
+0000081711 00000 n
+0000081873 00000 n
+0000082030 00000 n
+0000082192 00000 n
+0000082354 00000 n
+0000082516 00000 n
+0000082673 00000 n
+0000087617 00000 n
+0000087015 00000 n
+0000083004 00000 n
+0000087327 00000 n
+0000087162 00000 n
+0000487879 00000 n
+0000091413 00000 n
+0000090995 00000 n
+0000087742 00000 n
+0000091121 00000 n
+0000384326 00000 n
+0000382346 00000 n
+0000384160 00000 n
+0000095797 00000 n
+0000095026 00000 n
+0000091552 00000 n
+0000095563 00000 n
+0000095182 00000 n
+0000095401 00000 n
+0000100329 00000 n
+0000099707 00000 n
+0000095896 00000 n
+0000100211 00000 n
+0000099863 00000 n
+0000100025 00000 n
+0000105313 00000 n
+0000103548 00000 n
+0000100441 00000 n
+0000105137 00000 n
+0000103749 00000 n
+0000103954 00000 n
+0000104163 00000 n
+0000104367 00000 n
+0000104565 00000 n
+0000104762 00000 n
+0000104944 00000 n
+0000111059 00000 n
+0000108693 00000 n
+0000105439 00000 n
+0000110883 00000 n
+0000108921 00000 n
+0000109124 00000 n
+0000109323 00000 n
+0000109509 00000 n
+0000109705 00000 n
+0000109894 00000 n
+0000110092 00000 n
+0000110290 00000 n
+0000110488 00000 n
+0000110684 00000 n
+0000116349 00000 n
+0000114710 00000 n
+0000111184 00000 n
+0000116115 00000 n
+0000114902 00000 n
+0000115122 00000 n
+0000115342 00000 n
+0000115561 00000 n
+0000115742 00000 n
+0000115934 00000 n
+0000488004 00000 n
+0000120790 00000 n
+0000119962 00000 n
+0000116474 00000 n
+0000120441 00000 n
+0000120118 00000 n
+0000120279 00000 n
+0000381846 00000 n
+0000371238 00000 n
+0000381671 00000 n
+0000124904 00000 n
+0000124362 00000 n
+0000120929 00000 n
+0000124667 00000 n
+0000124509 00000 n
+0000131507 00000 n
+0000129346 00000 n
+0000125056 00000 n
+0000131211 00000 n
+0000129565 00000 n
+0000129757 00000 n
+0000129931 00000 n
+0000130150 00000 n
+0000130311 00000 n
+0000130495 00000 n
+0000130668 00000 n
+0000130857 00000 n
+0000131049 00000 n
+0000135523 00000 n
+0000134802 00000 n
+0000131659 00000 n
+0000135286 00000 n
+0000134958 00000 n
+0000135124 00000 n
+0000370697 00000 n
+0000359549 00000 n
+0000370515 00000 n
+0000141843 00000 n
+0000140220 00000 n
+0000135649 00000 n
+0000141725 00000 n
+0000140421 00000 n
+0000140600 00000 n
+0000140796 00000 n
+0000140982 00000 n
+0000141166 00000 n
+0000141368 00000 n
+0000141542 00000 n
+0000146959 00000 n
+0000145936 00000 n
+0000141955 00000 n
+0000146840 00000 n
+0000146110 00000 n
+0000146290 00000 n
+0000146480 00000 n
+0000146663 00000 n
+0000488129 00000 n
+0000152187 00000 n
+0000150262 00000 n
+0000147071 00000 n
+0000151653 00000 n
+0000150463 00000 n
+0000151831 00000 n
+0000150657 00000 n
+0000150824 00000 n
+0000150990 00000 n
+0000151891 00000 n
+0000151157 00000 n
+0000151950 00000 n
+0000151319 00000 n
+0000151486 00000 n
+0000156346 00000 n
+0000155385 00000 n
+0000152326 00000 n
+0000156049 00000 n
+0000155550 00000 n
+0000155717 00000 n
+0000155882 00000 n
+0000156227 00000 n
+0000156287 00000 n
+0000160983 00000 n
+0000160023 00000 n
+0000156484 00000 n
+0000160803 00000 n
+0000160863 00000 n
+0000160188 00000 n
+0000160393 00000 n
+0000160596 00000 n
+0000160923 00000 n
+0000165819 00000 n
+0000165303 00000 n
+0000161095 00000 n
+0000165641 00000 n
+0000165450 00000 n
+0000170643 00000 n
+0000169759 00000 n
+0000165944 00000 n
+0000170466 00000 n
+0000169924 00000 n
+0000170084 00000 n
+0000170251 00000 n
+0000175495 00000 n
+0000174897 00000 n
+0000170781 00000 n
+0000175376 00000 n
+0000175053 00000 n
+0000175213 00000 n
+0000488254 00000 n
+0000179584 00000 n
+0000178867 00000 n
+0000175634 00000 n
+0000179347 00000 n
+0000179023 00000 n
+0000179185 00000 n
+0000183966 00000 n
+0000183149 00000 n
+0000179723 00000 n
+0000183670 00000 n
+0000183305 00000 n
+0000183508 00000 n
+0000187563 00000 n
+0000187141 00000 n
+0000184105 00000 n
+0000187267 00000 n
+0000191271 00000 n
+0000190908 00000 n
+0000187729 00000 n
+0000191034 00000 n
+0000193865 00000 n
+0000193620 00000 n
+0000191409 00000 n
+0000193746 00000 n
+0000198694 00000 n
+0000197123 00000 n
+0000193990 00000 n
+0000198634 00000 n
+0000197324 00000 n
+0000197508 00000 n
+0000197692 00000 n
+0000197877 00000 n
+0000198063 00000 n
+0000198254 00000 n
+0000198445 00000 n
+0000488379 00000 n
+0000202804 00000 n
+0000202200 00000 n
+0000198819 00000 n
+0000202509 00000 n
+0000202347 00000 n
+0000207358 00000 n
+0000206447 00000 n
+0000202957 00000 n
+0000207181 00000 n
+0000206612 00000 n
+0000206813 00000 n
+0000207013 00000 n
+0000211588 00000 n
+0000210328 00000 n
+0000207497 00000 n
+0000211411 00000 n
+0000210511 00000 n
+0000210682 00000 n
+0000210852 00000 n
+0000211036 00000 n
+0000211221 00000 n
+0000215907 00000 n
+0000215352 00000 n
+0000211713 00000 n
+0000215670 00000 n
+0000215499 00000 n
+0000219911 00000 n
+0000219250 00000 n
+0000216060 00000 n
+0000219556 00000 n
+0000219397 00000 n
+0000223463 00000 n
+0000223039 00000 n
+0000220050 00000 n
+0000223165 00000 n
+0000223284 00000 n
+0000223344 00000 n
+0000488504 00000 n
+0000226483 00000 n
+0000226238 00000 n
+0000223589 00000 n
+0000226364 00000 n
+0000230563 00000 n
+0000229931 00000 n
+0000226595 00000 n
+0000230267 00000 n
+0000230078 00000 n
+0000234238 00000 n
+0000233340 00000 n
+0000230715 00000 n
+0000233824 00000 n
+0000233496 00000 n
+0000233658 00000 n
+0000236791 00000 n
+0000236487 00000 n
+0000234377 00000 n
+0000236613 00000 n
+0000240352 00000 n
+0000239632 00000 n
+0000236916 00000 n
+0000240115 00000 n
+0000239788 00000 n
+0000239954 00000 n
+0000243776 00000 n
+0000243413 00000 n
+0000240490 00000 n
+0000243539 00000 n
+0000488629 00000 n
+0000246220 00000 n
+0000245857 00000 n
+0000243914 00000 n
+0000245983 00000 n
+0000249769 00000 n
+0000248539 00000 n
+0000246359 00000 n
+0000249473 00000 n
+0000248713 00000 n
+0000248913 00000 n
+0000249107 00000 n
+0000249291 00000 n
+0000252915 00000 n
+0000252375 00000 n
+0000249908 00000 n
+0000252501 00000 n
+0000255805 00000 n
+0000255442 00000 n
+0000253068 00000 n
+0000255568 00000 n
+0000261206 00000 n
+0000260374 00000 n
+0000255930 00000 n
+0000261028 00000 n
+0000260539 00000 n
+0000260701 00000 n
+0000260867 00000 n
+0000265394 00000 n
+0000264527 00000 n
+0000261344 00000 n
+0000265275 00000 n
+0000264692 00000 n
+0000264879 00000 n
+0000265088 00000 n
+0000488754 00000 n
+0000270423 00000 n
+0000269316 00000 n
+0000265519 00000 n
+0000270187 00000 n
+0000269490 00000 n
+0000269659 00000 n
+0000269825 00000 n
+0000269996 00000 n
+0000274866 00000 n
+0000274141 00000 n
+0000270562 00000 n
+0000274629 00000 n
+0000274297 00000 n
+0000274464 00000 n
+0000277681 00000 n
+0000277259 00000 n
+0000274978 00000 n
+0000277385 00000 n
+0000280767 00000 n
+0000280463 00000 n
+0000277793 00000 n
+0000280589 00000 n
+0000283031 00000 n
+0000282727 00000 n
+0000280892 00000 n
+0000282853 00000 n
+0000288390 00000 n
+0000287133 00000 n
+0000283156 00000 n
+0000288212 00000 n
+0000287316 00000 n
+0000287479 00000 n
+0000287663 00000 n
+0000287827 00000 n
+0000288018 00000 n
+0000488879 00000 n
+0000294576 00000 n
+0000292101 00000 n
+0000288528 00000 n
+0000294398 00000 n
+0000292338 00000 n
+0000292535 00000 n
+0000292724 00000 n
+0000292910 00000 n
+0000293091 00000 n
+0000293257 00000 n
+0000293420 00000 n
+0000293612 00000 n
+0000293802 00000 n
+0000293991 00000 n
+0000294195 00000 n
+0000298211 00000 n
+0000297848 00000 n
+0000294714 00000 n
+0000297974 00000 n
+0000301763 00000 n
+0000301341 00000 n
+0000298336 00000 n
+0000301467 00000 n
+0000304234 00000 n
+0000303871 00000 n
+0000301888 00000 n
+0000303997 00000 n
+0000307711 00000 n
+0000307348 00000 n
+0000304359 00000 n
+0000307474 00000 n
+0000313247 00000 n
+0000311387 00000 n
+0000307836 00000 n
+0000312773 00000 n
+0000311579 00000 n
+0000311742 00000 n
+0000311966 00000 n
+0000312190 00000 n
+0000313187 00000 n
+0000312387 00000 n
+0000312575 00000 n
+0000489004 00000 n
+0000316970 00000 n
+0000315810 00000 n
+0000313372 00000 n
+0000316733 00000 n
+0000315984 00000 n
+0000316186 00000 n
+0000316377 00000 n
+0000316565 00000 n
+0000320832 00000 n
+0000320469 00000 n
+0000317082 00000 n
+0000320595 00000 n
+0000323616 00000 n
+0000323430 00000 n
+0000320970 00000 n
+0000323556 00000 n
+0000326738 00000 n
+0000326552 00000 n
+0000323741 00000 n
+0000326678 00000 n
+0000330171 00000 n
+0000329808 00000 n
+0000326876 00000 n
+0000329934 00000 n
+0000335756 00000 n
+0000334234 00000 n
+0000330323 00000 n
+0000335404 00000 n
+0000334426 00000 n
+0000334588 00000 n
+0000334750 00000 n
+0000334911 00000 n
+0000335073 00000 n
+0000335241 00000 n
+0000489129 00000 n
+0000339284 00000 n
+0000338597 00000 n
+0000335909 00000 n
+0000338929 00000 n
+0000338744 00000 n
+0000343193 00000 n
+0000341852 00000 n
+0000339409 00000 n
+0000343015 00000 n
+0000342035 00000 n
+0000342212 00000 n
+0000342405 00000 n
+0000342600 00000 n
+0000342812 00000 n
+0000347467 00000 n
+0000346200 00000 n
+0000343319 00000 n
+0000347171 00000 n
+0000346374 00000 n
+0000346572 00000 n
+0000346765 00000 n
+0000346971 00000 n
+0000351550 00000 n
+0000350178 00000 n
+0000347606 00000 n
+0000351077 00000 n
+0000350352 00000 n
+0000350515 00000 n
+0000350715 00000 n
+0000350900 00000 n
+0000357548 00000 n
+0000355434 00000 n
+0000351676 00000 n
+0000357252 00000 n
+0000355644 00000 n
+0000355837 00000 n
+0000356027 00000 n
+0000356218 00000 n
+0000356423 00000 n
+0000356636 00000 n
+0000356828 00000 n
+0000357041 00000 n
+0000357660 00000 n
+0000370995 00000 n
+0000382117 00000 n
+0000384564 00000 n
+0000384539 00000 n
+0000402094 00000 n
+0000405202 00000 n
+0000404979 00000 n
+0000428172 00000 n
+0000431393 00000 n
+0000431308 00000 n
+0000450253 00000 n
+0000454804 00000 n
+0000477112 00000 n
+0000487164 00000 n
+0000489254 00000 n
+0000489379 00000 n
+0000489505 00000 n
+0000489578 00000 n
+0000507684 00000 n
+0000514614 00000 n
+0000514655 00000 n
+0000514695 00000 n
+0000514829 00000 n
+trailer
+<<
+/Size 1514
+/Root 1512 0 R
+/Info 1513 0 R
+/ID [<9691F6998412E685218802699705E544> <9691F6998412E685218802699705E544>]
+>>
+startxref
+515110
+%%EOF
diff --git a/help/es-tex-faq/FAQ-CervanTeX.sgml b/help/es-tex-faq/FAQ-CervanTeX.sgml
new file mode 100644
index 0000000000..8408902098
--- /dev/null
+++ b/help/es-tex-faq/FAQ-CervanTeX.sgml
@@ -0,0 +1,5055 @@
+<!DOCTYPE linuxdoc SYSTEM>
+<!-- $Id: FAQ-CervanTeX.sgml,v 1.97 2006-05-09 15:12:22 agmartin Exp $ -->
+ <article>
+ <title>FAQ de Cervan&tex;</title>
+ <author>Cervan&tex;
+<date> Versin 1.97 de 2006-05-09 (15:12:22)
+
+ <abstract>
+ Esta es la lista de preguntas y respuestas frecuentes del grupo de usuarios
+ hispanohablantes de &tex;/&latex; Cervan&tex;. Est basada en las
+ preguntas que se repiten con frecuencia en los distintos foros y en
+ algunas contribuciones adicionales interesantes. Aunque todas ellas son
+ preguntas razonables, especialmente para un nefito, resulta un poco
+ <em/repetitivo/ verlas aparecer continuamente en los distintos foros de
+ discusin sobre &tex;/&latex;. Por esta razn se han intentado reunir en
+ esta FAQ. Se ruega echarle un vistazo antes de preguntar en la lista de
+ correo o en el grupo de noticias cosas que ya se han preguntado y
+ respondido mltiples veces y que estn en esta FAQ.
+ </abstract>
+ <toc>
+ <!-- ********************************************************* -->
+ <sect>Qu son &tex; y sus programas hermanos?
+ <!-- ********************************************************* -->
+ <sect1>Qu es &tex;?
+ <!-- ================================= -->
+ <p>
+ &tex; es un sistema de composicin de textos de alta calidad creado
+ por Donald E. Knuth, dirigido en particular a aqullos textos que
+ contienen una gran cantidad de expresiones matemticas. No debe
+ pensarse en &tex; como un procesador de palabras del tipo WYSIWYG, un
+ archivo <tt/tex/ es un archivo <tt/ASCII/ donde est el texto que
+ deseamos imprimir
+ junto con determinadas instrucciones sobre como debe ser tratado, que
+ debe ser procesado por un compilador (el programa &tex;). ste
+ devuelve un archivo que es independiente de la plataforma y que es el
+ que finalmente se transformar al lenguaje de impresora y se
+ imprimir.
+ <p>
+ Para escribir &tex; Knuth desarroll un sistema de <em/programacin
+ ilustrada/
+ denominado WEB. Las fuentes WEB de &tex; estn disponibles
+ gratuitamente, lo mismo que herramientas para convertir el original en
+ WEB en un programa que pueda compilarse y un texto que pueda
+ imprimirse. El sistema WEB proporciona herramientas para compilar
+ &tex; en distintos sistemas operativos.
+ <p>
+ &tex; en s es un procesador de macros, con una alta capacidad de
+ programacin. Utilizar &tex; puro reviste una cierta dificultad, por
+ lo que Knuth suministr una serie de macros para &tex; a las que se
+ denomin <em/plain &tex;/. Estas macros son el conjunto mnimo de
+ macros que se pueden utilizar de forma eficaz con &tex; e incluyen
+ algunos ejemplos de uso de rdenes &tex; de alto nivel. Cuando alguien
+ afirma programar en &tex; normalmente se refiere a que lo hace en
+ <em/plain &tex;/
+
+ <sect1>Por qu debo asegurarme de usar &tex; 3.X?
+ <!-- ========================================= -->
+ <p>
+ Bueno, hace unos aos (en el ***), diversas personas (y la existencia de
+ ML-&tex; :-) convencieron a Knuth de que el soporte que &tex;
+ proporcionaba a otros idiomas era insuficiente. As que lo modific de
+ la siguiente manera:
+ <itemize>
+ <item>
+ Soporte total a los 8 bits. &tex; puede ahora leer los 256 diferentes
+ cdigos. Los nuevos caracteres son cdigos utilizables como
+ cualquier otro. Antes haba algo, pero no bastante. Ahora podemos
+ hacer que <tt/^^e1/ sea la <tt//.
+ <item>
+ &tex; soporta ahora 256 tablas de particin simultneamente.
+ Puedes escribir:
+ <quote>
+ ... there is a difference between especially and
+ {<tt>\language\spanish</tt> especialmente} in that...
+ </quote>
+ y &tex; compondr el prrafo con las reglas de ingls, menos
+ <em/especialmente/ que lo har con las del castellano.
+
+ <item>
+ Dos nuevas macros <tt>\lefthyphenmin</tt> y
+ <tt>\righthyphenmin</tt> que controlan el tamao del trozo mnimo
+ que se puede dejar al partir palabras. Previamente estaban fijos a
+ 2 y 3, respectivamente.
+ <p>
+ Pero lo fundamental es que &tex; 2.X no existe ya. Hay que
+ cambiar tarde o temprano. No hay parches ni arreglos para &tex;
+ 2.X.
+ <p>
+ Por cierto, la versin actual es la 3.14159, y la versin actual
+ de METAFONT es la 2.718. La ltima versin de &tex; ser la
+ versin <em/pi/
+ (como ltima voluntad de Donald Knuth), y ya no habr ms
+ cambios. Y el ltimo METAFONT ser versin <em/e/.
+ </itemize>
+
+ <sect1>Si &tex es tan bueno, por qu es gratuito?<label id="tex-gratis">
+ <!-- =============================================================== -->
+ <p>
+ Porque Knuth lo decidi as, y no parece molestarle que otros ganen dinero
+ vendiendo productos y servicios basados en &tex;. De hecho, aunque
+ algunas herramientas que se usan junto a &tex; se ofrecen bajo la
+ <em/GNU General Public License (Copyleft)/, &tex; en s ni siquiera
+ tiene esa restriccin. La nica restriccin impuesta por Knuth es que
+ debe dar el mismo resultado en todas las implementaciones, para
+ garantizar la absoluta portabilidad de los documentos escritos con
+ &tex;.
+ <p>
+ Algunas empresas ofrecen implementaciones comerciales de &tex;/&latex; con
+ elementos propios (vase la seccin <ref id="tex-de-pago"
+ name="Implementaciones comerciales">)
+
+ <sect1>Qu es &latex;?
+ <!-- ============== -->
+ <p>
+ &latex; es un paquete de macros para &tex;, originalmente escrito por
+ Leslie
+ Lamport para proporcionar un sistema de procesamiento de documentos
+ ms simple de uso que &tex;, pero con toda su potencia. &latex;
+ proporciona una serie de rdenes para describir la estructura del
+ documento, de forma que el usuario final no deba pensar mucho en la
+ presentacin. Mediante distintas clases de documentos y paquetes
+ adicionales, el mismo documento puede producirse con muchos diferentes
+ aspectos.
+
+ <sect1>Qu es &latexe;?, Por qu debo usarlo si me va bien con el otro (&latex;209)?
+ <!-- =============================================================== -->
+ <p>
+ &latexe; es la nueva versin estndar de &latex;, preparada y
+ mantenida por el
+ equipo del proyecto &latex;3. Es la versin actual de &latex; y est
+ disponible desde cualquier punto CTAN, en
+
+<tscreen><verb>
+CTAN:macros/latex
+</verb></tscreen>
+ Desde que es oficial, &latex; = &latexe; y el otro ahora se llama
+ &latex; 2.09 y est obsoleto.
+ <p>
+ &latexe; es compatible hacia atrs con &latex;209, pero incluye toda
+ una serie
+ de caractersticas nuevas.
+ <p>
+ Hay una razn de peso para no usar &latex; 2.09: Solamente &latex; est
+ mantenido, lo cual quiere decir (entre otras cosas) que si encontramos
+ un error hay gente a quien decrselo y puede que lo arreglen, mientras
+ que si tenemos problemas con &latex; 2.09 nadie nos har caso, porque
+ &latex; 2.09 ya no va a cambiar jams.
+
+ <sect1>Qu son los paquetes de la AMS (AMS-&tex;, AMS-&latex;)?
+ <!-- ======================================================== -->
+ <p>
+ AMS-&tex; es un paquete de macros para &tex;. Escrito originalmente
+ por Michael
+ Spivak para la Sociedad Americana de Matemticas (AMS) entre 1983 y
+ 1985. Est basado en <em/plain &tex;/, pero proporciona ms medios
+ para producir frmulas matemticas de aspecto profesional con menor
+ esfuerzo por parte de los autores, con un gran cuidado en aspectos
+ como el tamao y la posicin de las frmulas. Entre los aspectos
+ tratados se encuentran las ecuaciones de ms de una lnea, la
+ numeracin de ecuaciones, los puntos de elipsis, las matrices, los
+ acentos dobles, sub y superndices en varios niveles, as como otras
+ cosas.
+ <p>
+ Segn fue aumentando la popularidad de &latex; la AMS desarroll
+ AMS-&latex;,
+ que consiste en una coleccin de clases y paquetes para &latex; que
+ ofrece a los autores la funcionalidad de AMS-&tex;.
+
+ <sect1>Qu es METAFONT?
+ <!-- ================================= -->
+ <p>
+ Donald Knuth escribi METAFONT al mismo tiempo que &tex;. Mientras
+ &tex define
+ la colocacin de los elementos en una pgina, METAFONT define cmo son
+ estos elementos, sus tamaos y cmo se crean.
+ <p>
+ El lenguaje utilizado por METAFONT para definir tipos permite describir
+ distintas cosas, la geometra del grafo, las propiedades del elemento
+ de impresin, informacin adicional que permita distinguir entre
+ distintos tamaos del mismo tipo, o diferencias entre dos tipos que
+ pertenecen a la misma o distinta familia.
+ <p>
+ Aunque Knuth y otros han diseado un buen nmero de tipos utilizando
+ METAFONT,
+ el diseo de tipos en general y en particular con METAFONT es un rea
+ muy especializada que nunca deber abordar el usuario
+ normal. Simplemente METAFONT deber estar instalado para cuando &tex;
+ quiera generar copias de nuevos tipos.
+
+ <!-- ********************************************************* -->
+ <sect>Qu ventajas e inconvenientes tiene &tex;/&latex;?
+ <!-- ********************************************************* -->
+ <!-- <p>
+ Esta seccin est fuertemente basada en la pgina
+ <htmlurl url="http://www.esi.us.es/~gonfer/tex.html" name="http://www.esi.us.es/~gonfer/tex.html">
+ de Antonio Gonzlez, de la Universidad de Sevilla -->
+
+ <sect1>Ventajas frente a otros procesadores.
+ <!-- ================================= -->
+ <p>
+ Adems de las ventajas que aqu se describen, en la pgina
+ <htmlurl
+ url="http://www.cudenver.edu/~hgreenbe/courses/texinfo/wordvslatex.html"
+ name="http://www.cudenver.edu/~hgreenbe/courses/texinfo/wordvslatex.html">
+ se recopilan (en ingls) buen numero de mensajes con una informacin
+ detallada de las razones que han llevado a toda una serie de personas a
+ utilizar &latex;
+ <descrip>
+ <tag/Funciona y es estable y multiplataforma./
+ Tan simple como eso, &latex; no se <em/cuelga/, el formato de los
+ archivos es mucho ms estable que en otros procesadores y
+ cualquier cambio es primero profundamente meditado y despus
+ profusamente documentado, existen implementaciones para distintas
+ plataformas y en todas el resultado es exactamente el mismo (si se
+ tienen los mismos estilos y tipos, claro).
+
+ <tag/Alta calidad en la edicin de ecuaciones./
+ Esta es siempre la razn ltima por la que un usuario cientfico
+ se inclina hacia &latex;. Este procesador ajusta los tamaos de
+ parntesis, integrales, subndices y superndices, alinea los
+ elementos de las matrices, construye cajas, etc.
+
+ <tag/&latex; permite redactar fcilmente documentos estructurados./
+ A travs de distintas clases de documento y de su conjunto de
+ macros, &latex; posibilita escribir textos dividindolos en
+ captulos, secciones, subsecciones, controlando en todo momento la
+ numeracin y las referencias cruzadas. Construye ndices de
+ contenidos, tablas o figuras. Ajusta los tamaos y tipos de letras
+ segn la parte del documento en que se hallen.
+
+ <tag/Facilidad en la construccin de macros y rdenes./
+ A poco de comenzar a usar este procesador, el usuario se encuentra
+ definiendo o redefiniendo rdenes para que stas se ajusten a sus
+ preferencias personales. Por ejemplo, es posible que una
+ determinada expresin aparezca repetidas veces en el texto. Nada
+ mas fcil que definir una orden que reemplace a todo un bloque. O
+ bien, es posible que no guste la forma en que &latex; numera las
+ pginas. Una redefinicin al principio del documento permite
+ cambiar esto.
+
+ <tag/Se escribe en ASCII./
+ Esto, que al principio puede parecer un inconveniente (ya que
+ implica teclear mucho ms) se torna en ventaja al cabo del
+ tiempo. Por un lado permite incrementar la velocidad de escritura
+ (pues no hay que andar utilizando ratn o mens), por otro
+ facilita el uso de cualquier editor de texto (no contiene
+ caracteres de control) y permite su transmisin por correo
+ electrnico (puede escribirse en ASCII de 7 bits). Esto hace que
+ muchas revistas cientficas admitan artculos escritos en &latex;,
+ enviados por <em/e-mail/. Ellos lo procesan en el lugar de
+ destino, hacen los cambios necesarios y lo imprimen.
+
+ <tag/Es gratis/
+ Pues eso. Para ver porqu vase la seccin
+ <ref id="tex-gratis" name="Porqu &tex; es gratis?">. A pesar de
+ ello, existen tambin implementaciones comerciales.
+
+ </descrip>
+
+ <sect1>Inconvenientes o ms bien, cules son las crticas ms habituales?
+ <!-- ================================================================= -->
+ <p>
+ <descrip>
+ <tag/Es muy difcil./
+ A diferencia de los procesadores visuales o <em/WYSIWYG/, que pueden
+ usarse casi
+ desde el primer da con resultados aceptables, &latex; requiere un
+ periodo de aprendizaje antes de conseguir los primeros
+ frutos. Incluso cuando ya se es un usuario medio o avanzado,
+ siempre es conveniente tener cerca un manual o un &latex;perto, al
+ que preguntarle.
+ <p>
+ Este proceso de iniciacin consiste principalmente en aprenderse
+ las rdenes
+ esenciales. Despus le siguen rdenes secundarias.
+ <p>
+ Ms tarde, puede uno aprender a programar en este
+ lenguaje. Llegado ese punto se
+ puede dar el siguiente salto, atacar el <em/plain-&tex;/ o incluso
+ el &tex;, para introducir rdenes de muy bajo nivel, pero esto muy
+ rara vez lo necesitar un usuario normal. Estas dos ultimas fases
+ slo son precisas si uno est interesado en los intrngulis del
+ sistema y los intrngulis de &latex; se le quedan cortos.
+ <p>
+ La contrapartida de este esfuerzo es que cuando se trabaja con
+ &latex; y se
+ compara el resultado con lo obtenido con otros procesadores, la
+ salida de stos ltimos parece <em/"poco seria"/ en cuanto se
+ exigen frmulas matemticas. Algo como los dientes, que duelen al
+ salir, pero luego se hacen imprescindibles.
+
+ <tag/No se ven los resultados hasta que se compila el archivo./
+ Una de las decepciones que sufre el usuario novato es que no ve los
+ frutos de su
+ trabajo hasta que compila. Como suelen aparecer errores de
+ compilacin, esto suele ser frustrante (aparte de conllevar una
+ prdida de tiempo). La nica solucin es armarse de paciencia. Con
+ el tiempo, los errores disminuyen y, simultneamente, se aprende a
+ procesar de cabeza, por lo que no se necesita hacer una
+ visualizacin para saber como va a quedar.
+ <p>
+ De todas formas, &latex; no est especialmente dirigido a los
+ aspectos puramente
+ estticos de cada pgina en concreto, sino a los estructurales del
+ documento. Si uno est interesado estrictamente en la esttica
+ (por ejemplo, porque trabaja en la autoedicin), &latex; no es el
+ procesador adecuado. ste basa la belleza de los documentos
+ creados ms en la claridad, en el buen criterio y en una esttica
+ agradable que en la posibilidad de hacer fcilmente diseos
+ rebuscados para cada pgina.
+ <p>
+ Existen, no obstante, soluciones intermedias entre &latex; y los
+ procesadores
+ WYSIWYG. As, el &tex;tures de los Mac, el <em/xdvi/ de las
+ <em/X-Window/ bajo <em/Unix/ o los <em/dviwin/, <em/yap/ o
+ <em/winview/ de los PC's permiten mantener en pantalla el archivo
+ que se est editando y la visualizacin del ltimo, lo cual
+ facilita la correccin de los documentos.
+
+ <tag/No permite introducir imgenes./
+ Esta acusacin habitual no es en absoluto cierta. Simplemente hay
+ que ser
+ conscientes de los medios de visualizacin e impresin de que
+ disponemos y obrar en consecuencia. Vase la seccin
+ <ref id="tex-dibujos" name="Introduciendo figuras en &latex;">
+
+ <p>
+ Lo que no debe olvidarse nunca es que tanto &tex; como &latex;
+ estn pensados como lenguajes de composicin de documentos, no de
+ autoedicin. A cada cual lo suyo.
+
+ <tag/No tiene variedad de tipos (fuentes)/
+ Es cierto que los tipos CM originalmente desarrollados por Knuth son
+ limitados
+ en cantidad y variedad, por lo que a medida que &latex; se
+ difunda han aumentado las demandas de ms tipos para usos
+ diversos. Aunque el crecimiento es todava lento, existe una gran
+ cantidad de tipos disponibles en el CTAN en:
+
+<tscreen><verb>
+CTAN:fonts
+</verb></tscreen>
+ En las versiones para salidas <em/postscript/ si es posible el uso
+ de cualquier tipo, pero no se garantiza que las ecuaciones
+ mantengan la calidad requerida.
+ </descrip>
+
+ <!-- ********************************************************* -->
+ <sect>Qu documentacin hay disponible sobre &tex;/&latex;?
+ <!-- ********************************************************* -->
+ <p>
+ Adems de las referencias que aqu se citan, puede consultarse la
+ seccin de manuales en las pginas de <em/Cervan&tex;/,
+ <htmlurl name="http://www.cervantex.org/manuales.php"
+ url="http://www.cervantex.org/manuales.php">
+ <sect1>Tutoriales de &latex; en castellano.<label id="es-tutores">
+ <!-- ==================================== -->
+ <p>
+ <descrip>
+ <tag/Una descripcin de &latex;/
+ <p> Toms Bautista <tt/(bautista _AT_ cma.ulpgc.es)/
+ ha escrito un documento titulado <em/Una descripcin de &latex;/
+ (basado inicialmente en <em/&latex;-Kurzbeschreibung/, de H. Partl,
+ E. Schlegl e
+ I. Hyna), donde se han introducido algunas notas especficas de la
+ implementacin del estilo <tt/spanish.sty/ desarrollado por
+ J. Snchez. Este documento se encuentra en CTAN (en
+ <tt>CTAN:documentation/short/spanish</tt>) y la versin ms
+ actualizada est siempre en
+ <quote>
+ <htmlurl
+ url="ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/"
+ name="ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/">
+ </quote>
+ <tag/Apuntes. Manual de &latex;/Preparado en Chile y disponible en
+ <htmlurl
+ url="http://cipres.cec.uchile.cl/~admcons/manuales/latex.html"
+ name="http://cipres.cec.uchile.cl/~admcons/manuales/latex.html">
+
+ <tag/Bases de datos bibliogrficos, &latex; y el idioma espaol/
+ Luis Seidel
+ <p>
+ Acerca del uso de Bib&tex; en castellano. Disponible en
+ <em/postscript/ en la pgina del autor y en formato <em/pdf/ en la
+ Universidad de la Rioja:
+ <p>
+ <htmlurl
+ url="http://feynman.faii.etsii.upm.es/~seidel/bibliogr.ps"
+ name="http://feynman.faii.etsii.upm.es/~seidel/bibliogr.ps">
+ <p>
+ <htmlurl
+ url="ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf"
+ name="ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf">
+ <tag/Curso de &latex;/
+ Kjetil Halvorsen. Transparencias de un curso de &latex; disponibles
+ en
+ <p>
+ <htmlurl
+ url="ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip"
+ name="ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip">
+
+ <tag/Recetario para &latex;/ por Aristarco. Disponible en
+ <htmlurl
+ url="http://recetariolatex.cjb.net"
+ name="http://recetariolatex.cjb.net">
+
+ <tag/Referencias rpidas de &latex;/ por Fernando Arbeiza. Disponible en
+ <htmlurl
+ url="http://www.loarco.homelinux.org/lqref-es"
+ name="http://www.loarco.homelinux.org/lqref-es">
+ </descrip>
+
+ <sect1>Libros en castellano
+ <!-- ================================= -->
+ <p>
+ <descrip>
+ <tag/Iniciacin a &latexe;/ Javier Sanguino Botella, Addison-Wesley
+ (1997)
+
+ <tag/Composicin de textos cientficos con &latex;./
+ G. Valiente. Edicions UPC, Barcelona, 1997
+
+ <tag/&latex;, primeros pasos./
+ F. Ortegn Gallego. Editorial Masson, Barcelona 1.992. (Sobre
+ &latex; 2.09)
+
+ <tag/&latex;, una imprenta en sus manos./
+ Bernardo Cascales Salinas, Pascual Lucas Saorn, Jose Manuel Mira
+ Ros, Antonio Pallars Ruiz y Salvador Snchez-Pedreo Guilln. Aula
+ Documental de Investigacin, Madrid, 2000.
+
+ <tag/El libro de &latex;./
+ Bernardo Cascales, Pascual Lucas, Jos Manuel Mira, Antonio Pallars
+ y Salvador Snchez-Pedreo. Prentice Hall, Madrid, 2003.
+
+ <tag/El universo &latex;./
+ Rodrigo De Castro. Facultad de Ciencias, Universidad Nacional de
+ Colombia, Bogot, 2003.
+ </descrip>
+
+ <sect1>Tutoriales en otros idiomas
+ <!-- ================================= -->
+ <p>
+ <descrip>
+ <tag/A Gentle Introduction to &tex;/ de Michael Dobb, disponible en
+ <tt>CTAN:documentation/gentle</tt>. Es un excelente tutorial de
+ introduccin al <em/plain/-&tex; en ingls.
+ <p>
+ Una referencia clsica de &tex;
+ <tag/Simplified Introduction to &latex;/ de Harvey J. Greenberg, disponible en
+ <tt>CTAN:documentation/simplified-latex/latex.ps</tt> (versin
+ postscript) y la versin ms reciente en
+ <htmlurl
+ url="http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html"
+ name="http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html">.
+ Basado en un curso para pregraduados.
+ <p>
+ <tag/&latex;: from quick and dirty to style and finesse/ Escrito por Tony
+ Roberts, se encuentra disponible en la Universidad de Southern
+ Queensland (Australia)
+ <htmlurl
+ url="http://www.sci.usq.edu.au/staff/robertsa/LaTeX/"
+ name="http://www.sci.usq.edu.au/staff/robertsa/LaTeX/">
+ con una rplica en Estados Unidos
+ <htmlurl
+ url="http://ricardo.ecn.wfu.edu/LaTeX/"
+ name="http://ricardo.ecn.wfu.edu/LaTeX/">.
+ <p>
+ <tag/&latex; for Word Processor Users/ Escrito por Guido Gonzato, es un
+ tutorial &latex; pensado especficamente para usuarios de
+ procesadores de texto. Est disponible en <tt>CTAN:info/latex4wp</tt>
+ <p>
+ <tag/l2tabu/ Escrito por Mark Trettin,
+ es un tutorial sobre lo que no debe hacer un usuario de
+ &latexe;. Disponible en el CTAN como un archivo pdf,
+ <htmlurl
+ url="http://www.ctan.org/tex-archive/info/l2tabu/"
+ name="http://www.ctan.org/tex-archive/info/l2tabu/">.
+ Contiene una lista de rdenes y paquetes obsoletos que no deben
+ utilizarse bajo &latexe;, as como otros errores habituales.
+ <tag/Online tutorials on &latex;/ del grupo de usuarios de &tex; de
+ la India, disponible en
+ <htmlurl
+ url="http://www.tug.org.in/tutorials.html"
+ name="http://www.tug.org.in/tutorials.html"
+ >.
+ </descrip>
+
+ <sect1>Libros en otros idiomas<label id="libros-int">
+ <!-- ============================================ -->
+ <p>
+ <!--
+ Esta seccin est extrada de la pgina
+ <htmlurl
+ url="http://www.esi.us.es/~gonfer/tex.html"
+ name="http://www.esi.us.es/~gonfer/tex.html">
+ de Antonio Gonzlez, de la Universidad de Sevilla
+ -->
+ <descrip>
+ <tag/A Guide to &latex;/
+ <htmlurl
+ url="http://www.awprofessional.com/title/0321173856"
+ name="H. Kopka y P.W. Daly, Addison-Wesley Professional (2004)">
+ <p>
+ Probablemente, el mejor manual existente sobre &latex;. Contiene
+ una gua completa de rdenes, abundantes ejemplos e informacin
+ adicional. (Incluye las dos versiones en uso de &latex;, &latexe;
+ y la ms antigua, &latex;2.09).
+
+ <tag/The &latex; Companion./
+ <htmlurl
+ url="http://www.awprofessional.com/title/0201362996"
+ name="Frank Mittelbach, Michel Goossens, Johannes Braams, David
+ Carlisle, Chris Rowley, Addison Wesley Professional (2004).">
+ <p>
+ Este manual sirve de ampliacin del anterior. Es una recopilacin
+ e informacin sobre los llamados paquetes (<em/packages/),
+ conjuntos de macros que distintos autores han puesto a disposicin
+ pblica.
+
+ <tag/The &latex; Web Companion: Integrating TeX, HTML, and XML/
+ <htmlurl
+ url="http://www.awprofessional.com/titles/0201433117"
+ name="Michel Goossens, Sebastian Rahtz, Eitan M. Gurari, Ross
+ Moore y Robert S. Sutor, Addison Wesley Professional (1999).">
+
+ Publicando documentos en la WWW mediante &latex;
+
+ <tag/&latex;--A Document preparation system/
+ <htmlurl
+ url="http://www.aw.com/catalog/academic/product/1,4096,0201529831,00.html"
+ name="L. Lamport (dos ediciones) Addison-Wesley (1985 y 1994).">
+ <p>
+ Durante mucho tiempo este fue <em/"el libro"/ del &latex;. Escrito
+ por el mismo autor del programa, contiene todo lo esencial para
+ introducirse en este procesador, si bien resulta un tanto
+ insuficiente para usuarios avanzados. La primera edicin
+ corresponde a la versin antigua del programa (&latex;209, hoy
+ obsoleta) y la segunda al &latexe;.
+
+ <tag/The &latex; Graphics Companion/
+ <htmlurl
+ url="http://www.aw.com/catalog/academic/product/1,4096,0201854694,00.html"
+ name="M. Goossens, S. Rahtz y F. Mittelbach, Addison-Wesley (1997).">
+ <p>
+ Un extenso manual acerca de cmo ilustrar documentos con &tex; y
+ postscript.
+
+ <tag/The &tex;book/
+ <htmlurl
+ url="http://www.aw.com/catalog/academic/product/1,4096,0201134470,00.html"
+ name="D.E. Knuth, Addison-Wesley (1986).">
+ <p>
+ Este es <em/"el libro"/ para los que quieren conocer las entraas de
+ &tex;. Contiene todo sobre el lenguaje &tex;, escrito por el mismo
+ autor del programa. Es un libro completo y ameno pero
+ absolutamente incomprensible para los novatos. El archivo fuente
+ en &tex; de este libro est disponible para aquellos que desean
+ conocer los trucos que el autor emple a la hora de escribirlo
+ (algunos verdaderamente complejos).
+
+ <p>
+ <!-- En CTAN estn: systems/knuth/tex/texbook.tex -->
+ Knuth proporciona el cdigo fuente con fines <em/didcticos/, no para que se
+ imprima. De hecho, si se intenta <em/&tex;earlo/ entrar en un
+ bucle infinito que dice que eso no debe hacerse. Aunque no es
+ complicado hacer que deje de ocurrir, sera ilegal hacerlo... :-)
+
+ <tag/TeX by Topic, A TeXnician's Reference/ de Victor Eijkhout, editado por
+ Addison-Wesley (1992) y disponible en
+ <htmlurl
+ url="http://www.eijkhout.net/tbt/"
+ name="http://www.eijkhout.net/tbt/">,
+ <p>
+ es otro de los libros clsico sobre &tex; (no &latex;) que puede descargarse
+ gratis (y legalmente) en un pdf.
+
+ <tag/&tex; for the Impatient/ de Karl Berry, tambin est
+ disponible en <tt>CTAN:info/impatient/</tt> de forma libre.
+
+ <tag/Making &tex; work/ de Norman Walsh, editado por O'Reilly
+ (ISBN: 156592-051-1), pero actualmente descatalogado. Sin embargo est
+ disponible de forma libre en
+ <htmlurl
+ url="http://makingtexwork.sourceforge.net/mtw/"
+ name="http://makingtexwork.sourceforge.net/mtw/">.
+ Aunque algunas cosas estn obsoletas, (de hecho todava se refiere a &latex; 2.09),
+ tanto su contenido como sus fuentes pueden an ser de utilidad.
+
+ </descrip>
+
+ <sect1>Revistas.<label id="revistas">
+ <!-- ==================================== -->
+ <p>
+ <descrip>
+ <tag/The PracTeX Journal/ Una revista de &tex; <em/on-line/ y
+ gratuita. Disponible en
+ <htmlurl
+ url="http://dw.tug.org/pracjourn/"
+ name="http://dw.tug.org/pracjourn/">.
+
+ </descrip>
+ <!-- ********************************************************* -->
+ <sect>Que elementos intervienen al procesar un documento con &latex;?
+ <!-- ********************************************************* -->
+ <sect1>El documento fuente: Cmo creo un documento con &latex;, lo proceso, lo veo y lo imprimo?
+ <!-- ====================================================================== -->
+ <p>
+ Como hemos dicho &tex;/&latex; es realmente un lenguaje de
+ programacin de textos. En el documento fuente original se introduce
+ el texto a procesar junto con una serie de rdenes especificando cmo
+ debe ser procesado ste. Este paso se realiza con el editor de texto
+ favorito del autor, aunque hay algunos editores de texto que estn,
+ mejor adaptados, o totalmente integrados para su uso con &tex;/&latex;
+ -- vase <ref id="tex-editores" name="editores para &tex;">
+ --. Pongamos por ejemplo que el documento creado es <tt/documento.tex/.
+ <p>
+ Una vez terminado el documento fuente (<tt/documento.tex/), ste se
+ procesa mediante &tex; si se han utilizado las rdenes de
+ <em/plain-&tex;/ o &latex si se han utilizado las rdenes de
+ &latex;. Se corrigen los posibles errores de sintaxis y se repite el
+ proceso hasta que stos se han eliminado. Como resultado del
+ procesamiento se tiene un <em/archivo independiente del dispositivo/,
+ o DVI (<tt/documento.dvi/).
+
+ <sect1>Qu es un archivo DVI?<label id="DVI">
+ <!-- ====================================== -->
+ <p>
+ Un archivo DVI es el archivo resultante de procesar el texto fuente a
+ travs de &tex;. Su forma no depende del dispositivo que se vaya a
+ utilizar para verlo/imprimirlo. Un archivo DVI est pensado para ser
+ ledo por un <em/conversor/ que produzca una salida adecuada para una
+ determinada impresora, o para un determinado visualizador en la
+ pantalla del ordenador. Los archivos DVI utilizan una codificacin
+ interna de &tex;, de forma que un documento fuente debe producir
+ exactamente el mismo archivo DVI, con independencia de la
+ implementacin de &tex; que se utiliza para producirlo.
+ <p>
+ Un archivo DVI contiene toda la informacin necesaria para imprimir o
+ ver el resultado, excepto los tipos o su aspecto concreto (aunque
+ contiene sus medidas) o informacin que se introducir mediante una
+ orden <tt/\special/
+ -- vase <ref id="special" name="Qu son los \special?">.
+
+ <sect1>Qu es un conversor (driver)?<label id="conversores">
+ <!-- ================================= -->
+ <p>
+ Un conversor es un programa que toma su entrada de un archivo DVI y
+ produce un archivo que puede enviarse a una impresora o una salida
+ directa a una pantalla.
+ <p>
+ Estos conversores normalmente son especficos a cada impresora o
+ lenguaje de impresora. Por ejemplo, una impresora <em/postscript/
+ entender siempre la salida de un conversor <em/postscript/, pero en
+ general no de otros formatos.
+ <p>
+ Al igual que el archivo DVI, el conversor necesita informacin sobre
+ los tipos que puede encontrar en distintos lugares.
+
+ <sect1>Qu son los archivos <tt/.pk/?
+ <!-- ================================= -->
+ <p>
+ Los archivos <tt/.pk/ (cuyo nombre viene de <em/packed raster/)
+ contienen tipos de letra en forma de mapa de bits. METAFONT produce
+ una salida en mapa de bits en un formato no comprimido denominado
+ <tt/.gf/, que es convertido a <tt/.pk/ mediante una utilidad
+ denominada <em/gftopk/. Para cada diseo de letra, tamao, peso y
+ familia es necesario un archivo <tt/.pk/ distinto, e incluso para
+ distintos dispositivos de salida. Como consecuencia de sto se guardan
+ en una estructura compleja de directorios, o en libreras de tipos,
+ para normalizar el acceso a las mismas.
+
+ <sect1>Qu son los archivos <tt/.tfm/?
+ <!-- ================================= -->
+ <p>
+ <tt/tfm/ es la abreviatura de <em/&tex; font metric/, mtrica de los
+ tipos &tex;. Los archivos <tt/.tfm/ guardan la informacin acerca de
+ los tamaos de los caracteres en cada tipo, as como las ligaduras y
+ desplazamientos dentro de cada tipo. Se necesita un archivo <tt/.tfm/
+ para cada tipo utilizado por &tex;, es decir para cada diseo, peso y
+ familia, aunque uno valga para todas las magnificaciones. &tex;
+ utiliza los archivos <tt/.tfm/ para componer la pgina, pero en
+ general los conversores no los necesitan.
+
+ <sect1> Qu son los tipos (fuentes) CM?<label id="CM">
+ <!-- ============================================== -->
+ <p>
+ Los tipos CM son los tipos originalmente creados por Donald
+ E. Knuth. Cuando desarroll &tex;, lo acompa de este conjunto
+ completo de tipos de alta calidad. Estos tipos eran independientes de
+ la impresora utilizada (ya que eran tratados como grficos) lo que
+ produca la misma calidad en cualquier sitio. Con el tiempo, estos
+ tipos (los Computer Modern o CM) se convirtieron en la <em/firma/ del
+ procesador, que permita identificar un documento a primera vista.
+
+ <sect1> Qu son los tipos (fuentes) EC/DC?<label id="EC/DC">
+ <!-- ============================================== -->
+ <p>
+ Son fuentes del tipo de las Computer Modern, pero con 256 caracteres,
+ que cubren las necesidades de casi todas las lenguas habladas en
+ Europa y algunas otras que utilizan el alfabeto latino. Su nombre
+ viene de <em/European Computer Modern Fonts/. Dichas fuentes contienen
+ caracteres acentuados siguiendo el esquema de codificacin de
+ Cork. Han estado durante bastante tiempo en periodo de pruebas y
+ durante ese tiempo se llamaban DC. Ya se distribuyen normalmente al
+ pblico en general, con el nombre EC, y a partir de ese momento las DC
+ se consideran obsoletas.
+ <p>
+ Estas fuentes ya estn presentes en las distribuciones modernas de
+ &tex;/&latex;, pero en caso de que se trabaje con una distribucin
+ antigua pueden conseguirse en:
+<tscreen><verb>
+CTAN:fonts/ec/ready-mf
+</verb></tscreen>
+ y los archivos <tt/tfm/ para &latex; estn en
+<tscreen><verb>
+CTAN:fonts/ec/tfm
+</verb></tscreen>
+ Si tenemos tipos de Cork (PostScript, DC, etc.) y queremos utilizar
+ esta codificacin en las fuentes de salida se debe introducir en el
+ prembulo del documento la lnea
+<tscreen><verb>
+\usepackage[T1]{fontenc}
+</verb></tscreen>
+
+ <sect1>Qu son los tipos (fuentes) virtuales?
+ <!-- ===================================== -->
+ <p>
+ Los tipos (fuentes) virtuales proporcionan a &tex; una forma de
+ trabajar con algo ms complejo que los caracteres individuales
+ definidos en un tipo. En un tipo virtual se definen a partir de
+ elementos simples de los tipos normales, elementos ms complejos que
+ &tex; considerar como si fueran elementos de un tipo normal (tienen
+ sus tamaos y su archivo <tt/.tfm/ de mtrica), pero que en realidad
+ el procesador del DVI compondr a partir de distintos elementos
+ constituyentes para formar a partir de ellos el elemento complejo
+ descrito en el tipo virtual. De esta forma es posible remapear
+ caracteres, hacer un tipo compuesto con elementos tomados de distintos
+ tipos o en general construir elementos muy complejos a partir de
+ elementos simples de los distintos tipos. Por ejemplo se utilizan
+ tipos virtuales para <em/remapear/ tipos <em/postscript/.
+ <p>
+ &tex; en s no ve los tipos virtuales, nicamente trabaja con las
+ mtricas que le da el tipo virtual en su <tt/.tfm/ como si se tratara
+ de tipos normales.
+
+ <sect1>Qu son las rdenes <tt/\special/?<label id="special">
+ <!-- ===================================================== -->
+ <p>
+ &tex; proporciona una forma de expresar cosas que los conversores
+ pueden hacer, pero de las que &tex; no sabe nada. Por ejemplo &tex; no
+ sabe cmo introducir figuras <em/postscript/ en un documento o cmo
+ cambiar el color del texto impreso, pero algunos conversores s saben cmo hacerlo.
+ <p>
+ Para ello &tex; proporciona la orden <tt/\special/. &tex; simplemente
+ entiende la orden como correcta y la pasa con sus argumentos al
+ archivo DVI, sin hacer nada de lo que en ella se dice. Es el conversor
+ el que debe interpretar la orden y hacer lo que se le pide.
+ <p>
+ La sintaxis de los <tt/\special/ es fuertemente dependiente del
+ dispositivo de salida y en general no es vlida para distintos
+ dispositivos. &latexe; proporciona paquetes estndar de grficos
+ (<tt/graphics, graphicx/) y manejo de color (<tt/color/), que hacen
+ ms fcil la inclusin de grficos, rotacin, reescalado y cambios de
+ color --Vase la seccin
+ <ref id="tex-dibujos" name="Introducir grficos con &latex;">.
+
+ <sect1>Qu es el postscript y el postscript encapsulado (archivos <tt/.eps/)?
+ <label id="postscript">
+ <!-- ========================================================== -->
+ <p>
+ <em/PostScript/ (PS) es un lenguaje de programacin para describir
+ pginas. Como lenguaje estructurado permite la programacin (tiene
+ estructuras de control y bucles), y recuerda el lenguaje de
+ programacin FORTH. Originalmente fue desarrollado por Adobe. Existen
+ varios intrpretes de <em/PostScript/ que permiten la visualizacin de
+ este formato. El ms extendido es <em/Ghostscript/ (GS), de Aladdin,
+ del que puede obtenerse informacin en
+ <htmlurl url="http://www.cs.wisc.edu/~ghost/index.html"
+ name="http://www.cs.wisc.edu/~ghost/index.html">
+ y en
+ <htmlurl url="http://www.aladdin.com" name="http://www.aladdin.com">
+ cuando acaben de construirla. El formato PS se basa en describir cada
+ pgina desde un origen de coordenadas que se sita en la esquina
+ inferior izquierda de la pgina. PS permite, sin embargo, redefinir el
+ origen, de forma que se puede recomenzar la descripcin de un bloque
+ de una pgina desde un origen arbitrario.
+ <p>
+ PS encapsulado (EPS) es el formato estndar para importar y exportar
+ archivos PS en cualquier tipo de entornos. Usualmente es un archivo
+ que contiene una sola pgina que describe una figura. El archivo EPS
+ est especialmente pensado para incluirlo en otros archivos PS, y es
+ como cualquier otro archivo PS con algunas restricciones. La FAQ de
+ <em/PostScript/ puede alcanzarse en
+ <htmlurl url="http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html"
+ name="http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html">,
+ de donde est tomado mucho de lo anterior.
+
+ <sect1>Qu es el formato <tt/pdf/?<label id="formato-pdf">
+ <!-- ================================= -->
+ <p>
+ PDF (Portable Document Format) es, como su nombre indica, un formato
+ de archivos transportable entre distintas plataformas, creado por
+ Adobe y especialmente diseado para visualizar documentos tal y como
+ se han diseado. Permite usar colores, grficos, seguir enlaces e
+ imprimir pero, fundamentalmente, permite ver en la pantalla los
+ documentos, siendo un formato compacto. Es muy similar a PS, pero no
+ tiene capacidades de programacin. En relacin con &tex;, PDF es un
+ formato que sustituye al DVI -- ver la pregunta
+ <ref id="DVI" name="Qu es DVI?"> -- en la salida de &tex;. En la web
+ hay informacin abundante sobre PDF en
+ <htmlurl url="http://www.pdfzone.com/webring/"
+ name="http://www.pdfzone.com/webring/">.
+ Los visualizadores de PDF ms recomendables son Adobe Reader (antes
+ Acrobat Reader), de Adobe, gratuito
+ (<htmlurl url="http://www.adobe.com" name="http://www.adobe.com">),
+ xpdf <htmlurl url="http://www.foolabs.com/xpdf/home.html"
+ name="http://www.foolabs.com/xpdf/home.html"> y
+ Ghostview <htmlurl url="http://www.cs.wisc.edu/~ghost/index.html"
+ name="http://www.cs.wisc.edu/~ghost/index.html">.
+
+ <sect1>Qu son los paquetes en &latex;?<label id="paquetes-latex">
+ <!-- ================================= -->
+ <p>
+ Escribir un documento a base de <em/primitivas/ &tex; puede resultar
+ extremadamente engorroso. &latex; utiliza las primitivas de &tex; para
+ definir otro conjunto de comandos ms amigable, para las tareas ms
+ habituales (definir captulos, tablas, listas enumeradas...). No
+ obstante, &latex; no incluy nuevos comandos de <em/alto nivel/ para
+ cualquier tarea imaginable, sino que se hizo extensible a base de
+ <em/paquetes/, de forma que hay un cuerpo de &latex; y unos aadidos
+ en forma de paquetes. Un <em/paquete/ es un fichero que contiene ms
+ cdigo, que se incluye en el prembulo del documento (con
+ <tt>\usepackage{nombre-de_paquete}</tt>),y que define nuevos comandos
+ basndose, ya sea en las primitivas de TeX o en los comandos
+ previamente definidos por LaTeX.
+ <p>
+ La distribucin de &tex;/&latex; instalada en el sistema ya incluir
+ una buena cantidad de paquetes listos para su uso. Sin embargo, pueden
+ aadirse nuevos paquetes
+ -- vase <ref id="paquetes-instalar" name="Instalacin de paquetes">.
+
+ <sect1>Qu son los archivos <tt/.dtx/?<label id="formato-dtx">
+ <!-- ================================= -->
+ <p>
+ Tanto &latexe; como muchos de los paquetes de macros se escriben en un
+ lenguaje de programacin ilustrada, con cdigo y documentacin en el
+ mismo fichero. Este formato, conocido como <tt/doc/ se debe a Frank
+ Mittelbach. El fichero que contiene las fuentes comentadas suele tener
+ la extensin <tt/.dtx/ y normalmente debe aligerarse de la
+ documentacin antes de su uso como macro, o correr &latex; sobre el
+ fichero para producir una versin maquetada de la
+ documentacin. Habitualmente se suministra un fichero <tt/.ins/ para
+ facilitar esto, que utiliza el paquete <em/docstrip/. Pueden incluirse
+ varios paquetes dentro de un mismo fichero <tt/.dtx/. Para ms
+ informacin acerca de cmo extraer el contenido de un fichero
+ <tt/.dtx/ vase <ref id="dtx-extraer" name="extraer de un .dtx">.
+ <p>
+ &latex; no utiliza los ficheros <tt/.dtx/ una vez procesados para
+ producir los <tt/.sty/ o <tt/.cls/, por lo que no es estrictamente
+ necesario tenerlos instalados, aunque puede ser recomendable, ya que
+ son siempre la principal fuente de informacin sobre el paquete.
+
+ <!-- ********************************************************* -->
+ <sect>Cmo consigo &latex; y otros programas relacionados?
+ <!-- ********************************************************* -->
+
+ <sect1>Distribuciones &tex;/&latex;
+ <!-- ========================================================= -->
+ <p>
+ En principio se podra coger todo el sistema elemento a elemento y
+ ponerlo todo en comn. Sin embargo, para que sto funcione
+ correctamente, el tiempo requerido y la complejidad del trabajo son
+ grandes. Por esta razn algunas personas o empresas ya lo han hecho y
+ lo ofrecen preparado en lo que se denominan distribuciones.
+ <p>
+ Se entiende por distribucin un conjunto de binarios y paquetes de
+ macros &latex; junto con otras utilidades adicionales, empaquetados de
+ forma coherente y organizada, para que trabajen en comn de la forma
+ ms eficiente posible. Hay distribuciones de libre distribucin,
+ shareware (se puede distribuir y probar, pero si se quiere usar
+ regularmente es necesario pagar el registro) y otras de distribucin
+ comercial. Aunque algunas de las distribuciones comerciales tienen
+ caractersticas adicionales sobre las distribuciones libres, a veces
+ es al contrario. Aunque algunas distribuciones estn disponibles para
+ distintos sistemas operativos, lo ms habitual es que estn limitadas
+ a un sistema operativo.
+ <p>
+ Las distribuciones libres o shareware pueden conseguirse en el CTAN --
+ vase <ref id="que-es-CTAN" name="Qu es el CTAN?"> --, o a travs de
+ los CD-ROM editados por distintos grupos de usuarios de &latex;,
+ mientras que las comerciales se consiguen a travs de sus respectivos
+ distribuidores o directamente si no los hay.
+ <p>
+ Para buscar distribuciones para los distintos sistemas operativos, la
+ estructura de un nodo CTAN es siempre la misma. Existe un directorio
+ <tt>tex-archive</tt> del cual cuelga un rbol de directorios. En
+ particular, existe un directorio <tt>systems</tt>, del que penden las
+ distintas implementaciones. Existen versiones para
+<tscreen><verb>
+Atari
+Amiga
+UNIX
+VMS
+Os2
+Windows NT
+Mac
+MS-DOS
+</verb></tscreen>
+ No es necesario tener una acceso de red para acceder al CTAN. El grupo
+ de usuarios alemanes de &tex; (DANTE) ha hecho una recopilacin en
+ CD-ROM del contenido del CTAN. Las edicin de 1999 y posteriores se
+ han distribuido a travs del grupo de usuarios Cervan&tex;. Para mayor
+ informacin se puede consultar la pgina web del grupo Cervan&tex;
+
+ <sect2>Distribuciones libres o <em/shareware/
+ <!-- ..................................... -->
+ <p>
+ <descrip>
+ <tag/Unix/
+ <em/te&tex;/ es, para sistemas <tt/Unix/ la eleccin ms
+ multiplataforma. Se puede encontrar en
+ <tt>CTAN:systems/unix/teTeX</tt> y contiene por un lado una
+ serie de archivos que no dependen del sistema operativo y por
+ otro lado binarios para toda una serie de sistemas operativos
+ <em/Unix/.
+
+ <tag/Linux/
+ Aunque lo que se acaba de decir de <em/Unix/ es tambin vlido
+ para <em/Linux/, recalcar adems que en las principales
+ distribuciones de <em/Linux/ vienen paquetes de <em/te&tex;/
+ listos para instalar y utilizar sin apenas esfuerzo.
+ <p>
+ Antes tambin haba otra distribucin denominada <em/N&tex;/. Es
+ necesario tener un especial cuidado y <bf/no utilizar/ la
+ incluida en el CD-ROM de Slackware'96, que inclua una versin
+ de las fuentes CM que no respetaba las condiciones de
+ distribucin y cambiaba la mtrica respecto de las estndar sin
+ cambiar el nombre, rompiendo la portabilidad de los
+ documentos. En la prctica este aviso debe estar ya obsoleto.
+
+ <tag/Mac/
+ Los Macs modernos ya no utilizan el sistema operativo clsico
+ sino uno basado en *BSD unix (<em/Mac OS X/), con una capa
+ grfica que no son las <em/X-Window/ (pero que tambin se pueden
+ poner).
+ <p>
+ Por este motivo muchas aplicaciones unix clsicas se han
+ adaptado con facilidad a <em/Mac OS X/, entre ellas
+ <em/te&tex;/. La pgina
+ <htmlurl url="http://www.rna.nl/tex.html" name="http://www.rna.nl/tex.html">
+ tiene una gran cantidad de informacin sobre el uso de &tex; en
+ <em/Mac OS X/, incluyendo un instalador de <em/te&tex;/. Se
+ necesita un editor que se comunique bien con &tex;, como los que
+ se mencionan ms adelante. Otras pginas muy interesantes son
+ <htmlurl url="http://www.esm.psu.edu/mac-tex/default.html"
+ name="http://www.esm.psu.edu/mac-tex/default.html"> y
+ <htmlurl url="http://latex.yauh.de/index_en.html"
+ name="http://latex.yauh.de/index_en.html">.
+ <p>
+ Para <em/Mac/ clsicos sigue existiendo Oz&tex;. ste es una
+ versin <em/shareware/ de &tex; para los ordenadores Macintosh
+ clsicos. Incluye un visualizador de dvi y un conversor a
+ postscript. Est disponible en
+ <tt>CTAN:non-free/systems/mac/oztex</tt>. Su pgina original est en
+ <htmlurl url="http://www.trevorrow.com/oztex/"
+ name="http://www.trevorrow.com/oztex/">
+
+ <tag>DOS/OS2</tag>
+ <em/em&tex;/ es, para sistemas <em/DOS/ la distribucin ms
+ extendida. Puede encontrarse en
+ <tt>CTAN:systems/msdos/emtex</tt>, aunque desde hace tiempo no
+ se ven versiones nuevas. <em/g&tex;/ era otra distribucin para
+ <em/DOS/, pero recientemente ha sido retirada de <tt/CTAN/ a
+ peticin de su creador. Tambin est <em/em&tex;-TDS/, que no es
+ ms que un rbol de archivos de estilo para &tex;/&latex;
+ preparado para ser utilizado con los binarios de <em/em&tex;/.
+
+ <tag/Win32/
+ <itemize>
+ <item>
+ <bf/Mik&tex;/ de Christian Schenk es tambin una
+ distribucin completa independiente de te&tex;. tiene su
+ propio visualizador <em/yap/ que permite imprimir, aunque
+ tambin se incluye <em/dvips/. Est disponible en
+ <tt>CTAN:systems/win32/miktex</tt>. Si se tiene conexin de
+ red, las ltimas versiones permiten traer e instalar
+ paquetes sobre la marcha segn se van necesitando. Para
+ obtener informacin sobre la instalacin de un sistema
+ &latex; (mik&tex;) en Windows puede consultarse la pgina
+ <htmlurl url="http://www.udlap.mx/~ma108907/latex/winlatex.html"
+ name="http://www.udlap.mx/~ma108907/latex/winlatex.html">.
+ <item>
+ <bf/XEm&tex;/, de Fabrice Popineau, es una distribucin
+ integrada de &tex;, &latex;, Con&tex;t, Xemacs y otros
+ programas para Windows. Todos los programas han sido
+ compilados de forma nativa para optimizar el rendimiento
+ bajo Windows. Se suministra configurado para que funcione
+ nada ms instalarse. Su pgina es
+ <htmlurl url="http://www.fptex.org/"
+ name="http://www.fptex.org/">
+ <item>
+ <bf/fp&tex;/ de Fabrice Popineau era una versin de
+ <em/te&tex;/ para Windows. Sin embargo, su autor lo ha
+ dejado de lado para concentrarse en XEm&tex;. De momento
+ sigue disponible en <tt>CTAN:systems/win32/fptex</tt>, pero
+ ya no est mantenido.
+ </itemize>
+ </descrip>
+
+ <sect2>Distribuciones comerciales<label id="tex-de-pago">
+ <!-- ................................................ -->
+ <p>
+ <descrip>
+ <tag/Windows/
+ <itemize>
+ <item>
+ <bf/Scientific Word/<em>Scientific
+ Word/WorkPlace/Notebook</em> ofrece una forma de trabajo
+ tipo casi <em/WYSIWYG/ con un procesador &tex; en segundo
+ plano. Ms informacin en
+ <htmlurl url="http://www.sciword.demon.co.uk/"
+ name="http://www.sciword.demon.co.uk/">.
+ Incluye <em/True&tex;/. Aunque proporciona un entorno
+ <em/amistoso/ para la escritura de documentos, en algunos
+ casos integrado con <em/maple/ para realizar clculos
+ simblicos, es muy rgido cuando es necesario salirse de los
+ estilos estndar proporcionados con <em/SW/ y no es fcil
+ compartir archivos &latex; generados con <em/SW/ con otras
+ personas que no lo usen, porque necesitan una serie de
+ paquetes especficos. Adems, los argumentos opcionales de
+ algunas macros dan error en <em/SW/, aunque dependiendo de
+ uso que se le de, sto puede no aparecer. A pesar de todo,
+ puede ser til para una persona que no quiere hacer cosas complicadas.
+ </itemize>
+ </descrip>
+
+ <sect1>Editores de texto que trabajan especialmente bien con &latex;<label id="tex-editores">
+ <!-- ================================================================= -->
+ <p>
+ <descrip>
+ <tag/Unix/
+ <itemize>
+ <item> GNU <em/emacs/ o <em/xemacs/
+ utilizado en combinacin con el paquete AUC&tex; (disponible
+ en <tt>CTAN:support/auctex)</tt> o como un paquete ya incluido
+ en muchas distribuciones) proporciona mens desplegables y
+ secuencias de control para las estructuras habituales,
+ verifica sintaxis y la muestra coloreada, permite llamar a
+ &tex; y a los conversores desde el editor y mucho
+ ms. Complejo, pero muy potente. Joaqun Ataz ha escrito un
+ manual para su uso con &latex;,
+ <em/Creacin de ficheros &latex; con GNU Emacs/, disponible en
+ <tt>CTAN:info/spanish/guia-atx/guia-atx.pdf</tt>
+ <item> <em/kile</em>
+ Trabaja sobre cualquier plataforma con KDE instalado y segn
+ la documentacin, hasta en OS-X... Tiene opciones para
+ compilacin y conversiones con una nica pulsacin de tecla,
+ se pueden personalizar las rdenes y se integra con cualquier
+ visualizador dvi, ps o pdf que tengamos. Disponible en la
+ mayor parte de las distribuciones Linux y en
+ <htmlurl url="http://kile.sourceforge.net"
+ name="http://kile.sourceforge.net">.
+ </itemize>
+ <tag/Mac/
+ Para <em/Mac OS X/ hay algunos editores que se entienden bien con
+ &tex;
+ <itemize>
+ <item> <bf/TeXShop/
+ Muy majo y en castellano. Se encuentra en
+ <htmlurl url="http://www.uoregon.edu/~koch/texshop/"
+ name="http://www.uoregon.edu/~koch/texshop/">.
+ <item> <bf/iTeXMac/
+ Tiene ms cosas, pero es ms lento y hay muchos mensajes de
+ "an no implementado". Se encuentra en
+ <htmlurl url="http://itexmac.sourceforge.net/"
+ name="http://itexmac.sourceforge.net/">.
+ </itemize>
+ <tag>DOS/OS2</tag>
+ &tex;shell es un entorno de trabajo simple y fcilmente
+ personalizable que puede ser utilizado con el editor favorito de
+ cada uno. Tambin cuenta con un editor propio que permite seguir
+ los errores de la compilacin fcilmente aunque no soporta
+ archivos de ms de 64K. Aunque puede particularizarse a otras
+ distribuciones, viene muy preconfigurado para em&tex;.
+ <tag/Win32/
+ <itemize>
+ <item> <bf/winedt/
+ es un paquete <em/shareware/ del que se suele oir hablar
+ bien. Proporciona un entorno de trabajo desde el que llamar a
+ los distintos programas y un editor potente y bien configurado
+ <item> <bf/Winshell/
+ es un programa libre de prestaciones menores, pero que puede
+ ser ms que suficiente para muchos usuarios.
+ <item> <bf/TeXnic Center/
+ es tambin un buen entorno de trabajo para Win32. Est
+ disponible en CTAN en
+ <tt>CTAN:systems/win32/TeXnicCenter/</tt>
+ </itemize>
+ </descrip>
+ <p>
+ Otros programas que no son editores completos, pero que ayudan a la edicin son:
+ <descrip>
+ <tag/LaTable/
+ es un ayudante de creacin de tablas que permite generar el cdigo
+ &latex; necesario para la creacin de una tabla. La tabla se
+ disea en un entorno visual muy cmodo y la herramienta genera el
+ cdigo &latex; que se incorpora al documento con un simple
+ <em/copy-paste/. Tambin permite guardar las tablas generadas para
+ su posterior modificacin. Todava tiene detalles, pero cuenta con
+ muchas opciones bastante tiles, y genera un cdigo relativamente
+ limpio... adems, aunque es un programa Win32 funciona bien en
+ <em/Linux/ usando el emulador <em/Wine/. Disponible en
+ <htmlurl url="http://www.g32.org/latable/"
+ name="http://www.g32.org/latable/">. Es freeware de uso, pero
+ sus fuentes no estn disponibles.
+
+ <tag/TeXaide/
+ para quienes sigan pensando que las ecuaciones se deben hacer con
+ diseadores ... (se consiguen mucho mejores resultados a mano,
+ pero no faltan quienes abandonan &latex; cuando se enfrentan a las
+ ecuaciones. Segn los que lo han probado, el cdigo que genera no
+ es en ocasiones muy limpio, pero suele funcionar bien. Es un
+ programa Win32 que tambin funciona en Linux usando el emulador
+ Wine. Disponible en
+ <htmlurl url="http://www.dessci.com/en/products/texaide/"
+ name="http://www.dessci.com/en/products/texaide/">.
+ </descrip>
+
+ <!-- ********************************************************* -->
+ <sect>Preguntas especficas para el &latex; en castellano
+ <!-- ********************************************************* -->
+ <sect1>Cmo puedo usar &tex; en castellano? o Qu es lo mnimo que hay que saber para escribir en castellano con &tex;/&latex;?
+ <!-- ===================================================================== -->
+ <p>
+ En realidad, no es necesario nada adicional que no est ya incluido en
+ las distribuciones ms habituales. El problema normalmente se reduce a tres cosas:
+ <enum>
+ <item>
+ Introduccin de caracteres acentuados. Vanse las respuestas a las
+ preguntas <ref id="raw-characters" name="mediante rdenes &latex;">,
+ <ref id="8bitintro" name="Cmo introducir directamente los caracteres extendidos?"> y
+ <ref id="acentos-math" name="acentos en modo matemtico">
+ <item>
+ Literales en castellano. Vase la respuesta a la pregunta
+ <ref id="literales" name="Cmo cambiar los literales que &latex; produce?">.
+ <item>
+ Patrones de particin de palabras (silabeo o guionado). Vase
+ <ref id="patrones-guionado" name="patrones de guionado"> donde se
+ explica cmo hacer que &tex; parta las palabras siguiendo las
+ reglas del espaol.
+ </enum>
+
+ <sect1>Con &latex;, cmo puedo escribir los acentos y dems caracteres extendidos?
+ <label id="acentos">
+ <!-- ========================================================================== -->
+
+ <sect2>Mediante rdenes &latex; <label id="raw-characters">
+ <!-- ........................................................... -->
+ <p>
+ Cuando no hay ms remedio, los caracteres extendidos se escriben as:
+ <tscreen><verb>
+ ==> \'a ==> \'A ==> \~n ==> ?`
+ ==> \'e ==> \'E ==> \~N ==> !`
+ ==> \'\i{} ==> \'I ==> \"u
+ ==> \'o ==> \'O ==> \"U
+ ==> \'u ==> \'U
+</verb></tscreen>
+ Sin embargo, sto normalmente no es necesario. Vase la respuesta a
+ la pregunta <ref id="8bitintro" name="Introducir directamente los
+ caracteres extendidos">
+
+ <sect2>Directamente mediante el paquete <em/inputenc/<label id="8bitintro">
+ <!-- ........................................................... -->
+ <p>
+ El paquete <em/inputenc/ permite escribir directamente en la pgina
+ de cdigos habitual, convirtindose internamente el texto
+ introducido a texto &latex;, de acuerdo con las diferentes tablas de
+ equivalencia para las distintas pginas de cdigos y de forma
+ completamente transparente al usuario.
+ <p>
+ Si somos usuarios de UNIX, debemos poner al principio de nuestro
+ documento (en lo que se denomina el prembulo, entre
+ <tt>\documentclass...</tt> y <tt>\begin{document}</tt>) lo
+ siguiente:
+<tscreen><verb>
+\usepackage[latin1]{inputenc}
+</verb></tscreen>
+ si la codificacin es <tt/iso-8889-1/ (tambin conocida como
+ <tt/latin1/).
+
+ Si la codificacin es <tt/utf-8/, como en muchas distribuciones
+ recientes de Linux:
+<tscreen><verb>
+\usepackage[utf8]{inputenc}
+</verb></tscreen>
+ pero si la instalacin es antigua, debe utilizarse el paquete
+ <em/ucs/ (en muchas distribuciones se le llama <em/latex-ucs/,
+ aunque carga <em/ucs.sty/):
+<tscreen><verb>
+\usepackage{ucs}
+\usepackage[utf-8]{inputenc}
+</verb></tscreen>
+ <p>
+ Si trabajamos con MS-Windog hay que usar <tt/cp1252/ (que es
+ <em/casi/ el <tt/latin1/)
+<tscreen><verb>
+\usepackage[cp1252]{inputenc}
+</verb></tscreen>
+ (<tt/ansinew/ es una variante obsoleta).
+ Si trabajamos con DOS, hay que poner esto:
+<tscreen><verb>
+\usepackage[cp850]{inputenc}
+</verb></tscreen>
+ y si somos de Macintosh, esto otro:
+<tscreen><verb>
+\usepackage[applemac]{inputenc}
+</verb></tscreen>
+ (aunque hay editores de Mac que guardan como <tt/latin1/ o <tt/utf8/).
+ <p>
+ Por lo tanto, el mtodo recomendado para utilizar caracteres de 8
+ bits en TODAS las plataformas en &latexe; es escribir:
+<tscreen><verb>
+\usepackage[tipo]{inputenc}
+</verb></tscreen>
+ para decir qu pgina de cdigos de entrada usamos.
+ <p>
+ Ni este mtodo ni el que se menciona en
+ <ref id="raw-characters" name="acentos &latex;"> son vlidos en modo
+ matemtico.
+
+ <sect2>Cmo introducir acentos en modo matemtico?<label id="acentos-math">
+ <!-- ................................................................... -->
+ <p>
+ Para introducir acentos en modo matemtico no hay ms remedio que
+ hacerlo mediante rdenes &latex;, pero en este caso son distintas de
+ las de la seccin
+ <ref id="raw-characters" name="acentos &latex;">. Por ejemplo
+ <em/mx/ se escribira en modo matemtico como <tt/m\acute{a}x/ y
+ <em// como <tt/\tilde{n}/. Si se quiere un acento sobre una i,
+ tanto <em/spanish/ para <em/babel/ como el paquete <em/dotlessi/
+ <tt>(CTAN:macros/latex/contrib/supported/bezos/dotlessi.sty)</tt>
+ proporcionan la orden <tt>\dotlessi</tt>; por ejemplo, mn se
+ escribira <tt>m\acute{\dotlessi}n</tt>.
+ <p>
+ <em/spanish.sty/ ya proporciona algunas de estas palabras
+ acentuadas, por ejemplo, despus de cargar el paquete <em/babel/ con
+ la opcin <em/spanish/ mediante <tt/\usepackage[spanish]{babel}/,
+ <tt/$\min a$/ permite escribir la palabra acentuada. Tambin
+ proporciona un <tt/\dotlessi/ que complementa a <tt/\imath/.
+
+ <sect1>Puedo compartir mis archivos &latex; en los que he escrito los acentos directamente?
+ <!-- ====================================================================== -->
+ <p>
+ Si los caracteres acentuados estn escritos mediante rdenes &latex;
+ pueden compartirse sin problemas, ya que se utiliza nicamente
+ codificacin de 7 bits.
+ <p>
+ Si introduzco las letras acentuadas directamente como en
+ <ref id="8bitintro" name="utilizando inputenc">, tendr dos posibles
+ problemas:
+ <enum>
+ <item>
+ Me servir para otros ordenadores que utilicen una pgina de
+ cdigos diferente?, pues la segunda mitad del conjunto de
+ caracteres es distinta de unos a otros.
+ <item>
+ Podr enviarlo por correo electrnico?, pues solamente acepta 7
+ bits.
+ </enum>
+ Cmo se soluciona esto? Con GNU <em/recode/, con MIME, o con las dos
+ cosas, segn el caso.
+ <enum>
+ <item>
+ Si simplemente se quiere procesar el documento, s que servir
+ para otros ordenadores: Ejemplo: Si nosotros tenemos Unix y
+ alguien que usa Macintosh nos da (en disquete) un archivo con los
+ cdigos del Mac, nuestro &latex; lo entender y lo procesar bien
+ si lleva la llamada a <em/inputenc/, dando el resultado correcto,
+ aunque no podamos ver correctamente el texto original con nuestro
+ editor de texto.
+ <p>
+ Si queremos adems modificar el documento o simplemente ver bien
+ o simplemente ver bien el texto sin procesar original,
+ necesitaremos convertirlo a la pgina de cdigos que se utilice
+ en nuestro ordenador. Para ello recurriremos a GNU <em/recode/
+ escribiendo:
+<tscreen><verb>
+recode applemac:latin1 archivo.tex
+</verb></tscreen>
+ que nos convierte el documento de la pgina de cdigos
+ <tt/applemac/ a la <tt/latin1/. Si ahora modificamos la lnea
+ del <em/inputenc/ para que ponga <tt/latin1/ en lugar de
+ <tt/applemac/ todo funciona exactamente igual que antes en
+ cuanto al resultado. Magia! Dnde encontrar fuentes o binarios
+ precompilados de <em/recode/? En los siguientes lugares:
+ <p>
+ <descrip>
+ <tag/fuentes/ En cualquier rplica del archivo GNU, en el
+ directorio <tt/recode/.
+ <tag/DOS/
+ <htmlurl name="ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos_only"
+ url="ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos_only">
+ o en el mismo lugar en cualquier rplica del archivo
+ <em/simtel/.
+ <tag/DOS32/
+ <htmlurl name="ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/"
+ url="ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/">
+ o en el mismo lugar en cualquier rplica del archivo <em/simtel/.
+ <tag/win32/
+ <htmlurl name="http://www.weihenstephan.de/~syring/win32/UnxUtils.html"
+ url="http://www.weihenstephan.de/~syring/win32/UnxUtils.html">
+ <tag/unix/ En caso de no tener directamente binarios
+ precompilados, suele ser sencillo compilar el programa a
+ partir de las fuentes para cada sistema unix concreto.
+ </descrip>
+ <p>
+ <item>
+ Para evitar problemas con el correo, siempre se puede convertir el
+ documento a formato &latex; <bf/antes/ de mandarlo por correo.
+ Despus de todo, la mayora de lo que se escribe es para uno
+ mismo, no para mandarlo por correo. Ejemplo: Si alguien tiene un
+ Mac, para enviar algo por correo debe en primer lugar hacer una
+ copia del documento (pues GNU <em/recode/ machaca el
+ original). Con la copia se puede hacer:
+<tscreen><verb>
+recode -d applemac:latex archivo.tex
+</verb></tscreen>
+ y ya podemos enviar el <tt/archivo.tex/ resultante por correo.
+
+ Supongamos que el receptor trabaja con Unix, tendra que escribir:
+<tscreen><verb>
+recode -d latex:latin1 archivo.tex
+</verb></tscreen>
+ y cambiar el <tt/inputenc/, en su caso.
+ <p>
+ En cualquier caso, si es posible, es mucho mejor enviar el
+ archivo directamente con acentos utilizando el estndar MIME con
+ <em/quoted-printable/, de esta forma llega el archivo con los
+ acentos intactos an usando los canales habituales de 7
+ bits. Naturalmente debemos ponernos de acuerdo con el receptor
+ del mensaje para que l tambin tenga un programa que acepte
+ MIME, pero dado que es un estndar, todo el mundo debera acabar
+ tenindolo.
+ </enum>
+ <em/Nota al margen/: <tt/recode 3.4/ no transforma correctamente de
+ <tt/850/ a <tt/iso/, porque no convierte bien los retornos de carro. A
+ partir de la versin <tt/3.4.1/ se supone que lo hace
+ correctamente. Si la versin de <tt/recode/ que tenemos es la
+ problemtica, se puede usar la opcin <tt/-a/ de <tt/unzip/ para
+ corregir los retornos de carro. Si nuestro documento no tiene
+ maysculas acentuadas, se puede usar la opcin <tt/ibmpc:l1/
+ (<tt/ibmpc/ es sinnimo de <tt/437/).
+
+ <sect1>Por qu cuando se selecciona texto en Adobe Reader o xpdf, desde un documento PDF generado con LaTeX, las letras acentuadas y ees no se copian bien?
+ <!-- ====================================================================== -->
+ <p>
+ El problema aparece cuando se utiliza un tipo de letra que no utiliza
+ la codificacin <tt/T1/, y desaparece cuando se usa.
+ <p>
+ El tipo por omisin de &latex; es el <em/Computer Modern/ que no
+ contiene vocales acentuadas. Cuando el texto usa por ejemplo <em//,
+ &latex; crea esta letra juntando dos caracteres, una <tt/a/ y un
+ acento agudo. El aspecto en pantalla y en papel es el correcto, pero
+ al seleccionar ese texto en el Acrobat Reader, lo que se obtiene es la
+ secuencia <tt/'a/.
+ <p>
+ Otros tipos de letra s contienen una letra <em//, y si se usa este
+ tipo y se indica a &latex; que use la codificacin <tt/T1/, la
+ seleccin de texto en Reader ya funcionar bien. As que el problema
+ se soluciona siguiendo estos pasos:
+ <itemize>
+ <item>
+ Indicarle a &latex; que use la codificacin <tt/T1/. Esto se logra
+ mediante un <tt>\usepackage[T1]{fontenc}</tt>.
+ <item>
+ Disponer de una fuente que realmente use esa codificacin.
+ </itemize>
+ Si ponemos <tt>\usepackage[T1]{fontenc}</tt> sin ms en un documento,
+ entonces &latex; cambia el tipo por omisin, y en vez de <em/Computer
+ Modern/, usar <em/European Computer Modern/ (EC). Si este tipo est
+ instalado, el PDF se generar sin problemas y el asunto de seleccionar
+ texto quedar arreglado. Pero aparecer otro problema, y es que
+ normalmente los tipos EC que vienen instaladas en las distribuciones
+ de &latex; vienen slo en formato PK, que es un formato que despus se
+ ve muy mal en el Reader (como borroso y descolocado).
+ <p>
+ Para esto la solucin tpica sola ser usar el paquete <em/ae/, el
+ cual instala un tipo virtual, que aparentemente usa la codificacin
+ <tt/T1/ (para que &latex; quede contento), pero que en realidad usa
+ las fuentes CM en vez de las EC (para poder usar los tipos postscript
+ en vez de los PK y as tener un PDF que se vea bien con el
+ Reader). Sin embargo esta solucin hace que el problema de la
+ seleccin de texto reaparezca, ya que, aunque desde el punto de vista
+ de &latex; los tipos <em/ae/ usan codificacin <tt/T1/, la realidad
+ es que en el PDF final no lo usa, y la <em// sigue siendo una
+ combinacin de <tt/a/ y <tt/'/ (como no poda ser de otra forma, ya
+ que la fuente CM no tiene el carcter <em//).
+ <p>
+ As que en este caso el truco de usar el paquete <em/ae/ no sirve, y
+ no queda ms remedio que recurrir a un tipo que <em/realmente/ use la
+ codificacin <tt/T1/, como los tipos Postscript estndar (Times-Roman, Palatino, etc.)
+ <p>
+ Existe una versin postscript de los tipos EC, cuyo desarrollo tiene
+ lugar junto al del lenguaje de descripcin musical <em/lilypond/ y
+ estn disponibles en
+ <htmlurl url="http://www.lilypond.org/download/fonts/"
+ name="http://www.lilypond.org/download/fonts/">. Asimismo los tipos
+ <em/cm-super/, disponibles en <tt>CTAN:fonts/ps-type1/cm-super/</tt>
+ tambin aceptan la codificacin <tt/T1/.
+ <p>
+ Resumiendo, la solucin es bien buscar y usar los tipos <tt/EC/ o
+ alguno que utilice la codificacin <tt/T1/, o si no compensa el
+ esfuerzo utilizar directamente los tipos Postscript estndar. Para
+ ello basta aadir al prembulo del documento
+<tscreen><verb>
+\usepackage{times} % Usar tipo Times-Roman
+\usepackage[T1]{fontenc} % Usar la codificacin T1
+</verb></tscreen>
+ Con esto ya funcionar lo de cortar y pegar desde el Reader, aunque
+ utilizando otro tipo de letra con otra mtrica que puede cambiar la
+ maquetacin. En vez de <em/times/ tambin pueden utilizarse
+ <em/palatino/ o <em/bookman/, dependiendo de los gustos.
+
+<sect1>Cmo cambiar los literales que produce &latex;?<label id="literales">
+<!-- ==================================================================== -->
+<p>
+ Cuando Lamport hizo el &latex; original, proporcion una serie de estilos
+ estndar como ejemplo de uso. Estos estilos se hicieron muy populares,
+ principalmente porque todas las instalaciones de &latex; los tienen. Sin
+ embargo, estos estilos utilizan unos convenios muy particulares y es fcil que
+ un usuario desee cambiarlos. Algo especialmente molesto para el uso en
+ castellano de los estilos estndar, es que generan determinados ttulos
+ (p.ej. <em/Contents/, <em/Bibliography/, etc.) en ingls, lo que hace
+ inaceptable su uso.
+<p>
+ Aunque era posible crear versiones modificadas para otros idiomas, se extendi
+ la idea de internacionalizar dichos estilos. Por ejemplo, donde pona la
+ palabra <tt/Contents/ se ha cambiado por <tt>\contentsname</tt> y se define
+ aparte el valor de esta macro.
+<p>
+ Esta es la forma en que funciona &latexe; actualmente. De esta manera, es
+ posible continuar usando los mismos estilos estndar en diferentes idiomas,
+ simplemente redefiniendo el valor de estas macros en el documento o en un
+ estilo aparte, por ejemplo con
+<tscreen><verb>
+\renewcommand{\contentsname}{Tabla de materias}
+</verb></tscreen>
+<p>
+ Un paquete de estilos que hace esto es babel -- Vase
+ <ref id="que-es-babel" name="Qu es babel?">. Cuando se quieren hacer estos
+ cambios en un documento que utiliza <em/babel/ con <em/spanish.sty/ hay que
+ proceder de una forma un poco distinta. Vase
+ <ref id="sectnames" name="Modificando los literales de spanish.sty">
+
+<sect1>Cmo hacer que &latex; parta correctamente las palabras en castellano?
+<!-- ==================================================================== -->
+
+<sect2>Qu configuraciones (o patterns) existen para la particin de palabras?<label id="patrones-guionado">
+<!-- ................................................................. -->
+<p>
+ Lo primero que hay que decir es que la particin en castellano es algo mucho
+ ms complejo de lo que pudiera parecer a simple vista. Aunque el espaol es un
+ lenguaje muy regular, tiene ciertas anomalas que convierten este tema en un
+ campo minado. Hay dos conclusiones bsicas: 1) No es posible encontrar el 100%
+ de los cortes legales y 2) no es deseable. Para empezar, la Academia permite
+ partir tanto por componentes (sub-ur-ba-no) como silbicamente
+ (su-bur-ba-no). Adems el concepto de slaba es en algunos casos confuso y la
+ etimologa tampoco ayuda (Ej: su-bli-me, a pesar de derivar de sub-limis,
+ contra sub-li-mi-nal). Sin mencionar que los conceptos de diptongo e hiato
+ distan mucho de estar claros. Este ltimo caso viene a carecer de importancia,
+ pues libros de estilo consultados prescriben ignorar los hiatos al partir
+ palabras. El siguiente comentario de Fernando M. Fournon Gonzlez-Barcia es
+ interesante para ilustrar los problemas:
+ <quote>
+ "La RAL dice que es POTESTATIVO lo de la separacin por prefijos. Al menos en
+ el esbozo, que si somos puristas y nos atenemos a la nica gramtica vlida,
+ la del 31, casi ni eso."
+ </quote>
+ <quote>
+ "Creo que, estticamente, lo mejor es no partir nunca, salvo cuando la cosa
+ vaya a quedar muy fea (esta recomendacin tambin la hace la RAL), como hace
+ el &latex;, y entonces partir lo ms conservadoramente posible. Si para los
+ poqusimos casos en que un prrafo se pone pesado y en vez de partir
+ subur-bano hay que hacer sub-urbano, pues ..., que se haga a mano, no?."
+ </quote>
+ <quote>
+ "Otra cosa es que al partir surjan vocablos malsonantes. Esto S que debera
+ de comprobarlo cualquier separador de palabras, pues normalmente es muy
+ difcil detectarlos a simple vista (si es que hay tiempo para releer nuestros
+ propios artculos). O sea, que antes que una lista de prefijos, sugerira la
+ creacin de una lista de <em/tacos/ y cacofonas varias. :-)"
+ </quote>
+ Es decir, lo mejor es evitar cualquier caso conflictivo en los patrones
+ (<em/patterns/) de uso general. Localmente puede hacerse los que se quiera,
+ usando excepciones o introducindolos a mano, por ejemplo.
+<p>
+ Al da de hoy existen 4 tablas diferentes de particin:
+ <itemize>
+ <item>
+ Los producidos en 1986 por Armando Jinich, Mara Garza y Max Daz de Aurion
+ Tecnologa, Mxico. Estn en el dominio pblico desde 1990. Pueden encontrarse
+ en:
+ <quote>
+ <htmlurl url="ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex" name="ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex">
+ </quote>
+ Estos patrones han sido producidos a partir de las reglas de la
+ gramtica. Actualmente no soportan explcitamente acentos. Max Daz es
+ actualmente <tt/max _AT_ east.aurora.com/
+ <item>
+ Los producidos por Manuel Vzquez de la Universidad de Zaragoza, que puede ser
+ localizado en <tt/(vazquez _AT_ cc.unizar.es)/. Estos patrones estn basados
+ en la gramtica.
+ <item>
+ Los que distribuye Arbortext producidos por Sistemas Grficos y Audiovisuales
+ de Chihuahua. Mxico. Estos estn generados a partir de un
+ diccionario. Soportan acentos.
+ <item>
+ Los producidos por Julio Snchez, que pueden obtenerse en:
+<tscreen><verb>
+CTAN:language/spanish/hyphen
+</verb></tscreen>
+ Estos soportan una variedad de opciones, incluido el soporte de acentos, tanto
+ como ligaduras como con el cdigo <tt>IS 8859/1</tt> (<tt/ISO Latin1/) para
+ ML-&tex; o &tex; 3.X. Adems, <em/son los actualmente recomendados por
+ Cervan&tex;/.
+</itemize>
+
+<sect2>Cmo activo el patrn de particin de palabras para el castellano?<label id="guionado">
+<!-- ................................................................... -->
+<p>
+ Para activar el patrn de particin para el castellano es necesario tener
+ babel -- Vase <ref id="que-es-babel" name="Qu es babel?"> -- instalado y
+ generar el formato cargando el patrn de separacin en slabas en
+ castellano. Esto podemos hacerlo de la siguiente manera
+<!-- (el path lo doy relativo a texmf, depende
+de cada distribucin donde reside este directorio, por ejemplo en RedHat 5.2 est en /usr/share/texmf) -->
+<p>
+<descrip>
+<tag/Para &tex; y &latex;: Cambiando el archivo <tt>language.dat</>/
+<itemize>
+<item>
+ Editar el archivo <tt/language.dat/. Dependiendo de la distribucin de &tex;
+ utilizada este archivo puede estar en distintos lugares. Por ejemplo en
+ te&tex; el rbol de &tex; parte de <tt>TEXMF=/usr/share/texmf</tt> y el
+ archivo en cuestin est en <tt>TEXMF/tex/generic/config/language.dat</tt>. En
+ al caso de <em>Debian/GNU-Linux</em>, est en <tt>/etc/texmf/language.dat</tt>
+ y el otro es un enlace a ste.
+<item>
+ Borrar el <tt/%/ que est al principio de la linea <tt/spanish/. Si mal no
+ recuerdo viene preparado con silabeo en alemn, si no lo
+ quieren pongan un <tt/%/ adelante. Tambin viene predefinido
+ ingls (o alguna de sus variantes, por ejemplo
+ american). ste debe estar siempre definido as que no debe
+ desactivarse.
+<item>
+ Es conveniente tambin verificar que la lnea con <tt/nohyphenation/ est
+ activada (sin el comentario). sto es muy til cuando se quiere desactivar la
+ particin de palabras.
+<item>
+ En caso de tener el Mik&tex;, la operacin es la misma, pero el archivo
+ <tt/language.dat/ est en <tt>TEXMF\tex\generic\hyphen\local</tt> o en
+ <tt>TEXMF\tex\generic\config</tt> donde <tt>TEXMF</tt> representa el punto del
+ que parte el rbol de directorios &tex;
+<item>
+ te&tex; tiene la utilidad <em/texconfig/ que invocada como
+<tscreen><verb>
+# texconfig hyphen latex
+</verb></tscreen>
+ lanza un editor para cambiar el fichero <tt/language.dat/ y que, al cerrar el
+ editor, genera los formatos automticamente, por lo que no es necesario hacer
+ el paso siguiente explcitamente.
+</itemize>
+
+<tag/Para &latex;./
+ Una vez hecho lo anterior no es necesario ms que rehacer los formatos
+ -- Vase <ref id="formatos" name="Cmo rehacer los formatos?"> --. Entonces
+ cuando se llame a <em/babel/ con la opcin <tt/spanish/, ste se encargar de
+ utilizar los patrones de guionado en castellano.
+
+<tag/Para <tt/plain/-&tex;/
+ Por omisin, cuando el <tt/initex/ crea el formato, carga el archivo
+ <tt/hyphen.tex/ que contiene las reglas de silabeo en ingls. Para activarlo
+ tambin en <em/plain-&tex;/ se debe copiar el archivo <tt/hyphen.cfg/ como
+ <tt/hyphen.tex/ en algn sitio que en el camino de bsqueda de &tex; est
+ antes del <tt/hyphen.tex/ que viene como parte de <tt/plain-&tex;/ y
+ asegurarse que existe el archivo <tt/ushyph1.tex/ (que realmente es el mismo
+ que el <tt/hyphen.tex/ original, pero con otro nombre). Este paso no es
+ necesario si slo se quiere la particin de palabras para &latex; y se va a
+ utilizar <em/babel/, pero tampoco sobra.
+<p>
+ Para los usuarios de <em/te&tex;/ los archivos estn en
+ <tt>TEXMF/tex/config/babel/hyphen.cfg</tt> y el <tt/hyphen.tex/ original en
+ <tt>TEXMF/tex/generic/hyphen/hyphen.tex</tt>
+<p>
+ Para los usuarios de Mik&tex;, los archivos estn en
+ <tt>TEXMF/generic/hyphen/hyphen.cfg</tt> y <tt>TEXMF/generic/hyphen/hyphen.tex</tt>
+<p>
+ En caso de no conseguirse hacer lo anterior tambin puede sustituirse el
+ archivo <tt/hyphen.tex/ por el <tt/hyphen.cfg/, pero debe tenerse cuidado al
+ actualizar la distribucin de no sobreescribir el <tt/hyphen.tex/ con al que
+ venga con la distribucin nueva.
+<p>
+ Entonces es necesario reconstruir el formato como se indica en
+ <ref id="formatos" name="Cmo rehacer los formatos?">.
+<p>
+ Cuando se quiere usar el silabeo en castellano, hay que agregar en el archivo
+ <tt/.tex/, al principio, una linea que diga <tt/\language1/ si el castellano
+ es el segundo lenguaje (no sinnimo) del <tt/language.dat/ (<tt/\language0/
+ correspondera al ingls americano)
+</descrip>
+
+<sect2>A pesar de que he activado los patrones de particin de palabras del castellano, hay una palabra que se me resiste
+<!-- .................................................................. -->
+<p>
+Aunque los patrones de particin de palabras intentan abarcar el mayor nmero de
+ casos posible, siempre puede quedar alguna palabra
+ recalcitrante. Tambin puede ocurrir que la particin sea correcta,
+ pero no deseable a los ojos del autor del documento. En este caso
+ hay dos posibilidades:
+<itemize>
+<item>
+Si la palabra es poco frecuente y slo falla en muy pocas ocasiones. En este
+ caso es preferible decirle directamente a la palabra en el lugar
+ donde aparece, dnde se le permite partirse, mediante
+ <tt>\-</tt>. Por ejemplo:
+<tscreen><verb>
+fotorrefractivo y electroptico --> foto\-rre\-frac\-tivo y elec\-tro\-ptico
+</verb></tscreen>
+<item>
+Si es una palabra frecuente que es una potencial causa de problemas en el
+ documento. En este caso es preferible definir en el prembulo
+ del documento cmo se permite la particin de esta palabra de
+ forma global para todo el documento, mediante
+ <tt/\hyphenation/. Por ejemplo:
+<tscreen><verb>
+\hyphenation{foto-rre-frac-tivo,elec-tro-ptico}
+</verb></tscreen>
+</itemize>
+
+<sect2>Mi &tex; no parte las palabras que tienen acentos. Por qu?
+<!-- ........................................................... -->
+<p>
+El primitivo <tt>\accent</tt> detiene la particin. Es posible ayudar a &tex;
+ invocando la siguiente macro despus de un acento:
+<tscreen><verb>
+\def\allowhyphens{\penalty10000 \hskip0pt}
+</verb></tscreen>
+<tt/spanish.sty/ lo hace automticamente en caso necesario. En cualquier caso,
+ lo mejor es usar fuentes con las letras acentuadas como por ejemplo
+ las descritas en <ref id="EC/DC" name="DC/EC">, o ML-&tex;, y
+ patrones de particin que contemplen esto.
+
+<sect1>Acerca de <tt/spanish.sty/
+<!-- ==================================================================== -->
+<p>
+ Los archivos para escribir en castellano con <em/babel/ (<tt/spanish.*/) los
+ cre y mantuvo durante mucho tiempo Julio Snchez. Ahora esos archivos los
+ mantiene Javier Bezos y desde hace tiempo son oficiales en la estructura de
+ <em/babel/. Es posible que alguna distribucin de &latex; an utilice los
+ archivos antiguos y que haya algunas diferencias respecto de lo que aqu se
+ describe. La actualizacin est ms que recomendada.
+
+<sect2> Dnde se puede obtener la documentacin de spanish en castellano?
+<!-- ......................................................................... -->
+<p>
+ La documentacin de <em/spanish/ que se incluye al componer <tt/user.drv/ est
+ en ingls, pero el archivo <tt/spanish.dtx/ tambin la incluye en
+ castellano. Basta con componer este archivo y obtendremos un detallado manual
+ como <tt/spanish.dvi/.
+<p>
+ La versin ms reciente del manual de <em/spanish.sty/ se encuentra en
+ <htmlurl url="http://perso.wanadoo.es/jbezos/archive/spanish.pdf"
+ name="http://perso.wanadoo.es/jbezos/archive/spanish.pdf">. Debe
+ tenerse cuidado con las versiones, pues puede referirse a una versin muy
+ posterior a la que se encuentra instalada en el sistema.
+
+<sect2>Cmo cambio los nombres de las secciones de bibliografa, ndice, etc... que pone <tt/spanish.sty/? <label id="sectnames">
+<!-- ......................................................................... -->
+<p>
+ Si no importa que este cambio no siga las caractersticas de <em/babel/ y
+ <em/spanish/ de cambio de idioma sobre la marcha, etc.., se puede hacer de la
+ misma forma que en la seccin <ref id="literales"
+ name="Cmo cambiar los literales que produce &latex;?"> poniendo las
+ definiciones despus de llamar a babel. El problema de este mtodo es que no
+ est bien integrado con <em/babel/ y por ese lado puede dar problemas, ya
+ <em/babel/ activa algunos cambios al llegarse al <tt>\begin{document}</tt>.
+<p>
+ Si embargo existe una forma ms elegante e integrada con <em/spanish/ y
+ <em/babel/. En el prembulo del documento hay que aadir lo siguiente, por
+ ejemplo, para cambiar Bibliografa por Referencias y Tabla por Cuadro
+<tscreen><verb>
+\addto\captionsspanish{%
+\def\bibname{Referencias}%
+\def\tablename{Cuadro}%
+}
+</verb></tscreen>
+ Y as con todos los nombres necesarios. La lista de nombres est en los dos
+ lugares siguientes
+<tscreen><verb>
+TEXMF/tex/generic/babel/spanish.ldf
+TEXMF/tex/generic/babel/spanish.tex
+</verb></tscreen>
+ <em/Nunca/ deben modificarse los ficheros <em/spanish.ldf/ y <em/spanish.tex/
+ directamente, ya que el documento resultante ya no sera universal, al
+ procesarlo en un sistema distinto dara distinto resultado, y no sera posible
+ acompaar el documento original con los archivos de estilo modificados puesto
+ que la LPPL (la licencia bajo la que se distribuye &latex;) no permite la
+ distribucin de versiones modificadas de stos bajo el mismo nombre.
+
+<sect2>Por qu <tt/spanish.sty/ pone los meses en minscula?
+<!-- ........................................................... -->
+<p>
+Ese es el uso aceptado en la actualidad. Documentos de la propia RAL lo hacen
+ as. El Mara Moliner tambin. Vase la siguiente cita del Mara
+ Moliner, 1990,
+<quote>
+"7. Aunque entre los preceptos de la G.R.A. figura el de escribir con mayscula
+ los nombres de los meses, de los das de la semana y de las
+ estaciones, [...] ha dejado decididamente de usarse la letra
+ mayscula en uno y otro de estos casos"
+</quote>
+
+<sect2>Por qu el spanish de babel reemplaza el punto decimal por una coma?
+<!-- ........................................................... -->
+<p>
+ Por tres razones: 1) porque las normas internacionales establecen que ha de
+ usarse coma para los decimales, excepto en aquellos pases cuya tradicin hace
+ preferible el punto (la propia ISO usa coma en sus informes); 2) porque el
+ punto decimal en Espaa carece de fuerza legal y slo la coma es oficialmente
+ vlida, y 3) porque la coma es el nico signo usado en la vida
+ diaria. Probablemente, la situacin es similar en otros pases, salvo Mxico.
+<p>
+ Se puede cambiar el comportamiento predefinido con la orden
+ <tt>\decimalpoint</tt> o <tt>\spanishdecimal{.}</tt> en el prembulo, despus
+ de cargar <em/babel/. En unas pocas materias, como el anlisis nmerico o la
+ estadstica, es necesario distinguir la coma decimal de la coma para separar
+ datos; en este caso se puede aumentar el espaciado de estas ltimas con:
+<tscreen><verb>
+\makeatletter
+\def\es@decimal{{\mathchar&quot;613B}}
+\mathcode`,=&quot;8000
+\begingroup
+\catcode`,=13
+\gdef,{\mkern2mu\mathchar&quot;613B\mkern8mu}
+\endgroup
+\makeatother
+</verb></tscreen>
+ (Se pueden probar otros valores en lugar de 2 [antes] y 8 [despus]. La unidad
+ mu de &tex; es para matemticas [aprox. 1/18 em].)
+
+<sect2>
+Por qu <tt/spanish.sty/ pone los nmeros romanos siempre en mayscula?
+<!-- ........................................................... -->
+<p>
+ Realmente no son maysculas, sino versalitas (<em/small caps/). En la
+ tradicin tipogrfica espaola no se utilizan los nmeros romanos en
+ minsculas, que se sustituyen por las versalitas. Por este motivo, el autor de
+ <em/spanish/ para babel, lo ha incluido en ste.
+
+<sect2>
+Por qu <tt/spanish.sty/ acenta la I de ndice?
+<!-- ........................................................... -->
+<p>
+ As lo han sostenido los tratadistas ms importantes sobre ortografa y
+ tipografa desde hace ms de un siglo: &lt;&lt; La maysculas deben llevar la
+ tilde que les corresponda &gt;&gt; (Sanmart, 1907). La RAE finalmente lo ha
+ considerado normativo en su ortografa de 1999: &lt;&lt;El empleo de las
+ maysculas no exime de poner tilde cuando as lo exijan las reglas de
+ acentuacin &gt;&gt; (p. 31).
+
+<sect2>
+Por qu spanish para babel dice cuadro en lugar de tabla?
+<!-- ........................................................... -->
+<p>
+ Tal y como se indica en el manual, el ingls <em/table/ y el espaol
+ <em/tabla/ son falsos amigos. Para ser ms precisos, podemos reproducir lo que
+ dice el Diccionario acadmico:
+ <quote>
+ Cuadro [...] 10. m. Conjunto de nombres, cifras u otros datos presentados
+ grficamente, de manera que se advierta la relacin existente entre ellos.
+ <p>
+ Tabla [...] 12. f. Cuadro o catlogo de nmeros de especie determinada,
+ dispuestos en forma adecuada para facilitar los clculos. Tabla de
+ multiplicar, de logaritmos, astronmica.
+ </quote>
+ El ingls <em/table/ tiene un sentido mucho ms general que el que tiene el
+ espaol <em/tabla/, y as tendramos tabla de logaritmos y tabla de
+ multiplicar frente a cuadro de reyes medievales y cuadro de aminocidos
+ esenciales. En este aspecto el espaol tiene ms riqueza y precisin que el
+ ingls.
+<p>
+ En fin, <em/cuadro/ es todava la forma ms frecuente, la ms castellana y
+ tradicional, y la preferida por los mejores tipgrafos (Morato, Martnez
+ Sicluna, Martnez de Sousa, etc.). Nada impide, por supuesto, redefinir el
+ nombre si resultara que todos los cuadros de un documento son tablas, tal y
+ como describe el manual y esta FAQ.
+
+<sect2>Cmo consigo que <em/babel/ y <tt/spanish.sty/ no utilicen los atajos de teclado NUNCA?
+<!-- .................................................................... -->
+<p>
+ Este ha sido un problema muy frecuente con babel y spanish, que ha dado como
+ consecuencia que, por ejemplo, en las bibliografas nombres como
+ "J.~N. Apellido" aparecieran como "J.. Apellido". Para solucionar este
+ problema, spanish ofrece ahora la orden <tt>\deactivatetilden</tt> que elimina
+ el uso de <tt/~/ para la ee, al tiempo que preserva su funcin de espacio sin
+ divisin (la orden <tt>\shorthandoff</tt> de babel cancela ambos usos). El
+ estilo <em/spanish/ tambin proporciona ms facilidades para desactivar otras
+ abreviaciones, que estn descritas en <tt>spanish.dtx</tt>, por ejemplo
+ <tt/\deactivatequoting/ en el prembulo.
+<p>
+ Sin embargo sto y el que funcione correctamente ha cambiado mucho entre
+ distintas versiones de <em/babel/ lo que hace que a veces los documentos
+ creados con una versin de babel no sean directamente portables a otros
+ sistemas. Aunque es recomendable actualizarse a la ltima versin de
+ <em/spanish/ y <em/babel/ en todos los ordenadores implicados, en caso de no
+ poderse hacer, la siguiente lnea (en &latexe;) en el prembulo del documento
+ elimina los atajos de teclado
+<tscreen><verb>
+\AtBeginDocument{\gdef~{\nobreakspace{}}\catcode`\&quot;=12}
+</verb></tscreen>
+ til para documentos que se utilizarn en distintos ordenadores, alguno de
+ ellos con versiones antiguas de babel o spanish.
+
+ <sect1>Cmo puedo indicar la abreviatura de los ordinales?
+ <!-- =================================================== -->
+ <p>
+ En &latexe; pueden utilizarse la rdenes <tt>\textordfeminine</tt> y
+ <tt>\textordmasculine</tt>; por ejemplo, para abreviar Mara,
+ escribimos <tt>M.\textordfeminine</tt>. Una variacin de estas macros
+ ha sido incorporada a <tt/spanish.sty/ versin 3.0 y extendida en la
+ versin 4.0. Se invocan como "a y "o, respectivamente, con la
+ posibilidad de usar <tt>\sptext</tt> para casos como <tt>1\sptext{er}</tt>.
+
+ <sect1>Cmo forzar sangra despus de las cabeceras?
+ <!-- ============================================= -->
+ <p>
+ El objetivo de esa sangra (<em/indentation/ para los que no estn al
+ tanto) es marcar claramente la separacin de los prrafos. Como tal,
+ es superflua despus de una cabecera. Hay otros sitios en los que, no
+ slo es superflua, sino que es confusa, como despus de un texto que
+ ya va sangrado (entorno quote, <tt>\[</tt> <tt>\]</tt>, un array,
+ etc.) Sin embargo, es esencialmente una cuestin de gusto.
+ <p>
+ Modificarlo en un estilo es bastante fcil. La mayora de las
+ secciones, etc. en &latex; son algo as como (en <tt/art10.sty/):
+<tscreen><verb>
+\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus
+-1ex minus -.2ex}{2.3ex plus .2ex}{\Large\bf}}
+\def\subsection{\@startsection{subsection}{2}{\z@}{-3.25ex plus
+ -2ex minus -.2ex}{1.5ex plus .2ex}{\large\bf}}
+</verb></tscreen>
+ El cuarto parmetro, si es negativo, indica que no se debe sangrar en
+ el primer prrafo tras la cabecera. Cmbiese a positivo.
+ <p>
+ Hay otro procedimiento para estilos que ya estn escritos y consiste
+ en decir:
+<tscreen><verb>
+\let\@afterindentfalse\@afterindenttrue
+\@afterindenttrue
+</verb></tscreen>
+ Esta solucin es la proporcionada en <tt/indentfirst.sty/ por David
+ Carlisle.
+
+ <sect1>Cmo puedo escribir las funciones matemticas en espaol?
+ <!-- ======================================================== -->
+ <p>
+ Comentario: Hay gente que discute el que las funciones vayan en
+ espaol y lleve acento el lm, mx, etc. Argumentan que los nombres
+ vienen del latn y all no haba acentos (y que en ingls tambin
+ vienen del latn, lo cual, por ejemplo, es claramente incierto con
+ gcd). El caso es que en todos los libros tradicionales en castellano
+ se escriba lm y mx con acento. Si ltimamente no se hace es
+ precisamente porque &tex; (en ingls) no lo tiene as. Todava estamos
+ a tiempo de no cometer ese error:
+ <p>
+ El caso ms comn es el del seno que, en plain &tex;, basta definirlo como
+<tscreen><verb>
+\def\sen{\mathop{\rm sen}\nolimits} % Sustituye a \sin
+</verb></tscreen>
+ Anlogamente,
+<tscreen><verb>
+\def\mcd{\mathop{\rm mcd}\nolimits} % Sustituye a \gcd
+
+\def\senh{\mathop{\rm senh}\nolimits} % Sustituye a \sinh
+
+\def\arcsen{\mathop{\rm arcsen}\nolimits} % Ni el arcsin ni el
+% arccos originales dejan espacio entre arc y sin o cos.
+</verb></tscreen>
+ Cuando la funcin en espaol tiene algn acento (sobre todo en la i), es ms complicado:
+<tscreen><verb>
+\def\max{\mathop{\rm m\acute ax}}
+
+\def\min{\mathop{\rm m\acute\mathchar&quot;7010n}}
+
+\def\inf{\mathop{\rm \acute\mathchar&quot;7010nf}}
+
+\def\lim{\mathop{\rm l\acute\mathchar&quot;7010m}}
+
+\def\limsup{\mathop{\rm l\acute\mathchar&quot;7010m\, sup}} % El limsup
+% y el liminf originales dejan espacio entre lim y sup o inf.
+
+\def\liminf{\mathop{\rm l\acute\mathchar&quot;7010m\, inf}}
+</verb></tscreen>
+ Por ltimo, adaptndolas de su definicin original (ver pg. 361 del
+ &tex;book) para poner el acento en las dos posibilidades de uso de
+ <tt/mod/ hacemos:
+<tscreen><verb>
+\def\bmod{\mskip-\medmuskip \mkern5mu
+ \mathbin{\rm m\acute od} \penalty900 \mkern5mu
+ \mskip-\medmuskip}
+\def\pmod#1{\allowbreak \mkern18mu ({\rm m\acute od}\,\,#1)}
+</verb></tscreen>
+ En &latex; se puede hacer de forma similar pero usando
+ <tt>\newcommand</tt> o <tt>\renewcommand</tt> en lugar de
+ <tt>\def</tt>.
+
+<sect1>Qu verificadores ortogrficos puedo utilizar para espaol?
+<!-- ========================================================== -->
+<p>
+<descrip>
+<tag/ispell/ <em/ispell/ es un verificador ortogrfico de uso libre que funciona
+ en UNIX, aunque hay un port para <em/emx/ en fase beta --que funciona o debe
+ funcionar tanto en DOS (con 386 o superior) como en OS/2 2.x o en OS/2 Warp.
+ <p>
+ Para <em/ispell/ existe lo siguiente:
+ <p>
+ <itemize>
+ <item> Ficheros de afijos para espaol:
+ <tabular ca="ll">
+ URL:|ftp://ftp.dante.de/tex-archive/language/spanish/ispell@
+ ARCHIVO:|castellano.aff.gz@
+ COMENTARIOS:|diccionario y parche elisp disponible en el mismo lugar.@
+ |Vanse los archivos LEEME o README.
+ </tabular>
+ <p>
+ <tabular ca="ll">
+<!-- URL:|http://www.datsi.fi.upm.es/&tilde;coes@ -->
+ URL:|<htmlurl url="http://www.datsi.fi.upm.es/~coes"
+ name="http://www.datsi.fi.upm.es/&tilde;coes">@
+ ARCHIVOS:|espa&tilde;nol.tar.gz@
+ COMENTARIOS:|incluye espa&tilde;nol.aff, lista de palabras,
+ instrucciones@
+ |y patrones de guionado para TeX en espaol.
+ </tabular>
+ <item>Diccionarios compatibles con ispell:
+ <tabular ca="ll">
+ URL:|ftp://ftp.dante.de/tex-archive/language/spanish/ispell@
+ ARCHIVOS:|palabras.sq.gz@
+ COMENTARIOS:|archivo de afijos y parche elisp disponible en el mismo@
+ |lugar. Vanse los archivos LEEME o README.
+ </tabular>
+ <p>
+ <tabular ca="ll">
+ URLs:|<htmlurl url="http://www.datsi.fi.upm.es/~coes"
+ name="http://www.datsi.fi.upm.es/&tilde;coes">@
+ ARCHIVOS:|espa&tilde;nol.tar.gz@
+ COMENTARIOS:|incluye espa&tilde;nol.aff, lista de palabras,
+ instrucciones,@
+ |y patrones de guionado para TeX en espaol.
+ </tabular>
+ </itemize>
+ El que hay en <tt/ftp.dante.de/ es de Julio Snchez y el que hay en
+ <htmlurl url="http://www.datsi.fi.upm.es/~coes"
+ name="http://www.datsi.fi.upm.es/~coes"> es de Santiago Rodrguez
+ <tt/srodri _AT_ fi.upm.es/ y Jess Carretero <tt/jesus _AT_ fi.upm.es/
+ <p>
+ Dependiendo de como se haya creado el diccionario de castellano es posible
+ que deba llamarse a ispell como
+<tscreen><verb>
+ispell -t -T latin1 -d espanol fichero.tex
+</verb></tscreen>
+ especificando explcitamente la codificacin.
+
+<tag/Excalibur/ Para Macintosh, existe un verificador ortogrfico de documentos
+ &latex; (y plain &tex;) llamado Excalibur. Es gratis, aunque el copyright es
+ del autor, Rick Zaccone <tt/(zaccone _AT_ bucknell.edu)/.
+ <p>
+ Excalibur puede conseguirse por ftp annimo en
+ <htmlurl url="ftp://sol.eg.bucknell.edu/pub/mac"
+ name="ftp://sol.eg.bucknell.edu/pub/mac">.
+ <p>
+ Juan Luis Varona <tt/(jvarona _AT_ dmc.unirioja.es)/ ha creado un diccionario con
+ 292342 palabras (versin de septiembre de 1999) que funciona con
+ Excalibur. Est realizado en formato de 7 bits, y la <tt// la reconoce
+ nicamente como <tt>\'{\i}</tt>. Pero puede modificarse si se desea. La
+ versin ms reciente puede encontrarse en
+ <htmlurl url="ftp://tex.unirioja.es/pub/tex/dict-mac"
+ name="ftp://tex.unirioja.es/pub/tex/dict-mac">
+ <p>
+ Asimismo, en la direccin mencionada para <em/Excalibur/, en el directorio
+ <tt/Excalibur-dictionaries/, se encuentran disponibles los diccionarios de los
+ distintos idiomas. El diccionario espaol puede encontrarse tambin en
+ <tt/CTAN/ en
+<tscreen><verb>
+CTAN:systems/mac/support/excalibur/Spanish_Dictionary.sit.hqx
+</verb></tscreen>
+<tag/4spell/ <em/4spell/ es un verificador ortogrfico para Windows (32 bits)
+ que se distribuye bajo una licencia libre (concretamente la GPL) y tiene un
+ diccionario de castellano. Puede encontrarse en <tt>CTAN:support/4spell</tt>
+<tag/Winedt/
+ El diccionario de Juan Luis Varona tambin se ha adaptado para su uso con el
+ verificador ortogrfico del entorno winedt para Windows. Est disponible en
+<quote>
+<htmlurl url="ftp://tex.unirioja.es/pub/tex/dict-win" name="ftp://tex.unirioja.es/pub/tex/dict-win">
+</quote>
+<tag/amspell/ <em/amspell/ es un verificador ortogrfico para DOS. El
+ diccionario de Juan Luis Varona tambin se ha adaptado para ser utilizado con
+ <em/amspell/. La versin para <em/amspell/ est disponible en
+<quote>
+<htmlurl url="ftp://tex.unirioja.es/pub/tex/dict-pc" name="ftp://tex.unirioja.es/pub/tex/dict-pc">
+</quote>
+y <em/amspell/ en
+<tscreen><verb>
+CTAN:support/amspell
+</verb></tscreen>
+</descrip>
+
+<sect1>Cmo utilizo Bib&tex; en castellano?
+<!-- ========================================================== -->
+<p>
+Para esto hay dos aproximaciones,
+ <sect2>Utilizar estilos adaptables (los <em>abstyles</em>)
+ <!-- -------------------------------------------------------- -->
+ <p>
+ Para que Bib&tex; funcione en espaol, Toms Bautista ha modificado con
+ <em/babel/ una <em/familia adaptable/ de estilos de Bib&tex; (tambin
+ llamadas <em/abstyles/).
+ <p>
+ Con las <em/abstyles/ se tiene la <em/ventaja/ de utilizar un nico estilo,
+ de forma que el idioma de las referencias nicamente depende del elegido con
+ <em/babel/. De este modo, si por h o por b, en cierto momento no se quiere
+ el documento en ingls, sino por ejemplo en espaol o en alemn, slo habra
+ que cambiar la opcin que corresponde en babel y no tambin el estilo puesto
+ dentro del <tt/\bibliographystyle{estilo}/.
+ <p>
+ Adems, con las abstyles slo es necesario un <tt/aplain.bst/ preparado
+ para distintos idiomas, segn lo elegido en babel. Estn disponibles en
+ <tt>CTAN:biblio/bibtex/contrib/abstyles-babel/</tt>.
+ </sect2>
+ <sect2>Utilizar el paquete <tt>custom-bib</tt><label id="custombib">
+ <!-- -------------------------------------------------------- -->
+ <p>
+ El paquete <em/custom-bib/ (disponible en
+ <tt>CTAN:macros/latex/contrib/supported/custom-bib/</tt>) permite crear
+ estilos bibliogrficos a medida, con una amplia serie de opciones y de
+ idiomas. Para utilizarlo, una vez desempaquetado debe hacerse
+<tscreen><verb>
+latex makebst.tex
+</verb></tscreen>
+ y responder a las (muchas) preguntas que se formulan. Es conveniente leerse
+ previamente la documentacin para ser consciente de qu se est preguntando
+ en cada momento, ya que muchas de las preguntas no son obvias. El documento
+ de Luis Seidel -- Vase la seccin
+ <ref id="es-tutores" name="Tutoriales en castellano"> -- es una ayuda
+ interesante al respecto.
+ <p>
+ El paquete <em/spanish/ proporciona el fichero <em/esbst.tex/ que es el que
+ debe usarse como <em/babelbst.tex/ para las adaptaciones al castellano. Si
+ la distribucin es antigua, este fichero puede estar prcticamente vaco y
+ tener como nico efecto que no aparezca un mensaje de error. En este caso es
+ conveniente copiar el archivo <em/esbst.tex/ de una versin reciente de
+ <em/spanish/ al directorio donde se va a utilizar el estilo <em/.bst/,
+ con el nombre <em/babelbst.tex/, ya que es el nombre con que lo espera el
+ estilo <em/.bst/ creado.
+ </sect2>
+
+ <sect1>Cmo genero un ndice alfabtico con la ordenacin correcta en castellano?
+<!-- ========================================================================= -->
+<p>
+El problema con que uno se encuentra al utilizar <em/makeindex/ es que no ordena
+ correctamente las palabras con caracteres acentuados, ya que por
+ ejemplo ordena la <tt// como <tt/\'a/ que es lo que &tex; escribe al
+ archivo de ndice y salvo que fuera la ms reciente versin de
+ <em/makeindex/ de 8 bits ni siquiera las reconocera si estuvieran
+ escritas directamente al archivo de ndice como palabras acentuadas. A
+ pesar de las limitaciones mencionadas para los idiomas que no pueden
+ describirse mediante la tabla de caracteres de 7 bits, es posible
+ utilizar <em/makeindex/ en idiomas como el castellano. Para solucionar
+ este problema hay varias aproximaciones:
+<descrip>
+<tag/Decir a <em/makeindex/ cmo debe ordenar la palabra acentuada/
+Por ejemplo, para los acentos o para la <tt// se introducira la entrada al
+ ndice como
+<tscreen><verb>
+\index{optica@ptica}
+\index{indice@ndice}
+\index{can^^ffa@caa}
+</verb></tscreen>
+y para una palabra compuesta como por ejemplo en
+<tscreen><verb>
+\index{optica electromagnetica@ptica electromagntica}
+</verb></tscreen>
+
+<tag/Utilizar el paquete <em>esindex</em>/
+<em/esindex/ es un paquete desarrollado por Javier Bezos para facilitar la
+ escritura de ndices correctamente alfabetizados en castellano. Su
+ nica orden es <tt/\esindex/ que convierte su argumento a una
+ forma adecuada. Por ejemplo,
+<tscreen><verb>
+\esindex{ca'n'on}
+</verb></tscreen>
+equivale a
+<tscreen><verb>
+\index{can^^ffon@ca'n'on}
+</verb></tscreen>
+Es necesario usar babel y que los acentos estn escritos en forma de
+ abreviaciones (<tt/'a/, <tt/'e/, etc.). El paquete utiliza ciertas
+ rdenes internas de babel por lo su funcionamiento puede cambiar
+ con versiones distintas a la 3.6.
+<p>
+Hay que sealar que con este paquete no se crea en el ndice una entrada propia
+ para la palabras que empiezan por ee, sino que tan slo se aaden
+ al final de la ene. En el rarsimo caso de que hubiera palabras
+ que empiezan por ee habra que modificar el archivo <tt/.ind/ a
+ mano. Este paquete puede encontrarse en
+<tscreen><verb>
+CTAN:macros/latex/contrib/supported/bezos/
+</verb></tscreen>
+
+<tag/Utilizar xindy/
+<em/xindy/ es un sistema de indexacin desarrollado por Roger Kehr, del
+ Instituto de Informtica Terica de Darmstadt, que puede ser
+ configurado fcilmente para adaptarse a las normas ortogrficas de
+ distintos idiomas, cada uno de ellos con un alfabeto distinto y
+ con unas reglas de ordenacin tambin distintas. <em/xindy/ puede
+ definir, para cada carcter del alfabeto, dnde debe ser ste
+ ordenado (reglas de ordenacin), as como a qu carcter o cadena
+ es equivalente (reglas de equivalencia). Permite incluso definir
+ reglas de ordenacin de distinto nivel que pueden ser aplicadas de
+ forma sucesiva. Este paquete puede encontrarse en
+ <tt>/CTAN:indexing/xindy/</tt> y su pgina web est en
+<quote>
+<htmlurl url="http://www.iti.informatik.tu-darmstadt.de/xindy/"
+name="http://www.iti.informatik.tu-darmstadt.de/xindy/">
+</quote>
+Existen unos archivos de estilo para utilizar <em/xindy/ en castellano en la
+ pgina anterior y la versin ms reciente, incluyendo binarios
+ para linux se puede encontrar en el directorio
+<htmlurl url="http://www.aq.upm.es/~agmartin/linux/store/xindy"
+name="http://www.aq.upm.es/~agmartin/linux/store/xindy">, con <tt/tgz/ para
+libc5 (xindy-2.0.1.tgz) y libc6 (xindyg21-2.1.tgz) Uno de los estilos
+(<tt/es-mkidx.xdy/) ordena segn las reglas modernas del castellano mientras que
+el otro (<tt/es-tridx.xdy/) ordena segn las reglas ya obsoletas, con ch y
+ll. Su uso es algo distinto del habitual en <em/makeindex/
+<tscreen><verb>
+xindy -f tex2xindy estilo.xdy tu_archivo.idx
+</verb></tscreen>
+donde <em/tex2xindy/ es un filtro que convierte sobre la marcha del formato
+ habitual de los <em/.idx/ al formato especial que utiliza
+ <em/xindy/, <em/estilo.xdy/ puede ser cualquiera de los dos
+ mencionados (u otro cualquiera para otro idioma o particularizado
+ por el autor del documento) y <em/tu_archivo.idx/ es el que crea
+ &latex; a partir de las llamadas a <tt/\index/.
+</descrip>
+
+<!-- ********************************************************* -->
+<sect>Que es...?
+<!-- ********************************************************* -->
+<sect1>Qu es el CTAN (<em/Comprehensive &tex; Archive Network/).<label id="que-es-CTAN"
+<!-- ========================================================= -->
+<p>
+Son las abreviaturas de <em/Comprehensive &tex; Archive Network/ (<em/Red del
+ Archivo Completo de &tex;/). Son tres servidores de FTP que
+ almacenan prcticamente todo lo relacionado con el &tex;. Sus
+ <em/nodos/ son:
+<itemize>
+<item> <htmlurl url="ftp://ftp.dante.de" name="ftp.dante.de"> (Alemania)
+<item> <htmlurl url="ftp://ftp.tex.ac.uk" name="ftp.tex.ac.uk"> (Reino Unido)
+<item> <htmlurl url="ftp://ftp.shsu.edu" name="ftp.shsu.edu"> (Estados Unidos)
+</itemize>
+
+Tambin se puede acceder mediante gopher o WWW con otros nombres, y existen
+ interfaces de acceso como
+<quote>
+<htmlurl url=" http://www.ucc.ie/cgi-bin/ctan" name="http://www.ucc.ie/cgi-bin/ctan">
+</quote>
+que muestra una serie de rplicas del CTAN, y permite hacer bsquedas en ellas.
+<p>
+En los tres casos el material de &tex; est en el directorio
+ <tt>/tex-archive</tt>. Cada uno es un <em/mirror/ o rplica de los
+ otros dos: Los tres contienen lo mismo (con un da de diferencia a lo
+ ms, en teora). Por lo tanto conviene conectarse al que que nos
+ caiga ms cerca. Dado que siempre hay que ir a <tt>/tex-archive</tt>,
+ se puede omitir dicho directorio y darse por supuesto. Por ejemplo,
+ si alguien nos dice que &latex; se encuentra en
+ <tt>CTAN:macros/latex</tt> quiere decir que podemos encontrarlo por
+ ejemplo en el directorio
+<tscreen><verb>
+ftp://ftp.dante.de/tex-archive/macros/latex
+</verb></tscreen>
+Nota: Desde hace tiempo, <tt>ftp.shsu.edu</tt> funciona tan mal que los
+ mantenedores del CTAN han decidido (20 de junio de 1996) no
+ considerarlo ya ms un nodo del CTAN. Para los usuarios de Amrica, se
+ recomienda usar la siguiente <em/rplica/:
+<quote>
+<htmlurl url="ftp://ftp.cdrom.com/pub/tex/ctan" name="ftp://ftp.cdrom.com/pub/tex/ctan">
+</quote>
+En Espaa existe una rplica del CTAN en
+<quote>
+<htmlurl url="ftp://ftp.rediris.es/mirror/tex-archive" name="ftp://ftp.rediris.es/mirror/tex-archive">
+</quote>
+aunque no se actualiza con la misma rapidez que los nodos del CTAN.
+
+<!-- <sect1>Los CD-ROM de Gutenberg. -->
+<!-- ================================= -->
+
+<sect1>Qu es el esquema de codificacin de Cork?
+<!-- ========================================== -->
+<p>
+ Es el cdigo acordado en la reunin del TUG 1990 en Cork, el llamado <em>&tex;
+ 256 international character set</em> que es, al menos en lo que se refiere al
+ castellano, compatible con ML-&tex;, ISO Latin Alphabet 1 (IS 8859/1) y el DEC
+ Multinational Character Set. Que adems, es el de las fuentes DC/EC. Esto
+ significa que es posible utilizar en entrada los caracteres acentuados
+ directamente (por ejemplo con <tt/compose/ en Sun o terminales <tt/VTxxx/
+ (<tt/xxx/ >= 200).
+
+<sect1>Qu es babel?<label id="que-es-babel">
+<!-- ===================================== -->
+<p>
+ <em/Babel/ es un conjunto de estilos escritos por Johannes L. Braams que:
+ <itemize>
+ <item>
+ Proporciona macros tiles para la produccin de documentos en una veintena
+ de idiomas, incluido el espaol.
+ <item>
+ Pblico y en evolucin. Esto significa la posibilidad de enviar documentos a
+ otros sin tener que intercambiar macros primero y que estas macros se actualizan en funcin de las necesidades.
+ <item>
+ La posibilidad de cambiar de idioma a mitad de documento, para, por ejemplo,
+ citar en otro idioma y tener disponibles las macros especficas de ese idioma.
+ <item>
+ Puede ser utilizado en plain &tex; tambin.
+ </itemize>
+ Adems, <em/babel/ convive cmodamente con otros estilos. Por ejemplo,
+ <tt/artikel1.sty/ usa parte de la ayuda de <em/babel/. Es fcil escribir
+ estilos que combinen con <em/babel/. Si tu estilo lo escribes usando para los
+ literales las macros que <em/babel/ define, lo tendrs sin ningn esfuerzo
+ adicional para una veintena de idiomas. Es cierto que la probabilidad de que
+ uses serbo-croata es escasa, pero hay francs, portugus, italiano, alemn,
+ etc. Los convenios de <em/babel/ derivan del trabajo realizado por Hubert
+ Partl. Estilos escritos de forma compatible con el trabajo de Partl, deben
+ funcionar con <em/babel/ en principio. De hecho, es ya estndar este convenio
+ en las versiones de &latex; posteriores a octubre de 1991.
+<p>
+ Babel puede conseguirse en:
+<tscreen><verb>
+CTAN:languages/babel
+</verb></tscreen>
+
+<sect1>Qu son e&tex;, e&latex; y <em/omega/?
+<!-- ======================================= -->
+<p>
+ e&tex; es una extensin de &tex; con nuevas primitivas y algunas correcciones
+ en el cdigo de &tex; para mejorar (an ms si cabe) sus capacidades
+ tipogrficas. Es slo un paso intermedio para <em/NTS/, que ser el nombre
+ definitivo. e&latex; es una versin de &latex; para e&tex;, que en realidad es
+ exactamente igual en su funcionamiento, slo que los archivos de formato de
+ &tex; y e&tex; no son compatibles.
+<p>
+ <em/omega/ es similar en concepto, aunque distinto en realizacin, ya que
+ utiliza preprocesadores integrados con &tex;. Adems, funciona con
+ <em/unicode/ y permite escribir en cualquier lengua conocida (o por
+ conocer). <em/lambda/ es una versin de &latex; para <em/omega/, y se puede
+ decir lo mismo que sobre e&latex;.
+<p>
+ Ambas son prescindibles si slo quieres usar &tex;; pero ambas son
+ imprescindibles si quieres ir ms all en tipografa.
+
+<sect1>Qu es Rev&tex;?<label id="que-es-revtex">
+<!-- ===================================== -->
+<p>
+ Rev&tex; es un conjunto de macros y estilos en &latex; realizado por la
+ Sociedad Americana de Fsica, la Sociedad Americana de ptica, y el Instituto
+ Americano de Fsica. Sirve para componer artculos y resmenes para muchas
+ revistas de estas sociedades y algunas otras. Las ventajas son las de &latex;
+ (texto en ASCII que puede enviarse por <em/e-mail/ y entre distintas
+ plataformas, archivos reducidos, ms importancia al contenido y la estructura
+ que a la esttica, frmulas matemticas impecables, manejo sofisticado de
+ referencias y citas, etc.) y las de estar especficamente desarrollado para
+ artculos de una revista cientfica. As, es muy fcil preparar <em/preprints/
+ que se asemejan mucho al resultado final y donde es muy fcil calcular el
+ nmero de pginas. Es inmediato preparar separatas en formato PDF.
+<p>
+ Debe procurarse utilizar al menos la versin Rev&tex; 4, ya que Rev&tex; 3.1
+ no es del todo compatible con &latex; (hay que modificar algo las tablas, por
+ ejemplo).
+<p>
+ Se puede encontrar ms informacin en la pgina Web del Instituto Americano de
+ Fsica (en la seccin de publicaciones, programa Compuscript)
+<quote>
+<htmlurl url="http://www.aip.org" name="http://www.aip.org">
+</quote>
+
+
+<sect1>Qu es una <tt/box/ y cundo conviene utilizarlas?
+<label id="que-es-box">
+<!-- ===================================================== -->
+<p>
+ Realmente esta es una pregunta ms especializada. Una <tt/box/ es una forma de
+ guardar informacin para reutilizarla despus. Por ejemplo, se podra guardar
+ un logo con informacin con
+<tscreen><verb>
+\newsavebox{\logo}
+\sbox{\logo}{\includegraphics{logo.eps}}
+</verb></tscreen>
+ y luego utilizarla con <tt>\usebox{\logo}</tt>. La diferencia con usar
+<tscreen><verb>
+\newcommand{\logo}{\includegraphics{logo.eps}}
+</verb></tscreen>
+ y luego poner <tt>\logo</tt> cada vez que se utilice es la siguiente:
+<p>
+ Lo que hay en un <tt/box/ ya est hecho y compuesto. Lo que hay en una macro
+ son ordenes que se ejecutan cuando se usa la macro, y por tanto no se componen
+ hasta ese momento. Cuando es necesario utilizar muchas veces la definicin
+ sale ms rentable usar un <tt/savebox/ ya que el recuadro usado contiene
+ siempre exactamente lo mismo y de esta forma, no se llama a
+ <tt>\includegraphics</tt> en cada pagina, sino tan solo una vez. Sin embargo,
+ una <tt/box/ no admite argumentos como lo hace una macro.
+
+<!-- ********************************************************* -->
+<sect>Cmo hago ...?
+<!-- ********************************************************* -->
+
+<sect1>Cmo y dnde instalo nuevos paquetes o archivos de estilo?<label id="paquetes-instalar">
+<!-- ========================================================================-->
+<p>
+ Este proceso constar en general de los pasos que se describen a continuacin:
+ traer el nuevo paquete, extraer los ficheros de estilo si es necesario,
+ colocarlos en el sitio apropiado y rehacer la base de datos.
+
+<sect2> Dnde buscar un paquete nuevo y qu traer
+<!-- ........................................ -->
+<p>
+ Normalmente los paquetes nuevos se encontrarn en el
+ <ref id="que-es-CTAN" name="CTAN">, aunque en ocasiones estarn en otros
+ lugares. En general, se debe descargar el directorio completo del paquete o el
+ archivo comprimido que lo contiene. Esto no es necesario cuando se quiere
+ descargar un archivo de estilo de uno de los directorios <em/misc/, que tienen
+ contribuciones al <em/CTAN/ en forma de archivos de estilo individuales
+ completos en s mismos. En este caso bastara con descargar el archivo
+ individual correspondiente.
+
+<sect2> Qu es cada uno de los archivos que traigo?
+<!-- ........................................ -->
+<p>
+ Un paquete pequeo puede estar compuesto nicamente de un archivo de estilo
+ <tt/.sty/ (por ejemplo <tt/paquete.sty/) con las instrucciones de uso
+ incluidas como comentarios en el mismo, en un archivo separado o bien en un
+ archivo <em/README/.
+<p>
+ Sin embargo, es ms frecuente encontrar el paquete en forma de un par de
+ archivos <tt/paquete.ins/ y <tt/paquete.dtx/, escritos para ser utilizados con
+ el sistema <em/doc/ de &latex;. Los archivos de estilo deben extraerse de
+ stos. Si hay un <em/README/ adicional debe leerse ste previamente.
+
+<sect2> Extrayendo archivos de estilo de los <tt/.dtx/ y <tt/.ins/<label id="dtx-extraer">
+<!-- .......................................................... -->
+<p>
+ En el sistema <em/doc/ el manual de usuario y el cdigo del paquete
+ documentado se encuentran en el archivo <tt/.dtx/, mientras que el archivo
+ <tt/.ins/ contiene instrucciones &latex; acerca de la extraccin del cdigo
+ del archivo <tt/.dtx/. Para extraer los distintos archivos debe seguirse el
+ siguiente procedimiento:
+ <itemize>
+ <item>
+ Correr &latex; sobre <tt/paquete.ins/. Esto extraer uno o ms archivos
+ (normalmente un <tt/paquete.sty/, pero dependiendo del paquete pueden
+ generarse ms archivos).
+ <item>
+ Correr &latex; sobre <tt/paquete.dtx/ para obtener el manual de usuario y
+ posiblemente una versin comentada del cdigo del paquete.
+ <item>
+ Correr de nuevo &latex; sobre <tt/paquete.dtx/. sto resolver las
+ referencias y generar una tabla de materias si el archivo original lo pide
+ as.
+ <item>
+ Si &latex; da el error <em/"No file paquete.ind"/ significa que no encontr
+ el archivo fuente para el ndice de rdenes. Para generar el ndice basta
+ hacer
+<tscreen><verb>
+makeindex -s ind.ist paquete
+</verb></tscreen>
+ y correr de nuevo &latex;.
+ <item> Imprimir y leer <tt/paquete.dvi/.
+</itemize>
+ A veces se proporciona el manual de usuario separadamente del archivo
+ <tt/.dtx/. En este caso es recomendable procesarlo despus de hacer lo
+ anterior, ya que puede necesitar elementos del paquete que est describiendo.
+
+ <sect2>Dnde colocar nuevos archivos de estilo?
+ <!-- ..................................................... -->
+ <p>
+ En primer lugar &tex; buscar archivos en el directorio
+ actual. Salvo que se trate de una prueba o de archivos muy
+ relacionados con el documento que se est preparando, es conveniente
+ colocarlos en un lugar de acceso ms general.
+ <p>
+ El lugar exacto en el que deben colocarse los nuevos archivos de
+ estilo depende de la distribucin &tex; que se est
+ utilizando. Asumiendo que se utiliza una de las distribuciones
+ modernas que son conformes al TDS (por ejemplo, te&tex;, fp&tex; o
+ mik&tex;) hay una serie de normas que deben tenerse en cuenta
+ <enum>
+ <item>
+ Instalar siempre los nuevos archivos personales en una rama
+ <em/texmf/ local del rbol global o en una rama personal,
+ dependiendo de si son archivos para uso comn en la mquina o
+ nicamente para el usuario. De esta forma puede actualizarse el
+ rbol <em/oficial/ sin tocar los archivos locales o
+ personales. Para la rama local, el directorio raz local tendr
+ un nombre del tipo:
+<tscreen><verb>
+teTeX: /usr/share/texmf.local/
+fpTeX: c:\fptex\texmf.local\
+mikTeX: c:\localtexmf\
+</verb></tscreen>
+ que puede cambiar dependiendo de las opciones dadas durante la
+ instalacin. Por simplicidad en lo que sigue le denominaremos
+ <tt/$TEXMFLOCAL/.
+ <item>
+ En la rama local, reproducir la estructura de directorios de la
+ rama principal. Estos son unos ejemplos de dnde deberan
+ colocarse archivos de distintas extensiones:
+<tscreen><verb>
+.sty, .cls o .fd: $TEXMFLOCAL/tex/latex/<paquete>/
+.dvi, .ps o .pdf: $TEXMFLOCAL/doc/latex/<paquete>/
+.bib: $TEXMFLOCAL/doc/bibtex/bib
+.bst: $TEXMFLOCAL/doc/bibtex/bst
+.tfm: $TEXMFLOCAL/fonts/tfm/<suministrador>/<fuente>/
+.vf: $TEXMFLOCAL/fonts/vf/<suministrador>/<fuente>/
+.afm: $TEXMFLOCAL/fonts/afm/<suministrador>/<fuente>/
+.pfb: $TEXMFLOCAL/fonts/type1/<suministrador>/<fuente>/
+.ttf: $TEXMFLOCAL/fonts/truetype/<suministrador>/<fuente>/
+</verb></tscreen>
+ donde <em/paquete/, <em/fuente/ y <em/suministrador/ dependen de
+ cada archivo individual de cada paquete.
+ <p>
+ La rama personal suele estar en un subdirectorio <tt/texmf/ del
+ directorio de usuario, pero puede cambiar. En ella tambin es
+ necesario reproducir la estructura de directorios de la rama
+ principal. Dependiendo de la distribucin y/o de las opciones de
+ configuracin puede ser necesario rehacer la base de datos
+ cuando se aaden o quitan elementos.
+ </enum>
+
+ <sect2>Activando ramas locales y personales del rbol de directorios &latex; global
+ <!-- ....................................................................... -->
+ <p>
+ A menudo la rama local del rbol global no est activada por omisin
+ y es necesario activarla:
+ <descrip>
+ <tag/<em>te&tex y fp&tex;;</em>/ En primer lugar es necesario
+ localizar el archivo de configuracin <tt/texmf.conf/. ste
+ puede estar en <tt>/etc/texmf/texmf.conf</tt>,
+ <tt>/etc/texmf.conf</tt> o
+ <tt>/usr/share/texmf/web2c/texmf.conf</tt>, dependiendo de la
+ distribucin. Aunque no siempre es necesario, en la primera
+ lnea del archivo borrar la palabra <tt/original/.
+ <p>
+ Jugando adecuadamente con <tt/texmf.cnf/, donde estn los
+ caminos de bsqueda, se configura sin problemas. Para activar
+ una lnea debe quitarse el carcter de comentario % al principio
+ de la lnea, para desactivarla aadir el carcter % al principio
+ de la lnea. Cuando se activa una lnea debe desactivarse la que
+ antes haca esa funcin, si la haba. Por ejemplo, si se tienen
+ los archivos de la distribucin bajo <tt>/usr/share/texmf/</tt>,
+ archivos locales bajo <tt>/usr/share/local.texmf</tt> y archivos
+ personales bajo <tt>~/texmf</tt>, las lneas del <tt/texmf.cnf/
+ que lo haran son
+<tscreen><verb>
+TEXMFMAIN = /usr/share/texmf
+</verb></tscreen>
+ para la rama principal, que viene activada por omisin. Para las
+ ramas local y personal se aadira (o se quitara el comentario
+ de la misma) una lnea del tipo
+<tscreen><verb>
+TEXMFLOCAL = /usr/share/texmf.local
+HOMETEXMF = $HOME/texmf
+</verb></tscreen>
+ que normalmente vienen comentadas. Finalmente se seleccionara
+<tscreen><verb>
+TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}
+</verb></tscreen>
+ que las junta todas. Como se ha dicho antes, en la estructura de
+ las ramas local y personal debe clonarse la estructura de la
+ rama principal y como se dice en la seccin siguiente debe
+ correrse <tt/texhash/ (o <tt/mktexlsr/) despus de hacer los
+ cambios para rehacer la base de datos de archivos. Para la rama
+ personal puede ser necesario rehacer la base de datos como
+ usuario.
+ <p>
+ El fichero de configuracin est extensamente comentado con
+ explicaciones de la funcin de cada una de las posibles lneas.
+ </descrip>
+
+ <sect2>Rehaciendo la base de datos de archivos instalados
+ <!-- ........................................................... -->
+ <p>
+ El paso final consiste en decirle a &latex; que hay una serie de
+ nuevos archivos que debe ser capaz de encontrar. En la mayor parte
+ de los sistemas &latex; libres recientes se mantiene una base de
+ datos de archivos instalados, para posibilitar una bsqueda ms
+ rpida. En estos sistemas es necesario actualizar esta base de datos
+ cada vez que se instalan nuevos archivos, mediante los programas
+ suministrados con este fin en la distribucin.
+ <descrip>
+ <tag/te&tex;, fp&tex;/ Correr
+<tscreen><verb>
+texhash
+</verb></tscreen>
+ <tag/web2c/ En cualquier distribucin <em/web2c/ reciente
+ <tt/texhash/ debiera funcionar. Si no es as, probar con
+<tscreen><verb>
+mktexlsr
+</verb></tscreen>
+ <tag/Mik&tex;/En una distribucin Mik&tex; anterior a la v2.0,
+ hacer con los menes desplegables:
+<tscreen><verb>
+Start-> Programs-> MikTeX-> Maintenance-> Refresh filename database
+</verb></tscreen>
+ o en una ventana DOS
+<tscreen><verb>
+initexmf -update-fndb
+</verb></tscreen>
+ En una distribucin Mik&tex; mayor o igual que la v2.0, hacer
+ con los menes desplegables
+<tscreen><verb>
+Start-> Programs-> MikTeX 2-> MikTeX Options
+</verb></tscreen>
+ y pulsar el botn <em/"Update filename database"/.
+ </descrip>
+
+ <sect2>Cmo verifico los directorios en los que &tex; busca archivos de estilo?
+ <!-- ................................................................ -->
+ <p>
+ La respuesta ms general sera mirando los archivos de
+ configuracin, pero si se trata de un &tex; que utiliza las rutinas
+ <em/kpathsearch/ de Karl Berry, es mucho ms sencillo
+<tscreen><verb>
+% kpsepath tex
+</verb></tscreen>
+ responder con la lista de los directorios en los que busca. Una
+ doble barra (<tt>//</tt>) indica que se busca recursivamente en los
+ subdirectorios del que pone. Es decir, que si los paquetes
+ particulares estn en <tt>~/texmf/tex/latex/lo-que-sea</tt>, o en
+ <tt>~/texmf/tex/mas-paquetes</tt> los encontrar.
+
+<sect1>Cmo personalizo el aspecto del documento?<label id="tex-personalizar">
+<!-- =======================================================================-->
+
+ <sect2>Cmo cambio la fuente de un documento o instalo nuevas?
+ <!-- ...................................................................... -->
+ <p>
+ Pues depende de la fuente que se quiera usar. Normalmente hay paquetes de
+ estilo que lo hacen automticamente. Por ejemplo, si pretendes usar la
+ familia de <em/Times/, usa el paquete <em/times/ poniendo en el prembulo
+ <tt>\usepackage{times}</tt>. Otra familia disponible es <em/lucida-bright/,
+ que puedes cargar con el paquete <em/lucidabr/. Si miras estos archivos
+ (<tt/times.sty/ o <tt/lucidabr.sty/) puedes aprender la forma de usar una
+ fuente, y copiarlo para otros tipos.
+ <p>
+ Hay muchos tipos de letras ya preparados as: <tt/times/, <tt/helvetica/
+ (<tt/arial/ est casi clonado de esta), courier, la letra gtica se
+ llama <tt/oldgerm/, griego...
+ <p>
+ Un segundo paso es ir al <em/CTAN/ para ver si alguien ha preparado un
+ paquete con el tipo deseado.
+ <p>
+ En el peor de los casos en el que no est preparado, puede crearse
+ manualmente un paquete a partir de los tipos originales en formato
+ <em/Type-1/, aunque no es un proceso inmediato. Ms informacin en
+ <tt>CTAN:info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf</tt>.
+
+ <sect2>Puedo utilizar una fuente <em/TrueType/ como <em/Arial/ en &latex;?
+ <!-- ...................................................................... -->
+ <p>
+ A veces se piden tipos de letra que no estn disponibles directamente en
+ &latex; como <em/Arial/. El tipo de letra Arial es <em/TrueType/, y este
+ formato no es soportado directamente por &latex;. Desde pdflatex s es
+ posible usar tipos <em/TrueType/, pero antes hay que crear unos cuantos
+ archivos auxiliares que necesita &tex;. El proceso no es sencillo. Est
+ descrito en
+ <htmlurl url="http://www.radamir.com/tex/ttf-tex.htm"
+ name="http://www.radamir.com/tex/ttf-tex.htm">
+ <p>
+ Recientemente ha aparecido otro documento que explica cmo convertir los
+ tipos <em/TrueType/ en tipos <em/PostScript/, y cmo usar estos tipos
+ convertidos desde <tt/latex->dvips/. El documento se encuentra disponible en
+ <tt>CTAN:info/TrueType/</tt> y est orientado a un sistema tetex, por lo que
+ es posible que no funcione bajo windows/miktex.
+ <p>
+ El tipo de letra <em/helvetica/ es muy parecido al tipo <em/Arial/ y s est
+ disponible bajo &latex;. Basta con aadir en el prembulo del documento
+<tscreen><verb>
+\renewcommand{\rmdefault}{phv}
+\renewcommand{\sfdefault}{phv}
+</verb></tscreen>
+ pero si hay frmulas matemticas stas seguiran utilizando los tipos
+ <em/computer modern/ por lo que quedarn feas en medio del texto en
+ <em/helvetica/.
+
+ <sect2>Incluyendo subdocumentos &tex;/&latex; en el documento
+ <!-- ...................................................................... -->
+ <p>
+ Pueden incluirse subdocumentos &tex;/&latex; en un documento mediante las
+ rdenes <tt/\input/ e <tt/\include/. <tt/\input{otro_documento}/ lo incluir
+ en el lugar en el que se introduce la orden, mientras que
+ <tt/\include{otro_documento}/ siempre abrir una pgina nueva al incluir el
+ documento. Sin embargo, <tt/\include/ permite incluir documentos de forma
+ selectiva mediante la orden <tt/\includeonly/, mientras que <tt/\input/ no
+ lo permite. As, la orden <tt/\includeonly{doca,docc}/ en el prembulo har
+ que se incluyan nicamente los documentos <tt/doca/ y <tt/docc/, a pesar de
+ que tambin <tt/docb/ tenga un <tt/\include/,
+<tscreen><verb>
+...
+\includeonly{doca,docc}
+\begin{document}
+...
+\include{doca}
+\include{docb}
+\include{docc}
+...
+</verb></tscreen>
+
+<sect2>Cmo evito que salga la palabra captulo en las cabeceras de captulo?
+<!-- ...................................................................... -->
+<p>
+ Cuando se usa <em/spanish-babel/ basta con poner en el prembulo, despus de
+ haberse cargado <em/babel/
+<tscreen><verb>
+\addto{\captionsspanish}{\def\chaptername{}}
+</verb></tscreen>
+ y queda eliminada la palabra Captulo. Si no se usa <em/babel/ basta con poner
+ en el prembulo <tt>\def\chaptername{}</tt>. Realmente esto es un caso
+ particular de cambio de literales, que se trata en las secciones <ref
+ id="literales" name="literales"> y <ref id="sectnames" name="Cambio de nombre
+ de secciones">
+
+<sect2>Cmo cambio la cabecera de captulo por otra ms a mi gusto?
+<!-- ...................................................................... -->
+<p>
+Hay dos formas, redefiniendo las rdenes que hacen las cabeceras, o utilizando
+ un paquete hecho que facilite el trabajo. Un paquete que permite
+ hacer cosas muy elaboradas con las cabeceras de los captulos es
+ <em/titlesec/, disponible en
+ <tt>CTAN:macros/latex/contrib/supported/titlesec</tt>
+
+<sect2>Quiero una seccin no numerada, pero que aparezca en la tabla de materias.
+<!-- ...................................................................... -->
+<p>
+ Por ejemplo, suponiendo que se trate de una lista de smbolos,
+<tscreen><verb>
+\section*{Lista de smbolos}
+\addcontentsline{toc}{section}{Lista de smbolos}
+</verb></tscreen>
+Lo mismo para otros elementos (subseccin,...).
+
+<sect2>No me funciona <tt>\subsubsubsection</tt>.
+<!-- ...................................................................... -->
+<p>
+<tt>\subsubsubsection</tt> no existe, en los estilos estndar es
+<tt>\paragraph</tt> quien hace ese papel.
+
+<sect2>Cmo quito los encabezados que &latex; pone automticamente en las pginas blancas?
+<!-- ...................................................................... -->
+<p>
+ Si se quiere controlar cundo se quiere o no este comportamiento en cada
+ pgina con este problema, se puede definir una nueva orden,
+<tscreen><verb>
+\newcommand{\clearemptydoublepage}{\newpage{\pagestyle{empty}\cleardoublepage}}
+</verb></tscreen>
+ y teclear <tt>\clearemptydoublepage</tt> cada vez que quieras continuar el
+ texto en una pagina impar.
+<p>
+ Cuando se quiere que esto ocurra automticamente hay que redefinir la orden
+ <tt>\cleardoublepage</tt> como sugiere la documentacin del paquete
+ <em/fancyhdr/,
+<tscreen><verb>
+\makeatletter
+ \def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else
+ \vspace*{\fill}
+ \thispagestyle{empty}
+ \newpage
+ \if@twocolumn\hbox{}\newpage\fi\fi\fi}
+\makeatother
+</verb></tscreen>
+<!-- \makeatletter
+\def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else
+ \vspace*{\fill}
+ \thispagestyle{empty}
+ \newpage\fi\fi}
+\makeatother -->
+<p>
+ Cuando se utiliza el paquete <em/titlesec/ de Javier Bezos para definir
+ formatos propios de cabeceras y pies de pagina, la opcin de paquete
+ <tt/clearempty/ ya hace el trabajo:
+<tscreen><verb>
+\usepackage[<tus_opciones>,clearempty]{titlesec}
+</verb></tscreen>
+<p>
+Otra posibilidad es utilizar el paquete <em/nextpage/,
+<tscreen><verb>
+\usepackage{nextpage}
+...
+\cleartooddpage[\thispagestyle{empty}]
+\chapter{...}
+</verb></tscreen>
+
+<sect2>Cmo quito los encabezados, pies o la numeracin de las pginas?
+<!-- ............................................-->
+<p>
+ La opcin <tt/\pagestyle{empty}/ quitar los encabezados y pies de todas las
+ pginas posteriores a aqulla en la que se invoca. La opcin
+ <tt/\thispagestyle{empty}/ quitar los encabezados y los pies de pgina en la
+ pgina donde se invoca esta orden.
+<p>
+ Cuando lo que se quiere es eliminar nicamente el nmero de pgina, en general
+ no es conveniente utilizar <tt>\renewcommand{\thepage}{}</tt> porque eso
+ suprime <em/todos/ los nmeros de pgina, incluidos los de los ndices o las
+ remisiones. Por tanto, hay que evitarla siempre que se pueda y optar por
+ soluciones mejor construidas y especficas a cada caso, como utilizar una
+ definicin personal de cabeceras que pueda activarse a voluntad para ciertas
+ pginas.
+
+<sect2>Cmo pongo encabezados o pies de pgina a mi gusto?
+<!-- ............................................-->
+<p>
+La forma ms habitual es utilizar el paquete <em/fancyhdr/. Por ejemplo, con
+pies
+<tscreen><verb>
+\documentclass{book}
+\usepackage{fancyhdr}
+\lfoot{titulo a la izquierda}
+\rfoot{titulo a la derecha}
+\cfoot{titulo al centro}
+\pagestyle{fancy}
+\begin{document}
+\chapter{A title}
+\thispagestyle{fancy} %opcional
+\newpage
+\section{a section}
+\end{document}
+</verb></tscreen>
+pero <em/titlesec/ tambin permite un amplio control del estilo de pgina.
+
+<sect2>Cmo hago que &latex; y &tex; no partan nunca las palabras?
+<!-- ................................................. -->
+<p>
+Para &latex; si se ha cargado el paquete babel basta con la orden
+<!-- \selectlanguage{nohyphenation} -->
+<tscreen><verb>
+\hyphenrules{nohyphenation}
+</verb></tscreen>
+Por supuesto el patrn <tt/nohyphenation/ debe de estar activado en
+<tt/language.dat/ y el formato creado con l (Vanse <ref id="guionado" name="Cmo activo el patrn de particin de palabras para el castellano?"> y <ref id="formatos" name="Cmo rehacer los formatos?">).
+<p>
+Para &tex; hay que hacer las cosas de otra forma. Una forma de conseguir que
+&tex; no corte casi nunca, (y as de paso se evita que corte mal) es poner:
+<tscreen><verb>
+\pretolerance=2000
+\tolerance=3000
+</verb></tscreen>
+al principio. Si se quiere que sto ocurra nicamente en un prrafo o en una
+ regin, debe encerrarse lo anterior y la regin deseada entre
+ llaves,
+<tscreen><verb>
+{\pretolerance=2000
+\tolerance=3000
+el prrafo o regin
+}
+</verb></tscreen>
+sto puede utilizarse tambin para &latex;
+<!--
+<sect1>Cmo hago en mi documento una parte preliminar para prlogo, agradecimientos, etc.?
+<p>
+Cuando se quiere hacer un captulo(s) introductorio a modo de prlogo en un documento (con secciones subsecciones y esas cosas) de forma que no numere los apartados y no introduzca la cabecera <em/captulo/, la forma ms sencilla es utilizar <tt>\chapter*{ttulo_del_captulo}</tt> (y si se quiere incluir en la tabla de materias aadir una lnea <tt>\addcontentsline{toc}{...}</tt>. Sin embargo, hay una forma ms elegante,
+<tscreen><verb>
+\begin{document}
+\frontmatter
+\chapter{Prlogo}
+\mainmatter
+etc.
+</verb></tscreen>
+-->
+
+<sect2> Cmo ajusto los mrgenes de un documento &latex;?
+<!-- ............................................ -->
+<p>
+Quizs la forma ms cmoda sea utilizar el paquete <em/geometry/, que se
+ encuentra disponible en
+ <tt>CTAN:macros/latex/contrib/supported/geometry</tt>. Por ejemplo
+<tscreen><verb>
+\documentclass[a4paper, 10pt]{article}
+\usepackage[a4paper,left=3cm,right=2cm]{geometry}
+</verb></tscreen>
+crea una pgina A4 con margen de 3cm a la izquierda y 2cm a la derecha, sin ms
+ complicaciones.
+<p>
+Otra cosa mucho ms complicada es cmo cambiar los mrgenes dentro de un
+ documento, en vez de hacerlo en el prembulo como lo hace el paquete
+ <em/geometry/. Un caso especial se tiene cuando se quiere alargar un
+ poco una pgina para que quepa un poco ms de texto y as evitar
+ situaciones poco estticas. Para sto, &latexe; proporciona la orden
+ <tt>\enlargethispage{distancia}</tt> donde se aumenta el tamao
+ vertical de la pgina en la distancia especificada.
+<p>
+A pesar de esa dificultad, puede utilizarse el paquete <em/chngpage/, que
+ proporciona rdenes para cambiar el aspecto de la pgina en
+ el medio de un documento (por ejemplo, hacerla ms estrecha
+ o ms ancha, ms corta o ms larga, e incluso desplazarla
+ horizontal o verticalmente), aunque no permite cambios
+ dentro de un prrafo.
+
+<sect2>Cmo obtengo un documento apaisado?
+<!-- ..................................... -->
+<p>
+ Cuando se quiere sacar la totalidad del documento apaisada, hay que decirle a
+ &tex; que las dimensiones horizontal y vertical estn cambiadas, comenzando el
+ documento con la opcin <tt/landscape/, algo del tipo
+<tscreen><verb>
+\documentclass[landscape,a4]{article}
+</verb></tscreen>
+ donde la clase de documento puede ser tambin cualquier otra como
+ <tt/slides/. Esto intercambia las distancias horizontal y vertical, pero no
+ rota el documento final para que se ajuste a la posicin de la hoja. Para ello
+ se puede utilizar el <em/dvips/, por ejemplo en la forma siguiente
+<tscreen><verb>
+dvips -ta4 -tlandscape tu_archivo -o tu_archivo.ps
+</verb></tscreen>
+ donde <tt/-tlandscape/ gira la salida. La opcin <tt/-ta4/ es a menudo
+ conveniente si se utiliza papel <em/a4/, para que el giro se haga de forma
+ adecuada.
+
+<sect2>Cmo ajusto el espaciado en el documento &latex;?
+<!-- ................................................ -->
+<p>
+ Para ajustar el espaciado entre lneas en un documento &latexe; se recomienda
+ utilizar el paquete <em/setspace/, que se cargar en el prembulo. Las rdenes
+ <tt/\singlespacing/, <tt/\onehalfspacing/, y <tt/\doublespacing/ colocadas en
+ el prembulo establecen el espaciado global del documento. Pueden establecerse
+ valores intermedios mediante la orden <tt/\setstretch{baselinestretch}/ en el
+ prembulo. El valor por omisin es espaciado simple. Asimismo se definen tres
+ entornos con los mismos nombres que las rdenes anteriores para cambios del
+ espaciado en regiones del documento (respecto del espaciado estndar en ese
+ momento, doublespacing empezar un entorno de espaciado doble que el espaciado
+ en ese momento, si es doble lo har an mayor).
+<p>
+ Para un documento &latex;209 puede utilizarse el paquete <em/doublespace/.
+<p>
+ La forma ms cmoda de controlar el espaciado entre prrafos es mediante el
+ paquete <em/parskip/.
+
+<sect1>Listas al gusto de cada cual.
+<!-- ================================================================ -->
+<sect2>Cmo ajusto el espaciado en una lista?
+<!-- ..................................... -->
+<p>
+ La distancia entre los elementos es la suma de los valores de <tt>\parsep</tt>
+ (que es tambin la distancia entre prrafos dentro de un mismo
+ elemento) e <tt>\itemsep</tt>. Si slo se quiere cambiar la distancia
+ entre elementos pero no entre prrafos de un mismo elemento, basta con
+ dar un nuevo valor a la distancia <tt>\itemsep</tt>.
+<p>
+ Es un espacio elstico, es decir, adems de con
+ <tt>\setlength{\itemsep}{1cm}</tt> se puede definir con algo como
+<tscreen><verb>
+\itemsep= 4pt plus 2pt minus 1pt
+</verb></tscreen>
+ donde 4pt sera el espacio <em/normal/, 2pt lo mximo que podra estirarse y 1pt
+ lo mximo que podra encogerse.
+
+ El valor de <tt>\itemsep</tt> se restablece con cada <tt>\begin{itemize}</tt>
+ (o la lista de que se trate), y se hace igual a <tt>\parsep</tt>, por lo que
+ hay que modificarlo <em/dentro/ de la lista, por ejemplo.
+<tscreen><verb>
+{\topsep=-15pt \parsep=-15pt \partopsep=-15pt
+ \begin{enumerate}\itemsep=-5pt
+ \item{ Pruebas de interespaciado}
+ \item{ Pruebas de interpaginado}
+ \item{ Pruebas de espaciado}
+ \end{enumerate}}
+</verb></tscreen>
+ Puede hacerse que la separacin sea nula, mediante
+ <tt>\setlength{\itemsep}{-\parsep}</tt>
+
+ Hacer el cambio para todas las listas es algo ms complejo, pero una forma de
+ hacerlo sera redefinir <tt>\itemize</tt> (y lo mismo para las dems listas)
+ en la forma
+<tscreen><verb>
+\let\olditemize\itemize
+\def\itemize{\olditemize\itemsep=0pt }
+</verb></tscreen>
+ donde en este caso se ha puesto un valor de 0pt a <tt>\itemsep</tt> en todas
+ las listas enumeradas.
+
+<sect2>Cmo cambio el tipo de numeracin en las listas numeradas?
+<!-- ..................................... -->
+<p>
+Por ejemplo, para que escriba los elementos de primer nivel con nmeros como 1 y
+los de segundo nivel con nmeros en la forma 1.1
+<tscreen><verb>
+\renewcommand{\theenumii}{\arabic{enumii}}
+\renewcommand{\labelenumii}{\theenumi .\theenumii .}
+</verb></tscreen>
+Si algn paquete que ests usando redefine los <tt/\theenum/, como el
+<em/babel-spanish,/ entonces debes asegurate que &latex; eliga tus parametros
+colocando las rdenes anteriores entre:
+<tscreen><verb>
+\AtBeginDocument{%
+comandos aqui..
+}
+</verb></tscreen>
+
+<sect2>Quiero mostrar un smbolo distinto en las listas <em/itemize/
+<!-- ..................................... -->
+<p>
+ Dentro de un <em/itemize/, puede especificarse en cada <tt/\item/ un parmetro
+ opcional, que es el smbolo que se mostrar (en lugar del topo por defecto),
+ por ejemplo, <tt/\item[$\odot$]/, y si se quieren cambiar todos, con el mismo
+ ejemplo,
+<tscreen><verb>
+\renewcommand{\item}{\item[$\odot$]}
+</verb></tscreen>
+o, mediante el paquete <em/paralist/,
+<tscreen><verb>
+\usepackage{paralist}
+...
+\begin{itemize}[$\star$]
+\item ...
+\item ...
+\end{itemize}
+</verb></tscreen>
+<p>
+Tambin puede utilizarse el paquete <em/pifont/, as:
+<tscreen><verb>
+\usepackage{pifont}
+\begin{Pilist}{pzd}{248}
+\item bla
+\item bla bla
+\item bla
+\end{Pilist}
+</verb></tscreen>
+
+El entorno <em/Pilist/ es anlogo a <em/itemize/, pero en lugar del <em/bullet/
+usa el caracter que se le pida de la fuente que se le pida. En el ejemplo
+anterior, se usa el carcter con cdigo 248 de la fuente <em/pzd/ que tiene gran
+cantidad de simbolos adecuados para <em/itemize/.
+
+<sect2>Puedo ajustar la separacin entre texto y listas?
+<!-- ..................................... -->
+<p>
+Con el paquete <em/enumitem/, en <tt>CTAN:macros/latex/contrib/bezos/</tt>.
+
+<sect2>Cmo interrumpir una lista numerada con un comentario y continuar
+despus con la numeracin correcta?
+<!-- ..................................... -->
+<p>
+Entre las <em/mdwtools/ hay un paquete llamado <em/mdwlist/ que permite hacer
+eso:
+<tscreen><verb>
+ \begin{enumerate}
+ \item ...
+ \item ...
+ \suspend{enumerate}
+Texto...
+ \resume{enumerate}
+ \item ...
+ \item ...
+ \end{enumerate}
+</verb></tscreen>
+Disponible en <tt>CTAN:macros/latex/contrib/supported/mdwtools/</tt>
+
+<sect2>Puedo hacer listas en paralelo?
+<!-- ..................................... -->
+<p>
+Para crear listas numeradas o por elementos de la forma
+<tscreen><verb>
+1. Primer elemento 2. Segundo elemento 3. Tercer elemento
+4. Cuarto elemento 5. Quinto elemento 6. Sexto elemento
+</verb></tscreen>
+puede utilizarse el paquete <em/paralist/ (disponible en
+<tt>CTAN:macros/latex/contrib/supported/paralist</tt>) o bien el paquete
+<em/multicol/. Tambin existe el paquete <em/multienumerate/
+(<tt>CTAN:macros/latex/contrib/supported/multenum</tt>) y el entorno
+<tt/shortenumerate/ del paquete <em/shortlst/
+(<tt>CTAN:macros/latex/contrib/supported/shortlst</tt>) destinado a listas de
+elementos cortos.
+
+<sect1>Referencias cruzadas, ndices, bibliografas y tablas de materias.
+<!-- ================================================================ -->
+<sect2>Hay alguna herramienta de gestin de bases de datos bibliogrficas en <em/Bib&tex;/?
+<!-- ............................................................ -->
+<p>
+S, existen varias, por ejemplo
+<descrip>
+ <tag/bibtex.el/
+ Modo <em/Bib&tex;/ para <em/emacs/. Normalmente viene
+ incluido con <em/emacs/, pero tambin se puede obtener de su pgina principal
+ <htmlurl url="http://www.ida.ing.tu-bs.de/people/dirk/bibtex/"
+ name="http://www.ida.ing.tu-bs.de/people/dirk/bibtex/">
+ <tag/Winbibdb y bibdb/
+ ambos excelentes y disponibles en
+ <tt>CTAN:support/bibdb</tt> con su pgina base en
+ <htmlurl url="http://www.mackichan.com/BibDB/default.htm"
+ name="http://www.mackichan.com/BibDB/default.htm">
+ <tag/bibtool/
+ disponible en <tt>CTAN:bibtex/utils/bibtool/</tt> con su
+ pgina principal en
+ <htmlurl url="http://bibtool.sourceforge.net/"
+ name="http://bibtool.sourceforge.net/">
+ <tag/jabref/
+ <htmlurl url="http://jabref.sourceforge.net/"
+ name="http://jabref.sourceforge.net/"> es una interfaz grfica
+ escrita en java para manejar bases de datos bibliogrficas.
+ Necesita Java >= 1.4.2
+<!--
+ <tag/pybliographer/
+ <htmlurl url="http://www.pybliographer.org/" name="http://www.pybliographer.org/">
+ <tag/gbib/
+-->
+<!-- <tag/Bibibamos/, que tiene la posibilidad de exportar <em/Bib&tex;/,
+ disponible en
+ <htmlurl url="http://www.edu.uni-klu.ac.at/~cschiest/products/bibibamos/"
+ name="http://www.edu.uni-klu.ac.at/~cschiest/products/bibibamos/">
+ -->
+</descrip>
+
+<sect2>Cmo introduzco la bibliografa o el ndice en la tabla de materias?
+<!-- ............................................................ -->
+<p>
+La forma ms cmoda es utilizar el paquete <em/tocbibind/, que se encuentra
+ disponible en
+ <tt>CTAN:macros/latex/contrib/supported/tocbibind</tt> y en la
+ mayor parte de las distribuciones, pero tambin puede hacerse
+ a mano con por ejemplo
+ <tt>\addcontentsline{toc}{chapter}{\bibname}</tt> en la
+ definicin correspondiente.
+
+<sect2>Cmo pongo el ndice con su contenido al principio de cada captulo?
+<!-- ............................................................ -->
+<p>
+Con el paquete <em/minitoc/
+
+<sect2>Cmo aado bibliografa al final de cada captulo en &latex;?
+<!-- ............................................................ -->
+<p>
+Puede hacerse usando el paquete <em/chapterbib/. Para hacerlo de esta
+ forma debe estructurarse el documento en un archivo raz
+ desde el que se incluyen las distintas secciones que estn
+ en archivos separados del raz, incluir al final de cada uno
+ de stos las rdenes de bibliografa y procesar con
+ <em/bibtex/ los .aux de cada una de estas partes. Si adems
+ se quiere que no haya un salto de pgina al comenzar la
+ bibliografa en cada captulo, debe utilizarse la opcin
+ <tt/sectionbib/.
+<p>
+ Otro paquete que permite una cosa similar es <em/bibunits/
+
+<sect2>Cmo divido la bibliografa por temas en &latex;?
+<!-- ....................................................... -->
+<p>
+ Los paquetes <em/multibib/ y <em/bibtopic/ permiten dividir una bibliografa
+ global en partes separadas para los distintos temas. El primero requiere el
+ uso de rdenes especficas para las citas bibliogrficas, mientras que el
+ segundo requiere dividir el archivo de bibliografa.
+
+<sect2>Cmo cito una pgina de una referencia bibliogrfica?
+<!-- ............................................................ -->
+<p>
+Mediante algo del tipo
+<tscreen><verb>
+\cite[pg.~29]{gar98}
+</verb></tscreen>
+donde <tt/gar98/ sera la etiqueta <em/Bib&tex;/ para la cita deseada.
+
+<sect2>Cmo cito una <tt/url/ con <em/Bib&tex;/?
+<!-- ....................................................... -->
+<p>
+ En los estilos bibliogrficos estndar de <em/Bib&tex;/ no hay un tipo para
+ las <tt/url/, aunque es posible que en una futura versin de <em/Bib&tex;/ s
+ lo haya.
+
+ En tanto esa versin aparece la forma ms sencilla consiste en utilizar el
+ campo <em/howpublished/ del tipo <em/misc/. Una entrada de ese tipo tendra la
+ forma
+<tscreen><verb>
+ @misc{...,
+ ...,
+ howpublished = "\url{http://...}"
+ }
+</verb></tscreen>
+ Tambin puede ocurrir que un artculo, informe o incluso libro se encuentre
+ disponible tambin en la <em/web/. En este caso se podra hacer algo del tipo
+<tscreen><verb>
+ @techreport{...,
+ ...,
+ note = "Tambin disponible como \url{http://...}"
+ }
+</verb></tscreen>
+ donde se supone que se ha utilizado el paquete <em/url/, disponible en
+ <tt>CTAN:macros/latex/contrib/other/misc/url.sty/</tt>, lo que es muy
+ recomendable para estas referencias por diversas razones.
+
+<sect2>Cmo colapso una serie de citas consecutivas?
+<!-- ............................................................ -->
+<p>
+ O cmo puedo hacer que aparezca una citacin bibliogrfica mltiple
+ consecutiva, por ejemplo, [1,2,3,4,5] como [1-5]? El paquete <em/cite/,
+ disponible en <tt>CTAN:macros/latex/contrib/supported/cite</tt> y en
+ <em/te&tex;/ permite hacer precisamente eso.
+
+<sect2>Cmo hago una referencia cruzada a un documento externo?
+<!-- ....................................................... -->
+<p>
+ Para hacer referencias cruzadas entre documentos se puede usar el paquete
+ <em/xr/, de David Carlisle, disponible en las distribuciones habituales y en
+ <tt>CTAN:macros/latex209/contrib/misc/xr.sty</tt>. Su uso es como sigue,
+<tscreen><verb>
+...
+\usepackage{xr} %Referencias a otros documentos
+...
+\externaldocument{miotrodocumento}
+...
+</verb></tscreen>
+ Una vez hecho esto las referencias se declaran como si de un nico documento
+ se tratase.
+
+<sect2> Afinando el aspecto de la tabla de materias o listas de figuras y tablas.
+<!-- ....................................................... -->
+<p>
+ <descrip>
+ <tag/Cmo controlar hasta qu nivel se incluye un elemento en la tabla de materias?/
+ En general, con
+<tscreen><verb>
+\setcounter{tocdepth}{X}
+</verb></tscreen>
+ en el prembulo se controla hasta que nivel se incluir en el ndice
+ general, siendo <tt/X/ un nmero. Con 3 se incluye hasta
+ <tt>\subsubsection</tt>, con 2 hasta <tt>\subsection</tt>. sto permite
+ cambiar el valor definido por omisin en el estilo utilizado.
+ <!-- ***-->
+ <tag/El ttulo del captulo, figura o tabla se solapa con su nmero si ste
+ tiene muchos dgitos/
+ Para las listas de figuras y tablas la separacin se define en <tt/\l@figure}/ o
+ <tt/\l@table/, por ejemplo <em/book.cls/ lo hace as para las figuras
+<tscreen><verb>
+\newcommand*\l@figure{\@dottedtocline{1}{1.5em}{2.3em}}
+</verb></tscreen>
+ En un estilo o en el prembulo entre <tt>makeatletter/makeatother</tt>
+ pueden redefinirse sus valores cambiando el ltimo nmero. Por ejemplo, en
+ el prembulo
+<tscreen><verb>
+\makeatletter
+\renewcommand*{\l@figure}{\@dottedtocline{1}{1.5em}{3.3em}}
+\renewcommand*{\l@table}{\@dottedtocline{1}{1.5em}{2.8em}}
+\makeatother
+</verb></tscreen>
+ Para las entradas de la tabla de materias sera necesario cambiar los
+ valores de <tt/\l@section/, <tt/\l@subsection/, <tt/\l@subsubsection/,
+ <tt/\l@paragraph/ o <tt/\l@subparagraph/ de una forma anloga. Para los
+ captulos la cosa es ms problemtica porque se cambian ms cosas.
+ </descrip>
+
+ El paquete <em/tocloft/ permite controlar detalles del diseo tipogrfico de
+ las tablas de materias y de las listas de figuras y tablas, aunque su
+ internacin con otros paquetes como <em/titlesec/ no est suficientemente
+ probada.
+
+<sect1>Cmo introduzco dibujos, diagramas e imgenes en &latex;?<label id="tex-dibujos">
+<!-- ===========================================================-->
+<p>
+ Hay dos formas de dibujar en &tex;, mediante el uso de funciones primitivas
+ &tex; bien directamente (muy duro) o a travs de alguno de los paquetes de ms
+ alto nivel que proveen de funciones que internamente utilizan esas primitivas,
+ pero que a un usuario se le representan como funciones de dibujo normales en
+ un cierto lenguaje, o bien incluyendo grficos realizados mediante
+ aplicaciones externas, como es el caso de grficos en <em/postscript
+ encapsulado/ o en mapa de bits.
+<p>
+ El problema en este segundo caso es que los datos del grfico deben darse en
+ el documento mediante rdenes <tt/\special/ -- Vase <ref id="special"
+ name="Qu son los \special"> -- y que stas rdenes son en general distintas
+ para los distintos conversores (drivers) a los formatos de impresin o
+ visualizacin. Para evitar al usuario tener que utilizar directamente los
+ <tt/\special/ se pueden utilizar paquetes de ms alto nivel que, dependiendo
+ de los conversores transforman sus rdenes a los <tt/\special/
+ correspondientes. Si se quiere obtener el resultado final en <em/pdf/ hay una
+ serie de limitaciones que hay que tener en cuenta, vase <ref id="tex-a-PDF"
+ name="Cmo obtengo un documento PDF a partir de mi documento &tex;?">
+<p>
+ Para ello se puede utilizar el paquete <em/graphics/, que est entre los
+ paquetes adicionales del &latexe; (disponible en
+ <tt>CTAN:macros/latex/required/graphics/</tt>). Dependiendo de las opciones
+ deseadas se le llama como <tt/graphics/ (menos potente) o <tt/graphicx/ (ms
+ potente y recomendado). Un paquete ms antiguo es <em/psfig/ que en la
+ prctica ha sido sustituido en &latexe; por <em/graphics/ que es el paquete
+ oficial de introduccin de grficos externos en &latexe;. Sin embargo, si se
+ usa &latex; 209 ser necesario usar <em/psfig/ (disponible en
+ <tt>CTAN:graphics/psfig</tt>)
+<p>
+ Tambin es necesario tener un conversor de DVI al lenguaje de impresora que
+ soporte esos <tt/\special/, lo que limita los formatos grficos soportados. En
+ particular es especialmente interesante que soporten el formato <tt/.eps/
+ (postscript encapsulado), lo que hacen el <em/dvips/ y los conversores que
+ vienen con <em/Oz&tex;/ o <em/&tex;tures/. La mayor parte de los
+ visualizadores de DVI no mostrarn correctamente estas figuras, sino slo su
+ espacio. En cualquier caso, es conveniente leer primero la documentacin del
+ paquete <em/graphics/ o alguna de las referencias que se dan a continuacin.
+<p>
+ Existe en el <tt/CTAN/ documentacin muy interesante acerca de este tema. El
+ documento de Anik K. Goel (<tt>CTAN:info/figsinltx.ps</tt>) trata de
+ diferentes formas de generar figuras y de incluirlas con <em/psfig/ para
+ &latex; 209. El documento de Keith Reckdahl (<tt>CTAN:info/epslatex.pdf</tt>)
+ est ms dirigido al trabajo en &latexe; y a las figuras <tt/.eps/. Una
+ referencia excelente sobre el tema es el <em/&latex; Graphics Companion/, de
+ M. Goossens, S. Rahtz y F. Mittelbach, vase la seccin <ref id="libros-int"
+ name="Libros en otros idiomas">.
+
+<sect2>Dibujando con &tex;
+<!-- ................. -->
+<p>
+ Existen una serie de formas de dibujar con &tex; en vez de importar archivos
+ externos. Desde el simple uso del entorno <em/picture/, incluso con mejoras
+ como las proporcionadas por <em/epic/ a dibujos sofisticados (aunque lentos)
+ con las macros <em/Pic&tex;/. Dependiendo de lo que se quiere hacer alguno de
+ los siguientes sistemas puede ser el ms til:
+ <descrip>
+ <tag/pstricks/
+ Disponible en <tt>CTAN:graphics/pstricks</tt>, que da acceso a la potencia
+ de postscript desde &tex; mediante un uso sofisticado de los
+ <tt/\special/. Necesita un conversor a postscript bueno (como
+ p.ej. <em/dvips/), est bien documentado y da buenos resultados.
+
+ <tag/pgf/
+ <em/pgf/ (<em/portable graphics format/) es un paquete de macros &tex; para
+ crear dibujos. Su uso recuerda a <em/pstricks/ y, aunque es menos potente
+ que ste, tiene la ventaja de que es compatible tanto con dvips como con
+ <em/pdf&tex;/.
+ <!-- Tiene <tt/tikz/, un -->
+
+ <tag/MetaPost/
+ Toda la potencia de METAFONT, pero generando figuras postscript en vez de
+ tipos. Para ms informacin en castellano sobre <em/metapost/ puede
+ consultarse la pgina
+ <htmlurl url="http://w3.mecanica.upm.es/metapost"
+ name="http://w3.mecanica.upm.es/metapost">
+ y para ver algunos ejemplos de lo que se puede hacer con <em/metapost/,
+ pueden seguirse los enlaces citados en
+ <htmlurl url="http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html"
+ name="http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html">.
+
+ A partir de la versin 3.7.1 del paquete grfico <em/gnuplot/ ste ya
+ permite exportar sus resultados en formato <em/metapost/. <em/gnuplot/ est
+ disponible en <tt>CTAN:graphics/gnuplot</tt>.
+ <p>
+ <em/pdf&latex;/ tambin trata <em/metapost/ nativamente mediante el uso
+ de <tt>\convertMPtoPDF</tt>. La sintaxis es
+<tscreen><verb>
+\convertMPtoPDF {nombre} {escala x} {escala y}
+</verb></tscreen>
+ Si el nombre del grfico incluido tiene la extensin <tt/.mps/
+ <tt/\includegraphics/ llama internamente a esta orden de forma
+ transparente al usuario y no es necesario incluirla de forma explcita.
+ <p>
+ El grfico MP as incluido se puede manipular sin problema con los
+ comandos habituales de graphicx: rotatebox, resizebox, scalebox, etc...
+ <p>
+ Los archivos <em/metapost/ pueden editarse con un editor de texto y
+ conocimiento del lenguaje <em/metapost/, pero tambin est disponible el
+ editor grfico <em/Metagraf/ para METAPOST, que se encuentra en fase
+ avanzada de desarrollo. Est escrito en <em/Java/ y por tanto funciona
+ bajo distintos sistemas operativos. Se encuentra disponible en la misma
+ pgina anterior,
+ <htmlurl url="http://w3.mecanica.upm.es/metapost" name="
+ http://w3.mecanica.upm.es/metapost">.
+ <p>
+ El programa <em/pstoedit/ permite pasar de postscript a otros formatos
+ editables, entre ellos <em/metapost/, aunque es posible que en el cambio
+ se pierdan elementos del dibujo original.
+ <tag/MfPic/
+ Disponible en <tt>CTAN:graphics/mfpic</tt>. Este paquete genera cdigo
+ METAFONT a partir de macros &tex; como las habituales. No da toda la
+ potencia de METAFONT, pero es bastante ms cmodo.
+
+ <tag/dra&tex;/
+ de Eitan Gurari. Disponible en <tt>CTAN:macros/generic</tt>. Un paquete de
+ macros del tipo de <em/Pic&tex;/, pero mucho ms manejable y menos
+ necesitado de recursos de ordenador.
+</descrip>
+
+<sect2>Introduciendo figuras postscript encapsulado en &latex;
+<!-- ........................................... -->
+<p>
+Un ejemplo de documento en el que se incluye una figura <em/postscript/ externa
+ utilizando el paquete <em/graphicx/ sera (se supone que se utiliza
+ el conversor <em/dvips/)
+<tscreen><verb>
+...
+
+\usepackage[dvips]{graphicx}
+
+...
+
+\begin{figure}
+ \centering
+ \includegraphics[width=10cm]{imagen.eps}
+ \caption{Esto es una imagen}
+ \label{fig:prueba}
+\end{figure}
+
+...
+</verb></tscreen>
+que incluira la figura <tt/imagen.eps/ con una anchura de 10cm. Ntese que el
+que &latex; haya procesado sin problemas no implica que se vaya a ver con el
+visualizador ni que se vaya a imprimir a una impresora, ya que para ello los
+conversores correspondientes deben saber cmo hacerlo (P.ej., <em/dvips/ sabe
+como incluir figuras <em/postscript/ y si se ha compilado con esa opcin algunos
+tipos de mapas de bits). Asimismo es conveniente usar <tt/\centering/ en vez del
+entorno <tt/center/, ya que este ltimo no es para centrar texto, sino para
+componer un poco aparte texto centrado, con blancos antes y despus. Si se usa
+center en un figure habr algo de espacio adicional que no debera estar
+ah. Adems,<tt/\centering/ se puede usar tambin como entorno, si fuera
+necesario <tt/(\begin{centering}/ <tt/.../ <tt/\end{centering})/. Si se desea
+cambiar la separacin con <tt/centering/ pueden cambiarse <tt/\textfloatsep/
+(para b y t) e <tt/\intextsep/ (para h) con <tt/\setlength/.
+
+Para contener el gasto en espacio de disco que supone usar PostScript, el
+ paquete <em/graphicx/ permite que las figuras que se van a incluir
+ estn comprimidas con <em/gzip/, puesto que entiende los sufijos
+ <tt/.eps.gz/ y <tt/.ps.gz/. Para que &latex; sepa el tamao de la
+ figura que est en el archivo, debe existir otro con extensin
+ <tt/.eps.bb/ o <tt/.ps.bb/ con la <em/Bounding Box/ (medidas de la
+ caja) de la figura en PostScript, que se puede obtener de ese mismo
+ archivo (es una de las primeras lneas) o usando algn programa como
+ <em/psbb/, distribuido con las utilidades <tt/groff/ de GNU
+ (<htmlurl url="http://www.gnu.org" name="http://www.gnu.org">).
+
+<sect2>Introduciendo imgenes en mapa de bits en &latex;.
+<!-- ................................................ -->
+<p>
+ En este caso la lnea del <tt/\includegraphics.../ anterior se convertira en
+<tscreen><verb>
+\includegraphics[0,0][101mm,50mm]{figura.pcx}
+</verb></tscreen>
+ donde suponemos que el conversor soporta este formato. Se le ha dicho
+ especficamente el tamao de la figura, ya que si no fuera as, se obtendran
+ distintos resultados al imprimirla en impresoras de distinta resolucin.
+
+<sect2>Inclusin de una imagen desde un PDF con mltiples pginas.
+<!-- ................................................ -->
+<p>
+ Puede hacerse con el paquete <em/graphicx/
+<tscreen><verb>
+\includegraphics[page=6]{archivo}
+</verb></tscreen>
+ o con el paquete <em/pdfpages/,
+<tscreen><verb>
+\usepackage{pdfpages}
+...
+\begin{document}
+\includepdf[pages={3-7,9}]{/path/to/other.pdf}
+\end{document}
+</verb></tscreen>
+
+<sect2>Introduciendo cdigo y figuras postscript en <em/pdf&tex;/
+<label id="pdftex-dibujos">
+<!-- ........................................... -->
+<p>
+ <em/PDF&tex;/ -- vase la pregunta <ref id="tex-a-PDF" name="Cmo obtengo un
+ documento PDF a partir de mi documento &tex;?"> -- no permite la inclusin
+ directa ni de cdigo ni de figuras PostScript. Pueden incluirse figuras en
+ <em/PDF&tex;/ siempre que stas estn en alguno de los formatos <em/JPEG/,
+ <em/PDF/ <em/PNG/ (Vanse en el prrafo siguiente las extensiones por
+ omisin que se esperan para cada formato). Parece que el soporte para formato
+ <em/TIFF/ se ha eliminado a partir de la versin 1.10a de <em/pdf&tex;/, por
+ lo que aunque se vuelva a poner es preferible utilizar alguno de los formatos
+ anteriores. Existen utilidades para convertir de PostScript encapsulado a
+ <em/PDF/ y <em/PNG/ (<em/Distiller/ de Adobe (<htmlurl
+ url="http://www.adobe.com" name="http://www.adobe.com">) para <em/PDF/ y
+ <em/ghostscript/ -- <em/gs/ -- (<htmlurl
+ url="http://www.cs.wisc.edu/~ghost/index.html"
+ name="http://www.cs.wisc.edu/~ghost/index.html">) para convertir a <em/PDF/ o
+ a <em/PNG/). Para este ltimo se tienen dos programas que lo utilizan y hacen
+ de intermediario con el usuario, <em/ps2pdf/, incluido en <em/ghostscript/ y
+ <em/epstopdf/ (disponible en
+ <tt>CTAN:usergrps/uktug/baskerville/epstopdf</tt>, e incluido al menos en
+ <em/te&tex;/) para conversin directa entre los formatos <tt/.eps/ y <tt/.pdf/
+<p>
+ Aunque no de forma directa, el paquete <em/tex4pdf/, disponible en
+ <tt>CTAN:macros/latex/contrib/ps2pdf</tt> permite incluir figuras y cdigo
+ postscript (figuras pstricks y eps, cadenas psfrag, reescalados postscript) en
+ un documento procesado con pdflatex, pero necesita versiones recientes de los
+ paquetes <em/preview/, <em/ifpdf/ e <em/ifvtex/ y del sistema &tex;/&latex;,
+ as como adaptar el documento &latex; para su uso. Tambin pueden utilizarse,
+ con mejor o peor fortuna otros mecanismos (Vase <ref id="tex-a-PDF"
+ name="Cmo obtengo un documento PDF a partir de mi documento &tex;?">)
+<p>
+ Para incluir una figura en <em/PDF&tex;/ se deben seguir los mismos pasos que
+ para incluir una figura PostScript encapsulado en &latex;. Cuando la figura
+ se tiene en dos formatos distintos, uno para pdf&latex; y otro para
+ &latex;/dvips, es recomendable omitir la extensin del archivo (<tt/.ps/,
+ <tt/.eps/, <tt/.ps.gz/, <tt/.eps.gz/ para PostScript y <tt/.jpg/, <tt/.tif/,
+ <tt/.pdf/, o <tt/.png/ para <em/PDF&tex;/). De esta forma el paquete
+ <em/graphicx/ tomar el archivo adecuado segn se est usando &latex; o
+ PDF&latex;.
+
+<sect2>Cmo coloco un fragmento TeX en una figura?
+<!-- ........................................... -->
+<p>
+Esencialmente hay dos formas, mediante los paquetes <em/psfrag/ y
+<em/overpic/,
+<descrip>
+ <tag/psfrag/ permite sustituir cadenas de texto en el grfico postscript por
+ cadenas de texto &tex;. Para ello la cadena de texto a sustituir
+ debe estar en el archivo postscript de forma explcita
+ utilizando alguno de los tipos postscript en vez de dibujada
+ mediante lneas. Es decir, en el archivo postscript debe
+ aparecer <em/(cadena)/ donde cadena es la cadena de texto a
+ sustituir. Esta cadena debe estar compuesta preferentemente de
+ caracteres los alfanumricos a-zA-Z0-9, aunque puede funcionar
+ en algunos otros casos. Para usarlo se cargara el paquete en el
+ prembulo:
+<tscreen><verb>
+\usepackage{psfrag}
+</verb></tscreen>
+ y dentro de un begin-end que englobe la figura o utilizando llaves (para que
+ su efecto no se extienda a otras figuras salvo que se quiera) se incluira
+<tscreen><verb>
+\psfrag{cadena_original}{cadena_sustituta}
+</verb></tscreen>
+ por cada una de las cadenas a sustituir.
+ <p>
+ Este sistema NO funciona directamente con pdf&latex; salvo que se utilice
+ <em/vtex/. Vase <ref id="tex-a-PDF" name="Cmo obtengo un documento PDF a
+ partir de mi documento &tex;?">. Del mismo modo, las cadenas sustituidas no se ven
+ correctamente en los visores de dvi habituales, sino slo cuando se ha pasado
+ a postscript. Puede hacerse funcionar con pdf&latex; de forma indirecta
+ mediante el paquete <em/ps4pdf/ o programas como <em/tex2pdf/.
+
+ <tag/overpic/ El paquete <em/overpic/ permite colocar cualquier tipo de texto
+ sobre una figura e incluso figuras sobre figuras. Tiene dos formas de
+ introducir las coordenadas, absolutas en % de la figura original, y
+ relativas, en % de la figura reescalada. Asimismo cuenta con una excelente
+ documentacin.
+<tscreen><verb>
+\usepackage{overpic}
+</verb></tscreen>
+</descrip>
+
+<sect1>Figuras, tablas y elementos flotantes<label id="tex-floats">
+<!-- ===========================================================-->
+<p>
+<sect2>Cmo puedo poner una figura rodeada de texto?
+<!-- ........................................... -->
+<p>
+Para ello existen distintas opciones, mediante los paquetes
+<itemize>
+<item><em/wrapfig/ (<tt>CTAN:macros/latex/contrib/other/misc/wrapfig.sty</tt>)
+ Contiene <em/wraptable/, para hacer lo mismo con tablas.
+<item><em/floatflt/ (<tt>CTAN:macros/latex/contrib/other/floatflt/</tt>)
+<item><em/picins/ (<tt>CTAN:macros/latex209/contrib/picins/</tt>), que tambin
+ puede utilizarse con tablas.
+<item><em/picinpar/ (<tt>CTAN:macros/latex209/contrib/picinpar</tt>)
+</itemize>
+ todos ellos disponibles en el <tt/CTAN/. Para casos sencillos un simple
+ <tt/parbox/ o una <tt/minipage/ pueden hacer un buen trabajo.
+
+<sect2>Cmo puedo poner una figura a dos columnas?
+<!-- ........................................... -->
+<p>
+ Usando el entorno <tt/figure*/ en vez de <tt/figure/, para que &latex; sepa
+ que ese elemento flotante es de doble ancho. Si no, lo considera de ancho
+ normal, y la imagen que se mete dentro, simplemente <em/no cabe/ y se sale por
+ el otro lado, ocultando el texto de la otra columna.
+
+<sect2>Cmo consigo un mayor control de la posicin de figuras y dems elementos flotantes?
+<!-- ........................................... -->
+<p>
+ Para ello puede utilizarse el paquete <em/float/,
+ (<tt>CTAN:macros/contrib/supported/float</tt>, que aade nuevas
+ funcionalidades al comportamiento normal de los elementos flotantes como
+ figuras y tablas.
+
+<sect2>Puedo poner una figura en una tabla?
+<!-- ........................................... -->
+<p>
+ Por qu no?,
+<tscreen><verb>
+...
+\usepackage{graphcix}
+...
+\begin{tabular}{ccc}
+\includegraphics{fig1} &
+\includegraphics{fig2} &
+...
+</verb></tscreen>
+
+<sect2>Cmo colocar dos figuras o tablas juntas de distintas formas?,
+ <!-- ........................................... -->
+ <p>
+ Es posible colocar en &latex; dos figuras o tablas en paralelo, cada una con
+ su pie, as como dos figuras juntas en posicin arbitraria o superpuestas
+ dentro de un entorno figure.
+ <p>
+ Dependiendo de lo que se quiera, puede hacerse bien mediante el paquete
+ <em/subfigure/ o mediante un entorno <em/minipage/ (Vase
+ <em/epslatex.ps/). <em/subfigure/ permite numerar las figuras como (a), ... y
+ tener un pie comn a las subfiguras ms pies individuales para cada subfigura
+ y <em/minipage/ mantiene los pies normales e independientes para cada
+ figura. Por ejemplo, con <em/minipage/,
+<tscreen><verb>
+ \usepackage{capt-of}
+ ...
+ \begin{figure}
+ \begin{minipage}{.5\linewidth}
+ Figure
+ \caption{Foo}
+ \end{minipage}%
+ \begin{minipage}{.5\linewidth}
+ Table
+ \captionof{table}{Too}
+ \end{minipage}
+ \end{figure}
+</verb></tscreen>
+ El uso del paquete <em/capt-of/ (Vase "Puedo poner un pie en tablas y figuras
+ que no flotan?") sera necesario en este caso ya que los dos elementos son
+ distintos, una figura y una tabla, pero no sera necesario si los dos fueran
+ figuras o los dos tablas.
+<p>
+ Si lo que se quiere es simplemente colocar dos figuras juntas adems de lo
+ anterior sin <tt/\caption/ puede utilizarse algo como
+<tscreen><verb>
+\setlength{\unitlengtth}{1cm}\begin{picture}(12,6)
+\put(0,0){\includegraphics[width=6cm]{figura1.ps}}
+\put(6,0){\includegraphics[width=6cm]{figura2.ps}}
+\end{picture}
+</verb></tscreen>
+ As las figuras se colocan como uno quiera e incluso puede hacerse que una
+ figura se superponga sobre otra (como si fueran fotos en una mesa).
+
+<sect2>Puedo poner un pie en tablas y figuras que no flotan?,
+ <!-- ........................................... -->
+<p>
+ A veces se desea colocar figuras y tablas en un lugar preciso y para ello se
+ prescinde de los entornos <em/figure/ y <em/table/. Sin embargo tambin se
+ desea poder usar <tt>\caption</tt> para no perder la numeracin y la
+ referencia en la lista de figuras y tablas.
+
+ Un equivalente a la orden <tt>\caption</tt> llamado <tt/\captionof/ puede ser
+ utilizado fuera de entornos flotantes (<em/figure/ y <em/table/) si se hace
+ uso del paquete <em/capt-of/. Su sintaxis es <tt/\captionof{tipo}[pie
+ corto]{pie largo}/ donde el pie corto es el opcional que ir a la tabla de
+ figuras/tablas y el tipo es figura/tabla.
+
+ La llamada en el documento sera del tipo
+<tscreen><verb>
+\centerline{\includegraphics{mi grafica}}
+\captionof{figure}{Esta es mi grafica}
+</verb></tscreen>
+ para una figura, mientras que para una tabla se puede usar algo del tipo:
+<tscreen><verb>
+\begin{center}
+\begin{tabular}{*2l}\hline\hline
+uno & dos\\
+tres & cuatro\\\hline
+\end{tabular}
+\end{center}
+\captionof{table}{Esto es una tabla} % se puede incluir dentro del entorno center.
+</verb></tscreen>
+
+<!-- ........................................... -->
+<sect2>Cmo hago para incluir elementos flotantes grandes o numerosos sin que den errores o se vayan al final?
+<!-- .......................................... -->
+<p>
+ Las clases <em/article/, <em/report/ y <em/book/ estndar son muy exigentes en
+ cuanto a sus "consideraciones estticas" para poner grficos flotantes en una
+ pgina. El caso es que sto slo es til cuando hay pocos objetos flotantes,
+ pero si hay muchos, esta exigencia es contraproducente. Lo que acaba pasando
+ es que &latex; no encuentra lugares adecuados para poner los grficos y los
+ acaba mandando todos al final o dando errores. Afortunadamente, los parmetros
+ que controlan todo sto son fcilmente configurables y para mejorar las cosas
+ basta copiar y pegar los que vienen en <em/amsart.cls/, que son mucho mas
+ flexibles,
+<tscreen><verb>
+\setcounter{topnumber}{4}
+\setcounter{bottomnumber}{4}
+\setcounter{totalnumber}{4}
+\setcounter{dbltopnumber}{4}
+\renewcommand{\topfraction}{.97}
+\renewcommand{\bottomfraction}{.97}
+\renewcommand{\textfraction}{.03}
+\renewcommand{\floatpagefraction}{.9}
+\renewcommand{\dbltopfraction}{.97}
+\renewcommand{\dblfloatpagefraction}{.9}
+\setlength{\floatsep}{12pt plus 6pt minus 4pt}
+\setlength{\textfloatsep}{15pt plus 8pt minus 5pt}
+\setlength{\intextsep}{12pt plus 6pt minus 4pt}
+\setlength{\dblfloatsep}{12pt plus 6pt minus 4pt}
+\setlength{\dbltextfloatsep}{15pt plus 8pt minus 5pt}
+</verb></tscreen>
+Cuando se quiere hacer para una nica figura puede utilizarse el paquete
+<em/afterpage/, por ejemplo en
+<tscreen><verb>
+\usepackage{afterpage}
+...
+\begin{figure}
+\includegraphics{figura-muy-grande}
+\end{figure}
+\afterpage{\clearpage}
+</verb></tscreen>
+la figura grande pasar a la pgina siguiente (donde quedar sola), en lugar de
+irse al final del documento.
+
+<!-- ........................................... -->
+<sect1>Cmo giro un elemento en un documento &latex;?
+<!-- ============================================= -->
+<p>
+ Para giros sencillos, el paquete <em/graphicx/ contiene las orden
+ <tt>\rotatebox</tt> que permite conseguir giros de elementos de texto o
+ incluso de elementos ms complejos.
+ Sin embargo, cuando se quieren rotar
+ elementos complejos es recomendable aprovechar las posibilidades del paquete
+ <em/rotating/ (disponible en
+ <tt>CTAN:macros/latex/contrib/supported/rotating</tt>). Este paquete permite
+ girar casi cualquier tipo de elemento, incluyendo figuras o tablas completas
+ con sus cabeceras, mediante los entornos <em/sideways/, <em/sidewaystable/ y
+ <em/sidewaysfigure/. Por ejemplo,
+<tscreen><verb>
+\documentclass{article}
+\usepackage{rotating}
+\begin{document}
+\begin{sideways}
+\begin{tabular}....
+
+\end{tabular}
+\end{sideways}
+\end{document}
+</verb></tscreen>
+ Hay que tener en cuenta que en todos estos casos se modifica el postscript,
+ por lo que los resultados no se ven correctamente con <em/xdvi/ ni funcionan
+ bien con <em/pdflatex/.
+
+<sect1>Cmo escribo algunos smbolos?
+<!-- ======================================================== -->
+<p>
+<descrip>
+<tag/Cmo obtener el smbolo del euro?/
+ Utilizando el paquete <em/eurofont/ de CTAN. Contiene instrucciones acerca de
+ su uso con &latex;. La notacin de entrada normal es
+ <tt>\EUR{1,50}</tt>. Tambin puede utilizarse el paquete textcomp y la macro
+ <tt>\texteuro</tt>.
+<tag/Cmo escribir los grados en &latex;?/
+ Para obtener un resultado de mejor calidad que con <tt>^\circ</tt> puede
+ utilizarse la orden <tt>\textdegree</tt> del paquete <em/textcomp/.
+<tag/Cmo encerrar un caracter en un crculo?/
+ Utilizando la orden <tt/\textcircled{...}/
+<tag/Cmo escribir la barra invertida?/
+ Como texto: <tt>\textbackslash</tt>.
+ Como matemticas: <tt>\backslash</tt>.
+ Como cdigo: <tt>\verb|\|</tt>
+<tag/Cmo escribir un espacio en blanco visible?/
+ Utilizando la orden <tt/\textvisiblespace/
+<tag/Cmo escribir el smbolo del sombrerito de la ?/
+ Utilizando la orden <tt>\textasciitilde</tt>
+</descrip>
+
+<sect1>Cmo convierto mis documentos a &latex; y desde &latex;?
+<!-- ======================================================== -->
+<p>
+ Existe una FAQ especfica acerca de las conversiones entre formatos &tex;
+ y de otros procesadores de textos,
+ <!-- disponible en
+ <htmlurl url="http://www.kfa-juelich.de/isr/1/texconv/texcnv.html"
+ name="http://www.kfa-juelich.de/isr/1/texconv/texcnv.html"> -->
+ que se archiva en <tt>CTAN:help/wp-conv/wp-conv.zip</tt>.
+
+<sect2>Cmo obtengo un documento PDF a partir de mi documento &tex;?
+<label id="tex-a-PDF">
+<!-- ......................................... -->
+<p>
+Existen distintas formas de producir PDF usando (La)&tex;.
+<itemize>
+ <item>
+ A partir del PS -- ver la pregunta <ref id="postscript"
+ name="Qu es PostScript?"> --, usando <em/Distiller/ (de Adobe) o
+ <em/ghostscript/, en este ltimo caso, se recomienda usar una versin
+ posterior a la 5.53, que mejora el PDF generado (lo hace ms compacto). Se
+ pueden perder los enlaces y algunas caractersticas de PDF (las
+ anotaciones). Las distribuciones de <em/ghostscript/ suelen venir con un
+ pequeo programa llamado <em/ps2pdf/ que hace la transformacin llamando a
+ <em/ghostscript/ con los parmetros adecuados.
+ <item>
+ A partir de DVI, usando <em/dvipdfm/, (<tt>CTAN:dviware/dvipdfm</tt>), que
+ genera PDF de alta calidad, insertando los grficos y permitiendo
+ anotaciones y enlaces. Su pgina raz es <htmlurl
+ url="http://odo.kettering.edu/dvipdfm"
+ name="http://odo.kettering.edu/dvipdfm">, pero tiene una serie de
+ restricciones que deben consultarse en el manual.
+ <item>
+ Usando <em/pdf&tex;/, que procesa el archivo fuente de &tex; y genera PDF
+ directamente. Acompaado por el paquete <em/hyperref/, es de la mxima
+ utilidad en la generacin de documentos que mantienen la calidad de
+ composicin de textos de &tex; y permiten cierta interaccin. <em/pdf&tex;/
+ est an en desarrollo, pero permite generar PDF para casi todos los
+ documentos -- para ver los detalles y limitaciones en la inclusin de
+ figuras y cdigo postscript, vase la seccin <ref id="pdftex-dibujos"
+ name="Introduciendo figuras y cdigo postscript en pdf&tex;"> --.
+ Las versiones de desarrollo pueden encontrarse
+ en: <htmlurl url="http://www.fi.muni.cz/~thanh/download/"
+ name="http://www.fi.muni.cz/~thanh/download/">. Informacin adicional est
+ disponible en <htmlurl url="http://www.tug.org/interest.html#projects"
+ name="http://www.tug.org/interest.html#projects">.
+</itemize>
+ Cuando el documento de entrada no contiene nicamente texto &tex;/&latex; sino
+ tambin figuras en postscript encapsulado o utiliza paquetes que mediante
+ cdigo postscript cambian el texto (rotaciones, reescalados, sustitucin de
+ cadenas) o dibujan, las cosas son un poco ms complicadas ya que <em/pdf&tex;/
+ no lo soporta directamente. El camino <tt>dvi->ps->pdf</tt> que se ha sealado
+ antes debe funcionar pero pueden perderse por el camino algunas caractersticas
+ del pdf. Otros caminos alternativos pasan por convertir sobre la marcha a pdf
+ las figuras y efectos postscript. Esto puede hacerse, con ms o menos
+ limitaciones de distintas formas:
+<itemize>
+ <item>
+ Utilizando <em/tex2pdf/, disponible en <htmlurl
+ url="http://developer.berlios.de/cvs/?group_id=57"
+ name="http://developer.berlios.de/cvs/?group_id=57">. La idea es que
+ <em/tex2pdf/ procesa cada grafico que emplea sustituciones de <em/psfrag/ y
+ luego lo convierte a pdf. Para grficos que no se encuentran en minipages,
+ tablas, funciona relativamente bien. La ltima versin cvs de <em/tex2pdf/
+ soporta preliminarmente <em/psfrag/ y <em/pstricks/ (este ultimo a traves de
+ <em/ps4pdf/), sin embargo, de momento el proyecto parece parado,
+ <item>
+ <em/v&tex;/ es una distribucin comercial de &tex; que da salida <em/.pdf/
+ directamente y soporta inclusin de figuras <tt/.eps/, as como el uso de
+ <em/psfrag/ y de algunos otros paquetes que utilizan <em/postscript/ de alto
+ nivel. Existen versiones para linux y OS/2 gratuitas, disponibles en
+ <itemize>
+ <item> <htmlurl url="http://www.micropress-inc.com/linux/"
+ name="http://www.micropress-inc.com/linux/">
+ <item> <htmlurl url="http://www.micropress-inc.com/os2/"
+ name="http://www.micropress-inc.com/os2/">
+ </itemize>
+ y en <tt>CTAN:systems/vtex</tt>. La versin para Windows es comercial
+ <htmlurl url="http://www.micropress-inc.com"
+ name="http://www.micropress-inc.com">
+ <item>
+ Utilizando el paquete <em/pdftricks/, disponible en
+ <tt>CTAN:macros/latex/contrib/pdftricks</tt>, que intenta extender el poder
+ del paquete <em/pstricks/ a pdf&latex;.
+ <item>
+ Utilizando el paquete <em/ps4pdf/, disponible en
+ <tt>CTAN:macros/latex/contrib/ps4pdf</tt>. Vase <ref id="pdftex-dibujos"
+ name="Introduciendo cdigo y figuras postscript en <em/pdf&tex;">
+</itemize>
+
+<sect2>Cmo obtengo una versin texto a partir de un documento PDF?
+<!-- ......................................... -->
+<p>
+ La forma ms sencilla es mediante el <em/Adobe Reader/ (antes <em/Acrobat
+ Reader/) -- vase <ref id="formato-pdf" name="El formato pdf" > -- utilizando
+ la herramienta <em/Obtener texto/ que se encuentra a la izquierda en el
+ <em/Adobe Reader/.
+
+<sect2>Cmo obtengo un documento html a partir de mi documento &tex;?
+<label id="tex-a-html">
+<!-- .............................................................. -->
+<p>
+ En la pgina
+ <htmlurl url="http://www.mayer.dial.pipex.com/tex.htm"
+ name="http://www.mayer.dial.pipex.com/tex.htm"> se comentan diferentes
+ programas de conversin de &latex; a html con ejemplos del resultado de las
+ distintas conversiones. Los ms conocidos son
+<descrip>
+<tag/HEVEA/
+ es un conversor de &latex; a html bastante completo, que
+ convierte los smbolos sin utilizar grficos (aunque puede requerir un poco de
+ configuracin del navegador). Disponible en
+ <htmlurl url="http://para.inria.fr/~maranget/hevea/"
+ name="http://para.inria.fr/~maranget/hevea/">. Tiene versiones para Linux,
+ Solaris y Windows aunque es posible compilarlo para otros sistemas
+ operativos a partir del cdigo fuente.
+<tag/TTH/
+ es otro conversor de &latex; a html que tambin convierte las
+ ecuaciones en vez de representarlas como imgenes. Disponible en
+ <htmlurl url="http://hutchinson.belmont.ma.us/tth/"
+ name="http://hutchinson.belmont.ma.us/tth/">. Tiene versiones para Linux,
+ Mac y Windows aunque es posible compilarlo para otros sistemas operativos a
+ partir del cdigo fuente. Utiliza grficos.
+<tag/&tex;4ht/
+ es otro conversor a distintos sistemas de hipertexto,
+ disponible en
+ <htmlurl url="http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html"
+ name="http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html">. Tiene
+ versiones para Linux, Mac y Windows aunque es posible compilarlo para otros
+ sistemas operativos a partir del cdigo fuente.
+<tag/latex2html/
+ es quizs el ms antiguo de los conversores, escrito en perl y utiliza
+ grficos.
+</descrip>
+
+<sect2>Convirtiendo a &latex; desde otros formatos
+<!-- ......................................... -->
+<p>
+ <descrip>
+ <tag/WordPerfect/
+ El programa <em/wp2latex/ (disponible en <tt>CTAN:support/wp2latex</tt>) ha
+ sido recientemente actualizado por Jaroslav Fojtik y ahora est disponible
+ tanto para <em/DOS/ como para <em/Unix/.
+
+ <tag/Rich Text Format (RTF)/
+ Hay dos conversores disponibles, <em/rtf2tex/ de Robert Lupton (disponible
+ en <tt>CTAN:support/rtf2tex</tt>) y <em/rtf2latex/, de Erwin Wechtl
+ (disponible en <tt>CTAN:support/rtf2latex</tt>), para &tex; y &latex;
+ respectivamente.
+
+ <tag/Microsoft Word/
+ Aunque hay un programa de conversin (<em/wd2latex/, disponible en
+ <tt>CTAN:dviware/wd2latex</tt>), se recomienda convertir el documento a RTF
+ y utilizar uno de los conversores de RTF mencionados.
+
+ Tambin hay un par de conversores comerciales, <em/word2tex/ y
+ <em/tex2word/.
+</descrip>
+
+
+<sect1>Cmo rehago los formatos de &tex; y &latex;?<label id="formatos">
+<!-- ==================================================================-->
+<p>
+Los formatos de &tex; son archivos que contienen las macros bsicas
+ precompiladas para obtener una mayor eficiencia. Para rehacer un
+ formato es necesario utilizar la orden <tt/initex/ (Este nombre cambia
+ para algunas distribuciones, por ejemplo para <em/em&tex;/ es <tt/tex
+ -i/). Como muestra, para rehacer el formato <em/plain/ se hara
+<tscreen><verb>
+initex plain \dump
+</verb></tscreen>
+Con eso se tiene el archivo <tt/plain.fmt/; ya slo queda reemplazarlo donde
+ estuviera el original y listo.
+<p>
+Para hacerlo por ejemplo para <em/eplain/ se habra hecho <tt/initex plain/, y
+ cuando aparece <tt/*/ se introducira <tt>\input eplain</tt> y
+ despus cuando vuelve a aparecer <tt/*/ se introducira
+ <tt>\dump</tt>, as tendra un formato con <tt/eplain/ y no habra que
+ estar ponindolo con <tt>\input</tt>.
+<p>
+Cuando deben incluirse distintos archivos en el formato, a menudo es ms cmodo
+ utilizar una archivo que los llame a todos. Por ejemplo, para
+ <tt/eplain/ se podra haber creado el archivo <tt/eplain.ini/ con las
+ lneas
+<tscreen><verb>
+\input plain
+\input eplain
+\dump
+</verb></tscreen>
+y se habra rehecho el formato con <tt/initex eplain.ini/.
+<p>
+En la mayor parte de las distribuciones modernas no es necesario rehacer los
+ formatos como se ha dicho antes, sino que hay herramientas que ayudan
+ a ello. As, por ejemplo en <em/te&tex;/ despus de configurar los
+ distintos parmetros del formato (idioma, tamaos de memoria...) al
+ salir se rehace automticamente el formato, o en <em/mik&tex;/ donde
+ hay un elemento en un men desplegable para rehacer los formatos ( o
+ desde una ventana DOS <tt>initexmf --dump</tt>).
+
+<sect1>Cmo llamo a un editor desde &tex;/&latex;?
+<!-- ====================================================-->
+<p>
+Dando el valor adecuado a la variable de entorno <tt/TEXEDIT/
+<tscreen><verb>
+SET TEXEDIT=tu_editor +%d %s
+</verb></tscreen>
+en el <tt/autoexec.bat/ o similares o
+<tscreen><verb>
+export TEXEDIT=tu_editor +%d %s
+</verb></tscreen>
+para <em/bash/ y similares
+
+<sect1>Algunas cosillas matemticas.
+<!-- ======================================================= -->
+<sect2>Cmo escribo un nmero con periodo utilizando &latex;?
+<!-- ...................................................... -->
+<p>
+Para escribir un periodo (el acento breve invertido que indica la repeticin de
+ cifras decimales y que se pone encima de la parte peridica del
+ nmero) la solucin ms elegante consiste en utilizar el paquete
+ <em/yhmath/ de Yannis Haralambous, disponible en
+ <tt>CTAN:macros/latex/contrib/supported/yhmath</tt>. Este paquete
+ permite indicar periodos de longitud arbitraria mediante un acento
+ matemtico <tt>\wideparen</tt> que hace precisamente ese papel.
+<p>
+El paquete <em/yhmath/ necesita un tipo especial que viene con el paquete y
+ adems el paquete <em/amsmath/, por lo que para uso espordico o no
+ tan exigente puede bastar una definicin como la siguiente
+<tscreen><verb>
+\def\periodo#1{\mathop{\vbox{\ialign{##\crcr\noalign{\kern3pt}%
+\ensuremath{\braceld\leaders\vrule\hfill\bracerd}%
+\crcr\noalign{\kern3pt\nointerlineskip}%
+\ensuremath{\hfill\displaystyle{#1}\hfill}\crcr}}}\limits}
+</verb></tscreen>
+Existe otro paquete denominado <em/tipa/, disponible en
+ <tt>CTAN:/fonts/tipa</tt>. ste es un sistema para trabajar con
+ alfabetos fonticos, que proporciona la orden
+ <tt>\texttoptiebar{'caracter'}</tt> donde <tt>'caracter'</tt>
+ obviamente es un numero(s) o una letra(s).
+
+<sect2>Cmo puedo hacer para que la etiqueta de una ecuacin p.ej. (3.5) contenga adems el nmero de la seccin actual p.ej. (3.1.5)
+<!-- ...................................................... -->
+<p>
+ La respuesta se puede encontrar en Lamport seccin 6.3 y en el Companion
+ seccin 8.6 (Este captulo del Companion est actualizado en
+ <tt>CTAN:info/companion-rev/</tt>). &latex; define y mantiene unos cuantos
+ contadores; uno de ellos es <em/equation/. Para generar una etiqueta impresa,
+ &latex; ejecuta una orden cuyo nombre se forma aadiendo <tt>\the</tt> al
+ comienzo del nombre del contador adecuado. Por ejemplo, un nmero de ecuacin
+ se genera con la orden <tt>\theequation</tt>.
+
+ Para cambiar la numeracin de ecuaciones de modo que se indique el captulo, la
+ seccin y un nmero correlativo dentro de la seccin haramos:
+<tscreen><verb>
+\renewcommand{\theequation}{\thesection.\arabic{equation}}
+</verb></tscreen>
+ El problema es que ahora tendramos que volver a poner a cero el contador de
+ ecuaciones al comienzo de cada seccin o captulo. Una solucin sencilla es
+ incluir en el prembulo (entre un <tt>\makeatletter</tt> y un
+ <tt>\makeatother</tt>) lo siguiente:
+<tscreen><verb>
+\@addtoreset {equation}{section}
+</verb></tscreen>
+ Esto har que automticamente se ponga el contador <em/equation/ a 1 cuando se
+ encuentre un nuevo <tt>\section.</tt>
+
+<sect2>Cmo hay que hacer para lograr la N, R de doble trazo con que se representan los nmeros naturales, reales, etc...
+<!-- ...................................................... -->
+<p>
+ Una forma que funciona incluso en plain &tex; y que no requiere cargar tipos
+ adicionales es con definiciones del tipo
+<tscreen><verb>
+\def\CC{{\rm C\kern-.18cm\vrule width.6pt height 6pt depth-.2pt \kern.18cm}}
+\def\NN{{\mathop{{\rm I}\kern-.2em{\rm N}}\nolimits}}
+\def\PP{{\mathop{{\rm I}\kern-.2em{\rm P}}\nolimits}}
+\def\RR{{\mathop{{\rm I}\kern-.2em{\rm R}}\nolimits}}
+\def\RRt{{\fa I}\kern-.2em{\fa R}}
+ %% This version of \RR can be used in the title of the paper
+\def\ZZ{{\mathop{{\rm Z}\kern-.28em{\rm Z}}\nolimits}}
+</verb></tscreen>
+ Tambin es posible utilizar el tipo <em/mathbb/ incluido con las
+ <em/amsfonts/. stas se cargaran en el prembulo con
+<tscreen><verb>
+\usepackage{amsfonts}
+\usepackage[mathscr]{euscript}
+</verb></tscreen>
+ y se llamaran como <tt>\mathbb{C}</tt>, etc...
+<p>
+ Otra alternativa es el uso de los tipos <em/bbm/. Estos de cargan en el
+ prembulo con
+<tscreen><verb>
+\usepackage{bbm}
+</verb></tscreen>
+ de forma que <tt>$\mathbbm{N, Z, R, Q, I, C}$</tt> dara el correspondiente
+ smbolo.
+
+<sect2>Puedo forzar que una frmula tenga el mismo nmero que otra?
+<!-- ................................... -->
+<p>
+S mediante el paquete <em/amsmath/ y la orden <tt/\tag/. Por ejemplo,
+<tscreen><verb>
+\begin{equation}\label{1}
+1+1=2.
+\end{equation}
+\begin{equation}
+1+1=2.\tag{\ref{1}}
+\end{equation}
+</verb></tscreen>
+<sect2>Puedo escribir smbolos matemticos en negrita?
+<!-- ................................... -->
+<p>
+Pues no es nada elemental. Sin tipos especiales no. Inicialmente no se consider
+necesario que las letras griegas pudieran representar vectores y no se
+incluyeron tipos con ellas. La solucin pasa por usar amstex y los tipos
+<em/euler/ (ms en concreto <em/eurb/).
+<p>
+Tambin puede utilizarse el paquete <em/amsmath/. As,
+<tscreen><verb>
+\usepackage{amsmath}
+\begin{document}
+$\boldsymbol{H}$
+\end{document}
+</verb></tscreen>
+Si algn smbolo de alguna fuente no cambia a negrita con esta orden, puede
+tambin utilizarse, con el mismo paquete, <tt/$\pmb{H}$/.
+
+<sect2>Puedo rotar una ecuacin?
+<!-- ................................... -->
+<p>
+Puede utilizarse ls orden <tt/rotatebox/ del paquete <em/graphicx/, pero hay que
+meter la ecuacin en un <tt/parbox/, por ejemplo, utilizando el entorno
+<tt/align/, del paquete <em/amsmath/,
+<tscreen><verb>
+\rotatebox{35}{
+ \parbox{4cm}{
+ \begin{align*}
+ (la ecuacion)
+ \end{align*}
+ }
+}
+</verb></tscreen>
+
+<sect2>Algunas preguntas matemticas de breve respuesta.
+<!-- .............................................. -->
+<p>
+<descrip>
+ <tag/Cmo se escriben los nmeros combinatorios (por ejemplo N sobre k)?/
+ <tt>\binom{N}{k}</tt>, disponible en el paquete <em/amsmath/.
+
+ <tag/Cmo represento un tensor con sus ndices?/
+ Puede probarse con el paquete <em/tensind/, disponible en
+ <tt>CTAN:/macros/latex/contrib/supported/bezos/</tt>.
+
+ <tag/Cmo cancelar elementos en una ecuacin en &latex;/
+ Mediante el paquete <em/cancel/
+
+ <tag/Cul es la instruccin para poner el producto vectorial?/
+ <tt/\times/ o <tt/\wedge/, segn la forma que prefieras (cruz y
+ angulito, respectivamente).
+
+ <tag/Qu smbolos estn disponibles para &latex;?/
+ Adems de los smbolos bsicos de &latex; muchos otros smbolos estn
+ disponibles a travs de distintos paquetes. Una excelente referencia a
+ todos los smbolos disponibles se encuentra en
+ <tt>CTAN:tex-archive/info/symbols/comprehensive</tt>
+</descrip>
+
+
+<sect1>Cmo hago cuadernillos, trpticos y documentos con formatos especiales?
+<label id="formatos-especiales">
+<!-- ================================================-->
+<sect2>Cmo hago cuadernillos con &tex; o &latex;?
+<!-- -------------------------------------------- -->
+<p>
+Para hacer cuadernillos estrictamente con &tex; o &latex; se pueden utilizar
+ las utilidades para manipular <tt/.dvi/ (disponibles en
+ <tt>CTAN:dviware/dvibook</tt>) o utilizar el paquete <em/quire/
+ (disponible en <tt>CTAN:macros/generic/midnight</tt>). Ambos permiten
+ hacer cuadernillos, pero en ambos casos es necesario tener los tipos
+ para los distintos tamaos antes y despus, y dan problemas con
+ facilidad cuando se incluyen grficos externos.
+<!-- > texexec, que se puede conseguir en http://www.pragma-ade.nl tambin puede
+> hacerlo (directamente desde el .tex!). texexec est en el sistema
+> ConTeXt, y a lo mejor hay que instalar ms cosas.
+-->
+<p>
+El mtodo ms recomendable es utilizar las <em/psutils/, un conjunto de
+ utilidades para manejar archivos <em/postscript/. Aunque el ejemplo
+ est para un unix, tambin estn disponibles para <em/DOS/, lo nico
+ que en vez de mandarlo a la cola de impresora se mandara a un archivo
+ que despus se imprimira con <em>ghostscript/ghostview</em>.
+<p>
+Para Unix por ejemplo, si se colocan adecuadamente las hojas en la impresora
+<tscreen><verb>
+psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -o | lpr
+</verb></tscreen>
+imprimira las caras impares del librillo (cada una de ellas con dos pginas
+ reducidas y correctamente ordenadas). Se sacan las hojas, se ordenan
+ adecuadamente y se colocan adecuadamente en la impresora y
+<tscreen><verb>
+psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -e | lpr
+</verb></tscreen>
+imprimira las caras pares del librillo, y ya est, se tiene un librillo
+ perfecto. La utilidad <em/pstops/ tambin permite hacer todo eso
+ directamente, pero con unas opciones mucho ms crpticas.
+<p>
+<em/psbook/ tambin permite definir el tamao del pliego, cuando el libro va a
+ constar de distintos pliegos cosidos, cada uno de ellos de un nmero
+ de pginas. Por ejemplo,
+<tscreen><verb>
+$ psbook -s 16 manualA4.ps
+</verb></tscreen>
+reordenara las pginas para hacer pliegos de 16 pginas, y su salida se pasara
+ despus por <em/psnup/ y <em/psselect/. El comportamiento por omisin
+ consiste en hacer un nico pliego.
+
+<sect2>Cmo hago trpticos con &latex;?
+<!-- -------------------------------------------- -->
+<p>
+ El paquete <em/leaflet/ nos permite construir trpticos. Realmente slo
+ modifica los mrgenes de la pgina completa para dividirla en tres reas. El
+ resultado al compilar es un documento con 6 pginas como mximo, en el que
+ cada pgina tiene el texto escrito en una columna estrecha a la izquierda y el
+ resto de la pgina est en blanco. Este documento an no est finalizado y
+ debe ser postprocesado. El postproceso lo hace un script (que viene incluido
+ en el paquete), que se ocupa de llamar a <em/pstops/ (que debe estar
+ instalado) y que es quien junta tres pginas en una, colocndolas en el orden
+ apropiado para que al imprimir a doble cara el resultado sea tres pginas por
+ cara, y de modo que al doblar en tres quede en el orden correcto de
+ lectura. Puesto que <em/pstops/ funciona sobre ficheros postscript (.ps), el
+ documento original debe ser procesado con <em/dvips/ (no sirve usar
+ <em/pdflatex/).
+
+ <sect2>Puedo preparar un pster con &tex/&latex;?
+ <label id="posters">
+ <!-- ......................................... -->
+ <p>
+ Por una parte existe un paquete llamado <em/a0poster/
+ (<tt>CTAN:macros/latex/contrib/supported/a0poster</tt>) y por otra existe
+ una alternativa basada en un programa C llamado <em/poster/
+ (<tt>CTAN:support/poster</tt>). Este ltimo distribuye el texto en pginas
+ A4 que pueden unirse para hacer un pster grande.
+
+ <sect2>Puedo hacer libretos y cartulas de CD con &latex;?
+ <!-- -------------------------------------------- -->
+ <p>
+ S, con el paquete <em/cd-cover/, disponible en
+ <tt>CTAN:macros/latex/contrib/cd-cover</tt>. Eso s, a la hora de imprimir
+ hay que decirlo que lo haga en apaisado.
+
+<sect1>Cmo puedo preparar una exposicin utilizando &latex;?
+<!-- ======================================================-->
+ <sect2> Haciendo transparencias con &latex;
+ <!-- ......................................... -->
+ <p>
+ En primer lugar se tiene la clase de documento <em/slides/, que forma
+ parte de &latexe;.
+ <!-- El aspecto de un documento que utiliza esta clase sera algo as como
+<tscreen><verb>
+\documentclass[a4paper]{slides}
+\begin{document}
+% Transparencia ....
+\begin{slide}
+\begin{center}
+{\Large **Titulo....**}
+\end{center}
+**Texto...**
+\end{slide}
+...
+\end{document}
+</verb></tscreen> -->
+ Adems, existen varios paquetes preparados para hacer transparencias. Los
+ ms clsicos son
+ <itemize>
+ <item><em/seminar/ (<tt>CTAN:macros/latex/contrib/other/seminar</tt>) </item>
+ <item><em/foiltex/ (<tt>CTAN:macros/latex/contrib/supported/foiltex</tt>).</item>
+ </itemize>
+ <sect2>Haciendo una presentacin con &latex;
+ <!-- ......................................... -->
+ <p>
+ Tambin es posible generar directamente las transparencias en formato
+ <em/.pdf/ <ref id="formato-pdf" name="Qu es el formato pdf?"> utilizando
+ los paquetes <em/pdfslide/
+ (<tt>CTAN:macros/latex/contrib/supported/pdfslide</tt>) y <em/pdfscreen/
+ (<tt>CTAN:macros/latex/contrib/supported/pdfscreen</tt>), quedando las
+ presentaciones preparadas para ser proyectadas desde un ordenador.
+ <!-- <htmlurl url="http://river-valley.com/download/" name="http://river-valley.com/download/"-->
+ Otra alternativa consiste en utilizar la clase de documento <em/foils/ (parte
+ de <em/foiltex/) y <em/pdflatex/, utilizando posteriormente el
+ postprocesador <em/ppower4/
+ (<htmlurl
+ url="http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html"
+ name="http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html" >)
+ para tratar el archivo <em/pdf/ obtenido. Un ejemplo de presentacin
+ realizada con este sistema es la de Luis Seidel al EGUTH99, disponible en
+ <htmlurl url="ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb"
+ name="ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb">
+
+ <sect3> beamer
+ <p>
+ Una opcin que se est haciendo muy popular es la clase <em/beamer/,
+ disponible en <htmlurl url="http://latex-beamer.sourceforge.net/"
+ name="http://latex-beamer.sourceforge.net/">. Aparte del propio manual puede
+ encontrarse una gua rpida en
+ <htmlurl url="http://www.geocities.com/kijoo2000/beamer.html"
+ name="http://www.geocities.com/kijoo2000/beamer.html">.
+ <p>
+ Con <em/beamer/ se distribuye otro paquete independiente para la inclusin
+ de objetos multimedia en los documentos PDF creados mediante pdftex.
+ <p>
+ nicamente se requiere en el prembulo:
+<tscreen><verb>
+\usepackage{multimedia}
+</verb></tscreen>
+ y la inclusin (pero no la incrustacin) de ficheros de vdeo AVI o QuickTime es
+ tan fcil como:
+<tscreen><verb>
+\movie[width=60mm,height=45mm,borderwidth=0.5mm]{Ttulo}}{fichero.avi}\\
+\movie[width=60mm,height=45mm,poster,showcontrols]{}{fichero.mov}\\
+</verb></tscreen>
+ as como para audio (estos s que pueden ser incrustables):
+<tscreen><verb>
+\sound[inlinesound,samplingrate=22050,encoding=muLaw,bitspersample=8,
+channels=2,label=misonido]{}{fichero.au}\\
+
+\hyperlinksound[]{misonido}{\includegraphics[width=10mm]{inicio.png}}
+\hyperlinkmute{\includegraphics[width=10mm]{paro.png}}\\
+</verb></tscreen>
+ <sect2>Ms informacin sobre presentaciones
+ <!-- ......................................... -->
+ <p>
+ La pgina web
+ <htmlurl url="http://www.math.uakron.edu/~dpstory/pdf_demos.html"
+ name="http://www.math.uakron.edu/~dpstory/pdf_demos.html">
+ enumera una serie de macros de &latex; y otros programas utilizados para
+ hacer presentaciones tipo PowerPoint.
+ <p>
+ Otra fuente de informacin acerca de las posibilidades de presentaciones
+ basadas en &tex; y <em/PDF/, es la pgina
+ <htmlurl url="http://www.cds.caltech.edu/caltex/2000/"
+ name="http://www.cds.caltech.edu/caltex/2000/">
+ de Ross Moore, que incluye fuentes de documentos, ejemplos,enlaces,...
+ <p>
+ Otra interesante pgina es
+ <htmlurl url="http://www.miwie.org/presentations/"
+ name="http://www.miwie.org/presentations/">, de Michael
+ Wiedmann, que contiene una enumeracin de distintos sistemas y se ejemplos
+ de cada uno. No slo cubre la presentacin en PDF, sino tambin en HTML y
+ otros formatos. Para cada solucin, muestra un ejemplo, pros y contras.
+ <p>
+ Para presentaciones en pster vase la seccin
+ <ref id="posters" name="psters">.
+
+<sect1>Algunas cosas que a veces se piden para mandar un documento a la imprenta.
+<!-- =========================================================================-->
+<p>
+La forma en que se debe mandar un documento a la imprenta no es nica, sino que depende del tipo de
+ proceso de impresin por el que vaya a pasar el documento. En
+ buena parte de los casos debiera bastar con enviar un archivo
+ postscript normal con el documento. Sin embargo, a veces se pide
+ el documento con caractersticas especiales como las que a
+ continuacin se tratan,
+
+<sect2>Sacando la imagen especular de un archivo (es decir, con todo al revs).
+<!-- .................................................................... -->
+<p>
+Con &latex; puede hacerse utilizando el paquete <em/crop/, en la forma
+<tscreen><verb>
+\usepackage[mirror]{crop}
+</verb></tscreen>
+ La reflexin especular se puede hacer directamente en el
+ postscript, en las tres formas siguientes (si se tiene una
+ distribucin completa y actual como te&tex;)
+<tscreen><verb>
+dvips <archivo dvi> -h mirr.hd
+dvips <archivo dvi> -Pmirr
+dvips <archivo dvi> -Pmirrorprint
+</verb></tscreen>
+Realmente las dos primeras son la misma, pero llamadas de distinta forma
+ (<tt/config.mirr/ llama a <tt/mirr.hd/). <em/crop/ y
+ <tt/mirr.hd/ estn disponible en muchas distribuciones y
+ adems pueden encontrarse en
+ <tt>CTAN:macros/latex/contrib/supported/crop/</tt> y
+ <tt>CTAN:macros/generic/TeX-PS/mirr.hd</tt>
+
+<sect2>Sacando el archivo en negativo (es decir, blanco sobre negro).
+<!-- ............................................................ -->
+<p>
+Para sacar el archivo en negativo puede utilizarse el paquete crop, cargndolo
+ como <tscreen><verb>
+\usepackage[invert]{crop}
+</verb></tscreen>
+
+<sect2> Marcas de corte.
+<!-- ............................................................ -->
+<p>
+ Para hacer los cortes, o marcas de corte (las lneas que sealan por donde
+ deber cortar la guillotina) puede utilizarse el paquete <em/crop/ al que se
+ acaba de hacer referencia. Dentro de las <em/midnight macros/ (disponibles en
+ <tt>CTAN:macros/generic/midnight</tt> se puede utilizar <em/quire/ que tambin
+ permite hacer marcas de corte.
+
+<sect1> Algunas cuestiones adicionales, o menos FAQ
+<!-- ========================================================================-->
+<p>
+<descrip>
+<tag/Cmo evito que se pegue el texto despus de una orden?/
+ Es decir, como evitar que si se escribe algo como <tt>\LaTeX es ...</tt>
+ aparezca como <tt/LaTeXes .../ con el texto pegado. Para ello hay varias
+ formas, algunas ms elegantes que otras. Las ms sencillas son escribirlo bien
+ como <tt>\LaTeX{} es ...</tt> o como <tt>\LaTeX\ es ...</tt>. Sin embargo esto
+ no resulta demasiado elegante, aunque es inevitable cuando se utiliza con
+ rdenes predefinidas. Cuando estas rdenes estn definidas por el autor del
+ documento, resulta muy cmodo utilizar el paquete <em/xspace/, parte de las
+ herramientas bsicas de &latexe;. La forma de uso es simple, debe incluirse en
+ el prembulo del documento la llamada al paquete, <tt>\usepackage{xspace}</tt>
+ y al definir la orden se hace como
+ <tscreen><verb>
+\newcommand{\mycommand}{palabra\xspace}
+ </verb></tscreen>
+ De este modo cualquier llamada a <tt>\mycommand</tt> incluir el espacio en
+ blanco si es necesario, y no lo har si no es necesario.
+
+<!-- ***-->
+
+<tag/Es posible poner en el margen derecho o izquierdo una imgen?/
+ Para colocar una figura en el margen:
+ <tscreen><verb>
+\marginpar{\includegraphics{icono}}
+ </verb></tscreen>
+
+<!-- ****** Notas a pie de pgina *******-->
+
+<tag/Puedo hacer referencias cruzadas a notas a pie de pgina, incluso desde otras notas a pie de pgina?/
+ Perfectamente, con <tt>\label</tt> puesto dentro de la nota al pie
+ <tt>(\footnote{\label{f1}Texto}</tt> y <tt>\ref</tt> puesto en su lugar
+ (<tt>\footnote</tt>{Esta nota hace referencia a la nota <tt>\ref{f1}</tt> de
+ la pgina <tt>\pageref{f1}})</tt>. Mediante <tt>\label</tt> se establece la
+ referencia al ltimo contador incrementado, en este caso el de las notas al
+ pie.
+
+ Naturalmente, hasta que no est la segunda nota, con su <tt>\label</tt>
+ correspondiente, el <tt>\ref</tt> que se ha puesto en la primera no tendr
+ valor asignado, y al componer el texto parcial, en lugar del nmero de la nota
+ aparecern los tpicos smbolos de interrogacin de cerrar.
+
+<!-- ***-->
+
+<tag/Puedo acumular las notas a pie de pgina al final del captulo?/
+ S, utilizando el paquete <em/endnotes/.
+
+<!-- ***-->
+
+<tag/Cmo conseguir que la llamada a la nota de pie de pgina no sea un nmero, sino una letra?/
+ Por ejemplo con
+ <tscreen><verb>
+\renewcommand{\thefootnote}{\itshape\alph{footnote}}
+ </verb></tscreen>
+ (Las llamadas con letras deben ser con cursiva, y se suelen reservar para
+ cuadros y similares.)
+
+<!-- ***-->
+
+<tag/Puedo escribir notas a pie de pgina en el margen?/
+<tscreen><verb>
+\marginpar{\footnotemark}\footnotetext{Texto de la nota}
+</verb></tscreen>
+
+<!-- ***-->
+
+<tag/Puedo escribir notas a pie de pgina en los ttulos de seccin?/
+ S, pero <tt>\footnote</tt> debe ser protegido como
+ <tt>\protect\footnote</tt>. sto tiene un problema adicional, saldr el
+ smbolo de la nota a pie de pgina en la tabla de materias. El paquete
+ <em/footmisc/ con la opcin <tt/stable/ permite hacerlo de una forma ms
+ adecuada.
+
+<tag/Puedo tener ms control sobre la posicin de las notas a pie de pgina?/
+ El paquete <em/yafoot/ permite un mayor control soble las notas a pie de
+ pgina, mediante tres ficheros de estilo, <tt/pfnote.sty/ para confinar las
+ notas a pie en una pgina, <tt/fnopos.sty/ para controlar su posicin y
+ <tt/dblfnote/ para hacerlas a doble columna.
+
+<!-- *** Fin notas a pie de pgina *** -->
+<!-- ****** Otras *******-->
+
+<tag/Cmo saco un listado bonito de un programa en un documento &latex;?/
+ Ms bonito que utilizar verbatim queda con cualquiera de los paquetes
+ <em>listings</em>, <em>lgrind</em> o <em>fancyvrb</em>
+
+<!-- ****** Algunos simbolillos -->
+<!-- ***-->
+
+<!-- ++++++++++++++ *** Otras de tablas y figuras *** +++++++++++++++++++ -->
+<tag/Cmo colorear texto en &latex;?/
+Algunos ejemplillos para empezar a colorear texto
+<tscreen><verb>
+...
+\usepackage{color}
+...
+\begin{document}
+...
+\textcolor[rgb]{1,0,0}{soy un texto que quedara en color rojo}
+\textcolor[rgb]{1,1,0}{yo soy un texto en amarillo}
+\textcolor[rgb]{0,0,1}{hola, soy azul}
+\textcolor[rgb]{0,1,1}{soy azul celeste}
+\textcolor[rgb]{1,0,1}{yo soy rosa}
+\textcolor[rgb]{0,1,0}{yo verde claro}
+\textcolor[rgb]{0.5,0,0}{marron}
+\textcolor[rgb]{0,0.5,0.5}{azul verdoso}
+\textcolor[rgb]{1,1,1}{soy blanco}
+</verb></tscreen>
+etc, etc, etc...
+<p>
+<tt/rgb/ significa <em/red/ <em/green/ <em/blue/ y corresponde a una forma de
+especificar el color. El numero entre corchetes indica cunto
+(R)ed, (G)reen, y (B)lue corresponde al color del texto.
+Existen otras maneras ms complicadas pero sta est bien para empezar.
+
+<tag/Cmo colorear celdas en &latex;?/
+ Utilizando el paquete <em/colortbl/ (junto con el paquete <em/graphicx/)
+<!-- package for the gray levels); read the documentations. -->
+ Algo como
+<tscreen><verb>
+\multicolumn{1}{>{\columncolor[gray]{0.8}}c}{text}
+</verb></tscreen>
+ debe colorear una celda.
+
+<!-- ***-->
+
+<tag/Cmo centrar elementos ms grandes que el ancho de lnea?/
+ Por ejemplo, para una figura puede hacerse de la forma siguiente:
+<tscreen><verb>
+\begin{center}
+ \makebox[0cm][c]{\includegraphics{tufigura.eps}}
+\end{center}
+</verb></tscreen>
+o en general,
+<tscreen><verb>
+\begin{center}
+ \makebox[0cm][c]{
+ Material tabular, o cualquier otra cosa.
+ }
+\end{center}
+</verb></tscreen>
+Si se desea usar el entorno <em/table/, para poder poner el correspondiente
+<tt>\caption</tt>, la cosa se complica un poco ya que <tt/\makebox/ no
+admite un entorno flotante como <em/table/ en su interior:
+<tscreen><verb>
+\begin{center}
+ \begin{table}
+ \centering\makebox[0cm[c]{
+ \begin{tabular}{|c|c|}
+ ...... ....
+ \end{tabular}
+ }
+ \caption{Texto}
+ \end{table}
+\end{center}
+</verb></tscreen>
+Tambin puede colocarse un pie dentro del <tt/\makebox/, pero se necesita un
+poco ms de trabajo (Vase "Puedo poner un pie en tablas y figuras que no flotan?")
+
+<!-- ***-->
+
+<tag/Cmo obtener el tamao de una tabla?/
+ Una posibilidad consiste en fabricar la tabla dentro de un <tt/savebox/ con el
+ entorno <tt/lrbox/ y luego medirlo con <tt/\widthof/, etc. del paquete
+ <em/calc/. Si se usa <em/longtable/, este procedimiento no funciona, ya que se
+ extiende por varias pginas. Sin embargo <em/longtable/ precisamente escribe
+ la longitud de cada fila de la tabla en el fichero <tt/.aux/, por lo que se
+ podra recuperar desde all. En concreto, <em/longtable/ escribe la definicin
+ de una macro <tt/\LT@&lt;num&gt;/, donde <tt/&lt;num&gt;/ es un nmero de
+ orden correlativo de cada entorno <em/longtable/ (en romano y en minsculas)
+ que contiene las longitudes de cada columna.
+
+<!-- ***-->
+
+<tag/Cmo cambiar el grosor que tienen definido por omisin las lneas que separan las columnas y filas dentro de tablas?/
+Por ejemplo con <tt>renewcommand{\arrayrulewidth}{1.1pt}</tt>
+
+<!-- ***-->
+
+<tag/Puedo hacer que una celda de una tabla est dividida en dos por una
+diagonal?/
+Puede utilizarse el paquete <em/slashbox/, disponible en
+<tt>CTAN:macros/latex/contrib/other/slashbox</tt>
+
+<!-- *****************+ Fin tablas y figuras +*********************** -->
+
+<!-- ***-->
+
+<tag/Cmo aadir al texto el nmero de pgina actual?/
+ En principio, podra pensarse que bastara con usar la orden
+ <tt>\thepage</tt>. Sin embargo, debido a cmo &tex; va componiendo los
+ prrafos el resultado puede ser incorrecto, ya que primero ejecuta todas las
+ macros segn va componiendo el prrafo y hasta que no est terminado no decide
+ en que pgina van sus lneas. Si el prrafo ocupa dos pginas, es muy probable
+ que la pgina sea incorrecta.
+ <p>
+ Para sincronizar correctamente la pgina con su nmero hay que usar algn
+ mecanismo que s permita conocer la pgina correcta, como el de las
+ referencias con <tt>\label</tt> y <tt>\pageref</tt>. El siguiente cdigo es
+ una modificacin de uno incluido en el <em/&latex; Companion/:
+<tscreen><verb>
+\usepackage{ifthen}
+\newcounter{pl}
+\newcommand\pcheck{%
+ \stepcounter{pl}%
+ \label{pl-\thepl}%
+ \ifthenelse{\isodd{\pageref{pl-\thepl}}}{impar}{par}}
+\begin{document}
+Esta pgina es \pcheck. \newpage
+Esta pgina es \pcheck.
+\end{document}
+</verb></tscreen>
+
+<!-- ***-->
+
+<tag/Cmo saber el nmero de pginas de un documento para utilizarlo en el mismo?/
+ El paquete <em/lastpage/ lo resuelve de forma adecuada (necesitar un par de
+ compilaciones). Mediante su uso pueden construirse expresiones del tipo pgina
+ 1 de 10 (con pgina <tt>\thepage{}</tt> de <tt>\pageref{LastPage}</tt>).
+
+<!-- ***-->
+
+<tag/Cmo evitar que una <tt/url/ muy larga se me desborde por la derecha?/
+ Utilizando el paquete <em/url/. Est pensado precisamente para eso, para
+ dividir los <tt/url/s por puntos adecuados que no afecten a su legibilidad,
+ como por ejemplo en las barras separadoras de directorio.
+
+<!-- ***-->
+
+<tag/Como se escribe parte de un texto a 2 columnas?/
+Por ejemplo, utilizando el paquete <em/multicol/.
+
+<!-- ***-->
+
+<tag/Como hacer que la clase report comience ndice y captulos en pginas impares?/
+Con la opcin <tt/openright/. Por ejemplo
+<tscreen><verb>
+\documentclass[12pt,a4paper,openright]{report}
+</verb></tscreen>
+
+<!-- ***-->
+
+<tag/Cmo hacer buen postscript o pdf?/
+ Puede utilizarse <em/testflow/. Es un paquete de diagnsticos que da bastante
+ informacin til para producir buen postscript y/o pdf en un sistema
+ &tex;. Se encuentra disponible en
+ <tt>CTAN::/macros/latex/contrib/supported/IEEEtran/testflow</tt>
+</descrip>
+
+<sect1>He encontrado un error en &latex; Cmo lo notifico?
+<!-- ====================================================-->
+ <p>
+ Para notificar errores o problemas se escribe <tt/latex latexbug/ y se enva
+ el informe as generado a <tt/latex-bugs _AT_ rus.uni-stuttgart.de/. Se
+ recomienda previamente leerse las distintas FAQ y pedir ayuda en los
+ distintos foros acerca del problema, y slo entonces, cuando se est seguro
+ que el problema es de &latexe; mandar el informe de error.
+
+<!-- ********************************************************* -->
+<sect>Por qu no consigo ...?
+<!-- ********************************************************* -->
+<sect1>Por qu no salen las imgenes en mi documento?
+<!-- ........................................................... -->
+ <p>
+ La misin de TeX/LaTeX no es entender de grficos. As que cuando se
+ encuentra con uno, este simplemente deja el hueco apropiado, da una
+ indicacin del grfico que hay que insertar (usando un comando
+ <tt>\special</tt>) y continua procesando el documento.
+ <p>
+ No todos los conversores soportan todos los formatos grficos, en el caso de
+ un formato incompatible, el conversor deja el hueco y no representa el
+ grfico. Es conocido que los visualizadores de <em/DVI/ en pantalla no
+ suelen representar bien todos los grficos <em/PS/.
+ <p>
+ Para solucionar esto, use otro conversor que si soporte dichos grficos (por
+ ejemplo use dvips y visualice con gs)
+ <p>
+ Vanse
+ <ref id="special" name="Qu son los \special?">,
+ <ref id="conversores" name="Qu es un conversor (driver)?">,
+ <ref id="tex-dibujos" name="Introduciendo figuras en &latex;">
+ para ms informacin.
+
+<sect1>Por qu no salen los caracteres acentuados si yo los escribo bien?
+<!-- ........................................................... -->
+ <p>
+ En primer lugar debe echarse un vistazo a seccin <ref id="acentos"
+ name="cmo puedo escribir los acentos y dems caracteres extendidos?">.
+ <p>
+ Cuando la entrada de caracteres mediante <tt/inputenc/ no funciona,
+ especialmente en un sistema <em/Linux/, suele ser debido a que por omisin
+ en algunos sistemas <em/Linux/, el fichero se guarda como <tt/utf-8/, por lo
+ que deben seguirse las instrucciones para <tt/utf-8/ que all se
+ detallan. Un sntoma habitual es que saque <tt// y otros caracteres
+ acentuados como <tt/A/ con <tt/~/ seguida de otro caracter extrao.
+ <p>
+ Otras posibilidades seran cambiar la codificacin del fichero con una
+ herramienta como <em/recode/ o <em/iconv/ antes de procesarlo con &latex; o,
+ si se guarda por omisin como <tt/utf-8/, decirle explcitamente si es
+ posible, al editor, la codificacin en debe leer y guardar el fichero en
+ cuestin. Por ejemplo, para <em/{x}emacs/, una primera lnea con
+ <tt/% -*- coding: iso-8859-1 -*-/ hara que el fichero se leyera y guardara
+ siempre como <tt/latin1/. Para otros editores debe consultarse la
+ documentacin para saber si es posible y cmo.
+
+<sect1>Por qu no encuentro el archivo babelbst.tex cuando uso <em/custom-bib/?
+<!-- ........................................................... -->
+<p>
+ La intencin del autor del paquete era que las lenguas de <em/babel/
+ proporcionaran ese archivo, de ah su nombre. Sin embargo, en la prctica
+ pocas lenguas lo proporcionan, aunque entre ellas est spanish. El archivo
+ <em/esbst.tex/ fue pensado para que se pueda utilizar como el
+ <em/babelbst.tex/ que esperan los estilos creados
+ (Vase <ref id="custombib" name="BibTeX en castellano, custom-bib">).
+
+<sect1>Por qu a veces no me da el mismo resultado o incluso errores al procesar un documento en dos sistemas distintos?
+<!-- ........................................................... -->
+<p>
+ O dicho con otras palabras, no se supone que una de las bondades de &latex;
+ es que el fuente es portable al igual que el dvi?
+<p>
+ La respuesta es que lo anterior es cierto, pero con matices. Lo que es
+ portable y universal es el lenguaje &tex;. Sus comandos <em/primitivos/ (los
+ que &tex; tiene definidos intrnsecamente) son utilizables en cualquier
+ mquina. No obstante, como escribir documentos a base de <em/primitivas/ puede
+ resultar extremadamente engorroso, &latex; define otro conjunto de comandos
+ ms amigable, para las tareas ms habituales. Algunos de stos estn en el
+ cuerpo de &latex; y otros en paquetes adicionales
+ -- vase <ref id="paquetes-latex" name="paquetes en &latex;">.
+<p>
+ De este modo, para que un documento sea portable y universal, no basta con que
+ &tex; est instalado en ambas mquinas. Debe tenerse adems el conjunto de
+ macros &latex; (y a ser posible en la misma versin), y el conjunto de todos
+ los paquetes que el documento use (tambin a ser posible en la misma
+ versin). Si las versiones no coinciden pueden producirse efectos secundarios
+ indeseados, aunque esto, por suerte, no es muy frecuente, pues salvo algunas
+ excepciones (<em/babel/, la ms notable) los paquetes intentan mantener la
+ "compatibilidad hacia atrs" (es decir, que las nuevas versiones se comporten
+ de la misma forma que lo hacan las antiguas).
+
+<!-- ********************************************************* -->
+<sect>Preguntas que se van quedando obsoletas
+<!-- ********************************************************* -->
+<sect1>Qu es <tt/FTC/?
+<!-- ........................................................... -->
+<p>
+<tt/FTC/ es un filtro que genera las particiones para el
+castellano. Adems, simplifica enormemente la introduccin
+de acentos. Est descrito en:
+<tscreen><verb>
+@ARTICLE(pepe:wds
+ ,AUTHOR= "Jos{\'e} A. Ma{\~n}as"
+ ,TITLE= "{Word Division in Spanish}"
+ ,JOURNAL= "Comm. ACM"
+ ,YEAR= 1987
+ ,volume= 30
+ ,number= 7
+ ,pages= "612--616"
+ ,month= "July"
+)
+</verb></tscreen>
+Puede conseguirse en:
+<tscreen>
+<htmlurl url="ftp://ftp.dit.upm.es/pub/pepe/ftc" name="ftp://ftp.dit.upm.es/pub/pepe/ftc">
+</tscreen>
+
+<sect1>Qu es ML-&tex;?
+<!-- ================================= -->
+<p>
+ML-&tex; es un conjunto de parches para el WEB de &tex; (hubo tambin versiones
+ para &tex; 2.X) que permiten manejar realmente 256 caracteres
+ internamente y, mediante el primitivo <tt>\charsubdef</tt>,
+ reconstruir esos caracteres mediante combinaciones de otros. Knuth
+ copi masivamente de ML-&tex; para el &tex; 3.X y <tt/spanish.sty/ usa
+ ideas sacadas de ah. ML-&tex; es la mejor solucin, si no se dispone
+ de fuentes extendidas. &tex; 3.X incorpora muchas de las ideas de
+ Ferguson, pero no todas. Los parches para ML-&tex; con &tex; 3.0 son
+ mucho ms pequeos que los antiguos.
+<p>
+Si somos usuarios de DOS, <em/em&tex;/ incorpora ya ML-&tex; sin ms que usar
+ <tt/-ml/ en la lnea de comando al crear el formato.
+<p>
+Si somos usuarios de UNIX, es muy posible que tengamos compilador de C (al menos
+ GCC) y podemos aplicar los cambios nosotros mismos con el <em/web2c/
+ de Karl Berry.
+
+<!-- ********************************************************* -->
+<sect>Informacin sobre &latex; en castellano
+<!-- ********************************************************* -->
+<sect1>El Grupo de Usuarios de &tex; Hispanohablantes (Cervan&tex;)
+<!-- ========================================================== -->
+<sect2>Qu es Cervan&tex;?
+<p>
+Cervan&tex; es el grupo de usuarios de &tex; hispanohablantes, y forma parte de
+los grupos locales asociados al <em/&tex; User Group/.
+<p>
+La asociacin Cervan&tex; busca intercambiar experiencias sobre &tex; y sobre
+sus aplicaciones, y promoverlo de forma adecuada en el mbito hispanohablante.
+<p>
+Estos fines se desarrollan mediante la discusin y la colaboracin en el
+desarrollo de aplicaciones de &tex; y programas asociados; la promocin y el
+fomento de publicaciones relacionadas con &tex;; la organizacin de cursos,
+congresos y seminarios; y la colaboracin e intercambio con todo tipo de
+sociedades, instituciones y editoriales cientficas.
+
+<sect2>Cmo puedo entrar en contacto con el grupo de usuarios?
+<!-- ...................................................... -->
+<p>
+ En este momento la Junta Directiva de <em/Cervan&tex;/ est formada por
+<tscreen><verb>
+PRESIDENTE: Juan Luis Varona presidente@cervantex.org
+SECRETARIO: Roberto Herrero secretario@cervantex.org
+TESORERO: Enrique Melndez tesorero@cervantex.org
+VOCALES: Luis Sanjun y Javier Bezos
+</verb></tscreen>
+ La pgina WWW del grupo Cervan&tex; se encuentra en:
+<quote>
+<htmlurl url="http://www.cervantex.org" name="http://www.cervantex.org">
+</quote>
+ con informacin ms especfica sobre las actividades del grupo en
+<quote>
+<htmlurl url="http://www.cervantex.org/actividades.php"
+ name="http://www.cervantex.org/actividades.php" >
+</quote>
+ La direccin postal del grupo es
+<tscreen><verb>
+CervanTeX
+Apartado de correos 60118 AP
+E-28080 Madrid
+Espaa
+</verb></tscreen>
+
+<sect1>La lista <tt/es-tex/ <label id="lista-estex">
+<!-- ================================= -->
+<p>
+<sect2>Cmo funciona la lista <tt/es-tex/?
+<!-- ....................................... -->
+<p>
+ La lista <tt/es-tex/ es el foro principal de discusin en este idioma. Se
+ trata de una lista cerrada, por lo que es necesario suscribirse a la misma
+ para enviar y recibir mensajes. Aunque es independiente del grupo
+ Cervan&tex;, gran parte de los suscriptores de la lista son miembros del
+ grupo y viceversa. Cervan&tex; recomienda a todas las personas interesadas
+ en &tex; en espaol la suscripcin a esta lista.
+<p>
+ <itemize>
+ <item>
+ Para suscribirse, debe enviarse un mensaje a <tt/LISTSERV@LISTSERV.REDIRIS.ES/
+ que tenga en el cuerpo del mismo
+ <quote>
+ <tt/subscribe ES-TEX/
+ </quote>
+ <item>
+ Para enviar un mensaje a la lista una vez suscrito:
+<tscreen><verb>
+mail ES-TEX@LISTSERV.REDIRIS.ES
+</verb></tscreen>
+ <item>
+ Es muy recomendable que los principiantes con las Listas de Distribucin
+ lean el documento sobre <em/Correcto Uso de las Listas de Distribucin/ que
+ se encuentra en:
+ <quote>
+ <htmlurl url="http://www.rediris.es/list/list-moral.html"
+ name="http://www.rediris.es/list/list-moral.html">.
+ </quote>
+ y no est de ms la lectura del documento <em/Cmo hacer preguntas de manera
+ inteligente/, disponible en
+ <quote>
+ <htmlurl url="http://www.sindominio.net/ayuda/preguntas-inteligentes.html"
+ name="http://www.sindominio.net/ayuda/preguntas-inteligentes.html">
+ <p>
+ <htmlurl url="http://www.catb.org/~esr/faqs/smart-questions.html"
+ name="http://www.catb.org/~esr/faqs/smart-questions.html">.
+ </quote>
+ Para darse de baja de la lista <em/ES-TEX/ debe enviarse a
+ <tt/LISTSERV@LISTSERV.REDIRIS.ES/ un mensaje que contenga en el cuerpo
+<tscreen><verb>
+unsubscribe ES-TEX
+</verb></tscreen>
+<!--
+ Para cambiar la direccin de correo-e suscrita a la lista debe enviarse a
+ <tt/LISTSERV@LISTSERV.REDIRIS.ES/ un mensaje que contenga en el cuerpo
+<tscreen><verb>
+change ES-TEX direccion_antigua
+</verb></tscreen>
+ desde la direccin nueva.
+-->
+ Existen otras muchas opciones, para obtener un listado de las mismas debe
+ enviarse a <tt/LISTSERV@LISTSERV.REDIRIS.ES/ un mensaje que contenga en el
+ cuerpo
+<tscreen><verb>
+HELP
+</verb></tscreen>
+ siendo especialmente interesantes las opciones <em/(NO)MAIL/, que regula
+ si se recibe un mensaje por cada contribucin a <em/ES-TEX/,
+ <em/(NO)REPRO/ que regula si se reciben los mensajes enviados por uno
+ mismo y <em/(NO)ACK/ que regula si se recibe confirmacin de
+ distribucin. Para todas ellas se enva un mensaje que contenga en el
+ cuerpo <tt/set ES-TEX opcion/, por ejemplo
+<tscreen><verb>
+set ES-TEX ACK
+set ES-TEX NOACK
+</verb></tscreen>
+ Para obtener informacin sobre el uso de las listas de RedIris tambin
+ puede visitarse la pgina
+ <htmlurl url="http://www.rediris.es/list/utilizacion.es.html"
+ name="http://www.rediris.es/list/utilizacion.es.html">
+ o sobre listserv en general (en ingls)
+ <htmlurl url="http://www.rediris.es/list/doc/user.html"
+ name="http://www.rediris.es/list/doc/user.html">
+ o ver la gua de referencia (tambin en ingls)
+ <htmlurl url="http://www.rediris.es/list/comandos/info-refcard.html"
+ name="http://www.rediris.es/list/comandos/info-refcard.html">
+ <p>
+ Por favor, NO mandar peticiones de suscripcin o des-suscripcin a la
+ propia lista (<tt/es-tex/).
+ </itemize>
+
+ <!-- ........................................................... -->
+ <sect2>Cuando contesto a alguien de la lista, quin recibe la respuesta? El que mand el mensaje o la lista entera?
+ <!-- .................................................................-->
+ <p>
+ Por omisin, se contesta a la lista entera, salvo que el remitente
+ incluya un campo <tt/Reply-To/ explcito.
+
+ <!-- ........................................................... -->
+ <sect2>Se archiva en algn sitio la lista <tt/es-tex/?
+ <!-- ........................................................... -->
+ <p>
+ S, en
+ <htmlurl url=" http://listserv.rediris.es/archives/es-tex.html"
+ name=" http://listserv.rediris.es/archives/es-tex.html">
+
+ <!-- ........................................................... -->
+ <sect2>Recibo correo de muchas listas. Cmo puedo filtrar lo que venga de la lista <tt/es-tex/?
+ <!-- ........................................................... -->
+ <p>
+ Todo lo que viene de <tt/es-tex/ tiene actualmente un campo de la
+ forma:
+<tscreen><verb>
+Sender: Usuarios hispanohablantes de TeX &lt;ES-TEX@LISTSERV.REDIRIS.ES&gt;
+</verb></tscreen>
+ Si utilizamos un filtro llamado <em/procmail/ (es software libre),
+ podemos poner las siguientes tres lneas en el archivo de
+ configuracin <tt/.procmailrc/:
+<tscreen><verb>
+:0
+* ^Sender:.*&lt;ES-TEX@LISTSERV.REDIRIS.ES&gt;
+spanish-tex
+</verb></tscreen>
+ y todo lo que venga de <em/es-tex/ se ir solito al archivo
+ <tt/spanish-tex/.
+ <p>
+ Es posible que algunos clientes de correo que permitan filtrado de
+ los mensajes a partir de sus cabeceras puedan intentar verificar si
+ el campo <em/Sender/ contiene
+ <tt>&lt;ES-TEX@LISTSERV.REDIRIS.ES&gt;</tt> o algo parecido, pero
+ eso debe comprobarse en cada caso.
+
+ <!-- ........................................................... -->
+ <sect2>Cmo es que hay tanta gente de fuera de Espaa en la lista?
+ <!-- ........................................................... -->
+ <p>
+ El tema previsto de esta lista era el uso de &tex; para la
+ produccin de documentos en castellano, no para discutir en
+ castellano acerca de &tex; ni el uso de &tex; en Espaa. Esto no es
+ rgido, pero no pretende ser una lista espaola. No se excluyen
+ tampoco discusiones acerca de las otras lenguas espaolas (cataln,
+ euskera, gallego, ingls, :-) pero gran parte de la audiencia no
+ estar interesada.
+
+ <sect1>Las listas <tt/spanish-tex/ y <tt/sptex/
+ <!-- ================================= -->
+ <p>
+ <em/ATENCIN/. Las listas <em/spanish-tex/ y <em/sptex/ estn
+ obsoletas. En su lugar debe utilizarse la lista <em/es-tex/.
+ Vase <ref id="lista-estex" name="lista es-tex">.
+
+ <sect2>Se archiva en algn sitio la lista <tt/spanish-tex/?
+ <!-- ................................................... -->
+ <p>
+ Antiguamente, en la siguiente direccin se archivaban los mensajes
+ de la lista <tt/spanish-tex/
+ <quote>
+ <htmlurl url="http://majordomo.eunet.es/listserv/spanish-tex/"
+ name="http://majordomo.eunet.es/listserv/spanish-tex/">
+ </quote>
+ junto con las instrucciones de acceso a la lista. Sin embargo, hace
+ tiempo que no est operativa.
+
+ <sect2>Se archiva en algn sitio la lista <tt/sptex/?
+ <!-- ........................................................ -->
+ <p>
+ S, en <htmlurl url="http://www2.cica.es/ListasD/sptex/"
+ name="http://www2.cica.es/ListasD/sptex/">, al menos temporalmente.
+
+ <sect1>El grupo de noticias <tt/es.comp.lenguajes.tex/
+ <!-- ============================================= -->
+ <p>
+ Una fuente de informacin alternativa es el grupo de noticias
+ <htmlurl url="es.comp.lenguajes.tex" name="es.comp.lenguajes.tex">,
+ aunque tiene bastante menos trfico que la lista de correo. Este es el
+ grupo de noticias principal sobre &tex; en espaol.
+
+ <sect1>El grupo de noticias <tt/es.eunet.spanish-tex/
+ <!-- ============================================ -->
+ <p>
+ Antes exista una pasarela (<em/gateway/) entre la lista y el grupo de
+ noticias <tt/es.eunet.spanish-tex/, pero actualmente no
+ funciona. Adems este grupo ya no es de acceso general, sino que es
+ propio de la red <tt/eunet/.
+
+ <!-- ********************************************************* -->
+ <sect> Meta-preguntas (preguntas sobre esta FAQ):
+ <!-- ********************************************************* -->
+
+ <sect1> Cul es la historia de esta FAQ?
+ <!-- ================================= -->
+ <p>
+ La primera versin de esta FAQ se la debemos a Julio Snchez que
+ recopil preguntas y respuestas a partir de las discusiones habidas en
+ la lista <tt/spanish-tex/.
+ <p>
+ Posteriormente Santiago Vila <tt/(sanvila _AT_ unex.es)/ se hizo cargo
+ de la FAQ, aadiendo ms preguntas y pasndola a <em/texinfo/.
+ <p>
+ Ms recientemente, Agustn Martn <tt/(agustin.martin _AT_
+ hispalinux.es)/ se ha hecho cargo de ella en el 99 y la ha pasado a
+ SGML, con la misma intencin con la que Santiago la pas a texinfo,
+ extraer de forma sencilla versiones en distintos formatos.
+ <p>
+ Esta lista de preguntas y respuestas est muy verde, y actualmente
+ sigue siendo algo catica. Se ruega algo de <em>intolerancia
+ activa</em>, es decir, siempre que se vea algo mal, comunquese al
+ coordinador de la FAQ. Se aceptan cambios, correcciones (incluso
+ ortogrficas o de estilo), adiciones, etc. Ni Julio Snchez ni
+ Santiago Vila se hacen cargo en este momento de la FAQ, as que por
+ favor no le mandis las preguntas a ellos, sino a la persona que en
+ este momento se hace cargo de la FAQ.
+
+ <sect1>Quin coordina actualmente la FAQ?
+ <!-- ================================= -->
+ <p>
+ El coordinador actual y a quien deben enviarse las sugerencias acerca
+ de esta FAQ es: Agustn Martn Domingo, <tt/agustin.martin _AT_ hispalinux.es/
+ <p>
+ Se ruega especificar en la cabecera del mensaje FAQ-CervanTeX. Por
+ favor, para dudas generales dirigirse a la lista de correo o al foro
+ de noticias. Utilizar esta direccin exclusivamente para asuntos
+ relacionados con la FAQ.
+
+ <sect1>Agradecimientos
+ <!-- ================================= -->
+ <p>
+ Para hacer esta FAQ se han utilizado, adems de los originales de
+ Julio Snchez y Santiago Vila las FAQ del grupo de noticias
+ <tt/comp.text.tex/ y la <em/New &tex; FAQ/, versin de la anterior
+ realizada por el grupo de usuarios de &tex; del Reino Unido. La
+ versin <em/html/ de esta FAQ con un buscador CGI
+ (<htmlurl name="http://www.tex.ac.uk/cgi-bin/texfaq2html"
+ url="http://www.tex.ac.uk/cgi-bin/texfaq2html">) tambin ha sido de
+ gran ayuda. Asimismo se han utilizado multitud de mensajes de las
+ listas de correo y grupos de noticias relacionados con &tex; a cuyos
+ autores agradezco sus ideas y contribuciones.
+ <p>
+ Fernando M. Fournon Gonzlez Barcia <tt/(furny _AT_ wd.estec.nl)/ y
+ Jess M. Gonzlez Barahona <tt/(jgb _AT_ gsyc.inf.uc3m.es)/ han
+ proporcionado las citas de las publicaciones de la Real Academia y del
+ diccionario de Mara Moliner. La seccin acerca de las funciones
+ matemticas en castellano se la debemos a Juan Luis Varona
+ <tt/(jvarona _AT_ dmc.unirioja.es)/ y las de postscript y PDF a
+ Enrique Melendez Asensio <!-- <ema _AT_ csn.es> -->. Adems se han
+ tomado muchos elementos (buena parte de las secciones de libros en
+ ingls y de ventajas y desventajas de &latex;) de las pgina sobre
+ &latex; de Antonio Gonzlez, de la Universidad de Sevilla
+ (<htmlurl url="http://www.esi.us.es/~gonfer/tex.html"
+ name="http://www.esi.us.es/~gonfer/tex.html">)
+ y otros cuantos de la pgina de Martn Pavn
+ (<htmlurl url="http://mate.dm.uba.ar/~mpavon/tex.html"
+ name="http://mate.dm.uba.ar/~mpavon/tex.html">)
+
+ <sect1>Dnde encuentro la versin ms reciente de esta FAQ?
+ <!-- =============================================== -->
+ <p>
+ La versin ms reciente de esta FAQ est disponible en el directorio
+<quote>
+<htmlurl url="http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX/" name="http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX/">
+</quote>
+ en una amplia variedad de formatos. Se puede acceder a travs de la pgina
+<quote>
+<htmlurl url="http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX-main.html" name="http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX-main.html">
+</quote>
+
+ <sect1>Dnde puedo encontrar otras FAQ, aunque sea en otros idiomas?
+ <!-- ======================================================== -->
+ <p>
+ Adems de la FAQ en castellano existen FAQ en otros idiomas que, si se
+ salva la barrera del lenguaje pueden ser de utilidad adicional. Sin
+ duda en ellas existen elementos que podran entrar bien en esta FAQ,
+ as que todo aquel que vea una pregunta de gran inters que est en
+ una de ellas y no en la FAQ en castellano est invitado a traducirla y
+ envirsela al responsable de esta FAQ. Las FAQ en otros idiomas ms
+ interesantes son las siguientes
+ <itemize>
+ <item>
+ El grupo de usuarios de &tex;/&latex; del Reino Unido mantiene una
+ excelente FAQ en ingls que puede encontrarse en <em/CTAN/ en el
+ directorio <tt>CTAN:usergrps/uktug/faq</tt>. La pgina web de la
+ UK-FAQ
+ <htmlurl name="http://www.tex.ac.uk/cgi-bin/texfaq2html"
+ url="http://www.tex.ac.uk/cgi-bin/texfaq2html"> tiene adems un
+ buscador CGI para facilitar las consultas. Existe una muy
+ interesante FAQ visual, es decir, un documento donde aparecen
+ destacado ciertos elementos con hiperenlaces a la FAQ
+ inglesa. Realmente merece la pena echarle un vistazo. Se encuentra en
+ <htmlurl name="http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf"
+ url="http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf">
+ </item>
+ <item>
+ Asimismo, el grupo alemn <em/DANTE/ de usuarios de &tex;/&latex;
+ mantiene su FAQ (en alemn) que puede encontrarse en el <em/CTAN/
+ en el directorio <tt>CTAN:help/de-tex-faq</tt>.
+ </item>
+ <item>
+ Aunque congelada desde hace algn tiempo, existe una FAQ en
+ francs en <tt>CTAN:help/LaTeX-FAQ-francaise</tt>
+ </item>
+ </itemize>
+ <!--
+<sect1>Por qu la versin original de este documento est escrito con SGML y no &latex;?
+<p>
+ Fundamentalmente, porque permitiendo tambin escribir documentacin
+estructurada, SGML est especialmente pensado para ser convertido a muchos
+formatos, y prefiero sacrificar el aspecto final en aras de una ms fcil
+conversin.
+-->
+ </article>
+
+<!--
+Local Variables:
+ mode: sgml
+ ispell-local-dictionary: "castellano8"
+ coding: iso-8859-1
+ sgml-indent-data: t
+ sgml-indent-step: 2
+End:
+-->
+
+<!--
+
+LocalWords: Donald Knuth WYSIWYG WEB plain METAFONT Public License CTAN
+LocalWords: Copyleft Leslie Lamport AMS Michael Spivak Snchez Sevilla
+LocalWords: Addison Wesley postscript dviwin yap winview Kjetil name PS
+LocalWords: Halvorsen Gonzlez knuth Mittelbach Popineau Windows Schenk
+LocalWords: dvips PostScript EPS mathbbm binom amsmath unix ghostview PC
+LocalWords: pstops psbook psnup psselect slides seminar foiltex pdfslide
+LocalWords: pdfscreen foils pdflatex crop colortbl subfigure minipage DC
+LocalWords: epslatex cancel gateway texinfo Mara Moliner Varona Asensio
+LocalWords: agmartin FAQ sgml Kurzbeschreibung Partl Schlegl Hyna Seidel
+LocalWords: Rioja Ortegn Cascales Lucas Saorn Jose Pallars Ruiz Daly
+LocalWords: Pedreo Guilln Greenberg Roberts Southern Queensland Rahtz
+LocalWords: Goosens Samarin Goossens DVI Cork shareware Slackware Windvi
+LocalWords: Fabrice fptex miktex emacs inputenc documentclass begin Max
+LocalWords: document Macintosh babel Daz Aurion Vzquez Arbortext EC ML
+LocalWords: accent Bezos RAL spanish Carlisle newcommand renewcommand SW
+LocalWords: def ispell Zaccone Excalibur ftp amspell makeindex esindex
+LocalWords: xindy Roger Kehr Darmstadt web linux Gutenberg TUG Johannes
+LocalWords: Braams Hubert unicode includegraphics eps usepackage parsep
+LocalWords: geometry enlargethispage chngpage itemsep bibtopic sty url
+LocalWords: graphics psfig Goel Keith Reckdahl Companion picture epic
+LocalWords: pstricks MetaPost metapost gnuplot pdf pstoedit graphicx RTF
+LocalWords: psfrag overpic picinpar float Distiller dvipdfm hyperref rtf
+LocalWords: Fojtik Rich Text Format tex Robert Lupton latex Erwin Wechtl
+LocalWords: psutils ghostscript fancyvrb eurofont circ textdegree Vila
+LocalWords: textcomp charsubdef Ferguson TEXMF Rodrguez equation amstex
+LocalWords: subseccin desplegables personalizable Debian HOMETEXMF Wine
+LocalWords: TEXMFLOCAL TEXMFMAIN mktexlsr initexmf tetex windows include
+LocalWords: includeonly RedIris listserv elipsis superndices Bogot dvi
+LocalWords: redefinicin Colombia descatalogado freeware guionado pdftex
+LocalWords: maquetacin desplegable Fernndez lilypond beamer maple
+LocalWords: Martnez
+
+ -->
diff --git a/help/es-tex-faq/FAQ-CervanTeX.tex b/help/es-tex-faq/FAQ-CervanTeX.tex
new file mode 100644
index 0000000000..d4f3449355
--- /dev/null
+++ b/help/es-tex-faq/FAQ-CervanTeX.tex
@@ -0,0 +1,6634 @@
+\documentclass[a4paper]{article}
+\usepackage{ifpdf}
+\usepackage{linuxdoc-sgml}
+\usepackage{qwertz}
+\usepackage{url}
+\usepackage[latin1]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage[colorlinks=true,urlcolor=blue,linkcolor=blue]{hyperref}
+\pdfcompresslevel=9
+\usepackage[spanish]{babel}
+\usepackage{epsfig}
+\usepackage{null}
+\def\addbibtoc{
+\addcontentsline{toc}{section}{\numberline{\mbox{}}\relax\bibname}
+}%end-preamble
+\setcounter{page}{1}
+\usepackage{times} \selectlanguage{spanish} \usepackage{t1enc} \AtBeginDocument{\gdef~{\nobreakspace{}}\catcode`\"=12}
+\title{FAQ de Cervan\TeX{}}
+\author{Cervan\TeX{}}
+\date{ Versi\'on 1.97 de 2006-05-09 (15:12:22)
+ }
+\abstract{ Esta es la lista de preguntas y respuestas frecuentes del grupo de usuarios
+ hispanohablantes de \TeX{}/\LaTeX{} Cervan\TeX{}. Est\'a basada en las
+ preguntas que se repiten con frecuencia en los distintos foros y en
+ algunas contribuciones adicionales interesantes. Aunque todas ellas son
+ preguntas razonables, especialmente para un ne\'ofito, resulta un poco
+ {\itshape repetitivo\/} verlas aparecer continuamente en los distintos foros de
+ discusi\'on sobre \TeX{}/\LaTeX{}. Por esta raz\'on se han intentado reunir en
+ esta FAQ. Se ruega echarle un vistazo antes de preguntar en la lista de
+ correo o en el grupo de noticias cosas que ya se han preguntado y
+ respondido m\'ultiples veces y que est\'an en esta FAQ.
+ }
+
+
+\begin{document}
+\maketitle
+\tableofcontents
+
+\section{Qu\'e son \TeX{} y sus programas hermanos?
+ }
+
+
+\subsection{Qu\'e es \TeX{}?
+ }
+
+\TeX{} es un sistema de composici\'on de textos de alta calidad creado
+por Donald E. Knuth, dirigido en particular a aqu\'ellos textos que
+contienen una gran cantidad de expresiones matem\'aticas. No debe
+pensarse en \TeX{} como un procesador de palabras del tipo WYSIWYG, un
+archivo {\ttfamily tex} es un archivo {\ttfamily ASCII} donde est\'a el texto que
+deseamos imprimir
+junto con determinadas instrucciones sobre como debe ser tratado, que
+debe ser procesado por un compilador (el programa \TeX{}). \'Este
+devuelve un archivo que es independiente de la plataforma y que es el
+que finalmente se transformar\'a al lenguaje de impresora y se
+imprimir\'a.
+
+
+Para escribir \TeX{} Knuth desarroll\'o un sistema de {\itshape programaci\'on
+ilustrada\/}
+denominado WEB. Las fuentes WEB de \TeX{} est\'an disponibles
+gratuitamente, lo mismo que herramientas para convertir el original en
+WEB en un programa que pueda compilarse y un texto que pueda
+imprimirse. El sistema WEB proporciona herramientas para compilar
+\TeX{} en distintos sistemas operativos.
+
+\TeX{} en s\'\i{} es un procesador de macros, con una alta capacidad de
+programaci\'on. Utilizar \TeX{} puro reviste una cierta dificultad, por
+lo que Knuth suministr\'o una serie de macros para \TeX{} a las que se
+denomin\'o {\itshape plain \TeX{}\/}. Estas macros son el conjunto m\'\i{}nimo de
+macros que se pueden utilizar de forma eficaz con \TeX{} e incluyen
+algunos ejemplos de uso de \'ordenes \TeX{} de alto nivel. Cuando alguien
+afirma programar en \TeX{} normalmente se refiere a que lo hace en
+{\itshape plain \TeX{}\/}
+
+
+
+
+\subsection{Por qu\'e debo asegurarme de usar \TeX{} 3.X?
+ }
+
+Bueno, hace unos a\~nos (en el ***), diversas personas (y la existencia de
+ML-\TeX{} :-) convencieron a Knuth de que el soporte que \TeX{}
+proporcionaba a otros idiomas era insuficiente. As\'\i{} que lo modific\'o de
+la siguiente manera:
+\begin{itemize}
+\item
+Soporte total a los 8 bits. \TeX{} puede ahora leer los 256 diferentes
+c\'odigos. Los nuevos caracteres son c\'odigos utilizables como
+cualquier otro. Antes hab\'\i{}a algo, pero no bastante. Ahora podemos
+hacer que {\ttfamily \^{}\^{}e1} sea la {\ttfamily \'a}.
+\item \TeX{} soporta ahora 256 tablas de partici\'on simult\'aneamente.
+Puedes escribir:
+\begin{quotation}
+... there is a difference between especially and
+$\{${\ttfamily $\backslash$language$\backslash$spanish} especialmente$\}$ in that...
+\end{quotation}
+
+y \TeX{} compondr\'a el p\'arrafo con las reglas de ingl\'es, menos
+{\itshape especialmente\/} que lo har\'a con las del castellano.
+
+\item Dos nuevas macros {\ttfamily $\backslash$lefthyphenmin} y
+{\ttfamily $\backslash$righthyphenmin} que controlan el tama\~no del trozo m\'\i{}nimo
+que se puede dejar al partir palabras. Previamente estaban fijos a
+2 y 3, respectivamente.
+Pero lo fundamental es que \TeX{} 2.X no existe ya. Hay que
+cambiar tarde o temprano. No hay parches ni arreglos para \TeX{}
+2.X.
+
+Por cierto, la versi\'on actual es la 3.14159, y la versi\'on actual
+de METAFONT es la 2.718. La \'ultima versi\'on de \TeX{} ser\'a la
+versi\'on {\itshape pi\/}
+(como \'ultima voluntad de Donald Knuth), y ya no habr\'a m\'as
+cambios. Y el \'ultimo METAFONT ser\'a versi\'on {\itshape e\/}.
+
+\end{itemize}
+
+
+
+
+
+\subsection{Si \TeX{} es tan bueno, por qu\'e es gratuito?\label{tex-gratis}
+ }
+
+Porque Knuth lo decidi\'o as\'\i{}, y no parece molestarle que otros ganen dinero
+vendiendo productos y servicios basados en \TeX{}. De hecho, aunque
+algunas herramientas que se usan junto a \TeX{} se ofrecen bajo la
+{\itshape GNU General Public License (Copyleft)\/}, \TeX{} en s\'\i{} ni siquiera
+tiene esa restricci\'on. La \'unica restricci\'on impuesta por Knuth es que
+debe dar el mismo resultado en todas las implementaciones, para
+garantizar la absoluta portabilidad de los documentos escritos con
+\TeX{}.
+
+Algunas empresas ofrecen implementaciones comerciales de \TeX{}/\LaTeX{} con
+elementos propios (v\'ease la secci\'on \ref{tex-de-pago} {(Implementaciones comerciales)})
+
+
+
+
+\subsection{Qu\'e es \LaTeX{}?
+ }
+
+\LaTeX{} es un paquete de macros para \TeX{}, originalmente escrito por
+Leslie
+Lamport para proporcionar un sistema de procesamiento de documentos
+m\'as simple de uso que \TeX{}, pero con toda su potencia. \LaTeX{}
+proporciona una serie de \'ordenes para describir la estructura del
+documento, de forma que el usuario final no deba pensar mucho en la
+presentaci\'on. Mediante distintas clases de documentos y paquetes
+adicionales, el mismo documento puede producirse con muchos diferentes
+aspectos.
+
+
+
+
+\subsection{Qu\'e es \LaTeXe{}?, Por qu\'e debo usarlo si me va bien con el otro (\LaTeX{}209)?
+ }
+
+\LaTeXe{} es la nueva versi\'on est\'andar de \LaTeX{}, preparada y
+mantenida por el
+equipo del proyecto \LaTeX{}3. Es la versi\'on actual de \LaTeX{} y est\'a
+disponible desde cualquier punto CTAN, en
+
+\begin{tscreen}
+\begin{verbatim}
+CTAN:macros/latex
+\end{verbatim}
+\end{tscreen}
+
+Desde que es oficial, \LaTeX{} = \LaTeXe{} y el otro ahora se llama
+\LaTeX{} 2.09 y est\'a obsoleto.
+
+\LaTeXe{} es compatible hacia atr\'as con \LaTeX{}209, pero incluye toda
+una serie
+de caracter\'\i{}sticas nuevas.
+
+Hay una raz\'on de peso para no usar \LaTeX{} 2.09: Solamente \LaTeX{} est\'a
+mantenido, lo cual quiere decir (entre otras cosas) que si encontramos
+un error hay gente a quien dec\'\i{}rselo y puede que lo arreglen, mientras
+que si tenemos problemas con \LaTeX{} 2.09 nadie nos har\'a caso, porque
+\LaTeX{} 2.09 ya no va a cambiar jam\'as.
+
+
+
+
+\subsection{Qu\'e son los paquetes de la AMS (AMS-\TeX{}, AMS-\LaTeX{})?
+ }
+
+AMS-\TeX{} es un paquete de macros para \TeX{}. Escrito originalmente
+por Michael
+Spivak para la Sociedad Americana de Matem\'aticas (AMS) entre 1983 y
+1985. Est\'a basado en {\itshape plain \TeX{}\/}, pero proporciona m\'as medios
+para producir f\'ormulas matem\'aticas de aspecto profesional con menor
+esfuerzo por parte de los autores, con un gran cuidado en aspectos
+como el tama\~no y la posici\'on de las f\'ormulas. Entre los aspectos
+tratados se encuentran las ecuaciones de m\'as de una l\'\i{}nea, la
+numeraci\'on de ecuaciones, los puntos de elipsis, las matrices, los
+acentos dobles, sub y super\'\i{}ndices en varios niveles, as\'\i{} como otras
+cosas.
+
+Seg\'un fue aumentando la popularidad de \LaTeX{} la AMS desarroll\'o
+AMS-\LaTeX{},
+que consiste en una colecci\'on de clases y paquetes para \LaTeX{} que
+ofrece a los autores la funcionalidad de AMS-\TeX{}.
+
+
+
+
+\subsection{Qu\'e es METAFONT?
+ }
+
+Donald Knuth escribi\'o METAFONT al mismo tiempo que \TeX{}. Mientras
+\TeX{} define
+la colocaci\'on de los elementos en una p\'agina, METAFONT define c\'omo son
+estos elementos, sus tama\~nos y c\'omo se crean.
+
+El lenguaje utilizado por METAFONT para definir tipos permite describir
+distintas cosas, la geometr\'\i{}a del grafo, las propiedades del elemento
+de impresi\'on, informaci\'on adicional que permita distinguir entre
+distintos tama\~nos del mismo tipo, o diferencias entre dos tipos que
+pertenecen a la misma o distinta familia.
+
+Aunque Knuth y otros han dise\~nado un buen n\'umero de tipos utilizando
+METAFONT,
+el dise\~no de tipos en general y en particular con METAFONT es un \'area
+muy especializada que nunca deber\'a abordar el usuario
+normal. Simplemente METAFONT deber\'a estar instalado para cuando \TeX{}
+quiera generar copias de nuevos tipos.
+
+
+
+
+\section{Qu\'e ventajas e inconvenientes tiene \TeX{}/\LaTeX{}?
+ }
+
+
+\subsection{Ventajas frente a otros procesadores.
+ }
+
+Adem\'as de las ventajas que aqu\'\i{} se describen, en la p\'agina
+\ifpdf
+\href{http://www.cudenver.edu/~hgreenbe/courses/texinfo/wordvslatex.html}{http://www.cudenver.edu/\~{}hgreenbe/courses/texinfo/wordvslatex.html}
+\else
+\onlynameurl{http://www.cudenver.edu/\~{}hgreenbe/courses/texinfo/wordvslatex.html}
+\fi
+
+se recopilan (en ingl\'es) buen numero de mensajes con una informaci\'on
+detallada de las razones que han llevado a toda una serie de personas a
+utilizar \LaTeX{}
+\begin{description}
+\item[Funciona y es estable y multiplataforma.] \mbox{}
+
+Tan simple como eso, \LaTeX{} no se {\itshape cuelga\/}, el formato de los
+archivos es mucho m\'as estable que en otros procesadores y
+cualquier cambio es primero profundamente meditado y despu\'es
+profusamente documentado, existen implementaciones para distintas
+plataformas y en todas el resultado es exactamente el mismo (si se
+tienen los mismos estilos y tipos, claro).
+
+
+
+\item[Alta calidad en la edici\'on de ecuaciones.] \mbox{}
+
+Esta es siempre la raz\'on \'ultima por la que un usuario cient\'\i{}fico
+se inclina hacia \LaTeX{}. Este procesador ajusta los tama\~nos de
+par\'entesis, integrales, sub\'\i{}ndices y super\'\i{}ndices, alinea los
+elementos de las matrices, construye cajas, etc.
+
+
+
+\item[\LaTeX{} permite redactar f\'acilmente documentos estructurados.] \mbox{}
+
+A trav\'es de distintas clases de documento y de su conjunto de
+macros, \LaTeX{} posibilita escribir textos dividi\'endolos en
+cap\'\i{}tulos, secciones, subsecciones, controlando en todo momento la
+numeraci\'on y las referencias cruzadas. Construye \'\i{}ndices de
+contenidos, tablas o figuras. Ajusta los tama\~nos y tipos de letras
+seg\'un la parte del documento en que se hallen.
+
+
+
+\item[Facilidad en la construcci\'on de macros y \'ordenes.] \mbox{}
+
+A poco de comenzar a usar este procesador, el usuario se encuentra
+definiendo o redefiniendo \'ordenes para que \'estas se ajusten a sus
+preferencias personales. Por ejemplo, es posible que una
+determinada expresi\'on aparezca repetidas veces en el texto. Nada
+mas f\'acil que definir una orden que reemplace a todo un bloque. O
+bien, es posible que no guste la forma en que \LaTeX{} numera las
+p\'aginas. Una redefinici\'on al principio del documento permite
+cambiar esto.
+
+
+
+\item[Se escribe en ASCII.] \mbox{}
+
+Esto, que al principio puede parecer un inconveniente (ya que
+implica teclear mucho m\'as) se torna en ventaja al cabo del
+tiempo. Por un lado permite incrementar la velocidad de escritura
+(pues no hay que andar utilizando rat\'on o men\'us), por otro
+facilita el uso de cualquier editor de texto (no contiene
+caracteres de control) y permite su transmisi\'on por correo
+electr\'onico (puede escribirse en ASCII de 7 bits). Esto hace que
+muchas revistas cient\'\i{}ficas admitan art\'\i{}culos escritos en \LaTeX{},
+enviados por {\itshape e-mail\/}. Ellos lo procesan en el lugar de
+destino, hacen los cambios necesarios y lo imprimen.
+
+
+
+\item[Es gratis] \mbox{}
+
+Pues eso. Para ver porqu\'e v\'ease la secci\'on
+\ref{tex-gratis} {(Porqu\'e \TeX{} es gratis?)}. A pesar de
+ello, existen tambi\'en implementaciones comerciales.
+
+
+
+\end{description}
+
+
+
+
+
+\subsection{Inconvenientes o m\'as bien, cu\'ales son las cr\'\i{}ticas m\'as habituales?
+ }
+
+\begin{description}
+\item[Es muy dif\'\i{}cil.] \mbox{}
+
+A diferencia de los procesadores visuales o {\itshape WYSIWYG\/}, que pueden
+usarse casi
+desde el primer d\'\i{}a con resultados aceptables, \LaTeX{} requiere un
+periodo de aprendizaje antes de conseguir los primeros
+frutos. Incluso cuando ya se es un usuario medio o avanzado,
+siempre es conveniente tener cerca un manual o un \LaTeX{}perto, al
+que preguntarle.
+
+Este proceso de iniciaci\'on consiste principalmente en aprenderse
+las \'ordenes
+esenciales. Despu\'es le siguen \'ordenes secundarias.
+
+M\'as tarde, puede uno aprender a programar en este
+lenguaje. Llegado ese punto se
+puede dar el siguiente salto, atacar el {\itshape plain-\TeX{}\/} o incluso
+el \TeX{}, para introducir \'ordenes de muy bajo nivel, pero esto muy
+rara vez lo necesitar\'a un usuario normal. Estas dos ultimas fases
+s\'olo son precisas si uno est\'a interesado en los intr\'\i{}ngulis del
+sistema y los intr\'\i{}ngulis de \LaTeX{} se le quedan cortos.
+
+La contrapartida de este esfuerzo es que cuando se trabaja con
+\LaTeX{} y se
+compara el resultado con lo obtenido con otros procesadores, la
+salida de \'estos \'ultimos parece {\itshape "poco seria"\/} en cuanto se
+exigen f\'ormulas matem\'aticas. Algo como los dientes, que duelen al
+salir, pero luego se hacen imprescindibles.
+
+
+
+\item[No se ven los resultados hasta que se compila el archivo.] \mbox{}
+
+Una de las decepciones que sufre el usuario novato es que no ve los
+frutos de su
+trabajo hasta que compila. Como suelen aparecer errores de
+compilaci\'on, esto suele ser frustrante (aparte de conllevar una
+p\'erdida de tiempo). La \'unica soluci\'on es armarse de paciencia. Con
+el tiempo, los errores disminuyen y, simult\'aneamente, se aprende a
+procesar de cabeza, por lo que no se necesita hacer una
+visualizaci\'on para saber como va a quedar.
+
+De todas formas, \LaTeX{} no est\'a especialmente dirigido a los
+aspectos puramente
+est\'eticos de cada p\'agina en concreto, sino a los estructurales del
+documento. Si uno est\'a interesado estrictamente en la est\'etica
+(por ejemplo, porque trabaja en la autoedici\'on), \LaTeX{} no es el
+procesador adecuado. \'Este basa la belleza de los documentos
+creados m\'as en la claridad, en el buen criterio y en una est\'etica
+agradable que en la posibilidad de hacer f\'acilmente dise\~nos
+rebuscados para cada p\'agina.
+
+Existen, no obstante, soluciones intermedias entre \LaTeX{} y los
+procesadores
+WYSIWYG. As\'\i{}, el \TeX{}tures de los Mac, el {\itshape xdvi\/} de las
+{\itshape X-Window\/} bajo {\itshape Unix\/} o los {\itshape dviwin\/}, {\itshape yap\/} o
+{\itshape winview\/} de los PC's permiten mantener en pantalla el archivo
+que se est\'a editando y la visualizaci\'on del \'ultimo, lo cual
+facilita la correcci\'on de los documentos.
+
+
+
+\item[No permite introducir im\'agenes.] \mbox{}
+
+Esta acusaci\'on habitual no es en absoluto cierta. Simplemente hay
+que ser
+conscientes de los medios de visualizaci\'on e impresi\'on de que
+disponemos y obrar en consecuencia. V\'ease la secci\'on
+\ref{tex-dibujos} {(Introduciendo figuras en \LaTeX{})}
+
+
+
+Lo que no debe olvidarse nunca es que tanto \TeX{} como \LaTeX{}
+est\'an pensados como lenguajes de composici\'on de documentos, no de
+autoedici\'on. A cada cual lo suyo.
+
+
+
+\item[No tiene variedad de tipos (fuentes)] \mbox{}
+
+Es cierto que los tipos CM originalmente desarrollados por Knuth son
+limitados
+en cantidad y variedad, por lo que a medida que \LaTeX{} se
+difund\'\i{}a han aumentado las demandas de m\'as tipos para usos
+diversos. Aunque el crecimiento es todav\'\i{}a lento, existe una gran
+cantidad de tipos disponibles en el CTAN en:
+
+\begin{tscreen}
+\begin{verbatim}
+CTAN:fonts
+\end{verbatim}
+\end{tscreen}
+
+En las versiones para salidas {\itshape postscript\/} si es posible el uso
+de cualquier tipo, pero no se garantiza que las ecuaciones
+mantengan la calidad requerida.
+
+\end{description}
+
+
+
+
+
+\section{Qu\'e documentaci\'on hay disponible sobre \TeX{}/\LaTeX{}?
+ }
+
+Adem\'as de las referencias que aqu\'\i{} se citan, puede consultarse la
+secci\'on de manuales en las p\'aginas de {\itshape Cervan\TeX{}\/},
+\ifpdf
+\href{http://www.cervantex.org/manuales.php}{http://www.cervantex.org/manuales.php}
+\else
+\onlynameurl{http://www.cervantex.org/manuales.php}
+\fi
+
+
+
+\subsection{Tutoriales de \LaTeX{} en castellano.\label{es-tutores}
+ }
+
+\begin{description}
+\item[Una descripci\'on de \LaTeX{}] \mbox{}
+
+ Tom\'as Bautista {\ttfamily (bautista \_AT\_ cma.ulpgc.es)}
+ha escrito un documento titulado {\itshape Una descripci\'on de \LaTeX{}\/}
+(basado inicialmente en {\itshape \LaTeX{}-Kurzbeschreibung\/}, de H. Partl,
+E. Schlegl e
+I. Hyna), donde se han introducido algunas notas espec\'\i{}ficas de la
+implementaci\'on del estilo {\ttfamily spanish.sty} desarrollado por
+J. S\'anchez. Este documento se encuentra en CTAN (en
+{\ttfamily CTAN:documentation/short/spanish}) y la versi\'on m\'as
+actualizada est\'a siempre en
+\begin{quotation}
+\ifpdf
+\href{ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/}{ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/}
+\else
+\onlynameurl{ftp://ftp.iuma.ulpgc.es/pub/tex/latex2e/doc/ldesc2e/}
+\fi
+
+\end{quotation}
+
+
+\item[Apuntes. Manual de \LaTeX{}] \mbox{}
+
+Preparado en Chile y disponible en
+\ifpdf
+\href{http://cipres.cec.uchile.cl/~admcons/manuales/latex.html}{http://cipres.cec.uchile.cl/\~{}admcons/manuales/latex.html}
+\else
+\onlynameurl{http://cipres.cec.uchile.cl/\~{}admcons/manuales/latex.html}
+\fi
+
+
+
+
+\item[Bases de datos bibliogr\'aficos, \LaTeX{} y el idioma espa\~nol] \mbox{}
+
+Luis Seidel
+
+Acerca del uso de Bib\TeX{} en castellano. Disponible en
+{\itshape postscript\/} en la p\'agina del autor y en formato {\itshape pdf\/} en la
+Universidad de la Rioja:
+
+\ifpdf
+\href{http://feynman.faii.etsii.upm.es/~seidel/bibliogr.ps}{http://feynman.faii.etsii.upm.es/\~{}seidel/bibliogr.ps}
+\else
+\onlynameurl{http://feynman.faii.etsii.upm.es/\~{}seidel/bibliogr.ps}
+\fi
+
+
+
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf}{ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/doc/bibliogr.pdf}
+\fi
+
+
+\item[Curso de \LaTeX{}] \mbox{}
+
+Kjetil Halvorsen. Transparencias de un curso de \LaTeX{} disponibles
+en
+
+
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip}{ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/doc/cursotex.zip}
+\fi
+
+
+
+
+\item[Recetario para \LaTeX{}] \mbox{}
+
+por Aristarco. Disponible en
+\ifpdf
+\href{http://recetariolatex.cjb.net}{http://recetariolatex.cjb.net}
+\else
+\onlynameurl{http://recetariolatex.cjb.net}
+\fi
+
+
+
+
+\item[Referencias r\'apidas de \LaTeX{}] \mbox{}
+
+por Fernando Arbeiza. Disponible en
+\ifpdf
+\href{http://www.loarco.homelinux.org/lqref-es}{http://www.loarco.homelinux.org/lqref-es}
+\else
+\onlynameurl{http://www.loarco.homelinux.org/lqref-es}
+\fi
+
+
+\end{description}
+
+
+
+
+
+\subsection{Libros en castellano
+ }
+
+\begin{description}
+\item[Iniciaci\'on a \LaTeXe{}] \mbox{}
+
+Javier Sanguino Botella, Addison-Wesley
+(1997)
+
+
+
+\item[Composici\'on de textos cient\'\i{}ficos con \LaTeX{}.] \mbox{}
+
+G. Valiente. Edicions UPC, Barcelona, 1997
+
+
+
+\item[\LaTeX{}, primeros pasos.] \mbox{}
+
+F. Orteg\'on Gallego. Editorial Masson, Barcelona 1.992. (Sobre
+\LaTeX{} 2.09)
+
+
+
+\item[\LaTeX{}, una imprenta en sus manos.] \mbox{}
+
+Bernardo Cascales Salinas, Pascual Lucas Saor\'\i{}n, Jose Manuel Mira
+Ros, Antonio Pallar\'es Ruiz y Salvador S\'anchez-Pedre\~no Guill\'en. Aula
+Documental de Investigaci\'on, Madrid, 2000.
+
+
+
+\item[El libro de \LaTeX{}.] \mbox{}
+
+Bernardo Cascales, Pascual Lucas, Jos\'e Manuel Mira, Antonio Pallar\'es
+y Salvador S\'anchez-Pedre\~no. Prentice Hall, Madrid, 2003.
+
+
+
+\item[El universo \LaTeX{}.] \mbox{}
+
+Rodrigo De Castro. Facultad de Ciencias, Universidad Nacional de
+Colombia, Bogot\'a, 2003.
+
+\end{description}
+
+
+
+
+
+\subsection{Tutoriales en otros idiomas
+ }
+
+\begin{description}
+\item[A Gentle Introduction to \TeX{}] \mbox{}
+
+de Michael Dobb, disponible en
+{\ttfamily CTAN:documentation/gentle}. Es un excelente tutorial de
+introducci\'on al {\itshape plain\/}-\TeX{} en ingl\'es.
+
+Una referencia cl\'asica de \TeX{}
+
+\item[Simplified Introduction to \LaTeX{}] \mbox{}
+
+de Harvey J. Greenberg, disponible en
+{\ttfamily CTAN:documentation/simplified-latex/latex.ps} (versi\'on
+postscript) y la versi\'on m\'as reciente en
+\ifpdf
+\href{http://www.cudenver.edu/~hgreenbe/aboutme/pubrec.html}{http://www.cudenver.edu/\~{}hgreenbe/aboutme/pubrec.html}
+\else
+\onlynameurl{http://www.cudenver.edu/\~{}hgreenbe/aboutme/pubrec.html}
+\fi
+.
+Basado en un curso para pregraduados.
+
+
+
+\item[\LaTeX{}: from quick and dirty to style and finesse] \mbox{}
+
+Escrito por Tony
+Roberts, se encuentra disponible en la Universidad de Southern
+Queensland (Australia)
+\ifpdf
+\href{http://www.sci.usq.edu.au/staff/robertsa/LaTeX/}{http://www.sci.usq.edu.au/staff/robertsa/LaTeX/}
+\else
+\onlynameurl{http://www.sci.usq.edu.au/staff/robertsa/LaTeX/}
+\fi
+
+con una r\'eplica en Estados Unidos
+\ifpdf
+\href{http://ricardo.ecn.wfu.edu/LaTeX/}{http://ricardo.ecn.wfu.edu/LaTeX/}
+\else
+\onlynameurl{http://ricardo.ecn.wfu.edu/LaTeX/}
+\fi
+.
+
+
+
+\item[\LaTeX{} for Word Processor Users] \mbox{}
+
+Escrito por Guido Gonzato, es un
+tutorial \LaTeX{} pensado espec\'\i{}ficamente para usuarios de
+procesadores de texto. Est\'a disponible en {\ttfamily CTAN:info/latex4wp}
+
+
+
+\item[l2tabu] \mbox{}
+
+Escrito por Mark Trettin,
+es un tutorial sobre lo que no debe hacer un usuario de
+\LaTeXe{}. Disponible en el CTAN como un archivo pdf,
+\ifpdf
+\href{http://www.ctan.org/tex-archive/info/l2tabu/}{http://www.ctan.org/tex-archive/info/l2tabu/}
+\else
+\onlynameurl{http://www.ctan.org/tex-archive/info/l2tabu/}
+\fi
+.
+Contiene una lista de \'ordenes y paquetes obsoletos que no deben
+utilizarse bajo \LaTeXe{}, as\'\i{} como otros errores habituales.
+
+\item[Online tutorials on \LaTeX{}] \mbox{}
+
+del grupo de usuarios de \TeX{} de
+la India, disponible en
+\ifpdf
+\href{http://www.tug.org.in/tutorials.html}{http://www.tug.org.in/tutorials.html}
+\else
+\onlynameurl{http://www.tug.org.in/tutorials.html}
+\fi
+.
+
+\end{description}
+
+
+
+
+
+\subsection{Libros en otros idiomas\label{libros-int}
+ }
+
+\begin{description}
+\item[A Guide to \LaTeX{}] \mbox{}
+
+\ifpdf
+\href{http://www.awprofessional.com/title/0321173856}{H. Kopka y P.W. Daly, Addison-Wesley Professional (2004)}
+\else
+\onlynameurl{H. Kopka y P.W. Daly, Addison-Wesley Professional (2004)}
+\fi
+
+
+Probablemente, el mejor manual existente sobre \LaTeX{}. Contiene
+una gu\'\i{}a completa de \'ordenes, abundantes ejemplos e informaci\'on
+adicional. (Incluye las dos versiones en uso de \LaTeX{}, \LaTeXe{}
+y la m\'as antigua, \LaTeX{}2.09).
+
+
+
+\item[The \LaTeX{} Companion.] \mbox{}
+
+\ifpdf
+\href{http://www.awprofessional.com/title/0201362996}{Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle, Chris Rowley, Addison Wesley Professional (2004).}
+\else
+\onlynameurl{Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle, Chris Rowley, Addison Wesley Professional (2004).}
+\fi
+
+
+Este manual sirve de ampliaci\'on del anterior. Es una recopilaci\'on
+e informaci\'on sobre los llamados paquetes ({\itshape packages\/}),
+conjuntos de macros que distintos autores han puesto a disposici\'on
+p\'ublica.
+
+
+
+\item[The \LaTeX{} Web Companion: Integrating TeX, HTML, and XML] \mbox{}
+
+\ifpdf
+\href{http://www.awprofessional.com/titles/0201433117}{Michel Goossens, Sebastian Rahtz, Eitan M. Gurari, Ross Moore y Robert S. Sutor, Addison Wesley Professional (1999).}
+\else
+\onlynameurl{Michel Goossens, Sebastian Rahtz, Eitan M. Gurari, Ross Moore y Robert S. Sutor, Addison Wesley Professional (1999).}
+\fi
+
+
+Publicando documentos en la WWW mediante \LaTeX{}
+
+
+
+\item[\LaTeX{}--A Document preparation system] \mbox{}
+
+\ifpdf
+\href{http://www.aw.com/catalog/academic/product/1,4096,0201529831,00.html}{L. Lamport (dos ediciones) Addison-Wesley (1985 y 1994).}
+\else
+\onlynameurl{L. Lamport (dos ediciones) Addison-Wesley (1985 y 1994).}
+\fi
+
+
+Durante mucho tiempo este fue {\itshape "el libro"\/} del \LaTeX{}. Escrito
+por el mismo autor del programa, contiene todo lo esencial para
+introducirse en este procesador, si bien resulta un tanto
+insuficiente para usuarios avanzados. La primera edici\'on
+corresponde a la versi\'on antigua del programa (\LaTeX{}209, hoy
+obsoleta) y la segunda al \LaTeXe{}.
+
+
+
+\item[The \LaTeX{} Graphics Companion] \mbox{}
+
+\ifpdf
+\href{http://www.aw.com/catalog/academic/product/1,4096,0201854694,00.html}{M. Goossens, S. Rahtz y F. Mittelbach, Addison-Wesley (1997).}
+\else
+\onlynameurl{M. Goossens, S. Rahtz y F. Mittelbach, Addison-Wesley (1997).}
+\fi
+
+
+Un extenso manual acerca de c\'omo ilustrar documentos con \TeX{} y
+postscript.
+
+
+
+\item[The \TeX{}book] \mbox{}
+
+\ifpdf
+\href{http://www.aw.com/catalog/academic/product/1,4096,0201134470,00.html}{D.E. Knuth, Addison-Wesley (1986).}
+\else
+\onlynameurl{D.E. Knuth, Addison-Wesley (1986).}
+\fi
+
+
+Este es {\itshape "el libro"\/} para los que quieren conocer las entra\~nas de
+\TeX{}. Contiene todo sobre el lenguaje \TeX{}, escrito por el mismo
+autor del programa. Es un libro completo y ameno pero
+absolutamente incomprensible para los novatos. El archivo fuente
+en \TeX{} de este libro est\'a disponible para aquellos que desean
+conocer los trucos que el autor emple\'o a la hora de escribirlo
+(algunos verdaderamente complejos).
+
+
+
+Knuth proporciona el c\'odigo fuente con fines {\itshape did\'acticos\/}, no para que se
+imprima. De hecho, si se intenta {\itshape \TeX{}earlo\/} entrar\'a en un
+bucle infinito que dice que eso no debe hacerse. Aunque no es
+complicado hacer que deje de ocurrir, ser\'\i{}a ilegal hacerlo... :-)
+
+
+
+\item[TeX by Topic, A TeXnician's Reference] \mbox{}
+
+de Victor Eijkhout, editado por
+Addison-Wesley (1992) y disponible en
+\ifpdf
+\href{http://www.eijkhout.net/tbt/}{http://www.eijkhout.net/tbt/}
+\else
+\onlynameurl{http://www.eijkhout.net/tbt/}
+\fi
+,
+
+es otro de los libros cl\'asico sobre \TeX{} (no \LaTeX{}) que puede descargarse
+gratis (y legalmente) en un pdf.
+
+
+
+\item[\TeX{} for the Impatient] \mbox{}
+
+de Karl Berry, tambi\'en est\'a
+disponible en {\ttfamily CTAN:info/impatient/} de forma libre.
+
+
+
+\item[Making \TeX{} work] \mbox{}
+
+de Norman Walsh, editado por O'Reilly
+(ISBN: 156592-051-1), pero actualmente descatalogado. Sin embargo est\'a
+disponible de forma libre en
+\ifpdf
+\href{http://makingtexwork.sourceforge.net/mtw/}{http://makingtexwork.sourceforge.net/mtw/}
+\else
+\onlynameurl{http://makingtexwork.sourceforge.net/mtw/}
+\fi
+.
+Aunque algunas cosas est\'an obsoletas, (de hecho todav\'\i{}a se refiere a \LaTeX{} 2.09),
+tanto su contenido como sus fuentes pueden a\'un ser de utilidad.
+
+
+
+\end{description}
+
+
+
+
+
+\subsection{Revistas.\label{revistas}
+ }
+
+\begin{description}
+\item[The PracTeX Journal] \mbox{}
+
+Una revista de \TeX{} {\itshape on-line\/} y
+gratuita. Disponible en
+\ifpdf
+\href{http://dw.tug.org/pracjourn/}{http://dw.tug.org/pracjourn/}
+\else
+\onlynameurl{http://dw.tug.org/pracjourn/}
+\fi
+.
+
+
+
+\end{description}
+
+
+
+\section{Que elementos intervienen al procesar un documento con \LaTeX{}?
+ }
+
+
+\subsection{El documento fuente: C\'omo creo un documento con \LaTeX{}, lo proceso, lo veo y lo imprimo? }
+
+Como hemos dicho \TeX{}/\LaTeX{} es realmente un lenguaje de
+programaci\'on de textos. En el documento fuente original se introduce
+el texto a procesar junto con una serie de \'ordenes especificando c\'omo
+debe ser procesado \'este. Este paso se realiza con el editor de texto
+favorito del autor, aunque hay algunos editores de texto que est\'an,
+mejor adaptados, o totalmente integrados para su uso con \TeX{}/\LaTeX{}
+-- v\'ease \ref{tex-editores} {(editores para \TeX{})}
+--. Pongamos por ejemplo que el documento creado es {\ttfamily documento.tex}.
+
+Una vez terminado el documento fuente ({\ttfamily documento.tex}), \'este se
+procesa mediante \TeX{} si se han utilizado las \'ordenes de
+{\itshape plain-\TeX{}\/} o \LaTeX{} si se han utilizado las \'ordenes de
+\LaTeX{}. Se corrigen los posibles errores de sintaxis y se repite el
+proceso hasta que \'estos se han eliminado. Como resultado del
+procesamiento se tiene un {\itshape archivo independiente del dispositivo\/},
+o DVI ({\ttfamily documento.dvi}).
+
+
+
+
+\subsection{Qu\'e es un archivo DVI?\label{DVI}
+ }
+
+Un archivo DVI es el archivo resultante de procesar el texto fuente a
+trav\'es de \TeX{}. Su forma no depende del dispositivo que se vaya a
+utilizar para verlo/imprimirlo. Un archivo DVI est\'a pensado para ser
+le\'\i{}do por un {\itshape conversor\/} que produzca una salida adecuada para una
+determinada impresora, o para un determinado visualizador en la
+pantalla del ordenador. Los archivos DVI utilizan una codificaci\'on
+interna de \TeX{}, de forma que un documento fuente debe producir
+exactamente el mismo archivo DVI, con independencia de la
+implementaci\'on de \TeX{} que se utiliza para producirlo.
+
+Un archivo DVI contiene toda la informaci\'on necesaria para imprimir o
+ver el resultado, excepto los tipos o su aspecto concreto (aunque
+contiene sus medidas) o informaci\'on que se introducir\'a mediante una
+orden {\ttfamily $\backslash$special}
+-- v\'ease \ref{special} {(Qu\'e son los $\backslash$special?)}.
+
+
+
+
+\subsection{Qu\'e es un conversor (driver)?\label{conversores}
+ }
+
+Un conversor es un programa que toma su entrada de un archivo DVI y
+produce un archivo que puede enviarse a una impresora o una salida
+directa a una pantalla.
+
+Estos conversores normalmente son espec\'\i{}ficos a cada impresora o
+lenguaje de impresora. Por ejemplo, una impresora {\itshape postscript\/}
+entender\'a siempre la salida de un conversor {\itshape postscript\/}, pero en
+general no de otros formatos.
+
+Al igual que el archivo DVI, el conversor necesita informaci\'on sobre
+los tipos que puede encontrar en distintos lugares.
+
+
+
+
+\subsection{Qu\'e son los archivos {\ttfamily .pk}?
+ }
+
+Los archivos {\ttfamily .pk} (cuyo nombre viene de {\itshape packed raster\/})
+contienen tipos de letra en forma de mapa de bits. METAFONT produce
+una salida en mapa de bits en un formato no comprimido denominado
+{\ttfamily .gf}, que es convertido a {\ttfamily .pk} mediante una utilidad
+denominada {\itshape gftopk\/}. Para cada dise\~no de letra, tama\~no, peso y
+familia es necesario un archivo {\ttfamily .pk} distinto, e incluso para
+distintos dispositivos de salida. Como consecuencia de \'esto se guardan
+en una estructura compleja de directorios, o en librer\'\i{}as de tipos,
+para normalizar el acceso a las mismas.
+
+
+
+
+\subsection{Qu\'e son los archivos {\ttfamily .tfm}?
+ }
+
+{\ttfamily tfm} es la abreviatura de {\itshape \TeX{} font metric\/}, m\'etrica de los
+tipos \TeX{}. Los archivos {\ttfamily .tfm} guardan la informaci\'on acerca de
+los tama\~nos de los caracteres en cada tipo, as\'\i{} como las ligaduras y
+desplazamientos dentro de cada tipo. Se necesita un archivo {\ttfamily .tfm}
+para cada tipo utilizado por \TeX{}, es decir para cada dise\~no, peso y
+familia, aunque uno valga para todas las magnificaciones. \TeX{}
+utiliza los archivos {\ttfamily .tfm} para componer la p\'agina, pero en
+general los conversores no los necesitan.
+
+
+
+
+\subsection{Qu\'e son los tipos (fuentes) CM?\label{CM}
+ }
+
+Los tipos CM son los tipos originalmente creados por Donald
+E. Knuth. Cuando desarroll\'o \TeX{}, lo acompa\~n\'o de este conjunto
+completo de tipos de alta calidad. Estos tipos eran independientes de
+la impresora utilizada (ya que eran tratados como gr\'aficos) lo que
+produc\'\i{}a la misma calidad en cualquier sitio. Con el tiempo, estos
+tipos (los Computer Modern o CM) se convirtieron en la {\itshape firma\/} del
+procesador, que permit\'\i{}a identificar un documento a primera vista.
+
+
+
+
+\subsection{Qu\'e son los tipos (fuentes) EC/DC?\label{EC/DC}
+ }
+
+Son fuentes del tipo de las Computer Modern, pero con 256 caracteres,
+que cubren las necesidades de casi todas las lenguas habladas en
+Europa y algunas otras que utilizan el alfabeto latino. Su nombre
+viene de {\itshape European Computer Modern Fonts\/}. Dichas fuentes contienen
+caracteres acentuados siguiendo el esquema de codificaci\'on de
+Cork. Han estado durante bastante tiempo en periodo de pruebas y
+durante ese tiempo se llamaban DC. Ya se distribuyen normalmente al
+p\'ublico en general, con el nombre EC, y a partir de ese momento las DC
+se consideran obsoletas.
+
+Estas fuentes ya est\'an presentes en las distribuciones modernas de
+\TeX{}/\LaTeX{}, pero en caso de que se trabaje con una distribuci\'on
+antigua pueden conseguirse en:
+\begin{tscreen}
+\begin{verbatim}
+CTAN:fonts/ec/ready-mf
+\end{verbatim}
+\end{tscreen}
+
+y los archivos {\ttfamily tfm} para \LaTeX{} est\'an en
+\begin{tscreen}
+\begin{verbatim}
+CTAN:fonts/ec/tfm
+\end{verbatim}
+\end{tscreen}
+
+Si tenemos tipos de Cork (PostScript, DC, etc.) y queremos utilizar
+esta codificaci\'on en las fuentes de salida se debe introducir en el
+pre\'ambulo del documento la l\'\i{}nea
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[T1]{fontenc}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsection{Qu\'e son los tipos (fuentes) virtuales?
+ }
+
+Los tipos (fuentes) virtuales proporcionan a \TeX{} una forma de
+trabajar con algo m\'as complejo que los caracteres individuales
+definidos en un tipo. En un tipo virtual se definen a partir de
+elementos simples de los tipos normales, elementos m\'as complejos que
+\TeX{} considerar\'a como si fueran elementos de un tipo normal (tienen
+sus tama\~nos y su archivo {\ttfamily .tfm} de m\'etrica), pero que en realidad
+el procesador del DVI compondr\'a a partir de distintos elementos
+constituyentes para formar a partir de ellos el elemento complejo
+descrito en el tipo virtual. De esta forma es posible remapear
+caracteres, hacer un tipo compuesto con elementos tomados de distintos
+tipos o en general construir elementos muy complejos a partir de
+elementos simples de los distintos tipos. Por ejemplo se utilizan
+tipos virtuales para {\itshape remapear\/} tipos {\itshape postscript\/}.
+
+\TeX{} en s\'\i{} no ve los tipos virtuales, \'unicamente trabaja con las
+m\'etricas que le da el tipo virtual en su {\ttfamily .tfm} como si se tratara
+de tipos normales.
+
+
+
+
+\subsection{Qu\'e son las \'ordenes {\ttfamily $\backslash$special}?\label{special}
+ }
+
+\TeX{} proporciona una forma de expresar cosas que los conversores
+pueden hacer, pero de las que \TeX{} no sabe nada. Por ejemplo \TeX{} no
+sabe c\'omo introducir figuras {\itshape postscript\/} en un documento o c\'omo
+cambiar el color del texto impreso, pero algunos conversores s\'\i{} saben c\'omo hacerlo.
+
+Para ello \TeX{} proporciona la orden {\ttfamily $\backslash$special}. \TeX{} simplemente
+entiende la orden como correcta y la pasa con sus argumentos al
+archivo DVI, sin hacer nada de lo que en ella se dice. Es el conversor
+el que debe interpretar la orden y hacer lo que se le pide.
+
+La sintaxis de los {\ttfamily $\backslash$special} es fuertemente dependiente del
+dispositivo de salida y en general no es v\'alida para distintos
+dispositivos. \LaTeXe{} proporciona paquetes est\'andar de gr\'aficos
+({\ttfamily graphics, graphicx}) y manejo de color ({\ttfamily color}), que hacen
+m\'as f\'acil la inclusi\'on de gr\'aficos, rotaci\'on, reescalado y cambios de
+color --V\'ease la secci\'on
+\ref{tex-dibujos} {(Introducir gr\'aficos con \LaTeX{})}.
+
+
+
+
+\subsection{Qu\'e es el postscript y el postscript encapsulado (archivos {\ttfamily .eps})?
+ \label{postscript}
+ }
+
+{\itshape PostScript\/} (PS) es un lenguaje de programaci\'on para describir
+p\'aginas. Como lenguaje estructurado permite la programaci\'on (tiene
+estructuras de control y bucles), y recuerda el lenguaje de
+programaci\'on FORTH. Originalmente fue desarrollado por Adobe. Existen
+varios int\'erpretes de {\itshape PostScript\/} que permiten la visualizaci\'on de
+este formato. El m\'as extendido es {\itshape Ghostscript\/} (GS), de Aladdin,
+del que puede obtenerse informaci\'on en
+\ifpdf
+\href{http://www.cs.wisc.edu/~ghost/index.html}{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\else
+\onlynameurl{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\fi
+
+y en
+\ifpdf
+\href{http://www.aladdin.com}{http://www.aladdin.com}
+\else
+\onlynameurl{http://www.aladdin.com}
+\fi
+
+cuando acaben de construirla. El formato PS se basa en describir cada
+p\'agina desde un origen de coordenadas que se sit\'ua en la esquina
+inferior izquierda de la p\'agina. PS permite, sin embargo, redefinir el
+origen, de forma que se puede recomenzar la descripci\'on de un bloque
+de una p\'agina desde un origen arbitrario.
+
+PS encapsulado (EPS) es el formato est\'andar para importar y exportar
+archivos PS en cualquier tipo de entornos. Usualmente es un archivo
+que contiene una sola p\'agina que describe una figura. El archivo EPS
+est\'a especialmente pensado para incluirlo en otros archivos PS, y es
+como cualquier otro archivo PS con algunas restricciones. La FAQ de
+{\itshape PostScript\/} puede alcanzarse en
+\ifpdf
+\href{http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html}{http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html}
+\else
+\onlynameurl{http://www.lib.ox.ac.uk/internet/news/faq/comp.lang.postscript.html}
+\fi
+,
+de donde est\'a tomado mucho de lo anterior.
+
+
+
+
+\subsection{Qu\'e es el formato {\ttfamily pdf}?\label{formato-pdf}
+ }
+
+PDF (Portable Document Format) es, como su nombre indica, un formato
+de archivos transportable entre distintas plataformas, creado por
+Adobe y especialmente dise\~nado para visualizar documentos tal y como
+se han dise\~nado. Permite usar colores, gr\'aficos, seguir enlaces e
+imprimir pero, fundamentalmente, permite ver en la pantalla los
+documentos, siendo un formato compacto. Es muy similar a PS, pero no
+tiene capacidades de programaci\'on. En relaci\'on con \TeX{}, PDF es un
+formato que sustituye al DVI -- ver la pregunta
+\ref{DVI} {(Qu\'e es DVI?)} -- en la salida de \TeX{}. En la web
+hay informaci\'on abundante sobre PDF en
+\ifpdf
+\href{http://www.pdfzone.com/webring/}{http://www.pdfzone.com/webring/}
+\else
+\onlynameurl{http://www.pdfzone.com/webring/}
+\fi
+.
+Los visualizadores de PDF m\'as recomendables son Adobe Reader (antes
+Acrobat Reader), de Adobe, gratuito
+(
+\ifpdf
+\href{http://www.adobe.com}{http://www.adobe.com}
+\else
+\onlynameurl{http://www.adobe.com}
+\fi
+),
+xpdf
+\ifpdf
+\href{http://www.foolabs.com/xpdf/home.html}{http://www.foolabs.com/xpdf/home.html}
+\else
+\onlynameurl{http://www.foolabs.com/xpdf/home.html}
+\fi
+ y
+Ghostview
+\ifpdf
+\href{http://www.cs.wisc.edu/~ghost/index.html}{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\else
+\onlynameurl{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\fi
+.
+
+
+
+
+\subsection{Qu\'e son los paquetes en \LaTeX{}?\label{paquetes-latex}
+ }
+
+Escribir un documento a base de {\itshape primitivas\/} \TeX{} puede resultar
+extremadamente engorroso. \LaTeX{} utiliza las primitivas de \TeX{} para
+definir otro conjunto de comandos m\'as amigable, para las tareas m\'as
+habituales (definir cap\'\i{}tulos, tablas, listas enumeradas...). No
+obstante, \LaTeX{} no incluy\'o nuevos comandos de {\itshape alto nivel\/} para
+cualquier tarea imaginable, sino que se hizo extensible a base de
+{\itshape paquetes\/}, de forma que hay un cuerpo de \LaTeX{} y unos a\~nadidos
+en forma de paquetes. Un {\itshape paquete\/} es un fichero que contiene m\'as
+c\'odigo, que se incluye en el pre\'ambulo del documento (con
+{\ttfamily $\backslash$usepackage$\{$nombre-de\_paquete$\}$}),y que define nuevos comandos
+bas\'andose, ya sea en las primitivas de TeX o en los comandos
+previamente definidos por LaTeX.
+
+La distribuci\'on de \TeX{}/\LaTeX{} instalada en el sistema ya incluir\'a
+una buena cantidad de paquetes listos para su uso. Sin embargo, pueden
+a\~nadirse nuevos paquetes
+-- v\'ease \ref{paquetes-instalar} {(Instalaci\'on de paquetes)}.
+
+
+
+
+\subsection{Qu\'e son los archivos {\ttfamily .dtx}?\label{formato-dtx}
+ }
+
+Tanto \LaTeXe{} como muchos de los paquetes de macros se escriben en un
+lenguaje de programaci\'on ilustrada, con c\'odigo y documentaci\'on en el
+mismo fichero. Este formato, conocido como {\ttfamily doc} se debe a Frank
+Mittelbach. El fichero que contiene las fuentes comentadas suele tener
+la extensi\'on {\ttfamily .dtx} y normalmente debe aligerarse de la
+documentaci\'on antes de su uso como macro, o correr \LaTeX{} sobre el
+fichero para producir una versi\'on maquetada de la
+documentaci\'on. Habitualmente se suministra un fichero {\ttfamily .ins} para
+facilitar esto, que utiliza el paquete {\itshape docstrip\/}. Pueden incluirse
+varios paquetes dentro de un mismo fichero {\ttfamily .dtx}. Para m\'as
+informaci\'on acerca de c\'omo extraer el contenido de un fichero
+{\ttfamily .dtx} v\'ease \ref{dtx-extraer} {(extraer de un .dtx)}.
+
+\LaTeX{} no utiliza los ficheros {\ttfamily .dtx} una vez procesados para
+producir los {\ttfamily .sty} o {\ttfamily .cls}, por lo que no es estrictamente
+necesario tenerlos instalados, aunque puede ser recomendable, ya que
+son siempre la principal fuente de informaci\'on sobre el paquete.
+
+
+
+
+\section{C\'omo consigo \LaTeX{} y otros programas relacionados?
+ }
+
+
+\subsection{Distribuciones \TeX{}/\LaTeX{}
+ }
+
+En principio se podr\'\i{}a coger todo el sistema elemento a elemento y
+ponerlo todo en com\'un. Sin embargo, para que \'esto funcione
+correctamente, el tiempo requerido y la complejidad del trabajo son
+grandes. Por esta raz\'on algunas personas o empresas ya lo han hecho y
+lo ofrecen preparado en lo que se denominan distribuciones.
+
+Se entiende por distribuci\'on un conjunto de binarios y paquetes de
+macros \LaTeX{} junto con otras utilidades adicionales, empaquetados de
+forma coherente y organizada, para que trabajen en com\'un de la forma
+m\'as eficiente posible. Hay distribuciones de libre distribuci\'on,
+shareware (se puede distribuir y probar, pero si se quiere usar
+regularmente es necesario pagar el registro) y otras de distribuci\'on
+comercial. Aunque algunas de las distribuciones comerciales tienen
+caracter\'\i{}sticas adicionales sobre las distribuciones libres, a veces
+es al contrario. Aunque algunas distribuciones est\'an disponibles para
+distintos sistemas operativos, lo m\'as habitual es que est\'en limitadas
+a un sistema operativo.
+
+Las distribuciones libres o shareware pueden conseguirse en el CTAN --
+v\'ease \ref{que-es-CTAN} {(Qu\'e es el CTAN?)} --, o a trav\'es de
+los CD-ROM editados por distintos grupos de usuarios de \LaTeX{},
+mientras que las comerciales se consiguen a trav\'es de sus respectivos
+distribuidores o directamente si no los hay.
+
+Para buscar distribuciones para los distintos sistemas operativos, la
+estructura de un nodo CTAN es siempre la misma. Existe un directorio
+{\ttfamily tex-archive} del cual cuelga un \'arbol de directorios. En
+particular, existe un directorio {\ttfamily systems}, del que penden las
+distintas implementaciones. Existen versiones para
+\begin{tscreen}
+\begin{verbatim}
+Atari
+Amiga
+UNIX
+VMS
+Os2
+Windows NT
+Mac
+MS-DOS
+\end{verbatim}
+\end{tscreen}
+
+No es necesario tener una acceso de red para acceder al CTAN. El grupo
+de usuarios alemanes de \TeX{} (DANTE) ha hecho una recopilaci\'on en
+CD-ROM del contenido del CTAN. Las edici\'on de 1999 y posteriores se
+han distribuido a trav\'es del grupo de usuarios Cervan\TeX{}. Para mayor
+informaci\'on se puede consultar la p\'agina web del grupo Cervan\TeX{}
+
+
+
+
+\subsubsection{Distribuciones libres o {\itshape shareware\/}
+ }
+
+\begin{description}
+\item[Unix] \mbox{}
+
+{\itshape te\TeX{}\/} es, para sistemas {\ttfamily Unix} la elecci\'on m\'as
+multiplataforma. Se puede encontrar en
+{\ttfamily CTAN:systems/unix/teTeX} y contiene por un lado una
+serie de archivos que no dependen del sistema operativo y por
+otro lado binarios para toda una serie de sistemas operativos
+{\itshape Unix\/}.
+
+
+
+\item[Linux] \mbox{}
+
+Aunque lo que se acaba de decir de {\itshape Unix\/} es tambi\'en v\'alido
+para {\itshape Linux\/}, recalcar adem\'as que en las principales
+distribuciones de {\itshape Linux\/} vienen paquetes de {\itshape te\TeX{}\/}
+listos para instalar y utilizar sin apenas esfuerzo.
+
+Antes tambi\'en hab\'\i{}a otra distribuci\'on denominada {\itshape N\TeX{}\/}. Es
+necesario tener un especial cuidado y {\bfseries no utilizar} la
+incluida en el CD-ROM de Slackware'96, que inclu\'\i{}a una versi\'on
+de las fuentes CM que no respetaba las condiciones de
+distribuci\'on y cambiaba la m\'etrica respecto de las est\'andar sin
+cambiar el nombre, rompiendo la portabilidad de los
+documentos. En la pr\'actica este aviso debe estar ya obsoleto.
+
+
+
+\item[Mac] \mbox{}
+
+Los Macs modernos ya no utilizan el sistema operativo cl\'asico
+sino uno basado en *BSD unix ({\itshape Mac OS X\/}), con una capa
+gr\'afica que no son las {\itshape X-Window\/} (pero que tambi\'en se pueden
+poner).
+
+Por este motivo muchas aplicaciones unix cl\'asicas se han
+adaptado con facilidad a {\itshape Mac OS X\/}, entre ellas
+{\itshape te\TeX{}\/}. La p\'agina
+\ifpdf
+\href{http://www.rna.nl/tex.html}{http://www.rna.nl/tex.html}
+\else
+\onlynameurl{http://www.rna.nl/tex.html}
+\fi
+
+tiene una gran cantidad de informaci\'on sobre el uso de \TeX{} en
+{\itshape Mac OS X\/}, incluyendo un instalador de {\itshape te\TeX{}\/}. Se
+necesita un editor que se comunique bien con \TeX{}, como los que
+se mencionan m\'as adelante. Otras p\'aginas muy interesantes son
+\ifpdf
+\href{http://www.esm.psu.edu/mac-tex/default.html}{http://www.esm.psu.edu/mac-tex/default.html}
+\else
+\onlynameurl{http://www.esm.psu.edu/mac-tex/default.html}
+\fi
+ y
+\ifpdf
+\href{http://latex.yauh.de/index_en.html}{http://latex.yauh.de/index\_en.html}
+\else
+\onlynameurl{http://latex.yauh.de/index\_en.html}
+\fi
+.
+
+Para {\itshape Mac\/} cl\'asicos sigue existiendo Oz\TeX{}. \'Este es una
+versi\'on {\itshape shareware\/} de \TeX{} para los ordenadores Macintosh
+cl\'asicos. Incluye un visualizador de dvi y un conversor a
+postscript. Est\'a disponible en
+{\ttfamily CTAN:non-free/systems/mac/oztex}. Su p\'agina original est\'a en
+\ifpdf
+\href{http://www.trevorrow.com/oztex/}{http://www.trevorrow.com/oztex/}
+\else
+\onlynameurl{http://www.trevorrow.com/oztex/}
+\fi
+
+
+
+
+\item[DOS/OS2] \mbox{}
+
+{\itshape em\TeX{}\/} es, para sistemas {\itshape DOS\/} la distribuci\'on m\'as
+extendida. Puede encontrarse en
+{\ttfamily CTAN:systems/msdos/emtex}, aunque desde hace tiempo no
+se ven versiones nuevas. {\itshape g\TeX{}\/} era otra distribuci\'on para
+{\itshape DOS\/}, pero recientemente ha sido retirada de {\ttfamily CTAN} a
+petici\'on de su creador. Tambi\'en est\'a {\itshape em\TeX{}-TDS\/}, que no es
+m\'as que un \'arbol de archivos de estilo para \TeX{}/\LaTeX{}
+preparado para ser utilizado con los binarios de {\itshape em\TeX{}\/}.
+
+
+
+\item[Win32] \mbox{}
+
+\begin{itemize}
+\item {\bfseries Mik\TeX{}} de Christian Schenk es tambi\'en una
+distribuci\'on completa independiente de te\TeX{}. tiene su
+propio visualizador {\itshape yap\/} que permite imprimir, aunque
+tambi\'en se incluye {\itshape dvips\/}. Est\'a disponible en
+{\ttfamily CTAN:systems/win32/miktex}. Si se tiene conexi\'on de
+red, las \'ultimas versiones permiten traer e instalar
+paquetes sobre la marcha seg\'un se van necesitando. Para
+obtener informaci\'on sobre la instalaci\'on de un sistema
+\LaTeX{} (mik\TeX{}) en Windows puede consultarse la p\'agina
+\ifpdf
+\href{http://www.udlap.mx/~ma108907/latex/winlatex.html}{http://www.udlap.mx/\~{}ma108907/latex/winlatex.html}
+\else
+\onlynameurl{http://www.udlap.mx/\~{}ma108907/latex/winlatex.html}
+\fi
+.
+\item {\bfseries XEm\TeX{}}, de Fabrice Popineau, es una distribuci\'on
+integrada de \TeX{}, \LaTeX{}, Con\TeX{}t, Xemacs y otros
+programas para Windows. Todos los programas han sido
+compilados de forma nativa para optimizar el rendimiento
+bajo Windows. Se suministra configurado para que funcione
+nada m\'as instalarse. Su p\'agina es
+\ifpdf
+\href{http://www.fptex.org/}{http://www.fptex.org/}
+\else
+\onlynameurl{http://www.fptex.org/}
+\fi
+
+\item {\bfseries fp\TeX{}} de Fabrice Popineau era una versi\'on de
+{\itshape te\TeX{}\/} para Windows. Sin embargo, su autor lo ha
+dejado de lado para concentrarse en XEm\TeX{}. De momento
+sigue disponible en {\ttfamily CTAN:systems/win32/fptex}, pero
+ya no est\'a mantenido.
+\end{itemize}
+
+
+\end{description}
+
+
+
+
+
+\subsubsection{Distribuciones comerciales\label{tex-de-pago}
+ }
+
+\begin{description}
+\item[Windows] \mbox{}
+
+\begin{itemize}
+\item {\bfseries Scientific Word}{\itshape Scientific
+Word/WorkPlace/Notebook\/} ofrece una forma de trabajo
+tipo casi {\itshape WYSIWYG\/} con un procesador \TeX{} en segundo
+plano. M\'as informaci\'on en
+\ifpdf
+\href{http://www.sciword.demon.co.uk/}{http://www.sciword.demon.co.uk/}
+\else
+\onlynameurl{http://www.sciword.demon.co.uk/}
+\fi
+.
+Incluye {\itshape True\TeX{}\/}. Aunque proporciona un entorno
+{\itshape amistoso\/} para la escritura de documentos, en algunos
+casos integrado con {\itshape maple\/} para realizar c\'alculos
+simb\'olicos, es muy r\'\i{}gido cuando es necesario salirse de los
+estilos est\'andar proporcionados con {\itshape SW\/} y no es f\'acil
+compartir archivos \LaTeX{} generados con {\itshape SW\/} con otras
+personas que no lo usen, porque necesitan una serie de
+paquetes espec\'\i{}ficos. Adem\'as, los argumentos opcionales de
+algunas macros dan error en {\itshape SW\/}, aunque dependiendo de
+uso que se le de, \'esto puede no aparecer. A pesar de todo,
+puede ser \'util para una persona que no quiere hacer cosas complicadas.
+\end{itemize}
+
+
+\end{description}
+
+
+
+
+
+\subsection{Editores de texto que trabajan especialmente bien con \LaTeX{}\label{tex-editores}
+ }
+
+\begin{description}
+\item[Unix] \mbox{}
+
+\begin{itemize}
+\item GNU {\itshape emacs\/} o {\itshape xemacs\/}
+utilizado en combinaci\'on con el paquete AUC\TeX{} (disponible
+en {\ttfamily CTAN:support/auctex)} o como un paquete ya incluido
+en muchas distribuciones) proporciona men\'us desplegables y
+secuencias de control para las estructuras habituales,
+verifica sintaxis y la muestra coloreada, permite llamar a
+\TeX{} y a los conversores desde el editor y mucho
+m\'as. Complejo, pero muy potente. Joaqu\'\i{}n Ataz ha escrito un
+manual para su uso con \LaTeX{},
+{\itshape Creaci\'on de ficheros \LaTeX{} con GNU Emacs\/}, disponible en
+{\ttfamily CTAN:info/spanish/guia-atx/guia-atx.pdf}
+\item {\itshape kile\/}
+Trabaja sobre cualquier plataforma con KDE instalado y seg\'un
+la documentaci\'on, hasta en OS-X... Tiene opciones para
+compilaci\'on y conversiones con una \'unica pulsaci\'on de tecla,
+se pueden personalizar las \'ordenes y se integra con cualquier
+visualizador dvi, ps o pdf que tengamos. Disponible en la
+mayor parte de las distribuciones Linux y en
+\ifpdf
+\href{http://kile.sourceforge.net}{http://kile.sourceforge.net}
+\else
+\onlynameurl{http://kile.sourceforge.net}
+\fi
+.
+\end{itemize}
+
+
+\item[Mac] \mbox{}
+
+Para {\itshape Mac OS X\/} hay algunos editores que se entienden bien con
+\TeX{}
+\begin{itemize}
+\item {\bfseries TeXShop}
+Muy majo y en castellano. Se encuentra en
+\ifpdf
+\href{http://www.uoregon.edu/~koch/texshop/}{http://www.uoregon.edu/\~{}koch/texshop/}
+\else
+\onlynameurl{http://www.uoregon.edu/\~{}koch/texshop/}
+\fi
+.
+\item {\bfseries iTeXMac}
+Tiene m\'as cosas, pero es m\'as lento y hay muchos mensajes de
+"a\'un no implementado". Se encuentra en
+\ifpdf
+\href{http://itexmac.sourceforge.net/}{http://itexmac.sourceforge.net/}
+\else
+\onlynameurl{http://itexmac.sourceforge.net/}
+\fi
+.
+\end{itemize}
+
+
+\item[DOS/OS2] \mbox{}
+
+\TeX{}shell es un entorno de trabajo simple y f\'acilmente
+personalizable que puede ser utilizado con el editor favorito de
+cada uno. Tambi\'en cuenta con un editor propio que permite seguir
+los errores de la compilaci\'on f\'acilmente aunque no soporta
+archivos de m\'as de 64K. Aunque puede particularizarse a otras
+distribuciones, viene muy preconfigurado para em\TeX{}.
+
+\item[Win32] \mbox{}
+
+\begin{itemize}
+\item {\bfseries winedt}
+es un paquete {\itshape shareware\/} del que se suele oir hablar
+bien. Proporciona un entorno de trabajo desde el que llamar a
+los distintos programas y un editor potente y bien configurado
+\item {\bfseries Winshell}
+es un programa libre de prestaciones menores, pero que puede
+ser m\'as que suficiente para muchos usuarios.
+\item {\bfseries TeXnic Center}
+es tambi\'en un buen entorno de trabajo para Win32. Est\'a
+disponible en CTAN en
+{\ttfamily CTAN:systems/win32/TeXnicCenter/}
+\end{itemize}
+
+
+\end{description}
+
+
+
+Otros programas que no son editores completos, pero que ayudan a la edici\'on son:
+\begin{description}
+\item[LaTable] \mbox{}
+
+es un ayudante de creaci\'on de tablas que permite generar el c\'odigo
+\LaTeX{} necesario para la creaci\'on de una tabla. La tabla se
+dise\~na en un entorno visual muy c\'omodo y la herramienta genera el
+c\'odigo \LaTeX{} que se incorpora al documento con un simple
+{\itshape copy-paste\/}. Tambi\'en permite guardar las tablas generadas para
+su posterior modificaci\'on. Todav\'\i{}a tiene detalles, pero cuenta con
+muchas opciones bastante \'utiles, y genera un c\'odigo relativamente
+limpio... adem\'as, aunque es un programa Win32 funciona bien en
+{\itshape Linux\/} usando el emulador {\itshape Wine\/}. Disponible en
+\ifpdf
+\href{http://www.g32.org/latable/}{http://www.g32.org/latable/}
+\else
+\onlynameurl{http://www.g32.org/latable/}
+\fi
+. Es freeware de uso, pero
+sus fuentes no est\'an disponibles.
+
+
+
+\item[TeXaide] \mbox{}
+
+para quienes sigan pensando que las ecuaciones se deben hacer con
+dise\~nadores ... (se consiguen mucho mejores resultados a mano,
+pero no faltan quienes abandonan \LaTeX{} cuando se enfrentan a las
+ecuaciones. Seg\'un los que lo han probado, el c\'odigo que genera no
+es en ocasiones muy limpio, pero suele funcionar bien. Es un
+programa Win32 que tambi\'en funciona en Linux usando el emulador
+Wine. Disponible en
+\ifpdf
+\href{http://www.dessci.com/en/products/texaide/}{http://www.dessci.com/en/products/texaide/}
+\else
+\onlynameurl{http://www.dessci.com/en/products/texaide/}
+\fi
+.
+
+\end{description}
+
+
+
+
+
+\section{Preguntas espec\'\i{}ficas para el \LaTeX{} en castellano
+ }
+
+
+\subsection{C\'omo puedo usar \TeX{} en castellano? o Qu\'e es lo m\'\i{}nimo que hay que saber para escribir en castellano con \TeX{}/\LaTeX{}?
+ }
+
+En realidad, no es necesario nada adicional que no est\'e ya incluido en
+las distribuciones m\'as habituales. El problema normalmente se reduce a tres cosas:
+\begin{enumerate}
+\item Introducci\'on de caracteres acentuados. V\'eanse las respuestas a las
+preguntas \ref{raw-characters} {(mediante \'ordenes \LaTeX{})},
+\ref{8bitintro} {(C\'omo introducir directamente los caracteres extendidos?)} y
+\ref{acentos-math} {(acentos en modo matem\'atico)}
+\item Literales en castellano. V\'ease la respuesta a la pregunta
+\ref{literales} {(C\'omo cambiar los literales que \LaTeX{} produce?)}.
+\item Patrones de partici\'on de palabras (silabeo o guionado). V\'ease
+\ref{patrones-guionado} {(patrones de guionado)} donde se
+explica c\'omo hacer que \TeX{} parta las palabras siguiendo las
+reglas del espa\~nol.
+\end{enumerate}
+
+
+
+
+
+\subsection{Con \LaTeX{}, c\'omo puedo escribir los acentos y dem\'as caracteres extendidos?
+ \label{acentos}
+ }
+
+
+\subsubsection{Mediante \'ordenes \LaTeX{} \label{raw-characters}
+ }
+
+Cuando no hay m\'as remedio, los caracteres extendidos se escriben as\'\i{}:
+\begin{tscreen}
+\begin{verbatim}
+ ==> \'a ==> \'A ==> \~n ==> ?`
+ ==> \'e ==> \'E ==> \~N ==> !`
+ ==> \'\i{} ==> \'I ==> \"u
+ ==> \'o ==> \'O ==> \"U
+ ==> \'u ==> \'U
+\end{verbatim}
+\end{tscreen}
+
+Sin embargo, \'esto normalmente no es necesario. V\'ease la respuesta a
+la pregunta \ref{8bitintro} {(Introducir directamente los caracteres extendidos)}
+
+
+
+
+\subsubsection{Directamente mediante el paquete {\itshape inputenc\/}\label{8bitintro}
+ }
+
+El paquete {\itshape inputenc\/} permite escribir directamente en la p\'agina
+de c\'odigos habitual, convirti\'endose internamente el texto
+introducido a texto \LaTeX{}, de acuerdo con las diferentes tablas de
+equivalencia para las distintas p\'aginas de c\'odigos y de forma
+completamente transparente al usuario.
+
+Si somos usuarios de UNIX, debemos poner al principio de nuestro
+documento (en lo que se denomina el pre\'ambulo, entre
+{\ttfamily $\backslash$documentclass...} y {\ttfamily $\backslash$begin$\{$document$\}$}) lo
+siguiente:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[latin1]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+si la codificaci\'on es {\ttfamily iso-8889-1} (tambi\'en conocida como
+{\ttfamily latin1}).
+
+Si la codificaci\'on es {\ttfamily utf-8}, como en muchas distribuciones
+recientes de Linux:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[utf8]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+pero si la instalaci\'on es antigua, debe utilizarse el paquete
+{\itshape ucs\/} (en muchas distribuciones se le llama {\itshape latex-ucs\/},
+aunque carga {\itshape ucs.sty\/}):
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{ucs}
+\usepackage[utf-8]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+
+Si trabajamos con MS-Windog hay que usar {\ttfamily cp1252} (que es
+{\itshape casi\/} el {\ttfamily latin1})
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[cp1252]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+({\ttfamily ansinew} es una variante obsoleta).
+Si trabajamos con DOS, hay que poner esto:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[cp850]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+y si somos de Macintosh, esto otro:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[applemac]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+(aunque hay editores de Mac que guardan como {\ttfamily latin1} o {\ttfamily utf8}).
+
+Por lo tanto, el m\'etodo recomendado para utilizar caracteres de 8
+bits en TODAS las plataformas en \LaTeXe{} es escribir:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[tipo]{inputenc}
+\end{verbatim}
+\end{tscreen}
+
+para decir qu\'e p\'agina de c\'odigos de entrada usamos.
+
+Ni este m\'etodo ni el que se menciona en
+\ref{raw-characters} {(acentos \LaTeX{})} son v\'alidos en modo
+matem\'atico.
+
+
+
+
+\subsubsection{C\'omo introducir acentos en modo matem\'atico?\label{acentos-math}
+ }
+
+Para introducir acentos en modo matem\'atico no hay m\'as remedio que
+hacerlo mediante \'ordenes \LaTeX{}, pero en este caso son distintas de
+las de la secci\'on
+\ref{raw-characters} {(acentos \LaTeX{})}. Por ejemplo
+{\itshape m\'ax\/} se escribir\'\i{}a en modo matem\'atico como {\ttfamily m$\backslash$acute$\{$a$\}$x} y
+{\itshape \~n\/} como {\ttfamily $\backslash$tilde$\{$n$\}$}. Si se quiere un acento sobre una i,
+tanto {\itshape spanish\/} para {\itshape babel\/} como el paquete {\itshape dotlessi\/}
+{\ttfamily (CTAN:macros/latex/contrib/supported/bezos/dotlessi.sty)}
+proporcionan la orden {\ttfamily $\backslash$dotlessi}; por ejemplo, m\'\i{}n se
+escribir\'\i{}a {\ttfamily m$\backslash$acute$\{$$\backslash$dotlessi$\}$n}.
+
+
+{\itshape spanish.sty\/} ya proporciona algunas de estas palabras
+acentuadas, por ejemplo, despu\'es de cargar el paquete {\itshape babel\/} con
+la opci\'on {\itshape spanish\/} mediante {\ttfamily $\backslash$usepackage[spanish]$\{$babel$\}$},
+{\ttfamily \$$\backslash$min a\$} permite escribir la palabra acentuada. Tambi\'en
+proporciona un {\ttfamily $\backslash$dotlessi} que complementa a {\ttfamily $\backslash$imath}.
+
+
+
+
+\subsection{Puedo compartir mis archivos \LaTeX{} en los que he escrito los acentos directamente?
+ }
+
+Si los caracteres acentuados est\'an escritos mediante \'ordenes \LaTeX{}
+pueden compartirse sin problemas, ya que se utiliza \'unicamente
+codificaci\'on de 7 bits.
+
+Si introduzco las letras acentuadas directamente como en
+\ref{8bitintro} {(utilizando inputenc)}, tendr\'e dos posibles
+problemas:
+\begin{enumerate}
+\item Me servir\'a para otros ordenadores que utilicen una p\'agina de
+c\'odigos diferente?, pues la segunda mitad del conjunto de
+caracteres es distinta de unos a otros.
+\item Podr\'e enviarlo por correo electr\'onico?, pues solamente acepta 7
+bits.
+\end{enumerate}
+
+C\'omo se soluciona esto? Con GNU {\itshape recode\/}, con MIME, o con las dos
+cosas, seg\'un el caso.
+\begin{enumerate}
+\item Si simplemente se quiere procesar el documento, s\'\i{} que servir\'a
+para otros ordenadores: Ejemplo: Si nosotros tenemos Unix y
+alguien que usa Macintosh nos da (en disquete) un archivo con los
+c\'odigos del Mac, nuestro \LaTeX{} lo entender\'a y lo procesar\'a bien
+si lleva la llamada a {\itshape inputenc\/}, dando el resultado correcto,
+aunque no podamos ver correctamente el texto original con nuestro
+editor de texto.
+Si queremos adem\'as modificar el documento o simplemente ver bien
+o simplemente ver bien el texto sin procesar original,
+necesitaremos convertirlo a la p\'agina de c\'odigos que se utilice
+en nuestro ordenador. Para ello recurriremos a GNU {\itshape recode\/}
+escribiendo:
+\begin{tscreen}
+\begin{verbatim}
+recode applemac:latin1 archivo.tex
+\end{verbatim}
+\end{tscreen}
+
+que nos convierte el documento de la p\'agina de c\'odigos
+{\ttfamily applemac} a la {\ttfamily latin1}. Si ahora modificamos la l\'\i{}nea
+del {\itshape inputenc\/} para que ponga {\ttfamily latin1} en lugar de
+{\ttfamily applemac} todo funciona exactamente igual que antes en
+cuanto al resultado. Magia! D\'onde encontrar fuentes o binarios
+precompilados de {\itshape recode\/}? En los siguientes lugares:
+
+\begin{description}
+\item[fuentes] \mbox{}
+
+En cualquier r\'eplica del archivo GNU, en el
+directorio {\ttfamily recode}.
+
+\item[DOS] \mbox{}
+
+\ifpdf
+\href{ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos_only}{ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos\_only}
+\else
+\onlynameurl{ftp://ftp.simtel.net/pub/simtelnet/gnu/gnuish/dos\_only}
+\fi
+
+o en el mismo lugar en cualquier r\'eplica del archivo
+{\itshape simtel\/}.
+
+\item[DOS32] \mbox{}
+
+\ifpdf
+\href{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/}{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/}
+\else
+\onlynameurl{ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/}
+\fi
+
+o en el mismo lugar en cualquier r\'eplica del archivo {\itshape simtel\/}.
+
+\item[win32] \mbox{}
+
+\ifpdf
+\href{http://www.weihenstephan.de/~syring/win32/UnxUtils.html}{http://www.weihenstephan.de/\~{}syring/win32/UnxUtils.html}
+\else
+\onlynameurl{http://www.weihenstephan.de/\~{}syring/win32/UnxUtils.html}
+\fi
+
+
+\item[unix] \mbox{}
+
+En caso de no tener directamente binarios
+precompilados, suele ser sencillo compilar el programa a
+partir de las fuentes para cada sistema unix concreto.
+
+\end{description}
+
+
+
+
+\item Para evitar problemas con el correo, siempre se puede convertir el
+documento a formato \LaTeX{} {\bfseries antes} de mandarlo por correo.
+Despu\'es de todo, la mayor\'\i{}a de lo que se escribe es para uno
+mismo, no para mandarlo por correo. Ejemplo: Si alguien tiene un
+Mac, para enviar algo por correo debe en primer lugar hacer una
+copia del documento (pues GNU {\itshape recode\/} machaca el
+original). Con la copia se puede hacer:
+\begin{tscreen}
+\begin{verbatim}
+recode -d applemac:latex archivo.tex
+\end{verbatim}
+\end{tscreen}
+
+y ya podemos enviar el {\ttfamily archivo.tex} resultante por correo.
+
+Supongamos que el receptor trabaja con Unix, tendr\'\i{}a que escribir:
+\begin{tscreen}
+\begin{verbatim}
+recode -d latex:latin1 archivo.tex
+\end{verbatim}
+\end{tscreen}
+
+y cambiar el {\ttfamily inputenc}, en su caso.
+En cualquier caso, si es posible, es mucho mejor enviar el
+archivo directamente con acentos utilizando el est\'andar MIME con
+{\itshape quoted-printable\/}, de esta forma llega el archivo con los
+acentos intactos a\'un usando los canales habituales de 7
+bits. Naturalmente debemos ponernos de acuerdo con el receptor
+del mensaje para que \'el tambi\'en tenga un programa que acepte
+MIME, pero dado que es un est\'andar, todo el mundo deber\'\i{}a acabar
+teni\'endolo.
+
+\end{enumerate}
+
+{\itshape Nota al margen\/}: {\ttfamily recode 3.4} no transforma correctamente de
+{\ttfamily 850} a {\ttfamily iso}, porque no convierte bien los retornos de carro. A
+partir de la versi\'on {\ttfamily 3.4.1} se supone que lo hace
+correctamente. Si la versi\'on de {\ttfamily recode} que tenemos es la
+problem\'atica, se puede usar la opci\'on {\ttfamily -a} de {\ttfamily unzip} para
+corregir los retornos de carro. Si nuestro documento no tiene
+may\'usculas acentuadas, se puede usar la opci\'on {\ttfamily ibmpc:l1}
+({\ttfamily ibmpc} es sin\'onimo de {\ttfamily 437}).
+
+
+
+
+\subsection{Por qu\'e cuando se selecciona texto en Adobe Reader o xpdf, desde un documento PDF generado con LaTeX, las letras acentuadas y e\~nes no se copian bien?
+ }
+
+El problema aparece cuando se utiliza un tipo de letra que no utiliza
+la codificaci\'on {\ttfamily T1}, y desaparece cuando se usa.
+
+
+El tipo por omisi\'on de \LaTeX{} es el {\itshape Computer Modern\/} que no
+contiene vocales acentuadas. Cuando el texto usa por ejemplo {\itshape \'a\/},
+\LaTeX{} crea esta letra juntando dos caracteres, una {\ttfamily a} y un
+acento agudo. El aspecto en pantalla y en papel es el correcto, pero
+al seleccionar ese texto en el Acrobat Reader, lo que se obtiene es la
+secuencia {\ttfamily 'a}.
+
+Otros tipos de letra s\'\i{} contienen una letra {\itshape \'a\/}, y si se usa este
+tipo y se indica a \LaTeX{} que use la codificaci\'on {\ttfamily T1}, la
+selecci\'on de texto en Reader ya funcionar\'a bien. As\'\i{} que el problema
+se soluciona siguiendo estos pasos:
+\begin{itemize}
+\item
+Indicarle a \LaTeX{} que use la codificaci\'on {\ttfamily T1}. Esto se logra
+mediante un {\ttfamily $\backslash$usepackage[T1]$\{$fontenc$\}$}.
+\item Disponer de una fuente que realmente use esa codificaci\'on.
+\end{itemize}
+
+Si ponemos {\ttfamily $\backslash$usepackage[T1]$\{$fontenc$\}$} sin m\'as en un documento,
+entonces \LaTeX{} cambia el tipo por omisi\'on, y en vez de {\itshape Computer
+Modern\/}, usar\'a {\itshape European Computer Modern\/} (EC). Si este tipo est\'a
+instalado, el PDF se generar\'a sin problemas y el asunto de seleccionar
+texto quedar\'a arreglado. Pero aparecer\'a otro problema, y es que
+normalmente los tipos EC que vienen instaladas en las distribuciones
+de \LaTeX{} vienen s\'olo en formato PK, que es un formato que despu\'es se
+ve muy mal en el Reader (como borroso y descolocado).
+
+Para esto la soluci\'on t\'\i{}pica sol\'\i{}a ser usar el paquete {\itshape ae\/}, el
+cual instala un tipo virtual, que aparentemente usa la codificaci\'on
+{\ttfamily T1} (para que \LaTeX{} quede contento), pero que en realidad usa
+las fuentes CM en vez de las EC (para poder usar los tipos postscript
+en vez de los PK y as\'\i{} tener un PDF que se vea bien con el
+Reader). Sin embargo esta soluci\'on hace que el problema de la
+selecci\'on de texto reaparezca, ya que, aunque desde el punto de vista
+de \LaTeX{} los tipos {\itshape ae\/} usan codificaci\'on {\ttfamily T1}, la realidad
+es que en el PDF final no lo usa, y la {\itshape \'a\/} sigue siendo una
+combinaci\'on de {\ttfamily a} y {\ttfamily '} (como no pod\'\i{}a ser de otra forma, ya
+que la fuente CM no tiene el car\'acter {\itshape \'a\/}).
+
+As\'\i{} que en este caso el truco de usar el paquete {\itshape ae\/} no sirve, y
+no queda m\'as remedio que recurrir a un tipo que {\itshape realmente\/} use la
+codificaci\'on {\ttfamily T1}, como los tipos Postscript est\'andar (Times-Roman, Palatino, etc.)
+
+Existe una versi\'on postscript de los tipos EC, cuyo desarrollo tiene
+lugar junto al del lenguaje de descripci\'on musical {\itshape lilypond\/} y
+est\'an disponibles en
+\ifpdf
+\href{http://www.lilypond.org/download/fonts/}{http://www.lilypond.org/download/fonts/}
+\else
+\onlynameurl{http://www.lilypond.org/download/fonts/}
+\fi
+. Asimismo los tipos
+{\itshape cm-super\/}, disponibles en {\ttfamily CTAN:fonts/ps-type1/cm-super/}
+tambi\'en aceptan la codificaci\'on {\ttfamily T1}.
+
+Resumiendo, la soluci\'on es bien buscar y usar los tipos {\ttfamily EC} o
+alguno que utilice la codificaci\'on {\ttfamily T1}, o si no compensa el
+esfuerzo utilizar directamente los tipos Postscript est\'andar. Para
+ello basta a\~nadir al pre\'ambulo del documento
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{times} % Usar tipo Times-Roman
+\usepackage[T1]{fontenc} % Usar la codificacin T1
+\end{verbatim}
+\end{tscreen}
+
+Con esto ya funcionar\'a lo de cortar y pegar desde el Reader, aunque
+utilizando otro tipo de letra con otra m\'etrica que puede cambiar la
+maquetaci\'on. En vez de {\itshape times\/} tambi\'en pueden utilizarse
+{\itshape palatino\/} o {\itshape bookman\/}, dependiendo de los gustos.
+
+
+
+
+\subsection{C\'omo cambiar los literales que produce \LaTeX{}?\label{literales}}
+
+Cuando Lamport hizo el \LaTeX{} original, proporcion\'o una serie de estilos
+est\'andar como ejemplo de uso. Estos estilos se hicieron muy populares,
+principalmente porque todas las instalaciones de \LaTeX{} los tienen. Sin
+embargo, estos estilos utilizan unos convenios muy particulares y es f\'acil que
+un usuario desee cambiarlos. Algo especialmente molesto para el uso en
+castellano de los estilos est\'andar, es que generan determinados t\'\i{}tulos
+(p.ej. {\itshape Contents\/}, {\itshape Bibliography\/}, etc.) en ingl\'es, lo que hace
+inaceptable su uso.
+
+Aunque era posible crear versiones modificadas para otros idiomas, se extendi\'o
+la idea de internacionalizar dichos estilos. Por ejemplo, donde pon\'\i{}a la
+palabra {\ttfamily Contents} se ha cambiado por {\ttfamily $\backslash$contentsname} y se define
+aparte el valor de esta macro.
+
+Esta es la forma en que funciona \LaTeXe{} actualmente. De esta manera, es
+posible continuar usando los mismos estilos est\'andar en diferentes idiomas,
+simplemente redefiniendo el valor de estas macros en el documento o en un
+estilo aparte, por ejemplo con
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\contentsname}{Tabla de materias}
+\end{verbatim}
+\end{tscreen}
+
+
+Un paquete de estilos que hace esto es babel -- V\'ease
+\ref{que-es-babel} {(Qu\'e es babel?)}. Cuando se quieren hacer estos
+cambios en un documento que utiliza {\itshape babel\/} con {\itshape spanish.sty\/} hay que
+proceder de una forma un poco distinta. V\'ease
+\ref{sectnames} {(Modificando los literales de spanish.sty)}
+
+
+
+
+\subsection{C\'omo hacer que \LaTeX{} parta correctamente las palabras en castellano?}
+
+
+\subsubsection{Qu\'e configuraciones (o patterns) existen para la partici\'on de palabras?\label{patrones-guionado}}
+
+Lo primero que hay que decir es que la partici\'on en castellano es algo mucho
+m\'as complejo de lo que pudiera parecer a simple vista. Aunque el espa\~nol es un
+lenguaje muy regular, tiene ciertas anomal\'\i{}as que convierten este tema en un
+campo minado. Hay dos conclusiones b\'asicas: 1) No es posible encontrar el 100\%
+de los cortes legales y 2) no es deseable. Para empezar, la Academia permite
+partir tanto por componentes (sub-ur-ba-no) como sil\'abicamente
+(su-bur-ba-no). Adem\'as el concepto de s\'\i{}laba es en algunos casos confuso y la
+etimolog\'\i{}a tampoco ayuda (Ej: su-bli-me, a pesar de derivar de sub-limis,
+contra sub-li-mi-nal). Sin mencionar que los conceptos de diptongo e hiato
+distan mucho de estar claros. Este \'ultimo caso viene a carecer de importancia,
+pues libros de estilo consultados prescriben ignorar los hiatos al partir
+palabras. El siguiente comentario de Fernando M. Fournon Gonz\'alez-Barcia es
+interesante para ilustrar los problemas:
+\begin{quotation}
+"La RAL dice que es POTESTATIVO lo de la separaci\'on por prefijos. Al menos en
+el esbozo, que si somos puristas y nos atenemos a la \'unica gram\'atica v\'alida,
+la del 31, casi ni eso."
+\end{quotation}
+
+\begin{quotation}
+"Creo que, est\'eticamente, lo mejor es no partir nunca, salvo cuando la cosa
+vaya a quedar muy fea (esta recomendaci\'on tambi\'en la hace la RAL), como hace
+el \LaTeX{}, y entonces partir lo m\'as conservadoramente posible. Si para los
+poqu\'\i{}simos casos en que un p\'arrafo se pone pesado y en vez de partir
+subur-bano hay que hacer sub-urbano, pues ..., que se haga a mano, no?."
+\end{quotation}
+
+\begin{quotation}
+"Otra cosa es que al partir surjan vocablos malsonantes. Esto S\'I que deber\'\i{}a
+de comprobarlo cualquier separador de palabras, pues normalmente es muy
+dif\'\i{}cil detectarlos a simple vista (si es que hay tiempo para releer nuestros
+propios art\'\i{}culos). O sea, que antes que una lista de prefijos, sugerir\'\i{}a la
+creaci\'on de una lista de {\itshape tacos\/} y cacofon\'\i{}as varias. :-)"
+\end{quotation}
+
+Es decir, lo mejor es evitar cualquier caso conflictivo en los patrones
+({\itshape patterns\/}) de uso general. Localmente puede hacerse los que se quiera,
+usando excepciones o introduci\'endolos a mano, por ejemplo.
+
+Al d\'\i{}a de hoy existen 4 tablas diferentes de partici\'on:
+\begin{itemize}
+\item Los producidos en 1986 por Armando Jinich, Mar\'\i{}a Garza y Max D\'\i{}az de Aurion
+Tecnolog\'\i{}a, M\'exico. Est\'an en el dominio p\'ublico desde 1990. Pueden encontrarse
+en:
+\begin{quotation}
+\ifpdf
+\href{ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex}{ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex}
+\else
+\onlynameurl{ftp://ftp.dante.de/tex-archive/language/spanish/old/silaba.tex}
+\fi
+\end{quotation}
+
+Estos patrones han sido producidos a partir de las reglas de la
+gram\'atica. Actualmente no soportan expl\'\i{}citamente acentos. Max D\'\i{}az es
+actualmente {\ttfamily max \_AT\_ east.aurora.com}
+\item Los producidos por Manuel V\'azquez de la Universidad de Zaragoza, que puede ser
+localizado en {\ttfamily (vazquez \_AT\_ cc.unizar.es)}. Estos patrones est\'an basados
+en la gram\'atica.
+\item Los que distribuye Arbortext producidos por Sistemas Gr\'aficos y Audiovisuales
+de Chihuahua. M\'exico. Estos est\'an generados a partir de un
+diccionario. Soportan acentos.
+\item Los producidos por Julio S\'anchez, que pueden obtenerse en:
+\begin{tscreen}
+\begin{verbatim}
+CTAN:language/spanish/hyphen
+\end{verbatim}
+\end{tscreen}
+
+Estos soportan una variedad de opciones, incluido el soporte de acentos, tanto
+como ligaduras como con el c\'odigo {\ttfamily IS 8859/1} ({\ttfamily ISO Latin1}) para
+ML-\TeX{} o \TeX{} 3.X. Adem\'as, {\itshape son los actualmente recomendados por
+Cervan\TeX{}\/}.
+\end{itemize}
+
+
+
+
+
+\subsubsection{C\'omo activo el patr\'on de partici\'on de palabras para el castellano?\label{guionado}}
+
+Para activar el patr\'on de partici\'on para el castellano es necesario tener
+babel -- V\'ease \ref{que-es-babel} {(Qu\'e es babel?)} -- instalado y
+generar el formato cargando el patr\'on de separaci\'on en s\'\i{}labas en
+castellano. Esto podemos hacerlo de la siguiente manera
+
+\begin{description}
+\item[Para \TeX{} y \LaTeX{}: Cambiando el archivo {\ttfamily language.dat}] \mbox{}
+
+\begin{itemize}
+\item Editar el archivo {\ttfamily language.dat}. Dependiendo de la distribuci\'on de \TeX{}
+utilizada este archivo puede estar en distintos lugares. Por ejemplo en
+te\TeX{} el \'arbol de \TeX{} parte de {\ttfamily TEXMF=/usr/share/texmf} y el
+archivo en cuesti\'on est\'a en {\ttfamily TEXMF/tex/generic/config/language.dat}. En
+al caso de {\itshape Debian/GNU-Linux\/}, est\'a en {\ttfamily /etc/texmf/language.dat}
+y el otro es un enlace a \'este.
+\item Borrar el {\ttfamily \%} que est\'a al principio de la linea {\ttfamily spanish}. Si mal no
+recuerdo viene preparado con silabeo en alem\'an, si no lo
+quieren pongan un {\ttfamily \%} adelante. Tambi\'en viene predefinido
+ingl\'es (o alguna de sus variantes, por ejemplo
+american). \'Este debe estar siempre definido as\'\i{} que no debe
+desactivarse.
+\item Es conveniente tambi\'en verificar que la l\'\i{}nea con {\ttfamily nohyphenation} est\'a
+activada (sin el comentario). \'Esto es muy \'util cuando se quiere desactivar la
+partici\'on de palabras.
+\item En caso de tener el Mik\TeX{}, la operaci\'on es la misma, pero el archivo
+{\ttfamily language.dat} est\'a en {\ttfamily TEXMF$\backslash$tex$\backslash$generic$\backslash$hyphen$\backslash$local} o en
+{\ttfamily TEXMF$\backslash$tex$\backslash$generic$\backslash$config} donde {\ttfamily TEXMF} representa el punto del
+que parte el \'arbol de directorios \TeX{}
+\item te\TeX{} tiene la utilidad {\itshape texconfig\/} que invocada como
+\begin{tscreen}
+\begin{verbatim}
+# texconfig hyphen latex
+\end{verbatim}
+\end{tscreen}
+
+lanza un editor para cambiar el fichero {\ttfamily language.dat} y que, al cerrar el
+editor, genera los formatos autom\'aticamente, por lo que no es necesario hacer
+el paso siguiente expl\'\i{}citamente.
+\end{itemize}
+
+
+
+
+\item[Para \LaTeX{}.] \mbox{}
+
+Una vez hecho lo anterior no es necesario m\'as que rehacer los formatos
+-- V\'ease \ref{formatos} {(C\'omo rehacer los formatos?)} --. Entonces
+cuando se llame a {\itshape babel\/} con la opci\'on {\ttfamily spanish}, \'este se encargar\'a de
+utilizar los patrones de guionado en castellano.
+
+
+
+\item[Para {\ttfamily plain}-\TeX{}] \mbox{}
+
+Por omisi\'on, cuando el {\ttfamily initex} crea el formato, carga el archivo
+{\ttfamily hyphen.tex} que contiene las reglas de silabeo en ingl\'es. Para activarlo
+tambi\'en en {\itshape plain-\TeX{}\/} se debe copiar el archivo {\ttfamily hyphen.cfg} como
+{\ttfamily hyphen.tex} en alg\'un sitio que en el camino de b\'usqueda de \TeX{} est\'e
+antes del {\ttfamily hyphen.tex} que viene como parte de {\ttfamily plain-\TeX{}} y
+asegurarse que existe el archivo {\ttfamily ushyph1.tex} (que realmente es el mismo
+que el {\ttfamily hyphen.tex} original, pero con otro nombre). Este paso no es
+necesario si s\'olo se quiere la partici\'on de palabras para \LaTeX{} y se va a
+utilizar {\itshape babel\/}, pero tampoco sobra.
+
+Para los usuarios de {\itshape te\TeX{}\/} los archivos est\'an en
+{\ttfamily TEXMF/tex/config/babel/hyphen.cfg} y el {\ttfamily hyphen.tex} original en
+{\ttfamily TEXMF/tex/generic/hyphen/hyphen.tex}
+
+
+Para los usuarios de Mik\TeX{}, los archivos est\'an en
+{\ttfamily TEXMF/generic/hyphen/hyphen.cfg} y {\ttfamily TEXMF/generic/hyphen/hyphen.tex}
+
+En caso de no conseguirse hacer lo anterior tambi\'en puede sustituirse el
+archivo {\ttfamily hyphen.tex} por el {\ttfamily hyphen.cfg}, pero debe tenerse cuidado al
+actualizar la distribuci\'on de no sobreescribir el {\ttfamily hyphen.tex} con al que
+venga con la distribuci\'on nueva.
+
+Entonces es necesario reconstruir el formato como se indica en
+\ref{formatos} {(C\'omo rehacer los formatos?)}.
+
+Cuando se quiere usar el silabeo en castellano, hay que agregar en el archivo
+{\ttfamily .tex}, al principio, una linea que diga {\ttfamily $\backslash$language1} si el castellano
+es el segundo lenguaje (no sin\'onimo) del {\ttfamily language.dat} ({\ttfamily $\backslash$language0}
+corresponder\'\i{}a al ingl\'es americano)
+
+\end{description}
+
+
+
+
+
+\subsubsection{A pesar de que he activado los patrones de partici\'on de palabras del castellano, hay una palabra que se me resiste}
+
+Aunque los patrones de partici\'on de palabras intentan abarcar el mayor n\'umero de
+casos posible, siempre puede quedar alguna palabra
+recalcitrante. Tambi\'en puede ocurrir que la partici\'on sea correcta,
+pero no deseable a los ojos del autor del documento. En este caso
+hay dos posibilidades:
+\begin{itemize}
+\item Si la palabra es poco frecuente y s\'olo falla en muy pocas ocasiones. En este
+caso es preferible decirle directamente a la palabra en el lugar
+donde aparece, d\'onde se le permite partirse, mediante
+{\ttfamily $\backslash$-}. Por ejemplo:
+\begin{tscreen}
+\begin{verbatim}
+fotorrefractivo y electroptico --> foto\-rre\-frac\-tivo y elec\-tro\-ptico
+\end{verbatim}
+\end{tscreen}
+\item Si es una palabra frecuente que es una potencial causa de problemas en el
+documento. En este caso es preferible definir en el pre\'ambulo
+del documento c\'omo se permite la partici\'on de esta palabra de
+forma global para todo el documento, mediante
+{\ttfamily $\backslash$hyphenation}. Por ejemplo:
+\begin{tscreen}
+\begin{verbatim}
+\hyphenation{foto-rre-frac-tivo,elec-tro-ptico}
+\end{verbatim}
+\end{tscreen}
+\end{itemize}
+
+
+
+
+
+\subsubsection{Mi \TeX{} no parte las palabras que tienen acentos. Por qu\'e?}
+
+El primitivo {\ttfamily $\backslash$accent} detiene la partici\'on. Es posible ayudar a \TeX{}
+invocando la siguiente macro despu\'es de un acento:
+\begin{tscreen}
+\begin{verbatim}
+\def\allowhyphens{\penalty10000 \hskip0pt}
+\end{verbatim}
+\end{tscreen}
+
+{\ttfamily spanish.sty} lo hace autom\'aticamente en caso necesario. En cualquier caso,
+lo mejor es usar fuentes con las letras acentuadas como por ejemplo
+las descritas en \ref{EC/DC} {(DC/EC)}, o ML-\TeX{}, y
+patrones de partici\'on que contemplen esto.
+
+
+
+
+\subsection{Acerca de {\ttfamily spanish.sty}}
+
+Los archivos para escribir en castellano con {\itshape babel\/} ({\ttfamily spanish.*}) los
+cre\'o y mantuvo durante mucho tiempo Julio S\'anchez. Ahora esos archivos los
+mantiene Javier Bezos y desde hace tiempo son oficiales en la estructura de
+{\itshape babel\/}. Es posible que alguna distribuci\'on de \LaTeX{} a\'un utilice los
+archivos antiguos y que haya algunas diferencias respecto de lo que aqu\'\i{} se
+describe. La actualizaci\'on est\'a m\'as que recomendada.
+
+
+
+
+\subsubsection{D\'onde se puede obtener la documentaci\'on de spanish en castellano? }
+
+La documentaci\'on de {\itshape spanish\/} que se incluye al componer {\ttfamily user.drv} est\'a
+en ingl\'es, pero el archivo {\ttfamily spanish.dtx} tambi\'en la incluye en
+castellano. Basta con componer este archivo y obtendremos un detallado manual
+como {\ttfamily spanish.dvi}.
+
+La versi\'on m\'as reciente del manual de {\itshape spanish.sty\/} se encuentra en
+\ifpdf
+\href{http://perso.wanadoo.es/jbezos/archive/spanish.pdf}{http://perso.wanadoo.es/jbezos/archive/spanish.pdf}
+\else
+\onlynameurl{http://perso.wanadoo.es/jbezos/archive/spanish.pdf}
+\fi
+. Debe
+tenerse cuidado con las versiones, pues puede referirse a una versi\'on muy
+posterior a la que se encuentra instalada en el sistema.
+
+
+
+
+\subsubsection{C\'omo cambio los nombres de las secciones de bibliograf\'\i{}a, \'\i{}ndice, etc... que pone {\ttfamily spanish.sty}? \label{sectnames}}
+
+Si no importa que este cambio no siga las caracter\'\i{}sticas de {\itshape babel\/} y
+{\itshape spanish\/} de cambio de idioma sobre la marcha, etc.., se puede hacer de la
+misma forma que en la secci\'on \ref{literales} {(C\'omo cambiar los literales que produce \LaTeX{}?)} poniendo las
+definiciones despu\'es de llamar a babel. El problema de este m\'etodo es que no
+est\'a bien integrado con {\itshape babel\/} y por ese lado puede dar problemas, ya
+{\itshape babel\/} activa algunos cambios al llegarse al {\ttfamily $\backslash$begin$\{$document$\}$}.
+
+Si embargo existe una forma m\'as elegante e integrada con {\itshape spanish\/} y
+{\itshape babel\/}. En el pre\'ambulo del documento hay que a\~nadir lo siguiente, por
+ejemplo, para cambiar Bibliograf\'\i{}a por Referencias y Tabla por Cuadro
+\begin{tscreen}
+\begin{verbatim}
+\addto\captionsspanish{%
+\def\bibname{Referencias}%
+\def\tablename{Cuadro}%
+}
+\end{verbatim}
+\end{tscreen}
+
+Y as\'\i{} con todos los nombres necesarios. La lista de nombres est\'a en los dos
+lugares siguientes
+\begin{tscreen}
+\begin{verbatim}
+TEXMF/tex/generic/babel/spanish.ldf
+TEXMF/tex/generic/babel/spanish.tex
+\end{verbatim}
+\end{tscreen}
+
+{\itshape Nunca\/} deben modificarse los ficheros {\itshape spanish.ldf\/} y {\itshape spanish.tex\/}
+directamente, ya que el documento resultante ya no ser\'\i{}a universal, al
+procesarlo en un sistema distinto dar\'\i{}a distinto resultado, y no ser\'\i{}a posible
+acompa\~nar el documento original con los archivos de estilo modificados puesto
+que la LPPL (la licencia bajo la que se distribuye \LaTeX{}) no permite la
+distribuci\'on de versiones modificadas de \'estos bajo el mismo nombre.
+
+
+
+
+\subsubsection{Por qu\'e {\ttfamily spanish.sty} pone los meses en min\'uscula?}
+
+Ese es el uso aceptado en la actualidad. Documentos de la propia RAL lo hacen
+as\'\i{}. El Mar\'\i{}a Moliner tambi\'en. V\'ease la siguiente cita del Mar\'\i{}a
+Moliner, 1990,
+\begin{quotation}
+"7. Aunque entre los preceptos de la G.R.A. figura el de escribir con may\'uscula
+los nombres de los meses, de los d\'\i{}as de la semana y de las
+estaciones, {[}...] ha dejado decididamente de usarse la letra
+may\'uscula en uno y otro de estos casos"
+\end{quotation}
+
+
+
+
+
+\subsubsection{Por qu\'e el spanish de babel reemplaza el punto decimal por una coma?}
+
+Por tres razones: 1) porque las normas internacionales establecen que ha de
+usarse coma para los decimales, excepto en aquellos pa\'\i{}ses cuya tradici\'on hace
+preferible el punto (la propia ISO usa coma en sus informes); 2) porque el
+punto decimal en Espa\~na carece de fuerza legal y s\'olo la coma es oficialmente
+v\'alida, y 3) porque la coma es el \'unico signo usado en la vida
+diaria. Probablemente, la situaci\'on es similar en otros pa\'\i{}ses, salvo M\'exico.
+
+Se puede cambiar el comportamiento predefinido con la orden
+{\ttfamily $\backslash$decimalpoint} o {\ttfamily $\backslash$spanishdecimal$\{$.$\}$} en el pre\'ambulo, despu\'es
+de cargar {\itshape babel\/}. En unas pocas materias, como el an\'alisis n\'umerico o la
+estad\'\i{}stica, es necesario distinguir la coma decimal de la coma para separar
+datos; en este caso se puede aumentar el espaciado de estas \'ultimas con:
+\begin{tscreen}
+\begin{verbatim}
+\makeatletter
+\def\es@decimal{{\mathchar"613B}}
+\mathcode`,="8000
+\begingroup
+\catcode`,=13
+\gdef,{\mkern2mu\mathchar"613B\mkern8mu}
+\endgroup
+\makeatother
+\end{verbatim}
+\end{tscreen}
+
+(Se pueden probar otros valores en lugar de 2 {[}antes] y 8 {[}despu\'es]. La unidad
+mu de \TeX{} es para matem\'aticas {[}aprox. 1/18 em].)
+
+
+
+
+\subsubsection{Por qu\'e {\ttfamily spanish.sty} pone los n\'umeros romanos siempre en may\'uscula?}
+
+Realmente no son may\'usculas, sino versalitas ({\itshape small caps\/}). En la
+tradici\'on tipogr\'afica espa\~nola no se utilizan los n\'umeros romanos en
+min\'usculas, que se sustituyen por las versalitas. Por este motivo, el autor de
+{\itshape spanish\/} para babel, lo ha incluido en \'este.
+
+
+
+
+\subsubsection{Por qu\'e {\ttfamily spanish.sty} acent\'ua la I de \'Indice?}
+
+As\'\i{} lo han sostenido los tratadistas m\'as importantes sobre ortograf\'\i{}a y
+tipograf\'\i{}a desde hace m\'as de un siglo: $<$$<$ La may\'usculas deben llevar la
+tilde que les corresponda $>$$>$ (Sanmart\'\i{}, 1907). La RAE finalmente lo ha
+considerado normativo en su ortograf\'\i{}a de 1999: $<$$<$El empleo de las
+may\'usculas no exime de poner tilde cuando as\'\i{} lo exijan las reglas de
+acentuaci\'on $>$$>$ (p. 31).
+
+
+
+
+\subsubsection{Por qu\'e spanish para babel dice cuadro en lugar de tabla?}
+
+Tal y como se indica en el manual, el ingl\'es {\itshape table\/} y el espa\~nol
+{\itshape tabla\/} son falsos amigos. Para ser m\'as precisos, podemos reproducir lo que
+dice el Diccionario acad\'emico:
+\begin{quotation}
+
+Cuadro {[}...] 10. m. Conjunto de nombres, cifras u otros datos presentados
+gr\'aficamente, de manera que se advierta la relaci\'on existente entre ellos.
+Tabla {[}...] 12. f. Cuadro o cat\'alogo de n\'umeros de especie determinada,
+dispuestos en forma adecuada para facilitar los c\'alculos. Tabla de
+multiplicar, de logaritmos, astron\'omica.
+
+\end{quotation}
+
+El ingl\'es {\itshape table\/} tiene un sentido mucho m\'as general que el que tiene el
+espa\~nol {\itshape tabla\/}, y as\'\i{} tendr\'\i{}amos tabla de logaritmos y tabla de
+multiplicar frente a cuadro de reyes medievales y cuadro de amino\'acidos
+esenciales. En este aspecto el espa\~nol tiene m\'as riqueza y precisi\'on que el
+ingl\'es.
+
+En fin, {\itshape cuadro\/} es todav\'\i{}a la forma m\'as frecuente, la m\'as castellana y
+tradicional, y la preferida por los mejores tip\'ografos (Morato, Mart\'\i{}nez
+Sicluna, Mart\'\i{}nez de Sousa, etc.). Nada impide, por supuesto, redefinir el
+nombre si resultara que todos los cuadros de un documento son tablas, tal y
+como describe el manual y esta FAQ.
+
+
+
+
+\subsubsection{C\'omo consigo que {\itshape babel\/} y {\ttfamily spanish.sty} no utilicen los atajos de teclado NUNCA?}
+
+Este ha sido un problema muy frecuente con babel y spanish, que ha dado como
+consecuencia que, por ejemplo, en las bibliograf\'\i{}as nombres como
+"J.~N. Apellido" aparecieran como "J.\~N. Apellido". Para solucionar este
+problema, spanish ofrece ahora la orden {\ttfamily $\backslash$deactivatetilden} que elimina
+el uso de {\ttfamily \~{}} para la e\~ne, al tiempo que preserva su funci\'on de espacio sin
+divisi\'on (la orden {\ttfamily $\backslash$shorthandoff} de babel cancela ambos usos). El
+estilo {\itshape spanish\/} tambi\'en proporciona m\'as facilidades para desactivar otras
+abreviaciones, que est\'an descritas en {\ttfamily spanish.dtx}, por ejemplo
+{\ttfamily $\backslash$deactivatequoting} en el pre\'ambulo.
+
+Sin embargo \'esto y el que funcione correctamente ha cambiado mucho entre
+distintas versiones de {\itshape babel\/} lo que hace que a veces los documentos
+creados con una versi\'on de babel no sean directamente portables a otros
+sistemas. Aunque es recomendable actualizarse a la \'ultima versi\'on de
+{\itshape spanish\/} y {\itshape babel\/} en todos los ordenadores implicados, en caso de no
+poderse hacer, la siguiente l\'\i{}nea (en \LaTeXe{}) en el pre\'ambulo del documento
+elimina los atajos de teclado
+\begin{tscreen}
+\begin{verbatim}
+\AtBeginDocument{\gdef~{\nobreakspace{}}\catcode`\"=12}
+\end{verbatim}
+\end{tscreen}
+
+\'util para documentos que se utilizar\'an en distintos ordenadores, alguno de
+ellos con versiones antiguas de babel o spanish.
+
+
+
+
+\subsection{C\'omo puedo indicar la abreviatura de los ordinales?
+ }
+
+En \LaTeXe{} pueden utilizarse la \'ordenes {\ttfamily $\backslash$textordfeminine} y
+{\ttfamily $\backslash$textordmasculine}; por ejemplo, para abreviar Mar\'\i{}a,
+escribimos {\ttfamily M.$\backslash$textordfeminine}. Una variaci\'on de estas macros
+ha sido incorporada a {\ttfamily spanish.sty} versi\'on 3.0 y extendida en la
+versi\'on 4.0. Se invocan como "a y "o, respectivamente, con la
+posibilidad de usar {\ttfamily $\backslash$sptext} para casos como {\ttfamily 1$\backslash$sptext$\{$er$\}$}.
+
+
+
+
+\subsection{C\'omo forzar sangr\'\i{}a despu\'es de las cabeceras?
+ }
+
+El objetivo de esa sangr\'\i{}a ({\itshape indentation\/} para los que no est\'en al
+tanto) es marcar claramente la separaci\'on de los p\'arrafos. Como tal,
+es superflua despu\'es de una cabecera. Hay otros sitios en los que, no
+s\'olo es superflua, sino que es confusa, como despu\'es de un texto que
+ya va sangrado (entorno quote, {\ttfamily $\backslash$[} {\ttfamily $\backslash$]}, un array,
+etc.) Sin embargo, es esencialmente una cuesti\'on de gusto.
+
+Modificarlo en un estilo es bastante f\'acil. La mayor\'\i{}a de las
+secciones, etc. en \LaTeX{} son algo as\'\i{} como (en {\ttfamily art10.sty}):
+\begin{tscreen}
+\begin{verbatim}
+\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus
+-1ex minus -.2ex}{2.3ex plus .2ex}{\Large\bf}}
+\def\subsection{\@startsection{subsection}{2}{\z@}{-3.25ex plus
+ -2ex minus -.2ex}{1.5ex plus .2ex}{\large\bf}}
+\end{verbatim}
+\end{tscreen}
+
+El cuarto par\'ametro, si es negativo, indica que no se debe sangrar en
+el primer p\'arrafo tras la cabecera. C\'ambiese a positivo.
+
+Hay otro procedimiento para estilos que ya est\'an escritos y consiste
+en decir:
+\begin{tscreen}
+\begin{verbatim}
+\let\@afterindentfalse\@afterindenttrue
+\@afterindenttrue
+\end{verbatim}
+\end{tscreen}
+
+Esta soluci\'on es la proporcionada en {\ttfamily indentfirst.sty} por David
+Carlisle.
+
+
+
+
+\subsection{C\'omo puedo escribir las funciones matem\'aticas en espa\~nol?
+ }
+
+Comentario: Hay gente que discute el que las funciones vayan en
+espa\~nol y lleve acento el l\'\i{}m, m\'ax, etc. Argumentan que los nombres
+vienen del lat\'\i{}n y all\'\i{} no hab\'\i{}a acentos (y que en ingl\'es tambi\'en
+vienen del lat\'\i{}n, lo cual, por ejemplo, es claramente incierto con
+gcd). El caso es que en todos los libros tradicionales en castellano
+se escrib\'\i{}a l\'\i{}m y m\'ax con acento. Si \'ultimamente no se hace es
+precisamente porque \TeX{} (en ingl\'es) no lo tiene as\'\i{}. Todav\'\i{}a estamos
+a tiempo de no cometer ese error:
+
+El caso m\'as com\'un es el del seno que, en plain \TeX{}, basta definirlo como
+\begin{tscreen}
+\begin{verbatim}
+\def\sen{\mathop{\rm sen}\nolimits} % Sustituye a \sin
+\end{verbatim}
+\end{tscreen}
+
+An\'alogamente,
+\begin{tscreen}
+\begin{verbatim}
+\def\mcd{\mathop{\rm mcd}\nolimits} % Sustituye a \gcd
+
+\def\senh{\mathop{\rm senh}\nolimits} % Sustituye a \sinh
+
+\def\arcsen{\mathop{\rm arcsen}\nolimits} % Ni el arcsin ni el
+% arccos originales dejan espacio entre arc y sin o cos.
+\end{verbatim}
+\end{tscreen}
+
+Cuando la funci\'on en espa\~nol tiene alg\'un acento (sobre todo en la i), es m\'as complicado:
+\begin{tscreen}
+\begin{verbatim}
+\def\max{\mathop{\rm m\acute ax}}
+
+\def\min{\mathop{\rm m\acute\mathchar"7010n}}
+
+\def\inf{\mathop{\rm \acute\mathchar"7010nf}}
+
+\def\lim{\mathop{\rm l\acute\mathchar"7010m}}
+
+\def\limsup{\mathop{\rm l\acute\mathchar"7010m\, sup}} % El limsup
+% y el liminf originales dejan espacio entre lim y sup o inf.
+
+\def\liminf{\mathop{\rm l\acute\mathchar"7010m\, inf}}
+\end{verbatim}
+\end{tscreen}
+
+Por \'ultimo, adapt\'andolas de su definici\'on original (ver p\'ag. 361 del
+\TeX{}book) para poner el acento en las dos posibilidades de uso de
+{\ttfamily mod} hacemos:
+\begin{tscreen}
+\begin{verbatim}
+\def\bmod{\mskip-\medmuskip \mkern5mu
+ \mathbin{\rm m\acute od} \penalty900 \mkern5mu
+ \mskip-\medmuskip}
+\def\pmod#1{\allowbreak \mkern18mu ({\rm m\acute od}\,\,#1)}
+\end{verbatim}
+\end{tscreen}
+
+En \LaTeX{} se puede hacer de forma similar pero usando
+{\ttfamily $\backslash$newcommand} o {\ttfamily $\backslash$renewcommand} en lugar de
+{\ttfamily $\backslash$def}.
+
+
+
+
+\subsection{Qu\'e verificadores ortogr\'aficos puedo utilizar para espa\~nol?}
+
+\begin{description}
+\item[ispell] \mbox{}
+
+{\itshape ispell\/} es un verificador ortogr\'afico de uso libre que funciona
+en UNIX, aunque hay un port para {\itshape emx\/} en fase beta --que funciona o debe
+funcionar tanto en DOS (con 386 o superior) como en OS/2 2.x o en OS/2 Warp.
+
+Para {\itshape ispell\/} existe lo siguiente:
+
+\begin{itemize}
+\item Ficheros de afijos para espa\~nol:
+\begin{center}
+\begin{tabular}{ll}
+URL:& ftp://ftp.dante.de/tex-archive/language/spanish/ispell\\
+ARCHIVO:& castellano.aff.gz\\
+COMENTARIOS:& diccionario y parche elisp disponible en el mismo lugar.\\
+& V\'eanse los archivos LEEME o README.
+\end{tabular}
+\end{center}
+
+\begin{center}
+\begin{tabular}{ll}
+URL:&
+\ifpdf
+\href{http://www.datsi.fi.upm.es/~coes}{http://www.datsi.fi.upm.es/\~{}coes}
+\else
+\onlynameurl{http://www.datsi.fi.upm.es/\~{}coes}
+\fi
+\\
+ARCHIVOS:& espa\~{}nol.tar.gz\\
+COMENTARIOS:& incluye espa\~{}nol.aff, lista de palabras,instrucciones\\
+& y patrones de guionado para TeX en espa\~nol.
+\end{tabular}
+\end{center}
+
+
+\item Diccionarios compatibles con ispell:
+\begin{center}
+\begin{tabular}{ll}
+URL:& ftp://ftp.dante.de/tex-archive/language/spanish/ispell\\
+ARCHIVOS:& palabras.sq.gz\\
+COMENTARIOS:& archivo de afijos y parche elisp disponible en el mismo\\
+& lugar. V\'eanse los archivos LEEME o README.
+\end{tabular}
+\end{center}
+
+\begin{center}
+\begin{tabular}{ll}
+URLs:&
+\ifpdf
+\href{http://www.datsi.fi.upm.es/~coes}{http://www.datsi.fi.upm.es/\~{}coes}
+\else
+\onlynameurl{http://www.datsi.fi.upm.es/\~{}coes}
+\fi
+\\
+ARCHIVOS:& espa\~{}nol.tar.gz\\
+COMENTARIOS:& incluye espa\~{}nol.aff, lista de palabras,instrucciones,\\
+& y patrones de guionado para TeX en espa\~nol.
+\end{tabular}
+\end{center}
+
+
+\end{itemize}
+
+El que hay en {\ttfamily ftp.dante.de} es de Julio S\'anchez y el que hay en
+\ifpdf
+\href{http://www.datsi.fi.upm.es/~coes}{http://www.datsi.fi.upm.es/\~{}coes}
+\else
+\onlynameurl{http://www.datsi.fi.upm.es/\~{}coes}
+\fi
+ es de Santiago Rodr\'\i{}guez
+{\ttfamily srodri \_AT\_ fi.upm.es} y Jes\'us Carretero {\ttfamily jesus \_AT\_ fi.upm.es}
+
+Dependiendo de como se haya creado el diccionario de castellano es posible
+que deba llamarse a ispell como
+\begin{tscreen}
+\begin{verbatim}
+ispell -t -T latin1 -d espanol fichero.tex
+\end{verbatim}
+\end{tscreen}
+
+especificando expl\'\i{}citamente la codificaci\'on.
+
+
+
+\item[Excalibur] \mbox{}
+
+Para Macintosh, existe un verificador ortogr\'afico de documentos
+\LaTeX{} (y plain \TeX{}) llamado Excalibur. Es gratis, aunque el copyright es
+del autor, Rick Zaccone {\ttfamily (zaccone \_AT\_ bucknell.edu)}.
+
+Excalibur puede conseguirse por ftp an\'onimo en
+\ifpdf
+\href{ftp://sol.eg.bucknell.edu/pub/mac}{ftp://sol.eg.bucknell.edu/pub/mac}
+\else
+\onlynameurl{ftp://sol.eg.bucknell.edu/pub/mac}
+\fi
+.
+
+Juan Luis Varona {\ttfamily (jvarona \_AT\_ dmc.unirioja.es)} ha creado un diccionario con
+292342 palabras (versi\'on de septiembre de 1999) que funciona con
+Excalibur. Est\'a realizado en formato de 7 bits, y la {\ttfamily \'\i{}} la reconoce
+\'unicamente como {\ttfamily $\backslash$'$\{$$\backslash$i$\}$}. Pero puede modificarse si se desea. La
+versi\'on m\'as reciente puede encontrarse en
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/dict-mac}{ftp://tex.unirioja.es/pub/tex/dict-mac}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/dict-mac}
+\fi
+
+
+Asimismo, en la direcci\'on mencionada para {\itshape Excalibur\/}, en el directorio
+{\ttfamily Excalibur-dictionaries}, se encuentran disponibles los diccionarios de los
+distintos idiomas. El diccionario espa\~nol puede encontrarse tambi\'en en
+{\ttfamily CTAN} en
+\begin{tscreen}
+\begin{verbatim}
+CTAN:systems/mac/support/excalibur/Spanish_Dictionary.sit.hqx
+\end{verbatim}
+\end{tscreen}
+
+
+\item[4spell] \mbox{}
+
+{\itshape 4spell\/} es un verificador ortogr\'afico para Windows (32 bits)
+que se distribuye bajo una licencia libre (concretamente la GPL) y tiene un
+diccionario de castellano. Puede encontrarse en {\ttfamily CTAN:support/4spell}
+
+\item[Winedt] \mbox{}
+
+El diccionario de Juan Luis Varona tambi\'en se ha adaptado para su uso con el
+verificador ortogr\'afico del entorno winedt para Windows. Est\'a disponible en
+\begin{quotation}
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/dict-win}{ftp://tex.unirioja.es/pub/tex/dict-win}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/dict-win}
+\fi
+\end{quotation}
+
+
+\item[amspell] \mbox{}
+
+{\itshape amspell\/} es un verificador ortogr\'afico para DOS. El
+diccionario de Juan Luis Varona tambi\'en se ha adaptado para ser utilizado con
+{\itshape amspell\/}. La versi\'on para {\itshape amspell\/} est\'a disponible en
+\begin{quotation}
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/dict-pc}{ftp://tex.unirioja.es/pub/tex/dict-pc}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/dict-pc}
+\fi
+\end{quotation}
+
+y {\itshape amspell\/} en
+\begin{tscreen}
+\begin{verbatim}
+CTAN:support/amspell
+\end{verbatim}
+\end{tscreen}
+
+
+\end{description}
+
+
+
+
+
+\subsection{C\'omo utilizo Bib\TeX{} en castellano?}
+
+Para esto hay dos aproximaciones,
+
+
+\subsubsection{Utilizar estilos adaptables (los {\itshape abstyles\/})
+ }
+
+Para que Bib\TeX{} funcione en espa\~nol, Tom\'as Bautista ha modificado con
+{\itshape babel\/} una {\itshape familia adaptable\/} de estilos de Bib\TeX{} (tambi\'en
+llamadas {\itshape abstyles\/}).
+
+Con las {\itshape abstyles\/} se tiene la {\itshape ventaja\/} de utilizar un \'unico estilo,
+de forma que el idioma de las referencias \'unicamente depende del elegido con
+{\itshape babel\/}. De este modo, si por h o por b, en cierto momento no se quiere
+el documento en ingl\'es, sino por ejemplo en espa\~nol o en alem\'an, s\'olo habr\'\i{}a
+que cambiar la opci\'on que corresponde en babel y no tambi\'en el estilo puesto
+dentro del {\ttfamily $\backslash$bibliographystyle$\{$estilo$\}$}.
+
+Adem\'as, con las abstyles s\'olo es necesario un {\ttfamily aplain.bst} preparado
+para distintos idiomas, seg\'un lo elegido en babel. Est\'an disponibles en
+{\ttfamily CTAN:biblio/bibtex/contrib/abstyles-babel/}.
+
+
+\subsubsection{Utilizar el paquete {\ttfamily custom-bib}\label{custombib}
+ }
+
+El paquete {\itshape custom-bib\/} (disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/custom-bib/}) permite crear
+estilos bibliogr\'aficos a medida, con una amplia serie de opciones y de
+idiomas. Para utilizarlo, una vez desempaquetado debe hacerse
+\begin{tscreen}
+\begin{verbatim}
+latex makebst.tex
+\end{verbatim}
+\end{tscreen}
+
+y responder a las (muchas) preguntas que se formulan. Es conveniente leerse
+previamente la documentaci\'on para ser consciente de qu\'e se est\'a preguntando
+en cada momento, ya que muchas de las preguntas no son obvias. El documento
+de Luis Seidel -- V\'ease la secci\'on
+\ref{es-tutores} {(Tutoriales en castellano)} -- es una ayuda
+interesante al respecto.
+
+El paquete {\itshape spanish\/} proporciona el fichero {\itshape esbst.tex\/} que es el que
+debe usarse como {\itshape babelbst.tex\/} para las adaptaciones al castellano. Si
+la distribuci\'on es antigua, este fichero puede estar pr\'acticamente vac\'\i{}o y
+tener como \'unico efecto que no aparezca un mensaje de error. En este caso es
+conveniente copiar el archivo {\itshape esbst.tex\/} de una versi\'on reciente de
+{\itshape spanish\/} al directorio donde se va a utilizar el estilo {\itshape .bst\/},
+con el nombre {\itshape babelbst.tex\/}, ya que es el nombre con que lo espera el
+estilo {\itshape .bst\/} creado.
+
+
+\subsection{C\'omo genero un \'\i{}ndice alfab\'etico con la ordenaci\'on correcta en castellano?}
+
+El problema con que uno se encuentra al utilizar {\itshape makeindex\/} es que no ordena
+correctamente las palabras con caracteres acentuados, ya que por
+ejemplo ordena la {\ttfamily \'a} como {\ttfamily $\backslash$'a} que es lo que \TeX{} escribe al
+archivo de \'\i{}ndice y salvo que fuera la m\'as reciente versi\'on de
+{\itshape makeindex\/} de 8 bits ni siquiera las reconocer\'\i{}a si estuvieran
+escritas directamente al archivo de \'\i{}ndice como palabras acentuadas. A
+pesar de las limitaciones mencionadas para los idiomas que no pueden
+describirse mediante la tabla de caracteres de 7 bits, es posible
+utilizar {\itshape makeindex\/} en idiomas como el castellano. Para solucionar
+este problema hay varias aproximaciones:
+\begin{description}
+\item[Decir a {\itshape makeindex\/} c\'omo debe ordenar la palabra acentuada] \mbox{}
+
+Por ejemplo, para los acentos o para la {\ttfamily \~n} se introducir\'\i{}a la entrada al
+\'\i{}ndice como
+\begin{tscreen}
+\begin{verbatim}
+\index{optica@ptica}
+\index{indice@ndice}
+\index{can^^ffa@caa}
+\end{verbatim}
+\end{tscreen}
+
+y para una palabra compuesta como por ejemplo en
+\begin{tscreen}
+\begin{verbatim}
+\index{optica electromagnetica@ptica electromagntica}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+\item[Utilizar el paquete {\itshape esindex\/}] \mbox{}
+
+{\itshape esindex\/} es un paquete desarrollado por Javier Bezos para facilitar la
+escritura de \'\i{}ndices correctamente alfabetizados en castellano. Su
+\'unica orden es {\ttfamily $\backslash$esindex} que convierte su argumento a una
+forma adecuada. Por ejemplo,
+\begin{tscreen}
+\begin{verbatim}
+\esindex{ca'n'on}
+\end{verbatim}
+\end{tscreen}
+
+equivale a
+\begin{tscreen}
+\begin{verbatim}
+\index{can^^ffon@ca'n'on}
+\end{verbatim}
+\end{tscreen}
+
+Es necesario usar babel y que los acentos est\'en escritos en forma de
+abreviaciones ({\ttfamily 'a}, {\ttfamily 'e}, etc.). El paquete utiliza ciertas
+\'ordenes internas de babel por lo su funcionamiento puede cambiar
+con versiones distintas a la 3.6.
+
+Hay que se\~nalar que con este paquete no se crea en el \'\i{}ndice una entrada propia
+para la palabras que empiezan por e\~ne, sino que tan s\'olo se a\~naden
+al final de la ene. En el rar\'\i{}simo caso de que hubiera palabras
+que empiezan por e\~ne habr\'\i{}a que modificar el archivo {\ttfamily .ind} a
+mano. Este paquete puede encontrarse en
+\begin{tscreen}
+\begin{verbatim}
+CTAN:macros/latex/contrib/supported/bezos/
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+\item[Utilizar xindy] \mbox{}
+
+{\itshape xindy\/} es un sistema de indexaci\'on desarrollado por Roger Kehr, del
+Instituto de Inform\'atica Te\'orica de Darmstadt, que puede ser
+configurado f\'acilmente para adaptarse a las normas ortogr\'aficas de
+distintos idiomas, cada uno de ellos con un alfabeto distinto y
+con unas reglas de ordenaci\'on tambi\'en distintas. {\itshape xindy\/} puede
+definir, para cada car\'acter del alfabeto, d\'onde debe ser \'este
+ordenado (reglas de ordenaci\'on), as\'\i{} como a qu\'e car\'acter o cadena
+es equivalente (reglas de equivalencia). Permite incluso definir
+reglas de ordenaci\'on de distinto nivel que pueden ser aplicadas de
+forma sucesiva. Este paquete puede encontrarse en
+{\ttfamily /CTAN:indexing/xindy/} y su p\'agina web est\'a en
+\begin{quotation}
+\ifpdf
+\href{http://www.iti.informatik.tu-darmstadt.de/xindy/}{http://www.iti.informatik.tu-darmstadt.de/xindy/}
+\else
+\onlynameurl{http://www.iti.informatik.tu-darmstadt.de/xindy/}
+\fi
+\end{quotation}
+
+Existen unos archivos de estilo para utilizar {\itshape xindy\/} en castellano en la
+p\'agina anterior y la versi\'on m\'as reciente, incluyendo binarios
+para linux se puede encontrar en el directorio
+\ifpdf
+\href{http://www.aq.upm.es/~agmartin/linux/store/xindy}{http://www.aq.upm.es/\~{}agmartin/linux/store/xindy}
+\else
+\onlynameurl{http://www.aq.upm.es/\~{}agmartin/linux/store/xindy}
+\fi
+, con {\ttfamily tgz} para
+libc5 (xindy-2.0.1.tgz) y libc6 (xindyg21-2.1.tgz) Uno de los estilos
+({\ttfamily es-mkidx.xdy}) ordena seg\'un las reglas modernas del castellano mientras que
+el otro ({\ttfamily es-tridx.xdy}) ordena seg\'un las reglas ya obsoletas, con ch y
+ll. Su uso es algo distinto del habitual en {\itshape makeindex\/}
+\begin{tscreen}
+\begin{verbatim}
+xindy -f tex2xindy estilo.xdy tu_archivo.idx
+\end{verbatim}
+\end{tscreen}
+
+donde {\itshape tex2xindy\/} es un filtro que convierte sobre la marcha del formato
+habitual de los {\itshape .idx\/} al formato especial que utiliza
+{\itshape xindy\/}, {\itshape estilo.xdy\/} puede ser cualquiera de los dos
+mencionados (u otro cualquiera para otro idioma o particularizado
+por el autor del documento) y {\itshape tu\_archivo.idx\/} es el que crea
+\LaTeX{} a partir de las llamadas a {\ttfamily $\backslash$index}.
+
+\end{description}
+
+
+
+
+
+\section{Que es...?}
+
+
+\subsection{Qu\'e es el CTAN ({\itshape Comprehensive \TeX{} Archive Network\/}).\label{que-es-CTAN}}
+
+Son las abreviaturas de {\itshape Comprehensive \TeX{} Archive Network\/} ({\itshape Red del
+Archivo Completo de \TeX{}\/}). Son tres servidores de FTP que
+almacenan pr\'acticamente todo lo relacionado con el \TeX{}. Sus
+{\itshape nodos\/} son:
+\begin{itemize}
+\item
+\ifpdf
+\href{ftp://ftp.dante.de}{ftp.dante.de}
+\else
+\onlynameurl{ftp.dante.de}
+\fi
+ (Alemania)
+\item
+\ifpdf
+\href{ftp://ftp.tex.ac.uk}{ftp.tex.ac.uk}
+\else
+\onlynameurl{ftp.tex.ac.uk}
+\fi
+ (Reino Unido)
+\item
+\ifpdf
+\href{ftp://ftp.shsu.edu}{ftp.shsu.edu}
+\else
+\onlynameurl{ftp.shsu.edu}
+\fi
+ (Estados Unidos)
+\end{itemize}
+
+
+Tambi\'en se puede acceder mediante gopher o WWW con otros nombres, y existen
+interfaces de acceso como
+\begin{quotation}
+\ifpdf
+\href{ http://www.ucc.ie/cgi-bin/ctan}{http://www.ucc.ie/cgi-bin/ctan}
+\else
+\onlynameurl{http://www.ucc.ie/cgi-bin/ctan}
+\fi
+\end{quotation}
+
+que muestra una serie de r\'eplicas del CTAN, y permite hacer b\'usquedas en ellas.
+
+En los tres casos el material de \TeX{} est\'a en el directorio
+{\ttfamily /tex-archive}. Cada uno es un {\itshape mirror\/} o r\'eplica de los
+otros dos: Los tres contienen lo mismo (con un d\'\i{}a de diferencia a lo
+m\'as, en teor\'\i{}a). Por lo tanto conviene conectarse al que que nos
+caiga m\'as cerca. Dado que siempre hay que ir a {\ttfamily /tex-archive},
+se puede omitir dicho directorio y darse por supuesto. Por ejemplo,
+si alguien nos dice que \LaTeX{} se encuentra en
+{\ttfamily CTAN:macros/latex} quiere decir que podemos encontrarlo por
+ejemplo en el directorio
+\begin{tscreen}
+\begin{verbatim}
+ftp://ftp.dante.de/tex-archive/macros/latex
+\end{verbatim}
+\end{tscreen}
+
+Nota: Desde hace tiempo, {\ttfamily ftp.shsu.edu} funciona tan mal que los
+mantenedores del CTAN han decidido (20 de junio de 1996) no
+considerarlo ya m\'as un nodo del CTAN. Para los usuarios de Am\'erica, se
+recomienda usar la siguiente {\itshape r\'eplica\/}:
+\begin{quotation}
+\ifpdf
+\href{ftp://ftp.cdrom.com/pub/tex/ctan}{ftp://ftp.cdrom.com/pub/tex/ctan}
+\else
+\onlynameurl{ftp://ftp.cdrom.com/pub/tex/ctan}
+\fi
+\end{quotation}
+
+En Espa\~na existe una r\'eplica del CTAN en
+\begin{quotation}
+\ifpdf
+\href{ftp://ftp.rediris.es/mirror/tex-archive}{ftp://ftp.rediris.es/mirror/tex-archive}
+\else
+\onlynameurl{ftp://ftp.rediris.es/mirror/tex-archive}
+\fi
+\end{quotation}
+
+aunque no se actualiza con la misma rapidez que los nodos del CTAN.
+
+
+
+
+
+
+\subsection{Qu\'e es el esquema de codificaci\'on de Cork?}
+
+Es el c\'odigo acordado en la reuni\'on del TUG 1990 en Cork, el llamado {\itshape \TeX{}
+256 international character set\/} que es, al menos en lo que se refiere al
+castellano, compatible con ML-\TeX{}, ISO Latin Alphabet 1 (IS 8859/1) y el DEC
+Multinational Character Set. Que adem\'as, es el de las fuentes DC/EC. Esto
+significa que es posible utilizar en entrada los caracteres acentuados
+directamente (por ejemplo con {\ttfamily compose} en Sun o terminales {\ttfamily VTxxx}
+({\ttfamily xxx} {$>$}= 200).
+
+
+
+
+\subsection{Qu\'e es babel?\label{que-es-babel}}
+
+{\itshape Babel\/} es un conjunto de estilos escritos por Johannes L. Braams que:
+\begin{itemize}
+\item Proporciona macros \'utiles para la producci\'on de documentos en una veintena
+de idiomas, incluido el espa\~nol.
+\item P\'ublico y en evoluci\'on. Esto significa la posibilidad de enviar documentos a
+otros sin tener que intercambiar macros primero y que estas macros se actualizan en funci\'on de las necesidades.
+\item La posibilidad de cambiar de idioma a mitad de documento, para, por ejemplo,
+citar en otro idioma y tener disponibles las macros espec\'\i{}ficas de ese idioma.
+\item Puede ser utilizado en plain \TeX{} tambi\'en.
+\end{itemize}
+
+Adem\'as, {\itshape babel\/} convive c\'omodamente con otros estilos. Por ejemplo,
+{\ttfamily artikel1.sty} usa parte de la ayuda de {\itshape babel\/}. Es f\'acil escribir
+estilos que combinen con {\itshape babel\/}. Si tu estilo lo escribes usando para los
+literales las macros que {\itshape babel\/} define, lo tendr\'as sin ning\'un esfuerzo
+adicional para una veintena de idiomas. Es cierto que la probabilidad de que
+uses serbo-croata es escasa, pero hay franc\'es, portugu\'es, italiano, alem\'an,
+etc. Los convenios de {\itshape babel\/} derivan del trabajo realizado por Hubert
+Partl. Estilos escritos de forma compatible con el trabajo de Partl, deben
+funcionar con {\itshape babel\/} en principio. De hecho, es ya est\'andar este convenio
+en las versiones de \LaTeX{} posteriores a octubre de 1991.
+
+Babel puede conseguirse en:
+\begin{tscreen}
+\begin{verbatim}
+CTAN:languages/babel
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsection{Qu\'e son e\TeX{}, e\LaTeX{} y {\itshape omega\/}?}
+
+e\TeX{} es una extensi\'on de \TeX{} con nuevas primitivas y algunas correcciones
+en el c\'odigo de \TeX{} para mejorar (a\'un m\'as si cabe) sus capacidades
+tipogr\'aficas. Es s\'olo un paso intermedio para {\itshape NTS\/}, que ser\'a el nombre
+definitivo. e\LaTeX{} es una versi\'on de \LaTeX{} para e\TeX{}, que en realidad es
+exactamente igual en su funcionamiento, s\'olo que los archivos de formato de
+\TeX{} y e\TeX{} no son compatibles.
+
+{\itshape omega\/} es similar en concepto, aunque distinto en realizaci\'on, ya que
+utiliza preprocesadores integrados con \TeX{}. Adem\'as, funciona con
+{\itshape unicode\/} y permite escribir en cualquier lengua conocida (o por
+conocer). {\itshape lambda\/} es una versi\'on de \LaTeX{} para {\itshape omega\/}, y se puede
+decir lo mismo que sobre e\LaTeX{}.
+
+Ambas son prescindibles si s\'olo quieres usar \TeX{}; pero ambas son
+imprescindibles si quieres ir m\'as all\'a en tipograf\'\i{}a.
+
+
+
+
+\subsection{Qu\'e es Rev\TeX{}?\label{que-es-revtex}}
+
+Rev\TeX{} es un conjunto de macros y estilos en \LaTeX{} realizado por la
+Sociedad Americana de F\'\i{}sica, la Sociedad Americana de \'Optica, y el Instituto
+Americano de F\'\i{}sica. Sirve para componer art\'\i{}culos y res\'umenes para muchas
+revistas de estas sociedades y algunas otras. Las ventajas son las de \LaTeX{}
+(texto en ASCII que puede enviarse por {\itshape e-mail\/} y entre distintas
+plataformas, archivos reducidos, m\'as importancia al contenido y la estructura
+que a la est\'etica, f\'ormulas matem\'aticas impecables, manejo sofisticado de
+referencias y citas, etc.) y las de estar espec\'\i{}ficamente desarrollado para
+art\'\i{}culos de una revista cient\'\i{}fica. As\'\i{}, es muy f\'acil preparar {\itshape preprints\/}
+que se asemejan mucho al resultado final y donde es muy f\'acil calcular el
+n\'umero de p\'aginas. Es inmediato preparar separatas en formato PDF.
+
+Debe procurarse utilizar al menos la versi\'on Rev\TeX{} 4, ya que Rev\TeX{} 3.1
+no es del todo compatible con \LaTeX{} (hay que modificar algo las tablas, por
+ejemplo).
+
+Se puede encontrar m\'as informaci\'on en la p\'agina Web del Instituto Americano de
+F\'\i{}sica (en la secci\'on de publicaciones, programa Compuscript)
+\begin{quotation}
+\ifpdf
+\href{http://www.aip.org}{http://www.aip.org}
+\else
+\onlynameurl{http://www.aip.org}
+\fi
+\end{quotation}
+
+
+
+
+
+
+
+\subsection{Qu\'e es una {\ttfamily box} y cu\'ando conviene utilizarlas?
+\label{que-es-box} }
+
+Realmente esta es una pregunta m\'as especializada. Una {\ttfamily box} es una forma de
+guardar informaci\'on para reutilizarla despu\'es. Por ejemplo, se podr\'\i{}a guardar
+un logo con informaci\'on con
+\begin{tscreen}
+\begin{verbatim}
+\newsavebox{\logo}
+\sbox{\logo}{\includegraphics{logo.eps}}
+\end{verbatim}
+\end{tscreen}
+
+y luego utilizarla con {\ttfamily $\backslash$usebox$\{$$\backslash$logo$\}$}. La diferencia con usar
+\begin{tscreen}
+\begin{verbatim}
+\newcommand{\logo}{\includegraphics{logo.eps}}
+\end{verbatim}
+\end{tscreen}
+
+y luego poner {\ttfamily $\backslash$logo} cada vez que se utilice es la siguiente:
+
+Lo que hay en un {\ttfamily box} ya est\'a hecho y compuesto. Lo que hay en una macro
+son ordenes que se ejecutan cuando se usa la macro, y por tanto no se componen
+hasta ese momento. Cuando es necesario utilizar muchas veces la definici\'on
+sale m\'as rentable usar un {\ttfamily savebox} ya que el recuadro usado contiene
+siempre exactamente lo mismo y de esta forma, no se llama a
+{\ttfamily $\backslash$includegraphics} en cada pagina, sino tan solo una vez. Sin embargo,
+una {\ttfamily box} no admite argumentos como lo hace una macro.
+
+
+
+
+\section{C\'omo hago ...?}
+
+
+\subsection{C\'omo y d\'onde instalo nuevos paquetes o archivos de estilo?\label{paquetes-instalar}}
+
+Este proceso constar\'a en general de los pasos que se describen a continuaci\'on:
+traer el nuevo paquete, extraer los ficheros de estilo si es necesario,
+colocarlos en el sitio apropiado y rehacer la base de datos.
+
+
+
+
+\subsubsection{D\'onde buscar un paquete nuevo y qu\'e traer}
+
+Normalmente los paquetes nuevos se encontrar\'an en el
+\ref{que-es-CTAN} {(CTAN)}, aunque en ocasiones estar\'an en otros
+lugares. En general, se debe descargar el directorio completo del paquete o el
+archivo comprimido que lo contiene. Esto no es necesario cuando se quiere
+descargar un archivo de estilo de uno de los directorios {\itshape misc\/}, que tienen
+contribuciones al {\itshape CTAN\/} en forma de archivos de estilo individuales
+completos en s\'\i{} mismos. En este caso bastar\'\i{}a con descargar el archivo
+individual correspondiente.
+
+
+
+
+\subsubsection{Qu\'e es cada uno de los archivos que traigo?}
+
+Un paquete peque\~no puede estar compuesto \'unicamente de un archivo de estilo
+{\ttfamily .sty} (por ejemplo {\ttfamily paquete.sty}) con las instrucciones de uso
+incluidas como comentarios en el mismo, en un archivo separado o bien en un
+archivo {\itshape README\/}.
+
+Sin embargo, es m\'as frecuente encontrar el paquete en forma de un par de
+archivos {\ttfamily paquete.ins} y {\ttfamily paquete.dtx}, escritos para ser utilizados con
+el sistema {\itshape doc\/} de \LaTeX{}. Los archivos de estilo deben extraerse de
+\'estos. Si hay un {\itshape README\/} adicional debe leerse \'este previamente.
+
+
+
+
+\subsubsection{Extrayendo archivos de estilo de los {\ttfamily .dtx} y {\ttfamily .ins}\label{dtx-extraer}}
+
+En el sistema {\itshape doc\/} el manual de usuario y el c\'odigo del paquete
+documentado se encuentran en el archivo {\ttfamily .dtx}, mientras que el archivo
+{\ttfamily .ins} contiene instrucciones \LaTeX{} acerca de la extracci\'on del c\'odigo
+del archivo {\ttfamily .dtx}. Para extraer los distintos archivos debe seguirse el
+siguiente procedimiento:
+\begin{itemize}
+\item Correr \LaTeX{} sobre {\ttfamily paquete.ins}. Esto extraer\'a uno o m\'as archivos
+(normalmente un {\ttfamily paquete.sty}, pero dependiendo del paquete pueden
+generarse m\'as archivos).
+\item Correr \LaTeX{} sobre {\ttfamily paquete.dtx} para obtener el manual de usuario y
+posiblemente una versi\'on comentada del c\'odigo del paquete.
+\item Correr de nuevo \LaTeX{} sobre {\ttfamily paquete.dtx}. \'Esto resolver\'a las
+referencias y generar\'a una tabla de materias si el archivo original lo pide
+as\'\i{}.
+\item Si \LaTeX{} da el error {\itshape "No file paquete.ind"\/} significa que no encontr\'o
+el archivo fuente para el \'\i{}ndice de \'ordenes. Para generar el \'\i{}ndice basta
+hacer
+\begin{tscreen}
+\begin{verbatim}
+makeindex -s ind.ist paquete
+\end{verbatim}
+\end{tscreen}
+
+y correr de nuevo \LaTeX{}.
+\item Imprimir y leer {\ttfamily paquete.dvi}.
+\end{itemize}
+
+A veces se proporciona el manual de usuario separadamente del archivo
+{\ttfamily .dtx}. En este caso es recomendable procesarlo despu\'es de hacer lo
+anterior, ya que puede necesitar elementos del paquete que est\'a describiendo.
+
+
+
+
+\subsubsection{D\'onde colocar nuevos archivos de estilo?
+ }
+
+En primer lugar \TeX{} buscar\'a archivos en el directorio
+actual. Salvo que se trate de una prueba o de archivos muy
+relacionados con el documento que se est\'a preparando, es conveniente
+colocarlos en un lugar de acceso m\'as general.
+
+El lugar exacto en el que deben colocarse los nuevos archivos de
+estilo depende de la distribuci\'on \TeX{} que se est\'e
+utilizando. Asumiendo que se utiliza una de las distribuciones
+modernas que son conformes al TDS (por ejemplo, te\TeX{}, fp\TeX{} o
+mik\TeX{}) hay una serie de normas que deben tenerse en cuenta
+\begin{enumerate}
+\item Instalar siempre los nuevos archivos personales en una rama
+{\itshape texmf\/} local del \'arbol global o en una rama personal,
+dependiendo de si son archivos para uso com\'un en la m\'aquina o
+\'unicamente para el usuario. De esta forma puede actualizarse el
+\'arbol {\itshape oficial\/} sin tocar los archivos locales o
+personales. Para la rama local, el directorio ra\'\i{}z local tendr\'a
+un nombre del tipo:
+\begin{tscreen}
+\begin{verbatim}
+teTeX: /usr/share/texmf.local/
+fpTeX: c:\fptex\texmf.local\
+mikTeX: c:\localtexmf\
+\end{verbatim}
+\end{tscreen}
+
+que puede cambiar dependiendo de las opciones dadas durante la
+instalaci\'on. Por simplicidad en lo que sigue le denominaremos
+{\ttfamily \$TEXMFLOCAL}.
+\item En la rama local, reproducir la estructura de directorios de la
+rama principal. Estos son unos ejemplos de d\'onde deber\'\i{}an
+colocarse archivos de distintas extensiones:
+\begin{tscreen}
+\begin{verbatim}
+.sty, .cls o .fd: $TEXMFLOCAL/tex/latex/<paquete>/
+.dvi, .ps o .pdf: $TEXMFLOCAL/doc/latex/<paquete>/
+.bib: $TEXMFLOCAL/doc/bibtex/bib
+.bst: $TEXMFLOCAL/doc/bibtex/bst
+.tfm: $TEXMFLOCAL/fonts/tfm/<suministrador>/<fuente>/
+.vf: $TEXMFLOCAL/fonts/vf/<suministrador>/<fuente>/
+.afm: $TEXMFLOCAL/fonts/afm/<suministrador>/<fuente>/
+.pfb: $TEXMFLOCAL/fonts/type1/<suministrador>/<fuente>/
+.ttf: $TEXMFLOCAL/fonts/truetype/<suministrador>/<fuente>/
+\end{verbatim}
+\end{tscreen}
+
+donde {\itshape paquete\/}, {\itshape fuente\/} y {\itshape suministrador\/} dependen de
+cada archivo individual de cada paquete.
+La rama personal suele estar en un subdirectorio {\ttfamily texmf} del
+directorio de usuario, pero puede cambiar. En ella tambi\'en es
+necesario reproducir la estructura de directorios de la rama
+principal. Dependiendo de la distribuci\'on y/o de las opciones de
+configuraci\'on puede ser necesario rehacer la base de datos
+cuando se a\~naden o quitan elementos.
+
+\end{enumerate}
+
+
+
+
+
+\subsubsection{Activando ramas locales y personales del \'arbol de directorios \LaTeX{} global
+ }
+
+A menudo la rama local del \'arbol global no est\'a activada por omisi\'on
+y es necesario activarla:
+\begin{description}
+\item[{\itshape te\TeX{} y fp\TeX{};\/}] \mbox{}
+
+En primer lugar es necesario
+localizar el archivo de configuraci\'on {\ttfamily texmf.conf}. \'Este
+puede estar en {\ttfamily /etc/texmf/texmf.conf},
+{\ttfamily /etc/texmf.conf} o
+{\ttfamily /usr/share/texmf/web2c/texmf.conf}, dependiendo de la
+distribuci\'on. Aunque no siempre es necesario, en la primera
+l\'\i{}nea del archivo borrar la palabra {\ttfamily original}.
+
+Jugando adecuadamente con {\ttfamily texmf.cnf}, donde est\'an los
+caminos de b\'usqueda, se configura sin problemas. Para activar
+una l\'\i{}nea debe quitarse el car\'acter de comentario \% al principio
+de la l\'\i{}nea, para desactivarla a\~nadir el car\'acter \% al principio
+de la l\'\i{}nea. Cuando se activa una l\'\i{}nea debe desactivarse la que
+antes hac\'\i{}a esa funci\'on, si la hab\'\i{}a. Por ejemplo, si se tienen
+los archivos de la distribuci\'on bajo {\ttfamily /usr/share/texmf/},
+archivos locales bajo {\ttfamily /usr/share/local.texmf} y archivos
+personales bajo {\ttfamily \~{}/texmf}, las l\'\i{}neas del {\ttfamily texmf.cnf}
+que lo har\'\i{}an son
+\begin{tscreen}
+\begin{verbatim}
+TEXMFMAIN = /usr/share/texmf
+\end{verbatim}
+\end{tscreen}
+
+para la rama principal, que viene activada por omisi\'on. Para las
+ramas local y personal se a\~nadir\'\i{}a (o se quitar\'\i{}a el comentario
+de la misma) una l\'\i{}nea del tipo
+\begin{tscreen}
+\begin{verbatim}
+TEXMFLOCAL = /usr/share/texmf.local
+HOMETEXMF = $HOME/texmf
+\end{verbatim}
+\end{tscreen}
+
+que normalmente vienen comentadas. Finalmente se seleccionar\'\i{}a
+\begin{tscreen}
+\begin{verbatim}
+TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}
+\end{verbatim}
+\end{tscreen}
+
+que las junta todas. Como se ha dicho antes, en la estructura de
+las ramas local y personal debe clonarse la estructura de la
+rama principal y como se dice en la secci\'on siguiente debe
+correrse {\ttfamily texhash} (o {\ttfamily mktexlsr}) despu\'es de hacer los
+cambios para rehacer la base de datos de archivos. Para la rama
+personal puede ser necesario rehacer la base de datos como
+usuario.
+
+El fichero de configuraci\'on est\'a extensamente comentado con
+explicaciones de la funci\'on de cada una de las posibles l\'\i{}neas.
+
+\end{description}
+
+
+
+
+
+\subsubsection{Rehaciendo la base de datos de archivos instalados
+ }
+
+El paso final consiste en decirle a \LaTeX{} que hay una serie de
+nuevos archivos que debe ser capaz de encontrar. En la mayor parte
+de los sistemas \LaTeX{} libres recientes se mantiene una base de
+datos de archivos instalados, para posibilitar una b\'usqueda m\'as
+r\'apida. En estos sistemas es necesario actualizar esta base de datos
+cada vez que se instalan nuevos archivos, mediante los programas
+suministrados con este fin en la distribuci\'on.
+\begin{description}
+\item[te\TeX{}, fp\TeX{}] \mbox{}
+
+Correr
+\begin{tscreen}
+\begin{verbatim}
+texhash
+\end{verbatim}
+\end{tscreen}
+
+
+\item[web2c] \mbox{}
+
+En cualquier distribuci\'on {\itshape web2c\/} reciente
+{\ttfamily texhash} debiera funcionar. Si no es as\'\i{}, probar con
+\begin{tscreen}
+\begin{verbatim}
+mktexlsr
+\end{verbatim}
+\end{tscreen}
+
+
+\item[Mik\TeX{}] \mbox{}
+
+En una distribuci\'on Mik\TeX{} anterior a la v2.0,
+hacer con los men\'ues desplegables:
+\begin{tscreen}
+\begin{verbatim}
+Start-> Programs-> MikTeX-> Maintenance-> Refresh filename database
+\end{verbatim}
+\end{tscreen}
+
+o en una ventana DOS
+\begin{tscreen}
+\begin{verbatim}
+initexmf -update-fndb
+\end{verbatim}
+\end{tscreen}
+
+En una distribuci\'on Mik\TeX{} mayor o igual que la v2.0, hacer
+con los men\'ues desplegables
+\begin{tscreen}
+\begin{verbatim}
+Start-> Programs-> MikTeX 2-> MikTeX Options
+\end{verbatim}
+\end{tscreen}
+
+y pulsar el bot\'on {\itshape "Update filename database"\/}.
+
+\end{description}
+
+
+
+
+
+\subsubsection{C\'omo verifico los directorios en los que \TeX{} busca archivos de estilo?
+ }
+
+La respuesta m\'as general ser\'\i{}a mirando los archivos de
+configuraci\'on, pero si se trata de un \TeX{} que utiliza las rutinas
+{\itshape kpathsearch\/} de Karl Berry, es mucho m\'as sencillo
+\begin{tscreen}
+\begin{verbatim}
+% kpsepath tex
+\end{verbatim}
+\end{tscreen}
+
+responder\'a con la lista de los directorios en los que busca. Una
+doble barra ({\ttfamily //}) indica que se busca recursivamente en los
+subdirectorios del que pone. Es decir, que si los paquetes
+particulares est\'an en {\ttfamily \~{}/texmf/tex/latex/lo-que-sea}, o en
+{\ttfamily \~{}/texmf/tex/mas-paquetes} los encontrar\'a.
+
+
+
+
+\subsection{C\'omo personalizo el aspecto del documento?\label{tex-personalizar}
+ }
+
+
+\subsubsection{C\'omo cambio la fuente de un documento o instalo nuevas?
+ }
+
+Pues depende de la fuente que se quiera usar. Normalmente hay paquetes de
+estilo que lo hacen autom\'aticamente. Por ejemplo, si pretendes usar la
+familia de {\itshape Times\/}, usa el paquete {\itshape times\/} poniendo en el pre\'ambulo
+{\ttfamily $\backslash$usepackage$\{$times$\}$}. Otra familia disponible es {\itshape lucida-bright\/},
+que puedes cargar con el paquete {\itshape lucidabr\/}. Si miras estos archivos
+({\ttfamily times.sty} o {\ttfamily lucidabr.sty}) puedes aprender la forma de usar una
+fuente, y copiarlo para otros tipos.
+
+Hay muchos tipos de letras ya preparados as\'\i{}: {\ttfamily times}, {\ttfamily helvetica}
+({\ttfamily arial} est\'a casi clonado de esta), courier, la letra g\'otica se
+llama {\ttfamily oldgerm}, griego...
+
+Un segundo paso es ir al {\itshape CTAN\/} para ver si alguien ha preparado un
+paquete con el tipo deseado.
+
+En el peor de los casos en el que no est\'e preparado, puede crearse
+manualmente un paquete a partir de los tipos originales en formato
+{\itshape Type-1\/}, aunque no es un proceso inmediato. M\'as informaci\'on en
+{\ttfamily CTAN:info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf}.
+
+
+
+
+\subsubsection{Puedo utilizar una fuente {\itshape TrueType\/} como {\itshape Arial\/} en \LaTeX{}?
+ }
+
+A veces se piden tipos de letra que no est\'an disponibles directamente en
+\LaTeX{} como {\itshape Arial\/}. El tipo de letra Arial es {\itshape TrueType\/}, y este
+formato no es soportado directamente por \LaTeX{}. Desde pdflatex s\'\i{} es
+posible usar tipos {\itshape TrueType\/}, pero antes hay que crear unos cuantos
+archivos auxiliares que necesita \TeX{}. El proceso no es sencillo. Est\'a
+descrito en
+\ifpdf
+\href{http://www.radamir.com/tex/ttf-tex.htm}{http://www.radamir.com/tex/ttf-tex.htm}
+\else
+\onlynameurl{http://www.radamir.com/tex/ttf-tex.htm}
+\fi
+
+
+Recientemente ha aparecido otro documento que explica c\'omo convertir los
+tipos {\itshape TrueType\/} en tipos {\itshape PostScript\/}, y c\'omo usar estos tipos
+convertidos desde {\ttfamily latex-{$>$}dvips}. El documento se encuentra disponible en
+{\ttfamily CTAN:info/TrueType/} y est\'a orientado a un sistema tetex, por lo que
+es posible que no funcione bajo windows/miktex.
+
+El tipo de letra {\itshape helvetica\/} es muy parecido al tipo {\itshape Arial\/} y s\'\i{} est\'a
+disponible bajo \LaTeX{}. Basta con a\~nadir en el pre\'ambulo del documento
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\rmdefault}{phv}
+\renewcommand{\sfdefault}{phv}
+\end{verbatim}
+\end{tscreen}
+
+pero si hay f\'ormulas matem\'aticas \'estas seguir\'\i{}an utilizando los tipos
+{\itshape computer modern\/} por lo que quedar\'an feas en medio del texto en
+{\itshape helvetica\/}.
+
+
+
+
+\subsubsection{Incluyendo subdocumentos \TeX{}/\LaTeX{} en el documento
+ }
+
+Pueden incluirse subdocumentos \TeX{}/\LaTeX{} en un documento mediante las
+\'ordenes {\ttfamily $\backslash$input} e {\ttfamily $\backslash$include}. {\ttfamily $\backslash$input$\{$otro\_documento$\}$} lo incluir\'a
+en el lugar en el que se introduce la orden, mientras que
+{\ttfamily $\backslash$include$\{$otro\_documento$\}$} siempre abrir\'a una p\'agina nueva al incluir el
+documento. Sin embargo, {\ttfamily $\backslash$include} permite incluir documentos de forma
+selectiva mediante la orden {\ttfamily $\backslash$includeonly}, mientras que {\ttfamily $\backslash$input} no
+lo permite. As\'\i{}, la orden {\ttfamily $\backslash$includeonly$\{$doca,docc$\}$} en el pre\'ambulo har\'a
+que se incluyan \'unicamente los documentos {\ttfamily doca} y {\ttfamily docc}, a pesar de
+que tambi\'en {\ttfamily docb} tenga un {\ttfamily $\backslash$include},
+\begin{tscreen}
+\begin{verbatim}
+...
+\includeonly{doca,docc}
+\begin{document}
+...
+\include{doca}
+\include{docb}
+\include{docc}
+...
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{C\'omo evito que salga la palabra cap\'\i{}tulo en las cabeceras de cap\'\i{}tulo?}
+
+Cuando se usa {\itshape spanish-babel\/} basta con poner en el pre\'ambulo, despu\'es de
+haberse cargado {\itshape babel\/}
+\begin{tscreen}
+\begin{verbatim}
+\addto{\captionsspanish}{\def\chaptername{}}
+\end{verbatim}
+\end{tscreen}
+
+y queda eliminada la palabra Cap\'\i{}tulo. Si no se usa {\itshape babel\/} basta con poner
+en el pre\'ambulo {\ttfamily $\backslash$def$\backslash$chaptername$\{$$\}$}. Realmente esto es un caso
+particular de cambio de literales, que se trata en las secciones \ref{literales} {(literales)} y \ref{sectnames} {(Cambio de nombre de secciones)}
+
+
+
+
+\subsubsection{C\'omo cambio la cabecera de cap\'\i{}tulo por otra m\'as a mi gusto?}
+
+Hay dos formas, redefiniendo las \'ordenes que hacen las cabeceras, o utilizando
+un paquete hecho que facilite el trabajo. Un paquete que permite
+hacer cosas muy elaboradas con las cabeceras de los cap\'\i{}tulos es
+{\itshape titlesec\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/titlesec}
+
+
+
+
+\subsubsection{Quiero una secci\'on no numerada, pero que aparezca en la tabla de materias.}
+
+Por ejemplo, suponiendo que se trate de una lista de s\'\i{}mbolos,
+\begin{tscreen}
+\begin{verbatim}
+\section*{Lista de smbolos}
+\addcontentsline{toc}{section}{Lista de smbolos}
+\end{verbatim}
+\end{tscreen}
+
+Lo mismo para otros elementos (subsecci\'on,...).
+
+
+
+
+\subsubsection{No me funciona {\ttfamily $\backslash$subsubsubsection}.}
+
+{\ttfamily $\backslash$subsubsubsection} no existe, en los estilos est\'andar es
+{\ttfamily $\backslash$paragraph} quien hace ese papel.
+
+
+
+
+\subsubsection{C\'omo quito los encabezados que \LaTeX{} pone autom\'aticamente en las p\'aginas blancas? }
+
+Si se quiere controlar cu\'ando se quiere o no este comportamiento en cada
+p\'agina con este problema, se puede definir una nueva orden,
+\begin{tscreen}
+\begin{verbatim}
+\newcommand{\clearemptydoublepage}{\newpage{\pagestyle{empty}\cleardoublepage}}
+\end{verbatim}
+\end{tscreen}
+
+y teclear {\ttfamily $\backslash$clearemptydoublepage} cada vez que quieras continuar el
+texto en una pagina impar.
+
+Cuando se quiere que esto ocurra autom\'aticamente hay que redefinir la orden
+{\ttfamily $\backslash$cleardoublepage} como sugiere la documentaci\'on del paquete
+{\itshape fancyhdr\/},
+\begin{tscreen}
+\begin{verbatim}
+\makeatletter
+ \def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else
+ \vspace*{\fill}
+ \thispagestyle{empty}
+ \newpage
+ \if@twocolumn\hbox{}\newpage\fi\fi\fi}
+\makeatother
+\end{verbatim}
+\end{tscreen}
+
+
+Cuando se utiliza el paquete {\itshape titlesec\/} de Javier Bezos para definir
+formatos propios de cabeceras y pies de pagina, la opci\'on de paquete
+{\ttfamily clearempty} ya hace el trabajo:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[<tus_opciones>,clearempty]{titlesec}
+\end{verbatim}
+\end{tscreen}
+
+
+Otra posibilidad es utilizar el paquete {\itshape nextpage\/},
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{nextpage}
+...
+\cleartooddpage[\thispagestyle{empty}]
+\chapter{...}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{C\'omo quito los encabezados, pies o la numeraci\'on de las p\'aginas? }
+
+La opci\'on {\ttfamily $\backslash$pagestyle$\{$empty$\}$} quitar\'a los encabezados y pies de todas las
+p\'aginas posteriores a aqu\'ella en la que se invoca. La opci\'on
+{\ttfamily $\backslash$thispagestyle$\{$empty$\}$} quitar\'a los encabezados y los pies de p\'agina en la
+p\'agina donde se invoca esta orden.
+
+Cuando lo que se quiere es eliminar \'unicamente el n\'umero de p\'agina, en general
+no es conveniente utilizar {\ttfamily $\backslash$renewcommand$\{$$\backslash$thepage$\}$$\{$$\}$} porque eso
+suprime {\itshape todos\/} los n\'umeros de p\'agina, incluidos los de los \'\i{}ndices o las
+remisiones. Por tanto, hay que evitarla siempre que se pueda y optar por
+soluciones mejor construidas y espec\'\i{}ficas a cada caso, como utilizar una
+definici\'on personal de cabeceras que pueda activarse a voluntad para ciertas
+p\'aginas.
+
+
+
+
+\subsubsection{C\'omo pongo encabezados o pies de p\'agina a mi gusto? }
+
+La forma m\'as habitual es utilizar el paquete {\itshape fancyhdr\/}. Por ejemplo, con
+pies
+\begin{tscreen}
+\begin{verbatim}
+\documentclass{book}
+\usepackage{fancyhdr}
+\lfoot{titulo a la izquierda}
+\rfoot{titulo a la derecha}
+\cfoot{titulo al centro}
+\pagestyle{fancy}
+\begin{document}
+\chapter{A title}
+\thispagestyle{fancy} %opcional
+\newpage
+\section{a section}
+\end{document}
+\end{verbatim}
+\end{tscreen}
+
+pero {\itshape titlesec\/} tambi\'en permite un amplio control del estilo de p\'agina.
+
+
+
+
+\subsubsection{C\'omo hago que \LaTeX{} y \TeX{} no partan nunca las palabras?}
+
+Para \LaTeX{} si se ha cargado el paquete babel basta con la orden
+\begin{tscreen}
+\begin{verbatim}
+\hyphenrules{nohyphenation}
+\end{verbatim}
+\end{tscreen}
+
+Por supuesto el patr\'on {\ttfamily nohyphenation} debe de estar activado en
+{\ttfamily language.dat} y el formato creado con \'el (V\'eanse \ref{guionado} {(C\'omo activo el patr\'on de partici\'on de palabras para el castellano?)} y \ref{formatos} {(C\'omo rehacer los formatos?)}).
+
+Para \TeX{} hay que hacer las cosas de otra forma. Una forma de conseguir que
+\TeX{} no corte casi nunca, (y as\'\i{} de paso se evita que corte mal) es poner:
+\begin{tscreen}
+\begin{verbatim}
+\pretolerance=2000
+\tolerance=3000
+\end{verbatim}
+\end{tscreen}
+
+al principio. Si se quiere que \'esto ocurra \'unicamente en un p\'arrafo o en una
+regi\'on, debe encerrarse lo anterior y la regi\'on deseada entre
+llaves,
+\begin{tscreen}
+\begin{verbatim}
+{\pretolerance=2000
+\tolerance=3000
+el prrafo o regin
+}
+\end{verbatim}
+\end{tscreen}
+
+\'Esto puede utilizarse tambi\'en para \LaTeX{}
+
+
+
+
+\subsubsection{C\'omo ajusto los m\'argenes de un documento \LaTeX{}?}
+
+Quiz\'as la forma m\'as c\'omoda sea utilizar el paquete {\itshape geometry\/}, que se
+encuentra disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/geometry}. Por ejemplo
+\begin{tscreen}
+\begin{verbatim}
+\documentclass[a4paper, 10pt]{article}
+\usepackage[a4paper,left=3cm,right=2cm]{geometry}
+\end{verbatim}
+\end{tscreen}
+
+crea una p\'agina A4 con margen de 3cm a la izquierda y 2cm a la derecha, sin m\'as
+complicaciones.
+
+Otra cosa mucho m\'as complicada es c\'omo cambiar los m\'argenes dentro de un
+documento, en vez de hacerlo en el pre\'ambulo como lo hace el paquete
+{\itshape geometry\/}. Un caso especial se tiene cuando se quiere alargar un
+poco una p\'agina para que quepa un poco m\'as de texto y as\'\i{} evitar
+situaciones poco est\'eticas. Para \'esto, \LaTeXe{} proporciona la orden
+{\ttfamily $\backslash$enlargethispage$\{$distancia$\}$} donde se aumenta el tama\~no
+vertical de la p\'agina en la distancia especificada.
+
+A pesar de esa dificultad, puede utilizarse el paquete {\itshape chngpage\/}, que
+proporciona \'ordenes para cambiar el aspecto de la p\'agina en
+el medio de un documento (por ejemplo, hacerla m\'as estrecha
+o m\'as ancha, m\'as corta o m\'as larga, e incluso desplazarla
+horizontal o verticalmente), aunque no permite cambios
+dentro de un p\'arrafo.
+
+
+
+
+\subsubsection{C\'omo obtengo un documento apaisado?}
+
+Cuando se quiere sacar la totalidad del documento apaisada, hay que decirle a
+\TeX{} que las dimensiones horizontal y vertical est\'an cambiadas, comenzando el
+documento con la opci\'on {\ttfamily landscape}, algo del tipo
+\begin{tscreen}
+\begin{verbatim}
+\documentclass[landscape,a4]{article}
+\end{verbatim}
+\end{tscreen}
+
+donde la clase de documento puede ser tambi\'en cualquier otra como
+{\ttfamily slides}. Esto intercambia las distancias horizontal y vertical, pero no
+rota el documento final para que se ajuste a la posici\'on de la hoja. Para ello
+se puede utilizar el {\itshape dvips\/}, por ejemplo en la forma siguiente
+\begin{tscreen}
+\begin{verbatim}
+dvips -ta4 -tlandscape tu_archivo -o tu_archivo.ps
+\end{verbatim}
+\end{tscreen}
+
+donde {\ttfamily -tlandscape} gira la salida. La opci\'on {\ttfamily -ta4} es a menudo
+conveniente si se utiliza papel {\itshape a4\/}, para que el giro se haga de forma
+adecuada.
+
+
+
+
+\subsubsection{C\'omo ajusto el espaciado en el documento \LaTeX{}?}
+
+Para ajustar el espaciado entre l\'\i{}neas en un documento \LaTeXe{} se recomienda
+utilizar el paquete {\itshape setspace\/}, que se cargar\'a en el pre\'ambulo. Las \'ordenes
+{\ttfamily $\backslash$singlespacing}, {\ttfamily $\backslash$onehalfspacing}, y {\ttfamily $\backslash$doublespacing} colocadas en
+el pre\'ambulo establecen el espaciado global del documento. Pueden establecerse
+valores intermedios mediante la orden {\ttfamily $\backslash$setstretch$\{$baselinestretch$\}$} en el
+pre\'ambulo. El valor por omisi\'on es espaciado simple. Asimismo se definen tres
+entornos con los mismos nombres que las \'ordenes anteriores para cambios del
+espaciado en regiones del documento (respecto del espaciado est\'andar en ese
+momento, doublespacing empezar\'a un entorno de espaciado doble que el espaciado
+en ese momento, si es doble lo har\'a a\'un mayor).
+
+Para un documento \LaTeX{}209 puede utilizarse el paquete {\itshape doublespace\/}.
+
+La forma m\'as c\'omoda de controlar el espaciado entre p\'arrafos es mediante el
+paquete {\itshape parskip\/}.
+
+
+
+
+\subsection{Listas al gusto de cada cual.}
+
+
+\subsubsection{C\'omo ajusto el espaciado en una lista?}
+
+La distancia entre los elementos es la suma de los valores de {\ttfamily $\backslash$parsep}
+(que es tambi\'en la distancia entre p\'arrafos dentro de un mismo
+elemento) e {\ttfamily $\backslash$itemsep}. Si s\'olo se quiere cambiar la distancia
+entre elementos pero no entre p\'arrafos de un mismo elemento, basta con
+dar un nuevo valor a la distancia {\ttfamily $\backslash$itemsep}.
+
+Es un espacio el\'astico, es decir, adem\'as de con
+{\ttfamily $\backslash$setlength$\{$$\backslash$itemsep$\}$$\{$1cm$\}$} se puede definir con algo como
+\begin{tscreen}
+\begin{verbatim}
+\itemsep= 4pt plus 2pt minus 1pt
+\end{verbatim}
+\end{tscreen}
+
+donde 4pt ser\'\i{}a el espacio {\itshape normal\/}, 2pt lo m\'aximo que podr\'\i{}a estirarse y 1pt
+lo m\'aximo que podr\'\i{}a encogerse.
+
+El valor de {\ttfamily $\backslash$itemsep} se restablece con cada {\ttfamily $\backslash$begin$\{$itemize$\}$}
+(o la lista de que se trate), y se hace igual a {\ttfamily $\backslash$parsep}, por lo que
+hay que modificarlo {\itshape dentro\/} de la lista, por ejemplo.
+\begin{tscreen}
+\begin{verbatim}
+
+{\topsep=-15pt \parsep=-15pt \partopsep=-15pt
+ \begin{enumerate}\itemsep=-5pt
+ \item{ Pruebas de interespaciado}
+ \item{ Pruebas de interpaginado}
+ \item{ Pruebas de espaciado}
+ \end{enumerate}}
+\end{verbatim}
+\end{tscreen}
+
+Puede hacerse que la separaci\'on sea nula, mediante
+{\ttfamily $\backslash$setlength$\{$$\backslash$itemsep$\}$$\{$-$\backslash$parsep$\}$}
+
+Hacer el cambio para todas las listas es algo m\'as complejo, pero una forma de
+hacerlo ser\'\i{}a redefinir {\ttfamily $\backslash$itemize} (y lo mismo para las dem\'as listas)
+en la forma
+\begin{tscreen}
+\begin{verbatim}
+
+\let\olditemize\itemize
+\def\itemize{\olditemize\itemsep=0pt }
+\end{verbatim}
+\end{tscreen}
+
+donde en este caso se ha puesto un valor de 0pt a {\ttfamily $\backslash$itemsep} en todas
+las listas enumeradas.
+
+
+
+
+\subsubsection{C\'omo cambio el tipo de numeraci\'on en las listas numeradas?}
+
+Por ejemplo, para que escriba los elementos de primer nivel con n\'umeros como 1 y
+los de segundo nivel con n\'umeros en la forma 1.1
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\theenumii}{\arabic{enumii}}
+\renewcommand{\labelenumii}{\theenumi .\theenumii .}
+\end{verbatim}
+\end{tscreen}
+
+Si alg\'un paquete que est\'es usando redefine los {\ttfamily $\backslash$theenum}, como el
+{\itshape babel-spanish,\/} entonces debes asegurate que \LaTeX{} eliga tus parametros
+colocando las \'ordenes anteriores entre:
+\begin{tscreen}
+\begin{verbatim}
+\AtBeginDocument{%
+comandos aqui..
+}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{Quiero mostrar un s\'\i{}mbolo distinto en las listas {\itshape itemize\/}}
+
+Dentro de un {\itshape itemize\/}, puede especificarse en cada {\ttfamily $\backslash$item} un par\'ametro
+opcional, que es el s\'\i{}mbolo que se mostrar\'a (en lugar del topo por defecto),
+por ejemplo, {\ttfamily $\backslash$item[\$$\backslash$odot\$]}, y si se quieren cambiar todos, con el mismo
+ejemplo,
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\item}{\item[$\odot$]}
+\end{verbatim}
+\end{tscreen}
+
+o, mediante el paquete {\itshape paralist\/},
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{paralist}
+...
+\begin{itemize}[$\star$]
+\item ...
+\item ...
+\end{itemize}
+\end{verbatim}
+\end{tscreen}
+
+
+Tambi\'en puede utilizarse el paquete {\itshape pifont\/}, as\'\i{}:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{pifont}
+\begin{Pilist}{pzd}{248}
+\item bla
+\item bla bla
+\item bla
+\end{Pilist}
+\end{verbatim}
+\end{tscreen}
+
+
+El entorno {\itshape Pilist\/} es an\'alogo a {\itshape itemize\/}, pero en lugar del {\itshape bullet\/}
+usa el caracter que se le pida de la fuente que se le pida. En el ejemplo
+anterior, se usa el car\'acter con c\'odigo 248 de la fuente {\itshape pzd\/} que tiene gran
+cantidad de simbolos adecuados para {\itshape itemize\/}.
+
+
+
+
+\subsubsection{Puedo ajustar la separaci\'on entre texto y listas?}
+
+Con el paquete {\itshape enumitem\/}, en {\ttfamily CTAN:macros/latex/contrib/bezos/}.
+
+
+
+
+\subsubsection{C\'omo interrumpir una lista numerada con un comentario y continuar despu\'es con la numeraci\'on correcta?}
+
+Entre las {\itshape mdwtools\/} hay un paquete llamado {\itshape mdwlist\/} que permite hacer
+eso:
+\begin{tscreen}
+\begin{verbatim}
+ \begin{enumerate}
+ \item ...
+ \item ...
+ \suspend{enumerate}
+Texto...
+ \resume{enumerate}
+ \item ...
+ \item ...
+ \end{enumerate}
+\end{verbatim}
+\end{tscreen}
+
+Disponible en {\ttfamily CTAN:macros/latex/contrib/supported/mdwtools/}
+
+
+
+
+\subsubsection{Puedo hacer listas en paralelo?}
+
+Para crear listas numeradas o por elementos de la forma
+\begin{tscreen}
+\begin{verbatim}
+1. Primer elemento 2. Segundo elemento 3. Tercer elemento
+4. Cuarto elemento 5. Quinto elemento 6. Sexto elemento
+\end{verbatim}
+\end{tscreen}
+
+puede utilizarse el paquete {\itshape paralist\/} (disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/paralist}) o bien el paquete
+{\itshape multicol\/}. Tambi\'en existe el paquete {\itshape multienumerate\/}
+({\ttfamily CTAN:macros/latex/contrib/supported/multenum}) y el entorno
+{\ttfamily shortenumerate} del paquete {\itshape shortlst\/}
+({\ttfamily CTAN:macros/latex/contrib/supported/shortlst}) destinado a listas de
+elementos cortos.
+
+
+
+
+\subsection{Referencias cruzadas, \'\i{}ndices, bibliograf\'\i{}as y tablas de materias.}
+
+
+\subsubsection{Hay alguna herramienta de gesti\'on de bases de datos bibliogr\'aficas en {\itshape Bib\TeX{}\/}? }
+
+S\'\i{}, existen varias, por ejemplo
+\begin{description}
+\item[bibtex.el] \mbox{}
+
+Modo {\itshape Bib\TeX{}\/} para {\itshape emacs\/}. Normalmente viene
+incluido con {\itshape emacs\/}, pero tambi\'en se puede obtener de su p\'agina principal
+\ifpdf
+\href{http://www.ida.ing.tu-bs.de/people/dirk/bibtex/}{http://www.ida.ing.tu-bs.de/people/dirk/bibtex/}
+\else
+\onlynameurl{http://www.ida.ing.tu-bs.de/people/dirk/bibtex/}
+\fi
+
+
+\item[Winbibdb y bibdb] \mbox{}
+
+ambos excelentes y disponibles en
+{\ttfamily CTAN:support/bibdb} con su p\'agina base en
+\ifpdf
+\href{http://www.mackichan.com/BibDB/default.htm}{http://www.mackichan.com/BibDB/default.htm}
+\else
+\onlynameurl{http://www.mackichan.com/BibDB/default.htm}
+\fi
+
+
+\item[bibtool] \mbox{}
+
+disponible en {\ttfamily CTAN:bibtex/utils/bibtool/} con su
+p\'agina principal en
+\ifpdf
+\href{http://bibtool.sourceforge.net/}{http://bibtool.sourceforge.net/}
+\else
+\onlynameurl{http://bibtool.sourceforge.net/}
+\fi
+
+
+\item[jabref] \mbox{}
+
+\ifpdf
+\href{http://jabref.sourceforge.net/}{http://jabref.sourceforge.net/}
+\else
+\onlynameurl{http://jabref.sourceforge.net/}
+\fi
+ es una interfaz gr\'afica
+escrita en java para manejar bases de datos bibliogr\'aficas.
+Necesita Java {$>$}= 1.4.2
+
+\end{description}
+
+
+
+
+
+\subsubsection{C\'omo introduzco la bibliograf\'\i{}a o el \'\i{}ndice en la tabla de materias?}
+
+La forma m\'as c\'omoda es utilizar el paquete {\itshape tocbibind\/}, que se encuentra
+disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/tocbibind} y en la
+mayor parte de las distribuciones, pero tambi\'en puede hacerse
+a mano con por ejemplo
+{\ttfamily $\backslash$addcontentsline$\{$toc$\}$$\{$chapter$\}$$\{$$\backslash$bibname$\}$} en la
+definici\'on correspondiente.
+
+
+
+
+\subsubsection{C\'omo pongo el \'\i{}ndice con su contenido al principio de cada cap\'\i{}tulo?}
+
+Con el paquete {\itshape minitoc\/}
+
+
+
+
+\subsubsection{C\'omo a\~nado bibliograf\'\i{}a al final de cada cap\'\i{}tulo en \LaTeX{}?}
+
+Puede hacerse usando el paquete {\itshape chapterbib\/}. Para hacerlo de esta
+forma debe estructurarse el documento en un archivo ra\'\i{}z
+desde el que se incluyen las distintas secciones que est\'an
+en archivos separados del ra\'\i{}z, incluir al final de cada uno
+de \'estos las \'ordenes de bibliograf\'\i{}a y procesar con
+{\itshape bibtex\/} los .aux de cada una de estas partes. Si adem\'as
+se quiere que no haya un salto de p\'agina al comenzar la
+bibliograf\'\i{}a en cada cap\'\i{}tulo, debe utilizarse la opci\'on
+{\ttfamily sectionbib}.
+
+Otro paquete que permite una cosa similar es {\itshape bibunits\/}
+
+
+
+
+\subsubsection{C\'omo divido la bibliograf\'\i{}a por temas en \LaTeX{}?}
+
+Los paquetes {\itshape multibib\/} y {\itshape bibtopic\/} permiten dividir una bibliograf\'\i{}a
+global en partes separadas para los distintos temas. El primero requiere el
+uso de \'ordenes espec\'\i{}ficas para las citas bibliogr\'aficas, mientras que el
+segundo requiere dividir el archivo de bibliograf\'\i{}a.
+
+
+
+
+\subsubsection{C\'omo cito una p\'agina de una referencia bibliogr\'afica?}
+
+Mediante algo del tipo
+\begin{tscreen}
+\begin{verbatim}
+\cite[pg.~29]{gar98}
+\end{verbatim}
+\end{tscreen}
+
+donde {\ttfamily gar98} ser\'\i{}a la etiqueta {\itshape Bib\TeX{}\/} para la cita deseada.
+
+
+
+
+\subsubsection{C\'omo cito una {\ttfamily url} con {\itshape Bib\TeX{}\/}?}
+
+En los estilos bibliogr\'aficos est\'andar de {\itshape Bib\TeX{}\/} no hay un tipo para
+las {\ttfamily url}, aunque es posible que en una futura versi\'on de {\itshape Bib\TeX{}\/} s\'\i{}
+lo haya.
+
+En tanto esa versi\'on aparece la forma m\'as sencilla consiste en utilizar el
+campo {\itshape howpublished\/} del tipo {\itshape misc\/}. Una entrada de ese tipo tendr\'\i{}a la
+forma
+\begin{tscreen}
+\begin{verbatim}
+ @misc{...,
+ ...,
+ howpublished = "\url{http://...}"
+ }
+\end{verbatim}
+\end{tscreen}
+
+Tambi\'en puede ocurrir que un art\'\i{}culo, informe o incluso libro se encuentre
+disponible tambi\'en en la {\itshape web\/}. En este caso se podr\'\i{}a hacer algo del tipo
+\begin{tscreen}
+\begin{verbatim}
+ @techreport{...,
+ ...,
+ note = "Tambin disponible como \url{http://...}"
+ }
+\end{verbatim}
+\end{tscreen}
+
+donde se supone que se ha utilizado el paquete {\itshape url\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/other/misc/url.sty/}, lo que es muy
+recomendable para estas referencias por diversas razones.
+
+
+
+
+\subsubsection{C\'omo colapso una serie de citas consecutivas?}
+
+O c\'omo puedo hacer que aparezca una citaci\'on bibliogr\'afica m\'ultiple
+consecutiva, por ejemplo, {[}1,2,3,4,5] como {[}1-5]? El paquete {\itshape cite\/},
+disponible en {\ttfamily CTAN:macros/latex/contrib/supported/cite} y en
+{\itshape te\TeX{}\/} permite hacer precisamente eso.
+
+
+
+
+\subsubsection{C\'omo hago una referencia cruzada a un documento externo?}
+
+Para hacer referencias cruzadas entre documentos se puede usar el paquete
+{\itshape xr\/}, de David Carlisle, disponible en las distribuciones habituales y en
+{\ttfamily CTAN:macros/latex209/contrib/misc/xr.sty}. Su uso es como sigue,
+\begin{tscreen}
+\begin{verbatim}
+...
+\usepackage{xr} %Referencias a otros documentos
+...
+\externaldocument{miotrodocumento}
+...
+\end{verbatim}
+\end{tscreen}
+
+Una vez hecho esto las referencias se declaran como si de un \'unico documento
+se tratase.
+
+
+
+
+\subsubsection{Afinando el aspecto de la tabla de materias o listas de figuras y tablas. }
+
+\begin{description}
+\item[C\'omo controlar hasta qu\'e nivel se incluye un elemento en la tabla de materias?] \mbox{}
+
+En general, con
+\begin{tscreen}
+\begin{verbatim}
+
+\setcounter{tocdepth}{X}
+\end{verbatim}
+\end{tscreen}
+
+en el pre\'ambulo se controla hasta que nivel se incluir\'a en el \'\i{}ndice
+general, siendo {\ttfamily X} un n\'umero. Con 3 se incluye hasta
+{\ttfamily $\backslash$subsubsection}, con 2 hasta {\ttfamily $\backslash$subsection}. \'Esto permite
+cambiar el valor definido por omisi\'on en el estilo utilizado.
+
+\item[El t\'\i{}tulo del cap\'\i{}tulo, figura o tabla se solapa con su n\'umero si \'este
+tiene muchos d\'\i{}gitos] \mbox{}
+
+Para las listas de figuras y tablas la separaci\'on se define en {\ttfamily $\backslash$l@figure$\}$} o
+{\ttfamily $\backslash$l@table}, por ejemplo {\itshape book.cls\/} lo hace as\'\i{} para las figuras
+\begin{tscreen}
+\begin{verbatim}
+\newcommand*\l@figure{\@dottedtocline{1}{1.5em}{2.3em}}
+\end{verbatim}
+\end{tscreen}
+
+En un estilo o en el pre\'ambulo entre {\ttfamily makeatletter/makeatother}
+pueden redefinirse sus valores cambiando el \'ultimo n\'umero. Por ejemplo, en
+el pre\'ambulo
+\begin{tscreen}
+\begin{verbatim}
+\makeatletter
+\renewcommand*{\l@figure}{\@dottedtocline{1}{1.5em}{3.3em}}
+\renewcommand*{\l@table}{\@dottedtocline{1}{1.5em}{2.8em}}
+\makeatother
+\end{verbatim}
+\end{tscreen}
+
+Para las entradas de la tabla de materias ser\'\i{}a necesario cambiar los
+valores de {\ttfamily $\backslash$l@section}, {\ttfamily $\backslash$l@subsection}, {\ttfamily $\backslash$l@subsubsection},
+{\ttfamily $\backslash$l@paragraph} o {\ttfamily $\backslash$l@subparagraph} de una forma an\'aloga. Para los
+cap\'\i{}tulos la cosa es m\'as problem\'atica porque se cambian m\'as cosas.
+
+\end{description}
+
+
+El paquete {\itshape tocloft\/} permite controlar detalles del dise\~no tipogr\'afico de
+las tablas de materias y de las listas de figuras y tablas, aunque su
+internaci\'on con otros paquetes como {\itshape titlesec\/} no est\'a suficientemente
+probada.
+
+
+
+
+\subsection{C\'omo introduzco dibujos, diagramas e im\'agenes en \LaTeX{}?\label{tex-dibujos}}
+
+Hay dos formas de dibujar en \TeX{}, mediante el uso de funciones primitivas
+\TeX{} bien directamente (muy duro) o a trav\'es de alguno de los paquetes de m\'as
+alto nivel que proveen de funciones que internamente utilizan esas primitivas,
+pero que a un usuario se le representan como funciones de dibujo normales en
+un cierto lenguaje, o bien incluyendo gr\'aficos realizados mediante
+aplicaciones externas, como es el caso de gr\'aficos en {\itshape postscript
+encapsulado\/} o en mapa de bits.
+
+El problema en este segundo caso es que los datos del gr\'afico deben darse en
+el documento mediante \'ordenes {\ttfamily $\backslash$special} -- V\'ease \ref{special} {(Qu\'e son los $\backslash$special)} -- y que \'estas \'ordenes son en general distintas
+para los distintos conversores (drivers) a los formatos de impresi\'on o
+visualizaci\'on. Para evitar al usuario tener que utilizar directamente los
+{\ttfamily $\backslash$special} se pueden utilizar paquetes de m\'as alto nivel que, dependiendo
+de los conversores transforman sus \'ordenes a los {\ttfamily $\backslash$special}
+correspondientes. Si se quiere obtener el resultado final en {\itshape pdf\/} hay una
+serie de limitaciones que hay que tener en cuenta, v\'ease \ref{tex-a-PDF} {(C\'omo obtengo un documento PDF a partir de mi documento \TeX{}?)}
+
+Para ello se puede utilizar el paquete {\itshape graphics\/}, que est\'a entre los
+paquetes adicionales del \LaTeXe{} (disponible en
+{\ttfamily CTAN:macros/latex/required/graphics/}). Dependiendo de las opciones
+deseadas se le llama como {\ttfamily graphics} (menos potente) o {\ttfamily graphicx} (m\'as
+potente y recomendado). Un paquete m\'as antiguo es {\itshape psfig\/} que en la
+pr\'actica ha sido sustituido en \LaTeXe{} por {\itshape graphics\/} que es el paquete
+oficial de introducci\'on de gr\'aficos externos en \LaTeXe{}. Sin embargo, si se
+usa \LaTeX{} 209 ser\'a necesario usar {\itshape psfig\/} (disponible en
+{\ttfamily CTAN:graphics/psfig})
+
+Tambi\'en es necesario tener un conversor de DVI al lenguaje de impresora que
+soporte esos {\ttfamily $\backslash$special}, lo que limita los formatos gr\'aficos soportados. En
+particular es especialmente interesante que soporten el formato {\ttfamily .eps}
+(postscript encapsulado), lo que hacen el {\itshape dvips\/} y los conversores que
+vienen con {\itshape Oz\TeX{}\/} o {\itshape \TeX{}tures\/}. La mayor parte de los
+visualizadores de DVI no mostrar\'an correctamente estas figuras, sino s\'olo su
+espacio. En cualquier caso, es conveniente leer primero la documentaci\'on del
+paquete {\itshape graphics\/} o alguna de las referencias que se dan a continuaci\'on.
+
+Existe en el {\ttfamily CTAN} documentaci\'on muy interesante acerca de este tema. El
+documento de Anik K. Goel ({\ttfamily CTAN:info/figsinltx.ps}) trata de
+diferentes formas de generar figuras y de incluirlas con {\itshape psfig\/} para
+\LaTeX{} 209. El documento de Keith Reckdahl ({\ttfamily CTAN:info/epslatex.pdf})
+est\'a m\'as dirigido al trabajo en \LaTeXe{} y a las figuras {\ttfamily .eps}. Una
+referencia excelente sobre el tema es el {\itshape \LaTeX{} Graphics Companion\/}, de
+M. Goossens, S. Rahtz y F. Mittelbach, v\'ease la secci\'on \ref{libros-int} {(Libros en otros idiomas)}.
+
+
+
+
+\subsubsection{Dibujando con \TeX{}}
+
+Existen una serie de formas de dibujar con \TeX{} en vez de importar archivos
+externos. Desde el simple uso del entorno {\itshape picture\/}, incluso con mejoras
+como las proporcionadas por {\itshape epic\/} a dibujos sofisticados (aunque lentos)
+con las macros {\itshape Pic\TeX{}\/}. Dependiendo de lo que se quiere hacer alguno de
+los siguientes sistemas puede ser el m\'as \'util:
+\begin{description}
+\item[pstricks] \mbox{}
+
+Disponible en {\ttfamily CTAN:graphics/pstricks}, que da acceso a la potencia
+de postscript desde \TeX{} mediante un uso sofisticado de los
+{\ttfamily $\backslash$special}. Necesita un conversor a postscript bueno (como
+p.ej. {\itshape dvips\/}), est\'a bien documentado y da buenos resultados.
+
+
+
+\item[pgf] \mbox{}
+
+{\itshape pgf\/} ({\itshape portable graphics format\/}) es un paquete de macros \TeX{} para
+crear dibujos. Su uso recuerda a {\itshape pstricks\/} y, aunque es menos potente
+que \'este, tiene la ventaja de que es compatible tanto con dvips como con
+{\itshape pdf\TeX{}\/}.
+
+
+
+\item[MetaPost] \mbox{}
+
+Toda la potencia de METAFONT, pero generando figuras postscript en vez de
+tipos. Para m\'as informaci\'on en castellano sobre {\itshape metapost\/} puede
+consultarse la p\'agina
+\ifpdf
+\href{http://w3.mecanica.upm.es/metapost}{http://w3.mecanica.upm.es/metapost}
+\else
+\onlynameurl{http://w3.mecanica.upm.es/metapost}
+\fi
+
+y para ver algunos ejemplos de lo que se puede hacer con {\itshape metapost\/},
+pueden seguirse los enlaces citados en
+\ifpdf
+\href{http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html}{http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html}
+\else
+\onlynameurl{http://ltx.blogspot.com/2003/09/ms-recursos-metapost.html}
+\fi
+.
+
+A partir de la versi\'on 3.7.1 del paquete gr\'afico {\itshape gnuplot\/} \'este ya
+permite exportar sus resultados en formato {\itshape metapost\/}. {\itshape gnuplot\/} est\'a
+disponible en {\ttfamily CTAN:graphics/gnuplot}.
+
+{\itshape pdf\LaTeX{}\/} tambi\'en trata {\itshape metapost\/} nativamente mediante el uso
+de {\ttfamily $\backslash$convertMPtoPDF}. La sintaxis es
+\begin{tscreen}
+\begin{verbatim}
+
+\convertMPtoPDF {nombre} {escala x} {escala y}
+\end{verbatim}
+\end{tscreen}
+
+Si el nombre del gr\'afico incluido tiene la extensi\'on {\ttfamily .mps}
+{\ttfamily $\backslash$includegraphics} llama internamente a esta orden de forma
+transparente al usuario y no es necesario incluirla de forma expl\'\i{}cita.
+
+El gr\'afico MP as\'\i{} incluido se puede manipular sin problema con los
+comandos habituales de graphicx: rotatebox, resizebox, scalebox, etc...
+
+Los archivos {\itshape metapost\/} pueden editarse con un editor de texto y
+conocimiento del lenguaje {\itshape metapost\/}, pero tambi\'en est\'a disponible el
+editor gr\'afico {\itshape Metagraf\/} para METAPOST, que se encuentra en fase
+avanzada de desarrollo. Est\'a escrito en {\itshape Java\/} y por tanto funciona
+bajo distintos sistemas operativos. Se encuentra disponible en la misma
+p\'agina anterior,
+\ifpdf
+\href{http://w3.mecanica.upm.es/metapost}{ http://w3.mecanica.upm.es/metapost}
+\else
+\onlynameurl{ http://w3.mecanica.upm.es/metapost}
+\fi
+.
+
+
+El programa {\itshape pstoedit\/} permite pasar de postscript a otros formatos
+editables, entre ellos {\itshape metapost\/}, aunque es posible que en el cambio
+se pierdan elementos del dibujo original.
+
+\item[MfPic] \mbox{}
+
+Disponible en {\ttfamily CTAN:graphics/mfpic}. Este paquete genera c\'odigo
+METAFONT a partir de macros \TeX{} como las habituales. No da toda la
+potencia de METAFONT, pero es bastante m\'as c\'omodo.
+
+
+
+\item[dra\TeX{}] \mbox{}
+
+de Eitan Gurari. Disponible en {\ttfamily CTAN:macros/generic}. Un paquete de
+macros del tipo de {\itshape Pic\TeX{}\/}, pero mucho m\'as manejable y menos
+necesitado de recursos de ordenador.
+
+\end{description}
+
+
+
+
+
+\subsubsection{Introduciendo figuras postscript encapsulado en \LaTeX{}}
+
+Un ejemplo de documento en el que se incluye una figura {\itshape postscript\/} externa
+utilizando el paquete {\itshape graphicx\/} ser\'\i{}a (se supone que se utiliza
+el conversor {\itshape dvips\/})
+\begin{tscreen}
+\begin{verbatim}
+...
+
+\usepackage[dvips]{graphicx}
+
+...
+
+\begin{figure}
+ \centering
+ \includegraphics[width=10cm]{imagen.eps}
+ \caption{Esto es una imagen}
+ \label{fig:prueba}
+\end{figure}
+
+...
+\end{verbatim}
+\end{tscreen}
+
+que incluir\'\i{}a la figura {\ttfamily imagen.eps} con una anchura de 10cm. N\'otese que el
+que \LaTeX{} haya procesado sin problemas no implica que se vaya a ver con el
+visualizador ni que se vaya a imprimir a una impresora, ya que para ello los
+conversores correspondientes deben saber c\'omo hacerlo (P.ej., {\itshape dvips\/} sabe
+como incluir figuras {\itshape postscript\/} y si se ha compilado con esa opci\'on algunos
+tipos de mapas de bits). Asimismo es conveniente usar {\ttfamily $\backslash$centering} en vez del
+entorno {\ttfamily center}, ya que este \'ultimo no es para centrar texto, sino para
+componer un poco aparte texto centrado, con blancos antes y despu\'es. Si se usa
+center en un figure habr\'a algo de espacio adicional que no deber\'\i{}a estar
+ah\'\i{}. Adem\'as,{\ttfamily $\backslash$centering} se puede usar tambi\'en como entorno, si fuera
+necesario {\ttfamily ($\backslash$begin$\{$centering$\}$} {\ttfamily ...} {\ttfamily $\backslash$end$\{$centering$\}$)}. Si se desea
+cambiar la separaci\'on con {\ttfamily centering} pueden cambiarse {\ttfamily $\backslash$textfloatsep}
+(para b y t) e {\ttfamily $\backslash$intextsep} (para h) con {\ttfamily $\backslash$setlength}.
+
+Para contener el gasto en espacio de disco que supone usar PostScript, el
+paquete {\itshape graphicx\/} permite que las figuras que se van a incluir
+est\'en comprimidas con {\itshape gzip\/}, puesto que entiende los sufijos
+{\ttfamily .eps.gz} y {\ttfamily .ps.gz}. Para que \LaTeX{} sepa el tama\~no de la
+figura que est\'a en el archivo, debe existir otro con extensi\'on
+{\ttfamily .eps.bb} o {\ttfamily .ps.bb} con la {\itshape Bounding Box\/} (medidas de la
+caja) de la figura en PostScript, que se puede obtener de ese mismo
+archivo (es una de las primeras l\'\i{}neas) o usando alg\'un programa como
+{\itshape psbb\/}, distribuido con las utilidades {\ttfamily groff} de GNU
+(
+\ifpdf
+\href{http://www.gnu.org}{http://www.gnu.org}
+\else
+\onlynameurl{http://www.gnu.org}
+\fi
+).
+
+
+
+
+\subsubsection{Introduciendo im\'agenes en mapa de bits en \LaTeX{}.}
+
+En este caso la l\'\i{}nea del {\ttfamily $\backslash$includegraphics...} anterior se convertir\'\i{}a en
+\begin{tscreen}
+\begin{verbatim}
+\includegraphics[0,0][101mm,50mm]{figura.pcx}
+\end{verbatim}
+\end{tscreen}
+
+donde suponemos que el conversor soporta este formato. Se le ha dicho
+espec\'\i{}ficamente el tama\~no de la figura, ya que si no fuera as\'\i{}, se obtendr\'\i{}an
+distintos resultados al imprimirla en impresoras de distinta resoluci\'on.
+
+
+
+
+\subsubsection{Inclusi\'on de una imagen desde un PDF con m\'ultiples p\'aginas.}
+
+Puede hacerse con el paquete {\itshape graphicx\/}
+\begin{tscreen}
+\begin{verbatim}
+\includegraphics[page=6]{archivo}
+\end{verbatim}
+\end{tscreen}
+
+o con el paquete {\itshape pdfpages\/},
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{pdfpages}
+...
+\begin{document}
+\includepdf[pages={3-7,9}]{/path/to/other.pdf}
+\end{document}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{Introduciendo c\'odigo y figuras postscript en {\itshape pdf\TeX{}\/}
+\label{pdftex-dibujos} }
+
+{\itshape PDF\TeX{}\/} -- v\'ease la pregunta \ref{tex-a-PDF} {(C\'omo obtengo un documento PDF a partir de mi documento \TeX{}?)} -- no permite la inclusi\'on
+directa ni de c\'odigo ni de figuras PostScript. Pueden incluirse figuras en
+{\itshape PDF\TeX{}\/} siempre que \'estas est\'en en alguno de los formatos {\itshape JPEG\/},
+{\itshape PDF\/} \'o {\itshape PNG\/} (V\'eanse en el p\'arrafo siguiente las extensiones por
+omisi\'on que se esperan para cada formato). Parece que el soporte para formato
+{\itshape TIFF\/} se ha eliminado a partir de la versi\'on 1.10a de {\itshape pdf\TeX{}\/}, por
+lo que aunque se vuelva a poner es preferible utilizar alguno de los formatos
+anteriores. Existen utilidades para convertir de PostScript encapsulado a
+{\itshape PDF\/} y {\itshape PNG\/} ({\itshape Distiller\/} de Adobe (
+\ifpdf
+\href{http://www.adobe.com}{http://www.adobe.com}
+\else
+\onlynameurl{http://www.adobe.com}
+\fi
+) para {\itshape PDF\/} y
+{\itshape ghostscript\/} -- {\itshape gs\/} -- (
+\ifpdf
+\href{http://www.cs.wisc.edu/~ghost/index.html}{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\else
+\onlynameurl{http://www.cs.wisc.edu/\~{}ghost/index.html}
+\fi
+) para convertir a {\itshape PDF\/} o
+a {\itshape PNG\/}). Para este \'ultimo se tienen dos programas que lo utilizan y hacen
+de intermediario con el usuario, {\itshape ps2pdf\/}, incluido en {\itshape ghostscript\/} y
+{\itshape epstopdf\/} (disponible en
+{\ttfamily CTAN:usergrps/uktug/baskerville/epstopdf}, e incluido al menos en
+{\itshape te\TeX{}\/}) para conversi\'on directa entre los formatos {\ttfamily .eps} y {\ttfamily .pdf}
+
+Aunque no de forma directa, el paquete {\itshape tex4pdf\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/ps2pdf} permite incluir figuras y c\'odigo
+postscript (figuras pstricks y eps, cadenas psfrag, reescalados postscript) en
+un documento procesado con pdflatex, pero necesita versiones recientes de los
+paquetes {\itshape preview\/}, {\itshape ifpdf\/} e {\itshape ifvtex\/} y del sistema \TeX{}/\LaTeX{},
+as\'\i{} como adaptar el documento \LaTeX{} para su uso. Tambi\'en pueden utilizarse,
+con mejor o peor fortuna otros mecanismos (V\'ease \ref{tex-a-PDF} {(C\'omo obtengo un documento PDF a partir de mi documento \TeX{}?)})
+
+Para incluir una figura en {\itshape PDF\TeX{}\/} se deben seguir los mismos pasos que
+para incluir una figura PostScript encapsulado en \LaTeX{}. Cuando la figura
+se tiene en dos formatos distintos, uno para pdf\LaTeX{} y otro para
+\LaTeX{}/dvips, es recomendable omitir la extensi\'on del archivo ({\ttfamily .ps},
+{\ttfamily .eps}, {\ttfamily .ps.gz}, {\ttfamily .eps.gz} para PostScript y {\ttfamily .jpg}, {\ttfamily .tif},
+{\ttfamily .pdf}, o {\ttfamily .png} para {\itshape PDF\TeX{}\/}). De esta forma el paquete
+{\itshape graphicx\/} tomar\'a el archivo adecuado seg\'un se est\'e usando \LaTeX{} o
+PDF\LaTeX{}.
+
+
+
+
+\subsubsection{C\'omo coloco un fragmento TeX en una figura?}
+
+Esencialmente hay dos formas, mediante los paquetes {\itshape psfrag\/} y
+{\itshape overpic\/},
+\begin{description}
+\item[psfrag] \mbox{}
+
+permite sustituir cadenas de texto en el gr\'afico postscript por
+cadenas de texto \TeX{}. Para ello la cadena de texto a sustituir
+debe estar en el archivo postscript de forma expl\'\i{}cita
+utilizando alguno de los tipos postscript en vez de dibujada
+mediante l\'\i{}neas. Es decir, en el archivo postscript debe
+aparecer {\itshape (cadena)\/} donde cadena es la cadena de texto a
+sustituir. Esta cadena debe estar compuesta preferentemente de
+caracteres los alfanum\'ericos a-zA-Z0-9, aunque puede funcionar
+en algunos otros casos. Para usarlo se cargar\'\i{}a el paquete en el
+pre\'ambulo:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{psfrag}
+\end{verbatim}
+\end{tscreen}
+
+y dentro de un begin-end que englobe la figura o utilizando llaves (para que
+su efecto no se extienda a otras figuras salvo que se quiera) se incluir\'\i{}a
+\begin{tscreen}
+\begin{verbatim}
+\psfrag{cadena_original}{cadena_sustituta}
+\end{verbatim}
+\end{tscreen}
+
+por cada una de las cadenas a sustituir.
+
+
+Este sistema NO funciona directamente con pdf\LaTeX{} salvo que se utilice
+{\itshape vtex\/}. V\'ease \ref{tex-a-PDF} {(C\'omo obtengo un documento PDF a partir de mi documento \TeX{}?)}. Del mismo modo, las cadenas sustituidas no se ven
+correctamente en los visores de dvi habituales, sino s\'olo cuando se ha pasado
+a postscript. Puede hacerse funcionar con pdf\LaTeX{} de forma indirecta
+mediante el paquete {\itshape ps4pdf\/} o programas como {\itshape tex2pdf\/}.
+
+
+
+\item[overpic] \mbox{}
+
+El paquete {\itshape overpic\/} permite colocar cualquier tipo de texto
+sobre una figura e incluso figuras sobre figuras. Tiene dos formas de
+introducir las coordenadas, absolutas en \% de la figura original, y
+relativas, en \% de la figura reescalada. Asimismo cuenta con una excelente
+documentaci\'on.
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{overpic}
+\end{verbatim}
+\end{tscreen}
+
+
+\end{description}
+
+
+
+
+
+\subsection{Figuras, tablas y elementos flotantes\label{tex-floats}}
+
+
+
+
+\subsubsection{C\'omo puedo poner una figura rodeada de texto?}
+
+Para ello existen distintas opciones, mediante los paquetes
+\begin{itemize}
+\item {\itshape wrapfig\/} ({\ttfamily CTAN:macros/latex/contrib/other/misc/wrapfig.sty})
+Contiene {\itshape wraptable\/}, para hacer lo mismo con tablas.
+\item {\itshape floatflt\/} ({\ttfamily CTAN:macros/latex/contrib/other/floatflt/})
+\item {\itshape picins\/} ({\ttfamily CTAN:macros/latex209/contrib/picins/}), que tambi\'en
+puede utilizarse con tablas.
+\item {\itshape picinpar\/} ({\ttfamily CTAN:macros/latex209/contrib/picinpar})
+\end{itemize}
+
+todos ellos disponibles en el {\ttfamily CTAN}. Para casos sencillos un simple
+{\ttfamily parbox} o una {\ttfamily minipage} pueden hacer un buen trabajo.
+
+
+
+
+\subsubsection{C\'omo puedo poner una figura a dos columnas?}
+
+Usando el entorno {\ttfamily figure*} en vez de {\ttfamily figure}, para que \LaTeX{} sepa
+que ese elemento flotante es de doble ancho. Si no, lo considera de ancho
+normal, y la imagen que se mete dentro, simplemente {\itshape no cabe\/} y se sale por
+el otro lado, ocultando el texto de la otra columna.
+
+
+
+
+\subsubsection{C\'omo consigo un mayor control de la posici\'on de figuras y dem\'as elementos flotantes?}
+
+Para ello puede utilizarse el paquete {\itshape float\/},
+({\ttfamily CTAN:macros/contrib/supported/float}, que a\~nade nuevas
+funcionalidades al comportamiento normal de los elementos flotantes como
+figuras y tablas.
+
+
+
+
+\subsubsection{Puedo poner una figura en una tabla?}
+
+Por qu\'e no?,
+\begin{tscreen}
+\begin{verbatim}
+...
+\usepackage{graphcix}
+...
+\begin{tabular}{ccc}
+\includegraphics{fig1} &
+\includegraphics{fig2} &
+...
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{C\'omo colocar dos figuras o tablas juntas de distintas formas?,
+ }
+
+Es posible colocar en \LaTeX{} dos figuras o tablas en paralelo, cada una con
+su pie, as\'\i{} como dos figuras juntas en posici\'on arbitraria o superpuestas
+dentro de un entorno figure.
+
+Dependiendo de lo que se quiera, puede hacerse bien mediante el paquete
+{\itshape subfigure\/} o mediante un entorno {\itshape minipage\/} (V\'ease
+{\itshape epslatex.ps\/}). {\itshape subfigure\/} permite numerar las figuras como (a), ... y
+tener un pie com\'un a las subfiguras m\'as pies individuales para cada subfigura
+y {\itshape minipage\/} mantiene los pies normales e independientes para cada
+figura. Por ejemplo, con {\itshape minipage\/},
+\begin{tscreen}
+\begin{verbatim}
+ \usepackage{capt-of}
+ ...
+ \begin{figure}
+ \begin{minipage}{.5\linewidth}
+ Figure
+ \caption{Foo}
+ \end{minipage}%
+ \begin{minipage}{.5\linewidth}
+ Table
+ \captionof{table}{Too}
+ \end{minipage}
+ \end{figure}
+\end{verbatim}
+\end{tscreen}
+
+El uso del paquete {\itshape capt-of\/} (V\'ease "Puedo poner un pie en tablas y figuras
+que no flotan?") ser\'\i{}a necesario en este caso ya que los dos elementos son
+distintos, una figura y una tabla, pero no ser\'\i{}a necesario si los dos fueran
+figuras o los dos tablas.
+
+Si lo que se quiere es simplemente colocar dos figuras juntas adem\'as de lo
+anterior sin {\ttfamily $\backslash$caption} puede utilizarse algo como
+\begin{tscreen}
+\begin{verbatim}
+\setlength{\unitlengtth}{1cm}\begin{picture}(12,6)
+\put(0,0){\includegraphics[width=6cm]{figura1.ps}}
+\put(6,0){\includegraphics[width=6cm]{figura2.ps}}
+\end{picture}
+\end{verbatim}
+\end{tscreen}
+
+As\'\i{} las figuras se colocan como uno quiera e incluso puede hacerse que una
+figura se superponga sobre otra (como si fueran fotos en una mesa).
+
+
+
+
+\subsubsection{Puedo poner un pie en tablas y figuras que no flotan?,
+ }
+
+A veces se desea colocar figuras y tablas en un lugar preciso y para ello se
+prescinde de los entornos {\itshape figure\/} y {\itshape table\/}. Sin embargo tambi\'en se
+desea poder usar {\ttfamily $\backslash$caption} para no perder la numeraci\'on y la
+referencia en la lista de figuras y tablas.
+
+Un equivalente a la orden {\ttfamily $\backslash$caption} llamado {\ttfamily $\backslash$captionof} puede ser
+utilizado fuera de entornos flotantes ({\itshape figure\/} y {\itshape table\/}) si se hace
+uso del paquete {\itshape capt-of\/}. Su sintaxis es {\ttfamily $\backslash$captionof$\{$tipo$\}$[pie
+corto]$\{$pie largo$\}$} donde el pie corto es el opcional que ir\'a a la tabla de
+figuras/tablas y el tipo es figura/tabla.
+
+La llamada en el documento ser\'\i{}a del tipo
+\begin{tscreen}
+\begin{verbatim}
+\centerline{\includegraphics{mi grafica}}
+\captionof{figure}{Esta es mi grafica}
+\end{verbatim}
+\end{tscreen}
+
+para una figura, mientras que para una tabla se puede usar algo del tipo:
+\begin{tscreen}
+\begin{verbatim}
+\begin{center}
+\begin{tabular}{*2l}\hline\hline
+uno & dos\\
+tres & cuatro\\\hline
+\end{tabular}
+\end{center}
+\captionof{table}{Esto es una tabla} % se puede incluir dentro del entorno center.
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{C\'omo hago para incluir elementos flotantes grandes o numerosos sin que den errores o se vayan al final?}
+
+Las clases {\itshape article\/}, {\itshape report\/} y {\itshape book\/} est\'andar son muy exigentes en
+cuanto a sus "consideraciones est\'eticas" para poner gr\'aficos flotantes en una
+p\'agina. El caso es que \'esto s\'olo es \'util cuando hay pocos objetos flotantes,
+pero si hay muchos, esta exigencia es contraproducente. Lo que acaba pasando
+es que \LaTeX{} no encuentra lugares adecuados para poner los gr\'aficos y los
+acaba mandando todos al final o dando errores. Afortunadamente, los par\'ametros
+que controlan todo \'esto son f\'acilmente configurables y para mejorar las cosas
+basta copiar y pegar los que vienen en {\itshape amsart.cls\/}, que son mucho mas
+flexibles,
+\begin{tscreen}
+\begin{verbatim}
+
+\setcounter{topnumber}{4}
+\setcounter{bottomnumber}{4}
+\setcounter{totalnumber}{4}
+\setcounter{dbltopnumber}{4}
+\renewcommand{\topfraction}{.97}
+\renewcommand{\bottomfraction}{.97}
+\renewcommand{\textfraction}{.03}
+\renewcommand{\floatpagefraction}{.9}
+\renewcommand{\dbltopfraction}{.97}
+\renewcommand{\dblfloatpagefraction}{.9}
+\setlength{\floatsep}{12pt plus 6pt minus 4pt}
+\setlength{\textfloatsep}{15pt plus 8pt minus 5pt}
+\setlength{\intextsep}{12pt plus 6pt minus 4pt}
+\setlength{\dblfloatsep}{12pt plus 6pt minus 4pt}
+\setlength{\dbltextfloatsep}{15pt plus 8pt minus 5pt}
+\end{verbatim}
+\end{tscreen}
+
+Cuando se quiere hacer para una \'unica figura puede utilizarse el paquete
+{\itshape afterpage\/}, por ejemplo en
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{afterpage}
+...
+\begin{figure}
+\includegraphics{figura-muy-grande}
+\end{figure}
+\afterpage{\clearpage}
+\end{verbatim}
+\end{tscreen}
+
+la figura grande pasar\'a a la p\'agina siguiente (donde quedar\'a sola), en lugar de
+irse al final del documento.
+
+
+
+
+\subsection{C\'omo giro un elemento en un documento \LaTeX{}?}
+
+Para giros sencillos, el paquete {\itshape graphicx\/} contiene las orden
+{\ttfamily $\backslash$rotatebox} que permite conseguir giros de elementos de texto o
+incluso de elementos m\'as complejos.
+Sin embargo, cuando se quieren rotar
+elementos complejos es recomendable aprovechar las posibilidades del paquete
+{\itshape rotating\/} (disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/rotating}). Este paquete permite
+girar casi cualquier tipo de elemento, incluyendo figuras o tablas completas
+con sus cabeceras, mediante los entornos {\itshape sideways\/}, {\itshape sidewaystable\/} y
+{\itshape sidewaysfigure\/}. Por ejemplo,
+\begin{tscreen}
+\begin{verbatim}
+\documentclass{article}
+\usepackage{rotating}
+\begin{document}
+\begin{sideways}
+\begin{tabular}....
+
+\end{tabular}
+\end{sideways}
+\end{document}
+\end{verbatim}
+\end{tscreen}
+
+Hay que tener en cuenta que en todos estos casos se modifica el postscript,
+por lo que los resultados no se ven correctamente con {\itshape xdvi\/} ni funcionan
+bien con {\itshape pdflatex\/}.
+
+
+
+
+\subsection{C\'omo escribo algunos s\'\i{}mbolos?}
+
+\begin{description}
+\item[C\'omo obtener el s\'\i{}mbolo del euro?] \mbox{}
+
+Utilizando el paquete {\itshape eurofont\/} de CTAN. Contiene instrucciones acerca de
+su uso con \LaTeX{}. La notaci\'on de entrada normal es
+{\ttfamily $\backslash$EUR$\{$1,50$\}$}. Tambi\'en puede utilizarse el paquete textcomp y la macro
+{\ttfamily $\backslash$texteuro}.
+
+\item[C\'omo escribir los grados en \LaTeX{}?] \mbox{}
+
+Para obtener un resultado de mejor calidad que con {\ttfamily \^{}$\backslash$circ} puede
+utilizarse la orden {\ttfamily $\backslash$textdegree} del paquete {\itshape textcomp\/}.
+
+\item[C\'omo encerrar un caracter en un c\'\i{}rculo?] \mbox{}
+
+Utilizando la orden {\ttfamily $\backslash$textcircled$\{$...$\}$}
+
+\item[C\'omo escribir la barra invertida?] \mbox{}
+
+Como texto: {\ttfamily $\backslash$textbackslash}.
+Como matem\'aticas: {\ttfamily $\backslash$backslash}.
+Como c\'odigo: {\ttfamily $\backslash$verb$|$$\backslash$$|$}
+
+\item[C\'omo escribir un espacio en blanco visible?] \mbox{}
+
+Utilizando la orden {\ttfamily $\backslash$textvisiblespace}
+
+\item[C\'omo escribir el s\'\i{}mbolo del sombrerito de la \~n?] \mbox{}
+
+Utilizando la orden {\ttfamily $\backslash$textasciitilde}
+
+\end{description}
+
+
+
+
+
+\subsection{C\'omo convierto mis documentos a \LaTeX{} y desde \LaTeX{}?}
+
+Existe una FAQ espec\'\i{}fica acerca de las conversiones entre formatos \TeX{}
+y de otros procesadores de textos,
+que se archiva en {\ttfamily CTAN:help/wp-conv/wp-conv.zip}.
+
+
+
+
+\subsubsection{C\'omo obtengo un documento PDF a partir de mi documento \TeX{}?
+\label{tex-a-PDF} }
+
+Existen distintas formas de producir PDF usando (La)\TeX{}.
+\begin{itemize}
+\item A partir del PS -- ver la pregunta \ref{postscript} {(Qu\'e es PostScript?)} --, usando {\itshape Distiller\/} (de Adobe) o
+{\itshape ghostscript\/}, en este \'ultimo caso, se recomienda usar una versi\'on
+posterior a la 5.53, que mejora el PDF generado (lo hace m\'as compacto). Se
+pueden perder los enlaces y algunas caracter\'\i{}sticas de PDF (las
+anotaciones). Las distribuciones de {\itshape ghostscript\/} suelen venir con un
+peque\~no programa llamado {\itshape ps2pdf\/} que hace la transformaci\'on llamando a
+{\itshape ghostscript\/} con los par\'ametros adecuados.
+\item A partir de DVI, usando {\itshape dvipdfm\/}, ({\ttfamily CTAN:dviware/dvipdfm}), que
+genera PDF de alta calidad, insertando los gr\'aficos y permitiendo
+anotaciones y enlaces. Su p\'agina ra\'\i{}z es
+\ifpdf
+\href{http://odo.kettering.edu/dvipdfm}{http://odo.kettering.edu/dvipdfm}
+\else
+\onlynameurl{http://odo.kettering.edu/dvipdfm}
+\fi
+, pero tiene una serie de
+restricciones que deben consultarse en el manual.
+\item Usando {\itshape pdf\TeX{}\/}, que procesa el archivo fuente de \TeX{} y genera PDF
+directamente. Acompa\~nado por el paquete {\itshape hyperref\/}, es de la m\'axima
+utilidad en la generaci\'on de documentos que mantienen la calidad de
+composici\'on de textos de \TeX{} y permiten cierta interacci\'on. {\itshape pdf\TeX{}\/}
+est\'a a\'un en desarrollo, pero permite generar PDF para casi todos los
+documentos -- para ver los detalles y limitaciones en la inclusi\'on de
+figuras y c\'odigo postscript, v\'ease la secci\'on \ref{pdftex-dibujos} {(Introduciendo figuras y c\'odigo postscript en pdf\TeX{})} --.
+Las versiones de desarrollo pueden encontrarse
+en:
+\ifpdf
+\href{http://www.fi.muni.cz/~thanh/download/}{http://www.fi.muni.cz/\~{}thanh/download/}
+\else
+\onlynameurl{http://www.fi.muni.cz/\~{}thanh/download/}
+\fi
+. Informaci\'on adicional est\'a
+disponible en
+\ifpdf
+\href{http://www.tug.org/interest.html#projects}{http://www.tug.org/interest.html\#projects}
+\else
+\onlynameurl{http://www.tug.org/interest.html\#projects}
+\fi
+.
+\end{itemize}
+
+Cuando el documento de entrada no contiene \'unicamente texto \TeX{}/\LaTeX{} sino
+tambi\'en figuras en postscript encapsulado o utiliza paquetes que mediante
+c\'odigo postscript cambian el texto (rotaciones, reescalados, sustituci\'on de
+cadenas) o dibujan, las cosas son un poco m\'as complicadas ya que {\itshape pdf\TeX{}\/}
+no lo soporta directamente. El camino {\ttfamily dvi-{$>$}ps-{$>$}pdf} que se ha se\~nalado
+antes debe funcionar pero pueden perderse por el camino algunas caracter\'\i{}sticas
+del pdf. Otros caminos alternativos pasan por convertir sobre la marcha a pdf
+las figuras y efectos postscript. Esto puede hacerse, con m\'as o menos
+limitaciones de distintas formas:
+\begin{itemize}
+\item Utilizando {\itshape tex2pdf\/}, disponible en
+\ifpdf
+\href{http://developer.berlios.de/cvs/?group_id=57}{http://developer.berlios.de/cvs/?group\_id=57}
+\else
+\onlynameurl{http://developer.berlios.de/cvs/?group\_id=57}
+\fi
+. La idea es que
+{\itshape tex2pdf\/} procesa cada grafico que emplea sustituciones de {\itshape psfrag\/} y
+luego lo convierte a pdf. Para gr\'aficos que no se encuentran en minipages,
+tablas, funciona relativamente bien. La \'ultima versi\'on cvs de {\itshape tex2pdf\/}
+soporta preliminarmente {\itshape psfrag\/} y {\itshape pstricks\/} (este ultimo a traves de
+{\itshape ps4pdf\/}), sin embargo, de momento el proyecto parece parado,
+\item {\itshape v\TeX{}\/} es una distribuci\'on comercial de \TeX{} que da salida {\itshape .pdf\/}
+directamente y soporta inclusi\'on de figuras {\ttfamily .eps}, as\'\i{} como el uso de
+{\itshape psfrag\/} y de algunos otros paquetes que utilizan {\itshape postscript\/} de alto
+nivel. Existen versiones para linux y OS/2 gratuitas, disponibles en
+\begin{itemize}
+\item
+\ifpdf
+\href{http://www.micropress-inc.com/linux/}{http://www.micropress-inc.com/linux/}
+\else
+\onlynameurl{http://www.micropress-inc.com/linux/}
+\fi
+
+\item
+\ifpdf
+\href{http://www.micropress-inc.com/os2/}{http://www.micropress-inc.com/os2/}
+\else
+\onlynameurl{http://www.micropress-inc.com/os2/}
+\fi
+
+\end{itemize}
+
+y en {\ttfamily CTAN:systems/vtex}. La versi\'on para Windows es comercial
+\ifpdf
+\href{http://www.micropress-inc.com}{http://www.micropress-inc.com}
+\else
+\onlynameurl{http://www.micropress-inc.com}
+\fi
+
+\item Utilizando el paquete {\itshape pdftricks\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/pdftricks}, que intenta extender el poder
+del paquete {\itshape pstricks\/} a pdf\LaTeX{}.
+\item Utilizando el paquete {\itshape ps4pdf\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/ps4pdf}. V\'ease \ref{pdftex-dibujos} {(Introduciendo c\'odigo y figuras postscript en {$<$}em/pdf\TeX{})}
+\end{itemize}
+
+
+
+
+
+\subsubsection{C\'omo obtengo una versi\'on texto a partir de un documento PDF?}
+
+La forma m\'as sencilla es mediante el {\itshape Adobe Reader\/} (antes {\itshape Acrobat
+Reader\/}) -- v\'ease \ref{formato-pdf} {(El formato pdf)} -- utilizando
+la herramienta {\itshape Obtener texto\/} que se encuentra a la izquierda en el
+{\itshape Adobe Reader\/}.
+
+
+
+
+\subsubsection{C\'omo obtengo un documento html a partir de mi documento \TeX{}?
+\label{tex-a-html} }
+
+En la p\'agina
+\ifpdf
+\href{http://www.mayer.dial.pipex.com/tex.htm}{http://www.mayer.dial.pipex.com/tex.htm}
+\else
+\onlynameurl{http://www.mayer.dial.pipex.com/tex.htm}
+\fi
+ se comentan diferentes
+programas de conversi\'on de \LaTeX{} a html con ejemplos del resultado de las
+distintas conversiones. Los m\'as conocidos son
+\begin{description}
+\item[HEVEA] \mbox{}
+
+es un conversor de \LaTeX{} a html bastante completo, que
+convierte los s\'\i{}mbolos sin utilizar gr\'aficos (aunque puede requerir un poco de
+configuraci\'on del navegador). Disponible en
+\ifpdf
+\href{http://para.inria.fr/~maranget/hevea/}{http://para.inria.fr/\~{}maranget/hevea/}
+\else
+\onlynameurl{http://para.inria.fr/\~{}maranget/hevea/}
+\fi
+. Tiene versiones para Linux,
+Solaris y Windows aunque es posible compilarlo para otros sistemas
+operativos a partir del c\'odigo fuente.
+
+\item[TTH] \mbox{}
+
+es otro conversor de \LaTeX{} a html que tambi\'en convierte las
+ecuaciones en vez de representarlas como im\'agenes. Disponible en
+\ifpdf
+\href{http://hutchinson.belmont.ma.us/tth/}{http://hutchinson.belmont.ma.us/tth/}
+\else
+\onlynameurl{http://hutchinson.belmont.ma.us/tth/}
+\fi
+. Tiene versiones para Linux,
+Mac y Windows aunque es posible compilarlo para otros sistemas operativos a
+partir del c\'odigo fuente. Utiliza gr\'aficos.
+
+\item[\TeX{}4ht] \mbox{}
+
+es otro conversor a distintos sistemas de hipertexto,
+disponible en
+\ifpdf
+\href{http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html}{http://www.cis.ohio-state.edu/\~{}gurari/TeX4ht/mn.html}
+\else
+\onlynameurl{http://www.cis.ohio-state.edu/\~{}gurari/TeX4ht/mn.html}
+\fi
+. Tiene
+versiones para Linux, Mac y Windows aunque es posible compilarlo para otros
+sistemas operativos a partir del c\'odigo fuente.
+
+\item[latex2html] \mbox{}
+
+es quiz\'as el m\'as antiguo de los conversores, escrito en perl y utiliza
+gr\'aficos.
+
+\end{description}
+
+
+
+
+
+\subsubsection{Convirtiendo a \LaTeX{} desde otros formatos}
+
+\begin{description}
+\item[WordPerfect] \mbox{}
+
+El programa {\itshape wp2latex\/} (disponible en {\ttfamily CTAN:support/wp2latex}) ha
+sido recientemente actualizado por Jaroslav Fojtik y ahora est\'a disponible
+tanto para {\itshape DOS\/} como para {\itshape Unix\/}.
+
+
+
+\item[Rich Text Format (RTF)] \mbox{}
+
+Hay dos conversores disponibles, {\itshape rtf2tex\/} de Robert Lupton (disponible
+en {\ttfamily CTAN:support/rtf2tex}) y {\itshape rtf2latex\/}, de Erwin Wechtl
+(disponible en {\ttfamily CTAN:support/rtf2latex}), para \TeX{} y \LaTeX{}
+respectivamente.
+
+
+
+\item[Microsoft Word] \mbox{}
+
+Aunque hay un programa de conversi\'on ({\itshape wd2latex\/}, disponible en
+{\ttfamily CTAN:dviware/wd2latex}), se recomienda convertir el documento a RTF
+y utilizar uno de los conversores de RTF mencionados.
+
+Tambi\'en hay un par de conversores comerciales, {\itshape word2tex\/} y
+{\itshape tex2word\/}.
+
+\end{description}
+
+
+
+
+
+
+
+\subsection{C\'omo rehago los formatos de \TeX{} y \LaTeX{}?\label{formatos}}
+
+Los formatos de \TeX{} son archivos que contienen las macros b\'asicas
+precompiladas para obtener una mayor eficiencia. Para rehacer un
+formato es necesario utilizar la orden {\ttfamily initex} (Este nombre cambia
+para algunas distribuciones, por ejemplo para {\itshape em\TeX{}\/} es {\ttfamily tex
+-i}). Como muestra, para rehacer el formato {\itshape plain\/} se har\'\i{}a
+\begin{tscreen}
+\begin{verbatim}
+initex plain \dump
+\end{verbatim}
+\end{tscreen}
+
+Con eso se tiene el archivo {\ttfamily plain.fmt}; ya s\'olo queda reemplazarlo donde
+estuviera el original y listo.
+
+Para hacerlo por ejemplo para {\itshape eplain\/} se habr\'\i{}a hecho {\ttfamily initex plain}, y
+cuando aparece {\ttfamily *} se introducir\'\i{}a {\ttfamily $\backslash$input eplain} y
+despu\'es cuando vuelve a aparecer {\ttfamily *} se introducir\'\i{}a
+{\ttfamily $\backslash$dump}, as\'\i{} tendr\'\i{}a un formato con {\ttfamily eplain} y no habr\'\i{}a que
+estar poni\'endolo con {\ttfamily $\backslash$input}.
+
+Cuando deben incluirse distintos archivos en el formato, a menudo es m\'as c\'omodo
+utilizar una archivo que los llame a todos. Por ejemplo, para
+{\ttfamily eplain} se podr\'\i{}a haber creado el archivo {\ttfamily eplain.ini} con las
+l\'\i{}neas
+\begin{tscreen}
+\begin{verbatim}
+\input plain
+\input eplain
+\dump
+\end{verbatim}
+\end{tscreen}
+
+y se habr\'\i{}a rehecho el formato con {\ttfamily initex eplain.ini}.
+
+En la mayor parte de las distribuciones modernas no es necesario rehacer los
+formatos como se ha dicho antes, sino que hay herramientas que ayudan
+a ello. As\'\i{}, por ejemplo en {\itshape te\TeX{}\/} despu\'es de configurar los
+distintos par\'ametros del formato (idioma, tama\~nos de memoria...) al
+salir se rehace autom\'aticamente el formato, o en {\itshape mik\TeX{}\/} donde
+hay un elemento en un men\'u desplegable para rehacer los formatos ( o
+desde una ventana DOS {\ttfamily initexmf --dump}).
+
+
+
+
+\subsection{C\'omo llamo a un editor desde \TeX{}/\LaTeX{}?}
+
+Dando el valor adecuado a la variable de entorno {\ttfamily TEXEDIT}
+\begin{tscreen}
+\begin{verbatim}
+SET TEXEDIT=tu_editor +%d %s
+\end{verbatim}
+\end{tscreen}
+
+en el {\ttfamily autoexec.bat} o similares o
+\begin{tscreen}
+\begin{verbatim}
+export TEXEDIT=tu_editor +%d %s
+\end{verbatim}
+\end{tscreen}
+
+para {\itshape bash\/} y similares
+
+
+
+
+\subsection{Algunas cosillas matem\'aticas.}
+
+
+\subsubsection{C\'omo escribo un n\'umero con periodo utilizando \LaTeX{}?}
+
+Para escribir un periodo (el acento breve invertido que indica la repetici\'on de
+cifras decimales y que se pone encima de la parte peri\'odica del
+n\'umero) la soluci\'on m\'as elegante consiste en utilizar el paquete
+{\itshape yhmath\/} de Yannis Haralambous, disponible en
+{\ttfamily CTAN:macros/latex/contrib/supported/yhmath}. Este paquete
+permite indicar periodos de longitud arbitraria mediante un acento
+matem\'atico {\ttfamily $\backslash$wideparen} que hace precisamente ese papel.
+
+El paquete {\itshape yhmath\/} necesita un tipo especial que viene con el paquete y
+adem\'as el paquete {\itshape amsmath\/}, por lo que para uso espor\'adico o no
+tan exigente puede bastar una definici\'on como la siguiente
+\begin{tscreen}
+\begin{verbatim}
+\def\periodo#1{\mathop{\vbox{\ialign{##\crcr\noalign{\kern3pt}%
+\ensuremath{\braceld\leaders\vrule\hfill\bracerd}%
+\crcr\noalign{\kern3pt\nointerlineskip}%
+\ensuremath{\hfill\displaystyle{#1}\hfill}\crcr}}}\limits}
+\end{verbatim}
+\end{tscreen}
+
+Existe otro paquete denominado {\itshape tipa\/}, disponible en
+{\ttfamily CTAN:/fonts/tipa}. \'Este es un sistema para trabajar con
+alfabetos fon\'eticos, que proporciona la orden
+{\ttfamily $\backslash$texttoptiebar$\{$'caracter'$\}$} donde {\ttfamily 'caracter'}
+obviamente es un numero(s) o una letra(s).
+
+
+
+
+\subsubsection{C\'omo puedo hacer para que la etiqueta de una ecuaci\'on p.ej. (3.5) contenga adem\'as el n\'umero de la secci\'on actual p.ej. (3.1.5) }
+
+La respuesta se puede encontrar en Lamport secci\'on 6.3 y en el Companion
+secci\'on 8.6 (Este cap\'\i{}tulo del Companion est\'a actualizado en
+{\ttfamily CTAN:info/companion-rev/}). \LaTeX{} define y mantiene unos cuantos
+contadores; uno de ellos es {\itshape equation\/}. Para generar una etiqueta impresa,
+\LaTeX{} ejecuta una orden cuyo nombre se forma a\~nadiendo {\ttfamily $\backslash$the} al
+comienzo del nombre del contador adecuado. Por ejemplo, un n\'umero de ecuaci\'on
+se genera con la orden {\ttfamily $\backslash$theequation}.
+
+Para cambiar la numeraci\'on de ecuaciones de modo que se indique el cap\'\i{}tulo, la
+secci\'on y un n\'umero correlativo dentro de la secci\'on har\'\i{}amos:
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\theequation}{\thesection.\arabic{equation}}
+\end{verbatim}
+\end{tscreen}
+
+El problema es que ahora tendr\'\i{}amos que volver a poner a cero el contador de
+ecuaciones al comienzo de cada secci\'on o cap\'\i{}tulo. Una soluci\'on sencilla es
+incluir en el pre\'ambulo (entre un {\ttfamily $\backslash$makeatletter} y un
+{\ttfamily $\backslash$makeatother}) lo siguiente:
+\begin{tscreen}
+\begin{verbatim}
+\@addtoreset {equation}{section}
+\end{verbatim}
+\end{tscreen}
+
+Esto har\'a que autom\'aticamente se ponga el contador {\itshape equation\/} a 1 cuando se
+encuentre un nuevo {\ttfamily $\backslash$section.}
+
+
+
+
+\subsubsection{C\'omo hay que hacer para lograr la N, R de doble trazo con que se representan los n\'umeros naturales, reales, etc...}
+
+Una forma que funciona incluso en plain \TeX{} y que no requiere cargar tipos
+adicionales es con definiciones del tipo
+\begin{tscreen}
+\begin{verbatim}
+\def\CC{{\rm C\kern-.18cm\vrule width.6pt height 6pt depth-.2pt \kern.18cm}}
+\def\NN{{\mathop{{\rm I}\kern-.2em{\rm N}}\nolimits}}
+\def\PP{{\mathop{{\rm I}\kern-.2em{\rm P}}\nolimits}}
+\def\RR{{\mathop{{\rm I}\kern-.2em{\rm R}}\nolimits}}
+\def\RRt{{\fa I}\kern-.2em{\fa R}}
+ %% This version of \RR can be used in the title of the paper
+\def\ZZ{{\mathop{{\rm Z}\kern-.28em{\rm Z}}\nolimits}}
+\end{verbatim}
+\end{tscreen}
+
+Tambi\'en es posible utilizar el tipo {\itshape mathbb\/} incluido con las
+{\itshape amsfonts\/}. \'Estas se cargar\'\i{}an en el pre\'ambulo con
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{amsfonts}
+\usepackage[mathscr]{euscript}
+\end{verbatim}
+\end{tscreen}
+
+y se llamar\'\i{}an como {\ttfamily $\backslash$mathbb$\{$C$\}$}, etc...
+
+Otra alternativa es el uso de los tipos {\itshape bbm\/}. Estos de cargan en el
+pre\'ambulo con
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{bbm}
+\end{verbatim}
+\end{tscreen}
+
+de forma que {\ttfamily \$$\backslash$mathbbm$\{$N, Z, R, Q, I, C$\}$\$} dar\'\i{}a el correspondiente
+s\'\i{}mbolo.
+
+
+
+
+\subsubsection{Puedo forzar que una f\'ormula tenga el mismo n\'umero que otra?}
+
+S\'\i{} mediante el paquete {\itshape amsmath\/} y la orden {\ttfamily $\backslash$tag}. Por ejemplo,
+\begin{tscreen}
+\begin{verbatim}
+\begin{equation}\label{1}
+1+1=2.
+\end{equation}
+\begin{equation}
+1+1=2.\tag{\ref{1}}
+\end{equation}
+\end{verbatim}
+\end{tscreen}
+
+
+
+\subsubsection{Puedo escribir s\'\i{}mbolos matem\'aticos en negrita?}
+
+Pues no es nada elemental. Sin tipos especiales no. Inicialmente no se consider\'o
+necesario que las letras griegas pudieran representar vectores y no se
+incluyeron tipos con ellas. La soluci\'on pasa por usar amstex y los tipos
+{\itshape euler\/} (m\'as en concreto {\itshape eurb\/}).
+
+Tambi\'en puede utilizarse el paquete {\itshape amsmath\/}. As\'\i{},
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{amsmath}
+\begin{document}
+$\boldsymbol{H}$
+\end{document}
+\end{verbatim}
+\end{tscreen}
+
+Si alg\'un s\'\i{}mbolo de alguna fuente no cambia a negrita con esta orden, puede
+tambi\'en utilizarse, con el mismo paquete, {\ttfamily \$$\backslash$pmb$\{$H$\}$\$}.
+
+
+
+
+\subsubsection{Puedo rotar una ecuaci\'on?}
+
+Puede utilizarse ls orden {\ttfamily rotatebox} del paquete {\itshape graphicx\/}, pero hay que
+meter la ecuaci\'on en un {\ttfamily parbox}, por ejemplo, utilizando el entorno
+{\ttfamily align}, del paquete {\itshape amsmath\/},
+\begin{tscreen}
+\begin{verbatim}
+\rotatebox{35}{
+ \parbox{4cm}{
+ \begin{align*}
+ (la ecuacion)
+ \end{align*}
+ }
+}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{Algunas preguntas matem\'aticas de breve respuesta.}
+
+\begin{description}
+\item[C\'omo se escriben los n\'umeros combinatorios (por ejemplo N sobre k)?] \mbox{}
+
+{\ttfamily $\backslash$binom$\{$N$\}$$\{$k$\}$}, disponible en el paquete {\itshape amsmath\/}.
+
+
+
+\item[C\'omo represento un tensor con sus \'\i{}ndices?] \mbox{}
+
+Puede probarse con el paquete {\itshape tensind\/}, disponible en
+{\ttfamily CTAN:/macros/latex/contrib/supported/bezos/}.
+
+
+
+\item[C\'omo cancelar elementos en una ecuaci\'on en \LaTeX{}] \mbox{}
+
+Mediante el paquete {\itshape cancel\/}
+
+
+
+\item[Cu\'al es la instrucci\'on para poner el producto vectorial?] \mbox{}
+
+{\ttfamily $\backslash$times} o {\ttfamily $\backslash$wedge}, seg\'un la forma que prefieras (cruz y
+angulito, respectivamente).
+
+
+
+\item[Qu\'e s\'\i{}mbolos est\'an disponibles para \LaTeX{}?] \mbox{}
+
+Adem\'as de los s\'\i{}mbolos b\'asicos de \LaTeX{} muchos otros s\'\i{}mbolos est\'an
+disponibles a trav\'es de distintos paquetes. Una excelente referencia a
+todos los s\'\i{}mbolos disponibles se encuentra en
+{\ttfamily CTAN:tex-archive/info/symbols/comprehensive}
+
+\end{description}
+
+
+
+
+
+
+
+\subsection{C\'omo hago cuadernillos, tr\'\i{}pticos y documentos con formatos especiales?
+\label{formatos-especiales} }
+
+
+\subsubsection{C\'omo hago cuadernillos con \TeX{} o \LaTeX{}?}
+
+Para hacer cuadernillos estrictamente con \TeX{} o \LaTeX{} se pueden utilizar
+las utilidades para manipular {\ttfamily .dvi} (disponibles en
+{\ttfamily CTAN:dviware/dvibook}) o utilizar el paquete {\itshape quire\/}
+(disponible en {\ttfamily CTAN:macros/generic/midnight}). Ambos permiten
+hacer cuadernillos, pero en ambos casos es necesario tener los tipos
+para los distintos tama\~nos antes y despu\'es, y dan problemas con
+facilidad cuando se incluyen gr\'aficos externos.
+
+El m\'etodo m\'as recomendable es utilizar las {\itshape psutils\/}, un conjunto de
+utilidades para manejar archivos {\itshape postscript\/}. Aunque el ejemplo
+est\'a para un unix, tambi\'en est\'an disponibles para {\itshape DOS\/}, lo \'unico
+que en vez de mandarlo a la cola de impresora se mandar\'\i{}a a un archivo
+que despu\'es se imprimir\'\i{}a con {\itshape ghostscript/ghostview\/}.
+
+Para Unix por ejemplo, si se colocan adecuadamente las hojas en la impresora
+\begin{tscreen}
+\begin{verbatim}
+psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -o | lpr
+\end{verbatim}
+\end{tscreen}
+
+imprimir\'\i{}a las caras impares del librillo (cada una de ellas con dos p\'aginas
+reducidas y correctamente ordenadas). Se sacan las hojas, se ordenan
+adecuadamente y se colocan adecuadamente en la impresora y
+\begin{tscreen}
+\begin{verbatim}
+psbook tu_archivo.ps | psnup -n 2 -pa4 | psselect -e | lpr
+\end{verbatim}
+\end{tscreen}
+
+imprimir\'\i{}a las caras pares del librillo, y ya est\'a, se tiene un librillo
+perfecto. La utilidad {\itshape pstops\/} tambi\'en permite hacer todo eso
+directamente, pero con unas opciones mucho m\'as cr\'\i{}pticas.
+
+{\itshape psbook\/} tambi\'en permite definir el tama\~no del pliego, cuando el libro va a
+constar de distintos pliegos cosidos, cada uno de ellos de un n\'umero
+de p\'aginas. Por ejemplo,
+\begin{tscreen}
+\begin{verbatim}
+$ psbook -s 16 manualA4.ps
+\end{verbatim}
+\end{tscreen}
+
+reordenar\'\i{}a las p\'aginas para hacer pliegos de 16 p\'aginas, y su salida se pasar\'\i{}a
+despu\'es por {\itshape psnup\/} y {\itshape psselect\/}. El comportamiento por omisi\'on
+consiste en hacer un \'unico pliego.
+
+
+
+
+\subsubsection{C\'omo hago tr\'\i{}pticos con \LaTeX{}?}
+
+El paquete {\itshape leaflet\/} nos permite construir tr\'\i{}pticos. Realmente s\'olo
+modifica los m\'argenes de la p\'agina completa para dividirla en tres \'areas. El
+resultado al compilar es un documento con 6 p\'aginas como m\'aximo, en el que
+cada p\'agina tiene el texto escrito en una columna estrecha a la izquierda y el
+resto de la p\'agina est\'a en blanco. Este documento a\'un no est\'a finalizado y
+debe ser postprocesado. El postproceso lo hace un script (que viene incluido
+en el paquete), que se ocupa de llamar a {\itshape pstops\/} (que debe estar
+instalado) y que es quien junta tres p\'aginas en una, coloc\'andolas en el orden
+apropiado para que al imprimir a doble cara el resultado sea tres p\'aginas por
+cara, y de modo que al doblar en tres quede en el orden correcto de
+lectura. Puesto que {\itshape pstops\/} funciona sobre ficheros postscript (.ps), el
+documento original debe ser procesado con {\itshape dvips\/} (no sirve usar
+{\itshape pdflatex\/}).
+
+
+
+
+\subsubsection{Puedo preparar un p\'oster con \TeX{}/\LaTeX{}?
+ \label{posters}
+ }
+
+Por una parte existe un paquete llamado {\itshape a0poster\/}
+({\ttfamily CTAN:macros/latex/contrib/supported/a0poster}) y por otra existe
+una alternativa basada en un programa C llamado {\itshape poster\/}
+({\ttfamily CTAN:support/poster}). Este \'ultimo distribuye el texto en p\'aginas
+A4 que pueden unirse para hacer un p\'oster grande.
+
+
+
+
+\subsubsection{Puedo hacer libretos y car\'atulas de CD con \LaTeX{}?
+ }
+
+S\'\i{}, con el paquete {\itshape cd-cover\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/cd-cover}. Eso s\'\i{}, a la hora de imprimir
+hay que decirlo que lo haga en apaisado.
+
+
+
+
+\subsection{C\'omo puedo preparar una exposici\'on utilizando \LaTeX{}?
+ }
+
+
+\subsubsection{Haciendo transparencias con \LaTeX{}
+ }
+
+En primer lugar se tiene la clase de documento {\itshape slides\/}, que forma
+parte de \LaTeXe{}.
+Adem\'as, existen varios paquetes preparados para hacer transparencias. Los
+m\'as cl\'asicos son
+\begin{itemize}
+\item {\itshape seminar\/} ({\ttfamily CTAN:macros/latex/contrib/other/seminar})
+\item {\itshape foiltex\/} ({\ttfamily CTAN:macros/latex/contrib/supported/foiltex}).
+\end{itemize}
+
+
+
+\subsubsection{Haciendo una presentaci\'on con \LaTeX{}
+ }
+
+Tambi\'en es posible generar directamente las transparencias en formato
+{\itshape .pdf\/} \ref{formato-pdf} {(Qu\'e es el formato pdf?)} utilizando
+los paquetes {\itshape pdfslide\/}
+({\ttfamily CTAN:macros/latex/contrib/supported/pdfslide}) y {\itshape pdfscreen\/}
+({\ttfamily CTAN:macros/latex/contrib/supported/pdfscreen}), quedando las
+presentaciones preparadas para ser proyectadas desde un ordenador.
+Otra alternativa consiste en utilizar la clase de documento {\itshape foils\/} (parte
+de {\itshape foiltex\/}) y {\itshape pdflatex\/}, utilizando posteriormente el
+postprocesador {\itshape ppower4\/}
+(
+\ifpdf
+\href{http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html}{http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html}
+\else
+\onlynameurl{http://www-sp.iti.informatik.tu-darmstadt.de/software/ppower4/index.html}
+\fi
+)
+para tratar el archivo {\itshape pdf\/} obtenido. Un ejemplo de presentaci\'on
+realizada con este sistema es la de Luis Seidel al EGUTH99, disponible en
+\ifpdf
+\href{ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb}{ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb}
+\else
+\onlynameurl{ftp://tex.unirioja.es/pub/tex/EGUTH99/texweb}
+\fi
+
+
+
+
+
+\paragraph{beamer
+ }
+
+Una opci\'on que se est\'a haciendo muy popular es la clase {\itshape beamer\/},
+disponible en
+\ifpdf
+\href{http://latex-beamer.sourceforge.net/}{http://latex-beamer.sourceforge.net/}
+\else
+\onlynameurl{http://latex-beamer.sourceforge.net/}
+\fi
+. Aparte del propio manual puede
+encontrarse una gu\'\i{}a r\'apida en
+\ifpdf
+\href{http://www.geocities.com/kijoo2000/beamer.html}{http://www.geocities.com/kijoo2000/beamer.html}
+\else
+\onlynameurl{http://www.geocities.com/kijoo2000/beamer.html}
+\fi
+.
+
+Con {\itshape beamer\/} se distribuye otro paquete independiente para la inclusi\'on
+de objetos multimedia en los documentos PDF creados mediante pdftex.
+
+\'Unicamente se requiere en el pre\'ambulo:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{multimedia}
+\end{verbatim}
+\end{tscreen}
+
+y la inclusi\'on (pero no la incrustaci\'on) de ficheros de v\'\i{}deo AVI o QuickTime es
+tan f\'acil como:
+\begin{tscreen}
+\begin{verbatim}
+
+\movie[width=60mm,height=45mm,borderwidth=0.5mm]{Ttulo}}{fichero.avi}\\
+\movie[width=60mm,height=45mm,poster,showcontrols]{}{fichero.mov}\\
+\end{verbatim}
+\end{tscreen}
+
+as\'\i{} como para audio (estos s\'\i{} que pueden ser incrustables):
+\begin{tscreen}
+\begin{verbatim}
+
+\sound[inlinesound,samplingrate=22050,encoding=muLaw,bitspersample=8,
+channels=2,label=misonido]{}{fichero.au}\\
+
+\hyperlinksound[]{misonido}{\includegraphics[width=10mm]{inicio.png}}
+\hyperlinkmute{\includegraphics[width=10mm]{paro.png}}\\
+\end{verbatim}
+\end{tscreen}
+
+
+
+\subsubsection{M\'as informaci\'on sobre presentaciones
+ }
+
+La p\'agina web
+\ifpdf
+\href{http://www.math.uakron.edu/~dpstory/pdf_demos.html}{http://www.math.uakron.edu/\~{}dpstory/pdf\_demos.html}
+\else
+\onlynameurl{http://www.math.uakron.edu/\~{}dpstory/pdf\_demos.html}
+\fi
+
+enumera una serie de macros de \LaTeX{} y otros programas utilizados para
+hacer presentaciones tipo PowerPoint.
+
+
+Otra fuente de informaci\'on acerca de las posibilidades de presentaciones
+basadas en \TeX{} y {\itshape PDF\/}, es la p\'agina
+\ifpdf
+\href{http://www.cds.caltech.edu/caltex/2000/}{http://www.cds.caltech.edu/caltex/2000/}
+\else
+\onlynameurl{http://www.cds.caltech.edu/caltex/2000/}
+\fi
+
+de Ross Moore, que incluye fuentes de documentos, ejemplos,enlaces,...
+
+Otra interesante p\'agina es
+\ifpdf
+\href{http://www.miwie.org/presentations/}{http://www.miwie.org/presentations/}
+\else
+\onlynameurl{http://www.miwie.org/presentations/}
+\fi
+, de Michael
+Wiedmann, que contiene una enumeraci\'on de distintos sistemas y se ejemplos
+de cada uno. No s\'olo cubre la presentaci\'on en PDF, sino tambi\'en en HTML y
+otros formatos. Para cada soluci\'on, muestra un ejemplo, pros y contras.
+
+Para presentaciones en p\'oster v\'ease la secci\'on
+\ref{posters} {(p\'osters)}.
+
+
+
+
+\subsection{Algunas cosas que a veces se piden para mandar un documento a la imprenta.}
+
+La forma en que se debe mandar un documento a la imprenta no es \'unica, sino que depende del tipo de
+proceso de impresi\'on por el que vaya a pasar el documento. En
+buena parte de los casos debiera bastar con enviar un archivo
+postscript normal con el documento. Sin embargo, a veces se pide
+el documento con caracter\'\i{}sticas especiales como las que a
+continuaci\'on se tratan,
+
+
+
+
+\subsubsection{Sacando la imagen especular de un archivo (es decir, con todo al rev\'es).}
+
+
+Con \LaTeX{} puede hacerse utilizando el paquete {\itshape crop\/}, en la forma
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[mirror]{crop}
+\end{verbatim}
+\end{tscreen}
+
+La reflexi\'on especular se puede hacer directamente en el
+postscript, en las tres formas siguientes (si se tiene una
+distribuci\'on completa y actual como te\TeX{})
+\begin{tscreen}
+\begin{verbatim}
+dvips <archivo dvi> -h mirr.hd
+dvips <archivo dvi> -Pmirr
+dvips <archivo dvi> -Pmirrorprint
+\end{verbatim}
+\end{tscreen}
+
+Realmente las dos primeras son la misma, pero llamadas de distinta forma
+({\ttfamily config.mirr} llama a {\ttfamily mirr.hd}). {\itshape crop\/} y
+{\ttfamily mirr.hd} est\'an disponible en muchas distribuciones y
+adem\'as pueden encontrarse en
+{\ttfamily CTAN:macros/latex/contrib/supported/crop/} y
+{\ttfamily CTAN:macros/generic/TeX-PS/mirr.hd}
+
+
+
+
+\subsubsection{Sacando el archivo en negativo (es decir, blanco sobre negro).}
+
+Para sacar el archivo en negativo puede utilizarse el paquete crop, carg\'andolo
+como
+\begin{tscreen}
+\begin{verbatim}
+\usepackage[invert]{crop}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsubsection{Marcas de corte.}
+
+Para hacer los cortes, o marcas de corte (las l\'\i{}neas que se\~nalan por donde
+deber\'a cortar la guillotina) puede utilizarse el paquete {\itshape crop\/} al que se
+acaba de hacer referencia. Dentro de las {\itshape midnight macros\/} (disponibles en
+{\ttfamily CTAN:macros/generic/midnight} se puede utilizar {\itshape quire\/} que tambi\'en
+permite hacer marcas de corte.
+
+
+
+
+\subsection{Algunas cuestiones adicionales, o menos FAQ}
+
+\begin{description}
+\item[C\'omo evito que se pegue el texto despu\'es de una orden?] \mbox{}
+
+Es decir, como evitar que si se escribe algo como {\ttfamily $\backslash$LaTeX es ...}
+aparezca como {\ttfamily LaTeXes ...} con el texto pegado. Para ello hay varias
+formas, algunas m\'as elegantes que otras. Las m\'as sencillas son escribirlo bien
+como {\ttfamily $\backslash$LaTeX$\{$$\}$ es ...} o como {\ttfamily $\backslash$LaTeX$\backslash$ es ...}. Sin embargo esto
+no resulta demasiado elegante, aunque es inevitable cuando se utiliza con
+\'ordenes predefinidas. Cuando estas \'ordenes est\'an definidas por el autor del
+documento, resulta muy c\'omodo utilizar el paquete {\itshape xspace\/}, parte de las
+herramientas b\'asicas de \LaTeXe{}. La forma de uso es simple, debe incluirse en
+el pre\'ambulo del documento la llamada al paquete, {\ttfamily $\backslash$usepackage$\{$xspace$\}$}
+y al definir la orden se hace como
+\begin{tscreen}
+\begin{verbatim}
+\newcommand{\mycommand}{palabra\xspace}
+
+\end{verbatim}
+\end{tscreen}
+
+De este modo cualquier llamada a {\ttfamily $\backslash$mycommand} incluir\'a el espacio en
+blanco si es necesario, y no lo har\'a si no es necesario.
+
+
+
+
+
+\item[Es posible poner en el margen derecho o izquierdo una im\'agen?] \mbox{}
+
+Para colocar una figura en el margen:
+\begin{tscreen}
+\begin{verbatim}
+\marginpar{\includegraphics{icono}}
+
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+
+\item[Puedo hacer referencias cruzadas a notas a pie de p\'agina, incluso desde otras notas a pie de p\'agina?] \mbox{}
+
+Perfectamente, con {\ttfamily $\backslash$label} puesto dentro de la nota al pie
+{\ttfamily ($\backslash$footnote$\{$$\backslash$label$\{$f1$\}$Texto$\}$} y {\ttfamily $\backslash$ref} puesto en su lugar
+({\ttfamily $\backslash$footnote}$\{$Esta nota hace referencia a la nota {\ttfamily $\backslash$ref$\{$f1$\}$} de
+la p\'agina {\ttfamily $\backslash$pageref$\{$f1$\}$$\}$)}. Mediante {\ttfamily $\backslash$label} se establece la
+referencia al \'ultimo contador incrementado, en este caso el de las notas al
+pie.
+
+Naturalmente, hasta que no est\'e la segunda nota, con su {\ttfamily $\backslash$label}
+correspondiente, el {\ttfamily $\backslash$ref} que se ha puesto en la primera no tendr\'a
+valor asignado, y al componer el texto parcial, en lugar del n\'umero de la nota
+aparecer\'an los t\'\i{}picos s\'\i{}mbolos de interrogaci\'on de cerrar.
+
+
+
+
+
+\item[Puedo acumular las notas a pie de p\'agina al final del cap\'\i{}tulo?] \mbox{}
+
+S\'\i{}, utilizando el paquete {\itshape endnotes\/}.
+
+
+
+
+
+\item[C\'omo conseguir que la llamada a la nota de pie de p\'agina no sea un n\'umero, sino una letra?] \mbox{}
+
+Por ejemplo con
+\begin{tscreen}
+\begin{verbatim}
+\renewcommand{\thefootnote}{\itshape\alph{footnote}}
+
+\end{verbatim}
+\end{tscreen}
+
+(Las llamadas con letras deben ser con cursiva, y se suelen reservar para
+cuadros y similares.)
+
+
+
+
+
+\item[Puedo escribir notas a pie de p\'agina en el margen?] \mbox{}
+
+\begin{tscreen}
+\begin{verbatim}
+\marginpar{\footnotemark}\footnotetext{Texto de la nota}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+
+\item[Puedo escribir notas a pie de p\'agina en los t\'\i{}tulos de secci\'on?] \mbox{}
+
+S\'\i{}, pero {\ttfamily $\backslash$footnote} debe ser protegido como
+{\ttfamily $\backslash$protect$\backslash$footnote}. \'Esto tiene un problema adicional, saldr\'a el
+s\'\i{}mbolo de la nota a pie de p\'agina en la tabla de materias. El paquete
+{\itshape footmisc\/} con la opci\'on {\ttfamily stable} permite hacerlo de una forma m\'as
+adecuada.
+
+
+
+\item[Puedo tener m\'as control sobre la posici\'on de las notas a pie de p\'agina?] \mbox{}
+
+El paquete {\itshape yafoot\/} permite un mayor control soble las notas a pie de
+p\'agina, mediante tres ficheros de estilo, {\ttfamily pfnote.sty} para confinar las
+notas a pie en una p\'agina, {\ttfamily fnopos.sty} para controlar su posici\'on y
+{\ttfamily dblfnote} para hacerlas a doble columna.
+
+
+
+
+
+\item[C\'omo saco un listado bonito de un programa en un documento \LaTeX{}?] \mbox{}
+
+M\'as bonito que utilizar verbatim queda con cualquiera de los paquetes
+{\itshape listings\/}, {\itshape lgrind\/} o {\itshape fancyvrb\/}
+
+
+
+
+
+\item[C\'omo colorear texto en \LaTeX{}?] \mbox{}
+
+Algunos ejemplillos para empezar a colorear texto
+\begin{tscreen}
+\begin{verbatim}
+...
+\usepackage{color}
+...
+\begin{document}
+...
+\textcolor[rgb]{1,0,0}{soy un texto que quedara en color rojo}
+\textcolor[rgb]{1,1,0}{yo soy un texto en amarillo}
+\textcolor[rgb]{0,0,1}{hola, soy azul}
+\textcolor[rgb]{0,1,1}{soy azul celeste}
+\textcolor[rgb]{1,0,1}{yo soy rosa}
+\textcolor[rgb]{0,1,0}{yo verde claro}
+\textcolor[rgb]{0.5,0,0}{marron}
+\textcolor[rgb]{0,0.5,0.5}{azul verdoso}
+\textcolor[rgb]{1,1,1}{soy blanco}
+\end{verbatim}
+\end{tscreen}
+
+etc, etc, etc...
+
+{\ttfamily rgb} significa {\itshape red\/} {\itshape green\/} {\itshape blue\/} y corresponde a una forma de
+especificar el color. El numero entre corchetes indica cu\'anto
+(R)ed, (G)reen, y (B)lue corresponde al color del texto.
+Existen otras maneras m\'as complicadas pero \'esta est\'a bien para empezar.
+
+
+
+\item[C\'omo colorear celdas en \LaTeX{}?] \mbox{}
+
+Utilizando el paquete {\itshape colortbl\/} (junto con el paquete {\itshape graphicx\/})
+Algo como
+\begin{tscreen}
+\begin{verbatim}
+\multicolumn{1}{>{\columncolor[gray]{0.8}}c}{text}
+\end{verbatim}
+\end{tscreen}
+
+debe colorear una celda.
+
+
+
+
+
+\item[C\'omo centrar elementos m\'as grandes que el ancho de l\'\i{}nea?] \mbox{}
+
+Por ejemplo, para una figura puede hacerse de la forma siguiente:
+\begin{tscreen}
+\begin{verbatim}
+\begin{center}
+ \makebox[0cm][c]{\includegraphics{tufigura.eps}}
+\end{center}
+\end{verbatim}
+\end{tscreen}
+
+o en general,
+\begin{tscreen}
+\begin{verbatim}
+\begin{center}
+ \makebox[0cm][c]{
+ Material tabular, o cualquier otra cosa.
+ }
+\end{center}
+\end{verbatim}
+\end{tscreen}
+
+Si se desea usar el entorno {\itshape table\/}, para poder poner el correspondiente
+{\ttfamily $\backslash$caption}, la cosa se complica un poco ya que {\ttfamily $\backslash$makebox} no
+admite un entorno flotante como {\itshape table\/} en su interior:
+\begin{tscreen}
+\begin{verbatim}
+\begin{center}
+ \begin{table}
+ \centering\makebox[0cm[c]{
+ \begin{tabular}{|c|c|}
+ ...... ....
+ \end{tabular}
+ }
+ \caption{Texto}
+ \end{table}
+\end{center}
+\end{verbatim}
+\end{tscreen}
+
+Tambi\'en puede colocarse un pie dentro del {\ttfamily $\backslash$makebox}, pero se necesita un
+poco m\'as de trabajo (V\'ease "Puedo poner un pie en tablas y figuras que no flotan?")
+
+
+
+
+
+\item[C\'omo obtener el tama\~no de una tabla?] \mbox{}
+
+Una posibilidad consiste en fabricar la tabla dentro de un {\ttfamily savebox} con el
+entorno {\ttfamily lrbox} y luego medirlo con {\ttfamily $\backslash$widthof}, etc. del paquete
+{\itshape calc\/}. Si se usa {\itshape longtable\/}, este procedimiento no funciona, ya que se
+extiende por varias p\'aginas. Sin embargo {\itshape longtable\/} precisamente escribe
+la longitud de cada fila de la tabla en el fichero {\ttfamily .aux}, por lo que se
+podr\'\i{}a recuperar desde all\'\i{}. En concreto, {\itshape longtable\/} escribe la definici\'on
+de una macro {\ttfamily $\backslash$LT@$<$num$>$}, donde {\ttfamily $<$num$>$} es un n\'umero de
+orden correlativo de cada entorno {\itshape longtable\/} (en romano y en min\'usculas)
+que contiene las longitudes de cada columna.
+
+
+
+
+
+\item[C\'omo cambiar el grosor que tienen definido por omisi\'on las l\'\i{}neas que separan las columnas y filas dentro de tablas?] \mbox{}
+
+Por ejemplo con {\ttfamily renewcommand$\{$$\backslash$arrayrulewidth$\}$$\{$1.1pt$\}$}
+
+
+
+
+
+\item[Puedo hacer que una celda de una tabla est\'e dividida en dos por una
+diagonal?] \mbox{}
+
+Puede utilizarse el paquete {\itshape slashbox\/}, disponible en
+{\ttfamily CTAN:macros/latex/contrib/other/slashbox}
+
+
+
+
+
+
+
+\item[C\'omo a\~nadir al texto el n\'umero de p\'agina actual?] \mbox{}
+
+En principio, podr\'\i{}a pensarse que bastar\'\i{}a con usar la orden
+{\ttfamily $\backslash$thepage}. Sin embargo, debido a c\'omo \TeX{} va componiendo los
+p\'arrafos el resultado puede ser incorrecto, ya que primero ejecuta todas las
+macros seg\'un va componiendo el p\'arrafo y hasta que no est\'a terminado no decide
+en que p\'agina van sus l\'\i{}neas. Si el p\'arrafo ocupa dos p\'aginas, es muy probable
+que la p\'agina sea incorrecta.
+
+
+Para sincronizar correctamente la p\'agina con su n\'umero hay que usar alg\'un
+mecanismo que s\'\i{} permita conocer la p\'agina correcta, como el de las
+referencias con {\ttfamily $\backslash$label} y {\ttfamily $\backslash$pageref}. El siguiente c\'odigo es
+una modificaci\'on de uno incluido en el {\itshape \LaTeX{} Companion\/}:
+\begin{tscreen}
+\begin{verbatim}
+\usepackage{ifthen}
+\newcounter{pl}
+\newcommand\pcheck{%
+ \stepcounter{pl}%
+ \label{pl-\thepl}%
+ \ifthenelse{\isodd{\pageref{pl-\thepl}}}{impar}{par}}
+\begin{document}
+Esta pgina es \pcheck. \newpage
+Esta pgina es \pcheck.
+\end{document}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+
+\item[C\'omo saber el n\'umero de p\'aginas de un documento para utilizarlo en el mismo?] \mbox{}
+
+El paquete {\itshape lastpage\/} lo resuelve de forma adecuada (necesitar\'a un par de
+compilaciones). Mediante su uso pueden construirse expresiones del tipo p\'agina
+1 de 10 (con p\'agina {\ttfamily $\backslash$thepage$\{$$\}$} de {\ttfamily $\backslash$pageref$\{$LastPage$\}$}).
+
+
+
+
+
+\item[C\'omo evitar que una {\ttfamily url} muy larga se me desborde por la derecha?] \mbox{}
+
+Utilizando el paquete {\itshape url\/}. Est\'a pensado precisamente para eso, para
+dividir los {\ttfamily url}s por puntos adecuados que no afecten a su legibilidad,
+como por ejemplo en las barras separadoras de directorio.
+
+
+
+
+
+\item[Como se escribe parte de un texto a 2 columnas?] \mbox{}
+
+Por ejemplo, utilizando el paquete {\itshape multicol\/}.
+
+
+
+
+
+\item[Como hacer que la clase report comience \'\i{}ndice y cap\'\i{}tulos en p\'aginas impares?] \mbox{}
+
+Con la opci\'on {\ttfamily openright}. Por ejemplo
+\begin{tscreen}
+\begin{verbatim}
+\documentclass[12pt,a4paper,openright]{report}
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+
+\item[C\'omo hacer buen postscript o pdf?] \mbox{}
+
+Puede utilizarse {\itshape testflow\/}. Es un paquete de diagn\'osticos que da bastante
+informaci\'on \'util para producir buen postscript y/o pdf en un sistema
+\TeX{}. Se encuentra disponible en
+{\ttfamily CTAN::/macros/latex/contrib/supported/IEEEtran/testflow}
+
+\end{description}
+
+
+
+
+
+\subsection{He encontrado un error en \LaTeX{} C\'omo lo notifico?
+ }
+
+Para notificar errores o problemas se escribe {\ttfamily latex latexbug} y se env\'\i{}a
+el informe as\'\i{} generado a {\ttfamily latex-bugs \_AT\_ rus.uni-stuttgart.de}. Se
+recomienda previamente leerse las distintas FAQ y pedir ayuda en los
+distintos foros acerca del problema, y s\'olo entonces, cuando se est\'e seguro
+que el problema es de \LaTeXe{} mandar el informe de error.
+
+
+
+
+\section{Por qu\'e no consigo ...?}
+
+
+\subsection{Por qu\'e no salen las im\'agenes en mi documento?
+ }
+
+La misi\'on de TeX/LaTeX no es entender de gr\'aficos. As\'\i{} que cuando se
+encuentra con uno, este simplemente deja el hueco apropiado, da una
+indicaci\'on del gr\'afico que hay que insertar (usando un comando
+{\ttfamily $\backslash$special}) y continua procesando el documento.
+
+No todos los conversores soportan todos los formatos gr\'aficos, en el caso de
+un formato incompatible, el conversor deja el hueco y no representa el
+gr\'afico. Es conocido que los visualizadores de {\itshape DVI\/} en pantalla no
+suelen representar bien todos los gr\'aficos {\itshape PS\/}.
+
+Para solucionar esto, use otro conversor que si soporte dichos gr\'aficos (por
+ejemplo use dvips y visualice con gs)
+
+V\'eanse
+\ref{special} {(Qu\'e son los $\backslash$special?)},
+\ref{conversores} {(Qu\'e es un conversor (driver)?)},
+\ref{tex-dibujos} {(Introduciendo figuras en \LaTeX{})}
+para m\'as informaci\'on.
+
+
+
+
+\subsection{Por qu\'e no salen los caracteres acentuados si yo los escribo bien?
+ }
+
+En primer lugar debe echarse un vistazo a secci\'on \ref{acentos} {(c\'omo puedo escribir los acentos y dem\'as caracteres extendidos?)}.
+
+Cuando la entrada de caracteres mediante {\ttfamily inputenc} no funciona,
+especialmente en un sistema {\itshape Linux\/}, suele ser debido a que por omisi\'on
+en algunos sistemas {\itshape Linux\/}, el fichero se guarda como {\ttfamily utf-8}, por lo
+que deben seguirse las instrucciones para {\ttfamily utf-8} que all\'\i{} se
+detallan. Un s\'\i{}ntoma habitual es que saque {\ttfamily \`a} y otros caracteres
+acentuados como {\ttfamily A} con {\ttfamily \~{}} seguida de otro caracter extra\~no.
+
+Otras posibilidades ser\'\i{}an cambiar la codificaci\'on del fichero con una
+herramienta como {\itshape recode\/} o {\itshape iconv\/} antes de procesarlo con \LaTeX{} o,
+si se guarda por omisi\'on como {\ttfamily utf-8}, decirle expl\'\i{}citamente si es
+posible, al editor, la codificaci\'on en debe leer y guardar el fichero en
+cuesti\'on. Por ejemplo, para {\itshape $\{$x$\}$emacs\/}, una primera l\'\i{}nea con
+{\ttfamily \% -*- coding: iso-8859-1 -*-} har\'\i{}a que el fichero se leyera y guardara
+siempre como {\ttfamily latin1}. Para otros editores debe consultarse la
+documentaci\'on para saber si es posible y c\'omo.
+
+
+
+
+\subsection{Por qu\'e no encuentro el archivo babelbst.tex cuando uso {\itshape custom-bib\/}?}
+
+La intenci\'on del autor del paquete era que las lenguas de {\itshape babel\/}
+proporcionaran ese archivo, de ah\'\i{} su nombre. Sin embargo, en la pr\'actica
+pocas lenguas lo proporcionan, aunque entre ellas est\'a spanish. El archivo
+{\itshape esbst.tex\/} fue pensado para que se pueda utilizar como el
+{\itshape babelbst.tex\/} que esperan los estilos creados
+(V\'ease \ref{custombib} {(BibTeX en castellano, custom-bib)}).
+
+
+
+
+\subsection{Por qu\'e a veces no me da el mismo resultado o incluso errores al procesar un documento en dos sistemas distintos?}
+
+O dicho con otras palabras, no se supone que una de las bondades de \LaTeX{}
+es que el fuente es portable al igual que el dvi?
+
+La respuesta es que lo anterior es cierto, pero con matices. Lo que es
+portable y universal es el lenguaje \TeX{}. Sus comandos {\itshape primitivos\/} (los
+que \TeX{} tiene definidos intr\'\i{}nsecamente) son utilizables en cualquier
+m\'aquina. No obstante, como escribir documentos a base de {\itshape primitivas\/} puede
+resultar extremadamente engorroso, \LaTeX{} define otro conjunto de comandos
+m\'as amigable, para las tareas m\'as habituales. Algunos de \'estos est\'an en el
+cuerpo de \LaTeX{} y otros en paquetes adicionales
+-- v\'ease \ref{paquetes-latex} {(paquetes en \LaTeX{})}.
+
+De este modo, para que un documento sea portable y universal, no basta con que
+\TeX{} est\'e instalado en ambas m\'aquinas. Debe tenerse adem\'as el conjunto de
+macros \LaTeX{} (y a ser posible en la misma versi\'on), y el conjunto de todos
+los paquetes que el documento use (tambi\'en a ser posible en la misma
+versi\'on). Si las versiones no coinciden pueden producirse efectos secundarios
+indeseados, aunque esto, por suerte, no es muy frecuente, pues salvo algunas
+excepciones ({\itshape babel\/}, la m\'as notable) los paquetes intentan mantener la
+"compatibilidad hacia atr\'as" (es decir, que las nuevas versiones se comporten
+de la misma forma que lo hac\'\i{}an las antiguas).
+
+
+
+
+\section{Preguntas que se van quedando obsoletas}
+
+
+\subsection{Qu\'e es {\ttfamily FTC}?}
+
+{\ttfamily FTC} es un filtro que genera las particiones para el
+castellano. Adem\'as, simplifica enormemente la introducci\'on
+de acentos. Est\'a descrito en:
+\begin{tscreen}
+\begin{verbatim}
+@ARTICLE(pepe:wds
+ ,AUTHOR= "Jos{\'e} A. Ma{\~n}as"
+ ,TITLE= "{Word Division in Spanish}"
+ ,JOURNAL= "Comm. ACM"
+ ,YEAR= 1987
+ ,volume= 30
+ ,number= 7
+ ,pages= "612--616"
+ ,month= "July"
+)
+\end{verbatim}
+\end{tscreen}
+
+Puede conseguirse en:
+\begin{tscreen}
+\ifpdf
+\href{ftp://ftp.dit.upm.es/pub/pepe/ftc}{ftp://ftp.dit.upm.es/pub/pepe/ftc}
+\else
+\onlynameurl{ftp://ftp.dit.upm.es/pub/pepe/ftc}
+\fi
+\end{tscreen}
+
+
+
+
+
+\subsection{Qu\'e es ML-\TeX{}?}
+
+
+ML-\TeX{} es un conjunto de parches para el WEB de \TeX{} (hubo tambi\'en versiones
+para \TeX{} 2.X) que permiten manejar realmente 256 caracteres
+internamente y, mediante el primitivo {\ttfamily $\backslash$charsubdef},
+reconstruir esos caracteres mediante combinaciones de otros. Knuth
+copi\'o masivamente de ML-\TeX{} para el \TeX{} 3.X y {\ttfamily spanish.sty} usa
+ideas sacadas de ah\'\i{}. ML-\TeX{} es la mejor soluci\'on, si no se dispone
+de fuentes extendidas. \TeX{} 3.X incorpora muchas de las ideas de
+Ferguson, pero no todas. Los parches para ML-\TeX{} con \TeX{} 3.0 son
+mucho m\'as peque\~nos que los antiguos.
+
+Si somos usuarios de DOS, {\itshape em\TeX{}\/} incorpora ya ML-\TeX{} sin m\'as que usar
+{\ttfamily -ml} en la l\'\i{}nea de comando al crear el formato.
+
+Si somos usuarios de UNIX, es muy posible que tengamos compilador de C (al menos
+GCC) y podemos aplicar los cambios nosotros mismos con el {\itshape web2c\/}
+de Karl Berry.
+
+
+
+
+\section{Informaci\'on sobre \LaTeX{} en castellano}
+
+
+\subsection{El Grupo de Usuarios de \TeX{} Hispanohablantes (Cervan\TeX{})}
+
+
+\subsubsection{Qu\'e es Cervan\TeX{}?}
+
+Cervan\TeX{} es el grupo de usuarios de \TeX{} hispanohablantes, y forma parte de
+los grupos locales asociados al {\itshape \TeX{} User Group\/}.
+
+La asociaci\'on Cervan\TeX{} busca intercambiar experiencias sobre \TeX{} y sobre
+sus aplicaciones, y promoverlo de forma adecuada en el \'ambito hispanohablante.
+
+Estos fines se desarrollan mediante la discusi\'on y la colaboraci\'on en el
+desarrollo de aplicaciones de \TeX{} y programas asociados; la promoci\'on y el
+fomento de publicaciones relacionadas con \TeX{}; la organizaci\'on de cursos,
+congresos y seminarios; y la colaboraci\'on e intercambio con todo tipo de
+sociedades, instituciones y editoriales cient\'\i{}ficas.
+
+
+
+
+\subsubsection{C\'omo puedo entrar en contacto con el grupo de usuarios?}
+
+
+En este momento la Junta Directiva de {\itshape Cervan\TeX{}\/} est\'a formada por
+\begin{tscreen}
+\begin{verbatim}
+PRESIDENTE: Juan Luis Varona presidente@cervantex.org
+SECRETARIO: Roberto Herrero secretario@cervantex.org
+TESORERO: Enrique Melndez tesorero@cervantex.org
+VOCALES: Luis Sanjun y Javier Bezos
+\end{verbatim}
+\end{tscreen}
+
+La p\'agina WWW del grupo Cervan\TeX{} se encuentra en:
+\begin{quotation}
+\ifpdf
+\href{http://www.cervantex.org}{http://www.cervantex.org}
+\else
+\onlynameurl{http://www.cervantex.org}
+\fi
+\end{quotation}
+
+con informaci\'on m\'as espec\'\i{}fica sobre las actividades del grupo en
+\begin{quotation}
+\ifpdf
+\href{http://www.cervantex.org/actividades.php}{http://www.cervantex.org/actividades.php}
+\else
+\onlynameurl{http://www.cervantex.org/actividades.php}
+\fi
+\end{quotation}
+
+La direcci\'on postal del grupo es
+\begin{tscreen}
+\begin{verbatim}
+CervanTeX
+Apartado de correos 60118 AP
+E-28080 Madrid
+Espaa
+\end{verbatim}
+\end{tscreen}
+
+
+
+
+
+\subsection{La lista {\ttfamily es-tex} \label{lista-estex}}
+
+
+
+
+\subsubsection{C\'omo funciona la lista {\ttfamily es-tex}?}
+
+La lista {\ttfamily es-tex} es el foro principal de discusi\'on en este idioma. Se
+trata de una lista cerrada, por lo que es necesario suscribirse a la misma
+para enviar y recibir mensajes. Aunque es independiente del grupo
+Cervan\TeX{}, gran parte de los suscriptores de la lista son miembros del
+grupo y viceversa. Cervan\TeX{} recomienda a todas las personas interesadas
+en \TeX{} en espa\~nol la suscripci\'on a esta lista.
+
+\begin{itemize}
+\item
+Para suscribirse, debe enviarse un mensaje a {\ttfamily LISTSERV@LISTSERV.REDIRIS.ES}
+que tenga en el cuerpo del mismo
+\begin{quotation}
+{\ttfamily subscribe ES-TEX}
+\end{quotation}
+\item Para enviar un mensaje a la lista una vez suscrito:
+\begin{tscreen}
+\begin{verbatim}
+mail ES-TEX@LISTSERV.REDIRIS.ES
+\end{verbatim}
+\end{tscreen}
+\item Es muy recomendable que los principiantes con las Listas de Distribuci\'on
+lean el documento sobre {\itshape Correcto Uso de las Listas de Distribuci\'on\/} que
+se encuentra en:
+\begin{quotation}
+\ifpdf
+\href{http://www.rediris.es/list/list-moral.html}{http://www.rediris.es/list/list-moral.html}
+\else
+\onlynameurl{http://www.rediris.es/list/list-moral.html}
+\fi
+.
+\end{quotation}
+
+y no est\'a de m\'as la lectura del documento {\itshape C\'omo hacer preguntas de manera
+inteligente\/}, disponible en
+\begin{quotation}
+\ifpdf
+\href{http://www.sindominio.net/ayuda/preguntas-inteligentes.html}{http://www.sindominio.net/ayuda/preguntas-inteligentes.html}
+\else
+\onlynameurl{http://www.sindominio.net/ayuda/preguntas-inteligentes.html}
+\fi
+
+\ifpdf
+\href{http://www.catb.org/~esr/faqs/smart-questions.html}{http://www.catb.org/\~{}esr/faqs/smart-questions.html}
+\else
+\onlynameurl{http://www.catb.org/\~{}esr/faqs/smart-questions.html}
+\fi
+.
+
+\end{quotation}
+
+Para darse de baja de la lista {\itshape ES-TEX\/} debe enviarse a
+{\ttfamily LISTSERV@LISTSERV.REDIRIS.ES} un mensaje que contenga en el cuerpo
+\begin{tscreen}
+\begin{verbatim}
+unsubscribe ES-TEX
+\end{verbatim}
+\end{tscreen}
+
+Existen otras muchas opciones, para obtener un listado de las mismas debe
+enviarse a {\ttfamily LISTSERV@LISTSERV.REDIRIS.ES} un mensaje que contenga en el
+cuerpo
+\begin{tscreen}
+\begin{verbatim}
+HELP
+\end{verbatim}
+\end{tscreen}
+
+siendo especialmente interesantes las opciones {\itshape (NO)MAIL\/}, que regula
+si se recibe un mensaje por cada contribuci\'on a {\itshape ES-TEX\/},
+{\itshape (NO)REPRO\/} que regula si se reciben los mensajes enviados por uno
+mismo y {\itshape (NO)ACK\/} que regula si se recibe confirmaci\'on de
+distribuci\'on. Para todas ellas se env\'\i{}a un mensaje que contenga en el
+cuerpo {\ttfamily set ES-TEX opcion}, por ejemplo
+\begin{tscreen}
+\begin{verbatim}
+set ES-TEX ACK
+set ES-TEX NOACK
+\end{verbatim}
+\end{tscreen}
+
+Para obtener informaci\'on sobre el uso de las listas de RedIris tambi\'en
+puede visitarse la p\'agina
+\ifpdf
+\href{http://www.rediris.es/list/utilizacion.es.html}{http://www.rediris.es/list/utilizacion.es.html}
+\else
+\onlynameurl{http://www.rediris.es/list/utilizacion.es.html}
+\fi
+
+o sobre listserv en general (en ingl\'es)
+\ifpdf
+\href{http://www.rediris.es/list/doc/user.html}{http://www.rediris.es/list/doc/user.html}
+\else
+\onlynameurl{http://www.rediris.es/list/doc/user.html}
+\fi
+
+o ver la gu\'\i{}a de referencia (tambi\'en en ingl\'es)
+\ifpdf
+\href{http://www.rediris.es/list/comandos/info-refcard.html}{http://www.rediris.es/list/comandos/info-refcard.html}
+\else
+\onlynameurl{http://www.rediris.es/list/comandos/info-refcard.html}
+\fi
+
+Por favor, NO mandar peticiones de suscripci\'on o des-suscripci\'on a la
+propia lista ({\ttfamily es-tex}).
+
+\end{itemize}
+
+
+
+
+
+\subsubsection{Cuando contesto a alguien de la lista, qui\'en recibe la respuesta? El que mand\'o el mensaje o la lista entera? }
+
+Por omisi\'on, se contesta a la lista entera, salvo que el remitente
+incluya un campo {\ttfamily Reply-To} expl\'\i{}cito.
+
+
+
+
+\subsubsection{Se archiva en alg\'un sitio la lista {\ttfamily es-tex}?
+ }
+
+S\'\i{}, en
+\ifpdf
+\href{ http://listserv.rediris.es/archives/es-tex.html}{ http://listserv.rediris.es/archives/es-tex.html}
+\else
+\onlynameurl{ http://listserv.rediris.es/archives/es-tex.html}
+\fi
+
+
+
+
+
+\subsubsection{Recibo correo de muchas listas. C\'omo puedo filtrar lo que venga de la lista {\ttfamily es-tex}? }
+
+Todo lo que viene de {\ttfamily es-tex} tiene actualmente un campo de la
+forma:
+\begin{tscreen}
+\begin{verbatim}
+Sender: Usuarios hispanohablantes de TeX <ES-TEX@LISTSERV.REDIRIS.ES>
+\end{verbatim}
+\end{tscreen}
+
+Si utilizamos un filtro llamado {\itshape procmail\/} (es software libre),
+podemos poner las siguientes tres l\'\i{}neas en el archivo de
+configuraci\'on {\ttfamily .procmailrc}:
+\begin{tscreen}
+\begin{verbatim}
+:0
+* ^Sender:.*<ES-TEX@LISTSERV.REDIRIS.ES>
+spanish-tex
+\end{verbatim}
+\end{tscreen}
+
+y todo lo que venga de {\itshape es-tex\/} se ir\'a solito al archivo
+{\ttfamily spanish-tex}.
+
+
+Es posible que algunos clientes de correo que permitan filtrado de
+los mensajes a partir de sus cabeceras puedan intentar verificar si
+el campo {\itshape Sender\/} contiene
+{\ttfamily $<$ES-TEX@LISTSERV.REDIRIS.ES$>$} o algo parecido, pero
+eso debe comprobarse en cada caso.
+
+
+
+
+\subsubsection{C\'omo es que hay tanta gente de fuera de Espa\~na en la lista?
+ }
+
+El tema previsto de esta lista era el uso de \TeX{} para la
+producci\'on de documentos en castellano, no para discutir en
+castellano acerca de \TeX{} ni el uso de \TeX{} en Espa\~na. Esto no es
+r\'\i{}gido, pero no pretende ser una lista espa\~nola. No se excluyen
+tampoco discusiones acerca de las otras lenguas espa\~nolas (catal\'an,
+euskera, gallego, ingl\'es, :-) pero gran parte de la audiencia no
+estar\'a interesada.
+
+
+
+
+\subsection{Las listas {\ttfamily spanish-tex} y {\ttfamily sptex}
+ }
+
+{\itshape ATENCI\'ON\/}. Las listas {\itshape spanish-tex\/} y {\itshape sptex\/} est\'an
+obsoletas. En su lugar debe utilizarse la lista {\itshape es-tex\/}.
+V\'ease \ref{lista-estex} {(lista es-tex)}.
+
+
+
+
+\subsubsection{Se archiva en alg\'un sitio la lista {\ttfamily spanish-tex}?
+ }
+
+Antiguamente, en la siguiente direcci\'on se archivaban los mensajes
+de la lista {\ttfamily spanish-tex}
+\begin{quotation}
+\ifpdf
+\href{http://majordomo.eunet.es/listserv/spanish-tex/}{http://majordomo.eunet.es/listserv/spanish-tex/}
+\else
+\onlynameurl{http://majordomo.eunet.es/listserv/spanish-tex/}
+\fi
+\end{quotation}
+
+junto con las instrucciones de acceso a la lista. Sin embargo, hace
+tiempo que no est\'a operativa.
+
+
+
+
+\subsubsection{Se archiva en alg\'un sitio la lista {\ttfamily sptex}?
+ }
+
+S\'\i{}, en
+\ifpdf
+\href{http://www2.cica.es/ListasD/sptex/}{http://www2.cica.es/ListasD/sptex/}
+\else
+\onlynameurl{http://www2.cica.es/ListasD/sptex/}
+\fi
+, al menos temporalmente.
+
+
+
+
+\subsection{El grupo de noticias {\ttfamily es.comp.lenguajes.tex}
+ }
+
+Una fuente de informaci\'on alternativa es el grupo de noticias
+\ifpdf
+\href{es.comp.lenguajes.tex}{es.comp.lenguajes.tex}
+\else
+\onlynameurl{es.comp.lenguajes.tex}
+\fi
+,
+aunque tiene bastante menos tr\'afico que la lista de correo. Este es el
+grupo de noticias principal sobre \TeX{} en espa\~nol.
+
+
+
+
+\subsection{El grupo de noticias {\ttfamily es.eunet.spanish-tex}
+ }
+
+Antes exist\'\i{}a una pasarela ({\itshape gateway\/}) entre la lista y el grupo de
+noticias {\ttfamily es.eunet.spanish-tex}, pero actualmente no
+funciona. Adem\'as este grupo ya no es de acceso general, sino que es
+propio de la red {\ttfamily eunet}.
+
+
+
+
+\section{Meta-preguntas (preguntas sobre esta FAQ):
+ }
+
+
+\subsection{Cu\'al es la historia de esta FAQ?
+ }
+
+La primera versi\'on de esta FAQ se la debemos a Julio S\'anchez que
+recopil\'o preguntas y respuestas a partir de las discusiones habidas en
+la lista {\ttfamily spanish-tex}.
+
+Posteriormente Santiago Vila {\ttfamily (sanvila \_AT\_ unex.es)} se hizo cargo
+de la FAQ, a\~nadiendo m\'as preguntas y pas\'andola a {\itshape texinfo\/}.
+
+M\'as recientemente, Agust\'\i{}n Mart\'\i{}n {\ttfamily (agustin.martin \_AT\_
+hispalinux.es)} se ha hecho cargo de ella en el 99 y la ha pasado a
+SGML, con la misma intenci\'on con la que Santiago la pas\'o a texinfo,
+extraer de forma sencilla versiones en distintos formatos.
+
+Esta lista de preguntas y respuestas est\'a muy verde, y actualmente
+sigue siendo algo ca\'otica. Se ruega algo de {\itshape intolerancia
+activa\/}, es decir, siempre que se vea algo mal, comun\'\i{}quese al
+coordinador de la FAQ. Se aceptan cambios, correcciones (incluso
+ortogr\'aficas o de estilo), adiciones, etc. Ni Julio S\'anchez ni
+Santiago Vila se hacen cargo en este momento de la FAQ, as\'\i{} que por
+favor no le mand\'eis las preguntas a ellos, sino a la persona que en
+este momento se hace cargo de la FAQ.
+
+
+
+
+\subsection{Qui\'en coordina actualmente la FAQ?
+ }
+
+El coordinador actual y a quien deben enviarse las sugerencias acerca
+de esta FAQ es: Agust\'\i{}n Mart\'\i{}n Domingo, {\ttfamily agustin.martin \_AT\_ hispalinux.es}
+
+Se ruega especificar en la cabecera del mensaje FAQ-CervanTeX. Por
+favor, para dudas generales dirigirse a la lista de correo o al foro
+de noticias. Utilizar esta direcci\'on exclusivamente para asuntos
+relacionados con la FAQ.
+
+
+
+
+\subsection{Agradecimientos
+ }
+
+Para hacer esta FAQ se han utilizado, adem\'as de los originales de
+Julio S\'anchez y Santiago Vila las FAQ del grupo de noticias
+{\ttfamily comp.text.tex} y la {\itshape New \TeX{} FAQ\/}, versi\'on de la anterior
+realizada por el grupo de usuarios de \TeX{} del Reino Unido. La
+versi\'on {\itshape html\/} de esta FAQ con un buscador CGI
+(
+\ifpdf
+\href{http://www.tex.ac.uk/cgi-bin/texfaq2html}{http://www.tex.ac.uk/cgi-bin/texfaq2html}
+\else
+\onlynameurl{http://www.tex.ac.uk/cgi-bin/texfaq2html}
+\fi
+) tambi\'en ha sido de
+gran ayuda. Asimismo se han utilizado multitud de mensajes de las
+listas de correo y grupos de noticias relacionados con \TeX{} a cuyos
+autores agradezco sus ideas y contribuciones.
+
+Fernando M. Fournon Gonz\'alez Barcia {\ttfamily (furny \_AT\_ wd.estec.nl)} y
+Jes\'us M. Gonz\'alez Barahona {\ttfamily (jgb \_AT\_ gsyc.inf.uc3m.es)} han
+proporcionado las citas de las publicaciones de la Real Academia y del
+diccionario de Mar\'\i{}a Moliner. La secci\'on acerca de las funciones
+matem\'aticas en castellano se la debemos a Juan Luis Varona
+{\ttfamily (jvarona \_AT\_ dmc.unirioja.es)} y las de postscript y PDF a
+Enrique Melendez Asensio . Adem\'as se han
+tomado muchos elementos (buena parte de las secciones de libros en
+ingl\'es y de ventajas y desventajas de \LaTeX{}) de las p\'agina sobre
+\LaTeX{} de Antonio Gonz\'alez, de la Universidad de Sevilla
+(
+\ifpdf
+\href{http://www.esi.us.es/~gonfer/tex.html}{http://www.esi.us.es/\~{}gonfer/tex.html}
+\else
+\onlynameurl{http://www.esi.us.es/\~{}gonfer/tex.html}
+\fi
+)
+y otros cuantos de la p\'agina de Mart\'\i{}n Pav\'on
+(
+\ifpdf
+\href{http://mate.dm.uba.ar/~mpavon/tex.html}{http://mate.dm.uba.ar/\~{}mpavon/tex.html}
+\else
+\onlynameurl{http://mate.dm.uba.ar/\~{}mpavon/tex.html}
+\fi
+)
+
+
+
+
+\subsection{D\'onde encuentro la versi\'on m\'as reciente de esta FAQ?
+ }
+
+La versi\'on m\'as reciente de esta FAQ est\'a disponible en el directorio
+\begin{quotation}
+\ifpdf
+\href{http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX/}{http://corbu.aq.upm.es/\~{}agmartin/latex/FAQ-CervanTeX/}
+\else
+\onlynameurl{http://corbu.aq.upm.es/\~{}agmartin/latex/FAQ-CervanTeX/}
+\fi
+\end{quotation}
+
+en una amplia variedad de formatos. Se puede acceder a trav\'es de la p\'agina
+\begin{quotation}
+\ifpdf
+\href{http://corbu.aq.upm.es/~agmartin/latex/FAQ-CervanTeX-main.html}{http://corbu.aq.upm.es/\~{}agmartin/latex/FAQ-CervanTeX-main.html}
+\else
+\onlynameurl{http://corbu.aq.upm.es/\~{}agmartin/latex/FAQ-CervanTeX-main.html}
+\fi
+\end{quotation}
+
+
+
+
+
+\subsection{D\'onde puedo encontrar otras FAQ, aunque sea en otros idiomas?
+ }
+
+Adem\'as de la FAQ en castellano existen FAQ en otros idiomas que, si se
+salva la barrera del lenguaje pueden ser de utilidad adicional. Sin
+duda en ellas existen elementos que podr\'\i{}an entrar bien en esta FAQ,
+as\'\i{} que todo aquel que vea una pregunta de gran inter\'es que est\'a en
+una de ellas y no en la FAQ en castellano est\'a invitado a traducirla y
+envi\'arsela al responsable de esta FAQ. Las FAQ en otros idiomas m\'as
+interesantes son las siguientes
+\begin{itemize}
+\item El grupo de usuarios de \TeX{}/\LaTeX{} del Reino Unido mantiene una
+excelente FAQ en ingl\'es que puede encontrarse en {\itshape CTAN\/} en el
+directorio {\ttfamily CTAN:usergrps/uktug/faq}. La p\'agina web de la
+UK-FAQ
+\ifpdf
+\href{http://www.tex.ac.uk/cgi-bin/texfaq2html}{http://www.tex.ac.uk/cgi-bin/texfaq2html}
+\else
+\onlynameurl{http://www.tex.ac.uk/cgi-bin/texfaq2html}
+\fi
+ tiene adem\'as un
+buscador CGI para facilitar las consultas. Existe una muy
+interesante FAQ visual, es decir, un documento donde aparecen
+destacado ciertos elementos con hiperenlaces a la FAQ
+inglesa. Realmente merece la pena echarle un vistazo. Se encuentra en
+\ifpdf
+\href{http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf}{http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf}
+\else
+\onlynameurl{http://www.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf}
+\fi
+\item Asimismo, el grupo alem\'an {\itshape DANTE\/} de usuarios de \TeX{}/\LaTeX{}
+mantiene su FAQ (en alem\'an) que puede encontrarse en el {\itshape CTAN\/}
+en el directorio {\ttfamily CTAN:help/de-tex-faq}.
+\item Aunque congelada desde hace alg\'un tiempo, existe una FAQ en
+franc\'es en {\ttfamily CTAN:help/LaTeX-FAQ-francaise}
+\end{itemize}
+
+
+\end{document}
diff --git a/help/greek b/help/greek
new file mode 120000
index 0000000000..1182ae1717
--- /dev/null
+++ b/help/greek
@@ -0,0 +1 @@
+../info/greek \ No newline at end of file
diff --git a/help/index.doc b/help/index.doc
new file mode 100644
index 0000000000..c76b74774b
--- /dev/null
+++ b/help/index.doc
@@ -0,0 +1,1505 @@
+% \iffalse
+% ====================================================================
+% @LaTeX-style-file{
+% author = "David M. Jones",
+% version = "3.04",
+% date = "07 March 1994",
+% time = "20:45:05 EST",
+% filename = "index.doc",
+% address = "MIT Laboratory for Computer Science
+% Room NE43-316
+% 545 Technology Square
+% Cambridge, MA 02139
+% USA",
+% telephone = "(617) 253-5936",
+% FAX = "(617) 253-3480",
+% checksum = "27647 1505 7071 54892",
+% email = "dmjones@theory.lcs.mit.edu",
+% codetable = "ISO/ASCII",
+% keywords = "LaTeX, index",
+% supported = "yes",
+% docstring = "This is a reimplementation of LaTeX's
+% indexing macros to provide better support
+% for indexing in LaTeX. For example, it
+% supports multiple indexes in a single
+% document and provides a more robust \index
+% command.
+%
+% The checksum field above contains a CRC-16
+% checksum as the first value, followed by
+% the equivalent of the standard UNIX wc
+% (word count) utility output of lines,
+% words, and characters. This is produced
+% by Robert Solovay's checksum utility.",
+%
+% }
+% ====================================================================
+% \fi
+%
+% \iffalse
+%
+% HOW TO INSTALL THIS FILE:
+%
+% If you have the latest versions of DocStrip and doc.sty installed on
+% your system, type "tex index.doc" to unpack the files index.sty and
+% sample.tex. Then install index.sty wherever style files belong on
+% your system and read the comments at the beginning of sample.tex to
+% see how to run the test. Finally, format the documentation by
+% executing the following three commands:
+%
+% latex index.doc
+% makeindex -s gind.ist index
+% latex index.doc
+%
+% If you don't already have DocStrip and doc.sty installed on your
+% system, you should get them from one of the following sources:
+%
+% ftp.uni-stuttgart.de:soft/tex/macros/latex/distribs/doc
+% pip.shsu.edu:tex-archive/macros/latex/distribs/doc
+% ftp.tex.ac.uk:tex-archive//macros/latex/distribs/doc
+%
+% If for some reason you really can't install the doc package on your
+% system, then you can name this file index.sty and use it as a style
+% file. However, you will likely notice some slowness in loading this
+% file, due to the large number of comments that have to be skipped
+% over.
+%
+% CAUTION: Use only as directed. Do not take internally. May cause
+% rash if applied directly to skin. Federal law prohibits
+% distributing without a proscription.
+%
+% __ __
+% / \ / \
+% / \ / \
+% / \ \ / \ \
+% / ) \ / ) \
+% \ ( / \ ( /
+% \ \ / \ \ /
+% \ / \ /
+% \__/ \__/
+% || ||
+% || ||
+% ------ ------
+%
+% Now the real fun starts. This file is designed to serve 4 (or 5, if
+% you prefer) distinct functions:
+%
+% (1) In the absence of DocStrip, it can be named index.sty and used
+% as a LaTeX style file.
+%
+% (2) It is a DocStrip batch file that can be used to unpack index.sty
+% and sample.tex. This function is triggered when the file is used as
+% an input file for plain TeX, i.e., when the command "tex index.doc"
+% is executed.
+%
+% (3) It is the driver file for the documentation of index.sty. This
+% function is triggered when the file is used as an input file for
+% LaTeX, i.e., when the command "latex index.doc" is executed.
+%
+% (4) It is the source file for steps 2 and 3.
+%
+% To make this work, we have to be able to determine which of these
+% cases we are in and take appropriate action.
+%
+% The next few lines of code accomplish this. First, note that if
+% this file is used as input to the doc.sty \DocInput command, then
+% the \iffalse ... \fi will cause this code to be ignored. Similarly,
+% the <install> guard prevents this code from being copied into any
+% output files by DocStrip.
+%
+% Next comes the more interesting code. We need two auxiliary
+% commands to make sure that the correct commands get executed at the
+% correct time. In order to avoid impinging on the user's namespace,
+% I use two macro names from index.sty.
+%
+% \proofmodetrue: This is a no-op, unless we are producing
+% documentation (i.e., the user has typed "latex index.doc"), in
+% which case it expands to the appropriate initialization code,
+% namely a \documentstyle command, plus \MakePercentIgnore to set
+% things up for doc.sty, and a call to \csname iffalse\endcsname
+% to match the fi that follows. (The earlier iffalse was ignored
+% because when that line was read, % was still a comment character
+% and not an ignored character.)
+%
+% \renewindex: This eats its argument unless this file is being used
+% as a DocStrip batchfile (i.e., the user has typed "tex
+% index.doc"), in which case it simply regurgitates its argument.
+% The commands inside the \renewindex commands are just normal
+% DocStrip batchfile commands.
+%
+% Before doing anything else, we check to make sure that \newindex is
+% not already defined. If it is, that means this file has already
+% been loaded once as a style file (or else someone else has already
+% defined a \newindex command), which means we should not load the
+% file a second time. (This is the same test that will be used later
+% to determine whether or not index.sty has already been loaded. So,
+% if you are using index.doc as index.sty, this test will actually be
+% made twice, but that should be ok.)
+%
+% Finally, we determine whether we are inside plain TeX or LaTeX by
+% checking to see if \documentstyle is defined. If we are inside
+% LaTeX, we check to see if we are being used as a style file or a
+% documentation file by checking to see if the \catcode of @ is 11
+% (letter) or not.
+%
+% The braces around the first two blocks of code below are necessary
+% because DocStrip will open this file and start reading it
+% line-by-line. The braces ensure that the entire \ifx ... \fi
+% structures are picked up at once.
+%
+% No doubt strange and terrible things will happen if you feed this
+% file to any dialect of TeX other than plain TeX or LaTeX.
+%
+% The blame for much of the following code goes to David Wald
+% <wald@theory.lcs.mit.edu>, who forced me to adopt this approach
+% after I had already come up with a safer alternative that was almost
+% as easy to unpack. If anything goes wrong, it's his fault.
+%
+% \fi
+%
+% \iffalse
+%<*install>
+{\expandafter\ifx\csname newindex\endcsname\relax\else\endinput\fi}
+{
+ \global\let\proofmodetrue\relax
+ \expandafter\ifx\csname documentstyle\endcsname\relax
+ \gdef\renewindex#1{#1}
+ \else
+ \gdef\renewindex#1{}
+ \ifcat a\noexpand @\else
+ \gdef\proofmodetrue{%
+ \documentstyle[doc]{article}\MakePercentIgnore
+ \csname iffalse\endcsname
+ }
+ \fi
+ \fi
+}
+\renewindex{\def\batchfile{index.doc}}
+\renewindex{\input docstrip.tex }
+\renewindex{\generateFile{index.sty}{t}{\from{index.doc}{style}}}
+\renewindex{\generateFile{sample.tex}{t}{\from{index.doc}{sample}}}
+\renewindex{\endinput}
+\proofmodetrue
+%</install>
+% \fi
+
+\def\fileversion{v3.04}
+\def\filedate{7 March 1994}
+\def\docdate {7 March 1994}
+
+%% \CheckSum{760}
+%% \CharacterTable
+%% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
+%% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
+%% Digits \0\1\2\3\4\5\6\7\8\9
+%% Exclamation \! Double quote \" Hash (number) \#
+%% Dollar \$ Percent \% Ampersand \&
+%% Acute accent \' Left paren \( Right paren \)
+%% Asterisk \* Plus \+ Comma \,
+%% Minus \- Point \. Solidus \/
+%% Colon \: Semicolon \; Less than \<
+%% Equals \= Greater than \> Question mark \?
+%% Commercial at \@ Left bracket \[ Backslash \\
+%% Right bracket \] Circumflex \^ Underscore \_
+%% Grave accent \` Left brace \{ Vertical bar \|
+%% Right brace \} Tilde \~}
+%%
+%
+% \DoNotIndex{\!,\/,\?,\@,\^,\_}
+% \DoNotIndex{\@@par,\@M,\@auxout,\@bsphack,\@esphack,\@depth,\@ehc}
+% \DoNotIndex{\@for,\@flushglue,\@gobble,\@gobbletwo,\@height,\@idxitem}
+% \DoNotIndex{\@ifnextchar,\@ifstar,\@ifundefined,\@input,\@latexerr}
+% \DoNotIndex{\@makeschapterhead,\@namedef,\@nameuse,\@nil}
+% \DoNotIndex{\@nobreakfalse,\@restonecolfalse,\@restonecoltrue}
+% \DoNotIndex{\@tempa,\@tempf,\@temptokena,\@themark,\@width}
+% \DoNotIndex{\active,\aindex,\baselineskip,\begin,\begingroup,\box}
+% \DoNotIndex{\c@page,\catcode,\chapter,\char,\chardef,\closeout}
+% \DoNotIndex{\CodelineIndex,\sp,\sb,\label,\leavevmode,\mark}
+% \DoNotIndex{\mark,\newinsert,\newwrite,\newtoks,\xdef}
+% \DoNotIndex{\columnsep,\columnseprule,\columnwidth,\csname,\def}
+% \DoNotIndex{\dimen,\do,\DocInput,\documentstyle,\edef,\else,\em}
+% \DoNotIndex{\EnableCrossrefs,\end,\endcsname,\endgroup,\endinput}
+% \DoNotIndex{\everypar,\expandafter,\fi,\filedate,\fileversion}
+% \DoNotIndex{\footnotesize,\gdef,\global,\glossary,\hangindent}
+% \DoNotIndex{\if@filesw,\if@nobreak,\if@twocolumn,\if@twoside}
+% \DoNotIndex{\hsize,\hskip,\ifhmode,\ifmmode,\ifodd,\ifvmode,\ifx}
+% \DoNotIndex{\immediate,\insert,\item,\jobname,\long}
+% \DoNotIndex{\let,\lineskip,\marginparsep,\marginparwidth,\maxdimen}
+% \DoNotIndex{\makeatletter,\noexpand,\openout,\protect,\rlap}
+% \DoNotIndex{\min,\newpage,\nobreak,\normalbaselineskip}
+% \DoNotIndex{\normallineskip,\p@,\par,\parfillskip,\parindent,\parskip}
+% \DoNotIndex{\penalty,\relax,\section,\sin,\sloppy,\space,\string}
+% \DoNotIndex{\tableofcontents,\the,\thepage,\thispagestyle,\toks,\tt}
+% \DoNotIndex{\twocolumn,\typeout,\uppercase,\vbox,\vrule,\vskip,\vss}
+% \DoNotIndex{\write,\z@,\z@skip}
+%
+% \MakeShortVerb{\=}
+%
+% \setcounter{StandardModuleDepth}{1}
+%
+% \newcommand{\email}[1]{$\langle${\tt#1}$\rangle$}
+%
+% \newcommand{\vdate}[1]{$\langle$#1$\rangle$}
+%
+% \newcommand{\file}[1]{{\tt#1}}
+%
+% \newcommand{\bundle}[1]{{\tt#1}}
+%
+% \newcommand{\program}[1]{{\sf#1}}
+%
+% \newcommand{\Ltag}[1]{{\tt\bslash#1}}
+%
+% \CodelineIndex
+%
+% \title{A new implementation of \LaTeX's indexing
+% commands\thanks{This file has version number \fileversion,
+% last revised \filedate, documentation dated \docdate. The
+% definitive version of this file is
+% \file{theory.lcs.mit.edu:pub/tex/index.doc}.}}
+%
+% \author{David M. Jones}
+%
+% \date{\filedate}
+%
+% \begin{document}
+%
+% \maketitle
+%
+% \section{Introduction}
+%
+% This style file reimplements \LaTeX's indexing macros to provide
+% better and more robust support for indexes. In particular, it
+% provides the following features:
+% \begin{enumerate}
+%
+% \item
+% Support for multiple indexes.
+%
+% \item
+% Indexing of items by counters other than the page number.
+%
+% \item
+% A $*$-variant of the =\index= command that, in addition to putting
+% it's argument in the index, also typesets it in the running text.
+%
+% \item
+% A =\shortindexingon= command that makes =^= and =_= shorthand for
+% =\index= and =\index*=, respectively (but only outside of math mode,
+% of course). This can be turned of with the =\shortindexingoff=
+% command.
+%
+% \item
+% The \bundle{showidx} style option has been merged into this file.
+% The command =\proofmodetrue= can be used to enable the printing of
+% index entries in the margin of pages. The size and style of font
+% can be controlled with the =\indexproofstyle= command.
+%
+% \item
+% A two-stage process, similar to that used to create tables of
+% contents, for creating the raw index files. This means that when
+% processing a portion of a document using the =\includeonly= command,
+% the index entries from the rest of the document are not lost.
+%
+% \item
+% A more robust =\index= command. In particular, it no longer depends
+% on =\catcode= changes to work properly, so the new =\index= command
+% can be used in places that the original couldn't, such as inside the
+% arguments of other macros.
+%
+% \end{enumerate}
+%
+%
+% \section{Creating an index with \LaTeX}
+%
+% Conceptually, there are four stages to creating an index. First,
+% \LaTeX\ must be informed of your intention to include an index in
+% your document. Second, you must add appropriate markup commands to
+% your document to tell \LaTeX\ what to put in the index. Third,
+% after \LaTeX\ has been run on your document, the raw index
+% information must be processed and turned into a form that \LaTeX\
+% can process to typeset the index. Finally, the finished index must
+% be inserted at the appropriate point in your document.
+%
+% In \LaTeX, these steps are accomplished with the commands
+% =\makeindex=, =\index=, =\printindex=, and (typically) with the
+% auxiliary program \program{MakeIndex}. For example, assuming that
+% your main file is called \file{foo.tex}, =\makeindex= opens the
+% file \file{foo.idx} and initializes it for holding the raw index
+% entries, and =\index= is used to add raw index entries into
+% \file{foo.idx}. Then the raw index file is processed by
+% \program{MakeIndex}, which puts the finished index in
+% \file{foo.ind}. Finally, the =\printindex= command is used in
+% your \LaTeX\ document to indicate where the file \file{foo.idx}
+% should be inserted, i.e., where the index should appear in your
+% document.
+%
+% The \bundle{index} package modifies the =\makeindex=, =\index=, and
+% =\printindex= commands, as described below.
+%
+%
+% \section{The user interface}
+%
+% There are four pieces of information associated with each index:
+% \begin{enumerate}
+%
+% \item
+% A short, unique tag that identifies the index.
+%
+% \item
+% The extension of the output file where the raw index information
+% will be put by \LaTeX.
+%
+% \item
+% The extension of the input file where the processed information
+% created by \program{MakeIndex} will be stored to be read in later by
+% \LaTeX.
+%
+% \item
+% The title of the index.
+%
+% \end{enumerate}
+%
+% \DescribeMacro{\newindex}
+% Correspondingly, the =\newindex= command has four required
+% arguments. For example, to declare an author index, you might use
+% the following:
+% \begin{verbatim}
+% \newindex{aut}{adx}{and}{Name Index}\end{verbatim}
+% Here, =aut= is the tag used to identify the author index, and ``Name
+% Index'' is the title of the index. If the name of your main file is
+% \file{root.tex}, then \LaTeX\ will write the raw index entries
+% to the file \file{root.adx}, and you will execute the following
+% \program{MakeIndex} command to process the author index:
+% \begin{verbatim}
+% makeindex -o root.and root.adx\end{verbatim}
+%
+% By default, the =\index= tags its argument with the page number
+% (i.e., the value of =\thepage=), but occasionaly you may want to
+% index items according to a different counter. For example, you may
+% want an index that contains figure numbers instead of page numbers.
+% To accomodate, this, the =\newindex= command takes an optional
+% argument, which is the name of the command that generates the number
+% that should be included in the index. For instance, to include the
+% number of a figure, you might say
+% \begin{verbatim}
+% \newindex[thefigure]{fig}{fdx}{fnd}{Figures}\end{verbatim}
+%
+% However, this introduces a new technicality: When creating an index
+% with page numbers, the choice of which page number is to be written
+% to the =aux= file should be deferred until the page containing the
+% entry is shipped out to the =dvi= file, otherwise the wrong number
+% will sometimes be chosen. However, when using counters other than
+% the page counter, one normally wants the opposite behaviour: the
+% number written to the =aux= file should be chosen immediately,
+% otherwise every item on a given page will be tagged with the number
+% of the last item on that page. So, when a counter is specified
+% using the optional argument of =\newindex=, it is assumed that the
+% counter should be evaluated immediately. If for some reason you
+% need the choice to be deferred until the page is written to the
+% =dvi= file, you can force this behaviour by putting a $*$ {\em
+% after\/} the optional argument:
+% \begin{verbatim}
+% \newindex[thefigure]*{fig}{fdx}{fnd}{Figures}\end{verbatim}
+% (One consequence of this scheme is that if, for some reason, you
+% need the choice of page number to be made immediately instead of
+% being deferred until a page is shipped out to the =dvi= file, you
+% can acomplish this by beginning your index declaration with
+% \begin{verbatim}
+% \newindex[thepage]*\end{verbatim}
+%
+%
+% \DescribeMacro{\renewindex}
+% The =\renewindex= command takes the same arguments as the
+% =\newindex= command and can be used to redefine indexes that have
+% been previously declared.
+%
+%
+% \DescribeMacro{\makeindex}
+% For backwards compatibility, the =\makeindex= command is redefined
+% to use =\newindex=. It is essentially equivalent to
+% \begin{verbatim}
+% \newindex{default}{idx}{ind}{Index}\end{verbatim}
+% The index labeled =default= is special: it is the one that will be
+% used by =\index= and =\printindex= unless another index is
+% specified (see below).
+%
+%
+% \DescribeMacro{\printindex}
+% The =\printindex= command is modified by the addition of an optional
+% argument, which is the tag of the index that should be printed.
+%
+%
+% \DescribeMacro{\index}
+% The =\index= command is modified in two ways. First, there is a
+% $*$-variant of the command that, in addition to putting its argument
+% into an index, also typesets it on the page. Second, =\index= now
+% takes an optional argument to indicate which index the new entry
+% should be added to. If given, the optional argument should be the
+% identifying tag of a previously-defined index. If no such tag is
+% supplied, the =default= index (such as that opened by =\makeindex=
+% above) is used.
+%
+%
+% \DescribeMacro{\shortindexingon}
+% \DescribeMacro{\shortindexingoff}
+% Perhaps the most dubious feature of \bundle{index.sty} is that it
+% allows you to define the characters =^= and =_= to be abbreviations
+% for =\index*= and =\index= outside of math mode. These
+% abbreviations are enabled by the =\shortindexingon= command and
+% disabled by the =\shortindexingoff= command. The scope of both of
+% these latter commands is local to the current group. (This might be
+% useful, for example, if you wanted the abbreviations turned on
+% throughout most of the documentation, but turned off in one
+% particular environment.) In addition,
+% \DescribeEnv{shortindexingon}=shortindexingon= can be used as an
+% environment if that seems appropriate.
+%
+%
+% \DescribeMacro{\proofmodetrue}
+% \DescribeMacro{\proofmodefalse}
+% \DescribeMacro{\indexproofstyle}
+% As mentioned above, the \bundle{showidx} document-style option has
+% been merged into \bundle{index.sty}. It can be turned on with
+% =\proofmodetrue= and turned off with =\proofmodefalse=. When it is
+% turned on, all index entries\footnote{Well, most, at least. There
+% are some circumstances under which the index entries won't show up
+% in the proofs, although they will show up in the index.} will be put
+% in the margin of the page where they appear. By default, they
+% appear in the typewriter font at =\footnotesize=, but the user can
+% override this with the =\indexproofstyle= command; for example,
+% \begin{verbatim}
+% \indexproofstyle{\footnotesize\it}\end{verbatim}
+% will cause them to be put in italics instead.
+%
+%
+% \DescribeMacro{\disableindex}
+% There are some circumstances where it might be helpful to suppress
+% the writing of a particular index. The =\disableindex= command is
+% provided for this purpose. It takes one argument, a comma-separated
+% list of tags of the indexes that should be disabled. This command
+% should come {\em before\/} the declarations for the indexes that are
+% being disabled\footnote{This limits its usefulness somewhat, but
+% since the output file for an index is opened when the index is
+% declared, the damage has already been done. We could close the
+% file, but we can't prevent a new output stream from being allocated
+% and we can't keep the old file from being truncated.}. One
+% situation where the =\disableindex= command might be useful is if
+% there are so many indexes that you are exhausting \TeX's supply of
+% output streams\footnote{\TeX\ only has 16 output streams, which are
+% allocated with the {\tt\string\newwrite} command. The standard
+% \LaTeX\ styles use from 3 to 7 of these, which should leave room for
+% up to 9 indexes. Of course, if you have extra output files, then
+% there will be fewer output streams left for indexes.}. For example,
+% suppose you have 10 indexes, but only 5 output streams available for
+% indexes. Then you could add a =\disableindex= command to the top of
+% your file to suppress the writing of all but 5 of the indexes.
+% (Note that the index entries would still get written to the =aux=
+% file; they just wouldn't get copied to the individual raw index
+% files at the end of the run.) At the end of the run, you could then
+% re-run your main file a couple of times with different indexes
+% disabled until you had created all of the raw index files. This is
+% somewhat clumsy, but safer than any alternative I've come up
+% with\footnote{A less clumsy (for the user, at least) solution would
+% be to read the =aux= file multiple times at the end of the run, each
+% time writing just one of the raw index files. The main disadvantage
+% of this scheme at present is that it would require a modification of
+% {\tt\string\enddocument}.}.
+%
+%
+% \section{Caveats}
+%
+% In order to implement this style file, it's been necessary to modify
+% a number of \LaTeX\ commands seemingly unrelated to indexing,
+% namely, =\@starttoc=, =\raggedbottom=, =\flushbottom=,
+% =\addcontentsline=, =\markboth=, and =\markright=. Naturally, this
+% could cause incompatibilities between \bundle{index.sty} and any
+% style files that either redefine these same commands or make
+% specific assumptions about how they operate. See
+% Section~\ref{sec:thecode} for explanations of why these various
+% commands needed modification.
+%
+% It's also been necessary to modify the =\theindex= environment, but
+% I've tried to do so very conservatively. If your style file uses
+% =\indexname= and your definition of =\theindex= doesn't take any
+% arguments, you should be ok. Otherwise, you'll need to redefine the
+% =\theindex= environment yourself if you don't want the \LaTeX\
+% \bundle{book.sty} default.
+%
+% In the current implementation, \bundle{index.sty} uses one output
+% stream for each index. Since there are a limited number of output
+% indexes, this means that there is a limit on the number of indexes
+% you can have in a document. See the description of =\disableindex=
+% for a fuller discussion of this problem and one way around it.
+%
+%
+% \section{To do's}
+%
+% The entire package should be rewritten as a
+% \LaTeX\kern.15em$2_{\textstyle\varepsilon}$ package.
+%
+% It might be nice if the =\index*= command parsed its argument so
+% that, for example, instead of writing `=\index{sin@$\sin$}$\sin$=',
+% one could write `=\index*{sin@$\sin$}='. However, this is fraught
+% with numerous dangers, and I'm both too lazy and too cowardly to
+% undertake it now.
+%
+% Maybe the user should be given the option of deciding which
+% characters are used for the shortindexing abbreviations
+%
+% It would be reasonable to add support for =\makeglossary= and
+% similar things, if they were well-defined enough to decide what the
+% general syntax for defining them should be.
+%
+% The documentation should be carefully read, edited, and finished.
+% (In particular, I should add some scathing comments about some of
+% the problems that made it necessary to redefine so many of \LaTeX's
+% commands. This wouldn't necessarily do any good, but it would make
+% me feel better.)
+%
+% Maybe it would be nice if this package were compatible with plain
+% \TeX.
+%
+% \StopEventually{}
+%
+% \section{The code}
+% \label{sec:thecode}
+%
+% As is customary, we first make sure the file is loaded only once.
+% Then we print an identifying message to the terminal.
+% \begin{macrocode}
+%<*style>
+\@ifundefined{newindex}{}{\endinput}
+
+\typeout{Style-Option: `index' \fileversion\space <\filedate> (dmj)}
+% \end{macrocode}
+%
+% \begin{macro}{\@ifundefined}
+% We begin by redefining the \LaTeX\ command =\@ifundefined= to
+% prevent it from expanding its arguments prematurely. This also
+% requires us to redefine =\@leftmark= and =\@rightmark= to make them
+% =\long=. The following three definitions are borrowed from
+% \bundle{amsart.sty}, v1.1b \vdate{31 Jul 1991}. I rely heavily upon
+% this more robust definition of =\@ifundefined=.
+% \begin{macrocode}
+\long\def\@ifundefined#1{%
+ \expandafter\ifx\csname#1\endcsname\relax
+ \expandafter\@leftmark
+ \else
+ \expandafter\@rightmark
+ \fi
+}
+
+\long\def\@leftmark#1#2{#1}
+\long\def\@rightmark#1#2{#2}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\disableindex}
+% The =\disableindex= should come before the declarations of the
+% indexes it refers to. (Question: If an index has been disabled,
+% should it show up in index proofs? Maybe there should be a separate
+% command to disable index proofs on and index-by-index basis.)
+% \begin{macrocode}
+\def\disableindex#1{%
+ \@for\@tempa:=#1\do{%
+ \@namedef{disable@\@tempa}{}%
+ \@ifundefined{tf@\@tempa}{}{%
+ \typeout{index.sty> Warning! It's too late to disable the
+ `\@tempa' index; the output}%
+ \typeout{index.sty> file \jobname.\@tempa\space has already
+ been opened for output. You should}%
+ \typeout{index.sty> put the \string\disableindex\space
+ command before the declaration of the}%
+ \typeout{index.sty> `\@tempa' index.}%
+ }%
+ }%
+}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\if@newindex}
+% \begin{macro}{\newindex}
+% \begin{macro}{\renewindex}
+% The =\newindex= and =\renewindex= commands are defined on analogy
+% with the =\[re]newcommand= macros. Each index is identified by a
+% unique tag, which is specified in the first required argument of
+% =\newindex=. Much of the information about the index labeled
+% \meta{tag} is kept in the macro =\idx@=\meta{tag}, so we can check
+% to see if a particular index has already been defined by checking
+% whether =\idx@=\meta{tag} is defined. =\newindex= and =\renewindex=
+% both check to see if their first argument is already associated with
+% an index and then either issue an appropriate error message or call
+% =\def@index=.
+%
+% The =\if@newindex= flag will be used to keep =\renewindex= from
+% re-allocating =\write= and =\toks= registers later.
+% \begin{macrocode}
+\newif\if@newindex
+
+\def\newindex{%
+ \@tempswafalse
+ \@ifnextchar[{\@tempswatrue\x@newindex}{\x@newindex[thepage]}%
+}
+
+\def\x@newindex[#1]{%
+ \@ifstar {\@tempswafalse\y@newindex{#1}}
+ {\y@newindex{#1}}%
+}
+
+\def\y@newindex#1#2{%
+ \@ifundefined{idx@#2}%
+ {\@newindextrue\def@index{#1}{#2}}%
+ {%
+ \@latexerr{Index type `\string#2' already defined}\@ehc
+ \expandafter\@gobble\@gobbletwo
+ }%
+}
+
+\def\renewindex{%
+ \@tempswafalse
+ \@ifnextchar[{\@tempswatrue\x@renewindex}{\x@renewindex[thepage]}%
+}
+
+\def\x@renewindex[#1]{%
+ \@ifstar {\@tempswafalse\y@renewindex{#1}}
+ {\y@renewindex{#1}}%
+}
+
+\def\y@renewindex#1#2{%
+ \@ifundefined{idx@#2}%
+ {%
+ \@newindextrue
+ \@latexerr{Index type `\string#2' not defined}\@ehc
+ }%
+ {\@newindexfalse}%
+ \def@index{#1}{#2}%
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\@preamblecmds}
+% Neither =\newindex=, =\renewindex=, nor =\disableindex= should be
+% used anywhere except inside style files or in the preamble of a
+% document, so we add them to the =\@preamblecmds= list.
+% \begin{macrocode}
+\begingroup
+ \def\do{\noexpand\do\noexpand}%
+ \xdef\@preamblecmds{%
+ \@preamblecmds
+ \do\newindex
+ \do\renewindex
+ \do\disableindex
+ }
+\endgroup
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\def@index}
+% =\def@index= does most of the work. First, it picks up the first
+% three arguments of the =\[re]newindex= command and stores the second
+% two in an appropriate =\idx@= macro. The title of the index is
+% treated differently, however, since it is potentially fragile in a
+% particularly odd way. To prevent mishaps, it is stored in a token
+% register. In addition to stashing away the information about the
+% index, =\def@index= also opens an appropriate output file if we are
+% writing auxiliary files (i.e., unless =\nofiles= is in effect).
+%
+% \begin{macro}{\my@newtoks}
+% Since we need to declare new token registers on the fly, we need a
+% non-=\outer= version of =\newtoks=.
+% \begin{macrocode}
+\def\my@newtoks{\csname newtoks\endcsname}
+
+\def\def@index#1#2#3#4{%
+ \@namedef{idx@#2}{#3:#4:#1}%
+ \expandafter\let\csname if@immediate@#2\endcsname\if@tempswa
+ \if@filesw
+ \if@newindex
+ \expandafter\my@newtoks\csname idxtitle@#2\endcsname
+ \fi
+ \@ifundefined{disable@#2}{%
+ \if@newindex
+ \expandafter\newwrite\csname tf@#2\endcsname
+ \else
+ \immediate\closeout\@nameuse{tf@#2}%
+ \fi
+ \immediate\openout\@nameuse{tf@#2}=\jobname.#3 %
+ \typeout{index.sty> Writing index file \jobname.#3 }%
+ }
+ {\typeout{index.sty> Index `#2' disabled -- not opening
+ \jobname.#3 }}%
+ \fi
+ \expandafter\csname idxtitle@#2\endcsname
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\@second}
+% \begin{macro}{\@third}
+% These are useful macros for retrieving the second and third field of
+% an index specification.
+% \begin{macrocode}
+\def\@second#1:#2:#3\@nil{#2}
+
+\def\@third#1:#2:#3\@nil{#3}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\@nearverbatim}
+% \begin{macro}{\@meaning}
+% =\@nearverbatim\foo= is much like =\meaning\foo=, except that it
+% suppresses the ``=macro ->='' string produced when =\meaning=
+% expands a macro. It is used by =\@wrindex= and =\@vwritefile= to
+% produce an ``almost verbatim'' copy of their arguments. This method
+% replaces the use of =\@sanitize= from latex.tex and allows indexing
+% macros to be used in places (such as inside macro arguments) where
+% the original =\index= command could not. Thanks to Donald Arseneau
+% \email{asnd@erich.triumf.ca} for pointing out this
+% trick to me. (For more information on this trick, see Dirty Trick
+% \#3 of the \TeX book, page 382).
+%
+% As defined, \@nearverbatim only works on macros. It would be nice
+% if it could work with other tokens, but it's more important that it
+% work only by expansion, which means we can't put in tests to see
+% what the next token is.
+% \begin{macrocode}
+\def\@nearverbatim{\expandafter\@meaning\meaning}
+
+\def\@meaning#1>{}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% Now we define the =\index= macro itself. The following definitions
+% are adapted from \bundle{latex.tex} v2.09 \vdate{25 March
+% 1992}.
+%
+% \begin{macro}{\makeindex}
+% First we redefine =\makeindex= to define the default index using
+% =\newindex=. We use =\edef= to make sure that =\indexname= gets
+% expanded here. Otherwise we'll get into an infinite loop later on
+% when we try to redefine =\indexname= inside the =\theindex=
+% environment.
+% \begin{macrocode}
+\edef\makeindex{%
+ \noexpand\newindex{default}{idx}{ind}{%
+ \expandafter\ifx\csname indexname\endcsname\relax
+ Index%
+ \else
+ \indexname
+ \fi
+ }%
+}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\if@silentindex}
+% \begin{macro}{\if@addtoindex}
+% \begin{macro}{\if@proofmode}
+% We need three new flags. The first, =\if@silentindex=, indicates
+% whether the entry should be typeset in running text, as well as
+% written out to the index; this is used to implement the =\index*=
+% command. The second, =\if@addtoindex=, indicates whether entries
+% should be written to the index; this is used to disable the =\index=
+% command inside of page headings and tables of contents. The third,
+% =\ifproofmode=, indicates whether index entries should be put in the
+% margin of the page for proofing purposes.
+% \begin{macrocode}
+\newif\if@silentindex\@silentindextrue
+
+\newif\if@addtoindex\@addtoindextrue
+
+\newif\ifproofmode\proofmodefalse
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\index}
+% \begin{macro}{\p@index}
+% \begin{macro}{\x@index}
+% =\index= will be made self-protecting (a la =\em=, etc.) so it can
+% be used inside, for example, sectioning commands. Unfortunately, to
+% really make =\index= robust, we have to redefine some of \LaTeX's
+% commands for dealing with tables of contents and page headings.
+% (See below.) $*$sigh$*$
+% \begin{macrocode}
+\def\index{\protect\p@index}
+
+\def\p@index{%
+ \if@silentindex\@bsphack\fi
+ \@ifstar{\@silentindexfalse\@xindex}{\@silentindextrue\@xindex}%
+}
+
+\def\@xindex{\@ifnextchar[{\@index}{\@index[default]}}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\@index}
+% \begin{macro}{\@@index}
+% \begin{macro}{\@wrindex}
+% The following is much more complicated than it should have to be.
+% First, note the check to see if =\index= is equal to =\@gobble=.
+% This is so I don't have to redefine =\@outputpage=, which
+% temporarily disables =\label=, =\index=, and =\glossary= by
+% =\let='ing them equal to =\@gobble=. (For this reason, we have to
+% be very careful to make sure that =\index= has expanded to
+% =\p@index= before it gets to =\@outputpage=.) Second, note that if
+% =\if@addtoindex= is false, we don't complain about undefined index
+% types. This is because if your page headings, for example, are
+% being typeset in all uppercase, you might end up with something like
+% =\index[AUT]{...}= instead of =\index[aut]{...}=.
+% \begin{macrocode}
+\def\@index[#1]{%
+ \ifx\index\@gobble
+ \@addtoindexfalse
+ \fi
+ \def\@tempf{\@@index{#1}}%
+ \if@addtoindex
+ \@ifundefined{idx@#1}%
+ {%
+ \def\@tempf{%
+ \@latexerr{Index type `\string#1' undefined}%
+ \@ehc
+ \@silentindextrue
+ \@gobble
+ }%
+ }%
+ {}%
+ \fi
+ \@tempf
+}
+
+\def\@@index#1#2{%
+ \if@addtoindex
+ \if@filesw\@wrindex{#1}{#2}\fi
+ \ifproofmode\@showidx{#2}\fi
+ \fi
+ \if@silentindex\expandafter\@esphack\else\@silentindextrue#2\fi
+}
+
+\def\@wrindex#1#2{%
+ \begingroup
+ \def\@tempa{#2}%
+ \edef\@tempb{\@nameuse{idx@#1}}%
+ \edef\@tempb{\expandafter\@third\@tempb\@nil}%
+ \csname if@immediate@#1\endcsname \else
+ \expandafter\let\csname\@tempb\endcsname\relax
+ \fi
+ \edef\@tempa{%
+ \write\@auxout{%
+ \string\@vwritefile{#1}{%
+ \string\indexentry{\@nearverbatim\@tempa}%
+ {\@nameuse{\@tempb}}%
+ }%
+ }%
+ }%
+ \expandafter\endgroup\@tempa
+ \if@nobreak\ifvmode\nobreak\fi\fi
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\seename}
+% \begin{macro}{\see}
+% \begin{macro}{\printindex}
+% \begin{macro}{\@printindex}
+% The following are adapted from \bundle{makeidx.sty}, v2.09 \vdate{21
+% Oct 91}.
+% \begin{macrocode}
+\@ifundefined{seename}{\def\seename{see}}{}
+
+\def\see#1#2{{\em \seename\/} #1}
+
+\def\printindex{\@ifnextchar[{\@printindex}{\@printindex[default]}}
+
+\def\@printindex[#1]{%
+ \def\@indextype{#1}%
+ \@ifundefined{idx@#1}%
+ {\@latexerr{Index type `\string#1' undefined}\@ehc}%
+ {%
+ \edef\@tempa{\@nameuse{idx@#1}}%
+ \@input{\jobname.\expandafter\@second\@tempa\@nil}%
+ }%
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\@indexstar@}
+% Now we set things up for =\shortindexing=. First, we define a
+% one-token shorthand for =\index*=. This will be needed in the
+% definition of =\idx@activehat=.
+% \begin{macrocode}
+\def\@indexstar@{\index*}
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\idx@activehat}
+% \begin{macro}{\idx@activebar}
+% Next, we define the values that =^= and =_= will have when
+% shortindexing is turned on.
+% \begin{macrocode}
+\def\idx@activehat{%
+ \relax
+ \ifmmode\expandafter\sp\else\expandafter\@indexstar@\fi
+}
+
+\def\idx@activebar{%
+ \relax
+ \ifmmode\expandafter\sb\else\expandafter\index\fi
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% \begin{macro}{\shortindexingon}
+% \begin{macro}{\shortindexingoff}
+% Now we define the =\shortindexingon= and =\shortindexinoff= commands
+% to turn shortindexing on and off (surprise!). =\shortindexingon=
+% saves the old definitions and =\catcode='s of =^= and =_= so they
+% can later be restored by =\shortindexingoff=. Both of these make
+% their changes local to any enclosing group, so they can be used as
+% declarations to disable or enable shortindexing temporarily. In
+% addition, =shortindexingon= can also be used as an environment.
+%
+% This is potentially very confusing. My basic rationale (if it can
+% be described as such) was that under normal circumstances, one would
+% put =\shortindexingon= in the preamble of one's document, and never
+% want to turn it off. =\shortindexingoff= is an attempt to make
+% allowance for the contingency that someone might want to turn
+% shortindexing off, either permanently or temporarily.
+% \begin{macrocode}
+\newif\if@shortindexing
+
+\begingroup
+
+ \catcode`\^=\active
+ \catcode`\_=\active
+
+ \gdef\shortindexingon{%
+ \@shortindexingtrue
+ \chardef\old@idxhatcode=\catcode`\^\relax
+ \chardef\old@idxbarcode=\catcode`\_\relax
+ \catcode`\^=\active
+ \catcode`\_=\active
+ \let\old@idxhat=^%
+ \let\old@idxbar=_%
+ \let^\idx@activehat
+ \let_\idx@activebar
+ }
+
+ \gdef\shortindexingoff{%
+ \if@shortindexing
+ \@shortindexingfalse
+ \let^=\old@idxhat
+ \let_=\old@idxbar
+ \catcode`\^=\old@idxhatcode
+ \catcode`\_=\old@idxbarcode
+ \fi
+ }
+
+\endgroup
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% Now we redefine =\theindex=. We try to make the minimal possible
+% change, but if the user's style doesn't know about =\indexname=, we
+% have no alternative but to redefine the entire environment and issue
+% a warning.
+%
+% Thanks to Alan Jeffrey \email{alanje@cogs.sussex.ac.uk} for
+% pointing out how the package should behave when =\indexname= is
+% already defined and for the code to implement that case.
+% \begin{macrocode}
+\expandafter\ifx\csname indexname\endcsname\relax
+
+ \typeout{index.sty> Uh oh! It looks like your document style
+ doesn't use \string\indexname.}
+ \typeout{index.sty> I'll have to redefine the
+ \string\theindex\space environment, using}
+ \typeout{index.sty> the `book' style default.}
+
+ \def\indexname{Index}
+% \end{macrocode}
+% The following is adapted from \bundle{book.sty} v2.09 \vdate{14 Jan
+% 92}.
+% \begin{macrocode}
+ \def\theindex{%
+ \@restonecoltrue
+ \if@twocolumn\@restonecolfalse\fi
+ \columnseprule\z@ \columnsep 35\p@
+ \edef\@indexname{%
+ \expandafter\the\@nameuse{idxtitle@\@indextype}%
+ }%
+ \twocolumn[\@makeschapterhead{\@indexname}]%
+ \@mkboth{\uppercase{\@indexname}}{\uppercase{\@indexname}}%
+ \thispagestyle{plain}%
+ \parindent\z@
+ \parskip\z@ plus .3\p@\relax\let\item\@idxitem
+ }
+
+\else
+
+ \@temptokena={%
+ \edef\indexname{\the\@nameuse{idxtitle@\@indextype}}%
+ }
+ \toks0=\expandafter{\theindex}%
+ \edef\theindex{\the\@temptokena\the\toks0}%
+
+\fi
+% \end{macrocode}
+%
+% \begin{macro}{\@vwritefile}
+% \begin{macro}{\x@vwritefile}
+% \begin{macro}{\y@vwritefile}
+% Now we define the =\@vwritefile= macro, which copies information
+% from the =aux= file to one of the other auxiliary files.
+% =\@vwritefile= performs essentially the same function as
+% =\@writefile=, except that it does not expand it second argument
+% (i.e., it writes it out verbatim (well, almost verbatim)).
+%
+% NOTE: There doesn't seem to be any reason why =\@writefile= *should*
+% expand its second argument and in fact, we later redefine
+% =\addcontentsline= to use =\@vwritefile= instead of =\@writefile=.
+% A slight extension of this idea could be used to solve part the
+% problem of fragility in sectioning commands.
+%
+% =\@vwritefile=, like =\@writefile=, should be disabled when the
+% =aux= file is being read by =\begin{document}=. To avoid having to
+% redefine =\document=, we make the behaviour of =\@vwritefile=
+% conditional on the current meaning of =\@writefile=.
+% \begin{macrocode}
+\def\@vwritefile{%
+ \ifx\@writefile\@gobbletwo
+ \expandafter\@gobbletwo
+ \else
+ \expandafter\x@vwritefile
+ \fi
+}
+
+\def\x@vwritefile#1{%
+ \@ifundefined{tf@#1}{\@gobbletwo}{\y@vwritefile}{#1}%
+}
+
+\long\def\y@vwritefile#1#2{%
+ \def\@tempa{#2}%
+ \immediate\write\csname tf@#1\endcsname{\@nearverbatim\@tempa}%
+}
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% Now we take some code from \bundle{showidx.sty} and merge it into our
+% new system. There are four reasons for redefining the commands here
+% rather than just inputting \bundle{showidx.sty} (or requiring the user
+% to do so). First, \bundle{showidx.sty} ends with a call to
+% =\flushbottom=, which I want to avoid. Second, the instructions for
+% successfully using \bundle{showidx.sty} along with \bundle{index.sty}
+% would be somewhat tricky. This way, I can just tell users not to
+% use \bundle{showidx.sty} at all. Third, I need to make some
+% alterations to =\@showidx= anyway. In particular, (a) I need to add
+% the =\@sanitizeat= command so this works correctly with AMS-\LaTeX\
+% and (b) I want to add the =\indexproofstyle= command so the user can
+% customize the size and font used for the index proofs. Finally,
+% \bundle{showidx.sty} has at least two annoying bugs in it. See the
+% edit-history for version 2.01 for a description.
+%
+% \begin{macro}{\@indexbox}
+% This code is adapted from \bundle{showidx.sty}, v2.09 \vdate{16 Jun
+% 1991}.
+% \begin{macrocode}
+\newinsert\@indexbox
+
+\dimen\@indexbox=\maxdimen
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\@sanitizeat}
+% The definition of =\@sanitizeat= is slightly tricky, since we need
+% =@= to be active when this macro is defined, but we also need it to
+% be part of the control sequence name.
+% \begin{macrocode}
+\begingroup
+ \catcode`\@=\active
+ \expandafter\gdef\csname\string @sanitizeat\endcsname
+ {\def @{\char`\@}}
+\endgroup
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\indexproofstyle}
+% \begin{macro}{\@showidx}
+% \begin{macro}{\@leftidx}
+% \begin{macro}{\@rightidx}
+% \begin{macro}{\@mkidx}
+% \begin{macro}{\raggedbottom}
+% \begin{macro}{\flushbottom}
+% \begin{macro}{\@texttop}
+% Note the cautious way of calling =\reset@font=, which is necessary
+% for this to work correctly under both the Old and New Font Selection
+% Schemes.
+% \begin{macrocode}
+\newtoks\indexproofstyle
+
+\indexproofstyle{\footnotesize\csname reset@font\endcsname\tt}
+
+\def\@showidx#1{%
+ \insert\@indexbox{%
+ \@sanitizeat
+ \the\indexproofstyle
+ \hsize\marginparwidth
+ \hangindent\marginparsep \parindent\z@
+ \everypar{}\let\par\@@par \parfillskip\@flushglue
+ \lineskip\normallineskip
+ \baselineskip .8\normalbaselineskip\sloppy
+ \raggedright \leavevmode
+ \vrule \@height .7\normalbaselineskip \@width \z@\relax#1\relax
+ \vrule \@height\z@ \@depth.3\normalbaselineskip \@width\z@\relax
+ }%
+ \ifhmode\penalty\@M \hskip\z@skip\fi
+}
+
+\def\@leftidx{\hskip-\marginparsep \hskip-\marginparwidth}
+
+\def\@rightidx{\hskip\columnwidth \hskip\marginparsep}
+
+\def\@mkidx{%
+ \vbox to \z@{%
+ \rlap{%
+ \if@twocolumn
+ \if@firstcolumn \@leftidx \else \@rightidx \fi
+ \else
+ \if@twoside
+ \ifodd\c@page \@rightidx \else \@leftidx \fi
+ \else
+ \@rightidx
+ \fi
+ \fi
+ \box\@indexbox
+ }%
+ \vss
+ }%
+}
+
+\def\raggedbottom{%
+ \def\@textbottom{\vskip\z@ plus.0001fil}%
+ \let\@texttop\@mkidx
+}
+
+\def\flushbottom{\let\@textbottom\relax \let\@texttop\@mkidx}
+
+\let\@texttop\@mkidx
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+% \end{macro}
+%
+% Now, this next bit really gets up my nose. The only way to make
+% sure that the =\index= command gets handled correctly when used
+% inside of sectioning commands is to redefine a bunch of \LaTeX's
+% table of contents and running-heads macros. $*$blech$*$ Fragility
+% rears its ugly head again. (Incidentally, it should be possible to
+% use the =\@nearverbatim= trick to make arguments of sectioning
+% commands robust. I'll have to explore this.)
+%
+% These are based on \bundle{latex.tex} 2.09 \vdate{25 March
+% 1992}.
+%
+% \begin{macro}{\addcontentsline}
+% We need to redefine =\addcontentsline= to keep it from expanding
+% =\index= commands too far. In particular, we have removed =\index=
+% from the list of macros that are set equal to =\@gobble= and we
+% substitute =\@vwritefile= for =\@writefile=. This latter change
+% also means that we can simplify the definition of =\protect=
+% somewhat.
+% \begin{macrocode}
+\def\addcontentsline#1#2#3{%
+ \if@filesw
+ \begingroup
+ \let\label\@gobble
+ \let\glossary\@gobble
+ \def\protect##1{\string##1\space}%
+ \@temptokena{\thepage}%
+ \edef\@tempa{%
+ \write\@auxout{%
+ \string\@vwritefile{#1}{\string\contentsline{#2}{#3}%
+ {\the\@temptokena}}%
+ }%
+ }%
+ \@tempa
+ \endgroup
+ \if@nobreak\ifvmode\nobreak\fi\fi
+ \fi
+}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\@starttoc}
+% We need to redefine =\@starttoc= to =\@addtoindexfalse= so that items
+% don't get written to the index from within tables of contents. The
+% only change here is the addition of =\@addtoindexfalse=.
+% \begin{macrocode}
+\def\@starttoc#1{%
+ \begingroup
+ \@addtoindexfalse
+ \makeatletter
+ \@input{\jobname.#1}%
+ \if@filesw
+ \expandafter\newwrite\csname tf@#1\endcsname
+ \immediate\openout \csname tf@#1\endcsname \jobname.#1\relax
+ \fi
+ \global\@nobreakfalse
+ \endgroup
+}
+% \end{macrocode}
+% \end{macro}
+%
+% \begin{macro}{\markboth}
+% \begin{macro}{\markright}
+% Finally, we have to redefine =\markboth= and =\markright= to keep
+% them from disabling the expansion of =\index= while putting section
+% heads into the =\mark=. Otherwise, we'd end up with ``=\index='' in
+% the mark, which would cause problems when =\@outputpage= redefines
+% =\index= to be equal to =\@gobble=. Instead, we want =\index= to
+% expand to =\p@index= in the =\mark=, so we retain control over what
+% happens in =\@outputpage=.
+%
+% This time, the only change is to remove =\index= from the list of
+% macros that are =\let= equal to =\relax=.
+% \begin{macrocode}
+\def\markboth#1#2{%
+ \gdef\@themark{{#1}{#2}}%
+ \begingroup
+ \let\protect\noexpand
+ \let\label\relax
+ \let\glossary\relax
+ \mark{\@themark}%
+ \endgroup
+ \if@nobreak\ifvmode\nobreak\fi\fi
+}
+
+\def\markright#1{%
+ \begingroup
+ \let\protect\noexpand
+ \let\label\relax
+ \let\glossary\relax
+ \expandafter\@markright\@themark{#1}%
+ \mark{\@themark}%
+ \endgroup
+ \if@nobreak\ifvmode\nobreak\fi\fi
+}
+%</style>
+% \end{macrocode}
+% \end{macro}
+% \end{macro}
+%
+% \section{Glossaries}
+%
+%
+% \section{Edit history}
+%
+% \begin{description}
+%
+% \item[v1.00 (4 Mar 1993)]
+% initial version, posted to comp.text.tex.
+%
+% \item[v1.01 (4 Mar 1993)]
+% added =\renewindex= command and checking to make sure index is (or
+% is not) defined in =\newindex=, =\index= and =\printindex=. Also
+% tightened up the code in various places and added check to make sure
+% file is only loaded once.
+%
+% \item[v2.00 (24 Mar 1993)]
+% added support for =\index*=, proofmode, =\shortindexingon= and
+% =\shortindexingoff=.
+%
+% \item[v2.01 (24 Jun 1993)]
+% Fixed 3 bugs. (1) If proofmode was turned on, then something like
+% ``=\index{WORD}WORD='' would suppress the hyphenation of WORD. This
+% was fixed by adding ``=\penalty\@M\hskip\z@skip='' to the end of
+% =\@showidx=. (This is just the definition of =\allowhyphens=
+% borrowed from \bundle{german.sty}, v2 \vdate{4 Nov 1988}). (2) The
+% =\hbox= in =\@mkidx= was being set at its natural width, which had a
+% tendency to interfere with the width of the page. The =\hbox= is
+% now replaced by =\rlap=. (3) If the title of an index (i.e., the
+% fourth argument of =\newindex=) contained a particularly fragile
+% command like~=\d=, havoc would ensue when =\theindex= tried to
+% extract the title. Titles are now kept in token registers to
+% prevent such unpleasantness. Bugs (2) and (3) were reported by
+% Dominik Wujastyk \email{D.Wujastyk@ucl.ac.uk} on 24 June
+% 1993. Note that bugs (1) and (2) are actually bugs in showidx.sty,
+% v2.09 \vdate{16 Jun 1991}.
+%
+% \item[v2.02 (25 Jun 1993)]
+% Rewrote the code that implements the short indexing commands (=^=
+% and =_=) to make index.sty compatible with other style files that
+% need to make =^= and =_= active in some contexts. See the code for
+% more details.
+%
+% \item[v2.03 (30 Jun 1993)]
+% Once again rewrote the code that implements the short indexing
+% commands. Dumped the shortindexing environment and rewrote the
+% =\shortindexingon= and =\shortindxingoff= commands to save and
+% restore the =\catcode='s and meanings of =^= and =_= in the safest
+% possible (I hope) order. Also added the =\if@shortindexing= flag to
+% keep =\shortindexingoff= from doing anything if it is called outside
+% of the scope of a =\shortindexingon= command. (Question: Should
+% =\shortindexingon= check that flag before doing anything?)
+%
+% \item[v2.04 (beta) (14 Jul 1993)]
+% Added =\disableindex= command. Added =\newindex= and =\renewindex=
+% to =\@preamblecmds=. Added =\if@newindex= flag to =\@newindex= to
+% prevent =\renewindex= from re-allocating new =\write= and =\toks=
+% registers. Rewrote using \bundle{doc.sty} and \program{DocStrip}.
+% Also cleaned up the code somewhat.
+%
+% \item[v3.00 (15 Jul 1993)]
+% Made further minor tweaks to code and internal documentation.
+% Booted version number up to 3.00 and released on the world.
+%
+% \item[v3.01 (19 Jul 1993)]
+% Fixed \program{DocStrip} CheckSum.
+%
+% \item[v3.02 (15 Sep 1993)]
+% Corrected spelling of =\@shortindexingfalse= in definition of
+% =\shortindexingoff=. Thanks to Hendrik G. Seliger
+% \email{hank@Blimp.automat.uni-essen.de} for this bug report. Also
+% added redefinitions of =\@leftmark= and =\@rightmark= to fix a bug
+% reported by Dominik Wujastyk \email{D.Wujastyk@ucl.ac.uk}.
+%
+% \item[v3.03 (beta) (20 Feb 1994)]
+% Added =\long= to the definition of =\@ifundefined= to cover the
+% unlikely contingency that someone wanted to use, for example,
+% =\string\par= in the middle of a control sequence name. Added an
+% optional argument to =\newindex= to specify which counter to use in
+% place of =\thepage=. The first change was suggested by Martin
+% Schroeder \email{l15d@zfn.uni-bremen.de}; the second was suggested
+% independently by Schroeder and Stefan Heinrich Hoening
+% \email{hoening@pool.informatik.rwth-aachen.de}. The =\@newindex=
+% command was renamed =\def@index=. Also fixed the =\disableindex=
+% command.
+%
+% \item[v3.04 (7 Mar 1994)]
+% Rewrote the user documentation (Sections 1--5) and released on the
+% world. Also deleted some extraneous spaces that had crept into some
+% macros.
+%
+% \end{description}
+%
+% \DisableCrossrefs
+%
+% \section{The sample file}
+%
+% \begin{macrocode}
+%<sample>%% latex sample.tex
+%<sample>%% makeindex sample
+%<sample>%% makeindex -o sample.and sample.adx
+%<sample>%% makeindex -o sample.nnd sample.ndx
+%<sample>%% makeindex -o sample.lnd sample.ldx
+%<sample>%% latex sample.tex
+%<sample>
+%<sample>\documentstyle[index]{book}
+%<sample>
+%<sample>\makeindex
+%<sample>\newindex{aut}{adx}{and}{Name Index}
+%<sample>\newindex{not}{ndx}{nnd}{List of Notation}
+%<sample>
+%<sample>\newindex[theenumi]{list}{ldx}{lnd}{Items}
+%<sample>
+%<sample>\shortindexingon
+%<sample>
+%<sample>\proofmodetrue
+%<sample>
+%<sample>\def\aindex{\index*[aut]}
+%<sample>
+%<sample>\begin{document}
+%<sample>
+%<sample>\tableofcontents
+%<sample>
+%<sample>\newpage
+%<sample>
+%<sample>\chapter{Here is a ^[aut]{chapter} title}
+%<sample>
+%<sample>\section{Section header\index[aut]{section}}
+%<sample>
+%<sample>Here is some text.\index{subject}
+%<sample>
+%<sample>Here is \index[not]{notation}some more \index[not]{sin@$\sin$}
+%<sample>text.
+%<sample>
+%<sample>\newpage
+%<sample>
+%<sample>Here is some ^{more} _[not]{notation} text.
+%<sample>
+%<sample>Here is yet more \aindex{text}.
+%<sample>
+%<sample>\section{Another Section header _[aut]{section2}}
+%<sample>
+%<sample>And here is some math: $x^1_b$.
+%<sample>
+%<sample>Here is an ^[aut]{index} entry \fbox{inside an
+%<sample>\index[not]{min@$\min$}fbox}
+%<sample>
+%<sample>\fbox{Here is an ^[aut]{entry} in a box.}
+%<sample>
+%<sample>\section{An indexed list environment}
+%<sample>
+%<sample>\begin{enumerate}
+%<sample>
+%<sample>\item
+%<sample>First item
+%<sample>
+%<sample>\item
+%<sample>Second item\index[list]{second item}
+%<sample>
+%<sample>\item
+%<sample>Third item
+%<sample>
+%<sample>\newpage
+%<sample>
+%<sample>\item
+%<sample>Fourth item
+%<sample>
+%<sample>\item
+%<sample>Fifth item\index[list]{fifth item}
+%<sample>
+%<sample>\item
+%<sample>Sixth item
+%<sample>
+%<sample>\end{enumerate}
+%<sample>
+%<sample>\printindex[not]
+%<sample>
+%<sample>\printindex[aut]
+%<sample>
+%<sample>\printindex[list]
+%<sample>
+%<sample>\printindex
+%<sample>
+%<sample>\end{document}
+% \end{macrocode}
+%
+% \PrintIndex
+% \PrintChanges
+%
+% \Finale
+%
+% \end{document}
+\endinput
diff --git a/help/tex-macro-catalogue.el b/help/tex-macro-catalogue.el
new file mode 100644
index 0000000000..f550ac03b4
--- /dev/null
+++ b/help/tex-macro-catalogue.el
@@ -0,0 +1,349 @@
+;;; ====================================================================
+;;; @Emacs-Lisp-file{
+;;; filename = "tex-macro-catalogue.el",
+;;; version = "2.00",
+;;; date = "15 February 1993",
+;;; time = "14:43:35 GMT",
+;;; author = "David Carlisle",
+;;; address = "Computer Science Department
+;;; Manchester University
+;;; Oxford Road
+;;; Manchester
+;;; England
+;;; M13 9PL",
+;;; telephone = "+44 61 275 6139",
+;;; FAX = "+44 61 275 6236",
+;;; email = "carlisle@cs.man.ac.uk (Internet)",
+;;; checksum = "05502 349 1299 11389",
+;;; codetable = "ISO/ASCII",
+;;; keywords = "TeX, macros,styles,index,catalogue",
+;;; supported = "yes",
+;;; docstring = "
+;;;
+;;; A GNU Emacs interface to David Jones' Catalogue of TeX macros.
+;;;
+;;; The most recent version of the catalogue is always available
+;;; from theory.lcs.mit.edu in the directory
+;;; pub/tex/tex-styles-and-macros.txt.
+;;;
+;;; Copies can also be obtained from the following locations:
+;;;
+;;; ftp.tex.ac.uk:pub/archive/help/tex-styles-and-macros.txt
+;;; ftp.th-darmstadt.de:
+;;; pub/tex/documentation/tex-styles-and-macros.txt[.Z]
+;;; ftp.uni-stuttgart.de:/soft/tex/documentation/TeX-index
+;;; ftp.SHSU.edu:[fileserv.tex-index]tex.index
+;;; ymir.claremont.edu:[anonymous.tex.documentation]tex-index.txt
+;;;
+;;; ftp.cs.ruu.nl:pub/TEX/DOC/TeX-index.Z
+;;; ftp.math.utah.edu:pub/tex/tex-index
+;;; ftp.diku.dk:pub/TeX/misc/TeX-Index.Z
+;;;
+;;;
+;;; The checksum field above was produced by
+;;; Robert Solovay's checksum utility.",
+;;; }
+;;; ====================================================================
+
+;;; tex-macro-catalogue.el
+;;; ;;;;;;;;;;;;;;;;;;;;;;
+
+;;; This is an attempt at an emacs interface to the TeX macro catalogue
+;;; produced by David Jones <dmjones@theory.lcs.mit.edu>
+
+;;; INSTALLATION
+;;;
+;;; First obtain the catalogue and install it in a suitable directory.
+;;; Then modify the setting of tmc-file below to refer to the path
+;;; name of the catalogue file.
+;;; This file may then be installed in an emacs-lisp directory, and
+;;; byte compiled.
+
+
+;;; BASIC USE
+;;;
+;;; Add the following lines (without the `;;;') to your .emacs. The
+;;; catalogue may then be searched with M-x tex-macro-catalogue
+;;;
+;;; (autoload 'tex-macro-catalogue "tex-macro-catalogue"
+;;; "TeX macro catalogue browser" t)
+;;;
+;;; The browser will start by displaying a help screen, this screen
+;;; may be recalled later by typing `?'.
+
+
+;;; CUSTOMISATION & OTHER DETAILS
+;;;
+;;; The hook tmc-mode-hook may be set in your .emacs file, to
+;;; customise the catalogue searching.
+;;;
+;;; You may wish to change the keybindings, or modify the list
+;;; tmc-latex-sections of sections that you consider latex-related.
+;;; (eg to add LAMSTeX, or remove FOILTeX.)
+;;;
+;;; The entries are returned with only the titles displayed.
+;;; The bodies are hidden by outline mode. Typing `s' by a title shows
+;;; the corresponding body. `S' shows all the returned entries.
+;;; Hiding entries is done with `h' (one entry) or `H' all entries.
+;;;
+;;; Typing `?' displays a help screen, as long as you do not abort
+;;; this with ^g, the previous contents of the tmc-entries buffer will
+;;; be redisplayed at the next keypress.
+;;;
+;;; The first time you restrict the search to LaTeX `L', there will be
+;;; a slight delay, as the positions of the LaTeX-related sections are
+;;; determined. After the first time `L' and `A' should quickly switch
+;;; between LaTeX-specific and unrestricted searching.
+;;;
+;;; If you usually require LaTeX-restricted searching, you could cause
+;;; the browser to start off in that mode by placing a hook such as
+;;; the following (without the ;;;) in your .emacs file.
+;;;
+;;; (setq tmc-mode-hook
+;;; (function
+;;; (lambda ()
+;;; (tmc-latex-only))))
+
+
+;;; David Carlisle <carlisle@cs.man.ac.uk>
+;;;
+;;; Version 1: May 1992
+;;; Version 2: 15 February 1993
+
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
+
+
+(defconst tmc-file
+ "/usr/common/lib/tex3/doc/tex-styles-and-macros.txt"
+ "The path name for the catalogue file.
+ MUST BE SET CORRECTLY FOR YOUR SITE.")
+
+(defvar tmc-latex-sections
+ (list "AMS-LATEX" "FOILTEX" "LATEX" "SLITEX" "GENERIC MACROS")
+ "The LaTeX-related sections of the catalogue.")
+
+(defvar tmc-file-buffer nil
+ "Buffer to store the catalogue.")
+
+(defvar tmc-ranges nil
+ "The current list of ranges to search.")
+
+(defvar tmc-latex-ranges nil
+ "The list of ranges corresponding to tmc-latex-sections.")
+
+(defun tmc-all-formats ()
+ "Search the whole file, not just LaTeX-related sections."
+ (interactive)
+ (if (string= (buffer-name) "tmc-entries")
+ (progn
+ (setq mode-name "Macro Catalogue Entries")
+;; Force an update to the modeline.
+ (set-buffer-modified-p (buffer-modified-p))))
+ (set-buffer tmc-file-buffer)
+;; Set the range list to be one range, the whole file.
+ (setq tmc-ranges (list (cons (point-min) (point-max)))))
+
+(defun tmc-latex-only ()
+ "Search the whole file, not just LaTeX-related sections."
+ (interactive)
+ (if (string= (buffer-name) "tmc-entries")
+ (progn
+ (setq mode-name "Macro Catalogue Entries (LaTeX only)")
+;; Force an update to the modeline.
+ (set-buffer-modified-p (buffer-modified-p))))
+ (set-buffer tmc-file-buffer)
+;; If we have not already computed the ranges coresponding to the
+;; section titles, compute them now.
+ (setq tmc-ranges
+ (or
+ tmc-latex-ranges
+ (prog2
+ (message "Locating LaTeX sections...")
+ (setq tmc-latex-ranges
+ (mapcar 'tmc-find-section tmc-latex-sections))
+ (message "done")))))
+
+
+(defun tmc-find-section (secname)
+ "Return a cons-pair containing the markers corresponding to the start
+ and finish of the requested section"
+ (goto-char (point-min))
+;; Section titles have a blank line before and after. (To distinguish
+;; them from the list of sections at the beginning.)
+ (re-search-forward
+ (concat "\n\\s-*\n%%Section [0-9]+: " secname " *$\n\\s-*\n"))
+ (cons (point)
+ (progn (re-search-forward "\n%%Section [0-9]+:" (point-max) 1)
+ (point))))
+
+(defun tmc-list-search-section (range)
+ "Search for an entry within the specified range."
+ (set-buffer (get-buffer-create "tmc-entries"))
+ (set-buffer tmc-file-buffer)
+ (goto-char (car range))
+ (while (re-search-forward
+ (concat "^"key-type": .*\\b"key"\\b") (cdr range) t)
+ (save-excursion (tmc-get-entry)))
+ (switch-to-buffer "tmc-entries")
+ (hide-body)
+ (goto-char (point-min))
+ (forward-line 1))
+
+(defun tmc-list-search (key-type key)
+ "Search for the entry in every range in the list tmc-ranges."
+ (message "Searching...")
+ (mapcar 'tmc-list-search-section tmc-ranges)
+ (message "done"))
+
+(defun tmc-list-by-author (auth)
+ "Search for entries by author."
+ (interactive "sAuthor Name: ")
+ (tmc-list-search "Author" auth))
+
+(defun tmc-list-by-keyword (key)
+ "Search for entries by keyword."
+ (interactive "sKeyword: ")
+ (tmc-list-search "Keywords" key))
+
+(defun tmc-list-by-title (name)
+ "Search for entries by title (= name)."
+ (interactive "sTitle: ")
+ (tmc-list-search "Name" name))
+
+(defun tmc-get-entry ()
+ "Insert the found entry into the tmc-entries buffer."
+ (re-search-backward "^[ ]*$")
+ (let ((tmc-entry
+ (buffer-substring (point)
+ (progn
+ (forward-line 1)(re-search-forward "^[ ]*$") (point)))))
+ (set-buffer "tmc-entries")
+ (goto-char (point-max))
+ (insert tmc-entry)))
+
+(defvar tmc-map (make-sparse-keymap)
+ "Local keymap used in TeX macro catalogue entries buffer.")
+
+
+(defun tex-macro-catalogue ()
+ "Initialise a buffer to control searching the TeX macro catalogue.
+ The available commands are:
+\\{tmc-map}"
+ (interactive)
+;; Load the file if not already loaded,
+;; without evaluating any hooks or local variables
+ (if tmc-file-buffer
+ (set-buffer tmc-file-buffer)
+;;else
+ (setq tmc-file-buffer (create-file-buffer tmc-file))
+ (set-buffer tmc-file-buffer)
+ (insert-file-contents tmc-file))
+ (setq buffer-read-only t)
+ (switch-to-buffer (get-buffer-create "tmc-entries"))
+;; Use outline mode to hide the entry bodies.
+ (outline-mode)
+ (make-local-variable 'outline-regexp)
+ (setq outline-regexp "Name")
+ (setq major-mode 'tex-macro-catalogue)
+ (tmc-all-formats)
+ (switch-to-buffer (get-buffer-create "tmc-entries"))
+ (use-local-map tmc-map)
+;; Individual customisations.
+ (run-hooks 'tmc-mode-hook)
+;; Start off with the help screen.
+ (tmc-help))
+
+(defvar tmc-help nil "The help string")
+
+(defun tmc-help ()
+ "Help for TeX macro catalogue searches."
+ (interactive)
+ (switch-to-buffer (get-buffer-create "tmc-entries"))
+;; The help string is displayed until the next key sequence.
+;; The previous contents of the buffer are then returned, unless the
+;; help is quit with \C-g.
+ (let ((p (point))
+ (tmc-temp (buffer-string)))
+ (erase-buffer)
+;; Only initialise the help string now in case the user has changed
+;; the key bindings in tmc-mode-hook.
+ (insert (or tmc-help
+ tmc-help
+ (setq tmc-help (substitute-command-keys
+"TeX Macro Catalogue
+
+Before Searching, type:
+
+ `\\[tmc-latex-only]' \
+Restrict search to LaTeX and related formats.
+ `\\[tmc-all-formats]' \
+Allow searching over the whole catalogue. (Default.)
+
+To search, type:
+ `\\[tmc-list-by-keyword]' \
+to search the catalogue by Keyword.
+ `\\[tmc-list-by-author]' \
+to search the catalogue by Author.
+ `\\[tmc-list-by-title]' \
+to search the catalogue by Title (name) of package.
+
+After a successful search, type:
+ `\\[outline-next-visible-heading]' \
+`\\[outline-previous-visible-heading]' \
+Move to next (previous) entry.
+
+ `\\[show-subtree]' `\\[show-all]' \
+Show current entry (All entries).
+ `\\[hide-subtree]' `\\[hide-body]' \
+Hide current entry (All entries).
+
+ `\\[tmc-clear]' Clear this buffer.
+ `\\[tmc-quit]' Quit.
+
+ `\\[tmc-help]' Get this help
+ "))))
+ (goto-char (point-min))
+ (sit-for 60)
+ (erase-buffer)
+ (insert tmc-temp)
+ (goto-char p)))
+
+
+(defun tmc-clear ()
+ "Clear the tmc-entries buffer."
+ (interactive)
+ (set-buffer "tmc-entries")
+ (erase-buffer))
+
+(defun tmc-quit ()
+ "Quit searching the catalogue."
+ (interactive)
+ (tmc-clear)
+ (bury-buffer tmc-file-buffer)
+ (let ((obuf (current-buffer)))
+ (switch-to-buffer (other-buffer))
+ (bury-buffer obuf)))
+
+
+;; Set up the default key bindings.
+(define-key tmc-map "S" 'show-all)
+(define-key tmc-map "H" 'hide-body)
+(define-key tmc-map "s" 'show-subtree)
+(define-key tmc-map "h" 'hide-subtree)
+(define-key tmc-map "n" 'outline-next-visible-heading)
+(define-key tmc-map "p" 'outline-previous-visible-heading)
+
+(define-key tmc-map "k" 'tmc-list-by-keyword)
+(define-key tmc-map "a" 'tmc-list-by-author)
+(define-key tmc-map "t" 'tmc-list-by-title)
+
+(define-key tmc-map "c" 'tmc-clear)
+(define-key tmc-map "q" 'tmc-quit)
+
+(define-key tmc-map "L" 'tmc-latex-only)
+(define-key tmc-map "A" 'tmc-all-formats)
+
+(define-key tmc-map "?" 'tmc-help)
+
+
+;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
diff --git a/help/texlists.txt b/help/texlists.txt
new file mode 100644
index 0000000000..4c9d7be627
--- /dev/null
+++ b/help/texlists.txt
@@ -0,0 +1,103 @@
+BABYL OPTIONS:
+Version: 5
+Labels:
+Note: This is the header of an rmail file.
+Note: If you are seeing it in rmail,
+Note: it means the file has no messages in it.
+
+1,,
+Return-Path: <spqr@minster.york.ac.uk>
+Received: from minster.york.ac.uk by ftp.tex.ac.uk (4.1/SMI-4.1)
+ id AA00327; Fri, 16 Apr 93 16:41:59 GMT
+From: spqr@minster.york.ac.uk
+Date: Fri, 16 Apr 93 17:31:11
+Message-Id: <swordfish.734978407@minster.york.ac.uk>
+To: archive@ftp.tex.ac.uk
+Subject: forwarded message from spqr
+
+*** EOOH ***
+Return-Path: <spqr@minster.york.ac.uk>
+From: spqr@minster.york.ac.uk
+Date: Fri, 16 Apr 93 17:31:11
+To: archive@ftp.tex.ac.uk
+Subject: forwarded message from spqr
+
+------- Start of forwarded message -------
+Status: RO
+X-VM-v5-Data: ([nil nil nil nil nil nil t nil nil]
+ ["3371" "Fri" "16" "April" "93" "10:23:33" nil "spqr" "spqr" nil "67" "TeX listserv mailing lists" "^To:" nil nil "4"])
+In-reply-to: smith-una@yale.edu's message of 13 Apr 93 18:42:51 GMT
+To:spqr
+Subject: TeX listserv mailing lists
+
+ From: smith-una@yale.edu (Una Smith)
+ Newsgroups: comp.text.tex,yale.tex-users
+ Date: 13 Apr 93 18:42:51 GMT
+ Reply-To: smith-una@yale.edu
+ Organization: Department of Biology, Yale University
+ NNTP-Posting-Host: minerva.cis.yale.edu
+
+
+ Sending the message "lists global /tex" to listserv@bitnic.bitnet on
+ 13 April 1993 resulted in the following list (after some editing by me).
+ I submit this for your entertainment, and suggest it be added to the
+ comp.text.tex FAQ.
+
+ To subscribe to one of these lists, send e-mail to the username "listserv"
+ at the indicated node, with the string "subscribe <list name> <Your Name>"
+ in the body of your message. From non-Bitnet sites, you'll need to append
+ the string ".bitnet" to the address below.
+
+ Una
+
+
+ Excerpt from the LISTSERV lists known to LISTSERV@BITNIC on 13 Apr 1993 14:14
+ Search string: TEX
+
+ List name Full address List title
+ --------- ------------ ----------
+ ATMTUG-L ATMTUG-L@TAMVM1 "ATMTUG-L (TAMU TeX Users Group Discussion l+
+ GOPUB-L GOPUB-L@BROWNVM Translating Formatted Text to ASCII Discussi+
+ ITALIC-L ITALIC-L@IRLEARN ITALIC-L - The Irish Tex And Latex Interest +
+ ITEX-L ITEX-L@TAUNIVM ITEX Discussion List
+ IVRITEX IVRITEX@TAUNIVM Hebrew TeX list
+ LATEX-L LATEX-L@BRUFSC FORUM LATEX-L - Discussao de assuntos pertin+
+ LATEX-UG LATEX-UG@SAUPM00 LaTeX Users Group.
+ MUTEX MUTEX@CSBRMU11 MUTEX - Masaryk University TEX discussion li+
+ RUSTEX-L RUSTEX-L@UBVM Russian TeX and Cyrillic text processing list
+ TEX-D-L TEX-D-L@DEARN German TeX Users Communication List
+ TEX-ED TEX-ED@UICVM TeX Education Forum List
+ TEX-EURO TEX-EURO@DHDURZ1 TeX-Euro Distribution List for European TeX+
+ TEX-IBM TEX-IBM@DHDURZ1 TEX-IBM Distribution list
+ TEX-L TEX-L@BNANDP11 (Peered) The TeXnical topics list
+ TEX-L@CLVM (Peered) The TeXnical topics list
+ TEX-L@DEARN (Peered) The TeXnical topics list
+ TEX-L@HEARN (Peered) The TeXnical topics list
+ TEX-L@MARIST (Peered) The TeXnical topics list
+ TEX-L@UBVM (Peered) The TeXnical topics list
+ TEXHAX@UWAVM (Peered) TeXhax Distribution List
+ TEX-NL TEX-NL@HEARN TEX-NL
+ TEXHAX-L TEXHAX-L@IRLEARN TeX Information Distribution List
+ TEXMAG-L TEXMAG-L@DEARN (Peered) TeXMaG list
+ TEXMAG-L@HEARN (Peered) (TeXMaG)
+ TEXMAG-L@IRLEARN (Peered) TeXMaG - Magazine for TeX Enthusias+
+ TEXMAG-L@PUCC (Peered) (TeXMaG)
+ TEXMAG-L@TCSVM (Peered) (TeXMaG)
+ TEXMAG-L@UICVM (Peered) (TeXMaG)
+ TEXMAG-L@UTORONTO (Peered) (TeXMaG)
+ TEXROX-L TEXROX-L@TAMVM1 The TeXrox Information List
+ TWGMLC-L TWGMLC-L@IRLEARN TWGMLC-L TeX Users Group TeXnical Working Gr+
+ UKTEX UKTEX@FRORS13 UKTeX : UKTeX redistribution from ASTON
+ UKTEX-L UKTEX-L@DHDURZ1 UKTeX-L Distribution List for German TeX Use+
+ VMSTEX-L VMSTEX-L@UICVM VMSTEX-L
+ YUNUS YUNUS@TRMETU (Peered) Turkish TeX Users Group YUNUS
+
+ --
+
+ Una Smith Biology Department smith-una@yale.edu
+ Yale University
+ New Haven, CT 06511
+------- End of forwarded message -------
+
+
+ \ No newline at end of file
diff --git a/help/uk-tex-faq/CHANGES-3.16b b/help/uk-tex-faq/CHANGES-3.16b
new file mode 100644
index 0000000000..1a9ab7d229
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.16b
@@ -0,0 +1,55 @@
+Changes in version 3.16c
+
+This file incorporates the changes from version 3.16 that previously
+appeared in file CHANGES-3.16a and -3.16b; new changes for this
+release (3.16c) are marked with a plus ("+") sign.
+
+
+New answer:
+ +Label isdef: "is this command defined?" tests
+ Label optionclash: clashing package options error in LaTeX
+
+Revised answers:
+ +Label bibprefixsort: two new examples
+ +Label citeURL: provide a list (rather than a bunch) of alternative
+ styles, mention babelbib
+ Label ECfonts: reword discussion of mathematics and EC fonts (i.e.,
+ emphasise that there's no direct relation)
+ Label filename: extend macro definitions, hopefully expanding the
+ usefulness and usability of the answer
+ Label hyperdupdest: other sources of the error than repeated pages
+ Label minitoc: corrected error in q-minitoc code, tidy comments
+ Label minxampl: include the word "minimal", since it's a common search term
+ +Label multirow: mention the case of multicolumn-multirow
+ Label music: mention Lilypond as a source of TeX-compatible music
+ +Label music: correct Web output of package list at end of answer
+ +Label oarglikesect: mention kernel command \@dblarg
+ Label poster: mention Nicola Talbot's experimental flowfram layout package
+ +Label secthead: rewritten accounts of sectsty & titlesec
+ Label texinfo: rewritten in parts, following a reader comment
+ Label texsystems: miktex installation has changed with v2.5
+ Label tutbitslatex: added pointers to TUG-maintained material on fonts
+ +Label tutbitslatex: added pointer to Fauske's page on PGF/TikZ
+ Label virtualfonts: re-thought through
+ +Label watermark: noted that package draftcopy doesn't work with pdflatex,
+ +Label watermark: mention draftwatermark
+ +Label whatbst: correct reed.edu link
+
+Bugfixes:
+ Label cmdstar: part of the example code was just wrong
+ Label enumerate: unclarity in text caused by a typo
+ Bug in "introduction=yes" HTML code corrected
+ Label atsigns: mark-up error caused curious HTML output (editorial
+ improvement too)
+ +Release dates are now represented in ISO format (yyyy-mm-dd) --
+ previously we used the LaTeX format, using solidus instead of hyphen
+
+Future releases:
+ Despite missing the nominal "end August 2006" delivery (through an
+ unfortunate combination of events), I'm aiming to maintain the
+ stream of (approximately) monthly "bugfix" releases. There are no
+ current plans for a major release, though work on the new web-based
+ version continues.
+
+Robin Fairbairns
+2006-10-02
diff --git a/help/uk-tex-faq/CHANGES-3.16c b/help/uk-tex-faq/CHANGES-3.16c
new file mode 100644
index 0000000000..8a651ecab8
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.16c
@@ -0,0 +1,52 @@
+Changes in version 3.16c
+
+This file incorporates the changes from version 3.16 that previously
+appeared in file CHANGES-3.16a and -3.16b; new changes for this
+release (3.16c) are marked with a plus ("+") sign.
+
+
+New answer:
+ +Label isdef: "is this command defined?" tests
+ Label optionclash: clashing package options error in LaTeX
+
+Revised answers:
+ +Label bibprefixsort: two new examples
+ +Label citeURL: provide a list (rather than a bunch) of alternative
+ styles, mention babelbib
+ Label ECfonts: reword discussion of mathematics and EC fonts (i.e.,
+ emphasise that there's no direct relation)
+ Label filename: extend macro definitions, hopefully expanding the
+ usefulness and usability of the answer
+ Label hyperdupdest: other sources of the error than repeated pages
+ Label minitoc: corrected error in q-minitoc code, tidy comments
+ Label minxampl: include the word "minimal", since it's a common search term
+ +Label multirow: mention the case of multicolumn-multirow
+ Label music: mention Lilypond as a source of TeX-compatible music
+ +Label music: correct Web output of package list at end of answer
+ +Label oarglikesect: mention kernel command \@dblarg
+ Label poster: mention Nicola Talbot's experimental flowfram layout package
+ +Label secthead: rewritten accounts of sectsty & titlesec
+ Label texinfo: rewritten in parts, following a reader comment
+ Label texsystems: miktex installation has changed with v2.5
+ Label tutbitslatex: added pointers to TUG-maintained material on fonts
+ +Label tutbitslatex: added pointer to Fauske's page on PGF/TikZ
+ Label virtualfonts: re-thought through
+ +Label watermark: noted that package draftcopy doesn't work with pdflatex,
+ +Label watermark: mention draftwatermark
+ +Label whatbst: correct reed.edu link
+
+Bugfixes:
+ Label cmdstar: part of the example code was just wrong
+ Label enumerate: unclarity in text caused by a typo
+ Bug in "introduction=yes" HTML code corrected
+ Label atsigns: mark-up error caused curious HTML output (editorial
+ improvement too)
+ +Release dates are now represented in ISO format (yyyy-mm-dd) --
+ previously we used the LaTeX format, using solidus instead of hyphen
+
+Future releases:
+ There are no current plans for a major release, though work on the
+ new web-based version continues.
+
+Robin Fairbairns
+2006-12-18
diff --git a/help/uk-tex-faq/CHANGES-3.17 b/help/uk-tex-faq/CHANGES-3.17
new file mode 100644
index 0000000000..c5c26c2c45
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.17
@@ -0,0 +1,58 @@
+Changes in version 3.16d
+
+This file incorporates the changes from version 3.16 that previously
+appeared in file CHANGES-3.16a, -3.16b and -3.16c; new changes for
+this release (3.16d) are marked with a plus ("+") sign.
+
+
+New answers:
+ +Label biblatex: discusses BibTeX replacements (amsrefs, biblatex)
+ +Label checksum: "checksum error in font" message
+ +Label figurehere: how to avoid floating figures/tables altogether
+ +Label entercompmode: "entering compatibility mode" message
+ +Label fontsize: how to program arbitrary font sizes in LaTeX
+ +Label latexqual: assessing the quality of your LaTeX
+ +Label mathonlyref: only referenced equations are numbered
+ +Label run-fn-nos: running footnote numbers when class numbers per chapter
+
+Revised answers:
+ +Label altabcr: extended examples and tidied a bit
+ +Label BibTeXing: add reference to Shell & Hoadley's btxFAQ
+ +Label books mention LaTeX Graphics Companion 2nd edition; use ISBN-13
+ +Label CD: now couched in terms of the TeX collection
+ +Label changebar: mention changes.sty
+ +Label commercial:update details of Textures
+ +Label dec_comma: mention numprint as possible way to get things right
+ +Label docpictex: mention PiCTeX summary now on CTAN
+ +Label fonts-pln: mention pdcmac bundle
+ +Label ftnsect: rewrite to make recommendations clearer
+ +Label getbitmap: reworded to suggest that bitmaps aren't standard any more
+ +Label LaTeXtoPlain: suggest ways forward for aspiring translators
+ +Label make: mention autolatex
+ +Label man-latex: mention Grtzer's "short course"
+ +Label minxampl: editorial work, including (perhaps) clarifying web version
+ +Label newfont*: was newfont; content rearranged between this, plninltx* and
+ the new label fontsize
+ +Label newfunction: expand description
+ +Label ol-books: TeX by Topic now available from CTAN
+ +Label papersize: mention Acrobat Reader's default scaling
+ +Label plninltx*: was plninltx; content rearranged between this, newfont* and
+ the new fontsize
+ +Label protect: clarify lists of commands known to be fragile, etc
+ +Label psfchoice: add links to papers about maths fonts in tex; add fouriernc,
+ mathdesign/FS Garamond, kpfonts, minionpro and mnsymbol
+ +Label running-nos: rearrange to emphasise package chngctr
+ +Label tabcellalign: rationalised, reduced range of recommendations
+ +Label tocbibind: mention \phantomsection for when doing the job "by hand"
+ +Label twooptarg: mention the xargs package
+ +Label unkgrfextn: mention grffile package
+ +Label wdnohyph: mention \uchyph (not that it's much use)
+
+Bugfixes:
+
+Future releases:
+ There are no current plans for a major release, though work on the
+ new web-based version continues.
+
+Robin Fairbairns
+2007-10-??
diff --git a/help/uk-tex-faq/CHANGES-3.18 b/help/uk-tex-faq/CHANGES-3.18
new file mode 100644
index 0000000000..75f90d12bc
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.18
@@ -0,0 +1,46 @@
+Changes in version 3.18
+
+This file lists changes since its most recent release (with version 3.17
+of the FAQ).
+
+New answers:
+ +Label acroantics:getting Adobe Reader to produce the right size output
+ +Label inst-scut: introduction to the old inst-miktex and to inst-tds-zip
+ +Label inst-tds-zip: installing a package using .tds.zip files
+ +Label onna-stick:making MikTeX run from a memory key
+ +Label papergeom: how to select the correct paper geometry
+ +Label prept1font:the generating metrics part of old instt1font
+ +Label tds-zip: brief outline of TDS ZIP files
+
+Revised answers:
+ +Label biblatex: now discusses crossTeX too
+ +Label bibtranscinit: discuss truly excessive sets of initials
+ +Label chngmargonfly: mention new changepage package
+ +Label findfiles: correct one of the search address links
+ +Label fmtconv: add tex4ht as a route to word format, tidy up
+ +Label footintab: I _think_ the answer now says what I meant it to say!
+ +Label labelfig: mention (auto-)pst-pdf
+ +Label letterspace: microtype now covers the functionality of old letterspace
+ +Label luatex: detail some recent developments
+ +Label oddpage: mention new changepage package
+ +Label papersize: rewritten as intro to new acroantics and papergeom
+ +Label parallel: mention the pdfcolparallel package
+ +Label patch: rewrite to downplay patch, add mention of ted and etoolbox
+ +Label pkfix: mention pkfix-helper
+ +Label poster: updated with further informative links, etc.
+ +Label protect: rewritten (again)
+ +Label psfchoice: add kpfonts, link to the font catalogue at various points
+ mention font catalogue (as a whole) and maths font survey
+Web interface:
+ A mechanism is now in place, whereby old question labels may be used to get
+ to the nearest current equivalent of the question. It does not cover *all*
+ old questions: please mail faq-devel@tex.ac.uk if you have a problem with an
+ old question label that you have stored.
+
+Bugfixes:
+ Bits of silliness in the web interface continue to surface. They get mended
+ as soon as I work out how; the most recent was a tendency not to translate
+ \textbackslash -- I know how to correct it, but not why it happened...
+
+Robin Fairbairns
+2008-06-20
diff --git a/help/uk-tex-faq/CHANGES-3.19 b/help/uk-tex-faq/CHANGES-3.19
new file mode 100644
index 0000000000..1e429919a2
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.19
@@ -0,0 +1,67 @@
+Changes in version 3.19
+
+This file lists changes since its most recent release (with version 3.18
+of the FAQ).
+
+New answers:
+ +Label grffilenames: "modern" file names in graphics
+ +Label keyval: using key-value input in macros and package
+ +Label linmacnames: why non-letters in macro names are a bad idea
+ +Label osf: using fonts with "old-style" numbers
+ +Label pdf-fig-chars: disappearing glyphs in pdfTeX figures (from Thanh)
+ +Label texorpdf: error "not allowed in PDFDocEncoded string"
+ +Label texthings: what all these <thing>TeX names are
+ +Label usesymb: using symbols
+ +Label whatmacros:brief outline of macros for "bits and pieces" section
+ +Label wideflt: centre a float wider than text area
+
+Relabelled answers:
+ +Label xfigetc: discusses xfig and asymptote (so far) (was label xfig)
+
+Revised answers:
+ +Label askquestion: what to do if your minimal example needs a figure
+ +Label acroantics:content of old label outszwrng merged in
+ +Label biblatex: updated, now also mentions biber
+ +Label books: mention Lulu version of TeX by Topic
+ +Label chngmargonfly: mention addlines package
+ +Label compactbib:mention the compactbib package (surprise!)
+ +Label drawing: describe pictex, epic and eepic (all previously skated over)
+ +Label editors: mention texworks
+ +Label figurehere:mention \MakeSorted from perpage package
+ +Label fonts-pln: mention varisize
+ +Label footnpp: mention zref package perpage module
+ +Label ftncapt: clarification (I hope)
+ +Label latex2html:mention plastex
+ +Label latexe: reworked for clarity
+ +Label latexpronounce: following on from latexe
+ +Label linenos: numline package now obsolete
+ +Label luatex: tidied up, now I'm clearer about LuaTeX, myself
+ +Label logos: clarified, in light of changes to printing layout we now use
+ +Label man-latex: added pointer to first-latex-doc
+ +Label marginpkgs:changepage package supplants chngpage
+ +Label mcite: mention mciteplus and collref packages
+ +Label nonfree: explain what went wrong and what is happening
+ +Label ifpdf: mention ifxetex and ifluatex
+ +Label noroom: tidied up e-TeX related part of answer
+ +Label ref-doc: mention latexcheat
+ +Label setURL: mention spaces and hyphens options of url.sty
+ +Label texsystems:mention MikTeX-for-Linux
+ +Label wordcount: mention TeXcount
+ +Label writecls: mention Oberdiek's splendid source2e pdf file
+ +Label wygexpts: preview-latex now part of auctex
+
+Deleted answers:
+ +Label outszwrng
+(remember, as of the previous release, links to "old" labels remain
+valid, pointing to an answer that is as near relevant as possible)
+
+Web interface:
+ The initial list of questions no longer gives a URL containing all
+ the answers -- Google was returning that for every match, which
+ didn't help!
+ All links to CTAN files, directory .zips and directories for
+ browsing are now http, and there's no longer any mention of .tar.gz
+ archives of CTAN directories (since they're no longer available)
+
+Robin Fairbairns
+2009-06-10
diff --git a/help/uk-tex-faq/CHANGES-3.19a b/help/uk-tex-faq/CHANGES-3.19a
new file mode 100644
index 0000000000..a9d2e1b0a4
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.19a
@@ -0,0 +1,44 @@
+Changes in version 3.19
+
+This file lists changes since its most recent release (with version 3.18
+of the FAQ).
+
+New answers:
+[none yet]
+ +Label grffilenames: "modern" file names in graphics
+ +Label keyval: using key-value input in macros and package
+ +Label linmacnames: why non-letters in macro names are a bad idea
+ +Label osf: using fonts with "old-style" numbers
+ +Label pdf-fig-chars: disappearing glyphs in pdfTeX figures (from Thanh)
+ +Label texorpdf: error "not allowed in PDFDocEncoded string"
+ +Label texthings: what all these <thing>TeX names are
+ +Label usesymb: using symbols
+ +Label whatmacros:brief outline of macros for "bits and pieces" section
+ +Label wideflt: centre a float wider than text area
+
+Relabelled answers:
+[none yet]
+ +Label xfigetc: discusses xfig and asymptote (so far) (was label xfig)
+
+Revised answers:
+ +Label impgraph: changed the question title
+ +Label man-latex: mention Philip Hirschhorn's "getting up and running..."
+ +Label mathstext: correct discussion of \textrm in maths
+
+Deleted answers:
+[none yet]
+ +Label outszwrng
+(remember, as of the previous release, links to "old" labels remain
+valid, pointing to an answer that is as near relevant as possible)
+
+Web interface:
+[no changes yet]
+ The initial list of questions no longer gives a URL containing all
+ the answers -- Google was returning that for every match, which
+ didn't help!
+ All links to CTAN files, directory .zips and directories for
+ browsing are now http, and there's no longer any mention of .tar.gz
+ archives of CTAN directories (since they're no longer available)
+
+Robin Fairbairns
+2009-06-16
diff --git a/help/uk-tex-faq/CHANGES-3.19c b/help/uk-tex-faq/CHANGES-3.19c
new file mode 100644
index 0000000000..dacd59d989
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.19c
@@ -0,0 +1,44 @@
+Changes in version 3.19c
+
+This file lists changes since its most recent release (with version 3.19a
+of the FAQ -- version 3.19b was a bug-fix patch).
+
+New answers:
+ <none>
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label adobetypen: mention xetex and luatex where previously said OTF unusable
+ +Label amfonts: mention DVI dis-/re-assembly to get rid of am fonts refs
+ +Label buildbib: mention Google Scholar's bibtex output
+ +Label cd: update details of the TeX collection
+ +Label context: attempt closer tally with reality (further input welcome!)
+ +Label doc-dirs: Herbert Voss's "tips and tricks" has gone
+ +Label errmissitem: remove spurious command in example code
+ +Label findfiles: update address given for dante search page
+ +Label figurehere: mention the re-implemented here package
+ +Label footintab: mention threeparttablex package
+ +Label keyval: replace keys3 mention with l3keys[2e]
+ +Label latex3: tidy, update broken references
+ +Label luatex: better English(!), mention release of 0.50.0
+ +Label mathml: correct link to mathtex
+ +Label nonfree: the non-free tree has disappeared...
+ +Label patch: sort out examples
+ +Label privinst: change recommended use of kpsewhich
+ default home texmf is different for MacTeX
+ +Label psfchoice: mention txfontsb
+ +Label what-tds: change recommended use of kpsewhich (as privinst)
+
+ (throughout): use mirrors.ctan.org rather than www.tex.ac.uk
+ where appropriate
+
+Deleted answers:
+ <none>
+
+Web interface:
+ One bug fix (code examples containing \let tended to be lost)
+
+Robin Fairbairns
+2010-01-19
diff --git a/help/uk-tex-faq/CHANGES-3.19d b/help/uk-tex-faq/CHANGES-3.19d
new file mode 100644
index 0000000000..f447a03924
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.19d
@@ -0,0 +1,34 @@
+Changes in version 3.19d
+
+This file lists changes since its most recent release (with version 3.19c
+of the FAQ).
+
+New answers:
+ +Label plaintex: explains "writing in tex", was part of Label whattex
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label codelist: mention the minted package
+ +Label docs: single reference to epslatex (via catalogue)
+ +Label etex: add ctan link
+ +Label filesused: rewrite to clarify the issue with \input
+ +Label luatex: now version 0.60.0
+ +Label fonts-pln: replace some complete gibberish (undoing mis-edits, I guess)
+ +Label parallel: mention the pdfcolparcolumns package
+ +Label seccntfmt: remove superfluous \expandafter in programming, tidy text
+ +Label tabcellalign: editorial on \PBS macro discussion
+ +Label texfuture: rehashed, in light of today's situation
+ +Label whattex: simplified by removal of material for Label plaintex
+
+Deleted answers:
+ <none>
+
+Web interface:
+ Extension of links to catalogue, to packages "distributed as part of..."
+ Abbreviate header text (omitting long list of "helpers" -- which will
+ ultimately be available in a separate file online)
+ Convert all alphabetic SGML entities to use numeric equivalents
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.20 b/help/uk-tex-faq/CHANGES-3.20
new file mode 100644
index 0000000000..346afcbdb1
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.20
@@ -0,0 +1,40 @@
+Changes since version 3.19d
+
+New answers:
+ +Label initex: why is there no initex?
+ +Label sysunix: TeX for Unix and GNU/Linux systems, revised from TeXsystems
+ added the tex-gpc distribution
+ +Label syswin: TeX for Windows 32, etc., systems, revised from TeXsystems
+ +Label sysmac: TeX for Macintosh systems, revised from TeXsystems
+ +Label sysother: TeX for other systems, revised from TeXsystems
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label baselinepar: rewritten, taking info account a recent issue from ctt
+ +Label biblatex: can now give a CTAN link for Biber
+ +Label cd: reworded to reflect current realities
+ +label extsizes: mention some classes that have non-standard font sizes
+ +label filename: bugfix for (simple) macros saving "current file name"
+ +Label letterclass: mention knuth's letter stuff and isodoc class
+ +Label manymathalph:correction to us of controls on alphabets in bm
+ +Label mathml: recognise STIX fonts as potential contribution
+ +Label mcite: revtex 4.1 has its own mechanism
+ +Label metrics: rewrite text about LY1 encoding
+ +Label multidoc: mention docmute, standalone and subdocs
+ +Label nopagebrk: correct assertion about lists vs. samepage environment
+ +Label poster: mention beamerposter
+ +Label psfchoice: add URW Classico to the list
+ +Label reallyblank: mention emptypage package
+ +Label slidecls: mention lecturer and present packages (neither is a class)
+ +Label TeXsystems: now a list of links to the new sys* labels
+ +Label widows: rewritten with clarification from Peter Moulder
+
+Deleted answers:
+ <none>
+
+Web interface:
+ Links to packages, etc., now use http://mirror.ctan.org
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.21 b/help/uk-tex-faq/CHANGES-3.21
new file mode 100644
index 0000000000..1d7abd0014
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.21
@@ -0,0 +1,47 @@
+Changes since version 3.20
+
+New answers:
+ +Label spawnprog: the \write18 mechanism for spawning programs
+ +Label whatengine: am I running pdfTeX, XeTeX or luaTeX?
+ +Label write: the \write primitive for writing text files
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label biblatex: mention bibtex8, even though biblatex+biber are winning
+ +Label codelist: extend coverage of minted package (and Pygments)
+ +Label commercial: remove Y&Y (not commercial any longer)
+ +Label dpfloat: mention floatpage package
+ +Label drawing: mention "embedded source" packages for asy, gplot, mp
+ +Label editors: rationalise, removing "wildcard"
+ +Label filename: add currfile, remove "DIY" code (which never worked right)
+ +Label floats: update discussion of morefloats package, mention etex.sty
+ +Label fmtconv: mention openoffice route for MS-word
+ +Label gethelp: link "latex community" and "latex stack exchange"
+ +Label graphicspath: rephrase discussion of \graphicspath
+ +Label instt1font: attempt to clarify updmap vs. updmap-sys
+ +Label labelfig: mention (new) lpic package
+ +Label latex2html: link to info on tug.org (note tex4ht now sourced there)
+ +Label mathml: link to info on tug.org
+ +Label music: rewritten following rearrangements on ctan
+ +Label nopagebrk: discuss \pagebreak, \nopagebreak (!)
+ +Label papergeom: discuss dvipdfm and its extensions
+ +Label psfchoice: report one (at least) known problem with [pt]xfonts
+ +Label pspreview: simplify, given that it's far less of a problem now
+ +Label ref-doc remove link to NASA latex ref, add link to gna.org one
+ +Label textflow: mention cutwin package
+ +Label tmupfl: mention morefloats package, with caveats
+ +Label verbwithin: mention cprotect package
+ +Label WYGexpts: drop "activetex" -- seems no longer available
+ +Label zerochap: rewrite for clarification
+
+Deleted answers:
+ +Label ifpdf: subsumed in new "whatengine" answer (link rerouted there)
+ +Label lollipop: no longer relevant (a pity)
+
+Web interface, etc.:
+ Some LaTeX command translations were broken, and have been mended
+ Work has started on a major reorganisation of the "fonts" section
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.22 b/help/uk-tex-faq/CHANGES-3.22
new file mode 100644
index 0000000000..b874fc0814
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.22
@@ -0,0 +1,45 @@
+Changes since version 3.21
+
+New answers:
+ +Label inlgrphapp: inline code to standalone graphics (new: gmp, mpgraphics)
+ +Label inst-texlive: install a package from TeX live
+ +Label startup: getting started with (La)TeX
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label archives: redo and update for 2 CTAN archives, cover mirror.ctan.org
+ +Label codelist: updated and reformatted
+ +Label drawing: removed inline code stuff to +inlgrphapp
+ mention XeTeX driver for pstricks
+ +Label dtx: mention sty2dtx
+ +Label findfiles: a more uniform description of what happens
+ +Label fontsize: deal with omissions from fix-cm
+ +Label hash: describe command-defs-within-commands in LaTeX syntax, too
+ +Label logos: mention hologos, metalogo
+ +Label ltxcmds: show use of (la)texdef package
+ +Label luatex: correct pdfTeX version number, add links to distributions
+ +Label man-latex: add CTAN reference for "Getting something out of LaTeX"
+ +Label mathml: expand font details to all known current free maths fonts
+ +Label mpprologues: mpsproof.tex has now moved on the archive
+ +Label oddpage: clarify use of \ifoddpage for LaTeX users
+ +Label pdftexgraphics: describe use of auto-pst-pdf
+ +Label psfchoice: discuss MathTime Pro 2 Lite fonts
+ +Label scriptfonts: mention rsfso, mnsymbol, mathabx and urwchancal
+ +Label struttab: describe use of makecell
+ +Label textrace: offer mf2pt1 (about time, too!)
+ +Label uploads: general update, including mirroring technologies
+ +Label xetex: add link to documentation
+ +Label xfigetc: replace link for jfig
+
+Deleted answers:
+ <none>
+
+Web interface, etc.:
+ Work on a slightly more sane layout is under way, but not yet in a
+ shape to be released
+ Since the start of March 2011, "last edited" tags have been added to/updated
+ in answers that have changed
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.23 b/help/uk-tex-faq/CHANGES-3.23
new file mode 100644
index 0000000000..47449bc125
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.23
@@ -0,0 +1,50 @@
+Changes since version 3.22
+
+New answers:
+ +Label book-lists: redirector to the dismembered parts of old "label books"
+ +Label ctan: summary of the salient points of the archives
+ +Label catalogue: outline of the CTAN catalogue
+ +Label latex-books: the LaTeX part of old "label books"
+ +Label other-books: the miscellanea from old "label books"
+ +Label subdepth: getting even subscripts in your maths
+ +Label tex-books: TeX and Plain TeX part of old "label books"
+ +Label type-books: typesetting part of old "label books"
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label altabcr: error can be caused by insufficient columns in a matrix
+ +Label clsvpkg: rewritten with a LaTeX 2e perspective (rather than 2.09)
+ +Label context: add detail following Hans Hagen's outline in Tugboat 100
+ +Label destable: more details of caption above table
+ +Label doc-dirs: correct link to TUG India tutorials page
+ +Label drawing: link to intro doc on pgf/TikZ, and sparse docs of DraTeX
+ +Label gethelp: rewritten for (slightly) improved clarity
+ +Label hyphen: LuaTeX's hyphenation pattern loading is different
+ +Label keyval: references to expl3, xpackages replaced with l3* versions
+ keyval: mention getoptk
+ +Label labelfig: mention pst-layout; mention that pgf/TikZ is also capable
+ +Label latex2e: mention "frozen" state
+ +Label latex3: references to expl3, xpackages replaced with l3* versions
+ +Label latexqual: mention lacheck
+ +Label luatex: "clarify" statement about future changes to PDFTeX
+ luatex: updated versions mentioned; MikTeX now offers LuaTeX
+ +Label MF: mention sidelining of Metafont in the modern world
+ +Label patch: use letltxmacro where necessary
+ +Label RCS: mention gitinfo
+ +Label texthings: clarify description of luatex
+ +Label tfm: XeTeX and LuaTeX don't need TFM files
+ +Label underscore: \_ in OT1 encoding is bad news
+ +Label useMF: a step in removing archaic baggage from this answer
+
+Deleted answers:
+ +Label books: dismembered to produce the new *-books above (the
+ label is now redirected to book-lists)
+
+Web interface, etc.:
+ A small change to the HTML generation has (to the author's eye)
+ improved the appearance of pages on the web. There remain problems
+ in this area, despite the improvement.
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.24 b/help/uk-tex-faq/CHANGES-3.24
new file mode 100644
index 0000000000..9217a662a4
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.24
@@ -0,0 +1,41 @@
+Changes since version 3.23
+
+New answers:
+ +Label labelcount: use the "value" of a label in counter operations
+ +Label optclash: LaTeX package options clash
+ +Label printvar: print the contents of a "variable"
+ +Label unicode: "Unicode for TeX users"
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label bug: reworded in the light of more on-line help available
+ +Label dvi: tidied, mention of XeTeX and its XDV format
+ +Label ECfonts: brought up to date (a bit: more remains to be done)
+ +Label editors: updated comments about TeXworks
+ +Label include: clarification of page number constraint
+ +Label LaTeX3: add git repository link, mention state of formats
+ +Label latex-books: add "LaTeX Beginner's Guide" and Herbert Voss's UIT books
+ +Label mathml: outline the use of MathJax
+ +Label missbegdoc: rewritten to take account of the BOM issue
+ +Label multind: add amsmind and imakeidx packages
+ +Label music: reflect restructuring of fonts
+ +Label sysmac: mention root privilege requirement for MacTeX
+ +Label sysother: discourage any hope of a current VMS version
+ +Label tds: toned-down and untangled the text, a bit
+ +Label texthings: mention ProTeXt among distributions
+ +Label TUG* corrected contact details
+ +Label tutbitslatex: revise statement about Herbert Voss's mathmode book
+ incorporate para about TUG India tutorials from doc-dirs
+ +Label underline: remove obsolete statement about ulem docs
+ +Label virtualfonts: rewrite, improving clarity (I hope...)
+ +Label wordcount: add health warnings for detex-like counts
+
+Deleted answers:
+ +Label doc-dirs: subsumed in label tutbitslatex
+
+Web interface, etc.:
+ <no changes>
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.25 b/help/uk-tex-faq/CHANGES-3.25
new file mode 100644
index 0000000000..766f3062f3
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.25
@@ -0,0 +1,47 @@
+Changes since version 3.24
+
+New answers:
+ +Label includeother:LaTeX refuses to \include from (some) other directories
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label acrobat: Rearranged and extended somewhat (dropped V-TeX details)
+ +Label bibinline: Outline use of the new usebib package
+ +Label citesort: Show how to do the job with biblatex
+ +Label cmdstar: Suggest use of xparse for *-commands
+ +Label crossref: Clarified wording, and removed incorrect "effect" of error
+ +Label eqnarray: Added link to Stefan Kottwitz blog entry on the problem
+ +Label euro: Updated note about using marvosym font
+ +Label extrabrace: Some clarification (and a new solution)
+ +Label filesused: Discuss mkjobtexmf
+ +Label findfont: Rewritten, downplaying Metafont and covering TTF and OTF
+ +Label footintab: Discuss tablefootnote package
+ +Label i18nbib: BibLaTeX is another candidate
+ +Label inlgrphapp: Add picture environment to list, mention picture package
+ +Label isitanum: Improve \testnum definition
+ +Label labelfig: Describe pinlabel package
+ +Label man-latex: Correct link to Chris Harrison's (now) tutorial;
+ Mention van Dongen's, Wilkins' and Buxbaum's offerings
+ +Label marginpkgs: Discuss zwpagelayout
+ +Label mfptutorials:Restore (lost) link to MetaFun manual
+ +Label noroom: Mention morewrites for lots of (pretend) output streams
+ +Label papergeom: Outline use of zwpagelayout package
+ +Label ref-doc: Added reference to macros2e document
+ +Label slashbox: Recommend diagbox package in preference to slashbox
+ +Label syswin32: Miktex 2.9 no longer beta ... so catch up!
+ +Label tutbitslatex:Rearrange stuff on pgf/tikz, after new management of site
+ +Label tutorials*: Changed question title to "... TeX-based systems"
+ +Label usesymb: Add fdsymbol, mdsymbol
+ +Label verbwithin: Suggest "v" argument type of xparse
+ +Label watermark: Discuss xwatermark and use of pdftk
+ +Label whatengine: Sort out erroneous wording, correct HTML of example code
+
+Deleted answers:
+ <none removed>
+
+Web interface, etc.:
+ <no changes>
+
+Robin Fairbairns
diff --git a/help/uk-tex-faq/CHANGES-3.26 b/help/uk-tex-faq/CHANGES-3.26
new file mode 100644
index 0000000000..ed71bfd11e
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.26
@@ -0,0 +1,59 @@
+Changes since version 3.25
+
+New answers:
+ +Label expl3-old: package needs a newer LaTeX 3 harness
+ +Label latex3-prog: learning LaTeX 3 programming
+ +Label repeat-num: repeat an operation a given number of times
+ +Label repeat-set: repeat an operation for each element of a set
+ +Label whatenv: brief outline of what environments are
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label acrobat: [tidying layout]
+ +Label archives: largely rewritten for "new" archive arrangements
+ +Label chapbib: show biblatex-based approach
+ +Label codelist: more on use of minted package
+ +Label complist: clarified description of "what's going on"
+ +Label cmdstar: clarified use of LaTeX 3, here
+ +Label conditional: suggest stampinclude for rapid (partial) compilation
+ +Label ctan: revised following recent changes to archive access
+ +Label dolldoll: elaborated "reasons" from a tex.stackexchange answer
+ +Label dpfloat: describe use of caption package for the job
+ +Label drawing: reword text about PGF/TikZ
+ +Label extsizes: describe use of scrextend package for document font sizes
+ +Label ftncapt: clarify example
+ +Label hyphenaccents: the "future" (unicode hyphenation tables) is here!
+ +Label ltxcmds: more detail of the latexdef application
+ +Label latexqual: add a proviso about l2tabu/nag
+ +Label make: add recommendation for arara
+ +Label man-latex: Nicola Talbot's stuff has moved to a new web site
+ +Label minxampl: discuss support packages
+ +Label nofm: suggest zref-lastpage
+ +Label oddpage: suggest the ifoddpage package
+ +Label patch: describe the regexpatch package
+ +Label pkgdoc: mention the site texdoc.net, miktex mthelp
+ +Label pdftexgraphics: mention pdftricks2
+ +Label psfchoice: update mathdesign outline, add newtx and garamondx
+ +Label readML: Context can do the job (rather well, one understands ;-)
+ +Label readtex: suggest asking for a PDF instead ;-)
+ +Label spell: update, add recommendation for (exptl) spelling package
+ +Label struttab: removed internal macros in example of cellspace
+ +Label symbols: rearrange, and mention unicode maths symbol table
+ +Label tocloft: mention new (straightforward) etoc package
+ +Label uploads: rewritten for the (new) archive arrangements
+ +Label vertspacefloat: moved to a new location in question list
+ +Label virtualfonts: change question "title" to be a question
+ +Label xetex: change question "title" to match other projects' titles,
+ redo answer, based on a tex/sx post
+
+Deleted answers:
+ <none removed>
+
+Web interface, etc.:
+ The "default archive" (used in links from answers) is now mirror.ctan.org
+ (i.e., it's not an archive, but a selector of a mirror of the archive)
+
+Robin Fairbairns
+Hapless FAQer of Cambridge
diff --git a/help/uk-tex-faq/CHANGES-3.27 b/help/uk-tex-faq/CHANGES-3.27
new file mode 100644
index 0000000000..f41f88cfa0
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.27
@@ -0,0 +1,43 @@
+Changes since version 3.26
+
+New answers:
+ <none yet>
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label buffovl: link to ghostscript and gsview homes, not CTAN
+ +Label catalogue: editorial clarification
+ +Label cmdstar: [tidying layout]
+ +Label commercial: remove mention of the (defunct) Textures distribution :-(
+ +Label dolldoll: editorial tidy (un-knotting tortuous text)
+ +Label dtx: suggest dtxgen
+ +Label dvipdfmgraphics: link to ghostscript home, not CTAN
+ +Label editors: add texstudio (to texworks) in list
+ +Label fontsize: recommend anyfontsize package, too
+ +Label footintab: clarify "table in minipage" (should have been "tabular")
+ +Label latexbug: removed "upload latex bug by email" (no longer available)
+ +Label luatex: revised for updates from the project, and clarified
+ +Label make: add arara and try; add vpp to ctan links list
+ +Label man-latex: two more links to "Dickimaw" books
+ +Label notWYSIWYG: rewritten after a bit of historical research
+ +Label osf: \oldstylenums does use bold face to match surrounding text
+ +Label otherprinters: link ghostscript home, not CTAN
+ +Label previewers: link ghostscript home, not CTAN
+ +Label psfchoice: mention newpx, give CTAN links for URW fonts in newpx,newtx
+ +Label pspreview: link ghostscript, gsview home, not CTAN
+ +Label recovertex: link ghostscript home, not CTAN
+ +Label repeatgrf: link ghostscript home, not CTAN
+ +Label scriptfonts: removed mention of ghostscript, add tg-chorus
+
+Deleted answers:
+ -Label y2k: removed as no longer relevant
+
+Web interface, etc.:
+ A statement of the FAQ's (PD) licence is shown in the introduction.
+ Now use standard glyph for arrows, rather than "hyphen-greater"
+ Translate \beta and \pi to greek letters rather than the letters' "names"
+
+Robin Fairbairns
+Hapless FAQer of Cambridge
diff --git a/help/uk-tex-faq/CHANGES-3.28 b/help/uk-tex-faq/CHANGES-3.28
new file mode 100644
index 0000000000..29409bb0a0
--- /dev/null
+++ b/help/uk-tex-faq/CHANGES-3.28
@@ -0,0 +1,66 @@
+Changes since version 3.27
+
+New answers:
+ +Label centre-flt: deals with center environment around a float
+ +Label cpy-srchpdf: replaces label srchpdf, and covers copying text, too
+ +Label getnff: support for fonts "not allowed" in distributions
+ +Label lollipop: restored entry, given new maintainer
+ +Label ltx-csv: how to deal with CSV files in LaTeX
+ +Label otf-maths: typeset maths using OpenType fonts
+ +Label parmoderr: about the error "not in outer par mode"
+
+Relabelled answers:
+ <none>
+
+Revised answers:
+ +Label bibtexing: link to www.bibtex.org
+ +Label boldgreek: clarify some really old text
+ +Label catalogue: update in light of new www.ctan.org
+ +Label clsvpkg: clarify some distinctions
+ +Label cmdstar: \makeatletter was incorrectly placed in example
+ +Label commercial: remove entry for Micropress, Inc (once vTeX suppliers)
+ +Label conditional: discuss use of the tagging package
+ +Label context: editorial (for better relation to reality, one hopes ;-)
+ +Label custbib: discourage "beginners" from attempting biblatex styles
+ +Label dtx: add discussion of generating output from the files
+ +Label filesused: change reference from teTeX to TeX-live(!)
+ +Label findfont: tidy, add more reference details
+ +Label gethelp: add reference to TeX/StackExchange "starter" summary
+ +Label hyphexcept: deal, perfunctorily, with Unicode hyphenation
+ +Label hyphoff: editorial change only
+ +Label nohyph: {ditto}
+ +Label labelfig: discuss pdfrack
+ +Label latexandplain: re-write -- previous version seemed not to help, much
+ +Label latextoplain: re-dump my mental image of what goes on ... looks better
+ +Label ltxcmds: clarification (editorial changes only)
+ +Label makeindex: further work on xindy description
+ +Label mfptutorials: remove one dead link, refer to Voipio's TUGboat papers
+ +Label mp: MetaPost can also create SVG output
+ +Label music: update discussion of lilypond, and mention lilyglyphs pkg
+ +Label normalszmiss: rewritten (a simple answer is difficult to write "well"!)
+ +Label numbersets: add boondox, newpx and newtx fonts as a potential source
+ +Label oldfontnames: tidied up
+ +Label papergeom: remove special case for vTeX
+ +Label plninltx*: clarification (editorial changes only)
+ +Label psfchoice: provide link to +otf-maths
+ +Label readtex: add a bit about using on-line LaTeX servers
+ +Label slidecls: mention a beamer gallery linked from post in TeX/sx
+ +Label spell: suggest hunspell (which is even part of recent MacOS X)
+ +Label sysother: remove references to vTeX
+ +Label sysunix: remove mention of MikTeX/Unix, and references to vTeX
+ +Label tocloftwrong: add actual answer (as well as reference to answer...)
+ +Label usepictex: remove reference to vTeX
+ +Label verbwithin: suggest newverbs, verbatim box-writing (tcolorbox,verbatim)
+ +Label whereFAQ: remove link to texnik.de
+ +Label xspace: clarify, play down the value of the command
+
+Deleted answers:
+ +Label srchpdf: replaced by answer labelled cpy-srchpdf
+
+Web interface, etc.:
+ Links in the section at the end of each answer now go via the mirror
+ selector mirror.ctan.org (previously all links went via the Cambridge
+ CTAN node).
+
+Robin Fairbairns
+Hapless FAQer of Cambridge
diff --git a/help/uk-tex-faq/ChangeLog b/help/uk-tex-faq/ChangeLog
new file mode 100644
index 0000000000..7eca576bcd
--- /dev/null
+++ b/help/uk-tex-faq/ChangeLog
@@ -0,0 +1,17802 @@
+2014-06-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * texfaq2html: tidy blank lines
+
+ * sanitize.pl: a few changes from -beta
+
+ * gather-faqbody.tex: new version
+
+ * faq-intro.tex:
+ * faq-mac-prog.tex
+ * faq-wdidt.tex:
+ * add-general.tex: \nothtml{\noindent}!!!
+
+2014-06-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-conditional): mention the tagging package
+
+2014-06-03 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-dtx): first stab at description of "using" a
+ .dtx/.ins combination to produce packages and docs
+
+2014-05-30 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-latextoplain): clarification (i hope!)
+
+ * faq-backgrnd.tex (q-context): attempting a better path for beginners
+
+2014-05-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-readtex): dash off ref to online compilers
+
+2014-05-18 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-t-g-wr.tex (q-oldfontnames): historic stuff cleared away,
+ slight rewording
+
+2014-05-07 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-makeindex): work on description of using xindy
+
+ * sanitize-beta.pl (sanitize_line): add \luatex and \lualatex
+
+ * faq.sty: add \luatex and \lualatex
+
+2014-05-02 Robin Fairbairns <rf10@cl.cam.ac.uk> ron.cummins@gmail.com
+
+ * faq-biblio.tex (q-custbib): discourage beginners from attempting
+ their own biblatex style; editorial
+
+2014-04-25 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: restore lollipop (w/cat link)
+
+ * faq-backgrnd.tex (q-lollipop): renew, from add-general
+
+2014-04-23 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: drop fonts/armenian (fonts now part of armtex)
+
+ * add-general.tex (q-lollipop): recreated entry for lollipop
+
+2014-04-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-cmdstar): bug fix from javier mora
+
+2014-03-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-getit.tex (q-findfiles): editorial
+
+2014-03-18 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-catalogue): yet another iteration
+ (q-context): typos
+ (q-latexandplain): rewrite. who knows if it's worth it...
+
+2014-03-17 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-catalogue): 2 iterations towards
+ comprehensibility
+
+2014-03-14 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-latex-books): sort out html of more math into latex
+ (still not terribly good, but no more actual latex...)
+
+2014-03-05 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-getnff,q-otf-maths): removed as already in main
+ (q-outer-err): removed, similarly
+
+2014-03-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex: missing close brace
+
+2014-02-18 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-mfptutorials): add links to the voipio papers,
+ and remove the (dead) one to Heck's
+
+2014-02-16 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex (q-pdfpagelabels): add {} to a \dots call
+ (q-cpy-srchpdf): deal with broken parens
+
+2014-02-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex: remove q-ltx-csv (now in faq-mac-prog)
+
+2014-01-31 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-biblio.tex (q-custbib): typo
+
+2014-01-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): remove {} from pattern \\The{}\{\} ?
+
+2014-01-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-gethelp): warning of abrasiveness on tex/sx
+
+2014-01-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (Q-filesused): convert tetex ref to texlive-unix(!)
+
+2014-01-22 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-dropping): remove ref to vtex
+
+ * faq-graphics.tex (q-labelfig): remove refs to vtex
+
+ * faq-hyp+pdf.tex (q-acrobat): remove ref to vtex
+
+ * faq-t-g-wr.tex (q-usepictex): root out reference to vtex
+
+ * faq-fonts.tex (q-otf-maths): new, from add-general
+ (q-psfchoice): editorial, incl reference to q-otf-maths
+
+2014-01-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-getit.tex (q-findfont): tidy, and fill in missing holes
+
+2013-12-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-mp): mp output may be svg, too
+
+2013-12-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-numbersets): add boondox as a source, mention
+ newpx, newtx as preferable to pxfonts/txfonts
+
+2013-11-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-cap-out-flt): new error answer
+
+2013-11-27 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-whattex): reworded for clarity
+
+2013-11-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-xspace): play the command down (after reading a post
+ on tex/sx by david carlisle, tidy the whole question.
+
+2013-11-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-normalszmiss): rewritten. not easy to do, without
+ sounding patronising
+
+2013-11-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-install.tex,faq-biblio.tex: editorial (% signs)
+
+ * faq-wdidt.tex (q-center-flt): new, from add-general
+
+ * sanitize-beta.pl (sanitize_line): move \textpercent{} to immediately
+ below "dump comments" code
+
+ * faq-adj-types.tex (a-outszwrng): braces after \textpercent
+
+2013-11-05 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-inputenc): show structure of multiple-encoding docs
+
+2013-10-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-linespace): editorial
+
+2013-10-22 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-getnff): new, from add-general
+
+ * add-general.tex (q-getnff): mention distinction between -sys and
+ user versions of the script
+
+2013-10-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): mention verbatim writing using
+ tcolorbox and moreverb (and mention the comments in the doc of
+ verbatim, for diy enthusiasts).
+
+ * faq-intro.tex: add martin garrod to the list, mark drucbert deceased
+
+ * faq-bits+pieces.tex (q-clsvpkg): remove duplicate "report" (!)
+
+2013-10-18 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-catcodes): doodling with better explanation
+ (not got very far)
+
+ * faq-docs.tex (q-latex-books): reference digital version of tlc2
+
+ * FAQ-wdidt.tex (q-verbwithin): typo (extra closing paren)
+
+2013-10-15 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-bibtexing): mention www.bibtex.org
+
+2013-10-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): provide link to minimals (even though
+ it's not the neatest of web sites...)
+
+2013-10-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add context-contrib
+
+ * faq-backgrnd.tex (q-context): edited for more realism re. ctan
+
+ * faq-getit.tex (q-findfiles): rsync is the only mirroring protocol
+
+2013-10-02 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-support.tex (q-spell): weave in hunspell (not on ctan...)
+
+2013-09-27 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-plninltx*): editorial (hoping for clarification)
+ (q-ltxcmds): editorial (again aiming for clarification)
+
+ * faq-adj-types.tex (q-music): typo for \progname
+
+2013-09-25 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-gethelp): change junk edit date to today
+
+2013-09-23 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: makeinfo's moved
+
+ * faq-adj-types.tex (q-music): use of lilyglyphs as option
+
+2013-09-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-nohyph): minor editorial
+ (q-hyphoff): ditto
+ (q-hyphexcept): editorial, add a bit of text discussing unicode
+ hyphenation
+
+2013-09-13 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * gather-faqbody.tex: comment out debugging stuff
+
+ * faq-docs.tex (q-gethelp): mention tex/sx "getting started" page
+
+2013-09-11 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: pgf dir is actually the base above graphics/pgf
+ add cat link for picinpar
+ * faq-mac-prog.tex (q-ltx-csv): new, from add-general
+
+2013-09-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-parmoderr): new, from add-general
+
+ * add-general.tex (q-parmoderr): tweaks for clarification
+
+2013-08-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-overstrike): suggest pdfcomment
+
+ * dirctan.tex: add pdfcomment
+
+2013-08-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-mathlips): sort out refs to yhmath (now in just
+ the one place on ctan
+
+ * dirctan.tex: add belleek (from broken filectan entry)
+
+ * faq-hyp+pdf.tex (q-cpy-srchpdf): extended replacement for q-srchpdf
+
+ * dirctan.tex: add mmap, belleek; remove one of the verbdef entries
+
+2013-08-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-intro.tex: editorial
+
+ * faq-wdidt.tex (q-tocloftwrong): missing brace
+
+2013-08-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: remove duplicate of verbdef
+
+2013-07-18 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: tidy up copies
+
+ * faq-texsys.tex (throughout): remove vtex
+ (q-sysunix): purge mention of unix miktex
+ dirctan.tex: remove biolinum
+
+2013-07-17 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-slidecls): link to beamer theme gallery
+
+2013-07-15 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-papergeom): no more vtex
+
+ * faq-texsys.tex (q-sysother): expunge reference to vtex
+
+2013-07-14 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-tocloftwrong): give answers as well as reference!
+ (needs some reference to koma-script)
+
+2013-07-12 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-labelfig): add text discussing pdfrack
+
+ * dirctan.tex: add pdfrack
+
+2013-07-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-clsvpkg): editorial
+
+2013-07-02 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-whereFAQ): remove voss's texnik.de (no longer there)
+
+2013-06-25 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-eplain): editorial
+ (q-whyfree): editorial on licence issues
+ (q-tug*): tidy conditional sections
+
+2013-06-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add verbatimbox
+
+ * faq-wdidt.tex (q-verbwithin): add bullet item about verbatimbox
+
+2013-06-17 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): flagged potential need for context
+ minimals; this file is wildly different to its supposed rcs copy...
+ needs review when i've learnt more about minimals
+
+2013-06-12 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faqbody.tex: version 3.28, today
+
+ * faq-symbols.tex (q-boldgreek): largely rewritten, with more detail
+ about the reasons for the acrobatics needed (also remove incorrect
+ assertion about amsmath and \mathbf)
+
+2013-06-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): newverbs helps -- like verbdef, etc
+
+ * dirctan.tex: add newverbs
+
+2013-06-07 *** Release 3.27 ***
+
+2013-06-06 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-otf-maths): minor tweak
+
+ * faq-install.tex (q-what-TDS): editorial
+
+2013-06-05 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-scriptfonts): mention tgchorus
+
+ * faq-wdidt.tex (q-dolldoll): editorial clarification (hopefully...)
+
+2013-06-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add anyfontsize, remove ghostscript, gsview,
+ correct polyglossia
+
+ * faq-mac-prog.tex (q-fontsize): editorial, incorporate
+ anyfontsize package
+
+2013-06-03 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-notWYSIWYG): flesh out, note demise of textures,
+ editorial
+
+ * texfaq2html-beta: ignore intro by scanning file for \end{introduction}
+
+ * faq-jot-err.tex (q-buffovl): editorial
+
+ * faq-graphics.tex (q-labelfig,q-repeatgrf,q-dvipdfmgraphics): gs
+ from web
+
+2013-05-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex (q-hyper, q-acrobat): tidies, gs from web
+
+2013-05-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-psfchoice): add URW base35 in their own right
+ to discussion of txfonts
+
+ * faq-graphics.tex (q-mpprologues): href for ghostscript
+ (q-labelfig): href for gsview
+
+ * faq-fonts.tex (q-psfchoice): href for ghostscript
+
+ * faq-dvi.tex (q-otherprinters): href for ghostscript
+
+2013-05-24 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * texfaq2html: minuscule changes from -beta
+
+ * sanitize.pl (sanitize_line): minuscule changes from -beta
+
+2013-05-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-texfuture): end date for luatex 2014 (i think)
+
+ * sanitize-beta.pl (sanitize_line): add entity xlations for \beta, \pi
+
+ * faq-projects.tex (q-luatex): update somewhat
+
+ * faq-backgrnd.tex (q-ctan): editorial
+ (q-catalogue): editorial
+ (q-y2k): commented out (no longer relevant)
+
+2013-05-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-editors): reword mention of texworks, add texstudio
+
+2013-05-14 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-osf): \oldstylenums _does_ use bold style
+
+2013-05-13 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add try
+
+ * faq-how-do-i.tex (q-make): add try
+
+ * faq-backgrnd.tex (q-catalogue): editorial
+
+2013-04-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-intro.tex: added subsection about licence
+
+2013-04-23 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-mpprologues): untangle some prose. slightly.
+
+2013-04-22 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-pspreview): ghostscript, gsview from web
+ (q-psfchoice): remove ghostscript mention in discussing urw fonts;
+ reference newpx from pxfonts, and newtx from txfonts, add urw-base35
+ to ctanrefs as locations of palladio and NimbusRomanNo9
+
+2013-04-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-dvi.tex (q-dvi-bmp): typo
+
+2013-04-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-buffovl): ghostscript and gsview from the net
+
+2013-04-17 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add dtxgen
+
+ * faq-bits+pieces.tex (q-dtx): mention dtxgen
+
+ * faq-projects.tex (q-luatex): revise version statement, editorial
+
+2013-04-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-commercial): remove bluesky :-(
+
+2013-04-16 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-recovertex): munge ghostscript refs, remove it
+ from ctanrefs
+
+ * faq-dvi.tex (q-dvi-bmp): editorial
+
+ * add-general.tex (q-tangle-weave): editorial, link to doc of web2c on
+ tug site
+
+2013-04-12 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-fmtconv): tidy, re-organise
+
+2013-04-11 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-readML): correct a \Qref call
+
+ * faq-fonts.tex (q-psfchoice): add newpx to the list
+
+ * faq-texsys.tex (q-syswin32): miktex 2.9 (in ctanrefs)
+
+ * faq-dvi.tex (q-otherprinters): reword because gs no longer on ctan
+ (q-previewers): ditto
+
+2013-04-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-scriptfonts): elide mention of ghostscript,
+ since (a) it doesn't add anything, and (b) it's no longer
+ available on ctan
+
+ * dirctan.tex: add newpx
+
+2013-03-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * filectan.tex: remove <ispell>
+
+ * dirctan.tex: add <showexpl>, <ispell>; correct <spelling>; remove
+ <makeinfo>, ghostscript-[gpl|ghostgum]
+
+ * faq-adj-types.tex (q-codelist): add showexpl
+
+2013-03-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-man-latex): add link to nicola's phd and admin books
+
+2013-03-22 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-tangle-weave): new: the basics of web
+
+2013-03-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-make): add ctan link for vpp
+
+2013-03-15 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-dvi): editorial, hoping to clarify
+
+2013-03-11 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-footintab): don't suggest putting a "table" in
+ minipage ... good sense from ulrike fischer
+
+2013-03-08 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): \arrowhyph translate to &#8594;
+
+2013-03-07 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * gather-faqbody.tex: v3.26b, today
+
+ * faq-the-end.tex (q-latexbug): removed "upload bug by email"; editorial
+
+2013-03-05 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-varitoc): start of an answer starting from the
+ ideas of the tableof package
+
+ * faq-adj-types.tex (q-minitoc): editorial
+
+2013-03-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * texfaq2html, texfaq2html-beta, sanitize.pl, sanitize-beta.pl:
+ correct \ctanhref coding (never-used flexibility in early coding
+ had confused me summat rotten)
+
+2013-03-01 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-intro: remove a spurious "<p/>" (huh?)
+
+ * faq-jot-err.tex (q-manymathalph): point out that the problem can also
+ be avoided by using xetex/luatex
+
+ * gather-faqbody.tex: version 3.26a, today (released as beta)
+
+ * faq-mac-prog.tex (q-repeat-num): tone down "tex.ne.prog language"
+ (q-repeat-set): consequential changes to match -repeat-num
+
+2013-02-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-cmdstar): this was buggy; corrected
+
+2013-02-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faqbody.tex: update \faqfiledate
+
+ *** released 3.26 ***
+
+2013-02-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-support.tex (q-spell): editorial
+
+ * faq-fmt-conv.tex (q-readml): question links for context, luatex
+
+2013-02-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-pdftexgraphics): \lastedit
+
+ * faq-adj-types.tex (q-nofm): \lastedit
+
+ * faq-mac-prog.tex (q-latexqual): \lastedit
+
+ * faq-how-do-i.tex (q-dpfloat, q-ftncapt): \lastedit
+
+ * faq-wdidt.tex (q-dolldoll): editorial
+
+ * faq-backgrnd.tex (q-ctan): editorial
+
+ * faq-adj-types.tex (q-codelist): editorial
+
+ * faq-bits+pieces.tex (q-whatenv): editorial
+
+ * faq-jot-err.tex (q-expl3-old): editorial
+
+ * faq-mac-prog.tex (q-repeat-num): editorial
+
+2013-02-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): updates from -beta (not many)
+
+2013-02-15 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): \lastedit outside ctanrefs(!)
+ (q-noline): question title in quotes
+
+2013-02-08 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add arara
+
+ * faq-how-do-i.tex (q-make): add arara
+
+2013-02-07 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * texfaq2html-beta: align with texfaq2html (regular)
+
+2013-02-01 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-projects.tex (q-omegaleph): editorial
+
+ * faq-jot-err.tex (q-expl3-old): editorial (too many parens)
+
+ * faq-how-do-i.tex (q-dpfloat): describe \ContinuedFloat
+
+ * faq-projects.tex (q-xetex): change question title to match others in
+ the section
+
+2013-01-31 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-getit.tex (q-uploads): reflect changed situation
+
+ * faq-backgrnd.tex (q-ctan): reflect changed situation
+
+2013-01-30 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add ucharclasses, xecjk
+
+ * add-general.tex (q-xetex*): new, from an answer in stackexchange
+
+2013-01-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq.sty: add \ctan for all those \acro calls
+
+ * gather-faqbody.tex: file date today. may be near, now...
+
+2013-01-10 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-pkgdoc): mthelp on miktex rather than texdoc
+
+2013-01-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add mwe, blindtext and lipsum
+
+ * faq-docs.tex (q-minxampl): more detail about support packages, etc;
+ editorial
+
+2013-01-04 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-biblio.tex (q-chapbib): show biblatex-based approach
+
+2012-12-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: remove biolinum-type1 (never actually used in a
+ published version...)
+
+ * faq-mac-prog.tex (q-patch): mention regexpatch
+
+ * dirctan.tex: add regexpatch
+
+2012-12-14 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-getit.tex (q-archives): first stab at "new world"
+ (q-uploads): only one upload method, nowadays
+
+2012-12-07 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add spelling
+
+ * faq-support.tex (q-spell): update text, and add spelling package
+
+ * sanitize-beta.pl (sanitize_line): add \^o
+
+2012-12-03 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-spawnprog): editorial
+ (q-hyphen): editorial, ref q-hyphenaccents
+
+2012-11-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-man-latex): omit frivolous comment about uea users
+ being taught by nicola
+ (q-latex3-prog): moved here from faq-mac-prog
+
+2012-11-28 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-conditional): suggest stampinclude
+
+ * dirctan.tex: add commado
+
+ * faq-mac-prog.tex (q-repeat-set): add commado and filesdo
+
+ * filectan.tex: add interface3-doc, expl3-doc
+
+ * faq-mac-prog.tex (q-latex3-prog): new, from stack exchange
+
+2012-11-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-codelist): elaborate on use of minted
+
+ * faq-fmt-conv.tex (q-readml): give context mkiv pride of place
+ (coming from nowhere in the previous release ;-)
+
+2012-11-21 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-center-flt): typo
+
+2012-11-20 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-pdftexgraphics): add pdftricks2
+
+ * faq-adj-types.tex (q-tocloft): mention etoc
+
+ * faq-fonts.tex (q-psfchoice): add garamondx extn to newtx
+
+ * dirctan.tex: add garamondx, pdftricks2; correct pdftricks; remove all
+ "libertine*" except libertine itself; add cat link for newtx
+
+2012-11-19 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-samepage): editorial twiddle
+
+ * faq-adj-types.tex (q-extsizes): caveat text for scrextend, about
+ design (perhaps restructure so as to have just one caveat for both
+ packages)
+
+2012-11-16 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-litprog.tex (q-lit): sort empty link target
+
+ * faq-support.tex (q-texcad): sort empty link target
+
+ * faq-how-do-i.tex (q-vertspacefloat): removed
+
+ * faq-wdidt.tex (q-vertspacefloat): come from faq-how-do-i
+
+ * faq-bits+pieces.tex (q-whatenv): point out args don't propagate to
+ end env code
+
+ * add-general.tex (q-center-flt): new, following q on c.t.t (or summat)
+
+2012-11-15 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * dirctan.tex: add shorttoc
+
+ * add-general.tex (q-shorttoc): new answer (copied from tex/sx)
+
+ * gather-faqbody.tex: v3.26, today (premature...)
+
+2012-11-09 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-expl3-old): new, from add-general
+
+ * faq-docs.tex (q-pkgdoc): mention texdoc.net
+
+2012-11-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-extsizes): show use of scrextend for random sizes
+
+2012-10-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): editorial don't refer to expl3 directly
+
+ * add-general.tex (q-expl3-old): new, about the common error message
+
+2012-10-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * filectan.tex: add memoir-man
+
+ * faq-how-do-i.tex (q-complist): editorial, for clarification, incl
+ pointer to memoir manual section
+
+2012-10-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-biblio.tex (q-usebibtex): editorial (testing macros)
+
+2012-10-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * archive.cfg: use mirror.ctan.org for arch ptrs
+
+ * add-general.tex (q-otf-maths): editorial
+
+2012-10-25 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-otf-maths): started yesterday -- what it says
+
+2012-10-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-psfchoice): change question answered, update listed
+ coverage of mathdesign
+ (q-pspreview): editorial
+ (q-charshift): note now vanishingly unlikely
+
+2012-10-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-bib-trblshoot): new answer, from sx/63852
+
+ * faq-wdidt.tex (q-dolldoll): tidy, on the basis of sx/503
+
+2012-10-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-texsystems): no empty arg to \qref
+
+ * faq-graphics.tex (q-drawing): clarify statements about pgf
+
+ * sanitize.pl (sanitize_line): pick up changes in -beta
+
+ * sanitize-beta.pl (sanitize_line): only one \pictex, with "i" flag
+
+ * faq-bits+pieces.tex (q-virtualfonts): correct href to knuth on vfs
+
+ * texfaq2html-gamma: use label-to-file.pl
+
+ * faq-bits+pieces.tex (q-dvi,q-pk,q-tfm,q-virtualfonts): editorial
+
+2012-10-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-simple-maths): remove refs to libgreek, libertine,
+ biolinum (since libgreek is based on libertine-legacy)
+
+ * faq-fonts.tex (q-psfchoice): libertine-legacy->libertine-type1
+
+ * dirctan.tex: add libertine, libertine-t1, biolinum-t1, remove
+ libertine-legacy
+
+2012-10-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: remove libertine-legacy, add libertine, {}-type1,
+ biolinum-type1
+
+2012-10-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-nofm): zref-lastpage does a LastPage label, too
+
+2012-10-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-gensym): opening out old proto-answer
+
+2012-10-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * patchdates.tex: is this really necessary
+
+ * add-general.tex (q-detknize): probably dead -- mark as such
+
+ * faq-bits+pieces.tex (q-whatenv): new, from add-general
+
+ * faq-backgrnd.tex (q-ctan): tweak description of mirror.ctan
+ (q-whyfree): add closing paren in first sentence!
+ (q-readtex): add a let-out clause at the end ;-)
+
+2012-10-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-ltxcmds): diddle with margins for narrowversion
+
+ * add-general.tex (q-whatenv): basic body of answer complete
+
+ * faq-t-g-wr.tex,faq-docs.tex,faq-graphics.texfaq-how-do-i.tex
+ (throughout): use \pictex{}
+
+ * faq.sty: \pictex so as to avoid typos ;-)
+
+ * filectan.tex: remove l2tabuen, l2tabuen.src
+
+ * faq-docs.tex (q-man-latex): unify reference to l2tabu
+
+ * faq-mac-prog.tex (q-ltxcmds): more examples of the performance of
+ latexdef, for environments
+ (q-latexqual): tone down the dogmatism about l2tabu/nag
+
+2012-10-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-prog-tex): a start on this, too
+ (q-prog-tex): another paragraph
+
+2012-10-05 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatenv): a start...
+
+2012-10-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-poster): update nlct link, add comments giving
+ status of links [CHANGES]
+
+2012-09-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): remove \quotify again (problems
+ with nested quotes)
+
+ * faq-jot-err.tex (q-badhyph): write out effect of \quotify; editorial
+
+ * faq.sty: remove \quotify again (see sanitize reversion)
+
+2012-09-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): process \quotify
+
+ * texfaq2html-beta: open $archive_list from $home (why did it work?)
+
+ * faq.sty: define \quotify (according to hyperversion)
+
+ * faq-jot-err.tex (q-badhyph): modernise markup with \cmdinvoke,
+ \quotify, etc
+
+ * faq-how-do-i.tex (q-hyphenaccents): the future (unicode
+ hyphenation) is here, so cover it (however briefly)
+
+ * faq.sty: suppress font list from pdftex (per heiko's tip on texhax)
+
+ * faq-jot-err.tex (q-optionclash): correct quote env matching
+
+2012-09-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-optclash): clarification, in light of several
+ tex/sx comments on a question there [needs checking!]
+
+2012-09-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * texfaq2html-beta: default_archive now mirror.ctan
+
+ * archive.list: add mirror.ctan.org, remove tug
+
+2012-09-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-multind): editorial
+
+2012-09-03 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-symbols): reorganise, add unimath-symbols
+
+ * add-general.tex (q-nolnerr): new, "no line to end"
+
+2012-09-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-newlineargs): editorial
+
+2012-08-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-view-rot): outline for new answer
+
+2012-08-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fonts.tex: correct doc link for txfontsb
+
+2012-08-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add newtx, references to libertine support, etc.
+
+ * faq-fonts.tex (q-psfchoice): editorial, add text about newtx
+
+2012-07-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-struttab): don't do \cmdinvoke in verbatim!
+
+2012-07-25 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-man-latex): uprate the wiki latex book
+
+2012-07-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-repeat-set): correct typo
+
+2012-07-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-repeat-num): comment-out repeat package (oops!)
+
+2012-07-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-repeat-num): restore para left behind in
+ q-repeat-set when the two were split
+
+ * add-general.tex (q-multiling): lots of editorial, trying not to
+ change sense, except my confusion in thinking polyglossia works with
+ luatex
+
+2012-07-03 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-patch): typo
+
+2012-06-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add dowith
+
+ * faq-mac-prog.tex (q-repetition): add dowith package (probably more i
+ need to write about, but this will do for the time being)
+
+2012-06-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-repetition): new, from add-general
+
+2012-06-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): big thrash toward a releasable thing
+
+ * dirctan.tex: add etextools, etoolbox, datatool, forarray
+
+ * filectan.tex: add repeat
+
+2012-06-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: standardise on libertineOTF as directory name
+
+ * add-general.tex: yet more diddling of list of repeater packages
+
+2012-04-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add ifoddpage
+
+ * faq-mac-prog.tex (q-oddpage): add ifoddpage
+
+2012-04-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-unicode): unicode bundle now ucs; reword text
+ around utf8 inputenc option selection
+
+ * dirctan.tex: libertine now *-legacy and *otf
+
+ * add-general.tex (q-simple-maths): split libertine links to otf, legacy
+
+ * faq-adj-types.tex (q-music): m-tx in ctanrefs
+
+ * dirctan.tex: rename unicode entry->ucs, mtx->m-tx
+
+2012-04-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-ftncapt): clarify example, per note from david c
+
+ * faq-bits+pieces.tex (q-virtualfonts): change title to question
+
+2012-03-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: v 3.25, today
+
+ * faq-wdidt.tex (q-eqnarray): link to kottwitz's tex blog entry
+
+2012-03-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex (q-acrobat): tidying, dragging into 21st century...
+
+ * faq-texsys.tex (q-syswin32): miktex 2.9 no longer beta, and so luatex
+ available on miktex too
+
+2012-03-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): accept \mf, \mp as well as uc vrsn
+
+ * faq.sty: new \mf, \mp, existing uc vrsn each only use initial capital
+
+ * faq-getit.tex (q-findfont): rewritten in rather different style,
+ noting the decline of mf and the appearance of alternate engines
+
+2012-03-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-sysunix): editorial -- clarify that tlmgr works
+ however you install tl
+
+2012-03-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add usebib
+
+ * faq-biblio.tex (q-i18nbib): biblatex does this too
+ (q-bibinline): suggest usebib
+
+2012-03-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-inlgrphapp): add picture environment to list, and
+ mention picture package with it
+
+ * faq-mac-prog.tex (q-printvar): \verb in verbatim sections is silly,
+ and in typeset sections doesn't get translated by process.pl ...
+
+2012-03-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-parmoderr): not in outer par mode
+
+2012-03-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-t-g-wr.tex (q-msxy): mention berthold horn's partial msym
+
+2012-03-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-inputenc,q-fontenc): proof-reading corrections
+ (probably meaning that other questions aren't any longer useful; these
+ questions marked...)
+
+2012-03-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-ltx-csv): \LastEdit tag
+ (q-archives-rev): editorial
+
+ * faq-bits+pieces.tex (q-unicode): editorial clarification
+
+2012-02-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add datatool
+
+ * add-general.tex (q-ltx-csv): new answer on csv lists
+
+2012-02-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-labelfig): editorial work
+
+2012-02-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add macros2e
+
+ * faq-docs.tex (q-ref-doc): add macros2e
+
+2012-02-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add mdframed
+ remove metafont(actually mac-),mctex,mewltx
+
+ * faq-adj-types.tex (q-subsubsub): editorial
+ (q-breakbox): add mdframed as another solution
+
+2012-02-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): xparse arguments for verbatim use
+
+ * sanitize-beta.pl (sanitize_line): get \{, \}, and \[oc]bracesymbol
+ working with numeric entities
+
+ * faq-jot-err.tex (q-includeother): it's \File not \FileName!!!
+
+ * faq-mac-prog.tex (q-whatengine): correct wording, and coding of
+ \ifthenelse example to make it do correct html
+
+2012-02-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-verbwithin): verbatim arg in \NewDocumentCommand etc
+
+2012-02-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-includeother): more editorial expansion
+
+ * faq-biblio.tex (q-citesort): mention biblatex number-comp style
+
+2012-02-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-extrabrace): more rationalisation
+
+2012-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-extrabrace): slip in a \Qref
+
+2012-02-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-install.tex (q-inst-tds-zip): in "that are that's" remove "that's"
+
+2012-02-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-includeother): came from add-general
+
+ * CHANGES-3.25: tags for cmdstar and crossref
+
+ * faq-projects.tex (q-latex3): explain the concept of "harness", tidy
+
+ * faq-mac-prog.tex (q-cmdstar): outline use of xparse to define *-macros
+
+ * faq-wdidt.tex (q-crossref): dang! -- it could never have had a
+ "previous figure number" + other editing
+
+ * faq-how-do-i.tex (q-footintab): move tablefootnotes "further up"
+
+2012-02-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-install.tex (q-install-find): tidying and clarification
+ (q-instmffont): more clarification
+
+2012-02-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq.sty, sanitize-beta.pl: add \LeadFrom
+
+ * faq-adj-types.tex (q-runheadtoobig): include an actual example of
+ using titlesec pkg
+
+2012-01-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add morewrites
+
+ * faq-jot-err.tex: move q-optionclash and q-optclash together, for
+ easier editing
+ (q-noroom): tidies, mention morewrites package
+
+2012-01-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-tutbitslatex): stefan kottwitz runs texample.net,
+ editorial
+
+ * faq-wdidt.tex: odd bits of editorial
+
+2012-01-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-bibtexing): correct parentheses
+
+ * dirctan.tex: add fdsymbol, mdsymbol
+
+ * faq-symbols.tex (q-usesymb): add fdsymbol and mdsymbol with mnsymbol
+
+2012-01-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex: comment on matthias' latest contribution
+
+ * faq-mac-prog.tex (q-isitanum): correct def of \testnum, per matthias
+
+2012-01-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-noroom): circumspection around the numbers of
+ floats that may be reserved
+
+2012-01-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-poster): correct (old) typo
+
+2012-01-03 Robin Fairbairns
+
+ * faq-docs.tex (q-man-latex): add van dongen's, wilkins' and buxbaum's
+ oeuvres
+
+ * dirctan.tex: add latex-course
+
+2011-12-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-pkgdoc): editorial (awful english)
+
+2011-12-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-fontenc): editorial
+
+2011-12-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-numbersets): editorial reducing verbosity
+
+2011-12-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-intro.tex: credit william adams
+
+ * faq-docs.tex (q-man-latex): new link for chris harrison's tutorial
+
+2011-12-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add pinlabel
+
+ * faq-graphics.tex (q-labelfig): mention pinlabel
+
+ * dirctan.tex: add zwpagelayout
+
+ * faq-adj-types.tex (q-papergeom): zwpagelayout usage outline
+ (q-marginpkgs): mention that zwpagelayout is also available
+
+2011-12-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex (q-acrobat): trying to drag into c.21
+
+ * add-general.tex (q-pdf-encr): re-arrange to make clear that pdftk is
+ worth considering
+
+2011-11-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add xwatermark
+
+ * faq-adj-types.tex (q-watermark): add xwatermark, discuss pdftk
+
+2011-11-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add mkjobtexmf
+
+ * faq-how-do-i.tex (q-filesused): discuss mkjobtexmf
+
+2011-11-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add tablefootnote
+
+ * faq-how-do-i.tex (q-footintab): mention tablefootnote
+
+2011-11-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-position): editorial stuff (seems ok, so far)
+
+2011-11-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add diagbox
+
+ * faq-how-do-i.tex (q-slashbox): convert to use diagbox, with slashbox
+ as an also-ran
+
+2011-11-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-position): first more or less complete version
+
+ * faq-docs.tex (q-mfptutorials): restore link to metafun manual
+
+ * faq-symbols.tex (q-euro): update (incl. usage of marvosym)
+
+2011-11-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): memo about csv commands
+
+2011-11-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-tutorials*): change question title to avoid clash
+ with q-tutbitslatex
+ (q-tutbitslatex): remove pTeX tutorial link (seems to have gone)
+
+ * faq-adj-types.tex (q-slidecls): add ctanref for pdfscreen
+
+ * dirctan.tex: add pdfscreen
+
+2011-11-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-detknize): correct link for q-filename
+
+2011-11-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-t1enc): tidy-up: \'e
+ (throughout): remove | except in a \verb command in verbatim env
+
+2011-11-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): add link to context standalone site
+
+ * faq-projects.tex (q-luatex): diddle with version numbers, add web doc
+ link
+
+ *** release 3.24 ***
+
+2011-11-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): add \FontFormat (from -beta)
+
+ * gather-faqbody.tex: today (had hoped to release yesterday)
+
+ * faq-adj-types.tex (q-music): more tweaking
+
+2011-10-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-music): changes for musixtex-fonts, lots of
+ tweaking following advice from bob tennent
+
+ * gather-faqbody.tex: v3.24, today
+
+2011-10-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-support.tex (q-wordcount): add provisos about detex-like routes
+
+ * faq-jot-err.tex (q-missbegdoc): restore a bit that got dropped
+
+2011-10-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-the-end.tex (q-bug): reword advice on on-line help
+ (q-latexbug): moved _after_ q-bug
+
+2011-10-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-missbegdoc): rewritten to include the bom issue
+ (taking the text of q-missing-begin)
+
+2011-10-26 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * add-general.tex (q-missing-begin): new answer
+
+2011-10-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-unicode): new, from add-general (slight edits)
+
+2011-10-25 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-tds): tone down some of the wilder claims
+
+ * faq.sty: add \FontFormat
+
+ * sanitize-beta.pl: add \FontFormat
+
+ * dirctan.tex: add cm-unicode
+
+ * faq-bits+pieces.tex (q-ecfonts): lots of edits (from work in kent)
+
+2011-10-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-tex-books): clarifying edit ... of a comment ;-)
+
+2011-10-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-mathml): mathtex rather than mimetex in sample!
+
+2011-10-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-mathml): add stuff about MathJax
+
+2011-10-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: correct dvistd, marvosym-fonts
+
+ * filectan.tex: remove varwidth, version
+
+ * dirctan.tex: add varwidth, version
+
+2011-10-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-specials,q-write): minor editorial
+
+2011-10-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-t-g-wr.tex (q-underline): remove statement about ulem docs
+ (saying there's no "real" docs, now false)
+
+2011-10-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-whatmacros): another challenging bit of
+ clarification (hem hem)
+
+2011-10-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-virtualfonts): rearrange and clarify
+
+ * faq-intro.tex: added david epstein to the grand list
+
+ * faq-adj-types.tex (q-algorithms): minor tidy, add comment about
+ algorithmicx (as requested by David Epstein)
+
+2011-10-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-driver,q-pk): tidied
+ (q-tfm): minor editorial
+
+ * dirctan.tex: add dvistd
+
+ * faq-bits+pieces.tex (q-dvi): tidy, mention xetex, ref dvistd
+
+2011-10-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex: editorial
+
+2011-10-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-optclash): new, from add-general
+
+ * add-general.tex (q-inputenc): further iterations towards an answer
+
+2011-10-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-sysmac): mention root requirement for installing
+ mactex
+ (q-sysother): hedge statements about vms tex
+
+2011-10-05 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add enctex
+
+ * faq-intro.tex: talk about the way the set of answers changes
+
+ * faq-wdidt.tex (q-include): clarify page number constraints
+
+2011-10-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-latex3): rehash stuff about acquiring the
+ sources, add comments about using l3 as a format
+
+2011-09-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-fontfmt): typo
+
+2011-09-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-fontfmt): draft replacement for q-adobetypen
+
+2011-09-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-tutorials*): remove link to q-docdirs
+
+ * faq-backgrnd.tex (q-texthings): remove link to q-docdirs
+
+2011-09-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add tex-overview, remove texline, unstar mimetex
+
+ * faq-backgrnd.tex (q-texthings): add protext to discussion of distrs,
+ link to ctan copy of tex-overview
+
+2011-09-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-editors): revise text on texworks
+
+2011-09-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-tug*): contact via web, only; all back tugboat
+
+2011-09-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-tutbitslatex): removed "specialised" from title, add
+ old q-doc-dirs on tug india stuff, adjust statement about voss'
+ mathmode document book form
+ (q-doc-dirs): gone
+
+2011-09-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-multind): describe amsmidx, imakeidx
+
+ * dirctan.tex: add amscls, imakeidx; correct texmacs
+
+2011-09-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-latex-books): add herbert voss's books under latex
+
+2011-09-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-printvar, q-labelcount): add \LastEdit* (oops)
+
+ * faq-docs.tex (q-latex-books): add latex beginner's guide
+
+2011-09-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-ref-doc): patch minor translation effect (\<eol>)
+ (q-doc-wiki): editorial, mostly
+ (q-doc-dirs): a lot more than two in tug india's thing, now
+
+2011-09-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-intro.tex: list Gernot Hassenpflug
+
+ * faq-mac-prog.tex: add q-printvar and q-labelcount from add-general
+
+ * patchdates.tex: updated. this is silly.
+
+2011-09-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex (list of helpers): cite another thing from dan l
+
+ * faq-backgrnd.tex (q-texthings): correct \input texinfo (!)
+
+2011-09-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-keyval): tweak words about getoptk
+ (too late for release...)
+
+ *** Release 3.23 ***
+
+ * texfaq2html, texfaq2html-beta: change "last modified" to "released"
+ in question footers
+
+ * gather-faqbody.tex: change version, date
+
+ * texfaq2html: minor change from -beta
+
+2011-09-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-usemf): further attempts to drag it into c.21
+ (q-keepfonts): modernise and tidy to today's standards
+ (q-getbitmap): modernisation, again
+
+2011-09-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-mp): reword the initial discussion (which had
+ multiple concepts in the same clause, at one point)
+
+2011-08-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-latex3): add l3experimental
+
+ * dirctan.tex: add gitinfo, l3experimental
+
+ * faq-how-do-i.tex (q-rcs): mention gitinfo
+
+2011-08-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-font-fmts): to replace q-adobetypen -- starts
+ with its content (ha ha)
+
+ * faq-bits+pieces.tex (q-adobetypen): editorial
+
+ * faq-how-do-i.tex (q-destable): editorial
+
+ * faq-backgrnd.tex (q-latex2e): describe frozen state; editorial stuff
+
+2011-08-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-scriptfonts): correct typo
+
+ * faq.sty: add \latexo (all lc)
+
+ * faq-symbols.tex (q-underscore): editorial+ref q-activechars
+
+2011-08-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-underscore): drop stuff about \us, add spiel about
+ using T1 and \textunderscore
+ (q-atsign): @ was a special character rather than command
+
+2011-07-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: remove screensty, add cat link for vf-howto
+
+ * faq-fmt-conv.tex (q-toascii): editorial on catdvi, remove screen.sty
+
+2011-07-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-pkgdoc): memoir doc not typo tutorial any more,
+ mention pgf as an example of separately-written stuff
+ (q-writecls): bit of editorial
+
+2011-07-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-optclash): new answer about package options
+
+2011-07-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-etex): correct ref to luatex in disc of context
+ (q-eplain): minute editorial
+
+2011-07-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-clsvpkg): rewrite
+
+2011-07-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-whatmacros): minor editorial
+
+ * faq-projects.tex (q-luatex): update versions, miktex now has luatex
+
+ * faq-bits+pieces.tex (q-tfm): mention xetex and luatex don't need 'em
+
+2011-07-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-keyval): add getoptk
+
+2011-07-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-destable): clarify caption package details for
+ captions above tables
+
+2011-07-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-altabcr): mention limit to sizes of matrices
+
+2011-07-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-whyfree): twiddle discussion of gpl
+ (q-texfuture): reword statement of luatex's release goal
+
+ * faq-docs.tex (q-latex-books): math into latex -> more <ditto>
+
+2011-07-05 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-write): editorial
+ (q-spawnprog): correct typo (epstopf), add cat link for epstopdf at end
+
+ * filectan.tex: add cat link to vf-howto
+
+2011-07-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-mf): caveat about the "modern" sidelining of mf
+
+2011-07-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-ctan): minor editorial
+ (q-dvi): tidy contorted xref
+ (q-ok): preparatory work (may not come to anything)
+
+ * faq-docs.tex (q-symbols): only pdf of symbol list, now
+
+ * filectan.tex: add cat link for metafp
+
+2011-06-29 Robin Fairbairns <rf10@cl.cam.ac.uk>
+
+ * faq-docs.tex (q-doc-dirs): correct tug india link
+
+2011-06-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-patch): recommend letltxcmd for macros with
+ opt arguments
+
+2011-06-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-long-outer): mention getting round \outer w/csname
+ (q-outer-err): new answer pointing to q-long-outer
+
+2011-06-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-includeother): new jot-err answer
+
+2011-06-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): explain difference between mkii and
+ mkiv (from hans' article in tb100)
+
+2011-06-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-latex3): replace expl3, xpackages with l3kernel,
+ l3packages
+
+ * faq-mac-prog.tex (q-keyval): replace expl3, xpackages with l3kernel,
+ l3packages
+
+ * dirctan.tex: remove expl3, xpackages; add l3kernel, l3packages
+
+2011-06-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-hyphen): mention luatex's more relaxed table
+ loading
+
+2011-06-03 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): typos, plus hack on text about dratex
+
+2011-06-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-fontsize): mention cmdunh, cmfib missing from
+ fix-cm
+
+2011-06-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add pst-layout
+
+ * faq-graphics.tex (q-drawing): link to cremeronline intro tutorial
+ (q-labelfig): mention pst-layout, and make reference to similar
+ power of pgf, capable of anything pstricks can do for this problem
+
+ * dirctan.tex: add multido (again...note, different machine)
+
+2011-06-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): add multido
+
+ * dirctan.tex: add multido
+
+2011-06-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex,faq-fonts.tex.tex,faq-graphics.tex,faq-jot-err.tex,
+ faq-jot-err.tex,faq-wdidt.tex,faq-backgrnd.tex,faq-adj-types.tex,
+ faq-bits+pieces.tex,faq-docs (throughout): replace q-books refs as
+ appropriate
+
+ * faq-docs.tex (q-book-lists,q-tex-books,q-latex-books,q-other-books):
+ formed by dismembering the old q-books
+
+2011-05-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-subdepth): new, slightly edited from add-general
+
+ * faq-images.tex: new, for snippets to be served as images
+
+ * sanitize-beta.pl (sanitize_line): add exptl \includegraphics
+
+2011-05-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-luatex): minor editorial to match q-texthings
+
+ * faq-backgrnd.tex (q-texthings): tidy and tweak xetex, rewrite luatex
+ a bit
+
+2011-05-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-gethelp): identify stack exchange before referring to
+ it; don't link to latex project team when saying that the user
+ shouldn't contact them
+
+2011-05-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add unicode
+
+ * add-general.tex (q-inputenc,q-fontenc): new, from q-whatenc
+ (q-unicode) skeleton only, so far
+
+ * faq-bits+pieces.tex (q-hyphen): editorial
+ (q-whatenc): minor editorial, preparing for split
+
+ * dirctan.tex: add cat link for lacheck
+
+ * faq-mac-prog.tex (q-latexqual): mention lacheck
+
+2011-05-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-sansmath): add hfbright to list of things
+
+ * dirctan.tex: add cmbright
+
+2011-05-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-sansmath): currently just a placeholder
+
+2011-05-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-subheight): typo
+
+ * faq-bits+pieces.tex (q-ctan,q-catalogue): new, from add-general
+
+ * faq-docs.tex (q-gethelp): complete replacement from add-general
+ q-gethelp*
+
+2011-05-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-luatex): clarification on "no changes to pdftex"
+ statement
+
+2011-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-gethelp*): (new) rewriting q-gethelp for the "new
+ philosophy"
+ (q-catalogue): further knocking into shape
+
+2011-05-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl: html list-alike environments issue <p/> their end,
+ to cause paragraph style to be invoked
+
+ * faq.sty: require pdf14.sty since thumbpdf has problems otherwise
+
+2011-05-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-latextoplain): undo mess in ctanrefs on web
+
+ *** Release 3.22 ***
+
+ * faq-support.tex (q-xfigetc): add \LastEdit
+
+ * faq-how-do-i.tex (q-struttab): add \LastEdit
+
+ * faq-getit.tex (q-archives): add \LastEdit
+
+2011-05-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-support.tex (q-xfigetc): new link for jfig
+
+ * faq-how-do-i.tex (q-struttab): describe use of makecell package
+
+2011-04-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): minor editorial
+ (q-labelcount): title "counter values" rather than "counters"
+
+2011-04-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: v3.22, today
+
+ * texfaq2html (throughout): tidy p tags
+
+ * sanitize.pl (sanitize_line): line up one comment with -beta
+
+ * dirctan.tex: cat links for ofs, pdcmac
+ remove pfm2afm, penelope, pbm2tex, pbmtopk
+
+2011-04-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-getnff): typo
+
+ * faq-getit.tex (q-archives): correct addresses(!)
+
+ * add-general.tex (q-repetition): modest tidies, detail of \multiput in
+ real text (works!)
+
+ * dirctan.tex: add cat links to a few euro* entries (not euro-fonts...)
+ remove lollipop
+
+2011-04-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-archives-rev): redo in context of q-ctan
+
+2011-04-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: cat link for nonumonpart, remove nrc (not used)
+
+2011-04-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): lots of tinkering
+
+ * dirctan.tex: add forloop
+
+2011-04-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-repetition): new, commands for repeating things
+ (only a skeleton, so far)
+
+2011-04-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-ctan): ref. twg on archives
+ (q-archives-rev): interim version of q-archives to go with q-ctan
+
+2011-04-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-printvar): examples of \printlength
+
+2011-04-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-eplain): qualify statement about "docs online"
+
+ * faq-install.tex (q-privinst): deconfuse emacs source colouring in one
+ or two places
+
+ * faq-backgrnd.tex (q-etex): stop suggesting that etex is context's
+ prime target
+
+2011-04-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-textrace): mention mf2pt1 (about time too)
+
+2011-04-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): tidy-up
+
+2011-04-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): mention pstricks xetex driver
+
+2011-04-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-xml2tex,q-subheight,q-multiling): editorial
+
+2011-04-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-parskip): mention that (some?) koma-script
+ classes have the facility (in spades, by the look of it)
+
+2011-03-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add metalogo
+
+2011-03-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-symbols.tex (q-scriptfonts): editorial
+
+ * add-general.tex (q-outputrtn, q-whatfloats): editorial
+
+2011-03-27 Robin Fairbairns <rf10@battam>
+
+ * add-general.tex (q-simple-maths): add libgreek to ctanrefs, plus a
+ bit of editorial
+
+ * faq-install.tex: editorial
+
+2011-03-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-logos): add text for hologo and metalogo
+
+2011-03-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: correct alphabetical order in one place
+
+ * faq-graphics.tex (q-pdftexgraphics): add auto-pst-pdf
+
+ * sanitize.pl, sanitize-beta.pl: alter pattern for |...| to "=" delims
+
+2011-03-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex: add q-simple-maths
+
+ * dirctan.tex: add mtp2lite, mathastext, cat link for mtx, and
+ libertine, libgreek
+
+ * faq-fonts.tex (q-psfchoice): mention mathtime pro 2 lite
+
+2011-03-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-referencl): new, about referring to enclosing thing
+
+2011-03-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize.pl, sanitize-beta.pl (sanitize_line): align use of + as subs
+ delimiter between the two files
+
+ * dirctan.tex: add texdef
+
+ * faq-mac-prog.tex (q-ltxcmds): mention texdef (neat!)
+
+2011-03-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * filectan.tex: remove mpsproof
+
+ * faq-graphics.tex (q-inlgrphapp): new, from add-general
+ (q-mpprologues): mpsproof now part of \mp{} itself
+
+2011-03-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): remove egplot from link list
+
+ * dirctan.tex: add cat link to gmp
+
+ * add-general.tex (q-inlgrphapp): slight tidy, add egplot to link list
+
+2011-03-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add gmp
+
+ * faq-graphics.tex (q-drawing): remove inline graphics app stuff to new
+ answer q-inlgrphapp
+
+ * add-general.tex: new q-inlgrphapp
+
+2011-03-11 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-attach): new answer, from stackexchange
+
+ * dirctan.tex: add attachfile, navigator
+
+ * faq.sty: add \xelatex
+
+ * sanitize-beta.pl (sanitize_line): add \xelatex
+
+2011-03-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): editorial
+
+2011-03-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-texthings): grinding on through (summary remains)
+
+2011-03-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-texthings): grinding through the lists
+
+ * texfaq2html-beta: initialise $item_extra
+
+ * sanitize-beta.pl (sanitize_line): experimental $item_extra for style
+
+ * texfaq2html-beta: add descr style to inline css
+
+ * sanitize-beta.pl (sanitize_line): a whiff of '"'-sanitisation
+
+ * faq-backgrnd.tex (q-mf): editorial, modernisation
+
+2011-03-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-mp): tidying, tweaking, etc.
+ (q-texthings): regularise various things
+
+2011-03-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-crossref): rewrite and lay out less tortuously
+ (throughout) tidy quote envs
+
+ * faq-t-g-wr.tex (throughout): tidied quote (in one instance only!)
+
+ * faq-projects.tex (q-latex3): sort out unterminated sentence after
+ alert from bruno le floch
+
+ * faq-mac-prog.tex: (throughout): tidied quotes, eliminated short verbs
+
+ * faq-symbols.tex (throughout): tidied quotes
+
+ * faq-how-do-i.tex (q-proof): add QED
+ (throughout): verbatim<->quotes checks
+
+ * faq-lab-ref.tex: verbatim<->quotes, again
+
+ * faq-adj-types.tex (throughout): verbatim/quote check
+
+ * texfaq2html-beta: tweak margins of <ul> (== itemize lists)
+
+ * faq-adj-types.tex (q-codelist): check, update, reformat
+
+2011-03-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex, faq-fonts.tex, faq-install.tex: juggling with
+ verbatim and quotes
+
+ * faq-support.tex: change one verbatim to quoted
+
+ * faq-symbols.tex (q-scriptfonts): add mathabx and urwchancal
+
+ * dirctan.tex: add mpgraphics, mathabx[-type1], urwchancal
+
+ * faq-graphics.tex (q-drawing): mention mpgraphics for inline
+
+2011-03-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-papergeom): slight tidying
+
+ * texfaq2html-beta: add trivial para-margin css
+
+2011-03-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * texfaq2html-beta (throughout): fiddling with html structure
+
+ * faq-backgrnd.tex (q-startup): new, from add-general
+
+ * faq-intro.tex: minor tweaks
+
+2011-03-03 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add asana-math, stix, unicode-math and xits
+
+ * faq-projects.tex (q-mathml): redo unicode maths fonts bit
+
+2011-03-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (q-context): editorial
+ (q-texthings): correct one of 2 texi2pdf, to texi2dvi
+
+ * add-general.tex (q-startup): new answer
+
+2011-02-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-hash): rewrite for both latex and plain forms
+
+ * faq-docs.tex (q-man-latex): add ctanref for "getting something..."(!)
+
+2011-02-25 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add polyglossia
+
+ * add-general.tex (q-multiling): new, on multilingual work, then&now
+
+ * faq-projects.tex (q-luatex): minor updates, add ctan link, correct
+ version no of current pdftex
+
+ * dirctan.tex: add xetexref, luatex
+
+ * faq-projects.tex (q-xetex): add ctan link to will r's doc
+
+2011-02-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-fontsize): mention fix-cm's omissions (and
+ suggest replacements)
+
+2011-02-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add sty2dtx
+
+ * faq-bits+pieces.tex (q-dtx): mention sty2dtx, tidy
+
+ * faq-getit.tex (q-archives): reverse http and ftp "recommendations",
+ remove last trace of reference to usa site
+
+ * faq-bits+pieces.tex (q-fontname): minor editorial
+
+ * faq-install.tex (q-inst-texlive): simple command line instructions,
+ only, for now
+ (q-inst-scut): promote tex live to same level as miktex here
+
+2011-02-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-install.tex (q-inst-texlive): stub for filling in...
+
+ * faq-getit.tex (q-archives): remove refs to tug.ctan.org as a ctan
+ site, update remarks about mirror.ctan.org, etc.
+ (q-uploads): update list of requirements for upload, mention rsync
+ protocol, update suggestions for mirroring
+ (q-findfiles): going over and rationalisation
+
+2011-02-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-labelcount): new, use of refcount package
+
+ * faq-mac-prog.tex (q-oddpage): detail use of changepage, incl use of
+ ifthen pkg for those who don't understand \if<xxx>
+
+2011-02-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add rsfso
+
+ * faq-symbols.tex (q-scriptfonts): mention rsfso
+
+ * sanitize.pl (sanitize_line): updated from -beta
+
+ *** Release 3.21 ***
+
+ * gather-faqbody.tex: today's date (must stop dithering)
+
+2011-02-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-ctan): proposed new answer to replace existing
+ q-archives, or to provide background for a revision of that
+
+2011-02-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-install.tex (q-instt1font): clarify updmap situation (perhaps)
+ (q-inst1cm): minor editorial
+
+ * faq-fonts.tex (q-pspreview): simplify, given that most browsers can
+ do the job on their own, nowadays
+
+2011-02-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-psfchoice): preliminary adjustments
+
+ * sanitize-beta.pl (sanitize_line): add \ttype and \otype
+
+ * faq.sty: add \ttype and \otype, add a few comments
+
+ * faq-fonts.tex (q-usepsfont): a spot more tweaking
+ (subsection{mf fonts}): moved to end of section (was first subsect)
+
+2011-02-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex: remove q-lollipop
+
+ * faq-fonts.tex (q-usepsfont): remove reference to lollipop, tidy
+
+ * dirctan.tex: add lpic
+
+ * faq-graphics.tex (q-labelfig): mention lpic
+
+ * add-general.tex (q-whatfloats): editorial
+ (q-outputrtn): more editorial
+
+2011-02-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-spawnprog): minor editorial
+
+2011-02-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-write,q-spawnprog): new, from add-general
+
+ * faq-mac-prog.tex (q-whatengine): new, from add-general, replaces
+ q-ifpdf
+
+ * dirctan.tex: remove acorn, epson
+
+ * filectan.tex: remove miktex-usb
+
+ * faq-biblio.tex (q-custbib): mention biblatex as an alternative route
+
+2011-02-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-litprog.tex (section{Literate programming}):
+
+ * dirctan.tex: add catalogue ref for ps2pk,ghostscript,gsftopk,fweb and
+ noweb
+ remove all entries for derivatives of noweb (leaving noweb itself...)
+
+ * faq-backgrnd.tex (q-whatpdftex): use \The {} in thanh's name
+
+ * faq-wdidt.tex (q-why-inp-font): \ss -> \ss {}
+
+ * faq-docs.tex,faq-graphics.tex (various): vo\ss -> vo\ss {}
+
+ * faq-how-do-i.tex (q-wholerow): space after \textasciicircum (euch)
+
+ * sanitize-beta.pl (sanitize_line): correct delimiter in pattern that
+ (seems to match) any letter-command name with empty arg [why is that
+ there in the first place?]; also correct \textasciicircum and \ss
+ patterns to require a space at the end (pro tem, at least); add \The
+
+2011-02-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatfloats): editorial tidies prior to moving
+ to main body
+ (q-write and q-write18): editorial, mostly
+
+ * faq-t-g-wr.tex (q-floats): editorial stuff
+
+2011-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add etex-pkg
+
+ * faq-t-g-wr.tex (q-floats): note interaction between morefloats and
+ etex packages
+
+ * faq-projects.tex (q-mathml): lowercase tex4ht in ctanrefs (for
+ consistency with other instances)
+ (q-wygexpts): remove ref to activetex, seems to have disappeared in its
+ original form
+
+ * faq-fmt-conv.tex (q-fmtconv): add web ref to tex4ht dev stuff in
+ ctanrefs for question
+
+2011-01-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-filename): remove the broken code and simply
+ report that "it's not easy" ;-)
+
+2011-01-13 Robin Fairbairns <rf10@battam>
+
+ * add-general.tex (q-write18): new proposed question
+ (q-write): on reflection, we need this preface to q-write18
+
+ * sanitize-beta.pl (sanitize_line): catch up with changes to faq.sty
+
+ * faq.sty: lc versions of \progname, \package and \class
+
+2011-01-12 Robin Fairbairns <rf10@battam>
+
+ * dirctan.tex: add cprotect; remote convert, cortex-email.dir, conrado
+
+ * faq-wdidt.tex (q-verbwithin): mention cprotect
+
+2010-12-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-codelist): extend words about minted/Pygments
+
+2010-12-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatfloats): more fiddling
+
+2010-12-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex: re-do tidies re. bibtex setup
+
+2010-12-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex (q-bibtexing): rewrite to deal with bibtex setup
+
+ * faq-biblio.tex (q-custbib): replace bibtex-doc link with just bibtex
+
+ * dirctan.tex: correct cat link for filehook, add bibtex
+
+ * filectan.tex: correct xampl-bib
+
+2010-12-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatengine): new answer to replace q-ifpdf
+
+2010-12-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-papergeom): update for the various extensions of
+ dvipdfm and rewrite descriptions
+
+2010-12-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-editors): re-ordered, rationalised a bit, removed
+ "wildcard" bullet
+ (q-commercial): clear up debris after removing y&y
+
+2010-12-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-filename): add currfile, mention fink gives way
+
+ * faq-backgrnd.tex (q-texthings): correct typo from yesterday
+
+ * dirctan.tex: add currfile, filehook, restore latex4jed (hah!)
+
+2010-12-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: removed latex4jed, larch, laserjet, since they irritated
+ me and won't ever be used
+
+ * faq-backgrnd.tex (q-texthings}: link to tug.org/levels.html, context
+ executable now texmfstart, i'm told
+
+ * faq-docs.tex (q-ref-doc): the nasa latex thing is no more; remove it
+ and add a ref to karl's thing at gna.org (and on ctan)
+
+2010-12-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-psfchoice): remove text about docs for [pt]xfonts
+ (now available via catalogue), mention bad spacing
+
+2010-12-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatfloats): add sketch of mechanism
+
+2010-11-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): mention asymptote, egplot and emp as
+ inline graphics mechanisms
+
+ * faq-adj-types.tex (q-music): correct "current" musixtex link
+
+ * gather-faqbody.tex: v3.21, today (probably shan't release until after
+ christmas, but...)
+
+ * filectan.tex: remove vertbars (now own dir); simpl-latex now pdf
+
+ * dirctan.tex: add cutwin, vertbars, egplot; biblatex[-contrib] now on
+ m/l/c
+
+ * faq-how-do-i.tex (q-textflow): mention cutwin
+
+2010-11-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-xml2tex): more work on peter f's input
+
+2010-11-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add cat link for html2latex
+
+2010-11-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Format conversions}): new q-xml2tex
+
+2010-11-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-readml): minor editorial
+
+2010-10-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add cat link to catdvi (ho ho)
+
+2010-10-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-mathml): point to tug page in ctanrefs
+
+ * faq-fmt-conv.tex (q-latex2html): add pointer to real tug.org page
+ on tex4ht (hence real location), in ctanrefs
+
+ * filectan.tex: tex4ht now on obsolete
+
+ * dirctan.tex: add memdesign
+
+ * faq-docs.tex (q-typo-style): memdesign rather than memman
+
+2010-10-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-nopagebrk): discuss \pagebreak, \nopagebreak
+
+2010-10-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-whatfloats): a start of a first stab
+
+ * faq-adj-types.tex (q-music): large rehash around musixtex and opustex
+
+2010-10-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-jot-err.tex (q-tmupfl,q-atvert): tidies, incl indent'n of quotes
+
+2010-10-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * filectan.tex: remove morefloats, parskip, path, printlen
+
+ * dirctan.tex: add morefloats, parskip, path, printlen; new location
+ for musixtex-egler
+
+ * faq-jot-err.tex (q-tmupfl): mention morefloats, with caveats
+
+2010-10-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-t-g-wr.tex (q-floats): updated morefloat, mention etex
+ restrictions-regardless-of-number-of-registers
+
+2010-09-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-onna-stick): comment-out the entire question --
+ moot now (i think, but am not _certain_)
+
+ * faq-graphics.tex (q-graphicspath): rephrase discussion of
+ \graphicspath's (potential) problems
+
+2010-09-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-outputrtn): new potential answer
+
+2010-09-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-graphics.tex (q-drawing): mention asyfig, too
+
+ * dirctan.tex: add asyfig and emp
+
+ * faq-graphics.tex (q-drawing): mention emp
+
+2010-09-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: transmute latex-help-texinfo to latex2e-...
+
+ * add-general.tex (q-getnff): new answer for the font installation mess
+
+ * faq-wdidt.tex (q-zerochap): reword for better comprehensibility
+
+2010-09-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fmt-conv.tex (q-fmtconv): add openoffice route for ms-word
+
+2010-09-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-filename): editorial, incl. emphasise latex form
+ of \input, only
+
+2010-09-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+ * filectan.tex: remove cat link from miktex-setup (confusion); remove
+ miktex-usb (no longer needed)
+
+2010-09-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-biblatex): mention bibtex8, refine biblatex/biber
+
+ * dirctan.tex: add bibtex8
+
+2010-09-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add translation for \bibtex
+
+ * faq.sty: add \bibtex
+
+ * faq-projects.tex (q-biblatex): rehash to reflect current realities
+ (biblatex+biber take over the world)
+
+2010-09-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (q-detknize): yet more diddling
+
+2010-08-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-intro.tex: add gregor zattler, anonymise "not covered" comment
+
+ * faq-bits+pieces.tex (q-adobetypen): typo
+
+2010-08-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add fltpage
+
+ * faq-how-do-i.tex (q-dpfloat): mention fltpage
+
+2010-08-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-detknize): printing the contents of a macro
+
+ * faq-docs.tex (q-gethelp): add latex community and stack exchange to
+ the list of places to ask
+
+2010-08-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (q-baselinepar): editorial work ("an quote environ...")
+
+2010-08-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * add-general.tex (q-detknize): rewrite last sentence
+
+ * faq.sty: use tmp/comment.cut instead of comment.sty's default; this
+ is a big win when reading files over nfs, if tmp -> /tmp
+
+2010-08-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * texfaq2html: bring up-to-date from -beta
+
+ * sanitize.pl: bring up-to-date from -beta
+
+ * gather-faqbody.tex: v3.20 (let's live dangerously!), today
+
+ * mk-makefile: add -t option
+
+ [RELEASE 3.20]
+
+2010-08-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex (section improvement; general typos): add siart for
+ correction of q-manymathalph
+
+ * faq-jot-err.tex (q-manymathalph): correct usage of bm
+
+2010-08-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-t-g-wr.tex (subsection{Things "gone away"}): new q-initex from
+ add-general
+
+ * faq-texsys.tex (q-syswin32): comments about miktex 2.9 (beta)
+
+ * add-general.tex (q-initex): further diddling on miktex statement (now
+ woollier still...)
+
+2010-08-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-filename): bug fix for the simple \input patch
+
+2010-08-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add isodoc
+
+ * filectan.tex: add knuth-letter
+
+ * faq-adj-types.tex (q-lettercls): add isodoc and give location of
+ knuth's letter.tex
+
+2010-08-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add present
+
+ * faq-adj-types.tex (q-slidecls): mention present
+
+2010-08-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-extsizes): mention classes with size ranges
+ that differ from the norm
+
+ * add-general.tex (q-initex): reword last para slightly to avoid
+ impression that i know more about miktex than i actually do
+
+2010-08-05 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add lecturer
+
+ * faq-adj-types.tex (q-slidecls): mention lecturer
+
+ * sanitize-beta.pl (sanitize_line): restore old \CONTeXt command
+
+ * faq.sty: add \context command
+
+2010-07-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-fancyhdr): add keywords for fancyhdr
+ (q-reallyblank): correct ref to fancyhdr
+
+2010-07-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * texfaq2file: add $mirror_selector, use extended dirctan, filectan
+ previously developed in texfaq2html-beta
+
+2010-07-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add beamerposter
+
+ * faq-adj-types.tex (q-slidecls): minor editorial
+ (q-poster): add beamerposter
+
+ * faq-intro.tex: add nicola talbot
+
+ * faq-adj-types.tex (q-poster): correct link for nicola's tutorial,
+ tidy link list
+
+2010-07-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-nopagebrk): correct assertion about samepage vs.
+ list items
+
+ * add-general.tex: new answer q-samepage in "why does it do that"
+
+ * faq.sty: add \alltex, \latex, \latexe, \pdflatex
+
+ * sanitize-beta.pl: more of the lower-case bumpy road commands, extend
+ replacement of " by + in substitute commands
+
+2010-07-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (q-fontname): elaborate a bit (why foundries'
+ names don't help)
+
+2010-07-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-fonts.tex (q-metrics): rewrite text around ly1
+
+ * faq-graphics.tex (q-dvipsgraphics): bmeps now part of dktools
+
+ * dirctan.tex: add titleref, dktools; remove bmeps; edit ly1,
+ pdftex-graphics
+
+ * filectan.tex: remove titleref
+
+ * faq-intro.tex: mention moulder in helpers list
+
+ * faq-t-g-wr.tex (q-widows): rewrite with clarification from peter
+ moulder
+
+2010-07-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq.sty: hack around the non-existence of \textcurrency in ptmr
+
+ * dirctan.tex: make revtex ref revtex4-1 (for clarity)
+
+ * faq-biblio.tex (q-mcite): deal with revtex 4.1 situation
+
+2010-06-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add cat link for ite
+
+2010-06-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (generate_CTAN_ref): use $mirror_selector
+
+ * texfaq2html-beta: add $mirror_selector
+
+2010-06-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (q-secnumdep): give actual commands for
+ manipulating secnumdepth and tocdepth, in tocvsec2 and memoir
+
+2010-05-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-mathml): gasp! stix now released
+
+ * dirctan.tex: fontspec moved to m/l/c
+
+ * faq-backgrnd.tex (q-triptrap): sort out paren at end of last para
+
+2010-05-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: del needspace,notoccite,nopageno,optional,underscore
+
+ * dirctan.tex: add needspace,notoccite,nopageno,optional,underscore
+
+ * faq-how-do-i.tex (q-conditional): xcomment now in own dir
+
+2010-05-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (q-footnpp): editorial on perpage vs zref-perpage
+
+2010-05-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (q-mathml): try to sound cheery about stix
+
+2010-05-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add emptypage
+
+ * faq-adj-types.tex (q-reallyblank): mention emptypage package
+
+2010-04-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (q-syswin32,q-sysunix): tl portable
+ (q-sysunix): we do now have reports of tex-gpc running
+
+ * faq-wdidt.tex (q-baselinepar): rewrite, with solutions after each
+ example, and dealing with the business of size change at end par
+
+2010-04-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex (list of contributors): add bob tennent, comment mike
+ vulis
+
+ * dirctan.tex: add classico, sansmath
+
+ * faq-fonts.tex (subsection{Adobe Type 1 fonts}): add entry to list in
+ q-psfchoice for urw classico
+
+ * CHANGES-3.19e: mention above change
+
+2010-04-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \macosx{}
+
+ * faq-texsys.tex (section{TeX Systems}): editorial in q-sysmac,
+ q-sysother
+
+2010-04-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-texsys.tex: diddle with oztex and cmactex stuff in q-sysmac;
+ editorial in q-sysother
+
+2010-04-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add atari-cstex
+
+ * faq-texsys.tex (section{TeX Systems}): various tidies in the various
+ q-sys* answers (removing the last of the description environments)
+
+2010-04-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (section{TeX Systems}): split out 4 sub-answers
+ (q-sys*) from q-TeXsystems, which then becomes (mostly) a list of
+ references
+
+2010-04-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add tex-gpc
+
+ * faq-texsys.tex (section{TeX Systems}): another thrash at windows,
+ incl commenting-out w32tex pending possible developments; amalgamate
+ "unix" and "linux" entries, and add tex-gpc
+
+2010-04-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (section{TeX Systems}): further iteration of windows
+ dists, removing w32tex (which i can't get to at all now) and rehashing
+ text around the miktex/tex live compare and contrast thing
+
+ * faq-getit.tex (q-cd): redo text after thinking about the faq-texsys
+ stuff about windows
+
+2010-04-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \textcurrency, \texteuro
+
+ * faq.sty: add \etex
+
+ * faq-intro.tex: qualify entry for scott pakin in list of the great and
+ good
+
+ * faq-adj-types.tex (q-codelist): correct ctanref for minted
+
+2010-04-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-texsys.tex (section{TeX Systems}): chunk of work on miktex/
+ texlive for windows. needs reviewing before release!!!
+
+ * sanitize-beta.pl (sanitize_line): \tex{} for TeX, similarly for
+ several other tex-variants
+
+2010-04-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add biber
+
+ * faq-projects.tex (q-biblatex): add ctanref to biber
+
+2010-04-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex: add subdocs to q-multidoc (feels dodgy as i write
+ the description...)
+
+ * sanitize-beta.pl (sanitize_line): semicolon at end of \hyperflat(!)
+
+ * texfaq2html: load sanitize.pl not -beta!
+
+2010-04-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq.sty: create skeleton of collecting catalogue entries in ctanrefs
+
+ * faq-adj-types.tex (q-replstdcls): editorial tidies
+
+ * faq.sty: add \hyperflat as long-term replacement for \latexhtml
+
+ * sanitize-beta.pl (sanitize_line): deal with \hyperflat
+
+ * faq-intro.tex (list of contributors): add tomek
+
+ * faq-adj-types.tex (subsection{Alternative document classes}): add
+ blurb about standalone in q-multidoc
+
+2010-04-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add docmute, standalone
+
+ * faq-adj-types.tex (subsection{Alternative document classes}): add
+ docmute in q-multidoc
+
+2010-04-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add docmute, cat link for docmfp
+
+2010-04-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): retitle q-doc-wiki as
+ wiki _books_, bits of editorial
+
+2010-04-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (q-latexwords): typo corrected
+
+RELEASE 3.19d (2nd attempt)
+
+2010-04-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (subsection{Typesetting specialities}): editorial
+ in q-makeindex (including two separate texindex entries in list)
+
+ * dirctan.tex: add catalogue link idxtex to glo+idxtex
+
+2010-04-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html, sanitize.pl: update
+
+ * sanitize-beta.pl (sanitize_line): massive shambles in [lr]brace
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}):
+ correct ref to shortvrb in ctanrefs of q-activechars, and tidy
+ verbatim stuff in 2nd para of answer
+
+2010-04-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (subsection{Alternative document classes}): add
+ example structures for combine and subfiles alternatives in q-multidoc
+
+2010-04-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (section{Current TeX-related projects}): accommodate
+ luatex 0.60.0 in scribble about luatex
+
+2010-04-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: v3.19d, today (to be revised ;-)
+
+ * faq-intro.tex: omit unnecessary stuff in html mode (looks a bit bare
+ now, but ought to improve if/when i can sort out a css for the output)
+
+2010-04-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-intro.tex: minute delta-comment in list of helpers
+
+ * faq-how-do-i.tex: correct typo in q-hyphoff
+
+2010-03-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-graphics.tex,faq-biblio.tex,faq-lab-ref.tex,faq-how-do-i.tex,
+ faq-symbols.tex,faq-mac-prog.tex,faq-t-g-wr.tex,faq-wdidt.tex,
+ faq-jot-err.tex,faq-projects.tex (throughout): add individual cat
+ links for "distributed as part of" ctanrefs
+
+2010-03-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fonts.tex (Macros for using fonts): editorial on some rubbish in
+ q-fonts-pln
+
+2010-03-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (Page Layout): mention pdfcolparcolumns in
+ q-parallel
+ (throughout): add individual cat links for "as part of" ctanrefs
+
+ * dirctan.tex: add minted
+
+ * faq-adj-types.tex (Typesetting specialities): add minted in q-codelist
+
+ * sanitize-beta.pl (sanitize_line): add flatversion in the $ignoring
+ twiddling at the end
+
+ * faq.sty: add flatversion env (== non-hyperversion)
+
+2010-03-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add vruler
+
+ * filectan.tex: remove vruler
+
+ * faq-adj-types.tex (Page Layout): editorial in q-parallel, add own cat
+ entry for pdfcolparallel
+
+2010-03-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add fncylab, ifmtarg, import (hypernat was here already)
+
+ * filectan.tex: remove fncylab, hypernat, ifmtarg, import
+
+2010-03-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * faq-docs.tex: epslatex one ref only, now, relying on catalogue
+
+ * sanitize-beta.pl (generate_CTAN_ref, etc.): generate per reference
+ catalogue entries if opt argument of \CTANref
+
+ * dirctan.tex: add cat link for everypage
+
+ * faq-texsys.tex: editorial to avoid multiple \ctanref per line
+
+ * faq-graphics.tex: single reference to epslatex (doc from catalogue)
+
+ * filectan.tex: remove epslatex_(ps|pdf)
+
+ * dirctan.tex: add epslatex
+
+ * faq.sty: have \CTANref check for following optional argument (and
+ ignore it)
+
+ * faq-adj-types.tex: mention atbegshi in q-watermark
+
+2010-03-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk>
+
+ * dirctan.tex: add framed, verbdef (despite believing it already done!)
+
+ * faq-biblio.tex (subsection{Creating citations}): qualify ctanref for
+ chapterbib in q-chapbib
+
+2010-03-08 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: add threeparttable
+ correct directory for bigstrut (it's multirow)
+
+ * filectan.tex: remove threeparttable
+
+2010-03-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Document management}): try to clear
+ ambiguity about \input in q-filesused
+
+ * Makefile: make "index" opt come out in help
+
+ * dirctan.tex: add framed, verbdef dirs
+
+ * filectan.tex: removed framed, verbdef
+
+2010-02-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: remove excludeonly
+
+ * dirctan.tex: add bigstrut, excludeonly
+
+ * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): remark
+ about docs of tabls and bigstrut now not needed; bigstrut now has own
+ registered directory
+
+2010-02-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add tabls qua directory
+
+ * filectan.tex: remove tabls
+
+2010-02-26 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): correct
+ incompletely edited reference to \PBS in q-tabcellalign
+
+2010-02-24 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * Makefile: add web-index target to updated (dir|file)ctan for when
+ ctan structure is changing
+
+2010-02-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Floating tables, figures, etc.}): remove
+ mention of docs of dpfloat
+
+ * faq-wdidt.tex (subsection{Common errors}): use fix2col package
+ direct, rather than ref to carlisle bundle
+
+ * filectan.tex: remove anonchap, bold-extra, braket, cancel, chngcntr,
+ dblfloatfix
+
+ * dirctan.tex: add anonchap, bold-extra, braket, cancel, chngcntr,
+ fix2col, dblfloatfix
+
+2010-02-18 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-intro.tex (section improvement; general typos): add enrico
+ gregorio (help with q-seccntfmt)
+
+ * faq-mac-prog.tex (subsection{LaTeX macro programming}): redo
+ switching code in q-seccntfmt
+
+2010-02-12 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * texfaq2html-beta: convert (rather smaller number of) entities
+
+ * sanitize-beta.pl (sanitize_line): convert all alphabetic entities to
+ numerical entities
+
+2010-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (section{The Background}): rehash q-texfuture, as
+ suggested by karl berry
+
+2010-02-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): scrunge hyperversion
+
+ * faq.sty: add a hyperversion env
+
+ * dirctan.tex: add knuth-dist
+
+ * faq-backgrnd.tex (section{The Background}): split q-plaintex from
+ q-whattex (controversial?)
+
+ * filectan.tex: add knuth-tds
+
+2010-02-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (section{The Background}): add ctan link in q-etex
+
+ * dirctan.tex: add etex
+
+2010-02-05 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * texfaq2html-beta: an even more abstruse grep command for registering
+ labels than was the old for registering question nos (do we really
+ need to convert + to space? are user-generated questions significant?
+ -- because if not there never will be "xxx + yyy")
+
+2010-02-03 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: add ulem "stand-alone"
+
+ * filectan.tex: remove ulem
+
+2010-02-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (subsection{LaTeX macro programming}): remove
+ superflous \expandafter in q-seccntfmt, and tidy text a bit
+
+2010-02-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): move
+ q-ovwtsym and q-long-outer to start of text
+ add q-detknize
+
+RELEASE 3.19c
+
+2010-01-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * mk-makefile: deal with CHANGES files
+
+2010-01-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: correct catalogue link for revtex
+
+ * filectan.tex: remove capt-of, url
+
+ * dirctan.tex: add capt-of, url
+
+2010-01-20 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): herbert voss's handy
+ "tips and tricks" has disappeared, leaving q-doc-dirs very thin
+
+ * dirctan.tex: add dtl, dviasm
+
+ * faq-t-g-wr.tex (subsection{Things have "gone away"}): suggest dis/re-
+ assembling dvi files to get rid of am font refs in q-amfonts
+
+2010-01-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex,faq-fonts.tex,faq-getit.tex,faq-how-do-i.tex: use
+ mirrors.ctan.org where reasonable
+
+ * dirctan.tex: add txfontsb
+
+ * faq-fonts.tex (subsection{Adobe Type1 fonts}): mention txfontsb
+
+2010-01-08 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: update version and date
+
+ * sanitize.pl (sanitize_line): brought -beta changes to mainstream
+
+2010-01-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: extend comment on the line making \faqinput work
+ when processing with latex
+
+ * build-faqbody (gather_process): slightly refine the regexp that
+ was ignoring all lines beginning \let ;-)
+
+2010-01-05 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sub-luximono.sty: jiffy for when \not\exists luximono
+
+ * faq.sty: provide for no luximono
+
+2010-01-04 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-biblio.tex (subsection{Creating bibliographies}): mention google
+ scholar in q-buildbib
+
+2009-12-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex (section improvement; general typos): add uwe lueck
+
+ * faq-t-g-wr.tex (subsection{Getting things to fit}): correct the name
+ of the author of pictexwd (courtesy uwe lueck)
+
+2009-12-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (section{Current TeX-related projects}): mention
+ luatex 0.50.0, and tidy up the paragraph, in q-luatex
+
+2009-12-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-install.tex (section{Installing (La)TeX files}): change two
+ (different) uses of kpsewhich to find a variable to use -var-value
+ instead, in q-what-tds and q-privinst
+
+2009-12-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-getit.tex (section{Acquiring the Software}): minor edit of
+ q-archives
+
+ * faq-bits+pieces.tex (section{Bits and pieces of (La)TeX}): change
+ anchor for liang's thesis in q-hyphen
+ (section{Bits and pieces of (La)TeX}): ctan link for auc-tex in q-dtx
+ (section{Bits and pieces of (La)TeX}): minor edit of q-ecfonts
+ (section{Bits and pieces of (La)TeX}): redo q-tds somewhat
+
+2009-12-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (section{Bits and pieces of (La)Tex}) rehash
+ q-dvi and q-specials somewhat
+
+ * dirctan.tex: typo in miktex
+
+ * filectan.tex: remove pdftex-oztex (moved, but no longer used anyway),
+ and move both install-tl links down from 2008/ subdir
+
+2009-12-17 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-getit.tex (section{Acquiring the Software}): reword q-nonfree to
+ reflect the actual disappearance of the nonfree tree
+ (section{Acquiring the Software}): update details of the tex collection
+ from the web site (in q-cd, of course)
+ (section{Acquiring the Software}): use official address for dante
+ search page, in q-findfiles
+
+2009-12-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-projects.tex (section{Current TeX-related projects}): tidy up
+ q-latex3 (used to ref unpackages)
+
+ * faq-texsys.tex (section{TeX Systems}): tidy up miktex, and ref to
+ miktex under linux; removed commented non-386 nt refs
+
+ * dirctan.tex: kill two non-intel miktex links, add miktex "plain"
+
+2009-12-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * gather-faqbody.tex: v3.19b, date
+
+ * dirctan.tex: add threeparttablex
+
+ * faq-how-do-i.tex (subsection{Footnotes}): add threeparttablex, and
+ rewrite somewhat...
+
+2009-12-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-backgrnd.tex (section{The Background}): context is already
+ running on luatex (in q-context)
+ (section{The Background}): \luatex without {} in q-texfuture :-(
+
+ * sanitize-beta.pl (sanitize_line): translate \LuaTeX{}
+
+2009-12-08 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Document management}): rewrite blurb
+ around pdftex in intro of q-changebars
+
+2009-11-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add here.sty
+
+ * faq-how-do-i.tex (subsection{Floating tables, figures, etc.}): add
+ here package to q-figurehere
+
+2009-11-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-install.tex (section{Installing (La)TeX files}): mention mactex
+ default location for home texmf, in q-privinst
+
+2009-11-20 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-hyp+pdf.tex (section{Hypertext and PDF}): first attempt at
+ sorting out q-pdfpagelabels
+
+2009-11-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Things have gone away}): minor typo in
+ q-initex
+
+ * faq-projects.tex (section{Current TeX-related projects}): work on
+ q-luatex to minimise hostages to fortune. (miktex 2.8 _wasn't_
+ released with a luatex implementation, for example)
+
+ * faq-intro.tex (section{Introduction}): explain what the visual faq is
+ about
+
+2009-11-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex: add steve mayer to the grand old list
+
+ * faq-projects.tex (section{Current TeX-related projects}): correct
+ link to mathtex
+
+2009-10-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex (section improvement; general typos): add david jansen
+
+ * sanitize-beta.pl (sanitize_line): deal with \ltxcounter
+
+ * faq.sty: add command \ltxcounter
+
+ * faq-jot-err.tex (section{The joy of TeX errors}): remove *two*
+ spurious \end{enumerate} from example code in q-errmissitem
+
+2009-10-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}): orig
+ command copy missing (more than once) in q-patch
+
+2009-10-23 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-intro.tex (subsection{Origins}): extend comment on joseph w
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}): add
+ l3keys[2e] to discussion in q-keyval
+
+2009-10-21 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-projects.tex (section{Current TeX-related projects}): remove ref
+ to and link to dir of keys3
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}):
+ remove mention of keys3 in q-keyval
+
+ * filectan.tex: xtexcad off nonfree tree
+
+ * dirctan.tex: add changepage directory
+
+ * filectan.tex: remove changepage
+
+2009-10-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): treat typesetversion like
+ dviversion (which ought to be right...)
+
+ * faq.sty: add environment typesetversion
+
+ * dirctan.tex: add subdepth, remove qms, quicspool
+
+ * add-general.tex (subsection{Mathematics}): add q-subdepth
+
+2009-10-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): change link for ams
+ "short math guide"
+
+2009-10-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-bits+pieces.tex (section{Bits and pieces of (La)TeX}): ref xetex
+ and luatex in q-adobetypen
+
+ * faq-intro.tex (introduction): add a para at the end of the list of
+ "real" contributors, to point out that lots of people help without
+ realising i'm snapping up their words...
+
+ * texfaq2html: use \end{introduction} to recognise end of intro copying
+ add code to read in catalogue details for files (oops)
+
+ * texfaq2html-beta: use \end{introduction} to recognise end of intro
+ copying
+
+ * dirctan.tex: various font-related catalogue entries (from psfchoice)
+
+2009-10-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+RELEASE 3.19a
+
+2009-10-08 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * CHANGES-3.19a: new, for release
+
+ * faq-wdidt.tex (subsection{Common misunderstandings}): new q-emptynum
+ from add-general
+
+ * Makefile ($(HTMLDIR)/index.html): add faqbody.tex to prereqs
+
+2009-10-07 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sanitize.pl: incorporate developments in -beta
+
+ * texfaq2file: correct root addr (in reading archive.list)
+
+2009-10-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Document management}): add latex-make,
+ latex_maker and vpp discussion to q-make
+
+ * dirctan.tex: add latex-make, latex_maker and vpp
+
+2009-10-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): add texlive and
+ miktex maintainers to people it's not good to ask direct, in q-gethelp
+
+2009-09-11 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-biblio.tex (subsection{Creating bibliographies}): append further
+ stuff to the last sentence of q-capbibtex
+
+2009-08-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-wdidt.tex (subsection{Why shouldn't I?}): editorial in q-dolldoll
+ (subsection{Why shouldn't I?}): correct typo in q-2letterfontcmd
+
+2009-08-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (subsection{Document structure}): remove caveat
+ about front- and backmatter in q-secthead
+
+ * faq-install.tex (section{Installing (La)TeX files}): another
+ editorial hack at q-instt1font
+
+2009-08-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-install.tex (section{Installing (La)TeX files}): minor editorial
+ in q-instt1font
+
+2009-08-26 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-install.tex (section{Installing (La)TeX files}): hack viciously
+ at q-inst1cm, move it to end of section
+
+ * Makefile (clean): remove faqbody.tex too
+ (<web copying rules>): correct variable names, correct dependencies
+
+2009-08-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-install.tex (section{Installing (La)TeX files}): deal with
+ confusion at the start of q-instt1font (spotted by jos\'e carlos
+ santos, again...)
+
+ * faq-bits+pieces.tex (section{Bits and pieces of (La)TeX}): tidy up
+ the shambles of q-ecfonts
+
+2009-08-25 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: correct three typos created while adding catalogue links
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}): in
+ q-patch, extend discussion of ted package, change patchcmd
+ accordingly, and do a few editorial diddles
+
+2009-08-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fonts.tex (subsection{Macros for using fonts}): mention
+ font-change in q-fonts-pln
+
+ * dirctan.tex: add font-change
+
+2009-08-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-intro.tex: add RIP note for Eitan Gurari ... much missed already
+
+ * dirctan.tex: sort out a couple of catalogue links
+
+ * check-ctan-lists: display missing cat entries
+
+ * filectan.tex: add cat links
+
+2009-08-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: remove t1tidy,t1tools,t1utils,uktug,umddvi,umlaute,
+ ugaritic,umrand,unadobe,uncompressing,undump,unix,unpacked,untex,usl,
+ utthesis,va,vector,vector,vga2mf,vietnamese,vispeech,vm-cms,vplutils,
+ vrb,vslitex,vutex,w2latex,wasy2,webtoc,whatstex,williams,winw2ltx,
+ word2tex,word_tex,wsuipa,xetal,xypic -- cat links completed
+
+2009-07-31 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): editorial in
+ q-maillists*
+
+ * dirctan.tex: remove pstab, pxlgen, qfig, quicspool, ransom,
+ recycle, redit, reduce, relabel, review, rmit, rune, rweb, s2latex;
+ cat links to end r*
+ remove sanskrit,saiter,sbtex,schemetex,screenview,script,scripttex,
+ sisisi, slant,sml,softfonts,southarabian,spain,spelchek,spell,
+ spiderweb,srune,ssl,ssqqote,stmaryrd,subeqnarray,sueterlin,swebib,
+ swedish,sweet-tex,swiftex,syriac
+ cat links to end s*
+ remove tamil,tbe,tcd-manual,tde-macros,teencontrex,tek2eepic,telugu,
+ tengwar,tex--xet,tex-d-l,tex-implementors,tex-primer_vms-specific,
+ tex-surface,texcalc,texchord,texdraw,texed,texfilt,texgraph,
+ texi2roff,texix,texpert,texproc,text1,text2dvi,textool,textures,
+ textures_figs,texutils,texware,thai,tie,tiff,translit,tree,tsipa,
+ tspell,turing[+],turkish,twcal,tx1,typingtex
+ cat links to end t*
+ restore spiderweb,spain,swebib
+
+
+2009-07-28 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new q-emptynum
+ containing an offcut from q-nopageno
+
+ * faq-adj-types.tex (subsection{Page layout}): further tidying of
+ q-nopageno, remove matter for q-emptynum
+
+2009-07-27 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (subsection{Page layout}): further tidying of
+ q-nopageno
+
+2009-07-21 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-adj-types.tex (subsection{Page layout}): amalgamate
+ q-nopageno and q-ps@empty (which talked about the same sorts of thing)
+ (subsection{Page layout}): change ref to \ps@empty in q-fancyhdr to
+ q-nopageno (not entirely reasonable just now, but we're getting there)
+
+ * add-general.tex (subsection{Things have "gone away"}): new q-initex
+
+2009-07-20 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): \dots->&hellip; (not ellipsis!)
+
+2009-07-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: cat links to end p*
+
+2009-07-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: added lshort, more cat links (up to l* now)
+
+ * filectan.tex: removed lshort (now in dirctan)
+
+2009-07-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-docs.tex (section{Documentation and Help}): add link to the
+ symbol classifier, in q-symbols
+
+ * dirctan.tex: still more catalogue links
+
+2009-07-13 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: bunch of new catalogue links (no particular order)
+
+ * texfaq2html-beta: deal with \CTANdirectory* and a cat link, and
+ \CTANfile ditto
+
+ * sanitize-beta.pl (generate_CTAN_ref): generate refs for directories
+
+2009-07-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: catalogue links up to f*
+
+2009-07-10 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-support.tex (section{Support Packages for TeX}): add link to
+ cygwin installation advice in q-xfigetc
+
+ * faq-projects.tex (section{Current TeX-related projects}): typo
+ spotted by fran\c{c}ois charette in q-biblatex, and further editorial
+ work starting from another of his observations
+
+2009-07-06 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-biblio.tex (section{References from articles}): add warning about
+ citeref's problems with cite.sty in q-backref
+
+2009-07-03 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: cat linkparallels up to cm-super
+
+ * add-general.tex (subsection{Bits and pieces of (La)TeX}): new
+ q-howfonts
+
+ * faq-mac-prog.tex (subsection{LaTeX macro programming}): correct one
+ instance of spelling of chngcntr in q-running-nos
+
+2009-07-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq.sty: get rid of optional args to \CTAN-(directory|file)
+
+2009-06-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq-fonts.tex (subsection{MF fonts}): bluesky fonts from amsfonts in
+ q-getbitmap
+
+ * faq-install.tex (section{Installing (La)TeX files}): remove "bluesky"
+ from name of q-inst1cm
+
+ * dirctan.tex: remove bluesky stuff
+
+2009-06-30 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * dirctan.tex: alpha now back to main tree
+
+ * faq-t-g-wr.tex (subsection{Things have "gone away"}): use amsfonts
+
+ * faq-install.tex (section{Installing (La)TeX files}): ams and cm fonts
+ type 1 links both go to amsfonts now
+
+ * dirctan.tex: add amsfonts-only link
+
+ * faq-fonts.tex (subsection{Adobe PS fonts}): replace refs to
+ ams-amstype1
+
+ * faq-symbols.tex (section{Symbols, etc.}): all ams things are in
+ amsfonts now
+
+ * dirctan.tex: added catalogue links up to babel
+
+2009-06-29 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * texfaq2html-beta: revert to oldstyle css, having experienced a
+ stronger yuck reaction to hufthammer's other suggestions
+
+ * dirctan.tex: add cat link for footmisc
+
+ * texfaq2html-beta: decode catalogue entry name (trailing [foo]) after
+ \CTANdirectory, non-starred versions only pro tem
+
+ * sanitize-beta.pl (generate_CTAN_ref): add catalogue link if available
+
+2009-06-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): a bit
+ of work on q-bgroup
+
+2009-06-23 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * texfaq2html-beta: try Steely style sheet for today...
+
+ * faq-docs.tex (section{Documentation and Help}): add reference to a
+ "full" tug india latex guide on sarovar
+
+2009-06-22 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * texfaq2html-beta: add css link to header of docs (Oldstyle)
+
+ * faq-docs.tex (section{Documentation and Help}): mention hisrchhorn's
+ amslatex-primer in q-man-latex
+ (section{Documentation and Help}): comment about difficulty of reading
+ in q-ref-doc
+
+2009-06-18 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-graphics.tex (section{Graphics}): change title of q-impgraph
+
+ * patchdates.tex: update patch version and date (was 2007...)
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): new
+ answer q-bgroup
+
+ * sanitize-beta.pl (sanitize_line): make \dots{} produce &ellipsis;
+
+2009-06-16 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faq-how-do-i.tex (subsection{Mathematics}): correct statements about
+ \textrm in q-mathstext (after enlightenment from Philipp Stephani...)
+
+2009-06-15 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * letterfaq.tex,newfaq-patch.tex,newfaq.tex: use gather-faqbody in jf's
+ lovely \afterassignment\endinput\input line...
+
+ * Makefile: include subdocuments.mk, add $(SUBDOCS) to BODY
+
+ * subdocuments.mk: list of things gathered by gather-faqbody
+
+2009-06-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * newfaq.tex,newfaq-patch.tex,letterfaq.tex: use gather-faqbody
+
+ * gather-faqbody.tex: new name for faqbody, as gutted (see below)
+
+ * faq-intro.tex,faq-backgrnd.tex,faq-docs.tex,faq-bits+pieces.tex,
+ faq-getit.tex,faq-texsys.tex,faq-dvi.tex,faq-support.tex,
+ faq-litprog.tex,fmt-conv.tex,faq-install.tex,faq-fonts.tex,
+ faq-hyp+pdf.tex,faq-graphics.tex,faq-biblio.tex,faq-adj-types.tex,
+ faq-lab-ref.tex,faq-how-do-i.tex,faq-symbols.tex,faq-mac-prog.tex,
+ faq-t-g-wr.tex,faq-wdidt.tex,faq-jot-err.tex,faq-projects.tex,
+ faq-the-end.tex: split out sections of faqbody.tex
+
+ * faqbody.tex: split sections out into their own faq-*.tex, make
+ this predominantly a set of \faqinput commands
+
+ * faq.sty: deal with LastEdit*
+
+ * sanitize-beta.pl (sanitize_line): process \LastEdit*
+
+ * faqbody.tex: adding \LastEdit to q-texorpdf,q-recovertex,
+ q-linmacnames,q-latexpronounce,q-logos,q-mcite,q-texthings
+
+2009-06-11 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * Makefile (newfaq.aux): move label to linf of its own
+
+ * Makefile.CTAN (CHANGES): do this properly (may need -new rather than
+ -replace)
+
+ * dirctan.tex: add figflow
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): add figflow
+ to q-textflow (at bnb's suggestion), and remove "in latex" qualifier
+ in question title
+
+ * faq.sty: add \LastEdit (to gobble, pro tem at least)
+
+ * sanitize-beta.pl (sanitize_line): add \LastEdit
+
+ * faqbody.tex: v3.19a, today
+ (paragraph{Modified tex executables}): a couple of typos spotted by
+ scott pakin in q-texthings, add experimental \LastEdit
+
+ * sanitize-beta.pl (sanitize_line): move \ISBN .. \Newsgroup above
+ \section, etc., so that those things can be in section arguments
+
+2009-06-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize.pl (generate_CTAN_ref): change worked for -beta, so here too
+
+ * sanitize-beta.pl (generate_CTAN_ref): missing "/" found by bnb
+
+2009-06-10 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * CHANGES-3.19: final released version
+
+ * faqbody.tex: today's date
+
+ * Makefile.CTAN (CHANGES): muck about with installation of new file
+
+ * locations.mk: add HTMLDIREL, define HTMLDIR in relation to it
+
+ * Makefile (release): new target, generate pdfs and html tar file
+
+2009-06-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add collref; bring macros/blu, systems/msdos/e4t,
+ support/et, support/jpeg2ps, macros/scripttex from nonfree; junk
+ oztex-german (now obsolete), patches (nonsense)
+
+ * faqbody.tex (section{References from articles}): rearrange q-mcite a
+ bit, and add collref to it
+
+2009-06-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * Makefile.CTAN: don't do .ps files any longer
+
+ * Makefile: don't generate .ps files in "all", just pdf
+
+ * sanitize.pl: up to date with -beta changes
+
+ * texfaq2html: up to date with -beta changes
+
+ * texfaq2html-beta: removed debugging statements (already commented)
+
+2009-06-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Background}): micro-editorial in q-latexpron...
+
+2009-06-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Background}): untangle logos in re. q-latexe,
+ and modify q-latexpronounce accordingly
+ (subsection{Odds and ends}): adjust q-logos to cope with non-bumpy text
+ such as we now use
+
+ * faq.sty: add \latexe
+
+2009-06-03 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): new
+ q-linmacname from add-general
+
+2009-05-29 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): change
+ name of q-macronames to q-linmacnames, yet more editorial
+
+ * faqbody.tex (section{Format conversions}): editorial in q-recovertex
+ (section{The joy of TeX errors}): new q-texorpdf from add-general
+
+2009-05-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): a bit
+ of editorial on q-macronames
+
+2009-05-28 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): translate \c{c}
+
+ * faqbody.tex (section{Current TeX-related projects}): revised q-xetex
+ from francois charette
+ (intro): add francois to list of acknowledgements
+ (first line): today's date
+
+2009-05-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): minor editorial on q-drawing
+
+ * dirctan.tex: add epic
+
+ * faqbody.tex (section{Graphics}): add brief descriptions of pictex,
+ epic and eepic[emu] to q-drawing
+
+2009-05-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add first-latex-doc
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): mention first-latex-doc in
+ q-man-latex
+
+2009-05-20 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Symbols, etc.}): new q-osf from add-general
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): refer
+ to q-whatmacros rather than spelling out the rules, in q-macronames
+
+2009-05-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): update link for textures in
+ q-commercial
+ (various places): minor editorial work
+
+ * add-general.tex (subsection{Odds and ends}): editorial on q-osf
+
+ * faqbody.tex (section{Support Packages for TeX}): correct \href for
+ texcount,in q-wordcount
+
+ * dirctan.tex: add asymptote
+
+ * faqbody.tex (section{Support Packages for TeX}): retitle q-xfig as
+ q-figetc, and mention asymptote in it (now it's on ctan!)
+
+2009-05-18 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): q-grffilenames from add-general
+
+ * add-general.tex (subsection{Graphics}): tidy q-grffilenames, correct
+ previous text about knuthian constraints on input file name format
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): moved q-whatmacros
+ from add-general *already*
+ (subsection{Floating tables, figures, etc.}): q-wideflt from
+ add-general, too!!
+
+ * add-general.tex (subsection{Bits and pieces of (La)TeX}): new "what
+ are macros" (q-whatmacros)
+ (subsection{Tables, figures and diagrams}): new "wide figures and
+ tables" (q-wideflt)
+ (subsection{Odds and ends}): editorial on q-osf
+
+2009-05-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add miktex-portable
+
+ * faqbody.tex (section{TeX Systems}): mention miktex-portable in
+ q-texsystems
+
+2009-05-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq.sty: tidy include/exclude comments; make introduction into a real
+ env
+
+ * faqbody.tex (intro): simplify \nothtml code in introduction env
+
+2009-05-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (intro): v3.19, today
+
+2009-05-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): yet more
+ editorial on q-keyval
+
+ * sanitize-beta.pl (sanitize_line): translate \par{} as <br/>
+
+2009-05-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): yet
+ another diddle of q-macronames ... just can't quite satisfy myself
+ about this thing
+
+2009-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): list macro
+ names for class/package options in xkeyval
+
+2009-05-07 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): mention
+ ifxetex and ifluatex in q-ifpdf
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): yet
+ more diddling with q-macronames
+ (subsection{\LaTeX{} macro tools and techniques}): wrap a terrible wide
+ line in an example in q-keyval
+
+ * dirctan.tex: add texcount
+
+ * faqbody.tex (section{Support Packages for TeX}): add ctan links for
+ (la)texcount and description of texcount in q-wordcount
+
+2009-05-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): minor
+ update of q-macronames on internal macros and why they work
+
+2009-05-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: psfig back on main tree; xypic link as catalogue, now;
+ xfig, xdvi and usergrps now browse-only;
+ remove arc521, arj, atob, binhex, boo, bsplit, checksum, comm, compact,
+ compress, filehdr, ftpd, ftpmail, hexbin, lharc, machdr, macunpack,
+ macutils, mcvert, mirror, mixed, parc, stuffit, tar, tex88, tex8fmts,
+ transname, unarj, unpack, unstuff, uue, uuencode, vtree, vtree-fix,
+ vvcode, xbin (tools/*);
+ remove two borceux subdirs -- diagram, user-guides
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): add
+ final(?) paragraphs of q-keyval
+
+2009-05-01 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): add
+ pgfkeys to q-keyval, and make a start on scrbase
+
+ * dirctan.tex: add biblatex-contrib
+
+ * faqbody.tex (section{Current TeX-related projects}): update
+ q-biblatex and mention biber therein
+
+2009-04-29 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): mention setspaces
+ spaces and hyphens options of url.sty, in q-setURL
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): don't
+ use |$| in q-catcodes, since it confuses auctex's text colouring --
+ \texttt{\$} instead
+ (subsection{"Generic" macros and techniques}): hack at q-macronames
+ after staring at it a bit
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): give
+ \textasciicircum a null argument in q-wholerow
+
+2009-04-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): add
+ xkeyval to q-keyval
+
+ * faqbody.tex (rogue's gallery): add joseph wright and philipp stephani
+ in recognition of help on q-keyval answer
+
+2009-04-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): add
+ kvoptions and kvsetkeys to q-keyval
+
+2009-04-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): more
+ work on q-keyval
+
+2009-04-14 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): new
+ q-keyval
+
+ * faqbody.tex (subsection{Why does it do that?}): editorial on
+ q-pdf-fig-chars following thanh's comment
+
+2009-04-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): new q-pdf-fig-chars from
+ add-general
+
+ * add-general.tex (subsection{Graphics}): flesh out q-grffilenames
+
+2009-04-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): complete sentence that
+ previously ended "but" (no full stop!) in q-changemargin
+
+ * add-general.tex (subsection{Why does it do that?}): further editorial
+ on q-pdf-fig-chars
+
+ * texfaq2html-beta: remove the "complete set" link at bottom of search
+
+ * faqbody.tex (subsection{Adobe Type 1 (PS) fonts}): editorial on cm
+ bright in T1 (now a bit less pompous, i hope)
+
+2009-04-12 (small hours) Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new
+ q-pdf-fig-chars at thanh's request
+
+2009-04-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): improvements to
+ q-luatex from manuel pegourie-gonnard
+ (intro): add mpg to list of names
+
+2009-04-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): editorial on
+ q-mfptutorials
+ (section{Acquiring the Software}): editorial on q-nonfree
+
+ * dirctan.tex: add latex-tds
+
+ * faqbody.tex (section{Documentation and Help}): mention heiko's
+ source2e in q-writecls
+
+ * filectan.tex: add latexcheat
+
+ * faqbody.tex (section{Documentation and Help}): add bullet item about
+ figures in q-askquestion
+ (section{Documentation and Help}): editorial on q-man-latex,
+ q-typo-style
+ (section{Documentation and Help}): correct link for pgf/tikz examples
+ in q-tutbitslatex
+ (section{Documentation and Help}): add cheat sheet in q-ref-doc
+
+2009-04-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (paragraph{TeX distributions}): editorial work on
+ q-texthings, q-plainvltx, q-amspkg, q-eplain, q-texfuture
+ (section{Documentation and Help}): editorial work on q-wherefaq,
+ q-gethelp, q-maillists*
+
+2009-04-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): add link to
+ liang's thesis in q-hyphen
+
+2009-04-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): add sentence to the end of
+ first para of q-whattex; hack away at q-whatpdftex
+
+ * dirctan.tex: delete preview-latex & fptex, make auctex browse only
+
+ * faqbody.tex (section{Current TeX-related projects}): preview-latex
+ now part of auctex, in q-wygexpts
+
+ * dirctan.tex: remove ghostview, move plnfss up one and remove *
+
+ * faqbody.tex (subsection{Finding the Files}): further iteration,
+ now checked in all 3 formats
+ (section{Hypertext and PDF}): ghostview now an unprogram in q-acrobat
+ (subsection{Adobe Type 1 fonts}): replace ghostview with gv
+
+ * Makefile (web,web-beta): correct shell syntax of yesterday's patch(!)
+
+2009-04-01 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Finding the Files}): further iteration
+
+ * Makefile (update web files): deal with case that file doesn't exist
+
+2009-03-31 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Finding the Files}): get rid of a link-
+ without-visible-anchor in the pdf, generally tidy
+
+2009-03-27 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): stupid error in sub of \wideonly
+
+ * texfaq2file: various errors thrown up by -w ... so remove -w
+
+2009-03-26 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (generate_CTAN_ref):
+
+ * texfaq2file: restore list of protocols and hosts (since they're used)
+ ... but don't overdo it ... this lot is a mess and needs tidying
+
+ * label-to-file.pl: the list of file names corresponding to q labels
+
+ * texfaq2file+texfaq2html-beta: use label-to-file.pl in place of list
+ in file
+
+2009-03-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add compactbib
+
+ * faqbody.tex (subsection{Creating citations}): mention compactbib in
+ q-compactbib (where else? ;-)
+
+2009-03-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: rename bibtex-doc-pdf to bibtex-doc (overwriting old
+ one) so that link takes you to something readable
+
+ * faqbody.tex: 3.18b, today
+ (section{Documentation and Help}): make bibtex docs link just
+ bibtex-doc -- see dirctan change
+ (subsection{Creating bibliographies}): ditto in q-custbib
+
+2009-03-20 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * check-ctan-lists: check status of directory .zip files ...
+
+ * dirctan.tex: bunch of anomalies shown up by latest version of scanner
+
+ * sanitize-beta.pl (generate_CTAN_ref): suppress .tar.gz link
+
+ * texfaq2html-beta: sort lists of matching answers numerically, at last
+ (initialisation): close CTANFILES and CTANDIR after reading them...
+
+ * faqbody.tex (section{Current TeX-related projects}): more twiddling
+ with q-xetex
+ (section{Current TeX-related projects}): ditto q-luatex
+ (section{Current TeX-related projects}): ditto q-omegaleph (more
+ downbeat still than previously :-(
+ (section{Symbols, etc.}): add q-usesymb from add-general
+
+2009-03-19 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Symbols, etc.}): add initial body for
+ q-usesymb
+
+ * faqbody.tex (section{TeX Systems}): mention miktex-for-linux in
+ q-texsystems
+ (section{Current TeX-related projects}): more hacking at q-luatex
+ (section{Current TeX-related projects}): rearrange q-omegaleph,
+ q-xetex, q-luatex, q-ant, q-extex into that order
+
+2009-03-18 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): more fiddling
+ with latex project answer
+ (section{Current TeX-related projects}): mimetex now superseded by
+ mathtex
+ (section{Current TeX-related projects}): don't compare ant to nts,
+ since we no longer mention nts ;-)
+ (section{Current \TeX{}-related projects}): hack at q-luatex
+
+ * dirctan.tex: add keys3, numparse3
+
+ * faqbody.tex (section{Format conversions}): reword q-fmtconv as
+ suggested by jose carlos santos
+
+ * dirctan.tex: add yagusylo
+
+ * add-general.tex (subsection{Symbols, etc.}): skeleton q-usesymb
+
+2009-03-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Footnotes}): try to clarify text of q-ftncapt
+ in re. complaint on c.t.t
+ (section{The joy of TeX errors}): tidy up talk about etex.sty in
+ q-noroom, and mention \reserveinserts
+
+2009-03-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add blackboard
+
+ * faqbody.tex (section{Symbols, etc.}): redo q-numbersets, mention
+ blackboard doc
+
+2009-03-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add urw-base35, remove plain urw
+
+ * faqbody.tex (section{Symbols, etc.}): redo refs to urw chancery, add
+ link to URW base35, in q-scriptfonts
+
+2009-03-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): tidy wording about tbt
+ in q-books
+
+2009-03-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): typo in q-editors
+
+2009-03-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): slightly less frivolity, in
+ pursuit of better comprehensibility, among the unix editors
+
+ * sanitize-beta.pl (sanitize_line): translate \texshop{}, \texworks{};
+ reorganise the list of "programs" for ease of editing
+
+ * faq.sty: define \texshop, \texworks
+
+ * faqbody.tex (section{TeX Systems}): add a wildcard entry to the list
+ for texworks, in q-editors
+
+2009-02-12 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): micro-
+ typo in q-patch
+
+2009-02-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add expl3, xpackages
+
+ * faqbody.tex (section{Current TeX-related projects}): update q-latex3
+
+2009-02-09 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): add q-texthings, from
+ add-general
+
+2009-01-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): add q-texorpdf
+
+2009-01-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): revise view of the
+ wiki books (which seem to have improved a lot)
+
+2009-01-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-beta: correct period positioning after previous mod
+
+ * faqbody.tex (subsection{Document structure}): chappg documented
+ "normally" now in q-pagebychap
+ (subsection{Document structure}): remove q-outszwrng
+ (subsection{Document structure}): merge (and condense) list from old
+ q-outszwrng into q-acroantics
+
+
+2009-01-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): exptl translation for \paragraph
+
+ * faq.sty: redefine \paragraph, too
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): more
+ minor diddling with q-macronames
+ (subsection{The Background}): similar for q-texthings
+
+2009-01-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document structure}): rewrite warning about
+ programming zoonekynd's stuff, in q-secthead
+
+2009-01-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add revised tth ;-)
+
+ * filectan.tex: remove tth
+
+2009-01-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): tidy up following
+ obsoleting of numline, in q-linenos
+
+ * dirctan.tex: remove rsfs-type1
+
+ * faqbody.tex (section{Symbols, etc.}): rsfs type 1 now part of base
+ distribution in q-scriptfonts
+
+ * filectan.tex: numline now in obsolete
+
+2008-12-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Background}): editorial on list of
+ enhanced tex engines
+
+2008-12-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): add
+ q-macronames from scott pakin
+ (subsection{The Background}): add q-texthings from scott pakin
+
+2008-12-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): typo in q-graphicspath spotted by
+ jim diamond
+
+2008-11-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): minor tidy of q-tds-zip
+ (section{Installing (La)TeX files}): clear up gross \qref error in
+ q-inst-tds-zip, and tidy up rest of question
+
+2008-11-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): mention tl network install, tl
+ and miktex package net update
+
+ * filectan.tex: add texlive-unix, texlive-windows
+
+ * faqbody.tex (section{Current TeX-related projects}): a bit of
+ rewording of the presumed prospects for omega 2
+
+2008-11-26 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex ([throughout]): minor edits for untidinesses spotted by
+ karl berry
+
+2008-11-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): minor ed of q-eps
+
+ * add-general.tex (subsection{Graphics}): added q-grffilenames
+ (initial stab ... not even complete in itself)
+
+2008-09-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html: as -beta
+
+ * texfaq2html-beta: add home link at end of answer, after next/prev
+ links if present
+
+2008-09-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): correct
+ invocation of topcapt package in q-destable
+
+2008-09-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): try to refer to dvipdfmx in parallel
+ in q-dvipdfmgraphics
+
+2008-09-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add ptr to emory
+ latex2e ref in q-ref-doc
+
+2008-08-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * Makefile (dist): new target for manual pegouri\'e-gonnard
+
+2008-08-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): mention lulu version
+ of tbt, both in q-ol-books and q-books
+
+2008-08-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add varisize
+
+ * faqbody.tex (subsection{Macros for using fonts}): mention varisize in
+ q-fonts-pln
+
+2008-08-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): deprecate
+ dropping, rewrite descr of lettrine appropriately
+ (subsection{Floating tables, figures, etc.}): mention perpage's
+ \MakeSorted in q-figurehere
+
+2008-08-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Generic macros and techniques}): store
+ a copy of donald a's \moverlay in q-ovwtsym, for future reference
+
+2008-08-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add addlines
+
+ * faqbody.tex (section{Graphics}): mention eplain as a plain route to
+ to loading graphics in q-impgraph (per kb's suggestion)
+ (subsection{Page layout}): mention addlines in q-chngmargonfly
+
+2008-07-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \htmlentity to deal with
+ q-dropping guillemet problem
+
+ * faqbody.tex (subsection{Typesetting specialities}): use \htmlentity
+ in \latexhtml (guillemets) in q-dropping
+
+2008-07-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): remove chngpage from
+ q-marginpkgs
+
+ * filectan.tex: chngpage->changepage; remove pdftex
+
+ * dirctan.tex: add mciteplus, pdftex, record move of aro-bend
+
+ * faqbody.tex (subsection{Creating citations}): mention mciteplus in
+ q-mcite
+
+2008-07-28 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2file: ruthless stamping on problems produces a use full output
+
+2008-07-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2file: more minor adjustments
+
+ * faqbody.tex (section{Introduction}): now a real (unnumbered) section
+
+2008-07-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faq.sty: include comment introduction
+
+ * faqbody.tex: put environment introduction around introduction
+
+2008-07-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: minor tidies, use index.html for intro, pro tem
+
+ * faqbody.tex (subsection{Common errors}): editorial in q-verbwithin
+
+2008-07-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: correct repeated-code subroutine from 19th
+ (print_intro_para, etc): attempt to sort out coherent "whole path"
+
+2008-07-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: some tidying of repeated code, clarification of
+ logic of the code -- lots more still to do...
+
+2008-07-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): discuss
+ \ifpatchable in the bit about etoolbox in q-patch
+ (section{Current TeX-related projects}): brief scribble about how lua
+ operates inside tex, in q-luatex
+
+2008-07-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Footnotes}): mention zref/perpage in
+ q-footnpp
+
+2008-07-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{MetaFont fonts}): more modernisation of
+ q-usemf (no longer mentions virmf, for example)
+
+2008-07-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: major upheavals: beginning to show signs of
+ working in the various parts separately
+
+ * faqbody.tex (subsection{Alternative document classes}): tidy text of
+ both q-thesis and q-journalpaper
+ (subsection{MetaFont fonts}): tidy up q-usemf (though whether to keep
+ it at all remains a matter of debate)
+
+2008-07-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add plastex
+
+ * faqbody.tex (section{Format conversions}): add plastex to
+ q-latex2html
+
+2008-07-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): enumerate the
+ complete set of memoir document sizes in q-extsizes
+
+2008-07-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * Makefile: add target inst-perl-gamma (just texfaq2html-gamma)
+
+ * texfaq2html-gamma: add description meta element to start_html
+
+ * texfaq2html-beta: added a description meta element
+
+ * texfaq2html-gamma: comment out setting of $seclevel hash, since it's
+ not used and therefore logging errors
+
+2008-07-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): miktex already
+ has xetex ('cos it's got to 2.7 already)
+
+2008-06-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * Makefile: delete FAQ-html.tar.gz in "clean"
+
+2008-06-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): make clear we're talking about latex
+ packages in re. the comp. list in q-symbols
+
+2008-06-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2file: add inst-miktex* to label_to_file (per mpg);
+ correct generation of links from index.html (per jonathan k)
+
+ * faqbody.tex: 3.18a, today
+ (subsection{Lists}): add mention of expdlist in q-interruptlist
+
+ **FAQ-html.tar.gz patched on archive**
+
+2008-06-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, for release
+ (section{Bits and pieces of (La)TeX}): correct typo in q-dtx
+ wideversion
+
+ **RELEASE**
+
+2008-06-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html: carried -beta modifications forward
+
+ * sanitize.pl (sanitize_line): carried -beta modifications forward
+
+2008-06-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): tidy descr
+ of patch.doc in q-patch, and mention ted and etoolbox
+
+2008-06-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (head): today's date
+ (section{Acquiring the Software}): rewrite of some of q-tds-zip
+ (section{Current TeX-related projects}): discuss luatex schedule for
+ distribution, and firm up demise of pdftex devel, in q-luatex
+ (section{Acquiring the Software}): \Qref* to q-psfchoice in link
+ in q-findfont (rather weird without the * ;-)
+
+2008-06-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): new q-tds-zip
+ (section{Installing (La)TeX files}): refer to q-tds-zip in
+ q-inst-tds-zip
+
+2008-06-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): reorganise to make
+ the text flow slightly more coherently in q-install-find
+
+ * dirctan.tex: add winedt (browse only)
+
+ * filectan.tex: add mathsurvey.(pdf|html), remove winedt
+
+ * faqbody.tex (subsection{Adobe Type 1 ("PostScript") fonts}): mention
+ Hartke's survey in q-psfchoice, add ctanref to it
+
+2008-06-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type1 ("PostScript") fonts}): mention
+ the tex font catalogue in q-psfchoice
+ (subsection{Adobe Type 1 (PostScript) fonts}): add links to the
+ catalogue for fonts we _do_ list, in q-psfchoice
+ (section{Installing (La)TeX files}): editorial on q-instmffont
+
+2008-06-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): recognise "\textbackslash ";
+ (hopefully) throughout routine, escape semicolons in substitution text
+
+ * faqbody.tex (section{Installing (La)TeX files}): diddle endlessly
+ with q-what-tds to get \textbackslash to work
+ (throughout): \textbackslash{} -> "\textbackslash " (dunno why)
+
+2008-06-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Hyphenation}): mention none option of
+ hyphenat package in q-hyphoff, and point out it's incompatible with
+ babel
+
+ * texfaq2html-beta: correct typo in no-mod branch of translation of
+ question labels
+
+2008-06-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): rearrange (and do a
+ smidgeon of editing while we're at it) q-install-find
+
+2008-06-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): change initexmf -u
+ to --update-fndb (official version) in q-inst-wlcf
+ (section{Installing (La)TeX files}): tidy up q-what-tds (last of
+ proof-reading stuff?)
+
+2008-05-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): proof-reading work
+ on q-installthings, q-install-find, q-install-unpack
+
+2008-05-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-beta: remove papersize* from label_to_file
+
+ * faqbody.tex (subsection{Page layout}): remove old q-papersize, rename
+ q-papersize* as q-papersize
+ (section{Installing (La)TeX files}): oops -- had missed the \Question
+ command of q-instt1font
+ (header) version 3.18, today
+
+2008-05-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): hack some more at
+ q-instt1font, and split q-prept1font from the front of it
+
+2008-05-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): major hacking of
+ q-instt1font, with a view to splitting it in two
+
+2008-05-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-beta: require aliasfile.list, use its hash to update
+ input labels
+
+ * faq.sty: write aliasquestion.list as a perl module creating a hash
+
+2008-05-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * Makefile (targets web and web-beta): add aliasquestion.list to the
+ files copied
+
+ * texfaq2html-beta,texfaq2html-gamma: add inst-miktex* to label_to_file
+ hash
+
+ * add-general.tex (subsection{Particular font families}): in q-mathtime
+ change ref to q-inst-miktex to q-inst-miktex* (even though mathtime
+ question has now presumably timed out)
+
+ * faqbody.tex (section{Installing \AllTeX{} files}): add questions
+ q-inst-scut, q-inst-miktex* and q-inst-tds-zip (from add-general)
+ in place of q-inst-miktex
+
+2008-05-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \AliasQuestion (ignored)
+
+ * faqbody.tex (section{Documentation and Help}): minor editorial in
+ q-pkgdoc
+
+2008-05-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): add body to
+ q-inst-tds-zip
+
+ * Makefile (target clean): add aliasquestion.list
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): editorial tidies
+ in q-pk and q-tfm
+
+2008-05-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): minor edit of
+ q-inst-miktex*
+
+2008-05-12 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): add alias
+ instpackages (for installthings) and wherefiles (for inst-wlcf)
+
+ * add-general.tex (subsection{Installing (La)TeX files}): add alias for
+ q-inst-scut, for testing purposes
+
+ * faq.sty: add \AliasQuestion and supporting mechanisms
+
+2008-05-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems errors}): tidy q-endingroup markup
+
+2008-05-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): stupid typo spotted by
+ keith briggs, in q-changebars
+
+ * sanitize-beta.pl (sanitize_line): \texlive, again
+
+ * faq.sty: \texlive according to karl b
+
+2008-05-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): tidy up the english
+ and the markup of q-install-unpack, a bit
+
+2008-05-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.17-3, today; add ernst to list of helpers
+ (subsection{Footnotes}): clarify text around mdw's packages in
+ q-footintab
+
+2008-04-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): mention textures on osx
+
+2008-04-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): correct tug box search
+ address in q-findfiles
+
+2008-04-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: correct dvitype, moved as part of texware (v.i.)
+
+ * dirctan.tex: correct errata, tex--xet, texware and web (knuth-isms
+ moved); add vc
+
+ * faqbody.tex (subsection{Document management}): add vc to q-rcs and
+ make various minor adjustments to accommodate it
+ (header) today's date, add hennig to list of contributors
+
+2008-04-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): mention tex4ht as a route
+ to word format in q-fmtconv; re-sort list to make it more reasonable
+ for today's use
+ (header) v3.17-2, today
+
+2008-03-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: correct committee font, lgrind and mfware; add ziffer
+
+ * filectan.tex: add changepage, remove ziffer, correct figsinltx
+
+ * faqbody.tex (subsection{Spacing of characters and lines}): the
+ letterspace package is no more so change description to microtype
+ in q-letterspace
+ (subsection{LaTeX macro programming}): mention changepage in q-oddpage,
+ (subsection{Page layout}): mention changepage in q-chngmargonfly
+
+2008-03-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-beta, texfaq2html-gamma: add papersize* to label mapping
+ list
+
+ * faqbody.tex (subsection{Page layout}): comment out q-papersize, add
+ q-papersize*, q-acroantics, q-papergeom from add-general
+
+2008-03-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: update \faqfiledate
+
+2008-03-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Footnotes}): rearrange recommendations in
+ q-footnpp
+
+2008-02-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): tfti is gnu _free_
+ documentation licence, in q-ol-books
+
+2008-02-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): correct usage of \bsbs
+
+2008-02-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): tidy text in q-acroantics
+ so the italic of \ProgName doesn't get confused with emphasis
+ (subsection{Odds and ends}): minor edit of q-osf
+
+2008-02-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): add memoir section to
+ q-papergeom
+
+2008-01-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): more diddling with
+ q-papergeom
+
+2008-01-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): replacement for
+ q-papersize (3 qs: q-papersize*, q-acroantics, q-papergeom)
+
+2008-01-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \plaintex{}
+
+ * faq.sty: add \plaintex{}
+
+ * faqbody.tex (subsection{Page layout}): lots of diddling of
+ q-papersize
+ (throughout) [Pp]lain[ ~]\TeX{} -> \plaintex{}
+
+2008-01-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): muck about with % (which fools
+ sanitize) in q-papersize quoted material about acrobat
+ (subsection{Page layout}): more hacking at this, trying to make it read
+ as if written by a human being
+
+2008-01-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): change url for
+ nicola's latex for novices, in q-man-latex
+
+2008-01-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Hypertext and PDF}): new q-pdf-encr
+
+2008-01-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (intro): add william ingram
+
+2008-01-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: * def of crosstex
+
+ * faqbody.tex (section{Current TeX-related projects}): lots of hacking
+ at q-biblatex
+
+2008-01-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): micro-change to q-etex
+
+2008-01-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): add a word of caution about about
+ bmeps bitmap patch for dvips, in q-dvipsgraphics
+
+2008-01-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add crosstex
+
+ * faqbody.tex (section{Current TeX-related projects}): mention crosstex
+ in q-biblatex
+
+2008-01-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Creating bibliographies}): dealing with p.m. de f. forster
+ in q-bibtranscinit
+
+2007-12-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add preview, remove ps4mf
+
+ * faqbody.tex (section{Graphics}): update text around pstricks in
+ q-drawing (the question may need more root-and-branch attention)
+
+2007-12-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): mention pdfcolparallel in
+ q-parallel
+
+2007-12-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * filectan.tex: add miktex-usb
+
+ * add-general.tex (section{TeX Systems}): add q-onna-stick
+
+2007-11-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): yet
+ more mucking with q-long-outer (mostly trimming narrowversion lines)
+
+ * Makefile (clean): add htmltex/* for cleaning
+
+2007-11-26 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): more-
+ or less finished q-long-outer
+
+2007-11-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \textasciicircum{}
+
+ * dirctan.tex: add picins
+
+ * filectan.tex: remove picins
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): heroic attack
+ on command skeletons in q-textflow
+ (throughout): lots of hacking to get rid of |...| verbatims
+
+ * faq.sty: \cmdinvoke accepts parenthesised arguments
+
+ * faqbody.tex (subsection{MF fonts}): tidy narrow/wide interaction in
+ basic mf commands in q-usemf
+ (subsection{Creating bibliographies}): get rid of inline verb in
+ q-bibaccent, and merge html and non-html versions
+
+2007-11-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): new
+ q-long-outer
+
+ * faqbody.tex (throughout (remaining)): spell-checked
+ (section{Symbols, etc.}): minor editorial on q-underscore
+
+2007-11-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout first ~50%): spell-checked
+
+2007-11-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add auto-pst-pdf (yet to be installed, but...)
+
+ * faqbody.tex (section{Graphics}): mention (auto-)pst-pdf in q-labelfig
+
+2007-11-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): replace
+ "places to look for are" (!) with "candidates are" in q-protect
+
+2007-11-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: add john harper to preamble list of helpers
+ (subsection{LaTeX macro tools and techniques}): yet another rehash
+ of q-protect, following further input from john harper
+
+2007-11-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add pkfix-helper
+ * faqbody.tex (subsection{Mathematics}): changed name of q-theoremfmt,
+ minor editorial work
+ (section{Hypertext and PDF}): mention pkfix-helper in q-pkfix
+
+2007-11-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add fontspec
+
+ * add-general.tex (subsection{Odds and ends}): tidy, ref fontspec pkg
+ in re. xetex use of fancy otf features, in q-osf
+
+2007-11-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (heading); today's date, add david kraus
+ (subsection{Tables of contents and indexes}): correct bug spotted by
+ david kraus, in q-tocbibind; also add example of koma options
+
+2007-11-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Odds and ends}): more work on q-osf
+
+ * faqbody.tex (subsection{Alternative document classes}): update norman
+ gray's link, add nicola talbot's and rob clark's, and expand all the
+ other links in q-poster
+ (section{Bits and pieces of (La)TeX}): remove assertions about matt
+ swift's doc-tex stuff in q-dtx -- auctex now does the job, says dak;
+ tidy tortuous ref to both q-mf and q-mp, now to work for narrow and
+ wide versions rather than \latexhtml
+
+2007-11-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (head): v3.17-1, today
+ (subsection{Document structure}): remove incorrect note about fncychap
+ docs in q-secthead (they're quite standard now)
+
+2007-11-08 [Released as 3.17]
+
+2007-11-07 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): extend reference to
+ nlct's tutorials page in q-man-latex
+
+ * faq.sty: change pdfpagemode to UseNone (but mailing ho for assurance)
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): typo in q-pk
+
+2007-11-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): update german minimal
+ example link
+
+2007-11-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.17, today
+
+ * sanitize.pl,texfaq2html: bring forward changes from -beta
+
+ * faqbody.tex (throughout): ensure all \dots have empty arg
+
+2007-11-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add xargs, xkeyval
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): discuss
+ xargs in q-twooptarg
+
+2007-10-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): reword
+ q-empty for clarity
+
+2007-10-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): editorial diddles
+ with q-dvi-bmp
+
+ * dirctan.tex: restore dviljk; pretend ghostscript is on free tree
+ (it will be, it will); make gv browse-only
+
+ * faqbody.tex (section{TeX Systems}): editorial work in q-editors
+ (section{TeX Systems}): two minor changes in q-commercial
+ (section{DVI Drivers and Previewers}): dviljk has reappeared
+
+2007-10-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): link to latest unsatisfactory
+ source for xemtex
+ (section{TeX Systems}): elide the mail address from atari listing in
+ q-texsystems
+
+ * filectan.tex: remove the protext entry (moved to dirctan for
+ symmetry reasons...)
+
+ * dirctan.tex: * the mactex entry, add protext
+
+ * faqbody.tex (section{Acquiring the Software}): rehash q-findfont
+ (section{Acquiring the Software}): mention ctan copies in q-cd
+
+2007-10-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): new link for troy
+ henderson's previewer in q-mfptutorials
+ (section{Documentation and Help}): and delete link to the metafun
+ tutorial, which seems to have vanished from the web :-(
+ (intro): today's date, add troy henderson
+
+2007-10-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): ref new askinclude in
+ q-conditional
+ (section{Acquiring the Software}): micro-edit of q-uploads
+
+ * filectan.tex: remove askinclude
+
+2007-10-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type 1 fonts}): update mtpro stuff for
+ mtpro2, incl providing working web link
+
+ * sanitize-beta.pl (sanitize_line): translate \par (one instance only!)
+
+ * faqbody.tex (section{Acquiring the Software}): add link to catalogue
+ set of licences in q-nonfree (rms' suggestion)
+
+ * filectan.tex: add cat-licences
+
+ * dirctan.tex: add kpfonts, minionpro, mnsymbol
+
+ * faqbody.tex (subsection{Adobe Type 1 fonts}): add kpfonts and
+ minionpro/mnsymbol
+
+2007-10-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add fouriernc
+
+ * faqbody.tex (subsection*{Origins}): extend the list to members of the
+ committee, thus reducing the confusion (in my mind) about who is/was
+ and who isn't/wasn't
+ (subsection{Adobe Type 1 fonts}): add web location for berthold horn's
+ paper, add thierry bouche, similarly, in q-psfchoice
+ (subsection{Adobe Type 1 fonts}): add fouriernc to list; add fontsite
+ garamond to the list of mathdesign fonts, in q-psfchoice
+
+2007-10-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): edit q-uploads
+
+2007-10-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): remove \xxx|...| forms of
+ \ProgName, \FontName, \Package, \Class, \Email, \mailto, \File and
+ \Newsgroup
+
+ * faqbody.tex (section{The joy of TeX errors}): remove last two
+ instances of \ProgName|...|, in q-8000
+ (throughout): remove last three instances of \Email|...|
+
+ * sanitize-beta.pl (sanitize_line): implement \ISBN*
+
+ * faq.sty: add \ISBN* (2 args) version, for ISBN10+ISBN13
+
+ * faqbody.tex (section{Documentation and Help}): use \ISBN* for tlc2
+ and tlgc2 (latter newly converted from original tlgc entry)
+
+2007-10-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): bits of editorial
+ work in q-adobetypen, q-resolns, q-fontname
+ (section{Acquiring the Software}): mention mirror.ctan.org in
+ q-archives
+
+2007-10-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): hack at q-dtx
+ (have asked dak about dtx in emacs...)
+ (section{Bits and pieces of (La)TeX}): minor editorial on q-whatenc and
+ q-ecfonts
+ (section{Bits and pieces of (La)TeX}): work on q-eps
+
+2007-10-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): rehash q-special
+ (section{Bits and pieces of (La)TeX}): minor editorial to q-hyphen
+
+2007-10-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): bit
+ more work on q-printvar
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): yet more
+ twiddling with q-protect
+
+2007-10-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): lots of hacking of
+ q-virtualfonts
+
+2007-10-12 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro tools and techniques}): new
+ q-printvar contributed by gernot hassenpflug
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): change to
+ q-protect developed from john harper's contribution
+ intro: v3.16z-4, today; add john harper to list of helpers
+
+2007-10-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add texbytopic
+
+ * faqbody.tex (subsection{Hyphenation}): tidy up alternatives at the
+ end of q-hyphoff
+ (subsection{Hyphenation}): mention \uchyph in q-wdnohyph
+ (section{Documentation and Help}): tex by topic now ctan in q-ol-books
+
+2007-10-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): remove latexhtml around
+ thanh's full name in q-whatpdftex
+ (section{The Background}): link to q-latextoplain from q-latexandplain
+ (section{The Background}): tidy up references to other projects,
+ add luatex in q-texfuture
+ (section{The Background}): replace last para of q-readtex
+ (section{The Background}): add \href to tug's web site in q-tug*
+ (section{The Background}): correct a couple of \luatex (capitalised)
+
+ * sanitize-beta.pl (sanitize_line): add def of \The (for thanh)
+
+2007-10-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add autolatex
+
+ * faqbody.tex (section{TeX Systems}): refer to makefile question in
+ q-editors, rather than just mentioning latexmk (not the only thing
+ wrong with that answer)
+ (subsection{Document management}): mention autolatex in q-make
+
+2007-10-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Spacing of characters and lines}): sanity
+ adjustment in q-flushboth ("latest version" was 2003)
+
+2007-10-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): q-biblatex from
+ add-general
+ (section{Current \TeX{}-related projects}): minor edit to q-luatex
+
+ * dirctan.tex: amsrefs now on m/l/c
+
+ * add-general.tex (subsection{Current TeX-related projects}): declare
+ that amsrefs is currently supported; while this seems true (as a
+ phenomenon) i wonder whether it's a good thing to rely on...
+
+ * faqbody.tex (section{Current TeX-related projects}): diddle with
+ q-xetex
+
+2007-09-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add dir excel2latex
+
+ * filectan.tex: remove the .zip distro of excel2latex
+
+ * faqbody.tex (section{Installing (La)TeX files}): reword text about
+ readme files in q-install-unpack
+
+2007-09-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): correct references to new installation qs
+
+2007-09-18 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16z-1, today
+ (section{Installing (La)TeX files}): bunch of answers from add-general,
+ replacing most of the section
+
+2007-09-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{You're still stuck?}): "carefule" corrected ;-)
+
+ * add-general.tex (subsection{Installing (La)TeX files}): lots of work
+ on q-what-tds and q-install-where, to clarify what's going on
+
+2007-09-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): more emphasis on ctan
+ supply of documentation, in q-gethelp
+ (subsection{Document management}): a bit extra on changes.sty in
+ q-changebar (whole question needs reviewing)
+ (section{Documentation and Help}): ctan supply of docs, again, in
+ q-man-latex
+
+2007-08-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): new q-entercompmode
+ and q-checksum from add-general
+
+2007-08-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): updated uk address for sciword
+
+2007-08-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add a warning about
+ mailing inappropriate people in q-gethelp
+ (section{Current \TeX{}-related projects}): the project is latex, not
+ latex3 -- correct some of the text of q-latex3
+ (subsection{Tables of contents and indexes}): mention the use of
+ \phantomsection in q-tocbibind
+
+ * dirctan.tex: amslatex-primer moved to info/amslatex/primer, now
+
+2007-08-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Odds and ends}): add ref to mathpazo on
+ ctan, in q-osf
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): new
+ q-figurehere from add-general
+
+2007-07-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of AllTeX}): restored "\" to
+ "acro" in q-virtualfonts
+
+2007-07-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): typo in
+ q-struttab, spotted by karl b
+
+2007-07-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): extend typo examples,
+ and tidy coding, in q-altabcr
+ (subsection{Tables, figures and diagrams}): rationalise, reduce range
+ of overlapping recommendations in q-tabcellalign
+
+2007-07-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add cmolddig, eco
+
+ * add-general.tex (subsection{Current TeX-related projects}): write
+ more on biblatex in q-biblatex
+ (subsection{Odds and ends}): mention vf access in q-osf
+
+2007-07-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): first
+ stab at new q-biblatex
+
+ * dirctan.tex: add biblatex and amsrefs; remove dvi2xx and dvilj4,
+ correct lollipop
+
+2007-07-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): editorial tidies of
+ q-writecls, mention clsguide.pdf
+
+2007-07-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-17, today; add axel sommerfeldt to list
+ (section{The joy of TeX errors}): add further text in q-hyperdupdest,
+ as suggested by axel sommerfeldt
+
+2007-06-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Odds and ends}): new q-osf
+
+2007-06-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v 3-16c-15, today; mention neto's input on numprint in
+ list of helpers
+
+ * dirctan.tex: add numprint
+
+ * faqbody.tex (subsection{Typesetting specialities}): mention numprint
+ in q-dec_comma
+
+2007-06-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add texlive
+
+ * faqbody.tex (section{TeX Systems}): add details of a mactex mailing
+ list in q-texsystems
+
+2007-06-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): mention fragility of \url in
+ q-verbwithin
+ (subsection{Typesetting specialities}): mention lack of robustness in
+ q-seturl, and explain use of \urldef to deal with the problem
+
+2007-06-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq.sty: yet another small typo (in the fail branch, this time)
+
+ * filectan.tex: add mil-short (gratzer's offering)
+
+ * faqbody.tex (section{Documentation and Help}): add gratzer's short
+ course to q-man-latex
+
+2007-06-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): editorial correction
+ of q-optionclash
+
+2007-06-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faq.sty: check for etex
+
+ * add-general.tex (subsection{Installing (La)TeX files}): add some
+ actual text to q-inst-tidy and q-what-tds
+ (subsection{The Joy of TeX errors}): new q-entercompmode
+
+2007-06-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): editorial
+ in q-install-where and q-inst-wlcf
+
+ * dirctan.tex: correct fptex link (even though nothing now uses it...)
+
+2007-06-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): flynn's classes.dtx
+ article now rev., in tub (q-writecls)
+
+2007-06-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): mention texshop in mactex distr,
+ in q-editors
+ (section{TeX Systems}): deal with oztex and cmactex's relation to os/x
+ (so far as i understand what's going on) in q-texsystems
+
+2007-05-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Generic macros and techniques}): complete
+ and clarify q-ovwtsym
+
+2007-05-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \xetex
+
+ * faq.sty: add \xetex
+
+ * faqbody.tex: v3.16c-15, today
+ (section{Current TeX-related projects}): xetex is available in texlive
+ and will be in miktex 2.7, mention bidi capabilities in q-xetex
+
+2007-05-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): extend and make less
+ abrupt the stuff of q-latextoplain
+
+ * add-general.tex (subsection{Installing (La)TeX files}): trying to bed
+ this set of answers down -- work on several of the questions
+
+2007-05-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-14, today
+ (section{Documentation and Help}): attempt to clarify q-minxampl
+
+2007-05-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): tidy the two
+ references to nicola talbot in q-man-latex
+
+2007-05-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-13, today
+ (subsection{Metafont fonts}): hack at q-getbitmap to hint that bitmap
+ fonts aren't really the world's prime concern any more
+
+2007-05-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Labels and references}): list zref's options
+ in q-nameref
+ (section{The joy of TeX errors}): correct error in q-errmissitem
+ (inserted yesterday at home :-( )
+
+2007-05-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): discuss lists inside
+ tables, in q-errmissitem
+
+2007-05-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): miktex stuff
+ given a bit of a going-over in q-install-where (plus a few
+ consequential changes
+
+ * sanitize-beta.pl (sanitize_line): add \textbackslash{}
+
+2007-05-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Lists}): expand details of enumitem in
+ q-complist
+
+2007-05-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Lists}): expand on enumitem stuff in
+ q-interruptlist (it _does_ allow nested interruptions ... sort of
+
+2007-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-12, today
+ (subsection{LaTeX macro programming}): new q-latexqual from add-general
+ (subsection{Mathematics}): new q-mathonlyref from add-general
+
+2007-05-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Macros for using fonts}): mention that eplain
+ doesn't do font selection in q-fonts-pln
+ (subsection{LaTeX macro tools and techniques}): editorial on q-atsigns
+
+2007-05-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html-beta: use &[lr][sd]quo; in decorating text
+
+ * dirctan.tex: add pdcmac
+
+ * faqbody.tex (subsection{Macros for using fonts}): mention pdcmac in
+ q-fonts-pln
+
+2007-05-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * locations.mk: correct path to cgi, tidy
+
+2007-05-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-beta: escape characters in keyword strings
+
+ * sanitize-beta.pl (sanitize_line): add \extension
+
+ * faqbody.tex (section{The joy of TeX errors}): mention grffile package
+ in q-unkgrfextn
+
+ * faq.sty: add \extension command
+
+ * faqbody.tex: v3.16c-11, today
+
+2007-05-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-beta: redo decoding of % in code reading switches
+
+ * faq.sty: correct typo
+
+2007-04-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add pictex(!) and texlive
+
+ * faq.sty: add def of \texlive
+
+ * faqbody.tex: v3.16c-10, today
+ (subsection{Alternative document classes}): add a pointer to context
+ resources in q-slidecls
+ (throughout): typeset variants of texlive -> \texlive{}
+
+2007-04-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: remove tetex-beta, tetex to point at obsolete/ tree
+
+ * filectan.tex: add bibtex-faq
+
+ * faqbody.tex (subsection{Page layout}): mention ar scaling issues in
+ q-papersize, and tidy rest of text, too
+ (section{Documentation and Help}): remove unnecessary conditionals in
+ q-gethelp
+ (section{Documentation and Help}): tidy q-bibtexing, add reference to
+ btxfaq
+
+2007-04-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * Makefile (inst-perl[-beta]): everything on standard web server, use
+ cp -p instead of copy -t, adjust help
+
+2007-04-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: version 3.16c-9, today
+ (subsection{Footnotes}): rewrite answer q-ftnsect
+ (section{TeX Systems}): update bluesky information in q-commercial
+
+2007-04-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): stick some
+ text in q-install-doc
+
+2007-04-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): further
+ clarification of options in q-install-find
+ (subsection{Installing (La)TeX files}): flesh out answer
+ q-install-unpack, elaborating on what appears in q-dtx
+ (subsection{Installing (La)TeX files}): new q-install-doc placeholder
+
+ * faqbody.tex: v3.16c-8, today
+ (subsection{Tables, figures and diagrams}): tidy up refs to ltxtable in
+ q-fixwidtab
+
+2007-04-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * newfaq-patch.tex: add patch option to \documentclass
+
+ * faq.cls: deal with option patch, produce different page footer if so
+
+2007-04-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Footnotes}): mention bigfoot in q-multfoot
+
+2007-03-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): correct
+ \dots (with no {}) in q-ltxabbrv
+
+2007-03-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-7; remove all references to package web2c
+
+2007-03-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: remove web2c, web2c*
+
+ * filectan.tex: remove unixtex.ftp, correct protext
+
+2007-03-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): tops-20 ftp link regularised
+ (section{Acquiring the Software}): redo description of ctan sites,
+ with alternative versions for hyper (wide) and non-hyper (narrow)
+ version in q-archives
+
+ * sanitize-beta.pl (sanitize_line): \FTP to accept braced args only
+
+2007-03-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): another thrash at q-texsystems
+
+2007-03-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c, today
+ (throughout): remove traces of tetex, and rewrite as necessary
+
+2007-03-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): redo q-cd to talk
+ about the tex collection, rather than just tex live
+ (section{TeX Systems}): work (so far) on unix, linux and win32
+ (win32 contains a line of "+++..." to follow on with)
+
+2007-03-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-5, today
+ (section{The Background}): 2^16->2^15 in q-etex (!)
+ (subsection{Why shouldn't I?}): replace q-newfont with q-newfont* from
+ add-general
+ (subsection{LaTeX macro tools and techniques}): replace q-plninltx with
+ q-plninltx* from add-general
+ (subsection{LaTeX macro programming}): new q-fontsize from add-general
+ (subsection{Footnotes}): new q-run-fn-nos from add-general
+
+2007-03-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-beta: attempts at introducing some sanity into the
+ search code; notably unsuccessful, to date
+
+ * add-general.tex (subsection{Odds and ends}): proof-reading
+ corrections in q-run-fn-nos, q-newfont*, q-plninltx* and q-fontsize
+
+2007-03-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2file: as for texfaq2html-beta
+
+ * texfaq2html-gamma: as for texfaq2html-beta
+
+ * texfaq2html-beta: add new *-names to %label_to_file
+
+ * add-general.tex (subsection{Odds and ends}): new q-fontsize,
+ q-plninltx* and q-newfont* (three questions from the old 2 non-*)
+
+2007-03-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * CHANGES-3.16d: revised q-running-nos
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): restore
+ commented-out hack above q-ltxabbrv; it's not clever and it's not
+ pretty, but the printed output is less awful than without the hack
+
+2007-03-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro programming}): recommend chngctr
+ first, the two fragment alternatives second in q-running-nos
+
+ * add-general.tex (subsection{Footnotes}): new q-run-fn-nos
+
+2007-03-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: modest doodling
+
+2007-02-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): odd tinkering
+ with answers in this section -- needs concerted attack
+
+2007-02-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Odds and ends}): new q-fontsize, to meld
+ with (new) q-plninltx* and q-newfont*
+
+ * faqbody.tex (section{Current TeX-related projects}): make mention of
+ lua itself in q-luatex into a hyperref
+
+2007-02-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faq.sty: add \LuaTeX
+
+ * faqbody.tex: v3.16c-4, today
+ (section{The Background}): rewrite of q-context from Aditya Mahajan
+ (intro): Aditya Mahajan in list of helpers
+ (section{Current TeX-related projects}): tidy luatex thing a bit, add
+ link to luatex.org site
+
+2007-02-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): correct typo in q-limits
+ (introduced, but change not documented, on 2007-01-30)
+
+ * add-general.tex (subsection{Mathematics}): new q-mathonlyref
+
+2007-01-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Mathematics}): more detail about "ad hoc" operators in
+ q-newfunction
+
+2007-01-26 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Introduction}): make links to pdf copies \CTANhref
+
+2007-01-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add changes
+ remove nonfree from bakoma-tex, dvi2tty, foiltex
+
+ * faqbody.tex: today's date
+ (subsection{Document management}): mention changes pkg in q-changebars
+
+2007-01-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: list listbib and biblist
+
+ * faqbody.tex: today's date
+ (subsection{Manipulating whole bibliographies}): mention listbib and
+ biblist in q-nocite*
+
+2007-01-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * newfaq-patch.tex: input additions (!)
+
+ * faqbody.tex (section{Documentation and Help}): correct ctan ref for
+ pictex-summary
+
+2007-01-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c-3, today
+ (subsection{Spacing of characters and lines}): mention microtype's
+ letterspace.sty in q-letterspace
+
+2007-01-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * patchdates.tex: pl4.14, today
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-checksum
+
+2006-12-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add pictex-summary
+
+ * faqbody.tex: v3.16c-2, today
+ (section{Documentation and Help}): pictex summary in q-docpictex
+
+2006-12-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Support Packages for TeX}): correct text about
+ ispell vs. aspell
+
+2006-12-18 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ *** released ***
+
+ * Makefile ($(WEB_BETA)*): use cp rather than copy (!)
+
+ * sanitize.pl (sanitize_line): add \narrowonly, \wideonly
+
+ * faqbody.tex: v3.16c-1, today (for release)
+
+2006-12-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * letterfaq.tex: do the single column trick here too, for letterfaq.pdf
+
+2006-12-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (everything up to section{Graphics}): use \Qref* when
+ appropriate, using \narrowonly, \wideonly as necessary
+
+ * sanitize-beta.pl (sanitize_line): deal with \narrowonly, \wideonly
+
+ * faq.sty: define \narrowonly, \wideonly
+
+2006-12-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): major edits to q-acrobat,
+ following cogent comments from karl berry
+ (section{Hypertext and PDF}): liberal use of \qref* makes q-dvips-pdf
+ more nearly comprehensible, when read as pdf
+
+ * dirctan.tex: add dvipdfmx, gv
+
+ * newfaq-patch.tex: make pdf output single column, as in newfaq.tex
+
+2006-12-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16c
+
+ * faq.sty: bludgeon \CTANhref in pdf mode
+
+ * faqbody.tex: v3.16b-6, today
+ (subsection{Document structure}): put titlesec and sectsty into
+ different paras, offer rationale for choice om q-secthead
+ (subsection{LaTeX macro tools and techniques}): mention \@dblarg in
+ q-oarglikesect
+
+2006-12-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * filectan.tex: shiny new *longer* path for btxmac
+
+2006-12-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): correct typos in
+ ctanrefs in q-music
+
+2006-12-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating citations}): correct reed.edu link,
+ thanks to barbara b
+
+2006-11-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): make an itemised
+ list of alternative styles in q-citeurl, add babelbib to list
+
+2006-11-28 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): add two more
+ examples in q-bibprefixsort
+
+2006-11-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16b-5, today
+ (section{Documentation and Help}): reference kmf's page about pgf/tikz
+
+2006-11-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16b-4, today
+ (subsection{Spacing of characters and lines}): \linestretch ->
+ \linespread (per ulrike fischer) in q-linespace
+
+2006-11-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): correct sciword uk phone nos in
+ q-commercial
+
+2006-11-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add everypage and draftwatermark; correct wd2latex,
+ remove wasy and xymtex
+
+ * faqbody.tex (subsection{Page layout}): mention draftwatermark (and
+ its everypage) in q-watermark
+
+2006-11-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): ctan ref for mptopdf
+ in q-mpprologues
+
+ * dirctan.tex: add pdftex-graphics
+
+ * faqbody.tex (section{The joy of TeX errors}): mention "h" response
+ in q-optionclash
+
+2006-11-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Floating tables, figures, etc.}): new
+ q-figurehere
+
+2006-11-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (preamble): today's date; input archive.cfg regardless of
+ whether we're using pdf
+
+ * faq.sty: yet more baroquery towards \CTANhref
+
+2006-11-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): ref to vis faq in "how to use"
+
+ * faq.sty: new command \CTANhref works for dvi version so far;
+ no longer requires \Status for pdf working, uses ifpdf pkg instead;
+ a fair bit of more minor tidying
+
+2006-11-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): example
+ code in {quote} in q-vertspacefloat and q-mcfloat
+
+2006-11-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention the
+ case of multirow-multicolumn in q-multirow
+ (subsection{"Generic" macros and techniques}): new q-isdef from
+ add-general
+
+2006-11-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): correct \cmdinvoke{c}{arg1}{arg2}
+ sanitize.pl (sanitize_line): -beta works, so correct here too
+
+06-11-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): bunch
+ of editorials in q-isdef
+ (subsection{"Generic" macros and techniques}): tidy narrow layout of
+ example, add wide version and hack at words a bit in q-ovwtsym
+
+2006-10-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Generic macros}): \csx{relax} in place of
+ \relax(!) in q-isdef
+
+ * dirctan.tex: add pspicture
+
+ * faqbody.tex (section{Graphics}): correct ctan ref for pspicture
+
+2006-10-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, v3.16b-3
+ (subsection{LaTeX macro programming}): dot \makeat* liberally around
+ examples in q-running-nos
+
+2006-10-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): draftcopy doesn't work with
+ pdflatex (in q-watermark)
+
+2006-10-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: version 3.16b-2, date now iso format (with hyphens)
+
+ * patchdates.tex: pl4.13, date now iso format (with hyphens)
+
+ * add-general.tex (subsection{Generic macros and techniques}): new
+ q-ovwtsym from a post by enrico gregorio (latest instance of an
+ oft-repeated answer)
+
+2006-10-05 Robin Fairbairns <rf10@pb000.cl.cam.ac.uk>
+
+ * Makefile.CTAN: basis of mechanism to install CHANGES files
+
+2006-10-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * texfaq2html: sigh...merge in intro patch from texfaq2html-beta
+
+ * dirctan.tex: add figflow
+
+ * faqbody.tex: v3.16c, today
+ (subsection{Tables, figures and diagrams}): add figflow for plain, tidy
+ some of the ghastly verbatim in q-textflow
+
+2006-10-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.16b-1, today
+ (section{Format conversions}): correct address for stil, in q-sgml2tex
+
+2006-10-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): updates from -beta
+
+ * faqbody.tex: v3.16b, today
+
+2006-09-28 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{``Generic'' macros and techniques}): new
+ q-isdef
+
+ * sanitize-beta.pl (sanitize_line): move \csx before text shape
+ changing commands, so we can have emphasised control seqq
+
+2006-09-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro programming}): misspelling of
+ corrollary (over and over again) in q-addtoreset
+
+2006-09-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): reference testflow in
+ q-dvips-pdf
+ (section{Documentation and Help}): link to q-dvips-pdf in tutbitslatex
+ (section{Hypertext and PDF}): trivial editorials in q-acrobat
+ (section{Documentation and Help}): remove caveat about epslatex in
+ q-tutbitslatex
+
+2006-09-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16a-6, today
+ (section{Documentation and Help}): add the word "minimal" (to assist
+ searching - suggestion from brooks moses) and tidy q-minxampl a bit
+ (section{The joy of TeX errors}): new q-optionclash from add-general
+
+2006-09-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): mention
+ nicola talbot's experimental jpgfdraw in q-poster
+
+2006-09-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): rewrite q-texinfo
+
+2006-09-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): yet more fun
+ with q-optionclash
+
+ * faqbody.tex: v3.16a-5, today
+ (throughout): t1 and ot1 done consistently (remains to check other
+ encodings like t2 series, etc)
+ (section{Installing AllTeX files}): correct \latinfamily in
+ q-instt1font
+
+2006-09-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): rewrite
+ recommendations for q-optionclash
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): add
+ \makeatletter to example in q-ltxcmds
+
+2006-09-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): add
+ q-optionclash
+
+2006-08-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * check-ctan-lists: add miktex-setup to list of known links
+
+ * dirctan.tex: correct dvipaste
+
+ * filectan.tex: correct miktex-setup, metafp-pdf
+
+2006-08-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): q-omegaleph tidy-ups in
+ q-texfuture, q-books, q-texsystems
+ (section{Current TeX-related projects}): q-omegaleph and q-luatex from
+ add-general
+
+2006-08-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): minor
+ editorial on q-luatex
+
+ * faqbody.tex (section{The Background}): typo in q-whatpdftex
+
+2006-08-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16a-4, today
+ (section{Bits and pieces of (La)TeX}): rehash q-virtualfonts
+
+ * faq.sty: make \htmlonly careful about spacing (thought experiment led
+ to this -- don't know that it's actually a concern)
+
+2006-08-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: lots more diddling (trying to get all keys into a
+ hash, and working from there ... not successful)
+
+ * faqbody.tex (section{Graphics}): suggestion from donald for \raisebox
+ alignment of graphics in q-topalign
+
+2006-08-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: yet more thrashing about
+
+ * faqbody.tex (section{The joy of TeX errors}): other reasons for the
+ error in q-hyperdupdest
+ (_the_ list): add iain murray
+
+2006-08-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: further extension of yesterday's fun; added
+ ?intro(duction) [needs work on texfaq2file] and more debugging
+
+ * add-general.tex (subsection{Current TeX-related projects}): tidy
+ q-omegaleph, extend q-luatex and (hopefully) make it more coherent
+
+2006-08-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): new
+ questions (rather, bases for questions) q-omegaleph and q-luatex
+
+ * faqbody.tex: version 3.16a-3, today
+ (section{TeX Systems}): different instructions for miktex installation
+ in q-texsystems
+ (subsection{Footnotes}): change ctan link for perpage in q-footnpp
+ (subsection{LaTeX macro programming}): change ctan link for perpage in
+ q-addtoreset
+ (subsection{Typesetting specialities}): mention lilypond in q-music
+ (subsection*{Origins}): add comment to contributor entry about dak,
+ remove the silly footnote about full stops
+
+ * filectan.tex: correct epsf (should be link to dir?), metafp,
+ metafont-for-beginners, miktex-setup (not *right*...); delete
+ miktex-install, perpage
+
+ * dirctan.tex: correct arabtex, cellspace, dvipaste pst-pdf, texindex;
+ add epsf
+
+ * faqbody.tex (subsection{Common misunderstandings}): spelling error in
+ q-paraparam
+
+ * texfaq2html-gamma: done a debugging session; add search-box
+ switching; add a modicum of doc in comments; allow to be run from
+ command line (editable pointer)
+
+ * faqbody.tex (section{Introduction}): capa_bi_lities (!)
+
+2006-08-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16a-2, today
+ (section{Documentation and Help}): add tug font resources to
+ q-tutbitslatex
+
+2006-08-07 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): correct spelling of separate & derivatives
+
+ * add-general.tex (subsection{LaTeX macro programming}): new
+ q-latexqual for nag, texidate
+
+ * dirctan.tex: add a (multilingual, as it were) browsable l2tabu
+
+2006-08-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): correct
+ typo in, and editorial on q-atsigns
+
+ * sanitize-beta.pl (sanitize_line): translate \LaTeX{} (!)
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): correct
+ sample code and slick up descr slightly, in q-minitoc
+ (subsection*{Origins}): mention Jean-Pierre Drucbert in _the_ list
+
+2006-08-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): delete doubling of "the" (!)
+
+2006-08-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): rewrite the note
+ about maths fonts in q-ecfonts
+
+2006-08-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): tweak wording
+ slightly
+
+ *** release 3.16a ***
+
+2006-07-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: separate section for searches, trim final else
+
+ * faqbody.tex (section{The Background}): correct current mf version no
+
+2006-07-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16a, today
+
+2006-07-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): extend q-filename with
+ a simpler file-name saver, and show how to strip .tex from fink
+ filenames
+
+ * texfaq2html-beta: more careful about \section test for end of intro
+
+2006-07-07 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): stupidity
+ in q-cmdstar, spotted by Kasper van den Berg
+
+2006-07-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Lists}): typo in q-enumerate spotted by
+ Samuel Lelievre
+
+2006-06-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.16, today
+
+ * sanitize.pl: bring up to date with sanitize-beta.pl
+
+ * texfaq2html-gamma: remove %SymbolChar table
+
+ * faqbody.tex (section{Documentation and Help}): typo in q-tutbitslatex
+ (wideversion only, so only now detected)
+
+2006-06-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Creating citations}): q-whatbst from add-general
+ (subsection{Macros for using fonts}): (new subsection) q-fonts-pln from
+ add-general
+ (section{Graphics}): new q-repeatgrf from add-general
+
+ * add-general.tex (subsection{Creating bibliographies}): proof-reading
+ corrections of q-whatbst
+
+2006-06-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Fonts}): proof-reading corrections in
+ q-fonts-pln
+ (subsection{Graphics}): proof-reading corrections in q-repeatgrf
+
+2006-06-28 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): mention dvips version, and
+ add missing pdf bit in q-repeatgrf
+
+2006-06-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): mention graphicx-psmin
+
+ * dirctan.tex: add graphicx-psmin
+
+2006-06-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): first stab at
+ body for q-install-find
+
+ * faqbody.tex: today's date
+ (subsection{Common misunderstandings}): new q-gutter from add-general
+ (subsection{Common errors}): new q-matchbrak from add-general
+
+2006-06-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): skeleton of
+ new installation question structure
+
+2006-06-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): editorial tidying of q-graphicspath
+ plus emphasise the need for trailing slash on \graphicspath dirs
+ (section{Graphics}): minor editorial in q-graph-pspdf q-mpprologues too
+ (subsection{Creating bibliographies}): editorials on q-bibstrtl
+
+2006-06-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): deal with \subsection* (i.e.,
+ ignore it, for intro \latexhtml command)
+
+ * faqbody.tex: version 3.16alpha, today
+ (section{Introduction}): rearrange to limit the amount we need to show
+ on the web by default
+
+2006-06-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date -- rehash the intro
+
+2006-06-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): actual text for
+ q-gutter
+
+ * additions.tex: let's change patch version and date, for once!
+
+2006-06-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): add smith's latex for logicians to
+ q-tutbitslatex
+ (section{TeX Systems}): make ref to w32tex, move dos & os/2 offerings
+ down below win32 in the doc (q-texsystems)
+
+2006-06-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): comment-out
+ q-dvipdfmgraphics* -- seems to have been a mistake
+
+ * faqbody.tex (subsection{Page layout}): restructure the list of
+ related answers in q-changemargin with an intersticial remark
+ (subsection{Page layout}): develop and extend q-chngmargonfly
+
+2006-06-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date in preamble
+ (subsection{Page layout}): split Q-changemargin into intro and 3 bits
+ of detail
+
+2006-06-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): a huge start on
+ new q-gutter (i.e., wrote \Question command)
+
+ * faqbody.tex (subsection{Page layout}): start of rehash of
+ q-changemargin
+
+2006-06-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add cellspace
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention
+ cellspace in q-struttab
+
+2006-06-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): give framed a
+ paragraph of its own in q-changebars
+
+2006-06-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): no longer mention
+ troff-to-latex in q-fmtconv
+
+ * dirctan.tex: add moderncv
+ chappg,mathdots,shade from filectan; correct pst-pdf; delete tr2tex,
+ troff-to-latex
+
+ * faqbody.tex (subsection{Alternative document classes}): refine the
+ statement about europecv, in q-cv
+ (section{TeX Systems}): redo note on y&y in q-commercial
+ (subsection{Alternative document classes}): mention moderncv in q-cv
+
+2006-05-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): simplify q-xetex
+ and mention xetex for linux
+ (section{Current TeX-related projects}): remove q-pdftex
+
+ * faq.sty: another iteration of ctanrefs: sanitising isn't right, since
+ we often have real commands in there, so use \scantokens -- which
+ means we need always to use an e-tex
+
+ * faqbody.tex (subsection{Document structure}): "simple minded" example
+ now no longer uses 2.09 fonts in q-secthead
+
+2006-05-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): add qualifier to actions of
+ distributors in q-triptrap
+
+ * dirctan.tex: add a2ping, sam2p
+
+ * faqbody.tex (section{Graphics}): tidy q-dvipsgraphics, add
+ sam2p/a2ping as alternatives for bitmaps
+
+2006-05-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Fonts}): new q-fonts-pln
+
+ * faq.sty: \@onelevel@sanitize \item args in ctanrefs env
+
+ * dirctan.tex: add ec-plain, font_selection, fontch, plnfss and ofs
+
+ * faqbody.tex (section{TeX Systems}): stupid logo macros in xemtex
+ description
+
+2006-05-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add labelcas
+
+ * faqbody.tex (subsection{Alternative document classes}): get q-poster
+ from add-general
+ (subsection{Why shouldn't I?}): get q-newfont from add-general
+ (subsection{LaTeX macro programming}): mention labelcas package in
+ q-labundef
+
+ * add-general.tex (subsection{Alternative document classes}): mention
+ multicol for "unadorned" a0poster-posters in q-poster
+
+ * faqbody.tex: today's date
+ (section{Bits and pieces of (La)TeX}): tidy up (and extend) q-ecfonts
+
+2006-05-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Acquiring the Software}): mention bytopic.html in q-findfiles
+
+2006-05-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Alternative document classes}): q-poster
+
+ * dirctan.tex: add sciposter, a0poster, flowfram
+
+2006-05-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): add chris harrison's book to
+ q-man-latex
+
+2006-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Current TeX-related projects}): add \href to berlios site, and
+ make link to CTAN rather than old site
+
+2006-05-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): elide all reference to
+ "quote site index" from q-findfiles
+
+2006-04-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{LaTeX macro programming}): correct recipe given in
+ Q-seccntfmt
+ (section{Installing (La)TeX files}): correct link to map update stuff
+ in miktex in q-instt1font and q-uselmfonts
+
+2006-04-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): yet another tidying of \cmdinvoke
+
+2006-04-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): mention tex-ptr-faq in
+ q-wherefaq
+ (section{You're still stuck?}): correct bnb's address in q-bug
+
+2006-04-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): annotation at end of
+ q-noline to mention other instances that could need covering
+
+2006-04-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): mention bernard
+ gaulle's faqs in q-wherefaq; emphasise that the fr.c.t.t one is no
+ longer in the land of the living [check!]
+
+2006-04-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new q-matchbrak
+
+2006-04-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): new q-doc-wiki from add-general
+ (section{Documentation and Help}): link q-doc-wiki in q-tutorials*
+ (section{The Background}): new q-whatpdftex from add-general
+ (throughout): refs to q-pdftex -> q-whatpdftex
+
+2006-03-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+
+ * sanitize-beta.pl: couple of changes to introduce quoteverbatim
+
+ * faq.sty: add quoteverbatim environment, for verbatim output of
+ verbatim environments (used by new q-verbwithin, of course)
+
+ * examples/verbwithin.tex: new file
+
+ * faqbody.tex (subsection{Common errors}): extend description of
+ failures of verbatim environment, in q-verbwithin
+
+2006-03-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): new address for pstricks site in
+ q-drawing and q-labelfig
+
+ * dirctan.tex: remove ps4pdf, add pst-pdf
+
+ * faqbody.tex: today's date
+ (section{Graphics}): ps4pdf->pst-pdf in q-pdftexgraphics, new address
+ for hv's web stuff
+
+2006-03-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * locations.mk: add HTMLDIR, HTMDIR_GAMMA and GAMMADIR
+
+ * Makefile: remove inst-html target, add inst-gamma
+
+ * sanitize-beta.pl (sanitize_line): translate both double and single
+ quotes to entities
+ (sanitize_line): make \end{quote} issue a <p> for the benefit of the
+ css mechanisms in -gamma
+
+ * texfaq2file: use sanitize-beta
+
+ * add-general.tex (subsection{The Background}): iterate q-whatpdftex
+
+2006-03-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): braces around
+ \multirow *s (distinction without a difference...)
+
+2006-03-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): update details for wheildon in
+ q-typebooks
+
+2006-03-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Creating bibliographies}): minor rewording of q-bibinline
+
+2006-03-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): deal with dviversion and pdfversion
+ (sanitize_line): deal with --- => &mdash; -- => &ndash;
+
+ * faqbody.tex: today's date on first line
+ (section{Documentation and Help}): mention visualFAQ in q-wherefaq
+
+ * filectan.tex: add visualFAQ
+
+ * faqbody.tex (section{The Background}): yet another minuscule
+ iteration of q-texpronounce
+
+2006-03-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): mention .pool, .fmt,
+ .base and .mem locations, tidy text a bit, in q-wherefiles
+
+2006-03-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): typo in q-changebars
+ (section{Creating citations}): tidy up q-bibinline a bit more
+
+2006-02-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): cut q-dvips down
+ to its bare bones (whole section needs a going-over)
+ (subsection{Hyphenation}): correct typo in q-hyphexcept
+
+2006-02-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Creating citations}): sort out *my*
+ understanding of footbib, in q-bibinline
+
+2006-02-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): mention urs oswald's
+ things in q-mfptutorials
+
+2006-02-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro programming}): mention the
+ koma-script facilities in q-oddpage
+
+2006-02-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Common errors}): "typeset" page number rather than
+ "set" page number in q-wrongpn
+ (subsection{Creating bibliographies}): remove snide comment about
+ tex2bib documentation -- it's standard now
+
+2006-02-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * README: try to avoid the contradictions; may need to take poli's
+ advice more nearly wholesale...
+
+ * faqbody.tex: today's date
+ (section{Graphics}): redo ref to epslatex in q-impgraph
+
+ * filectan.tex: ref epslatex -> epslatex_pdf
+
+ * faqbody.tex (section{Documentation and Help}): mention zoonekynd's
+ series in q-tutbitslatex, and reorganise references to epslatex (given
+ we're supposed to have source rsn)
+
+2006-02-20 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Graphics}): mention psfragx in q-labelfig
+ (section{Bits and pieces of (La)TeX}): mention "eps" as an abbr,
+ in q-eps (seems it's never previously been used!)
+
+2006-02-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{You're still stuck?}): improve layout of q-noans, tidy
+ text a bit
+
+ * filectan.tex: add xampl-bib
+
+ * add-general.tex (subsection{Creating bibliographies}): new q-whatbst
+
+ * faqbody.tex (section{Graphics}): mention tikz in q-drawing
+
+2006-02-14 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Adobe Type~1 fonts}): minor typo in q-usepsfont
+ (subsection{Common errors}): breakurl patches \url by default in
+ q-breaklinks
+ (section{Introduction}): add vilar camara neto to list
+
+2006-02-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today, note more input from ulrike f
+ (subsection{LaTeX macro tools and techniques}): extend \DefaultOpt
+ example in q-oarglikesect
+
+2006-02-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, note chris walker's further contribution
+ (subsection{Mathematics}): add \operatorname to q-newfunction
+
+ * dirctan.tex: add ite
+
+ * faqbody.tex (section{Graphics}): correct pstricks homepage link,
+ and add reference to ite in q-labelfig (Chris Walker)
+
+2006-02-06 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Getting things to fit}): re-describe mathspic
+ to tally with current reality
+
+ * dirctan.tex: correct paths of mathspic, bdfchess
+
+ * filectan.tex: correct tex2bib paths (2 off)
+
+2006-02-06 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Documentation and help}): new q-doc-wiki
+
+ * faqbody.tex (subsection{Lists}): mention multenum in q-complist
+
+ * dirctan.tex: add multenum
+
+2006-01-29 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): correct url (and name)
+ for the note on ptex in q-tutbitslatex
+
+2006-01-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): gosh -- a mention of
+ quote site index, still...removed from q-findfiles
+
+2006-01-10 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): hack around
+ at the text about includex, and add newclude
+
+2006-01-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add rotfloat
+
+ * faqbody.tex: today's date
+ (subsection{Page layout}): mention rotfloat in q-rotating
+
+2005-12-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): mention verbatim environment
+ in the intro to q-verbwithin
+
+2005-12-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Background}): new q-whatpdftex (just
+ a start, so far)
+
+ * faqbody.tex (section{Graphics}): change title of "making \mp output
+ display..."
+
+2005-12-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, v3.15b
+
+2005-12-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): remove rogue character on keywords
+ line
+
+ * faqbody.tex (subsection{Page layout}): restore lost text to
+ q-parallel (from RCS file :-})
+
+2005-12-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: add ttb-pdf
+
+ * faqbody.tex (section{Documentation and Help}): add ttb to q-bibtexing
+
+2005-12-05 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: add bidstobibtex
+
+ * faqbody.tex (subsection{Creating bibliographies}): make ref to
+ bids.to.bibtex in q-buildbib
+
+2005-11-30 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): new url for andy
+ roberts' latex page
+
+2005-11-29 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): remove code for \symbol
+
+ * faqbody.tex (section{Current TeX-related projects}): correct links in
+ q-latex3
+ (section{TeX Systems}): remove fptex, add xemtex
+ (section{Acquiring the Software}): replace fptex with protext in q-cd
+ (throughout): remove all remaining fptex options
+ (subsection{"Generic" macros and techniques}): don't use \symbol in
+ q-activechars
+ (subsection{Common errors}): do away with \symbol for underscore in
+ q-verbwithin (also rename \bs to \us for underscore, in the example)
+
+*** RELEASE 3.15 ***
+
+ * sanitize.pl,sanitize-beta.pl: attempts to solve the $symbolchar
+ lunacy (failed)
+
+ * faqbody.tex: 3.15a, today's date (already: at 10am!)
+ (section{Symbols, etc.}): \_ for underscores in q-underscore
+ (section{Current TeX-related projects}): correct urls in q-latex3
+
+ * texfaq2html,texfaq2html-beta,texfaq2file: correct *-list
+
+ * sanitize.pl (sanitize_line): add changes from -beta
+
+2005-11-28 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add mactex
+
+ * faqbody.tex (subsection{Creating citations}): new q-formbiblabel from
+ add-general
+ (subsection{Tables, figures and diagrams}): new q-varwidcol from
+ add-general
+ (header): v3.15, today
+ (section{Documentation and Help}): suppress link to mimi's documentation
+ at fsu -- they've removed it already, the fools
+ (section{Documentation and Help}): add ref to memoir manual in
+ q-typo-style
+ (section{TeX Systems}): mention mactex on ctan
+
+2005-11-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * texfaq2file,texfaq2html,texfaq2html-beta,texfaq2html-gamma: add
+ maillists* to translation list
+
+ * faqbody.tex (section{Documentation and Help}): new q-maillists* from
+ the rest of the old q-maillists (leaving a few bits out, admittedly)
+
+2005-11-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): build q-gethelp from
+ the old q-maillists
+
+2005-11-25 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{The joy of TeX errors}): reword (not change) advice in
+ q-errmissitem
+ (subsection{Mathematics}): new q-brkinline from add-general
+ (section{Hypertext and PDF}): new q-srchpdf from add-general
+
+ * add-general.tex (subsection{Why shouldn't I?}): change recommendation
+ to fix-cm in q-newfont, but retain mention of type1cm/ec for old latex
+ dists
+
+ * filectan.tex: add fix-cm (path to file)
+
+2005-11-24 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro programming}): editorial work on
+ q-seccntfmt and q-labundef
+
+ * sanitize-beta.pl (sanitize_line): sort out order of \cmdinvoke*
+ patterns
+
+2005-11-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro programming}): emphasise internal
+ commands in q-seccntfmt
+ (subsection{LaTeX macro tools and techniques}): reword to avoid blame
+ on the companion, and to use a tlc2 example in q-atsigns
+
+ * filectan.tex: get abstract.bst from biblio/bibtex/utils/bibtools
+ rather than contrib
+
+2005-11-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: point lucida at new metrics, add lucida-psnfss
+
+ * faqbody.tex (subsection{Adobe Type~1 fonts}): reinstate lucida
+ bright/math and add link to karl's interim web page
+
+2005-11-21 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): iteration
+ of q-varwidcol
+ (subsection{Hypertext and PDF}): iteration of q-srchpdf
+
+ * faqbody.tex (section{Current TeX-related projects}): tinkering with
+ q-aleph (needs rewrite to eliminate ref to q-omega, which is destined
+ to go some time soon
+
+ * add-general.tex (subsection{Why shouldn't I?}): change link for
+ type1cm (shouldn't this be fix-cm?)
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): new
+ answer q-ltxhash from add-general
+ (subsection{LaTeX macro programming}): was (confusingly) described as
+ techniques, too
+ (section{The joy of TeX errors}): new q-errparnum and q-fllost from
+ add-general
+ (section{Bits and pieces of (La)TeX}): move q-hyphen up above q-dtx
+ (section{Bits and pieces of (La)TeX}): new q-clsvpkg from add-general
+
+2005-11-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): new
+ q-varwidcol
+
+2005-11-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): mention alternative
+ locations for .map files following new tds, bit of editorial work
+ (section{Documentation and Help}): reinstate link to bausum's stuff in
+ q-ref-doc
+
+2005-11-18 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: axodraw is a directory now
+
+ * filectan.tex: remove axodraw, correct finplain
+
+ * faqbody.tex (subsection{Common misunderstandings}): correct path for
+ textcase in q-casechange
+ (subsection{Tables, figures and diagrams}): correct path for tabulary
+ in q-tabcellalign and q-fixwidtab
+
+ * dirctan.tex: add tabulary,textcase
+
+ * faqbody.tex (section{The Background}): add q-etex from add-general,
+ and edit it a bit
+ (throughout): remove references to q-nts, in favour of q-etex
+ (section{Current TeX-related projects}): dump q-nts
+ (section{Current TeX-related projects}): rewrite antecedent text in
+ q-aleph
+
+ * add-general.tex (subsection{Graphics}): ref to q-tutorial ->
+ q-tutbitslatex in q-repeatgrf
+
+ * Makefile (PATCH): remove add-tutorial
+
+ * dirctan.tex: add cmap
+
+ * add-general.tex (subsection{Hypertext and PDF}): add q-srchpdf
+
+2005-11-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma,texfaq2html-beta,texfaq2html,texfaq2file: add
+ q-tutorials* to %label_to_file initialisation
+
+ * faqbody.tex: v3.14c, today's date
+ (section{Documentation and Help}): add reference to syropoulos' book
+ (section{Documentation and Help}): replace q-tutorials with
+ q-tutorials* and friends (fix up refs to q-tutorials from elsewhere)
+
+ * add-tutorial.tex (subsection{Documentation and help}): final
+ rearrangement and tidy; add the guide to ptex posted yesterday
+
+ * faq.sty: pdfstartview=FitH since FitBH seems no longer to work with
+ AR7 or the latest pdftex or something
+
+2005-11-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Introduction}): add steve peter to contributors
+ (throughout): bunch of corrections from steve peter
+
+2005-11-14 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faq.sty: load textcomp
+
+ * dirctan.tex: add mutex
+
+2005-11-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * README: remove my name and email address
+
+ * newfaq(-patch).tex,letterfaq.tex: null \author
+
+ * texfaq2html(-beta),texfaq2file: remove claim that i'm involved with
+ maintenance
+
+ * faqbody.tex (throughout): replace my name with "another idiot"
+
+2005-11-08 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-tutorial.tex (subsection{Documentation and help}): yet more
+ rearrangement
+
+2005-11-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.14b, today
+
+2005-11-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: bbl2html and notex.bst moved
+
+ * add-tutorial.tex (subsection{Documentation and help}): more
+ rearrangement
+
+2005-11-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Hyphenation}): correct def of \hyph in
+ q-nohyph, do a bunch of quote-env stuff in whole subsection; also,
+ more enthusiastic wrapping of the quote about catalan
+
+2005-10-26 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Mathematics}): mention bracing to
+ suppress breaks in maths
+
+2005-10-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): suggest \textstyle/
+ \displaystyle alternative for q-limits
+
+2005-10-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): extend q-breaklinks to cover
+ the toc/lof/lot... case, and to outline circumstances where there's no
+ help to be had
+
+2005-10-10 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: sort regex in opening of ?section= code
+
+2005-10-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): add the offered text to
+ q-acrobat; this question is a mess and needs rearranging (probably
+ splitting into two)
+
+ * dirctan.tex: remove aix3.2, move miktexppc, miktex-AXP
+
+ * texfaq2html-gamma: start work on index/fullindex switching
+
+ * texfaq2file: secondary index now full-index.html
+
+ * add-general.tex (subsection{Bits and pieces of (La)TeX}): new q-etex
+
+ * faqbody.tex: v3.14a.3, today
+ (section{TeX Systems}): mention texlive mac distro
+
+2005-10-03 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * texfaq2file: more of same
+
+ * texfaq2html-gamma: yet more twiddling
+
+ * filectan.tex: epsf.tex moved
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): add \nolinkURL
+
+2005-09-26 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: restructure q_label_list
+
+ * faqbody.tex (section{Current TeX-related projects}): correct web addr
+ in q-extex
+
+ * texfaq2file: iterate -w actions
+
+2005-09-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: patch and shade have moved
+
+ * texfaq2html-gamma: label argument may be a list
+
+2005-09-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: letterspacing,backgrnd moved
+
+05-09-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): minor edits in q-type1T1
+ (section{The Background}): revised q-eplain from Oleg Katsitadze
+ (<heading>): today's date, add katsitadze to credits
+
+ * dirctan.tex: remove icelandic, which we weren't using
+
+ * filectan.tex: mathdots has moved
+
+2005-09-16 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add luximono, microtype; move tip pointer
+
+ * faqbody.tex: today's date
+ (subsection{Document structure}): new first para for q-fancyhdr
+ (subsection{Common misunderstandings}): reword description of
+ \emergencystretch and discuss microtype in q-overfull
+ (subsection{Odds and ends}): add luximono to q-bold-extras
+
+2005-09-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add powerdot
+
+ * faqbody.tex (subsection{Alternative document classes}): mention
+ powerdot in q-slidecls
+
+2005-09-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: add \nolinkURL definitions
+
+ * add-general.tex (subsection{Graphics}): a proto-q-dvipdfmgraphics
+ redefinition (hrrumph)
+
+2005-09-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.14a.2
+ (section{Introduction}): mention that the texlive version is no better
+ than the "current on the web"
+
+ [interim web release 3.14a.1]
+
+2005-09-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{You're still stuck?}): faq-devel@tex.ac.uk in q-noans
+
+2005-08-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): all remaining miktex references via \miktex
+
+2005-08-10 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: correct pointers for the two epslatex entries
+
+ * faqbody.tex (section{Installing (La)TeX files}): text about mpm in
+ q-miktexinst (and convert to \miktex in that question, where
+ appropriate)
+
+2005-08-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): tidy
+ \htmlignore stuff in q-textflow
+
+2005-08-06 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add talk
+
+ * faqbody.tex (subsection{Alternative document classes}): add talk to
+ q-slidecls
+
+2005-08-05 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Bits and pieces of (La)TeX}): new answer
+ q-clsvpkg on the distinction between classes and packages
+
+ * faqbody.tex (section{Bits and pieces of (La)TeX}): change of section
+ name
+
+2005-08-02 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): try to avoid the acronym
+ ASCII except where necessary in q-toascii
+
+2005-08-01 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): minor editorial in
+ q-conditional
+
+2005-07-31 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-fllost
+
+2005-07-20 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{You're still stuck?}): warn about non-latex bug
+ reports in q-latexbug and q-bug
+ (intro) v3.14a.1, today
+
+2005-07-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * README: faq->faq-devel in email addrs, except munged one for me in
+ sig line at bottom
+
+ * faqbody.tex (subsection{Odds and ends}): remove "not doing away with
+ bumpy-road logos" comment, since i now have done so
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): sigh -- \\textless...
+
+2005-07-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): yet another iteration
+ of the < > translation fiasco
+
+2005-07-15 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add quotchap
+
+ * faqbody.tex (subsection{Page layout}): add quotchap to q-epigraph and
+ rewrite intro to question somewhat.
+
+2005-07-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{You're still stuck?}): faq->faq-devel in
+ q-newans
+
+ * sanitize.pl (sanitize_line): as -beta (now it's been tested ;-)
+
+ * sanitize-beta.pl (sanitize_line): sort out translations of <> when
+ not converting
+
+2005-07-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * Makefile: remove inst-html target
+ (FAQ-html.tar.gz): make depend on html/index.html (does this do it?)
+
+2005-07-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.14a, today
+ (subsection{Document management}): boondoggle in q-rcs html output
+
+ * faqbody.tex: v3.14, today
+ New version installed
+
+ * faqbody.tex (section{Introduction}): mention static .zip files in
+ html-only bit about retrieving directories
+ (section{Acquiring the Software}): remove exact location names for
+ individual ctans, in q-archives
+ (section{Acquiring the Software}): rewrite the stuff about searching in
+ q-findfiles
+
+2005-07-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): add fancyhdr commands (to do
+ empty plain style) to q-ps@empty
+
+ * texfaq2html-beta,texfaq2file: as texfaq2html
+
+ * texfaq2html: switch .tar.gz and .zip in retrieval
+
+2005-07-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): add q-wrongpn and
+ q-breaklinks from add-general
+ (preamble) v3.13b.5, today
+ (subsection{Footnotes}): rewrite q-ftncapt, aiming for clarity (hah!)
+ (section{Acquiring the Software}): remove mention of ftpmail and finger
+ of ctan user
+
+ * dirctan.tex: add breakurl
+
+ * add-general.tex (subsection{Why does it do that?}): mention breakurl
+ in q-breaklinks -- looks as if this makes the answer usable...
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): correct
+ blatant error in q-tabcellalign (spotted by ulrike fischer)
+ (section{Introduction}): hack the note about the pdf version slightly,
+ add ulrike fischer to list of contributors
+
+2005-07-01 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add ref to
+ http://www.latex-einfuehrung.de/ in q-minxampl
+
+2005-06-29 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): correct advice on
+ over-long urls and url.sty in q-citeurl
+
+2005-06-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.13b.4, tonight
+
+ * faqbody.tex (section{Introduction}): add chris walker
+ (section{Bits and pieces of TeX}): \Qref* in q-dtx
+ (subsection{Tables of contents and indexes}): \Qref* in q-tocloft
+
+ * dirctan.tex: add revtex(!)
+
+ * faqbody.tex (subsection{Creating citations}): note that mcite doesn't
+ play with revtex, in q-mcite
+
+2005-06-09 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention use
+ of pict2e in q-slashbox
+
+2005-06-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{You're still stuck?}): slight editorial in q-bug
+
+ * add-tutorial.tex: bunch of work, throughout, which seems not to have
+ been recorded or even copied to backed-up space before now...
+
+ * faqbody.tex (section{Installing (La)TeX files}): mention .map and
+ .enc trees, and alternative inputs such as .sto, .clo and .cfg in
+ q-wherefiles
+
+ * filectan.tex: add nextpage
+
+ * faqbody.tex (subsection{Document structure}): mention nextpage
+ package in q-reallyblank
+
+2005-06-02 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): mention pspicture as a superseded
+ package in q-drawing
+ (section{Documentation and Help}): slight iteration of q-pkgdoc
+
+2005-05-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Why shouldn't I?}): mention vertical spacing
+ inconsistencies in q-dolldoll
+
+2005-05-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): add philip
+ ratcliffe's fake-accent solution to q-bibtranscinit
+ (preamble): v3.13b.3 (ok, i don't know what i'm doing here...), today
+ (section{Introduction}): add philip ratcliffe to thanks list
+
+ * add-general.tex (subsection{Why does it do that?}): add q-wrongpn
+
+ * faqbody.tex (subsection{LaTeX macro tools and techniques}): renamed
+ subsection, moved q-oarglikesect and q-twooptarg from "latex macros"
+ (subsection{LaTeX macro tools and techniques}): change name to "more
+ than one opt arg"
+ (subsection{LaTeX macro tools and techniques}): new q-cmdstar, from
+ add-general
+
+2005-05-18 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add q-minxampl
+ from add-tutorial
+ (section{Documentation and Help}): ref to q-minxampl from q-askquestion
+ (section{You're still stuck?}): ref to q-minxampl from q-latexbug
+
+2005-05-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macro tools}): add q-plninltx (from
+ add-general), and split this of from the more simple stuff (now
+ subsection "latex macro techniques"); other ones in here are
+ q-atsigns, q-protect, q-edef, q-ltxcmds and q-ltxabbrv
+
+ * faq.sty: remove spurious guff at start of ctanrefs env (was solemnly
+ forcing horizontal mode, thus confusing \addvspace at start of list)
+
+ * add-general.tex (subsection{Creating citations}): add q-formbiblabel
+
+2005-04-29 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add splitbib
+
+ * faqbody.tex (section{References from articles}): mention splitbib in
+ q-multbib
+
+2005-04-28 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add placeins as a directory
+
+ * filectan.tex: change beginlatex to its latest incarnation
+ remove placeins
+
+2005-04-26 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faq.sty: make robust a few commands that get to appear in tocs
+
+2005-04-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * texfaq2file: put correct cross question links if -w
+
+ * texfaq2html-gamma: miscellaneous tidies from debugging session
+
+2005-04-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: add clsguide
+
+ * dirctan.tex: add makedtx
+
+ * faqbody.tex (section{Bits and pieces of TeX}): mention makedtx in
+ q-dtx; list clsguide.pdf in links
+
+2005-04-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type1 ("PS") fonts}): add mathdesign to
+ the list in q-psfchoice
+
+2005-04-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): correct
+ \csx{listfiles} to \Package{snapshot} (!) as data collection mech for
+ bundledoc, in q-filesused
+
+2005-04-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): minor editorial
+ to q-xspace
+
+2005-04-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): remove some text that's
+ crept in unawares to q-tmupfl
+
+2005-04-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-errparnum
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): a bit of
+ desultory macro-usage editing
+
+ * add-general.tex (subsection{LaTeX macro programming}): new q-ltxhash
+
+2005-03-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-tutorial.tex (subsection{Documentation and help}): (changed name
+ for the subsection) new answer q-minxampl
+
+ * Makefile (PATCH): add add-tutorial (can't we automate this?)
+
+2005-03-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): new q-errmissitem from
+ add-general
+ (section{Documentation and Help}): editorials on q-askquestion
+
+ * add-general.tex (subsection{LaTeX macro programming}): minor
+ editorial to q-plninltx
+
+2005-03-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: correct path to obsolete/support/undump; point
+ umlaute at the latex package (rather than support/); remove umlaut
+
+2005-03-24 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why shouldn't I?}): new q-newfont
+ (subsection{LaTeX macro programming}): use \font rather than \newfont
+ in examples in q-plninltx
+
+2005-03-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): lots more
+ fiddling with q-plninltx, including extending the font stuff
+
+2005-03-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): add example of
+ font encoding confusion arising from \newfont, in q-plninltx
+ (subsection{LaTeX macro programming}): have narrow/wideversion of one
+ example in q-cmdstar
+
+2005-03-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): mention javier's
+ checkend package in q-endingroup
+
+2005-03-01 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): editorial on
+ q-errmissitem, plus mention of \mbox, \makebox, \framebox
+
+2005-02-28 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Mathematics}): new q-brkinline
+
+ * sanitize-beta.pl (sanitize_line): convert \< (never used) to
+ \textless, \> (ditto) to \textgreater ... so now i can use the beasts
+
+ * add-general.tex (subsection{The Joy of TeX errors}): mention \section
+ as another case of misbehaviour in q-errmissitem
+
+2005-02-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: rewrite \href (non-hyper version) so as to get quoting
+ actually right, and not to lose trailing spaces...
+
+ * faqbody.tex (subsection{Typesetting specialities}): mention c2latex
+ in q-codelist (previously, the program was in ctanrefs only); also add
+ an actual recommendation for listings, but suggest the others may be
+ worth considering; add tgrind, sitting with lgrind
+ (section{Graphics}): rewrite item about mfpic, and add one about pgf,
+ in q-drawing
+
+2005-02-25 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new
+ q-errmissitem
+
+2005-02-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-tutorial.tex: add a subsection heading (who cares there are 10?)
+
+ * faqbody.tex (subsection{Footnotes}): mention threeparttable in
+ q-ftncapt (suggestion by don arseneau)
+
+2005-02-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): reword etex
+ description in q-nts
+
+ * add-general.tex (subsection{LaTeX macro programming}): new q-cmdstar
+
+ * sanitize-beta.pl (sanitize_line): add \elatex and \miktex translation
+
+ * faq.sty: add \elatex and \miktex commands
+
+ * faqbody.tex (section{The joy of TeX errors}): elatex as a progname->
+ \elatex{} in q-endingroup
+
+2005-02-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): MiKTeX!!!
+
+2005-02-15 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): xdvi and xdvik are
+ no longer separate
+
+ * dirctan.tex: delete xet,xdvik,hp2xx311; correct addindex
+
+ * filectan.tex: correct pdftex, latexcount
+
+ * faqbody.tex: v3.13b.1, today
+
+ * filectan.tex: add vf-howto
+
+ * faqbody.tex (section{Bits and pieces of TeX}): mention virtual fonts
+ howto in q-virtualfonts
+
+2005-02-09 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faq.sty: minor twiddling with default font loading;
+
+ * faqbody.tex: v3.13b, today
+
+ * texfaq2file: generate labels that go to the modified file names
+ rather than to the raw label name, in .aux scan
+
+2005-02-04 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): correct enumii->enumi in one
+ of the "recipes" in q-labelformat
+
+2005-02-03 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): \qref* for etex
+ and aleph in q-omega mention of aleph
+ (subsection{Typesetting specialities}): remove rogue line break in
+ q-upquote
+
+ * faqfont.cfg.ugm: new: for typesetting with urw garamond
+
+ * faq.sty: require lmodern regardless (for sans fonts)
+
+2005-01-21 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): correct details for
+ ctan-ann, and mention mail-archive.com in q-maillists
+ (section{TeX Systems}): mention tetex mailing list (not -announce or
+ -pretest...), plus RSS feed, in q-texsystems
+
+2005-01-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Support Packages for TeX}): make clear that
+ 4spell comes from a package that's now defunct
+
+2005-01-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add pseudocode
+
+ * faqbody.tex (subsection{Typesetting specialities}): mention
+ pseudocode package in q-algorithms
+
+2005-01-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: single file ispell (is this supportable?)
+
+ * dirctan.tex: remove ispell
+
+2005-01-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add aspell
+
+ * faqbody.tex (section{Support Packages for TeX}): tidy up reference to
+ aspell in q-spell, given that it's now on ctan
+
+2005-01-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add svn, svninfo
+
+ * faqbody.tex (subsection{Document management}): add svn and svninfo to
+ q-rcs
+
+2005-01-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.13a.1, today
+ (section{TeX Systems}): update sciword bumf from mail from mabb
+ (section{Documentation and Help}): typo in q-mfptutorials
+ (subsection{Particular font families}): typos in both q-uselmfonts and
+ q-concrete
+ (section{TeX Systems}): add a link to the y&y mailing list page at the
+ end of q-commercial
+
+2005-01-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.13a
+ (subsection{Document management}): correction+more details of extract
+ package in q-conditional
+
+2005-01-04 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.13, today (release)
+
+2005-01-02 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Symbols, etc.}): add bbm and doublestroke, and
+ do various editorial changes (including pouring more derision on the
+ "lazy person's" macros)
+
+ * dirctan.tex: add bbm-macros, doublestroke
+
+2005-01-01 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Particular font families}): mention that lm
+ fonts are already in tetex 3.0, and may (at least) be added to miktex
+ automatically, also bring updmap stuff up to date for miktex
+ (section{Installing (La)TeX files}): same change in q-instt1font
+ (section{Installing (La)TeX files}): editorials in q-miktexinst
+ (section{Installing (La)TeX files}): mention non-standard things like
+ .cfg and .drv files in q-wherefiles
+
+ * sanitize.pl (sanitize_line): bring up-to-date with -beta
+
+ * sanitize-beta.pl (sanitize_line): add \href* pattern
+
+ * faq.sty: add * and quote detection to \href (non-hyper version; *
+ simply ignored \ifpdf)
+
+ * faqbody.tex (section{Documentation and Help}): make reference to the
+ rutgers typography guidelines in q-tutorials
+
+2004-12-30 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add extract
+
+ * faqbody.tex: v3.13rc2, today
+ (subsection{Document management}): mention extract.sty in q-conditional
+
+2004-12-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-hammond.tex (subsection{William Hammond's contributions}): more
+ work on q-sgml2tex* ... i'm bogging down here :-(
+
+ * faqbody.tex (subsection{LaTeX macros}): correct spelling of optparams
+ in q-twooptarg
+
+2004-12-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): replacement for
+ q-mathml from add-hammond (where it was q-mathml*)
+ (section{Current TeX-related projects}): move all the \URL entries to
+ body of q-textrace, and add link to fontforge
+ (subsection{Adobe Type 1 fonts}): remove mathtime, mathtime plus and
+ lucida; add mathtime pro
+ (section{TeX Systems}): correct details of personal tex inc from web
+
+2004-12-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-hammond.tex (subsection{William Hammond's contributions}):
+ mention inkscape in q-mathml*, as a free svg editor
+ (subsection{William Hammond's contributions}): general other editorials
+ throughout q-mathml*
+
+2004-12-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add wallpaper
+
+ * faqbody.tex (subsection{Page layout}): add wallpaper package to
+ q-watermark
+
+2004-12-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.13rc1, today
+
+ * dirctan.tex: add metatype1
+
+ * faqbody.tex (section{Current TeX-related projects}): provide
+ sourceforge link to autotrace and potrace, and talk up mftrace in
+ q-textrace; also add description of metatype1 and change title of
+ question to emphasise that it covers a bunch of projects; remove
+ references to actual fonts in the ctanrefs list
+ (section{Hypertext and PDF}): make reference to metatype1 via
+ q-textrace, in q-type1t1
+
+2004-12-20 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-tutorial.tex: new file: replacements for q-tutorials
+
+2004-12-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+ * add-hammond.tex (subsection{William Hammond's contributions}): yet
+ more editorials on q-sgml2tex*
+
+2004-12-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-hammond.tex (subsection{William Hammond's contributions}): edit-
+ orial work in both q-readml* and q-sgml2tex*
+
+ * faqbody.tex (subsection{Document management}): add xcomment with
+ example of use to q-conditional
+
+2004-12-16 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * 3.12a/faqbody.tex: v3.12a-p4, today
+ (subsection{Document management}): correct \includeversion ->
+ \includecomment in q-conditional (and install)
+
+ * faqbody.tex: v3.12a.9, today
+ (subsection{Document management}): correct \includeversion ->
+ \includecomment in q-conditional, and add an example
+
+2004-12-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it do that?}): couple of typos in
+ q-marginparside, spotted by vladimir volovich
+
+2004-12-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): typo in q-papersize...
+
+ * check-ctan-lists: distinguish linked files,
+
+ * filectan.tex: correct path for protext
+
+ * dirctan.tex: correct basix (yoyoy?)
+
+2004-12-02 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-hammond.tex (subsection{William Hammond's contributions}): editor
+ work on q-readml*
+
+2004-11-30 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-hammond.tex (subsection{William Hammond's contributions}): re-
+ write text around sgmls and stil in q-sgml2tex*
+
+ * dirctan.tex: add euler-latex
+
+ * faqbody.tex (subsection{Particular font families}): add mention of
+ euler package and eulervm to q-concrete
+
+2004-11-29 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: add protext
+
+ * faqbody.tex (section{TeX Systems}): mention protext
+
+2004-11-26 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): mention william hammond
+ (section{DVI Drivers and Previewers}): slight mod suggested by author
+ of dvipng to q-dvi-bmp
+
+ * add-hammond.tex (subsection{William Hammond's contributions}): edit-
+ orial on q-mathml*, q-sgml2tex*
+
+2004-11-25 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * Makefile (newfaq-patch.dvi,.pdf): run find-add-files
+ (clean): remove additions.tex, too
+
+ * patchdates.tex: new; the patch levels that were mastered in
+ additions.tex; now pl4.12g, today
+
+ * find-add-files: perl jiffy to find what add-* files exist just now,
+ and to create a suitable additions.tex
+
+ * add-general.tex: remove hammond answers
+
+ * add-hammond.tex: new, hammond revised answers
+
+2004-11-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{William Hammond's contributions}): add
+ q-mathml*, q-sgml2tex* and q-readml*
+
+ * dirctan.tex: add gellmu and jadetex
+
+2004-11-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.12a.8, today
+ (subsection{Typesetting specialities}): add c2latex to q-codelist
+
+2004-11-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faq.sty: provide a definition for \textoslash
+
+ * sanitize-beta.pl (sanitize_line): \textoslash for \o (but why does
+ perl substitution of \o not work?)
+
+ * faqbody.tex (section{Introduction}): \textoslash for \o
+
+2004-11-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \o{}
+
+ * faqbody.tex (section{Current TeX-related projects}): ant now has
+ insertions, so suggest it's worth investigating as a system.
+ (section{Introduction}): add morten h
+
+2004-11-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): new q-ouparmd from
+ add-general
+
+ * add-general.tex (subsection{The Joy of TeX errors}): editorials on
+ q-ouparmd
+
+ * faqbody.tex (subsection{Page layout}): q-changemargin replaced by the
+ body of q-changemargin* from add-general
+
+ * add-general.tex (subsection{Page layout}): q-changemargin* editorials
+
+ * dirctan.tex: add algorithmicx
+
+ * faqbody.tex (subsection{Typesetting specialities}): add algorithmicx
+ to q-algorithms
+
+2004-11-12 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): mention parcolumns in
+ q-parallel, add examples
+
+2004-11-11 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Making things stay where you want them}): use
+ of infinite value for widow and club penalties in q-widow
+
+2004-11-10 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add reference to jim's
+ one-person system web page, under tutorials (this question needs re-
+ working, methinks...)
+
+2004-11-09 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): new
+ q-subverttoks from add-general
+ (subsection{Creating citations}): q-i18nbib from add-general
+ (subsection{Tables, figures and diagrams}): q-rulethk from add-general
+
+ * dirctan.tex: add bib2xhtml
+
+ * faqbody.tex (section{Hypertext and PDF}): correction for words about
+ plainpages=false, from dan luecking
+ (subsection{Manipulating whole bibliographies}): add bib2xhtml to
+ q-htmlbib
+
+ * texfaq2file: missing </ul> before subsections in normal mode
+
+2004-11-08 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): ec-type1->tt2001
+ in q-textrace
+
+2004-10-27 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * filectan.tex: correct context-tmf to current location
+
+ * faqbody.tex (section{Graphics}): correct pdftricks link in
+ q-pdftexgraphics
+
+04-10-26 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Odds and ends}): mention bold csc fonts in
+ knuth-style t1-encoded fonts to q-bold-extras
+ (section{Hypertext and PDF}): add tt2001 to q-type1t1
+
+ * dirctan.tex: remove fonts/ps-type1/ec, add fonts/ps-type1/tt2001
+
+ * faqbody.tex: v3.12a.7, today
+
+2004-10-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): provide morten's witty
+ example of the problems with \iffalse in q-conditional
+
+2004-10-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Hyphenation}): rejig q-newlang to mention the
+ use of texconfig to do the format rebuild in tetex
+
+2004-10-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): editorial on
+ q-extrabrace
+
+ * sanitize.pl (sanitize_line): as -beta
+
+ * sanitize-beta.pl (sanitize_line): add \cmdinvoke*{cmd}[opt]{mand} and
+ \cmdinvoke*{cmd}[opt]{mand1}{mand2}
+
+ * faqbody.tex (subsection{Mathematics}): add reference to
+ \shortintertext in q-mathstext, and show how to do short intertexts
+ using flalign
+
+ * dirctan.tex: add mh
+
+ * add-general.tex (subsection{Creating citations}): add norbib to
+ q-i18nbib
+
+2004-10-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add dk-bib
+
+ * add-general.tex (subsection{Creating citations}): add dk-bib to
+ q-i18nbib, and reorganise the list
+
+2004-10-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): excise european modern from
+ q-type1T1
+
+2004-10-06 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): purge references to y&y
+
+2004-10-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of TeX}): editorial,
+ particularly on q-virtualfonts
+
+2004-10-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): mention pstricks overlaying stuff in
+ q-labelfig
+
+ * add-general.tex (subsection{Why does it do that?}): new q-breaklinks
+
+2004-09-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type 1 ("PS") fonts}): mention CH math
+
+2004-09-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.12a.6, today
+ (section{Current TeX-related projects}): minimum change to reflect
+ what's happened since john's omega bombshell, plus ref to aleph
+ (section{TeX Systems}): mention the miktex cd with miktex descr
+ (section{Acquiring the Software}): make q-cd talk about nothing but the
+ tex live distribution
+ (section{Current TeX-related projects}): describe etex as today's
+ thing, in the article on nts.
+
+2004-09-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Symbols, etc.}): mention fourier in q-numbersets
+
+2004-09-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): q-atvert problem
+ happens in maths mode too
+ (section{Adjusting the typesetting}): add ctanref for fancyhdr in
+ q-reallyblank, supply missing text about memoir
+
+2004-09-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: pl4.12f, today
+
+ * add-general.tex (subsection{Page layout}): q-changemargin* (revision
+ from donald)
+
+2004-09-17 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.12a.5, today
+ (subsection{Adobe Type 1 ("PS") fonts}): merry upheaval of q-psfchoice
+ (subsection{LaTeX macros}): mention optparams in q-twooptarg
+
+2004-09-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): ha-prosper is
+ a package, not a class
+
+2004-09-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): mention eplain online docs and
+ mailing list
+
+2004-09-14 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add fourier and utopia
+ corrected swebib and elsevier entries
+ added bigfoot (for suffix.sty)
+
+ * faqbody.tex: v3.12a.4, today
+ (subsection{Typesetting specialities}): add concrete examples of using
+ listings package
+ (subsection{Adobe Type1 ("PS") fonts}): add blurb about fourier
+
+2004-09-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): standardise on \ProgName{Perl} (note cap)
+ and \ProgName{Python} (all of one change)
+
+ * dirctan.tex: add latexdiff, remove language, and resort in that area
+
+ * faqbody.tex (subsection{Document management}): mention latexdiff in
+ q-changebar
+
+2004-09-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating citations}): provide criterion for
+ choosing jurabib instead of footbib in q-bibinline
+
+2004-09-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Labels and references}): tidy up description
+ of byname in q-nameref
+
+2004-09-09 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): bring in parallel with sanitize.pl
+
+ * faqbody.tex (subsection{Odds and ends}): \bsbs (twice) in q-varwidth
+ (subsection{Common errors}): \bsbs -> \texttt{\bsbs } in q-noline
+ (section{The joy of TeX errors}): \bsbs in q-altabcr
+ (subsection{Tables, figures and diagrams}): \bsbs in q-tabcellalign
+
+ * sanitize.pl (sanitize_line): make \bsbs gobble a single following
+ space
+
+2004-09-07 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): putative completion
+ of q-i18nbib
+
+ * faqbody.tex (section{The Background}): mention the wiki in q-context
+
+2004-09-06 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): bit more on
+ q-i18nbib -- probably more language contributions to be found, but
+ there's enough here for the time being
+
+ * dirctan.tex: add spain and bib-fr
+
+ * faqbody.tex (subsection{Creating bibliographies}): rewrite the
+ description of the custom-bib mechanism in q-custbib
+
+2004-09-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): start on q-i18nbib
+
+ * filectan.tex: add finplain.bst
+
+ * dirctan.tex: add bibgerm, swebib
+
+2004-08-30 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): new (tug) list address for
+ q-mp, and add reference to tug mp page
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-ouparmd
+
+2004-08-29 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add ebib
+ multibbl, texpower now both in (regular) latex/contrib
+
+ * faqbody.tex (subsection{Creating bibliographies}): add ref to ebib in
+ q-buildbib
+
+2004-08-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): new
+ q-rulethk
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): editorial,
+ q-destable, and add reference to memoir implementing booktabs commands
+
+2004-08-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): add karl berry's suggestion to
+ q-mathsize
+ (subsection{Tables of contents and indexes}): editorial on q-tocbibind
+
+2004-08-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): correct
+ startling error in q-vertposfp (courtesy of donald -- i can't work out
+ how i came to write the original rubbish in the first place)
+ (section{TeX Systems}): correct address for truetex
+ (subsection{Adobe Type 1 ("PS") fonts}): mention truetex using type 1
+ fonts under xp
+
+2004-08-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * sanitize[-beta].pl (sanitize_line): provide \mailto{}
+
+2004-08-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type 1 ("PS") fonts}): editorial on
+ q-pspreview
+ (subsection{Adobe Type 1 ("PS") fonts}): editorial on q-psfchoice (more
+ remains to be done)
+ (subsection{Adobe Type 1 ("PS") fonts}): editorial on q-concrete
+ (subsection{Adobe Type 1 ("PS") fonts}): editorial on q-uselmodern
+
+2004-08-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Metafont fonts}): editorial on q-getbitmap
+ (subsection{Adobe Type 1 ("PS") fonts}): editorial on q-usepsfont
+
+2004-08-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.12a.3, today
+ (section{TeX Systems}): forward ref to q-buildbib from q-editors
+ (section{Installing (La)TeX files}): refer to "specific font families"
+ in q-instfont
+ (throughout): \FontName|...| -> \FontName{...}
+
+2004-08-20 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): add mention of
+ JabRef
+ (section{The Background}): editorial on q-latexe
+ (section{The Background}): editorial on q-context
+ (section{The Background}): editorial on q-amspkg
+ (section{Acquiring the Software}): editorial (big time) on q-uploads
+
+2004-08-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): carry forward changes from non-beta
+
+ * sanitize.pl (sanitize_line): correct \Newsgroup{}
+
+2004-08-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): make all the variants of \cmdinvoke use
+ the <code>\\</code><code> trick we already have for \csx, to deal with
+ \@ problem
+
+2004-08-02 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add ziffer
+
+ * faqbody.tex (subsection{Typesetting specialities}): mend typo in q-
+ dec_comma, and add reference to ziffer
+
+2004-08-01 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): first stab at updating
+ package doc question
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): new
+ answer on \[ex]def -- going to need a lot more thought
+
+ * faqbody.tex (section{Documentation and Help}): add link to edith
+ hodgen's magnum opus
+
+2004-07-31 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): superseded theorem.sty with
+ amsthm.sty in the quaintly named "roman theorems" answer
+
+2004-07-30 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.12a.2, today
+
+ * filectan.tex: add voss-mathmode (again?!)
+
+2004-07-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add texniccenter
+
+ * faqbody.tex (section{TeX Systems}): add texniccenter to q-editors
+
+2004-07-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add voss-mathmode
+
+ * faqbody.tex (throughout): change \Newsgroup|...| -> {...}
+ (section{Documentation and Help}): refer to ctan version of herbert
+ voss' mathmode thing
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): add closing </code> in
+ \marg (!), and allow \Newsgroup{...}
+
+2004-07-23 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.12a.1, today
+
+ * 3.12a/faqbody.tex: pl2, today
+ (section{The Background}): 3.141592
+ (various): remaining ctanrefs to enumitem
+
+ * faqbody.tex (subsection{Lists}): document \begin{enumerate}[resume]
+ from enumitem (and tidy up remaining ctanrefs to enumitem)
+
+2004-07-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * Makefile.CTAN: remove all mention of -cm targets
+
+2004-07-22 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * Makefile: remove -cm targets from "all"
+
+ * faq.sty: use T1 encoding, times & luximono fonts, by default
+
+2004-07-21 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * 3.12a/faqbody.tex: change version to -p1, today's date (for web
+ release with enumitem directory correct)
+
+2004-07-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): correct tex version no, and
+ add link to copy of knuth's paper in maps archive
+
+2004-07-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add andy roberts'
+ stuff
+
+2004-07-19 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: move fonts/ps-type1/lm up one
+
+ * faqbody.tex (subsection{Lists}): change location of enumitem
+
+ * dirctan.tex: add enumitem
+
+2004-07-15 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.12a
+ (subsection{"Generic" macros and techniques}): editorial in q-patch
+
+*** RELEASE 3.12 ***
+
+2004-07-15 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): sigh -- narrowversion stuff in
+ q-mathstext
+
+ * sanitize.pl (sanitize_line): transfer change to table defs
+
+ * faqbody.tex: v3.12, today
+
+ * faq.sty: suppress \pdfavoidoverfull if the cs doesn't exist
+ add pdfstring disable command for \marg
+
+2004-07-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): q-slidecls
+ from add-general
+ (subsection{LaTeX macros}): suppress the stupid coding for this release
+ since adding the new answer has obviated the need pro tem
+
+2004-07-14 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): stupid coding to prevent
+ spacing silliness around q-ltxabbrv; this will need reviewing at every
+ release unless i can think of some better way around the problem
+
+ * add-general.tex (subsection{Alternative document classes}): minor
+ tweak to slides question
+
+ * sanitize-beta.pl (sanitize_line): add cellpadding to <table>
+
+ * faqbody.tex (section{Documentation and Help}): change address of
+ teencontrex (sent reply to prompt check whether the latest stuff
+ really is on ctan...)
+ (subsection{Mathematics}): point maths sizes at q-ltxabbrv
+ (subsection{LaTeX macros}): q-ltxabbrv from add-general
+
+2004-07-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): add pybliographer
+ to the list of "managers not on ctan"
+ 3.12RC2, today
+
+2004-07-12 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add ppr-prv, ha-prosper
+
+ * add-general.tex (subsection{Alternative document classes}): write up
+ prosper, with ppr-prv and ha-prosper
+
+ * dirctan.tex: add pgf,xcolor
+
+ * add-general.tex (subsection{Alternative document classes}): write up
+ beamer, add links for pgf and xcolor
+
+2004-07-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): new q-buildbib
+ from add-general
+ (subsection{Creating citations}): new q-usebibtex from add-general
+ (subsection{Common errors}): new q-zerochap from add-general
+
+ * dirctan.tex: add ps4pdf
+
+ * faqbody.tex (section{Graphics}): mention ps4pdf and pdftricks, and
+ reference voss' page for various support options
+
+2004-07-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): add texmaker after kile in
+ q-editors
+ (subsection{Typesetting specialities}): elaborate situation of texindex
+ in q-makeindex, and add reference to ltxindex
+
+ * add-general.tex (subsection{Creating bibliographies}): write up the
+ bibtex db management systems
+
+ * dirctan.tex: add xbibfile and btOOL
+
+2004-07-05 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Common errors} and elsewhere): adjust spacing of
+ ellipsis in question title
+
+ * add-general.tex (subsection{Why does it do that?}): new q-zerochap
+
+ * faq.sty: debug \Qref*{}{}''
+
+2004-07-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqfont.cfg.mbvj: add definition of \acro
+
+2004-07-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: adjust "null" \acro command so as not to gobble following
+ space in the toc!
+
+ * add-general.tex (subsection{Alternative document classes}): work on
+ the slides question
+
+2004-07-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): correct
+ section number of companion reference
+ (section{Installing (La)TeX files}): moved up to before fonts
+ (subsection{Document structure}): add section number for companion
+ reference
+
+2004-07-02 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * additions.tex: pl4.12e, today
+
+ * faqbody.tex: today's date
+ (subsection{LaTeX macros}): two more editorials on q-ltxcmds
+
+2004-07-01 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * dirctan.tex: add chapterfolder
+
+ * faqbody.tex: today's date
+ (subsection{Common misunderstandings}): add another example of trouble
+ to q-baselinepar
+ (subsection{Document management}): add chapterfolder to q-docotherdir
+
+2004-06-30 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * texfaq2html, texfaq2html-beta, texfaq2file: align all three with
+ sanitize changes
+
+ * sanitize.pl: up to date with sanitize-beta
+
+ * faqbody.tex (throughout): \path|...| -> \path{...}
+
+ * sanitize-beta.pl (sanitize_line): add \path{...}
+
+ * faqfont.cfg.mbvj: boldmath not available
+
+ * faqfont.cfg.cmfonts: boldmath is available
+
+ * faq.sty: define \ifboldmathavail and set false in default font setup
+
+ * faqbody.tex: today's date
+ (subsection{Tables of contents and indexes}): editorial on q-secnumdep
+ (subsection{LaTeX macros}): debugging and editorial on q-ltxcmds
+ (throughout): tidy \boldmath for question (etc) titles
+
+2004-06-28 Robin Fairbairns <rf@mole.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): correct \href for
+ "highlight" home site
+
+2004-06-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new q-zerochap
+
+2004-06-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX-related projects}): q-extex and
+ q-xetex from add-general
+ (subsection{Hyphenation}): q-hyphexcept from add-general
+ (subsection{Common misunderstandings}): q-tocloftwrong from add-general
+ (subsection{Page layout}): q-outszwrng from add-general
+
+ * add-general.tex (subsection{LaTeX macro programming}): change \hline
+ in q-ltxabbrv (on the off-chance we can introduce this answer to the
+ running version)
+ (subsection{Current \TeX-related projects}): editorial on xetex
+
+ * sanitize-beta.pl (sanitize_line): fiddle trying to make \hline equiv
+ commands show up in tables
+
+ * faq.sty: define \acro conditionally in body of file; define it as
+ null (apart from \@) in default font setup, but not in cmfonts version
+
+ * faqbody.tex (section{TeX Systems}): links for gwtex and texshop,
+ reword availability statements for oztex and cmactex (looks like the
+ only "generally" pre-macosX version is textures, now :-( )
+
+2004-06-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.12RC1, today
+ (subsection{Typesetting specialities}): rewrite highlight stuff to be
+ more upbeat about it (and to mention its valuable properties)
+
+2004-06-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Macro programming}): new q-subverttoks
+
+2004-06-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): missing \csx in q-fixnam
+
+2004-06-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): editorial
+ on q-ifpdf
+
+2004-06-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): use the
+ \relax trick in q-empty
+
+ * sanitize-beta.pl (sanitize_line): move the zapping of \relax to after
+ that of {}, so that \cmdinvoke{cmd}{\relax} describes empty arg
+
+2004-06-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): first stab at
+ "abbreviations" answer (q-ltxabbrv)
+
+2004-06-15 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): ftpmail only at dante,
+ only one answer about searching, in q-archives
+ (section{Acquiring the Software}): mend ref in q-nonfree
+ (section{Acquiring the Software}): replace refs in q-uploads
+ (section{Installing (La)TeX files}): ... and in q-instpackages
+ (subsection{Alternative document classes}): and in q-journalpaper
+ (subsection{Common errors}): jf contribution to q-verbwithin
+
+2004-06-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): replace q-findpkg,
+ q-siteindex and q-websearch by q-findfiles from add-general
+ (subsection{Common errors}): rewrite my\string_name in q-verbdef
+
+2004-06-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: version 3.11h, tomorrow
+
+ * add-general.tex (subsection{Acquiring the software}): minor edits of
+ q-findfiles
+
+2004-06-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): q-ifpdf
+ from add-general
+ (section{The joy of TeX errors}): new q-divzero, q-missbegdoc,
+ q-normalszmiss and q-manymathalph from add-general
+ (subsection{Creating citations}): new q-compactbib and q-bibtocorder
+ from add-general
+
+2004-06-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): new
+ q-xetex
+
+ * faqbody.tex (throughout): \mailto|...| -> \mailto{...}
+
+ * filectan.tex: add notoccite, remove tocunscite
+
+ * add-general.tex (subsection{Macro programming}): typo in q-ifpdf
+
+ * faqbody.tex (several places): deal with companion issues or mark
+ further work needed with ********
+
+ * dirctan.tex: add tlc2
+
+ * faqbody.tex (section{Documentation and Help}): add reference to tlc2
+ examples
+
+2004-06-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: make \mailto accept either sort of arg, \ifpdf
+
+2004-06-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): tweak q-mathsize
+
+2004-06-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: add fontmath and fontdef (in some order)
+
+ * faqbody.tex (subsection{Mathematics}): clarification (one hopes) of
+ q-mathsize
+
+2004-06-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): warn about non-error in
+ q-verbwithin
+
+2004-06-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): emphasise
+ that \ifnoerror is a fantasy...
+
+ * add-general.tex (subsection{Macro programming}): new q-ifpdf
+
+2004-06-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): tidy q-cv
+
+2004-06-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): mention amsmath in the \\ q
+
+ * CHANGES-3.12: mention europecv
+
+ * dirctan.tex: add europecv
+
+ * faqbody.tex (subsection{Alternative document classes}): add europecv
+ to q-cv
+
+2004-06-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): comments
+ on "is it an integer" from donald
+
+2004-06-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Common misunderstandings}): new
+ q-tocloftwrong dealing with numbers in toc and so on, basically just a
+ pointer to q-tocloft
+
+ * faqbody.tex (section{Documentation and Help}): refer aspirant authors
+ to tex books and to q-dtx
+
+2004-05-31 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): expand q-extrabrace a
+ bit, adding stuff about \caption and non-moving opt args
+
+2004-05-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: remove french-le and french-pro (not actually used, and
+ french-le has disappeared, at least temporarily)
+
+ * filectan.tex: correct litprog-faq
+ comment-out compan-ctan
+
+ * faqbody.tex (section{Documentation and Help}): correct pointer to
+ voss's latex stuff (twice)
+
+2004-05-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): add keywords for
+ q-extrabrace (also touch up verbatim quoting)
+ (subsection{LaTeX macros}): mention definition of fragile commands in
+ lamport, and that some robust commands (e.g., \cite) get redefined
+ fragile
+ (section{TeX Systems}): mention texshop as an editor/shell for macos x
+
+2004-05-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): correction to
+ q-bibprefixsort from james szinger
+
+2004-05-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): first draft of "output
+ size wrong"
+
+2004-05-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): provide documentation, etc., links
+ for pstricks
+
+2004-05-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): correct maarten sneep's name
+ (subsection{Common errors}): correct the example in q-alreadydef
+
+ * dirctan.tex: e4t moved to nonfree/ (though we don't use it...)
+
+ * CHANGES-3.12: document 4alltex and miktex changes to faqbody
+
+ * faqbody.tex (section{TeX Systems}): slightly more expansive about
+ kile, and a link to sourceforge in q-editors; also remove mention of
+ eddi4tex (defunct?) and the 4alltex cdrom
+ (subsection{Adobe Type 1 (postscript) fonts}): texlive 7 is no longer
+ the type example of a system that does dvips 5.90 (or better)
+ (section{Acquiring the Software}): mention the miktex cdrom (a good
+ deal, imo)
+
+2004-05-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): add keywords to
+ q-newlineargs
+
+2004-05-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * texfaq2html (oh_dear): put an (obfuscated) mail address in the
+ message (does it need obfuscation?)
+
+2004-05-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): deal with the table things
+
+ * faq.sty: macros for use in tables
+
+ * faqbody.tex (subsection{LaTeX macros}): tabular for *name macros
+
+2004-05-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (throughout): get rid \cs usage
+
+ * faqbody.tex (section{The Background}): rewrite that nasty para in
+ q-texpronounce
+ (subsection{Creating bibliographies}): correct use of \csx for \&
+
+2004-05-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.11f, today
+ (section{The Background}): another paragraph (shock!) to elucidate
+ the relationship to "technology" (i have a nasty feeling...)
+
+2004-05-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: redefine \csx to allow its argument to expand, remove \cs
+
+ * faqbody.tex (section{Symbols, etc.}): use \symbol{95} for underscore
+ in several places
+ (subsection{"Generic" macros and techniques}): use \symbol{95}
+
+ * texfaq2html-beta: remove symbol character table
+
+ * sanitize-beta.pl: add symbol character table, with 95=>"_", remove
+ \cs
+
+ * add-general.tex (subsection{Creating bibliographies}): note bibdesk
+ (in comment)
+
+2004-05-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{\LaTeX{} macros}): reinstate minor changes
+ done here over the w/e
+
+2004-05-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): redo text at
+ start of q-codelist -- wasn't translating properly to html
+
+ * faq.sty: squeeze list indentations a fair bit
+
+ * faqbody.tex (throughout): enumerate->itemize wherever reasonable,
+ plus associated tidying of markup
+
+2004-05-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add the FILES.* requirements
+
+ * add-general.tex (subsection{Acquiring the software}): q-findfiles
+ more or less complete
+
+2004-05-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Acquiring the software}): first serious
+ chunk of a q-findfiles to replace the existing three answers
+
+2004-05-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): fidgeting with the
+ "find stuff" answers; these ought all to be one :-(
+
+ * filectan.tex: move T1instguide one directory down in the tree (nb,
+ keeping companion.ctan entry, even though the file's not on archive,
+ on the basis that i've to rewrite the file for ed.2)
+
+ * faqbody.tex (section{Acquiring the Software}): more hacking at
+ q-findpkg
+
+2004-05-02 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): removed the "more
+ dynamic is" rubbish from intro to lshort
+ (subsection{Mathematics}): tidying markup to avoid verbatim, use quote
+ env, in q-proof
+ (section{Acquiring the Software}): purge references to companion.ctan
+
+2004-04-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): allow narrow
+ version of \normalsize error message
+
+2004-04-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): new q-repeatgrf
+
+2004-04-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * CHANGES-3.12: mention mimetex reference
+
+ * faqbody.tex (section{Current TeX-related projects}): tidy up narrow
+ column stuff in q-mathml
+
+2004-04-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add MimeTeX
+
+ * faqbody.tex: v3.11e, today
+ (section{Current TeX-related projects}): mention techexplorer as
+ introduction to mimetex in q-mathml
+
+ * commands-to-define: add \addvspace (simplified defn)
+
+2004-04-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention
+ \tabularnewline in q-tabcellalign
+
+2004-04-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): whinge about age of emtex and
+ djgpp, suggesting users who want up-to-date systems need to go to
+ win32 :-(
+
+ * dirctan.tex: emtexTDS now obsolete
+
+2004-04-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): mend markup in
+ q-bibplain
+ (subsection{Spacing of characters and lines}): markup in q-flushboth
+ (subsection{Page layout}): shambles in q-landscape
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): move \qref and
+ \cmdinvoke down below def of all "font-change-only" commands (things
+ that could be in args)
+
+2004-04-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): redo tex2bib
+ references in q-makebib
+
+2004-04-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: add tex2bib entries (one for doc too)
+
+ * dirctan.tex: remove incorrect tex2bib entry
+
+ * add-general.tex (subsection{Creating bibliographies}): added tex2bib
+ to q-buildbib
+
+2004-04-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): tidy markup of
+ q-siteindex
+
+ * texfaq2file,texfaq2html-gamma,texfaq2html-beta,texfaq2html: add
+ symbol 94 for work on q-siteindex
+
+2004-04-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): q-manymathalph
+ complete (first pass)
+
+2004-04-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): a start to
+ q-manymathalph (interrupted by falling asleep...)
+
+ * faqbody.tex: v3.11d, today
+ (section{Documentation and Help}): add reference to kindersley book in
+ q-typebooks
+ (section{Introduction}): added isaac khabaza to list
+ (section{Documentation and Help}): fourth edition of k&d, 2nd of tlc
+ (section{Documentation and Help}): sort out ~ in an \href line (twice)
+
+2004-04-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): deal with line-
+ broken \Qref command in q-seturl
+ (subsection{Typesetting specialities}): it's M-Tx not M_Tx in q-music
+
+ * Makefile.CTAN: drop stupid_names.sty
+
+ * sanitize.pl (sanitize_line): line up with changes to -beta
+
+ * additions.tex: pl 4.12a, today
+
+ * faqbody.tex: v3.11c, today
+ (subsection{The Joy of TeX errors}): q-altabcr from add-general
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-missbegdoc
+ (subsection{The Joy of TeX errors}): new q-normalszmiss
+
+ * sanitize-beta.pl (sanitize_line): remove $...$ re, add \beta, \marg{}
+
+ * faqbody.tex (throughout): replace $...$ with \ensuremath{...}
+
+2004-04-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): comment on relation to
+ grouping level errors in q-semanticnest
+
+ * add-general.tex (subsection{Creating citations}): correct typo in
+ Q-compactbib
+
+ * faq.sty: arrange that \Qref doesn't eat following space (by
+ converting \@ifnextchar to \afterassignment with "\let\@tempa= "
+
+2004-04-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): jiffy on compact
+ thebibliography lists
+
+2004-04-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize[-beta].pl (throughout): align the two files (2-way process)
+
+ * faqbody.tex: v3.11b, today
+ (subsection{Floating tables, figures, etc.}): note bottom double float
+ restrictions and complications
+
+2004-03-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2file: add -2 switch, and corresponding tidies; correct a
+ few things detected by perl -w
+
+ * sanitize.pl (generate_CTAN_ref): correct = -> == in conditional(!)
+
+2004-03-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: define a bunch of stupid name macros to free us of these
+ idiot logos for ever; also define \MF and \MP without package mflogo
+
+2004-03-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of \TeX{} errors}): graphicx
+ height/division question q-divzero
+
+2004-03-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Hyphenation}): writing hyphenation
+ exceptions q-hyphexcept
+
+2004-03-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Support Packages for TeX}): typo in q-fig title
+ (section{The Background}): correct the earlier twaddle about X in
+ Q-TeXpronounce (courtesy of Ulrich Klauer)
+ (section{Introduction}): added Ulrich Klauer
+ (subsection{Tables, figures and diagrams}): editorial on q-tabcellalign
+ (section{Documentation and Help}): add reference to shipman's texcrib
+
+2004-03-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): typo, found
+ courtesy of bil kleb
+
+2004-03-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new q-altabcr
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): tidy up
+ q-tabcellalign, adding refs to q-altabcr, and correcting errors
+
+2004-03-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: remove unnecessary \pdfstringdisable commands, sanitise \nts
+ and \texxet (but comment out \texxet and also \mltex, which aren't
+ used)
+
+ * sanitize-beta.pl (sanitize_line): get rid of \texsis
+
+ * faqbody.tex (subsection{Typesetting specialities}): write out in full
+ the one instance of use of \texsis...
+
+ * faq.sty: de-sillify \tex, \etex, \extex, \latex, \alltex, \context,
+ \pdftex, \pdflatex, \twee ... and junk \texsis
+
+2004-03-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): complete
+ first stab at extex question
+
+ * sanitize-beta.pl (sanitize_line): add \Omega
+
+2004-03-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * README: modify final paragraph (about distributing modified versions)
+
+ * sanitize-beta.pl (sanitize_line): remove \Q
+
+ * faq.sty: suppress \Q (temporarily, just possibly: it's going from
+ texfaq2html, anyway)
+
+2004-03-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Why shouldn't I?}): correct fantasy in html
+ of q-2letterfontcommands
+
+ * filectan.tex: add vruler
+
+ * faqbody.tex: 3.11a, today
+ (section{The Background}): editorial on q-triptrap
+ (section{Introduction}): add brooks moses to list
+ (subsection{Typesetting specialities}): add vruler to q-linenos
+
+ * sanitize.pl (sanitize_line): sanitize_beta changes
+
+2004-03-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): removed \ldots, added \psatempty
+
+ * faqbody.tex (subsection{Page layout}): minor editorials for ps@empty
+
+2004-03-15: release 3.11
+
+2004-03-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faq.sty: disable \, in \pdfstringdisablecommands; define \psatempty
+
+ * faqbody.tex (subsection{Page layout}): use \psatempty in question
+ title for label ps@empty
+
+2004-03-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): don't refer to individual
+ latex doc files (not sensible since none is now html)
+ (section{Documentation and Help}): mention clsguide via directory only
+
+ * dirctan.tex: latex documentation directory
+
+2004-03-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add texcnvfaq as a directory
+
+ * filectan.tex: remove texcnvfaq
+
+2004-03-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.11, today
+ (subsection{Page layout}): clarify "pdf output" for pdflscape
+
+2004-03-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): new text about
+ dvipng, from its author
+
+2004-03-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: document \Qref in the course of checking it...
+
+ * faqbody.tex (throughout): check on "\Qref..." -- ensure sensible
+ usage, specifically avoiding "(see question x)"
+
+2004-03-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Lists}): tidy "interrupting lists" answer
+
+ * CHANGES-3.11: 2 more answers listed
+
+ * additions.tex: pl4.12, today
+
+ * faqbody.tex (subsection{Why shouldn't I?}): q-2letterfontcmd from
+ add-general
+ (section{Graphics}): q-dvipdfmgraphics from add-general
+ v3.11RC4, today
+
+ * add-general.tex (subsection{Why shouldn't I?}): editorials on
+ q-2letterfontcmd and q-dvipdfmgraphics
+
+2004-03-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): edit the dvipdfm answer a bit
+
+2004-03-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.11b, today
+
+ * add-general.tex (subsection{Graphics}): graphics in dvipdfm
+
+2004-02-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v 3.11RC3, today
+ (section{Introduction}): contributors contributions, added szinger
+
+2004-02-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \bsbs{}
+
+ * faq.sty: add \bsbs
+
+ * filectan.tex: beginlatex and tex4ht changed names
+
+ * dirctan.tex: add pict2e, remove/amend things to match changes on
+ the archive
+
+ * faqbody.tex
+ (subsection{Odds and ends}): add pbox and eqparbox to q-varwidth
+ (section{Graphics}): mention pict2e in "drawing in latex"
+
+ * dirctan.tex: add eqparbox and pbox
+
+2004-02-26 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: date today, of course!
+ (subsection{Adobe Type 1 ("Postscript") fonts}): rearrange list of
+ fonts to clump free ones together better [more still to be done]
+
+2004-02-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Odds and ends}): tidy up coding around stupid
+ logos answer
+ v3.11RC2
+
+ * filectan.tex: texnames.sty from info/biblio
+
+ * Makefile.CTAN: texnames.sty -> stupid_names.sty
+
+ * faq.sty: load stupid_names
+
+ * stupid_names.sty: renamed [my] texnames.sty
+
+2004-02-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add smallcap
+
+ * add-general.tex (subsection{Why shouldn't I?}): New q-2letterfontcmd
+
+ * faqbody.tex (section{Installing AllTeX files}): add note about public
+ fonts directories
+ (subsection{Odds and ends}): mention texhash for bold-extra installs
+
+2004-02-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): mention that memoir doesn't
+ choke on verbatim in footnotes in q-verbwithin
+ (subsection{LaTeX macros}): note koma-script \chapterformat (etc.)
+ functions in q-seccntformat
+ (subsection{Common errors}): q-tabacc and q-alreadydef from add-general
+ (subsection{Common misunderstandings}): q-linespread and q-baselinepar
+ from add-general
+ (section{Hypertext and PDF}): q-pdfpagelabels from add-general
+ (subsection{Odds and ends}): q-varwidth from add-general
+ (subsection{Creating bibliographies}): q-bibtranscinit from add-general
+ (subsection{Creating citations}): q-sortbib from add-general
+ [preamble]: v3.11RC1, today
+ (section{The joy of TeX errors}): q-inputlev and q-hyperdupdest from
+ add-general
+
+2004-02-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): new options for
+ q-changebars, from peter w; ditto comment env in memoir, for
+ q-conditional; totals counters in memoir for q-howmanypp
+ (subsection{"Generic" macros and techniques}): mention memoir's
+ \ifinteger setup in q-isitanum; ifmtarg in memoir for q-empty
+ (subsection{LaTeX macros}): chngcntr in memoir for q-running-nos;
+ q-oddpage stuff in memoir
+
+2004-02-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10k, today
+ (section{Bits and pieces of TeX}): tidy up text about bitmap type 3
+ fonts in q-adobetypen
+
+2004-02-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): correct
+ conditional code in Q-bibtranscinit
+ (subsection{Creating bibliographies}): bit more on Q-buildbib
+
+2004-02-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention koma
+ \captionabove command
+
+2004-02-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Labels and references}): twiddle further with
+ reference-by-name answer (i wonder if it's comprehensible?)
+
+2004-02-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add smartref
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): reword text
+ about splitidx package to take account of split option; more work
+ needed on this answer still :-{
+ (subsection{Labels and references}): note memoir titleref functions,
+ and mention byname
+
+2004-02-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty (\Qref): new whistle in case "\Qref..."
+
+ * faqbody.tex (subsection{Page layout}): editorial work on ps@empty
+
+2004-02-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10j, today
+
+ * additions.tex: pl4.10f, today
+
+2004-02-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-gamma: first tentative steps towards a new web script
+ (nothing much to do with tex, as yet...)
+
+ * texfaq2file: add switches to control what is output, for grand new
+ scheme of things
+
+2004-01-31 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): correct
+ reference to index package
+
+ * dirctan.tex: add index
+
+2004-01-29 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add ledmac
+
+2004-01-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: qq159,161 (in wilson's notes) for memoir
+ q163 for both memoir and koma-script
+
+ * add-general.tex (subsection{Why does it do that?}): close paren in
+ q-baselinepar
+ (subsection{Odds and ends}): new q-varwidth
+
+ * filectan.tex: add varwidth
+
+2004-01-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): finished (first
+ draft of) q-baselinepar
+
+ * faqbody.tex (subsection{"Generic" macros and techniques}): correct a
+ typo (or perhaps "braino") pointed out by hendrik maryns
+
+2004-01-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new q-baselinepar
+ and a link to it from
+
+ * faqbody.tex (subsection{Common misunderstandings}): bit more scrunge
+ at end of q-paraparam
+
+2004-01-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of TeX}): mention swiftex in dtx
+ answer
+
+2004-01-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10i, today
+ (subsection{Document structure}): refer to zoonekynd's title, chapter
+ and section style pages
+
+ * additions.tex: pl4.10e, yesterday
+
+2004-01-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): correct miktex
+ "update database" key name
+
+ * add-general.tex (subsection{Why does it do that?}): nearing
+ completion of q-linespread
+
+2004-01-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): don't have comment.sty \end{xyz} other than
+ in column 1
+
+ * filectan.tex: add savesym
+
+ * add-general.tex (subsection{Why does it do that?}): new Q-alreadydef
+
+2004-01-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): reword paraparam,
+ having recommended it to someone :-}
+
+2004-01-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add Tabbing
+
+ * add-general.tex (subsection{Why does it do that?}): complete q-tabacc
+
+2004-01-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new q-tabacc (not
+ yet quite complete)
+
+2004-01-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: subfigure->subfig, in case i ever get to use it...
+
+2004-01-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): remove references to ntex
+ (subsection{Common misunderstandings}): quote work complete to end
+ of this subsection
+
+2004-01-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): more work on the
+ quote and verbatim
+
+2004-01-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: pl 4.10d, today
+
+ * add-general.tex (subsection{Hypertext and PDF}): new answer
+ q-pdfpagelabels
+ (subsection{The Joy of TeX errors}): new q-hyperdupdest
+
+ * faqbody.tex (section{Hypertext and PDF}): tidy qrefs to get rid of
+ stray space in html; reword intro to make clear what the answer will
+ tell us
+
+2004-01-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): still more work on tidying
+ (subsection{Getting things to fit}): remove question on miktex failing
+ to generate latex format
+ (subsection{Common errors}): mention dblfloatfix in "dbl float order"
+ v3.10h, today
+
+2004-01-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout, again): more work on conditionals
+ (correcting gross errors of yesterday) and tidying layout (more quote
+ environments, f'rex)
+
+2004-01-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): redoing conditional control
+
+2004-01-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): start of scan
+ of database offerings
+
+2004-01-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): memoir does crop marks
+
+2004-01-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): couple of editorials
+ from christina thiele
+
+2004-01-06 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): q-nopageno and q-ps@empty,
+ update for memoir and koma-script
+
+2004-01-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing (La)TeX files}): new q-privinst from
+ add-general
+ (section{Installing (La)TeX files}): new q-instt1font from add-general
+ (section{Bits and pieces of TeX}): new q-resolns from add-general
+ (section{Bits and pieces of TeX}): new q-fontname from add-general
+ (subsection{Tables of contents and indexes}): new q-minitoc from
+ add-general
+
+2004-01-04 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): add a stricture against using epsfig
+ unless really necessary
+ (subsection{Document structure}): mention memoir in "page numbering"
+ (subsection{Page layout}): note typearea's capabilities in q-papersize
+
+ * add-general.tex (subsection{Creating bibliographies}): wrap bib
+ entries in dviversion for transcribed initials question
+
+ * faqbody.tex (subsection{Document structure}): dealt with the stuff
+ about marks
+
+2004-01-02 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): new answer
+ from martin sneep, about transcribed initial letters
+
+ * faqbody.tex (subsection{Document structure}): \clearempty... koma
+ stuff in Q-reallyblank
+ (section{Documentation and Help}): typesetting japanese tutorial from
+ matsusaka u. in japan
+ (section{Current TeX-related projects}): mention lambda in q-omega,
+ and add a health warning to the \ctanref about omega itself
+
+2004-01-01 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention
+ tabulary
+ (subsection{Document structure}): koma-script scrpage2, memoir into
+ q-fancyhdr
+ (subsection{Page layout}): mention koma \chapterpagestyle in Q-ps@empty
+
+2003-12-31 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add capt-of
+
+ * faqbody.tex (subsection{Document structure}): record change back from
+ caption2 to caption
+ (subsection{Document structure}): koma & memoir appendix facilities
+ (section{Document structure}): caption facilities of koma and memoir,
+ and add capt-of too
+
+2003-12-29 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): refer to mimi's pages
+ next to tim love's
+ (section{Documentation and Help}): remove reference to basum (bausum?)
+ page on tug.org since it's shortly to be no more, and remove the ltx-2
+ one too, since we seem to have a latex one in the offing
+
+2003-12-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): mention mptopdf in "mp in gs" q
+
+ * add-general.tex (subsection{Creating citations}): mention ken
+ turner's list of reference styles
+
+ * faqbody.tex (section{Documentation and Help}): list herbert voss'
+ thing under both faqs and tutorials
+
+ * add-general.tex (subsection{Installing (La)TeX files}): tidy up the
+ private installation thing to fit in the columns (still needs proper
+ proof-reading)
+
+2003-12-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): yet more
+ verbosity about home texmf trees (this stuff needs proof-reading!!!)
+
+ * faqbody.tex (subsection{Document structure}): koma, memoir additions
+ to q-secthead
+
+2003-12-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Tables of contents and indexes}): finish
+ off minitoc q with reference to hyperref; nb no reference to
+ minitoc-hyper (since no-one else has complained about it)
+
+2003-12-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): new question
+ q-privinst (incomplete so far)
+
+ * sanitize-beta.pl (sanitize_line): remove translation of \& to bare &
+ (which surely isn't safe?)
+
+2003-12-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): remove
+ statement that koma and memoir classes are "still under development"
+ with its unfortunate suggestion that they're still incomplete
+ (subsection{Document structure}): mention koma and memoir's titling
+ capabilities
+
+2003-12-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Bits and pieces of TeX}): fontname q
+ (subsection{Installing AllTeX files}): refer to q-fontname in
+ q-instt1font
+ (subsection{Creating citations}): restored q-sortbib ...
+
+ * faq.sty: redo definition of \ProgName (and hence various others)
+ to work with latest url.sty (if it's available)
+
+2003-12-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Particular font families}): optimise \Qref in
+ lmfonts question
+ (subsection{Alternative document classes}): updated other sizes
+ question to mention koma and memoir
+
+ * add-general.tex (subsection{Installing AllTeX files}): another batch
+ of work on "installing type 1 fonts"
+
+ * filectan.tex: excalibur now apparently 4.0.2
+
+2003-12-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): new Q-sortbib
+
+2003-12-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): current gs version (in "old
+ gs" q) changed to 8.12 (dec 2003)
+ (preamble): v3.10g, today
+ (section{Installing (La)TeX files}): changes for new fptex
+
+2003-12-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add dblfloatfix
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): mention
+ dblfloatfix in Q-2colfloat
+
+2003-12-02 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): correction
+ of multind example [how _could_ i have got it so wrong?]
+ (preamble): v3.10f, today
+
+2003-11-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: pdftitle uk _tex_ faq (not tug)
+
+ * faqbody.tex (section{TeX Systems}): typos in emacs names
+
+2003-11-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: pl 4.10a
+
+ * add-general.tex (subsection{Tables of contents and indexes}): minitoc
+ question answered
+
+2003-11-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10e, today
+ (throughout): refer to koma-script (the object, as opposed to the ctan
+ address) as KOMA-script
+
+2003-11-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{References from articles}): minor extra
+ editorial
+
+2003-11-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10d, today
+ (section{References from articles}): clarification of, and expansion of
+ examples in, q-mcite
+
+2003-11-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10c, today
+ (subsection{Creating bibliographies}): correct @preamble for \noopsort
+ (section{References from articles}): correct location for unsrtnat,
+ plainnat
+
+2003-11-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ <release to the web>
+
+ * dirctan.tex: FirstSteps, lgc, lwc -> info/examples
+
+ * faqbody.tex: v3.10b, today
+ (section{Documentation and Help}): corrections to mf/mp tutorials, plus
+ two additions (from jose santos)
+
+ * texfaq2html: vital item left out yesterday when doing changes from
+ -beta
+
+2003-11-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.10a
+ (subsection{Document structure}): typo in appendices question
+
+ * texfaq2html: changes from -beta
+
+ * sanitize.pl (sanitize_line): changes from -beta
+
+ * faqbody.tex: v3.10 today
+
+2003-10-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: remove kostas entry (corresponding directory seems to
+ have disappeared from CTAN without trace...)
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): extend and
+ tidy examples in "multiple indexes"
+
+ * sanitize-beta.pl (sanitize_line): add \Email{ }
+
+ * faqbody.tex (subsection{Typesetting specialities}): correct mail list
+ details for tex-music (now at icking archive)
+ (throughout): change \Email|...| to \Email{...}
+
+ * dirctan.tex: algorithm2e
+
+ * faqbody.tex: 3.10RC2, today
+ (subsection{Typesetting specialities}): mention algorithm2e in
+ Q-algorithms
+
+2003-10-24 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: pl4.9g, today
+
+ * faqbody.tex: v3.10RC1, today
+ (section{Documentation and Help}): various small editorials
+
+2003-10-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Document Structure}): editorial work on
+ the appendix answer
+
+2003-10-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Labels and references}): tidy q-extref
+
+ * dirctan.tex: removed web/glasgow and all subdir references
+
+ * add-general.tex (subsection{Labels and references}): faithfully add
+ reference to xr-hyper's url optional argument (though i've not tried
+ heiko's new version of hyperref that he says makes it work)
+
+ * dirctan.tex: add appendix
+
+ * add-general.tex (subsection{Document Structure}): new Q-appendix
+
+2003-10-21 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Why shouldn't I?}): add example of how to
+ code align in place of eqnarray; make all questions in section have ?
+ at their ends (just for once, they _are_ written as questions)
+ (subsection{Common errors}): mention Q-eqnarray in Q-newlineargs where
+ eqnarray is used as an example
+
+2003-10-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): q-toodeep from
+ add-general
+ (subsection{Mathematics}): q-mathstext and q-reuseq from add-general
+ (subsection{Common misunderstandings}): q-exscale from add-general
+ (subsection{Page layout}): q-epigraph from add-general
+ (section{Current TeX-related projects}): q-aleph from add-general
+ (subsection{Footnotes}): q-footnpp from add-general
+ (subsection{LaTeX macros}): q-addtoreset from add-general
+ (subsection{Tables, figures and diagrams}): removed superfluous
+ \endhtmlignore in q-wholerow
+
+ * add-general.tex (subsection{LaTeX macro programming}): mention per
+ page resetting problem and the perpage package, in answer "master and
+ slave counters" (done once before, and obviously lost :-( )
+
+2003-10-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: pl4.9f, today
+
+ * faqbody.tex (section{Support Packages for TeX}): mention aspell under
+ q-spell; remove mention of fig2mf under q-fig, and expand list of
+ known export formats (which now includes mf)
+
+ * add-general.tex (subsection{The Joy of TeX errors}): finished
+ editorial work on q-toodeep -- removed wibble about pressing on past
+ the error
+ (subsection{Creating citations}): minor editorial on the "howto"
+
+2003-10-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): mention per
+ page resetting problem and the perpage package, in newly-renamed
+ answer "master and slave counters"
+
+2003-10-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: remove $original_keyword (no longer used); make
+ $keyword have spaces exchanged for + signs; if not providing link to
+ list of questions, </center> ...
+
+2003-10-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Footnotes}): typo; add example of perpage
+ and list sources of documentation
+
+2003-10-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): more work on
+ how to
+ (subsection{Mathematics}): re-use of equation
+
+2003-10-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): start on "how
+ to write a .bib file"
+
+2003-10-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add versions.sty
+
+ * faqbody.tex (subsection{Document management}): add versions.sty to
+ conditional compilation answer
+
+2003-10-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): remove the historical
+ stricture about the bibtex man page, and tidy the rest of the answer
+ up a bit
+
+2003-10-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Footnotes}): new subsection, new
+ Q-footnpp
+
+2003-10-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): add crippled keyword to
+ questions about fuzzy fonts
+
+2003-10-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): too deep (list
+ nesting error answer
+
+ * sanitize-beta.pl (sanitize_line): add \"u
+
+ * faqbody.tex (section{Documentation and Help}): reference to l2tabuen
+ as a -ve tutorial
+
+ * filectan.tex: add l2tabuen and l2tabuen.src
+
+2003-10-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * filectan.tex: add fncyref
+
+2003-10-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.9d, today
+ (subsection{"Generic" macros and techniques}): renamed section, added
+ Q-empty, tidied up quoting further up section
+ (subsection{LaTeX macros}): added Q-labundef
+ (section{The joy of TeX errors}): added Q-8000
+ (subsection{Why shouldn't I?}): add Q-dolldoll
+ (subsection{LaTeX macros}): mention latex kernel problem with \p@<*>,
+ and list the patch; also mention fncylab and point out that list
+ reference patching is best done with enumitem
+
+2003-10-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Labels and references}): new question on
+ xr and xr-hyper
+
+ * faqbody.tex (subsection{Labels and references}): hyperref defines
+ \nameref for itself; nameref doesn't need hyperref
+
+ * dirctan.tex: add clrscode
+
+ * faqbody.tex (subsection{Typesetting specialities}): mention clrscode
+
+ * sanitize-beta.pl (sanitize_line): add narrowversion and wideversion
+
+ * faq.sty: add narrowversion and wideversion
+
+ * add-general.tex (subsection{Labels and references}): new subsection,
+ for (new) q-extref
+
+ * faqbody.tex (subsection{Labels and references}): new, so far just
+ contains q-nameref
+
+2003-10-03 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): add an
+ \@addtoreset answer
+
+ * sanitize-beta.pl (sanitize_line): correct order of
+ \cmdinvoke*{c}{a1}{a2}{a3} and \cmdinvoke*{c}{a1}{a2}; add
+ \cmdinvoke*{c}{a1}[a2]
+
+ * faqbody.tex (subsection{Typesetting specialities}): slight tidying of
+ algorithm answer
+
+2003-10-01 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add epigraph
+
+ * add-general.tex (subsection{Creating citations}): fiddling with cites
+ in how to bibtex question
+ (subsection{Page layout}): answer on epigraphs
+
+2003-09-30 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): how to run bibtex
+
+2003-09-28 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add bezos
+
+ * faqbody.tex (subsection{Lists}): add enumitem to the same two answers
+
+ * add-general.tex (subsection{Mathematics}): correction, following
+ discussion on c.t.t
+
+2003-09-27 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add paralist, savetrees
+
+ * faqbody.tex (subsection{Lists}): add commentary on paralist and
+ savetrees to compaction of lists, and re-organise rest of question;
+ turn "fancy enumeration" upside down (to mention the package first),
+ and add side reference to paralist
+
+2003-09-25 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * additions.tex: v4.9d. 22nd
+
+ * faqbody.tex: v3.9c, today
+ (section{Documentation and Help}): mention www.macrotex.net/texbooks
+
+2003-09-23 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating citations}): consistent set of
+ examples for all three candidate packages, and compare-and-contrast
+ stuff to help users choose
+
+2003-09-22 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating citations}): add ctan ref for
+ multibbl
+
+ * add-general.tex (subsection{Mathematics}): add \intertext command to
+ answer on text in maths (example copied from amsldoc)
+
+2003-09-20 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): add ref to latex2html
+ mailing list
+
+ * dirctan.tex: add texpower, beamer
+
+ * add-general.tex (subsection{Alternative document classes}): bits and
+ pieces added on to slides question
+
+2003-09-19 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * texfaq2file: complete filename mapping to avoid nasty chars
+
+ * add-general.tex (subsection{Mathematics}): new answer: text in maths
+
+2003-09-18 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why shouldn't I?}): sort out $$ answer
+
+ * faqbody.tex (subsection{Common misunderstandings}): micro-tutorial on
+ the way \marginpar works
+
+2003-09-17 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Common misunderstandings}): add exscale q
+
+2003-09-16 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): reference odp tex area
+
+ * add-general.tex (subsection{LaTeX macro programming}): add answer on
+ detecting whether a label's undefined
+
+2003-09-15 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add 4-arg \cmdinvoke*
+
+ * dirctan.tex: add zoon-mp-eg
+
+ * faqbody.tex (section{Documentation and Help}): add zoonekynd's
+ example set to list of mp tutorials
+
+2003-09-14 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): bunch of
+ changes \Package| | to \Package{ }
+ (subsection{Getting things to fit}): advise etex/etex.sty for pictex
+ (section{The joy of TeX errors}): mention etex for dealing with
+ register problems
+
+2003-09-13 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): mention
+ bigstrut
+
+ * dirctan.tex: add multirow
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): Add q on
+ multirow
+
+2003-09-12 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): question
+ on modifying single rows
+
+2003-09-11 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: add aleph
+
+ * add-general.tex (subsection{Current TeX-related projects}): little
+ answer on the aleph project
+
+2003-09-10 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * dirctan.tex: directory for TftI
+
+ * faqbody.tex (section{Documentation and Help}): add tex for the
+ impatient to the list of books released "free"
+
+2003-09-09 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): \label outside environment
+ enclosing \caption, too
+ (section{The joy of TeX errors}): play the htmlversion trick in
+ semanticnest
+
+2003-09-08 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Bits and pieces of TeX}): question on
+ resolutions
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): mention mptut.pdf
+ (subsection{Getting things to fit}):
+
+2003-09-07 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Documentation and Help}): recommend TUG India tutorial page
+
+2003-09-06 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): complete rewrite
+ of the "mismatched mode" answer
+
+ * dirctan.tex: add bakoma-texfonts
+
+ * faqbody.tex: v3.9a, today; move hypertext section beyond fonts
+ (section{Graphics}): reorder questions, make all titles of answers that
+ refer to imported graphics actually say "imported"
+ (section{Documentation and Help}): minor editorial on mf books
+ (section{Documentation and Help}): mention herbert voss' maths tutorial
+ (section{Documentation and Help}): tidy up references to texhax
+ (section{Documentation and Help}): remark on the nasa latex thing
+ referring to 2.09
+ (section{Bits and pieces of TeX}): minor editorial
+ (section{Acquiring the Software}): minor editorial
+ (section{Hypertext and PDF}): add ctan ref for bakoma fonts
+
+2003-09-05 Robin Fairbairns <rf@beret.cl.cam.ac.uk>
+
+ * texfaq2file: start on facility for changing file names of awkwardly-
+ labelled questions
+
+2003-08-29 Robin Fairbairns <rf@shep.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.9
+
+2003-08-28 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.9RC2, today
+
+ * additions.tex: pl4.8a, today
+
+ * add-general.tex (subsection{Creating citations}): use donald's
+ simpler scheme for doing unsrt styles by hand... still no tocunsrt :-(
+
+ * faqbody.tex (section{Graphics}): rename the "graphics in" to
+ "imported graphics in", and rename q-graph-pspdf to "portable imported
+ graphics
+ (subsection{Creating bibliographies}): trivial anglicisation
+ (subsection{Typesetting specialities}): mention sverb.sty in the
+ verbatim input question, and tidy the whole mess up
+ (subsection{Typesetting specialities}): tidy ctanrefs of music answer
+ (section{The joy of TeX errors}): reorder the question about "missing
+ number", and refer to mathptmx to replace the old times package
+
+2003-08-27 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background} and elsewhere): yet more typos
+ noticed by jose carlos santos
+
+2003-08-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): bring up-to-date with changes to -beta
+
+ * sanitize-beta.pl (sanitize_line): move {} pattern to end of funtion
+
+ * faqbody.tex: 3.9RC1, today
+ (subsection{Spacing of characters and lines}): documentation (such as
+ it is) of setspace
+
+ * companion.ctan: remove contrib/(supported|other) with a lot of help
+ from reinhard
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): put code
+ example in quote environment (seems to set it off rather well)
+
+2003-08-12 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex,filectan.tex: remove all remaining contrib/supported
+
+2003-08-11 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): ignore \bgroup, \egroup (the latter
+ has to have trailing space in its pattern, for some reason)
+
+ * faqbody.tex (section{References from articles}): tidy up ctanrefs
+ (subsection{Tables of contents and indexes}): add example of the use of
+ index.sty (other two to come)
+
+2003-08-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Odds and ends}): advise against nameref with
+ hyperref
+
+ * dirctan.tex: added cm-lgc
+
+2003-08-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Spacing of characters and lines}): rewrite
+ doublespacing question for less pomposity
+
+2003-08-09 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): use \Qref*
+ (subsection{Particular font families}): use \Qref*
+ (section{Hypertext and PDF}): rework the 8-bit fonts question to
+ include cm-lgc, with caveats about its size range, and also to compare
+ the three type 1 alternatives to cm shapes
+
+2003-08-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): further slight tweaks
+
+2003-08-08 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.8c, today
+ (subsection{LaTeX macros}): add argument-version to \collect@body q
+
+2003-08-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): typo in
+ Q-slashbox
+
+ * sanitize-beta.pl (sanitize_line): deal with \Qref* (twice) -- same as
+ \Qref here
+
+ * faq.sty: deal with \Qref*
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): couple of
+ typos in destable, and use \Qref*
+
+2003-08-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.8b, today
+ (section{Current TeX-related projects}): reference to pdftex in its own
+ right on ctan
+
+ * filectan.tex: add pdftex
+
+2003-08-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize.pl, sanitize-beta.pl (sanitize_line): add \File{ }
+
+ * faqbody.tex: v3.8a, today
+ (section{Hypertext and PDF}): typo in Q-fuzzy-type3
+
+2003-07-31 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile.CTAN: remove texfaq2{file,html}, but install faq-html.tar.gz
+
+ * Makefile (inst-html): muck about with html .tar.gz creation
+
+ * additions.tex: pl4.8, today
+
+ * faqbody.tex (subsection{Creating bibliographies}): merge Q-capbibtex
+ and Q-bibcase to convert the latter to just Q-bibaccent
+ v3.8, today ** release **
+
+2003-07-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): use new fantasies
+ around the production of \~
+
+ * sanitize-beta.pl (sanitize_line): deal with \~
+
+ * sanitize.pl (sanitize_line): deal with \~, bring up to date with
+ sanitize-beta
+
+ * faqbody.tex (subsection{Creating bibliographies}): \htmlignore around
+ dvi/pdf versions in examples of case protection
+
+2003-07-29 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add lshort-parent
+
+ * faqbody.tex (section{Documentation and Help}): make sure that every
+ tutorial mentions it's available from ctan if it is; suggest browsing
+ for other language versions
+
+2003-07-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add testflow to list
+ of tutorials
+
+ * additions.tex: pl4.7c, today
+
+ * faqbody.tex: v3.8RC2, today
+
+2003-07-27 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): \ProgName|...| -> \ProgName{...}
+
+2003-07-26 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add epslatex to list
+ of tutorials
+
+2003-07-25 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): remove claim about the
+ regularity of tugboat :-)
+
+2003-07-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): Q-upquot, Q-time
+ and Q-the-commands from add-general (slight edit to Q-the-commands)
+ (subsection{Particular font families}): lm question from add-general
+ (subsection{Creating bibliographies}): sorting from add-general
+ (subsection{Tables, figures and diagrams}): Q-slashbox from add-general
+ v3.8RC1, today
+
+2003-07-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): turned the 8-bit fonts
+ question upside down so as to emphasise cm-like fonts.
+ (section{Current TeX-related projects}): change section title, and
+ adjust emphasis in the textrace/mftrace answer (as well as moving
+ download addresses to the ctanrefs section)
+ (section{Current TeX-related projects}): new answer on ANT (to what
+ question? you may well ask :-), from add-general
+
+2003-07-22 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Particular font families}): new one on lm
+
+ * faqbody.tex (section{Hypertext and PDF}): add lm fonts to type1T1
+
+2003-07-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add lm fonts
+
+2003-07-18 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating citations}): \noopsort question
+
+ * faqbody.tex (subsection{Creating bibliographies}): mention the natbib
+ styles and custom-bib _above_ harvard :-}
+
+2003-07-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type 1 ("PS") fonts}): mention cm-super
+ and hfbright as sources of type 1 cm bright
+
+ * dirctan.tex: add latex4jed; move mcite, mdwtools, mfnfss, ssqquote,
+ textfit and tocvsec2 up/down/sideways one; also multibbl and foiltex
+ on the nonfree tree; add hfbright
+
+ * faqbody.tex: v3.7.1a, today
+ (section{TeX Systems}): mention latex4jed
+
+2003-07-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: move minitoc, ms, multibib, nrc, ntheorem, rcs, rcsinfo,
+ refcheck, rotating, sectsty, showlabels, snapshot, sttools,
+ supertabular, titling and tocloft down one (or up one -- who cares?);
+ delete schroeder entry (pointing to the ms directory)
+
+ * faqbody.tex (two places): ctanref schroeder -> ms
+
+2003-07-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: move mparhack, ncctools, newlfm, oberdiek, soul and
+ tocbibind up one
+
+2003-07-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Current TeX-related projects}): minor
+ tidies
+ (subsection{Current TeX-related projects}): add a sentence on _why_
+ separation of languages might be a good thing
+
+2003-07-09 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add \textsf as a no-op (like \acro)
+
+ * add-general.tex (subsection{Typesetting specialities}): still more
+ tidying, after sleeping on the problem
+ (subsection{Current TeX-related projects}): (new title for the section)
+ new question on ANT
+
+2003-07-08 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Typesetting specialities}): another pass
+ over the wording of the advice in the \the_xxx_ question
+
+2003-07-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add 2-arg *'d \cmdinvoke
+
+ * add-general.tex (subsection{Typesetting specialities}): remove \emph
+ from the arguments of \csx in Q-the-commands
+
+ * dirctan.tex: move jknappen, jurabib and mailing down one level
+
+2003-07-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: move toppages, type1cm and ucthesis down one level
+
+2003-07-07 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add datetime; move memoir, utthesis, vector and vmargin
+ down one level
+
+2003-07-06 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): add twoopt.sty to Q-twooptarg
+
+2003-07-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document structure}): tidy q-captsty (incl
+ documentation reference, and add reference to Q-atsigns in the early
+ bit about diy
+
+2003-07-04 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.7b, today
+
+ * add-general.tex (subsection{Typesetting specialities}): new question
+ on typesetting the time
+
+ * faqbody.tex (subsection{Creating bibliographies}): btxmac is actually
+ part of eplain; reference eplain, too
+
+2003-07-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add slashbox; move textpos, was, wordcount, wrapfig,
+ xtab and xymtex down from contrib/supported
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): answer
+ containing a recommendation of slashbox (but presenting thomas lotze's
+ suggestion from textex_355 as an alternative)
+
+ * filectan.tex: add tocunscite (it's not there yet, mind)
+
+ * add-general.tex (subsection{Creating citations}): answer for unsrt
+ with table of contents (etc)
+
+ * faqbody.tex (section{Current TeX Projects}): added mailing list
+ details for pdftex from tug site
+ (section{The Background}): maillist address for MP (didn't know it had
+ one!)
+ (subsection{Alternative document classes}): scrlettr->scrlttr2
+
+2003-07-01 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of TeX}): reference docmfp in
+ Q-dtx (is this the right place for it?)
+ (section{The Background}): rewrite text about mp in pdflatex, including
+ making reference to Q-pdflatexgraphics rather than to the pdflatex
+ project itself
+ (section{Current TeX Projects}): update pdftex answer; still needs
+ reference for new mailing list sign-up
+
+ * dirctan.tex: add docmfp
+
+ * faqbody.tex: v3.7.1, today
+ (subsection{Spacing of characters and lines}): mention the justify
+ stuff in latest ragged2e
+ (subsection{Document structure}): mention fncychap's restriction re.
+ front/backmatter in Q-secthead
+
+2003-06-25 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macro programming}): aide-memoir
+ for vertical spacing commands in plain-in-latex
+
+2003-06-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: release...
+
+ * sanitize.pl (sanitize_line): corrections from -beta
+
+ * sanitize-beta.pl (sanitize_line): move \csx so it can appear in \Qref
+ (sanitize_line): correct \^e
+
+ * faqbody.tex (section{Hypertext and PDF}): reorganise reference to
+ dvisstrip
+ (subsection{Typesetting specialities}): minor editorial
+
+ * sanitize-beta.pl (sanitize_line): add \ensuremath
+
+ * faqbody.tex: v3.7, today (i'm determined...)
+ (section{Format conversions}): refer to hennings' faq via href, not an
+ entry in ctanrefs
+ (section{Hypertext and PDF}): minor editorial in fuzzy-type3
+
+2003-06-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: correct subeqnarray, subfigure, subfiles
+
+2003-06-18 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: correct arabtex, ifmslide, natbib, titlesec
+
+2003-06-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Typesetting specialities}): new question
+ on upright (Xterm-like) quotes
+
+ * filectan.tex: add upquote
+
+2003-06-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.7RC3, today
+ (section{Format conversions}): tidy up "others" question a bit, and add
+ mention of tex2word and word2tex; no longer first in section
+
+2003-06-15 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.7a, today
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new answer on
+ 8000dpi gsftopk attempts
+
+ * faqbody.tex: 3.7RC2, today
+ (section{The joy of TeX errors}): non-PDF-special from add-general
+
+2003-06-14 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add ifmtarg
+
+ * add-general.tex (subsection{Macro programming}): empty arg answer
+
+2003-06-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.7RC1, today
+ (section{Hypertext and PDF}): replace q-dvips-pdf from add-general qs
+ (section{Installing (La)TeX files}): 4 font install answers ditto
+
+ * add-general.tex (subsection{Hypertext and PDF}): real error message
+ from dvips when font missing: not mentioning latest version, since
+ systems will have the fonts anyway
+
+2003-06-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): change reference to fuzzy
+ fonts question in "8-bit fonts"
+ (subsection{Typesetting specialities}): pseudocode, from add-general
+
+ * add-general.tex (subsection{Hypertext and PDF}): several editorial
+ and typographic changes
+
+2003-06-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.6.1d, today
+
+ * additions.tex: pl4.6b, today
+
+ * faqbody.tex (section{Graphics}): add graphics needed... from
+ add-general
+
+ * dirctan.tex: harvard, hyper, hyperref and hyphenat
+
+ * faqbody.tex (subsection{"Generic" macros}): minor edits of "spaces"
+
+ * add-general.tex (subsection{Installing (La)TeX files}): tidies of
+ some of these font answers
+ (subsection{Graphics}): minor edit
+ (subsection{Hypertext and PDF}): add proviso about acroread 6
+
+ * dirctan.tex: psfig change
+
+2003-06-09 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add urlbst
+
+ * faqbody.tex (subsection{Creating bibliographies}): mention urlbst in
+ Q-citeurl
+
+2003-06-08 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): reference to
+ Q-algorithms in Q-proglist; also be more positive still about listings
+ package (when did anyone last recommend lgrind?)
+
+ * add-general.tex (subsection{Hypertext and PDF}): minor edits
+ (subsection{Typesetting specialities}): minor adjustments
+
+2003-06-07 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.6.1c, today
+ (section{Hypertext and PDF}): mention pstill in q-pkfix
+ (section{The joy of TeX errors}): \$ needs {} (eh!?)
+
+2003-06-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): bitmap drivers
+
+ * add-general.tex (subsection{Hypertext and PDF}): split "quality of
+ pdf" into two, so all "problems" are on the same level; slight
+ editorials (some as a result of split)
+
+ * faqbody.tex: v3.6.1b, today
+ (subsection{Page layout}): page sizes from add-general;
+ (subsection{Tables, figures and diagrams}): table design from
+ add-general
+ (subsection{Common errors}): float ordering question from add-general
+
+ * add-general.tex (subsection{Typesetting specialities}): remove the
+ "short" option; tidy up description of algorithms bundle; mention
+ float.sty; write documentation notes
+ (subsection{Page layout}): minor editorial of page sizes
+
+ * dirctan.tex: bunch of directories contrib/supported->contrib
+
+2003-06-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.6a, today
+
+2003-06-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add algorithms,alg,newalg; junk old (cyrillic) "program"
+ in favour of pseudocode one for scott's answer(s); deal with labels,
+ lineno, listings, refman and wasysym (now links)
+
+ * add-general.tex (subsection{Typesetting specialities}): both
+ alternatives of scott pakin's take on algorithm typesetting
+
+ * faqbody.tex: today's date
+ (subsection{Typesetting specialities}): minor edit of q-codelist
+
+2003-06-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document structure}): mention doc of fncychap
+
+2003-06-01 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add topcapt
+
+ * add-general.tex (subsection{Tables, figures and diagrams}): new
+ design of tables answer
+
+ * dirctan.tex: add ctable
+
+ * faqbody.tex: v3.6.1a, today
+ (subsection{Footnotes}): reference ctable.sty in footintab
+
+2003-05-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): more editorial, mentions of
+ dvipdfm
+
+2003-05-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): further
+ iterations, including reference to new bluesky-maps in place of clunky
+ instructions on generating the beastly things
+
+ * dirctan.tex: add bluesky-maps
+
+ * add-general.tex (subsection{Hypertext and PDF}): move Q-fuzzy-t1 up
+ one so questions are in order of itemize
+
+2003-05-20 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Hypertext and PDF}): editorial work on
+ quality; put related answers into an itemize
+ (subsection{Installing (LaTeX files}): editorial work on bluesky
+
+2003-05-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: move mflogo and moreverb "down one"
+
+2003-05-18 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): mention mp doesn't need help from
+ psfrag
+
+2003-05-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): mention winedt
+ changebar macros
+
+2003-05-16 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): add "revision bars" to
+ Q-changebars
+
+2003-05-15 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page layout}): new question on paper size
+
+2003-05-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.6, today
+
+ * add-general.tex (subsection{Graphics}): trim ps+pdf graphics q title
+
+ * faqbody.tex: v3.6.1, today
+ (subsection{Typesetting specialities}): add highlight to Q-codelist
+
+ * dirctan.tex: add highlight
+
+2003-05-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: collapse koma-script address
+
+ * sanitize.pl,sanitize-beta.pl (sanitize_line): correct \^E->\^e, bring
+ sanitize.pl up to date
+
+ * faqbody.tex (section{Documentation and Help}): texhax now at tug.org
+ (subsection{Spacing of characters and lines}): mention \centering in
+ "cancelling ragged" question
+
+2003-05-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Common Errors}): slight diddle on
+ fixltx2e question
+
+2003-05-11 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add hvfloat
+
+2003-05-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add fnbreak; bunch of contrib/supported directories ->
+ contrib directories, and also picked up other link directories
+ (allowing some to remain links for clarity)
+
+ * faqbody.tex: 3.6RC5, today
+ (subsection{Common misunderstandings}): mention fnbreak in q-splitfoot
+
+2003-05-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.5f, today
+
+ * add-general.tex (subsection{DVI drivers and previewers}): editorials
+ (subsection{Common Errors}): new question on fix2col/fixltx2e
+
+2003-05-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.5e, today
+
+ * add-general.tex (subsection{The Joy of TeX errors}): answer on
+ "unknown special ignored"
+
+ * sanitize-beta.pl (sanitize_line): add
+
+2003-05-03 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{DVI drivers and previewers}): minor typos
+ and editorial corrections
+ (subsection{Graphics}): mention dvipdfm option, and auto driver
+ selection, in q about ambivalent output generation
+
+2003-05-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): correct
+ spelling of rsum
+
+2003-04-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile (clean): add *.png
+
+ * add-general.tex (subsection{DVI drivers and previewers}): bunch of
+ tidies in this and other questions answered recently
+
+ * additions.tex: pl4.5d, today
+
+2003-04-21 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: correct tex4ht-mn.zip, remove usergrps-list
+
+ * dirctan.tex: remove geralpha, which has gone from the archive
+
+ * check-ctan-lists: make to work on gordon
+
+ * dirctan.tex: add dvipng
+
+ * add-general.tex (subsection{Hypertext and PDF}): new Q-fuzzy-t1 on
+ the effect of type3 fonts when switching to T1
+ (subsection{DVI drivers and previewers}): new Q-dvi-bmp
+
+2003-04-20 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Hypertext and PDF}): replacement `quality
+ of PDF' answer (part 1)
+ (subsection{Hypertext and PDF}): Q-gs-pdfqual (part 2 of same)
+ (subsection{Hypertext and PDF}): Q-distill-prob (part 3 of same)
+
+2003-04-17 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): Add \FontName
+
+ * faq.sty: add \FontName
+
+ * add-general.tex (subsection{Installing (La)TeX files}): yet more on
+ Q-instprinterfont
+
+2003-04-16 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Particular font families}): move mathtime
+ back where it started!
+ (subsection{Installing (La)TeX files}): more on Q-instprinterfont
+
+2003-04-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2file: name question files by label, rather than by number; add
+ web link for question at end; change regexp for \Question to require
+ label, and to return it alone as $1 (did have [] too); remove
+ provision for generating a list of all questions
+
+ * faqbody.tex: v3.6RC4, today
+ (subsection{Why shouldn't I?}): Q-eqnarray from add-general
+ (section{Bits and pieces of \TeX}): Q-adobetypen from add-general
+ (subsection{LaTeX macros}): Q-spaftend, Q-cmdasenv from add-general
+
+2003-04-13 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.5c, today
+
+ * faqbody.tex (section{Documentation and Help}): more on how to ask a
+ question
+ (section{Graphics}): mention graphicx.tex as well as miniltx
+
+2003-04-12 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing AllTeX files}): installing
+ mathtime, back from faqbody (not ready for prime time: reinstate when
+ new version released so it appears in beta again
+ (subsection{Bits and pieces of TeX}): new q-adobetypen on font formats
+
+ * filectan.tex: contrib/other/fragments -> contrib/fragments
+
+ * dirctan.tex: remove "other" (whole contrib/other directory!); move
+ all contrib/other stuff down to contrib
+
+2003-04-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: introduce \ifusePSfont, set true if using times
+
+ * faqbody.tex (subsection{Adobe Type1 ("PS") fonts}): remove reference
+ to fonts/psfonts in Q-metrics
+
+2003-04-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): add mpsproof to question on mp
+ output in ghostscript
+
+ * filectan.tex: add mpsproof
+
+2003-04-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: latex/contrib/(other|supported)/misc -> contrib/misc
+
+2003-04-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): only options now, in
+ Q-CD, are texlive and the ctan cds.
+
+2003-04-07 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): dvistrip corrected to
+ dvipsstrip
+
+ * dirctan.tex: remove fonts/psfonts
+
+ * faqbody.tex (subsection{Adobe Type 1 (postscript) fonts}): remove
+ reference to psfonts directory
+
+ * add-general.tex (subsection{Macro programming}): slight elaboration
+ of command-as-env question
+ (subsection{Macro programming}): move Q-spaftend in here
+ (subsection{LaTeX macro programming}): moved up (with one so far
+ incoherent question) so as to redesignate previous two questions as
+ latex
+
+2003-04-06 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Macro programming}): finally a usable
+ question on commands-as-environments, Q-cmdasenv
+
+2003-04-04 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): slight tidy Q-dvips-pdf
+
+ * add-general.tex (subsection{Why shouldn't I?}): new Q-eqnarray
+
+2003-04-03 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.6RC3, today
+ (subsection{Typesetting specialities}): add discouragement of the use
+ of path.sty with latex
+
+2003-04-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why does it do that?}): new Q-spaftend
+
+2003-03-31 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: oops -- remove line break in decl of psnfssx-mathtime
+
+ * faqbody.tex: v3.6RC2, today
+ (subsection{Creating bibliographies}): add Q-bibcase from add-general
+ (subsection{Mathematics}): add Q-limits and Q-mathlips from add-general
+ (subsection{Particular font families}): add Q-mathtime from add-general
+
+ * add-general.tex (subsection{Mathematics}): add csnames as keywords
+ for Q-mathlips
+ (subsection{Mathematics}): \CTANref for graphics.sty
+
+ * additions.tex: pl4.5b, today
+
+ * add-general.tex (subsection{Creating bibliographies}): small changes,
+ plus text-wrapping in verbatim examples
+
+2003-03-30 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Creating bibliographies}): new Q-bibcase
+
+2003-03-29 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): revise reference to
+ \DeclareMathOperator with reference to Q-limits
+
+ * filectan.tex: add T1instguide
+
+ * add-general.tex (subsection{Installing (La)TeX files}): add reference
+ to lehman's guide
+ (subsection{Mathematics}): new question Q-limits
+
+2003-03-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add yhmath-(fonts|macros)
+
+ * add-general.tex (subsection{Mathematics}): new question on ellipses
+
+ * filectan.tex: add mathdots
+
+ * faqbody.tex: v3.6RC1, today
+ (section{The joy of TeX errors}): Q-formatstymy from add-general
+
+ * add-general.tex: tidy after removing questions
+
+ * faqbody.tex (section{Graphics}): typos in Q-graphicspath
+ (subsection{Document structure}): typos in Q-captsty
+ (subsection{Alternative document classes}): missing close paren in Q-cv
+ (section{The joy of TeX errors}): Q-bufovfl from add-general
+ (subsection{Mathematics}): Q-mathsize from add-general
+
+2003-03-27 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.5.1c, today
+
+ * filectan.tex: add ltablex
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): refer
+ disparagingly to ltablex.sty
+
+2003-03-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: removed beginlatex again, having changed policy
+
+ * faqbody.tex (section{Documentation and Help}): update tutorials to
+ reference "production" version of beginner's latex
+
+ * dirctan.tex: mps2eps
+
+ * faqbody.tex (section{Graphics}): reference mps2eps in "mp output in
+ gs" question
+
+2003-03-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: info/beginlatex
+
+2003-03-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.5a, today
+
+ * add-general.tex (subsection{Mathematics}): new, Q on
+ \DeclareMathSizes
+
+ * sanitize-beta.pl (sanitize_line): add a 5-argument form of \cmdinvoke
+
+2003-03-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): new, on format
+ error stymying
+
+2003-03-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.5.1b, today
+ (subsection{Lists}): change \parsep to \parskip in patched definition
+ of itemize in q on compacting lists
+ (section{Introduction}): added simon law to list of helpers
+
+2003-03-17 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Particular font families}): added a
+ miktex url for font map management
+
+2003-03-15 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.5.1a, today
+
+ * filectan.tex: add excludeonly
+
+ * faqbody.tex (subsection{Document management}): mention excludeonly in
+ Q-conditional
+
+2003-03-12 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): add a couple of keywords to
+ Q-dvips-pdf (at scott pakin's suggestion)
+
+2003-03-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): minor editorial
+ on Q-buffov
+
+ * faqbody.tex: v3.5.1, today
+
+2003-03-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): up-to-date with sanitize.pl
+
+ * sanitize.pl (sanitize_line): bunch of "g" qualifiers missing on and
+ after patterns for \cmdinvoke, and on \csx
+
+ * faqbody.tex (section{Documentation and Help}): typo in Q-pkgdoc
+ (section{Documentation and Help}): typo in Q-mfptutorials
+ (section{Current TeX Projects}): separate "real" ~ from url so as to
+ avoid hacking by sanitize
+ (section{Current TeX Projects}): couple of typos in Q-mathml
+ (section{Current TeX Projects}): \textpercent mayn't be followed by {},
+ so use \ for space
+ (section{The joy of TeX errors}): several small typos
+
+ * Makefile (clean): add *.tpt (thumbpdf-related, afaict)
+
+ * sanitize.pl: bring up to date with -beta
+
+ * Makefile.CTAN: remove references to .lab files
+
+ * additions.tex: pl4.5, today
+
+ * add-general.tex (subsection{The Joy of TeX errors}): minor
+ tidies of Q-buffov
+
+ * faqbody.tex: 3.5, today
+ (section{Hypertext and PDF}): tidy stuff in the distillation question
+
+2003-03-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2file: bring up-to-date, too
+
+ * texfaq2html: brought up-to-date with texfaq2html-beta
+
+ * texfaq2html-beta: removed presetting of value in search fields
+
+ * faqbody.tex (subsection{MF fonts}): editorials on bitmap fonts q
+
+ * dirctan.tex: correct path for gsview
+
+ * faqbody.tex: 3.5RC1, today
+ (section{Hypertext and PDF}): implement jose santos' remark about AR
+
+2003-03-08 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add latexcount
+
+ * faqbody.tex (section{Support Packages for TeX}): mention latexcount
+ (section{Current TeX Projects}): use revised name for mftrace (was
+ pktrace)
+
+2003-03-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (subsection{Why shouldn't I?}): \ss now now {} after it...
+
+ * sanitize-beta.pl (sanitize_line): stupid change to \ss
+
+ * texfaq2html-beta: patch in the google searching stuff
+
+2003-03-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.4b.4, today
+ (subsection{Why shouldn't I?}): new subsection of "why does it do that"
+
+2003-03-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add psnfssx-mathtime, and remove a couple of essentially
+ defunct mathtime directories
+
+ * add-general.tex (subsection{Particular font families}): start of
+ question on installing mathtime
+
+2003-03-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): mention \epsfig in Q-impgraph
+
+2003-03-01 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.4c, yesterday
+
+ * faqbody.tex: v3.4b.3, today
+ (section{TeX Systems}): yet more mucking about with the words about
+ tetex
+
+ * dirctan.tex: tetex2->tetex, using current/ rather than 2.0/; restore
+ tetex-beta
+
+ * faqbody.tex (section{Graphics}): mention withdrawal of tiff from
+ pdftex graphics
+
+2003-02-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): add decoding of \hphantom --
+ converted to (another) gobble operation
+ (sanitize_line): don't detect an argument in regexps for \hphantom and
+ \nothtml (efficiency only)
+
+ * filectan.tex: delete wrapfig
+
+ * dirctan.tex: add wrapfig's new directory
+
+ * faqbody.tex (subsection{Creating bibliographies}): Reconstructing bib
+ files from add-general
+ (section{Graphics}): graphics from somewhere else, from add-general
+
+ * add-general.tex (subsection{Why shouldn't I}): oops: subsection
+ rename didn't take
+
+ * faqbody.tex (section{Hypertext and PDF}): mention cm-super in type1T1
+
+2003-02-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: add $host_[fd] for use in generate_CTAN_ref
+
+ * sanitize-beta.pl (generate_CTAN_ref): tidy generation of http
+ references (which were ending up on $default_archive)
+
+2003-02-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Why shouldn't I?}): renamed from
+ "encoding" -- will go into "why does it _do_ that"
+ new question on why not use $$ for display maths in latex
+
+ * faqbody.tex (section{Graphics}): correct \href in mentions of
+ hutchinson's paper
+
+2003-02-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.4b, today
+
+ * sanitize-beta.pl (sanitize_line): add \ss{}
+
+ * add-general.tex (subsection{Encoding (?~--- new)}): questions on
+ t1enc and on eliding inputenc-fontenc when the codings nearly match
+
+ * faqbody.tex: v3.4b.2, today
+ (section{Graphics}): reference to hutchinson's graphics inclusion paper
+
+2003-02-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: correct simpl-latex
+
+ * dirctan.tex: add dvi2bitmap
+
+2003-02-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): corrected the address
+ for eric raymond on questions to get answers
+
+2003-02-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: add skip links to top of search, top of list of
+ questions, at very start, if the (now very long) intro is present
+
+2003-02-15 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): describe \jobname as a
+ primitive, not a "special macro"
+
+2003-02-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): prevent
+ \normalfont in the description env in Q-vertposfp \nothtml (also done
+ as running repair on source on web site)
+
+2003-02-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: remove extensive (but hugely incomplete) change log
+ at front of file; move def of $default_web, and define $href_script in
+ terms of it; two minor corrections to previous work
+
+2003-02-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.4b.1, today
+ (section{Hypertext and PDF}): put comment from jose carlos santos in as
+ reminder of work needing to be done; note that gs8.00 is current (and
+ the date of the statement ;-), and claim that gs6.50 is the minimum
+ sensible; add proviso to recommendation of -G1
+
+2003-02-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: set up protocols for new sanitize
+
+ * texfaq2file: some updating w.r.t. latest texfaq2html
+
+ * sanitize-beta.pl (generate_CTAN_ref): use of different protocols for
+ different things
+
+ * add-general.tex (subsection{The Joy of TeX errors}): minor typo
+
+2003-02-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: date today
+
+ * add-general.tex (subsection{Graphics}): and a bit more, to make the
+ thing make sense
+ (subsection{The Joy of TeX errors}): line too long for buffer error
+
+2003-02-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): slight edit of yesterday's
+ question, to avoid bad line break
+
+ * dirctan.tex: add tex2bib
+
+ * add-general.tex (subsection{Creating bibliographies}): new question
+ on regenerating bibliographies
+
+2003-02-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.4a, today
+
+ * add-general.tex (subsection{Graphics}): new question on \graphicspath
+
+2003-02-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: remove provisions for .lab files
+
+ * all: checkin/release
+
+ * faqbody.tex: changed date in first line
+
+2003-02-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): \ctanref to tetex (per se)
+ upgraded in windows section (talking about cygwin usage)
+
+2003-02-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: update tds
+
+ * faqbody.tex: v4.3b, today
+ (section{Bits and pieces of TeX}): more tidying
+
+2003-02-04 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): reword talk about tetex around
+ current state of tetex2
+
+ * dirctan.tex: remove both instances of tetex 1.0
+
+2003-02-03 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of TeX}): updated tds stuff,
+ after announcement of tds v1.0
+
+2003-01-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: replace \CTAN with \@ctan@path
+
+ * faqbody.tex: v3.4, today
+ (subsection{Typesetting specialities}): typo in Q-makeindex
+ (subsection{Typesetting specialities}): minor editorial in Q-verbfile
+ (subsection{Odds and ends}): there's no \CTAN macro! (error spotted by
+ Charles Cameron, in Q-bold-extras)
+ (section{Introduction}): credit CC, and now ... v3.4a
+
+2003-01-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): minor change to ensure match
+ between -beta and master version
+
+ * texfaq2html-beta: match with master version (as far as poss)
+
+ * faqbody.tex: 3.4RC4, today
+ (subsection{Page layout}): slightly less absolutist about samepage
+ environment in Q-nopagebrk
+
+2003-01-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.4RC3, today
+ (section{TeX Systems}): add reference to tetex release candidates
+ (subsection{Page layout}): rewrite Q-abspos, to mention eso-pic
+ solution (which i learnt on c.t.t today)
+ (subsection{Page layout}): corrected statement of relation between
+ eso-pic and everyshi in Q-watermark
+
+ * dirctan.tex: make testflow a browsable directory; add tetex2
+
+ * add-general.tex (subsection{Alternative document classes}): comment
+ on texpower expanded somewhat (must _really_ work on this some time)
+
+2003-01-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: ifmslide
+
+ * add-general.tex (subsection{Alternative document classes}): make
+ reference to ifmslide (whatever that is)
+
+2003-01-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: 3.4RC2, today
+ (section{Adjusting the typesetting}): use a formulation of don
+ arseneau's for \sectionmark, in Q-runheadtoobig
+
+2003-01-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add the catalogue
+
+ * faqbody.tex (section{Acquiring the Software}): minor tidy in
+ Q-nonfree
+ (section{Acquiring the Software}): make reference to the catalogue in
+ Q-websearch
+
+ * additions.tex: pl4.3i, today
+
+ * faqbody.tex: v3.4RC1, today
+
+ * sanitize.pl (generate_CTAN_ref): bring in updates from -beta
+
+ * texfaq2html: bring in updates from -beta
+
+ * faqbody.tex (section{The Background}): correct web address for
+ context
+ (section{Documentation and Help}): correct web address for metafun
+ (subsection{Footnotes}): Q-multfoot from add-general
+ (section{Acquiring the Software}): correct address for dante's upload
+
+2003-01-15 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3q, today
+ (section{Adjusting the typesetting}): slight adjustment of the text
+ referring to \sectionmark in runheadtoobig
+
+2003-01-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: split keyword lists and examine each separately,
+ case-independently (even)
+
+ * faqbody.tex (section{Documentation and Help}): \url->\URL in writecls
+
+2003-01-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3p, today
+
+ * additions.tex: pl4.3h, today
+
+2003-01-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add ncctools
+
+ * add-general.tex (subsection{Installing (La)TeX files}): editorial
+ work on the type1 cm fonts installation stuff.
+ (subsection{Footnotes}): question whose answer is manyfoot
+
+ * faqbody.tex (section{Installing (La)TeX files}): mention /usr/local/
+ share/texmf (suggestion from julian gilbey), and also suggest
+ kpsewhich as a source of the information for a tetex system
+
+2002-12-28 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing LaTeX files}): tidying
+ (perhaps even finishing!) the type 1 cmfonts installation question
+
+2002-12-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): more work on
+ cmfonts answer
+
+2002-12-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): Q-dpfloat,
+ Q-vertposfp from add-general
+
+ * faq.sty: try forcing \l@section/\l@subsection onto next page if not
+ enough space (retracted ...)
+
+2002-12-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing (La)TeX files}): more work on
+ "installing CM type1" question
+
+2002-12-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (generate_CTAN_ref): provide link terminator, in
+ case that the link doesn't have $ctanref_plus set true
+
+ * texfaq2html-beta: forget about label "lastquestion", correct coding
+ of next/previous links in case of last question
+
+2002-12-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize-beta.pl (sanitize_line): first hopeful stab at multiple
+ formats (new file, copy of sanitize.pl)
+
+ * texfaq2html-beta: first stab at provision for multiple format
+ directory retrieval
+
+2002-12-03 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3g, today
+
+ * add-general.tex (subsection{Floating tables, figures, etc.}): new
+ Q-vertposfp
+
+2002-11-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3o, today
+ (section{Documentation and Help}): move \CTANref of teencontrex to list
+ at end of question
+ (section{Documentation and Help}): refer to bibtex-doc-pdf in bibtex
+ docs question
+ (section{Format conversions}): move ref to html2latex to ctanrefs
+ (section{TeX Systems}): separate vtex-common in ctanrefs (twice)
+ (subsection{\MF fonts}): tidy up references in "running mf" q
+ (subsection{Document structure}): move ctan reference for abstract.sty
+ in Q-onecolabs
+ (section{Current TeX Projects}): move reference to ltx3pub
+ (subsection{Alternative document classes}): slight modification of ctan
+ references in Q-letterclass
+
+ * dirctan.tex: add bibtex-doc-pdf
+
+2002-11-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3f, today
+
+ * faqbody.tex: v3.3n, today
+ (subsection{Document structure}): Q-pagebychap from add-general
+ (section{Documentation and Help}): Q-pkgdoc from add-general
+
+ * add-general.tex (subsection{Floating tables, figures, etc.}): new
+ answer Q-dpfloat
+ (subsection{Page Layout}): minor editorial
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): refer to
+ spliti[n]d[e]x in Q-multind
+
+ * dirctan.tex: add splitindex
+
+2002-11-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Adobe Type1 ("PS") fonts}): more editorials
+
+2002-11-24 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3e, today
+
+ * add-general.tex (subsection{Documentation and help}): editorial
+ corrections to documentation question
+
+ * faqbody.tex
+ (throughout): editorial corrections noted on train...
+
+2002-11-23 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add chappg
+
+ * add-general.tex (subsection{Page Layout}): new question on page nos
+ by chapter
+
+2002-11-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Documentation and help}): new question on
+ package documentation
+
+ * faqbody.tex (section{Bits and pieces of TeX}): slight tidy of Q-dtx
+
+2002-11-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Alternative document classes}): point at
+ miwie.org comparison of things in Q-slidecls
+
+ * faqbody.tex (subsection{Mathematics}): add example of coding \qedhere
+ in Q-proof
+
+2002-11-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3l, today
+ (subsection{Mathematics}): typo left "i" at very end of answer
+ (subsection{Typesetting specialities}): note documentation of path and
+ url in Q-setURL
+ (subsection{Common errors}): note documentation of url and verbdef in
+ Q-verbwithin
+
+2002-11-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3k, today
+ (subsection{Typesetting specialities}): Q-overstrike from add-general
+ (subsection{Mathematics}): Q-cancel from add-general
+ (subsection{Hyphenation}): typo in Q-hyphoff
+
+2002-11-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add eso-pic; remove ref2bib (which has gone, and whose
+ replacement's name i've forgotten)
+
+ * faqbody.tex (subsection{Page layout}): separate references to eso-pic
+ and everyshi
+
+2002-11-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3j, today
+ (subsection{Page layout}): mention \filbreak in question about
+ suppressing page breaks
+ (subsection{Making things stay where you want them}): mention the
+ (common) need to load ulem with normalem option
+
+ * additions.tex: pl4.3d, today
+
+ * filectan.tex: add cancel
+
+ * add-general.tex (subsection{Mathematics}): cancel.sty
+ (subsection{Typesetting specialities}): overstriking
+
+2002-11-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3i, today
+ (subsection{Common misunderstandings}): make clear what is actually
+ being redefined with \usepackage[overload]{textcase}
+
+2002-11-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3c, today
+
+ * add-general.tex (subsection{Installing (La)TeX files}): more scribble
+ on installing font files
+
+ * faqbody.tex: v3.3h, today
+ (section{Installing (La)TeX files}): correct location of font source
+ files, and mention font families all in one directory
+
+2002-11-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Creating bibliographies}): a bit more on the
+ capitalisation question
+
+2002-11-09 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3g, today
+ (section{The Background}): tidy eplain answer and add reference to the
+ project home page
+
+2002-11-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): minor typo in
+ non-html stuff on wrapfigure
+ (subsection{"Generic" macros}): slight iteration of active chars q
+ v3.3f, today
+
+2002-11-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros}): hacking to get html right
+ in active chars question
+
+ * sanitize.pl (sanitize_line): remove requirement for {} after \textbar
+
+2002-11-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3b, today
+
+ * add-general.tex (subsection{Installing (La)TeX files}): another whole
+ paragraph for the question about installing fonts
+
+ * faqbody.tex: v3.3e, today
+ (subsection{LaTeX macros}): make reference to newcommand in the
+ question about multiple optional arguments
+
+ * dirctan.tex: add newcommand
+
+ * faqbody.tex (subsection{"Generic macros}): more work on don A's
+ stuff
+
+2002-10-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{"Generic" macros}): mods to make tilde appear
+ in html output...
+ (subsection{"Generic" macros}): first pass at getting don A's revised
+ answer for activechars in (much interrupted -- needs checking)
+
+2002-10-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Lists}): Q-interruptlist from add-general
+ v3.3d, today
+
+2002-10-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.3a, today
+
+ * add-general.tex (subsection{Lists}): new question on suspending and
+ resuming lists
+
+ * faqbody.tex: v3.3c, today
+ (section{Format conversions}): add mayer.dial.pipex.com samples url to
+ latex->html question (they *really* make tex4ht look good ;-)
+
+2002-10-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add rcsinfo
+
+ * faqbody.tex: v3.3b, today
+ (subsection{Document management}): refer to rcsinfo (ex norman gray)
+
+ * Makefile (throughout): tabs before thumbpdf and following $(PDFLATEX)
+ seem to have gone missing -- reinstated
+
+2002-10-12 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * Makefile: add heiko's modification to run thumbpdf
+
+ * faq.sty: new version from heiko; slight patch to do \@ReturnAfterFi
+ at outer level since i'm experiencing problems with it where he had
+ defined it
+
+ * faqbody.tex (subsection{Document structure}): add a proviso about
+ sections in the question on marks different from the toc entry
+ (section{Symbols, etc.}): mention euro-ce
+
+2002-10-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added euro-ce
+
+2002-10-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.3, today
+
+2002-10-06 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * newfaq-patch.tex: remove a redundant \Dings
+
+ * add-general.tex (subsection{LaTeX macro programming}): bit more of
+ non-equivalences between latex and plain commands
+
+ * faqbody.tex (subsection{Page layout}): parallel setting from
+ add-general
+
+ * add-general.tex (subsection{Page layout}): remove reference to nrc
+ classes in parallel setting question (they're not _that_ wonderful in
+ this context)
+
+2002-10-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Bits and pieces of TeX}): give skips
+ question a label (warned by new faq.sty ;-)
+
+ * Makefile.CTAN (all): add (letterfaq|newfaq).lab, remove
+ newfaq.workers
+
+ * Makefile (clean): remove pdf-newfaq-patch.tex, *.lab
+
+ * newfaq.tex,newfaq-patch.tex,letterfaq.tex: \labellist
+
+ * faq.sty: added \labellist stuff; make \Question complain if no label
+
+ * faqbody.tex (throughout): final touches to last night's additions
+
+2002-09-30 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): add nopagebrk from add-general
+ (subsection{Hyphenation}): add wdnohyph from add-general
+ (subsection{Floating tables, figures, etc.}): 2 >1 column floats
+ questions from add-general
+ (section{Graphics}): topgraph from add-general
+ (subsection{Document management}): inclplain from add-general
+ (section{Symbols, etc.}): tradesyms from add-general
+
+2002-09-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.2e, today
+ (subsection{Adobe Type 1 ("PS") fonts}): put version number on the
+ dvips that doesn't do charshift
+
+ * add-general.tex (subsection{Alternative document classes}): start
+ question on producing slides
+
+ * dirctan.tex: move foiltex to nonfree, to reflect reality, add
+ prosper, ppower4
+
+2002-09-29 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today's date, no change of version
+
+ * add-general.tex (subsection{Page layout}): question on parallel
+ setting of texts
+
+ * dirctan.tex: add parallel
+
+2002-09-27 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Symbols}): new question on trade symbols
+
+ * additions.tex: pl4.2i, today
+
+2002-09-26 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl4.2h, today
+
+ * add-general.tex (subsection{Floating tables, figures, etc.}): new
+ questions about single-column floats in multicols, and bottom-
+ placement of double-column floats in twocolumn
+
+2002-09-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): new answer on top-aligning
+
+ * additions.tex: pl2.4g, today
+
+ * faqbody.tex: v3.2d, today
+ (section{Documentation and Help}): small tidying of book list
+
+ * add-general.tex (subsection{Page Layout}): mention \enlargethispage
+ in "keeping things together on the page"
+ (subsection{LaTeX macro programming}): expand for tidiness sake
+
+2002-09-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.2f, today
+
+ * faqbody.tex: v3.2d, today
+ (subsection{Document structure}): two questions from add-general
+ (subsection{Document management}): how many pp, from add-general
+ (section{Graphics}): limit width, from add-general
+ (subsection{Floating tables, figures, etc.}): extra vertical space from
+ add-general
+
+ * add-general.tex (throughout): several minor editorials
+
+2002-09-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macros}): question plain commands
+ in latex code
+ (subsection{How do I \dots{}?~--- somewhere}): plain.sty question
+
+ * faqbody.tex (section{How do I do ...?}): another change of name
+
+2002-09-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Floating tables, figures, etc.}): new section
+ heading for explicit float things (currently only floats on their own
+ float pages)
+
+ * add-general.tex (subsection{Graphics}): limit graphics width to page
+ (subsection{Floating tables, figures, etc.}): witter about vertical
+ space in figures
+
+ * additions.tex: pl4.2e, today
+
+ * faqbody.tex (subsection{Page layout}): slight tidy of watermark q's
+ ctanrefs env
+
+ * dirctan.tex: add totpages
+
+ * add-general.tex (section{Where? --- sort of support?}): "number of
+ pages in the document?" answer
+
+2002-09-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): booktabs _is_
+ now compatible with at least some other table packages...
+
+ * add-general.tex (subsection{Document structure}): add "page n of m"
+
+ * filectan.tex: add mtw
+
+ * faqbody.tex (section{Documentation and Help}): mention mtw on ctan
+
+2002-09-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.2c, today
+ (section{Documentation and Help}): restore "making tex work" in the
+ books section, note that it's out of (print|date), and add link to
+ tutorials, which now lists sourceforge url
+
+2002-09-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Document structure}): new question about
+ fitting text into the running head.
+
+ * faqbody.tex: v3.2b, today
+ (section{TeX Systems}): mention some vim scripts
+ (subsection{Mathematics}): moved Q-braket in here
+ (subsection{Page layout}): moved "changing margins" in here
+
+
+2002-09-15 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add pdftricks
+
+ * faqbody.tex (section{Graphics}): reference pdftricks in the answer
+ about alternative drawing systems
+
+2002-09-13 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): tidy up "editors" entry for
+ ms-dos (for tidiness' sake, rather than because of the intrinsic
+ importance of the subject matter ;-)
+
+2002-09-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.2a, today
+ (section{TeX Systems}): text on vim from schrcker
+ (section{Introduction}): mention schrcker
+
+ * add-general.tex (subsection{Hyphenation}): rather feeble answer on
+ suppressing hyphenation of words
+
+ * dirctan.tex: concmath is in supported...
+
+ * additions.tex: pl4.2d, today
+
+ * filectan.tex: add needspace, add .gz to latex209.tar
+
+ * add-general.tex (subsection{Page Layout}): complete \needspace
+ question
+
+2002-09-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Page Layout}): start of a question on
+ keeping things on the same page
+
+ * faqbody.tex (section{Graphics}): typo in dvipsgraphics
+
+2002-09-10 Robin Fairbairns <rf@shep.cl.cam.ac.uk>
+
+ * faq.sty: tidy up after stupidity working on text annotations in
+ pdf version (which preserved as botched-faq.sty)
+
+2002-09-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{LaTeX macros}): typo in "finding macros"
+ v3.2, today
+
+2002-09-09 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Spacing of characters and lines}): remove
+ reference to tracking.sty, following notice of its bug
+
+2002-09-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.2c, today
+
+ * faqbody.tex: v3.1c, today
+ (subsection{Creating citations}): "References from the bibliography to
+ the citation" from add-general
+ (section{Graphics}): "Labelling graphics" from add-general
+ (subsection{LaTeX macros}): "The definitions of LaTeX commands" from
+ add-general
+ (section{The joy of TeX errors}): add "missing $" and "font shape not
+ available" from add-general
+
+ * add-general.tex (subsection{LaTeX macros}): editorial
+ (subsection{The Joy of TeX errors}): editorial
+ (subsection{Bibliographies (somewhere)}): editorial
+ (subsection{Graphics}): editorial
+
+ * faq.sty: add a \toclevel@question with a view to shutting hyperref up
+ a bit
+
+ * faqbody.tex (subsection{Page layout}): bit more description of
+ eso-pic (from a post by rolf niepraschk)
+
+2002-09-08 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document structure}): since i'm more informed
+ about titlesec, i might as well instruct the world as well... (losing
+ the reference to titletoc in passing -- dunno about that yet)
+
+ * dirctan.tex: add citeref
+
+ * add-general.tex (subsection{Bibliographies (somewhere)}): backwards
+ reference to citation answer
+
+ * additions.tex: pl4.2b, today
+
+ * add-general.tex (subsection{The Joy of TeX errors}): answer on font
+ substitution messages (at long last!!!)
+
+ * filectan.tex: add type1ec
+
+ * dirctan.tex: add type1cm
+
+ * faqbody.tex: v3.1b, today
+ (subsection{Particular font families}): incorporate small correction
+ from Jos Carlos Santos
+
+2002-09-07 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: add overpic
+
+ * add-general.tex (subsection{Graphics}): first stab at answer on
+ overlaying text on figures
+
+2002-09-06 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The Joy of TeX errors}): $ missing answer
+
+2002-09-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macros}): tidy and slightly expand
+ yesterday's work
+
+2002-09-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Graphics}): add a label Q-impgraph
+ v3.1a, today
+ (section{Documentation and Help}): added "a tex primer for scientists"
+ (section{Introduction}): add Hartmut Henkel to list of helpers
+ (section{Literate programming}): promote noweb (which supersedes
+ spidery web)
+ v3.1a.1 (patched prior to re-release)
+
+ * additions.tex: pl4.2a, today
+
+ * add-general.tex (section{LaTeX macros}): tweak finding macro question
+
+2002-09-05 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{LaTeX macros}): new answer: finding macro
+ definitions
+
+2002-09-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Alternative document classes}): "replacing
+ the standard classes" from add-general
+ (subsection{LaTeX macros}): "presentation of section numbers" from
+ add-general
+
+ * add-general.tex (subsection{LaTeX macros}): editorial on seccntformat
+ answer
+
+ * faqbody.tex: v3.1, today
+ (section{Documentation and Help}): replace mention of uk tug (after
+ list of books) with notes on contributing
+ (section{Acquiring the Software}): editorial stuff; remove reference to
+ decus tape distribution
+ (section{\acro{DVI} Drivers and Previewers}): remove reference to decus
+ distribution holding a copy of dvips
+ (section{Format conversions}): remove troff translator in decus dist
+
+2002-09-03 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{LaTeX macros}): add actual body to
+ \@seccntformat question
+
+ * filectan.tex: add sober
+
+ * add-general.tex (subsection{Alternative document classes}): editorial
+ on standard classes answer
+
+ * dirctan.tex: add pstoedit and purifyeps
+
+ * faqbody.tex (section{Graphics}): mention purifyeps in pdf question,
+ as route to something includable by pdflatex
+
+2002-09-03 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.0.1v, today
+ (section{Documentation and Help}): moved ctan references out to
+ ctanrefs env after book list
+
+ * additions.tex: pl4.1m, today
+
+ * add-general.tex (subsection{Alternative document classes}): long-
+ awaited answer on ntgclass, koma-script and memoir
+
+ * faqbody.tex (subsection{"Generic" macros}): defining characters,
+ active characters in command arguments, defining characters from
+ command arguments, and transcribing latex commands, from add-general
+ (subsection{Particular font families}): new section, to hold "using
+ concrete fonts", from add-general
+ (subsection{Document management}): add makefiles q from add-general
+
+ * add-general.tex (subsection{How do I do X in (La)TeX}): editorial on
+ makefiles question
+ (subsection{Macro programming}): "macros from command arguments" solely
+ in terms of plain programming
+ (subsection{Fonts (or something)}): couple more editorials on concrete
+
+ * faqbody.tex (section{Graphics}): moved "making \mp graphics display"
+ into this section
+ (subsection{Alternative document classes}): moved "other document font
+ sizes" into this section
+ (subsection{Typesetting specialities}): moved code listings up to top
+ of section
+
+2002-09-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * locations.mk: add FTPDIR
+
+ * Makefile (inst-html): goes to $(FTPDIR)
+
+ * add-general.tex (subsection{Macro programming}): rebalance
+ "characters commands as commands" and "active chars in command
+ arguments"
+
+ * dirctan.tex: add concmath-f (the fonts)
+
+ * add-general.tex (subsection{Fonts (or something)}): tidy up, and add
+ ctan references to the fonts mentioned
+
+ * faqbody.tex (section{Fonts}): new section, to include metafont stuff
+ and postscript font issues (was \MF and \MP, and \PS and \TeX)
+ (section{Graphics}): new section, from add-general, plus \MP in
+ ghostscript (from old \MF and \MP) and drawing stuff from tables,
+ figures and diagrams
+ v3.0.1u, today
+ (subsection{Making things stay where you want them}): mention
+ flafter.sty in Q-floats
+
+2002-08-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add latexmake
+
+ * Makefile.CTAN (all): add Makefile itself
+
+ * Makefile (ctan): remove commented-out ftp target
+
+ * add-general.tex (subsection{How do I do X in (La)TeX}): more work on
+ the Makefile question (really for doc management, now, i suppose)
+
+ * locations.mk: new file of "private" locations, that won't go on CTAN
+
+ * Makefile: move explicit locations out to locations.mk
+
+ * dirctan.tex: texhax is browsable
+
+ * faqbody.tex (section{You're still stuck?}): typos/minor corrections
+ to latex bug and additions to the faq questions
+ (section{The joy of \TeX{} errors}): typend and unkgrfextn from
+ add-general
+ v3.0.1t, today
+
+ * sanitize.pl (sanitize_line): add \pkgoption
+
+ * faq.sty: add \pkgoption
+
+ * add-general.tex (subsection{The Joy of TeX errors}): amalgamated
+ graphics extension bit with earlier one
+
+ * additions.tex: pl4.1k, today
+
+ * filectan.tex: add gkpmac
+
+ * dirctan.tex: add ccfonts and concmath
+
+ * add-general.tex (subsection{Fonts (or something)}): new subsection
+ for question from jos carlos santos about concrete
+
+2002-08-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Graphics}): provide some sort of
+ completion for pdftex graphics question, and do first version of dvips
+ graphics
+ (subsection{The Joy of TeX errors}): tidy up "... say \end"
+
+ * dirctan.tex: add jpeg2ps, bmeps
+
+ * filectan.tex: add resume
+
+ * dirctan.tex: add currvita
+
+ * faqbody.tex (subsection{Alternative document classes}): update
+ curriculum vita question with rec for currvita
+ (section{Introduction}): hans nordhaug to list of contributors
+
+ * additions.tex: pl4.1j, today
+
+ * add-general.tex (subsection{"Generic" macros}): first pass of
+ \newcommand answer complete (do we need \@ifundefined, \@ifnextchar?)
+
+2002-08-25 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): editorial from santos
+
+2002-08-24 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): mention pdflscape.sty in the
+ landscape question
+ v3.0.1r, today
+
+2002-08-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Footnotes}): make reference to \footref in
+ "texts are identical"
+
+ * add-general.tex (subsection{Installing AllTeX files}): editorials
+
+ * faqbody.tex (subsection{Document management}): mention \gobble and
+ \iffalse ... \fi in "comments" question
+
+ * sanitize.pl (sanitize_line): add cmdinvoke with mandatory argument
+ followed by optional one
+
+ * dirctan.tex: add subfiles
+
+ * faqbody.tex (subsection{Alternative document classes}): add reference
+ to subfiles system in "report from lots of articles"
+ v3.0.1q, today
+
+ * additions.tex: pl4.1i, today
+
+ * add-general.tex (subsection{The joy of TeX errors}): new answer (from
+ a post by heiko oberdiek), about "unknown graphics extension"
+
+2002-08-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables of contents and indexes}): editorials,
+ including rearranging "unnumbered sections in toc"
+ (subsection{Typesetting specialities}): editorials
+ (subsection{Tables, figures and diagrams}): editorials
+
+ * add-general.tex (subsection{"Generic" macros}): first paragraph of
+ question on understanding latex command declarations
+
+ * faqbody.tex (section{Bits and pieces of TeX}): minor editorials
+ (section{Bibliographies and citations}): minor editorials, split into
+ subsections
+ (section{PS and TeX}): excise any mention of mathpple
+
+ * filectan.tex: give TeX-FAQ a filename (ha ha)
+
+ * dirctan.tex: remove TeX-FAQ (the old faq)
+
+2002-08-20 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): talk down
+ dropping package in Q-dropping (ha ha)
+ (subsection*{Finding the Files}): slight editorial
+ (section{The Background}): various holiday editorials
+ (section{Documentation and Help}): added joy of tex to list of books(!)
+ v3.0.1p, today
+
+2002-08-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex:
+ 3.0.1o, today
+ (sections{The Background,Bits and pieces of TeX}): minor tidies and
+ updates
+
+2002-07-31 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.1h, today
+
+ * add-general.tex
+ (subsections{Generic and LaTeX macros}): frameworks for a couple of new
+ questions
+
+ * faqbody.tex
+ v3.0.1n, today
+ (section{Macro programming}): split into two halves, "generic" and
+ latex
+
+2002-07-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex
+ (section{Documentation and Help}): add wilkins' pllong.pdf to the
+ tutorials section
+ v3.0.1m, today
+
+2002-07-25 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Symbols, etc.}): add mention of encoding problems, and suggest
+ \char`\_, in underscore question
+
+2002-07-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): add stabular
+ to the long table stuff
+ v3.0.1l, today
+
+2002-07-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.0.1k, today
+ (section{Bits and pieces of TeX}): record that ec fonts don't cover all
+ sami languages
+ (section{Introduction}): add Regnor Jernsletten to helpers' list
+
+2002-07-21 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): change \htmlonly to \nothtml in
+ Y&Y entry (!)
+
+ * sanitize.pl (sanitize_line): move \htmlonly down with the other two
+
+ * faqbody.tex (section{Current TeX Projects}): micro-typo in doc prep
+ (section{Bits and pieces of TeX}): \nothtml problem in encodings
+ (section{PS and TeX}): add licence remark to txfonts and pxfonts
+ (section{PS and TeX}): mention dvips -G1 bugfix (which version is it?)
+ v3.0.1j, today
+
+2002-07-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): moved \nothtml and \latexhtml to the end
+ of the big block of conversions, so their arguments get processed
+ before they do (probably need to do same for other similar commands)
+
+ * faqbody.tex (section{The Background}): \begin{footnoteenv} on a line
+ by itself (and three other places in the document)
+ (subsection{Things have "gone away"}): typo correction for msx/y font
+ ctanrefs environment
+ v3.0.1i, today
+ (section{Installing AllTeX files}): add Q-miktexinst from add-general
+ (section{The Background}): also tidy Q-MP
+
+2002-07-16 Robin Fairbairns <rf@stripos2.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing AllTeX files}): more work on
+ the cm-pfb fonts question
+
+2002-07-14 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{Installing AllTeX files}): correct typos;
+ add disclaimer about miktex failing to know about a package
+
+2002-07-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.1g, today
+
+ * add-general.tex (subsection{Installing (La)TeX files}): new question
+ about installing from miktex
+
+ * faqbody.tex:: v3.0.1h, today
+ (section{Installing (La)TeX files}): make reference to new question on
+ miktex installation
+
+2002-07-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.1f, today
+
+ * add-general.tex (subsection{Installing AllTeX files}): bit of editing
+ of the cm-type1 question
+
+2002-07-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Format conversions}): added info (from Alejandro Lopez-
+ Valencia) about using acrobat 5 to produce output via word 2000 (!)
+
+2002-07-07 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add system and OS info
+ to the list of things people should report, when appropriate.
+
+ * add-general.tex (subsection{Installing AllTeX files}): start on
+ questions about installing fonts, and installing type 1 cm in
+ particular
+
+ * faqbody.tex (section{MF and MP}): make the reference to bluesky to
+ mention browsing
+ v3.0.1g, today
+
+ * dirctan.tex: Make bluesky browsable
+
+2002-06-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date (not changing minor version number)
+ (section{Support Packages for TeX}): correct support reference for
+ xfig, and mention jfig in that question
+
+2002-06-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): minor usage mods
+ in "rerun" question, suggested by john palmieri
+
+ * sanitize.pl (sanitize_line): remove \end{document}
+
+ * faqbody.tex: v3.0.1f, today
+
+2002-06-22 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): correct address for
+ Peter Flynn's intro, which has moved with site re-org
+ 3.0.1e, today
+
+2002-06-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Page layout}): mention full document in
+ landscape orientation in landscape question, and include geometry for
+ that
+ v3.0.1d, today
+
+2002-06-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX Projects}): url for x-symbol
+ v3.0.1c, today
+
+2002-06-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): CTAN-refer to oberdiek
+
+ * dirctan.tex: add epstopdf, rename pagesel as oberdiek
+
+ * add-general.tex (subsection{Graphics}): start on pdftex question
+
+ * faqbody.tex (subsection{Mathematics}): deal with overflowing column
+ in second example definition of "log-like" \diag
+
+2002-06-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile.CTAN: removed required-questions
+
+2002-06-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (three places): remove \Destination commands
+ v3.0.1a, today
+
+2002-06-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.0.1, today
+ (section{Current TeX Projects}): web2c* for sources; final editorial
+ work on document prep question
+ (section{DVI Drivers and Previewers}): weasel words around dvilj
+
+ * dirctan.tex: add web2c*; remove pdftex, dviljk; update
+ french-(le|pro)
+
+2002-06-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Typesetting specialities}): "typesetting a
+ file in verbatim" -> drop the "in"
+ (section{Current TeX Projects}): typo in the web question
+ (section{Current TeX Projects}): several gross typos in the wysiwyg
+ question, and new intro para
+ v3.0h, today
+
+2002-06-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.0g, today
+ (section{Current TeX Projects}): new question re-derived from david
+ kastrup's input on wysiwyg
+ (section{The Background}): david kastrup's stuff moved away from here
+
+ * sanitize.pl (sanitize_line): rearrange deckchairs slightly so
+ \cmdinvoke "long forms" are scanned before shorter equivalents
+
+ * faqbody.tex (subsection{Spacing of characters and lines}): minor
+ reword to change emphasis of doublespace document
+
+2002-06-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v3.0f, today
+ (section{Macro programming}): correct minor think-o in opt args
+ question yesterday
+ (section{The Background}): lots more editorial work on wysiwyg
+
+ * texfaq2html-beta: require sanitize-beta.pl
+
+ * Makefile (inst-perl-beta): install sanitize-beta
+
+2002-06-04 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): moved wysiwyg question over
+ (section{Macro programming}): the two command argument answers, too
+
+ * additions.tex: pl4.1e, today
+
+ * add-general.tex (subsection{Macro programming}): new answer on >1
+ optional argument
+ (subsection{The background}): editorial work on david kastrup's
+ splendid contribution
+ (subsection{Macro programming}): added ctanrefs for Q-moren9
+
+ * sanitize.pl (sanitize_line): add \cmdinvoke{name}[opt]
+
+2002-06-02 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Mathematics}): refer to amsthm proof env
+
+2002-06-01 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Installing AllTeX files}): add .mf to wherefiles
+
+2002-05-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{The background}): revision of wysiwyg
+ question, courtesy of david kastrup
+
+ * dirctan.tex: added texmacs and preview-latex
+
+2002-05-26 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2file: distinguish sections and subsections in index.html, and
+ change the trailer of each question to be a bit like that of the web
+ version
+
+ * texfaq2html,texfaq2html-beta: distinguish sections and subsections in
+ the listing of questions at the start
+
+2002-05-25 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex,dirctan.tex,faqbody.tex: uktug-faq -> faq throughout
+ (file names as well as email address)
+
+ * Makefile (inst-html): add README
+
+ * README: first stab at this; done for thomas esser's benefit
+
+ * Makefile.CTAN: replace 00readme with README, add sanitize.pl and
+ texfaq2file
+
+ * additions.tex: pl4.1c, today
+
+ * faqbody.tex (section{Documentation and Help}): typo in words about
+ tex-by-topic on web, so reworded slightly, too
+ v3.0d, today
+
+ * add-general.tex (subsection{Macro programming}): added question on >9
+ arguments
+ (subsection{Graphics}): finished first pass on general question; added
+ headers for dvips and pdflatex graphics
+
+2002-05-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl4.1b, today
+
+ * filectan.tex: add epsf.tex
+
+ * add-general.tex (subsection{Graphics}): start of a witter about
+ graphics inclusion in general
+
+ * dirctan.tex: add dtxtut
+
+ * faqbody.tex: v3.0c, today
+ (section{Bits and pieces of TeX}): add ref to dtxtut
+
+2002-05-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document management}): rename question to
+ "conditional compilation and comments"
+
+2002-05-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): mathpazo now v1.003
+
+ * Makefile (ctan): use newly-defined $CTAN_ROOT and $CTAN_HOME
+
+ * faqbody.tex (section{Symbols, etc.}): redo text about euro in light
+ of the discovery that the commission now accepts non-sans symbols
+ v3.0b, today
+
+2002-05-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Macro programming}): \p@enumii needs
+ \renewcommand
+
+ * add-general.tex (subsection{Macro programming}): tidy and extend
+ catcodes question
+
+ * faqbody.tex (section{PS and TeX}): removed \acro round micropress
+ font name "capitals" part, and corrected "ps math"->"pa math"(!)
+ (section{Bibliographies and citations}): reword answer on multiple
+ citations
+
+2002-05-15 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Document structure}): balancing columns (as
+ amended) from add-general
+ (subsection{Alternative document classes}): letter classes from add-
+ general
+ v3.0a, today
+
+2002-05-15 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (subsection{How do I do X in (La)TeX}): remove
+ reference to baltools in "balancing columns" question
+ (subsection{Alternative document classes}): twiddle the wording a bit
+ (subsection{Macro programming}): more scribbling in "defining macro
+ from argument"
+
+2002-05-14 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: added testflow
+
+2002-05-14 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add akletter, dinbrief, newlfm; remove aladdin
+
+ * additions.tex: pl4.1, today
+
+ * add-general.tex (subsection{Alternative document classes}): letter
+ classes
+
+2002-05-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): \WYSIWYG translate as WYSIWYG(!)
+
+ * additions.tex: pl4.0, today
+
+ * faqbody.tex: v3.0, today
+
+ * texfaq2html: added provision for subsections
+
+ * faqbody.tex (section{Format conversions}): add latex->plain from
+ add-general
+ (section{The Background}): latex<->plain from add-general
+ (subsection{Document structure}): "really blank pages" from add-general
+ (subsection{Typesetting specialities}): decimal comma from add-general
+ (subsection{Document management}): RCS question from add-general
+ (subsection{Typesetting specialities}): breaking boxes from add-general
+ (subsection{Tables, figures and diagrams}): floats on their own float
+ pages from add-general
+
+2002-05-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong...}): rearranged, and
+ stuff moved out; suppressed question about miktex format creation
+ (section{PostScript and TeX}): moved charshift in here for want of
+ anything better...
+ (subsection{Page layout}): landscape orientation (from "specialities")
+
+ * add-general.tex (subsection{Format Conversions}): for part of the
+ latex->tex question (also edited a bit)
+
+ * additions.tex: pl3.9m, today
+
+ * faqbody.tex (section{You're still stuck?}): split bug question in
+ two, taking stuff from add-general
+ (section{Documentation and Help}): "how to ask a question" from
+ add-general
+ (section{Bibliographies and citations}): "bib->html" from add-general
+ (section{The Background}): add explanation of the acronym in the
+ wysiwyg question
+ v2.5.8u, today
+
+2002-05-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9l, today
+
+ * add-general.tex (subsection{You're still stuck?}): add details of
+ using the bugs web page to question on latex bug reports
+ (subsection{How do I do X in (La)TeX}): tidy wrapping in norman gray's
+ question
+
+2002-05-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add rcs
+
+ * add-general.tex (subsection{How do I do X in (La)TeX}): rcs question,
+ courtesy of norman gray
+
+ * additions.tex: pl3.9k, today
+
+ * faqbody.tex (section{TeX Systems}): tidied text about cygwin
+
+2002-05-06 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8t, today
+ (section{TeX Systems}): add reference to tetex for cygwin
+
+2002-04-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): added peter flynn's
+ tutorial to tutorials question
+
+ * add-general.tex (subsection{Documentation and Help}): new question on
+ how to formulate questions (self-referential or what?)
+ (subsection{The Background}): minor tidy of translation question
+ (throughout): removed most \Destination commands
+
+ * additions.tex: pl3.9j, today
+
+ * faqbody.tex: v2.5.8s, today
+ (section{Documentation and Help}): reword text about google
+
+2002-04-29 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: various questions moved around and subsections created
+
+2002-04-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): suppress
+ suggestion that dvips is readily available
+
+2002-04-28 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: changed date to today
+
+ * dirctan.tex: added feyn
+
+ * faqbody.tex (subsection{Tables, figures and diagrams}): correct
+ ctanrefs references to picins; put picins at the end of the list in
+ the body of the answer
+ (subsection{Footnotes}): mention the "table notes" feature of
+ threeparttable
+ (subsection{Tables, figures and diagrams}): refer to feyn font package
+
+2002-04-27 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common misunderstandings}): correction and
+ improvement to Q-marginparside from Norman Gray
+ v2.5.8r, today
+
+2002-04-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: removed three directories that no longer exist
+ (including dviware/dvipsk)
+
+2002-04-16 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9i, today
+
+ * add-general.tex: 3 questions->faqbody
+
+ * faqbody.tex: v2.5.8q, today
+ (subsection{Tables of contents and indexes}): bibliography and index in
+ toc from add-general
+ (subsection{Tables, figures and diagrams}): strutting tables, and long
+ tables from add-general
+
+2002-04-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Something or other}): add mention of tracking
+ to the letterspacing question
+
+ * filectan.tex: added tracking.sty
+
+2002-03-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9h, today
+
+ * faqbody.tex: bunch more shifting around of questions
+ v2.5.8p, today
+ (section{Current TeX Projects}): textrace question, from add-general
+
+ * faq.cls: add \ProvidesClass declaration, use obeyspaces option when
+ loading url.sty
+
+2002-03-10 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): mention DVIWindo as capable of
+ direct rendering of type1 fonts
+ (section{Hypertext and PDF}): hack at "making hypertext documents" and
+ "making acrobat documents", and correct references to [tp]xfonts (the
+ package name is plural]
+ v2.5.8o, today
+
+2002-03-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (subsection{Common errors}): new, under why does it do
+ that?; plus a whole bunch of new subsections, with corresponding re-
+ arrangements of text of questions
+
+ * texfaq2html-beta: treat \subsection the same as \section, pro tem
+
+ * sanitize.pl (sanitize_line): ignore \subsection and its arguments
+
+2002-03-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex: move all the questions into subsections
+
+ * faq.sty: today's date: deemed to be v1.1 (surely as good as any?)
+ define \subsection as a sort of mini-section (also \l@subsection)
+
+2002-03-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): mention that
+ \extracolsep can be cancelled
+ v2.5.8m, today
+
+2002-03-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: convert \def\file* + \typeout => \ProvidesPackage (v2.2)
+
+ * add-general.tex (section{Proposed new questions}): minor rewording of
+ q on breaking boxes of text
+
+2002-02-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8l, today
+ (section{Documentation and Help}): refer to ams short math guide
+
+2002-02-21 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9g, today
+
+ * add-general.tex (section{Proposed new questions}): tidy up breakable
+ boxes question
+
+ * faqbody.tex (section{Hypertext and PDF}): lates gs is 7.04
+ v2.5.8k, today
+ (section{Special sorts of typesetting}): eplain defines \path; provide
+ recipe for using url.sty in plain
+
+2002-02-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): stupid error in Q-latex2e
+
+ * texfaq2html: the -beta version seems to work, so let's go live with
+ it...
+
+ * faqbody.tex (section{You're still stuck?}): tidy noans and newans, in
+ particular making use of \href for the mailto url
+ [preamble]: v2.5.8j, today
+
+ * texfaq2html-beta: first stab at labellisation
+
+2002-02-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8i, today
+ (section{The Background}): add link to Q-lit under description of tex
+ (section{Literate programming}): add reference to
+ literateprogramming.com in Q-lit
+
+2002-02-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: add framed and shade
+
+ * add-general.tex (section{Proposed new questions}): start of breakable
+ boxes question
+
+2002-02-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added was (walter schmidt's bits and pieces)
+
+ * add-general.tex (section{Proposed new questions}): question about
+ commas as decimal separators
+
+2002-02-01 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): correct a \URL|...|
+
+2002-01-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): first stab at
+ answer on under- and overfull boxes, made by strapping a few
+ other people's postings onto a bit of intro stuff of mine
+
+ * additions.tex: pl3.9f, today
+
+ * add-general.tex (section{Proposed new questions}): added pktrace to
+ textrace question
+
+2002-01-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): typo spotted by jose carlos santos
+ (section{Why does it do that?}): typo spotted by j.c.s (again)
+
+2002-01-17 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9e, today
+
+ * add-general.tex (section{Proposed new questions}): minor tweaking of
+ the bib->html question
+
+Tue Jan 15 08:02:18 2002 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): added web pointers to
+ some known latex documentation, rewrote mention of tex by topic
+ v2.5.8h, today
+
+Sun Jan 13 22:17:28 2002 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9d, today
+
+ * filectan.tex: add noTeX, bbl2html
+
+ * add-general.tex (section{Proposed new questions}): add question on
+ bib->html, starting with noTeX, bbl2html
+
+2002-01-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): change information
+ about texhax, and provide url for finding info about tex lists via
+ heidelberg
+ v2.5.8g, today
+
+2002-01-09 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Symbols, etc.}): mention the m$ euro code
+
+ * faq.sty: change \Question \@startsection parameters to allow less
+ space between questions, and to use \normalsize bold text
+
+2002-01-08 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9c, today
+
+ * add-general.tex (section{Proposed new questions}): answer on
+ translating latex to plain, directly copied from Jules Bean on c.t.t
+
+ * dirctan.tex: removed all the obsolete/dviware things, the format-
+ dumper fantasies, systems/knuth/dviware and dvitodvi
+
+ * filectan.tex: correct axodraw
+
+ * newfaq.tex,newfaq-patch.tex,letterfaq.tex: \typeout at end report
+ \thequestion, not \thesubsection
+
+ * faq.sty: redo \question as a \@startsection in its own right with its
+ own counter), and remove all the kerfuffle needed to make it work
+ mapping to \subsection; also remove \subquestion and the like
+
+2002-01-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8f, today
+ (section{Introduction}): tidy reference to alternative html, remove
+ dick nickalls from the list of non-members of the committee
+ (section{The Background}): rewrite texinfo entry to mention texi2html
+ (section{The Background}): various other entries: provide pointers to
+ distributions in ctanrefs envs at end of questions
+
+2002-01-03 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): remove requirement for \nobreakspace to
+ have trailing {} (dunno why this makes it work, mind you...)
+
+ * faqbody.tex (section{Bibliographies and citations}): change ~ in
+ \href anchor to \nobreakspace
+ (section{Symbols, etc.}): change ~ at end of \href to \nobreakspace
+
+2002-01-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): all double-line
+ \Destination commands forced onto single line
+ (section{Proposed new questions}): tidy up question on long tables
+
+ * sanitize.pl (sanitize_line): escape "*" in \cmdinvoke* :-}
+
+Tue Jan 1 09:12:47 2002 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9b, today
+
+ * add-general.tex (section{Proposed new questions}): finish off
+ longtable question
+
+Sat Dec 29 22:52:52 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8e, today
+ (section{Documentation and Help}): various corrections to books, on
+ advice from Barbara Beeton (including removing Gr"atzer's math into
+ tex, which is superseded by math into latex)
+
+Wed Dec 26 00:28:32 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * sanitize.pl (sanitize_line): add * version of 2-mandatory-arg
+ \cmdinvoke
+
+ * faq.sty: make \cmdinvoke take * (for meta-arguments)
+
+ * filectan.tex: add ltxtable
+
+ * dirctan.tex: add xtab
+
+ * add-general.tex (section{Proposed new questions}): start new question
+ on long tables
+
+Tue Dec 25 09:15:35 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: 2.5.8d, today
+
+Mon Dec 24 17:37:18 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8c, today
+ (section{Documentation and Help}): add tex by topic to "tutorials";
+ remove it from "books"
+ (section{The Background}): switch reference to tex by topic
+ (section{Documentation and Help}): restore tex by topic to "books", at
+ victor's suggestion, and cross-link to tutorials
+
+2001-12-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.8b, today
+
+ * dirctan.tex: add nedit-latex
+
+ * faqbody.tex (section{Current TeX Projects}): explain that the java
+ version is called nts
+ (section{TeX Systems}): added reference to the nedit stuff in editors
+ and shells
+
+2001-12-18 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): Added question on
+ submitting latex bug reports; minor tidies to question on array
+ spacing
+ (section{Proposed new questions}): new version of q-bug
+
+Sun Dec 16 10:17:08 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today
+
+ * dirctan.tex: add booktabs
+
+ * filectan.tex: add tabls
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ array strutting
+
+ * sanitize.pl (sanitize_line): added \'o (for peter szabo)
+
+Sat Dec 15 10:56:39 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9a, today
+
+ * add-general.tex (section{Proposed new questions}): question on
+ textrace, with references to existing outputs
+
+ * dirctan.tex: added cm-super and ec-type1
+
+ * filectan.tex: added musixtex-type1
+
+ * Makefile.CTAN (all): remove newfaq.workers
+
+ * faqbody.tex: v2.5.8a, today
+ (section{Symbols, etc.}): removed second mention of europs<->eurosans
+ difference in recommendation at end of adobe subsection
+
+2001-12-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Symbols, etc.}): added mention of latin9 and its
+ implications
+
+2001-12-10 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.9
+
+ * faqbody.tex (section{Symbols, etc.}): added euro question from
+ add-general
+ (section{How do I do X in TeX or LaTeX}): added bold-xy and ragged
+ questions from add-general
+ v2.5.8
+
+ * add-general.tex (section{Proposed new questions}): yet more fiddling
+ with euro question
+ slight typo corrected in "cancelling ragged" question; comment out text
+ referring to donald's flushboth (which hasn't surfaced yet)
+
+ * faqbody.tex (section{Current TeX Projects}): minor tidy of omega q
+
+Mon Dec 10 07:30:22 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.7i, today
+
+ * add-general.tex (section{Proposed new questions}): revision and
+ slight extension of euro question
+
+Sun Dec 9 23:19:29 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX Projects}): slight further reduction
+ of random twaddle in text of nts q
+
+2001-12-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add nts
+
+ * faqbody.tex (section{Current TeX Projects}): deflower phil's text
+ about nts a bit, and add reference to public release of nts/java
+
+ * additions.tex: pl3.8b, today
+
+ * add-general.tex (section{Proposed new questions}): bunch of new stuff
+ on how to typeset euros (from yesterday and today)
+
+ * dirctan.tex: add china2e, eurosym, eurofont
+
+2001-12-06 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): good start on euro
+ question
+
+ * dirctan.tex: add euro-fonts, marvosym-fonts
+
+2001-12-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): added scott pakin's
+ keywords to symbol list question
+ v2.5.7h, today
+ (section{The Background}): correct \href for context
+
+2001-12-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): correct syntax
+ for latest version of pdfpages package
+ v2.5.4g, today
+ (section{Introduction}): add Andreas Matthias to list of benefactors
+
+2001-11-28 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: 2.5.7f, today
+ (section{PS and TeX}): tidy up question about metrics, add reference to
+ ly1 and to walter's site of extra goodies and, and, and...
+
+2001-11-27 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): spell martin
+ schrder's name right
+
+2001-11-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.7e, today
+
+ * additions.tex: pl4.8a, today
+
+ * add-general.tex (section{Proposed new questions}): add question on
+ flushboth (after discussion with da)
+
+ * faqbody.tex (throughout): saturday's -{}- -> -\relax-
+
+Sat Nov 24 09:47:06 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): -- (in "verbatim" bits convert) to -{}-,
+ and where necessary convert |..--..| -> \texttt{..-{}-..}
+ v2.5.7d, today
+ (section{Introduction}): add thomas esser
+
+2001-11-23 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): amend words about
+ metafun manual, and redirect web address to ntg site
+ v2.5.7c, today
+
+2001-11-22 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): \nothtml-tidy typo correction
+
+2001-11-20 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.7b, today
+ (sections {The Background}, {Acquiring the Software}): micro-editorials
+ from Jose Carlos Oliveira Santos
+ (section{The Background}): added a ref to the ntg copy of context web
+ site (pending the arrival of a "real" one...)
+
+2001-11-15 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): "tiny typo"
+ (\pagnumbering) in "eliminating page numbers"
+ v2,5,7a, today
+ (section{TeX Systems}): first stab (pre-ctan availability) of reference
+ to macos x tetex and texshop; added reference under "unix" to "mac"
+ (section{Current TeX Projects}): correct signup address for omega list
+ (section{TeX Systems}): corrected spelling of wierda
+ (section{Documentation and Help}): tug.org copy of bausum's list
+
+2001-11-13 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.8, today
+
+ * add-general.tex (section{Proposed new questions}): add a question on
+ bold tt and csc
+
+ * filectan.tex: add bold-extra
+
+ * faqbody.tex (throughout}): \CTAN{}->\acro{CTAN}
+
+2001-11-07 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): change references to miktex
+ v2.5.7, today
+
+ * dirctan.tex: remove miktex directory
+
+ * filectan.tex: replace miktex-zip with miktex-install and miktex-setup
+
+2001-11-05 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7l, today
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): mention
+ ntheorem in "roman theorems", use \upshape instead of \rm in original
+ example
+ 2.5.6k, today
+
+ * add-general.tex (section{Proposed new questions}): tocbibind question
+
+Sat Nov 3 15:29:07 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): moved code
+ listings from "how do i do x"
+ (section{How do I do X in TeX or LaTeX}): removed text about 209 in
+ "log-like function"
+ (section{Things are Going Wrong}): remove rmnonsense question, and
+ reference to it in "missing symbol commands"; tidy up "missing symbol
+ commands", and add ctanrefs for amsfonts
+ (section{Things are Going Wrong}): ctanrefs for msx/y question
+
+Wed Oct 31 23:10:31 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): finished belleek stuff
+
+Tue Oct 30 23:35:48 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add belleek (just the .zip file)
+
+ * faqbody.tex (section{PS and TeX}): mention belleek (needs url for
+ paper)
+
+2001-10-30 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile (inst-perl*): add sanitize_line
+
+ * texfaq2file,texfaq2html,texfaq2html-beta: require sanitize.pl, remove
+ sanitize_line
+
+ * sanitize.pl: new file, providing sanitize_line for texfaq2*
+
+ * faqbody.tex (section{Current TeX Projects}): not :8080 for omega site
+
+Tue Oct 30 00:14:29 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX Projects}): update omega question
+
+Mon Oct 29 22:32:39 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): use richard's words re. truetype
+ (section{How do I do X in TeX or LaTeX}): detail the further brilliant
+ things titlesec can do in re. \subsubsubsection
+ (section{Special sorts of typesetting}): remove misleading remark about
+ titlesec's capabilities re. \part
+ v2.5.6l, today
+
+2001-10-29 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bibliographies and citations}): change title
+ from just "bibliographies"
+ (section{PS and TeX}): change listing of {cm,ams}-amstype1 to "browse"
+ (section{TeX Systems}): change to truetex entry as per mail from
+ richard
+
+Sun Oct 28 09:19:36 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it do that?}): correct html problem
+ spotted by donald a, and modify \xspace question according to his
+ caveats
+
+ * texfaq2html,texfaq2html-beta,texfaq2file (sanitize_line): add
+ nullification of \relax at end
+
+ * faqbody.tex (section{PS and TeX}): comlete tidying-up the outline
+ fonts question (no more now until i've viewed the result on paper)
+
+Sat Oct 27 00:55:30 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PS and TeX}): corrections/extensions from Walter
+ Schmidt, started work on ctanrefs env at end of question
+ (section{Introduction}): add Walter's name to list
+
+ * dirctan.tex: add eulervm
+
+ * faqbody.tex (section{Typesetting particular types of documents}):
+ moved typesetting a thesis here
+ (section{Bibliographies}): rearranged to put things relating to
+ creating the bib together at the start of the section, with "using" it
+ (macros etc) afterwards; moved citing urls in here
+ (section{The joy of TeX errors}): replacement "how to approach",
+ new "missing number" questions from add-general
+
+ * additions.tex: pl3.7k, today
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): rewrite
+ parenthetical remarks about gill, correct parentheses later on
+ v2.5.6k, today
+
+ * add-general.tex (section{Proposed new questions}): yet again correct
+ wrapping of examples in "macros from command arguments" (will get it
+ right eventually...)
+
+Mon Oct 22 12:48:28 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): work on active
+ character questions (can we do without a screed on catcodes
+ altogether?)
+
+ * texfaq2file,texfaq2html,texfaq2html-beta (sanitize_line): add
+ \textbar
+
+ * faq.sty: add definition of \textbar
+
+Sat Oct 20 08:26:05 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): correct jos carlos santos' name
+
+2001-10-19 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): add a label to
+ "alignment of tabular cells" question
+ v2.5.6j, today
+
+2001-10-12 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7.l1 {since redone}, today
+
+ * add-general.tex (section{Proposed new questions}): redoing work done
+ at home decreasing the verbosity of the replacement error approach q,
+ and tidying it up
+
+2001-10-11 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The joy of TeX errors}): slight rewording of
+ Q-atvert to take account of "improper \spacefactor" (which appeared in
+ a question on c.t.t)
+ v2.5.6i, today
+
+Sat Oct 6 09:17:26 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7k, today
+
+ * add-general.tex (section{Proposed new questions}): tidied missing
+ number question, start on question on skips vs. dimens
+
+2001-10-04 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7j, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ "missing number"
+
+Tue Oct 2 22:45:47 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7i, today
+
+ * add-general.tex (section{Proposed new questions}): revision of
+ general approach errors question, taking account of trace package
+
+2001-10-02 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): gratuitous tidying of
+ mail list text
+
+2001-09-26 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): greek->Greek
+ (for epsilon in question about logos and things)
+
+ * texfaq2file (oh_dear): don't print wrapper for message...
+ (two other places): replace "die" with call to oh_dear
+
+Mon Sep 24 22:41:48 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.6h, yesterday (forgot the change then)
+
+ * additions.tex: pl3.7h, today
+
+ * add-general.tex (section{Proposed new questions}): tiny typo
+ correction in \clearemptydoublepage answer
+
+2001-09-24 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added memoir
+
+ * add-general.tex (section{Proposed new questions}): question on
+ empty pages between chapters
+
+Sun Sep 23 15:37:53 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ what to do when asked to type \end
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): "referring to
+ things by name" from add-general
+ (section{Bibliographies}): "listing all bib entries" from add-general
+
+ * add-general.tex (section{Proposed new questions}): wrap dvi version
+ of some of examples in "defining macro from arg" question (and adjust
+ the title of the question
+
+ * faqbody.tex (section{Special sorts of typesetting}): a couple of
+ issues raised in proofreading (principally in description of xindy)
+
+Mon Sep 10 14:52:09 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): muck about with the "alternative
+ versions text, and add reference to the pdf copies on ctan
+
+ * filectan.tex: added uktug-faq-{a4,letter}
+
+Sun Sep 9 00:43:37 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add titleref
+
+ * add-general.tex (section{Proposed new questions}): question on title
+ references (first stab)
+
+ * additions.tex: pl3.7g, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ \nocite{*}
+
+ * dirctan.tex: add fonts/amsfonts/{latex/plaintex}
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): rehash of
+ blackboard bold question
+
+Sat Sep 8 22:02:04 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: added ntheorem
+
+ * faqbody.tex (section{Why does it do that?}): twiddling with the over-
+ full boxes question
+ (section{How do I do X in TeX or LaTeX}): answer the "end proof
+ environment with symbol" question in the affirmative, ref. ntheorem
+ v2.5.6g, today
+
+Fri Sep 7 17:01:12 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7f, today
+
+ * faqbody.tex (section{Why does it do that?}): question on overfull
+ lines from add-general
+ v2.5.6f, today
+
+Thu Sep 6 09:54:29 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html,texfaq2html-beta: minor tidies to make uniform with
+ texfaq2file
+
+Wed Sep 5 17:55:48 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): tidying wysiwyg question
+ (again)
+
+Tue Sep 4 23:03:11 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): a little tidying
+ of the new question
+
+Tue Sep 4 17:32:47 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7e, today
+
+ * add-general.tex (section{Proposed new questions}): bit of tidying of
+ one-float-per-page question, new question on defining commands whose
+ name arrives in an argument
+
+Tue Aug 28 13:01:30 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX Projects}): correct typo
+ (section{The Background}): reading tex files, and why not wysiwyg from
+ add-general
+ (section{The joy of TeX errors}): \end in group from add-general
+ (section{Special sorts of typesetting}): dropped capitals from
+ add-general
+
+Tue Aug 28 11:37:17 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * Makefile (clean): delete _all_ *.out
+
+Mon Aug 27 10:53:49 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current TeX Projects}): normalise ctan etex and
+ pdftex references (and thus reword a little)
+
+ * dirctan.tex: make e-tex and pdftex *-directories
+
+ * add-general.tex (section{Proposed new questions}): new drop caps q
+ (should we mention dropcaps, if only to deprecate it?)
+ (section{Proposed new questions}): couple of \end{verbatim} missing
+ from end groups question(!)
+
+ * dirctan.tex: add dropping, lettrine
+
+Sun Aug 26 10:24:31 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.6d, today
+
+ * additions.tex: pl3.7d, today
+
+ * add-general.tex (section{Proposed new questions}): minor proofreading
+ edits
+
+ * faqbody.tex (section{Macro programming}): minor proofreading edits
+
+Sat Aug 25 19:59:17 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Macro programming}): added proposed question on
+ macro programming
+
+ * add-general.tex (section{Proposed new questions}): tidying "\end
+ inside a group"
+
+Thu Aug 23 15:06:09 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): first outline of
+ "\end inside a group..." question
+
+Wed Aug 22 12:28:17 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): minor proof-
+ reading changes
+
+ * faq.sty: make \WYSIWYG uppercase the first letter of the start of a
+ sentence ... mostly
+
+Sat Aug 18 09:29:00 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html,texfaq2html-beta (sanitize_line): as texfaq2file
+
+ * texfaq2file (sanitize_line): redo definition of \CONTeXT
+
+ * faq.sty: redo definition of \CONTeXT
+
+ * faqbody.tex (section{Why does it do that?}): standardise reference to
+ textcase package
+ (throughout): standardise on use of \CONTeXT macro
+
+ * add-general.tex (section{Proposed new questions}): putative
+ completion of the wysiwig question (lordie, is it turgid)
+
+ * faqbody.tex (section{Current TeX Projects}): typo in the "web" bullet
+ about svg
+
+ * Makefile: have `clean' target get rid of html/* as well as _all_
+ *.aux (no need to protect newfaq.aux nowadays), and remove a redundant
+ second (empty) `ctan' target
+
+ * texfaq2html,texfaq2html-beta (sanitize_line): as texfaq2file
+
+ * texfaq2file (sanitize_line): take {} requirements off definition of
+ \textasciitilde, so it can be used in \texttt
+
+ * add-general.tex (section{Proposed new questions}): correction/
+ improvement of spaces and active chars in arguments questions
+
+Fri Aug 17 00:53:10 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7c, today
+
+ * faqbody.tex (section{Special sorts of typesetting}): remove (now
+ unwanted) braces after \textpercent
+
+ * texfaq2html,texfaq2html-beta (sanitize_line): as texfaq2file
+
+ * texfaq2file (sanitize_line): don't have \textpercent requiring braces
+ after it (since it'll inevitably appear in the argument of \texttt)
+
+ * add-general.tex (section{Proposed new questions}): another new
+ question on unwanted space in macros
+
+Thu Aug 16 00:36:09 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ active chars in args of other commands
+
+ * faqbody.tex (section{The joy of TeX errors}): correct example in
+ "structure of errors"
+ (section{Why does it do that?}): minor improvement of english in "rerun
+ messages"
+ (section{Why does it do that?}): move "hash signs doubled in macros" to
+ macro programming, and change title to "defining macros within macros"
+
+ * add-general.tex (section{Proposed new questions}): a few more words
+ on wysiwygginess...
+
+Tue Aug 14 16:16:29 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ installed on ctan; checked-in
+
+ * dirctan.tex,filectan.tex: texsis no longer nonfree
+
+ * faqbody.tex (section{Format conversions}): revised address for
+ wilfried hennings' faq
+ v2.5.6c, today
+
+Mon Aug 13 01:01:12 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): more twiddles on
+ "what to do with a latex file"
+ (section{Proposed new questions}): new question on wysiwyg-ness
+
+ * texfaq2file: sorted archive and format defaults (were left blank)
+
+Sun Aug 12 01:01:49 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): "what to do with a
+ (la)tex file" (first version)
+
+ * additions.tex: pl3.7b, today
+
+ * faqbody.tex (section{Documentation and Help}): stray char in
+ booklist; move reference to errata for math into latex back up where
+ it belongs near the reference to the book
+
+ * add-general.tex (section{Proposed new questions}): change preamble of
+ each proposed question to use \Destination
+ (section{Proposed new questions}): add reference to paragraph parameter
+ problem in \tolerance question
+
+ * faq.sty: add \Destination
+
+ * texfaq2file (sanitize_line): add \Destination
+
+ * texfaq2html,texfaq2html-beta (sanitize_line): as texfaq2file
+
+ * texfaq2file (sanitize_line): redo definition of \keywords to produce
+ html comments (works! ... if not subsequently translated to html ;-),
+ and place it at the end of if (converting ...) section
+
+ * faqbody.tex (section{Bits and pieces of TeX}): verbatim \'e (again)
+ (section{The joy of TeX errors}): and again
+ v2.5.6b, today
+
+Fri Aug 10 14:21:38 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}): silliness of html trans
+ v2.5.6a, today -- checkin
+
+Thu Aug 9 12:42:56 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: set \@rightskip, not \rightskip, in def of ctanrefs env
+
+ * additions.tex: pl3.7a, today
+
+ * add-general.tex (section{Proposed new questions}): start of question
+ about tolerance (yeah, man)
+
+ * faqbody.tex (section{Things are Going Wrong...}): missing paren added
+ in Q-nohyph
+
+Tue Aug 7 14:41:37 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): correct
+ list info for music list
+
+Mon Aug 6 16:50:12 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * [various]: checkin
+
+Mon Aug 6 13:18:02 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.7, today
+
+ * Makefile.CTAN (DEST): new location (oops!)
+
+ * faqbody.tex: 2.5.6, today
+
+Sun Aug 5 00:31:07 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): correct urls for html
+ upload scripts
+ (section{Hypertext and PDF}): pkfix question from add-general
+ (section{Macro programming}): comparing the job name question (ditto)
+ (section{Why does it do that?}): commands gobbling space (ditto)
+ (section{How do I do X in TeX or LaTeX}): repeating footnotes (ditto)
+ (section{Macro programming}): argument a number (ditto)
+ (section{How do I do X in TeX or LaTeX}): altering tabular cell
+ alignment (ditto)
+
+ * add-general.tex (section{Proposed new questions}): finally struggled
+ through section on catcodes of question on catcodes and tokens
+
+ * texfaq2file,texfaq2html,texfaq2html-beta (sanitize_line): added
+ \environment translation(!)
+
+ * add-general.tex (section{Proposed new questions}): |\\|->|\||\|
+ throughout
+
+ * texfaq2file: add ability to read files whose names appear on $ARGV;
+ correct test for new faq sections at the start of while <TEXFAQ> (NB
+ still a problem with \begin{center}\itshape in add-* files)
+
+Sat Aug 4 09:21:21 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2file (sanitize_line): update to latest version from ...2html
+
+Fri Aug 3 20:03:18 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): correct typos in
+ tabular cell alignment question
+
+Fri Aug 3 14:58:31 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): added cross-references
+ for symbols, as suggested by scott pakin
+ v2.5.5f, today
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): completed question
+ (started last night at home) on \centering et al in tabular
+
+Thu Aug 2 22:11:35 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.6f, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ detecting numbers
+
+Thu Aug 2 09:44:18 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): ctan-ann at dante.de
+ v2.5.5e, today
+
+Wed Jul 25 11:27:01 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): typo in eitan's name
+
+ * add-general.tex (section{Proposed new questions}): new question about
+ \xspace
+
+Wed Jul 25 00:07:47 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): add a word about
+ mirroring
+
+ * faq.sty: define pdfversion and dviversion on the basis of \ifpdf
+
+ * additions.tex: pl3.6e, today
+
+ * faqbody.tex (section{Introduction}): added heiko's name to list of
+ helpers
+
+ * add-general.tex (section{Proposed new questions}): new question about
+ comparing \jobname to something
+
+Tue Jul 24 22:25:54 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): rewritten the upload
+ question to reflect what goes on in the real world now
+
+ * texfaq2html[-beta] (sanitize_line): add \PS{}
+
+ * faq.sty: add \PS command
+
+ * faqbody.tex: v2.5.5d, today
+ (throughout): postscript->\PS{}, ghostscript all l-c; various other
+ minor changes
+
+ * add-general.tex (section{Proposed new questions}): postscript->\PS{}
+ throughout
+
+Mon Jul 23 12:13:51 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): reword the pkfix
+ question
+
+ * faqbody.tex (section{Support Packages for TeX}): add reference to
+ spell checkers in winedt and 4alltex (last available separately,
+ 4spell)
+ (section{TeX Systems}): junk win3.1 section of editors and shells
+ v2.5.5c, today
+
+Fri Jul 20 00:22:56 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.6c, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ pkfix
+
+Thu Jul 19 17:31:25 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Macro programming}): minor typo in list
+ numbering question
+
+Thu Jul 19 13:55:55 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.5b, today
+ (section{The Background}): inappropriate line wrap corrected, given up
+ on \nobreakspace, pro tem
+
+ * texfaq2html-beta (sanitize_line): add \nobreakspace [doesn't work...]
+
+ * add-general.tex (section{Proposed new questions}): yet more fiddling
+ with the fixed footnotes question
+
+Tue Jul 17 13:41:03 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): witter about knuth's eminence
+
+ * texfaq2html (sanitize_line): add \nobreakspace...
+
+ * faqbody.tex (section{Documentation and Help}): \url->\URL in books
+ question
+ (section{The Background}): Donald E.\nobreakspace{}Knuth ;-)
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): tidy of fixed ftnt
+ question
+
+Mon Jul 16 17:54:15 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: v3.6a, today
+
+ * add-general.tex (section{Proposed new questions}): finished question
+ on fixed-text footnotes (1st draft, anyway)
+
+Sun Jul 15 22:14:41 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): start of a
+ question on repeating footnotes
+
+ * dirctan.tex: added fixfoot
+
+ * faqbody.tex (section{TeX Systems}): join up the two download lines
+ (and alternative urls) for miktex
+ (section{Hypertext and PDF}): adjust the blurb in the first question,
+ for consistency, and wind down the implication that the hypertex
+ project is an ongoing thing
+ (section{PostScript and TeX}): rehash the basic "using ps fonts" q, add
+ mention in the previewing question that recent xdvis cope with type1
+ fonts
+ v2.5.5a, today
+
+Sat Jul 14 10:10:11 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.5, today
+ (section{Installing \AllTeX{} files}): new section, holding two
+ installation questions from "acquiring the software" and the "temp
+ installation question from add-general
+
+ * additions.tex: pl3.6, today
+
+ * add-general.tex (section{Proposed new questions}): move "format of
+ labels","multiple citations","widows and orphans","retrieving tex...",
+ "bits of docs" (changed title and label name),"extending tex paths"
+ (again, changed title to "temporary installation") -> faqbody
+
+Thu Jul 12 16:19:25 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{MF and MP}): add further caveats to this
+ question (derived from a post by dan luecking)
+
+ * add-general.tex (section{Proposed new questions}): final tweaking of
+ revised margins question -- back to faqbody, replacing old version
+
+ * faqbody.tex (section{Special sorts of typesetting}): reference
+ harvard as a possible source of urls-in-biblios
+ v2.5.4q, today
+
+Tue Jul 10 10:34:16 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): more fiddling with
+ the margins faq
+
+Mon Jul 9 16:46:44 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.5o, today
+
+ * add-general.tex (section{Proposed new questions}): proposed new
+ version of the change margins faq
+
+Thu Jul 5 16:17:44 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): insert Q-TUG* in place of
+ Q-TUG and the two following
+ (section{You're still stuck?}): change reference to be to Q-TUG* (and
+ elsewhere, plus change on reference to Q-othergroups to a reference to
+ ntg's website)
+
+ * add-general.tex (section{Proposed new questions}): remove Q-TUG*
+
+ * faqbody.tex: v2.5.4p, today
+ (section{How do I do X in TeX or LaTeX}): text from Norman Gray added
+ (section{Introduction}): add Norman Gray to the list of helpers
+
+Tue Jun 19 10:38:45 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add xpdf
+
+ * additions.tex: pl5.5m, today
+
+ * add-general.tex (section{Proposed new questions}): reference
+ pdftotext from xpdf in the "final->revisable" question
+
+Fri Jun 15 10:21:57 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta,texfaq2html (sanitize_line): deal with tildes in
+ urls in \href commands too
+
+ * faqbody.tex (section{Documentation and Help}): add reference to hans'
+ metafun manual
+ v2.5.4o, today
+ (section{Introduction}): thanks to sanjoy mahajan
+
+Thu Jun 14 10:37:46 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html[-beta] (sanitize_line): correct \textcbracesymbol in both
+
+Tue Jun 12 13:10:08 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html: as -beta
+
+ * texfaq2html-beta: translate keyword spaces to + (and vice versa) when
+ initialising $original_keyword and $keyword
+
+Mon May 28 10:30:47 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): added question on
+ \p@... commands
+
+Sun May 27 23:58:37 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.5l, today
+
+ * add-general.tex (section{Proposed new questions}): quick question on
+ mcite
+
+Thu May 24 10:21:33 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: add \environment command
+
+ * add-general.tex (section{Proposed new questions}): one use of
+ \environment
+
+ * faqbody.tex (section{Bibliographies}): moved "bibtex with plain tex"
+ from "how to do"
+ today's date (same version no)
+ (throughout): use \environment
+
+ * additions.tex: pl3.5k, today
+
+ * add-general.tex (section{Proposed new questions}): add ps2ascii to
+ the list of tools for retrieving source from final form output
+
+Wed May 23 09:32:48 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it do that?}): more alternatives for
+ avoiding the use of \verb, in Q-verbwithin
+ 2.5.4n, today
+
+Tue May 22 09:43:20 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html,texfaq2file (sanitize_line): add \Class translations from
+ texfaq2html-beta
+
+Mon May 21 18:04:02 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): \endhtmlignore in
+ tutorial question!!!
+ (section{How do I do X in TeX or LaTeX}): \thispagestyle is what
+ chapters and things use ... change Q-nopageno
+
+Fri May 18 12:45:03 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): emphasised the scottishness of
+ "loch" in the silly thing about pronunciation
+
+Wed May 16 15:08:37 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): couple of typos in
+ balancing question
+
+ * faqbody.tex (section{Documentation and Help}): add reference to david
+ basum's list of tex primitives to "online tutorials", pointing out
+ that it's reference rather than tutorial...
+ (section{Macro programming}): refer to patchcmd as a package...
+ (section{Current TeX Projects}): correct reference to latex
+ experimental code, minor tidies of omega, nts entries
+
+Mon May 14 15:15:23 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.4l, today
+ (throughout): bunch of "unguarded" \dots had {} appended...
+
+Wed May 2 00:07:49 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Hypertext and PDF}, {how do i do}, {macro
+ programming}, {special sorts of typesetting}, etc): accession of
+ questions from add-general.tex
+
+ * additions.tex: pl3.5j, today
+
+ * add-general.tex (section{Proposed new questions}): numerous minor
+ editorial hackettes...
+
+Tue May 1 23:50:40 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.4k, today
+ (section{Format conversions}): correct url for w3.org
+ (section{Why does it do that?}): no need for \verb if \texttt will do
+ (unamended...)
+
+Tue May 1 10:04:13 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it do that?}): couple of tidies in
+ \verb question so's texfaq2html can cope (both applied to current web
+ copy too)
+
+Mon Apr 30 16:36:54 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Macro programming}): restore missing
+ \endhtmlignore in "optional arguments like \section"
+
+Fri Apr 27 12:02:02 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bibliographies}): added reference to multibbl
+
+ * dirctan.tex: added dpfloat
+
+ * faqbody.tex (section{Typesetting particular types of documents}): add
+ reference to pdfpages to "report from lots of..."
+
+ * additions.tex: pl3.5i, today
+
+ * faqbody.tex (section{Why does it do that?}): add reference to \string
+ inside \texttt as a means of avoiding \verb in command args
+ v2.5.4j, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ widows and orphans
+
+ * dirctan.tex: added curve (oh joy!)
+
+ * faqbody.tex (section{Typesetting particular types of documents}):
+ added curve to the cv question
+
+Thu Apr 26 10:01:23 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): \href-ise question on
+ sources of faqs, and add reference to the latex navigator
+ (section{The joy of \TeX{} errors}): removed {center}ed note of where
+ question was to go to, in Q-atvert... (emergency patch to copy on web
+ site, too!)
+
+Wed Apr 25 14:40:22 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): added a bit of
+ uncertainty about the name of the localtexmf tree ;-)
+ (section{Special sorts of typesetting}): added multiple indexing
+ and zero paragraph indent questions from add-general
+ (section{How do I do X in TeX or LaTeX}): added footnotes in
+ captions question from add-general
+
+Tue Apr 24 12:00:01 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): added urls to tug
+ article
+ (section{Proposed new questions}): adjust the balance columns question
+ to mention patricks balance.sty and to rename mine baltools.sty
+
+Sun Apr 22 00:07:16 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): TUG article now
+ only awaiting urls
+
+ * faqbody.tex (throughout): bunch of rewriting \URL commands as \href
+ commands (incomplete)
+
+ * Makefile (html): new target to run texfaq2file
+
+Sat Apr 21 18:19:23 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): question on t1
+ type 1 fonts, and one (as yet incomplete) to replace all three on TUG/
+ other user groups
+
+ * additions.tex: v3.5h, today
+
+ * faqbody.tex (section{Hypertext and PDF}): new section starting with
+ three questions from the "format conversion" section
+ v2.5.4i, today
+
+Fri Apr 20 14:38:55 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.5g, today
+
+ * add-general.tex (section{Proposed new questions}): questions on
+ tabularx and so on, and on non-terminating "rerun" diagnostics
+
+Wed Apr 18 10:38:30 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): added a changebars
+ question
+
+ * filectan.tex: add vertbars.sty and backgrnd.tex
+
+ * dirctan.tex: moved our location to uk-tex-faq
+
+ * additions.tex: pl3.5f, today
+
+ * add-general.tex (section{Proposed new questions}): mention \[sub]
+ includefrom commands in the blurb about import.sty
+
+ * faqbody.tex: 2.5.4h, today
+ (section{Acquiring the Software}): moved findpkg, siteindex and
+ websearch questions to "acquiring the software", and edit blooper out
+ of findpkg
+
+Mon Apr 16 00:16:21 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): start on question
+ about retrieving tex-ish source from final form files
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): added list
+ spacing question from add-general (should this really go to
+ typesetting?)
+ (section{Macro programming}): opt arg and counter-label questions from
+ add-general
+ (throughout): minor editorial change
+ (section{Acquiring the Software}): make reference to web access in the
+ question about archives, and remove reference to the DECUS collection
+ (section{Acquiring the Software}): tone down the question about finding
+ fonts (how does one do this nowadays?)
+ (section{Format conversions}): refer to w3c page on ->html conversion
+
+Sun Apr 15 00:12:06 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): removed the
+ "finding a document's files" proto-question, now taken over by
+ "extending search paths"
+
+ * faqbody.tex (section{You're still stuck?}): add "you don't understand
+ the answer", and "submitting new answers" questions from add-general
+ (section renamed from "perhaps there isn't an answer")
+ v2.5.4g, today
+
+ * markup-syntax: grand updating (for the submission faq)
+
+ * add-general.tex (section{Proposed new questions}): more new uns: opt
+ args that behave like \section's, \refstepcounter and submitting
+ material to the faq
+
+ * additions.tex: pl3.5e, today
+
+ * add-general.tex (section{Proposed new questions}): two new questions,
+ on extending path searches (needs careful review) and on loading files
+ from other directories (the import package)
+
+Sat Apr 14 18:52:30 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: add import.sty (up-to-date or what?)
+
+Fri Apr 13 16:50:41 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added pkfix, preprint
+
+Thu Apr 12 11:28:24 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): reference to
+ anonchap (and incidentally tocbibind) in "style of section headings"
+
+ * filectan.tex: added anonchap
+
+Tue Apr 10 00:00:30 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\MF{} and \MP{}}): renamed section, added
+ question on \MP{} prologues from add-general
+ (section{Special sorts of typesetting}): added questions on style of
+ captions and of document titles, from add-general, and style of
+ section headings and indent after section headings from herein, "how
+ do I do?"
+
+ * texfaq2file: removed redundant $href_script, remove echoing of
+ archive list
+
+ * faqbody.tex: 2.5.4f, today
+
+ * additions.tex: pl3.5d, today
+
+ * faqbody.tex (section{Macro programming}): new section with vaguely
+ programming-related things (6 from "how to do X", one from "things are
+ going wrong" and one from "why does it", plus a new one from
+ add-general.tex
+
+Mon Apr 9 23:59:40 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Typesetting particular types of documents}):
+ changed section name
+
+Mon Apr 9 12:08:07 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong...}): <some damned thing>
+ (section{How do I do X in TeX or LaTeX}): incorporated donald a's
+ comments on the hyphenation and raggedness questions
+
+Sun Apr 8 00:32:22 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2file: quick'n'dirty html file generator
+
+Sat Apr 7 16:35:58 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): define \Class
+
+ * faq.sty: add definition of \Class
+
+ * additions.tex: pl3.5c, today
+
+ * add-general.tex (section{Proposed new questions}): question on zero
+ parindent/non-zero parskip
+
+ * filectan.tex: add parskip
+
+Thu Apr 5 10:25:00 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ determining which side of the page we're on
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): hyphenation and
+ ragged right questions from add-general
+ v2.5.4e, today
+
+Wed Apr 4 13:16:41 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added patchcmd
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): refer to
+ patchcmd in question on (er) patching commands
+
+ * add-general.tex (section{Proposed new questions}): bit more
+ detail on the behaviour of ragged2e
+
+ * faqbody.tex (section{Bibliographies}): bibtex string too long
+ question moved here from "things going wrong"
+
+Wed Apr 4 00:09:17 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): question on ragged
+ right setting, needed by the now-finished hyphenation question
+
+ * faqbody.tex (section{Things are Going Wrong...}): added reference to
+ hyphenat in question about why hyphenation isn't happening
+
+ * dirctan.tex: added hyphenat, schroeder
+
+ * additions.tex: today
+
+ * add-general.tex (section{Proposed new questions}): started "no
+ hyphenation" question
+
+Tue Apr 3 00:21:27 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it do that?}): tidy marginpar and
+ pictex questions
+ v2.5.4d, today
+ (section{Things are Going Wrong...}): \tenrm question, remove .sty from
+ rawfonts
+
+ * add-general.tex (section{Proposed new questions}): minor tidies of
+ the two caption questions
+
+ * additions.tex: today
+
+ * add-general.tex (section{Proposed new questions}): do example in
+ caption format question in the usual three styles, and slight change
+ to text about typesetting caption.dtx for caption2
+
+Mon Apr 2 07:56:15 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): skeleton of
+ question on title formats (vehicle for titling.sty)
+
+ * dirctan.tex: add titling
+
+Sun Apr 1 20:40:44 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * filectan.tex: added chngcntr.sty
+
+ * additions.tex: pl3.5b, today
+
+ * add-general.tex (section{Proposed new questions}): added questions on
+ caption formats, and on footnotes in captions
+
+ * dirctan.tex: added symbols, caption, ccaption
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): rationalise
+ mention of chngpage package in "adjusting the margins"; mention
+ ccaption in the wide figures question; reference to chngcntr in
+ counter manipulation question
+ (section{The joy of TeX errors}): slight reword of \@ question
+ (section{Documentation and Help}): added question about symbols list
+ (head of file): v2.5.4c, today
+
+Thu Mar 29 14:13:36 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): as production version
+
+ * texfaq2html (sanitize_line): ignore \vspace*
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): tidied visual
+ typesetting so's texfaq2html could cope, added a missing \\ (names
+ question)
+
+Wed Mar 28 22:42:32 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): added \seename
+ and \alsoname to the list of names
+
+Wed Mar 28 09:25:54 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: add excel2latex (the .zip file thereof)
+
+ * faqbody.tex: v2.5.4a, today, for ctan installation, then v2.5.4b
+ (section{Format conversions}): added excel2latex
+
+ * dirctan.tex: add fink
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): shortened
+ written-out code for retaining file names, and added reference to
+ fink package
+
+Tue Mar 27 13:05:22 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.5a, today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ multiple indexes
+
+ * filectan.tex: added multind.sty
+
+ * dirctan.tex: added camel
+
+Mon Mar 26 14:08:37 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl3.5
+
+ * texfaq2html: bring up to date with -beta
+
+ * faqbody.tex: v2.5.4, today, for release
+
+Mon Mar 26 00:11:55 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today's date
+
+ * add-general.tex (section{Proposed new questions}): start of questions
+ on finding files in multi-file docs, and latex makefiles
+
+Sun Mar 25 10:17:04 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: dated today
+
+ * faqbody.tex (section{Bibliographies}): added bibtex capitalisation,
+ cite sorting, \subsubsubsection and file name qs from add-general
+ dated today
+
+ * add-general.tex: new question on lists
+ (section{Proposed new questions}): add reference to the companion in
+ \sub*section question
+
+Sat Mar 24 15:22:18 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): minor tidying of
+ the missing chars question
+
+ * faqbody.tex (section{Current TeX Projects}): added question on web
+ technologies, from add-general
+ (section{How do I do X in TeX or LaTeX}): added Q-fixnam, with list of
+ fixed names included
+
+ * add-general.tex: added column balancing question
+
+ * dirctan.tex: added nrc
+
+ * additions.tex: pl3.4m, today
+
+ * faqbody.tex (section{PostScript and TeX}): tidy up references to
+ ghostscript, gsview and (new) ghostview
+ (throughout): ensure ghostscript is properly referred to
+ v2.5.3r, today
+
+ * dirctan.tex: restore gsview link as *-directory (this stuff needs
+ moving on ctan)
+
+ * faqbody.tex (section{MF}): remove reference to paradissa which is no
+ longer on the archive
+
+ * dirctan.tex: add sttools
+ removed remaining things found in ctan scan
+
+ * faqbody.tex (throughout): impose consistency on part distributions in
+ ctanrefs environments
+
+Fri Mar 23 08:09:03 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.3q, yesterday
+
+ * additions.tex: pl3.4k, today
+
+ * add-general.tex (section{Proposed new questions}): major hack on the
+ new web technologies question; new question on what to do if you don't
+ understand
+
+Thu Mar 22 10:24:58 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added pmx and mtx
+
+ * faqbody.tex (section{Special sorts of typesetting}): tidied feynmann
+ question, and added reference to axodraw
+ (section{Special sorts of typesetting}): updated the musi[cx] question,
+ with very aged input from werner icking
+
+ * filectan.tex: added axodraw as a single file (after examining the
+ actual ctan holding)
+
+ * dirctan.tex: removed axodraw
+
+ * faqbody.tex (section{TeX Systems}): comment out the windows 3.1 stuff
+ in "editors and shells" (including the reference to eddi4tex), and
+ refer to the 4alltex cd under (current) windows
+
+ * add-general.tex (section{Proposed new questions}): sorted list of
+ \*name commands (on the *-bits) and corrected somewhat
+
+ * dirctan.tex: add pdfpages
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): mention
+ pdfpages in Q-conditional
+
+Wed Mar 21 13:43:55 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): mention
+ \verbatimtabinput in verbfile
+
+Tue Mar 20 07:54:30 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): suppress mention of
+ sgmlbase (in the absence of evidence that it's going anywhere beyond
+ the toy status); masses of tidying of questions
+
+ * dirctan.tex: make psfonts browsable
+
+ * texfaq2html-beta (sanitize_line): add a 3-mandatory-arg version of
+ \cmdinvoke; add \ae{}
+
+ * Makefile: add a bunch of short aliases for parts of make patch
+
+ * faq.sty: increase ctanrefs \topsep a bit (4pt: half of article.cls
+ default)
+
+ * add-general.tex (section{Proposed new questions}): body to Q-fixnam
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): remove some
+ text of Q-latexwords to Q-fixnam and add reference to that question
+ today's date; tidy code listings, logos questions
+
+ * add-general.tex (section{Proposed new questions}): put reference to
+ docs at end of bibtex caps question
+
+Mon Mar 19 23:18:19 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.4j
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): add question on
+ patching commands from add-general
+ (section{The joy of TeX errors}): \@ question from add-general
+ v2.5.3p
+
+ * add-general.tex (section{Proposed new questions}): corrected code in
+ "what's the name", rewrote sort&compress (for typographic reasons);
+ moved patching and \@ questions to faqbody
+
+Mon Mar 19 16:38:02 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added snapshot
+
+ * add-general.tex (section{Proposed new questions}): added some words
+ about mike downes's snapshot package, and correct the etex csname i
+ couldn't remember while typing at home (\middle)
+
+Mon Mar 19 08:47:50 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): rather feeble
+ question on bibtex capitalisation
+
+ * filectan.tex: add braket
+
+ * add-general.tex (section{Proposed new questions}): mostly-complete
+ question on dirac brackets
+
+ * additions.tex: today's date
+
+ * faqbody.tex: today's date
+ (section{Special sorts of typesetting}): tidy the "typesetting urls"
+ and "citing urls" questions, and add mention of hyperref's ability to
+ ignore %<eol> in urls
+
+ * dirctan.tex: add bundledoc
+
+ * add-general.tex (section{Proposed new questions}): first stab at
+ "what files" question
+
+Sun Mar 18 08:33:36 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, no change of versiion
+ (section{How do I do X in TeX or LaTeX}): tidy page-size question and
+ add reference to layout.sty for the diy-er; tidy the letterspacing
+ answer
+
+Sat Mar 17 13:35:37 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): \YandY->Y&amp;Y (!)
+
+ * add-general.tex (section{Proposed new questions}): sorting cites
+ question
+
+ * filectan.tex: add patch
+
+ * add-general.tex (section{Proposed new questions}): questions on file
+ name, patching commands
+
+ * faq.sty: minor adjustments (a) to separate the list from its
+ preceding pargraph, so that raggedness doesn't propagate backwards
+ into that paragraph(!) and (b) to set \topsep zero (prob. not nec.)
+
+ * faqbody.tex (section{The joy of TeX errors}): rehash unprocessed
+ floats question
+ v2.5.3o, today
+
+ * add-general.tex (section{Proposed new questions}): new "errors"
+ question on \@ in vertical mode; minor hacks
+
+ * faqbody.tex (section{Things are Going Wrong...}): tidy up (and
+ marginally correct) the \pagestyle{empty} question, and add soul to
+ the underline question; tidy old font names question; separate the two
+ case in missing symbols question; rehash the \@ question in the light
+ of Q-atvert
+
+Fri Mar 16 13:34:54 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): added scott pakin to helpers
+ list
+ (section{Things are Going Wrong...}): typo \CTANref{morefloats} for
+ endfloat
+
+ * add-general.tex (section{Proposed new questions}): removed tmupfl
+ question
+
+ * faqbody.tex: v4.5.3n, today
+ (section{Documentation and Help}): deja->groups.google
+ (section{Things are Going Wrong...}): remove some of text from Q-floats
+ and replace with reference to Q-tmupfl
+
+ * additions.tex: pl3.4i, today
+
+Fri Mar 16 00:19:03 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): changed title of
+ future web technologies
+ (section{Proposed new questions}): added tmupfl question
+
+Thu Mar 15 10:19:40 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it _do_ that?}): added mdwlist to the
+ "no line here to end" question
+
+ * additions.tex: pl3.4h, today
+
+ * add-general.tex (section{Proposed new questions}): new thing (with
+ stuff from the latex2html question) about the nature of future web
+ technologies
+
+ * faqbody.tex: 2.5.3m, today
+ (section{Format conversions}): yet another rehash of latex2html,
+ following further input from hutchinson
+
+Thu Mar 15 00:20:49 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): yet another iteration,
+ following input from eitan
+ (section{Why does it _do_ that?}): added reference to expdlist for the
+ no line to end question
+ (section{How do I do X in TeX or LaTeX}): tidy conditional compilation
+ and bold greeks questions
+
+Wed Mar 14 09:48:48 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: added \latex2html
+
+ * texfaq2html-beta (sanitize_line): added \latexhtml
+
+ * faqbody.tex (section{Why does it do that?}): added "no line" question
+ (section{How do I do X in TeX or LaTeX}): added "wide figure" question
+
+ * add-general.tex (section{Proposed new questions}): add an actual
+ recommendation on setting wide equations, and move to faqbody
+ (section{Proposed new questions}): no line to end error message too
+ wide for 2-col text, sorted; question moved to faqbody
+
+ * faqbody.tex: today (no change of version since nothing printed
+ (section{Introduction}): add peter wilson -- oops!
+ (section{Documentation and Help}): add "short history of the printed
+ word"
+ (section{Things are Going Wrong...}): minor honing of words of accented
+ hyphenation question and moving tables
+ (throughout): suppress (almost) all personal email addresses
+ (section{Things are Going Wrong...}): add mention of float.sty [H] in
+ the moving tables question
+
+Wed Mar 14 00:12:56 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): preserve ~ in arguments of URLs
+
+Tue Mar 13 22:59:56 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong...}): add the famous
+ arseneau parameters to the moving tables question, and add reference
+ to placeins.sty (simultaneously tidying up and de-ponceing the text a
+ bit)
+ v2.5.3k, today
+ (section{Format conversions}): input from eitan gurari and ian
+ hutchinson (coo, they were quick)
+ (section{Introduction}): added eitan gurari and ian hutchinson to the
+ hall of fame
+
+Mon Mar 12 11:33:47 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: added tth, tex4ht
+
+ * faqbody.tex (section{Format conversions}): ->html question rehashed,
+ including reference to texpider and hevea (both off ctan)
+
+ * dirctan.tex: make latex2html \CTANdirectory*
+
+ * faqbody.tex (section{Format conversions}): rewrote the ->ascii
+ question, including reference to tex2mail and catdvi
+ v2.5.3j, today
+
+ * dirctan.tex: added catdvi
+
+ * faqbody.tex (section{TeX Systems}): removed arbortext and northlake
+ from list of commercial systems (advice from bnb); add keywords to the
+ two systems questions so's bnb can find them by searching
+
+Sun Mar 11 09:22:44 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question about
+ subsubsubsections
+
+ * dirctan.tex: add latex (for base dir) and remove fonts/latex with the
+ same name
+
+ * additions.tex: today (no change of patch level)
+
+ * add-general.tex (section{Proposed new questions}): new question about
+ "no line here to end"
+
+Sat Mar 10 15:22:05 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): removed two
+ questions for the benefit of faqbody (vide infra)
+ (section{Proposed new questions}): new wide-figure question
+
+ * faqbody.tex (section{TeX Systems}): added vtex for linux & os/2
+ (section{DVI Drivers and Previewers}): new question about using
+ ghostscript in default of a printer-specific driver
+ (throughout): typos corrected
+ (section{Bits and pieces of TeX}): added encoding and eps questions
+ from add-general
+ v2.5.3i, today
+
+ * faq.cls: added hyphens option when loading url.sty
+
+Fri Mar 9 10:41:09 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): correcting a couple of
+ names, and a typo, in the section on conversion to "other formats"
+
+Thu Mar 8 09:15:30 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.3g, today
+
+ * additions.tex: pl3.4f, today
+
+ * add-general.tex (section{Proposed new questions}): remove questions
+ on character shifts in dvips output, toc, running equation etc,
+ crop marks and fixed positions
+
+ * faqbody.tex (section{Format conversions}): reformat the general
+ conversions question
+ (section{Literate programming}): add reference to dtx in the literate
+ programming question, and tidy up the packages question
+ (section{Support Packages for \TeX{}}): tidy up the spelling, wordcount
+ and fig questions
+ (section{DVI Drivers and Previewers}): minor tidies of previewers
+ (including excision of reference to dviwin, which has been withdrawn)
+ and laserjet questions, and removed reference to dvitops from the ps
+ output program
+ (section{Things are Going Wrong...}): added question on character
+ shifts in dvips output
+ (section{Special sorts of typesetting}): add toc question (from
+ peter wilson, originally)
+ (section{How do I do X in TeX or LaTeX}): add running equation etc,
+ crop marks and fixed positions questions
+
+ * dirctan.tex: add rtf2latex2e
+
+ * faq.sty: compact decsription environment, too
+
+ * faqbody.tex (section{Format conversions}): add question on quality of
+ PDF output, from add_general; tidy up question on generating pdf, link
+ to one on quality
+
+Tue Mar 6 23:18:23 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): narrow some of
+ the lines of code in principal value integral question, when doing
+ tex-only output; tidy footnotes in tables question
+
+ * add-general.tex (section{Proposed new questions}): wrap code in
+ running numbering question, when doing tex-only output
+
+ * faqbody.tex (section{Macros for Particular Types of Documents}): add
+ peter wilson's combine stuff to the question on multi-article
+ documents, and minor tidy of the vita class question
+
+Tue Mar 6 10:03:40 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: added removefr
+
+ * add-general.tex (section{Proposed new questions}): add "running
+ numbering" question
+
+ * faqbody.tex (section{Bits and pieces of TeX}): yet more diddling with
+ ec question
+
+ * additions.tex: pl3.4e, today
+
+ * faqbody.tex (section{Acquiring the Software}): removed ip address of
+ wuarchive
+ (section{Bits and pieces of TeX}): small rewording of hyphenation q
+ v2.5.3f, today
+ (section{Bits and pieces of TeX}): extend and reword ec font q
+
+ * add-general.tex (section{Proposed new questions}): minor improvements
+ to text of encoding and acrobat questions
+
+Mon Mar 5 11:40:20 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): two minor
+ improvements to the encodings, pdf output questions
+
+ * faqbody.tex (section{Acquiring the Software}): fptex local default is
+ texmf-local
+
+Sun Mar 4 00:00:57 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (chapter{Preface}): tidy "style of section headings"
+ (section{PostScript and TeX}): tidy wrapping of urls in the font
+ choice question
+ v2.5.3e, today
+
+Sat Mar 3 13:59:57 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): tidying the
+ section (un)numbering question
+
+ * dirctan.tex: added tocloft
+
+ * add-general.tex (section{Proposed new questions}): dvips output for
+ pdf, weird character mapping questions
+ (section{Proposed new questions}): added peter wilson's tocloft
+ question
+
+ * dirctan.tex: added textpos
+
+ * add-general.tex (section{Proposed new questions}): crop and textpos
+ questions
+
+ * faqbody.tex (section{\TeX{} Systems}): added brief info from carlos
+ santos re. windvi's printing capability
+ (section{Introduction}): added carlos santos to list of helpers
+ v2.5.3d, today
+ (section{Special sorts of typesetting}): tidied the fancyhdr question
+
+ * additions.tex: today (no change of patch level)
+
+ * add-general.tex (section{Proposed new questions}): yet again, hacking
+ at encodings question
+
+Fri Mar 2 14:22:08 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * filectan.tex: askinclude now from latex/contrib/other/misc
+
+ * dirctan.tex: removed mathpple
+
+Fri Mar 2 07:20:03 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today (no change of patch level)
+
+ * add-general.tex (section{Proposed new questions}): yet more fiddling
+ with the encodings question ("philosophy")
+
+Thu Mar 1 21:20:49 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): filled out the
+ body of "what is encapsulated postscript"
+
+ * additions.tex: pl3.4c, today
+
+ * add-general.tex (section{Proposed new questions}): honing the words
+ in "what are encodings"
+
+ * faqbody.tex (section{PostScript and TeX}): add mathpazo (serious drop
+ off that i hadn't mentioned it before)
+
+ * dirctan.tex: add mathpazo
+
+ * faqbody.tex: v2.5.3c, today
+
+Thu Mar 1 09:44:55 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and TeX}): added pxfonts to question
+ on font choice, updated txfonts outline
+
+ * dirctan.tex: added emtextds, pxfonts
+
+ * faqbody.tex (section{Things are Going Wrong...}): hack around to
+ cause texfaq2html not to be fazed by verbatim \\ commands
+ (section{TeX Systems}): ftp.math.utah.edu's ip address has changed --
+ removed it altogether
+
+ * texfaq2html-beta (sanitize_line): explicitly squash "{}" if it
+ survives to the end of the main conversion scan
+
+ * filectan.tex: morefloats->latex/contrib/other/misc
+
+Tue Feb 27 07:20:48 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.4b, today
+
+ * faqbody.tex (section{TeX Systems}): slight rearrangement of ctanrefs
+ in "(la)tex for different systems"
+
+ * add-general.tex (section{Proposed new questions}): three questions
+ transferred (see below)
+ (section{Proposed new questions}): bunch of diddling with the encodings
+ question (still not right, though)
+
+ * faqbody.tex (section{Special sorts of typesetting}): hack the
+ indexing question (new style ctan references, expand remarks about
+ xindy and about makeindex sorting issues)
+ (throughout): minor markup adjustments/typo corrections
+ (section{Special sorts of typesetting}): verbatim input, line numbering
+ and typesetting urls questions tidied to new format
+ (section{How do I do X in TeX or LaTeX}): using underscores, no page
+ nos and typing "@", from add-general
+
+ * dirctan.tex: * to xindy
+
+ * faqbody.tex: v2.5.3b, today
+
+Sun Feb 25 00:09:42 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): tidied up the freely-distributed
+ software question
+ (section{\TeX{} Systems}): further iteration of same (after a good
+ night's sleep ;-), also added more detail about web2c
+ (section{Special sorts of typesetting}): converted the `wrapping
+ figures' to new form, since it always did look untidy.
+
+Sat Feb 24 00:07:21 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{TeX Systems}): start of rearranging the non-
+ commercial systems part of the section
+
+ * dirctan.tex: added bakoma-tex
+
+ * faqbody.tex (section{Bits and pieces of TeX}): add "what is hyphen-
+ ation" question
+ (section{The joy of TeX errors}): add "bad hyphenation" question
+
+ * add-general.tex (section{Proposed new questions}): remove "what is
+ hyphenation" and "bad hyphenation" questions
+
+ * additions.tex: pl3.4a, today
+
+ * dirctan.tex: plain now refers to base only
+
+ * faqbody.tex (section{Things are Going Wrong...}): added "no
+ hyphenation" question at start of section
+
+ * add-general.tex (section{Proposed new questions}): removed "no
+ hyphenation" question
+
+ * faqbody.tex (section{Metafont}): scale down the panic of the bitmap
+ fonts question -- convert into advice to start using type 1 versions
+ v2.5.3a, today
+
+ * dirctan.tex: bluesky (was a reference to their mac mf port) becomes a
+ reference to the "bluesky" cm fonts
+
+Fri Feb 23 23:54:03 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: ps-type1 -> \CTANdirectory*
+
+Thu Feb 22 12:28:58 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html: brought in all -beta changes
+
+ * texfaq2html-beta: sit on $_ (in case we're not producing an intro) so
+ as not to get a lone "introduction", and dump the "index" statement in
+ front of the list of questions; various other minor tidies
+
+ * dirctan.tex: corrected dratex (another from dan l)
+
+ * faqbody.tex (section{Special sorts of typesetting}): mfpic can now do
+ \MP output (alert from dan luecking)
+
+Thu Feb 22 07:30:54 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and TeX}): first stab at rehashing
+ the figures question (pretty major rewrite, but issues remain)
+ today's date
+
+Wed Feb 21 09:17:47 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-beta: blundering attempt to create a better header; and
+ similarly distance from uktug in the footer
+
+ * faqbody.tex (section{PostScript and TeX}): redo question about
+ previewing files with type 1 fonts in 'em
+ (section{The Background}): less prissy about the reference to the list
+ of commercial vendors
+ (section{Format conversions}): tidy up question about generating pdf
+ (was talking about archaic versions of ghostscript)
+ (section{PostScript and \TeX{}}): renamed question deploying type 1
+ fonts ... substantial rewrite
+ (section{Introduction}): added mike vulis to ack list (belatedly)
+
+ * dirctan.tex: ghostscript nonfree; added gsview (with wrong value)
+
+ * faqbody.tex: v2.5.3, today
+
+Tue Feb 20 11:46:36 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: add a couple of <hr> directives, after the
+ "preamble", and before the "tail"
+
+ * dirctan.tex: added refcheck and crop
+
+Mon Feb 19 10:40:43 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bibliographies}): entire new section
+
+ * add-biblio.tex: ripped out entire text
+
+ * faqbody.tex (section{Special sorts of typesetting}): added the
+ document font sizes question
+
+ * add-general.tex (section{Proposed new questions}): removed the
+ document font sizes question
+
+ * faqbody.tex (section{Special sorts of typesetting}): added the
+ landscape typesetting question
+
+ * add-general.tex (section{Proposed new questions}): removed the
+ landscape typesetting question
+
+ * faq.sty: added a bit of raggedness to the ctanrefs environment
+
+ * faqbody.tex (section{Things are Going Wrong...}): add the end-line
+ question
+
+ * add-general.tex (section{Proposed new questions}): removed the end-
+ line thing
+
+ * texfaq2html: bring up to date with -beta (== -alpha) version
+
+ * faqbody.tex (section{Introduction}): add dan luecking
+
+ * add-general.tex (section{Proposed new questions}): added caveat about
+ viewing rotated output to landscape question
+
+ * texfaq2html-alpha (sanitize_line): add \YandY [does a raw & really
+ work reliably in html?]
+
+ * faq.sty: define \YandY
+
+ * faqbody.tex (throughout): \YandY for the company, for consistent
+ typesetting
+
+Sun Feb 18 00:14:33 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): rewording of the
+ "what is hyphenation" and "encodings" questions
+ (section{Proposed new questions}): new question on landscape
+ typesetting
+
+ * additions.tex: update to today
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ encodings (started yesterday)
+
+Sat Feb 17 15:56:43 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.4, today
+
+ * faqbody.tex: v2.5.2f, today
+ (throughout): article->FAQ where appropriate
+ (section{How do I do X in TeX or LaTeX): alter "changing babel's ideas"
+ to one that takes in the whole gamut, and thus renders redundant:
+ (section{Why does it do that?}): "why won't fixed names stay fixed",
+ which is therefore deleted
+
+ * newfaq-patch.tex,letterfaq.tex,newfaq.tex: slim down heading, again
+
+ * faqbody.tex (throughout): Plain \TeX{} now uniformly used
+ (subsection*{Finding the Files}): new slim-line slightly less pompous
+ intro (no tedious lists of committee members, which are impossible to
+ maintain when the committee don't maintain their web site)
+
+ * add-general.tex (section{Proposed new questions}): filled out the
+ \hyphenation error question
+
+ * texfaq2html-alpha: deal with label=, generate a label= URL at end for
+ people to quote, use \faqfiledate, \faqfileversion (oops)
+
+Fri Feb 16 13:59:41 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-alpha (sanitize_line): add code for \textbf
+
+Thu Feb 15 11:25:45 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): add the babel
+ question at end of section
+
+ * add-general.tex (section{Proposed new questions}): tidied up
+ representation of the babel error messages still further (option for
+ pdf printing, too)
+ (section{Proposed new questions}): removed babel question
+
+ * additions.tex: pl3.3, today
+
+ * faqbody.tex: 2.5.2e, today
+
+ * add-general.tex (section{Proposed new questions}): add the miktex 2
+ gen for the babel "add new language" question
+
+ * faqbody.tex (section{Acquiring the Software}): minor typographic
+ consistency changes in description of miktex 2.0 package install
+
+Wed Feb 14 13:44:07 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong...}): tidied up the
+ question about hyphenating accented letters
+ v2.5.2d, today
+
+ * add-general.tex (section{Proposed new questions}): start on question
+ about "improper hyphenation" error message
+
+ * texfaq2html-beta (sanitize_line): added \csx
+
+Mon Feb 12 14:42:27 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: 2.5.2c, today
+ (section{Documentation and Help}): recorded details of knuth boxed set
+
+Fri Feb 9 11:33:00 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.2b, today
+ (section{Documentation and Help}): replaced old references to french
+ and german faqs with a {booklist}, and added spanish and czech
+ (section{The Background}): slight iteration of the context question
+
+Thu Feb 8 13:41:36 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): question on \\
+ arguments
+
+Wed Jan 31 11:41:12 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: extra indirection (via texinfo) for both texinfo and
+ makeinfo
+
+ * faqbody.tex (section{The Background}): texinfo to use whole (sub-)
+ directory reference
+
+ * filectan.tex: removed texinfo-dist (no longer on archive)
+
+ * faqbody.tex (section{Format conversions}): expand referencing of vtex
+ (this is going to look gross...)
+
+ * dirctan.tex: pass to deal with check-ctan-lists diagnostics
+
+ * faqbody.tex (section{Special sorts of typesetting}): \textpercent{}
+
+ * texfaq2html-beta (sanitize_line): added \item[\normalfont{}...];
+ require \textpercent{}
+
+ * add-biblio.tex (section{Bibliographies}): added question on entries
+ in text of docs; added body of "writing your own .bst" question
+
+ * dirctan.tex: added inlinebib, jurabib, footbib
+
+Wed Jan 31 00:04:26 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex,additions.tex: \faqfileversion, \faqfiledate (because of
+ the confusion with definitions introduced by nameref.sty
+
+ * faqbody.tex: v2.5.2a, today
+
+Tue Jan 30 23:28:17 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl3.1, today
+
+ * newfaq.tex,letterfaq.tex,newfaq-patch.tex: use \ref* in the title,
+ \ifpdf; \faqfileversion, \faqfiledate
+
+ * add-general.tex (section{Proposed new questions}): have the correct
+ layout of the babel message (in the "new language" question) for html
+ generation
+
+Mon Jan 29 12:17:28 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html: bring up to date with latest thinking in -beta version
+
+ * faq.sty: add \[oc]bracesymbol
+
+ * texfaq2html-beta (sanitize_line): moved \symbol to the end
+ (sanitize_line): add \obracesymbol and \cbracesymbol
+
+ * additions.tex: comment out add-errors, pl3.0, today
+
+ * faqbody.tex (section{TeX Systems}): tidied miktex text
+ v2.5.2, today
+ (section{The joy of TeX errors}): moved en bloc from add-errors
+
+Tue Jan 23 16:58:28 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong...}): update the miktex
+ question with a reference to 2.0
+ (section{TeX Systems}): update remarks about miktex
+
+ * dirctan.tex: miktex itself now a *-reference to miktex/2.0
+
+ * filectan.tex: deleted miktex-latex, added miktex.zip
+
+Fri Jan 19 12:46:49 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile (clean): add *patch.aux
+
+ * add-general.tex (section{Proposed new questions}): question-ette
+ about typing @ signs
+
+ * additions.tex: pl2.14, today
+
+ * add-general.tex (section{Proposed new questions}): change reference
+ to carlisle to nopageno (\CTANref doesn't have a * form -- duh!)
+
+Thu Jan 18 11:37:53 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question on
+ "no page numbers"
+
+ * req.qs: bbl2html question
+
+Wed Jan 17 13:33:56 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl2.13, today
+
+ * add-general.tex (section{Proposed new questions}): question on eps
+ (outline only, as yet)
+
+Tue Jan 16 12:05:46 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): definition of \item _doesn't_ need
+ "."s to separate the variable instances...
+
+ * faqbody.tex (section{Introduction}): make reference to the dante faq
+ use \href
+
+ * texfaq2html-beta (sanitize_line): add \href
+
+ * faqbody.tex (section{The Background}): add knuth's url to the first
+ occurrence of his name
+
+ * faq.sty: add an \href command, that only has effect in the absence of
+ pdf generation (hyperref providing the necessary otherwise)
+
+ * faqbody.tex: v2.5.1d, today
+ (section{Documentation and Help}): corrected isbn for lamport 2nd ed
+ (section{Documentation and Help}): add reference to knuth's nimellium
+ boxed set (though no details since a-w can't get their act together)
+ (section{Documentation and Help}): update math into latex reference to
+ vol 3
+
+Tue Jan 16 11:40:37 2001 Robin Fairbairns <rf@huntingdon.cl.cam.ac.uk>
+
+ * additions.tex: pl2.12, today
+
+ * filectan.tex: underscore
+
+ * add-general.tex (section{Proposed new questions}): question on
+ underscore
+
+Sun Jan 14 20:59:29 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-errors.tex (section{The joy of TeX errors}): more on the
+ structure question
+
+ * additions.tex: pl2.11, today
+
+ * add-errors.tex (section{The joy of TeX errors}): refer to structure
+ question from the philosophy question
+
+ * add-general.tex (section{Proposed new questions}): reindented the
+ "missing character" messages for the tex versions
+
+Fri Jan 12 14:06:40 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: today's date (previous pl not yet printed out)
+
+ * add-general.tex (section{Proposed new questions}): finished the
+ hyphenation question, and added another about hyphenation problems and
+ their solution
+
+Thu Jan 11 21:42:45 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex: pl2.10, today
+
+ * add-general.tex (section{Proposed new questions}): start of the body
+ of the hyphenation question
+
+Tue Jan 9 14:59:56 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): minor tweaks to
+ the text of the babel question, and skeleton for a question on hyphen-
+ ation
+
+ * additions.tex: pl2.9, today
+
+ * add-errors.tex (section{The joy of \TeX{} errors}): v1 closure on
+ first question of section, and proposal for yet another new question
+ about the structure of error messages
+
+ * faq.sty: adjust \topsep in itemize and enumerate, and do the same to
+ verbatim
+
+ * faqbody.tex (section{The Background}): change reference to books
+ question
+
+ * add-biblio.tex (section{Bibliographies}): some wrapping of verbatim
+ text, and minor text tidies
+
+Fri Jan 5 18:08:32 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl2.8, today
+
+ * add-general.tex (section{Proposed new questions}): added caveat about
+ running out of pattern memory when adding a new hyphenation pattern
+
+Thu Jan 4 15:44:41 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): process `` and '' to ", and
+ isolated ` to ' (for the benefit of m$ browsers)
+ evaluate $last_question, $next_question and $previous_question as
+ we go along, and use them to produce pointers to previous and
+ next in the footer of the generated page, if appropriate
+
+Tue Jan 2 14:17:33 2001 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta (sanitize_line): make \ProgName and \Package accept
+ arguments in braces
+
+ * faq.sty: make \FTP, \File, \CTAN and \ProgName robust
+
+ * add-biblio.tex (section{Bibliographies}): lists of authors question
+
+ * additions.tex: pl2.7, today
+
+ * add-general.tex (section{Proposed new questions}): new question on mp
+ prologues
+
+Mon Jan 1 17:15:11 2001 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * texfaq2html-beta: normalise tabbing in perl code
+
+Sat Dec 30 16:35:47 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex: v2.5.1c, today
+
+ * additions.tex: pl2.6, today
+
+ * add-biblio.tex (section{Bibliographies}): ctanrefs at end of bibs per
+ section question
+
+ * faqbody.tex (section{Why does it do that?}): add pointers to fancyvrb
+ and verbdef packages in the question on verbatim in arguments
+
+ * filectan.tex: add verbdef.sty
+
+ * add-general.tex (section{Proposed new questions}): bit more at end of
+ missing characters question
+
+Wed Dec 27 14:19:48 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): missing characters
+
+ * faq.sty: minor typo corrected
+
+Tue Dec 26 16:39:47 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faq.sty: compact the booklist and ctanrefs environments, and
+ compactify standard itemize and enumerate environments
+
+Sun Dec 24 10:26:08 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-errors.tex (section{The joy of TeX errors}): filling out the
+ answer (work vaguely started last evening, and will probably take the
+ whole holiday...)
+
+Fri Dec 22 17:25:04 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex: pl2.4, today
+
+ * faqbody.tex (section{Introduction}): added giuseppe bilotta and
+ michael dewey to list of helpers
+
+ * add-general.tex (section{Proposed new questions}): provided format
+ generation instructions for the babel new language question
+
+ * faqbody.tex (section{Acquiring the Software}): tidy list at end of
+ "installing" question
+ 2.5.1b, today
+
+Thu Dec 21 00:24:20 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): tiny adjustment to
+ punctuation of \edef question, and a bit of rewording of one of
+ michael's sentences
+
+Wed Dec 20 16:56:43 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-general.tex (section{Proposed new questions}): new question
+ on \protected@[ex]def using some nice words of mjd's
+
+Tue Dec 19 10:00:41 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * Makefile (PATCH): add add-general
+
+ * additions.tex: replace body by \input of add-general
+
+ * add-general.tex: was body of additions.tex
+
+ * archive.list: correct list
+
+ * texfaq2html-beta: add code to deal with ctanrefs environment
+ (involves extra stuff in \item[...])
+ change default to cam.ctan.org
+
+ * Makefile (PATCH): add add-biblio.tex
+ add newfaq.aux as label parallel to newfaq.dvi; this satisfies a
+ dependency in the web and web-beta rules
+
+ * additions.tex: pl2.2, today
+
+ * faq.sty: define ctanrefs environment
+
+ * add-biblio.tex (section{Bibliographies}): fill out multiple
+ bibliographies question, introduce new ctanrefs environment for the
+ places to pull stuff from
+
+Mon Dec 18 11:42:43 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: added extsizes
+
+ * additions.tex (section{Proposed new questions}): extsizes question
+
+ * faqbody.tex: v2.5.1a, today
+
+ * texfaq2html (sanitize_line): as -beta version
+
+ * texfaq2html-beta (sanitize_line): add a couple of instances of
+ \cmdinvoke translation (cf comments on what's available in faq.sty)
+
+ * faq.sty: added \cmdinvoke
+
+ * faqbody.tex (section{Why does it do that?}): add reference to
+ textcase in the case-changing question
+
+ * dirctan.tex: add carlisle
+
+Fri Dec 15 16:41:49 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-biblio.tex (section{Bibliographies}): New file, some biblio
+ questions (mostly somewhat fragmentary), in a section of their own...
+
+ * dirctan.tex: added cite (the arseneau stuff) and bibunits ... and
+ multibib and bibtopic
+
+ * additions.tex: pl2.0, today; \input add-biblio
+
+Thu Dec 14 13:30:36 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: change url referring to archive (twice)
+ v2.5.1
+
+ * add-errors.tex (section{The joy of TeX errors}): it's isn't a
+ possessive!!!!!!
+
+ * texfaq2html: add provision for dealing with \symbol commands, tidy up
+ the url for the whole faq for the bottom of each message, and add "not
+ a help address" after email address
+ synchronise with texfaq2html-beta (incl adding title-modifier stuff)
+
+ * Makefile: add targets inst-perl and inst-perl-beta
+
+ * faqbody.tex (section{Things are Going Wrong...}): add reference to
+ new version of miktex's latex.zip
+ v2.5 (!)
+
+ * filectan.tex: added miktex 1.20 latex.zip
+
+ * faqbody.tex (throughout): htmlonly env -> htmlversion (oops!)
+ v2.4.8d, today
+
+Tue Dec 12 22:19:19 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): couple of tidies in
+ question on using quote site index; add new question on web searching
+ (section{Acquiring the Software}): remove outline of the web search
+ facility from question on repositories, and make reference to both
+ searching questions in place of partial duplication and reference to
+ one
+ 2.4.8c, today
+
+Mon Dec 11 11:07:56 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Support Packages for TeX}): add the wordcount
+ question
+ (section{Special sorts of typesetting}): add the watermarks question
+ (section{Acquiring the Software}): hacked the commercial stuff out of
+ the CDs question, and corrected the 4alltex bit to refer to windoze
+ rather than ms-dog
+
+ * add-errors.tex (section{The joy of TeX errors}): new section title,
+ and a couple of new questions (no room for a new..., and what to do
+ when epsf produces that diagnostic)
+
+ * faqbody.tex: 2.4.8b, today
+ (section{Special sorts of typesetting}): moved the script fonts
+ question from additions
+ (section{Why does it do that?}): replaced question about pictex and
+ register usage with improved one from additions
+
+ * additions.tex (section{Proposed new questions}): big hack on the
+ script fonts question, including lots of source references and
+ reference to the new scriptfonts thing; then moved question to faqbody
+ removed pictex, watermarks and wordcount questions
+
+ * filectan.tex: add eucal and mathscript
+
+ * dirctan.tex: add rsfs-type1 and jknappen-macros
+
+ * additions.tex (section{Proposed new questions}): change title of
+ pictex question
+
+ * Makefile (newfaq-patch): typo in yesterday's update
+
+Mon Dec 11 00:02:15 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): Tidied up Babel
+ question; still to complete the section on building a format at the
+ end (don't understand that at all -- does texconfig exist for other
+ than tetex systems, for example?
+
+Sun Dec 10 17:35:09 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * Makefile: replace all use of latexmk with the while-loop/get cross
+ construct
+
+ * additions.tex (section{Proposed new questions}): remove question
+ that's gone to faqbody
+ pl1.14, today
+
+ * faqbody.tex (section{Documentation and Help}): add question on
+ writing latex classes and packages
+ 2.4.8a, today
+
+ * filectan.tex: add latex-source
+
+Sat Dec 9 21:24:54 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): remove question
+ about conditional compilation
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): replace
+ question about excluding sections of a document with one about
+ "conditional compilation"
+
+ * additions.tex (section{Proposed new questions}): remove miktex
+ question
+ (section{Proposed new questions}): touch up pictex question with words
+ from existing one (mentioning the contex module that the yesterday's
+ effort omitted)
+
+ * faqbody.tex (section{Things are Going Wrong...}): add miktex question
+ (slightly reworded)
+
+ * additions.tex: pl1.13, today
+ (section{Proposed new questions}): junk question on recognising new
+ package files, since we've now integrated all the matter on these
+ ideas into two questions that have gone to faqbody
+ (section{Proposed new questions}): wrap code in script fonts question
+ so's not to overrun the verbatim margins
+
+ * faqbody.tex: v2.4.8, today
+
+ * additions.tex (section{Proposed new questions}): Remove the first two
+ questions to faqbody.tex
+
+ * faqbody.tex (section{Acquiring the Software}): Two new questions
+ lifted from additions.tex
+
+Fri Dec 8 09:51:42 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * add-errors.tex,additions.tex (throughout): normalised \Question cmds
+
+ * faqbody.tex: (throughout) TeX-systems (as Qref label) -> Q-TeXsystems
+ v2.4.7q, today
+ (throughout): normalise all \Question commands to have optional
+ argument [Q-<alpha string>]
+
+ * additions.tex (section{Proposed new questions}): question about the
+ miktex-latex problem
+ pl1.12, today (happy birthday Ma)
+
+ * faqbody.tex (section{PostScript and TeX}): removed comment at end of
+ type 1 fonts question (no date/time or version change this time)
+
+Tue Dec 5 10:22:48 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): label on the pictex
+ manual question (and remove old commented-out text about the
+ arrangement that used to exist for getting it from tug)
+ v2.4.7p, today
+ (section{Introduction}): add dick nickalls to list of helpers
+
+ * additions.tex (section{Proposed new questions}): added version.sty
+ and verbatim.sty to yesterday's question on conditional compilation
+ input add-errors at end
+ pl1.11, today
+
+ * filectan.tex: add version.sty
+
+ * add-errors.tex: errors section from additions.tex
+
+Mon Dec 4 13:23:04 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): question on
+ conditional compilation, from a c.t.t answer by donald arseneau
+ patch level 1.10, today
+ bunch of \Qref commands tidied not to produce "see" twice in the
+ printed output
+
+ * filectan.tex: remove comment (it's in a directory of its own, now)
+ add askinclude
+
+ * dirctan.tex: add pagesel (contrib/supported/oberdiek, in fact)
+ add comment
+
+ * filectan.tex: add selectp.sty
+
+ * faqbody.tex (section{Why does it do that?}): add label to \include
+ question
+ 2.4.7o, today
+
+Mon Nov 20 13:21:01 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): avoid column
+ overruns in verbatim `meta' sections in "where to put files"
+
+Tue Nov 14 13:23:57 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): tidied up
+ "installing a new package question
+ pl1.8, today
+ (section{Proposed new questions}): question on where to put files ...
+ very much in prototype stage just now (all in verbatim)
+
+ * faqbody.tex (section{Current TeX Projects}): add subscription info
+ for the pdftex list
+ v2.4.7n, today
+
+Tue Nov 7 11:23:44 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and TeX}): txfonts now have t1 and ts
+ encodings
+
+Wed Nov 1 12:24:01 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): added anthony goreham to
+ the list of helpers
+
+ * additions.tex (section{Proposed new questions}): added a thing
+ on formal scripts from anthony goreham
+
+Tue Oct 31 10:00:51 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: expunged all reference to gopher
+
+ * faqbody.tex (section{TeX Systems}): do away with reference to ctan
+ copy of 4alltex
+
+ * filectan.tex: corrected a bunch found by the script
+
+ * check-ctan-lists: new, jiffy checking script for (dir|file)ctan.tex
+
+Mon Oct 30 23:46:55 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): Add a question on LaTeX2e
+ v 2.4.7m, today
+
+Sat Oct 28 14:56:43 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): reference to
+ chngpage in question about changing margins
+
+ * filectan.tex: add chngpage; correct entry for comment.sty
+
+ * additions.tex (section{The joy of TeX error messages}): typo in
+ setting { (nb -- \symbol still not yet in texfaq2html)
+
+ * filectan.tex: added pdftex-oztex
+
+ * faq.sty: double accent for doing han the thanh `properly'
+
+ * faqbody.tex: v2.4.7l, today
+ (section{Current TeX Projects}): remove question on latex2e; move small
+ amount of matter from it into updated question on latex3; tidy and
+ update questions on omega, nts and pdftex
+
+Thu Oct 26 09:57:20 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: add txfonts
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): made a Ghostscript
+ reference uniform with rest (i.e., capitalised)
+ (section{PostScript and TeX}): details of the txfonts
+ v 2.4.7k, today
+
+Thu Oct 12 13:04:51 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: dvi2tty -> nonfree
+
+ * additions.tex (section{The joy of TeX error messages}): new question
+ about `extra }' (moving fragile command)
+
+ * Makefile: made web target a modified copy of web-beta
+
+ * filectan.tex: commented out fullpage
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): remove
+ reference to fullpage.sty, add geometry (by, that dates it); put a
+ label on footnotes in latex section headings
+ version 2.4.7j, today
+
+ * dirctan.tex: added geometry
+
+Mon Oct 9 12:30:34 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex (section{The joy of TeX error messages}): new section;
+ first two questions are general advice, and semantic nest
+
+Tue Sep 26 12:05:29 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faq.sty: repeated and undefined CTAN label warnings NoLine; repeated
+ CTAN labels counted and re-warned \AtEndDocument (as undefined labels
+ have been for some time)
+
+ * filectan.tex: abstract->abstract-bst
+
+ * faqbody.tex (section{Things are Going Wrong...}): in the bibtex
+ question, abstract->abstract-bst
+ 2.4.7h1, today
+
+ * additions.tex (section{Proposed new questions}): wordcount question;
+ pl5, today
+
+ * dirctan.tex: added wordcount
+
+Wed Sep 20 10:43:17 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): added a question
+ about one float per float page; pl4, today
+
+ * faqbody.tex (section{Things are Going Wrong...}): add Q-floats label
+ to moving tables and figures question
+
+Fri Sep 15 11:42:25 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Current \TeX{} Projects}): tidy up references to
+ omega implementations
+
+Thu Sep 14 10:27:00 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html-beta: title to contain beta indicator
+
+ * faqbody.tex (section{PostScript and \TeX{}}): added remaining
+ micropress font sample urls
+
+ * texfaq2html-beta: new file; runs beta sources
+ added question number to title if exactly one question requested
+
+ * faqbody.tex: 2.4.7h, today
+ (section{Documentation and Help}): removed frivolity about rtfm in
+ `where to get help' (at Manuel Gutierrez' suggestion)
+
+ * additions.tex (section{Proposed new questions}): add note of
+ confirmation of the sequence for refreshing the fndb under miktex
+
+Tue Sep 12 23:20:53 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): sound depressed about
+ deja
+ (preamble): today, v2.4.7g
+
+Sun Sep 10 10:22:45 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): upgrade of the
+ unnumbered sections question (from peter wilson), and of the 1-column
+ abstract question (from same source)
+
+ * dirctan.tex: added tocvsec2, tocbibind, abstract
+
+Sat Sep 9 14:15:21 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and TeX}): bunch of new stuff from
+ berthold and mike updating the section on scalable outline fonts
+ (section{Documentation and Help}): add a first reference to teencontrex
+ (section{Acquiring the Software}): correct address for the ctan list in
+ `contributing to the archives'
+
+ * dirctan.tex: added hvmath, tmmath and teencontrex
+
+ * faq.sty: make the tex logo robust
+
+Fri Sep 8 17:55:13 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: redid reference to c++2latex
+
+ * faqbody.tex (section{Documentation and Help}): correct a \dots
+ invocation in "where to get help"; recommend ctan search web address
+ rather than the catalogue direct
+ (section{How do I do X in TeX or LaTeX}): added reference to c++2latex
+ for typesetting code, at the suggestion of Michael Soulier
+
+Tue Aug 22 14:39:09 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): slight tidying
+ of matter in question about dashed integrals
+
+Sun Aug 20 17:27:55 2000 Robin Fairbairns <rf@gordon.cl.cam.ac.uk>
+
+ * dirctan.tex: added vmargin (now in supported)
+
+ * filectan.tex: removed vmargin
+
+Mon Jul 24 09:26:41 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * dirctan.tex: add ams-AMStype1
+
+ * faqbody.tex: v 2.4.7f, today
+ (section{PostScript and \TeX{}}): more work on the fonts stuff
+
+Sat Jul 22 10:24:05 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): add donald's
+ "typesetting principal value integral"
+ v2.4.7d, today
+ (section{Introduction}): removed email address for bodenheimer, which
+ hasn't (afaik) worked for some time
+
+Fri Jul 21 17:46:09 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and TeX}): berthold's stuff on
+ outline fonts (mike's is harder work ;-)
+ v 2.4.7c, today
+
+ * dirctan.tex: add cm-AMStype1
+
+Wed Jul 19 10:18:36 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): add \arrowhyph
+
+ * faq.sty: added \arrowhyph
+
+ * additions.tex (section{Proposed new questions}): moved Peter Wilson's
+ one on getting a new package
+
+ * faqbody.tex: v2.4.7b, today
+ (section{Special sorts of typesetting}): correct address for mutex
+
+Mon Jul 10 15:07:48 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * dirctan.tex: explicit location for tds (will presumably never now be
+ version 1.0 ...
+
+ * faqbody.tex (section{Support Packages for \TeX{}}): removed vortex
+ (section{Bits and pieces of \TeX{}}): add pw's on the tds
+
+Fri Jul 7 12:26:22 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): make \begin|\end{htmlversion} ignore
+ entire line
+
+ * faqbody.tex (section{Documentation and Help}): new question on \MF
+ and \MP tutorials (pw again)
+ v2.4.7a, today
+
+ * filectan.tex: added metafp.(ps|pdf)
+
+ * faqbody.tex (section{The Background}): pw's revision to mp answer
+ (section{Documentation and Help}): couple of additions to booklists
+ (section{Documentation and Help}): pw's major addition to mail list
+ stuff
+
+ * texfaq2html (sanitize_line): add \PDFLaTeX
+
+ * faq.sty: add \PDFLaTeX
+
+Sat Jul 1 13:12:00 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): added peter wilson to list of
+ acknowledgements
+ (section{Documentation and Help}): the first of peter wilson's new
+ answers -- books on type
+
+Fri Jun 23 12:26:31 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): give locations for
+ ctan servers, and correct www address for tug box search script
+
+Wed Jun 21 13:41:17 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): ignore \keywords argument
+
+ * faq.sty: add \keywords command (ignores argument, carefully)
+
+ * faqbody.tex (section{Why does it do that?}): question on renaming
+ fixed texts in the context of babel (has \keywords)
+
+Tue Jun 20 14:03:38 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): acknowledge alan jeffrey's
+ design of the html version, and record use of dante material
+
+ * dirctan.tex: add pictex-addon
+
+ * filectan.tex: add context-tmf, delete doublespace
+
+ * faqbody.tex (section{Why does it do that?}): question on pictex and
+ registers, largely lifted (with help from babelfish) from dante's faq
+
+Wed Jun 14 11:36:29 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): caveat for non-ia32 versions
+ of miktex, mention the psu.edu mac-tex page
+
+Tue Jun 13 10:27:09 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): updated details for gutenberg
+
+Wed Jun 7 12:33:02 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex: version 2.4.5, today (for release)
+ (section{Acquiring the Software}): missing \endhtmlignore in nonfree
+ tree question
+
+Thu Jun 1 16:41:28 2000 Robin Fairbairns <rf@pallas.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Things are Going Wrong}): rewritten question
+ about capacity exceeded (scrapping assertions about pure methods of
+ hacking the tex web source, for goodness' sake!)
+
+Fri May 5 12:44:05 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * filectan.tex: add reference to epslatex.ps
+
+ * faqbody.tex (section{PostScript and TeX}): add reference to
+ epslatex.ps in question on graphics inclusion where previously only
+ the pdf was mentioned
+
+Wed Apr 26 11:17:34 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): remove reference to
+ (now defunct) bitftp@pucc.bitnet
+ (section{Acquiring the Software}): add ctan.tug.org ftpmail
+ (section{Acquiring the Software}): hacking at search info (more to do)
+ (section{The Background}): update uk tug details
+ (throughout): remove parentheses from (+countrycode)
+
+ * faq.sty: another iteration of pdfstartview
+
+Tue Apr 25 15:30:52 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faq.sty: tried alternative pdfstartview value -- no joy
+
+Fri Apr 14 15:20:33 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * filectan.tex: add latex-classes, ltxguide
+
+Wed Apr 12 15:01:42 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: v2.4.2, today
+
+ * Makefile: add targets help, patch (==newfaq-patch) and web (==march)
+
+ * dirctan.tex: remove gtex; stick a whole lot of obsolete/ prefixes in
+ dviware things (that are probably not, in all honesty, ever going to
+ be used again, but what the hell...)
+
+ * faqbody.tex (section{DVI Drivers and Previewers}): remove all the
+ previewers that have been moved to obsolete/, rewrite the rest
+ mentioning miktex and fptex previewers, characterise emtex's thing as
+ dos+os/2 only, etc., etc.
+ (section{\TeX{} Systems}): remove references to gtex
+ (section{Special sorts of typesetting}): remove references to gtex
+
+Wed Apr 12 07:44 rf@huntingdon (using vi)
+
+ * companion.ctan: update location of version.sty
+
+Thu Apr 6 18:52:52 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): correct spelling of
+ bernice in sacks lipkin's name (oops) :-(
+
+Wed Apr 5 10:22:21 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and \TeX{}}): rewrite figure
+ inclusion with emphasis on the graphics package
+
+ * dirctan.tex: add draftcopy and ms
+
+ * additions.tex (section{Proposed new questions}): Add watermarks q
+
+Mon Apr 3 21:25:19 2000 Robin Fairbairns <rf@betsy.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): tidy up gratzer's
+ latest (which _has_ been published now, or else...) and add reference
+ to lipkin's latex for linux
+
+Fri Mar 31 14:40:29 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: v2.4, today
+
+ * additions.tex: bunch of questions moved out; back to pl 1 (only
+ unfinished `new language in babel' question now left)
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): moved in 1-col
+ abstract, babel words and code listings questions
+ (section{Acquiring the Software}): moved in `nonfree' question
+ (section{Format conversions}): moved in `read SGML/XML direct' question
+ (section{Why does it \emph{do} that?}): moved in \marginpar question
+
+2000-03-27 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * newfaq-patch.tex: input faqbody for version and date before additions
+
+ * additions.tex: make version reported derive from \fileversion from
+ faqbody
+
+ * faqbody.tex (section{\TeX{} Systems}): removed listing for microtex
+ v2.3a2, today
+
+2000-03-24 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): correct details for truetex
+
+ * faq.sty: define a url in pdf mode for the debian social contract,
+ _before_ loading hyperref; remove all the old (pre-url.sty)
+ definitions using the FAQverb mechanism; remove the attempts at
+ patching hyperref's normalisation mechanisms
+
+ * additions.tex (section{Proposed new questions}): use defined url for
+ debian social contract address (to bypass hyperref boondoggle)
+
+Fri Mar 17 15:30:56 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * additions.tex (section{Proposed new questions}): Completed new
+ questions added yesterday (but not, I see, documented) -- on listings
+ and \marginpar
+
+ * dirctan.tex: add listings, tiny_c2l
+
+Thu Mar 16 10:01:02 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): \URL argument in braces now
+ (sanitize_line): $e$ generalised to $<anything>$ (for $n$, just now)
+
+Thu Mar 2 14:27:03 2000 Robin Fairbairns <rf@huntingdon.cl.cam.ac.uk>
+
+ * dirctan.tex: added mparhack
+
+Thu Feb 10 16:55:44 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: add passivetex
+
+ * faq.sty: \URL is _just_ \url now
+
+ * additions.tex: v2.3a1 pl4, today
+ (throughout): convert all \URL commands to take arguments in braces
+ (section{Proposed new questions}): passivetex ctan reference now
+ only one version of reference to social contract
+
+ * faqbody.tex (throughout): convert all \URL commands to take arguments
+ in braces
+ v2.3a1, today
+
+Fri Jan 21 14:09:59 2000 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: added xmltex
+
+ * additions.tex (section{Proposed new questions}): added spqr's
+ question about typesetting *ml direct with tex;
+ 2.3a pl3, today
+
+Tue Dec 14 10:28:00 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faq.sty: attempted improvement of \ifpdf definition of \URL (trying
+ to use hyperref's sanitising facilities)
+
+ * additions.tex (section{Proposed new questions}): outlines for babel
+ hyphenation, babel `foreign words'
+ (section{Proposed new questions}): wrap verbatim lines a bit
+
+ * texfaq2html (sanitize_line): add \meta
+
+ * faq.sty: add \meta command
+
+Fri Dec 3 09:34:24 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile (newfaq-patch): new target (with ancillaries) to make pdf
+ and ps versions of the patched file
+
+ * letterfaq.tex: bring into line with newfaq (was rather wonky)
+
+ * additions.tex: new file -- proposed additions to faqbody
+
+ * newfaq-patch.tex: new file -- newfaq, with the additions
+
+ * newfaq.tex: eliminate reference to bodenheimer in the title, mention
+ the march 1999 printed issue
+
+Mon Nov 1 17:50:07 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * texfaq2html (tail): add href to default address for script using `TeX
+ FAQ' as anchor
+
+Mon Sep 6 13:25:08 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): removed phil taylor from list of
+ non-committee-members
+
+Thu Sep 2 14:11:02 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: today's date, v2.3a
+
+ * Makefile: add configuration variable CMFONTS(=cmz), and use it where
+ previously just said -Pcms
+
+ * filectan.tex: added simpl-latex
+
+ * faqbody.tex (section{PostScript and \TeX{}}): correct ref to mathpple
+ (section{Documentation and Help}): add ref to harvey greenbergs
+ simplified latex thing
+
+ * faq.sty: defer \let\Qlabel\label to begin document in case that we're
+ using hyperref
+
+Wed Sep 1 09:11:00 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faq.sty: don't have \raggedright explicit in the definition of
+ \Question -- hyperref chokes, now -- redefine \subsection instead
+
+ * faqbody.tex (section{PostScript and \TeX{}}): change description of
+ authorship of mathpple
+
+ * filectan.tex: remove mathpple (dangling pointer into tetex)
+
+ * dirctan.tex: add mathpple (fonts/mathpple)
+
+Mon Jul 26 14:34:46 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): change wording around binary
+ availability for tetex
+ v2.3 (3.0 for the published version?), today
+
+ * dirctan.tex: tetex binaries from distrib/binaries directory (change
+ label to tetex-bin from -install)
+
+Sat Jul 24 08:50:15 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): retrieved text about
+ ghostscript caoability of viewing acrobat docs
+ (section{The Background}): minor typo in lollipop
+
+Fri Jul 23 21:19:39 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): missing \\ in details for sci
+ word
+ (section{\TeX{} Systems}): updated with words from mike vulis about
+ vtex
+ (section{Format conversions}): add references to vtex & tidy a bit more
+
+ * dirctan.tex: add vtex (and delete vtex-demo, ancient)
+
+Tue Jul 13 09:31:14 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Support Packages for \TeX{}}): change reference
+ to ispell to reflect browsing status
+ (section{Format conversions}): tidy the question on generating acrobat,
+ add url for getting acroread
+ (section{Acquiring the Software}): canonical ctan.org addresses for
+ everything, remove numeric addresses (most of which were wrong anyway)
+
+ * dirctan.tex: make ispell directory browsable, and remove all
+ subdirectory references
+
+ * filectan.tex: update version number for excalibur
+
+Sun Jul 4 00:01:06 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): rewrote the section about
+ pdf output, including (inter alia) dvipdfm, and dropping reference to
+ dvipdf
+ (throughout): GhostScript->Ghostscript
+
+ * dirctan.tex: add dvipdfm
+
+ * faqbody.tex (section{Current \TeX{} Projects}): make NTS logo come
+ out bold in question title (using \afterquestion); use \afterquestion
+ for question about 2e
+ (section{The Background}): use \afterquestion (twice) in re. instances
+ of bold math characters in titles
+
+Sat Jul 3 10:02:22 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faq.sty: add \afterquestion command for use after \Question commands
+ inside groups
+
+ * faqbody.tex (section{How do I do X in \TeX{} or \LaTeX{}}): refer to
+ sectsty, titlesec and fncychap as alternatives for changing section
+ headings
+ remove reference to NFSS question in roman theorems question
+
+ * dirctan.tex: add sectsty, titlesec, fncychap
+
+ * faqbody.tex (section{Current \TeX{} Projects}): section renamed from
+ `recent developments'
+ commented-out the nfss question (hardly current any more)
+ rewritten latex question to refer to june 1999, and to stand alone re
+ nfss issue
+ (section{Things are Going Wrong\dots{}}): get rid of references to the
+ NFSS question
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): no question
+ reference for NFSS in section headings question
+
+ * dirctan.tex: add context
+
+ * faqbody.tex (section{The Background}): Add a question about context
+ (section{The Background}): junk the commented-out stuff about AMS
+ things we no longer admit to...
+ version 2.2t, today
+
+ * texfaq2html (sanitize_line): add \CONTeXT (and \PDFTeX, \NTS, \eTeX,
+ \Eplain, \TeXsis and \WYSIWYG ... oops)
+
+ * faq.sty: add \CONTeXT
+
+Mon Jun 14 17:46:49 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+
+ * texfaq2html (sanitize_line): add \'e
+
+ * faqbody.tex (section{Documentation and Help}): add a proto-
+ question on tutorials
+
+ * filectan.tex: add gentle, lshort (both pointing at .pdf files) and
+ change epslatex to point at the .pdf file
+
+Sun Jun 13 14:01:10 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): rearranged list of committee
+ members to be more easily editable, and removed malcolm and kaveh's
+ names from the list of people said to have retired in 1998
+ (section{Macros for Particular Types of Documents}): questions about
+ setting papers for journals, and creating a report from a bunch of
+ articles
+ v2.2q, today
+
+ * dirctan.tex: add frankenstein
+
+Sat Jun 12 09:25:42 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}):
+ struggling to make sense of the twaddle about logos, in html...
+ (section{Documentation and Help}): retrieved the isbn for knuth's
+ hardback
+
+ * texfaq2html: define $home from $ENV{FAQ_HOME} if that exists
+
+ * faqbody.tex (section{Documentation and Help}): \ISBN commands for tip
+ separate volumes; add first stab at entry for knuth's collected papers
+ (missing hardback isbn just now)
+ (section{Macros for Particular types of Documents}): new section, only
+ containing vita.cls as yet
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): be a bit ruder
+ still about the silly-logo syndrome; mention the \MP problem and the
+ difficulties with texnames.sty
+ (section{The Background}): credit hobby in \MP question
+ v2.2p, today
+
+ * dirctan.tex: Add vita
+
+ * faq.sty: \MP == MetaPost in public version (P was lower case)
+ (matches what's in texfaq2html)
+
+Thu Jun 10 09:41:01 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): rewritten win32 part,
+ emphasising the info got from fabrice's talk at the uk tug meeting
+
+ * dirctan.tex: added lwc, lgc
+
+ * faqbody.tex (section{Documentation and Help}): commented out entry
+ for making tex work (no longer in ora catalogue), updated entry for
+ diller's organ, removed buerger's entry (no longer in mcgraw-hill
+ cat.) and shultis' (no longer in prentice hall cat.)
+ removed comment about what is/isn't good for latex2e, added reference
+ to lgc and lwc directories
+
+ * texfaq2html (sanitize_line): moved \acro up above \emph
+
+Wed Jun 9 17:49:34 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Added lwc
+ v2.2o, today
+
+Sat Jun 5 11:10:19 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile.CTAN (archive.cfg): needs distributing, too
+
+ * faq.sty: NoLine for package warning about missing refs at end
+ damn -- need distinguished \CTANdirectory* in pdf case
+
+ * faqbody.tex: v2.2n, today
+
+ * faq.sty: make \CTANdirectory ignore *
+
+ * faqbody.tex (section{\TeX{} Systems}): `browse' 2 tetex directories
+
+ * texfaq2html: add \CTANdirectory* capability, for browsing dirs
+
+ * dirctan.tex: added 0.4 into tetex and tetex-bin, convert all tetex
+ entries to *-form
+
+Tue May 25 14:52:12 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): corrections to sciword stuff
+ 2.2m, today
+
+Mon May 24 14:29:21 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Updated sciword, etc., bumf
+ 2.2l, today
+
+Fri May 14 12:17:37 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): restore yesterday's change...
+
+Thu May 13 10:02:58 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): make the html redirect for
+ miktex go to the 1.20 directory, since miktex/index.html has gone :-(
+
+Fri May 7 10:05:15 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: correct directory address of fptex (!)
+
+ * Makefile.CTAN: add texfaq2html
+
+ * faqbody.tex: change date to today
+ (section{\TeX{} Systems}): different references for miktex as
+ between the printed and web versions (ouch...)
+ (section{\TeX{} Systems}): remove commented-out text about getting
+ oztex on floppies...
+
+ * dirctan.tex: add systems/win32/miktex
+
+ * filectan.tex: removed the three miktex file entries
+
+ * texfaq2html: add mail url for uktug-faq@tex.ac.uk in the tail
+
+Thu May 6 14:18:26 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): Add reference to
+ ISO 690-2 online version in question about citing urls
+ v2.2j, today
+
+Fri Apr 23 11:45:35 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile.march: new, update the things needed for the texfaq script,
+ _only_
+
+ * Makefile: add new target march to run Makefile.march in
+ VH-tex/faq-source
+
+ * faqbody.tex (section{The Background}): new url for uk tug
+ (section{Introduction}): change url for the faq to cambridge, remove
+ footnote about it being a temporary one
+
+ * texfaq2html: remove the `brought to you at' mucking about; change
+ $home; change web address for uktug
+
+Thu Apr 22 15:37:13 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Update details on K&D
+ to third edition
+
+Sat Apr 17 16:16:10 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * texfaq2html: /usr/bin/perl (so as to work both on bescot and march)
+
+Wed Apr 7 14:10:47 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * newfaq.workers: stupid file ... should i keep it?
+
+ * Makefile.CTAN: add newfaq.ps (eh?!)
+
+ * faqbody.tex (section{Documentation and Help}): kerfoodle to produce
+ the string /caption\\. as in-line verbatim in html
+ version 2.2g, today
+
+Sat Apr 3 08:57:10 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile.CTAN: (new file) first stab at automating installation on
+ CTAN
+
+ * Makefile.FTP: remove .dvi and .ps files from this distribution
+
+ * Makefile: add symbols DVIPS, PDFLATEX and LATEX (which last rather
+ useless at present
+
+ * faqbody.tex: today's date
+ (section{\acro{DVI} Drivers and Previewers}): remove reference to the
+ separately-available VMS version of dvips
+
+ * dirctan.tex: add tetex-beta
+
+ * faqbody.tex (section{\TeX{} Systems}): correct VMS entry
+ (section{Perhaps There \emph{isn't} an Answer}): sort screed about
+ consultants, and add pointer to TUG consultants page; correct
+ reference to latex project
+ (section{Recent Developments}): revise the text about the latex3
+ project; add reference to cyrillic in the latex2e stuff, and otherwise
+ revise _that_ text; refer to packaged systems that include omega
+ (section{\TeX{} Systems}): urge packaged systems for unix, and refer to
+ tetex-beta
+
+ * filectan.tex: remove all the old VMS references and add OpenVMSTeX
+
+Fri Apr 2 14:53:15 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): reword fptex stuff, and change
+ label
+ (throughout): ensure that _all_ em-dashes are preceded by nobreakspace
+ and use \LaTeXo in place of spelling out the old version number (for
+ consistency of layout)
+
+ * dirctan.tex: deal with latex packages directory (and delete the
+ `whole directory' label which wasn't used)
+ win32/web2c -> fptex
+
+Tue Mar 16 00:03:15 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): minor editorials on the Y2K
+ question
+
+Sun Mar 14 09:29:54 1999 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): Add a question on Y2K
+ compliance (and give a \Qref to the outline of LaTeX)
+ (section{The Background}): Add a section on trip/trap
+ version 2.2e, dated today
+ (section{Introduction}): Add John Palmer to the footnote about the
+ committee
+ (section{Documentation and Help}): add isbn for mfbook paperback
+ (section{Documentation and Help}): mention wichura under the pictex
+ manual, and add reference to pti's web site (without mentioning the
+ price they charge for the damned manual!!!!!)
+ (section{Acquiring the Software}): remove information (which is surely
+ out of date) about the `next' (late 1997) release of 4alltex disc --
+ no replacement since the situation isn't clear to me...
+ (section{Format conversions}): remove reference to jf's stuff (which
+ seems to have been abandoned in favour of activetex)
+
+Sat Nov 14 12:45:16 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * filectan.tex: add a winedt entry
+
+ * faqbody.tex (section{Introduction}): changes to lists of names
+ (section{\TeX{} Systems}): add a little thing about winedt (probably
+ not satisfactory)
+
+ * filectan.tex: three separate miktex files
+
+ * dirctan.tex: miktex (pc) _goes_
+
+ * faqbody.tex (section{Format conversions}): correct info about the
+ word processor conversions faq
+ (section{The Background}): remove reference to .zip file of texinfo
+
+ * filectan.tex: texcnven no longer exists -- record the .zip file in
+ the directory; update the texinfo file name (removing the version
+ number and thereby relying on the link) and get rid of the .zip
+ reference (did such a file _ever_ exist?)
+
+Tue Aug 25 13:51:52 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): New version of tech wg stuff
+ from kaja christiansen
+
+Thu Jun 11 17:10:37 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile (CONFIGS): new, another category of thing to depend on
+
+Wed Jun 10 12:58:02 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Bits and pieces of \TeX}): minor rewording of
+ text about ec fonts, correction of punctuation
+
+Tue Jun 9 20:40:05 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * dirctan.tex: start suppressing unused directories
+
+ * faq.sty: make \CTAN{directory,file} deal with case of active file or
+ directory name
+
+ * faqbody.tex (section{Special sorts of typesetting}): make direct
+ reference to suppport/xindy into a \CTANref; minor typos corrected
+
+ * archive.cfg: new file, configuration for {file,dir}ctan when make pdf
+
+Tue Jun 9 00:11:09 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faq.sty: distinguish two \Status targets, 1- and 2-column pdf (values
+ 1 and 2)
+
+ * faq.cls: load packages before setting page dimens, don't change
+ horizontal dimens if single column version
+
+ * faqbody.tex (section{Format conversions}): dvipdf lesenko spoke about
+ it in the past (was `hoping to speak' at tug'97); today's date; slight
+ rewording of basic outline of omega
+
+Mon Jun 8 17:21:15 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faq.sty: yet another fiddle with hyperref options; suppress multicol
+ when doing pdf
+
+Sun Jun 7 09:25:05 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Remove reference to
+ getting the old faq by ftpmail; increment patch number, date today
+
+ * faq.sty: juggle with hyperref package options; remove spurious space
+ in `public' definition of \MF
+
+ * Makefile: do pdf generation on the basis of pdf-{new,letter}faq.tex
+
+Sat Jun 6 00:59:02 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faq.cls: also require url.sty, since we again have a conflict with
+ hyperref
+
+ * faqbody.tex (section{\TeX{} Systems}): remove claim that tug can
+ supply pc software or copies of oztex (and restructure the mac
+ question slightly as a result); refer to omega port in cmactex
+
+ * faq.sty: replace all alan's old url-ish definitions with ones based
+ on url.sty (this is too slow processing dirctan.tex...)
+
+ * Makefile: add new targets newfaq.pdf and letterfaq.pdf; parameterise
+ files we depend on; do away with old `all' target, and use body of
+ `public' one instead
+
+Fri Jun 5 20:23:09 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faq.cls: input multicol before faq, in case we're running pdflatex
+ (\Status=1) -- since hyperref changes \@footnotetext, and multicol
+ checks it, this is somewhat important...
+
+ * faqbody.tex (section{Documentation and Help}): reword the sorry tale
+ of the pictex manual (i.e., not available at all)
+
+Thu May 28 14:52:14 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): refer to
+ fancyvrb in `including verbatim files' and `line numbers'
+ v2.2a, today
+
+ * dirctan.tex: add fancyvrb
+
+Tue May 5 11:05:11 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile.FTP (all): removed non-cm .dvi files, .300ps files
+
+Mon May 4 21:56:52 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): tug2->ctan.tug.org
+ (section{Acquiring the Software}): tug2->ctan.tug.org
+
+ * faq.sty: add \Status game (cribbed from seb's work on tex-live doc)
+
+Sat May 2 17:49:11 1998 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): backing off bodenheimer, ref the
+ version on TeX Live CD
+ (section{Acquiring the Software}): tex-live now third edition
+ v2.2, today
+
+ * Makefile (public): new `general' target, with no .300ps stuff
+ (newfaq.ps,letterfaq.ps): remove specification of elm
+
+ * faq.sty: junk the old diddling with parameters for times (there've
+ been several new releases of the metrics since those were recommended)
+ define \ifpublicversion, talking of the fonts to be used, so we can
+ have a type1-fonts-only version
+
+Fri May 1 17:55:49 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: 2.1o, today
+
+ * dirctan.tex: add footmisc
+
+ * filectan.tex: remove stblftnt
+
+ * faqbody.tex (section{How do I do X in \TeX or \LaTeX}): refer to
+ footmisc rather than stblftnt
+
+Mon Apr 6 12:56:20 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile (clean): add -f switch
+
+ * faqbody.tex (section{\TeX{} Systems}): refer to pctex32 (as a windows
+ implementation)
+ version 2.1n, today's date (forgot that last time)
+
+Thu Mar 26 16:51:01 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): redo the examples
+ for #-doubling in terms of + rather than -, so no need for farting
+ around with ligatures
+ (section{Introduction}): removed jf from list of resigned committee
+ members, added dpc, and brought committee list up to date
+
+Wed Mar 18 10:19:55 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * companion.ctan: correct calc, changebar
+
+Fri Jan 16 09:58:18 1998 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: v2.1m, today
+ (section{The Background}): Correct address and phone nos for TUG
+
+Wed Nov 5 10:40:40 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): minor typo in
+ line numbering q
+
+Tue Nov 4 11:03:45 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): Avoid nested
+ braces in indexing question
+ (section{Introduction}): Refer to LaTeX2e rather than LaTeXe in intro
+ (html version only)
+
+ * faq.sty: Define \oparen and \cparen commands
+
+
+Wed Oct 29 16:33:41 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Update truetex web page
+ address (and source details)
+
+Mon Oct 27 09:20:15 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faq.sty: Comment about oddity of \CTAN command
+
+ * faqbody.tex (section{Things are Going Wrong\dots{}}): Tidy up earlier
+ text (difficult to quote entire trivial lines, in-line)
+
+Sat Oct 25 23:37:11 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): \CTAN takes
+ a real argument, not one in vertical bars
+
+ * faq.sty: Add \TeXsis, \parens
+
+Sat Oct 25 10:52:42 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex: today's date
+ (section{Special sorts of typesetting}): Add questions on typesetting
+ URLs, and on citing them with BibTeX; reference texsis's indexing
+ macros, and mention xindy (not terribly satisfactorily, given the way
+ it's organised on CTAN)
+
+ * dirctan.tex: Add xindy
+
+ * filectan.tex: Add texsis-index
+
+ * faq.sty: remove definition of \ifnotreadCTAN, define \htmlonly and
+ \textpercent
+
+ * texfaq2html (sanitize_line): Add \htmlonly (as no-op), \\textpercent
+ rather than \\\% (!)
+
+ * filectan.tex,dirctan.tex: Own protection against being read twice
+
+ * newfaq.tex,letterfaq.tex,faqbody.tex: Do away with conditional around
+ loading {dir,file}ctan
+
+Fri Oct 24 19:34:37 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): Add Oren Patashnik to list of
+ contributors (in anticipation...)
+ (section{Things are Going Wrong\dots{}}): Modify answer to offer Oren's
+ solution to the `BibTeX string too long' problem
+ Add a question about underlining
+ (top of file): v2.1l, today
+
+ * filectan.tex: Add ulem.sty, abstract.bst
+ Excalibur entry now .sit.hqx (also corrected version no)
+
+Thu Oct 23 08:09:37 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * filectan.tex: Add url.sty, update version number in the texinfo
+ distribution
+
+ * faqbody.tex (section{How do I do X in TeX or LaTeX}): Rewrite the
+ initial text in a slightly less school-ma'am-ish way
+
+Fri Oct 10 19:40:06 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): Add question on
+ line numbering
+
+ * dirctan.tex: Add lineno
+ Delete a bunch of entries that are wrong/irrelevant/misleading
+ (including all the latex209 ones that didn't get moved to latex
+ by Seb in his LGC campaign, apart from ones that might figure in
+ a future question, like chbars, chem{struct,tex})
+ Correct xymtex (to contrib/other), crossword (to contrib/other/
+ crosswrd), elsevier (to contrib/supported), footnpag (to contrib/
+ supported), ucthesis (to contrib/supported)
+ Replace epic with (macros/latex/contrib/other/)eepic
+
+ * filectan.tex: Add numline, latex209-base
+ Correct ukhyph
+
+Fri Oct 10 11:41:13 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Recent Developments}): Correct John Plaice's
+ email address
+
+Fri Oct 10 07:01:24 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): Process \mailto
+ Use $0 if environment SCRIPT_NAME isn't defined
+
+ * faq.sty: Define \mailto
+
+ * faqbody.tex (throughout): Convert \Email to \mailto for addresses
+ that should/could be mailable direct from the web instance of the FAQ
+ (section{\TeX{} Systems}): Note update date of pctex info
+
+Thu Oct 9 22:36:02 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Add a question on
+ the behaviour of \include; small extension of the question about \verb
+ to note other exciting error messages
+
+Wed Oct 8 16:38:52 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): ctan-web from tug2
+ rather from its old Oh Really site
+
+Wed Oct 8 00:26:29 1997 Robin Fairbairns <rf@betsy.al.cl.cam.ac.uk>
+
+ * texfaq2html: Upgraded for perl5 (heaven knows whether it now works
+ under perl4
+
+ * faqbody.tex (section{Documentation and Help}): Add a url for
+ ctindex.html in addition to the full thing
+
+Mon Sep 6 13:50:51 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): New email addresses for PTI
+
+Fri Sep 5 18:42:23 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): correct URL for WC
+ CDROM information
+
+Wed Aug 20 10:51:16 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): Add tug2.cs.umb.edu
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): Add Donald
+ Arseneau's note about \mathbf vs. AMSLaTeX
+ (section{Introduction}): Add Donald Arseneau to acknowledgements
+
+Wed Aug 13 11:27:55 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * Makefile (clean): Only delete .aux files cgi-bin script doesn't use
+
+ * dirctan.tex: amslatex from latex/packages, amstex from macros/amstex,
+ fontsel from latex209/amslatex/fontsel (oops); junk AMS author-info
+ and its guidelines
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Mentioned
+ changing the text, and \enlargethispage for split footnotes
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): Add a question
+ on bold greek letters
+
+Tue Aug 12 14:39:30 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Add question on
+ split footnotes
+ v 2.1f, today
+ (section{Introduction}): Add David Kastrup to list of acknowledgements
+
+Mon Aug 11 16:07:37 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): Quote a CPAN address for
+ SGMLS (was using a direct UOttawa address for dmeggins' directory)
+ 2.1e, today
+
+Tue Jul 22 12:37:17 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * archive.list: List of acceptable archives (just archive name and root
+ so far, but abbrevs and acceptable formats also possible)
+
+ * texfaq2html: Further work to make the archive list and archive
+ selection work
+ Make the selected archive and format hidden input from the search form
+
+Mon Jul 21 13:59:21 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * texfaq2html: Add format (or f) and archive (or a) keywords
+ Add link at end to UK TUG home page
+ Add archive_list variable
+
+ * archive.list: New file, list of allowable archives
+
+Thu Jul 10 11:26:42 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * texfaq2html (sanitize_line): Add translation of \thinspace{} to space
+
+ * faqbody.tex (section{\TeX{} Systems}): {} after \thinspace
+
+Tue Jul 8 09:48:20 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): remove reference
+ to doublespace.sty
+ v2.1d, today
+
+ * filectan.tex: threeparttable.sty is now a latex (rather than 209)
+ package
+ remove entry for alltt
+
+ * texfaq2html: correct (to non-opaque html) translation of \pounds
+
+ * faqbody.tex (section{\TeX{} Systems}): Refer to the win32 port of
+ Web2C, miktexppc and miktex-AXP, and the djgpp port of Web2C
+
+ * dirctan.tex: Directory name djgpp (an obscure pointer to something
+ deep in the ps2pk tree) subverted to point at systems/msdos/djgpp
+ Add win32-web2c, miktexppc and miktex-AXP
+
+Wed Jun 18 15:57:57 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex: v2.1c, today
+
+Wed Jun 18 00:17:56 1997 Robin Fairbairns (robin@sams-machine)
+
+* faqbody.tex (section{Acquiring the Software}): Rearranged (and somewhat
+ reworded) the CDROM question, at Sebastian's suggestion
+
+Tue Jun 17 23:03:43 1997 Robin Fairbairns (robin@sams-machine)
+
+* faqbody.tex (section{Recent Developments}): Typos in PDFTeX stuff, change
+ assertion to say it is postgrad research rather than originating in an MSc
+ project (as I thought but Sebastian didn't)
+(section{Perhaps There \emph{isn't} an Answer}): Make reference to TUG as
+ contact for TeX bugs a link
+
+Tue Jun 17 14:43:56 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): fancyheadings->
+ fancyhdr
+ (section{Format conversions}): Further iteration of the acrobat-
+ creation text
+ (section{Things are Going Wrong\dots{}}): fancyheadings->fancyhdr in
+ the first-page-empty thing...
+ (top of file) version 2.1b, today's date
+ (section{Acquiring the Software}): Correct \Qref in 4AllTeX text
+
+ * dirctan.tex: other/fancyheadings->supported/fancyhdr
+
+ * faq.sty: Added \PDFTeX
+
+Mon Jun 16 15:40:07 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: Added pdftex
+
+ * faqbody.tex (section{Introduction}): Add Mark to committee list,
+ change URL to www.tex.ac.uk and remove footnote about it being
+ temporary
+ (throughout): \emph{}asise `your name' in mailing list subscription
+ info
+ (section{The Background}): Correct address for TUG
+ (section{Format conversions}): dvips implements the hypertex specials
+ now
+ (section{Format conversions}): First stab at editing `making acrobat
+ documents'
+ (section{\MF{}}): Got rid of that awful American-style date in ln03
+ mode file
+ (section{Recent Developments}): Added a pdftex question, moved all the
+ statements about eTeX into present tense, and linked to TeX live in
+ the CDROMs section
+
+ * newfaq.tex: Edit note (beneath title) to refer to 1995 Christmas
+ edition, and to make availability via WWW present tense...
+
+Tue Jun 10 12:44:20 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Tidy question about
+ availability of the article, and reword pointer to Bodenheimer's one
+ since it's now just to the directory;
+ (section{Bits and pieces of \TeX{}}): Reword the question about DC
+ fonts to one about EC fonts.
+ (section{Acquiring the Software}): Add TeX Live to CD-ROM distributions
+ (section{\TeX{} Systems}): Remvoed the reference to the AIX and 386ix
+ distributions (which are wildly out of date), tidy up the text about
+ Linux, and add a caveat about the Slackware '96 disc
+ Top of file: change to version 2.1
+
+ * dirctan.tex: Add TeX-FAQ (in obsolete/help)
+ Remove dc, add ec in its place
+
+ * filectan.tex: Remove TeX-FAQ
+
+Tue Jun 3 15:38:34 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): add the LGC to the
+ book list, and change the phrasing of the `books that cover 2e' list
+ at the bottom of the list.
+
+Thu Apr 24 11:03:17 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Correct Kinch's details
+ just that little bit further
+
+Wed Apr 23 09:31:06 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): New Web address for PTI
+
+Mon Apr 21 14:48:56 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: Remove (confusing) faq and sgi dirs (both under fweb)
+
+Thu Apr 17 17:34:55 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): Final address for NTG's Web
+ offering...
+
+Wed Apr 2 13:57:22 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Update Kinch's web address
+
+Fri Mar 7 10:45:43 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{How do I do \textsl{X} in \TeX{} or
+ \LaTeX{}}): Recode the expression of |\begin{comment}| ... it
+ would appear that the perl happily gobbles the \begin{comment}
+ because it's something it knows about
+
+Mon Mar 3 16:53:14 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * companion.ctan: Bunch of changes from latex209->latex trees
+
+Wed Jan 29 15:44:52 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * filectan.tex: Get xtexcad from graphics/xtexcad
+
+ * faqbody.tex (section{Support Packages for \TeX{}}): xtexcad
+ definitely does work on other Unices
+
+Tue Jan 7 12:25:50 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Remove the (hopeless)
+ reference to news.answers archives of BB's FAQ, and add references to
+ source location of our FAQ and to the cstug, dante and (2) french FAQs
+ (section{Introduction}): Update the information about the committee,
+ add a pointer to the sources, and tidy
+ (throughout): convert URL and FAQ to \acro (and change the one instance
+ of "an FAQ" to "a FAQ" ... who knows which is right, after all?); a
+ few more Ulrik Vieth typos
+ (section{Recent Developments}): Add references to Omega and e-TeX
+ distributions
+
+ * dirctan.tex: Add dante-faq, french-faq, uktug-faq, omega, e-TeX
+
+Thu Jan 2 13:56:25 1997 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): a small number of extra extra typos from
+ Ulrik Vieth
+
+Fri Dec 20 11:23:29 1996 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): Several typos corrected, mostly spotted by
+ Ulrik Vieth
+ Remove pointer to help/TeX-index/TeX-index from `finding packages', and
+ add a reference to www.ora.com instead
+ (section{Documentation and Help}): Add reference to www.dante.de in the
+ question on finding files on CTAN
+
+ * filectan.tex: Remove TeX-index (since it's now no longer on CTAN)
+
+Thu Dec 12 12:35:35 1996 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * dirctan.tex: Add moreverb
+
+ * faqbody.tex (section{The Background}): Correct the archive pointer
+ from the question on texinfo
+ (section{Special sorts of typesetting}): Add reference to moreverb in
+ the question on including a file in verbatim
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): Add a question
+ whose answer is (in part) stblftnt.sty
+ (section{Format conversions}): Add a reference to texcnven
+
+ * filectan.tex: Change texinfo-macros to texinfo-dist, which points to
+ the .tar.gz file, and add a texinfo-dist-zip (oh dammit)
+ Add stblftnt.sty and texcnven
+
+Sat Oct 19 21:48:52 1996 Robin Fairbairns <rf@cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Correct area code in Kinch's
+ telephone and fax nos
+
+Wed Jul 24 15:27:32 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Move ctan-ann to
+ Heidelberg ...
+ There are `other' TeX-related lists there now (!)
+ (section{Acquiring the Software}): Move ctan to Heidelberg too
+
+Mon Jul 1 11:26:32 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * Makefile (clean): new target
+
+ * faqbody.tex (section{Documentation and Help}): removed first
+ component of vm.urz.uni-heidelberg.de
+
+Thu Jun 27 15:06:50 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Downgrade the
+ reference to TeX-Index (should I junk reference to it altogether?),
+ and give catalogue.html top billing
+ (section{Acquiring the Software}): finger ctan@ftp.tex.ac.uk or
+ ctan@ftp.dante.de
+
+ * filectan.tex: Add catalogue
+
+Thu Jun 20 13:29:07 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): Remove reference to
+ ftpmail@shsu.edu
+ (section{Documentation and Help}): Nahhh... you can't get the FAQ from
+ SHSU's mail server (can you?) -- tell 'em to use ftpmail instead
+
+Tue Jun 18 17:10:49 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Acquiring the Software}): Removed SHSU from the
+ list of CTAN sites
+
+Mon May 27 13:49:23 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * companion.ctan: Corrections submitted by Brian Ripley
+
+Wed May 22 14:25:07 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * companion.ctan: Update moreverb
+
+Sat May 18 17:06:12 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * dirctan.tex: Add mdwtools
+
+ * filectan.tex: Add threeparttable
+
+Thu May 2 17:47:51 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * Makefile: for the letterfaq.*ps, use -t letter (now that I've
+ installed it in the config files... ;-) ... not that it works at all
+ ... ah me, back to the drawing board ...
+
+Thu Apr 11 12:59:58 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Extended TCI's ZIP to 9 digits
+ (_big_ deal!)
+
+Thu Apr 4 10:52:35 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Updated V\TeX entry from
+ MicroPress' home page (mailed a copy to their support address for
+ their evaluation
+
+Thu Mar 21 18:03:59 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * dirctan.tex: Add miktex
+
+ * filectan.tex: Correct location of setspace
+
+ * faqbody.tex (section{\TeX{} Systems}): Add mik\TeX
+ (section{Special sorts of typesetting}): Comment out the \subQ ahead of
+ the fancyheadings question, pending resolution of the problems with
+ the HTML-iser
+
+Wed Mar 13 11:08:11 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * companion.ctan: setspace from contrib/supported/setspace
+
+Mon Mar 11 <some time> 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * companion.ctan: major revision from SPQR (forgot to log it...)
+
+Mon Mar 4 09:57:37 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * companion.ctan: fnpara from contrib/other/misc
+
+Thu Feb 29 12:52:18 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faq.sty: Hideous hacking (no doubt, phase 1 only ;-) to get \subQ
+ working
+
+Thu Feb 22 11:59:26 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): Added Q66a (but
+ it won't typeset yet, because I don't have \subQ coded...)
+
+Wed Jan 31 09:37:17 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Recent Developments}): Disembuggered a bit of
+ conditional code in \LaTeXe question
+ (section{The Background}): Minor typo editing
+ (section{The Background}): WG-92-05 contact:=Sebastian, WG-94-07:=Karl
+ Berry
+ (section{Things are Going Wrong\dots{}}): hyphen.cfg not lthyphen.cfg
+ (section{Things are Going Wrong\dots{}}): Add a word about the
+ alternative hyphenation character in DC fonts 1.2
+ (section{Special sorts of typesetting}): Add descriptions of fenm[pf]
+
+ * dirctan.tex: Change tds to point to tds/draft-standard
+
+Tue Jan 30 15:05:06 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): Removed `May' from the
+ assertion about the date when JF hopes to release
+ (section{Bits and pieces of \TeX{}}): Add projected release date for EC
+ fonts (courtesy Ulrik Vieth), and add an exhortation about using
+ 1.2/pl1 at least
+ (section{PostScript and \TeX{}}): Add a reference to mathppl, in the
+ section on mathptm (of course)
+
+ * filectan.tex: Add mathppl
+
+Fri Jan 19 09:33:25 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex: (Throughout): Odd bits of \acro-isation ... still,
+ and general proof-reading corrections
+ (section{The Background}): Restore \rightmargin for quote env for NTG
+ (section{Acquiring the Software}): Commented out the elaborate text
+ about the Decus TeX collection (we know there's up-to-date images, but
+ the only mirror I can find is dated Apr '94, and wuarchive times out
+ (section{\MF{}}): Use list rather than tabular for the log report
+ (section{PostScript and \TeX{}}): Remove the reference to PSNFSS in the
+ discussion about font metrics
+ (section{Recent Developments}): Further iteration of the panegyric
+ about the qualities of 2e; also removed the text about latexbug, since
+ it also appears in the last question
+
+ * faq.sty: Today's date, slight increment of version
+ Add a command \fullline
+
+Thu Jan 18 14:15:23 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): Commented LAMSTeX out again
+ Gave the version today's date
+ (section{Recent Developments}): \acro-ised dvi throughout, except for
+ one instance where referring to the file name extension
+ (section{Special sorts of typesetting}): Removed the question
+ "insisting on changing the margins" (merged into the previous one),
+ reword the statements it makes slightly
+ (section{Special sorts of typesetting}): Added Seb's question on
+ drawing packages
+ (section{\TeX{} Systems}): Added a reference to TeXtelmExtel directory
+
+ * dirctan.tex: Add TeXtelmExtel
+
+ * production/bask5_6.tex: A bit more in the intro; \acro-ised
+
+Wed Jan 17 11:53:21 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): Hacked out Bodenheimer's intro
+ (which used to be commented out anyway); change "has been" to "was" in
+ describing Bodenheimer's maintenance...
+ Gave the version today's date
+ A few more proofreading corrections
+ (section{Special sorts of typesetting}): Redone the examples in the
+ figures-in-text question to use explicit line breaks
+ (section{Things are Going Wrong\dots{}}): Add question on hyphenation
+ of accented words
+ (section{Bits and pieces of \TeX{}}): Add question on DC fonts
+
+ * filectan.tex: Correct TeX-FAQ address (must have been wrong from the
+ start!!!
+
+Tue Jan 16 15:43:04 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex: Lots more \acro-isation
+ Up to v2.0d, dated today
+ Bunches of proof-reading corrections
+ (section{\TeX{} Systems}): Added TeXtelMextel to list of shells
+
+ * faq.sty: \acro-ise ISBN
+
+Mon Jan 15 09:44:14 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{The Background}): Added a web address for NTG
+ Surround both instances of `2e' in question names with \boldmath
+
+Sun Jan 14 18:01:19 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex: Surrounded a whole bunch of things in \acro
+ (section{The Background}): Added a few Web addresses for user groups
+ (throughout): Various proofreading corrections (DPC,MJC,RF)
+
+ * dirctan.tex: Got rid of all the old references to fonts/metrics
+
+ * faq.sty: In \AllTeX, kern equally on either side of the closing
+ parenthesis
+ \acroise \DANTE, \MSDOS and \CDROM
+ Declare a \twee macro (to append 2e if necessary)
+ Define a \careof macro (code out of tugboat.dtx)
+
+Tue Jan 9 13:19:42 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Format conversions}): Only one version of
+ "\AllTeX{} conversion to HTML" question title
+ (throughout): \TeX{}/\LaTeX{} -> \AllTeX{}
+
+Wed Jan 3 14:23:09 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Special sorts of typesetting}): Add a label to
+ the text flowing section, for reference in the editorial
+ (throughout): more minor editorials
+
+ * production/faqfont.cfg: Null file, to suppress faq.sty's default to
+ using times
+
+ * production/bask5_6.tex: Rewrote the editorial and the title of the
+ FAQ article itself
+
+ * production/baskerv.cls: Changed (guest) editor name
+ Subsection titles to use \bfseries (rather than \itshape)
+
+Note: directory spqr renamed as production...
+
+Tue Jan 2 12:35:03 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * spqr/bask5_6.tex: From bask4_6.tex, but added \thisyear
+ and \thismonth
+
+ * spqr/5_6baskerv.cls: Changed subsection heading back to \bfseries
+ Select font encoding before selecting family mbvx,
+ \usepackage{t1enc}->\usepackage[T1]{fontenc}
+
+ * faqbody.tex (throughout): Many minor editorial changes
+ Use \raggedwithindent
+ Subsume every occurrence of CTAN in an \acro
+
+ * faq.sty: Add \@ wherever I consider it necessary (includes replacing
+ at least one instance of `\spacefactor1000 '
+ Add a kern before the closing parenthesis in \AllTeX
+ Add an \acro command (and \textSMC as a result...)
+ Redo \Question using \newcommand with an optional argument, and set
+ raggedright in the question title (note: suppresses hyphenation)
+ Add \nothtml command (transparent)
+
+Mon Jan 1 16:37:53 1996 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Introduction}): Add Donald Arseneau and
+ W. Henning (what's the man's first name?)
+ (section{The Background}): Remove line break in Dante details
+ (section{Format conversions}): Add text on TeX2RTF
+ (section{Format conversions}): Correct SPQR's reference to latex2rtf
+ (he was plainly talking about tex2rtf)
+ (section{The Background}): Add a label to the lollipop question
+ (section{PostScript and \TeX{}}): Refer to the lollipop question where
+ a side reference to it is made re. PostScript metrics
+ (section{Special sorts of typesetting}): Slight rearrangement of text
+ in the stuff on wrapping text around figures...
+
+ * faq.sty: Add an \AllTeX command
+
+ * 00readme: Update, dealing with the existence of 600dpi versions,
+ letterfaq (used only to be dealt with in one place) and possibility of
+ problems with old versions of 2e
+
+ * Makefile.FTP: Add 00readme to `all' target
+
+ * Makefile: Add the .300ps things as separate targets
+ Ensure the ftp-directory Makefile is writeable once it's there
+
+Sat Dec 30 17:20:05 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex: Upped the file version and given it today's date
+ (section{Documentation and Help}): Sort out the text about obsolete man
+ pages...
+ (section{Documentation and Help}): Tried a few apostrophe-s in the list
+ of book titles that cover 2e
+ (section{Documentation and Help}): Tidied up DPC's text a bit
+ (incidentally also dealing with a fantasy introduced by my spelling
+ checker!)
+ (section{Documentation and Help}): Couple of minor enhancements to
+ Carol's text
+ (section{Special sorts of typesetting}): Added the long-bruited
+ question on flowing text around figures
+
+ * dirctan.tex: Added reference for floatflt
+
+ * filectan.tex: Added references for picins and wrapfig
+
+Fri Dec 29 21:03:12 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * Makefile: Move removal of the Makefile into the bracketed bit in
+ install
+ Let's have letterfaq.ps actually *make* letterfaq.ps rather than yet
+ another newfaq.ps, folks!
+
+ * faqbody.tex (section{Acquiring the Software}): Added Walnut Creek
+ address and telephone nos from their Web site
+
+Thu Dec 28 18:53:45 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Documentation and Help}): Replaced
+ \Question[index]{Finding \TeX{}/\LaTeX{} macro packages} and
+ \Question[compan-files]{Finding \LaTeXe{}-related packages} with two
+ entirely new answers by the estimable Dr. C.
+ (section{Acquiring the Software}): Added a reference to Walnut Creek's
+ little baby (and despatched a message asking for more)
+
+Tue Dec 19 17:07:09 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Updated Kinch's details from
+ the email he sent me
+
+
+Sat Dec 9 17:24:47 1995 Robin Fairbairns <rf@nape.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Updated Kinch's entry as best
+ I can just now...
+
+Mon Dec 4 10:03:22 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{PostScript and \TeX{}}): Rewrote paragraph about
+ Goel's document to cover Reckdahl's one as well
+ (section{Documentation and Help}): Rewrite `where to find' to make more
+ clear the distinction between Bodenheimer's article and ours (which
+ does, after all, get updated ;-)
+ (section{Documentation and Help}): Put all the subscribe messages in
+ the question on mailing lists into \texttt, so they can break
+
+ * dirctan.tex: Delete reference for ps2psfrag, alter psfrag to 2e
+ version
+ Add subfigure
+ Convert (2.09) supertab to (2e) supertabular
+
+ * filectan.tex: Added epslatex
+
+ * newfaq.tex: Remove the reference to c.t.t FAQ in the note, since it's
+ plain that nothing will ever get into anything maintained by
+ Bodenheimer
+
+Fri Dec 1 16:30:56 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * dirctan.tex: Add tweb
+
+ * faqbody.tex (section{\MF{}}): Add a label to `getting \MF to do what
+ you want'
+ (section{Literate programming}): Add a reference to tweb
+ (section{Bits and pieces of \TeX{}}): Add Carol's set: dvi, driver, pk
+ and tfm (order probably needs attention)
+ (section{Format conversions}): Thrown out scribe
+
+ * filectan.tex: Add dvitype
+
+Thu Nov 30 12:01:01 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (throughout): Convert all reference to specific TUGboat
+ issues to use the \TUGboat macro, all other references to \textsl
+ (section{Format conversions}): Add Clark's DSSSL page where Seb wanted
+ one, and fill in the URL for stil (Seb found this)
+ (section{Things are Going Wrong\dots{}}): Suggest upgrading \LaTeXo
+ ("if they must"), nopageno.sty
+ (section{\TeX{} Systems}): Sort out the reference to emTeX
+
+ * faq.sty: \ignorespaces before handing on to \@tugboat
+
+ * dirctan.tex: Add latex209-base
+
+ * filectan.tex: Add nopageno
+
+Wed Nov 29 16:33:39 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): |\protect\cmd| ->
+ \cs|protect|\cs|cmd| so that it doesn't get (hem-hem) b*ed by Alan's
+ perl script
+ (section{The Background}): Add reference to tds in the TWG's blurb
+ (section{The Background}): Update T.V. Raman's email address
+ (section{Documentation and Help}): Note that the book list is only of
+ English ones
+ ():
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): Add reference
+ to \frontmatter, \backmatter in the thing about unnumbered sections in
+ the TOC
+
+ * dirctan.tex: Add tds
+
+Tue Nov 28 10:14:34 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * dirctan.tex: Add hyper and hyperref
+ Change psfonts to dos-psfonts (it wasn't referred to, anyway), and
+ create a new psfonts pointing at fonts/psfonts
+
+ * faq.sty: Add definition of \TUGboat
+ Use \ProgName for \Package, pro tem
+
+ * faqbody.tex: Change version number
+ (section{Recent Developments}): Junk Q-SGML (and the one reference to
+ it)
+ (section{Perhaps There \emph{isn't} an Answer}): uktex->texhax
+ (section{Format conversions}): Added questions on hyperTeX and
+ conversion to pdf, and replace Q-SGML2TeX and Q-LaTeX2HTML
+ (section{PostScript and \TeX{}}): Replace Q-usepsfont, Q-metrics,
+ psfonts-problems
+ (section{Why does it \emph{do} that?}): A bit more text from Alan about
+ uppercase shenanigans
+ (section{The Background}): Update TUG's address
+
+Sat Nov 18 12:23:58 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Perhaps There \emph{isn't} an Answer}): Added a
+ pointer to the bugs database in the last question (ASAJ's suggestion)
+
+ * dirctan.tex: Remove emtex/betatest
+
+Sat Nov 18 00:05:11 1995 robin (robin@dosmachine)
+
+ * faqbody.tex (section{Documentation and Help}): Added the metafont
+ list to the section on mailing lists
+ (section{Introduction}): Redone the list of committee names (it said
+ "1993-94" !!!), and added a paragraph acknowledging Rho's, Jonathan's
+ and Chris's efforts.
+ (section{Acquiring the Software}): Make the numeric addresses \FTP
+ addresses, too, so that they wrap
+ (section{Acquiring the Software}): Put `quote site index' (and,
+ separately, `site index') into \texttt (rather than verbatim) so that
+ it wraps if necessary
+ (section{Support Packages for \TeX{}}): Add a bit of explanation of
+ _why_ VorTeX isn't still being developed
+
+ * dirctan.tex: Add metapost
+
+Fri Nov 17 23:29:42 1995 robin (robin@dosmachine)
+
+ * faqfont.cfg: Deal with \Dings
+
+ * faqbody.tex (section{Introduction}): Added John Hobby (because I'm
+ lifting some of his text) and Piet van Oostrum to the list of
+ contributors
+ (section{The Background}): Add a new question about MetaPost (does it
+ really need to be separate?)
+
+Fri Nov 17 13:12:10 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * dirctan.tex: Correct teTeX base directory and add tetex-bin
+
+ * faqbody.tex (section{Documentation and Help}): Disambiguate
+ references to Gratzer's books in the short para after the list of LaTeX
+ books
+ (section{\TeX{} Systems}): Add reference to the teTeX binaries
+ directory
+ (section{\TeX{} Systems}): Remove witter about emTeX betatest, and
+ reword the reference to memory extenders (emxrsx is now part of the
+ distribution)
+
+Wed Nov 8 11:41:47 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * filectan.tex: Add mil
+
+ * faqbody.tex (section{Documentation and Help}): Add reference to the
+ acrobat sampler of Gratzer's book
+
+Tue Nov 7 11:02:31 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{\TeX{} Systems}): Updated scientific word's
+ telephone no, following mail from Christopher
+ (section{Documentation and Help}): Add Gratzer's new book, and correct
+ the text at the end of the list detailing 2e coverage
+
+Sat Aug 26 14:57:41 1995 Robin Fairbairns <rf@dorceus.cl.cam.ac.uk>
+
+ * faqbody.tex (section{Recent Developments}): Subscription information
+ for the omega list
+
+Mon Jul 3 15:01:38 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * 00readme: Note that psfonts-beta is being used
+
+ * dirctan.tex: Added the two musixtex directories
+
+ * faqbody.tex: Added WWW entries for Bluesky, Personal TeX Inc. and TCI
+ Removed claim of "orchestral" music for MusicTeX, added a reference to
+ MusiXTeX
+
+Wed Jun 28 16:17:28 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex: subscribe to texhax via texhax-request
+ give details of Kopka and Daly 2nd ed
+ changed fileversion to 1.9e
+
+Thu Jun 15 17:26:05 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex: Added DPC's neato search for package.??? in quote site
+ index
+
+Wed May 3 10:06:54 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * companion.ctan: Corrected companion.ctan re. curves
+
+Fri Apr 28 13:10:30 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * simpl-sum.txt: A plain text version of the question `what is TeX'
+
+Fri Mar 31 11:15:23 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * texnames.sty: Add definition of \mathcal if it's not there, and
+ redo \AMSLaTeX, \AMSTeX (et al) in terms of \AmS defined similarly
+ to how the definition of \AmSTeX was done
+
+Mon Mar 6 14:55:13 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * companion.ctan: Added graphics.sty (not in companion?)
+
+Sat Feb 11 14:23:41 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{\TeX{} Systems}): Update contact details for Y&Y
+ (section{Documentation and Help}): details of ctan-ann mailing list
+ Up to 1.9d
+
+Tue Jan 31 17:48:21 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{Documentation and Help}): Add a proviso about
+ multiline-message suppression using `-' to the blurb about quote site
+ index
+
+Mon Jan 30 12:46:02 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * updates.tex (section{Updates to the FAQ}): as its name implies -- a
+ contribution to BV 5.1
+
+ * faqbody.tex (section{Documentation and Help}): Corrected the
+ information about info-tex and ctt-digest and their mutual relationship
+ to comp.text.tex
+
+ * filectan.tex: corrected file name of Tobin's metafont intro (and also
+ its directory!)
+
+Fri Jan 20 17:12:20 1995 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.cls: Adjust the page layout with a view to simplicity, symmetry,
+ and all those good things
+
+Fri Dec 16 13:22:52 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{The Background}): Remove the em-dashes between
+ the item labels and the TWG titles
+ (section{How do I do \textsl{X} in \TeX{} or \LaTeX{}}): Remove the
+ gratuitous \protect commands from the non-moving part of the [sub]
+ section arguments in the question on fiddling with the layout of
+ sectioning commands
+ (section{The Background}): Use \Emaildot for Yannis' address
+ (section{Format conversions}): Ditto for Nathan Torkington
+ (section{Documentation and Help}): Split the title boxes for both
+ Gr\"atzer's and Shultis' books
+ (section{\MF{}}): Insert @{} at every touch and turn in the
+ `table' specification for the instructions for inimf
+
+ * faqfont.cfg: Add (null) definition of \Dings
+
+ * faq.sty: If using PostScript, define \Dings
+ Add \Emaildot (as \Email, but dot-separates the first part of the
+ name)
+
+ * letterfaq.tex: Same as original newfaq.tex (i.e., letter paper by
+ default), except for \Dings
+
+ * newfaq.tex: Load faq.cls with a4paper option, use \Dings between toc
+ and body
+
+ * faq.cls: Use the paper size we're loaded with; adjust size of text
+ relative to it (using same values SPQR does for A4 paper, not some wild
+ proportional values)
+
+Mon Dec 12 13:07:36 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex: Use \ifnotreadCTAN, set it once the configs read
+
+ * faq.sty: Add \ifnotreadCTAN
+
+Sat Dec 10 10:21:36 1994 Robin Fairbairns (robin@home)
+
+ * faq.cls: First iteration of a class -- aim is that it should
+ ultimately be `generic' as between paper sizes
+
+ * newfaq.tex: Reword for `after the publication', add invocations of
+ multicols
+
+Sun Dec 4 13:54:02 1994 Robin Fairbairns (robin@home) (Sun 13:)
+
+ * faqbody.sty (throughout): The red-biro attack.
+ (throughout, again): The red-fine-felt-tip-pen attack (JF).
+ (section{Recent Developments}): Add a short blurb about JF's work.
+
+ * spqr/baskerv.cls: Cut down \topsep in \@listi to 4pt basic
+
+ * spqr/bask4_6.tex: Add a paragraph about use of the December edition;
+ Don't bother with table of contents before the editorial; the only toc
+ is that within the article itself
+
+Wed Dec 7 12:07:47 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * dirctan.tex: Add sgml2tex
+
+ * faqbody.tex (section{Recent Developments}): Add reference to the
+ conversion programs in the answer about JF's stuff
+ (section{Format conversions}): Add an answer about SGML2TeX conversion
+ programs
+ (section{\MF{}}): Modify the surroundings of the table for running MF,
+ to get rid of the unsightly space at the top
+ (section{Bits and pieces of \TeX{}}): Comment out that question on font
+ formats
+
+Tue Dec 6 13:54:07 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex: Change file version and date
+ (section{Bits and pieces of \TeX{}}): Add question on font formats
+
+Mon Dec 5 15:27:20 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * spqr/baskerv.cls: Hack the toc to make it not produce newarticle
+ entries whatsoever
+
+ * faqbody.tex (throughout): Final consistency checks following
+ spell-check
+
+Sun Dec 4 13:54:02 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.sty (throughout): The red-biro attack.
+ (throughout, again): The red-fine-felt-tip-pen attack (JF).
+ (section{Recent Developments}): Add a short blurb about JF's work.
+
+ * spqr/baskerv.cls: Cut down \topsep in \@listi to 4pt basic
+
+ * spqr/bask4_6.tex: Add a paragraph about use of the December edition;
+ Don't bother with table of contents before the editorial; the only toc
+ is that within the article itself
+
+Fri Dec 2 17:49:38 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * texnames.sty: Use \mathcal rather than \cal
+
+ * filectan.tex: Add morefloats.sty
+
+ * faqbody.tex (section{Things are Going Wrong\dots{}}): Replaced two
+ questions on floats with one conglomerate one (by me)
+
+Thu Dec 1 22:04:45 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Add a new
+ question on #-doubling (from a post of David C's)
+ (section{Things are Going Wrong\dots{}}): Add a new question on BibTeX
+ string sizes
+
+Tue Nov 29 18:49:52 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * spqr/bask4_6.tex: Twiddled with secnumdepth/tocdepth to get things
+ looking roughly right
+
+Tue Nov 29 13:19:09 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Add a question on
+ uppercase, from Jonathan's input
+ (section{Acquiring the Software}): Move the CD question here from TeX
+ systems
+ (throughout): Minor editorials
+
+ * faq.sty: Version no:=0.6, date changed
+ Added hacked-about LaTeX logo
+
+Mon Nov 28 13:32:53 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * spqr/bask4_6.tex: Moved setting secnumdepth/tocdepth to inside the
+ FAQ article
+
+ * faqbody.tex (throughout): More of my minor editorials
+ (subsection*{Finding the Files}): Added note about the lack of
+ full stops
+ (section{Introduction}): Sorted list of helpers into alphabetical
+ order, removed dots from the end
+
+Sun Nov 27 18:23:34 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (section{Why does it \emph{do} that?}): Add question on
+ the problems with \verb (from JF's input)
+
+Sat Nov 26 22:09:17 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (section{\TeX{} Systems}): Added Tom Rokicki's details
+ (wot no contact number) and changed the `source' of the stuff from the
+ AMS listing
+
+Fri Nov 25 12:41:36 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (throughout): Barbara Beeton's comments and Alan
+ Jeffrey's niggles
+ (section{PostScript and \TeX{}}): Added reference to mathptm in
+ Berthold's question
+ (throughout) Minor markups by your truly
+ (section{Documentation and Help}): Added a question about email lists
+
+ * faq.sty: Remove spurious space generated by \ProgName
+ Separate the hyphens in \TeXXeT.
+
+Thu Nov 24 15:29:47 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (throughout): Editorial markup after looking at
+ \BV-formatted version
+ (section{\TeX{} Systems}): Add a bit of blurb about Northlake Software
+
+ * dirctan.tex: Add emtex-betatest
+
+ * faq.sty: Define a new environment proglist (maps to booklist while
+ we've got program names italic)
+
+ * spqr/baskerv.cls: Remove stuff from faq.sty, and add requirement of
+ the FAQ package
+ Comment out definition of \CTAN (to something inconsistent)
+
+Wed Nov 23 10:20:27 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.sty: Make program names typeset in italic (experimentally)
+
+ * faqbody.tex: Released to SPQR for his work ... then:
+ (throughout): SPQR's editorial changes
+
+Tue Nov 22 22:53:24 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex: Iterate calls of \cs back again...
+
+ * faq.sty: Define \cs in terms of robust \csx (which is exactly the
+ same as the original \cs); \cs|...| now
+
+Tue Nov 22 13:10:26 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * texnames.sty: Sort out the definition of BibTeX (\if re. \textsc was
+ in the wrong place), do similar thing for SliTeX
+
+ * faqbody.tex (throughout): All \ldots -> \dots (and make sure there's
+ a {}!)
+ (section{Introduction}): Add Ulrik to the intro
+ (throughout): Two complete iterations of the syntax for \cs
+
+ * faq.sty: Replace my implementation of footnoteenv by one posted by
+ David to comp.text.tex (on a different matter, but there we are...)
+ Change syntax of \cs to \cs|...|, then find that doesn't work and
+ change it again to \cs[...]
+
+ * faqvers.tex: Removed, since now done in faqbody.tex
+
+Mon Nov 21 22:49:05 1994 Robin Fairbairns (robin@home)
+
+ * faq.sty: Replace \def\Q with the version Seb had put in the faqbody
+
+ * faqbody.tex: Remove \def\Q from front of file, and insert the content
+ of filevers.tex in its place (with comment about how it's to stay where
+ it is)
+
+ * newfaq.tex: Instead of reading faqvers.tex, read the first two lines
+ of faqbody.tex and execute them to get the file version and date
+
+Mon Nov 21 12:52:09 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (throughout): Implement Ulrik Vieth's and Malcolm Clarks
+ (latest) comments;
+ (section{How do I do \textsl{X} in \LaTeX{}}): Add a question about
+ indenting the first line of sections (Ulrik's suggestion)
+
+ * faq.sty: Added definition of \ISBN (to encourage uniformity)
+ \DANTE simply expands to DANTE (until someone else tells me
+ something different ;-)
+
+ * dirctan.tex: Added rnototex (now that it exists) and tetex
+
+Sun Nov 20 16:16:26 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (throughout): Deal with David C's comments
+ (section{Documentation and Help}): Add reference to LaTeX for
+ Scientists and Engineers;
+ (section{\TeX{} Systems}): Add some blurb about SciWord
+ (throughout): Deal with my editorial markup
+ Two new questions
+
+ * newfaq.tex: Report the number of questions at the end
+
+ * faq.sty: \ignorespaces at the beginning, \unskip at the end of
+ footnoteenv
+
+ * filectan.tex: Add xtexcad, CTAN-sites (needs checking)
+
+Fri Nov 18 22:12:21 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (section{Format conversions}): Correct Mark James' email
+ address, following mail from him saying that's OK (section name
+ changed, too)
+ (section{Acquiring the software}): Correct the DECUS address, telephone
+ no., etc., and Ted Nieland's email address; also add the proviso about
+ updating of the VMS material in the DECUS collection
+ (throughout): execute Reinhard Zierke's updates (though don't add his
+ complete set of ISBNs for von B ... yet: just leave them there behind
+ comment makers)
+
+Tue Nov 15 10:12:48 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * dirctan.tex: Add alpha (the mac editor)
+
+ * faqbody.tex (section{The Background}): Added a question on Lollipop
+ (which may get updated if Eijkhout responds to my mail)
+ (section{Documentation and Help}): Three more book titles (ex Malcolm),
+ re-attribution of ISBNs Clark<->von Bechtolsheim
+ (section{\TeX{} Systems}): Further refinement of the commercial stuff
+
+ * faqvers.tex: Upped to v1.5, changed date
+
+ * filectan.tex: Add texinfo-macros
+
+Mon Nov 14 22:14:08 1994 Robin Fairbairns (robin@home)
+
+ * faq.sty: Add a ghastly \TeXXeT logo (and a trivial \MLTeX)
+
+ * faqbody.tex (section{The Background}): Add new questions on
+ \LAMSTeX{} (split out of \AMSTeX{}) and Texinfo
+ (throughout): "like"->"such as" (where appropriate)
+
+Mon Nov 14 12:02:44 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (throughout): editorials from loads of people, new stuff
+ for the AMSTeX question from Michael Downes, several new questions from
+ Sebastian...
+
+ * filectan.tex: Added pk300[w]
+
+ * faq.sty: Provide command \CDROM
+
+Sun Nov 13 20:27:34 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex (throughout): All incarnations of the name DOS converted
+ to \MSDOS{}
+ Lots of minor edits following another batch of comments from RAB; three
+ new questions
+ Berthold Horn's question on scaleable fonts (probably needs post-
+ printing review)
+
+ * faq.sty: Redo definition of \cs to enable it to consume things other
+ than letters and others
+ Add definition of command \MSDOS
+
+ * faqbody.tex (section{The background}): When referring to WEB, do it
+ in capitals for consistency (What is TeX?)
+ (section{Things are Going Wrong\ldots}): Change invocation of \cs
+ to be simply \cs{pagestyle{empty}}, following change to \cs
+Fri Nov 11 11:45:59 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{\TeX{} Systems}): Modified the list of
+ commercial versions to say platform first, name of system second
+ (section{Introduction}): Add Malcolm's name to committee list!!!!!
+
+Thu Nov 10 12:38:03 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (from section{Bits and pieces of \TeX{}} to
+ section{Recent Developments} [i.e., the end]): sorted the html anchor
+ texts
+ (section{\TeX{} Systems}): Added Malcolm's body for the commercials
+ question
+ (section{The Background}): Added Damian Cugley's questions on
+ pronunciation
+ (section{Special sorts of typesetting}): Added Damian Cugley's question
+ on logos
+
+ * filectan.tex: Get setspace from the latex tree rather than the 209
+ one
+ Add texnames
+
+Wed Nov 9 14:44:25 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{Introduction}): Add Rick Zaccone to the list of
+ helpers
+ (up to section{Documentation and Help}): sorted the html anchor texts
+
+Tue Nov 8 11:43:02 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{Documentation and Help}): Added ISBNs (from
+ Malcolm) for his an von B's books
+ (section{PostScript and \TeX{}} and elsewhere): Small number of changes
+ arising from Alan's comments
+
+ * filectan.tex: Add Excalibur-sea (we don't want them loading the
+ entire directory)
+
+ * faqvers.tex: New, the settings of fileversion and filedate from
+ newfaq.tex
+
+ * newfaq.tex: Replace setting of fileversion and filedate by inputting
+ of faqvers.tex
+
+Mon Nov 7 11:42:12 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.sty: define a footnoteenv as suggested by Alan
+
+ * faqbody.tex (section{Acquiring the Software}): Removed the reference
+ to Flynn's ridiculously old "NETWORK SOURCES OF \TeX{}WARE"
+ (section{Acquiring the Software}): Couple of instances where there were
+ \\ commands at the end of a quote environment; this causes untoward
+ blank space after the environment, so they've been removed
+ (section{Bits and pieces of \TeX{}}): New section, with Seb's virtual
+ fonts question, and a version of \Rho's on \specials (will contain the
+ proposed .dvi and "what's a driver" questions, too)
+ (throughout): replace \footnote{}s with footnoteenv
+
+Sun Nov 6 20:10:52 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex: Slight editing, added questions on msx/y and am fonts
+
+Sat Nov 5 21:41:34 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex: Rearrange the intro slightly to include an outline of
+ what Usenet is about, for the benefit of members who aren't net-
+ connected (this at \Rho's suggestion)
+ Add question on paragraph setting parameters
+Sat Nov 5 14:52:03 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faqbody.tex (section{The Background}): Changed our contact address to
+ Peter Abott
+ (section{Documentation and Help}): Implemented David's suggestion
+ re. the PicTeX manual
+ (section{\TeX{} Systems}): changed `public domain' to `freely
+ available' in re. PC versions
+ (section{Literate programming}): Added a short new question from David
+ on the whole concept
+ (section{Special sorts of typesetting}): Corrected yet more oddities in
+ the changemargin environment
+ (section{Special sorts of typesetting}): Changed `emphasised' to
+ `emboldened' in the LaTeX version
+ (section{Things are Going Wrong\ldots}): Add a reference to ukhyph
+ (section{\TeX{} Systems}): Add reference to shareware fee payments for
+ OzTeX
+ (section{Things are going wrong}): Put the \caption commands in a
+ tabular env, for the benefit of Baskervill narrow setting
+ (section{PostScript and \TeX{}}): Added Sebastian's new questions
+ (inter alia, replacing the original about setting in PS fonts)
+
+ * filectan.tex: Add lw35nfss, LitProg-FAQ, ukhyph
+
+Wed Nov 2 01:26:47 1994 Robin Fairbairns (robin@home)
+
+ * faqbody.tex: updated to match newfaq.tex (\Rho's questions added
+ yesterday)
+
+Tue Nov 1 09:58:40 1994 Sebastian the system admin (root@cygnet)
+
+ * separated text into faqbody.tex and wrapper newfaq.tex;
+ this is to allow experimentation with Baskerville layout.
+
+ * rewrote PostScript fonts question and the one on
+ metrics; added one on problems with PS fonts.
+
+Mon Oct 31 12:14:55 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex: Added a new section How do I do X in \LaTeX{}, as
+ suggested by \Rho, and stuck her remaining proposed questions in it
+
+ * faq.sty: Added the stretchability recommendations from psnfss2e.tex
+ in case setting in times (and remove 'em again)
+
+Sun Oct 30 09:50:54 1994 Robin Fairbairns (robin@home)
+
+ * faq.sty: define a \WYSIWYG command
+
+ * filectan.tex: Change mf-beginners to refer to copy in documentation/,
+ add mf-list
+
+ * newfaq.tex: Move BibTeX docs question above the one on the PicTeX
+ manual
+ (throughout): reformat every \Qref so that the content of the second
+ (first mandatory) argument is the whole of the anchor text
+
+Sat Oct 29 14:27:12 1994 Robin Fairbairns (robin@home)
+
+ * filectan.tex: Add modes-file (to avoid `modes.mf in \CTANref{modes}')
+ and mf-beginners (needs checking)
+
+ * newfaq.tex (throughout): Use \Eplain{} for Eplain
+ Another instance of `\eTeX.'!!!
+ Mark up program names with \ProgName, (more) file names with \File
+ Hack at \MF{} section, following Karl Berry's suggestions
+
+ * faq.sty: Define \Eplain (nullish sort of definition), \ProgName
+ Require comment.sty and exclude a comment of htmlversion
+
+Fri Oct 28 14:05:37 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Acquiring the Software}): Record checking of
+ bitftp@pucc.bitnet, listserv@dhdurz1.bitnet
+ (section{Documentation and Help}): Add reference to Norm Walsh's book
+
+Thu Oct 27 10:39:12 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Special sorts of typesetting}): Added references
+ to abc2mtex, midi2tex (also uploaded 'em to CTAN)
+ (section{The Background}): Added comment about GNU copyleft to the `how
+ come it's free' question
+ (section{Documentation and Help}): Added new question about finding
+ \LaTeXe{} packages (as a place to hang a pointer to companion.ctan,
+ which I've almost finished...)
+
+ * dirctan.tex: Added abc2mtex, midi2tex
+
+ * filectan.tex: Added compan-ctan
+
+Wed Oct 26 23:39:41 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex (section{Documentation and Help}): Sort out formatting of
+ the book lists (ISBNs uniform, no wrapping of \item parameters, removed
+ redundant braces)
+
+Wed Oct 26 12:57:11 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Documentation and Help}): Added stuff about .dtx
+ files
+ (section{The Background}): Add a Question about Eplain (not exactly
+ frequently-asked, but there we are...)
+ (section{\TeX{} Systems}): Use Oz\TeX{} as the `logo'
+ (throughout): Various corrections following Alan's problems generating
+ html
+
+ * dirctan.tex: Corrected spelling of symbols in amsfonts-symbols...
+
+Wed Oct 26 00:02:37 1994 Robin Fairbairns (robin@home)
+
+ * faq.sty: Yet another iteration of the \AtEndDocument CTAN reference
+ checks...
+
+ * newfaq.tex (section{Things are going wrong}): Add RAB's questions
+ Behaviour of \rm, etc.; Missing symbols; Word division; Moving tables
+ and figures; Disappearing tables and figures
+ Add some words about journals in the intro to the question on double
+ spacing
+
+Mon Oct 24 11:26:27 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Special sorts of typesetting}): Refine reference
+ to amsfonts, to get to the directory directly related to the symbols
+ Comment out the "lazy person's" stuff, which I didn't like, and \Rho
+ says doesn't work
+
+ * dirctan.tex: Added amsfonts-symbols (a subdirectory of amsfonts)
+
+ * newfaq.tex (throughout): Do away with the "<American spelling> (sic)"
+ construct
+ (throughout): Lots of minor (and not-so-minor) editorials by Rosemary
+
+ * faq.sty: Add tie between reference to question and the question
+ number
+
+Sun Oct 23 00:25:48 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: Change fileversion to 1.4, date to tomorrow
+ Add 1994/95 committee to the footnote
+ General editorial consistency tidy-up
+ Add question on which font files need to be kept after a run of mf
+ Add new section "why does it _do_ that", with Joachim's text about
+ protection (this is where the proposed question on paragraph parameters
+ will go, too)
+
+ * faq.sty: Make provision for using faqfont.cfg
+
+ * faqfont.cfg: Null configuration file to enable use of CM fonts
+ in the lab
+
+Sat Oct 22 15:41:11 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{DVI Drivers and Previewers}): Extended the text
+ around dvips for VMS
+
+ * filectan.tex: Added {AXP,VAX}VMSdvips, VMSdvips-{fonts,support}
+
+ * dirctan.tex: Added l2a
+
+Sat Oct 22 13:30:17 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: Removed the \NeedsTeXFormat (since it's now done in
+ faq.sty); also types out file versions and so on.
+ Modified text (sometimes by bodily shifts or even rewrites) to ensure
+ that if a \CTANref is at the end of a sentence, it's always also at the
+ end of a paragraph, with no full stop after it
+ Added references (which aren't yet satisfied) for VMS dvips executables
+ and l2a (do we want that, though?)
+
+ * faq.sty: Moved \NeedsTeXFormat to style file
+ Define version number (now 0.4) and date, and type 'em out
+
+Fri Oct 21 09:52:11 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex (section{Documentation and Help}): Redo the lists somewhat
+ (throughout): Sort out {}s after acronym macros (where did those come
+ from?)
+
+ * filectan.tex: Specify usergrps.tex as coming from usergrps/info
+
+Fri Oct 21 13:40:02 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Special sorts of typesetting}): Added reference
+ to vmargin (and posted a question about whether we still want vpage)
+ (section{Special sorts of typesetting}): Add reference to makeindex (to
+ match the one for macmakeindex) and idxtex (what's all this garbage
+ about texindex? -- the .tar.gz file in the directory is (shall we say)
+ peculiar...)
+
+ * filectan.tex: Bit o' sorting into order...
+ Add fullpage, vmargin
+
+ * texnames.sty: Make logo for BibTeX transportable (i.e., usable not in
+ LaTeX2e if required)
+ Add logos \LaTeXe and \LaTeXo
+
+Thu Oct 20 19:38:17 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex (section{Special Sorts of Typesetting}): First attempt at
+ defining the distinction between `indexing' (deciding what's to be
+ indexed and how) and `making an index' (generating the file to include
+ from the .ind)
+ Throughout: re-mark-up \Qrefs (though the ones in comments aren't
+ touched...
+ (section{DVI Drivers and Previewers}): use Mattes' own emTeX logo
+ (at least as it appears in his documentation...)
+ Throughout: verbatimise `ftp'
+ * dirctan.tex: change reference to fancyheadings to point into 2e
+ directory tree
+
+ * texnames.sty: Define \BibTeX using \textsc rather than the ingenious
+ stuff that the original used (which, since it employs \sc, suppresses
+ the use of bold face in section titles)
+
+ * faq.sty: \Qref now to have three arguments, the third being the
+ actual thing we're referring to (the second is for the html processor's
+ anchoring text)
+
+Mon Oct 17 21:03:06 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex (section{Documentation and Help}): Change list of books to
+ use booklist environment
+ (section{Introduction}): Added a \subsection* giving details of the
+ `elided' first directory of every path name (this surrounded by
+ \htmlignore ... \endhtmlignore)
+
+ * faq.sty: Add environment booklist for use in the list of books
+ (egob!)
+ Define \htmlignore,\endhtmlignore to mean \relax
+
+Mon Oct 17 09:16:55 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Special sorts of typesetting}): Correct to a
+ reference to screensty
+ Tiny tweak of the intro note
+ (section{PostScript and \TeX{}}): Corrected reference to figsinlatex,
+ removed comments about the .dvi being available too...
+
+ * dirctan.tex: Added vmspell, txtdist, texsgi declarations
+ Moved 2etools from newfaq.tex itself
+
+ * newfaq.tex (section{PostScript and \TeX{}}): Record the fact that
+ EdMetrics is available on CTAN, rather than by writing to Bluew Sky
+
+ * faq.sty: In \FAQverb only insert \leavevmode if actually in vertical
+ mode
+
+ * newfaq.tex: Input dirctan.tex (instead of namectan) and filectan.tex
+ (instead of the inline definitions it contains)
+ Moved 2etools directory out to dirctan.tex
+ (section{PostScript and \TeX{}}): Give Blue Sky's telephone no. in
+ canonical form
+ (section{\TeX{} Systems}): Corrected the reference to science.utah.edu
+ (which is now ftp.math.utah.edu), checked that the files for TOPS-20
+ are still there...
+ (section{Documentation and Help}): Corrected numeric address for
+ rtfm.mit.edu
+ (section{Documentation and Help}): Made reference to the index an
+ (section{Acquiring the Software}): refer to, rather than name,
+ README.uploads
+ *Reference* the index rather than (as previously) use \CTANfile (which
+ did nothing and typeset oddly ;-)
+
+ * filectan.tex: New, the _files_ bit from newfaq.tex Added references
+ to README.uploads, TeX-index, EdMetrics, screen.sty, usergrps.tex
+
+ * dirctan.tex: Renamed from namectan.tex
+ Added a reference to TeX-index
+
+Sun Oct 16 10:28:04 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: Remove loading of package shortvrb and definition of the
+ short verb character
+ Changed layout of the path specified for the start of the CTAN archive
+ from "./tex-archive" to "tex-archive/" (and used \CTAN for reference in
+ place of \path)
+ Refer to ucthesis via its \CTANref
+ Change layout of the path reference for DECUS TeX on wuarchive (without
+ prejudice as to whether we actually want to retain the reference at
+ all, of course)
+ Quote DECUS library telephone number in the same way as all other nos
+ Correct reference to Barbara Beeton's email address
+
+ * faq.sty: Comment out the use of path.sty, all of my old stuff about
+ the CTAN labels
+ Add Alan's versions of the same... (less transmission errors)
+ Load the shortvrb package, and define | as the short verbatim character
+ _before_ using it as a delimiter for the various path-like commands
+ Similarly, make sure `@' is catcoded to `other' before defining the
+ \Email macro
+ Start \FAQverb with \leavevmode, since otherwise we might find
+ ourselves trying to change language while in vertical mode
+ Define \path in terms of \FAQverb
+
+Sat Oct 15 22:08:23 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.sty: added, then removed again, \emergencystretch
+
+Sat Oct 15 10:08:43 1994 Robin Fairbairns (robin@home)
+
+ * namectan.tex: add bibtex-doc, graphics
+
+ * newfaq.tex: editorial work on questions 2,4-9,11,12,14-19,21,24
+ Commented out the "alternative" FAQ sites (though left reference to
+ rtfm.mit.edu)
+ taken away the (sanitised) group around all the ctan directory/file
+ commands
+
+ * faq.sty: give \Qref an optional first argument (intro text, default
+ "see question")
+ make \CTANdirectory open a group, sanitise, and then call \@CTANdir
+ which is the old version of the command and then \egroup (similarly for
+ \CTANfile, with \@CTANfile)
+ make the scribble for undefined references come out in \texttt
+ lots of kerfuffle to recover the situation of the directory (etc.)
+ declarations split
+
+ * path.sty: define \@morediscreet, a version of the same as the
+ internal version of \discretionaries, except that it defines all the
+ active characters to become \relax, so that they can be \xdef'ed
+
+Fri Oct 14 22:38:58 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: change \Qref{dvi-ps} to {Q-dvips} (one or the other had
+ to change, after all)
+ second \CTANfile{unixtexftp} was really a \CTANref
+ removed original entry in the systems list for Macs, since it's been
+ superseded by Seb's new one
+ second \CTANfile{btxmactex} was in fact a \CTANref
+ (outstanding package warnings re CTANrefs are texsgi,vmspell and
+ txtdist)
+
+ * texnames.sty: made the name for SliTeX conform to the comment about
+ it (it's not a big deal now that it's dead, but lower-case `i' (as
+ opposed to small caps `i') looked really odd
+
+ * faq.sty: Added some scribble text in case of an unassigned \CTANref
+ err ... yet another instance of \makeatletter ... and another
+
+Thu Oct 12 16:00 1994 Sebastian Rahtz (s.rahtz@elsevier.co.uk)
+
+ * Removed all non-CTAN ftp references (to be put back as a table)
+
+ * changed order of questions
+
+ * added list of committee names
+
+ * made all questions statements, not questions (as per JS)
+
+ * made complete list of CTAN names (namectan.tex)
+
+Tue Oct 11 13:37:28 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.sty: add (null) definition of \checked macro
+ made \CTANfile and \CTANdirectory \gdef their reference commands, and
+ defined a \CTANsanitise command
+
+ * newfaq.tex: last two \CTANlabels become one \CTANdirectory (ispell)
+ and two \CTANfiles (VMS TeX)
+ (section{\MF{}}): mf \smode=... into a verbatim env (rather than short
+ verb)
+ (section{\TeX{} Systems}): VAX/VMS item -> VMS item (added a \checked
+ macro)
+ (section{\TeX{} Systems}): Updated the amiga stuff to point to CTAN
+ only (added a \checked macro)
+
+Fri Oct 7 15:24:29 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (throughout): more hacking at commands that split
+ themselves over lines, added {}s to the last few \LaTeXe's that needed
+ them
+ (section{\MF{}}): indent verbatim command sequences
+ (section{\TeX{} Systems}): unwrap Q-oztex \Question argument
+ (section{Documentation and Help}): use \LaTeX in Lamport's book title
+ (section{Special sorts of typesetting}): reference macmakeindex.sit
+ instead of giving an email address for Tolliver, which causes grief
+ with Alan's perl code...
+
+ * faq.sty: Add a \DANTE command, at Alan's suggestion
+
+Thu Oct 6 14:05:36 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * faq.sty: provide the commands for doing the \CTANlabel/\CTANref game
+
+ * newfaq.tex (section{Special sorts of typesetting}): Added remark
+ about the status of screenview
+ (throughout) try to ensure (as Alan requests) that all logos are
+ referenced as as \logoname{} _only_
+ (throughout) install the \CTANref mechanism for referring to existing
+ CTAN addresses
+ updated \fileversion and \filedate...
+
+Mon Oct 3 09:05:14 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{Documentation and Help}): Removed repeated TUG
+ address from PicTeX manual question (replaced with reference to TUG
+ question); then moved question down below TUG question
+ (section{\TeX{} Systems}): mailed Elizabeth Tachikawa about the Unix
+ tape service
+ (section{Documentation and Help}): mailed latex-help-coordinator about
+ LaTeX help service, but the response was "unknown user" -- deleted
+ question and answer
+ (section{Documentation and Help}): Added a question about national/
+ regional user groups
+ (section{Documentation and Help}): rationalise use of \BibTeX (in
+ particular, bibtex.1 is a _file_, not something that can reasonably
+ be expressed as a logo (why doesn't bold small caps appear in question
+ titles?)
+
+Sun Oct 2 17:14:30 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex (section{The Background}): Added body to the questions
+ What is TeX?, What is LaTeX?, why's it free?
+ (section{Introduction}): added a reference to Alan's server (even
+ though it's inevitably out of date w.r.t. this document...)
+
+Sat Oct 1 (evening) 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: significant upheaval (several new questions, fewer new
+ answers), following discussion with Jonathan;
+ add \NeedsTeXFormat requirement (should this be in faq.sty?);
+ new section The Background with some stuff moved out from Introduction,
+ containing questions What is TeX?, What is LaTeX?, should I use plain
+ or LaTeX?, why's it free?, why isn't it wysiwyg?, and what is the
+ future?;
+ Introduction completely re-written;
+ new questions in The Latest Developments, What is the NTS project?,
+ what is the LaTeX3 project?
+
+ * faq.sty: new commands for \BV, \NTS, \eTeX and \URL
+
+Thu Sep 29 12:43:52 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: lots of minor typos corrected;
+ yet more markup added;
+ one or two more of Joachim's comments addressed (but note new \Q about
+ LaTeX 2.09 and `weird hyphenatoin')
+
+ * faq.sty: load times.sty only \IfFileExists (such taste; such
+ originality)
+
+Wed Sep 28 10:23:30 1994 Robin Fairbairns (robin@home)
+
+ * newfaq.tex: modified so that all question references (that I've
+ spotted so far ;-) simply consist of a \Qref in parentheses;
+ first iteration of sticking stuff in new sections;
+ more books (well, one more) and into a new question;
+ more markup tidying (\Newsgroup, \CTAN, etc.);
+ now version 1.1, added \hfuzz and \emergencystretch
+
+ * faq.sty: (possibly merely experimental ;-) made Questions into
+ subsections, removed subsection from \cl@section, numbered sections
+ alphabetically...;
+ make \Qref produce "see question \ref{#1}"
+
+Tue Sep 27 16:10:17 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex: change to use \BibTeX instead of \BiBTeX (since the
+ latter's not one of the forms the name appears in texnames.sty;
+ refer to PiCTeX, VorTeX through their (new) logo macros;
+ similarly (though not new logos) tex->\TeX, AMS[La]TeX, LaTeX, BibTeX,
+ SliTeX;
+ correct wording describing incorporation of SliTeX into 2e (ex Joachim
+ Schrod's suggestion)
+
+ * texnames.sty: new, copied from eplain distribution, but with \PiCTeX
+ and \VorTeX added (pro tem, at least)
+
+ * faq.sty: moved the font-setting commands, etc., into the package
+
+Tue Sep 27 14:17:51 1994 Robin Fairbairns (robin@home)
+
+ * faq.sty: markup commands in separate package (ultimately to come in
+ several versions according to the environment it's to be processed in
+ -- e.g., versions for PS font usage/cm font usage, even a version for
+ processing to plain text?)
+
+ * newfaq.tex: moved all the markup commands out to (new) faq.sty;
+ couple of typos corrected following input from Joachim Schrod
+
+Thu Sep 22 09:18:38 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex: (last night's work) new-style markup for question
+ references, label for last question (so we can see how well we're
+ doing), \makeshortverb of \| so as to get coherent log output
+
+Tue Sep 20 13:54:51 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk)
+
+ * newfaq.tex: moved \documentclass, \usepackage above defs of
+ fileversion and date, so as not to pick up that from mflogo;
+ `getting a copy' - removed fileserv@shsu.bitnet, put various email
+ addresses in \Email; put NEWS.ANSWERS into more coherent form
+ (verbatim; and yes, it _does_ need to be upper case)
+ `pictex manual': escape the $s (!)
+ `oztex': it's now shareware, not PD
+ `fig and where to get it': remove escape from _ in \path (!)
+ `music': corrected email address for Taupin and his ftp site
+ `double-spacing': doublespace.sty is a file name; close paren round ref
+ to CTAN; "latest release of LaTeX"->"LaTeX2e"
+ `macros to do Y': verbatim site index command <term> in text
+ `... for machine Y running Q': FTP.nwc is a file, and yes, it is there
+ ibid, both AIX and PC made explicit reference to fpt.dante.de
+ `blackboard bold': tech-support is an email address; add reference to
+ the extraordinary bbm fonts
+ `repositories': correct address corresponding to ftp.tex.ac.uk; put
+ site index command into verbatim
+ `Laserjet': converted S's \Q about Berry's prog into an actual
+ reference to it
+ `\pagestyle{empty}': correct (;-) spelling of behaviour, "is"->"if"
+ `NFSS': rewritten to clarify relationship to New LaTeX
+ New question about things like \tenrm in 2e added
+ `references wrong': line up corrected code in two columns
+ `change margins': indent code
+ `width of letter, etc.': indent examples; remove redundant `T' from
+ LaTeX
+ `LaTeX2e': first production release was June
+ `log-like functions': indent examples
+ `\@': "?" at end of question
+ `Companion ... @': space after LaTeX in question, "!" at end
+ `I've found a bug': slight elaboration of 2.09 case
+ New version of path.sty with some hacking; redo all S's (and my one)
+ markup commands
+
+Mon Sep 19 11:46:40 1994 Robin Fairbairns (robin@home)
+
+ * define \Newsgroup (same as all the rest, pro tem) and use it for
+ comp.tex.tex, comp.unix.wizards, news.answers, comp.sources.unix,
+ comp.programming.literate, comp.sources.misc, comp.text, comp.fonts
+
+ * added new questions "what's all this about \@", "but the companion
+ tells me to use \@startsection" and "I've found a bug: what do I do"
+ (which last was a suggestion of Jonathan's)
+
+ * put \fileversion in the title (rather than \filedate twice)
+
+ * defined command \cs (out of ltxdoc.cls) so that we can put commands
+ in question names, required for q32 about \pagestyle{emtpy}
diff --git a/help/uk-tex-faq/Makefile b/help/uk-tex-faq/Makefile
new file mode 100644
index 0000000000..1345d54113
--- /dev/null
+++ b/help/uk-tex-faq/Makefile
@@ -0,0 +1,226 @@
+# define variables WEB, WEB_BETA, CGI_BIN, HOME_DIR, CTAN_HOME, CTAN_ROOT
+include locations.mk
+
+# list of subdocuments of gather-faqbody
+include subdocuments.mk
+
+BODY = gather-faqbody.tex filectan.tex dirctan.tex $(SUBDOCS)
+MACROS = faq.cls faq.sty
+CONFIGS = archive.cfg
+CMFONTS = cmz
+PATCH = newfaq-patch.tex add-general.tex add-hammond.tex
+MAKEF = Makefile
+
+HTML_TAR = FAQ-html.tar.gz
+
+LATEX = latex
+PDFLATEX = pdflatex
+
+CTAN_HOME = help/uk-tex-faq
+
+#h
+#hThe main targets of this Makefile are
+#h release build a distribution
+#h
+#h patch build latest patched version
+#h
+#h ctan install distribution on CTAN
+#h (to be run on the CTAN machine)
+#h web install files required for web access
+#h (must be run on the machine that hosts
+#h the CGI script)
+#h web-index web access files, just (dir|file)ctan
+#h web-beta as web, except beta distribution
+#h
+#h inst-perl install texfaq2html and sanitize.pl
+#h in the cgi-bin directory
+#h inst-perl-beta ditto, for texfaq2html-beta, sanitize-beta
+#h inst-perl-gamma ditto, for texfaq2html-gamma
+#h
+#h html make html files in html/
+#h html-gamma make html files in html, copy for -gamma tests
+
+help:; @sed -n 's/^#h//p' < $(MAKEF)
+
+release: all html-tar
+all: newfaq.pdf letterfaq.pdf
+
+# did have faqfont.cfg in here, but that caused problems, since it
+# typically doesn't exist...
+
+# pdf generation has to be done one a different base file name because
+# of incompatibilities in the .aux and .toc files
+newfaq.pdf: newfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ ln -sf newfaq.tex ./pdf-newfaq.tex
+ rm -f faqfont.cfg
+ while ( \
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-newfaq ; \
+ grep "Rerun to get cross" pdf-newfaq.log > /dev/null ) do true ; \
+ done
+ thumbpdf pdf-newfaq
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-newfaq
+ mv pdf-newfaq.pdf newfaq.pdf
+ rm pdf-newfaq.tex
+
+letterfaq.pdf: letterfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ ln -sf letterfaq.tex ./pdf-letterfaq.tex
+ rm -f faqfont.cfg
+ while ( \
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-letterfaq ; \
+ grep "Rerun to get cross" pdf-letterfaq.log > /dev/null ) do true ; \
+ done
+ thumbpdf pdf-letterfaq
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-letterfaq
+ mv pdf-letterfaq.pdf letterfaq.pdf
+ rm pdf-letterfaq.tex
+
+patch: newfaq-patch
+
+newfaq-patch: newfaq-patch.pdf newfaq-patch.ps
+
+patch.pdf: newfaq-patch.pdf
+
+newfaq-patch.pdf: $(PATCH) $(BODY) $(MACROS) $(CONFIGS)
+ ./find-add-files
+ ln -sf newfaq-patch.tex ./pdf-newfaq-patch.tex
+ rm -f faqfont.cfg
+ while ( \
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-newfaq-patch ; \
+ grep "Rerun to get cross" pdf-newfaq-patch.log > /dev/null ) do true ; \
+ done
+ thumbpdf pdf-newfaq-patch
+ $(PDFLATEX) \\def\\Status{1} \\input pdf-newfaq-patch
+ mv pdf-newfaq-patch.pdf newfaq-patch.pdf
+ ln -sf newfaq-patch.pdf patch.pdf
+ rm pdf-newfaq-patch.tex
+
+patch.dvi: newfaq-patch.dvi
+
+newfaq-patch.dvi: $(PATCH) $(BODY) $(MACROS) $(CONFIGS)
+ ./find-add-files
+ while ( \
+ $(LATEX) newfaq-patch ; \
+ grep "Rerun to get cross" newfaq-patch.log > /dev/null ) do true ; \
+ done
+ ln -sf newfaq-patch.dvi patch.dvi
+
+newfaq.aux: newfaq.dvi
+
+newfaq.dvi: newfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ echo $(LATEX)
+ while ( \
+ $(LATEX) newfaq ; \
+ grep "Rerun to get cross" newfaq.log > /dev/null ) do true ; \
+ done
+
+letterfaq.dvi: letterfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ while ( \
+ $(LATEX) letterfaq ; \
+ grep "Rerun to get cross" letterfaq.log > /dev/null ) do true ; \
+ done
+
+newfaq-cm.dvi: newfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ ln -sf faqfont.cfg.cmfonts faqfont.cfg
+ ln -sf newfaq.tex newfaq-cm.tex
+ while ( \
+ $(LATEX) newfaq-cm ; \
+ grep "Rerun to get cross" newfaq-cm.log > /dev/null ) do true ; \
+ done
+ rm faqfont.cfg newfaq-cm.tex
+
+letterfaq-cm.dvi: letterfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+ ln -sf faqfont.cfg.cmfonts faqfont.cfg
+ ln -sf letterfaq.tex letterfaq-cm.tex
+ while ( \
+ $(LATEX) letterfaq-cm ; \
+ grep "Rerun to get cross" letterfaq-cm.log > /dev/null ) do true ; \
+ done
+ rm faqfont.cfg letterfaq-cm.tex
+
+$(HTML_TAR):
+ tar czvf $(HTML_TAR) html/*
+
+ctan: $(HTML_TAR)
+ (cd $(CTAN_ROOT)/$(CTAN_HOME); \
+ really -u ctan make -f /home/rf/tex/faq/Makefile.CTAN)
+
+# faqbody for all the webbery stuff
+faqbody.tex: $(SUBDOCS) gather-faqbody.tex
+ ./build-faqbody
+
+web: $(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list
+
+web-index: $(WEB)/dirctan.tex $(WEB)/filectan.tex
+
+$(WEB)/dirctan.tex: dirctan.tex
+$(WEB)/filectan.tex: filectan.tex
+$(WEB)/faqbody.tex: faqbody.tex
+$(WEB)/newfaq.aux: newfaq.aux
+$(WEB)/archive.list: archive.list
+$(WEB)/aliasquestion.list: aliasquestion.list
+$(WEB)/label-to-file.pl: label-to-file.pl
+
+$(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list $(WEB)/aliasquestion.list $(WEB)/label-to-file.pl:
+ if [ -f $@ ]; then \
+ chmod 644 $@; \
+ cp -p $< $@-t; \
+ mv $@-t $@; \
+ else \
+ cp -p $< $@; \
+ fi
+ chmod 444 $@
+
+web-beta: $(WEB_BETA)/dirctan.tex $(WEB_BETA)/filectan.tex $(WEB_BETA)/faqbody.tex $(WEB_BETA)/newfaq.aux $(WEB_BETA)/archive.list $(WEB_BETA)/aliasquestion.list $(WEB_BETA)/label-to-file.pl
+
+$(WEB_BETA)/dirctan.tex: dirctan.tex
+$(WEB_BETA)/filectan.tex: filectan.tex
+$(WEB_BETA)/faqbody.tex: faqbody.tex
+$(WEB_BETA)/newfaq.aux: newfaq.aux
+$(WEB_BETA)/archive.list: archive.list
+$(WEB_BETA)/aliasquestion.list: aliasquestion.list
+$(WEB_BETA)/label-to-file.pl: label-to-file.pl
+
+$(WEB_BETA)/dirctan.tex $(WEB_BETA)/filectan.tex $(WEB_BETA)/faqbody.tex $(WEB_BETA)/newfaq.aux $(WEB_BETA)/archive.list $(WEB_BETA)/aliasquestion.list $(WEB_BETA)/label-to-file.pl:
+ if [ -f $@ ]; then \
+ chmod 644 $@; \
+ cp -p $< $@-t; \
+ mv $@-t $@; \
+ else \
+ cp -p $< $@; \
+ fi
+ chmod 444 $@
+
+inst-perl: $(CGI_BIN)/texfaq2html $(CGI_BIN)/sanitize.pl
+inst-perl-beta: $(CGI_BIN)/texfaq2html-beta $(CGI_BIN)/sanitize-beta.pl
+inst-perl-gamma: $(CGI_BIN)/texfaq2html-gamma
+
+$(CGI_BIN)/texfaq2html: $(HOME_DIR)/texfaq2html
+$(CGI_BIN)/texfaq2html-beta: $(HOME_DIR)/texfaq2html-beta
+$(CGI_BIN)/texfaq2html-gamma: $(HOME_DIR)/texfaq2html-gamma
+$(CGI_BIN)/sanitize.pl: $(HOME_DIR)/sanitize.pl
+$(CGI_BIN)/sanitize-beta.pl: $(HOME_DIR)/sanitize-beta.pl
+
+$(CGI_BIN)/texfaq2html $(CGI_BIN)/texfaq2html-beta $(CGI_BIN)/texfaq2html-gamma $(CGI_BIN)/sanitize.pl $(CGI_BIN)/sanitize-beta.pl:
+# co -l $@
+ cp -p $? $@
+# ci -u -m"automatic check-in" $@
+
+html: $(HTMLDIR)/index.html
+
+$(HTMLDIR)/index.html: $(BODY) newfaq.aux faqbody.tex
+ ./texfaq2file
+
+html-tar: html
+ tar czf FAQ-html.tar.gz $(HTMLDIREL)/
+
+html-gamma: $(HTMLDIR_GAMMA)/index.html
+
+$(HTMLDIR_GAMMA)/index.html: $(BODY) newfaq.aux faqbody.tex
+ ./texfaq2file -2 -w
+ cp -p $(HTMLDIR_GAMMA)/* $(GAMMADIR)/
+
+clean:
+ rm -f *.pdf *.dvi *.log *.bak *.toc *.out *.lab *.tpt *.png
+ rm -f *.aux html/*.html html_gamma/*.html htmltext/*.txt
+ rm -f pdf-newfaq*.tex comment.cut additions.tex aliasquestion.list
+ rm -f faqbody.tex FAQ-html.tar.gz
diff --git a/help/uk-tex-faq/Makefile-CTAN b/help/uk-tex-faq/Makefile-CTAN
new file mode 100644
index 0000000000..52912fb5fc
--- /dev/null
+++ b/help/uk-tex-faq/Makefile-CTAN
@@ -0,0 +1,103 @@
+# this file is auto-generated; edit mk-makefile, not this
+
+/anfs/ctan/tex-archive/help/uk-tex-faq/ChangeLog: ChangeLog
+/anfs/ctan/tex-archive/help/uk-tex-faq/Makefile: Makefile
+/anfs/ctan/tex-archive/help/uk-tex-faq/README: README
+/anfs/ctan/tex-archive/help/uk-tex-faq/dirctan.tex: dirctan.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq.cls: faq.cls
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq.sty: faq.sty
+/anfs/ctan/tex-archive/help/uk-tex-faq/filectan.tex: filectan.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/gather-faqbody.tex: gather-faqbody.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/letterfaq.tex: letterfaq.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/archive.cfg: archive.cfg
+/anfs/ctan/tex-archive/help/uk-tex-faq/markup-syntax: markup-syntax
+/anfs/ctan/tex-archive/help/uk-tex-faq/newfaq.tex: newfaq.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/letterfaq.pdf: letterfaq.pdf
+/anfs/ctan/tex-archive/help/uk-tex-faq/newfaq.pdf: newfaq.pdf
+/anfs/ctan/tex-archive/help/uk-tex-faq/faqfont.cfg.cmfonts: faqfont.cfg.cmfonts
+/anfs/ctan/tex-archive/help/uk-tex-faq/FAQ-html.tar.gz: FAQ-html.tar.gz
+/anfs/ctan/tex-archive/help/uk-tex-faq/CHANGES-3.25: CHANGES-3.25
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-adj-types.tex: faq-adj-types.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-backgrnd.tex: faq-backgrnd.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-biblio.tex: faq-biblio.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-bits+pieces.tex: faq-bits+pieces.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-docs.tex: faq-docs.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-dvi.tex: faq-dvi.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-fmt-conv.tex: faq-fmt-conv.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-fonts.tex: faq-fonts.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-getit.tex: faq-getit.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-graphics.tex: faq-graphics.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-how-do-i.tex: faq-how-do-i.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp+pdf-1.tex: faq-hyp+pdf-1.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp+pdf.tex: faq-hyp+pdf.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp-pdf-rev.tex: faq-hyp-pdf-rev.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-images.tex: faq-images.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-install.tex: faq-install.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-intro.tex: faq-intro.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-jot-err.tex: faq-jot-err.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-lab-ref.tex: faq-lab-ref.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-litprog.tex: faq-litprog.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-mac-prog.tex: faq-mac-prog.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-projects.tex: faq-projects.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-support.tex: faq-support.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-symbols.tex: faq-symbols.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-t-g-wr.tex: faq-t-g-wr.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-texsys.tex: faq-texsys.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-the-end.tex: faq-the-end.tex
+/anfs/ctan/tex-archive/help/uk-tex-faq/faq-wdidt.tex: faq-wdidt.tex
+
+TARGETS = \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/ChangeLog \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/Makefile \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/README \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/dirctan.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq.cls \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq.sty \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/filectan.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/gather-faqbody.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/letterfaq.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/archive.cfg \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/markup-syntax \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/newfaq.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/letterfaq.pdf \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/newfaq.pdf \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faqfont.cfg.cmfonts \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/FAQ-html.tar.gz \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-adj-types.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-backgrnd.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-biblio.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-bits+pieces.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-docs.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-dvi.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-fmt-conv.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-fonts.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-getit.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-graphics.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-how-do-i.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp+pdf-1.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp+pdf.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-hyp-pdf-rev.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-images.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-install.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-intro.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-jot-err.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-lab-ref.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-litprog.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-mac-prog.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-projects.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-support.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-symbols.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-t-g-wr.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-texsys.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-the-end.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/faq-wdidt.tex \
+ /anfs/ctan/tex-archive/help/uk-tex-faq/CHANGES-3.25
+
+all: $(TARGETS)
+ echo $^
+ if [ -f $^ ]; then \
+ /anfs/ctan-maint/install/ctan_install -replace -silent -nozip $(F^) help/uk-tex-faq/$(F^); \
+ else \
+ /anfs/ctan-maint/install/ctan_install -new -silent $(F^) help/uk-tex-faq/$(F^); \
+ fi
+
diff --git a/help/uk-tex-faq/README b/help/uk-tex-faq/README
new file mode 100644
index 0000000000..1f452b06e0
--- /dev/null
+++ b/help/uk-tex-faq/README
@@ -0,0 +1,34 @@
+ The UK TeX FAQ
+
+1. Origins and maintenance
+
+This FAQ was started as a committee effort by the UK TeX Users' Group.
+
+If you wish to offer help, or to comment on the content of the FAQ,
+please mail faq-devel@tex.ac.uk
+
+2. Licence
+
+The source of the FAQ itself and its derived products (human-readable
+versions presented as DVI, PostScript, Adobe Acrobat and HTML) are
+placed in the public domain.
+
+You are permitted (nay, encouraged) to distribute the FAQ as widely as
+you like. Please be careful to keep your copy of the FAQ up-to-date:
+it's possible to mirror the FAQ's directory on CTAN, or to watch the
+CTAN announcements mailing list (see the "answer" on mailing lists in
+the FAQ itself).
+
+Further, you are urged to be very careful about modifying the FAQ:
+
+- the source and its relationship to the macros that support it, and
+ to the dubious Perl scripts that create HTML versions, is extremely
+ fragile; so changes are likely to be tricky to "get right"
+
+- there's a positive danger in publishing un-reviewed advice,
+ particularly if it claims to come from a usually reliable source.
+
+Therefore, if you do have changes to make, please consider submitting
+them to faq-devel@tex.ac.uk at least in parallel with making changes
+to your own copy. A statement that details what you've done, in your
+copy of the FAQ, is particularly useful.
diff --git a/help/uk-tex-faq/archive.cfg b/help/uk-tex-faq/archive.cfg
new file mode 100644
index 0000000000..0d998ea78c
--- /dev/null
+++ b/help/uk-tex-faq/archive.cfg
@@ -0,0 +1,13 @@
+% this file is loaded by the {file,dir}ctan files to define the local
+% preferred archive and directory compression format
+
+%
+% the archive itself
+\def\LocalCTAN{http://mirror.ctan.org/} % could be anything
+ % out of CTAN.sites
+%
+% the format for use when retrieving directory hierarchies
+\def\CTANDirFmt{.zip} % could be .(tar[.(Z|gz)]|tgz|zip) according to what
+ % the local archive is capable of and the users need
+
+\endinput
diff --git a/help/uk-tex-faq/dirctan.tex b/help/uk-tex-faq/dirctan.tex
new file mode 100644
index 0000000000..00f797453a
--- /dev/null
+++ b/help/uk-tex-faq/dirctan.tex
@@ -0,0 +1,990 @@
+% $Id: dirctan.tex,v 1.302 2013/07/24 21:43:10 rf10 Exp rf10 $
+%
+% protect ourself against being read twice
+\csname readCTANdirs\endcsname
+\let\readCTANdirs\endinput
+%
+% declarations of significant directories on CTAN
+\CTANdirectory{2etools}{macros/latex/required/tools}[tools]
+\CTANdirectory{4spell}{support/4spell}[fourspell]
+\CTANdirectory*{Catalogue}{help/Catalogue}
+\CTANdirectory*{MathTeX}{support/mathtex}[mathtex]
+\CTANdirectory{MimeTeX}{support/mimetex}[mimetex]
+\CTANdirectory{Tabbing}{macros/latex/contrib/Tabbing}[tabbing]
+\CTANdirectory*{TeXtelmExtel}{systems/msdos/emtex-contrib/TeXtelmExtel}
+\CTANdirectory{TftI}{info/impatient}[impatient]
+\CTANdirectory{a0poster}{macros/latex/contrib/a0poster}[a0poster]
+\CTANdirectory*{a2ping}{graphics/a2ping}[a2ping]
+\CTANdirectory{a4}{macros/latex/contrib/a4}[a4]
+\CTANdirectory*{abc2mtex}{support/abc2mtex}
+\CTANdirectory{abstract}{macros/latex/contrib/abstract}[abstract]
+\CTANdirectory{abstyles}{biblio/bibtex/contrib/abstyles}
+\CTANdirectory{accents}{support/accents}
+\CTANdirectory{acronym}{macros/latex/contrib/acronym}[acronym]
+\CTANdirectory*{ada}{web/ada/aweb}
+\CTANdirectory{addindex}{indexing/addindex}
+\CTANdirectory{addlines}{macros/latex/contrib/addlines}[addlines]
+\CTANdirectory{adjkerns}{fonts/utilities/adjkerns}
+\CTANdirectory{ae}{fonts/ae}[ae]
+\CTANdirectory{aeguill}{macros/latex/contrib/aeguill}[aeguill]
+\CTANdirectory{afmtopl}{fonts/utilities/afmtopl}
+\CTANdirectory{akletter}{macros/latex/contrib/akletter}
+\CTANdirectory{aleph}{systems/aleph}
+\CTANdirectory{alg}{macros/latex/contrib/alg}
+\CTANdirectory{algorithm2e}{macros/latex/contrib/algorithm2e}[algorithm2e]
+\CTANdirectory{algorithmicx}{macros/latex/contrib/algorithmicx}[algorithmicx]
+\CTANdirectory{algorithms}{macros/latex/contrib/algorithms}[algorithms]
+\CTANdirectory*{alpha}{systems/mac/support/alpha}[alpha]
+\CTANdirectory{amiga}{systems/amiga}
+\CTANdirectory{amscls}{macros/latex/required/amslatex/amscls}[amscls]
+\CTANdirectory{amsfonts}{fonts/amsfonts}[amsfonts]
+\CTANdirectory{amslatex}{macros/latex/required/amslatex}[amslatex]
+\CTANdirectory{amslatex-primer}{info/amslatex/primer}[amslatex-primer]
+\CTANdirectory{amspell}{support/amspell}
+\CTANdirectory{amsrefs}{macros/latex/contrib/amsrefs}[amsrefs]
+\CTANdirectory{amstex}{macros/amstex}[amstex]
+\CTANdirectory{anonchap}{macros/latex/contrib/anonchap}[anonchap]
+\CTANdirectory{answers}{macros/latex/contrib/answers}[answers]
+\CTANdirectory{ant}{systems/ant}[ant]
+\CTANdirectory{anyfontsize}{macros/latex/contrib/anyfontsize}[anyfontsize]
+\CTANdirectory{apl}{fonts/apl}
+\CTANdirectory{aplweb}{web/apl/aplweb}
+\CTANdirectory{appl}{web/reduce/rweb/appl}
+\CTANdirectory{appendix}{macros/latex/contrib/appendix}[appendix]
+\CTANdirectory{arabtex}{language/arabic/arabtex}
+\CTANdirectory{arara}{support/arara}[arara]
+\CTANdirectory{aro-bend}{info/challenges/aro-bend}[aro-bend]
+\CTANdirectory{asana-math}{fonts/Asana-Math}[asana-math]
+\CTANdirectory{asc2tex}{systems/msdos/asc2tex}
+\CTANdirectory{ascii}{fonts/ascii}
+\CTANdirectory*{aspell}{support/aspell}[aspell]
+\CTANdirectory{astro}{fonts/astro}
+\CTANdirectory{asymptote}{graphics/asymptote}[asymptote]
+\CTANdirectory{asyfig}{macros/latex/contrib/asyfig}[asyfig]
+\CTANdirectory{atari}{systems/atari}
+\CTANdirectory*{atari-cstex}{systems/atari/cs-tex}[atari-cstex]
+\CTANdirectory{attachfile}{macros/latex/contrib/attachfile}
+\CTANdirectory*{auctex}{support/auctex}[auctex]
+\CTANdirectory{autolatex}{support/autolatex}
+\CTANdirectory{auto-pst-pdf}{macros/latex/contrib/auto-pst-pdf}[auto-pst-pdf]
+\CTANdirectory{aweb}{web/ada/aweb}
+\CTANdirectory*{awk}{web/spiderweb/src/awk}
+\CTANdirectory{axodraw}{graphics/axodraw}[axodraw]
+\CTANdirectory{babel}{macros/latex/required/babel}[babel]
+\CTANdirectory{babelbib}{biblio/bibtex/contrib/babelbib}[babelbib]
+\CTANdirectory{badge}{macros/plain/contrib/badge}
+\CTANdirectory{bakoma}{fonts/cm/ps-type1/bakoma}[bakoma-fonts]
+\CTANdirectory*{bakoma-tex}{systems/win32/bakoma}[bakoma]
+\CTANdirectory*{bakoma-texfonts}{systems/win32/bakoma/fonts}
+\CTANdirectory*{bard}{fonts/bard}
+\CTANdirectory{barr}{macros/generic/diagrams/barr}
+\CTANdirectory{bashkirian}{fonts/cyrillic/bashkirian}
+\CTANdirectory{basix}{macros/generic/basix}
+\CTANdirectory{bbding}{fonts/bbding}
+\CTANdirectory{bbfig}{support/bbfig}
+\CTANdirectory{bbm}{fonts/cm/bbm}[bbm]
+\CTANdirectory{bbm-macros}{macros/latex/contrib/bbm}[bbm-macros]
+\CTANdirectory{bbold}{fonts/bbold}[bbold]
+\CTANdirectory{bdfchess}{fonts/chess/bdfchess}
+\CTANdirectory{beamer}{macros/latex/contrib/beamer}[beamer]
+\CTANdirectory{beamerposter}{macros/latex/contrib/beamerposter}[beamerposter]
+\CTANdirectory{beebe}{dviware/beebe}
+\CTANdirectory{belleek}{fonts/belleek}[belleek]
+\CTANdirectory{beton}{macros/latex/contrib/beton}[beton]
+\CTANdirectory{bezos}{macros/latex/contrib/bezos}[bezos]
+\CTANdirectory{bib-fr}{biblio/bibtex/contrib/bib-fr}
+\CTANdirectory{bib2dvi}{biblio/bibtex/utils/bib2dvi}
+\CTANdirectory{bib2xhtml}{biblio/bibtex/utils/bib2xhtml}
+\CTANdirectory*{bibcard}{biblio/bibtex/utils/bibcard}
+\CTANdirectory*{bibclean}{biblio/bibtex/utils/bibclean}
+\CTANdirectory*{bibdb}{support/bibdb}
+\CTANdirectory{biber}{biblio/biber}[biber]
+\CTANdirectory{bibextract}{biblio/bibtex/utils/bibextract}
+\CTANdirectory{bibgerm}{biblio/bibtex/contrib/germbib}
+\CTANdirectory{bibindex}{biblio/bibtex/utils/bibindex}
+\CTANdirectory{biblatex}{macros/latex/contrib/biblatex}[biblatex]
+\CTANdirectory*{biblatex-contrib}{macros/latex/contrib/biblatex-contrib}
+\CTANdirectory{biblio}{info/biblio}
+\CTANdirectory{biblist}{macros/latex209/contrib/biblist}
+\CTANdirectory{bibsort}{biblio/bibtex/utils/bibsort}
+\CTANdirectory{bibtex}{biblio/bibtex/base}[bibtex]
+\CTANdirectory*{bibtex8}{biblio/bibtex/8-bit}[bibtex8bit]
+\CTANdirectory{bibtex-doc}{biblio/bibtex/contrib/doc}[bibtex]
+\CTANdirectory{bibtool}{biblio/bibtex/utils/bibtool}
+\CTANdirectory{bibtools}{biblio/bibtex/utils/bibtools}
+\CTANdirectory{bibtopic}{macros/latex/contrib/bibtopic}[bibtopic]
+\CTANdirectory{bibunits}{macros/latex/contrib/bibunits}[bibunits]
+\CTANdirectory{bibview}{biblio/bibtex/utils/bibview}
+\CTANdirectory{bigfoot}{macros/latex/contrib/bigfoot}[bigfoot]
+\CTANdirectory{bigstrut}{macros/latex/contrib/multirow}[bigstrut]
+\CTANdirectory{bit2spr}{graphics/bit2spr}
+\CTANdirectory{black}{fonts/cm/utilityfonts/black}
+\CTANdirectory{blackboard}{info/symbols/blackboard}[blackboard]
+\CTANdirectory{blackletter}{fonts/blackletter}
+\CTANdirectory{blindtext}{macros/latex/contrib/blindtext}[blindtext]
+\CTANdirectory{blocks}{macros/text1/blocks}
+\CTANdirectory{blu}{macros/blu}
+\CTANdirectory{bm2font}{graphics/bm2font}
+\CTANdirectory{boites}{macros/latex/contrib/boites}[boites]
+\CTANdirectory{bold}{fonts/cm/mf-extra/bold}
+\CTANdirectory{bold-extra}{macros/latex/contrib/bold-extra}[bold-extra]
+\CTANdirectory{bonus}{systems/msdos/emtex-contrib/bonus}
+\CTANdirectory{booktabs}{macros/latex/contrib/booktabs}[booktabs]
+\CTANdirectory{boondox}{fonts/boondox}[boondox]
+\CTANdirectory{borceux}{macros/generic/diagrams/borceux}
+\CTANdirectory{braket}{macros/latex/contrib/braket}[braket]
+\CTANdirectory{breakurl}{macros/latex/contrib/breakurl}[breakurl]
+\CTANdirectory{bridge}{macros/plain/contrib/bridge}
+\CTANdirectory{brief_t}{support/brief_t}
+\CTANdirectory{bst}{biblio/bibtex/contrib/germbib/bst}
+\CTANdirectory{btable}{macros/plain/contrib/btable}
+\CTANdirectory{btex8fmt}{macros/generic/cptex/btex8fmt}
+\CTANdirectory{btOOL}{biblio/bibtex/utils/btOOL}
+\CTANdirectory{bundledoc}{support/bundledoc}[bundledoc]
+\CTANdirectory{c}{web/spiderweb/src/c}
+\CTANdirectory{c++}{web/spiderweb/src/c++}
+\CTANdirectory{c++2latex}{support/C++2LaTeX-1_1pl1}
+\CTANdirectory{c2cweb}{web/c_cpp/c2cweb}
+\CTANdirectory{c2latex}{support/c2latex}
+\CTANdirectory{c_cpp}{web/c_cpp}
+\CTANdirectory{caesar-fonts-generic.dir}{macros/generic/caesarcm/caesar-fonts-generic.dir}
+\CTANdirectory{caesarcm}{macros/generic/caesarcm}
+\CTANdirectory{caesarcmfonts.dir}{macros/generic/caesarcm/caesarcmfonts.dir}
+\CTANdirectory{caesarcmv2.dir}{macros/generic/caesarcm/caesarcmv2.dir}
+\CTANdirectory{calendar}{macros/plain/contrib/calendar}
+\CTANdirectory{calligra}{fonts/calligra}
+\CTANdirectory{calrsfs}{macros/latex/contrib/calrsfs}
+\CTANdirectory{cancel}{macros/latex/contrib/cancel}[cancel]
+\CTANdirectory{capt-of}{macros/latex/contrib/capt-of}[capt-of]
+\CTANdirectory{caption}{macros/latex/contrib/caption}[caption]
+\CTANdirectory{carlisle}{macros/latex/contrib/carlisle}[carlisle]
+\CTANdirectory{cascover}{macros/plain/contrib/cascover}
+\CTANdirectory{casslbl}{macros/plain/contrib/casslbl}
+\CTANdirectory{catdvi}{dviware/catdvi}[catdvi]
+\CTANdirectory{ccaption}{macros/latex/contrib/ccaption}[ccaption]
+\CTANdirectory{ccfonts}{macros/latex/contrib/ccfonts}[ccfonts]
+\CTANdirectory{cellular}{macros/plain/contrib/cellular}
+\CTANdirectory{cellspace}{macros/latex/contrib/cellspace}[cellspace]
+\CTANdirectory{changebar}{macros/latex/contrib/changebar}[changebar]
+\CTANdirectory{changepage}{macros/latex/contrib/changepage}[changepage]
+\CTANdirectory{changes}{macros/latex/contrib/changes}[changes]
+\CTANdirectory{chappg}{macros/latex/contrib/chappg}[chappg]
+\CTANdirectory{chapterfolder}{macros/latex/contrib/chapterfolder}[chapterfolder]
+\CTANdirectory{charconv}{support/charconv}
+\CTANdirectory{charter}{fonts/charter}
+\CTANdirectory{chbar}{macros/plain/contrib/chbar}
+\CTANdirectory{chbars}{macros/latex209/contrib/chbars}
+\CTANdirectory{check}{support/check}
+\CTANdirectory{chemstruct}{macros/latex209/contrib/chemstruct}
+\CTANdirectory{chemtex}{macros/latex209/contrib/chemtex}
+\CTANdirectory{cheq}{fonts/chess/cheq}
+\CTANdirectory{cherokee}{fonts/cherokee}
+\CTANdirectory{chesstools}{support/chesstools}
+\CTANdirectory{chi2tex}{support/chi2tex}
+\CTANdirectory{china2e}{macros/latex/contrib/china2e}
+\CTANdirectory{chinese}{language/chinese}
+\CTANdirectory{chngcntr}{macros/latex/contrib/chngcntr}[chngcntr]
+\CTANdirectory{circ}{macros/generic/diagrams/circ}
+\CTANdirectory{circuit_macros}{graphics/circuit_macros}
+\CTANdirectory{cirth}{fonts/cirth}
+\CTANdirectory{cite}{macros/latex/contrib/cite}[cite]
+\CTANdirectory{citeref}{macros/latex/contrib/citeref}[citeref]
+\CTANdirectory{clark}{fonts/utilities/afmtopl/clark}
+\CTANdirectory{classico}{fonts/urw/classico}[classico]
+\CTANdirectory{clrscode}{macros/latex/contrib/clrscode}[clrscode]
+\CTANdirectory{cm}{fonts/cm}
+\CTANdirectory{cm-lgc}{fonts/ps-type1/cm-lgc}[cm-lgc]
+\CTANdirectory{cm-super}{fonts/ps-type1/cm-super}[cm-super]
+\CTANdirectory{cm-unicode}{fonts/cm-unicode}[cm-unicode]
+\CTANdirectory{cmactex}{systems/mac/cmactex}[cmactex]
+\CTANdirectory{cmap}{macros/latex/contrib/cmap}
+\CTANdirectory{cmastro}{fonts/cmastro}
+\CTANdirectory{cmbright}{fonts/cmbright}[cmbright]
+\CTANdirectory{cmcyralt}{macros/latex/contrib/cmcyralt}
+%[fonts/cmcyralt]
+\CTANdirectory{cmfrak}{fonts/gothic/cmfrak}
+\CTANdirectory{cmoefont}{fonts/cmoefont}
+\CTANdirectory{cmolddig}{fonts/cmolddig}
+\CTANdirectory{cmoutlines}{fonts/cm/cmoutlines}[cmoutlines]
+\CTANdirectory{cmpica}{fonts/cmpica}
+\CTANdirectory{cms_help_files}{macros/text1/cms_help_files}
+\CTANdirectory{cmtest}{fonts/cm/cmtest}
+\CTANdirectory{cnoweb}{web/c_cpp/cnoweb}
+\CTANdirectory{collref}{macros/latex/contrib/collref}
+\CTANdirectory{combine}{macros/latex/contrib/combine}[combine]
+\CTANdirectory{commado}{macros/generic/commado}[commado]
+\CTANdirectory{comment}{macros/latex/contrib/comment}[comment]
+\CTANdirectory{committee}{fonts/unsupported/committee}
+\CTANdirectory{comp-fonts-FAQ}{help/comp-fonts-FAQ}
+\CTANdirectory{components-of-TeX}{info/components-of-TeX}
+\CTANdirectory{compugraphics_8600}{macros/text1/compugraphics_8600}
+\CTANdirectory{concmath}{macros/latex/contrib/concmath}[concmath]
+\CTANdirectory{concmath-f}{fonts/concmath}[concmath-fonts]
+\CTANdirectory{concrete}{fonts/concrete}[concrete]
+\CTANdirectory{context}{macros/context/current}[context]
+\CTANdirectory{context-contrib}{macros/context/contrib}
+\CTANdirectory{cprotect}{macros/latex/contrib/cprotect}[cprotect]
+\CTANdirectory{cptex}{macros/generic/cptex}
+\CTANdirectory{crop}{macros/latex/contrib/crop}[crop]
+\CTANdirectory*{crosstex}{biblio/crosstex}[crosstex]
+\CTANdirectory{crosswrd}{macros/latex/contrib/crosswrd}
+\CTANdirectory{crudetype}{dviware/crudetype}[crudetype]
+\CTANdirectory{crw}{macros/plain/contrib/crw}
+\CTANdirectory{cs-tex}{systems/atari/cs-tex}
+\CTANdirectory{csvsimple}{macros/latex/contrib/csvsimple}[csvsimple]
+\CTANdirectory{ctable}{macros/latex/contrib/ctable}[ctable]
+\CTANdirectory{ctan}{help/ctan}
+\CTANdirectory{cun}{fonts/cun}
+\CTANdirectory{currfile}{macros/latex/contrib/currfile}[currfile]
+\CTANdirectory{currvita}{macros/latex/contrib/currvita}[currvita]
+\CTANdirectory{curve}{macros/latex/contrib/curve}[curve]
+\CTANdirectory{curves}{macros/latex/contrib/curves}
+\CTANdirectory{custom-bib}{macros/latex/contrib/custom-bib}[custom-bib]
+\CTANdirectory{cutwin}{macros/latex/contrib/cutwin}[cutwin]
+\CTANdirectory{cweb}{web/c_cpp/cweb}
+\CTANdirectory{cweb-p}{web/c_cpp/cweb-p}
+\CTANdirectory{cypriote}{fonts/cypriote}
+\CTANdirectory{cyrillic}{language/cyrillic}
+\CTANdirectory{cyrtug}{language/cyrtug}
+\CTANdirectory{dante}{usergrps/dante}
+\CTANdirectory{dante-faq}{help/de-tex-faq}
+\CTANdirectory{databases}{biblio/bibtex/databases}
+\CTANdirectory{datatool}{macros/latex/contrib/datatool}[datatool]
+\CTANdirectory{datetime}{macros/latex/contrib/datetime}
+\CTANdirectory{db2tex}{support/db2tex}
+\CTANdirectory{dblfloatfix}{macros/latex/contrib/dblfloatfix}[dblfloatfix]
+\CTANdirectory{dbtex}{support/dbtex}
+\CTANdirectory{dc-latex}{language/hyphen-accent/dc-latex}
+\CTANdirectory{dc-nfss}{language/hyphen-accent/dc-nfss}
+\CTANdirectory{detex}{support/detex}[detex]
+\CTANdirectory{devanagari}{language/devanagari}
+\CTANdirectory{diagbox}{macros/latex/contrib/diagbox}[diagbox]
+\CTANdirectory{diagrams}{macros/generic/diagrams}
+\CTANdirectory{dijkstra}{web/spiderweb/src/dijkstra}
+\CTANdirectory{dinbrief}{macros/latex/contrib/dinbrief}
+\CTANdirectory{dingbat}{fonts/dingbat}
+\CTANdirectory{djgpp}{systems/msdos/djgpp}
+\CTANdirectory{dk-bib}{biblio/bibtex/contrib/dk-bib}
+\CTANdirectory{dktools}{support/dktools}[dktools]
+\CTANdirectory{dm-latex}{language/hyphen-accent/dm-latex}
+\CTANdirectory{dm-plain}{language/hyphen-accent/dm-plain}
+\CTANdirectory{doc2sty}{language/swedish/slatex/doc2sty}
+\CTANdirectory{docmfp}{macros/latex/contrib/docmfp}[docmfp]
+\CTANdirectory{docmute}{macros/latex/contrib/docmute}[docmute]
+\CTANdirectory{docu}{support/makeprog/docu}
+\CTANdirectory{document}{biblio/bibtex/contrib/germbib/document}
+\CTANdirectory{dos-dc}{systems/msdos/dos-dc}
+\CTANdirectory{dos-psfonts}{systems/msdos/emtex-fonts/psfonts}
+\CTANdirectory{doublestroke}{fonts/doublestroke}[doublestroke]
+\CTANdirectory{dowith}{macros/generic/dowith}[dowith]
+\CTANdirectory{dpfloat}{macros/latex/contrib/dpfloat}[dpfloat]
+\CTANdirectory{dpmigcc}{systems/msdos/dpmigcc}
+\CTANdirectory{draftcopy}{macros/latex/contrib/draftcopy}[draftcopy]
+\CTANdirectory{draftwatermark}{macros/latex/contrib/draftwatermark}[draftwatermark]
+\CTANdirectory{dratex}{graphics/dratex}[dratex]
+\CTANdirectory{drawing}{graphics/drawing}
+\CTANdirectory{dropcaps}{macros/latex209/contrib/dropcaps}
+\CTANdirectory{dropping}{macros/latex/contrib/dropping}[dropping]
+\CTANdirectory{dtl}{dviware/dtl}[dtl]
+\CTANdirectory{dtxgen}{support/dtxgen}[dtxgen]
+\CTANdirectory{dtxtut}{info/dtxtut}[dtxtut]
+\CTANdirectory{duerer}{fonts/duerer}
+\CTANdirectory{dvgt}{dviware/dvgt}
+\CTANdirectory{dvi-augsburg}{dviware/dvi-augsburg}
+\CTANdirectory{dvi2bitmap}{dviware/dvi2bitmap}[dvi2bitmap]
+\CTANdirectory{dvi2pcl}{dviware/dvi2pcl}
+\CTANdirectory{dvi2tty}{dviware/dvi2tty}[dvi2tty]
+\CTANdirectory{dviasm}{dviware/dviasm}[dviasm]
+\CTANdirectory{dvibit}{dviware/dvibit}
+\CTANdirectory{dvibook}{dviware/dvibook}
+\CTANdirectory{dvichk}{dviware/dvichk}
+\CTANdirectory{dvicopy}{dviware/dvicopy}
+\CTANdirectory{dvidjc}{dviware/dvidjc}
+\CTANdirectory{dvidvi}{dviware/dvidvi}
+\CTANdirectory{dviimp}{dviware/dviimp}
+\CTANdirectory{dviljk}{dviware/dviljk}
+\CTANdirectory{dvimerge}{dviware/dvimerge}
+\CTANdirectory{dvimfj}{systems/msdos/emtex-contrib/dvimfj}
+\CTANdirectory{dvipage}{dviware/dvipage}
+\CTANdirectory{dvipaste}{dviware/dvipaste}
+\CTANdirectory{dvipdfm}{dviware/dvipdfm}
+\CTANdirectory{dvipdfmx}{dviware/dvipdfmx}[dvipdfmx]
+\CTANdirectory{dvipj}{dviware/dvipj}
+\CTANdirectory{dvipng}{dviware/dvipng}[dvipng]
+\CTANdirectory{dvips-pc}{systems/msdos/dviware/dvips}
+\CTANdirectory{dvips}{dviware/dvips}[dvips]
+\CTANdirectory{dvistd}{dviware/driv-standard}
+\CTANdirectory{dvisun}{dviware/dvisun}
+\CTANdirectory{dvitty}{dviware/dvitty}
+\CTANdirectory{dvivga}{dviware/dvivga}
+\CTANdirectory{e4t}{systems/msdos/e4t}
+\CTANdirectory*{e-TeX}{systems/e-tex}
+\CTANdirectory{easytex}{systems/msdos/easytex}
+\CTANdirectory{ebib}{biblio/bibtex/utils/ebib}
+\CTANdirectory{ec}{fonts/ec}[ec]
+\CTANdirectory{ec-plain}{macros/ec-plain}[ec-plain]
+\CTANdirectory{eco}{fonts/eco}[eco]
+\CTANdirectory{economic}{biblio/bibtex/contrib/economic}
+\CTANdirectory{edmac}{macros/plain/contrib/edmac}[edmac]
+\CTANdirectory{ednotes}{macros/latex/contrib/ednotes}[ednotes]
+\CTANdirectory{eepic}{macros/latex/contrib/eepic}[eepic]
+\CTANdirectory{ega2mf}{fonts/utilities/ega2mf}
+\CTANdirectory{egplot}{macros/latex/contrib/egplot}[egplot]
+\CTANdirectory{eiad}{fonts/eiad}
+\CTANdirectory{elvish}{fonts/elvish}
+\CTANdirectory{elwell}{fonts/utilities/afmtopl/elwell}
+\CTANdirectory{emp}{macros/latex/contrib/emp}[emp]
+\CTANdirectory{emptypage}{macros/latex/contrib/emptypage}[emptypage]
+\CTANdirectory{emt2tex}{systems/msdos/emtex-contrib/emt2tex}
+\CTANdirectory{emtex}{systems/msdos/emtex}
+\CTANdirectory{emtex-contrib}{systems/msdos/emtex-contrib}
+\CTANdirectory{emtex-fonts}{systems/msdos/emtex-fonts}
+\CTANdirectory{emtextds}{obsolete/systems/os2/emtex-contrib/emtexTDS}
+\CTANdirectory{enctex}{systems/enctex}[enctex]
+\CTANdirectory{endfloat}{macros/latex/contrib/endfloat}[endfloat]
+\CTANdirectory{english}{language/english}
+\CTANdirectory{engwar}{fonts/engwar}
+\CTANdirectory{enumitem}{macros/latex/contrib/enumitem}[enumitem]
+\CTANdirectory{environment}{support/lsedit/environment}
+\CTANdirectory{epic}{macros/latex/contrib/epic}[epic]
+\CTANdirectory{epigraph}{macros/latex/contrib/epigraph}[epigraph]
+\CTANdirectory{eplain}{macros/eplain}[eplain]
+\CTANdirectory{epmtex}{systems/os2/epmtex}
+\CTANdirectory{epslatex}{info/epslatex}[epslatex]
+\CTANdirectory*{epstopdf}{support/epstopdf}[epstopdf]
+\CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox}[eqparbox]
+\CTANdirectory{ergotex}{systems/msdos/ergotex}
+\CTANdirectory{errata}{systems/knuth/dist/errata}
+\CTANdirectory{eso-pic}{macros/latex/contrib/eso-pic}[eso-pic]
+\CTANdirectory{et}{support/et}
+\CTANdirectory{etex}{systems/e-tex}[etex]
+\CTANdirectory{etex-pkg}{macros/latex/contrib/etex-pkg}[etex-pkg]
+\CTANdirectory{etextools}{macros/latex/contrib/etextools}[etextools]
+\CTANdirectory{ethiopia}{language/ethiopia}
+\CTANdirectory{ethtex}{language/ethiopia/ethtex}
+\CTANdirectory{etoc}{macros/latex/contrib/etoc}[etoc]
+\CTANdirectory{etoolbox}{macros/latex/contrib/etoolbox}[etoolbox]
+\CTANdirectory{euler-latex}{macros/latex/contrib/euler}[euler]
+\CTANdirectory{eulervm}{fonts/eulervm}[eulervm]
+\CTANdirectory{euro-ce}{fonts/euro-ce}[euro-ce]
+\CTANdirectory{euro-fonts}{fonts/euro}
+\CTANdirectory{eurofont}{macros/latex/contrib/eurofont}[eurofont]
+\CTANdirectory{europecv}{macros/latex/contrib/europecv}[europecv]
+\CTANdirectory{eurosym}{fonts/eurosym}[eurosym]
+\CTANdirectory{everypage}{macros/latex/contrib/everypage}[everypage]
+\CTANdirectory{excalibur}{systems/mac/support/excalibur}
+\CTANdirectory{excel2latex}{support/excel2latex}
+\CTANdirectory{excerpt}{web/spiderweb/tools/excerpt}
+\CTANdirectory{excludeonly}{macros/latex/contrib/excludeonly}[excludeonly]
+\CTANdirectory{expdlist}{macros/latex/contrib/expdlist}
+\CTANdirectory{extract}{macros/latex/contrib/extract}[extract]
+\CTANdirectory{extsizes}{macros/latex/contrib/extsizes}[extsizes]
+% cat links to here
+\CTANdirectory{fancyhdr}{macros/latex/contrib/fancyhdr}[fancyhdr]
+\CTANdirectory{fancyvrb}{macros/latex/contrib/fancyvrb}[fancyvrb]
+\CTANdirectory{faq}{help/uk-tex-faq}[uk-tex-faq]
+\CTANdirectory{fc}{fonts/jknappen/fc}
+\CTANdirectory{fdsymbol}{fonts/fdsymbol}[fdsymbol]
+\CTANdirectory{feyn}{fonts/feyn}
+\CTANdirectory{feynman}{macros/latex209/contrib/feynman}
+\CTANdirectory{feynmf}{macros/latex/contrib/feynmf}[feynmf]
+\CTANdirectory{fig2eng}{graphics/fig2eng}
+\CTANdirectory{fig2mf}{graphics/fig2mf}
+\CTANdirectory{fig2mfpic}{graphics/fig2mfpic}
+\CTANdirectory{figflow}{macros/plain/contrib/figflow}[figflow]
+\CTANdirectory{filehook}{macros/latex/contrib/filehook}[filehook]
+\CTANdirectory{fink}{macros/latex/contrib/fink}[fink]
+\CTANdirectory{first-latex-doc}{info/first-latex-doc}
+\CTANdirectory{fix2col}{macros/latex/contrib/fix2col}[fix2col]
+\CTANdirectory{fixfoot}{macros/latex/contrib/fixfoot}[fixfoot]
+\CTANdirectory{float}{macros/latex/contrib/float}[float]
+\CTANdirectory{floatflt}{macros/latex/contrib/floatflt}[floatflt]
+\CTANdirectory{flow}{support/flow}
+\CTANdirectory{flowfram}{macros/latex/contrib/flowfram}[flowfram]
+\CTANdirectory{fltpage}{macros/latex/contrib/fltpage}[fltpage]
+\CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak}[fnbreak]
+\CTANdirectory{fncychap}{macros/latex/contrib/fncychap}[fncychap]
+\CTANdirectory{fncylab}{macros/latex/contrib/fncylab}
+\CTANdirectory{foiltex}{macros/latex/contrib/foiltex}[foiltex]
+\CTANdirectory{font-change}{macros/plain/contrib/font-change}[font-change]
+\CTANdirectory{fontch}{macros/plain/contrib/fontch}[fontch]
+\CTANdirectory{fontinst}{fonts/utilities/fontinst}[fontinst]
+\CTANdirectory{fontname}{info/fontname}[fontname]
+\CTANdirectory{fontspec}{macros/latex/contrib/fontspec}[fontspec]
+\CTANdirectory{font_selection}{macros/plain/contrib/font_selection}[font-selection]
+\CTANdirectory{footbib}{macros/latex/contrib/footbib}[footbib]
+\CTANdirectory{footmisc}{macros/latex/contrib/footmisc}[footmisc]
+\CTANdirectory{footnpag}{macros/latex/contrib/footnpag}[footnpag]
+\CTANdirectory{forarray}{macros/latex/contrib/forarray}[forarray]
+\CTANdirectory{forloop}{macros/latex/contrib/forloop}[forloop]
+\CTANdirectory{for_tex}{biblio/bibtex/contrib/germbib/for_tex}
+\CTANdirectory{fourier}{fonts/fourier-GUT}[fourier]
+\CTANdirectory{fouriernc}{fonts/fouriernc}[fouriernc]
+\CTANdirectory{framed}{macros/latex/contrib/framed}[framed]
+\CTANdirectory{frankenstein}{macros/latex/contrib/frankenstein}[frankenstein]
+\CTANdirectory{french-faq}{help/LaTeX-FAQ-francaise}
+\CTANdirectory{funnelweb}{web/funnelweb}
+\CTANdirectory{futhark}{fonts/futhark}
+\CTANdirectory{futhorc}{fonts/futhorc}
+\CTANdirectory{fweb}{web/fweb}[fweb]
+\CTANdirectory{garamondx}{fonts/garamondx}[garamondx]
+\CTANdirectory{gellmu}{support/gellmu}[gellmu]
+\CTANdirectory{genfam}{support/genfam}
+\CTANdirectory{geometry}{macros/latex/contrib/geometry}[geometry]
+\CTANdirectory{germbib}{biblio/bibtex/contrib/germbib}
+\CTANdirectory{getoptk}{macros/plain/contrib/getoptk}[getoptk]
+\CTANdirectory{gfs}{info/examples/FirstSteps} % gratzer's
+\CTANdirectory{gitinfo}{macros/latex/contrib/gitinfo}[gitinfo]
+\CTANdirectory{glo+idxtex}{indexing/glo+idxtex}[idxtex]
+\CTANdirectory{gmp}{macros/latex/contrib/gmp}[gmp]
+\CTANdirectory{gnuplot}{graphics/gnuplot}
+\CTANdirectory{go}{fonts/go}
+\CTANdirectory{gothic}{fonts/gothic}
+\CTANdirectory{graphbase}{support/graphbase}
+\CTANdirectory{graphics}{macros/latex/required/graphics}[graphics]
+\CTANdirectory{graphics-plain}{macros/plain/graphics}[graphics-pln]
+\CTANdirectory{graphicx-psmin}{macros/latex/contrib/graphicx-psmin}[graphicx-psmin]
+\CTANdirectory{gray}{fonts/cm/utilityfonts/gray}
+\CTANdirectory{greek}{fonts/greek}
+\CTANdirectory{greektex}{fonts/greek/greektex}
+\CTANdirectory{gsftopk}{fonts/utilities/gsftopk}[gsftopk]
+\CTANdirectory{gut}{usergrps/gut}
+\CTANdirectory*{gv}{support/gv}[gv]
+\CTANdirectory{ha-prosper}{macros/latex/contrib/ha-prosper}[ha-prosper]
+\CTANdirectory{half}{fonts/cm/utilityfonts/half}
+\CTANdirectory{halftone}{fonts/halftone}
+\CTANdirectory{hands}{fonts/hands}
+\CTANdirectory{harvard}{macros/latex/contrib/harvard}
+\CTANdirectory{harvmac}{macros/plain/contrib/harvmac}
+\CTANdirectory{hebrew}{language/hebrew}
+\CTANdirectory{help}{help}
+\CTANdirectory{here}{macros/latex/contrib/here}[here]
+\CTANdirectory{hershey}{fonts/hershey}
+\CTANdirectory{hfbright}{fonts/ps-type1/hfbright}[hfbright]
+\CTANdirectory{hge}{fonts/hge}
+\CTANdirectory{hieroglyph}{fonts/hieroglyph}
+\CTANdirectory{highlight}{support/highlight}
+\CTANdirectory{histyle}{macros/plain/contrib/histyle}
+\CTANdirectory{hp2pl}{support/hp2pl}
+\CTANdirectory{hp2xx}{support/hp2xx}
+\CTANdirectory{hpgl2ps}{graphics/hpgl2ps}
+\CTANdirectory{hptex}{macros/hptex}
+\CTANdirectory{hptomf}{support/hptomf}
+\CTANdirectory{html2latex}{support/html2latex}[html2latex]
+\CTANdirectory{htmlhelp}{info/htmlhelp}
+\CTANdirectory{hvfloat}{macros/latex/contrib/hvfloat}[hvfloat]
+\CTANdirectory{hvmath}{fonts/micropress/hvmath}[hvmath-fonts]
+\CTANdirectory{hyacc-cm}{macros/generic/hyacc-cm}
+\CTANdirectory{hyper}{macros/latex/contrib/hyper}
+\CTANdirectory{hyperbibtex}{biblio/bibtex/utils/hyperbibtex}
+\CTANdirectory{hypernat}{macros/latex/contrib/hypernat}[hypernat]
+\CTANdirectory{hyperref}{macros/latex/contrib/hyperref}[hyperref]
+\CTANdirectory{hyphen-accent}{language/hyphen-accent}
+\CTANdirectory{hyphenat}{macros/latex/contrib/hyphenat}[hyphenat]
+\CTANdirectory{hyphenation}{language/hyphenation}
+\CTANdirectory{ibygrk}{fonts/greek/ibygrk}
+\CTANdirectory{iching}{fonts/iching}
+\CTANdirectory{icons}{support/icons}
+\CTANdirectory{ifmtarg}{macros/latex/contrib/ifmtarg}[ifmtarg]
+\CTANdirectory{ifmslide}{macros/latex/contrib/ifmslide}[ifmslide]
+\CTANdirectory{ifoddpage}{macros/latex/contrib/ifoddpage}[ifoddpage]
+\CTANdirectory{ifxetex}{macros/generic/ifxetex}[ifxetex]
+\CTANdirectory{imakeidx}{macros/latex/contrib/imakeidx}[imakeidx]
+\CTANdirectory{imaketex}{support/imaketex}
+\CTANdirectory{impact}{web/systems/mac/impact}
+\CTANdirectory{import}{macros/latex/contrib/import}[import]
+\CTANdirectory{index}{macros/latex/contrib/index}[index]
+\CTANdirectory{indian}{language/indian}
+\CTANdirectory{infpic}{macros/generic/infpic}
+\CTANdirectory{inlinebib}{biblio/bibtex/contrib/inlinebib}
+\CTANdirectory{inrsdoc}{macros/inrstex/inrsdoc}
+\CTANdirectory{inrsinputs}{macros/inrstex/inrsinputs}
+\CTANdirectory{inrstex}{macros/inrstex}
+\CTANdirectory{isi2bibtex}{biblio/bibtex/utils/isi2bibtex}[isi2bibtex]
+\CTANdirectory{iso-tex}{support/iso-tex}
+\CTANdirectory{isodoc}{macros/latex/contrib/isodoc}[isodoc]
+\CTANdirectory{ispell}{support/ispell}[ispell]
+\CTANdirectory{ite}{support/ite}[ite]
+\CTANdirectory{ivd2dvi}{dviware/ivd2dvi}
+\CTANdirectory{jadetex}{macros/jadetex}
+\CTANdirectory{jemtex2}{systems/msdos/jemtex2}
+\CTANdirectory{jknappen-macros}{macros/latex/contrib/jknappen}
+\CTANdirectory{jpeg2ps}{support/jpeg2ps}[jpeg2ps]
+\CTANdirectory{jspell}{support/jspell}[jspell]
+\CTANdirectory{jurabib}{macros/latex/contrib/jurabib}[jurabib]
+\CTANdirectory{kamal}{support/kamal}
+\CTANdirectory{kane}{dviware/kane}
+\CTANdirectory{karta}{fonts/karta}
+\CTANdirectory{kd}{fonts/greek/kd}
+\CTANdirectory{kelem}{web/spiderweb/src/kelem}
+\CTANdirectory{kelly}{fonts/greek/kelly}
+\CTANdirectory{klinz}{fonts/klinz}
+\CTANdirectory{knit}{web/knit}
+\CTANdirectory{knot}{fonts/knot}
+\CTANdirectory{knuth}{systems/knuth}
+\CTANdirectory{knuth-dist}{systems/knuth/dist}[knuth-dist]
+\CTANdirectory{koma-script}{macros/latex/contrib/koma-script}[koma-script]
+\CTANdirectory{korean}{fonts/korean}
+\CTANdirectory{kpfonts}{fonts/kpfonts}[kpfonts]
+\CTANdirectory{kyocera}{dviware/kyocera}
+\CTANdirectory{l2a}{support/l2a}[l2a]
+\CTANdirectory{l2sl}{language/swedish/slatex/l2sl}
+\CTANdirectory*{l2tabu}{info/l2tabu}
+\CTANdirectory{l2x}{support/l2x}
+\CTANdirectory{la}{fonts/la}
+\CTANdirectory{laan}{macros/generic/laan}
+\CTANdirectory{laansort}{macros/generic/laansort}
+\CTANdirectory{labelcas}{macros/latex/contrib/labelcas}[labelcas]
+\CTANdirectory{labels}{macros/latex/contrib/labels}
+\CTANdirectory{labtex}{macros/generic/labtex}
+\CTANdirectory{lacheck}{support/lacheck}[lacheck]
+\CTANdirectory{lametex}{support/lametex}
+\CTANdirectory{lamstex}{macros/lamstex}
+\CTANdirectory{lastpage}{macros/latex/contrib/lastpage}[lastpage]
+\CTANdirectory{latex}{macros/latex/base}
+\CTANdirectory{latex-course}{info/latex-course}[latex-course]
+\CTANdirectory{latex-essential}{info/latex-essential}
+\CTANdirectory{latex2e-help-texinfo}{info/latex2e-help-texinfo}[latex2e-help-texinfo]
+\CTANdirectory{latex4jed}{support/jed}[latex4jed]
+\CTANdirectory*{latex-tds}{macros/latex/contrib/latex-tds}[latex-tds]
+\CTANdirectory*{latex2html}{support/latex2html}[latex2html]
+\CTANdirectory{latex2rtf}{support/latex2rtf}
+\CTANdirectory{latexdiff}{support/latexdiff}[latexdiff]
+\CTANdirectory{latexdoc}{macros/latex/doc}[latex-doc]
+\CTANdirectory{latexhlp}{systems/atari/latexhlp}
+\CTANdirectory{latexmake}{support/latexmake}[latexmake]
+\CTANdirectory{latex-make}{support/latex-make}[latex-make]
+\CTANdirectory{latex_maker}{support/latex_maker}[mk]
+\CTANdirectory{latexmk}{support/latexmk}[latexmk]
+\CTANdirectory{lecturer}{macros/generic/lecturer}[lecturer]
+\CTANdirectory{ledmac}{macros/latex/contrib/ledmac}[ledmac]
+\CTANdirectory{lettrine}{macros/latex/contrib/lettrine}[lettrine]
+\CTANdirectory{levy}{fonts/greek/levy}
+\CTANdirectory{lextex}{macros/plain/contrib/lextex}
+\CTANdirectory{lgc}{info/examples/lgc}
+\CTANdirectory{lgrind}{support/lgrind}[lgrind]
+\CTANdirectory{libertine}{fonts/libertine}[libertine]
+\CTANdirectory{libgreek}{macros/latex/contrib/libgreek}[libgreek]
+\CTANdirectory{lilyglyphs}{macros/luatex/latex/lilyglyphs}
+\CTANdirectory{lineno}{macros/latex/contrib/lineno}[lineno]
+\CTANdirectory{lipsum}{macros/latex/contrib/lipsum}[lipsum]
+\CTANdirectory{listbib}{macros/latex/contrib/listbib}[listbib]
+\CTANdirectory{listings}{macros/latex/contrib/listings}[listings]
+\CTANdirectory{lm}{fonts/lm}[lm]
+\CTANdirectory{lm-math}{fonts/lm-math}[lm-math]
+\CTANdirectory{lollipop}{macros/lollipop}[lollipop]
+\CTANdirectory{lookbibtex}{biblio/bibtex/utils/lookbibtex}
+\CTANdirectory{lpic}{macros/latex/contrib/lpic}[lpic]
+\CTANdirectory{lsedit}{support/lsedit}
+\CTANdirectory{lshort}{info/lshort/english}[lshort-english]
+\CTANdirectory*{lshort-parent}{info/lshort}[lshort]
+\CTANdirectory{ltx3pub}{info/ltx3pub}[ltx3pub]
+\CTANdirectory{ltxindex}{macros/latex/contrib/ltxindex}[ltxindex]
+\CTANdirectory{luatex}{systems/luatex}[luatex]
+\CTANdirectory{lucida}{fonts/psfonts/bh/lucida}[lucida]
+\CTANdirectory{lucida-psnfss}{macros/latex/contrib/psnfssx/lucidabr}[psnfssx-luc]
+\CTANdirectory{luximono}{fonts/LuxiMono}[luximono]
+\CTANdirectory{lwc}{info/examples/lwc}
+\CTANdirectory{ly1}{fonts/psfonts/ly1}[ly1]
+\CTANdirectory*{mactex}{systems/mac/mactex}[mactex]
+\CTANdirectory{macros2e}{info/macros2e}[macros2e]
+\CTANdirectory{mactotex}{graphics/mactotex}
+\CTANdirectory{mailing}{macros/latex/contrib/mailing}
+\CTANdirectory{make_latex}{support/make_latex}[make-latex]
+\CTANdirectory{makeafm.dir}{fonts/utilities/t1tools/makeafm.dir}
+\CTANdirectory{makecell}{macros/latex/contrib/makecell}[makecell]
+\CTANdirectory{makedtx}{support/makedtx}[makedtx]
+\CTANdirectory{makeindex}{indexing/makeindex}[makeindex]
+\CTANdirectory{makeinfo}{macros/texinfo/contrib/texinfo-hu/texinfo/makeinfo}
+\CTANdirectory{makeprog}{support/makeprog}\CTANdirectory{maketexwork}{info/maketexwork}
+\CTANdirectory{malayalam}{language/malayalam}
+\CTANdirectory{malvern}{fonts/malvern}
+\CTANdirectory{mapleweb}{web/maple/mapleweb}
+\CTANdirectory{marvosym-fonts}{fonts/marvosym}
+\CTANdirectory{mathabx}{fonts/mathabx}[mathabx]
+\CTANdirectory{mathabx-type1}{fonts/ps-type1/mathabx}[mathabx-type1]
+\CTANdirectory{mathastext}{macros/latex/contrib/mathastext}[mathastext]
+\CTANdirectory*{mathdesign}{fonts/mathdesign}[mathdesign]
+\CTANdirectory{mathdots}{macros/generic/mathdots}
+\CTANdirectory{mathematica}{macros/mathematica}
+\CTANdirectory{mathpazo}{fonts/mathpazo}[mathpazo]
+\CTANdirectory{mathsci2bibtex}{biblio/bibtex/utils/mathsci2bibtex}
+\CTANdirectory{mathspic}{graphics/mathspic}[mathspic]
+\CTANdirectory{mcite}{macros/latex/contrib/mcite}[mcite]
+\CTANdirectory{mciteplus}{macros/latex/contrib/mciteplus}[mciteplus]
+\CTANdirectory{mdframed}{macros/latex/contrib/mdframed}[mdframed]
+\CTANdirectory{mdsymbol}{fonts/mdsymbol}[mdsymbol]
+\CTANdirectory{mdwtools}{macros/latex/contrib/mdwtools}[mdwtools]
+\CTANdirectory{memdesign}{info/memdesign}[memdesign]
+\CTANdirectory{memoir}{macros/latex/contrib/memoir}[memoir]
+\CTANdirectory{messtex}{support/messtex}
+\CTANdirectory{metalogo}{macros/latex/contrib/metalogo}[metalogo]
+\CTANdirectory{metapost}{graphics/metapost}
+\CTANdirectory{metatype1}{fonts/utilities/metatype1}[metatype1]
+\CTANdirectory{mf2ps}{fonts/utilities/mf2ps}
+\CTANdirectory{mf2pt1}{support/mf2pt1}[mf2pt1]
+\CTANdirectory{mf_optimized_kerning}{fonts/cm/mf_optimized_kerning}
+\CTANdirectory{mfbook}{fonts/cm/utilityfonts/mfbook}
+\CTANdirectory{mff-29}{fonts/utilities/mff-29}
+\CTANdirectory{mffiles}{language/telugu/mffiles}
+\CTANdirectory{mflogo}{macros/latex/contrib/mflogo}[mflogo]
+\CTANdirectory{mfnfss}{macros/latex/contrib/mfnfss}
+\CTANdirectory{mfpic}{graphics/mfpic}
+\CTANdirectory{mfware}{systems/knuth/dist/mfware}
+\CTANdirectory{mh}{macros/latex/contrib/mh}[mh]
+\CTANdirectory{miktex}{systems/win32/miktex}[miktex]
+\CTANdirectory{microtype}{macros/latex/contrib/microtype}[microtype]
+\CTANdirectory{midi2tex}{support/midi2tex}
+\CTANdirectory{midnight}{macros/generic/midnight}
+\CTANdirectory{minionpro}{fonts/minionpro}[minionpro]
+\CTANdirectory{minitoc}{macros/latex/contrib/minitoc}[minitoc]
+\CTANdirectory{minted}{macros/latex/contrib/minted}[minted]
+\CTANdirectory{mkjobtexmf}{support/mkjobtexmf}[mkjobtexmf]
+\CTANdirectory{mma2ltx}{graphics/mma2ltx}
+\CTANdirectory{mmap}{macros/latex/contrib/mmap}
+\CTANdirectory{mnsymbol}{fonts/mnsymbol}[mnsymbol]
+\CTANdirectory{mnu}{support/mnu}
+\CTANdirectory{models}{macros/text1/models}
+\CTANdirectory{moderncv}{macros/latex/contrib/moderncv}[moderncv]
+\CTANdirectory{modes}{fonts/modes}
+\CTANdirectory{morefloats}{macros/latex/contrib/morefloats}[morefloats]
+\CTANdirectory{moreverb}{macros/latex/contrib/moreverb}[moreverb]
+\CTANdirectory{morewrites}{macros/latex/contrib/morewrites}[morewrites]
+\CTANdirectory{mparhack}{macros/latex/contrib/mparhack}[mparhack]
+\CTANdirectory{mpgraphics}{macros/latex/contrib/mpgraphics}[mpgraphics]
+\CTANdirectory{mps2eps}{support/mps2eps}
+\CTANdirectory{ms}{macros/latex/contrib/ms}[ms]
+\CTANdirectory{msdos}{systems/msdos}
+\CTANdirectory{msx2msa}{fonts/vf-files/msx2msa}
+\CTANdirectory{msym}{fonts/msym}
+\CTANdirectory{mtp2lite}{fonts/mtp2lite}[mtp2lite]
+\CTANdirectory{m-tx}{support/m-tx}[m-tx]
+\CTANdirectory{multenum}{macros/latex/contrib/multenum}[multenum]
+\CTANdirectory{multibbl}{macros/latex/contrib/multibbl}[multibbl]
+\CTANdirectory{multibib}{macros/latex/contrib/multibib}[multibib]
+\CTANdirectory{multido}{macros/generic/multido}[multido]
+\CTANdirectory{multirow}{macros/latex/contrib/multirow}[multirow]
+\CTANdirectory{musictex}{macros/musictex}[musictex]
+\CTANdirectory{musixtex-egler}{obsolete/macros/musixtex/egler}
+\CTANdirectory{musixtex-fonts}{fonts/musixtex-fonts}[musixtex-fonts]
+\CTANdirectory{musixtex}{macros/musixtex}[musixtex]
+\CTANdirectory{mutex}{macros/mtex}
+\CTANdirectory{mwe}{macros/latex/contrib/mwe}[mwe]
+\CTANdirectory{mxedruli}{fonts/georgian/mxedruli}
+\CTANdirectory{nag}{macros/latex/contrib/nag}[nag]
+\CTANdirectory{natbib}{macros/latex/contrib/natbib}[natbib]
+\CTANdirectory{navigator}{macros/generic/navigator}[navigator]
+\CTANdirectory{nawk}{web/spiderweb/src/nawk}
+\CTANdirectory{ncctools}{macros/latex/contrib/ncctools}[ncctools]
+\CTANdirectory{needspace}{macros/latex/contrib/needspace}[needspace]
+\CTANdirectory{newalg}{macros/latex/contrib/newalg}[newalg]
+\CTANdirectory{newcommand}{support/newcommand}[newcommand]
+\CTANdirectory{newlfm}{macros/latex/contrib/newlfm}[newlfm]
+\CTANdirectory{newsletr}{macros/plain/contrib/newsletr}
+\CTANdirectory{newpx}{fonts/newpx}[newpx]
+\CTANdirectory{newtx}{fonts/newtx}[newtx]
+\CTANdirectory{newverbs}{macros/latex/contrib/newverbs}[newverbs]
+\CTANdirectory{nedit-latex}{support/NEdit-LaTeX-Extensions}
+\CTANdirectory{nonumonpart}{macros/latex/contrib/nonumonpart}[nonumonpart]
+\CTANdirectory{nopageno}{macros/latex/contrib/nopageno}[nopageno]
+\CTANdirectory{norbib}{biblio/bibtex/contrib/norbib}
+\CTANdirectory{notoccite}{macros/latex/contrib/notoccite}[notoccite]
+\CTANdirectory{noweb}{web/noweb}[noweb]
+\CTANdirectory{ntg}{usergrps/ntg}
+\CTANdirectory{ntgclass}{macros/latex/contrib/ntgclass}[ntgclass]
+\CTANdirectory{ntheorem}{macros/latex/contrib/ntheorem}[ntheorem]
+\CTANdirectory{nts-l}{digests/nts-l}
+\CTANdirectory{nts}{systems/nts}
+\CTANdirectory{numprint}{macros/latex/contrib/numprint}[numprint]
+\CTANdirectory{nuweb}{web/nuweb}
+\CTANdirectory{nuweb0.87b}{web/nuweb/nuweb0.87b}
+\CTANdirectory{nuweb_ami}{web/nuweb/nuweb_ami}
+\CTANdirectory{oberdiek}{macros/latex/contrib/oberdiek}[oberdiek]
+\CTANdirectory{objectz}{macros/latex/contrib/objectz}
+\CTANdirectory{ocr-a}{fonts/ocr-a}
+\CTANdirectory{ocr-b}{fonts/ocr-b}
+\CTANdirectory{ofs}{macros/generic/ofs}[ofs]
+\CTANdirectory{ogham}{fonts/ogham}
+\CTANdirectory{ogonek}{macros/latex/contrib/ogonek}
+\CTANdirectory{okuda}{fonts/okuda}
+\CTANdirectory{omega}{systems/omega}
+\CTANdirectory{optional}{macros/latex/contrib/optional}[optional]
+\CTANdirectory{os2}{systems/os2}
+\CTANdirectory{osmanian}{fonts/osmanian}
+\CTANdirectory{overpic}{macros/latex/contrib/overpic}[overpic]
+\CTANdirectory{oztex}{systems/mac/oztex}
+\CTANdirectory{page}{support/lametex/page}
+\CTANdirectory{palladam}{language/tamil/palladam}
+\CTANdirectory{pandora}{fonts/pandora}
+\CTANdirectory{paralist}{macros/latex/contrib/paralist}[paralist]
+\CTANdirectory{parallel}{macros/latex/contrib/parallel}[parallel]
+\CTANdirectory{parskip}{macros/latex/contrib/parskip}[parskip]
+\CTANdirectory{passivetex}{macros/xmltex/contrib/passivetex}[passivetex]
+\CTANdirectory{patchcmd}{macros/latex/contrib/patchcmd}[patchcmd]
+\CTANdirectory{path}{macros/generic/path}[path]
+\CTANdirectory{pbox}{macros/latex/contrib/pbox}[pbox]
+\CTANdirectory{pcwritex}{support/pcwritex}
+\CTANdirectory{pdcmac}{macros/plain/contrib/pdcmac}[pdcmac]
+\CTANdirectory{pdfcomment}{macros/latex/contrib/pdfcomment}[pdfcomment]
+\CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages}[pdfpages]
+\CTANdirectory{pdfrack}{support/pdfrack}[pdfrack]
+\CTANdirectory{pdfscreen}{macros/latex/contrib/pdfscreen}[pdfscreen]
+\CTANdirectory{pdftex}{systems/pdftex}[pdftex]
+\CTANdirectory{pdftex-graphics}{graphics/metapost/contrib/tools/mptopdf}[pdf-mps-supp]
+\CTANdirectory{pdftricks}{graphics/pdftricks}[pdftricks]
+\CTANdirectory{pdftricks2}{graphics/pdftricks2}[pdftricks2]
+\CTANdirectory{pgf}{graphics/pgf/base}[pgf]
+\CTANdirectory{phonetic}{fonts/phonetic}
+\CTANdirectory{phy-bstyles}{biblio/bibtex/contrib/phy-bstyles}
+\CTANdirectory{physe}{macros/physe}
+\CTANdirectory{phyzzx}{macros/phyzzx}
+\CTANdirectory{picinpar}{macros/latex209/contrib/picinpar}[picinpar]
+\CTANdirectory{picins}{macros/latex209/contrib/picins}[picins]
+\CTANdirectory{pict2e}{macros/latex/contrib/pict2e}[pict2e]
+\CTANdirectory{pictex}{graphics/pictex}[pictex]
+\CTANdirectory{pictex-addon}{graphics/pictex/addon}[pictexwd]
+\CTANdirectory{pictex-converter}{support/pictex-converter}
+\CTANdirectory{pictex-summary}{info/pictex/summary}[pictexsum]
+\CTANdirectory{pinlabel}{macros/latex/contrib/pinlabel}[pinlabel]
+\CTANdirectory{pkbbox}{fonts/utilities/pkbbox}
+\CTANdirectory{pkfix}{support/pkfix}[pkfix]
+\CTANdirectory{pkfix-helper}{support/pkfix-helper}[pkfix-helper]
+\CTANdirectory{placeins}{macros/latex/contrib/placeins}[placeins]
+\CTANdirectory{plain}{macros/plain/base}[plain]
+\CTANdirectory*{plastex}{support/plastex}[plastex]
+\CTANdirectory{plnfss}{macros/plain/plnfss}[plnfss]
+\CTANdirectory{plttopic}{support/plttopic}
+\CTANdirectory{pmtex}{systems/os2/pmtex}
+\CTANdirectory{pmx}{support/pmx}
+\CTANdirectory{l3experimental}{macros/latex/contrib/l3experimental}[l3experimental]
+\CTANdirectory{l3kernel}{macros/latex/contrib/l3kernel}[l3kernel]
+\CTANdirectory{l3packages}{macros/latex/contrib/l3packages}[l3packages]
+\CTANdirectory{polish}{language/polish}
+\CTANdirectory{polyglossia}{macros/latex/contrib/polyglossia}[polyglossia]
+\CTANdirectory{poorman}{fonts/poorman}
+\CTANdirectory{portuguese}{language/portuguese}
+\CTANdirectory{poster}{macros/generic/poster}
+\CTANdirectory{powerdot}{macros/latex/contrib/powerdot}[powerdot]
+\CTANdirectory{pp}{support/pp}
+\CTANdirectory{preprint}{macros/latex/contrib/preprint}[preprint]
+\CTANdirectory{present}{macros/plain/contrib/present}[present]
+\CTANdirectory{preview}{macros/latex/contrib/preview}[preview]
+\CTANdirectory{print-fine}{support/print-fine}
+\CTANdirectory{printbib}{biblio/bibtex/utils/printbib}
+\CTANdirectory{printlen}{macros/latex/contrib/printlen}[printlen]
+\CTANdirectory{printsamples}{fonts/utilities/mf2ps/doc/printsamples}
+\CTANdirectory{program}{macros/latex/contrib/program}[program]
+\CTANdirectory{proofs}{macros/generic/proofs}
+\CTANdirectory*{protext}{systems/win32/protext}[protext]
+\CTANdirectory{ppower4}{support/ppower4}[ppower4]
+\CTANdirectory{ppr-prv}{macros/latex/contrib/ppr-prv}[ppr-prv]
+\CTANdirectory{prosper}{macros/latex/contrib/prosper}[prosper]
+\CTANdirectory{ps-type3}{fonts/cm/ps-type3}
+\CTANdirectory{ps2mf}{fonts/utilities/ps2mf}
+\CTANdirectory{ps2pk}{fonts/utilities/ps2pk}[ps2pk]
+\CTANdirectory{psbook}{systems/msdos/dviware/psbook}
+\CTANdirectory{psbox}{macros/generic/psbox}
+\CTANdirectory{pseudocode}{macros/latex/contrib/pseudocode}[pseudocode]
+\CTANdirectory{psfig}{graphics/psfig}[psfig]
+\CTANdirectory{psfrag}{macros/latex/contrib/psfrag}[psfrag]
+\CTANdirectory{psfragx}{macros/latex/contrib/psfragx}[psfragx]
+\CTANdirectory{psizzl}{macros/psizzl}
+\CTANdirectory{psnfss}{macros/latex/required/psnfss}[psnfss]
+\CTANdirectory{psnfss-addons}{macros/latex/contrib/psnfss-addons}
+\CTANdirectory{psnfssx-mathtime}{macros/latex/contrib/psnfssx/mathtime}
+\CTANdirectory{pspicture}{macros/latex/contrib/pspicture}[pspicture]
+\CTANdirectory{psprint}{dviware/psprint}
+\CTANdirectory{pst-layout}{graphics/pstricks/contrib/pst-layout}[pst-layout]
+\CTANdirectory{pst-pdf}{macros/latex/contrib/pst-pdf}[pst-pdf]
+\CTANdirectory{pstoedit}{support/pstoedit}[pstoedit]
+\CTANdirectory{pstricks}{graphics/pstricks}[pstricks]
+\CTANdirectory{psutils}{support/psutils}
+\CTANdirectory{punk}{fonts/punk}
+\CTANdirectory{purifyeps}{support/purifyeps}[purifyeps]
+\CTANdirectory{pxfonts}{fonts/pxfonts}[pxfonts]
+\CTANdirectory{qdtexvpl}{fonts/utilities/qdtexvpl}[qdtexvpl]
+\CTANdirectory{qfig}{support/qfig}
+\CTANdirectory{quotchap}{macros/latex/contrib/quotchap}[quotchap]
+\CTANdirectory{r2bib}{biblio/bibtex/utils/r2bib}[r2bib]
+\CTANdirectory{rcs}{macros/latex/contrib/rcs}[rcs]
+\CTANdirectory{rcsinfo}{macros/latex/contrib/rcsinfo}[rcsinfo]
+\CTANdirectory{realcalc}{macros/generic/realcalc}
+\CTANdirectory{refcheck}{macros/latex/contrib/refcheck}[refcheck]
+\CTANdirectory{refer-tools}{biblio/bibtex/utils/refer-tools}
+\CTANdirectory{refman}{macros/latex/contrib/refman}[refman]
+\CTANdirectory{regexpatch}{macros/latex/contrib/regexpatch}[regexpatch]
+\CTANdirectory{revtex4-1}{macros/latex/contrib/revtex}[revtex4-1]
+\CTANdirectory{rnototex}{support/rnototex}[rnototex]
+\CTANdirectory{rotating}{macros/latex/contrib/rotating}[rotating]
+\CTANdirectory{rotfloat}{macros/latex/contrib/rotfloat}[rotfloat]
+\CTANdirectory{rsfs}{fonts/rsfs}[rsfs]
+\CTANdirectory{rsfso}{fonts/rsfso}[rsfso]
+\CTANdirectory{rtf2tex}{support/rtf2tex}[rtf2tex]
+\CTANdirectory{rtf2html}{support/rtf2html}
+\CTANdirectory{rtf2latex}{support/rtf2latex}
+\CTANdirectory{rtf2latex2e}{support/rtf2latex2e}[rtf2latex2e]
+\CTANdirectory{rtflatex}{support/rtflatex}
+\CTANdirectory{rtfutils}{support/tex2rtf/rtfutils}
+\CTANdirectory{rumgraph}{support/rumgraph}
+\CTANdirectory{sam2p}{graphics/sam2p}[sam2p]
+\CTANdirectory{sansmath}{macros/latex/contrib/sansmath}[sansmath]
+\CTANdirectory{sauerj}{macros/latex/contrib/sauerj}[sauerj]
+\CTANdirectory{savetrees}{macros/latex/contrib/savetrees}[savetrees]
+\CTANdirectory{schemeweb}{web/schemeweb}[schemeweb]
+\CTANdirectory{sciposter}{macros/latex/contrib/sciposter}[sciposter]
+\CTANdirectory{sectsty}{macros/latex/contrib/sectsty}[sectsty]
+\CTANdirectory{selectp}{macros/latex/contrib/selectp}[selectp]
+\CTANdirectory{seminar}{macros/latex/contrib/seminar}[seminar]
+\CTANdirectory{shade}{macros/generic/shade}[shade]
+\CTANdirectory{shorttoc}{macros/latex/contrib/shorttoc}[shorttoc]
+\CTANdirectory{showexpl}{macros/latex/contrib/showexpl}[showexpl]
+\CTANdirectory{showlabels}{macros/latex/contrib/showlabels}[showlabels]
+\CTANdirectory{slashbox}{macros/latex/contrib/slashbox}[slashbox]
+\CTANdirectory{smallcap}{macros/latex/contrib/smallcap}[smallcap]
+\CTANdirectory{smartref}{macros/latex/contrib/smartref}[smartref]
+\CTANdirectory{snapshot}{macros/latex/contrib/snapshot}[snapshot]
+\CTANdirectory{soul}{macros/latex/contrib/soul}[soul]
+\CTANdirectory{spain}{biblio/bibtex/contrib/spain}
+\CTANdirectory{spelling}{macros/luatex/generic/spelling}[spelling]
+\CTANdirectory{spiderweb}{web/spiderweb}[spiderweb]
+\CTANdirectory{splitbib}{macros/latex/contrib/splitbib}[splitbib]
+\CTANdirectory{splitindex}{macros/latex/contrib/splitindex}[splitindex]
+\CTANdirectory{standalone}{macros/latex/contrib/standalone}[standalone]
+\CTANdirectory{stix}{fonts/stix}[stix]
+\CTANdirectory{sttools}{macros/latex/contrib/sttools}[sttools]
+\CTANdirectory{sty2dtx}{support/sty2dtx}[sty2dtx]
+\CTANdirectory{subdepth}{macros/latex/contrib/subdepth}[subdepth]
+\CTANdirectory{subfig}{macros/latex/contrib/subfig}[subfig]
+\CTANdirectory{subfiles}{macros/latex/contrib/subfiles}[subfiles]
+\CTANdirectory{supertabular}{macros/latex/contrib/supertabular}[supertabular]
+\CTANdirectory{svn}{macros/latex/contrib/svn}[svn]
+\CTANdirectory{svninfo}{macros/latex/contrib/svninfo}[svninfo]
+\CTANdirectory{swebib}{biblio/bibtex/contrib/swebib}
+\CTANdirectory*{symbols}{info/symbols/comprehensive}[comprehensive]
+\CTANdirectory{tablefootnote}{macros/latex/contrib/tablefootnote}[tablefootnote]
+\CTANdirectory{tabls}{macros/latex/contrib/tabls}[tabls]
+\CTANdirectory{tabulary}{macros/latex/contrib/tabulary}[tabulary]
+\CTANdirectory{tagging}{macros/latex/contrib/tagging}
+\CTANdirectory{talk}{macros/latex/contrib/talk}[talk]
+\CTANdirectory{tcolorbox}{macros/latex/contrib/tcolorbox}[tcolorbox]
+\CTANdirectory{tds}{tds}[tds]
+\CTANdirectory{ted}{macros/latex/contrib/ted}[ted]
+\CTANdirectory*{testflow}{macros/latex/contrib/IEEEtran/testflow}[testflow]
+\CTANdirectory*{tetex}{obsolete/systems/unix/teTeX/current/distrib}[tetex]
+\CTANdirectory{tex2mail}{support/tex2mail}[tex2mail]
+\CTANdirectory{tex2rtf}{support/tex2rtf}[tex2rtf]
+\CTANdirectory{texbytopic}{info/texbytopic}[texbytopic]
+\CTANdirectory{texcnvfaq}{help/wp-conv}[wp-conv]
+\CTANdirectory{texcount}{support/texcount}[texcount]
+\CTANdirectory{texdef}{support/texdef}[texdef]
+\CTANdirectory{tex-gpc}{systems/unix/tex-gpc}[tex-gpc]
+\CTANdirectory{tex-gyre}{fonts/tex-gyre}[tex-gyre]
+\CTANdirectory{tex-gyre-math}{fonts/tex-gyre-math}[tex-gyre-math]
+\CTANdirectory{tex-overview}{info/tex-overview}[tex-overview]
+\CTANdirectory*{texhax}{digests/texhax}[texhax]
+\CTANdirectory{texi2html}{support/texi2html}[texi2html]
+\CTANdirectory{texindex}{indexing/texindex}[texindex]
+\CTANdirectory{texinfo}{macros/texinfo/texinfo}[texinfo]
+\CTANdirectory*{texlive}{systems/texlive}[texlive]
+\CTANdirectory*{texmacs}{support/TeXmacs}[texmacs]
+\CTANdirectory*{texniccenter}{systems/win32/TeXnicCenter}[texniccenter]
+\CTANdirectory{texpower}{macros/latex/contrib/texpower}[texpower]
+\CTANdirectory{texshell}{systems/msdos/texshell}[texshell]
+\CTANdirectory{texsis}{macros/texsis}[texsis]
+\CTANdirectory{textcase}{macros/latex/contrib/textcase}[textcase]
+\CTANdirectory{textfit}{macros/latex/contrib/textfit}[textfit]
+\CTANdirectory{textmerg}{macros/latex/contrib/textmerg}[textmerg]
+\CTANdirectory{textpos}{macros/latex/contrib/textpos}[textpos]
+\CTANdirectory{textures_figs}{systems/mac/textures_figs}
+\CTANdirectory{texutils}{systems/atari/texutils}
+\CTANdirectory{tgrind}{support/tgrind}[tgrind]
+\CTANdirectory{threeparttable}{macros/latex/contrib/threeparttable}[threeparttable]
+\CTANdirectory{threeparttablex}{macros/latex/contrib/threeparttablex}[threeparttablex]
+\CTANdirectory{tib}{biblio/tib}[tib]
+\CTANdirectory{tiny_c2l}{support/tiny_c2l}[tinyc2l]
+\CTANdirectory{tip}{info/examples/tip}
+\CTANdirectory{titleref}{macros/latex/contrib/titleref}[titleref]
+\CTANdirectory{titlesec}{macros/latex/contrib/titlesec}[titlesec]
+\CTANdirectory{titling}{macros/latex/contrib/titling}[titling]
+\CTANdirectory{tlc2}{info/examples/tlc2}
+\CTANdirectory{tmmath}{fonts/micropress/tmmath}[tmmath]
+\CTANdirectory{tocbibind}{macros/latex/contrib/tocbibind}[tocbibind]
+\CTANdirectory{tocloft}{macros/latex/contrib/tocloft}[tocloft]
+\CTANdirectory{tocvsec2}{macros/latex/contrib/tocvsec2}[tocvsec2]
+\CTANdirectory{totpages}{macros/latex/contrib/totpages}[totpages]
+\CTANdirectory{tr2latex}{support/tr2latex}[tr2latex]
+\CTANdirectory{transfig}{graphics/transfig}[transfig]
+\CTANdirectory{try}{support/try}[try]
+\CTANdirectory{tt2001}{fonts/ps-type1/tt2001}[tt2001]
+\CTANdirectory{tth}{support/tth/dist}[tth]
+\CTANdirectory{ttn}{digests/ttn}
+\CTANdirectory{tug}{usergrps/tug}
+\CTANdirectory{tugboat}{digests/tugboat}
+\CTANdirectory{tweb}{web/tweb}[tweb]
+\CTANdirectory{txfonts}{fonts/txfonts}[txfonts]
+\CTANdirectory{txfontsb}{fonts/txfontsb}[txfontsb]
+\CTANdirectory{txtdist}{support/txt}[txt]
+\CTANdirectory{type1cm}{macros/latex/contrib/type1cm}[type1cm]
+\CTANdirectory{ucharclasses}{macros/xetex/latex/ucharclasses}[ucharclasses]
+\CTANdirectory{ucs}{macros/latex/contrib/ucs}[ucs]
+\CTANdirectory{ucthesis}{macros/latex/contrib/ucthesis}[ucthesis]
+\CTANdirectory{uktex}{digests/uktex}
+\CTANdirectory{ulem}{macros/latex/contrib/ulem}[ulem]
+\CTANdirectory{umrand}{macros/generic/umrand}
+\CTANdirectory{underscore}{macros/latex/contrib/underscore}[underscore]
+\CTANdirectory{unicode-math}{macros/latex/contrib/unicode-math}[unicode-math]
+\CTANdirectory{unix}{systems/unix}
+\CTANdirectory{unpacked}{macros/latex/unpacked}
+\CTANdirectory{untex}{support/untex}[untex]
+\CTANdirectory{url}{macros/latex/contrib/url}[url]
+\CTANdirectory{urlbst}{biblio/bibtex/contrib/urlbst}[urlbst]
+\CTANdirectory{urw-base35}{fonts/urw/base35}[urw-base35]
+\CTANdirectory{urwchancal}{fonts/urwchancal}[urwchancal]
+\CTANdirectory{usebib}{macros/latex/contrib/usebib}[usebib]
+\CTANdirectory{utopia}{fonts/utopia}[utopia]
+\CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize]
+\CTANdirectory{varwidth}{macros/latex/contrib/varwidth}[varwidth]
+\CTANdirectory{vc}{support/vc}[vc]
+\CTANdirectory{verbatim}{macros/latex/required/tools}[verbatim]
+\CTANdirectory{verbatimbox}{macros/latex/contrib/verbatimbox}[verbatimbox]
+\CTANdirectory{verbdef}{macros/latex/contrib/verbdef}[verbdef]
+\CTANdirectory{version}{macros/latex/contrib/version}[version]
+\CTANdirectory{vertbars}{macros/latex/contrib/vertbars}[vertbars]
+\CTANdirectory{vita}{macros/latex/contrib/vita}[vita]
+\CTANdirectory{vmargin}{macros/latex/contrib/vmargin}[vmargin]
+\CTANdirectory{vmspell}{support/vmspell}[vmspell]
+\CTANdirectory{vpp}{support/view_print_ps_pdf}[vpp]
+\CTANdirectory{vruler}{macros/latex/contrib/vruler}[vruler]
+\CTANdirectory{vtex-common}{systems/vtex/common}
+\CTANdirectory{vtex-linux}{systems/vtex/linux}[vtex-free]
+\CTANdirectory{vtex-os2}{systems/vtex/os2}[vtex-free]
+\CTANdirectory{wallpaper}{macros/latex/contrib/wallpaper}[wallpaper]
+\CTANdirectory{was}{macros/latex/contrib/was}[was]
+\CTANdirectory{wd2latex}{support/wd2latex}
+\CTANdirectory{web}{systems/knuth/dist/web}[web]
+\CTANdirectory*{winedt}{systems/win32/winedt}[winedt]
+\CTANdirectory{wordcount}{macros/latex/contrib/wordcount}[wordcount]
+\CTANdirectory{wp2latex}{support/wp2latex}[wp2latex]
+\CTANdirectory{wrapfig}{macros/latex/contrib/wrapfig}[wrapfig]
+\CTANdirectory{xargs}{macros/latex/contrib/xargs}[xargs]
+\CTANdirectory{xbibfile}{biblio/bibtex/utils/xbibfile}[xbibfile]
+\CTANdirectory{xcolor}{macros/latex/contrib/xcolor}[xcolor]
+\CTANdirectory{xcomment}{macros/generic/xcomment}[xcomment]
+\CTANdirectory*{xdvi}{dviware/xdvi}[xdvi]
+\CTANdirectory{xecjk}{macros/xetex/latex/xecjk}[xecjk]
+\CTANdirectory{xetexref}{info/xetexref}[xetexref]
+\CTANdirectory*{xfig}{graphics/xfig}[xfig]
+\CTANdirectory*{xindy}{indexing/xindy}[xindy]
+\CTANdirectory{xits}{fonts/xits}[xits]
+\CTANdirectory{xkeyval}{macros/latex/contrib/xkeyval}[xkeyval]
+\CTANdirectory{xmltex}{macros/xmltex/base}[xmltex]
+\CTANdirectory*{xpdf}{support/xpdf}[xpdf]
+\CTANdirectory{xtab}{macros/latex/contrib/xtab}[xtab]
+\CTANdirectory{xwatermark}{macros/latex/contrib/xwatermark}[xwatermark]
+\CTANdirectory{yagusylo}{macros/latex/contrib/yagusylo}[yagusylo]
+\CTANdirectory{yhmath}{fonts/yhmath}[yhmath]
+\CTANdirectory{zefonts}{fonts/zefonts}[zefonts]
+\CTANdirectory{ziffer}{macros/latex/contrib/ziffer}[ziffer]
+\CTANdirectory{zoon-mp-eg}{info/metapost/examples}[metapost-examples]
+\CTANdirectory{zwpagelayout}{macros/latex/contrib/zwpagelayout}[zwpagelayout]
+\endinput
diff --git a/help/uk-tex-faq/faq-adj-types.tex b/help/uk-tex-faq/faq-adj-types.tex
new file mode 100644
index 0000000000..0906f918f4
--- /dev/null
+++ b/help/uk-tex-faq/faq-adj-types.tex
@@ -0,0 +1,3671 @@
+% $Id: faq-adj-types.tex,v 1.50 2014/01/22 17:29:03 rf10 Exp $
+
+\section{Adjusting the typesetting}
+
+\subsection{Alternative document classes}
+
+\Question[Q-replstdcls]{Replacing the standard classes}
+
+People are forever concocting classes that replace the standard ones:
+the present author produced an \Class{ukart} class that used the
+\Package{sober} package, and a few British-specific things (such as
+appear in the \Package{babel} package's British-english
+specialisation) in the 1980s, which is still occasionally used.
+
+Similar public efforts were available well back in the days of
+\LaTeXo{}: a notable example, whose pleasing designs seem not to have
+changed much over all that time, is the \Class{ntgclass} bundle.
+Each of the standard classes is replaced by a selection of classes,
+named in Dutch, sometimes with a single numeric digit attached. So we
+have classes \Class{artikel2}, \Class{rapport1}, \Class{boek3} and
+\Class{brief}. These classes are moderately well documented in
+English.
+
+The \Class{KOMA-script} bundle (classes named \Class{scr...}) are a
+strong current contender. They are actively supported and are subject
+to sensitive development; they are comprehensive in their coverage of
+significant typesetting issues; they produce good-looking output and
+they are well documented in both English (\Package{scrguien} in the
+distribution) and German (\Package{scrguide} in the distribution).
+
+The other comparable class is \Class{memoir}. This aims to replace
+\Class{book} and \Class{report} classes directly, and (like
+\Class{KOMA-script}) is comprehensive in its coverage of small issues.
+\Class{Memoir}'s documentation (\Package{memman}) is very highly
+spoken of, and its lengthy introductory section is regularly
+recommended as a tutorial on typesetting.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}KOMA-script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[\nothtml{\rmfamily}NTGclass bundle]\CTANref{ntgclass}
+\item[sober.sty]\CTANref{sober}
+\end{ctanrefs}
+
+\Question[Q-slidecls]{Producing presentations (including slides)}
+
+Lamport's original \LaTeX{} had a separate program (Sli\TeX{}) for
+producing slides; it dates from the age when colour effects were
+produced by printing separate slides in different-coloured inks, and
+overlaying them, and was just about acceptable back then. When
+\LaTeXe{} came along, the reason Sli\TeX{} had to be a separate
+program went away, and its functionality was supplied by the
+\Class{slides} class. While this makes life a little easier for
+system administrators, it does nothing for the inferior functionality
+of the class: no-one who ``knows'' uses \Class{slides} nowadays.
+
+The `classic' alternatives have been \Class{seminar} and \Class{foils}
+(originally known as Foil\TeX{}). Both were originally designed to
+produce output on acetate foils, though subsequent work has provided
+environments in which they can be used with screen projectors (see
+below).
+
+The advent of Microsoft \ProgName{PowerPoint} (feeble though early
+versions of it were) has created a demand for ``dynamic'' slides~---
+images that develop their content in a more elaborate fashion than by
+merely replacing one foil with the next in the way that was the norm
+when \Class{slides}, \Class{foils} and \Class{seminar} were designed.
+
+The \Class{prosper} class builds on \Class{seminar} to provide dynamic
+effects and the like; it retains the ability to provide \acro{PDF} for
+a projected presentation, or to print foils for a foil-based
+presentation. The add-on package \Package{ppr-prv} adds ``preview''
+facilities (that which is commonly called ``hand-out printing''). The
+\Package{HA-prosper} package, which you load with \Class{prosper},
+mends a few bugs, and adds several facilities and slide design styles.
+The (more recent) \Class{powerdot} class is designed as a
+replacement for \Class{prosper} and \Package{HA-prosper}, co-authored
+by the author of \Package{HA-prosper}.
+
+\Class{Beamer} is a relatively easy-to-learn, yet powerful, class that
+(as its name implies) was designed for use with projection displays.
+It needs the \Package{pgf} package (for graphics support), which in
+turn requires \Package{xcolor}; while this adds to the tedium of
+installing \Class{beamer} ``from scratch'', both are good additions to
+a modern \LaTeX{} installation. \Class{Beamer} has reasonable
+facilities for producing printed copies of slides.
+
+\Class{Talk} is another highly functional, yet easy-to-learn class
+which claims to differ from the systems mentioned above, such as
+\Class{beamer}, in that it doesn't impose a slide style on you. You
+get to specify a bunch of slide styles, and you can switch from one to
+the other between slides, as you need. The class itself provides
+just the one style, in the package \Package{greybars}: the author's
+suggestion that users should contribute their own has been
+enthusiastically accepted~--- see (for example) the % !line break
+\href{http://deic.uab.es/~iblanes/beamer_gallery/}{Beamer Gallery}.
+
+\Package{Lecturer} is a \emph{generic} solution (it works with
+\plaintex{}, \latex{} and \context{}~mk~ii, but not~--- yet~--- with
+\context{}~mk iv). By separating the functionality needed for a
+presentation (using \tex{} for typesetting, and \acro{PDF} functions
+for layering and dynamic effects) a clear structure emerges. While it
+doesn't have the range of ``themes'' (presentation styles) of
+\Class{beamer} it seems a useful alternative candidate.
+
+\Package{Present} is designed for use with \plaintex{} only; its
+design is simple, to the extent that its author hopes that users will
+themselves be able to tune its macros.
+
+\ProgName{Ppower4} (commonly known as \ProgName{pp4}) is a
+\ProgName{Java}-based support program that will postprocess
+\acro{PDF}, to `animate' the file at places you've marked with
+commands from one of the \ProgName{pp4} packages. The commands don't
+work on \acro{PDF} that has come from \ProgName{dvips} output; they
+work with \acro{PDF} generated by \PDFLaTeX{}, \LaTeX{}, or
+\ProgName{dvipdfm} running on \LaTeX{} output.
+
+\Package{Pdfscreen} and \Package{texpower} are add-on packages that
+permit dynamic effects in documents formatted in ``more modest''
+classes; \Package{pdfscreen} will even allow you to plug
+``presentation effects'' into an \Class{article}-class document.
+
+% ifmslide
+%\noindent ifmslide: a few slides extolling virtues in \File{doc/ifmman.pdf}
+
+A more detailed examination of the alternatives (including examples
+of code using many of them) may be found at Michael Wiedmann's fine
+\URL{http://www.miwie.org/presentations/presentations.html}
+
+\CONTeXT{} users will find that much (if not all) of what they need is
+already in \CONTeXT{} itself; there's a useful summary of what's
+available, with examples, in
+\URL{http://wiki.contextgarden.net/Presentation_Styles}
+%
+\begin{ctanrefs}
+\item[beamer.cls]Download all of \CTANref{beamer}
+\item[foils.cls]\CTANref{foiltex}
+\item[greybars.sty]distributed with \CTANref{talk}
+\item[HA-prosper.sty]\CTANref{ha-prosper}
+%\item[ifmslide.sty]\CTANref{ifmslide}
+\item[lecturer.sty]\CTANref{lecturer}
+\item[seminar.cls]\CTANref{seminar}
+\item[pdfscreen.sty]\CTANref{pdfscreen}
+\item[pgf.sty]\CTANref{pgf}
+\item[powerdot.cls]\CTANref{powerdot}
+\item[pp4]\CTANref{ppower4}
+\item[ppr-prv.sty]\CTANref{ppr-prv}
+\item[present.tex]\CTANref{present}
+\item[prosper.cls]\CTANref{prosper}
+\item[talk.cls]\CTANref{talk}
+\item[texpower]\CTANref{texpower}
+\item[xcolor.sty]\CTANref{xcolor}
+\end{ctanrefs}
+
+\Question[Q-poster]{Creating posters with \LaTeX{}}
+
+There is no complete ``canned solution'' to creating a poster (as, for
+example, classes like \Class{seminar}, \Class{powerdot} and
+\Class{beamer} serve for creating presentations in a variety of
+styles).
+
+The nearest approach to the complete solution is the \Class{sciposter}
+class, which provides the means to produce really rather good posters
+according to the author's required style. A complete worked example
+is provided with the distribution
+
+Otherwise, there is a range of tools, most of which are based on the
+\Class{a0poster} class, which sets up an appropriately-sized piece of
+paper, sets font sizes appropriately, and leaves you to your own
+devices.
+
+Having used \Class{a0poster}, you can of course slog it out, and write
+all your poster as an unadorned \LaTeX{} document (presumably in
+multiple columns, using the \Package{multicol} package), but it's not really
+necessary: the (straightforward) \Package{textpos} package provides a
+simple way of positioning chunks of text, or tables or figures, on the
+poster page.
+
+More sophisticated is the \Package{flowfram} package, whose basic aim
+in life is flowing text from one box on the page to the next. One of
+the package's design aims seems to have been the production of
+posters, and a worked example is provided. The author of
+\Package{flowfram} has an experimental tool called
+\href{http://www.dickimaw-books.com/software.html#jpgfdraw}{JpgfDraw}, which
+allows you to construct the outline of frames for use with
+\Package{flowfram}.
+
+The \Package{beamerposter} package is added to a % ! line break
+\Qref*{\Class{beamer} document}{Q-slidecls} to enable the user to work
+as if in a \Class{a0poster} class. Thus \Class{beamer}'s neat
+provisions for layout may be used when creating the poster.
+Documentation of \Package{beamerposter} is sparse, but an example file
+allows the user to get a grip on what's available.
+
+Despite the relative shortage of tools, there are a fair few web pages
+that explain the process (mostly in terms of the \Class{a0poster}
+route):
+\begin{itemize}
+\item from Norman Gray, % ! line break; this item checked 2012-10-02
+ \href{http://nxg.me.uk/docs/posters/}{Producing posters using \LaTeX{}};
+\item from Nicola Talbot, % ! line break; this item checked 2012-10-02
+ \href{http://www.dickimaw-books.com/latex/posters/}{Creating technical posters with \LaTeX{}}
+\item From Rob Clark % ! line break; this item checked 2012-10-02
+ \href{http://homepages.inf.ed.ac.uk/robert/posters/advanced.html}{Advanced LaTeX Posters} % ! line break
+ (which has links to code samples);
+\item from Brian Wolven, % ! line break this item failed 2012-10-02
+ \href{http://fuse.pha.jhu.edu/~wolven/posters.html}{LaTeX Poster Macros, Examples, and Accessories} % ! line break
+ (this page also provides macros and other support suggestions); and
+\item from ``\emph{pjh}'' % ! line break; this item checked 2012-10-02
+ \href{http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html}{Making and printing a poster with \LaTeX{}}, % ! line break
+ which covers the specific issue of dealing with University of
+ Florida styled poster (offering supporting material as necessary),
+ but has hints which are generally useful.
+\end{itemize}
+\begin{ctanrefs}
+\item[a0poster.cls]\CTANref{a0poster}
+\item[beamer.cls]\CTANref{beamer}
+\item[beamerposter.sty]\CTANref{beamerposter}
+\item[flowfram.sty]\CTANref{flowfram}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
+\item[sciposter.cls]\CTANref{sciposter}
+\item[textpos.sty]\CTANref{textpos}
+\end{ctanrefs}
+
+\Question[Q-thesis]{Formatting a thesis in \LaTeX{}}
+
+Thesis styles are usually very specific to your University, so it's
+usually not profitable to ask around for a package outside your own
+University. Since many Universities (in their eccentric way) still
+require double-spaced thesis text, you may also need separately to set
+up \Qref*{double spacing}{Q-linespace}.
+
+If you want to write a new thesis class of your own, a good place to
+start is the University of California style, but remember that it's
+often difficult to produce a thesis that both looks good and conforms
+with the style that your Univeristy demands.
+\begin{ctanrefs}
+\item[UC thesis style]\CTANref{ucthesis}
+\end{ctanrefs}
+
+\Question[Q-journalpaper]{Setting papers for journals}
+
+Publishers of journals have a wide range of requirements for the
+presentation of papers, and while many publishers do accept electronic
+submissions in \AllTeX{}, they don't often submit recommended macros to
+public archives.
+
+Nevertheless, there are considerable numbers of macros of one sort or
+another available on \acro{CTAN}; searching for your journal name in
+the CTAN catalogue~--- see % ! line break
+\Qref{searching \acro{CTAN}}{Q-findfiles})~---
+may well turn up what you're seeking.
+
+Failing that, you may be well advised to contact the prospective
+publisher of your paper; many publishers have macros on their own web
+sites, or otherwise available only upon application.
+
+Check that the publisher is offering you macros suitable to an
+environment you can use: a few still have no macros for current
+\LaTeX{}, for example, claiming that \LaTeXo{} is good enough\dots{}
+
+Some publishers rekey anything sent them anyway, so that it doesn't
+really matter what macros you use. Others merely encourage you to use
+as few extensions of a standard package as possible, so that they will
+find it easy to transform your paper to their own internal form.
+
+\Question[Q-multidoc]{A `report' from lots of `article's}
+
+This is a requirement, for example, if one is preparing the
+proceedings of a conference whose papers were submitted in \LaTeX{}.
+
+The nearest things to canned solutions are Peter Wilson's
+\Class{combine} and Federico Garcia's \Class{subfiles} classes, but
+many approaches have been proposed. Each of of the offerings has its
+own advantages; in particular, several distinctly light-weight
+solutions (for example, \Package{includex} and \Package{docmute}) are
+available, well-suited to less formal documents.
+
+\Class{Combine} defines the means to `\csx{import}' entire documents,
+and provides means of specifying significant features of the layout of
+the document, as well as a global table of contents, and so on. The
+complete set of facilities is pretty complex. An auxiliary package,
+\Package{combinet}, allows use of the \csx{title}s and \csx{author}s
+(etc.\@) of the \csx{import}ed documents to appear in the global table
+of contents. The basic structure of a combined document would be:
+\begin{quote}
+\begin{verbatim}
+\documentclass[...]{combine}
+...
+\begin{document}
+...
+<introductory materiel>
+...
+\begin{papers}
+% title and author of first article,
+% to go the the main ToC
+\coltoctitle{...}
+\coltocauthor{...}
+\label{art1}
+\import{art1}
+...
+\end{papers}
+...
+<acknowledgements, etc.>
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+
+The \Class{subfiles} class is used in the component files of a multi-file
+project, and the corresponding \Package{subfiles} package is used in the
+master file; so the structure of the master file looks like:
+\begin{quote}
+\begin{verbatim}
+\documentclass{<whatever>}
+...
+\usepackage{subfiles}
+...
+\begin{document}
+...
+\subfile{subfile_name}
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+while a subfile has the structure:
+\begin{quote}
+\begin{verbatim}
+\documentclass[mainfile_name]{subfiles}
+\begin{document}
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+Arrangements may be made so that the component files will
+be typeset using different page format, etc., parameters than those
+used when they are typeset as a part of the main file.
+
+A more `raw' toolkit is offered by Matt Swift's \Package{includex} and
+\Package{newclude} packages, both part of the \Package{frankenstein}
+bundle. Note that Matt believes \Package{includex} is obsolete
+(though it continues to work for this author); furthermore, its
+replacement, \Package{newclude} remains ``in development'', as it has
+been since 1999.
+
+Both \Package{includex} and \Package{newclude} enable you to
+`\csx{includedoc}' complete articles (in the way that you
+`\csx{include}' chapter files in an ordinary report). The preamble
+(everything up to \cmdinvoke{begin}{document}), and everything after
+\cmdinvoke{end}{document}, is ignored by both packages. Thus the
+packages don't ``do the whole job'' for you, though: you need to
+analyse the package use of the individual papers, and ensure that a
+consistent set is loaded in the preamble of the main report. (Both
+packages require \Package{moredefs}, which is also part of the
+bundle.)
+
+A neat (and simple) toolkit is offered by the
+\Package{docmute} package; once the package is loaded, anything
+between \cmdinvoke{documentclass}[...]{...} and
+\cmdinvoke{begin}{document} in an \csx{input}'ed or \csx{include}'d
+document is ignored, and then the input is processed up to
+\cmdinvoke{end}{document} in the input file. The package does nothing
+about \csx{usepackage} (or anything else) in the preamble of the
+included document; it's up to the user to ensure that any packages
+needed are loaded, and any other necessary configuration is done, in
+the parent document.
+
+The \Package{standalone} package develops on the ideas of
+\Package{docmute}; it was designed to meet the needs of users who are
+developing images from one of the more extreme new graphics packages
+(notably \Package{pgf/tikz}) where the compile time of the graphics is
+such that separate compilation is very desirable.
+\Package{Standalone} provides a means of developing the graphics in a
+convenient way, detached from the development of the document as a
+whole; its value for use in multiple documents is clear.
+
+The user includes the \Package{standalone} package in the main
+document, and each subfile uses the \Class{standalone} class.
+(\Class{Standalone} uses \Class{article} for the ``real'' work in
+stand-alone mode, but it may be asked to use another).
+
+The real difference from the \Package{docmute} package is
+flexibility. In particular, you can ask that the preambles of the
+included documents be gathered up, so that you can construct a good
+preamble for the master document.
+
+A final ``compile-together'' approach comes from the \Package{subdocs}
+package. The driver file contains a \csx{subdocuments} command:
+\begin{quote}
+\cmdinvoke*{subdocuments}[options]{file1, file2, ...}
+\end{quote}
+(the optional arguments provide layout options, such as control over
+whether \csx{clearpage} or \csx{cleardoublepage} are used between the
+files). Each of the sub-files will execute
+\begin{quote}
+ \cmdinvoke*{usepackage}[master]{subdocs}
+\end{quote}
+to declare the name, \texttt{\emph{master}}, of the calling file;
+each of the subfiles reads all the \extension{aux} files, so that
+tables of contents may be produced.
+
+A completely different approach is to use the \Package{pdfpages}
+package, and to include articles submitted in \acro{PDF} format into a
+a \acro{PDF} document produced by \PDFLaTeX{}. The package
+defines an \csx{includepdf} command, which takes arguments similar to
+those of the \csx{includegraphics} command. With keywords in the
+optional argument of the command, you can specify which pages you want
+to be included from the file named, and various details of the layout
+of the included pages.
+\begin{ctanrefs}
+\item[combine.cls]\CTANref{combine}
+\item[combinet.sty]\CTANref{combine}
+\item[docmute.sty]\CTANref{docmute}
+\item[includex.sty]Distributed in the ``unsupported'' part of
+ \CTANref{frankenstein}[includex]
+\item[moredefs.sty]Distributed as part of \CTANref{frankenstein}[moredefs]
+\item[newclude.sty]Distributed as part of \CTANref{frankenstein}[newclude]
+\item[pdfpages.sty]\CTANref{pdfpages}
+\item[standalone.cls, standalone.sty]\CTANref{standalone}
+\item[subdocs.sty]Distributed as part of \CTANref{bezos}[subdocs]
+\item[subfiles.cls, etc.]\CTANref{subfiles}
+\end{ctanrefs}
+
+\Question[Q-cv]{\emph{Curriculum Vitae} (R\'esum\'e)}
+
+Andrej Brodnik's class, \Class{vita}, offers a framework for producing
+a \emph{curriculum vitae}. The class may be customised both for
+subject (example class option files support both computer scientists
+and singers), and for language (both the options provided are
+available for both English and Slovene). Extensions may be written by
+creating new class option files, or by using macros defined in the
+class to define new entry types, etc.
+
+Didier Verna's class, \Class{curve}, is based on a model in which
+the \acro{CV} is made of a set of \emph{rubrics} (each one dealing
+with a major item that you want to discuss, such as `education', `work
+experience', etc). The class's documentation is supported by a couple
+of example files, and an emacs mode is provided.
+
+Xavier Danaux offers a class \Class{moderncv} which supports
+typesetting modern \emph{curricula vitarum}, both in a classic and in a
+casual style. It is fairly customizable, allowing you to define your
+own style by changing the colours, the fonts, etc.
+
+The European Commission has recommended a format for % ! line break
+\emph{curricula vitarum} within Europe, and Nicola Vitacolonna has
+developed a class \Class{europecv} to produce it. While (by his own
+admission) the class doesn't solve all problems, it seems well-thought
+out and supports all current official EU languages (together with a
+few non-official languages, such as Catalan, Galician and Serbian).
+
+The alternative to using a separate class is to impose a package on
+one of the standard classes. An example,
+Axel Reichert's \Package{currvita} package, has been recommended to the
+\acro{FAQ} team. Its output certainly looks good.
+
+There is also a \LaTeXo{} package \Package{resume}, which comes with
+little but advice \emph{against} trying to use it.
+\begin{ctanrefs}
+\item[currvita.sty]\CTANref{currvita}
+\item[curve.cls]\CTANref{curve}
+\item[europecv.cls]\CTANref{europecv}
+\item[moderncv.cls]\CTANref{moderncv}
+\item[resume.sty]\CTANref{resume}
+\item[vita.cls]\CTANref{vita}
+\end{ctanrefs}
+
+\Question[Q-letterclass]{Letters and the like}
+
+\LaTeX{} itself provides a \Class{letter} document class, which is
+widely disliked; the present author long since gave up trying with
+it. If you nevertheless want to try it, but are irritated by its way
+of vertically-shifting a single-page letter, try the following hack:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\let\@texttop\relax
+\makeatother
+\end{verbatim}
+\end{quote}
+in the preamble of your file.
+
+Doing-it-yourself is a common strategy; Knuth (for use with
+\plaintex{}, in the \TeX{}book), and Kopka and Daly (in their Guide to
+\LaTeX{}) offer worked examples. (The latest version of Knuth's
+macros appear in his ``local library'' dump on the archive, which is
+updated in parallel with new versions of \TeX{}~--- so not very often\dots{})
+
+Nevertheless, there \emph{are} contributed alternatives~--- in fact
+there are an awfully large number of them: the following list, of
+necessity, makes but a small selection.
+
+The largest, most comprehensive, class is \Class{newlfm}; the \texttt{lfm}
+part of the name implies that the class can create letters, faxes and
+memoranda. The documentation is voluminous, and the package seems
+very flexible.
+
+Other classes recommended for inclusion in this \acro{FAQ} are
+\Class{akletter} and \Class{isodoc}.
+
+The \Class{dinbrief} class, while recommended, is only documented in
+German.
+
+There are letter classes in each of the excellent
+\Class{KOMA-script} (\Class{scrlttr2}: documentation is available in
+English) and \Package{ntgclass} (\Class{brief}: documentation in Dutch
+only) bundles. While these are probably good (since the bundles
+themselves inspire trust) they've not been specifically recommended by
+any users.
+\begin{ctanrefs}
+\item[akletter.cls]\CTANref{akletter}
+\item[brief.cls]Distributed as part of \CTANref{ntgclass}
+\item[dinbrief.cls]\CTANref{dinbrief}
+\item[isodoc.cls]\CTANref{isodoc}
+\item[\nothtml{\rmfamily}Knuth's letter.tex]\CTANref{knuth-letter}
+\item[newlfm.cls]\CTANref{newlfm}
+\item[scrlttr2.cls]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+
+\Question[Q-extsizes]{Other ``document font'' sizes?}
+
+The \LaTeX{} standard classes have a concept of a (base) ``document
+font'' size; this size is the basis on which other font sizes (those
+from \csx{tiny} to \csx{Huge}) are determined. The classes are designed
+on the assumption that they won't be used with sizes other than the
+set that \LaTeX{} offers by default (10--12pt), but people regularly
+find they need other sizes. The proper response to such a requirement
+is to produce a new design for the document, but many people don't
+fancy doing that.
+
+A simple solution is to use the \Package{extsizes} bundle. This
+bundle offers ``extended'' versions of the article, report, book and
+letter classes, at sizes of 8, 9, 14, 17 and 20pt as well as the
+standard 10--12pt. Since little has been done to these classes other
+than to adjust font sizes and things directly related to them, they
+may not be optimal~--- but they are at least practical.
+
+More satisfactory are the \emph{\acro{KOMA}-script} classes, which are
+designed to work properly with the class option files that come with
+\Package{extsizes}, and the \Class{memoir} class that has its own
+options for document font sizes 9pt--12pt, 14pt, 17pt, 20pt, 25pt,
+30pt, 36pt, 48pt and 60pt. The classes also offer size setup for any
+old font size, and the \Package{scrextend} package can extend this
+facility for use with any class:
+\begin{quote}
+\begin{verbatim}
+\usepackage[fontsize=12.3]{scrextend}
+\end{verbatim}
+\end{quote}
+will indeed set up the main document font to have size \texttt{12.3pt}
+with an appropriate default baselineskip. The package ``knows'' about
+\emph{\acro{KOMA}-script}'s default sizes, and for eccentric sizes
+such as the example, it will produce a warning:
+\begin{quote}
+\begin{verbatim}
+Using fallback calculation to setup font sizes
+\end{verbatim}
+\end{quote}
+(users should avoid becoming excited about that\dots{}). The package
+suffers from the same problem as does \Package{extsizes}: the
+resulting font sizes are the \emph{only} feature of the document that
+is changed, and the appearance of the resulting document will probably
+not be as good as if the document class had been designed for use at
+the size chosen.
+
+Many classes, designed to produce typeset results other than on
+``ordinary'' paper, will have their own font size mechanisms and
+ranges of sizes. This is true, for example, of % ! line break
+\Qref*{poster classes}{Q-poster} (such as \Class{a0poster}), and of
+\Qref*{presentation and lecturing classes}{Q-slidecls} (such as
+\Class{beamer}.
+\begin{ctanrefs}
+\item[a0poster.cls]\CTANref{a0poster}
+\item[beamer.cls]\CTANref{beamer}
+\item[extsizes bundle]\CTANref{extsizes}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[scrextend.sty]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+\LastEdit{2012-11-01}
+
+\subsection{Document structure}
+
+\Question[Q-titlsty]{The style of document titles}
+
+The \Package{titling} package provides a number of facilities that
+permit manipulation of the appearance of a \csx{maketitle} command, the
+\csx{thanks} commands within it, and so on. The package also defines a
+\environment{titlingpage} environment, that offers something in between the
+standard classes' \pkgoption{titlepage} option and the \environment{titlepage}
+environment, and is itself somewhat configurable.
+
+The memoir class includes all the functionality of the
+\Package{titling} package, while the \Class{KOMA-script} classes have
+their own range of different titling styles.
+
+Finally, the indefatigable Vincent Zoonekynd supplies examples of how
+to program alternative % don't let this \href suffer a line-break
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html}{title styles}.
+The web page is not useful to users unless they are willing to do
+their own \LaTeX{} programming.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[titling.sty]\CTANref{titling}
+\end{ctanrefs}
+
+\Question[Q-secthead]{The style of section headings}
+
+Suppose that the editor of your favourite journal has specified that section
+headings must be centred, in small capitals, and subsection headings ragged
+right in italic, but that you don't want to get involved in the sort of
+programming described in section 2.2 of \emph{The \LaTeX{} Companion}
+\begin{narrowversion} % really non-hyper
+ (\Qref{}{Q-latex-books}; the programming itself is discussed in
+ \Qref[question]{}{Q-atsigns}).
+\end{narrowversion}
+\begin{wideversion} % really hyper
+ (see \Qref{\latex{} books}{Q-latex-books}; the
+ \Qref{programming}{Q-atsigns} itself is discussed elsewhere in this
+ \acro{FAQ}).
+\end{wideversion}
+The following hack will
+probably satisfy your editor. Define yourself new commands
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand{\ssection}[1]{%
+ \section[#1]{\centering\normalfont\scshape #1}}
+\newcommand{\ssubsection}[1]{%
+ \subsection[#1]{\raggedright\normalfont\itshape #1}}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion} % really non-hyper
+\begin{verbatim}
+\newcommand{\ssection}[1]{%
+ \section[#1]{\centering
+ \normalfont\scshape #1}}
+\newcommand{\ssubsection}[1]{%
+ \subsection[#1]{\raggedright
+ \normalfont\itshape #1}}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+and then use \csx{ssection} and \csx{ssubsection} in place of
+\csx{section} and \csx{subsection}. This isn't perfect: section numbers
+remain in bold, and starred forms need a separate redefinition.
+
+The \Package{titlesec} package offers a structured approach to the
+problem, based on redefinition of the sectioning and chapter commands
+themselves. This approach allows it to offer radical adjustment: its
+options provide (in effect) a toolbox for designing your own
+sectioning commands' output.
+
+The \Package{sectsty} package provides a more simply structured set of
+tools; while it is less powerful than is \Package{titlesec}, it is
+perhaps preferable for minor adjustments, since you can use it after
+having read a smaller proportion of the manual.
+
+The \Package{fncychap} package provides a nice collection of customised
+chapter heading designs. The \Package{anonchap} package provides a
+simple means of typesetting chapter headings ``like section headings''
+(i.e., without the ``Chapter'' part of the heading); the
+\Package{tocbibind} package provides the same commands, in pursuit of
+another end.
+
+The \Class{memoir} class includes facilities that match
+\Package{sectsty} and \Package{titlesec}, as well as a bundle of
+chapter heading styles (including an \Package{anonchap}-equivalent).
+The \Class{KOMA-script} classes also have sets of tools that provide
+equivalent functionality, notably formatting specifications \csx{partformat},
+\csx{chapterformat}, \csx{sectionformat}, \dots{}, as well as several
+useful overall formatting specifications defined in class options.
+
+Finally, the indefatigable Vincent Zoonekynd supplies examples of how
+to program alternative % don't let these \href suffer line-breaks
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html}{chapter heading styles}
+and
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html}{section heading styles}.
+The web pages provide programming examples, and expect users to adapt
+them to their own \LaTeX{} use.
+\begin{ctanrefs}
+\item[anonchap.sty]\CTANref{anonchap}
+\item[fncychap.sty]\CTANref{fncychap}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[sectsty.sty]\CTANref{sectsty}
+\item[titlesec.sty]\CTANref{titlesec}
+\item[tocbibind.sty]\CTANref{tocbibind}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-appendix]{Appendixes}
+
+\LaTeX{} provides an exceedingly simple mechanism for appendixes: the
+command \csx{appendix} switches the document from generating sections
+(in \Class{article} class) or chapters (in \Class{report} or
+\Class{book} classes) to producing appendixes. Section or chapter
+numbering is restarted and the representation of the counter switches
+to alphabetic. So:
+\begin{quote}
+\begin{verbatim}
+\section{My inspiration}
+...
+
+\section{Developing the inspiration}
+...
+
+\appendix
+\section{How I became inspired}
+...
+\end{verbatim}
+\end{quote}
+would be typeset (in an \Class{article} document) something like:
+\begin{quote}
+\textbf{1~~My inspiration}
+
+\dots{}
+
+\textbf{2~~Developing the inspiration}
+
+\dots{}
+
+\textbf{A~~How I became inspired}
+
+\dots{}
+\end{quote}
+which is quite enough for many ordinary purposes. Note that, once
+you've switched to typesetting appendixes, \LaTeX{} provides you with
+no way back~--- once you've had an appendix, you can no longer have an
+``ordinary'' \csx{section} or \csx{chapter}.
+
+The \Package{appendix} provides several ways of elaborating on this
+simple setup. Straightforward use of the package allows you to have a
+separate heading, both in the body of the document and the table of
+contents; this would be achieved by
+\begin{quote}
+\begin{verbatim}
+\usepackage{appendix}
+...
+\appendix
+\appendixpage
+\addappheadtotoc
+\end{verbatim}
+\end{quote}
+The \csx{appendixpage} command adds a separate title ``Appendices''
+above the first appendix, and \csx{addappheadtotoc} adds a similar
+title to the table of contents. These simple modifications cover many
+people's needs about appendixes.
+
+The package also provides an \environment{appendices} environment,
+which provides for fancier use. The environment is best controlled by
+package options; the above example would be achieved by
+\begin{quote}
+\begin{verbatim}
+\usepackage[toc,page]{appendix}
+...
+\begin{appendices}
+...
+\end{appendices}
+\end{verbatim}
+\end{quote}
+The great thing that the \environment{appendices} environment gives
+you, is that once the environment ends, you can carry on with sections
+or chapters as before~--- numbering isn't affected by the intervening
+appendixes.
+
+The package provides another alternative way of setting appendixes, as
+inferior divisions in the document. The \environment{subappendices}
+environment allows you to put separate appendixes for a particular
+section, coded as \csx{subsection}s, or for a particular chapter, coded
+as \csx{section}s. So one might write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{appendix}
+...
+\section{My inspiration}
+...
+\begin{subappendices}
+\subsection{How I became inspired}
+...
+\end{subappendices}
+
+\section{Developing the inspiration}
+...
+\end{verbatim}
+\end{quote}
+Which will produce output something like:
+\begin{quote}
+\textbf{1~~My inspiration}
+
+\dots{}
+
+\textbf{1.A~~How I became inspired}
+
+\dots{}
+
+\textbf{2~~Developing the inspiration}
+
+\dots{}
+\end{quote}
+
+There are many other merry things one may do with the package; the
+user is referred to the package documentation for further details.
+
+The \Class{memoir} class includes the facilities of the
+\Package{appendix} package. The \Class{KOMA-script} classes offer a
+\csx{appendixprefix} command for manipulating the appearance of appendixes.
+\begin{ctanrefs}
+\item[appendix.sty]\CTANref{appendix}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-secindent]{Indent after section headings}
+
+\LaTeX{} implements a style that doesn't indent the first paragraph
+after a section heading. There are coherent reasons for this, but not
+everyone likes it.
+The \Package{indentfirst} package
+suppresses the mechanism, so that the first paragraph is
+indented.
+\begin{ctanrefs}
+\item[indentfirst.sty]Distributed as part of \CTANref{2etools}[indentfirst]
+\end{ctanrefs}
+
+\Question[Q-subsubsub]{How to create a \csx{subsubsubsection}}
+
+\LaTeX{}'s set of ``sections'' stops at the level of
+\csx{subsubsection}. This reflects a design decision by Lamport~---
+for, after all, who can reasonably want a section with such huge
+strings of numbers in front of it?
+
+In fact, \LaTeX{} standard classes \emph{do} define ``sectioning''
+levels lower than \csx{subsubsection}, but they don't format them like
+sections (they're not numbered, and the text is run-in after the
+heading). These deeply inferior section commands are \csx{paragraph}
+and \csx{subparagraph}; you can (if you \emph{must}) arrange that these
+two commands produce numbered headings, so that you can use them as
+\csx{subsubsubsection}s and lower.
+
+The \Package{titlesec} package provides a sensible set of macros for
+you to adjust the definitions of the sectioning macros, and it may be
+used to transform a \csx{paragraph}'s typesetting so that it looks
+like that of a \csx{section}.
+
+If you want to program the change yourself, you'll find that the
+commands (\csx{section} all the way down to \csx{subparagraph}) are
+defined in terms of the internal \csx{@startsection} command, which
+takes 6~arguments. Before attempting this sort of work, you are well
+advised to read the \LaTeX{} sources (\File{ltsect.dtx} in the
+\LaTeX{} distribution) and the source of the standard packages
+(\File{classes.dtx}), or to make use of the % ! line break
+\Qref*{\LaTeX{} Companion}{Q-latex-books}, which
+discusses the use of \csx{@startsection} for this sort of thing.
+
+You will note that Lamport didn't go on adding ``\texttt{sub}'' to the
+names of sectioning commands, when creating commands for the lowest
+levels of a document. This would seem sensible to any but the most
+rigorous stickler for symmetry~--- it would surely challenge pretty
+much anyone's reading of the source of a document, if there was a need
+to distinguish \csx{subsubsubsection} and \csx{subsubsubsubsection}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeX{} source]\CTANref{latex}
+\item[titlesec.sty]\CTANref{titlesec}
+\end{ctanrefs}
+\LastEdit{2012-02-14}
+
+\Question[Q-captsty]{The style of captions}
+
+Changes to the style of captions may be made by redefining the commands
+that produce the caption. So, for example, \csx{fnum@figure} (which
+produces the float number for figure floats) may be redefined, in a
+package of your own, or between
+\Qref*{\csx{makeatletter}--\csx{makeatother}}{Q-atsigns}:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\renewcommand{\fnum@figure}{\textbf{Fig.~\thefigure}}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\renewcommand{\fnum@figure}%
+ {\textbf{Fig.~\thefigure}}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+which will cause the number to be typeset in bold face. (Note that
+the original definition used \nothtml{\csx{figurename}~--- }%
+\Qref{\csx{figurename}}{Q-fixnam}.) More elaborate changes can be
+made by patching the \csx{caption} command, but since there are
+packages to do the job, such changes (which can get rather tricky)
+aren't recommended for ordinary users.
+
+The \Package{float} package provides some control of the appearance of
+captions, though it's principally designed for the creation of
+non-standard floats. The \Package{caption} and \Package{ccaption}
+(note the double ``\emph{c}'') packages provide a range of different
+formatting options.
+
+\Package{ccaption} also provides `continuation' captions and captions
+that can be placed outside of float environments. The (very simple)
+\Package{capt-of} package also allows captions outside a float
+environment. Note that care is needed when doing things that assume
+the sequence of floats (as in continuation captions), or potentially
+mix non-floating captions with floating ones.
+
+The \Class{memoir} class includes the facilities of the
+\Package{ccaption} package; the \Class{KOMA-script} classes also
+provide a wide range of caption-formatting commands.
+
+The documentation of \Package{caption} is available by processing a
+file \File{manual.tex}, which is created when you unpack
+\File{caption.dtx}
+
+Note that the previously-recommended package \Package{caption2} has
+now been overtaken again by \Package{caption}; however,
+\Package{caption2} remains available for use in older documents.
+\begin{ctanrefs}
+\item[caption.sty]\CTANref{caption}
+\item[capt-of.sty]\CTANref{capt-of}
+\item[ccaption.sty]\CTANref{ccaption}
+\item[float.sty]\CTANref{float}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-fancyhdr]{Alternative head- and footlines in \LaTeX{}}
+\keywords{headings header footer headline footline}
+
+The standard \LaTeX{} document classes define a small set of `page
+styles' which specify head- and footlines for your document (though
+they can be used for other purposes, too). The standard set is very
+limited, but \LaTeX{} is capable of much more. The internal
+\LaTeX{} coding needed to change page styles is not particularly
+challenging, but there's no need~--- there are packages that provide
+useful abstractions that match the way we typically think about these
+things.
+
+The \Package{fancyhdr} package provides
+simple mechanisms for defining pretty much every head- or footline
+variation you could want; the directory also contains some
+documentation and one or two smaller packages. \Package{Fancyhdr}
+also deals with the tedious behaviour of the standard styles with
+\Qref*{initial pages}{Q-nopageno}, by enabling you to define
+different page styles for initial and for body pages.
+
+While \Package{fancyhdr} will work with \Class{KOMA-script} classes,
+an alternative package, \Package{scrpage2}, eases integration with the
+classes. \Package{Scrpage2} may also be used as a \Package{fancyhdr}
+replacement, providing similar facilities. The \Class{KOMA-script}
+classes themselves permit some modest redefinition of head- and
+footlines, without the use of the extra package.
+
+\Class{Memoir} also contains the functionality of \Package{fancyhdr},
+and has several predefined styles.
+
+Documentation of \Package{fancyhdr} is distributed with the package,
+in a separate file; documentation of \Package{scrpage2} is integrated
+with the \File{scrgui*} documentation files that are distributed with
+the \Class{KOMA-script} classes.
+\begin{ctanrefs}
+\item[fancyhdr.sty]\CTANref{fancyhdr}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-widefigs]{Wide figures in two-column documents}
+
+Floating figures and tables ordinarily come out the same width as the
+page, but in two-column documents they're restricted to the width of
+the column. This is sometimes not good enough; so there are alternative
+versions of the float environments~--- in two-column documents,
+\texttt{figure*} provides a floating page-wide figure (and \texttt{table*} a
+page-wide table) which will do the necessary.
+
+The ``\texttt{*}''ed float environments can only appear at the top of a page,
+or on a whole page~--- \texttt{h} or \texttt{b} float placement directives are
+simply ignored.
+
+Unfortunately, page-wide equations can only be accommodated inside
+float environments. You should include them in \texttt{figure} environments,
+or use the \Package{float} or \Package{ccaption}package to define a
+new float type.
+\begin{ctanrefs}
+\item[ccaption.sty]\CTANref{ccaption}
+\item[float.sty]\CTANref{float}
+\end{ctanrefs}
+
+\Question[Q-onecolabs]{1-column abstract in 2-column document}
+
+One often requires that the abstract of a paper should appear across
+the entire page, even in a two-column paper. The required trick is:
+\begin{quote}
+\begin{verbatim}
+\documentclass[twocolumn]{article}
+...
+\begin{document}
+... % \author, etc
+\twocolumn[
+ \begin{@twocolumnfalse}
+ \maketitle
+ \begin{abstract}
+ ...
+ \end{abstract}
+ \end{@twocolumnfalse}
+ ]
+\end{verbatim}
+\end{quote}
+Unfortunately, with the above \csx{thanks} won't work in the
+\csx{author} list. If you need such specially-numbered footnotes, you
+can make them like this:
+\begin{quote}
+\begin{verbatim}
+\title{Demonstration}
+\author{Me, You\thanks{}}
+\twocolumn[
+ ... as above ...
+]
+{
+ \renewcommand{\thefootnote}%
+ {\fnsymbol{footnote}}
+ \footnotetext[1]{Thanks for nothing}
+}
+\end{verbatim}
+\end{quote}
+and so on.
+
+As an alternative, among other facilities the \Package{abstract} package
+provides a
+\csx{saythanks} command and a \environment{onecolabstract} environment
+which remove the need to fiddle with the \csx{thanks} and
+footnoting. They can be used like this:
+\begin{quote}
+\begin{verbatim}
+\twocolumn[
+ \maketitle % full width title
+ \begin{onecolabstract} % ditto abstract
+ ... text
+ \end{onecolabstract}
+]
+\saythanks % typeset any \thanks
+\end{verbatim}
+\end{quote}
+The \Class{memoir} class offers all the facilities of \Package{abstract}.
+\begin{ctanrefs}
+\item[abstract.sty]\CTANref{abstract}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-reallyblank]{Really blank pages between chapters}
+
+If you're using the standard classes, you need to take special action;
+the \Class{memoir} class and the \Class{Koma-Script} classes provide
+their own support for this~--- see below.
+
+\Class{Book} (by default) and \Class{report} (with \pkgoption{openright} class
+option) ensure that each chapter starts on a right-hand (recto) page;
+they do this by inserting a \csx{cleardoublepage} command between
+chapters (rather than a mere \csx{clearpage}). The empty page thus
+created gets to have a normal running header, which some people don't
+like.
+
+The (excellent) \Package{fancyhdr} manual covers this issue, basically
+advising the creation of a command \csx{clearemptydoublepage}:
+\begin{quote}
+\begin{verbatim}
+\let\origdoublepage\cleardoublepage
+\newcommand{\clearemptydoublepage}{%
+ \clearpage
+ {\pagestyle{empty}\origdoublepage}%
+}
+\end{verbatim}
+\end{quote}
+The ``obvious'' thing is then to use this command to replace
+\csx{cleardoublepage} in a patched version of the \csx{chapter} command.
+(Make a package of your own containing a copy
+of the command out of the class.) This isn't particularly difficult,
+but you can instead simply subvert \csx{cleardoublepage} (which isn't
+often used elsewhere):
+\begin{quote}
+\begin{verbatim}
+\let\cleardoublepage\clearemptydoublepage
+\end{verbatim}
+\end{quote}
+Note: this command works because \csx{clearemptydoublepage} uses a copy
+of \csx{cleardoublepage}: instructions on macro programming
+% beware line break
+\Qref*[question]{patching techniques}{Q-patch} explain the problem and
+why this is a solution.
+
+The \Package{emptypage} package does this sort of thing for you; all
+you need do is load the package, and it does the rest.
+
+The \emph{\acro{KOMA}-Script} replacements for the
+\Class{book} and \Class{report} classes (\Class{scrbook} and
+\Class{scrreprt} offers class options \pkgoption{cleardoubleempty},
+\pkgoption{cleardoubleplain} and \pkgoption{cleardoublestandard}
+(using the running page style, as normal) that control the appearance
+of these empty pages. The classes also offer do-it-yourself commands
+\csx{cleardoubleempty} (etc.\@).
+
+The \Class{memoir} class (and the \Package{nextpage} package)
+provide commands \csx{cleartooddpage} and \csx{cleartoevenpage},
+which both take an optional argument (the first, with no argument,
+being an equivalent of \csx{cleardoublepage}). One can achieve
+`special' effects by putting commands in the optional argument: the
+\csx{clearemptydoublepage} we're after would be achieved by
+\csx{cleartooddpage[}\cmdinvoke{thispagestyle}{empty}\texttt{]}. The
+commands will also serve if you want the surreal effect of ``This page
+intentionally left blank'' in the centre of an otherwise empty page.
+\begin{ctanrefs}
+\item[emptypage.sty]\CTANref{emptypage}
+\item[fancyhdr.sty]\CTANref{fancyhdr}
+\item[memoir.cls]\CTANref{memoir}
+\item[nextpage.sty]\CTANref{nextpage}
+\item[scrbook.cls, scrrept.cls]Part of \CTANref{koma-script}
+\end{ctanrefs}
+
+\Question[Q-balance]{Balancing columns at the end of a document}
+
+The \Package{twocolumn} option of the standard classes causes
+\LaTeX{} to set the text of a document in two columns. However, the last
+page of the document typically ends up with columns of different
+lengths~--- such columns are said to be ``unbalanced''. Many (most?)
+people don't like unbalanced columns.
+
+The simplest solution to the problem is to use the \Package{multicol}
+package in place of the \Package{twocolumn} option, as
+\Package{multicol} balances the columns on the final page by default.
+However, the use of \Package{multicol} does come at a cost: its
+special output routine disallows the use of in-column floats, though
+it does still permit full-width (e.g., \environment{figure*}
+environment) floats.
+
+As a result, there is a constant push for a means of balancing columns
+at the end of a \Package{twocolumn} document. Of course, the job can
+be done manually: \csx{pagebreak} inserted at the appropriate place on
+the last page can often produce the right effect, but this seldom
+appeals, and if the last page is made up of automatically-generated
+text (for example, bibliography or index) inserting the command will
+be difficult.
+
+The \Package{flushend} package offers a solution to this problem. It's a
+somewhat dangerous piece of macro code, which patches one of the most
+intricate parts of the \LaTeX{} kernel without deploying any of the
+safeguards discussed in \Qref[question]{patching commands}{Q-patch}.
+The package only changes the behaviour at end document (its
+\csx{flushend} command is enabled by default), and one other command
+permits adjustment of the final balance; other packages in the bundle
+provide means for insertion of full width material in two-column
+documents.
+
+The \Package{balance} package also patches the output routine
+(somewhat more carefully than \Package{flushend}).
+
+The user should be aware that any of these packages are liable to
+become confused in the presence of floats: if problems arise, manual
+adjustment of the floats in the document is likely to be necessary.
+It is this difficulty (what's required in any instance can't really be
+expressed in current \LaTeX{}) that led the author of
+\Package{multicol} to suppress single-column-wide floats.
+\begin{ctanrefs}
+\item[balance.sty]Distributed as part of \CTANref{preprint}[balance]
+\item[flushend.sty]Distributed as part of \CTANref{sttools}[flushend]
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
+
+\end{ctanrefs}
+
+\Question[Q-runheadtoobig]{My section title is too wide for the page header}
+
+By default, \LaTeX{} sectioning commands make the chapter or section
+title available for use by page headers and the like. Page headers
+operate in a rather constrained area, and it's common for titles too
+be too big to fit: the \LaTeX{} sectioning commands therefore take an
+optional argument:
+\begin{quote}
+\begin{verbatim}
+\section[short title]{full title}
+\end{verbatim}
+\end{quote}
+If the \meta{short title} is present, it is used both for the table of
+contents and for the page heading. The usual answer to people who
+complain that their title is too big for the running head is to
+suggest that they the optional argument.
+
+However, using the same text for the table of contents as for the
+running head may also be unsatisfactory: if your chapter titles are
+seriously long (like those of a Victorian novel), a valid and rational
+scheme is to have a shortened table of contents entry, and a really
+terse entry in the running head.
+
+One of the problems is the tendency of page headings to be set in
+capitals (which take up more space); so why not set headings as written
+for ``ordinary'' reading? It's not possible to do so with unmodified
+\LaTeX{}, but the \Package{fancyhdr} package provides a command
+\csx{nouppercase} for use in its header (and footer) lines to suppress
+\LaTeX{}'s uppercasing tendencies. Classes in the \Class{KOMA-script}
+bundle don't uppercase in the first place.
+
+In fact, the sectioning commands use `mark' commands to pass
+information to the page headers. For example, \csx{chapter} uses
+\csx{chaptermark}, \csx{section} uses \csx{sectionmark}, and so on. With
+this knowledge, one can achieve a three-layer structure for chapters:
+\begin{quote}
+\begin{verbatim}
+\chapter[middling version]{verbose version}
+\chaptermark{terse version}
+\end{verbatim}
+\end{quote}
+which should supply the needs of every taste.
+
+Chapters, however, have it easy: hardly any book design puts a page
+header on a chapter start page. In the case of sections, one has
+typically to take account of the nature of the \csx{*mark} commands:
+the thing that goes in the heading is the first mark on the page (or,
+failing any mark, the last mark on any previous page). As a result
+the recipe for sections is more tiresome:
+\begin{quote}
+\begin{verbatim}
+\section[middling version]{verbose version%
+ \sectionmark{terse version}}
+\sectionmark{terse version}
+\end{verbatim}
+\end{quote}
+(the first \csx{sectionmark} deals with the header of the page the
+\csx{section} command falls on, and the second deal with subsequent
+pages; note that here, you need the optional argument to \csx{section},
+even if ``\emph{middling version}'' is in fact the same text as
+``\emph{long version''}.)
+
+A similar arrangement is necessary even for chapters if the class
+you're using is odd enough that it puts a page header on a chapter's
+opening page.
+
+Note that the \Package{titlesec} package manages the running heads in
+a completely different fashion; for example, you can use the optional
+argument of sectioning commands for page headers, only, by loading the
+package as:
+\begin{quote}
+\begin{verbatim}
+\usepackage[toctitles]{titlesec}
+\end{verbatim}
+\end{quote}
+The package documentation offers other useful techniques in this area.
+\LeadFrom{Tobi}{sx}{2012-02-01}
+
+The \Class{memoir} class avoids all the silliness by providing an
+extra optional argument for chapter and sectioning commands, for
+example:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\section[middling version][terse version]%
+ {verbose version}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\section[middling version][terse version]{verbose version}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+As a result, it is always possible for users of \Class{memoir} to
+tailor the header text to fit, with very little trouble.
+\begin{ctanrefs}
+\item[fancyhdr.sty]\CTANref{fancyhdr}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[titlesec.sty]\CTANref{titlesec}
+\end{ctanrefs}
+\LastEdit{2012-02-01}
+
+\nothtml{\begingroup\boldmath}
+\Question[Q-nofm]{Page numbering ``\meta{n} of \meta{m}''}
+\nothtml{\afterquestion}
+
+Finding the page number of the last page of a document, from within
+the document, is somewhat tricky. The \Package{lastpage} and
+\Package{zref-lastpage} packages define a label
+\texttt{LastPage} whose number is \emph{right} (after sufficiently many
+passes through \LaTeX{}, of course). The \Class{memoir} class also
+defines a ``last page'' label.
+
+The documentation of the \Package{fancyhdr} package spells out exactly
+how one might actually use this information to produce page numbering
+as suggested in the question.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}fancyhdr documentation]\CTANref{fancyhdr}
+\item[lastpage.sty]\CTANref{lastpage}
+\item[zref-lastpage]Distributed as part of \CTANref{oberdiek}[zref]
+\end{ctanrefs}
+\LastEdit{2012-10-16}
+
+\Question[Q-pagebychap]{Page numbering by chapter}
+
+When I was a young man, a common arrangement for loose bound technical
+manuals is to number pages by chapter. (It's quite a good scheme, in
+those situations: even if your corrections add a whole page to the
+chapter, the most you have to redistribute is that chapter.)
+
+The problem, at first sight, seems pretty much the same as that in
+another answer on
+% beware line break
+\Qref*{running numbers within a chapter}{Q-running-nos},
+and the basic technique is indeed pretty similar.
+
+However, tidying-up loose ends, making sure the page number gets reset
+to the correct value at the start of each chapter, and so on, is
+slightly more challenging. This is why the \Package{chappg} package
+was written: it does the obvious things, and more.
+
+Users have been known to ask for running page numbers within a
+section, but this really doesn't make sense: you need to run page
+numbers within document objects that always start on a fresh page.
+\begin{ctanrefs}
+\item[chappg.sty]\CTANref{chappg}
+\end{ctanrefs}
+
+\subsection{Page layout}
+
+\Question[Q-papersize]{The size of printed output}
+
+The final product of a \AllTeX{} run is something for a person to
+read. Often, nowadays, that product will be read ``on-screen'', but
+the printed page remains a principal output form.
+
+When we come to print our output, it is important that the output fits
+on the paper; in some cases, for the output to ``fit'' is good enough.
+However, there are circumstances where the actual size of the printed
+output, on the page, is crucial to the acceptance of the output.
+(This might happen when the output is a book to be published, or when
+it's a dissertation which must match the fancies of some bureaucrat
+even to be considered.)
+
+Sadly, we often find that the printed output doesn't conform to our
+expectations\dots{}
+
+The check-list for such problems has two entries:
+\begin{itemize}
+\item Your output is generated via Adobe \ProgName{Reader} (or
+ possibly ``\ProgName{Acrobat Reader}''~--- older versions of the
+ program had the qualified name). In this case, it may be that
+ \ProgName{Reader} is willfully changing the size of your output:
+ read \Qref*{\ProgName{Reader} antics}{Q-acroantics}.
+\item Something in your \TeX{} system is producing the wrong size (or
+ shape) of output: read \Qref*{paper geometry}{Q-papergeom}.
+\end{itemize}
+
+An alternative approach is to use the (excellent) \Package{testflow}
+suite, that provides a detailed outline of the potential problems
+together with a sample document and prototype outputs.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}testflow bundle]\CTANref{testflow}
+\end{ctanrefs}
+
+\Question[Q-acroantics]{Adobe \ProgName{Reader} messing with print size}
+\AliasQuestion{Q-outszwrng}
+
+Printing from Adobe \ProgName{Reader} shrinks the page ``to fit''
+(\emph{by default}). Unfortunately, its calculation doesn't consider
+the existing margins of the document, so that it shrinks what it
+believes is your whole page onto what it believes is its output page.
+The effect typically looks as if your margins have expanded.
+
+Solve this problem by adjusting the \ProgName{Reader}'s default in the
+print dialogue; unfortunately, this dialogue varies from one version
+to the next:
+\begin{itemize}
+\item \ProgName{Reader} version 7:\\
+ Page Scaling (default: ``Fit to printer margins'')~--- change to
+ ``None'', and\\
+ Scale (default 95\textpercent{} of Normal size)~--- change to
+ ``100\textpercent{}''.
+\item Adobe Reader 6:\\
+ in the print dialogue, on the ``copies \& pages'' pane, you'll find a
+ popup menu/drop-down list titled ``Page Scaling''~--- change to ``None''.
+\item Windows, Linux Acrobat (Reader) 5.0:\\
+ In the print dialog, make sure the ``Shrink oversized pages to fit''
+ checkbox is unchecked. It may also be useful to uncheck the
+ ``Expand small pages to fit paper size'' checkbox as well.
+\end{itemize}
+
+\Question[Q-papergeom]{Getting the right paper geometry from \AllTeX{}}
+
+If your output is the wrong size, and you've checked that it's not due
+to the \Qref*{ministrations of Adobe \ProgName{Reader}}{Q-acroantics},
+the problem is probably that your \AllTeX{} system is producing output
+that specifies the wrong paper size. Paper sizes can be a pain:
+they're a forgotten backwater~--- Knuth seems not to have considered
+paper size as something the \TeX{} engine needs to know about. As a
+result, there is no \acro{DVI} command to specify the paper on which
+the document should be printed, which has led a dichotomy where macros
+shape the text according to the needs of the author's chosen paper
+size, and device drivers' choice happens independently of the macros'
+ideas.
+
+In practice, one usually finds that macro packages (such as \plaintex{} and
+\LaTeX{}) assume American ``letter'' paper size, by default; and since
+most distributions nowadays originate in Europe, the drivers usually
+default to \acro{ISO} ``A4'' paper size.
+
+This is (of course) pretty unsatisfactory. Users may select a
+different paper size for their document (current \LaTeX{} offers a
+range of sizes as options in the standard classes), pretty easily.
+Nevertheless, the user also has to be sure that each time
+\ProgName{xdvi}, \ProgName{dvips} (or whatever) runs, it uses the
+paper size the document was designed for.
+
+The default paper size for \acro{DVI} drivers may be changed by a
+distribution management command (\ProgName{texconfig} for \texlive{},
+the \ProgName{Options} application for \miktex{}), but this still
+doesn't provide for people using the ``wrong'' sort of paper for some
+reason.
+
+A different issue arises for users of \PDFTeX{}~--- the
+\acro{PDF} format \emph{does} have the means of expressing paper size
+and \PDFTeX{} has system variables \csx{pdfpagewidth} and
+\csx{pdfpageheight}, that are written into the output \acro{PDF} file.
+Unfortunately, most of the core software predates \PDFTeX{}, so not even
+\PDFLaTeX{} sets the correct values into those variables, to match the
+paper size specified in a \csx{documentclass} option.
+
+The \acro{DVI} drivers \ProgName{dvips}, \ProgName{dvipdfm} and its
+extensions (\ProgName{dvipdfmx} and \ProgName{xdvipdfmx}) define
+\csx{special} commands for the document to specify its own paper size;
+so in those cases, as when \PDFTeX{} is being used, the
+paper size can be programmed by the document. Users who wish to, may
+of course consult the manuals of the various programs to write the
+necessary code.
+
+The \Package{geometry} and \Package{zwpagelayout} packages (whose main
+business includes defining
+typeset page areas), also takes notice the size of the paper that the
+document is going to be printed on, and can issue the commands
+necessary to ensure the correct size of paper is used. If
+\Package{geometry} is used when a document is being processed by
+\PDFLaTeX{}, it can set the necessary dimensions ``in the output''.
+If the document is being processed by \LaTeX{} on a \TeX{} or \eTeX{}
+engine, there are package options which instruct \Package{geometry}
+which \csx{special} commands to use. (Note that the options are
+ignored if you are using \PDFLaTeX{}.)
+
+So, one resolution of the problem, when you are using \latex{}, is to add
+\begin{quote}
+\begin{verbatim}
+\usepackage[processor-option,...]{geometry}
+\end{verbatim}
+\end{quote}
+Where \pkgoption{processor-option} tells the package what will produce
+your (\PS{} or \acro{PDF} output~--- \Package{geometry} knows about
+\pkgoption{dvips} and \pkgoption{dvipdfm} (\pkgoption{dvipdfm} also
+serves for the extension \ProgName{dvipdfmx} and
+\ProgName{xdvipdfmx}).
+
+If you're using \PDFLaTeX{} or \xetex{}, load with
+\begin{quote}
+\begin{verbatim}
+\usepackage[program-option,...]{geometry}
+\end{verbatim}
+\end{quote}
+where \pkgoption{program-option} is \pkgoption{pdftex},
+\pkgoption{xetex}.
+
+The alternative, \Package{zwpagelayout} requires a \pkgoption{driver}
+option:
+\begin{quote}
+\begin{verbatim}
+\usepackage[driver=value,...]{zwpagelayout}
+\end{verbatim}
+\end{quote}
+(permissible \meta{values} are \pkgoption{pdftex}, \pkgoption{xetex}
+and \pkgoption{dvips}; the default value is \pkgoption{unknown}).
+
+Needless to say, both the ``big'' classes (\Class{koma-script} and
+\Class{memoir}) provide their own ways to get the paper size
+``right''.
+
+The \Package{typearea} package is the \Class{Koma-script}
+distribution's way of providing page layout functionality. Load it
+with the \pkgoption{pagesize} option and it will ensure the correct
+paper is selected, for \acro{PDF} output from \PDFLaTeX{}, and for
+\PS{} output from \LaTeX{} via \ProgName{dvips}.
+
+\Class{Memoir} has the standard classes' paper-size selections
+(\pkgoption{a4paper}, \pkgoption{letterpaper} and so on), but also
+permits the user to choose an arbitrary paper size, by setting the
+length registers \csx{stockheight} and \csx{stockwidth}. The commands
+\csx{fixdvipslayout} (for \LaTeX{} processing), and \csx{fixpdflayout}
+(for \PDFLaTeX{} processing) then instruct the processor to produce
+output that specifies the necessary paper size.
+\begin{ctanrefs}
+\item[geometry.sty]\CTANref{geometry}
+\item[memoir.cls]\CTANref{memoir}
+\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea]
+\item[zwpagelayout.sty]\CTANref{zwpagelayout}
+\end{ctanrefs}
+\LastEdit{2011-12-12}
+
+\Question[Q-changemargin]{Changing the margins in \LaTeX{}}
+
+Changing the layout of a document's text on the page involves several
+subtleties not often realised by the beginner. There are interactions
+between fundamental \TeX{} constraints, constraints related to the
+design of \LaTeX{}, and good typesetting and design practice, that
+mean that any change must be very carefully considered, both to ensure
+that it ``works'' and to ensure that the result is pleasing to the
+eye.
+
+\LaTeX{}'s defaults sometimes seem excessively conservative,
+but there are sound reasons behind how Lamport designed the layouts
+themselves, whatever one may feel about his overall design. For
+example, the common request for ``one-inch margins all round on A4
+paper'' is fine for 10- or 12-pitch typewriters, but not for 10pt (or
+even 11pt or 12pt) type because readers find such wide, dense, lines
+difficult to read. There should ideally be no more than 75 characters
+per line (though the constraints change for two-column text).
+
+So Lamport's warning to beginners in his section on `Customizing the
+Style'~--- ``don't do it''~--- should not lightly be ignored.
+
+This set of \acro{FAQ}s recommends that you use a package to establish
+consistent settings of the parameters: the interrelationships are
+taken care of in the established packages, without you \emph{needing}
+to think about them, but remember~--- the packages only provide
+consistent, working, mechanisms: they don't analyse the quality of
+what you propose to do.
+
+The following answers deal with the ways one may choose to proceed:
+\begin{itemize}
+\item \Qref*{Choose which package to use}{Q-marginpkgs}.
+\item \Qref*{Find advice on setting up page layout by hand}{Q-marginmanual}.
+\end{itemize}
+There is a related question~--- how to change the layout
+temporarily~--- and there's an answer that covers that, too:
+\begin{itemize}
+\item \Qref*{Change the margins on the fly}{Q-chngmargonfly}.
+\end{itemize}
+
+\Question[Q-marginpkgs]{Packages to set up page designs}
+
+There are two trustworthy tools for adjusting the dimensions and position of the
+printed material on the page are \Package{geometry} and the
+\Package{zwpagelayout} packages; a very
+wide range of adjustments of the layout may be relatively
+straightforwardly programmed with either, and package documentation is good and
+comprehensive.
+
+As is usual, users of the \Class{memoir} class have built-in
+facilities for this task, and users of the \Class{KOMA-script} classes
+are recommended to use an alternative package, \Package{typearea}. In
+either case it is difficult to argue that users should go for
+\Package{geometry}: both alternatives are good.
+
+The documentation both of \Package{geometry} and of
+\Package{zwpagelayout} is rather overwhelming, and
+learning all of of either package's capabilities is likely to be more
+than you ever need.
+The \Package{vmargin} package is somewhat simpler to use: it has a
+canned set of paper sizes (a superset of that provided in \LaTeXe{}),
+provision for custom paper, margin adjustments and provision for
+two-sided printing.
+\begin{ctanrefs}
+\item[geometry.sty]\CTANref{geometry}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[layout.sty]Distributed as part of \CTANref{2etools}[layout]
+\item[memoir.cls]\CTANref{memoir}
+\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea]
+\item[vmargin.sty]\CTANref{vmargin}
+\item[zwpagelayout.sty]\CTANref{zwpagelayout}
+\end{ctanrefs}
+\LastEdit{2011-12-12}
+
+\Question[Q-marginmanual]{How to set up page layout ``by hand''}
+
+So you're eager to do it yourself, notwithstanding the cautions
+\begin{flatversion}
+ outlined above (\Qref{}{Q-changemargin}).
+\end{flatversion}
+\begin{hyperversion}
+ outlined in ``\Qref{changing margins}{Q-changemargin}''.
+\end{hyperversion}
+
+It's important that you first start by familiarising yourself
+with LaTeX's page layout parameters. For example, see section C.5.3 of the
+\LaTeX{} manual (pp.~181-182), or corresponding sections in many of the other
+good \LaTeX{} manuals (see \Qref[question]{\LaTeX{} books}{Q-latex-books}).
+
+\LaTeX{} controls the page layout with a number of parameters, which
+allow you to change the distance from the edges of a page to the left
+and top edges of your typeset text, the width and height of the text,
+and the placement of other text on the page. However, they are
+somewhat complex, and it is easy to get their interrelationships wrong
+when redefining the page layout. The layout package defines a
+\csx{layout} command which draws a diagram of your existing page
+layout, with the dimensions (but not their interrelationships) shown.
+
+Even changing the text height and width, \csx{textheight} and
+\csx{textwidth}, requires more care than you might expect: the height
+should be set to fit a whole number of text lines (in terms of
+multiples of \csx{baselinskip}), and the width should be constrained
+by the number of characters per line, as mentioned in % ! line break
+``\Qref*{changing margins}{Q-changemargin}''.
+
+Margins are controlled by two parameters: \csx{oddsidemargin} and
+\csx{evensidemargin}, whose names come from the convention that
+odd-numbered pages appear on the right-hand side (`recto') of a
+two-page spread and even-numbered pages on the left-hand side
+(`verso'). Both parameters actually refer to the left-hand margin of
+the relevant pages; in each case the right-hand margin is specified by
+implication, from the value of \csx{textwidth} and the width of the
+paper. (In a one-sided document, which is the default in many
+classes, including the standard \Class{article} and \Class{report}
+classes, \csx{oddsidemargin} stands for both.)
+
+The
+``origin'' (the zero position) on the page is one inch from the top of
+the paper and one inch from the left side; positive horizontal
+measurements extend right across the page, and positive vertical
+measurements extend down the page. Thus, the parameters
+\csx{evensidemargin}, \csx{oddsidemargin} and \csx{topmargin}, should
+be set to be 1~inch less than the true margin; for margins closer to
+the left and top edges of the page than 1~inch, the margin parameters
+must be set to negative values.
+
+\Question[Q-chngmargonfly]{Changing margins ``on the fly''}
+
+One of the surprises characteristic of \TeX{} use is that you cannot
+change the width or height of the text within the document, simply by
+modifying the text size parameters; \TeX{} can't change the text width
+on the fly, and \LaTeX{} only ever looks at text height when starting
+a new page.
+
+So the simple rule is that the parameters should only be
+changed in the preamble of the document, i.e., before the
+\cmdinvoke{begin}{document} statement (so before any typesetting has
+happened.
+
+To adjust text width within a document we define an environment:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{changemargin}[2]{%
+ \begin{list}{}{%
+ \setlength{\topsep}{0pt}%
+ \setlength{\leftmargin}{#1}%
+ \setlength{\rightmargin}{#2}%
+ \setlength{\listparindent}{\parindent}%
+ \setlength{\itemindent}{\parindent}%
+ \setlength{\parsep}{\parskip}%
+ }%
+ \item[]}{\end{list}}
+\end{verbatim}
+\end{quote}
+The environment takes two arguments, and will indent the left and
+right margins, respectively, by the parameters' values. Negative
+values will cause the margins to be narrowed, so
+\cmdinvoke{begin}{changemargin}{-1cm}{-1cm} narrows the left and right
+margins by 1 centimetre.
+
+Given that \TeX{} can't do this, how does it work?~--- well, the
+environment (which is a close relation of the \LaTeX{}
+\environment{quote} environment) \emph{doesn't} change the text width
+as far as \TeX{} is concerned: it merely moves text around inside the
+width that \TeX{} believes in.
+
+The \Package{changepage} package provides ready-built commands to do
+the above; it includes provision for changing the shifts applied to
+your text according to whether you're on an odd (\emph{recto}) or an
+even (\emph{verso}) page of a two-sided document.
+\Package{Changepage}'s structure matches that of the \Class{memoir}
+class.
+
+The (earlier) package \Package{chngpage} provides the same facilities,
+but it uses rather different syntax. \Package{Changepage}'s structure
+matches that of the \Class{memoir} class, and it should be used for
+any new work.
+
+Changing the vertical dimensions of a page is more clumsy still: the
+\LaTeX{} command \csx{enlargethispage} adjusts the size of the current
+page by the size of its argument. Common uses are
+\begin{quote}
+\begin{verbatim}
+\enlargethispage{\baselineskip}
+\end{verbatim}
+\end{quote}
+to make the page one line longer, or
+\begin{quote}
+\begin{verbatim}
+\enlargethispage{-\baselineskip}
+\end{verbatim}
+\end{quote}
+to make the page one line shorter. The process is (to an extent)
+simplified by the \Package{addlines} package: its \csx{addlines}
+command takes as argument the \emph{number} of lines to add to the
+page (rather than a length): the package documentation also provides a
+useful analysis of when the command may (or may not) be expected to
+work.
+\begin{ctanrefs}
+\item[addlines.sty]\CTANref{addlines}
+\item[changepage.sty]\CTANref{changepage}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-nopageno]{How to get rid of page numbers}
+\AliasQuestion{ps@empty}
+
+Very occasionally, one wants a document with no page numbers. For
+such occasions, the package \Package{nopageno} will make
+\cmdinvoke{pagestyle}{plain} have the same effect as
+\cmdinvoke{pagestyle}{empty}; in simple documents, this will suppress
+all page numbering (it will not work, of course, if the document uses
+some other pagestyle than \environment{plain}).
+
+To suppress page numbers from a sequence of pages, you may use
+\cmdinvoke{pagestyle}{empty} at the start of the sequence, and restore
+the original page style at the end. Unfortunately, you still have to
+deal with the page numbers on pages containing a \csx{maketitle},
+\csx{part} or \csx{chapter} command, since the standard classes; deal
+with those separately, as described below.
+
+To suppress page numbers on a single page, use
+\cmdinvoke{thispagestyle}{empty} somewhere within the text of the
+page. Note that, in the standard classes, \csx{maketitle} and
+\csx{chapter} use \csx{thispagestyle} internally, so your call
+must be \emph{after} those commands.
+
+Unfortunately, \csx{thispagestyle} doesn't work for \Class{book} or
+\Class{report} \csx{part} commands: they set the page style (as do
+\csx{chapter} commands), but then they advance to the next page so
+that you have no opportunity to change the style using
+\csx{thispagestyle}. The present author has proposed solving the
+problem with the following ``grubby little patch'', on
+\Newsgroup{comp.text.tex}:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\let\sv@endpart\@endpart
+\def\@endpart{\thispagestyle{empty}\sv@endpart}
+\makeatother
+\end{verbatim}
+\end{quote}
+Fortunately, that patch has now been incorporated in a small package
+\Package{nonumonpart} (a difficult name\dots)
+
+Both the \Class{KOMA-script} classes and \Class{memoir} have separate
+page styles for the styles of various ``special'' pages, so, in a
+\Class{KOMA} class document one might say:
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\titlepagestyle}{empty}
+\end{verbatim}
+\end{quote}
+while \Class{memoir} will do the job with
+\begin{quote}
+ \cmdinvoke{aliaspagestyle}{title}{empty}
+\end{quote}
+
+An alternative (in all classes) is to use the rather delightful
+\cmdinvoke{pagenumbering}{gobble}; this has the simple effect that any
+attempt to print a page number produces nothing, so there's no issue
+about preventing any part of \LaTeX{} from printing the number.
+However, the \csx{pagenumbering} command does have the side effect that
+it resets the page number (to 1), so it is unlikely to be helpful
+other than at the beginning of a document.
+
+The \Package{scrpage2} package separates out the representation of the
+page number (it typesets the number using the \csx{pagemark} command) from
+the construction of the page header and footer; so one can say
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\pagemark}{}
+\end{verbatim}
+\end{quote}
+which will also suppress the printing of the page number.
+
+Neither of these ``suppress the page number'' techniques touches the
+page style in use; in practice this means they don't make sense unless
+you are using \cmdinvoke{pagestyle}{plain}
+\begin{ctanrefs}
+\item[fancyhdr.sty]\CTANref{fancyhdr}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[nonumonpart.sty]\CTANref{nonumonpart}
+\item[nopageno.sty]\CTANref{nopageno}
+\item[scrpage2.sty]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+\LastEdit{2011-04-16}
+
+\Question[Q-crop]{How to create crop marks}
+
+If you're printing something that's eventually to be reproduced in
+significant quantities, and bound, it's conventional to print on paper
+larger than your target product, and to place ``crop marks'' outside
+the printed area. These crop marks are available to the production
+house, for lining up reproduction and trimming machines.
+
+You can save yourself the (considerable) trouble of programming these
+marks for yourself by using the package \Package{crop}, which has
+facilities to satisfy any conceivable production house. Users of the
+\Class{memoir} class don't need the package, since \Class{memoir} has
+its own facilities for programming crop marks.
+\begin{ctanrefs}
+\item[crop.sty]\CTANref{crop}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-watermark]{`Watermarks' on every page}
+
+It's often useful to place some text (such as `DRAFT') in the
+background of every page of a document. For \LaTeX{} users, the
+simplest way to do this uses the \Package{draftcopy} package. This
+can deal with
+many types of \acro{DVI} processors (in the same way that the graphics
+package does) and knows translations for the word `DRAFT' into a wide
+range of languages (though you can choose your own word, too).
+Unfortunately, however, the package relies on \PS{} specials, and will
+therefore fail if you are viewing your document with \ProgName{xdvi},
+and won't even compile if you're using \PDFLaTeX{}. (\PDFLaTeX{}
+users need one of the other solutions below.)
+
+The \Package{wallpaper} package builds on \Package{eso-pic} (see
+below). Apart from the single-image backdrops described above
+(``wallpapers'', of course, to this package), the package provides
+facilities for tiling images. All its commands come in pairs: one for
+``general'' use, and one applying to the current page only.
+
+The \Package{draftwatermark} package uses the same author's
+\Package{everypage} package to provide a simple interface for adding
+textual (`DRAFT'-like) watermarks.
+
+The \Package{xwatermark} package provides very flexible watermarking,
+with a ``modern'' (key-value) interface.
+
+More elaborate watermarks may be achieved using the \Package{eso-pic}
+package, or by using \Package{everypage} (see below).
+\Package{Eso-pic} attaches a \environment{picture} environment to
+every page as it is shipped out; the user can put things into that
+environment: the package provides commands for placing things at
+certain useful points (like ``text upper left'' or ``text centre'') in
+the picture, but the user is at liberty to do what he or she likes.
+
+\Package{Eso-pic} is, in turn, built upon the package
+\Package{atbegshi}. That package has the capability to produce
+watermarks \emph{on top of} the other material on the page; this
+doesn't sound very ``watermark-like'', but can be useful on pages
+where the watermark would otherwise be hidden by graphics or the
+like. The \Package{atbegshi} command that \Package{eso-pic} uses is
+\csx{AtBeginShipoutUpperLeft}; \csx{AtBeginShipoutUpperLeftForeground}
+is what's needed instead to place the material on top of the rest of
+the content of the page.
+
+\Package{Everypage} allows you to add ``something'' to every page, or
+to a particular page; you therefore need to construct your own
+apparatus for anything complicated.
+
+Finally, one can use the \ProgName{pdftk} untility; with it, the
+command:
+\begin{quote}
+\begin{verbatim}
+pdftk a.pdf background b.pdf output c.pdf
+\end{verbatim}
+\end{quote}
+will recreate \File{a.pdf} as \File{c.pdf}, having used the first page
+of \File{b.pdf} as background on every page. If you have a standard
+background (``DRAFT'' or ``SECRET'', or whatever) used in several
+files, \ProgName{pdftk} might well be attractive.
+
+\ProgName{Pdftk} is available as a command line tool; it is available
+in most linux distritbutions, but may be downloaded from its
+% ! line break
+\href{http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/}{home site}
+\begin{ctanrefs}
+\item[atbegshi.sty]Distributed as part of \CTANref{oberdiek}[atbegshi]
+\item[draftcopy.sty]\CTANref{draftcopy}
+\item[draftwatermark.sty]\CTANref{draftwatermark}
+\item[eso-pic.sty]\CTANref{eso-pic}
+\item[everypage.sty]\CTANref{everypage}
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
+\item[wallpaper.sty]\CTANref{wallpaper}
+\end{ctanrefs}
+
+\Question[Q-landscape]{Typesetting things in landscape orientation}
+
+It's often necessary to typeset part of a document in landscape
+orientation; to achieve this, one needs not only to change the page
+dimensions, but also to instruct the output device to print the
+strange page differently.
+
+There are two ``ordinary'' mechanisms for doing two slight variations
+of landscape typesetting:
+\begin{itemize}
+\item If you have a single floating object that is wider than it is
+ deep, and will only fit on the page in landscape orientation, use
+ the \Package{rotating} package; this defines
+ \environment{sidewaysfigure} and \environment{sidewaystable}
+ environments which create floats that occupy a whole page.
+
+ Note that \Package{rotating} has problems in a document that also
+ loads the \Package{float} package, which recommended in other
+ answers in these \acro{FAQ}s, for example that on
+ \Qref*{float placement}{Q-floats}. The \Package{rotfloat} package
+ loads \Package{rotating} for you, and smooths the interaction with
+ \Package{float}.
+\item If you have a long sequence of things that need to be typeset in
+ landscape (perhaps a code listing, a wide \environment{tabbing}
+ environment, or a huge table typeset using \Package{longtable} or
+ \Package{supertabular}), use the \Package{lscape} package (or
+ \Package{pdflscape} if you're generating \acro{PDF} output, whether
+ using \PDFLaTeX{} or \ProgName{dvips} and generating \acro{PDF} from
+ that). Both packages define an environment \environment{landscape}, which
+ clears the current page and restarts typesetting in landscape
+ orientation (and clears the page at the end of the environment
+ before returning to portrait orientation).
+\end{itemize}
+No currently available package makes direct provision for typesetting
+in both portrait and landscape orientation on the same page (it's not
+the sort of thing that \TeX{} is well set-up to do). If such
+behaviour was an absolute necessity, one might use the techniques
+described in
+% beware line-wrap
+\Qref[question]{"flowing text around figures"}{Q-textflow}, and would
+rotate the landscape portion using the rotation facilities of the
+\Package{graphics} package. (Returning from landscape to portrait
+orientation would be somewhat easier: the portrait part of the page
+would be a bottom float at the end of the landscape section, with its
+content rotated.)
+
+To set an entire document in landscape orientation, one might use
+\Package{lscape} around the whole document. A better option is the
+\pkgoption{landscape} option of the \Package{geometry} package; if you
+also give it \pkgoption{dvips} or \pkgoption{pdftex} option,
+\Package{geometry} also emits the rotation instructions to cause the
+output to be properly oriented. The \Class{memoir} class has the same
+facilities, in this respect, as does \Package{geometry}.
+
+A word of warning: most current \TeX{} previewers do not honour
+rotation requests in \acro{DVI} files.
+%% (the exception is
+%% (the exceptions are the
+%% \begin{htmlversion}
+%% (\Qref{commercial}{Q-commercial}) \YandY{} previewer
+%% \ProgName{dviwindo},
+%% \end{htmlversion}
+%% \htmlignore
+%% (commercial) \YandY{} previewer \ProgName{dviwindo}
+%% (\Qref{}{Q-commercial}),
+%% \endhtmlignore
+%% and
+%% the fp\TeX{} previewer Win\acro{DVI}). If your previewer is not
+%% capable of rotation,
+Your best bet is to convert your output to \PS{} or to \acro{PDF}, and
+to view these `final' forms with an appropriate viewer.
+\begin{ctanrefs}
+\item[geometry.sty]\CTANref{geometry}
+\item[graphics.sty]Distributed as part of \CTANref{graphics}
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
+\item[lscape.sty]Distributed as part of \CTANref{graphics}[lscape]
+\item[memoir.cls]\CTANref{memoir}
+\item[pdflscape.sty]Distributed with Heiko Oberdiek's packages
+ \CTANref{oberdiek}[pdflscape]
+\item[rotating.sty]\CTANref{rotating}
+\item[rotfloat.sty]\CTANref{rotfloat}
+\item[supertabular.sty]\CTANref{supertabular}
+\end{ctanrefs}
+
+\Question[Q-abspos]{Putting things at fixed positions on the page}
+
+\TeX{}'s model of the world is (broadly speaking) that the author
+writes text, and \TeX{} and its macros decide how it all fits on the
+page. This is not good news for the author who has, from whatever
+source, a requirement that certain things go in exactly the right
+place on the page.
+
+There \emph{are} places on the page, from which things may be hung,
+and two \LaTeX{} packages allow you position things relative to such
+points, thus providing a means of absolute positioning.
+
+The \Package{textpos} package aids the construction of pages from
+``blobs'', dotted around over the page (as in a poster); you give it
+the location, and it places your typeset box accordingly.
+
+The \Package{eso-pic} defines a ``shipout picture'' that covers the
+page. The user may add \environment{picture}-mode commands to this
+picture, which of course can include box placements as well as the
+other rather stilted commands of \environment{picture}-mode.
+(\Package{Eso-pic} requires the services of \Package{everyshi}, which
+must therefore also be available.)
+%
+% Fortunately, in the \LaTeX{} world at least, there \emph{is} a fixed
+% point on every page, to whit the page header. The package
+% \Package{textpos} latches bits of typesetting to locations you
+% specify, by fixing them to the page header, and thereby solves the
+% problem.
+\begin{ctanrefs}
+\item[eso-pic.sty]\CTANref{eso-pic}
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
+\item[textpos.sty]\CTANref{textpos}
+\end{ctanrefs}
+
+\Question[Q-nopagebrk]{Preventing page breaks between lines}
+
+One commonly requires that a block of typeset material be kept on the
+same page; it turns out to be surprisingly tricky to arrange this.
+
+\LaTeX{} provides a \environment{samepage} environment which claims it
+does this sort of thing for you. It proceeds by setting infinite
+penalties for all sorts of page-break situations; but in many
+situations where you want to prevent a page break,
+\environment{samepage} doesn't help. If you're trying to keep running
+text together, you need to end the paragraph inside the environment
+(see \Qref[question]{preserving paragraph parameters}{Q-paraparam}).
+Also, if the things you are trying to keep together insert their own
+pagebreak hints, \environment{samepage} has no power over them (though
+list items' attempts~--- they suggest page breaks between items~---
+are subverted by \environment{samepage}). Naturally, if
+\environment{samepage} \emph{does} work, it is capable of leaving
+stuff jutting out at the bottom of the page.
+
+Another convenient trick is to set all the relevant stuff in a
+\csx{parbox} (or a \environment{minipage} if it contains things like
+verbatim text that may not be used in the argument of a \csx{parbox}).
+The resulting box certainly \emph{won't} break between pages, but
+that's not to say that it will actually do what you want it to do:
+again, the box may be left jutting out at the bottom of the page.
+
+Why do neither of these obvious things work?~--- Because \TeX{} can't
+really distinguish between infinitely awful things.
+\environment{Samepage} will make any possible break point ``infinitely
+bad'' and boxes don't even offer the option of breaks, but if the
+alternative is the leave an infinitely bad few centimetres of blank
+paper at the bottom of the page, \TeX{} will take the line of least
+resistance and do nothing.
+
+This problem still arises even if you have \csx{raggedbottom} in
+effect: \TeX{} doesn't notice the value of \emph{that} until it starts
+actually shipping a page out. One approach is to set:
+\begin{quote}
+\begin{verbatim}
+\raggedbottom
+\addtolength{\topskip}{0pt plus 10pt}
+\end{verbatim}
+\end{quote}
+The \texttt{10pt} offers a hint to the output routine that the column is
+stretchable; this will cause \TeX{} to be more tolerant of the need to
+stretch while building the page. If you're doing this as a temporary
+measure, cancel the change to \csx{topskip} by:
+\begin{quote}
+\begin{verbatim}
+\addtolength{\topskip}{0pt plus-10pt}
+\end{verbatim}
+\end{quote}
+as well as resetting \csx{flushbottom}. (Note that the \texttt{10pt} never
+actually shows up, because it is overwhelmed when the page is shipped
+out by the stretchability introduced by \csx{raggedbottom}; however, it
+could well have an effect if \csx{flushbottom} was in effect.)
+
+An alternative (which derives from a suggestion by Knuth in the
+\TeX{}book) is the package \Package{needspace} or the \Class{memoir} class,
+which both define a command \csx{needspace} whose argument tells it
+what space is needed. If the space isn't available, the current page
+is cleared, and the matter that needs to be kept together will be
+inserted on the new page. For example, if 4~lines of text need to be
+kept together, the sequence
+\begin{quote}
+\begin{verbatim}
+\par
+\needspace{4\baselineskip}
+% the stuff that must stay together
+<text generating lines 1-4>
+% now stuff we don't mind about
+\end{verbatim}
+\end{quote}
+Yet another trick by Knuth is useful if you have a sequence of small
+blocks of text that need, individually, to be kept on their own page.
+Insert the command \csx{filbreak} before each small block, and the
+effect is achieved. The technique can be used in the case of
+sequences of \LaTeX{}-style sections, by incorporating \csx{filbreak}
+into the definition of a command (as in % beware line break
+\Qref[question]{patching commands}{Q-patch}). A simple and effective
+patch would be:
+\begin{quote}
+\begin{verbatim}
+\let\oldsubsubsection=\subsubsection
+\renewcommand{\subsubsection}{%
+ \filbreak
+ \oldsubsubsection
+}
+\end{verbatim}
+\end{quote}
+While the trick works for consecutive sequences of blocks, it's
+slightly tricky to get out of such sequences unless the sequence is
+interrupted by a forced page break (such as \csx{clearpage}, which may
+be introduced by a \csx{chapter} command, or the end of the document).
+If the sequence is not interrupted, the last block is likely to be
+forced onto a new page, regardless of whether it actually needs it.
+
+If one is willing to accept that not everything can be accomplished
+totally automatically, the way to go is to typeset the document and to
+check for things that have the potential to give trouble. In such a
+scenario (which has Knuth's authority behind it, if one is to believe
+the rather few words he says on the subject in the \TeX{}book) one can
+decide, case by case, how to deal with problems at the last
+proof-reading stage. At this stage, you can manually alter page
+breaking, using either \csx{pagebreak} or \csx{clearpage}, or you can
+place a \csx{nopagebreak} command to suppress unfortunate breaks.
+Otherwise, you can make small adjustments to the page geometry, using
+\csx{enlargethispage}. Supposing you have a line or two that stray:
+issue the command \cmdinvoke{enlargethispage}{2\csx{baselineskip}} and
+two lines are added to the page you're typesetting. Whether this
+looks impossibly awful or entirely acceptable depends on the document
+context, but the command remains a useful item in the armoury.
+
+Note that both \csx{pagebreak} and \csx{nopagebreak} take an optional
+number argument to adjust how the command is to be interpreted. Thus
+\cmdinvoke{pagebreak}[0], the command `suggests' that a page break
+might be worth doing, whereas \cmdinvoke{pagebreak}[4] `demands' a
+page break. Similarly \cmdinvoke{nopagebreak}[0] makes a suggestion,
+while \cmdinvoke{nopagebreak}[4] is a demand. In both commands, the
+default value of the optional argument is 4.
+\begin{ctanrefs}
+\item[memoir.cls]\CTANref{memoir}
+\item[needspace.sty]\CTANref{needspace}
+\end{ctanrefs}
+
+\Question[Q-parallel]{Parallel setting of text}
+
+It's commonly necessary to present text in two languages `together' on a
+page, or on a two-page spread. For this to be satisfactory, one usually
+needs some sort of alignment between the two texts.
+
+The \Package{parallel} package satisfies the need, permitting
+typesetting in two columns (not necessarily of the same width) on one
+page, or on the two opposing pages of a two-page spread. Use can be
+as simple as
+\begin{quote}
+\begin{verbatim}
+\usepackage{parallel}
+...
+\begin{Parallel}{<left-width>}{<right-width}
+ \ParallelLText{left-text}
+ \ParallelRText{right-text}
+ \ParallelPar
+ ...
+\end{Parallel}
+\end{verbatim}
+\end{quote}
+\Package{Parallel} can get terribly confused with colour changes, in
+\PDFTeX{}; the indefatigable Heiko Oberdiek has a patch for this
+issue~--- the \Package{pdfcolparallel} package, which maintains
+separate colour stacks for the columns.
+
+The \Package{parcolumns} package can (in principle) deal with any
+number of columns: the documentation shows its use with three
+columns. Usage is rather similar to that of \Package{parallel},
+though there is of course a ``number of columns to specify'':
+\begin{quote}
+\begin{verbatim}
+\usepackage{parcolumns}
+...
+\begin{parcolumns}[<options>]{3}
+ \colchunk{<Column 1 text>}
+ \colchunk{<Column 2 text>}
+ \colchunk{<Column 3 text>}
+ \colplacechunks
+ ...
+\end{parcolumns}
+\end{verbatim}
+\end{quote}
+The \meta{options} can specify the widths of the columns, whether to
+place rules between the columns, whether to set the columns sloppy,
+etc. Again, there are issues with colours, which are addressed by the
+\Package{pdfcolparcolumns} package.
+
+The \Package{ledpar} package is distributed with (and integrated with)
+the \Qref{\Package{ledmac} package}{Q-linenos}. It provides parallel
+setting carefully integrated with the needs of a scholarly text,
+permitting translation, or notes, or both, to be set in parallel with
+the `base' text of the document.
+\begin{ctanrefs}
+\item[ledpar.sty]Distributed with \CTANref{ledmac}
+\item[parallel.sty]\CTANref{parallel}
+\item[parcolumns.sty]Distributed as part of \CTANref{sauerj}[parcolumns]
+\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek}[pdfcolparallel]
+\item[pdfcolparcolumns.sty]pdfcolparcolumns]
+\end{ctanrefs}
+
+\Question[Q-epigraph]{Typesetting epigraphs}
+
+Epigraphs are those neat quotations that authors put at the start of
+chapters (or even at the end of chapters: Knuth puts things at the
+ends of chapters of the \TeX{}book).
+
+Typesetting them is a bit of a fiddle, but not impossible to do for
+yourself. Fortunately, there are two packages that do the job, to
+some extent; there are also facilities in the two ``big'' classes
+(\Class{memoir} and \Class{koma-script}.
+
+The \Package{epigraph} package defines an \csx{epigraph} command, for
+creating a single
+epigraph (as at the top of a chapter):
+\begin{quote}
+\begin{verbatim}
+\chapter{The Social Life of Rabbits}
+\epigraph{Oh! My ears and whiskers!}%
+ {Lewis Carroll}
+\end{verbatim}
+\end{quote}
+and an epigraphs environment, for entering more than one epigraph
+consecutively, in a sort of list introduced by \csx{qitem} commands:
+\begin{quote}
+\begin{verbatim}
+\begin{epigraphs}
+\qitem{What I tell you three times is true}%
+ {Lewis Carroll}
+\qitem{Oh listen do, I'm telling you!}%
+ {A.A. Milne}
+\end{epigraphs}
+\end{verbatim}
+\end{quote}
+The \csx{epigraphhead} command enables you to place your epigraph
+\emph{above} a chapter header:
+\begin{quote}
+\begin{verbatim}
+\setlength{\unitlength}{1pt}
+...
+\chapter{The Social Life of Rabbits}
+\epigraphhead[<distance>]{%
+ \epigraph{Oh! My ears and whiskers!}%
+ {Lewis Carroll}%
+}
+\end{verbatim}
+\end{quote}
+The \meta{distance} says how far above the chapter heading the
+epigraph is to go; it's expressed in terms of the \csx{unitlength}
+that's used in the \environment{picture} environment; the package's
+author recommends \texttt{70pt}.
+
+The package also offers various tricks for adjusting the layout of
+chapter header (necessary if you've found a hugely long quotation for
+an \csx{epigraphhead}), for patching the bibliography, for patching
+\csx{part} pages, and so on. (Some of these suggested patches lead you
+through writing your own package\dots{})
+
+The \Package{quotchap} package redefines chapter headings (in a
+moderately striking way), and provides an environment
+\environment{savequotes} in which you can provide one (or more)
+quotations to use as epigraphs. The facilities seem not as flexible
+as those of \Package{epigraph}, but it's probably easier to use.
+
+The \Class{memoir} class offers all the facilities of the
+\Package{epigraph} package. The \Class{Koma-script} classes have
+commands \csx{setchapterpreamble} and \csx{dictum} to provide these
+facilities.
+\begin{ctanrefs}
+\item[epigraph.sty]\CTANref{epigraph}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[quotchap.sty]\CTANref{quotchap}
+\end{ctanrefs}
+
+% \Question[Q-outszwrng]{\AllTeX{} \acro{PDF} output prints at wrong size}
+
+% Having got everything \emph{else} right, you should be aware that the
+% problem may have nothing to do with \AllTeX{} and everything to do
+% with the program you use for printing. A regular cause for such
+% problems lies with Acrobat Reader, which by default enables its option
+% to scale pages to fit on the printable area of the paper. Since a
+% printer can rarely print right to the edge, this means that pdf-files
+% will be shrunk by some (small) factor (even if the pdf-file is
+% formatted for A4, and your paper size is set to A4 as well).
+
+% Correcting this silliness is not very hard, but the exact details
+% depend on the version of Acrobat Reader (or "Adobe Reader" from
+% version 6.0 onwards) you have installed:
+% \begin{itemize}
+% \item Mac OS X, Adobe Reader 6:\\
+% in the print dialogue, on the ``copies \& pages'' pane, you'll find a
+% popup menu titled ``Page Scaling''. Make sure that the menu reads
+% ``None''.
+% \item Windows, Adobe Reader 6:\\
+% in the print dialogue, select ``None'' from the drop-down list
+% ``Page Scaling''.
+% \item Windows, Linux Acrobat (Reader) 5.0:\\
+% In the print dialog, make sure the ``Shrink oversized pages to fit''
+% checkbox is unchecked. It may also be useful to uncheck the
+% ``Expand small pages to fit paper size'' checkbox as well.
+%\end{itemize}
+
+\subsection{Spacing of characters and lines}
+
+\Question[Q-linespace]{Double-spaced documents in \LaTeX{}}
+
+A quick and easy way of getting inter-line space for copy-editing is
+to change \csx{baselinestretch}~--- \cmdinvoke{linespread}{1.2} (or,
+equivalently \cmdinvoke{renewcommand}{\csx{baselinestretch}}{1.2}) may
+be adequate. Note that \csx{baselinestretch} changes don't take
+effect until you select a new font, so make the change in the preamble
+before any font is selected. Don't try changing \csx{baselineskip}:
+its value is reset at any size-changing command so that results will
+be inconsistent.
+
+For preference (and certainly for a production document, such as a
+dissertation or an article submission), use a line-spacing package.
+The only one currently supported is \Package{setspace}.
+\Package{Setspace} switches off double-spacing at places where even
+the most die-hard official would doubt its utility (footnotes, figure
+captions, and so on); it's very difficult to do this consistently if
+you're manipulating \csx{baselinestretch} yourself.
+
+(Note: do \emph{not} be tempted by \Package{doublespace}~--- its
+performance under current \LaTeX{} is at best problematical.)
+
+Of course, the real solution (other than for private copy editing) is
+\emph{not} to use double-spacing at all. Universities, in particular,
+have no excuse for specifying double-spacing in submitted
+dissertations: \LaTeX{} is a typesetting system, not a
+typewriter-substitute, and can (properly used) make single-spaced text
+even more easily readable than double-spaced typewritten text. If you
+have any influence on your university's system (for example, through
+your dissertation supervisor), it may be worth attempting to get the
+rules changed (at least to permit a ``well-designed book'' format).
+
+Double-spaced submissions are also commonly required when submitting
+papers to conferences or journals. Fortunately (judging by the
+questions from users in this author's department), this demand is
+becoming less common.
+
+Documentation of \Package{setspace} appears as \TeX{} comments in the
+package file itself.
+\begin{ctanrefs}
+\item[setspace.sty]\CTANref{setspace}
+\end{ctanrefs}
+\LastEdit{2013-10-28}
+
+\Question[Q-letterspace]{Changing the space between letters}
+
+A common technique in advertising copy (and other text whose actual
+content need not actually be \emph{read}) is to alter the space
+between the letters (otherwise known as the tracking). As a general
+rule, this is a very bad idea: it detracts from legibility, which is
+contrary to the principles of typesetting (any respectable font you
+might be using should already have optimum tracking built into it).
+
+The great type designer, Eric Gill, is credited with saying ``he who
+would letterspace lower-case text, would steal sheep''. (The
+attribution is probably apocryphal: others are also credited with the
+remark. Stealing sheep was, in the 19th century, a capital offence in
+Britain.) As the remark suggests, though, letterspacing of upper-case
+text is less awful a crime; the technique used also to be used for
+emphasis of text set in Fraktur (or similar) fonts.
+
+Straightforward macros (usable, in principle, with any \TeX{} macro
+package) may be found in \Package{letterspacing} (which is the name of
+the \extension{tex} file).
+
+%%% the package has a serious bug in it, so suppress mention pro tem
+%The \Package{tracking} package has similar facilities.
+
+A more comprehensive solution is to be found in the \Package{soul}
+package (which is optimised for use with \LaTeX{}, but also works with
+\plaintex{}). Soul also permits hyphenation of letterspaced text;
+Gill's view of such an activity is not (even apocryphally) recorded.
+(Spacing-out forms part of the name of \Package{soul}; the other half
+is described in \Qref[question]{another question}{Q-underline}.)
+
+Possibly the `ultimate' in this field is the \Package{microtype},
+which uses the micro-typography capabilities of current \PDFTeX{} to
+provide a \csx{textls} command, which operates according to parameters
+declared in a \csx{SetTracking} command. \Package{Microtype}'s
+`tracking' facility expands the natural spacing of the font itself,
+rather than inserting space between characters. Ordinarily,
+letter-spacing will destroy ligatures; however, this is \emph{wrong}
+for some font styles (for example, \FontName{fraktur}), and the
+package provides a means of protecting the ligatures in a
+letter-spaced text.
+\begin{ctanrefs}
+\item[letterspacing.tex]\CTANref{letterspacing}
+\item[microtype.sty]\CTANref{microtype}
+\item[soul.sty]\CTANref{soul}
+%\item[tracking.sty]\CTANref{tracking}
+\end{ctanrefs}
+
+\Question[Q-ragright]{Setting text ragged right}
+
+The trick with typesetting ragged right is to be sure you've told the
+\TeX{} engine ``make this paragraph ragged, but never \emph{too}
+ragged''. The \LaTeX{} \csx{raggedright} command (and the
+corresponding \environment{flushleft} environment) has a tendency to
+miss the ``never'' part, and will often create ridiculously short
+lines, for some minor benefit later in the paragraph. The
+\plaintex{} version of the command doesn't suffer this failing, but
+is rather conservative: it is loath to create too large a gap at the
+end of the line, but in some circumstances~--- such as where
+\Qref*{hyphenation is suppressed}{Q-hyphoff}~--- painfully large gaps
+may sometimes be required.
+
+Martin Schr\"oder's \Package{ragged2e} package offers the best of both
+worlds: it provides raggedness which is built on the \plaintex{}
+model, but which is easily configurable. It defines easily-remembered
+command (e.g., \csx{RaggedRight}) and environment (e.g.,
+\environment{FlushLeft}) names that are simply capitalised
+transformations of the \LaTeX{} kernel originals. The documentation
+discusses the issues and explains the significance of the various
+parameters of \Package{ragged2e}'s operation.
+\begin{ctanrefs}
+\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e]
+\end{ctanrefs}
+
+\Question[Q-flushboth]{Cancelling \csx{ragged} commands}
+
+\LaTeX{} provides commands \csx{raggedright} and \csx{raggedleft}, but
+none to cancel their effect. The \csx{centering} command is
+implemented in the same way as the \csx{ragged*} commands, and suffers
+in the same way.
+
+The following code (to be inserted in a package of your own, or as
+\nothtml{internal \LaTeX{} code~---}% beware line break
+\Qref{internal \LaTeX{} code}{Q-atsigns}) defines a command that
+restores flush justification at both margins:
+\begin{verbatim}
+\def\flushboth{%
+ \let\\\@normalcr
+ \@rightskip\z@skip \rightskip\@rightskip
+ \leftskip\z@skip
+ \parindent 1.5em\relax}
+\end{verbatim}
+There's a problem with the setting of \csx{parindent} in the code: it's
+necessary because both the \csx{ragged} commands set \csx{parindent} to
+zero, but the setting isn't a constant of nature: documents using a
+standard \LaTeX{} class with \pkgoption{twocolumn} option will have
+\texttt{1.0em} by default, and there's no knowing what you (or some
+other class) will have done.
+
+Any but a really old copy of Martin Schr\"oder's \Package{ragged2e}
+package has a \csx{justifying} command to match its % ! line break
+\Qref*{versions of the \LaTeX{} `ragged' commands}{Q-ragright}. The
+package also provides a \environment{justify} environment, which
+permits areas of justified text in a larger area which is ragged.
+\begin{ctanrefs}
+\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e]
+\end{ctanrefs}
+% this package hasn't materialised, for some reason i don't now
+% remember...
+%% Donald Arseneau's \Package{flushboth} package provides this code, and
+%% preserves a sensible value for \csx{parindent} (at begin document).
+%% This still doesn't protect it against any change you might make to
+%% \csx{parindent} within the body of your document.
+%% \begin{ctanrefs}
+%% \item[flushboth.sty]\CTANref{flushboth}
+%% \end{ctanrefs}
+
+\subsection{Typesetting specialities}
+
+\Question[Q-verbfile]{Including a file verbatim in \LaTeX{}}
+
+A good way is to use Rainer Sch\"opf's \Package{verbatim} package,
+which provides a command \csx{verbatiminput} that takes a file name as
+argument:
+\begin{quote}
+\begin{verbatim}
+\usepackage{verbatim}
+...
+\verbatiminput{verb.txt}
+\end{verbatim}
+\end{quote}
+Another way is to use the \environment{alltt} environment, which
+requires the \Package{alltt} package. The environment interprets its
+contents `mostly' verbatim, but executes any \AllTeX{} commands it
+finds:
+\begin{quote}
+\begin{verbatim}
+\usepackage{alltt}
+...
+\begin{alltt}
+\input{verb.txt}
+\end{alltt}
+\end{verbatim}
+\end{quote}
+of course, this is little use for inputting \AllTeX{} source
+code\dots{}
+
+The \Package{moreverb} package extends the \Package{verbatim} package,
+providing a \environment{listing} environment and a \csx{listinginput}
+command, which line-number the text of the file. The package also has
+a \csx{verbatimtabinput} command, that honours \acro{TAB} characters in
+the input (the package's \environment{listing} environment and the
+\csx{listinginput} command also both honour \acro{TAB}).
+
+The \Package{sverb} package provides verbatim input (without recourse
+to the facilities of the \Package{verbatim} package):
+\begin{quote}
+\begin{verbatim}
+\usepackage{sverb}
+...
+\verbinput{verb.txt}
+\end{verbatim}
+\end{quote}
+
+The \Package{fancyvrb} package offers configurable implementations of
+everything \Package{verbatim}, \Package{sverb} and \Package{moreverb}
+have, and more besides. It is nowadays the package of choice for the
+discerning typesetter of verbatim text, but its wealth of facilities
+makes it a complex beast and study of the documentation is strongly
+advised.
+
+The \Class{memoir} class includes the relevant functionality of the
+\Package{verbatim} and \Package{moreverb} packages.
+\begin{ctanrefs}
+\item[alltt.sty]Part of the \LaTeX{} distribution.
+\item[fancyvrb.sty]\CTANref{fancyvrb}
+\item[memoir.cls]\CTANref{memoir}
+\item[moreverb.sty]\CTANref{moreverb}
+\item[sverb.sty]Distributed as part of \CTANref{mdwtools}[sverb]
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim]
+\end{ctanrefs}
+
+\Question[Q-linenos]{Including line numbers in typeset output}
+
+For general numbering of lines, there are two packages for use with
+\LaTeX{}, \Package{lineno} (which permits labels attached to
+individual lines of typeset output) and \Package{numline}.
+(\Package{Numline} is considered obsolete, but remains available from
+the archive.)
+
+Both of these packages play fast and loose with the \LaTeX{} output
+routine, which can cause problems: the user should beware\dots{}
+
+If the requirement is for numbering verbatim text, \Package{moreverb},
+or \Package{fancyvrb} (see % ! line break
+\Qref[question]{including files verbatim}{Q-verbfile}) may be used.
+Class \Class{memoir} also provides the necessary facilities.
+
+One common use of line numbers is in critical editions of texts, and
+for this the \Package{edmac} package offers comprehensive support;
+\Package{ledmac} is a \LaTeX{} port of \Package{edmac}.
+
+The \Package{vruler} package sidesteps many of the problems associated
+with line-numbering, by offering (as its name suggests) a rule that
+numbers positions on the page. The effect is good, applied to
+even-looking text, but is poor in texts that involve breaks such as
+interpolated mathematics or figures. Documentation of the package, in
+the package itself, is pretty tough going, though there is an example
+(also inside the package file).
+\begin{ctanrefs}
+\item[edmac]\CTANref{edmac}
+\item[fancyvrb.sty]\CTANref{fancyvrb}
+\item[ledmac.sty]\CTANref{ledmac}
+\item[lineno.sty]\CTANref{lineno}
+\item[memoir.cls]\CTANref{memoir}
+\item[moreverb.sty]\CTANref{moreverb}
+\item[numline.sty]\CTANref{numline}
+\item[vruler.sty]\CTANref{vruler}
+\end{ctanrefs}
+
+\Question[Q-codelist]{Code listings in \LaTeX{}}
+
+`Pretty' code listings are sometimes considered worthwhile by the
+``ordinary'' programmer, but they have a serious place in
+the typesetting of dissertations by computer science and other
+students who are expected to write programs. Simple verbatim listings
+of programs are commonly useful, as well.
+
+\begin{hyperversion}
+ \Qref{Verbatim listings}{Q-verbfile} are dealt with elsewhere,
+\end{hyperversion}
+\begin{flatversion}
+ Verbatim listings are dealt with elsewhere (\Qref{}{Q-verbfile}),
+\end{flatversion}
+as is the problem of % ! line break
+\Qref*{typesetting algorithm specifications}{Q-algorithms}.
+
+The \Package{listings} package is widely regarded as the best bet for
+formatted output (it is capable of parsing program source, within the
+package itself), but there are several well-established packages that
+rely on a pre-compiler of some sort. You may use \Package{listings}
+to typeset snippets that you include within your source:
+\begin{quote}
+\begin{verbatim}
+\usepackage{listings}
+\lstset{language=C}
+...
+\begin{document}
+\begin{lstlisting}
+#include <stdio.h>
+
+int main(int argc, char ** argv)
+{
+ printf("Hello world!\n");
+ return 0;
+}
+\end{lstlisting}
+\end{document}
+\end{verbatim}
+\end{quote}
+or you can have it typeset whole files:
+\begin{quote}
+\begin{verbatim}
+\usepackage{listings}
+\lstset{language=C}
+...
+\begin{document}
+\lstinputlisting{main.c}
+\end{document}
+\end{verbatim}
+\end{quote}
+These very simple examples may be decorated in a huge variety of ways,
+and of course there are other languages in the package's vocabulary
+than just \ProgName{C}\dots{}
+
+For a long time, advice on \AllTeX{} lists seemed to regard
+\Package{listings} as the be-all and end-all on this topic. In the
+last few years, viable alternatives have appeared
+
+\ProgName{Highlight} is attractive if you need more than one output
+format for your program: as well as \AllTeX{} output,
+\ProgName{highlight} will produce (\acro{X})\acro{HTML}, \acro{RTF}
+and \acro{XSL}-\acro{FO} representations of your program listing. The
+manual leads you through the details of defining a parameter file for
+a ``new'' language, as well as the presentation details of a language.
+
+The \Package{minted} package is another alternative that offers
+the means of creating new language definitions. It
+requires that code be processed using an external (\ProgName{python})
+script, \href{http://pygments.org/}{\ProgName{Pygments}}.
+\ProgName{Pygments}, in turn, needs a ``lexer'' that knows the
+language you want to process; lots of these are available, for the
+more commonly-used languages, and there is advice on ``rolling your
+own'' on the % ! line break.
+<a href='http://pygments.org/docs/lexerdevelopment/'>\ProgName{Pygments} site</a>
+
+Usage of \Package{minted} can be as simple as
+\begin{quote}
+ \cmdinvoke{begin}{minted}{\meta{language}}\\
+ \dots{}\\
+ \cmdinvoke{end}{minted}
+\end{quote}
+which processes the program code dynamically, at typesetting time~---
+though such usage is likely to require that % ! line break
+\Qref*{separate processing be enabled}{Q-spawnprog}.
+
+On a rather different path, the package \Package{showexpl} supports
+typesetting \alltex{} code and its typeset output, in parallel
+`panes'. (Thiscould provide support for \alltex{} instruction texts,
+or for papers in \tex{} user group publications. The package uses
+\Package{listings} for its \alltex{} pane, and typesets the result
+into a simple box, for the other pane.
+
+Longer-established, and variously less ``powerful'' systems include:
+\begin{itemize}
+\item The \ProgName{lgrind} system is a well-established
+ pre-compiler, with all the facilities one might need and a wide
+ repertoire of languages; it is derived from the even
+ longer-established \ProgName{tgrind}, whose output is based on
+ \plaintex{}.
+\item The \ProgName{tiny_c2l} system is slightly more recent: users
+ are again encouraged to generate their own driver files for
+ languages it doesn't already deal with, but its ``tiny'' name
+ correctly hints that it's not a particularly elaborate system.
+\item The \ProgName{C++2LaTeX} system comes with strong
+ recommendations for use with \acro{C} and \acro{C}++.
+\item An extremely simple system is \ProgName{c2latex}, for which you
+ write \LaTeX{} source in your \acro{C} program comments. The
+ program then converts your program into a \LaTeX{} document for
+ processing. The program (implicitly) claims to be
+ ``self-documenting''.
+\end{itemize}
+\begin{ctanrefs}
+\item[c2latex]\CTANref{c2latex}
+\item[C++2LaTeX]\CTANref{c++2latex}
+\item[highlight]\CTANref{highlight}
+\item[lgrind]\CTANref{lgrind}
+\item[listings.sty]\CTANref{listings}
+\item[minted.sty]\CTANref{minted}
+\item[showexpl.sty]\CTANref{showexpl}
+\item[tgrind]\CTANref{tgrind}
+\item[tiny\_c2l]\CTANref{tiny_c2l}
+\end{ctanrefs}
+\LastEdit{2013-03-28}
+
+\Question[Q-algorithms]{Typesetting pseudocode in \LaTeX{}}
+
+There is no consensus on the `right' way to typeset pseudocode.
+Consequently, there are a variety of \LaTeX{} packages to choose from
+for producing \ae{}sthetically pleasing pseudocode listings.
+
+Pseudocode differs from actual program listings in that it lacks
+strict syntax and semantics. Also, because pseudocode is supposed to
+be a clear expression of an algorithm it may need to incorporate
+mathematical notation, figures, tables, and other \LaTeX{} features
+that do not appear in conventional programming languages.
+\begin{wideversion} % hyper?
+ \Qref{Typesetting program listings}{Q-codelist} is described
+ elsewhere.
+\end{wideversion}
+\begin{narrowversion} % non-hyper
+ Typesetting program listings is described elsewhere
+ (\Qref{}{Q-codelist}).
+\end{narrowversion}
+
+You can certainly create your own environment for typesetting
+pseudocode using, for example, the \environment{tabbing} or
+\environment{list} environments~--- it's not difficult, but it may
+prove boring. So it's worth trying the following packages, all
+designed specifically for typesetting pseudocode.
+
+The \Package{algorithms} bundle (which contains packages
+\Package{algorithm} and \Package{algorithmic}, both of which are
+needed for ordinary use) has a simple interface and produces fairly
+nice output. It provides primitives for statements, which can contain
+arbitrary \LaTeX{} commands, comments, and a set of iterative and
+conditional constructs. These primitives can easily be redefined to
+produce different text in the output. However, there is no support
+for adding new primitives. Typesetting the pseudocode itself is
+performed in \Package{algorithmic}; the \Package{algorithms} package
+uses the facilities of the \Package{float} package to number
+algorithms sequentially, enable algorithms to float like figures or
+tables, and support including a List of Algorithms in a document's
+front matter.
+
+Packages in the \Package{algorithmicx} bundle are similar both in
+concept and output form to \Package{algorithmic} but additionally
+provide support for adding new keywords and altering the formatting.
+It provides the \Package{algpseudocode} package which is (almost) a
+drop-in replacement for \Package{algorithmic}. Another package in the
+bundle, \Package{algpascal}, uses Pascal-like keywords, indents
+differently from \Package{algpseudocode}, and puts command arguments
+in maths mode instead of text mode. There is no floating environment
+but \Package{algorithmicx}, like \Package{algorithmic}, is compatible
+with the \Package{algorithm} package. (There have been reports of
+difficulty defining new commands to fit with the package;
+unfortunately, the author is not available to comment.)
+
+The \Package{alg} package, like \Package{algorithms}, offers a
+floating algorithm environment with all of the ensuing niceties.
+\Package{alg}, however, can caption its floats in a variety of
+(natural) languages. In addition, \Package{alg} unlike
+\Package{algorithms}, makes it easy to add new constructs.
+
+The \Package{newalg} package has a somewhat similar interface to
+\Package{algorithms}, but its output is designed to mimic the rather
+pleasant typesetting used in the book ``\emph{Introduction to Algorithms}''
+by Corman, Leiserson, Rivest and Stein. Unfortunately,
+\Package{newalg} does not support a floating environment or any
+customisation of the output.
+
+``\emph{Bona fide}'' use of the style of ``Introduction to
+Algorithms'' may be achieved with Cormen's own \Package{clrscode}:
+this is the package as used in the second edition of the book.
+
+Similarly, the style of % ! line break
+``\emph{Combinatorial Algorithms: Generation, Enumeration and Search}''
+is supported by the \Package{pseudocode} package, written by the
+authors of the book. It has the common `Pascal-like' style, and has
+some interesting constructs for what one thinks of as Pascal blocks.
+
+The \Package{algorithm2e} is of very long standing, and is widely used
+and recommended. It loads the \Package{float} package to provide the
+option of floating algorithm descriptions, but you can always use the
+``\texttt{H}'' option of \Package{float} to have the algorithm appear
+``where you write it''.
+
+The usage of the \Package{program} package is a little different from
+that of the other packages. It typesets programs in maths mode
+instead of text mode; and linebreaks are significant.
+\Package{program} lacks a floating environment but does number
+algorithms like \Package{alg} and \Package{algorithms}. Customisation
+and extension are not supported. Documentation of the
+\Package{program} package (such as it is) appears in a file
+\File{program.msg} in the distribution.
+
+None of the above are perfect. The factors that should influence your
+choice of package include the output style you prefer, how much you
+need to extend or modify the set of keywords, and whether you require
+algorithms to float like figures and tables.
+%%
+%% Documentation availability:
+%% \begin{description}
+%% \item[\Package{algorithms} bundle] is provided in \File{algorithms.ps}
+%% (also available as LaTeX{} source). The documentation speaks as if
+%% the two packages of the bundle were indeed one, called
+%% \Package{algorithms}.
+%% \item[\Package{program} package] (such as it is) appears in a file
+%% \File{program.msg}.
+%% \item[\Package{clrscode} package] is to be found in
+%% \File{clrscode.pdf} in the distribution.
+%% \item[\Package{algorithm2e} package] is to be found in
+%% \File{algorithm2e.tex} in the distribution (it needs the package
+%% itself when you process it).
+%% \end{description}
+\begin{ctanrefs}
+\item[algorithm2e.sty]\CTANref{algorithm2e}
+\item[algorithmicx\nothtml{\rmfamily} bundle]\CTANref{algorithmicx}
+\item[algorithms\nothtml{\rmfamily} bundle]\CTANref{algorithms}
+\item[alg.sty]\CTANref{alg}
+\item[clrscode.sty]\CTANref{clrscode}
+\item[float.sty]\CTANref{float}
+\item[newalg.sty]\CTANref{newalg}
+\item[program.sty]\CTANref{program}
+\item[pseudocode.sty]\CTANref{pseudocode}
+\end{ctanrefs}
+\LastEdit{2011-10-12}
+
+\Question[Q-makeindex]{Generating an index in \AllTeX{}}
+
+Making an index is not trivial; what to index, and how to index it, is
+difficult to decide, and uniform implementation is difficult to
+achieve. You will need to mark all items to be indexed in your text
+(typically with \csx{index} commands).
+
+It is not practical to sort a large index within \TeX{}, so a
+post-processing program is used to sort the output of one \TeX{} run,
+to be included into the document at the next run.
+
+The following programs are available:
+\begin{description}
+\item[makeindex] Comes with most distributions~--- a good workhorse,
+ but is not well-arranged to deal with other sort orders than the
+ canonical \acro{ASCII} ordering.
+
+ The \Package{makeindex} documentation is a good source of
+ information on how to create your own index. \Package{Makeindex} can
+ be used with some \TeX{}
+ macro packages other than \LaTeX{}, such as \nothtml{\Eplain\ (}%
+ \Qref{Eplain}{Q-eplain}\nothtml{)}, and \TeX{} (whose macros can
+ be used independently with \plaintex{}).
+\item[idxtex] for \LaTeX{} under \acro{VMS}; \ProgName{idxtex} comes
+ with a glossary-maker \ProgName{glotex}.
+\item[texindex(1)] A witty little shell-script using \ProgName{sed}
+ and \ProgName{awk}; designed for \LaTeX{} under Unix.
+\item[texindex(2)] The \Qref*{Texinfo}{Q-texinfo} system also offers a program
+ \ProgName{texindex}, whose source is to be found in the
+ \ProgName{texinfo} distribution. The \Package{ltxindex} package
+ provides macros that enable \LaTeX{} users to use this
+ \ProgName{texindex}.
+\item[xindy] arose from frustration at the difficulty of making a
+ multi-language version of \ProgName{makeindex}. It is designed to
+ be a successor to \ProgName{makeindex}, by a team that included the
+ then-current maintainer of \ProgName{makeindex}. It successfully
+ addresses many of \ProgName{makeindex}'s shortcomings, including
+ difficulties with collation order in different languages, and it is
+ highly flexible.
+
+ \ProgName{Xindy} itself will work with Unicode (UTF-8) encoded
+ \latex{} input. A separate application (\ProgName{texindy}) deals
+ with `standard' \latex{} source, processes it and passes
+ `sanitised' text to \ProgName{Xindy}.
+\end{description}
+\begin{ctanrefs}
+\item[idxtex]\CTANref{glo+idxtex}
+\item[ltxindex.sty]\CTANref{ltxindex}
+\item[makeindex]\CTANref{makeindex}
+\item[makeindex (Macintosh)]\CTANref{macmakeindex}
+\item[texindex \nothtml{\upshape\rmfamily}(the script)]\CTANref{texindex}
+\item[texindex \nothtml{\upshape\rmfamily}(the program)]Distributed
+ with \CTANref{texinfo}
+\item[texsis (system)]\CTANref{texsis}
+\item[texsis (makeindex support)]\CTANref{texsis-index}
+\item[xindy]\CTANref{xindy}
+\end{ctanrefs}
+
+\Question[Q-setURL]{Typesetting \acro{URL}s}
+
+\acro{URL}s tend to be very long, and contain characters that would
+naturally prevent them being hyphenated even if they weren't typically
+set in \csx{ttfamily}, verbatim. Therefore, without special treatment,
+they often produce wildly overfull \csx{hbox}es, and their typeset
+representation is awful.
+
+There are three packages that help solve this problem:
+\begin{itemize}
+\item The \Package{path} package, which defines a \csx{path} command.
+ The command defines each potential break character as a
+ \csx{discretionary}, and offers the user the opportunity of
+ specifying a personal list of potential break characters. Its chief
+ disadvantage is fragility in \LaTeX{} moving arguments. The
+% beware line breaks
+ \Qref*{\Eplain{} macros}{Q-eplain}~--- define a similar \csx{path} command.
+
+ \Package{Path}, though it works in simple situations, makes no
+ attempt to work with \LaTeX{} (it is irremediably fragile). Despite
+ its long and honourable history, it is no longer recommended for
+ \LaTeX{} use.
+\item The \Package{url} package, which defines an \csx{url} command
+ (among others, including its own \csx{path} command). The command
+ gives each potential break character a maths-mode `personality', and
+ then sets the \acro{URL} itself (in the user's choice of font) in
+ maths mode. It can produce (\LaTeX{}-style) `robust' commands
+ % beware line break within paren
+ (\htmlonly{see }\Qref{use of \csx{protect}}{Q-protect}) for use
+ within moving arguments.
+
+ The package ordinarily ignores spaces in the \acro{URL}, but
+ unfortunately \acro{URL}s that contain spaces do exist; to typeset
+ them, call the package with the \pkgoption{obeyspaces} option. Two
+ other useful options allow line breaks in the \acro{URL} in places
+ where they are ordinarily suppressed to avoid confusion:
+ \pkgoption{spaces} to allow breaks at spaces (note, this requires
+ \pkgoption{obeyspaces} as well, and \pkgoption{hyphens} to allow
+ breaks after hyphens. (Note that the package \emph{never} does
+ ``ordinary'' hyphenation of names inside an \acro{URL}.)
+
+ It is possible to use the \Package{url} package in \plaintex{},
+ with the assistance of the \Package{miniltx} package (which was
+ originally developed for using the \LaTeX{} graphics package in
+ \plaintex{}). A small patch is also necessary: the required
+ sequence is therefore:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\input miniltx
+\expandafter\def\expandafter\+%
+ \expandafter{\+}
+\input url.sty
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\input miniltx
+\expandafter\def\expandafter\+\expandafter{\+}
+\input url.sty
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+\item The \Package{hyperref} package, which uses the typesetting code
+ of \Package{url}, in a context where the typeset text forms the
+ anchor of a link.
+\end{itemize}
+
+The author of this answer prefers the (rather newer) \Package{url}
+package (directly or indirectly); both \Package{path} and
+\Package{url} work well with \plaintex{} (though of course, the fancy
+\LaTeX{} facilities of \Package{url} don't have much place there).
+(\Package{hyperref} isn't available in a version for use with \plaintex{}.)
+
+Note that neither \csx{path} (from package \Package{path}) nor \csx{url} (from
+package \Package{url}) is robust (in the \LaTeX{} sense). If you need
+a \acro{URL} to go in a moving argument, you need the command
+\csx{urldef} from the \Package{url} package. So one might write:
+\begin{quote}
+\begin{verbatim}
+\urldef\faqhome\url{http://www.tex.ac.uk/faq}
+\end{verbatim}
+\end{quote}
+after which, \csx{faqhome} is robust.
+
+Documentation of both package \Package{path} and package \Package{url}
+is in the package files.
+\begin{ctanrefs}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[miniltx.tex]Distributed as part of \CTANref{graphics-plain}[miniltx]
+\item[path.sty]\CTANref{path}
+\item[url.sty]\CTANref{url}
+\end{ctanrefs}
+
+\Question[Q-music]{Typesetting music in \tex{}}
+
+The current best bet for music typesetting is to use
+\Package{musixtex}. \Package{Musixtex} is a three-pass system that
+has a \tex{}-based pass, a processing pass and then a further \tex{}
+pass. The middle pass, a program called \ProgName{musixflx},
+optimises the spacing and sorts out slurs and ties.
+\Package{Musixtex} is demanding of \tex{} resources, and any
+significant score requires that typesetting is done using \etex{},
+whose expanded variable- and box-register ranges allow for more of the
+``parallel'' activities that abound in a music score.
+Of course, \Package{musixtex} also requires music fonts; those are
+available in a separate package on the archive.
+
+\Package{Musixtex} requires pretty arcane input; most people using it
+actually prepare (less obscure) input for \ProgName{pmx}, whose output
+is \tex{} input suitable for \Package{musixtex}.
+
+A further preprocessor, \ProgName{M-Tx}, allows preparation of music
+with lyrics; \ProgName{M-Tx}'s output is fed into \ProgName{pmx}, and
+thence to \Package{musixtex}.
+
+An alternative path to music examples within a \alltex{} document is
+\href{http://www.lilypond.org}{\ProgName{Lilypond}}.
+\ProgName{Lilypond} is (at heart) a batch music typesetting system
+with plain text input that does most of its work without \tex{}.
+\ProgName{Lilypond}'s input syntax is less cryptic than is
+MusiX\TeX{}'s, though similar quality is achieved. The
+\ProgName{lilypond}
+\href{http://lilypond.org/web/about/faq}{\acro{FAQ}} mentions programs
+with graphical user interfaces, that export lilypond output.
+
+For occasional music references (sharp and flat signs, notes, clefs
+and so on, there is a (\latex{}) package (with associated font) called
+\Package{lilyglyphs}. This uses \progname{lilypond}'s fonts (which
+are included in the package), and also provides the means to add stuff
+from other sources.
+
+Another alternative in the production of music is the \acro{ABC}
+notation, which was developed to notate the traditional music of
+Western Europe (which can be written on a single stave), though it can
+be used much more widely. A front end to \Package{musictex} (see
+below), \ProgName{abc2mtex}, makes \acro{ABC} typesetting possible.
+
+The program \ProgName{midi2tex} can also generate \Package{musictex}
+output, from \acro{MIDI} files.
+
+The history of music in \tex{} goes back some time; the earliest
+``working'' macros were Mu\tex{}, by Angelika Schofer and Andrea
+Steinbach. Mu\tex{} was very limited, but it was some time before
+Daniel Taupin took up the baton, and developed Music\TeX{}, which
+allows the typesetting of polyphonic and other multiple-stave music;
+Music\TeX{} remains available, but is no longer recommended.
+
+The first version of Musix\tex{} was developed by Andreas Egler, but
+he withdrew from the project to work on another package, Opus\tex{}.
+That never reached the mainstream, and is no longer maintained. The
+current recommended way of doing Opus\tex{}'s job is
+\href{http://home.gna.org/gregorio/}{\ProgName{gregorio}}, which can
+in principle feed into a \tex{}-based document.
+
+Once Andreas Egler had withdrawn (his last version of
+\Package{musixtex} is preserved on the archive), Daniel Taupin took up
+the development, leading to the \Package{musixtex} used today.
+\begin{ctanrefs}
+\item[abc2mtex]\CTANref{abc2mtex}
+\item[lilyglyphs]\CTANref{lilyglyphs}
+\item[M-Tx]\CTANref{m-tx}
+\item[midi2tex]\CTANref{midi2tex}
+\item[musictex]\CTANref{musictex}
+% ! line breaks
+\item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex}
+\item[musixtex \nothtml{\rmfamily}(Egler's version)]\CTANref{musixtex-egler}
+\item[musixtex \nothtml{\rmfamily}fonts]\CTANref{musixtex-fonts}
+\item[mutex]\CTANref{mutex}
+\item[pmx]\CTANref{pmx}
+\end{ctanrefs}
+\LastEdit{2013-09-27}
+
+\Question[Q-parskip]{Zero paragraph indent}
+
+The conventional way of typesetting running text has no separation
+between paragraphs, and the first line of each paragraph in a block of
+text indented.
+
+In contrast, one common convention for typewritten text was to have no
+indentation of paragraphs; such a style is often required for
+``brutalist'' publications such as technical manuals, and in styles
+that hanker after typewritten manuscripts, such as
+officially-specified dissertation formats.
+
+Anyone can see, after no more than a moment's thought, that if the
+paragraph indent is zero, the paragraphs must be separated by blank
+space: otherwise it is sometimes going to be impossible to see the
+breaks between paragraphs.
+
+The simple-minded approach to zero paragraph indentation is thus:
+\begin{quote}
+\begin{verbatim}
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{\baselineskip}
+\end{verbatim}
+\end{quote}
+and in the very simplest text, it's a fine solution.
+
+However, the non-zero \csx{parskip} interferes with lists and the like,
+and the result looks pretty awful. The \Package{parskip} package
+patches things up to look reasonable; it's not perfect, but it deals
+with most problems.
+
+The Netherlands Users' Group's set of classes includes an
+\Class{article} equivalent (\Class{artikel3}) and a \Class{report}
+equivalent (\Class{rapport3}) whose design incorporates zero paragraph
+indent and non-zero paragraph skip.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\acro{NTG} classes]\CTANref{ntgclass}
+\item[parskip.sty]\CTANref{parskip}
+\end{ctanrefs}
+\LastEdit{2011-04-01} % yes, really
+
+\Question[Q-dropping]{Big letters at the start of a paragraph}
+
+A common style of typesetting, now seldom seen except in newspapers,
+is to start a paragraph (in books, usually the first of a chapter)
+with its first letter set large enough to span several lines.
+
+This style is known as ``dropped capitals'', or (in French)
+\latexhtml{``lettrines''}{\htmlentity{laquo}lettrines\htmlentity{raquo}},
+and \TeX{}'s primitive facilities for hanging indentation make its
+(simple) implementation pretty straightforward.
+
+The \Package{dropping} package does the job simply, but has a curious
+attitude to the calculation of the size of the font to be used for the
+big letters. Examples appear in the package documentation, so before
+you process the \extension{dtx}, the package itself must already be
+installed. Unfortunately, \Package{dropping} has an intimate relation
+to the set of device drivers available in an early version of the
+\LaTeX{} graphics package, and it cannot be trusted to work with
+modern offerings such as \PDFTeX{} or \acro{DVI}pdfm, let
+alone such modernisms as \xetex{}. As a result, the package is widely
+deprecated, nowadays.
+
+The more recent \Package{lettrine} package is generally more reliable.
+It has a well-constructed array of options, and an impressive set of
+examples adds to the package's document.
+\begin{ctanrefs}
+\item[dropping]\CTANref{dropping}
+\item[lettrine]\CTANref{lettrine}
+\end{ctanrefs}
+\LastEdit{2014-01-22}
+
+\Question[Q-dec_comma]{The comma as a decimal separator}
+
+\TeX{} embodies the British/American cultural convention of using a
+period as the separator between the whole number and the decimal
+fraction part of a decimal number. Other cultures use a comma as
+separator, but if you use a comma in maths mode you get a small space
+after it; this space makes a comma that is used as a decimal separator
+look untidy.
+
+A simple solution to this problem, in maths mode, is to type
+\texttt{3}\marg{,}\texttt{14} in place of \texttt{3,14}. While such a
+technique may produce the right results, it is plainly not a
+comfortable way to undertake any but the most trivial amounts of
+typing numbers.
+
+Therefore, if you need to use commas as decimal separator, you will
+probably welcome macro support. There are two packages that
+can help relieve the tedium: \Package{icomma} and \Package{ziffer}.
+
+\Package{Icomma} ensures that there will be no extra space after a
+comma, unless you type a space after it (as in \texttt{f(x, y)}~--- in
+the absence of the package, you don't need that space), in which case
+the usual small space after the comma appears. \Package{Ziffer} is
+specifically targeted at the needs of those typesetting German, but
+covers the present need, as well as providing the double-minus sign
+used in German (and other languages) for the empty `cents' part of an
+amount of currency.
+
+The \Package{numprint} package provides a command
+\cmdinvoke*{numprint}{number} that prints its argument according to
+settings you give it, or according to settings chosen to match the
+language you have selected in \Package{babel}. The formatting works
+equally well in text or maths. The command is very flexible (it can also
+group the digits of very `long' numbers), but is inevitably less
+convenient than \Package{icomma} or \Package{ziffer} if you are typing a
+lot of numbers.
+\begin{ctanrefs}
+\item[icomma.sty]Distributed as part of \CTANref{was}[icomma]
+\item[numprint.sty]\CTANref{numprint}
+\item[ziffer.sty]\CTANref{ziffer}
+\end{ctanrefs}
+
+\Question[Q-breakbox]{Breaking boxes of text}
+
+\AllTeX{} boxes may not be broken, in ordinary usage: once you've
+typeset something into a box, it will stay there, and the box will jut
+out beyond the side or the bottom of the page if it doesn't fit in the
+typeset area.
+
+If you want a substantial portion of your text to be framed (or
+coloured), the restriction imposes a serious restriction.
+Fortunately, there are ways around the problem.
+
+The \Package{framed} package provides \environment{framed} and
+\environment{shaded} environments; both put their content into
+something which looks like a framed (or coloured) box, but which
+breaks as necessary at page end. The environments ``lose'' footnotes,
+marginpars and head-line entries, and will not work with
+\Package{multicol} or other column-balancing macros. The
+\Class{memoir} class includes the functionality of the
+\Package{framed} package.
+
+The \Package{mdframed} package does the same job, using a different
+algorithm. The package also provides means of defining
+`private' framed environments, whose parameters are set at definition
+time, thus saving considerable effort in documents with many framed
+boxes. Its restrictions seem much the same as those of
+\Package{framed}; this is as one would expect, but the list is
+noticeably different in the two packages' documentation.
+
+The \Package{boites} package provides a \environment{breakbox}
+environment; examples of its use may be found in the distribution, and
+the package's \File{README} file contains terse documentation. The
+environments may be nested, and may appear inside
+\environment{multicols} environments; however, floats, footnotes and
+marginpars will be lost.
+
+For \plaintex{} users, the facilities of the \Package{backgrnd}
+package may be useful; this package subverts the output routine to
+provide vertical bars to mark text, and the macros are clearly marked
+to show where coloured backgrounds may be introduced (this requires
+\Package{shade}, which is distributed as tex macros and
+device-independent \MF{} for the shading). The author of
+\Package{backgrnd} claims that the package works with \LaTeXo{}, but
+there are reasons to suspect that it may be unstable working with
+current \LaTeX{}.
+\begin{ctanrefs}
+\item[backgrnd.tex]\CTANref{backgrnd}
+\item[boites.sty]\CTANref{boites}
+\item[framed.sty]\CTANref{framed}
+\item[mdframed.sty]\CTANref{mdframed}
+\item[memoir.cls]\CTANref{memoir}
+\item[shade.tex]\CTANref{shade}
+\end{ctanrefs}
+\LastEdit{2012-02-14}
+
+\Question[Q-overstrike]{Overstriking characters}
+
+This may be used, for example, to indicate text deleted in the course
+of editing. Both the \Package{ulem} and the \Package{soul} packages
+provide the necessary facilities.
+
+Overstriking with an ``attached'' comment may be achieved using the
+\Package{pdfcomment} package, to which you can give optional arguments
+with all sorts of detail. The comment text is encoded using an Adobe
+`annotation'; unfortunately, support for these annotations is not a
+common feature of \acro{PDF} viewers, but if you can safely assume
+that your audience will use \ProgName{Acrobat Reader}, the facility
+provides that extra ``shine'' that business users so love.
+
+Overstriking for % beware line break
+\Qref*{cancellation in maths expressions}{Q-cancellation} is achieved
+by a different mechanism.
+
+Documentation of \Package{ulem} is in the package file.
+\begin{ctanrefs}
+\item[pdfcomment.sty]\CTANref{pdfcomment}
+\item[soul.sty]\CTANref{soul}
+\item[ulem.sty]\CTANref{ulem}
+\end{ctanrefs}
+\LastEdit{2013-08-29}
+
+\Question[Q-upquot]{Realistic quotes for verbatim listings}
+
+The \texttt{cmtt} font has ``curly'' quotes\nothtml{ (\texttt{`thus'})},
+which are pleasing on the eye, but don't really tally with what one
+sees on a modern % beware line break
+\ProgName{xterm}\nothtml{ (which look like \texttt{\textasciigrave this\textquotesingle})}.
+
+The appearance of these quotes is critical in program listings,
+particularly in those of Unix-like shell scripts. The
+\Package{upquote} package modifies the behaviour of the
+\environment{verbatim} environment so that the output is a clearer
+representation of what the user must type.
+\begin{ctanrefs}
+\item[upquote.sty]\CTANref{upquote}
+\end{ctanrefs}
+
+\Question[Q-time]{Printing the time}
+
+\TeX{} has a primitive register that contains ``the number of minutes
+since midnight''; with this knowledge it's a moderately simple
+programming job to print the time (one that no self-respecting
+\plaintex{} user would bother with anyone else's code for).
+
+However, \LaTeX{} provides no primitive for ``time'', so the
+non-programming \LaTeX{} user needs help.
+
+Two packages are available, both providing ranges of ways of printing
+the date, as well as of the time: this question will concentrate on
+the time-printing capabilities, and interested users can investigate
+the documentation for details about dates.
+
+The \Package{datetime} package defines two time-printing functions:
+\csx{xxivtime} (for 24-hour time), \csx{ampmtime} (for 12-hour time) and
+\csx{oclock} (for time-as-words, albeit a slightly eccentric set of
+words).
+
+The \Package{scrtime} package (part of the compendious
+\Class{KOMA-Script} bundle) takes a package option (\pkgoption{12h} or
+\pkgoption{24h}) to specify how times are to be printed. The command
+\csx{thistime} then prints the time appropriately (though there's no
+\emph{am} or \emph{pm} in \pkgoption{12h} mode). The \csx{thistime}
+command also takes an optional argument, the character to separate the
+hours and minutes: the default is of course \texttt{:}.
+\begin{ctanrefs}
+\item[datetime.sty]\CTANref{datetime}
+\item[scrtime.sty]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+
+\Question[Q-the-commands]{Redefining counters' \csx{the-}commands}
+
+Whenever you request a new \LaTeX{} counter, \LaTeX{} creates a bunch
+of behind-the-scenes commands, as well as defining the counter
+itself.
+
+Among other things, \cmdinvoke*{newcounter}{fred} creates a command
+\csx{the}\texttt{\emph{fred}}, which expands to ``the value of
+\texttt{\emph{fred}}'' when you're typesetting.
+
+The definition of \csx{the}\texttt{\emph{fred}} should express the
+value of the counter: it is almost always always a mistake to use the
+command to produce anything else. The value may reasonably be
+expressed as an arabic, a roman or a greek number, as an alphabetic
+expression, or even as a sequence (or pattern of) symbols. If you
+need a decision process on whether to re-define
+\csx{the}\texttt{\emph{fred}}, consider what might happen when you do
+so.
+
+So, for example, if you want your section numbers to be terminated by
+a period, you could make \csx{thesection} expand with a terminating
+period. However, such a change to \csx{thesection} makes the
+definition of \csx{thesubsection} look distinctly odd: you are going to
+find yourself redefining things left, right and centre. Rather, use
+the standard techniques for % beware line break
+\Qref*{adjusting the presentation of section numbers}{Q-seccntfmt}.
+
+Or, suppose you want the page number to appear at the bottom of each
+page surrounded by dashes (as in
+``\texttt{-}{}\texttt{-\textasciitilde}\texttt{nnn\textasciitilde-}{}\texttt{-}'').
+If you try to achieve this by redefining \csx{thepage}, problems will
+arise from the use of the page number in the table of contents (each
+number will have the dashes attached), and \csx{pageref} references
+will be oddly modified. In this case, the change of appearance is
+best done by redefining the page style itself, perhaps using
+\Qref*{package \Package{fancyhdr}}{Q-fancyhdr}.
+
+\subsection{Tables of contents and indexes}
+
+\Question[Q-tocloft]{The format of the Table of Contents, etc.}
+
+The formats of entries in the table of contents (\acro{TOC}) are
+controlled by a number of internal commands (discussed in section~2.3
+of \Qref*{\emph{The \LaTeX{} Companion}}{Q-latex-books}. The commands
+\csx{@pnumwidth}, \csx{@tocrmarg} and \csx{@dotsep} control the space
+for page numbers, the indentation of the right-hand margin, and the
+separation of the dots in the dotted leaders, respectively. The
+series of commands named \csx{l@\emph{xxx}}, where \texttt{\emph{xxx}}
+is the name of a sectional heading (such as \texttt{chapter} or
+\texttt{section}, \dots{}\@) control the layout of the corresponding
+heading, including the space for section numbers. All these internal
+commands may be individually redefined to give the effect that you
+want.
+
+All that work may be avoided, using the package \Package{tocloft}
+which provides a set of user-level commands that may be used to change
+the \acro{TOC} formatting. Since exactly the same mechanisms are used
+for the List of Figures and List of Tables, the layout of these
+sections may be controlled in the same way.
+
+The \Package{etoc} package offers similar flexibility, together with
+multicolumn tables of contents and boxes around tables (and the like).
+
+The \Class{KOMA-Script} classes provides an optional variant structure
+for the table of contents, and calculates the space needed for the
+numbers automatically. The \Class{memoir} class includes the functionality
+of \Package{tocloft}.
+\begin{ctanrefs}
+\item[etoc.sty]\CTANref{etoc}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[tocloft.sty]\CTANref{tocloft}
+\end{ctanrefs}
+\LastEdit{2012-12-07}
+
+\Question[Q-secnumdep]{Unnumbered sections in the Table of Contents}
+
+The way the relevant parts of sectioning commands work is exemplified
+by the way the \csx{chapter} command uses the counter \texttt{secnumdepth}
+(described in Appendix~C of the \LaTeX{} manual):
+\begin{enumerate}
+\item put something in the \extension{aux} file, which will appear in
+ the \extension{toc};
+\htmlignore
+\item if \ensuremath{\texttt{secnumdepth} \geq 0},
+\endhtmlignore
+\begin{htmlversion}
+\item if the \texttt{secnumdepth} counter is greater than or equal to
+ zero,
+\end{htmlversion}
+ increase the counter for the chapter and write it out.
+\item write the chapter title.
+\end{enumerate}
+Other sectioning commands are similar, but with other values used in
+the test.
+
+So a simple way to get headings of funny `sections' such as prefaces
+in the table of contents is to use the counter:
+\begin{quote}
+\begin{verbatim}
+\setcounter{secnumdepth}{-1}
+\chapter{Preface}
+\end{verbatim}
+\end{quote}
+Unfortunately, you have to set \texttt{secnumdepth} back to its usual
+value (which is~2 in the standard styles) before you do any `section'
+which you want to be numbered.
+
+Similar settings are made, automatically, in the \LaTeX{} book class by
+the \csx{frontmatter} and \csx{backmatter} commands.
+
+The value of the counter \texttt{tocdepth} controls which headings
+will be finally printed in the table of contents; it is normally set
+in the preamble and is a constant for the document. The package
+\Package{tocvsec2} package takes the tedium out of changing the
+\texttt{secnumdepth} and/or the \texttt{tocdepth} counter values at
+any point in the body of the document; the commands (respectively)
+\csx{setsecnumdepth} and \csx{settocdepth} make the changes based on
+the \emph{name} of the sectional unit (\texttt{chapter},
+\texttt{section}, etc.\@).
+
+The package \Package{abstract} (see % line break!
+\Qref[question]{one-column abstracts}{Q-onecolabs}) includes an option
+to add the \texttt{abstract} to the table of contents, while the
+package \Package{tocbibind} has options to include the table of
+contents itself, the \texttt{bibliography}, \texttt{index}, etc., to
+the table of contents.
+
+The \Class{KOMA-Script} classes have commands \csx{addchap} and
+\csx{addled}, which work like \csx{chapter} and \csx{section} but
+aren't numbered. The \Class{memoir} class incorporates the facilities
+of all three of the \Package{abstract}, \Package{tocbibind} and
+\Package{tocvsec2} packages.
+\begin{ctanrefs}
+\item[abstract.sty]\CTANref{abstract}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[tocbibind.sty]\CTANref{tocbibind}
+\item[tocvsec2.sty]\CTANref{tocvsec2}
+\end{ctanrefs}
+
+\Question[Q-tocbibind]{Bibliography, index, etc., in \acro{TOC}}
+
+The standard \LaTeX{} classes (and many others) use \csx{section*} or
+\csx{chapter*} for auto-generated parts of the document (the tables of
+contents, lists of figures and tables, the bibliography and the index). As a
+result, these items aren't numbered (which most people don't mind),
+and (more importantly) they don't appear in the table of contents.
+
+The correct solution (as always) is to have a class of your own that
+formats your document according to your requirements. The macro to do
+the job (\csx{addcontentsline}) is fairly simple, but there is always
+an issue of ensuring that the contents entry quotes the correct page.
+Supposing that our the document is chapter-based (class \Class{report}
+or \Class{book}, for example), the text:
+\begin{quote}
+\begin{verbatim}
+\bibliography{frooble}
+\addcontentsline{toc}{chapter}{Bibliography}
+\end{verbatim}
+\end{quote}
+will produce the \emph{wrong} answer if the bibliography is more than
+one page long. Instead, one should say:
+\begin{quote}
+\begin{verbatim}
+\cleardoublepage
+\addcontentsline{toc}{chapter}{Bibliography}
+\bibliography{frooble}
+\end{verbatim}
+\end{quote}
+(Note that \csx{cleardoublepage} does the right thing, even if your
+document is single-sided~--- in that case, it's a synonym for
+\csx{clearpage}). Ensuring that the entry refers to the right place is
+trickier still in a \csx{section}-based class.
+
+If you are using \Package{hyperref} (which will link entries in the
+table of contents to the relevant place in the file), a slight
+adjustment is necessary:
+\begin{quote}
+\begin{verbatim}
+\cleardoublepage
+\phantomsection
+\addcontentsline{toc}{chapter}{Bibliography}
+\bibliography{frooble}
+\end{verbatim}
+\end{quote}
+The extra command (\csx{phantomsection}) gives \Package{hyperref}
+something to ``hold on to'' when making the link.
+
+The common solution, therefore, is to use the \Package{tocbibind}
+package, which provides many facilities to control the way these
+entries appear in the table of contents.
+
+Classes of the \Class{KOMA-script} bundle provide this functionality
+as a set of class options (e.g., \pkgoption{bibtotoc} to add the
+bibliography to the table of contents); the \Class{memoir} class includes
+\Package{tocbibind} itself.
+\begin{ctanrefs}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[tocbibind.sty]\CTANref{tocbibind}
+\end{ctanrefs}
+
+\Question[Q-minitoc]{Table of contents, etc., per chapter}
+
+The common style, of a ``small'' table of contents for each part,
+chapter, or even section, is supported by the \Package{minitoc}
+package. The package also supports mini-lists of tables and figures;
+but, as the documentation observes, mini-bibliographies present a
+different problem~--- see
+\Qref[question]{bibliographies per chapter}{Q-chapbib}.
+
+The package's basic scheme is to generate a little \extension{aux} file for
+each chapter, and to process that within the chapter. Simple usage
+would be:
+\begin{quote}
+\begin{verbatim}
+\usepackage{minitoc}
+...
+\begin{document}
+...
+\dominitoc \tableofcontents
+\dominilof \listoffigures
+...
+\chapter{blah blah}
+\minitoc \mtcskip \minilof
+...
+\end{verbatim}
+\end{quote}
+though a lot of elaborations are possible (for example, you don't need
+a \csx{minitoc} for every chapter).
+
+\Package{Babel} doesn't know about \Package{minitoc}, but
+\Package{minitoc} makes provision for other document languages than
+English~--- a wide variety is available. Fortunately, the current
+version of the \Package{hyperref} package does know about
+\Package{minitoc} and treats \csx{minitoc} tables in the
+same way as ``real'' tables of contents.
+\begin{ctanrefs}
+\item[babel.sty]\CTANref{babel}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[minitoc.sty]\CTANref{minitoc}
+\end{ctanrefs}
+\LastEdit{2013-03-05}
+
+\Question[Q-multind]{Multiple indexes}
+
+\LaTeX{}'s standard indexing capabilities (those provided by the
+\Package{makeidx} package) only provide for one index in your
+document; even quite modest documents can be improved by indexes for
+separate topics.
+
+The \Package{multind} package provides simple and straightforward
+multiple indexing. You tag each \csx{makeindex}, \csx{index} and
+\csx{printindex} command with a file name, and indexing commands are
+written to (or read from) the name with the appropriate (\extension{idx} or
+\extension{ind}) extension appended. The \csx{printindex} command is modified
+from an old version of the \LaTeXo{} standard so that it doesn't
+create its own chapter or section heading; you therefore decide what
+names (or sectioning level, even) to use for the indexes, and
+\Qref*{\csx{indexname}}{Q-fixnam} is completely ignored.
+
+To create a ``general'' and an ``authors'' index, one might write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{multind}
+\makeindex{general}
+\makeindex{authors}
+...
+\index{authors}{Eccentric Professor}
+...
+\index{general}{FAQs}
+...
+\printindex{general}{General index}
+\printindex{authors}{Author index}
+\end{verbatim}
+\end{quote}
+To complete the job, run \LaTeX{} on your file enough times that
+labels, etc., are stable, and then execute the commands
+\begin{quote}
+\begin{verbatim}
+makeindex general
+makeindex authors
+\end{verbatim}
+\end{quote}
+before running \LaTeX{} again. Note that the names of the index files
+to process are not necessarily related to the name of the \LaTeX{}
+file you're processing, at all. (There's no documentation that comes
+with the package: what you see above is as good as you will
+get\dots{})
+
+The \Package{multind} package doesn't work with the % ! line break
+\Qref*{\amslatex{} classes}{Q-AMSpkg}, but the \acro{AMS} provide a
+substitute, the \Package{amsmidx} package. You use the
+\Package{amsmidx} package pretty much the same as you would
+\Package{multind}, but if things aren't clear, there \emph{is}
+documentation (unlike \Package{multind}).
+
+The \Package{index} package provides a comprehensive set of indexing
+facilities, including a \csx{newindex} command that allows the
+definition of new styles of index. \csx{newindex} takes a `tag' (for
+use in indexing commands), replacements for the \extension{idx} and
+\extension{ind} file extensions, and a title for the index when it's
+finally printed; it can also change the item that's being indexed
+against (for example, one might have an index of artists referenced by
+the figure number where their work is shown).
+
+Using \Package{index}, to create an author index together with a
+``normal'' index, one would start with preamble commands:
+\begin{quote}
+\begin{verbatim}
+\usepackage{index}
+\makeindex
+\newindex{aut}{adx}{and}{Name Index}
+\end{verbatim}
+\end{quote}
+which load the package, define a ``main'' (original-style) index, and
+then define an author index. Then, in the body of the document, we
+might find commands like:
+\begin{quote}
+\begin{verbatim}
+\index[aut]{Another Idiot}
+...
+\index{FAQs}
+\end{verbatim}
+\end{quote}
+Which place an entry in the author index, and then one in the main
+index. At the end of the document, we have two commands:
+\begin{quote}
+\begin{verbatim}
+\printindex
+\printindex[aut]
+\end{verbatim}
+\end{quote}
+Which will print the main index and then the author index. Supposing
+this lot to be in \File{myfile.tex}, after enough runs through
+\LaTeX{} that labels are stable, execute the following commands
+(Unix-style shell commands shown here, but the principle is the same
+whatever system you're using):
+\begin{quote}
+\begin{verbatim}
+makeindex myfile
+makeindex myfile.adx -o myfile.and
+\end{verbatim}
+\end{quote}
+and rerun \LaTeX{}. The \ProgName{makeindex} commands process
+\File{myfile.idx} to \File{myfile.ind} (the default action), and then
+\File{myfile.adx} to \File{myfile.and}, the two files needed as input
+by the two \csx{printindex} commands in \File{myfile.tex}.
+
+The \Package{splitidx} package can operate in the same way as the
+others: load the package with the \pkgoption{split} option, and
+declare each index with a \csx{newindex} command:
+\begin{quote}
+ \cmdinvoke{newindex}[\meta{index name}]{\meta{shortcut}}
+\end{quote}
+and \Package{splitidx} will generate a file
+\csx{jobname}\texttt{.\meta{shortcut}} to receive index entries
+generated by commands like \cmdinvoke{sindex}[\meta{shortcut}]{\meta{item}}.
+As with the other packages, this method is limited by \TeX{}'s total
+number of output files. However, \Package{splitindex} also comes with
+a small executable \ProgName{splitindex} (available for a variety of
+operating systems); if you use this auxiliary program (and don't use
+\pkgoption{split}), there's no limit to the number of indexes. Apart
+from this trick, \Package{splitidx} supports the same sorts of things
+as does \Package{index}. An example of use appears in
+the documentation.
+
+The \Package{imakeidx} package can do a wide range of things (in particular,
+it can run an index-builder~--- via % ! line break
+\Qref*{\csx{write18} commands}{Q-spawnprog}~--- so as to simplify
+business of making the final copy of a document). The package can
+also make multiple indexes; it can do the job in the conventional
+(\Package{multind}) way, or by using the external
+\ProgName{splitindex} script provided with the \Package{splitindex}
+package. (This arrangement allows efficient operation with small
+numbers of indexes, while retaining the flexibility of permitting
+large numbers of indexes without hitting the restriction of numbers of
+active output streams.)
+
+The \Class{memoir} class has its own multiple-index functionality (as
+well as its own index layout options, which other packages delegate to
+the index style used by \ProgName{makeindex}).
+\begin{ctanrefs}
+\item[amsmidx.sty]Part of the \acro{AMS} class distribution
+ \CTANref{amscls}[amsmidx]
+\item[imakeidx.sty]\CTANref{imakeidx}
+\item[index.sty]\CTANref{index}
+\item[makeidx.sty]Part of the \LaTeX{} distribution
+\item[memoir.cls]\CTANref{memoir}
+\item[multind.sty]\CTANref{multind}
+\item[splitidx.sty \bgroup\nothtml{\normalfont}and \egroup splitindex]%
+ \CTANref{splitindex}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-backgrnd.tex b/help/uk-tex-faq/faq-backgrnd.tex
new file mode 100644
index 0000000000..4b3ed75156
--- /dev/null
+++ b/help/uk-tex-faq/faq-backgrnd.tex
@@ -0,0 +1,1220 @@
+% $Id: faq-backgrnd.tex,v 1.31 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{The Background}
+
+\Question[Q-startup]{Getting started}
+
+\alltex{} offers a very large number of choices, and the beginner has
+to navigate through that set before even taking his first steps. The
+aim here is to guide the beginner through a set of answers that may
+help the process. We assume the beginner `knows' that \alltex{} is
+for them; if not, the discussion ``\Qref{what is \tex{}}{Q-whatTeX}''
+may help.
+
+To start at the very beginning, then, the beginner may wish to know
+what all those % ! line break
+``\Qref*{things with \tex{} in their name are}{Q-texthings}''.
+
+Armed with that knowledge, the beginner needs to decide what macro
+format she needs (always assuming someone hasn't already told her she
+needs to use ``foo\tex{}''. Learn about the alternatives in answers
+discussing common formats: look at % line break
+\Qref*{writing \plaintex{}}{Q-plaintex},
+\Qref*{\latex{}}{Q-latex} or
+\Qref*{\context{}}{Q-context}.
+
+If no system has been provided, the beginner needs to acquire a \tex{}
+distribution appropriate to their machine. Available options are
+available via the answer % ! line break
+``\Qref*{\alltex{} for various machines}{Q-TeXsystems}''; we assume
+here that the beginner can install things for herself, or has access
+to someone who can.
+
+Finally, the beginner needs to get started in the chosen format. For
+\plaintex{}, see ``\Qref[]{Online introductions: \TeX{}}{Q-man-tex}'';
+for \latex{}, see % ! line break
+``\Qref[]{Online introductions: \LaTeX{}}{Q-man-latex}''; and for
+\context{}, the place to start is the % line break
+\href{http://wiki.contextgarden.net/Main_Page}{ConTeXt garden wiki}
+(which is so good the present \acro{FAQ}s don't even try to compete).
+\LastEdit*{2011-03-04}
+
+
+\Question[Q-whatTeX]{What is \TeX{}?}
+
+\TeX{} is a typesetting system written by
+\href{http://sunburn.stanford.edu/~knuth/}{Donald E. Knuth}, who
+says in the Preface to his book on \TeX{}
+(see \Qref[question]{books about TeX}{Q-tex-books}) that it is
+%% !line wrap avoided by two commands
+``\emph{intended for the creation of beautiful books~---}
+\emph{and especially for books that contain a lot of mathematics}''.
+(If \TeX{} were \emph{only} good for mathematical books, much of its
+use nowadays would not happen: it's actually a pretty good general
+typesetting system.)
+
+Knuth is Emeritus Professor of the Art of Computer Programming at
+Stanford University in California, \acro{USA}. Knuth developed the
+first version of \TeX{} in 1978 to deal with revisions to his series
+``the Art of Computer Programming''. The idea proved popular and
+Knuth produced a second version (in 1982) which is the basis of what
+we use today.
+
+Knuth developed a system of % ! line breaks
+`\Qref*{literate programming}{Q-lit}' to write \TeX{},
+and he provides the literate (\acro{WEB}) source of \TeX{} free of charge,
+together with tools for processing the |web| source into something
+that can be compiled and something that can be printed; there is (in
+principle) never any mystery about what \TeX{} does. Furthermore, the
+\acro{WEB} system provides mechanisms to port \TeX{} to new operating
+systems and computers; and in order that one may have some confidence
+in the ports, Knuth supplied a \Qref*{test}{Q-triptrap} by
+means of which one may judge the fidelity of a \TeX{} system. \TeX{}
+and its documents are therefore highly portable.
+
+For the interested programmer, the distribution of \TeX{} has some
+fascination: it's nothing like the way one would construct such a
+program nowadays, yet it has lasted better than most, and has been
+ported to many different computer architectures and operating
+systems~--- the sorts of attributes that much modern programming
+practice aims for. The processed `readable' source of \TeX{} the
+program may be found in the % ! line break
+\begin{hyperversion}
+ \Qref*{\acro{TDS} structured}{Q-tds} version of the distribution.
+\end{hyperversion}
+\begin{dviversion}
+ \acro{TDS} structured version of the distribution (see
+ \Qref*{\acro{TDS} structure}{Q-tds}).
+\end{dviversion}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Knuth's source distribution]\CTANref{knuth-dist}
+\item[\nothtml{\rmfamily}Knuth's sources in \acro{TDS} layout]\CTANref{knuth-tds}
+\end{ctanrefs}
+\LastEdit{2013-11-27}
+
+\Question[Q-plaintex]{What's ``writing in \TeX{}''?}
+
+\TeX{} is a macro processor, and offers its users a powerful
+programming capability. To produce a document, you write macros and
+text interleaved with each other. The macros define an environment in
+which the text is to be typeset.
+
+However, the basic \TeX{} engine is pretty
+basic, and is a pretty difficult beast to deal with. Recognising this
+(and not wanting to write the same things at the start of every
+document, himself) Knuth provided a package of macros for use with
+\TeX{}, called \plaintex{}; \plaintex{} is a useful minimum set of
+macros that can be used with \TeX{}, together with some demonstration
+versions of higher-level commands. When people say they're ``writing
+(or programming) in \TeX{}'', they usually mean they're programming in
+\plaintex{}.
+
+\Question[Q-TeXpronounce]{How should I pronounce ``\TeX{}''?}
+
+The `X' is ``really'' the Greek letter % ! line break
+Chi\nothtml{ (\ensuremath{\chi}, in lower case)}, and is pronounced by
+English-speakers either a bit like the `ch' in the Scots word `loch'
+([x] in the IPA) or (at a pinch, if you can't do the Greek sound) like
+`k'. It definitely is not pronounced `ks' (the Greek letter with that
+sound doesn't look remotely like the Latin alphabet `X').
+
+This curious usage derives from Knuth's explanation in the \TeX{}book
+that the name comes from the Greek word for `art' or `craft'
+(`\latexhtml{\ensuremath{\tau\epsilon\chi\nu\eta}}{\emph{techni}}'),
+which is the root of the English word `technology'. Knuth's logo for \TeX{} is
+merely the uppercase version of the first three (Greek) letters of the
+word, jiggled about a bit; we don't use that logo (and logos like it)
+in this \acro{FAQ} (see % ! line break
+\Qref[question]{Typesetting \TeX{}-related logos}{Q-logos}).
+
+\Question[Q-MF]{What is \MF{}?}
+
+\MF{} was written by Knuth as a companion to \TeX{}; whereas \TeX{}
+defines the layout of glyphs on a page, \MF{} defines the shapes of
+the glyphs and the relations between them. \MF{} details the sizes of
+glyphs, for \TeX{}'s benefit, and creates bitmaps that may be used to
+represent the glyphs, for the benefit of programs that will produce
+printed output as post processes after a run of \TeX{}.
+
+\MF{}'s language for defining fonts permits the expression of several
+classes of things: first (of course), the simple geometry of the
+glyphs; second, the properties of the print engine for which the
+output is intended; and third, `meta'-information which can
+distinguish different design sizes of the same font, or the difference
+between two fonts that belong to the same (or related) families.
+
+Knuth (and others) have designed a fair range of fonts using \MF{},
+but font design using \MF{} is much more of a minority skill (even) than is
+\TeX{} macro-writing.
+What is more, it is a dying art: few new \tex{}-related fonts are
+produced using \MF{}, nowadays. Indeed, several of the major font
+families (that originated in \MF{} designs) are now seldom used in any
+other way than their conversion to an outline font format.
+%% The complete \TeX{}-user nevertheless needs to
+%% be aware of \MF{}, and may even be required run \MF{} to generate personal
+%% copies of Meta-fonts that come her way.
+\LastEdit{2011-07-03}
+
+\Question[Q-MP]{What is \MP{}?}
+
+The \MP{} system (by John Hobby) implements a picture-drawing language
+very much like that of \MF{}; the difference is that \MP{} outputs
+vector graphic files instead of run-length-encoded bitmaps; output
+formats available are \PS{} or \acro{SVG}
+\MP{}
+is a powerful language for producing figures for documents to be
+printed on \PS{} printers, either directly or embedded in \AllTeX{}
+documents. \MP{} is able to integrate text and mathematics, marked up
+for use with \TeX{}, within the graphics. (Knuth tells us that he
+uses nothing but \MP{} for diagrams in text that he is writing.)
+
+Although \PDFLaTeX{} cannot ordinarily handle \PS{} graphics, the
+output of \MP{} is sufficiently simple and regular that \PDFLaTeX{}
+can handle it direct, using code borrowed from
+\begin{hyperversion}
+ \Qref*{\context{}}{Q-context}~---
+\end{hyperversion}
+\begin{flatversion}
+ \context{}~---
+\end{flatversion}
+see \Qref[question]{graphics in \PDFLaTeX{}}{Q-pdftexgraphics}.
+
+Much of \MP{}'s source code was copied from \MF{}'s sources, with
+Knuth's permission.
+
+A mailing list discussing \MP{} is available;
+\begin{flatversion}
+ subscribe via the \acro{TUG} \ProgName{mailman} interface at
+ \URL{http://lists.tug.org/metapost}
+\end{flatversion}
+\begin{hyperversion}
+ subscribe via the % ! line break
+ \href{http://lists.tug.org/metapost}{\acro{TUG} \ProgName{mailman} interface}.
+\end{hyperversion}
+The \acro{TUG} website also hosts a % ! line break
+\href{http://tug.org/metapost.html}{\MP{} summary page}, and the
+\Package{tex-overview} document gives you a lot more detail (and some
+explanatory background material).
+\begin{ctanrefs}
+\item[tex-overview.pdf]\CTANref{tex-overview}
+\end{ctanrefs}
+\LastEdit{2013-12-10}
+
+\Question[Q-texthings]{Things with ``\TeX{}'' in the name}
+
+New \TeX{} users are often baffled by the myriad terms with ``\TeX{}''
+in the name. The goal of this answer is to clarify some of the more
+common such terms.
+
+\paragraph{\TeX{} itself}
+\TeX{} proper is a typesetting system based on a set of low-level
+control sequences that instruct \TeX{} how to lay out text on the
+page. For example, \csx{hskip} inserts a given amount of horizontal
+space into the document, and \csx{font} makes a given font available
+in a document. \TeX{} is fully programmable using an integrated macro
+scripting language that supports variables, scoping, conditional
+execution, control flow, and function (really, macro) definitions.
+See % ! line break
+\Qref[question]{what is \TeX{}?}{Q-whatTeX} for some background
+information on \TeX{} and % ! line break
+\Qref[question]{some reference documents}{Q-ref-doc} for pointers to
+descriptions of \TeX{} control sequences, data types, and other key
+parts of \TeX{}.
+
+\paragraph{\TeX{} macro packages (a.k.a.~\TeX{} formats)}
+Some of \TeX{}'s control sequences are tedious to use directly; they are
+intended primarily as building blocks for higher-level~--- and therefore
+more user-friendly~--- abstractions. For example, there is no way in
+base \TeX{} to specify that a piece of text should be typeset in a
+larger font. Instead, one must keep track of the current size and
+typeface, load a new font with the same typeface but a (specified)
+larger size, and tell \TeX{} to use that new font until instructed
+otherwise. Fortunately, because \TeX{} is programmable, it is
+possible to write a macro that hides this complexity behind a simple,
+new control sequence. (For example, it is possible to define
+\cmdinvoke{larger}{my text} to typeset ``my text'' in
+at a font size next larger than the current one.)
+
+While some users write their own, perfectly customized set of
+macros~--- which they then typically reuse across many documents~--- it is
+far more common to rely upon a \emph{macro package}, a collection of
+\TeX{} macros written by experts. For the user's convenience, these
+macro packages are often combined with the base \TeX{} engine into a
+standalone executable. The following are some of that macro packages
+that you are likely to encounter:
+\begin{description}
+ \item[Plain \TeX{} (executable: \ProgName{tex})]
+ See
+ \Qref[questions]{Books on \TeX{} and \plaintex{}}{Q-tex-books},
+ \Qref[]{Online introductions: \TeX{}}{Q-man-tex},
+ \Qref[]{Should I use Plain \TeX{} or \LaTeX{}?}{Q-plainvltx} and
+ \Qref[]{Freely available \AllTeX{} books}{Q-ol-books}.
+ Note that the Plain \TeX{} executable is called \ProgName{tex}; the
+ base \TeX{} engine is generally provided by a separate executable
+ such as \ProgName{initex} or as a \texttt{-ini} flag to
+ \ProgName{tex}.
+
+ \item[\LaTeX{} (executable: \ProgName{latex})]
+ See
+ \Qref[questions]{Books on \TeX{} and its relations}{Q-latex-books},
+ \Qref[]{\AllTeX{} Tutorials, etc.}{Q-tutorials*},
+ \Qref[]{Online introductions: \LaTeX{}}{Q-man-latex} and
+ \Qref[]{Specialized \AllTeX{} tutorials}{Q-tutbitslatex}.
+ Note that there have been two major versions of \LaTeX{}: \LaTeXe{}
+ refers to the current version of \LaTeX{} while \LaTeXo{} is the
+ long-since-obsolete (since 1994) version (cf.~%
+ \Qref[question]{What is \LaTeXe{}?}{Q-latex2e} for more information).
+
+ \item[\CONTeXT{} (executable: \ProgName{texmfstart})]
+ See
+ \Qref[question]{What is \CONTeXT{}?}{Q-context}.
+
+ \item[Texinfo (executables: \ProgName{tex}, \ProgName{makeinfo})]
+ See
+ \Qref[question]{What is Texinfo?}{Q-texinfo}. \ProgName{makeinfo}
+ converts Texinfo documents to \acro{HTML}, DocBook, Emacs info,
+ \acro{XML}, and plain text. \ProgName{Tex} (or wrappers such as
+ \ProgName{texi2dvi} and \ProgName{texi2pdf}) produce one of \TeX{}'s
+ usual output formats such as \acro{DVI} or \acro{PDF}. Because
+ \ProgName{tex} loads the Plain \TeX{} macros, not the Texinfo ones,
+ a Texinfo document must begin with
+ \begin{quote}
+ \csx{input}\texttt{ texinfo}
+ \end{quote}
+ explicitly load the Texinfo macro package.
+
+ \item[\Eplain{}~--- Extended Plain \TeX{} (executable: \ProgName{eplain})]
+ See
+ \Qref[question]{What is \Eplain{}?}{Q-eplain}.
+\end{description}
+
+\paragraph{Modified \ProgName{tex} executables}
+The original \ProgName{tex} executable was produced in the late 1970s
+(cf.~\Qref[question]{What is \TeX{}?}{Q-whatTeX}) and consequently
+lacked some features that users have come to expect from today's
+software. The following programs address these issues by augmenting
+the \TeX{} engine with some additional useful features:
+
+\begin{description}
+ \item[\PDFTeX{} (executable: \ProgName{pdftex})]
+ \TeX{}, which predates the \acro{PDF} file format by a decade,
+ outputs files in a \TeX{}-specific format called \acro{DVI}
+ (cf.~\Qref[question]{What is a \acro{DVI} file?}{Q-dvi}). In
+ contrast, \PDFTeX{} can output both \acro{DVI} \emph{and} \acro{PDF}
+ files. In \acro{PDF} mode, it lets documents exploit various
+ \acro{PDF} features such as hyperlinks, bookmarks, and annotations,
+ \PDFTeX{} additionally supports two sophisticated micro-typographic
+ features: character protrusion and font expansion. See
+ \Qref[question]{What is \PDFTeX{}?}{Q-whatpdftex}.
+
+ \item[\xetex{} (executable: \ProgName{xetex})]
+ \xetex{} reads \acro{UTF}-8 encoded Unicode input, and extends
+ \TeX{}'s font support to include `modern' formats such as TrueType
+ and OpenType; these extensions to its capabilities make it
+ well-suited to multi-lingual texts covering different writing
+ systems. See \Qref[question]{What is \xetex{}?}{Q-xetex}.
+
+ \item[\LuaTeX{} (executable: \ProgName{luatex})]
+ \TeX{} is programmed in its own arcane, integrated, macro-based
+ programming language. \LuaTeX{} adds a second programming engine
+ using a modern scripting language, Lua, which is `embedded' in a
+ \tex{}-alike engine; it too reads \acro{UTF}-8 and uses TrueType
+ OpenType fonts. See % ! line break
+ \Qref[question]{What is \LuaTeX{}?}{Q-luatex}.
+
+ \item[\eTeX{} (executable: \ProgName{etex})]
+ \eTeX{} is an extension of \tex{}'s programming interface; as such
+ it's only indirectly useful to end users, but it can be valuable to
+ package developers; there is an increasing number of macro packages
+ that require the use of \eTeX{}. As well as existing in
+ \ProgName{etex}, \eTeX{} features are usually available in the
+ \ProgName{pdftex} executables provided in the standard
+ distributions; \xetex{} and \luatex{} also provide \etex{}'s
+ programming facilities. See % ! line break
+ \Qref[question]{What is \eTeX{}?}{Q-etex}.
+
+ (Note: \eTeX{}, which enhances the \TeX{} engine, is not to be
+ confused with \Eplain{}, which enhances the Plain \TeX{} macro
+ package.)
+\end{description}
+
+Because each of the above derive from a base \TeX{} engine, it is in
+principle possible to combine any of them with one of the \TeX{} macro
+packages listed earlier to produce `extended' executables. For
+example, the \ProgName{pdflatex}, \ProgName{xelatex} and
+\ProgName{lualatex} executables each combine \LaTeX{} with an enhanced
+\TeX{} engine. Indeed, most (if not all) of the development of
+\context{} is now using \luatex{}.
+
+Some executables combine the features of multiple enhanced \TeX{}
+engines: for example, \ProgName{pdftex} now (in current distributions)
+offers both \PDFTeX{} and \eTeX{} extensions into a single executable
+This executable may be offered with a \LaTeX{} format (as
+\ProgName{latex} or \ProgName{pdflatex}) or with a \plaintex{} format
+(as \ProgName{pdftex}). (\ProgName{Tex} remains with an unadorned
+\TeX{} executable using \plaintex{}, for people such as Knuth himself,
+who want the certainty of the ``original''.)
+
+\paragraph{\TeX{} distributions}
+A \emph{\TeX{} distribution} provides a structured collection of
+\TeX{}-related software. Generally, a \TeX{} distribution includes a
+set of ``core'' \TeX{} executables such as \ProgName{tex} and
+\ProgName{latex}; various fonts optimized for use with \TeX{}; helper
+programs such as the \BibTeX{} bibliographic-database formatter,
+editors, integrated development environments, file-format-conversion
+programs; numerous \LaTeX{} packages; configuration tools; and any
+other goodies the distributor chooses to include.
+
+Commonly encountered \TeX{} distributions include \texlive{},
+\miktex{} and Mac\TeX{}; older ones include oz\TeX{},
+\acro{CM}ac\TeX{} and te\TeX{}. \miktex{} is also available as the
+basis of the Pro\TeX{}t bundle, distributed on the \texlive{}
+\acro{DVD} mailing, as well as being available online.
+
+Some \TeX{} distributions target a specific operating system and/or
+processor architecture; others run on multiple platforms. Many \TeX{}
+distributions are free; a few require payment. See % ! line break
+\Qref[question]{\AllTeX{} for different machines}{Q-TeXsystems} for a
+list of free and shareware \TeX{} distributions and % ! line break
+\Qref[question]{Commercial \TeX{} implementations}{Q-commercial} for a
+list of commercial \TeX{} distributions.
+
+\paragraph{Summary}
+What does it all mean?~--- the simple lists of objects, alone, offer
+no help for the beginner. The \acro{FAQ} team expects this answer
+only to be of use for people who are seeking guidance elsewhere
+(possibly within these \acro{FAQ}s) and coming across an unexpected
+name like ``blah\tex{}''.
+
+The subject matter covered by this answer is also addressed in a page
+on the \acro{TUG} site, % ! line break
+``\href{http://tug.org/levels.html}{the Levels of \tex{}}''.
+\LastEdit{2011-09-26}
+
+\Question[Q-ctan]{What is \acro{CTAN}?}
+
+The acronym stands for ``Comprehensive \tex{} Archive Network'', which
+more-or-less specifies what it's \emph{for}:
+\begin{itemize}
+\item The archives offer a comprehensive collection of \tex{} resources.
+\item The content is made publicly accessible, via the internet.
+\item \acro{CTAN} is a \emph{network} of archives, which strive to
+ stay in step with one another.
+\end{itemize}
+The basic framework was developed by a \acro{TUG} working group set up
+to resolve the (then existing) requirement for users to \emph{know} on
+which archive site a particular package might be found.
+
+Actual implementation offers three distinct types of host:
+\begin{description}
+\item[\emph{Core} archives]Which form a small, tightly-coupled set of
+ machines, which perform management functions as well as serving
+ files;
+\item[\emph{Mirror} archives]Which do no more than take regular copies
+ of core archives, and serve them; and
+\item[Archive selector]Which is a meta-service, which routes requests
+ to an apparently ``local'' mirror (``local'' is determined by an
+ algorithm that uses your net address to determine where you are, and
+ then selects a mirror that's close).
+\end{description}
+Note that there is nothing to prevent any archive from supporting
+other functions, so a \acro{CTAN} mirror may also operate as a
+\acro{CPAN} (Perl) mirror and as a SourceForge (general free software)
+mirror, and \dots{}
+
+Functions that distinguish core archives are:
+\begin{itemize}
+\item Uploads: users may submit new (or updated) material via the
+ \Qref*{upload redirector}{Q-uploads}. Significant changes to the
+ archive are reported via the mailing list \Email{ctan-ann@dante.de}
+\item Weak consistency: changes to the content of the archives are
+ rapidly distributed to all core archives. (Consistency is `weak'
+ since changes can take several minutes to propagate.)
+\item Providing distribution (\texlive{} and \miktex{}) support.
+\item Catalogue maintenance.
+\item Mirror monitoring.
+\end{itemize}
+
+Users may make direct contact with the
+\begin{flatversion}
+ \ctan{} management team, via \mailto{ctan@dante.de}
+\end{flatversion}
+\begin{hyperversion}
+ \href{mailto:ctan@dante.de}{\ctan{} management team}.
+\end{hyperversion}
+
+Users should ordinarily download material from \acro{CTAN} via the
+\href*{http://mirror.ctan.org/}{archive selector}: this uses the
+mirror monitor's database, and uses the caller's geographical location to
+offer an efficient choice of ``sufficiently up-to-date'' mirror site for
+you to connect to. This procedure has the advantage of distributing
+the load on \ctan{} mirrors.
+
+Note that all the download links, given in the web representation of
+these \acro{FAQ}s, are set up to use the mirror selector.
+\LastEdit{2013-05-21}
+
+\Question[Q-catalogue]{The (\acro{CTAN}) catalogue}
+
+Finding stuff on networks used always to be difficult, but in recent years,
+search engines have become amazingly good at digging out unconsidered
+trifles from the myriad items of information available on the net.
+However, for the \alltex{} user, confusion is added by the tendency to
+index the same file at several \acro{CTAN} mirror sites.
+
+Further, the \alltex{} user usually needs the most recent version of a
+package; it's a rare search result that describes itself as obsolete!
+
+The \acro{CTAN} catalogue, several years after it was introduced, has
+developed into a powerful tool for dealing with these difficulties.
+It provides an entry for each package to be found on \acro{CTAN};
+users may search the catalogue for an entry, or they may browse its
+contents, using the catalogue's lists of ``categories'' of item.
+
+The basis of the catalogue is a collection of small, stylised,
+articles; each shows basic information about a package on \acro{CTAN},
+and includes pointers to download address (on a \acro{CTAN} mirror),
+documentation and home page if any, and related packages.
+
+The \href{http://www.ctan.org}{\acro{CTAN} central database machine}
+offers a ``Browse \acro{CTAN}'' area, with links to the list of
+packages, to a list of `topics' (with packages that match each topic),
+and to a list of authors (with their packages).
+
+In addition, every \acro{CTAN} mirror holds a copy of the catalogue,
+presented as a series of web pages; one may scan the files in
+alphabetic order, or use a category-based index. Such access is not
+as ``sophisticated'' as that on the central site, but it served for
+years before the central site appeared.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}The CTAN catalogue (on CTAN)]\CTANref{Catalogue}
+\end{ctanrefs}
+\LastEdit{2014-03-17}
+
+\Question[Q-triptrap]{How can I be sure it's really \TeX{}?}
+
+\TeX{} (and \MF{} and \MP{}) are written in a
+\begin{flatversion} % really "non-hyper"
+ `literate' programming language called \ProgName{Web} (\Qref{}{Q-lit})
+\end{flatversion}
+\begin{hyperversion}
+ \Qref{`literate' programming}{Q-lit} language called \ProgName{Web}
+\end{hyperversion}
+which is designed to be portable across a wide range of computer
+systems. How, then, is a new version of \TeX{} checked?
+
+Of course, any sensible software implementor will have his own suite
+of tests to check that his software runs: those who port \TeX{} and
+its friends to other platforms do indeed perform such tests.
+
+Knuth, however, provides a `conformance test' for both \TeX{}
+(\Package{trip}) and \MF{} (\Package{trap}).
+%%% Is there a similar one for \MP{}?
+He characterises these as `torture tests': they are designed not to
+check the obvious things that ordinary typeset documents, or font
+designs, will exercise, but rather to explore small alleyways off the
+main path through the code of \TeX{}. They are, to the casual reader,
+pretty incomprehensible!
+
+Once an implementation of \TeX{} has passed its \Package{trip} test, or
+an implementation of \MF{} has passed its \Package{trap} test, then it
+may in principle be distributed as a working version. (In practice,
+any distributor would test new versions against ``real'' documents or
+fonts, too; while \Package{trip} and \Package{trap} test bits of
+pathways within the program, they don't actually test for any real
+world problem.)
+\LastEdit{2011-05-28}
+
+% \Question[Q-y2k]{Are \TeX{} and friends Y2K compliant?}
+
+% \begin{description}
+% \item[Crashing:] None of \TeX{}, \MF{} or \MP{} can themselves crash
+% due to any change whatever in the date of any sort.
+
+% \item[Timestamps:] In the original sources, a 2-digit year was
+% stored as the creation time for format files and that value is
+% printed in log-files. These items should not be of general concern,
+% since the only use of the date format file is to produce the log
+% output, and the log file is designed for human readers only.
+
+% Knuth announced in 1998 that implementors would be permitted
+% alter this code without fear of being accused of non-compliance.
+% Nearly all implementations that are being actively maintained had
+% been modified to generate 4-digit years in the format file and the
+% log, by the end of 1998. The original sources themselves have now
+% been modified so that 4-digit year numbers are stored.
+
+% \item[The \csx{year} primitive:] Certification of a \TeX{}
+% implementation (see \Qref[question]{trip/trap testing}{Q-triptrap})
+% does not require that \csx{year} return a meaningful value (which
+% means that \TeX{} can, in principle, be implemented on platforms
+% that don't make the value of the clock available to user programs).
+% The \emph{\TeX{}book} (see
+% \Qref[question]{TeX-related books}{Q-tex-books}) defines \csx{year} as
+% ``the current year of our Lord'', which is the only correct meaning
+% for \csx{year} for those implementations which can supply a
+% meaningful value, which is to say nearly all of them.
+
+% In short, \TeX{} implementations should provide a value in \csx{year}
+% giving the 4-digit year Anno Domini, or the value 1776 if the
+% platform does not support a date function.
+
+% Note that if the system itself fails to deliver a correct date to
+% \TeX{}, then \csx{year} will of course return an incorrect value.
+% \TeX{} cannot be considered Y2K compliant, in this sense, on a
+% system that is not itself Y2K compliant.
+
+% \item[Macros:] \TeX{} macros can in principle perform calculations on
+% the basis of the value of \csx{year}.
+% The \Qref*{LaTeX suite}{Q-latex}
+% performs such calculations in a small number of places; the
+% calculations performed in the current (supported) version of \LaTeX{} are
+% known to be Y2K compliant.
+
+% Other macros and macro packages should be individually checked.
+
+% \item[External software:] Software such as \acro{DVI} translators
+% needs to be individually checked.
+% \end{description}
+% \LastEdit{2011-06-01}
+%
+% withdrawn 2013-05-21
+
+\Question[Q-etex]{What is \eTeX{}?}
+
+While Knuth has declared that \TeX{} will never % !line break
+\Qref*{change in any substantial way}{Q-TeXfuture}, there remain
+things that one might wish had been done differently, or indeed
+implemented at all.
+
+The \acro{NTS} project set out to produce an advanced replacement for
+\TeX{}, to provide a basis for developing such modifications: this
+``New Typesetting System'' would share Knuth's aims, but would
+implement the work in a modern way taking account of the lessons
+learned with \TeX{}. While a first demonstrator \acro{NTS} did
+appear, it wasn't practically useful, and the project seems no longer
+active.
+
+In parallel with its work on \acro{NTS} itself, the project developed
+a set of extensions that can be used with a (``true'') \TeX{} system.
+Such a modified system is known as an \eTeX{} system, and the concept
+has proved widely successful. Indeed, current \TeX{} distributions
+are delivered with most formats built with an \eTeX{}-based system (for
+those who don't want them, \eTeX{}'s extensions can be disabled, leaving
+a functionally standard \TeX{} system).
+
+The extensions range from the seemingly simple (increasing the number
+of available registers from 256 to 32768) through to extremely subtle
+programming support.
+
+\Qref*{\CONTeXT{}}{Q-context} has required \eTeX{} for its operation
+for some time, though development is now focused on the use of
+\Qref*{\luatex{}}{Q-luatex}.
+
+Some \LaTeX{} packages already specify the use of \eTeX{}. Some such
+packages may not work at all on a non-\eTeX{} system; others will
+work, but not as well as on an \eTeX{} system. The % ! line break
+\Qref*{\LaTeX{} team}{Q-LaTeX3} has announced that future \LaTeX{}
+packages (specifically those from the team, as opposed to those
+individually contributed) may require \eTeX{} for optimum performance.
+\begin{ctanrefs}
+\item[\eTeX{}]\CTANref{etex}
+\end{ctanrefs}
+\LastEdit{2011-07-13}
+
+\Question[Q-whatpdftex]{What is \PDFTeX{}?}
+
+One can reasonably say that \PDFTeX{} is (today) the main stream of
+\TeX{} distributions: most \LaTeX{} and many \CONTeXT{} users nowadays use
+\PDFTeX{} whether they know it or not (more precisely, they use
+\PDFTeX{} extended by
+\begin{hyperversion}
+ \Qref*{\eTeX{}}{Q-etex}).
+\end{hyperversion}
+\begin{flatversion}
+ \eTeX{}~--- \Qref{}{Q-etex}).
+\end{flatversion}
+So what is \PDFTeX{}?
+
+\PDFTeX{} is a development of \TeX{} that is capable of generating
+typeset \acro{PDF} output in place of \acro{DVI}. \PDFTeX{} has
+other capabilities, most notably in the area of fine typographic
+detail (for example, its support for % ! line break
+\begin{hyperversion}
+ \Qref{optimising line breaks}{Q-overfull}),
+\end{hyperversion}
+\begin{flatversion}
+ % ( <- dummy for paren balancing
+ optimising line breaks~--- \Qref{}{Q-overfull}),
+\end{flatversion}
+but its greatest impact to date has been in the area of
+\acro{PDF} output.
+
+\PDFTeX{} started as a topic for H\`an \The {} Th\`anh's Master's~thesis,
+and seems first to have been published in \TUGboat{} 18(4), in 1997
+(though it was certainly discussed at the \acro{TUG}'96 conference in
+Russia).
+
+While the world was making good use of ``pre-releases'' of \PDFTeX{},
+Th\`anh used it as a test-bed for the micro-typography which was the
+prime subject of his Ph.D.~research. Since Th\`anh was finally
+awarded his Ph.D., day-to-day maintenance and development of
+\PDFTeX{}~1.0 (and later) has been in the hands of a group of
+\PDFTeX{} maintainers (which includes Th\`anh); the group has managed
+to maintain a stable platform for general use.
+
+Development of \PDFTeX{} has mostly stopped (only bug fixes, and
+occasional small development items are processed): future development
+is focused on \Qref*{\LuaTeX{}}{Q-luatex}.
+\LastEdit{2011-05-28}
+
+\Question[Q-latex]{What is \LaTeX{}?}
+
+\LaTeX{} is a \TeX{} macro package, originally written by Leslie Lamport, that
+provides a document processing system. \LaTeX{} allows markup to
+describe the structure of a document, so that the user
+need not think about presentation. By using document classes and
+add-on packages, the same document can be produced in a variety of
+different layouts.
+
+Lamport says that \LaTeX{}
+``\emph{represents a balance between functionality and ease of use}''.
+This shows itself as a continual conflict that leads to
+the need for such things as \acro{FAQ}s: \LaTeX{} \emph{can}
+meet most user requirements, but finding out \emph{how} is often
+tricky.
+
+\Question[Q-latex2e]{What is \LaTeXe{}?}
+
+Lamport's last version of \LaTeX{} (\LaTeXo{}, last updated in 1992)
+was superseded in 1994 by a new version (\LaTeXe{}) provided by
+\Qref*{the \LaTeX{} team}{Q-LaTeX3}.
+\LaTeXe{} is now the only readily-available version of
+\LaTeX{}, and draws together several threads of \LaTeX{} development
+from the later days of \LaTeXo{}. The ``e'' of the name is (in the
+% next (ghastly) line needed to maintain typesetting
+\wideonly{\Qref{official logo}{Q-logos}}\narrowonly{official logo~--- \Qref{\relax}{Q-logos}})
+% the \relax allows sanitize to cope with the line. just don't ask...
+a single-stroke epsilon
+(\latexhtml{\ensuremath{\varepsilon}}{&epsilon;}, supposedly
+indicative of no more than a small change).
+
+\LaTeXe{} has several enhancements over \LaTeXo{}, but they were all
+rather minor, with a view to continuity and stability rather than the
+``big push'' that some had expected from the team. \LaTeXe{}
+continues to this day to offer a compatibility mode in which most
+files prepared for use with \LaTeXo{} will run (albeit with somewhat
+reduced performance, and subject to voluminous complaints in the log
+file). Differences between \LaTeXe{} and \LaTeXo{} are
+outlined in a series of `guide' files that are available in every
+\LaTeX{} distribution (the same directory also contains ``news'' about
+each new release of \LaTeXe{}).
+
+Note that, now, \latexe{} is ``feature frozen'' (the only allowed
+changes come from bug reports); this, too, is in pursuit of stability,
+and is a driving force for many of the efforts to contribute \latex{}
+packages.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeX{} guides and news]\CTANref{latexdoc}
+\end{ctanrefs}
+\LastEdit{2011-08-19}
+
+\Question[Q-latexpronounce]{How should I pronounce ``\LaTeX{}(\twee{})''?}
+
+Lamport never recommended how one should pronounce \LaTeX{}, but a lot
+of people pronounce it `Lay \TeX{}' or perhaps `Lah \TeX{}' (with
+\TeX{} pronounced as the program itself; see
+\Qref[question]{the rules for TeX}{Q-TeXpronounce}). It is definitely
+\emph{not} to be pronounced in the same way as the rubber-tree gum
+(which would be `lay teks').
+
+The \LaTeXe{} logo is supposed to end with an
+\latexhtml{\ensuremath{\varepsilon}}{&epsilon;}; nevertheless, most
+people pronounce the name as `\LaTeX{}-two-ee'.
+\LastEdit{2009-06-08}
+
+\Question[Q-plainvltx]{Should I use \plaintex{} or \LaTeX{}?}
+
+There's no straightforward answer to this question. Many people swear
+by \plaintex{}, and produce highly respectable documents using it
+(Knuth is an example of this, of course). But equally, many people
+are happy to let someone else take the design decisions for them,
+accepting a small loss of flexibility in exchange for a saving of
+(mental) effort.
+
+The arguments around this topic can provoke huge amounts of noise and
+heat, without offering much by way of light; your best bet may be to
+find out what those around you are using, and to follow them in the
+hope of some support. Later on, you can always switch your
+allegiance; don't bother about it.
+
+If you are preparing a manuscript for a publisher or journal, ask them
+what markup they want before you
+develop your own; many big publishers have developed their own
+\AllTeX{} styles for journals and books, and insist that authors stick
+closely to their markup.
+
+\Question[Q-LaTeXandPlain]{How does \LaTeX{} relate to \plaintex{}?}
+
+\tex{} provides a programming language (of sorts), and any document
+more complex than the trivial ``hello world'' will need some
+programming.
+
+\LaTeX{} and \plaintex{} are both libraries written for use with
+\tex{}; the user commands \ProgName{tex} and \ProgName{latex} invoke
+\tex{}-the-program with a library incorporated. Libraries that may be
+loaded in this way are known as `\emph{formats}'; when a user ``runs''
+\plaintex{} or \latex{}, they are running \tex{} (the program) with an
+appropriate format. The documents are then programmed in \plaintex{}
+or \latex{} \emph{language}.
+
+\plaintex{} and \latex{} exist because writing your documents in `raw'
+\TeX{} could involve much reinventing of wheels for every document.
+Both languages serve as convenient aids to make document writing more
+pleasant: \LaTeX{} provides many more items to support `common'
+requirements of documents.
+
+As such, \LaTeX{} is close to being a superset of \plaintex{}, but
+some \plaintex{} commands don't work as expected when used in a
+\latex{} document. Using \plaintex{} commands in a \latex{} document
+is an occasional source of bugs: the output is \emph{almost} right,
+but some things are misplaced.
+
+So, \plaintex{} and \latex{} are related through a common parent, and
+are designed for use in similar jobs; programming for one will often
+not work correctly in the other.
+\LastEdit{2014-03-18}
+
+\Question[Q-context]{What is \context{}?}
+
+\href{http://www.pragma-ade.com/}{\context{}} is a macro package
+created by Hans Hagen of Pragma-Ade; it started as a production tool
+for Pragma (which is a publishing company). \CONTeXT{} is a
+document-production system based, like \LaTeX{}, on the \TeX{}
+typesetting system. Whereas \LaTeX{} insulates the writer from
+typographical details, \context{} takes a complementary approach by
+providing structured interfaces for handling typography, including
+extensive support for colors, backgrounds, hyperlinks, presentations,
+figure-text integration, and conditional compilation. It gives the
+user extensive control over formatting while making it easy to create
+new layouts and styles without learning the \TeX{} macro
+language. \CONTeXT{}'s unified design avoids the package clashes that
+can happen with \LaTeX{}.
+
+\context{} also integrates MetaFun, a superset of \MP{} and a powerful
+system for vector graphics. MetaFun can be used as a stand-alone
+system to produce figures, but its strength lies in enhancing
+\context{} documents with accurate graphic elements.
+
+\context{} allows users to specify formatting commands in English,
+Dutch, German, French, or Italian, and to use different typesetting
+engines (\PDFTeX{}, Xe\TeX{}, Aleph and \LuaTeX{}) without
+changing the user interface. \context{} continues to develop, often in
+response to requests from the user community.
+
+The development of \Qref*{\luatex{}}{Q-luatex} was originally driven
+by \context{}, almost from the start of its project. Nowadays,
+\context{} it is distributed in two versions~--- mark two (files with
+extension \extension{mkii}) which runs on \pdftex{} but is not under
+active development, and mark four (files with extension
+\extension{mkiv}) (which runs on \luatex{} and is where development
+happens).
+
+\context{} has a large developer community (though possibly not as
+large as that of latex{}), but those developers who are active seem to have
+prodigious energy. Support is available via a % ! line break
+\href{http://wiki.contextgarden.net/Main_Page}{\acro{WIKI} site} and via the
+\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}.
+A ``standalone'' distribution (a \TeX{} distribution with no macros
+other than \context{}-based ones) is available from
+\url{http://minimals.contextgarden.net/} --- it provides
+a \context{} system on any of a number of platforms, executing either
+mark~ii or mark~iv \context{}.
+
+Note that \acro{CTAN} does \emph{not} hold the primary distribution of
+\context{}~--- potential users should refer to
+\href{http://contextgarden.net}{\context{} `garden' site} for details
+of the
+current distribution. \acro{CTAN} holds a copy of \CONTeXT{} but
+makes no claim about its ``up-to-date''ness. Likewise, \acro{CTAN}
+holds a few contributed \context{} packages, but many more are to be
+found via the \href{http://contextgarden.net}{\CONTeXT{} garden}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context}
+\item[\nothtml{\rmfamily}\CONTeXT{} packages selection]\CTANref{context-contrib}
+\end{ctanrefs}
+\LastEdit{2014-05-30}
+
+\Question[Q-AMSpkg]{What are the \acro{AMS} packages (\AMSTeX{}, \emph{etc}.)?}
+
+\AMSTeX{} is a \TeX{} macro package, originally written by Michael Spivak for
+the American Mathematical Society (\acro{AMS}) during 1983--1985 and
+is described in the book ``\Qref*{The Joy of \TeX{}}{Q-tex-books}''.
+It is based on \plaintex{}, and provides many
+features for producing more professional-looking maths formulas with
+less burden on authors. It pays attention to the finer details of
+sizing and positioning that mathematical publishers care about. The
+aspects covered include multi-line displayed equations, equation
+numbering, ellipsis dots, matrices, double accents, multi-line
+subscripts, syntax checking (faster processing on initial
+error-checking \TeX{} runs), and other things.
+
+As \LaTeX{} increased in popularity, authors sought to submit papers to
+the \acro{AMS} in \LaTeX{}, so \AMSLaTeX{} was developed. \AMSLaTeX{}
+is a collection of \LaTeX{} packages and classes that offer authors most of
+the functionality of \AMSTeX{}.
+The \acro{AMS} no longer recommends the use of \AMSTeX{}, and urges
+its authors to use \AMSLaTeX{} instead.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\AMSTeX{} distribution]\CTANref{amstex}
+\item[\nothtml{\rmfamily}\AMSLaTeX{} distribution]\CTANref{amslatex}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-eplain]{What is \Eplain{}?}
+
+The \href{http://tug.org/eplain}{\Eplain{}}
+macro package expands on and extends the definitions in \plaintex{}.
+\Eplain{} is not intended to provide ``generic typesetting
+capabilities'', as do \CONTeXT{}, \LaTeX{} or
+\Qref*{Texinfo}{Q-texinfo}. Instead, it defines macro tools that
+should be useful whatever commands you choose to use when you prepare
+your manuscript.
+
+For example, \Eplain{} does not have a command \csx{section},
+which would format section headings in an ``appropriate'' way, as
+\LaTeX{}'s \csx{section} does. The philosophy of \Eplain{} is that
+some people will always need or want to go beyond the macro designer's
+idea of ``appropriate''. Canned sets of macros are fine~--- as long as you
+are willing to accept the resulting output. If you don't like the
+results, or if you are trying to match a different format, you may
+find that \Eplain{} is for you.
+
+On the other hand, almost everyone would like capabilities such as
+cross-referencing by labels, so that you don't have to put actual page
+numbers in the manuscript. The authors of \Eplain{} believe it is the
+only generally available macro package that does not force its
+typographic style on an author, and yet provides these capabilities.
+
+Another useful feature of \Eplain{} is the ability to create PDF files
+with hyperlinks. The cross-referencing macros can implicitly generate
+hyperlinks for the cross-references, but you can also create explicit
+hyperlinks, both internal (pointing to a destination within the
+current document) and external (pointing to another local document or
+a URL).
+
+Several \LaTeX{} packages provide capabilities which \plaintex{}
+users are lacking, most notably text colouring and rotation provided by
+the \Package{graphics} bundle (packages \Package{color} and
+\Package{graphics}). Although the \Package{graphics} bundle provides
+a \plaintex{} ``loader'' for some of the packages, it is not a
+trivial job to pass options to those packages under \plaintex{}, and
+much of the functionality of the packages is accessed through package
+options. \Eplain{} extends the loader so that options can be passed
+to the packages just as they are in \LaTeX{}. The following packages are
+known to work with \Eplain{}: \Package{graphics}, \Package{graphicx},
+\Package{color}, \Package{autopict} (\LaTeX{} picture environment),
+\Package{psfrag}, and \Package{url}.
+
+\href{http://tug.org/docs/html/eplain}{\Eplain{} documentation} is
+available online (there's a \acro{PDF} copy in the \acro{CTAN}
+package as well), and there's also a mailing list~--- sign up, or
+browse the list archives, via
+\URL{http://tug.org/mailman/listinfo/tex-eplain}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\Eplain{} distribution]\CTANref{eplain}
+\end{ctanrefs}
+\LastEdit{2013-06-25}
+
+\Question[Q-texinfo]{What is Texinfo?}
+
+Texinfo is a documentation system that uses one source file to produce
+both on-line information and printed output. So instead of writing
+two different documents, one for the on-line help and the other for a
+typeset manual, you need write only one document source file. When
+the work is revised, you need only revise one document. By
+convention, Texinfo source file names end with a \extension{texi} or
+\extension{texinfo} extension.
+
+Texinfo is a macro language, somewhat similar to \LaTeX{}, but with
+slightly less expressive power. Its appearance is of course rather
+similar to any \TeX{}-based macro language, except that its macros
+start with \texttt{@} rather than the |\| that's more commonly used in
+\TeX{} systems.
+
+You can write and format Texinfo files into Info files within \acro{GNU}
+\ProgName{emacs}, and read them using the \ProgName{emacs} Info
+reader. You can also format Texinfo files into Info files using
+\ProgName{makeinfo} and read them using \ProgName{info}, so you're not
+dependent on \ProgName{emacs}. The distribution includes a
+\ProgName{Perl} script, \ProgName{texi2html}, that will convert
+Texinfo sources into \acro{HTML}: the language is a far better fit to
+\acro{HTML} than is \LaTeX{}, so that the breast-beating agonies of
+\Qref*{converting \LaTeX{} to \acro{HTML}}{Q-LaTeX2HTML} are largely
+avoided.
+
+Finally, of course, you can also print the files, or convert them to
+\acro{PDF} using \PDFTeX{}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Texinfo distribution]\CTANref{texinfo}
+\end{ctanrefs}
+
+\Question[Q-lollipop]{Lollipop}
+
+A long time ago (in the early 1990s), the Lollipop \tex{} format was
+developed (originally to typeset the excellent book % !line break
+\Qref{\tex{} by topic}{Q-tex-books}). Several people admired the
+format, but no ``critical mass'' of users appeared, that could have
+prompted maintenance of the format.
+
+More than 20 years later, a new maintainer appeared: he hopes to build
+Lollipop into an engine for rapid document style development. (In
+addition, he intends to add support for right-to-left languages such
+as his own~--- Persian.)
+
+We can only hope that, this time, Lollipop will ``catch on''!
+\begin{ctanrefs}
+\item[lollipop]\CTANref{lollipop}
+\end{ctanrefs}
+
+\Question[Q-whyfree]{If \TeX{} is so good, how come it's free?}
+
+It's free because Knuth chose to make it so (he makes money from
+royalties on his \TeX{} books, which still sell well). He is
+nevertheless apparently happy that others should earn money by selling
+\TeX{}-based services and products. While several valuable
+\TeX{}-related tools and packages are offered subject to restrictions
+imposed by the \acro{GNU} General Public Licence (\acro{GPL},
+sometimes referred to as `Copyleft'), which denies the right to
+commercial exploitation. \TeX{} itself is offered under a pretty
+permissive licence of Knuth's own.
+
+There are commercial versions of \TeX{} available; for some users,
+it's reassuring to have paid support. What is more, some of the
+commercial implementations
+have features that are not available in free versions. (The
+reverse is also true: some free implementations have features
+not available commercially.)
+
+This \acro{FAQ} concentrates on `free' distributions of \TeX{}, but we
+do at least list the \Qref*{major vendors}{Q-commercial}.
+\LastEdit{2013-06-25}
+
+\Question[Q-TeXfuture]{What is the future of \TeX{}?}
+
+Knuth has declared that he will do no further development of \TeX{};
+he will continue to fix any bugs that are reported to him (though
+bugs are rare). This decision was made soon after
+\TeX{} version~3.0 was released; at each bug-fix release
+the version number acquires one more digit, so that it tends to the
+limit~\ensuremath{\pi} (at the time of writing, Knuth's latest release
+is version 3.1415926). Knuth wants \TeX{} to be frozen at
+version~\ensuremath{\pi} when he dies; thereafter, no further changes
+may be made to Knuth's source. (A similar rule is applied to \MF{};
+its version number tends to the limit~\emph{e}, and currently
+stands at 2.718281.)
+
+Knuth explains his decision, and exhorts us all to respect it, in a
+paper originally published in % ! line break
+\href{http://tug.org/TUGboat/Articles/tb11-4/tb30knut.pdf}{\TUGboat{} 11(4)},
+and reprinted in the % ! line break
+\href{http://www.ntg.nl/maps/pdf/5_34.pdf}{NTG journal MAPS}.
+
+There are projects (some of them long-term
+projects: see, for example,
+\Qref[question]{the LaTeX3 project}{Q-LaTeX3})
+%\Qref[and]{and the SGML work}{Q-SGML})
+to build substantial new macro packages based on \TeX{}. There are
+also various projects to build a \emph{successor} to \TeX{}. The
+\Qref*{\eTeX{}}{Q-etex} extension to \TeX{} itself arose from such a
+project (\acro{NTS}). Another pair of projects, which have delivered
+all the results they are likely to deliver, is the
+related % ! line break
+\Qref*{Omega and Aleph}{Q-omegaleph}. The % ! line break
+\Qref*{\xetex{} system}{Q-xetex} is in principle still under
+development, but is widely used, and the % ! line break
+\Qref*{\LuaTeX{} project}{Q-luatex} (though not scheduled to produce
+for some time) has already delivered a system that increasingly
+accessible to ``ordinary users''.
+\LastEdit{2013-05-21}
+
+\Question[Q-readtex]{Reading \AllTeX{} files}
+
+So you've been sent an \AllTeX{} file: what are you going to do with
+it?
+
+You can, of course, ``just read it'', since it's a plain text file;
+the problem is that the markup tags in the document may prove
+distracting. Most of the time, even \TeX{} \emph{experts} will
+typeset a \AllTeX{} file before attempting to read it\nobreakspace{}\dots{}
+
+So you shouldn't be too concerned if you can't make head nor tail of
+the file: it is designed to be read by a (sort of) compiler, and
+compilers don't have much in common with human readers.
+
+A possible next step is to try an on-line \latex{} editor. There are
+many of these~--- a compilation of links may be found in % line break
+\href{http://texblog.net/latex-link-archive/online-compiler/}{this blog post}
+
+Of that long list, the present author has only dabbled with
+\href{https://www.writelatex.com/}{Write\latex{}}; it seems well
+suited to simple `one-shot' use in this way.
+
+If no online compiler helps, you need to typeset the document
+``yourself''. The good news is that \TeX{} systems are available,
+free, for most sorts of computer; the bad news is that you need a
+pretty complete \TeX{} system even to read a single file, and complete
+\TeX{} systems are pretty large.
+
+\TeX{} is a typesetting system that arose from a publishing project (see
+\wideonly{``}\Qref[question]{what is \TeX{}}{Q-whatTeX}\wideonly{''}),
+and its basic source is available free from its author. However, at
+its root, it is \emph{just} a typesetting engine: even to view or to
+print the typeset output, you will need ancillary programs. In short,
+you need a \TeX{} \emph{distribution}~--- a collection of
+\TeX{}-related programs tailored to your operating system: for details
+of the sorts of things that are available, see
+% beware line break
+\htmlonly{``}\Qref[question]{\TeX{} distributions}{Q-TeXsystems}\htmlonly{''}
+or
+% beware line break
+\htmlonly{``}\Qref[\htmlonly]{commercial \TeX{} distributions}{Q-commercial}\latexhtml{ (for commercial distributions)}{''}.
+
+But beware~--- \TeX{} makes no attempt to look like the sort of
+\WYSIWYG{} system you're probably used to (see
+% beware line wrap
+\wideonly{``}\Qref[question]{why is \TeX{} not \WYSIWYG{}}{Q-notWYSIWYG}\wideonly{''}):
+while many modern versions of \TeX{} have a compile--view cycle that
+rivals the best commercial word processors in its responsiveness, what
+you type is usually \emph{markup}, which typically defines a logical
+(rather than a visual) view of what you want typeset.
+
+So there's a balance between the simplicity of the original
+(marked-up) document, which can more-or-less be read in \emph{any}
+editor, and the really rather large investment needed to install a
+system to read a document ``as intended''.
+
+Are you ``put off'' by all this?~--- remember that \tex{} is good at
+producing \acro{PDF}: why not ask the person who sent the \tex{} file
+to send an \acro{PDF} copy?
+\LastEdit{2014-05-21}
+
+\Question[Q-notWYSIWYG]{Why is \TeX{} not a \WYSIWYG{} system?}
+
+\WYSIWYG{} is a marketing term (``What you see is what you get'') for
+a particular style of text processor. \WYSIWYG{} systems are
+characterised by two principal claims: that you type what you want to
+print, and that what you see on the screen as you type is a close
+approximation to how your text will finally be printed.
+
+The simple answer to the question is, of course, that \TeX{} was
+conceived long before the marketing term, at a time when the marketing
+imperative wasn't perceived as significant. (In fact, it appears that
+the first experimental \WYSIWYG{} systems were running in commercial
+labs, near where Knuth was working on \tex{}. At the time, of course,
+\tex{} was only available on a mainframe, and getting it to run on the
+small experimental machines would have distracted Knuth from his
+mission to create a typesetting system that he could use when
+preparing his books for publication.)
+
+However, all that was a long time ago: why has nothing been done with
+the ``wonder text processor'' to make it fit with modern perceptions?
+
+There are two answers to this. First, the simple ``things \emph{have}
+been done'' (but they've not taken over the \TeX{} world); and second,
+``there are philosophical reasons why the way \TeX{} has developed is
+ill-suited to the \WYSIWYG{} style''.
+
+Indeed, there is a fundamental problem with applying \WYSIWYG{}
+techniques to \TeX{}: the complexity of \TeX{} makes it hard to get
+the equivalent of \TeX{}'s output without actually running \TeX{} over
+the whole of the document being prepared.
+
+A celebrated early system offering ``\WYSIWYG{} using \TeX{}'' came
+from the Vor\TeX{} project: a pair of Sun workstations worked in
+tandem, one handling the user interface while the other beavered away
+in the background typesetting the result. Vor\TeX{} was quite
+impressive for its time, but the two workstations combined had hugely
+less power than the average sub-thousand-dollar Personal Computer
+nowadays, and its code has not proved portable (it never even made the
+last `great' \TeX{} version change, at the turn of the 1990s, to
+\TeX{} version 3).
+
+Lightning Textures (an extension of Blue Sky's original \TeX{} system
+for the Macintosh), is sadly no longer available.
+
+Thus``\Qref*{Scientific Word}{Q-commercial}'' (which can also interact
+with a computer algebra system), is the only remaining \tex{} system
+that even approximates to \WYSIWYG{} operation.
+
+The issue has of recent years started to attract attention
+from \TeX{} developers, and several interesting projects that address
+the ``\Qref*{\TeX{} document preparation environment}{Q-WYGexpts}''
+are in progress.
+
+All the same, it's clear that the \TeX{} world has taken a long time
+to latch onto the idea of \WYSIWYG{}.
+Apart from simple arrogance (``we're better, and have no need to
+consider the petty doings of the commercial word processor market''),
+there is a real conceptual difference between the word processor model
+of the world and the model \LaTeX{} and \CONTeXT{} employ~--- the idea of
+``markup''. ``Pure'' markup expresses a logical model of a document,
+where every object within the document is labelled according to what
+it is rather than how it should appear: appearance is deduced from the
+properties of the type of object. Properly applied, markup can
+provide valuable assistance when it comes to re-use of documents.
+
+Established \WYSIWYG{} systems find the expression of this sort of
+structured markup difficult; however, markup \emph{is} starting to
+appear in the lists of the commercial world's requirements, for two
+reasons. First, an element of markup helps impose style on a
+document, and commercial users are increasingly obsessed with
+uniformity of style; and second, the increasingly pervasive use of
+\acro{XML}-derived document archival formats demands it. The same
+challenges must needs be addressed by \TeX{}-based document
+preparation support schemes, so we are
+observing a degree of confluence of the needs of the two communities:
+interesting times may be ahead of us.
+\LastEdit{2013-06-03}
+
+\Question[Q-TUG*]{\TeX{} User Groups}
+
+There has been a \TeX{} User Group since very near the time \TeX{}
+first appeared. That first group, \acro{TUG}, is still active and its
+journal \textsl{TUGboat} continues in regular publication
+with articles about \TeX{}, \MF{} and related technologies, and about
+document design, processing and production. \acro{TUG} holds a yearly
+conference, whose proceedings are published in \textsl{TUGboat}.
+
+\acro{TUG}'s \href{http://www.tug.org}{web site} is a valuable
+resource for all sorts of
+\TeX{}-related matters, such as details of \TeX{} software, and lists
+of \TeX{} vendors and \TeX{} consultants. Back articles from
+\textsl{TUGboat} are also available.
+
+Some time ago, \acro{TUG} established a ``technical council'', whose
+task was to oversee the development of \TeX{}nical projects. Most
+such projects nowadays go on their way without any support from
+\acro{TUG}, but \acro{TUG}'s web site lists its
+
+\begin{hyperversion}
+\href{http://www.tug.org/twg.html}{Technical Working Groups (\acro{TWG}s)}.
+\end{hyperversion}
+\begin{flatversion}
+Technical Working Groups (\acro{TWG}s: see
+\URL{http://www.tug.org/twg.html}).
+\end{flatversion}
+
+\acro{TUG} has a reasonable claim to be considered a world-wide
+organisation, but there are many national and regional user groups,
+too; \acro{TUG}'s web site maintains a list of
+\begin{hyperversion}
+href{http://www.tug.org/lugs.html}{``Local User Groups'' (\acro{LUG}s)}.
+\end{hyperversion}
+\begin{flatversion}
+``local user groups'' (\acro{LUG}s: see
+\URL{http://www.tug.org/lugs.html}).
+\end{flatversion}
+
+Contact \acro{TUG} itself via \URL{http://tug.org/contact}
+LastEdit{2013-06-25}
diff --git a/help/uk-tex-faq/faq-biblio.tex b/help/uk-tex-faq/faq-biblio.tex
new file mode 100644
index 0000000000..36419bb1bf
--- /dev/null
+++ b/help/uk-tex-faq/faq-biblio.tex
@@ -0,0 +1,1468 @@
+% $Id: faq-biblio.tex,v 1.15 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Bibliographies and citations}
+
+\subsection{Creating bibliographies}
+
+\Question[Q-buildbib]{Creating a \BibTeX{} bibliography file}
+
+A \BibTeX{} bibliography file may reasonably be compared to a small
+database, the entries in which are references to literature that may
+be called up by citations in a document.
+
+Each entry in the bibliography has a \emph{type} and a unique
+\emph{key}. The bibliography is read, by \BibTeX{}, using the details
+specified in a \emph{bibliography style}. From the style, \BibTeX{}
+finds what entry types are permissible, what \emph{fields} each entry
+type has, and how to format the whole entry.
+
+The type specifies the type of document you're making reference to; it
+may run all the way from things like ``\environment{Book}'' and
+``\environment{Proceedings}'' (which may even contain other citations
+of type ``\environment{InBook}'' or ``\environment{InProceedings}'')
+through dissertation styles like ``\environment{PhdThesis}'' to
+otherwise-uncategorisable things such as ``\environment{Misc}''. The
+unique key is something you choose yourself: it's what you use when
+you want to \Qref*{cite an entry in the file}{Q-usebibtex}. People
+commonly create a key that combines the (primary) author's name and
+the year of publication, possibly with a marker to distinguish
+publications in the same year. So, for example, the Dyson, Eddington,
+Davidson paper about deflection of starlight appears in my
+experimental \extension{bib} file as \texttt{Dyson20.1}.
+
+So, noting the rules of the style, you have `simply' to write a
+bibliography database. Fortunately, there are several tools to help
+in this endeavour:
+\begin{itemize}
+\item Most of the better \Qref*{\AllTeX{}-oriented editors}{Q-editors}
+ have ``\BibTeX{} modes''.
+\item If you have an existing \environment{thebibliography}
+ environment, the \ProgName{Perl} script \ProgName{tex2bib} will
+ probably help.
+\item There are a number of \BibTeX{} bibliography management systems
+ available, some of which permit a graphical user interface to the
+ task. Sadly, none seems to be available with the ordinary \TeX{}
+ distributions.
+
+ Tools such as \ProgName{Xbibfile} (a graphical user interface),
+ \ProgName{ebib} (a database application written to run `inside'
+ \ProgName{emacs}) and
+ \ProgName{btOOL} (a set of \ProgName{perl} tools for building
+ \BibTeX{} database handlers) are available from \acro{CTAN}.
+
+ Other systems, such as
+ \href{http://refdb.sourceforge.net/}{\ProgName{RefDB}},
+ \href{http://www.nongnu.org/biborb}{BibORB},
+ \href{http://bibdesk.sourceforge.net/}{\ProgName{BibDesk}},
+ \href{http://pybliographer.org}{\ProgName{pybliographer}} and the
+ \ProgName{Java}-based
+ \href{http://freshmeat.net/projects/bibkeeper/}{\ProgName{Bibkeeper}}
+ and \href{http://jabref.sourceforge.net}{\ProgName{JabRef}} (which
+ claims to supersede \ProgName{Bibkeeper})
+ are only available from their development sites.
+% review of web database offerings in textex_368
+\item Some commercial citation-management systems will export in
+ \BibTeX{} format; an example is
+ \href{http://www.endnote.com/}{EndNote}.
+\item Data from on-line citation databases may often be translated to
+ \BibTeX{} format by utilities to be found on \acro{CTAN}. For
+ example, the \ProgName{Perl} script \ProgName{isi2bibtex} will
+ translate citations from \acro{ISI} ``Web of knowledge'' (a
+ subscription service, available to \acro{UK} academics via
+ \acro{BIDS}). UK academics may translate \acro{BIDS} downloads
+ using \ProgName{bids.to.bibtex}
+\item \href{http://scholar.google.com}{Google Scholar} provides an
+ ``Import into \BibTeX{}'' tab for each reference it finds for you:
+ that tab gives you a page containing a \BibTeX{} entry for the
+ reference.
+\end{itemize}
+\begin{ctanrefs}
+\item[bids.to.bibtex]\CTANref{bidstobibtex}
+\item[btOOL]\CTANref{btOOL}
+\item[ebib]\CTANref{ebib}
+\item[isi2bibtex]\CTANref{isi2bibtex}
+\item[tex2bib]\CTANref{tex2bib}
+\item[tex2bib.readme]\CTANref{tex2bib-doc}
+\item[xbibfile]\CTANref{xbibfile}
+\end{ctanrefs}
+
+\Question[Q-custbib]{Creating a bibliography style}
+
+It \emph{is} possible to write your own: the standard bibliography
+styles are distributed in a form with many comments, and there is a description
+of the language in the \bibtex{} distribution (see % ! line wrap
+\Qref[question]{BibTeX documentation}{Q-BibTeXing}).
+However, it must be admitted that the language in which \BibTeX{}
+styles are written is pretty obscure, and one would not recommend
+anyone who's not a confident programmer to write their own, though
+minor changes to an existing style may be within the grasp of many.
+
+If your style isn't too `far out', you can probably avoid programming
+it by using the facilities of the \Package{custom-bib} bundle. The bundle
+contains a file \File{makebst.tex}, which runs you through a text menu
+to produce a file of instructions, which you can then use to generate your
+own \extension{bst} file. This technique doesn't offer entirely new styles
+of document, but the \Package{custom-bib}'s ``master \BibTeX{}
+styles'' already offer significantly more than the \BibTeX{} standard set.
+
+An alternative, which is increasingly often recommended, to use
+\Qref*{\Package{biblatex}}{Q-biblatex}. \Package{Biblatex} offers
+many hooks for adjusting the format of the output of your `basic'
+\bibtex{} style, and a collection of `contributed' styles have also
+started to appear. Note.bowever There are not as many of
+\Package{biblatex}'s contributed styles as there are for \bibtex{},
+and there is no \Package{custom-biblatex}, both of which suggest that
+beginners' r\"ole models are hard to come by. As a result, beginners
+should probably resist the temptation to write their own contributed
+\package{biblatex} style.
+\begin{ctanrefs}
+\item[biblatex.sty]\CTANref{biblatex}
+\item[biblatex \nothtml{\normalfont}contributed styles]\CTANref{biblatex-contrib}
+\item[\nothtml{\normalfont}\BibTeX{} documentation]\CTANref{bibtex}
+\item[makebst.tex]Distributed with \CTANref{custom-bib}
+\end{ctanrefs}
+
+\Question[Q-capbibtex]{Capitalisation in \BibTeX{}}
+
+The standard \BibTeX{} bibliography styles impose fixed ideas about
+the capitalisation of titles of things in the bibliography. While
+this is not unreasonable by \BibTeX{}'s lights (the rules come from
+the \emph{Chicago Manual of Style}) it can be troublesome, since
+\BibTeX{} fails to recognise special uses (such as acronyms, chemical
+formulae, etc.).
+
+The solution is to enclose the letter or letters, whose capitalisation
+\BibTeX{} should not touch, in braces, as:
+\begin{quote}
+\begin{verbatim}
+title = {The {THE} operating system},
+\end{verbatim}
+\end{quote}
+Sometimes you find \BibTeX{} changing the case of a single letter
+inappropriately. No matter: the technique can be applied to single
+letters, as in:
+\begin{quote}
+\begin{verbatim}
+title = {Te{X}niques and tips},
+\end{verbatim}
+\end{quote}
+If your document design specification requires a different style of
+capitalisation, you should acquire a bibliography style that doesn't
+enforce \BibTeX{}'s default rules. It is definitely \emph{not} a good
+idea to enclose an entire title in braces, as in
+\begin{quote}
+\begin{verbatim}
+title = {{TeXniques and tips}},
+\end{verbatim}
+\end{quote}
+though that does ensure that the capitalisation is not changed. Your
+\BibTeX{} database should be a general-purpose thing, not something
+tuned to the requirements of a particular document or bibliography
+style, or to the way you are thinking today~--- for example, on a
+future occasion, you might find yourself using a different \BibTeX{}
+style with different capitalisation rules.
+
+There's more on the subject in the
+% beware line wrap
+\Qref*{\BibTeX{} documentation}{Q-BibTeXing}.
+
+\Question[Q-bibaccent]{Accents in bibliographies}
+
+\BibTeX{} not only has a tendency (by default) to mess about with the
+% line wrap
+\Qref*{case of letters in your bibliography}{Q-capbibtex},
+also makes a hash of accent commands:
+``\texttt{ma}\csx{\textasciitilde}\texttt{nana}'' comes out as ``ma
+nana'' (!). The solution is similar that of the letter case problem:
+enclose the troublesome sequence in braces, as
+``\texttt{\{}\csx{\textasciitilde}\texttt{n\}}'', in this example.
+
+\Question[Q-bibstrtl]{`String too long' in \BibTeX{}}
+
+The \BibTeX{} diagnostic ``Warning--you've exceeded 1000, the
+\texttt{global-string-size}, for entry \texttt{foo}'' usually arises
+from a very large abstract or annotation included in the database.
+The diagnostic usually arises because of an infelicity in the coding of
+\File{abstract.bst}, or styles derived from it. (One doesn't
+ordinarily output annotations in other styles.)
+
+The solution is to make a copy of the style file (or get a clean copy
+from \acro{CTAN}~--- \CTANref{abstract-bst}), and rename it (e.g., on a
+long file-name system, to \File{abstract-long.bst}). Now edit it: find
+function \texttt{output.nonnull} and
+\begin{itemize}
+\item change its first line (line 60 in the version on \acro{CTAN})
+ from
+\begin{quote}
+\begin{verbatim}
+{ 's :=
+\end{verbatim}
+\end{quote}
+to
+\begin{quote}
+\begin{verbatim}
+{ swap$
+\end{verbatim}
+\end{quote}
+Finally,
+\item delete the function's last line, which just says ``\texttt{s}
+ (line 84 in the version on \acro{CTAN}).
+\end{itemize}
+Finally, change your \csx{bibliographystyle} command to refer to the
+name of the new file.
+
+This technique applies equally to any bibliography style: the same
+change can be made to any similar \texttt{output.nonnull} function.
+
+If you're reluctant to make this sort of change, the only way forward
+is to take the entry out of the database, so that you don't encounter
+\BibTeX{}'s limit, but you may need to retain the entry because it
+will be included in the typeset document. In such cases, put the body
+of the entry in a separate file:
+\begin{quote}
+\begin{verbatim}
+@article{long.boring,
+ author = "Fred Verbose",
+ ...
+ abstract = "{\input{abstracts/long.tex}}"
+}
+\end{verbatim}
+\end{quote}
+In this way, you arrange that all \BibTeX{} has to deal with is the
+file name, though it will tell \TeX{} (when appropriate) to include
+all the long text.
+
+\Question[Q-manyauthor]{\BibTeX{} doesn't understand lists of names}
+
+\BibTeX{} has a strict syntax for lists of authors' (or editors')
+names in the \BibTeX{} data file; if you write the list of names in a
+``natural''-seeming way, the chances are you will confuse \BibTeX{},
+and the output produced will be quite different from what you had
+hoped.
+
+Names should be expressed in one of the forms
+\begin{quote}
+\begin{verbatim}
+First Last
+Last, First
+Last, Suffix, First
+\end{verbatim}
+\end{quote}
+and lists of names should be separated with ``\texttt{and}''.
+For example:
+\begin{quote}
+\begin{verbatim}
+AUTHOR = {Fred Q. Bloggs, John P. Doe \&
+ Another Idiot}
+\end{verbatim}
+\end{quote}
+falls foul of two of the above rules: a syntactically significant
+comma appears in an incorrect place, and `\csx{\&}' is being used as a
+name separator. The output of the above might be something like:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+John P. Doe \& Another Idiot Fred Q. Bloggs
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+John P. Doe \& Another Idiot
+ Fred Q. Bloggs
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+because ``John P. Doe \& Another Idiot has become the `first name',
+while ``Fred Q. Bloggs'' has become the `last name' of a single
+person. The example should have been written:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+AUTHOR = {Fred Q. Bloggs and
+ John P. Doe and
+ Another Idiot}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+AUTHOR = {Fred Q. Bloggs and John P. Doe and
+ Another Idiot}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+Some bibliography styles implement clever acrobatics with very long
+author lists. You can force truncation by using the pseudo-name
+``\texttt{others}'', which will usually translate to something like
+``\emph{et al}'' in the typeset output. So, if Mr.~Bloggs wanted to
+distract attention from his co-authors, he would write:
+\begin{quote}
+\begin{verbatim}
+AUTHOR = {Fred Q. Bloggs and others}
+\end{verbatim}
+\end{quote}
+
+\Question[Q-citeURL]{\acro{URL}s in \BibTeX{} bibliographies}
+
+There is no citation type for \acro{URL}s, \emph{per se}, in the
+standard \BibTeX{} styles, though Oren Patashnik (the author of
+\BibTeX{}) is believed to be considering developing one such for use
+with the long-awaited \BibTeX{} version~1.0.
+
+The actual information that need be available in a citation of an
+\acro{URL} is discussed at some length in the publicly available
+on-line
+\begin{narrowversion}
+ extracts of \acro{ISO}~690--2, available via
+ \URL{http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm};
+ % checked 2004-01-15
+\end{narrowversion}
+\begin{wideversion}
+\href{http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm}{extracts of \acro{ISO}\nobreakspace690--2};
+\end{wideversion}
+the techniques below do \emph{not} satisfy all the requirements of
+\acro{ISO}~690--2, but they offer a solution that is at least
+available to users of today's tools.
+
+Until the new version of \BibTeX{} arrives, the simplest technique is
+to use the \texttt{howpublished} field of the standard styles' \texttt{@misc}
+function. Of course, the strictures
+about \Qref*{typesetting \acro{URL}s}{Q-setURL} still apply, so the
+entry will look like:
+\begin{quote}
+\begin{verbatim}
+@misc{...,
+ ...,
+ howpublished = "\url{http://...}"
+}
+\end{verbatim}
+\end{quote}
+A possible alternative approach is to use \BibTeX{} styles other than
+the standard ones, that already have \acro{URL} entry types.
+Candidates are:
+\begin{itemize}
+\item The \Package{natbib} styles (\Package{plainnat},
+ \Package{unsrtnat} and \Package{abbrevnat}), which are extensions of
+ the standard styles, principally for use with \Package{natbib}
+ itself. However, they've acquired \acro{URL}s and other ``modern''
+ entries along the way. The same author's \Package{custom-bib} is
+ also capable of generating styles that honour \acro{URL} entries.
+\item The \Package{babelbib} bundle, which offers % ! line break
+ \Qref*{multilingual bibliographies}{Q-i18nbib}, similarly provides a
+ set of standard-style equivalents that have \acro{URL} entries.
+\item More modern styles such as the \Package{harvard} package (if the
+ citation styles are otherwise satisfactory for you).
+ \Package{Harvard} bibliography styles all include a ``\texttt{url}''
+ field in their specification; however, the typesetting offered is
+ somewhat feeble (though it does recognise and use
+ \ProgName{LaTeX2HTML} macros if they are available, to create
+ hyperlinks).
+\end{itemize}
+You can also acquire new \BibTeX{} styles by use of Norman Gray's
+\Package{urlbst} system, which is based on a \ProgName{Perl} script
+that edits an existing \BibTeX{} style file to produce a new
+style. The new style thus generated has a \texttt{webpage} entry type, and
+also offers support for \texttt{url} and \texttt{lastchecked} fields
+in the other entry types. The \ProgName{Perl} script comes with a set
+of converted versions of the standard bibliography styles.
+
+Another possibility is that some conventionally-published paper,
+technical report (or even book) is also available on the Web. In such
+cases, a useful technique is something like:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+@techreport{...,
+ ...,
+ note = "Also available as \url{http://...}"
+}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+@techreport{...,
+ ...,
+ note = "Also available as
+ \url{http://...}"
+}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+There is good reason to use the \Package{url} or \Package{hyperref}
+packages in this context: \BibTeX{} has a habit of splitting
+lines it considers excessively long, and if there are no space
+characters for it to use as `natural' breakpoints, \BibTeX{} will
+insert a comment (`\texttt{\textpercent{}}') character~\dots{}\@ which
+is an acceptable character in an \acro{URL}. Any current version of
+either of the \Package{url} or \Package{hyperref} packages detects this
+``\texttt{\textpercent{}}--end-of-line'' structure in its argument, and
+removes it.
+\begin{ctanrefs}
+\item[babelbib \nothtml{\rmfamily}bundle]\CTANref{babelbib}
+\item[custom-bib \nothtml{\rmfamily}bundle]\CTANref{custom-bib}
+\item[harvard.sty]\CTANref{harvard}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[natbib \nothtml{\rmfamily}styles]\CTANref{natbib}
+\item[url.sty]\CTANref{url}
+\item[urlbst]\CTANref{urlbst}
+\end{ctanrefs}
+
+\Question[Q-bibplain]{Using \BibTeX{} with \plaintex{}}
+
+The file \File{btxmac.tex} (which is part of the \Eplain{} system)
+contains macros and documentation for using \BibTeX{} with
+\plaintex{}, either directly or with \Qref*{\Eplain{}}{Q-eplain}. See
+\Qref[question]{the use of \BibTeX{}}{Q-BibTeXing} for more
+information about \BibTeX{} itself.
+\begin{ctanrefs}
+\item[btxmac.tex]\CTANref{btxmactex}
+\item[eplain \nothtml{\rmfamily}system]\CTANref{eplain}
+\end{ctanrefs}
+
+\Question[Q-makebib]{Reconstructing \extension{bib} files}
+
+Perhaps you've lost the \extension{bib} file you generated your document from,
+or have been sent a document without one. Or even, you've realised
+the error of building a substantial document without the benefit of
+\BibTeX{}\dots{}
+
+The \ProgName{Perl} script, \Package{tex2bib} makes a reasonable job
+of regenerating \extension{bib} files from \environment{thebibliography}
+environments, provided that the original (whether automatically or
+manually generated) doesn't deviate too far from the ``standard''
+styles.
+
+You are well-advised to check the output of the script. While it will
+not usually destroy information, it can quite reasonably mislabel it.
+
+Documentation of the script is to be found in the file \File{tex2bib.readme}
+\begin{ctanrefs}
+\item[tex2bib]\CTANref{tex2bib}
+\item[tex2bib.readme]\CTANref{tex2bib-doc}
+\end{ctanrefs}
+
+\Question[Q-bibprefixsort]{\BibTeX{} sorting and name prefixes}
+
+\BibTeX{} recognises a bewildering array of name prefixes (mostly
+those deriving from European language names); it ignores the prefixes
+when sorting the bibliography~--- you want ``Ludwig van Beethoven''
+sorted under ``Beethoven'', not under ``van''. (Lamport made a witty
+deliberate mistake with Beethoven's name, in the first edition of his
+\LaTeX{} manual.)
+
+However, a recurring issue is the desire to quote Lord Rayleigh's
+publications (``Lord'' isn't an acceptable prefix), or names from
+languages that weren't considered when \BibTeX{} was designed such as
+``al-Wakil'' (transcribed from the Arabic). What's needed is a
+separate ``sort key'', but \BibTeX{} only allows such a thing in
+citations of items that have no author or editor.
+
+The solution is to embed the sort key in the author's name, but to
+prevent it from being typeset. Patashnik recommends a command
+\csx{noopsort} (no-output-sortkey), which is defined and used as
+follows:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+@PREAMBLE{ {\providecommand{\noopsort}[1]{}} }
+...
+@ARTICLE{Rayleigh1,
+AUTHOR = "{\noopsort{Rayleigh}}{Lord Rayleigh}",
+...
+}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+@PREAMBLE{
+ {\providecommand{\noopsort}[1]{}}
+}
+...
+@ARTICLE{Rayleigh1,
+AUTHOR =
+ "\noopsort{Rayleigh}{Lord Rayleigh}",
+...
+}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+Note that this \csx{noopsort} applies to the last name in this kind of
+construct, so an author with an Arabic name might be rendered:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+...
+AUTHOR = "Ali {\noopsort{Hadiidii}}{al-Hadiidii}",
+...
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+...
+AUTHOR =
+ "Ali {\noopsort{Hadiidii}}{al-Hadiidii}",
+...
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+A further use might deal with word order games, as in the famous
+Vietnamese name:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+...
+AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}",
+...
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+...
+AUTHOR =
+ "\noopsort{Thanh Han The}{Han The Thanh}",
+...
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+though that author seems well-acquainted with Western confusion about
+the significance of the parts of his name (even to the extent of
+missing out the accentuation, as above\dots{}).
+
+\Question[Q-bibtranscinit]{`Multi-letter' initials in \BibTeX{}}
+\keywords{compound initials, transcribed initials}
+
+If your bibliographic style uses initials~+ surname, you may encounter
+a problem with some transcribed names (for example, Russian ones).
+Consider the following example from the real world:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+@article{epifanov1997,
+ author = {Epifanov, S. Yu. and
+ Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+@article{epifanov1997,
+ author = {Epifanov, S. Yu. and Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+Note that the ``Yu'' is the initial, not a complete name. However,
+\BibTeX{}'s algorithms will leave you with a citation~---
+slightly depending on the bibliographic style~--- that reads:
+``S. Y. Epifanov and A. A. Vigasin, \dots{}''. instead of the intended
+``S. Yu. Epifanov and A. A. Vigasin, \dots{}''.
+
+One solution is to replace each affected initial by a command that
+prints the correct combination. To keep your bibliography portable,
+you need to add that command to your bibliography with the
+\texttt{@preamble} directive:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+@preamble{ {\providecommand{\BIBYu}{Yu} } }
+
+@article{epifanov1997,
+ author = {Epifanov, S. {\BIBYu}. and
+ Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+@preamble{ {\providecommand{\BIBYu}{Yu} } }
+
+@article{epifanov1997,
+ author = {Epifanov, S. {\BIBYu}. and Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+If you have many such commands, you may want to put them in a separate
+file and \csx{input} that \LaTeX{} file in a \texttt{@preamble}
+directive.
+
+An alternative is to make the transcription look like an accent, from
+\BibTeX{}'s point of view. For this we need a control sequence that
+does nothing:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+@article{epifanov1997,
+ author = {Epifanov, S. {\relax Yu}. and Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+@article{epifanov1997,
+ author = {Epifanov, S. {\relax Yu}. and
+ Vigasin, A. A.},
+ title = ...
+}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+Like the solution by generating extra commands, this involves tedious
+extra typing; which of the two techniques is preferable for a given
+bibliography will be determined by the names in it. It should be
+noted that a preamble that introduces lots of odd commands is usually
+undesirable if the bibliography is a shared one.
+
+``Compound'' initials (for single names made up of two or more words)
+may be treated in the same way, so one can enter Forster's rather
+complicated name as:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+@article{forster2006,
+ author = {Forster, P.M. {\relax de F.} and Collins, M.},
+ title = ...
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+@article{forster2006,
+ author = {Forster, P.M. {\relax de F.} and
+ Collins, M.},
+ title = ...
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+The same trick can be played if you're entering whole names:
+\begin{quote}
+\begin{verbatim}
+...
+ author = {Epifanov, Sasha {\relax Yu}ri and
+...
+\end{verbatim}
+\end{quote}
+(though no guarantee, that either of those names is right, is
+offered!)
+However, if you're typing the names in the ``natural'' (Western) way,
+with given names first, the trick:
+\begin{quote}
+\begin{verbatim}
+...
+ author = {P.M. {\relax de F.} Forster and
+...
+\end{verbatim}
+\end{quote}
+doesn't work~--- ``de F. Forster'' is treated as a compound family
+names.
+
+
+\subsection{Creating citations}
+
+\Question[Q-usebibtex]{``Normal'' use of \BibTeX{} from \LaTeX{}}
+
+To create a bibliography for your document, you need to perform a
+sequence of steps, some of which seem a bit odd. If you choose to use
+\BibTeX{}, the sequence is:
+
+First: you need a \BibTeX{} bibliography file (a \extension{bib}
+file)~--- see \Qref*[question]{``creating a \BibTeX{} file''}{Q-buildbib}.
+
+Second: you must write your \LaTeX{} document to include a declaration
+of the `style' of bibliography, citations, and a reference to the
+bibliography file mentioned above. So we may have a \LaTeX{}
+file containing:
+\begin{quote}
+\begin{verbatim}
+\bibliographystyle{plain}
+...
+Pooh is heroic~\cite{Milne:1926}.
+...
+Alice struggles~\cite{Carroll:1865}.
+...
+\bibliography{mybooks}
+\end{verbatim}
+\end{quote}
+Note: we have bibliography style \Package{plain}, above, which is
+nearly the simplest of the lot: a sample text, showing the sorts of
+style choices available, can be found on Ken Turner's web site:
+\URL{http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html}
+
+Third: you must process the file.
+\begin{quote}
+\begin{verbatim}
+latex myfile
+\end{verbatim}
+\end{quote}
+As \LaTeX{} processes the file, the \csx{bibliographystyle} command
+writes a note of the style to the \extension{aux} file; each
+\csx{cite} command writes a note of the citation to the
+\extension{aux} file, and the \csx{bibliography} command writes a note
+of which \extension{bib} file is to be used, to the \extension{aux} file.
+
+Note that, at this stage, \LaTeX{} isn't ``resolving'' any of the
+citations: at every \csx{cite} command, \LaTeX{} will warn you of the
+undefined citation, and when the document finishes, there will be a
+further warning of undefined references.
+
+%Some bibliography styles are designed to work with particular
+%packages...
+
+Fourth: you must run \BibTeX{}:
+\begin{quote}
+\begin{verbatim}
+bibtex myfile
+\end{verbatim}
+\end{quote}
+Don't try to tell \BibTeX{} anything but the file name: say
+\texttt{bibtex myfile.aux} (because you know it's going to read the
+\extension{aux} file) and \BibTeX{} will blindly attempt to process
+\texttt{myfile.aux.aux}.
+
+\BibTeX{} will scan the \extension{aux} file; it will find which bibliography
+style it needs to use, and will ``compile'' that style; it will note
+the citations; it will find which bibliography files it needs, and
+will run through them matching citations to entries in the
+bibliography; and finally it will sort the entries that have been
+cited (if the bibliography style specifies that they should be
+sorted), and outputs the resulting details to a \extension{bbl} file.
+
+Fifth: you run \LaTeX{} again. It warns, again, that each citation is
+(still) undefined, but when it gets to the \csx{bibliography} command,
+it finds a \extension{bbl} file, and reads it. As it encounters each
+\csx{bibitem} command in the file, it notes a definition of the
+citation.
+
+Sixth: you run \LaTeX{} yet again. This time, it finds values for all
+the citations, in its \extension{aux} file. Other things being equal, you're
+done\dots{} until you change the file.
+
+If, while editing, you change any of the citations, or add new ones,
+you need to go through the process above from steps 3 (first run of
+\LaTeX{}) to 6, again, before the document is once again stable.
+These four mandatory runs of \LaTeX{} make processing a document with
+a bibliography even more tiresome than the normal two runs required to
+resolve labels.
+
+To summarise: processing to resolve citations requires: \LaTeX{};
+\BibTeX{}; \LaTeX{}; \LaTeX{}.
+
+\Question[Q-whatbst]{Choosing a bibliography style}
+
+A large proportion of people are satisfied with one of Patashnik's
+original ``standard'' styles, \Package{plain}, \Package{unsrt},
+\Package{abbrv} and \Package{alpha}. However, no style in that set
+supports the ``author-date'' citation style that is popular in many
+fields; but there are a very large number of contributed styles
+available, that \emph{do} support the format.
+
+(Note that author-date styles arose because the simple and clear
+citation style that \Package{plain} produces is so awkward in a
+traditional manuscript preparation scenario. However, \TeX{}-based
+document production does away with all those difficulties, leaving us
+free once again to use the simple option.)
+
+Fortunately, help is at hand, on the Web, with this problem:
+\begin{itemize}
+\item a sample text, showing the sorts of style choices available, can
+ be found on
+\begin{narrowversion}
+ Ken Turner's web site:
+ \URL{http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html};
+\end{narrowversion}
+\begin{wideversion}
+ % ! line break
+ \href{http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html}{Ken Turner's web site};
+\end{wideversion}
+\item an excellent survey, that lists a huge variety of styles,
+ sorted into their nominal topics as well as providing a good range
+ of examples, is the Reed College % ! line break
+\begin{narrowversion}
+ ``Choosing a \BibTeX{} style''
+ (\URL{http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html}).
+\end{narrowversion}
+\begin{wideversion}
+ % ! line break
+ ``\href{http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html}{Choosing a \BibTeX{} style}''.
+\end{wideversion}
+\end{itemize}
+
+Of course, these pages don't cover everything; the problem the
+inquisitive user faces, in fact, is to find what the various available
+styles actually do. This is best achieved (if the links above don't
+help) by using \Package{xampl.bib} from the \BibTeX{} documentation
+distribution: one can get a pretty good feel for any style one has to
+hand using this ``standard'' bibliography. For style
+\Package{my-style.bst}, the simple \LaTeX{} document:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\begin{document}
+\bibliographystyle{my-style}
+\nocite{*}
+\bibliography{xampl}
+\end{document}
+\end{verbatim}
+\end{quote}
+will produce a representative sample of the citations the style will
+produce. (Because \Package{xampl.bib} is so extreme in some of its
+``examples'', the \BibTeX{} run will also give you an interesting
+selection of \BibTeX{}'s error messages\dots{})
+\begin{ctanrefs}
+\item[xampl.bib]\CTANref{xampl-bib}
+\end{ctanrefs}
+
+\Question[Q-chapbib]{Separate bibliographies per chapter?}
+
+A separate bibliography for each `chapter' of a document can be provided
+with the package \Package{chapterbib} (which comes with a bunch of
+other good bibliographic things). The package allows you a
+different bibliography for each \csx{include}d file (i.e., despite the
+package's name, the availability of bibliographies is related to the
+component source files of the document rather than to the chapters that
+logically structure the document).
+
+The package \Package{bibunits} ties bibliographies to logical units
+within the document: the package will deal with chapters and sections
+(as defined by \LaTeX{} itself) and also defines a \environment{bibunit}
+environment so that users can select their own structuring.
+
+\Qref*{The \Package{biblatex} package}{Q-biblatex}, with
+\ProgName{biber}, provides a similar facility; enclose the text for
+which you want a local bibliography in a \environment{refsection}
+environment, and place a \csx{printbibliography} command as the last
+thing in that environment:
+\begin{quote}
+\begin{verbatim}
+\begin{refsection}
+\chapter{First chapter}
+\section{Foo}
+Some text \cite{this}
+with citations \cite{that}.
+\printbibliography
+\end{refsection}
+\end{verbatim}
+\end{quote}
+Then process with \latex{} (of whatever flavour) and use
+\ProgName{biber} to process the bibliography output. Note that
+\csx{printbibliography} can take an optional argument
+\pkgoption{heading=bib title} to provide the bibliography with a
+(sub)section title.
+\begin{ctanrefs}
+\item[biber]\CTANref{biber}
+\item[biblatex]\CTANref{biblatex}
+\item[bibunits.sty]\CTANref{bibunits}
+\item[chapterbib.sty]distributed as part of \CTANref{cite}[chapterbib]
+\end{ctanrefs}
+\LastEdit{2013-01-04}
+
+\Question[Q-multbib]{Multiple bibliographies?}
+
+If you're thinking of multiple bibliographies tied to some part of
+your document (such as the chapters within the document), please see
+\Qref[question]{bibliographies per chapter}{Q-chapbib}.
+
+For more than one bibliography, there are three options.
+
+The \Package{multibbl} package offers a very simple interface: you use
+a command \csx{newbibliography} to define a bibliography ``tag''. The package
+redefines the other bibliography commands so that each time you use any one
+of them, you give it the tag for the bibliography where you want the
+citations to appear. The \csx{bibliography} command itself also takes
+a further extra argument that says what title to use for the resulting
+section or chapter (i.e., it patches
+\nothtml{\csx{refname} and \csx{bibname}~---}
+\Qref{\csx{refname} and \csx{bibname}}{Q-fixnam}\nothtml{~---} in a
+\Package{babel}-safe way). So one might write:
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{multibbl}
+\newbibliography{bk}
+\bibliographystyle{bk}{alpha}
+\newbibliography{art}
+\bibliographystyle{art}{plain}
+...
+\cite[pp.~23--25]{bk}{milne:pooh-corner}
+...
+\cite{art}{einstein:1905}
+...
+\bibliography{bk}{book-bib}%
+ {References to books}
+\bibliography{art}{art-bib}%
+ {References to articles}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{multibbl}
+\newbibliography{bk}
+\bibliographystyle{bk}{alpha}
+\newbibliography{art}
+\bibliographystyle{art}{plain}
+...
+\cite[pp.~23--25]{bk}{milne:pooh-corner}
+...
+\cite{art}{einstein:1905}
+...
+\bibliography{bk}{book-bib}{References to books}
+\bibliography{art}{art-bib}{References to articles}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+(Note that the optional argument of \csx{cite} appears \emph{before} the
+new tag argument, and that the \csx{bibliography} commands may list
+more than one \extension{bib} file~--- indeed all \csx{bibliography} commands
+may list the same set of files.)
+
+The \csx{bibliography} data goes into files whose names are
+\meta{tag-name}\emph{.aux}, so you will need to run
+\begin{quote}
+\begin{verbatim}
+bibtex bk
+bibtex art
+\end{verbatim}
+\end{quote}
+after the first run of \LaTeX{}, to get the citations in the correct
+place.
+
+The \Package{multibib} package allows you to define a series of
+``additional topics'', each of which comes with its own series of
+bibliography commands. So one might write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{multibib}
+\newcites{bk,art}%
+ {References from books,%
+ References from articles}
+\bibliographystylebk{alpha}
+\bibliographystyleart{plain}
+...
+\citebk[pp.~23--25]{milne:pooh-corner}
+...
+\citeart{einstein:1905}
+...
+\bibliographybk{book-bib}
+\bibliographyart{art-bib}
+\end{verbatim}
+\end{quote}
+Again, as for \Package{multibbl}, any \csx{bibliography...} command may
+scan any list of \extension{bib} files.
+
+\BibTeX{} processing with \Package{multibib} is much like that with
+\Package{multibbl}; with the above example, one needs:
+\begin{quote}
+\begin{verbatim}
+bibtex bk
+bibtex art
+\end{verbatim}
+\end{quote}
+Note that, unlike \Package{multibbl}, \Package{multibib} allows a
+simple, unmodified bibliography (as well as the ``topic'' ones).
+
+The \Package{bibtopic} package allows you separately to cite several
+different bibliographies. At the appropriate place in your document,
+you put a sequence of \environment{btSect} environments (each of which
+specifies a bibliography database to scan) to typeset the separate
+bibliographies. Thus, one might have a file \File{diss.tex} containing:
+\begin{quote}
+\begin{verbatim}
+\usepackage{bibtopic}
+\bibliographystyle{alpha}
+...
+\cite[pp.~23--25]{milne:pooh-corner}
+...
+\cite{einstein:1905}
+...
+\begin{btSect}{book-bib}
+\section{References from books}
+\btPrintCited
+\end{btSect}
+\begin{btSect}[plain]{art-bib}
+\section{References from articles}
+\btPrintCited
+\end{btSect}
+\end{verbatim}
+\end{quote}
+Note the different way of specifying a bibliographystyle: if you want
+a different style for a particular bibliography, you may give it as an
+optional argument to the \environment{btSect} environment.
+
+Processing with \BibTeX{}, in this case, uses \extension{aux} files whose names
+are derived from the name of the base document. So in this example
+you need to say:
+\begin{quote}
+\begin{verbatim}
+bibtex diss1
+bibtex diss2
+\end{verbatim}
+\end{quote}
+
+There is also a command \csx{btPrintNotCited}, which gives the rest of
+the content of the database (if nothing has been cited from the
+database, this is equivalent to \LaTeX{} standard \cmdinvoke{nocite}{*}).
+
+However, the \emph{real} difference from \Package{multibbl} and
+\Package{multibib} is that selection of what appears in each
+bibliography section is determined in \Package{bibtopic} by what's in
+the \extension{bib} files.
+
+An entirely different approach is taken by the \Package{splitbib}
+package. You provide a \environment{category} environment, in the
+preamble of your document, for each category you want a separate
+citation list for. In each environment, you list the \csx{cite} keys
+that you want listed in each category. The \csx{bibliography} command
+(or, more precisely, the \environment{thebibliography} environment it
+uses) will sort the keys as requested. (Keys not mentioned in a
+\environment{category} appear in a ``misc'' category created in the
+sorting process.) A code example appears in the package documentation
+(a \acro{PDF} file in the \acro{CTAN} directory,
+\begin{htmlversion}
+ which you can browse to, from the link, below).
+\end{htmlversion}
+\htmlignore
+ see the file list, below).
+\endhtmlignore
+\begin{ctanrefs}
+\item[bibtopic.sty]\CTANref{bibtopic}
+\item[multibbl.sty]\CTANref{multibbl}
+\item[multibib.sty]\CTANref{multibib}
+\item[splitbib.sty]\CTANref{splitbib}
+\end{ctanrefs}
+
+
+\Question[Q-bibinline]{Putting bibliography entries in text}
+
+This is a common requirement for journals and other publications in
+the humanities. Sometimes the requirement is for the entry to appear
+in the running text of the document, while other styles require that
+the entry appear in a footnote.
+
+Options for entries in running text are
+\begin{itemize}
+\item The package \Package{bibentry}, which puts slight restrictions
+ on the format of entry that your \extension{bst} file generates, but is
+ otherwise undemanding of the bibliography style.
+\item The package \Package{inlinebib}, which requires that you use its
+ \File{inlinebib.bst}. \Package{Inlinebib} was actually designed for
+ footnote citations: its \emph{expected} use is that you place a
+ citation inline as the argument of a \csx{footnote} command.
+\item The package \Package{jurabib}, which was originally designed for
+ German law documents, and has comprehensive facilities for the
+ manipulation of citations. The package comes with four bibliography
+ styles that you may use: \File{jurabib.bst}, \File{jhuman.bst} and
+ two Chicago-like ones.
+\end{itemize}
+
+Options for entries in footnotes are
+\begin{itemize}
+\item The package \Package{footbib}, and
+\item Packages \Package{jurabib} and \Package{inlinebib}, again.
+\end{itemize}
+Note that \Package{jurabib} does the job using \LaTeX{}'s standard
+footnotes, whereas \Package{footbib} creates its own sequence of
+footnotes. Therefore, in a document which has other footnotes, it may
+be advisable to use \Package{jurabib} (or of course
+\Package{inlinebib}), to avoid confusion of footnotes and
+foot-citations.
+
+The \Package{usebib} package offers a `toolbox', which allows the user
+to place exactly what is needed, in the text (that is, rather than a
+full citation). The package's command, that does the actual
+typesetting, is \cmdinvoke{usebibdata}{\meta{key}}{\meta{field}}; it
+typesets the \emph{field} item from the entry \emph{key} in the
+bibliography; the user then formats the entry as desired~--- obviously
+one could construct one's own bibliography, altogether, from this
+command, but it would quickly become tedious.
+\begin{ctanrefs}
+\item[bibentry.sty]\emph{Distributed with} \CTANref{natbib}
+\item[footbib.sty]\CTANref{footbib}
+\item[inlinebib.sty]\CTANref{inlinebib}
+\item[jurabib.sty]\CTANref{jurabib}
+\item[usebib.sty]\CTANref{usebib}
+\end{ctanrefs}
+\LastEdit{2012-03-23}
+
+\Question[Q-citesort]{Sorting and compressing citations}
+
+If you give \LaTeX{}
+\cmdinvoke{cite}{fred,joe,harry,min}, its default commands could give
+something like ``[2,6,4,3]'';
+this looks awful. One can of course get the things in order by
+rearranging the keys in the \csx{cite} command, but who wants to do
+that sort of thing for no more improvement than ``[2,3,4,6]''?
+
+The \Package{cite} package sorts the numbers and detects consecutive
+sequences, so creating ``[2--4,6]''. The \Package{natbib} package,
+with the \pkgoption{numbers} and \pkgoption{sort\&compress} options, will
+do the same when working with its own numeric bibliography styles
+(\File{plainnat.bst} and \File{unsrtnat.bst}).
+
+The package \Package{biblatex} has a built-in style
+\Package{numeric-comp} for its bibliographies.
+\begin{ctanrefs}
+\item[biblatex.sty]\CTANref{biblatex}
+\item[cite.sty]\CTANref{cite}
+\item[hypernat.sty]\CTANref{hypernat}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[plainnat.bst]Distributed with \CTANref{natbib}
+\item[unsrtnat.bst]Distributed with \CTANref{natbib}
+\end{ctanrefs}
+\LastEdit{2012-02-10}
+
+\Question[Q-mcite]{Multiple citations}
+
+A convention sometimes used in physics journals is to ``collapse'' a group of
+related citations into a single entry in the bibliography. \BibTeX{},
+by default, can't cope with this arrangement, but the \Package{mcite}
+and \Package{mciteplus} packages deal with the problem.
+
+\Package{mcite} overloads the \csx{cite} command to recognise a
+``\texttt{*}'' at the start of a key, so that citations of the form
+\begin{quote}
+\begin{verbatim}
+\cite{paper1,*paper2}
+\end{verbatim}
+\end{quote}
+appear in the document as a single citation, and appear arranged
+appropriately in the bibliography itself. You're not limited to
+collapsing just two references. You can mix ``collapsed'' references
+with ``ordinary'' ones, as in
+\begin{quote}
+\begin{verbatim}
+\cite{paper0,paper1,*paper2,paper3}
+\end{verbatim}
+\end{quote}
+Which will appear in the document as 3~citations ``[4,7,11]''
+(say)~--- citation `4' will refer to paper~0, `7' will refer to a
+combined entry for paper~1 and paper~2, and `11' will refer to
+paper~3.
+
+You need to make a small change to the bibliography style
+(\extension{bst}) file you use; the \Package{mcite} package
+documentation tells you how to do that.
+
+Most recent versions of \Class{REVTeX} (version 4.1 and later), in
+conjunction with recent versions of \Package{natbib}, already contain
+support for combined citations and so no longer even need
+\Package{mciteplus} (but \Package{mciteplus} is more general and will
+work with many other class and package combinations).
+
+The \Package{mciteplus} package adresses many of the infelicites of
+\Package{mcite}. Again, `ordinary' \extension{bst} files will not
+work with \Package{mciteplus}, but the package documentation explains
+how to patch an existing \BibTeX{} style.
+
+The \Package{collref} package takes a rather different approach to the
+problem, and will work with most (if not all) \BibTeX{} packages.
+\Package{Collref} spots common subsets of the references, so if it
+sees a sequence
+\begin{quote}
+\begin{verbatim}
+\cite{paper0,paper1,paper2,paper3}
+...
+\cite{some_other_paper,paper1,paper2,and_another}
+\end{verbatim}
+\end{quote}
+it will collect \texttt{paper1} and \texttt{paper2} as a multiple reference.
+\begin{ctanrefs}
+\item[collref.sty]\CTANref{collref}
+\item[mcite.sty]\CTANref{mcite}
+\item[mciteplus.sty]\CTANref{mciteplus}
+\item[natbib.sty]\CTANref{natbib}
+\item[revtex 4.1]\CTANref{revtex4-1}
+\end{ctanrefs}
+\LastEdit{2010-07-07}
+
+\Question[Q-backref]{References from the bibliography to the citation}
+
+A link (or at least a page reference), from the bibliography to the
+citing command, is often useful in large documents.
+
+Two packages support this requirement, \Package{backref} and
+\Package{citeref}. \Package{Backref} is part of the
+\Package{hyperref} bundle, and supports hyperlinks back to the citing
+command.
+
+\Package{Citeref} is the older, and seems to rely on rather simpler
+(and therefore possibly more stable) code; it produces a list of page
+references, only. It doesn't interact well with other citation
+packages (for example, \Package{cite}), which probably reflects its
+antiquity (it's derived from a \LaTeXo{} package).
+
+Neither collapses
+lists of pages (``\texttt{5, 6, 7}'' comes out as such, rather than as
+``\texttt{5--7}''), but neither package repeats the reference to a page that
+holds multiple citations. (The failure to collapse lists is of course
+forgiveable in the case of the \Package{hyperref}-related
+\Package{backref}, since the concept of multiple hyperlinks from the
+same anchor is less than appealing.)
+\begin{ctanrefs}
+\item[backref.sty]Distributed with \CTANref{hyperref}
+\item[citeref.sty]\CTANref{citeref}
+\end{ctanrefs}
+
+\Question[Q-sortbib]{Sorting lists of citations}
+
+\BibTeX{} has a sorting function, and most \BibTeX{} styles sort the
+citation list they produce; most people find this desirable.
+
+However, it is perfectly possible to write a
+\environment{thebibliography} environment that \emph{looks} as if it
+came from \BibTeX{}, and many people do so (in order to save time in
+the short term).
+
+The problem arises when \environment{thebibliography}-writers decide
+their citations need to be sorted. A common misapprehension is to
+insert \cmdinvoke{bibliographystyle}{alpha} (or similar) and expect
+the typeset output to be sorted in some magical way. \BibTeX{}
+doesn't work that way!~--- if you write \environment{thebibliography},
+you get to sort its contents. \BibTeX{} will only sort the contents
+of a \environment{thebibliography} environment when it creates it, to
+be inserted from a \extension{bbl} file by a \csx{bibliography} command.
+
+\Question[Q-compactbib]{Reducing spacing in the bibliography}
+
+Bibliographies are, in fact, implemented as lists, so all the
+confusion about \Qref*{reducing list item spacing}{Q-complist} also
+applies to bibliographies.
+
+If the \Package{natbib} package `works' for you (it may not if you are using
+some special-purpose bibliography style), the solution is relatively
+simple~--- add
+\begin{quote}
+\begin{verbatim}
+\usepackage{natbib}
+\setlength{\bibsep}{0.0pt}
+\end{verbatim}
+\end{quote}
+to the preamble of your document.
+
+The \Package{compactbib} package has a similar effect. Its primary
+purpose is to produce two bibliographies, and it seems to preclude use
+of \BibTeX{} (though the package documentation, in the package file
+itself, isn't particularly clear).
+
+Otherwise, one is into unseemly hacking of something or other. The
+\Package{mdwlist} package actually does the job, but it doesn't work
+here, because it makes a different-named list, while the name
+``\environment{thebibliography}'' is built into \LaTeX{} and
+\BibTeX{}. Therefore, we need to % ! line break
+\Qref*{patch the underlying macro}{Q-patch}:
+\begin{quote}
+\begin{verbatim}
+\let\oldbibliography\thebibliography
+\renewcommand{\thebibliography}[1]{%
+ \oldbibliography{#1}%
+ \setlength{\itemsep}{0pt}%
+}
+\end{verbatim}
+\end{quote}
+The \Package{savetrees} package performs such a patch, among a
+plethora of space-saving measures: you can, in principle, suppress all
+its other actions, and have it provide you a compressed bibliography
+\emph{only}.
+\begin{ctanrefs}
+\item[compactbib.sty]\CTANref{compactbib}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
+\item[natbib.sty]\CTANref{natbib}
+\item[savetrees.sty]\CTANref{savetrees}
+\end{ctanrefs}
+
+\Question[Q-bibtocorder]{Table of contents rearranges ``\Package{unsrt}'' ordering}
+
+If you're using the \Package{unsrt} bibliography style, you're
+expecting that your bibliography will \emph{not} be sorted, but that
+the entries will appear in the order that they first appeared in your
+document.
+
+However, if you're unfortunate enough to need a citation in a section
+title, and you also have a table of contents, the citations that now
+appear in the table of contents will upset the ``natural'' ordering
+produced by the \Package{unsrt} style. Similarly, if you have
+citations in captions, and have a list of figures (or tables).
+
+There's a pretty simple ``manual'' method for dealing with the
+problem~--- when you have the document stable:
+\begin{enumerate}
+\item Delete the \extension{aux} file, and any of \extension{toc},
+ \extension{lof}, \extension{lot} files.
+\item Run \LaTeX{}.
+\item Run \BibTeX{} for the last time.
+\item Run \LaTeX{} often enough that things are stable again.
+\end{enumerate}
+Which is indeed simple, but it's going to get tedious when you've
+found errors in your ``stable'' version, often enough.
+
+The package \Package{notoccite} avoids the kerfuffle, and suppresses
+citations while in the table of contents, or lists of figures, tables
+(or other floating things: the code is quite general).
+\begin{ctanrefs}
+\item[notoccite.sty]\CTANref{notoccite}
+\end{ctanrefs}
+
+\Question[Q-i18nbib]{Non-english bibliographies}
+
+Like so much of early \AllTeX{} software, \BibTeX{}'s assumptions were
+firmly rooted in what its author knew well, viz., academic papers in
+English (particularly those with a mathematical bent). \BibTeX{}'s
+standard styles all address exactly that problem, leaving the user who
+writes in another language (or who deal with citations in the style of
+other disciplines than maths) to strike out into contributed software.
+
+For the user whose language is not English, there are several
+alternatives. Possibly most straightforward is to switch to using
+\Package{biblatex}, which can produce a bibliography appropriate to
+several languages. However, \Package{biblatex} is large and has
+correspondingly large documentation (though it is well-written and
+pleasingly typeset), so its adoption takes time.
+
+Otherwise, the simplest procedure is to provide translations of
+\BibTeX{} styles into the
+required language: the solitary \Package{finplain.bst} does that for
+Finnish; others one can find are for Danish (\Package{dk-bib}), French
+(\Package{bib-fr}), German (\Package{bibgerm}), Norwegian
+(\Package{norbib}) and Swedish (\Package{swebib}) bundles (of which
+the \Package{bib-fr} set is the most extensive). The \Package{spain}
+style implements a traditional Spanish citation style.
+
+These static approaches solve the problem, for the languages that have
+been covered by them. Unfortunately, with such an approach, a lot of
+work is needed for every language involved. Two routes to a solution
+of the ``general'' problem are available~--- that offered by
+\Package{babelbib}, and the % ! line break
+\Qref*{\Package{custom-bib} mechanism for generating styles}{Q-custbib}.
+
+\Package{Babelbib} (which is a development of the ideas of the
+\Package{bibgerm} package) co-operates with \Package{babel} to control
+the language of presentation of citations (potentially at the level of
+individual items). The package has a built-in set of languages it
+`knows about', but the documentation includes instructions on defining
+commands for other languages. \Package{Babelbib} comes with its own
+set of bibliography styles, which could be a restriction if there
+wasn't also a link from \Package{custom-bib}.
+
+The \Package{makebst} menu of \Package{custom-bib} allows you to
+choose a language for the \BibTeX{} style you're generating (there are
+14 languages to choose; it looks as if \Package{spain.bst}, mentioned
+above, was generated this way). If, however, you opt not to specify a
+language, you are asked whether you want the style to interact with
+\Package{babelbib}; if you do so, you're getting the best of both
+worlds~--- formatting freedom from \Package{custom-bib} and linguistic
+freedom via the extensibility of \Package{babelbib}
+\begin{ctanrefs}
+\item[babelbib.sty]\CTANref{babelbib}
+\item[bib-fr \nothtml{\rmfamily\upshape}bundle]\CTANref{bib-fr}
+\item[bibgerm \nothtml{\rmfamily\upshape}bundle]\CTANref{bibgerm}
+\item[biblatex.sty]\CTANref{biblatex}
+\item[custom-bib \nothtml{\rmfamily\upshape}bundle]\CTANref{custom-bib}
+\item[finplain.bst]\CTANref{finplain}
+\item[norbib \nothtml{\rmfamily\upshape}bundle]\CTANref{norbib}
+\item[spain]\CTANref{spain}
+\item[swebib \nothtml{\rmfamily\upshape}bundle]\CTANref{swebib}
+\end{ctanrefs}
+\LastEdit{2012-03-23}
+
+\Question[Q-formbiblabel]{Format of numbers in the bibliography}
+
+By default, \LaTeX{} makes entries in the bibliography look like:
+\begin{quote}
+ [1] Doe, Joe et al. Some journal. 2004.\\ {}
+ [2] Doe, Jane et al. Some journal. 2003.
+\end{quote}
+while many documents need something like:
+\begin{quote}
+ 1. Doe, Joe et al. Some journal. 2004.\\
+ 2. Doe, Jane et al. Some journal. 2003.
+\end{quote}
+
+This sort of change may be achieved by many of the ``general''
+citation packages; for example, in \Package{natbib}, it's as simple as:
+\begin{quote}
+\begin{verbatim}
+\renewcommand{\bibnumfmt}[1]{#1.}
+\end{verbatim}
+\end{quote}
+but if you're not using such a package, the following internal
+\LaTeX{} commands, in the preamble of your document, will do the job:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\renewcommand*{\@biblabel}[1]{\hfill#1.}
+\makeatother
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[natbib.sty]\CTANref{natbib}
+\end{ctanrefs}
+
+\subsection{Manipulating whole bibliographies}
+
+\Question[Q-nocite*]{Listing all your \BibTeX{} entries}
+
+\LaTeX{} and \BibTeX{} co-operate to offer special treatment of this
+requirement. The command \cmdinvoke{nocite}{*} is specially treated,
+and causes \BibTeX{} to generate bibliography entries for every entry
+in each \extension{bib} file listed in your \csx{bibliography} statement, so
+that after a \LaTeX{}--\BibTeX{}--\LaTeX{} sequence, you have a
+document with the whole thing listed.
+
+Note that \LaTeX{} \emph{doesn't} produce
+% beware line breaks
+``\texttt{Citation ... undefined}'' or
+``\texttt{There were undefined references}'' warnings in respect of
+\cmdinvoke{nocite}{*}. This isn't a problem if you're running
+\LaTeX{} ``by hand'' (you \emph{know} exactly how many times you have
+to run things), but the lack might confuse automatic processors that
+scan the log file to determine whether another run is necessary.
+
+A couple of packages are available, that aim to reduce the impact of
+\cmdinvoke{nocite}{*} of a large citation database. \Package{Biblist}
+was written for use under \LaTeXo{}, but seems to work well enough;
+\Package{listbib} is more modern. Both provide their own
+\extension{bst} files. (The impact of large databases was significant
+in the old days of \LaTeX{} systems with very little free memory; this
+problem is less significant now than it once was.)
+\begin{ctanrefs}
+\item[biblist.sty]\CTANref{biblist}
+\item[listbib.sty]\CTANref{listbib}
+\end{ctanrefs}
+
+\Question[Q-htmlbib]{Making \acro{HTML} of your Bibliography}
+
+A neat solution is offered by the \Package{noTeX} bibliography style.
+This style produces a \extension{bbl} file which is in fact a series of
+\acro{HTML} `\texttt{P}' elements of class \texttt{noTeX}, and which
+may therefore be included in an \acro{HTML} file. Provision is made
+for customising your bibliography so that its content when processed by
+\Package{noTeX} is different from that presented when it is processed
+in the ordinary way by \AllTeX{}.
+
+A thorough solution is offered by \Package{bib2xhtml}; using it, you
+make use of one of its modified versions of many common \BibTeX{}
+styles, and post-process the output so produced using a
+\ProgName{perl} script.
+
+A more conventional translator is the \ProgName{awk} script
+\ProgName{bbl2html}, which translates the \extension{bbl} file you've generated:
+a sample of the script's output may be viewed on the web, at
+\URL{http://rikblok.cjb.net/lib/refs.html}
+\begin{ctanrefs}
+\item[bbl2html.awk]\CTANref{bbl2html}
+\item[bib2xhtml]\CTANref{bib2xhtml}
+\item[noTeX.bst]\CTANref{noTeX}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-bits+pieces.tex b/help/uk-tex-faq/faq-bits+pieces.tex
new file mode 100644
index 0000000000..113d1139e4
--- /dev/null
+++ b/help/uk-tex-faq/faq-bits+pieces.tex
@@ -0,0 +1,1174 @@
+% $Id: faq-bits+pieces.tex,v 1.32 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Bits and pieces of \AllTeX{}}
+
+\Question[Q-dvi]{What is a \acro{DVI} file?}
+
+`\acro{DVI}' is supposed to be an acronym for
+\acro{D}e\acro{V}ice-\acro{I}ndependent, meaning that the file may be
+processed for printing or viewing on most kinds of typographic output
+device or display.
+
+A \acro{DVI} file (that is, a file with the type or extension
+\extension{dvi}) is the main output file of ``original'' \tex{} (later
+\tex{}-like systems, such as \Qref*{\pdftex{}}{Q-whatpdftex} may use
+other formats).
+
+A \acro{DVI} file contains all the information that is needed for
+printing or previewing, except for the actual bitmaps or outlines of
+fonts, and any material to be introduced by means of % !line break
+\Qref*{\csx{special} commands}{Q-specials}. Characters in the
+\acro{DVI} file (representing glyphs for printing or display) appear
+in an encoding determined in the document.
+
+Any \TeX{} input file should produce the same \acro{DVI} file
+regardless of which implementation of \TeX{} is used to produce it.
+
+An \acro{DVI} file may be processed by a \Qref*{DVI driver}{Q-driver}
+to produce further output designed specifically for a particular
+printer, or for output in another format (for distribution), or it may
+be used by a previewer for display on a computer screen.
+
+Note that \Qref*{\xetex{}}{Q-xetex} (released some time after
+\pdftex{}) uses an ``extended \acro{DVI} format'' (\acro{XDV}) to send
+its output to a close-coupled \Qref*{\acro{DVI} driver}{Q-driver},
+\ProgName{xdvipdfmx}.
+
+The canonical reference for the structure of a \acro{DVI} file is the
+source of Knuth's program \ProgName{dvitype} (whose original purpose,
+as its name implies, was to view the content of a \acro{DVI} file).
+A partially complete ``standard'' for the way they should be
+processed may offer further enlightenment.
+\begin{ctanrefs}
+\item[\nothtml{rmfamily}DVI processing standard]\CTANref{dvistd}
+\item[dvitype]\CTANref{dvitype}
+\end{ctanrefs}
+\LastEdit{2013-03-15}
+
+\Question[Q-driver]{What is a \acro{DVI} driver?}
+
+A \acro{DVI} driver is a program that takes as input a
+\Qref*{\acro{DVI} file}{Q-dvi}
+and (usually) produces a file in a format that something \emph{other}
+than a \TeX{}-related program can process.
+
+A driver may be designed for producing output for printing (e.g.,
+\PS{}), for later processing (e.g., \PS{} for inclusion in a later
+document), or for document exchange (e.g., \acro{PDF}).
+
+As well as the \acro{DVI} file, the driver typically also needs font
+information. Font information may be held as bitmaps or as outlines,
+or simply as a set of pointers into the fonts that a printer itself
+provides. Each driver will expect the font information in a particular
+form.
+
+For more information on the forms of font information, see
+\Qref[questions]{\acro{PK} files}{Q-pk},
+% ! line break
+\Qref[]{\acro{TFM} files}{Q-tfm},
+\Qref[]{virtual fonts}{Q-virtualfonts}
+and \Qref[]{Using \PS{} fonts with \TeX{}}{Q-usepsfont}.
+\LastEdit{2011-10-10}
+
+\Question[Q-pk]{What are \acro{PK} files?}
+
+\acro{PK} files (packed raster) are the canonical form of \tex{} font
+bitmaps. The output from \Qref*{\MF{}}{Q-useMF} includes a generic
+font (\acro{GF}) file and the utility \ProgName{gftopk} produces a
+\acro{PK} file from that.
+
+There are potentially a lot of \acro{PK} files, as one
+is needed for each font: that is for each magnification of each
+design (point) size for each weight for each font in each family.
+
+Further, since the \acro{PK} files for one printer do not necessarily
+work well for another, the whole set needs to be duplicated for each
+printer type at a site.
+
+While this menagerie of bitmaps can (in principle) provide fonts that
+are closely matched to the capabilities of each printer, the size of
+the collection (and the resulting difficulty of maintaining it) has
+been a potent driver to the move towards outline fonts such as
+\Qref*{Adobe Type 1 fonts}{Q-adobetypen}.
+\LastEdit{2012-10-20}
+
+\Question[Q-tfm]{What are \acro{TFM} files?}
+
+\acro{TFM} is an acronym for `\TeX{} Font Metrics'; \acro{TFM} files hold
+information about the sizes of the characters of the font in question,
+and about ligatures and kerns within that font. One \acro{TFM} file is
+needed for each font used by \TeX{}, that is for each design (point)
+size for each weight for each family; each \acro{TFM} file serves for all
+magnifications of `its' font, so that there are (typically) fewer
+\acro{TFM} files than there are \Qref*{\acro{PK}}{Q-pk} files. \TeX{},
+\LaTeX{}, etc.,\@
+themselves need only know about the sizes of characters and their
+interactions with each other, but not what characters look like. By
+contrast, \acro{TFM} files are not, in principle, needed by the
+\acro{DVI} driver, which only needs to know about the glyphs that each
+character selects, so as to print or display them.
+
+Note that TrueType and OpenType fonts contain the necessary metrics,
+so that \Qref{\xetex{}}{Q-xetex} and \Qref{\luatex{}}{Q-luatex}, using
+such fonts, have no need of \acro{TFM} files. A corollary of this is
+that setting up fonts for use by these engines is far \emph{easier}.
+\LastEdit{2012-10-20}
+
+\Question[Q-virtualfonts]{What are virtual fonts?}
+
+Virtual fonts provide a means of collecting bits and pieces together
+to make the glyphs of a font: the bits and pieces may be glyphs from
+``other'' fonts, rules and other ``basic'' typesetting commands, and
+the positioning information that specifies how everything comes
+together.
+
+An early instance of something like virtual fonts for \TeX{} was
+implemented by David Fuchs to use an unusual printer. However, for
+practical purposes for the rest of us, virtual fonts date from when Knuth
+specified a format and wrote some support software, in 1989 (he
+published an % ! line break
+\href{http://tug.org/TUGboat/tb11-1/tb27knut.pdf}{article in \textsl{TUGboat}}
+at the time; a plain text copy is available on \acro{CTAN}).
+
+Virtual fonts provide a way of telling \TeX{} about something more
+complicated than just a one-to-one character mapping. \TeX{} reads a
+\acro{TFM} file of the font, just as before, but the \acro{DVI}
+processor will read the \acro{VF} and use its content to specify how
+each glyph is to be processed.
+
+The virtual font may contain commands:
+\begin{itemize}
+\item to `open' one or more (real) fonts for subsequent use,
+\item to remap a glyph from one of the (real) fonts for use in the
+ virtual font,
+\item to build up a more complicated effect (using \acro{DVI} commands).
+\end{itemize}
+
+% !this has to be generated as a new paragraph by the translator, so
+% leave the blank line in place
+In practice, the most common use of virtual fonts is to remap
+Adobe Type 1 fonts (see \Qref[question]{font metrics}{Q-metrics}),
+though there has also been useful useful work building `fake' maths
+fonts (by bundling glyphs from several fonts into a single virtual
+font). Virtual Computer Modern fonts, making a % ! line break
+\Qref*{Cork encoded}{Q-ECfonts} font from Knuth's originals by using
+remapping and fragments of \acro{DVI} for single-glyph `accented
+characters', were the first ``Type~1 format'' Cork-encoded Computer
+Modern fonts available.
+
+Virtual fonts are normally created in a single \acro{ASCII} \acro{VPL}
+(Virtual Property List) file, which includes two sets of information.
+The \ProgName{vptovf} utility will use the \acro{VPL} file to create
+the binary \acro{TFM} and \acro{VF} files.
+
+A ``how-to'' document, explaining how to generate a \acro{VPL},
+describes the endless hours of fun that may be had, doing the job by
+hand. Despite the pleasures to be had, the commonest way (nowadays)
+of generating an \acro{VPL} file is to use the
+\ProgName{fontinst} package, which is described in more detail
+\htmlonly{together with the discussion of}
+\Qref[in answer]{\PS{} font metrics}{Q-metrics}.
+\Package{Qdtexvpl} is another utility for creating ad-hoc virtual
+fonts (it uses \TeX{} to parse a description of the virtual font, and
+\ProgName{qdtexvpl} itself processes the resulting \acro{DVI} file).
+\begin{ctanrefs}
+\item[fontinst]\CTANref{fontinst}
+\item[\nothtml{\rmfamily}Knuth on virtual fonts]\CTANref{vf-knuth}
+\item[\nothtml{\rmfamily}Virtual fonts ``how to'']\CTANref{vf-howto}
+\item[qdtexvpl]\CTANref{qdtexvpl}
+\end{ctanrefs}
+\LastEdit{2012-10-20}
+
+\Question[Q-whatmacros]{What are (\TeX{}) macros}
+
+\TeX{} is a \emph{macro processor}: this is a computer-science-y term
+meaning ``text expander'' (more or less); \TeX{} typesets text as it
+goes along, but \emph{expands} each macro it finds. \TeX{}'s macros
+may include instructions to \TeX{} itself, on top of the simple text
+generation one might expect.
+
+Macros are a \emph{good thing}, since they allow the user to
+manipulate documents according to context. For example, the macro
+\csx{TeX} is usually defined to produce ``TEX'' with the `E' lowered
+(the original idea was Knuth's),
+but in these \acro{FAQ}s the default definition of the macro is
+overridden, and it simply expands to the letters ``TeX''. (\emph{You}
+may not think this a good thing, but the author of the macros has his
+reasons~-- see \Qref[question]{\TeX{}-related logos}{Q-logos}.)
+
+Macro names are conventionally built from a \texttt{\textbackslash }
+followed by a sequence of letters, which may be upper or lower case
+(as in \csx{TeX}, mentioned above). They may also be % ! line break
+\texttt{\textbackslash \meta{any single character}}, which allows all
+sorts of oddities (many built in to most \TeX{} macro sets, all the
+way up from the apparently simple `\csx{ }' meaning ``insert a space
+here'').
+
+Macro programming can be a complicated business, but at their very
+simplest they need little introduction~--- you'll hardly need to be
+told that:
+\begin{quote}
+\begin{verbatim}
+\def\foo{bar}
+\end{verbatim}
+\end{quote}
+replaces each instance of \csx{foo} with the text ``bar''. The
+command \csx{def} is \plaintex{} syntax for defining commands;
+\LaTeX{} offers a macro \csx{newcommand} that goes some way towards
+protecting users from themselves, but basically does the same thing:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\foo}{bar}
+\end{verbatim}
+\end{quote}
+Macros may have ``arguments'' , which are used to substitute for marked
+bits of the macro expansion:
+\begin{quote}
+\begin{verbatim}
+\def\foo#1{This is a #1 bar}
+...
+\foo{2/4}.
+\end{verbatim}
+\end{quote}
+which produces:
+\begin{quote}
+ This is a 2/4 bar.
+\end{quote}
+or, in \LaTeX{} speak:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\foo}[1]{This is a #1 bar}
+...
+\foo{3/4}.
+\end{verbatim}
+\end{quote}
+which produces:
+\begin{quote}
+ This is 3/4 bar.
+\end{quote}
+(\latex{} users waltz through life, perhaps?)
+
+You will have noticed that the arguments, above, were enclosed in
+braces (\texttt{\obracesymbol{}\dots{}\cbracesymbol{}}); this is the
+normal way of typing arguments, though \TeX{} is enormously flexible,
+and you may find all sorts of other ways of passing arguments (if you
+stick with it).
+
+Macro writing can get very complicated, very quickly. If you are a
+beginner \AllTeX{} programmer, you are well advised to read something
+along the lines of the \Qref*{\TeX{}book}{Q-tex-books}; once you're under
+way, \Qref*{\TeX{} by Topic}{Q-ol-books} is possibly a more satisfactory
+choice. Rather a lot of the answers in these \acro{FAQ}s tell you
+about various issues of how to write macros.
+\LastEdit{2011-10-12}
+
+\Question[Q-specials]{\csx{special} commands}
+
+\TeX{} provides the means to express things that device drivers can
+do, but about which \TeX{} itself knows nothing. For example, \TeX{}
+itself knows nothing about how to include \PS{} figures into
+documents, or how to set the colour of printed text; but some device
+drivers do.
+
+Instructions for such things are introduced to your document by means
+of \csx{special} commands; all that \TeX{} does with these commands is
+to expand their
+arguments and then pass the command to the \acro{DVI} file. In most
+cases, there are macro packages provided (often with the driver) that
+provide a human-friendly interface to the \csx{special}; for example,
+there's little point including a figure if you leave no gap for it in
+your text, and changing colour proves to be a particularly fraught
+operation that requires real wizardry. \LaTeXe{}
+has standard graphics and colour packages that make figure inclusion,
+rotation and scaling, and colour typesetting relatively
+straightforward, despite the rather daunting \csx{special} commands
+involved. (\CONTeXT{} provides similar support, though not by way of
+packages.)
+
+The allowable arguments of \csx{special} depend on the device driver
+you're using. Apart from the examples above, there are \csx{special}
+commands in the em\TeX{} drivers (e.g., \ProgName{dvihplj}, \ProgName{dviscr},
+\emph{etc}.)~that will draw lines at arbitrary orientations, and
+commands in \ProgName{dvitoln03} that permit the page to be set in
+landscape orientation.
+
+Note that \csx{special} behaves rather differently in \PDFTeX{}, since
+there is no device driver around. There \emph{is} a concept of
+\acro{PDF} specials, but in most cases \csx{special} will provoke a
+warning when used in \PDFTeX{}.
+\LastEdit{2011-10-15}
+
+\Question[Q-write]{Writing (text) files from \tex{}}
+
+\TeX{} allows you to write to output files from within your document.
+The facility is handy in many circumstances, but it is vital for
+several of the things \latex{} (and indeed almost any higher-level
+\tex{}-based macro package) does for you.
+
+The basic uses of writing to an external file are ``obvious''~---
+remembering titles of sections for a table of contents, remembering
+label names and corresponding section or figure numbers, all for a
+later run of your document. However, the ``non-obvious'' thing is
+easy to forget: that page numbers, in \tex{}, are slippery beasts, and
+have to be captured with some care. The trick is that \csx{write}
+operations are only executed as the page is sent to the \acro{DVI}
+or \acro{PDF} file. Thus, if you arrange that your page-number macro
+(\csx{thepage}, in \latex{}) is not expanded until the page is
+written, then the number written is correct, since that time is where
+\tex{} guarantees the page number tallies with the page being sent
+out.
+
+Now, there are times when you want to write something straight away:
+for example, to interact with the user. \TeX{} captures that
+requirement, too, with the primitive command \csx{immediate}:
+\begin{quote}
+\begin{verbatim}
+\immediate\write\terminal{I'm waiting...}
+\end{verbatim}
+\end{quote}
+writes a ``computer-irritates-user'' message, to the terminal.
+
+Which brings us to the reason for that \csx{terminal}. \TeX{} can
+``\csx{write}'' up to 16 streams simultaneously, and that argument to
+\csx{write} says which is to be used. Macro packages provide the
+means of allocating streams for your use: \plaintex{} provides a macro
+\csx{newwrite} (used as ``\csx{newwrite}\csx{streamname}'', which sets
+\csx{streamname} as the stream number). In fact, \csx{terminal} (or
+its equivalent) is the first output stream ever set up (in most macro
+packages): it is never attached to a file, and if \tex{} is asked to
+write to \emph{any} stream that isn't attached to a file it will send
+the output to the terminal (and the log).
+\LastEdit{2011-10-15}
+
+\Question[Q-spawnprog]{Spawning programs from \AllTeX{}: \csx{write18}}
+
+The \tex{} \Qref*{\csx{write} primitive instruction}{Q-write} is used
+to write to different file `streams'; TeX refers to each open file by
+a number, not by a file name (although most of the time we hide this).
+Originally, \tex{} would write to a file connected to a stream
+numbered 0--15. More recently, a special ``stream 18'' has been
+implemented: it is not writing to a file, but rather tells TeX to ask
+the operating system to do something. To run a command, we put it as
+the argument to \csx{write18}. So to run the \progname{epstopdf}
+utility on a file with name stored as \csx{epsfilename}, we would
+write:
+\begin{quote}
+\begin{verbatim}
+\write18{epstopdf \epsfilename}
+\end{verbatim}
+\end{quote}
+When using something like the \Package{epstopdf} package, the `stream'
+write operation is hidden away and you don't need to worry about the
+exact way it's done.
+
+However, there is a security issue. If you download some \alltex{} code from
+the Internet, can you be sure that there is not some command in it
+(perhaps in a hidden way) to do stuff that might be harmful to your
+computer (let's say: delete everything on the hard disk!)? In the
+face of this problem, both \miktex{} and \tex{}~Live have, for some
+time, disabled \csx{write18} by default. To turn the facility on,
+both distributions support an additional argument when starting \tex{}
+from the command shell:
+\begin{quote}
+\begin{verbatim}
+(pdf)(la)tex --shell-escape <file>
+\end{verbatim}
+\end{quote}
+The problem with this is that many people use \alltex{} via a graphical
+editor, so to use \csx{write18} for a file the editor's settings must
+be changed. Of course, the settings need restoring after the file is
+processed: you defeat the point of the original protection, that way.
+
+The latest \miktex{} (version 2.9), and recent \tex{}~Live (from the
+2010 release) get
+around this by having a special ``limited'' version of \csx{write18}
+enabled `out of the box'. The idea is to allow only a pre-set list of
+commands (for example, \BibTeX{}, \progname{epstopdf}, \tex{} itself,
+and so on). Those on the list are regarded as safe enough to allow,
+whereas anything else (for example deleting files) still needs to be
+authorised by the user. This seems to be a good balance: most people
+most of the time will not need to worry about \csx{write18} at all,
+but it will be available for things like \Package{epstopdf}.
+
+Note that the \tex{} system may tell you that the mechanism is in use:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010)
+ restricted \write18 enabled.
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+This is pdfTeX, Version 3.1415926-1.40.11
+ (TeX Live 2010)
+ restricted \write18 enabled.
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+when it starts.
+\begin{ctanrefs}
+\item[epstopdf.sty]Distributed with Heiko Oberdiek's packages
+ \CTANref{oberdiek}[epstopdf-pkg]
+\end{ctanrefs}
+\LastEdit{2012-12-03}
+
+\Question[Q-hyphen]{How does hyphenation work in \TeX{}?}
+
+Everyone knows what hyphenation is: we see it in most books we read,
+and (if we're alert) will spot occasional ridiculous mis-hyphenation
+(at one time, British newspapers were a fertile source).
+
+Hyphenation styles are culturally-determined, and the same language
+may be hyphenated differently in different countries~--- for example,
+British and American styles of hyphenation of English are very
+different. As a result, a typesetting system that is not restricted
+to a single language at a single locale needs to be able to change its
+hyphenation rules from time to time.
+
+\TeX{} uses a pretty good system for hyphenation (originally designed
+by Frank Liang~--- you may view his % ! line break
+\href{http://tug.org/docs/liang/}{Ph.D.\ thesis} online) and while
+it's capable of missing ``sensible'' hyphenation points, it seldom
+selects grossly wrong ones. The
+algorithm matches candidates for hyphenation against a set of
+``hyphenation patterns''. The candidates for hyphenation must be
+sequences of letters (or other single characters that \TeX{} may be
+persuaded to think of as letters). Non-letters interrupt hyphenation;
+this applies to \TeX{}'s \csx{accent} primitive (as in `syst\`eme')
+just as much as the exclamation in`syst!eme'.
+
+(Hyphenation takes place on the characters ``sent to the printer''.
+The problem with \csx{accent} is avoided~---in \latex{}~--- by the use
+of the \Package{fontenc} package, as discussed in % ! line break
+``\Qref*{Accented words aren t hyphenated}{Q-hyphenaccents}''.)
+
+Sets of hyphenation patterns are usually derived from analysis of
+a list of valid hyphenations (the process of derivation, using a tool
+called \Package{patgen}, is not ordinarily a sport to be played by
+ordinary mortals).
+
+The patterns for the languages a \TeX{} system is going to deal with
+may only be loaded when the system is installed. To change the set of
+hyphenation patterns recognised by a \tex{}-based or \xetex{} system,
+a \Qref*{partial reinstallation}{Q-newlang} is necessary (note that
+\Qref*{\luatex{}}{Q-luatex} relaxes this constraint).
+
+\TeX{} provides two ``user-level'' commands for control of
+hyphenation: \csx{language} (which selects a hyphenation style), and
+\csx{hyphenation} (which gives explicit instructions to the hyphenation
+engine, overriding the effect of the patterns).
+
+The ordinary \LaTeX{} user need not worry about \csx{language}, since
+it is very thoroughly managed by the \Package{babel} package; use of
+\csx{hyphenation} is discussed in
+\begin{wideversion}
+ the context of
+\end{wideversion}
+% beware line wrap
+\Qref[question]{hyphenation failure}{Q-nohyph}.
+\LastEdit{2012-12-03}
+
+\Question[Q-clsvpkg]{What are \LaTeX{} classes and packages?}
+
+\latex{} aims to be a general-purpose document processor. Such an aim
+could be achieved by a selection of instructions which would enable
+users to use \tex{} primitives, but such a procedure is considered too
+inflexible (and probably too daunting for ordinary users). Thus the
+designers of \latex{} created a model which offered an
+\emph{abstraction} of the design of documents. Obviously, not all
+documents can look the same (even with the defocussed eye of
+abstraction), so the model uses \emph{classes} of document. Base
+\latex{} offers five classes of document: \Class{book},
+\Class{report}, \Class{article} and \Class{letter}.
+For each class, \latex{} provides a \emph{class file}; the user
+arranges to use it via a \csx{documentclass} command at the top of the
+document. So a document starting
+\begin{quote}
+ \cmdinvoke{documentclass}{article}
+\end{quote}
+may be called ``an \emph{article} document''.
+
+This is a good scheme, but it has a glaring flaw: the actual
+typographical designs provided by the \latex{} class files aren't
+widely liked. The way around this is to \emph{refine} the class. To
+refine a class, a programmer may write a new class file that loads an
+existing class, and then does its own thing with the document design.
+
+If the user finds such a refined class, all is well, but if not, the
+common way is to load a \emph{package} (or several).
+
+The \latex{} distribution, itself, provides rather few package files,
+but there are lots of them, by a wide variety of authors, to be found
+on the archives. Several packages are designed just to adjust the
+design of a document~--- using such packages achieves what the
+programmer might have achieved by refining the class.
+
+Other packages provide new facilities: for example, the
+\Package{graphics} package (actually provided as part of any \latex{}
+distribution) allows the user to load externally-provided graphics
+into a document, and the \Package{hyperref} package enables the user
+to construct hyper-references within a document.
+
+On disc, class and package files only appear different by virtue of
+their name ``extension''~--- class files are called \File{*.cls} while
+package files are called \File{*.sty}. Thus we find that the \LaTeX{}
+standard \Class{article} class is represented on disc by a file called
+\File{article.cls}, while the \Package{hyperref} package is
+represented on disc by a file called \File{hyperref.sty}.
+
+The class vs.~package distinction was not clear in \LaTeXo{}~---
+everything was called a style (``document style'' or ``document style
+option''). It doesn't really matter that the nomenclature has
+changed: the important requirement is to understand what other people
+are talking about.
+\LastEdit{2013-10-21}
+
+\Question[Q-whatenv]{What are \latex{} ``environments''}
+
+While \tex{} makes direct provision for commands, \latex{} adds a
+concept of ``environment''; environments perform an action on a block
+(of something or other) rather than than just doing something at one
+place in your document.
+
+A totally trivial environment could change the font in use for a chunk
+of text, as
+\begin{quote}
+\begin{verbatim}
+\newenvironment{monoblock}%
+ {\ttfamily}%
+ {}
+\end{verbatim}
+\end{quote}
+which defines a \environment{monoblock} which may be used as
+\begin{quote}
+\begin{verbatim}
+\begin{monoblock}
+ some text set in monospace
+\end{monoblock}
+\end{verbatim}
+\end{quote}
+which will look like:
+\begin{quote}
+ \texttt{some text set in monospace}
+\end{quote}
+so it is a particularly simple example. A rather complicated
+environment is introduced by \cmdinvoke{begin}{document}; it looks
+simple, but needs all sorts of special \tex{} code to make it work
+`transparently'; most environments are more elaborate than
+\environment{monoblock} and \emph{much} simpler than
+\environment{document}.
+
+An environment puts its content inside a \tex{} \emph{group}, so that
+commands used inside the environment don't `leak out'~--- the
+\environment{monoblock} environment, above, restricts its effect to
+its own contents (the stuff between the \cmdinvoke{begin}{monoblock}
+and \cmdinvoke{end}{monoblock}), which is just what you need for this
+sort of thing.
+
+So that's ``simple'' environments; the \environment{monoblock}, above
+doesn't actually gain us much over
+\begin{quote}
+\begin{verbatim}
+{\ttfamily some text set in monospace}
+\end{verbatim}
+\end{quote}
+though in fact many useful environments are just as simple (to look
+at). Some, such as \environment{verbatim}, look simple but are
+actually very tricky inside.
+
+\latex{} also allows arguments to an environment:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{fontblock}[1]%
+ {#1\selectfont}%
+ {}
+\end{verbatim}
+\end{quote}
+and use of \environment{fontblock} as:
+\begin{quote}
+\begin{verbatim}
+\begin{fontblock}{\ttfamily}
+\end{verbatim}
+\end{quote}
+would produce the same effect as the \environment{monoblock}
+environment.
+
+Environments may also have optional arguments, in much the same way as
+commands:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{normaltext}[1][\itshape]%
+ {#1}%
+ {}
+\end{verbatim}
+\end{quote}
+which will ordinarily set its body in italic, but
+\begin{quote}
+\begin{verbatim}
+\begin{normaltext}[\ttfamily]
+ ...
+\end{normaltext}
+\end{verbatim}
+\end{quote}
+will observe its optional argument, and behave the same as the
+\environment{monoblock} we started with.
+
+Note that an environments argument(s) (mandatory or optional) are
+\emph{not} passed to the `\csx{end}' text of the environment~--- that
+is specified as a macro with no arguments, so that
+\begin{quote}
+\begin{verbatim}
+\newenvironment{normaltext}[1][\itshape]%
+ {#1}%
+ {\typeout{what was #1, again?}
+\end{verbatim}
+\end{quote}
+produces an error message
+\begin{quote}
+\begin{verbatim}
+! Illegal parameter number in definition of \endnormaltext.
+\end{verbatim}
+\end{quote}
+So, if you need to pass an environment argument to the end-code, you
+have to wrap it in a macro of its own:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{normaltext}[1][Intro]%
+ {#1%
+ \newcommand{\foo}{#1}}%
+ {\typeout{what was \foo{}, again?}
+\end{verbatim}
+\end{quote}
+\LastEdit*{2013-02-20}
+
+\Question[Q-dtx]{Documented \LaTeX{} sources (\extension{dtx} files)}
+
+\LaTeXe{}, and many contributed \latex{} macro packages, are written
+in a \Qref*{literate programming style}{Q-lit}, with source and
+documentation in the
+same file. This format in fact originated before the
+days of the \LaTeX{} project as one of the ``Mainz'' series of
+packages. A documented source file conventionally has the suffix
+\extension{dtx}, and will normally be `stripped' before use with
+\LaTeX{}; an installation (\extension{ins}) file is normally provided,
+to automate this process of removing comments for speed of loading.
+If the \extension{ins} file is available, you may process \emph{it}
+with \latex{} to produce the package (and, often, auxiliary files).
+
+Output should look something like:
+\begin{quote}
+\begin{verbatim}
+Generating file(s) ./foo.sty
+
+Processing file foo.dtx (package) -> foo.sty
+File foo.dtx ended by \endinput.
+Lines processed: 2336
+Comments removed: 1336
+Comments passed: 2
+Codelines passed: 972
+\end{verbatim}
+\end{quote}
+The lines ``\texttt{Processing \dots{}\ ended by \csx{endinput}}'' may
+be repeated if the \extension{dtx} file provides more than one
+`unpacked' file.
+
+To read the comments ``as a document'', you can run \LaTeX{} on the
+\extension{dtx} file to produce a nicely formatted version of the
+documented code. (Most \latex{} packages on \ctan{}, nowadays, already
+have \acro{PDF} of the result of processing the \extension{dtx} file,
+as ``documentation''.)
+
+Several packages may be included in one \extension{dtx} file, with
+conditional sections, and there are facilities for indexes of macros,
+etc. All of this m\'elange is sorted out by directives in the
+\extension{ins} file; conventional indexing utilities may be necessary
+for ``full'' output.
+
+Anyone may write \extension{dtx} files; the format is explained in
+\Qref*{The \LaTeX{} Companion}{Q-latex-books}, and a tutorial is available
+from \acro{CTAN} (which comes with skeleton \extension{dtx} and
+\extension{ins} files).
+
+Composition of \extension{dtx} files is supported in \ProgName{emacs} by
+\Qref*{\acro{AUC}-\TeX{}}{Q-editors}.
+
+The (unix-based) script \ProgName{dtxgen} generates a proforma basic
+\extension{dtx} file, which could be useful when starting a new
+project.
+
+Another route to an \extension{dtx} file is to write the
+documentation and the code separately, and then to combine them using
+the \ProgName{makedtx} system. This technique has particular value in
+that the documentation file can be used separately to generate
+\acro{HTML} output; it is often quite difficult to make % ! line break
+\Qref*{\LaTeX{} to \acro{HTML} conversion}{Q-LaTeX2HTML} tools deal
+with \extension{dtx} files, since they use an unusual class file.
+
+The \ProgName{sty2dtx} system goes one step further: it attempts to
+create a \extension{dtx} file from a `normal' \extension{sty} file
+with comments. It works well, in some circumstances, but can become
+confused by comments that aspire to ``structure'' (e.g., tabular
+material, as in many older packages' file headers).
+
+The \extension{dtx} files are not used by \LaTeX{} after they have been
+processed to produce \extension{sty} or \extension{cls} (or whatever)
+files. They need not be kept with the working system; however, for
+many packages the \extension{dtx} file is the primary source of
+documentation, so you may want to keep \extension{dtx} files elsewhere.
+
+An interesting sideline to the story of \extension{dtx} files is the
+\Package{docmfp} package, which extends the model of the \Package{doc}
+package to
+\begin{flatversion}
+ \MF{} and \MP{} (\Qref[see questions]{}{Q-MF} and \Qref[\nothtml]{}{Q-MP})
+\end{flatversion}
+\begin{hyperversion}
+ \Qref{\MF{}}{Q-MF} and \Qref{\MP{}}{Q-MP},
+\end{hyperversion}
+thus permitting documented distribution of bundles containing code for
+\MF{} and \MP{} together with related \LaTeX{} code.
+\begin{ctanrefs}
+\item[AUC-TeX]\CTANref{auctex}
+\item[clsguide.pdf]\CTANref{clsguide}
+\item[docmfp.sty]\CTANref{docmfp}
+\item[docstrip.tex]Part of the \LaTeX{} distribution
+\item[DTX tutorial]\CTANref{dtxtut}
+\item[dtxgen]\CTANref{dtxgen}
+\item[makedtx]\CTANref{makedtx}
+\item[sty2dtx]\CTANref{sty2dtx}
+\end{ctanrefs}
+\LastEdit{2014-06-03}
+
+\Question[Q-whatenc]{What are encodings?}
+
+Let's start by defining two concepts, the \emph{character} and the
+\emph{glyph}.
+The character is the abstract idea of the `atom' of a
+language or other dialogue: so it might be a letter in an alphabetic
+language, a syllable in a syllabic language, or an ideogram in an
+ideographic language. The glyph is the mark created on screen or
+paper which represents a character. Of
+course, if reading is to be possible, there must be some agreed
+relationship between the glyph and the character, so while the precise
+shape of the glyph can be affected by many other factors, such as the
+capabilities of the writing medium and the designer's style, the
+essence of the underlying character must be retained.
+
+Whenever a computer has to represent characters, someone has to define
+the relationship between a set of numbers and the characters they
+represent. This is the essence of an encoding: it is a mapping
+between a set of numbers and a set of things to be represented.
+
+\TeX{} of course deals in encoded characters all the time: the
+characters presented to it in its input are encoded, and it emits
+encoded characters in its \acro{DVI} or \acro{PDF} output. These
+encodings have rather different properties.
+
+The \TeX{} input stream was pretty unruly back in the days when Knuth
+first implemented the language. Knuth himself prepared documents on
+terminals that produced all sorts of odd characters, and as a result
+\TeX{} contains some provision for translating its input (however
+encoded) to something regular. Nowadays,
+the operating system translates keystrokes into a code appropriate for
+the user's language: the encoding used is usually a national or
+international standard, though some operating systems use ``code
+pages'' (as defined by Microsoft). These standards and code pages often
+contain characters that may not appear in the \TeX{} system's input
+stream. Somehow, these characters have to be dealt with~--- so
+an input character like ``\'e'' needs to be interpreted by \TeX{} in
+a way that that at least mimics the way it interprets ``\csx{'}\texttt{e}''.
+
+The \TeX{} output stream is in a somewhat different situation:
+characters in it are to be used to select glyphs from the fonts to be
+used. Thus the encoding of the output stream is notionally a font
+encoding (though the font in question may be a
+% beware line break (twice)
+\nothtml{virtual one~--- see }%
+\Qref[question]{virtual font}{Q-virtualfonts}). In principle, a
+fair bit of what appears in the output stream could be direct
+transcription of what arrived in the input, but the output stream
+also contains the product of commands in the input, and translations
+of the input such as ligatures like %
+\texttt{fi}\nothtml{\ensuremath\Rightarrow``fi''}.
+
+Font encodings became a hot topic when the
+\Qref*{Cork encoding}{Q-ECfonts}
+appeared, because of the possibility of suppressing
+\csx{accent} commands in the output stream (and hence improving the
+quality of the hyphenation of text in inflected languages, which is
+interrupted by the \csx{accent} commands~--- see
+% beware line break
+\Qref[question]{``how does hyphenation work''}{Q-hyphen}).
+To take advantage of the diacriticised characters represented in the
+fonts, it is necessary to arrange that whenever the
+command sequence ``\csx{'}\texttt{e}'' has been input
+(explicitly, or implicitly via the sort of mapping of input mentioned
+above), the character that codes the position of the ``\'e'' glyph is
+used.
+
+Thus we could have the odd arrangement that the diacriticised character in
+the \TeX{} input stream is translated into \TeX{} commands that would
+generate something looking like the input character; this sequence of
+\TeX{} commands is then translated back again into a single
+diacriticised glyph as the output is created. This is in fact
+precisely what the \LaTeX{} packages \Package{inputenc} and
+\Package{fontenc} do, if operated in tandem on (most) characters in
+the \acro{ISO}~Latin-1 input encoding and the \acro{T}1 font encoding.
+At first sight, it seems eccentric to have the first package do a thing, and
+the second precisely undo it, but it doesn't always happen that way:
+most font encodings can't match the corresponding input encoding
+nearly so well, and the two packages provide the sort of symmetry the
+\LaTeX{} system needs.
+
+\Question[Q-ECfonts]{What are the \acro{EC} fonts?}
+
+A font provides a number of \emph{glyphs}. In order that the glyphs
+may be printed, they are \Qref*{\emph{encoded}}{Q-whatenc}, and the
+encoding is used as an index into tables within the font. For various
+reasons, Knuth chose deeply eccentric encodings for his Computer
+Modern family of fonts; in particular, he chose different encodings
+for different fonts, so that the application using the fonts has to
+remember which font of the family it's using before selecting a
+particular glyph.
+
+When \TeX{} version 3 arrived, most of the drivers for the
+eccentricity of Knuth's encodings went away, and at \acro{TUG}'s Cork
+meeting, an encoding for a set of 256 glyphs, for use in \TeX{} text,
+was defined. The intention was that these glyphs should cover `most'
+European languages that use Latin alphabets, in the sense of including
+all accented letters needed. (Knuth's \acro{CMR} fonts missed things
+necessary for Icelandic and Polish, for example, which the Cork fonts
+do have, though even Cork encoding's coverage isn't complete.)
+\latex{} refers to the Cork encoding as \acro{T}1, and provides the
+means to use fonts thus encoded to avoid problems with the interaction
+of accents and hyphenation % ! line break
+(see \Qref[question]{hyphenation of accented words}{Q-hyphenaccents}).
+
+The first \MF{}-fonts to conform to the Cork encoding were the \acro{EC}
+fonts. They look \acro{CM}-like, though their metrics differ from \acro{CM}-font
+metrics in several areas. They have long been regarded as `stable' (in
+the same sense that the \acro{CM} fonts are stable: their metrics are
+unlikely ever to change). Each \acro{EC} font is, of course, roughly twice the
+size of the corresponding \acro{CM} font, and there are far more of them than
+there are CM fonts. The simple number of fonts proved problematic in
+the production of Type~1 versions of the fonts, but \acro{EC} or
+\acro{EC}-equivalent fonts in Type~1 or TrueType form (the latter only from
+\begin{wideversion}
+ \Qref{commercial suppliers}{Q-commercial}).
+\end{wideversion}
+\begin{narrowversion}
+ % ( <- paren matching
+ commercial suppliers~--- \Qref{question}{Q-commercial}).
+\end{narrowversion}
+Free \Qref*{auto-traced versions}{Q-textrace}~--- the \acro{CM}-super and
+the \acro{LGC} fonts, and the Latin Modern series (rather directly generated
+from Metafont sources), are available.
+
+Note that the Cork encoding doesn't cover mathematics (so that no
+``T1-encoded'' font families can not support it). If you're using
+Computer-Modern-alike fonts, this doesn't actually matter: your system
+will have the original Computer Modern mathematical fonts (or the
+those distributed with the Latin Modern set), which cover `basic' \TeX{}
+mathematics; more advanced mathematics are likely to need separate
+fonts anyway. Suitable mathematics fonts for use with other font
+families are discussed in % ! line break
+``\Qref*{choice of scalable fonts}{Q-psfchoice}''.
+
+The \acro{EC} fonts are distributed with a set of `Text Companion' (\acro{TC}) fonts
+that provide glyphs for symbols commonly used in text. The \acro{TC} fonts
+are encoded according to the \latex{} \acro{TS}1 encoding, and are not
+necessarily as `stable' are the \acro{EC} fonts are. Note that modern
+distributions tend not to distribute the \acro{EC} fonts in outline format, but
+rather to provide Latin Modern for \acro{T}1-encoded Computer Modern-style
+fonts. This can sometimes cause confusion when users are recompiling
+old documents.
+
+The Cork encoding is also implemented by virtual fonts provided in the
+\acro{PSNFSS} system, for Adobe Type 1 fonts, and also by most other such
+fonts that have been developed (or otherwise made available) for use
+with \alltex{}.
+
+Note that \acro{T}1 (and other eight-bit font encodings) are superseded in
+the developing \TeX{}-family members \Qref*{\xetex{}}{Q-xetex} and
+\Qref*{\luatex{}}{Q-luatex}, which use Unicode as their base encoding,
+and use Unicode-encoded fonts (typically in \FontFormat{ttf} or
+\FontFormat{otf} formats). The \Package{cm-unicode} fonts carry the
+flag in this arena, along with the Latin Modern set.
+\begin{ctanrefs}
+\item[CM-super fonts]\CTANref{cm-super}
+\item[CM-LGC fonts]\CTANref{cm-lgc}
+\item[CM unicode fonts]\CTANref{cm-unicode}
+\item[EC and TC fonts]\CTANref{ec}
+\item[Latin Modern fonts]\CTANref{lm}
+\end{ctanrefs}
+
+\Question[Q-unicode]{Unicode and \tex{}}
+
+Unicode is a character code scheme that has the capacity to express
+the text of the languages of the world, as well as important symbols
+(including mathematics). Any coding scheme that is directly
+applicable to \tex{} may be expressed in single bytes (expressing up
+to 256 characters); Unicode characters may require several bytes, and
+the scheme may express a very large number of characters.
+
+For ``old-style'' applications (\tex{} or \pdftex{}) to deal with
+Unicode input, the sequence of bytes to make up Unicode character are
+processed by a set of macros that deliver a glyph number in an
+appropriate font. The macros that read these bytes is complicated,
+and manifests as \pkgoption{utf8} option for the \latex{} distribution
+\Package{inputenc} package; the coverage of that option is limited to
+Unicode characters that can be represented using ``\latex{} standard
+encodings''. The separate package \Package{ucs} provides wider, but
+less robust, coverage via an \Package{inputenc} option
+\pkgoption{utf8x}. As a general rule, you should never use
+\pkgoption{utf8x} until you have convinced yourself that
+\pkgoption{utf8} can not do the job for you.
+
+`Modern' \tex{}-alike applications, \Qref*{\xetex{}}{Q-xetex} and
+\Qref*{\luatex{}}{Q-luatex} read their input using \acro{UTF}-8
+representations of Unicode as standard. They also use TrueType or
+OpenType fonts for output; each such font has tables that tell the
+application which part(s) of the Unicode space it covers; the tables
+enable the engines to decide which font to use for which character
+(assuming there is any choice at all).
+\begin{ctanrefs}
+\item[inputenc.sty]Part of the \CTANref{latex} distribution
+\item[ucs.sty]\CTANref{ucs}
+\end{ctanrefs}
+\LastEdit{2012-04-20}
+
+\Question[Q-tds]{What is the \acro{TDS}?}
+
+\acro{TDS} is an acronym for ``\TeX{} Directory Structure''; it
+specifies a standard way of organising all the \TeX{}-related files on
+a computer system.
+
+Most modern distributions arrange their \tex{} files in conformance
+with the \acro{TDS}, using both a `distribution' directory tree and a
+(set of) `local' directory trees, each containing \TeX{}-related
+files. The \acro{TDS} recommends the name \texttt{texmf} for the name
+of the root directory (folder) of an hierarchy; in practice there are
+typically several such trees, each of which has a name that compounds
+that (e.g., \texttt{texmf-dist}, \texttt{texmf-var}).
+
+Files supplied as part of the distribution are put into the
+distribution's tree, but the location of the distribution's hierarchy is
+system dependent. (On a Unix system it might be at
+\path{/usr/share/texmf} or \path{/opt/texmf}, or a similar location.)
+
+There may be more than one `local' hierarchy in which additional files
+can be stored. An installation will also typically offer a local
+hierarchy, while each user may have an individual local hierarchy.
+
+The \acro{TDS} itself is published as the output of a \acro{TUG} % ! line break
+\Qref*{Technical Working Group}{Q-TUG*}. You may browse an
+\href{http://tug.org/tds/}{on-line version} of the standard, and
+copies in several other formats (including source) are available on
+\acro{CTAN}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\acro{TDS} specification]\CTANref{tds}
+\end{ctanrefs}
+
+\Question[Q-eps]{What is ``Encapsulated \PS{}'' (``\acro{EPS}'')?}
+
+\PS{} has been for many years a \emph{lingua franca} of powerful
+printers (though modern high-quality printers now tend to require some
+constrained form of Adobe Acrobat, instead); since \PS{} is also a
+powerful graphical programming language, it is commonly used as an
+output medium for drawing (and other) packages.
+
+However, since \PS{} \emph{is} such a powerful language, some
+rules need to be imposed, so that the output drawing may be included
+in a document as a figure without ``leaking'' (and thereby destroying
+the surrounding document, or failing to draw at all).
+
+Appendix \acro{H} of the \PS{} Language Reference Manual (second
+and subsequent editions), specifies a set of rules for \PS{} to
+be used as figures in this way. The important features are:
+\begin{itemize}
+\item certain ``structured comments'' are required; important ones are
+ the identification of the file type, and information about the
+ ``bounding box'' of the figure (i.e., the minimum rectangle
+ enclosing it);
+\item some commands are forbidden~--- for example, a \texttt{showpage}
+ command will cause the image to disappear, in most \TeX{}-output
+ environments; and
+\item ``preview information'' is permitted, for the benefit of things
+ such as word processors that don't have the ability to draw
+ \PS{} in their own right~--- this preview information may be in
+ any one of a number of system-specific formats, and any viewing
+ program may choose to ignore it.
+\end{itemize}
+A \PS{} figure that conforms to these rules is said to be in
+``Encapsulated \PS{}'' (\acro{EPS}) format. Most \AllTeX{} packages for
+including \PS{} are structured to use Encapsulated \PS{};
+which of course leads to much hilarity as exasperated \AllTeX{} users
+struggle to cope with the output of drawing software whose authors
+don't know the rules.
+
+\Question[Q-adobetypen]{Adobe font formats}
+\keywords{type1 type3}
+
+Adobe has specified a number of formats for files to represent fonts
+in \PS{} files; this question doesn't attempt to be encyclopaedic, so
+we only discuss the two formats most commonly encountered in the
+\AllTeX{} context, types~1 and 3. In particular, we don't discuss the
+OpenType format, whose many advantages now becoming accessible to most
+\AllTeX{} users (by means of
+\begin{hyperversion}
+ the widely-used \Qref{\xetex{}}{Q-xetex} and the more experimental
+ \Qref{\LuaTeX{}}{Q-luatex}).
+\end{hyperversion}
+\begin{flatversion}
+ the widely-used \xetex{}~--- see \Qref[question]{}{Q-xetex}~--- and
+ the more experimental \LuaTeX{}~--- see \Qref[question]{}{Q-luatex}).
+\end{flatversion}
+
+Adobe Type~1 format specifies a means to represent outlines of the glyphs
+in a font. The `language' used is closely restricted, to ensure that
+the font is rendered as quickly as possible. (Or rather, as quickly
+as possible with Adobe's technology at the time the specification was
+written: the structure could well be different if it were specified
+now.) The format has long been the basis of the digital type-foundry
+business, though nowadays most new fonts are released in OpenType format.
+
+%% Type~1 fonts are directly supported by some operating system software,
+%% and at least one \TeX{} system, the commercial % line break!
+%% \Qref*{\YandY{} system}{Q-commercial}, bases its entire
+%% operation on the use of Type~1 fonts.
+
+In the \AllTeX{} context, Type~1 fonts are extremely important. Apart
+from their simple
+availability (there are thousands of commercial Type~1 text fonts around), the
+commonest reader for \acro{PDF} files has long (in effect) \emph{insisted} on
+their use (see below).
+
+Type~3 fonts have a more forgiving specification. A wide range of
+\PS{} operators is permissible, including bitmap specifiers. Type~3
+is therefore the natural format to be used for programs such as
+\ProgName{dvips} when they auto-generate something to represent
+\MF{}-generated fonts in a \PS{} file. It's Adobe Acrobat Viewer's
+treatment of bitmap Type~3 fonts that has made direct \MF{} output
+increasingly unattractive, in recent years. If you have a \acro{PDF}
+document in which the text looks fuzzy and uneven in Acrobat Reader,
+ask Reader for the \texttt{File}\arrowhyph{}%
+\texttt{Document Properties}\arrowhyph{}%
+\texttt{Fonts ...}, and it will likely show some font or other as
+``Type~3'' (usually with encoding ``Custom''). The problem has
+disappeared with version 6 of Acrobat Reader. See % line break
+\Qref[question]{\acro{PDF} quality}{Q-dvips-pdf} for a discussion of
+the issue, and for ways of addressing it.
+
+Type~3 fonts should not entirely be dismissed, however. Acrobat
+Reader's failure with them is entirely derived from its failure to use
+the anti-aliasing techniques common in \TeX{}-ware. Choose a
+different set of \PS{} graphical operators, and you can make pleasing
+Type~3 fonts that don't ``annoy'' Reader. For example, you may not
+change colour within a Type~1 font glyph, but there's no such
+restriction on a Type~3 font, which opens opportunities for some
+startling effects.
+
+\Question[Q-resolns]{What are ``resolutions''?}
+
+``Resolution'' is a word that is used with little concern for its
+multiple meanings, in computer equipment marketing. The word suggests
+a measure of what an observer (perhaps the human eye) can resolve; yet
+we regularly see advertisements for printers whose resolution is
+1200dpi~--- far finer than the unaided human eye can distinguish. The
+advertisements are talking about the precision with which the printer
+can place spots on the printed image, which affects the fineness of
+the representation of fonts, and the accuracy of the placement of
+glyphs and other marks on the page.
+
+In fact, there are two sorts of ``resolution'' on the printed page
+that we need to consider for \AllTeX{}'s purposes:
+\begin{itemize}
+\item the positioning accuracy, and
+\item the quality of the fonts.
+\end{itemize}
+In the case where \AllTeX{} output is being sent direct to a printer,
+in the printer's ``native'' language, it's plain that the \acro{DVI}
+processor must know all such details, and must take detailed account
+of both types of resolution.
+
+In the case where output is being sent to an intermediate distribution
+format, that has potential for printing (or displaying) we know not
+where, the final translator, that connects to directly to the printer
+or display, has the knowledge of the device's properties: the
+\acro{DVI} processor need not know, and should not presume to guess.
+
+Both \PS{} and \acro{PDF} output are in this category. While \PS{} is
+used less frequently for document distribution nowadays, it is
+regularly used as the source for distillation into \acro{PDF}; and
+\acro{PDF} is the workhorse of an enormous explosion of document
+distribution.
+
+Therefore, we need \acro{DVI} processors that will produce
+``resolution independent'' \PS{} or \acro{PDF} output; of course, the
+independence needs to extend to both forms of independence outlined
+above.
+
+Resolution-independence of fonts was for a long time forced upon the
+world by the feebleness of Adobe's \ProgName{Acrobat}
+\ProgName{Reader} at dealing with bitmap files: a sequence of answers
+starting with one aiming at the % ! line break
+\Qref*{quality of \acro{PDF} from \PS{}}{Q-dvips-pdf} addresses
+the problems that arise.
+
+Resolution-independence of positioning is more troublesome:
+\ProgName{dvips} is somewhat notorious for insisting on positioning to
+the accuracy of the declared resolution of the printer.
+One commonly-used approach is to declare a resolution of 8000 (``better
+than any device''), and this is reasonably successful though it does
+have its \Qref*{problems}{Q-8000}.
+
+\Question[Q-fontname]{What is the ``Berry naming scheme''?}
+
+In the olden days, \AllTeX{} distributions were limited by the
+feebleness of file systems' ability to represent long names. (The
+\MSDOS{} file system was a particular bugbear: fortunately any current
+Microsoft system allows rather more freedom to specify file names.
+Sadly, the ISO~9660 standard for the structure of \CDROM{}s has a
+similar failing, but that too has been modified by various extension
+mechanisms.)
+
+One area in which these short file names posed a particular problem
+was that of file names for Type~1 fonts.
+These fonts are distributed by their vendors with
+pretty meaningless short names, and there's a natural ambition to
+change the name to something that identifies the font somewhat
+precisely. Unfortunately, names such as ``BaskervilleMT'' are
+already far beyond the abilities of the typical feeble file system,
+and add the specifier of a font shape or variant, and the difficulties
+spiral out of control. Font companies deal with the issue by
+inventing silly names, and providing a map file to show what the
+``real'' names. Thus the Monotype Corporation provides the
+translations:
+\begin{quote}
+ \texttt{bas\_\_\_\_\_ BaskervilleMT}\\
+ \texttt{basb\_\_\_\_ BaskervilleMT-Bold}\\
+ \texttt{basbi\_\_\_ BaskervilleMT-BoldItalic}
+\end{quote}
+and so on. These names could be used within \AllTeX{} programs,
+except that they are not unique: there's nothing to stop Adobe using
+`\texttt{bas\_\_\_\_\_}' for \emph{their} Baskerville font.
+
+Thus arose the Berry naming scheme.
+
+The basis of the scheme is to encode the meanings of the various parts
+of the file's specification in an extremely terse way, so that enough
+font names can be expressed even in impoverished file name-spaces. The
+encoding allocates one character to the font ``foundry'' (Adobe, Monotype,
+and so on), two to the typeface name (Baskerville, Times Roman, and so
+on), one to the weight, shape, and encoding and so on.
+
+The whole scheme is outlined in the \Package{fontname} distribution,
+which includes extensive documentation and a set of tables of fonts
+whose names have been systematised.
+\begin{ctanrefs}
+\item[fontname distribution]\CTANref{fontname}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-docs.tex b/help/uk-tex-faq/faq-docs.tex
new file mode 100644
index 0000000000..dbbdeb37c5
--- /dev/null
+++ b/help/uk-tex-faq/faq-docs.tex
@@ -0,0 +1,1305 @@
+% $Id: faq-docs.tex,v 1.46 2014/03/04 15:42:45 rf10 Exp rf10 $
+
+\section{Documentation and Help}
+
+\Question[Q-book-lists]{Books relevant to \tex{} and friends}
+
+There are too many books for them all to appear in a single list, so
+the following answers aim to cover ``related'' books, with subject
+matter as follows:
+\begin{itemize}
+\item \Qref*{\tex{} itself and \plaintex{}}{Q-tex-books}
+\item \Qref*{\latex{}}{Q-latex-books}
+\item \Qref*{Books on other \tex{}-related matters}{Q-other-books}
+\item \Qref*{Books on Type}{Q-type-books}
+\end{itemize}
+
+These lists only cover books in English: notices of new books, or
+warnings that books are now out of print are always welcome. However,
+these \acro{FAQ}s do \emph{not} carry reviews of current published
+material.
+\LastEdit*{2011-06-01}
+
+\Question[Q-tex-books]{Books on \TeX{}, \plaintex{} and relations}
+\AliasQuestion{Q-books}
+
+While Knuth's book is the definitive reference for both \TeX{} and
+\plaintex{}, there are many books covering these topics:
+\begin{booklist}
+\item[The \TeX{}book]by Donald Knuth (Addison-Wesley, 1984,
+ \ISBN{0-201-13447-0}, paperback \ISBN{0-201-13448-9})
+\item[A Beginner's Book of \TeX{}]by Raymond Seroul and Silvio Levy,
+ (Springer Verlag, 1992, \ISBN{0-387-97562-4})
+\item[\TeX{} by Example: A Beginner's Guide]by Arvind Borde
+ (Academic Press, 1992, \ISBN{0-12-117650-9}~--- now out of print)
+\item[Introduction to \TeX{}]by Norbert Schwarz (Addison-Wesley,
+ 1989, \ISBN{0-201-51141-X}~--- now out of print)
+\item[A \plaintex{} Primer]by Malcolm Clark (Oxford University
+ Press, 1993, ISBNs~0-198-53724-7 (hardback) and~0-198-53784-0
+ (paperback))
+\item[A \TeX{} Primer for Scientists]by Stanley Sawyer and Steven
+ Krantz (CRC Press, 1994, \ISBN{0-849-37159-7})
+\item[\TeX{} by Topic]by Victor Eijkhout (Addison-Wesley, 1992,
+ \ISBN{0-201-56882-9}~--- now out of print, but see
+ \Qref[question]{online books}{Q-ol-books}; you can also now buy a copy
+ printed, on demand, by Lulu~--- see
+ \url{http://www.lulu.com/content/2555607})
+\item[\TeX{} for the Beginner]by Wynter Snow (Addison-Wesley, 1992,
+ \ISBN{0-201-54799-6})
+\item[\TeX{} for the Impatient]by Paul W.~Abrahams, Karl Berry and
+ Kathryn A.~Hargreaves (Addison-Wesley, 1990,
+ \ISBN{0-201-51375-7}~--- now out of print, but see
+ \Qref[question]{online books}{Q-ol-books})
+\item[\TeX{} in Practice]by Stephan von Bechtolsheim (Springer
+ Verlag, 1993, 4 volumes, \ISBN{3-540-97296-X} for the set, or
+% nos in comments are for German distribution (Springer Verlag, Berlin)
+ Vol.~1: \ISBN{0-387-97595-0}, % (3-540-97595-0)
+ Vol.~2: \ISBN{0-387-97596-9}, % (3-540-97596-9)
+ Vol.~3: \ISBN{0-387-97597-7}, and % (3-540-97597-7)
+ Vol.~4: \ISBN{0-387-97598-5})% (3-540-97598-5)
+\begin{typesetversion}
+\item[\TeX{}: Starting from \sqfbox{1}\,\footnotemark]%
+\footnotetext{That's `Starting from Square One'}%
+\end{typesetversion}
+\begin{htmlversion}
+\item[\TeX{}: Starting from Square One]
+\end{htmlversion}
+ by Michael Doob (Springer
+ Verlag, 1993, \ISBN{3-540-56441-1}~--- now out of print)
+\item[The Joy of \TeX{}]by Michael D.~Spivak (second edition,
+ \acro{AMS}, 1990, \ISBN{0-821-82997-1})
+\item[The Advanced \TeX{}book]by David Salomon (Springer Verlag, 1995,
+ \ISBN{0-387-94556-3})
+\end{booklist}
+A collection of Knuth's publications about typography is also available:
+\begin{booklist}
+\item[Digital Typography]by Donald Knuth (CSLI and Cambridge
+ University Press, 1999, \ISBN{1-57586-011-2}, paperback
+ \ISBN{1-57586-010-4}).
+\end{booklist}
+\nothtml{\noindent}and in late 2000, a ``Millennium Boxed Set'' of all
+5 volumes of Knuth's ``Computers and Typesetting'' series (about
+\TeX{} and \MF{}) was published by Addison Wesley:
+\begin{booklist}
+\item[Computers \& Typesetting, Volumes A--E Boxed Set]by Donald Knuth
+ (Addison-Wesley, 2001, \ISBN{0-201-73416-8}).
+\end{booklist}
+\checked{rf}{2000/02/12 -- http://cseng.aw.com/book/0,3828,0201734168,00.html}
+\LastEdit*{2011-06-01}
+
+\Question[Q-latex-books]{Books on \latex{}}
+
+\begin{booklist}
+\item[\LaTeX{}, a Document Preparation System]by Leslie Lamport
+ (second edition, Addison Wesley, 1994, \ISBN{0-201-52983-1})
+\item[Guide to \LaTeX{}]Helmut Kopka and Patrick W.~Daly (fourth
+ edition, Addison-Wesley, 2004, \ISBN{0-321-17385-6})
+\item[\latex{} Beginner's Guide]by Stefan Kottwitz (Packt Publishing,
+ 2011, \ISBN*{1847199860}{978-1847199867})
+\item[The \LaTeX{} Companion]by Frank Mittelbach, Michel Goossens,
+ Johannes Braams, David Carlisle and Chris Rowley (second edition,
+ Addison-Wesley, 2004, \ISBN*{0-201-36299-6}{978-0-201-36299-2}); the
+ book as also available as a digital download (in \acro{EPUB},
+ \acro{MOBI} and \acro{PDF} formats) from
+ \url{http://www.informit.com/store/latex-companion-9780133387667}
+\item[The \LaTeX{} Graphics Companion:]%
+ \emph{Illustrating documents with \TeX{} and \PS{}} by Michel
+ Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and
+ Herbert Vo\ss {} (second edition, Addison-Wesley, 2007,
+ \ISBN*{0-321-50892-0}{978-0-321-50892-8})
+\item[The \LaTeX{} Web Companion:]%
+ \emph{Integrating \TeX{}, \acro{HTML} and \acro{XML}} by Michel
+ Goossens and Sebastian Rahtz (Addison-Wesley, 1999, \ISBN{0-201-43311-7})
+\item[\TeX{} Unbound:]%
+ \emph{\LaTeX{} and \TeX{} strategies for fonts, graphics, and more}
+ by Alan Hoenig (Oxford University Press, 1998, \ISBN{0-19-509685-1}
+ hardback, \ISBN{0-19-509686-X} paperback)
+% \item[Math into \LaTeX{}:]\emph{An Introduction to \LaTeX{} and \AMSLaTeX{}}
+% by George Gr\"atzer (third edition Birkh\"auser and Springer Verlag,
+% 2000, \ISBN{0-8176-4431-9}, \ISBN{3-7643-4131-9})
+% \checked{RF}{2001/01/16}
+\item[More Math into \latex{}:]\emph{An Introduction to} \LaTeX{}
+ \emph{and} \AMSLaTeX{} by George Gr\"atzer (fourth edition Springer Verlag,
+ 2007, \ISBN{978-0-387-32289-6}
+%% gr\"atzer's home page
+%% http://www.maths.umanitoba.ca/homepages/gratzer.html/LaTeXBooks.html
+\item[Digital Typography Using \LaTeX{}]Incorporating some
+ multilingual aspects, and use of \Qref*{Omega}{Q-omegaleph}, by
+ Apostolos Syropoulos, Antonis Tsolomitis and Nick Sofroniou
+ (Springer, 2003, \ISBN{0-387-95217-9}).
+% A list of errata for the first printing of Digital Typography Using
+% \LaTeX{} is available from:
+% \URL{http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html}
+% (not any longer)
+\item[First Steps in \LaTeX{}]by George Gr\"atzer (Birkh\"auser, 1999,
+ \ISBN{0-8176-4132-7})
+\item[\LaTeX{}: Line by Line:]%
+ \emph{Tips and Techniques for Document Processing}
+ by Antoni Diller (second edition, John Wiley \& Sons,
+ 1999, \ISBN{0-471-97918-X})
+\item[\LaTeX{} for Linux:]\emph{A Vade Mecum}
+ by Bernice Sacks Lipkin (Springer-Verlag, 1999,
+ \ISBN{0-387-98708-8}, second printing)
+\item[Typesetting Mathematics with \latex{}]by Herbert Vo\ss {} (UIT
+ Cambridge, 2010, \ISBN{978-1-906-86017-2})
+% checked 2011-09-09 http://www.uit.co.uk/BK-TMWL/HomePage
+\item[Typesetting Tables with \latex{}]by Herbert Vo\ss {}, (UIT
+ Cambridge, 2011, \ISBN{978-1-906-86025-7})
+% checked 2011-09-09 http://www.uit.co.uk/BK-TTWL/HomePage
+\item[PSTricks: Graphics and PostScript for \tex{} and \latex{}]by
+ Herbert Vo\ss {}, (UIT Cambridge, 2011, \ISBN{978-1-906-86013-4})
+\end{booklist}
+A sample of George Gr\"atzer's ``Math into \LaTeX{}'', in Adobe
+Acrobat format, and example files
+for the three \LaTeX{} Companions, and for
+Gr\"atzer's ``First Steps in \LaTeX{}'', are all available on
+\acro{CTAN}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}First Steps in \LaTeX{}]\CTANref{gfs}
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2}
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Graphics Companion]\CTANref{lgc}
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Web Companion]\CTANref{lwc}
+%\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\TeX{} in Practice]\CTANref{tip}
+\item[\nothtml{\rmfamily}Sample of \nothtml{\upshape}Math into \LaTeX{}]\CTANref{mil}
+\end{ctanrefs}
+\LastEdit{2014-03-14}
+
+\Question[Q-other-books]{Books on other \tex{}-related matters}
+
+There's a nicely-presented list of of ``recommended books'' to be had
+on the web: \URL{http://www.macrotex.net/texbooks/}
+
+The list of \MF{} books is rather short:
+\begin{booklist}
+\item[The \MF{}book]by Donald Knuth (Addison Wesley, 1986,
+ \ISBN{0-201-13445-4}, \ISBN{0-201-52983-1} paperback)
+\end{booklist}
+Alan Hoenig's `\textsl{\TeX{} Unbound}' includes some discussion and
+examples of using \MF{}.
+
+A book covering a wide range of topics (including installation and
+maintenance) is:
+\begin{booklist}
+\item[Making \TeX{} Work]by Norman Walsh (O'Reilly and Associates,
+ Inc, 1994, \ISBN{1-56592-051-1})
+\end{booklist}
+The book is decidedly dated, and is now out of print, but a copy is
+available via \texttt{sourceforge} and on \acro{CTAN},
+and we list it under ``\Qref*{online books}{Q-ol-books}''.
+\LastEdit*{2011-06-01}
+
+\Question[Q-type-books]{Books on Type}
+
+ The following is a partial listing of books on typography in general.
+Of these, Bringhurst seems to be the one most often recommended.
+\begin{booklist}
+\item[The Elements of Typographic Style]by Robert Bringhurst
+ (Hartley \& Marks, 1992, \ISBN{0-88179-033-8})
+\item[Finer Points in the Spacing \& Arrangement of Type]by Geoffrey Dowding
+ (Hartley \& Marks, 1996, \ISBN{0-88179-119-9})
+\item[The Thames \& Hudson Manual of Typography]by Ruari McLean
+ (Thames \& Hudson, 1980, \ISBN{0-500-68022-1})
+\item[The Form of the Book]by Jan Tschichold
+ (Lund Humphries, 1991, \ISBN{0-85331-623-6})
+\item[Type \& Layout]by Colin Wheildon
+ (Strathmore Press, 2006, \ISBN{1-875750-22-3})
+\item[The Design of Books]by Adrian Wilson
+ (Chronicle Books, 1993, \ISBN{0-8118-0304-X})
+\item[Optical Letter Spacing]by David Kindersley and Lida Cardozo Kindersley
+ % ! line break
+ (\href{http://www.kindersleyworkshop.co.uk/}{The Cardozo Kindersley Workshop}
+ 2001, \ISBN{1-874426-139})
+\end{booklist}
+
+ There are many catalogues of type specimens but the following books provide
+a more interesting overall view of types in general and some of their history.
+\begin{booklist}
+\item[Alphabets Old \& New]by Lewis F.~Day
+ (Senate, 1995, \ISBN{1-85958-160-9})
+\item[An Introduction to the History of Printing Types]by Geoffrey Dowding
+ (British Library, 1998, UK \ISBN{0-7123-4563-9}; USA \ISBN{1-884718-44-2})
+\item[The Alphabet Abecedarium]by Richard A.~Firmage
+ (David R.~Godine, 1993, \ISBN{0-87923-998-0})
+\item[The Alphabet and Elements of Lettering]by Frederick Goudy
+ (Dover, 1963, \ISBN{0-486-20792-7})
+\item[Anatomy of a Typeface]by Alexander Lawson
+ (David R.~Godine, 1990, \ISBN{0-87923-338-8})
+\item[A Tally of Types]by Stanley Morison
+ (David R.~Godine, 1999, \ISBN{1-56792-004-7})
+\item[Counterpunch]by Fred Smeijers
+ (Hyphen, 1996, \ISBN{0-907259-06-5})
+\item[Treasury of Alphabets and Lettering]by Jan Tschichold
+ (W.~W.~Norton, 1992, \ISBN{0-393-70197-2})
+\item[A Short History of the Printed Word]by Warren Chappell and
+ Robert Bringhurst (Hartley \& Marks, 1999, \ISBN{0-88179-154-7})
+\end{booklist}
+
+ The above lists are limited to books published in English. Typographic
+styles are somewhat language-dependent, and similarly the `interesting' fonts
+depend on the particular writing system involved.
+\LastEdit{2011-06-01}
+
+\Question[Q-whereFAQ]{Where to find \acro{FAQ}s}
+
+Bobby Bodenheimer's article, from which this \acro{FAQ} was developed, used
+to be posted (nominally monthly) to newsgroup
+\Newsgroup{comp.text.tex}. The (long
+obsolete) last posted copy of that article is kept on \acro{CTAN} for
+auld lang syne.
+
+\begin{pdfversion}
+A version of the \href{http://www.tex.ac.uk/faq}{present \acro{FAQ}}
+may be browsed via the World-Wide Web, and its sources
+\end{pdfversion}
+\begin{dviversion}
+A version of the present \acro{FAQ} may be browsed via the World-Wide Web, at
+\acro{URL} \URL{http://www.tex.ac.uk/faq}, and its sources
+\end{dviversion}
+\begin{htmlversion}
+The sources of the present \acro{FAQ}
+\end{htmlversion}
+are available from \acro{CTAN}.
+
+This \acro{FAQ} and others are regularly mentioned, on
+\Newsgroup{comp.text.tex} and elsewhere, in a ``pointer \acro{FAQ}''
+which is also saved at \URL{http://tug.org/tex-ptr-faq}
+
+A 2006 innovation from Scott Pakin is the ``visual'' \LaTeX{} \acro{FAQ}.
+This is a document with (mostly rubbish) text formatted so as to
+highlight things we discuss here, and providing Acrobat hyper-links to
+the relevant answers in this \acro{FAQ} on the Web. The visual
+\acro{FAQ} is provided in \acro{PDF} format, on \acro{CTAN}; it works
+best using Adobe Acrobat Reader 7 (or later); some features are
+missing with other readers, or with earlier versions of Acrobat Reader
+
+Another excellent information source, available in English, is the
+\href{http://tex.loria.fr}{\AllTeX{} navigator}.
+
+Both the Francophone \TeX{} user group Gutenberg and the Czech/Slovak
+user group CS-TUG have published translations of this \acro{FAQ}, with
+extensions appropriate to their languages.
+
+% Herbert Vo\ss {}'s excellent % beware line break
+% \href{http://texnik.de/}{\LaTeX{} tips and tricks}
+% provides excellent advice on most topics one might imagine (though
+% it's not strictly a \acro{FAQ})~--- highly recommended for most
+% ordinary mortals' use.
+
+The Open Directory Project (\acro{ODP}) maintains a list of sources of
+\AllTeX{} help, including \acro{FAQ}s. View the \TeX{} area at
+\URL{http://dmoz.org/Computers/Software/Typesetting/TeX/}
+
+Other non-English \acro{FAQ}s are available (off-\acro{CTAN}):
+\begin{booklist}
+\item[German]Posted regularly to \Newsgroup{de.comp.tex}, and archived
+ on \acro{CTAN}; the \acro{FAQ} also appears at
+ \URL{http://www.dante.de/faq/de-tex-faq/}
+\item[French]%
+%% An interactive (full-screen!) FAQ may be found at
+%% \URL{http://www.frenchpro6.com/screen.pdf/FAQscreen.pdf}, and a copy
+%% for printing at \URL{http://frenchle.free.fr/FAQ.pdf};
+ A FAQ used to be posted regularly to
+ \Newsgroup{fr.comp.text.tex}, and is archived on \acro{CTAN}~---
+ sadly, that effort seems to have fallen by the wayside.
+%% \item[Spanish]See \URL{http://apolo.us.es/CervanTeX/FAQ/}
+\item[Czech]See \URL{http://www.fi.muni.cz/cstug/csfaq/}
+\end{booklist}
+
+Resources available on \acro{CTAN} are:
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Dante \acro{FAQ}]\CTANref{dante-faq}
+\item[\nothtml{\rmfamily}French \acro{FAQ}]\CTANref{french-faq}
+\item[\nothtml{\rmfamily}Sources of this \acro{FAQ}]\CTANref{faq}
+\item[\nothtml{\rmfamily}Obsolete \texttt{comp.text.tex} \acro{FAQ}]%
+ \CTANref{TeX-FAQ}
+\item[\nothtml{\rmfamily}The visual \acro{FAQ}]\CTANref{visualFAQ}
+\end{ctanrefs}
+\LastEdit{2013-07-02}
+
+\Question[Q-gethelp]{Getting help online}
+
+We assume, here, that you have looked at all relevant
+\Qref*{\acro{FAQ} answers}{Q-whereFAQ} you can find, you've looked in
+any \Qref*{books}{Q-book-lists} you have, and scanned relevant
+\Qref*{tutorials}{Q-tutorials*}\dots{} and still you don't know what
+to do.
+
+There are two more steps you can take before formulating a question to
+the \tex{} world at large.
+
+First, (if you are seeking a particular package or program), start by
+looking on your own system: you might already have what you seek~---
+the better \TeX{} distributions provide a wide range of supporting
+material. The \Qref*{\acro{CTAN} Catalogue}{Q-catalogue} can also
+identify packages that might help: you can % ! line break
+\href{http://www.tex.ac.uk/search}{search it}, or you can browse it
+\begin{hyperversion}
+% !!!! line break
+``\href{http://mirrors.ctan.org/help/Catalogue/bytopic.html}{by topic}''.
+\end{hyperversion}
+\begin{flatversion}
+``by topic'' at
+\url{http://mirrors.ctan.org/help/Catalogue/bytopic.html}
+\end{flatversion}
+Each catalogue entry has a brief description of the package, and links to
+known documentation on the net. In fact, a large proportion of
+\acro{CTAN} package directories now include documentation, so it's
+often worth looking at the catalogue entry for a package you're considering
+using (where possible, each package link in the main body of these
+\acro{FAQ}s \hyperflat{has a link to}{shows the \acro{URL} of}
+the relevant catalogue entry).
+
+Failing that, look to see if anyone has solved the problem before;
+places where people ask are:
+\begin{enumerate}
+\item newsgroup \Newsgroup{comp.text.tex}, whose ``historical posts''
+ are accessible via
+ \href{http://groups.google.com/group/comp.text.tex}{Google groups},
+ and
+\item the mailing list \texttt{texhax} via its
+ \href{http://tug.org/pipermail/texhax/}{archive}, or via the `Gmane'
+ newsgroup \Newsgroup{gmane.comp.tex.texhax}, which holds a
+ \emph{very} long history of the list. A long shot would be to
+ search the archives of the mailing list's ancient posts on
+ \acro{CTAN}, which go back to the days when it was a digest: in
+ those days, a question asked in one issue would only ever be
+ answered in the next one.
+\end{enumerate}
+If the ``back question'' searches fail, you must ask the world at
+large.
+
+So, how do you like to ask questions?~--- the three available
+mechanisms are:
+\begin{enumerate}
+\item Mailing lists: there are various specialist mailing lists, but
+ the place for `general' \alltex{} queries is the \texttt{texhax}
+ mailing list. Mail to \mailto{texhax@tug.org} to ask a question,
+ but it's probably better to subscribe to the list
+ (via \URL{http://tug.org/mailman/listinfo/texhax}) % ! no ~ allowed
+ first~--- not everyone will answer to you as well as to the list.
+\item Newsgroup: to ask a question on \Newsgroup{comp.text.tex}, you
+ can use your own news client (if you have one), or use the ``+ new
+ post'' button on
+ \URL{http://groups.google.com/group/comp.text.tex}.
+\item Web forum: alternatives are: the % ! line break
+ \href{http://www.latex-community.org/}{``\LaTeX{} community'' site},
+ which offers a variety of `categories' to place your query, and the
+ % the next line will tend to break if you add _anything_ to it!
+ \href{http://tex.stackexchange.com/}{\TeX{}, \LaTeX{} and friends Q\&A site}
+ (``StackExchange'').
+
+ StackExchange has a scheme for voting on the quality of answers (and
+ hence of those who offer support). This arrangement is supposed to
+ enable you to rank any answers that are posted.
+
+ StackExchange offers
+ \href{http://meta.tex.stackexchange.com/questions/1436/welcome-to-tex-sx}{hints about ``good behaviour''},
+ which any user should at least scan before asking for help there.
+ (The hints' principal aim is to maximise the chance that you get useful
+ advice from the first answer; for example, it suggests that you supply a
+ \Qref*{minimal example of your problem}{Q-askquestion}, just as
+ these \acro{FAQ}s do. There are people on the site who can be abrasive
+ to those asking questions, who seem not to be following the
+ guidelines for good behaviour)
+\end{enumerate}
+Do \textbf{not} try mailing the \LaTeX{} project team, the maintainers
+of the \texlive{} or \miktex{} distributions or the maintainers of
+these \acro{FAQ}s for help; while all these addresses reach
+experienced \AllTeX{} users, no small group can possibly have
+expertise in every area of usage so that the ``big'' lists and forums
+are a far better bet.
+\begin{ctanrefs}
+\item[texhax \nothtml{\rmfamily}`back copies']\CTANref{texhax}
+\end{ctanrefs}
+\LastEdit{2014-01-28}
+
+\Question[Q-maillists*]{Specialist mailing lists}
+
+The previous question, ``\Qref*{getting help}{Q-gethelp}'', talked of
+the two major forums in which \AllTeX{}, \MF{} and \MP{} are
+discussed; however, these aren't the only ones available.
+
+The \acro{TUG} web site offers many mailing lists other than just
+\texttt{texhax} via its % ! line break
+\href{http://tug.org/mailman/listinfo}{mail list management page}.
+
+The French national \TeX{} user group, Gutenberg, offers a \MF{} (and,
+de facto, \MP{}) mailing list, \mailto{metafont@ens.fr}: subscribe to
+it by sending a message
+\begin{quote}
+\begin{verbatim}
+subscribe metafont
+\end{verbatim}
+\end{quote}
+to \mailto{sympa@ens.fr}
+
+(Note that there's also a \MP{}-specific mailing list available via the
+\acro{TUG} list server; in fact there's little danger of becoming confused
+by subscribing to both.)
+
+Announcements of \TeX{}-related installations on the \acro{CTAN}
+archives are sent to the mailing list \texttt{ctan-ann}. Subscribe
+to the list via its \ProgName{MailMan} web-site
+\URL{https://lists.dante.de/mailman/listinfo/ctan-ann}; list archives
+are available at the same address. The list archives may also be
+browsed via \URL{http://www.mail-archive.com/ctan-ann@dante.de/}, and
+an \acro{RSS} feed is also available:
+\URL{http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml}
+
+\Question[Q-askquestion]{How to ask a question}
+
+You want help from the community at large; you've decided where you're
+going to \Qref*{ask your question}{Q-gethelp}, but how do you
+phrase it?
+
+Excellent ``general'' advice (how to ask questions of anyone) is
+contained in
+%beware line break
+\href{http://catb.org/~esr/faqs/smart-questions.html}{Eric Raymond's article on the topic}.
+Eric's an extremely self-confident person, and this comes through in
+his advice; but his guidelines are very good, even for us in the
+un-self-confident majority. It's important to remember that you don't
+have a right to advice from the world, but that if you express
+yourself well, you will usually find someone who will be pleased to
+help.
+
+So how do you express yourself in the \AllTeX{} world? There aren't
+any comprehensive rules, but a few guidelines may help in the
+application of your own common sense.
+\begin{itemize}
+\item Make sure you're asking the right people. Don't ask in a \TeX{}
+ forum about printer device drivers for the \ProgName{Foobar}
+ operating system. Yes, \TeX{} users need printers, but no, \TeX{}
+ users will typically \emph{not} be \ProgName{Foobar} systems
+ managers.
+
+ Similarly, avoid posing a question in a language that the majority
+ of the group don't use: post in Ruritanian to
+ \Newsgroup{de.comp.text.tex} and you may have a long wait before a
+ German- and Ruritanian-speaking \TeX{} expert notices your
+ question.
+\item If your question is (or may be) \TeX{}-system-specific, report
+ what system you're using, or intend to use: ``I can't install
+ \TeX{}'' is as good as useless, whereas ``I'm trying to install the
+ \ProgName{mumbleTeX} distribution on the \ProgName{Grobble}
+ operating system'' gives all the context a potential respondent
+ might need. Another common situation where this information is
+ important is when you're having trouble installing something new in
+ your system: ``I want to add the \Package{glugtheory} package to my
+ \ProgName{mumbleTeX v12.0} distribution on the \ProgName{Grobble 2024}
+ operating system''.
+\item If you need to know how to do something, make clear what your
+ environment is: ``I want to do \emph{x} in \plaintex{}'', or ``I
+ want to do \emph{y} in \LaTeX{} running the \Class{boggle}
+ class''. If you thought you knew how, but your attempts are
+ failing, tell us what you've tried: ``I've already tried installing
+ the \Package{elephant} in the \Package{minicar} directory, and it
+ didn't work, even after refreshing the filename database''.
+\item If something's going wrong within \AllTeX{}, pretend you're
+ \Qref*{submitting a \LaTeX{} bug report}{Q-latexbug},
+ and try to generate a \Qref*{minimum failing example}{Q-minxampl}.
+ If your example
+ needs your local \Class{xyzthesis} class, or some other resource
+ not generally available, be sure to include a pointer to how the
+ resource can be obtained.
+\item Figures are special, of course. Sometimes the figure itself is
+ \emph{really} needed, but most problems may be demonstrated with a
+ ``figure substitute'' in the form of a
+ \cmdinvoke*{rule}{width}{height} command, for some value of
+ \meta{width} and \meta{height}. If the (real) figure is needed,
+ don't try posting it: far better to put it on the web somewhere.
+\item Be as succinct as possible. Your helpers don't usually need to
+ know \emph{why} you're doing something, just \emph{what} you're
+ doing and where the problem is.
+\end{itemize}
+
+\Question[Q-minxampl]{How to make a ``minimum example''}
+
+\Qref[Question]{Our advice on asking questions}{Q-askquestion}
+suggests that you prepare a ``minimum example'' (also commonly known
+as a ``\emph{minimal} example'') of failing behaviour,
+as a sample to post with your question. If you have a problem in a
+two hundred page document, it may be unclear how to proceed from this
+problem to a succinct demonstration of your problem.
+
+There are two valid approaches to this task: building up, and hacking
+down.
+
+% ! line break
+\latexhtml{The ``building up'' process}{\textbf{\emph{Building up}}} starts
+with a basic document structure
+(for \LaTeX{}, this would have \csx{documentclass},
+\cmdinvoke{begin}{document}, \cmdinvoke{end}{document}) and adds
+things. First to add is a paragraph or so around the actual point
+where the problem occurs. (It may prove difficult to find the actual
+line that's provoking the problem. If the original problem is an
+error, reviewing % ! line break
+\Qref[the answer to question]{``the structure of \TeX{} errors''}{Q-errstruct}
+may help.)
+
+Note that there are things that can go wrong in one part of the
+document as a result of something in another part: the commonest is
+problems in the table of contents (from something in a section title,
+or whatever), or the list of \meta{something} (from something in a
+\csx{caption}). In such a case, include the section title or caption
+(the caption probably needs the \environment{figure} or
+\environment{table} environment around it, but it \emph{doesn't} need
+the figure or table itself).
+
+If this file you've built up shows the problem already, then you're done.
+Otherwise, try adding packages; the optimum is a file with only one
+package in it, but you may find that the guilty package won't even load
+properly unless another package has been loaded. (Another common case
+is that package \Package{A} only fails when package \Package{B} has been
+loaded.)
+
+% ! line break
+\latexhtml{The ``hacking down'' route}{\textbf{\emph{Hacking down}}} starts
+with your entire document, and
+removes bits until the file no longer fails (and then of course
+restores the last thing removed). Don't forget to hack out any
+unnecessary packages, but mostly, the difficulty is choosing what to
+hack out of the body of the document; this is the mirror of the
+problem above, in the ``building up'' route.
+
+If you've added a package (or more than one), add \csx{listfiles} to
+the preamble too: that way, \LaTeX{} will produce a list of the
+packages you've used and their version numbers. This information may
+be useful evidence for people trying to help you.
+
+The process of `building up', and to some extent that of `hacking
+down', can be helped by stuff available on \acro{CTAN}:
+\begin{itemize}
+\item the \Class{minimal} class (part of the \latex{} distribution)
+ does what its name says: it provides nothing more than what is
+ needed to get \latex{} code going, and
+\item the \Package{mwe} bundle provides a number of images in formats
+ that \alltex{} documents can use, and a small package \Package{mwe}
+ which loads other useful packages (such as \Package{blindtext} and
+ \Package{lipsum}, both capable of producing dummy text in a
+ document).
+\end{itemize}
+
+What if none of of these cut-down derivatives of your document will
+show your error? Whatever you do, don't post the whole of the document: if
+you can, it may be useful to make a copy available on the web
+somewhere: people will probably understand if it's impossible~\dots{}\
+or inadvisable, in the case of something confidential.
+
+If the whole document is indeed necessary, it could be that your
+error is an overflow of some sort; the best you can do is to post the
+code ``around'' the error, and (of course) the full text of the error.
+
+It may seem that all this work is rather excessive for preparing a
+simple post. There are two responses to that, both based on the
+relative inefficiency of asking a question on the internet.
+
+First, preparing a minimum document very often leads \emph{you} to the
+answer, without all the fuss of posting and looking for responses.
+
+Second, your prime aim is to get an answer as quickly as possible; a
+well-prepared example stands a good chance of attracting an answer
+``in a single pass'': if the person replying to your post finds she
+needs more information, you have to find that request, post again, and
+wait for your benefactor to produce a second response.
+
+All things considered, a good example file can save you a day, for
+perhaps half an hour's effort invested.
+
+Much of the above advice, differently phrased, may also be read on the
+web at \URL{http://www.minimalbeispiel.de/mini-en.html}; source of
+that article may be found at \URL{http://www.minimalbeispiel.de/}, in
+both German and English.
+\begin{ctanrefs}
+\item[blindtext.sty]\CTANref{blindtext}
+\item[lipsum.sty]\CTANref{lipsum}
+\item[minimal.cls]Distributed as part of \CTANref{latex}
+\item[mwe.sty]\CTANref{mwe}
+\end{ctanrefs}
+\LastEdit{2013-01-09}
+
+\Question[Q-tutorials*]{Tutorials, etc., for \tex{}-based systems}
+
+From a situation where every \AllTeX{} user \emph{had} to buy a book
+if she was not to find herself groping blindly along, we now have what
+almost amounts to an embarrassment of riches of online documentation.
+The following answers attempt to create lists of sources ``by topic''.
+
+First we have introductory manuals, for
+\Qref*{\plaintex{}}{Q-man-tex} and \Qref*{\LaTeX{}}{Q-man-latex}.
+
+Next comes a selection of
+\Qref*{``specialised'' \AllTeX{} tutorials}{Q-tutbitslatex},
+each of which concentrates on a single \LaTeX{} topic.
+
+A small selection of reference documents (it would be good to have
+more) are listed in an \Qref*{answer of their own}{Q-ref-doc}.
+
+Next comes the (somewhat newer) field of % ! line break
+\Qref*{\TeX{}-related WIKIs}{Q-doc-wiki}.
+
+A rather short list gives us a % ! line break
+\Qref*{Typography style tutorial}{Q-typo-style}.
+\LastEdit{2011-09-26}
+
+\Question[Q-man-tex]{Online introductions: \plaintex{}}
+
+Michael Doob's splendid `Gentle Introduction' to \plaintex{}
+(available on \acro{CTAN}) has been stable for a very long time.
+
+Another recommendable document is D. R.~Wilkins' `Getting started with \TeX{}',
+available on the web at \URL{http://www.ntg.nl/doc/wilkins/pllong.pdf}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Gentle Introduction]\CTANref{gentle}
+\end{ctanrefs}
+
+\Question[Q-man-latex]{Online introductions: \LaTeX{}}
+
+A pleasing little document, ``Getting something out of \LaTeX{}'' is
+designed to give a feel of \LaTeX{} to someone who's never used it at
+all. It's not a tutorial, merely helps the user to decide whether to
+go on to a tutorial, and thence to `real' use of \LaTeX{}.
+
+Tobias Oetiker's `(Not so) Short Introduction to \LaTeXe{}', is
+regularly updated, as people suggest better ways of explaining things,
+etc. The introduction is available on \acro{CTAN}, together with
+translations into a rather large set of languages.
+
+Peter Flynn's ``Beginner's \LaTeX{}'' (which started life as course
+material) is a pleasing read. A complete copy may be found on
+\acro{CTAN}, but it may also be browsed over the web
+(\URL{http://mirrors.ctan.org/info/beginlatex/html/}).
+
+Harvey Greenberg's `Simplified Introduction to \LaTeX{}' was written
+for a lecture course, and is also available on \acro{CTAN} (in \PS{}
+only, unfortunately).
+
+The fourth edition of George Gr\"atzer's book ``Math into \LaTeX{}''
+contains a ``short course'' in \LaTeX{} itself, and that course has
+been made publicly available on \acro{CTAN}.
+
+Philip Hirschhorn's ``Getting up and running with \AMSLaTeX{}'' has a
+brief introduction to \LaTeX{} itself, followed by a substantial
+introduction to the use of the \acro{AMS} classes and the
+\Package{amsmath} package and other things that are potentially of
+interest to those writing documents containing mathematics.
+
+Edith Hodgen's % beware line break
+\href{http://www.mcs.vuw.ac.nz/~david/latex/notes.pdf}{\LaTeX{}, a Braindump}
+starts you from the ground up~--- giving a basic tutorial in the use
+of \ProgName{Linux} to get you going (rather a large file\dots{}).
+Its parent site, David Friggens' % ! line break
+\href{http://www.mcs.vuw.ac.nz/~david/latex/}{documentation page} is a
+useful collection of links in itself.
+
+% ! line break
+\href{http://www.andy-roberts.net/misc/latex/}{Andy Roberts' introductory material}
+is a pleasing short introduction to the use of \AllTeX{}; some of the
+slides for \emph{actual} tutorials are to be found on the page, as
+well.
+
+D. R.~Wilkins' % ! line break
+\href{http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/}{`Getting started with \latex{}'}
+also looks good (it appears shorter~--- more of a primer~--- than some
+of the other offerings).
+
+Chris Harrison's % ! line break
+\href{http://xoph.co/20111024/latex-tutorial/}{LaTeX tutorial}
+presents basic \LaTeX{} in a rather pleasing and straightforward way.
+
+Nicola Talbot's % ! line break
+\href{http://www.dickimaw-books.com/latex/novices/}{\LaTeX{} for complete novices}
+does what it claims: the author teaches \LaTeX{} at the University of
+East Anglia. The ``Novices'' tutorial is one of several % ! line break
+\href{http://www.dickimaw-books.com/latex/}{introductory tutorials},
+which include exercises (with solutions). Other tutorials include
+those for % ! line break
+\href{http://www.dickimaw-books.com/latex/thesis/}{writing theses/dissertations with \LaTeX{}}, and for % ! line break
+\href{http://www.dickimaw-books.com/latex/admin/}{using \LaTeX{} in administrative work}
+
+Engelbert Buxbaum provides the `slides' for his \latex{} course `The
+\latex{} document preparation system'; this seems to be a departmental
+course at his university.
+
+Mark van Dongen's % line break
+\href{"http://csweb.ucc.ie/~dongen/LaTeX-and-Friends.pdf}{`\latex and friends'}
+appeared as he was writing his book on the subject (soon to be published).
+
+An interesting (and practical) tutorial about what \emph{not} to do is
+\Package{l2tabu}, or ``A list of sins of \LaTeXe{} users'' by Mark
+Trettin, translated into English by J\"urgen Fenn. The
+tutorial is available from \acro{CTAN} as a \acro{PDF} file (though
+the source is also available).
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Beginner's \LaTeX{}]\CTANref{beginlatex-pdf}
+% ! line break
+\item[\nothtml{\rmfamily}Getting something out of \latex{}]\CTANref{first-latex-doc}
+% ! line break
+\item[\nothtml{\rmfamily}Getting up and running with \AMSLaTeX{}]\CTANref{amslatex-primer}
+\item[\nothtml{\rmfamily}Slides for \latex{} course]\CTANref{latex-course}
+\item[\nothtml{\rmfamily}Not so Short Introduction]\CTANref{lshort}
+ (in English, you may browse for sources and other language versions at
+ \CTANref{lshort-parent})
+\item[\nothtml{\rmfamily}Simplified \LaTeX{}]\CTANref{simpl-latex}
+\item[\nothtml{\rmfamily}Short Course in \LaTeX{}]\CTANref{mil-short}
+% ! line break
+\item[\nothtml{\rmfamily}The sins of \LaTeX{} users]Browse
+ \CTANref{l2tabu} for a copy of the document in a language that is
+ convenient for you
+\end{ctanrefs}
+\LastEdit{2012-11-29}
+
+\Question[Q-tutbitslatex]{\AllTeX{} tutorials}
+\AliasQuestion{Q-doc-dirs}
+
+The \acro{AMS} publishes a ``Short Math Guide for \LaTeX{}'', which is
+available (in several formats) via
+\URL{http://www.ams.org/tex/amslatex.html} (the ``Additional
+Documentation'' about half-way down the page.
+
+Herbert Vo\ss {} has written an extensive guide to mathematics in
+\LaTeX{}, and a development of it has been % ! line break
+\Qref*{published as a book}{Q-latex-books}.
+
+Two documents written more than ten years apart about font usage in
+\TeX{} are worth reading: % ! line break
+\href{http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf}{Essential NFSS}
+by Sebastian Rahtz, and % ! line break
+\href{http://tug.org/pracjourn/2006-1/schmidt/schmidt.pdf}{Font selection in LaTeX},
+cast in the form of an \acro{FAQ}, by Walter Schmidt. A general
+compendium of font information (including the two above) may be found
+on the \href{http://www.tug.org/fonts/}{TUG web site}.
+
+T\acro{UG} India is developing a series of online \LaTeX{} tutorials
+which can be strongly recommended: select single chapters at a time
+from \URL{http://www.tug.org/tutorials/tugindia}\nobreakspace--- there
+are 17~chapters in the series, two of which are mostly introductory.
+
+Peter Smith's
+\begin{narrowversion}
+ ``\LaTeX{} for Logicians''
+ (\URL{http://www.logicmatters.net/latex-for-logicians/})
+\end{narrowversion}
+\begin{wideversion}
+ % ! line break
+ ``\href{http://www.logicmatters.net/latex-for-logicians/}{\LaTeX{} for Logicians}''
+\end{wideversion}
+page covers a rather smaller subject area, but is similarly comprehensive
+(mostly by links to documents on relevant topics, rather than as a
+monolithic document).
+
+Keith Reckdahl's ``Using Imported Graphics in \LaTeXe{}''
+(\Package{epslatex}) is an
+excellent introduction to graphics use. It's available on
+\acro{CTAN}, but not in the \texlive{} or miktex{} distributions, for
+lack of sources.
+
+Stefan Kottwitz manages a web site devoted to the use of the drawing
+packages % ! line break
+\Qref*{\acro{PGF} and \acro{T}ik\acro{Z}}{Q-drawing}, % ! line break
+\url{http://www.texample.net/}
+
+Included is % ! line break
+ \href{http://www.texample.net/tikz/examples/}{examples catalogue}
+includes examples (with output) from the package documentation as well
+as code written by the original site maintainer (Kjell Magne Fauske)
+and others.
+
+The compendious \acro{PGF}/\acro{T}ik\acro{Z} manual is clear, but is
+bewildering for some beginners. The % ! line break
+\href{http://cremeronline.com/LaTeX/minimaltikz.pdf}{`minimal' introduction}
+has helped at least the present author.
+
+Vincent Zoonekynd provides a set of excellent (and graphic) tutorials
+on the programming of % !line breaks, ...
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html}{title page styles},
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html}{chapter heading styles}
+and
+\href{http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html}{section heading styles}.
+In each file, there is a selection of graphics representing an output
+style, and for each style, the code that produces it is shown.
+
+An invaluable step-by-step setup guide for establishing a ``work
+flow'' through your \AllTeX{} system, so that output appears at the
+correct size and position on standard-sized paper, and that the print
+quality is satisfactory, is Mike Shell's \Package{testflow}. The
+tutorial consists of a large plain text document, and there is a
+supporting \LaTeX{} file together with correct output, both in \PS{} and
+\acro{PDF}, for each of \acro{A}4 and ``letter'' paper sizes. The
+complete kit is available on \acro{CTAN} (distributed with the
+author's macros for papers submitted for \acro{IEEE} publications).
+The issues are also covered in a later % ! line break
+\Qref{\acro{FAQ} answer}{Q-dvips-pdf}.
+
+Documentation of Japanese \ensuremath{\Omega{}} use appears in
+Haruhiko Okumura's page
+% ! line break
+\href{http://oku.edu.mie-u.ac.jp/~okumura/texfaq/japanese/}{typesetting Japanese with Omega}
+(the parent page is in Japanese, so out of the scope of this
+\acro{FAQ} list).
+
+Some university departments make their local documentation available
+on the web. Most straightforwardly, there's the simple translation of
+existing documentation into \acro{HTML}, for example the \acro{INFO}
+documentation of the \AllTeX{} installation, of which a sample is the
+\LaTeX{} documentation available at
+\URL{http://www.tac.dk/cgi-bin/info2www?(latex)}
+
+More ambitiously, some university departments have enthusiastic
+documenters who
+make public record of their \AllTeX{} support. For example, Tim Love
+(of Cambridge University Engineering Department) maintains his
+department's pages at
+\URL{http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/}
+%% and Mimi
+%% Burbank (of the School of Computer Science \& Information Technology
+%% at the University of Florida) manages her department's at
+%% \URL{http://www.csit.fsu.edu/~mimi/tex/}\nobreakspace--- both sets are fine
+%% examples of good practice.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]\CTANref{epslatex}
+\item[testflow]\CTANref{testflow}
+\item[\nothtml{\rmfamily}Herbert Vo\ss {}'s Maths tutorial]\CTANref{voss-mathmode}
+\end{ctanrefs}
+
+\Question[Q-ref-doc]{Reference documents}
+
+For \TeX{} primitive commands a rather nice % ! line break
+\href{http://www.nmt.edu/tcc/help/pubs/texcrib.pdf}{quick reference booklet},
+by John W.~Shipman, is available; it's arranged in the same way as the
+\TeX{}book. By contrast, you can view David Bausum's % ! line break
+\href{http://www.tug.org/utilities/plain/cseq.html}{list of \TeX{} primitives}
+alphabetically or arranged by ``family''. Either way, the list has a
+link for each control sequence, that leads you to a detailed
+description, which includes page references to the \TeX{}book.
+
+There doesn't seem to be a reference that takes in \plaintex{} as
+well as the primitive commands.
+
+An interesting \LaTeX{} ``cheat sheet'' is available from \acro{CTAN}:
+it's a list of (more or less) everything you `ought to' remember, for
+basic \LaTeX{} use. % line break
+(It's laid out very compactly for printing on N.\ American `letter';
+printed on \acro{ISO} \acro{A}4, using Adobe Acrobat's ``shrink to
+fit'', it strains aged eyes\dots{})
+
+For command organised references to \LaTeX{}, Karl Berry (et
+al)'s % !line break
+\href{http://home.gna.org/latexrefman}{LaTeX reference manual} is (to
+an extent) work in progress, but is generally reliable (source is
+available on the.archive as well).
+
+Martin Scharrer's ``List of internal \latex{} macros'' is a help to
+those aiming to write a class or package.
+
+The reference provided by the Emerson Center of Emory
+University), % ! line break
+\href{http://www.emerson.emory.edu/services/latex/latex2e/latex2e_toc.html}{LaTeXe help}
+also looks good.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Cheat sheet]\CTANref{latexcheat}
+\item[\nothtml{\rmfamily}LaTeX reference manual]\CTANref{latex2e-help-texinfo}
+\item[\nothtml{\rmfamily}LaTeX internal macros]\CTANref{macros2e}
+\end{ctanrefs}
+\LastEdit{2012-02-16}
+
+\Question[Q-doc-wiki]{\acro{WIKI} books for \TeX{} and friends}
+
+The \emph{\acro{WIKI}} concept can be a boon to everyone, if used sensibly.
+The ``general'' \acro{WIKI} allows \emph{anyone} to add stuff, or to edit
+stuff that someone else has added: while there is obvious potential
+for chaos, there is evidence that a strong user community can keep a
+\acro{WIKI} under control.
+
+Following the encouraging performance of the % ! line break
+\href{http://contextgarden.net/}{\CONTeXT{} \acro{WIKI}}, valiant
+efforts have been made generating ``\acro{WIKI} books'' for \AllTeX{}
+users. Thus we have % ! line break
+\href{http://en.wikibooks.org/wiki/TeX}{(Plain) \TeX{} \acro{WIKI} book} and
+\href{http://en.wikibooks.org/wiki/LaTeX}{\LaTeX{} \acro{WIKI} book}~---
+both well established. Both are highly rated as reference sources,
+and even as introductory texts.
+\LastEdit{2012-07-25}
+
+\Question[Q-typo-style]{Typography tutorials}
+
+Peter Wilson's article \Package{memdesign} has a lengthy introductory
+section on typographic considerations, which is a fine tutorial,
+written by someone who is aware of the issues as they apply to
+\AllTeX{} users. (\Package{Memdesign} now distributed separately from
+the manual for his \Class{memoir} class, but was originally part of
+that manual)
+
+There's also (at least one) typographic style tutorial available on
+the Web, the excellent % ! line break
+``\href*{http://www.nbcs.rutgers.edu/~hedrick/typography/typography.janson-syntax.107514.pdf}{Guidelines for Typography in NBCS}''.
+In fact, its % !!
+\href*{http://www.nbcs.rutgers.edu/~hedrick/typography/index.html}{parent page}
+is also worth a read: among other things, it provides copies of the
+``guidelines'' document in a wide variety of primary fonts, for
+comparison purposes. The author is careful to explain that he has no
+ambition to supplant such excellent books as
+\Qref*{Bringhurst's}{Q-type-books}, but the document (though it does
+contain its Rutgers-local matter) is a fine introduction to the issues
+of producing readable documents.
+\begin{ctanrefs}
+\item[memdesign]\CTANref{memdesign}
+\end{ctanrefs}
+
+\Question[Q-ol-books]{Freely available \AllTeX{} books}
+
+People have long argued for \AllTeX{} books to be made available on
+the web, and until relatively recently this demand went un-answered.
+
+The first to appear was Victor Eijkhout's excellent ``\TeX{} by
+Topic'' in 2001 (it had been published by Addison-Wesley, but was long
+out of print). The book is now available on \acro{CTAN}; it's not a
+beginner's tutorial but it's a fine reference. It's also available,
+as a printed copy, via the on-line publishers
+\href{http://www.lulu.com/content/2555607/}{Lulu} (not quite free, of
+course, but not a \emph{bad} deal\dots{}).
+
+Addison-Wesley have also released the copyright of ``\TeX{} for the
+Impatient'' by Paul W.~Abrahams, Karl Berry and Kathryn A.~Hargreaves,
+another book whose unavailability many have lamented. The authors
+have re-released the book under the \acro{GNU} Free Documentation
+Licence, and it is available from \acro{CTAN}.
+
+Norm Walsh's ``Making \TeX{} Work'' (originally published by O'Reilly)
+is also available (free) on the Web, at
+\URL{http://makingtexwork.sourceforge.net/mtw/}; the sources of the
+Web page are on \acro{CTAN}. The book was an excellent resource in
+its day, but while it is now somewhat dated, it still has its uses,
+and is a welcome addition to the list of on-line resources. A project
+to update it is believed to be under way.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Making \TeX{} Work]\CTANref{mtw}
+\item[\nothtml{\rmfamily}\TeX{} by Topic]\CTANref{texbytopic}
+\item[\nothtml{\rmfamily}\TeX{} for the Impatient]\CTANref{TftI}
+\end{ctanrefs}
+\LastEdit{2011-06-29}
+
+\Question[Q-pkgdoc]{Documentation of packages}
+
+These \acro{FAQ}s regularly suggest packages that will ``solve''
+particular problems. In some cases, the answer provides a recipe for
+the job. In other cases, or when the solution needs elaborating, how
+is the poor user to find out what to do?
+
+If you're lucky, the package you need is already in your installation.
+If you're particularly lucky, you're using a distribution that gives
+access to package documentation and the documentation is available in
+a form that can easily be shown.
+
+On \texlive{}-based distributions, help should be available from the
+\ProgName{texdoc} command, as in:
+\begin{quote}
+\begin{verbatim}
+texdoc footmisc
+\end{verbatim}
+\end{quote}
+which opens a window showing documentation of the \Package{footmisc}
+package. (The window is tailored to the file type, in the way normal
+for the system.)
+
+If \ProgName{texdoc} can't find any documentation, it may launch a Web
+browser to look at the package's entry in the \acro{CTAN} catalogue.
+The catalogue has an entry for package documentation, and most authors
+respond to the \acro{CTAN} team's request for documentation of
+packages, you will more often than not find documentation that way.
+
+On \miktex{} systems, the same function is provided by the
+\ProgName{mthelp}.
+
+Note that the site \url{texdoc.net} provides access to the
+documentation you \emph{would} have if you had a \emph{full}
+installation of \texlive{}; on the site you can simply ask for a
+package (as you would ask \ProgName{texdoc}, or you can use the site's
+index of documentation to find what you want. (This is helpful for
+some of us: many people don't have a full \alltex{} installation on
+their mobile phone~\dots{} yet.)
+
+If your luck (as defined above) doesn't hold out, you've got to find
+documentation by other means. That is, you have to find the
+documentation for yourself. The rest of this answer offers a range of
+possible techniques.
+
+The commonest form of documentation of \LaTeX{} add-ons is within the
+\extension{dtx} file in which the code is distributed (see
+\Qref[answer]{documented \LaTeX{} sources}{Q-dtx}). Such files
+are supposedly processable by \LaTeX{} itself, but there are
+occasional hiccups on the way to readable documentation. Common
+problems are that the package itself is needed to process its own
+documentation (so must be unpacked before processing), and that the
+\extension{dtx} file will \emph{not} in fact process with \LaTeX{}. In the
+latter case, the \extension{ins} file will usually produce a
+\extension{drv} (or similarly-named) file, which you process with
+\LaTeX{} instead. (Sometimes the package author even thinks to
+mention this wrinkle in a package \texttt{README} file.)
+
+Another common form is the separate documentation file; particularly
+if a package is ``conceptually large'' (and therefore needs a lot of
+documentation), the documentation would prove a cumbersome extension
+to the \extension{dtx} file. Examples of such cases are the \Class{memoir}
+class, the \Class{KOMA-script} bundle
+(whose developers take the trouble to produce detailed documentation
+in both German and English), the \Package{pgf} documentation (which
+would make a substantial book in its own right)
+and the \Package{fancyhdr} package (whose
+documentation derives from a definitive tutorial in a mathematical
+journal). Even if the documentation is not separately identified in a
+\texttt{README} file, it should not be too difficult to recognise its
+existence.
+
+Documentation within the package itself is the third common form.
+Such documentation ordinarily appears in comments at the head of the
+file, though at least one eminent author regularly places it after the
+\csx{endinput} command in the package. (This is desirable, since
+\csx{endinput} is a `logical' end-of-file, and \AllTeX{} doesn't read
+beyond it: thus such documentation does not `cost' any package loading time.)
+
+The above suggestions cover most possible ways of finding
+documentation. If, despite your best efforts, you can't find
+it in any of the above places, there's the awful possibility that the
+author didn't bother to document his package (on the ``if it was hard
+to write, it should be hard to use'' philosophy). Most ordinary
+mortals will seek support from some more experienced user at this
+stage, though it \emph{is} possible to proceed in the way that the original
+author apparently expected\dots{}by reading his code.
+\LastEdit{2012-11-09}
+
+\Question[Q-writecls]{Learning to write \LaTeX{} classes and packages}
+
+There's nothing particularly magic about the commands you use when
+writing a package, so you can simply bundle up a set of \LaTeX{}
+\csx{(re)newcommand} and \csx{(re)newenvironment} commands, put them in
+a file \File{package.sty} and you have a package.
+
+However, any but the most trivial package will require rather more
+sophistication. Some details of \LaTeX{} commands for the job are to
+be found in `\LaTeXe{} for class and package writers'
+(\File{clsguide}, part of the \LaTeX{} documentation distribution).
+Beyond this, a good knowledge of \TeX{} itself is valuable: thus books
+such as the \Qref*{\TeX{}book}{Q-tex-books} or % ! line break
+\Qref*{\TeX{} by topic}{Q-ol-books} are relevant. With good \TeX{}
+knowledge it is possible to use the documented source of \LaTeX{} as
+reference material (dedicated authors will acquaint themselves with the
+source as a matter of course). A complete set of the documented
+source of \LaTeX{} may be prepared by processing the file
+\File{source2e.tex} in the \LaTeX{} distribution. Such processing is
+noticeably tedious, but Heiko Oberdiek has prepared a well-linked
+\acro{PDF} version, which is in the file \File{base.tds.zip} of his
+\ProgName{latex-tds} distribution. Individual files in the \LaTeX{}
+distribution may be processed separately with \LaTeX{}, like any
+well-constructed \Qref*{\extension{dtx} file}{Q-dtx}.
+
+Writing good classes is not easy; it's a good idea to read some
+established ones (\File{classes.dtx}, for example, is the documented
+source of the standard classes other than \Class{Letter}, and may
+itself be formatted with \LaTeX{}). Classes that are not part of the
+distribution are commonly based on ones that are, and start by loading
+the standard class with \csx{LoadClass}~--- an example of this
+technique may be seen in \Package{ltxguide.cls}
+
+An % !! line break
+\href{http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf}{annotated version of \Class{article}},
+as it appears in \File{classes.dtx}, was published in
+\TUGboat{} 28(1). The article, by Peter Flynn, is a good guide to
+understanding \File{classes.dtx}
+\begin{ctanrefs}
+\item[classes.dtx]\CTANref{latex-classes}
+\item[clsguide.pdf]\CTANref{clsguide}
+\item[latex-tds \nothtml{rmfamily}collection]\CTANref{latex-tds}
+\item[ltxguide.cls]\CTANref{ltxguide}
+\item[\nothtml{\rmfamily}\LaTeX{} documentation]\CTANref{latexdoc}
+\item[source2e.tex]\CTANref{latex-source}
+\end{ctanrefs}
+\LastEdit{2011-07-19}
+
+\Question[Q-latex3-prog]{\latex{}3 programming}
+As yet, there is no book ``Programming in \latex{}3'', and even if
+such a thing existed there would be lots of gaps. So there is no
+\emph{comprehensive} support.
+
+However, there are some `resources':
+\begin{itemize}
+\item The ``introduction to \latex{}3 ideas'' in the \Package{expl3}
+ documentation gives a broad-brush overview of the concepts.
+\item Joseph Wright has written a short series of % !line break
+ \href{http://www.texdev.net/index.php?s=programming+latex3}{blog posts},
+ which may help.
+\item There is also a complete command reference in the
+ \Package{interface3} document.
+\end{itemize}
+
+The documents are still subject to development; some of the broader
+design issues are discussed on the \latex{} mailing list
+\texttt{latex-l}~--- you may subscribe to that list by sending a
+message by sending a message
+\begin{quote}
+ `\texttt{subscribe latex-l <\emph{your name}>}'
+\end{quote}
+to \mailto{listserv@urz.Uni-Heidelberg.de}
+\begin{ctanrefs}
+\item[expl3.pdf]\CTANref{expl3-doc}
+\item[interface3.pdf]\CTANref{interface3-doc}
+\end{ctanrefs}
+\LastEdit*{2012-11-29}
+
+\Question[Q-mfptutorials]{\MF{} and \MP{} Tutorials}
+
+Apart from Knuth's book, there seems to be only one publicly-available
+\href{http://metafont.tutorial.free.fr/}{tutorial for \MF{}}, by
+Christophe Grandsire (a copy in \acro{PDF} form may be downloaded).
+Geoffrey Tobin's \textit{\MF{} for Beginners} % !! line break
+(see \Qref[question]{using \MF{}}{Q-useMF}) describes how the \MF{}
+system works and how to avoid some of the potential pitfalls.
+
+Peter Wilson's experience of running both \MF{} and \MP{} (the
+programs), \textit{Some Experiences in Running \MF{} and \MP{}}
+(available on \ctan{}) offers the benefit of Peter's experience (he
+has designed a
+number of `historical' fonts using \MF{}). For \MF{} the article is
+geared towards testing and installing new \MF{} fonts, while its \MP{}
+section describes how to use \MP{} illustrations in \LaTeX{} and
+\PDFLaTeX{} documents, with an emphasis on how to use appropriate
+fonts for any text or mathematics.
+
+Hans Hagen (of \CONTeXT{} fame) offers a \MP{} tutorial called
+MetaFun (which admittedly concentrates on the use of \MP{} within
+\CONTeXT{}). It may be found on his company's % ! line break
+\href{http://www.pragma-ade.com/general/manuals/metafun-p.pdf}{`manuals' page}.
+
+Another \MP{} tutorial in English is: % ! line breaks
+\url{http://www.tlhiv.org/MetaPost/tutorial/} by Urs Oswald.
+One in French (listed here because it's clearly enough written
+that even this author understands it),
+\url{http://pauillac.inria.fr/~cheno/metapost/metapost.pdf}
+by Laurent Ch\'eno.
+
+Urs Oswald's tutorial uses Troy Henderson's tool
+(\URL{http://www.tlhiv.org/mppreview}) for testing little bits of
+\MP{}; it is an invaluable aid to the learner:
+\URL{http://www.tlhiv.org/mppreview}
+
+A three-part introduction, by Mari Voipio, was published in
+\href{http://tug.org/TUGboat/intromp/tb106voipio-grid.pdf}{\TUGboat34(1) (Entry-level \MP{}: On the grid)},
+\TUGboat34(2)
+\href{http://tug.org/TUGboat/intromp/tb107voipio-moveit.pdf}{(Entry-level \MP{}: Move it!\@)}, and
+\href{http://tug.org/TUGboat/intromp/tb108voipio-color.pdf}{\TUGboat34(2) (Entry-level \MP{}: Color)}.
+
+Vincent Zoonekynd's massive set of example \MP{} files is available on
+\acro{CTAN}; the set includes a \ProgName{Perl} script to convert the
+set to html, and the set may be % beware line break
+\href{http://zoonek.free.fr/LaTeX/Metapost/metapost.html}{viewed on the web}.
+While these examples don't exactly constitute a ``tutorial'', they're
+most certainly valuable learning material. Urs Oswald presents a
+\href{http://www.ursoswald.ch/metapost/tutorial.pdf}{similar document},
+written more as a document, and presented in \acro{PDF}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Beginners' guide]\CTANref{mf-beginners}
+\item[\nothtml{\rmfamily}Peter Wilson's ``experiences'']\CTANref{metafp-pdf}
+\item[\nothtml{\rmfamily}Vincent Zoonekynd's examples]\CTANref{zoon-mp-eg}
+\end{ctanrefs}
+\LastEdit{2014-02-18}
+
+\Question[Q-BibTeXing]{\bibtex{} Documentation}
+
+\bibtex{}, a program originally designed to produce bibliographies in
+conjunction with \LaTeX{}, is explained in Section~4.3 and Appendix~B
+of Leslie Lamport's \LaTeX{} manual.
+The document ``\bibtex{}ing'', in the \bibtex{} distribution (look for
+\File{btxdoc}),
+expands on the chapter in Lamport's book. \emph{The \LaTeX{} Companion}
+also has information on \bibtex{} and writing \bibtex{} style files.
+(See \Qref[question]{\latex{} books}{Q-latex-books} for details of both
+books.)
+
+The web site ``\href{http://www.bibtex.org}{Your \bibtex{} resource}''
+offers a solid introduction, but doesn't go into very great detail.
+
+The document ``Designing \bibtex{} Styles'', also in the \bibtex{}
+distribution (look for
+\File{btxhak}), explains the postfix stack-based language used to
+write \bibtex{} styles (\File{.bst} files). The file\File{btxbst.doc},
+also in the \bibtex{} distribution,
+is the template for the four standard styles (\Package{plain},
+\Package{abbrv}, \Package{alpha}, and \Package{unsrt}); it also
+contains their documentation.
+
+A useful tutorial of the whole process of using \bibtex{} is Nicolas
+Markey's ``\emph{Tame the BeaST (The B to X of \bibtex{})}'', which
+may also be found on \acro{CTAN}. A summary and \acro{FAQ} by Michael
+Shell and David Hoadley, is also to be recommended.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\bibtex{} distribution]\CTANref{bibtex}
+\item[\nothtml{\rmfamily}Shell and Hoadley's FAQ]\CTANref{bibtex-faq}
+\item[\nothtml{\rmfamily}Tame the BeaST]\CTANref{ttb-pdf}
+\end{ctanrefs}
+\LastEdit{2013-10-15}
+
+\Question[Q-symbols]{Where can I find the symbol for\,\dots{}}
+\keywords{assignment circular integral degrees diagonal dots Fourier transform}
+\keywords{Laplace greater less complex integer natural real}
+\keywords{cent euro}
+
+There is a wide range of symbols available for use with \TeX{}, most
+of which are not shown (or even mentioned) in \AllTeX{} books.
+\emph{The Comprehensive \LaTeX{} Symbol List} (by Scott Pakin
+% beware line wrap
+\emph{et al.}\@) illustrates over 2000 symbols, and details the
+commands and the \LaTeX{} packages needed to produce them.
+
+However, while the symbol list is a wonderful resource, it is never
+easy to find a particular symbol there. A graphical % ! line break
+\href{http://detexify.kirelabs.org/classify.html}{symbol search} is
+available on the web. The site provides you a scratch area on which
+you draw the symbol you're thinking of, with your mouse; when you've
+finished drawing, the classifier tries to match your sketch with
+symbols it knows about. The matching process is pretty good, even for
+the sketches of a \emph{really} poor draughtsman (such as the present
+author), and it's often worth trying more than once. `Detexify apps'
+are available for both Android and iPhone devices, you can use them to
+draw the symbol with your fingertip~--- a less challenging procedure
+than using your workstation's mouse, by all accounts!
+
+If you are using Unicode maths in \xetex{} or \luatex{}, your own
+distribution ought to provide the Unicode maths symbol table
+\File{unimath-symbols.pdf}; this lists the things available in the
+commonly-used mathematics fonts. (If the file isn't already available
+on your system, you can download it from \acro{CTAN}, where it live
+with the \Package{unicode-math} package.
+
+Other questions in this \acro{FAQ} offer specific help on kinds of
+symbols:
+\begin{itemize}
+\item \Qref*{Script fonts for mathematics}{Q-scriptfonts}
+\item \Qref*{Fonts for the number sets}{Q-numbersets}
+\item \Qref*{Typesetting the principal value integral}{Q-prinvalint}
+\end{itemize}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Symbol List]Browse \CTANref{symbols}; there
+ are processed versions \acro{PDF} form for both A4 and letter paper.
+\item[\nothtml{\rmfamily}Unicode maths symbols]Distributed as part of
+ \CTANref{unicode-math}
+\end{ctanrefs}
+\LastEdit{2012-09-03}
+
+\Question[Q-docpictex]{The \pictex{} manual}
+
+\pictex{} is a set of macros by Michael Wichura for drawing diagrams
+and pictures. The
+macros are freely available; however, the
+\pictex{} manual itself is not free.
+Unfortunately, \acro{TUG} is no longer able to supply copies of the
+manual (as it once did), and it is now available only through Personal
+\TeX{} Inc, the vendors of PC\TeX{} (\URL{http://www.pctex.com/}). The
+manual is \emph{not} available electronically.
+
+However, there \emph{is} a summary of \pictex{} commands available on
+\acro{CTAN}, which is a great aide-memoire for those who basically
+know the package to start with.
+\begin{ctanrefs}
+\item[\pictex{}]\CTANref{pictex}
+\item[\pictex{} summary]\CTANref{pictex-summary}
+\end{ctanrefs}
diff --git a/help/uk-tex-faq/faq-dvi.tex b/help/uk-tex-faq/faq-dvi.tex
new file mode 100644
index 0000000000..1b6ddf3cf4
--- /dev/null
+++ b/help/uk-tex-faq/faq-dvi.tex
@@ -0,0 +1,148 @@
+% $Id: faq-dvi.tex,v 1.2 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{\acro{DVI} Drivers and Previewers}
+
+\Question[Q-dvips]{\acro{DVI} to \PS{} conversion programs}
+
+The best public domain \acro{DVI} to \PS{} conversion program, which
+runs under many operating systems, is Tom Rokicki's \ProgName{dvips}.
+\ProgName{dvips} is written in \acro{C} and ports easily. All current
+development is in the context of Karl Berry's \ProgName{kpathsea}
+library, and sources are available from the \texlive{} repository,
+and versions are available in all \TeX{} distributions that recognise
+the use of \PS{}.
+
+An \acro{VMS} versions is available as part of the \acro{CTAN}
+distribution of \TeX{} for \acro{VMS}.
+
+A precompiled version to work with em\TeX{} is available on \acro{CTAN}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\MSDOS{} and \latexhtml{\acro{OS/}}{OS/}2]%
+ \CTANref{dvips-pc}
+\item[\nothtml{\rmfamily}VMS distribution]\CTANref{OpenVMSTeX}
+\end{ctanrefs}
+
+\Question[Q-HPdrivers]{\acro{DVI} drivers for \acro{HP} LaserJet}
+
+The em\TeX{} distribution (see \Qref[question]{\TeX{} systems}{Q-TeXsystems})
+contains a driver for the LaserJet, \ProgName{dvihplj}.
+
+Version 2.10 of the Beebe drivers supports the LaserJet. These drivers
+will compile under Unix, \acro{VMS}, and on the Atari ST and
+\acro{DEC}-20s.
+
+For Unix systems, Karl Berry's \ProgName{dviljk} uses the same
+path-searching library as \ProgName{web2c}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Beebe drivers]\CTANref{beebe}
+\item[dviljk]\CTANref{dviljk}
+\end{ctanrefs}
+
+\Question[Q-otherprinters]{Output to ``other'' printers}
+
+In the early years of \TeX{}, there were masses of \acro{DVI} drivers
+for any (then) imaginable kind of printer, but the steam seems rather
+to have gone out of the market for production of drivers for
+printer-specific formats. There are several reasons for this, but the
+primary one is that few formats offer the flexibility available
+through \PS{}, and with
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} (and its
+huge range of printer drivers) there is now little demand for new
+printer driver development.
+
+Thus, it is reasonable to \Qref*{generate \PS{}}{Q-dvips}, and
+use \href{http://www.ghostscript.com/}{\ProgName{ghostscript}} to send
+the resulting \PS{} output to the printer you actually have.
+
+(If you are using a Unix system of some sort, it's generally quite
+easy to insert
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} into the
+print spooling process, which makes printing \emph{really} simple.)
+\LastEdit{2013-05-29}
+
+\Question[Q-previewers]{\acro{DVI} previewers}
+
+Em\TeX{} for \acro{PC}s running \MSDOS{} or \acro{OS/}2, \miktex{} and
+XEm\TeX{} for \acro{PC}s running Windows and Oz\TeX{} for the Macintosh, all
+come with previewers that can be used on those platforms. Em\TeX{}'s
+previewer can also be run under Windows~3.1.
+
+Commercial \acro{PC} \TeX{} packages (see % ! line break
+\Qref[question]{commercial vendors}{Q-commercial})
+have good previewers for \acro{PC}s running Windows, or for Macintoshes.
+
+For Unix systems, there is one `canonical' viewer, \ProgName{xdvi}.
+\ProgName{Xdvik} is a version of \ProgName{xdvi} using the
+\ProgName{web2c} libraries; it is now built from the same distribution
+as \ProgName{xdvi}. The \texlive{} distributions for Unix systems
+include a version of \ProgName{xdvik}.
+
+Alternatives to previewing include
+\begin{itemize}
+\item conversion to `similar' \acro{ASCII} text (see
+ \Qref[question]{converting to \acro{ASCII}}{Q-toascii}) and using a
+ conventional text viewer to look at that,
+\item generating a \PS{} version of your document and viewing it
+ with a
+ \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}-based
+ previewer (see
+ \Qref[question]{previewing \PS{} files}{Q-PSpreview}), and
+\item generating \acro{PDF} output, and viewing that with
+ \ProgName{Acrobat} \ProgName{Reader} or one of the substitutes for that.
+\end{itemize}
+\begin{ctanrefs}
+\item[xdvi]\CTANref{xdvi}
+\end{ctanrefs}
+\LastEdit{2013-04-11}
+
+\Question[Q-dvi-bmp]{Generating bitmaps from \acro{DVI}}
+
+In the last analysis, any \acro{DVI} driver or previewer is generating
+bitmaps: bitmaps for placing tiny dots on paper via a laser- or
+inkjet-printer, or bitmaps for filling some portion of your screen.
+However, it's usually difficult to extract any of those bitmaps any
+way other than by screen capture, and the resolution of \emph{that} is
+commonly lamentable.
+
+Why would one want separate bitmaps? Most often, the requirement is for
+something that can be included in \acro{HTML} generated from \AllTeX{}
+source~--- not everything that you can write in \AllTeX{} can be
+translated to \acro{HTML} (at least, portable \acro{HTML} that may be
+viewed in `most' browsers), so the commonest avoiding action is to
+generate a bitmap of the missing bit. Examples are maths (a maths
+extension to the `|*|\acro{ML}' family is available but not
+universally supported by browsers), and `exotic' typescripts (ones
+that you cannot guarantee your readers will have available). Other
+common examples are generation of
+sample bitmaps, and generation for insertion into some other
+application's display~--- to insert equations into Microsoft
+PowerPoint, or to support the enhanced-\ProgName{emacs} setup called
+\Qref*{\ProgName{preview}-\ProgName{latex}}{Q-WYGexpts}.
+
+In the past, the commonest way of generating bitmaps was to generate a
+\PS{} file of the \acro{DVI} and then use
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} to
+produce the required bitmap format (possibly by way of \acro{PNM}
+format or something similar). This is an undesirable procedure (it is
+tedious, involving requires two or three steps that run slowly) but it
+served for a long time.
+
+\AllTeX{} users may now take advantage of two bitmap `drivers'. The
+longer-established, \ProgName{dvi2bitmap}, will generate \acro{XBM} and
+\acro{XPM} formats, the long-deprecated \acro{GIF} format (which is
+now obsolescent, but has finally been relieved of the patent
+protection of the \acro{LZW} compression it uses), and also
+the modern (\acro{ISO}-standardised) \acro{PNG} format.
+
+\ProgName{Dvipng} started out as a PNG renderer; from version 1.2 it can also
+render to the GIF format. It is designed for speed, in environments that
+generate large numbers of \acro{PNG} files: the \File{README} mentions
+\ProgName{preview}-\ProgName{latex}, \ProgName{LyX}, and a few
+web-oriented environments. Note that \ProgName{dvipng} gives
+high-quality output even though its internal operations are optimised
+for speed.
+\begin{ctanrefs}
+\item[dvi2bitmap]\CTANref{dvi2bitmap}
+\item[dvipng]\CTANref{dvipng}
+\end{ctanrefs}
+\LastEdit{2013-04-19}
diff --git a/help/uk-tex-faq/faq-fmt-conv.tex b/help/uk-tex-faq/faq-fmt-conv.tex
new file mode 100644
index 0000000000..d555e6f1a6
--- /dev/null
+++ b/help/uk-tex-faq/faq-fmt-conv.tex
@@ -0,0 +1,465 @@
+% $Id: faq-fmt-conv.tex,v 1.10 2014/05/29 11:24:34 rf10 Exp rf10 $
+
+\section{Format conversions}
+
+\Question[Q-toascii]{Conversion from \AllTeX{} to plain text}
+
+The aim here is to emulate the Unix \ProgName{nroff}, which formats
+text as best it can for the screen, from the same
+input as the Unix typesetting program \ProgName{troff}.
+
+Converting \acro{DVI} to plain text is the basis of many of these
+techniques; sometimes the simple conversion provides a good enough
+response. Options are:
+\begin{itemize}
+\item \ProgName{dvi2tty} (one of the earliest),
+\item \ProgName{crudetype} and
+\item \ProgName{catdvi}, which is capable of generating Latin-1
+ (ISO~8859-1) or \acro{UTF}-8 encoded output. \ProgName{Catdvi} was
+ conceived as a replacement for \ProgName{dvi2tty}, but development
+ seems to have stopped before the authors were willing to declare the
+ work complete.
+\end{itemize}
+A common problem is the hyphenation that \TeX{} inserts when
+typesetting something: since the output is inevitably viewed using
+fonts that don't match the original, the hyphenation usually looks
+silly.
+
+Ralph Droms provides a \Package{txt} bundle of things in support of
+\acro{ASCII} generation,
+but it doesn't do a good job with tables and mathematics.
+
+Another possibility is to
+use the \LaTeX{}-to-\acro{ASCII} conversion program, \ProgName{l2a},
+although this is really more of a de-\TeX{}ing program.
+
+The canonical de-\TeX{}ing program is \ProgName{detex}, which removes
+all comments and control sequences
+from its input before writing it to its output. Its original purpose
+was to prepare input for a dumb spelling checker, and it's only usable
+for preparing useful \acro{ASCII} versions of a document in highly
+restricted circumstances.
+
+\ProgName{Tex2mail} is slightly more than a de-TeX{}er~--- it's a
+\ProgName{Perl} script that converts \TeX{} files into
+plain text files, expanding various mathematical symbols
+(sums, products, integrals, sub/superscripts, fractions, square
+roots, \dots{}\@) into ``\acro{ASCII} art'' that spreads over
+multiple lines if necessary. The result is more readable to human
+beings than the flat-style \TeX{} code.
+
+Another significant possibility is to use one of the
+\Qref*{\acro{HTML}-generation solutions}{Q-LaTeX2HTML},
+and then to use a browser such as \ProgName{lynx} to dump the resulting
+\acro{HTML} as plain text.
+\begin{ctanrefs}
+\item[catdvi]\CTANref{catdvi}
+\item[crudetype]\CTANref{crudetype}
+\item[detex]\CTANref{detex}
+\item[dvi2tty]\CTANref{dvi2tty}
+\item[l2a]\CTANref{l2a}
+\item[tex2mail]\CTANref{tex2mail}
+\item[txt]\CTANref{txtdist}
+\end{ctanrefs}
+\LastEdit{2011-07-21}
+
+\Question[Q-SGML2TeX]{Conversion from \acro{SGML} or \acro{HTML} to \protect\TeX{}}
+
+\acro{SGML} is a very important system for document storage and interchange,
+but it has no formatting features; its companion \acro{ISO} standard
+\acro{DSSSL}
+(see \URL{http://www.jclark.com/dsssl/}) is designed for writing
+transformations and formatting,
+but this has not yet been widely implemented. Some \acro{SGML} authoring
+systems (e.g., SoftQuad \ProgName{Author/Editor}) have formatting
+abilities, and
+there are high-end specialist \acro{SGML} typesetting systems (e.g., Miles33's
+\ProgName{Genera}). However, the majority of \acro{SGML} users probably transform
+the source to an existing typesetting system when they want to print.
+\TeX{} is a good candidate for this. There are three approaches to writing a
+translator:
+\begin{enumerate}
+\item Write a free-standing translator in the traditional way, with
+ tools like \ProgName{yacc} and \ProgName{lex}; this is hard, in
+ practice, because of the complexity of \acro{SGML}.
+\item Use a specialist language designed for \acro{SGML} transformations; the
+ best known are probably \ProgName{Omnimark} and \ProgName{Balise}.
+ They are expensive, but powerful, incorporating \acro{SGML} query and
+ transformation abilities as well as simple translation.
+\item Build a translator on top of an existing \acro{SGML} parser. By far
+ the best-known (and free!) parser is James Clark's
+ \ProgName{nsgmls}, and this produces a much simpler output format,
+ called \acro{ESIS}, which can be parsed quite straightforwardly (one also
+ has the benefit of an \acro{SGML} parse against the \acro{DTD}). Two
+ good public domain packages use this method:
+ \begin{itemize}
+ \item
+\begin{narrowversion} % really non-hyper
+ David Megginson's \ProgName{sgmlspm}, written in \ProgName{Perl}
+ 5, which is available from
+ \URL{http://www.perl.com/CPAN/modules/by-module/SGMLS}
+\end{narrowversion}
+\begin{wideversion}
+ David Megginson's
+ \href{http://www.perl.com/CPAN/modules/by-module/SGMLS}{\ProgName{sgmlspm}},
+ written in \ProgName{Perl} 5.
+\end{wideversion}
+ \item
+\begin{narrowversion} % really non-hyper
+ Joachim Schrod and Christine Detig's \ProgName{STIL}
+ (`\acro{SGML} Transformations in Lisp'), which is available from
+ \URL{ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil}
+\end{narrowversion}
+\begin{wideversion}
+ Joachim Schrod and Christine Detig's
+ \href{ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil}{\ProgName{STIL}},
+ (`\acro{SGML} Transformations in Lisp').
+\end{wideversion}
+ \end{itemize}
+ Both of these allow the user to write `handlers' for every \acro{SGML}
+ element, with plenty of access to attributes, entities, and
+ information about the context within the document tree.
+
+ If these packages don't meet your needs for an average \acro{SGML}
+ typesetting job, you need the big commercial stuff.
+\end{enumerate}
+
+Since \acro{HTML} is simply an example of \acro{SGML}, we do not need a specific
+system for \acro{HTML}. However, Nathan Torkington developed
+% (\Email{Nathan.Torkington@vuw.ac.nz})
+\ProgName{html2latex} from the \acro{HTML} parser in \acro{NCSA}'s
+Xmosaic package.
+The program takes an \acro{HTML} file and generates a \LaTeX{} file from it.
+The conversion code is subject to \acro{NCSA} restrictions, but the whole
+source is available on \acro{CTAN}.
+
+Michel Goossens and Janne Saarela published a very useful summary of
+\acro{SGML}, and of public domain tools for writing and manipulating it, in
+\TUGboat{} 16(2).
+\begin{ctanrefs}
+\item[html2latex \nothtml{\rmfamily}source]\CTANref{html2latex}
+\end{ctanrefs}
+
+\Question[Q-LaTeX2HTML]{Conversion from \AllTeX{} to \acro{HTML}}
+
+\TeX{} and \LaTeX{} are well suited to producing electronically publishable
+documents. However, it is important to realize the difference
+between page layout and functional markup. \TeX{} is capable of
+extremely detailed page layout; \acro{HTML} is not, because \acro{HTML} is a
+functional markup language not a page layout language. \acro{HTML}'s exact
+rendering is not specified by the document that is published but is, to
+some degree, left to the discretion of the browser. If you require your
+readers to see an exact replication of what your document looks like
+to you, then you cannot use \acro{HTML} and you must use some other
+publishing format such as \acro{PDF}. That is true for any \acro{HTML}
+authoring tool.
+
+\TeX{}'s excellent mathematical capabilities remain a challenge in the
+business of conversion to \acro{HTML}. There are only two generally
+reliable techniques for generating mathematics on the web: creating
+bitmaps of bits of typesetting that can't be translated, and using
+symbols and table constructs. Neither technique is entirely
+satisfactory. Bitmaps lead to a profusion of tiny files, are slow to
+load, and are inaccessible to those with visual disabilities. The
+symbol fonts offer poor coverage of mathematics, and their use
+requires configuration of the browser. The future of mathematical
+browsing may be brighter~--- see
+% beware line break
+\Qref[question]{future Web technologies}{Q-mathml}.
+
+For today, possible packages are:
+\begin{description}
+\item[\ProgName{LaTeX2HTML}]a \ProgName{Perl} script package that
+ supports \LaTeX{} only, and generates mathematics (and other
+ ``difficult'' things) using bitmaps. The original version was
+ written by Nikos Drakos for Unix systems, but the package now sports
+ an illustrious list of co-authors and is also available for Windows
+ systems. Michel Goossens and Janne Saarela published a detailed
+ discussion of \ProgName{LaTeX2HTML}, and how to tailor it, in
+ \TUGboat{} 16(2).
+
+ A mailing list for users may be found via
+ \URL{http://tug.org/mailman/listinfo/latex2html}
+\item[\ProgName{TtH}]a compiled program that supports either \LaTeX{}
+ or \plaintex{}, and uses the font/table technique for representing
+ mathematics. It is written by Ian Hutchinson, using
+ \ProgName{flex}. The distribution consists of a single \acro{C}
+ source (or a compiled executable), which is easy to install and very
+ fast-running.
+\item[\ProgName{TeX4ht}]a compiled program that supports either
+ \LaTeX{} or \plaintex{}, by processing a \acro{DVI} file; it uses
+ bitmaps for mathematics, but can also use other technologies where
+ appropriate. Written by Eitan Gurari, it parses the \acro{DVI}
+ file generated when you run \AllTeX{} over your file with
+ \ProgName{tex4ht}'s macros included. As a result, it's pretty
+ robust against the macros you include in your document, and it's
+ also pretty fast.
+\item[\ProgName{plasTeX}]a Python-based \LaTeX{} document processing
+ framework. It gives DOM-like access to a \LaTeX{} document, as
+ well as the ability to generate mulitple output formats
+ (e.g. HTML, DocBook, tBook, etc.).
+\item[\ProgName{TeXpider}]a commercial program from
+ \Qref*{Micropress}{Q-commercial}, which is
+ described on \URL{http://www.micropress-inc.com/webb/wbstart.htm};
+ it uses bitmaps for equations.
+\item[\ProgName{Hevea}] a compiled program that supports \LaTeX{}
+ only, and uses the font/table technique for equations (indeed its
+ entire approach is very similar to \ProgName{TtH}). It is written
+ in Objective \acro{CAML} by Luc Maranget. \ProgName{Hevea} isn't
+ archived on \acro{CTAN}; details (including download points) are
+ available via \URL{http://pauillac.inria.fr/~maranget/hevea/}
+\end{description}
+An interesting set of samples, including conversion of the same text
+by the four free programs listed above, is available at
+\URL{http://www.mayer.dial.pipex.com/samples/example.htm}; a linked
+page gives lists of pros and cons, by way of comparison.
+
+The World Wide Web Consortium maintains a list of ``filters'' to
+\acro{HTML}, with sections on \AllTeX{} and \BibTeX{}~--- see
+\URL{http://www.w3.org/Tools/Word_proc_filters.html}
+\begin{ctanrefs}
+\item[latex2html]Browse \CTANref{latex2html}
+\item[plasTeX]Browse \CTANref{plastex}
+\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/})
+\item[tth]\CTANref{tth}
+\end{ctanrefs}
+
+\Question[Q-fmtconv]{Other conversions to and from \AllTeX{}}
+
+\begin{description}
+\item[troff]\ProgName{Tr2latex}, assists in the translation of a
+ \ProgName{troff} document into \LaTeXo{} format. It recognises most
+ |-ms| and |-man| macros, plus most \ProgName{eqn} and some
+ \ProgName{tbl} preprocessor commands. Anything fancier needs to be
+ done by hand. Two style files are provided. There is also a man page
+ (which converts very well to \LaTeX{}\dots{}).
+ \ProgName{Tr2latex} is an enhanced version of the earlier
+ \ProgName{troff-to-latex} (which is no longer available).
+
+% The \acro{DECUS} \TeX{} distribution (see
+% \Qref[question]{sources of software}{Q-archives})
+% also contains a program which converts \ProgName{troff} to \TeX{}.
+
+%\item[Scribe] Mark James (\Email{jamesm@dialogic.com}) has a copy of
+% \ProgName{scribe2latex} he has been unable to test but which he will
+% let anyone interested have. The program was written by Van Jacobson
+% of Lawrence Berkeley Laboratory.%
+% \checked{RF}{1994/11/18}
+
+\item[WordPerfect] \ProgName{wp2latex} is actively maintained, and is
+ available either for \MSDOS{} or for Unix systems.
+\item[\acro{RTF}] \ProgName{Rtf2tex}, by Robert Lupton, is for
+ converting Microsoft's Rich Text Format to \TeX{}. There is also a
+ converter to \LaTeX{} by Erwin Wechtl, called \ProgName{rtf2latex}.
+ The latest converter, by Ujwal Sathyam and Scott Prahl, is
+ \ProgName{rtf2latex2e} which seems rather good, though development
+ of it seems to have stalled.
+
+ Translation \emph{to} \acro{RTF} may be done (for a somewhat
+ constrained set of \LaTeX{} documents) by \TeX{}2\acro{RTF}, which
+ can produce ordinary \acro{RTF}, Windows Help \acro{RTF} (as well as
+ \acro{HTML}, \Qref{conversion to HTML}{Q-LaTeX2HTML}).
+ \TeX{}2\acro{RTF} is supported on various Unix platforms and under
+ Windows~3.1
+\item[Microsoft Word] A rudimentary (free) program for converting
+ \acro{MS-W}ord to \LaTeX{} is \ProgName{wd2latex}, which runs on \MSDOS{};
+ it probably processes the output of an archaic version of
+ \acro{MS-W}ord (the program itself was archived in 1991).
+
+ For conversion in the other direction, the current preferred
+ free-software method is a two-stage process:
+ \begin{itemize}
+ \item Convert \latex{} to \ProgName{OpenOffice} format, using the
+ \ProgName{tex4ht} command \ProgName{oolatex};
+ \item open the result in \ProgName{OpenOffice} and `save as' a
+ \acro{MS-W}ord document.
+ \end{itemize}
+ (Note that \ProgName{OpenOffice} itself is \emph{not} on
+ \acro{CTAN}; see \url{http://www.openoffice.org/}, though most
+ \ProgName{linux} systems offer it as a ready-to-install bundle.)
+
+ \ProgName{tex4ht} can also generate OpenOffice \acro{ODT}
+ format, which may be used as an intermediate to producing Word
+ format files.
+
+ \ProgName{Word2}\emph{\TeX{}} and \emph{\TeX{}}\ProgName{2Word} are
+ shareware translators from % beware line break
+ \href{http://www.chikrii.com/}{Chikrii Softlab}; positive users'
+ reports have been noted (but not recently).
+
+ If cost is a constraint, the best bet is probably to use an
+ intermediate format such as \acro{RTF} or \acro{HTML}.
+ \ProgName{Word} outputs and reads both, so in principle this route
+ may be useful.
+
+ You can also use \acro{PDF} as an intermediate format: Acrobat Reader
+ for Windows (version 5.0 and later) will output rather feeble
+ \acro{RTF} that \ProgName{Word} can read.
+\item[Excel] \ProgName{Excel2Latex} converts an \ProgName{Excel} file
+ into a \LaTeX{} \environment{tabular} environment; it comes as a
+ \extension{xls} file which defines some \ProgName{Excel} macros to produce
+ output in a new format.
+\item[runoff] Peter Vanroose's \ProgName{rnototex}
+ conversion program is written in \acro{VMS} Pascal.
+ The sources are distributed with a \acro{VAX} executable.
+\item[refer/tib] There are a few programs for converting bibliographic
+ data between \BibTeX{} and \ProgName{refer}/\ProgName{tib} formats.
+ The collection includes a shell script converter from \BibTeX{} to
+ \ProgName{refer} format as well. The collection
+ is not maintained.
+\item[\acro{PC}-Write]\ProgName{pcwritex.arc} is a
+ print driver for \acro{PC}-Write that ``prints'' a \acro{PC}-Write
+ V2.71 document to a \TeX{}-compatible disk file. It was written by Peter
+ Flynn at University College, Cork, Republic of Ireland.
+\end{description}
+
+% beware line breaks
+\href{http://www.tug.org/utilities/texconv/index.html}{Wilfried Hennings' \acro{FAQ}},
+which deals specifically with conversions between \TeX{}-based formats
+and word processor formats, offers much detail as well as tables that
+allow quick comparison of features.
+
+A group at Ohio State University (\acro{USA}) is working on
+a common document format based on \acro{SGML}, with the ambition that any
+format could be
+translated to or from this one. \ProgName{FrameMaker} provides
+``import filters'' to aid translation from alien formats
+(presumably including \TeX{}) to \ProgName{FrameMaker}'s own.
+\begin{ctanrefs}
+\item[excel2latex]\CTANref{excel2latex}
+\item[pcwritex.arc]\CTANref{pcwritex}
+\item[refer and tib tools]\CTANref{refer-tools}
+\item[rnototex]\CTANref{rnototex}
+\item[rtf2latex]\CTANref{rtf2latex}
+\item[rtf2latex2e]\CTANref{rtf2latex2e}
+\item[rtf2tex]\CTANref{rtf2tex}
+\item[tex2rtf]\CTANref{tex2rtf}
+\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/})
+\item[tr2latex]\CTANref{tr2latex}
+\item[wd2latex]\CTANref{wd2latex}
+\item[wp2latex]\CTANref{wp2latex}
+\item[\nothtml{\rmfamily}Word processor \acro{FAQ} (source)]%
+ \CTANref{texcnvfaq}
+\end{ctanrefs}
+
+\Question[Q-readML]{Using \TeX{} to read \acro{SGML} or \acro{XML} directly}
+
+\Qref*{\context{} (mark \acro{IV})}{Q-context} can process some
+\acro{*ML}, to produce typeset output directly. Details of what can
+(and can not) be done, are discussed in % ! line break
+\href{http://wiki.contextgarden.net/XML}{The \context{} \acro{WIKI}}.
+\context{} is probably the system of choice for \alltex{} users who
+also need to work in \acro{XML} (and friends). (Note that \context{}
+mark~\acro{IV} requires \Qref*{\luatex{}}{Q-luatex}, and should
+therefore be regarded as experimental, though many people \emph{do}
+use it successfully).
+
+Older systems also manage, using no more than \alltex{} macro
+programming, to process \acro{XML} and the like. David Carlisle's
+\Package{xmltex} is the prime example; it offers a solution
+for typesetting \acro{XML} files, and is still in active (though not
+very widespread) use.
+
+One use of a \TeX{} that can typeset \acro{XML} files is as a backend
+processor for \acro{XSL} formatting objects, serialized as \acro{XML}.
+Sebastian Rahtz's Passive\TeX{} uses \Package{xmltex} to
+achieve this end.
+
+However, modern usage would proceed via \acro{XSL} or \acro{XSLT}2 to
+produce a formattable version.
+\begin{ctanrefs}
+\item[Context]\CTANref{context}
+\item[xmltex]\CTANref{xmltex}
+\item[passivetex]\CTANref{passivetex}
+\end{ctanrefs}
+\LastEdit{2013-04-11}
+
+\Question[Q-recovertex]{Retrieving \AllTeX{} from \acro{DVI}, etc.}
+
+The job just can't be done automatically: \acro{DVI}, \PS{} and
+\acro{PDF} are ``final'' formats, supposedly not susceptible to
+further editing~--- information about where things came from has been
+discarded. So if you've lost your \AllTeX{} source (or never
+had the source of a document you need to work on) you've a serious job
+on your hands. In many circumstances, the best strategy is to retype
+the whole document, but this strategy is to be tempered by
+consideration of the size of the document and the potential typists'
+skills.
+
+If automatic assistance is necessary, it's unlikely that any more than
+text retrieval is going to be possible; the \AllTeX{} markup that
+creates the typographic effects of the document needs to be recreated
+by editing.
+
+If the file you have is in \acro{DVI} format, many of the techniques
+for \Qref*{converting \AllTeX{} to \acro{ASCII}}{Q-toascii} are
+applicable. Consider \ProgName{dvi2tty}, \ProgName{crudetype} and
+\ProgName{catdvi}. Remember that there are likely to be problems
+finding included material (such as included \PS{} figures, that
+don't appear in the \acro{DVI} file itself), and mathematics is
+unlikely to convert easily.
+
+To retrieve text from \PS{} files, the
+\ProgName{ps2ascii} tool (part of the
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+distribution) is available. One could try applying this tool to
+\PS{} derived from an \acro{PDF} file using \ProgName{pdf2ps} (also
+from the \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+distribution), or \ProgName{Acrobat}
+\ProgName{Reader} itself; an alternative is \ProgName{pdftotext},
+which is distributed with \ProgName{xpdf}.
+
+Another avenue available to those with a \acro{PDF} file they want to
+process is offered by Adobe \ProgName{Acrobat} (version 5 or later):
+you can tag the \acro{PDF} file into an estructured document, output
+thence to well-formed \acro{XHTML}, and import the results into
+Microsoft \ProgName{Word} (2000 or later). From there, one may
+convert to \AllTeX{} using one of the techniques discussed in
+% beware line break
+\wideonly{``}\Qref[question]{converting to and from \AllTeX{}}{Q-fmtconv}\wideonly{''}.
+
+The result will typically (at best) be poorly marked-up. Problems may
+also arise from the oddity of typical \TeX{} font encodings (notably
+those of the maths fonts), which \ProgName{Acrobat} doesn't know how
+to map to its standard Unicode representation.
+\begin{ctanrefs}
+\item[catdvi]\CTANref{catdvi}
+\item[crudetype]\CTANref{crudetype}
+\item[dvi2tty]\CTANref{dvi2tty}
+\item[xpdf]Browse \CTANref{xpdf}
+\end{ctanrefs}
+\LastEdit{2013-04-16}
+
+\Question[Q-LaTeXtoPlain]{Translating \LaTeX{} to \plaintex{}}
+
+Unfortunately, no ``general'', simple, automatic process is likely to
+succeed at this task. See % ! line break
+``\Qref*{How does \LaTeX{} relate to \plaintex{}}{Q-LaTeXandPlain}''
+for further details.
+
+Obviously, trivial documents will translate in a trivial way.
+Documents that use even relatively simple things, such as labels and
+references, are likely to cause trouble (\plaintex{} doesn't support
+labels). While graphics are in principle covered, by the \plaintex{}
+
+Translating a document designed to work with \LaTeX{} into one
+that will work with \plaintex{} is likely to amount to carefully
+including (or otherwise re-implementing) all those parts of \LaTeX{},
+beyond the provisions of \plaintex{}, which the document uses.
+
+Some of this work has (in a sense) been done, in the port of the
+\LaTeX{} graphics package to \plaintex{}. However, while
+\Package{graphics} is available, other complicated packages (notably
+\Package{hyperref}) are not. The aspiring translator may find the
+\Qref*{\Eplain{}}{Q-eplain} system a useful source of code. (In fact,
+a light-weight system such as \Eplain{} might reasonably be adopted as
+an alternative target of translation, though it undoubtedly gives the
+user more than the ``bare minimum'' that \plaintex{} is designed to
+offer.)
+\begin{ctanrefs}
+\item[\nothtml{\begingroup\rmfamily}The\nothtml{\endgroup} eplain \nothtml{\rmfamily}system]%
+ \CTANref{eplain}
+\item[\nothtml{\begingroup\rmfamily'}\plaintex{}\nothtml{'\endgroup} graphics]%
+ \CTANref{graphics-plain}
+\end{ctanrefs}
+\LastEdit{2011-05-30}
diff --git a/help/uk-tex-faq/faq-fonts.tex b/help/uk-tex-faq/faq-fonts.tex
new file mode 100644
index 0000000000..c60bce4f54
--- /dev/null
+++ b/help/uk-tex-faq/faq-fonts.tex
@@ -0,0 +1,1316 @@
+% $Id: faq-fonts.tex,v 1.21 2014/01/22 17:29:03 rf10 Exp $
+
+\section{Fonts}
+
+\subsection{Adobe Type~1 (``\PS{}'') fonts}
+
+\Question[Q-usepsfont]{Using Adobe Type 1 fonts with \protect\TeX{}}
+
+In order to use any font, \TeX{} needs a
+\emph{metric} file (\acro{TFM} file). Several sets of metrics for
+common Adobe Type 1 fonts are
+available from the archives; for mechanisms for generating new ones,
+see \Qref[question]{metrics for \PS{} fonts}{Q-metrics}. You
+also need the fonts themselves; \PS{} printers come with a set of
+fonts built in, but to extend your repertoire you usually
+need to buy from one of the many commercial font vendors (see, for
+example, \Qref[question]{``choice of fonts''}{Q-psfchoice}).
+
+If you use \LaTeXe{}, access to your printer's fonts is offered by the
+\acro{PSNFSS} package; the \LaTeX{}3 project team declare that
+\acro{PSNFSS} is a ``required'' part of a \latex{} distribution, and
+bug reports may be submitted via the % ! line break
+\Qref*{\LaTeX{} bugs system}{Q-latexbug}.
+\acro{PSNFSS} gives you a set of packages for changing the default
+roman, sans-serif and typewriter fonts; \emph{e.g}., the
+\Package{mathptmx} package will set up \FontName{Times}
+\FontName{Roman} as the main text font (and introduces mechanisms to
+typeset mathematics using \FontName{Times} and various more-or-less
+matching fonts), while package \Package{avant} changes the sans-serif
+family to \FontName{AvantGarde}, and \Package{courier} changes the
+typewriter font to \FontName{Courier}. To go with these
+packages, you need the font metric files
+and font description (\File{.fd}) files for each font family you
+want to use. For convenience,
+metrics for the `common 35' \PS{} fonts found in most \PS{} printers
+are provided with \acro{PSNFSS}, packaged as the ``Laserwriter set''.
+
+For older versions of \LaTeX{} there are various schemes, of which the
+simplest to use is probably the \acro{PS}\LaTeX{} macros distributed with
+\ProgName{dvips}.
+
+For \plaintex{}, you load whatever fonts you like; if the encoding of
+the fonts is not the same as Computer Modern it will be up to you to
+redefine various macros and accents, or you can use the font
+re-encoding mechanisms available in many drivers and in
+\ProgName{ps2pk} and \ProgName{afm2tfm}.
+
+Some common problems encountered are discussed elsewhere
+(see \Qref[question]{problems with \acro{PS} fonts}{Q-psfontprob}).
+\begin{ctanrefs}
+\item[Metrics for the `Laserwriter' set of 35 fonts]\CTANref{lw35nfss-zip}
+\item[psnfss]\CTANref{psnfss}
+\end{ctanrefs}
+
+\Question[Q-PSpreview]{Previewing files using Type 1 fonts}
+
+Originally, free \TeX{} previewers were only capable of displaying
+bitmap (\acro{PK}) fonts, but free Type~1 font rendering software has
+been available for some time, and many previewers now use such
+facilities.
+
+The alternative, for previewers, is automatic generation of the
+requisite \acro{PK} files (using \ProgName{gsftopk}, or similar,
+behind the scenes).
+
+In the unlikely event that your previewer isn't capable of either, you
+have a couple options:
+\begin{itemize}
+\item Convert the \acro{DVI} file to \PS{} and use a
+ \PS{} previewer. Some systems offer this capability as
+ standard, but most people will need to use a separate previewer such
+ as \href{http://www.ghostscript.com/}{\ProgName{ghostscript}} or
+ \ProgName{ghostscript}-based viewers
+ such as (free) \ProgName{gv} or (shareware)
+ \href{http://www.ghostgum.com.au/}{\ProgName{gsview}}.
+% \item Under Windows on a \acro{PC}, or on a Macintosh, let Adobe Type Manager
+% display the fonts (textures, on the Macintosh, works like this).
+% %% , and under
+% %% Windows you can use \YandY{}'s \ProgName{dviwindo} for bitmap-free
+% %% previewing.
+% \begin{narrowversion} % really hyper
+% (See \Qref[question]{}{Q-commercial} for details of these
+% suppliers.)
+% \end{narrowversion}
+% %\typeout{after narrowversion, before wideversion}
+% \begin{wideversion}
+% (See \Qref{commercial suppliers}{Q-commercial} for details.)
+% \end{wideversion}
+% %\typeout{after wideversion}
+\item If you have the \PS{} fonts in Type~1 format, use
+ \ProgName{ps2pk} or \ProgName{gsftopk} (designed for use with the
+ \href{http://www.ghostscript.com/}{\ProgName{ghostscript}} fonts) to
+ make \acro{PK} bitmap fonts which
+ your previewer will understand (a process similar to the way some
+ browsers fo the job `automatically') This can produce adequate results,
+ also suitable for printing with non-\PS{} devices. (Note: if you
+ purchased the fonts, it is advisable to check that their licence
+ permits you to convert them, for private use, in this way.)
+\end{itemize}
+\begin{ctanrefs}
+\item[gsftopk]\CTANref{gsftopk}
+\item[gv]Browse \CTANref{gv}
+\item[ps2pk]\CTANref{ps2pk}
+\end{ctanrefs}
+
+\Question[Q-metrics]{\TeX{} font metric files for Type 1 fonts}
+
+Reputable font vendors such as Adobe supply metric files for each
+font, in \acro{AFM} (Adobe Font Metric) form; these can be converted
+to \acro{TFM} (\TeX{} Font Metric) form. Most modern distributions have
+prebuilt metrics which will be more than enough for many people; but you may
+need to do the conversion yourself if you have special needs or
+acquire a new font. One important question is the \emph{encoding} of
+(Latin character) fonts; while we all more or less agree about the
+position of about 96 characters in fonts (the basic \acro{ASCII} set), the
+rest of the (typically) 256 vary. The most obvious problems are with
+floating accents and special characters such as the `pounds sterling'
+sign. There are three ways of dealing with this: either you change the
+\TeX{} macros which reference the characters (not much fun, and
+error-prone); or you change the encoding of the font (easier than you
+might think); or you use \Qref*{virtual fonts}{Q-virtualfonts} to
+\emph{pretend} to \TeX{} that the encoding is the same as it is used to.
+\LaTeXe{} has facilities for dealing with fonts in different
+encodings; read the \Qref*{\emph{\LaTeX{} Companion}}{Q-latex-books} for
+more details. In practice, if you do much non-English (but Latin
+script) typesetting, you are strongly recommended to use the
+\Package{fontenc} package with option `\pkgoption{T1}' to select
+\Qref*{`Cork'}{Q-ECfonts} encoding.
+
+An alternative favoured by some is \YandY{}'s ``private'' \acro{LY}1 encoding,
+which is designed to sit well with ``Adobe standard'' encoded fonts.
+Basic macro support of \acro{LY}1 is available: note that the
+``relation with Adobe's encoding'' means that the \acro{LY}1 user
+needs no virtual fonts.
+
+Alan Jeffrey's \ProgName{fontinst} package is an \acro{AFM} to
+\acro{TFM} converter written in \TeX{}; it is used to generate the
+files used by \LaTeXe{}'s \acro{PSNFSS} package to support use of
+\PS{} fonts. It is a sophisticated package, not for the faint-hearted,
+but is powerful enough to cope with most needs. Much of its power
+relies on the use of \Qref*{virtual fonts}{Q-virtualfonts}.
+
+For slightly simpler problems, Rokicki's \ProgName{afm2tfm},
+distributed with \ProgName{dvips}, is fast and
+efficient; note that the metrics and styles that come with
+\ProgName{dvips} are \emph{not} currently \LaTeXe{} compatible.
+
+For the Macintosh (classic), there is a program called
+\ProgName{EdMetrics} which does the job (and more).
+\ProgName{EdMetrics} comes with the (commercial)
+\Qref*{Textures}{Q-commercial} distribution, but is itself free
+software, and is available on \acro{CTAN}.
+%% \par
+%% Windows users can buy \Qref*{\YandY{}'s}{Q-commercial}
+%% Font Manipulation Tools package which includes a powerful
+%% \ProgName{afmtotfm} program among many other goodies.
+\begin{ctanrefs}
+\item[dvips]\CTANref{dvips}
+\item[EdMetrics]\CTANref{edmetrics}
+\item[fontinst]\CTANref{fontinst}
+\item[LY1 support]\CTANref{ly1}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-psfontprob]{Deploying Type 1 fonts}
+
+For the \LaTeX{} user trying to use the
+\Qref*{\acro{PSNFSS}}{Q-usepsfont} package, three questions may arise.
+
+First, you have to declare to the \acro{DVI} driver that you are using
+\PS{} fonts; in the case of \ProgName{dvips}, this means adding
+lines to the \File{psfonts.map} file, so that \ProgName{dvips} will know
+where the proper fonts are, and won't try to find \acro{PK}
+files. If the font isn't built into the printer, you have to acquire
+it (which may mean that you need to purchase the font files).
+
+Second, your previewer must know what to do with the fonts: see
+\Qref[question]{previewing type 1 fonts}{Q-PSpreview}.
+
+Third, the stretch and shrink between words is a function of the
+font metric; it is not specified in \acro{AFM} files, so different converters
+choose different values. The \PS{} metrics that come with \acro{PSNFSS}
+used to produce quite tight setting, but they were revised in mid 1995
+to produce a compromise between American and European practice.
+Sophisticated users may not find even the new the values to their taste, and
+want to override them. Even the casual user may find more
+hyphenation or overfull boxes than Computer Modern produces; but \acro{CM}
+is extremely generous.
+
+\Question[Q-psfchoice]{Choice of Type~1 fonts for typesetting Maths}
+
+If you are interested in text alone, you can in principle use any of
+the huge numbers of text fonts in Adobe Type~1, TrueType or OpenType
+formats. The constraint is, of course, that your previewer and
+printer driver should support such fonts (\TeX{} itself \emph{only}
+cares about metrics, not the actual character programs).
+
+If you also need mathematics, then your choice is more limited, in
+particular by the
+demands that \TeX{} makes of maths fonts (for details, see the papers
+by
+\begin{wideversion}
+% !! line break !!
+ \href{http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf}{B.K.P. Horn in \TUGboat{} 14(3)},
+ or by % ! line break
+ \href{http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf}{Thierry Bouche in \TUGboat{} 19(2)}).
+\end{wideversion}
+\begin{narrowversion}
+ B.K.P. Horn in \TUGboat{} 14(3) or by Thierry Bouche in \TUGboat{}
+ 19(2), available as
+ \URL{http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf} or
+ \URL{http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf}, respectively).
+\end{narrowversion}
+There are several options available, which are
+based on Knuth's original designs. Others complement other
+commercial and free text font designs; one set (MicroPress's `informal math')
+stands alone.
+
+Users should also consider the possibilities of typesetting
+\Qref*{maths using OpenType fonts}{Q-otf-maths}.
+
+``Free'' font families that will support \TeX{} mathematics include:
+\begin{booklist}
+\item[Computer Modern](75 fonts~--- optical scaling) Donald E. Knuth\\
+ The \acro{CM} fonts were originally designed in \MF{}, but are also
+ now available in scalable outline form. There are commercial as
+ well as public domain versions, and there are both Adobe Type~1 and
+ TrueType versions. A set of outline versions of the fonts was
+ developed as a commercial venture by \YandY{} and Blue Sky Research;
+ they have since assigned the copyright to the \acro{AMS}, and the
+ fonts are now freely available from \acro{CTAN}. Their quality is
+ such that they have become the \emph{de facto} standard for Type~1
+ versions of the fonts.
+
+\item[\acro{AMS} fonts](52 fonts, optical scaling) The \acro{AMS}\\
+ This set of fonts offers adjuncts to the \acro{CM} set, including
+ two sets of symbol fonts (\FontName{msam} and \FontName{msbm}) and
+ Euler text fonts.
+ These are not a self-standing family, but merit discussion here (not
+ least because several other families mimic the symbol fonts).
+ Freely-available Type~1 versions of the fonts are available on
+ \acro{CTAN}. The \Package{eulervm} package permits use
+ of the Euler maths alphabet in conjunction with text fonts that do
+ not provide maths alphabets of their own (for instance, Adobe
+ Palatino or Minion).
+
+\item[Mathpazo version 1.003](5 fonts) Diego Puga\\
+ The Pazo Math fonts are a family of type~1 fonts suitable for
+ typesetting maths in combination with the Palatino family of text
+ fonts. Four of the five fonts of the distribution are maths
+ alphabets, in upright and italic shapes, medium and bold weights;
+ the fifth font contains a small selection of ``blackboard bold''
+ characters (chosen for their mathematical significance). Support
+ under \LaTeXe{} is available in
+ \Qref*{\acro{PSNFSS}}{Q-usepsfont}; the fonts are
+ licensed under the \acro{GPL}, with legalese permitting the use of
+ the fonts in published documents.
+
+\item[Fourier/Utopia](15 fonts) Michel Bovani\\
+ \FontName{Fourier} is a family built on Adobe \FontName{Utopia}
+ (which has been released for usage free of charge by Adobe). The
+ fonts provide the basic Computer Modern set of mathematical symbols,
+ and add many of the \acro{AMS} mathematical symbols (though you are
+ expected to use some from the \acro{AMS} fonts themselves). There
+ are also several other mathematical and decorative symbols. The
+ fonts come with a \Package{fourier} package for use with \LaTeX{};
+ text support of \acro{OT}1 encoding is not provided~--- you are
+ expected to use \acro{T}1.
+
+ For a sample, see \url{http://www.tug.dk/FontCatalogue/utopia/}
+
+\item[Fourier/New Century Schoolbook]Michael Zedler\\
+ \FontName{Fouriernc} is a configuration using the Fourier fonts in
+ the context of New Century Schoolbook text fonts.
+
+ For a sample, see \url{http://www.tug.dk/FontCatalogue/newcent/}
+
+\item[KP-fonts]The Johannes Kepler project\\
+ The \FontName{kp-fonts} family provides a comprehensive set of text
+ and maths fonts. The set includes replacement fixed-width and sans
+ fonts (though some reports have suggested that these are less
+ successful, and their use may be suppressed when loading the fonts'
+ \Package{kpfonts} \LaTeX{} support package).
+
+ For an example, see \url{http://www.tug.dk/FontCatalogue/kpserif/}
+
+\item[MathDesign](3 free families, 3 commercial-based
+ families\dots{}so far) Paul Pichaureau\\
+ This set so far offers mathematics fonts to match the free fonts
+ Adobe Utopia, URW Garamond and Bitstream Charter (the text versions
+ of all of which are separately available, on \acro{CTAN}, in Type~1
+ format), and Adobe Garamond Pro, Adobe UtopiaStd and ITC Charter
+ (which are commercial fonts, all available for purchase on the web).
+ There has been a little comment on these fonts, but none
+ from actual users posted to the public forums. Users, particularly
+ those who are willing to discuss their experiences, would obviously
+ be welcome. Browse the \acro{CTAN} directory and see which you
+ want: there is a wealth of documentation and examples.
+
+ For samples of the free variants, see
+ \url{http://www.tug.dk/FontCatalogue/charter/} for URW Charter,
+ \url{http://www.tug.dk/FontCatalogue/garamond/} for URW Garamond and
+ \url{http://www.tug.dk/FontCatalogue/utopia-md/} for Adobe Utopia.
+
+\item[Belleek](3 fonts) Richard Kinch\\
+ Belleek is the upshot of Kinch's thoughts on how \MF{} might be used
+ in the future: they were published simultaneously as \MF{} source,
+ as Type~1 fonts, and as TrueType fonts. The fonts act as ``drop-in''
+ replacements for the basic MathTime set (as an example of ``what might
+ be done'').
+
+ The paper outlining Kinch's thoughts, proceeding from considerations
+ of the `intellectual' superiority of \MF{} to evaluations of why its
+ adoption is so limited and what might be done about the problem, is
+ to be found at \URL{http://truetex.com/belleek.pdf}
+
+\item[MTPro2 Lite]Pubish or Perish (Michael Spivak)\\
+ A (functional) subset of the MathTime Pro 2 font set, that is made
+ available, free, for general use. While it does not offer the full
+ power of the commercial product (see below), it is nevertheless a
+ desirable font set.
+
+\item[Mathptmx]Alan Jeffrey, Walter Schmidt and others.\\
+ This set contains maths italic, symbol, extension, and roman virtual
+ fonts, built from Adobe Times, Symbol, Zapf Chancery, and the
+ Computer Modern fonts. The resulting mixture is not entirely
+ acceptable, but can pass in many circumstances. The real advantage
+ is that the mathptm fonts are (effectively) free, and the resulting
+ \PS{} files can be freely exchanged. Support under \LaTeXe{}
+ is available in \Qref*{\acro{PSNFSS}}{Q-usepsfont}.
+
+ For a sample, see \url{http://www.tug.dk/FontCatalogue/times/}
+
+\item[Computer Modern Bright]Free scalable outline versions of these
+ fonts do exist; they are covered below together with their
+ commercial parallels.
+
+\item[URW Classico](4 fonts) LaTeX support by Bob Tennent\\
+ These are clones of Zapf's Optima available from CTAN (for
+ non-commercial use only). Mathematics support can be provided by
+ using packages \Package{eulervm} or \Package{sansmath}. As a
+ sans-serif font family, Optima is especially suitable for
+ presentations.
+\end{booklist}
+The excellent \emph{font catalogue} keeps an % ! line break
+\href{http://www.tug.dk/FontCatalogue/mathfonts.html}{up-to-date list}
+which describes the fonts by giving names and short examples, only.
+(At the time of writing~--- June 2008~--- the list has several that
+are only scheduled for inclusion here.
+
+Another useful document is Stephen Hartke's ``Free maths font
+survey'', which is available on \acro{CTAN} in both \acro{PDF} and
+\acro{HTML} formats. The survey covers most of the fonts mentioned in
+the font catalogue, but also mentions some (such as \Package{Belleek}
+that the catalogue omits.
+
+Fonts capable of setting \TeX{} mathematics, that are available
+commercially, include:
+\begin{booklist}
+\item[BA Math](13 fonts) MicroPress Inc.\\
+ BA Math is a family of serif fonts, inspired by the elegant
+ and graphically perfect font design of John Baskerville. BA
+ Math comprises the fonts necessary for mathematical typesetting
+ (maths italic, math symbols and extensions) in normal and bold
+ weights. The family also includes all \acro{OT}1 and \acro{T}1
+ encoded text fonts of various shapes, as well as fonts with most
+ useful glyphs of the \acro{TS}1 encoding. Macros for using the
+ fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{} are
+ provided.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (including samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/bamath/bamain.htm}
+ \nothtml{\par\egroup}
+\item[CH Math](15 fonts) MicroPress Inc.\\
+ CH Math is a family of slab serif fonts, designed as a maths
+ companion for Bitstream Charter. (The distribution includes
+ four free Bitstream text fonts, in addition to the 15 hand-hinted
+ MicroPress fonts.)
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (including samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/chmath/chmain.htm}
+ \nothtml{\par\egroup}
+
+\item[Computer Modern Bright](62 fonts~--- optical scaling) Walter
+ Schmidt\\
+ \acro{CM} Bright is a family of sans serif fonts, based on Knuth's
+ \acro{CM} fonts. It comprises the fonts necessary for mathematical
+ typesetting, including \acro{AMS} symbols, as well as text and text
+ symbol fonts of various shapes. The collection comes with its own
+ set of files for use with \LaTeX{}. The \acro{CM} Bright fonts are
+ supplied in Type~1 format by MicroPress, Inc. The
+ \Package{hfbright} bundle offers free Type~1 fonts for text using
+ the \acro{OT}1 encoding~--- the \Package{cm-super} fonts provide the
+ fonts in \acro{T}1 text encoding but don't support \acro{CM} bright
+ mathematics.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details of Micropress' offering (including samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/brmath/brmain.htm}
+ \nothtml{\par\egroup}
+
+\item[Concrete Math](25 fonts~--- optical scaling) Ulrik Vieth\\
+ The Concrete Math font set was derived from the Concrete Roman
+ typefaces designed by Knuth. The set provides a collection of math
+ italics, math symbol, and math extension fonts, and fonts of
+ \acro{AMS} symbols that fit with the Concrete set, so that Concrete
+ may be used as a complete replacement for Computer Modern. Since
+ Concrete is considerably darker than \acro{CM}, the family may
+ particularly attractive for use in low-resolution printing or in
+ applications such as posters or transparencies. Concrete Math
+ fonts, as well as Concrete Roman fonts, are supplied in Type 1
+ format by MicroPress, Inc.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further information (including samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/ccmath/ccmain.htm}
+ \nothtml{\par\egroup}
+
+\item[HV Math](14 fonts) MicroPress Inc.\\
+ HV Math is a family of sans serif fonts, inspired by the
+ Helvetica (\acro{TM}) typeface. HV Math comprises the fonts
+ necessary for mathematical typesetting (maths italic, maths symbols
+ and extensions) in normal and bold weights. The family also
+ includes all \acro{OT}1 and \acro{T}1 encoded text fonts of various
+ shapes, as well as fonts with most useful glyphs of the \acro{TS}1
+ encoding. Macros for using the fonts with \plaintex{}, \LaTeXo{}
+ and current \LaTeX{} are provided. Bitmapped copies of the fonts
+ are available free, on \acro{CTAN}.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (and samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/hvmath/hvmain.htm}
+ \nothtml{\par\egroup}
+
+\item[Informal Math](7 outline fonts) MicroPress Inc.\\
+ Informal Math is a family of fanciful fonts loosely based on the
+ Adobe's Tekton (\acro{TM}) family, fonts which imitate handwritten
+ text. Informal Math comprises the fonts necessary for
+ mathematical typesetting (maths italic, maths symbols and extensions)
+ in normal weight, as well as \acro{OT}1 encoded text fonts in
+ upright and oblique shapes. Macros for using the fonts with
+ \plaintex{}, \LaTeXo{} and current \LaTeX{} are provided.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (including samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/ifmath/ifmain.htm}
+ \nothtml{\par\egroup}
+
+\item[Lucida Bright \emph{with} Lucida New Math](25 fonts) Chuck Bigelow and
+ Kris Holmes\\
+ Lucida is a family of related fonts including seriffed, sans serif,
+ sans serif fixed width, calligraphic, blackletter, fax, Kris Holmes'
+ connected handwriting font, \emph{etc}; they're not as `spindly' as
+ Computer Modern, with a large x-height, and include a larger set of
+ maths symbols, operators, relations and delimiters than \acro{CM}
+ (over 800 instead of 384: among others, it also includes the
+ \acro{AMS} \FontName{msam} and \FontName{msbm} symbol sets). `Lucida
+ Bright Expert'
+ (14 fonts) adds seriffed fixed width, another handwriting font,
+ smallcaps, bold maths, upright `maths italic', \emph{etc}., to the
+ set. Support under \LaTeX{} is available under the auspices of the
+ \acro{PSNFSS}, and pre-built metrics are also provided.
+
+ \nothtml{\bgroup\raggedwithindent}
+ \acro{TUG} has the right to distribute these fonts; the web site
+\begin{narrowversion}
+ \href{http://tug.org/lucida/}{``Lucida and TUG''}
+\end{narrowversion}
+\begin{wideversion}
+ ``\href{http://tug.org/lucida/}{Lucida and TUG}''
+\end{wideversion}
+ has details.
+ \nothtml{\par\egroup}
+
+\item[Adobe Lucida, LucidaSans \emph{and} LucidaMath](12 fonts)\\
+ Lucida and LucidaMath are generally considered to be a bit heavy.
+ The three maths fonts contain only the glyphs in the \acro{CM} maths
+ italic, symbol, and extension fonts. Support for using LucidaMath
+ with \TeX{} is not very good; you will need to do some work
+ reencoding fonts \emph{etc}. (In some sense this set is the
+ ancestor of the LucidaBright plus LucidaNewMath font set, which are
+ not currently available.)
+
+\item[MathTime Pro2]Publish or Perish (Michael Spivak)\\
+ This latest instance of the MathTime family covers all the weights
+ (medium, bold and heavy) and symbols of previous versions of
+ MathTime. In addition it has a much extended range of symbols, and
+ many typographic improvements that make for high-quality documents.
+ The fonts are supported under both \plaintex{} and \LaTeXe{}, and
+ are exclusively available for purchase from
+ \Qref*{Personal \TeX{} Inc}{Q-commercial}.
+ \par{}
+ \nothtml{\bgroup\raggedwithindent}
+ For further details and samples and fliers, see
+ \URL{http://www.pctex.com/mtpro2.html}
+ \nothtml{\par\egroup}
+
+\item[Minion Pro and MnSymbol]Adobe, \LaTeX{} support and packaging by
+ Achim Blumensath \emph{et al}.\\
+ \FontName{Minion Pro} derives from the widely-available commercial
+ OpenType font of the same name by Adobe; scripts are provided to
+ convert relevant parts of it to Adobe Type~1 format. The
+ \Package{MinionPro} package will set up text and maths support using
+ \FontName{Minion Pro}, but a separate (free) font set
+ \FontName{MnSymbol} greatly extends the symbol coverage.
+
+\item[PA Math] PA~Math is a family of serif fonts
+ loosely based on the Palatino (\acro{TM}) typeface. PA~Math
+ comprises the fonts necessary for mathematical typesetting (maths
+ italics, maths, calligraphic and oldstyle symbols, and extensions)
+ in normal and bold weights. The family also includes all \acro{OT}1,
+ \acro{T}1 encoded text fonts of various shapes, as well as fonts
+ with the most useful glyphs of the \acro{TS}1 encoding. Macros for
+ using the fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{}
+ are provided.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (and samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/pamath/pamain.htm}
+ \nothtml{\par\egroup}
+
+\item[TM Math](14 fonts) MicroPress Inc.\\
+ TM Math is a family of serif fonts, inspired by the Times
+ (\acro{TM}) typeface. TM Math comprises the fonts necessary for
+ mathematical typesetting (maths italic, maths symbols and extensions)
+ in normal and bold weights. The family also includes all \acro{OT}1
+ and \acro{T}1 encoded text fonts of various shapes, as well as fonts
+ with most useful glyphs of the \acro{TS}1 encoding. Macros for
+ using the fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{}
+ are provided. Bitmapped copies of the fonts are available free, on
+ \acro{CTAN}.
+
+ \nothtml{\bgroup\raggedwithindent}
+ For further details (and samples) see\\
+ \URL{http://www.micropress-inc.com/fonts/tmmath/tmmain.htm}
+ \nothtml{\par\egroup}
+\end{booklist}
+Two other font sets should be mentioned, even though they don't
+currently produce satisfactory output~--- their author is no longer
+working on them, and several problems have been identified:
+\begin{booklist}
+\item[Pxfonts set version 1.0](26 fonts) by Young Ryu\\
+ The \FontName{pxfonts} set consists of
+ \begin{itemize}
+ \item virtual text fonts using \FontName{Adobe} \FontName{Palatino}
+ (or its \acro{URW} replacement, \FontName{Palladio})
+ with modified plus, equal and slash symbols;
+ \item maths alphabets using \FontName{Palatino} (or \FontName{Palladio};
+ \item maths fonts of all symbols in the computer modern maths fonts
+ (\FontName{cmsy}, \FontName{cmmi}, \FontName{cmex} and the Greek
+ letters of \FontName{cmr})
+ \item maths fonts of all symbols corresponding to the \acro{AMS}
+ fonts (\FontName{msam} and \FontName{msbm});
+ \item additional maths fonts of various symbols.
+ \end{itemize}
+ The text fonts are available in \acro{OT}1, \acro{T}1 and \acro{LY}1
+ encodings, and \acro{TS} encoded symbols are also available. The
+ sans serif and monospaced fonts supplied with the \FontName{txfonts}
+ set (see below) may be used with \FontName{pxfonts}; the
+ \FontName{txfonts} set should be installed whenever \FontName{pxfonts}
+ are. \LaTeX{}, \ProgName{dvips} and \PDFTeX{} support files are
+ included.
+
+ The fonts are not perfect; the widths assigned to the characters in
+ the \extension{tfm} file are wrong for some glyphs; this can cause
+ sequences of characters to ``look wrong'', or in some cases even to
+ overlap; the \FontName{newpx} fonts (noted above) aim to reduce
+ these problems.
+
+ The fonts are licensed under the \acro{GPL}; use in published
+ documents is permitted.
+
+\item[Newpx]by Michael Sharpe from Young Ryu's \ProgName{pxfonts}\\
+ This collection is derived from \ProgName{pxfonts}; the maths fonts
+ metrics have been adjusted so that the output is less cramped than
+ when \ProgName{pxfonts} is used; the appearance of the output is
+ much improved. Two packages are provided, \Package{newpxtext} for
+ using the associated text fonts, and \Package{newpxmath} for
+ mathematics.
+
+\item[Txfonts set version 3.1](42 fonts) by Young Ryu\\
+ The \FontName{txfonts} set consists of
+ \begin{itemize}
+ \item virtual text fonts using \FontName{Adobe} \FontName{Times} (or
+ the \acro{URW} \FontName{Nimbus Roman No9 L} font that
+ substitutes for Times, which is distributed as part of the
+ \acro{URW} ``basic 35'' collection) with
+ modified plus, equal and slash symbols;
+ \item matching sets of sans serif and monospace (`typewriter')
+ fonts (the sans serif set is based on \FontName{Adobe} \FontName{Helvetica});
+ \item maths alphabets using Adobe \FontName{Times}, or the URW
+ equivalent \FontName{NimbusRomanNo9};
+ \item maths fonts of all symbols in the computer modern maths fonts
+ (\FontName{cmsy}, \FontName{cmmi}, \FontName{cmex} and the Greek
+ letters of \FontName{cmr})
+ \item maths fonts of all symbols corresponding to the \acro{AMS}
+ fonts (\FontName{msam} and \FontName{msbm});
+ \item additional maths fonts of various symbols.
+ \end{itemize}
+ The text fonts are available in \acro{OT}1, \acro{T}1 and \acro{LY}1
+ encodings, and \acro{TS} encoded symbols are also available.
+
+ The fonts are not perfect; the widths assigned to the characters in
+ the \extension{tfm} file are wrong for some glyphs; this can cause
+ sequences of characters to ``look wrong'', or in some cases even to
+ overlap; the \FontName{newtx} fonts (noted above) aim to reduce
+ these problems.
+
+ The fonts are licensed under the \acro{GPL}; use in published
+ documents is permitted.
+\item[Txfontsb set version 1.00] by Young Ryu and Antonis Tsolomitis\\
+ The \ProgName{txfontsb} bundles \ProgName{txfonts}, extended to
+ provide a Small Caps set, Old-Style numbers and Greek text (from the
+ GNU Freefont set).
+\begin{flatversion}
+ Documentation
+ (\URL{http://mirrors.ctan.org/fonts/txfontsb/doc/txfontsb.pdf})
+\end{flatversion}
+\begin{hyperversion}
+ \href{http://mirrors.ctan.org/fonts/txfontsb/doc/txfontsb.pdf}{Documentation}
+\end{hyperversion}
+ is available for this variant, too.
+
+\item[Newtx]by Michael Sharpe from Young Ryu's \ProgName{txfonts}\\
+ This collection is derived from \ProgName{txfonts}; the maths fonts
+ metrics have been adjusted so that the output is less cramped than
+ when \ProgName{txfonts} is used; the appearance of the output is
+ much improved. Two packages are provided, \Package{newtxtext} for
+ using the associated text fonts, and \Package{newtxmath} for
+ mathematics. Options are provided to substitute
+ letters and symbols from the \FontName{Libertine} set, and from the
+ Garamond extension font \FontName{garamondx} (but note that
+ \FontName{garamondx}, which is an adaptation of \acro{URW} Garamond,
+ is not available via \texlive{}).
+\end{booklist}
+Finally, one must not forget:
+\begin{booklist}
+\item[Proprietary fonts]Various sources.\\
+ Since having a high quality font set in scalable outline form that
+ works with \TeX{} can give a publisher a real competitive advantage,
+ there are some publishers that have paid (a lot) to have such font
+ sets made for them. Unfortunately, these sets are not available on
+ the open market, despite the likelihood that they're more complete
+ than those that are.
+\end{booklist}
+We observe a very limited selection of commercial maths font sets; a
+Type~1 maths font has to be explicitly designed for use with \TeX{},
+which is an expensive business, and is of little appeal in other
+markets. Furthermore, the \TeX{} market for commercial fonts is
+minute by comparison with the huge sales of other font sets.
+
+Text fonts in Type~1 format are available from many vendors including
+Adobe, Monotype and Bitstream. However, be careful with cheap font
+``collections''; many of them dodge copyright restrictions by removing
+(or crippling) parts of the font programs such as hinting. Such
+behaviour is both unethical and bad for the consumer.
+The fonts may not render well (or at all, under \acro{ATM}), may not have the
+`standard' complement of 228 glyphs, or may not include metric files
+(which you need to make \acro{TFM} files).
+
+\ttype{} was for a long time the ``native'' format for Windows, but
+MicroSoft joined the development of the \otype{} specification, and
+`modern' windows will work happily with fonts in either format. Some \TeX{}
+implementations such as \Qref*{True\TeX{}}{Q-commercial} use TrueType
+versions of Computer Modern and Times Maths fonts to render \TeX{}
+documents in Windows without the need for additional system software like
+\acro{ATM}. (When used on a system running Windows~XP or later,
+True\TeX{} can also use Adobe Type~1 fonts.)
+
+When choosing fonts, your own system environment may not be the only one of
+interest. If you will be sending your finished documents to others for
+further use, you should consider whether a given font format will introduce
+compatibility problems. Publishers may require TrueType exclusively because
+their systems are Windows-based, or Type~1 exclusively, because their systems
+are based on the early popularity of that format in the publishing industry.
+Many service bureaus don't care as long as you present them with a finished
+print file (\PS{} or \acro{PDF}) for their output device.
+\begin{ctanrefs}
+\item[\nothtml{\normalfont}CM family collection]%
+ Distributed as part of \CTANref{amsfonts}
+\item[\nothtml{\normalfont}AMS font collection]%
+ Distributed as part of \CTANref{amsfonts}
+\item[Belleek \nothtml{\normalfont}fonts]%
+ \CTANref{belleek}
+\item[\nothtml{\normalfont} URW Classico fonts]\CTANref{classico}
+\item[CM-super \nothtml{\normalfont}collection]\CTANref{cm-super}
+\item[eulervm.sty \nothtml{\normalfont}and supporting metrics]%
+ \CTANref{eulervm}
+\item[fourier \nothtml{\normalfont}(including metrics and other support for \nothtml{\itshape}utopia]%
+ \CTANref{fourier}
+\item[fouriernc]\CTANref{fouriernc}
+\item[garamondx]\CTANref{garamondx}
+\item[hfbright \nothtml{\normalfont}collection]\CTANref{hfbright}
+\item[hvmath \nothtml{\normalfont\itshape}(free bitmapped version)]%
+ \CTANref{hvmath}
+\item[kpfonts \nothtml{\normalfont}family]\CTANref{kpfonts}
+\item[Libertine \nothtml{\normalfont}family]\CTANref{libertine}
+\item[Lucida Bright/Math metrics]\CTANref{lucida}
+\item[Lucida PSNFSS support]\CTANref{lucida-psnfss}
+\item[MathDesign \nothtml{\normalfont}collection]\CTANref{mathdesign}
+\item[\nothtml{\normalfont}Maths Font Survey]\CTANref{mathsurvey.pdf}
+ (\acro{PDF}) or \CTANref{mathsurvey.html} (\acro{HTML})
+\item[\nothtml{\normalfont}MathTime Pro 2 Lite]\CTANref{mtp2lite}
+\item[\nothtml{\normalfont}Minion Pro support]\CTANref{minionpro}
+\item[MnSymbol \nothtml{\normalfont}family]\CTANref{mnsymbol}
+\item[Newtx \nothtml{\normalfont}fonts]\CTANref{newtx}
+\item[NimbusRomanNo9 fonts]distributed in \CTANref{urw-base35}
+\item[Palladio fonts]distributed in \CTANref{urw-base35}
+\item[pxfonts]\CTANref{pxfonts}
+\item[sansmath.sty]\CTANref{sansmath}
+\item[tmmath \nothtml{\normalfont\itshape}(free bitmapped version)]%
+ \CTANref{tmmath}
+\item[txfonts]\CTANref{txfonts}
+\item[\nothtml{\normalfont}URW ``35 fonts'' collection]\CTANref{urw-base35}
+\item[utopia \nothtml{\normalfont}fonts]\CTANref{utopia}
+\end{ctanrefs}
+\LastEdit{2014-01-22}
+
+\Question[Q-otf-maths]{Unicode Maths using OpenType fonts}
+
+The \acro{ISO} standard Universal Coding Scheme (UCS), which is
+commonly known as Unicode, was adopted early by the designers of
+TrueType (\acro{TTF}) and OpenType (\acro{OTF}) fonts. The
+flexibility of the fonts offers hope, for the first time, of a uniform
+method for typesetting essentially any language.
+
+\tex{} users have been eagerly adopting the fonts, for some time,
+using \xetex{} (now a rather stable system) and \luatex{} (which is,
+at the time of writing, still being developed).
+
+While \tex{} users were investigating the use of these text fonts,
+\acro{ISO} was extending Unicode to provide a means of expressing
+mathematics. As this work proceeded, MicroSoft and (separately) a
+consortium of publishing companies were developing OpenType maths
+fonts. (Microsoft contributed on the development of the concepts,
+within the \acro{ISO} process.) MicroSoft's OpenType Maths font,
+\FontName{Cambria Math} has been available for purchase for some time.
+
+The first free OpenType Maths font to appear was % !line break
+\FontName{Asana Math}, which was eventually followed by
+the publishers' consortium's offer of an interim version
+of their font, \FontName{STIX}, which has been
+redeveloped to provide a more usable whole, \FontName{XITS}, by a group
+of \tex{} users.
+
+Other fonts are appearing, including % ! line break
+\FontName{TeX Gyre Termes Math} (based on Times-like fonts) and
+\FontName{Tex Gyre Pagella Math} (based on Palatino-like fonts),
+and \FontName{LM Math} extending the OpenType version of the
+\FontName{Latin Modern} font family.
+
+Actually using a unicode maths font is quite a complicated business,
+but the \latex{} package \Package{unicode-math} (supported
+by the \Package{fontspec} package) does the essential groundwork.
+\begin{ctanrefs}
+\item[Asana-Math \nothtml{\rmfamily}font]\CTANref{asana-math}[asana-math]
+\item[fontspec.sty]\CTANref{fontspec}
+\item[lm-math \nothtml{\rmfamily}fonts]\CTANref{lm-math}
+\item[STIX \nothtml{\rmfamily}fonts]\CTANref{stix}
+\item[unicode-math.sty]\CTANref{unicode-math}
+\item[tex-gyre-math-pagella \nothtml{\rmfamily}font]distributed as
+ part of \CTANref{tex-gyre-math}[tex-gyre-math-pagella]
+\item[tex-gyre-math-termes \nothtml{\rmfamily}font]distributed as part
+ of \CTANref{tex-gyre-math}[tex-gyre-math-termes]
+\item[XITS \nothtml{\rmfamily}fonts]\CTANref{xits}
+\end{ctanrefs}
+\LastEdit*{2014-01-22}
+% more to come...
+
+\Question[Q-charshift]{Weird characters in \ProgName{dvips} output}
+\keywords{fi ligature pound pounds sterling elephants}
+
+You've innocently generated output, using \ProgName{dvips}, and there
+are weird transpositions in it: for example, the \texttt{fi} ligature has
+appeared as a \textsterling{} symbol.
+This is an unwanted side-effect of the precautions
+outlined in \Qref*{generating \PS{} for PDF}{Q-dvips-pdf}.
+The \texttt{-G1} switch discussed in that question is appropriate for
+Knuth's text fonts, but doesn't work with text fonts that don't follow
+Knuth's patterns (such as fonts supplied by Adobe).
+
+If the problem arises, suppress the \texttt{-G1} switch: if you were using it
+explicitly, \emph{don't}; if you were using \texttt{-Ppdf}, add \texttt{-G0} to
+suppress the implicit switch in the pseudo-printer file.
+
+The problem has been corrected in \ProgName{dvips} v~5.90 (and later
+versions); it is unlikely ever to recur\dots{}
+\LastEdit{2012-10-24}
+
+\subsection{Macros for using fonts}
+
+\Question[Q-fonts-pln]{Using non-standard fonts in \plaintex{}}
+
+\plaintex{} (in accordance with its description) doesn't do anything
+fancy with fonts: it sets up the fonts that Knuth found he needed when
+writing the package, and leaves you to do the rest.
+
+To use something other than Knuth's default, you can use Knuth's
+mechanism, the \csx{font} primitive:
+\begin{quote}
+\begin{verbatim}
+\font\foo=nonstdfont
+...
+\foo
+Text set using nonstdfont ...
+\end{verbatim}
+\end{quote}
+The name you use (\texttt{nonstdfont}, above) is the name of the
+\extension{tfm} file for the font you want.
+
+If you want to use an italic version of \csx{foo}, you need to use
+\csx{font} again:
+\begin{quote}
+\begin{verbatim}
+\font\fooi=nonstdfont-italic
+...
+\fooi
+Text set using nonstdfont italic...
+\end{verbatim}
+\end{quote}
+This is all very elementary stuff, and serves for simple use of fonts.
+However, there are wrinkles, the most important of which is the matter
+of \Qref*{font encodings}{Q-whatenc}. One almost never sees new fonts
+that use Knuth's eccentric font encodings~--- but those encodings are
+built into \plaintex{}, so that some macros of \plaintex{} need to be
+changed to use the fonts. \LaTeX{} gets around all these problems by
+using a ``font selection scheme''~--- this `\acro{NFSS}' (`\acro{N}'
+for `new', as opposed to what \LaTeXo{} had) carries around with it
+separate information about the fonts you use, so the changes to
+encoding-specific commands happen automagically.
+
+If you only want to use the \Qref*{\acro{EC} fonts}{Q-ECfonts}, you
+can in principle use the \Package{ec-plain} bundle, which gives you a version
+of \plaintex{} which you can run in the same way that you run
+\plaintex{} using the original \acro{CM} fonts, by invoking
+\ProgName{tex}. (\Package{Ec-plain} also extends the \acro{EC} fonts,
+for reasons which aren't immediately clear, but which might cause
+problems if you're hoping to use Type 1 versions of the fonts.)
+
+The \Package{font_selection} package provides a sort of halfway house:
+it provides font face and size, but not family selection. This gives
+you considerable freedom, but leaves you stuck with the original
+\acro{CM} fonts. It's a compact solution, within its restrictions.
+
+Other \plaintex{} approaches to the problem (packages
+\Package{plnfss}, \Package{fontch} and \Package{ofs}) break out of the
+\plaintex{} model, towards the sort of font selection provided by
+\CONTeXT{} and \LaTeX{}~--- font selection that allows you to change
+family, as well as size and face. The remaining packages all make
+provision for using encodings other than Knuth's \acro{OT}1.
+
+\Package{Plnfss} has a rather basic set of font family details;
+however, it is capable of using font description (\extension{fd}) files
+created for \LaTeX{}. (This is useful, since most modern mechanisms
+for integrating outline fonts with \TeX{} generate \extension{fd} files
+in their process.)
+
+\Package{Fontch} has special provision for \acro{T}1 and \acro{TS}1
+encodings, which you select by arcane commands, such as:
+\begin{quote}
+\begin{verbatim}
+\let\LMTone\relax
+\input fontch.tex
+\end{verbatim}
+\end{quote}
+for \acro{T}1.
+
+\Package{Ofs} seems to be the most thoroughly thought-through of the
+alternatives, and can select more than one encoding: as well as
+\acro{T}1 it covers the encoding \acro{IL}2, which is favoured in the
+Czech Republic and Slovakia. \Package{Ofs} also covers mathematical fonts,
+allowing you the dubious pleasure of using fonts such as the % ! line break
+\Qref*{\FontName{pxfonts} and \FontName{txfonts}}{Q-psfchoice}.
+
+The \Package{pdcmac} \plaintex{} macro package aims to be a complete
+document preparation environment, like \Qref*{\Eplain{}}{Q-eplain}. One
+of its components is a font selection scheme, \Package{pdcfsel}, which
+is rather simple but adequately powerful for many uses. The package
+doesn't preload fonts: the user is required to declare the fonts the
+document is going to use, and the package provides commands to select
+fonts as they're needed. The distribution includes a configuration to
+use Adobe `standard' fonts for typesetting text. (\Eplain{} itself
+seems not to offer a font selection scheme.)
+
+The \Package{font-change} collection takes a rather different
+approach~--- it supplies what are (in effect) a series of templates
+that may be included in a document to change font usage. The
+package's documentation shows the effect rather well.
+
+Simply to change font \emph{size} in a document (i.e., not changing
+the default font itself), may be done using the rather straightforward
+\Package{varisize}, which offers font sizes ranging from 7~points to
+20~points (nominal sizes, all). Font size commands are generated when
+any of the package files is loaded, so the \File{11pt.tex} defines a
+command \csx{elevenpoint}; each of the files ensures there's a ``way
+back'', by defining a \csx{tenpoint} command.
+\begin{ctanrefs}
+\item[ec-plain]\CTANref{ec-plain}
+\item[font-change]\CTANref{font-change}
+\item[fontch]\CTANref{fontch}
+\item[font_selection]\CTANref{font_selection}
+\item[ofs]\CTANref{ofs}
+\item[pdcmac]\CTANref{pdcmac}
+\item[plnfss]\CTANref{plnfss}
+\item[varisize]\CTANref{varisize}
+\end{ctanrefs}
+
+\subsection{Particular font families}
+
+\Question[Q-concrete]{Using the ``Concrete'' fonts}
+
+The Concrete Roman fonts were designed by Don Knuth for a book called
+``Concrete Mathematics'', which he wrote with Graham and Patashnik
+(\emph{the} Patashnik, of \BibTeX{} fame). Knuth
+only designed text fonts, since the book used the Euler fonts for
+mathematics. The book was typeset using \plaintex{}, of course, with
+additional macros that may be viewed in a file \File{gkpmac.tex},
+which is available on \acro{CTAN}.
+
+The packages \Package{beton}, \Package{concmath}, and
+\Package{ccfonts} are \LaTeX{} packages that change the default text
+fonts from Computer Modern to Concrete. Packages \Package{beton} and
+\Package{ccfonts} also slightly increase the default value of
+\csx{baselineskip} to account for the rather heavier weight of the
+Concrete fonts. If you wish to use the \FontName{Euler} fonts for
+mathematics, as Knuth did, there's the \Package{euler} package which
+has been developed from Knuth's own \plaintex{}-based set: these
+macros are currently deprecated (they clash with many things, including
+\AMSLaTeX{}). The independently-developed \Package{eulervm}
+bundle is therefore preferred to the \Package{euler} package. (Note
+that installing the \Package{eulervm} bundle involves installing a
+series of virtual fonts. While most modern distributions seem to have
+the requisite files installed by default, you may find you have to
+install them. If so, see the file \File{readme} in the
+\Package{eulervm} distribution.)
+
+A few years after Knuth's original design, Ulrik Vieth
+designed the Concrete Math fonts. Packages
+\Package{concmath}, and \Package{ccfonts} also change the default math
+fonts from Computer Modern to Concrete and use the Concrete versions
+of the \acro{AMS} fonts (this last behaviour is optional in the case
+of the \Package{concmath} package).
+
+There are no bold Concrete fonts, but it is generally accepted that
+the Computer Modern Sans Serif demibold condensed fonts are an
+adequate substitute. If you are using \Package{concmath} or
+\Package{ccfonts} and you want to follow this suggestion, then use the
+package with \pkgoption{boldsans} class option (in spite of the fact
+that the \Package{concmath} documentation calls it
+\pkgoption{sansbold} class option). If you are using \Package{beton},
+add
+\begin{quote}
+ \cmdinvoke{renewcommand}{\csx{bfdefault}}{sbc}
+\end{quote}
+to the preamble of your document.
+
+Type~1 versions of the fonts are available. For \acro{OT}1 encoding,
+they are available from \Qref*{MicroPress}{Q-psfchoice}. The
+\Qref*{CM-Super fonts}{Q-textrace} contain Type~1 versions
+of the Concrete fonts in \acro{T}1 encoding.
+\begin{ctanrefs}
+\item[beton.sty]\CTANref{beton}
+\item[ccfonts.sty]\CTANref{ccfonts}
+\item[\nothtml{\rmfamily}CM-Super fonts]\CTANref{cm-super}
+\item[concmath.sty]\CTANref{concmath}
+\item[\nothtml{\rmfamily}Concmath fonts]\CTANref{concmath-f}
+\item[\nothtml{\rmfamily}Concrete fonts]\CTANref{concrete}
+\item[euler.sty]\CTANref{euler-latex}
+\item[eulervm \nothtml{\rmfamily}bundle]\CTANref{eulervm}
+\item[gkpmac.tex]\CTANref{gkpmac}
+\end{ctanrefs}
+
+\Question[Q-uselmfonts]{Using the Latin Modern fonts}
+
+The \Package{lm} fonts are an exciting addition to
+the armoury of the \AllTeX{} user: high quality outlines of fonts that
+were until recently difficult to obtain, all in a free and
+relatively compact package. However, the spartan information file
+that comes with the fonts remarks ``It is presumed that a potential
+user knows what to do with all these files''. This answer aims to
+fill in the requirements: the job is really not terribly difficult.
+
+Note that te\TeX{} distributions, from version~3.0, already have the
+\Package{lm} fonts: all you need do is use them. The fonts may also
+be installed via the package manager, in a current \miktex{} system.
+The remainder of this answer, then, is for people who don't use such
+systems.
+
+The font (and related) files appear on \acro{CTAN} as a set of
+single-entry \Qref*{\acro{TDS} trees}{Q-tds}~---
+\File{fonts}, \File{dvips}, \File{tex} and \File{doc}. The \File{doc}
+subtree really need not be copied (it's really a pair of sample
+files), but copy the other three into your existing Local
+\texttt{\$TEXMF} tree, and
+% beware line break
+\Qref*{update the filename database}{Q-inst-wlcf}.
+
+Now, incorporate the fonts in the set searched by \PDFLaTeX{},
+\ProgName{dvips}, \ProgName{dvipdfm}/\ProgName{dvipdfmx}, your
+previewers and Type~1-to-\acro{PK} conversion programs, by
+\begin{itemize}
+\item On a te\TeX{} system earlier than version~2.0, edit the file
+ \File{$TEXMF/dvips/config/updmap} %$
+ and insert an absolute path for the \File{lm.map} just after the
+ line that starts \texttt{extra\_modules="} (and before the closing
+ quotes).
+\item On a te\TeX{} version~2.0 (or later), execute the command
+\begin{quote}
+\begin{verbatim}
+updmap --enable Map lm.map
+\end{verbatim}
+\end{quote}
+\item On a \miktex{} system earlier than version~2.2, the ``Refresh
+ filename database'' operation, which you performed after installing
+ files, also updates the system's ``\PS{} resources database''.
+\item On a \miktex{} system, version~2.2 or later, update
+ \File{updmap.cfg} as described in the \miktex{} % beware line break
+ \href{http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg}{online documentation}.
+ Then execute the command \texttt{initexmf -\relax-mkmaps}, and the
+ job is done.
+\end{itemize}
+
+To use the fonts in a \LaTeX{} document, you should
+\begin{quote}
+ \cmdinvoke{usepackage}{lmodern}
+\end{quote}
+this will make the fonts the default
+for all three \LaTeX{} font families (``roman'', ``sans-serif'' and
+``typewriter''). You also need
+\begin{quote}
+ \cmdinvoke{usepackage}[T1]{fontenc}
+\end{quote}
+for text, and
+\begin{quote}
+ \cmdinvoke{usepackage}{textcomp}
+\end{quote}
+if you want to use any of the \acro{TS}1-encoding symbols. There is
+no support for using fonts according to the \acro{OT}1 encoding.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm}
+\end{ctanrefs}
+
+\Question[Q-getnff]{Getting `free' fonts not in your distribution}
+
+Some fonts are free to use, but may not be sold. This creates a
+dilemma for distributions: users may want the fonts, but since the
+distribution is also available on a \acro{DVD} for sale, the fonts may
+not be in the distribtution.
+
+The \acro{CTAN} archives hold such fonts, together with all the
+necessary support files, but even with the support files ready-made,
+installing a font is a tedious business.
+
+For \texlive{} users, this dilemma is solved by the
+\ProgName{getnonfreefonts} script. Download the script installer from
+\url{http://tug.org/fonts/getnonfreefonts/}; the web page tells you
+how to run the installer to get the script, and what fonts are
+currently available
+
+Once the script is installed, you can ask it what it has available by
+saying:
+\begin{quote}
+\begin{verbatim}
+getnonfreefonts -l
+\end{verbatim}
+\end{quote}
+and you can ask it to install a font (in your local texmf tree) by:
+\begin{quote}
+\begin{verbatim}
+getnonfreefonts luximono
+\end{verbatim}
+\end{quote}
+(for example; the printed version of the \acro{FAQ} uses luximono, so
+that the example was to hand\dots{}).
+
+(System adminstrators may use \ProgName{getnonfreefonts-sys}, which
+will install the font in the `public' \texttt{texmf} tree, so that all
+users of the system may use the new font.)
+
+The script will download the relevant font files from \acro{CTAN},
+extract them from their \extension{zip} file, install them and update
+the font maps. It even goes so far as to apologise for how long it's
+taking!
+\LastEdit*{2013-10-22}
+
+\subsection{\MF{} fonts}
+
+\Question[Q-useMF]{Getting \MF{} to do what you want}
+
+\MF{} allows you to create your own fonts, and most \TeX{} users
+will never need to use it~--- modern \AllTeX{} systems contain
+rather few \MF{} fonts of any significance, and when \MF{} output is
+needed the font generation is done, automatically, ``on the fly''.
+
+If you find you have some special requirement that the system doesn't
+satisfy, you need to know about \MF{} in rather more detail. \MF{},
+unlike \TeX{}, requires customisation for each output device: such
+customisation is conventionally held in a ``mode'' associated with the
+device. Modes are commonly defined using the \texttt{mode\_def}
+convention described on page~94 of \emph{The \MF{}book} % ! line break
+(see \Qref[question]{\TeX{}-related books}{Q-other-books}). Your
+distribution should provide
+a file, conventionally called \File{local.mf}, containing all the
+\texttt{mode\_def}s you will be using. In the unlikely event that
+\File{local.mf} doesn't already exist, Karl Berry's collection of
+modes (\File{modes.mf}) is a good starting point
+(it can be used as a `\File{local.mf}' without modification in a
+modern implementation of \MF{}).
+Settings for new output devices are added to \File{modes.mf} as they
+become available.
+
+Now create
+a \texttt{plain} base file using \ProgName{mf} (in ``initialisation''
+mode), \texttt{plain.mf}, and \texttt{local.mf}:
+\begin{quote}
+\begin{verbatim}
+% mf -ini
+This is METAFONT...
+**plain # you type plain
+(output)
+*input local # you type this
+(output)
+*dump # you type this
+Beginning to dump on file plain...
+(output)
+\end{verbatim}
+\end{quote}
+This will create a base file named \File{plain.base} (or something
+similar; for example, it will be \File{PLAIN.BAS} on \MSDOS{}
+systems). Move the file to the directory containing the base files on
+your system, and run \ProgName{texhash} as necessary.
+
+Now you need to make sure \MF{} loads this new base when it starts up. If
+\MF{} loads the \texttt{plain} base by default on your system, then you're
+ready to go. Under Unix (using the default \texlive{} (and earlier)
+distributions this does indeed happen, but we could for instance
+define a command \ProgName{plainmf}%
+\begin{footnoteenv}
+ On the grounds that a command \ProgName{plain} could be misconstrued
+ as a reference to \plaintex{}
+\end{footnoteenv}
+which executes `\texttt{mf -base=plain}' (or, in more traditional
+style `\texttt{mf \&plain}') which loads the \texttt{plain} base
+file.
+
+The usual way to create a font with \MF{} (with an appropriate base
+file loaded) is to start \MF{}'s input with the
+\begin{narrowversion}
+ lines
+ \begin{quote}
+ \csx{mode}\texttt{=<mode name>;}\\
+ \texttt{mag=<magnification>;}\\
+ \texttt{input <font file name>}
+ \end{quote}
+\end{narrowversion}
+\begin{wideversion}
+line
+\begin{quote}
+\begin{verbatim}
+\mode=<mode name>; mag=<magnification>; input <font file name>
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+in response to the `\texttt{**}' prompt or on the \MF{} command line. (If
+\texttt{<mode name>} is unknown or omitted, the mode defaults to
+`proof' mode and \MF{} will produce an output file called % ! line break
+\File{<font file name>.2602gf})
+The \texttt{<magnification>} is a floating point number or a
+`magstep' (magsteps define sizes by stating how many times you need to
+multiply a base size by \texttt{1.2}, so for a base size of
+\texttt{10}, \texttt{magstep 1} is \texttt{12}, \texttt{magstep 2} is
+\texttt{14.4}
+If \texttt{mag=<magnification>} is omitted, then the default
+is \texttt{1}~(\texttt{magstep 0}). For example, to generate
+\FontName{cmr10} at \texttt{12pt} for an Epson,
+printer you might type
+\begin{quote}
+\begin{verbatim}
+mf \mode=epson; mag=magstep 1; input cmr10
+\end{verbatim}
+\end{quote}
+Note that under Unix the \texttt{\textbackslash } and \texttt{;}
+characters must usually be quoted or escaped, so this would typically
+look something like
+\begin{quote}
+\begin{verbatim}
+ mf '\mode=epson; mag=magstep 1; input cmr10'
+\end{verbatim}
+\end{quote}
+If you need a special mode that isn't in the base, you can put its
+commands in a file (\emph{e.g.}, \File{ln03.mf}) and invoke it on the
+fly with the \csx{smode} command. For example, to create
+\File{cmr10.300gf} for an \acro{LN}03 printer, using the file
+\begin{quote}
+\begin{verbatim}
+% This is ln03.mf as of 1990/02/27
+% mode_def courtesy of John Sauter
+proofing:=0;
+fontmaking:=1;
+tracingtitles:=0;
+pixels_per_inch:=300;
+blacker:=0.65;
+fillin:=-0.1;
+o_correction:=.5;
+\end{verbatim}
+\end{quote}
+(note the absence of the \texttt{mode\_def} and \texttt{enddef}
+commands), you would type
+\begin{quote}
+\begin{verbatim}
+mf \smode="ln03"; input cmr10
+\end{verbatim}
+\end{quote}
+This technique isn't one you should regularly use, but it may
+prove useful if you acquire a new printer and want to experiment with
+parameters, or for some other reason are regularly editing the
+parameters you're using. Once you've settled on an appropriate set of
+parameters, you should use them to rebuild the base file that you use.
+
+Other sources of help are discussed in our list of % ! line break
+\Qref*{\MF{} and \MP{} Tutorials}{Q-mfptutorials}.
+\begin{ctanrefs}
+\item[modes.mf]\CTANref{modes-file}
+\end{ctanrefs}
+\LastEdit{2011-09-04}
+
+\Question[Q-keepfonts]{Which font files should be kept}
+
+\MF{} produces from its run three files, a metrics (\acro{TFM}) file, a
+generic font (\acro{GF}) file, and a log file; all of these files have the
+same base name as does the input (\emph{e.g.}, if the input file was
+\File{cmr10.mf}, the outputs will be \File{cmr10.tfm},
+\File{cmr10.nnngf} (the file name may be mangled if you are using an
+operating system which doesn't permit long file names)
+and \File{cmr10.log}).
+
+For \TeX{} to use the font, you need a \acro{TFM} file, so you need
+to keep that. However, you are likely to generate the same font
+at more than one magnification, and each time you do so you'll
+(incidentally) generate another \acro{TFM} file; these files are
+all the same, so you only need to keep one of them.
+
+To preview or to produce printed output, the \acro{DVI} processor will need a
+font raster file; this is what the \acro{GF} file provides. However, while
+there used (once upon a time) to be \acro{DVI} processors that could use
+\acro{GF} files, modern processors use
+packed raster (\acro{PK}) files (incidentally, \pdftex{} also uses
+\acro{PK} files if nothing ``better'' is available, but
+see \Qref[]{fuzzy fonts in \acro{PDF}}{Q-fuzzy-type3}).
+Therefore, you need to generate a \acro{PK} file from the \acro{GF} file; the
+program \ProgName{gftopk} does this for you, and once you've done that you
+may throw the \acro{GF} file away.
+
+The log file should never be needed again, unless there was some sort
+of problem in the \MF{} run, and need not therefore be kept.
+\LastEdit{2011-09-04}
+
+\Question[Q-getbitmap]{Acquiring bitmap fonts}
+
+When \acro{CTAN} was young, most people would start using \TeX{}
+with a 300 dots-per-inch (dpi) laser printer, and sets of Computer
+Modern bitmap fonts for this resolution are available on \acro{CTAN}.
+(There are separate sets for write-black and write-white printers, as
+well as sets at 120~dpi and 240~dpi.)
+
+There used to regular requests that \acro{CTAN} should hold
+a wider range of resolutions, but they were resisted for two reasons:
+\begin{itemize}
+\item The need to decide which printers to generate fonts for. The
+ broad-brush approach taken for 300~dpi printers was (more or less)
+ justified back then, given the dominance of certain printer
+ `engines', but nowadays one could not make any such assumption.
+\item Given the above, it has been near-impossible to justify the
+ space that would be required by a huge array of bitmap fonts.
+\end{itemize}
+Fortunately, \AllTeX{} distribution technology has put a stop to these
+arguments: most (if not all) current distributions generate bitmap
+fonts as needed, and cache them for later re-use. The impatient
+user, who is determined that all bitmap fonts should be created once
+and for all, may be supported by scripts such as \ProgName{allcm}
+(distributed with \texlive{}, at least; otherwise such a
+person should consult ``\Qref*{the use of \MF{}}{Q-useMF})''.
+
+If your output is to a \PS{}-capable device, or if your output is
+destined to be converted to \acro{PDF}, you should switch to
+using Type~1 versions of the \acro{CM} fonts. Two free
+sets are available; the older (\Package{bakoma}) is
+somewhat less well produced than the \Package{bluesky} fonts, which were
+originally professionally produced and sold, but were then released
+for general public use by their originators \YandY{} and Bluesky Research,
+in association with the \acro{AMS} and other scientific publishers
+(they are nowadays available under the SIL's Open Fonts Licence). The
+two sets contain slightly different ranges of fonts, but you are
+advised to use the \Package{bluesky} set except when \Package{bakoma}
+is for some reason absolutely unavoidable. In recent years, several
+other `\MF{}' fonts have been converted to Type~1 format; it's
+uncommon ever to need to generate bitmap fonts for any purpose other
+than previewing~--- see % ! line wrap
+\Qref*{``previewing documents with Type~1 fonts''}{Q-PSpreview}~---
+if even then.
+
+More modern fonts may be used in place of the Computer Modern set. The
+\Qref*{\acro{EC} fonts}{Q-ECfonts} and the % ! line break
+\Qref*{Latin Modern fonts}{Q-uselmfonts} are both close relatives with
+wider ranges of glyphs to offer.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}BaKoMa fonts]\CTANref{bakoma}
+\item[\nothtml{\rmfamily}Bluesky fonts]Distributed as part of
+ \CTANref{amsfonts}
+\item[\nothtml{\rmfamily}CM fonts (write-black printers)]\CTANref{pk300}
+\item[\nothtml{\rmfamily}CM fonts (write-white printers)]\CTANref{pk300w}
+\item[\nothtml{\rmfamily}EC fonts (Type 1 format)]\CTANref{cm-super}
+\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm}
+\end{ctanrefs}
+\LastEdit{2011-09-4}
diff --git a/help/uk-tex-faq/faq-getit.tex b/help/uk-tex-faq/faq-getit.tex
new file mode 100644
index 0000000000..8cdd9ccc5b
--- /dev/null
+++ b/help/uk-tex-faq/faq-getit.tex
@@ -0,0 +1,361 @@
+% $Id: faq-getit.tex,v 1.11 2014/01/22 17:29:03 rf10 Exp $
+
+\section{Acquiring the Software}
+
+\Question[Q-archives]{Repositories of \TeX{} material}
+
+To aid the archiving and retrieval of of \TeX{}-related files, a
+\acro{TUG} working group developed the Comprehensive \TeX{} Archive
+Network (\acro{CTAN}). Each \acro{CTAN} site has identical material,
+and maintains authoritative versions of its material. These
+collections are extensive; in particular, almost everything mentioned
+in this \acro{FAQ}
+is archived at the \acro{CTAN} sites (see the lists of software at the
+end of each answer).
+
+There are two main \acro{CTAN} sites (in Germany and the \acro{UK}),
+but users should ordinarily collect material via the % ! line break
+\href{http://mirror.ctan.org/}{\acro{CTAN} mirror redirector}
+(which connects you to a mirror that is in some sense ``near'' to
+you).
+
+To access a particular thing through the \texttt{mirror.ctan.org}
+mechanism, simply place the \acro{CTAN} path after the base
+\acro{URL}; so
+\URL{http://mirror.ctan.org/macros/latex/contrib/footmisc/} will
+connect you to the \Package{footmisc} directory at some \acro{CTAN}
+mirror.
+
+For details of how to find files at \acro{CTAN} sites, see
+``\Qref*{finding \AllTeX{} files}{Q-findfiles}''.
+
+The \TeX{} user who has no access to any sort of
+network may buy a copy of the archive as part of the
+\Qref*{\texlive{} distribution}{Q-CD}; the disc is, necessarily, out
+of date, but it is likely to be better than what (if anything) came
+with your operating system.
+\LastEdit{2012-12-14}
+
+\Question[Q-tds-zip]{Ready-built installation files on the archive}
+
+The \Qref*{\acro{TDS}}{Q-tds} is a simple structure, and almost all
+files can be installed simply by putting them in the ``right'' place,
+and updating a single index. (Note, this simple idea typically
+doesn't work for fonts, unless they're distributed as \MF{} source.)
+
+The CTAN network is therefore acquiring ``\acro{TDS}-\acro{ZIP}'' files,
+which have a built-in directory structure that matches the \acro{TDS}.
+These files have to be built, and the \acro{CTAN} team has asked that
+package authors supply them (the team will advise, of course, if the
+author has trouble). The \acro{CTAN} team hopes that the extra work
+involved will contribute to happier lives for package users, which in
+turn must surely help keep the TeX community lively and active.
+
+At the time of writing, there are rather few \extension{tds.zip}
+files (by comparison with the huge number of packages that are
+available). As packages are updated, the number of files is
+steadily increasing, but it will be a long time before the whole set
+is covered.
+
+Use of the files is discussed in % ! line break
+``\Qref*{installing using ready-built \acro{ZIP} files}{Q-inst-tds-zip}''.
+
+\Question[Q-nonfree]{What was the \acro{CTAN} \texttt{nonfree} tree?}
+
+When \acro{CTAN} was founded, in the 1990s, it was unusual to publish
+the terms under which a \TeX{}-related package was distributed (or, at
+any rate, to publish those terms formally).
+
+With the advent of the \TeX{} \emph{distributions}, however, people
+started to realise the need for such information, to protect those who
+create, distribute or sell the discs that hold the packages, etc.
+With the licence information available, the distributors can decide
+which packages may be distributed.
+
+The \acro{CTAN} team decided that it would be useful for users (and
+distributors, not to say package authors) to separate packages that
+were candidates for distribution, and those that were in some sense
+``not free''. Thus was the \texttt{nonfree} tree born.
+
+From the start, the \texttt{nonfree} tree was controversial: the terms
+under which a package would be placed on the tree were hotly
+contested, and the \acro{CTAN} team were only able slowly to populate
+the tree. It became obvious to the team that the project would never
+have been completed.
+
+The \acro{CTAN} catalogue now records the nature of the licences of a
+good proportion of the packages it describes (though there remain
+several for which the licence is unknown, which is as good, for the
+distributors, as a licence forbidding distribution). Since the
+catalogue's coverage of \acro{CTAN} is good (and slowly improving),
+the general rule for distributors has become
+\begin{quote}
+``if the package is listed in the catalogue, check there to see
+whether you should distribute; if the package is not listed in the
+catalogue, don't think of distributing it''.
+\end{quote}
+(The catalogue only has a modest % ! line break
+\CTANhref{cat-licences}{list of licences}, but it covers the set used
+by packages on \acro{CTAN}, with a wild-card ``\texttt{other-free}''
+which covers packages that the \acro{CTAN} administrators believe to
+be free even though the authors haven't used a standard licence.)
+
+There is a corollary to the `general rule': if you notice something
+that ought to be in the distributions, for which there is no catalogue
+entry, please let the \acro{CTAN} team (\mailto{ctan@dante.de}) know.
+It may well be that the package has simply been missed, but some aren't
+catalogued because there's no documentation and the team just doesn't
+understand the package.
+
+In the light of the above, the \texttt{nonfree} tree is being
+dismantled, and its contents moved (or moved \emph{back}) to the main
+\acro{CTAN} tree. So the answer to the question is, now, ``the
+nonfree tree was a part of \acro{CTAN}, whose contents are now in
+the main tree''.
+
+\Question[Q-uploads]{Contributing a file to the archives}
+
+You have something to submit to the archive~--- good news!
+
+Before we even start, here's a check-list of things to sort out:
+\begin{enumerate}
+\item Licence: in the spirit of \TeX{}, we hope for free software; in
+ the spirit of today's lawyer-enthralled society, \acro{CTAN}
+ provides a % ! line break
+ \href{http://mirror.ctan.org/help/Catalogue/licenses.html}{list of ``standard'' licence statements}.
+ Make sure that there's a formal statement of the licence of your
+ package, somewhere in the files you upload; beyond the \acro{CTAN}
+ installation, your package is a candidate for inclusion in \AllTeX{}
+ distributions~\dots{} and thereafter, also in operating system
+ distributions~\dots{} and the people who bundle all these things up
+ need a clear statement of your intent.
+\item Documentation: it's good for users to be able to browse
+ documentation before downloading a package. You need at least a
+ plain text \File{README} file (exactly that name, upper case and no
+ \extension{txt} extension); in addition a
+ \acro{PDF} file of the package documentation, prepared for screen
+ reading, is highly desirable.
+\item Name: endless confusion is caused by name clashes. If your
+ package has the same name as one already on \acro{CTAN}, or if your
+ package installation generates files of the same name as something
+ in a ``normal'' distribution, the \acro{CTAN} team will delay
+ installation while they check that you're doing the right thing:
+ they may nag you to change the name, or to negotiate a take-over
+ with the author of the original package. % beware line break
+ \Qref*{Browse the archive}{Q-findfiles} to ensure uniqueness.
+
+ The name you choose should also (as far as possible) be somewhat
+ descriptive of what your submission actually \emph{does}; while
+ ``descriptiveness'' is to some extent in the eye of the beholder,
+ it's clear that names such as \File{mypackage} or \File{jiffy}
+ aren't suitable.
+\end{enumerate}
+You upload via the
+\begin{flatversion}
+ CTAN upload redirector: \URL{http://www.ctan.org/upload}
+\end{flatversion}
+\begin{hyperversion}
+ \href{http://www.ctan.org/upload}{CTAN upload redirector}
+\end{hyperversion}
+(the archive's main page has a link). The upload page shows what it
+needs to know, and allows you to enter the information. The mechanism
+can only accept one file per upload: if you had intended to upload
+lots of files, you need to bundle them into an `archive' file of some
+sort; acceptable formats are \extension{zip} and \extension{tar.gz}
+(most uploads are packed in \extension{zip} format). Once you have
+completed your upload, the redirector assigns it to a member of the
+team for processing.
+
+If you can't use this method, or if you find something confusing, ask
+advice of the
+\begin{flatversion}
+ \acro{CTAN} management team (\mailto{ctan@dante.de}).
+\end{flatversion}
+\begin{hyperversion}
+ \href{mailto:ctan@dante.de}{\acro{CTAN} management team}
+\end{hyperversion}
+
+If your package is large, or regularly updated, it may be appropriate
+to `mirror' your contribution direct into \acro{CTAN}.
+Mirroring is only practical using \texttt{ftp} or \texttt{rsync}, so
+this facility is limited to packages offered by a server that uses one
+of those protocols.
+\begin{ctanrefs}
+\item[README.uploads]\CTANref{CTAN-uploads}
+\end{ctanrefs}
+\LastEdit{2013-01-31}
+
+\Question[Q-findfiles]{Finding \AllTeX{} files}
+
+Modern \TeX{} distributions contain a huge array of various sorts of
+files, but sooner or later most people need to find something that's
+not in their present system (if nothing else, because they've heard
+that something has been updated).
+
+But how to find the files?
+
+Modern distributions (\texlive{} and \miktex{}, at least) provide the
+means to update your system ``over the net''. This is the minimum
+effort route to getting a new file: `simply' find which of the
+distribution's `packages' holds the file in question, and ask the
+distribution to update itself. The mechanisms are different (the two
+distributions exhibit the signs of evolutionary divergence in their
+different niches), but neither is difficult~--- see % ! line break
+``\Qref*{using \miktex{} for installing}{Q-inst-miktex*}'' and % ! line break
+``\Qref*{using \texlive{} for installing}{Q-inst-texlive}''.
+
+There are packages, though, that aren't in the distribution you use
+(or for which the distribution hasn't yet been updated to offer the
+version you need).
+
+Some sources, such as these \acro{FAQ} answers, provide links to
+files: so if you've learnt about a package here, you should be able to
+retrieve it without too much fuss.
+
+Otherwise, \acro{CTAN} provides a full-text search, at its
+\href{http://www.ctan.org/}{`central database'} site, as well as
+topic- and author-based indexes and a link to browse the archive
+itself.
+
+% Two search mechanisms are offered: the simpler search, locating files
+% by name, simply scans a list of files (\File{FILES.byname}~--- see
+% below) and returns a list of matches, arranged neatly as a series of
+% links to directories and to individual files.
+
+% The more sophisticated search looks at the contents of each catalogue
+% entry, and returns a list of catalogue entries that mention the
+% keywords you ask for.
+
+An alternative way to scan the catalogue is to use the catalogue's
+% ! line break
+\href{http://mirrors.ctan.org/help/Catalogue/bytopic.html}{``by topic'' index};
+this is an older mechanism than the topic-based search (above), but is
+well presented (even though its data has not been updated for some time).
+
+In fact, \ProgName{Google}, and other search engines, can be useful
+tools. Enter your search keywords, and you may pick up a package that
+the author hasn't bothered to submit to \acro{CTAN}.
+
+A user of \ProgName{Google} can restrict the search to
+\acro{CTAN} by entering
+\begin{quote}
+ \texttt{site:ctan.org tex-archive \meta{search term(s)}}
+\end{quote}
+in \ProgName{Google}'s ``search box''. You can also enforce the
+restriction using \ProgName{Google}'s ``advanced search'' mechanism;
+other search engines (presumably) have similar facilities.
+
+Many people avoid the need to go over the network at all, for their
+searches, by downloading the file list that the archives' web
+file searches use. This file, \File{FILES.byname},
+presents a unified listing of the archive (omitting directory names and
+cross-links). Its companion \File{FILES.last07days} is also useful, to
+keep an eye on the changes on the archive. Since these files are
+updated only once a day, a nightly automatic download (using
+\ProgName{rsync}) makes good sense.
+\begin{ctanrefs}
+\item[FILES.byname]\CTANref{f-byname}
+\item[FILES.last07days]\CTANref{f-last7}
+\LastEdit{2014-03-19}
+\end{ctanrefs}
+
+\Question[Q-findfont]{Finding new fonts}
+
+Nowadays, new fonts are seldom developed by industrious people using
+\mf{}, but if such do appear, they will nowadays be distributed in
+the same way as any other part of \alltex{} collections. (An
+historical review of Metafont fonts available is held on \acro{CTAN}
+as ``\mf{} font list''.)
+
+Nowadays, most new fonts that appear are only available in some
+scalable outline form, and a large proportion is distributed under
+commercial terms. Such fonts will only make their way to the free
+distributions (at least \texlive{} and \miktex{}) if their licensing
+is such that the distributions can accept them. Commercial fonts
+(those you have to pay for) do not get to distributions, though
+support for some of them is held by \acro{CTAN}.
+
+Arranging for a new font to be usable by \alltex{} is very different,
+depending on which type of font it is, and which \tex{}-alike engine
+you are using; roughly speaking:
+\begin{itemize}
+\item MetaFont fonts will work without much fuss (provided their
+ sources are in the correct place in the installation's tree);
+ \tex{}-with-\ProgName{dvips}, and \pdftex{} are ``happy'' with them.
+ While a new font will need `generating' (by running \mf{}, etc.),
+ distributions are set up to do that ``on the fly'' and to save the
+ results (for next time).
+\item Adobe Type 1 fonts can be made to work, after \extension{tfm}
+ and (usually) \extension{vf} files have been created from their
+ metric (\extension{afm}) files; \extension{map} files also need to
+ be created. Such fonts will work with \pdftex{}, and with the
+ (`vanilla')\alltex{} and \ProgName{dvips} combination.
+\item TrueType fonts can be made to work with \pdftex{}~--- see
+% ! line break
+\href{http://www.radamir.com/tex/ttf-tex.htm}{Using TrueType fonts with \tex{}\dots{}}
+ (a rather dated document, dicsussing use with \miktex{}~1.11).
+\item TrueType and OpenType fonts are the usual sort used by \xetex{}
+ and \luatex{}; while straightforward use is pretty easy, one is
+ well-advised to use a package such as \Package{fontspec} to gain
+ access to the full range of a font's capabilities.
+\end{itemize}
+
+The answer ``\Qref*{choice of scalable fonts}{Q-psfchoice}'' discusses
+fonts that are configured for general (both textual and mathematical)
+use with \AllTeX{}. The list of such fonts is sufficiently short that
+they \emph{can} all be discussed in one answer.
+\begin{ctanrefs}
+\item[fontspec.sty]\CTANref{fontspec}
+\item[\nothtml{\rmfamily}\MF{} font list]\CTANref{mf-list}
+\end{ctanrefs}
+\LastEdit{2014-01-21}
+
+\Question[Q-CD]{The \TeX{} collection}
+
+If you don't have access to the Internet, there are obvious
+attractions to \TeX{} collections on a disc. Even those with net
+access will find large quantities of \TeX{}-related files to hand a
+great convenience.
+
+The \TeX{} collection provides this, together with
+ready-to-run \TeX{} systems for various architectures. The collection
+is distributed on \acro{DVD}, and contains:
+\begin{itemize}
+\item The \texlive{} distribution, including the programs themselves
+ compiled for a variety of architectures; \texlive{} may be
+ run from the \acro{DVD} or installed on hard disc.
+\item Mac\TeX{}: an easy to install \TeX{} system for MacOS/X, based
+ on \texlive{}; this distribution includes a native Mac installer,
+ % ! line break
+ \href{http://www.uoregon.edu/~koch/texshop/}{the \TeX{}Shop front-end}
+ and other Mac-specific tools;
+\item Pro\TeX{}t: an easy to install \TeX{} system for Windows, based
+ on \miktex{}, based on an `active' document that guides
+ installation; and
+\item A snapshot of \acro{CTAN}.
+\end{itemize}
+A fair number of national \TeX{} User Groups, as well as \acro{TUG},
+distribute copies to their members at no extra charge. Some user
+groups are also able to sell additional copies:
+contact your local user group or \Qref*{\acro{TUG}}{Q-TUG*}.
+
+You may also download disc images from \acro{CTAN}; the installation
+disc, Pro\TeX{}t and Mac\TeX{} are all separately available. Beware:
+they are all pretty large downloads. \texlive{}, once installed, may
+be updated online.
+
+More details of the collection are available from
+\begin{hyperversion}
+ \href{http://www.tug.org/texcollection/}{its own web page}
+ on the \acro{TUG} site.
+\end{hyperversion}
+\begin{flatversion}
+ its own web page on the
+ \acro{TUG} site \URL{http://www.tug.org/texcollection/}
+\end{flatversion}
+\begin{ctanrefs}
+\item[Mac\TeX{}]\CTANref{mactex}
+\item[Pro\TeX{}t]\CTANref{protext}
+\item[\texlive{} install image]\CTANref{texlive}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-graphics.tex b/help/uk-tex-faq/faq-graphics.tex
new file mode 100644
index 0000000000..bd90cc183c
--- /dev/null
+++ b/help/uk-tex-faq/faq-graphics.tex
@@ -0,0 +1,1035 @@
+% $Id: faq-graphics.tex,v 1.27 2014/01/22 17:29:03 rf10 Exp $
+
+\section{Graphics}
+
+\Question[Q-impgraph]{Importing graphics into \AllTeX{} documents}
+
+Knuth, when designing the current version of \TeX{} back in the early
+1980s, could discern no ``standard'' way of expressing graphics in
+documents. He reasoned that this state could not persist for ever,
+but that it would be foolish for him to define \TeX{} primitives that
+allowed the import of graphical image definitions. He therefore
+deferred the specification of the use of graphics to the writers of
+\acro{DVI} drivers; \TeX{} documents would control the drivers by
+means of \nothtml{\csx{special} commands (}% beware line breaks
+\Qref{\csx{special} commands}{Q-specials}\nothtml{)}.
+
+There is therefore a straightforward way for anyone to import graphics
+into their document: read the specification of the \csx{special}
+commands your driver uses, and `just' code them. This is the
+hair-shirt approach: it definitely works, but it's not for everyone.
+
+Over the years, therefore, ``graphics inclusion'' packages have sprung
+up; most were designed for inclusion of
+\nothtml{Encapsulated \PS{} graphics (}% beware line break
+\Qref{Encapsulated \PS{} graphics}{Q-eps}\nothtml{)}\nobreakspace---
+which has become the \emph{lingua franca} of graphics inclusion over
+the last decade or so.
+
+Notable examples are the \Package{epsf} package (distributed with
+\ProgName{dvips}) and the \Package{psfig} package. (Both of these
+packages were designed to work well with both \plaintex{} and
+\LaTeXo{}; they are both still available.) All such packages were
+tied to a particular \acro{DVI} driver (\ProgName{dvips}, in
+the above two cases), but their code could be configured for others.
+
+The obvious next step was to make the code configurable dynamically.
+The \LaTeX{} standard \Package{graphics} package and its derivatives
+made this step: it is strongly preferred for all current work.
+
+Users of \plaintex{} have two options allowing them to use
+\Package{graphicx}: the \Package{miniltx} ``\LaTeX{} emulator'' and
+the \Package{graphicx.tex} front-end allow you to load
+\Package{graphicx}, and \Qref*{\Eplain}{Q-eplain} allows you to load
+it (using the full \LaTeX{} syntax) direct.
+
+The \Package{graphics} package takes a variety of ``driver
+options''~--- package options that select code to generate the
+commands appropriate to the \acro{DVI} driver in use. In most cases,
+your \AllTeX{} distribution will provide a \File{graphics.cfg} file
+that will select the correct driver for what you're doing (for
+example, a distribution that provides both \LaTeX{} and \PDFLaTeX{}
+will usually provide a configuration file that determines whether
+\PDFLaTeX{} is running, and selects the definitions for it if so).
+
+The \Package{graphics} package provides a toolkit of commands (insert
+graphics, scale a box, rotate a box), which may be composed to provide
+most facilities you need; the basic command, \csx{includegraphics},
+takes one optional argument, which specifies the bounding box of the
+graphics to be included.
+
+The \Package{graphicx} package uses the facilities of of
+\Package{graphics} behind a rather more sophisticated command syntax
+to provide a very powerful version of the \csx{includegraphics}
+command. \Package{graphicx}'s version can combine scaling and
+rotation, viewporting and clipping, and many other things. While this
+is all a convenience (at some cost of syntax), it is also capable of
+producing noticeably more efficient \PS{}, and some of its
+combinations are simply not possible with the \Package{graphics}
+package version.
+
+The \Package{epsfig} package provides the same facilities as
+\Package{graphicx}, but via a \csx{psfig} command (also known as
+\csx{epsfig}), capable of emulating
+the behaviour (if not the bugs) the old \Package{psfig} package.
+\Package{Epsfig} also supplies homely support for former users of the
+\Package{epsf} package. However, there's a support issue: if you
+declare you're using \Package{epsfig}, any potential mailing list or
+usenet helper has to clear out of the equation the possibility that
+you're using ``old'' \Package{epsfig}, so that support is slower
+coming than it would otherwise be.
+
+There is no rational reason to stick with the old packages, which have
+never been entirely satisfactory in the \LaTeX{} context. (One
+irrational reason to leave them behind is that their replacement's
+name tends not to imply that it's exclusively related to \PS{}
+graphics. The reasoning also excludes \Package{epsfig}, of course.)
+
+A wide variety of detailed techniques and tricks have been developed
+over the years, and Keith Reckdahl's \Package{epslatex} outlines them
+in compendious detail: this highly recommendable document is available
+from \acro{CTAN}. An invaluable review of the practicalities of
+exchanging graphics between sites,
+% beware multiple line break problems
+\begin{wideversion} % hyperversion
+``\href{http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf}{Graphics for Inclusion in Electronic Documents}''
+\end{wideversion}
+\begin{narrowversion} % non-hyper
+\href{http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf}%
+ {``Graphics for Inclusion in Electronic Documents''}
+\end{narrowversion}
+has been written by Ian Hutchinson; the document isn't on \acro{CTAN},
+but may also be
+% beware line breaks
+\href{http://silas.psfc.mit.edu/elec_fig/}{browsed on the Web}.
+\begin{ctanrefs}
+\item[epsf.tex]\CTANref{epsf}
+\item[epsfig.sty]Part of the \CTANref{graphics} bundle
+\item[epslatex.pdf]\CTANref{epslatex}
+\item[graphics.sty]\CTANref{graphics}
+\item[graphicx.sty]Part of the \CTANref{graphics} bundle
+\item[miniltx.tex]\CTANref{graphics-plain}
+\item[psfig.sty]\CTANref{psfig}
+\end{ctanrefs}
+
+\Question[Q-dvipsgraphics]{Imported graphics in \ProgName{dvips}}
+
+\ProgName{Dvips}, as originally conceived, can only import a single
+graphics format: \nothtml{encapsulated \PS{} (\extension{eps} files, }%
+\Qref{encapsulated \PS{}}{Q-eps}\htmlonly{ (\extension{eps} files}).
+\ProgName{Dvips} also deals with the slightly eccentric \acro{EPS} that is
+created by \Qref*{\MP{}}{Q-MP}.
+
+Apart from the fact that a depressing proportion of drawing
+applications produce corrupt \acro{EPS} when asked for such output,
+this is pretty satisfactory for vector graphics work.
+
+To include bitmap graphics, you need some means of converting them to
+\PS{}; in fact many standard image manipulators (such as
+\ProgName{ImageMagick}'s \ProgName{convert}) make a good job of
+creating \acro{EPS} files (but be sure to ask for output at \PS{}
+level~2 or higher). (\ProgName{Unix} users should beware of
+\ProgName{xv}'s claims: it has a tendency to downsample your bitmap to
+your screen resolution.)
+
+Special purpose applications \ProgName{jpeg2ps} (which converts
+\acro{JPEG} files using \PS{} level 2 functionality),
+\ProgName{bmeps} (which converts both \acro{JPEG} and \acro{PNG}
+files) and \ProgName{a2ping}/\ProgName{sam2p} (which convert a
+bewildering array of bitmap formats to \acro{EPS} or \acro{PDF} files;
+\ProgName{sam2p} is one of the engines that \ProgName{a2ping} uses)
+are also considered ``good bets''.
+
+\ProgName{Bmeps} comes with patches to produce your own version of
+\ProgName{dvips} that can cope with \acro{JPEG} and \acro{PNG} direct,
+using \ProgName{bmeps}'s conversion library. \ProgName{Dvips}, as
+distributed by \miktex{}, comes with those patches built-in, but
+assuming that capability destroys portability, and is only
+recommendable if you are sure you will never want to share your
+document.
+\begin{ctanrefs}
+\item[a2ping]\CTANref{a2ping}
+\item[bmeps]Distributed as part of \CTANref{dktools}[bmeps]
+\item[jpeg2ps]\CTANref{jpeg2ps}
+\item[sam2p]\CTANref{sam2p}
+\end{ctanrefs}
+
+\Question[Q-pdftexgraphics]{Imported graphics in \PDFLaTeX{}}
+
+\PDFTeX{} itself has a rather wide range of formats that it can
+``natively'' incorporate into its output \acro{PDF} stream:
+\acro{JPEG} (\extension{jpg} files) for photographs and similar images,
+\acro{PNG} files for artificial bitmap images, and \acro{PDF} for
+vector drawings. Old versions of \PDFTeX{} (prior to version~1.10a)
+supported \acro{TIFF} (\extension{tif} files) format as an alternative
+to \acro{PNG} files; don't rely on this facility, even if you
+\emph{are} running an old enough version of \PDFTeX{}\dots{}
+
+In addition to the `native' formats, the standard \PDFLaTeX{}
+\Package{graphics} package setup causes Hans Hagen's \File{supp-pdf}
+macros to be loaded: these macros are capable of translating the
+output of \MP{} to \acro{PDF} ``on the fly''; thus \MP{} output
+(\extension{mps} files) may also be included in \PDFLaTeX{} documents.
+
+The commonest problem users encounter, when switching from \TeX{}, is
+that there is no straightforward way to include \acro{EPS} files:
+since \PDFTeX{} is its own ``driver'', and since it contains no means
+of converting \PS{} to \acro{PDF}, there's no direct way the job can
+be done.
+
+The simple solution is to convert the \acro{EPS} to an appropriate
+\acro{PDF} file. The \ProgName{epstopdf} program will do this: it's
+available either as a Windows executable or as a \ProgName{Perl}
+script to run on Unix and other similar systems. A \LaTeX{} package,
+\Package{epstopdf}, can be used to generate the requisite \acro{PDF}
+files ``on the fly''; this is convenient, but requires that you
+suppress one of \TeX{}'s security checks: don't allow its use in files
+from sources you don't entirely trust.
+
+The package \Package{pst-pdf} permits other things than `mere'
+graphics files in its argument. \Package{Pst-pdf} operates (the
+authors suggest) ``like \BibTeX{}''~--- you process your file using
+\PDFLaTeX{}, then use \LaTeX{}, \ProgName{dvips} and \ProgName{ps2pdf}
+in succession, to produce a secondary file to input to your next
+\PDFLaTeX{} run. (Scripts are provided to ease the production of the
+secondary file.)
+
+A further extension is \Package{auto-pst-pdf}, which generates
+\acro{PDF} (essentially) transparently, by spawning a job to process
+output such as \Package{pst-pdf} uses. If your \pdflatex{}
+installation doesn't automatically allow it~--- see % ! line break
+\Qref*{spawning a process}{Q-spawnprog}~--- then you need to start
+\pdflatex{} with:
+\begin{quote}
+\begin{verbatim}
+pdflatex -shell-escape <file>
+\end{verbatim}
+\end{quote}
+for complete `automation'.
+
+An alternative solution is to use \ProgName{purifyeps}, a
+\ProgName{Perl} script which uses the good offices of
+\ProgName{pstoedit} and of \MP{} to convert your Encapsulated \PS{} to
+``Something that looks like the encapsulated \PS{} that comes out of
+\MP{}'', and can therefore be included directly. Sadly,
+\ProgName{purifyeps} doesn't work for all \extension{eps} files.
+
+Good coverage of the problem is to be found in Herbert Vo\ss {}'s
+\href{http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput}{\acro{PDF} support page},
+which is targeted at the use of \Package{pstricks} in
+\PDFLaTeX{}, and also covers the \Package{pstricks}-specific package
+\Package{pdftricks}. A recent alternative (not covered in % ! line break
+Herbert Vo\ss {}'s page) is \Package{pdftricks2}, which offers similar
+facilities to \Package{pdftricks}, but with some useful variations.
+\begin{ctanrefs}
+\item[auto-pst-pdf.sty]\CTANref{auto-pst-pdf}
+\item[epstopdf]Browse \CTANref{epstopdf}
+\item[epstopdf.sty]Distributed with Heiko Oberdiek's packages
+ \CTANref{oberdiek}
+\item[pdftricks.sty]\CTANref{pdftricks}
+\item[pdftricks2.sty]\CTANref{pdftricks2}
+\item[pst-pdf.sty]\CTANref{pst-pdf}
+\item[pstoedit]\CTANref{pstoedit}
+\item[purifyeps]\CTANref{purifyeps}
+\end{ctanrefs}
+\LastEdit{2012-11-20}
+
+\Question[Q-dvipdfmgraphics]{Imported graphics in \ProgName{dvipdfm}}
+
+\ProgName{Dvipdfm} (and \ProgName{dvipdfmx}) translates direct from
+\acro{DVI} to \acro{PDF} (all other available routes produce \PS{}
+output using \ProgName{dvips} and then convert that to \acro{PDF} with
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+or \ProgName{Acrobat}'s \ProgName{Distiller}).
+
+\ProgName{Dvipdfm}/\ProgName{Dvipdfmx} are particularly flexible
+applications. They permit the inclusion of bitmap and \acro{PDF}
+graphics (as does \Qref*{\PDFTeX{}}{Q-pdftexgraphics}), but are also
+capable of employing
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} ``on the
+fly'' to permit the inclusion of encapsulated \PS{} (\extension{eps})
+files by translating them to \acro{PDF}. In this way, they combine the good
+qualities of \ProgName{dvips} and of \PDFTeX{} as a means of
+processing illustrated documents.
+
+Unfortunately, ``ordinary'' \LaTeX{} can't deduce the bounding box of
+a binary bitmap file (such as \acro{JPEG} or \acro{PNG}), so you have
+to specify the bounding box. This may be done explicitly, in the
+document:
+\begin{quote}
+\begin{verbatim}
+\usepackage[dvipdfm]{graphicx}
+...
+\includegraphics[bb=0 0 540 405]{photo.jpg}
+\end{verbatim}
+\end{quote}
+It's usually not obvious what values to give the ``\texttt{bb}'' key,
+but the program \ProgName{ebb} will generate a file
+containing the information; the above numbers came from an
+\ProgName{ebb} output file \File{photo.bb}:
+\begin{quote}
+\begin{verbatim}
+%%Title: /home/gsm10/photo.jpg
+%%Creator: ebb Version 0.5.2
+%%BoundingBox: 0 0 540 405
+%%CreationDate: Mon Mar 8 15:17:47 2004
+\end{verbatim}
+\end{quote}
+If such a file is available, you may abbreviate the inclusion
+code, above, to read:
+\begin{quote}
+\begin{verbatim}
+\usepackage[dvipdfm]{graphicx}
+...
+\includegraphics{photo}
+\end{verbatim}
+\end{quote}
+which makes the operation feel as simple as does including
+\extension{eps} images in a \LaTeX{} file for processing with
+\ProgName{dvips}; the \Package{graphicx} package knows to look for a
+\extension{bb} file if no bounding box is provided in the
+\csx{includegraphics} command.
+
+The one place where usage isn't quite so simple is the need to quote
+\ProgName{dvipdfm} explicitly, as an option when loading the
+\Package{graphicx} package: if you are using \ProgName{dvips}, you
+don't ordinarily need to specify the fact, since the default graphics
+configuration file (of most distributions) ``guesses'' the
+\texttt{dvips} option if you're using \TeX{}.
+\begin{ctanrefs}
+\item[dvipdfm]\CTANref{dvipdfm}
+\item[dvipdfmx]\CTANref{dvipdfmx}
+\item[ebb]Distributed as part of \CTANref{dvipdfm}
+\end{ctanrefs}
+\LastEdit{2013-06-03}
+
+\Question[Q-grffilenames]{``Modern'' graphics file names}
+
+\TeX{} was designed in a world where file names were very simple
+indeed, typically strictly limited both in character set and length.
+In modern systems, such restrictions have largely disappeared, which
+leaves \TeX{} rather at odds with its environment. Particular
+problems arise with spaces in file names, but things like multiple
+period characters can seriously confuse the \Package{graphics}
+package.
+
+The specification of \TeX{} leaves some leeway for distributions to
+adopt file access appropriate to their operating system, but this
+hasn't got us very far. Many modern distributions allow you to
+specify a file name as \texttt{"file name.tex"} (for example), which
+helps somewhat, but while this allows us to say
+\begin{quote}
+\begin{verbatim}
+\input "foo bar.tex"
+\end{verbatim}
+\end{quote}
+the analogous usage
+\begin{quote}
+\begin{verbatim}
+\includegraphics{"gappy graphics.eps"}
+\end{verbatim}
+\end{quote}
+using ``ordinary'' \LaTeX{} causes confusion in \ProgName{xdvi} and
+\ProgName{dvips}, even though it works at compilation time. Sadly,
+even within such quotes, multiple dots give \csx{includegraphics}
+difficulties. Note that
+\begin{quote}
+\begin{verbatim}
+\includegraphics{"gappy graphics.pdf"}
+\end{verbatim}
+\end{quote}
+works in a similar version of \PDFTeX{}.
+
+If you're using the \Package{graphics} package, the \Package{grffile}
+package will help. The package offers several options, the simplest
+of which are \pkgoption{multidot} (allowing more than one dot in a
+file name) and \pkgoption{space} (allowing space in a file name). The
+\pkgoption{space} option requires that you're running on a
+sufficiently recent version of \PDFTeX{}, in \acro{PDF} mode~--- and
+even then it won't work for \MP{} files, which are read as \TeX{}
+input, and therefore use the standard input mechanism).
+\begin{ctanrefs}
+\item[grffile.sty]Distributed as part of \CTANref{oberdiek}[grffile]
+\end{ctanrefs}
+
+\Question[Q-graphicspath]{Importing graphics from ``somewhere else''}
+
+By default, graphics commands like \csx{includegraphics} look
+``wherever \TeX{} files are found'' for the graphic file they're being
+asked to use. This can reduce your flexibility if you choose to hold
+your graphics files in a common directory, away from your \AllTeX{}
+sources.
+
+The simplest solution is to patch \TeX{}'s path, by changing the
+default path. On most systems, the default path is taken from the
+environment variable \texttt{TEXINPUTS}, if it's present; you can adapt that
+to take in the path it already has, by setting the variable to
+\begin{quote}
+\begin{verbatim}
+TEXINPUTS=.:<graphics path(s)>:
+\end{verbatim}
+\end{quote}
+on a Unix system; on a Windows system the separator will be ``\texttt{;}''
+rather than ``\texttt{:}''. The ``\texttt{.}'' is there to ensure
+that the current directory is searched first; the trailing
+``\texttt{:}'' says ``patch in the value of \texttt{TEXINPUTS} from
+your configuration file, here''.
+
+This method has the merit of efficiency (\AllTeX{} does \emph{all} of
+the searches, which is quick), but it's always clumsy and may prove
+inconvenient to use in Windows setups (at least).
+
+The alternative is to use the \Package{graphics} package command
+\csx{graphicspath}; this command is of course also available to users
+of the \Package{graphicx} and the \Package{epsfig} packages. The
+syntax of \csx{graphicspath}'s one argument is slightly odd: it's a
+sequence of paths (typically relative paths), each of which is
+enclosed in braces. A slightly odd example (slightly modified from one
+given in the \Package{graphics} bundle documentation) is:
+\begin{quote}
+\begin{verbatim}
+\graphicspath{{eps/}{png/}}
+\end{verbatim}
+\end{quote}
+which will search for graphics files in subdirectories \File{eps} and
+\File{png} of the directory in which \latex{} is running. (Note that
+the trailing ``\texttt{/}'' \emph{is} required.)
+
+(Note that some \AllTeX{} systems will only allow you to use files in
+the current directory and its sub-directories, for security reasons.
+However, \csx{graphicspath} imposes no such restriction: as far as
+\emph{it} is concerned, you can access files anywhere.)
+
+Be aware that \csx{graphicspath} does not affect the operations of
+graphics macros other than those from the graphics bundle~--- in
+particular, those of the outdated \Package{epsf} and
+\Package{psfig} packages are immune.
+
+The slight disadvantage of the \csx{graphicspath} method is
+inefficiency. The package will call \AllTeX{} once for each entry in
+the list to look for a file, which of course slows things. Further,
+\AllTeX{} remembers the name of any file it's asked to look up, thus
+effectively losing memory, so that in the limit a document that uses a
+huge number of graphical inputs could be embarrassed by lack of
+memory. (Such ``memory starvation'' is pretty unlikely with any
+ordinary document in a reasonably modern \AllTeX{} system, but it
+should be borne in mind.)
+
+If your document is split into a variety of directories, and each
+directory has its associated graphics, the \Package{import} package
+may well be the thing for you; see the discussion % beware line break
+\latexhtml{of ``bits of document in other directories'' (}{in the question ``}%
+\Qref{bits of document in other directories}{Q-docotherdir}%
+\latexhtml{)}{''}.
+\begin{ctanrefs}
+\item[graphics \nothtml{\rmfamily}bundle]\CTANref{graphics}
+\item[import.sty]\CTANref{import}
+\end{ctanrefs}
+
+\Question[Q-graph-pspdf]{Portable imported graphics}
+
+A regular need is a document to be distributed in more than
+one format: commonly both \PS{} and \acro{PDF}. The
+following advice is based on a post by one with much experience of
+dealing with the problem of dealing with \acro{EPS} graphics in this
+case.
+\begin{itemize}
+\item Don't specify a driver when loading loading whichever version of
+ the \Package{graphics} package you use. The scheme relies on the
+ distribution's ability to decide which driver is going to be used:
+ the choice is between \ProgName{dvips} and \PDFTeX{}, in this case.
+ Be sure to exclude options \pkgoption{dvips}, \pkgoption{pdftex} and
+ \pkgoption{dvipdfm} (\ProgName{dvipdfm} is not used in this scheme,
+ but the aspirant \acro{PDF}-maker may be using it for his output,
+ before switching to the scheme).
+\item Use \cmdinvoke{includegraphics}[...]{filename} without
+ specifying the extension (i.e., neither \extension{eps} nor
+ \extension{pdf}).
+\item For every \extension{eps} file you will be including, produce a
+ \extension{pdf} version, as described in % beware line break
+ \Qref[question]{Graphics in \PDFLaTeX{}}{Q-pdftexgraphics}. Having
+ done this, you will have two copies of each graphic (a \extension{eps}
+ and a \extension{pdf} file) in your directory.
+\item Use \PDFLaTeX{} (rather than
+ \LaTeX{}--\ProgName{dvips}--distillation or
+ \LaTeX{}--\ProgName{dvipdfm}) to produce your \acro{PDF} output.
+\end{itemize}
+\ProgName{Dvipdfm}'s charms are less than attractive here: the
+document itself needs to be altered from its default
+(\ProgName{dvips}) state, before \ProgName{dvipdfm} will process it.
+
+\Question[Q-repeatgrf]{Repeated graphics in a document}
+
+A logo or ``watermark'' image, or any other image that is repeated in
+your document, has the potential to make the processed version of the
+document unmanageably large. The problem is, that the default
+mechanisms of graphics usage add the image at every point it's to be
+used, and when processed, the image appears in the output file at each
+such point.
+
+Huge \PS{} files are embarrassing; explaining \emph{why} such a file
+is huge, is more embarrassing still.
+
+The \Qref*{\File{epslatex} graphics tutorial}{Q-tutbitslatex}
+describes a technique for avoiding the problem: basically, one
+converts the image that's to be repeated into a \PS{} subroutine, and
+load that as a \ProgName{dvips} prologue file. In place of the image,
+you load a file (with the same bounding box as the image) containing
+no more than an invocation of the subroutine defined in the prologue.
+
+The \File{epslatex} technique is tricky, but does the job. Trickier
+still is the neat scheme of converting the figure to a one-character
+Adobe Type~3 outline font. While this technique is for the ``real
+experts'' only (the author of this answer has never even tried it), it has
+potential for the same sort of space saving as the \File{epslatex}
+technique, with greater flexibility in actual use.
+
+More practical is Hendri Adriaens' \Package{graphicx-psmin}; you load
+this \emph{in place} of \Package{graphicx}, so rather than:
+\begin{quote}
+\begin{verbatim}
+\usepackage[<options>]{graphicx}
+\end{verbatim}
+\end{quote}
+you will write:
+\begin{quote}
+\begin{verbatim}
+\usepackage[<options>]{graphicx-psmin}
+\end{verbatim}
+\end{quote}
+and at the start of your document, you write:
+\begin{quote}
+\begin{verbatim}
+\loadgraphics[<bb>]{<list of graphics>}
+\end{verbatim}
+\end{quote}
+and each of the graphics in the list is converted to an ``object'' for
+use within the resulting \PS{} output. (This is, in essence, an
+automated version of the \File{epslatex} technique described above.)
+
+Having loaded the package as above, whenever you use
+\csx{includegraphics}, the command checks if the file you've asked for
+is one of the graphics in \csx{loadgraphics}' list. If so, the
+operation is converted into a call to the ``object'' rather than a new
+copy of the file; the resulting \PS{} can of course be \emph{much} smaller.
+
+Note that the package requires a recent \ProgName{dvips}, version
+5.95b (this version isn't~--- yet~--- widely distributed).
+
+If your \PS{} is destined for conversion to \acro{PDF}, either by a
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}-based
+mechanism such as \ProgName{ps2pdf} or by
+(for example) \ProgName{Acrobat} \ProgName{Distiller}, the issue isn't
+so pressing, since the distillation mechanism will amalgamate graphics
+objects whether or not the \PS{} has them amalgamated. \PDFTeX{} does
+the same job with graphics, automatically converting multiple uses
+into references to graphics objects.
+\begin{ctanrefs}
+\item[graphicx-psmin.sty]\CTANref{graphicx-psmin}
+\end{ctanrefs}
+\LastEdit{2013-06-03}
+
+\Question[Q-grmaxwidth]{Limit the width of imported graphics}
+
+Suppose you have graphics which may or may not be able to fit within
+the width of the page; if they will fit, you want to set them at their
+natural size, but otherwise you want to scale the whole picture so
+that it fits within the page width.
+
+You do this by delving into the innards of the graphics package (which
+of course needs a little \LaTeX{} internals programming):
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\def\maxwidth{%
+ \ifdim\Gin@nat@width>\linewidth
+ \linewidth
+ \else
+ \Gin@nat@width
+ \fi
+}
+\makeatother
+\end{verbatim}
+\end{quote}
+This defines a ``variable'' width which has the properties you want.
+Replace \csx{linewidth} if you have a different constraint on the width
+of the graphic.
+
+Use the command as follows:
+\begin{quote}
+\begin{verbatim}
+\includegraphics[width=\maxwidth]{figure}
+\end{verbatim}
+\end{quote}
+
+\Question[Q-topgraph]{Top-aligning imported graphics}
+
+When \TeX{} sets a line of anything, it ensures that the base-line of
+each object in the line is at the same level as the base-line of the
+final object. (Apart, of course, from \csx{raisebox} commands\dots{})
+
+Most imported graphics have their base-line set at the bottom of the
+picture. When using packages such as \Package{subfig}, one often
+wants to align figures by their tops. The following odd little bit of
+code does this:
+\begin{quote}
+\begin{verbatim}
+\vtop{%
+ \vskip0pt
+ \hbox{%
+ \includegraphics{figure}%
+ }%
+}
+\end{verbatim}
+\end{quote}
+The \csx{vtop} primitive sets the base-line of the resulting object to
+that of the first ``line'' in it; the \csx{vskip} creates the illusion
+of an empty line, so \csx{vtop} makes the very top of the box into the
+base-line.
+
+In cases where the graphics are to be aligned with text, there is a
+case for making the base-line one ex-height below the top of the box,
+as in:
+\begin{quote}
+\begin{verbatim}
+\vtop{%
+ \vskip-1ex
+ \hbox{%
+ \includegraphics{figure}%
+ }%
+}
+\end{verbatim}
+\end{quote}
+A more \LaTeX{}-y way of doing the job (somewhat inefficiently) uses
+the \Package{calc} package:
+\begin{quote}
+\begin{verbatim}
+\usepackage{calc}
+...
+\raisebox{1ex-\height}{\includegraphics{figure}}
+\end{verbatim}
+\end{quote}
+(this has the same effect as the text-align version, above).
+
+The fact is, \emph{you} may choose where the base-line ends up. This
+answer merely shows you sensible choices you might make.
+
+\Question[Q-mpprologues]{Displaying \MP{} output in \ProgName{ghostscript}}
+
+\MP{} ordinarily expects its output to be included in some context
+where the `standard' \MF{} fonts (that you've specified) are already
+defined~--- for example, as a figure in \TeX{} document. If you're
+debugging your \MP{} code, you may want to view it in a
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}-based (or some
+other \PS{}) previewer, but note that viewers (even
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}})
+\emph{don't} ordinarily have the fonts loaded, and you'll experience
+an error such as
+\begin{quote}
+\begin{verbatim}
+Error: /undefined in cmmi10
+\end{verbatim}
+\end{quote}
+There is provision in \MP{} for avoiding this problem: issue the
+command \texttt{prologues := 2;} at the start of the \extension{mp} file.
+
+Unfortunately, the \PS{} that \MP{} inserts in its output,
+following this command, is incompatible with ordinary use of the
+\PS{} in inclusions into \AllTeX{} documents, so it's best to
+make the \texttt{prologues} command optional. Furthermore, \MP{} takes a
+very simple-minded approach to font encoding: since \TeX{} font
+encodings are anything but simple, encoding of text in diagrams are
+another source of problems. If you're suffering such problems (the
+symptom is that
+characters disappear, or are wrongly presented) the solution is
+to view the `original' \MP{} output after processing through
+\LaTeX{} and \ProgName{dvips}.
+
+Conditional compilation may be done either
+by inputting \File{MyFigure.mp} indirectly from a simple wrapper
+\File{MyFigureDisplay.mp}:
+\begin{quote}
+\begin{verbatim}
+prologues := 2;
+input MyFigure
+\end{verbatim}
+\end{quote}
+or by issuing a shell command such as
+\begin{quote}
+\begin{verbatim}
+mp '\prologues:=2; input MyFigure'
+\end{verbatim}
+\end{quote}
+(which will work without the quote marks if you're not using a Unix
+shell).
+
+A suitable \LaTeX{} route would involve processing
+\File{MyFigure.tex}, which contains:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\usepackage{graphicx}
+\begin{document}
+\thispagestyle{empty}
+\includegraphics{MyFigure.1}
+\end{document}
+\end{verbatim}
+\end{quote}
+Processing the resulting \acro{DVI} file with the \ProgName{dvips}
+command
+\begin{quote}
+\begin{verbatim}
+dvips -E -o MyFigure.eps MyFigure
+\end{verbatim}
+\end{quote}
+would then give a satisfactory Encapsulated \PS{} file. This
+procedure may be automated using the \ProgName{Perl} script
+\ProgName{mps2eps}, thus saving a certain amount of tedium.
+
+The \plaintex{} user may use an adaptation, by
+Dan Luecking, of a jiffy of Knuth's. Dan's version
+\Package{mpsproof.tex} will work under
+\TeX{} to produce a \acro{DVI} file for use with \ProgName{dvips}, or
+under \PDFTeX{} to produce a \acro{PDF} file, direct. The output is
+set up to look like a proof sheet.
+
+A script application, \ProgName{mptopdf}, is available in recent
+\AllTeX{} distributions: it seems fairly reliably to produce
+\acro{PDF} from \MP{}, so may reasonably be considered an answer to
+the question\dots{}
+\begin{ctanrefs}
+\item[mps2eps]\CTANref{mps2eps}
+\item[mpsproof.tex]Distributed as part of the \MP{} distribution \CTANref{metapost}
+\item[mptopdf]Part of \CTANref{pdftex-graphics}
+\end{ctanrefs}
+\LastEdit{2013-04-23}
+
+\Question[Q-drawing]{Drawing with \TeX{}}
+
+There are many packages to do pictures in \AllTeX{} itself (rather than
+importing graphics created externally), ranging from simple use of
+\LaTeX{} \environment{picture} environment, through enhancements like
+\ProgName{eepic}, to
+sophisticated (but slow) drawing with \pictex{}. Depending on your type
+of drawing, and setup, here are a few systems you may consider:
+\begin{itemize}
+\item The \environment{picture} environment provides rather primitive
+ drawing capabilities (anything requiring more than linear
+ calculations is excluded, unless a font can come to your help). The
+ environment's tedious insistence on its own \csx{unitlength}, as the
+ basic measurement in a diagram, may be avoided by use of the
+ \Package{picture} package, which detects whether a length is quoted
+ as a number or as a length, and acts accordingly.
+\item \Package{epic} was designed to make use of the \LaTeX{}
+ \environment{picture} environment somewhat less agonising;
+ \Package{eepic} extends it, and is capable of using \ProgName{tpic}
+ \csx{special} commands to improve printing performance. (If the
+ \csx{special}s aren't available, the \Package{eepicemu} will do the
+ business, far less efficiently.
+\item \Package{pict2e}; this was advertised in % !line break
+ \Qref*{the \LaTeX{} manual}{Q-latex-books}, but didn't appear for nearly
+ ten years after publication of the book! It removes all the petty
+ restrictions that surround the use of the \environment{picture}
+ environment. It therefore suffers \emph{only} from the rather
+ eccentric drawing language of the environment, and is a far more
+ useful tool than the original environment has ever been. (Note that
+ \Package{pict2e} supersedes David Carlisle's stop-gap
+ \Package{pspicture}.)
+\item \pictex{} is a venerable, and very powerful, system, that draws
+ by placing dots on the page to give the effect of a line or curve. While
+ this has the potential of great power, it is (of course) much slower
+ than any of the other established packages. What's more, there
+ are problems with its \Qref*{documentation}{Q-docpictex}.
+\item \Package{PSTricks} gives you access to the (considerable) power of
+ \PS{} via a set of \tex{} macros, which talk to \PS{} using
+ \Qref*{\csx{special} commands}{Q-specials}. Since \PS{} is itself a
+ pretty powerful programming language, many astounding things can in
+ principle be achieved using \Package{PSTricks} (a wide range of
+ contributed packages, ranging from world mapping to lens design
+ diagrams, is available).
+ \Package{Pstricks}' \csx{special}s are
+ by default specific to \ProgName{dvips}, but there is
+ a \Package{Pstricks} `driver' that allow \Package{Pstricks} to
+ operate under \xetex{}. \PDFTeX{} users may use \Package{pst-pdf},
+ which (like \Package{epstopdf}~--- see % ! line break
+ \Qref[question]{\PDFLaTeX{} graphics}{Q-pdftexgraphics}) generates
+ \acro{PDF} files using an auxiliary program, from \Package{PSTricks}
+ commands (\Package{pst-pdf} also requires a recent installation of
+ the \Package{preview} package).
+
+ There is a \Package{PSTricks} mailing list
+ (\mailto{pstricks@tug.org}) which you may
+ \href{http://tug.org/mailman/listinfo/pstricks}{join}, or you may
+ just browse the % ! line break
+ \href{http://tug.org/pipermail/pstricks/}{list archives}.
+\item \Package{pgf}: while \Package{pstricks} is very powerful and
+ convenient from `traditional' \tex{}, using it with \PDFLaTeX{} is
+ pretty tiresome: if you
+ simply want the graphical capabilities, \Package{pgf}, together with
+ its ``user-oriented'' interface \Package{tikz}, may be a good
+ bet for you. While \acro{PDF} has (in essence) the same graphical
+ capabilities as \PS{}, it isn't programmable; \Package{pgf} provides
+ \LaTeX{} commands that will utilise the graphical capabilities of
+ both \PS{} and \acro{PDF} equally. \Package{Pgf} has extensive
+ mathematical support, which allows it to rival \Package{PSTricks}'
+ use of the computation engine within \PS{}.
+ The \Package{pgf} manual is enormous, but a simple introduction which
+ allows the user to get a feel for the capabilities of the system, is
+ available at \url{http://cremeronline.com/LaTeX/minimaltikz.pdf}
+\item \MP{}; you liked \MF{}, but never got to grips with font files?
+ Try \Qref*{\MP{}}{Q-MP}~---
+ all the power of \MF{}, but it generates \PS{} figures; \MP{}
+ is nowadays part of most serious \AllTeX{} distributions. Knuth
+ uses it for all his work\dots{}
+
+ Note that you can % ! line break
+ \Qref*{``embed'' \MP{} source in your document}{Q-inlgrphapp} (i.e.,
+ keep it in-line with your \latex{} code).
+\item You liked \MF{} (or \MP{}), but find the language difficult?
+ \ProgName{Mfpic} makes up \MF{} or \MP{} code for you using
+ familiar-looking \AllTeX{} macros. Not \emph{quite} the full power
+ of \MF{} or \MP{}, but a friendlier interface, and with \MP{} output
+ the results can be used equally well in either \LaTeX{} or \PDFLaTeX{}.
+\item You liked \pictex{} but don't have enough memory or time? Look
+ at the late Eitan Gurari's \Package{dratex}: it is just as powerful,
+ but is an entirely new implementation which is not as hard on
+ memory, is much more readable and is (admittedly sparsely) documented at
+ \url{http://www.cse.ohio-state.edu/~gurari/tpf/html/README.html},
+ as well as in the author's book ``TeX and LATeX: Drawing and
+ Literate Programming'', which remains available from on-line
+ booksellers.
+\end{itemize}
+
+In addition, there are several means of generating code for your
+graphics application (\ProgName{asymptote}, \ProgName{gnuplot} and
+\MP{}, at least) in-line in your document, and then have them
+processed in a command spawned from your \AllTeX{} run. For details,
+see \Qref{question}{Q-inlgrphapp}.
+\begin{ctanrefs}
+\item[dratex.sty]\CTANref{dratex}
+\item[epic.sty]\CTANref{epic}
+\item[eepic.sty]\CTANref{eepic}
+\item[eepicemu.sty]\CTANref{eepic}
+\item[mfpic]\CTANref{mfpic}
+\item[preview.sty]\CTANref{preview}
+\item[pspicture.sty]\CTANref{pspicture}
+\item[pst-pdf.sty]\CTANref{pst-pdf}
+\item[pgf.sty]\CTANref{pgf}
+\item[pict2e.sty]\CTANref{pict2e}
+\item[pictex.sty]\CTANref{pictex}
+\item[picture.sty]Distributed as part of \CTANref{oberdiek}[picture]
+\item[pstricks]\CTANref{pstricks}
+\item[tikz.sty]Distributed as part of \CTANref{pgf}
+\end{ctanrefs}
+\LastEdit{2012-10-19}
+
+\Question[Q-inlgrphapp]{In-line source for graphics applications}
+
+Some of the free-standing graphics applications may also be used
+(effectively) in-line in \latex{} documents; examples are
+\begin{booklist}
+\item[asymptote]The package \Package{asymptote} (provided in the
+ \ProgName{asymptote} distribution) defines an environment
+ \environment{asy} which arranges that its contents are available for
+ processing, and will therefore be typeset (after ``enough'' runs, in
+ the `usual' \latex{} way).
+
+ Basically, you write
+ \begin{quote}
+ \cmdinvoke{begin}{asy}\\
+ \latexhtml{\hspace*{1em}}{~~}\texttt{\meta{asymptote code}}\\
+ \cmdinvoke{end}{asy}
+ \end{quote}
+ and then execute
+\begin{quote}
+\begin{verbatim}
+latex document
+asy document-*.asy
+latex document
+\end{verbatim}
+\end{quote}
+\item[egplot]Allows you to incorporate \ProgName{GNUplot}
+ instructions in your document, for processing outside of \latex{}.
+ The package provides commands that enable the user to do calculation
+ in \ProgName{GNUplot}, feeding the results into the diagram
+ to be drawn.
+\item[gmp]Allows you to include the source of MetaPost diagrams, with
+ parameters of the diagram passed from the environment call.
+\item[emp]An earlier package providing facilities similar to those of
+ \Package{gmp} (\Package{gmp}'s author hopes that his package will
+ support the facilities \Package{emp}, which he believes is in need
+ of update.)
+\item[mpgraphics]Again, allows you to program parameters of \MP{}
+ diagrams from your \latex{} document, including the preamble details
+ of the \latex{} code in any recursive call from \MP{}.
+\end{booklist}
+In all cases (other than \Package{asymptote}), these packages require
+that you can % ! line break
+\Qref*{run external programs from within your document}{Q-spawnprog}.
+\begin{ctanrefs}
+\item[asymptote.sty]\CTANref{asymptote}
+\item[egplot.sty]\CTANref{egplot}
+\item[emp.sty]\CTANref{emp}
+\item[gmp.sty]\CTANref{gmp}
+\item[mpgraphics.sty]\CTANref{mpgraphics}
+\end{ctanrefs}
+\LastEdit*{2011-03-16}
+
+\Question[Q-drawFeyn]{Drawing Feynman diagrams in \LaTeX{}}
+
+Michael Levine's \Package{feynman} bundle for drawing the diagrams in
+\LaTeXo{} is still available.
+
+Thorsten Ohl's \Package{feynmf} is designed for use with current
+\LaTeX{}, and works in
+combination with \MF{} (or, in its \Package{feynmp} incarnation, with
+\MP{}). The \ProgName{feynmf} or
+\ProgName{feynmp} package reads a description of the diagram written
+in \TeX{}, and writes out code. \MF{} (or \MP{}) can then produce a
+font (or \PS{} file) for use in a subsequent \LaTeX{} run. For
+new users, who have access to \MP{}, the \PS{} version is
+probably the better route, for document portability and other reasons.
+% checked rf 2001/03/22
+
+Jos Vermaseren's \Package{axodraw} is mentioned as an alternative in
+the documentation of \Package{feynmf}, but it is written entirely in
+terms of \ProgName{dvips} \csx{special} commands, and is thus rather
+imperfectly portable.
+
+An alternative approach is implemented by Norman Gray's \Package{feyn}
+package. Rather than creating complete diagrams as postscript images,
+\Package{feyn} provides a font (in a variety of sizes) containing
+fragments, which you can compose to produce complete diagrams. It
+offers fairly simple diagrams which look good in equations, rather
+than complicated ones more suitable for display in figures.
+\begin{ctanrefs}
+\item[axodraw]\CTANref{axodraw}
+\item[feyn \nothtml{\rmfamily}font bundle]\CTANref{feyn}
+\item[feynman bundle]\CTANref{feynman}
+\item[feynmf/feynmp bundle]\CTANref{feynmf}
+\end{ctanrefs}
+
+\Question[Q-labelfig]{Labelling graphics}
+
+``Technical'' graphics (such as graphs and diagrams) are often
+labelled with quite complex mathematical expressions: there are few
+drawing or graphing tools that can do such things (the honourable
+exception being \MP{}, which allows you to program the labels, in
+\AllTeX{}, in the middle of specifying your graphic).
+
+Placing `labels' on graphics produced by all those \emph{other} tools is
+what we discuss here. (Note that the term ``label'' should be
+liberally interpreted; many of the techniques \emph{were} designed for
+use when applying labels to figures, but they may be used equally well
+to draw funny faces on a figure \dots{} or anything.
+
+The time-honoured \Package{psfrag} package can help, if your image is
+included as an (encapsulated) \PS{} file. Place an unique
+text in your graphic, using the normal text features of your tool, and
+you can ask \Package{psfrag} to replace the text with arbitrary
+\AllTeX{} material. \Package{Psfrag}'s ``operative'' command is
+\cmdinvoke{psfrag}{\emph{Orig text}}{\emph{Repl text}}, which
+instructs the system to replace the original (``unique'') text with
+the \TeX{}-typeset replacement text. Optional arguments permit
+adjustment of position, scale and rotation; full details may be found
+in \File{pfgguide} in the distribution.
+
+Since \Package{psfrag} works in terms of (encapsulated) \PS{} files,
+it needs extra work for use with \PDFLaTeX{}. Two techniques are
+available, using \Qref*{\Package{pst-pdf} package}{Q-pdftexgraphics}
+in a mode designed to do this work; and using \Package{pdfrack}.
+
+The \Qref*{\Package{Pst-pdf} package}{Q-pdftexgraphics} can support
+this ``extra work'' usage. In fact, the \Package{pst-pdf} support
+package \Package{auto-pst-pdf} offers a configuration setting
+precisely for use with \Package{psfrag}.
+
+If you have the `right' environment (see below), you could try the
+\Package{pdfrack} script bundle. The script aims to cut each figure
+out of your source, using it to produce a small \latex{} file with
+nothing but the figure inclusion commands. Each of these figure files
+is then processed to \PS{}, compiled using the \csx{psfrag} commands,
+and the resulting output converted to \acro{PDF} again.
+
+\Package{Pdfrack} is written to use the Unix Bourne shell (or
+equivalent); thus your environment needs to be a Unix-based system, or
+some equivalent such as \ProgName{cygwin} under windows. (What is
+more, \Package{pdfrack}'s author is rather disparaging about his
+package; the present author has never tried it.)
+
+The \Package{psfragx} package goes one step further than
+\Package{psfrag}: it provides a means whereby you can put the
+\Package{psfrag} commands into the preamble of your \acro{EPS} file
+itself. \Package{Psfrag} has such a command itself, but deprecates
+it; \Package{psfragx} has cleaned up the facility, and provides a
+script \ProgName{laprint} for use with \ProgName{Matlab} to produce
+appropriately tagged output. (In principle, other graphics
+applications could provide a similar facility, but apparently none does.)
+
+\ProgName{Emacs} users may find the embedded editor \ProgName{iTe} a
+useful tool for placing labels: it's a \AllTeX{}-oriented graphical
+editor written in \ProgName{Emacs Lisp}. You create
+\environment{iteblock} environments containing graphics and text, and
+may then invoke \ProgName{iTe} to arrange the elements relative to one
+another.
+
+Another useful approach is \Package{overpic}, which overlays a
+\environment{picture} environment on a graphic included by use of
+\csx{includegraphics}. This treatment lends itself to ready placement
+of texts and the like on top of a graphic. The package can draw a
+grid for planning your ``attack''; the distribution comes with simple
+examples.
+
+The \Package{lpic} package is somewhat similar to \Package{overpic};
+it defines an environment \environment{lpic} (which places your
+graphic for you): within the environment you may use the command
+\csx{lbl} to position \latex{} material at appropriate places over the
+graphic.
+
+\Package{Pinlabel} is another package whose author thought in the same
+sort of way as that of \Package{overpic}; the documentation explains
+in detail how to plan your `labelling attack'~--- in this case by
+loading your figure into a viewer and taking measurements from it.
+(The package discusses direct use of
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}} as well as
+customised viewers such as
+\href{http://www.ghostgum.com.au/}{\ProgName{gsview}} or
+\ProgName{gv}.)
+
+\Package{Pstricks} can of course do everything
+that \Package{overpic}, \Package{lpic} or \Package{pinlabel}
+can, with all the flexibility of \PS{} programming that it offers.
+This capability is exemplified by the \Package{pst-layout} package,
+which seems to be a superset of both \Package{overpic} and
+\Package{lpic}.
+
+Similarly, \Package{pgf/TikZ} has all the power needed, but no
+explicit package has been released.
+
+The \Package{pstricks} web site has a page with several % ! line break
+\href{http://pstricks.tug.org/main.cgi?file=Examples/overlay}{examples of labelling}
+which will get you started; if \Package{pstricks} is % ! line break
+\Qref*{an option for you}{Q-drawing}, this route is worth a try.
+
+The confident user may, of course, do the whole job in a picture
+environment which itself includes the graphic. I would recommend
+\Package{overpic} or the \Package{pstricks} approach, but such things
+are plainly little more than a convenience over what is achievable
+with the do-it-yourself approach.
+\begin{ctanrefs}
+\item[auto-pst-pdf.sty]\CTANref{auto-pst-pdf}
+\item[gv]\CTANref{gv}
+\item[iTe]\CTANref{ite}
+\item[laprint]Distributed with \CTANref{psfragx}
+\item[lpic.sty]\CTANref{lpic}
+\item[overpic.sty]\CTANref{overpic}
+\item[pdfrack]\CTANref{pdfrack}
+\item[pinlabel.sty]\CTANref{pinlabel}
+\item[pgf.sty]\CTANref{pgf}
+\item[psfrag.sty]\CTANref{psfrag}
+\item[psfragx.sty]\CTANref{psfragx}
+\item[pstricks.sty]\CTANref{pstricks}
+\item[pst-layout.sty]\CTANref{pst-layout}
+\item[pst-pdf.sty]\CTANref{pst-pdf}
+\end{ctanrefs}
+\LastEdit{2013-06-03}
diff --git a/help/uk-tex-faq/faq-how-do-i.tex b/help/uk-tex-faq/faq-how-do-i.tex
new file mode 100644
index 0000000000..ac61e60ef2
--- /dev/null
+++ b/help/uk-tex-faq/faq-how-do-i.tex
@@ -0,0 +1,4134 @@
+% $Id: faq-how-do-i.tex,v 1.47 2014/01/28 18:17:23 rf10 Exp $
+
+\section{How do I do\dots{}?}
+
+\subsection{Mathematics}
+
+\Question[Q-proof]{Proof environment}
+
+It was long thought impossible to make a \environment{proof}
+environment which automatically includes an `end-of-proof' symbol.
+Some proofs end in displayed maths; others do not. If the input file
+contains % ! line break
+\texttt{...\csx{]} }\cmdinvoke{end}{proof} then \LaTeX{} finishes off
+the displayed maths and gets ready for a new line before it reads any
+instructions connected with ending the proof, so the code is very
+tricky. You \emph{can} insert the symbol by hand, but the
+(apparently) original `automatic' solution came with Paul Taylor's
+\Package{QED}.
+
+Nowadays, the \Package{ntheorem} package now solves the problem for
+\LaTeX{} users: it provides an automatic way of signalling
+the end of a proof.
+
+The \AMSLaTeX{} package \Package{amsthm} also provides a
+\environment{proof} environment that does the job; though you need to
+insert a \csx{qedhere} command if the proof ends with a displayed
+equation:
+\begin{quote}
+\begin{verbatim}
+\begin{proof}
+ text...
+ \begin{equation*}
+ maths... \tag*{\qedhere}
+ \end{equation*}
+\end{proof}
+\end{verbatim}
+\end{quote}
+The \cmdinvoke{tag*}{\csx{qedhere}} construction may be used in any of
+\AMSLaTeX{}'s numbering environments.
+\begin{ctanrefs}
+\item[amsthm.sty]Distributed as part of the \AMSLaTeX{} bundle
+ \CTANref{amslatex}[amsthm]
+\item[ntheorem.sty]\CTANref{ntheorem}
+\end{ctanrefs}
+\LastEdit{2011-03-09}
+
+\Question[Q-theoremfmt]{Theorem bodies printed in a roman font}
+
+If you want to take advantage of the powerful \csx{newtheorem} command
+without the constraint that the contents of the theorem is in a sloped
+font (for example, you may want to use it to create remarks, examples, proofs,
+\dots{}) then you can use the \AMSLaTeX{} \Package{amsthm} package
+(which now supersedes the \Package{theorem} package previously
+recommended in these answers).
+Alternatively, the following sets up an environment
+\environment{remark} whose content is in the default roman font.
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\newtheorem{preremark}{Remark}
+\newenvironment{remark}%
+ {\begin{preremark}\upshape}%
+ {\end{preremark}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\newtheorem{preremark}{Remark}
+\newenvironment{remark}%
+ {\begin{preremark}\upshape}{\end{preremark}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+The \Package{ntheorem} package provides control of the fonts used by
+theorems, directly.
+\begin{ctanrefs}
+\item[amsthm.sty]Distributed as part of \CTANref{amslatex}[amsthm]
+\item[ntheorem.sty]\CTANref{ntheorem}
+\item[theorem.sty]Distributed as part of \CTANref{2etools}[theorem]
+\end{ctanrefs}
+
+\Question[Q-newfunction]{Defining a new log-like function in \LaTeX{}}
+
+Use the \csx{mathop} command, as in:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\diag}{\mathop{\mathrm{diag}}}
+\end{verbatim}
+\end{quote}
+
+Subscripts and superscripts on \csx{diag} will be placed below and
+above the function name, as they are on
+\csx{lim}. If you want your subscripts and superscripts always placed
+to the right, do:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\newcommand{\diag}%
+ {\mathop{\mathrm{diag}}\nolimits}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand{\diag}{\mathop{\mathrm{diag}}\nolimits}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+
+\AMSLaTeX{} (in its \Package{amsopn} package, which is automatically
+loaded by \Package{amsmath}) provides a command
+\csx{DeclareMathOperator} that takes does the same job as the first
+definition above. To create our original \csx{diag} command, one would
+say:
+\begin{quote}
+\begin{verbatim}
+\DeclareMathOperator{\diag}{diag}
+\end{verbatim}
+\end{quote}
+\csx{DeclareMathOperator*} declares the operator always to have its
+sub- and superscripts in the % ! line break
+``\Qref*{\csx{limits} position}{Q-limits}''.
+
+The \Package{amsopn} command \csx{operatorname} allows you to
+introduce \emph{ad hoc} operators into your mathematics, so
+\begin{quote}
+ \csx{[} \cmdinvoke{operatorname}{foo}\texttt{(bar)} \csx{]}
+\end{quote}
+typesets the same as
+\begin{quote}
+\begin{verbatim}
+\DeclareMathOperator{\foo}{foo}
+...
+\[ \foo(bar) \]
+\end{verbatim}
+\end{quote}
+As with \csx{DeclareMathOperator} there's a starred version
+\csx{operatorname*} for sub- and superscripts in the limits position.
+
+(It should be noted that ``log-like'' was reportedly a \emph{joke} on
+Lamport's part; it is of course clear what was meant.)
+\begin{ctanrefs}
+\item[amsopn.sty]Distributed as part of the \AMSLaTeX{} distribution
+ \CTANref{amslatex}[amsopn]
+\end{ctanrefs}
+
+\Question[Q-braket]{Set specifications and Dirac brackets}
+
+One of the few glaring omissions from \TeX{}'s mathematical
+typesetting capabilities is a means of setting separators in the
+middle of mathematical expressions. \TeX{} provides primitives called
+\csx{left} and \csx{right}, which can be used to modify brackets (of
+whatever sort) around a mathematical expression, as in:
+% beware line wrap
+\csx{left(}\texttt{ <expression> }\csx{right)}~--- the size of the
+parentheses is matched to the vertical extent of the expression.
+
+However, in all sorts of mathematical enterprises one may find oneself
+needing a \csx{middle} command, to be used in expressions like
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\left\{ x \in \mathbb{N} \middle| x \mbox{ even} \right\}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\left\{ x\in \mathbb{N} \middle|
+ x \mbox{ even} \right\}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+to specify the set of even natural numbers. The % ! line break
+\Qref*{\eTeX{} system}{Q-etex}
+defines just such a command, but users of Knuth's original need some
+support. Donald Arseneau's \Package{braket} package provides commands
+for set specifications (as above) and for Dirac brackets (and bras and
+kets). The package uses the \eTeX{} built-in command if it finds
+itself running under \eTeX{}.
+\begin{ctanrefs}
+\item[braket.sty]\CTANref{braket}
+\end{ctanrefs}
+
+\Question[Q-cancellation]{Cancelling terms in maths expressions}
+
+A technique used when explaining the behaviour of expressions or
+equations (often for pedagogical purposes). The \Package{cancel}
+package provides several variants of cancellation marks
+(``\texttt{\textbackslash }'', ``\texttt{/}'' and ``\texttt{X}''), and
+a means of cancelling `to' a particular value.
+
+Documentation of \Package{cancel} is in the package file.
+\begin{ctanrefs}
+\item[cancel.sty]\CTANref{cancel}
+\end{ctanrefs}
+
+\Question[Q-mathsize]{Adjusting maths font sizes}
+
+In \plaintex{}, when you introduce a new font size you must also
+declare what size fonts are to be used in mathematics with it. This
+is done by declaring \csx{textfont}, \csx{scriptfont} and
+\csx{scriptscriptfont} for the maths families you're using; all such
+things are described in chapter~17 of the % line wrap!
+\Qref*{\TeX{}book}{Q-tex-books} and in other books and
+\Qref*{tutorials}{Q-man-tex} that discuss \plaintex{} in sufficient
+detail.
+
+In \LaTeX{}, of course, all this stuff is automated: there is a scheme
+that, for each (text) font size, determines what maths font sizes are
+to be used. The scheme first checks a set of ``known'' text sizes,
+for each of which maths sizes are declared in advance. If the text
+size isn't ``known'', the script- and scriptscriptfont sizes are
+calculated as fixed ratios of the tex font size. (The values used are
+\csx{defaultscriptratio}\ensuremath{=}0.7, and
+\csx{defaultscriptscriptratio}\ensuremath{=}0.5.)
+
+The fixed-ratio formula is capable of producing inconvenient results
+(particularly if you are using fonts which \LaTeX{} believes are only
+available in a fixed set of sizes). You may also want to replace
+\LaTeX{}'s ideas altogether, for example by setting maths noticeably
+larger or smaller than its surrounding text. For this purpose, the
+\LaTeX{} command
+\cmdinvoke{DeclareMathSizes}{\meta{tfs}}{\meta{ts}}{\meta{ss}}{\meta{sss}}
+may be used (this is the same command that \LaTeX{} itself uses to
+define its own set of sizes). This establishes (or re-establishes)
+the maths font sizes to be used when the surrounding text font size is
+\texttt{\meta{tfs}}; (\texttt{\meta{ts}} being the size used for
+\csx{textfont}, \texttt{\meta{ss}} for \csx{scriptfont} and
+\texttt{\meta{sss}} for \csx{scriptscriptfont}).
+
+For example, you might want to use a font with a smaller body height
+than Computer Modern, but still prefer \acro{CM} math to any of the
+alternatives. In this case, you might use:
+\begin{quote}
+\begin{verbatim}
+\DeclareMathSizes{10}{9}{7}{5}
+\end{verbatim}
+\end{quote}
+to get 9pt maths when the surrounding body text is (nominal) 10pt.
+
+\csx{DeclareMathSizes} may only be used in the preamble of the
+document: only one association is available for each text font size
+for the whole document. The default settings are specified in
+\File{fontdef.dtx} in the latex distribution, and are compiled into
+\File{fontmath.ltx}; the arguments to the command are just numbers
+(`\texttt{pt}' is assumed), but some of them are written using
+\Qref*{\LaTeX{} abbreviations}{Q-ltxabbrv} for standard font sizes.
+Beware simply copying (parts of) the \LaTeX{} definitions~--- since
+they contain those internal abbreviations, they need to be treated as
+\Qref{internal commands}{Q-atsigns}.
+\begin{ctanrefs}
+\item[fontdef.dtx]\CTANref{fontdef}
+\item[fontmath.ltx]\CTANref{fontmath}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-mathlips]{Ellipses}
+\keywords{\csx{dots} \csx{cdots} \csx{vdots} \csx{ddots}}
+
+Ellipses are commonly required, and \LaTeX{} natively supplies a fair
+range (\csx{dots}, \csx{cdots}, \csx{vdots} and \csx{ddots}). By using
+the \Package{graphics} package, one can change the slope of the
+\csx{ddots} command, as in
+\begin{quote}
+\begin{verbatim}
+$ ... \reflectbox{$\ddots$} ... $
+\end{verbatim}
+\end{quote}
+While this works, it is not a recommended way of achieving the desired
+result (see below). Moreover, \LaTeX{}'s range is not adequate to
+everyone's requirements, and at least three packages provide
+extensions to the set.
+
+The \AMSLaTeX{} bundle provides a range of ``semantically-named''
+ellipses, for use in different situations: \csx{dotsb} for use between
+pairs of binary operators, \csx{dotsc} for use between pairs of commas,
+and so on.
+
+The \Package{yhmath} package defines an \csx{adots} command, which is
+the analogue of \csx{ddots}, sloping forwards rather than backwards.
+The \Package{yhmath} package comes with a rather interesting font that
+extends the standard \Package{cmex}; details are in the documentation.
+
+The \Package{mathdots} package (besides fixing up the behaviour of
+\AllTeX{} \csx{ddots} and \csx{vdots} when the font size changes)
+provides an ``inverse diagonal'' ellipsis \csx{iddots} (doing the same
+job as \Package{yhmath}'s \csx{adots}, but better).
+
+Documentation of \Package{yhmath} appears, processed, in the
+distribution (thus saving you the bother of installing the package
+before being able to read the documentation). Documentation of
+\Package{mathdots} appears at the end the package file itself.
+\begin{ctanrefs}
+\item[amslatex]\CTANref{amslatex}
+\item[graphics.sty]Part of the \CTANref{graphics} bundle
+\item[mathdots.sty]\CTANref{mathdots}
+\item[yhmath]\CTANref{yhmath}
+\end{ctanrefs}
+\LastEdit{2013-08-21}
+
+\Question[Q-limits]{Sub- and superscript positioning for operators}
+
+The commonest hand-written style for expressions is to place the limit
+expressions on operators such as \csx{sum} and \csx{int} physically
+above and below the operator. In \AllTeX{}, we write these limit
+expressions using sub- and superscripts applied to the operator, but
+they don't always appear in the ``handwritten'' way in \TeX{}'s
+output.
+
+The reason is, that when an expression appears in non-display maths,
+in running text (and is therefore in \TeX{} \csx{textstyle}), placing
+the limits thus could lead to ragged line spacing (and hence
+difficult-to-read text). It is therefore common (in \csx{textstyle})
+to place the limits as one would sub- and superscripts of variables.
+
+This is not universally satisfactory, so the primitive \csx{limits} is
+provided:
+\begin{quote}
+\begin{verbatim}
+$\sum\limits_{n=1}^{m} ...$
+\end{verbatim}
+\end{quote}
+which will place the limits right above and below the symbol (and be
+blowed to the typography\dots{}).
+
+Contrariwise, you may wish to change the arrangement of the limits
+when in \csx{displaystyle}. For this purpose, there's a corresponding
+\csx{nolimits}:
+\begin{quote}
+\begin{verbatim}
+\[\sum\nolimits_{n=1}^{m} ...\]
+\end{verbatim}
+\end{quote}
+which will place the limits as they would be in \csx{textstyle}.
+
+Alternatively, one can manipulate the
+\csx{textstyle}/\csx{displaystyle} state of the mathematics. To get
+``\csx{limits} placement'' in inline maths,
+\begin{quote}
+\begin{verbatim}
+$\displaystyle\sum_{n=1}^{m} ...$
+\end{verbatim}
+\end{quote}
+and for ``\csx{nolimits} placement'' in display maths,
+\csx{nolimits}:
+\begin{quote}
+\begin{verbatim}
+\[\textstyle\sum_{n=1}^{m} ...\]
+\end{verbatim}
+\end{quote}
+will serve. Either of these forms may have effects other than on the
+operator you're considering, but there are still those who prefer this
+formulation.
+
+Remember, if you're % ! line break
+\Qref*{declaring a special operator of your own}{Q-newfunction}, the
+\AMSLaTeX{} functions (that you ought to be using) allow you to choose
+how limits are displayed, at definition time.
+
+(Note that the macro \csx{int} normally has \csx{nolimits} built in to
+its definition. There is an example in the \TeX{}book to show how odd
+\csx{int}\csx{limits} looks when typeset.)
+
+\Question[Q-mathstext]{Text inside maths}
+
+When we type maths in \AllTeX{}, the letters from which we make up
+ordinary text assume a special significance: they all become
+single-letter variable names. The letters appear in italics, but it's
+not the same sort of italics that you see when you're typing ordinary
+text: a run of maths letters (for example ``here'') looks oddly
+``lumpy'' when compared with the word written in italic text. The
+difference is that the italic text is kerned to make the letters fit
+well together, whereas the maths is set to look as if you're
+multiplying \emph{h} by \emph{e} by \emph{r} by \emph{e}. The other
+way things are odd in \TeX{} maths typing is that spaces are ignored:
+at best we can write single words in this oddly lumpy font.
+
+So, if we're going to have good-looking text in amongst maths we're
+writing, we have to take special precautions. If you're using
+\LaTeX{}, the following should help.
+
+The simplest is to use \csx{mbox} or \csx{textrm}:
+\begin{quote}
+\begin{verbatim}
+$e = mc^2 \mbox{here we go again}$
+\end{verbatim}
+\end{quote}
+The problem is that, with either, the size of the text remains firmly
+at the surrounding text size, so that
+\begin{quote}
+\begin{verbatim}
+$z = a_{\mbox{other end}}$
+\end{verbatim}
+\end{quote}
+can look quite painfully wrong.
+
+The other simple technique, \csx{textrm}, is no more promising:
+\begin{quote}
+\begin{verbatim}
+$z = a_{\textrm{other end}}$
+\end{verbatim}
+\end{quote}
+does the same as \csx{mbox}, by default.
+
+(The maths-mode instance of your roman font (\csx{mathrm}) gets the
+size right, but since it's intended for use in maths, its spaces get
+ignored~--- use \csx{mathrm} for upright roman alphabetic variable
+names, but not otherwise.)
+
+You can correct these problems with size selectors in the text, as:
+\begin{quote}
+\begin{verbatim}
+$z = a_{\mbox{\scriptsize other end}}$
+\end{verbatim}
+\end{quote}
+which works if your surrounding text is at default document size, but
+gives you the wrong size otherwise.
+
+The \csx{mbox} short cut is (just about) \acro{OK} for ``occasional''
+use, but serious mathematics calls for a technique that
+relieves the typist of the sort of thought required. As usual, the
+\AMSLaTeX{} system provides what's necessary~--- the \csx{text}
+command. (The command is actually provided by the \Package{amstext}
+package, but the ``global'' \Package{amsmath} package loads it.) Thus
+anyone using \AMSLaTeX{} proper has the command available, so even
+this author can write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{amsmath}
+...
+$z = a_{\text{other end}}$
+\end{verbatim}
+\end{quote}
+and the text will be at the right size, and in the same font as
+surrounding text. (The \Package{amstext} package also puts
+\csx{textrm} to rights~--- but \csx{text} is easier to type than
+\csx{textrm}!)
+
+\AMSLaTeX{} also makes provision for interpolated comments in the
+middle of one of its multi-line display structures, through the
+\csx{intertext} command. For example:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{align}
+ A_1&=N_0(\lambda;\Omega')-
+ \phi(\lambda;\Omega'),\\
+ A_2&=\phi(\lambda;\Omega')-
+ \phi(\lambda;\Omega),\\
+\intertext{and}
+ A_3&=\mathcal{N}(\lambda;\omega).
+\end{align}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\begin{align}
+ A_1&=N_0(\lambda;\Omega')-\phi(\lambda;\Omega'),\\
+ A_2&=\phi(\lambda;\Omega')-\phi(\lambda;\Omega),\\
+ \intertext{and} A_3&=\mathcal{N}(\lambda;\omega).
+\end{align}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+places the text ``and'' on a separate line before the last line of the
+display. If the interjected text is short, or the equations
+themselves are light-weight, you may find that \csx{intertext} leaves
+too much space. Slightly more modest is the \csx{shortintertext}
+command from the \Package{mathtools} package:
+\begin{quote}
+\begin{verbatim}
+\begin{align}
+ a =& b
+ \shortintertext{or}
+ c =& b
+\end{align}
+\end{verbatim}
+\end{quote}
+To have the text on the same line as the second equation, one can use
+the \environment{flalign} environment (from \Package{amsmath})
+with lots of dummy equations (represented by the double \texttt{\&}
+signs):
+\begin{quote}
+\begin{verbatim}
+\begin{flalign}
+ && a =& b && \\
+ \text{or} && c =& b &&
+\end{flalign}
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+ \CTANref{amslatex}[amsmath]
+\item[amstext.sty]Distributed as part of \AMSLaTeX{}
+ \CTANref{amslatex}[amstext]
+\item[mathtools.sty]Distributed as part of the \Package{mh} bundle
+ \CTANref{mh}[mathtools]
+\end{ctanrefs}
+
+\Question[Q-reuseq]{Re-using an equation}
+
+To repeat an existing equation, one wants not only to have the same
+mathematics in it, one also wants to re-use the original label it had.
+The \Package{amsmath} package comes to our help, here:
+\begin{quote}
+\begin{verbatim}
+\usepackage{amsmath}
+...
+\begin{equation}
+ a=b
+ \label{eq1}
+\end{equation}
+...
+Remember that
+\begin{equation}
+ a=b
+ \tag{\ref{eq1}}
+\end{equation}
+\end{verbatim}
+\end{quote}
+Here, the second instance of \ensuremath{a=b} will be
+typeset with a copy, made by the \csx{tag} command, of the label of the
+first instance.
+\begin{ctanrefs}
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+ \CTANref{amslatex}[amsmath]
+\end{ctanrefs}
+
+\Question[Q-brkinline]{Line-breaking in in-line maths}
+
+\TeX{}, by default, allows you to split a mathematical expression at
+the end of the line; it allows breaks at relational operators (like
+``='', ``\textless'', etc.) and at binary operators (like ``+'',
+``-'', etc.). In the case of large expressions, this can sometimes be
+a life-saver.
+
+However, in the case of simple expressions like \ensuremath{a=b+c}, a
+break can be really disturbing to the reader, and one would like to
+avoid it.
+
+Fortunately, these breaks are controllable: there are ``penalties''
+associated with each type of operator: the penalty
+ says how
+undesirable a break at each point is. Default values are:
+\begin{quote}
+\begin{verbatim}
+\relpenalty = 500
+\binoppenalty = 700
+\end{verbatim}
+\end{quote}
+You make the break progressively less attractive by increasing these
+values. You can actually forbid all breaks, everywhere, by:
+\begin{quote}
+\begin{verbatim}
+\relpenalty = 10000
+\binoppenalty = 10000
+\end{verbatim}
+\end{quote}
+If you want just to prevent breaks in a single expression, write:
+\begin{quote}
+\begin{verbatim}
+{%
+ \relpenalty = 10000
+ \binoppenalty = 10000
+ $a=b+c$
+}
+\end{verbatim}
+\end{quote}
+and the original values will remain undisturbed outside the braces.
+This is tedious: there is often value in an alternative approach,
+in which you say which parts of the expression may not break whatever
+happens, and fortunately this is surprisingly easy. Suppose we want
+to defer a break until after the equality, we could write:
+\begin{quote}
+\begin{verbatim}
+${a+b+c+d} = z+y+x+w$
+\end{verbatim}
+\end{quote}
+The braces say ``treat this subformula as one atom'' and (in \TeX{} at
+least) atoms don't get split: not a \csx{binoppenalty} change in sight.
+
+\Question[Q-mathonlyref]{Numbers for referenced equations only}
+
+There are those who consider that papers look untidy with numbers on
+every equation; there is also a school of thought that claims that
+there should be numbers everywhere, in case some reader wants to make
+reference an equation to which the author made no cross-reference.
+
+If you hold to the ``only cross-referenced'' school of thought, you
+can (using the \csx{nonumber} command on the relevant equations, or by
+using the \AMSLaTeX{} unnumbered environments such as
+\environment{equation*}) mark those of your equations to which you
+make no reference. In a long or complex paper, this procedure could
+well become deeply tedious.
+
+Fortunately, help is at hand: the \Package{mh} bundle's
+\Package{mathtools} package offers a `\pkgoption{showonlyrefs}'
+switch through its \csx{mathtoolsset} command; when that's in
+operation, only those equations to which you make reference will be
+numbered in the final output. See the package's documentation for
+details of how to make references when the switch is in effect.
+\begin{ctanrefs}
+\item[mathtools.sty]Distributed as part of \CTANref{mh}[mathtools]
+\end{ctanrefs}
+
+\Question[Q-subheight]{Even subscript height}
+
+Other things being equal, \TeX{} will aim to position subscripts and
+superscripts in places that ``look good''. Unfortunately, it only
+does this for the sub- and superscripts of each atom at a time, so if
+you have
+\begin{quote}
+\begin{verbatim}
+$ X^{1}_{2} X_{2} $
+\end{verbatim}
+\end{quote}
+the second subscript will appear higher, since the first has moved
+down to avoid the superscript;
+the effect can be noticeably distracting:
+\begin{quote}
+\begin{typesetversion}
+ $ X^{1}_{2} X_{2} $
+\end{typesetversion}
+\begin{htmlversion}
+ \includegraphics{faq-images1.png}
+\end{htmlversion}
+\end{quote}
+
+You can avoid the problem, for a single instance, by
+\begin{quote}
+\begin{verbatim}
+$ X^{1}_{2} X^{}_{2} $
+\end{verbatim}
+\end{quote}
+here, the dummy superscript has the requisite ``pushing down'' effect:
+\begin{quote}
+\begin{typesetversion}
+ $ X^{1}_{2} X^{}_{2} $
+\end{typesetversion}
+\begin{htmlversion}
+ \includegraphics{faq-images2.png}
+\end{htmlversion}
+\end{quote}
+
+While this technique does what is necessary, it is tedious and
+potentially error-prone. So, for more than one or two equations
+in a document, the \LaTeX{} user is advised to use the
+\Package{subdepth} package, which forces the lower position for all
+subscripts.
+\begin{ctanrefs}
+\item[subdepth.sty]\CTANref{subdepth}
+\end{ctanrefs}
+
+\subsection{Lists}
+
+\Question[Q-enumerate]{Fancy enumeration lists}
+
+The \Package{enumerate} package allows you to control the display of
+the enumeration counter. The package adds an optional parameter to
+the \environment{enumerate} environment, which is used to specify the
+layout of the labels. The layout parameter contains an enumeration
+type (`\texttt{1}' for arabic numerals, `\texttt{a}' or `\texttt{A}'
+for alphabetic enumeration, and `\texttt{i}' or `\texttt{I}' for Roman
+numerals), and things to act as decoration of the enumeration. So,
+for example
+\begin{quote}
+\begin{verbatim}
+\usepackage{enumerate}
+...
+\begin{enumerate}[(a)]
+\item ... ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+starts a list whose labels run (a), (b), (c), \dots{}; while
+\begin{quote}
+\begin{verbatim}
+\usepackage{enumerate}
+...
+\begin{enumerate}[I/]
+\item ... ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+starts a list whose labels run I/, II/, III/, \dots{}
+
+The \Package{paralist} package, whose primary purpose is % beware line break
+\Qref*{compaction of lists}{Q-complist}, provides the same facilities
+for its \environment{enumerate}-like environments.
+
+If you need non-stereotyped designs, the \Package{enumitem} package
+gives you most of the flexibility you might want to design your own.
+The silly roman example above could be achieved by:
+\begin{quote}
+\begin{verbatim}
+\usepackage{enumitem}
+...
+\begin{enumerate}[label=\Roman{*}/]
+\item ... ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+Note that the `\texttt{*}' in the key value stands for the list
+counter at this level. You can also manipulate the format of
+references to list item labels:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\usepackage{enumitem}
+...
+\begin{enumerate}[label=\Roman{*}/,
+ ref=(\roman{*})]
+\item ... ...
+\end{enumerate}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\usepackage{enumitem}
+...
+\begin{enumerate}[label=\Roman{*}/, ref=(\roman{*})]
+\item ... ...
+\end{enumerate}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+to make references to the list items format appear as (i), (ii),
+(iii), etc.
+
+The \Class{memoir} class includes functions that match those in the
+\Package{enumerate} package, and has similar functionality for
+\environment{itemize} lists.
+%% It is possible (if not particularly convenient) to do the same thing
+%% yourself. Suppose you want your top-level \environment{enumerate}s to
+%% be labelled I/, II/, III/, \dots{}, then give these commands:
+%% \begin{verbatim}
+%% \renewcommand{\theenumi}{\Roman{enumi}}
+%% \renewcommand{\labelenumi}{\theenumi/}
+%% \end{verbatim}
+%% The possible styles of numbering are given in Section~6.3 of Lamport's
+%% book (see \Qref[question]{\TeX{}-related books}{Q-book-lists}). Both
+%% \csx{theenumi} and \csx{labelenumi} must be changed, since
+%% \csx{theenumi} is used in cross-references to the list.
+%%
+%% For lower level \environment{enumerate}s, replace |enumi| by |enumii|,
+%% |enumiii| or |enumiv|, according to the level. If your label is much
+%% larger than the default, you should also change \csx{leftmargini},
+%% \csx{leftmarginii}, \emph{etc}.
+\begin{ctanrefs}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate]
+\item[enumitem.sty]\CTANref{enumitem}
+\item[memoir.cls]\CTANref{memoir}
+\item[paralist.sty]\CTANref{paralist}
+\end{ctanrefs}
+
+\Question[Q-complist]{How to adjust list spacing}
+
+\Qref*{Lamport's book}{Q-latex-books} lists various
+parameters for the layout of list (things like \csx{topsep},
+\csx{itemsep} and \csx{parsep}), but fails to mention that they're set
+automatically within the standard (\latex{}-defined) lists. This
+happens because each list
+executes a command \csx{@list}\texttt{\meta{depth}} (the depth
+appearing as a lower-case roman numeral); what's more, the top-level
+\csx{@listi} is usually reset when the font size is changed. As a
+result, it's rather tricky for
+the user to control list spacing. Of course, the real answer is to use
+a document class designed with more modest list spacing, but we all
+know such things are hard to come by. The \Class{memoir} class doesn't
+provide more compact lists, but offers the user control over the list
+spacing using \csx{firmlist} and \csx{tightlist} (and \texttt{*}-ed
+versions of them); see section~8.6 of the memoir manual.
+
+There are packages that provide some control of list spacing, but they
+seldom address the separation from surrounding text (defined by
+\csx{topsep}). The \Package{expdlist} package, among its many controls
+of the appearance of \environment{description} lists, offers a
+compaction parameter (see the documentation); the \Package{mdwlist}
+package offers a \csx{makecompactlist} command for users' own list
+definitions, and uses it to define compact lists
+\environment{itemize*}, \environment{enumerate*} and
+\environment{description*}. In fact, you can write lists such as
+these commands define pretty straightforwardly~--- for example:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{itemize*}%
+ {\begin{itemize}%
+ \setlength{\itemsep}{0pt}%
+ \setlength{\parskip}{0pt}}%
+ {\end{itemize}}
+\end{verbatim}
+\end{quote}
+The \Package{paralist} package provides several approaches to list
+compaction:
+\begin{itemize}
+\item its \environment{asparaenum} environment formats each item as if
+ it were a paragraph introduced by the enumeration label (which saves
+ space if the item texts are long);
+\item its \environment{compactenum} environment is the same sort of
+ compact list as is provided in \Package{expdlist} and
+ \Package{mdwlist}; and
+\item its \environment{inparaenum} environment produces a list ``in
+ the paragraph'', i.e., with no line break between items, which is a
+ great space-saver if the list item texts are short.
+\end{itemize}
+The package will manipulate its \environment{enumerate} environment
+labels just like the \Qref*{\Package{enumerate} package}{Q-enumerate}
+does.
+
+\Package{Paralist} also provides \environment{itemize} equivalents
+(\environment{asparaitem}, etc.), and \environment{description}
+equivalents (\environment{asparadesc}, etc.).
+
+The \Package{multenum} package offers a more regular form of
+\Package{paralist}'s \environment{inparaenum}; you define a notional
+grid on which list entries are to appear, and list items will always
+appear at positions on that grid. The effect is somewhat like that of
+the `tab' keys on traditional typewriters; the package was designed
+for example sheets, or lists of answers in the appendices of a book.
+
+The \Package{expdlist}, \Package{mdwlist} and \Package{paralist}
+packages all offer other facilities for list configuration: you should
+probably not try the ``do-it-yourself'' approaches outlined below if
+you need one of the packages for some other list configuration
+purpose.
+
+For ultimate flexibility (including manipulation of \csx{topsep}), the
+\Package{enumitem} package permits adjustment of list parameters using
+a ``\emph{key}\latexhtml{\ensuremath{=}}{=}\meta{value}'' format.
+For example, one might write
+\begin{quote}
+\begin{verbatim}
+\usepackage{enumitem}
+...
+\begin{enumerate}[topsep=0pt, partopsep=0pt]
+\item ...
+\item ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+to suppress all spacing above and below your list, or
+\begin{quote}
+\begin{verbatim}
+\usepackage{enumitem}
+...
+\begin{enumerate}[itemsep=2pt,parsep=2pt]
+\item ...
+\item ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+to set spacing between items and between paragraphs within items.
+\Package{Enumitem} also permits manipulation of the label format in a
+more ``basic'' (and therefore more flexible) manner than the % ! line break
+\Qref*{\Package{enumerate} package}{Q-enumerate} does.
+
+The ultimate in compaction (of every sort) is offered by the
+\Package{savetrees} package; compaction of lists is included. The
+package's prime purpose is to save space at every touch and turn:
+don't use it if you're under any design constraint whatever!
+\begin{ctanrefs}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumitem]
+\item[enumitem.sty]\CTANref{enumitem}
+\item[expdlist.sty]\CTANref{expdlist}
+\item[memoir.cls]\CTANref{memoir}
+\item[memoir \nothtml{\rmfamily}manual]\CTANref{memoir-man}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
+\item[multenum.sty]\CTANref{multenum}
+\item[paralist.sty]\CTANref{paralist}
+\item[savetrees.sty]\CTANref{savetrees}
+\end{ctanrefs}
+\LastEdit{2012-10-30}
+
+\Question[Q-interruptlist]{Interrupting enumerated lists}
+
+It's often convenient to have commentary text, `outside' the list,
+between successive entries of a list. In the case of
+\environment{itemize} lists this is no problem, since there's never
+anything to distinguish successive items, while in the case of
+\environment{description} lists, the item labels are under the user's
+control so there's no automatic issue of continuity.
+
+For \environment{enumerate} lists, the labels are generated
+automatically, and are context-sensitive, so the context (in this
+case, the state of the enumeration counter) needs to be preserved.
+
+The belt-and-braces approach is to remember the state of the
+enumeration in your own counter variable, and then restore it when
+restarting enumerate:
+\begin{quote}
+\begin{verbatim}
+\newcounter{saveenum}
+ ...
+\begin{enumerate}
+ ...
+ \setcounter{saveenum}{\value{enumi}}
+\end{enumerate}
+<Commentary text>
+\begin{enumerate}
+ \setcounter{enumi}{\value{saveenum}}
+ ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+
+This is reasonable, in small doses\dots{} Problems (apart from sheer
+verbosity) are getting the level right (``should I use counter
+\texttt{enumi}, \texttt{enumii}, \dots{}'') and remembering not to
+nest the interruptions (i.e., not to have a separate list, that is
+itself interrupted) in the ``commentary text'').
+
+The \Package{mdwlist} package defines commands \csx{suspend} and
+\csx{resume} that simplify the process:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}
+ ...
+\suspend{enumerate}
+<Commentary text>
+\resume{enumerate}
+ ...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+The package allows an optional name (as in
+\cmdinvoke{suspend}[id]{enumerate}) to allow you to identify a
+particular suspension, and hence provide a handle for manipulating
+nested suspensions.
+
+If you're suspending a \Qref*{fancy-enumeration list}{Q-enumerate},
+you need to
+re-supply the optional ``item label layout'' parameters required by
+the \Package{enumerate} package when resuming the list, whether by the
+belt-and-braces approach, or by the \Package{mdwlist}
+\cmdinvoke{resume}{enumerate} technique. The task is a little tedious
+in the \Package{mdwlist} case, since the optional argument has to be
+encapsulated, whole, inside an optional argument to \csx{resume},
+which requires use of extra braces:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}[\textbf{Item} i]
+ ...
+\suspend{enumerate}
+<comment>
+\resume{enumerate}[{[\textbf{Item} i]}]
+...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+\nothtml{\noindent}The \Package{enumitem} package, in its most recent
+release, will also allow you to resume lists:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}
+...
+\end{enumerate}
+<comment>
+\begin{enumerate}[resume]
+...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+which feels just as ``natural'' as the \Package{mdwtools} facility,
+and has the advantage of playing well with the other excellent
+facilities of \Package{enumitem}.
+
+\Package{Expdlist} has a neat way of providing for comments, with its
+\csx{listpart} command. The command's argument becomes a comment
+between items of the list:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}
+\item item 1
+\item item 2
+ \listpart{interpolated comment}
+\item item 3
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+This, you will realise, means it doesn't even have to think about
+suspending or resuming the list, and of course it works equally well
+in any of the list environments (thought it's not actually
+\emph{necessary} for any but \environment{enumerate}).
+
+\Package{Enumitem} also allows multi-level suspension and resumption
+of lists:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}
+\item outer item 1
+\end{enumerate}
+<comment>
+\begin{enumerate}[resume]
+\item outer item 2
+% nested enumerate
+\begin{enumerate}
+\item inner item 1
+\end{enumerate}
+<nested comment>
+% resume nested enumerate
+\begin{enumerate}[resume]
+\item inner item 2
+\end{enumerate}
+\item outer item 3
+% end outer enumerate
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+However, the `nested comment' interpolated in the nested enumeration
+appears as if it were a second paragraph to ``outer item 2'', which is
+hardly satisfactory.
+\begin{ctanrefs}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate]
+\item[enumitem.sty]\CTANref{enumitem}
+\item[expdlist.sty]\CTANref{expdlist}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
+\end{ctanrefs}
+
+\subsection{Tables, figures and diagrams}
+
+\Question[Q-destable]{The design of tables}
+
+In recent years, several authors have argued that the examples, set
+out by Lamport in his \Qref*{\LaTeX{} manual}{Q-latex-books}, have cramped
+authors' style and have led to extremely poor table design. It is in
+fact difficult even to work out what many of the examples in Lamport's
+book ``mean''.
+
+The criticism focuses on the excessive use of rules (both horizontal
+and vertical) and on the poor vertical spacing that Lamport's macros
+offer.
+
+The problem of vertical spacing is plain for all to see, and is
+addressed in several packages~--- see % beware line breaks
+``\Qref*[question]{spacing of lines in tables}{Q-struttab}''.
+
+The argument about rules is presented in the excellent essay that
+prefaces the documentation of Simon Fear's \Package{booktabs} package,
+which (of course) implements Fear's scheme for `comfortable' rules.
+(The same rule commands are implemented in the \Class{memoir} class.)
+
+Lamport's \LaTeX{} was also inflexibly wrong in ``insisting'' that
+captions should come at the bottom of a table. Since a table may
+extend over several pages, traditional typography places the caption
+at the top of a table float. The \csx{caption} command will get its
+position wrong (by \texttt{10pt}) if you simply write:
+\begin{quote}
+\begin{verbatim}
+\begin{table}
+ \caption{Example table}
+ \begin{tabular}{...}
+ ...
+ \end{tabular}
+\end{table}
+\end{verbatim}
+\end{quote}
+The \Package{topcapt} package solves this problem:
+\begin{quote}
+\begin{verbatim}
+\usepackage{topcapt}
+...
+\begin{table}
+ \topcaption{Example table}
+ \begin{tabular}{...}
+ ...
+ \end{tabular}
+\end{table}
+\end{verbatim}
+\end{quote}
+The \Class{KOMA-script} classes provide a similar command
+\csx{captionabove}; they also have a class option
+\pkgoption{tablecaptionabove} which arranges that \csx{caption}
+\emph{means} \csx{captionabove}, in table environments. The
+\Package{caption} package may be loaded
+with an option that has the same effect:
+\begin{quote}
+\begin{verbatim}
+\usepackage[tableposition=top]{caption}
+\end{verbatim}
+\end{quote}
+or the effect may be established after the package has been loaded:
+\begin{quote}
+\begin{verbatim}
+\usepackage{caption}
+\captionsetup[table]{position=above}
+\end{verbatim}
+\end{quote}
+(Note that the two ``position'' options are different: actually,
+``above'' and ``top'' in these contexts mean the same thing.)
+
+Doing the job yourself is pretty easy: \Package{topcapt} switches the
+values of the \LaTeXe{} parameters \csx{abovecaptionskip} (default
+value \texttt{10pt}) and \csx{belowcaptionskip} (default value
+\texttt{0pt}), so:
+\begin{quote}
+\begin{verbatim}
+\begin{table}
+ \setlength{\abovecaptionskip}{0pt}
+ \setlength{\belowcaptionskip}{10pt}
+ \caption{Example table}
+ \begin{tabular}{...}
+ ...
+ \end{tabular}
+\end{table}
+\end{verbatim}
+\end{quote}
+does the job (if the length values are right; the package and classes
+are more careful!).
+\begin{ctanrefs}
+\item[booktabs.sty]\CTANref{booktabs}
+\item[caption.sty]\CTANref{caption}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[topcapt.sty]\CTANref{topcapt}
+\end{ctanrefs}
+\LastEdit{2011-08-19}
+
+\Question[Q-fixwidtab]{Fixed-width tables}
+
+There are two basic techniques for making fixed-width tables in
+\LaTeX{}: you can make the gaps between the columns stretch, or you
+can stretch particular cells in the table.
+
+Basic \LaTeX{} can make the gaps stretch: the \environment{tabular*}
+environment takes an extra argument (before the \texttt{clpr} layout one)
+which takes a length specification: you can say things like ``\texttt{15cm}''
+or ``\csx{columnwidth}'' here. You must also have an \csx{extracolsep}
+command in the \texttt{clpr} layout argument, inside an \texttt{@\{\}}
+directive. So, for example, one might have
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\begin{tabular*}{\columnwidth}{@{\extracolsep{\fill}}lllr}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{tabular*}{\columnwidth}%
+ {@{\extracolsep{\fill}}lllr}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+The \csx{extracolsep} applies to all inter-column gaps to its right as
+well; if you don't want all gaps stretched, add
+\cmdinvoke{extracolsep}{0pt} to cancel the original.
+
+The \Package{tabularx} package defines an extra \texttt{clpr} column
+specification, \texttt{X}; \texttt{X} columns behave as \texttt{p}
+columns which expand to fill the space available. If there's more
+than one \texttt{X} column in a table, the spare space is distributed
+between them.
+
+The \Package{tabulary} package (by the same author) provides a way of
+``balancing'' the space taken by the columns of a table. The package
+defines column specifications \texttt{C}, \texttt{L}, \texttt{R} and
+\texttt{J}, giving, respectively, centred, left, right and
+fully-justified versions of space-sharing columns. The package
+examines how long each column would be ``naturally'' (i.e., on a piece of paper of unlimited width), and
+allocates space to each column accordingly. There are ``sanity
+checks'' so that really large entries don't cause everything else to
+collapse into nothingness (there's a ``maximum width'' that any column
+can exert), and so that tiny entries can't get smaller than a
+specified minimum. Of course, all this work means that the package
+has to typeset each row several times, so things that leave
+``side-effects'' (for example, a counter used to produce a row-number
+somewhere) are inevitably unreliable, and should not even be tried.
+
+The \Package{ltxtable} package combines the features of the
+\Package{longtable} and \Package{tabularx} packages. It's important
+to read the documentation, since usage is distinctly odd; the
+distribution contains no more than a file \File{ltxtable.tex}, which you
+should process using \LaTeX{}. Processing will give you a \File{.sty}
+file as well as the \File{.dvi} or \File{.pdf} output containing the
+documentation.
+\begin{ctanrefs}
+\item[ltxtable.sty]Distributed as part of \CTANref{carlisle}[ltxtable]
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx]
+\item[tabulary.sty]\CTANref{tabulary}
+\end{ctanrefs}
+
+\Question[Q-varwidcol]{Variable-width columns in tables}
+
+This is a slightly different take on the problem addressed in
+``\Qref*[question]{fixed-width tables}{Q-fixwidtab}''~--- here we have
+a column whose size we can't absolutely predict when we design the
+document.
+
+While the basic techniques (the \Package{tabularx}, \Package{tabulary}
+and \Package{ltxtable} packages) are the same for this problem as for the
+fixed-width \emph{table} problem, there's one extra tool that we can
+call to our aid, which may be preferable in some situations.
+
+Suppose we have data in one column which we read from an external
+source, and the source itself isn't entirely predictable. The data in
+the column may end up pretty narrow in every row of the table, or it
+may be wide enough that the table would run over the edge of the page;
+however, we don't want to make the column as wide as possible ``just
+in case'', by defining a fixed size for the table. We would like the
+column to be as small as possible, but have the possibility to spread
+to a maximum width and (if even that width is exceeded) turn into a
+\texttt{p}-style column.
+
+The \Package{varwidth} package, discussed in % ! line break
+``\Qref*[question]{automatic sizing of minipages}{Q-varwidth}'', provides
+a solution. If you load it together with the \LaTeX{} ``required''
+\Package{array} package, i.e.:
+\begin{quote}
+\begin{verbatim}
+\usepackage{array}
+\usepackage{varwidth}
+\end{verbatim}
+\end{quote}
+\Package{varwidth} defines a new column-type ``\texttt{V}'', which you
+can use as follows:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{l V{3.5cm} r}
+ foo & blah & bar \\
+ foo & blah blah & bar \\
+\end{tabular}
+\end{verbatim}
+\end{quote}
+when the second column ends up less than 3.5cm wide;
+or you can use it as follows:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{l V{3.5cm} r}
+ foo & blah & bar \\
+ foo & blah blah & bar \\
+ foo & blah blah blah blah blah blah
+ & bar \\
+\end{tabular}
+\end{verbatim}
+\end{quote}
+where the second column will end up noticeably wider, and will wrap to
+a second line in the third row.
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\item[varwidth.sty]\CTANref{varwidth}
+\end{ctanrefs}
+
+\Question[Q-struttab]{Spacing lines in tables}
+
+\AllTeX{} mechanisms for maintaining the space between lines (the
+``\emph{leading}'') rely on \TeX{}'s paragraph builder, which compares
+the shape of consecutive lines and adjusts the space between them.
+
+These mechanisms can't work in exactly the same way when \AllTeX{} is
+building a table, because the paragraph builder doesn't get to see the
+lines themselves. As a result, tables sometimes typeset with lines
+uncomfortably close together (or occasionally ridiculously far apart).
+
+Traditional (moving metal type) typographers would adjust the spacing
+between lines of a table by use of a ``\emph{strut}'' (a metal
+spacer). A \TeX{} user can do exactly the same thing: most macro
+packages define a \csx{strut} command, that defines a space appropriate
+to the current size of the text; placing a \csx{strut} command at the
+end of a troublesome row is the simplest solution to the problem~---
+if it works. Other solutions below are \LaTeX{}-specific, but some
+may be simply translated to \plaintex{} commands.
+
+If your table exhibits a systematic problem (i.e., every row is wrong
+by the same amount) use \csx{extrarowheight}, which is defined by the
+\Package{array} package:
+\begin{quote}
+\begin{verbatim}
+\usepackage{array}% in the preamble
+...
+\setlength{\extrarowheight}{length}
+\begin{tabular}{....}
+\end{verbatim}
+\end{quote}
+
+To correct a single row whose maladjustment isn't corrected by a
+\csx{strut} command, you can define your own, using
+\cmdinvoke{rule}{0pt}{length}~--- which is a near approximation to the
+command that goes inside a \csx{strut}. The \Package{bigstrut} package
+defines a strut command that you can use for this purpose:
+\csx{bigstrut} on its own opens up both above and below the current
+line; \cmdinvoke{bigstrut}[t] opens up above the line,
+\cmdinvoke{bigstrut}[b] opens up below the line.
+
+General solutions are available, however. The \Package{tabls} package
+automatically generates an appropriately-sized strut at the end of
+each row. Its disadvantages are that it's really rather slow in
+operation (since it gets in the way of everything within tables) and
+its (lack of) compatibility with other packages.
+
+The \Package{makecell} package provides a command \csx{gape} that may
+be used to apply strut expansion for a single cell of a table:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{lll}
+ ... & \gape{cell contents} & ... \\
+ ...
+\end{tabular}
+\end{verbatim}
+\end{quote}
+The package's similar \csx{Gape} command provides the same function,
+but with optional arguments that allow you to adjust the top and
+bottom adjustment.
+
+To adjust every cell in whole tables, the
+\cmdinvoke{setcellgapes}{\meta{value}} sets the adjustment value (an
+optional argument of ``\texttt{t}'' or ``\texttt{b}'' restricts
+adjustment to the top or bottom of each cell, respectively). Having
+issued \csx{setcellgapes}, the command \csx{makegapedcells} switches
+cell expansion on, and \csx{nomakegapedcells} switches it off again.
+
+The \Package{cellspace} package does a (possibly inferior) job by
+defining a new table/array column type ``S'', which you apply to each
+column specification. So, for example,
+\begin{quote}
+\cmdinvoke{begin}{tabular}{l l l p{3cm}}
+\end{quote}
+would become
+\begin{quote}
+\cmdinvoke{begin}{tabular}{Sl Sl Sl Sp{3cm}}
+\end{quote}
+and so on. This technique shows
+promise of not interfering so much with other packages, but this
+author has heard of no reports from the field.
+
+The \Package{booktabs} package comes with a thought-provoking essay
+about how tables should be designed. Since table row-spacing problems
+most often appear in collisions with rules, the author's thesis,
+that \LaTeX{} users tend too often to rule their tables, is
+interesting. The package provides rule commands to support the
+author's scheme, but deals with inter-row spacing too. The most
+recent release of \Package{booktabs} sports compatibility with
+packages such as \Package{longtable}.
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\item[bigstrut.sty]\CTANref{bigstrut}
+\item[booktabs.sty]\CTANref{booktabs}
+\item[cellspace.sty]\CTANref{cellspace}
+\item[makecell.sty]\CTANref{makecell}
+\item[tabls.sty]\CTANref{tabls}
+\end{ctanrefs}
+\LastEdit{2011-05-02}
+
+\Question[Q-longtab]{Tables longer than a single page}
+
+Tables are, by default, set entirely in boxes of their own: as a
+result, they won't split over a page boundary. Sadly, the world keeps
+turning up tables longer than a single page that we need to typeset.
+
+For simple tables (whose shape is highly regular), the simplest
+solution may well be to use the \environment{tabbing} environment,
+which is slightly tedious to set up, but which doesn't force the whole alignment
+onto a single page.
+
+The \Package{longtable} package builds the whole table (in chunks), in
+a first pass, and then uses information it has written to the \extension{aux}
+file during later passes to get the setting ``right'' (the package
+ordinarily manages to set tables in just two passes). Since the
+package has overview of the whole table at the time it's doing
+``final'' setting, the table is set ``uniformly'' over its entire
+length, with columns matching on consecutive pages.
+\Package{longtable} has a reputation for failing to interwork with
+other packages, but it does work with \Package{colortbl}, and its
+author has provided the \Package{ltxtable} package to provide (most
+of) the facilities of \Package{tabularx} (see
+% beware line wrap
+\Qref[question]{fixed-width tables}{Q-fixwidtab}) for long tables:
+beware of its rather curious usage constraints~--- each long table
+should be in a file of its own, and included by
+\cmdinvoke*{LTXtable}{width}{file}. Since \Package{longtable}'s
+multiple-page tables can't possibly live inside floats, the package
+provides for captions within the \environment{longtable} environment
+itself.
+
+A seeming alternative to \Package{ltxtable} is \Package{ltablex}; but
+it is outdated and not fully functional. Its worst problem is its
+strictly limited memory capacity (\Package{longtable} is not so
+limited, at the cost of much complication in its code);
+\Package{ltablex} can only deal with relatively small tables, it doesn't seem
+likely that support is available; but its user interface is much
+simpler than \Package{ltxtable}, so if its restrictions aren't a
+problem for you, it may be worth a try.
+
+The \Package{supertabular} package starts and stops a
+\environment{tabular} environment for each page of the table. As a
+result, each `page worth' of the table is compiled independently, and
+the widths of corresponding columns may differ on successive pages.
+However, if the correspondence doesn't matter, or if your columns are
+fixed-width, \Package{supertabular} has the great advantage of doing
+its job in a single run.
+
+Both \Package{longtable} and \Package{supertabular} allow definition
+of head- and footlines for the table; \Package{longtable} allows
+distinction of the first and last head and foot.
+
+The \Package{xtab} package fixes some infelicities of
+\Package{supertabular}, and also provides a ``last head'' facility
+(though this, of course, destroys \Package{supertabular}'s advantage
+of operating in a single run).
+
+The \Package{stabular} package provides a simple-to-use ``extension to
+\environment{tabular}'' that allows it to typeset tables that run over
+the end of a page; it also has usability extensions, but doesn't have
+the head- and footline capabilities of the major packages.
+
+Documentation of \Package{ltablex} is to be found in the package file.
+\begin{ctanrefs}
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
+\item[ltablex.sty]\CTANref{ltablex}
+\item[ltxtable.sty]Generate by running \CTANref{ltxtable}
+\item[stabular.sty]Distributed as part of \CTANref{sttools}[stabular]
+\item[supertabular.sty]\CTANref{supertabular}
+\item[xtab.sty]\CTANref{xtab}
+\end{ctanrefs}
+
+\Question[Q-tabcellalign]{How to alter the alignment of tabular cells}
+
+One often needs to alter the alignment of a tabular \texttt{p} (`paragraph')
+cell, but problems at the end of a table row are common. With a
+\texttt{p} cell that looks like:
+\begin{quote}
+\begin{verbatim}
+... & \centering blah ... \\
+\end{verbatim}
+\end{quote}
+one is liable to encounter errors that complain about a ``misplaced
+\csx{noalign}'' or ``\Qref*{extra alignment tab}{Q-altabcr}'', or the like.
+The problem is that the command \texttt{\bsbs } means different things in
+different circumstances: the \environment{tabular} environment
+switches the meaning to a value for use in the table, and
+\csx{centering}, \csx{raggedright} and \csx{raggedleft} all change the
+meaning to something incompatible. Note that the problem only
+arises in the last cell of a row: since each cell is set into a box,
+its settings are lost at the \texttt{\&} (or \texttt{\bsbs }) that
+terminates it.
+
+In the old days, the actual value of \texttt{\bsbs } that the
+\environment{tabular} environment uses was only available as an
+internal command. Nowadays, the value is a public command, and you
+can in principle use it explicitly:
+\begin{quote}
+\begin{verbatim}
+... & \centering blah ... \tabularnewline
+\end{verbatim}
+\end{quote}
+(but that's a rather verbose way of doing things).
+
+The \Package{array} package provides a command \csx{arraybackslash}
+which restores \texttt{\bsbs } to its correct (within table) meaning;
+the command may be used in \Package{array}'s ``field format'' preamble
+specifications:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{tabular}{...%
+ >{\centering\arraybackslash}%
+ p{50mm}}
+...
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\begin{tabular}{... >{\centering\arraybackslash}p{50mm}}
+...
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+
+The \csx{tabularnewline} and \csx{arraybackslash} commands are
+(somewhat) modern additions to \LaTeX{} and the \Package{array}
+package, respectively. In the unlikely event that neither is
+available, the user may try the (old) solution which preserves the
+meaning of \texttt{\bsbs }:
+\begin{quote}
+\begin{verbatim}
+\newcommand\PBS[1]{\let\temp=\\%
+ #1%
+ \let\\=\temp
+}
+\end{verbatim}
+\end{quote}
+which one uses within a table as:
+\begin{quote}
+\begin{verbatim}
+... & \PBS\centering blah ... \\
+\end{verbatim}
+\end{quote}
+or in the preamble as:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{...>{\PBS\centering}p{5cm}}
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\end{ctanrefs}
+\nothtml{\vskip 0pt plus 4ex}
+
+\Question[Q-rulethk]{The thickness of rules in \LaTeX{} tables}
+
+The rules in a \LaTeX{} table are by default \texttt{0.4pt} thick;
+this is in fact a default built in at the lowest level, and applies to
+all rules (including those separating blocks of running text).
+
+Sometimes, however, we look at a table and find we want the rules to
+stand out~--- perhaps to separate the text from the rest of the body
+text, or to make the sections of the table stand out from one another.
+However, a quick review of any \LaTeX{} manual will reveal no
+technique for making any one rule stand out, and a little
+experimentation shows that it is indeed pretty difficult to prevent
+a change ``bleeding'' out to affect other rules in the same table.
+
+If you look at what we have to say on the % ! line break
+\Qref*{design of tables}{Q-destable}, elsewhere
+among these \acro{FAQ}s, and you may sense that the design of \LaTeX{}
+simply skipped the issues surrounding table design: \emph{that's}
+presumably why there's no facilities to help you.
+
+Specifically, the length \csx{arrayrulewidth} affects the thickness of
+the rules (both horizontal and vertical) within both
+\environment{tabular} and \environment{array} environments. If you
+change from the default (see above) only as far as
+\begin{quote}
+\begin{verbatim}
+\setlength{\arrayrulewidth}{1pt}
+\end{verbatim}
+\end{quote}
+the change is remarkably striking. However, really quite subtle user
+level programming proves incapable of changing just \emph{one} rule:
+it's necessary to delve into the (rather tricky) code of \csx{hline}
+and \csx{cline} themselves.
+
+Fortunately, this job has already been done for the community: the
+\Package{booktabs} package defines three different classes of rule
+(\csx{toprule}, \csx{midrule} and \csx{bottomrule}), and the package
+documentation offers hints on how to use them. You are
+\emph{strongly} advised to read the documentation pretty carefully.
+
+The \Class{memoir} class includes the \Package{booktabs} package, and
+repeats the documentation in its compendious manual.
+
+Note that none of the above mentions the issue of the weight of
+vertical rules (except in passing). For the reasons, see the
+documentation of the \Package{booktabs} package (again); vertical
+rules in tables are in any case even more trickily coded than are
+horizontal rules, and if their lack of configurability makes them
+still less attractive, so much the better for the design of your
+document.
+\begin{ctanrefs}
+\item[booktabs.sty]\CTANref{booktabs}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-textflow]{Flowing text around figures}
+
+There are several \LaTeX{} packages that purport to do this, but they
+all have their limitations because the \TeX{} machine isn't really
+designed to solve this sort of problem. Piet van Oostrum has
+conducted a survey of the available packages; he recommends:
+\begin{description}
+\item[\texttt{floatflt}] \Package{floatflt} is an improved version
+ (for \LaTeXe{}) of \File{floatfig.sty}, and its syntax is:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\begin{floatingfigure}[options]{width of figure}
+ figure contents
+\end{floatingfigure}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+ \begin{quote}
+ \cmdinvoke{begin}{floatingfigure}[\emph{options}]{\emph{figure width}}\\
+ \mbox{}\qquad\emph{figure contents}\\
+ \cmdinvoke{end}{floatingfigure}
+ \end{quote}
+\end{narrowversion}
+There is a (more or less similar) \environment{floatingtable}
+environment.
+
+The tables or figures can be set left or right, or alternating on
+even/odd pages in a double-sided document.
+
+The package works with the \texttt{multicol} package, but doesn't work well
+in the neighbourhood of list environments (unless you change your
+\LaTeX{} document).
+\item[\texttt{wrapfig}] \Package{wrapfig} has syntax:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\begin{wrapfigure}[height of figure in lines]{l,r,...}[overhang]{width}
+ figure, caption, etc.
+\end{wrapfigure}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+ \begin{quote}
+ \cmdinvoke{begin}{wrapfigure}\texttt{\%}\\
+ \mbox{}%
+ \qquad\qquad\texttt{[\emph{figure height in lines}]\%}\\
+ \mbox{}%
+ \qquad\qquad\texttt{\{l,r,\emph{etc}\}[\emph{overhang}]\{\emph{width}\}}\\
+ \mbox{}\qquad\emph{figure, caption, etc.}\\
+ \cmdinvoke{end}{wrapfigure}
+ \end{quote}
+\end{narrowversion}
+ The syntax of the \environment{wraptable} environment is similar.
+
+ The \emph{\texttt{height}} may be omitted, in which case it will
+ be calculated from the size of the figure; the package will use
+ the greater of the specified and the
+ actual width. The \texttt{\{l,r,\emph{etc}.\}} parameter may
+ also be specified as \texttt{i}\emph{(nside)} or
+ \texttt{o}\emph{(utside)} for two-sided documents, and uppercase
+ may be used to indicate that the picture should float. The
+ overhang allows the figure to be
+ moved into the margin. The figure or table will entered into the
+ list of figures or tables if you use the \csx{caption} command.
+
+ The environments do not work within list environments that end
+ before the figure or table has finished, but can be used in a
+ parbox or minipage, and in twocolumn format.
+ \item[\texttt{picins}] \Package{Picins} is part of a large bundle
+ that allows inclusion of pictures (e.g., with shadow boxes,
+ various \MSDOS{} formats, etc.). The command for inserting a
+ picture at the start of a paragraph is:
+\begin{wideversion}
+ \begin{quote}
+ \csx{parpic}\texttt{(width,height)(x-off,y-off)[Options][Position]\{Picture\}}\\
+ \emph{Paragraph text}
+ \end{quote}
+\end{wideversion}
+\begin{narrowversion}
+ \begin{quote}
+ \cmdinvoke*{picins}(width,height)(x-off,y-off)\texttt{\%}\\
+ \mbox{\qquad\qquad}\texttt{[\emph{options}][\emph{position}]\%}\\
+ \mbox{\qquad\qquad}\texttt{\{\emph{Picture}\}}\\
+ \emph{Paragraph text}
+ \end{quote}
+\end{narrowversion}
+ All parameters except the \emph{Picture} are optional. The picture
+ can be positioned left or right, boxed with a rectangle, oval,
+ shadowbox, dashed box, and a caption can be given which will be
+ included in the list of figures.
+
+ Unfortunately (for those of us whose understanding of German is not
+ good), the documentation is in German. Piet van Oostrum has written
+ a summary in English.
+\end{description}
+All of the above deal insertions at one or other margin; they are able
+to take advantage of the \tex{} \csx{parshape} primitive that allows
+you to adjust the margins of the text of a paragraph, by line (Knuth
+provides an example of such use, with text typeset in a circle,
+half-overlapping the margin, in chapter~14 of the \tex{}book). To
+place insertions in the middle of a paragraph requires effort of an
+entirely different sort; the \Package{cutwin} package does this for
+you. It requires a set of ``part line widths'' (two per line), and
+typesets the ``cutout'' section of the paragraph line by line. The
+examples in the package documentation look enticing.
+
+\plaintex{} users only have one option: \Package{figflow} (which
+doesn't work in \LaTeX{}). \Package{Figflow} only offers flowed
+figures at the start of the paragraph, but it seems perfectly
+functional. Syntax is
+\begin{quote}
+ \cmdinvoke*{figflow}{\meta{width}}{\meta{height}}{\meta{figure}}
+\end{quote}
+(the user is responsible for having the dimensions correct, and for
+ensuring the figure fits on the page).
+\begin{ctanrefs}
+\item[cutwin.sty]\CTANref{cutwin}
+\item[figflow.tex]\CTANref{figflow}
+\item[floatflt.sty]\CTANref{floatflt}
+\item[picins.sty]\CTANref{picins}
+\item[picins \nothtml{\rmfamily}documentation summary]\CTANref{picins-summary}
+\item[wrapfig.sty]\CTANref{wrapfig}
+\end{ctanrefs}
+\LastEdit{2009-06-11}
+
+\Question[Q-slashbox]{Diagonal separation in corner cells of tables}
+\keywords{tabular}
+
+You want to label both the top or bottom row and the left- or
+rightmost column, somewhere at the corner of the table where the row
+and column meet. A simple way to achieve the result is to construct
+the table with an arrangement of rules (and possibly \csx{multicolumn}
+entries), to look like:
+\begin{quote}
+\begin{verbatim}
+-----------------
+x y
+ --------------
+ 1 2 3 4 5
+-----------------
+1
+2
+3
+4
+5
+-----------------
+\end{verbatim}
+\end{quote}
+However, this doesn't satisfy everyone: many want the labelling in a
+single cell at the top left of the table. It sounds a simple enough
+requirement, yet it calls for some slightly tricky \LaTeX{} coding.
+The \Package{diagbox} package does this job for you: it defines a
+command \csx{diagbox} whose two arguments provide the texts to be
+used; an optional argument may be used for fine tuning of the result.
+It draws a picture with the two labels on either side of a slanting
+line; the command (and hence the picture) may be placed in the corner
+cell, where the labelled row and column meet.
+
+The \Package{diagbox} package supersedes \Package{slashbox}; the older
+package's commands \csx{slashbox} and \csx{backslashbox} are provided
+in a compatible way in the newer package, to ease transition.
+\begin{ctanrefs}
+\item[diagbox.sty]\CTANref{diagbox}
+\item[slashbox.sty]\CTANref{slashbox}
+\end{ctanrefs}
+\LastEdit{2010-11-22}
+
+\Question[Q-wholerow]{How to change a whole row of a table}
+
+Each cell of a table is set in a box, so that a change of font style
+(or whatever) only lasts to the end of the cell. If one has a
+many-celled table, or a long one which needs lots of rows emphasising,
+putting a font style change command in every cell will be impossibly
+tedious.
+
+With the \Package{array} package, you can define column modifiers
+which will change the font style for a whole \emph{column}. However,
+with a bit of subtlety, one can make such modifiers affect rows rather
+than columns. So, we set things up by:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\usepackage{array}
+\newcolumntype{$}{>{%
+ \global\let\currentrowstyle\relax}%
+}
+\newcolumntype{^}{>{\currentrowstyle}}
+\newcommand{\rowstyle}[1]{%
+ \gdef\currentrowstyle{#1}%
+ #1\ignorespaces
+}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\usepackage{array}
+\newcolumntype{$}{>{\global\let\currentrowstyle\relax}}
+\newcolumntype{^}{>{\currentrowstyle}}
+\newcommand{\rowstyle}[1]{\gdef\currentrowstyle{#1}%
+ #1\ignorespaces
+}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+Now, we put `\texttt{\$}' before the first column specifier; and we
+put `\texttt{\textasciicircum }'
+before the modifiers of subsequent ones. We then use \csx{rowstyle} at
+the start of each row we want to modify:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|$l|^l|^l|} \hline
+ \rowstyle{\bfseries}
+ Heading & Big and & Bold \\ \hline
+ Meek & mild & entry \\
+ Meek & mild & entry \\
+ \rowstyle{\itshape}
+ Strange & and & italic \\
+ Meek & mild & entry \\ \hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+The \Package{array} package works with several other
+\environment{tabular}-like environments from other packages (for
+example \environment{longtable}), but unfortunately this trick won't
+always work.
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\end{ctanrefs}
+
+\Question[Q-multirow]{Merging cells in a column of a table}
+
+It's easy to come up with a table design that requires a cell that
+spans several rows. An example is something where the left-most
+column labels the rest of the table; this can be done (in simple
+cases) by using % beware line break
+\Qref*{diagonal separation in corner cells}{Q-slashbox}, but that
+technique rather strictly limits what can be used as the content of
+the cell.
+
+The \Package{multirow} package enables you to construct such multi-row
+cells, in a very simple manner. For the simplest possible use, one
+might write:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|c|c|}
+\hline
+\multirow{4}{*}{Common g text}
+ & Column g2a\\
+ & Column g2b \\
+ & Column g2c \\
+ & Column g2d \\
+\hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+and \Package{multirow} will position ``Common g text'' at the vertical
+centre of the space defined by the other rows. Note that the rows
+that don't contain the ``multi-row'' specification must have empty
+cells where the multi-row is going to appear.
+
+The ``\texttt{*}'' may be replaced by a column width specification. In this
+case, the argument may contain forced line-breaks:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|c|c|}
+\hline
+\multirow{4}{25mm}{Common\\g text}
+ & Column g2a\\
+ & Column g2b \\
+ & Column g2c \\
+ & Column g2d \\
+\hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+A similar effect (with the possibility of a little more
+sophistication) may be achieved by putting a smaller table that lines
+up the text into a \texttt{*}-declared \csx{multirow}.
+
+The \csx{multirow} command may also used to write labels vertically
+down one or other side of a table (with the help of the
+\Package{graphics} or \Package{graphicx} package, which provide the
+\csx{rotatebox} command):
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|l|l|}
+\hline
+\multirow{4}{*}{\rotatebox{90}{hi there}}
+ & Column g2a\\
+ & Column g2b \\
+ & Column g2c \\
+ & Column g2d \\
+\hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+(which gives text going upwards; use angle \texttt{-90} for text going
+downwards, of course).
+
+To make a \csx{multicolumn} multi-row ``cell'' in a table, you have to
+enclose a \csx{multirow} inside a \csx{multicolumn}~--- the other way
+around does not work, so:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\begin{tabular}{|c|c|c|}\hline
+\multicolumn{2}{|c|}{\multirow{2}{*}{combined cells}}
+ &top right\\ \cline{3-3}
+\multicolumn{2}{|c|}{}
+ &middle right\\ \hline
+bottom left
+ &bottom center
+ &bottom right\\ \hline
+\end{tabular}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{tabular}{|c|c|c|}\hline
+\multicolumn{2}{|c|}{\multirow{2}{*}%
+ {combined cells}}
+ &top right\\ \cline{3-3}
+\multicolumn{2}{|c|}{}
+ &middle right\\ \hline
+bottom left
+ &bottom center
+ &bottom right\\ \hline
+\end{tabular}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+\Package{Multirow} is set up to interact with the \Package{bigstrut}
+package (which is also discussed in the answer to % beware line break
+\Qref[question]{spacing lines in tables}{Q-struttab}). You use an
+optional argument to the \csx{multirow} command to say how many of the
+rows in the multi-row have been opened up with \csx{bigstrut}.
+
+The documentation of both \Package{multirow} and \Package{bigstrut} is
+to be found, as comments, in the package files themselves.
+\begin{ctanrefs}
+\item[bigstrut.sty]\CTANref{bigstrut}
+\item[multirow.sty]\CTANref{multirow}
+\end{ctanrefs}
+
+\subsection{Floating tables, figures, etc.}
+
+\Question[Q-floatpages]{Floats on their own on float pages}
+
+It's sometimes necessary to force a float to live on a page by itself.
+(It's sometimes even necessary for \emph{every} float to live on a
+page by itself.) When the float fails to `set', and waits for the end
+of a chapter or of the document, the natural thing to do is to declare
+the float as
+\begin{quote}
+ \cmdinvoke{begin}{figure}[p!]
+\end{quote}
+but the overriding \texttt{!} modifier has no effect on float page floats; so
+you have to make the float satisfy the parameters.
+\Qref[Question]{Moving tables and figures}{Q-floats} offers some
+suggestions, but doesn't solve the one-float-per-page question.
+
+The `obvious' solution, using the counter \texttt{totalnumber}
+(``total number of floats per page'') doesn't work:
+\texttt{totalnumber} only applies to floats on `text' pages (pages
+containing text as well as one or more float). So, to allow any
+size float to take a whole page, set \csx{floatpagefraction} really
+small, and to ensure that no more than one float occupies a page, make
+the separation between floats really big:
+\begin{quote}
+\begin{verbatim}
+\renewcommand\floatpagefraction{.001}
+\makeatletter
+\setlength\@fpsep{\textheight}
+\makeatother
+\end{verbatim}
+\end{quote}
+
+\Question[Q-wideflt]{Centring a very wide figure or table}
+
+The normal means of centring a figure or table object is to include
+\csx{centering} at the top of the float. This doesn't help if the
+object is wider than \csx{textwidth}~--- the object starts at the left
+margin and juts out into the right margin (which is actually doubly
+unsatisfactory, since as well as looking bad, the float won't be
+placed until the next \csx{clearpage} or the like.)
+
+You can avoid the problem by rescaling the figure or table to fit, but
+this is often not satisfactory, for several reasons.
+
+Otherwise, if the object is wider than the printable area of the page,
+you've no choice other than to \Qref*{rotate it}{Q-landscape}. If,
+however, the object is \emph{just} wider than the text block, you can
+make it pretend to be the right size by:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\begin{figure}
+ \noindent
+ \makebox[\textwidth]{\includegraphics{my-wide-figure}}%
+ \caption{This figure juts out into both margins}
+\end{figure}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{figure}
+ \noindent
+ \makebox[\textwidth]{%
+ \includegraphics{my-wide-figure}%
+ }%
+ \caption{This figure juts out into both margins}
+\end{figure}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+Note the \csx{noindent}: the \csx{makebox} starts a paragraph, and you
+really don't want that indented by \csx{parindent}.
+
+\Question[Q-2colfloat]{Placing two-column floats at bottom of page}
+
+You specified placement `\texttt{[htbp]}' for your full-width figure or
+table, but they always get placed at the top of the page\dots{} Well,
+it \emph{is} what the documentation says: \LaTeX{}, unadorned, only
+allows full-width floats at the top of a page, or occupying (part of) a
+float page.
+
+The \Package{stfloats} package ameliorates the situation somewhat, and
+makes \LaTeX{} honour `[b]' placement as well; the
+\Package{dblfloatfix} package combines a tidied version of the changes
+made in \Package{stfloats} with the
+\begin{narrowversion} % non-hyper
+ float ordering corrections defined in \Package{fixltx2e}
+ (\Qref{}{Q-2colfltorder}).
+\end{narrowversion}
+\begin{wideversion} % hyper
+ \Qref{float ordering corrections}{Q-2colfltorder} defined in
+ \Package{fixltx2e}.
+\end{wideversion}
+
+A particular problem with \Package{stfloats} and \Package{dblfloatfix}
+is that the float will appear, at its earliest, on the page after it
+is specified. This has two undesirable side-effects: first, there may
+be no bottom float on the first page of a document, and second, float
+numbers may become ``entangled'' (particularly if you're using
+\Package{dblfloatfix} that ensures that the early-specified bottom
+float is set \emph{before} any single column floats).
+
+(The \acro{FAQ} team doesn't know of any package that will make
+\LaTeX{} honour `[h]' placement of double-column floats, but the
+\Package{midfloat} package can be pressed into service to provide
+something approximating the effect it would have.)
+\begin{ctanrefs}
+\item[dblfloatfix.sty]\CTANref{dblfloatfix}
+\item[midfloat.sty]Distributed as part of \CTANref{sttools}[midfloat]
+\item[stfloats.sty]Distributed as part of \CTANref{sttools}[stfloats]
+\end{ctanrefs}
+
+\Question[Q-mcfloat]{Floats in multicolumn setting}
+
+If you use
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ ...
+\end{figure}
+\end{verbatim}
+\end{quote}
+in a \environment{multicols} environment, the figure won't appear. If
+instead you use
+\begin{quote}
+\begin{verbatim}
+\begin{figure*}
+ ...
+\end{figure*}
+\end{verbatim}
+\end{quote}
+the figure will stretch right across the page (just the same as a
+\environment{figure*} in standard \LaTeX{}'s \pkgoption{twocolumn} option).
+
+It's possible to have single-column figures and tables with captions,
+using the `\texttt{[H]}' placement option introduced by the \Package{float}
+package but you might have to fiddle with the placement because they
+won't `float', and exhibit other strange behaviours (such as silently
+running off the end of the column at the end of the
+\environment{multicols} environment).
+\begin{ctanrefs}
+\item[float.sty]\CTANref{float}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
+\end{ctanrefs}
+
+\Question[Q-dpfloat]{Facing floats on 2-page spread}
+
+If a pair of floats need to be forced to form a 2-page spread (in a
+book, or whatever), the first must lie on the left side of the spread,
+on an even-numbered page. The \Package{dpfloat} package provides for
+this: the construction to use is:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}[p]
+ \begin{leftfullpage}
+ <left side figure>
+ \end{leftfullpage}
+\end{figure}
+\begin{figure}[p]
+ \begin{fullpage}
+ <right side figure>
+ \end{fullpage}
+\end{figure}
+\end{verbatim}
+\end{quote}
+The construction has no effect on documents with class option
+\pkgoption{oneside} (\pkgoption{twoside} is the default for
+\Class{book} class).
+
+A special case of this requirement places the caption for a float on
+the next page. (This is useful if you have a float that ``only just''
+fits the page.) You can (with a certain amount of twiddling) make
+this work with \Package{dpfloat}, but the \Package{fltpage} package is
+specially designed for the job:
+\begin{quote}
+\begin{verbatim}
+\documentclass[twoside]{article}
+\usepackage[leftFloats]{fltpage}
+\begin{document}
+...
+\begin{FPfigure}
+ \includegraphics{my-huge-figure}
+ \caption{Whew! That was a big one!}
+\end{FPfigure}
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+That example should produce a caption
+\begin{quote}
+ Figure \meta{n} \emph{(facing page)}: Whew! \dots{}
+\end{quote}
+(Note, however, that the package is an old one, and declares itself to
+be a beta release, and contains no valid licence statement so that it
+is not in \texlive{}. It seems to work, but\dots{})
+
+A alternative route is the ``continued'' mechanism of the
+\Package{caption} package. The \csx{ContinuedFloat} macro makes a
+small tweak to the next \csx{caption} command, so that the command
+makes no increment to the caption number. This does not (of course)
+have any effect on actual placement of the float, but it makes the
+caption texts read `sensibly':
+\begin{quote}
+\begin{verbatim}
+\begin{table}
+ \caption{A table}
+ ...
+\end{table}
+...
+\begin{table}\ContinuedFloat
+ \caption{A table (cont.)}
+ ...
+\end{table}
+\end{verbatim}
+\end{quote}
+which would produce:
+\begin{quote}
+ Table 3: A table
+ \dots
+ Table 3: A table (cont.)
+\end{quote}
+\begin{ctanrefs}
+\item[caption.sty]\CTANref{caption}
+\item[dpfloat.sty]\CTANref{dpfloat}
+\item[fltpage.sty]\CTANref{fltpage}
+\end{ctanrefs}
+\LastEdit{2013-02-01}
+
+\Question[Q-vertposfp]{Vertical layout of float pages}
+
+By default, \LaTeX{} vertically centres the floats on a float page;
+the present author is not alone in not liking this arrangement.
+Unfortunately, the control of the positioning is ``buried'' in
+\LaTeX{}-internal commands, so some care is needed to change the
+layout.
+
+Float pages use three \LaTeX{} lengths (i.e., \TeX{} skips) to define
+their layout:
+\begin{description}
+\item[\nothtml{\normalfont}\csx{@fptop}] defines the distance from the
+ top of the page to the top of the first float,
+\item[\nothtml{\normalfont}\csx{@fpsep}] defines the separation between
+ floats, and
+\item[\nothtml{\normalfont}\csx{@fpbot}] defines the distance from the
+ bottom of the last float on the page to the bottom of the page.
+\end{description}
+(In fact, the output routine places a skip of \csx{@fpsep} above each float, so
+the \csx{@fptop} skip is always followed by a correction for that.)
+
+
+The \LaTeX{} defaults are:
+\begin{quote}
+ \csx{@fptop} = \texttt{0pt + 1fil}\\
+ \csx{@fpsep} = \texttt{8pt + 2fil}\\
+ \csx{@fpbot} = \texttt{0pt + 1fil}\\
+\end{quote}
+so that the gaps expand to fill the space not occupied by floats, but
+if there is more than one float on the page, the gap between them will
+expand to twice the space at top and bottom.
+
+Those who understand this stuff will be able to play elaborate games,
+but the commonest requirement, that the floats start at the top of the
+page, is a simple thing to do:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\setlength{\@fptop}{0pt}
+\makeatother
+\end{verbatim}
+\end{quote}
+Surprisingly, you may find this setting leaves your floats too high on
+the page. One can justify a value of \texttt{5pt} (in place of
+\texttt{0pt})~--- it's roughly the difference between \csx{topskip}
+and the height of normal (\texttt{10pt}) text.
+
+Note that this is a ``global'' setting (best established in a class
+file, or at worst in the document preamble); making the change for a
+single float page is likely (at the least) to be rather tricky.
+
+\Question[Q-figurehere]{Figure (or table) \emph{exactly} where I want it}
+
+This is of course a contradiction: \environment{figure} and
+\environment{table} are \emph{designed} to float, and will always have
+the potential to appear away from where you asked for them. Therefore
+you need something that behaves like a \environment{figure} or
+\environment{table} environment, except that it doesn't allow the
+figure or table to float.
+
+The most straightforward way is to use of the \Package{float} package;
+it gives you a \texttt{[H]} float placement option that prevents
+floating:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}[H]
+ \centering
+ \includegraphics{foo}
+ \caption{caption text}
+ \label{fig:nonfloat}
+\end{figure}
+\end{verbatim}
+\end{quote}
+As the example suggests, such a `\texttt{[H]}' figure (or
+corresponding table) offers all you need to cross-reference as well
+as typeset. (The package \Package{here} provides the same function,
+but is no longer recommended.)
+
+However, you don't actually \emph{have} to use \Package{float} (or
+\Package{here}) since it is, in fact, doing rather little for you.
+You can place your figure as you please, with a sequence like
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+ \includegraphics{foo}
+ \captionof{figure}{caption text}
+ \label{fig:nonfloat}
+\end{center}
+\end{verbatim}
+\end{quote}
+which relies on the \csx{captionof} command to place a caption without
+benefit of an enclosing float. That command may be had from the extremely
+simple-minded package \Package{capt-of} or from the highly
+sophisticated \Package{caption} package.
+
+Using either method, you have to deal with the possibility of the
+figure or table being too large for the page. (Floating objects will
+float away in this circumstance; ``doing it by hand'', like this, you
+take upon yourself the responsibility for avoiding % ! line break
+`\textit{Overfull \csx{vbox}}' errors.
+
+A further problem is the possibility that such ``fixed floats'' will
+overtake ``real floats'', so that the numbers of figures will be out
+of order: figure 6 could be on page 12, while figure 5 had floated to
+page 13. It's best, therefore, either to stay with floating figures
+throughout a document, or to use fixed figures throughout.
+
+If it's really impossible to follow that counsel of perfection, you
+can use the \Package{perpage} package's command \csx{MakeSorted}
+command:
+\begin{quote}
+\begin{verbatim}
+...
+\usepackage{float}
+\usepackage{perpage}
+\MakeSorted{figure}
+\MakeSorted{table}
+...
+\end{verbatim}
+\end{quote}
+and the sequence of float numbers is all correct.
+\begin{ctanrefs}
+\item[capt-of.sty]\CTANref{capt-of}
+\item[caption.sty]\CTANref{caption}
+\item[float.sty]\CTANref{float}
+\item[here.sty]\CTANref{here}
+\item[perpage.sty]Distributed as part of \CTANref{bigfoot}[perpage]
+\end{ctanrefs}
+
+\subsection{Footnotes}
+
+\Question[Q-footintab]{Footnotes in tables}
+
+The standard \LaTeX{} \csx{footnote} command doesn't work in tables;
+the tabular environment (and its ``relations'') traps footnotes, and
+they can't escape to the bottom of the page. As a result, you get
+footnote marks in the table, and nothing else.
+
+This accords with common typographic advice: footnotes and tables are
+reckoned not to mix.
+
+The solution, if you accept the advice, is to use ``table notes''.
+The package \Package{threeparttable} provides table notes, and
+\Package{threeparttablex} additionally supports them in
+\environment{longtable}s. \Package{Threeparttable} works happily in
+ordinary text, or within a \environment{table} float.
+
+The \Package{ctable} package extends the model of
+\Package{threeparttable}, and also uses the ideas of the
+\Package{booktabs} package. The \csx{ctable} command does the complete
+job of setting the table, placing the caption, and defining the
+notes. The ``table'' may consist of diagrams, and a parameter in
+\csx{ctable}'s optional argument makes the float that is created a
+``figure'' rather than a ``table''.
+
+If you really want ``real'' footnotes in tables, despite the expert
+advice, you can:
+\begin{itemize}
+\item Use \csx{footnotemark} to position the little marker
+ appropriately, and then put in \csx{footnotetext} commands to fill in
+ the text once you've closed the \environment{tabular} environment.
+ This is described in Lamport's book, but it gets messy if there's
+ more than one footnote.
+\item Stick the \environment{tabular} environment in a
+ \environment{minipage}. Footnotes in the
+ table then ``work'', in the \environment{minipage}'s style, with no
+ extra effort. (This is, in effect, somewhat like table notes, but
+ the typeset appearance isn't designed for the job.)
+\item Use \Package{tabularx} or \Package{longtable} from the \LaTeX{}
+ tools distribution; they're noticeably less efficient than the
+ standard \environment{tabular} environment, but they do allow
+ footnotes.
+\item Use \Package{tablefootnote}; it provides a command \csx{tablefootnote},
+ which does the job without fuss.
+\item Use \Package{footnote}, which provides an
+ \environment{savenotes} which collects all footnotes and emits them
+ at the end of the environment; thus if you put your
+ \environment{tabular} environment inside a \environment{savenotes}
+ environment, the footnotes will appear as needed. Alternatively,
+ you may use \cmdinvoke{makesavenoteenv}{tabular} in the preamble of your
+ document, and tables will all behave as if they were inside a
+ \environment{savenotes} environment.
+\item Use \Package{mdwtab} from the same bundle; it will handle
+ footnotes as you might expect, and has other facilities to increase
+ the beauty of your tables. Unfortunately, it may be incompatible
+ with other table-related packages, though not those in the standard `tools'
+ bundle.
+\end{itemize}
+All the techniques listed will work, to some extent, whether in a float or
+in ordinary text. The author of this \acro{FAQ} answer doesn't actually
+recommend any of them, believing that table notes are the way to go\dots{}
+\begin{ctanrefs}
+\item[ctable.sty]\CTANref{ctable}
+\item[footnote.sty]Distributed as part of \CTANref{mdwtools}[footnote]
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
+\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}[mdwtab]
+\item[tablefootnote.sty]\CTANref{tablefootnote}
+\item[threeparttable.sty]\CTANref{threeparttable}
+\item[threeparttablex.sty]\CTANref{threeparttablex}
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx]
+\end{ctanrefs}
+\LastEdit{2013-03-11}
+
+\Question[Q-ftnsect]{Footnotes in \LaTeX{} section headings}
+
+The \csx{footnote} command is fragile, so that simply placing the
+command in \csx{section}'s arguments isn't satisfactory. Using
+\csx{protect}\csx{footnote} isn't a good idea either: the arguments of a
+section command are used in the table of contents and (more
+dangerously) potentially also in page headers. While footnotes will
+work in the table of contents, it's generally not thought a ``good
+thing'' to have them there; in the page header, footnotes will simply
+fail. Whatever the desirability of the matter, there's no mechanism
+to suppress the footnote in the page header while allowing it in the table
+of contents, so the footnote may only appear in the section heading itself.
+
+To suppress the footnote in headings and table of contents:
+\begin{itemize}
+\item Take advantage of the fact that the mandatory argument doesn't
+ `move' if the optional argument is present:
+
+ \cmdinvoke{section}[title]%
+ \texttt{\{title}\cmdinvoke{footnote}{title ftnt}\texttt{\}}
+\item Use the \Package{footmisc} package, with package option
+ \texttt{stable}~--- this modifies footnotes so that they softly and
+ silently vanish away if used in a moving argument. With this, you
+ simply need:
+\begin{verbatim}
+% in the document preamble
+\usepackage[stable]{footmisc}
+...
+% in the body of the document
+\section{title\footnote{title ftnt}}
+\end{verbatim}
+\end{itemize}
+\begin{ctanrefs}
+\item[footmisc.sty]\CTANref{footmisc}
+\end{ctanrefs}
+
+\Question[Q-ftncapt]{Footnotes in captions}
+
+Footnotes in captions are especially tricky: they present problems of
+their own, on top of the problems one experiences with
+\Qref*{footnotes in section titles}{Q-ftnsect} (footnotes migrating to
+to the list of figures or tables, or % ! line break
+\Qref{apparently random errors}{Q-extrabrace} because
+\csx{footnote} is a fragile command), and with % ! line break
+\Qref*{footnotes in tables}{Q-footintab} (typically, the footnote
+simply disappears). Fortunately, the requirement for footnotes in
+captions is extremely rare: if you are experiencing problems, it is
+worth reviewing what you are trying to say by placing this footnote:
+other options are to place text at the bottom of the float, or to
+place a footnote at the point where you refer to the float.
+
+Note that the \Package{threeparttable} scheme (see, again, % ! line break
+\Qref[question]{footnotes in tables}{Q-footintab}) also applies
+to notes in captions, and may very well be preferable to whatever you
+were thinking of.
+
+If you \emph{are} going to proceed:
+\begin{itemize}
+\item use an optional argument in your \csx{caption} command, that
+ doesn't have the footnote in it; this prevents the footnote
+ appearing in the ``List of \dots{}'', and
+\item put your whole float in a \environment{minipage} so as to keep
+ the footnotes with the float.
+\end{itemize}
+so we have:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\begin{figure}
+ \begin{minipage}{\textwidth}
+ ...
+ \caption[Compact Routing Example]%
+ {Compact Routing\footnote{something} Example}
+ \end{minipage}
+\end{figure}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\begin{figure}
+ \begin{minipage}{\textwidth}
+ ...
+ \caption[Compact Routing Example]%
+ {Compact Routing\footnote{something}
+ Example}
+ \end{minipage}
+\end{figure}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+So, we make an entry for the List of Figures, which doesn't hold
+troublesome commands, such as \csx{footnote}.
+
+However, \emph{as well as} all of the above, one \emph{also} has to
+deal with the tendency of the \csx{caption} command to produce the
+footnote's text twice. For this last problem, there is no tidy
+solution this author is aware of.
+
+If you're suffering the problem, a well-constructed \csx{caption}
+command in a \environment{minipage} environment within a float (as
+in the example above) can produce \emph{two} copies of the footnote
+body ``something''. (In fact, the effect only occurs with captions that are
+long enough to require two lines to be typeset, and so wouldn't appear
+with such a short caption as that in the example above.)
+
+The documentation of the \Package{ccaption} package describes a really
+rather awful work-around for this problem.
+\begin{ctanrefs}
+\item[ccaption.sty]\CTANref{ccaption}
+\item[threeparttable.sty]\CTANref{threeparttable}
+\end{ctanrefs}
+\LastEdit{2012-04-12}
+
+\Question[Q-repfootnote]{Footnotes whose texts are identical}
+
+If the \emph{same} footnote turns up at several places within a
+document, it's often inappropriate to repeat the footnote in its
+entirety over and over again. We can avoid repetition by
+semi-automatic means, or by simply labelling footnotes that we know
+we're going to repeat and then referencing the result. There is no
+completely automatic solution (that detects and suppresses repeats)
+available.
+
+If you know you only have one footnote, which you want to repeat, the
+solution is simple: merely use the optional argument of
+\csx{footnotemark} to signify the repeats:
+\begin{quote}
+\begin{verbatim}
+...\footnote{Repeating note}
+...
+...\footnotemark[1]
+\end{verbatim}
+\end{quote}
+\dots{}\@ which is very easy, since we know there will only ever be a
+footnote number 1. A similar technique can be used once the footnotes
+are stable, reusing the number that \LaTeX{} has allocated. This can
+be tiresome, though, as any change of typesetting could change the
+relationships of footnote and repeat: labelling is inevitably better.
+
+Simple hand-labelling of footnotes is possible, using a counter dedicated
+to the job:
+\begin{quote}
+\begin{verbatim}
+\newcounter{fnnumber}
+...
+...\footnote{Text to repeat}%
+\setcounter{fnnumber}{\thefootnote}%
+...
+...\footnotemark[\thefnnumber]
+\end{verbatim}
+\end{quote}
+but this is somewhat tedious. \LaTeX{}'s labelling mechanism can be
+summoned to our aid, but there are ugly error messages before the
+\csx{ref} is resolved on a second run through \LaTeX{}:
+\begin{quote}
+\begin{verbatim}
+...\footnote{Text to repeat\label{fn:repeat}}
+...
+...\footnotemark[\ref{fn:repeat}]
+\end{verbatim}
+\end{quote}
+Alternatively, one may use the \csx{footref} command, which has the
+advantage of working even when the footnote mark isn't expressed as a
+number. The command is defined in the \Package{footmisc} package and
+in the \Class{memoir} class (at least); \csx{footref} reduces the above
+example to:
+\begin{quote}
+\begin{verbatim}
+...\footnote{Text to repeat\label{fn:repeat}}
+...
+...\footref{fn:repeat}
+\end{verbatim}
+\end{quote}
+This is the cleanest simple way of doing the job. Note that the
+\csx{label} command \emph{must} be inside the argument of
+\csx{footnote}.
+
+The \Package{fixfoot} package takes away some of the pain of the
+matter: you declare footnotes you're going to reuse, typically in the
+preamble of your document, using a \csx{DeclareFixedFoot} command, and
+then use the command you've `declared' in the body of the document:
+\begin{quote}
+\begin{verbatim}
+\DeclareFixedFootnote{\rep}{Text to repeat}
+...
+...\rep{}
+...\rep{}
+\end{verbatim}
+\end{quote}
+The package ensures that the repeated text appears at most once per
+page: it will usually take more than one run of \LaTeX{} to get rid of
+the repeats.
+\begin{ctanrefs}
+\item[fixfoot.sty]\CTANref{fixfoot}
+\item[footmisc.sty]\CTANref{footmisc}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-multfoot]{More than one sequence of footnotes}
+
+The need for more than one series of footnotes is common in critical
+editions (and other literary criticism), but occasionally arises in
+other areas.
+
+Of course, the canonical critical edition package, \Package{edmac},
+offers the facility, as does its \LaTeX{} port, the \Package{ledmac}
+package.
+
+Multiple ranges of footnotes are offered to \LaTeX{} users by the
+\Package{manyfoot} package. The package provides a fair array of
+presentation options, as well. Another critical edition
+\Package{ednotes} package is built upon a basis that includes
+\Package{manyfoot}, as its mechanism for multiple sets of footnotes.
+
+The \Package{bigfoot} package also uses \Package{manyfoot} as part of
+its highly sophisticated structure of footnote facilities, which was
+also designed to support typesetting critical editions.
+\begin{ctanrefs}
+\item[bigfoot]\CTANref{bigfoot}
+\item[edmac]\CTANref{edmac}
+\item[ednotes]\CTANref{ednotes}
+\item[ledmac]\CTANref{ledmac}
+\item[manyfoot.sty]Distributed as part of \CTANref{ncctools}[manyfoot]
+\end{ctanrefs}
+
+\Question[Q-footnpp]{Footnotes numbered ``per page''}
+
+The obvious solution is to make the footnote number reset whenever the
+page number is stepped, using the % ! line break
+\Qref*{\LaTeX{} internal mechanism}{Q-addtoreset}. Sadly, the place
+in the document where the page number is stepped is unpredictable, not
+(``tidily'') at the end of the printed page; so changing the footnote
+number only ever works by `luck'.
+
+As a result, resetting footnotes is inevitably a complicated process,
+using labels of some sort. It's nevertheless important, given the
+common requirement for footnotes marked by symbols (with painfully
+small symbol sets). There are four packages that manage it, one way
+or another.
+
+The \Package{perpage} and \Package{zref-perpage} packages provide a
+general mechanism for resetting counters per page, so can obviously be
+used for this task. The interface is pretty simple:
+\cmdinvoke{MakePerPage}{footnote} (in \Package{perpage}) or
+\cmdinvoke{zmakeperpage}{footnote} (in \Package{zref-perpage}). If
+you want to restart the counter at something other than~1 (for example
+to avoid something in the \LaTeX{} footnote symbol list), you can use:
+\cmdinvoke{MakePerPage}[2]{footnote} (in \Package{perpage}) or
+\cmdinvoke{zmakeperpage}[2]{footnote} (in \Package{zref-perpage}).
+Note that you can also load \Package{zref-perpage}
+
+\Package{Perpage} is a compact and efficient package;
+\Package{zref-perpage}, being a \Package{zref} ``module'', comes with
+\Package{zref}'s general mechanism for extending the the
+\csx{label}---\csx{[page]ref} of \latex{}, which can offer many other
+useful facilities.
+
+The \Package{footmisc} package provides a variety of means of
+controlling footnote appearance, among them a package option
+\pkgoption{perpage} that adjusts the numbering per page; if you're
+doing something else odd about footnotes, it means you may only need
+the one package to achieve your ends.
+
+The \Package{footnpag} package also does per-page footnotes (and
+nothing else). With the competition from \Package{perpage}, it's
+probably not particularly useful any more.
+\begin{ctanrefs}
+\item[footmisc.sty]\CTANref{footmisc}
+\item[footnpag.sty]\CTANref{footnpag}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage]
+%\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref]
+\item[zref-perpage.sty]Distributed as part of \Package{zref} in
+ \CTANref{oberdiek}[zref]
+\end{ctanrefs}
+
+\Question[Q-run-fn-nos]{Not resetting footnote numbers per chapter}
+
+Some classes (for example, \Class{book} and \Class{report}) set up a
+different set of footnotes per chapter, by resetting the footnote
+number at the start of the chapter. This is essentially the same
+action as that of % ! line break
+\Qref*{equation, figure and table numbers}{Q-running-nos},
+except that footnote numbers don't get ``decorated'' with the chapter
+number, as happens with those other numbers.
+
+The solution is the same: use the \Package{chngcntr} package; since the
+numbers aren't ``decorated'' you can use the \csx{counterwithout*}
+variant; the code:
+\begin{quote}
+\begin{verbatim}
+\counterwithout*{footnote}{chapter}
+\end{verbatim}
+\end{quote}
+is all you need
+\begin{ctanrefs}
+\item[chngcntr.sty]\CTANref{chngcntr}
+\end{ctanrefs}
+
+\subsection{Document management}
+
+\Question[Q-filename]{What's the name of this file}
+
+One might want this so as to automatically generate a page header or
+footer recording what file is being processed. It's not easy\dots{}
+
+\TeX{} retains what it considers the name of the \emph{job}, only, in
+the primitive \csx{jobname}; this is the name of the file first
+handed to \TeX{}, stripped of its directory name and of any extension
+(such as \extension{tex}). If no file was passed (i.e., you're using
+\TeX{} interactively), \csx{jobname} has the value \texttt{texput}
+(the name that's given to \extension{log} files in this case).
+
+This is fine, for the case of a small document, held in a single file;
+most significant documents will be held in a bunch of files, and
+\TeX{} makes no attempt to keep track of files input to the
+\emph{job}. So the user has to keep track, himself~--- the only way
+is to patch the input commands and cause them to retain details of the
+file name. This is particularly difficult in the case of \plaintex{},
+since the syntax of the \csx{input} command is so peculiar.
+
+In the case of \LaTeX{}, the input commands have pretty regular
+syntax, and the simplest \Qref*{patching techniques}{Q-patch} can be
+used on them. (Note that latex{}'s \csx{input} command is itself a
+patch on top of the \plaintex{} command. Our patches apply to the
+\latex{} version of the command, which is used as \cmdinvoke*{input}{file})
+
+%% If you only have one level of input (you never input things from a
+%% file that was itself input), the job is almost trivial:
+%% \begin{quote}
+%% \begin{verbatim}
+%% \def\ThisFile{\jobname}
+%% \let\OldInput\input
+%% \renewcommand{\input}[1]{%
+%% \renewcommand{\ThisFile}{#1}%
+%% \OldInput#1%
+%% }
+%% \end{verbatim}
+%% \end{quote}
+%% With that, the macro \csx{ThisFile} always contains the last thing
+%% input: it starts pointing at the base file of your document
+%% (\csx{jobname}), and thereafter changes every time you use
+%% \cmdinvoke*{input}{file}. Note that this is not satisfactory if your
+%% document contains things \emph{other} than \csx{input} commands. For
+%% example, in:
+%% \begin{quote}
+%% \begin{verbatim}
+%% \documentclass{article}
+%% ... (macros above)
+%% \begin{document}
+%% \input{preamble}
+%% <body of document>
+%% \input{postamble}
+%% \end{document}
+%% \end{verbatim}
+%% \end{quote}
+%% \csx{ThisFile} contains ``\texttt{preamble}'' throughout the % !line break
+%% \meta{body of document}.
+
+%% Most ordinary users will quickly become irritated with the simplicity
+%% of of the \csx{ThisFile} mechanism above. The following code is more
+%% cunning: it maintains details of the files you've `come through' to
+%% get to where you are, and it restores \csx{ThisFile} to what the
+%% previous file was before returning.
+%% \begin{quote}
+%% \begin{verbatim}
+%% \def\ThisFile{\jobname}
+%% \newcounter{FileStack}
+%% \let\OrigInput\input
+%% \renewcommand{\input}[1]{%
+%% \stackinput{#1}{\OrigInput}%
+%% }
+%% \newcommand{\stackinput}[2]{%
+%% \stepcounter{FileStack}%
+%% \expandafter\let
+%% \csname NameStack\theFileStack\endcsname
+%% \ThisFile
+%% \def\ThisFile{#1}%
+%% #2#1%
+%% \expandafter\let\expandafter
+%% \ThisFile
+%% \csname NameStack\theFileStack\endcsname
+%% \addtocounter{FileStack}{-1}%
+%% }
+%% \end{verbatim}
+%% \end{quote}
+%% To do the same for \csx{include}, we need the simple addition:
+%% \begin{quote}
+%% \begin{verbatim}
+%% \let\OrigInclude\include
+%% \renewcommand{\include}[1]{%
+%% \stackinput{#1}{\OrigInclude}%
+%% }
+%% \end{verbatim}
+%% \end{quote}
+%% Remember, both examples of patching \csx{input} assume you always use
+%% \LaTeX{} syntax, i.e., always use braces around the argument.
+
+It is possible to keep track of the name of the file currently being
+processed, but it's surprisingly difficult (these \acro{FAQ}s offered
+code, for a long time, that just didn't work in many cases).
+
+The \Package{currfile} package provides a regular means of keeping
+track of the details of the current file (its name in
+\csx{currfilename}, directory in \csx{currfiledir}, as well as the
+file `base' name (less its extension) and its extension).
+\Package{Currfile} does this with the help of a second package,
+\Package{filehook}, which spots file operations that use \csx{input},
+\csx{InputIfFileExists} and \csx{include}, as well as package and
+class loading.
+
+The \Package{FiNK} (``File Name Keeper'') package keeps track of the
+file name and extension, in a macro \csx{finkfile}. \Package{FiNK} is
+now deprecated, in favour of \Package{currfile}, but remains available
+for use in old documents.
+%
+%% If you need the
+%% unadorned file name (without its `\extension{tex}'), use the commands:
+%% \begin{quote}
+%% \begin{verbatim}
+%% \def\striptexext#1.tex{#1}
+%% ...
+%% \edef\ThisFile{\expandafter\stripext\finkfile}
+%% \end{verbatim}
+%% \end{quote}
+%
+The \Package{FiNK} bundle includes a \File{fink.el} that provides
+support under \ProgName{emacs} with \acro{AUC}-\TeX{}.
+\begin{ctanrefs}
+\item[currfile.sty]\CTANref{currfile}
+\item[filehook.sty]\CTANref{filehook}
+\item[fink.sty]\CTANref{fink}
+\end{ctanrefs}
+
+\Question[Q-filesused]{All the files used by this document}
+
+When you're sharing a document with someone else (perhaps as part of a
+co-development cycle) it's as well to arrange that both correspondents
+have the same set of auxiliary files, as well as the document in
+question. Your correspondent obviously needs the same set of files
+(if you use the \Package{url} package, she has to have \Package{url}
+too, for example). But suppose you have a bug-free version of the
+\Package{shinynew} package but her copy is still the unstable
+original; until you both realise what is happening, such a situation
+can be very confusing.
+
+The simplest solution is the \LaTeX{} \csx{listfiles} command. This
+places a list of the files used and their version numbers in the log
+file. If you extract that list and transmit it with your file, it can
+be used as a check-list in case that problems arise.
+
+Note that \csx{listfiles} only registers things that are input by the
+``standard'' \LaTeX{} mechanisms (\csx{documentclass}, \csx{usepackage},
+\csx{include}, \csx{includegraphics} and so on).
+The \csx{input} command, as modified by \LaTeX{} and used, with
+\LaTeX{} syntax, as:
+\begin{verbatim}
+ \input{mymacros}
+\end{verbatim}
+records file details for \File{mymacros.tex}, but if you use \TeX{}
+primitive syntax for \csx{input}, as:
+\begin{verbatim}
+ \input mymacros
+\end{verbatim}
+\File{mymacros.tex} \emph{won't} be recorded, and so won't listed by
+\csx{listfiles}~--- you've bypassed the mechanism that records its use.
+
+The \Package{snapshot} package helps the owner of a \LaTeX{} document
+obtain a list of the external dependencies of the document, in a form
+that can be embedded at the top of the document. The intended use of
+the package is the creation of archival copies of documents, but it
+has application in document exchange situations too.
+
+The \ProgName{bundledoc} system uses the \Package{snapshot} to produce an
+archive (e.g., \extension{tar.gz} or \extension{zip}) of the files needed by your
+document; it comes with configuration files for use with
+\texlive{}-\ProgName{Unix} and \ProgName{\miktex{}}. It's plainly useful when
+you're sending the first copy of a document.
+
+The \ProgName{mkjobtexmf} finds which files are used in a `job',
+either via the \texttt{-recorder} option of \tex{}, or by using the
+(Unix) command \ProgName{strace} to keep an eye on what \tex{} is
+doing. The files thus found are copied (or linked) to a directory
+which may then be saved for transmission or archiving.
+\begin{ctanrefs}
+\item[bundledoc]\CTANref{bundledoc}
+\item[mkjobtexmf]\CTANref{mkjobtexmf}
+\item[snapshot.sty]\CTANref{snapshot}
+\end{ctanrefs}
+\LastEdit{2014-01-26}
+
+\Question[Q-changebars]{Marking changed parts of your document}
+
+One often needs clear indications of how a document has changed, but
+the commonest technique, ``change bars'' (also known as ``revision
+bars''), requires surprisingly much
+trickery of the programmer. The problem is that \TeX{} `proper'
+doesn't provide the programmer with any information about the
+``current position'' from which a putative start- or end-point of a
+bar might be calculated. \PDFTeX{} \emph{does} provide that
+information, but no \PDFTeX{}-based changebar package has been
+published, that takes advantage of that.
+
+The simplest package that offers change bars is Peter Schmitt's
+\Package{backgrnd.tex}; this was written as a \plaintex{} application
+that patches the output routine, but it appears to work at least on
+simple \LaTeX{} documents. Wise \LaTeX{} users will be alerted by the
+information that \Package{backgrnd} patches their output routine, and
+will watch its behaviour very carefully (patching the \LaTeX{} output
+routine is not something to undertake lightly\dots{}).
+
+The longest-established \LaTeX{}-specific solution is the
+\Package{changebar} package,
+which uses \csx{special} commands supplied by the driver you're using.
+You need therefore to tell the package which driver to you're using
+(in the same way that you need to tell the \Package{graphics}
+package); the list of available drivers is pretty
+wide, but does not include \ProgName{dvipdfm}. The package comes with
+a shell script \ProgName{chbar.sh} (for use on Unix machines) that
+will compare two documents and generate a third which is marked-up
+with \Package{changebar} macros to highlight changes.
+
+The shareware \ProgName{WinEDT} editor has a macro that will generate
+\Package{changebar} (or other) macros to show differences from an
+earlier version of your file, stored in an \ProgName{RCS}-controlled
+repository~--- see
+\URL{http://www.winedt.org/Macros/LaTeX/RCSdiff.php}
+
+The \Package{vertbars} package uses the techniques of the
+\Package{lineno} package (which it loads, so the \Package{lineno}
+itself must be installed); it's thus the smallest of the packages for
+change bar marking, since it leaves all the trickery to another
+package. \Package{Vertbars} defines a \environment{vertbar}
+environment to create changebars.
+
+The \Package{framed} package is
+another that provides bars as a side-effect of other desirable
+functionality: its \environment{leftbar} environment is simply a
+stripped-down frame (note, though, that the environment makes a
+separate paragraph of its contents, so it is best used when the
+convention is to mark a whole changed paragraph.
+
+Finally, the \Class{memoir} class allows marginal editorial comments,
+which you can obviously use to delimit areas of changed text.
+
+An even more comprehensive way to keep track of changes is employed by
+some word-processors~--- to produce a document that embodies both
+``old'' and ``new'' versions.
+
+To this end, the package \Package{changes} allows the user to manually
+markup changes of text, such as additions, deletions, or replacements.
+Changed text is shown in a different colour; deleted text is crossed
+out. The package allows you to define additional authors and their
+associated colour; it also allows you to define a markup for authors
+or annotations. The documentation (very clearly) demonstrates how the
+various functions work.
+
+The \ProgName{Perl} script \ProgName{latexdiff} may also be used to
+generate such markup for \LaTeX{} documents; you feed it the two
+documents, and it produces a new \LaTeX{} document in which the
+changes are very visible. An example of the output is embedded in the
+documentation,
+\begin{narrowversion} % actually non-hyperversion
+ \File{latexdiff-man.pdf}, in the distribution.
+\end{narrowversion}
+\begin{wideversion} % actually hyperversion
+ \href{http://mirrors.ctan.org/support/latexdiff/latexdiff-man.pdf}{latexdiff-man.pdf}
+ (part of the distribution).
+\end{wideversion}
+A rudimentary revision facility is provided by another
+\ProgName{Perl} script, \ProgName{latexrevise}, which accepts or rejects
+all changes. Manual editing of the difference file can be used to
+accept or reject selected changes only.
+\begin{ctanrefs}
+\item[backgrnd.tex]\CTANref{backgrnd}
+\item[changebar.sty]\CTANref{changebar}
+\item[changes.sty]\CTANref{changes}
+\item[framed.sty]\CTANref{framed}
+\item[latexdiff, latexrevise]\CTANref{latexdiff}
+\item[lineno.sty]\CTANref{lineno}
+\item[memoir.cls]\CTANref{memoir}
+\item[vertbars.sty]\CTANref{vertbars}
+\item[winedt]\CTANref{winedt}
+\end{ctanrefs}
+
+\Question[Q-conditional]{Conditional compilation and ``comments''}
+
+While \LaTeX{} (or any other \TeX{}-derived package) isn't really like a
+compiler, people regularly want to do compiler-like things using it.
+Common requirements are conditional `compilation' and `block
+comments', and several \LaTeX{}-specific means to this end are available.
+
+The simple \cmdinvoke{newcommand}{\csx{gobble}}[1]\texttt{\{\}}
+and \csx{iffalse}\texttt{ ... }\csx{fi} aren't really satisfactory (as
+a general solution) for comments, since the matter being skipped is
+nevertheless scanned by \TeX{}, not always as you would expect. The
+scanning imposes restrictions on what you're allowed to skip; this may
+not be a problem in \emph{today's} job, but could return to bite you
+tomorrow. For an example of surprises that may come to bite you,
+consider the following example (derived from real user experience):
+\begin{quote}
+\begin{verbatim}
+\iffalse % ignoring this bit
+consider what happens if we
+use \verb+\iftrue+ -- a surprise
+\fi
+\end{verbatim}
+\end{quote}
+The \csx{iftrue} is spotted by \TeX{} as it scans, ignoring the
+\csx{verb} command; so the \csx{iffalse} isn't terminated by the
+following \csx{fi}. Also, \csx{gobble} is pretty inefficient at
+consuming anything non-trivial, since all the matter to be skipped is
+copied to the argument stack before being ignored.
+
+If your requirement is for a document from which whole chapters (or
+the like) are missing, consider the \LaTeX{}
+\csx{include}/\csx{includeonly} system. If you `\csx{include}' your
+files (rather than \csx{input} them~--- see % line wrap!
+\Qref[question]{What's going on in my \csx{include} commands?}{Q-include}),
+\LaTeX{} writes macro traces of what's going on at the end of each
+chapter to the \extension{aux} file; by using \csx{includeonly}, you can give
+\LaTeX{} an exhaustive list of the files that are needed. Files that
+don't get \csx{include}d are skipped entirely, but the document
+processing continues as if they \emph{were} there, and page, footnote,
+and other numbers are not disturbed. Note that you can choose which
+sections you want included interactively, using the
+\Package{askinclude} package.
+
+A variant on the \csx{includeonly} mechanism is offered by the
+\Package{stampinclude} package, which takes advantage of the \pdftex{}
+\csx{pdffilemoddate} command. When an \csx{include}d file is
+processed in a \latex{} document, an \extension{aux} file is created
+holding data such as page-number ranges and chapter/section numbers.
+When \csx{stampinclude} is included in a document, it compares the
+file system modification times for each file and its corresponding
+\extension{aux} file; the file is only compiled in ``this run'' of the
+document if the file is newer than its corresponding \extension{aux}
+file. The package requires a current \pdftex{}, and will also run on
+\luatex{} if the \Package{pdftexcmds} package is available
+(\Package{pdftexcmds} emulates the requisite \pdftex{} commands using
+\texttt{lua}. Apart from this requirement, \Package{stampinclude} is
+a low-maintenace object; include it in your document and it silently
+does its job. When you want a final version of your document, delete
+all the \extension{aux} files, and and \Package{stampinclude} won't
+interfere.)
+
+The inverse can be done using the \Package{excludeonly} package: this
+allows you to exclude a (list of) \csx{include}d files from your
+document, by means of an \csx{excludeonly} command.
+
+If you want to select particular pages of your document, use Heiko
+Oberdiek's \Package{pagesel} or the \Package{selectp} packages. You
+can do something similar with an existing \acro{PDF} document (which
+you may have compiled using \ProgName{pdflatex} in the first place),
+using the \Package{pdfpages} package. The job is then done with a
+document looking like:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\usepackage[final]{pdfpages}
+\begin{document}
+\includepdf[pages=30-40]{yoursource.pdf}
+\end{document}
+\end{verbatim}
+\end{quote}
+(To include all of the document, you write
+\begin{quote}
+\begin{verbatim}
+\includepdf[pages=-]{yoursource.pdf}
+\end{verbatim}
+\end{quote}
+omitting the start and end pages in the optional argument.)
+
+If you want flexible facilities for including or excluding small
+portions of a file, consider the \Package{comment}, \Package{version} or
+\Package{optional} packages.
+
+The \Package{comment} package allows you to declare areas of a document to be
+included or excluded; you make these declarations in the preamble of
+your file. The command \cmdinvoke*{includecomment}{version-name}
+declares an environment \environment{version-name} whose content will
+be included in your document, while
+\cmdinvoke*{excludecomment}{version-name} defines an environment whose
+content will be excluded from the document. The package uses a method
+for exclusion that is pretty robust, and can cope with ill-formed
+bunches of text (e.g., with unbalanced braces or \csx{if} commands).
+
+(These FAQs employ the \Package{comment} package to alter layout
+between the printed (two-column) version and the \acro{PDF} version
+for browsing; there are \environment{narrowversion} and
+\environment{wideversion} for the two versions of the file.)
+
+\Package{version} offers similar facilities to \File{comment.sty}
+(i.e., \csx{includeversion} and \csx{excludeversion} commands);
+it's far ``lighter weight'', but is less robust (and in particular,
+cannot deal with very large areas of text being included/excluded).
+
+A significant development of \Package{version}, confusingly called
+\Package{versions} (i.e., merely a plural of the old package name).
+\Package{Versions} adds a command
+\cmdinvoke*{markversion}{version-name} which defines an environment
+that prints the included text, with a clear printed mark around it.
+
+\Package{optional} defines a command \csx{opt}; its first argument is
+an `inclusion flag', and its second is text to be included or
+excluded. Text to be included or excluded must be well-formed
+(nothing mismatched), and should not be too big~--- if a large body of
+text is needed, \csx{input} should be used in the argument.
+The documentation (in the package file itself) tells you
+how to declare which sections are to be included: this can be done in
+the document preamble, but the documentation also suggests ways in
+which it can be done on the command line that invokes \LaTeX{}, or
+interactively.
+
+And, not least of this style of conditional compilation,
+\Package{verbatim} (which should be available in any distribution)
+defines a \environment{comment} environment, which enables the
+dedicated user of the source text editor to suppress bits of a
+\LaTeX{} source file. The \Class{memoir} class offers the same
+environment.
+
+An interesting variation is the \Package{xcomment} package. This
+defines an environment whose body is all excluded, apart from
+environments named in its argument. So, for example:
+\begin{quote}
+\begin{verbatim}
+\begin{xcomment}{figure,table}
+ This text is not included
+ \begin{figure}
+ This figure is included
+ \end{figure}
+ This is not included, either
+ \begin{table}
+ This table also included
+ \end{table}
+ ...
+\end{xcomment}
+\end{verbatim}
+\end{quote}
+
+The \Package{tagging} package offers another neat set of syntax, which
+allow the user to apply ``tags'' to chunks of text, and to include and
+exclude tagged text, according to the tags. For example, the user may
+`use' text marked with some tags, and to `drop' marked with others:
+\begin{quote}
+\begin{verbatim}
+\usetag{<tag list>}
+\droptag{<tag list>}
+\end{verbatim}
+\end{quote}
+(the tag lists consist of comma-separated single words).
+
+There are then commands
+\begin{quote}
+\begin{verbatim}
+\tagged{<tag list>}{<text>}
+\end{verbatim}
+\end{quote}
+which reproduces the text only if the \meta{tag list} contains at
+least one tag listed in the \csx{usetag} comand, and
+\begin{quote}
+\begin{verbatim}
+\untagged{<tag list>}{<text>}
+\end{verbatim}
+\end{quote}
+which only reproduces the text unless the \meta{tag list} contains
+none of the tags mention in the \csx{droptag} command.
+
+Further commands offer an if-then-else setup, and specify
+\environment{taggedblock} and \environment{untaggedblock} environments
+that.
+
+Another valuable aspect of the problem is covered by the
+\Package{extract} package. The package allows you to produce a
+``partial copy'' of an existing document:
+the package was developed to permit production of a ``book of
+examples'' from a set of lecture notes. The package documentation
+shows the following usage:
+\begin{quote}
+\begin{verbatim}
+\usepackage[
+ active,
+ generate=foobar,
+ extract-env={figure,table},
+ extract-cmd={chapter,section}
+]{extract}
+\end{verbatim}
+\end{quote}
+which will cause the package to produce a file \File{foobar.tex}
+containing all the \environment{figure} and \environment{table}
+environments, and the \csx{chapter} and \csx{section} commands, from
+the document being processed. The new file \File{foobar.tex} is
+generated in the course of an otherwise ordinary run on the `master'
+document. The package provides a good number of other facilities,
+including (numeric or labelled) ranges of environments to extract, and
+an \environment{extract} environment which you can use to create complete
+ready-to-run \LaTeX{} documents with stuff you've extracted.
+\begin{ctanrefs}
+\item[askinclude.sty]Distributed as part of \CTANref{oberdiek}[askinclude]
+\item[comment.sty]\CTANref{comment}
+\item[excludeonly.sty]\CTANref{excludeonly}
+\item[extract.sty]\CTANref{extract}
+\item[memoir.cls]\CTANref{memoir}
+\item[optional.sty]\CTANref{optional}
+\item[pagesel.sty]Distributed as part of \CTANref{oberdiek}[pagesel]
+\item[pdfpages.sty]\CTANref{pdfpages}
+\item[selectp.sty]\CTANref{selectp}
+\item[stampinclude.sty]Distributed as part of \CTANref{oberdiek}[stampinclude]
+\item[tagging.sty]\CTANref{tagging}
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim]
+\item[version.sty]\CTANref{version}
+\item[versions.sty]\CTANref{versions}
+\item[xcomment.sty]\CTANref{xcomment}
+\end{ctanrefs}
+\LastEdit{2014-06-09}
+
+\Question[Q-docotherdir]{Bits of document from other directories}
+
+A common way of constructing a large document is to break it into a
+set of files (for example, one per chapter) and to keep everything
+related to each of these subsidiary files in a subdirectory.
+
+Unfortunately, \TeX{} doesn't have a changeable ``current directory'',
+so that all files you refer to have to be specified relative to the
+same directory as the main file. Most people find this
+counter-intuitive.
+
+It may be appropriate to use the ``path extension'' technique
+% beware line break
+\Qref[of question]{used in temporary installations}{Q-tempinst} to deal with
+this problem. However, if there several files with the same name in
+your document, such as \File{chapter1/fig1.eps} and
+\File{chapter2/fig1.eps}, you're not giving \TeX{} any hint as to
+which you're referring to when in the main chapter file you say
+\cmdinvoke{input}{sect1}; while this is readily soluble in the case of
+human-prepared files (just don't name them all the same),
+automatically produced files have a way of having repetitious names,
+and changing \emph{them} is a procedure prone to error.
+
+The \Package{import} package comes to your help here: it defines an
+\csx{import} command that accepts a full path name and the name of a
+file in that directory, and arranges things to ``work properly''.
+So, for example, if \File{/home/friend/results.tex} contains
+\begin{quote}
+\begin{verbatim}
+Graph: \includegraphics{picture}
+\input{explanation}
+\end{verbatim}
+\end{quote}
+then \cmdinvoke{import}{/home/friend/}{results} will include both
+graph and explanation as one might hope. A \csx{subimport} command
+does the same sort of thing for a subdirectory (a relative path rather
+than an absolute one), and there are corresponding \csx{includefrom}
+and \csx{subincludefrom} commands.
+
+The \Package{chapterfolder} package provides commands to deal with its
+(fixed) model of file inclusion in a document. It provides commands
+\csx{cfpart}, \csx{cfchapter}, \csx{cfsection} and \csx{cfsubsection},
+each of which takes directory and file arguments, e.g.:
+\begin{quote}
+\begin{verbatim}
+\cfpart[pt 1]{Part One}{part1}{part}
+\end{verbatim}
+\end{quote}
+which command will issue a `normal' command % ! line break
+\cmdinvoke{part}[pt 1]{Part One} and then input the file
+\File{part1/part.tex}, remembering that \File{part1/} is now the
+``current folder''. There are also commands of the form
+\csx{cfpartstar} (which corresponds to a \csx{part*} command).
+
+Once you're ``in'' a \Package{chapterfolder}-included document, you
+may use \csx{cfinput} to input something relative to the ``current
+folder'', or you may use \csx{input}, using \csx{cfcurrentfolder} to
+provide a path to the file. (There are also
+\csx{cfcurrentfolderfigure} for a \path{figure/} subdirectory and
+\csx{cfcurrentfolderlistings} for a \path{listings/} subdirectory.)
+
+Documentation of \Package{chapterfolder} is in French, but the
+\File{README} in the directory is in English.
+\begin{ctanrefs}
+\item[chapterfolder.sty]\CTANref{chapterfolder}
+\item[import.sty]\CTANref{import}
+\end{ctanrefs}
+
+\Question[Q-RCS]{Version control using \acro{RCS}, \acro{CVS} or the like}
+
+If you use \acro{RCS}, \acro{CVS}, \ProgName{Subversion},
+\ProgName{Bazaar} or \ProgName{Git} to maintain
+your \AllTeX{} documents under version control, you may need some
+mechanism for including the version details in your document, in such
+a way that they can be typeset (that is, rather than just hiding them
+inside a comment).
+
+The most complete solution for \acro{RCS} and \acro{CVS} is to use the
+(\LaTeX{}) package \Package{rcs}, which allows you to parse and
+display the contents of \acro{RCS} keyword fields in an extremely
+flexible way. The package \Package{rcsinfo} is simpler, but does most
+of what you want, and some people prefer it; it is explicitly
+compatible with \ProgName{LaTeX2HTML}.
+
+If, however, you need a solution which works without using external
+packages, or which will work in \plaintex{}, then you can use the
+following minimal solution:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}}
+\RCS$Revision: 1.47 $ % or any RCS keyword
+\RCS$Date: 2014/01/28 18:17:23 $
+...
+\date{Revision \RCSRevision, \RCSDate}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\def\RCS$#1: #2 ${\expandafter
+ \def\csname RCS#1\endcsname{#2}%
+}
+\RCS$Revision: 1.47 $ % or any RCS keyword
+\RCS$Date: 2014/01/28 18:17:23 $
+...
+\date{Revision \RCSRevision, \RCSDate}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+
+If you are a user of \ProgName{Subversion}, the package \Package{svn}
+may be for you. It has explicit cleverness about dealing with dates:
+\begin{quote}
+\csx{documentclass}\texttt{\{\meta{foo}\}}\\
+\texttt{...}\\
+\cmdinvoke{usepackage}{svn}\\
+\csx{SVNdate}\texttt{ \$Date\$}\\
+\cmdinvoke{author}{...}\\
+\cmdinvoke{title}{...}\\
+\texttt{...}\\
+\cmdinvoke{begin}{document}\\
+\csx{maketitle}\\
+\texttt{...}\\
+\cmdinvoke{end}{document}
+\end{quote}
+will (once \ProgName{subversion} has committed a copy of the document)
+cause \csx{maketitle} use the date that has been written into the
+\texttt{\$Date\$} keyword.
+
+Another alternative for \ProgName{Subversion} users is the
+\Package{svninfo} package, which has much the same mechanisms as does
+\Package{svn} but with a rather different focus. \Package{Svninfo}
+does the date trick that \Package{svn} performs (controlled by a
+package option), and can set up page foot-lines using % ! line break
+\Qref*{package \Package{fancyhdr}}{Q-fancyhdr}. There isn't much to
+choose between the two packages: you should read the packages'
+documentation to see which suits you best.
+
+An alternative script-based approach to version control has been taken
+by the \Package{vc} bundle, that in certain situations might work more
+reliably than any of the packages mentioned above. The \Package{vc}
+bundle supports \ProgName{Bazaar}, \ProgName{Git} and
+\ProgName{Subversion} usage and works with both \LaTeX{} and
+\plaintex{}. Note that \Package{vc} is the only option that
+currently claims to support \ProgName{Bazaar}-controlled repositories.
+
+Finally, for now, the \Package{gitinfo} package supports
+\ProgName{Git}-controlled documents.
+\begin{ctanrefs}
+\item[gitinfo.sty]\CTANref{gitinfo}
+\item[rcs.sty]\CTANref{rcs}
+\item[rcsinfo.sty]\CTANref{rcsinfo}
+\item[svn.sty]\CTANref{svn}
+\item[svninfo.sty]\CTANref{svninfo}
+\item[vc]\CTANref{vc}
+\end{ctanrefs}
+\LastEdit{2011-08-31}
+
+\Question[Q-make]{Makefiles for \LaTeX{} documents}
+
+\LaTeX{} documents are tricky beasts for building using
+(\ProgName{Uni*x}) \ProgName{make} on: the need to
+instruct \LaTeX{} to run several times for essentially different
+reasons (for example, ``get the table of contents stable'', ``get the
+labels stable'', ``add the bibliography'', ``add the index'') is
+actually rather difficult to express in the `ordinary' sort of
+dependency graph that one constructs for \ProgName{make}.
+
+The \ProgName{latex-make} package offers help with this task (far more
+sophisticated techniques than in the script that builds these \acro{FAQ}s); it
+looks good, but reports of its use (other than by its author) are scarce.
+
+For a long time, the only \ProgName{make}-like package on \acro{CTAN}
+was \ProgName{latexmk}, which is a \ProgName{Perl}
+script that analyses your \LaTeX{} source for its dependencies, runs
+\BibTeX{} or \ProgName{makeindex} as and when it notices that those
+programs' input (parts of the \extension{aux} file, or the
+\extension{idx} file, respectively) has changed, and so on.
+\ProgName{Latexmk} is a fine
+solution (and was used in generating printable versions of these
+\acro{FAQ}s for some time); it has recently been upgraded and has
+many bells and whistles that allow it to operate as if it were a poor
+man's \WYSIWYG{} system.
+
+A recent strong contender is \ProgName{arara}, written in
+\ProgName{Java}. It is (the documentation says) based on ``rules''
+and ``directives''; its aim is to determine what to do from explicit
+instructions in the document's source code, rather than secondary
+sources such as log file analysis. \ProgName{Arara} is relatively new
+on CTAN, and comes with recommendations from many of the great and
+good of the \latex{} world.
+
+Newer still is the Python script \ProgName{try}, which has a similar
+structure to \ProgName{arara}~--- it, too, reads instructions in the
+document source.
+
+Apparently along the same lines, is Auto\LaTeX{}. The \File{README}
+of the distribution is actual a Unix-type man-page output, and shows
+great attention to the details of the document production process.
+
+The (Ruby) script \ProgName{mk} (also, apparently, known as
+\ProgName{latex_maker}) works well with another of the author's
+scripts script called \ProgName{vpp} (View and Print
+\PS{}/\acro{PDF}).
+
+Windows users of the \miktex{} system may use that system's
+\ProgName{texify} application. \ProgName{Texify} deals with basic
+\LaTeX{} features, including generating a bibliography and an index;
+it makes no claim to deal with other things (such as multiple
+bibliographies or indexes, or lists of terminology, etc.), which
+Auto\LaTeX{} can be configured to process.
+
+The \Qref*{\Package{texinfo} system}{Q-texinfo} comes with a similar
+utility called \ProgName{texi2dvi}, which is capable of ``converting''
+either \LaTeX{} or \Package{texinfo} files into \acro{DVI} (or into
+\acro{PDF}, using \PDFTeX{}).
+
+A later contribution is the bundle \Package{latexmake}, which
+offers a set of \ProgName{make} rules that invoke \ProgName{texi2dvi}
+as necessary.
+
+The curious may examine the rules employed to run the present
+\acro{FAQ} through \LaTeX{}: we don't present them as a complete
+solution, but some of the tricks employed are surely re-usable.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}arara]\CTANref{arara}
+\item[\nothtml{\rmfamily}AutoLaTeX]\CTANref{autolatex}
+\item[\nothtml{\rmfamily}\acro{FAQ} distribution]\CTANref{faq}
+\item[\nothtml{\rmfamily}latexmake]\CTANref{latexmake}
+\item[latex-make]\CTANref{latex-make}
+\item[latex\_make]\CTANref{latex_maker}
+\item[latexmk]\CTANref{latexmk}
+\item[texi2dvi]Distributed as part of \CTANref{texinfo}
+\item[try]\CTANref{try}
+\item[vpp]\CTANref{vpp}
+\end{ctanrefs}
+\LastEdit{2013-05-13}
+
+\Question[Q-howmanypp]{How many pages are there in my document?}
+
+Simple documents (those that start at page 1, and don't have any
+breaks in their page numbering until their last page) present no
+problem to the seeker after this truth. The number of pages is
+reported by the \Package{lastpage} package in its \texttt{LastPage} label.
+
+For more complicated documents (most obviously, books with frontmatter
+in a different series of page numbers) this simple approach will not
+do.
+
+The \Package{count1to} package defines a label \texttt{TotalPages}; this is
+the value of its copy of \csx{count1} (a reserved \TeX{} count
+register) at the end of the document.
+
+Package \Package{totpages} defines a label \texttt{TotPages}, but it also
+makes the register it uses available as a \LaTeX{} counter,
+\texttt{TotPages}, which you can also reference via \csx{theTotPages}. Of
+course, the counter |TotPages| is asynchronous in the same way that
+page numbers are, but snapshots may safely be taken in the output
+routine.
+
+The \Class{memoir} class defines two counters \texttt{lastpage} and
+\texttt{lastsheet}, which are set (after the first run of a document)
+to the equivalent of the \texttt{LastPage} label and the
+\texttt{TotalPages} labels.
+
+Both \Package{count1to} and \Package{totpages} need the support of
+the \Package{everyshi} package.
+\begin{ctanrefs}
+\item[count1to.sty]Distributed as part of \CTANref{ms}[count1to]
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
+\item[lastpage.sty]\CTANref{lastpage}
+\item[memoir.cls]\CTANref{memoir}
+\item[totpages.sty]\CTANref{totpages}
+\end{ctanrefs}
+
+\Question[Q-inclplain]{Including \plaintex{} files in \LaTeX{}}
+
+\LaTeX{}, though originally \Qref*{based on \plaintex{}}{Q-LaTeXandPlain}, does not
+contain all of \plaintex{}'s commands. Worse, some \plaintex{}
+command names appear in \LaTeX{}, with different semantics. As a
+result, special measures need to be taken to allow general \plaintex{}
+documents (or parts of documents) to be typeset within \LaTeX{}.
+
+The truly reliable way is to translate the \plaintex{} commands, to
+produce an equivalent of the original's semantics. However, this is
+not practical in many circumstances, and for those occasions, the
+\Package{plain} package will often come to your aid. The package
+defines a \environment{plain} environment, in which a \plaintex{}
+document may be processed:
+\begin{quote}
+\begin{verbatim}
+\begin{plain}
+ \input{plain-doc}
+\end{plain}
+\end{verbatim}
+\end{quote}
+The package is known to fail, for example, with documents that use
+\AMSTeX{}; no doubt it would also fail if asked to load \Eplain{}.
+All these things can be overcome (although it's not often easy), but
+the environment saves a lot of work on many occasions.
+\begin{ctanrefs}
+\item[plain.sty]Distributed as part of \CTANref{carlisle}[plain-ltx]
+\end{ctanrefs}
+
+\subsection{Hyphenation}
+
+\Question[Q-nohyph]{My words aren't being hyphenated}
+
+Let's assume you've selected the right \TeX{} `language'~--- as
+explained in \Qref[question]{``how hyphenation works''}{Q-hyphen},
+you're not likely to get the correct results typesetting one language
+using the hyphenation rules of another. (Select the proper language,
+using \Package{babel} if you're a \LaTeX{} user. This may reveal that
+you need another set of hyphenation patterns; see
+% beware line wrap
+\Qref[question]{``using a new language''}{Q-newlang} for advice on how
+to install it.)
+
+So what else can go wrong?
+\begin{itemize}
+\item Since \TeX{} version~3.0, the limits on how near to either end
+ of a word hyphenation may take place have been programmable (see
+ \Qref[question]{``weird hyphenation''}{Q-weirdhyphen}), and for some
+ reason the values in question may have been corrupted in some macros
+ you are using. \TeX{} won't hyphenate less than \csx{lefthyphenmin}
+ characters after the start of a word, nor less than
+ \csx{righthyphenmin} before the end of a word; thus it won't
+ hyphenate a word shorter than the sum of the two minima, at all.
+ For example, since the minima are 2 and 3 for English, \TeX{} won't
+ hyphenate a word shorter than 5 letters long, if it believes the
+ word to be English.
+\item \TeX{} won't hyphenate a word that's already been hyphenated.
+ For example, the (caricature) English surname Smyth-Postlethwaite
+ wouldn't hyphenate, which could be troublesome. This is correct
+ English typesetting style (it may not be correct for other
+ languages), but if needs must, you can replace the hyphen in the
+ name with a \csx{hyph} command, defined
+\begin{quote}
+\begin{verbatim}
+\def\hyph{-\penalty0\hskip0pt\relax}
+\end{verbatim}
+\end{quote}
+ This is \emph{not} the sort of thing this \acro{FAQ} would
+ ordinarily recommend\dots{} The \Package{hyphenat} package defines a
+ bundle of such commands (for introducing hyphenation points at
+ various punctuation characters).
+\item There may be accent commands in the word. The causes of and
+ remedies for this effect are discussed in % !line break
+ \Qref[question]{accents and hyphens}{Q-hyphenaccents}.
+\item The hyphenation may simply not have been spotted; while \TeX{}'s
+ algorithm is good, it's not infallible, and it does miss perfectly
+ good hyphenations in some languages. When this happens, you need to
+ give \TeX{} \emph{explicit} instructions on how to hyphenate.
+\end{itemize}
+The \csx{hyphenation} command allows you to give explicit instructions.
+Provided that the word will hyphenate at all (that is, it is not
+prevented from hyphenating by any of the other restrictions above),
+the command will override anything the hyphenation patterns might
+dictate. The command takes one or more hyphenated words as
+argument~--- \cmdinvoke{hyphenation}{ana-lysis pot-able}; note that
+(as here, for analysis) you can use the command to overrule \TeX{}'s
+choice of hyphenation (ana-lysis is the British etymological
+hyphenation; some feel the American hyphenation feels
+`unfortunate'\dots{}).
+\begin{ctanrefs}
+\item[hyphenat.sty]\CTANref{hyphenat}
+\end{ctanrefs}
+\LastEdit{2013-09-20}
+
+\Question[Q-weirdhyphen]{Weird hyphenation of words}
+
+If your words are being h-yphenated, like this, with jus-t single
+letters at the
+beginning or the end of the word, you may have a version mismatch
+problem. \TeX{}'s hyphenation system changed between version~2.9
+and~3.0, and macros written for use with version~2.9 can have this
+effect with a version~3.0 system. If you are using \plaintex{}, make
+sure your \File{plain.tex} file has a version number which is at
+least~3.0, and rebuild your format. If you are using \LaTeXo{} your
+best plan is to upgrade to \LaTeXe{}. If for some reason you can't,
+the last version of \LaTeXo{} (released on 25 March 1992) is still
+available (for the time being at least) and ought to solve this
+problem.
+
+If you're using \LaTeXe{}, the problem probably arises from your
+|hyphen.cfg| file, which has to be created if you're using a
+multi-lingual version.
+
+A further source of oddity can derive from the 1995 release of
+\Qref*{Cork-encoded fonts}{Q-ECfonts},
+which introduced an alternative hyphen character. The \LaTeXe{}
+configuration files in the font release specified use of the
+alternative hyphen, and this could produce odd effects with words
+containing an explicit hyphen. The font configuration files in the
+December 1995 release of \LaTeXe{} do \emph{not} use the alternative
+hyphen character, and therefore removed this source of problems; the
+solution, again, is to upgrade your \LaTeX{}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeXo{}]\CTANref{latex209-base}
+\item[plain.tex]\CTANref{plain}
+\end{ctanrefs}
+
+\Question[Q-oddhyphen]{(Merely) peculiar hyphenation}
+
+You may have found that \TeX{}'s famed automatic word-division does
+not produce the break-points recommended by your dictionary. This may be
+because \TeX{} is set up for American English, whose rules for word
+division (as specified, for example, in Webster's Dictionary) are
+completely different from the British ones (as specified, for example,
+in the Oxford Dictionaries). This problem is being addressed by the \acro{UK}
+\TeX{} User community (see \BV{}, issue~4.4) but an entirely
+satisfactory solution will take time; the current status is to be
+found on \acro{CTAN} (see
+% beware line-wrap
+\Qref[question]{``using a new language''}{Q-newlang} for instructions
+on adding this new ``language'').
+\begin{ctanrefs}
+\item[UK patterns]\CTANref{ukhyph}
+\end{ctanrefs}
+
+\Question[Q-hyphenaccents]{Accented words aren't hyphenated}
+
+\TeX{}'s algorithm for hyphenation gives up when it encounters an
+\csx{accent} command; there are good reasons for this, but it means
+that quality typesetting in non-English languages can be difficult.
+
+For \TeX{} macro packages, you can avoiding the effect by using an
+appropriately encoded font (for example, a Cork-encoded font~--- see
+\Qref[question]{the \acro{EC} fonts}{Q-ECfonts}) which contains accented
+letters as single glyphs. \LaTeX{} users can achieve this end simply
+by adding the command
+\begin{verbatim}
+ \usepackage[T1]{fontenc}
+\end{verbatim}
+to the preamble of their document. Other encodings (notably
+\acro{LY}1, once promoted by \YandY{} inc) may be used
+in place of \acro{T}1. Indeed, most current 8-bit \TeX{} font
+encodings will `work' with the relevant sets of hyphenation patterns.
+
+With the advance of \xetex{} and \luatex{} to the mainstream, a new
+regime for generating hyphenation tables is in place. For each
+language, a table is written in Unicode, and ``8-bit'' versions are
+generated for use with various \latex{} font encodings. Original sets
+of patterns remain on \acro{CTAN}, for use when an older environment
+is needed.
+
+\Question[Q-newlang]{Using a new language with Babel}
+
+\Package{Babel} is capable of working with a large range of
+languages, and a new user often wants to use a language that her
+\TeX{} installation is not set up to employ. Simply asking Babel to
+use the language, with the command
+\begin{verbatim}
+ \usepackage[catalan]{babel}
+\end{verbatim}
+provokes the warning message
+\begin{wideversion}
+\begin{verbatim}
+Package babel Warning: No hyphenation patterns were loaded for
+(babel) the language `Catalan'
+(babel) I will use the patterns loaded for \language=0 instead.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+Package babel Warning: No hyphenation patterns
+ were loaded for
+(babel) the language `Catalan'
+(babel) I will use the patterns
+ loaded for \language=0 instead.
+\end{verbatim}
+(The first and third lines above have been wrapped to fit in the
+column.)
+\end{narrowversion}
+
+The problem is that your \TeX{} system doesn't know how to hyphenate
+Catalan text: you need to tell it how before Babel can do its work
+properly. To do this, for \LaTeX{} installations, one needs to change
+\File{language.dat} (which is part of the Babel installation); it will
+contain a line
+\begin{verbatim}
+%catalan cahyphen.tex
+\end{verbatim}
+which, if you remove the comment marker, is supposed to instruct
+\LaTeX{} to load Catalan hyphenation patterns when you tell it to build
+a new format.
+
+Unfortunately, in many Babel distributions, the line just isn't
+right~--- you need to check the name of the file containing the
+patterns you're going to use. As you can see, in the author's system,
+the name is supposed to be \File{cahyphen.tex}; however the file
+actually present on the system is \File{cahyph.tex}~--- fortunately,
+the error should prove little more than an inconvenience (most of the
+files are in better distributions anyway, but an elusive one
+may be found on \acro{CTAN}; if you have to retrieve
+a new file, ensure that it's correctly installed, for which see
+\Qref[question]{installing a new package}{Q-inst-wlcf}).
+
+Finally, you need to regenerate the formats used (in fact, most users
+of Babel are using it in their \LaTeX{} documents, so regenerating the
+\LaTeX{}-related formats will ordinarily be enough; however, the
+author always generates the lot, regardless).
+\begin{description}
+\item[te\TeX{}]It's possible to do the whole operation in one go, by
+ using the \ProgName{texconfig} command:
+\begin{verbatim}
+texconfig hyphen latex
+\end{verbatim}
+ which first enters an editor for you to edit \File{language.dat},
+ and then regenerates the format you specify (\ProgName{latex} in
+ this case).
+
+ Otherwise, to regenerate all formats, do: \\
+ \texttt{fmtutil -\relax-all}
+
+ If you're willing to think through what you're doing (this is
+ \emph{not} for the faint-hearted), you can select a sequence of
+ formats and for each one, run: \\
+ \texttt{fmtutil -\relax-byfmt \meta{formatname}}\\
+ where \emph{\texttt{formatname}} is something like `\texttt{latex}',
+ or: \\
+ \texttt{fmtutil -\relax-byhyphen \meta{hyphenfile}}\\
+ where \emph{\texttt{hyphenfile}} is the file specifying hyphenation
+ to the format~--- usually \texttt{language.dat}
+\item[\miktex{}] On a \Package{\miktex{}} distribution earlier than v2.0, do: \\
+ \texttt{Start}\arrowhyph{}%
+ \texttt{Programs}\arrowhyph{}%
+ \texttt{\miktex{}}\arrowhyph{}%
+ \texttt{Maintenance}\arrowhyph{}%
+ \texttt{Create all format files}
+% this sequence suggested for miktex 1.20e, 2000/12/22, by Giuseppe Bilotta
+
+ or get a DOS window and run:\\
+ \texttt{initexmf -\relax-dump}
+
+ On a \Package{\miktex{}} distribution v2.0 or later, the whole
+ procedure can be done via the \acro{GUI}. To select the new
+ language, do:\\
+ \texttt{Start}\arrowhyph{}%
+ \texttt{Programs}\arrowhyph{}%
+ \texttt{\miktex{} 2}\arrowhyph{}%
+ \texttt{\miktex{} Options}, and select the \texttt{Languages} tab.
+ Select your language from the list, press the \texttt{Apply} button,
+ and then the \texttt{OK} button. Then select the \texttt{General}
+ tab and press the \texttt{Update Now} button.
+
+ Otherwise, edit the \File{language.dat} file (as outlined above),
+ and then run:\\
+ \texttt{initexmf -\relax-dump}\\
+ just as for a pre-v2.0 system.
+\end{description}
+
+\nothtml{\noindent}\textbf{\emph{Caveat}:} It is (just) possible that
+your \TeX{} system may run out of ``pattern memory'' while generating
+the new format. Most \TeX{} implementations have fixed-size arrays
+for storing the details of hyphenation patterns, but although their
+size is adjustable in most modern distributions, actually changing the
+size is a fiddle. If you \emph{do} find you've run out of memory,
+it may be worth scanning the list of languages in your
+\File{language.dat} to see whether any could reasonably be removed.
+\begin{ctanrefs}
+\item[babel]\CTANref{babel}
+\item[hyphenation patterns]\CTANref{hyphenation}
+\end{ctanrefs}
+
+\Question[Q-hyphoff]{Stopping all hyphenation}
+
+It may seem an odd thing to want to do (after all, one of \TeX{}'s
+great advertised virtues is the quality of its hyphenation) but it's
+sometimes necessary. The real problem is, that the quality of
+\TeX{}'s output is by default largely dependent on the presence of
+hyphenation; if you want to abandon hyphenation, something has to
+give.
+
+\TeX{} (slightly confusingly) offers four possible mechanisms for
+suppressing hyphenation (there were only two prior to the extensions
+that arrived with \TeX{} version~3).
+
+First, one can set the hyphenation penalties \csx{hyphenpenalty} and
+\csx{exhyphenpenalty} to an `infinite' value (that is to say, 10000).
+This means that all hyphenations will sufficiently penalise the line
+that would contain them, that the hyphenation won't happen. The
+disadvantage of this method is that \TeX{} will re-evaluate any
+paragraph for which hyphenations might help, which will slow \TeX{}
+down.
+
+Second, one can select a language for which no hyphenation patterns
+exist. Some distributions create a language \texttt{nohyphenation},
+and the \Package{hyphenat} package uses this technique for its
+\csx{nohyphens} command which sets its argument without any
+hyphenation. You can load \Package{hyphenat} with the command
+\begin{quote}
+ \cmdinvoke{usepackage}[none]{hyphenat}
+\end{quote}
+to prevent any hyphenation in a single-language document. The
+technique cannot work in a document in which \Package{babel} controls
+language selection, since \Package{babel} incorporates hyphenation
+change into its language change facilities.
+
+Third, one can set \csx{left-} and/or \csx{righthyphenmin} to a
+sufficiently large value that no hyphenation could possibly succeed,
+since the minimum is larger than the length of the longest word
+\TeX{} is willing to hyphenate (the appropriate value is 62).
+
+Fourth, one can suppress hyphenation for all text using the current
+font by the command
+\begin{quote}
+\begin{verbatim}
+\hyphenchar\font=-1
+\end{verbatim}
+\end{quote}
+This isn't a particularly practical way for users to suppress
+hyphenation~--- the command has to be issued for every font the
+document uses~--- but it's how \LaTeX{} itself suppresses hyphenation
+in \texttt{tt} and other fixed-width fonts.
+
+Which of the techniques you should use depends on what you actually
+want to do. If the text whose hyphenation is to be suppressed runs
+for less than a paragraph, your only choice is the no-hyphens
+language: the language value is preserved along with the text (in the
+same way that the current font is); the values for penalties and
+hyphen minima active at the end of a paragraph are used when
+hyphenation is calculated.
+
+Contrariwise, if you are writing a multilanguage document using the
+\Package{babel} package, you \emph{cannot} suppress hyphenation
+throughout using either the no-hyphens language or the hyphen minima:
+all those values get changed at a \Package{babel} language switch: use
+the penalties instead.
+
+If you simply switch off hyphenation for a good bit of text, the
+output will have a jagged edge (with many lines seriously overfull),
+and your \AllTeX{} run will bombard you with warnings about overfull
+and underfull boxes (that is, really, lines). To avoid this you have
+two options.
+
+The simplest route is to use \csx{sloppy} (or its environment version
+\environment{sloppypar}), and have \TeX{} stretch what would otherwise
+be underfull lines to fill the space offered, while prematurely
+wrapping overfull lines and stretching the remainder.
+
+The better bet is to set the text \Qref*{ragged right}{Q-ragright},
+and at least get rid of the overfull lines; this technique is
+`traditional' (in the sense that typists have always done it) and may
+be expected to
+appeal to the specifiers of eccentric document layouts (such as those
+for dissertations), but for once their sense conforms with typographic
+style. (Or at least, style constrained in this curious way.)
+\begin{ctanrefs}
+\item[hyphenat.sty]\CTANref{hyphenat}
+\end{ctanrefs}
+\LastEdit{2013-09-20}
+
+\Question[Q-wdnohyph]{Preventing hyphenation of a particular word}
+
+It's quite possible for (\emph{any}) hyphenation of a particular word
+to seem ``completely wrong'', so that you want to prevent it being
+hyphenated.
+
+If the word occurs in just one place, put it in a box:
+\begin{quote}
+\begin{verbatim}
+\mbox{oddword}
+\end{verbatim}
+\end{quote}
+(\plaintex{} users should use \csx{hbox}, and take care at the start
+of paragraphs.) However, boxing the word is not really advisable
+unless you are sure it only occurs once.
+
+If the word occurs commonly, the best choice is to assert an
+hyphenation exception for it:
+\begin{quote}
+\begin{verbatim}
+\hyphenation{oddword}
+\end{verbatim}
+\end{quote}
+This hyphenation exception (with no break points) will be used in
+preference to what \TeX{}'s hyphenation algorithm may come up with.
+
+In a multilingual document, repeat the exception specification for
+each language the word may appear in. So:
+\begin{quote}
+\begin{verbatim}
+\usepackage[french,english]{babel}
+\selectlanguage{english}
+\hyphenation{oddword}
+\selectlanguage{french}
+\hyphenation{oddword}
+\end{verbatim}
+\end{quote}
+(note that \Package{babel} will select the default language for the
+document~--- English, in this case~--- at \cmdinvoke{begin}{document}.)
+
+A particular instance of this requirement is avoiding the hyphenation
+of acronyms; a general rule for those that concoct acronyms seems to
+be to make the capital-letter sequence read as near as is possible
+like a ``real'' word, but hyphenating an acronym often looks silly.
+The \TeX{} control \csx{uchyph} is designed for suppressing such
+behaviour:
+\begin{quote}
+\begin{verbatim}
+\uchyph=0
+\end{verbatim}
+\end{quote}
+will stop hyphenation of upper-case words. (Note that \plaintex{}
+syntax is needed here: there's no \LaTeX{} alternative for setting
+this value.)
+
+\Question[Q-hyphexcept]{Hyphenation exceptions}
+
+While \TeX{}'s hyphenation rules are good, they're not infallible: you
+will occasionally find words \TeX{} just gets \emph{wrong}. So for
+example, \TeX{}'s default hyphenation rules (for American English) don't
+know the word ``\emph{manuscript}'', and since it's a long word you
+may find you need to hyphenate it. You \emph{can} ``write the
+hyphenation out'' each time you use the word:
+\begin{quote}
+\begin{verbatim}
+... man\-u\-script ...
+\end{verbatim}
+\end{quote}
+Here, each of the \csx{-} commands is converted to a hyphenated break,
+if (\emph{and only if}) necessary.
+
+That technique can rapidly become tedious: you'll probably only accept
+it if there are no more than one or two wrongly-hyphenated words in
+your document. The alternative is to set up hyphenations in the
+document preamble. To do that, for the hyphenation above, you would
+write:
+\begin{quote}
+\begin{verbatim}
+\hyphenation{man-u-script}
+\end{verbatim}
+\end{quote}
+and the hyphenation would be set for the whole document. Barbara
+Beeton publishes articles containing lists of these ``hyphenation
+exceptions'', in \textsl{TUGboat}; the hyphenation `man-u-script'
+comes from one of those articles.
+
+What if you have more than one language in your document? Simple:
+select the appropriate language, and do the same as above:
+\begin{quote}
+\begin{verbatim}
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{re-cher-cher}
+\end{verbatim}
+\end{quote}
+(nothing clever here: this is the ``correct'' hyphenation of the word,
+in the current tables). However, there's a problem here: just as
+words with accent macros in them won't break, so an \csx{hyphenation}
+commands with accent macros in its argument will produce an error:
+\begin{quote}
+\begin{verbatim}
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{r\'e-f\'e-rence}
+\end{verbatim}
+\end{quote}
+tells us that the hyphenation is ``improper'', and that it will be ``flushed''.
+But, just as hyphenation of words is enabled by selecting an 8-bit
+font encoding, so \csx{hyphenation} commands are rendered proper again
+by selecting that same 8-bit font encoding. For the hyphenation
+patterns provided for `legacy', the encoding is
+\Qref*{Cork}{Q-ECfonts}, so the complete sequence is:
+\begin{quote}
+\begin{verbatim}
+\usepackage[T1]{fontenc}
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{r\'e-f\'e-rence}
+\end{verbatim}
+\end{quote}
+The same sort of performance goes for any language for which 8-bit
+fonts and corresponding hyphenation patterns are available. Since you
+have to select both the language and the font encoding to have your
+document typeset correctly, it should not be a great imposition to do
+the selections before setting up hyphenation exceptions.
+
+Modern TeX variants (principally \xetex{} and \luatex{}) use unicode,
+internally, and distributions that offer them also offer
+\acro{UTF}-8-encoded patterns; since the hyphenation team do all the
+work ``behind the scenes'', the use of Unicode hyphenation is
+deceptively similar to what we are used to.
+\LastEdit{2013-09-20}
+
+\subsection{Odds and ends}
+
+\Question[Q-logos]{Typesetting all those \TeX{}-related logos}
+
+Knuth was making a particular point about the capabilities of \TeX{}
+when he defined the logo. Unfortunately (in some people's opinion) he thereby
+opened floodgates to give the world a whole range of rather silly
+`bumpy road' logos for \TeX{} entities such as \AMSTeX{}, \pictex{},
+\BibTeX{}, and so on, produced in a flurry of different fonts, sizes,
+and baselines~--- indeed, everything one might hope to cause them to
+obstruct the reading process. In particular, Lamport invented
+\LaTeX{} (silly enough in itself, with a raised small `A' and a
+lowered `E') and marketing input from Addison-Wesley led to the even
+stranger current logo for \LaTeXe{}, which appends a lowered % !line break
+\latexhtml{\ensuremath{\varepsilon}}{single-stroke Greek letter &epsilon;}.
+
+Sensible users don't have to follow this stuff wherever it goes,
+but, for those who insist, a large collection of logos is defined in
+the \Package{texnames} package (but note that this set of macros isn't
+entirely reliable in \LaTeXe{}).
+The \MF{} and \MP{} logos can be set in fonts that \LaTeXe{}
+knows about (so that they scale with the surrounding text) using the
+\Package{mflogo} package; but be aware that booby-traps surround the
+use of the Knuthian font for \MP{} (you might get
+\begin{typesetversion}
+ \textlogo{META\hphantom{P}O\hphantom{S}T}).
+\end{typesetversion}
+% the following htmlversion stuff seems to do roughly what's required,
+% which is nice, given the feebleness of representing all these silly
+% logos in html otherwise...
+\begin{htmlversion}
+ something like `META\&nbsp;\&nbsp;O\&nbsp;\&nbsp;T').
+\end{htmlversion}
+You needn't despair, however~--- most versions of the logo font
+distributed nowadays contain the missing letters, and the author
+himself uses just `MetaPost'.
+
+A well-designed set of macros is provided by package \Package{hologo},
+which defines a command \csx{hologo}, which one uses as (for example)
+\cmdinvoke{hologo}{pdfLaTeX} for what you might get by typing
+``\texttt{pdf}\csx{LaTeX}'', as well as a capitalised version
+\cmdinvoke{Hologo}{pdfLaTeX} for ``\texttt{Pdf}\csx{LaTeX}''.
+
+The package \Package{metalogo} deals with a problem of these myriad
+logos, that's often ignored nowadays: the geometry of characters from
+different fonts is (obviously) different, and they naturally fit
+together differently. The package makes it possible for you to adjust
+the spacing between the the letters of one of these odd logos (even
+the especially weird mirrored ``E'' in \xetex{}).
+
+For those who don't wish to acquire the `proper' logos, the canonical
+thing to do is to say \texttt{AMS-}\cmdinvoke{TeX}{}
+for \AMSTeX{}, \texttt{Pic}\cmdinvoke{TeX}{}
+for \pictex{}, \texttt{Bib}\cmdinvoke{TeX}{}
+for \BibTeX{}, and so on.
+\begin{ctanrefs}
+\item[hologo.sty]Distributed as part of \CTANref{oberdiek}[hologo]
+\item[metalogo.sty]\CTANref{metalogo}
+\item[mflogo.sty]\CTANref{mflogo}
+\item[texnames.sty]\CTANref{texnames}
+\end{ctanrefs}
+\LastEdit{2010-03-24}
+
+\Question[Q-bold-extras]{How to do bold-tt or bold-sc}
+
+\LaTeX{}, as delivered, offers no means of handling bold ``teletype''
+or small-caps fonts. There's a practical reason for this (Knuth never
+designed such fonts), but there are typographical considerations too
+(the ``medium weight'' \texttt{cmtt} font is already pretty bold (by
+comparison with other fixed-width fonts), and bold small-caps is not
+popular with many professional typographers).
+
+There's a set of ``extra'' \MF{} files on \acro{CTAN} that provide bold
+versions of both \texttt{cmtt} and \texttt{cmcsc} (the small caps font). With
+modern \TeX{} distributions, one may bring these fonts into use simply
+by placing them in an % ! line break
+\Qref*{appropriate place in the \emph{texmf} tree}{Q-install-where}
+(these are \AllTeX{}-specific files, so the ``\emph{public}'' supplier
+would be an appropriate place). Once you've % ! line break, again
+\Qref*{rebuilt the file indexes as necessary}{Q-inst-wlcf},
+\TeX{} (and friends) will automatically build whatever font files they
+need when you first make reference to them. There's a jiffy package
+\Package{bold-extra} that builds the necessary font data structures
+so that you can use the fonts within \LaTeX{}.
+
+Another alternative is to use the \Qref*{\acro{EC} fonts}{Q-ECfonts},
+which come with bold variants of the small-caps fonts.
+
+If you need to use Type~1 fonts, you can't proceed with Knuth-style
+fonts, since there are no Type~1 versions of the \Package{mf-extra}
+set. There are, however, Type~1 distributions of the EC~fonts, so you
+can switch to EC and use them; alternatives are discussed in
+\Qref[question]{8-bit Type~1 fonts}{Q-type1T1}.
+
+Of course, commercial fixed-width fonts (even the default
+\FontName{Courier}) almost always come with a bold variant, so that's
+not a problem. Furthermore \Qref*{\acro{PSNFSS}}{Q-usepsfont}
+will usually provide ``faked'' small caps fonts, and has no
+compunctions about providing them in a bold form. \FontName{Courier}
+is (as we all know, to our cost) freely available; a far more
+presentable monospace font is \FontName{LuxiMono}, which is also
+freely available (monospace text in the typeset version of this
+\acro{FAQ} uses \FontName{LuxiMono}, with the metrics and \LaTeX{}
+support available on the archive.
+\begin{ctanrefs}
+\item[bold-extra.sty]\CTANref{bold-extra}
+\item[bold tt and small caps fonts]\CTANref{bold}
+\item[\nothtml{\rmfamily}LuxiMono fonts]\CTANref{luximono}
+\end{ctanrefs}
+
+\Question[Q-varwidth]{Automatic sizing of \environment{minipage}}
+
+The \environment{minipage} environment requires you to specify the
+width of the ``page'' you're going to create. This is sometimes
+inconvenient: you would like to occupy less space, if possible, but
+\environment{minipage} sets a box that is exactly the width you
+specified.
+
+The \Package{pbox} package defines a \csx{pbox} whose width is exactly
+that of the longest enclosed line, subject to a maximum width that you
+give it. So while \cmdinvoke{parbox}{2cm}{Hello\bsbs world!} produces a
+box of width exactly \texttt{2cm},
+\cmdinvoke{pbox}{2cm}{Hello\bsbs world!} produces one whose width is
+\texttt{1.79cm} (if one's using the default \FontName{cmr} font for the
+text, at least). The package also provides a
+\cmdinvoke*{settominwidth}[min]{length}{text} (which looks (almost)
+like the standard \csx{settowidth} command), and a \csx{widthofpbox}
+function analogous to the \csx{widthof} command for use with the
+\Package{calc} package.
+
+The \Package{eqparbox} package extends \Package{pbox}'s idea, by
+allowing you to set a series of boxes, all with the same (minimised)
+width. (Note that it doesn't accept a limiting maximum width
+parameter.) The package documentation shows the following example
+drawn from a joke \emph{curriculum vitae}:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\noindent%
+\eqparbox{place}%
+ {\textbf{Widgets, Inc.}}
+ \hfill
+\eqparbox{title}%
+ {\textbf{Senior Widget Designer}}
+ \hfill
+\eqparbox{dates}{\textbf{1/95--present}}
+
+...
+
+\noindent%
+\eqparbox{place}%
+ {\textbf{Thingamabobs, Ltd.}}
+ \hfill
+\eqparbox{title}%
+ {\textbf{Lead Engineer}}
+ \hfill
+\eqparbox{dates}{\textbf{9/92--12/94}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\noindent%
+\eqparbox{place}{\textbf{Widgets, Inc.}} \hfill
+\eqparbox{title}{\textbf{Senior Widget Designer}} \hfill
+\eqparbox{dates}{\textbf{1/95--present}}
+
+...
+
+\noindent%
+\eqparbox{place}{\textbf{Thingamabobs, Ltd.}} \hfill
+\eqparbox{title}{\textbf{Lead Engineer}} \hfill
+\eqparbox{dates}{\textbf{9/92--12/94}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+The code makes the three items on each of the heading lines have
+exactly the same width, so that the lines as a whole produce a regular
+pattern down the page. A command \csx{eqboxwidth} allows you to use
+the measured width of a group: the documentation shows how the command
+may be used to produce sensible-looking columns that mix \texttt{c}-,
+\texttt{r}- or \texttt{l}-rows, with the equivalent of a |p{...}|
+entry, by making the fixed-width rows an \Package{eqparbox} group, and
+making the last from a \csx{parbox} using the width that's been
+measured for the group.
+
+The \Package{varwidth} package defines a \environment{varwidth}
+environment which sets the content of the box to match a ``narrower
+natural width'' if it finds one. (You give it the same parameters as
+you would give \environment{minipage}: in effect, it is a `drop-in'
+replacement.) \Package{Varwidth} provides its own ragged text command:
+\csx{narrowragged}, which aims to make narrower lines and to put more
+text in the last line of the paragraph (thus producing lines with more
+nearly equal lengths than typically happens with \csx{raggedright}
+itself).
+
+The documentation (in the package file) lists various restrictions and
+things still to be done, but the package is already proving useful for
+a variety of jobs.
+\begin{ctanrefs}
+\item[eqparbox.sty]\CTANref{eqparbox}
+\item[pbox.sty]\CTANref{pbox}
+\item[varwidth.sty]\CTANref{varwidth}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-hyp+pdf.tex b/help/uk-tex-faq/faq-hyp+pdf.tex
new file mode 100644
index 0000000000..aa670393d9
--- /dev/null
+++ b/help/uk-tex-faq/faq-hyp+pdf.tex
@@ -0,0 +1,636 @@
+% $Id: faq-hyp+pdf.tex,v 1.8 2014/02/16 21:23:58 rf10 Exp $
+
+\section{Hypertext and \acro{PDF}}
+
+\Question[Q-acrobat]{Making \acro{PDF} documents from \AllTeX{}}
+
+There are three general routes to \acro{PDF} output: Adobe's original
+`distillation' route (via \PS{} output), direct conversion of a
+\acro{DVI} file, and the use of a direct \tex{}-like \acro{PDF}
+generator such as \Qref*{\PDFTeX{}}{Q-whatpdftex}.
+
+For simple documents (with no hyper-references), you can either
+\begin{itemize}
+\item process the document in the normal way, produce \PS{}
+ output and distill it;
+\item (on a Windows or Macintosh machine with appropriate
+ tools installed) pass the output through a \acro{PDF}writer in place
+ of a printer driver. This route is only appropriate for simple
+ documents: \acro{PDF} writers cannot create hyperlinks;
+\item process the document with ``vanilla'' \latex{} and generate \acro{PDF}
+ direct from the \acro{DVI} using \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or
+\item process the document direct to \acro{PDF} with \PDFTeX{},
+ \Qref{\luatex{}}{Q-luatex}, or \Qref{\xetex{}}{Q-xetex}.
+\end{itemize}
+
+To translate all the \LaTeX{} cross-referencing into Acrobat
+links, you need a \LaTeX{} package to redefine
+the internal commands. There are two of these for \LaTeX{}, both
+capable of conforming to the
+\Qref{Hyper\TeX{} specification}{Q-hyper}:
+Heiko Oberdiek's \Package{hyperref}, and Michael Mehlich's
+\Package{hyper}. (In practice, almost everyone uses
+\Package{hyperref}; \Package{hyper} hasn't been updated since 2000.)
+\Package{Hyperref} can often determine how it should generate
+hypertext from its environment, but there is a wide set of
+configuration options you can give via \csx{usepackage}. The package
+can operate using \PDFTeX{} primitives, the hyper\TeX{}
+\csx{special}s, or \acro{DVI} driver-specific \csx{special} commands.
+Both \ProgName{dvips} and \YandY{}'s \acro{\ProgName{DVIPSONE}} can
+translate the \acro{DVI} with these \csx{special} commands into
+\PS{} acceptable to Distiller, and
+\ProgName{dvipdfm} and \ProgName{dvipdfmx} have \csx{special} commands of
+their own.
+
+If you use \plaintex{}, the \Qref*{\Eplain{} macros}{Q-eplain} can
+help you create \acro{PDF} documents with hyper-references.
+It can operate using \PDFTeX{} primitives, or \csx{special} commands
+for the \ProgName{dvipdfm}/\ProgName{dvipdfmx} \acro{DVI} drivers.
+
+While there is no free implementation of all of \ProgName{Adobe}
+\ProgName{Distiller}'s
+functionality, any but the implausibly old versions of
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+provide pretty reliable distillation (but beware of the problems with
+\Qref*{\ProgName{dvips} output for distillation}{Q-dvips-pdf}).
+
+For viewing (and printing) the resulting files, Adobe's
+\ProgName{Acrobat} \ProgName{Reader} is available for a fair range of
+platforms; for those for which Adobe's reader is unavailable, remotely
+current versions of \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+combined with \ProgName{gv} or
+\href{http://www.ghostgum.com.au/}{\ProgName{gsview}} can display and
+print \acro{PDF} files, as can \ProgName{xpdf}.
+
+In some circumstances, a
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}-based viewer
+application is actually preferable to Acrobat Reader. For example, on
+Windows Acrobat Reader locks the \extension{pdf} file it's displaying: this
+makes the traditional (and highly effective) \AllTeX{} development
+cycle of ``Edit\arrowhyph{}Process\arrowhyph{}Preview'' become
+rather clumsy~--- \href{http://www.ghostgum.com.au/}{\ProgName{gsview}}
+doesn't make the same <mistake.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Acrobat Reader]download from \URL{http://get.adobe.com/reader}
+\item[dvipdfm]\CTANref{dvipdfm}
+\item[dvipdfmx]\CTANref{dvipdfmx}
+\item[gv]Browse \CTANref{gv}
+\item[hyper.sty]\CTANref{hyper}
+\item[hyperref.sty]\CTANref{hyperref}
+\end{ctanrefs}
+\LastEdit{2014-01-22}
+
+\Question[Q-hyper]{Making hypertext documents from \TeX{}}
+
+If you want on-line hypertext with a \AllTeX{} source, probably on the
+World Wide Web, there are four technologies to consider:
+\begin{itemize}
+\item start from \alltex{}, and use one of a number of techniques to
+ translate (more or less) directly to
+ \Qref{\acro{HTML}}{Q-LaTeX2HTML};
+% beware line break
+\item Start from \Qref*{\Package{texinfo}}{Q-texinfo} source,
+ and use the \ProgName{info} viewer, or convert the \Package{texinfo}
+ source to \acro{HTML} using \ProgName{texi2html};
+\item Start from \alltex{}; use \pdftex{}, \xetex{} or \luatex{} to
+ produce \acro{PDF}, using \Package{hyperref} to construct
+ hyperlinks.
+\item Start from (unconventional) \alltex{} which use the % ! line break
+ \Qref*{hyper\TeX{} conventions}{Q-hypertex}.
+\end{itemize}
+\begin{ctanrefs}
+\item[texinfo]\CTANref{texinfo}
+\end{ctanrefs}
+\LastEdit{2013-05-30}
+
+\Question[Q-hypertex]{The \emph{hyper\tex{}} project}
+
+The \emph{hyper\tex{}} project extended the functionality of all the
+\LaTeX{} cross-referencing commands (including the table of contents)
+to produce \csx{special} commands which are parsed by \acro{DVI} processors
+conforming to the Hyper\TeX{} guidelines;
+it provides general hypertext links, including those
+to external documents.
+
+The Hyper\TeX{} specification says that conformant viewers/translators
+must recognize the following set of \csx{special} commands:
+\begin{description}
+\item[href:] |html:<a href = "href_string">|
+\item[name:] |html:<a name = "name_string">|
+\item[end:] |html:</a>|
+\item[image:] |html:<img src = "href_string">|
+\item[base\_name:] |html:<base href = "href_string">|
+\end{description}
+
+The \emph{href}, \emph{name} and \emph{end} commands are used to do
+the basic hypertext operations of establishing links between sections
+of documents.
+
+Further details are available on \URL{http://arXiv.org/hypertex/}; there
+are two commonly-used implementations of the specification, a
+modified \ProgName{xdvi} and (recent releases of)
+\ProgName{dvips}. Output from the latter may be used in recent
+releases of \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+or Acrobat Distiller.
+
+\Question[Q-dvips-pdf]{Quality of \acro{PDF} from \PS{}}
+\keywords{blurry fuzzy crippled}
+
+Any reasonable \PS{}, including any output of \ProgName{dvips}, may be
+converted to \acro{PDF}, using (for example) a sufficiently recent
+version of \href{http://www.ghostscript.com/}{\ProgName{ghostscript}},
+Frank Siegert's (shareware)
+\href{http://www.pstill.com/}{\ProgName{PStill}}, or Adobe's (commercial)
+\ProgName{Distiller}.
+
+But, although the job may (almost always) be done, the results are
+often not acceptable: the most frequent problem is bad presentation of
+the character glyphs that make up the document. The following answers
+offer solutions to this (and other) problems of bad presentation.
+Issues covered are:
+\begin{itemize}
+\item \Qref*{Wrong type of fonts used}{Q-fuzzy-type3}, which is
+ the commonest cause of fuzzy text.
+\item \Qref*{\ProgName{Ghostscript} too old}{Q-fuzzy-gs},
+ which can also result in fuzzy text.
+% beware line breaks
+\item \Qref*{Switching to font encoding \acro{T}1 encoding}{Q-fuzzy-T1},
+ which is yet another possible cause of fuzzy text.
+\item Another problem~--- missing characters~--- arises from an
+ % beware line breaks
+ \Qref*{aged version of \ProgName{Adobe}~\ProgName{Distiller}}{Q-distill-prob}.
+\item Finally, there's the common confusion that arises from using the
+ \ProgName{dvips} configuration file \texttt{-Ppdf}, the % ! line br
+ \Qref*{weird characters}{Q-charshift}.
+\end{itemize}
+It should be noted that \ProgName{Adobe} % \ProgName{Acrobat} no longer
+ % part of the name
+\ProgName{Reader}~6 (released in mid-2003, and later versions) does
+not exhibit the ``fuzziness'' that so many of the answers below
+address. This is of course good news: however, it will inevitably be
+a long time before every user in the world has this (or later)
+versions, so the remedies below are going to remain for some time to
+come.
+
+The problems are also discussed, with practical examples, in Mike
+Shell's \Package{testflow} package, which these FAQs recommend as a
+``\Qref*{specialised tutorial}{Q-tutbitslatex}.
+\begin{ctanrefs}
+\item[testflow]\CTANref{testflow}
+\end{ctanrefs}
+
+
+\Question[Q-fuzzy-type3]{The wrong type of fonts in \acro{PDF}}
+\keywords{crippled blurry}
+
+This is far the commonest problem: the symptom is that text in the
+document looks ``fuzzy''.
+
+Most people use \ProgName{Adobe} \ProgName{Acrobat} \ProgName{Reader}
+to view their \acro{PDF}: \ProgName{Reader} is distributed free of
+charge, and is widely available, for all its faults. One of those
+faults is its failure to deal with bitmap fonts (at least, in all
+versions earlier than version~6, all of which copies are pretty old,
+now~\dots{} but some are occasionally found).
+
+So we don't want bitmap fonts in our \PS{}: with them, characters show
+up in \ProgName{Reader}'s display as blurred blobs which are often not
+even recognisable as the original letter, and are often not properly placed
+on the line. Nevertheless, even now, most \TeX{} systems have
+\ProgName{dvips} configured to use
+\Qref*{\extension{pk} files}{Q-pk} in its output. Even
+\PDFTeX{} will use \extension{pk} files if it can see no alternative for
+a font in the document it is processing.
+
+Our remedy is to use
+``\Qref*{Adobe Type~1}{Q-adobetypen}''
+versions of the fonts we need. Since Adobe are in the
+business of selling Type~1 fonts, \ProgName{Reader} was of course made
+to deal with them really rather well, from the very beginning.
+
+Of course, if your document uses nothing but fonts that came from
+Adobe in the first place~--- fonts such as \FontName{Times} that
+appear in pretty much every \PS{} printer, or such as Adobe
+\FontName{Sabon} that you pay extra for~--- then there's no problem.
+
+But most people use \FontName{Computer} \FontName{Modern} to start
+with, and even those relative sophisticates who use something as
+exotic as \ProgName{Sabon} often find themselves using odd characters
+from \acro{CM} without really intending to do so. Fortunately, rather
+good versions of the \acro{CM} fonts are available from the \acro{AMS}
+(who have them courtesy of % ! line break
+\Qref{Blue Sky Research}{Q-commercial} and \YandY{}).
+
+Most modern systems have the fonts installed ready to use; and any
+system installed less than 3~years ago has a \ProgName{dvips}
+configuration file `\texttt{pdf}' that signals the use of the
+\acro{CM} fonts, and also sets a few other parameters to improve
+\ProgName{dvips}' output. Use this configuration as:
+\begin{quote}
+\begin{verbatim}
+dvips -Ppdf myfile -o myfile.ps
+\end{verbatim}
+\end{quote}
+This may produce a warning message about failing to find the
+configuration file:
+\begin{quote}
+\begin{verbatim}
+dvips: warning: no config file for `pdf'
+\end{verbatim}
+\end{quote}
+or something similar, or about failing to find a font file:
+\begin{quote}
+\begin{verbatim}
+dvips: ! Couldn't find header file cmr10.pfb
+\end{verbatim}
+\end{quote}
+Either of these failures signals that your
+system doesn't have the fonts in the first place.
+
+A way of using the fonts that doesn't involve the sophistication of
+the \texttt{-Ppdf} mechanism is simply to load maps:
+\begin{quote}
+\begin{verbatim}
+dvips -Pcmz -Pamz myfile -o myfile.ps
+\end{verbatim}
+\end{quote}
+You may encounter the same warning messages as listed above.
+
+If your system does not have the fonts, it won't have the
+configuration file either; however, it might have the configuration
+file without the fonts. In either case, you need to
+\Qref*{install the fonts}{Q-inst1cm}.
+
+
+\Question[Q-fuzzy-gs]{Fuzzy fonts because \ProgName{Ghostscript} too old}
+\keywords{crippled blurry}
+
+So you've done everything the \acro{FAQ} has told you that you need,
+correct fonts properly installed and appearing in the \ProgName{dvips}
+output, but \emph{still} you get fuzzy character output after
+distilling with \href{http://www.ghostscript.com/}{\ProgName{ghostscript}}.
+
+The problem could arise from too old a version of
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}, which you
+may be using directly, or via a
+script such as \ProgName{ps2pdf} (distributed with
+\ProgName{ghostscript} itself), \ProgName{dvipdf}, or similar.
+Though \ProgName{ghostscript} was capable of distillation from
+version~5.50, that version could only produce bitmap Type~3 output of
+any font other than the fundamental 35~fonts (\FontName{Times},
+\FontName{Helvetica}, etc.). Later versions added `complete'
+distillation, but it wasn't until version~6.50 that one could rely on
+it for everyday work.
+
+So, if your \acro{PDF} output still looks fuzzy in \ProgName{Acrobat}
+\ProgName{Reader}, upgrade \ProgName{ghostscript}. The new version
+should be at least version~6.50, of course, but it's usually good
+policy to go to the most recent version (version~8.12 at the time of
+writing~--- 2003).
+
+\Question[Q-fuzzy-T1]{Fonts go fuzzy when you switch to \acro{T}1}
+\keywords{crippled blurry}
+
+You've been having problems with hyphenation, and someone has
+suggested that you should use ``\cmdinvoke{usepackage}[T1]{fontenc}''
+to help sort them out. Suddenly you find that your final \acro{PDF}
+has become fuzzy. The problem may arise whether you are using \PS{}
+output and then distilling it, or you are using \PDFTeX{} for the
+whole job.
+
+In fact, this is the same problem as most others about the
+\Qref*{quality of \acro{PDF}}{Q-dvips-pdf}: you've abandoned
+your previous setup using Type~1 versions of the \acro{CM} fonts, and
+\ProgName{dvips} has inserted Type~3 versions of the \acro{EC} fonts
+into your document output. (See % beware line break
+``\Qref*{Adobe font types}{Q-adobetypen}
+for details of these font types; also, note that the font
+\emph{encoding}~\acro{T}1
+has nothing directly to do with the font \emph{format}~Type~1).
+
+However, as noted in % beware line break
+\htmlonly{``}\Qref[question]{8-bit Type~1 fonts}{Q-type1T1}\htmlonly{''},
+Type~1 versions of \acro{CM}-like fonts in \acro{T}1 (or equivalent) encoding
+are now available, both as ``real'' fonts, and as virtual font sets.
+One solution, therefore, is to use one of these alternatives.
+
+The alternative is to switch font family altogether, to something like
+\FontName{Times} (as a no-thought default) or one of the many more pleasing
+Adobe-encoded fonts. The default action of \Package{fontinst}, when
+creating metrics for such a font, is to create settings for both \acro{OT}1
+and \acro{T}1 encodings, so there's little change in what goes on (at the
+user level) even if you have switched to \acro{T}1~encoding when using the
+fonts.
+
+\Question[Q-distill-prob]{Characters missing from \acro{PDF} output}
+
+If you're using \ProgName{Acrobat} \ProgName{Distiller} to create your
+\acro{PDF} output, you may find
+characters missing. This may manifest
+itself as messed-up maths equations (missing
+``\latexhtml{\ensuremath{-}}{-}'' signs, for example), or bits missing
+from large symbols. Early versions of \ProgName{Distiller} used to
+ignore character positions 0--31 and 128--159 of every font: Adobe's
+fonts never use such positions, so why should \ProgName{Distiller}?
+
+Well, the answer to this question is ``because Adobe don't produce all
+the world's fonts''~--- fonts like \FontName{Computer}
+\FontName{Modern} were around before Adobe came on the scene, and
+\emph{they} use positions 0--31. Adobe don't react to complaints like
+that in the previous sentence, but they do release new versions of
+their programs; and \ProgName{Distiller}, since at least version~4.0,
+\emph{has} recognised the font positions it used to shun.
+
+Meanwhile, \TeX{} users with old versions of \ProgName{Distiller} need
+to deal with their fonts. \ProgName{Dvips} comes to our aid: the
+switch \texttt{-G1} (``remap characters''), which moves the offending
+characters out of the way. The \acro{PDF} configuration file
+(\texttt{-Ppdf}), recommended % beware line break
+\latexhtml{above}{in ``\Qref{the wrong type of fonts}{Q-fuzzy-type3}''},
+includes the switch.
+
+The switch is not without its problems; pre-2003 versions of
+\ProgName{dvips} will apply it to Adobe fonts as well, causing
+\Qref*{havoc}{Q-charshift}, but fortunately
+that problem is usually soluble. However, a document using both
+\acro{CM} and Adobe-specified fonts is stuck. The only real solution
+is either to upgrade \ProgName{dvips}, or to spend money to upgrade
+\ProgName{Distiller}.
+
+\Question[Q-type1T1]{Finding `8-bit' Type~1 fonts}
+\keywords{eight}
+
+Elsewhere, answers to these \acro{FAQ}s recommend that you use an
+`8-bit' font to permit % line break!!
+\Qref*{accentuation of inflected languages}{Q-hyphenaccents},
+and also recommend the use of Type~1 fonts to ensure that
+you get \Qref*{good quality \acro{PDF}}{Q-fuzzy-type3}. These
+recommendations used to be contradictory: one could not just
+``switch'' from the free \acro{CM} fonts to free Cork- (or similarly)
+encoded Type~1 fonts. The first approach that started to alleviate
+these problems, was the development of virtual fonts that make
+a good approach to the Cork encoding (see below). Now, however, we
+have ``true'' Type~1 fonts available: as always, we have an
+embarrassment of riches with three free alternatives, and one
+commercial and one shareware version.
+
+\Package{CM-super} is an
+auto-traced set which encompasses all of the \acro{T}1 and \acro{TS}1
+encodings as well as the \acro{T}2* series (the family of encodings
+that cover languages based on Cyrillic alphabets). These fonts are
+pretty easy to install (the installation instructions are clear), but
+they are huge: don't try to install them if you're short of disc
+space.
+
+\Package{CM-LGC} is a similar ``super-font'' set, but of much more
+modest size; it covers \acro{T}1, \acro{TS}1 and \acro{T}2{A}
+encodings (as does \Package{CM-super}, and also covers the \acro{LGR}
+encoding (for typesetting Greek, based on Claudio Beccari's \MF{}
+sources). \Package{CM-LGC} manages to be small by going to the
+opposite extreme from \Package{CM-super}, which includes fonts at all
+the sizes supported by the original \acro{EC} (a huge range);
+\Package{CM-LGC} has one font per font shape, getting other sizes by
+scaling. There is an inevitable loss of quality inherent in this
+approach, but for the disc-space-challenged machine, \Package{CM-LGC}
+is an obvious choice.
+
+\Package{Tt2001} is a simple scan of the \acro{EC} and \acro{TC}
+fonts, and has some virtues~--- it's noticeably smaller than
+\Package{CM-super} while being less stark than \Package{CM-LGC}.
+
+\Package{Latin} \Package{Modern} is produced using the
+program \Qref*{\ProgName{MetaType1}}{Q-textrace}. The
+\Package{Latin} \Package{Modern} set comes with \acro{T}1, \acro{TS}1
+\acro{LY}1 encoded variants (as well as a variant using the Polish
+\acro{QX} encoding); for the glyph set it covers, its outlines seem
+rather cleaner than those of \Package{CM-super}. \Package{Latin}
+\Package{Modern} is more modest in its disc space demands than is
+\Package{CM-super}, while not being nearly as stark in its range of
+design sizes as is \Package{CM-LGC}~--- \Package{Latin}
+\Package{Modern}'s fonts are offered in the same set of sizes as the
+original \Package{CM} fonts. It's hard to argue with the choice:
+Knuth's range of sizes has stood the test of time, and is one of the
+bases on which the excellence of the \TeX{} system rests.
+
+\Qref*{Virtual fonts}{Q-virtualfonts} help us deal with the problem,
+since they allow us to map ``bits of \acro{DVI} file'' to single
+characters in the virtual font; so we can create an ``\'e'' character
+by recreating the \acro{DVI} commands that would result from the code
+``\csx{'}\texttt{e}''. However, since this involves two characters being
+selected from a font, the arrangement is sufficient to fool
+\ProgName{Acrobat} \ProgName{Reader}: you can't use the program's
+facilities for searching for text that contains inflected characters,
+and if you \emph{cut} text from a window that contains such a
+character, you'll find something unexpected (typically the accent and
+the `base' characters separated by a space) when you \ProgName{paste}
+the result. However, if you can live with this difficulty, virtual
+fonts are a useful and straightforward solution to the problem.
+
+There are two virtual-font offerings of \acro{CM}-based 8-bit
+fonts~--- the \Package{ae} (``almost \acro{EC}'') and
+\Package{zefonts} sets; the \Package{zefonts} set has wider coverage
+(though the \Package{ae} set may be extended to offer guillemets by
+use of the \Package{aeguill} package). Neither offers characters such
+as \texttt{eth} and \texttt{thorn} (used in, for example, in
+Icelandic), but the \Package{aecompl} package works with the
+\Package{ae} fonts to provide the missing characters from the
+\acro{EC} fonts (i.e., as bitmaps).
+
+The sole remaining commercial \acro{CM}-like 8-bit font comes from
+Micropress, who offer the complete \acro{EC} set
+in Type~1 format, as part of their range of outline versions of fonts
+that were originally distributed in \MF{} format. See
+\Qref[question]{``commercial distributions''}{Q-commercial}.
+
+The shareware % ! line break
+\Qref*{BaKoMa \TeX{} distribution}{Q-TeXsystems} offers a
+set of Type~1 \acro{EC} fonts, as an extra shareware option. (As far
+as the present author can tell, these fonts are \emph{only} available
+to users of BaKoMa \TeX{}: they are stored in an archive format that
+seems not to be publicly available.)
+
+Finally, you can use one of the myriad text fonts available in Type~1
+format (with appropriate \acro{PSNFSS} metrics for \acro{T}1 encoding,
+or metrics for some other 8-bit encoding such as \acro{LY}1). However,
+if you use someone else's text font (even something as simple as
+Adobe's Times family) you have to find a matching family of
+mathematical fonts, which is a non-trivial undertaking~---
+\htmlonly{see }\Qref{``choice of scalable fonts''}{Q-psfchoice}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}ae fonts]\CTANref{ae}
+\item[aecompl.sty]Distributed with \CTANref{ae}
+\item[aeguill.sty]\CTANref{aeguill}
+\item[\nothtml{\rmfamily}BaKoMa fonts]Browse \CTANref{bakoma-texfonts}
+\item[\nothtml{\rmfamily}CM-LGC fonts]\CTANref{cm-lgc}
+\item[\nothtml{\rmfamily}CM-super fonts]\CTANref{cm-super} (beware:
+ very large download)
+\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm}
+\item[\nothtml{\rmfamily}tt2001 fonts]\CTANref{tt2001}
+\item[\nothtml{\rmfamily}zefonts]\CTANref{zefonts}
+\end{ctanrefs}
+
+\Question[Q-pkfix]{Replacing Type 3 fonts in \PS{}}
+
+One often comes across a \PS{} file generated by
+\ProgName{dvips} which contains embedded \acro{PK} fonts; if you try
+to generate \acro{PDF} from such a file, the quality will be poor.
+
+Of course, the proper solution is to regenerate the \PS{} file,
+but if neither the sources nor the \acro{DVI} file are available, one
+must needs resort to some sort of patching to replace the bitmap fonts
+in the file by outline fonts.
+
+The program \ProgName{pkfix} (by Heiko Oberdiek) will do this
+patching, for files created by ``not too old versions'' of
+\ProgName{dvips}: it finds the fonts to be replaced by examining the
+\PS{} comments \ProgName{dvips} has put in the file. For each
+font, \ProgName{pkfix} puts appropriate \TeX{} commands in a file,
+which it then processes and runs through \ProgName{dvips} (with switch
+\texttt{-Ppdf}) to acquire an appropriate copy of the font; these copies are
+then patched back into the original file.
+
+If your source file is older than \ProgName{pkfix} can deal with,
+there's still a modicum of hope: \ProgName{pkfix-helper} examines the
+bitmap fonts in a document, compares them with the metric
+(\extension{tfm}) fonts on your system and comes to a view of which
+font might be which. The program reports on ``poor'' matches, and
+there are options for confirming, or replacing, its guesses. The
+technique (which sounds implausible) is successful enough to be worth
+a try.
+
+A further option is Frank Siegert's (shareware)
+\href{http://www.pstill.com}{PStill}, which is capable of processing
+the \PS{} it is distilling, and one option is to replace bitmap fonts
+in the file with Type~1 versions.
+\begin{ctanrefs}
+\item[pkfix]\CTANref{pkfix}
+\item[pkfix-helper]\CTANref{pkfix-helper}
+\end{ctanrefs}
+
+\Question[Q-pdfpagelabels]{\Package{Hyperref} and repeated page numbers}
+
+The \Class{book} class (and its friends and relations) automatically
+changes the display of page numbers in the frontmatter of the document
+to lower-case roman. This is fine for human readers, but if
+\Package{hyperref} has been misconfigured, the existence of pages have
+the same page number can cause problems. Fortunately, the
+configuration options to make \Package{hyperref} ``do the right
+thing'' are (by default) set up to avoid problems.
+
+The two options in question are:
+\begin{description}
+\item[\pkgoption{plainpages=false}] Make page anchors using the
+ formatted form of the page number. With this option,
+ \Package{hyperref} writes different anchors for pages `ii' and `2'.
+ (This is the default value for the option, which is a % ! line break
+ \emph{good thing}\dots{})
+ If the option is set `\texttt{true}' \Package{hyperref} writes page
+ anchors as the arabic form of the page number, rather than the
+ formatted form that gets printed; this is not usually appropriate.
+\item[\pkgoption{pdfpagelabels}] Set \acro{PDF} page labels; i.e.,
+ write the value of \csx{thepage} to the \acro{PDF} file so that
+ \Package{Acrobat Reader} can display the page number as (say) `ii (4
+ of 40)' rather than simply `4 of 40'.
+\end{description}
+The two should be used whenever page numbering is not just
+`1\texttt{..}\ensuremath{n}'; they may be used independently, but
+usually are not.
+
+The recipe isn't perfect: it relies on \csx{thepage} being different
+for every page in the document. A common problem arises when there is
+an unnumbered title page, after which page numbers are reset: the
+\PDFTeX{} warning of ``\Qref*{duplicate destinations}{Q-hyperdupdest}''
+will happen in this case, regardless of the options.
+\begin{ctanrefs}
+\item[hyperref.sty]\CTANref{hyperref}
+\end{ctanrefs}
+
+\Question[Q-cpy-srchpdf]{Copy-paste-able/searchable \acro{PDF} files}
+
+\acro{PDF} files generated from \tex{} (and friends), will by default
+hold their text in the encoding of the original \tex{} font used by
+the document.
+
+When \acro{PDF} readers, etc., offer copy-paste or searching
+functions, the operations take place on the glyph codes used for the
+fonts selected by the document. This is fine, for the simplest
+documents (in English, at least); the problem comes when you're using
+an inflected language (with accented letters, or composite glyphs
+such as `\ae{}')~--- \tex{} will typically use a non-standard
+encoding, and there are likely be problems, since \acro{PDF} readers
+assume the text is presented in Unicode.
+
+For \acro{PDF} generated from \latex{} (the \acro{DVI} being
+converted, by whatever means), or from \pdflatex{}, the character
+codes used in the \acro{PDF} file are in fact those of the document's
+\Qref*{font encoding}{Q-whatenc}; if you're using \acro{OT}1 or
+\acro{T}1, your document will be \acro{OK} for almost all \acro{ASCII}
+characters, but it's likely that anything ``out of the ordinary'' will
+not be represented properly. (Of course, \acro{PDF} generated from
+\xetex{}- or \luatex{}-based formats is going to be \acro{OK}, since
+those engines work in Unicode througout.)
+
+The solution comes from the character-mapping facilities in the
+\acro{PDF} specification: the file may specify a table of translations
+of characters present in the coding used in the file, to a Unicode
+version of the characters.
+
+Packages \Package{cmap} and \Package{mmap} both offer means of
+generating such tables (\Package{mmap} has wider coverage, including
+the various maths encodings); both work with \pdftex{} and no other
+engine. Thus your document becomes something like:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\usepackage{mmap} % (or cmap)
+\usepackage[T1]{fontenc}
+... % your other packages
+\begin{document}
+... % your actual text
+\end{verbatim}
+\end{quote}
+
+Unfortunately, the packages only work with fonts that are directly
+encoded, such as the default (Computer Modern, i.e., \FontName{cm}
+fonts, and things such as \FontName{cm-super} or the \FontName{Latin}
+\FontName{Modern} sets. Fonts like Adobe
+Times Roman (which are encoded for \AllTeX{} use via virtual fonts)
+are not amenable to this treatment.
+\begin{ctanrefs}
+\item[cmap.sty]\CTANref{cmap}
+\item[cm-super \nothtml{\rmfamily}fonts]\CTANref{cm-super}
+\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm}
+\item[mmap.sty]\CTANref{mmap}
+\end{ctanrefs}
+\LastEdit{2013-08-21}
+
+% \Question[Q-hypertex]{The Hyper\tex{} project}
+%
+% The Hyper\TeX{} project extended the functionality of all the
+% \LaTeX{} cross-referencing commands (including the table of contents)
+% to produce \csx{special} commands which are parsed by \acro{DVI} processors
+% conforming to the Hyper\TeX{} guidelines;
+% it provides general hypertext links, including those
+% to external documents.
+%
+% The Hyper\TeX{} specification says that conformant viewers/translators
+% must recognize the following set of \csx{special} commands:
+% \begin{description}
+% \item[href:] |html:<a href = "href_string">|
+% \item[name:] |html:<a name = "name_string">|
+% \item[end:] |html:</a>|
+% \item[image:] |html:<img src = "href_string">|
+% \item[base\_name:] |html:<base href = "href_string">|
+% \end{description}
+%
+% The \emph{href}, \emph{name} and \emph{end} commands are used to do
+% the basic hypertext operations of establishing links between sections
+% of documents.
+%
+% Further details are available on \URL{http://arXiv.org/hypertex/}; there
+% are two commonly-used implementations of the specification, a
+% modified \ProgName{xdvi} and (recent releases of)
+% \ProgName{dvips}. Output from the latter may be used in recent
+% releases of \ProgName{ghostscript} or Acrobat Distiller.
+
+
diff --git a/help/uk-tex-faq/faq-images.tex b/help/uk-tex-faq/faq-images.tex
new file mode 100644
index 0000000000..714c628f0a
--- /dev/null
+++ b/help/uk-tex-faq/faq-images.tex
@@ -0,0 +1,25 @@
+\documentclass[a4paper,12pt]{article}
+\usepackage[active,tightpage]{preview}
+\begin{document}
+\large
+
+% image 1: wobbly subscript
+\begin{preview}
+ $ X^{1}_{2} X_{2} $
+\end{preview}
+
+% image 2: even subscript pushed down by null superscript
+\begin{preview}
+ $ X^{1}_{2} X^{}_{2} $
+\end{preview}
+
+% image 3: simple use of maths:
+\begin{preview}
+ \texttt{fi}\ensuremath\Rightarrow``fi''
+\end{preview}
+\end{document}
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:
diff --git a/help/uk-tex-faq/faq-install.tex b/help/uk-tex-faq/faq-install.tex
new file mode 100644
index 0000000000..7c01b80fcf
--- /dev/null
+++ b/help/uk-tex-faq/faq-install.tex
@@ -0,0 +1,1021 @@
+% $Id: faq-install.tex,v 1.17 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Installing \AllTeX{} files}
+
+\Question[Q-installthings]{Installing things on a \AllTeX{} system}
+\AliasQuestion{Q-instpackages}
+
+Installing (or replacing) things on your \AllTeX{} system has the
+potential to be rather complicated; the following questions attempt to
+provide a step-by-step approach, starting from the point where you've
+decided what it is that you want to install:
+\begin{itemize}
+\item You must \Qref*{find the file you need}{Q-install-find};
+\item If you are going to install a \LaTeX{} package, you may need to
+ \Qref*{unpack the distributed files}{Q-install-unpack};
+\item It may be necessary to % ! line break
+ \Qref*{generate some documentation to read}{Q-install-doc};
+\item You need to % ! line break
+ \Qref*{decide where to install the files}{Q-install-where};
+\item You must now \Qref*{install the files}{Q-inst-wlcf}; and
+ finally
+\item You may need to \Qref*{tidy up}{Q-inst-tidy} after the installation.
+\end{itemize}
+
+\Question[Q-install-find]{Finding packages to install}
+
+How did you learn about the package?
+
+If the information came from these \acro{FAQ}s, you should already
+have a link to the file (there are lists of packages at the end of
+each answer).
+\begin{narrowversion}
+ Make a browser link from \URL{http://mirror.ctan.org/} and the text
+ in the package list; if the link returns a directory listing, you can
+ generally retrieve the whole directory by appending the link with
+ \extension{zip}~--- so, for example
+ \URL{http://mirror.ctan.org/macros/latex/doc.zip} for the \latex{}
+ documentation directory.
+\end{narrowversion}
+\begin{wideversion}
+ Click on one of the links associated with the package, and you can
+ get the package (which may be one file or several).
+% need separate wording for pdfversion and htmlversion, here
+\end{wideversion}
+
+If you heard about the file somewhere else, it's possible that the
+source told you where to look; if not, try the \acro{CTAN} searching
+facilities, such as \URL{http://www.tex.ac.uk/search/}. That (rather
+simple) search engine can return data from a search of the CTAN
+catalogue (which covers most useful packages), or data from a search
+of the names of files on the archive.
+
+Packages come in a variety of different styles of distribution; the
+very simplest will actually offer just \File{package.sty}~--- in this
+case, just download the file and % ! line break
+\Qref*{get on with installation}{Q-inst-wlcf}.
+
+You will regularly find that the file you want (e.g., \File{foo.sty})
+is distributed in a \LaTeX{} documented source file \File{foo.dtx};
+thus you should search just for \emph{foo}~--- \File{foo.sty} won't be
+visible anywhere on the archive or in the catalogue.
+
+Since most packages are distributed in this
+\extension{dtx}/\extension{ins} way, they usually occupy their own
+directory on the archive. Even if that directory contains other
+packages, you should download everything in the directory: as often as
+not, packages grouped in this way depend on each other, so that you
+really \emph{need} the other ones.
+
+Having acquired the package distribution, % ! line break
+``\Qref*{unpacking \LaTeX{} packages}{Q-install-unpack}'' outlines
+your next step.
+
+\Question[Q-install-unpack]{Unpacking \LaTeX{} packages}
+
+As discussed \Qref*{elsewhere}{Q-dtx}, the `ordinary' way to
+distribute a \LaTeX{} package is as a pair of files \File{package.dtx}
+and \File{package.ins}. If you've acquired such a pair, you simply
+process \File{package.ins} with \LaTeX{}, and the files will appear,
+ready for installation.
+
+Other sorts of provision should ordinarily be accompanied by a
+\File{README} file, telling you what to do; we list a few example
+configurations.
+
+Sometimes, a directory comes with a bunch of \extension{dtx} files, but
+fewer (often only one) \extension{ins} files (\LaTeX{} itself comes
+looking like this). If there is more than one \extension{ins} file,
+and in the absence of any instruction in the \File{README} file, simply
+process the \extension{ins} file(s) one by one.
+
+If you're missing the \File{package.ins} altogether, you need to play
+around until something works. Some \extension{dtx} files are
+``self-extracting''~--- they do without an \extension{ins} file, and once
+you've processed the \File{package.dtx}, \File{package.sty} has
+automagically appeared. Various other oddities may appear, but the
+archivists aim to have \File{README} file in every package, which
+should document anything out of the ordinary with the distribution.
+
+\Question[Q-install-doc]{Generating package documentation}
+
+We are faced with a range of ``normal'' provision, as well as several
+oddities. One should note that documentation of many packages is
+available on \acro{CTAN}, without the need of any further effort by
+the user~--- such documentation can usually be browsed \emph{in situ}.
+
+However, if you find a package that does not offer documentation on
+the archive, or if you need the documentation in some other format
+than the archive offers, you can usually generate the documentation
+yourself from what you download from the archive.
+
+The standard mechanism, for \LaTeX{} packages, is simply to run
+\LaTeX{} on the \File{package.dtx} file, as you would any ordinary
+\LaTeX{} file (i.e., repeatedly until the warnings go away).
+
+A variant is that the unpacking process provides a file
+\File{package.drv}; if such a thing appears, process it in preference
+to the \File{package.dtx} (it seems that when the documented \LaTeX{}
+source mechanism was first discussed, the \File{.drv} mechanism was
+suggested, but it's not widely used nowadays).
+
+Sometimes, the \LaTeX{} run will complain that it can't find
+\File{package.ind} (the code line index) and/or \File{package.gls}
+(the list of change records, not as you might imagine, a glossary).
+Both types of file are processed with special \ProgName{makeindex}
+style files; appropriate commands are:
+\begin{quote}
+\begin{verbatim}
+makeindex -s gind package
+makeindex -s gglo -o package.gls package.glo
+\end{verbatim}
+\end{quote}
+This author finds that the second (the change record) is generally of
+limited utility when reading package documentation; it is, however,
+valuable if you're part of the package development team. If you don't
+feel you need it, just leave out that step
+
+Another common (and reasonable) trick performed by package authors is
+to provide a separate file \File{package-doc.tex} or even simply
+\File{manual.tex}; if the file \File{package.dtx} doesn't help, simply
+look around for such alternatives. The files are treated in the same
+way as any ``ordinary'' \LaTeX{} file.
+
+\Question[Q-inst-wlcf]{Installing files ``where \AllTeX{} can find them''}
+\AliasQuestion{Q-wherefiles}
+
+In the past, package documentation used always to tell you to put your
+files ``where \LaTeX{} can find them''; this was always unhelpful~---
+if you knew where that \emph{was}, you didn't need telling, but if you
+\emph{didn't} know, you were completely stuck.
+
+It was from this issue that the whole idea of the \acro{TDS} sprang;
+``where to put'' questions now come down to ``where's the \acro{TDS}
+tree?''.
+
+We therefore answer the question by considering:
+\begin{itemize}
+\item \Qref*{what tree to use}{Q-what-TDS}, and
+\item \Qref*{where in the tree to put the files}{Q-install-where}.
+\end{itemize}
+
+Once we know the answer to both questions, and we've created any
+directories that are needed, we simply copy files to their rightful
+location.
+
+This has done what the old requirement specified: \LaTeX{} (or
+whatever) \emph{can} (in principle) find the files. However, in order
+that the software \emph{will} find the files, we need to update an
+index file.
+
+On a \miktex{} system, open the window
+ \texttt{Start}\arrowhyph{}%
+ \texttt{All Programs}\arrowhyph{}%
+ \texttt{\miktex{} \meta{version}}\arrowhyph{}%
+ \texttt{Settings},
+and click on \texttt{Refresh FNDB}.
+The job may also be done in a command window, using the command:
+\begin{quote}
+\begin{verbatim}
+initexmf --update-fndb
+\end{verbatim}
+\end{quote}
+The % ! line break
+\href{http://docs.miktex.org/manual/initexmf.html}{\miktex{} documentation}
+gives further details about \texttt{initexmf}.
+
+On a \texlive{}-based system (or its predecessor te\TeX{}, use the command
+\texttt{texhash} (or if that's not available, \texttt{mktexlsr}~---
+they ought to be different names for the same program).
+
+Having done all this, the new package will be available for use.
+
+\Question[Q-what-TDS]{Which tree to use}
+
+In almost all cases, new material that you install should go into the
+``local'' tree of your \AllTeX{} installation. (A discussion of
+reasons \emph{not} to use the local tree appears below.)
+
+On a Unix(-alike) system, using \texlive{} or te\TeX{}, the root
+directory will be named something like \path{/usr/share/texmf-local/}
+or \path{/usr/local/share/texmf/}
+You can ask such a system where it believes a local tree should be:
+\begin{quote}
+\begin{verbatim}
+kpsewhich -var-value TEXMFLOCAL
+\end{verbatim}
+\end{quote}
+the output being the actual path, for example (on the workstation this
+author is using today):
+\begin{quote}
+\begin{verbatim}
+/usr/local/share/texmf
+\end{verbatim}
+\end{quote}
+
+In a \miktex{} installation, the location will in fact typically be
+something you specified yourself when you installed \miktex{} in the
+first place, but you may find you need to create one. The \miktex{}
+``Settings'' window (%
+ \texttt{Start}\arrowhyph{}%
+ \texttt{Programs}\arrowhyph{}%
+ \texttt{\miktex{}}\arrowhyph{}%
+ \texttt{Settings})
+has a tab ``\texttt{Roots}''; that tab gives a list of current
+\acro{TDS} roots (they're typically not called
+\texttt{texmf}-anything). If there's not one there with
+``\texttt{local}'' in its name, create an appropriate one (see below),
+and register it using the window's
+``\texttt{Add}'' button.
+
+The % ! line break
+\href{http://docs.miktex.org/faq/maintenance.html}{\miktex{} \acro{FAQ}}
+suggests that you should create % ! line break
+``\texttt{C:\textbackslash Local TeX Files}'', which is good if you
+manage your own machine, but often not even possible in corporate, or
+similar, environments~--- in such situations, the user may have no
+control over the hard disc of the computer, at all.
+
+So the real criterion is that your local tree should be somewhere that
+\emph{you}, rather than the system, control. Restrictive systems often
+provide a ``home directory'' for each user, mounted as a network
+drive; this is a natural home for the user's local tree. Other (often
+academic) environments assume the user is going to provide a memory
+stick, and will assign it a defined drive letter~--- another good
+candidate location. Note that the semantics of such a tree are
+indistinguishable from those of a % ! line break
+\Qref*{``home'' \acro{TEXMF} tree}{Q-privinst}.
+
+You might not wish to use the `local' tree:
+\begin{itemize}
+\item if the package, or whatever, is ``personal'' (for example,
+ something commercial that has been licensed to you alone, or
+ something you're developing yourself), it should go in your
+ \Qref*{``home'' \acro{TEXMF} tree}{Q-privinst};
+\item if you \emph{know} that the package you are installing is a
+ replacement for the copy on the \acro{TEXMF} tree of your \AllTeX{}
+ distribution; in this case it is reasonable to replace the existing
+ copy in the \acro{TEXMF} tree.
+\end{itemize}
+If the system is upgraded (or otherwise re-installed), a copy made in
+the \acro{TEXMF} tree will probably be overwritten or deleted. This
+may be what you want, but otherwise it's a powerful incentive to use a
+tree that is \emph{not} ``part of the installed system''.
+
+The reason one might place upgrades the distribution's main tree is to
+avoid confusion. Suppose you were to place the file on the local
+tree, and then install a new version of the distribution~--- you might
+have an effect like:
+\begin{itemize}
+\item distribution comes with package version \ensuremath{n};
+\item you install package version \ensuremath{n+1} on the local tree; and
+\item the updated distribution provides package version \ensuremath{n+2}.
+\end{itemize}
+In such a situation, you could find yourself using version
+\ensuremath{n+1} (from the local tree) \emph{after} the new
+distribution has been installed.
+
+If you install in the local tree, the only way to avoid such problems
+is to carefully purge the local tree when installing a new
+distribution. This is tedious, if you're maintaining a large
+installation.
+
+\Question[Q-install-where]{Where to install packages}
+
+We assume here that you have decided what tree to put your files in,
+after reading % ! line break
+``\Qref*{choosing a \acro{TDS} tree}{Q-what-TDS}''. We will therefore
+write \texttt{\$TEXMF} for it, and you need to substitute the tree
+you decided on.
+
+The basic idea is to imitate the directory structure in your
+existing tree(s). Here are some examples of where various sorts of
+files should go:
+\begin{verbatim}
+.sty, .cls or .fd: $TEXMF/tex/<format>/<package>/
+.mf: $TEXMF/fonts/source/<supplier>/<font>/
+.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/
+.vf: $TEXMF/fonts/vf/<supplier>/<font>/
+.afm: $TEXMF/fonts/afm/<supplier>/<font>/
+.pfb: $TEXMF/fonts/type1/<supplier>/<font>/
+.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/
+.otf: $TEXMF/fonts/opentype/<supplier>/<font>/
+.pool, .fmt, .base or .mem: $TEXMF/web2c
+\end{verbatim}
+and for modern systems (those distributed in 2005 or later, using \acro{TDS}
+v1.1 layouts):
+\begin{verbatim}
+.map: $TEXMF/fonts/map/<syntax>/<bundle>/
+.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/
+\end{verbatim}
+(Map and encoding files went to directories under
+\File{$TEXMF/dvips/}, %$
+in earlier distributions.)
+
+In the lists above \meta{format} identifies the format the macros
+are designed for~--- it can be things such as \texttt{plain},
+\texttt{generic} (i.e., any format), \texttt{latex} or
+\texttt{context} (or several less common formats).
+
+For fonts, \meta{font} refers to the font family (such as \texttt{cm}
+for Knuth's Computer Modern, \texttt{times} for Adobe's Times Roman).
+The supplier is usually obvious~--- the supplier
+``public'' is commonly used for free fonts.
+
+The \meta{syntax} (for \extension{map} and \extension{enc} files) is a
+categorisation based on the way the files are written; candidates are
+names of programs such as \ProgName{dvips} or \ProgName{pdftex}.
+
+``Straight'' \AllTeX{} input can take other forms than the
+\extension{sty}, \extension{cls} or \extension{fd} listed above, too
+(apart from the `obvious' \extension{tex}). Examples are (the
+obvious) \extension{tex}, \extension{lfd} for \Package{babel} language
+definitions, \extension{sto} and \extension{clo} for package and class
+options, \extension{cfg} for configuration information,
+\extension{def} for variants (such as the types of devices
+\Package{graphics} drives). The \File{README} of the package should
+tell you of any others, though sometimes that information is printed
+when the package's \Qref*{comments are stripped}{Q-install-unpack}.
+All of these files should live together with the main package files.
+
+Note that \meta{font} may stand for a single font or an entire family:
+for example, files for all of Knuth's Computer Modern fonts are to be
+found in \texttt{.../public/cm}, with various prefixes as appropriate.
+
+The font ``supplier'' \emph{public} is a sort of hold-all for
+``free fonts produced for use with \AllTeX{}'': as well as Knuth's
+fonts, \emph{public}'s directory holds fonts designed by others
+(originally, but no longer exclusively, in \MF{}).
+
+Documentation for each package should all go, undifferentiated, into a
+directory on the \path{doc/} subtree of the \acro{TDS}. The layout of
+the subtree is slightly different: \path{doc/latex} hosts all
+\LaTeX{} documentation directories, but more fundamental things are
+covered, e.g., by \path{doc/etex} or \path{doc/xetex}.
+
+\Question[Q-inst-tidy]{Tidying up after installation}
+
+There's not usually a lot to do after you've completed the steps
+above~--- indeed, if you're merely installed files direct from the
+archive, or whatever, there will be precisely nothing left, by way of
+debris.
+
+Things you might care to clean up are:
+\begin{itemize}
+\item the archive file, if you retrieved your data from the archive
+ as a \extension{zip} file, or the like;
+\item the \extension{dtx} and \extension{ins} files, if you chose not
+ to install them with the documentation; and
+\item the \extension{aux}, \extension{log}, \extension{idx}, etc.,
+ from building the documentation.
+\end{itemize}
+A simple way of achieving all this is to download to a working
+directory that was created for the purpose, and then to delete that
+directory and all its contents after you've finished installing.
+
+\Question[Q-inst-scut]{Shortcuts to installing files}
+
+There are circumstances in which most of the fuss of installation can
+be bypassed:
+\begin{itemize}
+\item If you are a \miktex{} user, the
+\begin{hyperversion}
+ \Qref{\miktex{} package management system}{Q-inst-miktex*}
+ can usually help;
+\end{hyperversion}
+\begin{flatversion}
+ \miktex{} package management system can usually help
+ (\Qref{}{Q-inst-miktex*});
+\end{flatversion}
+\item Similarly, if you are a \texlive{} user, the
+\begin{hyperversion}
+ \Qref{\texlive{} manager}{Q-inst-texlive}
+ can usually help;
+\end{hyperversion}
+\begin{flatversion}
+ \texlive{} package management system can usually help
+ (\Qref{}{Q-inst-texlive});
+\end{flatversion}
+\item The package you want may already exist as a \acro{ZIP} file
+\begin{wideversion}
+ formatted for \Qref{direct installation}{Q-inst-tds-zip}.
+\end{wideversion}
+\begin{narrowversion}
+ formatted for direct installation (\Qref{}{Q-inst-tds-zip}).
+\end{narrowversion}
+\end{itemize}
+
+\Question[Q-inst-miktex*]{Installation using \miktex{} package manager}
+\AliasQuestion{Q-inst-miktex}
+
+Packages for use with \miktex{} are maintained very efficiently by the
+project managers (new packages and updates on \acro{CTAN} ordinarily
+make their way to the \miktex{} package repository within a week).
+Thus it makes sense for the \miktex{} user to take advantage of the
+system rather than grinding through the steps of installation.
+
+\miktex{} maintains a database of packages it ``knows about'',
+together with (coded) installation instructions that enable it to
+install the packages with minimal user intervention; you can update
+the database over the internet.
+
+If \miktex{} does know about a package you need installed, it's worth
+using the system:
+first, open the \miktex{} packages window: click on
+ \texttt{Start}\arrowhyph{}%
+ \texttt{Programs}\arrowhyph{}%
+ \texttt{MiKTeX}\arrowhyph{}%
+ \texttt{MiKTeX Options}, and select the
+ \texttt{Packages} tab.
+
+On the tab, there is an Explorer-style display of packages.
+Right-click on the root of the tree, ``\texttt{MiKTeX Packages}'',
+and select ``\texttt{Search}'': enter the name of the package you're
+interested in, and press the ``\texttt{Search}'' button. If
+\miktex{} knows about your package, it will open up the tree to show
+you a tick box for your package: check that box.
+
+If you prefer a command-line utility, there's \ProgName{mpm}. Open a
+command shell, and type:
+\begin{quote}
+\begin{verbatim}
+mpm --install=<package>
+\end{verbatim}
+\end{quote}
+(which of course assumes you know the name by which \miktex{} refers to
+your package).
+
+\Question[Q-inst-texlive]{Installation using \texlive{} manager}
+
+\texlive{} manager (\ProgName{tlmgr}) is, by default, a shell (or
+Windows terminal window) command. There is voluminous documentation
+about it from the command
+\begin{quote}
+ \texttt{tldoc tlmgr}
+\end{quote}
+but basic operation is pretty straightforward. The manager needs to
+know where to download stuff from; the canonical setup is
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+tlmgr option repository \
+ http://mirror.ctan.org/systems/texlive/tlnet
+\end{verbatim}
+(line wrapped to fit in the narrow column)
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+tlmgr option repository http://mirror.ctan.org/systems/texlive/tlnet
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+which passes the decision to the mirror selector. You can (of course)
+specify a particular archive or mirror that you ``trust'', or even a
+local disc copy that you keep up-to-date (disc space and bandwidth are
+so cheap nowadays, that a ``home mirror'' of \acro{CTAN} is a feasible
+proposition).
+
+To update a single package, use:
+\begin{quote}
+\begin{verbatim}
+tlmgr update <package>
+\end{verbatim}
+\end{quote}
+
+To update everything you already have in your installation, use:
+\begin{quote}
+\begin{verbatim}
+tlmgr update --all
+\end{verbatim}
+\end{quote}
+
+\Question[Q-inst-tds-zip]{Installing using ready-built \acro{ZIP} files}
+
+Installing packages, as they (``traditionally'') appear on
+\acro{CTAN}, involves:
+\begin{itemize}
+\item identifying where to put the various files on an \acro{TDS}
+ tree,
+\item installing them, and
+\item a few housekeeping operations.
+\end{itemize}
+Most people, for most packages, find the first two steps onerous, the
+last being easy (unless it is forgotten!).
+
+Ready-built \acro{ZIP} files~--- also known as % ! line break
+\Qref*{\acro{TDS}-\acro{ZIP} files}{Q-tds-zip}~--- are designed to lighten
+the load of performing the first two steps of installation: they
+contain all the files that are to be installed for a given
+package, in their ``correct'' locations in a % ! line break
+\Qref*{\acro{TDS} tree}{Q-tds}.
+
+To install such a file on a Unix system (we assume that you'll install
+into the local \acro{TEXMF} tree, at \texttt{\$TEXMFLOCAL}):
+\begin{quote}
+\begin{verbatim}
+cd $TEXMFLOCAL
+unzip $package.tds.zip
+\end{verbatim}
+\end{quote}
+
+On a Windows system that is modern enough that it has a built-in
+\acro{ZIP} unpacker, simply double-click on the file, and browse to
+where it's to be unpacked. (We trust that those using earlier
+versions of Windows will already have experience of using
+\ProgName{WinZIP} or the like.)
+
+Having unpacked the \extension{zip} archive, in most cases the only
+remaining chore is to update the file indexes~--- as in % ! line break
+\Qref*{normal installation instructions}{Q-inst-wlcf}. However, if
+the package provides a font, you also need to enable the font's map,
+which is discussed in % ! line break
+``\Qref*{Installing a Type~1 font}{Q-instt1font}''
+\LastEdit{2012-02-08}
+
+\Question[Q-tempinst]{``Temporary'' installation of \AllTeX{} files}
+
+Operating systems and applications need to know where to find files:
+many files that they need are ``just named''~--- the user doesn't
+necessarily know \emph{where} they are, but knows to ask for them.
+The commonest case, of course, is the commands whose names you type to
+a shell (yes, even Windows' ``\MSDOS{} prompt'') are using a shell to read what
+you type: many of the commands simply involve loading and executing a
+file, and the \texttt{PATH} variable tells the shell where to find those files.
+
+Modern \TeX{} implementations come with a bunch of search paths
+built in to them. In most circumstances these paths are adequate, but
+one sometimes needs to extend them to pick up files in strange
+places: for example, we may wish to try a new bundle of packages
+before \Qref*{installing them `properly'}{Q-installthings}. To do
+this, we need to change the relevant path as \TeX{} perceives it.
+However, we don't want to throw away \TeX{}'s built-in path (all of a
+sudden, \TeX{} won't know how to deal with all sorts of things).
+
+To \emph{extend} a \TeX{} path, we define an operating system
+environment variable in `path format', but leaving a gap which \TeX{}
+will fill with its built-in value for the path. The commonest case is
+that we want to place our extension in front of the path, so that our
+new things will be chosen in preference, so we leave our `gap to be
+filled' at the end of the environment variable. The syntax is simple
+(though it depends which shell you're actually using): so on a
+Unix-like system, using the \ProgName{bash} shell, the job might be
+done like:
+\begin{quote}
+\begin{verbatim}
+export TEXINPUTS=/tmp:
+\end{verbatim}
+\end{quote}
+while in a Windows system, within a \MSDOS{} window, it would be:
+\begin{quote}
+\begin{verbatim}
+set TEXINPUTS=C:/temp;
+\end{verbatim}
+\end{quote}
+In either case, we're asking \TeX{} to load files from the root disc
+temporary files directory; in the Unix case, the ``empty slot'' is
+designated by putting the path separator `|:|' on its own at the end
+of the line, while in the Windows case, the technique is the same, but
+the path separator is `|;|'.
+
+Note that in either sort of system, the change will only affect
+instances of \TeX{} that are started from the shell where the
+environment variable was set. If you run \TeX{} from another window,
+it will use the original input path. To make a change of input path
+that will ``stick'' for all windows, set the environment variable in
+your login script or profile (or whatever) in a Unix system and log
+out and in again, or in \File{autoexec.bat} in a Windows system, and
+reboot the system.
+
+While all of the above has talked about where \TeX{} finds its macro
+files, it's applicable to pretty much any sort of file any
+\TeX{}-related program reads~--- there are lots of these paths, and of
+their corresponding environment variables. In a
+\ProgName{web2c}-based system, the copious annotations in the
+\File{texmf.cnf} system configuration file help you to learn which
+path names correspond to which type of file.
+
+\Question[Q-privinst]{``Private'' installations of files}
+
+It sometimes happens that you need a new version of some macro package
+or font, but that the machine you use is maintained by someone who's
+unwilling to update and won't give you privileges to do the job
+yourself. A \Qref*{``temporary'' installation}{Q-tempinst} is
+sometimes the correct approach, but if there's the slightest chance
+that the installation will be needed on more than one project,
+temporary installations aren't right.
+
+In circumstances where you have plenty of quota on backed-up media, or
+adequate local scratch space, the correct approach is to create a
+private installation of \AllTeX{} which includes the new stuff you
+need; this is the ideal, but is not generally possible.
+
+So, since you can't install into the public \texttt{texmf} tree, you
+have to install into a \File{texmf} tree of your own; fortunately, the
+\acro{TDS} standard allows for this, and modern distributions allow
+you to do it. The most modern distributions refer to the tree as
+\texttt{\$TEXMFHOME}, but it used to be called \texttt{\$HOMETEXMF};
+so to check that your \TeX{} system does indeed support the mechanism
+you should start with
+\begin{quote}
+\begin{verbatim}
+kpsewhich -var-value TEXMFHOME
+\end{verbatim}
+\end{quote}
+(for example). This will almost invariably return a pointer to a
+subdirectory \File{texmf} of your home directory; the commonest
+exception is Macintoshes, using Mac\TeX{}, where the diretory is
+conventionally \File{Library/texmf} in your home directory.
+
+If you can confirm that the technique does indeed work, install your
+new package (or whatever) in the \Qref*{correct place}{Q-install-where}
+in a tree based on \File{$HOME/texmf}, %$
+and generate an index of that tree
+\begin{quote}
+\begin{verbatim}
+texhash $HOME/texmf
+\end{verbatim}
+\end{quote}
+(the argument specifies which tree you are indexing: it's necessary
+since you don't, by hypothesis, have access to the main tree, and
+\ProgName{texhash} without the argument would try to write the main
+tree.
+
+There are two wrinkles to this simple formula: first, the installation
+you're using may \emph{not} define a home TEXMF directory, and second,
+there may be some obstruction to using \File{$HOME/texmf} %$
+as the
+default name. In either case, a good solution is to have your own
+\File{texmf.cnf}~--- an idea that sounds more frightening that it
+actually is. The installation's existing file may be located with the
+command:
+\begin{quote}
+\begin{verbatim}
+kpsewhich texmf.cnf
+\end{verbatim}
+\end{quote}
+Take a copy of the file and put it into a directory of your own; this
+could be any directory, but an obvious choice is the \File{web2c}
+directory of the tree you want to create, i.e.,
+\File{$HOME/texmf/web2c} %$
+or the like. Make an environment variable to
+point to this directory:
+\begin{quote}
+\begin{verbatim}
+TEXMFCNF=$HOME/texmf/web2c
+export TEXMFCNF
+\end{verbatim}
+\end{quote}
+(for a Bourne shell style system), or
+\begin{quote}
+\begin{verbatim}
+setenv TEXMFCNF $HOME/texmf/web2c
+\end{verbatim}
+\end{quote}
+(for a C-shell style system). Now edit the copy of \File{texmf.cnf}
+
+There will be a line in the existing file that defines the tree where
+everything searches; the simplest form of the line is:
+\begin{quote}
+\begin{verbatim}
+TEXMF = !!$TEXMFMAIN
+\end{verbatim}
+\end{quote}
+but, there are likely to be several alternative settings behind
+comment markers (``\texttt{\textpercent{}}''), and the person who
+installed your system may have left them there. Whatever, you need to
+modify the line that's in effect: change the above to three lines:
+\begin{quote}
+\begin{verbatim}
+HOMETEXMF = $HOME/texmf
+TEXMF = {$HOMETEXMF,!!$TEXMFMAIN}
+% TEXMF = !!$TEXMFMAIN
+\end{verbatim}
+\end{quote}
+the important point being that \texttt{\$HOMETEXMF} must come before
+whatever was there before, inside the braces. For example, if the
+original was
+\begin{quote}
+\begin{verbatim}
+TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
+\end{verbatim}
+\end{quote}
+it should be converted to:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+HOMETEXMF = $HOME/texmf
+TEXMF = {$HOMETEXMF,!!$LOCALTEXMF,
+ !!$TEXMFMAIN}
+% TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
+\end{verbatim}
+{\small Note that the \texttt{TEXMF} line is only wrapped to make it
+ fit in the column; there should be no line break or space between
+ the final comma on the line and the \texttt{!!} on the next line.\par
+}%
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+HOMETEXMF = $HOME/texmf
+TEXMF = {$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
+% TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+(retaining the original, as a comment, is merely an aide-memoir in
+case you need to make another change, later). The \texttt{!!} signs
+tell the file-searching library that it should insist on a
+\ProgName{texhash}-ed directory tree; if you can count on yourself
+remembering to run \ProgName{texhash} on your new tree every time you
+change it, then it's worth adding the marks to your tree:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,
+ !!$TEXMFMAIN}
+\end{verbatim}
+{\small Note that the line is only wrapped to make it
+ fit in the column; there should be no line break or space between
+ the final comma on the line and the \texttt{!!} on the next line.\par
+}%
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+as this will make \AllTeX{} find its files marginally faster.
+
+Having made all these changes, \AllTeX{} should ``just use'' files in
+your new tree, in preference to anything in the main tree~--- you can
+use it for updates to packages in the main tree, as well as for
+installing new versions of things.
+\LastEdit{2011-04-13}
+
+\Question[Q-instfont]{Installing a new font}
+
+Fonts are really ``just another package'', and so should be installed
+in the same sort of way as packages. However, fonts tend to be more
+complicated than the average package, and as a result it's sometimes
+difficult to see the overall structure.
+
+Font files may appear in any of a large number of different formats;
+each format has a different function in a \TeX{} system, and each is
+stored in a directory its own sub-tree in the installation's
+\acro{TDS} tree; all these sub-trees have the directory
+\File{$TEXMF/fonts} %$
+as their root. A sequence of answers\nothtml{, below,} describes the
+installation of fonts\latexhtml{.}{:}
+\begin{htmlversion}
+follow the list through the ``next question'' links at the bottom of
+this answer to view them all.
+\end{htmlversion}
+Other answers discuss specific font families~--- for example,
+% ! line break
+``\Qref*{using the concrete fonts}{Q-concrete}''.
+
+\Question[Q-instmffont]{Installing a font provided as \MF{} source}
+
+Installing Metafont fonts is (by comparison with other sorts of font) rather
+pleasingly simple. Nowadays, they are mostly distributed just as the
+\MF{} source, since modern \TeX{} distributions are able to produce
+everything the user needs ``on the fly''; however, if the distribution
+\emph{does} include \acro{TFM} files, install them too, since they
+save a little time and don't occupy much disc space. Always distrust
+distributions of \acro{PK} font bitmap files: there's no way of
+learning from them what printer they were generated for, and naming
+schemes under different operating systems are another source of
+confusion.
+
+``\Qref*{Where to install files}{Q-install-where}''
+specifies where the files should go.
+
+Further confusion is introduced by font families whose authors devise rules
+for automatic generation of \MF{} sources for generating fonts at
+particular sizes; the installation has to know about the rules, as
+otherwise it cannot generate font files. No general advice is
+available, but most such font families are now obsolescent.
+
+\Question[Q-instprinterfont]{`Installing' a \PS{} printer built-in font}
+
+There is a ``standard'' set of fonts that has appeared in every \PS{}
+printer since the second generation of the type. These fonts
+(8~families of four text fonts each, and three special-purpose fonts)
+are of course widely used, because of their simple availability. The
+set consists of:
+\begin{itemize}
+\item \FontName{Times} family (4 fonts)
+\item \FontName{Palatino} family (4 fonts)
+\item \FontName{New} \FontName{Century} \FontName{Schoolbook} family (4 fonts)
+\item \FontName{Bookman} family (4 fonts)
+\item \FontName{Helvetica} family (4 fonts)
+\item \FontName{Avant} \FontName{Garde} (4 fonts)
+\item \FontName{Courier} family (4 fonts)
+\item \FontName{Utopia} family (4 fonts)
+\item Zapf \FontName{Chancery} (1 font)
+\item Zapf \FontName{Dingbats} (1 font)
+\item \FontName{Symbol} (1 font)
+\end{itemize}
+All these fonts are supported, for \LaTeX{} users, by the
+\Package{psnfss} set of metrics and support files in the file
+\File{lw35nfss.zip} on \acro{CTAN}. Almost any remotely modern \TeX{}
+system will have some version of \Package{psnfss} installed, but
+users should note that the most recent version has much improved
+coverage of maths with \FontName{Times} (see package
+\Package{mathptmx}) and with \FontName{Palatino} (see package
+\Package{mathpazo}, as well as a more reliable set of font metrics.
+
+The archive \File{lw35nfss.zip} is laid out according to the
+\acro{TDS}, so in principle, installation consists simply of
+``unzipping'' the file at the root of a \path{texmf} tree.
+
+Documentation of the \Package{psnfss} bundle is provided in
+\File{psnfss2e.pdf} in the distribution.
+\begin{ctanrefs}
+\item[mathpazo.sty]Part of the \Package{psnfss} bundle
+\item[mathptmx.sty]Part of the \Package{psnfss} bundle
+\item[psnfss \nothtml{\rmfamily}bundle]\CTANref{psnfss}
+\end{ctanrefs}
+
+\Question[Q-prept1font]{Preparing a Type~1 font}
+
+The process of installing a Type~1 font set is rather convoluted, and
+we will deal with it in two chunks: first (in the present answer)
+preparing the font for installation, and second % ! line break
+\Qref*{installing a Type~1 font}{Q-instt1font}).
+
+Many fonts are supplied in \AllTeX{} ready form: such fonts need no
+preparation, and may be installed immediately.
+
+However, if you purchase a font from a Type foundry (either direct or
+via one of the web stores), you are likely to need to `prepare' it for
+use with \AllTeX{}. The rest of this answer discusses this preparation.
+\begin{itemize}
+\item Acquire the font. A very small set of Type~1 fonts is installed
+ in most \PS{} printers you will encounter. For those few (whose use
+ is covered by the basic \acro{PSNFSS} package), you don't need the
+ Type~1 font itself, to be able to print using the font.
+
+ For all the myriad other Type~1 fonts, to be able to print using
+ the font you need the Type~1 file itself. Some of these are
+ available for free (they've either been donated to the public
+ domain, or were developed as part of a free software project), but
+ the vast majority are commercial products, requiring you to spend
+ real money.
+\item Acquire the fonts' \acro{AFM} files. \acro{AFM} files contain
+ information from the font foundry, about the sizes of the characters
+ in the font, and how they fit together. One measure of the quality
+ of a font-supplier is that they provide the \acro{AFM} files by
+ default: if the files are not available, you are unlikely to be able
+ to use the font with \AllTeX{}.
+\item Rename the \acro{AFM} files and the Type~1 files to match the
+ \Qref*{Berry font naming scheme}{Q-fontname}.
+\item Generate \TeX{} metric files from the \acro{AFM} files. The
+ commonest tool for this task is \Package{fontinst}; the package
+ documentation helps, but other guides are available (see below).
+ The simplest possible script to pass to \Package{fontinst} is:
+ \begin{quote}
+\begin{verbatim}
+\latinfamily{xyz}{}
+\bye
+\end{verbatim}
+ \end{quote}
+ where \texttt{xyz} is the Berry name of the font family. This
+ simple script is adequate for most purposes: its output covers the
+ font family in both \acro{T}1 and \acro{OT}1 font encodings. Nevertheless,
+ with fancier fonts, more elaborate things are possible with
+ \Package{fontinst}: see its documentation for details.
+
+ \Package{Fontinst} also generates map files, and \LaTeX{} font
+ definition (\extension{fd}) files.
+\end{itemize}
+Having traversed this list, you have a set of font files ready for
+installation.
+\begin{ctanrefs}
+\item[fontinst.sty]\CTANref{fontinst}
+\item[\nothtml{\rmfamily}Type 1 installation guide]\CTANref{T1instguide}
+\end{ctanrefs}
+
+
+\Question[Q-instt1font]{Installing a Type~1 font}
+
+Once you have a prepared Type~1 font, either direct from \acro{CTAN}
+or the like, or having \Qref*{`prepared' it yourself}{Q-prept1font},
+you can get on with installation.
+
+The procedure is merely an extension of that for packages, etc., so
+much of what follows will be familiar:
+\begin{itemize}
+\item Install the files, in your local \texttt{texmf} tree (the advice
+ about installing non-standard things applies here, too). The
+ following list gives reasonable destinations for the various files
+ related to a font family \meta{fname}:
+\begin{narrowversion}
+\begin{verbatim}
+.pfb,
+.pfa .../fonts/type1/<foundry>/<fname>
+.tfm .../fonts/tfm/<foundry>/<fname>
+.vf .../fonts/vf/<foundry>/<fname>
+.sty,
+.fd .../tex/latex/<fname>
+.map .../fonts/map/dvips/<foundry>
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+.pfb,
+.pfa .../fonts/type1/<foundry>/<fname>
+.tfm .../fonts/tfm/<foundry>/<fname>
+.vf .../fonts/vf/<foundry>/<fname>
+.sty,
+.fd .../tex/latex/<fname>
+.map .../fonts/map/dvips/<foundry>
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+ but if you are lucky, you will be starting from a distribution from
+ \acro{CTAN} and there is a corresponding \extension{tds.zip} file:
+ using this \acro{TDS}-file saves the bother of deciding where to put
+ your files in the \acro{TDS} tree.
+\item Regenerate the file indexes (as described in
+ \Qref[question]{package installation}{Q-inst-wlcf}).
+\item Update the \ProgName{dvips}, \PDFTeX{} and other maps:
+ \begin{itemize}
+ \item On any current \texlive{}-based system, or a te\TeX{} v3.0
+ system, execute the command
+\begin{quote}
+\begin{verbatim}
+updmap-sys --enable Map <fname>.map
+\end{verbatim}
+\end{quote}
+ as root. (If you \emph{can} use \ProgName{updmap-sys}~--- do; if
+ not~--- presumably because your \alltex{} system was set up by
+ someone else~--- you have to fall back on plain \ProgName{updmap},
+ but be aware that it's a potent source of confusion, setting up
+ map sets that might be changed behind your back.)
+ \item On a current \miktex{} system, update the system file
+ \File{updmap.cfg}, using the shell command
+\begin{quote}
+\begin{verbatim}
+initexmf --edit-config-file updmap
+\end{verbatim}
+\end{quote}
+ adding a line at the end:
+\begin{quote}
+\begin{verbatim}
+Map <fname>.map
+\end{verbatim}
+\end{quote}
+ for each font family \meta{fname} you are adding to the system.
+ Now generate revised maps with the shell command
+\begin{quote}
+\begin{verbatim}
+initexmf --mkmaps
+\end{verbatim}
+\end{quote}
+ This, and other matters, are described in \miktex{} % beware line break
+ \href{http://docs.miktex.org/manual/advanced.html}{``advanced'' documentation}.
+ \end{itemize}
+\end{itemize}
+Both processes (preparing and installing a font) are very well (and
+thoroughly) described in Philipp Lehman's guide to font installation,
+which may be found on \acro{CTAN}.
+\begin{ctanrefs}
+\item[fontinst.sty]\CTANref{fontinst}
+\item[\nothtml{\rmfamily}Type 1 installation guide]\CTANref{T1instguide}
+\end{ctanrefs}
+
+\Question[Q-inst1cm]{Installing the Type~1 versions of the CM~fonts}
+
+This is a specialised case of \Qref*{installing a font}{Q-instfont},
+but it is almost never necessary~--- it's inconceivable that any (even
+remotely) recent system will \emph{not} have the fonts already
+installed. You can confirm this (near-inevitable) fact by trying the
+fonts. On a system that uses \ProgName{dvips} (almost all do), try
+the sequence:
+\begin{quote}
+\begin{verbatim}
+latex sample2e
+dvips -o sample2e.ps sample2e
+\end{verbatim}
+\end{quote}
+at a ``command prompt'' (\ProgName{shell}, in a Unix-style system,
+``\acro{DOS} box'' in a Windows system).
+
+If the command works at all, the console output of the command will
+include a sequence of Type~1 font file names, listed as
+\texttt{<\emph{path}/cmr10.pfb>} and so on; this is \ProgName{dvips}
+telling you it's copying information from the Type~1 font, and you
+need do no more.
+
+If the test has failed, you need to install your own set of the fonts;
+the distribution (including all the fonts the \acro{AMS} designed and
+produced themselves) is now described as \Package{amsfonts}. The
+bundle contains metric and map files~--- all you need to
+\Qref*{install the fonts}{Q-instt1font}.
+\begin{ctanrefs}
+\item[AMS and CM fonts, in Type 1 format]\CTANref{amsfonts}
+\end{ctanrefs}
+
+
diff --git a/help/uk-tex-faq/faq-intro.tex b/help/uk-tex-faq/faq-intro.tex
new file mode 100644
index 0000000000..6d82072690
--- /dev/null
+++ b/help/uk-tex-faq/faq-intro.tex
@@ -0,0 +1,203 @@
+% $Id: faq-intro.tex,v 1.31 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+% this environment is for the benefit of new-style file generation
+\begin{introduction}
+% suppress section numbers until end environment
+\nothtml{\csname c@secnumdepth\endcsname=-1 }
+\section{Introduction}
+
+This is a set of Frequently Asked Questions (\acro{FAQ}) for
+English-speaking users of \TeX{}.
+
+The questions answered here cover a wide range of topics, but
+typesetting issues are mostly covered from the viewpoint of a \LaTeX{}
+user. Some of the questions answered have little relevance to today's
+users; this is inevitable~--- it's easier to add information than it
+is to decide that information is no longer needed. The set of
+answered questions is therefore in a state of slow flux: new questions
+are answered, while old questions are deleted~\dots{}~but the whole
+process depends on the time available for \acro{FAQ} maintenance.
+
+\nothtml{\noindent} You may use the \acro{FAQ}
+\begin{itemize}
+\item by reading a printed document,
+\item by viewing a \acro{PDF} file, with hyperlinks to assist
+ browsing: copies are available formatted so that they could be
+ printed on \CTANhref{faq-a4}{A4 paper} or on % ! line break
+ \CTANhref{faq-letter}{North American ``letter'' paper}, \htmlonly{or}
+\begin{typesetversion}
+\item by using the \acro{FAQ}'s web interface (base \acro{URL}:
+ \URL{http://www.tex.ac.uk/faq}); this version provides simple
+ search capabilities, as well as a link to Google for a more
+ sophisticated search restricted to the \acro{FAQ} itself, or
+\end{typesetversion}
+\item via Scott Pakin's \CTANhref{visualFAQ}{Visual FAQ}, which shows
+ \LaTeX{} constructions with links to \acro{FAQ} explanations of how
+ they may be created.
+\end{itemize}
+
+\subsection{Licence of the \acro{FAQ}}
+
+The source of the \acro{FAQ}, available in the % ! line break
+\CTANhref{faq}{\acro{FAQ}'s \ctan{} directory}, and its derived
+representations (currently, the \acro{HTML} found at
+\url{http://www.tex.ac.uk/faq} and \acro{PDF} copies, also in the
+% ! line break
+\CTANhref{faq}{\acro{FAQ}'s \ctan{} directory}) are all placed in the
+public domain.
+
+\subsection{Finding the Files}
+\begin{typesetversion}
+Unless otherwise specified, all files mentioned in this \acro{FAQ}
+are available from a \ctan{} archive, or from a mirror of
+\ctan{}~--- see \Qref[question]{later discussion}{Q-archives}% ! space
+\narrowonly{, which gives details} of the \ctan{}
+archives\wideonly{ and}\narrowonly{, including} how to retrieve files
+from them.
+
+The reader should also note that the first directory name of the path
+name of every file on \ctan{} is omitted from what follows, for
+the simple reason that, while it's always the same
+(\path{tex-archive/}) on the main sites, mirror sites often choose
+something else.
+
+To avoid confusion, we also omit the full stop from the end of any
+sentence whose last item is a path name (such sentences are rare, and
+only occur at the end of paragraphs). Though the path names are set
+in a different font from running text, it's not easy to distinguish
+the font of a single dot!
+\end{typesetversion}
+\begin{htmlversion}
+Almost all files suggested in any answer in these \acro{FAQ}s are
+available from \Qref{\ctan{} archives}{Q-archives}, and may be
+reached via links in the file list at the end of the answer. In
+particular, documentation (when available) is linked from the
+\ctan{} Catalogue entry, which is also listed in the file list.
+
+Unless doing so is unavoidable, the answers do not mention things that
+are not on the \ctan{} archives. An obvious exception is web
+resources such as supplementary documents, etc.
+\end{htmlversion}
+
+\begin{typesetversion}
+ \subsection*{Origins}
+\end{typesetversion}
+\begin{htmlversion}
+ \textbf{Origins}
+\end{htmlversion}
+The \acro{FAQ} was originated by the Committee of the \acro{UK}
+\TeX{} Users' Group (\acro{UK}~\acro{TUG}), in 1994, as a development of a
+regular posting to the \emph{Usenet} newsgroup
+\Newsgroup{comp.text.tex} that was maintained for some time by Bobby
+Bodenheimer. The first \acro{UK} version was much re-arranged and
+corrected from the original, and little of Bodenheimer's work now
+remains.
+
+\htmlignore
+The following people (at least~--- there are almost certainly others
+whose names weren't correctly recorded) have contributed help or
+advice on the development of the \acro{FAQ}:
+William Adams, % spotting dead url
+Donald Arseneau, % indefatigable
+Rosemary Bailey, % lots of initial set of maths answers
+Barbara Beeton, % one of first reviewers outside cttee
+Karl Berry, % often provides comments & suggestions
+Giuseppe Bilotta,
+Charles Cameron,
+Fran\c{c}ois Charette, % update of q-xetex
+Damian Cugley,
+Martin Garrod, % two consecutive "report" in clsvpkg
+Michael Dewey,
+Michael Downes, % (RIP) on (ams)maths stuff
+Jean-Pierre Drucbert, % (RIP) corrected my interpretation of minitoc
+David Epstein, % comment on q-algorithms, suggestion of tex-sx
+Michael Ernst, % alert on confusing colloquialism
+Thomas Esser,
+Ulrike Fischer, % spotted boondoggle in q-tabcellalign
+ % args like \section improvement; general typos
+Bruno Le Floch, % alert to mess in q-latex3
+Anthony Goreham,
+Norman Gray,
+Enrico Gregorio, % new definition for q-seccntfmt
+Werner Grundlingh, % xparse for *-commands
+Eitan Gurari, % (RIP) comparative html translators
+William Hammond, % lots of work on xml-related answers
+John Hammond, % corrections to q-protect
+John Harper, % patient help with q-robust ;-)
+Gernot Hassenpflug, % impetus and suggestions for q-printvar
+Troy Henderson, % metapost tutorials update
+Hartmut Henkel,
+Stephan Hennig, % text about vc in Q-RCS
+John Hobby,
+Morten H\textoslash gholm, % eagle eyes in search for problems
+Berthold Horn, % lots of stuff on fonts
+Ian Hutchinson, % comparative html translators
+Werner Icking, % (RIP) answer on tex-music
+William Ingram, % extension of transcinit
+David Jansen, % error in errmissitem example code
+Alan Jeffrey, % another founding father
+Regnor Jernsletten,
+David Kastrup, % inter alia, suggested mention of lilypond
+Oleg Katsitadze, % revision of q-eplain
+Isaac Khabaza, % kindersley book
+Ulrich Klauer, % pointed out twaddle in TeXpronounce
+Markus Kohm, % help with functionality of Koma-script
+Stefan Kottwitz % picked up text of q-wideflt
+David Kraus, % help with tocbibind (spotted embarrassing typo :-} )
+Ryszard Kubiak, % comment about q-driver
+Simon Law,
+Uwe L\"uck, % correction of typo
+Daniel Luecking, % typos
+Aditya Mahajan, % rewrite of q-context
+Sanjoy Mahajan,
+Diego Andres Alvarez Marin, % suggestion of lacheck
+Andreas Matthias, % most recently q-isitanum
+Steve Mayer, % proof reading
+Javier Mora, % bug in q-cmdstar
+Brooks Moses, % editorial suggestion
+Peter Moulder, % improvement of q-widows
+Iain Murray, % alternative solution in q-hyperdupdest
+Vilar Camara Neto, % explain breakurl pkg, suggest use of numprint
+Dick Nickalls,
+Ted Nieland,
+Hans Nordhaug,
+Pat Rau,
+Heiko Oberdiek,
+Piet van Oostrum,
+Scott Pakin, % bug reports (at least)
+Oren Patashnik,
+Manuel P\'egouri\'e-Gonnard, % improvement of q-luatex
+Steve Peter, % comprehensive review, lots of typos etc
+Sebastian Rahtz, % without whom there would be no...
+Philip Ratcliffe, % help with a bibtex oddity, editorial comment
+Chris Rowley, % founding father
+Jos\'e Carlos Santos, % assiduous reader of new versions
+Walter Schmidt,
+Hans-Peter Schr\"ocker,
+Joachim Schrod,
+Uwe Siart, % correction for manymathalph
+Maarten Sneep, % summary of c.t.t thread for outszwrng, inter alia
+Axel Sommerfeldt, % suggested rewrite of q-hyperdupdest
+Philipp Stephani, % xlation of komascript keyval stuff
+James Szinger, % who responded on c.t.t to request for answer
+Nicola Talbot, % correction of link
+Bob Tennent, % urw classico + sansmath
+Tomek Trzeciak, % suggested docmute and standalone together
+Ulrik Vieth,
+Mike Vulis, % details of micropress offerings
+Chris Walker, % revtex alert, ite suggestion (q-labelfig)
+Peter Wilson, % several, incl functionality of memoir
+Joseph Wright, % help with keyval, l3keys, etc.
+Rick Zaccone,
+Gregor Zattler % typo spotted
+and
+Reinhard Zierke.
+
+That list does \emph{not} cover the many people whose ideas were
+encountered on various mailing lists, in newsgroups, or (more
+recently!) in web forums. Many
+such people have helped, even if simply to highlight an area in which
+\acro{FAQ} work would be useful.
+\endhtmlignore
+% \LastEdit{2013-08-20} % not to be typeset or converted to html...
+\end{introduction}
diff --git a/help/uk-tex-faq/faq-jot-err.tex b/help/uk-tex-faq/faq-jot-err.tex
new file mode 100644
index 0000000000..3281e54a18
--- /dev/null
+++ b/help/uk-tex-faq/faq-jot-err.tex
@@ -0,0 +1,2467 @@
+% $Id: faq-jot-err.tex,v 1.25 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{The joy of \TeX{} errors}
+
+\Question[Q-erroradvice]{How to approach errors}
+
+Since \TeX{} is a macroprocessor, its error messages are often
+difficult to understand; this is a (seemingly invariant) property of
+macroprocessors. Knuth makes light of the problem in the \TeX{}book,
+suggesting that you acquire the sleuthing skills of a latter-day
+Sherlock Holmes; while this approach has a certain romantic charm to
+it, it's not good for the `production' user of \AllTeX{}. This
+answer (derived, in part, from an article by Sebastian Rahtz in
+\TUGboat{} 16(4)) offers some general guidance in dealing with \TeX{}
+error reports, and other answers in this section deal with common (but
+perplexing) errors that you may encounter. There's a long list of
+``hints'' in Sebastian's article, including the following:
+\begin{itemize}
+\item Look at \TeX{} errors; those messages may seem cryptic at first,
+ but they often contain a straightforward clue to the problem. See
+ \Qref[question]{the structure of errors}{Q-errstruct} for further
+ details.
+\item Read the \extension{log} file; it contains hints to things you may
+ not understand, often things that have not even presented as error
+ messages.
+\item Be aware of the amount of context that \TeX{} gives you. The
+ error messages gives you some bits of \TeX{} code (or of the
+ document itself), that show where the error ``actually happened'';
+ it's possible to control how much of this `context' \TeX{} actually
+ gives you. \LaTeX{} (nowadays) instructs \TeX{} only to give you
+ one line of context, but you may tell it otherwise by saying
+\begin{quote}
+\begin{verbatim}
+\setcounter{errorcontextlines}{999}
+\end{verbatim}
+\end{quote}
+ in the preamble of your document. (If you're not a confident macro
+ programmer, don't be ashamed of cutting that 999 down a bit; some
+ errors will go on and \emph{on}, and spotting the differences
+ between those lines can be a significant challenge.)
+\item As a last resort, tracing can be a useful tool; reading a full
+ \AllTeX{} trace takes a strong constitution, but once you know how,
+ the trace can lead you quickly to the source of a problem. You need
+ to have read the \TeX{}book (see
+% beware line break
+ \Qref[question]{books about \TeX{}}{Q-tex-books}) in some detail, fully
+ to understand the trace.
+
+ The command \csx{tracingall} sets up maximum tracing; it also sets
+ the output to come to the interactive terminal, which is somewhat of
+ a mixed blessing (since the output tends to be so vast~--- all but
+ the simplest traces are best examined in a text editor after the event).
+
+ The \LaTeX{} \Package{trace} package (first distributed with the
+ 2001 release of \LaTeX{}) provides more manageable tracing. Its
+ \csx{traceon} command gives you what \csx{tracingall} offers, but
+ suppresses tracing around some of the truly verbose parts of
+ \LaTeX{} itself. The package also provides a \csx{traceoff}
+ command (there's no ``off'' command for \csx{tracingall}), and a
+ package option (|logonly|) allows you to suppress output to the
+ terminal.
+\end{itemize}
+The best advice to those faced with \TeX{} errors is not to panic:
+most of the common errors are plain to the eye when you go back to the
+source line that \TeX{} tells you of. If that approach doesn't work,
+the remaining answers in this section deal with some of the odder
+error messages you may encounter. You should not ordinarily need to
+appeal to the \Qref*[question]{wider public}{Q-gethelp}
+for assistance, but if you do, be sure to
+report full backtraces (see |errorcontextlines| above) and so on.
+\begin{ctanrefs}
+\item[trace.sty]Distributed as part of \CTANref{2etools}[trace]
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-errstruct]{The structure of \TeX{} error messages}
+
+\TeX{}'s error messages are reminiscent of the time when \TeX{} itself
+was conceived (the 1970s): they're not terribly user-friendly, though
+they do contain all the information that \TeX{} can offer, usually in
+a pretty concise way.
+
+\TeX{}'s error reports all have the same structure:
+\begin{itemize}
+\item An error message
+\item Some `context'
+\item An error prompt
+\end{itemize}
+The error message will relate to the \emph{\TeX{}} condition that is
+causing a problem. Sadly, in the case of complex macro packages such
+as \LaTeX{}, the underlying \TeX{} problem may be superficially
+difficult to relate to the actual problem in the ``higher-level''
+macros. Many \LaTeX{}-detected problems manifest themselves as
+`generic' errors, with error text provided by \LaTeX{} itself (or by a
+\LaTeX{} class or package).
+
+The context of the error is a stylised representation of what \TeX{}
+was doing at the point that it detected the error. As noted in
+\Qref[question]{approaching errors}{Q-erroradvice}, a macro package
+can tell \TeX{} how much context to display, and the user may need to
+undo what the package has done. Each line of context is split at the
+point of the error; if the error \emph{actually} occurred in a macro
+called from the present line, the break is at the point of the call.
+(If the called object is defined with arguments, the ``point of call''
+is after all the arguments have been scanned.) For example:
+\begin{verbatim}
+\blah and so on
+\end{verbatim}
+produces the error report
+\begin{verbatim}
+! Undefined control sequence.
+l.4 \blah
+ and so on
+\end{verbatim}
+while:
+\begin{verbatim}
+\newcommand{\blah}[1]{\bleah #1}
+\blah{to you}, folks
+\end{verbatim}
+produces the error report
+\begin{verbatim}
+! Undefined control sequence.
+\blah #1->\bleah
+ #1
+l.5 \blah{to you}
+ , folks
+\end{verbatim}
+If the argument itself is in error, we will see things such as
+\begin{verbatim}
+\newcommand{\blah}[1]{#1 to you}
+\blah{\bleah}, folks
+\end{verbatim}
+producing
+\begin{verbatim}
+! Undefined control sequence.
+<argument> \bleah
+
+l.5 \blah{\bleah}
+ , folks
+\end{verbatim}
+
+The prompt accepts single-character commands: the list of what's
+available may be had by typing |?|\@. One immediately valuable
+command is |h|, which gives you an expansion of \TeX{}s original
+pr\'ecis message, sometimes accompanied by a hint on what to do to
+work round the problem in the short term. If you simply type `return'
+(or whatever else your system uses to signal the end of a line) at the
+prompt, \TeX{} will attempt to carry on (often with rather little
+success).
+
+\Question[Q-extrabrace]{An extra `\texttt{\cbracesymbol{}}'??}
+\keywords{caption heading}
+
+You've looked at your \LaTeX{} source and there's no sign of a misplaced
+\texttt{\cbracesymbol{}} on the line in question.
+
+Well, no: this is \TeX{}'s cryptic way of hinting that you've put a
+\begin{wideversion} % hyper
+\Qref{fragile command}{Q-protect} in a moving argument.
+\end{wideversion}
+\begin{narrowversion}
+fragile command in a moving argument (\Qref{}{Q-protect}).
+\end{narrowversion}
+
+For example, \csx{footnote} is fragile, and if we put that in the
+moving argument of a \csx{section} command, as
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\section{Mumble\footnote{%
+ I couldn't think of anything better}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\section{Mumble\footnote{I couldn't think of anything better}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+we get told
+\begin{quote}
+\begin{verbatim}
+! Argument of \@sect has an extra }.
+\end{verbatim}
+\end{quote}
+The same happens with captions (the following is a simplification of a
+\Newsgroup{comp.text.tex} post):
+\begin{quote}
+\begin{verbatim}
+\caption{Energy: \[e=mc^2\]}
+\end{verbatim}
+\end{quote}
+giving us the error message
+\begin{quote}
+\begin{verbatim}
+! Argument of \@caption has an extra }.
+\end{verbatim}
+\end{quote}
+The similar (but more sensible):
+\begin{quote}
+\begin{verbatim}
+\caption{Energy: \(e=mc^2\)}
+\end{verbatim}
+\end{quote}
+is more tiresome, still: there's no error when you first run the
+job~\dots{} but there is on the second pass, when the list of figures
+(or tables) is generated, giving:
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Bad math environment delimiter.
+\end{verbatim}
+\end{quote}
+in the \csx{listoffigures} processing.
+
+The solution is usually to use a robust command in place of the one
+you are using, or to force your command to be robust by prefixing it
+with \csx{protect}, which in the \csx{section} case would show as
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\section{Mumble\protect\footnote{%
+ I couldn't think of anything better}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\section{Mumble\protect\footnote{I couldn't think of anything better}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+However, in both the \csx{section} case and the \csx{caption} case,
+you can separate the moving argument, as in
+\cmdinvoke*{section}[moving]{static}; this gives us another standard
+route~--- simply to omit (or otherwise sanitise) the fragile command
+in the moving argument. So, one might rewrite the \csx{caption}
+example as:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\caption[Energy: (Einstein's equation)]%
+ {Energy: \(E=mc^2\)}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\caption[Energy: (Einstein's equation)]{Energy: \(E=mc^2\)}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+In practice, inserting mathematics in a moving argument has already
+been addressed in \latexe{} by the robust command \csx{ensuremath}:
+\begin{quote}
+\begin{verbatim}
+\caption{Energy: \ensuremath{E=mc^2}}
+\end{verbatim}
+\end{quote}
+So: always look for alternatives to the \csx{protect} route.
+
+Footnotes can be even more complex; % ! line break
+``\Qref*[question]{footnotes in \LaTeX{} section headings}{Q-ftnsect}''
+deals specifically with that issue.
+\LastEdit{2012-02-09}
+
+\Question[Q-semanticnest]{Capacity exceeded [semantic nest\,\dots{}]}
+
+\begin{narrowversion}
+\begin{verbatim}
+! TeX capacity exceeded, sorry [semantic nest
+ size=100].
+...
+If you really absolutely need more capacity,
+you can ask a wizard to enlarge me.
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+! TeX capacity exceeded, sorry [semantic nest size=100].
+...
+If you really absolutely need more capacity,
+you can ask a wizard to enlarge me.
+\end{verbatim}
+\end{wideversion}
+Even though \TeX{} suggests (as always) that enlargement by a wizard
+may help, this message usually results from a broken macro or bad
+parameters to an otherwise working macro.
+
+The ``semantic nest'' \TeX{} talks about is the nesting
+of boxes within boxes. A stupid macro can provoke the error pretty
+easily:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\def\silly{\hbox{here's \silly
+ being executed}}
+\silly
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\def\silly{\hbox{here's \silly being executed}}
+\silly
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+The extended traceback
+% beware of filling this line...
+(see \Qref{\emph{general advice} on errors}{Q-erroradvice})
+\emph{does} help, though it does rather run on. In the case above,
+the traceback consists of
+\begin{verbatim}
+\silly ->\hbox {
+ here's \silly being executed}
+\end{verbatim}
+followed by 100 instances of
+\begin{verbatim}
+\silly ->\hbox {here's \silly
+ being executed}
+\end{verbatim}
+The repeated lines are broken at exactly the offending macro; of
+course the loop need not be as simple as this~--- if \csx{silly} calls
+\csx{dopy} which boxes \csx{silly}, the effect is just the same and
+alternate lines in the traceback are broken at alternate positions.
+
+There are in fact two items being consumed when you nest boxes: the
+other is the grouping level. Whether you exhaust your % !line wrap
+\emph{semantic nest} or your permitted \emph{grouping levels} first is
+controlled entirely by the relative size of the two different sets of
+buffers in your \AllTeX{} executable.
+
+\Question[Q-noroom]{No room for a new `\emph{thing}'}
+
+The technology available to Knuth at the time \TeX{} was written is
+said to have been particularly poor at managing dynamic storage; as a
+result much of the storage used within \TeX{} is allocated as fixed
+arrays, in the reference implementations. Many of these fixed arrays
+are expandable in modern \TeX{} implementations, but size of the
+arrays of ``registers'' is written into the specification as being 256
+(usually); this number may not be changed if you still wish to call
+the result \TeX{}
+%% beware line wrap
+(see \Qref[question]{testing \TeX{} implementations}{Q-triptrap}).
+
+If you fill up one of these register arrays, you get a \TeX{} error
+message saying
+\begin{quote}
+\begin{verbatim}
+! No room for a new \<thing>.
+\end{verbatim}
+\end{quote}
+The \csx{thing}s in question may be \csx{count} (the object underlying
+\LaTeX{}'s \csx{newcounter} command), \csx{skip} (the object underlying
+\LaTeX{}'s \csx{newlength} command), \csx{box} (the object underlying
+\LaTeX{}'s \csx{newsavebox} command), or \csx{dimen}, \csx{muskip},
+\csx{toks}, \csx{read}, \csx{write} or \csx{language} (all types of object
+whose use is ``hidden'' in \LaTeX{}; the limit on the number of
+\csx{read} or \csx{write} objects is just 16).
+
+There is nothing that can directly be done about this error, as you can't
+extend the number of available registers without extending \TeX{}
+itself.
+\begin{htmlversion}
+ Of course, \Qref{\eTeX{}}{Q-etex}, \Qref{Omega}{Q-omegaleph} and
+ \Qref{\LuaTeX{}}{Q-luatex}
+\end{htmlversion}
+\htmlignore
+% beware line wrap here
+ Of course \Qref[question]{\etex{}}{Q-etex},
+ \Qref[question]{\ensuremath{\Omega}}{Q-omegaleph} and
+ \Qref[question]{\LuaTeX{}}{Q-luatex}
+\endhtmlignore
+all do this, as does \Qref*{MicroPress Inc's V\TeX{}}{Q-commercial}.
+
+The commonest way to encounter one of these error messages is to have
+broken macros of some sort, or incorrect usage of macros (an example
+is discussed in \Qref[question]{epsf problems}{Q-epsf}).
+
+However, sometimes one just \emph{needs} more than \TeX{} can offer,
+and when this happens, you've just got to work out a different way of
+doing things. An example is the % beware line wrap
+\Qref*{difficulty of loading \PiCTeX{} with \LaTeX{}}{Q-usepictex}.
+The more modern drawing package, \Package{pgf} with its higher-level
+interface \Package{TikZ} is also a common source of such problems.
+
+In such cases, it is usually possible to use the
+\Qref*{\eTeX{}}{Q-etex} extensions (all modern distributions provide
+them). The \LaTeX{} package \Package{etex} modifies the register allocation
+mechanism to make use of \eTeX{}'s extended register sets.
+\Package{Etex} is a
+derivative of the \plaintex{} macro file \Package{etex.src}, which is
+used in building the \eTeX{} Plain format; both files are part of the
+\eTeX{} distribution and are available in current distributions.
+
+It is possible that, even with \Package{etex} loaded, you still find
+yourself running out of things. Problems can be caused by packages
+that use large numbers of ``inserts'' (inserts are combinations of
+counter, box, dimension and skip registers, used for storing floats
+and footnotes). \Package{Morefloats} does this, of course (naturally enough,
+allocating new floats), and footnote packages such as
+\Package{manyfoot} and \Package{bigfoot} (which uses \Package{manyfoot})
+can also give problems. The \Package{etex} extensions allow you to deal with
+these things: the command \cmdinvoke*{reserveinserts}{n} ensures there
+is room for \meta{n} more inserts. Hint: by default
+\Package{morefloats} adds 18 inserts (though it can be instructed to
+use more), and \Package{manyfoot} seems to be happy with 10 reserved,
+but there are `hard' limits that we cannot program around~--- the
+discussion of \Qref*{running out of floats}{Q-tmupfl} has more about this.
+It is essential that you load \Package{etex} before any other
+packages, and reserve any extra inserts immediately:
+\begin{quote}
+\begin{verbatim}
+\documentclass[...]{...}
+\usepackage{etex}
+\reserveinserts{28}
+\end{verbatim}
+\end{quote}
+
+The \eTeX{} extensions don't help with \csx{read} or \csx{write}
+objects (and neither will the \Package{etex} package), but the
+\Package{morewrites} package can provide the \emph{illusion} of large
+numbers of \csx{write} objects.
+\begin{ctanrefs}
+\item[morewrites.sty]\CTANref{morewrites}
+\end{ctanrefs}
+
+\Question[Q-epsf]{\texttt{epsf} gives up after a bit}
+
+Some copies of the documentation of \File{epsf.tex} seemed once to
+suggest that the command
+\begin{verbatim}
+ \input epsf
+\end{verbatim}
+is needed for every figure included. If you follow this suggestion
+too literally, you get an error
+\begin{verbatim}
+ ! No room for a new \read .
+\end{verbatim}
+after a while; this is because each time \File{epsf.tex} is loaded, it
+allocates itself a \emph{new} file-reading handle to check the figure
+for its bounding box, and there just aren't enough of these things
+(see \Qref[question]{no room for a new thing}{Q-noroom}).
+
+The solution is simple~--- this is in fact an example of misuse of
+macros; one only need read \File{epsf.tex} once, so change
+\begin{verbatim}
+ ...
+ \input epsf
+ \epsffile{...}
+ ...
+ \input epsf
+ \epsffile{...}
+\end{verbatim}
+(and so on) with a single
+\begin{verbatim}
+ \input epsf
+\end{verbatim}
+somewhere near the start of your document, and then decorate your
+\csx{epsffile} statements with no more than adjustments of
+\csx{epsfxsize} and so on.
+
+\Question[Q-badhyph]{Improper \csx{hyphenation} will be flushed}
+
+For example
+\begin{verbatim}
+! Improper \hyphenation will be flushed.
+\'#1->{
+ \accent 19 #1}
+<*> \hyphenation{Ji-m\'e
+ -nez}
+\end{verbatim}
+(in \plaintex{}) or
+\begin{verbatim}
+! Improper \hyphenation will be flushed.
+\leavevmode ->\unhbox
+ \voidb@x
+<*> \hyphenation{Ji-m\'e
+ -nez}
+\end{verbatim}
+in \LaTeX{}.
+
+As mentioned in
+\begin{flatversion}
+ \Qref[question]{hyphenation failures}{Q-nohyph},
+\end{flatversion}
+\begin{hyperversion}
+ ``\Qref[question]{hyphenation failures}{Q-nohyph}'',
+\end{hyperversion}
+``words'' containing \csx{accent} commands may not be hyphenated. As
+a result, any such word is deemed improper in a \csx{hyphenation}
+command.
+
+Hyphenation happens as paragraphs are laid out; by this time, \tex{}
+knows what font is used for each glyph; thus it knows the encoding
+being used. So the solution to the problem is to use a font that
+contains the accented character; doing this this ``hides'' the accent
+from the hyphenation mechanisms.
+
+For \LaTeX{} users, this is quite an easy task; they select an 8-bit
+font with the package, as in \cmdinvoke{usepackage}[T1]{fontenc}, and
+accented-letter commands such as the \csx{'}\texttt{e} in
+\cmdinvoke{hyphenation}{Ji-m\csx{'}e-nez} automatically become the
+single accented character by the time the hyphenation gets to look at
+it.
+
+
+\Question[Q-optionclash]{Option clash for package}
+
+So you've innocently added:
+\begin{quote}
+\cmdinvoke{usepackage}[draft]{foo}
+\end{quote}
+to your document, and \LaTeX{} responds with
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! LaTeX Error: Option clash for package foo.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! LaTeX Error: Option clash for package foo.
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+
+The error is a complaint about loading a package % ! line break
+\emph{with options}, more than once. \LaTeX{} complains because it
+has no means of examining the options, rather than because it
+\emph{knows} there is a problem. (You may load a package any number
+of times in a document's preamble, with no options, and \LaTeX{} will
+ignore every loading request after the first; but you may only supply
+options when you first load the package.)
+
+So perhaps you weren't entirely innocent~--- the error would have
+occurred on the second line of:
+\begin{quote}
+\cmdinvoke{usepackage}[dvips]{graphics}\\
+\cmdinvoke{usepackage}[draft]{graphics}
+\end{quote}
+which could quite reasonably (and indeed correctly) have been typed:
+\begin{quote}
+\cmdinvoke{usepackage}[dvips,draft]{graphics}
+\end{quote}
+
+But if you've not made that mistake (even with several lines
+separating the \csx{usepackage} commands, it's pretty easy to spot),
+the problem could arise from something else loading the package for
+you. How do you find the culprit? The "\texttt{h}" response to the
+error message tells you which options were loaded each time.
+Otherwise, it's down to the log analysis games discussed in % ! line break
+``\Qref*{How to approach errors}{Q-erroradvice}''; the trick to remember
+is that that the process of loading each file is parenthesised in the
+log; so if package \Package{foo} loads \Package{graphics}, the log
+will contain something like:
+\begin{quote}
+\begin{verbatim}
+(<path>/foo.sty ...
+...
+(<path>/graphics.sty ...
+...)
+...
+)
+\end{verbatim}
+\end{quote}
+(the parentheses for \Package{graphics} are completely enclosed in
+those for \Package{foo}; the same is of course true if your class
+\Class{bar} is the culprit, except that the line will start with the
+path to \texttt{bar.cls}).
+
+If we're dealing with a package that loads the package you are
+interested in, you need to ask \LaTeX{} to slip in options when
+\Package{foo} loads it. Instead of:
+\begin{quote}
+\cmdinvoke{usepackage}{foo}\\
+\cmdinvoke{usepackage}[draft]{graphics}
+\end{quote}
+you would write:
+\begin{quote}
+\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\
+\cmdinvoke{usepackage}{foo}
+\end{quote}
+The command \csx{PassOptionsToPackage} tells \LaTeX{} to behave as if
+its options were passed, when it finally loads a package. As you would
+expect from its name, \csx{PassOptionsToPackage} can deal with a list
+of options, just as you would have in the the options brackets of
+\csx{usepackage}.
+
+The problem is more tricky if your document class loads a package you
+want options for. In this case, instead of:
+\begin{quote}
+\cmdinvoke{documentclass}[...]{bar}\\
+\cmdinvoke{usepackage}[draft]{graphics}
+\end{quote}
+you would write:
+\begin{quote}
+\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\
+\cmdinvoke{documentclass}[...]{bar}
+\end{quote}
+with \csx{PassOptionsToPackage} \emph{before} the \csx{documentclass}
+command.
+
+However, if the \Package{foo} package or the \Class{bar} class loads
+\Package{graphics} with an option of its own that clashes with
+what you need in some way, you're stymied. For example:
+\begin{quote}
+\cmdinvoke{PassOptionsToPackage}{draft}{graphics}
+\end{quote}
+where the package or class does:
+\begin{quote}
+\cmdinvoke{usepackage}[final]{graphics}
+\end{quote}
+sets \pkgoption{final} \emph{after} it's dealt with option you passed to
+it, so your \pkgoption{draft} will get forgotten. In extreme cases,
+the package might generate an error here (\Package{graphics} doesn't
+go in for that kind of thing, and there's no indication that
+\pkgoption{draft} has been forgotten).
+
+In such a case, you have to modify the package or class itself
+(subject to the terms of its licence). It may prove useful to contact
+the author: she may have a useful alternative to suggest.
+
+\Question[Q-optclash]{Option clash for package}
+
+The error message
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Option clash for package footmisc
+\end{verbatim}
+\end{quote}
+means what it says~--- your document contains a (potentially) clashing
+pair of options; sadly, it is not always obvious how the error has
+arisen.
+
+If you simply write:
+\begin{quote}
+\begin{verbatim}
+\usepackage[a]{foo}
+...
+\usepackage{foo}
+\end{verbatim}
+\end{quote}
+\latex{} is happy, as it is with:
+\begin{quote}
+\begin{verbatim}
+\usepackage[a]{foo}
+...
+\usepackage[a]{foo}
+\end{verbatim}
+\end{quote}
+since \latex{} can see there's no conflict (in fact, the second load
+does nothing).
+
+Similarly,
+\begin{quote}
+\begin{verbatim}
+\usepackage[a,b]{foo}
+...
+\usepackage[a]{foo}
+\end{verbatim}
+\end{quote}
+produces no error and does nothing for the second load.
+
+However
+\begin{quote}
+\begin{verbatim}
+\usepackage[a]{foo}
+...
+\usepackage[b]{foo}
+\end{verbatim}
+\end{quote}
+produces the error; even if option `\pkgoption{b}' is an alias for
+option `\pkgoption{a}'~--- \latex{} doesn't ``look inside'' the package
+to check anything like that.
+
+The general rule is: the first load of a package defines a set of
+options; if a further \csx{usepackage} or \csx{RequirePackage} also
+calls for the package, the options on that call may not extend the set
+on the first load.
+
+Fortunately, the error (in that sort of case) is easily curable
+once you've examined the preamble of your document.
+
+Now, suppose package \Package{foo} loads \Package{bar} with option
+\pkgoption{b}, and your document says:
+\begin{quote}
+\begin{verbatim}
+\usepackage{foo}
+...
+\usepackage[a]{bar}
+\end{verbatim}
+\end{quote}
+or
+\begin{quote}
+\begin{verbatim}
+\usepackage[a]{bar}
+...
+\usepackage{foo}
+\end{verbatim}
+\end{quote}
+the error will be detected, even though you have only explicitly
+loaded \Package{bar} once. Debugging such errors is tricky: it may
+involve reading the logs (to spot which packages were called), or the
+documentation of package \Package{foo}.
+
+\Question[Q-tmupfl]{``Too many unprocessed floats''}
+
+If \LaTeX{} responds to a \cmdinvoke{begin}{figure} or
+\cmdinvoke{begin}{table} command with the error message
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion
+... for explanation.
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+your figures (or tables) are not being placed properly. \LaTeX{}
+has a limited amount of storage for `floats' (figures, tables, or
+floats you've defined yourself with the \Package{float} package); if
+something you have done has prevented \latex{} from typesetting
+floats, it will run out of storage space.
+
+This failure usually occurs in extreme cases of % ! line break
+\Qref*{floats moving ``wrongly''}{Q-floats};
+\LaTeX{} has found it can't place a float, and floats of the same type
+have piled up behind it.
+
+How does this happen?~--- \LaTeX{} guarantees that caption numbers are
+sequential in the document, but the caption number is allocated when
+the figure (or whatever) is created, and can't be changed. Thus, if
+floats are placed out of order, their caption numbers would also
+appear out of order in the body of the document (and in the list of
+figures, or whatever). As a result, enforcement of the guarantee
+means that simple failure to place a float means that no subsequent
+float can be placed; and hence (eventually) the error.
+
+Techniques for solving the problem are discussed in the % ! line break
+\Qref*{floats question}{Q-floats} already referenced.
+
+An alternative \emph{may} be to use the \Package{morefloats} package.
+The package will allocate more ``float skeletons'' than \latex{}
+does by default; each such skeleton may then be used to store a
+float. Beware that even with \Package{morefloats}, the number you can
+allocate is limited; even with the \Package{etex} package (which makes
+available many more registers, etc., than \latex{} does by default;
+\etex{} can create lots more registers, but none of those ``beyond
+the original \TeX{} default'' may be used in float skeletons). Thus,
+\Package{etex} may offer some relief, but it can \emph{not} be
+regarded as a panacea
+
+The error also occurs in a long sequence of float environments, with
+no intervening text. Unless the environments will fit ``here'' (and
+you've allowed them to go ``here''), there will never be a page break,
+and so there will never be an opportunity for \LaTeX{} to reconsider
+placement. (Of course, the floats can't all fit ``here'' if the
+sequence is sufficiently prolonged: once the page fills, \LaTeX{}
+won't place any more floats, leading to the error.
+
+Techniques for resolution may involve redefining the floats using the
+\Package{float} package's \texttt{[H]} float qualifier, but you are unlikely
+to get away without using \csx{clearpage} from time to time.
+\begin{ctanrefs}
+\item[float.sty]\CTANref{float}
+\item[morefloats.sty]\CTANref{morefloats}
+\end{ctanrefs}
+
+\Question[Q-atvert]{\csx{spacefactor} complaints}
+
+The errors
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+! You can't use `\spacefactor' in
+... vertical mode.
+\@->\spacefactor
+ \@m
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+! You can't use `\spacefactor' in vertical mode.
+\@->\spacefactor
+ \@m
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+or
+\begin{quote}
+\begin{verbatim}
+! You can't use `\spacefactor' in math mode.
+\@->\spacefactor
+ \@m
+\end{verbatim}
+\end{quote}
+or simply
+\begin{quote}
+\begin{verbatim}
+! Improper \spacefactor.
+...
+\end{verbatim}
+\end{quote}
+bite the \LaTeX{} programmer who uses an internal command without
+taking ``precautions''. An internal-style command such as \csx{@foo}
+has been defined or used in a private macro, and it is interpreted as
+\csx{@}, followed by the `text' \texttt{foo}. (\csx{@} is used, for
+real, to set up end-of-sentence space in some circumstances; it uses
+\csx{spacefactor} to do that.)
+
+The problem is discussed in detail in
+% beware line wrap
+``\Qref*[question]{\texttt{@} in macro names}{Q-atsigns}'',
+together with solutions.
+
+\Question[Q-endingroup]{\csx{end} occurred inside a group}
+
+The actual error we observe is:
+
+\nothtml{\noindent}%
+|(\end occurred inside a group at level <|\texttt{\emph{n}}|>)|
+
+\nothtml{\noindent}%
+and it tells us that something we started in the document never got
+finished before we ended the document itself. The things involved
+(`groups') are what \TeX{} uses for restricting the scope of things:
+you see them, for example, in the ``traditional'' font selection
+commands: |{\it stuff\/}|~--- if the closing brace is left off such a
+construct, the effect of \csx{it} will last to the end of the document,
+and you'll get the diagnostic.
+
+\TeX{} itself doesn't tell you where your problem is, but you can
+often spot it by looking at the typeset output in a previewer.
+Otherwise, you can usually find mismatched braces using an intelligent
+editor (at least \ProgName{emacs} and \ProgName{winedt} offer this facility).
+However, groups are not \emph{only} created by matching
+\texttt{\obracesymbol{}} with \texttt{\cbracesymbol{}}:
+other grouping commands are discussed elsewhere in these \acro{FAQ}s,
+and are also a potential source of unclosed group.
+
+\cmdinvoke{begin}{\meta{environment}} encloses the environment's body
+in a group, and establishes its own diagnostic mechanism. If you end
+the document before closing some other environment, you get the
+`usual' \LaTeX{} diagnostic
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+! LaTeX Error: \begin{blah} on input line 6
+ ended by \end{document}.
+\end{verbatim}
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+! LaTeX Error: \begin{blah} on input line 6 ended by \end{document}.
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+! LaTeX Error: \begin{blah} on input line 6 ended by \end{document}.
+\end{verbatim}
+\end{htmlversion}
+which (though it doesn't tell you which \emph{file} the
+\cmdinvoke{begin}{blah} was in) is usually enough to locate the
+immediate problem. If you press on past the \LaTeX{} error, you get
+one or more repetitions of the ``occurred inside a group'' message
+before \LaTeX{} finally exits. The \Package{checkend} package
+recognises other unclosed \cmdinvoke{begin}{blob} commands, and
+generates an ``ended by'' error message for each one, rather than
+producing the ``occurred inside a group'' message, which is sometimes
+useful (if you remember to load the package).
+
+In the absence of such information from \LaTeX{}, you need to use
+``traditional'' binary search to find the offending group. Separate
+the preamble from the body of your file, and process each half on its
+own with the preamble; this tells you which half of the file is at
+fault. Divide again and repeat. The process needs to be conducted
+with care (it's obviously possible to split a correctly-written group
+by chopping in the wrong place), but it will usually find the problem
+fairly quickly.
+
+\eTeX{} (and \elatex{}~--- \LaTeX{} run on \eTeX{}) gives you
+further diagnostics after the traditional infuriating \TeX{} one~--- it
+actually keeps the information in a similar way to \LaTeX{}:
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+(\end occurred inside a group at level 3)
+
+### semi simple group (level 3) entered
+ at line 6 (\begingroup)
+### simple group (level 2) entered at line 5 ({)
+### simple group (level 1) entered at line 4 ({)
+### bottom level
+\end{verbatim}
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+(\end occurred inside a group at level 3)
+
+### semi simple group (level 3) entered at line 6 (\begingroup)
+### simple group (level 2) entered at line 5 ({)
+### simple group (level 1) entered at line 4 ({)
+### bottom level
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+(\end occurred inside a group at level 3)
+
+### semi simple group (level 3) entered at line 6 (\begingroup)
+### simple group (level 2) entered at line 5 ({)
+### simple group (level 1) entered at line 4 ({)
+### bottom level
+\end{verbatim}
+\end{htmlversion}
+The diagnostic not only tells us where the group started, but also the
+\emph{way} it started: \csx{begingroup} or |{| (which is an alias of
+\csx{bgroup}, and the two are not distinguishable at the \TeX{}-engine
+level).
+\begin{ctanrefs}
+\item[checkend.sty]Distributed as part of \CTANref{bezos}[checkend]
+\end{ctanrefs}
+
+\Question[Q-nonum]{``Missing number, treated as zero''}
+
+In general, this means you've tried to assign something to a count,
+dimension or skip register that isn't (in \TeX{}'s view of things) a
+number. Usually the problem will become clear using the
+\Qref*{ordinary techniques of examining errors}{Q-erroradvice}.
+
+Two \LaTeX{}-specific errors are commonly aired on the newsgroups.
+
+The commonest arises from attempting to use an example from the
+\Qref*{\emph{The \LaTeX{} Companion} (first edition)}{Q-latex-books}, and is
+exemplified by the following error text:
+\begin{verbatim}
+! Missing number, treated as zero.
+<to be read again>
+ \relax
+l.21 \begin{Ventry}{Return values}
+\end{verbatim}
+The problem arises because, in its first edition, the
+\emph{Companion}'s examples always assumed that the \Package{calc}
+package is loaded: this fact is mentioned in the book, but often not
+noticed. The remedy is to load the \Package{calc} package in any
+document using such examples from the \emph{Companion}. (The problem
+does not really arise with the second edition; copies of all the
+examples are available on the accompanying \CDROM{}, or on
+\acro{CTAN}.)
+
+The other problem, which is increasingly rare nowadays, arises from
+misconfiguration of a system that has been upgraded from \LaTeXo{}:
+the document uses the \Package{times} package, and the error appears
+at \cmdinvoke{begin}{document}. The file search paths are wrongly set
+up, and your \cmdinvoke{usepackage}{times} has picked up a \LaTeXo{}
+version of the package, which in its turn has invoked another which
+has no equivalent in \LaTeXe{}. The obvious solution is to rewrite
+the paths so that \LaTeXo{} packages are chosen only as a last resort
+so that the startlingly simple \LaTeXe{} \Package{times} package will
+be picked up. Better still is to replace the whole thing with
+something more modern still; current \Package{psnfss} doesn't provide
+a \Package{times} package~--- the alternative \Package{mathptmx}
+incorporates \FontName{Times}-like mathematics, and a sans-serif face
+based on \FontName{Helvetica}, but scaled to match \FontName{Times}
+text rather better.
+\begin{ctanrefs}
+\item[calc.sty]Distributed as part of \CTANref{2etools}[calc]
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2}
+\item[The psnfss bundle]\CTANref{psnfss}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-typend]{``Please type a command or say \csx{end}''}
+
+Sometimes, when you are running \AllTeX{}, it will abruptly stop and
+present you with a prompt (by default, just a |*| character). Many
+people (including this author) will reflexively hit the `return'
+key, pretty much immediately, and of course this is no help at all~---
+\TeX{} just says:
+\begin{verbatim}
+(Please type a command or say `\end')
+\end{verbatim}
+and prompts you again.
+
+What's happened is that your \AllTeX{} file has finished prematurely,
+and \TeX{} has fallen back to a supposed including file, from the
+terminal. This could have happened simply because you've omitted
+the \csx{bye} (\plaintex{}), \cmdinvoke{end}{document} (\LaTeX{}), or
+whatever. Other common errors are failure to close the braces round a
+command's argument, or (in \LaTeX{}) failure to close a verbatim
+environment: in such cases you've already read and accepted an
+error message about encountering end of file while scanning something.
+
+If the error is indeed because you've forgotten to end your document,
+you can insert the missing text: if you're running \plaintex{}, the
+advice, to ``say \csx{end}'' is good enough: it will kill the run; if
+you're running \LaTeX{}, the argument will be necessary:
+\cmdinvoke{end}{document}.
+
+However, as often as not this isn't the problem, and (short of
+debugging the source of the document before ending) brute force is
+probably necessary. Excessive force (killing the job that's
+running \TeX{}) is to be avoided: there may well be evidence in the
+\extension{log} file that will be useful in determining what the
+problem is~--- so the aim is to persuade \TeX{} to shut itself down
+and hence flush all log output to file.
+
+If you can persuade \TeX{} to read it, an end-of-file indication
+(control-|D| under Unix, control-|Z| under Windows) will provoke
+\TeX{} to report an error and exit immediately. Otherwise you should
+attempt to provoke an error dialogue, from which you can exit (using
+the |x| `command'). An accessible error could well be inserting an
+illegal character: what it is will depend on what macros you are
+running. If you can't make that work, try a silly command name or
+two.
+
+\Question[Q-unkgrfextn]{``Unknown graphics extension''}
+
+The \LaTeX{} graphics package deals with several different types of
+\acro{DVI} (or other) output drivers; each one of them has a potential
+to deal with a different selection of graphics formats. The package
+therefore has to be told what graphics file types its output driver
+knows about; this is usually done in the \meta{driver}\extension{def} file
+corresponding to the output driver you're using.
+
+The error message arises, then, if you have a graphics file whose
+extension doesn't correspond with one your driver knows about. Most
+often, this is because you're being optimistic: asking
+\ProgName{dvips} to deal with a \extension{png} file, or \PDFTeX{} to deal with
+a \extension{eps} file: the solution in this case is to transform the graphics
+file to a format your driver knows about.
+
+If you happen to \emph{know} that your device driver deals with the
+format of your file, you are probably falling foul of a limitation of
+the file name parsing code that the graphics package uses. Suppose
+you want to include a graphics file \File{home.bedroom.eps} using the
+\ProgName{dvips} driver; the package will conclude that your file's
+extension is \extension{bedroom.eps}, and will complain.
+
+The \Package{grffile} package deals with the last problem (and
+others~--- see the package documentation); using the package, you may
+write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{graphicx}
+\usepackage{grffile}
+...
+\includegraphics{home.bedroom.eps}
+\end{verbatim}
+\end{quote}
+or you may even write
+\begin{quote}
+\begin{verbatim}
+\includegraphics{home.bedroom}
+\end{verbatim}
+\end{quote}
+and \Package{graphicx} will find a \extension{eps} or \extension{pdf}
+(or whatever) version, according to what version of \AllTeX{} you're
+running.
+
+If for some reason you can't use \Package{grffile}, you have three
+unsatisfactory alternatives:
+\begin{itemize}
+\item Rename the file~--- for example \File{home.bedroom.eps}\arrowhyph{}%
+ \File{home-bedroom.eps}
+\item Mask the first dot in the file name:
+\begin{verbatim}
+\newcommand*{\DOT}{.}
+\includegraphics{home\DOT bedroom.eps}
+\end{verbatim}
+\item Tell the graphics package what the file is, by means of options
+ to the \csx{includegraphics} command:
+\begin{narrowversion}
+\begin{verbatim}
+\includegraphics[type=eps,ext=.eps,
+ read=.eps]{home.bedroom}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom}
+\end{verbatim}
+\end{wideversion}
+\end{itemize}
+\begin{ctanrefs}
+\item[grffile.sty]Distributed as part of the Oberdiek collection
+ \CTANref{oberdiek}[grffile]
+\end{ctanrefs}
+
+\Question[Q-nodollar]{``Missing \texttt{\$} inserted''}
+
+There are certain things that \emph{only} work in maths mode. If your
+document is not in maths mode and you have an |_| or a |^| character,
+\TeX{} (and by inheritance, \LaTeX{} too) will say
+\begin{verbatim}
+! Missing $ inserted
+\end{verbatim}
+as if you couldn't possibly have misunderstood the import of what you
+were typing, and the only possible interpretation is that you had
+committed a typo in failing to enter maths mode. \TeX{}, therefore,
+tries to patch things up by inserting the \texttt{\$} you `forgot', so that
+the maths-only object will work; as often as not this will land you in
+further confusion.
+
+It's not just the single-character maths sub- and superscript
+operators: anything that's built in or declared as a maths operation,
+from the simplest lower-case \csx{alpha} through the inscrutable
+\csx{mathchoice} primitive, and beyond, will provoke the error if
+misused in text mode.
+
+\LaTeX{} offers a command \csx{ensuremath}, which will put you in maths
+mode for the execution of its argument, if necessary: so if you want
+an \csx{alpha} in your running text, say
+\cmdinvoke{ensuremath}{\csx{alpha}}; if the bit of running text somehow
+transmutes into a bit of mathematics, the \csx{ensuremath} will become
+a no-op, so it's pretty much always safe.
+
+\Question[Q-fontunavail]{Warning: ``Font shape \dots{}\ not available''}
+
+\LaTeX{}'s font selection scheme maintains tables of the font families
+it has been told about. These tables list the font families that
+\LaTeX{} knows about, and the shapes and series in which those font
+families are available. In addition, in some cases, the tables list
+the sizes at which \LaTeX{} is willing to load fonts from the family.
+
+When you specify a font, using one of the \LaTeX{} font selection
+commands, \LaTeX{} looks for the font (that is, a font that matches
+the encoding, family, shape, series and size that you want) in its
+tables. If the font isn't there at the size you want, you will see a
+message like:
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/m/n' in
+... size <11.5> not available
+(Font) size <12> substituted on
+... input line ...
+\end{verbatim}
+(All the message texts in this answer have been wrapped so that they
+will fit in the narrow columns of this version of the \acro{FAQ}. The
+continuation marker is |...| at the start of the broken-off portion of
+the line.)
+
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <11.5> not available
+(Font) size <12> substituted on input line ...
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <11.5> not available
+(Font) size <12> substituted on input line ...
+\end{verbatim}
+\end{htmlversion}
+There will also be a warning like:
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+LaTeX Font Warning: Size substitutions with
+... differences
+(Font) up to 0.5pt have occurred.
+\end{verbatim}
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+LaTeX Font Warning: Size substitutions with differences
+(Font) up to 0.5pt have occurred.
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+LaTeX Font Warning: Size substitutions with differences
+(Font) up to 0.5pt have occurred.
+\end{verbatim}
+\end{htmlversion}
+after \LaTeX{} has encountered \cmdinvoke{end}{document}.
+
+The message tells you that you've chosen a font size that is not in
+\LaTeX{}'s list of ``allowed'' sizes for this font; \LaTeX{} has
+chosen the nearest font size it knows is allowed. In fact, you can
+tell \LaTeX{} to allow \emph{any} size: the restrictions come from the
+days when only bitmap fonts were available, and they have never
+applied to fonts that come in scaleable form in the first place.
+Nowadays, most of the fonts that were once bitmap-only are also
+available in scaleable (Adobe Type~1) form. If your installation uses
+scaleable versions of the Computer Modern or European Computer Modern
+(\acro{EC}) fonts, you can tell \LaTeX{} to remove the restrictions;
+use the \Package{type1cm} or \Package{type1ec} package as appropriate.
+
+If the combination of font shape and series isn't available, \LaTeX{}
+will usually have been told of a fall-back combination that may be
+used, and will select that:
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/bx/sc'
+... undefined
+(Font) using `OT1/cmr/bx/n'
+... instead on input line 0.
+\end{verbatim}
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined
+(Font) using `OT1/cmr/bx/n' instead on input line 0.
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined
+(Font) using `OT1/cmr/bx/n' instead on input line 0.
+\end{verbatim}
+\end{htmlversion}
+
+Substitutions may also be ``silent''; in this case, there is no more
+than an ``information'' message in the log file. For example, if you
+specify an encoding for which there is no version in the current font
+family, the `default family for the encoding' is selected. This
+happens, for example, if you use command \csx{textbullet}, which is
+normally taken from the maths symbols font, which is in |OMS|
+encoding. My test log contained:
+\htmlignore
+\begin{dviversion}
+\begin{verbatim}
+LaTeX Font Info: Font shape `OMS/cmr/m/n' in
+... size <10> not available
+(Font) Font shape `OMS/cmsy/m/n'
+... tried instead on input
+... line ...
+\end{verbatim}
+\end{dviversion}
+\begin{pdfversion}
+\begin{verbatim}
+LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line ...
+\end{verbatim}
+\end{pdfversion}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line ...
+\end{verbatim}
+\end{htmlversion}
+
+In summary, these messages are not so much error messages, as
+information messages, that tell you what \LaTeX{} has made of your
+text. You should check what the messages say, but you will ordinarily
+not be surprised at their content.
+\begin{ctanrefs}
+\item[type1cm.sty]\CTANref{type1cm}
+\item[type1ec.sty]\CTANref{type1ec}
+\end{ctanrefs}
+
+\Question[Q-buffovl]{Unable to read an entire line}
+
+\TeX{} belongs to the generation of applications written for
+environments that didn't offer the sophisticated string and i/o
+manipulation we nowadays take for granted (\TeX{} was written in
+Pascal, and the original Pascal standard made no mention of i/o, so
+that anything but the most trivial operations were likely to be
+unportable).
+
+When you overwhelm \TeX{}'s input mechanism, you get told:
+\begin{verbatim}
+! Unable to read an entire line---bufsize=3000.
+ Please ask a wizard to enlarge me.
+\end{verbatim}
+(for some value of `3000'~--- the quote was from a
+\Newsgroup{comp.text.tex} posting by a someone who was presumably
+using an old \TeX{}).
+
+As the message implies, there's (what \TeX{} thinks of as a) line in
+your input that's ``too long'' (to \TeX{}'s way of thinking). Since
+modern distributions tend to have tens of thousands of bytes of input
+buffer, it's somewhat rare that these messages occur ``for real''.
+Probable culprits are:
+\begin{itemize}
+\item A file transferred from another system, without translating
+ record endings. With the decline of fixed-format records (on
+ mainframe operating systems) and the increased intelligence of
+ \TeX{} distributions at recognising other systems' explicit
+ record-ending characters, this is nowadays rather a rare cause of
+ the problem.
+\item A graphics input file, which a package is examining for its
+ bounding box, contains a binary preview section. Again,
+ sufficiently clever \TeX{} distributions recognise this situation,
+ and ignore the previews (which are only of interest, if at all, to a
+ \TeX{} previewer).
+\end{itemize}
+
+The usual advice is to ignore what \TeX{} says (i.e., anything about
+enlarging), and to put the problem right in the source.
+
+If the real problem is over-long text lines, most self-respecting text
+editors will be pleased to automatically split long lines (while
+preserving the ``word'' structure) so that they are nowhere any longer
+than a given length; so the solution is just to edit the file.
+
+If the problem is a ridiculous preview section, try using
+\href{http://www.ghostscript.com/}{\ProgName{ghostscript}}
+to reprocess the file, outputting a ``plain
+\extension{eps}'' file. (\ProgName{Ghostscript}'s distribution
+includes a script \ProgName{ps2epsi} which will regenerate the preview
+if necessary.) Users of the shareware program % ! line break
+\href{http://www.ghostgum.com.au/}{\ProgName{gsview}}
+will find buttons to perform the required transformation of the file
+being displayed.
+\LastEdit{2013-06-03}
+
+\Question[Q-formatstymy]{``Fatal format file error; I'm stymied''}
+
+\AllTeX{} applications often fail with this error when you've been
+playing with the configuration, or have just installed a new version.
+
+The format file contains the macros that define the system you want to
+use: anything from the simplest (\plaintex{}) all the way to the most
+complicated, such as \LaTeX{} or \CONTeXT{}. From the command you
+issue, \TeX{} knows which format you want.
+
+The error message
+\begin{verbatim}
+ Fatal format file error; I'm stymied
+\end{verbatim}
+means that \TeX{} itself can't understand the format you want.
+Obviously, this could happen if the format file had got corrupted, but
+it usually doesn't. The commonest cause of the message, is that a new
+binary has been installed in the system: no two \TeX{} binaries on the
+same machine can
+understand each other's formats. So the new version of \TeX{} you
+have just installed, won't understand the format generated by the one
+you installed last year.
+
+Resolve the problem by regenerating the format; of course, this
+depends on which system you are using.
+\begin{itemize}
+\item On a te\TeX{}-based system, run
+\begin{verbatim}
+ fmtutil --all
+\end{verbatim}
+ or
+\begin{verbatim}
+ fmtutil --byfmt=<format name>
+\end{verbatim}
+ to build only the format that you are interested in.
+\item On a \miktex{} system, click \texttt{Start}\arrowhyph{}%
+\texttt{Programs}\arrowhyph{}%
+\texttt{\miktex{} \emph{version}}\arrowhyph{}%
+\texttt{\miktex{} Options}, and in the options window, click
+ \texttt{Update now}.
+\end{itemize}
+
+\Question[Q-nonpdfsp]{Non-\acro{PDF} special ignored!}
+
+This is a \PDFTeX{} error: \PDFTeX{} is running in \acro{PDF} output
+% beware line break at end line
+mode, and it has encountered a \nothtml{\csx{special} command (}%
+\Qref{\csx{special}}{Q-specials}\latexhtml{)}{ command}. \PDFTeX{} is
+able to generate its own output, and in this mode of operation has no
+need of \csx{special} commands (which allow the user to pass
+information to the driver being used to generate output).
+
+Why does this happen? \LaTeX{} users, nowadays, hardly ever use
+\csx{special} commands on their own~--- they employ packages to do the
+job for them. Some packages will generate \csx{special} commands
+however they are invoked: \Package{pstricks} is an example (it's very
+raison d'\^etre is to emit \PS{} code in a sequence of \csx{special}
+commands). \Package{Pstricks} may be dealt with by other means (the
+\Package{pdftricks} package offers a usable technique).
+
+More amenable to correction, but more confusing, are packages (such as
+\Package{color}, \Package{graphics} and \Package{hyperref}) that
+specify a ``driver''. These packages have plug-in modules that
+determine what \csx{special} (or other commands) are needed to generate
+any given effect: the \texttt{pdftex} driver for such packages knows not to
+generate \csx{special} commands. In most circumstances, you can let
+the system itself choose which driver you need; in this case
+everything will act properly when you switch to using \PDFLaTeX{}. If
+you've been using \ProgName{dvips} (and specifying the |dvips| driver)
+or \ProgName{dvipdfm} (for which you have to specify the driver), and
+decide to try \PDFLaTeX{}, you \emph{must} remove the |dvips| or
+|dvipdfm| driver specification from the package options, and let the
+system recognise which driver is needed.
+\begin{ctanrefs}
+\item[pdftricks.sty]\CTANref{pdftricks}
+\item[pstricks.sty]\CTANref{pstricks}
+\end{ctanrefs}
+
+\Question[Q-8000]{Mismatched mode ljfour and resolution 8000}
+
+You're running \ProgName{dvips}, and you encounter a stream of error
+messages, starting with ``\texttt{Mismatched mode}''. The mode is the
+default used in your installation~--- it's set in the \ProgName{dvips}
+configuration file, and \texttt{ljfour} is commonest (since it's the
+default in most distributions), but not invariable.
+
+The problem is that \ProgName{dvips} has encountered a font for which
+it must generate a bitmap (since it can't find it in Type~1 format),
+and there is no proforma available to provide instructions to give to
+\MF{}.
+
+So what to do? The number 8000 comes from the `\texttt{-Ppdf}' option
+to \ProgName{dvips}, which you might have found from the answer
+\nothtml{``wrong type of fonts'' (}% beware % beware line breaks
+\Qref{``wrong type of fonts''}{Q-fuzzy-type3}\nothtml{)}. The obvious
+solution is to switch to the trivial substitute `\texttt{-Pwww}',
+which selects the necessary type~1 fonts for \acro{PDF} generation,
+but nothing else: however, this will leave you with undesirable bitmap
+fonts in your \acro{PDF} file. The ``proper'' solution is to find a
+way of expressing what you want to do, using type~1 fonts.
+
+\Question[Q-toodeep]{``Too deeply nested''}
+
+This error appears when you start a \LaTeX{} list.
+
+\LaTeX{} keeps track of the nesting of one list inside another. There
+is a set of list formatting parameters built-in for application to
+each of the list nesting levels; the parameters determine indentation,
+item separation, and so on. The \environment{list} environment (the
+basis for list environments like \environment{itemize} and
+\environment{enumerate}) ``knows'' there are only 6 of these sets.
+
+There are also different label definitions for the
+\environment{enumerate} and \environment{itemize} environments at
+their own private levels of nesting. Consider this example:
+\begin{quote}
+\begin{verbatim}
+\begin{enumerate}
+\item first item of first enumerate
+ \begin{itemize}
+ \item first item of first itemize
+ \begin{enumerate}
+ \item first item of second enumerate
+ ...
+ \end{enumerate}
+ ...
+ \end{itemize}
+...
+\end{enumerate}
+\end{verbatim}
+\end{quote}
+In the example,
+\begin{itemize}
+\item the first \environment{enumerate} has labels as for a
+ first-level \environment{enumerate}, and is indented as for a
+ first-level list;
+\item the first \environment{itemize} has labels as for a first level
+ \environment{itemize}, and is indented as for a second-level list;
+ and
+\item the second \environment{enumerate} has labels as for a
+ second-level \environment{enumerate}, and is indented as for a
+ third-level list.
+\end{itemize}
+Now, as well as \LaTeX{} \emph{knowing} that there are 6~sets of
+parameters for indentation, it also \emph{knows} that there are only
+4~types of labels each, for the environments \environment{enumerate}
+and \environment{itemize} (this ``knowledge'' spells out a requirement
+for class writers, since the class supplies the sets of parameters).
+
+From the above, we can deduce that there are several ways we can run
+out of space: we can have 6~lists (of any sort) nested, and try to
+start a new one; we can have 4~\environment{enumerate} environments
+somewhere among the set of nested lists, and try to add another one;
+and we can have 4~\environment{itemize} environments somewhere among
+the set of nested lists, and try to add another one.
+
+What can be done about the problem? Not much, short of rewriting
+\LaTeX{}~--- you really need to rewrite your document in a slightly
+less labyrinthine way.
+
+\Question[Q-inputlev]{Capacity exceeded~--- input levels}
+
+The error
+\begin{wideversion}
+\begin{verbatim}
+! TeX capacity exceeded, sorry [text input levels=15].
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! TeX capacity exceeded, sorry
+ [text input levels=15].
+\end{verbatim}
+\end{narrowversion}
+is caused by nesting your input too deeply. You can provoke it with
+the trivial (\plaintex{}) file \File{input.tex}, which contains
+nothing but:
+\begin{verbatim}
+\input input
+\end{verbatim}
+In the real world, you are unlikely to encounter the error with a
+modern \TeX{} distribution. Te\TeX{} (used to produce the error
+message above) allows 15 files open for \TeX{} input at any one time,
+which is improbably huge for a document generated by real human
+beings.
+
+However, for those improbable (or machine-generated) situations,
+some distributions offer the opportunity to adjust the parameter
+|max_in_open| in a configuration file.
+
+\Question[Q-hyperdupdest]{\PDFTeX{} destination \dots{}\ ignored}
+
+The warning:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! pdfTeX warning (ext4): destination with the same identifier
+(name{page.1}) has been already used, duplicate ignored
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! pdfTeX warning (ext4): destination with
+ the same identifier (name{page.1}) has
+ been already used, duplicate ignored
+\end{verbatim}
+{\small NB: message text wrapped to fit in the column\par}
+\end{narrowversion}
+\end{quote}
+arises because of duplicate page numbers in your document. The
+problem is usually soluble: see % beware line break
+\Qref*[question]{\acro{PDF} page destinations}{Q-pdfpagelabels}~--- which
+answer also describes the problem in more detail.
+
+If the identifier in the message is different, for example
+\texttt{name\{figure.1.1\}}, the problem is (often) due to a problem of
+package interaction. The \File{README} in the \Package{hyperref}
+distribution mentions some of these issues~--- for example,
+\environment{equation} and \environment{eqnarray} as supplied by the
+\Package{amsmath} package; means of working around the problem are
+typically supplied there.
+
+Some packages are simply incompatible with
+\Package{hyperref}, but most work simply by ignoring it. In most
+cases, therefore, you should load your package before you load
+\Package{hyperref}, and \Package{hyperref} will patch things up so
+that they work, so you can utilise your (patched) package \emph{after}
+loading both:
+\begin{quote}
+ \cmdinvoke{usepackage}{\emph{your package}}\\
+ \texttt{...}\\
+ \cmdinvoke{usepackage}[\emph{opts}]{hyperref}\\
+ \texttt{...}\\
+ \meta{code that uses your package}
+\end{quote}
+\begin{wideversion}
+For example:
+\begin{quote}
+\begin{verbatim}
+\usepackage{float} % defines \newfloat
+...
+\usepackage[...]{hyperref} % patches \newfloat
+...
+\newfloat{...}{...}{...}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+So, if we need \csx{newfloat}:
+\begin{quote}
+\cmdinvoke{usepackage}{float}
+\end{quote}
+will define the command,
+\begin{quote}
+\cmdinvoke{usepackage}[\emph{opts}]{hyperref}
+\end{quote}
+will patch it, and now:
+\begin{quote}
+\cmdinvoke{newfloat}{...}{...}{...}
+\end{quote}
+will use the command, patched to create `proper' hyperreferences.
+\end{narrowversion}
+You should load packages in this order as a matter of course, unless
+the documentation of a package says you \emph{must} load it after
+\Package{hyperref}. (There are few packages that require to be
+loaded after hyperref: one such is \Class{memoir}'s
+``\Package{hyperref} fixup'' package \Package{memhfixc}.)
+
+If loading your packages in the (seemingly) ``correct'' order doesn't
+solve the problem, you need to \Qref*{seek further help}{Q-gethelp}.
+
+\Question[Q-altabcr]{Alignment tab changed to \csx{cr}}
+
+This is an error you may encounter in \LaTeX{} when a tabular
+environment is being processed. ``Alignment tabs'' are the
+\texttt{\&} signs that separate the columns of a \environment{tabular}
+(or \environment{array} or matrix) environment; so the error message
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+! Extra alignment tab has been
+ changed to \cr
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+! Extra alignment tab has been changed to \cr
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+could arise from a simple typo, such as:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{ll}
+ hello & there & jim \\
+ goodbye & now
+\end{tabular}
+\end{verbatim}
+\end{quote}
+where the second \texttt{\&} in the first line of the table is more than the
+two-column \texttt{ll} column specification can cope with. In this
+case, an extra ``\texttt{l}'' in that solves the problem. (If you
+continue from the error in this case, ``\texttt{jim}'' will be moved
+to a row of his own.) Another simple typo that can provoke the error
+is:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{ll}
+ hello & there
+ goodbye & now
+\end{tabular}
+\end{verbatim}
+\end{quote}
+where the `\texttt{\bsbs }' has been missed from the first line of the table.
+In this case, if you continue from the error, you will find that
+\LaTeX{} has made a table equivalent to:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{ll}
+ hello & there goodbye\\
+ now
+\end{tabular}
+\end{verbatim}
+\end{quote}
+(with the second line of the table having only one cell).
+
+Rather more difficult to spot is the occurrence of the error when
+you're using alignment instructions in a ``\texttt{p}'' column:
+\begin{quote}
+\begin{verbatim}
+\usepackage{array}
+...
+\begin{tabular}{l>{\raggedright}p{2in}}
+here & we are again \\
+happy & as can be
+\end{tabular}
+\end{verbatim}
+\end{quote}
+the problem here (as explained in % ! line break
+\Qref[question]{tabular cell alignment}{Q-tabcellalign}) is that the
+\csx{raggedright} command in the column specification has overwritten
+\environment{tabular}'s definition of \texttt{\bsbs }, so that
+``\texttt{happy}'' appears in a new line of the second column, and the
+following \texttt{\&} appears to \LaTeX{} just like the second
+\texttt{\&} in the first example above.
+
+Get rid of the error in the way described in % ! linebreak
+\Qref[question]{tabular cell alignment}{Q-tabcellalign}~--- either use
+\csx{tabularnewline} explicitly, or use the \csx{RBS} trick described
+there.
+
+The \Package{amsmath} package adds a further twist; when typesetting
+a matrix (the package provides many matrix environments), it has a
+fixed maximum number of columns in a matrix~--- exceed that maximum,
+and the error will appear. By default, the maximum is set to 10, but
+the value is stored in counter \texttt{MaxMatrixCols} and may be
+changed (in the same way as any counter):
+\begin{quote}
+\begin{verbatim}
+\setcounter{MaxMatrixCols}{20}
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\end{ctanrefs}
+\LastEdit{2011-07-06}
+
+\Question[Q-divzero]{Graphics division by zero}
+
+While the error
+\begin{quote}
+\begin{verbatim}
+! Package graphics Error: Division by 0.
+\end{verbatim}
+\end{quote}
+can actually be caused by offering the package a figure which claims
+to have a zero dimension, it's more commonly caused by rotation.
+
+Objects in \TeX{} may have both height (the height above the baseline)
+and depth (the distance the object goes below the baseline). If you
+rotate an object by 180\,degrees, you convert its height into depth,
+and vice versa; if the object started with zero depth, you've
+converted it to a zero-height object.
+
+Suppose you're including your graphic with a command like:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\includegraphics[angle=180,height=5cm]{myfig.eps}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\includegraphics[angle=180,%
+ height=5cm]{myfig.eps}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+In the case that \File{myfig.eps} has no depth to start with, the
+scaling calculations will produce the division-by-zero error.
+
+Fortunately, the \Package{graphicx} package has a keyword
+\pkgoption{totalheight}, which allows you to specify the size of the
+image relative to the sum of the object's \pkgoption{height} and
+\pkgoption{depth}, so
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\includegraphics[angle=180,totalheight=5cm]{myfig.eps}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\includegraphics[angle=180,%
+ totalheight=5cm]{myfig.eps}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+will resolve the error, and will behave as you might hope.
+
+If you're using the simpler \Package{graphics} package, use the
+\texttt{*} form of the \csx{resizebox} command to specify the use of
+\pkgoption{totalheight}:
+\begin{quote}
+\begin{verbatim}
+\resizebox*{!}{5cm}{%
+ \rotatebox{180}{%
+ \includegraphics{myfig.eps}%
+ }%
+}
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[graphics.sty,graphicx.sty]Both parts of the \CTANref{graphics} bundle
+\end{ctanrefs}
+
+\Question[Q-missbegdoc]{Missing \csx{begin}\marg{document}}
+
+The \emph{preamble} of your document is the stuff before
+\cmdinvoke{begin}{document}; you put \csx{usepackage} commands and
+your own macro definitions in there. \latex{} doesn't like
+\emph{typesetting} anything in the preamble, so if you have:
+\begin{itemize}
+\item typed the odd grumble,
+\item created a box with \csx{newsavebox} and put something in it
+ using \csx{sbox} (or the like),
+\item forgotten to put \cmdinvoke{begin}{document} into the document,
+ at all, or even
+\item gave it the wrong file
+\end{itemize}
+the error is inevitable and the solution is simple~--- judicious use
+of comment markers (`\texttt{\textpercent{}}') at the beginning of a
+line, moving things around, providing something that was
+missing~\dots{} or switching to the correct file.
+
+The error may also occur while reading the \extension{aux} file from an
+earlier processing run on the document; if so, delete the
+\extension{aux} file and start again from scratch. If the error
+recurs, it could well be due to a buggy class or package.
+
+However, it may be that none of the above solves the problem.
+
+If so, remember that things that appear before \csx{documentclass} are
+also problematical: they are inevitably before
+\cmdinvoke{begin}{document}!
+
+Unfortunately, modern editors are capable of putting things there, and
+preventing you from seeing them. This can happen when your document
+is being `written' in \Qref*{Unicode}{Q-unicode}. The Unicode
+standard defines ``Byte Order Marks'' (\acro{BOM}), that reassure a
+program (that reads the document) of the way the Unicode codes are
+laid out. Sadly ordinary \latex{} or \pdflatex{} choke on
+\acro{BOM}s, and consider them typesetting requests. The error
+message you see will look like:
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Missing \begin{document}.
+...
+l.1 <?>
+ <?><?>\documentclass{article}
+\end{verbatim}
+\end{quote}
+(Those \texttt{<?>}s are your operating system's representation of an
+unknown character; on the author's system it's a reverse video
+`\texttt{?}' sign.)
+
+You can spot the \acro{BOM} by examining the bytes; for example, the
+Unix \ProgName{hexdump} application can help:
+\begin{quote}
+\begin{verbatim}
+$ hexdump -C <file>
+00000000 ef bb bf 5c 64 6f 63 75 ...
+\end{verbatim}
+\end{quote}
+The \texttt{5c 64 6f 63 75} are the ``\csx{docu}'' at the start of
+(the `real' part of) your document; the three bytes before it form the
+\acro{BOM}.
+
+How to stop your editor from doing this to you depends, of course, on
+the editor you use; if you are using \acro{GNU E}macs, you have to
+change the encoding from \texttt{utf-8-with-signature} to `plain'
+\texttt{utf-8}; instructions for that are found on
+% ! line break
+\href{http://stackoverflow.com/questions/3859274/}{the ``stack overflow'' site}
+
+(So far, all instances of this problem that the author has seen have
+afflicted \acro{GNU E}macs users.)
+
+Fortunately \xetex{} and \luatex{} know about \acro{BOM}s and what to
+do with them, so \latex{} using them is ``safe''.
+
+\Question[Q-normalszmiss]{\csx{normalsize} not defined}
+
+The \LaTeX{} error:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+The font size command \normalsize is not
+ defined: there is probably something
+ wrong with the class file.
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+The font size command \normalsize is not defined:
+there is probably something wrong with the class file.
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+reports something pretty fundamental (document base font size has not
+been set, something the document class does for you). It \emph{can},
+in principle, be a problem with the document class, but is more often
+caused by the user forgetting to start their document with a
+\csx{documentclass} command.
+\LastEdit{2013-11-20}
+
+\Question[Q-manymathalph]{Too many math alphabets}
+
+\TeX{} mathematics is one of its most impressive features, yet the
+internal structure of the mechanism that produces it is painfully
+complicated and (in some senses) pathetically limited. One area of
+limitation is that one is only allowed 16~''maths alphabets''
+
+\LaTeX{} offers the user quite a lot of flexibility with allocating
+maths alphabets, but few people use the flexibility directly.
+Nevertheless, there are many packages that provide symbols, or that
+manipulate them, which allocate themselves one or more maths alphabet.
+
+If you can't afford to drop any of these packages, you might be able
+to consider switching to use of \Qref*{\xetex{}}{Q-xetex} or
+\Qref{\luatex{}}{Q-luatex}, which both have 65536 alphabet slots
+available. (Such a change is best not done when under pressure to
+complete a document; other issues, such as font availability) could
+make a change impractical.)
+
+Even if switching is not possible, there's still hope if you're using
+the \Package{bm} package to support \Qref*{bold maths}{Q-boldgreek}:
+\Package{bm} is capable of gobbling alphabets as if there is no
+tomorrow. The package defines two limiter commands: \csx{bmmax} (for
+\emph{bold} symbols; default~4) and \csx{hmmax} (for \emph{heavy}
+symbols, if you have them; default~3), which control the number of
+alphabets to be used.
+
+Any reduction of the \csx{\emph{xx}max} variables will slow
+\Package{bm} down~--- but that's surely better than the document not
+running at all. So unless you're using maths fonts (such as
+\FontName{Mathtime Plus}) that feature a heavy symbol weight, suppress all
+use of heavy families by
+\begin{quote}
+\begin{verbatim}
+ \newcommand{\hmmax}{0}
+\end{verbatim}
+\end{quote}
+(before loading \Package{bm}), and then steadily reduce the bold
+families, starting with
+\begin{quote}
+\begin{verbatim}
+ \newcommand{\bmmax}{3}
+\end{verbatim}
+\end{quote}
+(again before loading \Package{bm}), until (with a bit of luck) the
+error goes away.
+\begin{ctanrefs}
+\item[bm.sty]Distributed as part of \CTANref{2etools}[bm]
+\end{ctanrefs}
+
+\Question[Q-ouparmd]{Not in outer par mode}
+
+The error:
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Not in outer par mode.
+\end{verbatim}
+\end{quote}
+comes when some ``main'' document feature is shut up somewhere it
+doesn't like.
+
+The commonest occurrence is when the user wants a figure somewhere
+inside a table:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|l|}
+ \hline
+ \begin{figure}
+ \includegraphics{foo}
+ \end{figure}
+ \hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+a construction that was supposed to put a frame around the diagram,
+but doesn't work, any more than:
+\begin{quote}
+\begin{verbatim}
+\framebox{\begin{figure}
+ \includegraphics{foo}
+ \end{figure}%
+}
+\end{verbatim}
+\end{quote}
+The problem is, that the \environment{tabular} environment, and the
+\csx{framebox} command restrain the \environment{figure} environment
+from its natural m\'etier, which is to float around the document.
+
+The solution is simply not to use the \environment{figure} environment
+here:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{|l|}
+ \hline
+ \includegraphics{foo}
+ \hline
+\end{tabular}
+\end{verbatim}
+\end{quote}
+What was the float for?~--- as written in the first two examples, it
+serves no useful purpose; but perhaps you actually wanted a diagram
+and its caption framed, in a float.
+
+It's simple to achieve this~--- just reverse the order of the
+environments (or of the \environment{figure} environment and the
+command):
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ \begin{tabular}{|l|}
+ \hline
+ \includegraphics{foo}
+ \caption{A foo}
+ \hline
+ \end{tabular}
+\end{figure}
+\end{verbatim}
+\end{quote}
+The same goes for \environment{table} environments (or any other sort
+of float you've defined for yourself) inside tabulars or box commands;
+you \emph{must} get the float environment out from inside, one way or
+another.
+
+\Question[Q-errmissitem]{Perhaps a missing \csx{item}?}
+
+Sometimes, the error
+\begin{quote}
+\begin{verbatim}
+Something's wrong--perhaps a missing \item
+\end{verbatim}
+\end{quote}
+actually means what it says:
+\begin{quote}
+\begin{verbatim}
+\begin{itemize}
+ boo!
+\end{itemize}
+\end{verbatim}
+\end{quote}
+produces the error, and is plainly in need of an \csx{item} command.
+
+You can also have the error appear when at first sight things are
+correct:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{l}
+ \begin{enumerate}
+ \item foo\\
+ \item bar
+ \end{enumerate}
+\end{tabular}
+\end{verbatim}
+\end{quote}
+produces the error at the \texttt{\bsbs }. This usage is just wrong; if you
+want to number the cells in a table, you have to do it ``by hand'':
+\begin{quote}
+\begin{verbatim}
+\newcounter{tablecell}
+...
+\begin{tabular}{l}
+ \stepcounter{tablecell}
+ \thetablecell. foo\\
+ \stepcounter{tablecell}
+ \thetablecell. bar
+\end{tabular}
+\end{verbatim}
+\end{quote}
+This is obviously untidy; a command \csx{numbercell} defined as:
+\begin{quote}
+\begin{verbatim}
+\newcounter{tablecell}
+...
+\newcommand*{\numbercell}{%
+ \stepcounter{tablecell}%
+ \thetablecell. % **
+}
+\end{verbatim}
+\end{quote}
+could make life easier:
+\begin{quote}
+\begin{verbatim}
+\begin{tabular}{l}
+ \numbercell foo\\
+ \numbercell bar
+\end{tabular}
+\end{verbatim}
+\end{quote}
+Note the deliberate introduction of a space as part of the command,
+marked with asterisks. Omitted above, the code needs to set the
+counter \ltxcounter{tablecell} to zero
+(\cmdinvoke{setcounter}{tablecell}{0}) before each tabular that uses it.
+
+The error also regularly appears when you would never have thought
+that a \csx{item} command might be appropriate. For example, the
+seemingly innocent:
+\begin{quote}
+\begin{verbatim}
+\fbox{%
+ \begin{alltt}
+ boo!
+ \end{alltt}%
+}
+\end{verbatim}
+\end{quote}
+produces the error (the same happens with \csx{mbox} in place of
+\csx{fbox}, or with either of their ``big brothers'', \csx{framebox} and
+\csx{makebox}). This is because the \environment{alltt} environment
+uses a ``trivial'' list, hidden inside its definition. (The
+\environment{itemize} environment also has this construct inside
+itself, in fact, so \cmdinvoke{begin}{itemize} won't work inside an
+\csx{fbox}, either.) The list construct wants to happen between
+paragraphs, so it makes a new paragraph of its own. Inside the
+\csx{fbox} command, that doesn't work, and subsequent macros convince
+themselves that there's a missing \csx{item} command.
+
+To solve this rather cryptic error, one must put the
+\environment{alltt} inside a paragraph-style box. The following
+modification of the above \emph{does} work:
+\begin{quote}
+\begin{verbatim}
+\fbox{%
+ \begin{minipage}{0.75\textwidth}
+ \begin{alltt}
+ hi, there!
+ \end{alltt}
+ \end{minipage}
+}
+\end{verbatim}
+\end{quote}
+The code above produces a box that's far too wide for the text. One
+may want to use something that allows % ! line break
+\Qref*{variable size boxes}{Q-varwidth} in place of the
+\environment{minipage} environment.
+
+Oddly, although the \environment{verbatim} environment wouldn't work
+inside a \csx{fbox} command argument (see % ! line break
+\Qref[question]{verbatim in command arguments}{Q-verbwithin}), you
+get an error that complains about \csx{item}: the environment's
+internal list bites you before \environment{verbatim} has even had a
+chance to create its own sort of chaos.
+
+Another (seemingly) obvious use of \csx{fbox} also falls foul of this
+error:
+\begin{quote}
+\begin{verbatim}
+\fbox{\section{Boxy section}}
+\end{verbatim}
+\end{quote}
+This is a case where you've simply got to be more subtle; you should
+either write your own macros to replace the insides of \LaTeX{}'s
+sectioning macros, or look for some alternative in the packages
+discussed in % ! line break
+``\Qref*[question]{The style of section headings}{Q-secthead}''.
+
+\Question[Q-errparnum]{Illegal parameter number in definition}
+
+The error message means what it says. In the simple case, you've
+attempted a definition like:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\abc}{joy, oh #1!}
+\end{verbatim}
+\end{quote}
+or (using \TeX{} primitive definitions):
+\begin{quote}
+\begin{verbatim}
+\def\abc{joy, oh #1!}
+\end{verbatim}
+\end{quote}
+In either of the above, the definition uses an argument, but the
+programmer did not tell \AllTeX{}, in advance, that she was going to.
+The fix is simple~--- \cmdinvoke{newcommand}{\csx{abc}}[1], in the
+\LaTeX{} case, |\def\abc#1| in the basic \TeX{} case.
+
+The more complicated case is exemplified by the attempted definition:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\abc}{joy, oh joy!%
+ \newcommand{\ghi}[1]{gloom, oh #1!}%
+}
+\end{verbatim}
+\end{quote}
+will also produce this error, as will its \TeX{} primitive equivalent:
+\begin{quote}
+\begin{verbatim}
+\def\abc{joy, oh joy!%
+ \def\ghi#1{gloom, oh #1!}%
+}
+\end{verbatim}
+\end{quote}
+This is because special care is needed when defining one macro within
+the code of another macro. This is explained elsewhere, separately
+for \Qref*[question]{\LaTeX{} definitions}{Q-ltxhash} and for
+\Qref*[question]{\TeX{} primitive definitions}{Q-hash}
+
+\Question[Q-fllost]{Float(s) lost}
+
+The error
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Float(s) lost.
+\end{verbatim}
+\end{quote}
+seldom occurs, but always seems deeply cryptic when it \emph{does}
+appear.
+
+The message means what it says: one or more figures, tables, etc., or
+marginpars has not been typeset. (Marginpars are treated internally
+as floats, which is how they come to be lumped into this error
+message.)
+
+The most likely reason is that you placed a float or a \csx{marginpar}
+command inside another float or marginpar, or inside a
+\environment{minipage} environment, a \csx{parbox} or \csx{footnote}.
+Note that the error may be detected a long way from the problematic
+command(s), so the techniques of % ! line break
+\Qref*{tracking down elusive errors}{Q-erroradvice} all need to be
+called into play.
+
+This author has also encountered the error when developing macros that
+used the \LaTeX{} internal float mechanisms. Most people doing that
+sort of thing are expected to be able to work out their own problems\dots{}
+
+\Question[Q-parmoderr]{Not in outer par mode}
+
+For example:
+\begin{quote}
+\begin{verbatim}
+*\mbox{\marginpar{foo}}
+
+! LaTeX Error: Not in outer par mode.
+\end{verbatim}
+\end{quote}
+The error comes when you try to build something movable inside a box.
+Movable things, in this context, are floating environments
+(\environment{figure} and \environment{table}, for example), and
+\csx{marginpar}s. \latex{} simply doesn't have the mechanisms for
+floating out of boxes. In fact, floats and \csx{marginpar}s
+themselves are built out of boxes, so that they can't be nested.
+
+If your error arises from \csx{marginpar}, you simply have to think of
+an alternative way of placing the command; there is no slick solution.
+
+If a floating environment is the culprit, it may be possible to use
+the ``\texttt{H}'' placement option, provided (for example) by the
+\Package{float} package:
+\begin{quote}
+\begin{verbatim}
+\parbox{25cm}{%
+ \begin{figure}[H]
+ ...
+ \caption{Apparently floating...}
+ \end{figure}%
+}
+\end{verbatim}
+\end{quote}
+This example makes little sense as it stands; however, it is
+conceivable that sane uses could be found (for example, using a
+package such as \Package{algorithm2e} to place two algorithms
+side-by-side).
+\begin{ctanrefs}
+\item[algorithm2e.sty]\CTANref{algorithm2e}
+\item[float.sty]\CTANref{float}
+\end{ctanrefs}
+\LastEdit{2013-09-09}
+
+\Question[Q-texorpdf]{Token not allowed in PDFDocEncoded string}
+
+The package \Package{hyperref} produces this error when it doesn't
+know how to make something into a ``character'' that will go into one
+of its \acro{PDF} entries. For example, the (unlikely) sequence
+\begin{quote}
+\begin{verbatim}
+\newcommand{\filled}[2]{%
+ #1%
+ \hfil
+ #2%
+}
+\section{\filled{foo}{bar}}
+\end{verbatim}
+\end{quote}
+provokes the error. \Package{Hyperref} goes on to tell you:
+\begin{quote}
+\begin{verbatim}
+removing `\hfil' on input line ...
+\end{verbatim}
+\end{quote}
+It's not surprising: how would \emph{you} put the
+typesetting instruction \csx{hfil} into a \acro{PDF} bookmark?
+
+\Package{Hyperref} allows you to define an alternative for such
+things: the command \csx{texorpdfstring}, which takes two
+arguments~--- the first is what is typeset, the second is what is put
+into the bookmark. For example, what you would probably like in this
+case is just a single space in the bookmark; if so, the erroneous
+example above would become:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\filled}[2]{%
+ #1%
+ \texorpdfstring{\hfil}{\space}%
+ #2%
+}
+\section{\filled{foo}{bar}}
+\end{verbatim}
+\end{quote}
+and with that definition, the example will compile succesfully
+(\Package{hyperref} knows about the macro \csx{space}).
+\LastEdit*{2009-05-29}
+
+\Question[Q-checksum]{Checksum mismatch in font}
+
+When \MF{} generates a font it includes a checksum in the font bitmap
+file, and in the font metrics file (\acro{TFM}). \AllTeX{} includes
+the checksum from the \acro{TFM} file in the \acro{DVI} file.
+
+When \ProgName{dvips} (or other \acro{DVI} drivers) process a
+\acro{DVI} file, they compare checksums in the \acro{DVI} file to
+those in the bitmap fonts being used for character images. If the
+checksums don't match, it means the font metric file used by \AllTeX{}
+was not generated from the same \MF{} program that generated the
+font.
+
+This commonly occurs when you're processing someone else's \acro{DVI}
+file.
+
+The fonts on your system may also be at fault: possibilities are that
+the new \acro{TFM} was not installed, or installed in a path after an
+old \acro{TFM} file, or that you have a personal cache of bitmaps from
+an old version of the font.
+
+In any case, look at the output -- the chances are that it's perfectly
+\acro{OK}, since metrics tend not to change, even when the bitmaps are
+improved. (Indeed, many font designers~--- Knuth included~---
+maintain the metrics come what may.)
+
+If the output \emph{does} look bad, your only chance is to regenerate
+things from scratch. Options include: flushing your bitmap cache,
+rebuild the \acro{TFM} file locally, and so on.
+
+\Question[Q-entercompmode]{Entering compatibility mode}
+
+You run your \LaTeX{} job, and it starts by saying
+\begin{quote}
+\begin{verbatim}
+Entering LaTeX 2.09 COMPATIBILITY MODE
+\end{verbatim}
+\end{quote}
+followed by lines of asterisks and \texttt{!!WARNING!!}.
+
+This means that the document is not written in ``current'' \LaTeX{}
+syntax, and that there is no guarantee that all parts of the document
+will be formatted correctly.
+
+If the document is someone else's, and you want no more than a copy to
+read, ignore the error. The document may fail elsewhere, but as often
+as not it will provide a \extension{dvi} or \extension{pdf} that's
+adequate for most purposes.
+
+If it's a new document you have just started working on, you have been
+misled by someone. You have written something like:
+\begin{quote}
+ \cmdinvoke{documentstyle}{article}
+\end{quote}
+or, more generally:
+\begin{quote}
+ \cmdinvoke*{documentstyle}[options]{class}
+\end{quote}
+These forms are (as the warning says) \LaTeXo{} syntax, and to get rid
+of the warning, you must change the command.
+
+The simple form is easy to deal with:
+\begin{quote}
+ \cmdinvoke{documentstyle}{article}
+\end{quote}
+should become:
+\begin{quote}
+ \cmdinvoke{documentclass}{article}
+\end{quote}
+The complex form is more difficult, since \LaTeXo{} ``options''
+conflate two sorts of things~--- options for the class (such as
+\pkgoption{11pt}, \pkgoption{fleqn}), and packages to be loaded.
+So:
+\begin{quote}
+ \cmdinvoke{documentstyle}[11pt,verbatim]{article}
+\end{quote}
+should become:
+\begin{quote}
+ \cmdinvoke{documentclass}[11pt]{article}\\
+ \cmdinvoke{usepackage}{verbatim}
+\end{quote}
+because \pkgoption{11pt} happens to be a class option, while
+\Package{verbatim} is a package.
+
+There's no simple way to work out what are class options under
+\LaTeXo{}; for \Class{article}, the list includes \pkgoption{10pt},
+\pkgoption{11pt}, \pkgoption{12pt}, \pkgoption{draft},
+\pkgoption{fleqn}, \pkgoption{leqno}, \pkgoption{twocolumn} and
+\pkgoption{twoside}~--- anything else must be a package.
+
+Your document may well ``just work'' after changes like those above;
+if not, you should think through what you're trying to do, and consult
+documentation on how to do it~--- there are lots of % ! line break
+\Qref*{free tutorials}{Q-tutorials*} to help you on your way, if you
+don't have access to a \LaTeX{} manual of any sort.
+
+\Question[Q-includeother]{\latex{} won't include from other directories}
+
+You wanted to \cmdinvoke{include}{../bar/xyz.tex}, but \latex{} says:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+latex: Not writing to ../bar/xyz.aux (openout_any = p).
+! I can't write on file `../bar/xyz.aux'.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+LaTeX: Not writing to ../bar/xyz.aux
+ (openout_any = p).
+! I can't write on file `../bar/xyz.aux'.
+\end{verbatim}
+(The first line of that message is wrapped, here.)
+\end{narrowversion}
+\end{quote}
+The error comes from \tex{}'s protection against writing to
+directories that aren't descendents of the one where your document
+resides. (The restriction protects against problems arising from
+\latex{}ing someone else's malicious, or merely broken, document. If
+such a document overwrites something you wanted kept, there is obvious
+potential for havoc.)
+
+Document directory structures that can lead to this problem will look
+like the fictional \File{mybook}:
+\begin{quote}
+\begin{verbatim}
+./base/mybook.tex
+./preface/Preface.tex
+./preface/***
+./chapter1/Intro.tex
+...
+\end{verbatim}
+\end{quote}
+With such a structure, any document directory (other than the one
+where \File{mybook.tex} lives), seems ``up'' the tree from the
+base directory. (References to such files will look like
+\cmdinvoke{include}{../preface/Preface}: the ``\texttt{..}'' is the
+hint.)
+
+But why did it want to write at all?~--- % ! line break
+``\Qref*{what's going in in my \csx{include}}{Q-include}'' explains
+how \csx{include} works, among other things by writing an
+\extension{aux} file for every \csx{includ}ed file.
+
+Solutions to the problem tend to be drastic:
+\begin{enumerate}
+\item Restructure the directories that hold your document so that the
+ master file is at the root of the tree:
+ \begin{quote}
+\begin{verbatim}
+./mybook.tex
+./mybook/preface/Preface.tex
+./mybook/preface/***
+./mybook/chapter1/Intro.tex
+...
+\end{verbatim}
+ \end{quote}
+ and so on.
+\item Did you actually \emph{need} \csx{include}?~--- if not, you can
+ replace \csx{include} by \csx{input} throughout. (This only works
+ if you don't need \csx{includeonly}.)
+\item You \emph{could} patch your system's \File{texmf.cnf}~--- if you
+ know what you're doing, the error message should be enough of a
+ hint; this action is definitely not recommended, and is left to
+ those who can ``help themselves'' in this respect.
+\end{enumerate}
+\LastEdit*{2012-02-13}
+
+\Question[Q-expl3-old]{Support package \Package{expl3} too old}
+
+Some (rather modern) packages are written using the % ! line break
+\Qref*{\latex{}3 programming environment}{Q-LaTeX3}. Since \latex{}3
+is still under development, the author cannot reliably guess what
+version of \latex{}3 the user has installed, and whether that version
+is adequate for the current package. Thus the package's code often
+checks the user's installation, and complains if it's older than the
+author's installation at time of testing. The error message is:
+\begin{quote}
+\begin{verbatim}
+! Support package expl3 too old.
+\end{verbatim}
+\end{quote}
+The ``additional help'' tells you the solution: update your \latex{}3
+installation. The relevant things are \Package{l3kernel} (the
+programming environment, which contains the \Package{expl3} mentioned
+in the error message) and \Package{l3packages} (\latex{}3 constructs
+such as command definitions).
+
+While this sounds a drastic remedy, it is no longer the major
+undertaking it once was~--- if you are using a modern \tex{}
+distribution that you installed yourself, ask it to update over the
+internet; if that choice is not available, install from the
+\extension{tds.zip} files available for both packages on \ctan{}.
+\begin{ctanrefs}
+\item[l3kernel \nothtml{\rmfamily}bundle]\CTANref{l3kernel}
+\item[l3packages \nothtml{\rmfamily}bundle]\CTANref{l3packages}
+\end{ctanrefs}
+\LastEdit*{2013-02-20}
diff --git a/help/uk-tex-faq/faq-lab-ref.tex b/help/uk-tex-faq/faq-lab-ref.tex
new file mode 100644
index 0000000000..d1629fd7b7
--- /dev/null
+++ b/help/uk-tex-faq/faq-lab-ref.tex
@@ -0,0 +1,182 @@
+% $Id: faq-lab-ref.tex,v 1.4 2011/05/08 10:16:43 rf10 Exp $
+
+\subsection{Labels and references}
+
+\Question[Q-nameref]{Referring to things by their name}
+
+\LaTeX{}'s labelling mechanism is designed for the impersonal world of
+the academic publication, in which everything has a number: an
+extension is necessary if we are to record the \emph{name} of things
+we've labelled. The two packages available extend the \LaTeX{}
+sectioning commands to provide reference by the name of the section.
+
+The \Package{titleref} package is a simple extension which provides
+the command \csx{titleref}; it is a stand-alone package~--- don't use it
+in a document in which you also need to use \Package{hyperref}.
+
+The \Package{byname} package is part of the \Package{smartref} bundle
+and works well with \Package{smartref}, and works (to an extent) with
+\Package{hyperref}, but the links it defines are not hyperlinks.
+
+The \Class{memoir} class incorporates the functionality of
+\Package{titleref}, but doesn't work with \Package{byname} (though a
+search of \Newsgroup{comp.text.tex} on \URL{groups.google.com} will
+find a patch to \Package{byname} to remedy the problem).
+
+The \Package{hyperref} bundle includes a package \Package{nameref},
+which will work standing alone (i.e., without \Package{hyperref}: of
+course, in this mode its references are not hyperlinked). If you load
+\Package{hyperref} itself, \Package{nameref} is automatically loaded.
+\Class{Memoir} requires the \Package{memhfixc} when running with
+\Package{hyperref}; following the sequence:
+\begin{quote}
+\begin{verbatim}
+\documentclass[...]{memoir}
+...
+\usepackage[...]{hyperref}
+\usepackage{memhfixc}
+\end{verbatim}
+\end{quote}
+\Package{nameref} commands may be used in a \Class{memoir} document.
+
+\Package{Zref} defines a proposed replacement for all of the \LaTeX{}
+reference mechanisms, and among other things provides
+name-referencing mechanisms:
+\begin{quote}
+\begin{verbatim}
+\usepackage[user,titleref]{zref}
+...
+\section{hello}\zlabel{sec:one}
+The section name is: \ztitleref{sec:one}.
+\end{verbatim}
+\end{quote}
+(One might hope that something of this sort would be the ``way of the
+future'', but things move slowly in the \LaTeX{} world: don't hold
+your breath.)
+
+Each of \Package{titleref}, \Package{byname} and \Package{nameref}
+defines a reference command with the same name as the package:
+\csx{titleref}, \csx{byname} and \csx{nameref}. The \Package{nameref}
+package also defines a command \csx{byshortnameref}, which uses the
+optional `short' title argument to the chapter and section commands.
+(Although it comes from the same author, \Package{zref} \emph{doesn't}
+define a short-name variant.)
+\begin{ctanrefs}
+\item[byname.sty]Distributed with \CTANref{smartref}
+\item[hyperref.sty]\CTANref{hyperref}
+\item[memoir.cls]\CTANref{memoir}
+\item[nameref.sty]Distributed with \CTANref{hyperref}
+\item[smartref.sty]\CTANref{smartref}
+\item[titleref.sty]\CTANref{titleref}
+\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref]
+\end{ctanrefs}
+
+\Question[Q-extref]{Referring to labels in other documents}
+
+When producing a set of inter-related documents, you'll often want to
+refer to labels in another document of the set; but \LaTeX{}, of its
+own accord, doesn't permit this.
+
+So the package \Package{xr} was written: if you say
+\begin{quote}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument{volume1}
+\end{verbatim}
+\end{quote}
+will load all the references from \File{volume1} into your present
+document.
+
+But what if the documents both have a section labelled
+``\environment{introduction}'' (likely enough, after all)? The
+package provides a means to transform all the imported labels, so you
+don't have to change label names in either document. For example:
+\begin{quote}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+\end{verbatim}
+\end{quote}
+loads the references from \File{volume1}, but prefixes every one with
+the string \texttt{V1-}. So you would refer to the introduction to volume~1
+as:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+...
+... the introduction to volume1
+ (\ref{V1-introduction})...
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+...
+... the introduction to volume1 (\ref{V1-introduction})...
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+To have the facilities of \Package{xr} working with
+\Package{hyperref}, you need \Package{xr-hyper}. For simple
+hyper-cross-referencing (i.e., to a local \acro{PDF} file you've just
+compiled), write:
+\begin{quote}
+\begin{verbatim}
+\usepackage{xr-hyper}
+\usepackage{hyperref}
+\externaldocument[V1-]{volume1}
+...
+... the \nameref{V1-introduction})...
+\end{verbatim}
+\end{quote}
+and the name reference will appear as an active link to the
+``introduction'' chapter of \File{volume1.pdf}.
+
+To link to a \acro{PDF} document on the Web, for which you happen to
+have the .aux file, write:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\usepackage{xr-hyper}
+\usepackage{hyperref}
+\externaldocument[V1-]{volume1}[http://mybook.com/volume1.pdf]
+...
+... the \nameref{V1-introduction})...
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\usepackage{xr-hyper}
+\usepackage{hyperref}
+\externaldocument[V1-]{volume1}%
+ [http://mybook.com/volume1.pdf]
+...
+... the \nameref{V1-introduction})...
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+Heiko Oberdiek's experimental \Package{zref} bundle includes a
+hyper-crossreferencing mechanism using its \Package{zref-xr} module.
+Usage is closely modelled on \Package{xr} and \Package{xr-hyper}; a
+trivial example (from a \Newsgroup{comp.text.tex} posting) is
+\begin{quote}
+\begin{verbatim}
+\usepackage{zref-xr,zref-user}
+\zexternaldocument*{xr02}
+...
+\zref{foo}
+\end{verbatim}
+\end{quote}
+The module provides all the facilities of the older packages, and can
+deal both with ``traditional'' \LaTeX{} labels and with
+\Package{zref}'s style of labels.
+\begin{ctanrefs}
+\item[xr.sty]Distributed as part of \CTANref{2etools}[xr]
+\item[xr-hyper.sty]Distributed with \CTANref{hyperref}[xr-hyper]
+\item[zref \nothtml{\rmfamily\itshape}bundle]Distributed as part of
+ \CTANref{oberdiek}[zref]
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-litprog.tex b/help/uk-tex-faq/faq-litprog.tex
new file mode 100644
index 0000000000..e5ba9eb671
--- /dev/null
+++ b/help/uk-tex-faq/faq-litprog.tex
@@ -0,0 +1,81 @@
+% $Id: faq-litprog.tex,v 1.3 2012/11/24 10:56:03 rf10 Exp $
+
+\section{Literate programming}
+
+\Question[Q-lit]{What is Literate Programming?}
+
+Literate programming is the combination of documentation and source
+together in a fashion suited for reading by human beings.
+In general, literate programs combine source
+and documentation in a single file. Literate programming tools then
+parse the file to produce either readable documentation or compilable
+source. The \acro{WEB} style of literate programming was created by
+D.~E.~Knuth during the development of \TeX{}.
+
+\htmlignore
+The ``\Qref*{documented \LaTeX{}}{Q-dtx}'' style of programming
+\endhtmlignore
+\begin{htmlversion}
+ The ``\Qref{documented \LaTeX{}}{Q-dtx}'' style of programming
+\end{htmlversion}
+is regarded by some as a form of literate programming, though it only
+contains a subset of the constructs Knuth used.
+
+Discussion of literate programming is conducted in the newsgroup
+\Newsgroup{comp.programming.literate}, whose \acro{FAQ} is stored on
+\acro{CTAN}. Another good source of information is
+\URL{http://www.literateprogramming.com/}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Literate Programming \acro{FAQ}]%
+ \CTANref{LitProg-FAQ}
+\end{ctanrefs}
+\LastEdit{2012-11-16}
+
+\Question[Q-webpkgs]{\acro{WEB} systems for various languages}
+
+\TeX{} is written in the programming language \acro{WEB}; \acro{WEB}
+is a tool to implement the concept of ``literate programming''.
+Knuth's original implementation will be in any respectable
+distribution of \TeX{}, but the sources of the two tools
+(\ProgName{tangle} and \ProgName{weave}), together with a manual
+outlining the programming techniques, may be had from \acro{CTAN}.
+
+\acro{\ProgName{CWEB}}, by Silvio Levy, is a \acro{WEB} for \acro{C} programs.
+
+\acro{\ProgName{FWEB}}, by John Krommes, is a version for Fortran,
+Ratfor,\acro{C}, \acro{C}++, working with \latex{}; it was derived
+from \ProgName{CWEB}.
+
+Spidery \acro{WEB}, by Norman Ramsey, supports many
+languages including Ada, \texttt{awk}, and \acro{C}
+and, while not in the public domain, is usable without charge. It is
+now superseded by \ProgName{noweb} (also by Norman Ramsay) which
+incorporates the lessons learned in implementing spidery \acro{WEB},
+and which is a simpler, equally powerful, tool.
+
+\ProgName{Scheme}\acro{\ProgName{WEB}}, by John Ramsdell, is a Unix filter that
+translates Scheme\acro{WEB} into \LaTeX{} source or Scheme source.
+
+\acro{\ProgName{APLWEB}} is a version of \acro{WEB} for \acro{APL}.
+
+\ProgName{FunnelWeb} is a version of \acro{WEB} that is language independent.
+
+Other language independent versions of \acro{WEB} are \ProgName{nuweb} (which
+is written in \acro{ANSI} \acro{C}).
+
+\ProgName{Tweb} is a \acro{WEB} for \plaintex{} macro files, using
+\ProgName{noweb}.
+\begin{ctanrefs}
+\item[aplweb]\CTANref{aplweb}
+\item[cweb]\CTANref{cweb}
+\item[funnelweb]\CTANref{funnelweb}
+\item[fweb]\CTANref{fweb}
+\item[noweb]\CTANref{noweb}
+\item[nuweb]\CTANref{nuweb}
+\item[schemeweb]\CTANref{schemeweb}
+\item[spiderweb]\CTANref{spiderweb}
+\item[tangle]\CTANref{web}
+\item[tweb]\CTANref{tweb}
+\item[weave]\CTANref{web}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-mac-prog.tex b/help/uk-tex-faq/faq-mac-prog.tex
new file mode 100644
index 0000000000..e9a881ba2a
--- /dev/null
+++ b/help/uk-tex-faq/faq-mac-prog.tex
@@ -0,0 +1,3724 @@
+% $Id: faq-mac-prog.tex,v 1.35 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Macro programming}
+
+\subsection{``Generic'' macros and techniques}
+
+\Question[Q-linmacnames]{Non-letters in macro names}
+
+New \LaTeX{} users are often suprised that macro definitions
+containing non-letters, such as
+\begin{quote}
+\begin{verbatim}
+\newcommand{\cul8r}{Goodbye!}
+\end{verbatim}
+\end{quote}
+fail to compile. The reason is that the \TeX{} macro language, unlike
+most programming languages, allows % ! loin break (twatbili)
+\Qref*{nothing but letters in macro names}{Q-whatmacros}.
+
+There are a number of techniques for defining a macro with a name like
+\csx{cul8r}. Unfortunately, none of the techniques is particularly
+good:
+\begin{enumerate}
+\item Use \csx{csname}\dots\csx{endcsname} to define and invoke the
+ macro:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\expandafter\newcommand
+ \csname cul8r\endcsname{Goodbye!}
+I said, ``\csname cul8r\endcsname''.
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\expandafter\newcommand\csname cul8r\endcsname{Goodbye!}
+I said, ``\csname cul8r\endcsname''.
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+ \begin{description}
+ \item[Pro:] No unexpected side effects
+ \item[Con:] So verbose as to be unusable
+ \end{description}
+\item Define a ``special-command generator'', and use the resulting
+ commands:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\newcommand{\DefineRemark}[2]{%
+ \expandafter\newcommand
+ \csname rmk-#1\endcsname{#2}%
+}
+\newcommand{\Remark}[1]{%
+ \csname rmk-#1\endcsname%
+}
+...
+\DefineRemark{cul8r}{Goodbye!}
+...
+I said, ``\Remark{cul8r}''.
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand{\DefineRemark}[2]{%
+ \expandafter\newcommand\csname rmk-#1\endcsname{#2}%
+}
+\newcommand{\Remark}[1]{\csname rmk-#1\endcsname}
+...
+\DefineRemark{cul8r}{Goodbye!}
+...
+\Remark{cul8r}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+ \begin{description}
+ \item[Pro:] Straightforward to use, not too untidy
+ \item[Con:] It's hardly doing what we set out to do (experts will
+ see that you are defining a macro, but others likely won't)
+ \end{description}
+\item Convince \TeX{} that ``\texttt{8}'' is a letter:
+\begin{quote}
+\begin{verbatim}
+\catcode`8 = 11
+\newcommand{\cul8r}{Goodbye!}
+I said, ``\cul8r''.
+\end{verbatim}
+\end{quote}
+ \begin{description}
+ \item[Pro:] \csx{cul8r} can be used directly
+ \item[Con:] Likely to break other uses of ``\texttt{8}'' (such as
+ numbers or dimensions; so
+ \cmdinvoke{setlength}{\csx{paperwidth}}{8in} tells us:
+\begin{quote}
+\begin{verbatim}
+! Missing number, treated as zero.
+<to be read again>
+ 8
+\end{verbatim}
+\end{quote}
+ \end{description}
+ As a general rule, changing category codes is something to use
+ \emph{in extremis}, after detailed examination of options. It is
+ conceivable that such drastic action could be useful for you, but
+ most ordinary users are well advised not even to try such a
+ technique.
+\item Define a macro \csx{cul} which must always be followed by
+ ``\texttt{8r}'':
+\begin{quote}
+\begin{verbatim}
+\def\cul8r{Goodbye!}
+I said, ``\cul8r''.
+\end{verbatim}
+\end{quote}
+ \begin{description}
+ \item[Pro:] \csx{cul8r} can be used directly
+ \item[Con~\#1:] Breaks if \csx{cul} is followed by anything other
+ than ``\texttt{8r}'', with a confusing diagnostic~---
+ \csx{cul99} produces:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! Use of \cul doesn't match its definition.
+<*> \cul9
+ 9
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! Use of \cul doesn't match its
+ definition.
+<*> \cul9
+ 9
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+ (which would confuse someone who hadn't even realised there
+ \emph{was} a definition of \csx{cul} in the document).
+ \item[Con~\#2:] Silently redefines existing \csx{cul}, if any;
+ as a result, the technique cannot be used to define both a
+ \csx{cul8r} and, say, a \csx{cul123} macro in the same
+ document.
+ \end{description}
+\end{enumerate}
+Technique~3 is in fact commonly used~--- in a limited form~--- within
+most \LaTeX{} packages and within \LaTeX{} itself. The convention is to
+use ``\texttt{@}'' within the names of internal macros to hide them
+from the user and thereby prevent naming conflicts. To this end,
+\LaTeX{} automatically treats ``\texttt{@}'' as a letter while
+processing classes and packages and as a non-letter while processing
+the user's document. The key to this technique is the separation:
+internally a non-letter is used for macro names, and the user doesn't
+see anything of it, while the status remains ``frozen'' in all the
+definitions created within the class or package. See % ! line break
+\Qref[question]{\csx{@} and \texttt{@} in macro names}{Q-atsigns} for
+more information.
+
+Note that analogous use of technique~3 in this example would give us
+\begin{quote}
+\begin{verbatim}
+\begingroup
+ \catcode`8 = 11
+ \gdef\cul8r{Goodbye!}
+ \gdef\later{\cul8r}
+\endgroup
+I said, ``\later''.
+\end{verbatim}
+\end{quote}
+which works, but rather defeats the object of the exercise.
+(\csx{later} has the ``frozen'' catcode for `8', even though the value
+has reverted to normal by the time it's used; note, also, the use of
+the primitive command \csx{gdef}, since \csx{newcommand} can't make a
+macro that's available outside the group.)
+
+\emph{Recommendation}: Either choose another mechanism (such as
+\csx{DefineRemark} above), or choose another name for your macro, one
+that contains only ordinary letters. A common approach is to use
+roman numerals in place of arabic ones:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\culVIIIr}{Goodbye!}
+\end{verbatim}
+\end{quote}
+which rather spoils the intent of the joke implicit in the example
+\csx{cul8r}!
+\LastEdit*{2009-06-03}
+
+\Question[Q-repeat-num]{Repeating a command \emph{n} times}
+
+\tex{} was \emph{not} designed as a programming language, but there
+are occasions when you want to repeat some part of your document, just
+as parts of programs need to run several times. An obvious
+example is \tex{}-based drawing: \latex{}'s \environment{picture}
+environment and \Package{pgf} (at least) provide repeat facilities~---
+they are useful for drawing repeating patterns. As a result,
+``common'' programming techniques often have to be emulated using
+obscure macro \tex{}niques.
+
+This answer deals with repeating an operation a given number of times;
+repeating operations once for each of a set of objects is dealt with
+in the answer \Qref*{repeating ``over a set''}{Q-repeat-set}.
+
+Plain \tex{} itself provides a \csx{loop} \dots{} \csx{repeat}
+contruct, which enables you to repeat a command (or set of commands).
+The syntax is simple enough, but it use of \tex{} conditionals is
+different enough that many people find it confusing.
+\begin{quote}
+\begin{verbatim}
+\newcount\foo
+\foo=10
+\loop
+ \message{\the\foo}
+ \advance \foo -1
+\ifnum \foo>0
+\repeat
+\end{verbatim}
+\end{quote}
+In this slightly tricky code, \csx{loop} starts the construct ended by
+\csx{repeat}, but \csx{repeat} also ``serves as'' the \csx{fi} to the
+\csx{ifnum}. The loop above prints the numbers from 10 down to 1 via
+\tex{} \csx{message} (i.e., on the console output).
+
+The \Package{multido} package is also `generic' (usable both in
+\plaintex{} and latex{}); it defines a command \csx{multido} with
+three arguments:
+\begin{quote}
+ % ! line break
+ \cmdinvoke{multido}{\meta{variables}}{\meta{repetitions}}{\meta{stuff to repeat}}
+\end{quote}
+When the macro is executing, the \meta{stuff to repeat} gets executed
+\meta{repetitions} times; the \meta{variables} gives a list of
+variables that can be used in \meta{stuff}. Each variable is a
+composite of a command sequence and how it varies; so a variable
+``\csx{iz}\texttt{=2+4}'' sets \csx{iz} to \texttt{2} first time
+around, then \texttt{6} and \texttt{10} in the next two iterations,
+and so on. (The variable \csx{iz} is an integer; variables with other
+initial letters represent different data types.)
+
+% [do these things matter?]
+% The \latexe{} kernel has commands \csx{@for} and \csx{@tfor}.
+%
+% The \latex{}3 kernel includes the command |\prg_replicate:nn|; this
+% information isn't much use unless you're a \latex{}3 user.
+Both current \latex{} and (experimental) \latex{}3 have iteration
+commands for internal use and for package writers; their use is
+probably not recommendable.
+
+The \latex{} distribution package \Package{ifthen} offers the macro
+\csx{whiledo}:
+\begin{quote}
+\begin{verbatim}
+\newcounter{ct}
+...
+\setcounter{ct}{1}
+\whiledo {\value{ct} < 5}%
+{%
+ \thect\
+ \stepcounter {ct}%
+}
+\end{verbatim}
+\end{quote}
+
+The \Package{forloop} package provides nothing but \csx{forloop}:
+\begin{quote}
+\begin{verbatim}
+\newcounter{ct}
+...
+\forloop{ct}{1}{\value{ct} < 5}%
+{%
+ \thect\
+}
+\end{verbatim}
+\end{quote}
+as you can see, the arguments are counter, starting value and
+termination condition; an optional argument supplies a step value
+(default step is 1).
+
+The \latex{} \environment{picture} environment has a simple command
+for repeated drawing:
+\begin{quote}
+\begin{verbatim}
+\multiput(x,y)(xstep,ystep){n}{obj}
+\end{verbatim}
+\end{quote}
+which places \meta{obj} (intended to be a bit of picture)
+\meta{n} times at positions (\meta{x}, \meta{y}),
+(\meta{x}+\meta{xstep}, \meta{y}+\meta{ystep}),
+(\meta{x}+2\meta{xstep}, \meta{y}+2\meta{ystep}) and so on, adding the
+displacement again each time. The command was designed for use in
+\environment{picture}, but it makes no check, and may even be used to
+provide eccentric typesetting in a ``regular'' sentence, such as:
+\begin{quote}
+\begin{verbatim}
+Here \multiput(0,0)(1,1){3}{we} are again.
+\end{verbatim}
+\end{quote}
+with predictable (if not actually desirable) effect. It may be used
+with nothing but an iterative calculation in the braced argument, in
+which case its graphical capabilities have no effect.
+
+The \Package{pgffor} package, which is part of the % ! line break
+\Qref*{\Package{pgf} distribution}{Q-drawing}, also
+provides iterations to support the needs of graphics. Its syntax is
+in the style of common programming languages:
+\begin{quote}
+\begin{verbatim}
+\usepackage{pgffor}
+\newcommand{\cmd}{-x-}
+...
+\foreach \n in {1,...,4}{\cmd{}}
+\end{verbatim}
+\end{quote}
+typesets ``\texttt{-x-\relax-x-\relax-x-\relax-x-}''
+
+The \csx{foreach} command has the potential drawback that its repeated
+unit is executed in a group, so that any calculations done within the
+loop are lost (unless their result is made \csx{global}); however, it
+does not `build in' its graphical origins (as \csx{multiput} does) so
+its potential outside its own graphics environment ``home'' is more
+clear.
+%
+%% can't convince myself that \naturalloop helps with anything
+% The \Package{etextools} package provides \csx{naturalloop}, which
+% repeats material according to a count argument that you give it.
+%
+%% this stuff removed, following the observation that the package's use
+%% of \repeat is inconsistent with both plain tex and latex; pity --
+%% it's a nice package apart from being totally unusable :-(
+%
+% The \Package{repeat} package provides a \csx{for} command that
+% encompasses a lot of the above; for example:
+% \begin{quote}
+% \begin{verbatim}
+% \input repeat
+% \newcount\foo
+% \repeat
+% \for{foo} \from{1} \to{10} \do{x*}
+% \end{verbatim}
+% \end{quote}
+% which will typeset \texttt{x*} ten times (the count \csx{foo} will
+% end up with value 11).
+%
+% Note the \plaintex{} usage: \Package{repeat} is ``generic'' and
+% defines commands that are comfortable to \plaintex{} users, while
+% remaining usable by \latex{} users.
+%
+% The complete syntax is given in the meta-expression:
+% \begin{quote}
+% \begin{verbatim}
+% \repeat
+% \for{var}
+% \from{<start>} \by{<step>} \to{<end>}
+% \downto{<end>} \until{<cond>} \while{<cond>}
+% \do{<operate on something>}
+% \end{verbatim}
+% \end{quote}
+% You must choose a consistent set of \csx{from}, \csx{by}, \csx{to},
+% \csx{downto}, \csx{until} and \csx{while} (none is actually required,
+% but of course any loop has to have \emph{some}).
+
+% In summary, while it is certainly possible to write this sort of code as
+% a private project (for example, using the \etex{} \csx{numexpr}
+% primitive), one cannot deny that plenty of choice for the task is
+% readily available.
+%
+% (the above ignore Pic\tex{}, which almost certainly has similar
+% functions, but in the absence of a manual\dots{})
+\begin{ctanrefs}
+%\item[etextools.sty]\CTANref{etextools}
+\item[forarray.sty]\CTANref{forarray}
+\item[forloop.sty]\CTANref{forloop}
+\item[ifthen.sty]Distributed as part of \CTANref{latex}
+\item[multido.sty]\CTANref{multido}
+\item[pgffor.sty]Distributed as part of \CTANref{pgf}
+%\item[repeat.tex]\CTANref{repeat}
+\end{ctanrefs}
+\LastEdit{2013-03-01}
+
+\Question[Q-repeat-set]{Repeating something for each `thing' in a set}
+
+As another question % line break!
+(\Qref*{repeating something a given number of times}{Q-repeat-num})
+explains, \tex{} is not explicitly designed for `regular' programming
+operations. As a result, we must resort to arcane tricks to do the
+seemingly simple task of repeating an operation. This answer deals
+with repeating an operation for each of a given set of objects.
+
+The \Package{etoolbox} package provides iteration over a
+comma-separated list of items, in its \csx{docsvlist} and
+\csx{forcsvlist} commands; they are well-described in the package
+documentation. The \Package{datatool} package manages ``databases''
+(of its own definition) and you may iterate over entries in such a
+database using the command \csx{DTLforeach}.
+
+The \Package{forarray} package defines its own ``list'' and ``array''
+structures, together with commands \csx{ForEach} and \csx{ForArray}
+which enable a command to be executed for each element in a list or
+array, respectively.
+
+The \Package{dowith} defines a pair of macros \csx{DoWith} and
+\csx{StopDoing} that process each ``thing'' between them; a trivial
+example of use is:
+\begin{quote}
+\begin{verbatim}
+\usepackage{dowith}
+...
+\begin{document}
+\newcommand{\foo}[1]{\message{#1+}
+\DoWith\foo a{BBB}c\StopDoing
+\end{verbatim}
+\end{quote}
+which produces terminal output:
+\begin{quote}
+\begin{verbatim}
+a+ BBB+ c+
+\end{verbatim}
+\end{quote}
+so, the macros have found 3 ``things'', including one with braces
+around it. (The interpolated spaces come from the primitive
+\csx{message} command.)
+
+The only constraint is that all commands in the enclosed stuff are
+``expandable'' (which means, for example, that you may not use
+commands with optional arguments).
+
+From the same stable (as \Package{dowith}) comes the package
+\Package{commado}, that provides commands \csx{DoWithCSL} (apply a
+command to each element of a comma-separated-variable list) and
+\csx{DoWithBasesExts} (apply a command to each of a set of files,
+defined by base name and ``extension''). Use of these \csx{DoWith*}
+macros is also expandable (if the command applied to the list elements
+is itself expandable).
+\begin{ctanrefs}
+\item[commado.sty]\CTANref{commado}
+\item[datatool.sty]\CTANref{datatool}
+\item[dowith.sty]\CTANref{dowith}
+\item[etoolbox.sty]\CTANref{etoolbox}
+\item[filesdo.sty]Distributed with \CTANref{commado}
+\end{ctanrefs}
+\LastEdit{2013-02-20}
+
+%See \url{http://tex.stackexchange.com/questions/16189/repeat-command-n-times}
+%for details (do i need this any more?)
+
+\Question[Q-findwidth]{Finding the width of a letter, word, or phrase}
+
+Put the word in a box, and measure the width of the box. For example,
+\begin{quote}
+\begin{verbatim}
+\newdimen\stringwidth
+\setbox0=\hbox{hi}
+\stringwidth=\wd0
+\end{verbatim}
+\end{quote}
+Note that if the quantity in the \csx{hbox} is a phrase, the actual
+measurement only approximates the width that the phrase will occupy in
+running text, since the inter-word glue can be adjusted in paragraph
+mode.
+
+The same sort of thing is expressed in \LaTeX{} by:
+\begin{quote}
+\begin{verbatim}
+\newlength{\gnat}
+\settowidth{\gnat}{\textbf{small}}
+\end{verbatim}
+\end{quote}
+This sets the value of the length command |\gnat| to the width of ``small''
+in bold-face text.
+
+\Question[Q-patch]{Patching existing commands}
+
+In the general case (possibly sticking something in the middle of an
+existing command) this is difficult. However, the common requirement,
+to add some code at the beginning or the end of an existing command,
+is conceptually quite easy. Suppose we want to define a version of a
+command that does some small extension of its original definition: we
+would naturally write:
+\begin{quote}
+\begin{verbatim}
+\renewcommand{\splat}{\mumble\splat}
+\end{verbatim}
+\end{quote}
+However, this would not work: a call to \csx{splat} would execute
+\csx{mumble}, and then call the redefined \csx{splat} again; this is an
+`unterminated recursion', that will quickly exhaust \TeX{}'s memory.
+
+Fortunately, the \TeX{} primitive \csx{let} command comes to our
+rescue; it allows us to take a ``snapshot'' of the current state of a
+command, which we can then use in the redefinition of the command.
+So:
+\begin{quote}
+\begin{verbatim}
+\let\OldSmooth\smooth
+\renewcommand{\smooth}{\mumble\OldSmooth}
+\end{verbatim}
+\end{quote}
+effects the required patch, safely. Adding things at the end of a
+command works similarly.
+
+If \csx{smooth} takes arguments, one must pass them on:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\let\OldSmooth\smooth
+\renewcommand{\smooth}[2]{\mumble\OldSmooth{#1}{#2}}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\let\OldSmooth\smooth
+\renewcommand{\smooth}[2]%
+ {\mumble\OldSmooth{#1}{#2}}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+
+The situation is more difficult still if \csx{smooth} takes an
+optional argument; the structure of the command is so complex that the
+simple \csx{let} command does not retain the necessary detail. In
+this case, we need the \Package{letltxmacro} package which knows about all
+sorts of \latex{} commands and how to replicate them. Suppose we have
+a command defined as:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\rough}[1][\default]{...}
+\end{verbatim}
+\end{quote}
+with an optional argument (substituted with \csx{default} if it's not
+present) as well as an ordinary one. In this case we copy it using
+\begin{quote}
+\begin{verbatim}
+\LetLtxMacro{\NewRough}{\rough}
+\end{verbatim}
+\end{quote}
+and then repeat the technique we had above, with one extension:
+\begin{quote}
+\begin{verbatim}
+\renewcommand{\rough}[1][\newdef]%
+ {\mumble\OldRough[{#1}]{#2}}
+\end{verbatim}
+\end{quote}
+We see here that (for tedious argument-matching reasons) it is
+necessary to provide braces arround the optional argument that is
+being passed on.
+
+The general case may be achieved in two ways. First, one can use the
+\LaTeX{} command \csx{CheckCommand}; this compares an existing command
+with the definition you give it, and issues a warning if two don't
+match. Use is therefore:
+\begin{quote}
+ |\CheckCommand{\complex}{|\meta{original definition}|}|\\
+ |\renewcommand{\complex}{|\meta{new definition}|}|
+\end{quote}
+This technique is obviously somewhat laborious, but if the original
+command comes from a source that's liable to change under the control
+of someone else, it does at least warn you that your patch is in
+danger of going wrong.
+
+Otherwise, \LaTeX{} users may use one of the \Package{patchcmd},
+\Package{ted} or \Package{etoolbox} packages.
+
+The \Package{patchcmd} package addresses a slightly simpler task, by
+restricting the set of commands that you may patch; you mayn't patch
+any command that has an optional argument, though it does deal with
+the case of commands defined with \csx{DeclareRobustCommand}. The
+package defines a \csx{patchcommand} command, that takes three
+arguments: the command to patch, stuff to stick at the front of its
+definition, and stuff to stick on the end of its definition. So,
+after
+\begin{quote}
+\begin{verbatim}
+\def\b{b}
+\patchcmd\b{a}{c}
+\end{verbatim}
+\end{quote}
+we will have a new version of \csx{b} defined as ``\texttt{abc}''.
+
+The \Package{ted} package is a `token list editor', and provides a
+command \csx{substitute} which will patch the
+contents of a macro, putting the result in a token-list, or
+(in the form \csx{Substitute*}) using the result to (re)define a
+macro. The following example defines a simple macro, and then changes
+its definition:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\myfont}%
+ {\Large\sffamily\selectfont}
+\Substitute*[\renewcommand{\myfont}]{\myfont}%
+ {\Large\sffamily}{\huge\itshape}
+\end{verbatim}
+\end{quote}
+The macro's definition is now:
+\begin{quote}
+\begin{verbatim}
+\huge\itshape\selectfont
+\end{verbatim}
+\end{quote}
+
+The package also offers a command \csx{ShowTokens}, which shows the
+content of its argument, one token to a line, with details of the
+token's category code, etc. This is recommended as a debugging tool.
+
+The \Package{etoolbox} package (which provides user access to \eTeX{}'s
+programming facilities) provides a command \csx{patchcmd} which is
+very similar to \csx{Substitute}, except that it only replaces a
+single instance of the token(s) in its search pattern. Since not all
+commands may be patched in this way, \csx{patchcmd} takes extra
+arguments for \emph{success} and \emph{failure} cases. The
+package also provides commands that prepend (\csx{pretocmd}) or append
+(\csx{apptocmd}) to the definition of a command. Not all commands may
+be patched in this way; the package provides a command
+\csx{ifpatchable} which checks the prerequisites, and checks that the
+target command's body does indeed include the patch string you propose
+to use. (The command \csx{ifpatchable*} omits the test on the patch
+string.)
+
+The \Package{regexpatch} package deals with cases that are
+inaccessible with \Package{etoolbox}; it uses the regular expression
+(pattern-matching) package \Package{l3regex} from the \latex{}3
+distribution to find the code you need to patch. The package also
+``knows about'' robust commands and about
+\Qref*{\Package{biblatex}}{Q-biblatex}.
+
+Finally, we'll briefly consider a package that is (just about)
+usable, but not really recommendable. \Package{Patch} gives you an
+ingenious (and difficult to understand) mechanism, and comes as an
+old-style \LaTeX{} documented macro file, which can no longer be
+processed to \Qref*{produce formatted documentation, etc.\@}{Q-install-doc}.
+Fortunately, the file (\File{patch.doc}) may be input directly, and
+``documentation'' may found by reading the source of the package.
+Roughly speaking, one gives the command a set of instructions
+analogous to \ProgName{sed} substitutions, and it regenerates the
+command thus amended. Unless you can't do your job any other way,
+\Package{patch} is best avoided.
+\begin{ctanrefs}
+\item[etoolbox.sty]\CTANref{etoolbox}
+\item[l3regex.sty]Distributed as part of \CTANref{l3experimental}[l3regex]
+\item[letltxmacro.sty]Distributed as part of \CTANref{oberdiek}[letltxmacro]
+\item[patch.doc]\CTANref{patch}
+\item[patchcommand.sty]\CTANref{patchcmd}
+\item[regexpatch.sty]\CTANref{regexpatch}
+\item[ted.sty]\CTANref{ted}
+\end{ctanrefs}
+\LastEdit{2012-12-21}
+
+\Question[Q-compjobnam]{Comparing the ``job name''}
+
+The token \csx{jobname} amusingly produces a sequence of characters
+whose category code is 12 (`other'), regardless of what the characters
+actually are. Since one inevitably has to compare a macro with the
+contents of another macro (using \csx{ifx}, somewhere) one needs to
+create a macro whose expansion looks the same as the expansion of
+\csx{jobname}. We find we can do this with \csx{meaning}, if we strip
+the ``\csx{show} command'' prefix.
+
+The full command looks like:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\def\StripPrefix#1>{}
+\def\jobis#1{FF\fi
+ \def\predicate{#1}%
+ \edef\predicate{\expandafter\StripPrefix\meaning\predicate}%
+ \edef\job{\jobname}%
+ \ifx\job\predicate
+}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\def\StripPrefix#1>{}
+\def\jobis#1{FF\fi
+ \def\predicate{#1}%
+ \edef\predicate{\expandafter\StripPrefix
+ \meaning\predicate}%
+ \edef\job{\jobname}%
+ \ifx\job\predicate
+}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+And it's used as:
+\begin{quote}
+\begin{verbatim}
+\if\jobis{mainfile}%
+ \message{YES}%
+\else
+ \message{NO}%
+\fi
+\end{verbatim}
+\end{quote}
+Note that the command \csx{StripPrefix} need not be defined if you're
+using \LaTeX{}~--- there's already an % line break!
+\Qref*{internal command}{Q-atsigns} \csx{strip@prefix} that you can
+use.
+
+\Question[Q-isitanum]{Is the argument a number?}
+
+\TeX{}'s own lexical analysis doesn't offer the macro programmer
+terribly much support: while category codes will distinguish letters
+(or what \TeX{} currently thinks of as letters) from everything else,
+there's no support for analysing numbers.
+
+The simple-minded solution is to compare numeric characters with the
+characters of the argument, one by one, by a sequence of direct tests,
+and to declare the argument ``not a number'' if any character fails
+all comparisons:
+\begin{quote}
+\begin{verbatim}
+\ifx1#1
+\else\ifx2#1
+...
+\else\ifx9#1
+\else\isanumfalse
+\fi\fi...\fi
+\end{verbatim}
+\end{quote}
+which one would then use in a tail-recursing macro to gobble an
+argument. One could do slightly better by assuming (pretty safely)
+that the digits' character codes are consecutive:
+\begin{quote}
+\begin{verbatim}
+\ifnum`#1<`0 \isanumfalse
+\else\ifnum`#1>`9 \isanumfalse
+ \fi
+\fi
+\end{verbatim}
+\end{quote}
+again used in tail-recursion. However, these forms aren't very
+satisfactory: getting the recursion ``right'' is troublesome (it has a
+tendency to gobble spaces in the argument), and in any case \TeX{}
+itself has mechanisms for reading numbers, and it would be nice to use
+them.
+
+Donald Arseneau's \Package{cite} package offers the following test
+for an argument being a strictly positive integer:
+\begin{quote}
+\begin{verbatim}
+\def\IsPositive#1{%
+ TT\fi
+ \ifcat_\ifnum0<0#1 _\else A\fi
+}
+\end{verbatim}
+\end{quote}
+which can be adapted to a test for a non-negative integer thus:
+\begin{quote}
+\begin{verbatim}
+\def\IsNonNegative{%
+ \ifcat_\ifnum9<1#1 _\else A\fi
+}
+\end{verbatim}
+\end{quote}
+or a test for any integer:
+\begin{quote}
+\begin{verbatim}
+\def\gobbleminus#1{\ifx-#1\else#1\fi}
+\def\IsInteger#1{%
+ TT\fi
+ \ifcat_\ifnum9<1\gobbleminus#1 _\else A\fi
+}
+\end{verbatim}
+\end{quote}
+but this surely stretches the technique further than is reasonable.
+
+If we don't care about the sign, we can use \TeX{} to remove the
+entire number (sign and all) from the input stream, and then look at
+what's left:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\def\testnum#1{\afterassignment\testresult
+ \count255=0#1 \end}
+\def\testresult#1\end{\ifx\end#1\end}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\def\testnum#1{\afterassignment\testresult\count255=0#1 \end}
+\def\testresult#1\end{\ifx\end#1\end\isanumtrue\else\isanumfalse\fi}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+(which technique is due to David Kastrup; the trick for avoiding the
+errors, noted in an earlier version of this answer, was suggested by
+Andreas Matthias).
+In a later thread on the same topic, Michael Downes offered:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\def\IsInteger#1{%
+ TT\fi
+ \begingroup \lccode`\-=`\0 \lccode`+=`\0
+ \lccode`\1=`\0 \lccode`\2=`\0 \lccode`\3=`\0
+ \lccode`\4=`\0 \lccode`\5=`\0 \lccode`\6=`\0
+ \lccode`\7=`\0 \lccode`\8=`\0 \lccode`\9=`\0
+ \lowercase{\endgroup
+ \expandafter\ifx\expandafter\delimiter
+ \romannumeral0\string#1}\delimiter
+}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\def\IsInteger#1{%
+ TT\fi
+ \begingroup \lccode`\-=`\0 \lccode`+=`\0
+ \lccode`\1=`\0 \lccode`\2=`\0
+ \lccode`\3=`\0 \lccode`\4=`\0
+ \lccode`\5=`\0 \lccode`\6=`\0
+ \lccode`\7=`\0 \lccode`\8=`\0
+ \lccode`\9=`\0
+ \lowercase{\endgroup
+ \expandafter\ifx\expandafter\delimiter
+ \romannumeral0\string#1}\delimiter
+}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+which relies on \csx{romannumeral} producing an empty result if its
+argument is zero. Sadly, this technique has the unfortunate property
+that it accepts simple expressions such as `\texttt{1+2-3}'; this
+could be solved by an initial \csx{gobbleminus}-like construction.
+
+All the complete functions above are designed to be used in \TeX{}
+conditionals written ``naturally''~--- for example:
+\begin{quote}
+\begin{verbatim}
+\if\IsInteger{<subject of test>}%
+ <deal with integer>%
+\else
+ <deal with non-integer>%
+\fi
+\end{verbatim}
+\end{quote}
+The \LaTeX{} \Class{memoir} class has an internal command of its own,
+\cmdinvoke*{checkifinteger}{num}, that sets the conditional command
+\csx{ifinteger} according to whether the argument was an integer.
+
+Of course, all this kerfuffle would be (essentially) void if there was
+a simple means of ``catching'' \TeX{} errors. Imagining an
+error-catching primitive \csx{ifnoerror}, one might write:
+\begin{quote}
+\begin{verbatim}
+\def\IsInteger#1{%
+ TT%
+ \ifnoerror
+ \tempcount=#1\relax
+% carries on if no error
+ \expandafter\iftrue
+ \else
+% here if there was an error
+ \expandafter\iffalse
+ \fi
+}
+\end{verbatim}
+\end{quote}
+thus using \TeX{}'s own integer-parsing code to do the check. It's a
+pity that such a mechanism was never defined (it could be that it's
+impossible to program within \TeX{}!).
+\begin{ctanrefs}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-hash]{Defining macros within macros}
+
+The way to think of this is that |##| gets replaced by |#| in just the
+same way that |#1| gets replaced by `whatever is the first argument'.
+
+So if you define a macro:
+\begin{quote}
+\begin{verbatim}
+\newcommand\a[1]{+#1+#1+#1+}
+\end{verbatim}
+\end{quote}
+or (using the \tex{} primitive \csx{def}):
+\begin{quote}
+\begin{verbatim}
+\def\a#1{+#1+#1+#1+}
+\end{verbatim}
+\end{quote}
+and use it as \cmdinvoke{a}{b},
+the macro expansion produces `+b+b+b+',
+as most people would expect.
+
+However, if we now replace part of the macro:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\newcommand\a[1]{+#1+%
+ \newcommand\x[1]{xxx#1}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand\a[1]{+#1+\newcommand\x[1]{xxx#1}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+then \cmdinvoke{a}{b} will give us the rather odd
+\begin{quote}
+ +b+\cmdinvoke{newcommand}{x}[1]{xxxb}
+\end{quote}
+so that the new \csx{x} ignores its argument.
+
+If we use the \tex{} primitive:
+\begin{quote}
+\begin{verbatim}
+\def\a#1{+#1+\def\x #1{xxx#1}}
+\end{verbatim}
+\end{quote}
+\cmdinvoke{a}{b} will expand to `+b+|\def\x b{xxxb}|'. This
+defines \csx{x} to be a macro \emph{delimited} by |b|, and taking no
+arguments, which is surely not what was intended!
+
+Actually, to define \csx{x} to take an argument, we need
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\newcommand\a[1]{+#1+%
+ \newcommand\x[1]{xxx##1}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand\a[1]{+#1+\newcommand\x[1]{xxx##1}}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+or, using the \tex{} primitive definition:
+\begin{quote}
+\begin{verbatim}
+\def\a#1{+#1+\def\x ##1{xxx##1}}
+\end{verbatim}
+\end{quote}
+and \cmdinvoke{a}{b} will expand to
+\begin{quote}
+ +b+|\def\x #1{xxx#1}|
+\end{quote}
+because |#1| gets replaced by `b'
+and |##| gets replaced by |#|.
+
+To nest a definition inside a definition inside a definition then you
+need |####1|, doubling the number of |#| signs; and at the next level
+you need 8~|#|s each time, and so on.
+
+\Question[Q-spinmacro]{Spaces in macros}
+
+It's very easy to write macros that produce space in the typeset
+output where it's neither desired nor expected. Spaces introduced by
+macros are particularly insidious because they don't amalgamate with
+spaces around the macro (unlike consecutive spaces that you
+type), so your output can have a single bloated space that proves
+to be made up of two or even more spaces that haven't amalgamated.
+And of course, your output can also have a space where none was wanted
+at all.
+
+Spaces are produced, inside a macro as elsewhere, by space or tab
+characters, or by end-of-line characters. There are two basic rules
+to remember when writing a macro: first, the rules for ignoring spaces
+when you're typing macros are just the same as the rules that apply
+when you're typing ordinary text, and second, rules for ignoring
+spaces do \emph{not} apply to spaces produced while a macro is being
+obeyed (``expanded'').
+
+Spaces are ignored in vertical mode (between paragraphs), at the
+beginning of a line, and after a command name. Since sequences of
+spaces are collapsed into one, it `feels as if' spaces are ignored if
+they follow another space. Space can have syntactic meaning after
+certain sorts of non-braced arguments (e.g., \emph{count} and
+\emph{dimen} variable assignments in \plaintex{}) and after certain
+control words (e.g., in \csx{hbox} |to|, so again we have instances
+where it `feels as if' spaces are being ignored when they're merely
+working quietly for their living.
+
+Consider the following macro, fairly faithfully adapted from one that
+appeared on \Newsgroup{comp.text.tex}:
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand{\stline}[1]
+ { \bigskip \makebox[2cm]{ \textbf{#1} } }
+\end{verbatim}
+\end{quote}
+(the original appeared on a single line: it's wrapped here to fit in
+the printed \acro{FAQ}'s narrow columns).
+
+\nothtml{\noindent}
+\end{narrowversion}
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand{\stline}[1]{ \bigskip \makebox[2cm]{ \textbf{#1} } }
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+The macro definition contains five spaces:
+\begin{itemize}
+\item after the opening |{| of the macro body; this space will be
+ ignored, not because ``because the macro appears at the start of a
+ line'', but rather because the macro was designed to operate between
+ paragraphs
+\item after \csx{bigskip}; this space will be ignored (while the macro
+ is being defined) because it follows a command name
+\item after the |{| of the mandatory argument of \csx{makebox}; even
+ though this space will inevitably appear at the start of an output
+ line, it will \emph{not} be ignored
+\item after the |}| closing the argument of \csx{textbf}; this space
+ will not be ignored, but may be overlooked if the argument is well
+ within the |2cm| allowed for it
+\item after the |}| closing the mandatory argument of \csx{makebox};
+ this space will not be ignored
+\end{itemize}
+The original author of the macro had been concerned that the starts of
+his lines with this macro in them were not at the left margin, and
+that the text appearing after the macro wasn't always properly
+aligned. These problems arose from the space at the start of the
+mandatory argument of \csx{makebox} and the space immediately after the
+same argument. He had written his macro in that way to emphasise the
+meaning of its various parts; unfortunately the meaning was rather
+lost in the problems the macro caused.
+
+The principal technique for suppressing spaces is the use of
+\texttt{\textpercent{}} characters: everything after a
+\texttt{\textpercent{}} is ignored, even the end of line itself (so
+that not even the end of line can contribute an unwanted space). The
+secondary technique is to ensure that the end of line is preceded by a
+command name (since the end of line behaves like a space, it will be
+ignored following a command name). Thus the above command would be
+written (by an experienced programmer with a similar eye to
+emphasising the structure):
+\begin{quote}
+\begin{verbatim}
+\newcommand{\stline}[1]{%
+ \bigskip
+ \makebox[2cm]{%
+ \textbf{#1}\relax
+ }%
+}
+\end{verbatim}
+\end{quote}
+Care has been taken to ensure that every space in the revised
+definition is ignored, so none appears in the output. The revised
+definition takes the ``belt and braces'' approach, explicitly dealing
+with every line ending (although, as noted above, a space introduced
+at the end of the first line of the macro would have been ignored in
+actual use of the macro. This is the best technique, in fact~--- it's
+easier to blindly suppress spaces than to analyse at every point
+whether you actually need to. Three techniques were used to suppress
+spaces:
+\begin{itemize}
+\item placing a \texttt{\textpercent{}} character at the end of a line
+ (as in the 1st, 3rd and 5th lines),
+\item ending a line `naturally' with a control sequence, as in line 2,
+ and
+\item ending a line with an `artificial' control sequence, as in line
+ 4; the control sequence in this case (\csx{relax}) is a no-op in many
+ circumstances (as here), but this usage is deprecated~--- a
+ \texttt{\textpercent{}} character would have been better.
+\end{itemize}
+Beware of the (common) temptation to place a space \emph{before} a
+\texttt{\textpercent{}} character: if you do this you might as well omit
+the \texttt{\textpercent{}} altogether.
+
+In ``real life'', of course, the spaces that appear in macros are far
+more cryptic than those in the example above. The most common spaces
+arise from unprotected line ends, and this is an error that
+occasionally appears even in macros written by the most accomplished
+programmers.
+
+\Question[Q-moren9]{How to break the 9-argument limit}
+
+If you think about it, you will realise that Knuth's command
+definition syntax:
+\begin{quote}
+\begin{verbatim}
+\def\blah#1#2 ... #9{<macro body>}
+\end{verbatim}
+\end{quote}
+is intrinsically limited to just 9 arguments. There's no direct way
+round this: how would you express a 10th argument?~--- and ensure that
+the syntax didn't gobble some other valid usage?
+
+If you really must have more than 9 arguments, the way to go is:
+\begin{quote}
+\begin{verbatim}
+\def\blah#1#2 ... #9{%
+ \def\ArgI{{#1}}%
+ \def\ArgII{{#2}}%
+ ...
+ \def\ArgIX{{#9}}%
+ \BlahRelay
+}
+\def\BlahRelay#1#2#3{%
+ % arguments 1-9 are now in
+ % \ArgI-\ArgIX
+ % arguments 10-12 are in
+ % #1-#3
+ <macro body>%
+}
+\end{verbatim}
+\end{quote}
+This technique is easily extendible by concert pianists of the \TeX{}
+keyboard, but is really hard to recommend.
+
+\LaTeX{} users have the small convenience of merely giving a number of
+arguments in the \csx{newcommand} that defines each part of the
+relaying mechanism: Knuth's restriction applies to \csx{newcommand}
+just as it does to \csx{def}. However, \LaTeX{} users also have the
+way out of such barbarous command syntax: the \Package{keyval}
+package. With \Package{keyval}, and a bit of programming, one can
+write really quite sophisticated commands, whose invocation might look
+like:
+\begin{quote}
+\begin{verbatim}
+\flowerinstance{species=Primula veris,
+ family=Primulaceae,
+ location=Coldham's Common,
+ locationtype=Common grazing land,
+ date=1995/04/24,
+ numplants=50,
+ soiltype=alkaline
+}
+\end{verbatim}
+\end{quote}
+The merit of such verbosity is that it is self-explanatory: the typist
+doesn't have to remember that argument twelve is |soiltype|, and so
+on: the commands may be copied from field notes quickly and
+accurately.
+\begin{ctanrefs}
+\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval]
+\end{ctanrefs}
+
+ * faq-mac-prog.tex (q-keyval): tweak words about getoptk
+
+\Question[Q-keyval]{Key-value input for macros and package options}
+
+When we discussed % !line break
+\Qref*{extending the number of arguments to a macro}{Q-moren9}, we
+suggested that large numbers of arguments, distinguished only by their
+position, aren't very kind to the user, and that a package such as
+\Package{keyval} offers a more attractive user interface. We now
+consider the packages that the macro programmer might use, to create
+such a user interface.
+
+The simplest key-value processor (for \latex{}, at least) remains
+\Package{keyval}; it has a command \csx{define@key} to declare a key
+and a \emph{handler} to process it, and a macro \csx{setkeys} to offer
+values to the handler of one or more keys. Thus:
+\begin{quote}
+\begin{verbatim}
+\define@key{my}{foo}{Foo is #1\par}
+\define@key{my}{bar}[99]{Bar is #1\par}
+...
+\setkeys{my}{foo=3,bar}
+\end{verbatim}
+\end{quote}
+will produce output saying:
+\begin{quote}
+ Foo is 3\par{}
+ Bar is 99
+\end{quote}
+This has defined two keys `\texttt{foo}' and `\texttt{bar}' in family
+`\texttt{my}', and then executed them, the first with argument
+`\texttt{3}' and the second with no argument, so that the default
+value of `\texttt{99}' is picked up. In effect, the two calls to
+\csx{define@key} are simply defining commands, as (for example):
+\begin{quote}
+\begin{verbatim}
+\newcommand{\KV@my@foo}[1]{Foo is #1}
+\end{verbatim}
+\end{quote}
+(the definition of \csx{KV@my@bar} is similar, but trickier). The
+command \csx{setkeys} knows how to find those commands when it needs to
+process each key~--- it is easy to regurgitate the structure of the
+command name, with family name (`\texttt{my}', here) after the first
+`\texttt{@}', and the key name after the second `\texttt{@}'. (The
+`\texttt{KV}' part is fixed, in \Package{keyval}.)
+
+These simple commands are enough, in fact, to process the botanical
+example offered as replacement for multi-argument commands in % ! line break
+\Qref[question]{the question mentioned above}{Q-moren9}, or the
+optional arguments of the \csx{includegraphics} command of the
+\Package{graphicx} package. (The last is, in fact, what
+\Package{keyval} was designed to do.)
+
+However, we need more if we're to to have package options in
+`key-value' form. Packages like \Package{hyperref} have enormously
+complicated package options which need key-value processing at
+\csx{ProcessOptions} time: \Package{keyval} can't do that on its own.
+
+Heiko Oberdiek's \Package{kvoptions} package comes to our help: it
+enables the programmer to declare class or package options that
+operate as key and value pairs. The package defines commands
+\csx{DeclareBoolOption} for options whose value should be either
+\emph{true} or \emph{false}, and \csx{DeclareStringOption} for all
+other options that have a value. Keys are declared using
+\Package{keyval} and may remain available for use within the document,
+or may be `cancelled' to avoid confusion. If you have loaded
+\Package{kvoptions}, the \LaTeX{} kernel's \csx{DeclareOption} becomes
+\csx{DeclareVoidOption} (it's an option with no value), and
+\csx{DeclareOption*} becomes \csx{DeclareDefaultOption}.
+
+Heiko also provides \Package{kvsetkeys} which is a more robust version
+of \Package{setkeys}, with some of the rough edges made smoother.
+
+Hendri Adriaens' \Package{xkeyval} offers more flexibility than
+the original \Package{keyval} and is more robust than the original,
+too. Like \Package{kvoptions}, the package also has mechanisms to
+allow class and package options in key-value form (macros
+\csx{DeclareOptionX}, \csx{ExecuteOptionsX} and \csx{ProcessOptionsX}.
+\Package{Pstricks} bundle packages use a \Package{xkeyval} derivative
+called \Package{pst-xkey} for their own key-value manipulation.
+% xkvview? (i think we can ignore xkvltxp for these purposes)
+
+The (widely-respected) \Package{pgf} graphics package has its own
+key-value package called \Package{pgfkeys}. The documentation of the
+package (part of the huge \Package{pgf} manual, in part 5,
+``utilities'') contains a useful comparison with other key-value
+systems; some notable differences are:
+\begin{itemize}
+\item key organisation: \Package{pgfkeys} uses a tree structure, while
+ \Package{keyval} and \Package{xkeyval} both associate keys with a family;
+\item \Package{pgfkeys} supports multi-argument key code; and
+\item \Package{pgfkeys} can support call-backs when an unknown key
+ appears (these things are called \emph{handlers}.
+\end{itemize}
+Keys are organized in a tree that is reminiscent of the Unix fille
+tree. A typical key might be, \File{/tikz/coordinate system/x} or
+just \File{/x}. When you specify keys you can provide the complete
+path of the key, but you usually just provide the name of the key
+(corresponding to the file name without any path) and the path is
+added automatically. So a \csx{pgfkeys} command might be:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\pgfkeys{/my key=hello,/your keys/main key=something\strange,
+ key name without path=something else}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\pgfkeys{/my key=hello,
+ /your keys/main key=something\strange,
+ key name without path=something else}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+and for each key mentioned, the associated code will be executed.
+\dots{} and that code is also set up using \csx{pgfkeys}:
+\begin{quote}
+\begin{verbatim}
+\pgfkeys{/my key/.code=The value is '#1'.}
+\end{verbatim}
+\end{quote}
+after which
+\begin{quote}
+\begin{verbatim}
+\pgfkeys{/my key=hi!}
+\end{verbatim}
+\end{quote}
+will produce just
+\begin{quote}
+ The value is 'hi!'.
+\end{quote}
+The manual goes on, showing how to define a key with two arguments,
+how to provide default value for a key, and how to define aliases for
+particular key sequences (which are called ``styles''). All in all,
+it seems a well thought-out system, offering a lot of flexibility that
+isn't available with the other keys packages. However, there seems to
+be no mechanism for using \Package{pgfkeys} keys as part of the
+options of another package, in the way that \Package{kvoptions} does.
+
+The \Package{l3kernel} programming layer for \Qref*{\LaTeX{}3}{Q-LaTeX3}
+includes the \Package{l3keys} module. Inspired by \Package{pgfkeys},
+it provides a keyval-based method for the programmer to create keys.
+As with keyval and derivatives, \Package{l3keys} uses separate macros
+for defining and setting keys. The package \Package{l3keys2e} makes
+it possible for \latexe{} class and package
+options to be processed using \Package{l3keys}. \Package{L3kernel}
+code can be used within existing LaTeX2e documents, so
+\Package{l3keys} is also available to the \latexe{} programmer `direct'.
+
+Another key-value system that's part of larger set of macros is
+\Package{scrbase}, which uses the facilities of \Package{keyval} to
+build a larger set of facilities, originally for use within the
+\Class{KOMA-script} bundle. For English-speaking authors, there are
+difficulties from the German-only documentation; however, from a
+partial translation available to the author of this answer, a summary
+is possible. The package may build on the facilities either of
+\Package{kyeval} or of \Package{xkeyval}, and builds its functionality
+on the structure of the `key family'. The user may define family
+`members' and keys are defined relative to the members. (For example,
+the package \Package{scrbase} is part of the \Class{KOMA-script}
+bundle; so its keys are all members of the \Package{scrbase.sty}
+family within the \Package{KOMA} family. The function
+\csx{FamilyProcessOptions} allows the programmer to decode the options
+of the package in terms of the package's key family. Note that there
+is no special provision made for ``traditional'' package options, as
+in the \Package{kvoptions} package.
+
+This brief summary was guided by input from two sources: a draft article
+for \textsl{TUGboat} by Joseph Wright, and the partial translation of the
+documentation of package \Package{scrbase} prepared by Philipp
+Stephani.
+
+All the above are (at least) aimed at \latex{} programming; there is
+one package, \Package{getoptk}, aimed at the \plaintex{} programmer.
+\Package{Getoptk} uses syntax inspired by that offered by \tex{}
+primitives such as \csx{hrule} and \csx{hbox}, so we are offered
+syntax such as:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\begindisplay file {chapter1} literal offset 20pt
+\end{verbatim}
+\end{quote}
+(taken from the package manual).
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\begindisplay file {chapter1} %
+ literal offset 20pt
+\end{verbatim}
+\end{quote}
+(taken from the package manual, but wrapped to fit into narrow
+columns).
+\end{narrowversion}
+
+There are (we know) people who would swear that such syntax is
+wonderful (the present author wouldn't), but the package earns its
+place as the only stand-alone key-value macros that will work in \plaintex{}.
+\begin{ctanrefs}
+\item[getoptk.tex]\CTANref{getoptk}
+\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval]
+\item[kvoptions.sty]Distributed as part of \CTANref{oberdiek}[kvoptions]
+\item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek}[kvsetkeys]
+\item[l3keys.sty]Distributed as part of \CTANref{l3kernel}
+\item[l3keys2e.sty]Distributed as part of \CTANref{l3packages}
+\item[pgfkeys.sty]Distributed as part of \CTANref{pgf}
+\item[scrbase.sty]Distributed as part of \CTANref{koma-script}
+\item[xkeyval.sty]\CTANref{xkeyval}
+\end{ctanrefs}
+\LastEdit{2011-09-06}
+
+\Question[Q-activechars]{Defining characters as macros}
+
+Single characters can act as macros (defined commands), and both
+\plaintex{} and \LaTeX{} define the character
+``\texttt{\textasciitilde}'' as a ``non-breakable space''. A
+character is made definable, or ``active'', by setting its
+\emph{category code} (catcode) to be \csx{active} (13):
+\begin{quote}
+\begin{verbatim}
+\catcode`\_=\active
+\end{verbatim}
+\end{quote}
+Any character could, in principle, be activated this way and defined
+as a macro:
+\begin{quote}
+\begin{verbatim}
+\def_{\_}
+\end{verbatim}
+\end{quote}
+which could be characterised as an over-simple answer to % ! line break
+\Qref[question]{using underscores}{Q-underscore}. However, you must be
+wary: whereas people expect an active tilde, other active characters
+may be unexpected and interact badly with other macros. Furthermore,
+by defining an active character, you preclude the character's use for
+other purposes, and there are few characters ``free'' to be subverted
+in this way.
+
+To define the character ``\texttt{z}'' as a command, one would say something
+like:
+\begin{quote}
+\begin{verbatim}
+\catcode`\z=\active
+\def z{Yawn, I'm tired}%
+\end{verbatim}
+\end{quote}
+and each subsequent ``\texttt{z}'' in the text would become a
+yawn. This would be an astoundingly bad idea for most documents, but
+might have special applications. (Note that, in ``\csx{def}\texttt{
+ z}'', ``\texttt{z}'' is no longer interpreted as a letter; the space
+is therefore not necessary~--- ``\csx{defz}'' would do; we choose to
+retain the space, for what little clarity we can manage.)
+Some \LaTeX{} packages facilitate such definitions. For example, the
+\Package{shortvrb} package with its \csx{MakeShortVerb} command.
+
+\TeX{} uses category codes to interpret characters as they are read
+from the input.
+% beware line break
+\emph{Changing a catcode value will not affect characters that have already been read}.
+Therefore, it is best if characters have fixed category codes for the
+duration of a document. If catcodes are changed for particular
+purposes (the \csx{verb} command does this), then the altered
+characters will not be interpreted properly when they appear in the
+argument to another command (as, for example, in
+% beware line-break
+\htmlonly{``}\Qref[question]{\csx{verb} in command arguments}{Q-verbwithin}\htmlonly{''}).
+An exemplary case is the \Package{doc} package, which processes .dtx
+files using the \Package{shortvrb} package to define
+\texttt{\textbar\dots{}\textbar} as a shorthand for
+\csx{verb}\texttt{\textbar\dots{}\textbar}. But \texttt{\textbar} is
+also used in the preambles of tabular environments, so that tables in
+\extension{dtx} files can only have vertical line separation between
+columns by employing special measures of some sort.
+
+Another consequence is that catcode assignments made
+in macros often don't work as expected % beware linebreak
+(\htmlonly{see ``}\Qref{Active characters in command arguments}{Q-actinarg}\htmlonly{''}).
+For example, the definition
+\begin{quote}
+\begin{verbatim}
+\def\mistake{%
+\catcode`_=\active
+\def_{\textunderscore\-}%
+}
+\end{verbatim}
+\end{quote}
+does not work because it attempts to define an ordinary \texttt{\_} character:
+When the macro is used, the category change does not apply to the
+underscore character already in the macro definition. Instead, one may
+use:
+\begin{quote}
+\begin{verbatim}
+\begingroup
+\catcode`_=\active
+\gdef\works{% note the global \gdef
+ \catcode`_=\active
+ \def_{\textunderscore\-}%
+}
+\endgroup
+\end{verbatim}
+\end{quote}
+The alternative (``tricksy'') way of creating such an isolated
+definition depends on the curious properties of \csx{lowercase}, which
+changes characters without altering their catcodes. Since there is
+always \emph{one} active character (``\texttt{\textasciitilde}''), we
+can fool \csx{lowercase} into patching up a definition without ever
+explicitly changing a catcode:
+\begin{quote}
+\begin{verbatim}
+\begingroup
+ \lccode`\~=`\_
+ \lowercase{\endgroup
+ \def~{\textunderscore\-}%
+ }%
+\end{verbatim}
+\end{quote}
+The two definitions have the same overall effect (the character is
+defined as a command, but the character does not remain active),
+except that the first defines a \csx{global} command.
+
+For active characters to be used only in maths mode, it is much better
+to leave the character having its ordinary catcode, but assign it a
+special active \emph{maths code}, as with
+\begin{quote}
+\begin{verbatim}
+\begingroup
+ \lccode`~=`x
+ \lowercase{\endgroup
+ \def~{\times}%
+ }%
+\mathcode`x="8000
+\end{verbatim}
+\end{quote}
+The special character does not need to be redefined whenever it is
+made active~--- the definition of the command persists even if the
+character's catcode reverts to its original value; the definition
+becomes accessible again if the character once again becomes active.
+\begin{ctanrefs}
+\item[doc.sty]Part of the \LaTeX{} distribution \CTANref{latex}[doc]
+\item[shortvrb.sty]Part of the \LaTeX{} distribution \CTANref{latex}[shortvrb]
+\end{ctanrefs}
+
+
+\Question[Q-actinarg]{Active characters in command arguments}
+
+Occasionally, it's nice to make one or two characters active in the
+argument of a command, to make it easier for authors to code the
+arguments.
+
+Active characters \emph{can} be used safely in such situations; but
+care is needed.
+
+An example arose while this answer was being considered: an aspirant
+macro writer posted to \Newsgroup{comp.text.tex} asking for help to
+make |#| and |b| produce musical sharp and flat signs, respectively,
+in a macro for specifying chords.
+
+The first problem is that both |#| and |b| have rather important uses
+elsewhere in \TeX{} (to say the least!), so that the characters can
+only be made active while the command is executing.
+
+Using the techniques discussed in % beware line break, next line
+\htmlonly{``}\Qref[question]{characters as commands}{Q-activechars}\htmlonly{''},
+we can define:
+\begin{quote}
+\begin{verbatim}
+\begingroup
+ \catcode`\#=\active
+ \gdef#{$\sharp$}
+\endgroup
+\end{verbatim}
+\end{quote}
+and:
+\begin{quote}
+\begin{verbatim}
+\begingroup
+ \lccode`\~=`\b
+ \lowercase{\endgroup
+ \def~{$\flat$}%
+ }
+\end{verbatim}
+\end{quote}
+The second problem is one of timing: the command has to make each
+character active \emph{before} its arguments are read: this means that
+the command can't actually ``have'' arguments itself, but must be
+split in two. So we write:
+\begin{quote}
+\begin{verbatim}
+\def\chord{%
+ \begingroup
+ \catcode`\#=\active
+ \catcode`\b=\active
+ \Xchord
+}
+\def\Xchord#1{%
+ \chordfont#1%
+ \endgroup
+}
+\end{verbatim}
+\end{quote}
+and we can use the command as \cmdinvoke{chord}{F\#} or
+\cmdinvoke{chord}{Bb minor}.
+
+Two features of the coding are important:
+\begin{itemize}
+\item \csx{begingroup} in \csx{chord} opens a group that is closed by
+ \csx{endgroup} in \csx{Xchord}; this group limits the change of
+ category codes, which is the \emph{raison d'\^etre} of the whole
+ exercise.
+\item Although |#| is active while \csx{Xchord} is executed, it's
+ \emph{not} active when it's being defined, so that the use of |#1|
+ doesn't require any special attention.
+\end{itemize}
+
+Note that the technique used in such macros as \csx{chord}, here, is
+analogous to that used in such commands as \csx{verb}; and, in just the
+same way as \csx{verb} (see
+% beware breaking long line
+\htmlonly{``}\Qref[question]{\csx{verb} doesn't work in arguments}{Q-verbwithin}\htmlonly{''}),
+\csx{chord} won't work inside the argument of another command (the
+error messages, if they appear at all, will probably be rather odd).
+
+
+\Question[Q-csname]{Defining a macro from an argument}
+
+It's common to want a command to create another command: often one
+wants the new command's name to derive from an argument. \LaTeX{}
+does this all the time: for example, \csx{newenvironment} creates
+start- and end-environment commands whose names are derived from the
+name of the environment command.
+
+The (seemingly) obvious approach:
+\begin{quote}
+\begin{verbatim}
+\def\relay#1#2{\def\#1{#2}}
+\end{verbatim}
+\end{quote}
+doesn't work (the \TeX{} engine interprets it
+as a rather strange redefinition of |\#|). The trick is to use
+\csx{csname}, which is a \TeX{} primitive for generating command names
+from random text, together with \csx{expandafter}. The definition
+above should read:
+\begin{quote}
+\begin{verbatim}
+\def\relay#1#2{%
+ \expandafter\def\csname #1\endcsname{#2}%
+}
+\end{verbatim}
+\end{quote}
+With this definition, \cmdinvoke{relay}{blah}{bleah} is equivalent to
+\csx{def}\cmdinvoke{blah}{bleah}.
+
+Note that the definition of \csx{relay} omits the braces round the
+`command name' in the \csx{newcommand} it executes. This is
+because they're not necessary (in fact they seldom are), and in this
+circumstance they make the macro code slightly more tedious.
+
+The name created need not (of course) be \emph{just} the argument:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\def\newrace#1#2#3{\expandafter\def
+ \csname start#1\endcsname{%
+ #2%
+ }%
+ \expandafter\def
+ \csname finish#1\endcsname{%
+ #3%
+ }%
+}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\def\newrace#1#2#3{%
+ \expandafter\def\csname start#1\endcsname{%
+ #2%
+ }%
+ \expandafter\def\csname finish#1\endcsname{%
+ #3%
+ }%
+}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+With commands
+\begin{quote}
+\begin{verbatim}
+\def\start#1{\csname start#1\endcsname}
+\def\finish#1{\csname finish#1\endcsname}
+\end{verbatim}
+\end{quote}
+these `races' could behave a bit like \LaTeX{} environments.
+
+\Question[Q-cvtlatex]{Transcribing \LaTeX{} command definitions}
+
+At several places in this \acro{FAQ}, questions are answered in terms
+of how to program a \LaTeX{} macro. Sometimes, these macros might
+also help users of \plaintex{} or other packages; this answer
+attempts to provide a rough-and-ready guide to transcribing such macro
+definitions for use in other packages.
+
+The reason \LaTeX{} has commands that replace \csx{def}, is that
+there's a general philosophy within \LaTeX{} that the user should be
+protected from himself: the user has different commands according to
+whether the command to be defined exists (\csx{renewcommand}) or not
+(\csx{newcommand}), and if its status proves not as the user expected,
+an error is reported. A third definition command,
+\csx{providecommand}, only defines if the target is not already
+defined; \LaTeX{} has no direct equivalent of \csx{def}, which ignores
+the present state of the command. The final command of this sort is
+\csx{DeclareRobustCommand}, which creates a command which is ``robust''
+(i.e., will not expand if subjected to \LaTeX{} ``protected
+expansion''); from the \plaintex{} user's point of view,
+\csx{DeclareRobustCommand} should be treated as a non-checking version
+of \csx{newcommand}.
+
+\LaTeX{} commands are, by default, defined \csx{long}; an optional \texttt{*}
+between the \csx{newcommand} and its (other) arguments specifies that
+the command is \emph{not} to be defined \csx{long}. The \texttt{*} is
+detected by a command \csx{@ifstar} which uses \csx{futurelet} to switch
+between two branches, and gobbles the \texttt{*}: \LaTeX{} users are
+encouraged to think of the \texttt{*} as part of the command name.
+
+\LaTeX{}'s checks for unknown command are done by \csx{ifx} comparison
+of a \csx{csname} construction with \csx{relax}; since the command name
+argument is the desired control sequence name, this proves a little
+long-winded. Since \texttt{\#1} is the requisite argument, we have:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\expandafter\ifx
+ \csname
+ \expandafter\@gobble\string#1%
+ \endcsname
+ \relax
+ ...
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\expandafter\ifx
+ \csname\expandafter\@gobble\string#1\endcsname
+ \relax
+ ...
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+(\csx{@gobble} simply throws away its argument).
+
+The arguments of a \LaTeX{} command are specified by two optional
+arguments to the defining command: a count of arguments (0--9: if the
+count is 0, the optional count argument may be omitted), and a default
+value for the first argument, if the defined command's first argument
+is to be optional. So:
+\begin{quote}
+\begin{verbatim}
+\newcommand\foo{...}
+\newcommand\foo[0]{...}
+\newcommand\foo[1]{...#1...}
+\newcommand\foo[2][boo]{...#1...#2...}
+\end{verbatim}
+\end{quote}
+In the last case, \csx{foo} may be called as \cmdinvoke{foo}{goodbye},
+which is equivalent to \cmdinvoke{foo}[boo]{goodbye} (employing the
+default value given for the first argument), or as
+\cmdinvoke{foo}[hello]{goodbye} (with an explicit first argument).
+
+Coding of commands with optional arguments is exemplified by the
+coding of the last \csx{foo} above:
+\begin{quote}
+\begin{verbatim}
+\def\foo{\futurelet\next\@r@foo}
+\def\@r@foo{\ifx\next[%
+ \let\next\@x@foo
+ \else
+ \def\next{\@x@foo[boo]}%
+ \fi
+ \next
+}
+\def\@x@foo[#1]#2{...#1...#2...}
+\end{verbatim}
+\end{quote}
+
+\Question[Q-empty]{Detecting that something is empty}
+
+Suppose you need to know that the argument of your command is empty:
+that is, to distinguish between \cmdinvoke{cmd}{\relax} % \relax doesn't print
+and \cmdinvoke{cmd}{blah}. This is pretty simple:
+\begin{quote}
+\begin{verbatim}
+\def\cmd#1{%
+ \def\tempa{}%
+ \def\tempb{#1}%
+ \ifx\tempa\tempb
+ <empty case>
+ \else
+ <non-empty case>
+ \fi
+}
+\end{verbatim}
+\end{quote}
+The case where you want to ignore an argument that consists of nothing
+but spaces, rather than something completely empty, is more tricky.
+It's solved in the code fragment \Package{ifmtarg}, which defines
+commands \csx{@ifmtarg} and \csx{@ifnotmtarg}, which examine their
+first argument, and select (in opposite directions) their second or
+third argument. The package's code also appears in the \LaTeX{}
+\Class{memoir} class.
+
+\Package{Ifmtarg} makes challenging reading; there's also a discussion of the
+issue in number two of the ``around the bend'' articles by the late
+lamented Mike Downes.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Around the bend series]\CTANref{aro-bend}
+\item[ifmtarg.sty]\CTANref{ifmtarg}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-whatengine]{Am I using \pdftex{}, \xetex{} or \luatex{}?}
+\AliasQuestion{Q-ifpdf}
+
+You often need to know what ``engine'' your macros are running on (the
+engine is the \tex{}-derivative or \tex{}-alike processor that
+typesets your document). The reason that you need to know is that the
+set of functions available in each engine is different. Thus, for
+\tex{} macros to run on any engine, they need to ``know'' what they
+can and cannot do, which depends on the engine in use. Getting the
+right answer is surprisingly tricky (see below for an elaboration of
+one apparently simple test).
+
+There is now a comprehensive set of packages that answer the question
+for you. They all create a \tex{} conditional command:
+\begin{itemize}
+\item \Package{ifpdf} creates a command \csx{ifpdf},
+\item \Package{ifxetex} creates a command \csx{ifxetex} and
+\item \Package{ifluatex} creates a command \csx{ifluatex}.
+\end{itemize}
+These \tex{} commands may be used within the \latex{} conditional
+framework, as (for example):
+\begin{quote}
+ \csx{ifthenelse}\texttt{\obracesymbol{}}\cmdinvoke{boolean}{pdf}\texttt{\cbracesymbol{}}\texttt{\obracesymbol{}}\meta{if pdf}\texttt{\cbracesymbol{}}\texttt{\obracesymbol{}}\meta{if not pdf}\texttt{\cbracesymbol{}}
+\end{quote}
+
+The \Package{ifxetex} package also provides a command
+\csx{RequireXeTeX} which creates an error if the code is not running
+under \xetex{}; while the other packages don't provide such a command,
+it's not really difficult to write one for yourself.
+
+% khalighi's iftex package, too -- \require's for all engines, but i'm
+% not entirely sure of the conditionals, so "for later" if at all
+
+Now for those who want to do the job for themselves: here's a
+discussion of doing the job for \pdftex{} and \csx{ifpdf}~--- the
+eager programmer can regenerate \csx{ifxetex} or \csx{ifluatex} in the
+same fashion. It's not recommended\dots
+
+Suppose you need to test whether your output will be \acro{PDF} or
+\acro{DVI}. The natural thing is to check whether you have access to
+some \PDFTeX{}-only primitive; a good one to try (not least because it
+was present in the very first releases of \PDFTeX{}) is
+\csx{pdfoutput}. So you try
+\begin{quote}
+\begin{verbatim}
+\ifx\pdfoutput\undefined
+ ... % not running PDFTeX
+\else
+ ... % running PDFTeX
+\fi
+\end{verbatim}
+\end{quote}
+Except that neither branch of this conditional is rock-solid. The
+first branch can be misleading, since the ``awkward'' user could have
+written:
+\begin{quote}
+\begin{verbatim}
+\let\pdfoutput\undefined
+\end{verbatim}
+\end{quote}
+so that your test will falsely choose the first alternative. While
+this is a theoretical problem, it is unlikely to be a major one.
+
+More important is the user who loads a package that uses
+\LaTeX{}-style testing for the command name's existence (for example,
+the \LaTeX{} \Package{graphics} package, which is useful even to the
+\plaintex{} user). Such a package may have gone ahead of you, so the
+test may need to be elaborated:
+\begin{quote}
+\begin{verbatim}
+\ifx\pdfoutput\undefined
+ ... % not running PDFTeX
+\else
+ \ifx\pdfoutput\relax
+ ... % not running PDFTeX
+ \else
+ ... % running PDFTeX
+ \fi
+\fi
+\end{verbatim}
+\end{quote}
+If you only want to know whether some \PDFTeX{} extension (such as
+marginal kerning) is present, you can stop at this point: you know as
+much as you need.
+
+However, if you need to know whether you're creating \acro{PDF}
+output, you also need to know about the value of \csx{pdfoutput}:
+\begin{quote}
+\begin{verbatim}
+\ifx\pdfoutput\undefined
+ ... % not running PDFTeX
+\else
+ \ifx\pdfoutput\relax
+ ... % not running PDFTeX
+ \else
+ % running PDFTeX, with...
+ \ifnum\pdfoutput>0
+ ... % PDF output
+ \else
+ ... % DVI output
+ \fi
+ \fi
+\fi
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[ifpdf.sty]Distributed as part Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[ifpdf]
+\item[ifluatex.sty]Distributed as part of Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[ifluatex]
+\item[ifxetex.sty]\CTANref{ifxetex}
+\end{ctanrefs}
+\LastEdit{2012-02-13}
+
+\Question[Q-subverttoks]{Subverting a token register}
+
+A common requirement is to ``subvert'' a token register that other
+macros may use. The requirement arises when you want to add something
+to a system token register (\csx{output} or \csx{every*}), but know
+that other macros use the token register, too. (A common requirement
+is to work on \csx{everypar}, but \LaTeX{} changes \csx{everypar} at
+every touch and turn.)
+
+The following technique, due to David Kastrup, does what you need, and
+allows an independent package to play the exact same game:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\let\mypkg@@everypar\everypar
+\newtoks\mypkg@everypar
+\mypkg@everypar\expandafter{\the\everypar}
+\mypkg@@everypar{\mypkgs@ownstuff\the\mypkg@everypar}
+\def\mypkgs@ownstuff{%
+ <stuff to do at the start of the token register>%
+}
+\let\everypar\mypkg@everypar
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\let\mypkg@@everypar\everypar
+\newtoks\mypkg@everypar
+\mypkg@everypar\expandafter{\the\everypar}
+\mypkg@@everypar{\mypkgs@ownstuff
+ \the\mypkg@everypar}
+\def\mypkgs@ownstuff{%
+ <stuff to do at the start of
+ the token register>%
+}
+\let\everypar\mypkg@everypar
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+As you can see, the package (\Package{mypkg})
+\begin{itemize}
+\item creates an alias for the existing ``system'' \csx{everypar}
+ (which is frozen into any surrounding environment, which will carry
+ on using the original);
+\item creates a token register to subvert \csx{everypar} and
+ initialises it with the current contents of \csx{everypar};
+\item sets the ``old'' \csx{everypar} to execute its own extra code,
+ as well as the contents of its own token register;
+\item defines the macro for the extra code; and
+\item points the token \csx{everypar} at the new token register.
+\end{itemize}
+and away we go.
+
+The form \csx{mypkg@...} is (sort of) blessed for \LaTeX{} package
+internal names, which is why this example uses macros of that form.
+
+\Question[Q-isdef]{Is this command defined?}
+
+Macro sets from the earliest days of \TeX{} programming may be
+observed to test whether commands exist by using
+\begin{quote}
+\csx{ifx} \csx{}\texttt{\emph{command}} \csx{undefined} \meta{stuff} \dots{}
+\end{quote}
+(which of course actually tests that the command \emph{doesn't}
+exist). \LaTeX{} programmers can make use of the internal command
+\begin{quote}
+ \cmdinvoke*{@ifundefined}{cmd name}{action1}{action2}
+\end{quote}
+which executes \texttt{action1} if the command is undefined, and
+\texttt{action2} if it is defined
+(\emph{cmd name} is the command name only, omitting the `|\|' character).
+
+The \csx{@ifundefined} command is based on the sequence
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\expandafter
+ \ifx\csname cmd name\endcsname\relax
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\expandafter \ifx \csname cmd name\endcsname \relax
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+which relies on the way \csx{csname} works: if the command doesn't
+exist, it simply creates it as an alias for \csx{relax}.
+
+So: what is wrong with these techniques?
+
+Using \csx{undefined} blithely assumes that the command is indeed not
+defined. This isn't entirely safe; one could make the name more
+improbable, but that may simply make it more difficult to spot a
+problem when things go wrong. \LaTeX{} programmers who use the
+technique will typically employ \csx{@undefined}, adding a single
+level of obscurity.
+
+The \csx{@ifundefined} mechanism has the unfortunate property of
+polluting the name space: each test that turns out undefined adds a
+name to the set \TeX{} is holding, and often all those ``\csx{relax}''
+names serve no purpose whatever. Even so (sadly) there are places in
+the code of \LaTeX{} where the existence of the \csx{relax} is relied
+upon, after the test, so we can't get away from \csx{@ifundefined}
+altogether.
+
+David Kastrup offers the (rather tricky)
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+{\expandafter}\expandafter\ifx \csname cmd name\endcsname\relax ...
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+{\expandafter}\expandafter
+ \ifx \csname cmd name\endcsname \relax ...
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+which ``creates'' the \csx{relax}-command inside the group of the first
+\csx{expandafter}, therefore forgets it again once the test is done.
+The test is about as good as you can do with macros.
+
+The \Qref*{\eTeX{} system}{Q-etex} system comes to our help here: it
+defines two new primitives:
+\begin{itemize}
+\item \csx{ifdefined}, which tests whether a thing is defined (the
+ negative of comparing with \csx{undefined}, as it were), and
+\item \csx{ifcsname} \texttt{cmd name}\csx{endcsname}, which does the
+ negative of \csx{@ifundefined} without the \csx{relax}-command
+ side-effect.
+\end{itemize}
+So, in an \eTeX{}-based system, the following two conditional clauses do
+the same thing:
+\begin{quote}
+\begin{verbatim}
+\ifdefined\foo
+ \message{\string\foo\space is defined}%
+\else
+ \message{no command \string\foo}%
+\fi
+%
+\ifcsname foo\endcsname
+ \message{\string\foo\space is defined}%
+\else
+ \message{no command \string\foo}%
+\fi
+\end{verbatim}
+\end{quote}
+However, after using the \LaTeX{}
+\cmdinvoke{@ifundefined}{foo}\dots{}, the conditionals will detect the
+command as ``existing'' (since it has been \csx{let} to \csx{relax});
+so it is important not to mix mechanisms for detecting the state of a
+command.
+
+Since most distributions nowadays use \eTeX{} as their base executable
+for most packages, these two primitives may be expected appear widely
+in new macro packages.
+
+\subsection{\LaTeX{} macro tools and techniques}
+
+\Question[Q-plninltx*]{Using Plain or primitive commands in \LaTeX{}}
+
+It's well-known that \LaTeX{} commands tend to be more complex, and to
+run more slowly than, any \plaintex{} (or primitive) command that they
+replace. There is therefore great temptation not to use \LaTeX{}
+commands when macro programming. Nevertheless, the general rule is
+that you should use \LaTeX{} commands, if there are seeming
+equivalents. The exception is when you are sure you know the
+differences between the two commands and you know that you need the
+\plaintex{} version. So, for example, use \csx{mbox} in place of \csx{hbox}
+unless you know that the extras that \LaTeX{} provides in \csx{mbox}
+would cause trouble in your application. Similarly, use
+\csx{newcommand} (or one of its relatives) unless you need one of the
+constructs that cannot be achieved without the use of \csx{def} (or friends).
+
+As a general rule, any \LaTeX{} text command will start a new
+paragraph if necessary; this isn't the case with \plaintex{}
+commands, a fact which has a potential to confuse.
+
+The commands \csx{smallskip}, \csx{medskip} and \csx{bigskip} exist both
+in \plaintex{} and \LaTeX{}, but behave slightly differently: in
+\plaintex{} they terminate the current paragraph, but in \LaTeX{} they
+don't. The command \csx{line} is part of picture mode in \LaTeX{},
+whereas it's defined as ``\csx{hbox}\texttt{ to }\csx{hsize}'' in
+\plaintex{}. (There's no equivalent for users of the \plaintex{} command in
+\LaTeX{}: an equivalent appears as the internal command \csx{@@line}).
+
+Maths setting shows a case where the \LaTeX{} version \emph{is}
+essentially equivalent to the \TeX{} primitive commands: the \LaTeX{}
+\csx{(}\texttt{\ ...\ }\csx{)} does essentially no different to the
+primitive \texttt{\$\ ...\ \$}; except for checking that you're not
+attempting to open a maths environment when you're already in one, or
+attempting to close one when you're not.
+However, \csx{[}\texttt{\ ...\ }\csx{]} has a more significant
+difference from \texttt{\$\$\ ...\ \$\$}: the primitive version, used
+in \LaTeX{}, can miss the effect of the class option \pkgoption{fleqn}.
+
+Font handling is, of course, wildly different in \plaintex{} and
+\LaTeX{}. \plaintex{}'s font loading command
+(\csx{font}\csx{foo=}\meta{fontname}) and its \LaTeX{} equivalent
+(\csx{newfont}) should be avoided wherever possible. They are only
+safe in the most trivial contexts, and are potential sources of great
+confusion in many circumstances. Further discussion of this issue
+may be found in ``\Qref*{What's wrong with \csx{newfont}?}{Q-newfont*}''.
+\LastEdit{2013-09-27}
+
+\Question[Q-atsigns]{\csx{@} and \texttt{@} in macro names}
+
+Macro names containing \texttt{@} are \emph{internal} to \LaTeX{}, and
+without special treatment just don't work in ordinary use. A nice
+example of the problems caused is discussed in % ! beware line break
+\Qref*{\csx{@} in vertical mode}{Q-atvert}''.
+
+The problems users see are caused by copying bits of a class
+(\extension{cls} file) or
+package (\extension{sty} file) into a document, or by including a class or
+package file into a \LaTeX{} document by some means other than
+\csx{documentclass} or \csx{usepackage}. \LaTeX{} defines internal
+commands whose names contain the character \texttt{@} to
+avoid clashes between its internal names and names that we would
+normally use in our documents. In order that these commands may work
+at all, \csx{documentclass} and \csx{usepackage} play around with the
+meaning of \texttt{@}.
+
+If you've included a file some other way (for example, using
+\csx{input}), you can probably solve the problem by using the correct
+command.
+
+If you're using a fragment of a package or class, you may well feel
+confused: books such as the first edition of the % ! line break
+\Qref*{The \LaTeX{} Companion}{Q-latex-books}
+are full of fragments of packages as examples for you to employ.
+The second edition of the \emph{Companion} makes clearer how you
+should use these fragments, and in addition, the code of
+all the examples is now available on \acro{CTAN}.
+To see the technique in practice, look at the example below, from file
+\File{2-2-7.ltx} in the \emph{Companion} examples directory:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\renewcommand\subsection{\@startsection
+ {subsection}{2}{0mm}%name, level, indent
+ {-\baselineskip}% beforeskip
+ {0.5\baselineskip}% afterskip
+ {\normalfont\normalsize\itshape}}% style
+\makeatother
+\end{verbatim}
+\end{quote}
+(That example appears on page 29 of \emph{The \LaTeX{} Companion},
+second edition.)
+
+The alternative is to treat all these fragments as a package proper,
+bundling them up into a \extension{sty} file and including them with
+\csx{usepackage}; this way you hide your \LaTeX{} internal code somewhere
+that \LaTeX{} internal code is expected, which often looks `tidier'.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Examples from the Companion]\CTANref{tlc2}
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-protect]{What's the reason for `protection'?}
+
+Sometimes \LaTeX{} saves data it will reread later. These data are
+often the argument of some command; they are the so-called moving
+arguments. (`Moving' because data are moved around.) Candidates
+are all arguments that may go into table of contents, list of figures,
+\emph{etc}.; namely, data that are written to an auxiliary file and
+read in later. Other places are those data that might appear in head-
+or footlines. Section headings and figure captions are the most
+prominent examples; there's a complete list in Lamport's book
+(see \Qref[question]{\TeX{}-related books}{Q-latex-books}).
+
+What's going on really, behind the scenes? The commands in moving
+arguments are normally expanded to their internal structure during the
+process of saving. Sometimes this expansion results in invalid \TeX{}
+code, which shows either during expansion or when the code is
+processed again. Protecting a command, using
+``\csx{protect}\csx{cmd}'' tells \LaTeX{} to save \csx{cmd} as
+\csx{cmd}, without expanding it at all.
+
+So, what is a `fragile command'?~--- it's a command that expands into
+illegal \TeX{} code during the save process.
+
+What is a `robust command'?~--- it's a command that expands into legal
+\TeX{} code during the save process.
+
+Lamport's book says in its description of every LaTeX command whether
+it is `robust' or `fragile'; it also says that every command with an
+optional argument is fragile. The list isn't reliable, and neither
+is the assertion about optional arguments; the statements may have
+been true in early versions of \LaTeXe{} but are not any longer
+necessarily so:
+\begin{itemize}
+\item Some fragile commands, such as \csx{cite}, have been made robust
+ in later revisions of \LaTeX{}.
+\item Some commands, such as \csx{end} and \csx{nocite}, are fragile
+ even though they have no optional arguments.
+\item The ``user's way'' of creating a command with an optional
+ argument (using \csx{newcommand} or \csx{newcommand*}) now always
+ creates a robust command (though macros without optional arguments
+ may still be fragile if they do things that are themselves fragile).
+\item There is no reason that a package author should not also make
+ robust commands with optional arguments as part of the package.
+\item Some robust commands are redefined by certain packages to be
+ fragile (the \csx{cite} command commonly suffers this treatment).
+\end{itemize}
+Further, simply ``hiding'' a fragile command in another command, has
+no effect on fragility. So, if \csx{fred} is fragile, and you write:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\jim}{\fred}
+\end{verbatim}
+\end{quote}
+then \csx{jim} is fragile too. There is, however, the
+\csx{newcommand}-replacement \csx{DeclareRobustCommand}, which
+\emph{always} creates a robust command (whether or not it has optional
+arguments). The syntax of \csx{DeclareRobustCommand} is substantially
+identical to that of \csx{newcommand}, and if you do the wrapping
+trick above as:
+\begin{quote}
+\begin{verbatim}
+\DeclareRobustCommand{\jim}{\fred}
+\end{verbatim}
+\end{quote}
+then \csx{jim} is robust.
+
+Finally, we have the \Package{makerobust} package, which defines
+\csx{MakeRobustCommand} to convert a command to be robust. With the
+package, the ``wrapping'' above can simply be replaced by:
+\begin{quote}
+\begin{verbatim}
+\MakeRobustCommand\fred
+\end{verbatim}
+\end{quote}
+Whereafter, \csx{fred} is robust. Using the package may be reasonable
+if you have lots of fragile commands that you need to use in moving
+arguments.
+
+In short, the situation is confusing. No-one believes this is
+satisfactory; the \LaTeX{} team have removed the need for
+protection of some things, but the techniques available in
+current \LaTeX{} mean that this is an expensive exercise. It remains
+a long-term aim of the team to remove all need for \csx{protect}ion.
+\begin{ctanrefs}
+\item[makerobust.sty]Distributed as part of Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[makerobust]
+\end{ctanrefs}
+\LastEdit{2011-06-01}
+
+\Question[Q-edef]{\csx{edef} does not work with \csx{protect}}
+
+Robust \LaTeX{} commands are either ``naturally robust''~--- meaning that
+they never need \csx{protect}, or ``self-protected''~--- meaning that
+they have \csx{protect} built in to their definition in some
+way. Self-protected commands, and fragile commands with
+\csx{protect}ion are only robust in a context where the \csx{protect}
+mechanism is properly handled. The body of an \csx{edef} definition
+doesn't handle \csx{protect} properly, since \csx{edef} is a \TeX{}
+primitive rather than a \LaTeX{} command.
+
+This problem is resolved by a \LaTeX{} internal command
+\csx{protected@edef}, which does the job of \csx{edef} while keeping the
+\csx{protect} mechanism working. There's a corresponding
+\csx{protected@xdef} which does the job of \csx{xdef}.
+
+Of course, these commands need to be tended carefully, since they're
+% beware line break on next line
+internal: see \Qref[question]{'@' in control sequence names}{Q-atsigns}.
+
+\Question[Q-ltxcmds]{The definitions of \LaTeX{} commands}
+
+There are several reasons to want to know the definitions of \LaTeX{}
+commands: from the simplest ``idle curiosity'', to the pressing need
+to patch something to make it ``work the way you want it''. None of
+these are \emph{pure} motives, but knowledge and expertise seldom
+arrive through the purest of motives.
+
+Using a \tex{} executable of some sort, the simple answer is to try
+\csx{show}, in a run that is taking commands from the terminal:
+\begin{quote}
+\begin{verbatim}
+*\makeatletter
+*\show\protected@edef
+> \protected@edef=macro:
+->\let \@@protect \protect
+ \let \protect \@unexpandable@protect
+ \afterassignment \restore@protect \edef .
+\end{verbatim}
+\end{quote}
+(I've rearranged the output there, from the rather confused version
+\TeX{} itself produces.)
+
+So, what about \csx{@unexpandable@protect}?:
+\begin{quote}
+\begin{verbatim}
+*\show\@unexpandable@protect
+> \@unexpandable@protect=macro:
+->\noexpand \protect \noexpand .
+\end{verbatim}
+\end{quote}
+and we're starting to see how one part of the \csx{protect}ion
+mechanism works (one can probably fairly safely guess what
+\csx{restore@protect} does).
+
+Many kernel commands are declared robust:
+\begin{quote}
+\begin{verbatim}
+*\show\texttt
+> \texttt=macro:
+->\protect \texttt .
+\end{verbatim}
+\end{quote}
+so that \csx{show} isn't much help. Define a command \csx{pshow} as
+shown below, and simply execute the command to find its definition:
+\begin{quote}
+\begin{verbatim}
+*\def\pshow#1{{\let\protect\show #1}}
+*\pshow\texttt
+> \texttt =\long macro:
+#1->\ifmmode \nfss@text {\ttfamily #1}%
+ \else \hmode@bgroup \text@command {#1}%
+ \ttfamily \check@icl #1\check@icr
+ \expandafter \egroup \fi .
+\end{verbatim}
+\end{quote}
+Note that the command name that is protected is the `base' command,
+with a space appended. This is cryptically visible, in a couple of
+places above. (Again, the output has been sanitised.)
+% Similar provisions are made in the package \Package{show2e} but i
+% don't understand them yet...
+
+The command \ProgName{texdef} (or \ProgName{latexdef}~--- the same
+command with a different name) will do all that for you and return the
+results slightly more tidily than \latex{} itself manages. For
+example:
+\begin{quote}
+\begin{verbatim}
+$ latexdef texttt
+\end{verbatim}
+\end{quote}
+gives:
+\begin{quote}
+\begin{verbatim}
+macro:->\protect \texttt
+
+\texttt :
+#1->\ifmmode \nfss@text {\ttfamily #1}%
+ \else \hmode@bgroup \text@command {#1}%
+ \ttfamily \check@icl #1\check@icr
+ \expandafter \egroup \fi .
+\end{verbatim}
+\end{quote}
+(again, the output has been sanitised~--- but we see that
+\ProgName{latexdef} has useful `intelligence' in it, as it has spotted
+and dealt with the \csx{protect}.)
+
+With the \texttt{-s} switch, \ProgName{latexdef} will give you a
+source location:
+\begin{quote}
+\begin{verbatim}
+$ latexdef -s texttt
+% latex.ltx, line 3736:
+\DeclareTextFontCommand{\texttt}{\ttfamily}
+\end{verbatim}
+\end{quote}
+though one should note that it doesn't give you the detail of the
+actual coding, merely the definition's location.
+
+Environments also surrender their details to \ProgName{latexdef}:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+$ latexdef -E itemize
+
+\itemize:
+macro:->\ifnum \@itemdepth >\thr@@ \@toodeep
+ \else \advance \@itemdepth \@ne
+ \edef \@itemitem {labelitem\romannumeral \the \@itemdepth}%
+ \expandafter \list \csname \@itemitem \endcsname
+ {\def \makelabel ##1{\hss \llap {##1}}}%
+ \fi
+
+\enditemize:
+macro:->\global \advance \@listdepth \m@ne \endtrivlist
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+$ latexdef -E itemize
+
+\itemize:
+macro:->\ifnum \@itemdepth >\thr@@ \@toodeep
+ \else \advance \@itemdepth \@ne
+ \edef \@itemitem {labelitem\romannumeral
+ \the \@itemdepth}%
+ \expandafter \list
+ \csname \@itemitem \endcsname
+ {\def \makelabel ##1{\hss \llap {##1}}}%
+ \fi
+
+\enditemize:
+macro:->\global \advance \@listdepth \m@ne
+ \endtrivlist
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+(Yet again, this is a sanitised version of the macro definition
+output, which appears as a single very wide line for each definition.)
+
+If one has a malleable text editor, the same investigation may be
+conducted by examining the file \File{latex.ltx} (which is usually to
+be found, in a \acro{TDS} system, in directory \path{tex/latex/base}).
+
+In fact, \File{latex.ltx} is the product of a \ProgName{docstrip}
+process on a large number of \Qref*{\extension{dtx} files}{Q-dtx}, and
+you can refer to those instead. The \LaTeX{} distribution includes a file
+\File{source2e.tex}, and most systems retain it, again in
+\path{tex/latex/base}. \File{Source2e.tex} may be processed to
+provide a complete source listing of the \LaTeX{} kernel (in fact the
+process isn't entirely straightforward, but the file produces messages
+advising you what to do). The result is a huge document, with a
+line-number index of control sequences the entire kernel and a
+separate index of changes recorded in each of the files since the
+\LaTeX{} team took over.
+
+The printed kernel is a nice thing to have, but it's unwieldy and sits
+on my shelves, seldom used. One problem is that the comments are
+patchy: the different modules range from well and lucidly documented,
+through modules documented only through an automatic process that
+converted the documentation of the source of \LaTeXo{}, to modules
+that hardly had any useful documentation even in the \LaTeXo{} original.
+
+In fact, each kernel module \extension{dtx} file will process separately
+through \LaTeX{}, so you don't have to work with the whole of
+\File{source2e}. You can easily determine which module defines the
+macro you're interested in: use your ``malleable text editor'' to find
+the definition in \File{latex.ltx}; then search backwards from that
+point for a line that starts % ! line break
+\texttt{\textpercent{}\textpercent{}\textpercent{}\ From File:}~--- that line
+tells you which \extension{dtx} file contains the definition you are interested
+in. Doing this for \csx{protected@edef}, we find:
+\begin{quote}
+\begin{verbatim}
+%%% From File: ltdefns.dtx
+\end{verbatim}
+\end{quote}
+When we come to look at it, \File{ltdefns.dtx} proves to contain
+quite a dissertation on the methods of handling \csx{protect}ion; it
+also contains some automatically-converted \LaTeXo{} documentation.
+
+And of course, the kernel isn't all of \LaTeX{}: your command may be
+defined in one of \LaTeX{}'s class or package files. For example, we
+find a definition of \csx{thebibliography} in \Class{article}, but
+there's no \File{article.dtx}. Some such files are generated from
+parts of the kernel, some from other files in the distribution. You
+find which by looking at the start of the file: in \File{article.cls},
+we find:
+\begin{quote}
+\begin{verbatim}
+%% This is file `article.cls',
+%% generated with the docstrip utility.
+%%
+%% The original source files were:
+%%
+%% classes.dtx (with options: `article')
+\end{verbatim}
+\end{quote}
+so we need to format \File{classes.dtx} to see the definition in
+context.
+
+All these .dtx files are on \acro{CTAN} as part of the main \LaTeX{}
+distribution.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeX{} distribution]\CTANref{latex}
+\item[texdef,\nothtml{\rmfamily aka} latexdef]\CTANref{texdef}
+\end{ctanrefs}
+\LastEdit{2013-09-27}
+
+\Question[Q-oarglikesect]{Optional arguments like \csx{section}}
+
+Optional arguments, in macros defined using \csx{newcommand}, don't
+quite work like the optional argument to \csx{section}. The default
+value of \csx{section}'s optional argument is the value of the
+mandatory argument, but \csx{newcommand} requires that you `know' the
+value of the default beforehand.
+
+The requisite trick is to use a macro in the optional argument:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\newcommand\thing[2][\DefaultOpt]{%
+ \def\DefaultOpt{#2}%
+ optional arg: #1, mandatory arg: #2%
+}
+\begin{document}
+\thing{manda}% #1=#2
+
+\thing[opti]{manda}% #1="opti"
+\end{document}
+\end{verbatim}
+\end{quote}
+\LaTeX{} itself has a trickier (but less readily understandable)
+method, using a macro \csx{@dblarg}; inside \LaTeX{}, the example
+above would have been programmed:
+\begin{quote}
+\begin{verbatim}
+\newcommand\thing{\@dblarg\@thing}
+\newcommand\@thing[2][\@error]{%
+ optional arg: #1, mandatory arg: #2%
+}
+\end{verbatim}
+\end{quote}
+In that code, \csx{@thing} is only ever called with an optional and a
+mandatory argument; if the default from the \csx{newcommand} is
+invoked, a bug in user code has bitten\dots{}
+
+\Question[Q-twooptarg]{More than one optional argument}
+
+If you've already read % ! line break
+``\Qref*[question]{breaking the 9-argument limit}{Q-moren9}''.
+you can probably guess the ``simple'' solution to this problem:
+command relaying.
+
+\LaTeX{} allows commands with a single optional argument thus:
+\begin{quote}
+\begin{verbatim}
+ \newcommand{\blah}[1][Default]{...}
+\end{verbatim}
+\end{quote}
+
+You may legally call such a command either with its optional argument
+present, as
+\cmdinvoke{blah}[nonDefault] or without, as \csx{blah}; in the latter
+case, the code of \csx{blah} will have an argument of |Default|.
+
+To define a command with two optional arguments, we use the relaying
+technique, as follows:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\blah}[1][Default1]{%
+ \def\ArgI{{#1}}%
+ \BlahRelay
+}
+\newcommand\BlahRelay[1][Default2]{%
+ % the first optional argument is now in
+ % \ArgI
+ % the second is in #1
+ ...%
+}
+\end{verbatim}
+\end{quote}
+Of course, \csx{BlahRelay} may have as many mandatory arguments as are
+allowed, after allowance for the one taken up with its own
+optional argument~--- that is, 8.
+
+Variants of \csx{newcommand} (and friends), with names like
+\csx{newcommandtwoopt}, are available in the \Package{twoopt} package.
+However, if you can, it's probably better to learn to write the commands
+yourself, just to see why they're not even a good idea from the
+programming point of view.
+
+A command with two optional arguments strains the limit of what's
+sensible: obviously you can extend the technique to provide as many
+optional arguments as your fevered imagination can summon. However,
+see the comments on the use of the \Package{keyval} package, in
+``\Qref*[question]{breaking the 9-argument limit}{Q-moren9}'',
+which offers an alternative way forward.
+
+If you must, however, consider the \Package{optparams} or
+\Package{xargs} packages. \Package{Optparams}
+provides a \csx{optparams} command that you use as an intermediate in
+defining commands with up to nine optional arguments. The
+documentation shows examples of commands with four optional arguments
+(and this from an author who has his own key-value package!).
+
+The \Package{xargs} package uses a key-value package
+(\Package{xkeyval}) to \emph{define} the layout of the optional
+arguments. Thus
+\begin{quote}
+\begin{verbatim}
+\usepackage{xargs}
+...
+\newcommandx{\foo}[3][1=1, 3=n]{...}
+\end{verbatim}
+\end{quote}
+defines a command \csx{foo} that has an optional first argument
+(default 1), a mandatory second argument, and an optional third
+argument (default n).
+
+An alternative approach is offered by Scott Pakin's
+\ProgName{newcommand} program, which takes a command name and a
+definition of a set of command arguments (in a fairly
+readily-understood language), and emits \AllTeX{} macros which enable
+the command to be defined. The command requires that a
+\ProgName{Python} interpreter (etc.\@) be installed on your computer.
+\begin{ctanrefs}
+\item[newcommand.py]\CTANref{newcommand}
+\item[optparams.sty]Distributed as part of \CTANref{sauerj}[optparams]
+\item[twoopt.sty]Distributed as part of \CTANref{oberdiek}[twoopt]
+\item[xargs.sty]\CTANref{xargs}
+\item[xkeyval.sty]\CTANref{xkeyval}
+\end{ctanrefs}
+
+\Question[Q-cmdstar]{Commands defined with * options}
+
+\LaTeX{} commands commonly have ``versions'' defined with an asterisk
+tagged onto their name: for example \csx{newcommand} and
+\csx{newcommand*} (the former defines a \csx{long} version of the
+command).
+
+The simple-minded way for a user to write such a command involves use
+of the \Package{ifthen} package:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand{\mycommand}[1]{\ifthenelse{\equal{#1}{*}}%
+ {\mycommandStar}%
+ {\mycommandNoStar{#1}}%
+}
+\newcommand{\mycommandStar}{starred version}
+\newcommand{\mycommandNoStar}[1]{normal version}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand{\mycommand}[1]{%
+ \ifthenelse{\equal{#1}{*}}%
+ {\mycommandStar}%
+ {\mycommandNoStar{#1}}%
+}
+\newcommand{\mycommandStar}%
+ {starred version}
+\newcommand{\mycommandNoStar}[1]%
+ {normal version}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+This does the trick, for sufficiently simple commands, but it has
+various tiresome failure modes, and it requires \csx{mycommandnostar}
+to take an argument.
+
+The \LaTeX{} kernel does a lot of this, and has its own command,
+\csx{@ifstar} (which needs `internal command protection', cf.
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\makeatletter
+\newcommand{\mycommand}{%
+ \@ifstar
+ \mycommandStar%
+ \mycommandNoStar%
+\makeatother
+}
+\newcommand{\mycommandStar}{starred version}
+\newcommand{\mycommandNoStar}{normal version}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\makeatletter
+\newcommand{\mycommand}{\@ifstar
+ \mycommandStar%
+ \mycommandNoStar%
+}
+\makeatother
+\newcommand{\mycommandStar}{starred version}
+\newcommand{\mycommandNoStar}{normal version}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+(Note that arguments to \csx{mycommandStar} and \csx{mycommandNoStar}
+are independent~--- either can have their own arguments, unconstrained
+by the technique we're using, unlike the trick described above.)
+The \csx{@ifstar} trick is all very well, is fast and efficient, but
+it requires that the definition be % ! line break
+\Qref*{\csx{makeatletter} protected}{Q-atsigns}.
+
+A pleasing alternative is the \Package{suffix} package. This elegant
+piece of code allows you to define variants of your commands:
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand\mycommand{normal version}
+\WithSuffix\newcommand\mycommand*%
+ {starred version}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\newcommand\mycommand{normal version}
+\WithSuffix\newcommand\mycommand*{starred version}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+The package needs \Qref*{\elatex{}}{Q-etex}, but any new enough
+distribution defines \LaTeX{} as \elatex{} by default. Command
+arguments may be specified in the normal way, in both command
+definitions (after the ``\texttt{*}'' in the \csx{WithSuffix}
+version). You can also use the \TeX{} primitive commands, creating a
+definition like:
+\begin{quote}
+\begin{verbatim}
+\WithSuffix\gdef\mycommand*{starred version}
+\end{verbatim}
+\end{quote}
+
+For those of an adventurous disposition, a further option is to use
+the \Package{xparse} package from the \Package{l3packages}
+distribution. The package defines a bunch of commands (such as
+\csx{NewDocumentCommand}) which are somewhat analagous to
+\csx{newcommand} and the like, in \latexe{}. The big difference is
+the specification of command arguments; for each argument, you have a
+set of choices in the command specification. So, to create a
+*-command (in \latexe{} style), one might write:
+\begin{quote}
+\begin{verbatim}
+\NewDocumentCommand \foo { s m } {%
+ % #1 is the star indicator
+ % #2 is a mandatory argument
+ ...
+}
+\end{verbatim}
+\end{quote}
+The ``star indicator'' (\texttt{s}) argument appears as \texttt{\#1}
+and will take values \csx{BooleanTrue} (if there was a star) or
+\csx{BooleanFalse} (otherwise); the other (\texttt{m}) argument is a
+normal \tex{}-style mandatory argument, and appears as \texttt{\#2}.
+
+While \Package{xparse} provides pleasing command argument
+specifications, it \emph{is} part of the % ! line break
+\Qref*{\latex{}~3 experimental harness}{Q-LaTeX3}.
+Simply loading the package to provide \csx{DeclareDocumentCommand}
+``pulls in'' all of the \latex{}3 kernel (a large bunch of packages)
+via the \Package{expl3} package.
+\begin{ctanrefs}
+\item[ifthen.sty]Part of the \LaTeX{} distribution
+\item[suffix.sty]Distributed as part of \CTANref{bigfoot}[suffix]
+\item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse]
+\item[expl3.sty]Distributed as part of \CTANref{l3kernel}[expl3]
+\end{ctanrefs}
+\LastEdit{2014-04-04}
+
+\nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax}
+\Question[Q-ltxabbrv]{\LaTeX{} internal ``abbreviations'', etc.}
+
+In the deeps of time, when \TeX{} first happened, computers had
+extremely limited memory, and were (by today's standards) painfully
+slow. When \LaTeX{} came along, things weren't much better, and even
+when \LaTeXe{} appeared, there was a strong imperative to save memory
+space (and to a lesser extent) \acro{CPU} time.
+
+From the very earliest days, Knuth used shortcut macros to speed
+things up. \LaTeX{}, over the years, has extended Knuth's list by a
+substantial amount. An interesting feature of the ``abbreviations'' is
+that on paper, they may look longer than the thing they stand for;
+however, to \AllTeX{} they \emph{feel} smaller\dots{}
+
+The table at the end of this answer lists the commonest of these
+``abbreviations''. It is not complete; as always, if the table
+doesn't help, try the \LaTeX{} source. The table lists each
+abbreviation's \emph{name} and its \emph{value}, which provide most of
+what a user needs to know. The table also lists the abbreviation's
+\emph{type}, which is a trickier concept: if you need to know, the
+only real confusion is that the abbreviations labelled `defn' are
+defined using an \csx{\emph{xxxx}def} command.
+
+\begin{tabular}{lll}
+Name \tbamp Type \tbamp Value \tbeol
+\tbhline
+\csx{m@ne} \tbamp count \tbamp \ensuremath{-1} \tbeol
+\csx{p@} \tbamp dimen \tbamp 1pt \tbeol
+\csx{z@} \tbamp dimen \tbamp 0pt \tbeol
+\csx{z@skip} \tbamp skip \tbamp 0pt plus 0pt minus 0pt \tbeol
+\tbhline
+\csx{@ne} \tbamp defn \tbamp 1 \tbeol
+\csx{tw@} \tbamp defn \tbamp 2\tbeol
+\csx{thr@@} \tbamp defn \tbamp 3 \tbeol
+\csx{sixt@@n} \tbamp defn \tbamp 16 \tbeol
+\csx{@cclv} \tbamp defn \tbamp 255 \tbeol
+\csx{@cclvi} \tbamp defn \tbamp 256 \tbeol
+\csx{@m} \tbamp defn \tbamp 1000 \tbeol
+\csx{@M} \tbamp defn \tbamp 10000 \tbeol
+\csx{@MM} \tbamp defn \tbamp 20000 \tbeol
+\tbhline
+\csx{@vpt} \tbamp macro \tbamp 5 \tbeol
+\csx{@vipt} \tbamp macro \tbamp 6 \tbeol
+\csx{@viipt} \tbamp macro \tbamp 7 \tbeol
+\csx{@viiipt} \tbamp macro \tbamp 8 \tbeol
+\csx{@ixpt} \tbamp macro \tbamp 9 \tbeol
+\csx{@xpt} \tbamp macro \tbamp 10 \tbeol
+\csx{@xipt} \tbamp macro \tbamp 10.95 \tbeol
+\csx{@xiipt} \tbamp macro \tbamp 12 \tbeol
+\csx{@xivpt} \tbamp macro \tbamp 14.4 \tbeol
+\csx{@xviipt} \tbamp macro \tbamp 17.28 \tbeol
+\csx{@xxpt} \tbamp macro \tbamp 20.74 \tbeol
+\csx{@xxvpt} \tbamp macro \tbamp 24.88 \tbeol
+\tbhline
+\csx{@plus} \tbamp macro \tbamp ``\texttt{plus}'' \tbeol
+\csx{@minus} \tbamp macro \tbamp ``\texttt{minus}'' \tbeol
+%\csx{hb@xt@} \tbamp macro \tbamp ``\csx{hbox} \texttt{to}''
+\end{tabular}
+
+\Question[Q-ltxhash]{Defining \LaTeX{} commands within other commands}
+
+\LaTeX{} command definition is significantly different from the \TeX{}
+primitive form discussed in an % ! line break
+\Qref*[\htmlonly]{earlier question}{Q-hash} about definitions within
+macros.
+
+In most ways, the \LaTeX{} situation is simpler (at least in part
+because it imposes more restrictions on the user); however, defining a
+command within a command still requires some care.
+
+The earlier question said you have to double the |#| signs in command
+definitions: in fact, the same rule holds, except that \LaTeX{}
+already takes care of some of the issues, by generating argument lists
+for you.
+
+The basic problem is that:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\abc}[1]{joy, oh #1!%
+ \newcommand{\ghi}[1]{gloom, oh #1!}%
+}
+\end{verbatim}
+\end{quote}
+followed by a call:
+\begin{quote}
+\begin{verbatim}
+\cmdinvoke{abc}{joy}
+\end{verbatim}
+\end{quote}
+typesets ``joy, oh joy!'', but defines a command \csx{ghi} that takes
+one parameter, which it ignores; \cmdinvoke{ghi}{gloom} will expand to
+``gloom, oh joy!'', which is presumably not what was expected.
+
+And (as you will probably guess, if you've read the earlier question)
+the definition:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\abc}[1]{joy, oh #1!%
+ \newcommand{\ghi}[1]{gloom, oh ##1!}%
+}
+\end{verbatim}
+\end{quote}
+does what is required, and \cmdinvoke{ghi}{gloom} will expand to
+``gloom, oh gloom!'', whatever the argument to \csx{abc}.
+
+The doubling is needed whether or not the enclosing command has an
+argument, so:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\abc}{joy, oh joy!%
+ \newcommand{\ghi}[1]{gloom, oh ##1!}%
+}
+\end{verbatim}
+\end{quote}
+is needed to produce a replica of the \csx{ghi} we defined earlier.
+
+\Question[Q-printvar]{How to print contents of variables?}
+\keywords{typeout, print variables, showthe}
+
+It is often useful to print out the values of variables in the log
+file or on the terminal. Three possible ways to print out the
+contents of \csx{textheight} variable are:
+\begin{enumerate}
+\item \csx{showthe}\csx{textheight}
+\item \cmdinvoke{message}{The text height is \csx{the}\csx{textheight}}
+\item \cmdinvoke{typeout}{The text height is \csx{the}\csx{textheight}}
+\end{enumerate}
+These techniques use the \TeX{} primitives \csx{the} (which provides
+the value of a variable), \csx{showthe} (print a variable to the
+terminal and the log, on a line of its own), and \csx{message}, which
+interpolates something into the log. The command \csx{typeout} is
+\LaTeX{}'s general message output mechanism.
+
+In each case, the variable's value is printed as a number of points.
+
+To typeset the value of \csx{textheight}, just
+\csx{the}\csx{textheight} is enough, but a more flexible alternative is
+to use the \Package{printlen} package. \Package{Printlen} allows you
+to choose the units in which you print a variable; this is useful,
+given that the most ordinary people don't think in points
+(particularly Knuth's points, of which there are 72.27 to the inch).
+
+So, using \Package{printlen}, we could say:
+\begin{quote}
+\begin{verbatim}
+\newlength{\foo}
+\setlength{\foo}{12pt}
+\verb|\foo| is \printlength{\foo}
+\end{verbatim}
+\end{quote}
+and get:
+\begin{quote}
+\csx{foo} is 12pt
+\end{quote}
+while, if we say:
+\begin{quote}
+\begin{verbatim}
+\newlength{\foo}
+\setlength{\foo}{12pt}
+\uselengthunit{mm}
+\verb|foo| is \printlength{\foo}
+\end{verbatim}
+\end{quote}
+we get:
+\begin{quote}
+\csx{foo} is 4.21747mm
+\end{quote}
+\begin{ctanrefs}
+\item[printlen.sty]\CTANref{printlen}
+\end{ctanrefs}
+\LastEdit{2012-03-16}
+
+\Question[Q-labelcount]{Using labels as counter values}
+
+Labels are tempting sources of `numbers'~--- their most common use,
+after all, is simply to typeset a number. However, their seeming
+simplicity is deceptive; the packages \Package{babel} and
+\Package{hyperref}, at least, fiddle with the definition of
+\csx{ref} and \csx{pageref} in ways that make
+\begin{quote}
+\begin{verbatim}
+\setcounter{foo}{\ref{bar}}
+\end{verbatim}
+\end{quote}
+(etc.\@) not work; thus the technique may not be relied upon.
+
+The solution is to use the \Package{refcount} package (incidentally,
+by the author of \Package{hyperref}). The package provides four
+commands, all similar to:
+\begin{quote}
+\begin{verbatim}
+\usepackage{refcount}
+...
+\label{bar}
+...
+\setcounterref{foo}{bar}
+\end{verbatim}
+\end{quote}
+(the other three are \csx{addtocounterref}, \csx{setcounterpageref}
+and \csx{addtocounterpageref}).
+
+The package also provides a command
+\cmdinvoke*{getrefnumber}{label-name} that may be used where a
+`number' value is needed. For example:
+\begin{quote}
+\begin{verbatim}
+... \footnote{foo bar ...\label{foofoot}}
+...
+\footnotemark[\getrefnumber{foofoot}]
+\end{verbatim}
+\end{quote}
+which gives you a second footnote mark reference the the footnote.
+(There is also a command \csx{getpagerefnumber}, of course).
+
+The commands could be used by one determined not to use
+\Package{changepage} to determine whether % ! line break
+\Qref*{the current page is odd}{Q-oddpage}, but it's probably no more
+trouble to use the fully-developed tool in this case.
+\begin{ctanrefs}
+\item[refount.sty]Distributed as part of \CTANref{oberdiek}
+\end{ctanrefs}
+\LastEdit*{2011-09-08}
+
+\subsection{\LaTeX{} macro programming}
+
+\Question[Q-fixnam]{How to change \LaTeX{}'s ``fixed names''}
+
+\LaTeX{} document classes define several typographic operations that
+need `canned text' (text not supplied by the user). In the earliest
+days of \LaTeXo{} these bits of text were built in to the body of
+\LaTeX{}'s macros and were rather difficult to change, but ``fixed
+name'' macros were introduced for the benefit of those wishing to use
+\LaTeX{} in languages other than English.
+For example, the special section produced by the \csx{tableofcontents}
+command is always called \csx{contentsname} (or rather, what
+\csx{contentsname} is defined to mean).
+Changing the canned text is now one of the easiest customisations a
+user can do to \LaTeX{}.
+
+The canned text macros are all of the form
+\csx{\meta{thing}name}, and changing them is simplicity
+itself. Put:
+\begin{quote}
+\cmdinvoke{renewcommand}{\csx{\meta{thing}name}}{Res minor}
+\end{quote}
+in the preamble of your document, and the job is done.
+(However, beware of the \Package{babel} package, which requires you to
+use a different mechanism: be sure to check
+% beware line wrap
+\Qref[question]{changing \Package{babel} names}{Q-latexwords} if
+you're using it.)
+
+The names that are defined in the standard \LaTeX{} classes (and the
+\Package{makeidx} package) are listed
+below. Some of the names are only defined in a subset of the classes
+(and the \Class{letter} class has a set of names all of its own);
+the list shows the specialisation of each name, where appropriate.
+
+\nothtml{\noindent}\begin{tabular}{@{}ll}
+\csx{abstractname} \tbamp Abstract\tbeol
+\csx{alsoname} \tbamp see also (\Package{makeidx} package)\tbeol
+\csx{appendixname} \tbamp Appendix\tbeol
+\csx{bibname} \tbamp Bibliography (\Class{report},\Class{book})\tbeol
+\csx{ccname} \tbamp cc (\Class{letter})\tbeol
+\csx{chaptername} \tbamp Chapter (\Class{report},\Class{book})\tbeol
+\csx{contentsname} \tbamp Contents\tbeol
+\csx{enclname} \tbamp encl (\Class{letter})\tbeol
+\csx{figurename} \tbamp Figure (for captions)\tbeol
+\csx{headtoname} \tbamp To (\Class{letter})\tbeol
+\csx{indexname} \tbamp Index\tbeol
+\csx{listfigurename} \tbamp List of Figures\tbeol
+\csx{listtablename} \tbamp List of Tables\tbeol
+\csx{pagename} \tbamp Page (\Class{letter})\tbeol
+\csx{partname} \tbamp Part\tbeol
+\csx{refname} \tbamp References (\Class{article})\tbeol
+\csx{seename} \tbamp see (\Package{makeidx} package)\tbeol
+\csx{tablename} \tbamp Table (for caption)
+\end{tabular}
+
+\Question[Q-latexwords]{Changing the words \Package{babel} uses}
+
+\LaTeX{} uses symbolic names for many of the automatically-generated
+text it produces (special-purpose section headings, captions, etc.).
+As noted in \Qref[question]{``\LaTeX{} fixed names''}{Q-fixnam} (which
+includes a list of the names themselves),
+this enables the user to change the
+names used by the standard classes, which is particularly useful if
+the document is being prepared in some language other than \LaTeX{}'s
+default English. So, for example, a Danish author may wish that her
+table of contents was called ``Indholdsfortegnelse'', and so
+would expect to place a command
+\begin{verbatim}
+\renewcommand{\contentsname}%
+ {Indholdsfortegnelse}
+\end{verbatim}
+in the preamble of her document.
+
+However, it's natural for a user of a non-English language to use
+\Package{babel}, because it offers many conveniences and typesetting
+niceties for those preparing documents in those languages. In
+particular, when \Package{babel} is selecting a new language, it
+ensures that \LaTeX{}'s symbolic names are translated appropriately
+for the language in question. Unfortunately, \Package{babel}'s choice
+of names isn't always to everyone's choice, and there is still a need
+for a mechanism to replace the `standard' names.
+
+Whenever a new language is selected, \Package{babel} resets all the
+names to the settings for that language. In particular,
+\Package{babel} selects the document's main language when
+\cmdinvoke{begin}{document} is executed, which immediately destroys
+any changes to these symbolic names made in the prologue of a document
+that uses \Package{babel}.
+
+Therefore, babel defines a command to enable users to change the
+definitions of the symbolic names, on a per-language basis:
+\csx{addto}\csx{captions}\texttt{\meta{language}} is the thing
+(\texttt{\meta{language}} being the language option you gave to
+\Package{babel} in the first place). For example:
+\begin{verbatim}
+\addto\captionsdanish{%
+ \renewcommand{\contentsname}%
+ {Indholdsfortegnelse}%
+}
+\end{verbatim}
+
+\Question[Q-running-nos]{Running equation, figure and table numbering}
+
+Many \LaTeX{} classes (including the standard \Class{book} class)
+number things per chapter; so figures in chapter 1 are numbered 1.1,
+1.2, and so on. Sometimes this is not appropriate for the user's
+needs.
+
+Short of rewriting the whole class, one may use the \Package{chngcntr}
+package, which provides commands \csx{counterwithin} (which
+establishes this nested numbering relationship) and
+\csx{counterwithout} (which undoes it).
+
+So if you have figures numbered by chapter as 1.1, 1.2, 2.1, \dots{},
+the command
+\begin{quote}
+\begin{verbatim}
+\counterwithout{figure}{chapter}
+\end{verbatim}
+\end{quote}
+will convert them to figures 1, 2, 3, \dots{}. (Note that the command
+has also removed the chapter number from the counter's definition.)
+
+More elaborate use could change things numbered per section to things
+numbered per chapter:
+\begin{quote}
+\begin{verbatim}
+\counterwithout{equation}{section}
+\counterwithin{equation}{chapter}
+\end{verbatim}
+\end{quote}
+(assuming there was a class that did such a thing in the first place...)
+
+The \Package{chngcntr} approach doesn't involve much programming, and
+the enthusiastic \LaTeX{} programmer might choose to try the technique
+that we had to use before the advent of \Package{chngcntr}. Each of
+the packages \Package{removefr} and \Package{remreset} defines a
+\csx{@removefromreset} command, and having included the package one
+writes something like:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\@removefromreset{figure}{chapter}
+\makeatother
+\end{verbatim}
+\end{quote}
+and the automatic renumbering stops. You may then need to redefine the
+way in which the figure number (in this case) is printed:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\renewcommand{\thefigure}{\@arabic\c@figure}
+\makeatother
+\end{verbatim}
+\end{quote}
+(remember to do the whole job, for every counter you want to
+manipulate, within \csx{makeatletter} \dots{}\@ \csx{makeatother}).
+
+This technique, too, may be used to change where in a multilevel
+structure a counter is reset. Suppose your class numbers figures as
+\meta{chapter}.\meta{section}.\meta{figure}, and you want figures
+numbered per chapter, try:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\makeatletter
+\@removefromreset{figure}{section}
+\@addtoreset{figure}{chapter}
+\renewcommand{\thefigure}{\thechapter.\@arabic\c@figure}
+\makeatother
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\makeatletter
+\@removefromreset{figure}{section}
+\@addtoreset{figure}{chapter}
+\renewcommand{\thefigure}%
+ {\thechapter.\@arabic\c@figure}
+\makeatother
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+(the command \csx{@addtoreset} is a part of \LaTeX{} itself).
+\begin{ctanrefs}
+\item[chngcntr.sty]\CTANref{chngcntr}
+\item[memoir.cls]\CTANref{memoir}
+\item[removefr.tex]\CTANref{removefr} (note, this is constructed as a
+ ``fragment'' for use within other packages: load by
+ \cmdinvoke{input}{removefr})
+\item[remreset.sty]Distributed as part of \CTANref{carlisle}[remreset]
+\end{ctanrefs}
+
+\Question[Q-labelctr]{Making labels from a counter}
+
+Suppose we have a \LaTeX{} counter, which we've defined with
+\cmdinvoke{newcounter}{foo}. We can increment the value of the counter
+by \cmdinvoke{addtocounter}{foo}{1}, but that's pretty clunky for an
+operation that happens so often \dots{}~so there's a command
+\cmdinvoke{stepcounter}{foo} that does this special case of
+increasing-by-one.
+
+There's an internal \LaTeX{} variable, the ``current label'', that
+remembers the last `labellable' thing that \LaTeX{} has processed.
+You could (if you were to insist) set that value by the relevant
+\TeX{} command (having taken the necessary precautions to ensure that
+the internal command worked)~--- but it's not necessary. If, instead
+of either of the stepping methods above, you say
+\cmdinvoke{refstepcounter}{foo}, the internal variable is set to the
+new value, and (until something else comes along), \csx{label} will
+refer to the counter.
+
+\Question[Q-oddpage]{Finding if you're on an odd or an even page}
+
+\Qref[Question]{Another question}{Q-marginparside} discusses the issue
+of getting \csx{marginpar} commands to put their output in the correct
+margin of two-sided documents. This is an example of the general
+problem of knowing where a particular bit of text lies: the output
+routine is asynchronous, and \AllTeX{} will usually process quite a
+bit of the ``next'' page before deciding to output any page. As a
+result, the |page| counter (known internally in \LaTeX{} as
+\csx{c@page}) is normally only reliable when you're actually \emph{in}
+the output routine.
+
+The solution is to use some version of the \csx{label} mechanism to
+determine which side of the page you're on; the value of the page
+counter that appears in a \csx{pageref} command has been inserted in
+the course of the output routine, and is therefore safe.
+
+However, \csx{pageref} itself isn't reliable: one might hope that
+\begin{quote}
+\begin{verbatim}
+\ifthenelse{\isodd{\pageref{foo}}}{odd}{even}
+\end{verbatim}
+\end{quote}
+would do the necessary, but both the \Package{babel} and
+\Package{hyperref} packages have been known to interfere with the
+output of \csx{pageref}; be careful!
+
+The \Package{changepage} package needs to provide this functionality
+for its own use, and therefore provides a command \csx{checkoddpage};
+this sets a private-use `label', and the page reference part of that
+label is then examined (in a \Package{hyperref}-safe way) to set a
+conditional \csx{ifoddpage} true if the command was issued on an odd
+page. (The \Class{memoir} class has the same command.) \latex{}
+users who are unfamiliar with \tex{}'s \csx{if...} commands may use
+the \Package{ifthen} package:
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{ifthen,changepage}
+...
+\checkoddpage
+\ifthenelse{\boolean{oddpage}}{<odd page stuff>}{<even page stuff>}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{ifthen,changepage}
+...
+\checkoddpage
+\ifthenelse{\boolean{oddpage}}%
+ {<odd page stuff>}%
+ {<even page stuff>}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+
+Of course, the `label' contributes to \LaTeX{}'s ``Rerun to get
+cross-references right'' error messages\dots{}
+
+The Koma-Script classes have an \environment{addmargin*} environment
+that also provides the sorts of facilities that the \Package{changepage}
+offers. Koma-Script's supporting command:
+\begin{quote}
+\cmdinvoke{ifthispageodd}{<true>}{<false>}
+\end{quote}
+executes different things depending on the page number.
+
+The package \Package{ifoddpage} is designed to provide the same
+facility; crucially, it can behave ``sensibly'' even if you are
+typesetting for one-side printing only; like the \Package{changepage}
+it uses a `check' command \csx{checkoddpage}. The conditional `side'
+flags are set using (Plain) \TeX{} conditionals; they are defined
+locally, so that you can minimise their use of \tex{} workspace~---
+see the package documentation for the somewhat tricky sequence
+involved. In addition the package provides a command
+\csx{ifoddpageoroneside}, which is true on odd pages of a two-side
+document, or on all pages of a one-side document. Usage is:
+\begin{quote}
+\begin{verbatim}
+\checkoddpage
+\ifoddpage
+ odd-side text
+\else
+ even-side text
+\fi
+\end{verbatim}
+\end{quote}
+The author's recommended usage (trickily) includes the whole operation
+in a box; this has the advantage that your test will always work, but
+the usual disadvantage that boxes may not split. In common uses, the
+whole work will be done inside a box (as, for example, in the case of
+a float), so the elaborate work proposed by the author is not
+necessary.
+\begin{ctanrefs}
+\item[changepage.sty]\CTANref{changepage}
+\item[ifoddpage.sty]\CTANref{ifoddpage}
+\item[ifthen.sty]Part of the \latex{} distribution: \CTANref{latex}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-labelformat]{How to change the format of labels}
+
+By default, when a label is created, it takes on the appearance of the
+counter labelled, so the label appears as
+\csx{the}\texttt{\meta{counter}}~--- what would be used if you
+asked to typeset the counter in your text. This isn't always what you
+need: for example, if you have nested enumerated lists with the outer
+numbered and the inner labelled with letters, one might expect to want
+to refer to items in the inner list as ``2(c)''. (Remember, you can
+\nothtml{change the structure of list items~--- }%
+\Qref{change the structure of list items}{Q-enumerate}.)
+The change is of course
+possible by explicit labelling of the parent and using that label to
+construct the typeset result~--- something like
+\begin{quote}
+\begin{verbatim}
+\ref{parent-item}(\ref{child-item})
+\end{verbatim}
+\end{quote}
+which would be both tedious and error-prone. What's more, it would be
+undesirable, since you would be constructing a visual representation
+which is inflexible (you couldn't change all the references to elements
+of a list at one fell swoop).
+
+\LaTeX{} in fact has a label-formatting command built into every label
+definition; by default it's null, but it's available for the user to
+program. For any label \meta{counter} there's a \LaTeX{} internal
+command \csx{p@}\meta{\texttt{counter}}; for example, a label definition
+on an inner list item is supposedly done using the command
+\cmdinvoke{p@enumii}{\csx{theenumii}}. Unfortunately, the internal
+workings of this aren't quite right, and you need to patch the
+\csx{refstepcounter} command:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\renewcommand*\refstepcounter[1]{%
+ \stepcounter{#1}%
+ \protected@edef\@currentlabel{%
+ \csname p@#1\expandafter\endcsname
+ \csname the#1\endcsname
+ }%
+}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\renewcommand*\refstepcounter[1]{\stepcounter{#1}%
+ \protected@edef\@currentlabel{%
+ \csname p@#1\expandafter\endcsname
+ \csname the#1\endcsname
+ }%
+}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+With the patch in place you can now, for example, change the labels on
+all inner lists by adding the following code in your preamble:
+\begin{quote}
+\begin{verbatim}
+\makeatletter
+\renewcommand{\p@enumii}[1]{\theenumi(#1)}
+\makeatother
+\end{verbatim}
+\end{quote}
+This would make the labels for second-level enumerated lists appear as
+``1(a)'' (and so on). The analogous change works for any counter that
+gets used in a \csx{label} command.
+
+In fact, the \Package{fncylab} package does all the above (including
+the patch to \LaTeX{} itself). With the package, the code above is
+(actually quite efficiently) rendered by the command:
+\begin{quote}
+\begin{verbatim}
+\labelformat{enumii}{\theenumi(#1)}
+\end{verbatim}
+\end{quote}
+In fact, the above example, which we can do in several different ways,
+has been rendered obsolete by the appearance of the \Package{enumitem}
+package, which is discussed in the answer about % ! line break
+\Qref*{decorating enumeration lists}{Q-enumerate}.
+\begin{ctanrefs}
+\item[enumitem.sty]\CTANref{enumitem}
+\item[fncylab.sty]\CTANref{fncylab}
+\end{ctanrefs}
+
+\Question[Q-seccntfmt]{Adjusting the presentation of section numbers}
+
+The general issues of adjusting the appearance of section headings are
+pretty complex, and are covered in % beware line breaks (2 lines)
+\latexhtml{question}{the question on}
+\Qref[\htmlonly]{the style of section headings}{Q-secthead}.
+
+However, people regularly want merely to change the way the section
+number appears in the heading, and some such people don't mind writing
+out a few macros. This answer is for \emph{them}.
+
+The section number is typeset using the
+\begin{dviversion}
+ \LaTeX{} internal
+\end{dviversion}
+\begin{hyperversion}
+ \Qref{\LaTeX{} internal}{Q-atsigns}
+\end{hyperversion}
+\csx{@seccntformat} command, which is given the ``name'' (section,
+subsection, \dots{}) of the heading, as argument. Ordinarily,
+\csx{@seccntformat}
+merely outputs the section number, and then a \csx{quad} of space:
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\@seccntformat}[1]{%
+ \csname the#1\endcsname\quad
+}
+\end{verbatim}
+\end{quote}
+Suppose you want to put a stop after every section (subsection,
+subsubsection, \dots{}) number, a trivial change may be implemented by
+simple modification of the command:
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\@seccntformat}[1]{%
+ \csname the#1\endcsname.\quad
+}
+\end{verbatim}
+\end{quote}
+However, many people want to modify section numbers, but not
+subsection numbers, or any of the others. To do this, one must make
+\csx{@seccntformat} switch according to its argument. The following
+technique for doing the job is slightly wasteful, but is efficient
+enough for a relatively rare operation:
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\@seccntformat}[1]{%
+ \csname the#1\endcsname
+ \csname adddot@#1\endcsname\quad
+}
+\end{verbatim}
+\end{quote}
+which uses a second-level command to provide the dot, if it has been
+defined; otherwise it merely appends \csx{relax} (which does nothing
+in this context). The definition of the second-level command (the
+version for the \texttt{section}, here) specifies what to put after a
+section number, but it could be used to put anything after it:
+\begin{quote}
+\begin{verbatim}
+\newcommand*{\adddot@section}{.}
+\end{verbatim}
+\end{quote}
+Note that all the command definitions above are dealing in
+\Qref*{\LaTeX{} internal commands}{Q-atsigns}, so the above
+code should be in a package file, for preference.
+
+The \Class{Koma-script} classes have different commands for specifying
+changes to section number presentation: \csx{partformat},
+\csx{chapterformat} and \csx{othersectionlevelsformat}, but otherwise
+their facilities are similar to those of ``raw'' \LaTeX{}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\end{ctanrefs}
+
+\Question[Q-spaftend]{There's a space added after my environment}
+
+You've written your own environment \environment{env}, and it works
+except that a space appears at the start of the first line of typeset
+text after \cmdinvoke{end}{env}. This doesn't happen with similar
+\LaTeX{}-supplied environments.
+
+You could impose the restriction that your users always put a
+``\texttt{\textpercent{}}'' sign after the environment~\dots{}\nothtml{\@} but
+\LaTeX{} environments don't require that, either.
+
+The \LaTeX{} environments' ``secret'' is an internal flag which causes
+the unwanted spaces to be ignored. Fortunately, you don't have to use
+the internal form: since 1996, \LaTeX{} has had a user command
+\csx{ignorespacesafterend}, which sets the internal flag.
+
+\Question[Q-labundef]{Finding if a label is undefined}
+
+People seem to want to know (at run time) if a label is undefined (I
+don't actually understand \emph{why}, particularly: it's a transient
+state, and \LaTeX{} deals with it quite well).
+
+A resolved label is simply a command:
+\csx{r@}\texttt{\meta{label-name}}; determining if the label is set is
+then simply a matter of detecting if the command exists. The usual
+\LaTeX{} internal way of doing this is to use the command
+\csx{@ifundefined}:
+\begin{quote}
+ \cmdinvoke*{@ifundefined}{\textup{r@}label-name}{undef-cmds}{def-cmds}
+\end{quote}
+In which, \meta{label-name} is exactly what you would use in
+a \csx{label} command, and the remaining two arguments are command
+sequences to be used if the label is undefined
+(\meta{undef-cmds}) or if it is defined
+(\meta{def-cmds}).
+
+Note that any command that incorporates \csx{@ifundefined} is naturally
+fragile, so remember to create it with \csx{DeclareRobustCommand} or to
+use it with \csx{protect} in a moving argument.
+
+If you're into this game, you may well not care about \LaTeX{}'s
+warning about undefined labels at the end of the document; however,
+if you are, include the command \csx{G@refundefinedtrue} in
+\meta{\texttt{undef-cmds}}.
+
+And of course, remember you're dealing in internal commands, and pay
+attention to the \Qref*{at-signs}{Q-atsigns}.
+
+All the above can be avoided by using the \Package{labelcas} package:
+it provides commands that enable you to switch according to the state
+of a single label, or the states of a list of labels. The package's
+definition is a bit complicated, but the package itself is pretty
+powerful.
+\begin{ctanrefs}
+\item[labelcas.sty]\CTANref{labelcas}
+\end{ctanrefs}
+
+\Question[Q-addtoreset]{Master and slave counters}
+
+It's common to have things numbered ``per chapter'' (for example, in
+the standard \Class{book} and \Class{report} classes, figures, tables
+and footnotes are all numbered thus). The process of resetting is
+done automatically, when the ``master'' counter is stepped (when the
+\csx{chapter} command that starts chapter \meta{n} happens, the
+\texttt{chapter} counter is stepped, and all the dependent counters are set
+to zero).
+
+How would you do that for yourself? You might want to number
+algorithms per section, or corollaries per theorem, for example. If
+you're defining these things by hand, you declare the relationship
+when you define the counter in the first place:
+\begin{quote}
+\cmdinvoke*{newcounter}{new-name}[master]
+\end{quote}
+says that every time counter \meta{master} is stepped, counter
+\meta{new-name} will be reset.
+
+But what if you have an uncooperative package, that defines the
+objects for you, but doesn't provide a programmer interface to make
+the counters behave as you want?
+
+The \csx{newcounter} command uses a \LaTeX{} internal command, and you
+can also use it:
+\begin{quote}
+\cmdinvoke*{@addtoreset}{new-name}{master}
+\end{quote}
+(but remember that it needs to be between \csx{makeatletter} and
+\csx{makeatother}, or in a package of your own).
+
+The \Package{chngcntr} package encapsulates the \csx{@addtoreset}
+command into a command \csx{counterwithin}. So:
+\begin{quote}
+\begin{verbatim}
+\counterwithin*{corrollary}{theorem}
+\end{verbatim}
+\end{quote}
+will make the corollary counter slave to theorem counters. The
+command without its asterisk:
+\begin{quote}
+\begin{verbatim}
+\counterwithin{corrollary}{theorem}
+\end{verbatim}
+\end{quote}
+will do the same, and also redefine \csx{thecorollary} as % line brk!
+\meta{theorem number}.\meta{corollary number}, which is a good scheme
+if you ever want to refer to the corollaries~--- there are potentially
+many ``corollary~1'' in any document, so it's as well to tie its number
+to the counter of the theorem it belongs to. This is true of pretty
+much any such counter-within-another; if you're not using the
+\Package{chngcntr}, refer to the answer to % line break!
+\Qref*{redefining counters' \csx{the-}commands}{Q-the-commands} for
+the necessary techniques.
+
+Note that the technique doesn't work if the master counter is |page|,
+the number of the current page. The |page| counter is stepped deep
+inside the output routine, which usually gets called some time after
+the text for the new page has started to appear: so special
+techniques are required to deal with that. One special case is dealt
+with elsewhere: \Qref*{footnotes numbered per page}{Q-footnpp}. One
+of the techniques described there, using package \Package{perpage},
+may be applied to any counter. The command:
+\begin{quote}
+\cmdinvoke*{MakePerPage}{counter}
+\end{quote}
+will cause \meta{counter} to be reset for each page. The package uses
+a label-like mechanism, and may require more than one run of \LaTeX{}
+to stabilise counter values~--- \LaTeX{} will generate the usual
+warnings about labels changing.
+\begin{ctanrefs}
+\item[chngcntr.sty]\CTANref{chngcntr}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage]
+\end{ctanrefs}
+
+\Question[Q-fontsize]{Fonts at arbitrary sizes}
+
+Almost all fonts, nowadays, are provided with \LaTeX{} control
+(\extension{fd}) files, so the temptation to risk the
+\Qref*{problems of \csx{newfont}}{Q-newfont*} is usually easy to
+resist.
+
+However, one temptation remains, arising from the way that \LaTeX{}
+restricts the sizes of fonts. In fact, the restriction only
+significantly applies to the default (Computer Modern) and the
+Cork-encoded (\acro{T}1) EC fonts, but it is widely considered to be
+anomalous, nowadays. In recognition of this problem, there is a
+package \Package{fix-cm} which will allow you to use the fonts, within
+\LaTeX{}, at any size you choose. If you're not using scaleable
+versions of the fonts, most modern distributions will just generate an
+appropriate bitmap for you.
+
+So, suppose you want to produce a heading in Computer Modern Roman at
+30 points, you might be tempted to write:
+\begin{quote}
+\begin{verbatim}
+\newfont{\bigfont}{cmr10 at 30pt}
+\begin{center}
+ \bigfont Huge text
+\end{center}
+\end{verbatim}
+\end{quote}
+which will indeed work, but will actually produce a worse result than
+\begin{quote}
+\begin{verbatim}
+\usepackage{fix-cm}
+...
+\begin{center}
+ \fontsize{30}{36}\selectfont
+ Huge text
+\end{center}
+\end{verbatim}
+\end{quote}
+Note that the \Package{fix-cm} package was not distributed until the
+December 2003 edition of \LaTeX{}; if you have an older distribution,
+the packages \Package{type1cm} (for \acro{CM} fonts) and
+\Package{type1ec} (for \acro{EC} fonts) are available.
+
+\Package{Fix-cm} doesn't has one or two omissions~--- fonts the \latex{}
+team did not consider useful, or something; the CM dunhill fonts (as
+CM, but with stretched ascenders) and the CM fibonacci font (which is only
+available in 8-point design size) are certainly missing. If
+\Package{fix-cm} doesn't do the job, try the \Package{type1xx}
+packages, or the \Package{anyfontsize} package.
+
+A further alternative might be to switch to the
+\Qref*{\FontName{Latin} \FontName{Modern} fonts}{Q-uselmfonts} (which
+provide a close simulacrum of the \FontName{Computer}
+\FontName{Modern} set); these fonts were scaleable from their first
+distribution, and don't therefore need any such trick as the above.
+\begin{ctanrefs}
+\item[anyfontsize.sty]\CTANref{anyfontsize}
+\item[fix-cm.sty]Distributed as part of \CTANref{latex}[fix-cm] (an unpacked
+ version is available at \CTANref{fix-cm})
+\item[\nothtml{\rmfamily}\FontName{Latin} \FontName{Modern} fonts]\CTANref{lm}
+\item[type1cm.sty]\CTANref{type1cm}
+\item[type1ec.sty]\CTANref{type1ec} (the package is actually part of
+ the \CTANref{cm-super} distribution, but it works happily in
+ the absence of the scaled fonts)
+\end{ctanrefs}
+\LastEdit{2013-06-04}
+
+\Question[Q-latexqual]{The quality of your \LaTeX{}}
+
+The \Package{l2tabu} tutorial (mentioned in % ! line break
+\Qref[question]{online introductions}{Q-man-latex}) is undoubtedly a
+good read.
+
+However, it's always difficult to remember the things you should
+\emph{not} do, when there are so many things to remember that you
+really must do: some automation is useful\dots{}.
+
+The nicely-named \Package{nag} allows you to apply a configurable set
+of checks to your document, as you run it through \LaTeX{}; you get
+messages like:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+Package nag Warning: Command \bf is an old LaTeX 2.09 command.
+(nag) Use \bfseries or \textbf instead on input line 30.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+Package nag Warning: Command \bf is an old
+ LaTeX 2.09 command.
+(nag) Use \bfseries or \textbf
+ instead on input line 30.
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+\begin{wideversion}
+ (the package provides a demo file which contains most of the sorts
+ of errors you might make~--- the example is one of them).
+\end{wideversion}
+\begin{narrowversion}
+ (the error lines above represent two lines which have been wrapped;
+ the package provides a demo file which contains most of the sorts of
+ errors you might make~--- the example is one of them).
+\end{narrowversion}
+While \Package{l2tabu} and \Package{nag} alert you to \emph{possible}
+programming errors, you should not forget that they are merely
+commenting on \emph{style}; don't assume that a \Package{nag} error is
+going to damn your code~--- rather, note the issue and try to train
+your fingers not to do the same ``next time''.
+
+The \ProgName{lacheck} program analyses your source and comments on
+it; its view of what is ``bad'' is \emph{very} subjective (the
+documentation says), but it can be useful.
+
+There's also a web site
+\href{http://www.kohm.name/markus/texidate.html}{TeXidate}
+which will do a static analysis of your document (unfortunately, you
+have to paste your document source into a text window). The site
+doesn't seem as comprehensive as \Package{nag}, but it allows you to
+download its script, which you can then juggle with to make it more
+draconian.
+\begin{ctanrefs}
+\item[l2tabu]Browse \CTANref{l2tabu} for a copy of the document in a
+ language that is convenient for you
+\item[lacheck]\CTANref{lacheck}
+\item[nag.sty]\CTANref{nag}
+\end{ctanrefs}
+\LastEdit{2012-10-09}
+
+\Question[Q-ltx-csv]{Process a \acro{CSV} file in \latex{}}
+
+Comma-separated-variable (\acro{CSV}) files are a common means of
+interchanging simple data between applications; for example, most
+spreadsheet applications can provide files containing tables of
+numbers with commas between them. One can envisage these tables as
+``\latex{} tables'', and the packages to process them all provide
+table generation, one way or another.
+
+For rather a long time, the canonical tools for dealing with such
+files have been those provided in the \Package{datatool} bundle;
+packages in the bundle allow the user to write procedures to process
+numbers, currency amounts, names, etc., and to display them in tables
+(including pie charts).
+
+The \Package{csvsimple} does similar tasks. Its processing is
+controlled by keys established via the \Package{pgfkeys} package,
+which define how each row of the \acro{CSV} file is to be processed.
+
+For usage ``nearer to the bone'', one might consider the commands
+\csx{docsvlist} and \csx{forcsvlist} (from the \Package{etoolbox}
+package). The first uses the time-honoured \latex{} technique of
+changing the definition of a \csx{do} command; it runs through the
+list, and processes every item of the list as the argument of the
+\csx{do} command; so:
+\begin{quote}
+\begin{verbatim}
+\begin{itemize}
+\renewcommand*{\do}[1]{\item #1}
+\docsvlist{item1, item2, {item3a, item3b}, item4}
+\end{itemize}
+\end{verbatim}
+\end{quote}
+will convert the elements of a \acro{CSV} list into an itemised list.
+
+The macro \csx{forcsvlist} applies a function to each element of a
+\acro{CSV} list; this can of course be used to implement
+\csx{docsvlist}, at the cost of a little clarity.
+\begin{ctanrefs}
+\item[csvsimple.sty]\CTANref{csvsimple}
+\item[datatool \nothtml{\rmfamily}bundle]\CTANref{datatool}
+\item[etoolbox.sty]\CTANref{etoolbox}
+\item[pgfkeys.sty]Distributed as part of \CTANref{pgf}
+\end{ctanrefs}
+\LastEdit*{2013-09-10}
diff --git a/help/uk-tex-faq/faq-projects.tex b/help/uk-tex-faq/faq-projects.tex
new file mode 100644
index 0000000000..e7a616ace8
--- /dev/null
+++ b/help/uk-tex-faq/faq-projects.tex
@@ -0,0 +1,644 @@
+% $Id: faq-projects.tex,v 1.29 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Current \TeX{}-related projects}
+
+\Question[Q-LaTeX3]{The \LaTeX{} project}
+
+The \LaTeX{} project team (see \URL{http://www.latex-project.org/latex3.html})
+is a small group of volunteers whose aim is
+to produce a major new document processing system based on the
+principles pioneered by Leslie Lamport in the current \LaTeX{}. The
+new system is (provisionally) called \LaTeX{}3; it
+will remain freely available and it will be fully documented at
+all levels.
+
+The \LaTeX{} team's first product (\LaTeXe{}) was delivered in 1994
+(it's now properly called ``\LaTeX{}'', since no other version is current).
+
+\LaTeXe{} was intended as a consolidation exercise, unifying several
+sub-variants of \LaTeX{} while changing nothing whose change wasn't
+absolutely necessary. This has permitted the team to support a single
+version of \LaTeX{}, in parallel with development of \LaTeX{}3.
+
+Some of the older discussion papers about directions for \LaTeX{}3 are
+to be found on \acro{CTAN}; other (published) articles are to be found
+on the project web site (\URL{http://www.latex-project.org/papers/}).
+
+Some of the project's experimental code is visible on the net:
+\begin{itemize}
+\item via \URL{http://www.latex-project.org/code.html}, which points
+ to the project's \acro{SVN} repository;
+\item via the project's
+ \href{https://github.com/latex3/svn-mirror}{\emph{GitHub} mirror};
+\item from \acro{CTAN}: snapshots of two major collections from the
+ code, \Package{l3kernel} (supporting \LaTeX{}3 coding conventions in
+ a \LaTeXe{} environment), \Package{l3packages} (a first cut of a
+ ``document designer's interface'') as well as
+ \Package{l3experimental} (new stuff that's still under
+ development).
+\end{itemize}
+The packages \Package{l3kernel} and \Package{l3packages} provide an
+``experimental harness'' that may be used as a testbed for \latex{}3
+work.
+
+Note that \Package{l3kernel} introduces a coding structure quite
+different from earlier \latex{} code; a few hardy authors, who are not
+members of the project, are nevertheless using it in their development
+work.
+
+Anyone may participate in discussions of the future of \LaTeX{}
+through the mailing list \texttt{latex-l}; some development work
+(outside the project) is discussed on the list. Subscribe to the list
+by sending a message `\texttt{subscribe latex-l <\emph{your name}>}'
+to \mailto{listserv@urz.Uni-Heidelberg.de}
+\begin{ctanrefs}
+\item[l3experimental \nothtml{\rmfamily}bundle]\CTANref{l3experimental}
+\item[l3kernel \nothtml{\rmfamily}bundle]\CTANref{l3kernel}
+\item[\nothtml{\rmfamily}\LaTeX{} project publications]\CTANref{ltx3pub}
+\item[l3packages \nothtml{\rmfamily}bundle]\CTANref{l3packages}
+\end{ctanrefs}
+\LastEdit{2012-02-07}
+
+\Question[Q-mathml]{Future \acro{WWW} technologies and \AllTeX{}}
+
+An earlier answer % ! line break
+(\Qref[number]{``converting to \acro{HTML}''}{Q-LaTeX2HTML})
+addresses the issue of converting existing \AllTeX{} documents for
+viewing on the Web as \acro{HTML}. All the present techniques are
+somewhat flawed: the answer explains why.
+
+However, things are changing, with
+better font availability, cunning \acro{HTML} programming and the
+support for new Web standards.
+\begin{description}
+\item[Font technologies] Direct representation of mathematics in
+ browsers has been hampered up to now by the limited range of symbols
+ in the fonts whose availability designers can count on. Some existing
+ \AllTeX{} to \acro{HTML} converters provide maths symbols by
+ hitching them to alternate font face specifications for standard
+ code points in a non-standard way. This does nothing for the
+ universality of the \acro{HTML} so generated.
+
+ Now, however, free Unicode-encoded OpenType fonts, with coverage of
+ mathematical symbols, are starting to appear. The much-heralded
+ \href{http://www.stixfonts.org/}{\FontName{STIX} fonts} are now
+ available on \acro{CTAN}, and a tweaked version
+ (\FontName{XITS}) and \FontName{Asana Math} are also
+ available. The \acro{STIX} project has still not released macros
+ for using the fonts, but the \Package{unicode-math} package will do
+ what is necessary under \xetex{} and \luatex{}, and the fonts can of
+ course be used in browsers.
+%% In the near future, we can expect rather wide availability of
+%% Unicode fonts with good coverage of symbols, which should make life
+%% easier for those who need to represent mathematics.
+\item[\acro{XML}] The core of the range of new standards is
+ \acro{XML}, which provides a framework for better structured markup;
+ limited support for it has already appeared in some browsers.
+
+ Conversion of \AllTeX{} source to \acro{XML} is already available
+ (through \TeX{}4ht at least), and work continues in that arena. The
+ alternative, authoring in \acro{XML} (thus producing documents that
+ are immediately Web-friendly, if not ready) and using \AllTeX{} to
+ typeset is also well advanced. One useful technique is
+ \Qref*{\emph{transforming} the \acro{XML} to \LaTeX{}}{Q-SGML2TeX},
+ using an \acro{XSLT} stylesheet or code for an \acro{XML} library,
+ and then simply using \LaTeX{}; alternatively, one may
+ \Qref*{typeset direct from the \acro{XML} source}{Q-readML}.
+\item[Direct representation of mathematics]
+ Math\acro{ML} is a standard for representing maths on the Web; its
+ original version was distinctly limited, but version 2 of Math\acro{ML}
+ has had major browser support since 2002 with richness of mathematical
+ content for online purposes approaching that of \TeX{} for print.
+ Browser support for Math\acro{ML} is provided by \ProgName{amaya}, the
+ `Open Source' browser \ProgName{mozilla} (and its derivatives
+ including \ProgName{NetScape}, \ProgName{Firefox} and \ProgName{Galeon}) and
+ \ProgName{Internet Explorer} when equipped with a suitable plug-in
+ such as \ProgName{MathPlayer}.
+ There's evidence that \AllTeX{} users are starting to use such
+ browsers. Some believe that \acro{XHTML}+Math\acro{ML} now provides
+ better online viewing than \acro{PDF}.
+ Work to produce \acro{XHTML}+Math\acro{ML} is well advanced in both the
+ \TeX{}4ht and \ProgName{TtH} projects for \AllTeX{} conversion.
+%% Such conversion, however, has limits of soundness unless one
+%% is very much aware of the needs of one's conversion program
+%% and adapts one's usage of \AllTeX{} accordingly.
+
+ The \href{http://www.mathjax.org}{\ProgName{MathJax}} engine will process the
+ content of \latex{} \csx{[} \dots{}~\csx{]} and \csx{(} \dots{}~\csx{)}
+ `environments' in an \acro{HTML} document, to produce mathematical
+ output that may (for example) be cut-and-pasted into other programs.
+
+ Incorporation into your document can be
+\begin{wideversion}
+ as simple as incorporating:
+\begin{verbatim}
+<script type="text/javascript"
+ src="http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS_HTML">
+</script>
+\end{verbatim}
+ into the header of your \acro{HTML} document,
+\end{wideversion}
+\begin{narrowversion}
+ incorporating the script~---
+ \url{http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS_HTML}
+ ---~as the \texttt{src} tab of a \texttt{script type="text/javascript"}
+ element in the header of your \acro{HTML} document,
+\end{narrowversion}
+ though the \href{http://www.mathjax.org/}{MathJax project's site}
+ also allows you to download your own copy and install it on one of
+ \emph{your} servers. \ProgName{MathJax} is open source software, so
+ you could, in principle, extend it to do even more eccentric tasks.
+
+ An approach different from \AllTeX{} conversion is taken by
+ the \href{http://www.albany.edu/~hammond/gellmu/}{\emph{GELLMU} Project}.
+ Its \emph{article} \acro{XML} document type, which has a markup vocabulary
+ close to \LaTeX{} that can be edited using \LaTeX{}-like markup
+ (even though it is not \LaTeX{}~--- so far), comes with translators
+ that make both \acro{PDF} (via \emph{pdflatex}) and
+ \acro{XHTML}+Math\acro{ML}. Such an approach avoids the inherent
+ limitations of the ``traditional'' \AllTeX{} translation processes,
+ which have traps that can be sprung by unfettered use of \AllTeX{}
+ markup.
+\item[Graphics]
+ \acro{SVG} is a standard for graphics representation on the web.
+ While the natural use is for converting existing figures,
+ representations of formulas are also possible, in place of the separate
+ bitmaps that have been used in the past (and while we wait for the
+ wider deployment of Math\acro{ML}).
+
+ Browser plug-ins, that deal with \acro{SVG} are already available
+ (Adobe offer one, for example). More recently, the open source
+ graphics editor \href{http://www.inkscape.org/}{\ProgName{Inkscape}}
+ has appeared, and has been reported to be useful for
+ \acro{SVG}-related work in at least one \TeX{}-related project. Be
+ aware that the developers of \ProgName{Inkscape} have no illusions
+ about being able to replace commercial software, yet\dots{}
+\item[Direct use of \TeX{} markup]
+ Some time back, \acro{IBM} developed a browser plug-in called
+ TechExplorer, which would display \AllTeX{} documents direct in a
+ browser. Over the years, it developed into a Math\acro{ML} browser
+ plug-in, while still retaining its \AllTeX{} abilities, but it's now
+ distributed (free for Linux and Windows platforms) by
+ \href{http://www.integretechpub.com/}{Integre Technical Publishing}.
+
+ The disadvantage of the TechExplorer approach is that it places the
+ onus on the browser user; and however technically proficient
+ \emph{you} are, it's never safe to assume too much of your readers.
+ An interesting alternative is
+ \href{http://www.forkosh.com/mathtex.html}{Math\TeX{}}, which sits
+ on your server as a \acro{CGI} script, and you use it to include
+ your \TeX{}, in your \acro{HTML}, as if it were an image:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+<img src="/cgi-bin/mathtex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt">
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+<img src="/cgi-bin/mathtex.cgi?f(x)=
+ \int\limits_{-\infty}^xe^{-t^2}dt">
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+(\Package{Mathtex} supersedes the author's earlier \Package{mimetex}.)
+\end{description}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Asana Math fonts]\CTANref{asana-math}
+\item[GELLMU]\CTANref{gellmu}
+\item[MathTeX]\CTANref{MathTeX}
+\item[MimeTeX]\CTANref{MimeTeX}
+\item[\nothtml{\rmfamily}STIX fonts]\CTANref{stix}
+\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/})
+\item[unicode-math.sty]\CTANref{unicode-math}
+\item[\nothtml{\rmfamily}XITS fonts]\CTANref{xits}
+\end{ctanrefs}
+\LastEdit{2011-10-17}
+
+\Question[Q-textrace]{Making outline fonts from \MF{}}
+
+\ProgName{TeXtrace}, originally developed by P\'eter Szab\'o, is a
+bundle of Unix scripts that use Martin Weber's freeware boundary
+tracing package
+\href{http://autotrace.sourceforge.net}{\ProgName{autotrace}} to
+generate Type~1 outline fonts from \MF{} bitmap
+font outputs. The result is unlikely ever to be of the quality of
+the commercially-produced Type~1 font, but there's always the
+\href{http://fontforge.sourceforge.net/}{\ProgName{FontForge}} font
+editor to tidy things. Whatever, there
+remain fonts which many people find useful and which fail to attract
+the paid experts, and auto-tracing is providing a useful service here.
+Notable sets of
+fonts generated using \ProgName{TeXtrace} are P\'eter Szab\'o's own
+\acro{EC}/\acro{TC} font set \FontName{tt2001} and Vladimir Volovich's
+\acro{CM}-Super set, which covers the \acro{EC}, \acro{TC}, and the
+Cyrillic \acro{LH} font sets (for details of both of which sets, see
+\Qref[answer]{``8-bit'' type 1 fonts}{Q-type1T1}).
+
+Another system, which arrived slightly later, is
+\href{http://www.cs.uu.nl/~hanwen/mftrace/}{\ProgName{mftrace}}:
+this is a small \ProgName{Python} program that does the same job.
+\ProgName{Mftrace} may use either \ProgName{autotrace} (like
+\ProgName{TeXtrace}) or Peter Selinger's
+\href{http://potrace.sourceforge.net}{\ProgName{potrace}} to produce
+the initial outlines to process. \ProgName{Mftrace} is said to be
+more flexible, and easier to use, than is \ProgName{TeXtrace}, but both systems
+are increasingly being used to provide Type~1 fonts to the public domain.
+
+The \ProgName{MetaType1} system aims to use \MF{} font sources, by way
+of \MP{} and a bunch of scripts and so on, to produce high-quality
+Type~1 fonts. The first results, the % ! line break
+\Qref*{\Package{Latin Modern} fonts}{Q-type1T1}, are now
+well-established, and a bunch of existing designs have been reworked
+in MetaType1 format.
+
+\Package{Mf2pt1} is another translator of \MF{} font sources by way of
+\MP{}; in addition,
+available, \Package{mf2pt1} will use
+\href{http://fontforge.sourceforge.net/}{\ProgName{fontforge}} (if it's
+available) to auto-hint the result of its conversion.
+(\Package{Mf2pt1} is also written in \ProgName{perl}.)
+\begin{ctanrefs}
+\item[MetaType1]\CTANref{metatype1}
+\item[mf2pt1]\CTANref{mf2pt1}
+\end{ctanrefs}
+
+\Question[Q-WYGexpts]{The \TeX{} document preparation environment}
+
+``\Qref*{Why \TeX{} is not \WYSIWYG{}}{Q-notWYSIWYG}''
+outlines the reasons (or excuses) for the huge disparity of user
+interface between ``typical'' \TeX{} environments and commercial word
+processors.
+
+Nowadays, at last, there is a range of tools available that try either
+to bridge or to close the gap. One range modestly focuses on
+providing the user with a legible source document. At the other
+extreme we have \href{http://www.texmacs.org}{\ProgName{TeXmacs}},
+a~document processor using
+\TeX{}'s algorithms and fonts for both editor display and printing.
+\ProgName{TeXmacs} does not use the \TeX{}
+language itself (though among other formats, \LaTeX{} may be exported
+and imported). A bit closer to \LaTeX{} is
+\href{http://www.lyx.org/}{LyX}, which has its own
+editor display and file formats as well, but does its print output by
+exporting to \LaTeX{}. The editor display merely resembles the
+printed output, but you have the possibility of entering arbitrary
+\LaTeX{} code. If you use constructs that LyX does not
+understand, it will just display them as source text marked red, but
+will properly export them.
+
+Since a lot of work is needed to create an editor from scratch that
+actually is good at editing (as well as catering for \TeX{}), it is
+perhaps no accident that several approaches have been implemented
+using the extensible \ProgName{emacs} editor. The low end of the
+prettifying range is occupied by syntax highlighting: marking \TeX{}
+tokens, comments and other stuff with special colours.
+Many free editors (including \ProgName{emacs}) can cater for \TeX{} in
+this way. Under Windows, one of the more popular editors with such
+support is the
+Shareware product \href{http://www.winedt.com/}{\ProgName{winedt}}.
+Continuing the range of
+tools prettifying your input, we have the \ProgName{emacs} package
+\href{http://x-symbol.sourceforge.net}{\Package{x-symbol}}, which does
+the \WYSIWYG{} part of its work by replacing single \TeX{} tokens and
+accented letter sequences with appropriate-looking characters on the
+screen.
+
+A different type of tool focuses on making update and access to
+previews of the typeset document more immediate. A recent addition
+in several viewers, editors and \TeX{} executables are so-called
+`source specials' for cross-navigation. When \TeX{} compiles a
+document, it will upon request insert special markers for every input
+line into the typeset output. The markers are interpreted by the \acro{DVI}
+previewer which can be made to let its display track the page
+corresponding to the editor input position, or to let the editor jump
+to a source line corresponding to a click in the preview window.
+
+An \ProgName{emacs} package that combines this sort of editor movement
+tracking with automatic fast recompilations (through the use of dumped
+formats) is
+\href{http://pauillac.inria.fr/whizzytex/}{\Package{WhizzyTeX}}
+ which is best used with a previewer by the
+same author.
+
+Another \ProgName{emacs} package called
+\href{http://preview-latex.sourceforge.net}{\Package{preview-latex}}
+tries to solve
+the problem of visual correlation between source and previews in a
+more direct way: it uses a \LaTeX{} package to chop the document source
+into interesting fragments (like figures, text or display math) which
+it runs through \LaTeX{} and replaces the source text of those
+fragments with the corresponding rendered output images. Since it
+does not know about the structure of the images, at the actual cursor
+position the source text is displayed while editing rather than the
+preview. This approach is more or less a hybrid of the source
+prettifying and fast preview approaches since it works in the source
+buffer but uses actual previews rendered by \LaTeX{}.
+
+A more ambitious contender is called \TeX{}lite. This
+system is only available on request from its author;
+it continuously updates its screen with the help of a special version
+of \TeX{} dumping its state in a compressed format at each page and
+using hooks into \TeX{}'s line breaking mechanism for reformatting
+paragraphs on the fly. That way, it can render the output from the
+edited \TeX{} code with interactive speed on-screen, and it offers the
+possibility of editing directly in the preview window.
+
+That many of these systems occupy slightly different niches can be
+seen by comparing the range of the
+\ProgName{emacs}-based solutions ranging from syntax highlighting to instant
+previewing: all of them can be activated at the same time without
+actually interfering in their respective tasks.
+
+The different approaches offer various choices differing in the
+immediacy of their response, the screen area they work on (source or
+separate window), degree of correspondence of the display to the final
+output, and the balance they strike between visual aid and visual
+distraction.
+\begin{ctanrefs}
+\item[preview-latex]Distributed as part of \CTANref{auctex}[preview-latex]
+\item[texmacs]Browse \CTANref{texmacs}
+\end{ctanrefs}
+
+\Question[Q-omegaleph]{Omega and Aleph}
+
+Omega\nothtml{ (\ensuremath{\Omega})} was developed as an extension of
+\TeX{}, to use with multilingual texts, expressed in a variety of
+input encodings. Omega uses 16-bit, Unicode-encoded, characters. It
+provides many innovative concepts, notably including the ``translation
+process'' that takes a character stream and transforms it according to
+various processes that may be internally specified, or be a separate
+program.
+
+While Omega showed a lot of promise at its mid-1990s announcement,
+progress was slow, and development was essentially dead by the time
+that one of the original developers withdrew (taking with him a bunch
+of research students).
+
+Before that distressing event, a separate thread of development had
+started, to produce a program % !avoid space between Aleph and comma
+called Aleph\nothtml{ (\ensuremath{\aleph})}, which merged the facilities of
+\Qref*{\eTeX{}}{Q-etex} into a stable Omega codebase and added other
+extensions. Aleph also proved an attractive platform for many people;
+but its development, too, has dried up.
+
+A presentation at Euro\TeX{} 2006 claimed that development of Omega
+was picking up again, in parallel with research into what the (new)
+developers consider a rational scheme for supporting \TeX{}-style
+typesetting. The new system was to be known as Omega-2
+(\latexhtml{\ensuremath{\Omega_2}}{Omega subscript 2}), and was to be
+designed in a modular fashion so that support of new facilities (such
+as use of advanced OpenType fonts) could be added in a relatively
+straightforward fashion. A quick web search leads to a recommendation
+that potential users consider \Qref*{\luatex{}}{Q-luatex} instead;
+fortunately, lessons learned in Aleph project have been carried
+forward in the development of \luatex{}.
+
+\Question[Q-xetex]{\xetex{}}
+
+\href{http://scripts.sil.org/xetex}{\xetex{}}, by Jonathan Kew, is a
+successor to the shareware TeX/GX program for Macintoshes. It was
+developed as a \acro{WEB} `change file' applied to the original source
+of \tex{}; the main changes include:
+\begin{description}
+\item[The input stage] \xetex{} by default reads Unicode (UTF-8, for
+ instance), although it's also capable of interpreting differently
+ encoded files (for backwards compatibility). Multibyte characters
+ are reduced to a single internal character upon reading, so they are
+ considered as a unique entity when tokenization is performed. (So,
+ for example, you can have command names in cyrillic, if you must,
+ but such a practice is not recommended.)
+\item[The font management] a substantial revision has added support
+ for OpenType and TrueType fonts, delegating some parts to
+ third-party libraries.
+\item[The maths font set up] \xetex{} introduces new primitives for
+ extending the \csx{mathcode} and \csx{mathchardef} commands in TeX,
+ allowing the user to specify characters in the whole Unicode set and
+ in 256 `math families' (\tex{} only has 16, which limits some maths
+ coding techniques).
+\item[``Post-processing'' features (A)] \xetex{} links to the
+ \ProgName{teckit} library so it can apply a \extension{map} file
+ that allows transformation of characters in already formed token
+ lists, before they are processed in the ``stomach'' for typesetting.
+ In this way, a declaration ``\texttt{Ligatures=TeX}'' is provided,
+ which attaches a map directive to the font that transforms the
+ character combinations (familiar to \tex{} users) into a single
+ character; for instance \texttt{-{}-{}-} is transformed into
+ ``\textemdash''.
+\item[``Post-processing'' features (B)] Characters can be assigned to
+ an ``interchar token class'' and it is possible to specify tokens to
+ be added when there is a transition from one class to another. The
+ packages \Package{polyglossia}, \Package{xeCJK} and
+ \Package{ucharclasses} exploit this feature.
+\end{description}
+Otherwise, the process of typesetting is essentially the same as
+\tex{}'s. (However some changes have also been made in the
+hyphenation stage that may give slightly different results if the same
+document is compiled with \pdftex{} or \xetex{}.)
+\begin{ctanrefs}
+\item[polyglossia.sty]\CTANref{polyglossia}
+\item[xeCJK.sty]\CTANref{xecjk}
+\item[ucharclasses.sty]\CTANref{ucharclasses}
+\end{ctanrefs}
+\LastEdit{2013-02-21}
+
+
+\Question[Q-luatex]{\PDFTeX{} and \LuaTeX{}}
+
+Elsewhere in these \acro{FAQ}s, we learn that development of
+\Qref*{\PDFTeX{}}{Q-whatpdftex} is ``in essence'' complete~--- no new
+facilities are being developed at the time of writing. The \PDFTeX{}
+team has announced that they have frozen \PDFTeX{}'s specification in
+its current state (version 1.40.11), and that nothing but bug
+corrections will be provided up to the time of the final release,
+\PDFTeX{} 1.50.0. (The interpretation of the statement seems to allow
+sensible changes that are beyond any reasonable definition of
+\emph{bug}\dots{})
+
+As \PDFTeX{} development ran down,
+development of a new system, \LuaTeX{} was started.
+\href{http://www.lua.org/}{\ProgName{Lua}} is a interpreter designed
+to be incorporated into other applications. \LuaTeX{} consists of a
+\TeX{}-like engine with a \ProgName{lua} interpreter `embedded' in it;
+the \ProgName{lua} interpreter has access to many of the data
+structures used for typesetting, so that the programmer may also
+interpolate chunks of \ProgName{lua} code into their \AllTeX{} macros,
+or as `call-backs' for use when the \TeX{}-like engine does certain
+operations.
+
+This arrangement offers the prospect of a ``semi-soft'' typesetting
+engine: it will have its basic behaviour, but the user gets to
+redefine functionality if an idea occurs~--- there will be no need to
+persuade the world first, and then find a willing developer to work on
+the sources of of the distribution.
+
+The \href{http://www.luatex.org/}{\LuaTeX{} project} is (with monetary
+support from various sources) pursuing avenues that many of the other
+current projects have in their sights, notably Unicode character
+representations and support for OpenType fonts. The intention is
+to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}.
+Users may also care to view the % ! line break
+\href{http://www.luatex.org/documentation.html}{\luatex{} documentation page}
+or the \href{http://wiki.luatex.org}{\luatex{} \acro{WIKI}}
+
+\texlive{} (2013) holds version 0.76.0 of \luatex{}. This version
+demonstrates the ``final functionality'', though the project
+remains a \ensuremath{\beta}-release. Functional stability was first
+declared for version 0.50.0, released near the end of December 2009.
+
+\CONTeXT{} `Mark 4' can already make use of \LuaTeX{}; much of its
+code already appears in two forms~--- a \TeX{}-based version
+(\extension{mkii}) and a `\extension{mkiv}' version (new functionality
+typically \emph{only} appears in `\extension{mkiv}' form), which uses
+\luatex{} extensions (including \ProgName{lua} scripting). \LaTeX{}
+packages that support its use are appearing (some of them providing
+re-implementations of existing \context{} code).
+
+\latex{} running over \luatex{} (commonly known as Lua\latex{}) is not
+an ``official'' entity (yet), but useful packages are
+appearing (i.e., the \ctan{} path \path{macros/luatex/latex} holds
+several items).
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\luatex{} snapshot]\CTANref{luatex}
+\item[\nothtml{\rmfamily}\pdftex{} distribution]\CTANref{pdftex}
+\end{ctanrefs}
+\LastEdit{2013-05-21}
+
+\Question[Q-ant]{The \textsf{ANT} typesetting system}
+
+Achim Blumensath's \href{http://ant.berlios.de}{\textsf{ANT}} project
+aims not to replicate \TeX{} with a different implementation
+technique, but rather to provide a replacement for \TeX{} which uses
+\TeX{}-like typesetting algorithms in a very different programming
+environment. \textsf{ANT} remains under development, but it is now
+approaching the status of a usable typesetting system.
+
+\textsf{ANT}'s markup language is immediately recognisable to the
+\AllTeX{} user, but the scheme of implementing design in
+\textsf{ANT}'s own implementation language (presently
+\ProgName{OCaml}) comes as a pleasant surprise to the jaded \acro{FAQ}
+writer. This architecture holds the promise of a system that avoids a
+set of serious problems with \TeX{}'s user interface: those that
+derive from the design language being the same as the markup language.
+\begin{ctanrefs}
+\item[\textsf{ANT}]\CTANref{ant}
+\end{ctanrefs}
+
+\Question[Q-extex]{The \ExTeX{} project}
+
+\href{http://www.extex.org/}{The \ExTeX{} project} is
+building on the experience of the many existing \TeX{} development and
+extension projects, to develop a new \TeX{}-like system. The system
+is to be developed in Java (like the ill-fated \NTS{} project).
+
+While \ExTeX{} will implement all of \TeX{}'s primitives, some may be
+marked as obsolete, and ``modern'' alternatives provided (an obvious
+example is the primitive \csx{input} command, whose syntax inevitably
+makes life difficult for users of modern operating system file
+paths). Desirable extensions from \Qref*{\eTeX{}}{Q-etex},
+\Qref*{\PDFTeX{}}{Q-whatpdftex} and \Qref*{\ensuremath{\Omega}}{Q-omegaleph}
+have been identified.
+
+Usability will be another focus of the work: debugging support and log
+filtering mechanisms will please those who have long struggled with
+\TeX{} macros.
+
+\ExTeX{} will accept Unicode input, from the start. In the longer
+term, drawing primitives are to be considered.
+
+\Question[Q-biblatex]{Replacing the \BibTeX{}--\LaTeX{} mechanism}
+
+Producing a successor to \BibTeX{} has long been a favoured activity
+among a certain class of \TeX{}-users; the author has seen reports of
+progress (on several projects), over the years, but few that claim to
+be ready for ``real-world'' use.
+
+Few would deny that \BibTeX{} is ripe for renewal: as originally
+conceived, it was a program for creating bibliographies for technical
+documents, in English. People have contributed mechanisms for a
+degree of multilingual use (whose techniques are arcane, and quite
+likely inextensible), while an extension (\ProgName{bibtex8}) allows
+use with 8-bit character codes, thus providing some multilingual
+capabilities. In addition, specialist \BibTeX{} style files are
+available for use in non-technical papers.
+
+\BibTeX{} uses a style language whose mechanisms are unfamiliar to
+most current programmers: it's difficult to learn, but since there are
+few opportunities to write the language, it's also difficult to become
+fluent (in the way that so many people fluently write the equally
+arcane \TeX{} macro language).
+
+Oren Patashnik (the author of \BibTeX{}) summarises the issues as he
+sees them, in a % !line break
+\href{http://tug.org/TUGboat/Articles/tb24-1/patashnik.pdf}{\acro{TUG} conference paper from 2003}
+that seems to suggest that we might expect a
+\BibTeX{}~1.0 \dots{} which hasn't (yet) appeared.
+
+In the absence of \BibTeX{}~1.0, what do we need from the bibliography
+system of the future?~--- simple: a superset of what \BibTeX{} does
+(or can be made to do), preferably implementing a simpler style
+language, and with coherent multilingual capabilities.
+
+There are two parts to a bibliography system; processing the database
+of citations, and typesetting the results. The existing \bibtex{}
+system provides a means of processing the database, and there are
+macros built into \latex{}, as well as many \latex{} packages, that
+process the results.
+
+Of the direct \BibTeX{} replacements, only two have been submitted to
+\acro{CTAN}: Cross\TeX{} and \ProgName{biber}.
+
+Cross\TeX{}'s language feels familiar to the existing user of
+\BibTeX{}, but it's redesigned in an object-oriented style, and looks
+(to a non-user) as if it may well be adequately flexible. It is said
+to operate as a \bibtex{} replacement.
+
+Cross\TeX{}'s team respond to queries, and seem well aware of the
+need for multilingual support, though it isn't currently offered.
+
+\ProgName{Biber} is intimately associated with the \latex{} package
+\Package{biblatex}; it is logically a \bibtex{} replacement, but is also
+capable of using bibliography databases in its own
+\ProgName{biblatexml} (\acro{XML}-based) format. \Package{Biblatex}
+can also use \bibtex{}, but \ProgName{biber} opens up a far wider
+range of possibilities, including full Unicode support.
+
+\Package{Biblatex} is a processor for the output of an application
+such as \ProgName{biber} or \bibtex{}; the style of citations and of
+the bibliography itself (in your document) is determined by the way
+your \Package{biblatex} style has been set up, not on some
+\bibtex{}-\latex{} package combination. \Package{Biblatex}'s
+structure thus eliminates the collections of \BibTeX{} styles, at a
+stroke; it comes with a basic set of styles, and details are
+determined by options, set at package loading time. The author,
+Philipp Lehman, evaluated the whole field of bibliography software
+before starting, and as a result the package provides answers to
+many of the questions asked in the bibliography sections of these
+\acro{FAQ}s.
+
+\Package{Biblatex} was released as experimental software, but it's
+clear that many users are already using it happily; Lehman is
+responsive to problem reports, at the moment, but a \emph{de facto}
+set of expert users is already establishing itself. A set of
+contributed styles has appeared, which cover some of the trickier
+bibliography styles. The road map of the project shows that we are
+now working on the final \emph{beta} releases before the ``stable''
+\Package{biblatex}~1.0.
+
+Finally, \Package{Amsrefs} uses a transformed \extension{bib} file,
+which is expressed as \LaTeX{} macros. (The package provides a
+\BibTeX{} style that performs the transformation, so that a \LaTeX{}
+source containing a \cmdinvoke{nocite}{*} command enables \BibTeX{} to
+produce a usable \Package{amsrefs} bibliography database.)
+
+\Package{Amsrefs} is maintained by the AMS as part of its author
+support programme,
+\begin{ctanrefs}
+\item[amsrefs.sty]\CTANref{amsrefs}
+\item[biber]\CTANref{biber}
+\item[biblatex.sty]\CTANref{biblatex}
+\item[bibtex8]\CTANref{bibtex8}
+\item[\nothtml{\rmfamily}biblatex contributions]\CTANref{biblatex-contrib}
+\item[\nothtml{\rmfamily}CrossTeX]\CTANref{crosstex}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-support.tex b/help/uk-tex-faq/faq-support.tex
new file mode 100644
index 0000000000..1a08d1865c
--- /dev/null
+++ b/help/uk-tex-faq/faq-support.tex
@@ -0,0 +1,188 @@
+% $Id: faq-support.tex,v 1.9 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Support Packages for \TeX{}}
+
+\Question[Q-xfigetc]{\AllTeX{}-friendly drawing packages}
+\AliasQuestion{Q-xfig}
+\AliasQuestion{Q-figetc}
+
+\ProgName{(X)Fig} is a menu driven tool that allows you to
+draw objects on the screen of an \acro{X} workstation; \ProgName{transfig}
+is a set of tools which translate the code \ProgName{fig}. The list
+of export formats is very long, and includes \MF{} and \MP{},
+Encapsulated \PS{} and \acro{PDF}, as well as combinations that wrap
+a graphics format in a \LaTeX{} import file, which may include
+\LaTeX{} commands to place text (compiled by \LaTeX{} itself) as
+labels, etc., in the figures.
+
+There's no explicit port of \ProgName{xfig} to windows (although it is
+believed to work under \ProgName{cygwin} with its X-windows system).
+However, the program % ! line break
+\href{http://tams-www.informatik.uni-hamburg.de/applets/jfig/}{\ProgName{jfig}}
+is thought by many to be an acceptable substitute, written in Java.
+
+\ProgName{Asymptote} is a widely-praised development of the \MP{}
+language, which can draw 2D or 3D diagrams, and can also label
+diagrams with \LaTeX{} text; copious documentation is available via
+\href{http://asymptote.sourceforge.net}{\ProgName{asymptote}'s web site}.
+\begin{ctanrefs}
+\item[asymptote]\CTANref{asymptote}
+\item[xfig]\CTANref{xfig}
+\item[transfig]\CTANref{transfig}
+\end{ctanrefs}
+\LastEdit{2011-05-02}
+
+\Question[Q-texcad]{\TeX{}\acro{CAD}, a drawing package for \LaTeX{}}
+
+\TeX{}\acro{CAD} is a program for the \acro{PC} which enables the user to draw diagrams
+on screen using a mouse or arrow keys, with an on-screen menu of available
+picture-elements. Its output is code for the \LaTeX{}
+\environment{picture} environment.
+Optionally, it can be set to include lines at all angles using
+the em\TeX{} driver-family
+\htmlignore
+(\Qref*{\csx{special}s}{Q-specials}).
+\endhtmlignore
+\begin{htmlversion}
+\Qref{\csx{special}s}{Q-specials}.
+\end{htmlversion}
+\TeX{}\acro{CAD} is part of the em\TeX{} distribution.
+
+A Unix port of the program (\ProgName{xtexcad}) has been made.
+\begin{ctanrefs}
+\item[emtex]\CTANref{emtex}
+\item[xtexcad]\CTANref{xtexcad}
+\end{ctanrefs}
+
+\Question[Q-spell]{Spelling checkers for work with \TeX{}}
+
+`Traditional' approaches to the problem (of checking your spelling) were
+designed to work with a plain text file; in our case, we have an \alltex{}
+source. For the user, this is a simple-to-understand way to do the
+job; but for the spell-checker programmer, it requires heuristic (and
+hence fallible) analysis of \alltex{} macros and so on. The
+alternative, of viewing the text \emph{after} \alltex{} has processed
+the results, is covered below.
+
+The user of an \Qref*{shell/editor}{Q-editors} will usually find it
+embeds a spelling checker. For command-line use, there are several
+choices, depending on the system you're using.
+
+For Unix, \ProgName{ispell} was long the program of choice; it is well
+integrated with \ProgName{emacs}, and deals with some \TeX{} syntax.
+However, it has more-or-less been replaced everywhere, by
+\ProgName{aspell}, which was designed as a successor, and certainly
+performs better on most metrics; there remains some question as to its
+performance with \AllTeX{} sources. The most recent offering (which
+is widely used in other open-source software projects) is
+\begin{hyperversion}
+ \href{http://hunspell.sourceforge.net/}{\ProgName{Hunspell}}.
+\end{hyperversion}
+\begin{flatversion}
+ Hunspell~(see \URL{http://hunspell.sourceforge.net/}).
+\end{flatversion}
+\ProgName{Hunspell} is available for other architectures, too; a web
+search shows versions available for Windows, at least.
+
+For the Macintosh, \ProgName{Excalibur} has long been used; its
+distribution comes with dictionaries for several languages.
+\ProgName{Hunspell} (see above) is actually part of OS X from version 10.6.
+
+The \acro{VMS} Pascal program \ProgName{spell} makes special cases of
+some important features of \LaTeX{} syntax.
+
+For \MSDOS{}, there are several programs. \ProgName{Amspell} can be
+called from within an editor, and \ProgName{jspell} is an extended
+version of \ProgName{ispell}.
+
+An alternative approach takes \alltex{} output, and checks that. A
+straightforward approach is to produce \acro{PDF} output, and process
+it with \ProgName{pdftotext}, using any plain text checker on the
+result (the checkers listed above all work in this r\^ole). For this
+to work reasonably well, the user should disable hyphenation before
+making the \acro{PDF} output.
+
+The (experimental) \luatex{}/\latex{} package \Package{spelling} goes
+one step further: it uses \ProgName{lua} code to extract words
+\emph{while typesetting is going on}, but before hyphenation is
+applied. Each word is looked up in a list of known bad spellings, and
+the word highlighted if it appears there. In parallel, a text file is
+created, which can be processed by a `normal' spelling checker to
+produce a revised ``bad spelling'' list. (The package documentation
+shows the end result; it includes words such as `spellling', which are
+duly highlighted.)
+\begin{ctanrefs}
+\item[4spell]\CTANref{4spell}
+\item[amspell]\CTANref{amspell}
+\item[aspell]Browse \CTANref{aspell}~--- choose just those language
+ dictionaries (under subdirectory \File{dict/}) that you need.
+\item[excalibur]\CTANref{Excalibur}
+\item[ispell]\CTANref{ispell}
+\item[jspell]\CTANref{jspell}
+\item[spelling.sty]\CTANref{spelling}
+\item[\nothtml{\bgroup\rmfamily}\acro{VMS}\nothtml{\egroup} spell]%
+ \CTANref{vmspell}
+\item[winedt]\CTANref{winedt}
+\end{ctanrefs}
+\LastEdit{2013-10-02}
+
+\Question[Q-wordcount]{How many words have you written?}
+
+One often has to submit a document (e.g., a paper or a dissertation)
+under some sort of constraint about its size. Sensible people set a
+constraint in terms of numbers of pages, but there are some that
+persist in limiting the numbers of words you type.
+
+A simple solution to the requirement can be achieved following a
+simple observation: the powers that be are unlikely to count all the
+words of a document submitted to them. Therefore, a statistical
+method can be employed: find how many words there are on a full page;
+find how many full pages there are in the document (allowing for
+displays of various sorts, this number will probably not be an
+integer); multiply the two. However, if the document to be submitted
+is to determine the success of the rest of one's life, it takes a
+brave person to thumb their nose at authority quite so
+comprehensively\dots{}
+
+The simplest method is to strip out the \AllTeX{} markup, and to count
+what's left. On a Unix-like system, this may be done using
+\ProgName{detex} and the built-in \ProgName{wc}:
+\begin{quote}
+\begin{verbatim}
+detex <filename> | wc -w
+\end{verbatim}
+\end{quote}
+The technique is beguilingly simple, but it's not terribly accurate
+
+The \ProgName{latexcount} script does the same sort of job, in one
+``step''; being a \ProgName{perl} script, it is in principle rather
+easily configured (see documentation inside the script).
+Several \Qref*{editors and shells}{Q-editors} offer something similar.
+
+\ProgName{TeXcount} goes a long way with heuristics for counting,
+starting from a \LaTeX{} file; the documentation is comprehensive, and
+you may try the script on-line via the % ! line break
+\begin{hyperversion}
+ \href{http://folk.uio.no/einarro/Comp/texwordcount.html}{package home page}.
+\end{hyperversion}
+\begin{flatversion}
+ package home page~(see
+ \URL{http://folk.uio.no/einarro/Comp/texwordcount.html}).
+\end{flatversion}
+
+However, even quite sophisticated stripping of \AllTeX{} markup can
+never be entirely reliable: markup itself may contribute typeset
+words, or even consume words that appear in the text.
+
+The \Package{wordcount} package
+contains a Bourne shell (i.e., typically Unix) script for running a
+\LaTeX{} file with a special piece of supporting \TeX{} code, and then
+counting word indications in the log file. This is probably as
+accurate automatic counting as you can get, if it works for you.
+\begin{ctanrefs}
+\item[detex]\CTANref{detex}
+\item[latexcount.pl]\CTANref{latexcount}
+\item[TeXcount]\CTANref{texcount}
+\item[wordcount]\CTANref{wordcount}
+\end{ctanrefs}
+
diff --git a/help/uk-tex-faq/faq-symbols.tex b/help/uk-tex-faq/faq-symbols.tex
new file mode 100644
index 0000000000..07050510f3
--- /dev/null
+++ b/help/uk-tex-faq/faq-symbols.tex
@@ -0,0 +1,613 @@
+% $Id: faq-symbols.tex,v 1.15 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{Symbols, etc.}
+
+\Question[Q-usesymb]{Using symbols}
+
+Most symbol font sets come with a package that defines commands for
+every symbol in the font. While this is convenient, it can lead to
+difficulties, particularly with name clashes when you load packages
+that cover fonts which duplicate symbols~--- an issue which is
+discussed in
+\begin{narrowversion}
+ \Qref[question]{}{Q-alreadydef}.
+\end{narrowversion}
+\begin{wideversion}
+ ``\Qref{symbol already defined}{Q-alreadydef}''.
+\end{wideversion}
+Some font sets (for example the related set: \FontName{FdSymbol},
+\FontName{MdSymbol} and \FontName{MnSymbol}) are huge, and the
+accompanying macros cover so many symbols that name clashes are surely
+a serious problem.
+
+The \Package{pifont} package (originally designed to use the Adobe
+\FontName{Zapf Dingbats} font) avoids this sort of problem: it requires
+you to know the font position of any symbol you want to use (the
+documentation provides font tables). The basic command is
+\cmdinvoke*{ding}{number} for a single symbol; there are commands for
+other fancier uses. \Package{Pifont} also allows you to select other
+fonts, for similar use.
+
+The \Package{yagusylo} describes itself as ``an extended version of
+\Package{pifont}, gone technicolor''. It provides all the facilities
+of \Package{pifont}, but allows you to create your own mnemonic names
+for symbols. Thus, while you can say % ! line break
+\cmdinvoke*{yagding}[family]{symbol number}[colour], you can also
+define symbol names with \csx{defdingname}, and then use them
+with \cmdinvoke*{yagding*}{symbol name} (the defined name carries the
+font family and colour specified in the arguments of
+\csx{defdingname}).
+
+\Package{Yagusylo} is somewhat complicated, but its documentation is
+clear; it is probably the best tool to use for picking and choosing
+symbols from a variety of font families.
+\begin{ctanrefs}
+\item[FdSymbol \nothtml{\rmfamily}fonts]\CTANref{fdsymbol}
+\item[MdSymbol \nothtml{\rmfamily}fonts]\CTANref{mdsymbol}
+\item[MnSymbol \nothtml{\rmfamily}fonts]\CTANref{mnsymbol}
+\item[pifont.sty]Distributed as part of \CTANref{psnfss}
+\item[yagusylo.sty]\CTANref{yagusylo}
+\end{ctanrefs}
+
+\Question[Q-numbersets]{Symbols for the number sets}
+
+Mathematicians commonly use special lettering for the real numbers and
+other standard number sets. Traditionally these were typeset in bold.
+In the ordinary course of events, but mathematicians do not have
+access to bold chalk, so they invented special symbols that are now
+often used for the number sets. Such symbols are known as
+``blackboard bold'' (or double-stroked) letters; in place of the heavier
+strokes of a bold font, (some) strokes of the letters are doubled.
+The minimum useful set is upper-case letters `I', `N', `R', `Q' and
+`Z'; some fonts offer a figure `1' (for a unit matrix~--- not a number
+set at all).
+
+A set of blackboard bold capitals is available in the \acro{AMS}
+\FontName{msbm} fonts (\FontName{msbm} is available at a range of
+design sizes, with names such as \FontName{msbm10}). The \acro{AMS}
+actually provides a pair of font
+families (the other is called \FontName{msam}), which offer a large number of
+mathematical symbols to supplement those provided in Knuth's fonts.
+The fonts are available in Type~1 format in
+modern distributions. Support for using the fonts under
+\LaTeX{} is available in packages \Package{amssymb} and
+\Package{amsfonts}. The font shape is a rather
+austere sans, which many people don't like (though it captures the
+essence of quickly-chalked writing rather well).
+
+The \FontName{bbold} family is set of blackboard bold fonts written in
+\MF{}. This set offers blackboard bold forms of lower-case letters;
+the font source directory also contains sources for a \LaTeX{} package
+that enables use of the fonts. The fonts are not available in Type~1 format.
+
+The \FontName{bbm} family claims to provide
+`blackboard' versions of most of the \FontName{cm} fonts~\dots{} including
+the bold and bold-extended series. Again, the fonts are designed in
+\MF{} and are not available in Type~1 format. \LaTeX{} macro support
+comes from a package by Torsten Hilbrich.
+
+The \FontName{doublestroke} family comes in just roman
+and sans shapes, at a single weight, and is available both as \MF{}
+sources and as Type~1; the font covers the uppercase latin letters,
+lowercase `h' and 'k', and the digit `1'.
+
+A document that shows the \FontName{bbm}, \FontName{bbold},
+\FontName{doublestroke} and \FontName{msbm} fonts, so that you can get
+a feel for their appearance, is available (\acro{CTAN} package
+\Package{blackboard}).
+
+The \Package{boondox} font set consists of Type~1 versions of the
+\acro{STIX} mathematics set (the originals are distributed in
+\acro{OTF} format). The set contains a font
+`BOONDOXDoubleStruck-Regular' (blackboard bold) (as well as a `bold'
+version of that.
+
+An alternative source of Type~1 fonts with blackboard bold characters
+may be found in the steadily increasing set of complete families, both
+commercial and free, that have been prepared for use with \AllTeX{}
+(see % beware line break
+\htmlonly{``}\Qref[question]{choice of outline fonts}{Q-psfchoice}\htmlonly{''}).
+Of the free sets, the \FontName{txfonts} and \FontName{pxfonts} families
+both come with replicas of \FontName{msam} and \FontName{msbm}, but
+(as noted elsewhere, there are other reasons not to use these fonts);
+revised versions of the fonts, \FontName{newtx} and \FontName{newpx}
+are better adjusted. The \FontName{mathpazo} family includes a
+``mathematically significant'' choice of blackboard bold characters, and the
+\FontName{fourier} fonts contain blackboard bold upper-case letters,
+the digit `1', and lower-case `k'.
+
+The ``lazy person's'' blackboard bold macros:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\R}{{\textsf{R}\hspace*{-0.9ex}%
+ \rule{0.15ex}{1.5ex}\hspace*{0.9ex}}}
+\newcommand{\N}{{\textsf{N}\hspace*{-1.0ex}%
+ \rule{0.15ex}{1.3ex}\hspace*{1.0ex}}}
+\newcommand{\Q}{{\textsf{Q}\hspace*{-1.1ex}%
+ \rule{0.15ex}{1.5ex}\hspace*{1.1ex}}}
+\newcommand{\C}{{\textsf{C}\hspace*{-0.9ex}%
+ \rule{0.15ex}{1.3ex}\hspace*{0.9ex}}}
+\end{verbatim}
+\end{quote}
+are almost acceptable at normal size if the surrounding text is
+\FontName{cmr10} (the position of the vertical bar can be affected by
+the surrounding font). However, they are not part of a proper maths font,
+and do not work in sub- and superscripts. As we've seen, there are
+plenty of alternatives: that mythical ``lazy'' person can inevitably
+do better than the macros, or anything similar using capital `I'
+(which looks even worse!). Voluntary \AllTeX{} effort has redefined
+the meaning of laziness (in this respect!).
+\begin{ctanrefs}
+\item[AMS support files]Distributed as part of \CTANref{amsfonts}
+\item[AMS symbol fonts]Distributed as part of \CTANref{amsfonts}
+\item[bbm fonts]\CTANref{bbm}
+\item[bbm macros]\CTANref{bbm-macros}
+\item[bbold fonts]\CTANref{bbold}
+\item[blackboard \nothtml{\rmfamily}evaluation set]\CTANref{blackboard}
+\item[doublestroke fonts]\CTANref{doublestroke}
+\item[fourier fonts]\CTANref{fourier}
+\item[mathpazo fonts]\CTANref{mathpazo}
+\item[newpx]\CTANref{newpx}
+\item[newtx]\CTANref{newtx}
+\item[pxfonts]\CTANref{pxfonts}
+\item[txfonts]\CTANref{txfonts}
+\end{ctanrefs}
+\LastEdit{2013-12-04}
+
+\Question[Q-scriptfonts]{Better script fonts for maths}
+
+The font selected by \csx{mathcal} is the only script font `built
+in'. However, there are other useful calligraphic fonts included with
+modern \TeX{} distributions.
+\begin{description}
+\item[Euler] The \Package{eucal} package (part of most sensible \TeX{}
+ distributions; the fonts are part of the \acro{AMS} font set) gives
+ a slightly curlier font than the default. The package changes the
+ font that is selected by \csx{mathcal}.
+
+ Type 1 versions of the fonts are available in the \acro{AMS} fonts
+ distribution.
+\item[mathabx] The \FontName{mathabx} bundle provides calligraphic
+ letters (in both upper and lower case); the fonts were developed in
+ MetaFont, but a version in Adobe Type 1 format is available. The
+ bundle's documentation offers a series of comparisons of its
+ calligraphic set with Computer Modern's (both regular mathematical
+ and calligraphic letters); the difference are not large.
+\item[mnsymbol] The \FontName{mnsymbol} bundle provides (among many
+ other symbols) a set of calligraphic letters, though (again) they're
+ rather similar to the default Computer Modern set.
+\item[RSFS] The \Package{mathrsfs} package uses a really fancy script
+ font (the name stands for ``Ralph Smith's Formal Script'') which is
+ already part of most modern \TeX{} distributions (Type~1 versions of
+ the font are also provided, courtesy of Taco Hoekwater). The package
+ creates a new command \csx{mathscr}.
+\item[RSFSO] The bundle \Package{rsfso} provides a less dramatically
+ oblique version of the \acro{RSFS} fonts; the result proves quite
+ pleasing~--- similar to the effect of the the (commercial) script
+ font in the Adobe Mathematical Pi collection.
+\item[Zapf Chancery] is the standard \PS{} calligraphic font. There
+ is no package but you can easily make it available by means of the
+ command
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+ {m}{it}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}{m}{it}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+ in your preamble. You may find the font rather too big; if so, you
+ can use a scaled version of it like this:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\DeclareFontFamily{OT1}{pzc}{}
+\DeclareFontShape{OT1}{pzc}{m}{it}%
+ {<-> s * [0.900] pzcmi7t}{}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+ {m}{it}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\DeclareFontFamily{OT1}{pzc}{}
+\DeclareFontShape{OT1}{pzc}{m}{it}{<-> s * [0.900] pzcmi7t}{}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}{m}{it}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+ Adobe Zapf Chancery (which the above examples use) is distributed in
+ any but the most basic \PS{} printers. A substantially identical
+ font (to the extent that the same metrics may be used) is
+ available from \acro{URW}, called URW Chancery L: it is distributed
+ as part of the ``URW base35'' bundle; the
+ \Package{urwchancal} package (which includes virtual fonts to tweak
+ appearance) provides for its use as a calligraphic font.
+
+ The TeX Gyre font family also includes a Chancery replacement,
+ \FontName{Chorus}; use it with \Package{tgchorus} (and ignore the
+ complaints about needing to change font shape).
+\end{description}
+Examples of the available styles are linked from the packages'
+catalogue entries.
+\begin{ctanrefs}
+\item[eucal.sty]Distributed as part of \CTANref{amsfonts}
+\item[euler fonts]Distributed as part of \CTANref{amsfonts}
+\item[mathabx \nothtml{\rmfamily}as \MF{}]\CTANref{mathabx}
+\item[mathabx \nothtml{\rmfamily}in Type 1 format]\CTANref{mathabx-type1}
+\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}[mathrsfs]
+\item[mnsymbol \nothtml{\rmfamily}fonts]\CTANref{mnsymbol}
+\item[rsfs \nothtml{\rmfamily}fonts]\CTANref{rsfs}
+\item[rsfso \nothtml{\rmfamily}fonts]\CTANref{rsfso}
+\item[Script font examples]\CTANref{mathscript}
+\item[TeX Gyre Chorus font family]Distributed as part of \CTANref{tex-gyre}[tex-gyre-chorus]
+\item[urwchancal]\CTANref{urwchancal}[urwchancal]
+\item[URW Chancery L]Distributed as part of \CTANref{urw-base35}
+\end{ctanrefs}
+\LastEdit{2011-08-17}
+
+\Question[Q-boldgreek]{Setting bold Greek letters in \LaTeX{} maths}
+
+The issue here is complicated by the fact that \csx{mathbf} (the
+command for setting bold \emph{text} in \TeX{} maths) affects a select
+few mathematical `symbols' (the uppercase Greek letters).
+
+In the default configuration, lower-case Greek letters behave
+differently from upper-case Greek letters (the lower-case greek
+letters are in the maths fonts, while the upper-case letters are in
+the original (OT1-encoded) text fonts).
+
+The \plaintex{} solution \emph{does} work, in a limited way; you set a
+maths \emph{style}, before you start an equation; thus
+\begin{quote}
+\begin{verbatim}
+{\boldmath$\theta$}
+\end{verbatim}
+\end{quote}
+does the job, but \csx{boldmath} may not be used in maths mode. As a
+result, this solution requires that you embed single bold characters
+in a text box:
+\begin{quote}
+\begin{verbatim}
+$... \mbox{\boldmath$\theta$} ...$
+\end{verbatim}
+\end{quote}
+which then causes problems in superscripts, etc. With
+\Package{amsmath} loaded,
+\begin{quote}
+\begin{verbatim}
+$... \text{\boldmath$\theta$} ...$
+\end{verbatim}
+\end{quote}
+does the trick (and is less bad in regard to superscripts, etc), but
+is an unsatisfactory solution, too.
+
+These problems may be addressed by using a bold mathematics package.
+\begin{itemize}
+\item The \Package{bm} package, which is part of the \LaTeX{} tools
+ distribution, defines a command \csx{bm} which may be used anywhere
+ in maths mode.
+\item The \Package{amsbsy} package (which is part of \AMSLaTeX{})
+ defines a command \csx{boldsymbol}, which (though slightly less
+ comprehensive than \csx{bm}) covers almost all common cases.
+\end{itemize}
+
+All these solutions apply to all mathematical symbols, not merely
+Greek letters.
+\begin{ctanrefs}
+\item[bm.sty]Distributed as part of \CTANref{2etools}[bm]
+\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}[amsbsy]
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+ \CTANref{amslatex}[amsmath]
+\end{ctanrefs}
+\LastEdit{2013-06-12}
+
+\Question[Q-prinvalint]{The Principal Value Integral symbol}
+
+This symbol (an integral sign, `crossed') does not appear in any of
+the fonts ordinarily available to \AllTeX{} users, but it can be
+created by use of the following macros:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\def\Xint#1{\mathchoice
+ {\XXint\displaystyle\textstyle{#1}}%
+ {\XXint\textstyle\scriptstyle{#1}}%
+ {\XXint\scriptstyle\scriptscriptstyle{#1}}%
+ {\XXint\scriptscriptstyle\scriptscriptstyle{#1}}%
+ \!\int}
+\def\XXint#1#2#3{{\setbox0=\hbox{$#1{#2#3}{\int}$}
+ \vcenter{\hbox{$#2#3$}}\kern-.5\wd0}}
+\def\ddashint{\Xint=}
+\def\dashint{\Xint-}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\def\Xint#1{\mathchoice
+ {\XXint\displaystyle\textstyle{#1}}%
+ {\XXint\textstyle\scriptstyle{#1}}%
+ {\XXint\scriptstyle\scriptscriptstyle{#1}}%
+ {\XXint\scriptscriptstyle
+ \scriptscriptstyle{#1}}%
+ \!\int}
+\def\XXint#1#2#3{{%
+ \setbox0=\hbox{$#1{#2#3}{\int}$}
+ \vcenter{\hbox{$#2#3$}}\kern-.5\wd0}}
+\def\ddashint{\Xint=}
+\def\dashint{\Xint-}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+\csx{dashint} gives a single-dashed integral sign, \csx{ddashint} a
+double-dashed one.
+
+\Question[Q-underscore]{How to typeset an underscore character}
+
+The underscore character `\texttt{\_}' is ordinarily used in \TeX{} to
+indicate a subscript in maths mode; if you type \texttt{\_}, on its
+own, in the course of ordinary text, \TeX{} will complain. The
+``proper'' \latex{} command for underscore is \csx{textunderscore},
+but the \latexo{} command \csx{\_} is an established alias. Even so,
+if you're writing a document which will contain a large number of
+underscore characters, the prospect of typing \csx{\_} for every one
+of them will daunt most ordinary people.
+
+Moderately skilled macro programmers can readily generate a quick hack
+to permit typing `\texttt{\_}' to mean `text underscore' (the answer in
+\begin{hyperversion}
+ ``\Qref{defining characters as macros}{Q-activechars}''
+\end{hyperversion}
+\begin{flatversion}
+ \Qref[question]{}{Q-activechars}
+\end{flatversion}
+uses this example to illustrate its techniques).
+However, the code \emph{is} somewhat tricky, and more importantly
+there are significant points where it's easy to get it wrong. There
+is therefore a package \Package{underscore} which provides a general
+solution to this requirement.
+
+There is a problem, though: \acro{OT}1 text fonts don't contain an
+underscore character, unless they're in the typewriter version of the
+encoding (used by fixed-width fonts such as \texttt{cmtt}). In place
+of such a character, \latex{} (in \acro{OT}1 encoding) uses a short rule
+for the command \csx{textunderscore}, but this poses problems
+for systems that interpret \acro{PDF}~--- for example those
+\acro{PDF}-to-voice systems used by those who find reading difficult.
+
+So either you must ensure that your underscore characters only occur
+in text set in a typewriter font, or you must use a more modern
+encoding, such as \acro{T}1, which has the same layout for every font,
+and thus an underscore in every font.
+
+A stable procedure to achieve this is:
+\begin{quote}
+\begin{verbatim}
+% (1) choose a font that is available as T1
+% for example:
+\usepackage{lmodern}
+
+% (2) specify encoding
+\usepackage[T1]{fontenc}
+
+% (3) load symbol definitions
+\usepackage{textcomp}
+\end{verbatim}
+\end{quote}
+which will provide a command \csx{textunderscore} which robustly
+selects the right character. The \Package{underscore} package,
+mentioned above, will use this command.
+\begin{ctanrefs}
+\item[underscore.sty]\CTANref{underscore}
+\end{ctanrefs}
+\LastEdit{2011-08-17}
+
+\Question[Q-atsign]{How to type an `@' sign?}
+
+Long ago, some packages used to use the `@' sign as a special
+character, so that special measures were needed to type it. While
+those packages are still in principle available, few people use them,
+and those that do use them have ready access to rather good
+documentation.
+
+Ordinary people (such as the author of this \acro{FAQ}) need only type
+`@'.
+\LastEdit{2011-08-16}
+
+\Question[Q-euro]{Typesetting the Euro sign}
+
+The European currency ``Euro'' (\texteuro {}) is represented by a symbol
+of somewhat dubious design, but it's an important currency and
+\AllTeX{} users need to typeset it. When the currency first appeared,
+typesetting it was a serious problem for \AllTeX{} users; things are
+easier now (most fonts have some way of providing a Euro sign), but
+this answer provides a summary of methods ``just in case''.
+
+Note that the Commission of the European Community at first deemed
+that the Euro symbol should always be set in a sans-serif font;
+fortunately, this eccentric ruling has now been rescinded, and one may
+apply best typesetting efforts to making it appear at least slightly
+``respectable'' (typographically).
+
+The \acro{TS}1-encoded \acro{TC} fonts provided as part of the \acro{EC} font
+distribution provide Euro glyphs. The fonts are called Text Companion
+(\acro{TC}) fonts, and offer the same range
+of faces as do the \acro{EC} fonts themselves. The
+\Package{textcomp} package provides a \csx{texteuro} command for
+accessing the symbol, which selects a symbol to match the surrounding
+text. The design of the symbol in the \acro{TC} fonts is not
+universally loved\dots{}
+Nevertheless, use the \acro{TC} font version of the symbol if you are
+producing documents using Knuth's Computer Modern Fonts.
+
+The each of the \Package{latin9} and \Package{latin10} input encoding
+definitions for the \Package{inputenc} package has a euro character
+defined (character position 164, occupied in other \acro{ISO} Latin
+character sets by the ``currency symbol'' \textcurrency {}, which
+ordinary people seldom see except in character-set listings\dots{}).
+The \acro{TC} encoding file offers the command \csx{texteuro} for the
+character; that command is (probably) \emph{only} available from the
+\Package{textcomp} package.
+
+Use of the \acro{TC} encoding character may therefore made via
+\csx{texteuro} or via the Latin-9 or Latin-10 character in ordinary
+text.
+
+Note that there is a Microsoft code page position (128), too, and that has
+been added to \Package{inputenc} tables for \acro{CP}1252 and
+\acro{CP}1257. (There's another position in \acro{CP}858, which has
+it in place of ``dotless i'' in \acro{CP850}; the standardisation of
+these things remains within Microsoft, so one can never tell what will
+come next\dots{})
+
+Outline fonts which contain nothing but Euro symbols are available
+(free) from
+\href{ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe}{Adobe}\nobreakspace---
+the file is packaged as a \ProgName{Windows} self-extracting
+executable, but it may be decoded as a \extension{zip} format archive
+on other operating systems.
+The \Package{euro} bundle contains metrics, \ProgName{dvips} map
+files, and macros (for \plaintex{} and \LaTeX{}), for using these
+fonts in documents. \LaTeX{} users will find two packages in the
+bundle: \Package{eurosans} only offers the sans-serif version (to
+conform with the obsolete ruling about sans-serif-only symbols; the
+package provides the
+command \csx{euro}), whereas \Package{europs} matches the Euro symbol
+with the surrounding text (providing the command \csx{EUR}). To use
+either package
+with the \Package{latin9} encoding, you need to define \csx{texteuro}
+as an alias for the euro command the package defines.
+
+The Adobe fonts are probably the best bet for use in non-Computer
+Modern environments. They are apparently designed to fit with Adobe
+Times, Helvetica and Courier, but can probably fit with a wider range
+of modern fonts.
+
+The \Package{eurofont} package provides a compendious analysis of the
+``problem of the euro symbol'' in its documentation, and offers macros
+for configuring the source of the glyphs to be used; however, it seems
+rather large for everyday use.
+
+The \Package{euro-ce} bundle is a rather pleasing \MF{}-only design
+providing Euro symbols in a number of shapes. The file
+\File{euro-ce.tex}, in the distribution, offers hints as to how a
+\plaintex{} user might make use of the fonts.
+
+Euro symbols are found in several other places, which we list here for
+completeness.
+
+The \Package{marvosym} font contains a Euro symbol (in a number of
+typographic styles), among many other good things; the font is
+available in both Adobe Type 1 and TrueType formats.
+
+Other \MF{}-based bundles containing Euro symbols are to be found in
+\Package{china2e} (whose primary aim is Chinese dates and suchlike
+matters) and the \Package{eurosym} fonts.
+\begin{ctanrefs}
+\item[china2e bundle]\CTANref{china2e}
+\item[EC fonts]\CTANref{ec}
+\item[euro fonts]\CTANref{euro-fonts}
+\item[euro-ce fonts]\CTANref{euro-ce}
+\item[eurofont.sty]\CTANref{eurofont}
+\item[eurosym fonts]\CTANref{eurosym}
+\item[marvosym fonts]\CTANref{marvosym-fonts}
+\item[textcomp.sty]Part of the \LaTeX{} distribution.
+\end{ctanrefs}
+\LastEdit{2011-11-21}
+
+\Question[Q-tradesyms]{How to get copyright, trademark, etc.}
+
+The ``\nothtml{Comprehensive symbol list'' (}% beware line break
+\Qref{Comprehensive symbol list}{Q-symbols}\latexhtml{)}{''}, lists
+the symbol commands \csx{textcopyright},
+\csx{textregistered} and \csx{texttrademark}, which are available in
+\acro{TS}1-encoded fonts, and which are enabled using the
+\Package{textcomp} package.
+
+In fact, all three commands are enabled in default \LaTeX{}, but the
+glyphs you get aren't terribly beautiful. In particular,
+\csx{textregistered} behaves oddly when included in bold text (for
+example, in a section heading), since it is composed of a small-caps
+letter, which typically degrades to a regular shape letter when asked
+to set in a bold font. This means that the glyph becomes a circled
+``r'', whereas the proper symbol is a circled ``R''.
+
+This effect is of course avoided by use of \Package{textcomp}.
+
+Another problem arises if you want \csx{textregistered} in a
+superscript position (to look similar to \csx{texttrademark}).
+Using a maths-mode superscript to do this provokes lots of pointless
+errors: you \emph{must} use
+\begin{quote}
+\begin{verbatim}
+\textsuperscript{\textregistered}
+\end{verbatim}
+\end{quote}
+
+\Question[Q-osf]{Using ``old-style'' figures}
+
+These numbers are also called medieval or lowercase figures and their
+use is mostly font-specific. Terminology is confusing since the
+lining figures (which are now the default) are a relatively recent
+development (19th century) and before they arrived, oldstyle figures
+were the norm, even when setting mathematics. (An example is Thomas
+Harriot's \emph{Artis Analyticae Praxis} published in 1631). In a
+typical old style 3, 4, 5, 7 and 9 have descenders and 6 and 8 ascend
+above the x-height; sometimes 2 will also ascend (this last seems to
+be a variation associated with French typography).
+
+\LaTeX{} provides a command \cmdinvoke*{oldstylenums}{digits}, which
+by default uses an old-style set embedded in Knuth's `math italic'
+font. The command is only sensitive to `bold' of the font style of
+surrounding text: glyphs (for this command) are only available to
+match the normal medium and bold (i.e., bold-extended) weights of the
+Computer Modern Roman fonts.
+
+The \Package{textcomp} package changes \csx{oldstylenums} to use the
+glyphs in the Text Companion fonts (\LaTeX{} \acro{TS}1 encoding) when
+in text mode, and also makes them available using the macros of the
+form \csx{text<number>oldstyle}, e.g., \csx{textzerooldstyle}.
+(Of course, not all font families can provide this facility.)
+
+Some font packages (e.g., \Package{mathpazo}) make old-style figures
+available and provide explicit support for making them the default:
+\cmdinvoke{usepackage}[osf]{mathpazo} selects a form where digits are
+always old-style in text. The \Package{fontinst} package will
+automatically generate ``old-style versions'' of commercial Adobe Type
+1 font families for which ``expert'' sets are available.
+
+It's also possible to make virtual fonts, that offer old-style digits,
+from existing font packages. The \FontName{cmolddig} bundle provides
+a such a virtual version of Knuth's originals, and the \FontName{eco}
+or \FontName{hfoldsty} bundles both provide versions of the \acro{EC}
+fonts. The \FontName{lm} family offers old-style figures to OpenType
+users (see below), but we have no stable mapping for \FontName{lm}
+with old-style digits from the Adobe Type 1 versions of the fonts.
+
+Originally, oldstyle figures were only to be found the expert sets of
+commercial fonts, but now they are increasingly widely available. An
+example is Matthew Carter's Georgia font, which has old-style figures
+as its normal form (the font was created for inclusion with certain
+Microsoft products and is intended for on-screen viewing).
+
+OpenType fonts have a pair of axes for number variations~---
+proportional/tabular and lining/oldstyle selections are commonly
+available. ``Full feature access'' to OpenType fonts, making such
+options available to the \AllTeX{} user, is already supported by
+\Qref*{\xetex{}}{Q-xetex} using, for example, the \Package{fontspec}
+package. Similar support is also in the works for
+\Qref*{\LuaTeX{}}{Q-luatex}.
+\begin{ctanrefs}
+\item[boondox \nothtml{\rmfamily}fonts]\CTANref{boondox}
+\item[cmolddig \nothtml{\rmfamily}fonts]\CTANref{cmolddig}
+\item[eco \nothtml{\rmfamily}fonts]\CTANref{eco}
+\item[fontinst]\CTANref{fontinst}
+\item[fontspec.sty]\CTANref{fontspec}
+\item[mathpazo \nothtml{\rmfamily}fonts]\CTANref{mathpazo}
+\end{ctanrefs}
+\LastEdit{2013-12-04}
diff --git a/help/uk-tex-faq/faq-t-g-wr.tex b/help/uk-tex-faq/faq-t-g-wr.tex
new file mode 100644
index 0000000000..48e5a1af7f
--- /dev/null
+++ b/help/uk-tex-faq/faq-t-g-wr.tex
@@ -0,0 +1,467 @@
+% $Id: faq-t-g-wr.tex,v 1.15 2014/01/22 17:27:56 rf10 Exp $
+
+\section{Things are Going Wrong\dots{}}
+
+\subsection{Getting things to fit}
+\Question[Q-enlarge]{Enlarging \TeX{}}
+
+The \TeX{} error message `capacity exceeded' covers a multitude of
+problems. What has been exhausted is listed in brackets after the
+error message itself, as in:
+\begin{quote}
+\begin{verbatim}
+! TeX capacity exceeded, sorry
+... [main memory size=263001].
+\end{verbatim}
+\end{quote}
+Most of the time this error can be fixed
+\emph{without} enlarging \TeX{}. The most common causes are unmatched braces,
+extra-long lines, and poorly-written macros. Extra-long lines are
+often introduced when files are transferred incorrectly between
+operating systems, and line-endings are not preserved properly (the
+tell-tale sign of an extra-long line error is the complaint
+that the `|buf_size|' has overflowed).
+
+If you really need to extend your \TeX{}'s capacity, the proper method
+depends on your installation. There is no need (with modern \TeX{}
+implementations) to change the defaults in Knuth's \acro{WEB} source;
+but if you do need to do so, use a change file to modify the values set in
+module 11, recompile your \TeX{} and regenerate all format files.
+
+Modern implementations allow the sizes of the various bits of \TeX{}'s
+memory to be changed semi-dynamically. Some (such as em\TeX{}) allow
+the memory parameters to be changed in command-line switches when
+\TeX{} is started; most frequently, a configuration file is read which
+specifies the size of the memory. On \ProgName{web2c}-based systems,
+this file is called \File{texmf.cnf}: see the documentation that comes
+with the distribution for other implementations. Almost invariably,
+after such a change, the format files need to be regenerated after
+changing the memory parameters.
+
+\Question[Q-usepictex]{Why can't I load \pictex{}?}
+
+\pictex{} is a resource hog; fortunately, most modern \TeX{}
+implementations offer generous amounts of space, and most modern
+computers are pretty fast, so users aren't too badly affected by its
+performance.
+
+However, \pictex{} has the further unfortunate tendency to fill up
+\TeX{}'s fixed-size arrays~--- notably the array of 256 `dimension'
+registers. This is a particular problem when you're using
+\File{pictex.sty} with \LaTeX{} and some other packages that also need
+dimension registers. When this happens, you will see the \TeX{} error
+message:
+\begin{quote}
+\begin{verbatim}
+! No room for a new \dimen.
+\end{verbatim}
+\end{quote}
+There is nothing that can directly be done about this error: you
+can't extend the number of available \csx{dimen} registers without
+extending \TeX{} itself.
+\begin{wideversion} % hyper
+ \Qref{Omega}{Q-omegaleph} and \Qref{\eTeX{}}{Q-etex} both do this.
+\end{wideversion}
+\begin{narrowversion}
+ \ensuremath{\Omega} and \eTeX{}~---
+ \Qref[see questions]{}{Q-omegaleph}
+ \Qref[and]{}{Q-etex} respectively~--- both do this.
+\end{narrowversion}
+
+It's actually quite practical (with most modern distributions) to use
+\eTeX{}'s extended register set: use package \Package{etex} (which
+comes with \eTeX{} distributions) and the allocation mechanism is
+altered to cope with the larger register set: \pictex{} will now load.
+
+If you're in some situation where you can't use \eTeX{}, you need to change
+\pictex{}; unfortunately \pictex{}'s author is no longer active in the
+\TeX{} world, so one must resort to patching. There are two solutions
+available.
+
+The \CONTeXT{} module \File{m-pictex.tex} (for \plaintex{} and
+variants) or the corresponding \LaTeX{} \Package{m-pictex} package provide
+an ingenious solution to the problem based on hacking the code of
+\csx{newdimen} itself.
+
+Alternatively, Andreas Schrell's \Package{pictexwd} and related
+packages replace \pictex{} with a version that uses 33 fewer
+\csx{dimen} registers; so use \Package{pictexwd} in place of
+\Package{pictex} (either as a \LaTeX{} package, or as a file to read
+into \plaintex{}).
+
+And how does one use \pictex{} anyway, given that the
+manual is so \Qref*{hard to come by}{Q-docpictex}?
+Fortunately for us all, the \ProgName{MathsPic}
+system may be used to translate a somewhat different language into
+\pictex{} commands; and the \ProgName{MathsPic} manual is free (and
+part of the distribution). \ProgName{MathsPic} is available either as
+a \ProgName{Basic} program for \acro{DOS}, or as a \ProgName{Perl}
+program for other systems (including Windows, nowadays).
+\begin{ctanrefs}
+\item[etex.sty]\CTANref{etex-pkg}
+\item[m-pictex.sty]Distributed as part of \CTANref{context-tmf}
+\item[m-pictex.tex]Distributed as part of \CTANref{context-tmf}
+\item[MathsPic]\CTANref{mathspic}
+\item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon}[pictexwd]
+\end{ctanrefs}
+\LastEdit{2014-01-22}
+
+\subsection{Making things stay where you want them}
+
+\Question[Q-floats]{Moving tables and figures in \LaTeX{}}
+
+Tables and figures have a tendency to surprise, by \emph{floating}
+away from where they were specified to appear. This is in fact
+perfectly ordinary document design; any professional typesetting
+package will float figures and tables to where they'll fit without
+violating the certain typographic rules. Even if you use the
+placement specifier~''\texttt{h}'' (for `here'), the figure or table
+will not be
+printed `here' if doing so would break the rules; the rules themselves
+are pretty simple, and are given on page~198, section~C.9 of the
+\LaTeX{} manual. In the worst case, \LaTeX{}'s rules can cause the
+floating items to pile up to the extent that you get an error message
+saying ``\Qref*{Too many unprocessed floats}{Q-tmupfl}''.
+What follows is a simple checklist of things to do to solve these
+problems (the checklist talks throughout about figures, but applies
+equally well to tables, or to ``non-standard'' floats defined by the
+\Package{float} or other packages).
+\begin{itemize}
+\item Do your figures need to float at all? If not, look at the
+ recommendations for ``\Qref*{non-floating floats}{Q-figurehere}''
+\item Are the placement parameters on your figures right? The
+ default (``\texttt{tbp}'') is usually satisfactory, but you can
+ reasonably change it (for example, to add an ``\texttt{h}'').
+ Whatever you do, \emph{don't}
+ omit the ``\texttt{p}'': doing so could cause \LaTeX{} to believe that if you
+ can't have your figure \emph{here}, you don't want it
+ \emph{anywhere}. (\LaTeX{} does try to avoid being confused in
+ this way\dots{})
+\item \LaTeX{}'s own float placement parameters could be preventing
+ placements that seem entirely ``reasonable'' to you~--- they're
+ notoriously rather conservative. To encourage \LaTeX{} not to move
+ your figure, you may need to loosen its demands. (The most important
+ ones are the ratio of text to float on a given page, but it's
+ sensible to have a fixed set that changes the whole lot, to meet
+ every eventuality.)
+\begin{verbatim}
+\renewcommand{\topfraction}{.85}
+\renewcommand{\bottomfraction}{.7}
+\renewcommand{\textfraction}{.15}
+\renewcommand{\floatpagefraction}{.66}
+\renewcommand{\dbltopfraction}{.66}
+\renewcommand{\dblfloatpagefraction}{.66}
+\setcounter{topnumber}{9}
+\setcounter{bottomnumber}{9}
+\setcounter{totalnumber}{20}
+\setcounter{dbltopnumber}{9}
+\end{verbatim}
+ The meanings of these
+ parameters are described on pages~199--200, section~C.9 of the
+ \LaTeX{} manual.
+\item Are there places in your document where you could `naturally'
+ put a \csx{clearpage} command? If so, do: the backlog of floats is
+ cleared after a \csx{clearpage}. (Note that the \csx{chapter}
+ command in the standard \Class{book} and \Class{report} classes
+ implicitly executes \csx{clearpage}, so your floats can't wander past
+ the end of a chapter.)
+\item Try the \Package{placeins} package: it defines a
+ \csx{FloatBarrier} command beyond which floats may not pass. A
+ package option allows you to declare that floats may not pass a
+ \csx{section} command, but you can place \csx{FloatBarrier}s wherever
+ you choose.
+\item If you are bothered by floats appearing at the top of the page
+ (before they are specified in your text), try the \Package{flafter}
+ package, which avoids this problem by insisting that floats should
+ always appear after their definition.
+\item Have a look at the \LaTeXe{} \Package{afterpage} package.
+ Its documentation gives as an example the idea
+ of putting \csx{clearpage} \emph{after} the current page (where it
+ will clear the backlog, but not cause an ugly gap in your text), but
+ also admits that the package is somewhat fragile. Use it as a last
+ resort if the other possibilities below don't help.
+\item If you would actually \emph{like} great blocks of floats at the
+ end of each of your chapters, try the \Package{morefloats} package;
+ this allows you to increase the number of floating inserts that \LaTeX{}
+ can handle at one time (from its original value of~18, in
+ \LaTeXe{}). Note that, even with \etex{}'s greater supply of
+ registers, there is still a modest limit on the total number of
+ floating inserts (\etex{} increases the total number of registers
+ available, but inserts don't work if they are constructed from
+ registers in the extended range).
+
+ Caveat: if you are using \Package{etex} to increase the number of
+ registers available, you need to ``reserve'' some inserts for
+ \Package{morefloats}: something like:
+ \begin{quote}
+\begin{verbatim}
+\usepackage{etex}
+\reserveinserts{18}
+\usepackage{morefloats}
+\end{verbatim}
+ \end{quote}
+\item If you actually \emph{wanted} all your figures to float to the
+ end (\emph{e.g}., for submitting a draft copy of a paper), don't
+ rely on \LaTeX{}'s mechanism: get the \Package{endfloat} package to do
+ the job for you.
+\end{itemize}
+\begin{ctanrefs}
+\item[afterpage.sty]Distributed as part of \CTANref{2etools}[afterpage]
+\item[endfloat.sty]\CTANref{endfloat}
+\item[etex.sty]\CTANref{etex-pkg}
+\item[flafter.sty]Part of the \LaTeX{} distribution
+\item[float.sty]\CTANref{float}
+\item[morefloats.sty]\CTANref{morefloats}
+\item[placeins.sty]\CTANref{placeins}
+\end{ctanrefs}
+
+\Question[Q-underline]{Underlined text won't break}
+
+Knuth made no provision for underlining text: he took the view that
+underlining is not a typesetting operation, but rather one that
+provides emphasis on typewriters, which typically offer but one
+typeface. The corresponding technique in typeset text is to switch
+from upright to italic text (or vice-versa): the \LaTeX{} command
+\csx{emph} does just that to its argument.
+
+Nevertheless, typographically illiterate people (such as those that
+specify double-spaced
+\nothtml{thesis styles~--- }\Qref{thesis styles}{Q-linespace})
+continue to require underlining of us, so \LaTeX{} as distributed
+defines an \csx{underline} command that applies the mathematical
+`underbar' operation to text. This technique is not entirely
+satisfactory, however: the text gets stuck into a box, and won't break
+at line end.
+
+Two packages are available that solve this problem. The
+\Package{ulem} package redefines the
+\csx{emph} command to underline its argument; the underlined text thus
+produced behaves as ordinary emphasised text, and will break over the
+end of a line. (The package is capable of other peculiar effects,
+too: read its documentation.)
+The \Package{soul} package defines an \csx{ul} command (after which the
+package is, in part, named) that underlines running text.
+
+Beware of \Package{ulem}'s default behaviour, which is to convert the
+\csx{emph} command into an underlining command; this can be avoided by
+loading the package with:
+\begin{quote}
+\begin{verbatim}
+\usepackage[normalem]{ulem}
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[ulem.sty]\CTANref{ulem}
+\item[soul.sty]\CTANref{soul}
+\end{ctanrefs}
+
+\Question[Q-widows]{Controlling widows and orphans}
+
+Widows (the last line of a paragraph at the start of a page) and
+orphans (the first line of paragraph at the end of a page) interrupt
+the reader's flow, and are generally considered ``bad form'';
+\AllTeX{} takes some precautions to avoid them, but completely
+automatic prevention is often impossible. If you are typesetting your
+own text, consider whether you can bring yourself to change the
+wording slightly so that the page break will fall differently.
+
+The \AllTeX{} page maker, when forming a page, takes account of variables
+\csx{widowpenalty} and \csx{clubpenalty} (which relates to orphans!).
+These penalties are usually set to the moderate value of \texttt{150}; this
+offers mild discouragement of bad breaks. You can increase the values
+by saying (for example) \csx{widowpenalty}\texttt{=500}; however, vertical
+lists (such as pages are made of) typically have rather little
+stretchability or shrinkability, so if the page maker has to balance
+the effect of stretching the unstretchable and being penalised, the
+penalty will seldom win. Therefore, for typical layouts, there are
+only two sensible settings for the penalties: finite (150 or 500, it
+doesn't matter which) to allow widows and orphans, and infinite (10000
+or greater) to forbid them.
+
+The problem can be avoided by allowing the pagemaker to run pages
+short, by using the \csx{raggedbottom} directive; however, many
+publishers insist on the default \csx{flushbottom}; it is seldom
+acceptable to introduce stretchability into the vertical list, except
+at points (such as section headings) where the document design
+explicitly permits it.
+
+Once you've exhausted the automatic measures, and have a final draft
+you want to ``polish'', you should proceed to manual measures. To
+get rid of an orphan is simple: precede the paragraph with
+\csx{clearpage} and the paragraph can't start in the wrong place.
+
+Getting rid of a widow can be more tricky. Options are
+\begin{itemize}
+\item If the previous page contains a long paragraph with a short last
+ line, it may be possible to set it `tight': write
+ \csx{looseness}\texttt{=-1} immediately after the last word of the
+ paragraph.
+\item If that doesn't work, adjusting the page size, using
+ \cmdinvoke{enlargethispage}{\csx{baselineskip}} to `add a line' to
+ the page, which may have the effect of getting the whole paragraph
+ on one page.
+\item Reducing the size of the page by
+ \cmdinvoke{enlargethispage}{-\csx{baselineskip}} may produce a
+ (more-or-less) acceptable ``two-line widow''.
+\end{itemize}
+Note that \csx{looseness}\texttt{=1} (which should increase the line
+length by one) seldom has the right effect~--- the looser paragraph
+typically has a one-word final line, which doesn't look much better
+than the original widow.
+
+\subsection{Things have ``gone away''}
+
+\Question[Q-oldfontnames]{Old \LaTeX{} font references such as \csx{tenrm}}
+
+\LaTeXo{} defined a large set of commands for access to the fonts
+that it had built in to itself. For example, \FontName{cmr} might
+appear as \csx{fivrm}, \csx{sixrm}, \csx{sevrm},
+\csx{egtrm}, \csx{ninrm}, \csx{tenrm}, \csx{elvrm}, \csx{twlrm},
+\csx{frtnrm}, \csx{svtnrm}, \csx{twtyrm} and \csx{twfvrm}, according
+to the size it's being typeset at.
+These commands were never documented, but certain packages
+nevertheless used them to achieve effects they needed.
+
+Since the commands weren't public, they weren't included in \LaTeXe{};
+to use the unconverted \LaTeXo{} packages under \LaTeXe{}, you need
+also to include the \Package{rawfonts} package (which is part of the
+\LaTeXe{} distribution).
+
+\Question[Q-misssymb]{Missing symbol commands}
+
+You're processing an old document, and some symbol commands such as
+\csx{Box} and \csx{lhd} appear no longer to exist. These commands were
+present in the core of \LaTeXo{}, but are not in current \LaTeX{}.
+They are available in the \Package{latexsym} package (which is part of
+the \LaTeX{} distribution), and in the \Package{amsfonts} package
+(which is part of the \acro{AMS} distribution, and requires \acro{AMS}
+symbol fonts).
+\begin{ctanrefs}
+\item[AMS fonts]\CTANref{amsfonts}
+\end{ctanrefs}
+
+\Question[Q-msxy]{Where are the \texttt{msx} and \texttt{msy} fonts?}
+
+The \FontName{msx} and \FontName{msy} fonts were designed by the
+American Mathematical Society in the very early days of \TeX{}, for
+use in typesetting papers for mathematical journals. They were
+designed using the `old' \MF{}, which wasn't portable and is no longer
+available; for a long time they were only available in 300dpi versions
+which only imperfectly matched modern printers. The \acro{AMS} has
+now redesigned the fonts, using the current version of \MF{}, and the
+new versions are called the \FontName{msa} and \FontName{msb}
+families.
+
+Nevertheless, \FontName{msx} and \FontName{msy} continue to turn up.
+There may, of course, still be sites that haven't got around to
+upgrading; but, even if everyone upgraded, there would still be the
+problem of old documents that specify them.
+
+If you have a \extension{tex} source that requests \FontName{msx} and
+\FontName{msy}, the best technique is to edit it so that it requests
+\FontName{msa} and \FontName{msb} (you only need to change the single
+letter in the font names).
+
+A partial re-implementation of the blackboard-bold part of the
+\FontName{msy} font (covering C, N, R, S and Z, only) is available in
+Type~1 format; if your mathematical needs only extend that far, the
+font could be a good choice.
+
+If you have a \acro{DVI} file that requests the fonts, there is a package
+of \Qref*{virtual fonts}{Q-virtualfonts} to map the old to the new series.
+\begin{ctanrefs}
+\item[msam \& msbm \nothtml{\rmfamily}fonts]Distributed as part of \CTANref{amsfonts}
+\item[msym \nothtml{\rmfamily}fonts]\CTANref{msym}
+\item[\nothtml{\rmfamily}virtual font set]\CTANref{msx2msa}
+\end{ctanrefs}
+\LastEdit{2012-03-09}
+
+%%%???%%% spell-checked to here....zzzyx
+
+\Question[Q-amfonts]{Where are the \texttt{am} fonts?}
+
+One \emph{still} occasionally comes across a request for the \FontName{am}
+series of fonts. The initials stood for `Almost [Computer] Modern',
+and they were the predecessors of the Computer Modern fonts that we
+all know and love (or hate)%
+\begin{footnoteenv}
+ The fonts acquired their label `Almost' following the realisation
+ that their first implementation in \MF{}79 still wasn't quite right;
+ Knuth's original intention had been that they were the final answer.
+\end{footnoteenv}.
+There's not a lot one can do with these
+fonts; they are (as their name implies) almost (but not quite) the
+same as the \FontName{cm} series; if you're faced with a document that requests
+them, the only reasonable approach is to edit the document to replace
+\FontName{am*} font names with \FontName{cm*}.
+
+The appearance of \acro{DVI} files that request them is sufficiently
+rare that no-one has undertaken the mammoth task of creating a
+translation of them by means of virtual fonts.
+
+You therefore have to fool the system into using \FontName{cm*} fonts
+where the original author specified \FontName{am*}.
+
+One option is the font substitutions that many
+\acro{DVI} drivers provide via their configuration file~---
+specify that every \FontName{am} font should be replaced by its
+corresponding \FontName{cm} font.
+
+Alternatively, one may try \acro{DVI} editing~--- packages
+\Package{dtl} (\acro{DVI} Text Language) and \Package{dviasm}
+(\acro{DVI} assembler) can both provide round trips from \acro{DVI} to
+text and back to \acro{DVI}. One therefore edits font names
+(throughout the text representation of the file) in the middle of that
+round trip.
+
+The \acro{DTL} text is pretty straightforward, for this purpose:
+fontnames are in single quotes at the end of lines, so:
+\begin{quote}
+ \texttt{dv2dt -o} \meta{doc.txt} \meta{doc.dvi}\\
+ (\emph{edit the \extension{txt} file})\\
+ \texttt{dt2dv -o} \meta{edited.dvi} \meta{edited.txt}
+\end{quote}
+(you have to compile the \acro{C} programs for this).
+
+\ProgName{Dviasm} is a \ProgName{Python} script; its output has font
+names in a section near the start of the document, and then dotted
+about through the body, so:
+\begin{quote}
+ \texttt{python dviasm.py -o} \meta{doc.txt} \meta{doc.dvi}\\
+ (\emph{edit the \extension{txt} file})\\
+ \texttt{python dviasm.py -o} \meta{edited.dvi} \meta{edited.txt}
+\end{quote}
+Both routes seem acceptable ways forward; it is a matter of taste
+which any particular user may choose (it's not likely that it will be
+necessary very often...).
+\begin{ctanrefs}
+\item[dviasm.py]\CTANref{dviasm}
+\item[dtl]\CTANref{dtl}
+\end{ctanrefs}
+
+\Question[Q-initex]{What's happened to \ProgName{initex}?}
+
+In the beginning, \AllTeX{} was stretching the capacity of every
+system it was ported to, so there was a premium on reducing the size
+of executables. One way of doing this was to have a separate
+executable, \ProgName{initex}, that had things in it that aren't
+needed in ordinary document runs~--- notably \csx{patterns} (which
+builds hyphenation tables), and \csx{dump} (which writes out a format).
+
+On modern systems, the size of this code is insignificant in
+comparison to the memory available, and maintaining separate programs
+has been found sufficiently error-prone that free Unix-style system
+distributions have abolished \ProgName{initex} and its friends and
+relations such as \ProgName{inipdftex} in favour of a single
+executable (that is, just \ProgName{tex} or \ProgName{pdftex}) that
+will ``do what \ProgName{initex} (or whatever) used to do'' if it
+detects the command option ``\texttt{-ini}''.
+
+The change happened with the advent of te\TeX{} version
+3.0, which appeared at the beginning of 2005. At that time,
+\texlive{} was following te\TeX{}, so that year's \texlive{}
+distribution would also have dropped \ProgName{initex}.
+
+It would appear that the equation is somewhat different for the
+\miktex{} developers, since that system continues to offer an
+\ProgName{initex} executable.
diff --git a/help/uk-tex-faq/faq-texsys.tex b/help/uk-tex-faq/faq-texsys.tex
new file mode 100644
index 0000000000..0fcc34bf65
--- /dev/null
+++ b/help/uk-tex-faq/faq-texsys.tex
@@ -0,0 +1,488 @@
+% $Id: faq-texsys.tex,v 1.17 2013/07/24 21:50:56 rf10 Exp $
+
+\section{\TeX{} Systems}
+
+\Question[Q-TeXsystems]{\AllTeX{} for different machines}
+
+We list here the free or shareware packages;
+\htmlignore
+a later \Qref{question}{Q-commercial} discusses commercial \tex{} products.
+\endhtmlignore
+\begin{htmlversion}
+ another question addresses
+ \Qref{commercial \TeX{} vendors'}{Q-commercial} products.
+\end{htmlversion}
+
+The list is provided in four answers:
+\begin{itemize}
+\item \TeX{} systems for use with
+ \Qref*{Unix and \acro{GNU} Linux systems}{Q-sysunix}
+\item \TeX{} systems for use with % ! line break
+ \Qref*{Modern Windows systems}{Q-syswin32}
+\item \TeX{} systems for use with % ! line break
+ \Qref*{Macintosh systems}{Q-sysmac}
+\item \TeX{} systems for % ! line break
+ \Qref*{Other sorts of systems}{Q-sysother}
+\end{itemize}
+
+\Question[Q-sysunix]{Unix and \acro{GNU} Linux systems}
+
+\begin{quote}
+ Note that \macosx{}, though it is also a Unix-based system, has
+ different options; users should refer to the information in
+ \Qref[question]{Mac systems}{Q-sysmac}.
+\end{quote}
+
+The \TeX{} distribution of choice, for Unix systems (including
+\acro{GNU}/Linux and most other free Unix-like systems) is \texlive{},
+which is distributed as part of the \Qref*{\TeX{} collection}{Q-CD}.
+
+\texlive{} may also be installed ``over the network''; a network
+installer is provided, and once you have a system (whether installed
+from the network or installed off-line from a disc) a manager
+(\ProgName{tlmgr}) can both keep your installation up-to-date and add
+packages you didn't install at first.
+
+\texlive{} may be run with no installation at all; the web page % ! line break
+\href{http://www.tug.org/texlive/portable.html}{\texlive{} portable usage}
+describes the options for installing \texlive{} on a memory stick for
+use on another computer, or for using the \texlive{} \acro{DVD} with
+no installation at all.
+
+\tex{}-gpc is a ``back-to-basics'' distribution of \tex{} utilities,
+\emph{only} (unlike \texlive{}, no `tailored' package bundles are
+provided). It is distributed as source, and compiles with \acro{GNU}
+Pascal, thereby coming as close as you're likely to get to Knuth's original
+distribution. It is known to work well, but the omission of \etex{}
+and \pdftex{} will rule it out of many users' choices.
+\begin{ctanrefs}
+\item[tex-gpc]\CTANref{tex-gpc}
+\item[texlive]Browse \CTANref{texlive}
+\item[texlive installer (Unix)]\CTANref{texlive-unix}
+\end{ctanrefs}
+\LastEdit{2013-07-18}
+
+\Question[Q-syswin32]{(Modern) Windows systems}
+
+Windows users nowadays have a real choice, between two excellent
+distributions, \miktex{} and \texlive{}. \texlive{} on windows has
+only in recent years been a real challenger to the long-established
+\miktex{}, and even now \miktex{} has features that \texlive{} lacks.
+Both are comprehensive
+distributions, offering all the established \tex{} variants (\tex{},
+\pdftex{}~--- both with \etex{} variants~--- as well as \xetex{} and
+\luatex{}), together with a wide range of support tools.
+
+Both \miktex{} and \texlive{} offer management tools, including the
+means of keeping an installation ``up-to-date'', by reinstalling
+packages that have been updated on \acro{CTAN} (the delay between a
+package update appearing, and it being available to the distribution
+users) can be as short as a day (and is never very long).
+
+\miktex{}, by Christian Schenk, is the longer-established of the pair,
+and has a large audience of satisfied users; \texlive{} is the
+dominant distribution in use in the world of Unix-like systems, and so
+its Windows version may be expected to appeal to those who use both
+Unix-like and Windows systems. The latest release of \miktex{}~---
+version 2.9~--- requires Windows~XP, or later (so it does not work on
+Windows~2000 or earlier).
+
+Both distributions may be used in a configuration which involves no
+installation at all. \miktex{}'s ``portable'' distribution may be
+unpacked on a memory stick, and used on any windows computer without
+making any direct use of the hard drive. The web page % ! line break
+\href{http://www.tug.org/texlive/portable.html}{\texlive{} portable usage}
+describes the options for installing \texlive{} on a memory stick, or
+for using the \texlive{} \acro{DVD} with no installation at all.
+
+Both \miktex{} and \texlive{} may be downloaded and installed, package
+by package, over the net. This is a mammoth undertaking, only to be
+undertaken by those with a good network connection (and a patient
+disposition!).
+
+A ready-to-run copy of the \miktex{} distribution,
+on \acro{DVD} may be bought via the % ! line break
+\href{http://www.miktex.org/cd/}{\miktex{} web site}. \miktex{} may
+also be installed using Pro\TeX{}t, on the % ! line break
+\Qref*{\TeX{} Collection \acro{DVD}}{Q-CD}.
+
+The \Qref*{\TeX{} Collection \acro{DVD}}{Q-CD} also provides an
+offline installer for \texlive{}.
+
+% can't find any evidence this is still available
+%
+%% \href{http://foundry.supelec.fr/projects/xemtex/}{XEm\TeX{}}, by
+%% Fabrice Popineau (he who created the excellent, but now defunct,
+%% fp\TeX{} distribution), is another integrated distribution of \tex{},
+%% \latex{}, \CONTeXT{}, \ProgName{XEmacs} and other friends for Windows.
+%% All programs have been compiled natively to take the best advantage of
+%% the Windows environment. Configuration is provided so that the
+%% resulting set of programs runs out-of-the-box, but the distribution is
+%% not actively promoted.
+%
+% this isn't right, but i'm not sure how to deal with it...
+%
+%% The (Japanese) \acro{W}32\acro{TEX} distribution was motivated by
+%% the needs of Japanese users (Japanese won't fit in a ``simple''
+%% character set like \acro{ASCII}, but \TeX{} is based on a version of
+%% \acro{ASCII}). Despite its origins, \acro{W}32\acro{TEX} is said to
+%% be a good bet for Western users, notably those whose disks are short
+%% of space: the minimum documented download is as small as
+%% 95\,MBytes. Investigate the distribution at
+%% \URL{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html}
+%
+% the url is now http://w32tex.org/current/
+
+A further (free) option is available thanks to the
+\href{http://www.cygwin.com}{CygWin bundle}, which presents a
+Unix-like environment in Windows systems (and also provides an
+X-windows server). The (now obsolete) te\TeX{} distribution is
+provided as part of the CygWin distribution, but there is a CygWin
+build of \texlive{} so you can have a current \tex{} system. \TeX{}
+under CygWin is reputedly somewhat slower than native Win32
+implementations such as \miktex{}, and of course the \tex{}
+applications behave like Unix-system applications.
+
+BaKoMa \TeX{}, by Basil Malyshev, is a comprehensive (shareware)
+distribution, which focuses on support of Acrobat. The distribution
+comes with a bunch of Type~1 fonts packaged to work with BaKoMa
+\TeX{}, which further the focus.
+\begin{ctanrefs}
+\item[bakoma]\CTANref{bakoma-tex}
+\item[miktex]\CTANref{miktex}; % ! line break so only one \CTANref on line
+ acquire \CTANref{miktex-setup} (also available from the \miktex{}
+ web site), and read installation instructions from % ! line break
+ \href{http://www.miktex.org/2.9/setup}{the \miktex{} installation page}
+\item[\nothtml{\bgroup\rmfamily}Portable\nothtml{\egroup} miktex]\CTANref{miktex-portable}
+\item[protext.exe]\CTANref{protext}
+\item[texlive]Browse \CTANref{texlive}
+\item[texlive installer (Windows)]\CTANref{texlive-windows}
+\end{ctanrefs}
+\LastEdit{2013-04-11}
+
+\Question[Q-sysmac]{Macintosh systems}
+
+The \Qref*{\TeX{} collection}{Q-CD} \acro{DVD} includes Mac\TeX{},
+which is a Mac-tailored version of \texlive{}; details may be found on
+the \href{http://tug.org/mactex}{\acro{TUG} web site}. If you don't
+have the disc, you can download the distribution from \acro{CTAN} (but
+note that it's pretty big). Mac\TeX{} is an instance of \texlive{},
+and has a Mac-tailored graphical \texlive{} manager, so that you can
+keep your distribution up-to-date.
+
+Note that installing Mac\TeX{} requires \texttt{root} privilege. This
+is a pity, since it offers several extras that aren't available via a
+standard \texlive{}, which aren't therefore available to ``ordinary
+folk'' at work. For those who don't have \texttt{root} privilege, the
+option is to install using the \texlive{} \texttt{tlinstall} utility.
+
+\href{http://www.trevorrow.com/oztex/}{Oz\TeX{}}, by Andrew Trevorrow,
+is a shareware version of \TeX{} for the Macintosh. A \acro{DVI}
+previewer and \PS{} driver are also included.
+Oz\TeX{} is a Carbon app, so will run under \macosx{} (see
+\url{http://www.trevorrow.com/oztex/ozosx.html} for details), but it
+is \emph{not} a current version: it doesn't even offer \pdftex{}. A
+mailing list is provided by \acro{TUG}: sign up via
+\url{http://tug.org/mailman/listinfo/oztex}
+
+Another partly shareware program is
+\href{http://www.kiffe.com/cmactex.html}{CMac\TeX{}}, put together by
+Tom Kiffe. CMac\TeX{} is much closer than Oz\TeX{} to the Unix \TeX{}
+model of things (it uses \ProgName{dvips}, for instance). CMac\TeX{}
+runs natively under \macosx{}; it includes a port of a version of
+\Qref*{Omega}{Q-omegaleph}.
+
+\begin{flatversion}
+ A wiki for Mac users is to be found at
+ \URL{http://mactex-wiki.tug.org/}
+\end{flatversion}
+\begin{hyperversion}
+ Further information may be available in the % ! line break
+ \href{http://mactex-wiki.tug.org/}{MacTeX wiki}.
+\end{hyperversion}
+The Mac\TeX{}-on-OS~X mailing list is another useful resource for
+users; subscribe via the
+\href{http://mactex-wiki.tug.org/wiki/index.php?title=TeX_on_Mac_OS_X_mailing_list}{list home page}
+\begin{ctanrefs}
+\item[cmactex]\CTANref{cmactex}
+\item[mactex]\CTANref{mactex}
+\item[oztex]\CTANref{oztex}
+\end{ctanrefs}
+
+\Question[Q-sysother]{Other systems' \tex{} availability}
+
+For \acro{PC}s, running \MSDOS{} or \acro{OS/}2, Em\TeX{} (by Eberhard
+Mattes) offers \LaTeX{}, \BibTeX{}, previewers, and drivers. It is
+available as a series of zip archives, with documentation in both
+German and English. Appropriate memory managers for using em\TeX{}
+with 386 (and better) processors and under pre-'9x Windows, are
+included in the distribution. (Em\TeX{} \emph{can} be made to operate
+under Windows, but even back when it was ``current'', such use wasn't
+very actively encouraged.)
+
+A version of em\TeX{}, packaged to use a % ! line break
+\Qref*{TDS directory structure}{Q-tds}, is separately available as an
+em\TeX{} `contribution'. Note that neither em\TeX{} itself, nor
+em\TeX{}-\acro{TDS}, is maintained. Users of Microsoft operating
+systems, who want an up-to-date \AllTeX{} system, need Win32-based
+systems.
+
+For \acro{PC}s, running \MSDOS{}, a further option is a port of the
+Web2C~7.0 implementation, using the \acro{GNU} \ProgName{djgpp}
+compiler. While this package is more recent than em\TeX{}, it
+nevertheless also offers a rather old instance of \AllTeX{}.
+
+For \acro{VAX} systems running Open\acro{VMS}, a \TeX{} distribution
+is available \acro{CTAN}, but is almost certainly not the latest (it
+is more than 10 years old). Whether a version is even available for
+current \acro{VMS} (which typically runs on Intel 64-bit processors)
+is not clear, but it seems unlikely.
+
+For the Atari \acro{ST} and \acro{TT}, \acro{CS}-\TeX{} is available
+from \acro{CTAN}; it's offered as a set of \acro{ZOO} archives.
+
+Amiga users have the option of a full implementations of \TeX{} 3.1
+(Pas\TeX{}) and \MF{} 2.7.
+
+It's less likely that hobbyists would be running \acro{TOPS}-20
+machines, but since \TeX{} was originally written on a \acro{DEC}-10
+under \acro{WAITS}, the \acro{TOPS}-20 port is another near approach
+to Knuth's original environment. Sources are available by anonymous
+\texttt{ftp} from \url{ftp://ftp.math.utah.edu/pub/tex/pub/web}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Atari TeX]\CTANref{atari-cstex}
+\item[djgpp]\CTANref{djgpp}
+\item[emtex]\CTANref{emtex}
+\item[emtexTDS]\CTANref{emtextds}
+\item[OpenVMS]\CTANref{OpenVMSTeX}
+\item[PasTeX]\CTANref{amiga}
+\end{ctanrefs}
+\LastEdit{2013-07-18}
+
+\Question[Q-editors]{\TeX{}-friendly editors and shells}
+
+There are good \TeX{}-writing environments and editors for most
+operating systems; some are described below, but this is only a
+personal selection:
+\begin{description}
+\item[Unix] The commonest choices are \ProgName{[X]Emacs} or
+ \ProgName{vim}, though several others are available.
+
+ \href{http://www.gnu.org/software/emacs/emacs.html}{\acro{GNU}\nobreakspace\ProgName{emacs}}
+ and \href{http://www.xemacs.org/}{\ProgName{XEmacs}} are supported
+ by the \acro{AUC}-\TeX{}
+ bundle (available from \acro{CTAN}). \acro{AUC}-\TeX{} provides menu
+ items and control sequences for common constructs, checks syntax,
+ lays out markup nicely, lets you call \TeX{} and drivers from
+ within the editor, and everything else like this that you can think
+ of. Complex, but very powerful.
+
+ \href{http://vim.sourceforge.net}{\ProgName{Vim}} is also highly
+ configurable (also available for Windows and Macintosh systems).
+ Many plugins are available to support the needs of the \AllTeX{} user,
+ including syntax highlighting, calling \TeX{} programs,
+ auto-insertion and -completion of common \AllTeX{} structures, and
+ browsing \LaTeX{} help. The scripts \File{auctex.vim} and
+ \File{bibtex.vim} seem to be the most common recommendations.
+
+ The editor \href{http://nedit.org/}{\ProgName{NEdit}} is also free
+ and programmable, and is available for Unix systems. An
+ \acro{AUC}-\TeX{}-alike set of extensions for \ProgName{NEdit} is available
+ from \acro{CTAN}.
+
+ \ProgName{LaTeX4Jed} provides much enhanced \LaTeX{} support for the
+ \href{http://www.jedsoft.org/jed/}{\ProgName{jed}} editor.
+ \ProgName{LaTeX4Jed} is similar to \acro{AUC}-\TeX{}: menus,
+ shortcuts, templates, syntax highlighting, document outline,
+ integrated debugging, symbol completion, full integration with
+ external programs, and more. It was designed with both the beginner
+ and the advanced LaTeX user in mind.
+
+ The \ProgName{Kile} editor that is provided with the \acro{KDE}
+ window manager provides \acro{GUI} ``shell-like'' facilities, in a
+ similar way to the widely-praised \ProgName{Winedt} (see below);
+ details (and downloads) are available from the project's
+ \href{http://kile.sourceforge.net/}{home on SourceForge}.
+
+ \acro{TUG} is sponsoring the development of a cross-platform editor
+ and shell, modelled on the excellent \texshop{} for the Macintosh.
+ The result,
+ \href{http://www.tug.org/texworks/}{\texworks{}}, is recommended: if
+ you're looking for a
+ \AllTeX{} development environment, it may be for you. (It is
+ distributed with both \texlive{} and \miktex{}.)
+
+ A possible alternative is
+ \href{http://texstudio.sourceforge.net/}{TeXstudio}
+\item[Windows-32]\ProgName{TeXnicCenter} is a (free)
+ \TeX{}-oriented development system, uniting a powerful platform for
+ executing \AllTeX{} and friends with a configurable editor.
+
+ \texworks{} (see above) is also available for Windows systems.
+
+ \ProgName{Winedt}, a shareware package, is also highly spoken of.
+ It too provides a shell for the use of \TeX{} and related programs,
+ as well as a powerful and well-configured editor. The editor can
+ generate its output in \acro{UTF}-8 (to some extent), which is
+ useful when working with \Qref*{\xetex{}}{Q-xetex} (and other
+ ``next-generation'' \AllTeX{} applications).
+
+ Both \ProgName{emacs} and \ProgName{vim} are available in versions
+ for Windows systems.
+\item[Macintosh] For \macosx{} users, the free tool of choice appears to be
+ \href{http://pages.uoregon.edu/koch/texshop/index.html}{\texshop{}}, which
+ combines an editor and a shell with a coherent philosophy of dealing
+ with \AllTeX{} in the OS~X environment. TeXShop is distributed as
+ part of the MacTeX system, and will therefore be available out of
+ the box on machines on which MacTeX has been installed.
+
+ \ProgName{Vim} is also available for use on Macintosh systems.
+
+ The commercial Textures provides an excellent integrated Macintosh
+ environment with its own editor. More powerful still (as an editor)
+ is the shareware \ProgName{Alpha} which is extensible enough to let
+ you perform almost any \TeX{}-related job. It also works well with
+ Oz\TeX{}. From release 2.2.0 (at least), Textures works under \macosx{}.
+\item[\acro{OS/}2] \ProgName{epmtex} offers an \acro{OS/}2-specific shell.
+\end{description}
+Atari, Amiga and \acro{N}e\acro{XT} users also have nice
+environments. \LaTeX{} users looking for \ProgName{make}-like
+facilities should review the answer on
+\Qref*{Makefiles for \LaTeX{} documents}{Q-make}.
+
+While many \AllTeX{}-oriented editors can support work on \BibTeX{}
+files, there are many systems that provide specific ``database-like''
+access to your \BibTeX{} files~---
+\begin{hyperversion}
+ see ``\Qref{creating a bibliography file}{Q-buildbib}''.
+\end{hyperversion}
+\begin{flatversion}
+ these are discussed in % ! line break
+ ``\Qref*{creating a bibliography file}{Q-buildbib}''.
+\end{flatversion}
+\begin{ctanrefs}
+\item[alpha]\CTANref{alpha}
+\item[auctex]\CTANref{auctex}
+\item[epmtex]\CTANref{epmtex}
+\item[LaTeX4Jed]\CTANref{latex4jed}
+\item[Nedit LaTeX support]\CTANref{nedit-latex}
+\item[TeXnicCenter]\CTANref{texniccenter}
+\item[TeXshell]\CTANref{texshell}
+\item[TeXtelmExtel]\CTANref{TeXtelmExtel}
+\item[winedt]\CTANref{winedt}
+\end{ctanrefs}
+\LastEdit{2013-05-20}
+
+\Question[Q-commercial]{Commercial \TeX{} implementations}
+\keywords{windows,macintosh,commercial}
+
+There are many commercial implementations of \TeX{}. The first
+appeared not long after \TeX{} itself appeared.
+
+What follows is probably an incomplete list. Naturally, no warranty or
+fitness for purpose is implied by the inclusion of any vendor in this
+list. The source of the information is given to provide some clues to
+its currency.
+
+In general, a commercial implementation will come `complete', that is,
+with suitable previewers and printer drivers. They normally also have
+extensive documentation (\emph{i.e}., not just the \TeX{}book!) and some
+sort of support service. In some cases this is a toll free number
+(probably applicable only within the \acro{USA} and or Canada), but others
+also have email, and normal telephone and fax support.
+\begin{description}
+\item[\acro{PC}; True\TeX{}] Runs on all versions of Windows.
+ \begin{quote}
+ Richard J. Kinch\\
+ TrueTeX Software\\
+ 7890 Pebble Beach Court\\
+ Lake Worth \acro{FL} 33467\\
+ \acro{USA}\\[.25\baselineskip]
+ Tel: +1 561-966-8400\\
+ Email: \mailto{kinch@truetex.com}\\
+ Web: \URL{http://www.truetex.com/}
+ \end{quote}
+ Source: Mail from Richard Kinch, August 2004.
+\item[pc\TeX{}] Long-established: pc\TeX{}32 is a Windows implementation.
+ \begin{quote}
+ Personal \TeX{} Inc\\
+ 725 Greenwich Street, Suite 210 \\
+ San Francisco, \acro{CA} 94133\\
+ \acro{USA}\\[.25\baselineskip]
+ Tel: 800-808-7906 (within the \acro{USA})\\
+ Tel: +1 415-296-7550\\
+ Fax: +1 415-296-7501\\
+ Email: \mailto{sales@pctex.com}\\
+ Web: \URL{http://www.pctex.com/}
+ \end{quote}
+ Source: Personal \TeX{} Inc web site, December 2004
+\item[\acro{PC}; Scientific Word] Scientific Word and Scientific Workplace
+ offer a mechanism for near-\WYSIWYG{} input of \LaTeX{} documents; they
+ ship with True\TeX{} from Kinch (see above). Queries within the \acro{UK}
+ and Ireland should be addressed to Scientific Word Ltd., others should be
+ addressed directly to the publisher, MacKichan Software Inc.
+ \begin{quote}
+ Dr Christopher Mabb\\
+ Scientific Word Ltd.\\
+ 990 Anlaby Road,\\
+ Hull,\\
+ East Yorkshire,\\
+ \acro{HU}4 6\acro{AT}\\
+ \acro{UK}\\[0.25\baselineskip]
+ Tel: 0845 766\,0340 (within the \acro{UK}) \\
+ Fax: 0845 603\,9443 (within the \acro{UK}) \\
+ Email: \mailto{christopher@sciword.demon.co.uk} \\
+ Web: \URL{http://www.sciword.demon.co.uk}
+ \end{quote}
+ \begin{quote}
+ MacKichan Software Inc.\\
+ 19307 8th Avenue, Suite C\\
+ Poulsbo \acro{WA} 98370-7370\\
+ \acro{USA}\\[0.25\baselineskip]
+ Tel: +1 360 394\,6033\\
+ Tel: 877 724\,9673 (within the \acro{USA})
+ Fax: +1 360 394\,6039\\
+ Email: \mailto{info@mackichan.com}\\
+ Web: \URL{http://www.mackichan.com}
+ \end{quote}
+ Source: Mail from Christopher Mabb, August 2007
+%% \item[Macintosh; Textures] ``A \TeX{} system `for the rest of
+%% us'\,''. A beta release of Textures for \macosx{} is
+%% available~--- see \URL{http://www.bluesky.com/news/news_frames.html}
+%%
+%% (Blue Sky also gives away a \MF{} implementation and some
+%% font manipulation tools for Macs.)
+%% \begin{quote}
+%% Blue Sky Research\\
+%% PO Box 80424\\
+%% Portland, \acro{OR} 97280\\
+%% \acro{USA}\\[.25\baselineskip]
+%% Tel: 800-622-8398 (within the \acro{USA})\\
+%% Tel/Fax: +1 503-222-9571\\
+%% Fax: +1 503-246-4574\\
+%% Email: \mailto{sales@bluesky.com}\\
+%% Web: \URL{http://www.bluesky.com/}
+%% \end{quote}
+%% Source: Mail from Gordon Lee, April 2007
+\item[Amiga\TeX{}] A full implementation for the Commodore Amiga,
+ including full, on-screen and printing support for all \PS{}
+ graphics and fonts, IFF raster graphics, automatic font generation,
+ and all of the standard macros and utilities.
+ \begin{quote}
+ Radical Eye Software\\
+ \acro{PO} Box 2081\\
+ Stanford, \acro{CA} 94309\\
+ \acro{USA}
+ \end{quote}
+ Source: Mail from Tom Rokicki, November 1994
+\end{description}
+\checked{mc}{1994/11/09}%
+\checked{RF}{1994/11/24}%
+
+Note that the company \YandY{} has gone out of business, and \YandY{}
+\TeX{} (and support for it) is therefore no longer available. Users
+of \YandY{} systems may care to use the self-help
+\href*{http://tug.org/pipermail/yandytex/}{mailing list}
+that was established in 2003; the remaining usable content of
+\YandY{}'s web site is available at \URL{http://www.tug.org/yandy/}
+
diff --git a/help/uk-tex-faq/faq-the-end.tex b/help/uk-tex-faq/faq-the-end.tex
new file mode 100644
index 0000000000..9ace9b7919
--- /dev/null
+++ b/help/uk-tex-faq/faq-the-end.tex
@@ -0,0 +1,167 @@
+% $Id: faq-the-end.tex,v 1.3 2014/01/28 18:17:36 rf10 Exp rf10 $
+
+\section{You're still stuck?}
+
+\Question[Q-noans]{You don't understand the answer}
+
+While the \acro{FAQ} maintainers don't offer a `help' service, they're
+very keen that you understand the answers they've already written.
+They're (almost) written ``in a vacuum'', to provide something to
+cover a set of questions that have arisen; it's always possible that
+they're written in a way that a novice won't understand them.
+
+Which is where you can help the community. Mail the
+\begin{wideversion}
+ \href{mailto:faq-devel@tex.ac.uk}{maintainers}
+\end{wideversion}
+\begin{narrowversion}
+ maintainers (at \Email{faq-devel@tex.ac.uk})
+\end{narrowversion}
+to report the answer that you find unclear, and (if you can) suggest
+what we need to clarify. Time permitting (the team is small and all
+its members are busy), we'll try and clarify the answer. This way,
+with a bit of luck, we can together improve the value of this resource
+to the whole community.
+
+Note that the \acro{FAQ} development email address is not for
+answering questions: it's for you to suggest which questions we should
+work on, or new questions we should answer in future editions.
+
+Those who simply ask questions at that address will be referred to
+\mailto{texhax@tug.org} or to \Newsgroup{comp.text.tex}.
+
+\Question[Q-newans]{Submitting new material for the \acro{FAQ}}
+
+The \acro{FAQ} will never be complete, and we always expect that
+there will be people out there who know better than we do about
+something or other. We always need to be put right about whatever
+we've got wrong, and suggestions for improvements, particularly
+covering areas we've missed, are always needed: mail anything you have
+to the
+\begin{wideversion}
+ \href{mailto:faq-devel@tex.ac.uk}{maintainers}
+\end{wideversion}
+\begin{narrowversion}
+ maintainers (at \Email{faq-devel@tex.ac.uk})
+\end{narrowversion}
+
+If you have actual material to submit, your contribution is more than
+ever welcome. Submission in plain text is entirely acceptable, but
+if you're really willing, you may feel free to mark up your submission
+in the form needed for the \acro{FAQ} itself. The markup is a
+strongly-constrained version of \LaTeX{}~--- the constraints come from
+the need to translate the marked-up text to \acro{HTML} on the fly
+(and hence pretty efficiently). There is a file \File{markup-syntax}
+in the \acro{FAQ} distribution that describes the structure of the
+markup, but there's no real substitute for reading at least some of
+the source (\File{faqbody.tex}) of the \acro{FAQ} itself. If you
+understand \ProgName{Perl}, you may also care to look at the
+translation code in \File{texfaq2file} and \File{sanitize.pl} in the
+distribution: this isn't the code actually used on the Web site, but
+it's a close relation and is kept
+up to date for development purposes.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\acro{FAQ} distribution]\CTANref{faq}
+\end{ctanrefs}
+
+\Question[Q-bug]{What to do if you find a bug}
+
+For a start, make entirely sure you \emph{have} found a bug.
+Double-check with books about \TeX{}, \LaTeX{}, or whatever you're using;
+compare what you're seeing against the other answers above; ask every
+possible person you know who has any \TeX{}-related expertise.
+The reasons for all this caution are various.
+
+If you've found a bug in \TeX{} itself, you're a rare animal indeed.
+Don Knuth is so sure of the quality of his code that he offers real
+money prizes to finders of bugs; the cheques he writes are
+such rare items that they are seldom cashed. If \emph{you}
+think you have found a genuine fault in \TeX{} itself (or \MF{}, or the
+\acro{CM} fonts, or the \TeX{}book), don't immediately write to Knuth,
+however. He only looks at bugs infrequently, and even then
+only after they are agreed as bugs by a small vetting team. In the
+first instance, contact Barbara Beeton at the \acro{AMS}
+(\Email{bnb@ams.org}), or contact
+\Qref*{\acro{TUG}}{Q-TUG*}.
+
+If you've found a bug in \LaTeXe{}, \Qref*{report it}{Q-latexbug}
+using mechanisms supplied by the \LaTeX{} team. (Please be
+careful to ensure you've got a \LaTeX{} bug, or a bug in one of the
+``required'' packages distributed by the \LaTeX{} team.)
+
+If you've found a bug in a contributed \LaTeX{} package, the best
+starting place is usually to ask in the ``usual places for % ! line break
+\Qref*{help on-line}{Q-gethelp}, or just possibly one of the % ! line break
+\Qref*{specialised mailing lists}{Q-maillists*}.
+The author of the package may well answer on-line, but if no-one
+offers any help, you may stand a chance if you mail the author
+(presuming that you can find an address\dots{}).
+
+If you've found a bug in \LaTeXo{}, or some other such unsupported
+software, your only real hope is \Qref*{help on-line}{Q-gethelp}.
+
+Failing all else, you may need to pay for
+help~--- \acro{TUG} maintains a % ! line break
+\href{http://www.tug.org/consultants.html}{register of \TeX{} consultants}.
+(This of course requires that you have the resources~--- and a
+pressing enough need~--- to hire someone.)
+
+
+\htmlignore
+\par
+\endhtmlignore
+\Question[Q-latexbug]{Reporting a \LaTeX{} bug}
+\htmlignore
+\par
+\endhtmlignore
+%
+% This here isn't a reference to a question...
+\label{lastquestion}
+
+The \LaTeX{} team supports \LaTeX{}, and will deal with
+% beware line wrap
+\emph{bona fide} bug reports. Note that the \LaTeX{} team does
+\emph{not} deal with contributed packages~--- just the software that
+is part of the \LaTeX{} distribution itself: \LaTeX{} and the
+``required'' packages.
+Furthermore, you need to be slightly
+careful to produce a bug report that is usable by the team. The steps
+are:
+
+\nothtml{\noindent}\textbf{1.} Are you still using current \LaTeX{}? Maintenance is only
+available for sufficiently up-to-date versions of \LaTeX{}~--- if your
+\LaTeX{} is more than two versions out of date, the bug reporting
+mechanisms may reject your report.
+
+\nothtml{\noindent}\textbf{2.} Has your bug already been reported? Browse the
+% beware line break
+\href{http://www.latex-project.org/cgi-bin/ltxbugs2html?introduction=yes}{\LaTeX{} bugs database},
+to find any earlier instance of your bug. In many cases, the database
+will list a work-around.
+
+\nothtml{\noindent}\textbf{3.} Prepare a % ! line break
+\Qref*{``minimum'' file}{Q-minxampl} that exhibits the problem.
+Ideally, such a file should contain no contributed packages~--- the
+\LaTeX{} team as a whole takes no responsibility for such packages (if
+they're supported at all, they're supported by their authors). The
+``minimum'' file should be self-sufficient: if a member of the team
+runs it in a clean directory, on a system with no contributed
+packages, it should replicate your problem.
+
+\nothtml{\noindent}\textbf{4.} Run your file through \LaTeX{}: the bug
+system needs the \extension{log} file that this process creates.
+
+\nothtml{\noindent}\textbf{5.} Connect to the % ! line break
+\href{http://www.latex-project.org/bugs-upload.html}{latex bugs processing web page}
+and enter details of your bug~--- category, summary and full
+description, and the two important files (source and log file).
+
+The personal details are \emph{not} optional: the members of the
+\LaTeX{} team may need to contact to discuss the bug with you, or to
+advise you of a work-around. Your details will not appear in the
+public view of the database.
+
+%%% Local Variables:
+%%% mode: latex
+%%% TeX-master: t
+%%% End:
diff --git a/help/uk-tex-faq/faq-wdidt.tex b/help/uk-tex-faq/faq-wdidt.tex
new file mode 100644
index 0000000000..c6cdd8e95e
--- /dev/null
+++ b/help/uk-tex-faq/faq-wdidt.tex
@@ -0,0 +1,2142 @@
+% $Id: faq-wdidt.tex,v 1.24 2014/01/22 17:29:03 rf10 Exp $
+
+\section{Why does it \emph{do} that?}
+
+\subsection{Common errors}
+
+\Question[Q-crossref]{\LaTeX{} gets cross-references wrong}
+
+Sometimes, however many times you run \LaTeX{}, the cross-references
+are just wrong. A likely reason is that you have placed the label
+before the data for the label was set; if the label is recording a
+\csx{caption} command, the \csx{label} command must appear
+\emph{after} the \csx{caption} command, or be part of it. For example:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ <the illustration itself>
+ \caption{My figure}
+ \label{myfig}
+\end{figure}
+\end{verbatim}
+\end{quote}
+is correct, as is
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ <the illustration itself>
+ \caption{My figure%
+ \label{myfig}}
+\end{figure}
+\end{verbatim}
+\end{quote}
+whereas, in
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ <the illustration itself>
+ \label{myfig}
+ \caption{My figure}
+\end{figure}
+\end{verbatim}
+\end{quote}
+the label will report the number of the section (or whatever) in which
+the surrounding text resides, or the like.
+
+You can, with the same malign effect, shield the \csx{caption} command
+from its associated \csx{label} command, by enclosing the caption in an
+environment of its own. This effect will be seen with:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ <the illustration itself>
+ \caption{A Figure}
+\end{figure}
+\label{myfig}
+\end{verbatim}
+\end{quote}
+where the \csx{label} definitely \emph{is} after the \csx{caption},
+but because the \environment{figure} environment closed before the
+\csx{label} command, the \csx{caption} is no longer ``visible''.
+
+In summary, the \csx{label} must be \emph{after} the command that
+defines it (e.g., \csx{caption}), and if the \csx{caption} is inside
+an environment, the \csx{label} must be in there too.
+\LastEdit{2012-02-07}
+
+\Question[Q-newlineargs]{Start of line goes awry}
+\keywords{asterisk square bracket start line}
+
+This answer concerns two sorts of problems: errors of the form
+\begin{quote}
+\begin{verbatim}
+! Missing number, treated as zero.
+<to be read again>
+ p
+<*> [perhaps]
+\end{verbatim}
+\end{quote}
+and errors where a single asterisk at the start of a line mysteriously
+fails to appear in the typeset output.
+
+Both problems arise because \texttt{\bsbs } takes optional arguments. The
+command \texttt{\bsbs *} means ``break the line here, and inhibit page break
+following the line break''; the command \texttt{\bsbs [}\meta{dimen}\texttt{]}
+means ``break the line here and add \meta{dimen} extra vertical space
+afterwards''.
+
+The problem arises because \texttt{\bsbs } looks for the next
+non-blank thing; the test it uses ignores the end of the line in
+your input text, so that \texttt{\bsbs } comes to imagine that you
+were giving it a `modifier'.
+
+An obvious solution is to enclose the stuff at the start of the new
+line in braces, typing:
+\begin{quote}
+\begin{verbatim}
+{\ttfamily
+ /* C-language comment\\
+ {[perhaps]} this could be done better\\
+ {*}/
+}
+\end{verbatim}
+\end{quote}
+This particular example could be coded (without any problems) in
+verbatim, but the behaviour does confuse people.
+
+The problem also appears in maths mode, in arrays and so on. In this
+case, large-scale bracketing of things is \emph{not} a good idea; the
+\TeX{} primitive \csx{relax} (which does nothing except to block
+searches of this nature) may be used. From another
+\Newsgroup{comp.text.tex} example:
+\begin{quote}
+\begin{verbatim}
+\begin{eqnarray}
+ [a] &=& b \\
+ \relax[a] &=& b
+\end{eqnarray}
+\end{verbatim}
+\end{quote}
+which is a usage this \acro{FAQ} would not recommend, anyway: refer
+to the \Qref*{reason not to use \environment{eqnarray}}{Q-eqnarray}.
+
+Note that the \Package{amsmath} package modifies the behaviour of
+\texttt{\bsbs } in maths. With \Package{amsmath}, the
+\environment{eqnarray} example doesn't need any special action
+(\csx{relax} or braces).
+\LastEdit{2012-09-02}
+
+\Question[Q-verbwithin]{Why doesn't verbatim work within\,\dots{}?}
+
+The \LaTeX{} verbatim commands work by changing category codes. Knuth
+says of this sort of thing ``Some care is needed to get the timing
+right\dots{}'', since once the category code has been assigned to a
+character, it doesn't change. So \csx{verb} and
+\cmdinvoke{begin}{verbatim} have to assume that they are getting the
+first look at the parameter text; if they aren't, \TeX{} has already
+assigned category codes so that the verbatim command doesn't have a
+chance. For example:
+\begin{quote}
+\begin{verbatim}
+\verb+\error+
+\end{verbatim}
+\end{quote}
+will work (typesetting `\csx{error}'), but if we define no more than a
+no-op macro,
+\begin{quote}
+\begin{verbatim}
+\newcommand{\unbrace}[1]{#1}
+\end{verbatim}
+\end{quote}
+which simply regurgitates its argument, and use it as:
+\begin{quote}
+\begin{verbatim}
+\unbrace{\verb+\error+}
+\end{verbatim}
+\end{quote}
+the combinartion will not (it will attempt to execute \csx{error}).
+Other errors one
+may encounter are `\csx{verb} ended by end of line', or even the
+rather more helpful `\csx{verb} illegal in command argument'. The
+same sorts of thing happen with \cmdinvoke{begin}{verbatim} \dots{}
+\cmdinvoke{end}{verbatim}:
+\begin{quote}
+\begin{quoteverbatim}
+\ifthenelse{\boolean{foo}}{%
+\begin{verbatim}
+foobar
+\end{verbatim}
+}{%
+\begin{verbatim}
+barfoo
+\end{verbatim}
+}
+\end{quoteverbatim}
+\end{quote}
+provokes errors like `File ended while scanning use of
+\csx{@xverbatim}', as \cmdinvoke{begin}{verbatim} fails to see its
+matching \cmdinvoke{end}{verbatim}.
+
+This is why the \LaTeX{} book insists that verbatim
+commands must not appear in the argument of any other command; they
+aren't just fragile, they're quite unusable in any ``normal'' command
+parameter,
+regardless of \Qref*{\csx{protect}ion}{Q-protect}. (The \csx{verb}
+command tries hard to detect if you're misusing it; unfortunately, it
+can't always do so, and the error message is therefore not reliable as an
+indication of problems.)
+
+The first question to ask yourself is: ``is \csx{verb} actually
+necessary?''.
+\begin{itemize}
+\item If \cmdinvoke{texttt}{\emph{your text}} produces the same result
+ as \csx{verb}\texttt{+\emph{your text}+}, then there's no need of
+ \csx{verb} in the first place.
+\item If you're using \csx{verb} to typeset a \acro{URL} or email
+ address or the like, then the \csx{url} command from the
+ \Package{url} will help: it doesn't suffer from all the problems of
+ \csx{verb}, though it's still not robust; % ! line break
+ ``\Qref*{typesetting \acro{URL}s}{Q-setURL}'' offers advice here.
+\item If you're putting \csx{verb} into the argument of a boxing
+ command (such as \csx{fbox}), consider using the \environment{lrbox}
+ environment:
+\begin{quote}
+\begin{verbatim}
+\newsavebox{\mybox}
+...
+\begin{lrbox}{\mybox}
+ \verb!VerbatimStuff!
+\end{lrbox}
+\fbox{\usebox{\mybox}}
+\end{verbatim}
+\end{quote}
+\end{itemize}
+
+If you can't avoid verbatim, the \csx{cprotect} command (from the
+package \Package{cprotect}) might help. The package manages to make a
+macro read a verbatim argument in a ``sanitised'' way by the simple
+medium of prefixing the macro with \csx{cprotect}:
+\begin{quote}
+\begin{verbatim}
+\cprotect\section{Using \verb|verbatim|}
+\end{verbatim}
+\end{quote}
+The package \emph{does} work in this simple case, and deserves
+consideration in many others cases; the package documentation gives
+more details.
+
+Another way out is to use one of ``argument types'' of the
+\csx{NewDocumentCommand} command in the experimental \latex{}3 package
+\Package{xparse}:
+\begin{quote}
+\begin{verbatim}
+\NewDocumentCommand\cmd{ m v m }{#1 `#2' #3}
+\cmd{Command }|\furble|{ isn't defined}
+\end{verbatim}
+\end{quote}
+Which gives us:
+\begin{quote}
+ Command \csx{furble} isn't defined
+\end{quote}
+The ``\texttt{m}'' tag argument specifies a normal mandatory argument,
+and the ``\texttt{v}'' specifies one of these verbatim arguments.
+As you see, it's implanting a \csx{verb}-style command argument in the
+argument sequence of an otherwise ``normal'' sort of command; that
+\begin{typesetversion}
+ `\texttt{\char`\|}'
+\end{typesetversion}
+\begin{htmlversion}
+ `\texttt{|}' % | balance for emacs text-colouring
+\end{htmlversion}
+may be any old character that doesn't
+conflict with the content of the argument.
+
+This is pretty neat (even if the verbatim is in an argument of its
+own) but the downside is that \Package{xparse} pulls in
+the experimental \latex{}3 programming environment
+(\Package{l3kernel}) which is pretty big.
+
+Other than the \Package{cprotect} package, there are four partial
+solutions to the problem:
+\begin{itemize}
+\item Some packages have macros which are designed to be responsive
+ to verbatim text in their arguments. For example,
+ the \Package{fancyvrb} package defines a command
+ \csx{VerbatimFootnotes}, which redefines the \csx{footnotetext}
+ command, and hence also the behaviour of the \csx{footnote})
+ command, in such a way that you can include \csx{verb} commands in
+ its argument. This approach could in principle be extended to the
+ arguments of other commands, but it can clash with other packages:
+ for example, \csx{VerbatimFootnotes} interacts poorly with the
+ \pkgoption{para} option of the \Package{footmisc} package.
+
+ The \Class{memoir} class defines its \csx{footnote} command so that
+ it will accept verbatim in its arguments, without any supporting package.
+\item The \Package{fancyvrb} package defines a command \csx{SaveVerb},
+ with a corresponding \csx{UseVerb} command, that allow you to save
+ and then to reuse the content of its argument; for details of this
+ extremely powerful facility, see the package documentation.
+
+ Rather simpler is the \Package{verbdef} package, whose \csx{verbdef}
+ command defines a (robust) command which expands to the verbatim
+ argument given; the \Package{newverbs} package provides a similar
+ function as well as several related ones.
+\item In a similar vein, the \Package{verbatimbox} package makes it
+ possible to put verbatim material in a box:
+ \begin{quote}
+\begin{verbatim}
+\begin{verbbox}
+some exotic _&$ stuff
+\end{verbbox}
+\theverbbox
+\end{verbatim}
+ \end{quote}
+ the operation typesets exotic stuff into an anonymous box, and its
+ contents may be retrieved using the command \csx{theverbbox}. It is
+ clear that it's in the same mould as the \csx{verbdef} command
+ mentioned above; the package defines other similar commands.
+\item The \Package{tcolorbox} package provides a similar facility
+\item If you have a single character that is giving trouble (in
+ its absence you could simply use \csx{texttt}), consider using
+ \csx{string}. \cmdinvoke{texttt}{my\csx{string}\_name}
+ typesets the same as
+ \csx{verb+my\_name+}, and will work in the argument of a command. It
+ won't, however, work in a moving argument, and no amount of
+ \Qref*{\csx{protect}ion}{Q-protect} will make it work in
+ such a case.
+
+ A robust alternative is:
+\begin{quote}
+\begin{verbatim}
+\chardef\us=`\_
+...
+\section{... \texttt{my\us name}}
+\end{verbatim}
+\end{quote}
+ Such a definition is `naturally' robust; the construction
+ ``\meta{back-tick}\csx{\meta{char}}'' may be used for any
+ troublesome character (though it's plainly not necessary for things
+ like percent signs for which \AllTeX{} already provides
+ robust macros).
+
+\item One may also consider putting verbatim material in an external
+ file; this is somewhat more tedious, but the file may be reused
+ several times within a single document. The \Package{tcolorbox}
+ permits this:
+\begin{quote}
+\begin{verbatim}
+\begin{tcbverbatimwrite}{<file name>}
+...
+\end{tcbverbatimwrite}
+\end{verbatim}
+\end{quote}
+ which (as one might guess) writes to the named file; load the saved
+ contents using \cmdinvoke{input}{<file name>}
+
+ A second environment puts your verbatim material in an (apparently)
+ anonymous temporary file:
+\begin{quote}
+\begin{verbatim}
+\begin{tcbwritetemp}{<file name>}
+...
+\end{tcbverbatimwrite}
+\end{verbatim}
+\end{quote}
+ In this case, you use the anonymous file with the \csx{tcbusetemp}
+ macro. (You can change the name used for the `anonymous' file, if
+ its default proves troublesome.)
+
+ The \Package{moreverb} package provides a \csx{verbatimwrite}
+ command, which doesn't provide an anonynous file.
+
+ Macros, to achieve the same effect, are outlined in the
+ documentation of the \Package{verbatim} package; the macros use the
+ facilities of the package, but the user has to write a mini-package
+ actually to use them.
+\end{itemize}
+\begin{ctanrefs}
+\item[cprotect.sty]\CTANref{cprotect}
+\item[fancyvrb.sty]\CTANref{fancyvrb}
+\item[l3kernel \nothtml{\rmfamily}bundle]\CTANref{l3kernel}
+\item[memoir.cls]\CTANref{memoir}
+\item[newverbs.sty]\CTANref{newverbs}
+\item[tcolorbox.sty]\CTANref{tcolorbox}
+\item[url.sty]\CTANref{url}
+\item[verbatim.sty]\CTANref{verbatim}
+\item[verbatimbox.sty]\CTANref{verbatimbox}
+\item[verbdef.sty]\CTANref{verbdef}
+\item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse]
+\end{ctanrefs}
+\LastEdit{2013-10-21}
+
+\Question[Q-noline]{``No line here to end''}
+
+The error
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! LaTeX Error: There's no line here to end.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! LaTeX Error: There's no line here to end.
+
+See the LaTeX manual or LaTeX Companion
+... for explanation.
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+appears when you give \LaTeX{} a \texttt{\bsbs } command at a time
+when it's not expecting it; it is a \emph{line-breaking} command, and
+is confused if \latex{} isn't building a paragraph when you give the
+command. A common case is where you've decided you want the label of
+a list item to be on a line of its own, and written (for example):
+\begin{quote}
+\begin{verbatim}
+\begin{description}
+\item[Very long label] \\
+ Text...
+\end{description}
+\end{verbatim}
+\end{quote}
+% ridiculous coding for sanitize.pl -- careful!
+% \bsbs {} is actually a rather bad command to use in this case (even if
+% it worked), since it could force the `paragraph' that's made up of the
+% text of the item to terminate a line which has nothing on it but the
+% label. This could lead to an ``\texttt{Underfull }\csx{hbox}'' warning message
+% (usually with `infinite' badness of 10000); while this message doesn't
+% do any actual harm other than slowing down your \LaTeX{} run, any
+% message that doesn't convey any information distracts for no useful
+% purpose.
+
+The proper solution to the problem is to write a new sort of
+\environment{description} environment, that does just what you're after. (The
+\nothtml{\emph{\LaTeX{} Companion}~--- see }% ! line wrap, and next line
+\Qref[question]{\emph{\LaTeX{} Companion}}{Q-latex-books}\nothtml{~---}
+offers a rather wide selection of variants of these things.)
+
+A straightforward solution, which avoids the warning, is to write:
+\begin{quote}
+\begin{verbatim}
+\begin{description}
+\item[Very long label] \leavevmode \\
+ Text...
+\end{description}
+\end{verbatim}
+\end{quote}
+which starts a paragraph before forcing a break. The
+\Package{expdlist} package provides the same functionality with its
+\csx{breaklabel} command, and \Package{mdwlist} provides it via its
+\csx{desclabelstyle} command.
+
+The other common occasion for the message is when you're using the
+\texttt{center} (or \environment{flushleft} or \environment{flushright})
+environment, and have decided you need extra separation between lines
+in the environment:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+ First (heading) line\\
+ \\
+ body of the centred text...
+\end{center}
+\end{verbatim}
+\end{quote}
+The solution here is plain: use the \texttt{\bsbs } command in the way it's
+supposed to be used, to provide more than just a single line break
+space. \texttt{\bsbs } takes an optional argument, which specifies
+how much extra space to add; the required effect in the text above can
+be had by saying:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+ First (heading) line\\[\baselineskip]
+ body of the centred text...
+\end{center}
+\end{verbatim}
+\end{quote}
+
+You \emph{can} use \csx{leavevmode}, as above:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+ First (heading) line\\
+ \leavevmode\\
+ body of the centred text...
+\end{center}
+\end{verbatim}
+\end{quote}
+but that is just as tiresome to type as \texttt{\bsbs } with an optional
+argument, and can not be recommended.
+\begin{ctanrefs}
+\item[expdlist.sty]\CTANref{expdlist}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
+\end{ctanrefs}
+\LastEdit{2014-01-13}
+
+% other instances: \[no]linebreak in vertical mode
+
+\Question[Q-vertspacefloat]{Extra vertical space in floats}
+
+A common complaint is that extra vertical space has crept into
+\environment{figure} or \environment{table} floating environments.
+More common still are users who post code that introduces this extra
+space, and \emph{haven't noticed the problem}!
+
+The trouble arises from the fact that the \environment{center}
+environment (and its siblings \environment{flushleft} and
+\environment{flushright}) are actually based on \LaTeX{}'s
+list-handling code; and lists always separate themselves from the
+material around them. Meanwhile, there are parameters provided to
+adjust the spacing between floating environments and their
+surroundings; so if we have:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ \begin{center}
+ \includegraphics{...}
+ \caption{...}
+ \end{center}
+\end{figure}
+\end{verbatim}
+\end{quote}
+\nothtml{\noindent}or worse still:
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ \begin{center}
+ \includegraphics{...}
+ \end{center}
+ \caption{...}
+\end{figure}
+\end{verbatim}
+\end{quote}
+unwarranted vertical space is going to appear.
+
+The solution is to let the float and the objects in it position
+themselves, and to use ``generic'' layout commands rather than their
+list-based encapsulations.
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ \centering
+ \includegraphics{...}
+ \caption{...}
+\end{figure}
+\end{verbatim}
+\end{quote}
+(which even involves less typing).
+
+This alternative code will work with any \LaTeX{} package. It will
+not work with obsolete (pre-\LaTeXe{}) packages such as
+\Package{psfig} or \Package{epsf}~--- see % beware line break
+\Qref[question]{graphics inclusion}{Q-impgraph} for discussion of the
+genesis of \csx{includegraphics}.
+\LastEdit{2012-11-16}
+
+\Question[Q-centre-flt]{Why is my table/figure/\dots{} not centred?}
+
+You want a float whose contents are centred, but \latex{} ignores your
+\environment{center} environment. Most likely, you have written:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+ \begin{figure}
+ ...
+ \end{figure}
+\end{center}
+\end{verbatim}
+\end{quote}
+In this case, \latex{} has ``taken the \environment{figure} away'',
+and will typeset it at some location it fancies (it does the same with
+\environment{table}s) the only thing we can say (for sure) about the
+location is that it \emph{won't} be inside that \environment{center}
+environment. As a result, the \environment{center} environment is
+left with nothing to do~\dots{} except to % !line break
+\Qref*{make a mess of your vertical spacing}{Q-vertspacefloat}.
+
+The solution is the same as that outlined in % !line break
+\Qref*{the same answer}{Q-vertspacefloat}, noting that all control of
+an \environment{figure} or \environment{table} needs to be
+inside the environment. So the example's code should be converted to
+\begin{quote}
+\begin{verbatim}
+\begin{figure}
+ \centering
+ ...
+\end{figure}
+\end{verbatim}
+\end{quote}
+(or something similar for a \environment{table}).
+\LastEdit*{2013-11-19}
+
+\Question[Q-2colfltorder]{Two-column float numbers out of order}
+
+When \LaTeX{} can't place a float immediately, it places it on one of
+several ``defer'' lists. If another float of the same type comes
+along, and the ``defer'' list for that type still has something in it,
+the later float has to wait for everything earlier in the list.
+
+Now, standard \LaTeX{} has different lists for single-column floats,
+and double-column floats; this means that single-column figures can
+overtake double-column figures (or vice-versa), and you observe later
+figures appear in the document before early ones. The same is true,
+of course, for tables, or for any user-defined float.
+
+The \LaTeX{} team recognise the problem, and provides a package
+(\Package{fixltx2e}) to deal with it. \Package{Fixltx2e} amalgamates
+the two defer lists, so that floats don't get out of order.
+
+For those who are still running an older \LaTeX{} distribution, the
+package \Package{fix2col} should serve. This package (also by a
+member of the \LaTeX{} team) was the basis of the relevant part of
+\Package{fixltx2e}. The functionality has also been included in
+\Package{dblfloatfix}, which also has code to place full-width floats
+at \Qref*{\texttt{[b]} placement}{Q-2colfloat}.
+
+Once you have loaded the package, no more remains to be done: the
+whole requirement is to patch the output routine; no extra commands
+are needed.
+\begin{ctanrefs}
+\item[dblfloatfix.sty]\CTANref{dblfloatfix}
+\item[fix2col.sty]\CTANref{fix2col}
+\item[fixltx2e.sty]Part of the \LaTeX{} distribution
+\end{ctanrefs}
+
+\Question[Q-tabacc]{Accents misbehave in \environment{tabbing}}
+
+So you are constructing a \environment{tabbing} environment, and you
+have the need of some diacriticised text~--- perhaps something as simple
+as \cmdinvoke{'}{e}~--- and the accent disappears because it has been
+interpreted as a \environment{tabbing} command, and everything goes
+wrong.
+
+This is really a rather ghastly feature of the \environment{tabbing}
+environment; in order to type accented characters you need to use the
+\csx{a} kludge: so \cmdinvoke{a'}{e} inside \environment{tabbing} for
+\cmdinvoke{'}{e} outside, and similarly \csx{a`} for \csx{`} and \csx{a=}
+for \csx{=}. This whole procedure is of course hideous and
+error-prone.
+
+The simplest alternative is to type in an encoding that has the
+diacriticised characters in it, and to use an appropriate encoding
+definition file in the \Package{inputenc} package. So for example,
+type:
+\begin{quote}
+ \cmdinvoke{usepackage}[latin1]{inputenc}\\
+ \texttt{...}\\
+ \cmdinvoke{begin}{tabbing}\\
+ \texttt{...}\\
+ \texttt{...} \csx{>} \texttt{voil\`a} \csx{>} \texttt{...}
+\end{quote}
+for:
+\begin{quote}
+ \dots{}\quad voil\`a\quad \dots{}
+\end{quote}
+and the internal mechanisms of the \Package{inputenc} package will put
+the right version of the accent command in there.
+
+A witty reversal of the r\^oles is introduced by the package
+\Package{Tabbing} (note the capital ``T''): it provides a
+\environment{Tabbing} environment which duplicates
+\environment{tabbing}, but all the single-character commands become
+complicated objects. So \environment{tabbing}'s \csx{>} becomes
+\csx{TAB>}, \csx{=} becomes \csx{TAB=}, and so on. The above trivial
+example would therefore become:
+\begin{quote}
+\begin{verbatim}
+\usepackage{Tabbing}
+...
+\begin{Tabbing}
+ ... ... \TAB> voil\`a \TAB> ...
+\end{verbatim}
+\end{quote}
+\begin{ctanrefs}
+\item[Tabbing.sty]\CTANref{Tabbing}
+\end{ctanrefs}
+
+\Question[Q-alreadydef]{Package reports ``command already defined''}
+
+You load a pair of packages, and the second reports that one of the
+commands it defines is already present. For example, both the
+\Package{txfonts} and \Package{amsmath} define a command \csx{iint}
+(and \csx{iiint} and so on); so
+\begin{quote}
+\begin{verbatim}
+...
+\usepackage{txfonts}
+\usepackage{amsmath}
+\end{verbatim}
+\end{quote}
+produces a string of error messages of the form:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+! LaTeX Error: Command \iint already defined.
+ Or name \end... illegal, see p.192 of the manual.
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+! LaTeX Error: Command \iint already
+ defined. Or name \end... illegal,
+ see p.192 of the manual.
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+As a general rule, things that \Package{amsmath} defines, it defines
+well; however, there is a good case for using the \Package{txfonts}
+version of \csx{iint}~--- the associated \FontName{tx} fonts have a
+double integral symbol that doesn't need to be ``faked'' in the way
+\Package{amsmath} does. In the case that you are loading several
+symbol packages, every one of which defines the same symbol, you are
+likely to experience the problem in a big way (\csx{euro} is a common
+victim).
+
+There are similar cases where one package redefines another's command,
+but no error occurs because the redefining package doesn't use
+\csx{newcommand}. Often, in such a case, you only notice the change
+because you assume the definition given by the first package. The
+\Package{amsmath}--\Package{txfonts} packages are just such a pair;
+\Package{txfonts} doesn't provoke errors.
+
+You may deal with the problem by saving and restoring the command.
+Macro programmers may care to do this for themselves; for the rest of
+us, there's the package \Package{savesym}. The sequence:
+\begin{quote}
+\begin{verbatim}
+\usepackage{savesym}
+\usepackage{amsmath}
+\savesymbol{iint}
+\usepackage{txfonts}
+\restoresymbol{TXF}{iint}
+\end{verbatim}
+\end{quote}
+does the job; restoring the \Package{amsmath} version of the command,
+and making the \Package{txfonts} version of the command available as
+\csx{TXFiint}.
+
+Documentation of \Package{savesym} doesn't amount to much: the only
+commands are \csx{savesymbol} and \csx{restoresymbol}, as noted above.
+\begin{ctanrefs}
+\item[amsmath.sty]Part of \CTANref{amslatex}
+\item[savesym.sty]\CTANref{savesym}
+\item[txfonts.sty]Part of \CTANref{txfonts}
+\end{ctanrefs}
+
+\Question[Q-zerochap]{Why are my sections numbered 0.1\,\dots{}?}
+
+This happens when your document is using the standard \Class{book} or
+\Class{report} class (or one similar), and you've got a \csx{section}
+before your first \csx{chapter}.
+
+What happens is, that the class numbers sections as % ! line break
+``\meta{chapter no}.\meta{section no}'', and until the first
+\csx{chapter} has appeared, the chapter number is 0. (If you
+use\csx{chapter*}, which doesn't number the chapter it produces, the
+problem still arises.)
+
+If you're doing this, it's possible that the \Class{article} class
+is for you; try it and see. Otherwise, put a \csx{chapter} before
+your sections, or do away with section numbering by using
+\csx{section*} instead. An alternative way of avoiding numbering is
+discussed in % ! line break
+``\Qref*{unnumbered sections in the table of contents}{Q-secnumdep}''.
+
+\Question[Q-breaklinks]{Link text doesn't break at end line}
+\keywords{hyperref overfull link}
+
+When using the \Package{hyperref} package, you make a block of text
+``active'' when you define a hyper-link (when the user clicks on
+that text, the reader program will divert to the \emph{target} of the
+link).
+
+The \Package{hyperref} package uses a \emph{driver} (in the same way
+as the \Package{graphics} package does), to determine how to implement
+all that hyper-stuff.
+
+If you use the driver for \ProgName{dvips} output (presumably you want
+to distill the resulting \PS{}), limitations in the way \ProgName{dvips}
+deals with the \csx{special} commands mean that \Package{hyperref}
+must prevent link anchors from breaking at the end of lines. Other
+drivers (notably those for \PDFTeX{} and for \ProgName{dvipdfm}) don't
+suffer from this problem.
+
+The problem may occur in a number of different circumstances. For a
+couple of them, there are work-arounds:
+
+First, if you have an \acro{URL} which is active (so that clicking on
+it will activate your web browser to ``go to'' the \acro{URL}). In
+this case \Package{hyperref} employs the \Package{url} package to
+split up the \acro{URL} (as described in % ! line break
+\Qref[question]{typesetting \acro{URL}s}{Q-setURL}), but the
+\ProgName{dvips} driver then suppresses the breaks. The way out is
+the \Package{breakurl} package, which modifies the \csx{url} command
+to produce several smaller pieces, between each of which a line break
+is permitted. Each group of pieces, that ends up together in one
+line, is converted to a single clickable link.
+
+Second, if you have a table of contents, list of figure or tables, or
+the like, \Package{hyperref} will ordinarily make the titles in the
+table of contents, or captions in the lists, active. If the title or
+caption is long, it will need to break within the table, but the
+\ProgName{dvips} driver will prevent that. In this case, load
+\Package{hyperref} with the option \pkgoption{linktocpage}, and only
+the page number will be made active.
+
+Otherwise, if you have a lengthy piece of text that you want active,
+you have at present no simple solution: you have to rewrite your text,
+or to use a different \acro{PDF} generation mechanism.
+\begin{ctanrefs}
+\item[breakurl.sty]\CTANref{breakurl}
+\end{ctanrefs}
+
+\Question[Q-wrongpn]{Page number is wrong at start of page}
+
+This is a long story, whose sources are deep inside the workings of
+\TeX{} itself; it all derives from the \TeX{}'s striving to generate
+the best possible output.
+
+The page number is conventionally stored in \csx{count0}; \LaTeX{}
+users see this as the counter \texttt{page}, and may typeset its value
+using \csx{thepage}.
+
+The number (that is to say, \csx{count0}) is only updated when \TeX{}
+actually outputs a page. \TeX{} only even tries to do this when it
+detects a hint that it may be a good thing to do. From \TeX{}'s point
+of view, the end of a paragraph is a good time to consider outputting
+a page; it will output a page if it has \emph{more} than a page's
+worth of material to output. (Ensuring it always has something in
+hand makes some optimisations possible.) As a result, \csx{count0}
+(\csx{thepage}) is almost always wrong in the first paragraph of a
+page (the exception is where the page number has been ``forcibly''
+changed, either by changing its value directly, or by breaking the
+page where \TeX{} wouldn't necessarily have chosen to break).
+
+\LaTeX{} provides a safe way of referring to the page number, by using
+label references. So, rather than writing:
+\begin{quote}
+\begin{verbatim}
+Here is page \thepage{}.
+\end{verbatim}
+\end{quote}
+you should write:
+\begin{quote}
+\begin{verbatim}
+Here is page \pageref{here}\label{here}.
+\end{verbatim}
+\end{quote}
+(note: no space between the \csx{pageref} and the \csx{label}, since
+that could potentially end up as a page-break space itself, which
+rather defeats the purpose of the exercise!).
+
+\Question[Q-matchbrak]{My brackets don't match}
+
+\AllTeX{} has a low-level mechanism for matching braces in document
+text. This means you can type something like:
+\begin{quote}
+\begin{verbatim}
+\section{All \emph{OK} now.}
+\end{verbatim}
+\end{quote}
+and know that the first brace (for the argument of \csx{section}) will
+be matched with the last brace, and the internal pair of braces (for
+the argument of \csx{emph}) will be matched with each other. It's all
+very simple.
+
+However, \LaTeX{} has a convention of enclosing optional arguments in
+brackets, as in:
+\begin{quote}
+\begin{verbatim}
+\section[OK]{All \emph{OK} now.}
+\end{verbatim}
+\end{quote}
+These brackets are not matched by \TeX{} mechanisms, despite the
+superficial similarity of their use. As a result,
+straightforward-looking usages like:
+\begin{quote}
+\begin{verbatim}
+\section[All [OK] now]{All \emph{OK} now.}
+\end{verbatim}
+\end{quote}
+aren't \acro{OK} at all~--- the optional argument comes to consist of
+``All [OK'', and \csx{section} takes the single character ``n'' (of
+the first ``now'') as its argument.
+
+Fortunately, \TeX{}'s scanning mechanisms helps us by accepting the
+syntax ``\texttt{\{]\}}'' to `hide' the closing bracket from the
+scanning mechanism that \LaTeX{} uses. In practice, the commonest way
+to use this facility is:
+\begin{quote}
+\begin{verbatim}
+\section[All {[OK]} now]{All \emph{OK} now.}
+\end{verbatim}
+\end{quote}
+since bracing the bracket on its own ``looks odd''.
+
+\LaTeX{} has another argument syntax, even less regular, where the
+argument is enclosed in parentheses, as in:
+\begin{quote}
+\begin{verbatim}
+\put(1,2){foo}
+\end{verbatim}
+\end{quote}
+(a picture environment command).
+
+This mechanism is also prone to problems with matching closing
+parentheses, but the issue seldom arises since such arguments rarely
+contain text. If it were to arise, the same solution (enclosing the
+confused characters in braces) would solve the problem.
+
+\Question[Q-pdf-fig-chars]{Characters disappear from figures in \PDFTeX{}}
+
+You have a \acro{PDF} figure, which you want to use in your
+\PDFLaTeX{} document. When you compile the document, \PDFTeX{}
+complains about ``missing glyphs'', and some (or all) of the labelling
+text or symbols in the original figure is no longer visible.
+
+What has happened is:
+\begin{enumerate}
+\item Your figure file (say \File{fig.pdf}) has a font \File{font.pfb}
+ embedded in it.
+\item \PDFTeX{} notes that it has \File{font.pfb} on disc, and loads
+ that in place of the copy in \File{fig.pdf}.
+\item It turns out that the copy in \File{fig.pdf} has glyphs that
+ aren't in \File{font.pfb} on disc, so that you get errors while
+ compiling and you see that characters are missing when you view the
+ output. (\PDFTeX{} can't know that the fonts are different, since
+ they have the same name.)
+\end{enumerate}
+Which is all very undesirable.
+
+\PDFTeX{} does this to keep file sizes down: suppose you have a
+document that loads figures \File{fig1.pdf} and \File{fig2.pdf}; both
+of those use font \File{font.pfb}. If \PDFTeX{} takes no action,
+there will be \emph{two} copies of \File{font.pfb} in the output.
+(If your document also uses the font, there could be three copies.)
+
+A real case is the \acro{URW} font \File{NimbusRomNo9L-Regu} (a clone
+of Times Roman), which is available in a version with Cyrillic
+letters, while the version in \TeX{} distributions doesn't have those
+letters. Both versions, as distributed, have the same name.
+
+The simple (``quick and dirty'') solution is to add the command
+\begin{quote}
+ \csx{pdfinclusioncopyfonts}\texttt{=1}
+\end{quote}
+to the preamble of your document.
+
+The ``real'' solution is that one or other font should be renamed. In
+either case, this would require that you reconfigure some program's
+(\TeX{}'s or your drawing package's) font tables~--- inevitably a
+tiresome job.
+
+\Question[Q-emptynum]{I asked for ``empty'', but the page is numbered}
+
+If you use \cmdinvoke{pagestyle}{empty} and you find some pages are
+numbered anyway, you are probably encountering one of the style
+decisions built into the standard \LaTeX{} classes: that certain
+special pages should always appear with \cmdinvoke{pagestyle}{plain},
+with a page number at the centre of the page foot. The special pages
+in question are those (in \Class{article} class) containing a
+\csx{maketitle}, or (in \Class{book} and \Class{report} classes)
+\csx{chapter} or \csx{part} commands.
+
+The simple solution is to reissue the page style \emph{after} the
+command, with effect for a single page, as, for example (in
+\Class{article}):
+\begin{quote}
+\begin{verbatim}
+\maketitle
+\thispagestyle{empty}
+\end{verbatim}
+\end{quote}
+or (in \Class{book} or \Class{report})
+\begin{quote}
+\begin{verbatim}
+\chapter{foo bar}
+\thispagestyle{empty}
+\end{verbatim}
+\end{quote}
+A similar technique doesn't work for a \Class{book} or \Class{report}
+\csx{part} command pages. For that, and for other detail, take look
+at ``\Qref*{getting rid of page numbers}{Q-nopageno}''.
+
+\subsection{Common misunderstandings}
+
+\Question[Q-include]{What's going on in my \csx{include} commands?}
+
+The original \LaTeX{} provided the \csx{include} command to address the
+problem of long documents: with the relatively slow computers of the
+time, the companion \csx{includeonly} facility was a boon. With the
+vast increase in computer speed, \csx{includeonly} is less valuable
+(though it still has its place in some very large projects).
+Nevertheless, the facility is retained in current \LaTeX{}, and causes
+some confusion to those who misunderstand it.
+
+In order for \csx{includeonly} to work, \csx{include} makes a separate
+\extension{aux} file for each included file, and makes a `checkpoint' of
+important parameters (such as page, figure, table and footnote
+numbers). As a direct result, it \emph{must} clear the current page
+both before and after the \csx{include} command. (The requirement
+derives from the difficulties of % ! line break
+\begin{hyperversion}
+ \Qref*{observing page numbers}{Q-wrongpn}.)
+\end{hyperversion}
+\begin{flatversion}
+ observing page numbers~--- see \Qref{}{Q-wrongpn}.)
+\end{flatversion}
+What's more, this mechanism doesn't work if a \csx{include} command
+appears in a file that was \csx{include}d itself: \LaTeX{} diagnoses
+this as an error.
+
+So, we can now answer the two commonest questions about \csx{include}:
+\begin{itemize}
+\item Why does \LaTeX{} throw a page before and after \csx{include}
+ commands?
+
+ Answer: because it has to. If you don't like it, replace the
+ \csx{include} command with \csx{input}~--- you won't be able to use
+ \csx{includeonly} any more, but you probably don't need it anyway, so
+ don't worry.
+\begin{htmlversion}
+
+\end{htmlversion}
+\item Why can't I nest \csx{include}d files?~--- I always used to be
+ able to under \LaTeXo{}.
+
+ Answer: in fact, you couldn't, even under \LaTeXo{}, but the failure
+ wasn't diagnosed. However, since you were happy with the behaviour
+ under \LaTeXo{}, replace the \csx{include} commands with \csx{input}
+ commands (with \csx{clearpage} as appropriate).
+\end{itemize}
+
+
+\Question[Q-paraparam]{Why does it ignore paragraph parameters?}
+
+When \TeX{} is laying out text, it doesn't work from word to word, or
+from line to line; the smallest complete unit it formats is the
+paragraph. The paragraph is laid down in a buffer, as it appears, and
+isn't touched further until the end-paragraph marker is processed.
+It's at this point that the paragraph parameters have effect; and it's
+because of this sequence that one often makes mistakes that lead to
+the paragraph parameters not doing what one would have hoped (or
+expected).
+
+Consider the following sequence of \LaTeX{}:
+\begin{quote}
+\begin{verbatim}
+{\raggedright % declaration for ragged text
+Here's text to be ranged left in our output,
+but it's the only such paragraph, so we now
+end the group.}
+
+Here's more that needn't be ragged...
+\end{verbatim}
+\end{quote}
+\TeX{} will open a group, and impose the ragged-setting parameters within
+that group; it will then save a couple of sentences of text and
+close the group (thus restoring the previous value of the
+parameters that \csx{raggedright} set). Then \TeX{} encounters a blank
+line, which it knows to treat as a \csx{par} token, so it typesets the
+two sentences; but because the enclosing group has now been closed,
+the parameter settings have been lost, and the paragraph will be
+typeset normally.
+
+The solution is simple: close the paragraph inside the group, so that
+the setting parameters remain in place. An appropriate way of doing
+that is to replace the last three lines above with:
+\begin{quote}
+\begin{verbatim}
+end the group.\par}
+Here's more that needn't be ragged...
+\end{verbatim}
+\end{quote}
+In this way, the paragraph is completed while \csx{raggedright}'s
+parameters are still in force within the enclosing group.
+
+Another alternative is to define an environment that does the
+appropriate job for you. For the above example, \LaTeX{} already
+defines an appropriate one:
+\begin{quote}
+\begin{verbatim}
+\begin{flushleft}
+Here's text to be ranged left...
+\end{flushleft}
+\end{verbatim}
+\end{quote}
+
+In fact, there are a number of parameters for which \TeX{} only
+maintains one value per paragraph. A tiresome one is the set of upper
+case/lower case translations, which (oddly enough) constrains
+hyphenation of mutilingual texts. Another that regularly creates
+confusion is \Qref*{\csx{baselineskip}}{Q-baselinepar}.
+
+\Question[Q-casechange]{Case-changing oddities}
+
+\TeX{} provides two primitive commands \csx{uppercase} and
+\csx{lowercase} to change the case of text; they're not much used, but
+are capable creating confusion.
+
+The two commands do not expand the text that is their parameter~---
+the result of \cmdinvoke{uppercase}{abc} is `\texttt{ABC}', but
+\cmdinvoke{uppercase}{\csx{abc}} is always `\csx{abc}', whatever the
+meaning of \csx{abc}. The commands are simply interpreting a table of
+equivalences between upper- and lowercase characters.
+They have (for example) no mathematical sense, and
+\begin{quote}
+\begin{verbatim}
+\uppercase{About $y=f(x)$}
+\end{verbatim}
+\end{quote}
+will produce
+\begin{quote}
+\begin{verbatim}
+ABOUT $Y=F(X)$
+\end{verbatim}
+\end{quote}
+which is probably not what is wanted.
+
+In addition, \csx{uppercase} and \csx{lowercase} do not deal very well
+with non-American characters, for example
+\cmdinvoke{uppercase}{\csx{ae}} is the same as \csx{ae}.
+
+\LaTeX{} provides commands \csx{MakeUppercase} and \csx{MakeLowercase}
+which fixes the latter problem. These commands are used in the
+standard classes to produce upper case running heads for chapters
+and sections.
+
+Unfortunately \csx{MakeUppercase} and \csx{MakeLowercase} do not solve
+the other problems with \csx{uppercase}, so for example a section
+title containing \cmdinvoke{begin}{tabular} \dots{}
+\cmdinvoke{end}{tabular} will produce a running head containing
+\cmdinvoke{begin}{TABULAR}. The simplest solution to this problem is
+using a user-defined command, for example:
+\begin{quote}
+\begin{verbatim}
+\newcommand{\mytable}{\begin{tabular}...
+ \end{tabular}}
+\section{A section title \protect\mytable{}
+ with a table}
+\end{verbatim}
+\end{quote}
+Note that \csx{mytable} has to be protected, otherwise it will be
+expanded and made upper case; you can achieve the same result by
+declaring it with \csx{DeclareRobustCommand}, in which case the
+\csx{protect} won't be necessary.
+
+David Carlisle's \Package{textcase} package
+addresses many of these problems in a transparent way. It defines
+commands \csx{MakeTextUppercase} and \csx{MakeTextLowercase} which do
+upper- or lowercase, with the fancier features of the \LaTeX{}
+standard \csx{Make*}-commands but without the problems
+mentioned above. Load the package with
+\cmdinvoke{usepackage}[overload]{textcase}, and it will redefine the \LaTeX{}
+commands (\emph{not} the \TeX{} primitive commands \csx{uppercase} and
+\csx{lowercase}), so that section headings and the like don't produce
+broken page headings.
+\begin{ctanrefs}
+\item[textcase.sty]\CTANref{textcase}
+\end{ctanrefs}
+
+\Question[Q-splitfoot]{Why does \LaTeX{} split footnotes across pages?}
+
+\LaTeX{} splits footnotes when it can think of nothing better to do.
+Typically, when this happens, the footnote mark is at the bottom of
+the page, and the complete footnote would overfill the page. \LaTeX{}
+could try to salvage this problem by making the page short of both the
+footnote and the line with the footnote mark, but its priorities told
+it that splitting the footnote would be preferable.
+
+As always, the best solution is to change your text so that the
+problem doesn't occur in the first place. Consider whether the text
+that bears the footnote could move earlier in the current page, or on
+to the next page.
+
+If this isn't possible, you might want to change \LaTeX{}'s perception
+of its priorities: they're controlled by
+\csx{interfootnotelinepenalty}~--- the larger it is, the less willing
+\LaTeX{} is to split footnotes.
+
+Setting
+\begin{quote}
+\begin{verbatim}
+\interfootnotelinepenalty=10000
+\end{verbatim}
+\end{quote}
+inhibits split footnotes altogether, which will cause `\texttt{Underfull}
+\csx{vbox}' messages unless you also specify \csx{raggedbottom}. The
+default value of the penalty is \texttt{100}, which is rather mild.
+
+An alternative technique is to juggle with the actual size of the
+pages. \csx{enlargethispage} changes the size of the current page by
+its argument (for example, you might say
+\cmdinvoke{enlargethispage}{\csx{baselineskip}} to add a single line
+to the page, but you can use any ordinary \TeX{} length such as
+\texttt{15mm} or \texttt{-20pt} as argument). Reducing the size of
+the current page could force the offending text to the next page;
+increasing the size of the page may allow the footnote to be included
+in its entirety. It may be necessary to change the size of more than
+one page.
+
+The \Package{fnbreak} package detects (and generates warnings about)
+split footnotes.
+\begin{ctanrefs}
+\item[fnbreak.sty]\CTANref{fnbreak}
+\end{ctanrefs}
+
+\Question[Q-marginparside]{Getting \csx{marginpar} on the right side}
+
+In an ideal world, marginal notes would be in ``analogous'' places on
+every page: notes on an even-side page would be in the left margin,
+while those on an odd-side page would be in the right margin. A
+moment's thought shows that a marginal note on the left needs to be
+typeset differently from a marginal note on the right. The \LaTeX{}
+\csx{marginpar} command therefore takes two arguments in a
+\texttt{twoside} documents: % beware line break
+\cmdinvoke*{marginpar}[left text]{right text}. \LaTeX{} uses the
+``obvious'' test to
+get the \csx{marginpar}s in the correct margin, but a booby-trap arises
+because \TeX{} runs its page maker asynchronously. If a
+\csx{marginpar} is processed while page \ensuremath{n} is being built, but
+doesn't get used until page \ensuremath{n}+1, then the \csx{marginpar} will turn
+up on the wrong side of the page. This is an instance of a general
+problem: see
+% beware line break
+``\Qref*{finding if you're on an odd or an even page}{Q-oddpage}''.
+
+The solution to the problem is for \LaTeX{} to `remember' which side
+of the page each \csx{marginpar} \emph{should} be on. The
+\Package{mparhack} package does this, using label-like marks stored in
+the \extension{aux} file; the \Class{memoir} class does likewise.
+\begin{ctanrefs}
+\item[memoir.cls]\CTANref{memoir}
+\item[mparhack.sty]\CTANref{mparhack}
+\end{ctanrefs}
+
+\Question[Q-misschar]{Where have my characters gone?}
+
+You've typed some apparently reasonable text and processed it, but the
+result contains no sign of some of the characters you typed. A likely
+reason is that the font you selected just doesn't have a
+representation for the character in question.
+
+For example, if I type ``that will be \pounds{}44.00'' into an ordinary
+\AllTeX{} document, or if I select the font \texttt{rsfs10} (which contains
+uppercase letters only) and type pretty much anything, the \pounds{}
+sign, or any lowercase letters or digits will not appear in the
+output. There's no actual error message, either: you have to read the
+log file, where you'll find cryptic little messages like
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+Missing character: There is no ^^a3 in font cmr10!
+Missing character: There is no 3 in font rsfs10!
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+Missing character:
+ There is no ^^a3 in font cmr10!
+Missing character:
+ There is no 3 in font rsfs10!
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+(the former demonstrating my \TeX{}'s unwillingness to deal in characters
+which have the eighth bit set, while the \texttt{rsfs10} example shows that
+\TeX{} will log the actual character in error, if it thinks it's
+possible).
+
+Somewhat more understandable are the diagnostics you may get from
+\Package{dvips} when using the \acro{OT}1 and \acro{T}1 versions of
+fonts that were supplied in Adobe standard encoding:
+\begin{quote}
+\begin{verbatim}
+dvips: Warning: missing glyph `Delta'
+\end{verbatim}
+\end{quote}
+The process that generates the metrics for using the fonts generates
+an instruction to \Package{dvips} to produce these diagnostics, so
+that their non-appearance in the printed output is less surprising
+than it might be. Quite a few glyphs provided in Knuth's text
+encodings and in the Cork encoding are not available in the Adobe
+fonts. In these cases, there \emph{is} a typeset sign of the
+character: \ProgName{dvips} produces a black rectangle of whatever
+size the concocted font file has specified.
+
+\Question[Q-rerun]{``Rerun'' messages won't go away}
+
+The \LaTeX{} message ``Rerun to get crossreferences right'' is
+supposed to warn the user that the job needs to be processed again,
+since labels seem to have changed since the previous run. (\LaTeX{}
+compares the labels it has created this time round with what it found
+from the previous run when it started; it does this comparison at
+\cmdinvoke{end}{document}.)
+
+Sometimes, the message won't go away: however often you reprocess your
+document, \LaTeX{} still tells you that ``Label(s) may have
+changed''. This can sometimes be caused by a broken package: both
+\Package{footmisc} (with the \pkgoption{perpage} option) and \Package{hyperref}
+have been known to give trouble, in the past: if you are using either,
+check you have the latest version, and upgrade if possible.
+
+However, there \emph{is} a rare occasion when this error can happen
+as a result of pathological structure of the document itself. Suppose
+you have pages numbered in roman, and you add a reference to a label
+on page ``ix'' (9). The presence of the reference pushes the thing
+referred to onto page ``x'' (10), but since that's a shorter reference
+the label moves back to page ``ix'' at the next run. Such a sequence
+can obviously not terminate.
+
+The only solution to this problem is to make a small change to your
+document (something as small as adding or deleting a comma will often
+be enough).
+\begin{ctanrefs}
+\item[footmisc.sty]\CTANref{footmisc}
+\item[hyperref.sty]\CTANref{hyperref}
+\end{ctanrefs}
+
+\Question[Q-xspace]{Commands gobble following space}
+
+People are forever surprised that simple commands gobble the space
+after them: this is just the way it is. The effect arises from the
+way \TeX{} works, and Lamport describes a solution (place a pair of braces
+after a command's invocation) in the description of \LaTeX{} syntax.
+Thus the requirement is in effect part of the definition of \LaTeX{}.
+
+These \acro{FAQ}s,
+for example, is written in \latex{} for production of a web site. The
+HTML code is generated by a script that \emph{requires} a pair of
+braces, to make a null argument, as in:
+\begin{quote}
+ \cmdinvoke{fred}{\relax} % the \relax prevents {} being gobbled
+ % in html production (sigh)
+ % (we needn't tell them about _that_ ;-)
+\end{quote}
+for almost all macro invocations, regardless
+of whether the following space is required: however, these \acro{FAQ}s
+should not itself be regarded as a model of \latex{} style.
+
+Many users find all those braces become very tedious very
+quickly, and would really rather not type them all.
+
+An alternative structure, that doesn't violate the design of \LaTeX{},
+is to say \csx{fred}\csx{ }~--- the \csx{ } command is ``self
+terminating'' (like \texttt{\bsbs }) and you don't need braces after
+\emph{it}. Thus one can reduce to one the number of extra characters
+one needs to type.
+
+If even that one character is too many, the package \Package{xspace}
+defines a command \csx{xspace} that guesses whether there should have
+been a space after it, and if so introduces that space. So
+% beware line wrap
+``\texttt{fred\csx{xspace} jim}'' produces ``fred jim'', while
+``\texttt{fred\csx{xspace}.\@ jim}'' produces ``fred. jim''. Which
+usage would of course be completely pointless; but you can incorporate
+\csx{xspace} in your own macros:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\usepackage{xspace}
+...
+\newcommand{\restenergy}{\ensuremath{mc^2}\xspace}
+...
+and we find \restenergy available to us...
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\usepackage{xspace}
+...
+\newcommand{\restenergy}%
+ {\ensuremath{mc^2}\xspace}
+...
+and we find \restenergy available to us...
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+The \csx{xspace} command must be the last thing in your macro
+definition (as in the example); it's not completely foolproof, but it
+copes with most obvious situations in running text.
+
+The \Package{xspace} package doesn't save you anything if you use it in
+a macro that appears only once or twice within your document, and it
+is not totally foolproof. (The original author of the package wrote
+it because he had been bitten by lost spaces. He no longer recommends
+its use, simply because of the possibility of error.)
+
+In any case, be
+careful with usage of \csx{xspace}~--- it changes your input syntax,
+which can be confusing, notably to a collaborating author
+(particularly if you create some commands which use it and some which
+don't). No command built into \LaTeX{} or into any
+``standard'' class or package will use \csx{xspace}.
+\begin{ctanrefs}
+\item[xspace.sty]Distributed as part of \CTANref{2etools}[xspace]
+\end{ctanrefs}
+\LastEdit{2013-11-26}
+
+\Question[Q-overfull]{\AllTeX{} makes overfull lines}
+
+When \TeX{} is building a paragraph, it can make several attempts to
+get the line-breaking right; on each attempt it runs the same
+algorithm, but gives it different parameters. You can affect the way
+\TeX{}'s line breaking works by adjusting the parameters: this answer
+deals with the ``tolerance'' and stretchability parameters. The other
+vital `parameter' is the set of hyphenations to be applied: see
+``\Qref*[question]{my words aren't being hyphenated}{Q-nohyph}''
+(and the questions it references) for advice.
+
+If you're getting an undesired ``overfull box'', what has happened is
+that \TeX{} has given up: the parameters you gave it don't allow it to
+produce a result that \emph{doesn't} overfill. In this circumstance,
+Knuth decided the best thing to do was to produce a warning, and to
+allow the user to solve the problem. (The alternative, silently to go
+beyond the envelope of ``good taste'' defined for this run of \TeX{},
+would be distasteful to any discerning typographer.) The user can
+almost always address the problem by rewriting the text that's
+provoking the problem~--- but that's not always possible, and in some
+cases it's impossible to solve the problem without adjusting the
+parameters. This answer discusses the approaches one might take to
+resolution of the problem, on the assumption that you've got the
+hyphenation correct.
+
+The simplest case is where a `small' word fails to break at the end of
+a line; pushing the entire word to a new line isn't going to make much
+difference, but it might make things just bad enough that \TeX{} won't
+do it by default. In such a case on can \emph{try} the \LaTeX{}
+\csx{linebreak} command: it may solve the problem, and if it does, it
+will save an awful lot of fiddling. Otherwise, one needs to adjust
+parameters: to do that we need to recap the details of \TeX{}'s line
+breaking mechanisms.
+
+\TeX{}'s first attempt at breaking lines is performed without even
+trying hyphenation: \TeX{} sets its ``tolerance'' of line breaking
+oddities to the internal value \csx{pretolerance}, and sees what
+happens. If it can't get an acceptable break, \TeX{} adds the
+hyphenation points allowed by the current patterns, and tries again
+using the internal \csx{tolerance} value. If this pass also fails, and
+the internal \csx{emergencystretch} value is positive, \TeX{} will try
+a pass that allows \csx{emergencystretch} worth of extra stretchability
+to the spaces in each line.
+
+In principle, therefore, there are three parameters (other than
+hyphenation) that you can change: \csx{pretolerance}, \csx{tolerance}
+and \csx{emergencystretch}. Both the \texttt{tolerance} values are
+simple numbers, and should be set by \TeX{} primitive count
+assignment~--- for example
+\begin{quote}
+\begin{verbatim}
+\pretolerance=150
+\end{verbatim}
+\end{quote}
+For both, an ``infinite'' tolerance is represented by the value
+\texttt{10}\nothtml{\,}\texttt{000}, but infinite tolerance is rarely
+appropriate, since it can lead to very bad line breaks indeed.
+
+\csx{emergencystretch} is a \TeX{}-internal `dimen' register, and can
+be set as normal for dimens in \plaintex{}; in \LaTeX{}, use
+\csx{setlength}~--- for example:
+\begin{quote}
+\begin{verbatim}
+\setlength{\emergencystretch}{3em}
+\end{verbatim}
+\end{quote}
+
+The choice of method has time implications~--- each of the
+passes takes time, so adding a pass (by changing
+\csx{emergencystretch}) is less desirable than suppressing one (by
+changing \csx{pretolerance}). However, it's unusual nowadays to find a
+computer that's slow enough that the extra passes are really
+troublesome.
+
+In practice, \csx{pretolerance} is rarely used other than to manipulate
+the use of hyphenation; \plaintex{} and \LaTeX{} both set its value
+to \texttt{100}. To suppress the first scan of paragraphs, set
+\csx{pretolerance} to \texttt{-1}.
+
+\csx{tolerance} is often a good method for adjusting spacing;
+\plaintex{} and \LaTeX{} both set its value to \texttt{200}. \LaTeX{}'s
+\csx{sloppy} command sets it to \texttt{9999}, as does the
+\environment{sloppypar} environment. This value is the largest
+available, this side of infinity, and can allow pretty poor-looking
+breaks (this author rarely uses \csx{sloppy} ``bare'', though he does
+occasionally use \environment{sloppypar}~--- that way, the change of
+\csx{tolerance} is confined to the environment). More satisfactory is
+to make small changes to \csx{tolerance}, incrementally, and then to look to
+see how the change affects the result; very small increases can often
+do what's necessary. Remember that \csx{tolerance} is a paragraph
+parameter, so you need to ensure it's actually applied~--- see
+``\Qref*[question]{ignoring paragraph parameters}{Q-paraparam}''.
+\LaTeX{} users could use an environment like:
+\begin{quote}
+\begin{verbatim}
+\newenvironment{tolerant}[1]{%
+ \par\tolerance=#1\relax
+}{%
+ \par
+}
+\end{verbatim}
+\end{quote}
+enclosing entire paragraphs (or set of paragraphs) in it.
+
+The value of \csx{emergencystretch} is added to the assumed
+stretchability of each line of a paragraph, in a further run of the
+paragraph formatter in case that the paragraph can't be made to look
+right any other way. (The extra scan happens if
+\csx{emergencystretch\textgreater0pt}~--- if it's zero or negative, no gain
+could be had from rerunning the paragraph setter.) The example above
+set it to \texttt{3em}; the Computer Modern fonts ordinarily fit three
+space skips to the \texttt{em}, so the change would allow anything up
+to the equivalent of nine extra spaces in each line. In a line with
+lots of spaces, this could be reasonable, but with (say) only three
+spaces on the line, each could stretch to four times its natural
+width. It is therefore clear that \csx{emergencystretch} needs to be
+treated with a degree of caution.
+
+More subtle (but more tricky to manage) are the microtypographic
+extensions provided by \PDFTeX{}. Since \PDFTeX{} is the default
+`engine' for \LaTeX{} and \CONTeXT{} work in all distributions,
+nowadays, the extensions are available to all. There are two
+extensions, margin kerning and font expansion; margin kerning only
+affects the visual effect of the typeset page, and has little effect
+on the ability of the paragraph setter to ``get things right''.
+Font expansion works like a subtler version of the trick that
+\csx{emergencystretch} plays: \PDFTeX{} `knows' that your current font
+may be stretched (or shrunk) to a certain extent, and will do that
+``on the fly'' to optimise the setting of a paragraph. This is a
+powerful tool in the armoury of the typesetter.
+
+As mentioned above, the microtypographic extensions are tricky beasts
+to control; however, the \Package{microtype} package relieves the user
+of the tedious work of specifying how to perform margin adjustments
+and how much to scale each font~\dots{}\@ for the fonts the package
+knows about; it's a good tool, and users who can take on the
+specification of adjustments for yet more fonts are always welcome.
+\begin{ctanrefs}
+\item[microtype.sty]\CTANref{microtype}
+\end{ctanrefs}
+
+\Question[Q-exscale]{Maths symbols don't scale up}
+
+By default, the ``large'' maths symbols stay at the same size
+regardless of the font size of the text of the document. There's good
+reason for this: the \FontName{cmex} fonts aren't really designed to
+scale, so that \TeX{}'s maths placement algorithms don't perform as
+well as they might when the fonts are scaled.
+
+However, this behaviour confounds user expectations, and can lead to
+slightly odd-looking documents. If you want the fonts to scale,
+despite the warning above, use the \Package{exscale} package~--- just
+loading it is enough.
+%%
+%% (Note: if you are using bitmap versions of the \FontName{cmex} fonts,
+%% you will find extra bitmaps are generated. The extended sizes are not
+%% ordinarily generated for any other purpose.)
+\begin{ctanrefs}
+\item[exscale.sty]Part of the \LaTeX{} distribution.
+\end{ctanrefs}
+
+\Question[Q-linespread]{Why doesn't \csx{linespread} work?}
+
+The command \cmdinvoke*{linespread}{factor} is supposed to multiply
+the current \csx{baselineskip} by \meta{factor}; but, to all
+appearances, it doesn't.
+
+In fact, the command is equivalent to
+\cmdinvoke{renewcommand}{\csx{baselinestretch}}{factor}: written that
+way, it somehow feels less surprising that the effect isn't immediate.
+The \csx{baselinestretch} factor is only used when a font is selected;
+a mere change of \csx{baselinestretch} doesn't change the font, any
+more than does the command
+\cmdinvoke*{fontsize}{size}{baselineskip}~--- you have to follow
+either command with \csx{selectfont}. So:
+\begin{quote}
+\begin{verbatim}
+\fontsize{10}{12}%
+\selectfont
+\end{verbatim}
+\end{quote}
+or:
+\begin{quote}
+\begin{verbatim}
+\linespread{1.2}%
+\selectfont
+\end{verbatim}
+\end{quote}
+Of course, a package such as \Package{setspace}, whose job is to
+manage the baseline, will deal with all this stuff~--- see
+``\Qref*[question]{managing double-spaced documents}{Q-linespace}''. If
+you want to avoid \Package{setspace}, beware the behaviour of
+linespread changes within a paragraph: read % ! line break
+``\Qref*[question]{\csx{baselineskip} is a paragraph parameter}{Q-baselinepar}''.
+\begin{ctanrefs}
+\item[setspace.sty]\CTANref{setspace}
+\end{ctanrefs}
+
+\Question[Q-baselinepar]{Only one \csx{baselineskip} per paragraph}
+
+The \csx{baselineskip}, which determines the space between lines, is
+not (as one might hope) a property of a line, but of a paragraph. As
+a result, in a \texttt{10pt} (nominal) document (with a default
+\csx{baselineskip} of \texttt{12pt}), a single character with a larger
+size, as:
+\begin{quote}
+\begin{verbatim}
+{\Huge A}
+\end{verbatim}
+\end{quote}
+will be squashed into the paragraph: \TeX{} will make sure it doesn't
+scrape up against the line above, but won't give it ``room to
+breathe'', as it does the text at standard size; that is, its size
+(\texttt{24.88pt}) is taken account of, but its \csx{baselineskip}
+(\texttt{30pt}) isn't. This problem may be solved by a \emph{strut}:
+the name comes from movable metal typography, and refers to a spacer
+that held the boxes (that contained the metal character shapes) apart.
+Every time you change font size, \LaTeX{} redefines the command
+\csx{strut} to provide the equivalent of a metal-type strut for the
+size chosen. So for the example above, we would type
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+ {\Huge A\strut}
+ ... paragraph continues ...
+\end{verbatim}
+\end{quote}
+This technique \emph{only} works for such very short intrusions; if
+you need several lines, you should convert your intrusion into a
+\environment{quote} environment, since it's not possible to provide a
+\csx{strut} command for every line of the intrusion, in a sensible
+way, so proceed by:
+\begin{quote}
+\begin{verbatim}
+\begin{quote}
+ \Huge A LENGTHY TEXT ...
+ SHOUTING AT THE READER!
+\end{quote}
+\end{verbatim}
+\end{quote}
+
+The contrary case:
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+{\footnotesize Extended interjection ...
+ ... into the paragraph.}
+ ... paragraph continues ...
+\end{verbatim}
+\end{quote}
+will look wrong, since the \texttt{8pt} interjection will
+end up set on the \texttt{12pt} \csx{baselineskip} of the paragraph,
+rather than its preferred \texttt{8.5pt}. A \csx{strut} here is no
+help: there is no such thing as a ``negative strut'', that draws lines
+together, so once more, one falls back on the \environment{quote} to
+separate the interjection:
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+\begin{quote}
+ \footnotesize Extended interjection ...
+ ... into the paragraph.
+\end{quote}
+... paragraph continues ...
+\end{verbatim}
+\end{quote}
+
+The same effect is at work when we have something like:
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+ ... paragraph body ends.
+{\footnotesize Comment on the paragraph.}
+
+Next paragraph starts...
+\end{verbatim}
+\end{quote}
+which will set the body of the first paragraph on the constricted
+\csx{baselineskip} of the \csx{footnotesize} comment. Solve this
+problem by ending the initial paragraph before starting the comment:
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+ ... paragraph body ends.
+\par\nothtml{\noindent}
+{\footnotesize Comment on the paragraph.}
+
+Next paragraph starts...
+\end{verbatim}
+\end{quote}
+(We suggest \csx{noindent} to make the comment look as if it is part
+of the paragraph it discusses; omit \csx{noindent} if that is inappropriate.)
+
+A variation of the previous issue arises from a paragraph whose size
+is different from those around it:
+\begin{quote}
+\begin{verbatim}
+{\Large (Extended) IMPORTANT DETAILS ...}
+
+Main body of text...
+\end{verbatim}
+\end{quote}
+Again, the problem is solved by ending the paragraph in the same group
+as the text with a different size:
+\begin{quote}
+\begin{verbatim}
+{\Large (Extended) IMPORTANT DETAILS ...\par}
+
+Main body of text...
+\end{verbatim}
+\end{quote}
+
+\Question[Q-tocloftwrong]{Numbers too large in table of contents, etc.}
+
+\keywords{memoir table-of-contents spacing}
+\LaTeX{} constructs the table of contents, list of figures, tables,
+and similar tables, on the basis of a layout specified in the class.
+As a result, they do \emph{not} react to the sizes of things in them,
+as they would if a \environment{tabular} environment (or something
+similar) was used.
+
+This arrangement can provoke problems, most commonly with deep section
+nesting or very large page numbers: the numbers in question just don't
+fit in the space allowed for them in the class.
+
+A separate answer discusses % ! line break
+\nothtml{re-designing the tables ---} % ! line break
+\Qref{re-designing the tables}{Q-tocloft}\nothtml{ ---}
+and techniques from that answer may be employed to make the numbers
+fit:
+\begin{quote}
+\begin{verbatim}
+\setlength\cftsectionnumwidth{4em}
+\end{verbatim}
+\end{quote}
+
+The same command may be employed in documents typeset with the
+\Class{memoir} package (by the same author as \Package{tocloft}).
+
+\Class{Memoir} has another mechanism for the job:
+\cmdinvoke{cftsetindents}{\meta{kind}}{indent}{numwidth}. Here
+\emph{kind} is \texttt{chapter}, \texttt{section}, or whatever; the
+\emph{indent} specifies the `margin' before the entry starts; and the
+\emph{width} is of the box into which the number is typeset (so needs
+to be wide enough for the largest number, with the necessary spacing
+to separate it from what comes after it in the line.
+\begin{ctanrefs}
+\item[memoir.cls]\CTANref{memoir}
+\item[tocloft.sty]\CTANref{tocloft}
+\end{ctanrefs}
+\LastEdit{2013-08-20}
+
+\Question[Q-gutter]{Why is the inside margin so narrow?}
+
+If you give the standard classes the \pkgoption{twoside} option, the
+class sets the margins narrow on the left of odd-numbered pages, and
+on the right of even-numbered pages. This is often thought to look
+odd, but it is quite right.
+
+The idea is that the typographic urge for symmetry should also apply
+to margins: if you lay an even numbered page to the left of an
+odd-numbered one, you will see that you've three equal chunks of
+un-printed paper: the left margin of the even page, the right margin
+of the odd page, and the two abutting margins together.
+
+This is all very fine in the abstract, but in practical book(let)
+production it only works ``sometimes''.
+
+If your booklet is produced on double-width paper and stapled, the
+effect will be good; if your book(let) is produced using a so-called
+``perfect'' binding, the effect will again be good.
+
+However, almost any ``quality'' book-binder will need some of your
+paper to grab hold of, and a book bound in such a way won't exhibit
+the treasured symmetry unless you've done something about the margin
+settings.
+
+The packages recommended in % ! line break
+``\Qref*{setting up margins}{Q-marginpkgs}'' mostly have provision for
+a ``binding offset'' or a ``binding correction''~--- search for
+``binding'' in the manuals (\Package{vmargin} doesn't help, here).
+
+If you're doing the job by hand (see % ! line break
+\Qref[question]{manual margin setup}{Q-marginmanual}), the trick is to
+calculate your page and margin dimensions as normal, and then:
+\begin{itemize}
+\item subtract the binding offset from \csx{evensidemargin}, and
+\item add the binding offset to \csx{oddsidemargin}.
+\end{itemize}
+which can be achieved by:
+\begin{quote}
+\begin{verbatim}
+\addtolength{\evensidemargin}{-offset}
+\addtolength{\oddsidemargin}{offset}
+\end{verbatim}
+\end{quote}
+(substituting something sensible like ``\texttt{5mm}'' for
+``\texttt{offset}'', above).
+
+The above may not be the best you can do: you may well choose to
+change the \csx{textwidth} in the presence of the binding offset; but
+the changes do work for constant \csx{textwidth}.
+
+\subsection{Why shouldn't I?}
+
+\Question[Q-t1enc]{Why use \Package{fontenc} rather than \Package{t1enc}?}
+
+In the very earliest days of \LaTeXe{}, the only way to use the
+\acro{T}1 encoding was \Package{t1enc}; with the summer 1994
+``production'' release, the \Package{fontenc} package appeared, and
+provided comprehensive support for use of the encoding.
+
+Nevertheless, the \Package{t1enc} package remains (as part of the
+\LaTeXo{} compatibility code), but it does very little: it merely
+selects font encoding \acro{T}1, and leaves to the user the business
+of generating the character codes required.
+
+Generating such character codes could be a simple matter, \emph{if}
+the \acro{T}1 encoding matched any widely-supported encoding standard,
+since in that case, one might expect one's keyboard to generate the
+character codes. However, the \acro{T}1 encoding is a mix of several
+standard encodings, and includes code points in areas of the table
+which standard encodings specifically exclude, so no \acro{T}1
+keyboards have been (or ever will be) manufactured.
+
+By contrast, the \Package{fontenc} package generates the \acro{T}1
+code points from ordinary \LaTeX{} commands (e.g., it generates the
+\texttt{\'e} character codepoint from the command \csx{'}\texttt{e}).
+So, unless you have program-generated \acro{T}1 input (which is almost
+inconceivable), use \cmdinvoke{usepackage}[T1]{fontenc} rather than
+\cmdinvoke{usepackage}{t1enc}.
+
+\Question[Q-why-inp-font]{Why bother with \Package{inputenc} and \Package{fontenc}?}
+
+The standard input encoding for Western Europe (pending the arrival of
+Unicode) is \acro{ISO}~8859--1 (commonly known by the standard's
+subtitle `Latin-1'). Latin-1 is remarkably close, in the codepoints
+it covers, to the \AllTeX{} \acro{T}1 encoding.
+
+In this circumstance, why should one bother with \Package{inputenc}
+and \Package{fontenc}? Since they're pretty exactly mirroring each
+other, one could do away with both, and use just \Package{t1enc},
+despite its \Qref*{shortcomings}{Q-t1enc}.
+
+One doesn't do this for a variety of small reasons:
+\begin{description}
+\item[Confusion] You've been happily working in this mode, and for
+ some reason find you're to switch to writing in German: the effect
+ of using ``\texttt{\ss }'' is somewhat startling, since \acro{T}1
+ and Latin-1 treat the codepoint differently.
+\item[Compatibility] You find yourself needing to work with a
+ colleague in Eastern Europe: their keyboard is likely to be set to
+ produce Latin-2, so that the simple mapping doesn't work.
+\item[Traditional \LaTeX{}] You lapse and write something like
+ \cmdinvoke{'}{e} rather than typing \texttt{\'e}; only \Package{fontenc}
+ has the means to convert this \LaTeX{} sequence into the \acro{T}1
+ character, so an \csx{accent} primitive slips through into the
+ output, and hyphenation is in danger.
+\end{description}
+The \Package{inputenc}--\Package{fontenc} combination seems slow and
+cumbersome, but it's safe.
+
+\Question[Q-eqnarray]{Why not use \environment{eqnarray}?}
+
+The environment \environment{eqnarray} is attractive for the
+occasional user of mathematics in \LaTeX{} documents: it seems to
+allow aligned systems of equations. Indeed it \emph{does} supply such
+things, but it makes a serious mess of spacing. In the system:
+\begin{quote}
+\begin{verbatim}
+\begin{eqnarray}
+ a & = & b + c \\
+ x & = & y - z
+\end{eqnarray}
+\end{verbatim}
+\end{quote}
+the spacing around the ``='' signs is \emph{not} that defined in the
+metrics for the font from which the glyph comes~--- it's
+\csx{arraycolsep}, which may be set to some very odd value for reasons
+associated with real arrays elsewhere in the document.
+
+The user is far better served by the \AMSLaTeX{} bundle, which
+provides an \environment{align} environment, which is designed with
+the needs of mathematicians in mind (as opposed to the convenience of
+\LaTeX{} programmers). For this simple case (\environment{align} and
+other \AMSLaTeX{} alignment environments are capable of far greater
+things), code as:
+\begin{quote}
+\begin{verbatim}
+\begin{align}
+ a & = b + c \\
+ x & = y - z
+\end{align}
+\end{verbatim}
+\end{quote}
+The matter is discussed in more detail in a % ! line break
+\href{http://tug.org/pracjourn/2006-4/madsen/madsen.pdf}{Prac\TeX{} journal paper}
+by Lars Madsen; Stefan Kottwitz offers a % ! line break
+\href{http://texblog.net/latex-archive/maths/eqnarray-align-environment/}{\tex{} blog entry}
+which includes screen shots of the output, convincingly demonstrating
+the problem.
+\begin{ctanrefs}
+\item[AMSLaTeX]\CTANref{amslatex}
+\end{ctanrefs}
+
+\Question[Q-dolldoll]{Why use \csx{[}\,\dots{}\csx{]} in place of \texttt{\$\$}\,\dots{}\,\texttt{\$\$}?}
+
+\LaTeX{} defines inline- and display-maths commands, apparently
+duplicating the \TeX{} primitive maths sequences which surround maths
+commands with single (or pairs of) dollar signs.
+
+In fact, \LaTeX{}'s inline maths grouping, % !line break
+\csx{(}\texttt{ ... }\csx{)}, has (almost) exactly the same effect as the
+\TeX{} primitive version \texttt{\$ ... \$}. (The exception:
+the \LaTeX{} version checks to ensure you don't put \csx{(} and
+\csx{)} the wrong way round; this does occasionally detect errors\dots{}.)
+
+Since this is the case, one often finds \LaTeX{} users, who have some
+experience of using \plaintex{}, merely assuming that \LaTeX{}'s
+display maths grouping \csx{[}\texttt{ ... }\csx{]} may be replaced by
+the \TeX{} primitive display maths \texttt{\$\$ ... \$\$}.
+
+Unfortunately, the assumption is wrong: some \LaTeX{} code needs to
+patch display maths, it can only do so by patching \csx{[} and \csx{]}
+(or their equivalents). Most obviously, the class option \pkgoption{fleqn}
+simply does not work for equations coded using % ! line break
+\texttt{\$\$ ... \$\$}, whether you're using the standard classes
+alone, or using package \Package{amsmath}. Also, the \csx{[} and
+\csx{]} construct has code for rationalising vertical spacing in some
+extreme cases; that code is not provided \texttt{\$\$ ... \$\$}, so if
+you use the \plaintex{} version, you may occasionally observe
+inconsistent vertical spacing. Similar behaviour can bite if you are
+writing a \emph{proof}; placing the ``\acro{QED} symbol'' doesn't work
+if it is in \texttt{\$\$}-displayed maths.
+
+There are more subtle effects (especially with package
+\Package{amsmath}), and the simple rule is ``use % ! line break
+\csx{[}\texttt{ ... }\csx{]} (at least) whenever displayed maths is
+needed in \LaTeX{}''.
+
+(Note that the sequence \csx{[}\texttt{ ... }\csx{]} is duplicated by
+the \environment{displaymath} environment, which can be said to ``look
+nicer'', and actually \emph{describes} what's being done.)
+\LastEdit{2013-06-05}
+
+\Question[Q-2letterfontcmd]{What's wrong with \csx{bf}, \csx{it}, etc.?}
+
+The font-selection commands of \LaTeXo{} were \csx{rm}, \csx{sf},
+\csx{tt}, \csx{it}, \csx{sl}, \csx{em} and \csx{bf}; they were modal
+commands, so you used them as:
+\begin{quote}
+\begin{verbatim}
+{\bf Fred} was {\it here\/}.
+\end{verbatim}
+\end{quote}
+with the font change enclosed in a group, so as to limit its effect;
+note the italic correction command \csx{/} that was necessary at the
+end of a section in italics.
+
+At the release of \LaTeXe{} in summer 1994, these simple commands were
+deprecated, but recognising that their use is deeply embedded in the
+brains of \LaTeX{} users, the commands themselves remain in \LaTeX{},
+\emph{with their \LaTeXo{} semantics}. Those semantics were part of
+the reason they were deprecated: each \csx{\emph{xx}} overrides
+any other font settings, keeping only the size. So, for example,
+\begin{quote}
+\begin{verbatim}
+{\bf\it Here we are again\/}
+\end{verbatim}
+\end{quote}
+ignores \csx{bf} and produces text in italic, medium weight (and the
+italic correction has a real effect), whereas
+\begin{quote}
+\begin{verbatim}
+{\it\bf happy as can be\/}
+\end{verbatim}
+\end{quote}
+ignores \csx{it} and produces upright text at bold weight (and the
+italic correction has nothing to do). The same holds if you mix
+\LaTeXe{} font selections with the old style commands:
+\begin{quote}
+\begin{verbatim}
+\textbf{\tt all good friends}
+\end{verbatim}
+\end{quote}
+ignores the \csx{textbf} that encloses the text, and produces
+typewriter text at medium weight.
+
+So why are these commands deprecated?~--- it is because of confusions
+such as that in the last example. The alternative (\LaTeXe{})
+commands are discussed in the rest of this answer.
+
+\LaTeXe{}'s font commands come in two forms: modal commands and
+text-block commands. The default set of modal commands offers weights
+\csx{mdseries} and \csx{bfseries}, shapes \csx{upshape},
+\csx{itshape}, \csx{scshape} and \csx{slshape}, and families
+\csx{rmfamily}, \csx{sffamily} and \csx{ttfamily}. A font selection
+requires a family, a shape and a series (as well as a size, of
+course). A few examples
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+{\bfseries\ttfamily
+ and jolly good company!}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+{\bfseries\ttfamily and jolly good company!}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+produces bold typewriter text (but note the lack of a % ! line break, big time
+\begin{narrowversion} % non hyper version
+ bold typewriter font~--- \Qref{}{Q-bold-extras}~---
+\end{narrowversion}
+\begin{wideversion}
+ \Qref{bold typewriter font}{Q-bold-extras}
+\end{wideversion}
+in the default Computer Modern fonts), or
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+{\slshape\sffamily
+ Never mind the weather\/}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+{\slshape\sffamily Never mind the weather\/}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+(note the italic correction needed on slanted fonts, too).
+
+\LaTeXe{}'s text block commands take the first two letters of the
+modal commands, and form a \csx{text}\emph{\texttt{xx}} command from
+them. Thus \csx{bfseries} becomes \cmdinvoke*{textbf}{text},
+\csx{itshape} becomes \cmdinvoke*{textit}{text}, and \csx{ttfamily}
+becomes \cmdinvoke*{texttt}{text}. Block commands may be nested, as:
+\begin{quote}
+\begin{verbatim}
+\textit{\textbf{Never mind the rain}}
+\end{verbatim}
+\end{quote}
+to produce bold italic text (note that the block commands supply
+italic corrections where necessary), and they be nested with the
+\LaTeXe{} modal commands, too:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+\texttt{\bfseries
+ So long as we're together}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\texttt{\bfseries So long as we're together}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+for bold typewriter, or
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+{\slshape\textbf{%
+ Whoops! she goes again}\/}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+{\slshape \textbf{Whoops! she goes again}\/}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+for a bold slanted instance of the current family (note the italic
+correction applied at the end of the modal command group, again).
+
+The new commands (as noted above) override commands of the same type.
+In almost all cases, this merely excludes ludicrous ideas such as
+``upright slanted'' fonts, or ``teletype roman'' fonts. There are a
+couple of immediate oddities, though. The first is the conflict
+between \csx{itshape} (or \csx{slshape}) and \csx{scshape}: while many
+claim that an italic small-caps font is typographically unsound, such
+fonts do exist. Daniel Taupin's \Package{smallcap} package enables
+use of the instances in the \Qref*{\acro{EC} fonts}{Q-ECfonts}, and
+similar techniques could be brought to bear on many other font sets.
+The second is the conflict between \csx{upshape} and \csx{itshape}:
+Knuth actually offers an upright-italic font which \LaTeX{} uses for
+the ``\pounds{}'' symbol in the default font set. The combination is
+sufficiently weird that, while there's a defined font shape, no
+default \LaTeX{} commands exist; to use the shape, the (eccentric) user
+needs \LaTeX{}'s simplest font selection commands:
+\begin{quote}
+\begin{narrowversion}
+\begin{verbatim}
+{\fontshape{ui}\selectfont
+ Tra la la, di dee}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+{\fontshape{ui}\selectfont Tra la la, di dee}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+\begin{ctanrefs}
+\item[smallcap.sty]\CTANref{smallcap}
+\end{ctanrefs}
+
+\Question[Q-newfont*]{What's wrong with \csx{newfont}?}
+
+If all else fails, you \emph{can} specify a font using the \LaTeX{}
+\csx{newfont} command. The font so specified doesn't fit into the
+\LaTeX{} font selection mechanism, but the technique can be tempting
+under several circumstances. The command is merely the thinnest of
+wrappers around the \csx{font} primitive, and doesn't really fit with
+\LaTeX{} at all. A simple, but really rather funny, example of the
+problems it poses, may be seen in:
+\begin{quote}
+\begin{verbatim}
+\documentclass[10pt]{article}
+\begin{document}
+\newfont{\myfont}{cmr17 scaled 2000}
+\myfont
+\LaTeX
+\end{document}
+\end{verbatim}
+\end{quote}
+(the reader is encouraged to try this). The ``A'' of \csx{LaTeX} pretty
+much disappears: \LaTeX{} chooses the size on the ``A'' according to
+\emph{its} idea of the font size (10pt), but positions it according to
+the dimensions of ``\csx{myfont}'', which is more than three times
+that size.
+
+Another ``\csx{myfont}'' example arises from an entirely different
+source. The mini-document:
+\begin{quote}
+\begin{verbatim}
+\documentclass{article}
+\begin{document}
+\newfont{\myfont}{ecrm1000}
+{\myfont voil\`a}
+\end{document}
+\end{verbatim}
+\end{quote}
+gives you ``German low double quotes'' (under the ``a'') in place of
+the grave accent. This happens because \FontName{ecrm1000} is in a
+different \Qref*{font encoding}{Q-whatenc} than \LaTeX{} is
+expecting~--- if you use the \LaTeX{} \Package{fontenc} package to
+select the \acro{EC} fonts, all these tiresome encoding issues are
+solved for you, behind the scenes.
+
+There does however remain a circumstance when you will be tempted to
+use \csx{newfont}~--- viz., to get a font size that doesn't fall into
+the Knuth standard set of sizes: \LaTeX{} (by default) won't allow you
+to use such a size. Don't despair: see the answer % ! line break
+``\Qref*{arbitrary font sizes}{Q-fontsize}''.
+
+
diff --git a/help/uk-tex-faq/faq.cls b/help/uk-tex-faq/faq.cls
new file mode 100644
index 0000000000..a5ae3cdf54
--- /dev/null
+++ b/help/uk-tex-faq/faq.cls
@@ -0,0 +1,93 @@
+% simple class to format the UK TeX FAQ in two columns
+
+\ProvidesClass{faq}[2002/03/11 v2.0 UK TeX FAQ]
+
+\NeedsTeXFormat{LaTeX2e}[1995/12/01]
+
+\newif\if@patchversion
+\@patchversionfalse
+\DeclareOption{patch}{\@patchversiontrue}
+
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+\ProcessOptions
+
+\LoadClass{article}
+
+\RequirePackage[hyphens,obeyspaces]{url}
+\RequirePackage{multicol,faq}
+
+% now, hack at page layout, taking account of whether we're in a
+% single-column version...
+
+% ****************************************
+% * PAGE LAYOUT *
+% ****************************************
+%
+% (This stuff is hacked from SPQR (et al) in baskerv.cls)
+%
+% SIDE MARGINS: (as is for single column)
+\ifsinglecolumn\else
+\oddsidemargin -2.5pc \evensidemargin -2.5pc
+\marginparwidth 4pc % don't use marginal notes...
+\marginparsep 0.5pc % ...in the UK TUG newsletter
+\fi
+
+% VERTICAL SPACING:
+\topmargin -0.5in % allow half an inch border
+\headheight 0\p@ % we don't bother with headers here ...
+\headsep 0\p@ % ... this ain't a publication
+\topskip 10\p@
+\footskip 15\p@
+
+% DIMENSION OF TEXT:
+
+% vertical dimension
+\textheight \paperheight
+\advance\textheight -1.5in
+%\textheight 250mm % height of text on a page (A4 paper)
+
+% horizontal dimension: pro tem, as is for singlcolumn
+\ifsinglecolumn\else
+\textwidth \paperwidth
+\advance\textwidth -1in
+%\textwidth 180mm % total width of a page (A4 paper)
+
+\columnseprule 0.5\p@ % width of line in the inter-column gutter
+\columnsep 10mm % space between columns
+\tolerance 9999 % make those columns justify
+\fi
+
+% FOOTNOTES:
+\footnotesep 6\p@
+\skip\footins 19.5\p@ plus 12\p@ \@minus \p@
+
+% page footer: include date if patched version
+\def\@twodigit#1{\ifnum#1<10\relax0\fi\number#1}
+\def\faq@patched@date{\@arabic\year-\@twodigit\month-\@twodigit\day}
+\if@patchversion
+ \renewcommand\ps@plain{%
+ \let\@mkboth\@gobbletwo
+ \let\@evenhead\@empty
+ \let\@oddhead\@empty
+ \def\@oddfoot{%
+ \reset@font
+ \hfil
+ \faq@patched@date\ : \thepage
+ \hfil
+ }%
+ \let\@evenfoot\@oddfoot
+ }
+ \let\ps@myplain\ps@plain
+ \pagestyle{myplain}
+\fi
+% little patch generated in investigating a request from a user here
+% in cambridge
+\let\FAQ@@tableofcontents\tableofcontents
+\renewcommand\tableofcontents{{%
+ \let\FAQ@@addvspace\addvspace
+ \def\addvspace##1{%
+ \@tempskipa##1\relax
+ \FAQ@@addvspace{0.1\@tempskipa}%
+ }%
+ \FAQ@@tableofcontents
+}}
diff --git a/help/uk-tex-faq/faq.sty b/help/uk-tex-faq/faq.sty
new file mode 100644
index 0000000000..e057007ae8
--- /dev/null
+++ b/help/uk-tex-faq/faq.sty
@@ -0,0 +1,1281 @@
+% $Id: faq.sty,v 1.140 2014/01/28 18:16:50 rf10 Exp rf10 $
+%
+% This is the LaTeX package that deals with the eccentricities of mark
+% up of the UK TeX FAQ.
+%
+% uses production LaTeX 2e commands
+\NeedsTeXFormat{LaTeX2e}[1994/06/01]% at least!
+\ProvidesPackage{faq}[2007/06/08 v2.4 English TeX FAQ macros]
+
+% this package new requires etex
+\@ifundefined{eTeXversion}{%
+ \PackageError{faq}{This package requires e-TeX}{}%
+}{}
+
+%
+% something affecting fonts: do we use only freely available fonts
+% (i.e., are we going to make the postscript of this publicly
+% available?); the config file could change this setting if
+% necessary. things affected herein are the definition of \MP (for
+% metapost), which isn't currently doable with free fonts, and
+% suppression of boldface versions of the logo fonts.
+\newif\ifpublicversion \publicversiontrue
+
+%
+% what fonts are we going to typeset in?
+\newif\ifboldmathavail
+\InputIfFileExists{faqfont.cfg}% must set \ifboldmathavail if necessary
+ {\typeout{FAQ -- loading font configuration file faqfont.cfg}}
+ {%
+ \RequirePackage[T1]{fontenc}%
+ \RequirePackage{lmodern}% for sans fonts
+ \RequirePackage{mathptmx}
+ \RequirePackage{textcomp}%
+ \AtBeginDocument{%
+ \let\save@textcurrency\textcurrency
+ \def\textcurrency{%
+ {%
+ \fontfamily{lmr}\selectfont
+ \save@textcurrency
+ }%
+ }%
+ }
+ \boldmathavailfalse
+ \IfFileExists{luximono.sty}%
+ {\RequirePackage[scaled=0.85]{luximono}}% not using cmtt-alike
+ {\RequirePackage{sub-luximono}}% load whatever
+ \DeclareRobustCommand{\$}{\char`\$}% otherwise tries to load tctt....
+ \@ifundefined{Dings}{\RequirePackage{pifont}%
+ \def\Dings{\nopagebreak{\footnotesize
+ \dingline{167}}}%
+ }%
+ {}%
+ \DeclareRobustCommand\acro[1]{##1\@{}}
+ }
+
+% debugging (requires etex, like much of this package)
+%\tracingifs=1
+
+% suppress bold maths if they're not available
+\ifboldmathavail\else\let\boldmath\@empty\fi
+
+%
+% true for pdf output
+\newif\ifsinglecolumn
+
+\RequirePackage{ifpdf}
+\ifpdf
+ \PackageInfo{faq}{1-column PDF output\@gobble}
+ \expandafter\singlecolumntrue
+\else
+ \PackageInfo{faq}{2-column DVI output\@gobble}
+ \expandafter\singlecolumnfalse
+\fi
+
+\ifpdf
+ % suppress font list from pdftex
+ \RequirePackage{atveryend}
+ \AtVeryVeryEnd{\batchmode}
+\fi
+
+%
+% if we're doing pdf, set up hyperref package and backdoors that avoid
+% its sillier byproducts...
+\ifpdf
+ \@ifundefined{pdfavoidoverfull}{}{\pdfavoidoverfull=1}
+ \let\@faq@@url\url
+ \urldef\DebianSocialContract\@faq@@url
+ {http://www.debian.org/social_contract#guidelines}
+ \RequirePackage[pdftex%
+ ,colorlinks%
+ ,pdftitle=The\ UK\ TeX\ FAQ%
+ ,linkcolor=blue%
+ ,pdfpagemode=UseNone%
+ ,pdfstartview=FitH%
+% ,bookmarks=false%
+ ,bookmarksnumbered%
+ ]{hyperref}
+ \RequirePackage{pdf14}
+ \usepackage{thumbpdf}
+ \pdfstringdefDisableCommands{%
+ \let\cs\psd@cs
+ \def\csx#1{\textbackslash#1}%
+ \def\marg#1{\textbraceleft#1\textbraceright}%
+ \let\acro\@firstofone
+ \let\ProgName\@firstofone
+ \let\Package\@firstofone
+ \def\meta#1{<#1>}%
+ %
+ \def\WYSIWYG{WYSIWYG}%
+ \def\AMSTeX{AmSTeX}%
+ \def\BibTeX{BibTeX}%
+ \def\bibtex{BibTeX}%
+ \def\PiCTeX{PiCTeX}%
+ \def\pictex{PiCTeX}%
+ \def\CDROM{CD-ROM}%
+ \def\TeXXeT{TeXXeT}%
+ \def\MLTeX{ML-TeX}%
+ \def\MP{MetaPost}%
+ \def\dots{...}%
+ \def\obracesymbol{\{}%
+ \def\cbracesymbol{\}}%
+ \def\,{}%
+ }%
+ \begingroup
+ \lccode`\~=`\|%
+ \lowercase{\endgroup
+ \def\psd@cs~#1~{\textbackslash#1}%
+ }%
+ % adding table of contents to bookmarks
+ \let\Orig@tableofcontents\tableofcontents
+ \def\tableofcontents{%
+ \pdfbookmark[1]{\contentsname}{contents}%
+ \Orig@tableofcontents
+ }%
+ % adding \subsection*{Finding the Files}
+ \AtBeginDocument{%
+ \let\Orig@subsection\subsection
+ \def\subsection{%
+ \@ifstar{\bookmark@subsectionstar}{\Orig@subsection}%
+ }%
+ }%
+ \def\bookmark@subsectionstar#1{%
+ \advance\Hy@linkcounter by 1\relax
+ \pdfbookmark[2]{#1}{subsectionstar.\the\Hy@linkcounter}%
+ \Orig@subsection*{#1}%
+ }%
+\fi
+
+%
+% general support
+%\RequirePackage{calc}
+\RequirePackage{microtype}
+%
+% code for handling logo font
+%% \RequirePackage{mflogo}
+%% \ifpublicversion
+%% \renewcommand{\MP}{Meta\-Post}
+%% \let\faq@@MF\MF
+%% \def\faq@bx{bx}
+%% \DeclareRobustCommand{\MF}{{%
+%% \ifx\f@series\faq@bx
+%% \expandafter\textmd%
+%% \fi
+%% {\faq@@MF}%
+%% }%
+%% }
+%% \fi
+\DeclareRobustCommand\MF{Meta\-font}
+\let\mf\MF
+\DeclareRobustCommand\MP{Meta\-post}
+\let\mp\MP
+\newcommand\ttype{TrueType}
+\newcommand\otype{OpenType}
+\let\textlogo\textmd
+%
+% define substitutes for stupid_names
+\newcommand\LaTeXo{\latex\,2.09}
+ \newcommand\latexo{\latex\,2.09}
+\newcommand\AMSTeX{AMS\TeX}
+\newcommand\AMSLaTeX{AMS\latex}
+ \newcommand\amslatex{AMS\latex}
+\newcommand\BibTeX{Bib\TeX}
+ \newcommand\bibtex{Bib\TeX}
+\newcommand\PiCTeX{PiC\TeX}
+ \newcommand\pictex{PiC\TeX}
+ \newcommand\texlive{\TeX{} Live}
+% and...
+%
+% ifthenelse for the undefined references
+\RequirePackage{ifthen}
+%
+% tables are all long'uns
+\RequirePackage{booktabs}
+%
+% we define conditional stuff using Eijkhout's package
+\RequirePackage{comment}
+\def\CommentCutFile{tmp/comment.cut} % use this in place of ./comment.cut
+\excludecomment{htmlversion}
+\includecomment{typesetversion}
+\ifpdf
+ \includecomment{pdfversion}
+ \includecomment{wideversion}
+ \includecomment{hyperversion}
+ \excludecomment{flatversion}
+ \excludecomment{dviversion}
+ \excludecomment{narrowversion}
+\else
+ \excludecomment{pdfversion}
+ \excludecomment{wideversion}
+ \excludecomment{hyperversion}
+ \includecomment{flatversion} % non-hyper
+ \includecomment{dviversion}
+ \includecomment{narrowversion}
+\fi
+%
+% define commands that behave differently according to the above
+% \begin{hyperversion}
+% \newcommand\quotify[1]{``#1''}
+% \end{hyperversion}
+% \begin{flatversion}
+% \let\quotify\@firstofone
+% \end{flatversion}
+%
+% dummy environment for separating the intro
+\newenvironment{introduction}{}{}
+%
+% but we also want short versions, like LaTeX2HTML's
+\let\htmlonly\@gobble
+\let\nothtml\@firstofone
+\let\latexhtml\@firstoftwo
+\ifpdf
+ \let\narrowonly\@gobble
+ \let\wideonly\@firstofone
+ \let\hyperflat\@firstoftwo
+\else
+ \let\narrowonly\@firstofone
+ \let\wideonly\@gobble
+ \let\hyperflat\@secondoftwo
+\fi
+\let\hyperonly\wideonly
+\let\flatonly\narrowonly
+%
+% the little bit(s) of code that's(re) going to be ignored when the
+% html is generated are enclosed by the following two commands
+\let\htmlignore\relax
+\let\endhtmlignore\relax
+
+%
+% the Baskerville and other logos and abbreviations
+\providecommand\BV{\emph{Baskerville}}
+\providecommand\DANTE{\acro{DANTE}}
+\providecommand\MSDOS{\acro{MS-DOS}}
+\providecommand\CDROM{\acro{CD-ROM}}
+%
+\providecommand\elatex{e-\LaTeX{}}
+\providecommand\plaintex{Plain \TeX{}}
+\providecommand\miktex{MiKTeX}
+\providecommand\texshop{\ProgName{TeXshop}}
+\providecommand\texworks{\ProgName{TeXworks}}
+%
+\newcommand\ctan{\acro{CTAN}}
+\newcommand\tex{\TeX{}}
+%
+\newcommand\macosx{Mac \acro{OS}/X}
+%
+%% \providecommand\TeXXeT{\TeX-{}-X\lower.5ex\hbox{E}\kern-.1667emT\@}
+%\providecommand\MLTeX{ML-\TeX}
+%
+% provided for consistency's sake
+\newcommand\PS{PostScript}
+%
+% to get \\ into example command arguments
+\def\bsbs{\char`\\\char`\\}
+%
+\def\careof{\leavevmode\hbox{\raise.75ex\hbox{c}\kern-.15em
+ /\kern-.125em\smash{\lower.3ex\hbox{o}}}}
+%
+% another silliness:
+\providecommand{\textoslash}{\o}
+%
+% \cs{SMC} \emph{isn't} small caps~--- Barbara Beeton says she thinks
+% of it as ``big small caps''. She says (modulo capitalisation of
+% things\dots):
+% \begin{quote}
+% For the things it's used for, regular small caps are not
+% appropriate~--- they're too small. Real small caps are
+% appropriate for author names (and are so used in continental
+% bibliographies), section headings, running heads, and, on
+% occasion, words to which some emphasis is to be given. \cs{SMC}
+% was designed to be used for acronyms and all-caps abbreviations,
+% which look terrible in small caps, but nearly as bad in all caps
+% in the regular text size. The principle of using ``one size
+% smaller'' than the text size is similar to the design of caps in
+% German~--- where they are smaller relative to lowercase than are
+% caps in fonts intended for English, to improve the appearance of
+% regular text in which caps are used at the heads of all nouns, not
+% just at the beginnings of sentences.
+% \end{quote}
+%
+% We define this in terms of the memory of the size currently selected
+% that's maintained in \cs{@currsize}: if the user does something
+% silly re.~selecting fonts, we'll get the wrong results. The
+% following code is adapted from |relsize.sty| by Donald Arseneau and
+% Matt Swift, from a 2.09 original by Bernie Cosell. (Note that the
+% order of examination of \cs{@currsize} is to get the commonest cases
+% out of the way first.)
+% \begin{macrocode}
+%<!latex2e>\def\SMC{\small}
+%<*latex2e>
+\DeclareRobustCommand\SMC{%
+ \ifx\@currsize\normalsize\small\else
+ \ifx\@currsize\small\footnotesize\else
+ \ifx\@currsize\footnotesize\scriptsize\else
+ \ifx\@currsize\large\normalsize\else
+ \ifx\@currsize\Large\large\else
+ \ifx\@currsize\LARGE\Large\else
+ \ifx\@currsize\scriptsize\tiny\else
+ \ifx\@currsize\tiny\tiny\else
+ \ifx\@currsize\huge\LARGE\else
+ \ifx\@currsize\Huge\huge\else
+ \small\SMC@unknown@warning
+ \fi\fi\fi\fi\fi\fi\fi\fi\fi\fi
+}
+\newcommand\SMC@unknown@warning{\PackageWarning{faq}{Unknown text font
+ size command -- using \string\small}}
+\DeclareRobustCommand\textSMC[1]{{\SMC #1}}
+% \end{macrocode}
+%
+% The \cs{acro} command uses \cs{SMC} as it was originally intended.
+% Note that, since most of these things are uppercase-only names, it
+% fiddles with the spacefactor after inserting its text. font config
+% files may define \cs{acro} otherwise
+%
+% \begin{macrocode}
+\@ifundefined{acro}{%
+ \DeclareRobustCommand\acro[1]{\textSMC{#1}\@}%
+}{}
+% \end{macrocode}
+%
+%\TUGboat (effectively) takes arguments {<empty>}vol(issue)
+\DeclareRobustCommand\TUGboat[1]{\expandafter\@TUGboat\ignorespaces}
+\def\@TUGboat#1(#2){\textsl{TUGboat} \textbf{#1}(#2)}
+%
+% The NTS and eTeX (and for consistency Eplain) logos
+%% \DeclareRobustCommand\NTS{$\mathcal{N}$\lower.5ex\hbox
+%% {$\mathcal{T}$}$\mathcal{S}$\@}
+%% \DeclareRobustCommand\eTeX{{$\varepsilon$}-\TeX}
+%% \DeclareRobustCommand\eTeX{e-\TeX}
+%% \DeclareRobustCommand\Eplain{Eplain}
+%% \DeclareRobustCommand\PDFTeX{\acro{PDF}\TeX}
+%% \DeclareRobustCommand\PDFLaTeX{\acro{PDF}\LaTeX}
+%% \DeclareRobustCommand\CONTeXT{Con\TeX{}t}
+\DeclareRobustCommand\YandY{\acro{Y}\&\acro{Y}}
+
+% non-silly names...
+\renewcommand\TeX{TeX}
+\newcommand\Eplain{Eplain}
+\newcommand\etex{e-\TeX}
+\let\eTeX\etex % some day all the old format will have gone...
+\newcommand\ExTeX{Ex\TeX}
+\newcommand\NTS{NTS}
+\newcommand\PDFTeX{PDF\TeX}
+\newcommand\pdftex{PDF\TeX}
+\newcommand\LuaTeX{Lua\TeX}
+\newcommand\luatex{Lua\TeX}
+\newcommand\lualatex{Lua\LaTeX}
+\newcommand\xetex{XeTeX}
+\newcommand\xelatex{XeLaTeX}
+%\newcommand\TeXXeT{TeX-{}-XeT}
+
+\newcommand\AllTeX{(La)\TeX}
+\newcommand\alltex{(La)\TeX}
+\newcommand\CONTeXT{Con\TeX{}t}
+\newcommand\context{Con\tex{}t}
+\newcommand\PDFLaTeX{PDF\LaTeX}
+\newcommand\pdflatex{PDF\latex}
+\renewcommand\LaTeX{La\TeX}
+\newcommand\latex{La\TeX}
+\newcommand\twee{2e}
+\renewcommand\LaTeXe{\LaTeX\twee}
+\newcommand\latexe{\LaTeX\twee}
+%
+% Other odds and ends (appear differently in TeX and http or plain
+% text
+%
+% wysiwyg gets capitalised at the beginning of a sentence. not
+% entirely reliably...
+\DeclareRobustCommand\WYSIWYG{%
+ \ifvmode
+ \let\faq@tempa\MakeUppercase
+ \else
+ \ifnum\spacefactor>2000
+ \let\faq@tempa\MakeUppercase
+ \else
+ \let\faq@tempa\relax
+ \fi
+ \fi
+ \textsc{\faq@tempa wysiwyg}%
+}
+%
+% Command for doing `square one' :-}
+\newcommand\sqfbox[1]{\framebox{\makebox[\totalheight]{#1\/}}}
+%
+% an arrow used as a hyphen...
+\newcommand\arrowhyph{\ensuremath{\rightarrow}\penalty0\hskip0pt\relax}
+%
+% Here's a \fullline macro that works in lists and so on
+\newcommand\fullline[1]{\@tempdima\hsize\relax
+ \advance\@tempdima-\leftmargin\relax
+ \advance\@tempdima-\rightmargin\relax
+ \hb@xt@\@tempdima{#1}%
+}
+%
+% list indentations (narrower than default because two-column, but
+% squeezed further to gain a bit more space still)
+\setlength\leftmargini {1.8em}
+\setlength\leftmarginii {1.2em}
+\setlength\leftmarginiii{1em}
+\setlength\leftmarginiv {0.8em}
+%
+% for tidy expression of things with parentheses around them:
+\newcommand\parens[1]{(#1)}
+\newcommand\oparen{(}%)( [footling around to match brackety things in emacs]
+\newcommand\cparen{)}
+%
+% make the tex logo robust
+\edef\@tempa{\noexpand\DeclareRobustCommand\noexpand\TeX{\TeX}}
+\@tempa
+%
+% this piece of fantasy was let loose on an unsuspecting world by
+% christina thiele, but i bet she didn't write it ;-)
+\edef\diatop{\noexpand\protect\csname diatop \endcsname}
+\expandafter\def\csname diatop \endcsname[#1|#2]{%
+ \leavevmode
+ {%
+ \setbox1=\hbox{{#1{}}}\setbox2=\hbox{{#2{}}}%
+ \dimen0=\ifdim\wd1>\wd2\wd1\else\wd2\fi%
+ \dimen1=\ht2\advance\dimen1by-1ex%
+ \setbox1=\hbox to1\dimen0{\hss#1\hss}%
+ \rlap{\raise1\dimen1\box1}%
+ \hbox to1\dimen0{\hss#2\hss}%
+ }%
+}%
+%
+% for han the thanh (who knows whether i've actually got this right; i
+% can't use the T5 fonts, which aren't even really publicly available
+% yet)
+\DeclareRobustCommand{\The}{Th\diatop[\'|\^e]}
+%% %
+%% % 2e's LaTeX logo sets the A in scripstyle jammed up to the top of the T; it
+%% % also has the advantage that it's set in the same font as the
+%% % surrounding text. However, the esteemed bbeeton says the logo looks
+%% % "squidge awful" in italic text (I agree; and the same is true of its
+%% % behaviour in slanted text)
+%% %
+%% % So here's a version that allows for the slant of the leading L
+%% \DeclareRobustCommand{\LaTeX}{L%
+%% {\setbox0\hbox{T}%
+%% \setbox\@tempboxa\hbox{$\m@th$%
+%% \csname S@\f@size\endcsname
+%% \fontsize\sf@size\z@
+%% \math@fontsfalse\selectfont
+%% A}%
+%% \@tempdima\ht0
+%% \advance\@tempdima-\ht\@tempboxa
+%% \@tempdima\strip@pt\fontdimen1\font\@tempdima
+%% \advance\@tempdima-.36em
+%% \kern\@tempdima
+%% \vbox to\ht0{\box\@tempboxa
+%% \vss}%
+%% }%
+%% \kern-.15em
+%% \TeX}
+%% %
+%% % Ditto for \AllTeX (as used in TUGboat)
+%% \DeclareRobustCommand{\AllTeX}{(L%
+%% {\setbox0\hbox{T}%
+%% \setbox\@tempboxa\hbox{$\m@th$%
+%% \csname S@\f@size\endcsname
+%% \fontsize\sf@size\z@
+%% \math@fontsfalse\selectfont
+%% A}%
+%% \@tempdima\ht0
+%% \advance\@tempdima-\ht\@tempboxa
+%% \@tempdima\strip@pt\fontdimen1\font\@tempdima
+%% \advance\@tempdima-.36em
+%% \kern\@tempdima
+%% \vbox to\ht0{\box\@tempboxa
+%% \vss}%
+%% }\kern-.075em)%
+%% \kern-.075em\TeX}
+%% %
+%% % A similar game is used in defining an `all LaTeX' sort of thing:
+%% \DeclareRobustCommand\twee{2$_{\textstyle\varepsilon}$}
+%
+% it proves that, for Alan's stuff, the following needs to have been
+% done _before_ we define the macros
+\RequirePackage{shortvrb}
+\MakeShortVerb{\|}
+%
+% A command which sets some text in typewriter, with the hyphenchar
+% temporarily set to its first argument \FAQverb\HYPHEN{TEXT}.
+% NB: This requires no catcode hackery, so should work inside moving
+% arguments. It will, however, produce spurious spaces after CSs, and
+% won't allow brace-unmatched input. It also won't survive going into a
+% moving argument if \HYPHEN won't.
+%
+\let\FAQverbFamily\ttfamily
+\DeclareRobustCommand{\FAQverb}[2]{{%
+ \ifvmode\leavevmode\fi
+ \lefthyphenmin=256\setlanguage\language
+ \FAQverbFamily\hyphenchar\the\font`#1\relax
+ \def\@tempa{#2}%
+ \expandafter\@faq@strip\meaning\@tempa\@faq@strip
+ \hyphenchar\the\font\m@ne
+}\setlanguage\language}
+\def\@faq@strip#1->#2\@faq@strip{#2}
+%
+% Document markup:
+%
+% (new method, using url.sty -- old version using FAQverb stuff
+% deleted from comments 2000/03/24)
+\newcommand\Email{\begingroup \urlstyle{tt}\Url} % email address
+\ifpdf
+\def\mailto#1{\href{mailto:#1}{\Email{#1}}}
+\else
+\newcommand\mailto{\begingroup \urlstyle{tt}\Url} % mailable address
+\fi
+\DeclareRobustCommand\FTP{\begingroup \urlstyle{tt}\Url} % FTP site address
+\DeclareRobustCommand\File{\begingroup \urlstyle{tt}\Url} % File name
+\DeclareRobustCommand\@ctan@path{\begingroup \urlstyle{tt}\Url} % CTAN path
+ % (argument in braces)
+\ifpdf
+\newcommand\@CTAN[3]{\href{#1#2#3}{\@ctan@path{#2}}} % relay via hyperreference
+\else
+\newcommand\@CTAN[3]{\@ctan@path{#2}} % text-only reference
+\fi
+\newcommand\Newsgroup{\begingroup \urlstyle{tt}\Url} % newsgroup
+\let\URL\url % just a URL
+\ifpdf
+\let\nolinkURL\nolinkurl % unlinked version
+\else
+\let\nolinkURL\url % there ain't no linking
+\fi
+% url.sty defines \path, etc. hyperref may redefine...
+\ifpdf
+ % hyperref has defined \href
+ \let\FAQ@@href\href
+ % we actually want to ignore the * in \href*
+ \def\href{\@ifstar\FAQ@@href\FAQ@@href}
+\else
+%
+% here, latex for printing
+ \newcommand\href{%
+ \@ifstar
+ {\let\@href@text\@empty\@href@a}%
+ {\def\@href@text{see }\@href@a}%
+ }
+%
+% decisions now made about
+ \newcommand\@href@a{\begingroup
+ \@makeother\\%
+ \@makeother\_%
+ \@makeother\%%
+ \@makeother\~%
+ \@makeother\#%
+ \@href@b
+ }
+%
+% enter here in a group with sanitised arg
+ \newcommand\@href@b[1]{\endgroup
+ \urldef\@href@tempurl\url{#1}%
+ \@href@getanchor
+ }
+%
+% out of the group again: argument is the anchor
+ \newcommand\@href@getanchor[1]{#1%
+ \@ifnextchar@nosp'%
+ {\@href@getanchorq}%
+ { (\@href@text\@href@tempurl)\@let@token}%
+ }
+%
+% one quote after the anchor - check for a second
+ \newcommand\@href@getanchorq{% gobble the first quote
+ \@ifnextchar@nosp'%
+ \href@getanchor@qq
+ {' (\@href@text\@href@tempurl)\@let@token}% restore quote
+ }
+ \newcommand\href@getanchor@qq{% gobble the second quote too
+ {'' (\@href@text\@href@tempurl)}% restore both quotes
+ }
+%
+% two quotes after the anchor
+\fi
+\long\def\@ifnextchar@nosp#1#2#3{%
+ \let\reserved@d=#1%
+ \def\reserved@a{#2}%
+ \def\reserved@b{#3}%
+ \afterassignment\@ifnch@nosp\let\@let@token= }
+\def\@ifnch@nosp{%
+ \ifstophere\stopherefalse\show\@let@token\fi
+ \ifx\@let@token\reserved@d
+ \expandafter\reserved@a
+ \else
+ \expandafter\reserved@b
+ \fi
+}
+\setcounter{errorcontextlines}{999}
+\newif\ifstophere
+
+%%\ifx\DeclareUrlCommand\undefined
+\DeclareRobustCommand\ProgName{%
+ \begingroup
+ \def\UrlFont{\rmfamily\itshape}\csname Url@do\endcsname
+ \Url
+}
+\let\progname\ProgName
+%%\else
+%% \DeclareUrlCommand\@ProgName{\def\UrlFont{\rmfamily\itshape}}
+%% \DeclareRobustCommand\ProgName{\@ProgName}
+%%\fi
+\let\Package\ProgName % pro tem
+\let\package\Package
+
+\let\Class\Package % ...
+\let\class\Class
+
+\let\FontName\Package % ...
+% \let\fontname\FontName % ahh, ... no!
+
+% another little oddity (from doc.sty originally, iirc)
+\newcommand\meta[1]{\ensuremath{\langle}\emph{#1}\ensuremath{\rangle}}
+
+%
+% ISBN references
+\def\ISBN{\@ifstar\@ISBNstar\@ISBN}
+\def\@ISBNstar#1#2{\acro{ISBN}-10~#1, \acro{ISBN}-13~#2}
+\def\@ISBN#1{\acro{ISBN}-10~#1}
+%
+% Alan's code for CTAN references (now hacked to be capable of urls
+% for use in pdf output):
+%
+% define a location for a package on CTAN
+% ignores a leading * (which has meaning for html version only)
+% #1 is the package name
+% #2 is the CTAN path to the thing
+% a package in a directory
+\ifpdf
+ \newcommand{\CTANdirectory}{\@ifstar\@sCTANdirectory\@CTANdirectory}
+\else
+ \newcommand{\CTANdirectory}{\@ifstar\@CTANdirectory\@CTANdirectory}
+\fi
+\newcommand{\@CTANdirectory}[2]{\@ifundefined{ctan-#1}{%
+ \expandafter\gdef\csname ctan-#1\endcsname{\@CTAN\LocalCTAN{#2}\CTANDirFmt}%
+ }{%
+ \PackageWarningNoLine{faq}{Repeated definition of label: #1}%
+ \stepcounter{CTAN@replabs}%
+ }%
+ \@faq@disposeopt
+}
+\ifpdf
+ \newcommand{\@sCTANdirectory}[2]{\@ifundefined{ctan-#1}{%
+ \expandafter\gdef\csname ctan-#1\endcsname{\@CTAN\LocalCTAN{#2}/}%
+ }{%
+ \PackageWarningNoLine{faq}{Repeated definition of label: #1}%
+ \stepcounter{CTAN@replabs}%
+ }%
+ \@faq@disposeopt
+ }
+\fi
+%
+% a package in a single file (the same appearance, but the WWW -- and
+% ultimately the pdf -- versions are different).
+\ifpdf
+\newcommand{\CTANfile}[2]{\@ifundefined{ctan-#1}{%
+ \expandafter\gdef\csname ctan-#1\endcsname{\@CTAN\LocalCTAN{#2}{}}%
+ }{%
+ \PackageWarningNoLine{faq}{Repeated definition of label: #1}%
+ \stepcounter{CTAN@replabs}%
+ }%
+ \@faq@disposeopt
+}
+\else
+\let\CTANfile\CTANdirectory
+\fi
+%
+% get rid of optional catalogue pointer in \CTAN(directory|file)
+\newcommand\@faq@disposeopt{%
+ \@ifnextchar[\@faq@gobbleopt{}% ]
+}
+\def\@faq@gobbleopt[#1]{}
+%
+% Make reference to a CTAN package
+%
+% counters for the undefined references and repeated labels
+\newcounter{CTAN@unrefs}
+\newcounter{CTAN@replabs}%
+%
+% the command itself
+\newcommand{\CTANref}[1]{%
+ \@ifundefined{ctan-#1}{%
+ \PackageWarning{CTAN}{Undefined reference: #1}%
+ \stepcounter{CTAN@unrefs}%
+ \futurelet\@let@token\faq@zap@trailing@opt
+ }{%
+ \csname ctan-#1\endcsname
+ \expandafter\let
+ \expandafter\faq@cat@ref\csname ctan-catref-#1\endcsname
+ }%
+ \futurelet\@let@token\faq@check@trailing@opt
+}
+\newcommand\faq@check@trailing@opt{%
+ \ifx\@let@token[%
+ \expandafter\faq@collect@catref
+ \else
+ \let\faq@catref\@empty%
+ \fi
+}
+\def\faq@collect@catref[#1]{\edef\faq@catref{\noexpand
+ \url{\faq@fixed@cataddr#1.html}%
+ }%
+}%
+\def\faq@fixed@cataddr{ help/Catalogue/}%
+\newcommand\faq@zap@trailing@opt{\ifx\@let@token[%
+ \expandafter\@gobble@opt\fi
+}
+\def\@gobble@opt[#1]{}
+%
+% href to a ctan package
+\ifpdf
+ \DeclareRobustCommand{\CTANhref}[2]{\@ifundefined{ctan-#1}{%
+ \PackageWarning{CTAN}{Undefined reference: #1}%
+ \stepcounter{CTAN@unrefs}%
+ }{{%
+ \def\@CTAN##1##2##3{http://mirror.ctan.org/##2}%
+ \href{\csname ctan-#1\endcsname}{#2}%
+ }}}
+\else % DVI version
+ \DeclareRobustCommand{\CTANhref}[2]{\@ifundefined{ctan-#1}{%
+ \PackageWarning{CTAN}{Undefined reference: #1}%
+ \stepcounter{CTAN@unrefs}%
+ }{{%
+% \def\@ctan@path##1{\expandafter\httpify\LocalCTAN!##1}
+ \def\@ctan@path##1{\LocalCTAN##1}
+ \edef\@tempa{\csname ctan-#1\endcsname}%
+ \expandafter\href\expandafter{\@tempa}{#2}%
+ }}}
+\fi
+%
+% this is surely temporary
+\def\httpify ftp://ftp#1!{http://www#1}
+%
+% hook for diagnosing undefined references at the end
+\AtEndDocument{\ifthenelse{\theCTAN@unrefs > 0}{%
+ \PackageWarningNoLine{ctan}{There were \arabic{CTAN@unrefs} undefined
+ references to CTAN}%
+ }%
+ {}%
+ \ifthenelse{\theCTAN@replabs > 0}{%
+ \PackageWarningNoLine{ctan}{There were \arabic{CTAN@replabs}
+ multiply defined references to CTAN}%
+ }%
+ {}%
+}
+%
+% a slight variation of description for lists of book titles
+\newcommand{\booklabel}[1]{\hspace\labelsep\normalfont\itshape #1}
+\newenvironment{booklist}{%
+ \begin{list}{}%
+ {%
+ \labelwidth\z@
+ \itemindent-\leftmargin
+ \let\makelabel\booklabel
+ \parskip \z@
+ \itemsep \z@
+ }%
+ }%
+ {\end{list}}
+%
+% proglist is the same as booklist if we're using italics for program
+% names, but will need hacking otherwise
+\newenvironment{proglist}{\begin{booklist}}{\end{booklist}}
+%
+% similarly for ctanrefs environment
+\newcommand{\ctanreference}[1]{%
+ \hspace\labelsep\normalfont\ttfamily\itshape
+ \bgroup
+ \@makeother\_%
+ \scantokens{#1}%
+ \unskip
+ \egroup
+ \/\normalfont:%
+}
+\newenvironment{ctanrefs}{%
+ \begin{list}{}%
+ {%
+ \labelwidth\z@
+ \itemindent-\leftmargin
+ \let\makelabel\ctanreference
+ \topsep 4\p@
+ \parskip \z@
+ \itemsep \z@
+ \@rightskip=\z@\@plus1in\relax
+ \spaceskip=.3333em\relax
+ \xspaceskip=.5em\relax
+ }%
+ }%
+ {\end{list}}
+%
+% compact the itemize, enumerate and description environments
+\let\FAQ@@itemize\itemize
+\renewcommand\itemize{%
+ \topsep 0.25\topsep
+ \FAQ@@itemize
+ \parskip \z@
+ \itemsep \z@
+}
+\let\FAQ@@enumerate\enumerate
+\renewcommand\enumerate{%
+ \topsep 0.25\topsep
+ \FAQ@@enumerate
+ \parskip \z@
+ \itemsep \z@
+}
+\let\FAQ@@description\description
+\renewcommand\description{%
+ \topsep 0.25\topsep
+ \FAQ@@description
+ \parskip \z@
+ \itemsep \z@
+}
+%
+% and similarly close up verbatim's separation from what surrounds it
+\let\FAQ@@verbatim\verbatim
+\renewcommand\verbatim{%
+ \topsep 0.25\topsep
+ \FAQ@@verbatim
+}
+%
+% \raggedwithindent is useful when we've got an URL or something
+% overrunning the end of the line (and this line is terminated with
+% \\)
+%
+% Typical usage is within the argument of a \nothtml command
+\newcommand\raggedwithindent{%
+ \rightskip=\z@\@plus5em\relax
+ \spaceskip=.3333em\relax
+ \xspaceskip=.5em\relax
+ \hangindent=1pc\relax}
+%
+% things needed for the benefit of texfaq2html's `sanitise_line'
+\let\textpercent\%
+\let\faq@@textbar\textbar
+\chardef\faq@vertbar`\|
+\renewcommand\textbar{\def\@tempa{cmtt}%
+ \ifx\@tempa\f@family
+ \faq@vertbar
+ \else
+ \faq@@textbar
+ \fi
+}
+%
+% redefine \cs{l@section} to require space for itself at the bottom
+% of a column
+\renewcommand\l@section[2]{%
+ \ifnum \c@tocdepth >\z@
+ \addpenalty\@secpenalty
+ \addvspace{1.0em \@plus\p@}%
+% "needspace" element here (doesn't work)
+% \vskip \z@ \@plus 3\baselineskip
+% \penalty -\@highpenalty
+% \vskip \z@ \@plus -3\baselineskip
+ \setlength\@tempdima{1.5em}%
+ \begingroup
+ \parindent \z@ \rightskip \@pnumwidth
+ \parfillskip -\@pnumwidth
+ \leavevmode \bfseries
+ \advance\leftskip\@tempdima
+ \hskip -\leftskip
+ #1\nobreak\hfil \nobreak\hb@xt@\@pnumwidth{\hss #2}\par
+ \endgroup
+ \fi
+}
+%
+% subsections: these are a curious half-breed between latex sections
+% and subsections -- as designed, i'm not intending there ever to be
+% more than 9 per section (hahaha)
+\renewcommand\subsection{\@startsection{subsection}%
+ \tw@
+ \z@
+ {-1.5ex \@plus-1ex \@minus-.3ex}%
+ {1ex \@plus.2ex}%
+ {\normalfont\large\bfseries
+ \raggedright}%
+ }
+\renewcommand*\l@subsection[2]{%
+ \ifnum \c@tocdepth >\@ne
+ \addpenalty\@secpenalty
+ \addvspace{0.5em \@plus\p@}%
+% "needspace" element here (doesn't work)
+% \vskip \z@ \@plus 3\baselineskip
+% \penalty -\@highpenalty
+% \vskip \z@ \@plus -3\baselineskip
+ \setlength\@tempdima{2.0em}%
+ \begingroup
+ \parindent \z@ \rightskip \@pnumwidth
+ \parfillskip -\@pnumwidth
+ \leavevmode \bfseries
+ \advance\leftskip\@tempdima
+ \hskip -\leftskip
+ #1\nobreak\hfil \nobreak\hb@xt@\@pnumwidth{\hss #2}\par
+ \endgroup
+ \fi}
+%
+%
+% the question structure
+% \Question[label name]{question asked}
+% if [label name] present, the named label is assigned with \Qlabel
+\newcounter{question}
+\newcommand\Question[2][]{%
+ \ifpdf
+ \def\annot@label{#1}%
+ \def\annot@question{#2}%
+ \fi
+ \edef\l@stl@bel{\@gobbletwo#1}%
+ \qu@stion{#2}%
+ \def\reserved@a{#1}%
+ \ifx\reserved@a\@empty
+ \PackageWarning{faq}{Question "#2" has no label}%
+ \else
+ \Qlabel{#1}%
+ \fi
+}
+\newcommand\qu@stion{\@startsection{question}%
+ \thr@@
+ \z@
+ {-1.25ex \@plus -1ex \@minus -.2ex}%
+ {0.75ex \@plus .2ex}%
+ {%
+ \normalfont
+ \normalsize
+ \bfseries
+ \raggedright
+ \protected@edef\@svsec{\protect\annot@set\@svsec}%
+ }%
+}
+\newcommand*\questionmark[1]{}
+\newcommand*\l@question{\@dottedtocline{2}{2.0em}{2.3em}}
+
+%
+% \paragraph: has appeared in a submission, so let's give it a faq
+% definition...
+\renewcommand\paragraph{\@startsection{paragraph}%
+ 4%
+ \z@
+ {1.25ex \@plus 1ex \@minus.2ex}%
+ {-1em}
+ {%
+ \normalfont
+ \normalsize
+ \bfseries
+ }}
+%
+% alias questions make a little perl script to set up a hash array
+% that takes one from old question to current one.
+\newcount\aliasfile
+\aliasfile=-1
+\newcommand\AliasQuestion[1]{%
+ \ifnum\aliasfile<0
+ \newwrite\aliasfile
+ \immediate\openout\aliasfile aliasquestion.list
+ \immediate\write\aliasfile {\faq@percent old_label_to_new = (}%)
+ \AtEndDocument{%(
+ \immediate\write\aliasfile{);}%
+ \immediate\write\aliasfile{1;}%
+ }%
+ \else
+ \immediate\write\aliasfile {,}% finish previous line
+ \fi
+ \immediate\write\aliasfile{"\@gobbletwo#1","\l@stl@bel"}%
+}
+{%
+ \catcode`\!=\the\catcode`\%%
+ \catcode`\%=\the\catcode`\+!
+ \gdef\faq@percent{%}!
+}
+%
+\long\def\@ReturnAfterFi#1\fi{\fi#1}%
+\ifpdf
+ \newcommand*\toclevel@question{3}%
+ \let\orig@section\section
+ \let\orig@subsection\subsection
+ \let\orig@subsubsection\subsubsection
+ \def\section{%
+ \def\toclevel@question{2}%
+ \orig@section
+ }
+ \def\subsection{%
+ \def\toclevel@question{3}%
+ \orig@subsection
+ }
+ \def\subsubsection{%
+ \def\toclevel@question{4}%
+ \orig@subsubsection
+ }
+ %
+ \def\annot@set{%
+ \ifx\annot@label\@empty
+ \else
+ \begingroup
+ \def\x##1-##2\@nil{\def\annot@label{##2}}%
+ \expandafter\x\annot@label\@nil
+ \def\x##1_##2\@nil{%
+ ##1%
+ \ifx\\##2\\%
+ \else
+ \noexpand\textunderscore
+ \@ReturnAfterFi{\x##2\@nil}%
+ \fi
+ }%
+ \edef\annot@label{\expandafter\x\annot@label_\@nil}%
+ \edef\NL{\string\n}%
+ \pdfstringdef\annot@text{%
+ http://www.tex.ac.uk/cgi-bin/texfaq2html?label=\annot@label\NL
+ \annot@question
+ }%
+ \rlap{%
+ \kern-10mm\relax
+ \settoheight{\dimen@}{X}%
+ \pdfannotlink
+ width 200mm
+ height \dimen@
+ depth 25mm
+ user {%
+ /Subtype/Text%
+ /T(Question \thequestion: \annot@label)%
+ /Contents(\annot@text)%
+ }%
+ \pdfendlink
+ }%
+ \endgroup
+ \fi
+ }%
+ \@ifundefined{pdfannotlink}{%
+ \let\pdfannotlink\pdfstartlink
+ }{}
+\else
+ \let\annot@set\relax
+\fi
+%
+% \QuestionLabel starts out as a null command (so that inputting a
+% .lab file at s.o.d has no effect), but it's then reset to
+% \@questionLabel in case the file is going to be read again later
+% (e.g., as an appendix), but we don't have a sensible definition of
+% _that_ yet, either...
+\newcommand{\labellist}{%
+ \newcommand{\QuestionLabel}[3]{}%
+% \@starttoc{lab}%
+ \let\QuestionLabel\@questionLabel
+}
+\newcommand{\@questionLabel}[3]{}
+%
+% \afterquestion is used when the \Question command itself has to be
+% inside a group for some reason (e.g., to have it in \boldmath)
+\newcommand\afterquestion{%
+ \global\toks@\expandafter{\the\everypar}%
+ \edef\@tempa{%
+ \noexpand\@afterindentfalse
+ \noexpand\everypar{\the\toks@}%
+ }%
+ \expandafter\endgroup\@tempa
+}
+%
+% \cs{Destination} is used immediately after a \cs{Question} command
+% in the various add-* files to signify where the question is supposed
+% to go
+\newcommand\Destination[1]{\begin{center}
+ \itshape#1
+ \end{center}
+}
+%
+% we `number' our sections alphabetically
+\renewcommand{\thesection}{\Alph{section}}
+%
+% keywords for questions. these get translated into comments in web
+% versions
+\newcommand\keywords{\begingroup
+ \@makeother\\%
+ \@makeother\^%
+ \@makeother\_%
+ \@makeother\%%
+ \expandafter\endgroup
+ \@gobble
+}
+%
+% date question last edited
+\def\LastEdit{\@ifstar\@gobble\@gobble}
+%
+% where the info came from
+\newcommand\LeadFrom[3]{}
+%
+% \Qlabel and \Qref: define and refer to labels
+\ifpdf
+% hyperref version of \label doesn't get set until begin document
+ \AtBeginDocument{\let\Qlabel\label}
+\else
+ \let\Qlabel\label
+\fi
+% \Qref[<text before q no>]{<hyper anchor text>}{<question label>}
+% (default for arg 1 is "see question"; a conventional null argument
+% here is \htmlonly, which gobbles a space)
+% produces:
+% <text before q no> <question number>
+%
+% \Qref*... produces
+% <hyper anchor text> (<text before q no> <question number>)
+%
+% the code is supposed to deal correctly with things surrounded by
+% double quotes (i.e., ``\Qref*....'' closes the quotes before putting
+% the question number in parentheses.
+%
+% this stuff should be reconsidered to produce more sensible behaviour
+% when running pdftex
+%
+\ifpdf
+%
+% if we're using pdflatex, we let hyperref take the strain, and make
+% \Qrefs look like the html versions
+\DeclareRobustCommand\Qref{\@ifstar\@QrefH\@QrefH}
+\newcommand\@QrefH[3][\relax]{%
+ \expandafter\let\expandafter\reserved@a\csname r@#3\endcsname
+ \ifx\reserved@a\relax
+ \protect\G@refundefinedtrue
+ \nfss@text{\reset@font\bfseries ??}%
+ \@latex@warning{%
+ Reference `#3' on page \thepage \space undefined%
+ }%
+ \else
+% \protected@edef\reserved@b{\reserved@a}%
+ \def\reserved@c##1##2##3##4##5{%
+ \def\reserved@d{{##1}{##2}{#2}{##4}{##5}}%
+ }%
+ \expandafter\reserved@c\reserved@a
+ \expandafter\Hy@setref@link\reserved@d\@empty\@empty\@nil\@thirdoffive
+ \fi
+}
+\else
+%
+% not using pdflatex: we've a ghastly job on our hands...
+\newcommand\Qref{\@ifstar\@QrefA\@QrefB}
+\newcommand\@QrefA[3][see question]{#2%
+ \def\@QrefAai{#1}%
+ \def\@QrefAaiii{#3}%
+ \afterassignment\@QrefAl\let\@tempa= }
+\newcommand\@QrefAl{% \@tempa is char after original \Qref's args
+ % \@QrefAai/\@QrefAaiii are arguments of \Qref
+ \ifx\@tempa'%
+ \def\@next{%
+ \afterassignment\@QrefAQ
+ \let\@tempa= %
+ }%
+ \expandafter\@next
+ \else
+ { (\@QrefAai~\ref{\@QrefAaiii})\@tempa}%
+ \fi
+}
+\newcommand\@QrefAQ{% \@tempa is second char after original \Qref's
+ % arguments (first was a quote character)
+ \ifx\@tempa'%
+ '' (\@QrefAai~\ref{\@QrefAaiii})%
+ \else
+ { (\@QrefAai~\ref{\@QrefAaiii})'\@tempa}%
+ \fi
+}
+%% \@ifnextchar'{\@QrefAQb{#1}{#2}}{ (#1~\ref{#2})'}}
+%% \newcommand\@QrefAQb[3]{% param 3 quote again
+%% '' (#1~\ref{#2})}
+\newcommand\@QrefB[3][see question]{#1~\ref{#3}}
+%
+\fi
+%
+% from doc package, then hacked about by yours truly
+\DeclareRobustCommand\csx[1]{{\FAQverbFamily\char`\\#1}}
+%\def\cs|#1|{\csx{#1}}
+%
+% fancier versions of the above
+%
+% \cmdinvoke\cs<argument sequence>
+% \cs typeset as above
+% <argument sequence> may consist of optional or mandatory arguments;
+%
+% the `arguments' are simply typesett \texttt, as yet -- if something
+% fancier is needed, there's a bunch of code needs rewriting here...
+\DeclareRobustCommand\cmdinvoke{\@ifstar
+ {\let\@tempa\emph\@scmdinvoke}%
+ {\let\@tempa\relax\@scmdinvoke}%
+}
+\def\@scmdinvoke#1{\texttt{\symbol{92}#1}%
+ \futurelet\@let@token\@cmdinvoke
+}
+\def\@cmdinvoke{\ifx\@let@token\bgroup
+ \let\@tempb\@cmdinvoke@lbrace
+ \else
+ \ifx\@let@token[% ]
+ \let\@tempb\@cmdinvoke@lbrack
+ \else
+ \ifx\@let@token(% )
+ \let\@tempb\@cmdinvoke@lparen
+ \else
+ \let\@tempb\@empty
+ \fi
+ \fi
+ \fi
+ \@tempb
+}
+\def\@cmdinvoke@lbrace#1{\penalty0\hskip0pt\relax
+ \texttt{\symbol{123}\@tempa{#1}\symbol{125}}%
+ \futurelet\@let@token\@cmdinvoke
+}
+\def\@cmdinvoke@lbrack[#1]{\penalty-150\hskip0pt\relax
+ \texttt{[\@tempa{#1}]}%
+ \futurelet\@let@token\@cmdinvoke
+}
+\def\@cmdinvoke@lparen(#1){\penalty-150\hskip0pt\relax
+ \texttt{(\@tempa{#1})}%
+ \futurelet\@let@token\@cmdinvoke
+}
+%
+% for writing \cmdinvoke out by hand (in titles)
+\def\marg#1{\texttt{\symbol{123}{#1}\symbol{125}}}
+
+% that stuff doesn't work in pdf thumbnails. herewith an alternative
+% for label ps@empty:
+\DeclareRobustCommand\psatempty{%
+ \texttt{\string\pagestyle\string{empty\string}}%
+}
+
+% minuscule bit more structured markup...
+\newcommand\environment[1]{\texttt{#1}}
+\newcommand\pkgoption[1]{\texttt{#1}}
+\newcommand\extension[1]{\texttt{.#1}}
+\newcommand\ltxcounter[1]{\texttt{#1}}
+\newcommand\FontFormat[1]{\texttt{#1}}
+
+% deal with tabular: special defs to make texfaq2html doable
+\let\tbamp&
+\def\tbeol{\\}
+\def\tbhline{\midrule}
+
+%
+% symbols for the braces (which can confuse perl sumfink rotten
+\def\obracesymbol{\symbol{123}}
+\def\cbracesymbol{\symbol{125}}
+
+%
+% for quoting verbatim environments in examples:
+\begingroup \catcode `|=0 \catcode `[= 1
+\catcode`]=2 \catcode `\{=12 \catcode `\}=12
+\catcode`\\=12
+|gdef|@quotexverbatim#1\end{quoteverbatim}[#1|end[quoteverbatim]]
+|endgroup
+\def\quoteverbatim{\@verbatim \frenchspacing\@vobeyspaces \@quotexverbatim}
+\let\endquoteverbatim\endverbatim
+
+%
+% for comments during maintenance
+%\def\Q#1{\footnote{{\ttfamily QUERY: #1}}}
+%\def\Q#1{\marginpar{{\ttfamily QUERY: #1}}}
+%
+% Checking structure (null for now)
+\newcommand\checked[2]{}
+%
+% for Alan's benefit
+\newbox\@footnoteenvbox
+\newenvironment{footnoteenv}
+ {\begin{lrbox}\@footnoteenvbox\reset@font\footnotesize\ignorespaces}
+ {\end{lrbox}%
+ \footnote{\unhbox\@footnoteenvbox}}
+%
+% end of package
+\endinput
diff --git a/help/uk-tex-faq/faqfont.cfg b/help/uk-tex-faq/faqfont.cfg
new file mode 100644
index 0000000000..ae36c3730e
--- /dev/null
+++ b/help/uk-tex-faq/faqfont.cfg
@@ -0,0 +1,4 @@
+%
+% null FAQ configuration file: leaves LaTeX default use of cm* fonts
+\typeout{FAQ -- Typesetting using Computer Modern fonts}
+\@ifundefined{Dings}{\let\Dings\relax}{}
diff --git a/help/uk-tex-faq/faqfont.cfg.cmfonts b/help/uk-tex-faq/faqfont.cfg.cmfonts
new file mode 100644
index 0000000000..4f5f663bfa
--- /dev/null
+++ b/help/uk-tex-faq/faqfont.cfg.cmfonts
@@ -0,0 +1,6 @@
+%
+% null FAQ configuration file: leaves LaTeX default use of cm* fonts
+\typeout{FAQ -- Typesetting using Computer Modern fonts}
+\@ifundefined{Dings}{\let\Dings\relax}{}
+\boldmathavailtrue
+
diff --git a/help/uk-tex-faq/faqfont.cfg.lmfonts b/help/uk-tex-faq/faqfont.cfg.lmfonts
new file mode 100644
index 0000000000..707e6c6cf8
--- /dev/null
+++ b/help/uk-tex-faq/faqfont.cfg.lmfonts
@@ -0,0 +1,19 @@
+% version to use latin modern, and not luximono or trying to do dinglines
+ \RequirePackage[T1]{fontenc}%
+ \RequirePackage{lmodern}% for sans fonts
+ \RequirePackage{textcomp}%
+ \AtBeginDocument{%
+ \let\save@textcurrency\textcurrency
+ \def\textcurrency{%
+ {%
+ \fontfamily{lmr}\selectfont
+ \save@textcurrency
+ }%
+ }%
+ }
+ \boldmathavailfalse
+ \DeclareRobustCommand{\$}{\char`\$}% otherwise tries to load tctt....
+ \let\Dings\relax
+ \DeclareRobustCommand\acro[1]{#1\@{}}
+
+
diff --git a/help/uk-tex-faq/faqfont.cfg.mbvj b/help/uk-tex-faq/faqfont.cfg.mbvj
new file mode 100644
index 0000000000..cbf128b80c
--- /dev/null
+++ b/help/uk-tex-faq/faqfont.cfg.mbvj
@@ -0,0 +1,11 @@
+\renewcommand\rmdefault{mbvj}
+\renewcommand{\sfdefault}{lmss}
+\renewcommand{\ttdefault}{lmtt}
+\usepackage{textcomp}
+\usepackage[T1]{fontenc}
+\DeclareRobustCommand{\$}{\char`\$}
+\@ifundefined{Dings}{\RequirePackage{pifont}%
+ \def\Dings{\nopagebreak{\footnotesize
+ \dingline{167}}}}{}%
+\boldmathavailfalse
+\def\acro##1{##1\@{}}
diff --git a/help/uk-tex-faq/faqfont.cfg.ugm b/help/uk-tex-faq/faqfont.cfg.ugm
new file mode 100644
index 0000000000..04f3133b3c
--- /dev/null
+++ b/help/uk-tex-faq/faqfont.cfg.ugm
@@ -0,0 +1,12 @@
+\usepackage{textcomp}
+\usepackage[T1]{fontenc}
+\RequirePackage{lmodern} % for sans text (one instance only?)
+\renewcommand\rmdefault{ugm}
+\renewcommand\bfdefault{b}
+\RequirePackage{eulervm}
+\RequirePackage[scaled=0.85]{luximono}
+\@ifundefined{Dings}{\RequirePackage{pifont}%
+ \def\Dings{\nopagebreak{\footnotesize
+ \dingline{167}}}}{}%
+\boldmathavailtrue % is it?
+\def\acro#1{#1\@{}}
diff --git a/help/uk-tex-faq/filectan.tex b/help/uk-tex-faq/filectan.tex
new file mode 100644
index 0000000000..326b455cbc
--- /dev/null
+++ b/help/uk-tex-faq/filectan.tex
@@ -0,0 +1,107 @@
+% $Id: filectan.tex,v 1.143 2012/12/07 19:34:33 rf10 Exp rf10 $
+%
+% protect ourself against being read twice
+\csname readCTANfiles\endcsname
+\let\readCTANfiles\endinput
+%
+% interesting/useful individual files to be found on CTAN
+\CTANfile{CTAN-sites}{CTAN.sites}
+\CTANfile{CTAN-uploads}{README.uploads}% yes, it really is in the root
+\CTANfile{Excalibur}{systems/mac/support/excalibur/Excalibur-4.0.2.sit.hqx}[excalibur]
+\CTANfile{expl3-doc}{macros/latex/contrib/l3kernel/expl3.pdf}[l3kernel]
+\CTANfile{f-byname}{FILES.byname}
+\CTANfile{f-last7}{FILES.last07days}
+\CTANfile{interface3-doc}{macros/latex/contrib/l3kernel/interface3.pdf}[l3kernel]
+\CTANfile{LitProg-FAQ}{help/comp.programming.literate_FAQ}
+\CTANfile{OpenVMSTeX}{systems/OpenVMS/TEX97_CTAN.ZIP}
+\CTANfile{T1instguide}{info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf}
+\CTANfile{TeX-FAQ}{obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers}
+\CTANfile{abstract-bst}{biblio/bibtex/utils/bibtools/abstract.bst}
+\CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex}[backgrnd]
+\CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk}[bbl2html]
+\CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf}[beginlatex]
+\CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf}
+\CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex}[bidstobibtex]
+\CTANfile{btxmactex}{macros/eplain/tex/btxmac.tex}[eplain]
+\CTANfile{catalogue}{help/Catalogue/catalogue.html}
+\CTANfile{cat-licences}{help/Catalogue/licenses.html}
+\CTANfile{clsguide}{macros/latex/doc/clsguide.pdf}[clsguide]
+\CTANfile{compactbib}{macros/latex/contrib/compactbib/compactbib.sty}[compactbib]
+%\CTANfile{compan-ctan}{info/companion.ctan}
+\CTANfile{context-tmf}{macros/context/current/cont-tmf.zip}[context]
+\CTANfile{dvitype}{systems/knuth/dist/texware/dvitype.web}[dvitype]
+\CTANfile{edmetrics}{systems/mac/textures/utilities/EdMetrics.sea.hqx}[edmetrics]
+\CTANfile{epsf}{macros/generic/epsf/epsf.tex}[epsf]
+\CTANfile{figsinlatex}{obsolete/info/figsinltx.ps}
+\CTANfile{finplain}{biblio/bibtex/contrib/misc/finplain.bst}
+\CTANfile{fix-cm}{macros/latex/unpacked/fix-cm.sty}[fix-cm]
+\CTANfile{fntguide.pdf}{macros/latex/doc/fntguide.pdf}[fntguide]
+\CTANfile{fontdef}{macros/latex/base/fontdef.dtx}
+\CTANfile{fontmath}{macros/latex/unpacked/fontmath.ltx}
+\CTANfile{gentle}{info/gentle/gentle.pdf}[gentle]
+\CTANfile{gkpmac}{systems/knuth/local/lib/gkpmac.tex}[gkpmac]
+\CTANfile{knuth-letter}{systems/knuth/local/lib/letter.tex}
+\CTANfile{knuth-tds}{macros/latex/contrib/latex-tds/knuth.tds.zip}
+\CTANfile{latex209-base}{obsolete/macros/latex209/distribs/latex209.tar.gz}[latex209]
+\CTANfile{latex-classes}{macros/latex/base/classes.dtx}
+\CTANfile{latex-source}{macros/latex/base/source2e.tex}
+\CTANfile{latexcount}{support/latexcount/latexcount.pl}[latexcount]
+\CTANfile{latexcheat}{info/latexcheat/latexcheat/latexsheet.pdf}[latexcheat]
+\CTANfile{letterspacing}{macros/generic/misc/letterspacing.tex}[letterspacing]
+\CTANfile{ltablex}{macros/latex/contrib/ltablex/ltablex.sty}[ltablex]
+\CTANfile{ltxguide}{macros/latex/base/ltxguide.cls}
+\CTANfile{ltxtable}{macros/latex/contrib/carlisle/ltxtable.tex}[ltxtable]
+\CTANfile{lw35nfss-zip}{macros/latex/required/psnfss/lw35nfss.zip}[lw35nfss]
+\CTANfile{macmakeindex}{systems/mac/macmakeindex2.12.sea.hqx}
+\CTANfile{mathscript}{info/symbols/math/scriptfonts.pdf}
+\CTANfile{mathsurvey.html}{info/Free_Math_Font_Survey/en/survey.html}
+\CTANfile{mathsurvey.pdf}{info/Free_Math_Font_Survey/en/survey.pdf}
+\CTANfile{memoir-man}{macros/latex/contrib/memoir/memman.pdf}
+\CTANfile{metafp-pdf}{info/metafont/metafp/metafp.pdf}[metafp]
+\CTANfile{mf-beginners}{info/metafont/beginners/metafont-for-beginners.pdf}[metafont-beginners]
+\CTANfile{mf-list}{info/metafont-list}
+\CTANfile{miktex-portable}{systems/win32/miktex/setup/miktex-portable.exe}
+\CTANfile{miktex-setup}{systems/win32/miktex/setup/setup.exe}[miktex]
+\CTANfile{mil}{info/mil/mil.pdf}
+\CTANfile{mil-short}{info/Math_into_LaTeX-4/Short_Course.pdf}[math-into-latex-4]
+\CTANfile{modes-file}{fonts/modes/modes.mf}[modes]
+\CTANfile{mtw}{info/makingtexwork/mtw-1.0.1-html.tar.gz}
+\CTANfile{multind}{macros/latex209/contrib/misc/multind.sty}[multind]
+\CTANfile{nextpage}{macros/latex/contrib/misc/nextpage.sty}[nextpage]
+\CTANfile{noTeX}{biblio/bibtex/utils/misc/noTeX.bst}[notex]
+\CTANfile{numline}{obsolete/macros/latex/contrib/numline/numline.sty}[numline]
+\CTANfile{patch}{macros/generic/misc/patch.doc}[patch]
+\CTANfile{picins-summary}{macros/latex209/contrib/picins/picins.txt}
+\CTANfile{pk300}{fonts/cm/pk/pk300.zip}
+\CTANfile{pk300w}{fonts/cm/pk/pk300w.zip}
+\CTANfile{QED}{macros/generic/proofs/taylor/QED.sty}[qed]
+\CTANfile{removefr}{macros/latex/contrib/fragments/removefr.tex}[removefr]
+\CTANfile{repeat}{macros/generic/eijkhout/repeat.tex}[repeat]
+\CTANfile{resume}{obsolete/macros/latex209/contrib/resume/resume.sty}
+\CTANfile{savesym}{macros/latex/contrib/savesym/savesym.sty}[savesym]
+\CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}[setspace]
+\CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.pdf}[simplified-latex]
+\CTANfile{sober}{macros/latex209/contrib/misc/sober.sty}[sober]
+\CTANfile{tex2bib}{biblio/bibtex/utils/tex2bib/tex2bib}[tex2bib]
+\CTANfile{tex2bib-doc}{biblio/bibtex/utils/tex2bib/README}
+\CTANfile{tex4ht}{obsolete/support/TeX4ht/tex4ht-all.zip}[tex4ht]
+\CTANfile{texlive-unix}{systems/texlive/tlnet/install-tl-unx.tar.gz}
+\CTANfile{texlive-windows}{systems/texlive/tlnet/install-tl.zip}
+\CTANfile{texnames}{info/biblio/texnames.sty}
+\CTANfile{texsis-index}{macros/texsis/index/index.tex}
+\CTANfile{topcapt}{macros/latex/contrib/misc/topcapt.sty}[topcapt]
+\CTANfile{tracking}{macros/latex/contrib/tracking/tracking.sty}[tracking]
+\CTANfile{ttb-pdf}{info/bibtex/tamethebeast/ttb_en.pdf}[tamethebeast]
+\CTANfile{type1ec}{fonts/ps-type1/cm-super/type1ec.sty}[type1ec]
+\CTANfile{ukhyph}{language/hyphenation/ukhyphen.tex}
+\CTANfile{upquote}{macros/latex/contrib/upquote/upquote.sty}[upquote]
+\CTANfile{faq-a4}{help/uk-tex-faq/newfaq.pdf}
+\CTANfile{faq-letter}{help/uk-tex-faq/letterfaq.pdf}
+\CTANfile{versions}{macros/latex/contrib/versions/versions.sty}[versions]
+\CTANfile{vf-howto}{info/virtualfontshowto/virtualfontshowto.txt}[vf-howto]
+\CTANfile{vf-knuth}{info/knuth/virtual-fonts}[vf-knuth]
+\CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}[visualfaq]
+\CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf}
+\CTANfile{wujastyk-txh}{digests/texhax/txh/wujastyk.txh}
+\CTANfile{xampl-bib}{biblio/bibtex/base/xampl.bib}
+\CTANfile{xtexcad}{graphics/xtexcad/xtexcad-2.4.1.tar.gz}
diff --git a/help/uk-tex-faq/gather-faqbody.tex b/help/uk-tex-faq/gather-faqbody.tex
new file mode 100644
index 0000000000..97f7b0cd69
--- /dev/null
+++ b/help/uk-tex-faq/gather-faqbody.tex
@@ -0,0 +1,57 @@
+\def\faqfileversion{3.28} \def\faqfiledate{2014-06-10}
+%
+% The above line defines the file version and date, and must remain
+% the first line with any `assignment' in the file, or things will
+% blow up in a stupid fashion
+%
+% get lists of CTAN labels
+%
+% configuration for the lists, if we're going to need to generate urls
+% for the files
+\InputIfFileExists{archive.cfg}{}{}
+%
+% ... directories
+\input{dirctan}
+%
+% ... files
+\input{filectan}
+
+% facilitate auto-processing of this stuff; this line is clunkily
+% detected (and ignored) in the build-faqbody script
+%\let\faqinput\input
+\def\faqinput#1{%\message{*** inputting #1; group level \the\currentgrouplevel}
+ \input{#1}%
+ %\message{*** out of #1; group level \the\currentgrouplevel}
+}
+
+% the stuff to print
+\faqinput{faq-intro} % introduction
+\faqinput{faq-backgrnd} % background
+\faqinput{faq-docs} % docs
+\faqinput{faq-bits+pieces} % bits and pieces
+\faqinput{faq-getit} % getting software
+\faqinput{faq-texsys} % TeX systems
+\faqinput{faq-dvi} % DVI drivers and previewers
+\faqinput{faq-support} % support stuff
+\faqinput{faq-litprog} % programming for literates
+\faqinput{faq-fmt-conv} % format conversions
+\faqinput{faq-install} % installation and so on
+\faqinput{faq-fonts} % fonts and what to do
+\faqinput{faq-hyp+pdf} % hyper-foodle and pdf
+\faqinput{faq-graphics} % graphics
+\faqinput{faq-biblio} % bib stuff
+\faqinput{faq-adj-types} % adjusting typesetting
+\faqinput{faq-lab-ref} % labels and references
+\faqinput{faq-how-do-i} % how to do things
+\faqinput{faq-symbols} % symbols, their natural history and use
+\faqinput{faq-mac-prog} % macro programming
+\faqinput{faq-t-g-wr} % things going wrong
+\faqinput{faq-wdidt} % why does it do that
+%*****************************************quote environments up to here
+\faqinput{faq-jot-err} % joy (hem hem) of tex errors
+\faqinput{faq-projects} % current projects
+%
+% This is the last section, and is to remain the last section...
+\faqinput{faq-the-end} % wrapping it all up
+
+% \end{document} is in calling file (e.g., newfaq.tex)
diff --git a/help/uk-tex-faq/install-CTAN b/help/uk-tex-faq/install-CTAN
new file mode 100644
index 0000000000..162a568631
--- /dev/null
+++ b/help/uk-tex-faq/install-CTAN
@@ -0,0 +1,48 @@
+# this file is auto-generated; edit mk-makefile, not this
+
+for f in \
+ ChangeLog \
+ Makefile \
+ README \
+ dirctan.tex \
+ faq.cls \
+ faq.sty \
+ filectan.tex \
+ gather-faqbody.tex \
+ letterfaq.tex \
+ archive.cfg \
+ markup-syntax \
+ newfaq.tex \
+ letterfaq.pdf \
+ newfaq.pdf \
+ faqfont.cfg.cmfonts \
+ FAQ-html.tar.gz \
+ CHANGES-3.24 \
+ faq-adj-types.tex \
+ faq-backgrnd.tex \
+ faq-biblio.tex \
+ faq-bits+pieces.tex \
+ faq-docs.tex \
+ faq-dvi.tex \
+ faq-fmt-conv.tex \
+ faq-fonts.tex \
+ faq-getit.tex \
+ faq-graphics.tex \
+ faq-how-do-i.tex \
+ faq-hyp+pdf.tex \
+ faq-install.tex \
+ faq-intro.tex \
+ faq-jot-err.tex \
+ faq-lab-ref.tex \
+ faq-litprog.tex \
+ faq-mac-prog.tex \
+ faq-projects.tex \
+ faq-support.tex \
+ faq-symbols.tex \
+ faq-t-g-wr.tex \
+ faq-texsys.tex \
+ faq-the-end.tex \
+ faq-wdidt.tex ; do
+if [ -f /anfs/ctan/tex-archive/help/uk-tex-faq/$f ]; then
+ ctan_install -replace -silent -nozip $f help/uk-tex-faq/$f ; else
+ ctan_install -new -silent -nozip $f help/uk-tex-faq/$f ; fi; done
diff --git a/help/uk-tex-faq/letterfaq.pdf b/help/uk-tex-faq/letterfaq.pdf
new file mode 100644
index 0000000000..5d9d731974
--- /dev/null
+++ b/help/uk-tex-faq/letterfaq.pdf
Binary files differ
diff --git a/help/uk-tex-faq/letterfaq.tex b/help/uk-tex-faq/letterfaq.tex
new file mode 100644
index 0000000000..dd0b4427d7
--- /dev/null
+++ b/help/uk-tex-faq/letterfaq.tex
@@ -0,0 +1,64 @@
+% This is the UK TeX FAQ
+%
+\documentclass{faq}
+%
+\setcounter{errorcontextlines}{999}
+%
+% read the first two definitions of faqbody.tex for the file version
+% and date
+\afterassignment\endinput\input gather-faqbody
+%
+\typeout{The UK TeX FAQ, v\faqfileversion, date \faqfiledate}
+%
+% let's not be too fussy while we're developing...
+\hfuzz10pt
+\emergencystretch10pt
+%
+\begin{document}
+\title{The \acro{UK} \TeX{} \acro{FAQ}\\
+ Your \ifpdf\ref*{lastquestion}\else\protect\ref{lastquestion}\fi
+ \ Questions Answered\\
+ version \faqfileversion, date \faqfiledate}
+\author{}
+\maketitle
+
+\centerline{\textsc{Note}}
+
+\begin{quotation}\small
+ This document is an updated and extended version of the \acro{FAQ} article
+ that was published as the December 1994 and 1995, and March 1999
+ editions of the \acro{UK}\,\acro{TUG} magazine \BV{} (which weren't
+ formatted like this).
+
+ The article is also available via the World Wide Web.
+\end{quotation}
+
+\ifsinglecolumn
+ \tableofcontents
+\else
+ \begin{multicols}{2}
+ \tableofcontents
+ \end{multicols}
+\fi
+
+\Dings
+
+% label list for later processing
+\labellist
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% load the CTAN references if necessary
+\input{dirctan}
+\input{filectan}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\ifsinglecolumn
+ \input{gather-faqbody}
+\else
+ \begin{multicols}{2}
+ \input{gather-faqbody}
+ \end{multicols}
+\fi
+
+\typeout{*** That makes \thequestion\space questions ***}
+\end{document}
diff --git a/help/uk-tex-faq/locations.mk b/help/uk-tex-faq/locations.mk
new file mode 100644
index 0000000000..49f6146e0c
--- /dev/null
+++ b/help/uk-tex-faq/locations.mk
@@ -0,0 +1,17 @@
+# the locations of files that are targets of the Makefile rules
+
+# on web server
+WEB = /anfs/www/VH-tex/faq-source
+WEB_BETA = /anfs/www/VH-tex/faq-source/beta
+CGI_BIN = /anfs/www/VH-tex/cgi-bin
+
+# on archive machine
+HOME_DIR = /home/rf/tex/faq
+CTAN_ROOT = /anfs/ctan/tex-archive
+
+# on vlan 100 host
+HTMLDIREL = html
+HTMLDIR = $(HOME_DIR)/$(HTMLDIREL)
+
+HTMLDIR_GAMMA = $(HOME_DIR)/html_gamma
+GAMMADIR = $(HOME_DIR)/gamma
diff --git a/help/uk-tex-faq/markup-syntax b/help/uk-tex-faq/markup-syntax
new file mode 100644
index 0000000000..409aff99ca
--- /dev/null
+++ b/help/uk-tex-faq/markup-syntax
@@ -0,0 +1,237 @@
+Writing text for the TeX FAQ -- the requirements
+
+There are some ground rules for text for the FAQ which need to be
+adhered to. Some of the rules relate to the perl program that's used
+to create an HTML file of the FAQ from the TeX source, or to the
+nature of the macros that Sebastian, Alan and I have written; others
+relate to the way in which I try to manage change. Please remember
+that we're attempting distributed authoring of a relatively small
+document over a tight timescale; while I _can_ in principle work into
+the night to put things right after a submission, my employers tend to
+prefer me awake during the working day...
+
+Rules for presentation of text
+------------------------------
+
+1. Don't line wrap in macro calls. Ignore the fact that this can mean
+ very long lines. This restriction applies equally to the
+ []-surrounded optional arguments of macros (e.g., \item).
+
+2. Always put {} after `name' macros (such as \TeX{}). Do this
+ - even if you prefer \TeX\ to ensure the name's delimited
+ - even if the name's immediately followed by punctuation
+
+3. Don't use \verb or \shortvrb -- find alternatives in other
+ constructions like \csx, \cmdinvoke, etc.
+
+Rules for managing the text
+---------------------------
+
+The first version of the FAQ was developed in a distributed fashion by
+the members of the committee of UKTUG. Just now, it's under my (RF's)
+sole control; if there were a clamour for other people to contribute,
+I guess the thing to do _today_ would be to create a sourceforge
+project. (Sourceforge, or anything like it, wasn't even a gleam in
+anyone's eye back in 1994 when we were first discussing the FAQ.)
+
+Source of the text
+------------------
+
+The text currently resides in
+
+newfaq.tex The body of the text
+filectan.tex Declarations of the locations of individual files on
+ CTAN archives
+dirctan.tex Declarations of the directories on CTAN archives
+
+faq.sty The main package
+
+This pre-production version of the text is printed (by default) in
+Adobe Times Roman, etc. An alternative font may by used by setting
+yourself up with a file faqfont.cfg that contains the commands that
+should be used to define what fonts are needed.
+
+A faqfont.cfg which does nothing, and hence leaves LaTeX with its
+default of cm* fonts, is available with the text; if you *want* the
+faq printed in Times Roman, you should not transfer the file (or you
+should delete it once you *have* transferred it).
+
+All these files are to be found in the CTAN distribution of the FAQ,
+in usergrps/uktug/faq
+
+Markup commands
+---------------
+
+The faq is written in LaTeX. Commands to use are:
+
+\CTANdirectory{tag}{directory-path}
+\CTANfile{tag}{file-path}
+
+ These are used in dirctan.tex and filectan.tex, respectively. The
+ <tag> is used in the \CTANref command, and the <*-path> is is what
+ gets typeset in respect of a \CTANref (and what becomes the anchor
+ of an html link to retrieve the referenced thing).
+
+\CTANdirectory*{tag}{directory-path}
+
+ As \CTANdirectory, but appears in HTML as "browse directory" only
+
+\CTANref{tag} (and the ctanrefs environment)
+
+ make reference to a <tag> defined by a \CTANfile or \CTANdirectory
+ command; will usually appear in a ctanrefs environment at the end of
+ an answer. Refer to the files with markup such as \Package,
+ \Class or \ProgName in the body of the question, and then say:
+ \begin{ctanrefs}
+ \item[blah.sty]\CTANref{blah}
+ \end{ctanrefs}
+
+\Question[label]{question-title}
+
+ Set the title of a question, and define a label for it (in fact, an
+ unusual sort of subsection command). The [label] is (now)
+ mandatory, and must be prefixed by "Q-" (as in
+ \Question[Q-newans]{Submitting new material for the FAQ}).
+
+\Qref[intro-text]{anchor-text}{label}
+
+ Refer to a question. The <intro-text> is set before the reference,
+ and is "see question" by default. The <anchor-text> is used in
+ hyper-enabled output, as the anchor for jumping to the labelled
+ question. The <label> is defined somewhere in the document as a
+ \Question command's (nominally) optional argument.
+
+\Qref*{anchor-text}{label}
+
+ Refer to a question. In hyper-enabled output, results are the same
+ as for \Qref; in DVI output, produces
+ anchor-text (see question <label>)
+ special care being taken with surrounding quotes.
+
+\TUGboat{} <vol>(<number>)
+
+ TUGboat reference (we have surprisingly many). Really does have
+ that syntax \TUGboat{} 16(3), though as far as the HTML translator
+ is concerned, the command ends at \TUGboat{} so it doesn't matter if
+ it gets split across lines.
+
+Environment booklist
+
+ Is used to set lists of books; it uses \item in the same way that
+ the description environment does, but sets the label thus defined in
+ normal weight italic text from the current family
+
+\htmlignore ... \endhtmlignore
+
+ Brackets around bits of text that are to be ignored by the html
+ generator (deprecated: use environment typesetversion instead
+
+Environment htmlversion
+
+ Text to appear in HTML but not in the typeset versions of the FAQ.
+ (The body of the environment will be processed before appearing in
+ the HTML output, just the same as text for joint use.)
+ Similar are:
+Environment dviversion (DVI output only)
+Environment pdfversion (PDF output only)
+Environment narrowversion (DVI output only -- narrow since 2-col output)
+Environment wideversion (HTML or PDF output only)
+ Note that we use narrow for non-hyper, and wide for hyper versions
+ of the source.
+
+\htmlonly{text}
+\narrowonly{text}
+\wideonly{text}
+ These three are command versions of the corresponding environments
+
+\nothtml{text}
+
+ Text not to appear in the HTML version
+
+\latexhtml{latex text}{HTML text}
+
+ Typesets latex text, or processes HTML text, according to context
+
+\csx{name}
+
+ A robust command to typeset a control sequence in typewriter. The
+ <name> should only have letters or (at most) others in it -- no
+ active characters, please...
+
+\cmdinvoke{cmd name}<arguments>
+
+ Typesets a complete command invocation, and all its arguments.
+ The LaTeX macro will take arbitrary sequences of optional and
+ mandatory arguments, but while the HTML processor will deal with a
+ wide range of variants, its stunning simplemindedness means it's
+ always good to check such output.
+
+\cmdinvoke*{cmd name}<arguments>
+
+ As \cmdinvoke, but arguments are typeset with \emph
+
+\checked{intials}{date}
+
+ Records when an answer (or part of an answer) was checked, and by
+ whom. Currently typsets as nothing.
+
+\LastEdit{date}
+
+ Date of last editing a Question; argument is yyyy-mm-dd (ISO form)
+ (placed at the end of an answer)
+
+\LastEdit*{date}
+ Last edit was the initial version
+
+\keywords{<stuff>}
+
+ For labelling questions. Doesn't currently have any effect at all.
+
+\Email{<name>@<address>}
+\FTP{<site-address>}
+\File{file-path>}
+\path{file-path>}
+\Newsgroup{usenet-group-name}
+\URL{protocol>://site/path}
+\mailto{mail@ddress}
+
+ All these things typeset their argument in typewriter, but allowing
+ line-splitting at appropriate characters (using url.sty). The last
+ two (\URL and \mailto) become active in both the HTML and PDF
+ versions of the FAQ; \Email is for formatting a name (e.g., a finger
+ identifier) that the reader is _not_ supposed to mail.
+
+\Package{package name} % (no .sty)
+\Class{class name} % (no .cls)
+\ProgName{executable command name}
+
+ Set the item in an appropriate fashion. _Please_ use these commands
+ wherever appropriate.
+
+Names, logos, etc., for use whenever needed (to be used just as
+\name{}):
+
+ \AllTeX [(La)TeX], \LaTeXe, \LaTeXo [LaTeX 2.09, with requisite
+ precautions about dealing with the undead], \MF, \MP [MetaPost], \BV
+ [Baskerville], \PDFTeX, \PDFLaTeX, \CONTeXT, \NTS, \eTeX, \Eplain,
+ \TeXsis, \YandY [the firm, whose name is a bit tricky in HTML],
+ \WYSIWYG, \dots, \ldots, \pounds, \arrowhyph [->, used in
+ descriptions of selections from menus, and looking better when
+ typeset], \textpercent, \textasciitilde
+
+Typesetting things, arguments in braces:
+
+ \acro [for upper-case acronyms such as CTAN], \emph, \textit,
+ \textsl, \meta [as in doc.sty], \texttt, \thinspace, \ISBN
+
+Typesetting environments:
+
+ quote, description, itemize, enumerate, verbatim
+
+Other odds and ends:
+
+ $\pi$, $...$, \$, \#, \ , \&, ~ [just produces a space]
+
+Robin Fairbairns
+2009-06-13
+\LastEdit{2009-03-27}
diff --git a/help/uk-tex-faq/newfaq.pdf b/help/uk-tex-faq/newfaq.pdf
new file mode 100644
index 0000000000..c758c0b589
--- /dev/null
+++ b/help/uk-tex-faq/newfaq.pdf
Binary files differ
diff --git a/help/uk-tex-faq/newfaq.tex b/help/uk-tex-faq/newfaq.tex
new file mode 100644
index 0000000000..be32724192
--- /dev/null
+++ b/help/uk-tex-faq/newfaq.tex
@@ -0,0 +1,67 @@
+% This is the UK TeX FAQ
+%
+\documentclass[a4paper]{faq}
+%
+\setcounter{errorcontextlines}{999}
+%
+% read the first two definitions of faqbody.tex for the file version
+% and date
+\afterassignment\endinput\input gather-faqbody
+%
+\typeout{The UK TeX FAQ, v\faqfileversion, date \faqfiledate}
+%
+% let's not be too fussy while we're developing...
+\hfuzz10pt
+\emergencystretch10pt
+%
+\begin{document}
+\title{The \acro{UK} \TeX{} \acro{FAQ}\\
+ Your \ifpdf\ref*{lastquestion}\else\protect\ref{lastquestion}\fi
+ \ Questions Answered\\
+ version \faqfileversion, date \faqfiledate}
+\author{}
+\maketitle
+
+\centerline{\textsc{Note}}
+
+\begin{quotation}\small
+ This document is an updated and extended version of the \acro{FAQ} article
+ that was published as the December 1994 and 1995, and March 1999
+ editions of the \acro{UK}\,\acro{TUG} magazine \BV{} (which weren't
+ formatted like this).
+
+ The article is also available via the World Wide Web.
+\end{quotation}
+
+\ifsinglecolumn
+ \tableofcontents
+\else
+ \begin{multicols}{2}
+ \tableofcontents
+ \end{multicols}
+\fi
+
+\Dings
+
+% label list for later processing
+\labellist
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% load the CTAN references if necessary
+\input{dirctan}
+\input{filectan}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%\showthe\currentgrouplevel
+\begin{multicols}{2}
+%\expandafter\show\csname @currenvir\endcsname
+%\tracingnesting=2
+ \input{gather-faqbody}
+\end{multicols}
+
+%\showthe\currentgrouplevel
+%% (should be 0)
+%
+%\expandafter\show\csname @currenvir\endcsname
+%% (should be "document"
+\typeout{*** That makes \thequestion\space questions ***}
+\end{document}
diff --git a/help/virtual-fonts.knuth b/help/virtual-fonts.knuth
new file mode 120000
index 0000000000..f6e379df30
--- /dev/null
+++ b/help/virtual-fonts.knuth
@@ -0,0 +1 @@
+../info/virtual-fonts.knuth \ No newline at end of file
diff --git a/help/virtualfonts.txt b/help/virtualfonts.txt
new file mode 100644
index 0000000000..f93fdfc737
--- /dev/null
+++ b/help/virtualfonts.txt
@@ -0,0 +1,233 @@
+Return-Path: <spqr@minster.york.ac.uk>
+Received: from minster.york.ac.uk by ftp.tex.ac.uk (4.1/SMI-4.1)
+ id AA16747; Mon, 1 Feb 93 10:52:05 GMT
+From: spqr@minster.york.ac.uk
+Date: Mon, 1 Feb 93 10:42:10
+Message-Id: <swordfish.728563858@minster.york.ac.uk>
+To: archive@ftp.tex.ac.uk
+In-Reply-To: jeremy@cs.aukuni.ac.nz's message of 28 Jan 93 01:53:05 GMT
+Subject: Re: Virtual fonts
+Status: R
+
+ From: jeremy@cs.aukuni.ac.nz (Jeremy Gibbons)
+ Newsgroups: comp.text.tex
+ Date: 28 Jan 93 01:53:05 GMT
+ Organization: Computer Science Dept. University of Auckland
+
+ In <10234580@MVB.SAIC.COM> Ralf Mollenhauer <ENSP067%FRMRS11.BITNET@SHSU.edu> writes:
+
+ >Now I would like to know:
+ >1. Does there exist any documentation about virtual fonts ?
+ [...]
+ >4. What are *.vf files for ?
+
+ Here is a summary I wrote a while back, complete with comments from
+ Berthold Horn and Yannis Haralambous.
+
+ One of these days I'll get this put in the FAQ.
+
+ Jeremy
+
+
+
+ >Newsgroups: comp.text.tex
+ >Path: cs18.cs.aukuni.ac.nz!jeremy
+ >From: jeremy@cs.aukuni.ac.nz (Jeremy Gibbons)
+ >Subject: Re: Virtual Fonts are...?
+ >Message-ID: <1992Oct19.235603.9537@cs.aukuni.ac.nz>
+ >Cc: jeremy@cs.aukuni.ac.nz
+ >Organization: Computer Science Dept. University of Auckland
+ >References: <1992Oct16.050908.18407@lugb.latrobe.edu.au>
+ >Date: Mon, 19 Oct 1992 23:56:03 GMT
+
+ In <1992Oct16.050908.18407@lugb.latrobe.edu.au> ecsgrt@luxor.latrobe.edu.au (Geoffrey Tobin) writes:
+
+ >1. Exactly what are virtual fonts?
+
+ Here is my understanding of virtual fonts. Perhaps others could join in,
+ and we can put something in the FAQ, or in Geoffrey's "MF for Beginners"?
+ (I seem to have answered this question half a dozen times recently.)
+
+ Knuth discusses virtual fonts in the article "Virtual Fonts: More Fun for
+ Grand Wizards" in TUGboat 11(1), which was also published in TeXhax,
+ volume 90, issues 11 and 12. Go and read that article!
+
+ In summary, virtual fonts are a solution to the problem of using fonts with
+ different encodings (in the sense of "mappings from character codes to
+ character glyphs"). In passing, they also allow you to construct composite
+ fonts (such as Computer Modern Roman letters with oldstyle digits) and
+ composite characters (such as accented letters) without having to do
+ anything clever in TeX. Finally, they provide an elegant solution to the
+ realisation on one system (eg a previewer) of documents set with fonts
+ available only on another system (eg a phototypesetter with native fonts),
+ by substituting available glyphs for unavailable ones. To do all this,
+ "all we need is a good way to specify a mapping from TeX's notion of a font
+ character to a device's capabilities for printing".
+
+ Corresponding to .pl ("property list") files, there are .vpl ("virtual
+ property list") files. These describe, in a human-readable format, both the
+ typesetting information that TeX needs and the information on where to find
+ specific glyphs that a device driver needs. The format for .vpl files is an
+ extension of the format for .pl files. All the information on character
+ metrics (the "metric" information) and ligatures and kerning (the "extra"
+ information, for want of a better term) that TeX requires in a .tfm file is
+ there; for every character, there is also information for the device driver
+ on how to draw the glyph (the "shape" information). The shape information
+ for a virtual character can take the form of a reference to a character in
+ another (perhaps also virtual) font, rules or specials, and all of these
+ can be shifted, scaled and combined. In general, this shape information
+ "can be any sequence of typesetting commands that might appear in a page of
+ a DVI file".
+
+ There are two programs for processing .vpl files, VPtoVF and VFtoVP; these
+ convert between the human-readable information and compact machine-readable
+ data. VPtoVF takes a .vpl file and constructs two files, a .tfm file and a
+ .vf file; the .tfm file contains the metric and extra information which TeX
+ needs, and the .vf file contains the metric and shape information which the
+ device driver needs. VFtoVP takes the .tfm and .vf files and reconstructs
+ the .vpl file.
+
+ Comments?
+
+ Jeremy
+
+ ---
+ Jeremy Gibbons <jeremy@cs.aukuni.ac.nz> tel: +64 9 373 7599
+ Department of Computer Science, fax: +64 9 373 7453
+ University of Auckland, Private Bag 92019, Auckland, New Zealand.
+
+
+
+ From comp.text.tex Fri Oct 23 18:57:34 1992
+ From: bkph@kauai.ai.mit.edu (Berthold K.P. Horn)
+ Date: 21 Oct 92 12:26:30 GMT
+ Newsgroups: comp.text.tex
+ Subject: Re: Virtual Fonts are...?
+
+
+ In article <1992Oct19.235603.9537@cs.aukuni.ac.nz> jeremy@cs.aukuni.ac.nz (Jeremy Gibbons) writes:
+
+ >1. Exactly what are virtual fonts?
+
+ Here is my understanding of virtual fonts. Perhaps others could join in,
+ and we can put something in the FAQ, or in Geoffrey's "MF for Beginners"?
+ (I seem to have answered this question half a dozen times recently.)
+
+ ....
+
+ In summary, virtual fonts are a solution to the problem of using fonts with
+ different encodings (in the sense of "mappings from character codes to
+ character glyphs").
+
+ Just a note on this here: Virtual fonts provide a mechanism for PERMUTING
+ an encoding vector, not for true reencoding, since they deal only with
+ numeric codes, not character names. Characters that are not in the base
+ encoding of the `actual' font, cannot be made accessible by permuting the
+ mapping. For instance, `Yacute' is not in Adobe StandardEncoding, so if
+ your DVI driver does not reencode a font using SE, this character is not
+ accessible, no matter how much you permute the numbers from 0 through 255.
+
+ Note also that you do not need necessarily need virtual fonts to reencode a
+ font. Different DVI drivers provide different mechanisms for doing this.
+ Some provide instead for on-the-fly reencoding.
+
+ There is also a common misconception that one needs virtual fonts in order
+ to use scalable outline fonts (Type 1, TrueType, etc). This is entirely DVI
+ driver dependent. Some can deal with scalable outline fonts without virtual
+ fonts.
+
+ In passing, they also allow you to construct composite
+ fonts (such as Computer Modern Roman letters with oldstyle digits)
+
+ This, on the other hand, is something they ARE good for.
+
+ and composite characters (such as accented letters) without having to do
+ anything clever in TeX.
+
+ This is less of an issue, since most plain vanilla text fonts in Type 1
+ format contain 58 standard accented characters (Although some DVI
+ processors won't let you get at these, however, because of the encoding they
+ use of the font).
+
+ Finally, they provide an elegant solution to the
+ realisation on one system (eg a previewer) of documents set with fonts
+ available only on another system (eg a phototypesetter with native fonts),
+ by substituting available glyphs for unavailable ones.
+
+ Again, this has really nothing to do with virtual fonts. Most previewers
+ (and printer drivers) have a mechanism for substituting existing fonts for
+ missing ones.
+
+ Comments?
+
+ See above.
+
+ Jeremy
+
+
+ Berthold K.P. Horn
+ Cambridge, Massachusetts, USA
+
+
+
+
+ Date: 26 Jan 1993 13:06:51 +0100
+ From: yannis@gat.citilille.fr
+ Subject: virtual fonts
+ Sender: metafont@dmi.ens.fr
+ To: Multiple recipients of list <metafont@dmi.ens.fr>
+ Errors-To: server@dmi.ens.fr
+ Reply-To: metafont@dmi.ens.fr
+ Content-Transfer-Encoding: 7BIT
+ Originator: metafont@dmi.ens.fr
+ Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
+
+
+ Jeremy's description of virtual fonts is very accurate, I would like to add
+ some comments and thoughts.
+
+ A virtual font is a kind of interface between something that is either big
+ (think of PK files for 2540dpi typesetting machines) or rigid (PostScript
+ fonts inside some printer) or anyway external to TeX, and TeX itself. As long
+ as we work with CM/DC fonts everything runs smoothly, but there is the cruel
+ world of incompatibilities there outside and we shouldn't make a different
+ version of TeX for every platform or encoding. There is another very important
+ fact difference between fonts:
+ -- some of them are made for information exchange
+ -- some are made to emulate traditional typography
+ (-- and some are trying to do both, miserably most of the time).
+ In the first case you only have the characters you need for example for email.
+ You wan't find there any fi fl ligatures, think of the CM typewriter fonts.
+ In the second case, you will have characters and/or variants which will serve
+ only for typographical purposes, that is for the visual representation of your
+ text.
+ Most word processors work with one font encoding which aims to cover both needs.
+ This may still be possible for the Roman script, by making some compromises.
+ But for other scripts it is impossible (think of Arabic ligatures). In front
+ of this problem, word processors behave in various ways. For TeX, output quality
+ is the most important goal. So, in most cases, TeX will use it's own output
+ fonts, which will take profit of TeX's extraordinary features of box manipu-
+ lation etc etc.
+ You see now what I mean: TeX uses it's own fonts for the output (or at least
+ should use it's own fonts to get the best quality --- a sad counterexample is
+ Moschovakis' Greek system where quality is sacrified for the sake of IBM's
+ encoding) and if this output should use external commercail fonts, somebody
+ must change: either the font, or TeX.
+ Virtual fonts are there to fill this gap. We can now (and will!!) make
+ typesetting systems for all languages having typographical quality in our mind
+ and not compatibility with anything or anyone. A virtual structure will then
+ insure compatibility with the outside world.
+
+ So let me summarize: suppose we want a TeX system for Tomanian.
+ The input will be done in Tomanian ISO for data exchange, or some equally
+ important and standardized encoding.
+ TeX's output will be done using a private encoding, carefully studied so that
+ all TeX's features having been exploited to insure max typographical quality.
+ Virtual structures will be used to convert the private encoding found in the
+ DVI file into any possible encoding of the real Tomanian world.
+
+ In my mind, virtual fonts are TeX's passport to travel around the world, and
+ still remain universal and unique.
+
+ Cheers
+ Yannis
diff --git a/help/wp-conv/GPL.txt b/help/wp-conv/GPL.txt
new file mode 100644
index 0000000000..694ca98495
--- /dev/null
+++ b/help/wp-conv/GPL.txt
@@ -0,0 +1,341 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ <http://www.gnu.org>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/help/wp-conv/bin/license.txt b/help/wp-conv/bin/license.txt
new file mode 100644
index 0000000000..694ca98495
--- /dev/null
+++ b/help/wp-conv/bin/license.txt
@@ -0,0 +1,341 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ <http://www.gnu.org>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/help/wp-conv/html2LaTeX.txt b/help/wp-conv/html2LaTeX.txt
new file mode 100644
index 0000000000..c0f2df7ca9
--- /dev/null
+++ b/help/wp-conv/html2LaTeX.txt
@@ -0,0 +1,8 @@
+Filename: html2latex.zip
+
+Function: Creates LateX 2.09 files from html-files.
+
+Comments: Compiled from Unix sources version 0.9c with emx 0.9c fix 2.
+ Runs on DOS, Windows (3.x, 9x, NT), OS/2 Warp
+
+Recompiled by Roland Reimers (reimers@muffin.physik.uni-bremen.de)
diff --git a/help/wp-conv/html2latex.html b/help/wp-conv/html2latex.html
new file mode 100644
index 0000000000..f40d6c35bd
--- /dev/null
+++ b/help/wp-conv/html2latex.html
@@ -0,0 +1,147 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>html2latex(1)</title>
+</head>
+
+<body>
+
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+
+Up to <a href="textopc.html">Converters from LaTeX to PC
+Textprocessors - Overview</a></p>
+
+<h1>NAME</h1>
+
+<p>html2latex -- convert HTML markup to LaTeX markup </p>
+
+<p>The original author, Nathan Torrington, wrote:<br>
+
+"The source is available
+<a href="http://www.vuw.ac.nz/non-local/software/html2latex-0.9c.tar.Z">here (external link)</a>",
+<br>
+but this is obviously no longer the case. <br>
+Instead, I (W.Hennings) put it <a href="bin/html2ltx.zip">here</a>.
+This zip-file includes an msdos executable. <br>
+There is another compiled version on CTAN which I also put
+<a href="bin/html2LaTeX.zip">here</a> (see <a href="html2LaTeX.txt">description</a>), but both
+result from the same source. </p>
+
+<p></p>
+
+<h1>SYNOPSIS</h1>
+
+<p><tt>html2latex <i>[opt ...] [file ...]</i></tt>
+</p>
+
+<h1>DESCRIPTION</h1>
+
+<p>For each file argument, <i>html2latex</i>
+converts the text as HTML markup to LaTeX markup. If no files are
+specified, a usage message is given.
+Input will be taken from standard input for files named <em>-</em>.
+Output will to a similarly named file with a <b>.tex</b>
+extension (<i>html2latex</i> recognises
+<b>.html</b> extensions). </p>
+
+<p>Options modify the action of <i>html2latex</i>.
+The options are: </p>
+
+<dl>
+
+ <dt>-n</dt>
+
+ <dd>Number sections. </dd>
+
+ <dt>-p</dt>
+
+ <dd>Place page breaks after the title page (if present) and the
+table of
+contents (if present). </dd>
+
+ <dt>-c</dt>
+
+ <dd>Generate a table of contents. </dd>
+
+ <dt>-s</dt>
+
+ <dd>Create no files -- LaTeX is output to stdout. </dd>
+
+ <dt>-t Title</dt>
+
+ <dd>Generate a title page, with the title 'Title'. </dd>
+
+ <dt>-a Author</dt>
+
+ <dd>Generate a title page, with the author 'Author'. </dd>
+
+</dl>
+
+<h1>EXAMPLES</h1>
+
+<p>An example of use is html2latex -n - &lt; file.html | less
+This converts <b>file.html</b> to LaTeX and pages through the output.
+The sections (corresponding to heading tags in the HTML source) will
+be numbered. </p>
+
+<p>Another example is html2latex -t 'Introduction to HTML' -a
+gnat -p -c html-intro This takes input from the file <b>html-intro</b>,
+writing to <b>html-intro.tex</b>, and adds a title page
+(with title <i>Introduction to HTML</i> and
+author <i>gnat</i>) and table of contents with page-breaks after
+both. The sections of the document are not numbered. </p>
+
+<h1>BUGS</h1>
+
+<p>Current the only HTML tags supported are: <b>TITLE, H1,
+H2, H3, H4, H5, H6,
+UL, OL, DL, DT, DD, LI, B, I, U, EM, STRONG, CODE, SAMP, KBD, VAR, DFN,
+CITE, LISTING</b>. The only recognised SGML escapes are <b>&amp;amp,
+&amp;lt,
+&amp;gt</b>. <b>ADDRESS</b> tags are handled
+badly. </p>
+
+<p>The <b>COMPACT</b> attribute to a <b>DL</b>
+tag is not recognised.
+<b>MENU</b> and <b>DIR</b> styles are not handled well.
+<b>TITLE</b> text are ignored. </p>
+
+<p>Currently <b>PRE</b> tags are not handled at all.
+</p>
+
+<p>The entire file is read into memory. For long HTML documents
+on machines with little memory, this may cause problems. </p>
+
+<h1>CREDITS</h1>
+
+<p>Nathan Torkington adapted the HTML parser from NCSA's Xmosaic
+package
+(<b>file://ncsa.uiuc.edu/Web/xmosaic</b>) and wrote the
+conversion code. The HTML parser code is subject to the NCSA
+restrictions. The conversion code is subject to the VUW restrictions.
+Enquiries should be sent via e-mail to
+<tt>Nathan.Torkington "at" vuw.ac.nz</tt>. </p>
+
+<p></p>
+
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+
+ <li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format)
+is granted as long as the contents are unchanged. </li>
+
+ <li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+
+</body>
+</html>
diff --git a/help/wp-conv/index.html b/help/wp-conv/index.html
new file mode 100644
index 0000000000..d62e362db4
--- /dev/null
+++ b/help/wp-conv/index.html
@@ -0,0 +1,106 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en-us"><head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta name="description" content="Converters between LaTeX and PC Textprocessors" lang="en">
+<meta name="keywords" content="FAQ, converter, LaTeX, winword, word perfect, textprocessor" lang="en"><title>Converters between LaTeX and PC Textprocessors</title>
+
+</head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a></p>
+<h1>Converters between LaTeX and PC Textprocessors</h1>
+<p>Author: Wilfried Hennings (texconvfaq "at" gmx.de).<br>
+last update of this page or any of its subpages: June 14, 2012<br>
+The url of this page is <a href="http://tug.org/utilities/texconv/index.html">
+http://tug.org/utilities/texconv/index.html</a></p>
+<p><strong>I am experiencing that I have practically no
+time to keep these pages up to date so I'd like to retreat from this. <br>
+I would be glad if someone else would take over this task.
+I would then transfer the copyright to her/him.</strong><br>
+(The copyright only serves two objectives:<br>
+&#8211; to prevent anyone from claiming the copyright for himself
+and thus
+preventing the original author from continuing her/his work,<br>
+&#8211; to achieve that the author is been informed about any
+incorrect or
+missing information.)</p>
+<p><strong>The main list is divided into two parts:</strong></p>
+<p><strong>Converters <a href="textopc.html">from
+LaTeX to PC textprocessors</a></strong></p>
+<p><strong>Converters <a href="pctotex.html">from
+PC textprocessors to LaTeX</a></strong></p>
+<p>Please also read the <a href="#copyright">copyright</a>
+and the <a href="#disclaimer">disclaimer</a></p>
+<p>You can also <strong>download the whole set of www pages</strong>
+in a <strong><a href="wp-conv.zip">zip file</a></strong>.
+It is also available from <a href="#ctan">CTAN</a>
+(directory .../help/wp-conv/).</p>
+<h2>Related external www pages</h2>
+<p><a href="http://mactex-wiki.tug.org/wiki/index.php?title=Converters" target="_blank">
+Mac Converters for TeX/LaTeX (external link)</a></p>
+<p><a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv" target="_blank">TeX-FAQ (English), Other conversions to and
+from (La)TeX</a></p>
+<p><a href="http://projekte.dante.de/DanteFAQ/DokumentKonverter" target="_blank">
+TeX-FAQ (auf Deutsch), Dokument-Konverter von bzw. in das
+(La)TeX-Markup-Format (externer Link)</a>
+</p>
+<h3><a name="ctan">CTAN</a></h3>
+<p>CTAN is "The Comprehensive TeX Archive Network". It consists
+of two primary hosts and many mirrors.<br>
+To reduce load on the primary hosts, the following link where you find
+the converters uses the generic "mirror" address which resolves to one
+of the mirror hosts:
+<br>
+<a href="http://mirror.ctan.org/support/" target="_blank">http://mirror.ctan.org/support/</a></p>
+<p>The primary CTAN hosts &#8211; which also allow uploading &#8211; are the
+German and the British:<br>
+<a href="http://www.dante.de/" target="_blank">Der
+deutsche CTAN
+Server (The German CTAN server - external link)</a><br>
+<a href="http://www.tex.ac.uk/" target="_blank">The
+British CTAN
+server (external link)</a></p>
+<p>It is also possible to order CD-ROM(s) from CTAN with the CTAN
+contents &#8211; <br>
+description in German: <a href="http://projekte.dante.de/DanteFAQ/Bezugsquellen" target="_blank">
+http://projekte.dante.de/DanteFAQ/Bezugsquellen (external link)</a>,<br>
+description in English: <a href="http://www.tug.org/store/#software" target="_blank">
+http://www.tug.org/store/#software (external link)</a>.</p>
+<hr>
+<p>This HTML page is part of the texconv pages.</p>
+<p><big><strong><a name="copyright">Copyright</a></strong></big>
+ 1998 &#8230; 2012 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>It must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation
+format) is granted as long as the contents are unchanged.</li>
+<li>You may NOT ask money for it except a reasonable cost for
+media and distribution.</li>
+</ul>
+<h2><a name="disclaimer">Disclaimer</a></h2>
+<p>1. Because the information is licensed free of charge, there
+is no warranty for the information, to the extent permitted by
+applicable law.
+Except when otherwise stated in writing the copyright holders and/or
+other parties provide the information "as is" without warranty of any
+kind, either expressed or implied, including, but not limited to, the
+implied warranties of merchantability and fitness for a particular
+purpose. The entire risk as to the quality and performance of the
+information is with you. Should the information prove defective, you
+assume the cost of all necessary servicing, repair or correction.</p>
+<p>2. At the time of putting a link in one of my pages, I found
+the linked content appropriate and probably helpful for readers of my
+pages. However in most cases I did not test whether the information on
+external pages is correct or conforms to legal requirements so I take
+no responsibility for its correctness nor for its legal conformity.
+Moreover, external contents may be changed without my knowledge and an
+URL may be taken over by a different party without my knowledge. I
+therefore also take no responsibility for changes of external contents
+after adding a link to one of my webpages.
+If a link seems inappropriate, please inform me. (In this context,
+"external contents" means contents of webpages of which I am not the
+author. In my pages they are marked by the clause "external link".)</p>
+<p>3. All opinions mentioned are my own.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/ktbugs.html b/help/wp-conv/ktbugs.html
new file mode 100644
index 0000000000..a4de6e6b35
--- /dev/null
+++ b/help/wp-conv/ktbugs.html
@@ -0,0 +1,88 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>Why K-Talk's software doesn't work for me</title>
+
+</head>
+
+<body>
+
+<h1>Why K-Talk's software doesn't work for me</h1>
+
+<p>last substantial update: May 25, 1998<br>
+editorial update: Oct. 10, 2008</p>
+
+<h3>Distinguish two groups of causes why K-Talk's software
+doesn't work for me:
+</h3>
+
+<h3>A. General Problems</h3>
+
+<p>1. K-Talk's software uses their own formula editor "MathEdit",
+which is incompatible with Microsoft's equation editor. Therefore if I
+convert a LaTeX file to word, only users having K-Talk's MathEdit are
+able to use the converted file.</p>
+
+<p>2. On the PC wordprocessor side, K-Talk's software primarily
+uses the WordPerfect 5.1 format. MS Word users must install extra
+macros for conversion to a "tagged document file". <br>
+
+These macros however are written for Word6 and need some dlls belonging
+to word6 which I don't have because I have word7(95). So I could not
+get them running.</p>
+
+<p>3. Capacity: on converting the "LaTeX2e Kurzbeschreibung"
+(from CTAN, "l2kurz.tex" plus include-files) I get the error message
+"file l2k2.tex too large to include".<br>
+
+As LaTeX is intended for large documents, a professional converter
+should be able to convert large documents!</p>
+
+<h3>B. Localization Problems</h3>
+
+<p>1. In addition to being not compatible with MS word versions
+later than word6, the word macros need to be localized if one doesn't
+have the English version of Word.</p>
+
+<p>2. TexPort doesn't recognize German umlauts used in german.sty
+- see the converted example "l2kurz"</p>
+
+<h3>Sample of Converted Files (LaTeX -&gt; WP)</h3>
+
+<p><a href="bin/essent.zip">essent.zip</a>
+containing the files:<br>
+essential.tex, hndout.sty=LaTeX source<br>
+essent.wp5=wp5.1 file converted by TexPort </p>
+
+<p><a href="bin/l2kurz.zip">l2kurz.zip</a>
+containing the files:<br>
+l2kurz.tex, l2k1.tex, l2k2.tex, l2k3.tex, l2k4.tex, l2ksym.tex, a4.sty,
+german.sty=LaTeX source<br>
+l2kurz.wp5=wp5.1 file converted by TexPort</p>
+
+<p>where essential.tex and l2kurz.tex are originals from CTAN.<br>
+(Meanwhile these files got updated on CTAN.
+If you want to use these files for other purpose than reproducing my
+conclusion, get the current versions from CTAN.)</p>
+
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+
+ <li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+
+ <li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+
+</body>
+</html>
diff --git a/help/wp-conv/la2mml.html b/help/wp-conv/la2mml.html
new file mode 100644
index 0000000000..f3e61f8357
--- /dev/null
+++ b/help/wp-conv/la2mml.html
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>la2mml: LaTeX to FrameMaker</title></head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="textopc.html">Converters from LaTeX to PC
+Textprocessors - Overview</a></p>
+<h1>la2mml</h1>
+<p>last update: Jan. 22, 2008</p>
+<p>Converts LaTeX documents to MML (Maker Markup Language), a
+format used by Adobe FrameMaker, a page layout program available for
+Unix, Windows, and Mac. </p>
+<p>USA site:
+<a href="http://vasc.ri.cmu.edu/old_help/Document/Latex2fm/latex2fm.html">http://vasc.ri.cmu.edu/old_help/Document/Latex2fm/latex2fm.html
+(external link)</a>
+</p>
+<p>The site <a href="http://www.cs.stir.ac.uk/%7Ekjt/software/framemaker/">
+http://www.cs.stir.ac.uk/~kjt/software/framemaker/ (external link)</a>
+contains templates which make conversion from Framemaker to LaTeX more
+easy. It also supplies converters from Framemaker to LaTeX and from
+LaTeX to
+Framemaker.</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
diff --git a/help/wp-conv/laola.html b/help/wp-conv/laola.html
new file mode 100644
index 0000000000..0b509318b8
--- /dev/null
+++ b/help/wp-conv/laola.html
@@ -0,0 +1,37 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>LAOLA</title>
+
+</head>
+
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX - Overview</a></p>
+<h1>LAOLA</h1>
+<p>last update: Jan. 22, 2008</p>
+<p>LAOLA can read Word6- and Word7-documents under Unix and
+extract the text. </p>
+<p>Excerpt from the WWW page: "LAOLA is a collection of
+documentations and perl programs dealing with binary file formats of
+Windows program documents. LAOLA is giving access to the raw document
+streams of any program using
+"structured storage" technology to save its documents. ELSER is
+dealing especially with these streams as they are present in Word 6 and
+Word 7 documents." </p>
+<p>See <a href="http://user.cs.tu-berlin.de/%7Eschwartz/pmh/">
+http://user.cs.tu-berlin.de/~schwartz/pmh/ (external link)</a>
+</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
diff --git a/help/wp-conv/latex2rtf.html b/help/wp-conv/latex2rtf.html
new file mode 100644
index 0000000000..8ba5ec132a
--- /dev/null
+++ b/help/wp-conv/latex2rtf.html
@@ -0,0 +1,114 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>latex2rtf converter</title></head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="textopc.html">Converters from LaTeX to PC
+Textprocessors -
+Overview</a></p>
+<h1>latex2rtf converter </h1>
+<p>this page last updated on Jan. 10, 2011</p>
+<p>latex2rtf, written in C. </p>
+<p>Converts most standard LaTeX markup and some more, but only
+those
+markup and packages which are hard-coded in latex2rtf's program code.
+</p>
+<p>LaTeX equations are converted either to Word's formula fields
+(EQ fields) or images.
+(Anyone who wants and is able to implement conversion to equation
+editor objects please contact me (texconvfaq "at" gmx.de).)<br>
+The default is conversion to formula fields. These generally display
+the equations in a reasonable quality. If in Word you double-click on a
+formula field, it will be converted to an equation editor object, but
+often with really bad result (depending on which constructs are
+contained in the equation). <br>
+Conversion of equations to images requires a TeX installation,
+ImageMagick, and Ghostscript.
+</p>
+<p>References are converted to field functions which must be
+updated after loading the resulting rtf file into Word (mark complete
+document and press F9).
+</p>
+<p>Still there are drawbacks in the conversion. In fact, don't
+expect any LaTeX-file to be converted like you want, don't expect it to
+be converted without errors or warnings, and: don't even expect it to
+be converted at all, since LaTeX2rtf is at most at a very experimental
+stage. LaTeX2rtf is known to have a lot of bugs. In fact we could state
+that there are some special cases, where a LaTeX-file can be translated
+to RTF satisfactorily by LaTeX2rtf. <br>
+-- This was sort of disclaimer, ok? Ok! </p>
+<p>C-source and makefiles (compiles on Unix and Macintosh OSX
+with gcc;
+Linux with gcc; MS-DOS/Windows with gcc (djgpp or cygwin); and
+Macintosh OS9 with the DropUnix environment) as well as executables for
+MS-DOS (compatible with win95, win98, winME, nt4.0, win2000, winXP, and
+Vista) and Macintosh are available from <a href="http://sourceforge.net/projects/latex2rtf/">
+http://sourceforge.net/projects/latex2rtf/ (external link)</a>. </p>
+<p>A stable but not always the most recent release is also
+available from <a href="index.html#ctan">CTAN</a>,
+directory .../support/latex2rtf <br>
+(the ... stands for a host specific base directory, which often is
+either "/pub/tex" or "/tex-archive"). </p>
+<p>We still seek for people joining us as maintainer or
+developer. If you are interested, contact me (texconvfaq "at" gmx.de).</p>
+<h3>Program Copyright:</h3>
+<p>This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License as
+published by the
+Free Software Foundation; either version 2 of the License, or (at your
+option) any later version. <br>
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANT-ABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the <a href="GPL.txt">GNU General Public License</a>
+for more details. </p>
+<p>Note that this Copyright note only applies to the changes made
+to get the actual version. The older versions have their own Copyright
+policy stated in their distribution. </p>
+<h3>History:</h3>
+<p> In 1994 the first Version of LaTeX2rtf was written by a group
+of students of the Viena University supervised by Ralf Schlatterbeck.
+They took up a LaTeX parser and added most of the functionality to the
+program. In 1995 work continued with a second group of students. The
+result was LaTeX2rtf Version 1.5. </p>
+<p>Unfortunately, two different persons started further
+development of that program, not knowing of each other:</p>
+<ul>
+<li>In 1997, Daniel Taupin started updating this converter. He
+added e.g. the feature to convert equations to bitmaps by invoking the
+TeX engine. However this required the emTeX distribution (for DOS)
+which is no longer supported. </li>
+<li> In 1998, Georg Lehner found the reference to the original
+LaTeX2rtf on this webpage and added some functionality. His work
+resulted in version 1.8aa. Unfortunately he did not know about Daniel's
+developments.</li>
+</ul>
+<p>In 2001, Scott Prahl started to make some significant
+enhancements, also including many of Daniel's additions. He is still
+working on it. Latest stable release is 2.1.1 b5 and includes all of
+the features of Daniel's version.</p>
+<p>Temporarily I (Wilfried Hennings) feel responsible for
+coordinating the exchange of development information. But <em>we
+are still seeking for a person who can act as coordinator of future
+development, and we also need a person to take over the development.
+</em> Anyone feeling able to do that
+please contact me by email to texconvfaq "at" gmx.de. </p>
+<p>The project is now hosted at sourceforge.net which aids in
+further development. Visit its homepage at <a href="http://latex2rtf.sourceforge.net/">
+http://latex2rtf.sourceforge.net/ (external link)</a> or its
+project page at <a href="http://sourceforge.net/projects/latex2rtf/">
+http://sourceforge.net/projects/latex2rtf/ (external link)</a>. </p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 &#8230; 2011 Wilfried
+Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/ltx2word.html b/help/wp-conv/ltx2word.html
new file mode 100644
index 0000000000..8df71c27d5
--- /dev/null
+++ b/help/wp-conv/ltx2word.html
@@ -0,0 +1,97 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+ <title>ltx2word macros</title></head>
+
+<body>
+
+
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+
+Up to <a href="textopc.html">Converters from LaTeX to PC Textprocessors -
+Overview</a></p>
+
+<h1>ltx2word macros</h1>
+
+<p>last update: July 24, 2001</p>
+
+<p>LaTeX to WinWord 6, WinWord 7(95) and WinWord 97 converter, written as Word
+macros. </p>
+
+<p>Author: W. Hennings (myself) (texconvfaq "at" gmx.de)</p>
+
+<p>Caution! Quick-and-dirty "pre-alpha" version! <br>
+
+The author grants no warranty of any kind, especially neither for functionality
+nor for any damage caused by use of the program, but suggestions for
+enhancement are welcome. </p>
+
+<p>New version June 11, 1997: More tags implemented, e.g. now also converts
+\begin{tabular} ... \end{tabular} to a table and \begin{center} ...
+\end{center} to centered text. Still no formulae!!</p>
+
+<p>Download: <a href="bin/ltx2word.zip">ltx2word.zip</a>. This zipfile
+contains: </p>
+
+<dl>
+
+ <dt>ltx2w95.dot:</dt>
+
+ <dd>Template for GERMAN WinWord 7, probably also WinWord 6. <br>
+
+NOT designed for, but adaptable to non-German versions. </dd>
+
+ <dt>ltx2w97.doc:</dt>
+
+ <dd>Converted to Word97 by Carsten Schwartz &lt;smike "at" vip.cybercity.dk&gt;</dd>
+
+ <dt>license.txt:</dt>
+
+ <dd>The GNU Public License</dd>
+
+</dl>
+
+<p>Note: This macro set is free software; you can redistribute it and/or modify
+it under the terms of the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
+General Public License</a> as published by the Free Software Foundation; either
+version 2 of the License, or (at your option) any later version. </p>
+
+<hr>
+
+<p>This HTML page is part of the texconv pages.<br>
+
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+
+ <li>it must remain intact and the contents unchanged; if you'd like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting (e.g.
+from HTML to some other presentation format) is granted as long as the contents
+are unchanged. </li>
+
+ <li>you may NOT ask money for it except a reasonable cost for media and
+distribution</li>
+
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+
+</body></html>
+pyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+>
diff --git a/help/wp-conv/mathtype.html b/help/wp-conv/mathtype.html
new file mode 100644
index 0000000000..03aa9a61b2
--- /dev/null
+++ b/help/wp-conv/mathtype.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+ <title>MathType equation editor</title></head>
+
+<body>
+
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC Textprocessors to LaTeX -
+Overview</a></p>
+
+<h1>MathType equation editor</h1>
+
+<p>last update: Sep. 21, 2007</p>
+
+<p>MathType, the full scale, commercial version of the equation editor
+which comes with Microsoft Word, is capable of converting its equations
+to TeX format. Plain Tex, LaTeX, AMS-TeX, AMS-LaTeX and several flavors
+of MathML are available in the current release 6. <br>
+MathType comes with a Word macro which will convert all the equations in a Word
+document into TeX.<br>
+One can also type or paste an equation coded in TeX into MathType 6.</p>
+<p>A special version of MathType, called TeXaide, is now available to be
+downloaded for free from the <a href="http://www.mathtype.com/mathtype/">mathtype homepage (external link)</a>.
+With TeXaide you can compose equations and output them in Plain TeX, AMS TeX,
+LaTeX, and AMS LaTeX. You can also select and copy a Word equation
+(with or without opening the equation editor), paste it into TeXaide
+and then output it in TeX format, one equation at a time. It runs on
+Windows 95, 98, 2000 and NT 4.0 and newer. </p>
+
+<p>I personally have MathType 3.1 and 4.0, too, and these are able to
+convert from their own format as well as from WinWord's EquationEditor
+format TO TeX. The backward direction (TeX to MathType) is ONLY possible
+for TeX code which was produced by MathType (containing a TeX comment
+which allows MathType to see how it was generated).
+<br>However MathType 6 now allows typing or pasting TeX code which thereby
+is converted to a MathType object.
+<br>Back-conversion from MathType to EquationEditor is only possible
+from MathType 3.1 and 4, not from the later versions. </p>
+
+<hr>
+
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2002, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+ <li>it must remain intact and the contents unchanged; if you'd like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting (e.g.
+from HTML to some other presentation format) is granted as long as the contents
+are unchanged. </li>
+ <li>you may NOT ask money for it except a reasonable cost for media and
+distribution</li>
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/pc2txtbl.html b/help/wp-conv/pc2txtbl.html
new file mode 100644
index 0000000000..10437c6849
--- /dev/null
+++ b/help/wp-conv/pc2txtbl.html
@@ -0,0 +1,231 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en-us"><head><title>PC -&gt; LaTeX Converter Quick Comparison List</title></head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>PC -&gt; LaTeX Converter Quick Comparison List</h1>
+<p><strong>Switch conversion direction: <a href="tx2pctbl.html">From LaTeX to
+PC</a></strong></p>
+<p>Author: Wilfried Hennings (texconvfaq "at" gmx.de), last
+update: March 3, 2011</p>
+<p>NOTE: This table is still under construction. I only had time
+to include the most recent converters.</p>
+<table border="1" width="100%">
+<tbody>
+<tr>
+<th width="18%">Program<br>
+Author(s)<br>
+referred version</th>
+<th width="40%">Features</th>
+<th width="20%">supported Systems</th>
+<th width="190">where to get<br>
+(external links!)</th>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">rtf2latex2e
+<br>
+by Ujwal Sathyam and Scott Prahl (free)<br>2-0-1 (Feb. 1, 2011)</td>
+<td align="left" valign="top" width="40%">convert
+from RTF
+<ul>
+<li> detects text style: bold, italic, color, big,
+small,... </li>
+<li> reads embedded figures: PICT, EMF, GIF, TIFF, WMF, PNG, JPEG </li>
+<li> reads tables: simple to semi-complex </li>
+<li>reads Equation Editor or MathType equations</li>
+<li>converts most greek and math symbols </li>
+<li> reads footnotes</li>
+<li>converted latex file uses utf8<br></li><li>supports codepages 1250, 1251, 1252, 1254, mac, NeXt </li>
+<li> translates hyperlinks using the hyperref package </li>
+</ul>
+</td>
+<td align="left" valign="top" width="20%">all
+kinds of Unix <br>
+DOS, MS Windows</td>
+<td align="left" valign="top" width="190">CTAN:<br>
+.../support/rtf2latex2e <br>
+for most recent version see <br>
+<a href="http://sourceforge.net/projects/rtf2latex2e/">sourceforge.net/
+projects/rtf2latex2e/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">wsW2LTXGUI<br>
+by Ingo H. de Boer<br>
+1.1.0.0 (May 25, 2006)</td>
+<td align="left" valign="top" width="40%">The
+wsW2LTXGUI program is a graphical user interface to the wsW2LTX library
+which handles all the methods described in the wsW2LTX API reference.<br>
+The wsW2LTX library is an application programming interface (API)
+designed to translate a MS Word document to LaTeX. The library is based
+on libwv and on several other (mostly Unix based) libraries. </td>
+<td align="left" valign="top" width="20%">MS
+Windows</td>
+<td align="left" valign="top" width="190">CTAN:<br>
+.../support/word2latex<br>
+homepage: <a href="http://www.winshell.de/modules/w2ltx_download/">www.winshell.de/
+modules/w2ltx_download/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">wp2latex
+<br>
+by J. Fojtik (free)<br>
+3.53 (Sep. 19, 2010)</td>
+<td align="left" valign="top" width="40%">convert
+from WordPerfect 3.x, 4.x, 5.x, and 6/7/8.x document files <br>
+converts (among others):
+<ul>
+<li>Equations</li>
+<li>Tables </li>
+<li>Footnotes, Endnotes, Cross-references</li>
+<li>Superscript, Subscript</li>
+<li>Extended characters (foreign language/accented, math,
+Greek - not linedrawing)</li>
+</ul>
+</td>
+<td align="left" valign="top" width="20%">Linux<br>
+DOS, MS Windows</td>
+<td align="left" valign="top" width="190">CTAN:<br>
+.../support/wp2latex
+(older version 3.38)<br>
+for most recent version see <a href="http://www.penguin.cz/%7Efojtik/wp2latex/wp2latex.htm">www.penguin.cz/
+~fojtik/wp2latex/ wp2latex.htm</a> </td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Word2TeX<br>
+Chikrii Softlab. shareware, 99$ (45$ academic)<br>
+version 5.01 (Feb. 2010)</td>
+<td align="left" valign="top" width="40%">save
+as LaTeX from within Word<br>
+converts:
+<ul>
+<li>Equation Editor 2.x-3.x, Design Science MathType 1.x,
+2.x, 3.x, 3.5, 4.0 embedded objects (*)</li>
+<li>figures (to EPS or PDF)(*)</li>
+<li>tables (even very complicated) (*)</li>
+<li>footnotes</li>
+<li>endnotes (to bibliography)</li>
+<li>index</li>
+<li>cross-references</li>
+<li>paragraph styles (heading1 to heading4, custom styles)</li>
+<li>character attributes</li>
+<li>Greek-charset</li>
+<li>multibyte character encodings (Unicode)</li>
+<li>and many more (see <a href="http://www.word2tex.com/">homepage</a>)</li>
+</ul>
+(*) some restrictions will apply in unregistered Word2TeX</td>
+<td align="left" valign="top" width="20%">MS
+Windows 98 + Word for Windows&nbsp;95, or newer required</td>
+<td align="left" valign="top" width="190">homepage:<br>
+<a href="http://www.word2tex.com/">www.word2tex.com</a></td>
+</tr>
+<tr>
+<td align="left" valign="top">Word-to-LaTeX<br>
+Michal Kebrt (Shareware, 79&nbsp;$)<br>version 2.0 (Jan 2011)</td>
+<td align="left" valign="top">save as LaTeX
+from within Word<br>
+converts:
+<ul>
+<li>equations (conversion to TeX code requires MathType,
+otherwise they are converted to png or eps)</li>
+<li>raster images</li>
+<li>tables</li>
+<li>lists</li>
+<li>footnotes and endnotes</li>
+<li>bookmarks</li>
+<li>and more (see <a href="http://www.wordtolatex.com/">homepage</a>)</li>
+</ul>
+</td>
+<td align="left" valign="top">MS Windows +
+Word for Windows 2002 (XP) or newer required, plus MS .NET Framework 2.0</td>
+<td align="left" valign="top">Homepage: <br>
+<a href="http://www.wordtolatex.com/">www.wordtolatex.com</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Writer2LaTeX<br>
+converts OpenOffice.org / StarOfficeWriter documents into LaTeX2e
+(free).<br>1.0.0 (Sept. 21, 2009)</td>
+<td align="left" valign="top" width="40%">The
+current version deals with plain text and formulas. <br>
+It is included as export filter in OpenOffice 2.04 and later<br>
+</td>
+<td align="left" valign="top" width="20%">all
+OS supporting Java </td>
+<td align="left" valign="top" width="190">homepage:<br>
+<a href="http://writer2latex.sourceforge.net/">writer2latex.sourceforge.net/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Calc2LaTeX<br>
+converts OpenOffice.org spreadsheet tables into LaTeX2e (free)<br>0.2.4 (Oct. 29, 2005)</td>
+<td align="left" valign="top" width="40%">Calc2LaTeX
+is an OpenOffice.org Calc (Spreadsheet) macro for converting tables.</td>
+<td align="left" valign="top" width="20%">Linux
+or MS Windows plus Open Office 1.03, 1.1 or 2.0</td>
+<td align="left" valign="top" width="190">homepage:<br>
+<a href="http://calc2latex.sourceforge.net/">calc2latex.sourceforge.net/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Excel2LaTeX<br>
+converts Excel spreadsheet to LaTeX<br>2.1 (Sept. 18, 2008)</td>
+<td align="left" valign="top" width="40%">Excel-macro
+to convert Excel to LaTeX. The generated LaTeX code uses the tabular
+environment.</td>
+<td align="left" valign="top" width="20%">MS
+Windows plus MS Excel</td>
+<td align="left" valign="top" width="190">CTAN:<br><a href="http://www.ctan.org/tex-archive/support/excel2latex/">www.ctan.org/tex-archive/ support/excel2latex/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Gnumeric
+can import Excel data and export to LaTeX</td>
+<td align="left" valign="top" width="40%">Gnumeric
+is an open source
+spreadsheet application which can import Excel data and export to LaTeX</td>
+<td align="left" valign="top" width="20%">Linux
+or MS Windows</td>
+<td align="left" valign="top" width="190">homepage:<br>
+<a href="http://www.gnome.org/projects/gnumeric/">www.gnome.org/
+projects/gnumeric/</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">Publishing
+Companion<br>
+KTalk Communications (commercial, 399 US$)<br>
+v. 2.21</td>
+<td align="left" valign="top" width="40%">converts
+(among others):
+<ul>
+<li>Automatic Indexes</li>
+<li>Footnotes, Endnotes</li>
+<li>Foreign Characters</li>
+<li>Running Headers &amp; Footers</li>
+<li>Superscripts &amp; Subscripts</li>
+<li>MathEdit Math Equations</li>
+<li>MS Word 6.0 Math Equations</li>
+<li>WordPerfect Math Equations</li>
+</ul>
+</td>
+<td align="left" valign="top" width="20%">DOS
+/ MS Windows</td>
+<td align="left" valign="top" width="190">homepage:<br>
+<a href="http://www.ktalk.com/pubcomp.html">
+www.ktalk.com/
+pubcomp.html</a></td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 ... 2011
+Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/pctotex.html b/help/wp-conv/pctotex.html
new file mode 100644
index 0000000000..1be2094c86
--- /dev/null
+++ b/help/wp-conv/pctotex.html
@@ -0,0 +1,511 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en-us"><head><title>Converters from PC Textprocessors to LaTeX - Overview</title></head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="index.html">Converters between LaTeX and
+PC Textprocessors homepage</a></p>
+<h1>Converters from PC Textprocessors to LaTeX - Overview</h1>
+<p><strong>Switch conversion direction: <a href="textopc.html">From LaTeX to
+PC</a></strong></p>
+<p>Author: Wilfried Hennings (texconvfaq "at" gmx.de), last
+update (including subpages): March 3, 2011<br>
+The url of this page is <a href="http://tug.org/utilities/texconv/pctotex.html">
+http://tug.org/utilities/texconv/pctotex.html</a> </p>
+<p>I maintain these pages because I need converters between LaTeX
+and PC Textprocessors for my work and I want to share the information
+with others who need it. Because I maintain them in my spare time (uh,
+what is spare time?), I can not answer individual questions.</p>
+<p><strong>This list is as good or as bad as its support,
+and I need YOUR support to update and supplement this list.</strong>
+Please supplement if you know more and/or better ones. There are some
+more converters on the CTAN sites, but the following seem to be most
+promising for conversion to and from the
+current versions of wordprocessors. </p>
+<p>Neither correctness nor completeness is guaranteed. <br>
+All opinions mentioned (if any) are my own, not my employer's. Please
+send corrections, enhancements and supplements (auch in deutscher
+Sprache) to the following address: <br>
+texconvfaq "at" gmx.de</p>
+<p>Note that this FAQ list contains information about converters
+<strong>ONLY</strong> between PC word processors and LaTeX.
+Converters to and from <strong>other formats may have own FAQ
+lists</strong> &#8211; e.g. see the link for converters to
+and from
+HTML.</p>
+<hr>
+<p>For the impatient, here is a <a href="pc2txtbl.html">table
+with overview of features</a> of the most recent converters.</p>
+<hr>
+<h2>General Remarks</h2>
+<p>Before looking for a converter, stop and think about a
+principal question: </p>
+<h3>What do you want to be converted in which way?</h3>
+<p>Do you want to convert the <strong>document structure</strong>,
+i.e. a heading should remain a heading, a list should remain a list
+etc., no matter how it will look like in the target format?<br>
+Or do you want to convert the <strong>appearance</strong>,
+i.e. how it looks like, no matter how it is represented in the target
+format?<br>
+Or do you want a mixture of both?<br>
+For using SGML as an intermediate format, you would have to specify the
+translation rules yourself (as far as I understood). This makes sense,
+and explains why different people have very different opinions about
+which converter best fits their needs: They simply have different
+demands and expectations on what should be converted and how. <br>
+So, not only practically there is no converter which is good for
+everyone and every purpose, but this is even principally impossible
+because there are no well-defined requirements which a converter should
+meet. </p>
+<p>So keep this in mind when looking through the following list
+of converters, try yourself and decide what you need.</p>
+<h3>Principal problems of wordprocessor to LaTeX conversion</h3>
+<p>One advantage of LaTeX is that it forces to structure a
+document, whereas wordprocessors like Word/WordPerfect allow
+unstructured documents. It is hardly possible to automatically
+structure a document where there was no structure before. </p>
+<p>However it is nevertheless possible to write a structured
+document with a wordprocessor by consistently using styles. Therefore,
+wordprocessor documents using styles can be converted to a LaTeX with
+an equivalent (but not necessarily identical) structure. </p>
+<h3>There are several ways to convert</h3>
+<ul>
+<li>use a Wordprocessor macro: search for formats, special
+characters and equations, tag them with LaTeX markup, then save as
+plain text <br>
+<br>
+</li>
+<li>use a Wordprocessor export filter<br>
+<br>
+</li>
+<li>use an external converter: </li>
+</ul>
+<ol>
+<li>Word binary format -&gt; LaTeX</li>
+<li>RTF (Word ASCII format, use Word's own RTF export)
+-&gt; LaTeX</li>
+<li>Open Office format -&gt; LaTeX</li>
+<li>WordPerfect 5.1 format -&gt; LaTeX</li>
+<li>HTML (use Wordprocessor's built-in or add-on html
+converter) -&gt; LaTeX </li>
+<li>maybe other external format(s)</li>
+</ol>
+<p>The converters being most complete, undergoing further
+development and
+having support are:</p>
+<p><a href="#rtf2latex2e">rtf2latex2e</a> -
+free standalone rtf to LaTeX converter for Mac, PC, and Unix</p>
+<p><a href="#word2tex">word2tex</a> -
+shareware, MS Word export filter for PC</p>
+<p><a href="#GrindEQ">GrindEQ</a> - shareware,
+MS Word export filter for PC </p>
+<p><a href="#wordtolatex">word-to-latex</a> - shareware,
+MS Word export filter for PC </p>
+<p><a href="#writer2latex">Writer2LaTeX</a> -
+free export filter and standalone Open Office converter</p>
+<p><a href="#wp2latex">WP2LaTeX</a> - free
+standalone Word Perfect converter for PC</p>
+<hr>
+<h2>Using a Word macro</h2>
+<h3>Free:</h3>
+<p><b>winw2ltx</b>: A set
+of macros, originally for WinWord 2, adapted to WinWord 6 and
+7 (95) and now (Aug. 2008) to WinWord 97 (and up)
+<br>
+See <a href="winw2ltx.html">more detailed page</a>
+</p>
+<h3>Commercial:</h3>
+<p><b>MathType</b>: PC equation editor with export to
+LaTeX. <br>
+See <a href="mathtype.html">more detailed page</a>.<br>
+<a href="http://www.mathtype.com/">
+MathType home page (external link)</a> </p>
+<hr>
+<h2>Using a Word export filter</h2>
+<h3>Shareware:<br>
+</h3>
+<p><a name="wordtolatex"></a><b>Word-To-LaTeX</b>:
+This converter can convert documents
+from Word2002(XP) or later to LaTeX.<br>The
+conversion can be run from the command-line (can be used for
+batch-processing), through the graphic interface, or directly from Word.<br>Besides Word2002(XP) or later it also needs MS .NET
+Framework <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&amp;displaylang=en">2.0
+(external link)</a><br>
+Converts:
+</p>
+<ul>
+<li>Equation Editor objects and MathType objects, if one has
+MathType installed.</li>
+<li>Images and embedded objects like Excel graphs to
+Encapsulated PostScript (EPS) format or to bitmaps (PNG format).</li>
+<li>Paragraphs marked as headings using the Word built-in
+styles to sections (the default mappings can be changed).</li>
+<li>Ordered and unordered lists (even nested), and complex
+tables with merged rows and columns.</li>
+<li>Footnotes and endnotes. Bibliography
+items can be optionally created from endnotes.</li>
+<li>Table and figure titles, index, table of contents,
+multicolumn sections, hyperlinks.</li>
+<li>Special and national characters (e.g. Greek, Russian or
+Hebrew), even those from the Symbol font. (Remark: To make LaTeX
+recognize some converted special characters, one should add the line
+"\usepackage[T1]{fontenc}" to the preamble. If the text is not in
+English, LaTeX also needs the line "\usepackage[language]{babel}".)</li>
+</ul>
+<p>For a complete list of features, visit its
+<a href="http://www.wordtolatex.com/">homepage
+(external link)</a>.</p>
+<p>The package can be downloaded from the <a href="http://www.wordtolatex.com/">homepage
+(external link)</a>. Limited to 15 days of trial.</p>
+
+<p><a name="word2tex"></a><b>Word2TeX</b>:
+This converter can save documents
+from&nbsp;Word95 or later as LaTeX, <b>including equation
+editor (!)</b>
+objects, MathType objects and Word 2007-2010 equations. <br>
+Current version: 5.01, Feb. 2011.<br>Converts:</p>
+<ul>
+<li>all versions of Equation Editor and Design Science
+MathType embedded objects (*)</li>
+<li>figures (to EPS or PDF)(*)</li>
+<li>tables (even very complicated) (*)</li>
+<li>footnotes </li>
+<li>endnotes (to bibliography)</li>
+<li>index</li>
+<li>cross-references</li>
+<li>paragraph styles (heading1 to heading4, custom styles) --
+customizable</li>
+<li>character attributes (bold, italic etc.) -- customizable</li>
+<li>Greek-charset</li>
+<li>multibyte character encodings (Unicode)</li>
+<li>and many more (see <a href="http://www.word2tex.com/">homepage
+(external link)</a>)</li>
+</ul>
+<p>(*) restrictions will apply in unregistered Word2TeX: only 7
+first equations will be translated, only 1 first table will be
+translated, only 1 first figure will be translated. Limited to 30 days
+of trial.</p>
+<p>For a complete list of features, visit its
+<a href="http://www.word2tex.com/">homepage (external link)</a>.</p>
+<p><a name="GrindEQ"></a><b>GrindEQ
+Word-to-Latex</b>: Shareware, 99EUR (49EUR academic)<br>
+converts Microsoft Word documents to LaTeX, AMS-LaTeX, Plain TeX, or
+AMS-TeX format. <br>
+Microsoft Equation 2007, Microsoft Equation 3.x, and
+MathType are supported. <br>
+Works with Microsoft Word 97/2000/XP/2003/2007
+and Microsoft Windows 98/Me/NT/2000/XP/2003/x64/Vista. <br>
+Evaluation version is restricted to 10 launches.<br>
+See <a href="http://www.grindeq.com/">homepage (external
+link)</a>
+</p>
+<h2>Converting from Word binary format</h2>
+<p>This means the .doc format which is used by Word 95, 97, 2000,
+XP and 2003 and in which also Word 2007 can save its documents if
+you tell it to do so. The new XML format which is by default used by
+Word 2007 is (afaik) not yet supported.</p>
+<h3>Free:</h3>
+<p>The free (LGPL) office suite <b>Open
+Office</b> can import Word format and export to
+LaTeX format.
+Open Office runs on MacOSX, several Linux/Unix's and also
+Windows95/98/NT/XP/2003 and Vista and stores documents as XML.<br>
+My (and other's) experiences with OO&nbsp;3.1 are quite good, given
+the following prerequisites. <br>
+- You need to install the <a href="pctotex.html#writer2latex">Writer2LaTeX</a>
+extension.<br>
+- You need to check
+"Extras-Options-Load/Save-Microsoft Office-Load-MathType to OpenOffice
+Math".<br>
+See <a href="http://www.openoffice.org/">
+homepage (external link)</a> </p>
+<p><b>LAOLA</b> can
+read Word6/Word7(=95) documents under Unix and extract the text.<br>
+See <a href="laola.html">more detailed page</a><br>
+<a href="http://user.cs.tu-berlin.de/%7Eschwartz/pmh/">LAOLA
+homepage (external link)</a></p>
+<p><b>word2x</b>: Converts
+Word6/Word7(=95) documents to LaTeX or plain text. <br>
+See <a href="word2x.html">more detailed page</a><br>
+<a href="http://sourceforge.net/projects/word2x/">word2x
+homepage (external link)</a></p>
+<p><b>antiword</b>: A free MS Word reader for Linux,
+BeOS and RISC OS. It converts the binary files from Word 6, 7, 97 and
+2000 to text and Postscript.
+<br>
+See <a href="http://www.winfield.demon.nl/index.html">antiword
+homepage (external link)</a>. <br>
+A user's comment: "It is still a
+bit incomplete, but I found it to be rather useful. Moreover, it is
+available for a wider-than-usual range of platforms."</p>
+<p><b>wvWare</b> is a library that can read the
+Word6/Word7(=95), Word8(=97) and Word9(=2000) binary file format. It
+works under most Unix systems.<br>
+See <a href="http://wvware.sourceforge.net/">wvWare
+homepage (external link)</a>.<br>
+The wvWare library is used as import library in the wordprocessor
+AbiWord (see below). <br>
+Its predecessor MSWordView could only read Word8(=97) and convert word
+into html, which can then be read with a browser. </p>
+<p>For the wvware library an API "wsW2LTX" and a GUI shell
+"wsW2LTXGUI" (for MS Windows) is available at
+<a href="http://www.winshell.de/modules/w2ltx_download/">http://www.winshell.de/modules/w2ltx_download/
+(external link)</a>
+</p>
+<p>The free (GPL) wordprocessor <b>AbiWord</b>
+can import Word format (by using the aforementioned wvWare) and export
+to LaTeX format. AbiWord runs on BeOS, several Unix's and also
+Windows95/98/NT and stores documents as XML.<br>
+<a href="http://www.abisource.com/">AbiWord homepage
+(external link)</a>
+</p>
+<hr>
+<h2>Converting from RTF</h2>
+<p>To use an RTF converter, the wordprocessor document must first
+be "saved as" Rich Text Format. However each new version of MS Word
+came with a new level of the RTF language. Most of the available
+converters cannot understand the current RTF version</p>
+<h3>Free:</h3>
+<p><a name="rtf2latex2e"></a><b>rtf2latex2e</b> 2-0-1 version (2011). <br>
+download from <a href="http://sourceforge.net/projects/rtf2latex2e/">
+sourceforge (external link)</a>.<br>
+See <a href="rtf2latex2e.html">more detailed page</a><br>
+If you are interested in the history of this converter, see <a href="rtf2latex.html">this page.</a></p>
+<p><b>RTF2LaTeX</b>, a patch for WP2LaTeX that allows
+it to convert also RTF documents. Experimental Release 0.4 (works, but
+it knows only a small group of commands). See its
+<a href="http://www.penguin.cz/%7Efojtik/wp2latex/rtf2latex.htm">homepage
+(external link)</a>.</p>
+<p><b>GNU unRTF</b> is a command-line program written
+in C which
+converts documents in Rich Text Format (.rtf) to several formats
+including LaTeX. <br>
+See its <a href="http://www.gnu.org/software/unrtf/unrtf.html">
+homepage (external link)</a>.
+The latest version 0.21.10 (Jan.17, 2010) is only available as source
+code. <br>
+A precompiled binary for Windows, however an older version (0.19.3,
+Feb.12, 2005), is
+available from <a href="http://gnuwin32.sourceforge.net/packages/unrtf.htm">sourceforge
+(external link)</a>.</p>
+<p>The free (GPL) wordprocessor <b>AbiWord</b>
+can import rtf and also MS Word doc format and export to LaTeX format.
+AbiWord runs on BeOS,
+several Unix's and also Windows95b or higher (up to XP) and stores
+documents as XML.<br>
+<a href="http://www.abisource.com/">AbiWord homepage
+(external link)</a></p>
+<h3>Commercial:</h3>
+<p><b>Scientific Word</b>: Win95/98/2000/NT4 based
+TeX/LaTeX system with graphical editor and rtf import capability
+including MS's equation editor equations. The rtf import converter is
+basically the same as rtf2latex2e. <br>
+See <a href="sciword.html">more detailed page</a><br>
+<a href="http://www.mackichan.com/">Scientific Word home
+page (external link)</a></p>
+<hr>
+<h2>Converting from Open Office format</h2>
+<p><a name="writer2latex"></a><b>Writer2LaTeX</b>
+is a commandline utility written in java. It converts
+OpenOffice.org/StarOffice Writer documents into LaTeX2e.</p>
+<p>If you have OpenOffice or StarOffice installed, get the Writer2LaTeX extension from
+<a href="http://extensions.services.openoffice.org/project/writer2latex">
+http://extensions.services.openoffice.org/project/writer2latex</a>.</p>
+<p>If you need Writer2LaTeX as a standalone converter, see its <a href="http://writer2latex.sourceforge.net/">
+homepage (external link)</a>
+<br>
+<br>
+Supported operating systems: All on which Java is supported.
+Requires java runtime environment (JRE), version 1.4 or higher, to run
+Writer2LaTeX. JRE is included in OpenOffice, and also can
+be downloaded from <a href="http://java.sun.com/javase/downloads/index.jsp">java.sun.com
+(external link)</a> (scroll down to "Java Runtime
+Environment (JRE)").</p>
+<hr>
+<h2>Converting from WordPerfect format</h2>
+<h3>Free:</h3>
+<p><a name="wp2latex"></a><b>WP2LaTeX</b>
+converts
+WordPerfect 1.x / 2.x / 3.x / 4.x / 5.x / 6-8.x, including
+equations, to LaTeX.<br>
+See <a href="wp2latex.html">more detailed page</a><br>
+<a href="http://www.penguin.cz/%7Efojtik/wp2latex/wp2latex.htm">homepage
+(external link)</a></p>
+<p><a href="texperf.html">TeXPerfect</a>:
+WordPerfect 5.1 for DOS -&gt; LaTeX Translater</p>
+<h3>Commercial:</h3>
+<p><a name="pubcomp"></a><b>Publishing
+Companion</b>:
+converts Word/WordPerfect, including equations, to LaTeX. Comes with
+own equation editor. <br>
+See <a href="pubcomp.html">more
+detailed page</a><br>
+<a href="http://www.ktalk.com/">KTALK's
+home page (external link)</a> </p>
+<hr>
+<h2>HTML as intermediate format</h2>
+<h3>Wordprocessor to HTML</h3>
+<p>There are free HTML converters for Word 6 and 7(95) for
+Windows available from Microsoft: <br>
+Download... <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/WORDIA.EXE">IA
+for Word 6 (external link)</a> /
+<a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/WDIA204Z.EXE">IA
+for Word 7 (95) (external link)</a> / <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/MACIA20Z.HQX">IA
+for Word for Mac (external link)</a> <br>
+Word&nbsp;97 contains an html converter by default, but in contrary
+to
+the previous versions it only recognizes heading styles if they are
+first converted into the corresponding html styles. Also, it sometimes
+inserts unnecessary tags. <br>
+Word&nbsp;2000 contains the html converter by default, but you
+should not use this default: It actually creates sort of XML with many
+Word-specific elements. Instead, for saving as "clean" html, download
+and install the <a href="http://office.microsoft.com/downloads/2000/Msohtmf2.aspx">add-on
+converter from Microsoft (external link)</a>.<br>
+For Word&nbsp;XP (2002) and above the "clean" html export
+can be installed with Word's setup. It is recommended to "save
+as" "html filtered". However this isn't "clean" enough, you should
+manually edit the saved html before feeding it to the html-to-LaTeX
+converter. </p>
+<p>WordPerfect 7 and up have an integrated InternetPublisher. <br>
+For WordPerfect 6.1 for Windows, the InternetPublisher is available
+separately:
+<br>
+Download...
+<a href="ftp://ftp.corel.com/pub/WordPerfect/wpwin/61/internetpublisher.exe">InternetPublisher
+for WPWin 6.1 (external link)</a> </p>
+<p>There also is a tool for Unix which is intended to convert
+word6, word7(95) and word8(97) binary files to html. See
+<a href="http://www.su.shuttle.de/turbo/michael/projekte/software/word2html.c.gz">http://www.su.shuttle.de/turbo/michael/projekte/software/word2html.c.gz
+(external link)</a>
+</p>
+<p>Also see www.w3.org for a
+<a href="http://www.w3.org/pub/WWW/Tools/Word_proc_filters.html">list
+of converters between word processors and HTML (external link)</a>
+- now outdated (last change March 1999).
+</p>
+<h3>HTML to LaTeX</h3>
+<p>Because HTML is a structured format, the conversion between
+HTML and LaTeX is rather straightforward. However there remain the
+limitations of HTML compared to LaTeX, i.e. there are many elements in
+LaTeX which can not (yet?) be represented in HTML. </p>
+<p>There are several HTML-to-LaTeX converters available. Without
+giving recommendations:</p>
+<p>Frans Faase's <b>html2tex</b> (C source)
+<br>
+See <a href="http://home.wxs.nl/%7Efaase009/html2tex.html">
+homepage (external link)</a>
+</p>
+<p>Peter Thatcher's <b>html2latex</b> (Perl script)<br>
+See <a href="http://html2latex.sourceforge.net/">
+homepage at sourceforge.net (external link)</a>
+</p>
+<p>Jeffrey Schaefer's
+<b>html2latex</b> (Perl script)<br>
+See <a href="http://www.geom.umn.edu/software/html2latex/welcome.html">
+homepage at www.geom.umn.edu (external link)</a>
+</p>
+<p>Michal Kebrt's <b>htmltolatex</b> (Java Program)<br>
+See <a href="http://htmltolatex.sourceforge.net/">homepage
+at sourceforge.net (external link)</a></p>
+<p>Some converters are available from
+<a href="http://www.tex.ac.uk/tex-archive/CTAN.sites">CTAN
+(external link)</a>
+("Comprehensive TeX Archive Network"), e.g. in
+.../support/html2latex. However, what you can find in CTAN under
+.../support/html2latex/ is Nathan Torkington's converter of 1993 --
+rather outdated.<br>
+(The ... stands for a host specific base directory, which often is
+either "/pub/tex" or "/tex-archive") </p>
+<hr>
+<h2>Other intermediate formats</h2>
+<p>There are ways to use <b>SGML</b> as intermediate
+format, and others have used it successfully. Having had a quick look
+at it, I found it rather complicated, especially it seems that you have
+to define the translation rules yourself. So I did not put more effort
+in trying to use it. If anyone can give me a ready-to-use cookbook
+solution, I will include it here. </p>
+<p>Another intermediate format is <b>TeXML</b>. It
+was designed to make conversion to (La)TeX as easy as possible,
+especially XSLT-conversion from XML format. A converter from TeXML to
+(La)TeX is available, see
+<a href="http://getfo.sourceforge.net/texml/">http://getfo.sourceforge.net/texml/
+(external link)</a>.
+However I yet don't know of any converter from a texprocessor format to
+TeXML. </p>
+<hr>
+<h2>Converting from PageMaker</h2>
+<p>Pmtolatex, a perl script to convert PageMaker files to LaTeX.
+See
+<a href="http://www.lightandmatter.com/pmtolatex/pmtolatex.html">homepage
+(external link)</a>.
+</p>
+<hr>
+<h2>Converting from FrameMaker</h2>
+<p><a href="http://www.cs.stir.ac.uk/%7Ekjt/software/framemaker/">FrameMaker
+Utilities (external link)</a>: Contains converters for both
+directions
+(LaTeX &lt;-&gt; FrameMaker) as well as templates which make
+conversion from Framemaker to LaTeX more easy</p>
+<hr>
+<h2>Converting from NotaBene</h2>
+<p>NB4LATEX converts files from NotaBene4 for DOS (which is an
+old
+version for DOS) to LaTeX2e format. You find it on <a href="index.html#ctan">CTAN</a>
+in directory .../systems/msdos/nb4latex
+</p>
+<hr>
+<h2>Converting from ChiWriter</h2>
+<p>There are two converters on CTAN, but I don't know how good
+they are and whether they still work (they are DOS programs from 1993
+and 1994). You find them on <a href="index.html#ctan">CTAN</a>
+in directory .../support/chi2ltx/
+and in directory .../support/chi2tex/</p>
+<hr>
+<h2>Converting from Excel</h2>
+<p>There are two possibilities to do that:</p>
+<p>1. <span style="font-weight: bold;">Excel2LaTeX</span>:
+Excel-macro to convert Excel to LaTeX.
+The generated LaTeX code uses the tabular environment.<br>
+On CTAN in .../support/excel2latex/, i.e. <a href="http://www.dante.de/CTAN//help/Catalogue/entries/excel2latex.html">here</a><br>
+</p>
+<p>&lt;citation from
+<a href="http://www.latex-community.org/forum/viewtopic.php?f=5&amp;p=28364">http://www.latex-community.org/forum/viewtopic.php?f=5&amp;p=28364</a>&gt;<br>
+"when I use Excel2Latex, it&nbsp;says "Can't find project or
+library" after pressing on the conversion button. ..."<br>
+"This problem may be caused by a broken reference to REFEDIT.DLL.
+Excel2LaTeX.xla contains a reference to folder OFFICE12 (Office 2007).
+If you use the macro with Office 2003 (OFFICE11) you must fix the
+reference. REFEDIT.DLL is in c:\Program Files\Microsoft
+Office\OFFICE11\. In Excel go to Tools&gt;Macros&gt;Visual
+Basic Editor, select VBAProject (Excel2LaTeX.xla) in Project Explorer,
+then go to Tools&gt;References and uncheck MISSING:Ref Edit
+Control,
+click Browse and Open REFEDIT.DLL, then use the priority button to
+raise the new Ref Edit Control entry to where the MISSING entry was
+(click the up arrow button once and then hold Space to raise)."
+&lt;/citation
+end&gt;. </p>
+<p>2. Importing Excel file into <a href="http://www.gnome.org/projects/gnumeric/">Gnumeric
+(external link)</a>,
+then exporting to LaTeX. But I have no further info on the resulting
+LaTeX markup.</p>
+<h2>Converting from OpenOffice spreadsheet</h2>
+<p>OO macro to convert from OO to LaTeX:
+<a href="http://calc2latex.sourceforge.net/">http://calc2latex.sourceforge.net/
+(external link)</a>.
+</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 ... 2011 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/pubcomp.html b/help/wp-conv/pubcomp.html
new file mode 100644
index 0000000000..30afbe9cd7
--- /dev/null
+++ b/help/wp-conv/pubcomp.html
@@ -0,0 +1,108 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>Publishing Companion</title>
+
+</head>
+
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC Textprocessors to LaTeX -
+Overview</a></p>
+<h1>Publishing Companion</h1>
+<p>last update: July 24, 2001</p>
+<p>Note: I tried an older version of this product, but it turned
+out not to be
+useful for me. Reasons: <a href="ktbugs.html">see here</a>.
+Maybe the current
+version does much better, but it's too expensive for me.</p>
+<p>citation from
+<a href="http://www.ktalk.com/pubcomp.html">http://www.ktalk.com/pubcomp.html
+(external link)</a>
+- citation begin&gt;&gt;</p>
+<table align="center" border="3" bordercolor="#000080" cellpadding="5">
+<tbody>
+<tr>
+<th colspan="2" bgcolor="#d9c8a6"><font color="Maroon">Publishing Companion
+translates the following to plain TeX or LaTeX:</font></th>
+</tr>
+<tr>
+<td>Automatic Indexes</td>
+<td>Newspaper-style Columns</td>
+</tr>
+<tr>
+<td>Boxes</td>
+<td>Non-break Hyphens &amp; Spaces</td>
+</tr>
+<tr>
+<td>Centering</td>
+<td>Outlines</td>
+</tr>
+<tr>
+<td>Endnotes</td>
+<td>Page Numbering</td>
+</tr>
+<tr>
+<td>Flush Right</td>
+<td>Paragraphs</td>
+</tr>
+<tr>
+<td>Footnotes</td>
+<td>Parallel Columns</td>
+</tr>
+<tr>
+<td>Foreign Characters</td>
+<td>Point Sizes</td>
+</tr>
+<tr>
+<td>Full Fonts</td>
+<td>Redlining</td>
+</tr>
+<tr>
+<td>Horizontal Lines</td>
+<td>Running Headers &amp; Footers</td>
+</tr>
+<tr>
+<td>Indents</td>
+<td>Soft Hyphens</td>
+</tr>
+<tr>
+<td>Justification</td>
+<td>Strikeout</td>
+</tr>
+<tr>
+<td>Mail Merge</td>
+<td>Superscripts &amp; Subscripts</td>
+</tr>
+<tr>
+<td>MathEdit Math Equations</td>
+<td>Table of Contents</td>
+</tr>
+<tr>
+<td>MS Word 6.0 Math Equations</td>
+<td>Type Styles (bold, italic)</td>
+</tr>
+<tr>
+<td>WordPerfect Math Equations</td>
+<td>Widows &amp; Orphans on/off</td>
+</tr>
+</tbody>
+</table>
+<p> &lt;&lt;citation end</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+ary and mirror) hosts is available at
diff --git a/help/wp-conv/readme.txt b/help/wp-conv/readme.txt
new file mode 100644
index 0000000000..95f0fbaaf0
--- /dev/null
+++ b/help/wp-conv/readme.txt
@@ -0,0 +1,12 @@
+The html files in this directory (=folder) or zipfile
+contain my FAQ list of
+converters between LaTeX and PC Textprocessors in HTML format.
+
+Because all html links between these pages are relative links,
+the files can be put into any directory of your choice ("base dir");
+but be sure to keep the directory structure,
+i.e. there should be a subdir "bin" in the base dir.
+
+Then start with the page "index.html".
+
+
diff --git a/help/wp-conv/rtf2latex.html b/help/wp-conv/rtf2latex.html
new file mode 100644
index 0000000000..a402aa49c7
--- /dev/null
+++ b/help/wp-conv/rtf2latex.html
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>rtf2TeX and rtf2LaTeX converters</title></head>
+<body>
+<p> Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX - Overview</a></p>
+<h1>rtf2TeX and rtf2LaTeX</h1>
+<p>last update: Feb 14, 2011</p>
+<p>The information provided here is for those who are interested
+in the history.
+</p>
+<p>First, Paul Dubois &lt;dubois "at"
+primate.wisc.edu&gt; wrote an RTF reader and
+converter to plain text or troff. The version is dated April 1991. <br>
+See <a href="http://www.snake.net/software/RTF/">RTF
+utilities homepage (external link)</a>.
+</p>
+<p>a) Based on this reader, Robert Lupton &lt;rhl "at"
+astro.princeton.edu&gt; wrote
+the <strong>rtf2TeX</strong> converter. Last revision
+date: May 1992 </p>
+<p>He comments on this as follows (README-file): <br>
+citation begin&gt;&gt; <br>
+This is a first attempt at an RTF to TeX converter. The parts that
+handle fonts and such like seem to work pretty well, although they
+could be improved, but the table handling is a problem. I had a good
+deal of trouble trying to figure out what particular rtf control codes
+were supposed to do; this makes it hard
+to convert them into TeX. I have tried to produce good TeX, but this is
+not easy due to the sloppy way that many RTF writers generate redundant
+font and other changes. <br>
+Many things are not handled at all, more due to my lacking motivation
+than to their intrinsic difficulty. For example, I don't support double
+columns, but it would be easy enough to do (I'd generate a control
+sequence to do it, and add the TeX code required to the TeX_defs file.
+I even have the TeX somewhere...).
+<br>
+&lt;&lt;citation end</p>
+<p>So far the beginning of the README file. Later he commented: <br>
+citation begin&gt;&gt; <br>
+Most (all?) RTF is hopelessly unstructured <br>
+(the equivalent of \bf \it Hello \rm World \bf He \it \rm said. ) <br>
+and the code that I wrote tries valiantly to convert this to something
+sensible, in this case <br>
+{\it Hello\/} World {\bf He} said. <br>
+It is this attempt to make the output TeX usable that makes the code
+complicated... <br>
+I did not try to convert equations or tables as I could find no
+adaquate description of either; I don't think that it would be very
+hard. <br>
+&lt;&lt;citation end</p>
+<p>Available on CTAN sites, dir .../support/rtf2tex </p>
+<p>b) Based on these two, Erwin Wechtl wrote the rtf2LaTeX
+converter. <br>
+Last revision date: Aug. 1993 </p>
+<p>He comments on this as follows (README-file): <br>
+citation begin&gt;&gt; <br>
+<strong>rtf2LaTeX</strong> is a filter built on Paul
+DuBois' RTF reader that converts RTF (Microsoft's Rich Text Format)
+into LaTeX. rtf2LaTeX expends a good deal of effort in an attempt to
+make the resulting LaTeX maintainable and modifiable. <br>
+&lt;&lt;citation end</p>
+<p>At the moment converts text elements, but no formulas and no
+graphics. <br>
+C-source and an executable for MSDOS are available on CTAN sites,
+dir .../support/rtf2latex </p>
+<p>c) In 1999, Ujwal Sathyam took Paul Dubois' rtf reader source
+and adapted it to handle later versions of rtf.
+To distinguish this branch from the others, it was named
+<strong>rtf2latex2e</strong>.<br>
+In 2000, Steve Swanson from Mackichan Software
+(http://www.mackichan.com, makers of Scientific Word and Workplace)
+added the capability to convert Equation Editor and MathType objects.<br>
+In the further course of development, many more features were added,
+e.g. the capability to convert several types of embedded graphics.<br>
+Release 1.0fc2 was finished in May 2001 and remained as such until 2010.</p>
+<p>In Dec. 2010, Scott Prahl resumed development on rtf2latex2e,
+resulting in a first 2.0 release in Jan 2011.</p>
+<p>Available on CTAN sites, dir .../support/rtf2latex2e </p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2007, 2008, 2009, 2011 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
diff --git a/help/wp-conv/rtf2latex2e.html b/help/wp-conv/rtf2latex2e.html
new file mode 100644
index 0000000000..fb76d423fd
--- /dev/null
+++ b/help/wp-conv/rtf2latex2e.html
@@ -0,0 +1,52 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>rtf2latex2e</title>
+
+</head>
+
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>rtf2latex2e</h1>
+<p>rtf2latex2e is a utility to convert RTF files from popular
+word processors
+to the LaTeX2e format.
+<br>
+rtf2latex2e uses the <a href="http://www.snake.net/software/RTF/">RTF
+reader (external link)</a> package by Paul DuBois to parse the
+RTF code and generates an
+appropriate <a href="http://www.tug.org/">LaTeX (external
+link)</a> file. </p>
+<p>rtf2latex2e was developed on under Mac OS X but should compile
+under any Unix variant.<br>
+Windows users should compile under something like MinGW or use
+the precompiled binary in the ...-Win package. <br>
+rtf2latex2e is distributed along with the source code
+under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
+General Public
+License (external link)</a>. </p>
+<p>The main features of rtf2latex2e are:</p>
+<ul>
+</ul>
+<p>&nbsp;1. detects text style: bold, italic, color, big,
+small,...<br>
+&nbsp;2. reads embedded figures: PICT, EMF, GIF, TIFF, WMF, PNG,
+JPEG<br>
+&nbsp;3. reads tables: simple to semi-complex<br>
+&nbsp;4. equations: converts embedded MathType equations<br>
+&nbsp;5. symbols: converts most greek and math symbols<br>
+&nbsp;6. reads footnotes (not in tables yet)<br>
+&nbsp;7. translates hyperlinks using the hyperref package<br>
+&nbsp;8. converted latex file uses utf8<br>
+&nbsp;9. supports codepages 1250, 1251, 1252, 1254, mac, NeXt<br>
+10. converts RTFD (rtf directories)<br>
+11. extended preferences<br>
+12. internal document page references<br>
+13. save all converted files in a separate directory<br>
+<br>
+The latest version of rtf2latex2e can be found
+<a href="http://sourceforge.net/projects/rtf2latex2e/">here (external link)</a>.</p>
+<p>(c) Ujwal Sathyam 1999, Scott Prahl 2011 </p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/sciword.html b/help/wp-conv/sciword.html
new file mode 100644
index 0000000000..522664bd2b
--- /dev/null
+++ b/help/wp-conv/sciword.html
@@ -0,0 +1,129 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>Scientific Word and Scientific WorkPlace</title>
+
+</head>
+
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>Scientific Word and Scientific WorkPlace</h1>
+<p>last update: July 24, 2001</p>
+<p>citation begin&gt;&gt;</p>
+<p><a href="http://www.mackichan.com/">MacKichan
+Software (external link)</a> publishes
+Scientific Word and Scientific WorkPlace. Included with these products
+is a
+conversion program that will input RTF and output LaTeX. This
+conversion will
+correctly convert Microsoft Word Equation Editor or MathType equations
+in the
+RTF file to LaTeX. The conversion program is not available separately,
+but it
+is based on the free <a href="rtf2latex2e.html">rtf2latex2e</a>.
+</p>
+<p>&lt;&lt;citation end</p>
+<p>There is a "light" (and cheaper) version available called
+<a href="http://www.scinotebook.com/">Scientific Notebook (external link)</a>,
+which is also
+capable of importing RTF and exporting (sort of) LaTeX. They also
+provide a
+free 30 day evaluation version.</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+mpatible with win95, win98, winME, nt4.0, win2000, winXP) and
+Macintosh are available from <a href="http://sourceforge.net/projects/latex2rtf/">
+http://sourceforge.net/projects/latex2rtf/ (external link)</a>. </p>
+<p>A stable but not always the most recent release is also
+available from
+<a href="index.html#ctan">CTAN</a>,
+directory .../support/latex2rtf <br>
+(the ... stands for a host specific base directory, which often is
+either "/pub/tex" or "/tex-archive"). </p>
+<p>We still seek for people joining us as maintainer or
+developer. If you are interested, contact me (texconvfaq "at" gmx.de).</p>
+<h3> Program Copyright:</h3>
+<p>This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License as
+published by the
+Free Software Foundation; either version 2 of the License, or (at your
+option) any later version. <br>
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANT-ABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the <a href="GPL.txt">GNU
+General Public License</a>
+for more details. </p>
+<p>Note that this Copyright note only applies to the changes made
+to get the actual version. The older versions have their own Copyright
+policy
+stated in their distribution. </p>
+<h3>History:</h3>
+<p> In 1994 the first Version of LaTeX2rtf was written by a group
+of students of the Viena University supervised by Ralf Schlatterbeck.
+They took up
+a LaTeX parser and added most of the functionality to the program. In
+1995 work
+continued with a second group of students. The result was LaTeX2rtf
+Version 1.5. </p>
+<p>Unfortunately, two different persons started further
+development of that program, not knowing of each other:</p>
+<ul>
+<li>In 1997, Daniel Taupin started updating this converter. He
+added e.g. the feature to convert equations to bitmaps by invoking the
+TeX engine. However this required the emTeX distribution (for DOS)
+which is no longer supported. </li>
+<li> In 1998, Georg Lehner found the reference to the original
+LaTeX2rtf on this webpage and added some functionality. His work
+resulted in version 1.8aa. Unfortunately he did not know about Daniel's
+developments.</li>
+</ul>
+<p>In 2001, Scott Prahl started to make some significant
+enhancements, also including many of Daniel's additions. He is still
+working on it. So <b>this page is about Georg's and Scott's
+version</b>. Latest stable
+release is 1.9.19 and includes all of the features of Daniel's version.</p>
+<p>Temporarily I (Wilfried Hennings) feel responsible for
+coordinating the exchange of development information. But <em>we
+are still seeking for a person who can act as coordinator of future
+development, and we also need a person to take over the development.</em>
+Anyone feeling able to do that
+please contact me by email to texconvfaq "at" gmx.de. </p>
+<p>We got a project initiated at sourceforge.net which aids in
+further development. Visit its homepage at <a href="http://latex2rtf.sourceforge.net/">
+http://latex2rtf.sourceforge.net/ (external link)</a> or its
+project page at <a href="http://sourceforge.net/projects/latex2rtf/">
+http://sourceforge.net/projects/latex2rtf/ (external link)</a>. </p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2002, 2005, 2007, 2008 Wilfried
+Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+ <i><b>my </b></i> with personal installation when
diff --git a/help/wp-conv/texperf.html b/help/wp-conv/texperf.html
new file mode 100644
index 0000000000..de8212d671
--- /dev/null
+++ b/help/wp-conv/texperf.html
@@ -0,0 +1,93 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>TeXPerfect</title>
+</head>
+
+<body>
+
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC Textprocessors to LaTeX -
+Overview</a></p>
+
+<h1>TeXPerfect</h1>
+
+<p>last update: July 28, 1998</p>
+
+<p>citation begin&gt;&gt;</p>
+
+<p>From: John Forkosh &lt;forkosh "at" panix.com&gt; <br>
+Subject: New WordPerfect -&gt; LaTeX Translater <br>
+Date: Thu, 22 Aug 1996 09:16:36 -0400 (EDT) <br>
+I recently uploaded my WordPerfect -&gt; LaTeX translater, called TeXPerfect,
+to CTAN. It's available in the support directory under texperf
+(.../support/texperf). <br>
+(The ... stands for a host specific base directory, which often is either
+"/pub/tex" or "/tex-archive") <br>
+Full C source is provided, as are executables for both DOS and Linux. The
+00README file in the directory provides more details. John (forkosh "at" panix.com)
+<br>
+&lt;&lt;citation end</p>
+
+<p>following extracted from the 00README file: </p>
+
+<p>citation begin&gt;&gt;</p>
+
+<p>Conversion functionality </p>
+
+<p>Some of the LaTeX conversions performed by TeXPerfect are: <br>
+Suppose your input contains a greek alpha from the WordPerfect character set 8.
+The output will contain $\alpha$ instead. Most of the other special character
+sets provided by WordPerfect are similarly converted. (This conversion is
+table-driven by the data in wpchrset.h, and can be easily augmented or
+modified.) <br>
+Superscripts, subscripts, bold, italics, etc, are all properly interpreted and
+handled. <br>
+"Hard" returns in WordPerfect <strong>should</strong> generate an
+extra blank line, so that LaTeX will see them as paragraphs. That functionality
+is mostly programmed, but a last-minute difficulty prevented me from completing
+it. Also, no attempt is made to generate section/subsection/etc commands. <br>
+If your running text contains an expression like f(x), TeXPerfect will
+recognize it and surround it with $'s. A variety of other ad hoc
+"rules" are hand-coded into the program to decide when to enter/exit
+math mode. Needless to say, the decision isn't always right. You'll need to
+correct tp's mistakes in Step 2 above. <br>
+Equations written with WordPerfect's equation editor will be reproduced
+"verbatim" by TeXPerfect, surrounded by \[ and \]. The only
+correction applied is that 1 over 2 becomes 1 \over 2, and similarly for
+various other keywords. But no serious attempt to interpret and translate your
+equation is made. Matrices, etc, will require considerable hand-tweaking on
+your part. But at least you'll have what you originally wrote right in front of
+your eyes. <br>
+A little LaTeX preamble, etc, is provided, primarily for "cosmetic"
+purposes. WordPerfect's margin settings, etc, are <strong>not</strong>
+interpreted to construct this preamble. You'll have to modify that information
+yourself. </p>
+
+<p>Warnings </p>
+
+<p>TeXPerfect was written to interpret files formatted by WordPerfect 5.1 for
+DOS. When run against 5.1 files, TeXPerfect is pretty robust. But, for this
+release, I commented out the lines that check the version number. If you're
+using WP/Win, it can prepare output in 5.1 format. I'd recommend you do that
+before using TeXPerfect. <br>
+&lt;&lt;citation end</p>
+
+<hr>
+
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+ <li>it must remain intact and the contents unchanged; if you'd like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting (e.g.
+from HTML to some other presentation format) is granted as long as the contents
+are unchanged. </li>
+ <li>you may NOT ask money for it except a reasonable cost for media and
+distribution</li>
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body>
+</html>
diff --git a/help/wp-conv/texport.html b/help/wp-conv/texport.html
new file mode 100644
index 0000000000..f464df4739
--- /dev/null
+++ b/help/wp-conv/texport.html
@@ -0,0 +1,155 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title></title>
+
+</head>
+
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="textopc.html">Converters from LaTeX to PC
+Textprocessors -
+Overview</a></p>
+<h1>TexPort</h1>
+<p>last update: July 24, 2001</p>
+<p>Note: I tried an older version of this product, but it turned
+out not to be
+useful for me. Reasons: <a href="ktbugs.html">see here</a>.
+Maybe the current
+version does much better, but it's too expensive for me.</p>
+<p>citation from <a href="http://www.ktalk.com/texport.html">
+http://www.ktalk.com/texport.html (external link)</a> - citation
+begin&gt;&gt; </p>
+<p><b>TexPort converts your TeX and LaTeX files to
+WordPerfect or Microsoft
+Word documents. </b></p>
+<table align="center" border="3" bordercolor="#000080" cellpadding="2" cellspacing="2">
+<tbody>
+<tr>
+<td colspan="2" bgcolor="#d9c8a6">
+<p align="center"><b><font color="#800000">TexPort
+converts the following:</font></b></p>
+</td>
+</tr>
+<tr>
+<td>Equations</td>
+<td>Itemize and enumerate</td>
+</tr>
+<tr>
+<td>Greek characters</td>
+<td>Framebox, fbox, makebox and mbox <br>
+commands</td>
+</tr>
+<tr>
+<td>Math/Scientific characters</td>
+<td>Indexes</td>
+</tr>
+<tr>
+<td>Bold and Italic styles</td>
+<td>Simple tables</td>
+</tr>
+<tr>
+<td>Footnotes</td>
+<td>European accent characters</td>
+</tr>
+<tr>
+<td>Verbatim and verb commands</td>
+<td>\def and \newcommand</td>
+</tr>
+<tr>
+<td>Itemize and Bib Item </td>
+<td><a href="http://www.ktalk.com/faq.html">Itemize,
+Bib Item, <br>
+Cite Item.</a> <br>
+Want to know how to convert Itemize, <br>
+Bib Item, Cite Item for TexPort 2.00 E <br>
+<a href="http://www.ktalk.com/faq.html">Click here</a></td>
+</tr>
+</tbody>
+</table>
+<p>&lt;&lt;citation end</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+" gmx.de).</p>
+<h3> Program Copyright:</h3>
+<p>This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License as
+published by the
+Free Software Foundation; either version 2 of the License, or (at your
+option) any later version. <br>
+This program is distributed in the hope that it will be useful, but
+WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANT-ABILITY or
+FITNESS FOR A PARTICULAR PURPOSE. See the <a href="GPL.txt">GNU
+General Public License</a>
+for more details. </p>
+<p>Note that this Copyright note only applies to the changes made
+to get the actual version. The older versions have their own Copyright
+policy
+stated in their distribution. </p>
+<h3>History:</h3>
+<p> In 1994 the first Version of LaTeX2rtf was written by a group
+of students of the Viena University supervised by Ralf Schlatterbeck.
+They took up
+a LaTeX parser and added most of the functionality to the program. In
+1995 work
+continued with a second group of students. The result was LaTeX2rtf
+Version 1.5. </p>
+<p>Unfortunately, two different persons started further
+development of that program, not knowing of each other:</p>
+<ul>
+<li>In 1997, Daniel Taupin started updating this converter. He
+added e.g. the feature to convert equations to bitmaps by invoking the
+TeX engine. However this required the emTeX distribution (for DOS)
+which is no longer supported. </li>
+<li> In 1998, Georg Lehner found the reference to the original
+LaTeX2rtf on this webpage and added some functionality. His work
+resulted in version 1.8aa. Unfortunately he did not know about Daniel's
+developments.</li>
+</ul>
+<p>In 2001, Scott Prahl started to make some significant
+enhancements, also including many of Daniel's additions. He is still
+working on it. So <b>this page is about Georg's and Scott's
+version</b>. Latest stable
+release is 1.9.19 and includes all of the features of Daniel's version.</p>
+<p>Temporarily I (Wilfried Hennings) feel responsible for
+coordinating the exchange of development information. But <em>we
+are still seeking for a person who can act as coordinator of future
+development, and we also need a person to take over the development.</em>
+Anyone feeling able to do that
+please contact me by email to texconvfaq "at" gmx.de. </p>
+<p>We got a project initiated at sourceforge.net which aids in
+further development. Visit its homepage at <a href="http://latex2rtf.sourceforge.net/">
+http://latex2rtf.sourceforge.net/ (external link)</a> or its
+project page at <a href="http://sourceforge.net/projects/latex2rtf/">
+http://sourceforge.net/projects/latex2rtf/ (external link)</a>. </p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2002, 2005, 2007, 2008 Wilfried
+Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
+ <i><b>my </b></i> with personal installation when
diff --git a/help/wp-conv/textopc.html b/help/wp-conv/textopc.html
new file mode 100644
index 0000000000..64741077d3
--- /dev/null
+++ b/help/wp-conv/textopc.html
@@ -0,0 +1,430 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en-us"><head><title>Converters from LaTeX to PC Textprocessors - Overview</title>
+
+<meta name="author" content="Wilfried Hennings">
+<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="index.html">Converters between LaTeX and
+PC Textprocessors homepage</a></p>
+<h1>Converters from LaTeX to PC Textprocessors - Overview</h1>
+<p><strong>Switch conversion direction: <a href="pctotex.html">From PC to LaTeX</a></strong></p>
+<p>Author: Wilfried Hennings (texconvfaq "at" gmx.de), this page
+last updated on June 30, 2011<br>
+The url of this page is <a href="http://tug.org/utilities/texconv/textopc.html">
+http://tug.org/utilities/texconv/textopc.html</a> </p>
+<p>I maintain these pages because I need converters between LaTeX
+and PC Textprocessors for my work and I want to share the information
+with others who need it. Because I maintain them in my spare time (uh,
+what is spare time?), I
+can not answer individual questions.</p>
+<p><strong>This list is as good or as bad as its support,
+and it needs YOUR support to update and supplement this list.</strong>
+Please supplement if you know more and/or better ones. There are some
+more converters on the CTAN sites, but the following seem to be most
+promising for conversion to and from the current versions of
+wordprocessors. </p>
+<p>Neither correctness nor completeness is guaranteed. <br>
+All opinions mentioned (if any) are my own. Please
+send corrections, enhancements and supplements (auch in deutscher
+Sprache) to the following address: <br>
+texconvfaq "at" gmx.de</p>
+<p>Note that this FAQ list contains information about converters
+<strong>ONLY</strong> between LaTeX and PC word processors.
+Converters to and from <strong>other formats may have own FAQ
+lists</strong>
+- e.g. see the link for converters to and from HTML.</p>
+<hr>
+<p>For the impatient, here is a <a href="tx2pctbl.html">table
+with overview of features</a> of the most recent converters.</p>
+<hr>
+<h2>General Remarks</h2>
+<p>Before looking for a converter, stop and think about a
+principal question: </p>
+<h3>What do you want to be converted in which way?</h3>
+<p>Do you want to convert the <strong>document structure</strong>,
+i.e. a heading should remain a heading, a list should remain a list
+etc., no matter how it will look like in the target format?<br>
+Or do you want to convert the <strong>appearance</strong>,
+i.e. how it looks like, no matter how it is represented in the target
+format?<br>
+Or do you want a mixture of both?<br>
+For using SGML as an intermediate format, you would have to specify the
+translation rules yourself (as far as I understood). This makes sense,
+and explains why different people have very different opinions about
+which converter best fits their needs: They simply have different
+demands and expectations on what should be converted and how. <br>
+So, not only practically there is no converter which is good for
+everyone and every purpose, but this is even principally impossible
+because there are no well-defined requirements which a converter should
+meet. </p>
+<p>An additional problem is that TeX/LaTeX can be extended by an
+unlimited number of macros. Unless the converter contains a full-scale
+TeX system, it can at best support the publicly available macro
+commands, not the ones privately written by individual users.
+Practically you can expect that it supports the standard LaTeX commands
+and perhaps a few more widely used packages. The only converter which
+uses a full-scale TeX system is TeX4ht. </p>
+<p>So keep this in mind when looking through the following list
+of converters, try yourself and decide what you need.</p>
+<h3>There are several ways to convert. </h3>
+<p>To illustrate these, let me restrict it to the Microsoft Word
+case:</p>
+<ul>
+<li>directly type or paste LaTeX code into Word <br>
+<br>
+</li>
+<li>use a Word import filter <br>
+<br>
+</li>
+<li>use a Word macro: load LaTeX file as plain text, then
+search for LaTeX markup and replace the markup by formatting, special
+characters and equations. <br>
+<br>
+</li>
+<li>use an external converter: </li>
+</ul>
+<ol>
+<li>LaTeX -&gt; RTF, then use Word's
+own RTF import,</li>
+<li>LaTeX -&gt; HTML, then use Word's internet assistant or
+built-in html converter,</li>
+<li>maybe other external format(s).</li>
+</ol>
+<p>The converters being most complete and currently maintained /
+supported are: </p>
+<p><a href="#tex2word">TeX2Word</a> - a
+shareware LaTeX import filter for MS Word</p>
+<p><a href="#GrindEQ">GrindEQ</a> - a
+shareware LaTeX import filter for MS Word</p>
+<p><a href="#latex2rtf">latex2rtf</a> - a free
+standalone LaTeX -&gt; RTF
+converter for PC, Macintosh and Unix, </p>
+<p><a href="#TeX4ht">TeX4ht</a> - a free LaTeX
+to html or XML converter for PC and Unix produces html which is good
+for loading into Word. TeX4ht relies on other software, it needs at
+least a full TeX system.</p>
+<p>There are also converters to Powerpoint and to FrameMaker (see
+further below).</p>
+<hr>
+<h2>Directly type or paste LaTeX code into Word</h2>
+All of these only allow typing or pasting LaTeX coded <span style="font-style: italic;">equations</span> in Word,
+not LaTeX coded text elements.<br>
+<p><b>"Aurora"</b>
+(formerly named Ribbit) can now convert a LaTeX coded equation (which
+must be placed on the Windows clipboard) to Word. The converter is
+still experimental and as such has a number of limitations, some of
+which will be addressed in future releases. The converter&#8217;s
+output will generally need some manual touching up to achieve the level
+of fidelity
+on a par with the original document.<br>
+The other functionality of Aurora, which was the only functionality of
+its predecessor "Ribbit", is letting you enter LaTeX equations in word
+processors such as MS Word or in Powerpoint. One can enter the equation
+in LaTeX markup, and the formatted equation is inserted as an object.<br>
+See <a href="http://elevatorlady.ca/">homepage (external
+link)</a>
+(Shareware)<br>
+Aurora needs a working LaTeX installation. If there is no, it will
+install a micro version of MiKTeX.
+</p>
+<p><b>"LaTeX in Word"</b>:
+See <a href="http://latexinword.sourceforge.net/">homepage
+(external link)</a>
+(Freeware, GPL). <br>
+It allows to enter LaTeX equations in word
+processors such as MS Word in LaTeX markup, and the
+formatted equation is inserted in the Wordprocessor as a png
+bitmap. It needs a server which performs the conversion. Server
+installation files are available from the <a href="http://sourceforge.net/project/showfiles.php?group_id=186573">download
+page (external link)</a>.</p>
+<p><a href="http://www.mathtype.com/"><b>MathType</b>
+(external link)</a> allows typing and pasting equations in LaTeX
+markup and also direct conversion of an equation in LaTeX markup which
+is part of the Word document text.</p>
+<p><b>OpenOffice</b>
+allows typing equations in LaTeX-like markup. </p>
+<hr>
+<h2>Use a Word import filter</h2>
+<p><a name="tex2word"></a><b>TeX2Word:</b>
+Shareware, 99$ (45$ academic). <br>
+Current version: 3.0, Feb 2011.<br>
+Support for more document styles and packages will be available with
+future versions. You can also supply support for document styles,
+packages and user defined macros by yourself (needs TeX programming
+knowledge).<br>
+Needs:<br>
+* MS Windows 2000, XP or later, <br>
+* MS Word 97 or later, <br>
+* with Word 97 to 2003, also <a href="http://www.mathtype.com/">MathType
+(external
+link)</a> 4
+or later is needed (full version of the Equation Editor which comes
+with MS Word).<br>
+See <a href="http://www.tex2word.com/">homepage
+(external link)</a></p>
+<p><a name="GrindEQ"></a><b>GrindEQ
+LaTeX-to-Word:</b> Shareware, 99EUR (49EUR academic).<br>
+converts LaTeX, AMS-LaTeX, Plain TeX, or AMS-TeX documents to Microsoft
+Word format.<br>
+You can choose the following formats for TeX/LaTeX equations: Microsoft
+Equation 2007, Microsoft Equation 3.x, or MathType. <br>
+Works with Microsoft Word 97/2000/XP/2003/2007 and Microsoft Windows
+98/Me/NT/2000/XP/2003/x64/Vista.<br>
+Evaluation version is restricted to 10 launches.<br>
+See <a href="http://www.grindeq.com/">homepage
+(external link)</a></p>
+<hr>
+<h2>Convert to RTF</h2>
+<h3>Free:</h3>
+<p><a name="latex2rtf"></a><b>latex2rtf</b>:
+LaTeX-to-RTF-converter. See the <a href="latex2rtf.html">more
+detailed page</a>. </p>
+<hr>
+<h2>Convert to WordPerfect format</h2>
+<h3>Commercial:</h3>
+<p><a name="TexPort"></a><b>TexPort</b>
+converts your TeX
+and LaTeX files to WordPerfect or Microsoft Word documents.<br>
+See <a href="texport.html">more detailed page</a>
+<br>
+See&nbsp;<a href="http://www.ktalk.com/texport.html">home
+page
+(external link)</a></p>
+<hr>
+<h2>Use a Word macro</h2>
+<h3>Free:</h3>
+<p><b>tex2doc</b> by <a href="http://members.a1.net/t.link/">Thomas Link
+(external link)</a>:
+LaTeX to WinWord 6 and WinWord 7(95) converter, written as Word macros.
+Also attempts to convert tables! Not compatible with Word 2000 and up,
+no further development.<br>
+<a href="http://members.a1.net/t.link/tex2doc.html">homepage
+(external link)</a>,
+</p>
+<p><b>ltx2word</b>,
+by myself: LaTeX to WinWord 6, WinWord 7(95) and WinWord 97 converter,
+written as Word macros. No tables. Not compatible with Word 2000 and
+up, no further development.<br>
+See <a href="ltx2word.html">more detailed page</a>.</p>
+<hr>
+<h2>Use a Word add-in</h2>
+<p>The following are no full converters but only allow
+typing or pasting LaTeX code into Word:</p>
+<p><b>"Aurora"</b>
+(formerly named Ribbit) can now convert LaTeX code (which must be
+placed on the Windows clipboard) to Word. The converter is still
+experimental and as such has a number of limitations, some of which
+will be addressed in future releases. The converter&#8217;s output
+will
+generally need some manual touching up to achieve the level of fidelity
+on par with the original document.<br>
+The other functionality of Aurora, which was the only functionality of
+its predecessor "Ribbit", is letting you enter LaTeX equations in word
+processors such as MS Word or in Powerpoint. One can enter the equation
+in LaTeX markup, and the formatted equation is inserted as an object.<br>
+See <a href="http://elevatorlady.ca/">homepage (external
+link)</a>
+(Shareware)<br>
+Aurora needs a working LaTeX installation. If there is no, it will
+install a micro version of MiKTeX.
+</p>
+<p><b>"LaTeX in Word"</b>: It allows to enter
+equations in word processors such as MS Word in LaTeX markup, and the
+formatted equation is inserted in the Wordprocessor as a png
+bitmap. It needs a server which performs the conversion. <br>
+See <a href="http://latexinword.sourceforge.net/">homepage
+(external link)</a> (Freeware, GPL)<br>
+Server installation files are available from the <a href="http://sourceforge.net/project/showfiles.php?group_id=186573">download
+page (external link)</a>.</p>
+<h2>Use a PowerPoint add-in</h2>
+<p><b>TexPoint</b> enables the easy use of Latex
+symbols and formulas in
+Powerpoint presentations. See <a href="http://texpoint.necula.org/">homepage
+(external link)</a>.
+(Shareware)
+<br>
+Latest version requires PowerPoint2000, does not work with earlier
+versions of PowerPoint.</p>
+<p><b>Aurora</b> (formerly named Ribbit) now also
+supports PowerPoint.
+See <a href="http://elevatorlady.ca/">homepage (external
+link)</a>
+(Shareware)</p>
+<hr>
+<h2>HTML as intermediate format</h2>
+<h3>LaTeX to HTML</h3>
+<p>cost free unless otherwise stated</p>
+<p>Because HTML is a structured format, the conversion between
+HTML and LaTeX is rather straightforward. However there remain the
+limitations of HTML compared to LaTeX, i.e. there are many elements in
+LaTeX which can not (yet?) be represented in HTML. Converters from
+LaTeX to HTML are:</p>
+<p><a name="TeX4ht"></a><strong>Recommended</strong>
+if you have TeX installed or don't mind to install it: <a href="http://tug.org/applications/tex4ht/mn.html">
+<b>TeX4ht</b> (external link)</a>
+is a highly configurable TeX-based converter to hypertext. It comes
+with a built-in default setting for plain TeX, LaTeX and TeXinfo, and
+it generates html with accompanying css stylesheet, xhtml, or xml. The
+converter needs a full TeX installation, but this gives the advantage
+that TeX's full support for macros and styles is available (with only
+few exceptions).<br>
+Equations are converted to either bitmaps or MathML. There are some
+different MathML flavors around which can be chosen by an option.
+(Following description is partially copied from the TeX4ht web site.)<br>
+The special command <br>
+<tt>oolatex</tt> <br>
+is available for producing xml compatible with OpenOffice, LibreOffice
+(and probably also StarOffice). The output of the command <tt>oolatex
+&lt;filename&gt;</tt> is a zipped file with same name and
+a ".odt" extension (containing the document in xml format which does
+not suffer the limitations of html). For this to work, TeX4ht needs a
+zip program which is not included in the TeX4ht distribution but e.g.
+in the MikTeX distribution.
+A zip program can be downloaded from e.g. <a href="http://www.info-zip.org/">http://www.info-zip.org/
+(external link)</a>.<br>
+The resulting .odt file can directly be opened in OpenOffice or
+LibreOffice, converted equations are editable in OpenOffice's or
+LibreOffice's own equation editor. OpenOffice and LibreOffice
+can save the document in MS Word 97/2000/XP (.doc) format, but
+some equations may not be converted correctly to Word. It is also
+possible to save as Microsoft Word 2007 XML (.docx), but this breaks
+the equations (at least in LibreOffice 3.3.2).<br>
+A command of the form <br>
+<tt>htlatex filename "html,word"&nbsp;"symbol/!"</tt><br>
+asks for HTML output tuned toward Microsoft Word. Such a format,
+however, relies on bitmaps for mathematical formulas.<br>
+Conversion to bitmaps additionally needs Ghostscript and ImageMagic or
+netpbm. <br>
+For more information see
+<a href="http://tug.org/applications/tex4ht/mn.html">http://tug.org/applications/tex4ht/mn.html
+(external link)</a>.
+</p>
+<p><a href="http://hutchinson.belmont.ma.us/tth/"><b>TTH</b>
+(external link)</a>:
+LaTeX-to-HTML converter which translates LaTeX into HTML 4.0 markup.
+Formulae are also translated into standard html markup. (Free for
+non-commercial applications.) <br>
+A sister of tth, <a href="http://hutchinson.belmont.ma.us/tth/mml/">TtM
+(external link)</a>,
+converts formulae to MathML (Linux version for free, Windows version
+must be paid).</p>
+<p><a href="http://www.ctan.org/tex-archive/support/ltoh"><b>ltoh</b>
+(external
+link)</a>:
+LaTeX-to-HTML converter which is highly customizable, i.e. you can
+define how the LaTeX macros which are used in your document are to be
+translated. Requires that the input file conforms to LaTeX2e (see
+documentation). It was last updated 1979, and it seems
+that the homepage is no longer available, so look on
+CTAN in .../support/ltoh/ .</p>
+<p><a href="http://para.inria.fr/%7Emaranget/hevea/"><b>HEVEA</b>
+(external link)</a>:
+LaTeX-to-HTML converter which translates LaTeX into HTML4.0 markup.
+Formulae are also translated into standard html markup (not yet using
+MathML).</p>
+<p><a href="http://hyperlatex.sourceforge.net/"><b>Hyperlatex</b>
+(external link)</a>
+allows the use of a subset of LaTeX to produce documents in HTML .</p>
+<p>Some converters are available from
+<a href="http://www.tex.ac.uk/tex-archive/CTAN.sites">CTAN
+(external link)</a>
+("Comprehensive TeX Archive Network"), e.g. in
+.../support/latex2html. <br>
+(The ... stands for a host specific base directory, which often is
+either "/pub/tex" or "/tex-archive") </p>
+<h3>HTML to Wordprocessor</h3>
+<p>Word 8 (97) and up contain the html converter by default (but
+its installation may have to be explicitly chosen during the Word setup
+in user-defined mode). <br>
+For Word 6 and 7 (95) for Windows and Mac there are free HTML
+converters available from Microsoft: <br>
+Download... <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/WORDIA.EXE">IA
+for Word 6 (external link)</a> / <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/WDIA204Z.EXE">IA
+for Word 7 (95) (external link)</a> / <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/MACIA20Z.HQX">IA
+for Word for Mac (external link)</a><br>
+</p>
+<p>WordPerfect 7 and up have an integrated InternetPublisher. <br>
+For WordPerfect 6.1 for Windows, the InternetPublisher is available
+separately:
+<br>
+Download...
+<a href="ftp://ftp.corel.com/pub/WordPerfect/wpwin/61/internetpublisher.exe">InternetPublisher
+for WPWin 6.1 (external link)</a> </p>
+<p>OpenOffice can also import html, but much better is using
+tex4ht for lossless conversion to native OpenOffice format.</p>
+<hr>
+<h2>Other intermediate formats</h2>
+<p>There are ways to use <b>SGML</b> as intermediate
+format, and others have used it successfully. Having had a quick look
+at it, I found it rather complicated, especially it seems that you have
+to define the translation rules yourself. So I did not put more effort
+in trying to use it. If anyone can give me a ready-to-use cookbook
+solution, I will include it here.</p>
+<p>An upcoming format is <b>XML</b>, a subset of
+which can be exported and imported by Microsoft Office 2000 and up,
+OpenOffice uses it as its native format, and the browser programmers
+are working on implementing XML. It actually is an instance of SGML. As
+it is more powerful than HTML,
+conversion from LaTeX to XML would lose much less information than
+conversion from LaTeX to HTML. There are good chances that it could be
+used as a general exchange format in the future. <a href="#TeX4ht">TeX4ht</a>
+already has scripts for converting to XML (TEI or DOCBOOK). MS Word
+2000 and earlier can not import XML, for these target systems convert
+to html+css using the xwtex and xwlatex scripts. MS Word 2003 can
+export and import XML, but I haven't yet tested whether it can import
+the TEI or DOCBOOK files produced by TeX4ht. <br>
+The most successful path is using <a href="textopc.html#TeX4ht">TeX4ht</a>
+to convert to the OpenOffice format (.sxw, which actually is a zip
+compressed archive containing the document and vector graphics as XML
+and the bitmap graphics as bitmap files) and open this in OpenOffice.
+One could stop there, as OpenOffice is publicly available, or go on and
+save from OpenOffice as a "MS Word 97/2000/XP"
+file.</p>
+<p>Most astonishing, one could also use <b>PDF</b>
+as intermediate format.
+Generating PDF from LaTeX is straightforward if you have a full TeX
+implementation installed. If you have the full commercial version of
+Adobe Acrobat 7, you can open the pdf and "save as" e.g. rtf (saving
+"as Word doc" actually generates an rtf file, too), xml, or plain
+text. Or you can use other commercial software to convert PDF to Word,
+just do a www search for "pdf to word" to get several hits. In this
+path of conversion however the document strucure and probably some
+formatting will be lost. </p>
+<p>Finally, you can use OCR software to convert any printed
+document to word or plain text. To avoid the inaccuracy introduced by
+printing to paper and scanning, you can convert the TeX output to ps or
+pdf, convert this to a bitmap (using ghostscript), and feed this bitmap
+into the ocr software.</p>
+<hr>
+<h2>Convert to FrameMaker</h2>
+<p><b>la2mml</b>: converts LaTeX to FrameMaker
+format. Maybe outdated, latest version was created
+Nov. 1995. <br>
+See <a href="la2mml.html">more detailed page</a>.<br>
+<a href="http://vasc.ri.cmu.edu/old_help/Document/Latex2fm/latex2fm.html">homepage
+(external link)</a>
+</p>
+<p><b>FrameMaker Utilities</b>: Contains converters
+for both directions
+(LaTeX &lt;-&gt; FrameMaker) as well as templates which make
+conversion from Framemaker to LaTeX more easy<br>
+<a href="http://www.cs.stir.ac.uk/%7Ekjt/software/framemaker/">
+homepage (external link)</a>
+</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 &#8230; 2011 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation
+format) is granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html>
diff --git a/help/wp-conv/tx2pctbl.html b/help/wp-conv/tx2pctbl.html
new file mode 100644
index 0000000000..bc21d364b3
--- /dev/null
+++ b/help/wp-conv/tx2pctbl.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>LaTeX -&gt; PC Converter Quick Comparison List</title></head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="textopc.html">Converters from LaTeX to PC Textprocessors - Overview</a></p>
+<h1>LaTeX -&gt; PC Converter Quick Comparison List</h1>
+<p><strong>Switch conversion direction: <a href="pc2txtbl.html">From PC to LaTeX</a></strong></p>
+<p>Author: Wilfried Hennings (texconvfaq "at" gmx.de), last
+update of this page on March 3, 2011</p>
+<p>NOTE: This table is still under construction. I only had time
+to include the most recent converters.</p>
+<table border="1" width="100%">
+<tbody>
+<tr>
+<th width="18%">Program<br>
+Author(s)<br>
+referred version</th>
+<th width="37%">Features</th>
+<th width="18%">supported Systems</th>
+<th width="229">where to get<br>(external links!)</th>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">TeX2Word<br>
+Chikrii Softlab. shareware, 99$ (45$ academic)<br>3.0, Feb. 2011 </td>
+<td align="left" valign="top" width="37%">load
+TeX file from within Word. Needs Word97 or later. With Word 97 to 2003, also MathType is needed. </td>
+<td align="left" valign="top" width="18%">Windows 2000, XP or later</td>
+<td align="left" valign="top" width="229"><a href="http://www.tex2word.com/">www.tex2word.com</a></td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">TeX4ht
+(free)</td>
+<td align="left" valign="top" width="37%">invokes
+TeX to convert to
+html+stylesheet which can be loaded into Word; converts equations to
+either bitmaps or MathML</td>
+<td align="left" valign="top" width="18%">DOS,
+MS Windows, all kinds of Unix</td>
+<td align="left" valign="top" width="229">
+<a href="http://www.cse.ohio-state.edu/%7Egurari/TeX4ht/mn.html">www.cse.ohio-state.edu/~gurari/TeX4ht/mn.html</a>
+</td>
+</tr>
+<tr>
+<td align="left" valign="top" width="18%">latex2rtf
+(free)<br>
+Scott Prahl<br>
+v. 2.1.1 b7, Feb. 2011</td>
+<td align="left" valign="top" width="37%">LaTeX-to-RTF-converter.
+<br>
+conversion of most equation elements to EQ fields (or images, which
+requires a TeX installation, ImageMagick, and Ghostscript) </td>
+<td align="left" valign="top" width="18%">DOS,
+MS Windows 95 / 98 / ME / NT4 / 2000 / XP, Macintosh, all kinds of Unix</td>
+<td align="left" valign="top" width="229">CTAN:
+directory .../support/latex2rtf;<br>
+for most recent versions and development see the
+<a href="http://sourceforge.net/projects/latex2rtf/">project on
+sourceforge.net</a></td>
+</tr>
+</tbody>
+</table>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 ... 2011
+Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have something changed, contact me (texconvfaq "at" gmx.de).
+Reformatting (e.g. from HTML to some other presentation format) is
+granted as long as the contents are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/w2latex.html b/help/wp-conv/w2latex.html
new file mode 100644
index 0000000000..337f8acaf0
--- /dev/null
+++ b/help/wp-conv/w2latex.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>w2latex converter</title>
+</head>
+
+<body>
+
+<p>Up to the <a href="http://tug.org">TUG homepage (external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC Textprocessors to LaTeX -
+Overview</a></p>
+
+<h1>w2latex</h1>
+
+<p>last update: July 28, 1998</p>
+
+<p>written in C. (C compiler necessary.) Actually converts RTF to LaTeX. <br>
+The Word document must first be saved to disk in RTF format. </p>
+
+<p>Advantages: <br>
+Converts text elements and formula fields. <br>
+Converts nearly all special characters of the basic TrueType fonts (Arial,
+Courier New, Times New Roman) I personally made some changes to additionally
+support German left quotes and a few other special characters. </p>
+
+<p>Disadvantages: <br>
+Does not convert the document structure (i.e. headings are not recognised as
+such). <br>
+Does not handle other fields, equation editor objects, graphics. Table handling
+is rudimentary (conversion of table cells to minipages, but problems with
+borders). <br>
+It only handles RTF versions up to WinWord 2, not yet WinWord 6. </p>
+
+<p>Can be found on all CTAN sites, dir .../support/w2latex <br>
+German version is in dir .../support/w2latex/german <br>
+(The ... stands for a host specific base directory, which often is either
+"/pub/tex" or "/tex-archive") </p>
+
+<hr>
+
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2001, 2007, 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+
+<ul>
+ <li>it must remain intact and the contents unchanged; if you'd like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting (e.g.
+from HTML to some other presentation format) is granted as long as the contents
+are unchanged. </li>
+ <li>you may NOT ask money for it except a reasonable cost for media and
+distribution</li>
+</ul>
+
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body>
+</html>
diff --git a/help/wp-conv/winw2ltx.html b/help/wp-conv/winw2ltx.html
new file mode 100644
index 0000000000..0dbf535784
--- /dev/null
+++ b/help/wp-conv/winw2ltx.html
@@ -0,0 +1,85 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>WINW2LTX macros</title>
+
+</head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>WINW2LTX</h1>
+<p>last update: Aug 12, 2008</p>
+<p>A set of macros for WinWord 2, now also available for WinWord
+6 and 7 (95)
+<br>
+by Allin Cottrell &lt;cottrell "at" wfu.edu&gt;<br>
+Adapted to German WinWord versions by Wilfried Hennings in
+1998.<br>
+Heavily extended and adapted to WinWord97 (and up) by Vincent Belache
+in 2008.</p>
+Advantages:<br>
+Converts the document structure, i.e. headings level 1 and 2 (and level
+3 in later version), bulleted lists and numbered lists, and some of
+the
+special characters.<br>
+<br>
+------------------------------------------------------------------
+<br>
+<br>
+<b>English / French Word97 version Aug. 2008:</b><br>
+<br>
+Heavily extended and adapted to WinWord97 (and up) by Vincent Belache.
+<br>
+Now also converts EQ fields.<br>
+<br>
+<b>Download</b> <a href="bin/w97toltx.zip">w97toltx.zip</a>. This package contains a word doc with the macros and further descriptions.<br>
+<br>
+Caution: <br>
+1) Before using, the macros have to be localized.<br>
+2) I (Wilfried Hennings) did not test them and give no support.<br>
+<br>
+------------------------------------------------------------------<br>
+<br>
+<b>German Word 95 Version Feb. 1998:</b> <br>
+<p>Supported: <br>
+Heading levels 1 to 5 <br>
+most special characters from the standard font and the symbol font.<br>
+Formulas can not be converted by this macro, but after its completion
+they can
+be converted by MathType, the full version of the equation editor.<br>
+<b>Download</b> latest German version <a href="bin/w95toltx.zip">w95toltx.zip</a>. This zipfile
+contains: </p>
+<dl>
+<dt>w95toltx.dot:</dt>
+<dd>Template for GERMAN WinWord 7, probably also WinWord 6. <br>
+NOT designed for, but adaptable to non-German versions. </dd>
+<dt>license.txt:</dt>
+<dd>The GNU Public License</dd>
+</dl>
+<p>Note: This macro set is free software; you can redistribute it
+and/or modify
+it under the terms of the <a href="http://www.gnu.org/copyleft/gpl.html">GNU
+General Public License (external link)</a> as published by the
+Free Software
+Foundation; either
+version 2 of the License, or (at your option) any later version. </p>
+<br>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998 ... 2008 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/word2x.html b/help/wp-conv/word2x.html
new file mode 100644
index 0000000000..3319bee520
--- /dev/null
+++ b/help/wp-conv/word2x.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>word2x</title>
+
+</head>
+<body>
+<p>Up to the <a href="http://tug.org">TUG homepage
+(external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>word2x</h1>
+<p>last update of this page: Feb. 9, 2009</p>
+<p>&copy; D.P.Simpson 2000 (word2x "at" duncan.telstar.net)</p>
+<p>Converts MS Word for Windows 6.0 / 7.0(=95) documents
+(binary!) to LaTeX, plain text or html,
+without the necessity to have Word available, also on many non-PC
+systems.</p>
+<p>Latest version of this converter is of 2000.
+</p>
+<p>See <a href="http://sourceforge.net/projects/word2x/">http://word2x.sourceforge.net/
+(external link)</a></p>
+<p>Written in C++</p>
+<p>Environments reported to work include</p>
+<ul>
+<li>RS6000 running AIX (Unix)</li>
+<li>cygwin32 (win 32 Microsoft platforms)</li>
+<li>DEC Alpha AXP under OSF/1 (Unix)</li>
+<li>IBM SP2 (Unix)</li>
+<li><a href="http://www.linux.org/index.html">Linux
+(external link)</a>
+(Unix)</li>
+<li>SunOS (Unix)&lt; /LI&gt; </li>
+<li>gcc on solaris (unix)</li>
+<li>FreeBSD (Unix)</li>
+<li>SGI (Unix, some hacking reuqired)</li>
+<li>OS/2 and EMX with <a href="http://mars.aclcom.co.uk/download/word2x_os2.zip">this
+patch (external link)</a> from Oleg V.Cat. Another port by Joerg
+Klemenz has a
+<a href="http://www.d3.net/joerg/word2x.html">web page
+(external link)</a>.</li>
+</ul>
+<p>Environments reported <b>not</b> to work include</p>
+<ul>
+<li>acc on Solaris (source ANSI violations, fixes wanted)</li>
+<li>Microsoft Visual C++ (lots of problems, includng lack of
+alloca and incapable make clone)</li>
+<li>Borland C++</li>
+</ul>
+<p>Further development in progress. </p>
+<p>On CTAN sites, directory <br>
+.../tools/word2x <br>
+(The ... stands for a host specific base directory, which often is
+either
+"/pub/tex" or "/tex-archive") </p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright &copy; 1998 &hellip; 2009 Wilfried Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file
diff --git a/help/wp-conv/wp2latex.html b/help/wp-conv/wp2latex.html
new file mode 100644
index 0000000000..1ef07f247f
--- /dev/null
+++ b/help/wp-conv/wp2latex.html
@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><title>WP2LaTeX</title>
+
+</head>
+<body>
+<p>Up to the <a href="http://tug.org/">TUG homepage
+(external link)</a><br>
+Up to <a href="pctotex.html">Converters from PC
+Textprocessors to LaTeX -
+Overview</a></p>
+<h1>WP2LaTeX</h1>
+<p>last update: Feb 9, 2011</p>
+<p>written in C. Current version converts Macintosh WordPerfect
+1.x, 2.x, 3.x, 4.x, PC WordPerfect 4.x, 5.x and 6/7/8.x
+to LaTeX.</p>
+<p> Latest version is 3.53 (Sep. 19, 2010). Download
+from
+<a href="http://www.penguin.cz/%7Efojtik/wp2latex/wp2latex.htm">http://www.penguin.cz/~fojtik/wp2latex/wp2latex.htm
+(external link)</a> <br>
+WP2LaTeX is also on CTAN sites, dir .../support/wp2latex , but this
+contains an older version (3.38).<br>
+Executables are available for MSDOS, MSWIN and LINUX. </p>
+<p>converts (e.g.)</p>
+<ul>
+<li>Equations</li>
+<li>Tables, Tabs (only WP5.x and up)</li>
+<li>Footnotes, Endnotes</li>
+<li>Cross-References (only WP5.x and up)</li>
+<li>Superscript, Subscript</li>
+<li>Extended characters (foreign language/accented, math, Greek
+- not linedrawing)</li>
+<li>Newspaper-style columns (using multicol.sty) (only WP5.x
+and up)</li>
+</ul>
+<p>For more info on features, see homepage -&gt;
+<a href="http://www.penguin.cz/%7Efojtik/wp2latex/wp2l_features.htm">features
+(external link)</a>
+</p>
+<hr>
+<p>This HTML page is part of the texconv pages.<br>
+Copyright 1998, 1999, 2000, 2002, 2003, 2007, 2008, 2011 Wilfried
+Hennings<br>
+You may copy and redistribute it under the following conditions:</p>
+<ul>
+<li>it must remain intact and the contents unchanged; if you'd
+like to have
+something changed, contact me (texconvfaq "at" gmx.de). Reformatting
+(e.g.
+from HTML to some other presentation format) is granted as long as the
+contents
+are unchanged. </li>
+<li>you may NOT ask money for it except a reasonable cost for
+media and
+distribution</li>
+</ul>
+<p>Please also note the <a href="index.html#disclaimer">disclaimer</a>.</p>
+</body></html> \ No newline at end of file