move generic english documents out of texmf-doc

git-svn-id: svn://tug.org/texlive/trunk@13396 c570f23f-e606-0410-a88d-b1316a301751

529 files changed, 80211 insertions, 0 deletions

diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.16b b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.16b
new file mode 100644
index 00000000000..1a9ab7d229d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.16c b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.16c
new file mode 100644
index 00000000000..8a651ecab89
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.17 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.17
new file mode 100644
index 00000000000..c5c26c2c451
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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 Grätzer'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/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.18 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.18
new file mode 100644
index 00000000000..75f90d12bc6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog
new file mode 100644
index 00000000000..8d4f3747781
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog
@@ -0,0 +1,13349 @@
+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
+
+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 etooolbox
+
+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 résumé
+
+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 schröcker
+	(section{Introduction}): mention schröcker
+
+	* 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
+	 schröder'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/Master/texmf-dist/doc/generic/FAQ-en/Makefile b/Master/texmf-dist/doc/generic/FAQ-en/Makefile
new file mode 100644
index 00000000000..981a8bbcaa3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/Makefile
@@ -0,0 +1,191 @@
+BODY	= faqbody.tex filectan.tex dirctan.tex
+MACROS	= faq.cls faq.sty
+CONFIGS	= archive.cfg
+CMFONTS	= cmz
+PATCH   = newfaq-patch.tex additions.tex add-errors.tex add-biblio.tex \
+	  add-general.tex
+MAKEF	= Makefile
+
+LATEX	= latex
+PDFLATEX = pdflatex
+DVIPS	= dvips
+
+# define variables WEB, WEB_BETA, CGI_BIN, HOME_DIR, CTAN_HOME, CTAN_ROOT
+include locations.mk
+
+CTAN_HOME = help/uk-tex-faq
+
+#h
+#hThe main targets of this Makefile are
+#h	all		build a distribution
+#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-beta	ditto, except beta distribution
+#h
+#h	inst-perl	install texfaq2html in the cgi-bin directory
+#h			(to be run on the CTAN machine)
+#h	inst-perl-beta	ditto, for texfaq2html-beta
+#h
+#h	html		make html files in html/
+#h	inst-html	export html/ files via ftp.cl.cam.ac.uk
+
+help:;	@sed -n 's/^#h//p' < $(MAKEF)
+
+all:	newfaq.pdf letterfaq.pdf \
+	newfaq.ps letterfaq.ps \
+	newfaq-cm.dvi letterfaq-cm.dvi
+
+# 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
+	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
+	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)
+	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
+	mv pdf-newfaq-patch.pdf newfaq-patch.pdf
+	rm pdf-newfaq-patch.tex
+
+patch.ps: newfaq-patch.ps
+
+newfaq-patch.ps: newfaq-patch.dvi
+	$(DVIPS) -P$(CMFONTS) -j1 newfaq-patch
+
+patch.dvi: newfaq-patch.dvi
+
+newfaq-patch.dvi: $(PATCH) $(BODY) $(MACROS) $(CONFIGS)
+	rm -f faqfont.cfg
+	while ( \
+	  $(LATEX) newfaq-patch ; \
+	  grep "Rerun to get cross" newfaq-patch.log > /dev/null ) do true ; \
+        done
+
+newfaq.ps: newfaq.dvi
+	$(DVIPS) -P$(CMFONTS) -j1 newfaq
+
+letterfaq.ps: letterfaq.dvi
+	$(DVIPS) -t letter -P$(CMFONTS) -j1 letterfaq
+
+newfaq.dvi newfaq.aux: newfaq.tex $(BODY) $(MACROS) $(CONFIGS)
+	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
+
+#install:
+#	(cd /homes/rf/FTP/faq; \
+#	 make -f /homes/rf/tex/faq/Makefile.FTP)
+
+ctan:
+	(cd $(CTAN_ROOT)/$(CTAN_HOME); \
+	 really -u ctan make -f /homes/rf/tex/faq/Makefile.CTAN)
+
+web: $(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list
+
+$(WEB)/dirctan.tex: $(HOME_DIR)/dirctan.tex
+$(WEB)/filectan.tex: $(HOME_DIR)/filectan.tex
+$(WEB)/faqbody.tex: $(HOME_DIR)/faqbody.tex
+$(WEB)/newfaq.aux: $(HOME_DIR)/newfaq.aux
+$(WEB)/archive.list: $(HOME_DIR)/archive.list
+
+$(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list:
+	rm -f $@
+	copy -t $? $@
+	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)/dirctan.tex: $(HOME_DIR)/dirctan.tex
+$(WEB_BETA)/filectan.tex: $(HOME_DIR)/filectan.tex
+$(WEB_BETA)/faqbody.tex: $(HOME_DIR)/faqbody.tex
+$(WEB_BETA)/newfaq.aux: $(HOME_DIR)/newfaq.aux
+$(WEB_BETA)/archive.list: $(HOME_DIR)/archive.list
+
+$(WEB_BETA)/dirctan.tex $(WEB_BETA)/filectan.tex $(WEB_BETA)/faqbody.tex $(WEB_BETA)/newfaq.aux $(WEB_BETA)/archive.list:
+	rm -f $@
+	copy -t $? $@
+	chmod 444 $@
+
+inst-perl: $(CGI_BIN)/texfaq2html $(CGI_BIN)/sanitize.pl
+inst-perl-beta: $(CGI_BIN)/texfaq2html-beta $(CGI_BIN)/sanitize-beta.pl
+
+$(CGI_BIN)/texfaq2html: $(HOME_DIR)/texfaq2html
+$(CGI_BIN)/texfaq2html-beta: $(HOME_DIR)/texfaq2html-beta
+$(CGI_BIN)/sanitize.pl: $(HOME_DIR)/sanitize.pl
+$(CGI_BIN)/sanitize-beta.pl: $(HOME_DIR)/sanitize.pl
+
+$(CGI_BIN)/texfaq2html $(CGI_BIN)/texfaq2html-beta $(CGI_BIN)/sanitize.pl $(CGI_BIN)/sanitize-beta.pl:
+	co -l $@
+	copy -t $? $@
+	ci -u -m"automatic check-in" $@
+
+html:	$(HTMLDIR)/index.html
+
+$(HTMLDIR)/index.html: $(BODY) newfaq.aux
+	./texfaq2file
+
+inst-html: $(HTMLDIR)/index.html
+	gtar czvf /homes/rf/FTP/faq/FAQ-html.tar.gz README html/*
+
+clean:
+	rm -f *.ps *.pdf *.dvi *.log *.bak *.toc *.out comment.cut
+	rm -f *.aux html/*.html
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/README b/Master/texmf-dist/doc/generic/FAQ-en/README
new file mode 100644
index 00000000000..1f452b06e05
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/archive.cfg b/Master/texmf-dist/doc/generic/FAQ-en/archive.cfg
new file mode 100644
index 00000000000..8b64957f06f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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{ftp://ftp.tex.ac.uk/tex-archive/} % 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/Master/texmf-dist/doc/generic/FAQ-en/archive.list b/Master/texmf-dist/doc/generic/FAQ-en/archive.list
new file mode 100644
index 00000000000..60945ca30d0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/archive.list
@@ -0,0 +1,4 @@
+ftp.tex.ac.uk   tex-archive
+ftp.dante.de    tex-archive
+tug2.cs.umb.edu tex-archive
+ftp.cdrom.com   pub/tex/ctan
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex
new file mode 100644
index 00000000000..927736d1e15
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex
@@ -0,0 +1,1018 @@
+%
+% protect ourself against being read twice
+\csname readCTANdirs\endcsname
+\let\readCTANdirs\endinput
+%
+% declarations of significant directories on CTAN
+\CTANdirectory{2etools}{macros/latex/required/tools}
+\CTANdirectory{4spell}{support/4spell}
+\CTANdirectory{Catalogue}{help/Catalogue}
+\CTANdirectory{CJK}{language/chinese/CJK}
+\CTANdirectory{MimeTeX}{support/mimetex}
+\CTANdirectory{Tabbing}{macros/latex/contrib/Tabbing}
+\CTANdirectory{TeXtelmExtel}{systems/msdos/emtex-contrib/TeXtelmExtel}
+\CTANdirectory{TftI}{info/impatient}
+\CTANdirectory{a0poster}{macros/latex/contrib/a0poster}
+\CTANdirectory{a2ping}{graphics/a2ping}
+\CTANdirectory{a4}{macros/latex/contrib/a4}
+\CTANdirectory{abc2mtex}{support/abc2mtex}
+\CTANdirectory{abstract}{macros/latex/contrib/abstract}
+\CTANdirectory{abstyles}{biblio/bibtex/contrib/abstyles}
+\CTANdirectory{accents}{support/accents}
+\CTANdirectory{acorn}{obsolete/systems/acorn}
+\CTANdirectory{acronym}{macros/latex/contrib/acronym}
+\CTANdirectory{ada}{web/ada}
+\CTANdirectory{addindex}{indexing/addindex}
+\CTANdirectory{adjkerns}{fonts/utilities/adjkerns}
+\CTANdirectory{ae}{fonts/ae}
+\CTANdirectory{aeguill}{macros/latex/contrib/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}
+\CTANdirectory{algorithmicx}{macros/latex/contrib/algorithmicx}
+\CTANdirectory{algorithms}{macros/latex/contrib/algorithms}
+\CTANdirectory{alpha}{nonfree/systems/mac/support/alpha}
+\CTANdirectory{amiga}{systems/amiga}
+\CTANdirectory*{ams-AMStype1}{fonts/amsfonts/ps-type1}
+\CTANdirectory{amsfonts-euler}{fonts/amsfonts/sources/euler}
+\CTANdirectory{amsfonts-symbols}{fonts/amsfonts/sources/symbols}
+\CTANdirectory{amsfonts-latex}{fonts/amsfonts/latex}
+\CTANdirectory{amsfonts-plain}{fonts/amsfonts/plaintex}
+\CTANdirectory{amslatex}{macros/latex/required/amslatex}
+\CTANdirectory{amslatex-primer}{info/amslatex/primer}
+\CTANdirectory{amspell}{support/amspell}
+\CTANdirectory{amsrefs}{macros/latex/contrib/amsrefs}
+\CTANdirectory{amstex}{macros/amstex}
+\CTANdirectory{answers}{macros/latex/contrib/answers}
+\CTANdirectory{ant}{systems/ant}
+\CTANdirectory{apl}{fonts/apl}
+\CTANdirectory{aplweb}{web/apl/aplweb}
+\CTANdirectory{appl}{web/reduce/rweb/appl}
+\CTANdirectory{appendix}{macros/latex/contrib/appendix}
+\CTANdirectory{arabtex}{language/arabic/arabtex}
+\CTANdirectory{arc521}{tools/arc521}
+\CTANdirectory{arj}{tools/arj}
+\CTANdirectory{armenian}{fonts/armenian}
+\CTANdirectory{aro-bend}{info/aro-bend}
+\CTANdirectory{asc2tex}{systems/msdos/asc2tex}
+\CTANdirectory{ascii}{fonts/ascii}
+\CTANdirectory*{aspell}{support/aspell}
+\CTANdirectory{astro}{fonts/astro}
+\CTANdirectory{atari}{systems/atari}
+\CTANdirectory{atob}{tools/atob}
+\CTANdirectory{atops}{support/atops}
+\CTANdirectory{auctex}{support/auctex}
+\CTANdirectory{autolatex}{support/autolatex}
+\CTANdirectory{auto-pst-pdf}{macros/latex/contrib/auto-pst-pdf}
+\CTANdirectory{aweb}{web/ada/aweb}
+\CTANdirectory{awk}{web/spiderweb/src/awk}
+\CTANdirectory{axodraw}{graphics/axodraw}
+\CTANdirectory{babel}{macros/latex/required/babel}
+\CTANdirectory{babelbib}{biblio/bibtex/contrib/babelbib}
+\CTANdirectory{badge}{macros/plain/contrib/badge}
+\CTANdirectory{bakoma}{fonts/cm/ps-type1/bakoma}
+\CTANdirectory{bakoma-tex}{systems/win32/bakoma}
+\CTANdirectory*{bakoma-texfonts}{systems/win32/bakoma/fonts}
+\CTANdirectory{barcodes}{fonts/barcodes}
+\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}
+\CTANdirectory{bbm-macros}{macros/latex/contrib/bbm}
+\CTANdirectory{bbold}{fonts/bbold}
+\CTANdirectory{bdfchess}{fonts/chess/bdfchess}
+\CTANdirectory{beamer}{macros/latex/contrib/beamer}
+\CTANdirectory{beebe}{dviware/beebe}
+\CTANdirectory{beton}{macros/latex/contrib/beton}
+\CTANdirectory{bezos}{macros/latex/contrib/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{bibextract}{biblio/bibtex/utils/bibextract}
+\CTANdirectory{bibgerm}{biblio/bibtex/contrib/germbib}
+\CTANdirectory{bibindex}{biblio/bibtex/utils/bibindex}
+\CTANdirectory{biblatex}{macros/latex/exptl/biblatex}
+\CTANdirectory{biblio}{info/biblio}
+\CTANdirectory{biblist}{macros/latex209/contrib/biblist}
+\CTANdirectory{bibsort}{biblio/bibtex/utils/bibsort}
+\CTANdirectory{bibtex}{support/lsedit/bibtex}
+\CTANdirectory{bibtex-doc}{biblio/bibtex/distribs/doc}
+\CTANdirectory{bibtex-doc-pdf}{biblio/bibtex/contrib/doc}
+\CTANdirectory{bibtool}{biblio/bibtex/utils/bibtool}
+\CTANdirectory{bibtools}{biblio/bibtex/utils/bibtools}
+\CTANdirectory{bibtopic}{macros/latex/contrib/bibtopic}
+\CTANdirectory{bibunits}{macros/latex/contrib/bibunits}
+\CTANdirectory{bibview}{biblio/bibtex/utils/bibview}
+\CTANdirectory{bigfoot}{macros/latex/contrib/bigfoot}
+\CTANdirectory{binhex}{tools/binhex}
+\CTANdirectory{bit2spr}{graphics/bit2spr}
+\CTANdirectory{black}{fonts/cm/utilityfonts/black}
+\CTANdirectory{blackletter}{fonts/blackletter}
+\CTANdirectory{blocks}{macros/text1/blocks}
+\CTANdirectory{blu}{nonfree/macros/blu}
+\CTANdirectory*{bluesky}{fonts/cm/ps-type1/bluesky}
+\CTANdirectory{bluesky-maps}{fonts/cm/ps-type1/bluesky-contrib/dvips}
+\CTANdirectory{bm2font}{graphics/bm2font}
+\CTANdirectory{bmeps}{support/bmeps}
+\CTANdirectory{boites}{macros/latex/contrib/boites}
+\CTANdirectory{bold}{fonts/cm/mf-extra/bold}
+\CTANdirectory{bonus}{systems/msdos/emtex-contrib/bonus}
+\CTANdirectory{boo}{tools/boo}
+\CTANdirectory{booktabs}{macros/latex/contrib/booktabs}
+\CTANdirectory{borceux}{macros/generic/diagrams/borceux}
+\CTANdirectory{breakurl}{macros/latex/contrib/breakurl}
+\CTANdirectory{bridge}{macros/plain/contrib/bridge}
+\CTANdirectory{brief_t}{support/brief_t}
+\CTANdirectory{bsplit}{tools/bsplit}
+\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}
+\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{camel}{macros/latex/contrib/camel}
+\CTANdirectory{caption}{macros/latex/contrib/caption}
+\CTANdirectory{carlisle}{macros/latex/contrib/carlisle}
+\CTANdirectory{cascover}{macros/plain/contrib/cascover}
+\CTANdirectory{casslbl}{macros/plain/contrib/casslbl}
+\CTANdirectory{catdvi}{dviware/catdvi}
+\CTANdirectory{ccaption}{macros/latex/contrib/ccaption}
+\CTANdirectory{ccfonts}{macros/latex/contrib/ccfonts}
+\CTANdirectory{cellular}{macros/plain/contrib/cellular}
+\CTANdirectory{cellspace}{macros/latex/contrib/cellspace}
+\CTANdirectory{changebar}{macros/latex/contrib/changebar}
+\CTANdirectory{changes}{macros/latex/contrib/changes}
+\CTANdirectory{chappg}{macros/latex/contrib/chappg}
+\CTANdirectory{chapterfolder}{macros/latex/contrib/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{checksum}{tools/checksum}
+\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{circ}{macros/generic/diagrams/circ}
+\CTANdirectory{circuit_macros}{graphics/circuit_macros}
+\CTANdirectory{cirth}{fonts/cirth}
+\CTANdirectory{cite}{macros/latex/contrib/cite}
+\CTANdirectory{citeref}{macros/latex/contrib/citeref}
+\CTANdirectory{clark}{fonts/utilities/afmtopl/clark}
+\CTANdirectory{clrscode}{macros/latex/contrib/clrscode}
+\CTANdirectory{cm}{fonts/cm}
+\CTANdirectory*{cm-AMStype1}{fonts/cm/ps-type1/bluesky}
+\CTANdirectory{cm-lgc}{fonts/ps-type1/cm-lgc}
+\CTANdirectory{cm-super}{fonts/ps-type1/cm-super}
+\CTANdirectory{cmactex}{nonfree/systems/mac/cmactex}
+\CTANdirectory{cmap}{macros/latex/contrib/cmap}
+\CTANdirectory{cmastro}{fonts/cmastro}
+\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}
+\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{combine}{macros/latex/contrib/combine}
+\CTANdirectory{comm}{tools/macutils/comm}
+\CTANdirectory{comment}{macros/latex/contrib/comment}
+\CTANdirectory{committee}{fonts/unsupported/committee}
+\CTANdirectory{comp-fonts-FAQ}{help/comp-fonts-FAQ}
+\CTANdirectory{compact}{tools/compact}
+\CTANdirectory{components-of-TeX}{info/components-of-TeX}
+\CTANdirectory{compress}{tools/compress}
+\CTANdirectory{compugraphics_8600}{macros/text1/compugraphics_8600}
+\CTANdirectory{concmath}{macros/latex/contrib/concmath}
+\CTANdirectory{concmath-f}{fonts/concmath}
+\CTANdirectory{concrete}{fonts/concrete}
+\CTANdirectory{conrado}{web/noweb/contrib/conrado}
+\CTANdirectory{context}{macros/context}
+\CTANdirectory{convert}{support/convert}
+\CTANdirectory{cortex-email.dir}{language/typingtex/cortex-email.dir}
+%[fonts/courier]
+\CTANdirectory{cptex}{macros/generic/cptex}
+\CTANdirectory{crop}{macros/latex/contrib/crop}
+\CTANdirectory*{crosstex}{biblio/crosstex}
+\CTANdirectory{crosswrd}{macros/latex/contrib/crosswrd}
+\CTANdirectory{crudetype}{dviware/crudetype}
+\CTANdirectory{crw}{macros/plain/contrib/crw}
+\CTANdirectory{cs-tex}{systems/atari/cs-tex}
+\CTANdirectory{ctable}{macros/latex/contrib/ctable}
+\CTANdirectory{ctan}{help/ctan}
+\CTANdirectory{cun}{fonts/cun}
+\CTANdirectory{currvita}{macros/latex/contrib/currvita}
+\CTANdirectory{curve}{macros/latex/contrib/curve}
+\CTANdirectory{curves}{macros/latex/contrib/curves}
+\CTANdirectory{custom-bib}{macros/latex/contrib/custom-bib}
+\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{datetime}{macros/latex/contrib/datetime}
+\CTANdirectory{davelove}{web/noweb/contrib/davelove}
+\CTANdirectory{db2tex}{support/db2tex}
+\CTANdirectory{dbtex}{support/dbtex}
+\CTANdirectory{dc-latex}{language/hyphen-accent/dc-latex}
+\CTANdirectory{dc-nfss}{language/hyphen-accent/dc-nfss}
+\CTANdirectory{detex}{support/detex}
+\CTANdirectory{devanagari}{language/devanagari}
+\CTANdirectory{diagram}{macros/generic/diagrams/borceux/diagram}
+\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{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}
+\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}
+\CTANdirectory{dpfloat}{macros/latex/contrib/dpfloat}
+\CTANdirectory{dpmigcc}{systems/msdos/dpmigcc}
+\CTANdirectory{draftcopy}{macros/latex/contrib/draftcopy}
+\CTANdirectory{draftwatermark}{macros/latex/contrib/draftwatermark}
+\CTANdirectory{dratex}{graphics/dratex}
+\CTANdirectory{drawing}{graphics/drawing}
+\CTANdirectory{dropcaps}{macros/latex209/contrib/dropcaps}
+\CTANdirectory{dropping}{macros/latex/contrib/dropping}
+\CTANdirectory{dtxtut}{info/dtxtut}
+\CTANdirectory{duerer}{fonts/duerer}
+\CTANdirectory{dvgt}{dviware/dvgt}
+\CTANdirectory{dvi-augsburg}{dviware/dvi-augsburg}
+\CTANdirectory{dvi2bitmap}{dviware/dvi2bitmap}
+\CTANdirectory{dvi2pcl}{dviware/dvi2pcl}
+\CTANdirectory{dvi2tty}{dviware/dvi2tty}
+\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}
+\CTANdirectory{dvipj}{dviware/dvipj}
+\CTANdirectory{dvipng}{dviware/dvipng}
+\CTANdirectory{dvips-pc}{systems/msdos/dviware/dvips}
+\CTANdirectory{dvips}{dviware/dvips}
+\CTANdirectory{dvisun}{dviware/dvisun}
+\CTANdirectory{dvitty}{dviware/dvitty}
+\CTANdirectory{dvivga}{dviware/dvivga}
+\CTANdirectory{e4t}{nonfree/systems/msdos/e4t}
+\CTANdirectory*{e-TeX}{systems/e-tex}
+\CTANdirectory{easytex}{systems/msdos/easytex}
+\CTANdirectory{ebib}{biblio/bibtex/utils/ebib}
+\CTANdirectory{ec}{fonts/ec}
+\CTANdirectory{ec-plain}{macros/ec-plain}
+\CTANdirectory{eco}{fonts/eco}
+\CTANdirectory{economic}{biblio/bibtex/contrib/economic}
+\CTANdirectory{edmac}{macros/plain/contrib/edmac}
+\CTANdirectory{ednotes}{macros/latex/contrib/ednotes}
+\CTANdirectory{eepic}{macros/latex/contrib/eepic}
+\CTANdirectory{ega2mf}{fonts/utilities/ega2mf}
+\CTANdirectory{eiad}{fonts/eiad}
+\CTANdirectory{elsevier}{macros/latex/contrib/elsevier}
+\CTANdirectory{elvish}{fonts/elvish}
+\CTANdirectory{elwell}{fonts/utilities/afmtopl/elwell}
+\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{endfloat}{macros/latex/contrib/endfloat}
+\CTANdirectory{english}{language/english}
+\CTANdirectory{engwar}{fonts/engwar}
+\CTANdirectory{enumitem}{macros/latex/contrib/enumitem}
+\CTANdirectory{environment}{support/lsedit/environment}
+\CTANdirectory{epigraph}{macros/latex/contrib/epigraph}
+\CTANdirectory{eplain}{macros/eplain}
+\CTANdirectory{epmtex}{systems/os2/epmtex}
+\CTANdirectory{epson}{dviware/epson}
+\CTANdirectory*{epstopdf}{support/epstopdf}
+\CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox}
+\CTANdirectory{ergotex}{systems/msdos/ergotex}
+\CTANdirectory{errata}{systems/knuth/dist/errata}
+\CTANdirectory{eso-pic}{macros/latex/contrib/eso-pic}
+\CTANdirectory{et}{nonfree/support/et}
+\CTANdirectory{ethiopia}{language/ethiopia}
+\CTANdirectory{ethtex}{language/ethiopia/ethtex}
+\CTANdirectory{etoolbox}{macros/latex/contrib/etoolbox}
+\CTANdirectory{euler}{fonts/amsfonts/sources/euler}
+\CTANdirectory{euler-latex}{macros/latex/contrib/euler}
+\CTANdirectory{eulervm}{fonts/eulervm}
+\CTANdirectory{euro-ce}{fonts/euro-ce}
+\CTANdirectory{euro-fonts}{fonts/euro}
+\CTANdirectory{eurofont}{macros/latex/contrib/eurofont}
+\CTANdirectory{europecv}{macros/latex/contrib/europecv}
+\CTANdirectory{eurosym}{fonts/eurosym}
+\CTANdirectory{everypage}{macros/latex/contrib/everypage}
+\CTANdirectory{excalibur}{systems/mac/support/excalibur}
+\CTANdirectory{excel2latex}{support/excel2latex}
+\CTANdirectory{excerpt}{web/spiderweb/tools/excerpt}
+\CTANdirectory{expdlist}{macros/latex/contrib/expdlist}
+\CTANdirectory{extracm}{fonts/amsfonts/sources/extracm}
+\CTANdirectory{extract}{macros/latex/contrib/extract}
+\CTANdirectory{extsizes}{macros/latex/contrib/extsizes}
+\CTANdirectory{fancyhdr}{macros/latex/contrib/fancyhdr}
+\CTANdirectory{fancyvrb}{macros/latex/contrib/fancyvrb}
+\CTANdirectory{fc}{fonts/jknappen/fc}
+\CTANdirectory{feyn}{fonts/feyn}
+\CTANdirectory{feynman}{macros/latex209/contrib/feynman}
+\CTANdirectory{feynmf}{macros/latex/contrib/feynmf}
+\CTANdirectory{fig2eng}{graphics/fig2eng}
+\CTANdirectory{fig2mf}{graphics/fig2mf}
+\CTANdirectory{fig2mfpic}{graphics/fig2mfpic}
+\CTANdirectory{filehdr}{tools/filehdr}
+\CTANdirectory{fink}{macros/latex/contrib/fink}
+\CTANdirectory{fixfoot}{macros/latex/contrib/fixfoot}
+\CTANdirectory{float}{macros/latex/contrib/float}
+\CTANdirectory{floatflt}{macros/latex/contrib/floatflt}
+\CTANdirectory{flow}{support/flow}
+\CTANdirectory{flowfram}{macros/latex/contrib/flowfram}
+\CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak}
+\CTANdirectory{fncychap}{macros/latex/contrib/fncychap}
+\CTANdirectory{foiltex}{macros/latex/contrib/foiltex}
+\CTANdirectory{fontch}{macros/plain/contrib/fontch}
+\CTANdirectory{fontinst}{fonts/utilities/fontinst}
+\CTANdirectory{fontname}{info/fontname}
+\CTANdirectory{fontspec}{macros/xetex/latex/fontspec}
+\CTANdirectory{font_selection}{macros/plain/contrib/font_selection}
+\CTANdirectory{footbib}{macros/latex/contrib/footbib}
+\CTANdirectory{footmisc}{macros/latex/contrib/footmisc}
+\CTANdirectory{footnpag}{macros/latex/contrib/footnpag}
+\CTANdirectory{for_tex}{biblio/bibtex/contrib/germbib/for_tex}
+\CTANdirectory{fourier}{fonts/fourier-GUT}
+\CTANdirectory{fouriernc}{fonts/fouriernc}
+\CTANdirectory{frankenstein}{macros/latex/contrib/frankenstein}
+\CTANdirectory{french-faq}{help/LaTeX-FAQ-francaise}
+\CTANdirectory{ftpd}{tools/ftpd}
+\CTANdirectory{ftpmail}{tools/ftpmail}
+\CTANdirectory{funnelweb}{web/funnelweb}
+\CTANdirectory{futhark}{fonts/futhark}
+\CTANdirectory{futhorc}{fonts/futhorc}
+\CTANdirectory{fweb}{web/fweb}
+\CTANdirectory{gellmu}{support/gellmu}
+\CTANdirectory{genfam}{support/genfam}
+\CTANdirectory{geometry}{macros/latex/contrib/geometry}
+\CTANdirectory{georgian}{fonts/georgian}
+\CTANdirectory{german}{language/german}
+\CTANdirectory{germbib}{biblio/bibtex/contrib/germbib}
+\CTANdirectory{gfs}{info/examples/FirstSteps} % gratzer's
+\CTANdirectory*{ghostscript}{support/ghostscript}
+\CTANdirectory*{ghostview}{support/ghostscript/gnu/ghostview}
+\CTANdirectory{glo+idxtex}{indexing/glo+idxtex}
+\CTANdirectory{gnuplot}{graphics/gnuplot}
+\CTANdirectory{go}{fonts/go}
+\CTANdirectory{gothic}{fonts/gothic}
+\CTANdirectory{graphbase}{support/graphbase}
+\CTANdirectory{graphics}{macros/latex/required/graphics}
+\CTANdirectory{graphics-plain}{macros/plain/graphics}
+\CTANdirectory{graphicx-psmin}{macros/latex/contrib/graphicx-psmin}
+\CTANdirectory{gray}{fonts/cm/utilityfonts/gray}
+\CTANdirectory{greek}{fonts/greek}
+\CTANdirectory{greektex}{fonts/greek/greektex}
+\CTANdirectory{gregory}{web/noweb/contrib/gregory}
+\CTANdirectory{gsftopk}{fonts/utilities/gsftopk}
+\CTANdirectory*{gsview}{nonfree/support/ghostscript/ghostgum}
+\CTANdirectory{gut}{usergrps/gut}
+\CTANdirectory*{gv}{support/gv}
+\CTANdirectory{ha-prosper}{macros/latex/contrib/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{hershey}{fonts/hershey}
+\CTANdirectory{hexbin}{tools/macutils/hexbin}
+\CTANdirectory{hfbright}{fonts/ps-type1/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}
+\CTANdirectory{htmlhelp}{info/htmlhelp}
+\CTANdirectory{hvfloat}{macros/latex/contrib/hvfloat}
+\CTANdirectory{hvmath}{fonts/micropress/hvmath}
+\CTANdirectory{hyacc-cm}{macros/generic/hyacc-cm}
+\CTANdirectory{hyper}{macros/latex/contrib/hyper}
+\CTANdirectory{hyperbibtex}{biblio/bibtex/utils/hyperbibtex}
+\CTANdirectory{hyperref}{macros/latex/contrib/hyperref}
+\CTANdirectory{hyphen-accent}{language/hyphen-accent}
+\CTANdirectory{hyphenat}{macros/latex/contrib/hyphenat}
+\CTANdirectory{hyphenation}{language/hyphenation}
+\CTANdirectory{ibygrk}{fonts/greek/ibygrk}
+\CTANdirectory{iching}{fonts/iching}
+\CTANdirectory{icons}{support/icons}
+\CTANdirectory{ifmslide}{macros/latex/contrib/ifmslide}
+\CTANdirectory{imaketex}{support/imaketex}
+\CTANdirectory{impact}{web/systems/mac/impact}
+\CTANdirectory{index}{macros/latex/contrib/index}
+\CTANdirectory{indexing}{indexing}
+\CTANdirectory{indian}{language/indian}
+\CTANdirectory{info}{info}
+\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}
+\CTANdirectory{iso-tex}{support/iso-tex}
+\CTANdirectory{ite}{support/ite}
+\CTANdirectory{ivd2dvi}{dviware/ivd2dvi}
+\CTANdirectory{jadetex}{macros/jadetex}
+\CTANdirectory{jemtex2}{systems/msdos/jemtex2}
+\CTANdirectory{jknappen-macros}{macros/latex/contrib/jknappen}
+\CTANdirectory{jonkrom}{web/noweb/contrib/jonkrom}
+\CTANdirectory{jpeg2ps}{nonfree/support/jpeg2ps}
+\CTANdirectory{jspell}{support/jspell}
+\CTANdirectory{jurabib}{macros/latex/contrib/jurabib}
+\CTANdirectory{kaelin}{web/noweb/contrib/kaelin}
+\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{koma-script}{macros/latex/contrib/koma-script}
+\CTANdirectory{korean}{fonts/korean}
+%[language/korean]
+\CTANdirectory{kpfonts}{fonts/kpfonts}
+\CTANdirectory{kyocera}{dviware/kyocera}
+\CTANdirectory{l2a}{support/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}
+\CTANdirectory{labels}{macros/latex/contrib/labels}
+\CTANdirectory{labtex}{macros/generic/labtex}
+\CTANdirectory{lacheck}{support/lacheck}
+\CTANdirectory{lametex}{support/lametex}
+\CTANdirectory{lamstex}{macros/lamstex}
+\CTANdirectory{latex}{macros/latex/base}
+\CTANdirectory{latex4jed}{support/jed}
+\CTANdirectory{larch}{web/spiderweb/src/larch}
+\CTANdirectory{laserjet}{dviware/laserjet}
+\CTANdirectory{lastpage}{macros/latex/contrib/lastpage}
+\CTANdirectory{latex-essential}{info/latex-essential}
+\CTANdirectory{latex-help-texinfo}{info/latex-help-texinfo}
+\CTANdirectory*{latex2html}{support/latex2html}
+\CTANdirectory{latex2rtf}{support/latex2rtf}
+\CTANdirectory{latexdiff}{support/latexdiff}
+\CTANdirectory{latexdoc}{macros/latex/doc}
+\CTANdirectory{latexhlp}{systems/atari/latexhlp}
+\CTANdirectory{latexmake}{support/latexmake}
+\CTANdirectory{latexmk}{support/latexmk}
+\CTANdirectory{ledmac}{macros/latex/contrib/ledmac}
+\CTANdirectory{leew}{web/noweb/contrib/leew}
+\CTANdirectory{lettrine}{macros/latex/contrib/lettrine}
+\CTANdirectory{levy}{fonts/greek/levy}
+\CTANdirectory{lextex}{macros/plain/contrib/lextex}
+\CTANdirectory{lgc}{info/examples/lgc}
+\CTANdirectory{lgrind}{support/lgrind}
+\CTANdirectory{lharc}{tools/lharc}
+\CTANdirectory{lineno}{macros/latex/contrib/lineno}
+\CTANdirectory{listbib}{macros/latex/contrib/listbib}
+\CTANdirectory{listings}{macros/latex/contrib/listings}
+\CTANdirectory{lm}{fonts/lm}
+\CTANdirectory{lollipop}{macros/lollipop}
+\CTANdirectory{lookbibtex}{biblio/bibtex/utils/lookbibtex}
+\CTANdirectory{lsedit}{support/lsedit}
+\CTANdirectory*{lshort-parent}{info/lshort}
+\CTANdirectory{ltx3pub}{info/ltx3pub}
+\CTANdirectory{ltxindex}{macros/latex/contrib/ltxindex}
+\CTANdirectory{lucida}{fonts/psfonts/bh/lucida}
+\CTANdirectory{lucida-psnfss}{macros/latex/contrib/psnfssx/lucidabr}
+\CTANdirectory{luximono}{fonts/LuxiMono}
+\CTANdirectory{lwc}{info/examples/lwc}
+\CTANdirectory{ly1}{macros/latex/contrib/psnfssx/ly1}
+\CTANdirectory{machdr}{tools/macunpack/machdr}
+\CTANdirectory*{mactex}{systems/mac/mactex}
+\CTANdirectory{mactotex}{graphics/mactotex}
+\CTANdirectory{macunpack}{tools/macunpack}
+\CTANdirectory{macutils}{tools/macutils}
+\CTANdirectory{mailing}{macros/latex/contrib/mailing}
+\CTANdirectory{make_latex}{support/make_latex}
+\CTANdirectory{makeafm.dir}{fonts/utilities/t1tools/makeafm.dir}
+\CTANdirectory{makedtx}{support/makedtx}
+\CTANdirectory{makeindex}{indexing/makeindex}
+\CTANdirectory{makeinfo}{macros/texinfo/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/psfonts/marvosym}
+\CTANdirectory*{mathdesign}{fonts/mathdesign}
+\CTANdirectory{mathdots}{macros/generic/mathdots}
+\CTANdirectory{mathematica}{macros/mathematica}
+\CTANdirectory{mathpazo}{fonts/mathpazo}
+\CTANdirectory{mathsci2bibtex}{biblio/bibtex/utils/mathsci2bibtex}
+\CTANdirectory{mathspic}{graphics/mathspic}
+\CTANdirectory{mcite}{macros/latex/contrib/mcite}
+\CTANdirectory{mctex}{support/mctex}
+\CTANdirectory{mcvert}{tools/mcvert}
+\CTANdirectory{mdwtools}{macros/latex/contrib/mdwtools}
+\CTANdirectory{memoir}{macros/latex/contrib/memoir}
+\CTANdirectory{messtex}{support/messtex}
+\CTANdirectory{metafont}{systems/mac/metafont}
+\CTANdirectory{metapost}{graphics/metapost}
+\CTANdirectory{metatype1}{fonts/utilities/metatype1}
+\CTANdirectory{mewltx}{support/mewltx}
+\CTANdirectory{mf-extra}{fonts/cm/mf-extra}
+\CTANdirectory{mf2ps}{fonts/utilities/mf2ps}
+\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}
+\CTANdirectory{mfnfss}{macros/latex/contrib/mfnfss}
+\CTANdirectory{mfpic}{graphics/mfpic}
+\CTANdirectory{mfware}{systems/knuth/dist/mfware}
+\CTANdirectory{mh}{macros/latex/contrib/mh}
+\CTANdirectory{microtype}{macros/latex/contrib/microtype}
+\CTANdirectory{midi2tex}{support/midi2tex}
+\CTANdirectory{midnight}{macros/generic/midnight}
+\CTANdirectory{miktexppc}{obsolete/systems/win32/miktexppc}
+\CTANdirectory{miktex-AXP}{obsolete/systems/win32/miktex-AXP}
+\CTANdirectory{minionpro}{fonts/minionpro}
+\CTANdirectory{minitoc}{macros/latex/contrib/minitoc}
+\CTANdirectory{mirror}{tools/mirror}
+\CTANdirectory{mixed}{tools/macutils/mixed}
+\CTANdirectory{mma2ltx}{graphics/mma2ltx}
+\CTANdirectory{mnsymbol}{fonts/mnsymbol}
+\CTANdirectory{mnu}{support/mnu}
+\CTANdirectory{models}{macros/text1/models}
+\CTANdirectory{moderncv}{macros/latex/contrib/moderncv}
+\CTANdirectory{modes}{fonts/modes}
+\CTANdirectory{moreverb}{macros/latex/contrib/moreverb}
+\CTANdirectory{mparhack}{macros/latex/contrib/mparhack}
+\CTANdirectory{mps2eps}{support/mps2eps}
+\CTANdirectory{ms}{macros/latex/contrib/ms}
+\CTANdirectory{msdos}{systems/msdos}
+\CTANdirectory{msx2msa}{fonts/vf-files/msx2msa}
+\CTANdirectory{msym}{fonts/msym}
+\CTANdirectory{mtx}{support/mtx}
+\CTANdirectory{multenum}{macros/latex/contrib/multenum}
+\CTANdirectory{multibbl}{macros/latex/contrib/multibbl}
+\CTANdirectory{multibib}{macros/latex/contrib/multibib}
+\CTANdirectory{multirow}{macros/latex/contrib/multirow}
+\CTANdirectory{musictex}{macros/musictex}
+\CTANdirectory{musixtex-egler}{macros/musixtex/egler}
+\CTANdirectory{musixtex-taupin}{macros/musixtex/taupin}
+\CTANdirectory{mutex}{macros/mtex}
+\CTANdirectory{mxedruli}{fonts/georgian/mxedruli}
+\CTANdirectory{nag}{macros/latex/contrib/nag}
+\CTANdirectory{natbib}{macros/latex/contrib/natbib}
+\CTANdirectory{nawk}{web/spiderweb/src/nawk}
+\CTANdirectory{ncctools}{macros/latex/contrib/ncctools}
+\CTANdirectory{newalg}{macros/latex/contrib/newalg}
+\CTANdirectory{newcommand}{support/newcommand}
+\CTANdirectory{newlfm}{macros/latex/contrib/newlfm}
+\CTANdirectory{newsletr}{macros/plain/contrib/newsletr}
+\CTANdirectory{nedit-latex}{support/NEdit-LaTeX-Extensions}
+\CTANdirectory{norbib}{biblio/bibtex/contrib/norbib}
+\CTANdirectory{noweb}{web/noweb}
+\CTANdirectory{nrc}{macros/latex/contrib/nrc}
+\CTANdirectory{ntg}{usergrps/ntg}
+\CTANdirectory{ntgclass}{macros/latex/contrib/ntgclass}
+\CTANdirectory{ntheorem}{macros/latex/contrib/ntheorem}
+\CTANdirectory{nts-l}{digests/nts-l}
+\CTANdirectory{nts}{systems/nts}
+\CTANdirectory{numprint}{macros/latex/contrib/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}
+\CTANdirectory{objectz}{macros/latex/contrib/objectz}
+\CTANdirectory{ocr-a}{fonts/ocr-a}
+\CTANdirectory{ocr-b}{fonts/ocr-b}
+\CTANdirectory{ofs}{macros/generic/ofs}
+\CTANdirectory{ogham}{fonts/ogham}
+\CTANdirectory{ogonek}{macros/latex/contrib/ogonek}
+\CTANdirectory{okuda}{fonts/okuda}
+\CTANdirectory{omega}{systems/omega}
+\CTANdirectory{os2}{systems/os2}
+\CTANdirectory{osmanian}{fonts/osmanian}
+\CTANdirectory{overpic}{macros/latex/contrib/overpic}
+\CTANdirectory{oztex}{nonfree/systems/mac/oztex}
+\CTANdirectory{oztex-german}{nonfree/systems/mac/oztex-german}
+\CTANdirectory{page}{support/lametex/page}
+\CTANdirectory{palladam}{language/tamil/palladam}
+\CTANdirectory{pandora}{fonts/pandora}
+\CTANdirectory{paralist}{macros/latex/contrib/paralist}
+\CTANdirectory{parallel}{macros/latex/contrib/parallel}
+\CTANdirectory{parc}{tools/parc}
+\CTANdirectory{passivetex}{macros/xmltex/contrib/passivetex}
+\CTANdirectory{patchcmd}{macros/latex/contrib/patchcmd}
+\CTANdirectory{patches}{web/spiderweb/patches}
+\CTANdirectory{pbm2tex}{support/pbm2tex}
+\CTANdirectory{pbmtopk}{graphics/pbmtopk}
+\CTANdirectory{pbox}{macros/latex/contrib/pbox}
+\CTANdirectory{pcwritex}{support/pcwritex}
+\CTANdirectory{pdcmac}{macros/plain/contrib/pdcmac}
+\CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages}
+\CTANdirectory{pdftex-graphics}{macros/pdftex/graphics}
+\CTANdirectory{pdftricks}{macros/latex/contrib/pdftricks}
+\CTANdirectory{penelope}{web/spiderweb/src/penelope}
+\CTANdirectory{pfm2afm}{fonts/utilities/pfm2afm}
+\CTANdirectory{pgf}{graphics/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}
+\CTANdirectory{picins}{macros/latex209/contrib/picins}
+\CTANdirectory{pict2e}{macros/latex/contrib/pict2e}
+\CTANdirectory{pictex}{graphics/pictex}
+\CTANdirectory{pictex-addon}{graphics/pictex/addon}
+\CTANdirectory{pictex-converter}{support/pictex-converter}
+\CTANdirectory{pictex-summary}{info/pictex/summary}
+\CTANdirectory{pkbbox}{fonts/utilities/pkbbox}
+\CTANdirectory{pkfix}{support/pkfix}
+\CTANdirectory{pkfix-helper}{support/pkfix-helper}
+\CTANdirectory{placeins}{macros/latex/contrib/placeins}
+\CTANdirectory{plain}{macros/plain/base}
+\CTANdirectory*{plnfss}{macros/plain/contrib/plnfss}
+\CTANdirectory{plttopic}{support/plttopic}
+\CTANdirectory{pmtex}{systems/os2/pmtex}
+\CTANdirectory{pmx}{support/pmx}
+\CTANdirectory{polish}{language/polish}
+\CTANdirectory{poorman}{fonts/poorman}
+\CTANdirectory{portuguese}{language/portuguese}
+\CTANdirectory{poster}{macros/generic/poster}
+\CTANdirectory{powerdot}{macros/latex/contrib/powerdot}
+\CTANdirectory{pp}{support/pp}
+\CTANdirectory{preprint}{macros/latex/contrib/preprint}
+\CTANdirectory{preview}{macros/latex/contrib/preview}
+\CTANdirectory*{preview-latex}{support/preview-latex}
+\CTANdirectory{print-fine}{support/print-fine}
+\CTANdirectory{printbib}{biblio/bibtex/utils/printbib}
+\CTANdirectory{printsamples}{fonts/utilities/mf2ps/doc/printsamples}
+\CTANdirectory{program}{macros/latex/contrib/program}
+\CTANdirectory{proofs}{macros/generic/proofs}
+\CTANdirectory*{protext}{systems/win32/protext}
+\CTANdirectory{ppower4}{support/ppower4}
+\CTANdirectory{ppr-prv}{macros/latex/contrib/ppr-prv}
+\CTANdirectory{prosper}{macros/latex/contrib/prosper}
+\CTANdirectory*{ps-type1}{fonts/cm/ps-type1}
+\CTANdirectory{ps-type3}{fonts/cm/ps-type3}
+\CTANdirectory{ps2mf}{fonts/utilities/ps2mf}
+\CTANdirectory{ps2pk}{fonts/utilities/ps2pk}
+\CTANdirectory{psbook}{systems/msdos/dviware/psbook}
+\CTANdirectory{psbox}{macros/generic/psbox}
+\CTANdirectory{pseudocode}{macros/latex/contrib/pseudocode}
+\CTANdirectory{psfig}{nonfree/graphics/psfig}
+\CTANdirectory{psfrag}{macros/latex/contrib/psfrag}
+\CTANdirectory{psfragx}{macros/latex/contrib/psfragx}
+\CTANdirectory{psizzl}{macros/psizzl}
+\CTANdirectory{psnfss}{macros/latex/required/psnfss}
+\CTANdirectory{psnfss-addons}{macros/latex/contrib/psnfss-addons}
+\CTANdirectory{psnfssx-mathtime}{macros/latex/contrib/psnfssx/mathtime}
+\CTANdirectory{pspicture}{macros/latex/contrib/pspicture}
+\CTANdirectory{psprint}{dviware/psprint}
+\CTANdirectory{pst-pdf}{macros/latex/contrib/pst-pdf}
+\CTANdirectory{pstab}{support/pstab}
+\CTANdirectory{pstoedit}{support/pstoedit}
+\CTANdirectory{pstricks}{graphics/pstricks}
+\CTANdirectory{psutils}{support/psutils}
+\CTANdirectory{punk}{fonts/punk}
+\CTANdirectory{purifyeps}{support/purifyeps}
+\CTANdirectory{pxfonts}{fonts/pxfonts}
+\CTANdirectory{pxlgen}{systems/msdos/pxlgen}
+\CTANdirectory{qdtexvpl}{fonts/utilities/qdtexvpl}
+\CTANdirectory{qfig}{support/qfig}
+\CTANdirectory{qms}{dviware/qms}
+\CTANdirectory{quicspool}{dviware/quicspool}
+\CTANdirectory{quotchap}{macros/latex/contrib/quotchap}
+\CTANdirectory{r2bib}{biblio/bibtex/utils/r2bib}
+\CTANdirectory{ransom}{fonts/ransom}
+\CTANdirectory{rcs}{macros/latex/contrib/rcs}
+\CTANdirectory{rcsinfo}{macros/latex/contrib/rcsinfo}
+\CTANdirectory{realcalc}{macros/generic/realcalc}
+\CTANdirectory{recycle}{fonts/recycle}
+\CTANdirectory{redit}{support/redit}
+\CTANdirectory{reduce}{web/reduce}
+%[web/spiderweb/src/reduce]
+\CTANdirectory{refcheck}{macros/latex/contrib/refcheck}
+\CTANdirectory{refer-tools}{biblio/bibtex/utils/refer-tools}
+\CTANdirectory{refman}{macros/latex/contrib/refman}
+\CTANdirectory{relabel}{support/relabel}
+\CTANdirectory{review}{support/lsedit/review}
+\CTANdirectory{revtex}{macros/latex/contrib/revtex}
+\CTANdirectory{rmit}{fonts/thai/rmit}
+\CTANdirectory{rnototex}{support/rnototex}
+\CTANdirectory{rotating}{macros/latex/contrib/rotating}
+\CTANdirectory{rotfloat}{macros/latex/contrib/rotfloat}
+\CTANdirectory{rsfs}{fonts/rsfs}
+\CTANdirectory{rsfs-type1}{fonts/rsfs/ps-type1/hoekwater}
+\CTANdirectory{rtf2tex}{support/rtf2tex}
+\CTANdirectory{rtf2html}{support/rtf2html}
+\CTANdirectory{rtf2latex}{support/rtf2latex}
+\CTANdirectory{rtf2latex2e}{support/rtf2latex2e}
+\CTANdirectory{rtflatex}{support/rtflatex}
+\CTANdirectory{rtfutils}{support/tex2rtf/rtfutils}
+\CTANdirectory{rumgraph}{support/rumgraph}
+\CTANdirectory{rune}{fonts/rune}
+\CTANdirectory{rweb}{web/reduce/rweb}
+\CTANdirectory{s2latex}{support/s2latex}
+\CTANdirectory{sam2p}{graphics/sam2p}
+\CTANdirectory{sanskrit}{language/sanskrit}
+\CTANdirectory{sauerj}{macros/latex/contrib/sauerj}
+\CTANdirectory{sauter}{fonts/cm/sauter}
+\CTANdirectory{savetrees}{macros/latex/contrib/savetrees}
+\CTANdirectory{sbtex}{systems/msdos/sbtex}
+\CTANdirectory{schemetex}{support/schemetex}
+\CTANdirectory{schemeweb}{web/schemeweb}
+\CTANdirectory{sciposter}{macros/latex/contrib/sciposter}
+\CTANdirectory{screenview}{dviware/screenview}
+\CTANdirectory{script}{macros/latex/contrib/script}
+\CTANdirectory{scripttex}{nonfree/macros/scripttex}
+\CTANdirectory{sectsty}{macros/latex/contrib/sectsty}
+\CTANdirectory{seminar}{macros/latex/contrib/seminar}
+\CTANdirectory{sfware}{fonts/softfonts/sfware}
+\CTANdirectory{shade}{macros/generic/shade}
+\CTANdirectory{showlabels}{macros/latex/contrib/showlabels}
+\CTANdirectory{sisisi}{systems/unix/sisisi}
+\CTANdirectory{slant}{fonts/cm/utilityfonts/slant}
+\CTANdirectory{slashbox}{macros/latex/contrib/slashbox}
+\CTANdirectory{slatex}{language/swedish/slatex}
+\CTANdirectory{smallcap}{macros/latex/contrib/smallcap}
+\CTANdirectory{smartref}{macros/latex/contrib/smartref}
+\CTANdirectory{sml}{web/spiderweb/src/sml}
+\CTANdirectory{snapshot}{macros/latex/contrib/snapshot}
+\CTANdirectory{softfonts}{fonts/softfonts}
+\CTANdirectory{soul}{macros/latex/contrib/soul}
+\CTANdirectory{southarabian}{fonts/southarabian}
+\CTANdirectory{spain}{biblio/bibtex/contrib/spain}
+\CTANdirectory{spelchek}{support/spelchek}
+\CTANdirectory{spell}{support/spell}
+\CTANdirectory{spiderweb}{web/spiderweb}
+\CTANdirectory{splitbib}{macros/latex/contrib/splitbib}
+\CTANdirectory{splitindex}{macros/latex/contrib/splitindex}
+\CTANdirectory{srune}{fonts/srune}
+\CTANdirectory{ssl}{web/spiderweb/src/ssl}
+\CTANdirectory{ssqquote}{macros/latex/contrib/ssqquote}
+\CTANdirectory{stmaryrd}{fonts/stmaryrd}
+\CTANdirectory{sttools}{macros/latex/contrib/sttools}
+\CTANdirectory{stuffit}{tools/stuffit}
+\CTANdirectory{subeqnarray}{macros/latex/contrib/subeqnarray}
+\CTANdirectory{subfig}{macros/latex/contrib/subfig}
+\CTANdirectory{subfiles}{macros/latex/contrib/subfiles}
+\CTANdirectory{sueterlin}{fonts/gothic/sueterlin}
+\CTANdirectory{supertabular}{macros/latex/contrib/supertabular}
+\CTANdirectory{svn}{macros/latex/contrib/svn}
+\CTANdirectory{svninfo}{macros/latex/contrib/svninfo}
+\CTANdirectory{swebib}{biblio/bibtex/contrib/swebib}
+\CTANdirectory{swedish}{language/swedish}
+\CTANdirectory{sweet-tex}{systems/mac/sweet-tex}
+\CTANdirectory{swetex}{language/swedish/swetex}
+\CTANdirectory{swiftex}{support/emacs-modes/swiftex}
+\CTANdirectory*{symbols}{info/symbols/comprehensive}
+\CTANdirectory{syriac}{fonts/syriac}
+\CTANdirectory{t1tidy}{fonts/utilities/t1tools/t1tidy}
+\CTANdirectory{t1tools}{fonts/utilities/t1tools}
+\CTANdirectory{t1utils}{fonts/utilities/t1utils}
+\CTANdirectory{tabulary}{macros/latex/contrib/tabulary}
+\CTANdirectory{talk}{macros/latex/contrib/talk}
+\CTANdirectory{tamil}{language/tamil}
+\CTANdirectory{tar}{tools/tar}
+\CTANdirectory{tbe}{macros/plain/contrib/tbe}
+\CTANdirectory{tcdmanual}{info/tcdmanual}
+\CTANdirectory{tde-macros}{language/swedish/slatex/tde-macros}
+\CTANdirectory{tds}{tds}
+\CTANdirectory{ted}{macros/latex/contrib/ted}
+\CTANdirectory{teencontrex}{info/spanish/TeEncontreX}
+\CTANdirectory{tek2eepic}{support/tek2eepic}
+\CTANdirectory{telugu}{language/telugu}
+\CTANdirectory{tengwar}{fonts/tengwar}
+\CTANdirectory*{testflow}{macros/latex/contrib/IEEEtran/testflow}
+\CTANdirectory*{tetex}{obsolete/systems/unix/teTeX/current/distrib}
+\CTANdirectory{tex--xet}{obsolete/systems/knuth/tex--xet}
+\CTANdirectory{tex-d-l}{digests/tex-d-l}
+\CTANdirectory{tex-implementors}{digests/tex-implementors}
+\CTANdirectory{tex-mag}{digests/tex-mag}
+\CTANdirectory{tex-primer_vms-specific}{info/tex-primer_vms-specific}
+\CTANdirectory{tex-surface}{support/tex-surface}
+\CTANdirectory{tex2mail}{support/tex2mail}
+\CTANdirectory{tex2rtf}{support/tex2rtf}
+\CTANdirectory{tex88}{digests/tex88}
+\CTANdirectory{tex8fmts}{macros/generic/cptex/tex8fmts}
+\CTANdirectory{texbytopic}{info/texbytopic}
+\CTANdirectory{texcalc}{support/texcalc}
+\CTANdirectory{texchord}{macros/generic/texchord}
+\CTANdirectory{texcnvfaq}{help/wp-conv}
+\CTANdirectory{texdraw}{graphics/texdraw}
+\CTANdirectory{texed}{support/texed}
+\CTANdirectory{texfilt}{support/texfilt}
+\CTANdirectory{texgraph}{macros/inrstex/texgraph}
+\CTANdirectory*{texhax}{digests/texhax}
+\CTANdirectory{texi2html}{support/texi2html}
+\CTANdirectory{texi2roff}{support/texi2roff}
+\CTANdirectory{texindex}{indexing/texindex}
+\CTANdirectory{texinfo}{macros/texinfo/texinfo}
+\CTANdirectory{texix}{macros/text1/texix}
+\CTANdirectory{texline}{digests/texline}
+\CTANdirectory*{texlive}{systems/texlive}
+\CTANdirectory*{texmacs}{systems/unix/TeXmacs}
+\CTANdirectory*{texniccenter}{systems/win32/TeXnicCenter}
+\CTANdirectory{texpert}{systems/msdos/texpert}
+\CTANdirectory{texpower}{macros/latex/contrib/texpower}
+\CTANdirectory{texproc}{support/texproc}
+\CTANdirectory{texshell}{systems/msdos/texshell}
+\CTANdirectory{texsis}{macros/texsis}
+\CTANdirectory{text1}{macros/text1}
+\CTANdirectory{text2dvi}{systems/msdos/text2dvi}
+\CTANdirectory{textcase}{macros/latex/contrib/textcase}
+\CTANdirectory{textfit}{macros/latex/contrib/textfit}
+\CTANdirectory{textmerg}{macros/latex/contrib/textmerg}
+\CTANdirectory{textpos}{macros/latex/contrib/textpos}
+\CTANdirectory{textool}{dviware/textool}
+\CTANdirectory{textures}{systems/mac/textures}
+\CTANdirectory{textures_figs}{systems/mac/textures_figs}
+\CTANdirectory{texutils}{systems/atari/texutils}
+\CTANdirectory{texware}{systems/knuth/dist/texware}
+\CTANdirectory{tgrind}{support/tgrind}
+\CTANdirectory{thai}{fonts/thai}
+\CTANdirectory{tib}{biblio/tib}
+\CTANdirectory{tie}{web/tie}
+\CTANdirectory{tiff}{graphics/tiff}
+\CTANdirectory{tiny_c2l}{support/tiny_c2l}
+\CTANdirectory{tip}{info/examples/tip}
+\CTANdirectory{titlesec}{macros/latex/contrib/titlesec}
+\CTANdirectory{titling}{macros/latex/contrib/titling}
+\CTANdirectory{tlc2}{info/examples/tlc2}
+\CTANdirectory{tmmath}{fonts/micropress/tmmath}
+\CTANdirectory{tocbibind}{macros/latex/contrib/tocbibind}
+\CTANdirectory{tocloft}{macros/latex/contrib/tocloft}
+\CTANdirectory{tocvsec2}{macros/latex/contrib/tocvsec2}
+\CTANdirectory{totpages}{macros/latex/contrib/totpages}
+\CTANdirectory{tr2latex}{support/tr2latex}
+\CTANdirectory{transfig}{graphics/transfig}
+\CTANdirectory{translit}{support/translit}
+\CTANdirectory{transname}{tools/macunpack/transname}
+\CTANdirectory{tree}{graphics/tree}
+\CTANdirectory{troff}{indexing/makeindex/troff}
+\CTANdirectory{tsipa}{fonts/tsipa}
+\CTANdirectory{tspell}{support/tspell}
+\CTANdirectory{tt2001}{fonts/ps-type1/tt2001}
+\CTANdirectory{ttn}{digests/ttn}
+\CTANdirectory{tug}{usergrps/tug}
+\CTANdirectory{tugboat}{digests/tugboat}
+\CTANdirectory{turing}{web/spiderweb/src/turing}
+\CTANdirectory{turing+}{web/spiderweb/src/turing+}
+\CTANdirectory{turkish}{language/turkish}
+\CTANdirectory{twcal}{fonts/twcal}
+\CTANdirectory{tweb}{web/tweb}
+\CTANdirectory{tx1}{systems/msdos/tx1}
+\CTANdirectory{txfonts}{fonts/txfonts}
+\CTANdirectory{txtdist}{support/txt}
+\CTANdirectory{type1cm}{macros/latex/contrib/type1cm}
+\CTANdirectory{typingtex}{language/typingtex}
+\CTANdirectory{ucthesis}{macros/latex/contrib/ucthesis}
+\CTANdirectory{ugaritic}{fonts/ugaritic}
+\CTANdirectory{uktex}{digests/uktex}
+\CTANdirectory{uktug}{usergrps/uktug}
+\CTANdirectory{faq}{help/uk-tex-faq}
+\CTANdirectory{umddvi}{dviware/umddvi}
+\CTANdirectory{umlaute}{macros/latex/contrib/umlaute}
+\CTANdirectory{umrand}{macros/generic/umrand}
+\CTANdirectory{unadobe}{fonts/utilities/unadobe}
+\CTANdirectory{unarj}{tools/unarj}
+\CTANdirectory{uncompressing}{fonts/utilities/mf2ps/mf2ps/uncompressing}
+\CTANdirectory{undump}{obsolete/support/undump}
+\CTANdirectory{unix}{systems/unix}
+\CTANdirectory{unpack}{tools/macunpack/unpack}
+\CTANdirectory{unpacked}{macros/latex/unpacked}
+\CTANdirectory{unstuff}{tools/unstuff}
+\CTANdirectory{untex}{support/untex}
+\CTANdirectory{urlbst}{biblio/bibtex/contrib/urlbst}
+\CTANdirectory{urw}{fonts/urw}
+\CTANdirectory{user-guides}{macros/generic/diagrams/borceux/user-guides}
+\CTANdirectory{usergrps}{usergrps}
+\CTANdirectory{usl}{fonts/thai/usl}
+\CTANdirectory{utopia}{fonts/utopia}
+\CTANdirectory{utthesis}{macros/latex/contrib/utthesis}
+\CTANdirectory{uue}{tools/uue}
+\CTANdirectory{uuencode}{tools/uuencode}
+\CTANdirectory{va}{fonts/va}
+\CTANdirectory{vc}{support/vc}
+\CTANdirectory{vector}{macros/latex/contrib/vector}
+\CTANdirectory{vertex}{macros/plain/contrib/vertex}
+\CTANdirectory{vga2mf}{systems/msdos/vga2mf}
+\CTANdirectory{vietnamese}{language/vietnamese}
+\CTANdirectory{vispeech}{language/vispeech}
+\CTANdirectory{vita}{macros/latex/contrib/vita}
+\CTANdirectory{vm-cms}{obsolete/systems/vm-cms}
+\CTANdirectory{vmargin}{macros/latex/contrib/vmargin}
+\CTANdirectory{vmspell}{support/vmspell}
+\CTANdirectory{vplutils}{fonts/utilities/vplutils}
+\CTANdirectory{vrb}{macros/generic/vrb}
+\CTANdirectory{vslitex}{fonts/vf-files/vslitex}
+\CTANdirectory{vtex-common}{systems/vtex/common}
+\CTANdirectory{vtex-linux}{systems/vtex/linux}
+\CTANdirectory{vtex-os2}{systems/vtex/os2}
+\CTANdirectory{vtree}{tools/vtree}
+\CTANdirectory{vtree-fix}{tools/vtree-fix}
+\CTANdirectory{vutex}{dviware/vutex}
+\CTANdirectory{vvcode}{tools/vvcode}
+\CTANdirectory{w2latex}{support/w2latex}
+\CTANdirectory{wallpaper}{macros/latex/contrib/wallpaper}
+\CTANdirectory{was}{macros/latex/contrib/was}
+\CTANdirectory{wasy2}{fonts/wasy2}
+\CTANdirectory{wasysym}{macros/latex/contrib/wasysym}
+\CTANdirectory{wd2latex}{support/wd2latex}
+\CTANdirectory{web}{systems/knuth/dist/web}
+\CTANdirectory{webtoc}{support/makeprog/webtoc}
+\CTANdirectory{whatstex}{info/whatstex}
+\CTANdirectory{williams}{macros/latex/contrib/williams}
+\CTANdirectory{fptex}{obsolete/systems/win32/fptex}
+\CTANdirectory*{winedt}{systems/win32/winedt}
+\CTANdirectory{winw2ltx}{support/winw2ltx}
+\CTANdirectory{word2tex}{support/word2tex}
+\CTANdirectory{word_tex}{support/word_tex}
+\CTANdirectory{wordcount}{macros/latex/contrib/wordcount}
+\CTANdirectory{wp2latex}{support/wp2latex}
+\CTANdirectory{wrapfig}{macros/latex/contrib/wrapfig}
+\CTANdirectory{wsuipa}{fonts/wsuipa}
+\CTANdirectory{xargs}{macros/latex/contrib/xargs}
+\CTANdirectory{xbibfile}{biblio/bibtex/utils/xbibfile}
+\CTANdirectory{xbin}{tools/xbin}
+\CTANdirectory{xcolor}{macros/latex/contrib/xcolor}
+\CTANdirectory{xdvi}{dviware/xdvi}
+\CTANdirectory{xetal}{support/xetal}
+\CTANdirectory{xettex}{language/xettex}
+\CTANdirectory{xfig}{graphics/xfig}
+\CTANdirectory*{xindy}{support/xindy}
+\CTANdirectory{xkeyval}{macros/latex/contrib/xkeyval}
+\CTANdirectory{xmltex}{macros/xmltex/base}
+\CTANdirectory*{xpdf}{support/xpdf}
+\CTANdirectory{xtab}{macros/latex/contrib/xtab}
+\CTANdirectory{xypic}{macros/generic/diagrams/xypic}
+\CTANdirectory{yhmath-fonts}{fonts/yhmath}
+\CTANdirectory{yhmath-macros}{macros/latex/contrib/yhmath}
+\CTANdirectory{zefonts}{fonts/zefonts}
+\CTANdirectory{ziffer}{macros/latex/contrib/ziffer}
+\CTANdirectory{zoon-mp-eg}{info/metapost/examples}
+\endinput
+
+%%% Local Variables: 
+%%% mode: plain-tex
+%%% TeX-master: "faqbody"
+%%% End: 
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.cls b/Master/texmf-dist/doc/generic/FAQ-en/faq.cls
new file mode 100644
index 00000000000..a5ae3cdf54e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty
new file mode 100644
index 00000000000..e9acef465a4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty
@@ -0,0 +1,1150 @@
+% This is a LaTeX2e package for the UKTUG FAQ document.
+%
+% 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{lmodern}% for sans fonts
+        \RequirePackage{mathptmx}
+        \RequirePackage[T1]{fontenc}%
+        \RequirePackage{textcomp}%
+        \boldmathavailfalse
+        \RequirePackage[scaled=0.85]{luximono}% not using cmtt-alike
+        \RequirePackage{textcomp}%
+        \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
+
+%
+% 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}
+  \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\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}
+%
+% 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}
+\DeclareRobustCommand\MP{Meta\-Post}
+\let\textlogo\textmd
+%
+% get texnames package (as amended)
+%\RequirePackage{stupid_names}
+% define substitutes for stupid_names
+\newcommand\LaTeXo{\LaTeX\,2.09}
+\newcommand\AMSTeX{AMS\TeX}
+\newcommand\AMSLaTeX{AMS\LaTeX}
+\newcommand\BibTeX{Bib\TeX}
+\newcommand\PiCTeX{PiC\TeX}
+\newcommand\texlive{\TeX{} Live}
+%
+% ifthenelse for the undefined references
+\RequirePackage{ifthen}
+%
+% tables are all long'uns
+\RequirePackage{booktabs}
+%
+% we define conditional stuff using Eijkhout's package
+\RequirePackage{comment}
+\excludecomment{htmlversion}
+\ifpdf
+  \includecomment{pdfversion}
+  \excludecomment{dviversion}
+  \includecomment{wideversion}
+  \excludecomment{narrowversion}
+\else
+  \excludecomment{pdfversion}
+  \includecomment{dviversion}
+  \includecomment{narrowversion}
+  \excludecomment{wideversion}
+\fi
+%
+% 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
+\else
+  \let\narrowonly\@firstofone
+  \let\wideonly\@gobble
+\fi
+%
+% 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\miktex{MiKTeX}
+\providecommand\xetex{XeTeX}
+\providecommand\plaintex{Plain \TeX{}}
+%
+%% \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}
+\newcommand\ExTeX{Ex\TeX}
+\newcommand\NTS{NTS}
+\newcommand\PDFTeX{PDF\TeX}
+\newcommand\LuaTeX{Lua\TeX}
+%\newcommand\TeXXeT{TeX-{}-XeT}
+
+\newcommand\AllTeX{(La)\TeX}
+\newcommand\CONTeXT{Con\TeX{}t}
+\newcommand\PDFLaTeX{PDF\LaTeX}
+\renewcommand\LaTeX{La\TeX}
+\newcommand\twee{2e}
+%
+% 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
+}
+%%\else
+%%  \DeclareUrlCommand\@ProgName{\def\UrlFont{\rmfamily\itshape}}
+%%  \DeclareRobustCommand\ProgName{\@ProgName}
+%%\fi
+\let\Package\ProgName                                      % pro tem
+\let\Class\Package                                         % ...
+\let\FontName\Package                                      % ...
+
+% 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}%
+}}
+\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}%
+  }}
+\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}%
+}}
+\else
+\let\CTANfile\CTANdirectory
+\fi
+%
+% Make reference to a CTAN package
+%
+% counters for the undefined references and repeated labels
+\newcounter{CTAN@unrefs}
+\newcounter{CTAN@replabs}%
+%
+% the command itself
+\DeclareRobustCommand{\CTANref}[1]{\@ifundefined{ctan-#1}{%
+    \PackageWarning{CTAN}{Undefined reference: #1}%
+    \stepcounter{CTAN@unrefs}%
+}{%
+    \csname ctan-#1\endcsname
+}}
+%
+% 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://www.tex.ac.uk/tex-archive/##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}
+      \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}}
+%
+% 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
+}
+%
+% \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;
+%     so far only "one mandatory" and "one optional, one mandatory"
+%     are supported by texfaq2html
+%
+% 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...
+\def\environment#1{\texttt{#1}}
+\def\pkgoption#1{\texttt{#1}}
+\def\extension#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/Master/texmf-dist/doc/generic/FAQ-en/faqbody.tex b/Master/texmf-dist/doc/generic/FAQ-en/faqbody.tex
new file mode 100644
index 00000000000..1b35a314993
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faqbody.tex
@@ -0,0 +1,24231 @@
+\def\faqfileversion{3.18}    \def\faqfiledate{2008-06-20}
+%
+% 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}
+
+\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 the actual typesetting issues are mostly
+covered from the viewpoint of a \LaTeX{} user.
+
+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 for printing on
+  \CTANhref{faq-a4}{A4 paper} or on % ! line break
+  \CTANhref{faq-letter}{North American ``letter'' paper}, or
+\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
+\item via Scott Pakin's \CTANhref{visualFAQ}{Visual FAQ}.
+\end{itemize}
+
+\begin{htmlversion}
+% pseudo-subsection here, because of limitations of latex->html translator
+\textbf{Caveat: Acquiring files}
+
+Most answers in this \acro{FAQ} provide links for downloading
+software; a large proportion of these links direct you to entire
+directories on the \acro{CTAN} archives.  Unfortunately, some browsers
+issue a sequence of commands that causes \acro{CTAN} servers to deny
+the existence of compressed archive files of the directory, that the
+server would be happy to create ``on the fly''.  The \acro{FAQ}
+therefore offers three possible links for downloading directories
+(that aren't already designated ``browse only''): the links give you
+\extension{zip} and \extension{tar.gz} archives, and a link for browsing
+the directory.
+
+Fortunately, \acro{CTAN} is switching to statically-generated
+directory archive files; many directories mentioned in this \acro{FAQ}
+will also exist as \extension{zip} files on the archives, and won't fall
+foul of the browser problem.  Of course, if the \extension{zip} file
+does not exist, and the browser is playing up, you will need to use
+the ``browse'' link.
+\end{htmlversion}
+
+\htmlignore
+\subsection*{Finding the Files}
+
+Unless otherwise specified, all files mentioned in this \acro{FAQ} are
+available from a \acro{CTAN} archive, or from one of their mirrors.
+\Qref[Question]{}{Q-archives} % this one doesn't need anchor text
+gives details of the \acro{CTAN} archives, and how to retrieve files from
+them.  If you don't have access to the Internet, the
+\Qref*{\texlive{} distribution}{Q-CD} offers off-line snapshots of
+the archives.
+
+The reader should also note that the first directory name of the path
+name of every file on \acro{CTAN} has been elided from what follows, for the
+simple reason that it's always the same (\path{tex-archive/}).
+
+To avoid confusion, we've also elided 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!
+\endhtmlignore
+
+\latexhtml{\subsection*{Origins}}{\textbf{Origins}}
+
+The \acro{FAQ} was originated by the Committee of the \acro{UK} \TeX{}
+Users' Group (\acro{UK}~\acro{TUG}) 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.
+
+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}:
+Donald Arseneau,
+Rosemary Bailey, % lots of initial set of maths answers
+Barbara Beeton, % one of first reviewers outside cttee
+Karl Berry,
+Giuseppe Bilotta,
+Charles Cameron,
+Damian Cugley,
+Michael Dewey,
+Michael Downes, % (RIP) on (ams)maths stuff
+Jean-Pierre Drucbert, % corrected my interpretation of minitoc
+Michael Ernst, % alert on confusing colloquialism
+Thomas Esser,
+Ulrike Fischer, % spotted boondoggle in q-tabcellalign
+                % args like \section improvement; general typos
+Anthony Goreham,
+Norman Gray,
+Eitan Gurari, % comparative html translators
+William Hammond, % lots of work on xml-related answers
+John Harper, % patient help with q-robust ;-)
+John Hammond, % corrections to q-protect
+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
+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
+David Kraus, % help with tocbibind (spotted embarrassing typo  :-} )
+Ryszard Kubiak, % comment about q-driver
+Simon Law,
+Daniel Luecking,
+Aditya Mahajan, % rewrite of q-context
+Sanjoy Mahajan,
+Andreas Matthias,
+Brooks Moses, % editorial suggestion
+Iain Murray, % alternative solution in q-hyperdupdest
+Vilar Camara Neto, % explain breakurl pkg, suggest use of numprint
+Dick Nickalls, % now a member of the committee
+Ted Nieland,
+Hans Nordhaug,
+Pat Rau,
+Heiko Oberdiek,
+Piet van Oostrum,
+Scott Pakin,
+Oren Patashnik,
+Steve Peter, % comprehensive review, lots of typos etc
+Sebastian Rahtz, % without whom there would be no...
+Philip Ratcliffe, % help with a bibtex oddity
+Chris Rowley, % founding father
+Jos\'e Carlos Santos, % very assiduous reader of new versions
+Walter Schmidt,
+Hans-Peter Schr\"ocker,
+Joachim Schrod,
+Maarten Sneep, % summary of c.t.t thread for outszwrng, inter alia
+Axel Sommerfeldt, % suggested rewrite of q-hyperdupdest
+James Szinger, % who responded on c.t.t to request for answer
+Ulrik Vieth,
+Mike Vulis,
+Chris Walker, % revtex alert, ite suggestion (q-labelfig)
+Peter Wilson, % several, incl functionality of memoir
+Rick Zaccone and
+Reinhard Zierke.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{The Background}
+
+\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-books}) that it is
+%% beware line wrap
+``\emph{intended for the creation of beautiful books~--- and especially for books that contain a lot of mathematics}''.
+
+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's 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.
+
+\TeX{} is a macro processor, and offers its users a powerful
+programming capability.  For this reason, \TeX{} on its own is a
+pretty difficult beast to deal with, so Knuth provided a package of
+macros for use with \TeX{} called \plaintex{}; \plaintex{} is
+effectively the minimum set of macros one can usefully employ with
+\TeX{}, together with some demonstration versions of higher-level
+commands (the latter are better regarded as models than used as-is).
+When people say they're ``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 details the rasters 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 than is
+\TeX{} macro-writing.  The complete \TeX{}-user nevertheless needs to
+be aware of \MF{}, and to be able to run \MF{} to generate personal
+copies of Meta-fonts that come her way.
+
+\Question[Q-MP]{What is \MP{}?}
+
+The \MP{} system (by John Hobby) implements a picture-drawing language
+very much like that of \MF{} except that it outputs Encapsulated \PS{}
+files instead of run-length-encoded bitmaps.  \MP{} is a powerful
+language for producing figures for documents to be printed on \PS{}
+printers, either directly or embedded in \AllTeX{} documents. It
+includes facilities for directly integrating \TeX{} text and
+mathematics with 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 \CONTeXT{}~--- 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{narrowversion} % really non-hyper
+  subscribe via the \acro{TUG} \ProgName{mailman} interface at
+  \URL{http://lists.tug.org/metapost}
+\end{narrowversion}
+\begin{wideversion} % really hyper
+  subscribe via the % ! line break
+  \href{http://lists.tug.org/metapost}{\acro{TUG} \ProgName{mailman} interface}.
+\end{wideversion}
+The \acro{TUG} website also hosts a % ! line break
+\href{http://tug.org/metapost.html}{\MP{} summary page}.
+
+\Question[Q-triptrap]{How can I be sure it's really \TeX{}?}
+
+\TeX{} (and \MF{} and \MP{}) are written in a
+\begin{narrowversion} % really "non-hyper"
+  `literate' programming language called Web (\Qref{}{Q-lit})
+\end{narrowversion}
+\begin{wideversion}
+  \Qref{`literate' programming}{Q-lit} language called Web
+\end{wideversion}
+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{}
+(\texttt{trip}) and \MF{} (\texttt{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 \texttt{trip} test, or an
+implementation of \MF{} has passed its \texttt{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; \texttt{trip} and \texttt{trap} don't actually test any
+for real world problems.
+
+
+\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 could
+  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-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}
+
+\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.
+
+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.
+
+\Question[Q-whatpdftex]{What is \PDFTeX{}?}
+
+\PDFTeX{} has entered the main stream of \TeX{} distributions: most
+\LaTeX{} and \CONTeXT{} users nowadays use \PDFTeX{} whether they know
+it or not (more precisely, they use an amalgam of \PDFTeX{} and
+\Qref*{\eTeX{}}{Q-etex}).  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{wideversion}
+  \Qref{optimising line breaks}{Q-overfull}),
+\end{wideversion}
+\begin{narrowversion}
+  % ( <- dummy for paren balancing
+  optimising line breaks~--- \Qref{}{Q-overfull}),
+\end{narrowversion}
+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 (in essence) stopped: the brave new world
+is to be \Qref*{\LuaTeX{}}{Q-luatex}.
+
+\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{}.
+
+\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 bitter 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{}).
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeX{} guides and news]\CTANref{latexdoc}
+\end{ctanrefs}
+
+
+\nothtml{\begingroup\ifboldmathavail\boldmath\fi}
+\Question[Q-latexpronounce]{How should I pronounce ``\LaTeX{}(\twee{})''?}
+\nothtml{\afterquestion}
+
+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.
+
+The `epsilon' in `\LaTeXe{}' is supposed to be suggestive of a small
+improvement over the old \LaTeXo{}.  Nevertheless, most people
+pronounce the name as `\LaTeX{}-two-ee'.
+
+\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
+brain power.
+
+The arguments around this topic can provoke huge amounts of noise and
+heat, without offering much by way of light; your best bet is to find
+out what those around you are using, and to go with the crowd.  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{}?}
+
+\LaTeX{} is a program written in the programming language \TeX{}.  (In
+the same sense, any \LaTeX{} document is also a program, which is
+designed to run `alongside', or `inside' \LaTeX{}, whichever metaphor
+you prefer.)
+
+\plaintex{} is also a program written in the programming language
+\TeX{}.
+
+Both exist because writing your documents in `raw' \TeX{} would
+involve much reinventing of wheels for every document.  They both
+serve as convenient aids to make document writing more pleasant:
+\LaTeX{} is a far more extensive aid.
+
+\LaTeX{} is close to being a superset of \plaintex{}.  Many documents
+designed for \plaintex{} will work with \LaTeX{} with no more than
+minor modifications (though some will require substantial work).
+
+Interpretation of any \AllTeX{} program involves some data-driven
+elements, and \LaTeX{} has a wider range of such elements than does
+\plaintex{}.  As a result, the mapping from \LaTeX{} to \plaintex{}
+is far less clear than that in the other direction~--- see a later
+answer about \Qref*{translating to \plaintex{}}{Q-LaTeXtoPlain}.
+
+\Question[Q-context]{What is \CONTeXT{}?}
+
+\href{http://www.pragma-ade.com/}{\CONTeXT{}} is a macro package
+developed by Hans Hagen of Pragma-Ade.  \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 the users to specify formatting commands in English,
+Dutch, German, French, or Italian, and to use different typesetting
+engines (\PDFTeX{}, Xe\TeX{}, Aleph, and soon \LuaTeX{}) without
+changing the user interface. \CONTeXT{} is developed rapidly, often in
+response to requests from the user community.
+
+%%% RF's original version
+%% developed by Hans Hagen, originally to
+%% serve the needs of his (Dutch) firm Pragma.  It was designed with the
+%% same general-purpose aims as \LaTeX{}, but (being younger) reflects
+%% much more recent thinking about the structure of markup, etc.  In
+%% particular, \CONTeXT{} can customise its markup to an
+%% author's language (customising modules for Dutch, English and German
+%% are provided, at present).
+%%
+%% \CONTeXT{} is well integrated, in all of its structure,
+%% with the needs of hypertext markup, and in particular with the
+%% facilities offered by \Qref*{\PDFTeX{}}{Q-whatpdftex}.
+%% The default installation employs a version of \PDFTeX{} built with the
+%% \Qref*{\eTeX{} extensions}{Q-etex}, which allows further flexibility.
+
+\CONTeXT{} doesn't yet have quite such a large developer community as
+does \LaTeX{}, but those developers who are active seem to have
+prodigious energy.  Support is available via a % ! line break
+\href{http://contextgarden.net}{\acro{WIKI} site} and via the
+\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context}
+\end{ctanrefs}
+
+\nothtml{\begingroup\ifboldmathavail\boldmath\fi}
+\Question[Q-AMSpkg]{What are the \acro{AMS} packages (\AMSTeX{}, \emph{etc}.)?}
+\nothtml{\afterquestion}
+
+\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-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 asked to submit papers to
+the \acro{AMS} in \LaTeX{}, and so the \acro{AMS} developed
+\AMSLaTeX{}, which 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 users to use \AMSLaTeX{} instead.
+\checked{RAB}{1994/11/12} % edited by RF; input from Michael Downes, too
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\AMSTeX{} distribution]\CTANref{amstex}
+\item[\nothtml{\rmfamily}\AMSLaTeX{} distribution]\CTANref{amslatex}
+\end{ctanrefs}
+
+\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 \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''.  Such canned 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 are out
+of luck.
+
+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{} are not aware of
+any generally available macro packages that do not force their
+typographic style on an author, and yet provide such 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, 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}
+
+\Question[Q-lollipop]{What is Lollipop?}
+
+Lollipop is a macro package written by Victor Eijkhout; it was used in
+the production of his book ``\emph{\TeX{} by Topic}'' (see
+\Qref[question]{\AllTeX{} Tutorials}{Q-ol-books}).  The manual says of
+it:
+\begin{quote}
+  Lollipop is `\TeX{} made easy'. Lollipop is a macro package that
+  functions as a toolbox for writing \TeX{} macros.  It was my
+  intention to make macro writing so easy that implementing a fully
+  new layout in \TeX{} would become a matter of less than an hour for
+  an average document, and that it would be a task that could be
+  accomplished by someone with only a very basic training in \TeX{}
+  programming.
+
+  Lollipop is an attempt to make structured text formatting available
+  for environments where previously only \WYSIWYG{} packages could be
+  used because adapting the layout is so much more easy with them than
+  with traditional \TeX{} macro packages.
+\end{quote}
+
+The manual goes on to talk of ambitions to ``capture some of the
+\LaTeX{} market share''; it's a very witty package, but little sign of
+\htmlignore
+it taking over from \LaTeX{} is detectable\dots{}\@
+\endhtmlignore
+\begin{htmlversion}
+it taking over from \LaTeX{} is detectable\dots{}
+\end{htmlversion}
+An article about Lollipop appeared in \TUGboat{} 13(3).
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Lollipop distribution]\CTANref{lollipop}
+\end{ctanrefs}
+
+\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-whyfree]{If \TeX{} is so good, how come it's free?}
+
+It's free because Knuth chose to make it so.  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 (`Copyleft'), \TeX{} itself is not subject to Copyleft.
+
+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}.
+
+\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.141592).  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~\ensuremath{e}, and currently stands at 2.71828.)
+
+Knuth explains his decision, and exhorts us all to respect it, in a
+paper originally published in \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{}.  For the even longer term, there
+are various projects to build a \emph{successor} to \TeX{}; see, for example,
+the
+\begin{narrowversion}
+  \LuaTeX{}, Omega/Aleph and \ExTeX{} projects (questions
+\end{narrowversion}
+\Qref[\nothtml]{\LuaTeX}{Q-luatex},
+\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} and
+\Qref[\nothtml]{\ExTeX{}}{Q-extex}\narrowonly{).}
+\begin{wideversion}
+  projects.
+\end{wideversion}
+
+\Question[Q-readtex]{Reading \AllTeX{} files}
+
+So you've been sent a \TeX{} file: what are you going to do with it?
+
+You can, of course, ``just read it'', since it's a plain text file,
+but the markup tags in the document may prove distracting.  Most of
+the time, even \TeX{} experts will typeset a \TeX{} file before
+attempting to read it.
+
+So, you need to typeset the document.  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''.
+
+\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.  However, 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{}.
+
+A celebrated early system offering ``\WYSIWYG{} using \TeX{}'' came from the
+Vor\TeX{} project: a pair of (early) 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).  Modern systems that are similar in
+their approach are Lightning Textures (an extension of
+Blue Sky's original \TeX{} system for the Macintosh), and Scientific
+Word (which can also cooperate with a computer algebra system); both
+these systems are \Qref*{commercially available}{Q-commercial}.
+
+The issue has of recent years started to attract attention from \TeX{}
+developers, and several interesting projects addressing the
+``\Qref*{\TeX{} document preparation environment}{Q-WYGexpts}''
+are in progress.
+
+Nevertheless, 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.
+
+\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 slowly (subject to copyright issues, etc.\@)
+making their way to the site, too.
+
+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
+\htmlignore
+\ifpdf
+\href{http://www.tug.org/twg.html}{Technical Working Groups (\acro{TWG}s)}.
+\else
+Technical Working Groups (\acro{TWG}s: see
+\URL{http://www.tug.org/twg.html}).
+\fi
+\endhtmlignore
+\begin{htmlversion}
+\href{http://www.tug.org/twg.html}{Technical Working Groups (\acro{TWG}s)}.
+\end{htmlversion}
+
+\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
+\htmlignore
+\ifpdf
+\href{http://www.tug.org/lugs.html}{``Local User Groups'' (\acro{LUG}s)}.
+\else
+``local user groups'' (\acro{LUG}s: see
+\URL{http://www.tug.org/lugs.html}).
+\fi
+\endhtmlignore
+\begin{htmlversion}
+\href{http://www.tug.org/lugs.html}{``local user groups'' (\acro{LUG}s)}.
+\end{htmlversion}
+
+Contact \acro{TUG} itself via:
+\begin{quote}
+  \TeX{} Users Group\\
+  1466 NW Front Avenue, Suite 3141\\
+  Portland, OR 97209\\
+  \acro{USA}\\[.25\baselineskip]
+  Tel: +1 503-223-9994\\
+  Fax: +1 503-223-3960\\
+  Email: \mailto{tug@mail.tug.org}\\
+  Web: \URL{http://www.tug.org/}
+\end{quote}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Documentation and Help}
+
+\Question[Q-books]{Books on \TeX{} and its relations}
+
+While Knuth's book is the definitive reference for \TeX{}, there are
+other books covering \TeX{}:
+\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})
+\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 brackets 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)
+\htmlignore
+\item[\TeX{}: Starting from \sqfbox{1}\,\footnotemark]%
+\footnotetext{That's `Starting from Square One'}%
+\endhtmlignore
+\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}
+For \LaTeX{}, see:
+\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[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})
+\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}
+%% 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 is available from:
+  \URL{http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html}
+\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)
+\end{booklist}
+A sample of George Gr\"atzer's ``Math into \LaTeX{}'', in Adobe
+Acrobat format, and example files
+%for von Bechtolsheim's ``\TeX{} in Practice'', 
+for the three \LaTeX{} Companions, and for
+Gr\"atzer's ``First Steps in \LaTeX{}'', are all available on
+\acro{CTAN}.
+
+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}''.
+
+
+This list only covers books in English: notices of new books, or
+warnings that books are now out of print are always welcome.  However,
+this \acro{FAQ} does \emph{not} carry reviews of current published material.
+\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}
+
+\Question[Q-typebooks]{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.
+
+\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}
+
+\Question[Q-gethelp]{How to get help}
+
+So you've looked at all relevant \Qref*{\acro{FAQ}s}{Q-whereFAQ} you
+can find, you've looked in any \Qref*{books}{Q-books} you have, and
+scanned relevant \Qref*{tutorials}{Q-tutorials*}\dots{} and still you
+don't know what to do.
+
+If you are seeking a particular package or program, look on your own
+system first: you might already have it~--- the better \TeX{}
+distributions contain a wide range of supporting material.  The
+\acro{CTAN} Catalogue can also help: you can
+\href{http://www.tex.ac.uk/search}{search it}, or you can browse it
+% !!!! line break
+``\href{http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html}{by topic}''.
+A catalogue entry has a brief description of the package, and links to
+any 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.
+
+Failing all that, look to see if anyone else has had the problem
+before; there are two places where people ask: browse or search the
+newsgroup \Newsgroup{comp.text.tex} via
+\href{http://groups.google.com/group/comp.text.tex}{Google groups},
+and the mailing list \texttt{texhax} via its
+\href{http://tug.org/pipermail/texhax/}{archive}
+
+If those ``back question'' searches fail, you'll have to ask the world
+at large.  To ask a question on \Newsgroup{comp.text.tex}, you can use
+your own news client (if you have one), or use the ``start a new
+topic'' button on \URL{http://groups.google.com/group/comp.text.tex}.
+To ask a question on \texttt{texhax}, you may simply send mail to
+\mailto{texhax@tug.org}, but it's probably better to subscribe to the
+list (via \URL{http://tug.org/mailman/listinfo/texhax}) % ! no ~ on this line
+first~--- not everyone will answer to you as well as to the list.
+
+Do \textbf{not} try mailing the % ! line break
+\Qref*{\LaTeX{} project team}{Q-LaTeX3} or the maintainers of these
+\acro{FAQ}s for help; while both addresses reach experienced \AllTeX{}
+users, no small group can possibly have expertise in every area of
+usage so that the ``big'' lists are a far better bet.
+
+\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} lists; 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 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.
+
+What if your document simply doesn't fail in any of these cut-down
+scenarios?  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 necessary, it could be that it's 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.
+
+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.
+
+\Question[Q-tutorials*]{\AllTeX{} Tutorials, etc.}
+
+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 couple 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 (rather new) 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}.
+
+Finally, we have a set of links to
+\Qref*{Directories of \AllTeX{} information}{Q-doc-dirs}, and details
+of some ``\Qref*{books}{Q-ol-books}'' that were once published
+conventionally, but are now available on-line.
+
+\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{}}
+
+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 also started 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://www.tex.ac.uk/tex-archive/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}.
+
+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.
+
+Chris Harrison's % ! line break
+\href{http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html}{TeX book}
+presents basic \LaTeX{} with useful hints for extensions
+
+Nicola Talbot's % ! line break
+\href{http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/}{\LaTeX{} for complete novices}
+does what it claims: the author teaches \LaTeX{} at the University of
+East Anglia.  That is one of several of Nicola's % ! line break
+\href{http://theoval.cmp.uea.ac.uk/~nlct/latex/}{introductory tutorials},
+which include exercises (with solutions).  Other tutorials include
+those for writing theses/dissertations with \LaTeX{}, and for using
+\LaTeX{} in administrative work.  (The page seems to be an adjunct to
+her \LaTeX{} courses~--- fortunate people, the people of \acro{UEA}!).
+
+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}
+\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]\CTANref{l2tabuen};
+  source also available: \CTANref{l2tabuen.src}
+\end{ctanrefs}
+
+\Question[Q-tutbitslatex]{Specialised \AllTeX{} tutorials}
+
+The \acro{AMS} publishes a ``Short Math Guide for \LaTeX{}'', which is
+available (in several formats) via
+\URL{http://www.ams.org/tex/short-math-guide.html}
+
+Herbert Vo\ss{} is developing a parallel document, that is also very
+useful; it's part of his ``\Qref*{tips and tricks}{Q-doc-dirs}'' and
+a copy is maintained on \acro{CTAN}.
+%\URL{http://www.perce.de/LaTeX/math/Mathmode-TeX.pdf}
+
+Two documents written more than ten years apart about font usage in
+\TeX{} are worth reading: % ! line breaks, next 3 lines
+\href{href='http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf}{Essential NFSS}
+by Sebastian Rahtz, and
+\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}.
+
+Peter Smith's
+\begin{narrowversion}
+  ``\LaTeX{} for Logicians''
+  (\URL{http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/})
+\end{narrowversion}
+\begin{wideversion}
+  % ! line break
+  ``\href{http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/}{\LaTeX{} for Logicians}''
+\end{wideversion}
+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{}'' is an
+excellent introduction to graphics use.  It's available on
+\acro{CTAN}, but the sources aren't available (promised ``some time
+soon'').
+
+Kjell Magne Fauske offers a set of examples of the use of the drawing
+packages % ! line break
+\Qref*{\acro{PGF} and \acro{T}ik\acro{Z}}{Q-drawing}; the % ! line break
+\href{http://www.fauskes.net/pgftikzexamples/}{examples catalogue}
+includes examples (with output) from the package documentation as well
+as code written by the author himself.
+
+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 \TeX{} use appears at least twice on the web:
+Haruhiko Okumura's page on
+% ! 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}).
+
+One ``Tim'' documents p\TeX{} (a \TeX{} system widely used in Japan)
+in his
+\begin{narrowversion}
+  ``English notes on p\TeX{}'' (see
+  \url{http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf}).
+\end{narrowversion}
+\begin{wideversion}
+  % ! line break
+  ``\href{http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf}{English notes on p\TeX{}}''.
+\end{wideversion}
+
+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
+deparment'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{}]the
+  document is available in \PS{} and \acro{PDF} formats as
+  \CTANref{epslatex_ps} and \CTANref{epslatex_pdf} respectively
+\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.
+
+Similarly, there's no completely reliable command-organised reference
+to \LaTeX{}, but the NASA % ! line break
+\href{http://www.giss.nasa.gov/latex/}{Hypertext Help with LaTeX} is
+recently much improved.  It still talks in \LaTeXo{}-isms in places,
+but it's been updated for current \LaTeX{}; there are a number of
+mirrors of the site, and it may be worth choosing a ``local'' one if
+you're going to use it a lot.
+
+\Question[Q-doc-wiki]{WIKI pages for \TeX{} and friends}
+
+The \emph{WIKI} concept can be a boon to everyone, if used sensibly.
+The ``general'' 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
+WIKI under control.
+
+Following the encouraging performance of the % ! line break
+\href{http://contextgarden.net/}{\CONTeXT{} WIKI}, both a
+\href{http://en.wikibooks.org/wiki/TeX}{(Plain) \TeX{} WIKI} and a
+\href{http://en.wikibooks.org/wiki/LaTeX}{\LaTeX{} WIKI} have been
+established.  Both seem rather sparse, as yet, and the \LaTeX{} WIKI
+contains some suggestions that go counter to established advice (e.g.,
+the \LaTeX{} WIKI has details on the % ! line break
+\Qref*{use of the \environment{eqnarray} environment}{Q-eqnarray});
+however one may hope that both will become useful resources in the
+longer term.
+
+\Question[Q-typo-style]{Typography tutorials}
+
+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-typebooks}, but the document (though it does
+contain its Rutgers-local matter) is a fine introduction to the issues
+of producing readable documents.
+
+Peter Wilson's manual for his \Class{memoir} class 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.
+\begin{ctanrefs}
+\item[memoir \nothtml{\rmfamily}distribution]\CTANref{memoir}
+\end{ctanrefs}
+
+\Question[Q-doc-dirs]{Directories of \AllTeX{} information}
+
+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.in/tutorials.html}\nobreakspace--- the
+set comprises two parts, ``Text'' and ``Graphics'', so far.
+
+Herbert Vo\ss{}'s excellent % beware line break
+\href{http://texnik.de/}{\LaTeX{} tips and tricks} is an excellent
+source of small articles on the use of \LaTeX{}.
+
+\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.
+
+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}
+
+\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.  For example, on many current
+distributions, the \ProgName{texdoc} command often helps, as in: 
+\begin{quote}
+\begin{verbatim}
+texdoc footmisc
+\end{verbatim}
+\end{quote}
+which opens a \acro{DVI} viewer window showing documentation of the
+\Package{footmisc} package.  According to the type of file
+\ProgName{texdoc} finds, it will launch a \acro{DVI} or \PS{} viewer
+or a \acro{PDF} reader.
+
+If \ProgName{texdoc} can't find any documentation, it may launch a Web
+browser to look at its copy of the \acro{CTAN} catalogue.  The
+catalogue has an entry for package documentation, and since the
+\acro{CTAN} team asks authors documentation of their packages (and
+members of the team even occasionally generate documentation that
+seems useful), you will more often than not find documentation that
+way.
+
+If your luck (as defined above) doesn't hold out, you've got to find
+documentation by other means.  This is where you need to exercise your
+intelligence: you have to find the documentation for yourself.  What
+follows 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 (whose documentation, \File{memman}, is widely praised as an
+introduction to typesetting concepts), the \Class{KOMA-script} bundle
+(whose developers take the trouble to produce detailed documentation
+in both German and English), 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.
+
+\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-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, but individual files
+in the 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, which is some help in
+understanding \File{classes.dtx}
+\begin{ctanrefs}
+\item[classes.dtx]\CTANref{latex-classes}
+\item[clsguide.pdf]\CTANref{clsguide}
+\item[ltxguide.cls]\CTANref{ltxguide}
+\item[\nothtml{\rmfamily}\LaTeX{} documentation]\CTANref{latexdoc}
+\item[source2e.tex]\CTANref{latex-source}
+\end{ctanrefs}
+
+\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.
+
+There is also an article on how to run both \MF{} and \MP{} (the
+programs).  Peter Wilson's % !! line break
+\textit{Some Experiences in Running \MF{} and \MP{}}
+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/metapost.htm}{\MP{} page}.
+
+Other \MP{} tutorials that have appeared are two in English by % ! line breaks
+\href{http://remote.science.uva.nl/~heck/Courses/mptut.pdf}{Andr\'e Heck}
+and \href{http://www.tlhiv.org/MetaPost/tutorial/}{Urs Oswald},
+and one in French (listed here because it's clearly enough written
+that even this author understands it), by
+\href{http://pauillac.inria.fr/~cheno/metapost/metapost.pdf}{Laurent Ch\'eno};
+both have been recommended for inclusion in the \acro{FAQ}
+
+Urs Oswald's tutorial is accompanied by a super tool (by Troy
+Henderson) for testing little bits of \MP{}, which is an invaluable
+aid to the learner: \URL{http://www.tlhiv.org/mppreview}
+
+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}
+  (\acro{PDF} format) 
+\item[\nothtml{\rmfamily}Vincent Zoonekynd's examples]\CTANref{zoon-mp-eg}
+\end{ctanrefs}
+
+\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'', contained in the file \File{btxdoc.tex},
+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]{TeX-related books}{Q-books} for details of both
+books.)
+
+The document ``Designing \BibTeX{} Styles'', contained in the file
+\File{btxhak.tex}, explains the postfix stack-based language used to
+write \BibTeX{} styles (\File{.bst} files). The file \File{btxbst.doc}
+is the template for the four standard styles (\Package{plain},
+\Package{abbrv}, \Package{alpha}, and \Package{unsrt}). It also
+contains their documentation.  The complete \BibTeX{} documentation
+set (including all the files above) is available on \acro{CTAN}.
+
+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}
+(\File{btxFAQ}), by Michael Shell and David Hoadley, is also to be
+recommended.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\BibTeX{} documentation]\CTANref{bibtex-doc}
+\item[\nothtml{\rmfamily}\BibTeX{} documentation, in \acro{PDF}]%
+  \CTANref{bibtex-doc-pdf}
+\item[btxFAQ.pdf]\CTANref{bibtex-faq}
+\item[\nothtml{\rmfamily}Tame the BeaST]\CTANref{ttb-pdf}
+\end{ctanrefs}
+
+\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 packages needed to produce them.
+
+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[Symbol List]Browse \CTANref{symbols}; there are processed
+  versions in both \PS{} and \acro{PDF} forms for both A4 and
+  letter paper.
+\end{ctanrefs}
+
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Bits and pieces of \AllTeX{}}
+
+\Question[Q-dvi]{What is a \acro{DVI} file?}
+
+A \acro{DVI} file (that is, a file with the type or extension
+\extension{dvi}) is \TeX{}'s main output file, using \TeX{} in its
+broadest sense to include \LaTeX{}, etc.  `\acro{DVI}' is supposed to
+be an acronym for \acro{D}e\acro{V}ice-\acro{I}ndependent, meaning
+that the file can be printed on most
+kinds of typographic output device.  The \acro{DVI} file is designed to be
+read by a driver (\Qref{DVI drivers}{Q-driver}) to produce
+further output designed specifically for a particular printer (e.g., a
+LaserJet) or to be used as input to a previewer for display on a
+computer screen.  \acro{DVI} files use \TeX{}'s internal coding; a \TeX{}
+input file should produce the same \acro{DVI} file regardless of which
+implementation of \TeX{} is used to produce it.
+
+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 
+possibly material to be introduced by means of
+\Qref*{\csx{special} commands}{Q-specials}.
+
+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).
+\begin{ctanrefs}
+\item[dvitype]\CTANref{dvitype}
+\end{ctanrefs}
+
+\Question[Q-driver]{What is a \acro{DVI} driver?}
+
+A \acro{DVI} driver is a program that takes as input a \acro{DVI} file
+(\Qref{\acro{DVI} files}{Q-dvi})  and
+(usually) produces a file that can be sent to a typographic
+output device (which we will call a printer, for short), or to another
+format.
+
+A driver will usually be specific to a particular printer,
+although any \PS{} printer ought to be able to print
+the output from a \PS{} driver.
+% (these are also called \PS{} conversion programs).
+
+As well as the \acro{DVI} file, the driver 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 the printer itself `has'.
+Each driver will expect the font information in
+a particular form.  For more information on the forms of fonts,
+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}.
+
+\Question[Q-pk]{What are \acro{PK} files?}
+
+\acro{PK} files (packed raster) contain font bitmaps.  The output
+from \Qref*{\MF{}}{Q-useMF} includes a generic font (\acro{GF}) file
+and the utility \ProgName{gftopk} produces the \acro{PK} file from
+that.  There are a lot of \acro{PK} files, as one is needed for each
+font, that is each magnification (size) of each design (point) size
+for each weight for 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.  In a
+modern \TeX{} distribution, files are arranged according to the \TeX{}
+directory structure \Qref*{\acro{TDS}}{Q-tds}, which has provision for
+all this variety.
+
+\Question[Q-tfm]{What are \acro{TFM} files?}
+
+\acro{TFM} stands 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 \acro{PK} files.  \TeX{} (\LaTeX{}, etc.\@)
+itself needs only to 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.
+
+\Question[Q-virtualfonts]{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 other glyphs,
+rules and other ``basic'' typesetting commands, and the positioning
+information that specifies how everything comes together.
+
+Things that match the concept of virtual fonts for \TeX{} were first
+implemented by David Fuchs in the very early days.  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 article in \textsl{TUGboat} at the time, and 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. The entities you
+define in a virtual font look like characters to \TeX{} (they appear
+with their sizes in a \acro{TFM} file), but the \acro{DVI} processor may
+expand them to something quite different.
+
+From the virtual font file, the \acro{DVI} processor learns
+details of what is in the virtual font, so as to know ``what to draw,
+where''.   The virtual font may contain commands:
+\begin{itemize}
+\item just to remap the glyphs of a single font,
+\item to make a composite font with glyphs drawn from several
+  different fonts, or
+\item to build up an effect in arbitrarily complicated ways (since a
+  virtual font may contain anything which is legal in a \acro{DVI}
+  file).
+\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 both sets of
+information. The \ProgName{vptovf} program is then used to the 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 of the manual method, the
+commonest way (nowadays) of generating \acro{VPL} files is to use the
+\ProgName{fontinst} package, which is described in 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}
+
+\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} provides rather different facilities in \PDFTeX{}
+operation: since there is no device driver around, in this context.
+In \PDFTeX{}, \csx{special} is only needed to generated \acro{PDF} for
+which there is no existing defined \PDFTeX{} operation.
+
+\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), 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)~--- things such as \TeX{}'s
+\csx{accent} primitive interrupt hyphenation.
+
+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 participatory sport).
+
+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
+languages, a \Qref*{partial reinstallation}{Q-newlang} is necessary.
+
+\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}.
+
+\Question[Q-clsvpkg]{What are \LaTeX{} classes and packages?}
+
+Current \LaTeX{} makes a distinction between the macros that define the
+overall layout of a document, and the macros that tweak that layout
+(to one extent or another) to provide what the author \emph{really}
+wants.
+
+The distinction was not very clear in \LaTeXo{}, and after some
+discussion (in the later stages of development of current \LaTeX{})
+the names ``class'' and ``package'' were applied to the two concepts.
+
+The idea is that a document's \emph{class} tells \LaTeX{} what sort of
+document it's dealing with, while the \emph{packages} the document
+loads ``refine'' that overall specification.
+
+On the disc, the files only appear different by virtue of their name
+``extension''~--- class files are called \texttt{*.cls} while package
+files are called \texttt{*.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{footmisc} package (which
+refines \Class{article}'s definition of footnotes) is represented on
+disc by a file called \File{footmisc.sty}.
+
+The user defines the class of his document with the
+\csx{documentclass} command (typically the first command in a
+document), and loads packages with the \csx{usepackage} command.  A
+document may have several \csx{usepackage} commands, but it may have
+only one \csx{documentclass} command.  (Note that there are
+programming-interface versions of both commands, since a class may
+choose to load another class to refine its capabilities, and both
+classes and packages may choose to load other packages.)
+
+\Question[Q-dtx]{Documented \LaTeX{} sources (\extension{dtx} files)}
+
+\LaTeXe{}, and most contributed macro packages, are now written in a
+\Qref*{literate programming style}{Q-lit}, with source and
+documentation in the
+same file.  This format, known as `doc', 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 file (\extension{ins}) is normally provided,
+to automate this process of removing comments for speed of loading.
+To read the comments, you can run \LaTeX{} on the
+\extension{dtx} file to produce a nicely formatted version of the
+documented code.  Several
+packages can be included in one \extension{dtx} file (they're sorted
+out by the \extension{ins} file), with conditional
+sections, and there are facilities for indexes of macros, etc.
+
+Anyone can write \extension{dtx} files; the format is explained in
+\Qref*{The \LaTeX{} Companion}{Q-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}.
+
+Another useful way of generating \extension{dtx} files 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 \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{narrowversion}
+  \MF{} and \MP{} (\Qref[see questions]{}{Q-MF} and \Qref[\nothtml]{}{Q-MP})
+\end{narrowversion}
+\begin{wideversion}
+  \Qref{\MF{}}{Q-MF} and \Qref{\MP{}}{Q-MP},
+\end{wideversion}
+thus permitting documented distribution of bundles containing code for
+\MF{} and \MP{} together with related \LaTeX{} code.
+\begin{ctanrefs}
+\item[clsguide.pdf]\CTANref{clsguide}
+\item[docmfp.sty]\CTANref{docmfp}
+\item[docstrip.tex]Part of the \LaTeX{} distribution
+\item[DTX tutorial]\CTANref{dtxtut}
+\item[makedtx]\CTANref{makedtx}
+\end{ctanrefs}
+
+\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 the input encoding to
+something regular.  Nowadays, 
+the operating system translates keystrokes into a code appropriate for
+the user's language: the encoding used is often a national or
+international standard, though many operating systems use ``code
+pages'' defined by Microsoft.  These standards and code pages often
+contain characters that can't 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 consists of 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 excuses 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, but the Cork
+fonts have them.  Even Cork's coverage isn't complete: it misses
+letters from Romanian, Eastern and Northern Sami, and Welsh, at
+least.  The Cork encoding does contain ``\acro{NG}'' glyphs that
+allows it to support Southern Sami.)  \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 only \MF{}-fonts that conform to the Cork encoding are the
+\acro{EC} fonts.  They look \acro{CM}-like, though their metrics
+differ from \acro{CM}-font metrics in several areas.  The fonts are
+now regarded as `stable' (in the same sense that the \acro{CM} fonts
+are stable: their metrics are unlikely ever to change).  Their serious
+disadvantages for the casual user are their size (each \acro{EC} font
+is roughly twice the size of the corresponding \acro{CM} font), and
+there are far more of them than there are \acro{CM} fonts.  The simple
+number of fonts has acted as a disincentive to the production of Adobe
+Type~1 versions of the fonts, but several commercial suppliers offer
+\acro{EC} or
+\acro{EC}-equivalent fonts in type~1 or TrueType form~--- see
+% beware line fill
+\Qref[question]{commercial suppliers}{Q-commercial}.  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 \MF{} sources), are available.
+
+%% Unfortunately, until corresponding fonts for mathematics are produced,
+%% the \acro{CM} fonts must be retained, since some mathematical symbols
+%% are drawn from text fonts in the \acro{CM} encodings.
+Note that the Cork encoding doesn't cover mathematics (and neither do
+``\acro{T}1-encoded'' font families, of course).  If you're using
+Computer-Modern-alike fonts, this doesn't actually matter: your system
+will have the original Computer Modern fonts, 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 viewed as
+`stable' in the same way as are the \acro{EC} fonts are.
+
+The Cork encoding is also implemented by virtual fonts provided in the
+\Qref*{\acro{PSNFSS} system}{Q-usepsfont},
+for Adobe Type~1 fonts, and also by the \Package{txfonts} and
+\Package{pxfonts} font packages
+% beware line wrap
+(see \Qref[question]{``choice of scalable fonts''}{Q-psfchoice}).
+\begin{ctanrefs}
+\item[CM-super fonts]\CTANref{cm-super}
+\item[CM-LGC fonts]\CTANref{cm-lgc}
+\item[EC and TC fonts]\CTANref{ec}
+\item[Latin Modern fonts]\CTANref{lm}
+\end{ctanrefs}
+
+\Question[Q-tds]{What is the \acro{TDS}?}
+
+    \acro{TDS} stands for the \TeX{} Directory Structure, which is a standard
+way of organising all the \TeX{}-related files on a computer system. 
+
+    Most modern distributions conform to the \acro{TDS}, which
+provides for both a `standard' and a (set of) `local' hierarchies of
+directories containing \TeX{}-related files. The
+\acro{TDS} reserves the name \texttt{texmf} as the name of the root directory
+(folder) of the hierarchies.  Files supplied as part of the
+distribution are put into the standard hierarchy. The location of the
+standard hierarchy is system dependent, but on a Unix system it might
+be at 
+\path{/usr/local/texmf}, or
+\path{/usr/local/share/texmf}, or
+\path{/opt/texmf}, or
+a similar location, but in each case the \TeX{} files will be under the 
+\path{/texmf} subdirectory. 
+
+There may be more than on `local' hierarchy in which additional files
+can be stored. In the extreme an installation can have a local
+hierarchy and each user can also have an individual local hierarchy. The
+location of any local hierarchy is not only system dependent but also user
+dependent. Again, though, all files should be put under a local \path{/texmf}
+directory.
+
+The \acro{TDS} is published as the output of a \acro{TUG} % beware line wrap
+\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 (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 has many advantages are somewhat ahead of the
+\TeX{} world's mainstream (at time of writing).
+
+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 this was 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.
+
+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 letter to the font ``foundry'', two to the
+typeface name, one to the weight, 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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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).
+
+\begin{narrowversion} % non-hyper
+  The \acro{CTAN} sites are in Germany, the UK and the USA; the
+  directory layout is the same on each of the sites, starting from a
+  tree root of \path{tex-archive/} The sites are
+  \texttt{dante.ctan.org} (Dante, Germany), \texttt{cam.ctan.org}
+  (Cambridge, UK) and \texttt{tug.ctan.org} (TUG, USA).
+\end{narrowversion}
+\begin{wideversion} % hyper
+  The \acro{CTAN} sites are
+  \href{ftp://dante.ctan.org/tex-archive}{Dante (Germany)},
+  \href{ftp://cam.ctan.org/tex-archive}{Cambridge (UK)} and
+  \href{ftp://tug.ctan.org/tex-archive}{TUG (USA)}; the links are to
+  the root of the \acro{CTAN} tree, above which the layout is
+  identical at each site.
+\end{wideversion}
+
+The \TeX{} files at each \acro{CTAN} node may also be accessed via
+the Web at \acro{URL}s \URL{http://www.dante.de/tex-archive},
+\URL{http://www.tex.ac.uk/tex-archive} and
+\URL{http://www.ctan.org/tex-archive} respectively, but not all
+\acro{CTAN} mirrors are Web-accessible.
+
+As a matter of course, to reduce network load,
+please use the \acro{CTAN} site
+or mirror closest to you.  A complete and current list of \acro{CTAN} sites
+and known mirrors is available as file \CTANref{CTAN-sites} on the
+archives themselves.
+
+Better still, the script behind \URL{http://mirror.ctan.org/} will
+cunningly choose a ``nearby'' mirror for you, using information from
+the database `behind' \CTANref{CTAN-sites}; at present it uses
+\texttt{ftp} protocol for transfers, but the intention is to convert
+it to using \texttt{http} (web) protocol in the near future.
+
+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~--- note that the
+\File{tex-archive} part of the \acro{CTAN} path isn't needed.
+
+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}.
+
+\Question[Q-tds-zip]{Prebuilt 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-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).  Everyone hopes that the extra work involved will
+contrinute to happier lives for package users, which in turn must
+surely help keep the TeX community lively and active.
+
+Use of the files is discussed in % ! line break
+``\Qref*{installing using preformatted \acro{ZIP} files}{Q-inst-tds-zip}''.
+
+\Question[Q-nonfree]{What's 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 is now obvious to the team that the project would never
+be 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.)
+
+In the light of the above, the \texttt{nonfree} tree is being
+dismantled, and its contents moved to the main \acro{CTAN} tree.  So
+the answer to the question is, now, ``the nonfree tree is a part of
+\acro{CTAN}, and is now being merged with the main tree''.
+
+
+% The \acro{CTAN} archives are currently restructuring their holdings
+% so that files that are `not free' are held in a separate tree.  The
+% definition of what is `free' (for this purpose) is influenced by, but
+% not exactly the same as the 
+% \begin{narrowversion} % really non-hyper version
+%   Debian Free Software Guidelines (\acro{DFSG}: see
+%   \URL{http://www.debian.org/social_contract#guidelines}).
+% \end{narrowversion}
+% \begin{wideversion}
+% % don't let the line wrap...
+% \href{http://www.debian.org/social_contract#guidelines}{Debian Free Software Guidelines (\acro{DFSG})}.
+% \end{wideversion}
+
+% Material is placed on the \texttt{nonfree} tree if it is not
+% freely-usable (e.g., if the material is shareware, commercial, or if
+% its usage is not permitted in certain domains at all, or without
+% payment).  Users of the archive should check that they are entitled to
+% use material they have retrieved from the \texttt{nonfree} tree.
+
+% The Catalogue (one of the prime sources for finding \TeX{}-related
+% material via \nothtml{web search~--- }%
+% \Qref{web search}{Q-findfiles}) lists the licence details in each
+% entry in its lists.
+% For details of the licence categories, see its % !line break
+% \href{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of licences}.
+
+\Question[Q-uploads]{Contributing a file to the archives}
+
+You have something to submit to the archive~--- great!  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://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of ``standard'' licence statements}.
+\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); 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}
+
+If you are able to use anonymous \ProgName{ftp}, you can upload that
+way.  The file \File{README.uploads} on \acro{CTAN} tells you
+where to upload, what to upload, and how to notify the \acro{CTAN}
+management about what you want doing with your upload.
+
+You may also upload via the Web: each of the principal \acro{CTAN}
+sites offers an upload page~--- choose from
+\URL{http://www.ctan.org/upload.html},
+\URL{http://www.dante.de/CTAN/upload.html} or
+\URL{http://www.tex.ac.uk/upload.html}; the pages lead you through the
+process, showing you the information you need to supply.  This method
+enforces 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} (or
+\extension{tar.bz2}).
+
+If you can use neither of these methods, or if you find something
+confusing, ask advice of the
+\begin{narrowversion} % really non-hyper version
+  \acro{CTAN} management (\mailto{ctan@dante.de}):
+\end{narrowversion}
+\begin{wideversion}
+  \href{mailto:ctan@dante.de}{\acro{CTAN} management}:
+\end{wideversion}
+if the worst comes to the worst, it may be possible to mail a
+contribution.  This really is a last-resort route: none of the
+\acro{CTAN} sites is anyone's regular workstation, so if you mail to
+one of the maintainers, that maintainer then has to upload to
+\acro{CTAN}.
+  
+If it's appropriate (if your package is large, or regularly updated),
+the \acro{CTAN} management can arrange to \ProgName{mirror} your
+contribution direct into the archive.  At present this may only be
+done if your contribution is available via \ProgName{ftp}, and of
+course the directory structure on your repository must `fit'.
+\begin{ctanrefs}
+\item[README.uploads]\CTANref{CTAN-uploads}
+\end{ctanrefs}
+
+\Question[Q-findfiles]{Finding \AllTeX{} files}
+
+Modern \TeX{} distributions contain a huge array of support files of
+various sorts, 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?
+
+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, the \acro{CTAN} sites provide searching facilities, via the web.
+The simplest search, locating files by name, is to be found on the
+Dante \acro{CTAN}
+at \URL{http://www.dante.de/cgi-bin/ctan-index}; the script scans a
+list of files (\File{FILES.byname}~--- see below) and returns a list
+of matches, arranged very neatly as a series of links to directories
+and to individual files.
+
+The \href{http://www.tex.ac.uk/search}{\acro{UK}} and
+\href{http://www.ctan.org/search.html}{\acro{USA}} \acro{CTAN}s offer a
+search page that provides
+\begin{itemize}
+\item a file-name search similar to the Dante machine's (above);
+\item a keyword search of the archive catalogue (see below): this is a
+  pretty powerful tool: the results include links to the catalogue
+  ``short descriptions'', so you can assure yourself that the package
+  you've found is the one you want; and
+\item a search form that allows you to use \ProgName{Google} to search
+  \acro{CTAN}.
+\end{itemize}
+
+An alternative way to scan the catalogue is to use the catalogue's
+% ! line break
+\href{http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html}{``by topic'' index};
+this lists a series of topics, and \AllTeX{} projects that are worth
+considering if you're working on matters related to the topic.  
+
+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}.  If you're using
+\ProgName{Google}, you can restrict your 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 (perhaps using
+\ProgName{rsync}) makes good sense.
+\begin{ctanrefs}
+\item[FILES.byname]\CTANref{f-byname}
+\item[FILES.last07days]\CTANref{f-last7}
+\end{ctanrefs}
+
+\Question[Q-findfont]{Finding new fonts}
+
+A comprehensive list of \MF{} fonts used to be posted to
+\Newsgroup{comp.fonts} and to \Newsgroup{comp.text.tex}, roughly
+every six weeks, by Lee Quin.
+Nowadays, authors of new material in \MF{} are few and far between
+(and mostly designing highly specialised things with limited appeal to
+ordinary users); as a result, no-one has taken over maintenance of the
+list of fonts.  If you need a font for some esoteric purpose, it may
+be worth \Qref*{searching \acro{CTAN}}{Q-findfiles} using your purpose
+as a search keyword.
+
+Most new fonts that appear are prepared in some scalable outline form
+or other, and a large proportion is distributed under commercial
+terms.  However, once you have acquired such a font, converting it to
+a form usable by your \AllTeX{} distribution is not (in principle) a
+serious problem.
+
+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 here.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\MF{} font list]\CTANref{mf-list}
+\end{ctanrefs}
+
+\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.  Contents of
+the collection are:
+\begin{itemize}
+\item The \texlive{} installation disc (a \acro{CD}) provides \TeX{}
+  systems for use on \acro{GNU}-Linux, MacOS/X and Win-32
+  architectures;
+\item The \texlive{} `Live' disc (a \acro{DVD}) providing \TeX{} for
+  a wider range of architectures;
+\item Mac\TeX{}: an easy to install \TeX{} system for MacOS/X, based
+  on \texlive{}, and including the % ! line break
+  \href{http://www.uoregon.edu/~koch/texshop/}{texshop front-end}
+  and other tools;
+\item Pro\TeX{}t: an easy to install \TeX{} system for Windows, based
+  on \miktex{}, and including an `active' document to guide
+  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.
+
+More details of the collection are available from its own
+\begin{wideversion} % this really ought to be "hyperversion" or summat
+  \href{http://www.tug.org/texcollection/}{web page}
+  on the \acro{TUG} site.
+\end{wideversion}
+\begin{narrowversion} % and non-hyperversion?
+  web page on the
+  \acro{TUG} site \URL{http://www.tug.org/texcollection/}
+\end{narrowversion}
+\begin{ctanrefs}
+\item[Mac\TeX{}]\CTANref{mactex}
+\item[Pro\TeX{}t]\CTANref{protext}
+\item[\TeX{}live install image]\CTANref{texlive}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{\TeX{} Systems}
+
+\Question[Q-TeXsystems]{\AllTeX{} for different machines}
+\keywords{windows,macintosh,macos,ms-dos,os/2,unix,linux}
+
+We list here the free or shareware packages;
+\htmlignore
+see \Qref{}{Q-commercial} for details of commercial packages.
+\endhtmlignore
+\begin{htmlversion}
+  another question addresses
+  \Qref{commercial \TeX{} vendors'}{Q-commercial} products.
+\end{htmlversion}
+\begin{description}
+\item[Unix] The only current distribution of \TeX{} for Unix systems
+  (including \acro{GNU}/Linux and other free Unix-like systems) is
+  \texlive{}, which is distributed as part of the % ! line break
+  \Qref*{\TeX{} collection}{Q-CD}.
+
+  Members of many \TeX{} user groups receive copies of the collection
+  (on \acro{CD} and \acro{DVD}), as part of their membership of the
+  groups.
+
+  MacOS/X is also a Unix-based system; however users should refer to
+  the information below, under item ``Mac''.
+  \begin{ctanrefs}
+  \item[texlive]Browse \CTANref{texlive}
+  \end{ctanrefs}
+\item[Linux] GNU/Linux users are supported by \texlive{} (as noted
+  above).
+
+  A free version of the commercial 
+  \Qref*{V\TeX{} extended \TeX{} system}{Q-commercial} is available
+  for use under Linux, which among other things specialises in direct
+  production of \acro{PDF} from \AllTeX{} input.  Sadly, it's no
+  longer supported, and the ready-built images are made for use with a
+  rather ancient Linux kernel.
+  \begin{ctanrefs}
+  \item[texlive]Browse \CTANref{texlive}
+  \item[vtex]\CTANref{vtex-linux}
+  \item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common}
+  \end{ctanrefs}
+\item[\acro{PC}: Windows post-95]
+  \miktex{}, by Christian Schenk, is a comprehensive distribution.  It has
+  its own previewer, \acro{YAP}, which is itself capable of printing,
+  though the distribution also includes a port of \ProgName{dvips}.
+  The current version is available for file-by-file download (the
+  \acro{HTML} files in the directory offer hints
+  on what you need to get going).  The \miktex{} developers provide a
+  ready-to-run copy of the distribution, on \acro{CD} (for purchase) via the
+  \href{http://www.miktex.org/cd/}{\miktex{} web site}; otherwise the
+  \File{setup} executable is available on \acro{CTAN}, together with
+  all the optional packages.
+  
+  \href{http://tug.org/protext/}{Pro\TeX{}t}, part of the \TeX{}
+  collection by Thomas Feuerstack, is
+  a further option for installing \miktex{}.  It bundles a \miktex{}
+  setup with some further useful utilities, together with a \acro{PDF}
+  file which contains clickable links for the various installation
+  steps, along with explanations.
+
+  Windows users are also supported directly by the \texlive{}
+  distribution; a system is provided on the installation disc of the
+  \TeX{} collection (and it can, with some difficulty, be run ``from
+  the disc'' without installing \emph{anything}).
+
+  \href{http://foundry.supelec.fr/projects/xemtex/}{XEm\TeX{}}, by
+  Fabrice Popineau (he who created the excellent, but now defunct,
+  fp\TeX{} distribution), is an integrated distribution of \TeX{}, \LaTeX{},
+  \CONTeXT{}, \ProgName{XEmacs} and 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.
+
+  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}
+
+  A further (free) option arises from the
+  \href{http://www.cygwin.com}{CygWin bundle}, which presents a
+  Unix-like environment over the Win32 interface; an X-windows server
+  is available.  If you run CygWin on your Windows machine, you have
+  the option of using \texlive{}, too (you will need the X-server, to
+  run \ProgName{xdvi}).  Of course, \texlive{} components will look like
+  Unix applications (of course, that's presumably what you wanted),
+  but \TeX{} under CygWin also reputedly somewhat slower than native
+  Win32 implementations such as \miktex{} or XEm\TeX{}.  The (now
+  obsolete) te\TeX{} distribution is provided as part of the CygWin
+  distribution, and but you can build your own copy of \texlive{} from
+  the current sources.
+
+  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]Acquire \CTANref{miktex-setup} (also available from the
+    \miktex{} web site), and read installation instructions from %
+                                % ! line break
+    \href{http://www.miktex.org/2.5/Setup.aspx}{the \miktex{} installation page}
+  \item[protext.exe]\CTANref{protext}
+  \item[tetex]\CTANref{tetex}
+  \end{ctanrefs}
+\item[\acro{PC}: \MSDOS{} or \acro{OS/}2] Em\TeX{}, by Eberhard Mattes,
+  includes \LaTeX{}, \BibTeX{}, previewers, and drivers, and is
+  available  as a series of zip archives.  Documentation is
+  available in both German and English.  Appropriate memory managers
+  for using em\TeX{} with 386 (and better) processors and under
+  Windows, are included in the distribution.  Em\TeX{} will operate
+  under Windows, but Windows users are better advised to use a
+  distribution tailored for the Windows environment.
+
+  A version of em\TeX{}, packaged to use a
+  % beware 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.  Most users of Microsoft
+  operating systems, who want an up-to-date \AllTeX{} system, need to
+  migrate to Win32-based systems.
+  \begin{ctanrefs}
+  \item[emtex]\CTANref{emtex}
+  \item[emtexTDS]\CTANref{emtextds}
+  \end{ctanrefs}
+\item[\acro{PC}: \MSDOS{}] The most recent \MSDOS{} offering 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 still implements a rather old instance of \AllTeX{}.
+  \begin{ctanrefs}
+  \item[djgpp]\CTANref{djgpp}
+  \end{ctanrefs}
+\item[\acro{PC}: \acro{OS/}2] Em\TeX{}, by Eberhard Mattes (see
+  above), was actually developed under \acro{OS/}2, and lives happily
+  in that environment.
+
+  \acro{OS/}2 users may also use a free version of the
+  commercial \Qref*{V\TeX{}}{Q-commercial}, which specialises
+  in direct production of \acro{PDF} from \AllTeX{} input.  (This
+  version is, like the Linux version, unfortunately no longer supported.)
+  \begin{ctanrefs}
+  \item[emtex]\CTANref{emtex}
+  \item[emtexTDS]\CTANref{emtextds}
+  \item[vtex]\CTANref{vtex-os2}
+  \item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common}
+  \end{ctanrefs}
+%% \item[Windows \acro{NT}, other platforms] Ports of \miktex{} for
+%%   \acro{NT} on Power \acro{PC} and \acro{AXP} are available.  Neither
+%%   version has been updated for version~1.2 (or later) of
+%%   \miktex{}~--- they may not be satisfactory.
+%%   \begin{ctanrefs}
+%%   \item[miktex for AXP]\CTANref{miktex-AXP}
+%%   \item[miktex for Power PC]\CTANref{miktexppc}
+%%   \end{ctanrefs}
+\item[Mac] \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.  (Members of \acro{UK}~\acro{TUG} may
+  acquire the software without further payment, as part of a
+  membership deal.)  Oz\TeX{} does not run, natively, under MacOS/X,
+  but will run with a sufficiently recent CarbonLib (see
+  \URL{http://www.trevorrow.com/oztex/ozosx.html}).
+  Other questions about Oz\TeX{} itself may be directed to
+  \mailto{oztex@midway.uchicago.edu}
+
+  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  includes a port of a version of
+  \Qref*{Omega}{Q-omegaleph}.
+
+  Both Oz\TeX{} and \acro{CM}ac\TeX{} run on either MacOS/X or on a
+  sufficiently recent MacOS with CarbonLib 
+  (v1.3~for Oz\TeX{}, v1.4~for CMac\TeX{}).
+  % beware line wrap
+
+  From its 2005 release, the \Qref*{\texlive{} disc set}{Q-CD}
+  includes Mac\TeX{}.  Details (and a downloadable distribution set)
+  may be found on the % ! line break
+  \href{http://tug.org/mactex}{\acro{TUG} web site}; the distribution
+  is also on \acro{CTAN}.
+
+\begin{narrowversion} % really, non-hyper version
+  A useful resource for Mac users is to be found at
+  \URL{http://www.esm.psu.edu/mac-tex/}; it has a news and `help'
+  section, as well as details of systems and tools.
+\end{narrowversion}
+\begin{wideversion}
+  A useful
+  \href{http://www.esm.psu.edu/mac-tex/}{resource for Mac users}
+  has a news and `help' section, as well as details of systems and
+  tools.
+\end{wideversion}
+  The Mac\TeX{}-on-OSX mailing list is a useful resource for users;
+  mail \mailto{MacOSX-TeX-on@email.esm.psu.edu} to subscribe.
+\begin{ctanrefs}
+  \item[cmactex]\CTANref{cmactex}
+  \item[mactex]\CTANref{mactex}
+  \item[oztex]\CTANref{oztex}
+\end{ctanrefs}
+\item[Open\acro{VMS}] \TeX{} for Open\acro{VMS} is available, though
+  it seems unlikely that the version on \acro{CTAN} is the latest
+  available.  
+  \begin{ctanrefs}
+  \item[OpenVMS]\CTANref{OpenVMSTeX}
+  \end{ctanrefs}
+\item[Atari] \TeX{} for the Atari \acro{ST} is available from \acro{CTAN}.
+  \begin{ctanrefs}
+  \item[Atari TeX]\CTANref{atari}
+  \end{ctanrefs}
+\item[Amiga] Full implementations of \TeX{} 3.1 (Pas\TeX{}) and \MF{}
+  2.7 are available.
+  \begin{ctanrefs}
+  \item[PasTeX]\CTANref{amiga}
+  \end{ctanrefs}
+\item[\acro{TOPS}-20] \TeX{} was originally written on a \acro{DEC}-10
+  under \acro{WAITS},
+  and so was easily ported to \acro{TOPS}-20. A distribution that runs on
+  \acro{TOPS}-20 is available via anonymous \texttt{ftp} from
+  \FTP{ftp.math.utah.edu} in \path{pub/tex/pub/web}
+  \checked{RF}{2001/03/01}
+\end{description}
+
+\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] Try
+  \href{http://www.gnu.org/software/emacs/emacs.html}{\acro{GNU}\nobreakspace\ProgName{emacs}}
+  or \href{http://www.xemacs.org/}{\ProgName{XEmacs}}, and
+  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.
+
+  Many who consider the versions of \ProgName{emacs} spawn of the devil, prefer
+  \href{http://vim.sourceforge.net}{\ProgName{vim}}, a highly configurable
+  editor (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}.  A newer
+  system (by \ProgName{Kile}'s original author),
+  \href{http://www.xm1math.net/texmaker/}{\ProgName{texmaker}} doesn't
+  rely on \acro{KDE}'s facilities, and so may be more easily portable.
+\item[\MSDOS{}] \TeX{}shell is a simple,
+  easily-customisable environment, which can be used with the editor
+  of your choice.
+
+  You can also use \acro{GNU}~\ProgName{emacs} and \acro{AUC}-\TeX{}
+  under \MSDOS{}.
+\item[Windows '9x, NT, etc.]\ProgName{TeXnicCenter} is a (free)
+  \TeX{}-oriented development system, uniting a powerful platform for
+  executing \AllTeX{} and friends with a configurable editor.
+  
+  \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[\acro{OS/}2] \ProgName{epmtex}  offers an \acro{OS/}2-specific shell.
+\item[Macintosh] 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
+  works well with Oz\TeX{}.  From release 2.2.0 (at least), Textures
+  works with MacOS~X.
+
+  For MacOS~X users, the free tool of choice appears to be
+  \href{http://www.uoregon.edu/~koch/texshop/texshop.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.
+\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{wideversion}
+  see ``\Qref{creating a bibliography file}{Q-buildbib}''.
+\end{wideversion}
+\begin{narrowversion}
+  these are discussed in % ! line break
+  ``\Qref*{creating a bibliography file}{Q-buildbib}''.
+\end{narrowversion}
+\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}
+
+\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[\acro{PC}; \YandY{} \TeX{}] ``Bitmap free \TeX{} for Windows.''
+%%   \begin{quote}
+%%     \YandY{}, Inc.\\
+%%     106 Indian Hill, \acro{MA} 01741-1747\\
+%%     \acro{USA}\\[.25\baselineskip]
+%%     Tel: 800-742-4059 (within North America)\\
+%%     Tel: +1 978-371-3286\\
+%%     Fax: +1 978-371-2004\\
+%%     Email: \mailto{sales-help@YandY.com} and
+%%     \nothtml{\\ \hphantom{Email: }}%
+%%     \mailto{tech-help@YandY.com}\\
+%%     Web: \URL{http://www.YandY.com/}
+%%   \end{quote}
+%%   Source: Confirmed with \YandY{}, February 2003
+\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}; V\TeX{}] \acro{DVI}, \acro{PDF} and \acro{HTML}
+  backends, Visual Tools and Type 1 fonts
+  \begin{quote}
+    MicroPress Inc\\
+    68-30 Harrow Street\\
+    Forest Hills, \acro{NY} 11375\\
+    \acro{USA}\\[.25\baselineskip]
+    Tel: +1 718-575-1816\\
+    Fax: +1 718-575-8038\\
+    Email: \mailto{support@micropress-inc.com}\\
+    Web: \URL{http://www.micropress-inc.com/}
+  \end{quote}
+  Source: Mail from MicroPress, Inc., July 1999
+\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 MacOS/X is
+  available \URL{http://www.bluesky.com/news/220b.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/}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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 \ProgName{ghostscript} is \emph{so} good, and
+has \emph{such} a wide range of printer drivers (perhaps this is where
+the \acro{DVI} output driver writers have all gone?).
+
+The general advice, then, is to \Qref*{generate \PS{}}{Q-dvips}, and
+to process that with \ProgName{ghostscript} set to generate the format
+for the printer you actually have.  If you are using a Unix system of
+some sort, it's generally quite easy to insert \ProgName{ghostscript}
+into the print spooling process.
+\begin{ctanrefs}
+\item[ghostscript]Browse \CTANref{ghostscript}
+\end{ctanrefs}
+
+\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 \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}
+
+\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 widely
+used), 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 \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
+very slow, and requires two or three steps) but it has 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.
+
+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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Support Packages for \TeX{}}
+
+\Question[Q-fig]{Fig, a \AllTeX{}-friendly drawing package}
+
+\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.
+
+There's no explicit port of \ProgName{xfig} to windows (although it is
+believed to work under \ProgName{cygwin} with their X-windows system).
+However, the program % ! line break
+\href{http://tech-www.informatik.uni-hamburg.de/applets/javafig/}{\ProgName{jfig}}
+is thought by many to be an acceptable substitute, written in Java.
+\begin{ctanrefs}
+\item[xfig]\CTANref{xfig}
+\item[transfig]\CTANref{transfig}
+\end{ctanrefs}
+
+\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
+\csx{special}s (\Qref{}{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{}}
+
+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.
+
+For Windows, there is a good spell checker incorporated into many of
+the \Qref*{shell/editor}{Q-editors} combinations that are available.
+The spell checker from the (now defunct) 4All\TeX{} shell remains
+available as a separate package, \ProgName{4spell}.
+
+For the Macintosh, \ProgName{Excalibur} is the program of choice.  It
+will run in native mode on both sorts of Macintosh.  The distribution
+comes with dictionaries for several languages.
+
+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}.
+\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[\nothtml{\bgroup\rmfamily}\acro{VMS}\nothtml{\egroup} spell]%
+  \CTANref{vmspell}
+\item[winedt]\CTANref{winedt}
+\end{ctanrefs}
+
+\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{verbatim}
+  detex <filename> | wc -w
+\end{verbatim}
+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).
+\ProgName{Winedt} (see \Qref[question]{editors and shells}{Q-editors})
+provides this functionality direct in the Windows environment.
+
+Simply stripping \AllTeX{} markup isn't entirely reliable, however:
+that markup itself may contribute typeset words, and this could be a
+problem.  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.
+\begin{ctanrefs}
+\item[detex]\CTANref{detex}
+\item[wordcount]\CTANref{wordcount}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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 ``documented \LaTeX{}'' style of programming (\Qref{}{Q-dtx})
+\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}
+
+\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.
+
+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.
+
+\acro{\ProgName{FWEB}}, by John Krommes, is a version for Fortran,
+Ratfor, and \acro{C}. 
+
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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 can't (quite)
+  be recommended as a complete replacement yet.
+\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.  An
+alternative is the \Package{screen} package.
+
+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[screen.sty]\CTANref{screensty}
+\item[tex2mail]\CTANref{tex2mail}
+\item[txt]\CTANref{txtdist}
+\end{ctanrefs}
+
+\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{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[tex4ht]\CTANref{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}; this system seems rather good already, and
+  is still being improved.
+
+  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
+  MS-Word to \LaTeX{} is \ProgName{wd2latex}, which runs on \MSDOS{}.
+  \ProgName{Word2}\emph{\TeX{}} and \emph{\TeX{}}\ProgName{2Word} are 
+  shareware translators from % beware line break
+  \href{http://www.chikrii.com/}{Chikrii Softlab}; users' reports are
+  very positive.
+
+  The excellent \ProgName{tex4ht} will generate OpenOffice \acro{ODT}
+  format, which can be used as an intermediate to producing Word
+  format files.
+
+  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[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}
+
+This can nowadays be done, with a certain amount of clever macro
+programming.  David Carlisle's \Package{xmltex} is the prime example;
+it offers a practical solution to typesetting
+\acro{XML} files.
+
+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.
+\begin{ctanrefs}
+\item[xmltex]\CTANref{xmltex}
+\item[passivetex]\CTANref{passivetex}
+\end{ctanrefs}
+
+\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  \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 \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
+\htmlonly{``}\Qref[question]{converting to and from \AllTeX{}}{Q-fmtconv}\htmlonly{''}.
+
+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[ghostscript]Browse \CTANref{ghostscript}
+\item[xpdf]Browse \CTANref{xpdf}
+\end{ctanrefs}
+
+\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.
+
+Translating a document designed to work with \LaTeX{} into one
+designed to 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 is 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[\latexhtml{\textrm{The}}{The} eplain \nothtml{\rmfamily}system]%
+  \CTANref{eplain}
+\item[\latexhtml{\textrm{`\plaintex{}'}}{\plaintex{}} graphics]%
+  \CTANref{graphics-plain}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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 at the end of each answer):
+\begin{narrowversion}
+  copy that link into a browser,
+\end{narrowversion}
+\begin{wideversion}
+  click on that link,
+\end{wideversion}
+and you can get the file, one way or another.
+
+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}.
+
+Normally, though, you will want \File{foo.sty} but that file 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 te\TeX{} or \texlive{}-based system, 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 te\TeX{} or \texlive{}, 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 -expand-var "\$TEXMFLOCAL"
+\end{verbatim}
+\end{quote}
+the output being the actual path, for example (on the workstation the
+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}.
+
+There are circumstances when 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), the package 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, you should replace the existing copy in the
+  \acro{TEXMF} tree.
+\end{itemize}
+The reason one would put things on a local tree is to avoid their
+disappearance if the system is upgraded (or otherwise re-installed).
+
+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 comes with package version \ensuremath{n+2}.
+\end{itemize}
+In such a situation, you will 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{quote}
+\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}
+\end{quote}
+and for modern systems (those distributed in 2005 or later, using \acro{TDS}
+v1.1 layouts):
+\begin{quote}
+\begin{verbatim}
+.map:  $TEXMF/fonts/map/<syntax>/<bundle>/
+.enc:  $TEXMF/fonts/enc/<syntax>/<bundle>/
+\end{verbatim}
+\end{quote}
+(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}
+\AliasQuestion{Q-inst-miktex}
+
+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{wideversion}
+  \Qref{\miktex{} package management system}{Q-inst-miktex*}
+  can usually help;
+\end{wideversion}
+\begin{narrowversion}
+  \miktex{} package management system can usually help
+  (\Qref{}{Q-inst-miktex*});
+\end{narrowversion}
+\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}
+
+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-tds-zip]{Installing using preformatted \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!).
+
+Preformatted \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 that's 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):
+\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}''
+
+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.
+
+\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{verbatim}
+  export TEXINPUTS=/tmp:
+\end{verbatim}
+while in a Windows system, within a \MSDOS{} window, it would be:
+\begin{verbatim}
+  set TEXINPUTS=C:/temp;
+\end{verbatim}
+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{verbatim}
+kpsewhich -expand-var "\$TEXMFHOME"
+\end{verbatim}
+
+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.
+
+\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}
+
+Metafont fonts are (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.
+
+\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-inst1cm]{Installing the Bluesky versions of the CM~fonts}
+
+This is a specialised case of \Qref*{installing a font}{Q-instfont},
+but it comes easier
+than most, since the font metrics are installed in every \AllTeX{}
+system before you even start.  Indeed, most recent systems will have
+the Type~1 fonts themselves already installed, so that the job is
+already done, and all you need is to start using them:
+so the first thing to do is to just try it.  On a system that uses
+\ProgName{dvips} (most systems nowadays do), try the sequence:
+\begin{verbatim}
+  latex sample2e
+  dvips -Pcmz -Pamz -o sample2e.ps sample2e
+\end{verbatim}
+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{<cmr10.pfb>} and so on;
+this is \ProgName{dvips} telling you it's including 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 \acro{CTAN} directories listed below contain compressed archives of
+the Type~1 
+files for various architectures, both for the Computer Modern fonts
+and for the \acro{AMS} fonts of mathematical and other useful things.
+Download the archives that are appropriate for your architecture, and
+extract the files~--- you only actually need the contents of the
+\File{pfb} directories, since you already have the fonts
+installed in the ``ordinary'' way, so that the \acro{TFM} files are
+already present.  (You don't need the \PS{} font metric~--- \acro{AFM}
+and \acro{PFM}~--- files in any case.)
+
+The files should go into your local \texttt{texmf} tree (\File{texmf.local},
+\File{texmf-local}, \File{localtexmf}, or whatever).  Create
+directories at offsets \path{fonts/type1/bluesky/cm} and
+\path{fonts/type1/bluesky/ams}, and copy the \extension{pfb} files into them.
+
+Now you need to tell \ProgName{dvips}, \PDFTeX{}, etc., that the fonts
+are available.  This is done by use of a \emph{map file}, which lists
+\emph{font name} (as \TeX{} understands it), \emph{font name} (as it
+appears in the type~1 file itself), and where the program will find
+the file.  Map files are provided in the download bundles for the
+\acro{AMS} fonts; for the \acro{CM} fonts, map files are available
+separately.
+
+The set of map files includes files \texttt{config.*}; each of these contains
+an instruction to load a single map file.  For ordinary use, you
+instruct \ProgName{dvips} to load the ``detailed'' map of the
+\acro{CM} fonts by use of the command:
+\begin{verbatim}
+  dvips -Pcmz myfile
+\end{verbatim}
+The same can be done with the \acro{AMS} fonts, and you may invoke
+both sets of fonts with:
+\begin{verbatim}
+  dvips -Pcmz -Pamz myfile
+\end{verbatim}
+Alternatively, the contents of \File{config.cmz} and \File{config.amz}
+could be combined into a single file, perhaps \File{config.bluesky},
+loaded by the command
+\begin{verbatim}
+  dvips -Pbluesky myfile
+\end{verbatim}
+
+Remember, after all such changes, the % beware line breaks
+\Qref*{file-name database must be refreshed}{Q-inst-wlcf}.
+\begin{ctanrefs}
+\item[AMS fonts]Browse \CTANref{ams-AMStype1}
+\item[CM fonts]Browse \CTANref{bluesky}
+\item[CM font maps]\CTANref{bluesky-maps}
+\end{ctanrefs}
+
+\Question[Q-prept1font]{Preparing a Type~1 font}
+
+The process of installing a Type~1 font set is rather convoluted, but
+it may be separated into a modest set of operations.
+
+The two basic stages are to prepare the font(s) for installation (this
+question) and installing the result (see % ! line break
+\Qref[question]{installing a Type~1 font}{Q-instt1font}).  Each of
+these basic stages
+
+Many fonts are supplied in \AllTeX{} ready form: such fonts need no
+preparation, and may be \Qref*{installed immediately}{Q-instt1font}.
+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.
+
+\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 \texttt{texmf} tree.  All the
+  strictures about installing non-standard things apply here: be sure
+  to put the files in the local tree.  The list gives reasonable
+  destinations for the various files related to a font family \meta{fname}:
+\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}
+  but if you are lucky, you will be starting from a distribution from
+  \acro{CTAN} and can make use of the corresponding
+  \extension{tds.zip} file, and not care about how to place 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.  (You \emph{can} use plain \ProgName{updmap}, but you
+    will be in danger of creating confusion with different map sets
+    for different users thereby.)
+  \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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Fonts}
+
+\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. \MF{}, unlike \TeX{}, requires some
+customisation: each output device for which you will be generating
+fonts needs a mode associated with it. Modes are defined using the
+|mode_def| convention described on page~94 of \emph{The \MF{}book}
+(see \Qref[question]{\TeX{}-related books}{Q-books}). You will need
+a file, which conventionally called \File{local.mf}, containing all the
+|mode_def|s you will be using. If \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 `big
+enough' implementation of \MF{}). Lists of
+settings for various output devices are also published periodically in
+\textsl{TUGboat} (see \Qref[question]{\acro{TUG}}{Q-TUG*}). Now create
+a \texttt{plain} base
+file using \ProgName{inimf}, \texttt{plain.mf}, and \texttt{local.mf}:
+\begin{htmlversion}
+\begin{verbatim}
+   % inimf
+   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{htmlversion}
+\htmlignore
+\par\vspace{\topsep}
+%\begin{tabular}{@{}l@{}l@{}}
+%|% inimf|\\
+%This is METAFONT\dots{}\\{}
+%**|plain|& you type `|plain|'\\{}
+%(output)\\{}
+%*|input local|& you type this\\{}
+%(output)\\{}
+%*|dump|& you type this\\{}
+%Beginning to dump on file plain\dots{}\\{}
+%(output)\\{}
+%\end{tabular}\par
+\begin{list}{}{}\item\relax
+  |% inimf|\\
+  This is METAFONT\dots{}\\{}
+  \fullline{**\texttt{plain}\hss you type `\texttt{plain}'}
+  (\emph{output})\\{}
+  \fullline{*\texttt{input local}\hss you type this}
+  (\emph{output})\\{}
+  \fullline{*\texttt{dump}\hss you type this}
+  Beginning to dump on file plain\dots{}\\{}
+  (\emph{output})
+\end{list}\par
+\endhtmlignore
+This will create a base file named \File{plain.base} (or something
+similar; for example, it will be
+\htmlignore
+\acro{\File{PLAIN.BAS}}
+\endhtmlignore
+\begin{htmlversion}
+  \File{PLAIN.BAS}
+\end{htmlversion}
+on \MSDOS{} systems) which should be moved to the directory containing
+the base files on your system (note that some systems have two or more
+such directories, one for each `size' of \MF{} used).
+
+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 \ProgName{web2c}
+distribution%
+\begin{footnoteenv}
+  The \ProgName{command_name} is symbolically linked to
+  \ProgName{virmf}, and \ProgName{virmf} loads \File{command_name.base}
+\end{footnoteenv})
+this does indeed happen, but we could for instance define a command
+\ProgName{mf} which executes \texttt{virmf \&plain} loading the
+\texttt{plain} base file.
+
+The usual way to create a font with \texttt{plain} \MF{} is to start 
+it 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{verbatim}
+\mode=<mode name>; mag=<magnification>; input <font file name>
+\end{verbatim}
+\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' and
+\MF{} will produce an output file called
+% beware!! -- argument of \File naturally breaks across line end
+\File{<font file name>.2602gf})
+The \texttt{<magnification>} is a floating point number or
+`magstep' (magsteps are defined in \emph{The \MF{}book} and
+\emph{The \TeX{}book}).
+If \texttt{mag=<magnification>} is omitted, then the default
+is 1 (magstep 0).  For example, to generate cmr10 at 12pt for an epson
+printer you would type
+\begin{verbatim}
+  mf \mode=epson; mag=magstep 1; input cmr10
+\end{verbatim}
+Note that under Unix the \texttt{\textbackslash } and \texttt{;}
+characters must usually be quoted or escaped, so this would typically
+look something like
+\begin{verbatim}
+ mf '\mode=epson; mag=magstep 1; input cmr10'
+\end{verbatim}
+
+If you don't have \ProgName{inimf} or 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{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}
+(note the absence of the \texttt{mode\_def} and \texttt{enddef}
+commands), you would type
+\begin{verbatim}
+   mf \smode="ln03"; input cmr10
+\end{verbatim}
+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 mentioned in % beware line break
+\Qref[question]{\MF{} and \MP{} Tutorials}{Q-mfptutorials}.
+\begin{ctanrefs}
+\item[modes.mf]\CTANref{modes-file}
+\end{ctanrefs}
+
+\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}%
+\begin{footnoteenv}
+  Note that the file name may be transmuted by such operating systems
+  as \MSDOS{}, which don't permit long file names
+\end{footnoteenv}
+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.
+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 need to be used, unless there was some sort
+of problem in the \MF{} run, and need not be ordinarily kept.
+
+\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.)
+
+Over the years, there have been 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, justifying the space taken up 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 donated to
+the public domain by their originators \YandY{} and Bluesky Research,
+in association with the \acro{AMS}.  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 common never to need to
+generate bitmap fonts for any purpose other than previewing (see
+% beware of 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 of
+Computer Modern with wider ranges of glyphs to offer.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}BaKoMa fonts]\CTANref{bakoma}
+\item[\nothtml{\rmfamily}Bluesky fonts]Browse \CTANref{bluesky}
+\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}
+
+\subsection{Adobe Type~1 (``\PS{}'') fonts}
+
+\Question[Q-usepsfont]{Using \PS{} fonts with \protect\TeX{}}
+
+In order to use \PS{} fonts, \TeX{} needs
+\emph{metric} (called \acro{TFM}) files. Several sets of metrics 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 almost invariably
+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{}, the best way to get \PS{} fonts into your
+document is to use the \acro{PSNFSS} package maintained by Walter
+Schmidt.  The \LaTeX{}3 project team declare that \acro{PSNFSS} is
+``required'', 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}.
+
+Victor Eijkhout's \Qref*{Lollipop package}{Q-lollipop}
+supports declaration of font families and styles in a similar way to
+\LaTeX{}'s \acro{NFSS}, and so is easy to use with \PS{} fonts.
+
+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[lollipop]\CTANref{lollipop}
+\item[psnfss]\CTANref{psnfss}
+\end{ctanrefs}
+
+\Question[Q-PSpreview]{Previewing files using Type 1 fonts}
+
+Until recently, free \TeX{} previewers have only been capable of
+displaying bitmap \acro{PK} fonts, but current versions of
+\ProgName{xdvi} sport a Type~1 font renderer.
+%% \YandY{}'s commercial
+%% previewer \Qref*{\acro{DVIW}indo}{Q-commercial} has in the past used
+%% \ProgName{Adobe} \ProgName{Type} \ProgName{Manager} to display Type~1
+%% fonts directly and now uses the system-provided font renderer
+%% available in Windows~2000 and~XP.
+
+Other (free) previewers of the current generation offer automatic
+generation of the requisite \acro{PK} files (using \ProgName{gsftopk},
+or similar, behind the scenes).  If your previewer isn't capable of
+this, you have three 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 \ProgName{ghostscript} or \ProgName{ghostscript}-based viewers
+  such as \ProgName{ghostview} or shareware offering \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 \ProgName{ghostscript} fonts) to make
+  \acro{PK} bitmap fonts which your previewer 
+  will understand. This can produce excellent results, also suitable
+  for printing with non-\PS{} devices. Check the legalities of
+  this if you have purchased the fonts.
+\end{itemize}
+\begin{ctanrefs}
+\item[ghostscript]Browse \CTANref{ghostscript}
+\item[ghostview]Browse \CTANref{ghostview}
+\item[gsftopk]\CTANref{gsftopk}
+\item[GSview]Browse \CTANref{gsview}
+\item[ps2pk]\CTANref{ps2pk}
+\item[xdvi]\CTANref{xdvi}
+\end{ctanrefs}
+
+\Question[Q-metrics]{\protect\TeX{} font metric files for \PS{} 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-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.
+A useful alternative is \YandY{}'s ``private'' \acro{LY}1 encoding,
+which is designed to sit well with ``Adobe standard'' encoded fonts.
+Basic support of \acro{LY1} is available on \acro{CTAN}: note that the
+``relation with Adobe's encoding'' means that there are no
+virtual fonts in the \acro{LY}1 world.
+
+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}
+
+\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 scalable outline fonts}
+
+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 you are severely limited 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}
+For mathematics, then, there are relatively few choices (though the list is
+at last growing).  There are several font families available that are
+based on Knuth's original designs, and some that complement other
+commercial text font designs; one set (MicroPress's `informal math')
+stands alone.  ``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](4 entire families\dots{}so far) Paul Pichaureau\\
+  This set so far offers mathematics fonts to match Adobe Utopia, URW
+  Garamond, Bitstream Charter (all of which are separately available,
+  on \acro{CTAN}, in Type~1 format) and Fontsite Garamond
+  (which is a commercial font, available from the % ! line wrap (twice)
+\begin{wideversion}
+  \href{FontSite Web shop}{http://www.fontsite.com/Pages/FFDownloads.html}).
+\end{wideversion}
+\begin{narrowversion}
+  FontSite Web shop, \URL{http://www.fontsite.com/Pages/FFDownloads.html}).
+\end{narrowversion}
+  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} (the paper is a
+  good read, but is set with Bitmap fonts, and can be difficult
+  on-screen in Acrobat reader 5 or earlier).
+\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.
+\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} set for
+  use with \acro{T}1 texts doesn't (yet) offer support for 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 the \acro{URW}
+    replacement used by \ProgName{ghostscript}) with modified plus,
+    equal and slash symbols;
+  \item maths alphabets using \FontName{Palatino};
+  \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.
+\begin{narrowversion} % really non-hyper version
+  Documentation 
+  (\URL{http://www.tex.ac.uk/tex-archive/fonts/pxfonts/doc/pxfontsdocA4.pdf})
+\end{narrowversion}
+\begin{wideversion}
+  \href{http://www.tex.ac.uk/tex-archive/fonts/pxfonts/doc/pxfontsdocA4.pdf}{Documentation}
+\end{wideversion}
+  is readily available.
+
+  The fonts are licensed under the \acro{GPL}; use in published
+  documents is permitted.
+\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}
+    replacement used by \ProgName{ghostscript}) 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 \FontName{Times};
+  \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.
+\begin{narrowversion} % really non-hyper version
+  Documentation
+  (\URL{http://www.tex.ac.uk/tex-archive/fonts/txfonts/doc/txfontsdocA4.pdf})
+\end{narrowversion}
+\begin{wideversion}
+  \href{http://www.tex.ac.uk/tex-archive/fonts/txfonts/doc/txfontsdocA4.pdf}{Documentation}
+\end{wideversion}
+  is readily available.
+
+  The fonts are licensed under the \acro{GPL}; use in published
+  documents is permitted.
+\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
+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).
+
+TrueType remains the ``native'' format for Windows.  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, True\TeX{} can
+also use 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[CM \nothtml{\normalfont}family collection]%
+  Browse \CTANref{cm-AMStype1}
+\item[AMS \nothtml{\normalfont}font collection]%
+  Browse \CTANref{ams-AMStype1}
+\item[Belleek \nothtml{\normalfont}fonts]%
+  \CTANref{belleek}
+\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[hfbright \nothtml{\normalfont}collection]\CTANref{hfbright}
+\item[hvmath \nothtml{\normalfont\itshape}(free bitmapped version)]%
+  \CTANref{hvmath}
+\item[kpfonts \nothtml{\normalfont}family]\CTANref{kpfonts}
+\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[Minion Pro support]\CTANref{minionpro}
+\item[MnSymbol \nothtml{\normalfont}family]\CTANref{mnsymbol}
+\item[pxfonts]\CTANref{pxfonts}
+\item[tmmath \nothtml{\normalfont\itshape}(free bitmapped version)]%
+  \CTANref{tmmath}
+\item[txfonts]\CTANref{txfonts}
+\item[utopia \nothtml{\normalfont}fonts]\CTANref{utopia}
+\end{ctanrefs}
+
+\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), which should be available in any recent \TeX{} distribution.
+
+\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, the default mechanism is
+to use 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}.  Unfortunately, many fonts that
+have appeared recently simply don't come in versions using 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.)
+\begin{ctanrefs}
+\item[ec-plain]\CTANref{ec-plain}
+\item[fontch]\CTANref{fontch}
+\item[font_selection]\CTANref{font_selection}
+\item[ofs]\CTANref{ofs}
+\item[pdcmac]\CTANref{pdcmac}
+\item[plnfss]\CTANref{plnfss}
+\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}, 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{verbatim}
+  updmap --enable Map lm.map
+\end{verbatim}
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Hypertext and \acro{PDF}}
+
+\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 Direct \Qref{\AllTeX{} conversion to \acro{HTML}}{Q-LaTeX2HTML};
+% beware line break
+\item Use \Qref*{\Package{Texinfo}}{Q-texinfo},
+  and use the \ProgName{info} viewer, or convert the \Package{texinfo}
+  to \acro{HTML};
+\item Use Adobe Acrobat, which will preserve your typesetting
+  perfectly
+  \Qref*{Making Acrobat \acro{PDF} documents from \LaTeX{}}{Q-acrobat};
+\item The hyper\TeX{} conventions (standardised \csx{special}
+  commands); there are supporting macro packages for \plaintex{} and
+  \LaTeX{}).
+\end{itemize}
+
+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.
+
+\Question[Q-acrobat]{Making Acrobat \acro{PDF} documents from \AllTeX{}}
+
+There are three general routes to \acro{PDF} output: Adobe's original
+`distillation' route (via \PS{} output), conversion of a
+\acro{DVI} file, and the use of a direct \acro{PDF} generator such as
+\Qref*{\PDFTeX{}}{Q-whatpdftex}) or
+MicroPress's V\TeX{} (which comes both as a % ! line break
+\Qref*{commercial version}{Q-commercial} for Windows PCs, and as a
+\Qref*{`free' version)}{Q-TeXsystems} for \acro{OS}/2 and Linux systems).
+
+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 the appropriate Adobe
+  tools installed) pass the output through the
+  \acro{PDF}writer in place of a printer driver (this route is a dead
+  end: the \acro{PDF}writer cannot create hyperlinks);
+\item process the document in the normal way 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{} or
+  V\TeX{}.  \PDFTeX{} has
+  the advantage of availability for a wide range of platforms, V\TeX{}
+  (available commercially for Windows, or free of charge, but
+  unsupported, for Linux or \acro{OS/}2) has wider graphics
+  capability, dealing with encapsulated \PS{} and some in-line \PS{}.
+\end{itemize}
+
+To translate all the \LaTeX{} cross-referencing into Acrobat
+links, you need a \LaTeX{} package to suitably 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} has \csx{special}
+commands of its 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} \acro{DVI} driver.
+
+While there is no free implementation of all of \ProgName{Adobe}
+\ProgName{Distiller}'s
+functionality, any but the very oldest versions of \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 \ProgName{ghostscript} combined with
+\ProgName{gv}, \ProgName{GSview} (or even the unsupported
+\ProgName{ghostview}) can display and print \acro{PDF} files, as can
+\ProgName{xpdf}.
+
+In many circumstances, \ProgName{Ghostscript} combined with a 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~--- \ProgName{GSview} doesn't make the same
+mistake.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Acrobat Reader]browse
+  \URL{ftp://ftp.adobe.com/pub/adobe/acrobatreader}
+\item[dvipdfm]\CTANref{dvipdfm}
+\item[dvipdfmx]\CTANref{dvipdfmx}
+\item[ghostscript]Browse \CTANref{ghostscript}
+\item[ghostview]Browse \CTANref{ghostview}
+\item[GSview]Browse \CTANref{gsview}
+\item[gv]\CTANref{gv}
+\item[hyper.sty]\CTANref{hyper}
+\item[hyperref.sty]\CTANref{hyperref}
+\end{ctanrefs}
+
+\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 \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 the recently released version~6).
+
+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
+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{verbatim}
+  dvips -Ppdf myfile -o myfile.ps
+\end{verbatim}
+This may produce a warning message about failing to find the
+configuration file:
+\begin{verbatim}
+  dvips: warning: no config file for `pdf'
+\end{verbatim}
+or something similar, or about failing to find a font file:
+\begin{verbatim}
+  dvips: ! Couldn't find header file cmr10.pfb
+\end{verbatim}
+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{verbatim}
+  dvips -Pcmz -Pamz myfile -o myfile.ps
+\end{verbatim}
+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 \ProgName{ghostscript}.
+
+The problem could arise from too old a version of
+\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 it confuses
+\Package{hyperref} since there are pages which seem (to
+\Package{hyperref}) to have the same page number.  Fortunately, there are
+configuration options to make \Package{hyperref} ``do the right
+thing''.
+
+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'.
+  (If the option is set `\texttt{true}'~--- the default~---
+  \Package{hyperref} writes page anchors as the arabic form of the
+  absolute page number, rather than the formatted form.)
+\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-srchpdf]{Searching \acro{PDF} files}
+
+In principle, you can search a \acro{PDF} file: the text of the file
+is available to the viewer, and at least some viewers provide a search
+facility.  (It's not the fastest thing in the world, but it does help
+in some circumstances.)
+
+However, there is a problem: the viewer wants to look at Unicode text,
+but no ordinary \TeX{}-based system deals in Unicode text.
+Fortunately for us Anglophones, this is is hardly ever a problem for
+our text, since even Knuth's ``\acro{OT}1'' encoding matches ASCII (and hence
+the lowest 128 characters of Unicode) for most things printable.
+However, using the inflected characters of Continental European
+languages, or anything that doesn't use a Latin alphabet, there is
+potential for problems, since \TeX{}'s view of what a font is doesn't
+map \acro{PDF}'s and the reader won't understand\dots{}
+
+\dots{} Unless you use the \Package{cmap} package with \PDFLaTeX{},
+that is.  The package will instruct \PDFTeX{} to load character
+maps into your \acro{PDF} for output fonts encoded according to the \acro{T}1
+(Western European Languages), T2A, T2B, or T2C (Cyrillic Languages),
+or T5 (Vietnamese) encodings.  If your document uses such encodings,
+viewers that can search will use the maps to interpret what they find
+in the file.
+
+Unfortunately, the package only works with fonts that are directly
+encoded, such as the \FontName{cm-super} distribution.  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}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Graphics}
+
+\Question[Q-impgraph]{How to import 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.  It can
+also be used (with the help of the \Package{miniltx} ``\LaTeX{}
+emulator'' and the \Package{graphicx.tex} front-end) in documents
+written in \plaintex{}.
+
+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_pdf}; the document is also available
+  in \PS{} format as \CTANref{epslatex_ps}
+\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]\CTANref{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.
+
+A similar 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.)
+
+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
+``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{}'
+\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}.
+\begin{ctanrefs}
+\item[epstopdf]Browse \CTANref{epstopdf}
+\item[epstopdf.sty]Distributed with Heiko Oberdiek's packages
+  \CTANref{oberdiek}
+\item[pdftricks.sty]\CTANref{pdftricks}
+\item[pst-pdf.sty]\CTANref{pst-pdf}
+\item[pstoedit]\CTANref{pstoedit}
+\item[purifyeps]\CTANref{purifyeps}
+\end{ctanrefs}
+
+\Question[Q-dvipdfmgraphics]{Imported graphics in \ProgName{dvipdfm}}
+
+\ProgName{Dvipdfm} 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
+\ProgName{ghostscript} or \ProgName{Acrobat} \ProgName{Distiller}).
+
+\ProgName{Dvipdfm} is a particularly flexible application.  It will
+permit the inclusion of bitmap and \acro{PDF} graphics, as does
+\Qref*{\PDFTeX{}}{Q-pdftexgraphics}, but is also capable of employing
+\ProgName{ghostscript} ``on the fly'' so as to be able to permit the
+inclusion of encapsulated \PS{} (\extension{eps}) files by translating
+them to \acro{PDF}.  In this way, \ProgName{dvipdfm} combines 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}
+However, 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[ebb]Distributed as part of \CTANref{dvipdfm}
+\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 sample, given in the
+\Package{graphics} bundle documentation, is:
+\begin{quote}
+\begin{verbatim}
+\graphicspath{{eps/}{tiff/}}
+\end{verbatim}
+\end{quote}
+however, if the security checks on your \AllTeX{} system allow, the
+path may be anything you choose (rather than strictly relative, like
+those above); note that the trailing ``\texttt{/}'' \emph{is} required.
+
+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 disadvantage of the \csx{graphicspath} method is inefficiency.  The
+package will call \AllTeX{} once for each entry in the list, which is
+itself slows things.  More seriously, \TeX{} remembers the file name,
+thus effectively losing memory, every time it's
+asked to look up a file, so a document that uses a huge number of
+graphical inputs could be embarrassed by lack of memory.
+
+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
+\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}
+
+\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
+\ProgName{ghostscript} (or some other \PS{} previewer).  However,
+the \PS{} `engine' in \ProgName{ghostscript} \emph{doesn'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 regularly confuse sophisticated minds, this can prove
+troublesome.  If you're suffering such problems (the symptom is that
+characters disappear, or are wrongly presented) the only 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 of a jiffy of Knuth's, by
+Dan Luecking.  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]\CTANref{mpsproof}
+\item[mptopdf]Part of \CTANref{pdftex-graphics}
+\end{ctanrefs}
+
+\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{epic}, 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 \Package{pict2e}; this was advertised in % !line break
+  \Qref*{the \LaTeX{} manual}{Q-books}, but didn't appear for nearly
+  ten years after publication of the book!  It removes all the petty
+  niggles 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 \Package{PSTricks}; this gives you access to all the power of
+  \PS{} from \TeX{} itself, by sophisticated use of
+  \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}.
+  \Package{pstricks}' \csx{special}s are
+  by default specific to \ProgName{dvips}, but V\TeX{} (both in its
+  commercial and in its free versions) understands them.  \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, using it with \PDFLaTeX{} is an awful fidget: if you
+  simply want the graphical capabilities, \Package{pgf}, together with
+  its rather pleasing ``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
+  common \LaTeX{} commands that will utilise the graphical
+  capabilities of both \PS{} and \acro{PDF} equally.
+\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{}
+\item \ProgName{Mfpic}; you liked \MF{}, but can't understand the
+  language?  The package makes up \MF{} or \MP{} code for you
+  within using familiar-looking \TeX{} macros.  Not \emph{quite} the
+  full power of \MP{}, but a friendlier interface; of course, 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 Eitan Gurari's \Package{dratex}, which is as powerful as most
+  other \TeX{} drawing packages, but is an entirely new
+  implementation, which is not as hard on memory, is much more
+  readable (and is fully documented).
+\end{itemize}
+\begin{ctanrefs}
+\item[dratex.sty]\CTANref{dratex}
+\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[pstricks]\CTANref{pstricks}
+\item[tikz.sty]Distributed with \CTANref{pgf}
+\end{ctanrefs}
+
+\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).
+
+Labels on graphics produced by all those \emph{other} tools is where
+the \Package{psfrag} package can help.  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{PS text}}{\emph{Repl text}}, which instructs
+the system to replace the original (``\texttt{PS}'') 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{}.  The % ! line break
+\Qref*{\Package{pst-pdf} package}{Q-pdftexgraphics} can support such
+usage.  In fact, the \Package{pst-pdf} support package
+\Package{auto-pst-pdf} offers a configuration setting precisely for
+use with \Package{psfrag}.
+
+On the other hand,
+\begin{narrowversion}
+  V\TeX{}'s GeX processor (\Qref{}{Q-commercial})
+\end{narrowversion}
+\begin{wideversion}
+  \Qref*{V\TeX{}}{Q-commercial}'s GeX processor
+\end{wideversion}
+explicitly deals with \Package{psfrag}, both in its free and
+commercial instances.
+
+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.
+
+\Package{Pstricks} can of course do everything that \Package{overpic}
+can, with all the flexibility of \PS{} programming that it offers
+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[iTe]\CTANref{ite}
+\item[laprint]Distributed with \CTANref{psfragx}
+\item[overpic.sty]\CTANref{overpic}
+\item[psfrag.sty]\CTANref{psfrag}
+\item[psfragx.sty]\CTANref{psfragx}
+\item[pstricks.sty]\CTANref{pstricks}
+\item[pst-pdf.sty]\CTANref{pst-pdf}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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}
+\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 commented form, and there is a description
+of the language (see
+% beware 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 generate it by
+using the facilities of the \Package{custom-bib} bundle.  This
+contains a file \File{makebst.tex}, which runs you through a text menu
+to produce a file of instructions, with which you can generate your
+own \extension{bst} file.  This technique doesn't offer entirely new styles
+of document, but the system's ``master \BibTeX{} styles'' already
+offer significantly more than the \BibTeX{} standard set.
+\begin{ctanrefs}
+\item[\nothtml{\normalfont}\BibTeX{} documentation]\CTANref{bibtex-doc}
+\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 to the way you
+are thinking today.
+
+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 the
+\Package{url} or \Package{hyperref} package 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
+\nothtml{``creating a \BibTeX{} file'' (\Qref[question]{}{Q-buildbib}).}
+\begin{htmlversion}
+``\Qref[question]{creating a \BibTeX{} file}{Q-buildbib}''.
+\end{htmlversion}
+
+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 in the step 1.  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.
+\begin{ctanrefs}
+\item[chapterbib.sty]\CTANref{cite}
+\item[bibunits.sty]\CTANref{bibunits}
+\end{ctanrefs}
+
+\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.
+\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}
+\end{ctanrefs}
+
+\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 \texttt{numbers} and \texttt{sort\&compress} options, will
+do the same when working with its own numeric bibliography styles
+(\File{plainnat.bst} and \File{unsrtnat.bst}).
+
+If you might need to make hyperreferences to your citations,
+\Package{cite} isn't adequate.  If you add the \Package{hypernat}
+package:
+\begin{verbatim}
+  \usepackage[...]{hyperref}
+  \usepackage[numbers,sort&compress]{natbib}
+  \usepackage{hypernat}
+  ...
+  \bibliographystyle{plainnat}
+\end{verbatim}
+the \Package{natbib} and \Package{hyperref} packages will interwork.
+\begin{ctanrefs}
+\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}
+
+\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}
+package deals with the problem.
+
+The package 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.
+
+Unfortunately, the \Class{revtex} system doesn't play with
+\Package{mcite}.  As a result, for that (primarily physics-targeted
+system) you need to play silly games like:
+\begin{quote}
+\begin{verbatim}
+\cite{paper0,paper1,paper3}
+\nocite{paper2}
+\end{verbatim}
+\end{quote}
+and then edit the \extension{bbl} file to merge the two citations, to
+achieve the effects of \Package{mcite}.
+\begin{ctanrefs}
+\item[mcite.sty]\CTANref{mcite}
+\item[revtex \nothtml{\rmfamily}bundle]\CTANref{revtex}
+\end{ctanrefs}
+
+\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.  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.
+
+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[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\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.  The simplest 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[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}
+
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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, are
+comprehensive in their coverage of significant typesetting issues,
+produce good-looking output and are well documented in both English
+and German (\Package{scrguien} in the distribution for English,
+\Package{scrguide} for German).
+
+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 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 (relatively new) \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
+hopes users will contribute their own styles, based on
+\Package{greybars}.)
+
+\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{}, V\TeX{} \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[seminar.cls]\CTANref{seminar}
+\item[pgf.sty]\CTANref{pgf}
+\item[powerdot.cls]\CTANref{powerdot}
+\item[pp4]\CTANref{ppower4}
+\item[ppr-prv.sty]\CTANref{ppr-prv}
+\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://theoval.cmp.uea.ac.uk/~nlct/jpgfdraw/}{JpgfDraw}, which
+allows you to construct the outline of frames for use with
+\Package{flowfram}.
+
+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,
+  \href{http://nxg.me.uk/docs/posters/}{Producing posters using \LaTeX{}};
+\item from Nicola Talbot, % ! line break
+  \href{http://theoval.sys.uea.ac.uk/~nlct/latex/posters/index.html}{Creating technical posters with \LaTeX{}}
+\item from ``\emph{awf}'' and ``\emph{capes}'' % ! line break
+  \href{http://www.robots.ox.ac.uk/~awf/latex-posters/}{Preparing conference posters in \LaTeX{}}
+  (the page discusses a sample, which you can download);
+\item From Rob Clark % ! line break
+  \href{http://homepages.inf.ed.ac.uk/robert/posters/advanced.html}{Advanced LaTeX Posters}
+  (which has links to code samples);
+\item from Brian Wolven,
+  \URL{http://fuse.pha.jhu.edu/~wolven/posters.html} (this page also
+  provides macros and other support suggestions); and
+\item from ``\emph{pjh}'' % ! line break
+  \href{http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html}{Making and printing a poster with \LaTeX{}},
+  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[flowfram.sty]\CTANref{flowfram}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}
+\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-spacing, you may care to refer to
+\Qref[question]{the relevant question}{Q-linespace}.
+If you want to write your own, a good place to start is the University
+of California style, but it's not worth going to a lot of trouble. (If
+officials won't allow standard typographic conventions, you won't be
+able to produce an \ae{}sthetically pleasing document anyway!)
+\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 wrap
+\Qref[question]{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.
+
+\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.  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.
+
+\Class{Subfiles} is used in the component files of a multi-file
+project, and the corresponding \Package{subfiles} is used in the
+master file; 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 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[includex.sty]Distributed in the ``unsupported'' part of
+  \CTANref{frankenstein}
+\item[moredefs.sty]Distributed as part of \CTANref{frankenstein}
+\item[newclude.sty]Distributed as part of \CTANref{frankenstein}
+\item[pdfpages.sty]\CTANref{pdfpages}
+\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{verbatim}
+\makeatletter
+\let\@texttop\relax
+\makeatother
+\end{verbatim}
+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.
+
+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.
+
+Axel Kielhorn's \Class{akletter} class is the only other one,
+recommended for inclusion in this \acro{FAQ}, whose documentation is
+available in English.
+
+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[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're certainly 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, 14pt and 17pt.
+\begin{ctanrefs}
+\item[extsizes bundle]\CTANref{extsizes}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\end{ctanrefs}
+
+\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-books}; the programming itself is discussed in
+  \Qref[question]{}{Q-atsigns}).
+\end{narrowversion}
+\begin{wideversion} % really hyper
+  (see \Qref{\TeX{}-related books}{Q-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.  Unfortunately, \Package{fncychap} is not attuned to the
+existence of front- and backmatter in \Class{book} class documents.
+
+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 are not useful to users unless they are willing to do
+their own \LaTeX{} programming.
+\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}
+
+\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}
+\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} allows 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}).  The \Qref*{\LaTeX{} Companion}{Q-books}
+discusses use of \csx{@startsection} for this sort of thing.
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}\LaTeX{} source]\CTANref{latex}
+\item[titlesec.sty]\CTANref{titlesec}
+\end{ctanrefs}
+
+\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{}}
+
+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-ps@empty}, 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}
+
+\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.
+
+Note that 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[fancyhdr]\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}
+\item[flushend.sty]Distributed as part of \CTANref{sttools}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}
+
+\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; users of that package should refer to
+the documentation.
+
+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}
+
+\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} package is
+therefore supplied to make life easy for us all; it defines 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}
+\end{ctanrefs}
+
+\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.
+
+Documentation of \Package{chappg} is to be found in the package file.
+\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}
+
+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.  On \ProgName{Reader} version 7, there are two entries to
+check:
+\begin{quote}
+   Page Scaling (default: ``Fit to printer margins'')~--- change to
+   ``None'', and\\
+   Scale (default 95\textpercent {} of Normal size)~--- change to
+   ``100\textpercent''.
+% NB the space after \textpercent seems to be necessary for the health
+% of sanitize.pl :-(
+\end{quote}
+
+\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} and \ProgName{dvipdfm} define
+\csx{special} commands for the document to specify its own paper size;
+so in those cases, as when \PDFTeX{} or V\TeX{} 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} package (whose main business is 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 either \PDFLaTeX{} or V\TeX{}.)
+
+So, the resolution of the problem is to add
+\begin{quote}
+\begin{verbatim}
+\usepackage[dvixxx,...]{geometry}
+\end{verbatim}
+\end{quote}
+(where \pkgoption{dvixxx} is your current favourite \acro{DVI}
+driver~--- \Package{geometry} knows about \pkgoption{dvips} and
+\pkgoption{dvipdfm}), and the document will run correctly with
+\LaTeX{}.  If you're using \PDFLaTeX{}, load with
+\begin{quote}
+\begin{verbatim}
+\usepackage[pdftex,...]{geometry}
+\end{verbatim}
+\end{quote}
+
+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}
+\end{ctanrefs}
+
+\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 needing to
+think about them, but 
+
+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}
+
+The `ultimate' tool for adjusting the dimensions and position of the
+printed material on the page is the \Package{geometry} package; a very
+wide range of adjustments of the layout may be relatively
+straightforwardly programmed, 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 of \Package{geometry} is a bit overwhelming, and
+learning all its capabilities may be more than you ever need.
+Somewhat simpler to use is the \Package{vmargin} package, which 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}
+\item[memoir.cls]\CTANref{memoir}
+\item[typearea.sty]Distributed as part of \CTANref{koma-script}
+\item[vmargin.sty]\CTANref{vmargin}
+\end{ctanrefs}
+
+\Question[Q-marginmanual]{How to set up page layout ``by hand''}
+
+So you're eager to do it yourself, notwithstanding the cautions
+\begin{narrowversion}
+  outlined above (\Qref{}{Q-changemargin}).
+\end{narrowversion}
+\begin{wideversion}
+  outlined in ``\Qref{changing margins}{Q-changemargin}''.
+\end{wideversion}
+
+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-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.
+
+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.
+\begin{ctanrefs}
+\item[changepage.sty]\CTANref{changepage}
+\item[chngpage.sty]\CTANref{chngpage}
+\end{ctanrefs}
+
+\Question[Q-nopageno]{How to get rid of page numbers}
+
+The package \Package{nopageno} will suppress page numbers in a whole
+document.
+
+To suppress page numbers from a single page, use
+\cmdinvoke{thispagestyle}{empty} somewhere within the text of the
+page.  (Note that \csx{maketitle} and \csx{chapter} both use
+\csx{thispagestyle} internally, so you need to call it after you've
+called them.)
+
+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
+use \csx{thispagestyle} after any \csx{maketitle} or \csx{chapter}
+command.
+
+In the \Class{memoir} class, the troublesome commands (\csx{maketitle},
+\csx{chapter}, etc.\@) invoke their own page style
+(\environment{title}, \environment{chapter}, etc.\@), which you may
+redefine using the class's own techniques to be equivalent to
+``\environment{empty}''.  The \Class{KOMA-script} classes have
+commands that contain the page style to be used, so one might say:
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\titlepagestyle}{empty}
+\end{verbatim}
+\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), which may be undesirable.
+
+The \Package{scrpage2} package separates out the representation from
+the resetting; so one can say
+\begin{quote}
+\begin{verbatim}
+\renewcommand*{\pagemark}{}
+\end{verbatim}
+\end{quote}
+to have the same effect as the \texttt{gobble} trick, without
+resetting the page number.
+\begin{ctanrefs}
+\item[nopageno]\CTANref{nopageno}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[scrpage2.sty]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+
+\Question[Q-ps@empty]{\psatempty{} on first page in \LaTeX{}}
+
+If you use \cmdinvoke{pagestyle}{empty}, but the first page is numbered
+anyway, you are probably using the \csx{maketitle} command too. The
+behaviour is not a bug but a feature.  The standard \LaTeX{} classes are
+written so that initial pages (pages containing a \csx{maketitle},
+\csx{part}, or \csx{chapter}) have a different page style from the rest
+of the document; to achieve this, the commands internally issue
+\cmdinvoke{thispagestyle}{plain}. This is usually not acceptable
+behaviour if the surrounding page style is `empty'.
+
+Possible workarounds include:
+\begin{itemize}
+\item Put \csx{thispagestyle{empty}} immediately after the
+  \csx{maketitle} command, with no blank line between them.
+\item Use the \Package{fancyhdr} or \Package{scrpage2} packages, which
+  allow you to customise the style for initial pages independently of
+  that for body pages.
+
+  For example, use \Package{fancyhdr} commands:
+\begin{verbatim}
+\fancypagestyle{plain}{%
+  \fancyhf{}%
+  \renewcommand{\headrulewidth}{0pt}%
+  \renewcommand{\footrulewidth}{0pt}%
+}
+\end{verbatim}
+  and the ``\texttt{empty}'' page style (invoked by \csx{chapter}
+  commands and title pages) will have no header or footer.
+\item If you are using either the \Class{memoir} class or a
+  \Class{KOMA-script} class, use the techniques outlined for them in
+  ``\Qref*[question]{no page numbers}{Q-nopageno}''.
+\end{itemize}
+\begin{ctanrefs}
+\item[fancyhdr.sty]\CTANref{fancyhdr}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[nopageno.sty]\CTANref{nopageno}
+\item[scrpage2.sty]Distributed as part of \CTANref{koma-script}
+\end{ctanrefs}
+
+\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, this can
+be achieved with 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.
+
+More elaborate watermarks may be achieved using the \Package{eso-pic}
+package, which in turn uses the package \Package{everyshi}, or by
+using \Package{everypage}.  \Package{Eso-pic} attaches a
+\environment{picture} environment to every page as it is shipped out;
+you 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 you're at liberty
+to do what you like.
+
+\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.
+\begin{ctanrefs}
+\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}
+\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}
+\item[lscape.sty]Distributed as part of \CTANref{graphics}
+\item[memoir.cls]\CTANref{memoir}
+\item[pdflscape.sty]Distributed with Heiko Oberdiek's packages
+  \CTANref{oberdiek}
+\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}
+\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: a good
+example is list items~--- they suggest page breaks between them.  Even
+if \environment{samepage} \emph{does} work, it's likely to leave stuff
+jutting out at the bottom of the page.
+
+A 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 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.  The alternatives are to insert \csx{clearpage}
+commands as necessary, or to use \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.  It depends on the document
+whether this looks impossibly awful or entirely acceptable, but the
+command remains a useful item in the armoury.
+\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}, 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.
+
+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}
+\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek}
+\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} (do \emph{not}
+be tempted by \Package{doublespace}~--- its performance under current
+\LaTeX{} is at best problematical).  \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.
+
+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}
+
+\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 font itself, rather
+than inserting space between characters.  Ordinarily, letter-spacing
+will destroy ligatures; however, this is \emph{wrong} if the font is
+of a fraktur style, 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}
+\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}
+\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}
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}
+\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}.
+
+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},
+\Class{memoir} or \Package{fancyvrb} (see % beware line break
+\Qref[question]{including files verbatim}{Q-verbfile}) may be used.
+
+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{wideversion} % really hyper
+  \Qref{Verbatim listings}{Q-verbfile} are dealt with elsewhere,
+\end{wideversion}
+\begin{narrowversion}
+  Verbatim listings are dealt with elsewhere (\Qref{}{Q-verbfile}),
+\end{narrowversion}
+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{}
+
+Most people, advising others on \AllTeX{} lists, seem to regard
+\Package{listings} as the be-all and end-all on this topic.  But there
+\emph{are} alternatives, which may be worth considering, in some
+situations.
+
+\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.
+Documentation is available on the % ! line break
+\href{http://www.andre-simon.de/}{\ProgName{highlight} project site}.
+
+The \ProgName{lgrind} system is another well-established pre-compiler,
+with all the facilities one might need and a wide repertoire of
+languages; it is derived from the very long-established
+\ProgName{tgrind}, whose output is based on \plaintex{}
+
+The \ProgName{tiny_c2l} system is more recent: users are encouraged to
+generate their own driver files for languages it doesn't already deal
+with.
+
+The \ProgName{C++2LaTeX} system comes with strong recommendations for
+use with \acro{C} and \acro{C}++.
+
+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''.
+\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[tgrind]\CTANref{tgrind}
+\item[tiny\_c2l]\CTANref{tiny_c2l}
+\end{ctanrefs}
+
+\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.
+
+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}
+
+\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}, which comes with a
+  glossary-maker called \Package{glotex}.
+\item[texindex] A witty little shell/\ProgName{sed}-script-based
+  utility for \LaTeX{} under Unix.
+  
+  The \Qref*{Texinfo}{Q-texinfo} system also uses a program
+  \ProgName{texindex}, whose source is to be found in the
+  \ProgName{texinfo} distribution.  The \Package{ltxindex} package
+  provides macros to allow \LaTeX{} users to use \emph{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.  Sadly, its take-up is proving rather slow.
+\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.  Note that, because the operation is
+  conducted in maths mode, spaces within the \acro{URL} argument are
+  ignored unless special steps are taken.
+  
+  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{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}
+\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}
+\item[path.sty]\CTANref{path}
+\item[url.sty]\CTANref{url}
+\end{ctanrefs}
+
+\Question[Q-music]{Typesetting music in \TeX{}}
+
+In the early days, a simple music package called Mu\TeX{} was
+written by Angelika Schofer and Andrea Steinbach, which demonstrated
+that music typesetting was possible; the package was very limited, and is
+hardly ever used nowadays.  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 most
+definitely no longer recommended.
+
+Music\TeX{} has been superseded by its successor MusiX\TeX{}, which is
+a three-pass system (with a processor program that computes values for
+the element spacing in the music), and achieves finer control than is
+possible in the unmodified \TeX{}-based mechanism that Music\TeX{}
+uses.  Daniel Taupin's is the only version of MusiX\TeX{} currently
+being developed (the original author, Andreas Egler, had an
+alternative version, but he is now working on a different package
+altogether).
+
+Input to Musix\TeX{} is extremely tricky stuff, and Don Simons'
+preprocessor \ProgName{pmx} is the preferred method of creating input
+for Taupin's version.  \ProgName{Pmx} greatly eases use of
+Musix\TeX{}, but it doesn't support the full range of Musix\TeX{}'s
+facilities directly; however, it does allow in-line Musix\TeX{} code
+in \ProgName{pmx} sources.
+
+Dirk Laurie's \ProgName{M-Tx} allows preparation of music with lyrics;
+it operates ``on top of'' \ProgName{pmx}
+
+Another simple notation is supported by \ProgName{abc2mtex}; this is a
+package designed to notate tunes stored in an \acro{ASCII} format
+(\texttt{abc} notation). It was designed primarily for folk and traditional
+tunes of Western European origin (such as Irish, English and Scottish)
+which can be written on one stave in standard classical notation, and
+creates input intended for Music\TeX{}.  However, it should be
+extendable to many other types of music.
+
+Digital music fans can typeset notation for their efforts by using
+\ProgName{midi2tex}, which translates \acro{MIDI} data files into
+Music\TeX{} source code.
+
+There is a mailing list (\Email{TeX-music@icking-music-archive.org})
+for discussion of typesetting music in \TeX{}; it mostly covers
+Musix\TeX{} and related systems.  To subscribe, use
+\URL{http://icking-music-archive.org/mailman/listinfo/tex-music/}
+
+An alternative (free) means of embedding music examples into \AllTeX{}
+documents is \href{http://www.lilypond.org}{Lilypond}.  Lilypond is
+(at heart) a batch music typesetting system with plain text input that
+does most of its work without TeX.  Lilypond's input syntax is far
+less cryptic than is Musix\TeX{}'s, and it handles much more stuff
+automatically, yielding the same or better quality with less effort.
+Lilypond can also produce basic \acro{MIDI} output.
+\begin{ctanrefs}
+\item[abc2mtex]\CTANref{abc2mtex}
+\item[M-Tx]\CTANref{mtx}
+\item[midi2tex]\CTANref{midi2tex}
+\item[musictex]\CTANref{musictex}
+% ! line breaks
+\item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex-taupin}
+\item[musixtex \nothtml{\rmfamily}(Egler's version)]\CTANref{musixtex-egler}
+\item[mutex]\CTANref{mutex}
+\item[pmx]\CTANref{pmx}
+\end{ctanrefs}
+
+\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{verbatim}
+  \setlength{\parindent}{0pt}
+  \setlength{\parskip}{\baselineskip}
+\end{verbatim}
+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}
+
+\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''}{«lettrines»}, 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 recent
+offerings like \PDFTeX{}, V\TeX{} or \acro{DVI}pdfm.
+
+On such occasions, the more recent \Package{lettrine} package is more
+likely to succeed.  It has a well-constructed array of options, and
+the examples (a pretty impressive set) come as a separate file in the
+distribution (also available in \PS{}, so that they can be viewed
+without installing the package itself).
+\begin{ctanrefs}
+\item[dropping]\CTANref{dropping}
+\item[lettrine]\CTANref{lettrine}
+\end{ctanrefs}
+
+\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}
+\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 starts to seem a real imposition.
+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{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[memoir.cls]\CTANref{memoir}
+\item[shade.tex]\CTANref{shade}
+\end{ctanrefs}
+
+\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 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[soul.sty]\CTANref{soul}
+\item[ulem.sty]\CTANref{ulem}
+\end{ctanrefs}
+
+\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-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.
+
+Alternatively, the package \Package{tocloft} 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 \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[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[tocloft.sty]\CTANref{tocloft}
+\end{ctanrefs}
+
+\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.  This normally has
+to be set in the preamble and is a constant for the document.  The
+package \Package{tocvsec2} package provides a convenient interface to
+allow you to change the \texttt{secnumdepth} and/or the
+\texttt{tocdepth} counter values at any point in the body of the
+document; this provides convenient independent controls over the
+sectional numbering and the table of contents.
+
+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 are 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}
+
+\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 the \LaTeX{} 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}{Another Idiot}
+...
+\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{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 \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[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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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}
+\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{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+...
+... the introduction to volume1
+               (\ref{V1-introduction})...
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+...
+... the introduction to volume1 (\ref{V1-introduction})...
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+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}
+\begin{ctanrefs}
+\item[xr.sty]Distributed as part of \CTANref{2etools}
+\item[xr-hyper.sty]Distributed with \CTANref{hyperref}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{How do I do\dots{}?}
+
+\subsection{Mathematics}
+
+\Question[Q-proof]{Proof environment}
+
+It has long been 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
+% beware 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
+\Package{ntheorem} package now solves the problem for \LaTeX{} users:
+it does indeed provide 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}
+\item[ntheorem.sty]\CTANref{ntheorem}
+\end{ctanrefs}
+
+\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}
+\item[ntheorem.sty]\CTANref{ntheorem}
+\item[theorem.sty]Distributed as part of \CTANref{2etools}
+\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]In the \AMSLaTeX{} distribution \CTANref{amslatex}
+\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-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}
+
+\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{verbatim}
+  $ ... \reflectbox{$\ddots$} ... $
+\end{verbatim}
+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 disadvantage of this setup is, that although \csx{adots} is merely
+a macro, the package tries to load its own font and produces a
+``missing font'' substitution warning message if you haven't installed
+the font.
+
+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 \nothtml{\rmfamily}(fonts)]\CTANref{yhmath-fonts}
+\item[yhmath \nothtml{\rmfamily}(macros)]\CTANref{yhmath-macros}
+\end{ctanrefs}
+
+\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}
+looks quite painfully wrong.
+
+The other simple technique, \csx{textrm}, is more promising:
+\begin{quote}
+\begin{verbatim}
+$z = a_{\textrm{other end}}$
+\end{verbatim}
+\end{quote}
+is definitely right.  However, the surrounding text may not be in your
+roman font; if you care about matching text, you need to choose
+between \csx{textrm}, \csx{textsf}, and so on.
+
+(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.
+
+These short cuts are (just about) \acro{OK} for the ``occasional''
+mathematician, 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, so
+anyone using \AMSLaTeX{} proper has the command available, so even
+joke mathematicians 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.
+
+\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}
+
+Comprehensive documentation of \AMSLaTeX{} is to be found in
+\File{amsldoc}, in the distribution; it is also available on the web
+at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf}
+\begin{ctanrefs}
+\item[amsldoc.tex]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\item[amstext.sty]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\item[mathtools.sty]Distributed as part of the \Package{mh} bundle
+  \CTANref{mh}
+\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.
+
+Comprehensive documentation of \AMSLaTeX{} is to be found in
+\File{amsldoc}, in the distribution; it is also available on the web
+at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf}
+\begin{ctanrefs}
+\item[amsldoc.tex]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\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}
+\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-books}).  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}
+\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-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 list itself.  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 wasn't
+designed for more compact lists \emph{per se}, but offers the user
+control over the list spacing.
+
+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 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!
+
+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.
+\begin{ctanrefs}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}
+\item[enumitem.sty]\CTANref{enumitem}
+\item[expdlist.sty]\CTANref{expdlist}
+\item[memoir.cls]\CTANref{memoir}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\item[multenum.sty]\CTANref{multenum}
+\item[paralist.sty]\CTANref{paralist}
+\item[savetrees.sty]\CTANref{savetrees}
+\end{ctanrefs}
+
+\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{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}
+However, the comment interpolated in the nested enumeration appears as
+if it were a second paragraph to ``outer item 2'', which is hardly
+satisfactory.
+\end{quote}
+\begin{ctanrefs}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}
+\item[enumitem.sty]\CTANref{enumitem}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\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-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{topcaption}
+...
+\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} (from the release of 23 January, 2004) may be loaded
+with an option that has the same effect:
+\begin{quote}
+\begin{verbatim}
+\usepackage[tableposition=top]{caption}
+\end{verbatim}
+\end{quote}
+
+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.  (The package itself is very slightly more elaborate\dots{})
+\begin{ctanrefs}
+\item[booktabs.sty]\CTANref{booktabs}
+\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
+\item[memoir.cls]\CTANref{memoir}
+\item[topcapt.sty]\CTANref{topcapt}
+\end{ctanrefs}
+
+\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{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}
+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}
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}
+\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}
+\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{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}
+\begin{verbatim}
+\cmdinvoke{begin}{tabular}{l l l p{3cm}}
+\end{verbatim}
+\end{quote}
+would become
+\begin{quote}
+\begin{verbatim}
+\cmdinvoke{begin}{tabular}{Sl Sl Sl Sp{3cm}}
+\end{verbatim}
+\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}.
+
+Documentation of both \Package{bigstrut} and \Package{tabls} may be
+found as comments in the package files themselves.
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}
+\item[bigstrut.sty]Distributed as part of \CTANref{multirow}
+\item[booktabs.sty]\CTANref{booktabs}
+\item[cellspace.sty]\CTANref{cellspace}
+\item[tabls.sty]\CTANref{tabls}
+\end{ctanrefs}
+
+\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}
+\item[ltablex.sty]\CTANref{ltablex}
+\item[ltxtable.sty]Generate by running \CTANref{ltxtable}
+\item[stabular.sty]Distributed as part of \CTANref{sttools}
+\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. 
+
+
+The technique using \csx{PBS} was developed in the days of \LaTeXo{}
+because 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}
+
+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.  If 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}
+\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 in \LaTeX{}}
+
+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.
+    
+    Height can be omitted, in which case it will be calculated by the
+    package; 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}
+\begin{ctanrefs}
+\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}
+
+\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{slashbox} package does the job for you: it defines
+commands \csx{slashbox} and \csx{backslashbox}, each taking the two
+labels as arguments.  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 isn't the world's neatest: it uses \LaTeX{}
+\environment{picture} mode to draw its line, and picture mode has many
+tedious restrictions (and doesn't, in all honesty, produce
+particularly good pictures).  Load slashbox with the \Package{pict2e}
+package, and at least the picture quality will be improved.
+
+Documentation of \Package{slashbox} is less than satisfactory: a
+\LaTeX{} source file of rather startling starkness accompanies the
+package file in the distribution.  It does, however, process to a
+\acro{DVI} file that gives some idea of how the \csx{slashbox} may be
+expected to look.  (The third example in the file shows the effect of
+\environment{picture} mode's restrictions: the dividing line doesn't
+go from corner to corner in the box: to correct this requires revision
+of \Package{slashbox}~--- \Package{pict2e} alone doesn't help in this
+regard.)
+\begin{ctanrefs}
+\item[slashbox.sty]\CTANref{slashbox}
+\end{ctanrefs}
+
+\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}
+\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]Distributed as part of \CTANref{multirow}
+\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-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}.
+
+\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[stfloats.sty, midfloat.sty]Distributed as part of
+  \CTANref{sttools}
+\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}
+\end{ctanrefs}
+
+\Question[Q-dpfloat]{Facing floats on 2-page spread}
+
+If a pair of floats are 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 unless the standard class option
+\pkgoption{twoside} is in effect.
+
+Full documentation of the package (such as it is) is to be found in
+\File{README.dpfloat}
+\begin{ctanrefs}
+\item[dpfloat.sty]\CTANref{dpfloat}
+\end{ctanrefs}
+
+\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 have to find a means of getting the caption and other effects
+without allowing the figure or table to float.
+
+The most straightforward way is to use 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 shows, these \texttt{[H]} figures (and correspondingly,
+tables) offer all you need to cross-reference as well as typeset.
+
+However, you don't actually \emph{have} to use \Package{float} 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 in
+ordinary running text.  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.
+\begin{ctanrefs}
+\item[capt-of.sty]\CTANref{capt-of}
+\item[caption.sty]\CTANref{caption}
+\item[float.sty]\CTANref{float}
+\end{ctanrefs}
+
+\subsection{Footnotes}
+
+\Question[Q-footintab]{Footnotes in tables}
+
+The standard \LaTeX{} \csx{footnote} command doesn't work in tables; the table
+traps the footnotes and they can't escape to the bottom of the page.
+
+If your table is floating, your best bet is (unfortunately) to put the
+table in a \environment{minipage} environment and to put the notes
+underneath the table, or to use Donald Arseneau's package
+\Package{threeparttable} (which implements ``table notes'' proper).
+
+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''.
+
+Otherwise, if your table is not floating (it's just a
+`\texttt{tabular}' in the middle of some text), there are several
+things you can do to fix the problem.
+\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 table in a \texttt{minipage} anyway.  This provides all the
+  ugliness of footnotes in a minipage with no extra effort.
+\item Use \Package{threeparttable} anyway; the package is intended for
+  floating tables, and the result might look odd if the table is not
+  floating, but it will be reasonable.
+\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{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 the 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 properly, 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}
+
+The documentation of \Package{threeparttable} appears in the package
+file itself; that of \Package{ctable} is distributed as a \acro{PDF}
+file (for convenience's sake).
+\begin{ctanrefs}
+\item[ctable.sty]\CTANref{ctable}
+\item[footnote.sty]Distributed as part of \CTANref{mdwtools}
+\item[longtable.sty]Distributed as part of \CTANref{2etools}
+\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}
+\item[threeparttable.sty]\CTANref{threeparttable}
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}
+\end{ctanrefs}
+
+\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} and with % ! line break
+\Qref*{footnotes in tables}{Q-footintab}.  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.  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{verbatim}
+\begin{figure}
+  \begin{minipage}{\textwidth}
+    ...
+    \caption[Caption for LOF]%
+      {Real caption\footnote{blah}}
+  \end{minipage}
+\end{figure}
+\end{verbatim}
+\end{quote}
+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 ``blah''. (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.)
+
+The documentation of the \Package{ccaption} package describes a really
+rather awful work-around.
+\begin{ctanrefs}
+\item[ccaption.sty]\CTANref{ccaption}
+\item[threeparttable.sty]\CTANref{threeparttable}
+\end{ctanrefs}
+
+\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 the \CTANref{ncctools}
+  bundle
+\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 the link 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 three packages that manage it, one way
+or another.
+
+The \Package{perpage} package provides a general mechanism for
+resetting counters per page, so can obviously be used for this task.
+The interface is pretty simple: \cmdinvoke{MakePerPage}{footnote} will
+do the job.  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}.  It's a
+first-rate package, small and efficient
+
+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.  (Documentation is
+\File{footnpag-user.pdf} in the distribution.)
+\begin{ctanrefs}
+\item[footmisc.sty]\CTANref{footmisc}
+\item[footnpag.sty]\CTANref{footnpag}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}
+\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.
+
+If you're not inputting things from a file that's already been 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}.
+
+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}
+Both examples of patching \csx{input} assume you always use
+\LaTeX{} syntax, i.e., always use braces around the argument.
+
+The \Package{FiNK} (``File Name Keeper'') package provides a
+regular means of keeping track of the current file name (with its
+extension), in a macro \csx{finkfile}.  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[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{input}, \csx{include}, \csx{includegraphics} and so on).  But if you
+use \TeX{} primitive syntax, as in
+\begin{verbatim}
+  \input mymacros
+\end{verbatim}
+\File{mymacros.tex} \emph{won't} be listed by \csx{listfiles}, since
+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
+\ProgName{teTeX} and \ProgName{\miktex{}}.  It's plainly useful when
+you're sending the first copy of a document.
+\begin{ctanrefs}
+\item[bundledoc]\CTANref{bundledoc}
+\item[snapshot.sty]\CTANref{snapshot}
+\end{ctanrefs}
+
+\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 being 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 the
+information, but we're not aware yet of any programmer taking
+advantage of the fact to write a \PDFTeX{}-based changebar package).
+
+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 generate
+\csx{special}s for (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://www.tex.ac.uk/tex-archive/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}
+\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{\{}\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.
+
+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}
+
+A further valuable twist is offered by the \Package{extract} package.
+This 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 with Heiko Oberdiek's packages~---
+  \CTANref{oberdiek}
+\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 with Heiko Oberdiek's packages~---
+  \CTANref{oberdiek}
+\item[pdfpages.sty]\CTANref{pdfpages}
+\item[selectp.sty]\CTANref{selectp}
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}
+\item[version.sty]\CTANref{version}
+\item[versions.sty]\CTANref{versions}
+\item[xcomment.sty]Distributed as part of \CTANref{seminar}
+\end{ctanrefs}
+
+\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.548 $ % or any RCS keyword
+\RCS$Date: 2008/06/20 13:37:44 $
+...
+\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.548 $ % or any RCS keyword
+\RCS$Date: 2008/06/20 13:37:44 $
+...
+\date{Revision \RCSRevision, \RCSDate}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+
+If you've entered the brave new world 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}- and
+\ProgName{Git}-controlled repositories.
+\begin{ctanrefs}
+\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}
+
+\Question[Q-make]{Makefiles for \LaTeX{} documents}
+
+\LaTeX{} is a tricky beast for running \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}.
+
+For this reason, the only \ProgName{make}-like package on \acro{CTAN}
+(for a long time) 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 a long 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.
+
+Apparently along the same lines, and currently (2007) under active
+development, 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.
+
+Windows users of the \miktex{} system may use that systems
+\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}AutoLaTeX]\CTANref{autolatex}
+\item[\nothtml{\rmfamily}\acro{FAQ} distribution]\CTANref{faq}
+\item[\nothtml{\rmfamily}latexmake]\CTANref{latexmake}
+\item[latexmk]\CTANref{latexmk}
+\item[texi2dvi]Distributed as part of \CTANref{texinfo}
+\end{ctanrefs}
+
+\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 \nothtml{\bgroup\rmfamily}and\nothtml{\egroup} everyshi.sty]% line break!!
+  Distributed in \CTANref{ms}
+\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}
+\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 accents in the word.  The causes of and remedies
+  for this effect are discussed in
+  % beware 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}
+
+\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. 
+
+One might hope that, with the many aspirant successors to \TeX{} such
+as
+\begin{wideversion}
+  \Qref{Omega}{Q-omegaleph}, \Qref{\LuaTeX{}}{Q-luatex} and
+  \Qref{Ex\TeX{}}{Q-extex},
+\end{wideversion}
+\begin{narrowversion}
+  Omega, \LuaTeX{} and Ex\TeX{}
+  (\Qref[see questions]{}{Q-omegaleph}\Qref[,]{}{Q-luatex}
+  \Qref[and]{}{Q-extex}),
+\end{narrowversion}
+all of which base their operations on Unicode, that the whole basis of
+encodings will change.
+
+\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{usepckage}[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 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.  
+
+Alternatively, you may 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 do 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}
+
+\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 a
+non-hyphenation 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{} flag \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 accents in them won't break, so \csx{hyphenation} commands
+with accents in them 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 in the usual distributions, 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.
+
+\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, many believe, he thereby
+opened floodgates to give the world a whole range of rather silly
+`bumpy road' logos 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{}
+\htmlignore
+(silly enough in itself)
+\endhtmlignore
+\begin{htmlversion}
+  (silly enough in itself, with a raised small `A' and a lowered `E')
+\end{htmlversion}
+and marketing input from Addison-Wesley led to the even
+stranger current logo
+\htmlignore
+\LaTeXe{}.
+\endhtmlignore
+\begin{htmlversion}
+  \LaTeXe{}, which appends a lowered single-stroke Greek letter
+  epsilon.
+\end{htmlversion}
+
+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
+\htmlignore
+\textlogo{META\hphantom{P}O\hphantom{S}T}).
+\endhtmlignore
+% 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;O&nbsp;T').
+\end{htmlversion}
+You needn't despair, however~--- the author himself uses just `MetaPost'.
+
+For those who don't wish to acquire the `proper' logos, the canonical
+thing to do is to say \texttt{AMS-}\cmdinvoke{TeX}{}
+\htmlignore
+(\acro{AMS}-\TeX{})
+\endhtmlignore
+for \AMSTeX{}, \texttt{Pic}\cmdinvoke{TeX}{}
+\htmlignore
+(Pic\TeX{})
+\endhtmlignore
+for \PiCTeX{}, \texttt{Bib}\cmdinvoke{TeX}{}
+\htmlignore
+(Bib\TeX{})
+\endhtmlignore
+for \BibTeX{}, and so on.
+\begin{ctanrefs}
+\item[mflogo.sty]\CTANref{mflogo}
+\item[texnames.sty]\CTANref{texnames}
+\end{ctanrefs}
+
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Symbols, etc.}
+
+\Question[Q-numbersets]{Symbols for the number sets}
+
+It is a good idea to have commands such as \csx{R} for the real numbers and
+other standard number sets. Traditionally these were typeset in bold.
+Because, in the ordinary course of events, mathematicians do not have
+access to bold chalk, they invented the special symbols that are now
+often used for \csx{R}, \csx{C}, \emph{etc}.  These symbols are known
+as ``blackboard bold''.  Before insisting on using them, consider
+whether going back to the old system of ordinary bold might not be
+acceptable (it is certainly simpler).
+
+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 pair of font
+families (the other is called \FontName{msam}) have a large number of
+mathematical symbols to supplement the ones in the standard \TeX{}
+distribution, and are available in Type~1 format with most modern
+distributions. Support files for using the fonts, both under
+\plaintex{} and \LaTeX{} (packages \Package{amssymb} and
+\Package{amsfonts}), are available.  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'.
+
+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}
+(though, as noted elsewhere, there are other reasons not to use these
+fonts).  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}{{\sf R\hspace*{-0.9ex}%
+  \rule{0.15ex}{1.5ex}\hspace*{0.9ex}}}
+\newcommand{\N}{{\sf N\hspace*{-1.0ex}%
+  \rule{0.15ex}{1.3ex}\hspace*{1.0ex}}}
+\newcommand{\Q}{{\sf Q\hspace*{-1.1ex}%
+  \rule{0.15ex}{1.5ex}\hspace*{1.1ex}}}
+\newcommand{\C}{{\sf 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}.  However, they are not part of a proper maths font,
+and so do not work in sub- and superscripts.  Moreover, the size and
+position of the vertical bar can be affected by the font of the
+surrounding text.  As we've seen, there are plenty of alternatives:
+don't try the macros, or anything similar using capital `I' (which
+looks even worse!).
+\begin{ctanrefs}
+\item[AMS support files (Plain)]\CTANref{amsfonts-plain}
+\item[AMS support files (LaTeX)]\CTANref{amsfonts-latex}
+\item[AMS symbol fonts]\CTANref{amsfonts-symbols}
+\item[AMS symbol fonts in Type~1 format]Browse \CTANref{ams-AMStype1}
+\item[bbm fonts]\CTANref{bbm}
+\item[bbm macros]\CTANref{bbm-macros}
+\item[bbold fonts]\CTANref{bbold}
+\item[doublestroke fonts]\CTANref{doublestroke}
+\item[fourier fonts]\CTANref{fourier}
+\item[mathpazo fonts]\CTANref{mathpazo}
+\item[pxfonts]\CTANref{pxfonts}
+\item[txfonts]\CTANref{txfonts}
+\end{ctanrefs}
+
+\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[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.  The package
+  creates a new command \csx{mathscr}.
+  
+  Type 1 versions of the font have been made available by Taco
+  Hoekwater.
+\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{verbatim}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+                                 {m}{it}
+\end{verbatim}
+  in your preamble.  You may find the font rather too big; if so, you
+  can use a scaled version of it like this:
+\begin{verbatim}
+\DeclareFontFamily{OT1}{pzc}{}
+\DeclareFontShape{OT1}{pzc}{m}{it}%
+             {<-> s * [0.900] pzcmi7t}{}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+                                 {m}{it}
+\end{verbatim}
+  
+  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} and is distributed with
+  \ProgName{ghostscript}.
+\end{description}
+Examples of the available styles are available on \acro{CTAN}.
+\begin{ctanrefs}
+\item[eucal.sty]\CTANref{eucal}
+\item[euler fonts]\CTANref{amsfonts-euler}
+\item[euler fonts, in Type 1 format]\CTANref{ams-AMStype1}
+\item[ghostscript]Browse \CTANref{ghostscript}
+\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}
+\item[rsfs fonts]\CTANref{rsfs}
+\item[rsfs fonts, in Type 1 format]\CTANref{rsfs-type1}
+\item[Script font examples]\CTANref{mathscript}
+\end{ctanrefs}
+
+\Question[Q-boldgreek]{Setting bold Greek letters in \LaTeX{}}
+
+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).  However
+lower-case Greek letters behave differently from upper-case Greek
+letters (due to Knuth's esoteric font encoding decisions).  However,
+\csx{mathbf} \emph{can't} be used even for upper-case Greek letters in
+the \AMSLaTeX{} \Package{amsmath} package, which
+disables this font-switching and you must use one of the techniques
+outlined below.
+
+The \plaintex{} solution \emph{does} work, in a limited way:
+\begin{quote}
+\begin{verbatim}
+{\boldmath$\theta$}
+\end{verbatim}
+\end{quote}
+but \csx{boldmath} may not be used in maths mode, so this `solution'
+requires arcana such as:
+\begin{quote}
+\begin{verbatim}
+$... \mbox{\boldmath$\theta$} ...$
+\end{verbatim}
+\end{quote}
+which then causes problems in superscripts, etc.
+
+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 cover all mathematical symbols, not merely Greek
+letters.
+\begin{ctanrefs}
+\item[bm.sty]Distributed as part of \CTANref{2etools}
+\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}
+\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
+  \CTANref{amslatex}
+\end{ctanrefs}
+
+\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{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}
+\csx{dashint} gives a single-dashed integral sign, \csx{ddashint} a
+double-dashed one.
+
+\Question[Q-underscore]{How to use the 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.  If you're writing a document which will contain a large
+number of underscore characters, the prospect of typing
+\csx{\_} (or, worse, \csx{textunderscore}) 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'.
+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}).  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.
+
+If the requirement is only for occasional uses of underscores, it may
+be acceptable to use the following construct:
+\begin{quote}
+\begin{verbatim}
+\def\us{\char`\_}
+...
+\texttt{create\us process}
+\end{verbatim}
+\end{quote}
+The construction isn't in the least robust (in the normal English
+sense of the word), but it \emph{is} robust under expansion (i.e., the
+\LaTeX{} sense of the word); so use it with care, but don't worry
+about section headings and the like.
+\begin{ctanrefs}
+\item[underscore.sty]\CTANref{underscore}
+\end{ctanrefs}
+
+\Question[Q-atsign]{How to type an `@' sign?}
+
+Long ago, some packages used to use the `@' sign as a command, 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
+`@'.
+
+\Question[Q-euro]{Typesetting the Euro sign}
+
+The European currency ``Euro'' is represented by a symbol of somewhat
+dubious design, but it's an important currency and \AllTeX{} users
+need to typeset it.
+
+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 \Package{latin9} input encoding defined by the \Package{inputenc}
+package has a euro character defined (character position 164, occupied
+in other \acro{ISO} Latin character sets by the ``currency symbol'').
+The encoding uses the command \csx{texteuro} for the character; at
+present that command is \emph{only} available from the
+\Package{textcomp} package.  There is a Microsoft code page position,
+too, but standardisation of such things proceeds via rather different
+routes and the \LaTeX{} project hasn't yet been given details of the
+change.
+
+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} fonts contain a Euro symbol among many other
+good things.
+%% ; the font on \acro{CTAN} is not Adobe \ProgName{ATM}
+%% compatible, but a compatible version is available free from
+%% \href{http://www.YandY.com/download/marvosym.zip}{\YandY{}}.  The font
+%% on \acro{CTAN} comes with a set of macros to typeset all the symbols
+%% it contains.
+
+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}
+
+\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}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\section{Macro programming}
+
+\subsection{``Generic'' macros and techniques}
+
+\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 the call the redefined \csx{splat} again; this is an
+infinite recursive loop, 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}
+\renewcommand{\smooth}[2]{\mumble\OldSmooth{#1}{#2}}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\renewcommand{\smooth}[2]%
+             {\mumble\OldSmooth{#1}{#2}}
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+
+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 (optionally) using the result
+to (re)define a macro.  The package may also be used as a powerful
+debugging tool.
+
+The \Package{etoolbox} (which provides user access to \eTeX{}'s
+programming facilities) provides a command \csx{patchcmd} which will
+perform a ``string substitution'' in a macro's definition.  The
+package also provides commands that prepend (\csx{pretocmd}) or append
+(\csx{apptocmd}) to the definition of a command.
+
+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 (as in
+\begin{narrowversion}
+  generating documentation for a new package~--- \Qref{}{Q-install-doc}).
+\end{narrowversion}
+\begin{wideversion}
+  \Qref{generating documentation for a new package}{Q-install-doc}).
+\end{wideversion}
+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, you
+had probably best avoid \Package{Patch}.
+\begin{ctanrefs}
+\item[etoolbox.sty]\CTANref{etoolbox}
+\item[patch.doc]\CTANref{patch}
+\item[patchcommand.sty]\CTANref{patchcmd}
+\item[ted.sty]\CTANref{ted}
+\end{ctanrefs}
+
+\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=#1 \end}
+\def\testresult#1\end{\ifx\end#1\end}
+\def\IsInteger#1{TT\fi \testnum{#1}}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\def\testnum#1{\afterassignment\testresult\count255=#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); this can provoke errors.
+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 and use it as:
+\begin{quote}
+\begin{verbatim}
+\def\a#1{+++#1+++#1+++#1+++}  \a{b}
+\end{verbatim}
+\end{quote}
+the macro expansion produces `+++b+++b+++b+++',
+which people find normal.  However, if we now replace part of the macro:
+\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 people may find strange, even though it is just a
+specialisation of the example above.  If you want \csx{a} to
+define \csx{x} to be a macro with one argument, you need to write:
+\begin{quote}
+\begin{verbatim}
+\def\a#1{+++#1+++\def\x ##1{xxx##1}}
+\end{verbatim}
+\end{quote}
+and \csx{a{b}} will expand to 
+`+++b+++|\def\x #1{xxx#1}|', because |#1| gets replaced by `b'
+and |##| gets replaced by |#|.
+
+To nest a definition inside a definition inside a definition then
+you need |####1|, as at each stage |##| is replaced by
+|#|.  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).
+
+\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}
+\end{ctanrefs}
+
+\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):
+|\catcode`_=\active|.
+
+Any character could, in principle, be activated this way and defined
+as a macro (\csx{def}\texttt{\_\{}\csx{\_}\texttt{\}}~--- the simple answer to
+% beware line break
+\Qref[question]{using underscores}{Q-underscore}), but 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 ``|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 ``|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 ``|\def z|'', ``|z|'' is no longer interpreted as
+a letter; the space is therefore not necessary~--- ``|\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 |_| 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]Distributed as part of the source of \LaTeX{}, \CTANref{latex}
+\item[shortvrb.sty]Distributed as part of \CTANref{2etools}
+\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-ifpdf]{Am I using \PDFTeX{}?}
+
+It's often useful to know whether your macros are operating within
+\PDFTeX{} or within (``normal'') \TeX{}; getting the right answer is
+surprisingly tricky.
+
+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}
+The above is, in essence, what Heiko Oberdiek's \Package{ifpdf}
+package does; the reasoning is the \acro{FAQ}'s interpretation of
+Heiko's explanation.
+\begin{ctanrefs}
+\item[ifpdf.sty]Distributed with Heiko Oberdiek's packages \CTANref{oberdiek}
+\end{ctanrefs}
+
+\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
+\TeX{} \texttt{\$\ ...\ \$}
+(except for checking that you're not attempting to open a maths
+environment when you're already in one, or vice versa).  % ! line break
+However, \csx{[}\texttt{\ ...\ }\csx{]} \emph{isn't} the same as 
+\texttt{\$\$\ ...\ \$\$}: the \TeX{} 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*}''.
+%%
+%% Consider \csx{vskip} (or \plaintex{} users of it like \csx{medskip})
+%% \emph{vs}.\nothtml{\@} \csx{vspace} or \csx{vspace*}, but most
+%% especially \csx{addvspace}.
+%% \begin{ctanrefs}
+%% \item[fntguide.pdf]\CTANref{fntguide.pdf}
+%% \item[fntguide.tex]Distributed with \CTANref{latex}
+%% \end{ctanrefs}
+
+\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-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}
+
+\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-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 with Heiko Oberdiek's packages
+  \CTANref{oberdiek}
+\end{ctanrefs}
+
+\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.
+
+The simple answer is to try \csx{show}, in a run of \LaTeX{} 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.)  We may perhaps, now, wonder 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 use that instead:
+\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.)
+
+If one has a malleable text editor, the same investigation may more
+comfortably 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}
+\end{ctanrefs}
+
+\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{verbatim}
+  \newcommand{\blah}[1][Default]{...}
+\end{verbatim}
+
+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{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}
+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}
+\item[twoopt.sty]Distributed as part of \CTANref{oberdiek}
+\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.
+
+Of course, the \LaTeX{} kernel has something slicker than this:
+\begin{quote}
+\begin{wideversion}
+\begin{verbatim}
+\newcommand{\mycommand}{\@ifstar
+                     \mycommandStar%
+                     \mycommandNoStar%
+}
+\newcommand{\mycommandStar}[2]{starred version}
+\newcommand{\mycommandNoStar}[1]{normal version}
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+\newcommand{\mycommand}{\@ifstar
+                     \mycommandStar%
+                     \mycommandNoStar%
+}
+\newcommand{\mycommandStar}[2]{starred version}
+\newcommand{\mycommandNoStar}[1]{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 the definition to 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}
+\begin{ctanrefs}
+\item[ifthen.sty]Part of the \LaTeX{} distribution
+\item[suffix.sty]Distributed as part of \CTANref{bigfoot}
+\end{ctanrefs}
+
+\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{xxx}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.
+
+\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{chngctr}
+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}
+\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{verbatim}
+\ifthenelse{\isodd{\pageref{foo}}}{odd}{even}
+\end{verbatim}
+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 setting a conditional
+\csx{ifoddpage}.  Of course, the \csx{label} contributes to \LaTeX{}'s
+``Rerun to get cross-references right'' error messages\dots{}
+
+The (older) \Package{chngpage} provides the same facilities (though it
+provides a \csx{ifcpoddpage} command; \Package{changepage} (whose
+functions are extracted from the author's \Class{memoir} class) is the
+designated successor to \Package{chngpage}.
+
+The Koma-Script classes have an \environment{addmargin*} environment
+that also provides the sorts of facilities that the \Package{chngpage}
+offers.  Koma-Script's supporting command is % !line break
+\cmdinvoke{ifthispageodd}{<true>}{<false>} executes different things
+depending on the page number.
+\begin{ctanrefs}
+\item[changepage.sty]\CTANref{changepage}
+\item[chngpage.sty]\CTANref{chngpage}
+\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{narrowversion}
+  \LaTeX{} internal
+\end{narrowversion}
+\begin{wideversion}
+  \Qref{\LaTeX{} internal}{Q-atsigns}
+\end{wideversion}
+\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.
+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}
+
+Many people (for some reason) want a stop after a section number, but
+not after a subsection number, 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{wideversion}
+\begin{quote}
+\begin{verbatim}
+\let\@@seccntformat\@seccntformat
+\renewcommand*{\@seccntformat}[1]{%
+  \expandafter\ifx\csname @seccntformat@#1\endcsname\relax
+    \expandafter\@@seccntformat
+  \else
+    \expandafter
+      \csname @seccntformat@#1\expandafter\endcsname
+  \fi
+    {#1}%
+}
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+\let\@@seccntformat\@seccntformat
+\renewcommand*{\@seccntformat}[1]{%
+  \expandafter\ifx
+      \csname @seccntformat@#1\endcsname
+      \relax
+    \expandafter\@@seccntformat
+  \else
+    \expandafter
+      \csname @seccntformat@#1\expandafter
+      \endcsname
+  \fi
+    {#1}%
+}
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+which looks to see if a second-level command has been defined, and
+uses it if so; otherwise it uses the original.  The second-level
+command to define stops after section numbers (only) has the same
+definition as the original ``all levels alike'' version:
+\begin{quote}
+\begin{verbatim}
+\newcommand*{\@seccntformat@section}[1]{%
+  \csname the#1\endcsname.\quad
+}
+\end{verbatim}
+\end{quote}
+Note that all the command definitions of this answer 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}
+\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 use 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.
+\begin{ctanrefs}
+\item[fix-cm.sty]Distributed as part of \CTANref{latex} (an unpacked
+  version is available at \CTANref{fix-cm})
+\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}
+
+\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 needed\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~--- this is one of them).
+\end{wideversion}
+\begin{narrowversion}
+  (the two error lines both wrapped above; the package provides a demo
+  file which contains most of the sorts of errors you might make~---
+  this is one of them).
+\end{narrowversion}
+
+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 in a language that's
+  convenient for you
+\item[nag.sty]\CTANref{nag}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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{\eTeX{}}{Q-etex} and \Qref{Omega}{Q-omegaleph} both do this, as
+  does \Qref{MicroPress Inc's V\TeX{}}{Q-commercial}.
+\end{wideversion}
+\begin{narrowversion}
+  \eTeX{} and \ensuremath{\Omega}~--- \Qref[see questions]{}{Q-etex}
+  \Qref[and]{}{Q-omegaleph} respectively~--- both do this, as does
+  MicroPress Inc's V\TeX{}~--- \Qref{}{Q-commercial}.
+\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 Schell'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[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}
+\end{ctanrefs}
+
+\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 reasonable, 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 hard 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 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 you can't float 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 `simply' increases the number of floating inserts that \LaTeX{}
+  can handle at one time (from~18 to~36).
+\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}
+\item[endfloat.sty]\CTANref{endfloat}
+\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, contained within the file itself.)
+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{verbatim}
+  \usepackage[normalem]{ulem}
+\end{verbatim}
+Documentation of \Package{ulem} is in the package itself.
+\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 page maker, when forming a page, takes account of
+\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.  If the paragraph is a long
+one, it may be possible to set it `tight': say \csx{looseness}\texttt{=-1}
+immediately after the last word of the paragraph.  If that doesn't
+work, try adjusting the page size:
+\cmdinvoke{enlargethispage}{\csx{baselineskip}} may do the job, and
+get the whole paragraph on one page.  Reducing the size of the page by
+\cmdinvoke{enlargethispage}{-\csx{baselineskip}} may produce a
+(more-or-less) acceptable ``two-line widow''.  (Note:
+\csx{looseness}\texttt{=1},
+increasing the line length by one, seldom seems to work~--- the looser
+paragraph typically has a one-word final line, which doesn't look much
+better than the straight 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, various flavours of
+|cmr| could be found 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}.
+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[amsfonts.sty]\CTANref{amsfonts-latex}
+\item[AMS symbol fonts]\CTANref{amsfonts-symbols}
+\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 to
+plague us.  There are, of course, still 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).
+
+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[msa and msb fonts]\CTANref{amsfonts-symbols}
+\item[virtual font set]\CTANref{msx2msa}
+\end{ctanrefs}
+
+%%%???%%% 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, all you can reasonably do is to edit the document.  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; however, most drivers let you have a
+configuration file in which you can specify font substitutions. If you
+specify that every \FontName{am} font should be replaced by its corresponding
+\FontName{cm} font, the output should be almost correct.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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. Remember that
+the \csx{label} command must come \emph{after} the \csx{caption} command, or
+be part of it. For example,
+\htmlignore
+\par\noindent
+\begin{tabular}{@{}lll}
+|  \begin{figure}|     &    & |\begin{figure}|\\
+|  \caption{A Figure}| & or & |\caption{A Figure%| \\
+|  \label{fig}|        &    & |      \label{fig}}| \\
+|  \end{figure}|       &    & |\end{figure}| \\
+\end{tabular}
+\endhtmlignore
+\begin{htmlversion}
+\begin{verbatim}
+  \begin{figure}          \begin{figure}
+  \caption{A Figure}  or  \caption{A Figure%
+  \label{fig}                   \label{fig}}
+  \end{figure}            \end{figure}
+\end{verbatim}
+\end{htmlversion}
+
+You can, just as effectively, shield the \csx{caption} command from its
+associated \csx{label} command, by enclosing the caption in an
+environment of its own.  For example, people commonly seek help after:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+  \caption{A Figure}
+\end{center}
+\label{fig}
+\end{verbatim}
+\end{quote}
+has failed to label correctly.  If you really need this centring (and
+those in the know commonly reject it), code it as:
+\begin{quote}
+\begin{verbatim}
+\begin{center}
+  \caption{A Figure}
+  \label{fig}
+\end{center}
+\end{verbatim}
+\end{quote}
+
+\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> 
+                   g
+<*> [grump]
+\end{verbatim}
+\end{quote}
+and those where a single asterisk at the start of a line mysteriously
+fails to appear in the output.
+
+Both problems arise because |\|{}|\| takes optional arguments.  The
+command |\|{}|\*| means ``break the line here, and inhibit page break
+following the line break''; the command |\|{}|\[|\meta{dimen}|]|
+means ``break the line here and add \meta{dimen} extra vertical space
+afterwards''.
+
+So why does |\|{}|\| get confused by these things at the start of a
+line?  It's looking for the first non-blank thing, and in the test it
+uses ignores the end of the line in your input text.
+
+The solution is to enclose the stuff at the start of the new line in
+braces:
+\begin{quote}
+\begin{verbatim}
+{\ttfamily
+  /* C-language comment\\
+  {[grump]} I don't like this format\\
+  {*}/
+}
+\end{verbatim}
+\end{quote}
+(The above text derives from an actual post to
+\Newsgroup{comp.text.tex}; this particular bit of typesetting could
+plainly also be done using the \environment{verbatim} environment.)
+
+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 measures.
+
+\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
+\begin{quote}
+\begin{verbatim}
+\newcommand{\unbrace}[1]{#1}
+\unbrace{\verb+\error+}
+\end{verbatim}
+\end{quote}
+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 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 a reliable
+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}
+
+Otherwise, there are three 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} (and
+  hence the \csx{footnote}) commands 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 |para| option to 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, which defines a
+  (robust) command which expands to the verbatim argument given.
+\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 
+  |\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).
+\end{itemize}
+Documentation of both \Package{url} and \Package{verbdef} is in the
+package files.
+\begin{ctanrefs}
+\item[fancyvrb.sty]\CTANref{fancyvrb}
+\item[memoir.cls]\CTANref{memoir}
+\item[url.sty]\CTANref{url}
+\item[verbdef.sty]\CTANref{verbdef}
+\end{ctanrefs}
+
+\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}
+comes in reaction to you giving \LaTeX{} a |\|{}|\| command at a time
+when it's not expecting it.  The commonest case is where you've
+decided you want the label of a list item to be on a line of its own,
+so you've written (for example):
+\begin{quote}
+\begin{verbatim}
+\begin{description}
+\item[Very long label] \\
+  Text...
+\end{description}
+\end{verbatim}
+\end{quote}
+|\|{}|\| is actually a rather bad command to use in this case (even if
+it worked), since it would 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 would lead to an ``|Underfull \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
+\Qref[question]{\emph{\LaTeX{} Companion}}{Q-books}\nothtml{~---} offers a
+rather wide selection of variants of these things.)
+
+The quick-and-easy solution, which avoids the warning, is to write:
+\begin{quote}
+\begin{verbatim}
+\begin{description}
+\item[Very long label] \hspace*{\fill} \\
+  Text...
+\end{description}
+\end{verbatim}
+\end{quote}
+which fills out the under-full line before forcing its closure.  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}
+\begin{ctanrefs}
+\item[expdlist.sty]\CTANref{expdlist}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\end{ctanrefs}
+
+% other instances: \[no]linebreak in vertical mode
+
+\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]Distributed as part of \CTANref{carlisle}
+\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
+chapter has appeared, the chapter number is 0.
+
+If you're doing this, it's quite likely that the \Class{article} class
+is for you; try it and see.  Otherwise, give your sections a
+`superior' chapter, 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.
+
+\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.  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 |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 |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{}.
+
+This \acro{FAQ},
+for example, is written with definitions that \emph{require} one to
+type \cmdinvoke{fred}{\relax} % the \relax prevents {} being gobbled
+                              % in html production (sigh)
+for almost all macro invocations, regardless
+of whether the following space is required: however, this \acro{FAQ}
+is written by highly dedicated (and, some would say, eccentric)
+people.  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 |\|{}|\|) and you don't need braces after
+\emph{it}.  Thus one can reduce to one the 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 only use
+a modified macro once or twice within your document.  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).  Of course, 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}
+\end{ctanrefs}
+
+\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
+|10|\nothtml{\,}|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 |100|.  To suppress the first scan of paragraphs, set
+\csx{pretolerance} to |-1|.
+
+\csx{tolerance} is often a good method for adjusting spacing;
+\plaintex{} and \LaTeX{} both set its value to |200|.  \LaTeX{}'s
+\csx{sloppy} command sets it to |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} 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.  Similarly
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+{\footnotesize Extended interjection ...
+   ... into the paragraph.}
+      ... paragraph continues ...
+\end{verbatim}
+\end{quote}
+will look silly, 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}.  Finally, something like
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+  ... paragraph body ends.
+{\footnotesize Short comment on paragraph.}
+
+Next paragraph starts...
+\end{verbatim}
+\end{quote}
+will set the body of the first paragraph on the constricted
+\csx{baselineskip} of the \csx{footnotesize} comment.
+
+So, how to deal with these problems?  The oversized (short) section is
+typically corrected by a \emph{strut}: this word 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}
+However, more extended insertions (whether of larger or smaller text)
+are always going to cause problems; while you can strut larger text,
+ensuring that you strut every line will be tiresome, and there's no
+such thing as a ``negative strut'' that pulls the lines together for
+smaller text.
+
+The only satisfactory way to deal with an extended insertion at a
+different size is to set it off as a separate paragraph.  A
+satisfactory route to achieving this is the \environment{quote}
+environment, which sets its text modestly inset from the enclosing
+paragraph:
+\begin{quote}
+\begin{verbatim}
+Paragraph text ...
+\begin{quote}
+  \footnotesize This is an inset account
+  of something relevant to the enclosing
+  paragraph...
+\end{quote}
+... paragraph continues ...
+\end{verbatim}
+\end{quote}
+Such quote-bracketing also deals with the problem of a trailing
+comment on the paragraph.
+
+\Question[Q-tocloftwrong]{Numbers too large in table of contents, etc.}
+
+\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 those techniques can be employed to make the numbers fit.
+
+\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 |\'|{}|e|).  So, unless you
+have program-generated \acro{T}1 input, 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
+  |\'|{}|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 (align is 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}
+\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
+analogous to those that derive from the \TeX{} primitive maths
+sequences bracketing maths commands with single dollar signs (or pairs
+of dollar signs).
+
+As it turns out, \LaTeX{}'s inline maths grouping, % !line break
+\csx{(}\texttt{ ... }\csx{)}, has precisely the same effect as the
+\TeX{} primitive version \texttt{\$ ... \$}.  (Except that
+the \LaTeX{} version checks to ensure you don't put \csx{(} and
+\csx{)} the wrong way round.)
+
+In this circumstance, 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, they are wrong: if \LaTeX{} code is going to patch display
+maths, it can only do so by patching \csx{[} and \csx{]}.  The most
+obvious way this turns up, is that the class option \pkgoption{fleqn}
+simply does not work for equations coded using % beware line break
+\texttt{\$\$ ... \$\$}, whether you're using the standard classes
+alone, or using package \Package{amsmath}.  Also, the \csx{[} and
+\csx{]} has code for rationalising vertical spacing in some extreme
+cases; that code is not available in \texttt{\$\$ ... \$\$}, so if you
+use the non-standard version, you may occasionally observe
+inconsistent vertical spacing .
+
+There are more subtle effects (especially with package
+\Package{amsmath}), and the simple rule is % ! line break
+\csx{[}\texttt{ ... }\csx{]} whenever
+unadorned displayed maths is needed in \LaTeX{}.
+
+\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 |\|\emph{\texttt{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}
+ignore \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}''.
+
+%*****************************************quote environments up to here
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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-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}
+\end{ctanrefs}
+
+\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 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}
+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:  $E=mc^2$]%
+        {Energy: \[E=mc^2\]}
+\end{verbatim}
+\end{narrowversion}
+\begin{wideversion}
+\begin{verbatim}
+\caption[Energy:  $E=mc^2$]{Energy: \[E=mc^2\]}
+\end{verbatim}
+\end{wideversion}
+\end{quote}
+for, after all, even if you want display maths in a caption, you
+surely don't want it in the list of figures.
+
+The case of footnotes is somewhat more complex;
+``\Qref[question]{footnotes in \LaTeX{} section headings}{Q-ftnsect}''
+deals specifically with that issue.
+
+\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} and \Qref{Omega}{Q-omegaleph}
+\end{htmlversion}
+\htmlignore
+% beware line wrap here
+  Of course, \ensuremath{\Omega} and \eTeX{}~---
+  \Qref[see questions]{}{Q-omegaleph} \Qref[and]{}{Q-etex} respectively~---
+\endhtmlignore
+ both 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}.
+In cases like \PiCTeX{}, it may be possible to use
+\Qref*{\eTeX{}}{Q-etex} (all modern distributions provide it).  The
+\LaTeX{} package \Package{etex} modifies the register allocation
+mechanism to make use of \eTeX{}'s extended register sets (it's 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).  Unfortunately, \eTeX{} doesn't help with
+\csx{read} or \csx{write} objects.
+
+\Question[Q-epsf]{\texttt{epsf} gives up after a bit}
+
+Some copies of the documentation of \File{epsf.tex} seem 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 \Qref[question]{``hyphenation failures''}{Q-nohyph},
+words with accents in them may not be hyphenated.  As a result, any
+such word is deemed improper in a \csx{hyphenation} command.
+
+The solution is to use a font that contains the character in question,
+and to express the \csx{hyphenation} command in terms of that
+character; this ``hides'' the accent from the hyphenation mechanisms.
+\LaTeX{} users can be achieved this by use of the \Package{fontenc}
+package (part of the \LaTeX{} distribution).  If you select an 8-bit
+font with the package, as in \cmdinvoke{usepackage}[T1]{fontenc},
+accented-letter commands such as the |\'||e| in
+|\hyphenation{Ji-m\'||e-nez}| automatically become the single accented
+character by the time the hyphenation gets to look at it.
+
+\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{htmlversion}
+\begin{verbatim}
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+\end{verbatim}
+\end{htmlversion}
+\htmlignore
+\ifpdf
+\begin{verbatim}
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+\end{verbatim}
+\else
+\begin{verbatim}
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion
+...                           for explanation.
+\end{verbatim}
+\fi
+\endhtmlignore
+your figures (or tables) are failing to be 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
+you don't let it ever actually typeset any floats, it will run out of
+space.
+
+This failure usually occurs in extreme cases of
+% beware line break
+\nothtml{floats moving ``wrongly'' (see }%
+\Qref[question]{floats moving ``wrongly''}{Q-floats}\latexhtml{);}{;}
+\LaTeX{} has found it can't place a float, and floats of the same type
+have piled up behind it.  \LaTeX{}'s idea is to ensure that caption
+numbers are sequential in the document: the caption number is
+allocated when the figure (or whatever) is created, and can't be
+changed, so that placement out of order would mean figure numbers
+appearing out of order in the document (and in the list of figures, or
+whatever).  So a simple failure to place a figure means that no
+subsequent figure can be placed; and hence (eventually) the error.
+
+Techniques for solving the problem are discussed in the
+\nothtml{floats question (}%
+\Qref[\htmlonly]{floats question}{Q-floats}\nothtml{)}
+already referenced.
+
+The error also occurs in a 
+long sequence of \environment{figure} or \environment{table}
+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}
+\end{ctanrefs}
+
+\Question[Q-atvert]{\csx{spacefactor} complaints}
+
+The errors
+\begin{verbatim}
+! You can't use `\spacefactor' in vertical mode.
+\@->\spacefactor 
+                 \@m 
+\end{verbatim}
+or
+\begin{verbatim}
+! You can't use `\spacefactor' in math mode.
+\@->\spacefactor 
+                 \@m 
+\end{verbatim}
+or simply
+\begin{verbatim}
+! Improper \spacefactor.
+...
+\end{verbatim}
+bites the \LaTeX{} programmer who uses an internal command without taking
+``precautions''.  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}
+\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-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}
+\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2}
+\item[The psnfss bundle]\CTANref{psnfss}
+\end{ctanrefs}
+
+\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 \CTANref{oberdiek} collection
+\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
+\ProgName{ghostscript} to reprocess the file, outputting a ``plain
+\extension{eps}'' file.  (\ProgName{Ghostscript} is distributed with a script
+\ProgName{ps2epsi} which will regenerate the preview if necessary.)
+Users of the shareware program \ProgName{GSview} will find buttons to
+perform the required transformation of the file being displayed.
+\begin{ctanrefs}
+\item[ghostscript]Browse \CTANref{ghostscript}
+\item[GSview]Browse \CTANref{gsview}
+\end{ctanrefs}
+
+\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
+|name{figure.1.1}|, the problem is (usually) due to a problem of
+package interaction.  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 aren't many 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 tabular; 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.
+\begin{ctanrefs}
+\item[array.sty]Distributed as part of \CTANref{2etools}
+\end{ctanrefs}
+
+\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}}
+
+Give it a file of plain text, or a \LaTeX{} file that really does have no
+\cmdinvoke{begin}{document} command in it, and \LaTeX{} will produce
+this error, quite correctly.  \LaTeX{} \emph{needs}
+\cmdinvoke{begin}{document} so as to know when to execute the commands
+that finish off the document preamble.
+
+Other than that, the error can occur as a result of an error of yours,
+of a corrupt \extension{aux} file, or of a buggy class or package.
+
+The errors you might commit are absent-mindedly typing a document
+command (such as \csx{section}) in the preamble of your document,
+missing the comment marker from the beginning of a line, or giving too
+many arguments to one of the setup commands related to the class or a
+package that you have loaded.
+
+A corrupt \extension{aux} file might be due to any number of things;
+delete the file and to run \LaTeX{} again, twice.  If the error
+recurs, it's probably due to a buggy class or package.
+
+If the error occurs while \LaTeX{} is reading a class or package, then
+there's probably a bug in the file.  The author of the class or
+package stands the best chance of finding the bug, but with luck you
+(or someone you ask on a mailing list or on \Newsgroup{comp.text.tex})
+will be able to spot the problem and provide a work-around.  Always
+report such bugs, even if you have found a work-around.
+
+\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}
+is reporting something pretty fundamental (document base font size not
+set up).  While this \emph{can}, as the message implies, be due to a
+broken class file, the more common cause is that you have simply
+forgotten to put a \csx{documentclass} command in your document.
+
+\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, 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}
+  \renewcommand{\hmmax}{0}
+\end{verbatim}
+\end{quote}
+and then steadily reduce the bold families, starting with
+\begin{quote}
+\begin{verbatim}
+  \renewcommand{\bmmax}{3}
+\end{verbatim}
+\end{quote}
+until (with a bit of luck) the error goes away.
+\begin{ctanrefs}
+\item[bm.sty]Distributed as part of \CTANref{2etools}
+\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{enumerate}
+\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{enumerate}
+\end{tabular}
+\end{verbatim}
+\end{quote}
+(Note the deliberate introduction of a space as part of the command,
+marked with asterisks.)
+
+However, the error 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 their 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-optionclash]{Option clash for package}
+
+So you've innocently added:
+\begin{quote}
+\cmdinvoke{usepackage}[draft]{graphics}
+\end{quote}
+to your document, and \LaTeX{} responds with
+\begin{wideversion}
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Option clash for package graphics.
+\end{verbatim}
+\end{quote}
+\end{wideversion}
+\begin{narrowversion}
+\begin{quote}
+\begin{verbatim}
+! LaTeX Error: Option clash for package
+                                    graphics.
+\end{verbatim}
+\end{quote}
+\end{narrowversion}
+
+The error is a complaint about loading a package % ! line break
+\emph{with options}, more than once (\LaTeX{} doesn't actually examine
+what options there are: it complains because it can't do anything with
+the multiple sets of options).  You can load a package
+any number of times, with no options, and \LaTeX{} will be happy, 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}.
+
+More trickily, 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-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.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\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/}), as is some of the
+project's experimental code
+(see \URL{http://www.latex-project.org/code.html}, which allows you to
+read the project's source repository).  You can
+participate in discussions of the future of \LaTeX{} through the
+mailing list \texttt{latex-l}.  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[\nothtml{\rmfamily}\LaTeX{} project publications]\CTANref{ltx3pub}
+\end{ctanrefs}
+
+\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 one can rely on being available.  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.
+  
+  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.
+
+  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/mimetex.html}{Mime\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/mimetex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt">
+\end{verbatim}
+\end{wideversion}
+\begin{narrowversion}
+\begin{verbatim}
+<img src="../cgi-bin/mimetex.cgi?f(x)=
+   \int\limits_{-\infty}^xe^{-t^2}dt">
+\end{verbatim}
+\end{narrowversion}
+\end{quote}
+\end{description}
+\begin{ctanrefs}
+\item[GELLMU]\CTANref{gellmu}
+\item[MimeTeX]\CTANref{MimeTeX}
+\item[TeX4HT]\CTANref{tex4ht}
+\end{ctanrefs}
+
+\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.
+\begin{ctanrefs}
+\item[MetaType1]\CTANref{metatype1}
+\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.  A simpler package in a similar spirit is called
+\href{http://www.activetex.org/}{\Package{InstantPreview}} and makes
+use of a continuously running copy of \TeX{}
+(under the moniker of \texttt{TeX daemon}) instead of dumping formats to
+achieve its speed.
+
+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]Browse \CTANref{preview-latex}
+\item[texmacs]Browse \CTANref{texmacs}
+\end{ctanrefs}
+
+\Question[Q-ant]{The \textsf{ANT} typesetting system}
+
+Achim Blumensath's \href{http://ant.berlios.de}{\textsf{ANT}} project,
+in contrast to \NTS{}, 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-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, its
+development 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 was
+started, to produce a program 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.
+
+The latest news (from Euro\TeX{} 2006) is that development of Omega is
+picking up again, in parallel with research into what the (new)
+authors consider a rational scheme for supporting \TeX{}-style
+typesetting.  The new system is to be known as Omega-2
+(\latexhtml{\ensuremath{\Omega_2}}{Omega subscript 2}), and is being
+designed in a modular fashion so that support of new facilities (such
+as use of advanced OpenType fonts) can be added in a relatively
+straightforward fashion.
+
+The work done in the Aleph project is also being carried forward in
+the \Qref*{\LuaTeX{}}{Q-luatex} project.
+
+\Question[Q-luatex]{\PDFTeX{} becomes \LuaTeX{}}
+
+As is said elsewhere in these \acro{FAQ}s, development of
+\Qref*{\PDFTeX{}}{Q-whatpdftex} is ``in essence'' complete~---
+development of new facilities continues, but the limitations of the
+present structure impose a strong limit on what facilities are
+possible.  (The \PDFTeX{} team has announced that no further
+developments will be added after the release of \PDFTeX{} 1.50.0,
+which will be the next major release.)
+
+In this context, the idea of \LuaTeX{} arose.
+\href{http://www.lua.org/}{\ProgName{Lua}} is a script
+language, designed to offer an interpreter with a very small
+``footprint'', so it is rather easy to build it into other
+applications.  So \LuaTeX{} was launched as a \PDFTeX{}
+executable with a \ProgName{Lua} interpreter built into it.
+
+A \href{http://www.luatex.org/}{\LuaTeX{} project} is now proceeding
+(with monetary support from various sources) and is pursuing avenues
+that many of the other
+current projects have in their sights, notably Unicode character
+representations and support for OpenType fonts.  Work is also in hand
+to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}.
+
+The next release of \texlive{} (due in July 2008) and \miktex{}
+version 2.8 (no current release date) will incorporate \LuaTeX{}.
+\CONTeXT{} distributions can already make use of it.
+
+\Question[Q-xetex]{The \xetex{} project}
+
+\xetex{} (by Jonathan Kew) is a successor to the shareware \TeX{}/\acro{GX}
+program for Macintoshes. It is a Unicode-based (\acro{UTF}-8) TeX
+implementation which is able to make use of Mac~\acro{OS}~X \acro{AAT}
+(Apple Advanced Typography) \extension{dfonts} and OpenType fonts.  It
+uses Apple's Quartz system (which facilitates the afore-mentioned font
+access) to generate \acro{PDF} output.  \xetex{} supports Unicode
+character sets and bidirectional typesetting, and is widely used by
+people studying linguistics, as well as an increasing range of people
+working in other fields.
+
+A Linux and Unix-system version is available in \texlive{}~2007; that
+version (of course) relies on OpenType fonts alone.  A version is
+planned for \miktex{} version 2.7 (currently planned for December 2007).
+
+The project has a \href{http://scripts.sil.org/xetex}{web site} for
+the user who wants more than this simple answer, and you can also sign
+up to a \href{http://www.tug.org/mailman/listinfo/xetex}{mailing list}.
+
+\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); and 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
+fewer 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), implemented in a simpler style language, with
+coherent multilingual capabilities.
+
+Of the direct \BibTeX{} replacements, the only one whose authors have
+sufficient confidence to submit to \acro{CTAN} is Cross\TeX{}.
+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.
+
+Cross\TeX{}'s team respond to queries, and seem well aware of the
+need for multilingual support.  Cross\TeX{} is probably a development
+to watch.
+
+Two interesting alternative approaches, that the author has
+investigated, are \Package{amsrefs} and \Package{biblatex}.
+\Package{Amsrefs} does away with \BibTeX{} altogether, while
+\Package{biblatex} makes rather limited use of \BibTeX{}.  Both are
+heavily dependent on \LaTeX{}'s support.
+
+\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,
+
+\Package{Biblatex} uses \BibTeX{} more-or-less as normal, but with
+\Package{biblatex}'s own style; the style of citations and of the
+bibliography itself is determined by the way your \Package{biblatex}
+style has been set up.  This structure eliminates the collections of
+\BibTeX{} styles, at a stroke; the package 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
+comes with answers to many of the questions asked in the bibliography
+sections of these \acro{FAQ}s.
+
+\Package{Biblatex} is 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 set of expert
+users is already establishing itself.
+\begin{ctanrefs}
+\item[amsrefs.sty]\CTANref{amsrefs}
+\item[biblatex.sty]\CTANref{biblatex}
+\item[\nothtml{\rmfamily}CrossTeX]\CTANref{crosstex}
+\end{ctanrefs}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%
+% This is the last section, and is to remain the last section...
+\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-latexbug]{Reporting a \LaTeX{} bug}
+
+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
+should run 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.
+
+You now have two possible ways to proceed: either create a mail report
+to send to the bug processing mechanism (5, below), or submit your bug
+report via the web (7, below).
+
+\nothtml{\noindent}\textbf{5.} Process the bug-report creation file, using \LaTeX{} itself:
+\begin{verbatim}
+  latex latexbug
+\end{verbatim}
+\File{latexbug} asks you some questions, and then lets you describe
+the bug you've found.  It produces an output file \File{latexbug.msg},
+which includes the details you've supplied, your ``minimum'' example
+file, and the log file you got after running the example.  (I always
+need to edit the result before submitting it: typing text into
+\File{latexbug} isn't much fun.)
+
+\nothtml{\noindent}\textbf{6.} Mail the resulting file to
+\Email{latex-bugs@latex-project.org}; the subject line of your email
+should be the same as the bug title you gave to \File{latexbug}.  The
+file \File{latexbug.msg} should be included into your message in-line:
+attachments are likely to be rejected by the bug processor.
+
+\nothtml{\noindent}\textbf{7.} Connect to the
+% beware 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); note
+that members of the \LaTeX{} team \emph{need} your name and email address, as
+they may need to discuss the bug with you, or to advise you of a
+work-around.
+
+\htmlignore
+\par
+\endhtmlignore
+\Question[Q-bug]{What to do if you find a bug}
+\htmlignore
+\par
+\endhtmlignore
+%
+% This here isn't a reference to a question...
+\label{lastquestion}
+
+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, you could try
+contacting the author (if you can find a contact address).  However,
+it's generally best to treat any package as unsupported, in the first
+instance, and only try the author \emph{after} mailing list/news group
+support has failed you.
+
+If you've found a bug in \LaTeXo{}, or some other such unsupported
+software, you may find help or
+\emph{de facto} support on a newsgroup such as
+\Newsgroup{comp.tex.tex} or on a mailing list such as
+\mailto{texhax@tug.org}; be careful to include a % ! line wrap
+\Qref*{code example}{Q-minxampl} of the
+failure, if relevant.
+
+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}.
+
+
+%%% Local Variables: 
+%%% mode: latex
+%%% TeX-master: t
+%%% End: 
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faqfont.cfg b/Master/texmf-dist/doc/generic/FAQ-en/faqfont.cfg
new file mode 100644
index 00000000000..ae36c3730e0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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/Master/texmf-dist/doc/generic/FAQ-en/faqfont.cfg.cmfonts b/Master/texmf-dist/doc/generic/FAQ-en/faqfont.cfg.cmfonts
new file mode 100644
index 00000000000..1849c021285
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faqfont.cfg.cmfonts
@@ -0,0 +1,5 @@
+%
+% null FAQ configuration file: leaves LaTeX default use of cm* fonts
+\typeout{FAQ -- Typesetting using Computer Modern fonts}
+\@ifundefined{Dings}{\let\Dings\relax}{}
+\boldmathavailtrue
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex
new file mode 100644
index 00000000000..cdfe79c55b8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex
@@ -0,0 +1,144 @@
+%
+% 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}
+\CTANfile{f-byname}{FILES.byname}
+\CTANfile{f-last7}{FILES.last07days}
+\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{anonchap}{macros/latex/contrib/misc/anonchap.sty}
+\CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex}
+\CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk}
+\CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf}
+\CTANfile{belleek}{fonts/belleek/belleek.zip}
+\CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf}
+\CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex}
+\CTANfile{bold-extra}{macros/latex/contrib/misc/bold-extra.sty}
+\CTANfile{braket}{macros/latex/contrib/misc/braket.sty}
+\CTANfile{btxmactex}{macros/eplain/tex/eplain/btxmac.tex}
+\CTANfile{cancel}{macros/latex/contrib/misc/cancel.sty}
+\CTANfile{capt-of}{macros/latex/contrib/misc/capt-of.sty}
+\CTANfile{catalogue}{help/Catalogue/catalogue.html}
+\CTANfile{cat-licences}{help/Catalogue/licenses.html}
+\CTANfile{changepage}{macros/latex/contrib/misc/changepage.sty}
+\CTANfile{chngcntr}{macros/latex/contrib/misc/chngcntr.sty}
+\CTANfile{chngpage}{macros/latex/contrib/misc/chngpage.sty}
+\CTANfile{clsguide}{macros/latex/doc/clsguide.pdf}
+%\CTANfile{compan-ctan}{info/companion.ctan}
+\CTANfile{context-tmf}{macros/context/current/cont-tmf.zip}
+\CTANfile{dblfloatfix}{macros/latex/contrib/misc/dblfloatfix.sty}
+\CTANfile{dvitype}{systems/knuth/dist/texware/dvitype.web}
+\CTANfile{edmetrics}{systems/mac/textures/utilities/EdMetrics.sea.hqx}
+\CTANfile{epsf}{macros/generic/epsf/epsf.tex}
+\CTANfile{epslatex_pdf}{info/epslatex/english/epslatex.pdf}
+\CTANfile{epslatex_ps}{info/epslatex/english/epslatex.ps}
+\CTANfile{eucal}{fonts/amsfonts/latex/eucal.sty}
+\CTANfile{excludeonly}{macros/latex/contrib/misc/excludeonly.sty}
+\CTANfile{figsinlatex}{obsolete/info/figsinltx.ps}
+\CTANfile{finplain}{biblio/bibtex/contrib/misc/finplain.bst}
+\CTANfile{fix-cm}{macros/latex/unpacked/fix-cm.sty}
+\CTANfile{fncylab}{macros/latex/contrib/misc/fncylab.sty}
+\CTANfile{fntguide.pdf}{macros/latex/doc/fntguide.pdf}
+\CTANfile{fontdef}{macros/latex/base/fontdef.dtx}
+\CTANfile{fontmath}{macros/latex/unpacked/fontmath.ltx}
+\CTANfile{framed}{macros/latex/contrib/misc/framed.sty}
+\CTANfile{gentle}{info/gentle/gentle.pdf}
+\CTANfile{gkpmac}{systems/knuth/local/lib/gkpmac.tex}
+\CTANfile{hypernat}{macros/latex/contrib/misc/hypernat.sty}
+\CTANfile{ifmtarg}{macros/latex/contrib/misc/ifmtarg.sty}
+\CTANfile{import}{macros/latex/contrib/misc/import.sty}
+\CTANfile{ispell}{support/ispell/ispell-3.2.06.tar.gz}
+\CTANfile{l2tabuen}{info/l2tabu/english/l2tabuen.pdf}
+\CTANfile{l2tabuen.src}{info/l2tabu/english/l2tabuen.tex}
+\CTANfile{latex209-base}{obsolete/macros/latex209/distribs/latex209.tar.gz}
+\CTANfile{latex-classes}{macros/latex/base/classes.dtx}
+\CTANfile{latex-source}{macros/latex/base/source2e.tex}
+\CTANfile{latexcount}{support/latexcount/latexcount.pl}
+\CTANfile{letterspacing}{macros/generic/misc/letterspacing.tex}
+\CTANfile{lshort}{info/lshort/english/lshort.pdf}
+\CTANfile{ltablex}{macros/latex/contrib/ltablex/ltablex.sty}
+\CTANfile{ltxguide}{macros/latex/base/ltxguide.cls}
+\CTANfile{ltxtable}{macros/latex/contrib/carlisle/ltxtable.tex}
+\CTANfile{lw35nfss-zip}{macros/latex/required/psnfss/lw35nfss.zip}
+\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{metafp-pdf}{info/metafont/metafp/metafp.pdf}
+\CTANfile{mf-beginners}{info/metafont/beginners/metafont-for-beginners.pdf}
+\CTANfile{mf-list}{info/metafont-list}
+\CTANfile{miktex-setup}{systems/win32/miktex/setup/setup.exe}
+\CTANfile{miktex-usb}{info/MiKTeX+Ghostscript+GSview+USB-drive-HOWTO.txt}
+\CTANfile{mil}{info/mil/mil.pdf}
+\CTANfile{mil-short}{info/Math_into_LaTeX-4/Short_Course.pdf}
+\CTANfile{modes-file}{fonts/modes/modes.mf}
+\CTANfile{morefloats}{macros/latex/contrib/misc/morefloats.sty}
+\CTANfile{mpsproof}{graphics/metapost/contrib/misc/mpsproof.tex}
+\CTANfile{mtw}{info/makingtexwork/mtw-1.0.1-html.tar.gz}
+\CTANfile{multind}{macros/latex209/contrib/misc/multind.sty}
+\CTANfile{musixtex-type1}{fonts/musixtex/ps-type1/musixps-unix.tar.gz}
+\CTANfile{needspace}{macros/latex/contrib/misc/needspace.sty}
+\CTANfile{nextpage}{macros/latex/contrib/misc/nextpage.sty}
+\CTANfile{notoccite}{macros/latex/contrib/misc/notoccite.sty}
+\CTANfile{noTeX}{biblio/bibtex/utils/misc/noTeX.bst}
+\CTANfile{nopageno}{macros/latex/contrib/carlisle/nopageno.sty}
+\CTANfile{numline}{macros/latex/contrib/numline/numline.sty}
+\CTANfile{optional}{macros/latex/contrib/misc/optional.sty}
+\CTANfile{parskip}{macros/latex/contrib/misc/parskip.sty}
+\CTANfile{patch}{macros/generic/misc/patch.doc}
+\CTANfile{path}{macros/latex/contrib/misc/path.sty}
+\CTANfile{pdftex}{systems/pdftex/pdftex.zip}
+\CTANfile{pdftex-oztex}{nonfree/systems/mac/pdftex/pdftex_for_oztex.sit.bin}
+\CTANfile{picins-summary}{macros/latex209/contrib/picins/picins.txt}
+\CTANfile{pk300}{fonts/cm/pk/pk300.zip}
+\CTANfile{pk300w}{fonts/cm/pk/pk300w.zip}
+\CTANfile{printlen}{macros/latex/contrib/misc/printlen.sty}
+\CTANfile{removefr}{macros/latex/contrib/fragments/removefr.tex}
+\CTANfile{resume}{obsolete/macros/latex209/contrib/resume/resume.sty}
+\CTANfile{savesym}{macros/latex/contrib/savesym/savesym.sty}
+\CTANfile{screensty}{macros/latex209/contrib/misc/screen.sty}
+\CTANfile{selectp}{macros/latex/contrib/misc/selectp.sty}
+\CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}
+\CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.ps}
+\CTANfile{sober}{macros/latex209/contrib/misc/sober.sty}
+\CTANfile{tabls}{macros/latex/contrib/misc/tabls.sty}
+\CTANfile{tex2bib}{biblio/bibtex/utils/tex2bib/tex2bib}
+\CTANfile{tex2bib-doc}{biblio/bibtex/utils/tex2bib/README}
+\CTANfile{tex4ht}{support/TeX4ht/tex4ht-all.zip}
+\CTANfile{texnames}{info/biblio/texnames.sty}
+\CTANfile{texsis-index}{macros/texsis/index/index.tex}
+\CTANfile{threeparttable}{macros/latex/contrib/misc/threeparttable.sty}
+\CTANfile{titleref}{macros/latex/contrib/misc/titleref.sty}
+\CTANfile{topcapt}{macros/latex/contrib/misc/topcapt.sty}
+\CTANfile{tracking}{macros/latex/contrib/tracking/tracking.sty}
+\CTANfile{ttb-pdf}{info/bibtex/tamethebeast/ttb_en.pdf}
+\CTANfile{tth}{nonfree/support/tth/dist/tth_C.tgz}
+\CTANfile{type1ec}{fonts/ps-type1/cm-super/type1ec.sty}
+\CTANfile{ukhyph}{language/hyphenation/ukhyphen.tex}
+\CTANfile{upquote}{macros/latex/contrib/upquote/upquote.sty}
+\CTANfile{faq-a4}{help/uk-tex-faq/newfaq.pdf}
+\CTANfile{faq-letter}{help/uk-tex-faq/letterfaq.pdf}
+\CTANfile{ulem}{macros/latex/contrib/misc/ulem.sty}
+\CTANfile{url}{macros/latex/contrib/misc/url.sty}
+\CTANfile{underscore}{macros/latex/contrib/misc/underscore.sty}
+\CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty}
+\CTANfile{verbdef}{macros/latex/contrib/misc/verbdef.sty}
+\CTANfile{version}{macros/latex/contrib/misc/version.sty}
+\CTANfile{versions}{macros/latex/contrib/versions/versions.sty}
+\CTANfile{vertbars}{macros/latex/contrib/misc/vertbars.sty}
+\CTANfile{vf-howto}{info/virtualfontshowto/virtualfontshowto.txt}
+\CTANfile{vf-knuth}{info/knuth/virtual-fonts}
+\CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}
+\CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf}
+\CTANfile{vruler}{macros/latex/contrib/misc/vruler.sty}
+\CTANfile{wujastyk-txh}{digests/texhax/txh/wujastyk.txh}
+\CTANfile{xampl-bib}{biblio/bibtex/distribs/doc/xampl.bib}
+\CTANfile{xtexcad}{nonfree/graphics/xtexcad/xtexcad-2.4.1.tar.gz}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html
new file mode 100644
index 00000000000..79fddff663a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label 2colfloat</title>
+</head><body>
+<h3>Placing two-column floats at bottom of page</h3>
+<p/>You specified placement &lsquo;<code>[htbp]</code>&rsquo; for your full-width figure or
+table, but they always get placed at the top of the page...  Well,
+it <em>is</em> what the documentation says: LaTeX, unadorned, only
+allows full-width floats at the top of a page, or occupying (part of) a
+float page.
+<p/>The <i>stfloats</i> package ameliorates the situation somewhat, and
+makes LaTeX honour &lsquo;[b]&rsquo; placement as well; the
+<i>dblfloatfix</i> package combines a tidied version of the changes
+made in <i>stfloats</i> with the
+
+  <a href="FAQ-2colfltorder.html">float ordering corrections</a> defined in
+  <i>fixltx2e</i>.
+<p/>A particular problem with <i>stfloats</i> and <i>dblfloatfix</i>
+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 &ldquo;entangled&rdquo; (particularly if you&rsquo;re using
+<i>dblfloatfix</i> that ensures that the early-specified bottom
+float is set <em>before</em> any single column floats).
+<p/>(The FAQ team doesn&rsquo;t know of any package that will make
+LaTeX honour &lsquo;[h]&rsquo; placement of double-column floats, but the
+<i>midfloat</i> package can be pressed into service to provide
+something approximating the effect it would have.)
+<dl>
+<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/dblfloatfix.sty">macros/latex/contrib/misc/dblfloatfix.sty</a>
+<dt><tt><i>stfloats.sty, midfloat.sty</i></tt><dd>Distributed as part of
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html
new file mode 100644
index 00000000000..a16ff8fe4dc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label 2colfltorder</title>
+</head><body>
+<h3>Two-column float numbers out of order</h3>
+<p/>When LaTeX can&rsquo;t place a float immediately, it places it on one of
+several &ldquo;defer&rdquo; lists.  If another float of the same type comes
+along, and the &ldquo;defer&rdquo; list for that type still has something in it,
+the later float has to wait for everything earlier in the list.
+<p/>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.
+<p/>The LaTeX team recognise the problem, and provides a package
+(<i>fixltx2e</i>) to deal with it.  <i>Fixltx2e</i> amalgamates
+the two defer lists, so that floats don&rsquo;t get out of order.
+<p/>For those who are still running an older LaTeX distribution, the
+package <i>fix2col</i> should serve.  This package (also by a
+member of the LaTeX team) was the basis of the relevant part of
+<i>fixltx2e</i>.  The functionality has also been included in
+<i>dblfloatfix</i>, which also has code to place full-width floats
+at <a href="FAQ-2colfloat.html"><code>[b]</code> placement</a>.
+<p/>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.
+<dl>
+<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/dblfloatfix.sty">macros/latex/contrib/misc/dblfloatfix.sty</a>
+<dt><tt><i>fix2col.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>)
+<dt><tt><i>fixltx2e.sty</i></tt><dd>Part of the LaTeX distribution
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html
new file mode 100644
index 00000000000..c87a5c088e6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html
@@ -0,0 +1,124 @@
+<head>
+<title>UK TeX FAQ -- question label 2letterfontcmd</title>
+</head><body>
+<h3>What&rsquo;s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</h3>
+<p/>The font-selection commands of LaTeX 2.09 were <code>\</code><code>rm</code>, <code>\</code><code>sf</code>,
+<code>\</code><code>tt</code>, <code>\</code><code>it</code>, <code>\</code><code>sl</code>, <code>\</code><code>em</code> and <code>\</code><code>bf</code>; they were modal
+commands, so you used them as:
+<blockquote>
+<pre>
+{\bf Fred} was {\it here\/}.
+</pre>
+</blockquote><p>
+with the font change enclosed in a group, so as to limit its effect;
+note the italic correction command <code>\</code><code>/</code> that was necessary at the
+end of a section in italics.
+<p/>At the release of LaTeX2e 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,
+<em>with their LaTeX 2.09 semantics</em>.  Those semantics were part of
+the reason they were deprecated: each <code>\</code><em><code>xx</em></code> overrides
+any other font settings, keeping only the size.  So, for example,
+<blockquote>
+<pre>
+{\bf\it Here we are again\/}
+</pre>
+</blockquote><p>
+ignores <code>\</code><code>bf</code> and produces text in italic, medium weight (and the
+italic correction has a real effect), whereas
+<blockquote>
+<pre>
+{\it\bf happy as can be\/}
+</pre>
+</blockquote><p>
+ignore <code>\</code><code>it</code> and produces upright text at bold weight (and the
+italic correction has nothing to do).  The same holds if you mix
+LaTeX2e font selections with the old style commands:
+<blockquote>
+<pre>
+\textbf{\tt all good friends}
+</pre>
+</blockquote><p>
+ignores the <code>\</code><code>textbf</code> that encloses the text, and produces
+typewriter text at medium weight.
+<p/>So why are these commands deprecated? &mdash; it is because of confusions
+such as that in the last example.  The alternative (LaTeX2e)
+commands are discussed in the rest of this answer.
+<p/>LaTeX2e&rsquo;s font commands come in two forms: modal commands and
+text-block commands.  The default set of modal commands offers weights
+<code>\</code><code>mdseries</code> and <code>\</code><code>bfseries</code>, shapes <code>\</code><code>upshape</code>,
+<code>\</code><code>itshape</code>, <code>\</code><code>scshape</code> and <code>\</code><code>slshape</code>, and families
+<code>\</code><code>rmfamily</code>, <code>\</code><code>sffamily</code> and <code>\</code><code>ttfamily</code>.  A font selection
+requires a family, a shape and a series (as well as a size, of
+course).  A few examples
+<blockquote>
+
+<pre>
+{\bfseries\ttfamily and jolly good company!}
+</pre>
+</blockquote><p>
+produces bold typewriter text (but note the lack of a 
+
+  <a href="FAQ-bold-extras.html">bold typewriter font</a>
+in the default Computer Modern fonts), or
+<blockquote>
+
+<pre>
+{\slshape\sffamily Never mind the weather\/}
+</pre>
+</blockquote><p>
+(note the italic correction needed on slanted fonts, too).
+<p/>LaTeX2e&rsquo;s text block commands take the first two letters of the
+modal commands, and form a <code>\</code><code>text</code><em><code>xx</em></code> command from
+them.  Thus <code>\</code><code>bfseries</code> becomes <code>\</code><code>textbf{</code><em>text</em><code>}</code>,
+<code>\</code><code>itshape</code> becomes <code>\</code><code>textit{</code><em>text</em><code>}</code>, and <code>\</code><code>ttfamily</code>
+becomes <code>\</code><code>texttt{</code><em>text</em><code>}</code>.  Block commands may be nested, as:
+<blockquote>
+<pre>
+\textit{\textbf{Never mind the rain}}
+</pre>
+</blockquote><p>
+to produce bold italic text (note that the block commands supply
+italic corrections where necessary), and they be nested with the
+LaTeX2e modal commands, too:
+<blockquote>
+
+<pre>
+\texttt{\bfseries So long as we're together}
+</pre>
+</blockquote><p>
+for bold typewriter, or
+<blockquote>
+
+<pre>
+{\slshape \textbf{Whoops!  she goes again}\/}
+</pre>
+</blockquote><p>
+for a bold slanted instance of the current family (note the italic
+correction applied at the end of the modal command group, again).
+<p/>The new commands (as noted above) override commands of the same type.
+In almost all cases, this merely excludes ludicrous ideas such as
+&ldquo;upright slanted&rdquo; fonts, or &ldquo;teletype roman&rdquo; fonts.  There are a
+couple of immediate oddities, though.  The first is the conflict
+between <code>\</code><code>itshape</code> (or <code>\</code><code>slshape</code>) and <code>\</code><code>scshape</code>: while many
+claim that an italic small-caps font is typographically unsound, such
+fonts do exist.  Daniel Taupin&rsquo;s <i>smallcap</i> package enables
+use of the instances in the <a href="FAQ-ECfonts.html">EC fonts</a>, and
+similar techniques could be brought to bear on many other font sets.
+The second is the conflict between <code>\</code><code>upshape</code> and <code>\</code><code>itshape</code>:
+Knuth actually offers an upright-italic font which LaTeX uses for
+the &ldquo;&pound;&rdquo; symbol in the default font set.  The combination is
+sufficiently weird that, while there&rsquo;s a defined font shape, no
+default LaTeX commands exist; to use the shape, the (eccentric) user
+needs LaTeX&rsquo;s simplest font selection commands:
+<blockquote>
+
+<pre>
+{\fontshape{ui}\selectfont Tra la la, di dee}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>smallcap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.zip">macros/latex/contrib/smallcap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smallcap/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html
new file mode 100644
index 00000000000..77549595a86
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html
@@ -0,0 +1,24 @@
+<head>
+<title>UK TeX FAQ -- question label 8000</title>
+</head><body>
+<h3>Mismatched mode ljfour and resolution 8000</h3>
+<p/>You&rsquo;re running <i>dvips</i>, and you encounter a stream of error
+messages, starting with &ldquo;<code>Mismatched mode</code>&rdquo;.  The mode is the
+default used in your installation &mdash; it&rsquo;s set in the <i>dvips</i>
+configuration file, and <code>ljfour</code> is commonest (since it&rsquo;s the
+default in most distributions), but not invariable.
+<p/>The problem is that <i>dvips</i> has encountered a font for which
+it must generate a bitmap (since it can&rsquo;t find it in Type 1 format),
+and there is no proforma available to provide instructions to give to
+Metafont.
+<p/>So what to do?  The number 8000 comes from the &lsquo;<code>-Ppdf</code>&rsquo; option
+to <i>dvips</i>, which you might have found from the answer
+
+<a href="FAQ-fuzzy-type3.html">&ldquo;wrong type of fonts&rdquo;</a>.  The obvious
+solution is to switch to the trivial substitute &lsquo;<code>-Pwww</code>&rsquo;,
+which selects the necessary type 1 fonts for PDF generation,
+but nothing else: however, this will leave you with undesirable bitmap
+fonts in your PDF file.  The &ldquo;proper&rdquo; solution is to find a
+way of expressing what you want to do, using type 1 fonts.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html
new file mode 100644
index 00000000000..18d62bc7e03
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label AMSpkg</title>
+</head><body>
+<h3>What are the AMS packages (AMSTeX, <em>etc</em>.)?</h3>
+
+<p/>AMSTeX is a TeX macro package, originally written by Michael Spivak for
+the American Mathematical Society (AMS) during 1983&ndash;1985 and
+is described in the book &ldquo;<a href="FAQ-books.html">The Joy of TeX</a>&rdquo;.
+It is based on Plain TeX, 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.
+<p/>As LaTeX increased in popularity, authors asked to submit papers to
+the AMS in LaTeX, and so the AMS developed
+AMSLaTeX, which is a
+collection of LaTeX packages and classes that offer authors most of
+the functionality of AMSTeX.
+The AMS no longer recommends the use of AMSTeX, and urges
+its users to use AMSLaTeX instead.
+ 
+<dl>
+<dt><tt><i>AMSTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/amstex.zip">macros/amstex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/amstex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/amstex/">browse</a>)
+<dt><tt><i>AMSLaTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html
new file mode 100644
index 00000000000..7591756e032
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label BibTeXing</title>
+</head><body>
+<h3>BibTeX Documentation</h3>
+<p/>BibTeX, a program originally designed to produce bibliographies in
+conjunction with LaTeX, is explained in Section 4.3 and Appendix B
+of Leslie Lamport&rsquo;s LaTeX manual.
+The document &ldquo;BibTeXing&rdquo;, contained in the file <i>btxdoc.tex</i>,
+expands on the chapter in Lamport&rsquo;s book.  <em>The LaTeX Companion</em>
+also has information on BibTeX and writing BibTeX style files.
+(See <a href="FAQ-books.html">TeX-related books</a> for details of both
+books.)
+<p/>The document &ldquo;Designing BibTeX Styles&rdquo;, contained in the file
+<i>btxhak.tex</i>, explains the postfix stack-based language used to
+write BibTeX styles (<i>.bst</i> files). The file <i>btxbst.doc</i>
+is the template for the four standard styles (<i>plain</i>,
+<i>abbrv</i>, <i>alpha</i>, and <i>unsrt</i>). It also
+contains their documentation.  The complete BibTeX documentation
+set (including all the files above) is available on CTAN.
+<p/>A useful tutorial of the whole process of using BibTeX is Nicolas
+Markey&rsquo;s &ldquo;<em>Tame the BeaST (The B to X of BibTeX)</em>&rdquo;, which
+may also be found on CTAN.  A summary and FAQ
+(<i>btxFAQ</i>), by Michael Shell and David Hoadley, is also to be
+recommended.
+<dl>
+<dt><tt><i>BibTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>)
+<dt><tt><i>BibTeX documentation, in PDF</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/doc/">browse</a>)
+<dt><tt><i>btxFAQ.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc/btxFAQ.pdf">biblio/bibtex/contrib/doc/btxFAQ.pdf</a>
+<dt><tt><i>Tame the BeaST</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/bibtex/tamethebeast/ttb_en.pdf">info/bibtex/tamethebeast/ttb_en.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html
new file mode 100644
index 00000000000..42f4b0a63f8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html
@@ -0,0 +1,45 @@
+<head>
+<title>UK TeX FAQ -- question label CD</title>
+</head><body>
+<h3>The TeX collection</h3>
+<p/>If you don&rsquo;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.
+<p/>The TeX collection provides this, together with
+ready-to-run TeX systems for various architectures.  Contents of
+the collection are:
+<ul>
+<li> The TeX Live installation disc (a CD) provides TeX
+  systems for use on GNU-Linux, MacOS/X and Win-32
+  architectures;
+<li> The TeX Live &lsquo;Live&rsquo; disc (a DVD) providing TeX for
+  a wider range of architectures;
+<li> MacTeX: an easy to install TeX system for MacOS/X, based
+  on TeX Live, and including the 
+  <a href="http://www.uoregon.edu/~koch/texshop/">texshop front-end</a>
+  and other tools;
+<li> ProTeXt: an easy to install TeX system for Windows, based
+  on MiKTeX, and including an &lsquo;active&rsquo; document to guide
+  installation; and
+<li> A snapshot of CTAN.
+</ul>
+A fair number of national TeX User Groups, as well as 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 <a href="FAQ-TUGstar.html">TUG</a>.
+<p/>You may also download disc images from CTAN; the installation
+disc, ProTeXt and MacTeX are all separately available.  Beware:
+they are all pretty large downloads.
+<p/>More details of the collection are available from its own
+  <a href="http://www.tug.org/texcollection/">web page</a>
+  on the TUG site.
+
+<dl>
+<dt><tt><i>MacTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">systems/mac/mactex/</a>
+<dt><tt><i>ProTeXt</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/protext/">systems/win32/protext/</a>
+<dt><tt><i>TeXlive install image</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a>
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html
new file mode 100644
index 00000000000..17985361f8d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html
@@ -0,0 +1,74 @@
+<head>
+<title>UK TeX FAQ -- question label ECfonts</title>
+</head><body>
+<h3>What are the EC fonts?</h3>
+<p/>A font consists of a number of <em>glyphs</em>.  In order that the
+glyphs may be printed, they are <a href="FAQ-whatenc.html"><em>encoded</em></a>, 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&rsquo;s using before selecting a
+particular glyph.
+<p/>When TeX version 3 arrived, most of the excuses for the
+eccentricity of Knuth&rsquo;s encodings went away, and at TUG&rsquo;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 &lsquo;most&rsquo;
+European languages that use Latin alphabets, in the sense of including
+all accented letters needed.  (Knuth&rsquo;s CMR fonts missed things
+necessary for Icelandic and Polish, for example, but the Cork
+fonts have them.  Even Cork&rsquo;s coverage isn&rsquo;t complete: it misses
+letters from Romanian, Eastern and Northern Sami, and Welsh, at
+least.  The Cork encoding does contain &ldquo;NG&rdquo; glyphs that
+allows it to support Southern Sami.)  LaTeX refers to the
+Cork encoding as T1, and
+provides the means to use fonts thus encoded to avoid problems with
+the interaction of accents and hyphenation 
+(see <a href="FAQ-hyphenaccents.html">hyphenation of accented words</a>).
+<p/>The only Metafont-fonts that conform to the Cork encoding are the
+EC fonts.  They look CM-like, though their metrics
+differ from CM-font metrics in several areas.  The fonts are
+now regarded as &lsquo;stable&rsquo; (in the same sense that the CM fonts
+are stable: their metrics are unlikely ever to change).  Their serious
+disadvantages for the casual user are their size (each EC font
+is roughly twice the size of the corresponding CM font), and
+there are far more of them than there are CM fonts.  The simple
+number of fonts has acted as a disincentive to the production of Adobe
+Type 1 versions of the fonts, but several commercial suppliers offer
+EC or
+EC-equivalent fonts in type 1 or TrueType form &mdash; see
+
+<a href="FAQ-commercial.html">commercial suppliers</a>.  Free 
+<a href="FAQ-textrace.html">auto-traced versions</a> (the CM-super
+and the LGC fonts), and the Latin Modern series (rather
+directly generated from Metafont sources), are available.
+<p/>
+
+
+Note that the Cork encoding doesn&rsquo;t cover mathematics (and neither do
+&ldquo;T1-encoded&rdquo; font families, of course).  If you&rsquo;re using
+Computer-Modern-alike fonts, this doesn&rsquo;t actually matter: your system
+will have the original Computer Modern fonts, which cover &lsquo;basic&rsquo;
+TeX mathematics; more advanced mathematics are likely to need
+separate fonts anyway.  Suitable mathematics fonts for use with other
+font families are discussed in 
+&ldquo;<a href="FAQ-psfchoice.html">choice of scalable fonts</a>&rdquo;.
+<p/>The EC fonts are distributed with a
+set of &lsquo;Text Companion&rsquo; (TC) fonts that provide glyphs for
+symbols commonly used in text.  The TC fonts are encoded
+according to the LaTeX TS1 encoding, and are not viewed as
+&lsquo;stable&rsquo; in the same way as are the EC fonts are.
+<p/>The Cork encoding is also implemented by virtual fonts provided in the
+<a href="FAQ-usepsfont.html">PSNFSS system</a>,
+for Adobe Type 1 fonts, and also by the <i>txfonts</i> and
+<i>pxfonts</i> font packages
+
+(see <a href="FAQ-psfchoice.html">&ldquo;choice of scalable fonts&rdquo;</a>).
+<dl>
+<dt><tt><i>CM-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>)
+<dt><tt><i>CM-LGC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.zip">fonts/ps-type1/cm-lgc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-lgc/">browse</a>)
+<dt><tt><i>EC and TC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ec.zip">fonts/ec</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ec/">browse</a>)
+<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html
new file mode 100644
index 00000000000..7b59a98ca4d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label HPdrivers</title>
+</head><body>
+<h3>DVI drivers for HP LaserJet</h3>
+<p/>The emTeX distribution (see <a href="FAQ-TeXsystems.html">TeX systems</a>)
+contains a driver for the LaserJet, <i>dvihplj</i>.
+<p/>Version 2.10 of the Beebe drivers supports the LaserJet. These drivers
+will compile under Unix, VMS, and on the Atari ST and
+DEC-20s.
+<p/>For Unix systems, Karl Berry&rsquo;s <i>dviljk</i> uses the same
+path-searching library as <i>web2c</i>.
+<dl>
+<dt><tt><i>Beebe drivers</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/beebe.zip">dviware/beebe</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/beebe.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/beebe/">browse</a>)
+<dt><tt><i>dviljk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dviljk.zip">dviware/dviljk</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dviljk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dviljk/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html
new file mode 100644
index 00000000000..e0f2d5d30c9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html
@@ -0,0 +1,78 @@
+<head>
+<title>UK TeX FAQ -- question label LaTeX2HTML</title>
+</head><body>
+<h3>Conversion from (La)TeX to HTML</h3>
+<p/>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; HTML is not, because HTML is a
+functional markup language not a page layout language. HTML&rsquo;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 HTML and you must use some other
+publishing format such as PDF. That is true for any HTML
+authoring tool.
+<p/>TeX&rsquo;s excellent mathematical capabilities remain a challenge in the
+business of conversion to HTML.  There are only two generally
+reliable techniques for generating mathematics on the web: creating
+bitmaps of bits of typesetting that can&rsquo;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 &mdash; see
+
+<a href="FAQ-mathml.html">future Web technologies</a>.
+<p/>For today, possible packages are:
+<dl>
+<dt><i>LaTeX2HTML</i><dd>a <i>Perl</i> script package that
+  supports LaTeX only, and generates mathematics (and other
+  &ldquo;difficult&rdquo; 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 <i>LaTeX2HTML</i>, and how to tailor it, in
+  <i>TUGboat</i> 16(2).
+<p/>  A mailing list for users may be found via
+  <a href="http://tug.org/mailman/listinfo/latex2html">http://tug.org/mailman/listinfo/latex2html</a>
+<dt><i>TtH</i><dd>a compiled program that supports either LaTeX
+  or Plain TeX, and uses the font/table technique for representing
+  mathematics.  It is written by Ian Hutchinson, using
+  <i>flex</i>.  The distribution consists of a single C
+  source (or a compiled executable), which is easy to install and very
+  fast-running.
+<dt><i>Tex4ht</i><dd>a compiled program that supports either
+  LaTeX or Plain TeX, by processing a DVI file; it uses
+  bitmaps for mathematics, but can also use other technologies where
+  appropriate.  Written by Eitan Gurari, it parses the DVI
+  file generated when you run (La)TeX over your file with
+  <i>tex4ht</i>&rsquo;s macros included.  As a result, it&rsquo;s pretty
+  robust against the macros you include in your document, and it&rsquo;s
+  also pretty fast.
+<dt><i>TeXpider</i><dd> a commercial program from
+  <a href="FAQ-commercial.html">Micropress</a>, which is
+  described on <a href="http://www.micropress-inc.com/webb/wbstart.htm">http://www.micropress-inc.com/webb/wbstart.htm</a>;
+  it uses bitmaps for equations.
+<dt><i>Hevea</i><dd> a compiled program that supports LaTeX
+  only, and uses the font/table technique for equations (indeed its
+  entire approach is very similar to <i>TtH</i>).  It is written
+  in Objective CAML by Luc Maranget.  <i>Hevea</i> isn&rsquo;t
+  archived on CTAN; details (including download points) are
+  available via <a href="http://pauillac.inria.fr/~maranget/hevea/">http://pauillac.inria.fr/~maranget/hevea/</a>
+</dl>
+An interesting set of samples, including conversion of the same text
+by the four free programs listed above, is available at
+<a href="http://www.mayer.dial.pipex.com/samples/example.htm">http://www.mayer.dial.pipex.com/samples/example.htm</a>; a linked
+page gives lists of pros and cons, by way of comparison.
+<p/>The World Wide Web Consortium maintains a list of &ldquo;filters&rdquo; to
+HTML, with sections on (La)TeX and BibTeX &mdash; see
+<a href="http://www.w3.org/Tools/Word_proc_filters.html">http://www.w3.org/Tools/Word_proc_filters.html</a>
+<dl>
+<dt><tt><i>latex2html</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/latex2html/">support/latex2html/</a>
+<dt><tt><i>tex4ht</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a>
+<dt><tt><i>tth</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/support/tth/dist/tth_C.tgz">nonfree/support/tth/dist/tth_C.tgz</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html
new file mode 100644
index 00000000000..2a29b0b7692
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label LaTeX3</title>
+</head><body>
+<h3>The LaTeX project</h3>
+<p/>The LaTeX project team (see <a href="http://www.latex-project.org/latex3.html">http://www.latex-project.org/latex3.html</a>)
+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 LaTeX3; it
+will remain freely available and it will be fully documented at
+all levels.
+<p/>The LaTeX team&rsquo;s first product (LaTeX2e) was delivered in 1994
+(it&rsquo;s now properly called &ldquo;LaTeX&rdquo;, since no other version is current).
+<p/>LaTeX2e was intended as a consolidation exercise, unifying several
+sub-variants of LaTeX while changing nothing whose change wasn&rsquo;t
+absolutely necessary.  This has permitted the team to support a single
+version of LaTeX, in parallel with development of LaTeX3.
+<p/>Some of the older discussion papers about directions for LaTeX3 are
+to be found on CTAN; other (published) articles are to be
+found on the project web site
+(<a href="http://www.latex-project.org/papers/">http://www.latex-project.org/papers/</a>), as is some of the
+project&rsquo;s experimental code
+(see <a href="http://www.latex-project.org/code.html">http://www.latex-project.org/code.html</a>, which allows you to
+read the project&rsquo;s source repository).  You can
+participate in discussions of the future of LaTeX through the
+mailing list <code>latex-l</code>.  Subscribe to the list by sending a
+message &lsquo;<code>subscribe latex-l &lt;<em>your name</em>&gt;</code>&rsquo; to 
+<a href="mailto:listserv@urz.Uni-Heidelberg.de"><i>listserv@urz.Uni-Heidelberg.de</i></a>
+<dl>
+<dt><tt><i>LaTeX project publications</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.zip">info/ltx3pub</a> (<a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/ltx3pub/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html
new file mode 100644
index 00000000000..ab94f60b823
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html
@@ -0,0 +1,24 @@
+<head>
+<title>UK TeX FAQ -- question label LaTeXandPlain</title>
+</head><body>
+<h3>How does LaTeX relate to Plain TeX?</h3>
+<p/>LaTeX is a program written in the programming language TeX.  (In
+the same sense, any LaTeX document is also a program, which is
+designed to run &lsquo;alongside&rsquo;, or &lsquo;inside&rsquo; LaTeX, whichever metaphor
+you prefer.)
+<p/>Plain TeX is also a program written in the programming language
+TeX.
+<p/>Both exist because writing your documents in &lsquo;raw&rsquo; TeX would
+involve much reinventing of wheels for every document.  They both
+serve as convenient aids to make document writing more pleasant:
+LaTeX is a far more extensive aid.
+<p/>LaTeX is close to being a superset of Plain TeX.  Many documents
+designed for Plain TeX will work with LaTeX with no more than
+minor modifications (though some will require substantial work).
+<p/>Interpretation of any (La)TeX program involves some data-driven
+elements, and LaTeX has a wider range of such elements than does
+Plain TeX.  As a result, the mapping from LaTeX to Plain TeX
+is far less clear than that in the other direction &mdash; see a later
+answer about <a href="FAQ-LaTeXtoPlain.html">translating to Plain TeX</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html
new file mode 100644
index 00000000000..4a0148e2129
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label LaTeXtoPlain</title>
+</head><body>
+<h3>Translating LaTeX to Plain TeX</h3>
+<p/>Unfortunately, no &ldquo;general&rdquo;, simple, automatic process is likely to
+succeed at this task.  See 
+&ldquo;<a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX</a>&rdquo;
+for further details.
+<p/>Translating a document designed to work with LaTeX into one
+designed to work with Plain TeX is likely to amount to carefully
+including (or otherwise re-implementing) all those parts of LaTeX,
+beyond the provisions of Plain TeX, which the document uses.
+<p/>Some of this work is has (in a sense) been done, in the port of the
+LaTeX graphics package to Plain TeX.  However, while
+<i>graphics</i> is available, other complicated packages (notably
+<i>hyperref</i>) are not.  The aspiring translator may find the
+<a href="FAQ-eplain.html">Eplain</a> 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 &ldquo;bare minimum&rdquo; that Plain TeX is designed to
+offer.)
+<dl>
+<dt><tt><i>\latexhtml{\textrm{The}}{The} eplain system</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>)
+<dt><tt><i>\latexhtml{\textrm{&lsquo;Plain TeX&rsquo;}}{Plain TeX} graphics</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html
new file mode 100644
index 00000000000..45a0be06dd8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label MF</title>
+</head><body>
+<h3>What is Metafont?</h3>
+<p/>Metafont was written by Knuth as a companion to TeX; whereas TeX
+defines the layout of glyphs on a page, Metafont defines the shapes of
+the glyphs and the relations between them.  Metafont details the sizes of
+glyphs, for TeX&rsquo;s benefit, and details the rasters used to
+represent the glyphs, for the benefit of programs that will produce
+printed output as post processes after a run of TeX.
+<p/>Metafont&rsquo;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, &lsquo;meta&rsquo;-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.
+<p/>Knuth (and others) have designed a fair range of fonts using Metafont,
+but font design using Metafont is much more of a minority skill than is
+TeX macro-writing.  The complete TeX-user nevertheless needs to
+be aware of Metafont, and to be able to run Metafont to generate personal
+copies of Meta-fonts that come her way.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html
new file mode 100644
index 00000000000..e9a6ceaaa3e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label MP</title>
+</head><body>
+<h3>What is MetaPost?</h3>
+<p/>The MetaPost system (by John Hobby) implements a picture-drawing language
+very much like that of Metafont except that it outputs Encapsulated PostScript
+files instead of run-length-encoded bitmaps.  MetaPost is a powerful
+language for producing figures for documents to be printed on PostScript
+printers, either directly or embedded in (La)TeX documents. It
+includes facilities for directly integrating TeX text and
+mathematics with the graphics. (Knuth tells us that he uses nothing
+but MetaPost for diagrams in text that he is writing.)
+<p/>Although PDFLaTeX cannot ordinarily handle PostScript graphics, the
+output of MetaPost is sufficiently simple and regular that PDFLaTeX
+can handle it direct, using code borrowed from ConTeXt &mdash; see
+<a href="FAQ-pdftexgraphics.html">graphics in PDFLaTeX</a>.
+<p/>Much of MetaPost&rsquo;s source code was copied from Metafont&rsquo;s sources, with
+Knuth&rsquo;s permission.
+<p/>A mailing list discussing MetaPost is available;
+
+  subscribe via the 
+  <a href="http://lists.tug.org/metapost">TUG <i>mailman</a> interface</i>.
+The TUG website also hosts a 
+<a href="http://tug.org/metapost.html">MetaPost summary page</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html
new file mode 100644
index 00000000000..8b6bd2a9737
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label PSpreview</title>
+</head><body>
+<h3>Previewing files using Type 1 fonts</h3>
+<p/>Until recently, free TeX previewers have only been capable of
+displaying bitmap PK fonts, but current versions of
+<i>xdvi</i> sport a Type 1 font renderer.
+
+
+
+
+
+<p/>Other (free) previewers of the current generation offer automatic
+generation of the requisite PK files (using <i>gsftopk</i>,
+or similar, behind the scenes).  If your previewer isn&rsquo;t capable of
+this, you have three options:
+<ul>
+<li> Convert the DVI file to PostScript and use a
+  PostScript previewer.  Some systems offer this capability as
+  standard, but most people will need to use a separate previewer such
+  as <i>ghostscript</i> or <i>ghostscript</i>-based viewers
+  such as <i>ghostview</i> or shareware offering <i>GSview</i>.
+<li> Under Windows on a PC, or on a Macintosh, let Adobe Type Manager
+  display the fonts (textures, on the Macintosh, works like this).
+
+
+
+
+
+  (See <a href="FAQ-commercial.html">commercial suppliers</a> for details.)
+
+<li> If you have the PostScript fonts in Type 1 format,
+  use <i>ps2pk</i> or <i>gsftopk</i>
+  (designed for use with the <i>ghostscript</i> fonts) to make
+  PK bitmap fonts which your previewer 
+  will understand. This can produce excellent results, also suitable
+  for printing with non-PostScript devices. Check the legalities of
+  this if you have purchased the fonts.
+</ul>
+<dl>
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+<dt><tt><i>ghostview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/gnu/ghostview/">support/ghostscript/gnu/ghostview/</a>
+<dt><tt><i>gsftopk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/gsftopk.zip">fonts/utilities/gsftopk</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/gsftopk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/gsftopk/">browse</a>)
+<dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a>
+<dt><tt><i>ps2pk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/ps2pk.zip">fonts/utilities/ps2pk</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/ps2pk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/ps2pk/">browse</a>)
+<dt><tt><i>xdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.zip">dviware/xdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/xdvi/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html
new file mode 100644
index 00000000000..d8ef63eaa2c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html
@@ -0,0 +1,73 @@
+<head>
+<title>UK TeX FAQ -- question label RCS</title>
+</head><body>
+<h3>Version control using RCS, CVS or the like</h3>
+<p/>If you use RCS, CVS, <i>Subversion</i>,
+<i>Bazaar</i> or <i>Git</i> to maintain
+your (La)TeX 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).
+<p/>The most complete solution for RCS and CVS is to use the
+(LaTeX) package <i>rcs</i>, which allows you to parse and
+display the contents of RCS keyword fields in an extremely
+flexible way.  The package <i>rcsinfo</i> is simpler, but does most
+of what you want, and some people prefer it; it is explicitly
+compatible with <i>LaTeX2HTML</i>.
+<p/>If, however, you need a solution which works without using external
+packages, or which will work in Plain TeX, then you can use the
+following minimal solution:
+<blockquote>
+<pre>
+\def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}}
+\RCS$Revision: 1.543 $ % or any RCS keyword
+\RCS$Date: 2008/06/21 18:54:02 $
+...
+\date{Revision \RCSRevision, \RCSDate}
+</pre>
+
+</blockquote><p>
+<p/>If you&rsquo;ve entered the brave new world of <i>Subversion</i>, the
+package <i>svn</i> may be for you.  It has explicit cleverness
+about dealing with dates:
+<blockquote>
+<code>\</code><code>documentclass</code><code>{&lt;<i>foo</i>&gt;}</code><br>
+<code>...</code><br>
+<code>\</code><code>usepackage{svn}</code><br>
+<code>\</code><code>SVNdate</code><code> $Date$</code><br>
+<code>\</code><code>author{...}</code><br>
+<code>\</code><code>title{...}</code><br>
+<code>...</code><br>
+<code>\</code><code>begin{document}</code><br>
+<code>\</code><code>maketitle</code><br>
+<code>...</code><br>
+<code>\</code><code>end{document}</code>
+</blockquote><p>
+will (once <i>subversion</i> has committed a copy of the document)
+cause <code>\</code><code>maketitle</code> use the date that has been written into the
+<code>$Date$</code> keyword.
+<p/>Another alternative for <i>Subversion</i> users is the
+<i>svninfo</i> package, which has much the same mechanisms as does
+<i>svn</i> but with a rather different focus.  <i>Svninfo</i>
+does the date trick that <i>svn</i> performs (controlled by a
+package option), and can set up page foot-lines using 
+<a href="FAQ-fancyhdr.html">package <i>fancyhdr</i></a>.  There isn&rsquo;t much to
+choose between the two packages: you should read the packages&rsquo;
+documentation to see which suits you best.
+<p/>An alternative script-based approach to version control has been taken
+by the <i>vc</i> bundle, that in certain situations might work more
+reliably than any of the packages mentioned above.  The <i>vc</i>
+bundle supports <i>Bazaar</i>, <i>Git</i> and
+<i>Subversion</i> usage and works with both LaTeX and
+Plain TeX.  Note that <i>vc</i> is the only option that
+currently claims to support <i>Bazaar</i>- and
+<i>Git</i>-controlled repositories.
+<dl>
+<dt><tt><i>rcs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcs.zip">macros/latex/contrib/rcs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rcs/">browse</a>)
+<dt><tt><i>rcsinfo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcsinfo.zip">macros/latex/contrib/rcsinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcsinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rcsinfo/">browse</a>)
+<dt><tt><i>svn.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svn.zip">macros/latex/contrib/svn</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svn.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/svn/">browse</a>)
+<dt><tt><i>svninfo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svninfo.zip">macros/latex/contrib/svninfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svninfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/svninfo/">browse</a>)
+<dt><tt><i>vc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/vc.zip">support/vc</a> (<a href="ftp://cam.ctan.org/tex-archive/support/vc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/vc/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html
new file mode 100644
index 00000000000..8a5d7f1fd4e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label SGML2TeX</title>
+</head><body>
+<h3>Conversion from SGML or HTML to TeX</h3>
+<p/>SGML is a very important system for document storage and interchange,
+but it has no formatting features; its companion ISO standard
+DSSSL
+(see <a href="http://www.jclark.com/dsssl/">http://www.jclark.com/dsssl/</a>) is designed for writing
+transformations and formatting,
+but this has not yet been widely implemented. Some SGML authoring
+systems (e.g., SoftQuad <i>Author/Editor</i>) have formatting
+abilities, and
+there are high-end specialist SGML typesetting systems (e.g., Miles33&rsquo;s
+<i>Genera</i>).  However, the majority of 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:
+<ol>
+<li> Write a free-standing translator in the traditional way, with
+  tools like <i>yacc</i> and <i>lex</i>; this is hard, in
+  practice, because of the complexity of SGML.
+<li> Use a specialist language designed for SGML transformations; the
+  best known are probably <i>Omnimark</i> and <i>Balise</i>.
+  They are expensive, but powerful, incorporating SGML query and
+  transformation abilities as well as simple translation.
+<li> Build a translator on top of an existing SGML parser.  By far
+  the best-known (and free!) parser is James Clark&rsquo;s
+  <i>nsgmls</i>, and this produces a much simpler output format,
+  called ESIS, which can be parsed quite straightforwardly (one also
+  has the benefit of an SGML parse against the DTD). Two
+  good public domain packages use this method:
+  <ul>
+  <li>
+
+      David Megginson&rsquo;s
+      <a href="http://www.perl.com/CPAN/modules/by-module/SGMLS"><i>sgmlspm</a></i>,
+      written in <i>Perl</i> 5.
+    <li>
+
+      Joachim Schrod and Christine Detig&rsquo;s
+      <a href="ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil"><i>STIL</a></i>,
+       (&lsquo;SGML Transformations in Lisp&rsquo;).
+  </ul>
+  Both of these allow the user to write &lsquo;handlers&rsquo; for every SGML
+  element, with plenty of access to attributes, entities, and
+  information about the context within the document tree.
+<p/>  If these packages don&rsquo;t meet your needs for an average SGML
+  typesetting job, you need the big commercial stuff.
+</ol>
+<p/>Since HTML is simply an example of SGML, we do not need a specific
+system for HTML.  However, Nathan Torkington developed
+
+<i>html2latex</i> from the HTML parser in NCSA&rsquo;s
+Xmosaic package.
+The program takes an HTML file and generates a LaTeX file from it.
+The conversion code is subject to NCSA restrictions, but the whole
+source is available on CTAN.
+<p/>Michel Goossens and Janne Saarela published a very useful summary of
+SGML, and of public domain tools for writing and manipulating it, in
+<i>TUGboat</i> 16(2).
+<dl>
+<dt><tt><i>html2latex source</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/html2latex.zip">support/html2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/html2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/html2latex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html
new file mode 100644
index 00000000000..f33711fd008
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label TUG*</title>
+</head><body>
+<h3>TeX User Groups</h3>
+<p/>There has been a TeX User Group since very near the time TeX
+first appeared.  That first group, TUG, is still active and its
+journal <i>TUGboat</i> continues in regular publication
+with articles about TeX, Metafont and related technologies, and about
+document design, processing and production.  TUG holds a yearly
+conference, whose proceedings are published in <i>TUGboat</i>.
+<p/>TUG&rsquo;s <a href="http://www.tug.org">web site</a> 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
+<i>TUGboat</i> are slowly (subject to copyright issues, etc.)
+making their way to the site, too.
+<p/>Some time ago, TUG established a &ldquo;technical council&rdquo;, whose
+task was to oversee the development of TeXnical projects.  Most
+such projects nowadays go on their way without any support from
+TUG, but TUG&rsquo;s web site lists its
+
+<a href="http://www.tug.org/twg.html">Technical Working Groups (TWGs)</a>.
+<p/>TUG has a reasonable claim to be considered a world-wide
+organisation, but there are many national and regional user groups,
+too; TUG&rsquo;s web site maintains a list of
+
+<a href="http://www.tug.org/lugs.html">&ldquo;local user groups&rdquo; (LUGs)</a>.
+<p/>Contact TUG itself via:
+<blockquote>
+  TeX Users Group<br>
+  1466 NW Front Avenue, Suite 3141<br>
+  Portland, OR 97209<br>
+  USA<br>
+  Tel: +1 503-223-9994<br>
+  Fax: +1 503-223-3960<br>
+  Email: <a href="mailto:tug@mail.tug.org"><i>tug@mail.tug.org</i></a><br>
+  Web: <a href="http://www.tug.org/">http://www.tug.org/</a>
+</blockquote><p>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html
new file mode 100644
index 00000000000..6db8acf7837
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label TeXfuture</title>
+</head><body>
+<h3>What is the future of TeX?</h3>
+<p/>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 pi (at the time of writing, Knuth&rsquo;s latest release is version
+3.141592).  Knuth wants TeX to be frozen at version pi when he
+dies; thereafter, no further changes may be made to Knuth&rsquo;s source.
+(A similar rule is applied to Metafont; its version number tends to the
+limit e, and currently stands at 2.71828.)
+<p/>Knuth explains his decision, and exhorts us all to respect it, in a
+paper originally published in <i>TUGboat</i> 11(4) (and reprinted in the
+
+<a href="http://www.ntg.nl/maps/pdf/5_34.pdf">NTG journal MAPS</a>).
+<p/>There are projects (some of them long-term
+projects: see, for example,
+<a href="FAQ-LaTeX3.html">the LaTeX3 project</a>)
+
+to build substantial
+new macro packages based on TeX.  For the even longer term, there
+are various projects to build a <em>successor</em> to TeX; see, for example,
+the
+
+<a href="FAQ-luatex.html">\LuaTeX</a>,
+<a href="FAQ-omegaleph.html">Omega/Aleph</a> and
+<a href="FAQ-extex.html">ExTeX</a>
+  projects.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html
new file mode 100644
index 00000000000..2da01c865cf
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label TeXpronounce</title>
+</head><body>
+<h3>How should I pronounce &ldquo;TeX&rdquo;?</h3>
+<p/>The &lsquo;X&rsquo; is &ldquo;really&rdquo; the Greek letter 
+Chi, and is pronounced by
+English-speakers either a bit like the &lsquo;ch&rsquo; in the Scots word &lsquo;loch&rsquo;
+([x] in the IPA) or (at a pinch, if you can&rsquo;t do the Greek sound) like
+&lsquo;k&rsquo;.  It definitely is not pronounced &lsquo;ks&rsquo; (the Greek letter with that
+sound doesn&rsquo;t look remotely like the Latin alphabet &lsquo;X&rsquo;).
+<p/>This curious usage derives from Knuth&rsquo;s explanation in the TeXbook
+that the name comes from the Greek word for &lsquo;art&rsquo; or &lsquo;craft&rsquo;
+(&lsquo;<em>techni</em>&rsquo;),
+which is the root of the English word &lsquo;technology&rsquo;.  Knuth&rsquo;s logo for TeX is
+merely the uppercase version of the first three (Greek) letters of the
+word, jiggled about a bit; we don&rsquo;t use that logo (and logos like it)
+in this FAQ (see 
+<a href="FAQ-logos.html">Typesetting TeX-related logos</a>).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html
new file mode 100644
index 00000000000..40217a1f6c7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html
@@ -0,0 +1,204 @@
+<head>
+<title>UK TeX FAQ -- question label TeXsystems</title>
+</head><body>
+<h3>(La)TeX for different machines</h3>
+<!-- windows,macintosh,macos,ms-dos,os/2,unix,linux -->
+<p/>We list here the free or shareware packages;
+
+  another question addresses
+  <a href="FAQ-commercial.html">commercial TeX vendors&rsquo;</a> products.
+<dl>
+<dt>Unix<dd> The only current distribution of TeX for Unix systems
+  (including GNU/Linux and other free Unix-like systems) is
+  TeX Live, which is distributed as part of the 
+  <a href="FAQ-CD.html">TeX collection</a>.
+<p/>  Members of many TeX user groups receive copies of the collection
+  (on CD and DVD), as part of their membership of the
+  groups.
+<p/>  MacOS/X is also a Unix-based system; however users should refer to
+  the information below, under item &ldquo;Mac&rdquo;.
+  <dl>
+  <dt><tt><i>texlive</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a>
+  </dl>
+<dt>Linux<dd> GNU/Linux users are supported by TeX Live (as noted
+  above).
+<p/>  A free version of the commercial 
+  <a href="FAQ-commercial.html">VTeX extended TeX system</a> is available
+  for use under Linux, which among other things specialises in direct
+  production of PDF from (La)TeX input.  Sadly, it&rsquo;s no
+  longer supported, and the ready-built images are made for use with a
+  rather ancient Linux kernel.
+  <dl>
+  <dt><tt><i>texlive</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a>
+  <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.zip">systems/vtex/linux</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/linux/">browse</a>)
+  <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>)
+  </dl>
+<dt>PC: Windows post-95<dd>
+  MiKTeX, by Christian Schenk, is a comprehensive distribution.  It has
+  its own previewer, YAP, which is itself capable of printing,
+  though the distribution also includes a port of <i>dvips</i>.
+  The current version is available for file-by-file download (the
+  HTML files in the directory offer hints
+  on what you need to get going).  The MiKTeX developers provide a
+  ready-to-run copy of the distribution, on CD (for purchase) via the
+  <a href="http://www.miktex.org/cd/">MiKTeX web site</a>; otherwise the
+  <i>setup</i> executable is available on CTAN, together with
+  all the optional packages.
+<p/>  <a href="http://tug.org/protext/">ProTeXt</a>, part of the TeX
+  collection by Thomas Feuerstack, is
+  a further option for installing MiKTeX.  It bundles a MiKTeX
+  setup with some further useful utilities, together with a PDF
+  file which contains clickable links for the various installation
+  steps, along with explanations.
+<p/>  Windows users are also supported directly by the TeX Live
+  distribution; a system is provided on the installation disc of the
+  TeX collection (and it can, with some difficulty, be run &ldquo;from
+  the disc&rdquo; without installing <em>anything</em>).
+<p/>  <a href="http://foundry.supelec.fr/projects/xemtex/">XEmTeX</a>, by
+  Fabrice Popineau (he who created the excellent, but now defunct,
+  fpTeX distribution), is an integrated distribution of TeX, LaTeX,
+  ConTeXt, <i>XEmacs</i> and 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.
+<p/>  The (Japanese) W32TEX distribution was motivated by
+  the needs of Japanese users (Japanese won&rsquo;t fit in a &ldquo;simple&rdquo;
+  character set like ASCII, but TeX is based on a version of
+  ASCII).  Despite its origins, W32TEX 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
+  <a href="http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html">http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html</a>
+<p/>  A further (free) option arises from the
+  <a href="http://www.cygwin.com">CygWin bundle</a>, which presents a
+  Unix-like environment over the Win32 interface; an X-windows server
+  is available.  If you run CygWin on your Windows machine, you have
+  the option of using TeX Live, too (you will need the X-server, to
+  run <i>xdvi</i>).  Of course, TeX Live components will look like
+  Unix applications (of course, that&rsquo;s presumably what you wanted),
+  but TeX under CygWin also reputedly somewhat slower than native
+  Win32 implementations such as MiKTeX or XEmTeX.  The (now
+  obsolete) teTeX distribution is provided as part of the CygWin
+  distribution, and but you can build your own copy of TeX Live from
+  the current sources.
+<p/>  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.
+  <dl>
+  <dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/bakoma.zip">systems/win32/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/win32/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/win32/bakoma/">browse</a>)
+  <dt><tt><i>miktex</i></tt><dd>Acquire <a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a> (also available from the
+    MiKTeX web site), and read installation instructions from 
+                                
+    <a href="http://www.miktex.org/2.5/Setup.aspx">the MiKTeX installation page</a>
+  <dt><tt><i>protext.exe</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/protext/">systems/win32/protext/</a>
+  <dt><tt><i>tetex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/unix/teTeX/current/distrib/">obsolete/systems/unix/teTeX/current/distrib/</a>
+  </dl>
+<dt>PC: MSDOS or OS/2<dd> EmTeX, by Eberhard Mattes,
+  includes LaTeX, BibTeX, previewers, and drivers, and is
+  available  as a series of zip archives.  Documentation is
+  available in both German and English.  Appropriate memory managers
+  for using emTeX with 386 (and better) processors and under
+  Windows, are included in the distribution.  EmTeX will operate
+  under Windows, but Windows users are better advised to use a
+  distribution tailored for the Windows environment.
+<p/>  A version of emTeX, packaged to use a
+  
+  <a href="FAQ-tds.html">TDS directory structure</a>, is separately available as
+  an emTeX &lsquo;contribution&rsquo;.  Note that neither emTeX itself, nor
+  emTeXTDS, is maintained.  Most users of Microsoft
+  operating systems, who want an up-to-date (La)TeX system, need to
+  migrate to Win32-based systems.
+  <dl>
+  <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>)
+  <dt><tt><i>emtexTDS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.zip">obsolete/systems/os2/emtex-contrib/emtexTDS</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS/">browse</a>)
+  </dl>
+<dt>PC: MSDOS<dd> The most recent MSDOS offering is a
+  port of the Web2C 7.0 implementation, using the GNU
+  <i>djgpp</i> compiler.  While this package is more recent than
+  emTeX, it still implements a rather old instance of (La)TeX.
+  <dl>
+  <dt><tt><i>djgpp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.zip">systems/msdos/djgpp</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/djgpp/">browse</a>)
+  </dl>
+<dt>PC: OS/2<dd> EmTeX, by Eberhard Mattes (see
+  above), was actually developed under OS/2, and lives happily
+  in that environment.
+<p/>  OS/2 users may also use a free version of the
+  commercial <a href="FAQ-commercial.html">VTeX</a>, which specialises
+  in direct production of PDF from (La)TeX input.  (This
+  version is, like the Linux version, unfortunately no longer supported.)
+  <dl>
+  <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>)
+  <dt><tt><i>emtexTDS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.zip">obsolete/systems/os2/emtex-contrib/emtexTDS</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS/">browse</a>)
+  <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.zip">systems/vtex/os2</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/os2/">browse</a>)
+  <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>)
+  </dl>
+
+
+
+
+
+
+
+
+<dt>Mac<dd> <a href="http://www.trevorrow.com/oztex/">OzTeX</a>, by Andrew
+  Trevorrow, is a shareware version of
+  TeX for the Macintosh.  A DVI previewer and PostScript
+  driver are also included.  (Members of UK TUG may
+  acquire the software without further payment, as part of a
+  membership deal.)  OzTeX does not run, natively, under MacOS/X,
+  but will run with a sufficiently recent CarbonLib (see
+  <a href="http://www.trevorrow.com/oztex/ozosx.html">http://www.trevorrow.com/oztex/ozosx.html</a>).
+  Other questions about OzTeX itself may be directed to
+  <a href="mailto:oztex@midway.uchicago.edu"><i>oztex@midway.uchicago.edu</i></a>
+<p/>  Another partly shareware program is
+  <a href="http://www.kiffe.com/cmactex.html">CMacTeX</a> , put together
+  by Tom Kiffe.  CMacTeX is much closer than OzTeX to the Unix
+  TeX model of things (it uses <i>dvips</i>, for instance).
+  CMacTeX runs natively under  includes a port of a version of
+  <a href="FAQ-omegaleph.html">Omega</a>.
+<p/>  Both OzTeX and CMacTeX run on either MacOS/X or on a
+  sufficiently recent MacOS with CarbonLib 
+  (v1.3 for OzTeX, v1.4 for CMacTeX).
+  
+<p/>  From its 2005 release, the <a href="FAQ-CD.html">TeX Live disc set</a>
+  includes MacTeX.  Details (and a downloadable distribution set)
+  may be found on the 
+  <a href="http://tug.org/mactex">TUG web site</a>; the distribution
+  is also on CTAN.
+<p/>
+  A useful
+  <a href="http://www.esm.psu.edu/mac-tex/">resource for Mac users</a>
+  has a news and &lsquo;help&rsquo; section, as well as details of systems and
+  tools.
+  The MacTeX-on-OSX mailing list is a useful resource for users;
+  mail <a href="mailto:MacOSX-TeX-on@email.esm.psu.edu"><i>MacOSX-TeX-on@email.esm.psu.edu</i></a> to subscribe.
+<dl>
+  <dt><tt><i>cmactex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.zip">nonfree/systems/mac/cmactex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/cmactex/">browse</a>)
+  <dt><tt><i>mactex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">systems/mac/mactex/</a>
+  <dt><tt><i>oztex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.zip">nonfree/systems/mac/oztex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/oztex/">browse</a>)
+</dl>
+<dt>OpenVMS<dd> TeX for OpenVMS is available, though
+  it seems unlikely that the version on CTAN is the latest
+  available.  
+  <dl>
+  <dt><tt><i>OpenVMS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/OpenVMS/TEX97_CTAN.ZIP">systems/OpenVMS/TEX97_CTAN.ZIP</a>
+  </dl>
+<dt>Atari<dd> TeX for the Atari ST is available from CTAN.
+  <dl>
+  <dt><tt><i>Atari TeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/atari.zip">systems/atari</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/atari.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/atari/">browse</a>)
+  </dl>
+<dt>Amiga<dd> Full implementations of TeX 3.1 (PasTeX) and Metafont
+  2.7 are available.
+  <dl>
+  <dt><tt><i>PasTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/amiga.zip">systems/amiga</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/amiga.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/amiga/">browse</a>)
+  </dl>
+<dt>TOPS-20<dd> TeX was originally written on a DEC-10
+  under WAITS,
+  and so was easily ported to TOPS-20. A distribution that runs on
+  TOPS-20 is available via anonymous <code>ftp</code> from
+  <a href="ftp://ftp.math.utah.edu} in <i>pub/tex/pub/web/">ftp.math.utah.edu</i> in \path{pub/tex/pub/web</a>
+  
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html
new file mode 100644
index 00000000000..5de14a4523d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html
@@ -0,0 +1,96 @@
+<head>
+<title>UK TeX FAQ -- question label WYGexpts</title>
+</head><body>
+<h3>The TeX document preparation environment</h3>
+<p/><p/>&ldquo;<a href="FAQ-notWYSIWYG.html">Why TeX is not WYSIWYG</a>&rdquo;
+outlines the reasons (or excuses) for the huge disparity of user
+interface between &ldquo;typical&rdquo; TeX environments and commercial word
+processors.
+<p/>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 <a href="http://www.texmacs.org"><i>TeXmacs</a></i>,
+a document processor using
+TeX&rsquo;s algorithms and fonts for both editor display and printing.
+<i>TeXmacs</i> does not use the TeX
+language itself (though among other formats, LaTeX may be exported
+and imported).  A bit closer to LaTeX is
+<a href="http://www.lyx.org/">LyX</a>, 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.
+<p/>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 <i>emacs</i> 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 <i>emacs</i>) can cater for TeX in
+this way.  Under Windows, one of the more popular editors with such
+support is the
+Shareware product <a href="http://www.winedt.com/"><i>winedt</a></i>.
+Continuing the range of
+tools prettifying your input, we have the <i>emacs</i> package
+<a href="http://x-symbol.sourceforge.net"><i>x-symbol</a></i>, which does
+the WYSIWYG part of its work by replacing single TeX tokens and
+accented letter sequences with appropriate-looking characters on the
+screen.
+<p/>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
+&lsquo;source specials&rsquo; 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 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.
+<p/>An <i>emacs</i> package that combines this sort of editor movement
+tracking with automatic fast recompilations (through the use of dumped
+formats) is
+<a href="http://pauillac.inria.fr/whizzytex/"><i>WhizzyTeX</a></i>
+ which is best used with a previewer by the
+same author.  A simpler package in a similar spirit is called
+<a href="http://www.activetex.org/"><i>InstantPreview</a></i> and makes
+use of a continuously running copy of TeX
+(under the moniker of <code>TeX daemon</code>) instead of dumping formats to
+achieve its speed.
+<p/>Another <i>emacs</i> package called
+<a href="http://preview-latex.sourceforge.net"><i>preview-latex</a></i>
+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.
+<p/>A more ambitious contender is called TeXlite.  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&rsquo;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.
+<p/>That many of these systems occupy slightly different niches can be
+seen by comparing the range of the
+<i>emacs</i>-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.
+<p/>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.
+<dl>
+<dt><tt><i>preview-latex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/preview-latex/">support/preview-latex/</a>
+<dt><tt><i>texmacs</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/TeXmacs/">systems/unix/TeXmacs/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html
new file mode 100644
index 00000000000..34d7cedaf42
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label abspos</title>
+</head><body>
+<h3>Putting things at fixed positions on the page</h3>
+<p/>TeX&rsquo;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.
+<p/>There <em>are</em> 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.
+<p/>The <i>textpos</i> package aids the construction of pages from
+&ldquo;blobs&rdquo;, dotted around over the page (as in a poster); you give it
+the location, and it places your typeset box accordingly.
+<p/>The <i>eso-pic</i> defines a &ldquo;shipout picture&rdquo; that covers the
+page.  The user may add <code>picture</code>-mode commands to this
+picture, which of course can include box placements as well as the
+other rather stilted commands of <code>picture</code>-mode.
+(<i>Eso-pic</i> requires the services of <i>everyshi</i>, which
+must therefore also be available.)
+
+
+
+
+
+
+<dl>
+<dt><tt><i>eso-pic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.zip">macros/latex/contrib/eso-pic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic/">browse</a>)
+<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>)
+<dt><tt><i>textpos.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html
new file mode 100644
index 00000000000..9768f8a3c7b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label acroantics</title>
+</head><body>
+<h3>Adobe <i>Reader</i> messing with print size</h3>
+<p/>Printing from Adobe <i>Reader</i> shrinks the page &ldquo;to fit&rdquo;
+(<em>by default</em>).  Unfortunately, its calculation doesn&rsquo;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.
+<p/>Solve this problem by adjusting the <i>Reader</i>&rsquo;s default in the
+print dialogue; unfortunately, this dialogue varies from one version
+to the next.  On <i>Reader</i> version 7, there are two entries to
+check:
+<blockquote>
+   Page Scaling (default: &ldquo;Fit to printer margins&rdquo;) &mdash; change to
+   &ldquo;None&rdquo;, and<br>
+   Scale (default 95%  of Normal size) &mdash; change to
+   &ldquo;100%&rdquo;.
+
+
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acroantics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acroantics</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html
new file mode 100644
index 00000000000..da4bb7af6b0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html
@@ -0,0 +1,83 @@
+<head>
+<title>UK TeX FAQ -- question label acrobat</title>
+</head><body>
+<h3>Making Acrobat PDF documents from (La)TeX</h3>
+<p/>There are three general routes to PDF output: Adobe&rsquo;s original
+&lsquo;distillation&rsquo; route (via PostScript output), conversion of a
+DVI file, and the use of a direct PDF generator such as
+<a href="FAQ-whatpdftex.html">PDFTeX</a>) or
+MicroPress&rsquo;s VTeX (which comes both as a 
+<a href="FAQ-commercial.html">commercial version</a> for Windows PCs, and as a
+<a href="FAQ-TeXsystems.html">&lsquo;free&rsquo; version)</a> for OS/2 and Linux systems).
+<p/>For simple documents (with no hyper-references), you can either
+<ul>
+<li> process the document in the normal way, produce PostScript
+  output and distill it;
+<li> (on a Windows or Macintosh machine with the appropriate Adobe
+  tools installed) pass the output through the
+  PDFwriter in place of a printer driver (this route is a dead
+  end: the PDFwriter cannot create hyperlinks);
+<li> process the document in the normal way and generate PDF
+  direct from the DVI using
+  <i>dvipdfm</i>/<i>dvipdfmx</i>; or 
+<li> process the document direct to PDF with PDFTeX or
+  VTeX.  PDFTeX has
+  the advantage of availability for a wide range of platforms, VTeX
+  (available commercially for Windows, or free of charge, but
+  unsupported, for Linux or OS/2) has wider graphics
+  capability, dealing with encapsulated PostScript and some in-line PostScript.
+</ul>
+<p/>To translate all the LaTeX cross-referencing into Acrobat
+links, you need a LaTeX package to suitably redefine
+the internal commands.  There are two of these for LaTeX, both
+capable of conforming to the
+<a href="FAQ-hyper.html">HyperTeX specification</a>:
+Heiko Oberdiek&rsquo;s <i>hyperref</i>, and Michael Mehlich&rsquo;s
+<i>hyper</i>.  (In practice, almost everyone uses
+<i>hyperref</i>; <i>hyper</i> hasn&rsquo;t been updated since 2000.)
+<i>Hyperref</i> can often determine how it should generate
+hypertext from its environment, but there is a wide set of
+configuration options you can give via <code>\</code><code>usepackage</code>.  The package
+can operate using PDFTeX primitives, the hyperTeX
+<code>\</code><code>special</code>s, or DVI driver-specific <code>\</code><code>special</code> commands.
+Both <i>dvips</i> and Y&amp;Y&rsquo;s <i>DVIPSONE</i> can
+translate the DVI with these <code>\</code><code>special</code> commands into
+PostScript acceptable to Distiller, and <i>dvipdfm</i> has <code>\</code><code>special</code>
+commands of its own.
+<p/>If you use Plain TeX, the <a href="FAQ-eplain.html">Eplain macros</a> can
+help you create PDF documents with hyper-references.
+It can operate using PDFTeX primitives, or <code>\</code><code>special</code> commands
+for the <i>dvipdfm</i> DVI driver.
+<p/>While there is no free implementation of all of <i>Adobe</i>
+<i>Distiller</i>&rsquo;s
+functionality, any but the very oldest versions of <i>Ghostscript</i>
+provide pretty reliable distillation (but beware of the problems with
+<a href="FAQ-dvips-pdf.html"><i>dvips</i> output for distillation</a>).
+<p/>For viewing (and printing) the resulting files, Adobe&rsquo;s
+<i>Acrobat</i> <i>Reader</i> is available for a fair range of
+platforms; for those for which Adobe&rsquo;s reader is unavailable, remotely
+current versions of <i>ghostscript</i> combined with
+<i>gv</i>, <i>GSview</i> (or even the unsupported
+<i>ghostview</i>) can display and print PDF files, as can
+<i>xpdf</i>.
+<p/>In many circumstances, <i>Ghostscript</i> combined with a viewer
+application is actually preferable to Acrobat Reader.  For example, on
+Windows Acrobat Reader locks the <code>.pdf</code> file it&rsquo;s displaying: this
+makes the traditional (and highly effective) (La)TeX development
+cycle of &ldquo;Edit-&gt; Process-&gt; Preview&rdquo; become
+rather clumsy &mdash; <i>GSview</i> doesn&rsquo;t make the same
+mistake.
+<dl>
+<dt><tt><i>Acrobat Reader</i></tt><dd>browse
+  <a href="ftp://ftp.adobe.com/pub/adobe/acrobatreader">ftp://ftp.adobe.com/pub/adobe/acrobatreader</a>
+<dt><tt><i>dvipdfm</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>)
+<dt><tt><i>dvipdfmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.zip">dviware/dvipdfmx</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfmx/">browse</a>)
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+<dt><tt><i>ghostview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/gnu/ghostview/">support/ghostscript/gnu/ghostview/</a>
+<dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a>
+<dt><tt><i>gv</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/gv/">support/gv/</a>
+<dt><tt><i>hyper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.zip">macros/latex/contrib/hyper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyper/">browse</a>)
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html
new file mode 100644
index 00000000000..7d024d8dd5c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html
@@ -0,0 +1,76 @@
+<head>
+<title>UK TeX FAQ -- question label actinarg</title>
+</head><body>
+<h3>Active characters in command arguments</h3>
+<p/>Occasionally, it&rsquo;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.
+<p/>Active characters <em>can</em> be used safely in such situations; but
+care is needed.
+<p/>An example arose while this answer was being considered: an aspirant
+macro writer posted to <i>comp.text.tex</i> asking for help to
+make <code>#</code> and <code>b</code> produce musical sharp and flat signs, respectively,
+in a macro for specifying chords.
+<p/>The first problem is that both <code>#</code> and <code>b</code> 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.
+<p/>Using the techniques discussed in 
+&ldquo;<a href="FAQ-activechars.html">characters as commands</a>&rdquo;,
+we can define:
+<blockquote>
+<pre>
+\begingroup
+  \catcode`\#=\active
+  \gdef#{$\sharp$}
+\endgroup
+</pre>
+</blockquote><p>
+and:
+<blockquote>
+<pre>
+\begingroup
+  \lccode`\~=`\b
+  \lowercase{\endgroup
+    \def~{$\flat$}%
+  }
+</pre>
+</blockquote><p>
+The second problem is one of timing: the command has to make each
+character active <em>before</em> its arguments are read: this means that
+the command can&rsquo;t actually &ldquo;have&rdquo; arguments itself, but must be
+split in two.  So we write:
+<blockquote>
+<pre>
+\def\chord{%
+  \begingroup
+    \catcode`\#=\active
+    \catcode`\b=\active
+    \Xchord
+}
+\def\Xchord#1{%
+    \chordfont#1%
+  \endgroup
+}
+</pre>
+</blockquote><p>
+and we can use the command as <code>\</code><code>chord{F#}</code> or
+<code>\</code><code>chord{Bb minor}</code>.
+<p/>Two features of the coding are important:
+<ul>
+<li> <code>\</code><code>begingroup</code> in <code>\</code><code>chord</code> opens a group that is closed by
+  <code>\</code><code>endgroup</code> in <code>\</code><code>Xchord</code>; this group limits the change of
+  category codes, which is the <em>raison d&rsquo;&ecirc;tre</em> of the whole
+  exercise.
+<li> Although <code>#</code> is active while <code>\</code><code>Xchord</code> is executed, it&rsquo;s
+  <em>not</em> active when it&rsquo;s being defined, so that the use of <code>#1</code>
+  doesn&rsquo;t require any special attention.
+</ul>
+<p/>Note that the technique used in such macros as <code>\</code><code>chord</code>, here, is
+analogous to that used in such commands as <code>\</code><code>verb</code>; and, in just the
+same way as <code>\</code><code>verb</code> (see
+
+&ldquo;<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> doesn&rsquo;t work in arguments</a>&rdquo;),
+<code>\</code><code>chord</code> won&rsquo;t work inside the argument of another command (the
+error messages, if they appear at all, will probably be rather odd).
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html
new file mode 100644
index 00000000000..7bb7a695e11
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html
@@ -0,0 +1,120 @@
+<head>
+<title>UK TeX FAQ -- question label activechars</title>
+</head><body>
+<h3>Defining characters as macros</h3>
+<p/>Single characters can act as macros (defined commands), and both
+Plain TeX and LaTeX define the character
+&ldquo;<code>~</code>&rdquo; as a &ldquo;non-breakable space&rdquo;.  A
+character is made definable, or &ldquo;active&rdquo;, by setting its
+<em>category code</em> (catcode) to be <code>\</code><code>active</code> (13):
+<code>\catcode&lsquo;_=\active</code>.
+<p/>Any character could, in principle, be activated this way and defined
+as a macro (<code>\</code><code>def</code><code>_{</code><code>\</code><code>_</code><code>}</code> &mdash; the simple answer to
+
+<a href="FAQ-underscore.html">using underscores</a>), but 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&rsquo;s use for
+other purposes, and there are few characters &ldquo;free&rdquo; to be subverted
+in this way.
+<p/>To define the character &ldquo;<code>z</code>&rdquo; as a command, one would say something
+like:
+<blockquote>
+<pre>
+\catcode`\z=\active
+\def z{Yawn, I'm tired}%
+</pre>
+</blockquote><p>
+and each subsequent &ldquo;<code>z</code>&rdquo; 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 &ldquo;<code>\def z</code>&rdquo;, &ldquo;<code>z</code>&rdquo; is no longer interpreted as
+a letter; the space is therefore not necessary &mdash; &ldquo;<code>\defz</code>&rdquo; would do; we
+choose to retain the space, for what little clarity we can manage.)
+Some LaTeX packages facilitate such definitions. For example, the
+<i>shortvrb</i> package with its <code>\</code><code>MakeShortVerb</code> command.
+<p/>TeX uses category codes to interpret characters as they are read 
+from the input.
+
+<em>Changing a catcode value will not affect characters that have already been read</em>.
+Therefore, it is best if characters have fixed category codes for the
+duration of a document.  If catcodes are changed for particular
+purposes (the <code>\</code><code>verb</code> 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
+
+&ldquo;<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> in command arguments</a>&rdquo;).
+An exemplary case is the <i>doc</i> package, which processes .dtx
+files using the <i>shortvrb</i> package to define
+<code>|...|</code> as a shorthand for
+<code>\</code><code>verb</code><code>|...|</code>. But <code>|</code> is
+also used in the preambles of tabular environments, so that tables in
+<code>.dtx</code> files can only have vertical line separation between
+columns by employing special measures of some sort.
+<p/>Another consequence is that catcode assignments made
+in macros often don&rsquo;t work as expected 
+(see &ldquo;<a href="FAQ-actinarg.html">Active characters in command arguments</a>&rdquo;).
+For example, the definition
+<blockquote>
+<pre>
+\def\mistake{%
+\catcode`_=\active
+\def_{\textunderscore\-}%
+}
+</pre>
+</blockquote><p>
+does not work because it attempts to define an ordinary <code>_</code> 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:
+<blockquote>
+<pre>
+\begingroup
+\catcode`_=\active
+\gdef\works{%    note the global \gdef
+  \catcode`_=\active
+  \def_{\textunderscore\-}%
+}
+\endgroup
+</pre>
+</blockquote><p>
+The alternative (&ldquo;tricksy&rdquo;) way of creating such an isolated
+definition depends on the curious properties of <code>\</code><code>lowercase</code>, which
+changes characters without altering their catcodes.  Since there is
+always <em>one</em> active character (&ldquo;<code>~</code>&rdquo;), we
+can fool <code>\</code><code>lowercase</code> into patching up a definition without ever
+explicitly changing a catcode:
+<blockquote>
+<pre>
+\begingroup
+  \lccode`\~=`\_
+  \lowercase{\endgroup
+    \def~{\textunderscore\-}%
+  }%
+</pre>
+</blockquote><p>
+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 <code>\</code><code>global</code> command.
+<p/>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 <em>maths code</em>, as with
+<blockquote>
+<pre>
+\begingroup
+  \lccode`~=`x
+  \lowercase{\endgroup
+    \def~{\times}%
+  }%
+\mathcode`x="8000
+</pre>
+</blockquote><p>
+The special character does not need to be redefined whenever it is
+made active &mdash; the definition of the command persists even if the
+character&rsquo;s catcode reverts to its original value; the definition
+becomes accessible again if the character once again becomes active.
+<dl>
+<dt><tt><i>doc.sty</i></tt><dd>Distributed as part of the source of LaTeX, <a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>)
+<dt><tt><i>shortvrb.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html
new file mode 100644
index 00000000000..219c4a1d6ba
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html
@@ -0,0 +1,74 @@
+<head>
+<title>UK TeX FAQ -- question label addtoreset</title>
+</head><body>
+<h3>Master and slave counters</h3>
+<p/>It&rsquo;s common to have things numbered &ldquo;per chapter&rdquo; (for example, in
+the standard <i>book</i> and <i>report</i> classes, figures, tables
+and footnotes are all numbered thus).  The process of resetting is
+done automatically, when the &ldquo;master&rdquo; counter is stepped (when the
+<code>\</code><code>chapter</code> command that starts chapter &lt;<i>n</i>&gt; happens, the
+<code>chapter</code> counter is stepped, and all the dependent counters are set
+to zero).
+<p/>How would you do that for yourself?  You might want to number
+algorithms per section, or corollaries per theorem, for example.  If
+you&rsquo;re defining these things by hand, you declare the relationship
+when you define the counter in the first place:
+<blockquote>
+<code>\</code><code>newcounter{</code><em>new-name</em><code>}[</code><em>master</em><code>]</code>
+</blockquote><p>
+says that every time counter &lt;<i>master</i>&gt; is stepped, counter
+&lt;<i>new-name</i>&gt; will be reset.
+<p/>But what if you have an uncooperative package, that defines the
+objects for you, but doesn&rsquo;t provide a programmer interface to make
+the counters behave as you want?
+<p/>The <code>\</code><code>newcounter</code> command uses a LaTeX internal command, and you
+can also use it:
+<blockquote>
+<code>\</code><code>@addtoreset{</code><em>new-name</em><code>}{</code><em>master</em><code>}</code>
+</blockquote><p>
+(but remember that it needs to be between <code>\</code><code>makeatletter</code> and
+<code>\</code><code>makeatother</code>, or in a package of your own).
+<p/>The <i>chngcntr</i> package encapsulates the <code>\</code><code>@addtoreset</code>
+command into a command <code>\</code><code>counterwithin</code>.  So:
+<blockquote>
+<pre>
+\counterwithin*{corrollary}{theorem}
+</pre>
+</blockquote><p>
+will make the corollary counter slave to theorem counters.  The
+command without its asterisk:
+<blockquote>
+<pre>
+\counterwithin{corrollary}{theorem}
+</pre>
+</blockquote><p>
+will do the same, and also redefine <code>\</code><code>thecorollary</code> as 
+&lt;<i>theorem number</i>&gt;.&lt;<i>corollary number</i>&gt;, which is a good scheme
+if you ever want to refer to the corollaries &mdash; there are potentially
+many &ldquo;corollary 1&rdquo; in any document, so it&rsquo;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&rsquo;re not using the
+<i>chngcntr</i>, refer to the answer to 
+<a href="FAQ-the-commands.html">redefining counters&rsquo; <code>\</code><code>the-</code>commands</a> for
+the necessary techniques.
+<p/>Note that the technique doesn&rsquo;t work if the master counter is <code>page</code>,
+the number of the current page.  The <code>page</code> 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: <a href="FAQ-footnpp.html">footnotes numbered per page</a>.  One
+of the techniques described there, using package <i>perpage</i>,
+may be applied to any counter.  The command:
+<blockquote>
+<code>\</code><code>MakePerPage{</code><em>counter</em><code>}</code>
+</blockquote><p>
+will cause &lt;<i>counter</i>&gt; 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 &mdash; LaTeX will generate the usual
+warnings about labels changing.
+<dl>
+<dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a>
+<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html
new file mode 100644
index 00000000000..570d284480a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label adobetypen</title>
+</head><body>
+<h3>Adobe font formats</h3>
+<!-- type1 type3 -->
+<p/>Adobe has specified a number of formats for files to represent fonts
+in PostScript files; this question doesn&rsquo;t attempt to be encyclopaedic, so
+we only discuss the two formats most commonly encountered in the
+(La)TeX context, types 1 and 3.  In particular, we don&rsquo;t discuss the
+OpenType format, whose has many advantages are somewhat ahead of the
+TeX world&rsquo;s mainstream (at time of writing).
+<p/>Adobe Type 1 format specifies a means to represent outlines of the glyphs
+in a font.  The &lsquo;language&rsquo; used is closely restricted, to ensure that
+the font is rendered as quickly as possible.  (Or rather, as quickly
+as possible with Adobe&rsquo;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.
+<p/>
+
+
+
+<p/>In the (La)TeX 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 PDF files has long (in effect) <em>insisted</em> on
+their use (see below).
+<p/>Type 3 fonts have a more forgiving specification.  A wide range of
+PostScript operators is permissible, including bitmap specifiers.  Type 3
+is therefore the natural format to be used for programs such as
+<i>dvips</i> when they auto-generate something to represent
+Metafont-generated fonts in a PostScript file.  It&rsquo;s Adobe Acrobat Viewer&rsquo;s
+treatment of bitmap Type 3 fonts that has made direct Metafont output
+increasingly unattractive, in recent years.  If you have a PDF
+document in which the text looks fuzzy and uneven in Acrobat Reader,
+ask Reader for the <code>File</code>-&gt; 
+<code>Document Properties</code>-&gt; 
+<code>Fonts ...</code>, and it will likely show some font or other as
+&ldquo;Type 3&rdquo; (usually with encoding &ldquo;Custom&rdquo;).  The problem has
+disappeared with version 6 of Acrobat Reader.  See 
+<a href="FAQ-dvips-pdf.html">PDF quality</a> for a discussion of
+the issue, and for ways of addressing it.
+<p/>Type 3 fonts should not entirely be dismissed, however.  Acrobat
+Reader&rsquo;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 PostScript graphical operators, and you can make pleasing
+Type 3 fonts that don&rsquo;t &ldquo;annoy&rdquo; Reader.  For example, you may not
+change colour within a Type 1 font glyph, but there&rsquo;s no such
+restriction on a Type 3 font, which opens opportunities for some
+startling effects.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html
new file mode 100644
index 00000000000..61cf79d5c30
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html
@@ -0,0 +1,107 @@
+<head>
+<title>UK TeX FAQ -- question label algorithms</title>
+</head><body>
+<h3>Typesetting pseudocode in LaTeX</h3>
+<p/>There is no consensus on the &lsquo;right&rsquo; way to typeset pseudocode.
+Consequently, there are a variety of LaTeX packages to choose from
+for producing &aelig;sthetically pleasing pseudocode listings.
+<p/>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.
+  <a href="FAQ-codelist.html">Typesetting program listings</a> is described
+  elsewhere.
+
+<p/>You can certainly create your own environment for typesetting
+pseudocode using, for example, the <code>tabbing</code> or
+<code>list</code> environments &mdash; it&rsquo;s not difficult, but it may
+prove boring.  So it&rsquo;s worth trying the following packages, all
+designed specifically for typesetting pseudocode.
+<p/>The <i>algorithms</i> bundle (which contains packages
+<i>algorithm</i> and <i>algorithmic</i>, 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 <i>algorithmic</i>; the <i>algorithms</i> package
+uses the facilities of the <i>float</i> package to number
+algorithms sequentially, enable algorithms to float like figures or
+tables, and support including a List of Algorithms in a document&rsquo;s
+front matter.
+<p/>Packages in the <i>algorithmicx</i> bundle are similar both in
+concept and output form to <i>algorithmic</i> but additionally
+provide support for adding new keywords and altering the formatting.
+It provides the <i>algpseudocode</i> package which is (almost) a
+drop-in replacement for <i>algorithmic</i>.  Another package in the
+bundle, <i>algpascal</i>, uses Pascal-like keywords, indents
+differently from <i>algpseudocode</i>, and puts command arguments
+in maths mode instead of text mode.  There is no floating environment
+but <i>algorithmicx</i>, like <i>algorithmic</i>, is compatible
+with the <i>algorithm</i> package.
+<p/>The <i>alg</i> package, like <i>algorithms</i>, offers a
+floating algorithm environment with all of the ensuing niceties.
+<i>alg</i>, however, can caption its floats in a variety of
+(natural) languages.  In addition, <i>alg</i> unlike
+<i>algorithms</i>, makes it easy to add new constructs.
+<p/>The <i>newalg</i> package has a somewhat similar interface to
+<i>algorithms</i>, but its output is designed to mimic the rather
+pleasant typesetting used in the book &ldquo;<em>Introduction to Algorithms</em>&rdquo;
+by Corman, Leiserson, Rivest and Stein. Unfortunately,
+<i>newalg</i> does not support a floating environment or any
+customisation of the output.
+<p/>&ldquo;<em>Bona fide</em>&rdquo; use of the style of &ldquo;Introduction to
+Algorithms&rdquo; may be achieved with Cormen&rsquo;s own <i>clrscode</i>:
+this is the package as used in the second edition of the book.
+<p/>Similarly, the style of 
+&ldquo;<em>Combinatorial Algorithms: Generation, Enumeration and Search</em>&rdquo;
+is supported by the <i>pseudocode</i> package, written by the
+authors of the book.  It has the common &lsquo;Pascal-like&rsquo; style, and has
+some interesting constructs for what one thinks of as Pascal blocks.
+<p/>The <i>algorithm2e</i> is of very long standing, and is widely used
+and recommended.  It loads the <i>float</i> package to provide the
+option of floating algorithm descriptions, but you can always use the
+&ldquo;<code>H</code>&rdquo; option of <i>float</i> to have the algorithm appear
+&ldquo;where you write it&rdquo;.
+<p/>The usage of the <i>program</i> 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.
+<i>program</i> lacks a floating environment but does number
+algorithms like <i>alg</i> and <i>algorithms</i>.  Customisation
+and extension are not supported.  Documentation of the
+<i>program</i> package (such as it is) appears in a file
+<i>program.msg</i> in the distribution.
+<p/>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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<dl>
+<dt><tt><i>algorithm2e.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithm2e.zip">macros/latex/contrib/algorithm2e</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithm2e.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/algorithm2e/">browse</a>)
+<dt><tt><i>algorithmicx bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithmicx.zip">macros/latex/contrib/algorithmicx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithmicx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/algorithmicx/">browse</a>)
+<dt><tt><i>algorithms bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithms.zip">macros/latex/contrib/algorithms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/algorithms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/algorithms/">browse</a>)
+<dt><tt><i>alg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/alg.zip">macros/latex/contrib/alg</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/alg.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/alg/">browse</a>)
+<dt><tt><i>clrscode.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/clrscode.zip">macros/latex/contrib/clrscode</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/clrscode.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/clrscode/">browse</a>)
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+<dt><tt><i>newalg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newalg.zip">macros/latex/contrib/newalg</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newalg.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/newalg/">browse</a>)
+<dt><tt><i>program.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/program.zip">macros/latex/contrib/program</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/program.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/program/">browse</a>)
+<dt><tt><i>pseudocode.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pseudocode.zip">macros/latex/contrib/pseudocode</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pseudocode.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pseudocode/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html
new file mode 100644
index 00000000000..748ce8e51cc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label alreadydef</title>
+</head><body>
+<h3>Package reports &ldquo;command already defined&rdquo;</h3>
+<p/>You load a pair of packages, and the second reports that one of the
+commands it defines is already present.  For example, both the
+<i>txfonts</i> and <i>amsmath</i> define a command <code>\</code><code>iint</code>
+(and <code>\</code><code>iiint</code> and so on); so
+<blockquote>
+<pre>
+...
+\usepackage{txfonts}
+\usepackage{amsmath}
+</pre>
+</blockquote><p>
+produces a string of error messages of the form:
+<blockquote>
+<pre>
+! LaTeX Error: Command \iint already defined.
+               Or name \end... illegal, see p.192 of the manual.
+</pre>
+
+</blockquote><p>
+As a general rule, things that <i>amsmath</i> defines, it defines
+well; however, there is a good case for using the <i>txfonts</i>
+version of <code>\</code><code>iint</code> &mdash; the associated <i>tx</i> fonts have a
+double integral symbol that doesn&rsquo;t need to be &ldquo;faked&rdquo; in the way
+<i>amsmath</i> 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 (<code>\</code><code>euro</code> is a common
+victim).
+<p/>There are similar cases where one package redefines another&rsquo;s command,
+but no error occurs because the redefining package doesn&rsquo;t use
+<code>\</code><code>newcommand</code>.  Often, in such a case, you only notice the change
+because you assume the definition given by the first package.  The
+<i>amsmath</i>&ndash;<i>txfonts</i> packages are just such a pair;
+<i>txfonts</i> doesn&rsquo;t provoke errors.
+<p/>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&rsquo;s the package <i>savesym</i>.  The sequence:
+<blockquote>
+<pre>
+\usepackage{savesym}
+\usepackage{amsmath}
+\savesymbol{iint}
+\usepackage{txfonts}
+\restoresymbol{TXF}{iint}
+</pre>
+</blockquote><p>
+does the job; restoring the <i>amsmath</i> version of the command,
+and making the <i>txfonts</i> version of the command available as
+<code>\</code><code>TXFiint</code>.
+<p/>Documentation of <i>savesym</i> doesn&rsquo;t amount to much: the only
+commands are <code>\</code><code>savesymbol</code> and <code>\</code><code>restoresymbol</code>, as noted above.
+<dl>
+<dt><tt><i>amsmath.sty</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>savesym.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savesym/savesym.sty">macros/latex/contrib/savesym/savesym.sty</a>
+<dt><tt><i>txfonts.sty</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html
new file mode 100644
index 00000000000..b895f454cad
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html
@@ -0,0 +1,77 @@
+<head>
+<title>UK TeX FAQ -- question label altabcr</title>
+</head><body>
+<h3>Alignment tab changed to <code>\</code><code>cr</code></h3>
+<p/>This is an error you may encounter in LaTeX when a tabular
+environment is being processed.  &ldquo;Alignment tabs&rdquo; are the
+<code>&amp;</code> signs that separate the columns of a tabular; so the error
+message
+<blockquote>
+
+<pre>
+! Extra alignment tab has been changed to \cr
+</pre>
+</blockquote><p>
+could arise from a simple typo, such as:
+<blockquote>
+<pre>
+\begin{tabular}{ll}
+  hello   & there & jim \\
+  goodbye & now
+\end{tabular}
+</pre>
+</blockquote><p>
+where the second <code>&amp;</code> in the first line of the table is more than the
+two-column <code>ll</code> column specification can cope with. In this
+case, an extra &ldquo;<code>l</code>&rdquo; in that solves the problem.  (If you
+continue from the error in this case, &ldquo;<code>jim</code>&rdquo; will be moved
+to a row of his own.)  Another simple typo that can provoke the error
+is:
+<blockquote>
+<pre>
+\begin{tabular}{ll}
+  hello   & there
+  goodbye & now
+\end{tabular}
+</pre>
+</blockquote><p>
+where the &lsquo;<code>\\</code>&rsquo; 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:
+<blockquote>
+<pre>
+\begin{tabular}{ll}
+  hello   & there goodbye\\
+  now
+\end{tabular}
+</pre>
+</blockquote><p>
+(with the second line of the table having only one cell).
+<p/>Rather more difficult to spot is the occurrence of the error when
+you&rsquo;re using alignment instructions in a &ldquo;<code>p</code>&rdquo; column:
+<blockquote>
+<pre>
+\usepackage{array}
+...
+\begin{tabular}{l&gt;{\raggedright}p{2in}}
+here & we are again \\
+happy & as can be
+\end{tabular}
+</pre>
+</blockquote><p>
+the problem here (as explained in 
+<a href="FAQ-tabcellalign.html">tabular cell alignment</a>) is that the
+<code>\</code><code>raggedright</code> command in the column specification has overwritten
+<code>tabular</code>&rsquo;s definition of <code>\\</code>, so that
+&ldquo;<code>happy</code>&rdquo; appears in a new line of the second column, and the
+following <code>&amp;</code> appears to LaTeX just like the second
+<code>&amp;</code> in the first example above.
+<p/>Get rid of the error in the way described in 
+<a href="FAQ-tabcellalign.html">tabular cell alignment</a> &mdash; either use
+<code>\</code><code>tabularnewline</code> explicitly, or use the <code>\</code><code>RBS</code> trick described
+there.
+<dl>
+<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
new file mode 100644
index 00000000000..fc542341fc2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label amfonts</title>
+</head><body>
+<h3>Where are the <code>am</code> fonts?</h3>
+<p/>One <em>still</em> occasionally comes across a request for the <i>am</i>
+series of fonts.  The initials stood for &lsquo;Almost [Computer] Modern&rsquo;,
+and they were the predecessors of the Computer Modern fonts that we
+all know and love (or hate)
+.
+There&rsquo;s not a lot one can do with these
+fonts; they are (as their name implies) almost (but not quite) the
+same as the <i>cm</i> series; if you&rsquo;re faced with a document that requests
+them, all you can reasonably do is to edit the document.  The
+appearance of 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; however, most drivers let you have a
+configuration file in which you can specify font substitutions. If you
+specify that every <i>am</i> font should be replaced by its corresponding
+<i>cm</i> font, the output should be almost correct.
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html
new file mode 100644
index 00000000000..9fda82f2995
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label ant</title>
+</head><body>
+<h3>The ANT typesetting system</h3>
+<p/>Achim Blumensath&rsquo;s <a href="http://ant.berlios.de">ANT</a> project,
+in contrast to <i>NTS</i>, 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.
+ANT remains under development, but it is now approaching the
+status of a usable typesetting system.
+<p/>ANT&rsquo;s markup language is immediately recognisable to the
+(La)TeX user, but the scheme of implementing design in
+ANT&rsquo;s own implementation language (presently
+<i>OCaml</i>) comes as a pleasant surprise to the jaded FAQ
+writer.  This architecture holds the promise of a system that avoids a
+set of serious problems with TeX&rsquo;s user interface: those that
+derive from the design language being the same as the markup language.
+<dl>
+<dt><tt><i>ANT</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/ant.zip">systems/ant</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/ant.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/ant/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html
new file mode 100644
index 00000000000..89083a05049
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html
@@ -0,0 +1,110 @@
+<head>
+<title>UK TeX FAQ -- question label appendix</title>
+</head><body>
+<h3>Appendixes</h3>
+<p/>LaTeX provides an exceedingly simple mechanism for appendixes: the
+command <code>\</code><code>appendix</code> switches the document from generating sections
+(in <i>article</i> class) or chapters (in <i>report</i> or
+<i>book</i> classes) to producing appendixes.  Section or chapter
+numbering is restarted and the representation of the counter switches
+to alphabetic.  So:
+<blockquote>
+<pre>
+\section{My inspiration}
+...
+
+\section{Developing the inspiration}
+...
+
+\appendix
+\section{How I became inspired}
+...
+</pre>
+</blockquote><p>
+would be typeset (in an <i>article</i> document) something like:
+<blockquote>
+<b>1  My inspiration</b>
+<p/>...
+<p/><b>2  Developing the inspiration</b>
+<p/>...
+<p/><b>A  How I became inspired</b>
+<p/>...
+</blockquote><p>
+which is quite enough for many ordinary purposes.  Note that, once
+you&rsquo;ve switched to typesetting appendixes, LaTeX provides you with
+no way back &mdash; once you&rsquo;ve had an appendix, you can no longer have an
+&ldquo;ordinary&rdquo; <code>\</code><code>section</code> or <code>\</code><code>chapter</code>.
+<p/>The <i>appendix</i> 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
+<blockquote>
+<pre>
+\usepackage{appendix}
+...
+\appendix
+\appendixpage
+\addappheadtotoc
+</pre>
+</blockquote><p>
+The <code>\</code><code>appendixpage</code> command adds a separate title &ldquo;Appendices&rdquo;
+above the first appendix, and <code>\</code><code>addappheadtotoc</code> adds a similar
+title to the table of contents.  These simple modifications cover many
+people&rsquo;s needs about appendixes.
+<p/>The package also provides an <code>appendices</code> environment,
+which provides for fancier use.  The environment is best controlled by
+package options; the above example would be achieved by
+<blockquote>
+<pre>
+\usepackage[toc,page]{appendix}
+...
+\begin{appendices}
+...
+\end{appendices}
+</pre>
+</blockquote><p>
+The great thing that the <code>appendices</code> environment gives
+you, is that once the environment ends, you can carry on with sections
+or chapters as before &mdash; numbering isn&rsquo;t affected by the intervening
+appendixes.
+<p/>The package provides another alternative way of setting appendixes, as
+inferior divisions in the document.  The <code>subappendices</code>
+environment allows you to put separate appendixes for a particular
+section, coded as <code>\</code><code>subsection</code>s, or for a particular chapter, coded
+as <code>\</code><code>section</code>s.  So one might write:
+<blockquote>
+<pre>
+\usepackage{appendix}
+...
+\section{My inspiration}
+...
+\begin{subappendices}
+\subsection{How I became inspired}
+...
+\end{subappendices}
+
+\section{Developing the inspiration}
+...
+</pre>
+</blockquote><p>
+Which will produce output something like:
+<blockquote>
+<b>1  My inspiration</b>
+<p/>...
+<p/><b>1.A  How I became inspired</b>
+<p/>...
+<p/><b>2  Developing the inspiration</b>
+<p/>...
+</blockquote><p>
+<p/>There are many other merry things one may do with the package; the
+user is referred to the package documentation for further details.
+<p/>The <i>memoir</i> class includes the facilities of the
+<i>appendix</i> package.  The <i>KOMA-script</i> classes offer a
+<code>\</code><code>appendixprefix</code> command for manipulating the appearance of appendixes.
+<dl>
+<dt><tt><i>appendix.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/appendix.zip">macros/latex/contrib/appendix</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/appendix.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/appendix/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html
new file mode 100644
index 00000000000..c5d5971f4f9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html
@@ -0,0 +1,47 @@
+<head>
+<title>UK TeX FAQ -- question label archives</title>
+</head><body>
+<h3>Repositories of TeX material</h3>
+<p/>To aid the archiving and retrieval of of TeX-related files, a
+TUG working group developed the Comprehensive TeX Archive
+Network (CTAN).  Each CTAN site has identical material,
+and maintains authoritative versions of its material.  These
+collections are extensive; in particular, almost everything mentioned
+in this FAQ
+is archived at the CTAN sites (see the lists of software at the
+end of each answer).
+<p/>
+  The CTAN sites are
+  <a href="ftp://dante.ctan.org/tex-archive">Dante (Germany)</a>,
+  <a href="ftp://cam.ctan.org/tex-archive">Cambridge (UK)</a> and
+  <a href="ftp://tug.ctan.org/tex-archive">TUG (USA)</a>; the links are to
+  the root of the CTAN tree, above which the layout is
+  identical at each site.
+<p/>The TeX files at each CTAN node may also be accessed via
+the Web at URLs <a href="http://www.dante.de/tex-archive">http://www.dante.de/tex-archive</a>,
+<a href="http://www.tex.ac.uk/tex-archive">http://www.tex.ac.uk/tex-archive</a> and
+<a href="http://www.ctan.org/tex-archive">http://www.ctan.org/tex-archive</a> respectively, but not all
+CTAN mirrors are Web-accessible.
+<p/>As a matter of course, to reduce network load,
+please use the CTAN site
+or mirror closest to you.  A complete and current list of CTAN sites
+and known mirrors is available as file <a href="ftp://cam.ctan.org/tex-archive/CTAN.sites">CTAN.sites</a> on the
+archives themselves.
+<p/>Better still, the script behind <a href="http://mirror.ctan.org/">http://mirror.ctan.org/</a> will
+cunningly choose a &ldquo;nearby&rdquo; mirror for you, using information from
+the database &lsquo;behind&rsquo; <a href="ftp://cam.ctan.org/tex-archive/CTAN.sites">CTAN.sites</a>; at present it uses
+<code>ftp</code> protocol for transfers, but the intention is to convert
+it to using <code>http</code> (web) protocol in the near future.
+<p/>To access a particular thing through the <code>mirror.ctan.org</code>
+mechanism, simply place the CTAN path after the base
+URL; so
+<a href="http://mirror.ctan.org/macros/latex/contrib/footmisc/">http://mirror.ctan.org/macros/latex/contrib/footmisc/</a> will
+connect you to the <i>footmisc</i> directory &mdash; note that the
+<i>tex-archive</i> part of the CTAN path isn&rsquo;t needed.
+<p/>For details of how to find files at CTAN sites, see
+&ldquo;<a href="FAQ-findfiles.html">finding (La)TeX files</a>&rdquo;.
+<p/>The TeX user who has no access to any sort of
+network may buy a copy of the archive as part of the
+<a href="FAQ-CD.html">TeX Live distribution</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html
new file mode 100644
index 00000000000..f2f9211afd8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label askquestion</title>
+</head><body>
+<h3>How to ask a question</h3>
+<p/>You want help from the community at large; you&rsquo;ve decided where you&rsquo;re
+going to <a href="FAQ-gethelp.html">ask your question</a>, but how do you
+phrase it?
+<p/>Excellent &ldquo;general&rdquo; advice (how to ask questions of anyone) is
+contained in
+
+<a href="http://catb.org/~esr/faqs/smart-questions.html">Eric Raymond&rsquo;s article on the topic</a>.
+Eric&rsquo;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&rsquo;s important to remember that you don&rsquo;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.
+<p/>So how do you express yourself in the (La)TeX world?  There aren&rsquo;t
+any comprehensive rules, but a few guidelines may help in the
+application of your own common sense.
+<ul>
+<li> Make sure you&rsquo;re asking the right people.  Don&rsquo;t ask in a TeX
+  forum about printer device drivers for the <i>Foobar</i>
+  operating system.  Yes, TeX users need printers, but no, TeX
+  users will typically <em>not</em> be <i>Foobar</i> systems
+  managers.
+<p/>  Similarly, avoid posing a question in a language that the majority
+  of the group don&rsquo;t use: post in Ruritanian to
+  <i>de.comp.text.tex</i> and you may have a long wait before a
+  German- and Ruritanian-speaking TeX expert notices your
+  question.
+<li> If your question is (or may be) TeX-system-specific, report
+  what system you&rsquo;re using, or intend to use: &ldquo;I can&rsquo;t install
+  TeX&rdquo; is as good as useless, whereas &ldquo;I&rsquo;m trying to install the
+  <i>mumbleTeX</i> distribution on the <i>Grobble</i>
+  operating system&rdquo; gives all the context a potential respondent
+  might need.  Another common situation where this information is
+  important is when you&rsquo;re having trouble installing something new in
+  your system: &ldquo;I want to add the <i>glugtheory</i> package to my
+  <i>mumbleTeX v12.0</i> distribution on the <i>Grobble 2024</i>
+  operating system&rdquo;.
+<li> If you need to know how to do something, make clear what your
+  environment is: &ldquo;I want to do <em>x</em> in Plain TeX&rdquo;, or &ldquo;I
+  want to do <em>y</em> in LaTeX running the <i>boggle</i>
+  class&rdquo;.  If you thought you knew how, but your attempts are
+  failing, tell us what you&rsquo;ve tried: &ldquo;I&rsquo;ve already tried installing
+  the <i>elephant</i> in the <i>minicar</i> directory, and it
+  didn&rsquo;t work, even after refreshing the filename database&rdquo;.
+<li> If something&rsquo;s going wrong within (La)TeX, pretend you&rsquo;re
+  <a href="FAQ-latexbug.html">submitting a LaTeX bug report</a>,
+  and try to generate a <a href="FAQ-minxampl.html">minimum failing example</a>.
+  If your example 
+  needs your local <i>xyzthesis</i> class, or some other resource
+  not generally available, be sure to include a pointer to how the
+  resource can be obtained.
+<li> Be as succinct as possible.  Your helpers don&rsquo;t usually need to
+  know <em>why</em> you&rsquo;re doing something, just <em>what</em> you&rsquo;re
+  doing and where the problem is.
+</ul>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html
new file mode 100644
index 00000000000..7f2c267226b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html
@@ -0,0 +1,12 @@
+<head>
+<title>UK TeX FAQ -- question label atsign</title>
+</head><body>
+<h3>How to type an &lsquo;@&rsquo; sign?</h3>
+<p/>Long ago, some packages used to use the &lsquo;@&rsquo; sign as a command, 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.
+<p/>Ordinary people (such as the author of this FAQ) need only type
+&lsquo;@&rsquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html
new file mode 100644
index 00000000000..1c73cdc7fbe
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label atsigns</title>
+</head><body>
+<h3><code>\</code><code>@</code> and <code>@</code> in macro names</h3>
+<p/>Macro names containing <code>@</code> are <em>internal</em> to LaTeX, and
+without special treatment just don&rsquo;t work in ordinary use.  A nice
+example of the problems caused is discussed in 
+<a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>&rdquo;.
+<p/>The problems users see are caused by copying bits of a class
+(<code>.cls</code> file) or 
+package (<code>.sty</code> file) into a document, or by including a class or
+package file into a LaTeX document by some means other than
+<code>\</code><code>documentclass</code> or <code>\</code><code>usepackage</code>.  LaTeX defines internal
+commands whose names contain the character <code>@</code> 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, <code>\</code><code>documentclass</code> and <code>\</code><code>usepackage</code> play around with the
+meaning of <code>@</code>.
+<p/>If you&rsquo;ve included a file some other way (for example, using
+<code>\</code><code>input</code>), you can probably solve the problem by using the correct
+command.
+<p/>If you&rsquo;re using a fragment of a package or class, you may well feel
+confused: books such as the first edition of the 
+<a href="FAQ-books.html">The LaTeX Companion</a> 
+are full of fragments of packages as examples for you to employ.
+The second edition of the <em>Companion</em> makes clearer how you
+should use these fragments, and in addition, the code of
+all the examples is now available on CTAN.
+To see the technique in practice, look at the example below, from file
+<i>2-2-7.ltx</i> in the <em>Companion</em> examples directory:
+<blockquote>
+<pre>
+\makeatletter
+\renewcommand\subsection{\@startsection
+  {subsection}{2}{0mm}%name, level, indent
+  {-\baselineskip}%             beforeskip
+  {0.5\baselineskip}%            afterskip
+  {\normalfont\normalsize\itshape}}% style
+\makeatother
+</pre>
+</blockquote><p>
+(That example appears on page 29 of <em>The LaTeX Companion</em>,
+second edition.)
+<p/>The alternative is to treat all these fragments as a package proper,
+bundling them up into a <code>.sty</code> file and including them with
+<code>\</code><code>usepackage</code>; this way you hide your LaTeX internal code somewhere
+that LaTeX internal code is expected, which often looks &lsquo;tidier&rsquo;.
+<dl>
+<dt><tt><i>Examples from the Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html
new file mode 100644
index 00000000000..f1761290a2d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label atvert</title>
+</head><body>
+<h3><code>\</code><code>spacefactor</code> complaints</h3>
+<p/>The errors
+<pre>
+! You can't use `\spacefactor' in vertical mode.
+\@-&gt;\spacefactor 
+                 \@m 
+</pre>
+or
+<pre>
+! You can't use `\spacefactor' in math mode.
+\@-&gt;\spacefactor 
+                 \@m 
+</pre>
+or simply
+<pre>
+! Improper \spacefactor.
+...
+</pre>
+bites the LaTeX programmer who uses an internal command without taking
+&ldquo;precautions&rdquo;.  The problem is discussed in detail in
+
+&ldquo;<a href="FAQ-atsigns.html"><code>@</code> in macro names</a>&rdquo;,
+together with solutions.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html
new file mode 100644
index 00000000000..882a922f255
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label backref</title>
+</head><body>
+<h3>References from the bibliography to the citation</h3>
+<p/>A link (or at least a page reference), from the bibliography to the
+citing command, is often useful in large documents.
+<p/>Two packages support this requirement, <i>backref</i> and
+<i>citeref</i>.  <i>Backref</i> is part of the
+<i>hyperref</i> bundle, and supports hyperlinks back to the citing
+command.  <i>Citeref</i> is the older, and seems to rely on rather
+simpler (and therefore possibly more stable) code.  Neither collapses
+lists of pages (&ldquo;<code>5, 6, 7</code>&rdquo; comes out as such, rather than as
+&ldquo;<code>5&ndash;7</code>&rdquo;), 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 <i>hyperref</i>-related
+<i>backref</i>, since the concept of multiple hyperlinks from the
+same anchor is less than appealing.)
+<dl>
+<dt><tt><i>backref.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>citeref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/citeref.zip">macros/latex/contrib/citeref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/citeref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/citeref/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html
new file mode 100644
index 00000000000..4ca66686b50
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label badhyph</title>
+</head><body>
+<h3>Improper <code>\</code><code>hyphenation</code> will be flushed</h3>
+<p/>For example
+<pre>
+! Improper \hyphenation will be flushed.
+\'#1-&gt;{
+       \accent 19 #1}
+&lt;*&gt; \hyphenation{Ji-m\'e
+                        -nez}
+</pre>
+(in Plain TeX) or
+<pre>
+! Improper \hyphenation will be flushed.
+\leavevmode -&gt;\unhbox 
+                      \voidb@x 
+&lt;*&gt; \hyphenation{Ji-m\'e
+                        -nez}
+</pre>
+in LaTeX.
+<p/>As mentioned in <a href="FAQ-nohyph.html">&ldquo;hyphenation failures&rdquo;</a>,
+words with accents in them may not be hyphenated.  As a result, any
+such word is deemed improper in a <code>\</code><code>hyphenation</code> command.
+<p/>The solution is to use a font that contains the character in question,
+and to express the <code>\</code><code>hyphenation</code> command in terms of that
+character; this &ldquo;hides&rdquo; the accent from the hyphenation mechanisms.
+LaTeX users can be achieved this by use of the <i>fontenc</i>
+package (part of the LaTeX distribution).  If you select an 8-bit
+font with the package, as in <code>\</code><code>usepackage[T1]{fontenc}</code>,
+accented-letter commands such as the <code>\&rsquo;</code><code>e</code> in
+<code>\hyphenation{Ji-m\&rsquo;</code><code>e-nez}</code> automatically become the single accented
+character by the time the hyphenation gets to look at it.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html
new file mode 100644
index 00000000000..f04c9d28794
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html
@@ -0,0 +1,47 @@
+<head>
+<title>UK TeX FAQ -- question label balance</title>
+</head><body>
+<h3>Balancing columns at the end of a document</h3>
+<p/>The <i>twocolumn</i> 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 &mdash; such columns are said to be &ldquo;unbalanced&rdquo;.  Many (most?)
+people don&rsquo;t like unbalanced columns.
+<p/>The simplest solution to the problem is to use the <i>multicol</i>
+package in place of the <i>twocolumn</i> option, as
+<i>multicol</i> balances the columns on the final page by default.
+However, the use of <i>multicol</i> 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., <code>figure*</code>
+environment) floats. 
+<p/>As a result, there is a constant push for a means of balancing columns
+at the end of a <i>twocolumn</i> document.  Of course, the job can
+be done manually: <code>\</code><code>pagebreak</code> 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.
+<p/>The <i>flushend</i> package offers a solution to this problem.  It&rsquo;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 <a href="FAQ-patch.html">patching commands</a>.
+The package only changes the behaviour at end document (its
+<code>\</code><code>flushend</code> 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.
+<p/>The <i>balance</i> package also patches the output routine
+(somewhat more carefully than <i>flushend</i>).
+<p/>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&rsquo;s required in any instance can&rsquo;t really be
+expressed in current LaTeX) that led the author of
+<i>multicol</i> to suppress single-column-wide floats.
+<dl>
+<dt><tt><i>balance.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preprint.zip">macros/latex/contrib/preprint</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preprint.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint/">browse</a>)
+<dt><tt><i>flushend.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse</a>)
+<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<p/></dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html
new file mode 100644
index 00000000000..0d1a560fea1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html
@@ -0,0 +1,79 @@
+<head>
+<title>UK TeX FAQ -- question label baselinepar</title>
+</head><body>
+<h3>Only one <code>\</code><code>baselineskip</code> per paragraph</h3>
+<p/>The <code>\</code><code>baselineskip</code> is not (as one might hope) a property of a
+line, but of a paragraph.  As a result, in a <code>10pt</code> (nominal)
+document (with a default <code>\</code><code>baselineskip</code> of <code>12pt</code>), a
+single character with a larger size, as:
+<blockquote>
+<pre>
+{\Huge A}
+</pre>
+</blockquote><p>
+will be squashed into the paragraph: TeX will make sure it doesn&rsquo;t
+scrape up against the line above, but won&rsquo;t give it &ldquo;room to
+breathe&rdquo;, as it does the text at standard size; that is, its size
+(<code>24.88pt</code>) is taken account of, but its <code>\</code><code>baselineskip</code>
+(<code>30pt</code>) isn&rsquo;t.  Similarly
+<blockquote>
+<pre>
+Paragraph text ...
+{\footnotesize Extended interjection ...
+   ... into the paragraph.}
+      ... paragraph continues ...
+</pre>
+</blockquote><p>
+will look silly, since the <code>8pt</code> interjection will end up set
+on the <code>12pt</code> <code>\</code><code>baselineskip</code> of the paragraph, rather than
+its preferred <code>8.5pt</code>.  Finally, something like
+<blockquote>
+<pre>
+Paragraph text ...
+  ... paragraph body ends.
+{\footnotesize Short comment on paragraph.}
+
+Next paragraph starts...
+</pre>
+</blockquote><p>
+will set the body of the first paragraph on the constricted
+<code>\</code><code>baselineskip</code> of the <code>\</code><code>footnotesize</code> comment.
+<p/>So, how to deal with these problems?  The oversized (short) section is
+typically corrected by a <em>strut</em>: this word 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 <code>\</code><code>strut</code> to provide the
+equivalent of a metal-type strut for the size chosen.  So for the
+example above, we would type
+<blockquote>
+<pre>
+Paragraph text ...
+   {\Huge A\strut}
+   ... paragraph continues ...
+</pre>
+</blockquote><p>
+However, more extended insertions (whether of larger or smaller text)
+are always going to cause problems; while you can strut larger text,
+ensuring that you strut every line will be tiresome, and there&rsquo;s no
+such thing as a &ldquo;negative strut&rdquo; that pulls the lines together for
+smaller text.
+<p/>The only satisfactory way to deal with an extended insertion at a
+different size is to set it off as a separate paragraph.  A
+satisfactory route to achieving this is the <code>quote</code>
+environment, which sets its text modestly inset from the enclosing
+paragraph:
+<blockquote>
+<pre>
+Paragraph text ...
+\begin{quote}
+  \footnotesize This is an inset account
+  of something relevant to the enclosing
+  paragraph...
+\end{quote}
+... paragraph continues ...
+</pre>
+</blockquote><p>
+Such quote-bracketing also deals with the problem of a trailing
+comment on the paragraph.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html
new file mode 100644
index 00000000000..2e9553e7a6e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html
@@ -0,0 +1,14 @@
+<head>
+<title>UK TeX FAQ -- question label bibaccent</title>
+</head><body>
+<h3>Accents in bibliographies</h3>
+<p/>BibTeX not only has a tendency (by default) to mess about with the
+
+<a href="FAQ-capbibtex.html">case of letters in your bibliography</a>,
+also makes a hash of accent commands:
+&ldquo;<code>ma</code><code>\</code><code>~</code><code>nana</code>&rdquo; comes out as &ldquo;ma
+nana&rdquo; (!).  The solution is similar that of the letter case problem:
+enclose the troublesome sequence in braces, as
+&ldquo;<code>{</code><code>\</code><code>~</code><code>n}</code>&rdquo;, in this example.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html
new file mode 100644
index 00000000000..6bf4d75f2d8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label bibinline</title>
+</head><body>
+<h3>Putting bibliography entries in text</h3>
+<p/>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.
+<p/>Options for entries in running text are
+<ul>
+<li> The package <i>bibentry</i>, which puts slight restrictions
+  on the format of entry that your <code>.bst</code> file generates, but is
+  otherwise undemanding of the bibliography style.
+<li> The package <i>inlinebib</i>, which requires that you use its
+  <i>inlinebib.bst</i>.  <i>Inlinebib</i> was actually designed for
+  footnote citations: its <em>expected</em> use is that you place a
+  citation inline as the argument of a <code>\</code><code>footnote</code> command.
+<li> The package <i>jurabib</i>, 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: <i>jurabib.bst</i>, <i>jhuman.bst</i> and
+  two Chicago-like ones.
+</ul>
+<p/>Options for entries in footnotes are
+<ul>
+<li> The package <i>footbib</i>, and
+<li> Packages <i>jurabib</i> and <i>inlinebib</i>, again.
+</ul>
+Note that <i>jurabib</i> does the job using LaTeX&rsquo;s standard
+footnotes, whereas <i>footbib</i> creates its own sequence of
+footnotes.  Therefore, in a document which has other footnotes, it may
+be advisable to use <i>jurabib</i> (or of course
+<i>inlinebib</i>), to avoid confusion of footnotes and foot-citations.
+<dl>
+<dt><tt><i>bibentry.sty</i></tt><dd><em>Distributed with</em> <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+<dt><tt><i>footbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footbib.zip">macros/latex/contrib/footbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footbib/">browse</a>)
+<dt><tt><i>inlinebib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/inlinebib.zip">biblio/bibtex/contrib/inlinebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/inlinebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/inlinebib/">browse</a>)
+<dt><tt><i>jurabib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jurabib.zip">macros/latex/contrib/jurabib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jurabib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jurabib/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html
new file mode 100644
index 00000000000..055e46b3acb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label biblatex</title>
+</head><body>
+<h3>Replacing the BibTeX&ndash;LaTeX mechanism</h3>
+<p/>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 &ldquo;real-world&rdquo; use.
+<p/>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); and specialist BibTeX style files are
+available for use in non-technical papers.
+<p/>BibTeX uses a style language whose mechanisms are unfamiliar to
+most current programmers: it&rsquo;s difficult to learn, but since there are
+fewer opportunities to write the language, it&rsquo;s also difficult to become
+fluent (in the way that so many people fluently write the equally
+arcane TeX macro language).
+<p/>Oren Patashnik (the author of BibTeX) summarises the issues as he
+sees them, in a 
+<a href="http://tug.org/TUGboat/Articles/tb24-1/patashnik.pdf">TUG conference paper from 2003</a>
+that seems to suggest that we might expect a
+BibTeX 1.0...which hasn&rsquo;t (yet) appeared.
+<p/>In the absence of BibTeX 1.0, what do we need from the bibliography
+system of the future? &mdash; simple: a superset of what BibTeX does
+(or can be made to do), implemented in a simpler style language, with
+coherent multilingual capabilities.
+<p/>Of the direct BibTeX replacements, the only one whose authors have
+sufficient confidence to submit to CTAN is CrossTeX.
+CrossTeX&rsquo;s language feels familiar to the existing user of
+BibTeX, but it&rsquo;s redesigned in an object-oriented style, and looks
+(to a non-user) as if it may well be adequately flexible.
+<p/>CrossTeX&rsquo;s team respond to queries, and seem well aware of the
+need for multilingual support.  CrossTeX is probably a development
+to watch.
+<p/>Two interesting alternative approaches, that the author has
+investigated, are <i>amsrefs</i> and <i>biblatex</i>.
+<i>Amsrefs</i> does away with BibTeX altogether, while
+<i>biblatex</i> makes rather limited use of BibTeX.  Both are
+heavily dependent on LaTeX&rsquo;s support.
+<p/><i>Amsrefs</i> uses a transformed <code>.bib</code> file, which is
+expressed as LaTeX macros.  (The package provides a BibTeX style
+that performs the transformation, so that a LaTeX source containing
+a <code>\</code><code>nocite{*}</code> command enables BibTeX to produce a usable
+<i>amsrefs</i> bibliography database.)
+<p/><i>Amsrefs</i> is maintained by the AMS as part of its author
+support programme,
+<p/><i>Biblatex</i> uses BibTeX more-or-less as normal, but with
+<i>biblatex</i>&rsquo;s own style; the style of citations and of the
+bibliography itself is determined by the way your <i>biblatex</i>
+style has been set up.  This structure eliminates the collections of
+BibTeX styles, at a stroke; the package 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
+comes with answers to many of the questions asked in the bibliography
+sections of these FAQs.
+<p/><i>Biblatex</i> is released as experimental software, but it&rsquo;s
+clear that many users are already using it happily; Lehman is
+responsive to problem reports, at the moment, but a set of expert
+users is already establishing itself.
+<dl>
+<dt><tt><i>amsrefs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/amsrefs.zip">macros/latex/contrib/amsrefs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/amsrefs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/amsrefs/">browse</a>)
+<dt><tt><i>biblatex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/exptl/biblatex.zip">macros/latex/exptl/biblatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/exptl/biblatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/exptl/biblatex/">browse</a>)
+<dt><tt><i>CrossTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/crosstex/">biblio/crosstex/</a>
+</dl>
+<p/>
+<p/>
+
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=biblatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=biblatex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibplain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibplain.html
new file mode 100644
index 00000000000..6e2fc9e212b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibplain.html
@@ -0,0 +1,15 @@
+<head>
+<title>UK TeX FAQ -- question label bibplain</title>
+</head><body>
+<h3>Using BibTeX with Plain TeX</h3>
+<p/>The file <i>btxmac.tex</i> (which is part of the Eplain system)
+contains macros and documentation for using BibTeX with
+Plain TeX, either directly or with <a href="FAQ-eplain.html">Eplain</a>.  See
+<a href="FAQ-BibTeXing.html">the use of BibTeX</a> for more
+information about BibTeX itself.
+<dl>
+<dt><tt><i>btxmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain/tex/eplain/btxmac.tex">macros/eplain/tex/eplain/btxmac.tex</a>
+<dt><tt><i>eplain system</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html
new file mode 100644
index 00000000000..e82194c6ae8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html
@@ -0,0 +1,56 @@
+<head>
+<title>UK TeX FAQ -- question label bibprefixsort</title>
+</head><body>
+<h3>BibTeX sorting and name prefixes</h3>
+<p/>BibTeX recognises a bewildering array of name prefixes (mostly
+those deriving from European language names); it ignores the prefixes
+when sorting the bibliography &mdash; you want &ldquo;Ludwig van Beethoven&rdquo;
+sorted under &ldquo;Beethoven&rdquo;, not under &ldquo;van&rdquo;.  (Lamport made a witty
+deliberate mistake with Beethoven&rsquo;s name, in the first edition of his
+LaTeX manual.)
+<p/>However, a recurring issue is the desire to quote Lord Rayleigh&rsquo;s
+publications (&ldquo;Lord&rdquo; isn&rsquo;t an acceptable prefix), or names from
+languages that weren&rsquo;t considered when BibTeX was designed such as
+&ldquo;al-Wakil&rdquo; (transcribed from the Arabic).  What&rsquo;s needed is a
+separate &ldquo;sort key&rdquo;, but BibTeX only allows such a thing in
+citations of items that have no author or editor.
+<p/>The solution is to embed the sort key in the author&rsquo;s name, but to
+prevent it from being typeset.  Patashnik recommends a command
+<code>\</code><code>noopsort</code> (no-output-sortkey), which is defined and used as
+follows:
+<blockquote>
+<pre>
+@PREAMBLE{ {\providecommand{\noopsort}[1]{}} }
+...
+@ARTICLE{Rayleigh1,
+AUTHOR = "{\noopsort{Rayleigh}}{Lord Rayleigh}",
+...
+}
+</pre>
+
+</blockquote><p>
+Note that this <code>\</code><code>noopsort</code> applies to the last name in this kind of
+construct, so an author with an Arabic name might be rendered:
+<blockquote>
+<pre>
+...
+AUTHOR = "Ali {\noopsort{Hadiidii}}{al-Hadiidii}",
+...
+</pre>
+</blockquote><p>
+
+A further use might deal with word order games, as in the famous
+Vietnamese name:
+<blockquote>
+<pre>
+...
+AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}",
+...
+</pre>
+</blockquote><p>
+
+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...).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
new file mode 100644
index 00000000000..c8665ba7998
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
@@ -0,0 +1,55 @@
+<head>
+<title>UK TeX FAQ -- question label bibstrtl</title>
+</head><body>
+<h3>&lsquo;String too long&rsquo; in BibTeX</h3>
+<p/>The BibTeX diagnostic &ldquo;Warning&ndash;you&rsquo;ve exceeded 1000, the
+<code>global-string-size</code>, for entry <code>foo</code>&rdquo; 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
+<i>abstract.bst</i>, or styles derived from it.  (One doesn&rsquo;t
+ordinarily output annotations in other styles.)
+<p/>The solution is to make a copy of the style file (or get a clean copy
+from CTAN &mdash; <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a
+long file-name system, to <i>abstract-long.bst</i>).  Now edit it: find
+function <code>output.nonnull</code> and
+<ul>
+<li> change its first line (line 60 in the version on CTAN)
+  from
+  <blockquote>
+<pre>
+{ 's :=
+</pre>
+  </blockquote><p>
+to
+  <blockquote>
+<pre>
+{ swap$
+</pre>
+  </blockquote><p>
+  Finally,
+<li> delete the function&rsquo;s last line, which just says &ldquo;<code>s</code>
+  (line 84 in the version on CTAN).
+</ul>
+Finally, change your <code>\</code><code>bibliographystyle</code> command to refer to the
+name of the new file.
+<p/>This technique applies equally to any bibliography style: the same
+change can be made to any similar <code>output.nonnull</code> function.
+<p/>If you&rsquo;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&rsquo;t encounter
+BibTeX&rsquo;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:
+<blockquote>
+<pre>
+@article{long.boring,
+  author =    "Fred Verbose",
+  ...
+  abstract =  "{\input{abstracts/long.tex}}"
+}
+</pre>
+</blockquote><p>
+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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html
new file mode 100644
index 00000000000..1818cab7147
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label bibtocorder</title>
+</head><body>
+<h3>Table of contents rearranges &ldquo;<i>unsrt</i>&rdquo; ordering</h3>
+<p/>If you&rsquo;re using the <i>unsrt</i> bibliography style, you&rsquo;re
+expecting that your bibliography will <em>not</em> be sorted, but that
+the entries will appear in the order that they first appeared in your
+document.
+<p/>However, if you&rsquo;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 &ldquo;natural&rdquo; ordering
+produced by the <i>unsrt</i> style.  Similarly, if you have
+citations in captions, and have a list of figures (or tables).
+<p/>There&rsquo;s a pretty simple &ldquo;manual&rdquo; method for dealing with the
+problem &mdash; when you have the document stable:
+<ol>
+<li> Delete the <code>.aux</code> file, and any of <code>.toc</code>,
+  <code>.lof</code>, <code>.lot</code> files.
+<li> Run LaTeX.
+<li> Run BibTeX for the last time.
+<li> Run LaTeX often enough that things are stable again.
+</ol>
+Which is indeed simple, but it&rsquo;s going to get tedious when you&rsquo;ve
+found errors in your &ldquo;stable&rdquo; version, often enough.
+<p/>The package <i>notoccite</i> 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).
+<dl>
+<dt><tt><i>notoccite.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/notoccite.sty">macros/latex/contrib/misc/notoccite.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html
new file mode 100644
index 00000000000..4d2b65ca6cc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html
@@ -0,0 +1,91 @@
+<head>
+<title>UK TeX FAQ -- question label bibtranscinit</title>
+</head><body>
+<h3>&lsquo;Multi-letter&rsquo; initials in BibTeX</h3>
+<!-- compound initials, transcribed initials -->
+<p/>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:
+<blockquote>
+
+<pre>
+@article{epifanov1997,
+   author = {Epifanov, S. Yu. and Vigasin, A. A.},
+   title  = ...
+}
+</pre>
+</blockquote><p>
+Note that the &ldquo;Yu&rdquo; is the initial, not a complete name. However,
+BibTeX&rsquo;s algorithms will leave you with a citation &mdash; 
+slightly depending on the bibliographic style &mdash; that reads:
+&ldquo;S. Y. Epifanov and A. A. Vigasin, ...&rdquo;. instead of the intended
+&ldquo;S. Yu. Epifanov and A. A. Vigasin, ...&rdquo;.
+<p/>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
+<code>@preamble</code> directive:
+<blockquote>
+
+<pre>
+@preamble{ {\providecommand{\BIBYu}{Yu} } }
+
+@article{epifanov1997,
+   author   = {Epifanov, S. {\BIBYu}. and Vigasin, A. A.},
+   title    = ...
+}
+</pre>
+</blockquote><p>
+If you have many such commands, you may want to put them in a separate
+file and <code>\</code><code>input</code> that LaTeX file in a <code>@preamble</code>
+directive.
+<p/>An alternative is to make the transcription look like an accent, from
+BibTeX&rsquo;s point of view.  For this we need a control sequence that
+does nothing:
+<blockquote>
+<pre>
+@article{epifanov1997,
+   author   = {Epifanov, S. {\relax Yu}. and Vigasin, A. A.},
+   title    = ...
+}
+</pre>
+</blockquote><p>
+
+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.
+<p/>&ldquo;Compound&rdquo; initials (for single names made up of two or more words)
+may be treated in the same way, so one can enter Forster&rsquo;s rather
+complicated name as:
+<blockquote>
+<pre>
+@article{forster2006,
+  author   = {Forster, P.M. {\relax de F.} and Collins, M.},
+  title    = ...
+</pre>
+</blockquote><p>
+
+The same trick can be played if you&rsquo;re entering whole names:
+<blockquote>
+<pre>
+...
+  author   = {Epifanov, Sasha {\relax Yu}ri and
+...
+</pre>
+</blockquote><p>
+(though no guarantee, that either of those names is right, is
+offered!)
+However, if you&rsquo;re typing the names in the &ldquo;natural&rdquo; (Western) way,
+with given names first, the trick:
+<blockquote>
+<pre>
+...
+  author   = {P.M. {\relax de F.} Forster and
+...
+</pre>
+</blockquote><p>
+doesn&rsquo;t work &mdash; &ldquo;de F. Forster&rdquo; is treated as a compound family
+names.
+<p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html
new file mode 100644
index 00000000000..d590e8896a4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label bold-extras</title>
+</head><body>
+<h3>How to do bold-tt or bold-sc</h3>
+<p/>LaTeX, as delivered, offers no means of handling bold &ldquo;teletype&rdquo;
+or small-caps fonts.  There&rsquo;s a practical reason for this (Knuth never
+designed such fonts), but there are typographical considerations too
+(the &ldquo;medium weight&rdquo; <code>cmtt</code> font is already pretty bold (by
+comparison with other fixed-width fonts), and bold small-caps is not
+popular with many professional typographers).
+<p/>There&rsquo;s a set of &ldquo;extra&rdquo; Metafont files on CTAN that provide bold
+versions of both <code>cmtt</code> and <code>cmcsc</code> (the small caps font).  With
+modern TeX distributions, one may bring these fonts into use simply
+by placing them in an 
+<a href="FAQ-install-where.html">appropriate place in the <em>texmf</em> tree</a>
+(these are (La)TeX-specific files, so the &ldquo;<em>public</em>&rdquo; supplier
+would be an appropriate place).  Once you&rsquo;ve 
+<a href="FAQ-inst-wlcf.html">rebuilt the file indexes as necessary</a>,
+TeX (and friends) will automatically build whatever font files they
+need when you first make reference to them.  There&rsquo;s a jiffy package
+<i>bold-extra</i> that builds the necessary font data structures
+so that you can use the fonts within LaTeX.
+<p/>Another alternative is to use the <a href="FAQ-ECfonts.html">EC fonts</a>,
+which come with bold variants of the small-caps fonts.
+<p/>If you need to use Type 1 fonts, you can&rsquo;t proceed with Knuth-style
+fonts, since there are no Type 1 versions of the <i>mf-extra</i>
+set.  There are, however, Type 1 distributions of the EC fonts, so you
+can switch to EC and use them; alternatives are discussed in
+<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>.
+<p/>Of course, commercial fixed-width fonts (even the default
+<i>Courier</i>) almost always come with a bold variant, so that&rsquo;s
+not a problem.  Furthermore <a href="FAQ-usepsfont.html">PSNFSS</a>
+will usually provide &ldquo;faked&rdquo; small caps fonts, and has no
+compunctions about providing them in a bold form.  <i>Courier</i>
+is (as we all know, to our cost) freely available; a far more
+presentable monospace font is <i>LuxiMono</i>, which is also
+freely available (monospace text in the typeset version of this
+FAQ uses <i>LuxiMono</i>, with the metrics and LaTeX
+support available on the archive.
+<dl>
+<dt><tt><i>bold-extra.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/bold-extra.sty">macros/latex/contrib/misc/bold-extra.sty</a>
+<dt><tt><i>bold tt and small caps fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.zip">fonts/cm/mf-extra/bold</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/mf-extra/bold/">browse</a>)
+<dt><tt><i>LuxiMono fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.zip">fonts/LuxiMono</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/LuxiMono/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html
new file mode 100644
index 00000000000..b2cfa27d529
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label boldgreek</title>
+</head><body>
+<h3>Setting bold Greek letters in LaTeX</h3>
+<p/>The issue here is complicated by the fact that <code>\</code><code>mathbf</code> (the
+command for setting bold <em>text</em> in TeX maths) affects a select
+few mathematical symbols (the uppercase Greek letters).  However
+lower-case Greek letters behave differently from upper-case Greek
+letters (due to Knuth&rsquo;s esoteric font encoding decisions).  However,
+<code>\</code><code>mathbf</code> <em>can&rsquo;t</em> be used even for upper-case Greek letters in
+the AMSLaTeX <i>amsmath</i> package, which
+disables this font-switching and you must use one of the techniques
+outlined below.
+<p/>The Plain TeX solution <em>does</em> work, in a limited way:
+<blockquote>
+<pre>
+{\boldmath$\theta$}
+</pre>
+</blockquote><p>
+but <code>\</code><code>boldmath</code> may not be used in maths mode, so this &lsquo;solution&rsquo;
+requires arcana such as:
+<blockquote>
+<pre>
+$... \mbox{\boldmath$\theta$} ...$
+</pre>
+</blockquote><p>
+which then causes problems in superscripts, etc.
+<p/>These problems may be addressed by using a bold mathematics package.
+<ul>
+<li> The <i>bm</i> package, which is part of the LaTeX tools
+  distribution, defines a command <code>\</code><code>bm</code> which may be used anywhere
+  in maths mode.
+<li> The <i>amsbsy</i> package (which is part of AMSLaTeX)
+  defines a command <code>\</code><code>boldsymbol</code>, which (though slightly less
+  comprehensive than <code>\</code><code>bm</code>) covers almost all common cases.
+</ul>
+<p/>All these solutions cover all mathematical symbols, not merely Greek
+letters.
+<dl>
+<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>amsbsy.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html
new file mode 100644
index 00000000000..f466f8f7bb6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html
@@ -0,0 +1,139 @@
+<head>
+<title>UK TeX FAQ -- question label books</title>
+</head><body>
+<h3>Books on TeX and its relations</h3>
+<p/>While Knuth&rsquo;s book is the definitive reference for TeX, there are
+other books covering TeX:
+<dl>
+<dt>The TeXbook<dd>by Donald Knuth (Addison-Wesley, 1984,
+  ISBN 0-201-13447-0, paperback ISBN 0-201-13448-9)
+<dt>A Beginner&rsquo;s Book of TeX<dd>by Raymond Seroul and Silvio Levy,
+  (Springer Verlag, 1992, ISBN 0-387-97562-4)
+<dt>TeX by Example: A Beginner&rsquo;s Guide<dd>by Arvind Borde 
+  (Academic Press, 1992, ISBN 0-12-117650-9 &mdash; now out of print)
+<dt>Introduction to TeX<dd>by Norbert Schwarz (Addison-Wesley,
+  1989, ISBN 0-201-51141-X &mdash; now out of print)
+<dt>A Plain TeX Primer<dd>by Malcolm Clark (Oxford University
+  Press, 1993, ISBNs 0-198-53724-7 (hardback) and 0-198-53784-0
+  (paperback))
+<dt>A TeX Primer for Scientists<dd>by Stanley Sawyer and Steven
+  Krantz (CRC Press, 1994, ISBN 0-849-37159-7)
+<dt>TeX by Topic<dd>by Victor Eijkhout (Addison-Wesley, 1992,
+  ISBN 0-201-56882-9 &mdash; now out of print, but see
+  <a href="FAQ-ol-books.html">online books</a>)
+<dt>TeX for the Beginner<dd>by Wynter Snow (Addison-Wesley, 1992,
+  ISBN 0-201-54799-6)
+<dt>TeX for the Impatient<dd>by Paul W. Abrahams, Karl Berry and
+  Kathryn A. Hargreaves (Addison-Wesley, 1990,
+  ISBN 0-201-51375-7 &mdash; now out of print, but see
+  <a href="FAQ-ol-books.html">online books</a>)
+<dt>TeX in Practice<dd>by Stephan von Bechtolsheim (Springer
+  Verlag, 1993, 4 volumes, ISBN 3-540-97296-X for the set, or
+
+  Vol. 1: ISBN 0-387-97595-0, 
+  Vol. 2: ISBN 0-387-97596-9, 
+  Vol. 3: ISBN 0-387-97597-7, and 
+  Vol. 4: ISBN 0-387-97598-5)
+
+<dt>TeX: Starting from Square One<dd>
+  by Michael Doob (Springer
+  Verlag, 1993, ISBN 3-540-56441-1 &mdash; now out of print)
+<dt>The Joy of TeX<dd>by Michael D. Spivak (second edition,
+  AMS, 1990, ISBN 0-821-82997-1)
+<dt>The Advanced TeXbook<dd>by David Salomon (Springer Verlag, 1995,
+  ISBN 0-387-94556-3)
+</dl>
+A collection of Knuth&rsquo;s publications about typography is also available:
+<dl>
+<dt>Digital Typography<dd>by Donald Knuth (CSLI and Cambridge
+  University Press, 1999, ISBN 1-57586-011-2, paperback
+  ISBN 1-57586-010-4).
+</dl>
+and in late 2000, a &ldquo;Millennium Boxed Set&rdquo; of all
+5 volumes of Knuth&rsquo;s &ldquo;Computers and Typesetting&rdquo; series (about
+TeX and Metafont) was published by Addison Wesley:
+<dl>
+<dt>Computers &amp; Typesetting, Volumes A&ndash;E Boxed Set<dd>by Donald Knuth
+  (Addison-Wesley, 2001, ISBN 0-201-73416-8).
+</dl>
+
+For LaTeX, see:
+<dl>
+<dt>LaTeX, a Document Preparation System<dd>by Leslie Lamport
+  (second edition, Addison Wesley, 1994, ISBN 0-201-52983-1)
+<dt>Guide to LaTeX<dd>Helmut Kopka and Patrick W. Daly (fourth
+  edition, Addison-Wesley, 2004, ISBN 0-321-17385-6)
+<dt>The LaTeX Companion<dd>by Frank Mittelbach, Michel Goossens,
+  Johannes Braams, David Carlisle and Chris Rowley (second edition,
+  Addison-Wesley, 2004, ISBN-10 0-201-36299-6, ISBN-13 978-0-201-36299-2)
+<dt>The LaTeX Graphics Companion:<dd>
+  <em>Illustrating documents with TeX and PostScript</em> by Michel
+  Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and
+  Herbert Voss (second edition, Addison-Wesley, 2007,
+  ISBN-10 0-321-50892-0, ISBN-13 978-0-321-50892-8)
+<dt>The LaTeX Web Companion:<dd>
+  <em>Integrating TeX, HTML and XML</em> by Michel
+  Goossens and Sebastian Rahtz (Addison-Wesley, 1999, ISBN 0-201-43311-7)
+<dt>TeX Unbound:<dd>
+  <em>LaTeX and TeX strategies for fonts, graphics, and more</em>
+  by Alan Hoenig (Oxford University Press, 1998, ISBN 0-19-509685-1
+  hardback, ISBN 0-19-509686-X paperback)
+<dt>Math into LaTeX:<dd><em>An Introduction to LaTeX and AMSLaTeX</em>
+  by George Gr&auml;tzer (third edition Birkh&auml;user and Springer Verlag,
+  2000, ISBN 0-8176-4431-9, ISBN 3-7643-4131-9)
+
+
+
+<dt>Digital Typography Using LaTeX<dd>Incorporating some
+  multilingual aspects, and use of <a href="FAQ-omegaleph.html">Omega</a>, by
+  Apostolos Syropoulos, Antonis Tsolomitis and Nick Sofroniou
+  (Springer, 2003, ISBN 0-387-95217-9).
+<p/>  A list of errata for the first printing is available from:
+  <a href="http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html">http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html</a>
+<dt>First Steps in LaTeX<dd>by George Gr&auml;tzer (Birkh&auml;user, 1999,
+  ISBN 0-8176-4132-7) 
+<dt>LaTeX: Line by Line:<dd>
+  <em>Tips and Techniques for Document Processing</em>
+  by Antoni Diller (second edition, John Wiley &amp; Sons,
+  1999, ISBN 0-471-97918-X)
+<dt>LaTeX for Linux:<dd><em>A Vade Mecum</em>
+  by Bernice Sacks Lipkin (Springer-Verlag, 1999,
+  ISBN 0-387-98708-8, second printing)
+</dl>
+A sample of George Gr&auml;tzer&rsquo;s &ldquo;Math into LaTeX&rdquo;, in Adobe
+Acrobat format, and example files
+
+for the three LaTeX Companions, and for
+Gr&auml;tzer&rsquo;s &ldquo;First Steps in LaTeX&rdquo;, are all available on
+CTAN.
+<p/>There&rsquo;s a nicely-presented list of of &ldquo;recommended books&rdquo; to be had
+on the web: <a href="http://www.macrotex.net/texbooks/">http://www.macrotex.net/texbooks/</a>
+<p/>The list of Metafont books is rather short:
+<dl>
+<dt>The Metafontbook<dd>by Donald Knuth (Addison Wesley, 1986,
+  ISBN 0-201-13445-4, ISBN 0-201-52983-1 paperback)
+</dl>
+Alan Hoenig&rsquo;s &lsquo;<i>TeX Unbound</i>&rsquo; includes some discussion and
+examples of using Metafont.
+<p/>A book covering a wide range of topics (including installation and
+maintenance) is:
+<dl>
+<dt>Making TeX Work<dd>by Norman Walsh (O&rsquo;Reilly and Associates,
+  Inc, 1994, ISBN 1-56592-051-1)
+</dl>
+The book is decidedly dated, and is now out of print, but a copy is
+available via <code>sourceforge</code> and on CTAN, 
+and we list it under &ldquo;<a href="FAQ-ol-books.html">online books</a>&rdquo;.
+<p/><p/>This list only covers books in English: notices of new books, or
+warnings that books are now out of print are always welcome.  However,
+this FAQ does <em>not</em> carry reviews of current published material.
+<dl>
+<dt><tt><i>Examples for First Steps in LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/FirstSteps.zip">info/examples/FirstSteps</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/FirstSteps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/FirstSteps/">browse</a>)
+<dt><tt><i>Examples for LaTeX Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>)
+<dt><tt><i>Examples for LaTeX Graphics Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/lgc.zip">info/examples/lgc</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/lgc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/lgc/">browse</a>)
+<dt><tt><i>Examples for LaTeX Web Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/lwc.zip">info/examples/lwc</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/lwc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/lwc/">browse</a>)
+
+<dt><tt><i>Sample of Math into LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/mil/mil.pdf">info/mil/mil.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html
new file mode 100644
index 00000000000..a43bde32fba
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label braket</title>
+</head><body>
+<h3>Set specifications and Dirac brackets</h3>
+<p/>One of the few glaring omissions from TeX&rsquo;s mathematical
+typesetting capabilities is a means of setting separators in the
+middle of mathematical expressions.  TeX provides primitives called
+<code>\</code><code>left</code> and <code>\</code><code>right</code>, which can be used to modify brackets (of
+whatever sort) around a mathematical expression, as in:
+
+<code>\</code><code>left(</code><code> &lt;expression&gt; </code><code>\</code><code>right)</code> &mdash; the size of the
+parentheses is matched to the vertical extent of the expression.
+<p/>However, in all sorts of mathematical enterprises one may find oneself
+needing a <code>\</code><code>middle</code> command, to be used in expressions like
+<blockquote>
+<pre>
+\left\{ x \in \mathbb{N} \middle| x \mbox{ even} \right\}
+</pre>
+
+</blockquote><p>
+to specify the set of even natural numbers.  The 
+<a href="FAQ-etex.html">e-TeX system</a>
+defines just such a command, but users of Knuth&rsquo;s original need some
+support.  Donald Arseneau&rsquo;s <i>braket</i> package provides commands
+for set specifications (as above) and for Dirac brackets (and bras and
+kets).  The package uses the e-TeX built-in command if it finds
+itself running under e-TeX.
+<dl>
+<dt><tt><i>braket.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/braket.sty">macros/latex/contrib/misc/braket.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html
new file mode 100644
index 00000000000..6d2d0339c93
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label breakbox</title>
+</head><body>
+<h3>Breaking boxes of text</h3>
+<p/>(La)TeX boxes may not be broken, in ordinary usage: once you&rsquo;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&rsquo;t fit in the
+typeset area.
+<p/>If you want a substantial portion of your text to be framed (or
+coloured), the restriction starts to seem a real imposition.
+Fortunately, there are ways around the problem.
+<p/>The <i>framed</i> package provides <code>framed</code> and
+<code>shaded</code> 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 &ldquo;lose&rdquo; footnotes,
+marginpars and head-line entries, and will not work with
+<i>multicol</i> or other column-balancing macros.  The
+<i>memoir</i> class includes the functionality of the
+<i>framed</i> package.
+<p/>The <i>boites</i> package provides a <code>breakbox</code>
+environment; examples of its use may be found in the distribution, and
+the package&rsquo;s <i>README</i> file contains terse documentation.  The
+environments may be nested, and may appear inside
+<code>multicols</code> environments; however, floats, footnotes and
+marginpars will be lost.
+<p/>For Plain TeX users, the facilities of the <i>backgrnd</i>
+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
+<i>shade</i>, which is distributed as tex macros and
+device-independent Metafont for the shading).  The author of
+<i>backgrnd</i> claims that the package works with LaTeX 2.09, but
+there are reasons to suspect that it may be unstable working with
+current LaTeX.
+<dl>
+<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a>
+<dt><tt><i>boites.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/boites.zip">macros/latex/contrib/boites</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/boites.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/boites/">browse</a>)
+<dt><tt><i>framed.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>shade.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.zip">macros/generic/shade</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/shade/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html
new file mode 100644
index 00000000000..beaa7106abb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html
@@ -0,0 +1,45 @@
+<head>
+<title>UK TeX FAQ -- question label breaklinks</title>
+</head><body>
+<h3>Link text doesn&rsquo;t break at end line</h3>
+<!-- hyperref overfull link -->
+<p/>When using the <i>hyperref</i> package, you make a block of text
+&ldquo;active&rdquo; when you define a hyper-link (when the user clicks on
+that text, the reader program will divert to the <em>target</em> of the
+link).
+<p/>The <i>hyperref</i> package uses a <em>driver</em> (in the same way
+as the <i>graphics</i> package does), to determine how to implement
+all that hyper-stuff.
+<p/>If you use the driver for <i>dvips</i> output (presumably you want
+to distill the resulting PostScript), limitations in the way <i>dvips</i>
+deals with the <code>\</code><code>special</code> commands mean that <i>hyperref</i>
+must prevent link anchors from breaking at the end of lines.  Other
+drivers (notably those for PDFTeX and for <i>dvipdfm</i>) don&rsquo;t
+suffer from this problem.
+<p/>The problem may occur in a number of different circumstances.  For a
+couple of them, there are work-arounds:
+<p/>First, if you have an URL which is active (so that clicking on
+it will activate your web browser to &ldquo;go to&rdquo; the URL).  In
+this case <i>hyperref</i> employs the <i>url</i> package to
+split up the URL (as described in 
+<a href="FAQ-setURL.html">typesetting URLs</a>), but the
+<i>dvips</i> driver then suppresses the breaks.  The way out is
+the <i>breakurl</i> package, which modifies the <code>\</code><code>url</code> 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.
+<p/>Second, if you have a table of contents, list of figure or tables, or
+the like, <i>hyperref</i> 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
+<i>dvips</i> driver will prevent that.  In this case, load
+<i>hyperref</i> with the option <code>linktocpage</code>, and only
+the page number will be made active.
+<p/>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 PDF generation mechanism.
+<dl>
+<dt><tt><i>breakurl.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.zip">macros/latex/contrib/breakurl</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/breakurl/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html
new file mode 100644
index 00000000000..ab441192f5f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label brkinline</title>
+</head><body>
+<h3>Line-breaking in in-line maths</h3>
+<p/>TeX, by default, allows you to split a mathematical expression at
+the end of the line; it allows breaks at relational operators (like
+&ldquo;=&rdquo;, &ldquo;&lt;&rdquo;, etc.) and at binary operators (like &ldquo;+&rdquo;,
+&ldquo;-&rdquo;, etc.).  In the case of large expressions, this can sometimes be
+a life-saver.
+<p/>However, in the case of simple expressions like a=b+c, a
+break can be really disturbing to the reader, and one would like to
+avoid it.
+<p/>Fortunately, these breaks are controllable: there are &ldquo;penalties&rdquo;
+associated with each type of operator: the penalty 
+ says how
+undesirable a break at each point is.  Default values are:
+<blockquote>
+<pre>
+\relpenalty   = 500
+\binoppenalty = 700
+</pre>
+</blockquote><p>
+You make the break progressively less attractive by increasing these
+values.  You can actually forbid all breaks, everywhere, by:
+<blockquote>
+<pre>
+\relpenalty   = 10000
+\binoppenalty = 10000
+</pre>
+</blockquote><p>
+If you want just to prevent breaks in a single expression, write:
+<blockquote>
+<pre>
+{%
+  \relpenalty   = 10000
+  \binoppenalty = 10000
+  $a=b+c$
+}
+</pre>
+</blockquote><p>
+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:
+<blockquote>
+<pre>
+${a+b+c+d} = z+y+x+w$
+</pre>
+</blockquote><p>
+The braces say &ldquo;treat this subformula as one atom&rdquo; and (in TeX at
+least) atoms don&rsquo;t get split: not a <code>\</code><code>binoppenalty</code> change in sight.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html
new file mode 100644
index 00000000000..e31223e21bf
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label buffovl</title>
+</head><body>
+<h3>Unable to read an entire line</h3>
+<p/>TeX belongs to the generation of applications written for
+environments that didn&rsquo;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).
+<p/>When you overwhelm TeX&rsquo;s input mechanism, you get told:
+<pre>
+! Unable to read an entire line---bufsize=3000.
+    Please ask a wizard to enlarge me.
+</pre>
+(for some value of &lsquo;3000&rsquo; &mdash; the quote was from a
+<i>comp.text.tex</i> posting by a someone who was presumably
+using an old TeX).
+<p/>As the message implies, there&rsquo;s (what TeX thinks of as a) line in
+your input that&rsquo;s &ldquo;too long&rdquo; (to TeX&rsquo;s way of thinking).  Since
+modern distributions tend to have tens of thousands of bytes of input
+buffer, it&rsquo;s somewhat rare that these messages occur &ldquo;for real&rdquo;.
+Probable culprits are:
+<ul>
+<li> 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&rsquo; explicit
+  record-ending characters, this is nowadays rather a rare cause of
+  the problem.
+<li> 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).
+</ul>
+<p/>The usual advice is to ignore what TeX says (i.e., anything about
+enlarging), and to put the problem right in the source. 
+<p/>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 &ldquo;word&rdquo; structure) so that they are nowhere any longer
+than a given length; so the solution is just to edit the file.
+<p/>If the problem is a ridiculous preview section, try using
+<i>ghostscript</i> to reprocess the file, outputting a &ldquo;plain
+<code>.eps</code>&rdquo; file.  (<i>Ghostscript</i> is distributed with a script
+<i>ps2epsi</i> which will regenerate the preview if necessary.)
+Users of the shareware program <i>GSview</i> will find buttons to
+perform the required transformation of the file being displayed.
+<dl>
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+<dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html
new file mode 100644
index 00000000000..3f58bef68bb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html
@@ -0,0 +1,48 @@
+<head>
+<title>UK TeX FAQ -- question label bug</title>
+</head><body>
+<h3>What to do if you find a bug</h3>
+
+
+
+
+<p/>For a start, make entirely sure you <em>have</em> found a bug.
+Double-check with books about TeX, LaTeX, or whatever you&rsquo;re using;
+compare what you&rsquo;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.
+<p/>If you&rsquo;ve found a bug in TeX itself, you&rsquo;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 <em>you</em>
+think you have found a genuine fault in TeX itself (or Metafont, or the
+CM fonts, or the TeXbook), don&rsquo;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 AMS
+(<i>bnb@ams.org</i>), or contact
+<a href="FAQ-TUGstar.html">TUG</a>.
+<p/>If you&rsquo;ve found a bug in LaTeX2e, <a href="FAQ-latexbug.html">report it</a>
+using mechanisms supplied by the LaTeX team.  (Please be
+careful to ensure you&rsquo;ve got a LaTeX bug, or a bug in one of the
+&ldquo;required&rdquo;  packages distributed by the LaTeX team.)
+<p/>If you&rsquo;ve found a bug in a contributed LaTeX package, you could try
+contacting the author (if you can find a contact address).  However,
+it&rsquo;s generally best to treat any package as unsupported, in the first
+instance, and only try the author <em>after</em> mailing list/news group
+support has failed you.
+<p/>If you&rsquo;ve found a bug in LaTeX 2.09, or some other such unsupported
+software, you may find help or
+<em>de facto</em> support on a newsgroup such as
+<i>comp.tex.tex</i> or on a mailing list such as
+<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>; be careful to include a 
+<a href="FAQ-minxampl.html">code example</a> of the
+failure, if relevant.
+<p/>Failing all else, you may need to pay for
+help &mdash; TUG maintains a 
+<a href="http://www.tug.org/consultants.html">register of TeX consultants</a>.
+<p/><p/>
+
+
+
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html
new file mode 100644
index 00000000000..03d4b998995
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html
@@ -0,0 +1,76 @@
+<head>
+<title>UK TeX FAQ -- question label buildbib</title>
+</head><body>
+<h3>Creating a BibTeX bibliography file</h3>
+<p/>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.
+<p/>Each entry in the bibliography has a <em>type</em> and a unique
+<em>key</em>.  The bibliography is read, by BibTeX, using the details
+specified in a <em>bibliography style</em>.  From the style, BibTeX
+finds what entry types are permissible, what <em>fields</em> each entry
+type has, and how to format the whole entry.
+<p/>The type specifies the type of document you&rsquo;re making reference to; it
+may run all the way from things like &ldquo;<code>Book</code>&rdquo; and
+&ldquo;<code>Proceedings</code>&rdquo; (which may even contain other citations
+of type &ldquo;<code>InBook</code>&rdquo; or  &ldquo;<code>InProceedings</code>&rdquo;)
+through dissertation styles like  &ldquo;<code>PhdThesis</code>&rdquo; to
+otherwise-uncategorisable things such as &ldquo;<code>Misc</code>&rdquo;.  The
+unique key is something you choose yourself: it&rsquo;s what you use when
+you want to <a href="FAQ-usebibtex.html">cite an entry in the file</a>.  People
+commonly create a key that combines the (primary) author&rsquo;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 <code>.bib</code> file as <code>Dyson20.1</code>.
+<p/>So, noting the rules of the style, you have &lsquo;simply&rsquo; to write a
+bibliography database.  Fortunately, there are several tools to help
+in this endeavour:
+<ul>
+<li> Most of the better <a href="FAQ-editors.html">(La)TeX-oriented editors</a>
+  have &ldquo;BibTeX modes&rdquo;.
+<li> If you have an existing <code>thebibliography</code>
+  environment, the <i>Perl</i> script <i>tex2bib</i> will
+  probably help.
+<li> 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.
+<p/>  Tools such as <i>Xbibfile</i> (a graphical user interface),
+  <i>ebib</i> (a database application written to run &lsquo;inside&rsquo;
+  <i>emacs</i>) and 
+  <i>btOOL</i> (a set of <i>perl</i> tools for building 
+  BibTeX database handlers) are available from CTAN.
+<p/>  Other systems, such as
+  <a href="http://refdb.sourceforge.net/"><i>RefDB</a></i>,
+  <a href="http://www.nongnu.org/biborb">BibORB</a>,
+  <a href="http://bibdesk.sourceforge.net/"><i>BibDesk</a></i>,
+  <a href="http://pybliographer.org"><i>pybliographer</a></i> and the
+  <i>Java</i>-based
+  <a href="http://freshmeat.net/projects/bibkeeper/"><i>Bibkeeper</a></i>
+  and <a href="http://jabref.sourceforge.net"><i>JabRef</a></i> (which
+  claims to supersede <i>Bibkeeper</i>)
+  are only available from their development sites.
+
+<li> Some commercial citation-management systems will export in
+  BibTeX format; an example is
+  <a href="http://www.endnote.com/">EndNote</a>.
+<li> Data from on-line citation databases may often be translated to
+  BibTeX format by utilities to be found on CTAN.  For
+  example, the <i>Perl</i> script <i>isi2bibtex</i> will
+  translate citations from ISI &ldquo;Web of knowledge&rdquo; (a
+  subscription service, available to UK academics via
+  BIDS).  UK academics may translate BIDS downloads
+  using <i>bids.to.bibtex</i>
+</ul>
+<dl>
+<dt><tt><i>bids.to.bibtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bids/bids.to.bibtex">biblio/bibtex/utils/bids/bids.to.bibtex</a>
+<dt><tt><i>btOOL</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/btOOL.zip">biblio/bibtex/utils/btOOL</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/btOOL.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/btOOL/">browse</a>)
+<dt><tt><i>ebib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/ebib.zip">biblio/bibtex/utils/ebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/ebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/ebib/">browse</a>)
+<dt><tt><i>isi2bibtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/isi2bibtex.zip">biblio/bibtex/utils/isi2bibtex</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/isi2bibtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/isi2bibtex/">browse</a>)
+<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/tex2bib">biblio/bibtex/utils/tex2bib/tex2bib</a>
+<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a>
+<dt><tt><i>xbibfile</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.zip">biblio/bibtex/utils/xbibfile</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/xbibfile/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html
new file mode 100644
index 00000000000..68d98f6654e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html
@@ -0,0 +1,15 @@
+<head>
+<title>UK TeX FAQ -- question label cancellation</title>
+</head><body>
+<h3>Cancelling terms in maths expressions</h3>
+<p/>A technique used when explaining the behaviour of expressions or
+equations (often for pedagogical purposes).  The <i>cancel</i>
+package provides several variants of cancellation marks
+(&ldquo;<code>\</code>&rdquo;, &ldquo;<code>/</code>&rdquo; and &ldquo;<code>X</code>&rdquo;), and
+a means of cancelling &lsquo;to&rsquo; a particular value.
+<p/>Documentation of <i>cancel</i> is in the package file.
+<dl>
+<dt><tt><i>cancel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/cancel.sty">macros/latex/contrib/misc/cancel.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html
new file mode 100644
index 00000000000..054ae10fb92
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label capbibtex</title>
+</head><body>
+<h3>Capitalisation in BibTeX</h3>
+<p/>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&rsquo;s lights (the rules come from
+the <em>Chicago Manual of Style</em>) it can be troublesome, since
+BibTeX fails to recognise special uses (such as acronyms, chemical
+formulae, etc.).
+<p/>The solution is to enclose the letter or letters, whose capitalisation
+BibTeX should not touch, in braces, as:
+<blockquote>
+<pre>
+title = {The {THE} operating system},
+</pre>
+</blockquote><p>
+Sometimes you find BibTeX changing the case of a single letter
+inappropriately.  No matter: the technique can be applied to single
+letters, as in:
+<blockquote>
+<pre>
+title = {Te{X}niques and tips},
+</pre>
+</blockquote><p>
+If your document design specification requires a different style of
+capitalisation, you should acquire a bibliography style that doesn&rsquo;t
+enforce BibTeX&rsquo;s default rules.  It is definitely <em>not</em> a good
+idea to enclose an entire title in braces, as in
+<blockquote>
+<pre>
+title = {{TeXniques and tips}},
+</pre>
+</blockquote><p>
+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 to the way you
+are thinking today.
+<p/>There&rsquo;s more on the subject in the
+
+<a href="FAQ-BibTeXing.html">BibTeX documentation</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html
new file mode 100644
index 00000000000..d9dfeb65092
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label captsty</title>
+</head><body>
+<h3>The style of captions</h3>
+<p/>Changes to the style of captions may be made by redefining the commands
+that produce the caption.  So, for example, <code>\</code><code>fnum@figure</code> (which
+produces the float number for figure floats) may be redefined, in a
+package of your own, or between
+<a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code>&ndash;<code>\</code><code>makeatother</code></a>:
+<blockquote>
+<pre>
+\renewcommand{\fnum@figure}{\textbf{Fig.~\thefigure}}
+</pre>
+
+</blockquote><p>
+which will cause the number to be typeset in bold face.  (Note that
+the original definition used 
+<a href="FAQ-fixnam.html"><code>\</code><code>figurename</code></a>.)  More elaborate changes can be
+made by patching the <code>\</code><code>caption</code> command, but since there are
+packages to do the job, such changes (which can get rather tricky)
+aren&rsquo;t recommended for ordinary users.
+<p/>The <i>float</i> package provides some control of the appearance of
+captions, though it&rsquo;s principally designed for the creation of
+non-standard floats.  The <i>caption</i> and <i>ccaption</i>
+(note the double &ldquo;<em>c</em>&rdquo;) packages provide a range of different
+formatting options.
+<p/><i>ccaption</i> also provides &lsquo;continuation&rsquo; captions and captions
+that can be placed outside of float environments.  The (very simple)
+<i>capt-of</i> 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.
+<p/>The <i>memoir</i> class includes the facilities of the
+<i>ccaption</i> package; the <i>KOMA-script</i> classes also
+provide a wide range of caption-formatting commands.
+<p/>The documentation of <i>caption</i> is available by processing a
+file <i>manual.tex</i>, which is created when you unpack
+<i>caption.dtx</i>
+<p/>Note that the previously-recommended package <i>caption2</i> has
+now been overtaken again by <i>caption</i>; however,
+<i>caption2</i> remains available for use in older documents.
+<dl>
+<dt><tt><i>caption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.zip">macros/latex/contrib/caption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/caption/">browse</a>)
+<dt><tt><i>capt-of.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/capt-of.sty">macros/latex/contrib/misc/capt-of.sty</a>
+<dt><tt><i>ccaption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse</a>)
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
new file mode 100644
index 00000000000..147a29f6e65
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label casechange</title>
+</head><body>
+<h3>Case-changing oddities</h3>
+<p/>TeX provides two primitive commands <code>\</code><code>uppercase</code> and
+<code>\</code><code>lowercase</code> to change the case of text; they&rsquo;re not much used, but
+are capable creating confusion.
+<p/>The two commands do not expand the text that is their parameter &mdash;
+the result of <code>\</code><code>uppercase{abc}</code> is &lsquo;<code>ABC</code>&rsquo;, but
+<code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always &lsquo;<code>\</code><code>abc</code>&rsquo;, whatever the
+meaning of <code>\</code><code>abc</code>.  The commands are simply interpreting a table of
+equivalences between upper- and lowercase characters.
+They have (for example) no mathematical sense, and
+<blockquote>
+<pre>
+\uppercase{About $y=f(x)$}
+</pre>
+</blockquote><p>
+will produce
+<blockquote>
+<pre>
+ABOUT $Y=F(X)$
+</pre>
+</blockquote><p>
+which is probably not what is wanted.
+<p/>In addition, <code>\</code><code>uppercase</code> and <code>\</code><code>lowercase</code> do not deal very well
+with non-American characters, for example
+<code>\</code><code>uppercase{<code>\</code><code>ae</code>}</code> is the same as <code>\</code><code>ae</code>.
+<p/>LaTeX provides commands <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code>
+which fixes the latter problem.  These commands are used in the
+standard classes to produce upper case running heads for chapters
+and sections.
+<p/>Unfortunately <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> do not solve
+the other problems with <code>\</code><code>uppercase</code>, so for example a section
+title containing <code>\</code><code>begin{tabular}</code> ...
+<code>\</code><code>end{tabular}</code> will produce a running head containing
+<code>\</code><code>begin{TABULAR}</code>.  The simplest solution to this problem is
+using a user-defined command, for example: 
+<blockquote>
+<pre>
+\newcommand{\mytable}{\begin{tabular}...
+  \end{tabular}}
+\section{A section title \protect\mytable{}
+  with a table}
+</pre>
+</blockquote><p>
+Note that <code>\</code><code>mytable</code> has to be protected, otherwise it will be
+expanded and made upper case; you can achieve the same result by
+declaring it with <code>\</code><code>DeclareRobustCommand</code>, in which case the
+<code>\</code><code>protect</code> won&rsquo;t be necessary.
+<p/>David Carlisle&rsquo;s <i>textcase</i> package
+addresses many of these problems in a transparent way.  It defines
+commands <code>\</code><code>MakeTextUppercase</code> and <code>\</code><code>MakeTextLowercase</code> which do
+upper- or lowercase, with the fancier features of the LaTeX
+standard <code>\</code><code>Make*</code>-commands but without the problems
+mentioned above.  Load the package with
+<code>\</code><code>usepackage[overload]{textcase}</code>, and it will redefine the LaTeX
+commands (<em>not</em> the TeX primitive commands <code>\</code><code>uppercase</code> and
+<code>\</code><code>lowercase</code>), so that section headings and the like don&rsquo;t produce
+broken page headings.
+<dl>
+<dt><tt><i>textcase.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.zip">macros/latex/contrib/textcase</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html
new file mode 100644
index 00000000000..c7a89b8a53a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html
@@ -0,0 +1,83 @@
+<head>
+<title>UK TeX FAQ -- question label changebars</title>
+</head><body>
+<h3>Marking changed parts of your document</h3>
+<p/>One often needs clear indications of how a document has changed, but
+the commonest technique, &ldquo;change bars&rdquo; (also known as &ldquo;revision
+bars&rdquo;), requires surprisingly much
+trickery of the programmer (the problem being that TeX &lsquo;proper&rsquo;
+doesn&rsquo;t provide the programmer with any information about the
+&ldquo;current position&rdquo; from which a putative start- or end-point of a
+bar might be calculated; PDFTeX <em>does</em> provide the
+information, but we&rsquo;re not aware yet of any programmer taking
+advantage of the fact to write a PDFTeX-based changebar package).
+<p/>The simplest package that offers change bars is Peter Schmitt&rsquo;s
+<i>backgrnd.tex</i>; this was written as a Plain TeX 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 <i>backgrnd</i> patches their output routine, and
+will watch its behaviour very carefully (patching the LaTeX output
+routine is not something to undertake lightly...).
+<p/>The longest-established LaTeX-specific solution is the
+<i>changebar</i> package,
+which uses <code>\</code><code>special</code> commands supplied by the driver you&rsquo;re using.
+You need therefore to tell the package which driver to generate
+<code>\</code><code>special</code>s for (in the same way that you need to tell the
+<i>graphics</i> package); the list of available drivers is pretty
+wide, but does not include <i>dvipdfm</i>.  The package comes with
+a shell script <i>chbar.sh</i> (for use on Unix machines) that
+will compare two documents and generate a third which is marked-up
+with <i>changebar</i> macros to highlight changes.  The
+shareware <i>WinEDT</i> editor has a macro that will generate
+<i>changebar</i> (or other) macros to show differences from an
+earlier version of your file, stored in an
+<i>RCS</i>-controlled repository &mdash; see
+<a href="http://www.winedt.org/Macros/LaTeX/RCSdiff.php">http://www.winedt.org/Macros/LaTeX/RCSdiff.php</a>
+<p/>The <i>vertbars</i> package uses the techniques of the
+<i>lineno</i> package (which it loads, so the <i>lineno</i>
+itself must be installed); it&rsquo;s thus the smallest of the packages for
+change bar marking, since it leaves all the trickery to another
+package.  <i>Vertbars</i> defines a <code>vertbar</code>
+environment to create changebars.
+<p/>The <i>framed</i> package is
+another that provides bars as a side-effect of other desirable
+functionality: its <code>leftbar</code> 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.
+<p/>Finally, the <i>memoir</i> class allows marginal editorial comments,
+which you can obviously use to delimit areas of changed text.
+<p/>An even more comprehensive way to keep track of changes is employed by
+some word-processors &mdash; to produce a document that embodies both
+&ldquo;old&rdquo; and &ldquo;new&rdquo; versions.
+<p/>To this end, the package <i>changes</i> 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.
+<p/>The <i>Perl</i> script <i>latexdiff</i> 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,
+
+  <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/latexdiff-man.pdf">latexdiff-man.pdf</a>
+  (part of the distribution).
+A rudimentary revision facility is provided by another
+<i>Perl</i> script, <i>latexrevise</i>, which accepts or rejects
+all changes.  Manual editing of the difference file can be used to 
+accept or reject selected changes only.
+<dl>
+<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a>
+<dt><tt><i>changebar.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.zip">macros/latex/contrib/changebar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changebar/">browse</a>)
+<dt><tt><i>changes.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changes.zip">macros/latex/contrib/changes</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changes.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changes/">browse</a>)
+<dt><tt><i>framed.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a>
+<dt><tt><i>latexdiff, latexrevise</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.zip">support/latexdiff</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/">browse</a>)
+<dt><tt><i>lineno.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.zip">macros/latex/contrib/lineno</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lineno/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>vertbars.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/vertbars.sty">macros/latex/contrib/misc/vertbars.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html
new file mode 100644
index 00000000000..8de6cff6081
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label changemargin</title>
+</head><body>
+<h3>Changing the margins in LaTeX</h3>
+<p/>Changing the layout of a document&rsquo;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 &ldquo;works&rdquo; and to ensure that the result is pleasing to the
+eye.
+<p/>LaTeX&rsquo;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 &ldquo;one-inch margins all round on A4
+paper&rdquo; 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).
+<p/>So Lamport&rsquo;s warning to beginners in his section on &lsquo;Customizing the
+Style&rsquo; &mdash; &ldquo;don&rsquo;t do it&rdquo; &mdash; should not lightly be ignored.
+<p/>This set of FAQs 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 needing to
+think about them, but 
+<p/>The following answers deal with the ways one may choose to proceed:
+<ul>
+<li> <a href="FAQ-marginpkgs.html">Choose which package to use</a>.
+<li> <a href="FAQ-marginmanual.html">Find advice on setting up page layout by hand</a>.
+</ul>
+There is a related question &mdash; how to change the layout
+temporarily &mdash; and there&rsquo;s an answer that covers that, too:
+<ul>
+<li> <a href="FAQ-chngmargonfly.html">Change the margins on the fly</a>.
+</ul>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html
new file mode 100644
index 00000000000..550ae8aeb80
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label chapbib</title>
+</head><body>
+<h3>Separate bibliographies per chapter?</h3>
+<p/>A separate bibliography for each &lsquo;chapter&rsquo; of a document can be provided
+with the package <i>chapterbib</i> (which comes with a bunch of
+other good bibliographic things).  The package allows you a
+different bibliography for each <code>\</code><code>include</code>d file (i.e., despite the
+package&rsquo;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).
+<p/>The package <i>bibunits</i> 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 <code>bibunit</code>
+environment so that users can select their own structuring.
+<dl>
+<dt><tt><i>chapterbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse</a>)
+<dt><tt><i>bibunits.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibunits.zip">macros/latex/contrib/bibunits</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibunits.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bibunits/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html
new file mode 100644
index 00000000000..46eb2c9bac7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label charshift</title>
+</head><body>
+<h3>Weird characters in <i>dvips</i> output</h3>
+<!-- fi ligature pound pounds sterling elephants -->
+<p/>You&rsquo;ve innocently generated output, using <i>dvips</i>, and there
+are weird transpositions in it: for example, the <code>fi</code> ligature has
+appeared as a textsterling symbol.
+This is an unwanted side-effect of the precautions
+outlined in <a href="FAQ-dvips-pdf.html">generating PostScript for PDF</a>.
+The <code>-G1</code> switch discussed in that question is appropriate for
+Knuth&rsquo;s text fonts, but doesn&rsquo;t work with text fonts that don&rsquo;t follow
+Knuth&rsquo;s patterns (such as fonts supplied by Adobe).
+<p/>If the problem arises, suppress the <code>-G1</code> switch: if you were using it
+explicitly, <em>don&rsquo;t</em>; if you were using <code>-Ppdf</code>, add <code>-G0</code> to
+suppress the implicit switch in the pseudo-printer file.
+<p/>The problem has been corrected in <i>dvips</i> v 5.90 (and later
+versions), which should be available in any recent TeX distribution.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html
new file mode 100644
index 00000000000..a41bdb014bb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label checksum</title>
+</head><body>
+<h3>Checksum mismatch in font</h3>
+<p/>When Metafont generates a font it includes a checksum in the font bitmap
+file, and in the font metrics file (TFM).  (La)TeX includes
+the checksum from the TFM file in the DVI file.
+<p/>When <i>dvips</i> (or other DVI drivers) process a
+DVI file, they compare checksums in the DVI file to
+those in the bitmap fonts being used for character images.  If the
+checksums don&rsquo;t match, it means the font metric file used by (La)TeX
+was not generated from the same Metafont program that generated the
+font.
+<p/>This commonly occurs when you&rsquo;re processing someone else&rsquo;s DVI
+file.
+<p/>The fonts on your system may also be at fault: possibilities are that
+the new TFM was not installed, or installed in a path after an
+old TFM file, or that you have a personal cache of bitmaps from
+an old version of the font.
+<p/>In any case, look at the output &ndash; the chances are that it&rsquo;s perfectly
+OK, since metrics tend not to change, even when the bitmaps are
+improved.  (Indeed, many font designers &mdash; Knuth included &mdash;
+maintain the metrics come what may.)
+<p/>If the output <em>does</em> look bad, your only chance is to regenerate
+things from scratch.  Options include: flushing your bitmap cache,
+rebuild the TFM file locally, and so on.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=checksum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=checksum</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html
new file mode 100644
index 00000000000..18c0bec481d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label chngmargonfly</title>
+</head><body>
+<h3>Changing margins &ldquo;on the fly&rdquo;</h3>
+<p/>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&rsquo;t change the text width
+on the fly, and LaTeX only ever looks at text height when starting
+a new page.
+<p/>So the simple rule is that the parameters should only be
+changed in the preamble of the document, i.e., before the
+<code>\</code><code>begin{document}</code> statement (so before any typesetting has
+happened.
+<p/>To adjust text width within a document we define an environment:
+<blockquote>
+<pre>
+\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}}
+</pre>
+</blockquote><p>
+The environment takes two arguments, and will indent the left and
+right margins, respectively, by the parameters&rsquo; values. Negative
+values will cause the margins to be narrowed, so
+<code>\</code><code>begin{changemargin}{-1cm}{-1cm}</code> narrows the left and right
+margins by 1 centimetre.
+<p/>Given that TeX can&rsquo;t do this, how does it work? &mdash; well, the
+environment (which is a close relation of the LaTeX
+<code>quote</code> environment) <em>doesn&rsquo;t</em> change the text width
+as far as TeX is concerned: it merely moves text around inside the
+width that TeX believes in.
+<p/>The <i>changepage</i> package provides ready-built commands to do the
+above; it includes provision for changing the shifts applied to your
+text according to whether you&rsquo;re on an odd (<em>recto</em>) or an even
+(<em>verso</em>) page of a two-sided document.
+<p/>The (earlier) package <i>chngpage</i> provides the same facilities,
+but it uses rather different syntax.  <i>Changepage</i>&rsquo;s structure
+matches that of the <i>memoir</i> class, and it should be used for
+any new work.
+<p/>Changing the vertical dimensions of a page is more clumsy still: the
+LaTeX command <code>\</code><code>enlargethispage</code> adjusts the size of the current
+page by the size of its argument.  Common uses are
+<blockquote>
+<pre>
+\enlargethispage{\baselineskip}
+</pre>
+</blockquote><p>
+to make the page one line longer, or
+<blockquote>
+<pre>
+\enlargethispage{-\baselineskip}
+</pre>
+</blockquote><p>
+to make the page one line shorter.
+<dl>
+<dt><tt><i>changepage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/changepage.sty">macros/latex/contrib/misc/changepage.sty</a>
+<dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html
new file mode 100644
index 00000000000..ebe82a177d8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html
@@ -0,0 +1,89 @@
+<head>
+<title>UK TeX FAQ -- question label citeURL</title>
+</head><body>
+<h3>URLs in BibTeX bibliographies</h3>
+<p/>There is no citation type for URLs, <em>per se</em>, 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.
+<p/>The actual information that need be available in a citation of an
+URL is discussed at some length in the publicly available
+on-line 
+
+<a href="http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm">extracts of ISO 690&ndash;2</a>;
+the techniques below do <em>not</em> satisfy all the requirements of
+ISO 690&ndash;2, but they offer a solution that is at least
+available to users of today&rsquo;s tools.
+<p/>Until the new version of BibTeX arrives, the simplest technique is
+to use the <code>howpublished</code> field of the standard styles&rsquo; <code>@misc</code>
+function.  Of course, the strictures
+about <a href="FAQ-setURL.html">typesetting URLs</a> still apply, so the
+entry will look like:
+<blockquote>
+<pre>
+@misc{...,
+  ...,
+  howpublished = "\url{http://...}"
+}
+</pre>
+</blockquote><p>
+A possible alternative approach is to use BibTeX styles other than
+the standard ones, that already have URL entry types.
+Candidates are:
+<ul>
+<li> The <i>natbib</i> styles (<i>plainnat</i>,
+  <i>unsrtnat</i> and <i>abbrevnat</i>), which are extensions of
+  the standard styles, principally for use with <i>natbib</i>
+  itself.  However, they&rsquo;ve acquired URLs and other &ldquo;modern&rdquo;
+  entries along the way.  The same author&rsquo;s <i>custom-bib</i> is
+  also capable of generating styles that honour URL entries.
+<li> The <i>babelbib</i> bundle, which offers 
+  <a href="FAQ-i18nbib.html">multilingual bibliographies</a>, similarly provides a
+  set of standard-style equivalents that have URL entries.
+<li> More modern styles such as the <i>harvard</i> package (if the
+  citation styles are otherwise satisfactory for you).
+  <i>Harvard</i> bibliography styles all include a &ldquo;<code>url</code>&rdquo;
+  field in their specification; however, the typesetting offered is
+  somewhat feeble (though it does recognise and use
+  <i>LaTeX2HTML</i> macros if they are available, to create
+  hyperlinks).
+</ul>
+You can also acquire new BibTeX styles by use of Norman Gray&rsquo;s
+<i>urlbst</i> system, which is based on a <i>Perl</i> script
+that edits an existing BibTeX style file to produce a new
+style. The new style thus generated has a <code>webpage</code> entry type, and
+also offers support for <code>url</code> and <code>lastchecked</code> fields
+in the other entry types.  The <i>Perl</i> script comes with a set
+of converted versions of the standard bibliography styles.
+<p/>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:
+<blockquote>
+<pre>
+@techreport{...,
+  ...,
+  note = "Also available as \url{http://...}"
+}
+</pre>
+
+</blockquote><p>
+There is good reason to use the <i>url</i> or <i>hyperref</i>
+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 &lsquo;natural&rsquo; breakpoints, BibTeX will
+insert a comment (&lsquo;<code>%</code>&rsquo;) character ... which
+is an acceptable character in an URL.  Any current version of the
+<i>url</i> or <i>hyperref</i> package detects this
+&ldquo;<code>%</code>&ndash;end-of-line&rdquo; structure in its argument, and
+removes it.
+<dl>
+<dt><tt><i>babelbib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse</a>)
+<dt><tt><i>custom-bib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>)
+<dt><tt><i>harvard.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/harvard.zip">macros/latex/contrib/harvard</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/harvard.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/harvard/">browse</a>)
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>natbib styles</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+<dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a>
+<dt><tt><i>urlbst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/urlbst.zip">biblio/bibtex/contrib/urlbst</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/urlbst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/urlbst/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html
new file mode 100644
index 00000000000..2fbf74de819
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label citesort</title>
+</head><body>
+<h3>Sorting and compressing citations</h3>
+<p/>If you give LaTeX
+<code>\</code><code>cite{fred,joe,harry,min}</code>, its default commands could give
+something like &ldquo;[2,6,4,3]&rdquo;;
+this looks awful.  One can of course get the things in order by
+rearranging the keys in the <code>\</code><code>cite</code> command, but who wants to do
+that sort of thing for no more improvement than &ldquo;[2,3,4,6]&rdquo;?
+<p/>The <i>cite</i> package sorts the numbers and detects consecutive
+sequences, so creating &ldquo;[2&ndash;4,6]&rdquo;.  The <i>natbib</i> package,
+with the <code>numbers</code> and <code>sort&amp;compress</code> options, will
+do the same when working with its own numeric bibliography styles
+(<i>plainnat.bst</i> and <i>unsrtnat.bst</i>).
+<p/>If you might need to make hyperreferences to your citations,
+<i>cite</i> isn&rsquo;t adequate.  If you add the <i>hypernat</i>
+package:
+<pre>
+  \usepackage[...]{hyperref}
+  \usepackage[numbers,sort&compress]{natbib}
+  \usepackage{hypernat}
+  ...
+  \bibliographystyle{plainnat}
+</pre>
+the <i>natbib</i> and <i>hyperref</i> packages will interwork.
+<dl>
+<dt><tt><i>cite.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse</a>)
+<dt><tt><i>hypernat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/hypernat.sty">macros/latex/contrib/misc/hypernat.sty</a>
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>plainnat.bst</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+<dt><tt><i>unsrtnat.bst</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html
new file mode 100644
index 00000000000..b5b23e0c7b9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label clsvpkg</title>
+</head><body>
+<h3>What are LaTeX classes and packages?</h3>
+<p/>Current LaTeX makes a distinction between the macros that define the
+overall layout of a document, and the macros that tweak that layout
+(to one extent or another) to provide what the author <em>really</em>
+wants.
+<p/>The distinction was not very clear in LaTeX 2.09, and after some
+discussion (in the later stages of development of current LaTeX)
+the names &ldquo;class&rdquo; and &ldquo;package&rdquo; were applied to the two concepts.
+<p/>The idea is that a document&rsquo;s <em>class</em> tells LaTeX what sort of
+document it&rsquo;s dealing with, while the <em>packages</em> the document
+loads &ldquo;refine&rdquo; that overall specification.
+<p/>On the disc, the files only appear different by virtue of their name
+&ldquo;extension&rdquo; &mdash; class files are called <code>*.cls</code> while package
+files are called <code>*.sty</code>.  Thus we find that the LaTeX
+standard <i>article</i> class is represented on disc by a file called
+<i>article.cls</i>, while the <i>footmisc</i> package (which
+refines <i>article</i>&rsquo;s definition of footnotes) is represented on
+disc by a file called <i>footmisc.sty</i>.
+<p/>The user defines the class of his document with the
+<code>\</code><code>documentclass</code> command (typically the first command in a
+document), and loads packages with the <code>\</code><code>usepackage</code> command.  A
+document may have several <code>\</code><code>usepackage</code> commands, but it may have
+only one <code>\</code><code>documentclass</code> command.  (Note that there are
+programming-interface versions of both commands, since a class may
+choose to load another class to refine its capabilities, and both
+classes and packages may choose to load other packages.)
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html
new file mode 100644
index 00000000000..cd2b68610d8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html
@@ -0,0 +1,69 @@
+<head>
+<title>UK TeX FAQ -- question label cmdstar</title>
+</head><body>
+<h3>Commands defined with * options</h3>
+<p/>LaTeX commands commonly have &ldquo;versions&rdquo; defined with an asterisk
+tagged onto their name: for example <code>\</code><code>newcommand</code> and
+<code>\</code><code>newcommand*</code> (the former defines a <code>\</code><code>long</code> version of the
+command).
+<p/>The simple-minded way for a user to write such a command involves use
+of the <i>ifthen</i> package:
+<blockquote>
+<pre>
+\newcommand{\mycommand}[1]{\ifthenelse{\equal{#1}{*}}%
+  {\mycommandStar}%
+  {\mycommandNoStar{#1}}%
+}
+\newcommand{\mycommandStar}{starred version}
+\newcommand{\mycommandNoStar}[1]{normal version}
+</pre>
+</blockquote><p>
+
+This does the trick, for sufficiently simple commands, but it has
+various tiresome failure modes, and it requires <code>\</code><code>mycommandnostar</code>
+to take an argument.
+<p/>Of course, the LaTeX kernel has something slicker than this:
+<blockquote>
+<pre>
+\newcommand{\mycommand}{\@ifstar
+                     \mycommandStar%
+                     \mycommandNoStar%
+}
+\newcommand{\mycommandStar}[2]{starred version}
+\newcommand{\mycommandNoStar}[1]{normal version}
+</pre>
+
+</blockquote><p>
+(Note that arguments to <code>\</code><code>mycommandStar</code> and <code>\</code><code>mycommandNoStar</code>
+are independent &mdash; either can have their own arguments, unconstrained
+by the technique we&rsquo;re using, unlike the trick described above.)
+The <code>\</code><code>@ifstar</code> trick is all very well, is fast and efficient, but
+it requires the definition to be 
+<a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code> protected</a>.
+<p/>A pleasing alternative is the <i>suffix</i> package.  This elegant
+piece of code allows you to define variants of your commands:
+
+<blockquote>
+<pre>
+\newcommand\mycommand{normal version}
+\WithSuffix\newcommand\mycommand*{starred version}
+</pre>
+</blockquote><p>
+The package needs <a href="FAQ-etex.html">e-LaTeX</a>, but any new enough
+distribution defines LaTeX as e-LaTeX by default.  Command
+arguments may be specified in the normal way, in both command
+definitions (after the &ldquo;<code>*</code>&rdquo; in the <code>\</code><code>WithSuffix</code>
+version).  You can also use the TeX primitive commands, creating a
+definition like:
+<blockquote>
+<pre>
+\WithSuffix\gdef\mycommand*{starred version}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>ifthen.sty</i></tt><dd>Part of the LaTeX distribution
+<dt><tt><i>suffix.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>)
+</dl>
+<p/>
+<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html
new file mode 100644
index 00000000000..4ec9f46961d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label codelist</title>
+</head><body>
+<h3>Code listings in LaTeX</h3>
+<p/>&lsquo;Pretty&rsquo; code listings are sometimes considered worthwhile by the
+&ldquo;ordinary&rdquo; 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.
+<p/>  <a href="FAQ-verbfile.html">Verbatim listings</a> are dealt with elsewhere,
+
+as is the problem of 
+<a href="FAQ-algorithms.html">typesetting algorithm specifications</a>.
+<p/>The <i>listings</i> 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 <i>listings</i>
+to typeset snippets that you include within your source:
+<blockquote>
+<pre>
+\usepackage{listings}
+\lstset{language=C}
+...
+\begin{document}
+\begin{lstlisting}
+#include &lt;stdio.h&gt;
+
+int main(int argc, char ** argv)
+{
+  printf("Hello world!\n");
+  return 0;
+}
+\end{lstlisting}
+\end{document}
+</pre>
+</blockquote><p>
+or you can have it typeset whole files:
+<blockquote>
+<pre>
+\usepackage{listings}
+\lstset{language=C}
+...
+\begin{document}
+\lstinputlisting{main.c}
+\end{document}
+</pre>
+</blockquote><p>
+These very simple examples may be decorated in a huge variety of ways,
+and of course there are other languages in the package&rsquo;s vocabulary
+than just <i>C</i>...
+<p/>Most people, advising others on (La)TeX lists, seem to regard
+<i>listings</i> as the be-all and end-all on this topic.  But there
+<em>are</em> alternatives, which may be worth considering, in some
+situations.
+<p/><i>Highlight</i> is attractive if you need more than one output
+format for your program: as well as (La)TeX output,
+<i>highlight</i> will produce (X)HTML, RTF
+and XSL-FO representations of your program listing.
+Documentation is available on the 
+<a href="http://www.andre-simon.de/"><i>highlight</a> project site</i>.
+<p/>The <i>lgrind</i> system is another well-established pre-compiler,
+with all the facilities one might need and a wide repertoire of
+languages; it is derived from the very long-established
+<i>tgrind</i>, whose output is based on Plain TeX
+<p/>The <i>tiny_c2l</i> system is more recent: users are encouraged to
+generate their own driver files for languages it doesn&rsquo;t already deal
+with.
+<p/>The <i>C++2LaTeX</i> system comes with strong recommendations for
+use with C and C++.
+<p/>An extremely simple system is <i>c2latex</i>, for which you write
+LaTeX source in your C program comments.  The program then
+converts your program into a LaTeX document for processing.  The
+program (implicitly) claims to be &ldquo;self-documenting&rdquo;.
+<dl>
+<dt><tt><i>c2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/c2latex.zip">support/c2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/c2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/c2latex/">browse</a>)
+<dt><tt><i>C++2LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/C++2LaTeX-1_1pl1.zip">support/C++2LaTeX-1_1pl1</a> (<a href="ftp://cam.ctan.org/tex-archive/support/C++2LaTeX-1_1pl1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/C++2LaTeX-1_1pl1/">browse</a>)
+<dt><tt><i>highlight</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/highlight.zip">support/highlight</a> (<a href="ftp://cam.ctan.org/tex-archive/support/highlight.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/highlight/">browse</a>)
+<dt><tt><i>lgrind</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/lgrind.zip">support/lgrind</a> (<a href="ftp://cam.ctan.org/tex-archive/support/lgrind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/lgrind/">browse</a>)
+<dt><tt><i>listings.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listings.zip">macros/latex/contrib/listings</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listings.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listings/">browse</a>)
+<dt><tt><i>tgrind</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tgrind.zip">support/tgrind</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tgrind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tgrind/">browse</a>)
+<dt><tt><i>tiny_c2l</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tiny_c2l.zip">support/tiny_c2l</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tiny_c2l.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tiny_c2l/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html
new file mode 100644
index 00000000000..195e7d938ee
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html
@@ -0,0 +1,140 @@
+<head>
+<title>UK TeX FAQ -- question label commercial</title>
+</head><body>
+<h3>Commercial TeX implementations</h3>
+<!-- windows,macintosh,commercial -->
+<p/>There are many commercial implementations of TeX. The first
+appeared not long after TeX itself appeared.
+<p/>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.
+<p/>In general, a commercial implementation will come &lsquo;complete&rsquo;, that is,
+with suitable previewers and printer drivers.  They normally also have
+extensive documentation (<em>i.e</em>., not just the TeXbook!) and some
+sort of support service.  In some cases this is a toll free number
+(probably applicable only within the USA and or Canada), but others
+also have email, and normal telephone and fax support.
+<dl>
+<dt>PC; TrueTeX<dd> Runs on all versions of Windows.
+  <blockquote>
+    Richard J. Kinch<br>
+    TrueTeX Software<br>
+    7890 Pebble Beach Court<br>
+    Lake Worth FL 33467<br>
+    USA<br>
+    Tel: +1 561-966-8400<br>
+    Email: <a href="mailto:kinch@truetex.com"><i>kinch@truetex.com</i></a><br>
+    Web: <a href="http://www.truetex.com/">http://www.truetex.com/</a>
+  </blockquote><p>
+  Source: Mail from Richard Kinch, August 2004.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<dt>pcTeX<dd> Long-established: pcTeX32 is a Windows implementation.
+  <blockquote>
+    Personal TeX Inc<br>
+    725 Greenwich Street, Suite 210 <br>
+    San Francisco, CA 94133<br>
+    USA<br>
+    Tel: 800-808-7906 (within the USA)<br>
+    Tel: +1 415-296-7550<br>
+    Fax: +1 415-296-7501<br>
+    Email: <a href="mailto:sales@pctex.com"><i>sales@pctex.com</i></a><br>
+    Web: <a href="http://www.pctex.com/">http://www.pctex.com/</a>
+  </blockquote><p>
+  Source: Personal TeX Inc web site, December 2004
+<dt>PC; VTeX<dd> DVI, PDF and HTML
+  backends, Visual Tools and Type 1 fonts
+  <blockquote>
+    MicroPress Inc<br>
+    68-30 Harrow Street<br>
+    Forest Hills, NY 11375<br>
+    USA<br>
+    Tel: +1 718-575-1816<br>
+    Fax: +1 718-575-8038<br>
+    Email: <a href="mailto:support@micropress-inc.com"><i>support@micropress-inc.com</i></a><br>
+    Web: <a href="http://www.micropress-inc.com/">http://www.micropress-inc.com/</a>
+  </blockquote><p>
+  Source: Mail from MicroPress, Inc., July 1999
+<dt>PC; Scientific Word<dd> Scientific Word and Scientific Workplace
+  offer a mechanism for near-WYSIWYG input of LaTeX documents; they
+  ship with TrueTeX from Kinch (see above).  Queries within the UK
+  and Ireland should be addressed to Scientific Word Ltd., others should be
+  addressed directly to the publisher, MacKichan Software Inc.
+  <blockquote>
+    Dr Christopher Mabb<br>
+    Scientific Word Ltd.<br>
+    990 Anlaby Road,<br>
+    Hull,<br>
+    East Yorkshire,<br>
+    HU4 6AT<br>
+    UK<br>
+    Tel: 0845 766 0340 (within the UK) <br>
+    Fax: 0845 603 9443 (within the UK) <br>
+    Email: <a href="mailto:christopher@sciword.demon.co.uk"><i>christopher@sciword.demon.co.uk</i></a> <br>
+    Web: <a href="http://www.sciword.demon.co.uk">http://www.sciword.demon.co.uk</a>
+  </blockquote><p>
+  <blockquote>
+    MacKichan Software Inc.<br>
+    19307 8th Avenue, Suite C<br>
+    Poulsbo WA 98370-7370<br>
+    USA<br>
+    Tel: +1 360 394 6033<br>
+    Tel: 877 724 9673 (within the USA)
+    Fax: +1  360 394 6039<br>
+    Email: <a href="mailto:info@mackichan.com"><i>info@mackichan.com</i></a><br>
+    Web: <a href="http://www.mackichan.com">http://www.mackichan.com</a>
+  </blockquote><p>
+  Source: Mail from Christopher Mabb, August 2007
+<dt>Macintosh; Textures<dd> &ldquo;A TeX system &lsquo;for the rest of
+  us&rsquo; &rdquo;.  A beta release of Textures for MacOS/X is
+  available <a href="http://www.bluesky.com/news/220b.html">http://www.bluesky.com/news/220b.html</a>
+<p/>  (Blue Sky also gives away a Metafont implementation and some
+  font manipulation tools for Macs.)
+  <blockquote>
+    Blue Sky Research<br>
+    PO Box 80424<br>
+    Portland, OR 97280<br>
+    USA<br>
+    Tel: 800-622-8398 (within the USA)<br>
+    Tel/Fax: +1 503-222-9571<br>
+    Fax: +1 503-246-4574<br>
+    Email: <a href="mailto:sales@bluesky.com"><i>sales@bluesky.com</i></a><br>
+    Web: <a href="http://www.bluesky.com/">http://www.bluesky.com/</a>
+  </blockquote><p>
+  Source: Mail from Gordon Lee, April 2007
+<dt>AmigaTeX<dd> A full implementation for the Commodore Amiga,
+  including full, on-screen and printing support for all PostScript
+  graphics and fonts, IFF raster graphics, automatic font generation,
+  and all of the standard macros and utilities.
+  <blockquote>
+    Radical Eye Software<br>
+    PO Box 2081<br>
+    Stanford, CA 94309<br>
+    USA
+  </blockquote><p>
+  Source: Mail from Tom Rokicki, November 1994
+</dl>
+
+
+<p/>Note that the company Y&amp;Y has gone out of business, and Y&amp;Y
+TeX (and support for it) is therefore no longer available.  Users
+of Y&amp;Y systems may care to use the self-help
+<a href="http://tug.org/pipermail/yandytex/">mailing list</a>
+that was established in 2003; the remaining usable content of
+Y&amp;Y&rsquo;s web site is available at <a href="http://www.tug.org/yandy/">http://www.tug.org/yandy/</a>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html
new file mode 100644
index 00000000000..8675cc55670
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label compactbib</title>
+</head><body>
+<h3>Reducing spacing in the bibliography</h3>
+<p/>Bibliographies are, in fact, implemented as lists, so all the
+confusion about <a href="FAQ-complist.html">reducing list item spacing</a> also
+applies to bibliographies.
+<p/>If the <i>natbib</i> package &lsquo;works&rsquo; for you (it may not if you are using
+some special-purpose bibliography style), the solution is relatively
+simple &mdash; add
+<blockquote>
+<pre>
+\usepackage{natbib}
+\setlength{\bibsep}{0.0pt}
+</pre>
+</blockquote><p>
+to the preamble of your document.
+<p/>Otherwise, one is into unseemly hacking of something or other.  The
+<i>mdwlist</i> package actually does the job, but it doesn&rsquo;t work
+here, because it makes a different-named list, while the name
+&ldquo;<code>thebibliography</code>&rdquo; is built into LaTeX and
+BibTeX.  Therefore, we need to 
+<a href="FAQ-patch.html">patch the underlying macro</a>:
+<blockquote>
+<pre>
+\let\oldbibliography\thebibliography
+\renewcommand{\thebibliography}[1]{%
+  \oldbibliography{#1}%
+  \setlength{\itemsep}{0pt}%
+}
+</pre>
+</blockquote><p>
+The <i>savetrees</i> 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
+<em>only</em>.
+<dl>
+<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+<dt><tt><i>natbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+<dt><tt><i>savetrees.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html
new file mode 100644
index 00000000000..616e7d9ecc0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html
@@ -0,0 +1,40 @@
+<head>
+<title>UK TeX FAQ -- question label compjobnam</title>
+</head><body>
+<h3>Comparing the &ldquo;job name&rdquo;</h3>
+<p/>The token <code>\</code><code>jobname</code> amusingly produces a sequence of characters
+whose category code is 12 (&lsquo;other&rsquo;), regardless of what the characters
+actually are.  Since one inevitably has to compare a macro with the
+contents of another macro (using <code>\</code><code>ifx</code>, somewhere) one needs to
+create a macro whose expansion looks the same as the expansion of
+<code>\</code><code>jobname</code>.  We find we can do this with <code>\</code><code>meaning</code>, if we strip
+the &ldquo;<code>\</code><code>show</code> command&rdquo; prefix.
+<p/>The full command looks like:
+<blockquote>
+<pre>
+\def\StripPrefix#1&gt;{}
+\def\jobis#1{FF\fi
+  \def\predicate{#1}%
+  \edef\predicate{\expandafter\StripPrefix\meaning\predicate}%
+  \edef\job{\jobname}%
+  \ifx\job\predicate
+}
+</pre>
+
+</blockquote><p>
+And it&rsquo;s used as:
+<blockquote>
+<pre>
+\if\jobis{mainfile}%
+  \message{YES}%
+\else
+  \message{NO}%
+\fi
+</pre>
+</blockquote><p>
+Note that the command <code>\</code><code>StripPrefix</code> need not be defined if you&rsquo;re
+using LaTeX &mdash; there&rsquo;s already an 
+<a href="FAQ-atsigns.html">internal command</a> <code>\</code><code>strip@prefix</code> that you can
+use.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html
new file mode 100644
index 00000000000..81365892835
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html
@@ -0,0 +1,111 @@
+<head>
+<title>UK TeX FAQ -- question label complist</title>
+</head><body>
+<h3>How to adjust list spacing</h3>
+<p/><a href="FAQ-books.html">Lamport&rsquo;s book</a> lists various
+parameters for the layout of list (things like <code>\</code><code>topsep</code>,
+<code>\</code><code>itemsep</code> and <code>\</code><code>parsep</code>), but fails to mention that they&rsquo;re set
+automatically within the list itself.  This happens because each list
+executes a command <code>\</code><code>@list</code><code>&lt;<i>depth</i>&gt;</code> (the depth
+appearing as a lower-case roman numeral); what&rsquo;s more, the top-level
+<code>\</code><code>@listi</code> is usually reset when the font size is changed.  As a
+result, it&rsquo;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 <i>memoir</i> class wasn&rsquo;t
+designed for more compact lists <em>per se</em>, but offers the user
+control over the list spacing.
+<p/>There are packages that provide some control of list spacing, but they
+seldom address the separation from surrounding text (defined by
+<code>\</code><code>topsep</code>).  The <i>expdlist</i> package, among its many controls
+of the appearance of <code>description</code> lists, offers a
+compaction parameter (see the documentation); the <i>mdwlist</i>
+package offers a <code>\</code><code>makecompactlist</code> command for users&rsquo; own list
+definitions, and uses it to define compact lists
+<code>itemize*</code>, <code>enumerate*</code> and
+<code>description*</code>.  In fact, you can write lists such as
+these commands define pretty straightforwardly &mdash; for example:
+<blockquote>
+<pre>
+\newenvironment{itemize*}%
+  {\begin{itemize}%
+    \setlength{\itemsep}{0pt}%
+    \setlength{\parskip}{0pt}}%
+  {\end{itemize}}
+</pre>
+</blockquote><p>
+The <i>paralist</i> package provides several approaches to list
+compaction:
+<ul>
+<li> its <code>asparaenum</code> environment formats each item as if
+  it were a paragraph introduced by the enumeration label (which saves
+  space if the item texts are long);
+<li> its <code>compactenum</code> environment is the same sort of
+  compact list as is provided in <i>expdlist</i> and
+  <i>mdwlist</i>; and
+<li> its <code>inparaenum</code> environment produces a list &ldquo;in
+  the paragraph&rdquo;, i.e., with no line break between items, which is a
+  great space-saver if the list item texts are short.
+</ul>
+The package will manipulate its <code>enumerate</code> environment
+labels just like the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a>
+does.
+<p/><i>Paralist</i> also provides <code>itemize</code> equivalents
+(<code>asparaitem</code>, etc.), and <code>description</code>
+equivalents (<code>asparadesc</code>, etc.).
+<p/>The <i>multenum</i> package offers a more regular form of
+<i>paralist</i>&rsquo;s <code>inparaenum</code>; 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 &lsquo;tab&rsquo; keys on traditional typewriters; the package was designed
+for example sheets, or lists of answers in the appendices of a book.
+<p/>The ultimate in compaction (of every sort) is offered by the
+<i>savetrees</i> package; compaction of lists is included.  The
+package&rsquo;s prime purpose is to save space at every touch and turn:
+don&rsquo;t use it if you&rsquo;re under any design constraint whatever!
+<p/>The <i>expdlist</i>, <i>mdwlist</i> and <i>paralist</i>
+packages all offer other facilities for list configuration: you should
+probably not try the &ldquo;do-it-yourself&rdquo; approaches outlined below if
+you need one of the packages for some other list configuration
+purpose.
+<p/>For ultimate flexibility (including manipulation of <code>\</code><code>topsep</code>), the
+<i>enumitem</i> package permits adjustment of list parameters using
+a &ldquo;<em>key</em>=&lt;<i>value</i>&gt;&rdquo; format.
+For example, one might write
+<blockquote>
+<pre>
+\usepackage{enumitem}
+...
+\begin{enumerate}[topsep=0pt, partopsep=0pt]
+\item ...
+\item ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+to suppress all spacing above and below your list, or
+<blockquote>
+<pre>
+\usepackage{enumitem}
+...
+\begin{enumerate}[itemsep=2pt,parsep=2pt]
+\item ...
+\item ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+to set spacing between items and between paragraphs within items.
+<i>Enumitem</i> also permits manipulation of the label format in a
+more &ldquo;basic&rdquo; (and therefore more flexible) manner than the 
+<a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does.
+<dl>
+<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>)
+<dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+<dt><tt><i>multenum.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multenum.zip">macros/latex/contrib/multenum</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multenum.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multenum/">browse</a>)
+<dt><tt><i>paralist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse</a>)
+<dt><tt><i>savetrees.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html
new file mode 100644
index 00000000000..388fc0299e8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label concrete</title>
+</head><body>
+<h3>Using the &ldquo;Concrete&rdquo; fonts</h3>
+<p/>The Concrete Roman fonts were designed by Don Knuth for a book called
+&ldquo;Concrete Mathematics&rdquo;, which he wrote with Graham and Patashnik
+(<em>the</em> Patashnik, of BibTeX fame).  Knuth
+only designed text fonts, since the book used the Euler fonts for
+mathematics.  The book was typeset using Plain TeX, of course, with
+additional macros that may be viewed in a file <i>gkpmac.tex</i>,
+which is available on CTAN.
+<p/>The packages <i>beton</i>, <i>concmath</i>, and
+<i>ccfonts</i> are LaTeX packages that change the default text
+fonts from Computer Modern to Concrete.  Packages <i>beton</i> and
+<i>ccfonts</i> also slightly increase the default value of
+<code>\</code><code>baselineskip</code> to account for the rather heavier weight of the
+Concrete fonts.  If you wish to use the <i>Euler</i> fonts for
+mathematics, as Knuth did, there&rsquo;s the <i>euler</i> package which
+has been developed from Knuth&rsquo;s own Plain TeX-based set: these
+macros are currently deprecated (they clash with many things, including
+AMSLaTeX).  The independently-developed <i>eulervm</i>
+bundle is therefore preferred to the <i>euler</i> package.  (Note
+that installing the <i>eulervm</i> 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 <i>readme</i> in the
+<i>eulervm</i> distribution.)
+<p/>A few years after Knuth&rsquo;s original design, Ulrik Vieth
+designed the Concrete Math fonts.  Packages
+<i>concmath</i>, and <i>ccfonts</i> also change the default math
+fonts from Computer Modern to Concrete and use the Concrete versions
+of the AMS fonts (this last behaviour is optional in the case
+of the <i>concmath</i> package).
+<p/>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 <i>concmath</i> or
+<i>ccfonts</i> and you want to follow this suggestion, then use the
+package with <code>boldsans</code> class option (in spite of the fact
+that the <i>concmath</i> documentation calls it
+<code>sansbold</code> class option). If you are using <i>beton</i>,
+add
+<blockquote>
+  <code>\</code><code>renewcommand{<code>\</code><code>bfdefault</code>}{sbc}</code>
+</blockquote><p>
+to the preamble of your document.
+<p/>Type 1 versions of the fonts are available.  For OT1 encoding,
+they are available from <a href="FAQ-psfchoice.html">MicroPress</a>.  The
+<a href="FAQ-textrace.html">CM-Super fonts</a> contain Type 1 versions
+of the Concrete fonts in T1 encoding.
+<dl>
+<dt><tt><i>beton.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beton.zip">macros/latex/contrib/beton</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beton.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/beton/">browse</a>)
+<dt><tt><i>ccfonts.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccfonts.zip">macros/latex/contrib/ccfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccfonts/">browse</a>)
+<dt><tt><i>CM-Super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>)
+<dt><tt><i>concmath.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/concmath.zip">macros/latex/contrib/concmath</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/concmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/concmath/">browse</a>)
+<dt><tt><i>Concmath fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/concmath.zip">fonts/concmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/concmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/concmath/">browse</a>)
+<dt><tt><i>Concrete fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/concrete.zip">fonts/concrete</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/concrete.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/concrete/">browse</a>)
+<dt><tt><i>euler.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/euler.zip">macros/latex/contrib/euler</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/euler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/euler/">browse</a>)
+<dt><tt><i>eulervm bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.zip">fonts/eulervm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/eulervm/">browse</a>)
+<dt><tt><i>gkpmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/local/lib/gkpmac.tex">systems/knuth/local/lib/gkpmac.tex</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html
new file mode 100644
index 00000000000..cba1c195363
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html
@@ -0,0 +1,169 @@
+<head>
+<title>UK TeX FAQ -- question label conditional</title>
+</head><body>
+<h3>Conditional compilation and &ldquo;comments&rdquo;</h3>
+<p/>While LaTeX (or any other TeX-derived package) isn&rsquo;t really like a
+compiler, people regularly want to do compiler-like things using it.
+Common requirements are conditional &lsquo;compilation&rsquo; and &lsquo;block
+comments&rsquo;, and several LaTeX-specific means to this end are available.
+<p/>The simple <code>\</code><code>newcommand{<code>\</code><code>gobble</code>}[1]</code><code>{</code><code>}</code> 
+and <code>\</code><code>iffalse</code><code> ... </code><code>\</code><code>fi</code> aren&rsquo;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&rsquo;re allowed to skip; this may
+not be a problem in <em>today&rsquo;s</em> 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):
+<blockquote>
+<pre>
+\iffalse % ignoring this bit
+consider what happens if we
+use \verb+\iftrue+ -- a surprise
+\fi
+</pre>
+</blockquote><p>
+The <code>\</code><code>iftrue</code> is spotted by TeX as it scans, ignoring the
+<code>\</code><code>verb</code> command; so the <code>\</code><code>iffalse</code> isn&rsquo;t terminated by the
+following <code>\</code><code>fi</code>.  Also, <code>\</code><code>gobble</code> is pretty inefficient at
+consuming anything non-trivial, since all the matter to be skipped is
+copied to the argument stack before being ignored.
+<p/>If your requirement is for a document from which whole chapters (or
+the like) are missing, consider the LaTeX
+<code>\</code><code>include</code>/<code>\</code><code>includeonly</code> system.  If you &lsquo;<code>\</code><code>include</code>&rsquo; your
+files (rather than <code>\</code><code>input</code> them &mdash; see 
+<a href="FAQ-include.html">What&rsquo;s going on in my <code>\</code><code>include</code> commands?</a>),
+LaTeX writes macro traces of what&rsquo;s going on at the end of each
+chapter to the <code>.aux</code> file; by using <code>\</code><code>includeonly</code>, you can give
+LaTeX an exhaustive list of the files that are needed.  Files that
+don&rsquo;t get <code>\</code><code>include</code>d are skipped entirely, but the document
+processing continues as if they <em>were</em> there, and page, footnote,
+and other numbers are not disturbed.  Note that you can choose which
+sections you want included interactively, using the
+<i>askinclude</i> package.
+<p/>The inverse can be done using the <i>excludeonly</i> package: this
+allows you to exclude a (list of) <code>\</code><code>include</code>d files from your
+document, by means of an <code>\</code><code>excludeonly</code> command.
+<p/>If you want to select particular pages of your document, use Heiko
+Oberdiek&rsquo;s <i>pagesel</i> or the <i>selectp</i> packages.  You
+can do something similar with an existing PDF document (which
+you may have compiled using <i>pdflatex</i> in the first place),
+using the <i>pdfpages</i> package.  The job is then done with a
+document looking like:
+<blockquote>
+<pre>
+\documentclass{article}
+\usepackage[final]{pdfpages}
+\begin{document}
+\includepdf[pages=30-40]{yoursource.pdf}
+\end{document}
+</pre>
+</blockquote><p>
+(To include all of the document, you write
+<blockquote>
+<pre>
+\includepdf[pages=-]{yoursource.pdf}
+</pre>
+</blockquote><p>
+omitting the start and end pages in the optional argument.)
+<p/>If you want flexible facilities for including or excluding small
+portions of a file, consider the <i>comment</i>, <i>version</i> or
+<i>optional</i> packages.
+<p/>The <i>comment</i> 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 <code>\</code><code>includecomment{</code><em>version-name</em><code>}</code>
+declares an environment <code>version-name</code> whose content will
+be included in your document, while
+<code>\</code><code>excludecomment{</code><em>version-name</em><code>}</code> 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 <code>\</code><code>if</code> commands).
+<p/>These FAQs employ the <i>comment</i> package to alter layout
+between the printed (two-column) version and the PDF version
+for browsing; there are <code>narrowversion</code> and
+<code>wideversion</code> for the two versions of the file.
+<p/><i>version</i> offers similar facilities to <i>comment.sty</i>
+(i.e., <code>\</code><code>includeversion</code> and <code>\</code><code>excludeversion</code> commands);
+it&rsquo;s far &ldquo;lighter weight&rdquo;, but is less robust (and in particular,
+cannot deal with very large areas of text being included/excluded).
+<p/>A significant development of <i>version</i>, confusingly called
+<i>versions</i> (i.e., merely a plural of the old package name).
+<i>Versions</i> adds a command
+<code>\</code><code>markversion{</code><em>version-name</em><code>}</code> which defines an environment
+that prints the included text, with a clear printed mark around it.
+<p/><i>optional</i> defines a command <code>\</code><code>opt</code>; its first argument is
+an &lsquo;inclusion flag&rsquo;, 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 &mdash; if a large body of
+text is needed, <code>\</code><code>input</code> 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.
+<p/>And, not least of this style of conditional compilation,
+<i>verbatim</i> (which should be available in any distribution)
+defines a <code>comment</code> environment, which enables the
+dedicated user of the source text editor to suppress bits of a
+LaTeX source file.  The <i>memoir</i> class offers the same
+environment.
+<p/>An interesting variation is the <i>xcomment</i> package.  This
+defines an environment whose body is all excluded, apart from
+environments named in its argument.  So, for example:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+<p/>A further valuable twist is offered by the <i>extract</i> package.
+This allows you to produce a &ldquo;partial copy&rdquo; of an existing document:
+the package was developed to permit production of a &ldquo;book of
+examples&rdquo; from a set of lecture notes.  The package documentation
+shows the following usage:
+<blockquote>
+<pre>
+\usepackage[
+  active,
+  generate=foobar,
+  extract-env={figure,table},
+  extract-cmd={chapter,section}
+]{extract}
+</pre>
+</blockquote><p>
+which will cause the package to produce a file <i>foobar.tex</i>
+containing all the <code>figure</code> and <code>table</code>
+environments, and the <code>\</code><code>chapter</code> and <code>\</code><code>section</code> commands, from
+the document being processed.  The new file <i>foobar.tex</i> is
+generated in the course of an otherwise ordinary run on the &lsquo;master&rsquo;
+document.  The package provides a good number of other facilities,
+including (numeric or labelled) ranges of environments to extract, and
+an <code>extract</code> environment which you can use to create complete
+ready-to-run LaTeX documents with stuff you&rsquo;ve extracted.
+<dl>
+<dt><tt><i>askinclude.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages &mdash;
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+<dt><tt><i>comment.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.zip">macros/latex/contrib/comment</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/comment/">browse</a>)
+<dt><tt><i>excludeonly.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/excludeonly.sty">macros/latex/contrib/misc/excludeonly.sty</a>
+<dt><tt><i>extract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.zip">macros/latex/contrib/extract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extract/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>optional.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/optional.sty">macros/latex/contrib/misc/optional.sty</a>
+<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages &mdash;
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+<dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>)
+<dt><tt><i>selectp.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/selectp.sty">macros/latex/contrib/misc/selectp.sty</a>
+<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>version.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/version.sty">macros/latex/contrib/misc/version.sty</a>
+<dt><tt><i>versions.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/versions/versions.sty">macros/latex/contrib/versions/versions.sty</a>
+<dt><tt><i>xcomment.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html
new file mode 100644
index 00000000000..c3f57b68c60
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label context</title>
+</head><body>
+<h3>What is ConTeXt?</h3>
+<p/><a href="http://www.pragma-ade.com/">ConTeXt</a> is a macro package
+developed by Hans Hagen of Pragma-Ade.  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&rsquo;s unified design avoids the package clashes that
+can happen with LaTeX.
+<p/>ConTeXt also integrates MetaFun, a superset of MetaPost 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.
+<p/>ConTeXt allows the users to specify formatting commands in English,
+Dutch, German, French, or Italian, and to use different typesetting
+engines (PDFTeX, XeTeX, Aleph, and soon LuaTeX) without
+changing the user interface. ConTeXt is developed rapidly, often in
+response to requests from the user community.
+<p/>
+
+
+
+
+
+
+
+
+
+
+
+
+
+<p/>ConTeXt doesn&rsquo;t yet have quite such a large developer community as
+does LaTeX, but those developers who are active seem to have
+prodigious energy.  Support is available via a 
+<a href="http://contextgarden.net">WIKI site</a> and via the
+<a href="http://www.ntg.nl/mailman/listinfo/ntg-context">mailing list</a>.
+<dl>
+<dt><tt><i>ConTeXt distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/context.zip">macros/context</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/context.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/context/">browse</a>)
+</dl>
+<p/>
+<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=context">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=context</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html
new file mode 100644
index 00000000000..2c86ecce729
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label crop</title>
+</head><body>
+<h3>How to create crop marks</h3>
+<p/>If you&rsquo;re printing something that&rsquo;s eventually to be reproduced in
+significant quantities, and bound, it&rsquo;s conventional to print on paper
+larger than your target product, and to place &ldquo;crop marks&rdquo; outside
+the printed area.  These crop marks are available to the production
+house, for lining up reproduction and trimming machines.
+<p/>You can save yourself the (considerable) trouble of programming these
+marks for yourself by using the package <i>crop</i>, which has
+facilities to satisfy any conceivable production house.  Users of the
+<i>memoir</i> class don&rsquo;t need the package, since <i>memoir</i> has
+its own facilities for programming crop marks.
+<dl>
+<dt><tt><i>crop.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.zip">macros/latex/contrib/crop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/crop/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crossref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crossref.html
new file mode 100644
index 00000000000..c4b0763ff22
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crossref.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label crossref</title>
+</head><body>
+<h3>LaTeX gets cross-references wrong</h3>
+<p/>Sometimes, however many times you run LaTeX, the cross-references
+are just wrong. Remember that
+the <code>\</code><code>label</code> command must come <em>after</em> the <code>\</code><code>caption</code> command, or
+be part of it. For example,
+
+<pre>
+  \begin{figure}          \begin{figure}
+  \caption{A Figure}  or  \caption{A Figure%
+  \label{fig}                   \label{fig}}
+  \end{figure}            \end{figure}
+</pre>
+<p/>You can, just as effectively, shield the <code>\</code><code>caption</code> command from its
+associated <code>\</code><code>label</code> command, by enclosing the caption in an
+environment of its own.  For example, people commonly seek help after:
+<blockquote>
+<pre>
+\begin{center}
+  \caption{A Figure}
+\end{center}
+\label{fig}
+</pre>
+</blockquote><p>
+has failed to label correctly.  If you really need this centring (and
+those in the know commonly reject it), code it as:
+<blockquote>
+<pre>
+\begin{center}
+  \caption{A Figure}
+  \label{fig}
+\end{center}
+</pre>
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html
new file mode 100644
index 00000000000..d2abced359a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label csname</title>
+</head><body>
+<h3>Defining a macro from an argument</h3>
+<p/>It&rsquo;s common to want a command to create another command: often one
+wants the new command&rsquo;s name to derive from an argument.  LaTeX
+does this all the time: for example, <code>\</code><code>newenvironment</code> creates
+start- and end-environment commands whose names are derived from the
+name of the environment command.
+<p/>The (seemingly) obvious approach:
+<blockquote>
+<pre>
+\def\relay#1#2{\def\#1{#2}}
+</pre>
+</blockquote><p>
+doesn&rsquo;t work (the TeX engine interprets it
+as a rather strange redefinition of <code>#</code>).  The trick is to use
+<code>\</code><code>csname</code>, which is a TeX primitive for generating command names
+from random text, together with <code>\</code><code>expandafter</code>.  The definition
+above should read:
+<blockquote>
+<pre>
+\def\relay#1#2{%
+  \expandafter\def\csname #1\endcsname{#2}%
+}
+</pre>
+</blockquote><p>
+With this definition, <code>\</code><code>relay{blah}{bleah}</code> is equivalent to
+<code>\</code><code>def</code><code>\</code><code>blah{bleah}</code>.
+<p/>Note that the definition of <code>\</code><code>relay</code> omits the braces round the
+&lsquo;command name&rsquo; in the <code>\</code><code>newcommand</code> it executes.  This is
+because they&rsquo;re not necessary (in fact they seldom are), and in this
+circumstance they make the macro code slightly more tedious.
+<p/>The name created need not (of course) be <em>just</em> the argument:
+<blockquote>
+
+<pre>
+\def\newrace#1#2#3{%
+  \expandafter\def\csname start#1\endcsname{%
+    #2%
+  }%
+  \expandafter\def\csname finish#1\endcsname{%
+    #3%
+  }%
+}
+</pre>
+</blockquote><p>
+With commands
+<blockquote>
+<pre>
+\def\start#1{\csname start#1\endcsname}
+\def\finish#1{\csname finish#1\endcsname}
+</pre>
+</blockquote><p>
+these &lsquo;races&rsquo; could behave a bit like LaTeX environments.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html
new file mode 100644
index 00000000000..69209eed9eb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label custbib</title>
+</head><body>
+<h3>Creating a bibliography style</h3>
+<p/>It <em>is</em> possible to write your own: the standard bibliography
+styles are distributed in a commented form, and there is a description
+of the language (see
+
+<a href="FAQ-BibTeXing.html">BibTeX documentation</a>).
+However, it must be admitted that the language in which BibTeX
+styles are written is pretty obscure, and one would not recommend
+anyone who&rsquo;s not a confident programmer to write their own, though
+minor changes to an existing style may be within the grasp of many.
+<p/>If your style isn&rsquo;t too &lsquo;far out&rsquo;, you can probably generate it by
+using the facilities of the <i>custom-bib</i> bundle.  This
+contains a file <i>makebst.tex</i>, which runs you through a text menu
+to produce a file of instructions, with which you can generate your
+own <code>.bst</code> file.  This technique doesn&rsquo;t offer entirely new styles
+of document, but the system&rsquo;s &ldquo;master BibTeX styles&rdquo; already
+offer significantly more than the BibTeX standard set.
+<dl>
+<dt><tt><i>BibTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>)
+<dt><tt><i>makebst.tex</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html
new file mode 100644
index 00000000000..caa9ad674ba
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label cv</title>
+</head><body>
+<h3><em>Curriculum Vitae</em> (R&eacute;sum&eacute;)</h3>
+<p/>Andrej Brodnik&rsquo;s class, <i>vita</i>, offers a framework for producing
+a <em>curriculum vitae</em>.  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.
+<p/>Didier Verna&rsquo;s class, <i>curve</i>, is based on a model in which
+the CV is made of a set of <em>rubrics</em> (each one dealing
+with a major item that you want to discuss, such as &lsquo;education&rsquo;, &lsquo;work
+experience&rsquo;, etc).  The class&rsquo;s documentation is supported by a couple
+of example files, and an emacs mode is provided.
+<p/>Xavier Danaux offers a class <i>moderncv</i> which supports
+typesetting modern <em>curricula vitarum</em>, 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.
+<p/>The European Commission has recommended a format for 
+<em>curricula vitarum</em> within Europe, and Nicola Vitacolonna has
+developed a class <i>europecv</i> to produce it.  While (by his own
+admission) the class doesn&rsquo;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).
+<p/>The alternative to using a separate class is to impose a package on
+one of the standard classes.  An example,
+Axel Reichert&rsquo;s <i>currvita</i> package, has been recommended to the
+FAQ team.  Its output certainly looks good.
+<p/>There is also a LaTeX 2.09 package <i>resume</i>, which comes with
+little but advice <em>against</em> trying to use it.
+<dl>
+<dt><tt><i>currvita.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.zip">macros/latex/contrib/currvita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/currvita/">browse</a>)
+<dt><tt><i>curve.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/curve.zip">macros/latex/contrib/curve</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/curve.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/curve/">browse</a>)
+<dt><tt><i>europecv.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/europecv.zip">macros/latex/contrib/europecv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/europecv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/europecv/">browse</a>)
+<dt><tt><i>moderncv.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moderncv.zip">macros/latex/contrib/moderncv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moderncv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moderncv/">browse</a>)
+<dt><tt><i>resume.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/macros/latex209/contrib/resume/resume.sty">obsolete/macros/latex209/contrib/resume/resume.sty</a>
+<dt><tt><i>vita.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.zip">macros/latex/contrib/vita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vita/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
new file mode 100644
index 00000000000..cdaf84cfbbf
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
@@ -0,0 +1,77 @@
+<head>
+<title>UK TeX FAQ -- question label cvtlatex</title>
+</head><body>
+<h3>Transcribing LaTeX command definitions</h3>
+<p/>At several places in this FAQ, questions are answered in terms
+of how to program a LaTeX macro.  Sometimes, these macros might
+also help users of Plain TeX or other packages; this answer
+attempts to provide a rough-and-ready guide to transcribing such macro
+definitions for use in other packages.
+<p/>The reason LaTeX has commands that replace <code>\</code><code>def</code>, is that
+there&rsquo;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 (<code>\</code><code>renewcommand</code>) or not
+(<code>\</code><code>newcommand</code>), and if its status proves not as the user expected,
+an error is reported.  A third definition command,
+<code>\</code><code>providecommand</code>, only defines if the target is not already
+defined; LaTeX has no direct equivalent of <code>\</code><code>def</code>, which ignores
+the present state of the command.  The final command of this sort is
+<code>\</code><code>DeclareRobustCommand</code>, which creates a command which is &ldquo;robust&rdquo;
+(i.e., will not expand if subjected to LaTeX &ldquo;protected
+expansion&rdquo;); from the Plain TeX user&rsquo;s point of view,
+<code>\</code><code>DeclareRobustCommand</code> should be treated as a non-checking version
+of <code>\</code><code>newcommand</code>.
+<p/>LaTeX commands are, by default, defined <code>\</code><code>long</code>; an optional <code>*</code>
+between the <code>\</code><code>newcommand</code> and its (other) arguments specifies that
+the command is <em>not</em> to be defined <code>\</code><code>long</code>.  The <code>*</code> is
+detected by a command <code>\</code><code>@ifstar</code> which uses <code>\</code><code>futurelet</code> to switch
+between two branches, and gobbles the <code>*</code>: LaTeX users are
+encouraged to think of the <code>*</code> as part of the command name.
+<p/>LaTeX&rsquo;s checks for unknown command are done by <code>\</code><code>ifx</code> comparison
+of a <code>\</code><code>csname</code> construction with <code>\</code><code>relax</code>; since the command name
+argument is the desired control sequence name, this proves a little
+long-winded.  Since <code>#1</code> is the requisite argument, we have:
+<blockquote>
+
+<pre>
+\expandafter\ifx
+  \csname\expandafter\@gobble\string#1\endcsname
+  \relax
+    ...
+</pre>
+</blockquote><p>
+(<code>\</code><code>@gobble</code> simply throws away its argument).
+<p/>The arguments of a LaTeX command are specified by two optional
+arguments to the defining command: a count of arguments (0&ndash;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&rsquo;s first argument
+is to be optional.  So:
+<blockquote>
+<pre>
+\newcommand\foo{...}
+\newcommand\foo[0]{...}
+\newcommand\foo[1]{...#1...}
+\newcommand\foo[2][boo]{...#1...#2...}
+</pre>
+</blockquote><p>
+In the last case, <code>\</code><code>foo</code> may be called as <code>\</code><code>foo{goodbye}</code>,
+which is equivalent to <code>\</code><code>foo[boo]{goodbye}</code> (employing the
+default value given for the first argument), or as
+<code>\</code><code>foo[hello]{goodbye}</code> (with an explicit first argument).
+<p/>Coding of commands with optional arguments is exemplified by the
+coding of the last <code>\</code><code>foo</code> above:
+<blockquote>
+<pre>
+\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...}
+</pre>
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html
new file mode 100644
index 00000000000..8c4bc8f9ae9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label dec_comma</title>
+</head><body>
+<h3>The comma as a decimal separator</h3>
+<p/>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.
+<p/>A simple solution to this problem, in maths mode, is to type
+<code>3</code><code>{,}</code><code>14</code> in place of <code>3,14</code>.  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.
+<p/>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: <i>icomma</i> and <i>ziffer</i>.
+<p/><i>Icomma</i> ensures that there will be no extra space after a
+comma, unless you type a space after it (as in <code>f(x, y)</code> &mdash; in
+the absence of the package, you don&rsquo;t need that space), in which case
+the usual small space after the comma appears.  <i>Ziffer</i> 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 &lsquo;cents&rsquo; part of an
+amount of currency.
+<p/>The <i>numprint</i> package provides a command
+<code>\</code><code>numprint{</code><em>number</em><code>}</code> that prints its argument according to
+settings you give it, or according to settings chosen to match the
+language you have selected in <i>babel</i>.  The formatting works
+equally well in text or maths.  The command is very flexible (it can also
+group the digits of very &lsquo;long&rsquo; numbers), but is inevitably less
+convenient than <i>icomma</i> or <i>ziffer</i> if you are typing a
+lot of numbers.
+<dl>
+<dt><tt><i>icomma.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.zip">macros/latex/contrib/was</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was/">browse</a>)
+<dt><tt><i>numprint.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numprint.zip">macros/latex/contrib/numprint</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numprint.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/numprint/">browse</a>)
+<dt><tt><i>ziffer.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ziffer.zip">macros/latex/contrib/ziffer</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ziffer.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ziffer/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html
new file mode 100644
index 00000000000..53ed96568b7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html
@@ -0,0 +1,83 @@
+<head>
+<title>UK TeX FAQ -- question label destable</title>
+</head><body>
+<h3>The design of tables</h3>
+<p/>In recent years, several authors have argued that the examples, set
+out by Lamport in his <a href="FAQ-books.html">LaTeX manual</a>, have cramped
+authors&rsquo; 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&rsquo;s
+book &ldquo;mean&rdquo;.
+<p/>The criticism focuses on the excessive use of rules (both horizontal
+and vertical) and on the poor vertical spacing that Lamport&rsquo;s macros
+offer.
+<p/>The problem of vertical spacing is plain for all to see, and is
+addressed in several packages &mdash; see 
+&ldquo;<a href="FAQ-struttab.html">spacing of lines in tables</a>&rdquo;.
+<p/>The argument about rules is presented in the excellent essay that
+prefaces the documentation of Simon Fear&rsquo;s <i>booktabs</i> package,
+which (of course) implements Fear&rsquo;s scheme for &lsquo;comfortable&rsquo; rules.
+(The same rule commands are implemented in the <i>memoir</i> class.)
+<p/>Lamport&rsquo;s LaTeX was also inflexibly wrong in &ldquo;insisting&rdquo; 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 <code>\</code><code>caption</code> command will get its
+position wrong (by <code>10pt</code>) if you simply write:
+<blockquote>
+<pre>
+\begin{table}
+  \caption{Example table}
+  \begin{tabular}{...}
+    ...
+  \end{tabular}
+\end{table}
+</pre>
+</blockquote><p>
+The <i>topcapt</i> package solves this problem:
+<blockquote>
+<pre>
+\usepackage{topcaption}
+...
+\begin{table}
+  \topcaption{Example table}
+  \begin{tabular}{...}
+    ...
+  \end{tabular}
+\end{table}
+</pre>
+</blockquote><p>
+The <i>KOMA-script</i> classes provide a similar command
+<code>\</code><code>captionabove</code>; they also have a class option
+<code>tablecaptionabove</code> which arranges that <code>\</code><code>caption</code>
+<em>means</em> <code>\</code><code>captionabove</code>, in table environments.  The
+<i>caption</i> (from the release of 23 January, 2004) may be loaded
+with an option that has the same effect:
+<blockquote>
+<pre>
+\usepackage[tableposition=top]{caption}
+</pre>
+</blockquote><p>
+<p/>Doing the job yourself is pretty easy: <i>topcapt</i> switches the
+values of the LaTeX2e parameters <code>\</code><code>abovecaptionskip</code> (default
+value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (default value
+<code>0pt</code>), so:
+<blockquote>
+<pre>
+\begin{table}
+  \setlength{\abovecaptionskip}{0pt}
+  \setlength{\belowcaptionskip}{10pt}
+  \caption{Example table}
+  \begin{tabular}{...}
+    ...
+  \end{tabular}
+\end{table}
+</pre>
+</blockquote><p>
+does the job.  (The package itself is very slightly more elaborate...)
+<dl>
+<dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>topcapt.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/topcapt.sty">macros/latex/contrib/misc/topcapt.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html
new file mode 100644
index 00000000000..c5f3d90571e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label distill-prob</title>
+</head><body>
+<h3>Characters missing from PDF output</h3>
+<p/>If you&rsquo;re using <i>Acrobat</i> <i>Distiller</i> to create your
+PDF output, you may find
+characters missing.  This may manifest
+itself as messed-up maths equations (missing
+&ldquo;-&rdquo; signs, for example), or bits missing
+from large symbols.  Early versions of <i>Distiller</i> used to
+ignore character positions 0&ndash;31 and 128&ndash;159 of every font: Adobe&rsquo;s
+fonts never use such positions, so why should <i>Distiller</i>?
+<p/>Well, the answer to this question is &ldquo;because Adobe don&rsquo;t produce all
+the world&rsquo;s fonts&rdquo; &mdash; fonts like <i>Computer</i>
+<i>Modern</i> were around before Adobe came on the scene, and
+<em>they</em> use positions 0&ndash;31.  Adobe don&rsquo;t react to complaints like
+that in the previous sentence, but they do release new versions of
+their programs; and <i>Distiller</i>, since at least version 4.0,
+<em>has</em> recognised the font positions it used to shun.
+<p/>Meanwhile, TeX users with old versions of <i>Distiller</i> need
+to deal with their fonts.  <i>Dvips</i> comes to our aid: the
+switch <code>-G1</code> (&ldquo;remap characters&rdquo;), which moves the offending
+characters out of the way.  The PDF configuration file
+(<code>-Ppdf</code>), recommended 
+in &ldquo;<a href="FAQ-fuzzy-type3.html">the wrong type of fonts</a>&rdquo;,
+includes the switch.
+<p/>The switch is not without its problems; pre-2003 versions of
+<i>dvips</i> will apply it to Adobe fonts as well, causing
+<a href="FAQ-charshift.html">havoc</a>, but fortunately
+that problem is usually soluble.  However, a document using both
+CM and Adobe-specified fonts is stuck.  The only real solution
+is either to upgrade <i>dvips</i>, or to spend money to upgrade
+<i>Distiller</i>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html
new file mode 100644
index 00000000000..675a02de27b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label divzero</title>
+</head><body>
+<h3>Graphics division by zero</h3>
+<p/>While the error
+<blockquote>
+<pre>
+! Package graphics Error: Division by 0.
+</pre>
+</blockquote><p>
+can actually be caused by offering the package a figure which claims
+to have a zero dimension, it&rsquo;s more commonly caused by rotation.
+<p/>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&rsquo;ve
+converted it to a zero-height object.
+<p/>Suppose you&rsquo;re including your graphic with a command like:
+<blockquote>
+<pre>
+\includegraphics[angle=180,height=5cm]{myfig.eps}
+</pre>
+
+</blockquote><p>
+In the case that <i>myfig.eps</i> has no depth to start with, the
+scaling calculations will produce the division-by-zero error.
+<p/>Fortunately, the <i>graphicx</i> package has a keyword
+<code>totalheight</code>, which allows you to specify the size of the
+image relative to the sum of the object&rsquo;s <code>height</code> and
+<code>depth</code>, so
+<blockquote>
+<pre>
+\includegraphics[angle=180,totalheight=5cm]{myfig.eps}
+</pre>
+
+</blockquote><p>
+will resolve the error, and will behave as you might hope.
+<p/>If you&rsquo;re using the simpler <i>graphics</i> package, use the
+<code>*</code> form of the <code>\</code><code>resizebox</code> command to specify the use of
+<code>totalheight</code>:
+<blockquote>
+<pre>
+\resizebox*{!}{5cm}{%
+  \rotatebox{180}{%
+    \includegraphics{myfig.eps}%
+  }%
+}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>graphics.sty,graphicx.sty</i></tt><dd>Both parts of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html
new file mode 100644
index 00000000000..577b074dc47
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html
@@ -0,0 +1,13 @@
+<head>
+<title>UK TeX FAQ -- question label doc-dirs</title>
+</head><body>
+<h3>Directories of (La)TeX information</h3>
+<p/>TUG India is developing a series of online LaTeX tutorials
+which can be strongly recommended: select single chapters at a time
+from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutorials.html</a> &mdash; the
+set comprises two parts, &ldquo;Text&rdquo; and &ldquo;Graphics&rdquo;, so far.
+<p/>Herbert Voss&rsquo;s excellent 
+<a href="http://texnik.de/">LaTeX tips and tricks</a> is an excellent
+source of small articles on the use of LaTeX.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html
new file mode 100644
index 00000000000..14f72dc46ec
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label doc-wiki</title>
+</head><body>
+<h3>WIKI pages for TeX and friends</h3>
+<p/>The <em>WIKI</em> concept can be a boon to everyone, if used sensibly.
+The &ldquo;general&rdquo; WIKI allows <em>anyone</em> 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
+WIKI under control.
+<p/>Following the encouraging performance of the 
+<a href="http://contextgarden.net/">ConTeXt WIKI</a>, both a
+<a href="http://en.wikibooks.org/wiki/TeX">(Plain) TeX WIKI</a> and a
+<a href="http://en.wikibooks.org/wiki/LaTeX">LaTeX WIKI</a> have been
+established.  Both seem rather sparse, as yet, and the LaTeX WIKI
+contains some suggestions that go counter to established advice (e.g.,
+the LaTeX WIKI has details on the 
+<a href="FAQ-eqnarray.html">use of the <code>eqnarray</code> environment</a>);
+however one may hope that both will become useful resources in the
+longer term.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html
new file mode 100644
index 00000000000..aa6074b7fed
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label docotherdir</title>
+</head><body>
+<h3>Bits of document from other directories</h3>
+<p/>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.
+<p/>Unfortunately, TeX doesn&rsquo;t have a changeable &ldquo;current directory&rdquo;,
+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.
+<p/>It may be appropriate to use the &ldquo;path extension&rdquo; technique
+
+<a href="FAQ-tempinst.html">used in temporary installations</a> to deal with
+this problem.  However, if there several files with the same name in
+your document, such as <i>chapter1/fig1.eps</i> and
+<i>chapter2/fig1.eps</i>, you&rsquo;re not giving TeX any hint as to
+which you&rsquo;re referring to when in the main chapter file you say
+<code>\</code><code>input{sect1}</code>; while this is readily soluble in the case of
+human-prepared files (just don&rsquo;t name them all the same),
+automatically produced files have a way of having repetitious names,
+and changing <em>them</em> is a procedure prone to error.
+<p/>The <i>import</i> package comes to your help here: it defines an
+<code>\</code><code>import</code> command that accepts a full path name and the name of a
+file in that directory, and arranges things to &ldquo;work properly&rdquo;.
+So, for example, if <i>/home/friend/results.tex</i> contains
+<blockquote>
+<pre>
+Graph: \includegraphics{picture}
+\input{explanation}
+</pre>
+</blockquote><p>
+then <code>\</code><code>import{/home/friend/}{results}</code> will include both
+graph and explanation as one might hope.  A <code>\</code><code>subimport</code> command
+does the same sort of thing for a subdirectory (a relative path rather
+than an absolute one), and there are corresponding <code>\</code><code>includefrom</code>
+and <code>\</code><code>subincludefrom</code> commands.
+<p/>The <i>chapterfolder</i> package provides commands to deal with its
+(fixed) model of file inclusion in a document.  It provides commands
+<code>\</code><code>cfpart</code>, <code>\</code><code>cfchapter</code>, <code>\</code><code>cfsection</code> and <code>\</code><code>cfsubsection</code>,
+each of which takes directory and file arguments, e.g.:
+<blockquote>
+<pre>
+\cfpart[pt 1]{Part One}{part1}{part}
+</pre>
+</blockquote><p>
+which command will issue a &lsquo;normal&rsquo; command 
+<code>\</code><code>part[pt 1]{Part One}</code> and then input the file
+<i>part1/part.tex</i>, remembering that <i>part1/</i> is now the
+&ldquo;current folder&rdquo;.  There are also commands of the form
+<code>\</code><code>cfpartstar</code> (which corresponds to a <code>\</code><code>part*</code> command).
+<p/>Once you&rsquo;re &ldquo;in&rdquo; a <i>chapterfolder</i>-included document, you
+may use <code>\</code><code>cfinput</code> to input something relative to the &ldquo;current
+folder&rdquo;, or you may use <code>\</code><code>input</code>, using <code>\</code><code>cfcurrentfolder</code> to
+provide a path to the file.  (There are also
+<code>\</code><code>cfcurrentfolderfigure</code> for a <i>figure/</i> subdirectory and
+<code>\</code><code>cfcurrentfolderlistings</code> for a <i>listings/</i> subdirectory.)
+<p/>Documentation of <i>chapterfolder</i> is in French, but the
+<i>README</i> in the directory is in English.
+<dl>
+<dt><tt><i>chapterfolder.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chapterfolder.zip">macros/latex/contrib/chapterfolder</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chapterfolder.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chapterfolder/">browse</a>)
+<dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docpictex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docpictex.html
new file mode 100644
index 00000000000..2040e88b3ac
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docpictex.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label docpictex</title>
+</head><body>
+<h3>The PicTeX manual</h3>
+<p/>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, 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 PCTeX (<a href="http://www.pctex.com/">http://www.pctex.com/</a>).  The
+manual is <em>not</em> available electronically.
+<p/>However, there <em>is</em> a summary of PicTeX commands available on
+CTAN, which is a great aide-memoire for those who basically
+know the package to start with.
+<dl>
+<dt><tt><i>pictex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pictex.zip">graphics/pictex</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/">browse</a>)
+<dt><tt><i>PiCTeX summary</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/pictex/summary.zip">info/pictex/summary</a> (<a href="ftp://cam.ctan.org/tex-archive/info/pictex/summary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/pictex/summary/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html
new file mode 100644
index 00000000000..3c4ccb76671
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label dolldoll</title>
+</head><body>
+<h3>Why use <code>\</code><code>[</code> ...<code>\</code><code>]</code> in place of <code>$$</code> ...<code>$$</code>?</h3>
+<p/>LaTeX defines inline- and display-maths commands, apparently
+analogous to those that derive from the TeX primitive maths
+sequences bracketing maths commands with single dollar signs (or pairs
+of dollar signs).
+<p/>As it turns out, LaTeX&rsquo;s inline maths grouping, 
+<code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code>, has precisely the same effect as the
+TeX primitive version <code>$ ... $</code>.  (Except that
+the LaTeX version checks to ensure you don&rsquo;t put <code>\</code><code>(</code> and
+<code>\</code><code>)</code> the wrong way round.)
+<p/>In this circumstance, one often finds LaTeX users, who have some
+experience of using Plain TeX, merely assuming that LaTeX&rsquo;s
+display maths grouping <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> may be replaced by
+the TeX primitive display maths <code>$$ ... $$</code>.
+<p/>Unfortunately, they are wrong: if LaTeX code is going to patch display
+maths, it can only do so by patching <code>\</code><code>[</code> and <code>\</code><code>]</code>.  The most
+obvious way this turns up, is that the class option <code>fleqn</code>
+simply does not work for equations coded using 
+<code>$$ ... $$</code>, whether you&rsquo;re using the standard classes
+alone, or using package <i>amsmath</i>.  Also, the <code>\</code><code>[</code> and
+<code>\</code><code>]</code> has code for rationalising vertical spacing in some extreme
+cases; that code is not available in <code>$$ ... $$</code>, so if you
+use the non-standard version, you may occasionally observe
+inconsistent vertical spacing .
+<p/>There are more subtle effects (especially with package
+<i>amsmath</i>), and the simple rule is 
+<code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> whenever
+unadorned displayed maths is needed in LaTeX.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html
new file mode 100644
index 00000000000..56c65cbb3c2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label dpfloat</title>
+</head><body>
+<h3>Facing floats on 2-page spread</h3>
+<p/>If a pair of floats are 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 <i>dpfloat</i> package provides for
+this: the construction to use is:
+<blockquote>
+<pre>
+\begin{figure}[p]
+  \begin{leftfullpage}
+    &lt;left side figure&gt;
+  \end{leftfullpage}
+\end{figure}
+\begin{figure}[p]
+  \begin{fullpage}
+    &lt;right side figure&gt;
+  \end{fullpage}
+\end{figure}
+</pre>
+</blockquote><p>
+The construction has no effect unless the standard class option
+<code>twoside</code> is in effect.
+<p/>Full documentation of the package (such as it is) is to be found in
+<i>README.dpfloat</i>
+<dl>
+<dt><tt><i>dpfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dpfloat.zip">macros/latex/contrib/dpfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dpfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dpfloat/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html
new file mode 100644
index 00000000000..08a3f88af38
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label drawFeyn</title>
+</head><body>
+<h3>Drawing Feynman diagrams in LaTeX</h3>
+<p/>Michael Levine&rsquo;s <i>feynman</i> bundle for drawing the diagrams in
+LaTeX 2.09 is still available.
+<p/>Thorsten Ohl&rsquo;s <i>feynmf</i> is designed for use with current
+LaTeX, and works in
+combination with Metafont (or, in its <i>feynmp</i> incarnation, with
+MetaPost).  The <i>feynmf</i> or
+<i>feynmp</i> package reads a description of the diagram written
+in TeX, and writes out code.  Metafont (or MetaPost) can then produce a
+font (or PostScript file) for use in a subsequent LaTeX run.  For
+new users, who have access to MetaPost, the PostScript version is
+probably the better route, for document portability and other reasons.
+
+<p/>Jos Vermaseren&rsquo;s <i>axodraw</i> is mentioned as an alternative in
+the documentation of <i>feynmf</i>, but it is written entirely in
+terms of <i>dvips</i> <code>\</code><code>special</code> commands, and is thus rather
+imperfectly portable.
+<p/>An alternative approach is implemented by Norman Gray&rsquo;s <i>feyn</i>
+package.  Rather than creating complete diagrams as postscript images,
+<i>feyn</i> 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.
+<dl>
+<dt><tt><i>axodraw</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/axodraw.zip">graphics/axodraw</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/axodraw.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/axodraw/">browse</a>)
+<dt><tt><i>feyn font bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/feyn.zip">fonts/feyn</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/feyn.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/feyn/">browse</a>)
+<dt><tt><i>feynman bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.zip">macros/latex209/contrib/feynman</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/feynman/">browse</a>)
+<dt><tt><i>feynmf/feynmp bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.zip">macros/latex/contrib/feynmf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/feynmf/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html
new file mode 100644
index 00000000000..5cd801f9013
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html
@@ -0,0 +1,77 @@
+<head>
+<title>UK TeX FAQ -- question label drawing</title>
+</head><body>
+<h3>Drawing with TeX</h3>
+<p/>There are many packages to do pictures in (La)TeX itself (rather than
+importing graphics created externally), ranging from simple use of
+LaTeX <code>picture</code> environment, through enhancements like
+<i>epic</i>, to 
+sophisticated (but slow) drawing with PicTeX. Depending on your type
+of drawing, and setup, here are a few systems you may consider:
+<ul>
+<li> <i>pict2e</i>; this was advertised in 
+  <a href="FAQ-books.html">the LaTeX manual</a>, but didn&rsquo;t appear for nearly
+  ten years after publication of the book!  It removes all the petty
+  niggles that surround the use of the <code>picture</code>
+  environment.  It therefore suffers <em>only</em> 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
+  <i>pict2e</i> supersedes David Carlisle&rsquo;s stop-gap
+  <i>pspicture</i>.)
+<li> <i>PSTricks</i>; this gives you access to all the power of
+  PostScript from TeX itself, by sophisticated use of
+  <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>.  Since PostScript is itself a
+  pretty powerful programming language, many  astounding things can in
+  principle be achieved using <i>PSTricks</i>.
+  <i>pstricks</i>&rsquo; <code>\</code><code>special</code>s are
+  by default specific to <i>dvips</i>, but VTeX (both in its
+  commercial and in its free versions) understands them.  PDFTeX
+  users may use <i>pst-pdf</i>, which (like
+  <i>epstopdf</i> &mdash; see 
+  <a href="FAQ-pdftexgraphics.html">PDFLaTeX graphics</a>) generates
+  PDF files using an auxiliary program, from <i>PSTricks</i>
+  commands (<i>pst-pdf</i> also requires a recent installation of
+  the <i>preview</i> package).
+<p/>  There is a <i>PSTricks</i> mailing list
+  (<a href="mailto:pstricks@tug.org"><i>pstricks@tug.org</i></a>) which you may
+  <a href="http://tug.org/mailman/listinfo/pstricks">join</a>, or you may
+  just browse the 
+  <a href="http://tug.org/pipermail/pstricks/">list archives</a>.
+<li> <i>pgf</i>: while <i>pstricks</i> is very powerful and
+  convenient, using it with PDFLaTeX is an awful fidget: if you
+  simply want the graphical capabilities, <i>pgf</i>, together with
+  its rather pleasing &ldquo;user-oriented&rdquo; interface <i>tikz</i>, may be a good
+  bet for you.  While PDF has (in essence) the same graphical
+  capabilities as PostScript, it isn&rsquo;t programmable; <i>pgf</i> provides
+  common LaTeX commands that will utilise the graphical
+  capabilities of both PostScript and PDF equally.
+<li> MetaPost; you liked Metafont, but never got to grips with font files?
+  Try <a href="FAQ-MP.html">MetaPost</a> &mdash;
+  all the power of Metafont, but it generates PostScript figures; MetaPost
+  is nowadays part of most serious (La)TeX distributions.  Knuth
+  uses it for all his work...
+<li> <i>Mfpic</i>; you liked Metafont, but can&rsquo;t understand the
+  language?  The package makes up Metafont or MetaPost code for you
+  within using familiar-looking TeX macros.  Not <em>quite</em> the
+  full power of MetaPost, but a friendlier interface; of course, with
+  MetaPost output, the results can be used equally well in either
+  LaTeX or PDFLaTeX.
+<li> You liked PicTeX but don&rsquo;t have enough memory or time?  Look
+  at Eitan Gurari&rsquo;s <i>dratex</i>, which is as powerful as most
+  other TeX drawing packages, but is an entirely new
+  implementation, which is not as hard on memory, is much more
+  readable (and is fully documented).
+</ul>
+<dl>
+<dt><tt><i>dratex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/dratex.zip">graphics/dratex</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/dratex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/dratex/">browse</a>)
+<dt><tt><i>mfpic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/mfpic.zip">graphics/mfpic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/mfpic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/mfpic/">browse</a>)
+<dt><tt><i>preview.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preview.zip">macros/latex/contrib/preview</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preview.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preview/">browse</a>)
+<dt><tt><i>pspicture.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pspicture.zip">macros/latex/contrib/pspicture</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pspicture.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pspicture/">browse</a>)
+<dt><tt><i>pst-pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.zip">macros/latex/contrib/pst-pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf/">browse</a>)
+<dt><tt><i>pgf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>)
+<dt><tt><i>pict2e.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pict2e.zip">macros/latex/contrib/pict2e</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pict2e.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pict2e/">browse</a>)
+<dt><tt><i>pstricks</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>)
+<dt><tt><i>tikz.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html
new file mode 100644
index 00000000000..bb395b8b06a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label driver</title>
+</head><body>
+<h3>What is a DVI driver?</h3>
+<p/>A DVI driver is a program that takes as input a DVI file
+(<a href="FAQ-dvi.html">DVI files</a>)  and
+(usually) produces a file that can be sent to a typographic
+output device (which we will call a printer, for short), or to another
+format.
+<p/>A driver will usually be specific to a particular printer,
+although any PostScript printer ought to be able to print
+the output from a PostScript driver.
+
+<p/>As well as the DVI file, the driver 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 the printer itself &lsquo;has&rsquo;.
+Each driver will expect the font information in
+a particular form.  For more information on the forms of fonts,
+see <a href="FAQ-pk.html">PK files</a>,
+
+<a href="FAQ-tfm.html">TFM files</a>,
+<a href="FAQ-virtualfonts.html">virtual fonts</a>
+and <a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html
new file mode 100644
index 00000000000..32a0256fd41
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label dropping</title>
+</head><body>
+<h3>Big letters at the start of a paragraph</h3>
+<p/>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.
+<p/>This style is known as &ldquo;dropped capitals&rdquo;, or (in French)
+«lettrines», and TeX&rsquo;s primitive
+facilities for hanging indentation make its (simple) implementation
+pretty straightforward.
+<p/>The <i>dropping</i> 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 <code>.dtx</code>, the package itself must already be installed.
+Unfortunately, <i>dropping</i> 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 recent
+offerings like PDFTeX, VTeX or DVIpdfm.
+<p/>On such occasions, the more recent <i>lettrine</i> package is more
+likely to succeed.  It has a well-constructed array of options, and
+the examples (a pretty impressive set) come as a separate file in the
+distribution (also available in PostScript, so that they can be viewed
+without installing the package itself).
+<dl>
+<dt><tt><i>dropping</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dropping.zip">macros/latex/contrib/dropping</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dropping.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dropping/">browse</a>)
+<dt><tt><i>lettrine</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lettrine.zip">macros/latex/contrib/lettrine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lettrine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lettrine/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html
new file mode 100644
index 00000000000..cbbed32fbb1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html
@@ -0,0 +1,53 @@
+<head>
+<title>UK TeX FAQ -- question label dtx</title>
+</head><body>
+<h3>Documented LaTeX sources (<code>.dtx</code> files)</h3>
+<p/>LaTeX2e, and most contributed macro packages, are now written in a
+<a href="FAQ-lit.html">literate programming style</a>, with source and
+documentation in the
+same file.  This format, known as &lsquo;doc&rsquo;, in fact originated before the
+days of the LaTeX project as one of the &ldquo;Mainz&rdquo; series of
+packages. A documented source file conventionally has the suffix
+<code>.dtx</code>, and will normally be &lsquo;stripped&rsquo; before use with
+LaTeX; an installation file (<code>.ins</code>) is normally provided,
+to automate this process of removing comments for speed of loading.
+To read the comments, you can run LaTeX on the
+<code>.dtx</code> file to produce a nicely formatted version of the
+documented code.  Several
+packages can be included in one <code>.dtx</code> file (they&rsquo;re sorted
+out by the <code>.ins</code> file), with conditional
+sections, and there are facilities for indexes of macros, etc.
+<p/>Anyone can write <code>.dtx</code> files; the format is explained in
+<a href="FAQ-books.html">The LaTeX Companion</a>, and a tutorial is available
+from CTAN (which comes with skeleton <code>.dtx</code> and
+<code>.ins</code> files).
+<p/>Composition of <code>.dtx</code> files is supported in <i>emacs</i> by
+<a href="FAQ-editors.html">AUC-TeX</a>.
+<p/>Another useful way of generating <code>.dtx</code> files is to write the
+documentation and the code separately, and then to combine them using
+the <i>makedtx</i> system.  This technique has particular value in
+that the documentation file can be used separately to generate
+HTML output; it is often quite difficult to make 
+<a href="FAQ-LaTeX2HTML.html">LaTeX to HTML conversion</a> tools deal
+with <code>.dtx</code> files, since they use an unusual class file.
+<p/>The <code>.dtx</code> files are not used by LaTeX after they have been
+processed to produce <code>.sty</code> or <code>.cls</code> (or whatever)
+files.  They need not be kept with the working system; however, for
+many packages the <code>.dtx</code> file is the primary source of
+documentation, so you may want to keep <code>.dtx</code> files elsewhere.
+<p/>An interesting sideline to the story of <code>.dtx</code> files is the
+<i>docmfp</i> package, which extends the model of the <i>doc</i>
+package to
+
+  <a href="FAQ-MF.html">Metafont</a> and <a href="FAQ-MP.html">MetaPost</a>,
+thus permitting documented distribution of bundles containing code for
+Metafont and MetaPost together with related LaTeX code.
+<dl>
+<dt><tt><i>clsguide.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc/clsguide.pdf">macros/latex/doc/clsguide.pdf</a>
+<dt><tt><i>docmfp.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/docmfp.zip">macros/latex/contrib/docmfp</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/docmfp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/docmfp/">browse</a>)
+<dt><tt><i>docstrip.tex</i></tt><dd>Part of the LaTeX distribution
+<dt><tt><i>DTX tutorial</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/dtxtut.zip">info/dtxtut</a> (<a href="ftp://cam.ctan.org/tex-archive/info/dtxtut.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/dtxtut/">browse</a>)
+<dt><tt><i>makedtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/makedtx.zip">support/makedtx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/makedtx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/makedtx/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html
new file mode 100644
index 00000000000..11ea878604c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label dvi-bmp</title>
+</head><body>
+<h3>Generating bitmaps from DVI</h3>
+<p/>In the last analysis, any 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&rsquo;s usually difficult to extract any of those bitmaps any
+way other than by screen capture, and the resolution of <em>that</em> is
+commonly lamentable.
+<p/>Why would one want separate bitmaps?  Most often, the requirement is for
+something that can be included in HTML generated from (La)TeX
+source &mdash; not everything that you can write in (La)TeX can be
+translated to HTML (at least, portable HTML that may be
+viewed in &lsquo;most&rsquo; browsers), so the commonest avoiding action is to
+generate a bitmap of the missing bit.  Examples are maths (a maths
+extension to the <code>*</code>ML family is available but not widely
+used), and &lsquo;exotic&rsquo; 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&rsquo;s display &mdash; to insert equations into Microsoft
+PowerPoint, or to support the enhanced-<i>emacs</i> setup called
+<a href="FAQ-WYGexpts.html"><i>preview</i>-<i>latex</i></a>.
+<p/>In the past, the commonest way of generating bitmaps was to generate a
+PostScript file of the DVI and then use <i>ghostscript</i> to
+produce the required bitmap format (possibly by way of PNM
+format or something similar).  This is an undesirable procedure (it is
+very slow, and requires two or three steps) but it has served for a
+long time.
+<p/>(La)TeX users may now take advantage of two bitmap &lsquo;drivers&rsquo;.  The
+longer-established, <i>dvi2bitmap</i>, will generate XBM and
+XPM formats, the long-deprecated GIF format (which is
+now obsolescent, but has finally been relieved of the patent
+protection of the LZW compression it uses), and also
+the modern (ISO-standardised) PNG format.
+<p/>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 PNG files: the <i>README</i> mentions
+<i>preview</i>-<i>latex</i>, <i>LyX</i>, and a few
+web-oriented environments. Note that <i>dvipng</i> gives
+high-quality output even though its internal operations are optimised
+for speed.
+<dl>
+<dt><tt><i>dvi2bitmap</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2bitmap.zip">dviware/dvi2bitmap</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2bitmap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2bitmap/">browse</a>)
+<dt><tt><i>dvipng</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipng.zip">dviware/dvipng</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipng.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipng/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html
new file mode 100644
index 00000000000..7539268ba10
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label dvi</title>
+</head><body>
+<h3>What is a DVI file?</h3>
+<p/>A DVI file (that is, a file with the type or extension
+<code>.dvi</code>) is TeX&rsquo;s main output file, using TeX in its
+broadest sense to include LaTeX, etc.  &lsquo;DVI&rsquo; is supposed to
+be an acronym for DeVice-Independent, meaning
+that the file can be printed on most
+kinds of typographic output device.  The DVI file is designed to be
+read by a driver (<a href="FAQ-driver.html">DVI drivers</a>) to produce
+further output designed specifically for a particular printer (e.g., a
+LaserJet) or to be used as input to a previewer for display on a
+computer screen.  DVI files use TeX&rsquo;s internal coding; a TeX
+input file should produce the same DVI file regardless of which
+implementation of TeX is used to produce it.
+<p/>A DVI file contains all the information that is needed for printing 
+or previewing except for the actual bitmaps or outlines of fonts, and 
+possibly material to be introduced by means of
+<a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>.
+<p/>The canonical reference for the structure of a DVI file is the
+source of Knuth&rsquo;s program <i>dvitype</i> (whose original purpose,
+as its name implies, was to view the content of a DVI file).
+<dl>
+<dt><tt><i>dvitype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/dist/texware/dvitype.web">systems/knuth/dist/texware/dvitype.web</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html
new file mode 100644
index 00000000000..e0e0c376c90
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label dvipdfmgraphics</title>
+</head><body>
+<h3>Imported graphics in <i>dvipdfm</i></h3>
+<p/><i>Dvipdfm</i> translates direct from DVI to PDF
+(all other available routes produce PostScript output using
+<i>dvips</i> and then convert that to PDF with
+<i>ghostscript</i> or <i>Acrobat</i> <i>Distiller</i>).
+<p/><i>Dvipdfm</i> is a particularly flexible application.  It will
+permit the inclusion of bitmap and PDF graphics, as does
+<a href="FAQ-pdftexgraphics.html">PDFTeX</a>, but is also capable of employing
+<i>ghostscript</i> &ldquo;on the fly&rdquo; so as to be able to permit the
+inclusion of encapsulated PostScript (<code>.eps</code>) files by translating
+them to PDF.  In this way, <i>dvipdfm</i> combines the good
+qualities of <i>dvips</i> and of PDFTeX as a means of
+processing illustrated documents.
+<p/>Unfortunately, &ldquo;ordinary&rdquo; LaTeX can&rsquo;t deduce the bounding box of
+a binary bitmap file (such as JPEG or PNG), so you have
+to specify the bounding box.  This may be done explicitly, in the
+document:
+<blockquote>
+<pre>
+\usepackage[dvipdfm]{graphicx}
+...
+\includegraphics[bb=0 0 540 405]{photo.jpg}
+</pre>
+</blockquote><p>
+It&rsquo;s usually not obvious what values to give the &ldquo;<code>bb</code>&rdquo; key,
+but the program <i>ebb</i> will generate a file
+containing the information; the above numbers came from an
+<i>ebb</i> output file <i>photo.bb</i>:
+<blockquote>
+<pre>
+%%Title: /home/gsm10/photo.jpg
+%%Creator: ebb Version 0.5.2
+%%BoundingBox: 0 0 540 405
+%%CreationDate: Mon Mar  8 15:17:47 2004
+</pre>
+</blockquote><p>
+However, if such a file is available, you may abbreviate the inclusion
+code, above, to read:
+<blockquote>
+<pre>
+\usepackage[dvipdfm]{graphicx}
+...
+\includegraphics{photo}
+</pre>
+</blockquote><p>
+which makes the operation feel as simple as does including
+<code>.eps</code> images in a LaTeX file for processing with
+<i>dvips</i>; the <i>graphicx</i> package knows to look for a
+<code>.bb</code> file if no bounding box is provided in the
+<code>\</code><code>includegraphics</code> command.
+<p/>The one place where usage isn&rsquo;t quite so simple is the need to quote
+<i>dvipdfm</i> explicitly, as an option when loading the
+<i>graphicx</i> package: if you are using <i>dvips</i>, you
+don&rsquo;t ordinarily need to specify the fact, since the default graphics
+configuration file (of most distributions) &ldquo;guesses&rdquo; the
+<code>dvips</code> option if you&rsquo;re using TeX.
+<dl>
+<dt><tt><i>dvipdfm</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>)
+<dt><tt><i>ebb</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html
new file mode 100644
index 00000000000..9da7380561b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label dvips-pdf</title>
+</head><body>
+<h3>Quality of PDF from PostScript</h3>
+<!-- blurry fuzzy crippled -->
+<p/>Any reasonable PostScript, including any output of <i>dvips</i>, may be
+converted to PDF, using (for example) a sufficiently recent
+version of <i>ghostscript</i>, Frank Siegert&rsquo;s (shareware)
+<a href="http://www.pstill.com/"><i>PStill</a></i>, or Adobe&rsquo;s (commercial)
+<i>Distiller</i>.
+<p/>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:
+<ul>
+<li> <a href="FAQ-fuzzy-type3.html">Wrong type of fonts used</a>, which is
+  the commonest cause of fuzzy text.
+<li> <a href="FAQ-fuzzy-gs.html"><i>Ghostscript</i> too old</a>,
+  which can also result in fuzzy text.
+
+<li> <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1 encoding</a>,
+  which is yet another possible cause of fuzzy text.
+<li> Another problem &mdash; missing characters &mdash; arises from an
+  
+  <a href="FAQ-distill-prob.html">aged version of <i>Adobe</i> <i>Distiller</i></a>.
+<li> Finally, there&rsquo;s the common confusion that arises from using the
+  <i>dvips</i> configuration file <code>-Ppdf</code>, the 
+  <a href="FAQ-charshift.html">weird characters</a>.
+</ul>
+It should be noted that <i>Adobe</i> 
+                                         
+<i>Reader</i> 6 (released in mid-2003, and later versions) does
+not exhibit the &ldquo;fuzziness&rdquo; 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.
+<p/>The problems are also discussed, with practical examples, in Mike
+Shell&rsquo;s <i>testflow</i> package, which these FAQs recommend as a
+&ldquo;<a href="FAQ-tutbitslatex.html">specialised tutorial</a>.
+<dl>
+<dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html
new file mode 100644
index 00000000000..b64722780eb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label dvips</title>
+</head><body>
+<h3>DVI to PostScript conversion programs</h3>
+<p/>The best public domain DVI to PostScript conversion program, which
+runs under many operating systems, is Tom Rokicki&rsquo;s <i>dvips</i>.
+<i>dvips</i> is written in C and ports easily.  All current
+development is in the context of Karl Berry&rsquo;s <i>kpathsea</i>
+library, and sources are available from the TeX Live repository,
+and versions are available in all TeX distributions that recognise
+the use of PostScript.
+<p/>An VMS versions is available as part of the CTAN
+distribution of TeX for VMS.
+<p/>A precompiled version to work with emTeX is available on CTAN.
+<dl>
+<dt><tt><i>MSDOS and OS/2</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.zip">systems/msdos/dviware/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/dviware/dvips/">browse</a>)
+<dt><tt><i>VMS distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/OpenVMS/TEX97_CTAN.ZIP">systems/OpenVMS/TEX97_CTAN.ZIP</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html
new file mode 100644
index 00000000000..19140f647be
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label dvipsgraphics</title>
+</head><body>
+<h3>Imported graphics in <i>dvips</i></h3>
+<p/><i>Dvips</i>, as originally conceived, can only import a single
+graphics format: 
+<a href="FAQ-eps.html">encapsulated PostScript</a> (<code>.eps</code> files).
+<i>Dvips</i> also deals with the slightly eccentric EPS that is
+created by <a href="FAQ-MP.html">MetaPost</a>.
+<p/>Apart from the fact that a depressing proportion of drawing
+applications produce corrupt EPS when asked for such output,
+this is pretty satisfactory for vector graphics work.
+<p/>To include bitmap graphics, you need some means of converting them to
+PostScript; in fact many standard image manipulators (such as
+<i>ImageMagick</i>&rsquo;s <i>convert</i>) make a good job of
+creating EPS files (but be sure to ask for output at PostScript
+level 2 or higher).  (<i>Unix</i> users should beware of
+<i>xv</i>&rsquo;s claims: it has a tendency to downsample your bitmap to
+your screen resolution.)
+<p/>Special purpose applications <i>jpeg2ps</i> (which converts
+JPEG files using PostScript level 2 functionality),
+<i>bmeps</i> (which converts both JPEG and PNG
+files) and <i>a2ping</i>/<i>sam2p</i> (which convert a
+bewildering array of bitmap formats to EPS or PDF files;
+<i>sam2p</i> is one of the engines that <i>a2ping</i> uses)
+are also considered &ldquo;good bets&rdquo;.
+<p/><i>Bmeps</i> comes with patches to produce your own version of
+<i>dvips</i> that can cope with JPEG and PNG direct,
+using <i>bmeps</i>&rsquo;s conversion library.  <i>Dvips</i>, 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.
+<dl>
+<dt><tt><i>a2ping</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/a2ping.zip">graphics/a2ping</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/a2ping.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/a2ping/">browse</a>)
+<dt><tt><i>bmeps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/bmeps.zip">support/bmeps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/bmeps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/bmeps/">browse</a>)
+<dt><tt><i>jpeg2ps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.zip">nonfree/support/jpeg2ps</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/jpeg2ps/">browse</a>)
+<dt><tt><i>sam2p</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.zip">graphics/sam2p</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/sam2p/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html
new file mode 100644
index 00000000000..14e4e09b747
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label edef</title>
+</head><body>
+<h3><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></h3>
+<p/>Robust LaTeX commands are either &ldquo;naturally robust&rdquo; &mdash; meaning that
+they never need <code>\</code><code>protect</code>, or &ldquo;self-protected&rdquo; &mdash; meaning that
+they have <code>\</code><code>protect</code> built in to their definition in some
+way.  Self-protected commands, and fragile commands with
+<code>\</code><code>protect</code>ion are only robust in a context where the <code>\</code><code>protect</code>
+mechanism is properly handled.  The body of an <code>\</code><code>edef</code> definition
+doesn&rsquo;t handle <code>\</code><code>protect</code> properly, since <code>\</code><code>edef</code> is a TeX
+primitive rather than a LaTeX command.
+<p/>This problem is resolved by a LaTeX internal command
+<code>\</code><code>protected@edef</code>, which does the job of <code>\</code><code>edef</code> while keeping the
+<code>\</code><code>protect</code> mechanism working.  There&rsquo;s a corresponding
+<code>\</code><code>protected@xdef</code> which does the job of <code>\</code><code>xdef</code>.
+<p/>Of course, these commands need to be tended carefully, since they&rsquo;re
+
+internal: see <a href="FAQ-atsigns.html">&rsquo;@&rsquo; in control sequence names</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html
new file mode 100644
index 00000000000..e9e01c97566
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html
@@ -0,0 +1,97 @@
+<head>
+<title>UK TeX FAQ -- question label editors</title>
+</head><body>
+<h3>TeX-friendly editors and shells</h3>
+<p/>There are good TeX-writing environments and editors for most
+operating systems; some are described below, but this is only a
+personal selection:
+<dl>
+<dt>Unix<dd> Try
+  <a href="http://www.gnu.org/software/emacs/emacs.html">GNU <i>emacs</a></i>
+  or <a href="http://www.xemacs.org/"><i>XEmacs</a></i>, and
+  the AUC-TeX
+  bundle (available from CTAN).  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.
+<p/>  Many who consider the versions of <i>emacs</i> spawn of the devil, prefer
+  <a href="http://vim.sourceforge.net"><i>vim</a></i>, a highly configurable
+  editor (also available for Windows and Macintosh systems).  Many
+  plugins are available to support the needs of the (La)TeX user,
+  including syntax highlighting, calling TeX programs,
+  auto-insertion and -completion of common (La)TeX structures, and
+  browsing LaTeX help.  The scripts <i>auctex.vim</i> and
+  <i>bibtex.vim</i> seem to be the most common recommendations.
+<p/>  The editor <a href="http://nedit.org/"><i>NEdit</a></i> is also free
+  and programmable, and is available for Unix systems.  An
+  AUC-TeX-alike set of extensions for <i>NEdit</i> is available
+  from CTAN.
+<p/>  <i>LaTeX4Jed</i> provides much enhanced LaTeX support for the
+  <a href="http://www.jedsoft.org/jed/"><i>jed</a></i> editor.
+  <i>LaTeX4Jed</i> is similar to 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.
+<p/>  The <i>Kile</i> editor that is provided with the KDE
+  window manager provides GUI &ldquo;shell-like&rdquo; facilities, in a
+  similar way to the widely-praised <i>Winedt</i> (see below);
+  details (and downloads) are available from the project&rsquo;s
+  <a href="http://kile.sourceforge.net/">home on SourceForge</a>.  A newer
+  system (by <i>Kile</i>&rsquo;s original author),
+  <a href="http://www.xm1math.net/texmaker/"><i>texmaker</a></i> doesn&rsquo;t
+  rely on KDE&rsquo;s facilities, and so may be more easily portable.
+<dt>MSDOS<dd> TeXshell is a simple,
+  easily-customisable environment, which can be used with the editor
+  of your choice.
+<p/>  You can also use GNU <i>emacs</i> and AUC-TeX
+  under MSDOS.
+<dt>Windows &rsquo;9x, NT, etc.<dd><i>TeXnicCenter</i> is a (free)
+  TeX-oriented development system, uniting a powerful platform for
+  executing (La)TeX and friends with a configurable editor.
+<p/>  <i>Winedt</i>, 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 UTF-8 (to some extent), which is
+  useful when working with <a href="FAQ-xetex.html">XeTeX</a> (and other
+  &ldquo;next-generation&rdquo; (La)TeX applications).
+<p/>  Both <i>emacs</i> and <i>vim</i> are available in versions
+  for Windows systems.
+<dt>OS/2<dd> <i>epmtex</i>  offers an OS/2-specific shell.
+<dt>Macintosh<dd> The commercial Textures provides an excellent integrated
+  Macintosh environment with its own editor.  More powerful still (as an
+  editor) is the shareware <i>Alpha</i> which is
+  extensible enough to let you perform almost any TeX-related job. It
+  works well with OzTeX.  From release 2.2.0 (at least), Textures
+  works with MacOS X.
+<p/>  For MacOS X users, the free tool of choice appears to be
+  <a href="http://www.uoregon.edu/~koch/texshop/texshop.html">TeXShop</a>, which
+  combines an editor and a shell with a coherent philosophy of dealing
+  with (La)TeX 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.
+<p/>  <i>Vim</i> is also available for use on Macintosh systems.
+</dl>
+Atari, Amiga and NeXT users also have nice
+environments. LaTeX users looking for <i>make</i>-like
+facilities should review the answer on
+<a href="FAQ-make.html">Makefiles for LaTeX documents</a>.
+<p/>While many (La)TeX-oriented editors can support work on BibTeX
+files, there are many systems that provide specific &ldquo;database-like&rdquo;
+access to your BibTeX files &mdash;
+  see &ldquo;<a href="FAQ-buildbib.html">creating a bibliography file</a>&rdquo;.
+
+<dl>
+<dt><tt><i>alpha</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.zip">nonfree/systems/mac/support/alpha</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/support/alpha/">browse</a>)
+<dt><tt><i>auctex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/auctex.zip">support/auctex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/auctex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/auctex/">browse</a>)
+<dt><tt><i>epmtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/os2/epmtex.zip">systems/os2/epmtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/os2/epmtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/os2/epmtex/">browse</a>)
+<dt><tt><i>LaTeX4Jed</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/jed.zip">support/jed</a> (<a href="ftp://cam.ctan.org/tex-archive/support/jed.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/jed/">browse</a>)
+<dt><tt><i>Nedit LaTeX support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/NEdit-LaTeX-Extensions.zip">support/NEdit-LaTeX-Extensions</a> (<a href="ftp://cam.ctan.org/tex-archive/support/NEdit-LaTeX-Extensions.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/NEdit-LaTeX-Extensions/">browse</a>)
+<dt><tt><i>TeXnicCenter</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/TeXnicCenter/">systems/win32/TeXnicCenter/</a>
+<dt><tt><i>TeXshell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/texshell.zip">systems/msdos/texshell</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/texshell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/texshell/">browse</a>)
+<dt><tt><i>TeXtelmExtel</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel.zip">systems/msdos/emtex-contrib/TeXtelmExtel</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel/">browse</a>)
+<dt><tt><i>winedt</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/winedt/">systems/win32/winedt/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html
new file mode 100644
index 00000000000..0d37b2b6658
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label empty</title>
+</head><body>
+<h3>Detecting that something is empty</h3>
+<p/>Suppose you need to know that the argument of your command is empty:
+that is, to distinguish between <code>\</code><code>cmd{}</code> 
+and <code>\</code><code>cmd{blah}</code>.  This is pretty simple:
+<blockquote>
+<pre>
+\def\cmd#1{%
+  \def\tempa{}%
+  \def\tempb{#1}%
+  \ifx\tempa\tempb
+    &lt;empty case&gt;
+  \else
+    &lt;non-empty case&gt;
+  \fi
+}
+</pre>
+</blockquote><p>
+The case where you want to ignore an argument that consists of nothing
+but spaces, rather than something completely empty, is more tricky.
+It&rsquo;s solved in the code fragment <i>ifmtarg</i>, which defines
+commands <code>\</code><code>@ifmtarg</code> and <code>\</code><code>@ifnotmtarg</code>, which examine their
+first argument, and select (in opposite directions) their second or
+third argument.  The package&rsquo;s code also appears in the LaTeX
+<i>memoir</i> class.
+<p/><i>Ifmtarg</i> makes challenging reading; there&rsquo;s also a discussion of the
+issue in number two of the &ldquo;around the bend&rdquo; articles by the late
+lamented Mike Downes.
+<dl>
+<dt><tt><i>Around the bend series</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/aro-bend.zip">info/aro-bend</a> (<a href="ftp://cam.ctan.org/tex-archive/info/aro-bend.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/aro-bend/">browse</a>)
+<dt><tt><i>ifmtarg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ifmtarg.sty">macros/latex/contrib/misc/ifmtarg.sty</a>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html
new file mode 100644
index 00000000000..4bbeb620fe9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html
@@ -0,0 +1,69 @@
+<head>
+<title>UK TeX FAQ -- question label endingroup</title>
+</head><body>
+<h3><code>\</code><code>end</code> occurred inside a group</h3>
+<p/>The actual error we observe is:
+<p/>
+<code>(\end occurred inside a group at level &lt;</code><code><em>n</em></code><code>&gt;)</code>
+<p/>
+and it tells us that something we started in the document never got
+finished before we ended the document itself.  The things involved
+(&lsquo;groups&rsquo;) are what TeX uses for restricting the scope of things:
+you see them, for example, in the &ldquo;traditional&rdquo; font selection
+commands: <code>{\it stuff\/}</code> &mdash; if the closing brace is left off such a
+construct, the effect of <code>\</code><code>it</code> will last to the end of the document,
+and you&rsquo;ll get the diagnostic.
+<p/>TeX itself doesn&rsquo;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 <i>emacs</i> and <i>winedt</i> offer this facility).
+However, groups are not <em>only</em> created by matching
+<code>{</code> with <code>}</code>:
+other grouping commands are discussed elsewhere in these FAQs,
+and are also a potential source of unclosed group.
+<p/><code>\</code><code>begin{&lt;<i>environment</i>&gt;}</code> encloses the environment&rsquo;s body
+in a group, and establishes its own diagnostic mechanism.  If you end
+the document before closing some other environment, you get the
+&lsquo;usual&rsquo; LaTeX diagnostic
+
+<pre>
+! LaTeX Error: \begin{blah} on input line 6 ended by \end{document}.
+</pre>
+which (though it doesn&rsquo;t tell you which <em>file</em> the
+<code>\</code><code>begin{blah}</code> 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 &ldquo;occurred inside a group&rdquo; message
+before LaTeX finally exits.  The <i>checkend</i> package
+recognises other unclosed <code>\</code><code>begin{blob}</code> commands, and
+generates an &ldquo;ended by&rdquo; error message for each one, rather than
+producing the &ldquo;occurred inside a group&rdquo; message, which is sometimes
+useful (if you remember to load the package).
+<p/>In the absence of such information from LaTeX, you need to use
+&ldquo;traditional&rdquo; 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&rsquo;s obviously possible to split a correctly-written group
+by chopping in the wrong place), but it will usually find the problem
+fairly quickly.
+<p/>e-TeX (and e-LaTeX &mdash; LaTeX run on e-TeX) gives you
+further diagnostics after the traditional infuriating TeX one &mdash; it
+actually keeps the information in a similar way to LaTeX:
+
+<pre>
+(\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
+</pre>
+The diagnostic not only tells us where the group started, but also the
+<em>way</em> it started: <code>\</code><code>begingroup</code> or <code>{</code> (which is an alias of
+<code>\</code><code>bgroup</code>, and the two are not  distinguishable at the TeX-engine
+level).
+<dl>
+<dt><tt><i>checkend.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bezos.zip">macros/latex/contrib/bezos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bezos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html
new file mode 100644
index 00000000000..6b4f7dae543
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html
@@ -0,0 +1,36 @@
+<head>
+<title>UK TeX FAQ -- question label enlarge</title>
+</head><body>
+<h3>Enlarging TeX</h3>
+<p/>The TeX error message &lsquo;capacity exceeded&rsquo; covers a multitude of
+problems.  What has been exhausted is listed in brackets after the
+error message itself, as in:
+<blockquote>
+<pre>
+! TeX capacity exceeded, sorry
+...              [main memory size=263001].
+</pre>
+</blockquote><p>
+Most of the time this error can be fixed
+<em>without</em> 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 &lsquo;<code>buf_size</code>&rsquo; has overflowed).
+<p/>If you really need to extend your TeX&rsquo;s capacity, the proper method
+depends on your installation.  There is no need (with modern TeX
+implementations) to change the defaults in Knuth&rsquo;s 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.
+<p/>Modern implementations allow the sizes of the various bits of TeX&rsquo;s
+memory to be changed semi-dynamically.  Some (such as emTeX) 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 <i>web2c</i>-based systems,
+this file is called <i>texmf.cnf</i>: 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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html
new file mode 100644
index 00000000000..edf4b689a28
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html
@@ -0,0 +1,64 @@
+<head>
+<title>UK TeX FAQ -- question label entercompmode</title>
+</head><body>
+<h3>Entering compatibility mode</h3>
+<p/>You run your LaTeX job, and it starts by saying
+<blockquote>
+<pre>
+Entering LaTeX 2.09 COMPATIBILITY MODE
+</pre>
+</blockquote><p>
+followed by lines of asterisks and <code>!!WARNING!!</code>.
+<p/>This means that the document is not written in &ldquo;current&rdquo; LaTeX
+syntax, and that there is no guarantee that all parts of the document
+will be formatted correctly.
+<p/>If the document is someone else&rsquo;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 <code>.dvi</code> or <code>.pdf</code> that&rsquo;s
+adequate for most purposes.
+<p/>If it&rsquo;s a new document you have just started working on, you have been
+misled by someone.  You have written something like:
+<blockquote>
+  <code>\</code><code>documentstyle{article}</code>
+</blockquote><p>
+or, more generally:
+<blockquote>
+  <code>\</code><code>documentstyle[</code><em>options</em><code>]{</code><em>class</em><code>}</code>
+</blockquote><p>
+These forms are (as the warning says) LaTeX 2.09 syntax, and to get rid
+of the warning, you must change the command.
+<p/>The simple form is easy to deal with:
+<blockquote>
+  <code>\</code><code>documentstyle{article}</code>
+</blockquote><p>
+should become:
+<blockquote>
+  <code>\</code><code>documentclass{article}</code>
+</blockquote><p>
+The complex form is more difficult, since LaTeX 2.09 &ldquo;options&rdquo;
+conflate two sorts of things &mdash; options for the class (such as
+<code>11pt</code>, <code>fleqn</code>), and packages to be loaded.
+So:
+<blockquote>
+  <code>\</code><code>documentstyle[11pt,verbatim]{article}</code>
+</blockquote><p>
+should become:
+<blockquote>
+  <code>\</code><code>documentclass[11pt]{article}</code><br>
+  <code>\</code><code>usepackage{verbatim}</code>
+</blockquote><p>
+because <code>11pt</code> happens to be a class option, while
+<i>verbatim</i> is a package.
+<p/>There&rsquo;s no simple way to work out what are class options under
+LaTeX 2.09; for <i>article</i>, the list includes <code>10pt</code>,
+<code>11pt</code>, <code>12pt</code>, <code>draft</code>,
+<code>fleqn</code>, <code>leqno</code>, <code>twocolumn</code> and
+<code>twoside</code> &mdash; anything else must be a package.
+<p/>Your document may well &ldquo;just work&rdquo; after changes like those above;
+if not, you should think through what you&rsquo;re trying to do, and consult
+documentation on how to do it &mdash; there are lots of 
+<a href="FAQ-tutorialstar.html">free tutorials</a> to help you on your way, if you
+don&rsquo;t have access to a LaTeX manual of any sort.
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html
new file mode 100644
index 00000000000..0804dc1c7ea
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html
@@ -0,0 +1,89 @@
+<head>
+<title>UK TeX FAQ -- question label enumerate</title>
+</head><body>
+<h3>Fancy enumeration lists</h3>
+<p/>The <i>enumerate</i> package allows you to control the display of
+the enumeration counter.  The package adds an optional parameter to
+the <code>enumerate</code> environment, which is used to specify the
+layout of the labels.  The layout parameter contains an enumeration
+type (&lsquo;<code>1</code>&rsquo; for arabic numerals, &lsquo;<code>a</code>&rsquo; or &lsquo;<code>A</code>&rsquo;
+for alphabetic enumeration, and &lsquo;<code>i</code>&rsquo; or &lsquo;<code>I</code>&rsquo; for Roman
+numerals), and things to act as decoration of the enumeration.  So,
+for example
+<blockquote>
+<pre>
+\usepackage{enumerate}
+...
+\begin{enumerate}[(a)]
+\item ...  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+starts a list whose labels run (a), (b), (c), ...; while
+<blockquote>
+<pre>
+\usepackage{enumerate}
+...
+\begin{enumerate}[I/]
+\item ...  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+starts a list whose labels run I/, II/, III/, ...
+<p/>The <i>paralist</i> package, whose primary purpose is 
+<a href="FAQ-complist.html">compaction of lists</a>, provides the same facilities
+for its <code>enumerate</code>-like environments.
+<p/>If you need non-stereotyped designs, the <i>enumitem</i> package
+gives you most of the flexibility you might want to design your own.
+The silly roman example above could be achieved by:
+<blockquote>
+<pre>
+\usepackage{enumitem}
+...
+\begin{enumerate}[label=\Roman{*}/]
+\item ...  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+Note that the &lsquo;<code>*</code>&rsquo; in the key value stands for the list
+counter at this level.  You can also manipulate the format of
+references to list item labels:
+<blockquote>
+
+<pre>
+\usepackage{enumitem}
+...
+\begin{enumerate}[label=\Roman{*}/, ref=(\roman{*})]
+\item ...  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+to make references to the list items format appear as (i), (ii),
+(iii), etc.
+<p/>The <i>memoir</i> class includes functions that match those in the
+<i>enumerate</i> package, and has similar functionality for
+<code>itemize</code> lists.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<dl>
+<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>paralist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html
new file mode 100644
index 00000000000..30224225c79
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label epigraph</title>
+</head><body>
+<h3>Typesetting epigraphs</h3>
+<p/>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 TeXbook).
+<p/>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 &ldquo;big&rdquo; classes
+(<i>memoir</i> and <i>koma-script</i>.
+<p/>The <i>epigraph</i> package defines an <code>\</code><code>epigraph</code> command, for
+creating a single 
+epigraph (as at the top of a chapter):
+<blockquote>
+<pre>
+\chapter{The Social Life of Rabbits}
+\epigraph{Oh!  My ears and whiskers!}%
+         {Lewis Carroll}
+</pre>
+</blockquote><p>
+and an epigraphs environment, for entering more than one epigraph
+consecutively, in a sort of list introduced by <code>\</code><code>qitem</code> commands:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+The <code>\</code><code>epigraphhead</code> command enables you to place your epigraph
+<em>above</em> a chapter header:
+<blockquote>
+<pre>
+\setlength{\unitlength}{1pt}
+...
+\chapter{The Social Life of Rabbits}
+\epigraphhead[&lt;distance&gt;]{%
+  \epigraph{Oh!  My ears and whiskers!}%
+           {Lewis Carroll}%
+}
+</pre>
+</blockquote><p>
+The &lt;<i>distance</i>&gt; says how far above the chapter heading the
+epigraph is to go; it&rsquo;s expressed in terms of the <code>\</code><code>unitlength</code>
+that&rsquo;s used in the <code>picture</code> environment; the package&rsquo;s
+author recommends <code>70pt</code>.
+<p/>The package also offers various tricks for adjusting the layout of
+chapter header (necessary if you&rsquo;ve found a hugely long quotation for
+an <code>\</code><code>epigraphhead</code>), for patching the bibliography, for patching
+<code>\</code><code>part</code> pages, and so on.  (Some of these suggested patches lead you
+through writing your own package...)
+<p/>The <i>quotchap</i> package redefines chapter headings (in a
+moderately striking way), and provides an environment
+<code>savequotes</code> in which you can provide one (or more)
+quotations to use as epigraphs.  The facilities seem not as flexible
+as those of <i>epigraph</i>, but it&rsquo;s probably easier to use.
+<p/>The <i>memoir</i> class offers all the facilities of the
+<i>epigraph</i> package.  The <i>Koma-script</i> classes have
+commands <code>\</code><code>setchapterpreamble</code> and <code>\</code><code>dictum</code> to provide these
+facilities.
+<dl>
+<dt><tt><i>epigraph.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/epigraph.zip">macros/latex/contrib/epigraph</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/epigraph.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/epigraph/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>quotchap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.zip">macros/latex/contrib/quotchap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/quotchap/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html
new file mode 100644
index 00000000000..de3f766ac42
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label eplain</title>
+</head><body>
+<h3>What is Eplain?</h3>
+<p/>The <a href="http://tug.org/eplain">Eplain</a>
+macro package expands on and extends the definitions in Plain TeX.
+Eplain is not intended to provide &ldquo;generic typesetting
+capabilities&rdquo;, as do LaTeX or <a href="FAQ-texinfo.html">Texinfo</a>.  Instead, it
+defines macro tools that should be useful whatever commands you choose
+to use when you prepare your manuscript.
+<p/>For example, Eplain does not have a command <code>\</code><code>section</code>,
+which would format section headings in an &ldquo;appropriate&rdquo; way, as
+LaTeX&rsquo;s <code>\</code><code>section</code> does.  The philosophy of Eplain is that
+some people will always need or want to go beyond the macro designer&rsquo;s
+idea of &ldquo;appropriate&rdquo;.  Such canned macros are fine &mdash; as long as you
+are willing to accept the resulting output.  If you don&rsquo;t like the
+results, or if you are trying to match a different format, you are out
+of luck.
+<p/>On the other hand, almost everyone would like capabilities such as
+cross-referencing by labels, so that you don&rsquo;t have to put actual page
+numbers in the manuscript.  The authors of Eplain are not aware of
+any generally available macro packages that do not force their
+typographic style on an author, and yet provide such capabilities.
+<p/>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).
+<p/>Several LaTeX packages provide capabilities which Plain TeX
+users are lacking, most notably text colouring and rotation provided by
+the <i>graphics</i> bundle (packages <i>color</i> and
+<i>graphics</i>).  Although the <i>graphics</i> bundle provides
+a Plain TeX &ldquo;loader&rdquo; for some of the packages, it is not a
+trivial job to pass options to those packages under Plain TeX, 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:  <i>graphics</i>, <i>graphicx</i>,
+<i>color</i>, <i>autopict</i> (LaTeX picture environment),
+<i>psfrag</i>, and <i>url</i>.
+<p/><a href="http://tug.org/docs/html/eplain">Eplain documentation</a> is
+available online, and there&rsquo;s
+also a mailing list &mdash; sign up, or browse the list archives, via
+<a href="http://tug.org/mailman/listinfo/tex-eplain">http://tug.org/mailman/listinfo/tex-eplain</a>
+<dl>
+<dt><tt><i>Eplain distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html
new file mode 100644
index 00000000000..ae5d45c197a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label eps</title>
+</head><body>
+<h3>What is &ldquo;Encapsulated PostScript&rdquo; (&ldquo;EPS&rdquo;)</h3>
+<p/>PostScript has been for many years a <em>lingua franca</em> of powerful
+printers (modern high-quality printers now tend to require some
+constrained form of Adobe Acrobat, instead); since PostScript is also a
+powerful graphical programming language, it is commonly used as an
+output medium for drawing (and other) packages.
+<p/>However, since PostScript <em>is</em> 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 &ldquo;leaking&rdquo; (and thereby destroying
+the surrounding document, or failing to draw at all).
+<p/>Appendix H of the PostScript Language Reference Manual (second
+and subsequent editions), specifies a set of rules for PostScript to
+be used as figures in this way.  The important features are:
+<ul>
+<li> certain &ldquo;structured comments&rdquo; are required; important ones are
+  the identification of the file type, and information about the
+  &ldquo;bounding box&rdquo; of the figure (i.e., the minimum rectangle
+  enclosing it);
+<li> some commands are forbidden &mdash; for example, a <code>showpage</code>
+  command will cause the image to disappear, in most TeX-output
+  environments; and
+<li> &ldquo;preview information&rdquo; is permitted, for the benefit of things
+  such as word processors that don&rsquo;t have the ability to draw
+  PostScript in their own right &mdash; this preview information may be in
+  any one of a number of system-specific formats, and any viewing
+  program may choose to ignore it.
+</ul>
+A PostScript figure that conforms to these rules is said to be in
+&ldquo;Encapsulated PostScript&rdquo; (EPS) format.  Most (La)TeX packages for
+including PostScript are structured to use Encapsulated PostScript;
+which of course leads to much hilarity as exasperated (La)TeX users
+struggle to cope with the output of drawing software whose authors
+don&rsquo;t know the rules.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html
new file mode 100644
index 00000000000..10eab64cd9b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label epsf</title>
+</head><body>
+<h3><code>epsf</code> gives up after a bit</h3>
+<p/>Some copies of the documentation of <i>epsf.tex</i> seem to suggest
+that the command
+<pre>
+  \input epsf
+</pre>
+is needed for every figure included.  If you follow this suggestion
+too literally, you get an error
+<pre>
+  ! No room for a new \read .
+</pre>
+after a while; this is because each time <i>epsf.tex</i> is loaded, it
+allocates itself a <em>new</em> file-reading handle to check the figure
+for its bounding box, and there just aren&rsquo;t enough of these things
+(see <a href="FAQ-noroom.html">no room for a new thing</a>).
+<p/>The solution is simple &mdash; this is in fact an example of misuse of
+macros; one only need read <i>epsf.tex</i> once, so change
+<pre>
+  ...
+  \input epsf
+  \epsffile{...}
+  ...
+  \input epsf
+  \epsffile{...}
+</pre>
+(and so on) with a single
+<pre>
+  \input epsf
+</pre>
+somewhere near the start of your document, and then decorate your
+<code>\</code><code>epsffile</code> statements with no more than adjustments of
+<code>\</code><code>epsfxsize</code> and so on.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html
new file mode 100644
index 00000000000..8e023a4e0e0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label eqnarray</title>
+</head><body>
+<h3>Why not use <code>eqnarray</code>?</h3>
+<p/>The environment <code>eqnarray</code> is attractive for the
+occasional user of mathematics in LaTeX documents: it seems to
+allow aligned systems of equations.  Indeed it <em>does</em> supply such
+things, but it makes a serious mess of spacing.  In the system:
+<blockquote>
+<pre>
+\begin{eqnarray}
+  a & = & b + c \\
+  x & = & y - z
+\end{eqnarray}
+</pre>
+</blockquote><p>
+the spacing around the &ldquo;=&rdquo; signs is <em>not</em> that defined in the
+metrics for the font from which the glyph comes &mdash; it&rsquo;s
+<code>\</code><code>arraycolsep</code>, which may be set to some very odd value for reasons
+associated with real arrays elsewhere in the document.
+<p/>The user is far better served by the AMSLaTeX bundle, which
+provides an <code>align</code> environment, which is designed with
+the needs of mathematicians in mind (as opposed to the convenience of
+LaTeX programmers).  For this simple case (align is capable of far
+greater things), code as:
+<blockquote>
+<pre>
+\begin{align}
+  a & = b + c \\
+  x & = y - z
+\end{align}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>AMSLaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html
new file mode 100644
index 00000000000..b893df4e722
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html
@@ -0,0 +1,127 @@
+<head>
+<title>UK TeX FAQ -- question label errmissitem</title>
+</head><body>
+<h3>Perhaps a missing <code>\</code><code>item</code>?</h3>
+<p/>Sometimes, the error
+<blockquote>
+<pre>
+Something's wrong--perhaps a missing \item
+</pre>
+</blockquote><p>
+actually means what it says:
+<blockquote>
+<pre>
+\begin{itemize}
+  boo!
+\end{itemize}
+</pre>
+</blockquote><p>
+produces the error, and is plainly in need of an <code>\</code><code>item</code> command.
+<p/>You can also have the error appear when at first sight things are
+correct:
+<blockquote>
+<pre>
+\begin{tabular}{l}
+  \begin{enumerate}
+  \item foo\\
+  \item bar
+  \end{enumerate}
+\end{tabular}
+</pre>
+</blockquote><p>
+produces the error at the <code>\\</code>.  This usage is just wrong; if you
+want to number the cells in a table, you have to do it &ldquo;by hand&rdquo;:
+<blockquote>
+<pre>
+\newcounter{tablecell}
+\begin{tabular}{l}
+  \stepcounter{tablecell}
+  \thetablecell. foo\\
+  \stepcounter{tablecell}
+  \thetablecell. bar
+  \end{enumerate}
+\end{tabular}
+</pre>
+</blockquote><p>
+This is obviously untidy; a command <code>\</code><code>numbercell</code> defined as:
+<blockquote>
+<pre>
+\newcounter{tablecell}
+\newcommand*{\numbercell}{%
+  \stepcounter{tablecell}%
+  \thetablecell. % **
+}
+</pre>
+</blockquote><p>
+could make life easier:
+<blockquote>
+<pre>
+\begin{tabular}{l}
+  \numbercell foo\\
+  \numbercell bar
+  \end{enumerate}
+\end{tabular}
+</pre>
+</blockquote><p>
+(Note the deliberate introduction of a space as part of the command,
+marked with asterisks.)
+<p/>However, the error regularly appears when you would never have thought
+that a <code>\</code><code>item</code> command  might be appropriate.  For example, the
+seemingly innocent:
+<blockquote>
+<pre>
+\fbox{%
+  \begin{alltt}
+    boo!
+  \end{alltt}%
+}
+</pre>
+</blockquote><p>
+produces the error (the same happens with <code>\</code><code>mbox</code> in place of
+<code>\</code><code>fbox</code>, or with either of their &ldquo;big brothers&rdquo;, <code>\</code><code>framebox</code> and
+<code>\</code><code>makebox</code>).  This is because the <code>alltt</code> environment
+uses a &ldquo;trivial&rdquo; list, hidden inside their definition.  (The
+<code>itemize</code> environment also has this construct inside
+itself, in fact, so <code>\</code><code>begin{itemize}</code> won&rsquo;t work inside an
+<code>\</code><code>fbox</code>, either.)  The list construct wants to happen between
+paragraphs, so it makes a new paragraph of its own.  Inside the
+<code>\</code><code>fbox</code> command, that doesn&rsquo;t work, and subsequent macros convince
+themselves that there&rsquo;s a missing <code>\</code><code>item</code> command.
+<p/>To solve this rather cryptic error, one must put the
+<code>alltt</code> inside a paragraph-style box.  The following
+modification of the above <em>does</em> work:
+<blockquote>
+<pre>
+\fbox{%
+  \begin{minipage}{0.75\textwidth}
+    \begin{alltt}
+      hi, there!
+    \end{alltt}
+  \end{minipage}
+}
+</pre>
+</blockquote><p>
+The code above produces a box that&rsquo;s far too wide for the text.  One
+may want to use something that allows 
+<a href="FAQ-varwidth.html">variable size boxes</a> in place of the
+<code>minipage</code> environment.
+<p/>Oddly, although the <code>verbatim</code> environment wouldn&rsquo;t work
+inside a <code>\</code><code>fbox</code> command argument (see 
+<a href="FAQ-verbwithin.html">verbatim in command arguments</a>), you
+get an error that complains about <code>\</code><code>item</code>: the environment&rsquo;s
+internal list bites you before <code>verbatim</code> has even had a
+chance to create its own sort of chaos.
+<p/>Another (seemingly) obvious use of <code>\</code><code>fbox</code> also falls foul of this
+error:
+<blockquote>
+<pre>
+\fbox{\section{Boxy section}}
+</pre>
+</blockquote><p>
+This is a case where you&rsquo;ve simply got to be more subtle; you should
+either write your own macros to replace the insides of LaTeX&rsquo;s
+sectioning macros, or  look for some alternative in the packages
+discussed in 
+&ldquo;<a href="FAQ-secthead.html">The style of section headings</a>&rdquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html
new file mode 100644
index 00000000000..52223c34168
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html
@@ -0,0 +1,71 @@
+<head>
+<title>UK TeX FAQ -- question label erroradvice</title>
+</head><body>
+<h3>How to approach errors</h3>
+<p/>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 TeXbook,
+suggesting that you acquire the sleuthing skills of a latter-day
+Sherlock Holmes; while this approach has a certain romantic charm to
+it, it&rsquo;s not good for the &lsquo;production&rsquo; user of (La)TeX.  This
+answer (derived, in part, from an article by Sebastian Rahtz in
+<i>TUGboat</i> 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&rsquo;s a long list of
+&ldquo;hints&rdquo; in Sebastian&rsquo;s article, including the following:
+<ul>
+<li> Look at TeX errors; those messages may seem cryptic at first,
+  but they often contain a straightforward clue to the problem.  See
+  <a href="FAQ-errstruct.html">the structure of errors</a> for further
+  details. 
+<li> Read the <code>.log</code> file; it contains hints to things you may
+  not understand, often things that have not even presented as error
+  messages.
+<li> 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 &ldquo;actually happened&rdquo;;
+  it&rsquo;s possible to control how much of this &lsquo;context&rsquo; TeX actually
+  gives you.  LaTeX (nowadays) instructs TeX only to give you
+  one line of context, but you may tell it otherwise by saying
+<blockquote>
+<pre>
+\setcounter{errorcontextlines}{999}
+</pre>
+</blockquote><p>
+  in the preamble of your document.  (If you&rsquo;re not a confident macro
+  programmer, don&rsquo;t be ashamed of cutting that 999 down a bit; some
+  errors will go on and <em>on</em>, and spotting the differences
+  between those lines can be a significant challenge.)
+<li> As a last resort, tracing can be a useful tool; reading a full
+  (La)TeX 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 TeXbook (see
+
+  <a href="FAQ-books.html">books about TeX</a>) in some detail, fully
+  to understand the trace.
+<p/>  The command <code>\</code><code>tracingall</code> 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 &mdash; all but
+  the simplest traces are best examined in a text editor after the event).
+<p/>  The LaTeX <i>trace</i> package (first distributed with the
+  2001 release of LaTeX) provides more manageable tracing.  Its
+  <code>\</code><code>traceon</code> command gives you what <code>\</code><code>tracingall</code> offers, but
+  suppresses tracing around some of the truly verbose parts of
+  LaTeX itself.  The package also provides a <code>\</code><code>traceoff</code>
+  command (there&rsquo;s no &ldquo;off&rdquo; command for <code>\</code><code>tracingall</code>), and a
+  package option (<code>logonly</code>) allows you to suppress output to the
+  terminal.
+</ul>
+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&rsquo;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 <a href="FAQ-gethelp.html">wider public</a>
+for assistance, but if you do, be sure to
+report full backtraces (see <code>errorcontextlines</code> above) and so on.
+<dl>
+<dt><tt><i>trace.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html
new file mode 100644
index 00000000000..2fc2e255709
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label errparnum</title>
+</head><body>
+<h3>Illegal parameter number in definition</h3>
+<p/>The error message means what it says.  In the simple case, you&rsquo;ve
+attempted a definition like:
+<blockquote>
+<pre>
+\newcommand{\abc}{joy, oh #1!}
+</pre>
+</blockquote><p>
+or (using TeX primitive definitions):
+<blockquote>
+<pre>
+\def\abc{joy, oh #1!}
+</pre>
+</blockquote><p>
+In either of the above, the definition uses an argument, but the
+programmer did not tell (La)TeX, in advance, that she was going to.
+The fix is simple &mdash; <code>\</code><code>newcommand{<code>\</code><code>abc</code>}[1]</code>, in the
+LaTeX case, <code>\def\abc#1</code> in the basic TeX case.
+<p/>The more complicated case is exemplified by the attempted definition:
+<blockquote>
+<pre>
+\newcommand{\abc}{joy, oh joy!%
+  \newcommand{\ghi}[1]{gloom, oh #1!}%
+}
+</pre>
+</blockquote><p>
+will also produce this error, as will its TeX primitive equivalent:
+<blockquote>
+<pre>
+\def\abc{joy, oh joy!%
+  \def\ghi#1{gloom, oh #1!}%
+}
+</pre>
+</blockquote><p>
+This is because special care is needed when defining one macro within
+the code of another macro.  This is explained elsewhere, separately
+for <a href="FAQ-ltxhash.html">LaTeX definitions</a> and for
+<a href="FAQ-hash.html">TeX primitive definitions</a>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html
new file mode 100644
index 00000000000..5f29857452f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html
@@ -0,0 +1,75 @@
+<head>
+<title>UK TeX FAQ -- question label errstruct</title>
+</head><body>
+<h3>The structure of TeX error messages</h3>
+<p/>TeX&rsquo;s error messages are reminiscent of the time when TeX itself
+was conceived (the 1970s): they&rsquo;re not terribly user-friendly, though
+they do contain all the information that TeX can offer, usually in
+a pretty concise way.
+<p/>TeX&rsquo;s error reports all have the same structure:
+<ul>
+<li> An error message
+<li> Some &lsquo;context&rsquo;
+<li> An error prompt
+</ul>
+The error message will relate to the <em>TeX</em> 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 &ldquo;higher-level&rdquo;
+macros.  Many LaTeX-detected problems manifest themselves as
+&lsquo;generic&rsquo; errors, with error text provided by LaTeX itself (or by a
+LaTeX class or package).
+<p/>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
+<a href="FAQ-erroradvice.html">approaching errors</a>, 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 <em>actually</em> 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 &ldquo;point of call&rdquo;
+is after all the arguments have been scanned.)  For example:
+<pre>
+\blah and so on
+</pre>
+produces the error report
+<pre>
+! Undefined control sequence.
+l.4 \blah
+          and so on
+</pre>
+while:
+<pre>
+\newcommand{\blah}[1]{\bleah #1}
+\blah{to you}, folks
+</pre>
+produces the error report
+<pre>
+! Undefined control sequence.
+\blah #1-&gt;\bleah 
+                 #1
+l.5 \blah{to you}
+                 , folks
+</pre>
+If the argument itself is in error, we will see things such as
+<pre>
+\newcommand{\blah}[1]{#1 to you}
+\blah{\bleah}, folks
+</pre>
+producing
+<pre>
+! Undefined control sequence.
+&lt;argument&gt; \bleah 
+                  
+l.5 \blah{\bleah}
+                 , folks
+</pre>
+<p/>The prompt accepts single-character commands: the list of what&rsquo;s
+available may be had by typing <code>?</code>.  One immediately valuable
+command is <code>h</code>, which gives you an expansion of TeXs original
+pr&eacute;cis message, sometimes accompanied by a hint on what to do to
+work round the problem in the short term.  If you simply type &lsquo;return&rsquo;
+(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).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html
new file mode 100644
index 00000000000..cc73f99bb87
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label etex</title>
+</head><body>
+<h3>What is e-TeX?</h3>
+<p/>While Knuth has declared that TeX will never 
+<a href="FAQ-TeXfuture.html">change in any substantial way</a>, there remain
+things that one might wish had been done differently, or indeed
+implemented at all.
+<p/>The NTS project set out to produce an advanced replacement for
+TeX, to provide a basis for developing such modifications: this
+&ldquo;New Typesetting System&rdquo; would share Knuth&rsquo;s aims, but would
+implement the work in a modern way taking account of the lessons
+learned with TeX.  While a first demonstrator NTS did
+appear, it wasn&rsquo;t practically useful, and the project seems no longer
+active.
+<p/>In parallel with its work on NTS itself, the project developed
+a set of extensions that can be used with a (&ldquo;true&rdquo;) TeX system.
+Such a modified system is known as an e-TeX system, and the concept
+has proved widely successful.  Indeed, current TeX distributions
+are delivered with most formats built with an e-TeX-based system (for
+those who don&rsquo;t want them, e-TeX&rsquo;s extensions can be disabled, leaving
+a functionally standard TeX system).
+<p/>The extensions range from the seemingly simple (increasing the number
+of available registers from 256 to 32768) through to extremely subtle
+programming support.
+<p/><a href="FAQ-context.html">ConTeXt</a> has required e-TeX for its operation
+for some time.
+<p/>Some LaTeX packages already specify the use of e-TeX.  Some such
+packages may not work at all on a non-e-TeX system; others will
+work, but not as well as on an e-TeX system.  The 
+<a href="FAQ-LaTeX3.html">LaTeX team</a> has announced that future LaTeX
+packages (specifically those from the team, as opposed to those
+individually contributed) may require e-TeX for optimum performance.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html
new file mode 100644
index 00000000000..353ecc6f12f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label euro</title>
+</head><body>
+<h3>Typesetting the Euro sign</h3>
+<p/>The European currency &ldquo;Euro&rdquo; is represented by a symbol of somewhat
+dubious design, but it&rsquo;s an important currency and (La)TeX users
+need to typeset it.
+<p/>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
+&ldquo;respectable&rdquo; (typographically).
+<p/>The TS1-encoded TC fonts provided as part of the EC font
+distribution provide Euro glyphs.  The fonts are called Text Companion
+(TC) fonts, and offer the same range
+of faces as do the EC fonts themselves.  The
+<i>textcomp</i> package provides a <code>\</code><code>texteuro</code> command for
+accessing the symbol, which selects a symbol to match the surrounding
+text.  The design of the symbol in the TC fonts is not
+universally loved...
+Nevertheless, use the TC font version of the symbol if you are
+producing documents using Knuth&rsquo;s Computer Modern Fonts.
+<p/>The <i>latin9</i> input encoding defined by the <i>inputenc</i>
+package has a euro character defined (character position 164, occupied
+in other ISO Latin character sets by the &ldquo;currency symbol&rdquo;).
+The encoding uses the command <code>\</code><code>texteuro</code> for the character; at
+present that command is <em>only</em> available from the
+<i>textcomp</i> package.  There is a Microsoft code page position,
+too, but standardisation of such things proceeds via rather different
+routes and the LaTeX project hasn&rsquo;t yet been given details of the
+change.
+<p/>Outline fonts which contain nothing but Euro symbols are available
+(free) from
+<a href="ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe">Adobe</a> &mdash;
+the file is packaged as a <i>Windows</i> self-extracting
+executable, but it may be decoded as a <code>.zip</code> format archive
+on other operating systems.
+The <i>euro</i> bundle contains metrics, <i>dvips</i> map
+files, and macros (for Plain TeX and LaTeX), for using these
+fonts in documents.  LaTeX users will find two packages in the
+bundle: <i>eurosans</i> only offers the sans-serif version (to
+conform with the obsolete ruling about sans-serif-only symbols; the
+package provides the
+command <code>\</code><code>euro</code>), whereas <i>europs</i> matches the Euro symbol
+with the surrounding text (providing the command <code>\</code><code>EUR</code>).  To use
+either package
+with the <i>latin9</i> encoding, you need to define <code>\</code><code>texteuro</code>
+as an alias for the euro command the package defines.
+<p/>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.
+<p/>The <i>eurofont</i> package provides a compendious analysis of the
+&ldquo;problem of the euro symbol&rdquo; in its documentation, and offers macros
+for configuring the source of the glyphs to be used; however, it seems
+rather large for everyday use.
+<p/>The <i>euro-ce</i> bundle is a rather pleasing Metafont-only design
+providing Euro symbols in a number of shapes.  The file
+<i>euro-ce.tex</i>, in the distribution, offers hints as to how a
+Plain TeX user might make use of the fonts.
+<p/>Euro symbols are found in several other places, which we list here for
+completeness.
+<p/>The <i>marvosym</i> fonts contain a Euro symbol among many other
+good things.
+
+
+
+
+
+<p/>Other Metafont-based bundles containing Euro symbols are to be found in
+<i>china2e</i> (whose primary aim is Chinese dates and suchlike
+matters) and the <i>eurosym</i> fonts.
+<dl>
+<dt><tt><i>china2e bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/china2e.zip">macros/latex/contrib/china2e</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/china2e.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/china2e/">browse</a>)
+<dt><tt><i>EC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ec.zip">fonts/ec</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ec/">browse</a>)
+<dt><tt><i>euro fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/euro.zip">fonts/euro</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/euro.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/euro/">browse</a>)
+<dt><tt><i>euro-ce fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/euro-ce.zip">fonts/euro-ce</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/euro-ce.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/euro-ce/">browse</a>)
+<dt><tt><i>eurofont.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eurofont.zip">macros/latex/contrib/eurofont</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eurofont.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eurofont/">browse</a>)
+<dt><tt><i>eurosym fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/eurosym.zip">fonts/eurosym</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/eurosym.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/eurosym/">browse</a>)
+<dt><tt><i>marvosym fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/marvosym.zip">fonts/psfonts/marvosym</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/marvosym.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/psfonts/marvosym/">browse</a>)
+<dt><tt><i>textcomp.sty</i></tt><dd>Part of the LaTeX distribution.
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html
new file mode 100644
index 00000000000..fb1431f03c4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label exscale</title>
+</head><body>
+<h3>Maths symbols don&rsquo;t scale up</h3>
+<p/>By default, the &ldquo;large&rdquo; maths symbols stay at the same size
+regardless of the font size of the text of the document.  There&rsquo;s good
+reason for this: the <i>cmex</i> fonts aren&rsquo;t really designed to
+scale, so that TeX&rsquo;s maths placement algorithms don&rsquo;t perform as
+well as they might when the fonts are scaled.
+<p/>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 <i>exscale</i> package &mdash; just
+loading it is enough.
+
+
+
+
+<dl>
+<dt><tt><i>exscale.sty</i></tt><dd>Part of the LaTeX distribution.
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html
new file mode 100644
index 00000000000..79c17ffe680
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label extex</title>
+</head><body>
+<h3>The ExTeX project</h3>
+<p/><a href="http://www.extex.org/">The ExTeX project</a> 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 <i>NTS</i> project).
+<p/>While ExTeX will implement all of TeX&rsquo;s primitives, some may be
+marked as obsolete, and &ldquo;modern&rdquo; alternatives provided (an obvious
+example is the primitive <code>\</code><code>input</code> command, whose syntax inevitably
+makes life difficult for users of modern operating system file
+paths).  Desirable extensions from <a href="FAQ-etex.html">e-TeX</a>,
+<a href="FAQ-whatpdftex.html">PDFTeX</a> and <a href="FAQ-omegaleph.html">Omega</a>
+have been identified.
+<p/>Usability will be another focus of the work: debugging support and log
+filtering mechanisms will please those who have long struggled with
+TeX macros.
+<p/>ExTeX will accept Unicode input, from the start.  In the longer
+term, drawing primitives are to be considered.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html
new file mode 100644
index 00000000000..1f68cf4bd74
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label extrabrace</title>
+</head><body>
+<h3>An extra &lsquo;<code>}</code>&rsquo;??</h3>
+<!-- caption heading -->
+<p/>You&rsquo;ve looked at your LaTeX source and there&rsquo;s no sign of a misplaced
+<code>}</code> on the line in question.
+<p/>Well, no: this is TeX&rsquo;s cryptic way of hinting that you&rsquo;ve put a
+<a href="FAQ-protect.html">fragile command</a> in a moving argument.
+
+<p/>For example, <code>\</code><code>footnote</code> is fragile, and if we put that in the
+moving argument of a <code>\</code><code>section</code> command, as
+<blockquote>
+
+<pre>
+\section{Mumble\footnote{I couldn't think of anything better}}
+</pre>
+</blockquote><p>
+we get told
+<blockquote>
+<pre>
+! Argument of \@sect has an extra }.
+</pre>
+</blockquote><p>
+The same happens with captions (the following is a simplification of a
+<i>comp.text.tex</i> post):
+<blockquote>
+<pre>
+\caption{Energy: \[e=mc^2\]}
+</pre>
+</blockquote><p>
+giving us the error message
+<blockquote>
+<pre>
+! Argument of \@caption has an extra }.
+</pre>
+</blockquote><p>
+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 <code>\</code><code>protect</code>, which in the <code>\</code><code>section</code> case would show as
+<blockquote>
+
+<pre>
+\section{Mumble\protect\footnote{I couldn't think of anything better}}
+</pre>
+</blockquote><p>
+In both the <code>\</code><code>section</code> case and the <code>\</code><code>caption</code> case, you can
+separate the moving argument, as in
+<code>\</code><code>section[</code><em>moving</em><code>]{</code><em>static</em><code>}</code>; this gives us another standard
+route &mdash; simply to omit (or otherwise sanitise) the fragile command
+in the moving argument.  So, one might rewrite the <code>\</code><code>caption</code>
+example as:
+<blockquote>
+
+<pre>
+\caption[Energy:  $E=mc^2$]{Energy: \[E=mc^2\]}
+</pre>
+</blockquote><p>
+for, after all, even if you want display maths in a caption, you
+surely don&rsquo;t want it in the list of figures.
+<p/>The case of footnotes is somewhat more complex;
+&ldquo;<a href="FAQ-ftnsect.html">footnotes in LaTeX section headings</a>&rdquo;
+deals specifically with that issue.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html
new file mode 100644
index 00000000000..c38d4bf0af9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label extref</title>
+</head><body>
+<h3>Referring to labels in other documents</h3>
+<p/>When producing a set of inter-related documents, you&rsquo;ll often want to
+refer to labels in another document of the set; but LaTeX, of its
+own accord, doesn&rsquo;t permit this.
+<p/>So the package <i>xr</i> was written: if you say
+<blockquote>
+<pre>
+\usepackage{xr}
+\externaldocument{volume1}
+</pre>
+</blockquote><p>
+will load all the references from <i>volume1</i> into your present
+document.
+<p/>But what if the documents both have a section labelled
+&ldquo;<code>introduction</code>&rdquo; (likely enough, after all)?  The
+package provides a means to transform all the imported labels, so you
+don&rsquo;t have to change label names in either document.  For example:
+<blockquote>
+<pre>
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+</pre>
+</blockquote><p>
+loads the references from <i>volume1</i>, but prefixes every one with
+the string <code>V1-</code>.  So you would refer to the introduction to volume 1
+as:
+
+<blockquote>
+<pre>
+\usepackage{xr}
+\externaldocument[V1-]{volume1}
+...
+... the introduction to volume1 (\ref{V1-introduction})...
+</pre>
+</blockquote><p>
+To have the facilities of <i>xr</i> working with
+<i>hyperref</i>, you need <i>xr-hyper</i>.  For simple
+hyper-cross-referencing (i.e., to a local PDF file you&rsquo;ve just
+compiled), write:
+<blockquote>
+<pre>
+\usepackage{xr-hyper}
+\usepackage{hyperref}
+\externaldocument[V1-]{volume1}
+...
+... the \nameref{V1-introduction})...
+</pre>
+</blockquote><p>
+and the name reference will appear as an active link to the
+&ldquo;introduction&rdquo; chapter of <i>volume1.pdf</i>.
+<p/>To link to a PDF document on the Web, for which you happen to
+have the .aux file, write:
+<blockquote>
+<pre>
+\usepackage{xr-hyper}
+\usepackage{hyperref}
+\externaldocument[V1-]{volume1}[http://mybook.com/volume1.pdf]
+...
+... the \nameref{V1-introduction})...
+</pre>
+
+</blockquote><p>
+<dl>
+<dt><tt><i>xr.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>xr-hyper.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html
new file mode 100644
index 00000000000..20f9d86dafe
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html
@@ -0,0 +1,29 @@
+<head>
+<title>UK TeX FAQ -- question label extsizes</title>
+</head><body>
+<h3>Other &ldquo;document font&rdquo; sizes?</h3>
+<p/>The LaTeX standard classes have a concept of a (base) &ldquo;document
+font&rdquo; size; this size is the basis on which other font sizes (those
+from <code>\</code><code>tiny</code> to <code>\</code><code>Huge</code>) are determined.  The classes are designed
+on the assumption that they won&rsquo;t be used with sizes other than the
+set that LaTeX offers by default (10&ndash;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&rsquo;t
+fancy doing that.
+<p/>A simple solution is to use the <i>extsizes</i> bundle.  This
+bundle offers &ldquo;extended&rdquo; versions of the article, report, book and
+letter classes, at sizes of 8, 9, 14, 17 and 20pt as well as the
+standard 10&ndash;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 &mdash; but they&rsquo;re certainly practical.
+<p/>More satisfactory are the <em>KOMA-script</em> classes, which are
+designed to work properly with the class option files that come with
+<i>extsizes</i>, and the <i>memoir</i> class that has its own
+options for document font sizes 9pt, 14pt and 17pt.
+<dl>
+<dt><tt><i>extsizes bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extsizes.zip">macros/latex/contrib/extsizes</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extsizes.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extsizes/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html
new file mode 100644
index 00000000000..a07ae879e1d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label fancyhdr</title>
+</head><body>
+<h3>Alternative head- and footlines in LaTeX</h3>
+<p/>The standard LaTeX document classes define a small set of &lsquo;page
+styles&rsquo; 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&rsquo;s no need &mdash; there are packages that provide
+useful abstractions that match the way we typically think about these
+things.
+<p/>The <i>fancyhdr</i> 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.  <i>Fancyhdr</i> 
+also deals with the tedious behaviour of the standard styles with
+<a href="FAQ-psatempty.html">initial pages</a>, by enabling you to define
+different page styles for initial and for body pages.
+<p/>While <i>fancyhdr</i> will work with <i>KOMA-script</i> classes,
+an alternative package, <i>scrpage2</i>, eases integration with the
+classes.  <i>Scrpage2</i> may also be used as a <i>fancyhdr</i>
+replacement, providing similar facilities.  The <i>KOMA-script</i>
+classes themselves permit some modest redefinition of head- and
+footlines, without the use of the extra package.
+<p/><i>Memoir</i> also contains the functionality of <i>fancyhdr</i>,
+and has several predefined styles.
+<p/>Documentation of <i>fancyhdr</i> is distributed with the package,
+in a separate file; documentation of <i>scrpage2</i> is integrated
+with the <i>scrgui*</i> documentation files that are distributed with
+the <i>KOMA-script</i> classes.
+<dl>
+<dt><tt><i>fancyhdr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fig.html
new file mode 100644
index 00000000000..8573b218546
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fig.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label fig</title>
+</head><body>
+<h3>Fig, a (La)TeX-friendly drawing package</h3>
+<p/><i>(X)Fig</i> is a menu driven tool that allows you to
+draw objects on the screen of an X workstation; <i>transfig</i>
+is a set of tools which translate the code <i>fig</i>.  The list
+of export formats is very long, and includes Metafont and MetaPost,
+Encapsulated PostScript and PDF, as well as combinations that wrap
+a graphics format in a LaTeX import file.
+<p/>There&rsquo;s no explicit port of <i>xfig</i> to windows (although it is
+believed to work under <i>cygwin</i> with their X-windows system).
+However, the program 
+<a href="http://tech-www.informatik.uni-hamburg.de/applets/javafig/"><i>jfig</a></i>
+is thought by many to be an acceptable substitute, written in Java.
+<dl>
+<dt><tt><i>xfig</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/xfig.zip">graphics/xfig</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/xfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/xfig/">browse</a>)
+<dt><tt><i>transfig</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/transfig.zip">graphics/transfig</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/transfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/transfig/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html
new file mode 100644
index 00000000000..e5b38703e2e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label figurehere</title>
+</head><body>
+<h3>Figure (or table) <em>exactly</em> where I want it</h3>
+<p/>This is of course a contradiction: <code>figure</code> and
+<code>table</code> are <em>designed</em> to float, and will always have
+the potential to appear away from where you asked for them.  Therefore
+you have to find a means of getting the caption and other effects
+without allowing the figure or table to float.
+<p/>The most straightforward way is to use the <i>float</i> package; it
+gives you a <code>[H]</code> float placement option that prevents
+floating:
+<blockquote>
+<pre>
+\begin{figure}[H]
+  \centering
+  \includegraphics{foo}
+  \caption{caption text}
+  \label{fig:nonfloat}
+\end{figure}
+</pre>
+</blockquote><p>
+As the example shows, these <code>[H]</code> figures (and correspondingly,
+tables) offer all you need to cross-reference as well as typeset.
+<p/>However, you don&rsquo;t actually <em>have</em> to use <i>float</i> since
+it is, in fact, doing rather little for you.  You can place your
+figure as you please, with a sequence like
+<blockquote>
+<pre>
+\begin{center}
+  \includegraphics{foo}
+  \captionof{figure}{caption text}
+  \label{fig:nonfloat}
+\end{center}
+</pre>
+</blockquote><p>
+which relies on the <code>\</code><code>captionof</code> command to place a caption in
+ordinary running text.  That command may be had from the extremely
+simple-minded package <i>capt-of</i> or from the highly
+sophisticated <i>caption</i> package.
+<p/>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; &ldquo;doing it by hand&rdquo;, like this, you
+take upon yourself the responsibility for avoiding 
+&lsquo;<i>Overfull <code>\</code><code>vbox</code></i>&rsquo; errors.
+<p/>A further problem is the possibility that such &ldquo;fixed floats&rdquo; will
+overtake &ldquo;real floats&rdquo;, 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&rsquo;s best, therefore, either to stay with floating figures
+throughout a document, or to use fixed figures throughout.
+<dl>
+<dt><tt><i>capt-of.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/capt-of.sty">macros/latex/contrib/misc/capt-of.sty</a>
+<dt><tt><i>caption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.zip">macros/latex/contrib/caption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/caption/">browse</a>)
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html
new file mode 100644
index 00000000000..3937df6fbcc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html
@@ -0,0 +1,94 @@
+<head>
+<title>UK TeX FAQ -- question label filename</title>
+</head><body>
+<h3>What&rsquo;s the name of this file</h3>
+<p/>One might want this so as to automatically generate a page header or
+footer recording what file is being processed.  It&rsquo;s not easy...
+<p/>TeX retains what it considers the name of the <em>job</em>, only, in
+the primitive <code>\</code><code>jobname</code>; this is the name of the file first
+handed to TeX, stripped of its directory name and of any extension
+(such as <code>.tex</code>).  If no file was passed (i.e., you&rsquo;re using
+TeX interactively), <code>\</code><code>jobname</code> has the value <code>texput</code>
+(the name that&rsquo;s given to <code>.log</code> files in this case).
+<p/>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
+<em>job</em>.  So the user has to keep track, himself &mdash; 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 Plain TeX,
+since the syntax of the <code>\</code><code>input</code> command is so peculiar.
+<p/>In the case of LaTeX, the input commands have pretty regular
+syntax, and the simplest <a href="FAQ-patch.html">patching techniques</a> can be
+used on them.
+<p/>If you&rsquo;re not inputting things from a file that&rsquo;s already been input,
+the job is almost trivial:
+<blockquote>
+<pre>
+\def\ThisFile{\jobname}
+\let\OldInput\input
+\renewcommand{\input}[1]{%
+  \renewcommand{\ThisFile}{#1}%
+  \OldInput{#1}%
+}
+</pre>
+</blockquote><p>
+With that, the macro <code>\</code><code>ThisFile</code> always contains the last thing
+input: it starts pointing at the base file of your document
+(<code>\</code><code>jobname</code>), and thereafter changes every time you use
+<code>\</code><code>input{</code><em>file</em><code>}</code>.
+<p/>Most ordinary users will quickly become irritated with the simplicity
+of of the <code>\</code><code>ThisFile</code> mechanism above.  The following code is more
+cunning: it maintains details of the files you&rsquo;ve &lsquo;come through&rsquo; to
+get to where you are, and it restores <code>\</code><code>ThisFile</code> to what the
+previous file was before returning.
+<blockquote>
+<pre>
+\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}%
+}
+</pre>
+</blockquote><p>
+To do the same for <code>\</code><code>include</code>, we need the simple addition:
+<blockquote>
+<pre>
+\let\OrigInclude\include
+\renewcommand{\include}[1]{%
+  \stackinput{#1}{\OrigInclude}%
+}
+</pre>
+</blockquote><p>
+Both examples of patching <code>\</code><code>input</code> assume you always use
+LaTeX syntax, i.e., always use braces around the argument.
+<p/>The <i>FiNK</i> (&ldquo;File Name Keeper&rdquo;) package provides a
+regular means of keeping track of the current file name (with its
+extension), in a macro <code>\</code><code>finkfile</code>.  If you need the unadorned file
+name (without its &lsquo;<code>.tex</code>&rsquo;), use the commands:
+<blockquote>
+<pre>
+\def\striptexext#1.tex{#1}
+...
+\edef\ThisFile{\expandafter\stripext\finkfile}
+</pre>
+</blockquote><p>
+The <i>FiNK</i> bundle includes a <i>fink.el</i> that provides
+support under <i>emacs</i> with AUC-TeX.
+<dl>
+<dt><tt><i>fink.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.zip">macros/latex/contrib/fink</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fink/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html
new file mode 100644
index 00000000000..9a10f936df3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label filesused</title>
+</head><body>
+<h3>All the files used by this document</h3>
+<p/>When you&rsquo;re sharing a document with someone else (perhaps as part of a
+co-development cycle) it&rsquo;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 <i>url</i> package, she has to have <i>url</i>
+too, for example).  But suppose you have a bug-free version of the
+<i>shinynew</i> package but her copy is still the unstable
+original; until you both realise what is happening, such a situation
+can be very confusing.
+<p/>The simplest solution is the LaTeX <code>\</code><code>listfiles</code> 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.
+<p/>Note that <code>\</code><code>listfiles</code> only registers things that are input by the
+&ldquo;standard&rdquo; LaTeX mechanisms (<code>\</code><code>documentclass</code>, <code>\</code><code>usepackage</code>,
+<code>\</code><code>input</code>, <code>\</code><code>include</code>, <code>\</code><code>includegraphics</code> and so on).  But if you
+use TeX primitive syntax, as in
+<pre>
+  \input mymacros
+</pre>
+<i>mymacros.tex</i> <em>won&rsquo;t</em> be listed by <code>\</code><code>listfiles</code>, since
+you&rsquo;ve bypassed the mechanism that records its use.
+<p/>The <i>snapshot</i> 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.
+<p/>The <i>bundledoc</i> system uses the <i>snapshot</i> to produce an
+archive (e.g., <code>.tar.gz</code> or <code>.zip</code>) of the files needed by your
+document; it comes with configuration files for use with
+<i>teTeX</i> and <i>MiKTeX</i>.  It&rsquo;s plainly useful when
+you&rsquo;re sending the first copy of a document.
+<dl>
+<dt><tt><i>bundledoc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/bundledoc.zip">support/bundledoc</a> (<a href="ftp://cam.ctan.org/tex-archive/support/bundledoc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/bundledoc/">browse</a>)
+<dt><tt><i>snapshot.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.zip">macros/latex/contrib/snapshot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/snapshot/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html
new file mode 100644
index 00000000000..929facbf9f2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label findfiles</title>
+</head><body>
+<h3>Finding (La)TeX files</h3>
+<p/>Modern TeX distributions contain a huge array of support files of
+various sorts, but sooner or later most people need to find something
+that&rsquo;s not in their present system (if nothing else, because they&rsquo;ve
+heard that something has been updated).
+<p/>But how to find the files?
+<p/>Some sources, such as these FAQ answers, provide links to
+files: so if you&rsquo;ve learnt about a package here, you should be able to
+retrieve it without too much fuss.
+<p/>Otherwise, the CTAN sites provide searching facilities, via the web.
+The simplest search, locating files by name, is to be found on the
+Dante CTAN
+at <a href="http://www.dante.de/cgi-bin/ctan-index">http://www.dante.de/cgi-bin/ctan-index</a>; the script scans a
+list of files (<i>FILES.byname</i> &mdash; see below) and returns a list
+of matches, arranged very neatly as a series of links to directories
+and to individual files.
+<p/>The <a href="http://www.tex.ac.uk/search">UK</a> and
+<a href="http://www.ctan.org/search.html">USA</a> CTANs offer a
+search page that provides
+<ul>
+<li> a file-name search similar to the Dante machine&rsquo;s (above);
+<li> a keyword search of the archive catalogue (see below): this is a
+  pretty powerful tool: the results include links to the catalogue
+  &ldquo;short descriptions&rdquo;, so you can assure yourself that the package
+  you&rsquo;ve found is the one you want; and
+<li> a search form that allows you to use <i>Google</i> to search
+  CTAN.
+</ul>
+<p/>An alternative way to scan the catalogue is to use the catalogue&rsquo;s
+
+<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">&ldquo;by topic&rdquo; index</a>;
+this lists a series of topics, and (La)TeX projects that are worth
+considering if you&rsquo;re working on matters related to the topic.  
+<p/>In fact, <i>Google</i>, and other search engines, can be useful
+tools.  Enter your search keywords, and you may pick up a package that
+the author hasn&rsquo;t bothered to submit to CTAN.  If you&rsquo;re using
+<i>Google</i>, you can restrict your search to CTAN by
+entering
+<blockquote>
+  <code>site:ctan.org tex-archive &lt;<i>search term(s)</i>&gt;</code>
+</blockquote><p>
+in <i>Google</i>&rsquo;s &ldquo;search box&rdquo;.  You can also enforce the
+restriction using <i>Google</i>&rsquo;s &ldquo;advanced search&rdquo; mechanism;
+other search engines (presumably) have similar facilities.
+<p/>Many people avoid the need to go over the network at all, for their
+searches, by downloading the file list that the archives&rsquo; web
+file searches use.  This file, <i>FILES.byname</i>,
+presents a unified listing of the archive (omitting directory names and
+cross-links).  Its companion <i>FILES.last07days</i> 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 (perhaps using
+<i>rsync</i>) makes good sense.
+<dl>
+<dt><tt><i>FILES.byname</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/FILES.byname">FILES.byname</a>
+<dt><tt><i>FILES.last07days</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/FILES.last07days">FILES.last07days</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html
new file mode 100644
index 00000000000..240ad8b393d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label findfont</title>
+</head><body>
+<h3>Finding new fonts</h3>
+<p/>A comprehensive list of Metafont fonts used to be posted to
+<i>comp.fonts</i> and to <i>comp.text.tex</i>, roughly
+every six weeks, by Lee Quin.
+Nowadays, authors of new material in Metafont are few and far between
+(and mostly designing highly specialised things with limited appeal to
+ordinary users); as a result, no-one has taken over maintenance of the
+list of fonts.  If you need a font for some esoteric purpose, it may
+be worth <a href="FAQ-findfiles.html">searching CTAN</a> using your purpose
+as a search keyword.
+<p/>Most new fonts that appear are prepared in some scalable outline form
+or other, and a large proportion is distributed under commercial
+terms.  However, once you have acquired such a font, converting it to
+a form usable by your (La)TeX distribution is not (in principle) a
+serious problem.
+<p/>The answer &ldquo;<a href="FAQ-psfchoice.html">choice of scalable fonts</a>&rdquo; discusses
+fonts that are configured for general (both textual and mathematical)
+use with (La)TeX.  The list of such fonts is sufficiently short that
+they <em>can</em> all be discussed in one answer here.
+<dl>
+<dt><tt><i>Metafont font list</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont-list">info/metafont-list</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html
new file mode 100644
index 00000000000..c381aed0824
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label findwidth</title>
+</head><body>
+<h3>Finding the width of a letter, word, or phrase</h3>
+<p/>Put the word in a box, and measure the width of the box. For example,
+<blockquote>
+<pre>
+\newdimen\stringwidth
+\setbox0=\hbox{hi}
+\stringwidth=\wd0
+</pre>
+</blockquote><p>
+Note that if the quantity in the <code>\</code><code>hbox</code> 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.
+<p/>The same sort of thing is expressed in LaTeX by:
+<blockquote>
+<pre>
+\newlength{\gnat}
+\settowidth{\gnat}{\textbf{small}}
+</pre>
+</blockquote><p>
+This sets the value of the length command <code>\gnat</code> to the width of &ldquo;small&rdquo;
+in bold-face text.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html
new file mode 100644
index 00000000000..d62c6f8a162
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label fixnam</title>
+</head><body>
+<h3>How to change LaTeX&rsquo;s &ldquo;fixed names&rdquo;</h3>
+<p/>LaTeX document classes define several typographic operations that
+need &lsquo;canned text&rsquo; (text not supplied by the user).  In the earliest
+days of LaTeX 2.09 these bits of text were built in to the body of
+LaTeX&rsquo;s macros and were rather difficult to change, but &ldquo;fixed
+name&rdquo; 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 <code>\</code><code>tableofcontents</code>
+command is always called <code>\</code><code>contentsname</code> (or rather, what
+<code>\</code><code>contentsname</code> is defined to mean).
+Changing the canned text is now one of the easiest customisations a
+user can do to LaTeX.
+<p/>The canned text macros are all of the form
+<code>\</code><code>&lt;<i>thing</code>name</i>&gt;, and changing them is simplicity
+itself.  Put:
+<blockquote>
+<code>\</code><code>renewcommand{<code>\</code><code>&lt;<i>thing</code>name</i>&gt;}{Res minor}</code>
+</blockquote><p>
+in the preamble of your document, and the job is done.
+(However, beware of the <i>babel</i> package, which requires you to
+use a different mechanism: be sure to check
+
+<a href="FAQ-latexwords.html">changing <i>babel</i> names</a> if
+you&rsquo;re using it.)
+<p/>The names that are defined in the standard LaTeX classes (and the
+<i>makeidx</i> package) are listed
+below.  Some of the names are only defined in a subset of the classes
+(and the <i>letter</i> class has a set of names all of its own);
+the list shows the specialisation of each name, where appropriate.
+<p/><table rules="groups" border="0" cellpadding="3"><tbody><tr><td>
+<code>\</code><code>abstractname</code> <td> Abstract<tr><td>
+<code>\</code><code>alsoname</code> <td> see also (<i>makeidx</i> package)<tr><td>
+<code>\</code><code>appendixname</code> <td> Appendix<tr><td>
+<code>\</code><code>bibname</code> <td> Bibliography (<i>report</i>,<i>book</i>)<tr><td>
+<code>\</code><code>ccname</code> <td> cc (<i>letter</i>)<tr><td>
+<code>\</code><code>chaptername</code> <td> Chapter (<i>report</i>,<i>book</i>)<tr><td>
+<code>\</code><code>contentsname</code> <td> Contents<tr><td>
+<code>\</code><code>enclname</code> <td> encl (<i>letter</i>)<tr><td>
+<code>\</code><code>figurename</code> <td> Figure (for captions)<tr><td>
+<code>\</code><code>headtoname</code> <td> To (<i>letter</i>)<tr><td>
+<code>\</code><code>indexname</code> <td> Index<tr><td>
+<code>\</code><code>listfigurename</code> <td> List of Figures<tr><td>
+<code>\</code><code>listtablename</code> <td> List of Tables<tr><td>
+<code>\</code><code>pagename</code> <td> Page (<i>letter</i>)<tr><td>
+<code>\</code><code>partname</code> <td> Part<tr><td>
+<code>\</code><code>refname</code> <td> References (<i>article</i>)<tr><td>
+<code>\</code><code>seename</code> <td> see (<i>makeidx</i> package)<tr><td>
+<code>\</code><code>tablename</code> <td> Table (for caption)
+</tbody></table>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html
new file mode 100644
index 00000000000..f72016b2eb1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html
@@ -0,0 +1,53 @@
+<head>
+<title>UK TeX FAQ -- question label fixwidtab</title>
+</head><body>
+<h3>Fixed-width tables</h3>
+<p/>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.
+<p/>Basic LaTeX can make the gaps stretch: the <code>tabular*</code>
+environment takes an extra argument (before the <code>clpr</code> layout one)
+which takes a length specification: you can say things like &ldquo;<code>15cm</code>&rdquo;
+or &ldquo;<code>\</code><code>columnwidth</code>&rdquo; here.  You must also have an <code>\</code><code>extracolsep</code>
+command in the <code>clpr</code> layout argument, inside an <code>@</code>
+directive.  So, for example, one might have
+<pre>
+\begin{tabular*}{\columnwidth}{@{\extracolsep{\fill}}lllr}
+</pre>
+
+The <code>\</code><code>extracolsep</code> applies to all inter-column gaps to its right as
+well; if you don&rsquo;t want all gaps stretched, add
+<code>\</code><code>extracolsep{0pt}</code> to cancel the original.
+<p/>The <i>tabularx</i> package defines an extra <code>clpr</code> column
+specification, <code>X</code>; <code>X</code> columns behave as <code>p</code>
+columns which expand to fill the space available.  If there&rsquo;s more
+than one <code>X</code> column in a table, the spare space is distributed
+between them.
+<p/>The <i>tabulary</i> package (by the same author) provides a way of
+&ldquo;balancing&rdquo; the space taken by the columns of a table.  The package
+defines column specifications <code>C</code>, <code>L</code>, <code>R</code> and
+<code>J</code>, giving, respectively, centred, left, right and
+fully-justified versions of space-sharing columns.  The package
+examines how long each column would be &ldquo;naturally&rdquo; (i.e., on a piece of paper of unlimited width), and
+allocates space to each column accordingly.  There are &ldquo;sanity
+checks&rdquo; so that really large entries don&rsquo;t cause everything else to
+collapse into nothingness (there&rsquo;s a &ldquo;maximum width&rdquo; that any column
+can exert), and so that tiny entries can&rsquo;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
+&ldquo;side-effects&rdquo; (for example, a counter used to produce a row-number
+somewhere) are inevitably unreliable, and should not even be tried.
+<p/>The <i>ltxtable</i> package combines the features of the
+<i>longtable</i> and <i>tabularx</i> packages.  It&rsquo;s important
+to read the documentation, since usage is distinctly odd; the
+distribution contains no more than a file <i>ltxtable.tex</i>, which you
+should process using LaTeX.  Processing will give you a <i>.sty</i>
+file as well as the <i>.dvi</i> or <i>.pdf</i> output containing the
+documentation.
+<dl>
+<dt><tt><i>ltxtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>)
+<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>tabulary.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html
new file mode 100644
index 00000000000..9d2d936517b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label fllost</title>
+</head><body>
+<h3>Float(s) lost</h3>
+<p/>The error
+<blockquote>
+<pre>
+! LaTeX Error: Float(s) lost.
+</pre>
+</blockquote><p>
+seldom occurs, but always seems deeply cryptic when it <em>does</em>
+appear.
+<p/>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.)
+<p/>The most likely reason is that you placed a float or a <code>\</code><code>marginpar</code>
+command inside another float or marginpar, or inside a
+<code>minipage</code> environment, a <code>\</code><code>parbox</code> or <code>\</code><code>footnote</code>.
+Note that the error may be detected a long way from the problematic
+command(s), so the techniques of 
+<a href="FAQ-erroradvice.html">tracking down elusive errors</a> all need to be
+called into play.
+<p/>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...
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html
new file mode 100644
index 00000000000..79c7a8812ec
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label floatpages</title>
+</head><body>
+<h3>Floats on their own on float pages</h3>
+<p/>It&rsquo;s sometimes necessary to force a float to live on a page by itself.
+(It&rsquo;s sometimes even necessary for <em>every</em> float to live on a
+page by itself.)  When the float fails to &lsquo;set&rsquo;, and waits for the end
+of a chapter or of the document, the natural thing to do is to declare
+the float as
+<blockquote>
+  <code>\</code><code>begin{figure}[p!]</code>
+</blockquote><p>
+but the overriding <code>!</code> modifier has no effect on float page floats; so
+you have to make the float satisfy the parameters.
+<a href="FAQ-floats.html">Moving tables and figures</a> offers some
+suggestions, but doesn&rsquo;t solve the one-float-per-page question.
+<p/>The &lsquo;obvious&rsquo; solution, using the counter <code>totalnumber</code>
+(&ldquo;total number of floats per page&rdquo;) doesn&rsquo;t work:
+<code>totalnumber</code> only applies to floats on &lsquo;text&rsquo; pages (pages
+containing text as well as one or more float).  So, to allow any
+size float to take a whole page, set <code>\</code><code>floatpagefraction</code> really
+small, and to ensure that no more than one float occupies a page, make
+the separation between floats really big:
+<blockquote>
+<pre>
+\renewcommand\floatpagefraction{.001}
+\makeatletter
+\setlength\@fpsep{\textheight}
+\makeatother
+</pre>
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floatpages">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floatpages</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html
new file mode 100644
index 00000000000..118069a5b39
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html
@@ -0,0 +1,91 @@
+<head>
+<title>UK TeX FAQ -- question label floats</title>
+</head><body>
+<h3>Moving tables and figures in LaTeX</h3>
+<p/>Tables and figures have a tendency to surprise, by <em>floating</em>
+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&rsquo;ll fit without
+violating the certain typographic rules.  Even if you use the
+placement specifier <code>h</code> for &lsquo;here&rsquo;, the figure or table will not be
+printed &lsquo;here&rsquo; 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&rsquo;s rules can cause the
+floating items to pile up to the extent that you get an error message
+saying <a href="FAQ-tmupfl.html">&ldquo;Too many unprocessed floats&rdquo;</a>.
+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 &ldquo;non-standard&rdquo; floats defined by the
+<i>float</i> or other packages).
+<ul>
+<li> Do your figures need to float at all?  If not, look at the
+  recommendations for &ldquo;<a href="FAQ-figurehere.html">non-floating floats</a>&rdquo;
+<li> Are the placement parameters on your figures right?  The
+  default (<code>tbp</code>) is reasonable, but you can reasonably change it (for
+  example, to add an <code>h</code>).  Whatever you do, <em>don&rsquo;t</em>
+  omit the &lsquo;<code>p</code>&rsquo;: doing so could cause LaTeX to believe that if you
+  can&rsquo;t have your figure <em>here</em>, you don&rsquo;t want it
+  <em>anywhere</em>.  (LaTeX does try hard to avoid being confused in
+  this way...)
+<li> LaTeX&rsquo;s own float placement parameters could be preventing
+  placements that seem entirely &ldquo;reasonable&rdquo; to you &mdash; they&rsquo;re
+  notoriously rather conservative.  To encourage LaTeX not to move
+  your figure, you need to loosen its demands.  (The most important
+  ones are the ratio of text to float on a given page, but it&rsquo;s
+  sensible to have a fixed set that changes the whole lot, to meet
+  every eventuality.)
+<pre>
+\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}
+</pre>
+  The meanings of these
+  parameters are described on pages 199&ndash;200, section C.9 of the
+  LaTeX manual.
+<li> Are there places in your document where you could &lsquo;naturally&rsquo;
+  put a <code>\</code><code>clearpage</code> command?  If so, do: the backlog of floats is
+  cleared after a <code>\</code><code>clearpage</code>.  (Note that the <code>\</code><code>chapter</code>
+  command in the standard <i>book</i> and <i>report</i> classes
+  implicitly executes <code>\</code><code>clearpage</code>, so you can&rsquo;t float past
+  the end of a chapter.)
+<li> Try the <i>placeins</i> package: it defines a
+  <code>\</code><code>FloatBarrier</code> command beyond which floats may not pass.  A
+  package option allows you to declare that floats may not pass a
+  <code>\</code><code>section</code> command, but you can place <code>\</code><code>FloatBarrier</code>s wherever
+  you choose.
+<li> If you are bothered by floats appearing at the top of the page
+  (before they are specified in your text), try the <i>flafter</i>
+  package, which avoids this problem by insisting that floats should
+  always appear after their definition.
+<li> Have a look at the LaTeX2e <i>afterpage</i> package.
+  Its documentation gives as an example the idea
+  of putting <code>\</code><code>clearpage</code> <em>after</em> 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&rsquo;t help.
+<li> If you would actually <em>like</em> great blocks of floats at the
+  end of each of your chapters, try the <i>morefloats</i> package;
+  this &lsquo;simply&rsquo; increases the number of floating inserts that LaTeX
+  can handle at one time (from 18 to 36).
+<li> If you actually <em>wanted</em> all your figures to float to the
+  end (<em>e.g</em>., for submitting a draft copy of a paper), don&rsquo;t
+  rely on LaTeX&rsquo;s mechanism: get the <i>endfloat</i> package to do
+  the job for you.
+</ul>
+<dl>
+<dt><tt><i>afterpage.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>endfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/endfloat.zip">macros/latex/contrib/endfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/endfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/endfloat/">browse</a>)
+<dt><tt><i>flafter.sty</i></tt><dd>Part of the LaTeX distribution
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+<dt><tt><i>morefloats.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/morefloats.sty">macros/latex/contrib/misc/morefloats.sty</a>
+<dt><tt><i>placeins.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/placeins.zip">macros/latex/contrib/placeins</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/placeins.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/placeins/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html
new file mode 100644
index 00000000000..9627e742196
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html
@@ -0,0 +1,44 @@
+<head>
+<title>UK TeX FAQ -- question label flushboth</title>
+</head><body>
+<h3>Cancelling <code>\</code><code>ragged</code> commands</h3>
+<p/>LaTeX provides commands <code>\</code><code>raggedright</code> and <code>\</code><code>raggedleft</code>, but
+none to cancel their effect.  The <code>\</code><code>centering</code> command is
+implemented in the same way as the <code>\</code><code>ragged*</code> commands, and suffers
+in the same way.
+<p/>The following code (to be inserted in a package of your own, or as
+
+<a href="FAQ-atsigns.html">internal LaTeX code</a>) defines a command that
+restores flush justification at both margins:
+<pre>
+\def\flushboth{%
+  \let\\\@normalcr
+  \@rightskip\z@skip \rightskip\@rightskip
+  \leftskip\z@skip
+  \parindent 1.5em\relax}
+</pre>
+There&rsquo;s a problem with the setting of <code>\</code><code>parindent</code> in the code: it&rsquo;s
+necessary because both the <code>\</code><code>ragged</code> commands set <code>\</code><code>parindent</code> to
+zero, but the setting isn&rsquo;t a constant of nature: documents using a
+standard LaTeX class with <code>twocolumn</code> option will have
+<code>1.0em</code> by default, and there&rsquo;s no knowing what you (or some
+other class) will have done.
+<p/>Any but a really old copy of Martin Schr&ouml;der&rsquo;s <i>ragged2e</i>
+package has a <code>\</code><code>justifying</code> command to match its 
+<a href="FAQ-ragright.html">versions of the LaTeX &lsquo;ragged&rsquo; commands</a>.  The
+package also provides a <code>justify</code> environment, which
+permits areas of justified text in a larger area which is ragged.
+<dl>
+<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>)
+</dl>
+
+
+
+
+
+
+
+
+
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html
new file mode 100644
index 00000000000..347f62ff2ff
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html
@@ -0,0 +1,96 @@
+<head>
+<title>UK TeX FAQ -- question label fmtconv</title>
+</head><body>
+<h3>Other conversions to and from (La)TeX</h3>
+<p/><dl>
+<dt>troff<dd><i>Tr2latex</i>, assists in the translation of a
+  <i>troff</i> document into LaTeX 2.09 format.  It recognises most
+  <code>-ms</code> and <code>-man</code> macros, plus most <i>eqn</i> and some
+  <i>tbl</i> 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...).
+  <i>Tr2latex</i> is an enhanced version of the earlier
+  <i>troff-to-latex</i> (which is no longer available).
+<p/>
+
+
+<p/>
+
+
+
+
+<p/><dt>WordPerfect<dd> <i>wp2latex</i> is actively maintained, and is
+  available either for MSDOS or for Unix systems.
+<dt>RTF<dd> <i>Rtf2tex</i>, by Robert Lupton, is for
+  converting Microsoft&rsquo;s Rich Text Format to TeX.  There is also a
+  converter to LaTeX by Erwin Wechtl, called <i>rtf2latex</i>.
+  The latest converter, by Ujwal Sathyam and Scott Prahl, is
+  <i>rtf2latex2e</i>; this system seems rather good already, and
+  is still being improved.
+<p/>  Translation <em>to</em> RTF may be done (for a somewhat
+  constrained set of LaTeX documents) by TeX2RTF, which
+  can produce ordinary RTF, Windows Help RTF (as well as
+  HTML, <a href="FAQ-LaTeX2HTML.html">conversion to HTML</a>).
+  TeX2RTF is supported on various Unix platforms and under
+  Windows 3.1
+<dt>Microsoft Word<dd> A rudimentary (free) program for converting
+  MS-Word to LaTeX is <i>wd2latex</i>, which runs on MSDOS.
+  <i>Word2</i><em>TeX</em> and <em>TeX</em><i>2Word</i> are 
+  shareware translators from 
+  <a href="http://www.chikrii.com/">Chikrii Softlab</a>; users&rsquo; reports are
+  very positive.
+<p/>  The excellent <i>tex4ht</i> will generate OpenOffice ODT
+  format, which can be used as an intermediate to producing Word
+  format files.
+<p/>  If cost is a constraint, the best bet is probably to use an
+  intermediate format such as RTF or HTML.
+  <i>Word</i> outputs and reads both, so in principle this route
+  may be useful.
+<p/>  You can also use PDF as an intermediate format: Acrobat Reader
+  for Windows (version 5.0 and later) will output rather feeble
+  RTF that <i>Word</i> can read.
+<dt>Excel<dd> <i>Excel2Latex</i> converts an <i>Excel</i> file
+  into a LaTeX <code>tabular</code> environment; it comes as a
+  <code>.xls</code> file which defines some <i>Excel</i> macros to produce
+  output in a new format.
+<dt>runoff<dd> Peter Vanroose&rsquo;s <i>rnototex</i>
+  conversion program is written in VMS Pascal.
+  The sources are distributed with a VAX executable.
+<dt>refer/tib<dd> There are a few programs for converting bibliographic
+  data between BibTeX and <i>refer</i>/<i>tib</i> formats.
+  The collection includes a shell script converter from BibTeX to
+  <i>refer</i> format as well. The collection
+  is not maintained.
+<dt>PC-Write<dd><i>pcwritex.arc</i> is a
+  print driver for PC-Write that &ldquo;prints&rdquo; a PC-Write
+  V2.71 document to a TeX-compatible disk file.  It was written by Peter
+  Flynn at University College, Cork, Republic of Ireland.
+</dl>
+<p/>
+<a href="http://www.tug.org/utilities/texconv/index.html">Wilfried Hennings&rsquo; FAQ</a>,
+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.
+<p/>A group at Ohio State University (USA) is working on
+a common document format based on SGML, with the ambition that any
+format could be
+translated to or from this one.  <i>FrameMaker</i> provides
+&ldquo;import filters&rdquo; to aid translation from alien formats
+(presumably including TeX) to <i>FrameMaker</i>&rsquo;s own.
+<dl>
+<dt><tt><i>excel2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/excel2latex.zip">support/excel2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/excel2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/excel2latex/">browse</a>)
+<dt><tt><i>pcwritex.arc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.zip">support/pcwritex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pcwritex/">browse</a>)
+<dt><tt><i>refer and tib tools</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/refer-tools.zip">biblio/bibtex/utils/refer-tools</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/refer-tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/refer-tools/">browse</a>)
+<dt><tt><i>rnototex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rnototex.zip">support/rnototex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rnototex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rnototex/">browse</a>)
+<dt><tt><i>rtf2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rtf2latex.zip">support/rtf2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rtf2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rtf2latex/">browse</a>)
+<dt><tt><i>rtf2latex2e</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rtf2latex2e.zip">support/rtf2latex2e</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rtf2latex2e.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rtf2latex2e/">browse</a>)
+<dt><tt><i>rtf2tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rtf2tex.zip">support/rtf2tex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rtf2tex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rtf2tex/">browse</a>)
+<dt><tt><i>tex2rtf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tex2rtf.zip">support/tex2rtf</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tex2rtf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tex2rtf/">browse</a>)
+<dt><tt><i>tr2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tr2latex.zip">support/tr2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tr2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tr2latex/">browse</a>)
+<dt><tt><i>wd2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/wd2latex.zip">support/wd2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/wd2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/wd2latex/">browse</a>)
+<dt><tt><i>wp2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/wp2latex.zip">support/wp2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/wp2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/wp2latex/">browse</a>)
+<dt><tt><i>Word processor FAQ (source)</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.zip">help/wp-conv</a> (<a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/wp-conv/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html
new file mode 100644
index 00000000000..0b6f33c0f47
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label fontname</title>
+</head><body>
+<h3>What is the &ldquo;Berry naming scheme&rdquo;</h3>
+<p/>In the olden days, (La)TeX distributions were limited by the
+feebleness of file systems&rsquo; 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 CDROMs has a
+similar failing, but that too has been modified by various extension
+mechanisms.)
+<p/>One area in which this was 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&rsquo;s a natural ambition to
+change the name to something that identifies the font somewhat
+precisely.  Unfortunately, names such as &ldquo;BaskervilleMT&rdquo; 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.
+<p/>Thus arose the Berry naming scheme.
+<p/>The basis of the scheme is to encode the meanings of the various parts
+of the file&rsquo;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 letter to the font &ldquo;foundry&rdquo;, two to the
+typeface name, one to the weight, and so on.  The whole scheme is
+outlined in the <i>fontname</i> distribution, which includes
+extensive documentation and a set of tables of fonts whose names have
+been systematised.
+<dl>
+<dt><tt><i>fontname distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/fontname.zip">info/fontname</a> (<a href="ftp://cam.ctan.org/tex-archive/info/fontname.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/fontname/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html
new file mode 100644
index 00000000000..da8f8a82f2b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html
@@ -0,0 +1,96 @@
+<head>
+<title>UK TeX FAQ -- question label fonts-pln</title>
+</head><body>
+<h3>Using non-standard fonts in Plain TeX</h3>
+<p/>Plain TeX (in accordance with its description) doesn&rsquo;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.
+<p/>To use something other than Knuth&rsquo;s default, the default mechanism is
+to use the <code>\</code><code>font</code> primitive:
+<blockquote>
+<pre>
+\font\foo=nonstdfont
+...
+\foo
+Text set using nonstdfont ...
+</pre>
+</blockquote><p>
+The name you use (<code>nonstdfont</code>, above) is the name of the
+<code>.tfm</code> file for the font you want.
+<p/>If you want to use an italic version of <code>\</code><code>foo</code>, you need to use
+<code>\</code><code>font</code> again:
+<blockquote>
+<pre>
+\font\fooi=nonstdfont-italic
+...
+\fooi
+Text set using nonstdfont italic...
+</pre>
+</blockquote><p>
+<p/>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 <a href="FAQ-whatenc.html">font encodings</a>.  Unfortunately, many fonts that
+have appeared recently simply don&rsquo;t come in versions using Knuth&rsquo;s
+eccentric font encodings &mdash; but those encodings are built into
+Plain TeX, so that some macros of Plain TeX need to be changed to
+use the fonts.  LaTeX gets around all these problems by using a
+&ldquo;font selection scheme&rdquo; &mdash; this &lsquo;NFSS&rsquo; (&lsquo;N&rsquo; for
+&lsquo;new&rsquo;, as opposed to what LaTeX 2.09 had) carries around with it
+separate information about the fonts you use, so the changes to
+encoding-specific commands happen automagically.
+<p/>If you only want to use the <a href="FAQ-ECfonts.html">EC fonts</a>, you
+can in principle use the <i>ec-plain</i> bundle, which gives you a version
+of Plain TeX which you can run in the same way that you run
+Plain TeX using the original CM fonts, by invoking
+<i>tex</i>.  (<i>Ec-plain</i> also extends the EC fonts,
+for reasons which aren&rsquo;t immediately clear, but which might cause
+problems if you&rsquo;re hoping to use Type 1 versions of the fonts.)
+<p/>The <i>font_selection</i> 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
+CM fonts.  It&rsquo;s a compact solution, within its restrictions.
+<p/>Other Plain TeX approaches to the problem (packages
+<i>plnfss</i>, <i>fontch</i> and <i>ofs</i>) break out of the
+Plain TeX model, towards the sort of font selection provided by
+ConTeXt and LaTeX &mdash; 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&rsquo;s OT1.
+<p/><i>Plnfss</i> has a rather basic set of font family details;
+however, it is capable of using font description (<code>.fd</code>) files
+created for LaTeX.  (This is useful, since most modern mechanisms
+for integrating outline fonts with TeX generate <code>.fd</code> files
+in their process.)
+<p/><i>Fontch</i> has special provision for T1 and TS1
+encodings, which you select by arcane commands, such as:
+<blockquote>
+<pre>
+\let\LMTone\relax
+\input fontch.tex
+</pre>
+</blockquote><p>
+for T1.
+<p/><i>Ofs</i> seems to be the most thoroughly thought-through of the
+alternatives, and can select more than one encoding: as well as
+T1 it covers the encoding IL2, which is favoured in the
+Czech Republic and Slovakia.  <i>Ofs</i> also covers mathematical fonts,
+allowing you the dubious pleasure of using fonts such as the 
+<a href="FAQ-psfchoice.html"><i>pxfonts</i> and <i>txfonts</i></a>.
+<p/>The <i>pdcmac</i> Plain TeX macro package aims to be a complete
+document preparation environment, like <a href="FAQ-eplain.html">Eplain</a>.  One
+of its components is a font selection scheme, <i>pdcfsel</i>, which
+is rather simple but adequately powerful for many uses.  The package
+doesn&rsquo;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&rsquo;re needed.  The distribution includes a configuration to
+use Adobe &lsquo;standard&rsquo; fonts for typesetting text.  (Eplain itself
+seems not to offer a font selection scheme.)
+<dl>
+<dt><tt><i>ec-plain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.zip">macros/ec-plain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/ec-plain/">browse</a>)
+<dt><tt><i>fontch</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.zip">macros/plain/contrib/fontch</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/fontch/">browse</a>)
+<dt><tt><i>font_selection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.zip">macros/plain/contrib/font_selection</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/font_selection/">browse</a>)
+<dt><tt><i>ofs</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.zip">macros/generic/ofs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/ofs/">browse</a>)
+<dt><tt><i>pdcmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/pdcmac.zip">macros/plain/contrib/pdcmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/pdcmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/pdcmac/">browse</a>)
+<dt><tt><i>plnfss</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/plnfss/">macros/plain/contrib/plnfss/</a>
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html
new file mode 100644
index 00000000000..73a6e47094e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label fontsize</title>
+</head><body>
+<h3>Fonts at arbitrary sizes</h3>
+<p/>Almost all fonts, nowadays, are provided with LaTeX control
+(<code>.fd</code>) files, so the temptation to risk the
+<a href="FAQ-newfontstar.html">problems of <code>\</code><code>newfont</code></a> is usually easy to
+resist.
+<p/>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 (T1) EC fonts, but it is widely considered to be
+anomalous, nowadays.  In recognition of this problem, there is a
+package <i>fix-cm</i> which will allow you to use the fonts, within
+LaTeX, at any size you choose.  If you&rsquo;re not using scaleable
+versions of the fonts, most modern distributions will just generate an
+appropriate bitmap for you.
+<p/>So, suppose you want to use Computer Modern Roman at 30 points, you
+might be tempted to write:
+<blockquote>
+<pre>
+\newfont{\bigfont}{cmr10 at 30pt}
+\begin{center}
+  \bigfont Huge text
+\end{center}
+</pre>
+</blockquote><p>
+which will indeed work, but will actually produce a worse result than
+<blockquote>
+<pre>
+\usepackage{fix-cm}
+...
+\begin{center}
+  \fontsize{30}{36}\selectfont
+  Huge text
+\end{center}
+</pre>
+</blockquote><p>
+Note that the <i>fix-cm</i> package was not distributed until the
+December 2003 edition of LaTeX; if you have an older distribution,
+the packages <i>type1cm</i> (for CM fonts) and
+<i>type1ec</i> (for EC fonts) are available.
+<dl>
+<dt><tt><i>fix-cm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) (an unpacked
+  version is available at <a href="ftp://cam.ctan.org/tex-archive/macros/latex/unpacked/fix-cm.sty">macros/latex/unpacked/fix-cm.sty</a>)
+<dt><tt><i>type1cm.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.zip">macros/latex/contrib/type1cm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm/">browse</a>)
+<dt><tt><i>type1ec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super/type1ec.sty">fonts/ps-type1/cm-super/type1ec.sty</a> (the package is actually part of
+  the <a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) distribution, but it works happily in
+  the absence of the scaled fonts)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontsize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontsize</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html
new file mode 100644
index 00000000000..b14b1e7e089
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label fontunavail</title>
+</head><body>
+<h3>Warning: &ldquo;Font shape ... not available&rdquo;</h3>
+<p/>LaTeX&rsquo;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.
+<p/>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&rsquo;t there at the size you want, you will see a
+message like:
+
+<pre>
+LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size &lt;11.5&gt; not available
+(Font)              size &lt;12&gt; substituted on input line ...
+</pre>
+There will also be a warning like:
+
+<pre>
+LaTeX Font Warning: Size substitutions with differences
+(Font)              up to 0.5pt have occurred.
+</pre>
+after LaTeX has encountered <code>\</code><code>end{document}</code>.
+<p/>The message tells you that you&rsquo;ve chosen a font size that is not in
+LaTeX&rsquo;s list of &ldquo;allowed&rdquo; sizes for this font; LaTeX has
+chosen the nearest font size it knows is allowed.  In fact, you can
+tell LaTeX to allow <em>any</em> 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
+(EC) fonts, you can tell LaTeX to remove the restrictions;
+use the <i>type1cm</i> or <i>type1ec</i> package as appropriate.
+<p/>If the combination of font shape and series isn&rsquo;t available, LaTeX
+will usually have been told of a fall-back combination that may be
+used, and will select that:
+
+<pre>
+LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined
+(Font)              using `OT1/cmr/bx/n' instead on input line 0.
+</pre>
+<p/>Substitutions may also be &ldquo;silent&rdquo;; in this case, there is no more
+than an &ldquo;information&rdquo; message in the log file.  For example, if you
+specify an encoding for which there is no version in the current font
+family, the &lsquo;default family for the encoding&rsquo; is selected.  This
+happens, for example, if you use command <code>\</code><code>textbullet</code>, which is
+normally taken from the maths symbols font, which is in <code>OMS</code>
+encoding.  My test log contained:
+
+<pre>
+LaTeX Font Info:    Font shape `OMS/cmr/m/n' in size &lt;10&gt; not available
+(Font)              Font shape `OMS/cmsy/m/n' tried instead on input line ...
+</pre>
+<p/>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.
+<dl>
+<dt><tt><i>type1cm.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.zip">macros/latex/contrib/type1cm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm/">browse</a>)
+<dt><tt><i>type1ec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super/type1ec.sty">fonts/ps-type1/cm-super/type1ec.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html
new file mode 100644
index 00000000000..b5cf890a453
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label footintab</title>
+</head><body>
+<h3>Footnotes in tables</h3>
+<p/>The standard LaTeX <code>\</code><code>footnote</code> command doesn&rsquo;t work in tables; the table
+traps the footnotes and they can&rsquo;t escape to the bottom of the page.
+<p/>If your table is floating, your best bet is (unfortunately) to put the
+table in a <code>minipage</code> environment and to put the notes
+underneath the table, or to use Donald Arseneau&rsquo;s package
+<i>threeparttable</i> (which implements &ldquo;table notes&rdquo; proper).
+<p/>The <i>ctable</i> package extends the model of
+<i>threeparttable</i>, and also uses the ideas of the
+<i>booktabs</i> package.  The <code>\</code><code>ctable</code> command does the complete
+job of setting the table, placing the caption, and defining the
+notes.  The &ldquo;table&rdquo; may consist of diagrams, and a parameter in
+<code>\</code><code>ctable</code>&rsquo;s optional argument makes the float that is created a
+&ldquo;figure&rdquo; rather than a &ldquo;table&rdquo;.
+<p/>Otherwise, if your table is not floating (it&rsquo;s just a
+&lsquo;<code>tabular</code>&rsquo; in the middle of some text), there are several
+things you can do to fix the problem.
+<ul>
+<li> Use <code>\</code><code>footnotemark</code> to position the little marker
+  appropriately, and then put in <code>\</code><code>footnotetext</code> commands to fill in
+  the text once you&rsquo;ve closed the <code>tabular</code> environment.
+  This is described in Lamport&rsquo;s book, but it gets messy if there&rsquo;s
+  more than one footnote.
+<li> Stick the table in a <code>minipage</code> anyway.  This provides all the
+  ugliness of footnotes in a minipage with no extra effort.
+<li> Use <i>threeparttable</i> anyway; the package is intended for
+  floating tables, and the result might look odd if the table is not
+  floating, but it will be reasonable.
+<li> Use <i>tabularx</i> or <i>longtable</i> from the LaTeX
+  tools distribution; they&rsquo;re noticeably less efficient than the
+  standard <code>tabular</code> environment, but they do allow
+  footnotes.
+<li> Use <i>footnote</i>, which provides an
+  <code>savenotes</code> which collects all footnotes and emits them
+  at the end of the environment; thus if you put your
+  <code>tabular</code> environment inside the environment, the
+  footnotes will appear as needed.  Alternatively, you may use
+  <code>\</code><code>makesavenoteenv{tabular}</code> in the preamble of your
+  document, and tables will all behave as if they were inside a
+  <code>savenotes</code> environment.
+<li> Use <i>mdwtab</i> from the same bundle; it will handle
+  footnotes properly, 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 &lsquo;tools&rsquo;
+  bundle.
+</ul>
+<p/>The documentation of <i>threeparttable</i> appears in the package
+file itself; that of <i>ctable</i> is distributed as a PDF
+file (for convenience&rsquo;s sake).
+<dl>
+<dt><tt><i>ctable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ctable.zip">macros/latex/contrib/ctable</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ctable.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ctable/">browse</a>)
+<dt><tt><i>footnote.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>mdwtab.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+<dt><tt><i>threeparttable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a>
+<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html
new file mode 100644
index 00000000000..160a51f0534
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label footnpp</title>
+</head><body>
+<h3>Footnotes numbered &ldquo;per page&rdquo;</h3>
+<p/>The obvious solution is to make the footnote number reset whenever the
+page number is stepped, using the 
+<a href="FAQ-addtoreset.html">LaTeX internal mechanism</a>.  Sadly, the place
+in the document where the page number is stepped is unpredictable, not
+(&ldquo;tidily&rdquo;) at the end of the printed page; so the link only ever
+works by luck.
+<p/>As a result, resetting footnotes is inevitably a complicated process,
+using labels of some sort.  It&rsquo;s nevertheless important, given the
+common requirement for footnotes marked by symbols (with painfully
+small symbol sets).  There are three packages that manage it, one way
+or another.
+<p/>The <i>perpage</i> package provides a general mechanism for
+resetting counters per page, so can obviously be used for this task.
+The interface is pretty simple: <code>\</code><code>MakePerPage{footnote}</code> will
+do the job.  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: <code>\</code><code>MakePerPage[2]{footnote}</code>.  It&rsquo;s a
+first-rate package, small and efficient
+<p/>The <i>footmisc</i> package provides a variety of means of
+controlling footnote appearance, among them a package option
+<code>perpage</code> that adjusts the numbering per page; if you&rsquo;re
+doing something else odd about footnotes, it means you may only need
+the one package to achieve your ends.
+<p/>The <i>footnpag</i> package also does per-page footnotes (and
+nothing else).  With the competition from <i>perpage</i>, it&rsquo;s
+probably not particularly useful any more.  (Documentation is
+<i>footnpag-user.pdf</i> in the distribution.)
+<dl>
+<dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>)
+<dt><tt><i>footnpag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.zip">macros/latex/contrib/footnpag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footnpag/">browse</a>)
+<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html
new file mode 100644
index 00000000000..46463ed2b18
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label formatstymy</title>
+</head><body>
+<h3>&ldquo;Fatal format file error; I&rsquo;m stymied&rdquo;</h3>
+<p/>(La)TeX applications often fail with this error when you&rsquo;ve been
+playing with the configuration, or have just installed a new version.
+<p/>The format file contains the macros that define the system you want to
+use: anything from the simplest (Plain TeX) all the way to the most
+complicated, such as LaTeX or ConTeXt.  From the command you
+issue, TeX knows which format you want.
+<p/>The error message
+<pre>
+  Fatal format file error; I'm stymied
+</pre>
+means that TeX itself can&rsquo;t understand the format you want.
+Obviously, this could happen if the format file had got corrupted, but
+it usually doesn&rsquo;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&rsquo;s formats.  So the new version of TeX you
+have just installed, won&rsquo;t understand the format generated by the one
+you installed last year.
+<p/>Resolve the problem by regenerating the format; of course, this
+depends on which system you are using.
+<ul>
+<li> On a teTeX-based system, run
+<pre>
+  fmtutil --all
+</pre>
+  or
+<pre>
+  fmtutil --byfmt=&lt;format name&gt;
+</pre>
+  to build only the format that you are interested in.
+<li> On a MiKTeX system, click <code>Start</code>-&gt; 
+<code>Programs</code>-&gt; 
+<code>MiKTeX <em>version</em></code>-&gt; 
+<code>MiKTeX Options</code>, and in the options window, click
+  <code>Update now</code>.
+</ul>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html
new file mode 100644
index 00000000000..aa9b41b0c40
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label formbiblabel</title>
+</head><body>
+<h3>Format of numbers in the bibliography</h3>
+<p/>By default, LaTeX makes entries in the bibliography look like:
+<blockquote>
+  [1] Doe, Joe et al.  Some journal.  2004.<br> 
+  [2] Doe, Jane et al. Some journal. 2003.
+</blockquote><p>
+while many documents need something like:
+<blockquote>
+  1. Doe, Joe et al.  Some journal.  2004.<br>
+  2. Doe, Jane et al. Some journal. 2003.
+</blockquote><p>
+<p/>This sort of change may be achieved by many of the &ldquo;general&rdquo;
+citation packages; for example, in <i>natbib</i>, it&rsquo;s as simple as:
+<blockquote>
+<pre>
+\renewcommand{\bibnumfmt}[1]{#1.}
+</pre>
+</blockquote><p>
+but if you&rsquo;re not using such a package, the following internal
+LaTeX commands, in the preamble of your document, will do the job:
+<blockquote>
+<pre>
+\makeatletter
+\renewcommand*{\@biblabel}[1]{\hfill#1.}
+\makeatother
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>natbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html
new file mode 100644
index 00000000000..f02c5ebd728
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html
@@ -0,0 +1,53 @@
+<head>
+<title>UK TeX FAQ -- question label ftncapt</title>
+</head><body>
+<h3>Footnotes in captions</h3>
+<p/>Footnotes in captions are especially tricky: they present problems of
+their own, on top of the problems one experiences with
+<a href="FAQ-ftnsect.html">footnotes in section titles</a> and with 
+<a href="FAQ-footintab.html">footnotes in tables</a>.  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.  Note that the <i>threeparttable</i>
+scheme (see, again, 
+<a href="FAQ-footintab.html">footnotes in tables</a>) also applies
+to notes in captions, and may very well be preferable to whatever you
+were thinking of.
+<p/>If you <em>are</em> going to proceed:
+<ul>
+<li> use an optional argument in your <code>\</code><code>caption</code> command, that
+  doesn&rsquo;t have the footnote in it; this prevents the footnote
+  appearing in the &ldquo;List of ...&rdquo;, and
+<li> put your whole float in a <code>minipage</code> so as to keep
+  the footnotes with the float.
+</ul>
+so we have:
+<blockquote>
+<pre>
+\begin{figure}
+  \begin{minipage}{\textwidth}
+    ...
+    \caption[Caption for LOF]%
+      {Real caption\footnote{blah}}
+  \end{minipage}
+\end{figure}
+</pre>
+</blockquote><p>
+However, <em>as well as</em> all of the above, one <em>also</em> has to
+deal with the tendency of the <code>\</code><code>caption</code> command to produce the
+footnote&rsquo;s text twice.  For this last problem, there is no tidy
+solution this author is aware of.
+<p/>If you&rsquo;re suffering the problem, a well-constructed <code>\</code><code>caption</code>
+command in a <code>minipage</code> environment within a float (as
+in the example above) can produce <em>two</em> copies of the footnote
+body &ldquo;blah&rdquo;. (In fact, the effect only occurs with captions that are
+long enough to require two lines to be typeset, and so wouldn&rsquo;t appear
+with such a short caption.)
+<p/>The documentation of the <i>ccaption</i> package describes a really
+rather awful work-around.
+<dl>
+<dt><tt><i>ccaption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse</a>)
+<dt><tt><i>threeparttable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html
new file mode 100644
index 00000000000..5461d389a4b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label ftnsect</title>
+</head><body>
+<h3>Footnotes in LaTeX section headings</h3>
+<p/>The <code>\</code><code>footnote</code> command is fragile, so that simply placing the
+command in <code>\</code><code>section</code>&rsquo;s arguments isn&rsquo;t satisfactory.  Using
+<code>\</code><code>protect</code><code>\</code><code>footnote</code> isn&rsquo;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&rsquo;s generally not thought a &ldquo;good
+thing&rdquo; to have them there; in the page header, footnotes will simply
+fail.  Whatever the desirability of the matter, there&rsquo;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.
+<p/>To suppress the footnote in headings and table of contents:
+<ul>
+<li> Take advantage of the fact that the mandatory argument doesn&rsquo;t
+  &lsquo;move&rsquo; if the optional argument is present:
+<p/>  <code>\</code><code>section[title]</code>
+    <code>{title</code><code>\</code><code>footnote{title ftnt}</code><code>}</code>
+<li> Use the <i>footmisc</i> package, with package option
+  <code>stable</code> &mdash; this modifies footnotes so that they softly and
+  silently vanish away if used in a moving argument.  With this, you
+  simply need:
+<pre>
+% in the document preamble
+\usepackage[stable]{footmisc}
+...
+% in the body of the document
+\section{title\footnote{title ftnt}}
+</pre>
+</ul>
+<dl>
+<dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html
new file mode 100644
index 00000000000..3c65b2248d0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label fuzzy-T1</title>
+</head><body>
+<h3>Fonts go fuzzy when you switch to T1</h3>
+<!-- crippled blurry -->
+<p/>You&rsquo;ve been having problems with hyphenation, and someone has
+suggested that you should use &ldquo;<code>\</code><code>usepackage[T1]{fontenc}</code>&rdquo;
+to help sort them out.  Suddenly you find that your final PDF
+has become fuzzy.  The problem may arise whether you are using PostScript
+output and then distilling it, or you are using PDFTeX for the
+whole job.
+<p/>In fact, this is the same problem as most others about the
+<a href="FAQ-dvips-pdf.html">quality of PDF</a>: you&rsquo;ve abandoned
+your previous setup using Type 1 versions of the CM fonts, and
+<i>dvips</i> has inserted Type 3 versions of the EC fonts
+into your document output.  (See 
+&ldquo;<a href="FAQ-adobetypen.html">Adobe font types</a>
+for details of these font types; also, note that the font
+<em>encoding</em> T1
+has nothing directly to do with the font <em>format</em> Type 1).
+<p/>However, as noted in 
+&ldquo;<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>&rdquo;,
+Type 1 versions of CM-like fonts in T1 (or equivalent) encoding
+are now available, both as &ldquo;real&rdquo; fonts, and as virtual font sets.
+One solution, therefore, is to use one of these alternatives.
+<p/>The alternative is to switch font family altogether, to something like
+<i>Times</i> (as a no-thought default) or one of the many more pleasing
+Adobe-encoded fonts.  The default action of <i>fontinst</i>, when
+creating metrics for such a font, is to create settings for both OT1
+and T1 encodings, so there&rsquo;s little change in what goes on (at the
+user level) even if you have switched to T1 encoding when using the
+fonts.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html
new file mode 100644
index 00000000000..848da58ff4f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label fuzzy-gs</title>
+</head><body>
+<h3>Fuzzy fonts because <i>Ghostscript</i> too old</h3>
+<!-- crippled blurry -->
+<p/>So you&rsquo;ve done everything the FAQ has told you that you need,
+correct fonts properly installed and appearing in the <i>dvips</i>
+output, but <em>still</em> you get fuzzy character output after
+distilling with <i>ghostscript</i>.
+<p/>The problem could arise from too old a version of
+<i>ghostscript</i>, which you may be using directly, or via a
+script such as <i>ps2pdf</i> (distributed with
+<i>ghostscript</i> itself), <i>dvipdf</i>, or similar.
+Though <i>ghostscript</i> 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 (<i>Times</i>,
+<i>Helvetica</i>, etc.).  Later versions added &lsquo;complete&rsquo;
+distillation, but it wasn&rsquo;t until version 6.50 that one could rely on
+it for everyday work.
+<p/>So, if your PDF  output still looks fuzzy in <i>Acrobat</i>
+<i>Reader</i>, upgrade <i>ghostscript</i>.  The new version
+should be at least version 6.50, of course, but it&rsquo;s usually good
+policy to go to the most recent version (version 8.12 at the time of
+writing &mdash; 2003).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html
new file mode 100644
index 00000000000..043e7fb8fb9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label fuzzy-type3</title>
+</head><body>
+<h3>The wrong type of fonts in PDF</h3>
+<!-- crippled blurry -->
+<p/>This is far the commonest problem: the symptom is that text in the
+document looks &ldquo;fuzzy&rdquo;.
+<p/>Most people use <i>Adobe</i> <i>Acrobat</i> <i>Reader</i>
+to view their PDF: <i>Reader</i> 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 the recently released version 6).
+<p/>So we don&rsquo;t want bitmap fonts in our PostScript: with them, characters show
+up in <i>Reader</i>&rsquo;s display as blurred blobs which are often not
+recognisable as the original letter, and are often not properly placed
+on the line.  Nevertheless, even now, most TeX systems have
+<i>dvips</i> configured to use
+<a href="FAQ-pk.html"><code>.pk</code> files</a> in its output.  Even
+PDFTeX will use <code>.pk</code> files if it can see no alternative for
+a font in the document it is processing.
+<p/>Our remedy is to use
+&ldquo;<a href="FAQ-adobetypen.html">Adobe Type 1</a>&rdquo;
+versions of the fonts we need.  Since Adobe are in the
+business of selling Type 1 fonts, <i>Reader</i> was of course made
+to deal with them really rather well, from the very beginning.
+<p/>Of course, if your document uses nothing but fonts that came from
+Adobe in the first place &mdash; fonts such as <i>Times</i> that
+appear in pretty much every PostScript printer, or such as Adobe
+<i>Sabon</i> that you pay extra for &mdash; then there&rsquo;s no problem.
+<p/>But most people use <i>Computer</i> <i>Modern</i> to start
+with, and even those relative sophisticates who use something as
+exotic as <i>Sabon</i> often find themselves using odd characters
+from CM without really intending to do so.  Fortunately, rather
+good versions of the CM fonts are available from the AMS
+(who have them courtesy of 
+<a href="FAQ-commercial.html">Blue Sky Research</a> and Y&amp;Y).
+<p/>Most modern systems have the fonts installed ready to use; and any
+system installed less than 3 years ago has a <i>dvips</i>
+configuration file &lsquo;<code>pdf</code>&rsquo; that signals the use of the
+CM fonts, and also sets a few other parameters to improve
+<i>dvips</i>&rsquo; output.  Use this configuration as:
+<pre>
+  dvips -Ppdf myfile -o myfile.ps
+</pre>
+This may produce a warning message about failing to find the
+configuration file:
+<pre>
+  dvips: warning: no config file for `pdf'
+</pre>
+or something similar, or about failing to find a font file:
+<pre>
+  dvips: ! Couldn't find header file cmr10.pfb
+</pre>
+Either of these failures signals that your
+system doesn&rsquo;t have the fonts in the first place.
+<p/>A way of using the fonts that doesn&rsquo;t involve the sophistication of
+the <code>-Ppdf</code> mechanism is simply to load maps:
+<pre>
+  dvips -Pcmz -Pamz myfile -o myfile.ps
+</pre>
+You may encounter the same warning messages as listed above.
+<p/>If your system does not have the fonts, it won&rsquo;t have the
+configuration file either; however, it might have the configuration
+file without the fonts.  In either case, you need to
+<a href="FAQ-inst1cm.html">install the fonts</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html
new file mode 100644
index 00000000000..dac8d715163
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html
@@ -0,0 +1,56 @@
+<head>
+<title>UK TeX FAQ -- question label getbitmap</title>
+</head><body>
+<h3>Acquiring bitmap fonts</h3>
+<p/>When 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 CTAN.
+(There are separate sets for write-black and write-white printers, as
+well as sets at 120 dpi and 240 dpi.)
+<p/>Over the years, there have been regular requests that CTAN should hold
+a wider range of resolutions, but they were resisted for two reasons:
+<ul>
+<li> 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
+  &lsquo;engines&rsquo;, but nowadays one could not make any such assumption.
+<li> Given the above, justifying the space taken up by a huge array
+  of bitmap fonts.
+</ul>
+Fortunately, (La)TeX 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 <i>allcm</i>
+(distributed with TeX Live, at least; otherwise such a
+person should consult &ldquo;<a href="FAQ-useMF.html">the use of Metafont</a>)&rdquo;.
+<p/>If your output is to a PostScript-capable device, or if your output is
+destined to be converted to PDF, you should switch to
+using Type 1 versions of the CM fonts.  Two free
+sets are available; the older (<i>bakoma</i>) is
+somewhat less well produced than the <i>bluesky</i> fonts, which were
+originally professionally produced and sold, but were then donated to
+the public domain by their originators Y&amp;Y and Bluesky Research,
+in association with the AMS.  The two sets contain slightly
+different ranges of fonts, but you are advised to use the
+<i>bluesky</i> set except when <i>bakoma</i> is for some reason
+absolutely unavoidable.  In recent years, several other &lsquo;Metafont&rsquo; fonts
+have been converted to Type 1 format; it&rsquo;s common never to need to
+generate bitmap fonts for any purpose other than previewing (see
+
+<a href="FAQ-PSpreview.html">&ldquo;previewing documents with Type 1 fonts&rdquo;</a>),
+if even then.
+<p/>More modern fonts may be used in place of the Computer Modern set.  The
+<a href="FAQ-ECfonts.html">EC fonts</a> and the 
+<a href="FAQ-uselmfonts.html">Latin Modern fonts</a> are both close relatives of
+Computer Modern with wider ranges of glyphs to offer.
+<dl>
+<dt><tt><i>BaKoMa fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.zip">fonts/cm/ps-type1/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bakoma/">browse</a>)
+<dt><tt><i>Bluesky fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a>
+<dt><tt><i>CM fonts (write-black printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300.zip">fonts/cm/pk/pk300.zip</a>
+<dt><tt><i>CM fonts (write-white printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300w.zip">fonts/cm/pk/pk300w.zip</a>
+<dt><tt><i>EC fonts (Type 1 format)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>)
+<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html
new file mode 100644
index 00000000000..eaa0377987e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label gethelp</title>
+</head><body>
+<h3>How to get help</h3>
+<p/>So you&rsquo;ve looked at all relevant <a href="FAQ-whereFAQ.html">FAQs</a> you
+can find, you&rsquo;ve looked in any <a href="FAQ-books.html">books</a> you have, and
+scanned relevant <a href="FAQ-tutorialstar.html">tutorials</a>... and still you
+don&rsquo;t know what to do.
+<p/>If you are seeking a particular package or program, look on your own
+system first: you might already have it &mdash; the better TeX
+distributions contain a wide range of supporting material.  The
+CTAN Catalogue can also help: you can
+<a href="http://www.tex.ac.uk/search">search it</a>, or you can browse it
+
+&ldquo;<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">by topic</a>&rdquo;.
+A catalogue entry has a brief description of the package, and links to
+any known documentation on the net.  In fact, a large proportion of
+CTAN package directories now include documentation, so it&rsquo;s
+often worth looking at the catalogue entry for a package you&rsquo;re considering
+using.
+<p/>Failing all that, look to see if anyone else has had the problem
+before; there are two places where people ask: browse or search the
+newsgroup <i>comp.text.tex</i> via
+<a href="http://groups.google.com/group/comp.text.tex">Google groups</a>,
+and the mailing list <code>texhax</code> via its
+<a href="http://tug.org/pipermail/texhax/">archive</a>
+<p/>If those &ldquo;back question&rdquo; searches fail, you&rsquo;ll have to ask the world
+at large.  To ask a question on <i>comp.text.tex</i>, you can use
+your own news client (if you have one), or use the &ldquo;start a new
+topic&rdquo; button on <a href="http://groups.google.com/group/comp.text.tex">http://groups.google.com/group/comp.text.tex</a>.
+To ask a question on <code>texhax</code>, you may simply send mail to
+<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>, but it&rsquo;s probably better to subscribe to the
+list (via <a href="http://tug.org/mailman/listinfo/texhax">http://tug.org/mailman/listinfo/texhax</a>) 
+first &mdash; not everyone will answer to you as well as to the list.
+<p/>Do <b>not</b> try mailing the 
+<a href="FAQ-LaTeX3.html">LaTeX project team</a> or the maintainers of these
+FAQs for help; while both addresses reach experienced (La)TeX
+users, no small group can possibly have expertise in every area of
+usage so that the &ldquo;big&rdquo; lists are a far better bet.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html
new file mode 100644
index 00000000000..9ff4a89bdf6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label graph-pspdf</title>
+</head><body>
+<h3>Portable imported graphics</h3>
+<p/>A regular need is a document to be distributed in more than
+one format: commonly both PostScript and PDF.  The
+following advice is based on a post by one with much experience of
+dealing with the problem of dealing with EPS graphics in this
+case.
+<ul>
+<li> Don&rsquo;t specify a driver when loading loading whichever version of
+  the <i>graphics</i> package you use.  The scheme relies on the
+  distribution&rsquo;s ability to decide which driver is going to be used:
+  the choice is between <i>dvips</i> and PDFTeX, in this case.
+  Be sure to exclude options <code>dvips</code>, <code>pdftex</code> and
+  <code>dvipdfm</code> (<i>dvipdfm</i> is not used in this scheme,
+  but the aspirant PDF-maker may be using it for his output,
+  before switching to the scheme).
+<li> Use <code>\</code><code>includegraphics[...]{filename}</code> without
+  specifying the extension (i.e., neither <code>.eps</code> nor
+  <code>.pdf</code>).
+<li> For every <code>.eps</code> file you will be including, produce a
+  <code>.pdf</code> version, as described in 
+  <a href="FAQ-pdftexgraphics.html">Graphics in PDFLaTeX</a>.  Having
+  done this, you will have two copies of each graphic (a <code>.eps</code>
+  and a <code>.pdf</code> file) in your directory.
+<li> Use PDFLaTeX (rather than
+  LaTeX&ndash;<i>dvips</i>&ndash;distillation or
+  LaTeX&ndash;<i>dvipdfm</i>) to produce your PDF output.
+</ul>
+<i>Dvipdfm</i>&rsquo;s charms are less than attractive here: the
+document itself needs to be altered from its default
+(<i>dvips</i>) state, before <i>dvipdfm</i> will process it.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
new file mode 100644
index 00000000000..b0f03e19b76
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
@@ -0,0 +1,63 @@
+<head>
+<title>UK TeX FAQ -- question label graphicspath</title>
+</head><body>
+<h3>Importing graphics from &ldquo;somewhere else&rdquo;</h3>
+<p/>By default, graphics commands like <code>\</code><code>includegraphics</code> look
+&ldquo;wherever TeX files are found&rdquo; for the graphic file they&rsquo;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 (La)TeX
+sources.
+<p/>The simplest solution is to patch TeX&rsquo;s path, by changing the
+default path.  On most systems, the default path is taken from the
+environment variable <code>TEXINPUTS</code>, if it&rsquo;s present; you can adapt that
+to take in the path it already has, by setting the variable to
+<blockquote>
+<pre>
+TEXINPUTS=.:&lt;graphics path(s)&gt;:
+</pre>
+</blockquote><p>
+on a Unix system; on a Windows system the separator will be &ldquo;<code>;</code>&rdquo;
+rather than &ldquo;<code>:</code>&rdquo;.  The &ldquo;<code>.</code>&rdquo; is there to ensure
+that the current directory is searched first; the trailing
+&ldquo;<code>:</code>&rdquo; says &ldquo;patch in the value of <code>TEXINPUTS</code> from
+your configuration file, here&rdquo;.
+<p/>This method has the merit of efficiency ((La)TeX does <em>all</em> of
+the searches, which is quick), but it&rsquo;s always clumsy and may prove
+inconvenient to use in Windows setups (at least).
+<p/>The alternative is to use the <i>graphics</i> package command
+<code>\</code><code>graphicspath</code>; this command is of course also available to users
+of the <i>graphicx</i> and the <i>epsfig</i> packages.  The
+syntax of <code>\</code><code>graphicspath</code>&rsquo;s one argument is slightly odd: it&rsquo;s a
+sequence of paths (typically relative paths), each of which is
+enclosed in braces.  A slightly odd sample, given in the
+<i>graphics</i> bundle documentation, is:
+<blockquote>
+<pre>
+\graphicspath{{eps/}{tiff/}}
+</pre>
+</blockquote><p>
+however, if the security checks on your (La)TeX system allow, the
+path may be anything you choose (rather than strictly relative, like
+those above); note that the trailing &ldquo;<code>/</code>&rdquo; <em>is</em> required.
+<p/>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of
+graphics macros other than those from the graphics bundle &mdash; in
+particular, those of the outdated <i>epsf</i> and
+<i>psfig</i> packages are immune.
+<p/>The disadvantage of the <code>\</code><code>graphicspath</code> method is inefficiency.  The
+package will call (La)TeX once for each entry in the list, which is
+itself slows things.  More seriously, TeX remembers the file name,
+thus effectively losing memory, every time it&rsquo;s
+asked to look up a file, so a document that uses a huge number of
+graphical inputs could be embarrassed by lack of memory.
+<p/>If your document is split into a variety of directories, and each
+directory has its associated graphics, the <i>import</i> package
+may well be the thing for you; see the discussion 
+in the question &ldquo;
+<a href="FAQ-docotherdir.html">bits of document in other directories</a>
+&rdquo;.
+<dl>
+<dt><tt><i>graphics bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>)
+<dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html
new file mode 100644
index 00000000000..06edd868751
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label grmaxwidth</title>
+</head><body>
+<h3>Limit the width of imported graphics</h3>
+<p/>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.
+<p/>You do this by delving into the innards of the graphics package (which
+of course needs a little LaTeX internals programming):
+<blockquote>
+<pre>
+\makeatletter
+\def\maxwidth{%
+  \ifdim\Gin@nat@width&gt;\linewidth
+    \linewidth
+  \else
+    \Gin@nat@width
+  \fi
+}
+\makeatother
+</pre>
+</blockquote><p>
+This defines a &ldquo;variable&rdquo; width which has the properties you want.
+Replace <code>\</code><code>linewidth</code> if you have a different constraint on the width
+of the graphic.
+<p/>Use the command as follows:
+<blockquote>
+<pre>
+\includegraphics[width=\maxwidth]{figure}
+</pre>
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html
new file mode 100644
index 00000000000..05ddfdb9a15
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html
@@ -0,0 +1,47 @@
+<head>
+<title>UK TeX FAQ -- question label gutter</title>
+</head><body>
+<h3>Why is the inside margin so narrow?</h3>
+<p/>If you give the standard classes the <code>twoside</code> 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.
+<p/>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&rsquo;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.
+<p/>This is all very fine in the abstract, but in practical book(let)
+production it only works &ldquo;sometimes&rdquo;.
+<p/>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
+&ldquo;perfect&rdquo; binding, the effect will again be good.
+<p/>However, almost any &ldquo;quality&rdquo; book-binder will need some of your
+paper to grab hold of, and a book bound in such a way won&rsquo;t exhibit
+the treasured symmetry unless you&rsquo;ve done something about the margin
+settings.
+<p/>The packages recommended in 
+&ldquo;<a href="FAQ-marginpkgs.html">setting up margins</a>&rdquo; mostly have provision for
+a &ldquo;binding offset&rdquo; or a &ldquo;binding correction&rdquo; &mdash; search for
+&ldquo;binding&rdquo; in the manuals (<i>vmargin</i> doesn&rsquo;t help, here).
+<p/>If you&rsquo;re doing the job by hand (see 
+<a href="FAQ-marginmanual.html">manual margin setup</a>), the trick is to
+calculate your page and margin dimensions as normal, and then:
+<ul>
+<li> subtract the binding offset from <code>\</code><code>evensidemargin</code>, and
+<li> add the binding offset to <code>\</code><code>oddsidemargin</code>.
+</ul>
+which can be achieved by:
+<blockquote>
+<pre>
+\addtolength{\evensidemargin}{-offset}
+\addtolength{\oddsidemargin}{offset}
+</pre>
+</blockquote><p>
+(substituting something sensible like &ldquo;<code>5mm</code>&rdquo; for
+&ldquo;<code>offset</code>&rdquo;, above).
+<p/>The above may not be the best you can do: you may well choose to
+change the <code>\</code><code>textwidth</code> in the presence of the binding offset; but
+the changes do work for constant <code>\</code><code>textwidth</code>.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html
new file mode 100644
index 00000000000..0d74b368834
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label hash</title>
+</head><body>
+<h3>Defining macros within macros</h3>
+<p/>The way to think of this is that <code>##</code> gets replaced by <code>#</code> in just the
+same way that <code>#1</code> gets replaced by &lsquo;whatever is the first argument&rsquo;.
+<p/>So if you define a macro and use it as:
+<blockquote>
+<pre>
+\def\a#1{+++#1+++#1+++#1+++}  \a{b}
+</pre>
+</blockquote><p>
+the macro expansion produces &lsquo;+++b+++b+++b+++&rsquo;,
+which people find normal.  However, if we now replace part of the macro:
+<blockquote>
+<pre>
+\def\a#1{+++#1+++\def\x #1{xxx#1}}
+</pre>
+</blockquote><p>
+<code>\</code><code>a{b}</code> will expand to &lsquo;+++b+++<code>\def\x b{xxxb}</code>&rsquo;.  This
+defines <code>\</code><code>x</code> to be a macro <em>delimited</em> by <code>b</code>, and taking no
+arguments, which people may find strange, even though it is just a
+specialisation of the example above.  If you want <code>\</code><code>a</code> to
+define <code>\</code><code>x</code> to be a macro with one argument, you need to write:
+<blockquote>
+<pre>
+\def\a#1{+++#1+++\def\x ##1{xxx##1}}
+</pre>
+</blockquote><p>
+and <code>\</code><code>a{b</code>} will expand to 
+&lsquo;+++b+++<code>\def\x #1{xxx#1}</code>&rsquo;, because <code>#1</code> gets replaced by &lsquo;b&rsquo;
+and <code>##</code> gets replaced by <code>#</code>.
+<p/>To nest a definition inside a definition inside a definition then
+you need <code>####1</code>, as at each stage <code>##</code> is replaced by
+<code>#</code>.  At the next level you need 8 <code>#</code>s each time, and so on.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html
new file mode 100644
index 00000000000..1ebcaea92f0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label howmanypp</title>
+</head><body>
+<h3>How many pages are there in my document?</h3>
+<p/>Simple documents (those that start at page 1, and don&rsquo;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 <i>lastpage</i> package in its <code>LastPage</code> label.
+<p/>For more complicated documents (most obviously, books with frontmatter
+in a different series of page numbers) this simple approach will not
+do.
+<p/>The <i>count1to</i> package defines a label <code>TotalPages</code>; this is
+the value of its copy of <code>\</code><code>count1</code> (a reserved TeX count
+register) at the end of the document.
+<p/>Package <i>totpages</i> defines a label <code>TotPages</code>, but it also
+makes the register it uses available as a LaTeX counter,
+<code>TotPages</code>, which you can also reference via <code>\</code><code>theTotPages</code>.  Of
+course, the counter <code>TotPages</code> is asynchronous in the same way that
+page numbers are, but snapshots may safely be taken in the output
+routine.
+<p/>The <i>memoir</i> class defines two counters <code>lastpage</code> and
+<code>lastsheet</code>, which are set (after the first run of a document)
+to the equivalent of the <code>LastPage</code> label and the
+<code>TotalPages</code> labels.
+<p/>Both <i>count1to</i> and <i>totpages</i> need the support of
+the <i>everyshi</i> package.
+<dl>
+<dt><tt><i>count1to.sty and everyshi.sty</i></tt><dd>
+  Distributed in <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>)
+<dt><tt><i>lastpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.zip">macros/latex/contrib/lastpage</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lastpage/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>totpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/totpages.zip">macros/latex/contrib/totpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/totpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/totpages/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html
new file mode 100644
index 00000000000..1ea5aaf2e27
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label htmlbib</title>
+</head><body>
+<h3>Making HTML of your Bibliography</h3>
+<p/>A neat solution is offered by the <i>noTeX</i> bibliography style.
+This style produces a <code>.bbl</code> file which is in fact a series of
+HTML &lsquo;<code>P</code>&rsquo; elements of class <code>noTeX</code>, and which
+may therefore be included in an HTML file.  Provision is made
+for customising your bibliography so that its content when processed by
+<i>noTeX</i> is different from that presented when it is processed
+in the ordinary way by (La)TeX.
+<p/>A thorough solution is offered by <i>bib2xhtml</i>; 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
+<i>perl</i> script.
+<p/>A more conventional translator is the <i>awk</i> script
+<i>bbl2html</i>, which translates the <code>.bbl</code> file you&rsquo;ve generated:
+a sample of the script&rsquo;s output may be viewed on the web, at
+<a href="http://rikblok.cjb.net/lib/refs.html">http://rikblok.cjb.net/lib/refs.html</a>
+<dl>
+<dt><tt><i>bbl2html.awk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/misc/bbl2html.awk">biblio/bibtex/utils/misc/bbl2html.awk</a>
+<dt><tt><i>bib2xhtml</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.zip">biblio/bibtex/utils/bib2xhtml</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bib2xhtml/">browse</a>)
+<dt><tt><i>noTeX.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/misc/noTeX.bst">biblio/bibtex/utils/misc/noTeX.bst</a>
+</dl>
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html
new file mode 100644
index 00000000000..caaa70653c6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html
@@ -0,0 +1,44 @@
+<head>
+<title>UK TeX FAQ -- question label hyper</title>
+</head><body>
+<h3>Making hypertext documents from TeX</h3>
+<p/>If you want on-line hypertext with a (La)TeX source, probably on the
+World Wide Web, there are four technologies to consider:
+<ul>
+<li> Direct <a href="FAQ-LaTeX2HTML.html">(La)TeX conversion to HTML</a>;
+
+<li> Use <a href="FAQ-texinfo.html"><i>Texinfo</i></a>,
+  and use the <i>info</i> viewer, or convert the <i>texinfo</i>
+  to HTML;
+<li> Use Adobe Acrobat, which will preserve your typesetting
+  perfectly
+  <a href="FAQ-acrobat.html">Making Acrobat PDF documents from LaTeX</a>;
+<li> The hyperTeX conventions (standardised <code>\</code><code>special</code>
+  commands); there are supporting macro packages for Plain TeX and
+  LaTeX).
+</ul>
+<p/>The HyperTeX project extended the functionality of all the
+LaTeX cross-referencing commands (including the table of contents)
+to produce <code>\</code><code>special</code> commands which are parsed by DVI processors
+conforming to the HyperTeX guidelines;
+it provides general hypertext links, including those
+to external documents.
+<p/>The HyperTeX specification says that conformant viewers/translators
+must recognize the following set of <code>\</code><code>special</code> commands:
+<dl>
+<dt>href:<dd> <code>html:&lt;a href = "href_string"&gt;</code>
+<dt>name:<dd> <code>html:&lt;a name = "name_string"&gt;</code>
+<dt>end:<dd> <code>html:&lt;/a&gt;</code>
+<dt>image:<dd> <code>html:&lt;img src = "href_string"&gt;</code>
+<dt>base_name:<dd> <code>html:&lt;base href = "href_string"&gt;</code>
+</dl>
+<p/>The <em>href</em>, <em>name</em> and <em>end</em> commands are used to do
+the basic hypertext operations of establishing links between sections
+of documents. 
+<p/>Further details are available on <a href="http://arXiv.org/hypertex/">http://arXiv.org/hypertex/</a>; there
+are two commonly-used implementations of the specification, a
+modified <i>xdvi</i> and (recent releases of)
+<i>dvips</i>. Output from the latter may be used in recent
+releases of <i>ghostscript</i> or Acrobat Distiller.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html
new file mode 100644
index 00000000000..49ca9f2012c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label hyperdupdest</title>
+</head><body>
+<h3>PDFTeX destination ... ignored</h3>
+<p/>The warning:
+<blockquote>
+<pre>
+! pdfTeX warning (ext4): destination with the same identifier
+(name{page.1}) has been already used, duplicate ignored
+</pre>
+
+</blockquote><p>
+arises because of duplicate page numbers in your document.  The
+problem is usually soluble: see 
+<a href="FAQ-pdfpagelabels.html">PDF page destinations</a> &mdash; which
+answer also describes the problem in more detail.
+<p/>If the identifier in the message is different, for example
+<code>name{figure.1.1}</code>, the problem is (usually) due to a problem of
+package interaction.  Some packages are simply incompatible with
+<i>hyperref</i>, but most work simply by ignoring it.  In most
+cases, therefore, you should load your package before you load
+<i>hyperref</i>, and <i>hyperref</i> will patch things up so
+that they work, so you can utilise your (patched) package <em>after</em>
+loading both:
+<blockquote>
+  <code>\</code><code>usepackage{<em>your package</em>}</code><br>
+  <code>...</code><br>
+  <code>\</code><code>usepackage[<em>opts</em>]{hyperref}</code><br>
+  <code>...</code><br>
+  &lt;<i>code that uses your package</i>&gt;
+</blockquote><p>
+For example:
+<blockquote>
+<pre>
+\usepackage{float}          % defines \newfloat
+...
+\usepackage[...]{hyperref}  % patches \newfloat
+...
+\newfloat{...}{...}{...}
+</pre>
+</blockquote><p>
+
+You should load packages in this order as a matter of course, unless
+the documentation of a package says you <em>must</em> load it after
+<i>hyperref</i>.  (There aren&rsquo;t many packages that require to be
+loaded after hyperref: one such is <i>memoir</i>&rsquo;s
+&ldquo;<i>hyperref</i> fixup&rdquo; package <i>memhfixc</i>.)
+<p/>If loading your packages in the (seemingly) &ldquo;correct&rdquo; order doesn&rsquo;t
+solve the problem, you need to <a href="FAQ-gethelp.html">seek further help</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html
new file mode 100644
index 00000000000..a7bf8f25ab3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label hyphen</title>
+</head><body>
+<h3>How does hyphenation work in TeX?</h3>
+<p/>Everyone knows what hyphenation is: we see it in most books we read,
+and (if we&rsquo;re alert) will spot occasional ridiculous mis-hyphenation
+(at one time, British newspapers were a fertile source).
+<p/>Hyphenation styles are culturally-determined, and the same language
+may be hyphenated differently in different countries &mdash; 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.
+<p/>TeX uses a pretty good system for hyphenation (originally designed
+by Frank Liang), and while it&rsquo;s capable of missing &ldquo;sensible&rdquo;
+hyphenation points, it seldom selects grossly wrong ones.  The
+algorithm matches candidates for hyphenation against a set of
+&ldquo;hyphenation patterns&rdquo;.  The candidates for hyphenation must be
+sequences of letters (or other single characters that TeX may be
+persuaded to think of as letters) &mdash; things such as TeX&rsquo;s
+<code>\</code><code>accent</code> primitive interrupt hyphenation.
+<p/>Sets of hyphenation patterns are usually derived from analysis of
+a list of valid hyphenations (the process of derivation, using a tool
+called <i>patgen</i>, is not ordinarily a participatory sport).
+<p/>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
+languages, a <a href="FAQ-newlang.html">partial reinstallation</a> is necessary.
+<p/>TeX provides two &ldquo;user-level&rdquo; commands for control of
+hyphenation: <code>\</code><code>language</code> (which selects a hyphenation style), and
+<code>\</code><code>hyphenation</code> (which gives explicit instructions to the hyphenation
+engine, overriding the effect of the patterns).
+<p/>The ordinary LaTeX user need not worry about <code>\</code><code>language</code>, since
+it is very thoroughly managed by the <i>babel</i> package; use of
+<code>\</code><code>hyphenation</code> is discussed in
+  the context of
+
+<a href="FAQ-nohyph.html">hyphenation failure</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html
new file mode 100644
index 00000000000..4b1eb28c382
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label hyphenaccents</title>
+</head><body>
+<h3>Accented words aren&rsquo;t hyphenated</h3>
+<p/>TeX&rsquo;s algorithm for hyphenation gives up when it encounters an
+<code>\</code><code>accent</code> command; there are good reasons for this, but it means
+that quality typesetting in non-English languages can be difficult.
+<p/>For TeX macro packages, you can avoiding the effect by using an
+appropriately encoded font (for example, a Cork-encoded font &mdash; see
+<a href="FAQ-ECfonts.html">the EC fonts</a>) which contains accented
+letters as single glyphs.  LaTeX users can achieve this end simply
+by adding the command
+<pre>
+  \usepackage[T1]{fontenc}
+</pre>
+to the preamble of their document.  Other encodings (notably
+LY1, once promoted by Y&amp;Y inc) may be used
+in place of T1.  Indeed, most current 8-bit TeX font
+encodings will &lsquo;work&rsquo; with the relevant sets of hyphenation patterns. 
+<p/>One might hope that, with the many aspirant successors to TeX such
+as
+  <a href="FAQ-omegaleph.html">Omega</a>, <a href="FAQ-luatex.html">LuaTeX</a> and
+  <a href="FAQ-extex.html">ExTeX</a>,
+
+all of which base their operations on Unicode, that the whole basis of
+encodings will change.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html
new file mode 100644
index 00000000000..50bcaf4f25e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label hyphexcept</title>
+</head><body>
+<h3>Hyphenation exceptions</h3>
+<p/>While TeX&rsquo;s hyphenation rules are good, they&rsquo;re not infallible: you
+will occasionally find words TeX just gets <em>wrong</em>.  So for
+example, TeX&rsquo;s default hyphenation rules (for American English) don&rsquo;t
+know the word &ldquo;<em>manuscript</em>&rdquo;, and since it&rsquo;s a long word you
+may find you need to hyphenate it.  You <em>can</em> &ldquo;write the
+hyphenation out&rdquo; each time you use the word:
+<blockquote>
+<pre>
+... man\-u\-script ...
+</pre>
+</blockquote><p>
+Here, each of the <code>\</code><code>-</code> commands is converted to a hyphenated break,
+if (<em>and only if</em>) necessary.
+<p/>That technique can rapidly become tedious: you&rsquo;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:
+<blockquote>
+<pre>
+\hyphenation{man-u-script}
+</pre>
+</blockquote><p>
+and the hyphenation would be set for the whole document.  Barbara
+Beeton publishes articles containing lists of these &ldquo;hyphenation
+exceptions&rdquo;, in <i>TUGboat</i>; the hyphenation &lsquo;man-u-script&rsquo;
+comes from one of those articles.
+<p/>What if you have more than one language in your document?  Simple:
+select the appropriate language, and do the same as above:
+<blockquote>
+<pre>
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{re-cher-cher}
+</pre>
+</blockquote><p>
+(nothing clever here: this is the &ldquo;correct&rdquo; hyphenation of the word,
+in the current tables).  However, there&rsquo;s a problem here: just as
+words with accents in them won&rsquo;t break, so <code>\</code><code>hyphenation</code> commands
+with accents in them produce an error:
+<blockquote>
+<pre>
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{r\'e-f\'e-rence}
+</pre>
+</blockquote><p>
+tells us that the hyphenation is &ldquo;improper&rdquo;, and that it will be &ldquo;flushed&rdquo;.
+But, just as hyphenation of words is enabled by selecting an 8-bit
+font encoding, so <code>\</code><code>hyphenation</code> commands are rendered proper again
+by selecting that same 8-bit font encoding.  For the hyphenation
+patterns provided in the usual distributions, the encoding is
+<a href="FAQ-ECfonts.html">Cork</a>, so the complete sequence is:
+<blockquote>
+<pre>
+\usepackage[T1]{fontenc}
+\usepackage[french]{babel}
+\selectlanguage{french}
+\hyphenation{r\'e-f\'e-rence}
+</pre>
+</blockquote><p>
+<p/>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.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html
new file mode 100644
index 00000000000..a2da4df0c21
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html
@@ -0,0 +1,78 @@
+<head>
+<title>UK TeX FAQ -- question label hyphoff</title>
+</head><body>
+<h3>Stopping all hyphenation</h3>
+<p/>It may seem an odd thing to want to do (after all, one of TeX&rsquo;s
+great advertised virtues is the quality of its hyphenation) but it&rsquo;s
+sometimes necessary.  The real problem is, that the quality of
+TeX&rsquo;s output is by default largely dependent on the presence of
+hyphenation; if you want to abandon hyphenation, something has to
+give.
+<p/>TeX (slightly confusingly) offers four possible mechanisms for
+suppressing hyphenation (there were only two prior to the extensions
+that arrived with TeX version 3).
+<p/>First, one can set the hyphenation penalties <code>\</code><code>hyphenpenalty</code> and
+<code>\</code><code>exhyphenpenalty</code> to an &lsquo;infinite&rsquo; value (that is to say, 10000).
+This means that all hyphenations will sufficiently penalise the line
+that would contain them, that the hyphenation won&rsquo;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.
+<p/>Second, one can select a language for which no hyphenation patterns
+exist.  Some distributions create a language <code>nohyphenation</code>,
+and the <i>hyphenat</i> package uses this technique for its
+<code>\</code><code>nohyphens</code> command which sets its argument without any
+hyphenation.  You can load <i>hyphenat</i> with the command
+<blockquote>
+  <code>\</code><code>usepckage[none]{hyphenat}</code>
+</blockquote><p>
+to prevent any hyphenation in a single-language document.  The
+technique cannot work in a document in which <i>babel</i> controls
+language selection, since <i>babel</i> incorporates hyphenation
+change into its language change facilities.
+<p/>Third, one can set <code>\</code><code>left-</code> and/or <code>\</code><code>righthyphenmin</code> 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).
+<p/>Fourth, one can suppress hyphenation for all text using the current
+font by the command
+<blockquote>
+<pre>
+\hyphenchar\font=-1
+</pre>
+</blockquote><p>
+This isn&rsquo;t a particularly practical way for users to suppress
+hyphenation &mdash; the command has to be issued for every font the
+document uses &mdash; but it&rsquo;s how LaTeX itself suppresses hyphenation
+in <code>tt</code> and other fixed-width fonts.
+<p/>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.
+<p/>Contrariwise, if you are writing a multilanguage document using the
+<i>babel</i> package, you <em>cannot</em> suppress hyphenation
+throughout using either the no-hyphens language or the hyphen minima:
+all those values get changed at a <i>babel</i> language switch: use
+the penalties instead.
+<p/>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 (La)TeX run will bombard you with warnings about overfull
+and underfull lines.  To avoid this you have two options.
+<p/>The simplest route is to use <code>\</code><code>sloppy</code> (or its environment version
+<code>sloppypar</code>), and have TeX stretch what would otherwise
+be underfull lines to fill the space offered, while prematurely
+wrapping overfull lines and stretching the remainder.  
+<p/>Alternatively, you may set the text <a href="FAQ-ragright.html">ragged right</a>,
+and at least get rid of the overfull lines; this technique is
+&lsquo;traditional&rsquo; (in the sense that typists do 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.)
+<dl>
+<dt><tt><i>hyphenat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html
new file mode 100644
index 00000000000..7376c7dfe99
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html
@@ -0,0 +1,53 @@
+<head>
+<title>UK TeX FAQ -- question label i18nbib</title>
+</head><body>
+<h3>Non-english bibliographies</h3>
+<p/>Like so much of early (La)TeX software, BibTeX&rsquo;s assumptions were
+firmly rooted in what its author knew well, viz., academic papers in
+English (particularly those with a mathematical bent).  BibTeX&rsquo;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.
+<p/>For the user whose language is not English, there are several
+alternatives.  The simplest is to provide translations of BibTeX
+styles into the required language: the solitary <i>finplain.bst</i>
+does that for Finnish; others one can find are for Danish
+(<i>dk-bib</i>), French (<i>bib-fr</i>), German
+(<i>bibgerm</i>), Norwegian (<i>norbib</i>) and Swedish
+(<i>swebib</i>) bundles (of which the <i>bib-fr</i> set is the
+most extensive).  The <i>spain</i> style implements a traditional
+Spanish citation style.
+<p/>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 &ldquo;general&rdquo; problem are available &mdash; that offered by
+<i>babelbib</i>, and the 
+<a href="FAQ-custbib.html"><i>custom-bib</i> mechanism for generating styles</a>.
+<p/><i>Babelbib</i> (which is a development of the ideas of the
+<i>bibgerm</i> package) co-operates with <i>babel</i> 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
+&lsquo;knows about&rsquo;, but the documentation includes instructions on defining
+commands for other languages.  <i>Babelbib</i> comes with its own
+set of bibliography styles, which could be a restriction if there
+wasn&rsquo;t also a link from <i>custom-bib</i>.
+<p/>The <i>makebst</i> menu of <i>custom-bib</i> allows you to
+choose a language for the BibTeX style you&rsquo;re generating (there are
+14 languages to choose; it looks as if <i>spain.bst</i>, 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
+<i>babelbib</i>; if you do so, you&rsquo;re getting the best of both
+worlds &mdash; formatting freedom from <i>custom-bib</i> and linguistic
+freedom via the extensibility of <i>babelbib</i>
+<dl>
+<dt><tt><i>babelbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse</a>)
+<dt><tt><i>bib-fr bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/bib-fr.zip">biblio/bibtex/contrib/bib-fr</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/bib-fr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/bib-fr/">browse</a>)
+<dt><tt><i>bibgerm bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/germbib.zip">biblio/bibtex/contrib/germbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/germbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/germbib/">browse</a>)
+<dt><tt><i>custom-bib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>)
+<dt><tt><i>finplain.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/misc/finplain.bst">biblio/bibtex/contrib/misc/finplain.bst</a>
+<dt><tt><i>norbib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/norbib.zip">biblio/bibtex/contrib/norbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/norbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/norbib/">browse</a>)
+<dt><tt><i>spain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.zip">biblio/bibtex/contrib/spain</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/spain/">browse</a>)
+<dt><tt><i>swebib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.zip">biblio/bibtex/contrib/swebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/swebib/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html
new file mode 100644
index 00000000000..7f26397e5c5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html
@@ -0,0 +1,80 @@
+<head>
+<title>UK TeX FAQ -- question label ifpdf</title>
+</head><body>
+<h3>Am I using PDFTeX?</h3>
+<p/>It&rsquo;s often useful to know whether your macros are operating within
+PDFTeX or within (&ldquo;normal&rdquo;) TeX; getting the right answer is
+surprisingly tricky.
+<p/>Suppose you need to test whether your output will be PDF or
+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
+<code>\</code><code>pdfoutput</code>.  So you try
+<blockquote>
+<pre>
+\ifx\pdfoutput\undefined
+  &lt;not running PDFTeX&gt;
+\else
+  &lt;running PDFTeX&gt;
+\fi
+</pre>
+</blockquote><p>
+Except that neither branch of this conditional is rock-solid.  The
+first branch can be misleading, since the &ldquo;awkward&rdquo; user could have
+written:
+<blockquote>
+<pre>
+\let\pdfoutput\undefined
+</pre>
+</blockquote><p>
+so that your test will falsely choose the first alternative.  While
+this is a theoretical problem, it is unlikely to be a major one.
+<p/>More important is the user who loads a package that uses
+LaTeX-style testing for the command name&rsquo;s existence (for example,
+the LaTeX <i>graphics</i> package, which is useful even to the
+Plain TeX user).  Such a package may have gone ahead of you, so the
+test may need to be elaborated:
+<blockquote>
+<pre>
+\ifx\pdfoutput\undefined
+  &lt;not running PDFTeX&gt;
+\else
+  \ifx\pdfoutput\relax
+    &lt;not running PDFTeX&gt;
+  \else
+    &lt;running PDFTeX&gt;
+  \fi
+\fi
+</pre>
+</blockquote><p>
+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.
+<p/>However, if you need to know whether you&rsquo;re creating PDF
+output, you also need to know about the value of <code>\</code><code>pdfoutput</code>:
+<blockquote>
+<pre>
+\ifx\pdfoutput\undefined
+  &lt;not running PDFTeX&gt;
+\else
+  \ifx\pdfoutput\relax
+    &lt;not running PDFTeX&gt;
+  \else
+    &lt;running PDFTeX, with...&gt;
+    \ifnum\pdfoutput&gt;0
+      &lt;...PDF output&gt;
+    \else
+      &lt;...DVI output&gt;
+    \fi
+  \fi
+\fi
+</pre>
+</blockquote><p>
+The above is, in essence, what Heiko Oberdiek&rsquo;s <i>ifpdf</i>
+package does; the reasoning is the FAQ&rsquo;s interpretation of
+Heiko&rsquo;s explanation.
+<dl>
+<dt><tt><i>ifpdf.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html
new file mode 100644
index 00000000000..2f7959add31
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html
@@ -0,0 +1,96 @@
+<head>
+<title>UK TeX FAQ -- question label impgraph</title>
+</head><body>
+<h3>How to import graphics into (La)TeX documents</h3>
+<p/>Knuth, when designing the current version of TeX back in the early
+1980s, could discern no &ldquo;standard&rdquo; 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
+DVI drivers; TeX documents would control the drivers by
+means of 
+<a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>.
+<p/>There is therefore a straightforward way for anyone to import graphics
+into their document: read the specification of the <code>\</code><code>special</code>
+commands your driver uses, and &lsquo;just&rsquo; code them.  This is the
+hair-shirt approach: it definitely works, but it&rsquo;s not for everyone.
+<p/>Over the years, therefore, &ldquo;graphics inclusion&rdquo; packages have sprung
+up; most were designed for inclusion of
+
+<a href="FAQ-eps.html">Encapsulated PostScript graphics</a> &mdash;
+which has become the <em>lingua franca</em> of graphics inclusion over
+the last decade or so.
+<p/>Notable examples are the <i>epsf</i> package (distributed with
+<i>dvips</i>) and the <i>psfig</i> package.  (Both of these
+packages were designed to work well with both Plain TeX and
+LaTeX 2.09; they are both still available.)  All such packages were
+tied to a particular DVI driver (<i>dvips</i>, in
+the above two cases), but their code could be configured for others.
+<p/>The obvious next step was to make the code configurable dynamically.
+The LaTeX standard <i>graphics</i> package and its derivatives
+made this step: it is strongly preferred for all current work.  It can
+also be used (with the help of the <i>miniltx</i> &ldquo;LaTeX
+emulator&rdquo; and the <i>graphicx.tex</i> front-end) in documents
+written in Plain TeX.
+<p/>The <i>graphics</i> package takes a variety of &ldquo;driver
+options&rdquo; &mdash; package options that select code to generate the
+commands appropriate to the DVI driver in use.  In most cases,
+your (La)TeX distribution will provide a <i>graphics.cfg</i> file
+that will select the correct driver for what you&rsquo;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).
+<p/>The <i>graphics</i> 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, <code>\</code><code>includegraphics</code>,
+takes one optional argument, which specifies  the bounding box of the
+graphics to be included.
+<p/>The <i>graphicx</i> package uses the facilities of of
+<i>graphics</i> behind a rather more sophisticated command syntax
+to provide a very powerful version of the <code>\</code><code>includegraphics</code>
+command.  <i>graphicx</i>&rsquo;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 PostScript, and some of its
+combinations are simply not possible with the <i>graphics</i>
+package version.
+<p/>The <i>epsfig</i> package provides the same facilities as
+<i>graphicx</i>, but via a <code>\</code><code>psfig</code> command (also known as
+<code>\</code><code>epsfig</code>), capable of emulating
+the behaviour (if not the bugs) the old <i>psfig</i> package.
+<i>Epsfig</i> also supplies homely support for former users of the
+<i>epsf</i> package.  However, there&rsquo;s a support issue: if you
+declare you&rsquo;re using <i>epsfig</i>, any potential mailing list or
+usenet helper has to clear out of the equation the possibility that
+you&rsquo;re using &ldquo;old&rdquo; <i>epsfig</i>, so that support is slower
+coming than it would otherwise be.
+<p/>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&rsquo;s
+name tends not to imply that it&rsquo;s exclusively related to PostScript
+graphics.  The reasoning also excludes <i>epsfig</i>, of course.)
+<p/>A wide variety of detailed techniques and tricks have been developed
+over the years, and Keith Reckdahl&rsquo;s <i>epslatex</i> outlines them
+in compendious detail: this highly recommendable document is available
+from CTAN.  An invaluable review of the practicalities of
+exchanging graphics between sites,
+
+&ldquo;<a href="http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf">Graphics for Inclusion in Electronic Documents</a>&rdquo;
+
+has been written by Ian Hutchinson; the document isn&rsquo;t on CTAN,
+but may also be
+
+<a href="http://silas.psfc.mit.edu/elec_fig/">browsed on the Web</a>.
+<dl>
+<dt><tt><i>epsf.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/epsf/epsf.tex">macros/generic/epsf/epsf.tex</a>
+<dt><tt><i>epsfig.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle
+<dt><tt><i>epslatex.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a>; the document is also available
+  in PostScript format as <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a>
+<dt><tt><i>graphics.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>)
+<dt><tt><i>graphicx.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle
+<dt><tt><i>miniltx.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>)
+<dt><tt><i>psfig.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/psfig.zip">nonfree/graphics/psfig</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/psfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/graphics/psfig/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html
new file mode 100644
index 00000000000..2cccad6434f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label inclplain</title>
+</head><body>
+<h3>Including Plain TeX files in LaTeX</h3>
+<p/>LaTeX, though originally <a href="FAQ-LaTeXandPlain.html">based on Plain TeX</a>, does not
+contain all of Plain TeX&rsquo;s commands.  Worse, some Plain TeX
+command names appear in LaTeX, with different semantics.  As a
+result, special measures need to be taken to allow general Plain TeX
+documents (or parts of documents) to be typeset within LaTeX.
+<p/>The truly reliable way is to translate the Plain TeX commands, to
+produce an equivalent of the original&rsquo;s semantics.  However, this is
+not practical in many circumstances, and for those occasions, the
+<i>plain</i> package will often come to your aid.  The package
+defines a <code>plain</code> environment, in which a Plain TeX
+document may be processed:
+<blockquote>
+<pre>
+\begin{plain}
+  \input{plain-doc}
+\end{plain}
+</pre>
+</blockquote><p>
+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&rsquo;s not often easy), but
+the environment saves a lot of work on many occasions.
+<dl>
+<dt><tt><i>plain.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html
new file mode 100644
index 00000000000..7a758f34ee1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label include</title>
+</head><body>
+<h3>What&rsquo;s going on in my <code>\</code><code>include</code> commands?</h3>
+<p/>The original LaTeX provided the <code>\</code><code>include</code> command to address the
+problem of long documents: with the relatively slow computers of the
+time, the companion <code>\</code><code>includeonly</code> facility was a boon.  With the
+vast increase in computer speed, <code>\</code><code>includeonly</code> 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.
+<p/>In order for <code>\</code><code>includeonly</code> to work, <code>\</code><code>include</code> makes a separate
+<code>.aux</code> file for each included file, and makes a &lsquo;checkpoint&rsquo; of
+important parameters (such as page, figure, table and footnote
+numbers); as a direct result, it <em>must</em> clear the current page
+both before and after the <code>\</code><code>include</code> command.  What&rsquo;s more, this
+mechanism doesn&rsquo;t work if a <code>\</code><code>include</code> command appears in a file
+that was <code>\</code><code>include</code>d itself: LaTeX diagnoses this as an error.
+<p/>So, we can now answer the two commonest questions about <code>\</code><code>include</code>:
+<ul>
+<li> Why does LaTeX throw a page before and after <code>\</code><code>include</code>
+  commands?
+<p/>  Answer: because it has to.  If you don&rsquo;t like it, replace the
+  <code>\</code><code>include</code> command with <code>\</code><code>input</code> &mdash; you won&rsquo;t be able to use
+  <code>\</code><code>includeonly</code> any more, but you probably don&rsquo;t need it anyway, so
+  don&rsquo;t worry.
+<p/><li> Why can&rsquo;t I nest <code>\</code><code>include</code>d files? &mdash; I always used to be
+  able to under LaTeX 2.09.
+<p/>  Answer: in fact, you couldn&rsquo;t, even under LaTeX 2.09, but the failure
+  wasn&rsquo;t diagnosed.  However, since you were happy with the behaviour
+  under LaTeX 2.09, replace the <code>\</code><code>include</code> commands with <code>\</code><code>input</code>
+  commands (with <code>\</code><code>clearpage</code> as appropriate).
+</ul>
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html
new file mode 100644
index 00000000000..366d97da0c9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label inputlev</title>
+</head><body>
+<h3>Capacity exceeded &mdash; input levels</h3>
+<p/>The error
+<pre>
+! TeX capacity exceeded, sorry [text input levels=15].
+</pre>
+
+is caused by nesting your input too deeply.  You can provoke it with
+the trivial (Plain TeX) file <i>input.tex</i>, which contains
+nothing but: 
+<pre>
+\input input
+</pre>
+In the real world, you are unlikely to encounter the error with a
+modern TeX distribution.  TeTeX (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.
+<p/>However, for those improbable (or machine-generated) situations,
+some distributions offer the opportunity to adjust the parameter
+<code>max_in_open</code> in a configuration file.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html
new file mode 100644
index 00000000000..7ffb88aba90
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label inst-miktex*</title>
+</head><body>
+<h3>Installation using MiKTeX package manager</h3>
+<p/>Packages for use with MiKTeX are maintained very efficiently by the
+project managers (new packages and updates on 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.
+<p/>MiKTeX maintains a database of packages it &ldquo;knows about&rdquo;,
+together with (coded) installation instructions that enable it to
+install the packages with minimal user intervention; you can update
+the database over the internet.
+<p/>If MiKTeX does know about a package you need installed, it&rsquo;s worth
+using the system:
+first, open the MiKTeX packages window: click on
+  <code>Start</code>-&gt; 
+  <code>Programs</code>-&gt; 
+  <code>MiKTeX</code>-&gt; 
+  <code>MiKTeX Options</code>, and select the
+  <code>Packages</code> tab.
+<p/>On the tab, there is an Explorer-style display of packages.
+Right-click on the root of the tree, &ldquo;<code>MiKTeX Packages</code>&rdquo;,
+and select &ldquo;<code>Search</code>&rdquo;: enter the name of the package you&rsquo;re
+interested in, and press the &ldquo;<code>Search</code>&rdquo; 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.
+<p/>If you prefer a command-line utility, there&rsquo;s <i>mpm</i>.  Open a
+command shell, and type:
+<blockquote>
+<pre>
+mpm --install=&lt;package&gt;
+</pre>
+</blockquote><p>
+(which of course assumes you know the name by which MiKTeX refers to
+your package).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-miktex*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-miktex*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-scut.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-scut.html
new file mode 100644
index 00000000000..5b1d5a1c03d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-scut.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label inst-scut</title>
+</head><body>
+<h3>Shortcuts to installing files</h3>
+<p/><p/>There are circumstances in which most of the fuss of installation can
+be bypassed:
+<ul>
+<li> If you are a MiKTeX user, the 
+  <a href="FAQ-inst-miktexstar.html">MiKTeX package management system</a>
+  can usually help;
+
+<li> The package you want may already exist as a ZIP file
+  formatted for <a href="FAQ-inst-tds-zip.html">direct installation</a>.
+
+</ul>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-scut">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-scut</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html
new file mode 100644
index 00000000000..b5317c52051
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label inst-tds-zip</title>
+</head><body>
+<h3>Installing using preformatted ZIP files</h3>
+<p/>Installing packages, as they (&ldquo;traditionally&rdquo;) appear on
+CTAN, involves:
+<ul>
+<li> identifying where to put the various files on an TDS
+  tree,
+<li> installing them, and
+<li> a few housekeeping operations.
+</ul>
+Most people, for most packages, find the first two steps onerous, the
+last being easy (unless it is forgotten!).
+<p/>Preformatted ZIP files (also known as 
+<a href="FAQ-tds-zip.html">TDS ZIP files</a>) are designed to lighten
+the load of performing the first two steps of installation: they
+contain all the files that are that&rsquo;s to be installed for a given
+package, in their &ldquo;correct&rdquo; locations in a 
+<a href="FAQ-tds.html">TDS tree</a>.
+<p/>To install such a file on a Unix system (we assume that you&rsquo;ll install
+into the local TEXMF tree):
+<blockquote>
+<pre>
+cd $TEXMFLOCAL
+unzip $package.tds.zip
+</pre>
+</blockquote><p>
+<p/>On a Windows system that is modern enough that it has a built-in
+ZIP unpacker, simply double-click on the file, and browse to
+where it&rsquo;s to be unpacked.  (We trust that those using earlier
+versions of Windows will already have experience of using
+<i>WinZIP</i> or the like.)
+<p/>Having unpacked the <code>.zip</code> archive, in most cases the only
+remaining chore is to update the file indexes &mdash; as in 
+<a href="FAQ-inst-wlcf.html">normal installation instructions</a>.  However, if
+the package provides a font, you also need to enable the font&rsquo;s map,
+which is discussed in 
+&ldquo;<a href="FAQ-instt1font.html">Installing a Type 1 font</a>&rdquo;
+<p/>At the time of writing, there are rather few <code>.tds.zip</code>
+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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tds-zip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tds-zip</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html
new file mode 100644
index 00000000000..6678ef7888a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label inst-tidy</title>
+</head><body>
+<h3>Tidying up after installation</h3>
+<p/>There&rsquo;s not usually a lot to do after you&rsquo;ve completed the steps
+above &mdash; indeed, if you&rsquo;re merely installed files direct from the
+archive, or whatever, there will be precisely nothing left, by way of
+debris.
+<p/>Things you might care to clean up are:
+<ul>
+<li> the archive file, if you retrieved your data from the archive
+  as a <code>.zip</code> file, or the like;
+<li> the <code>.dtx</code> and <code>.ins</code> files, if you chose not
+  to install them with the documentation; and
+<li> the <code>.aux</code>, <code>.log</code>, <code>.idx</code>, etc.,
+  from building the documentation.
+</ul>
+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&rsquo;ve finished installing.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html
new file mode 100644
index 00000000000..2303718154d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html
@@ -0,0 +1,44 @@
+<head>
+<title>UK TeX FAQ -- question label inst-wlcf</title>
+</head><body>
+<h3>Installing files &ldquo;where (La)TeX can find them&rdquo;</h3>
+<p/><p/>In the past, package documentation used always to tell you to put your
+files &ldquo;where LaTeX can find them&rdquo;; this was always unhelpful &mdash;
+if you knew where that <em>was</em>, you didn&rsquo;t need telling, but if you
+<em>didn&rsquo;t</em> know, you were completely stuck.
+<p/>It was from this issue that the whole idea of the TDS sprang;
+&ldquo;where to put&rdquo; questions now come down to &ldquo;where&rsquo;s the TDS
+tree?&rdquo;.
+<p/>We therefore answer the question by considering:
+<ul>
+<li> <a href="FAQ-what-TDS.html">what tree to use</a>, and
+<li> <a href="FAQ-install-where.html">where in the tree to put the files</a>.
+</ul>
+<p/>Once we know the answer to both questions, and we&rsquo;ve created any
+directories that are needed, we simply copy files to their rightful
+location.
+<p/>This has done what the old requirement specified: LaTeX (or
+whatever) <em>can</em> (in principle) find the files.  However, in order
+that the software <em>will</em> find the files, we need to update an
+index file.
+<p/>On a MiKTeX system, open the window
+  <code>Start</code>-&gt; 
+  <code>All Programs</code>-&gt; 
+  <code>MiKTeX &lt;<i>version</i>&gt;</code>-&gt; 
+  <code>Settings</code>,
+and click on <code>Refresh FNDB</code>.
+The job may also be done in a command window, using the command:
+<blockquote>
+<pre>
+initexmf --update-fndb
+</pre>
+</blockquote><p>
+The 
+<a href="http://docs.miktex.org/manual/initexmf.html">MiKTeX documentation</a>
+gives further details about <code>initexmf</code>.
+<p/>On a teTeX or TeX Live-based system, use the command
+<code>texhash</code> (or if that&rsquo;s not available, <code>mktexlsr</code> &mdash;
+they ought to be different names for the same program).
+<p/>Having done all this, the new package will be available for use.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html
new file mode 100644
index 00000000000..468e2e503e7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label inst1cm</title>
+</head><body>
+<h3>Installing the Bluesky versions of the CM fonts</h3>
+<p/>This is a specialised case of <a href="FAQ-instfont.html">installing a font</a>,
+but it comes easier
+than most, since the font metrics are installed in every (La)TeX
+system before you even start.  Indeed, most recent systems will have
+the Type 1 fonts themselves already installed, so that the job is
+already done, and all you need is to start using them:
+so the first thing to do is to just try it.  On a system that uses
+<i>dvips</i> (most systems nowadays do), try the sequence:
+<pre>
+  latex sample2e
+  dvips -Pcmz -Pamz -o sample2e.ps sample2e
+</pre>
+at a &ldquo;command prompt&rdquo; (<i>shell</i>, in a Unix-style system,
+&ldquo;DOS box&rdquo; in a Windows system).
+<p/>If the command works at all, the console output of the command will
+include a sequence of Type 1 font file names, listed as
+<code>&lt;cmr10.pfb&gt;</code> and so on;
+this is <i>dvips</i> telling you it&rsquo;s including the Type 1 font,
+and you need do no more.
+<p/>If the test has failed, you need to install your own set of the fonts.
+<p/>The CTAN directories listed below contain compressed archives of
+the Type 1 
+files for various architectures, both for the Computer Modern fonts
+and for the AMS fonts of mathematical and other useful things.
+Download the archives that are appropriate for your architecture, and
+extract the files &mdash; you only actually need the contents of the
+<i>pfb</i> directories, since you already have the fonts
+installed in the &ldquo;ordinary&rdquo; way, so that the TFM files are
+already present.  (You don&rsquo;t need the PostScript font metric &mdash; AFM
+and PFM &mdash; files in any case.)
+<p/>The files should go into your local <code>texmf</code> tree (<i>texmf.local</i>,
+<i>texmf-local</i>, <i>localtexmf</i>, or whatever).  Create
+directories at offsets <i>fonts/type1/bluesky/cm</i> and
+<i>fonts/type1/bluesky/ams</i>, and copy the <code>.pfb</code> files into them.
+<p/>Now you need to tell <i>dvips</i>, PDFTeX, etc., that the fonts
+are available.  This is done by use of a <em>map file</em>, which lists
+<em>font name</em> (as TeX understands it), <em>font name</em> (as it
+appears in the type 1 file itself), and where the program will find
+the file.  Map files are provided in the download bundles for the
+AMS fonts; for the CM fonts, map files are available
+separately.
+<p/>The set of map files includes files <code>config.*</code>; each of these contains
+an instruction to load a single map file.  For ordinary use, you
+instruct <i>dvips</i> to load the &ldquo;detailed&rdquo; map of the
+CM fonts by use of the command:
+<pre>
+  dvips -Pcmz myfile
+</pre>
+The same can be done with the AMS fonts, and you may invoke
+both sets of fonts with:
+<pre>
+  dvips -Pcmz -Pamz myfile
+</pre>
+Alternatively, the contents of <i>config.cmz</i> and <i>config.amz</i>
+could be combined into a single file, perhaps <i>config.bluesky</i>,
+loaded by the command
+<pre>
+  dvips -Pbluesky myfile
+</pre>
+<p/>Remember, after all such changes, the 
+<a href="FAQ-inst-wlcf.html">file-name database must be refreshed</a>.
+<dl>
+<dt><tt><i>AMS fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a>
+<dt><tt><i>CM fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a>
+<dt><tt><i>CM font maps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips.zip">fonts/cm/ps-type1/bluesky-contrib/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html
new file mode 100644
index 00000000000..b0248ad8f6e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label install-doc</title>
+</head><body>
+<h3>Generating package documentation</h3>
+<p/>We are faced with a range of &ldquo;normal&rdquo; provision, as well as several
+oddities.  One should note that documentation of many packages is
+available on CTAN, without the need of any further effort by
+the user &mdash; such documentation can usually be browsed <em>in situ</em>.
+<p/>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.
+<p/>The standard mechanism, for LaTeX packages, is simply to run
+LaTeX on the <i>package.dtx</i> file, as you would any ordinary
+LaTeX file (i.e., repeatedly until the warnings go away).
+<p/>A variant is that the unpacking process provides a file
+<i>package.drv</i>; if such a thing appears, process it in preference
+to the <i>package.dtx</i> (it seems that when the documented LaTeX
+source mechanism was first discussed, the <i>.drv</i> mechanism was
+suggested, but it&rsquo;s not widely used nowadays).
+<p/>Sometimes, the LaTeX run will complain that it can&rsquo;t find
+<i>package.ind</i> (the code line index) and/or <i>package.gls</i>
+(the list of change records, not as you might imagine, a glossary).
+Both types of file are processed with special <i>makeindex</i>
+style files; appropriate commands are:
+<blockquote>
+<pre>
+makeindex -s gind package
+makeindex -s gglo -o package.gls package.glo
+</pre>
+</blockquote><p>
+This author finds that the second (the change record) is generally of
+limited utility when reading package documentation; it is, however,
+valuable if you&rsquo;re part of the package development team.  If you don&rsquo;t
+feel you need it, just leave out that step
+<p/>Another common (and reasonable) trick performed by package authors is
+to provide a separate file <i>package-doc.tex</i> or even simply
+<i>manual.tex</i>; if the file <i>package.dtx</i> doesn&rsquo;t help, simply
+look around for such alternatives.  The files are treated in the same
+way as any &ldquo;ordinary&rdquo; LaTeX file.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-doc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html
new file mode 100644
index 00000000000..cf04c651947
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label install-find</title>
+</head><body>
+<h3>Finding packages to install</h3>
+<p/>How did you learn about the package?
+<p/>If the information came from these FAQs, you should already
+have a link to the file (there are lists at the end of each answer):
+
+  click on that link,
+and you can get the file, one way or another.
+<p/>If you heard about the file somewhere else, it&rsquo;s possible that the
+source told you where to look; if not, try the CTAN searching
+facilities, such as <a href="http://www.tex.ac.uk/search/">http://www.tex.ac.uk/search/</a>.  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.
+<p/>Packages come in a variety of different styles of distribution; the
+very simplest will actually offer just <i>package.sty</i> &mdash; in this
+case, just download the file and 
+<a href="FAQ-inst-wlcf.html">get on with installation</a>.
+<p/>Normally, though, you will want <i>foo.sty</i> but that file is distributed
+in a LaTeX documented source file <i>foo.dtx</i>; thus you should
+search just for <em>foo</em> &mdash; <i>foo.sty</i> won&rsquo;t be visible
+anywhere on the archive or in the catalogue.
+<p/>Since most packages are distributed in this
+<code>.dtx</code>/<code>.ins</code> 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 <em>need</em> the other ones.
+<p/>Having acquired the package distribution, 
+&ldquo;<a href="FAQ-install-unpack.html">unpacking LaTeX packages</a>&rdquo; outlines
+your next step.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-find">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-find</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html
new file mode 100644
index 00000000000..600d4b8d617
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label install-unpack</title>
+</head><body>
+<h3>Unpacking LaTeX packages</h3>
+<p/>As discussed <a href="FAQ-dtx.html">elsewhere</a>, the &lsquo;ordinary&rsquo; way to
+distribute a LaTeX package is as a pair of files <i>package.dtx</i>
+and <i>package.ins</i>.  If you&rsquo;ve acquired such a pair, you simply
+process <i>package.ins</i> with LaTeX, and the files will appear,
+ready for installation.
+<p/>Other sorts of provision should ordinarily be accompanied by a
+<i>README</i> file, telling you what to do; we list a few example
+configurations.
+<p/>Sometimes, a directory comes with a bunch of <code>.dtx</code> files, but
+fewer (often only one) <code>.ins</code> files (LaTeX itself comes
+looking like this).  If there is more than one <code>.ins</code> file,
+and in the absence of any instruction in the <i>README</i> file, simply
+process the <code>.ins</code> file(s) one by one.
+<p/>If you&rsquo;re missing the <i>package.ins</i> altogether, you need to play
+around until something works.  Some <code>.dtx</code> files are
+&ldquo;self-extracting&rdquo; &mdash; they do without an <code>.ins</code> file, and once
+you&rsquo;ve processed the <i>package.dtx</i>, <i>package.sty</i> has
+automagically appeared.  Various other oddities may appear, but the
+archivists aim to have <i>README</i> file in every package, which
+should document anything out of the ordinary with the distribution.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-unpack">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-unpack</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html
new file mode 100644
index 00000000000..42ec4dd1199
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html
@@ -0,0 +1,71 @@
+<head>
+<title>UK TeX FAQ -- question label install-where</title>
+</head><body>
+<h3>Where to install packages</h3>
+<p/>We assume here that you have decided what tree to put your files in,
+after reading 
+&ldquo;<a href="FAQ-what-TDS.html">choosing a TDS tree</a>&rdquo;.  We will therefore
+write <code>$TEXMF</code> for it, and you need to substitute the tree
+you decided on.
+<p/>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:
+<blockquote>
+<pre>
+.sty, .cls or .fd: $TEXMF/tex/&lt;format&gt;/&lt;package&gt;/
+.mf:   $TEXMF/fonts/source/&lt;supplier&gt;/&lt;font&gt;/
+.tfm:  $TEXMF/fonts/tfm/&lt;supplier&gt;/&lt;font&gt;/
+.vf:   $TEXMF/fonts/vf/&lt;supplier&gt;/&lt;font&gt;/
+.afm:  $TEXMF/fonts/afm/&lt;supplier&gt;/&lt;font&gt;/
+.pfb:  $TEXMF/fonts/type1/&lt;supplier&gt;/&lt;font&gt;/
+.ttf:  $TEXMF/fonts/truetype/&lt;supplier&gt;/&lt;font&gt;/
+.otf:  $TEXMF/fonts/opentype/&lt;supplier&gt;/&lt;font&gt;/
+.pool, .fmt, .base or .mem: $TEXMF/web2c
+</pre>
+</blockquote><p>
+and for modern systems (those distributed in 2005 or later, using TDS
+v1.1 layouts):
+<blockquote>
+<pre>
+.map:  $TEXMF/fonts/map/&lt;syntax&gt;/&lt;bundle&gt;/
+.enc:  $TEXMF/fonts/enc/&lt;syntax&gt;/&lt;bundle&gt;/
+</pre>
+</blockquote><p>
+(Map and encoding files went to directories under
+<i>$TEXMF/dvips/</i>, in earlier distributions.)
+<p/>In the lists above &lt;<i>format</i>&gt; identifies the format the macros
+are designed for &mdash; it can be things such as <code>plain</code>,
+<code>generic</code> (i.e., any format), <code>latex</code> or
+<code>context</code> (or several less common formats).
+<p/>For fonts, &lt;<i>font</i>&gt; refers to the font family (such as <code>cm</code>
+for Knuth&rsquo;s Computer Modern, <code>times</code> for Adobe&rsquo;s Times Roman).
+The supplier is usually obvious &mdash; the supplier
+&ldquo;public&rdquo; is commonly used for free fonts.
+<p/>The &lt;<i>syntax</i>&gt; (for <code>.map</code> and <code>.enc</code> files) is a
+categorisation based on the way the files are written; candidates are
+names of programs such as <i>dvips</i> or <i>pdftex</i>.
+<p/>&ldquo;Straight&rdquo; (La)TeX input can take other forms than the
+<code>.sty</code>, <code>.cls</code> or <code>.fd</code> listed above, too
+(apart from the &lsquo;obvious&rsquo; <code>.tex</code>).  Examples are (the
+obvious) <code>.tex</code>, <code>.lfd</code> for <i>babel</i> language
+definitions, <code>.sto</code> and <code>.clo</code> for package and class
+options, <code>.cfg</code> for configuration information,
+<code>.def</code> for variants (such as the types of devices
+<i>graphics</i> drives).  The <i>README</i> of the package should
+tell you of any others, though sometimes that information is printed
+when the package&rsquo;s <a href="FAQ-install-unpack.html">comments are stripped</a>.
+All of these files should live together with the main package files.
+<p/>Note that &lt;<i>font</i>&gt; may stand for a single font or an entire family:
+for example, files for all of Knuth&rsquo;s Computer Modern fonts are to be
+found in <code>.../public/cm</code>, with various prefixes as appropriate.
+<p/>The font &ldquo;supplier&rdquo; <em>public</em> is a sort of hold-all for
+&ldquo;free fonts produced for use with (La)TeX&rdquo;: as well as Knuth&rsquo;s
+fonts, <em>public</em>&rsquo;s directory holds fonts designed by others
+(originally, but no longer exclusively, in Metafont).
+<p/>Documentation for each package should all go, undifferentiated, into a
+directory on the <i>doc/</i> subtree of the TDS.  The layout of
+the subtree is slightly different: <i>doc/latex</i> hosts all
+LaTeX documentation directories, but more fundamental things are
+covered, e.g., by <i>doc/etex</i> or <i>doc/xetex</i>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html
new file mode 100644
index 00000000000..4daeacdbfd9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label installthings</title>
+</head><body>
+<h3>Installing things on a (La)TeX system</h3>
+<p/><p/>Installing (or replacing) things on your (La)TeX 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&rsquo;ve
+decided what it is that you want to install:
+<ul>
+<li> You must <a href="FAQ-install-find.html">find the file you need</a>;
+<li> If you are going to install a LaTeX package, you may need to
+  <a href="FAQ-install-unpack.html">unpack the distributed files</a>;
+<li> It may be necessary to 
+  <a href="FAQ-install-doc.html">generate some documentation to read</a>;
+<li> You need to 
+  <a href="FAQ-install-where.html">decide where to install the files</a>;
+<li> You must now <a href="FAQ-inst-wlcf.html">install the files</a>; and
+  finally
+<li> You may need to <a href="FAQ-inst-tidy.html">tidy up</a> after the installation.
+</ul>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=installthings">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=installthings</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html
new file mode 100644
index 00000000000..e60489af791
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label instfont</title>
+</head><body>
+<h3>Installing a new font</h3>
+<p/>Fonts are really &ldquo;just another package&rdquo;, 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&rsquo;s sometimes
+difficult to see the overall structure.
+<p/>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&rsquo;s
+TDS tree; all these sub-trees have the directory
+<i>$TEXMF/fonts</i> as their root.  A sequence of answers
+ describes the installation of fonts:
+follow the list through the &ldquo;next question&rdquo; links at the bottom of
+this answer to view them all.
+Other answers discuss specific font families &mdash; for example,
+
+&ldquo;<a href="FAQ-concrete.html">using the concrete fonts</a>&rdquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html
new file mode 100644
index 00000000000..325dc388bff
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label instmffont</title>
+</head><body>
+<h3>Installing a font provided as Metafont source</h3>
+<p/>Metafont fonts are (by comparison with other sorts of font) rather
+pleasingly simple.  Nowadays, they are mostly distributed just as the
+Metafont source, since modern TeX distributions are able to produce
+everything the user needs &ldquo;on the fly&rdquo;; however, if the distribution
+<em>does</em> include TFM files, install them too, since they
+save a little time and don&rsquo;t occupy much disc space.  Always distrust
+distributions of PK font bitmap files: there&rsquo;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.
+<p/>&ldquo;<a href="FAQ-install-where.html">Where to install files</a>&rdquo;
+specifies where the files should go.
+<p/>Further confusion is introduced by font families whose authors devise rules
+for automatic generation of Metafont sources for generating fonts at
+particular sizes; the installation has to know about the rules, as
+otherwise it cannot generate font files.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html
new file mode 100644
index 00000000000..34d170f7891
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label instprinterfont</title>
+</head><body>
+<h3>Installing a PostScript printer built-in font</h3>
+<p/>There is a &ldquo;standard&rdquo; set of fonts that has appeared in every PostScript
+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:
+<ul>
+<li> <i>Times</i> family (4 fonts)
+<li> <i>Palatino</i> family (4 fonts)
+<li> <i>New</i> <i>Century</i> <i>Schoolbook</i> family (4 fonts)
+<li> <i>Bookman</i> family (4 fonts)
+<li> <i>Helvetica</i> family (4 fonts)
+<li> <i>Avant</i> <i>Garde</i> (4 fonts)
+<li> <i>Courier</i> family (4 fonts)
+<li> <i>Utopia</i> family (4 fonts)
+<li> Zapf <i>Chancery</i> (1 font)
+<li> Zapf <i>Dingbats</i> (1 font)
+<li> <i>Symbol</i> (1 font)
+</ul>
+All these fonts are supported, for LaTeX users, by the
+<i>psnfss</i> set of metrics and support files in the file
+<i>lw35nfss.zip</i> on CTAN.  Almost any remotely modern TeX
+system will have some version of <i>psnfss</i> installed, but
+users should note that the most recent version has much improved
+coverage of maths with <i>Times</i> (see package
+<i>mathptmx</i>) and with <i>Palatino</i> (see package
+<i>mathpazo</i>, as well as a more reliable set of font metrics.
+<p/>The archive <i>lw35nfss.zip</i> is laid out according to the
+TDS, so in principle, installation consists simply of
+&ldquo;unzipping&rdquo; the file at the root of a <i>texmf</i> tree.
+<p/>Documentation of the <i>psnfss</i> bundle is provided in
+<i>psnfss2e.pdf</i> in the distribution.
+<dl>
+<dt><tt><i>mathpazo.sty</i></tt><dd>Part of the <i>psnfss</i> bundle
+<dt><tt><i>mathptmx.sty</i></tt><dd>Part of the <i>psnfss</i> bundle
+<dt><tt><i>psnfss bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html
new file mode 100644
index 00000000000..06e84384215
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html
@@ -0,0 +1,75 @@
+<head>
+<title>UK TeX FAQ -- question label instt1font</title>
+</head><body>
+<h3>Installing a Type 1 font</h3>
+<p/>Once you have a prepared Type 1 font, either direct from CTAN
+or the like, or having <a href="FAQ-prept1font.html">&lsquo;prepared&rsquo; it yourself</a>,
+you can get on with installation.
+<p/>The procedure is merely an extension of that for packages, etc., so
+much of what follows will be familiar:
+<ul>
+<li> Install the files, in your <code>texmf</code> tree.  All the
+  strictures about installing non-standard things apply here: be sure
+  to put the files in the local tree.  The list gives reasonable
+  destinations for the various files related to a font family &lt;<i>fname</i>&gt;:
+<pre>
+.pfb,
+.pfa  .../fonts/type1/&lt;foundry&gt;/&lt;fname&gt;
+.tfm  .../fonts/tfm/&lt;foundry&gt;/&lt;fname&gt;
+.vf   .../fonts/vf/&lt;foundry&gt;/&lt;fname&gt;
+.sty,
+.fd   .../tex/latex/&lt;fname&gt;
+.map  .../fonts/map/dvips/&lt;foundry&gt;
+</pre>
+  but if you are lucky, you will be starting from a distribution from
+  CTAN and can make use of the corresponding
+  <code>.tds.zip</code> file, and not care about how to place your files
+  in the TDS tree.
+<li> Regenerate the file indexes (as described in
+  <a href="FAQ-inst-wlcf.html">package installation</a>).
+<li> Update the <i>dvips</i>, PDFTeX and other maps:
+  <ul>
+  <li> On any current TeX Live-based system, or a teTeX v3.0
+    system, execute the command
+    <blockquote>
+<pre>
+updmap-sys --enable Map &lt;fname&gt;.map
+</pre>
+    </blockquote><p>
+    as root.  (You <em>can</em> use plain <i>updmap</i>, but you
+    will be in danger of creating confusion with different map sets
+    for different users thereby.)
+  <li> On a current MiKTeX system, update the system file
+    <i>updmap.cfg</i>, using the shell command
+    <blockquote>
+<pre>
+initexmf --edit-config-file updmap
+</pre>
+    </blockquote><p>
+    adding a line at the end:
+    <blockquote>
+<pre>
+Map &lt;fname&gt;.map
+</pre>
+    </blockquote><p>
+    for each font family &lt;<i>fname</i>&gt; you are adding to the system.
+    Now generate revised maps with the shell command
+    <blockquote>
+<pre>
+initexmf --mkmaps
+</pre>
+    </blockquote><p>
+    This, and other matters, are described in MiKTeX 
+    <a href="http://docs.miktex.org/manual/advanced.html">&rdquo;advanced&rdquo; documentation</a>.
+  </ul>
+</ul>
+Both processes (preparing and installing a font) are very well (and
+thoroughly) described in Philipp Lehman&rsquo;s guide to font installation,
+which may be found on CTAN.
+<dl>
+<dt><tt><i>fontinst.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>)
+<dt><tt><i>Type 1 installation guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf">info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf</a>
+</dl>
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html
new file mode 100644
index 00000000000..419d3f8d472
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html
@@ -0,0 +1,141 @@
+<head>
+<title>UK TeX FAQ -- question label interruptlist</title>
+</head><body>
+<h3>Interrupting enumerated lists</h3>
+<p/>It&rsquo;s often convenient to have commentary text, &lsquo;outside&rsquo; the list,
+between successive entries of a list.  In the case of
+<code>itemize</code> lists this is no problem, since there&rsquo;s never
+anything to distinguish successive items, while in the case of
+<code>description</code> lists, the item labels are under the user&rsquo;s
+control so there&rsquo;s no automatic issue of continuity.
+<p/>For <code>enumerate</code> 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.
+<p/>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:
+<blockquote>
+<pre>
+\newcounter{saveenum}
+ ...
+\begin{enumerate}
+  ...
+  \setcounter{saveenum}{\value{enumi}}
+\end{enumerate}
+&lt;Commentary text&gt;
+\begin{enumerate}
+  \setcounter{enumi}{\value{saveenum}}
+  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+<p/>This is reasonable, in small doses... Problems (apart from sheer
+verbosity) are getting the level right (&ldquo;should I use counter
+<code>enumi</code>, <code>enumii</code>, ...&rdquo;) and remembering not to
+nest the interruptions (i.e., not to have a separate list, that is
+itself interrupted) in the &ldquo;commentary text&rdquo;).
+<p/>The <i>mdwlist</i> package defines commands <code>\</code><code>suspend</code> and
+<code>\</code><code>resume</code> that simplify the process:
+<blockquote>
+<pre>
+\begin{enumerate}
+  ...
+\suspend{enumerate}
+&lt;Commentary text&gt;
+\resume{enumerate}
+  ...
+\end{enumerate}
+</pre>
+</blockquote><p>
+The package allows an optional name (as in
+<code>\</code><code>suspend[id]{enumerate}</code>) to allow you to identify a
+particular suspension, and hence provide a handle for manipulating
+nested suspensions.
+<p/>If you&rsquo;re suspending a <a href="FAQ-enumerate.html">fancy-enumeration list</a>,
+you need to 
+re-supply the optional &ldquo;item label layout&rdquo; parameters required by
+the <i>enumerate</i> package when resuming the list, whether by the
+belt-and-braces approach, or by the <i>mdwlist</i>
+<code>\</code><code>resume{enumerate}</code> technique.  The task is a little tedious
+in the <i>mdwlist</i> case, since the optional argument has to be
+encapsulated, whole, inside an optional argument to <code>\</code><code>resume</code>,
+which requires use of extra braces:
+<blockquote>
+<pre>
+\begin{enumerate}[\textbf{Item} i]
+  ...
+\suspend{enumerate}
+&lt;comment&gt;
+\resume{enumerate}[{[\textbf{Item} i]}]
+...
+\end{enumerate}
+</pre>
+</blockquote><p>
+The <i>enumitem</i> package, in its most recent
+release, will also allow you to resume lists:
+<blockquote>
+<pre>
+\begin{enumerate}
+...
+\end{enumerate}
+&lt;comment&gt;
+\begin{enumerate}[resume]
+...
+\end{enumerate}
+</pre>
+</blockquote><p>
+which feels just as &ldquo;natural&rdquo; as the <i>mdwtools</i> facility,
+and has the advantage of playing well with the other excellent
+facilities of <i>enumitem</i>.
+<p/><i>Expdlist</i> has a neat way of providing for comments, with its
+<code>\</code><code>listpart</code> command.  The command&rsquo;s argument becomes a comment
+between items of the list:
+<blockquote>
+<pre>
+\begin{enumerate}
+\item item 1
+\item item 2
+  \listpart{interpolated comment}
+\item item 3
+\end{enumerate}
+</pre>
+</blockquote><p>
+This, you will realise, means it doesn&rsquo;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&rsquo;s not actually
+<em>necessary</em> for any but <code>enumerate</code>).
+<p/><i>Enumitem</i> also allows multi-level suspension and resumption
+of lists:
+<blockquote>
+<pre>
+\begin{enumerate}
+\item outer item 1
+\end{enumerate}
+&lt;comment&gt;
+\begin{enumerate}[resume]
+\item outer item 2
+% nested enumerate
+\begin{enumerate}
+\item inner item 1
+\end{enumerate}
+&lt;nested comment&gt;
+% resume nested enumerate
+\begin{enumerate}[resume]
+\item inner item 2
+\end{enumerate}
+\item outer item 3
+% end outer enumerate
+\end{enumerate}
+</pre>
+</blockquote><p>
+However, the &lsquo;nested comment&rsquo; interpolated in the nested enumeration
+appears as if it were a second paragraph to &ldquo;outer item 2&rdquo;, which is
+hardly satisfactory.
+<dl>
+<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>)
+<dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>)
+<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html
new file mode 100644
index 00000000000..beb30d35535
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html
@@ -0,0 +1,86 @@
+<head>
+<title>UK TeX FAQ -- question label isdef</title>
+</head><body>
+<h3>Is this command defined?</h3>
+<p/>Macro sets from the earliest days of TeX programming may be
+observed to test whether commands exist by using
+<blockquote>
+<code>\</code><code>ifx</code> csx<code><em>command</em></code> <code>\</code><code>undefined</code> &lt;<i>stuff</i>&gt; ...
+</blockquote><p>
+(which of course actually tests that the command <em>doesn&rsquo;t</em>
+exist).  LaTeX programmers can make use of the internal command
+<blockquote>
+  <code>\</code><code>@ifundefined{</code><em>cmd name</em><code>}{</code><em>action1</em><code>}{</code><em>action2</em><code>}</code>
+</blockquote><p>
+which executes <code>action1</code> if the command is undefined, and
+<code>action2</code> if it is defined
+(<em>cmd name</em> is the command name only, omitting the &lsquo;<code>\</code>&rsquo; character).
+<p/>The <code>\</code><code>@ifundefined</code> command is based on the sequence
+<blockquote>
+
+<pre>
+\expandafter \ifx \csname cmd name\endcsname \relax
+</pre>
+</blockquote><p>
+which relies on the way <code>\</code><code>csname</code> works: if the command doesn&rsquo;t
+exist, it simply creates it as an alias for <code>\</code><code>relax</code>.
+<p/>So: what is wrong with these techniques?
+<p/>Using <code>\</code><code>undefined</code> blithely assumes that the command is indeed not
+defined.  This isn&rsquo;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 <code>\</code><code>@undefined</code>, adding a single
+level of obscurity.
+<p/>The <code>\</code><code>@ifundefined</code> 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 &ldquo;<code>\</code><code>relax</code>&rdquo;
+names serve no purpose whatever.  Even so (sadly) there are places in
+the code of LaTeX where the existence of the <code>\</code><code>relax</code> is relied
+upon, after the test, so we can&rsquo;t get away from <code>\</code><code>@ifundefined</code>
+altogether.
+<p/>David Kastrup offers the (rather tricky)
+<blockquote>
+<pre>
+{\expandafter}\expandafter\ifx \csname cmd name\endcsname\relax ...
+</pre>
+
+</blockquote><p>
+which &ldquo;creates&rdquo; the <code>\</code><code>relax</code>-command inside the group of the first
+<code>\</code><code>expandafter</code>, therefore forgets it again once the test is done.
+The test is about as good as you can do with macros.
+<p/>The <a href="FAQ-etex.html">e-TeX system</a> system comes to our help here: it
+defines two new primitives:
+<ul>
+<li> <code>\</code><code>ifdefined</code>, which tests whether a thing is defined (the
+  negative of comparing with <code>\</code><code>undefined</code>, as it were), and
+<li> <code>\</code><code>ifcsname</code> <code>cmd name</code><code>\</code><code>endcsname</code>, which does the
+  negative of <code>\</code><code>@ifundefined</code> without the <code>\</code><code>relax</code>-command
+  side-effect.
+</ul>
+So, in an e-TeX-based system, the following two conditional clauses do
+the same thing:
+<blockquote>
+<pre>
+\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
+</pre>
+</blockquote><p>
+However, after using the LaTeX
+<code>\</code><code>@ifundefined{foo}</code>..., the conditionals will detect the
+command as &ldquo;existing&rdquo; (since it has been <code>\</code><code>let</code> to <code>\</code><code>relax</code>);
+so it is important not to mix mechanisms for detecting the state of a
+command.
+<p/>Since most distributions nowadays use e-TeX as their base executable
+for most packages, these two primitives may be expected appear widely
+in new macro packages.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html
new file mode 100644
index 00000000000..b45422f401c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html
@@ -0,0 +1,138 @@
+<head>
+<title>UK TeX FAQ -- question label isitanum</title>
+</head><body>
+<h3>Is the argument a number?</h3>
+<p/>TeX&rsquo;s own lexical analysis doesn&rsquo;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&rsquo;s no support for analysing numbers.
+<p/>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 &ldquo;not a number&rdquo; if any character fails
+all comparisons:
+<blockquote>
+<pre>
+\ifx1#1
+\else\ifx2#1
+...
+\else\ifx9#1
+\else\isanumfalse
+\fi\fi...\fi
+</pre>
+</blockquote><p>
+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&rsquo; character codes are consecutive:
+<blockquote>
+<pre>
+\ifnum`#1&lt;`0 \isanumfalse
+\else\ifnum`#1&gt;`9 \isanumfalse
+     \fi
+\fi
+</pre>
+</blockquote><p>
+again used in tail-recursion.  However, these forms aren&rsquo;t very
+satisfactory: getting the recursion &ldquo;right&rdquo; 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.
+<p/>Donald Arseneau&rsquo;s <i>cite</i> package offers the following test
+for an argument being a strictly positive integer:
+<blockquote>
+<pre>
+\def\IsPositive#1{%
+  TT\fi
+  \ifcat_\ifnum0&lt;0#1 _\else A\fi
+}
+</pre>
+</blockquote><p>
+which can be adapted to a test for a non-negative integer thus:
+<blockquote>
+<pre>
+\def\IsNonNegative{%
+  \ifcat_\ifnum9&lt;1#1 _\else A\fi
+}
+</pre>
+</blockquote><p>
+or a test for any integer:
+<blockquote>
+<pre>
+\def\gobbleminus#1{\ifx-#1\else#1\fi}
+\def\IsInteger#1{%
+  TT\fi
+  \ifcat_\ifnum9&lt;1\gobbleminus#1 _\else A\fi
+}
+</pre>
+</blockquote><p>
+but this surely stretches the technique further than is reasonable.
+<p/>If we don&rsquo;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&rsquo;s left:
+<blockquote>
+
+<pre>
+\def\testnum#1{\afterassignment\testresult\count255=#1 \end}
+\def\testresult#1\end{\ifx\end#1\end\isanumtrue\else\isanumfalse\fi}
+</pre>
+</blockquote><p>
+(which technique is due to David Kastrup); this can provoke errors.
+In a later thread on the same topic, Michael Downes offered:
+<blockquote>
+<pre>
+\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
+}
+</pre>
+
+</blockquote><p>
+which relies on <code>\</code><code>romannumeral</code> producing an empty result if its
+argument is zero.  Sadly, this technique has the unfortunate property
+that it accepts simple expressions such as &lsquo;<code>1+2-3</code>&rsquo;; this
+could be solved by an initial <code>\</code><code>gobbleminus</code>-like construction.
+<p/>All the complete functions above are designed to be used in TeX
+conditionals written &ldquo;naturally&rdquo; &mdash; for example:
+<blockquote>
+<pre>
+\if\IsInteger{&lt;subject of test&gt;}%
+  &lt;deal with integer&gt;%
+\else
+  &lt;deal with non-integer&gt;%
+\fi
+</pre>
+</blockquote><p>
+The LaTeX <i>memoir</i> class has an internal command of its own,
+<code>\</code><code>checkifinteger{</code><em>num</em><code>}</code>, that sets the conditional command
+<code>\</code><code>ifinteger</code> according to whether the argument was an integer.
+<p/>Of course, all this kerfuffle would be (essentially) void if there was
+a simple means of &ldquo;catching&rdquo; TeX errors.  Imagining an
+error-catching primitive <code>\</code><code>ifnoerror</code>, one might write:
+<blockquote>
+<pre>
+\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
+}
+</pre>
+</blockquote><p>
+thus using TeX&rsquo;s own integer-parsing code to do the check.  It&rsquo;s a
+pity that such a mechanism was never defined (it could be that it&rsquo;s
+impossible to program within TeX!).
+<dl>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html
new file mode 100644
index 00000000000..b3da3be3629
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label journalpaper</title>
+</head><body>
+<h3>Setting papers for journals</h3>
+<p/>Publishers of journals have a wide range of requirements for the
+presentation of papers, and while many publishers do accept electronic
+submissions in (La)TeX, they don&rsquo;t often submit recommended macros to
+public archives.
+<p/>Nevertheless, there are considerable numbers of macros of one sort or
+another available on CTAN; searching for your journal name in
+the CTAN catalogue (see 
+<a href="FAQ-findfiles.html">searching CTAN</a>)
+may well turn up what you&rsquo;re seeking.
+<p/>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.
+<p/>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 LaTeX 2.09 is good enough...
+<p/>Some publishers rekey anything sent them anyway, so that it doesn&rsquo;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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html
new file mode 100644
index 00000000000..84234b0e9dd
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label keepfonts</title>
+</head><body>
+<h3>Which font files should be kept</h3>
+<p/>Metafont produces from its run three files, a metrics (TFM) file, a
+generic font (GF) file, and a log file; all of these files have the
+same base name as does the input (<em>e.g.</em>, if the input file was
+<i>cmr10.mf</i>, the outputs will be <i>cmr10.tfm</i>,
+<i>cmr10.nnngf</i>
+
+and <i>cmr10.log</i>).
+<p/>For TeX to use the font, you need a 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&rsquo;ll
+(incidentally) generate another TFM file; these files are
+all the same, so you only need to keep one of them.
+<p/>To preview or to produce printed output, the DVI processor will need a
+font raster file; this is what the GF file provides.  However, while
+there used (once upon a time) to be DVI processors that could use
+GF files, modern processors use packed raster (PK) files.
+Therefore, you need to generate a PK file from the GF file; the
+program <i>gftopk</i> does this for you, and once you&rsquo;ve done that you
+may throw the GF file away.
+<p/>The log file should never need to be used, unless there was some sort
+of problem in the Metafont run, and need not be ordinarily kept.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html
new file mode 100644
index 00000000000..c629c881aa0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label labelctr</title>
+</head><body>
+<h3>Making labels from a counter</h3>
+<p/>Suppose we have a LaTeX counter, which we&rsquo;ve defined with
+<code>\</code><code>newcounter{foo}</code>.  We can increment the value of the counter
+by <code>\</code><code>addtocounter{foo}{1}</code>, but that&rsquo;s pretty clunky for an
+operation that happens so often ... so there&rsquo;s a command
+<code>\</code><code>stepcounter{foo}</code> that does this special case of
+increasing-by-one.
+<p/>There&rsquo;s an internal LaTeX variable, the &ldquo;current label&rdquo;, that
+remembers the last &lsquo;labellable&rsquo; 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) &mdash; but it&rsquo;s not necessary.  If, instead
+of either of the stepping methods above, you say
+<code>\</code><code>refstepcounter{foo}</code>, the internal variable is set to the
+new value, and (until something else comes along), <code>\</code><code>label</code> will
+refer to the counter.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html
new file mode 100644
index 00000000000..2c0757af447
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html
@@ -0,0 +1,74 @@
+<head>
+<title>UK TeX FAQ -- question label labelfig</title>
+</head><body>
+<h3>Labelling graphics</h3>
+<p/>&ldquo;Technical&rdquo; 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 MetaPost, which allows you to program the labels, in
+(La)TeX, in the middle of specifying your graphic).
+<p/>Labels on graphics produced by all those <em>other</em> tools is where
+the <i>psfrag</i> package can help.  Place an unique
+text in your graphic, using the normal text features of your tool, and
+you can ask <i>psfrag</i> to replace the text with arbitrary
+(La)TeX material.  <i>Psfrag</i>&rsquo;s &ldquo;operative&rdquo; command is
+<code>\</code><code>psfrag{<em>PS text</em>}{<em>Repl text</em>}</code>, which instructs
+the system to replace the original (&ldquo;<code>PS</code>&rdquo;) text with the
+TeX-typeset replacement text.  Optional
+arguments permit adjustment of position, scale and rotation; full
+details may be found in <i>pfgguide</i> in the distribution.
+<p/>Since <i>psfrag</i> works in terms of (encapsulated) PostScript files,
+it needs extra work for use with PDFLaTeX.  The 
+<a href="FAQ-pdftexgraphics.html"><i>pst-pdf</i> package</a> can support such
+usage.  In fact, the <i>pst-pdf</i> support package
+<i>auto-pst-pdf</i> offers a configuration setting precisely for
+use with <i>psfrag</i>.
+<p/>On the other hand,
+
+  <a href="FAQ-commercial.html">VTeX</a>&rsquo;s GeX processor
+explicitly deals with <i>psfrag</i>, both in its free and
+commercial instances.
+<p/>The <i>psfragx</i> package goes one step further than
+<i>psfrag</i>: it provides a means whereby you can put the
+<i>psfrag</i> commands into the preamble of your EPS file
+itself.  <i>Psfrag</i> has such a command itself, but deprecates
+it; <i>psfragx</i> has cleaned up the facility, and provides a
+script <i>laprint</i> for use with <i>Matlab</i> to produce
+appropriately tagged output.  (In principle, other graphics
+applications could provide a similar facility, but apparently none does.)
+<p/><i>Emacs</i> users may find the embedded editor <i>iTe</i> a
+useful tool for placing labels: it&rsquo;s a (La)TeX-oriented graphical
+editor written in <i>Emacs Lisp</i>.  You create
+<code>iteblock</code> environments containing graphics and text, and
+may then invoke <i>iTe</i> to arrange the elements relative to one
+another.
+<p/>Another useful approach is <i>overpic</i>, which overlays a
+<code>picture</code> environment on a graphic included by use of
+<code>\</code><code>includegraphics</code>.  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 &ldquo;attack&rdquo;; the distribution comes with simple
+examples.
+<p/><i>Pstricks</i> can of course do everything that <i>overpic</i>
+can, with all the flexibility of PostScript programming that it offers
+The <i>pstricks</i> web site has a page with several 
+<a href="http://pstricks.tug.org/main.cgi?file=Examples/overlay">examples of labelling</a>
+which will get you started; if <i>pstricks</i> is 
+<a href="FAQ-drawing.html">an option for you</a>, this route is worth a try.
+<p/>The confident user may, of course, do the whole job in a picture
+environment which itself includes the graphic.  I would recommend
+<i>overpic</i> or the <i>pstricks</i> approach, but such things
+are plainly little more than a convenience over what is achievable
+with the do-it-yourself approach.
+<dl>
+<dt><tt><i>auto-pst-pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/auto-pst-pdf.zip">macros/latex/contrib/auto-pst-pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/auto-pst-pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/auto-pst-pdf/">browse</a>)
+<dt><tt><i>iTe</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ite.zip">support/ite</a> (<a href="ftp://cam.ctan.org/tex-archive/support/ite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/ite/">browse</a>)
+<dt><tt><i>laprint</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfragx/">browse</a>)
+<dt><tt><i>overpic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/overpic.zip">macros/latex/contrib/overpic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/overpic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/overpic/">browse</a>)
+<dt><tt><i>psfrag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfrag.zip">macros/latex/contrib/psfrag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfrag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfrag/">browse</a>)
+<dt><tt><i>psfragx.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfragx/">browse</a>)
+<dt><tt><i>pstricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>)
+<dt><tt><i>pst-pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.zip">macros/latex/contrib/pst-pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html
new file mode 100644
index 00000000000..1a34c99d57e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html
@@ -0,0 +1,74 @@
+<head>
+<title>UK TeX FAQ -- question label labelformat</title>
+</head><body>
+<h3>How to change the format of labels</h3>
+<p/>By default, when a label is created, it takes on the appearance of the
+counter labelled, so the label appears as
+<code>\</code><code>the</code><code>&lt;<i>counter</i>&gt;</code> &mdash; what would be used if you
+asked to typeset the counter in your text.  This isn&rsquo;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 &ldquo;2(c)&rdquo;.   (Remember, you can
+
+<a href="FAQ-enumerate.html">change the structure of list items</a>.)
+The change is of course
+possible by explicit labelling of the parent and using that label to
+construct the typeset result &mdash; something like
+<blockquote>
+<pre>
+\ref{parent-item}(\ref{child-item})
+</pre>
+</blockquote><p>
+which would be both tedious and error-prone.  What&rsquo;s more, it would be
+undesirable, since you would be constructing a visual representation
+which is inflexible (you couldn&rsquo;t change all the references to elements
+of a list at one fell swoop).
+<p/>LaTeX in fact has a label-formatting command built into every label
+definition; by default it&rsquo;s null, but it&rsquo;s available for the user to
+program.  For any label &lt;<i>counter</i>&gt; there&rsquo;s a LaTeX internal
+command <code>\</code><code>p@</code>&lt;<i><code>counter</i>&gt;</code>; for example, a label definition
+on an inner list item is supposedly done using the command
+<code>\</code><code>p@enumii{<code>\</code><code>theenumii</code>}</code>.  Unfortunately, the internal
+workings of this aren&rsquo;t quite right, and you need to patch the
+<code>\</code><code>refstepcounter</code> command:
+<blockquote>
+
+<pre>
+\renewcommand*\refstepcounter[1]{\stepcounter{#1}%
+  \protected@edef\@currentlabel{%
+    \csname p@#1\expandafter\endcsname
+      \csname the#1\endcsname
+  }%
+}
+</pre>
+</blockquote><p>
+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:
+<blockquote>
+<pre>
+\makeatletter
+\renewcommand{\p@enumii}[1]{\theenumi(#1)}
+\makeatother
+</pre>
+</blockquote><p>
+This would make the labels for second-level enumerated lists appear as
+&ldquo;1(a)&rdquo; (and so on).  The analogous change works for any counter that
+gets used in a <code>\</code><code>label</code> command.
+<p/>In fact, the <i>fncylab</i> 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:
+<blockquote>
+<pre>
+\labelformat{enumii}{\theenumi(#1)}
+</pre>
+</blockquote><p>
+In fact, the above example, which we can do in several different ways,
+has been rendered obsolete by the appearance of the <i>enumitem</i>
+package, which is discussed in the answer about 
+<a href="FAQ-enumerate.html">decorating enumeration lists</a>.
+<dl>
+<dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>)
+<dt><tt><i>fncylab.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/fncylab.sty">macros/latex/contrib/misc/fncylab.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html
new file mode 100644
index 00000000000..ba3c6c803b8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label labundef</title>
+</head><body>
+<h3>Finding if a label is undefined</h3>
+<p/>People seem to want to know (at run time) if a label is undefined (I
+don&rsquo;t actually understand <em>why</em>, particularly: it&rsquo;s a transient
+state, and LaTeX deals with it quite well).
+<p/>A resolved label is simply a command:
+<code>\</code><code>r@</code><code>&lt;<i>label-name</i>&gt;</code>; 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
+<code>\</code><code>@ifundefined</code>:
+<blockquote>
+  <code>\</code><code>@ifundefined{</code><em></em>r@<em>label-name</em><code>}{</code><em>undef-cmds</em><code>}{</code><em>def-cmds</em><code>}</code>
+</blockquote><p>
+In which, &lt;<i>label-name</i>&gt; is exactly what you would use in
+a <code>\</code><code>label</code> command, and the remaining two arguments are command
+sequences to be used if the label is undefined
+(&lt;<i>undef-cmds</i>&gt;) or if it is defined
+(&lt;<i>def-cmds</i>&gt;).
+<p/>Note that any command that incorporates <code>\</code><code>@ifundefined</code> is naturally
+fragile, so remember to create it with <code>\</code><code>DeclareRobustCommand</code> or to
+use it with <code>\</code><code>protect</code> in a moving argument.
+<p/>If you&rsquo;re into this game, you may well not care about LaTeX&rsquo;s
+warning about undefined labels at the end of the document; however,
+if you are, include the command <code>\</code><code>G@refundefinedtrue</code> in
+&lt;<i><code>undef-cmds</i>&gt;</code>.
+<p/>And of course, remember you&rsquo;re dealing in internal commands, and pay
+attention to the <a href="FAQ-atsigns.html">at-signs</a>.
+<p/>All the above can be avoided by using the <i>labelcas</i> 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&rsquo;s
+definition is a bit complicated, but the package itself is pretty
+powerful.
+<dl>
+<dt><tt><i>labelcas.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.zip">macros/latex/contrib/labelcas</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/labelcas/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html
new file mode 100644
index 00000000000..f2b910ffd23
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html
@@ -0,0 +1,83 @@
+<head>
+<title>UK TeX FAQ -- question label landscape</title>
+</head><body>
+<h3>Typesetting things in landscape orientation</h3>
+<p/>It&rsquo;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.
+<p/>There are two &ldquo;ordinary&rdquo; mechanisms for doing two slight variations
+of landscape typesetting:
+<ul>
+<li> 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 <i>rotating</i> package; this defines
+  <code>sidewaysfigure</code> and <code>sidewaystable</code>
+  environments which create floats that occupy a whole page.
+<p/>  Note that <i>rotating</i> has problems in a document that also
+  loads the <i>float</i> package, which recommended in other
+  answers in these FAQs, for example that on
+  <a href="FAQ-floats.html">float placement</a>.  The <i>rotfloat</i> package
+  loads <i>rotating</i> for you, and smooths the interaction with
+  <i>float</i>.
+<li> If you have a long sequence of things that need to be typeset in
+  landscape (perhaps a code listing, a wide <code>tabbing</code>
+  environment, or a huge table typeset using <i>longtable</i> or
+  <i>supertabular</i>), use the <i>lscape</i> package (or
+  <i>pdflscape</i> if you&rsquo;re generating PDF output, whether
+  using PDFLaTeX or <i>dvips</i> and generating PDF from
+  that).  Both packages define an environment <code>landscape</code>, 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).
+</ul>
+No currently available package makes direct provision for typesetting
+in both portrait and landscape orientation on the same page (it&rsquo;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
+
+<a href="FAQ-textflow.html">"flowing text around figures"</a>, and would
+rotate the landscape portion using the rotation facilities of the
+<i>graphics</i> 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.)
+<p/>To set an entire document in landscape orientation, one might use
+<i>lscape</i> around the whole document.  A better option is the
+<code>landscape</code> option of the <i>geometry</i> package; if you
+also give it <code>dvips</code> or <code>pdftex</code> option,
+<i>geometry</i> also emits the rotation instructions to cause the
+output to be properly oriented.  The <i>memoir</i> class has the same
+facilities, in this respect, as does <i>geometry</i>.
+<p/>A word of warning: most current TeX previewers do not honour
+rotation requests in DVI files.
+
+
+
+
+
+
+
+
+
+
+
+
+
+Your best bet is to convert your output to PostScript or to PDF, and
+to view these &lsquo;final&rsquo; forms with an appropriate viewer.
+<dl>
+<dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>)
+<dt><tt><i>graphics.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>)
+<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>lscape.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>pdflscape.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+<dt><tt><i>rotating.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotating.zip">macros/latex/contrib/rotating</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotating.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotating/">browse</a>)
+<dt><tt><i>rotfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.zip">macros/latex/contrib/rotfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotfloat/">browse</a>)
+<dt><tt><i>supertabular.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html
new file mode 100644
index 00000000000..45ebbff0b07
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label latex</title>
+</head><body>
+<h3>What is LaTeX?</h3>
+<p/>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.
+<p/>Lamport says that LaTeX
+&ldquo;<em>represents a balance between functionality and ease of use</em>&rdquo;.
+This shows itself as a continual conflict that leads to
+the need for such things as FAQs: LaTeX <em>can</em> 
+meet most user requirements, but finding out <em>how</em> is often
+tricky.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html
new file mode 100644
index 00000000000..52101cdbfe6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label latex2e</title>
+</head><body>
+<h3>What is LaTeX2e?</h3>
+<p/>Lamport&rsquo;s last version of LaTeX (LaTeX 2.09, last updated in 1992)
+was superseded in 1994 by a new version (LaTeX2e) provided by
+<a href="FAQ-LaTeX3.html">the LaTeX team</a>.
+LaTeX2e is now the only readily-available version of
+LaTeX, and draws together several threads of LaTeX development
+from the later days of LaTeX 2.09.
+<p/>LaTeX2e has several enhancements over LaTeX 2.09, but they were all
+rather minor, with a view to continuity and stability rather than the
+&ldquo;big push&rdquo; that some had expected from the team.  LaTeX2e
+continues to this day to offer a compatibility mode in which most
+files prepared for use with LaTeX 2.09 will run (albeit with somewhat
+reduced performance, and subject to bitter complaints in the log
+file).  Differences between LaTeX2e and LaTeX 2.09 are
+outlined in a series of &lsquo;guide&rsquo; files that are available in every
+LaTeX distribution (the same directory also contains &ldquo;news&rdquo; about
+each new release of LaTeX2e).
+<dl>
+<dt><tt><i>LaTeX guides and news</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse</a>)
+</dl>
+<p/><p/>
+<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex2e">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex2e</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html
new file mode 100644
index 00000000000..fdc854a2f5d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label latexbug</title>
+</head><body>
+<h3>Reporting a LaTeX bug</h3>
+<p/>The LaTeX team supports LaTeX, and will deal with
+
+<em>bona fide</em> bug reports.  Note that the LaTeX team does
+<em>not</em> deal with contributed packages &mdash; just the software that
+is part of the LaTeX distribution itself: LaTeX and the
+&ldquo;required&rdquo; packages.
+Furthermore, you need to be slightly
+careful to produce a bug report that is usable by the team.  The steps
+are:
+<p/><b>1.</b> Are you still using current LaTeX?  Maintenance is only
+available for sufficiently up-to-date versions of LaTeX &mdash; if your
+LaTeX is more than two versions out of date, the bug reporting
+mechanisms may reject your report.
+<p/><b>2.</b> Has your bug already been reported?  Browse the
+
+<a href="http://www.latex-project.org/cgi-bin/ltxbugs2html?introduction=yes">LaTeX bugs database</a>,
+to find any earlier instance of your bug.  In many cases, the database
+will list a work-around.
+<p/><b>3.</b> Prepare a 
+<a href="FAQ-minxampl.html">&ldquo;minimum&rdquo; file</a> that exhibits the problem.
+Ideally, such a file should contain no contributed packages &mdash; the
+LaTeX team as a whole takes no responsibility for such packages (if
+they&rsquo;re supported at all, they&rsquo;re supported by their authors).  The
+&ldquo;minimum&rdquo; file should be self-sufficient: if a member of the team
+should run it in a clean directory, on a system with no contributed
+packages, it should replicate your problem.
+<p/><b>4.</b> Run your file through LaTeX: the bug
+system needs the <code>.log</code> file that this process creates.
+<p/>You now have two possible ways to proceed: either create a mail report
+to send to the bug processing mechanism (5, below), or submit your bug
+report via the web (7, below).
+<p/><b>5.</b> Process the bug-report creation file, using LaTeX itself:
+<pre>
+  latex latexbug
+</pre>
+<i>latexbug</i> asks you some questions, and then lets you describe
+the bug you&rsquo;ve found.  It produces an output file <i>latexbug.msg</i>,
+which includes the details you&rsquo;ve supplied, your &ldquo;minimum&rdquo; example
+file, and the log file you got after running the example.  (I always
+need to edit the result before submitting it: typing text into
+<i>latexbug</i> isn&rsquo;t much fun.)
+<p/><b>6.</b> Mail the resulting file to
+<i>latex-bugs@latex-project.org</i>; the subject line of your email
+should be the same as the bug title you gave to <i>latexbug</i>.  The
+file <i>latexbug.msg</i> should be included into your message in-line:
+attachments are likely to be rejected by the bug processor.
+<p/><b>7.</b> Connect to the
+
+<a href="http://www.latex-project.org/bugs-upload.html">latex bugs processing web page</a>
+and enter details of your bug &mdash; category, summary and full
+description, and the two important files (source and log file); note
+that members of the LaTeX team <em>need</em> your name and email address, as
+they may need to discuss the bug with you, or to advise you of a
+work-around.
+<p/>
+<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexbug">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexbug</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html
new file mode 100644
index 00000000000..d06cf474cee
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html
@@ -0,0 +1,15 @@
+<head>
+<title>UK TeX FAQ -- question label latexpronounce</title>
+</head><body>
+<h3>How should I pronounce &ldquo;LaTeX(2e)&rdquo;?</h3>
+
+<p/>Lamport never recommended how one should pronounce LaTeX, but a lot
+of people pronounce it &lsquo;Lay TeX&rsquo; or perhaps &lsquo;Lah TeX&rsquo; (with
+TeX pronounced as the program itself; see
+<a href="FAQ-TeXpronounce.html">the rules for TeX</a>).  It is definitely
+<em>not</em> to be pronounced in the same way as the rubber-tree gum.
+<p/>The &lsquo;epsilon&rsquo; in &lsquo;LaTeX2e&rsquo; is supposed to be suggestive of a small
+improvement over the old LaTeX 2.09.  Nevertheless, most people
+pronounce the name as &lsquo;LaTeX-two-ee&rsquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html
new file mode 100644
index 00000000000..a13f693fe96
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label latexqual</title>
+</head><body>
+<h3>The quality of your LaTeX</h3>
+<p/>The <i>l2tabu</i> tutorial (mentioned in 
+<a href="FAQ-man-latex.html">online introductions</a>) is undoubtedly a
+good read.
+<p/>However, it&rsquo;s always difficult to remember the things you should
+<em>not</em> do, when there are so many things to remember that you
+really must do: some automation is needed....
+<p/>The nicely-named <i>nag</i> allows you to apply a configurable set
+of checks to your document, as you run it through LaTeX; you get
+messages like:
+<blockquote>
+<pre>
+Package nag Warning: Command \bf is an old LaTeX 2.09 command. 
+(nag)                Use \bfseries or \textbf instead on input line 30.
+</pre>
+
+</blockquote><p>
+  (the package provides a demo file which contains most of the sorts
+  of errors you might make &mdash; this is one of them).
+
+<p/>There&rsquo;s also a web site
+<a href="http://www.kohm.name/markus/texidate.html">TeXidate</a>
+which will do a static analysis of your document (unfortunately, you
+have to paste your document source into a text window).  The site
+doesn&rsquo;t seem as comprehensive as <i>nag</i>, but it allows you to
+download its script, which you can then juggle with to make it more
+draconian.
+<dl>
+<dt><tt><i>l2tabu</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/l2tabu/">info/l2tabu/</a> for a copy in a language that&rsquo;s
+  convenient for you
+<dt><tt><i>nag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/nag.zip">macros/latex/contrib/nag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/nag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/nag/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexqual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexqual</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html
new file mode 100644
index 00000000000..eae9c92a51f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label latexwords</title>
+</head><body>
+<h3>Changing the words <i>babel</i> uses</h3>
+<p/>LaTeX uses symbolic names for many of the automatically-generated
+text it produces (special-purpose section headings, captions, etc.).
+As noted in <a href="FAQ-fixnam.html">&ldquo;\LaTeX fixed names&rdquo;</a> (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&rsquo;s
+default English.  So, for example, a Danish author may wish that her
+table of contents was called &ldquo;Indholdsfortegnelse&rdquo;, and so 
+would expect to place a command
+<pre>
+\renewcommand{\contentsname}%
+    {Indholdsfortegnelse}
+</pre>
+in the preamble of her document.
+<p/>However, it&rsquo;s natural for a user of a non-English language to use
+<i>babel</i>, because it offers many conveniences and typesetting
+niceties for those preparing documents in those languages.  In
+particular, when <i>babel</i> is selecting a new language, it
+ensures that LaTeX&rsquo;s symbolic names are translated appropriately
+for the language in question.  Unfortunately, <i>babel</i>&rsquo;s choice
+of names isn&rsquo;t always to everyone&rsquo;s choice, and there is still a need
+for a mechanism to replace the &lsquo;standard&rsquo; names.
+<p/>Whenever a new language is selected, <i>babel</i> resets all the
+names to the settings for that language.  In particular,
+<i>babel</i> selects the document&rsquo;s main language when
+<code>\</code><code>begin{document}</code> is executed, which immediately destroys
+any changes to these symbolic names made in the prologue of a document
+that uses <i>babel</i>. 
+<p/>Therefore, babel defines a command to enable users to change the
+definitions of the symbolic names, on a per-language basis:
+<code>\</code><code>addto</code><code>\</code><code>captions</code><code>&lt;<i>language</i>&gt;</code> is the thing
+(<code>&lt;<i>language</i>&gt;</code> being the language option you gave to
+<i>babel</i> in the first place).  For example:
+<pre>
+\addto\captionsdanish{%
+  \renewcommand{\contentsname}%
+    {Indholdsfortegnelse}%
+}
+</pre>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html
new file mode 100644
index 00000000000..3daf4d5a2fa
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html
@@ -0,0 +1,44 @@
+<head>
+<title>UK TeX FAQ -- question label letterclass</title>
+</head><body>
+<h3>Letters and the like</h3>
+<p/>LaTeX itself provides a <i>letter</i> 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:
+<pre>
+\makeatletter
+\let\@texttop\relax
+\makeatother
+</pre>
+in the preamble of your file.
+<p/>Doing-it-yourself is a common strategy; Knuth (for use with
+Plain TeX, in the TeXbook), and Kopka and Daly (in their Guide to
+LaTeX) offer worked examples.
+<p/>Nevertheless, there <em>are</em> contributed alternatives &mdash; in fact
+there are an awfully large number of them: the following list, of
+necessity, makes but a small selection.
+<p/>The largest, most comprehensive, class is <i>newlfm</i>; the <code>lfm</code>
+part of the name implies that the class can create letters, faxes and
+memoranda.  The documentation is voluminous, and the package seems
+very flexible.
+<p/>Axel Kielhorn&rsquo;s <i>akletter</i> class is the only other one,
+recommended for inclusion in this FAQ, whose documentation is
+available in English.
+<p/>The <i>dinbrief</i> class, while recommended, is only documented in
+German.
+<p/>There are letter classes in each of the excellent
+<i>KOMA-script</i> (<i>scrlttr2</i>: documentation is available in
+English) and <i>ntgclass</i> (<i>brief</i>: documentation in Dutch
+only) bundles.  While these are probably good (since the bundles
+themselves inspire trust) they&rsquo;ve not been specifically recommended by
+any users.
+<dl>
+<dt><tt><i>akletter.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/akletter.zip">macros/latex/contrib/akletter</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/akletter.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/akletter/">browse</a>)
+<dt><tt><i>brief.cls</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntgclass/">browse</a>)
+<dt><tt><i>dinbrief.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dinbrief.zip">macros/latex/contrib/dinbrief</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dinbrief.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dinbrief/">browse</a>)
+<dt><tt><i>newlfm.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newlfm.zip">macros/latex/contrib/newlfm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newlfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/newlfm/">browse</a>)
+<dt><tt><i>scrlttr2.cls</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html
new file mode 100644
index 00000000000..d20e191d767
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html
@@ -0,0 +1,45 @@
+<head>
+<title>UK TeX FAQ -- question label letterspace</title>
+</head><body>
+<h3>Changing the space between letters</h3>
+<p/>A common technique in advertising copy (and other text whose actual
+content need not actually be <em>read</em>) 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).
+<p/>The great type designer, Eric Gill, is credited with saying &ldquo;he who
+would letterspace lower-case text, would steal sheep&rdquo;.  (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.
+<p/>Straightforward macros (usable, in principle, with any TeX macro
+package) may be found in <i>letterspacing</i> (which is the name of
+the <code>.tex</code> file).
+<p/>
+
+<p/>A more comprehensive solution is to be found in the <i>soul</i>
+package (which is optimised for use with LaTeX, but also works with
+Plain TeX).  Soul also permits hyphenation of letterspaced text;
+Gill&rsquo;s view of such an activity is not (even apocryphally) recorded.
+(Spacing-out forms part of the name of <i>soul</i>; the other half
+is described in <a href="FAQ-underline.html">another question</a>.)
+<p/>Possibly the &lsquo;ultimate&rsquo; in this field is the <i>microtype</i>,
+which uses the micro-typography capabilities of current PDFTeX to
+provide a <code>\</code><code>textls</code> command, which operates according to parameters
+declared in a <code>\</code><code>SetTracking</code> command.  <i>Microtype</i>&rsquo;s
+&lsquo;tracking&rsquo; facility expands the natural spacing font itself, rather
+than inserting space between characters.  Ordinarily, letter-spacing
+will destroy ligatures; however, this is <em>wrong</em> if the font is
+of a fraktur style, and the package provides a means of protecting the
+ligatures in a letter-spaced text.
+<dl>
+<dt><tt><i>letterspacing.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/letterspacing.tex">macros/generic/misc/letterspacing.tex</a>
+<dt><tt><i>microtype.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse</a>)
+<dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>)
+
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html
new file mode 100644
index 00000000000..c09918b890b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html
@@ -0,0 +1,60 @@
+<head>
+<title>UK TeX FAQ -- question label limits</title>
+</head><body>
+<h3>Sub- and superscript positioning for operators</h3>
+<p/>The commonest hand-written style for expressions is to place the limit
+expressions on operators such as <code>\</code><code>sum</code> and <code>\</code><code>int</code> physically
+above and below the operator.  In (La)TeX, we write these limit
+expressions using sub- and superscripts applied to the operator, but
+they don&rsquo;t always appear in the &ldquo;handwritten&rdquo; way in TeX&rsquo;s
+output.
+<p/>The reason is, that when an expression appears in non-display maths,
+in running text (and is therefore in TeX <code>\</code><code>textstyle</code>), placing
+the limits thus could lead to ragged line spacing (and hence
+difficult-to-read text).  It is therefore common (in <code>\</code><code>textstyle</code>)
+to place the limits as one would sub- and superscripts of variables.
+<p/>This is not universally satisfactory, so the primitive <code>\</code><code>limits</code> is
+provided:
+<blockquote>
+<pre>
+$\sum\limits_{n=1}^{m} ...$
+</pre>
+</blockquote><p>
+which will place the limits right above and below the symbol (and be
+blowed to the typography...).
+<p/>Contrariwise, you may wish to change the arrangement of the limits
+when in <code>\</code><code>displaystyle</code>.  For this purpose, there&rsquo;s a corresponding
+<code>\</code><code>nolimits</code>:
+<blockquote>
+<pre>
+\[\sum\nolimits_{n=1}^{m} ...\]
+</pre>
+</blockquote><p>
+which will place the limits as they would be in <code>\</code><code>textstyle</code>.
+<p/>Alternatively, one can manipulate the
+<code>\</code><code>textstyle</code>/<code>\</code><code>displaystyle</code> state of the mathematics.  To get
+&ldquo;<code>\</code><code>limits</code> placement&rdquo; in inline maths,
+<blockquote>
+<pre>
+$\displaystyle\sum_{n=1}^{m} ...$
+</pre>
+</blockquote><p>
+and for &ldquo;<code>\</code><code>nolimits</code> placement&rdquo; in display maths,
+<code>\</code><code>nolimits</code>:
+<blockquote>
+<pre>
+\[\textstyle\sum_{n=1}^{m} ...\]
+</pre>
+</blockquote><p>
+will serve.  Either of these forms may have effects other than on the
+operator you&rsquo;re considering, but there are still those who prefer this
+formulation.
+<p/>Remember, if you&rsquo;re 
+<a href="FAQ-newfunction.html">declaring a special operator of your own</a>, the
+AMSLaTeX functions (that you ought to be using) allow you to choose
+how limits are displayed, at definition time.
+<p/>(Note that the macro <code>\</code><code>int</code> normally has <code>\</code><code>nolimits</code> built in to
+its definition.  There is an example in the TeXbook to show how odd
+<code>\</code><code>int</code><code>\</code><code>limits</code> looks when typeset.)
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html
new file mode 100644
index 00000000000..ac06276ba38
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label linenos</title>
+</head><body>
+<h3>Including line numbers in typeset output</h3>
+<p/>For general numbering of lines, there are two packages for use with
+LaTeX, <i>lineno</i> (which permits labels attached to
+individual lines of typeset output) and <i>numline</i>.
+<p/>Both of these packages play fast and loose with the LaTeX output
+routine, which can cause problems: the user should beware...
+<p/>If the requirement is for numbering verbatim text, <i>moreverb</i>,
+<i>memoir</i> or <i>fancyvrb</i> (see 
+<a href="FAQ-verbfile.html">including files verbatim</a>) may be used.
+<p/>One common use of line numbers is in critical editions of texts, and
+for this the <i>edmac</i> package offers comprehensive support;
+<i>ledmac</i> is a LaTeX port of <i>edmac</i>.
+<p/>The <i>vruler</i> 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).
+<dl>
+<dt><tt><i>edmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.zip">macros/plain/contrib/edmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/edmac/">browse</a>)
+<dt><tt><i>fancyvrb.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb/">browse</a>)
+<dt><tt><i>ledmac.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse</a>)
+<dt><tt><i>lineno.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.zip">macros/latex/contrib/lineno</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lineno/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>moreverb.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moreverb.zip">macros/latex/contrib/moreverb</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moreverb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb/">browse</a>)
+<dt><tt><i>numline.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numline/numline.sty">macros/latex/contrib/numline/numline.sty</a>
+<dt><tt><i>vruler.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/vruler.sty">macros/latex/contrib/misc/vruler.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html
new file mode 100644
index 00000000000..459a395ed47
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label linespace</title>
+</head><body>
+<h3>Double-spaced documents in LaTeX</h3>
+<p/>A quick and easy way of getting inter-line space for copy-editing is
+to change <code>\</code><code>baselinestretch</code> &mdash; <code>\</code><code>linespread{1.2}</code> (or,
+equivalently <code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{1.2}</code>) may
+be adequate.  Note that <code>\</code><code>baselinestretch</code> changes don&rsquo;t take
+effect until you select a new font, so make the change in the preamble
+before any font is selected.  Don&rsquo;t try changing <code>\</code><code>baselineskip</code>:
+its value is reset at any size-changing command so that results will
+be inconsistent.
+<p/>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 <i>setspace</i> (do <em>not</em>
+be tempted by <i>doublespace</i> &mdash; its performance under current
+LaTeX is at best problematical).  <i>Setspace</i> switches off
+double-spacing at places where even the most die-hard official would
+doubt its utility (footnotes, figure captions, and so on); it&rsquo;s very
+difficult to do this consistently if you&rsquo;re manipulating
+<code>\</code><code>baselinestretch</code> yourself.
+<p/>Of course, the real solution (other than for private copy editing) is
+<em>not</em> 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&rsquo;s system (for example, through
+your dissertation supervisor), it may be worth attempting to get the
+rules changed (at least to permit a &ldquo;well-designed book&rdquo; format).
+<p/>Double-spaced submissions are also commonly required when submitting
+papers to conferences or journals.  Fortunately (judging by the
+questions from users in this author&rsquo;s department), this demand is
+becoming less common.
+<p/>Documentation of <i>setspace</i> appears as TeX comments in the
+package file itself.
+<dl>
+<dt><tt><i>setspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html
new file mode 100644
index 00000000000..79c57fffa0e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label linespread</title>
+</head><body>
+<h3>Why doesn&rsquo;t <code>\</code><code>linespread</code> work?</h3>
+<p/>The command <code>\</code><code>linespread{</code><em>factor</em><code>}</code> is supposed to multiply
+the current <code>\</code><code>baselineskip</code> by &lt;<i>factor</i>&gt;; but, to all
+appearances, it doesn&rsquo;t.
+<p/>In fact, the command is equivalent to
+<code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{factor}</code>: written that
+way, it somehow feels less surprising that the effect isn&rsquo;t immediate.
+The <code>\</code><code>baselinestretch</code> factor is only used when a font is selected;
+a mere change of <code>\</code><code>baselinestretch</code> doesn&rsquo;t change the font, any
+more than does the command
+<code>\</code><code>fontsize{</code><em>size</em><code>}{</code><em>baselineskip</em><code>}</code> &mdash; you have to follow
+either command with <code>\</code><code>selectfont</code>.  So:
+<blockquote>
+<pre>
+\fontsize{10}{12}%
+\selectfont
+</pre>
+</blockquote><p>
+or:
+<blockquote>
+<pre>
+\linespread{1.2}%
+\selectfont
+</pre>
+</blockquote><p>
+Of course, a package such as <i>setspace</i>, whose job is to
+manage the baseline, will deal with all this stuff &mdash; see
+&ldquo;<a href="FAQ-linespace.html">managing double-spaced documents</a>&rdquo;.  If
+you want to avoid <i>setspace</i>, beware the behaviour of
+linespread changes within a paragraph: read 
+&ldquo;<a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code> is a paragraph parameter</a>&rdquo;.
+<dl>
+<dt><tt><i>setspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html
new file mode 100644
index 00000000000..539033c4fd6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label lit</title>
+</head><body>
+<h3>What is Literate Programming?</h3>
+<p/>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 WEB style of literate programming was created by
+D. E. Knuth during the development of TeX.
+<p/>
+  The &ldquo;<a href="FAQ-dtx.html">documented LaTeX</a>&rdquo; style of programming
+is regarded by some as a form of literate programming, though it only
+contains a subset of the constructs Knuth used.
+<p/>Discussion of literate programming is conducted in the newsgroup
+<i>comp.programming.literate</i>, whose FAQ is stored on
+CTAN.  Another good source of information is
+<a href="http://www.literateprogramming.com/">http://www.literateprogramming.com/</a>
+<dl>
+<dt><tt><i>Literate Programming FAQ</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/help/comp.programming.literate_FAQ">help/comp.programming.literate_FAQ</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html
new file mode 100644
index 00000000000..f0e08fac9cc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label logos</title>
+</head><body>
+<h3>Typesetting all those TeX-related logos</h3>
+<p/>Knuth was making a particular point about the capabilities of TeX
+when he defined the logo.  Unfortunately, many believe, he thereby
+opened floodgates to give the world a whole range of rather silly
+&lsquo;bumpy road&rsquo; logos such as AMSTeX, PicTeX, BibTeX, and so on,
+produced in a flurry of different fonts, sizes, and baselines &mdash; 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 &lsquo;A&rsquo; and a lowered &lsquo;E&rsquo;)
+and marketing input from Addison-Wesley led to the even
+stranger current logo
+
+  LaTeX2e, which appends a lowered single-stroke Greek letter
+  epsilon.
+<p/>Sensible users don&rsquo;t have to follow this stuff wherever it goes,
+but, for those who insist, a large collection of logos is defined in
+the <i>texnames</i> package (but note that this set of macros isn&rsquo;t
+entirely reliable in LaTeX2e).
+The Metafont and MetaPost logos can be set in fonts that LaTeX2e
+knows about (so that they scale with the surrounding text) using the
+<i>mflogo</i> package; but be aware that booby-traps surround the
+use of the Knuthian font for MetaPost (you might get
+
+
+
+
+  something like &lsquo;META&nbsp;O&nbsp;T&rsquo;).
+You needn&rsquo;t despair, however &mdash; the author himself uses just &lsquo;MetaPost&rsquo;.
+<p/>For those who don&rsquo;t wish to acquire the &lsquo;proper&rsquo; logos, the canonical
+thing to do is to say <code>AMS-</code><code>\</code><code>TeX</code>
+
+for AMSTeX, <code>Pic</code><code>\</code><code>TeX</code>
+
+for PicTeX, <code>Bib</code><code>\</code><code>TeX</code>
+
+for BibTeX, and so on.
+<dl>
+<dt><tt><i>mflogo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.zip">macros/latex/contrib/mflogo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mflogo/">browse</a>)
+<dt><tt><i>texnames.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/biblio/texnames.sty">info/biblio/texnames.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html
new file mode 100644
index 00000000000..ec9d1b7a1a8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label lollipop</title>
+</head><body>
+<h3>What is Lollipop?</h3>
+<p/>Lollipop is a macro package written by Victor Eijkhout; it was used in
+the production of his book &ldquo;<em>TeX by Topic</em>&rdquo; (see
+<a href="FAQ-ol-books.html">(La)TeX Tutorials</a>).  The manual says of
+it:
+<blockquote>
+  Lollipop is &lsquo;TeX made easy&rsquo;. Lollipop is a macro package that
+  functions as a toolbox for writing TeX macros.  It was my
+  intention to make macro writing so easy that implementing a fully
+  new layout in TeX would become a matter of less than an hour for
+  an average document, and that it would be a task that could be
+  accomplished by someone with only a very basic training in TeX
+  programming.
+<p/>  Lollipop is an attempt to make structured text formatting available
+  for environments where previously only WYSIWYG packages could be
+  used because adapting the layout is so much more easy with them than
+  with traditional TeX macro packages.
+</blockquote><p>
+<p/>The manual goes on to talk of ambitions to &ldquo;capture some of the
+LaTeX market share&rdquo;; it&rsquo;s a very witty package, but little sign of
+
+it taking over from LaTeX is detectable...
+An article about Lollipop appeared in <i>TUGboat</i> 13(3).
+<dl>
+<dt><tt><i>Lollipop distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.zip">macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html
new file mode 100644
index 00000000000..a749efd9b5c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label longtab</title>
+</head><body>
+<h3>Tables longer than a single page</h3>
+<p/>Tables are, by default, set entirely in boxes of their own: as a
+result, they won&rsquo;t split over a page boundary.  Sadly, the world keeps
+turning up tables longer than a single page that we need to typeset.
+<p/>For simple tables (whose shape is highly regular), the simplest
+solution may well be to use the <code>tabbing</code> environment,
+which is slightly tedious to set up, but which doesn&rsquo;t force the whole alignment
+onto a single page.
+<p/>The <i>longtable</i> package builds the whole table (in chunks), in
+a first pass, and then uses information it has written to the <code>.aux</code>
+file during later passes to get the setting &ldquo;right&rdquo; (the package
+ordinarily manages to set tables in just two passes).  Since the
+package has overview of the whole table at the time it&rsquo;s doing
+&ldquo;final&rdquo; setting, the table is set &ldquo;uniformly&rdquo; over its entire
+length, with columns matching on consecutive pages.
+<i>longtable</i> has a reputation for failing to interwork with
+other packages, but it does work with <i>colortbl</i>, and its
+author has provided the <i>ltxtable</i> package to provide (most
+of) the facilities of <i>tabularx</i> (see
+
+<a href="FAQ-fixwidtab.html">fixed-width tables</a>) for long tables:
+beware of its rather curious usage constraints &mdash; each long table
+should be in a file of its own, and included by
+<code>\</code><code>LTXtable{</code><em>width</em><code>}{</code><em>file</em><code>}</code>.  Since <i>longtable</i>&rsquo;s
+multiple-page tables can&rsquo;t possibly live inside floats, the package
+provides for captions within the <code>longtable</code> environment
+itself.
+<p/>A seeming alternative to <i>ltxtable</i> is <i>ltablex</i>; but
+it is outdated and not fully functional.  Its worst problem is its
+strictly limited memory capacity (<i>longtable</i> is not so
+limited, at the cost of much complication in its code);
+<i>ltablex</i> can only deal with relatively small tables, it doesn&rsquo;t seem
+likely that support is available; but its user interface is much
+simpler than <i>ltxtable</i>, so if its restrictions aren&rsquo;t a
+problem for you, it may be worth a try.
+<p/>The <i>supertabular</i> package starts and stops a
+<code>tabular</code> environment for each page of the table.  As a
+result, each &lsquo;page worth&rsquo; of the table is compiled independently, and
+the widths of corresponding columns may differ on successive pages.
+However, if the correspondence doesn&rsquo;t matter, or if your columns are
+fixed-width, <i>supertabular</i> has the great advantage of doing
+its job in a single run.
+<p/>Both <i>longtable</i> and <i>supertabular</i> allow definition
+of head- and footlines for the table; <i>longtable</i> allows
+distinction of the first and last head and foot.
+<p/>The <i>xtab</i> package fixes some infelicities of
+<i>supertabular</i>, and also provides a &ldquo;last head&rdquo; facility
+(though this, of course, destroys <i>supertabular</i>&rsquo;s advantage
+of operating in a single run).
+<p/>The <i>stabular</i> package provides a simple-to-use &ldquo;extension to
+<code>tabular</code>&rdquo; that allows it to typeset tables that run over
+the end of a page; it also has usability extensions, but doesn&rsquo;t have
+the head- and footline capabilities of the major packages.
+<p/>Documentation of <i>ltablex</i> is to be found in the package file.
+<dl>
+<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>ltablex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltablex/ltablex.sty">macros/latex/contrib/ltablex/ltablex.sty</a>
+<dt><tt><i>ltxtable.sty</i></tt><dd>Generate by running <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle/ltxtable.tex">macros/latex/contrib/carlisle/ltxtable.tex</a>
+<dt><tt><i>stabular.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse</a>)
+<dt><tt><i>supertabular.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse</a>)
+<dt><tt><i>xtab.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xtab.zip">macros/latex/contrib/xtab</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xtab.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xtab/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html
new file mode 100644
index 00000000000..0602a30cfc6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html
@@ -0,0 +1,59 @@
+<head>
+<title>UK TeX FAQ -- question label ltxabbrv</title>
+</head><body>
+<h3>LaTeX internal &ldquo;abbreviations&rdquo;, etc.</h3>
+<p/>In the deeps of time, when TeX first happened, computers had
+extremely limited memory, and were (by today&rsquo;s standards) painfully
+slow.  When LaTeX came along, things weren&rsquo;t much better, and even
+when LaTeX2e appeared, there was a strong imperative to save memory
+space (and to a lesser extent) CPU time.
+<p/>From the very earliest days, Knuth used shortcut macros to speed
+things up.  LaTeX, over the years, has extended Knuth&rsquo;s list by a
+substantial amount.  An interesting feature  of the &ldquo;abbreviations&rdquo; is
+that on paper, they may look longer than the thing they stand for;
+however, to (La)TeX they <em>feel</em> smaller...
+<p/>The table at the end of this answer lists the commonest of these
+&ldquo;abbreviations&rdquo;.  It is not complete; as always, if the table
+doesn&rsquo;t help, try the LaTeX source.  The table lists each
+abbreviation&rsquo;s <em>name</em> and its <em>value</em>, which provide most of
+what a user needs to know.  The table also lists the abbreviation&rsquo;s
+<em>type</em>, which is a trickier concept: if you need to know, the
+only real confusion is that the abbreviations labelled &lsquo;defn&rsquo; are
+defined using an <code>\</code><code><em>xxx</code>def</em> command.
+<p/><table rules="groups" border="0" cellpadding="3"><tbody><tr><td>
+Name <td> Type <td> Value <tr><td>
+</tbody><tbody><tr><td>
+<code>\</code><code>m@ne</code> <td> count <td> -1 <tr><td>
+<code>\</code><code>p@</code>  <td> dimen <td> 1pt <tr><td>
+<code>\</code><code>z@</code>  <td> dimen <td> 0pt <tr><td>
+<code>\</code><code>z@skip</code> <td> skip <td> 0pt plus 0pt minus 0pt <tr><td>
+</tbody><tbody><tr><td>
+<code>\</code><code>@ne</code> <td> defn <td> 1 <tr><td>
+<code>\</code><code>tw@</code> <td> defn <td> 2<tr><td>
+<code>\</code><code>thr@@</code> <td> defn <td> 3 <tr><td>
+<code>\</code><code>sixt@@n</code> <td> defn <td> 16 <tr><td>
+<code>\</code><code>@cclv</code> <td> defn <td> 255 <tr><td>
+<code>\</code><code>@cclvi</code> <td> defn <td> 256 <tr><td>
+<code>\</code><code>@m</code> <td> defn <td> 1000 <tr><td>
+<code>\</code><code>@M</code> <td> defn <td> 10000 <tr><td>
+<code>\</code><code>@MM</code> <td> defn <td> 20000 <tr><td>
+</tbody><tbody><tr><td>
+<code>\</code><code>@vpt</code> <td> macro <td> 5 <tr><td>
+<code>\</code><code>@vipt</code> <td> macro <td> 6 <tr><td>
+<code>\</code><code>@viipt</code> <td> macro <td> 7 <tr><td>
+<code>\</code><code>@viiipt</code> <td> macro <td> 8 <tr><td>
+<code>\</code><code>@ixpt</code> <td> macro <td> 9 <tr><td>
+<code>\</code><code>@xpt</code> <td> macro <td> 10 <tr><td>
+<code>\</code><code>@xipt</code> <td> macro <td> 10.95 <tr><td>
+<code>\</code><code>@xiipt</code> <td> macro <td> 12 <tr><td>
+<code>\</code><code>@xivpt</code> <td> macro <td> 14.4 <tr><td>
+<code>\</code><code>@xviipt</code> <td> macro <td> 17.28 <tr><td>
+<code>\</code><code>@xxpt</code> <td> macro <td> 20.74 <tr><td>
+<code>\</code><code>@xxvpt</code> <td> macro <td> 24.88 <tr><td>
+</tbody><tbody><tr><td>
+<code>\</code><code>@plus</code> <td> macro <td> &ldquo;<code>plus</code>&rdquo; <tr><td>
+<code>\</code><code>@minus</code> <td> macro <td> &ldquo;<code>minus</code>&rdquo; <tr><td>
+
+</tbody></table>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html
new file mode 100644
index 00000000000..af41f3f0733
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html
@@ -0,0 +1,122 @@
+<head>
+<title>UK TeX FAQ -- question label ltxcmds</title>
+</head><body>
+<h3>The definitions of LaTeX commands</h3>
+<p/>There are several reasons to want to know the definitions of LaTeX
+commands: from the simplest &ldquo;idle curiosity&rdquo;, to the pressing need
+to patch something to make it &ldquo;work the way you want it&rdquo;.  None of
+these are <em>pure</em> motives, but knowledge and expertise seldom
+arrive through the purest of motives.
+<p/>The simple answer is to try <code>\</code><code>show</code>, in a run of LaTeX that is
+taking commands from the terminal:
+<blockquote>
+<pre>
+*\makeatletter
+*\show\protected@edef
+&gt; \protected@edef=macro:
+-&gt;\let \@@protect \protect
+  \let \protect \@unexpandable@protect
+  \afterassignment \restore@protect \edef .
+</pre>
+</blockquote><p>
+(I&rsquo;ve rearranged the output there, from the rather confused version
+TeX itself produces.)  We may perhaps, now, wonder about
+<code>\</code><code>@unexpandable@protect</code>:
+<blockquote>
+<pre>
+*\show\@unexpandable@protect
+&gt; \@unexpandable@protect=macro:
+-&gt;\noexpand \protect \noexpand .
+</pre>
+</blockquote><p>
+and we&rsquo;re starting to see how one part of the <code>\</code><code>protect</code>ion
+mechanism works (one can probably fairly safely guess what
+<code>\</code><code>restore@protect</code> does).
+<p/>Many kernel commands are declared robust:
+<blockquote>
+<pre>
+*\show\texttt
+&gt; \texttt=macro:
+-&gt;\protect \texttt  .
+</pre>
+</blockquote><p>
+so that <code>\</code><code>show</code> isn&rsquo;t much help.  Define a command <code>\</code><code>pshow</code> as
+shown below, and use that instead:
+<blockquote>
+<pre>
+*\def\pshow#1{{\let\protect\show #1}}
+*\pshow\texttt
+&gt; \texttt =\long macro:
+#1-&gt;\ifmmode \nfss@text {\ttfamily #1}%
+    \else \hmode@bgroup \text@command {#1}%
+          \ttfamily \check@icl #1\check@icr
+    \expandafter \egroup \fi .
+</pre>
+</blockquote><p>
+Note that the command name that is protected is the &lsquo;base&rsquo; command,
+with a space appended.  This is cryptically visible, in a couple of
+places above.  (Again, the output has been sanitised.)
+<p/>If one has a malleable text editor, the same investigation may more
+comfortably be conducted by examining the file <i>latex.ltx</i> (which
+is usually to be found, in a TDS system, in directory
+<i>tex/latex/base</i>).
+<p/>In fact, <i>latex.ltx</i> is the product of a <i>docstrip</i>
+process on a large number of <a href="FAQ-dtx.html"><code>.dtx</code> files</a>, and
+you can refer to those instead.  The LaTeX distribution includes a file
+<i>source2e.tex</i>, and most systems retain it, again in
+<i>tex/latex/base</i>.  <i>Source2e.tex</i> may be processed to
+provide a complete source listing of the LaTeX kernel (in fact the
+process isn&rsquo;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.
+<p/>The printed kernel is a nice thing to have, but it&rsquo;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 LaTeX 2.09, to modules
+that hardly had any useful documentation even in the LaTeX 2.09 original.
+<p/>In fact, each kernel module <code>.dtx</code> file will process separately
+through LaTeX, so you don&rsquo;t have to work with the whole of
+<i>source2e</i>.  You can easily determine which module defines the
+macro you&rsquo;re interested in: use your &ldquo;malleable text editor&rdquo; to find
+the definition in <i>latex.ltx</i>; then search backwards from that
+point for a line that starts 
+<code>%%% From File:</code> &mdash; that line
+tells you which <code>.dtx</code> file contains the definition you are interested
+in.  Doing this for <code>\</code><code>protected@edef</code>, we find:
+<blockquote>
+<pre>
+%%% From File: ltdefns.dtx
+</pre>
+</blockquote><p>
+When we come to look at it, <i>ltdefns.dtx</i> proves to contain
+quite a dissertation on the methods of handling <code>\</code><code>protect</code>ion; it
+also contains some automatically-converted LaTeX 2.09 documentation.
+<p/>And of course, the kernel isn&rsquo;t all of LaTeX: your command may be
+defined in one of LaTeX&rsquo;s class or package files.  For example, we
+find a definition of <code>\</code><code>thebibliography</code> in <i>article</i>, but
+there&rsquo;s no <i>article.dtx</i>.  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 <i>article.cls</i>,
+we find:
+<blockquote>
+<pre>
+%% This is file `article.cls',
+%% generated with the docstrip utility.
+%%
+%% The original source files were:
+%%
+%% classes.dtx  (with options: `article')
+</pre>
+</blockquote><p>
+so we need to format <i>classes.dtx</i> to see the definition in
+context.
+<p/>All these .dtx files are on CTAN as part of the main LaTeX
+distribution.
+<dl>
+<dt><tt><i>LaTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html
new file mode 100644
index 00000000000..0e3d777727f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html
@@ -0,0 +1,55 @@
+<head>
+<title>UK TeX FAQ -- question label ltxhash</title>
+</head><body>
+<h3>Defining LaTeX commands within other commands</h3>
+<p/>LaTeX command definition is significantly different from the TeX
+primitive form discussed in an 
+<a href="FAQ-hash.html">earlier question</a> about definitions within
+macros.
+<p/>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.
+<p/>The earlier question said you have to double the <code>#</code> 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.
+<p/>The basic problem is that:
+<blockquote>
+<pre>
+\newcommand{\abc}[1]{joy, oh #1!%
+  \newcommand{\ghi}[1]{gloom, oh #1!}%
+}
+</pre>
+</blockquote><p>
+followed by a call:
+<blockquote>
+<pre>
+\cmdinvoke{abc}{joy}
+</pre>
+</blockquote><p>
+typesets &ldquo;joy, oh joy!&rdquo;, but defines a command <code>\</code><code>ghi</code> that takes
+one parameter, which it ignores; <code>\</code><code>ghi{gloom}</code> will expand to
+&ldquo;gloom, oh joy!&rdquo;, which is presumably not what was expected.
+<p/>And (as you will probably guess, if you&rsquo;ve read the earlier question)
+the definition:
+<blockquote>
+<pre>
+\newcommand{\abc}[1]{joy, oh #1!%
+  \newcommand{\ghi}[1]{gloom, oh ##1!}%
+}
+</pre>
+</blockquote><p>
+does what is required, and <code>\</code><code>ghi{gloom}</code> will expand to
+&ldquo;gloom, oh gloom!&rdquo;, whatever the argument to <code>\</code><code>abc</code>.
+<p/>The doubling is needed whether or not the enclosing command has an
+argument, so:
+<blockquote>
+<pre>
+\newcommand{\abc}{joy, oh joy!%
+  \newcommand{\ghi}[1]{gloom, oh ##1!}%
+}
+</pre>
+</blockquote><p>
+is needed to produce a replica of the <code>\</code><code>ghi</code> we defined earlier.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html
new file mode 100644
index 00000000000..bd8af31be3b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label luatex</title>
+</head><body>
+<h3>PDFTeX becomes LuaTeX</h3>
+<p/>As is said elsewhere in these FAQs, development of
+<a href="FAQ-whatpdftex.html">PDFTeX</a> is &ldquo;in essence&rdquo; complete &mdash;
+development of new facilities continues, but the limitations of the
+present structure impose a strong limit on what facilities are
+possible.  (The PDFTeX team has announced that no further
+developments will be added after the release of PDFTeX 1.50.0,
+which will be the next major release.)
+<p/>In this context, the idea of LuaTeX arose.
+<a href="http://www.lua.org/"><i>Lua</a></i> is a script
+language, designed to offer an interpreter with a very small
+&ldquo;footprint&rdquo;, so it is rather easy to build it into other
+applications.  So LuaTeX was launched as a PDFTeX
+executable with a <i>Lua</i> interpreter built into it.
+<p/>A <a href="http://www.luatex.org/">LuaTeX project</a> is now proceeding
+(with monetary support from various sources) and is pursuing avenues
+that many of the other
+current projects have in their sights, notably Unicode character
+representations and support for OpenType fonts.  Work is also in hand
+to integrate the extensions pioneered by <a href="FAQ-omegaleph.html">Aleph</a>.
+<p/>The next release of TeX Live (due in July 2008) and MiKTeX
+version 2.8 (no current release date) will incorporate LuaTeX.
+ConTeXt distributions can already make use of it.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html
new file mode 100644
index 00000000000..c44c1de89f7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label maillists*</title>
+</head><body>
+<h3>Specialist mailing lists</h3>
+<p/>The previous question, &ldquo;<a href="FAQ-gethelp.html">getting help</a>&rdquo;, talked of
+the two major forums in which (La)TeX, Metafont and MetaPost are
+discussed; however, these aren&rsquo;t the only ones available.
+<p/>The TUG web site offers many mailing lists other than just
+<code>texhax</code> via its 
+<a href="http://tug.org/mailman/listinfo">mail list management page</a>.
+<p/>The French national TeX user group, Gutenberg, offers a Metafont (and,
+de facto, MetaPost) mailing list, <a href="mailto:metafont@ens.fr"><i>metafont@ens.fr</i></a>: subscribe to
+it by sending a message
+<blockquote>
+<pre>
+subscribe metafont
+</pre>
+</blockquote><p>
+to <a href="mailto:sympa@ens.fr"><i>sympa@ens.fr</i></a>
+<p/>(Note that there&rsquo;s also a MetaPost-specific mailing list available via the
+TUG lists; in fact there&rsquo;s little danger of becoming confused
+by subscribing to both.)
+<p/>Announcements of TeX-related installations on the CTAN
+archives are sent to the mailing list <code>ctan-ann</code>.  Subscribe
+to the list via its <i>MailMan</i> web-site
+<a href="https://lists.dante.de/mailman/listinfo/ctan-ann">https://lists.dante.de/mailman/listinfo/ctan-ann</a>; list archives
+are available at the same address.  The list archives may also be
+browsed via <a href="http://www.mail-archive.com/ctan-ann@dante.de/">http://www.mail-archive.com/ctan-ann@dante.de/</a>, and
+an RSS feed is also available:
+<a href="http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml">http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml</a>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
new file mode 100644
index 00000000000..18971011cad
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label make</title>
+</head><body>
+<h3>Makefiles for LaTeX documents</h3>
+<p/>LaTeX is a tricky beast for running <i>make</i> on: the need to
+instruct LaTeX to run several times for essentially different
+reasons (for example, &ldquo;get the table of contents stable&rdquo;, &ldquo;get the
+labels stable&rdquo;, &ldquo;add the bibliography&rdquo;, &ldquo;add the index&rdquo;) is
+actually rather difficult to express in the &lsquo;ordinary&rsquo; sort of
+dependency graph that one constructs for <i>make</i>.
+<p/>For this reason, the only <i>make</i>-like package on CTAN
+(for a long time) was <i>latexmk</i>, which is a <i>Perl</i>
+script that analyses your LaTeX source for its dependencies, runs
+BibTeX or <i>makeindex</i> as and when it notices that those
+programs&rsquo; input (parts of the <code>.aux</code> file, or the
+<code>.idx</code> file, respectively) has changed, and so on.
+<i>Latexmk</i> is a fine 
+solution (and was used in generating printable versions of these
+FAQs for a long time); it has recently been upgraded and has
+many bells and whistles that allow it to operate as if it were a poor
+man&rsquo;s WYSIWYG system.
+<p/>Apparently along the same lines, and currently (2007) under active
+development, is AutoLaTeX.  The <i>README</i> of the distribution is
+actual a Unix-type man-page output, and shows great attention to the
+details of the document production process.
+<p/>Windows users of the MiKTeX system may use that systems
+<i>texify</i> application.  <i>Texify</i> 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
+AutoLaTeX can be configured to process.
+<p/>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a similar
+utility called <i>texi2dvi</i>, which is capable of &ldquo;converting&rdquo;
+either LaTeX or <i>texinfo</i> files into DVI (or into
+PDF, using PDFTeX).
+<p/>A later contribution is the bundle <i>latexmake</i>, which
+offers a set of <i>make</i> rules that invoke <i>texi2dvi</i>
+as necessary.
+<p/>The curious may examine the rules employed to run the present
+FAQ through LaTeX: we don&rsquo;t present them as a complete
+solution, but some of the tricks employed are surely re-usable.
+<dl>
+<dt><tt><i>AutoLaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/autolatex.zip">support/autolatex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/autolatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/autolatex/">browse</a>)
+<dt><tt><i>FAQ distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>)
+<dt><tt><i>latexmake</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexmake.zip">support/latexmake</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexmake.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexmake/">browse</a>)
+<dt><tt><i>latexmk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexmk.zip">support/latexmk</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexmk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexmk/">browse</a>)
+<dt><tt><i>texi2dvi</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html
new file mode 100644
index 00000000000..80fafa4181e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label makebib</title>
+</head><body>
+<h3>Reconstructing <code>.bib</code> files</h3>
+<p/>Perhaps you&rsquo;ve lost the <code>.bib</code> file you generated your document from,
+or have been sent a document without one.  Or even, you&rsquo;ve realised
+the error of building a substantial document without the benefit of
+BibTeX...
+<p/>The <i>Perl</i> script, <i>tex2bib</i> makes a reasonable job
+of regenerating <code>.bib</code> files from <code>thebibliography</code>
+environments, provided that the original (whether automatically or
+manually generated) doesn&rsquo;t deviate too far from the &ldquo;standard&rdquo;
+styles.
+<p/>You are well-advised to check the output of the script.  While it will
+not usually destroy information, it can quite reasonably mislabel it.
+<p/>Documentation of the script is to be found in the file <i>tex2bib.readme</i>
+<dl>
+<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/tex2bib">biblio/bibtex/utils/tex2bib/tex2bib</a>
+<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html
new file mode 100644
index 00000000000..f0a1f6ca76d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html
@@ -0,0 +1,53 @@
+<head>
+<title>UK TeX FAQ -- question label makeindex</title>
+</head><body>
+<h3>Generating an index in (La)TeX</h3>
+<p/>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 <code>\</code><code>index</code> commands).
+<p/>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.
+<p/>The following programs are available:
+<dl>
+<dt>makeindex<dd> Comes with most distributions &mdash; a good workhorse,
+  but is not well-arranged to deal with other sort orders than the
+  canonical ASCII ordering.
+<p/>  The <i>makeindex</i> documentation is a good source of
+  information on how to create your own index. <i>Makeindex</i> can
+  be used with some TeX
+  macro packages other than LaTeX, such as 
+  <a href="FAQ-eplain.html">Eplain</a>, and TeX (whose macros can
+  be used independently with Plain TeX).
+<dt>idxtex<dd> for LaTeX under VMS, which comes with a
+  glossary-maker called <i>glotex</i>.
+<dt>texindex<dd> A witty little shell/<i>sed</i>-script-based
+  utility for LaTeX under Unix.
+<p/>  The <a href="FAQ-texinfo.html">Texinfo</a> system also uses a program
+  <i>texindex</i>, whose source is to be found in the
+  <i>texinfo</i> distribution.  The <i>ltxindex</i> package
+  provides macros to allow LaTeX users to use <em>this</em>
+  <i>texindex</i>.
+<dt>xindy<dd> arose from frustration at the difficulty of making a
+  multi-language version of <i>makeindex</i>.  It is designed to
+  be a successor to <i>makeindex</i>, by a team that included the
+  then-current maintainer of <i>makeindex</i>.  It successfully
+  addresses many of <i>makeindex</i>&rsquo;s shortcomings, including
+  difficulties with collation order in different languages, and it is
+  highly flexible.  Sadly, its take-up is proving rather slow.
+</dl>
+<dl>
+<dt><tt><i>idxtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/indexing/glo+idxtex.zip">indexing/glo+idxtex</a> (<a href="ftp://cam.ctan.org/tex-archive/indexing/glo+idxtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/indexing/glo+idxtex/">browse</a>)
+<dt><tt><i>ltxindex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltxindex.zip">macros/latex/contrib/ltxindex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltxindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ltxindex/">browse</a>)
+<dt><tt><i>makeindex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/indexing/makeindex.zip">indexing/makeindex</a> (<a href="ftp://cam.ctan.org/tex-archive/indexing/makeindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/indexing/makeindex/">browse</a>)
+<dt><tt><i>makeindex (Macintosh)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/macmakeindex2.12.sea.hqx">systems/mac/macmakeindex2.12.sea.hqx</a>
+<dt><tt><i>texindex (the script)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/indexing/texindex.zip">indexing/texindex</a> (<a href="ftp://cam.ctan.org/tex-archive/indexing/texindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/indexing/texindex/">browse</a>)
+<dt><tt><i>texindex (the program)</i></tt><dd>Distributed
+  with <a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>)
+<dt><tt><i>texsis (system)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texsis.zip">macros/texsis</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texsis.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texsis/">browse</a>)
+<dt><tt><i>texsis (makeindex support)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texsis/index/index.tex">macros/texsis/index/index.tex</a>
+<dt><tt><i>xindy</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/xindy/">support/xindy/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html
new file mode 100644
index 00000000000..2840ad9104c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html
@@ -0,0 +1,60 @@
+<head>
+<title>UK TeX FAQ -- question label man-latex</title>
+</head><body>
+<h3>Online introductions: LaTeX</h3>
+<p/>Tobias Oetiker&rsquo;s &lsquo;(Not so) Short Introduction to LaTeX2e&rsquo;, is
+regularly updated, as people suggest better ways of explaining things,
+etc.  The introduction is available on CTAN, together with
+translations into a rather large set of languages.
+<p/>Peter Flynn&rsquo;s &ldquo;Beginner&rsquo;s LaTeX&rdquo; (which also started as course
+material) is a pleasing read.  A complete copy may be found on
+CTAN, but it may also be browsed over the web
+(<a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/html/">http://www.tex.ac.uk/tex-archive/info/beginlatex/html/</a>).
+<p/>Harvey Greenberg&rsquo;s &lsquo;Simplified Introduction to LaTeX&rsquo; was written
+for a lecture course, and is also available on CTAN (in PostScript
+only, unfortunately).
+<p/>The fourth edition of George Gr&auml;tzer&rsquo;s book &ldquo;Math into LaTeX&rdquo;
+contains a &ldquo;short course&rdquo; in LaTeX itself, and that course has
+been made publicly available on CTAN.
+<p/>Edith Hodgen&rsquo;s 
+<a href="http://www.mcs.vuw.ac.nz/~david/latex/notes.pdf">LaTeX, a Braindump</a>
+starts you from the ground up &mdash; giving a basic tutorial in the use
+of <i>Linux</i> to get you going (rather a large file...).
+Its parent site, David Friggens&rsquo; 
+<a href="http://www.mcs.vuw.ac.nz/~david/latex/">documentation page</a> is a
+useful collection of links in itself.
+<p/>
+<a href="http://www.andy-roberts.net/misc/latex/">Andy Roberts&rsquo; introductory material</a>
+is a pleasing short introduction to the use of (La)TeX; some of the
+slides for <em>actual</em> tutorials are to be found on the page, as
+well.
+<p/>Chris Harrison&rsquo;s 
+<a href="http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html">TeX book</a>
+presents basic LaTeX with useful hints for extensions
+<p/>Nicola Talbot&rsquo;s 
+<a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/">LaTeX for complete novices</a>
+does what it claims: the author teaches LaTeX at the University of
+East Anglia.  That is one of several of Nicola&rsquo;s 
+<a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/">introductory tutorials</a>,
+which include exercises (with solutions).  Other tutorials include
+those for writing theses/dissertations with LaTeX, and for using
+LaTeX in administrative work.  (The page seems to be an adjunct to
+her LaTeX courses &mdash; fortunate people, the people of UEA!).
+<p/>An interesting (and practical) tutorial about what <em>not</em> to do is
+<i>l2tabu</i>, or &ldquo;A list of sins of LaTeX2e users&rdquo; by Mark
+Trettin, translated into English by J&uuml;rgen Fenn.  The
+tutorial is available from CTAN as a PDF file (though
+the source is also available).
+<dl>
+<dt><tt><i>Beginner&rsquo;s LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/beginlatex/beginlatex-3.6.pdf">info/beginlatex/beginlatex-3.6.pdf</a>
+<dt><tt><i>Not so Short Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/lshort/english/lshort.pdf">info/lshort/english/lshort.pdf</a>
+  (in English, you may browse for sources and other language versions at
+  <a href="http://www.tex.ac.uk/tex-archive/info/lshort/">info/lshort/</a>)
+<dt><tt><i>Simplified LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/simplified-latex/simplified-intro.ps">info/simplified-latex/simplified-intro.ps</a>
+<dt><tt><i>Short Course in LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Math_into_LaTeX-4/Short_Course.pdf">info/Math_into_LaTeX-4/Short_Course.pdf</a>
+
+<dt><tt><i>The sins of LaTeX users</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.pdf">info/l2tabu/english/l2tabuen.pdf</a>;
+  source also available: <a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.tex">info/l2tabu/english/l2tabuen.tex</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html
new file mode 100644
index 00000000000..7b021ea561e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html
@@ -0,0 +1,13 @@
+<head>
+<title>UK TeX FAQ -- question label man-tex</title>
+</head><body>
+<h3>Online introductions: Plain TeX</h3>
+<p/>Michael Doob&rsquo;s splendid &lsquo;Gentle Introduction&rsquo; to Plain TeX
+(available on CTAN) has been stable for a very long time.
+<p/>Another recommendable document is D. R. Wilkins &lsquo;Getting started with TeX&rsquo;,
+available on the web at <a href="http://www.ntg.nl/doc/wilkins/pllong.pdf">http://www.ntg.nl/doc/wilkins/pllong.pdf</a>
+<dl>
+<dt><tt><i>Gentle Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/gentle/gentle.pdf">info/gentle/gentle.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html
new file mode 100644
index 00000000000..8828376fbf1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html
@@ -0,0 +1,56 @@
+<head>
+<title>UK TeX FAQ -- question label manyauthor</title>
+</head><body>
+<h3>BibTeX doesn&rsquo;t understand lists of names</h3>
+<p/>BibTeX has a strict syntax for lists of authors&rsquo; (or editors&rsquo;)
+names in the BibTeX data file; if you write the list of names in a
+&ldquo;natural&rdquo;-seeming way, the chances are you will confuse BibTeX,
+and the output produced will be quite different from what you had
+hoped.
+<p/>Names should be expressed in one of the forms
+<blockquote>
+<pre>
+First Last
+Last, First
+Last, Suffix, First
+</pre>
+</blockquote><p>
+and lists of names should be separated with &ldquo;<code>and</code>&rdquo;.
+For example:
+<blockquote>
+<pre>
+AUTHOR = {Fred Q. Bloggs, John P. Doe &amp;
+          Another Idiot}
+</pre>
+</blockquote><p>
+falls foul of two of the above rules: a syntactically significant
+comma appears in an incorrect place, and &lsquo;<code>\</code><code>&amp;</code>&rsquo; is being used as a
+name separator.  The output of the above might be something like:
+<blockquote>
+<pre>
+John P. Doe &amp; Another Idiot Fred Q. Bloggs
+</pre>
+
+</blockquote><p>
+because &ldquo;John P. Doe &amp; Another Idiot has become the &lsquo;first name&rsquo;,
+while &ldquo;Fred Q. Bloggs&rdquo; has become the &lsquo;last name&rsquo; of a single
+person.  The example should have been written:
+<blockquote>
+
+<pre>
+AUTHOR = {Fred Q. Bloggs and John P. Doe and
+          Another Idiot}
+</pre>
+</blockquote><p>
+Some bibliography styles implement clever acrobatics with very long
+author lists.  You can force truncation by using the pseudo-name
+&ldquo;<code>others</code>&rdquo;, which will usually translate to something like
+&ldquo;<em>et al</em>&rdquo; in the typeset output.  So, if Mr. Bloggs wanted to
+distract attention from his co-authors, he would write:
+<blockquote>
+<pre>
+AUTHOR = {Fred Q. Bloggs and others}
+</pre>
+</blockquote><p>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html
new file mode 100644
index 00000000000..349ad41cd8d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label manymathalph</title>
+</head><body>
+<h3>Too many math alphabets</h3>
+<p/>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 &rdquo;maths alphabets&rdquo;
+<p/>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.
+<p/>If you can&rsquo;t afford to drop any of these packages, there&rsquo;s
+still hope if you&rsquo;re using the <i>bm</i> package to support
+<a href="FAQ-boldgreek.html">bold maths</a>: <i>bm</i> is capable
+of gobbling alphabets as if there is no tomorrow.  The package defines
+two limiter commands: <code>\</code><code>bmmax</code> (for <em>bold</em> symbols; default 4)
+and <code>\</code><code>hmmax</code> (for <em>heavy</em> symbols, if you have them;
+default 3), which control the number of alphabets to be used.  
+<p/>Any reduction of the <code>\</code><code><em>xx</code>max</em> variables will slow
+<i>bm</i> down &mdash; but that&rsquo;s surely better than the document not
+running at all.  So unless you&rsquo;re using maths fonts (such as
+<i>Mathtime Plus</i>) that feature a heavy symbol weight, suppress all
+use of heavy families by
+<blockquote>
+<pre>
+  \renewcommand{\hmmax}{0}
+</pre>
+</blockquote><p>
+and then steadily reduce the bold families, starting with
+<blockquote>
+<pre>
+  \renewcommand{\bmmax}{3}
+</pre>
+</blockquote><p>
+until (with a bit of luck) the error goes away.
+<dl>
+<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html
new file mode 100644
index 00000000000..55669eb2d3c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html
@@ -0,0 +1,46 @@
+<head>
+<title>UK TeX FAQ -- question label marginmanual</title>
+</head><body>
+<h3>How to set up page layout &ldquo;by hand&rdquo;</h3>
+<p/>So you&rsquo;re eager to do it yourself, notwithstanding the cautions
+
+  outlined in &ldquo;<a href="FAQ-changemargin.html">changing margins</a>&rdquo;.
+<p/>It&rsquo;s important that you first start by familiarising yourself
+with LaTeX&rsquo;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 <a href="FAQ-books.html">LaTeX books</a>). 
+<p/>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
+<code>\</code><code>layout</code> command which draws a diagram of your existing page
+layout, with the dimensions (but not their interrelationships) shown.
+<p/>Even changing the text height and width, <code>\</code><code>textheight</code> and
+<code>\</code><code>textwidth</code>, 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 <code>\</code><code>baselinskip</code>), and the width should be constrained
+by the number of characters per line, as mentioned in 
+&ldquo;<a href="FAQ-changemargin.html">changing margins</a>&rdquo;.
+<p/>Margins are controlled by two parameters: <code>\</code><code>oddsidemargin</code> and
+<code>\</code><code>evensidemargin</code>, whose names come from the convention that
+odd-numbered pages appear on the right-hand side (&lsquo;recto&rsquo;) of a
+two-page spread and even-numbered pages on the left-hand side
+(&lsquo;verso&rsquo;).  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 <code>\</code><code>textwidth</code> and the width of the
+paper.  (In a one-sided document, which is the default in many
+classes, including the standard <i>article</i> and <i>report</i>
+classes, <code>\</code><code>oddsidemargin</code> stands for both.)
+<p/>The
+&ldquo;origin&rdquo; (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
+<code>\</code><code>evensidemargin</code>, <code>\</code><code>oddsidemargin</code> and <code>\</code><code>topmargin</code>, 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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html
new file mode 100644
index 00000000000..2746486f12f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label marginparside</title>
+</head><body>
+<h3>Getting <code>\</code><code>marginpar</code> on the right side</h3>
+<p/>In an ideal world, marginal notes would be in &ldquo;analogous&rdquo; 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&rsquo;s thought shows that a marginal note on the left needs to be
+typeset differently from a marginal note on the right.  The LaTeX
+<code>\</code><code>marginpar</code> command therefore takes two arguments in a
+<code>twoside</code> documents: 
+<code>\</code><code>marginpar[</code><em>left text</em><code>]{</code><em>right text</em><code>}</code>.  LaTeX uses the
+&ldquo;obvious&rdquo; test to
+get the <code>\</code><code>marginpar</code>s in the correct margin, but a booby-trap arises
+because TeX runs its page maker asynchronously.  If a
+<code>\</code><code>marginpar</code> is processed while page n is being built, but
+doesn&rsquo;t get used until page n+1, then the <code>\</code><code>marginpar</code> will turn
+up on the wrong side of the page.  This is an instance of a general
+problem: see
+
+&ldquo;<a href="FAQ-oddpage.html">finding if you&rsquo;re on an odd or an even page</a>&rdquo;.
+<p/>The solution to the problem is for LaTeX to &lsquo;remember&rsquo; which side
+of the page each <code>\</code><code>marginpar</code> <em>should</em> be on.  The
+<i>mparhack</i> package does this, using label-like marks stored in
+the <code>.aux</code> file; the <i>memoir</i> class does likewise.
+<dl>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>mparhack.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mparhack.zip">macros/latex/contrib/mparhack</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mparhack.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mparhack/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html
new file mode 100644
index 00000000000..a8a81d47fe4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label marginpkgs</title>
+</head><body>
+<h3>Packages to set up page designs</h3>
+<p/>The &lsquo;ultimate&rsquo; tool for adjusting the dimensions and position of the
+printed material on the page is the <i>geometry</i> package; a very
+wide range of adjustments of the layout may be relatively
+straightforwardly programmed, and package documentation is good and
+comprehensive.
+<p/>As is usual, users of the <i>memoir</i> class have built-in
+facilities for this task, and users of the <i>KOMA-script</i> classes
+are recommended to use an alternative package, <i>typearea</i>.  In
+either case it is difficult to argue that users should go for
+<i>geometry</i>: both alternatives are good.
+<p/>The documentation of <i>geometry</i> is a bit overwhelming, and
+learning all its capabilities may be more than you ever need.
+Somewhat simpler to use is the <i>vmargin</i> package, which has a
+canned set of paper sizes (a superset of that provided in LaTeX2e),
+provision for custom paper, margin adjustments and provision for
+two-sided printing.
+<dl>
+<dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>layout.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>vmargin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.zip">macros/latex/contrib/vmargin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html
new file mode 100644
index 00000000000..1f7f5f25f3b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label matchbrak</title>
+</head><body>
+<h3>My brackets don&rsquo;t match</h3>
+<p/>(La)TeX has a low-level mechanism for matching braces in document
+text.  This means you can type something like:
+<blockquote>
+<pre>
+\section{All \emph{OK} now.}
+</pre>
+</blockquote><p>
+and know that the first brace (for the argument of <code>\</code><code>section</code>) will
+be matched with the last brace, and the internal pair of braces (for
+the argument of <code>\</code><code>emph</code>) will be matched with each other.  It&rsquo;s all
+very simple.
+<p/>However, LaTeX has a convention of enclosing optional arguments in
+brackets, as in:
+<blockquote>
+<pre>
+\section[OK]{All \emph{OK} now.}
+</pre>
+</blockquote><p>
+These brackets are not matched by TeX mechanisms, despite the
+superficial similarity of their use.  As a result,
+straightforward-looking usages like:
+<blockquote>
+<pre>
+\section[All [OK] now]{All \emph{OK} now.}
+</pre>
+</blockquote><p>
+aren&rsquo;t OK at all &mdash; the optional argument comes to consist of
+&ldquo;All [OK&rdquo;, and <code>\</code><code>section</code> takes the single character &ldquo;n&rdquo; (of
+the first &ldquo;now&rdquo;) as its argument.
+<p/>Fortunately, TeX&rsquo;s scanning mechanisms helps us by accepting the
+syntax &ldquo;<code>{]}</code>&rdquo; to &lsquo;hide&rsquo; the closing bracket from the
+scanning mechanism that LaTeX uses.  In practice, the commonest way
+to use this facility is:
+<blockquote>
+<pre>
+\section[All {[OK]} now]{All \emph{OK} now.}
+</pre>
+</blockquote><p>
+since bracing the bracket on its own &ldquo;looks odd&rdquo;.
+<p/>LaTeX has another argument syntax, even less regular, where the
+argument is enclosed in parentheses, as in:
+<blockquote>
+<pre>
+\put(1,2){foo}
+</pre>
+</blockquote><p>
+(a picture environment command).
+<p/>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.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html
new file mode 100644
index 00000000000..6308b2a33a8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html
@@ -0,0 +1,45 @@
+<head>
+<title>UK TeX FAQ -- question label mathlips</title>
+</head><body>
+<h3>Ellipses</h3>
+<!-- <code>\</code><code>dots</code> <code>\</code><code>cdots</code> <code>\</code><code>vdots</code> <code>\</code><code>ddots</code> -->
+<p/>Ellipses are commonly required, and LaTeX natively supplies a fair
+range (<code>\</code><code>dots</code>, <code>\</code><code>cdots</code>, <code>\</code><code>vdots</code> and <code>\</code><code>ddots</code>).  By using
+the <i>graphics</i> package, one can change the slope of the
+<code>\</code><code>ddots</code> command, as in
+<pre>
+  $ ... \reflectbox{$\ddots$} ... $
+</pre>
+While this works, it is not a recommended way of achieving the desired
+result (see below).  Moreover, LaTeX&rsquo;s range is not adequate to
+everyone&rsquo;s requirements, and at least three packages provide
+extensions to the set.
+<p/>The AMSLaTeX bundle provides a range of &ldquo;semantically-named&rdquo;
+ellipses, for use in different situations: <code>\</code><code>dotsb</code> for use between
+pairs of binary operators, <code>\</code><code>dotsc</code> for use between pairs of commas,
+and so on.
+<p/>The <i>yhmath</i> package defines an <code>\</code><code>adots</code> command, which is
+the analogue of <code>\</code><code>ddots</code>, sloping forwards rather than backwards.
+The <i>yhmath</i> package comes with a rather interesting font that
+extends the standard <i>cmex</i>; details are in the documentation.
+The disadvantage of this setup is, that although <code>\</code><code>adots</code> is merely
+a macro, the package tries to load its own font and produces a
+&ldquo;missing font&rdquo; substitution warning message if you haven&rsquo;t installed
+the font.
+<p/>The <i>mathdots</i> package (besides fixing up the behaviour of
+(La)TeX <code>\</code><code>ddots</code> and <code>\</code><code>vdots</code> when the font size changes)
+provides an &ldquo;inverse diagonal&rdquo; ellipsis <code>\</code><code>iddots</code> (doing the same
+job as <i>yhmath</i>&rsquo;s <code>\</code><code>adots</code>, but better).
+<p/>Documentation of <i>yhmath</i> appears, processed, in the
+distribution (thus saving you the bother of installing the package
+before being able to read the documentation).  Documentation of
+<i>mathdots</i> appears at the end the package file itself.
+<dl>
+<dt><tt><i>amslatex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>graphics.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle
+<dt><tt><i>mathdots.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/mathdots.zip">macros/generic/mathdots</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/mathdots.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/mathdots/">browse</a>)
+<dt><tt><i>yhmath (fonts)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.zip">fonts/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/yhmath/">browse</a>)
+<dt><tt><i>yhmath (macros)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.zip">macros/latex/contrib/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/yhmath/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html
new file mode 100644
index 00000000000..39bdeb00df9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html
@@ -0,0 +1,104 @@
+<head>
+<title>UK TeX FAQ -- question label mathml</title>
+</head><body>
+<h3>Future WWW technologies and (La)TeX</h3>
+<p/>An earlier answer 
+(<a href="FAQ-LaTeX2HTML.html">&ldquo;converting to HTML&rdquo;</a>)
+addresses the issue of converting existing (La)TeX documents for
+viewing on the Web as HTML.  All the present techniques are
+somewhat flawed: the answer explains why.
+<p/>However, things are changing, with
+better font availability, cunning HTML programming and the
+support for new Web standards.
+<dl>
+<dt>Font technologies<dd> Direct representation of mathematics in
+  browsers has been hampered up to now by the limited range of symbols
+  in the fonts one can rely on being available.  Some existing
+  (La)TeX to 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 HTML so generated.
+<p/>  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.
+<dt>XML<dd> The core of the range of new standards is
+  XML, which provides a framework for better structured markup;
+  limited support for it has already appeared in some browsers.
+<p/>  Conversion of (La)TeX source to XML is already available
+  (through TeX4ht at least), and work continues in that arena.  The
+  alternative, authoring in XML (thus producing documents that
+  are immediately Web-friendly, if not ready) and using (La)TeX to
+  typeset is also well advanced.  One useful technique is
+  <a href="FAQ-SGML2TeX.html"><em>transforming</em> the XML to LaTeX</a>,
+  using an XSLT stylesheet or code for an XML library,
+  and then simply using LaTeX; alternatively, one may
+  <a href="FAQ-readML.html">typeset direct from the XML source</a>.
+<dt>Direct representation of mathematics<dd>
+  MathML is a standard for representing maths on the Web; its
+  original version was distinctly limited, but version 2 of MathML
+  has had major browser support since 2002 with richness of mathematical
+  content for online purposes approaching that of TeX for print.
+  Browser support for MathML is provided by <i>amaya</i>, the
+  &lsquo;Open Source&rsquo; browser <i>mozilla</i> (and its derivatives
+  including <i>NetScape</i>, <i>Firefox</i> and <i>Galeon</i>) and
+  <i>Internet Explorer</i> when equipped with a suitable plug-in
+  such as <i>MathPlayer</i>.
+  There&rsquo;s evidence that (La)TeX users are starting to use such
+  browsers.  Some believe that XHTML+MathML now provides
+  better online viewing than PDF.
+  Work to produce XHTML+MathML is well advanced in both the
+  TeX4ht and <i>TtH</i> projects for (La)TeX conversion.
+
+
+
+<p/>  An approach different from (La)TeX conversion is taken by
+  the <a href="http://www.albany.edu/~hammond/gellmu/"><em>GELLMU</em> Project</a>.
+  Its <em>article</em> 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 &mdash; so far), comes with translators
+  that make both PDF (via <em>pdflatex</em>) and
+  XHTML+MathML.  Such an approach avoids the inherent
+  limitations of the &ldquo;traditional&rdquo; (La)TeX translation processes,
+  which have traps that can be sprung by unfettered use of (La)TeX
+  markup.
+<dt>Graphics<dd> 
+  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 MathML).
+<p/>  Browser plug-ins, that deal with SVG are already available
+  (Adobe offer one, for example).  More recently, the open source
+  graphics editor <a href="http://www.inkscape.org/"><i>Inkscape</a></i>
+  has appeared, and has been reported to be useful for
+  SVG-related work in at least one TeX-related project.  Be
+  aware that the developers of <i>Inkscape</i> have no illusions
+  about being able to replace commercial software, yet...
+<dt>Direct use of TeX markup<dd>
+  Some time back, IBM developed a browser plug-in called
+  TechExplorer, which would display (La)TeX documents direct in a
+  browser.  Over the years, it developed into a MathML browser
+  plug-in, while still retaining its (La)TeX abilities, but it&rsquo;s now
+  distributed (free for Linux and Windows platforms) by
+  <a href="http://www.integretechpub.com/">Integre Technical Publishing</a>.
+<p/>  The disadvantage of the TechExplorer approach is that it places the
+  onus on the browser user; and however technically proficient
+  <em>you</em> are, it&rsquo;s never safe to assume too much of your readers.
+  An interesting alternative is
+  <a href="http://www.forkosh.com/mimetex.html">MimeTeX</a>, which sits
+  on your server as a CGI script, and you use it to include
+  your TeX, in your HTML, as if it were an image:
+<blockquote>
+<pre>
+&lt;img src="../cgi-bin/mimetex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt"&gt;
+</pre>
+
+</blockquote><p>
+</dl>
+<dl>
+<dt><tt><i>GELLMU</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/gellmu.zip">support/gellmu</a> (<a href="ftp://cam.ctan.org/tex-archive/support/gellmu.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/gellmu/">browse</a>)
+<dt><tt><i>MimeTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mimetex.zip">support/mimetex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mimetex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mimetex/">browse</a>)
+<dt><tt><i>TeX4HT</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html
new file mode 100644
index 00000000000..317eb2cd798
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label mathonlyref</title>
+</head><body>
+<h3>Numbers for referenced equations only</h3>
+<p/>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.
+<p/>If you hold to the &ldquo;only cross-referenced&rdquo; school of thought, you
+can (using the <code>\</code><code>nonumber</code> command on the relevant equations, or by
+using the AMSLaTeX unnumbered environments such as
+<code>equation*</code>) mark those of your equations to which you
+make no reference.  In a long or complex paper, this procedure could
+well become deeply tedious.
+<p/>Fortunately, help is at hand: the <i>mh</i> bundle&rsquo;s
+<i>mathtools</i> package offers a &lsquo;<code>showonlyrefs</code>&rsquo;
+switch through its <code>\</code><code>mathtoolsset</code> command; when that&rsquo;s in
+operation, only those equations to which you make reference will be
+numbered in the final output.  See the package&rsquo;s documentation for
+details of how to make references when the switch is in effect.
+<dl>
+<dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html
new file mode 100644
index 00000000000..c24a7c06895
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html
@@ -0,0 +1,58 @@
+<head>
+<title>UK TeX FAQ -- question label mathsize</title>
+</head><body>
+<h3>Adjusting maths font sizes</h3>
+<p/>In Plain TeX, 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 <code>\</code><code>textfont</code>, <code>\</code><code>scriptfont</code> and
+<code>\</code><code>scriptscriptfont</code> for the maths families you&rsquo;re using; all such
+things are described in chapter 17 of the 
+<a href="FAQ-books.html">TeXbook</a> and in other books and
+<a href="FAQ-man-tex.html">tutorials</a> that discuss Plain TeX in sufficient
+detail.
+<p/>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 &ldquo;known&rdquo; text sizes,
+for each of which maths sizes are declared in advance.  If the text
+size isn&rsquo;t &ldquo;known&rdquo;, the script- and scriptscriptfont sizes are
+calculated as fixed ratios of the tex font size.  (The values used are
+<code>\</code><code>defaultscriptratio</code>=0.7, and
+<code>\</code><code>defaultscriptscriptratio</code>=0.5.)
+<p/>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&rsquo;s ideas altogether, for example by setting maths noticeably
+larger or smaller than its surrounding text.  For this purpose, the
+LaTeX command
+<code>\</code><code>DeclareMathSizes{&lt;<i>tfs</i>&gt;}{&lt;<i>ts</i>&gt;}{&lt;<i>ss</i>&gt;}{&lt;<i>sss</i>&gt;}</code>
+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
+<code>&lt;<i>tfs</i>&gt;</code>; (<code>&lt;<i>ts</i>&gt;</code> being the size used for
+<code>\</code><code>textfont</code>, <code>&lt;<i>ss</i>&gt;</code> for <code>\</code><code>scriptfont</code> and
+<code>&lt;<i>sss</i>&gt;</code> for <code>\</code><code>scriptscriptfont</code>).
+<p/>For example, you might want to use a font with a smaller body height
+than Computer Modern, but still prefer CM math to any of the
+alternatives.  In this case, you might use:
+<blockquote>
+<pre>
+\DeclareMathSizes{10}{9}{7}{5}
+</pre>
+</blockquote><p>
+to get 9pt maths when the surrounding body text is (nominal) 10pt.
+<p/><code>\</code><code>DeclareMathSizes</code> 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
+<i>fontdef.dtx</i> in the latex distribution, and are compiled into
+<i>fontmath.ltx</i>; the arguments to the command are just numbers
+(&lsquo;<code>pt</code>&rsquo; is assumed), but some of them are written using
+<a href="FAQ-ltxabbrv.html">LaTeX abbreviations</a> for standard font sizes.
+Beware simply copying (parts of) the LaTeX definitions &mdash; since
+they contain those internal abbreviations, they need to be treated as
+<a href="FAQ-atsigns.html">internal commands</a>.
+<dl>
+<dt><tt><i>fontdef.dtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/fontdef.dtx">macros/latex/base/fontdef.dtx</a>
+<dt><tt><i>fontmath.ltx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/unpacked/fontmath.ltx">macros/latex/unpacked/fontmath.ltx</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html
new file mode 100644
index 00000000000..777930ef9f9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html
@@ -0,0 +1,124 @@
+<head>
+<title>UK TeX FAQ -- question label mathstext</title>
+</head><body>
+<h3>Text inside maths</h3>
+<p/>When we type maths in (La)TeX, 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&rsquo;s
+not the same sort of italics that you see when you&rsquo;re typing ordinary
+text: a run of maths letters (for example &ldquo;here&rdquo;) looks oddly
+&ldquo;lumpy&rdquo; 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&rsquo;re
+multiplying <em>h</em> by <em>e</em> by <em>r</em> by <em>e</em>.  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.
+<p/>So, if we&rsquo;re going to have good-looking text in amongst maths we&rsquo;re
+writing, we have to take special precautions.  If you&rsquo;re using
+LaTeX, the following should help.
+<p/>The simplest is to use <code>\</code><code>mbox</code> or <code>\</code><code>textrm</code>:
+<blockquote>
+<pre>
+$e = mc^2 \mbox{here we go again}$
+</pre>
+</blockquote><p>
+The problem is that, with either, the size of the text remains firmly
+at the surrounding text size, so that
+<blockquote>
+<pre>
+$z = a_{\mbox{other end}}$
+</pre>
+</blockquote><p>
+looks quite painfully wrong.
+<p/>The other simple technique, <code>\</code><code>textrm</code>, is more promising:
+<blockquote>
+<pre>
+$z = a_{\textrm{other end}}$
+</pre>
+</blockquote><p>
+is definitely right.  However, the surrounding text may not be in your
+roman font; if you care about matching text, you need to choose
+between <code>\</code><code>textrm</code>, <code>\</code><code>textsf</code>, and so on.
+<p/>(The maths-mode instance of your roman font (<code>\</code><code>mathrm</code>) gets the
+size right, but since it&rsquo;s intended for use in maths, its spaces get
+ignored &mdash; use <code>\</code><code>mathrm</code> for upright roman alphabetic variable
+names, but not otherwise.)
+<p/>You can correct these problems with size selectors in the text, as:
+<blockquote>
+<pre>
+$z = a_{\mbox{\scriptsize other end}}$
+</pre>
+</blockquote><p>
+which works if your surrounding text is at default document size, but
+gives you the wrong size otherwise.
+<p/>These short cuts are (just about) OK for the &ldquo;occasional&rdquo;
+mathematician, but serious mathematics calls for a technique that
+relieves the typist of the sort of thought required.  As usual, the
+AMSLaTeX system provides what&rsquo;s necessary &mdash; the <code>\</code><code>text</code>
+command.  The command is actually provided by the <i>amstext</i>
+package, but the &ldquo;global&rdquo; <i>amsmath</i> package loads it, so
+anyone using AMSLaTeX proper has the command available, so even
+joke mathematicians can write:
+<blockquote>
+<pre>
+\usepackage{amsmath}
+...
+$z = a_{\text{other end}}$
+</pre>
+</blockquote><p>
+and the text will be at the right size, and in the same font as
+surrounding text.
+<p/>AMSLaTeX also makes provision for interpolated comments in the
+middle of one of its multi-line display structures, through the
+<code>\</code><code>intertext</code> command.  For example:
+<blockquote>
+
+<pre>
+\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}
+</pre>
+</blockquote><p>
+places the text &ldquo;and&rdquo; 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 <code>\</code><code>intertext</code> leaves
+too much space.  Slightly more modest is the <code>\</code><code>shortintertext</code>
+command from the <i>mathtools</i> package:
+<blockquote>
+<pre>
+\begin{align}
+  a =& b
+  \shortintertext{or}
+  c =& b
+\end{align}
+</pre>
+</blockquote><p>
+To have the text on the same line as the second equation, one can use
+the <code>flalign</code> environment (from <i>amsmath</i>)
+with lots of dummy equations (represented by the double <code>&amp;</code>
+signs):
+<blockquote>
+<pre>
+\begin{flalign}
+            && a =& b && \\
+  \text{or} && c =& b &&
+\end{flalign}
+</pre>
+</blockquote><p>
+<p/>Comprehensive documentation of AMSLaTeX is to be found in
+<i>amsldoc</i>, in the distribution; it is also available on the web
+at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a>
+<dl>
+<dt><tt><i>amsldoc.tex</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>amstext.sty</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of the <i>mh</i> bundle
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html
new file mode 100644
index 00000000000..8184f2d9ad3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label mcfloat</title>
+</head><body>
+<h3>Floats in multicolumn setting</h3>
+<p/>If you use
+<blockquote>
+<pre>
+\begin{figure}
+  ...
+\end{figure}
+</pre>
+</blockquote><p>
+in a <code>multicols</code> environment, the figure won&rsquo;t appear.  If
+instead you use
+<blockquote>
+<pre>
+\begin{figure*}
+  ...
+\end{figure*}
+</pre>
+</blockquote><p>
+the figure will stretch right across the page (just the same as a
+<code>figure*</code> in standard LaTeX&rsquo;s <code>twocolumn</code> option).
+<p/>It&rsquo;s possible to have single-column figures and tables with captions,
+using the &lsquo;<code>[H]</code>&rsquo; placement option introduced by the <i>float</i>
+package but you might have to fiddle with the placement because they
+won&rsquo;t &lsquo;float&rsquo;, and exhibit other strange behaviours (such as silently
+running off the end of the column at the end of the
+<code>multicols</code> environment).
+<dl>
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html
new file mode 100644
index 00000000000..4a577b1dabc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html
@@ -0,0 +1,48 @@
+<head>
+<title>UK TeX FAQ -- question label mcite</title>
+</head><body>
+<h3>Multiple citations</h3>
+<p/>A convention sometimes used in physics journals is to &ldquo;collapse&rdquo; a group of
+related citations into a single entry in the bibliography.  BibTeX,
+by default, can&rsquo;t cope with this arrangement, but the <i>mcite</i>
+package deals with the problem.
+<p/>The package overloads the <code>\</code><code>cite</code> command to recognise a
+&ldquo;<code>*</code>&rdquo; at the start of a key, so that citations of the form
+<blockquote>
+<pre>
+\cite{paper1,*paper2}
+</pre>
+</blockquote><p>
+appear in the document as a single citation, and appear arranged
+appropriately in the bibliography itself.  You&rsquo;re not limited to
+collapsing just two references.  You can mix &ldquo;collapsed&rdquo; references
+with &ldquo;ordinary&rdquo; ones, as in
+<blockquote>
+<pre>
+\cite{paper0,paper1,*paper2,paper3}
+</pre>
+</blockquote><p>
+Which will appear in the document as 3 citations &ldquo;[4,7,11]&rdquo;
+(say) &mdash; citation &lsquo;4&rsquo; will refer to paper 0, &lsquo;7&rsquo; will refer to a
+combined entry for paper 1 and paper 2, and &lsquo;11&rsquo; will refer to
+paper 3.
+<p/>You need to make a small change to the bibliography style
+(<code>.bst</code>) file you use; the <i>mcite</i> package
+documentation tells you how to do that.
+<p/>Unfortunately, the <i>revtex</i> system doesn&rsquo;t play with
+<i>mcite</i>.  As a result, for that (primarily physics-targeted
+system) you need to play silly games like:
+<blockquote>
+<pre>
+\cite{paper0,paper1,paper3}
+\nocite{paper2}
+</pre>
+</blockquote><p>
+and then edit the <code>.bbl</code> file to merge the two citations, to
+achieve the effects of <i>mcite</i>.
+<dl>
+<dt><tt><i>mcite.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mcite.zip">macros/latex/contrib/mcite</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mcite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mcite/">browse</a>)
+<dt><tt><i>revtex bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/revtex.zip">macros/latex/contrib/revtex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/revtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/revtex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html
new file mode 100644
index 00000000000..06dd0d2de82
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label metrics</title>
+</head><body>
+<h3>TeX font metric files for PostScript fonts</h3>
+<p/>Reputable font vendors such as Adobe supply metric files for each
+font, in AFM (Adobe Font Metric) form; these can be converted
+to 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 <em>encoding</em> of
+(Latin character) fonts; while we all more or less agree about the
+position of about 96 characters in fonts (the basic ASCII set), the
+rest of the (typically) 256 vary. The most obvious problems are with
+floating accents and special characters such as the &lsquo;pounds sterling&rsquo;
+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 <a href="FAQ-virtualfonts.html">virtual fonts</a> to
+<em>pretend</em> to TeX that the encoding is the same as it is used to.
+LaTeX2e has facilities for dealing with fonts in different
+encodings; read the <a href="FAQ-books.html"><em>LaTeX Companion</em></a> for
+more details.  In practice, if you do much non-English (but Latin
+script) typesetting, you are strongly recommended to use the
+<i>fontenc</i> package with option &lsquo;<code>T1</code>&rsquo; to select
+<a href="FAQ-ECfonts.html">&lsquo;Cork&rsquo;</a> encoding.
+A useful alternative is Y&amp;Y&rsquo;s &ldquo;private&rdquo; LY1 encoding,
+which is designed to sit well with &ldquo;Adobe standard&rdquo; encoded fonts.
+Basic support of LY1 is available on CTAN: note that the
+&ldquo;relation with Adobe&rsquo;s encoding&rdquo; means that there are no
+virtual fonts in the LY1 world.
+<p/>Alan Jeffrey&rsquo;s <i>fontinst</i> package is an AFM to
+TFM converter written in TeX; it is used to generate the
+files used by LaTeX2e&rsquo;s PSNFSS package to support use of
+PostScript 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 <a href="FAQ-virtualfonts.html">virtual fonts</a>.
+<p/>For slightly simpler problems, Rokicki&rsquo;s <i>afm2tfm</i>,
+distributed with <i>dvips</i>, is fast and
+efficient; note that the metrics and styles that come with
+<i>dvips</i> are <em>not</em> currently LaTeX2e compatible.
+<p/>For the Macintosh (classic), there is a program called
+<i>EdMetrics</i> which does the job (and more).
+<i>EdMetrics</i> comes with the (commercial)
+<a href="FAQ-commercial.html">Textures</a> distribution, but is itself free
+software, and is available on CTAN.
+
+
+
+
+<dl>
+<dt><tt><i>dvips</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvips.zip">dviware/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvips/">browse</a>)
+<dt><tt><i>EdMetrics</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/textures/utilities/EdMetrics.sea.hqx">systems/mac/textures/utilities/EdMetrics.sea.hqx</a>
+<dt><tt><i>fontinst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>)
+<dt><tt><i>LY1 support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/ly1.zip">macros/latex/contrib/psnfssx/ly1</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/ly1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psnfssx/ly1/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html
new file mode 100644
index 00000000000..a43366b900e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label mfptutorials</title>
+</head><body>
+<h3>Metafont and MetaPost Tutorials</h3>
+<p/>Apart from Knuth&rsquo;s book, there seems to be only one publicly-available
+<a href="http://metafont.tutorial.free.fr/">tutorial for Metafont</a>, by
+Christophe Grandsire (a copy in PDF form may be downloaded).
+Geoffrey Tobin&rsquo;s <i>Metafont for Beginners</i> 
+(see <a href="FAQ-useMF.html">using Metafont</a>) describes how the Metafont
+system works and how to avoid some of the potential pitfalls.
+<p/>There is also an article on how to run both Metafont and MetaPost (the
+programs).  Peter Wilson&rsquo;s 
+<i>Some Experiences in Running Metafont and MetaPost</i>
+offers the benefit of Peter&rsquo;s experience (he has designed a number of
+&lsquo;historical&rsquo; fonts using Metafont).  For Metafont the article is geared
+towards testing and installing new Metafont fonts, while its MetaPost
+section describes how to use MetaPost illustrations in LaTeX and
+PDFLaTeX documents, with an emphasis on how to use appropriate
+fonts for any text or mathematics.
+<p/>
+
+
+
+<p/>Other MetaPost tutorials that have appeared are two in English by 
+<a href="http://remote.science.uva.nl/~heck/Courses/mptut.pdf">Andr&eacute; Heck</a>
+and <a href="http://www.tlhiv.org/MetaPost/tutorial/">Urs Oswald</a>,
+and one in French (listed here because it&rsquo;s clearly enough written
+that even this author understands it), by
+<a href="http://pauillac.inria.fr/~cheno/metapost/metapost.pdf">Laurent Ch&eacute;no</a>;
+both have been recommended for inclusion in the FAQ
+<p/>Urs Oswald&rsquo;s tutorial is accompanied by a super tool (by Troy
+Henderson) for testing little bits of MetaPost, which is an invaluable
+aid to the learner: <a href="http://www.tlhiv.org/mppreview">http://www.tlhiv.org/mppreview</a>
+<p/>Vincent Zoonekynd&rsquo;s massive set of example MetaPost files is available on
+CTAN; the set includes a <i>Perl</i> script to convert the
+set to html, and the set may be 
+<a href="http://zoonek.free.fr/LaTeX/Metapost/metapost.html">viewed on the web</a>.
+While these examples don&rsquo;t exactly constitute a &ldquo;tutorial&rdquo;, they&rsquo;re
+most certainly valuable learning material.  Urs Oswald presents a
+<a href="http://www.ursoswald.ch/metapost/tutorial.pdf">similar document</a>,
+written more as a document, and presented in PDF.
+<dl>
+<dt><tt><i>Beginners&rsquo; guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont/beginners/metafont-for-beginners.pdf">info/metafont/beginners/metafont-for-beginners.pdf</a>
+<dt><tt><i>Peter Wilson&rsquo;s &ldquo;experiences&rdquo;</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont/metafp/metafp.pdf">info/metafont/metafp/metafp.pdf</a>
+  (PDF format) 
+<dt><tt><i>Vincent Zoonekynd&rsquo;s examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (<a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html
new file mode 100644
index 00000000000..75fec2d9e7a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label minitoc</title>
+</head><body>
+<h3>Table of contents, etc., per chapter</h3>
+<p/>The common style, of a &ldquo;small&rdquo; table of contents for each part,
+chapter, or even section, is supported by the <i>minitoc</i>
+package.  The package also supports mini-lists of tables and figures;
+but, as the documentation observes, mini-bibliographies are a
+different problem &mdash; see
+<a href="FAQ-chapbib.html">bibliographies per chapter</a>.
+<p/>The package&rsquo;s basic scheme is to generate a little <code>.aux</code> file for
+each chapter, and to process that within the chapter.  Simple usage
+would be:
+<blockquote>
+<pre>
+\usepackage{minitoc}
+...
+\begin{document}
+...
+\dominitoc \tableofcontents
+\dominilof \listoffigures
+...
+\chapter{blah blah}
+\minitoc \mtcskip \minilof
+...
+</pre>
+</blockquote><p>
+though a lot of elaborations are possible (for example, you don&rsquo;t need
+a <code>\</code><code>minitoc</code> for every chapter).
+<p/><i>Babel</i> doesn&rsquo;t know about <i>minitoc</i>, but
+<i>minitoc</i> makes provision for other document languages than
+English &mdash; a wide variety is available.  Fortunately, the current
+version of the <i>hyperref</i> package does know about
+<i>minitoc</i> and treats <code>\</code><code>minitoc</code> tables in the
+same way as &ldquo;real&rdquo; tables of contents.
+<dl>
+<dt><tt><i>babel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.zip">macros/latex/required/babel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel/">browse</a>)
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>minitoc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/minitoc.zip">macros/latex/contrib/minitoc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/minitoc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/minitoc/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html
new file mode 100644
index 00000000000..75e9c7b1b0f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html
@@ -0,0 +1,75 @@
+<head>
+<title>UK TeX FAQ -- question label minxampl</title>
+</head><body>
+<h3>How to make a &ldquo;minimum example&rdquo;</h3>
+<p/><a href="FAQ-askquestion.html">Our advice on asking questions</a>
+suggests that you prepare a &ldquo;minimum example&rdquo; (also commonly known
+as a &ldquo;<em>minimal</em> example&rdquo;) 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.
+<p/>There are two valid approaches to this task: building up, and hacking
+down.
+<p/>
+<b><em>Building up</em></b> starts
+with a basic document structure
+(for LaTeX, this would have <code>\</code><code>documentclass</code>,
+<code>\</code><code>begin{document}</code>, <code>\</code><code>end{document}</code>) 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&rsquo;s provoking the problem.  If the original problem is an
+error, reviewing 
+<a href="FAQ-errstruct.html">&ldquo;the structure of TeX errors&rdquo;</a>
+may help.)
+<p/>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 &lt;<i>something</i>&gt; (from something in a
+<code>\</code><code>caption</code>).  In such a case, include the section title or caption
+(the caption probably needs the <code>figure</code> or
+<code>table</code> environment around it, but it <em>doesn&rsquo;t</em> need
+the figure or table itself).
+<p/>If this file you&rsquo;ve built up shows the problem already, then you&rsquo;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&rsquo;t even load
+properly unless another package has been loaded.  (Another common case
+is that package <i>A</i> only fails when package <i>B</i> has been
+loaded.)
+<p/>
+<b><em>Hacking down</em></b> starts
+with your entire document, and
+removes bits until the file no longer fails (and then of course
+restores the last thing removed).  Don&rsquo;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 &ldquo;building up&rdquo; route.
+<p/>If you&rsquo;ve added a package (or more than one), add <code>\</code><code>listfiles</code> to
+the preamble too: that way, LaTeX will produce a list of the
+packages you&rsquo;ve used and their version numbers.  This information may
+be useful evidence for people trying to help you.
+<p/>What if your document simply doesn&rsquo;t fail in any of these cut-down
+scenarios?  Whatever you do, don&rsquo;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&rsquo;s impossible ... 
+or inadvisable, in the case of something confidential.
+<p/>If the whole document is necessary, it could be that it&rsquo;s an overflow
+of some sort; the best you can do is to post the code &ldquo;around&rdquo; the
+error, and (of course) the full text of the error.
+<p/>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.
+<p/>First, preparing a minimum document very often leads <em>you</em> to the
+answer, without all the fuss of posting and looking for responses.
+<p/>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
+&ldquo;in a single pass&rdquo;: 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.
+<p/>All things considered, a good example file can save you a day, for
+perhaps half an hour&rsquo;s effort invested.
+<p/>The above advice, differently phrased, may also be read on the web at
+<a href="http://www.minimalbeispiel.de/mini-en.html">http://www.minimalbeispiel.de/mini-en.html</a>; source of that
+article may be found at <a href="http://www.minimalbeispiel.de/">http://www.minimalbeispiel.de/</a>, in
+both German and English.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html
new file mode 100644
index 00000000000..75ea3442415
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label missbegdoc</title>
+</head><body>
+<h3>Missing <code>\</code><code>begin</code><code>{document}</code></h3>
+<p/>Give it a file of plain text, or a LaTeX file that really does have no
+<code>\</code><code>begin{document}</code> command in it, and LaTeX will produce
+this error, quite correctly.  LaTeX <em>needs</em>
+<code>\</code><code>begin{document}</code> so as to know when to execute the commands
+that finish off the document preamble.
+<p/>Other than that, the error can occur as a result of an error of yours,
+of a corrupt <code>.aux</code> file, or of a buggy class or package.
+<p/>The errors you might commit are absent-mindedly typing a document
+command (such as <code>\</code><code>section</code>) in the preamble of your document,
+missing the comment marker from the beginning of a line, or giving too
+many arguments to one of the setup commands related to the class or a
+package that you have loaded.
+<p/>A corrupt <code>.aux</code> file might be due to any number of things;
+delete the file and to run LaTeX again, twice.  If the error
+recurs, it&rsquo;s probably due to a buggy class or package.
+<p/>If the error occurs while LaTeX is reading a class or package, then
+there&rsquo;s probably a bug in the file.  The author of the class or
+package stands the best chance of finding the bug, but with luck you
+(or someone you ask on a mailing list or on <i>comp.text.tex</i>)
+will be able to spot the problem and provide a work-around.  Always
+report such bugs, even if you have found a work-around.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html
new file mode 100644
index 00000000000..cef0b600977
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label misschar</title>
+</head><body>
+<h3>Where have my characters gone?</h3>
+<p/>You&rsquo;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&rsquo;t have a
+representation for the character in question.
+<p/>For example, if I type &ldquo;that will be &pound;44.00&rdquo; into an ordinary
+(La)TeX document, or if I select the font <code>rsfs10</code> (which contains
+uppercase letters only) and type pretty much anything, the &pound;
+sign, or any lowercase letters or digits will not appear in the
+output.  There&rsquo;s no actual error message, either: you have to read the
+log file, where you&rsquo;ll find cryptic little messages like
+<blockquote>
+<pre>
+Missing character: There is no ^^a3 in font cmr10!
+Missing character: There is no 3 in font rsfs10!
+</pre> 
+
+</blockquote><p>
+(the former demonstrating my TeX&rsquo;s unwillingness to deal in characters
+which have the eighth bit set, while the <code>rsfs10</code> example shows that
+TeX will log the actual character in error, if it thinks it&rsquo;s
+possible).
+<p/>Somewhat more understandable are the diagnostics you may get from
+<i>dvips</i> when using the OT1 and T1 versions of
+fonts that were supplied in Adobe standard encoding:
+<blockquote>
+<pre>
+dvips: Warning: missing glyph `Delta'
+</pre>
+</blockquote><p>
+The process that generates the metrics for using the fonts generates
+an instruction to <i>dvips</i> 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&rsquo;s text
+encodings and in the Cork encoding are not available in the Adobe
+fonts.  In these cases, there <em>is</em> a typeset sign of the
+character: <i>dvips</i> produces a black rectangle of whatever
+size the concocted font file has specified.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html
new file mode 100644
index 00000000000..24165ca886b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label misssymb</title>
+</head><body>
+<h3>Missing symbol commands</h3>
+<p/>You&rsquo;re processing an old document, and some symbol commands such as
+<code>\</code><code>Box</code> and <code>\</code><code>lhd</code> appear no longer to exist.  These commands were
+present in the core of LaTeX 2.09, but are not in current LaTeX.
+They are available in the <i>latexsym</i> package (which is part of
+the LaTeX distribution), and in the <i>amsfonts</i> package
+(which is part of the AMS distribution, and requires AMS
+symbol fonts).
+<dl>
+<dt><tt><i>amsfonts.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.zip">fonts/amsfonts/latex</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/latex/">browse</a>)
+<dt><tt><i>AMS symbol fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.zip">fonts/amsfonts/sources/symbols</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/symbols/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misssymb">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misssymb</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html
new file mode 100644
index 00000000000..20669160583
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html
@@ -0,0 +1,64 @@
+<head>
+<title>UK TeX FAQ -- question label moren9</title>
+</head><body>
+<h3>How to break the 9-argument limit</h3>
+<p/>If you think about it, you will realise that Knuth&rsquo;s command
+definition syntax:
+<blockquote>
+<pre>
+\def\blah#1#2 ... #9{&lt;macro body&gt;}
+</pre>
+</blockquote><p>
+is intrinsically limited to just 9 arguments.  There&rsquo;s no direct way
+round this: how would you express a 10th argument? &mdash; and ensure that
+the syntax didn&rsquo;t gobble some other valid usage?
+<p/>If you really must have more than 9 arguments, the way to go is:
+<blockquote>
+<pre>
+\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
+  &lt;macro body&gt;%
+}
+</pre>
+</blockquote><p>
+This technique is easily extendible by concert pianists of the TeX
+keyboard, but is really hard to recommend.
+<p/>LaTeX users have the small convenience of merely giving a number of
+arguments in the <code>\</code><code>newcommand</code> that defines each part of the
+relaying mechanism: Knuth&rsquo;s restriction applies to <code>\</code><code>newcommand</code>
+just as it does to <code>\</code><code>def</code>.  However, LaTeX users also have the
+way out of such barbarous command syntax: the <i>keyval</i>
+package.  With <i>keyval</i>, and a bit of programming, one can
+write really quite sophisticated commands, whose invocation might look
+like:
+<blockquote>
+<pre>
+\flowerinstance{species=Primula veris,
+  family=Primulaceae,
+  location=Coldham's Common,
+  locationtype=Common grazing land,
+  date=1995/04/24,
+  numplants=50,
+  soiltype=alkaline
+}
+</pre>
+</blockquote><p>
+The merit of such verbosity is that it is self-explanatory: the typist
+doesn&rsquo;t have to remember that argument twelve is <code>soiltype</code>, and so
+on: the commands may be copied from field notes quickly and
+accurately.
+<dl>
+<dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html
new file mode 100644
index 00000000000..848e6932446
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label mpprologues</title>
+</head><body>
+<h3>Displaying MetaPost output in <i>ghostscript</i></h3>
+<p/>MetaPost ordinarily expects its output to be included in some context
+where the &lsquo;standard&rsquo; Metafont fonts (that you&rsquo;ve specified) are already
+defined &mdash; for example, as a figure in TeX document.  If you&rsquo;re
+debugging your MetaPost code, you may want to view it in
+<i>ghostscript</i> (or some other PostScript previewer).  However,
+the PostScript &lsquo;engine&rsquo; in <i>ghostscript</i> <em>doesn&rsquo;t</em>
+ordinarily have the fonts loaded, and you&rsquo;ll experience an error such
+as
+<blockquote>
+<pre>
+Error: /undefined in cmmi10
+</pre>
+</blockquote><p>
+There is provision in MetaPost for avoiding this problem: issue the
+command <code>prologues := 2;</code> at the start of the <code>.mp</code> file.
+<p/>Unfortunately, the PostScript that MetaPost inserts in its output,
+following this command, is incompatible with ordinary use of the
+PostScript in inclusions into (La)TeX documents, so it&rsquo;s best to
+make the <code>prologues</code> command optional.  Furthermore, MetaPost takes a
+very simple-minded approach to font encoding: since TeX font
+encodings regularly confuse sophisticated minds, this can prove
+troublesome.  If you&rsquo;re suffering such problems (the symptom is that
+characters disappear, or are wrongly presented) the only solution is
+to view the &lsquo;original&rsquo; MetaPost output after processing through
+LaTeX and <i>dvips</i>.
+<p/>Conditional compilation may be done either
+by inputting <i>MyFigure.mp</i> indirectly from a simple wrapper
+<i>MyFigureDisplay.mp</i>:
+<blockquote>
+<pre>
+prologues := 2;
+input MyFigure
+</pre>
+</blockquote><p>
+or by issuing a shell command such as
+<blockquote>
+<pre>
+mp '\prologues:=2; input MyFigure'
+</pre>
+</blockquote><p>
+(which will work without the quote marks if you&rsquo;re not using a Unix
+shell).
+<p/>A suitable LaTeX route would involve processing
+<i>MyFigure.tex</i>, which contains:
+<blockquote>
+<pre>
+\documentclass{article}
+\usepackage{graphicx}
+\begin{document}
+\thispagestyle{empty}
+\includegraphics{MyFigure.1}
+\end{document}
+</pre>
+</blockquote><p>
+Processing the resulting DVI file with the <i>dvips</i>
+command
+<blockquote>
+<pre>
+dvips -E -o MyFigure.eps MyFigure
+</pre>
+</blockquote><p>
+would then give a satisfactory Encapsulated PostScript file.  This
+procedure may be automated using the <i>Perl</i> script
+<i>mps2eps</i>, thus saving a certain amount of tedium.
+<p/>The Plain TeX user may use an adaptation of a jiffy of Knuth&rsquo;s, by
+Dan Luecking.  Dan&rsquo;s version <i>mpsproof.tex</i> will work under
+TeX to produce a DVI file for use with <i>dvips</i>, or
+under PDFTeX to produce a PDF file, direct.  The output is
+set up to look like a proof sheet.
+<p/>A script application, <i>mptopdf</i>, is available in recent
+(La)TeX distributions: it seems fairly reliably to produce
+PDF from MetaPost, so may reasonably be considered an answer to
+the question...
+<dl>
+<dt><tt><i>mps2eps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mps2eps.zip">support/mps2eps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mps2eps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mps2eps/">browse</a>)
+<dt><tt><i>mpsproof.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/metapost/contrib/misc/mpsproof.tex">graphics/metapost/contrib/misc/mpsproof.tex</a>
+<dt><tt><i>mptopdf</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.zip">macros/pdftex/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/pdftex/graphics/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html
new file mode 100644
index 00000000000..c6ab8fb6c7f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label msxy</title>
+</head><body>
+<h3>Where are the <code>msx</code> and <code>msy</code> fonts?</h3>
+<p/>The <i>msx</i> and <i>msy</i> 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 &lsquo;old&rsquo; Metafont, which wasn&rsquo;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 AMS has
+now redesigned the fonts, using the current version of Metafont, and the
+new versions are called the <i>msa</i> and <i>msb</i>
+families.
+<p/>Nevertheless, <i>msx</i> and <i>msy</i> continue to turn up to
+plague us.  There are, of course, still sites that haven&rsquo;t got around
+to upgrading; but, even if everyone upgraded, there would still be the
+problem of old documents that specify them.
+<p/>If you have a <code>.tex</code> source that requests <i>msx</i> and
+<i>msy</i>, the best technique is to edit it so that it requests
+<i>msa</i> and <i>msb</i> (you only need to change the single
+letter in the font names).
+<p/>If you have a DVI file that requests the fonts, there is a package
+of <a href="FAQ-virtualfonts.html">virtual fonts</a> to map the old to the new series.
+<dl>
+<dt><tt><i>msa and msb fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.zip">fonts/amsfonts/sources/symbols</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/symbols/">browse</a>)
+<dt><tt><i>virtual font set</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/vf-files/msx2msa.zip">fonts/vf-files/msx2msa</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/vf-files/msx2msa.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/vf-files/msx2msa/">browse</a>)
+</dl>
+<p/>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html
new file mode 100644
index 00000000000..1105a43ecc9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html
@@ -0,0 +1,144 @@
+<head>
+<title>UK TeX FAQ -- question label multbib</title>
+</head><body>
+<h3>Multiple bibliographies?</h3>
+<p/>If you&rsquo;re thinking of multiple bibliographies tied to some part of
+your document (such as the chapters within the document), please see
+<a href="FAQ-chapbib.html">bibliographies per chapter</a>.
+<p/>For more than one bibliography, there are three options.
+<p/>The <i>multibbl</i> package offers a very simple interface: you use
+a command <code>\</code><code>newbibliography</code> to define a bibliography &ldquo;tag&rdquo;.  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 <code>\</code><code>bibliography</code> command itself also takes
+a further extra argument that says what title to use for the resulting
+section or chapter (i.e., it patches
+
+<a href="FAQ-fixnam.html"><code>\</code><code>refname</code> and <code>\</code><code>bibname</code></a> in a
+<i>babel</i>-safe way).  So one might write:
+
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+(Note that the optional argument of <code>\</code><code>cite</code> appears <em>before</em> the
+new tag argument, and that the <code>\</code><code>bibliography</code> commands may list
+more than one <code>.bib</code> file &mdash; indeed all <code>\</code><code>bibliography</code> commands
+may list the same set of files.)
+<p/>The <code>\</code><code>bibliography</code> data goes into files whose names are
+&lt;<i>tag-name</i>&gt;<em>.aux</em>, so you will need to run
+<blockquote>
+<pre>
+bibtex bk
+bibtex art
+</pre>
+</blockquote><p>
+after the first run of LaTeX, to get the citations in the correct
+place.
+<p/>The <i>multibib</i> package allows you to define a series of
+&ldquo;additional topics&rdquo;, each of which comes with its own series of
+bibliography commands.  So one might write:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+Again, as for <i>multibbl</i>, any <code>\</code><code>bibliography...</code> command may
+scan any list of <code>.bib</code> files.
+<p/>BibTeX processing with <i>multibib</i> is much like that with
+<i>multibbl</i>; with the above example, one needs:
+<blockquote>
+<pre>
+bibtex bk
+bibtex art
+</pre>
+</blockquote><p>
+Note that, unlike <i>multibbl</i>, <i>multibib</i> allows a
+simple, unmodified bibliography (as well as the &ldquo;topic&rdquo; ones).  
+<p/>The <i>bibtopic</i> package allows you separately to cite several
+different bibliographies.  At the appropriate place in your document,
+you put a sequence of <code>btSect</code> environments (each of which
+specifies a bibliography database to scan) to typeset the separate
+bibliographies.  Thus, one might have a file <i>diss.tex</i> containing:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+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 <code>btSect</code> environment.
+<p/>Processing with BibTeX, in this case, uses <code>.aux</code> files whose names
+are derived from the name of the base document.  So in this example
+you need to say:
+<blockquote>
+<pre>
+bibtex diss1
+bibtex diss2
+</pre>
+</blockquote><p>
+<p/>There is also a command <code>\</code><code>btPrintNotCited</code>, which gives the rest of
+the content of the database (if nothing has been cited from the
+database, this is equivalent to LaTeX standard <code>\</code><code>nocite{*}</code>).
+<p/>However, the <em>real</em> difference from <i>multibbl</i> and
+<i>multibib</i> is that selection of what appears in each
+bibliography section is determined in <i>bibtopic</i> by what&rsquo;s in
+the <code>.bib</code> files.
+<p/>An entirely different approach is taken by the <i>splitbib</i>
+package.  You provide a <code>category</code> environment, in the
+preamble of your document, for each category you want a separate
+citation list for.  In each environment, you list the <code>\</code><code>cite</code> keys
+that you want listed in each category.  The <code>\</code><code>bibliography</code> command
+(or, more precisely, the <code>thebibliography</code> environment it
+uses) will sort the keys as requested.  (Keys not mentioned in a
+<code>category</code> appear in a &ldquo;misc&rdquo; category created in the
+sorting process.)  A code example appears in the package documentation
+(a PDF file in the CTAN directory,
+  which you can browse to, from the link, below).
+
+<dl>
+<dt><tt><i>bibtopic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibtopic.zip">macros/latex/contrib/bibtopic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibtopic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bibtopic/">browse</a>)
+<dt><tt><i>multibbl.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibbl.zip">macros/latex/contrib/multibbl</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibbl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multibbl/">browse</a>)
+<dt><tt><i>multibib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibib.zip">macros/latex/contrib/multibib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multibib/">browse</a>)
+<dt><tt><i>splitbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitbib.zip">macros/latex/contrib/splitbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/splitbib/">browse</a>)
+</dl>
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html
new file mode 100644
index 00000000000..0d2441aa7df
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label multfoot</title>
+</head><body>
+<h3>More than one sequence of footnotes</h3>
+<p/>The need for more than one series of footnotes is common in critical
+editions (and other literary criticism), but occasionally arises in
+other areas.
+<p/>Of course, the canonical critical edition package, <i>edmac</i>,
+offers the facility, as does its LaTeX port, the <i>ledmac</i>
+package.
+<p/>Multiple ranges of footnotes are offered to LaTeX users by the
+<i>manyfoot</i> package.  The package provides a fair array of
+presentation options, as well.  Another critical edition
+<i>ednotes</i> package is built upon a basis that includes
+<i>manyfoot</i>, as its mechanism for multiple sets of footnotes.
+<p/>The <i>bigfoot</i> package also uses <i>manyfoot</i> as part of
+its highly sophisticated structure of footnote facilities, which was
+also designed to support typesetting critical editions.
+<dl>
+<dt><tt><i>bigfoot</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>)
+<dt><tt><i>edmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.zip">macros/plain/contrib/edmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/edmac/">browse</a>)
+<dt><tt><i>ednotes</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ednotes.zip">macros/latex/contrib/ednotes</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ednotes.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ednotes/">browse</a>)
+<dt><tt><i>ledmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse</a>)
+<dt><tt><i>manyfoot.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ncctools.zip">macros/latex/contrib/ncctools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ncctools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools/">browse</a>)
+  bundle
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html
new file mode 100644
index 00000000000..f5ee627147b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label multidoc</title>
+</head><body>
+<h3>A &lsquo;report&rsquo; from lots of &lsquo;article&rsquo;s</h3>
+<p/>This is a requirement, for example, if one is preparing the
+proceedings of a conference whose papers were submitted in LaTeX.
+<p/>The nearest things to canned solutions are Peter Wilson&rsquo;s
+<i>combine</i> and Federico Garcia&rsquo;s <i>subfiles</i> classes.
+<p/><i>Combine</i> defines the means to &lsquo;<code>\</code><code>import</code>&rsquo; 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.  An
+auxiliary package, <i>combinet</i>, allows use of the <code>\</code><code>title</code>s
+and <code>\</code><code>author</code>s (etc.) of the <code>\</code><code>import</code>ed documents to appear in
+the global table of contents.
+<p/><i>Subfiles</i> is used in the component files of a multi-file
+project, and the corresponding <i>subfiles</i> is used in the
+master file; 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.
+<p/>A more &lsquo;raw&rsquo; toolkit is offered by Matt Swift&rsquo;s <i>includex</i> and
+<i>newclude</i> packages, both part of the <i>frankenstein</i>
+bundle.  Note that Matt believes <i>includex</i> is obsolete
+(though it continues to work for this author); furthermore, its
+replacement, <i>newclude</i> remains &ldquo;in development&rdquo;, as it has
+been since 1999.
+<p/>Both <i>includex</i> and <i>newclude</i> enable you to
+&lsquo;<code>\</code><code>includedoc</code>&rsquo; complete articles (in the way that you
+&lsquo;<code>\</code><code>include</code>&rsquo; chapter files in an ordinary report).  The preamble
+(everything up to <code>\</code><code>begin{document}</code>), and everything after
+<code>\</code><code>end{document}</code>, is ignored by both packages.  Thus the
+packages don&rsquo;t &ldquo;do the whole job&rdquo; 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 <i>moredefs</i>, which is also part of the bundle.)
+<p/>A completely different approach is to use the <i>pdfpages</i>
+package, and to include articles submitted in PDF format into a
+a PDF document produced by PDFLaTeX.  The package
+defines an <code>\</code><code>includepdf</code> command, which takes arguments similar to
+those of the <code>\</code><code>includegraphics</code> 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.
+<dl>
+<dt><tt><i>combine.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse</a>)
+<dt><tt><i>combinet.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse</a>)
+<dt><tt><i>includex.sty</i></tt><dd>Distributed in the &ldquo;unsupported&rdquo; part of
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>)
+<dt><tt><i>moredefs.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>)
+<dt><tt><i>newclude.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>)
+<dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>)
+<dt><tt><i>subfiles.cls, etc.</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.zip">macros/latex/contrib/subfiles</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/subfiles/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html
new file mode 100644
index 00000000000..8dad6c9943a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html
@@ -0,0 +1,126 @@
+<head>
+<title>UK TeX FAQ -- question label multind</title>
+</head><body>
+<h3>Multiple indexes</h3>
+<p/>LaTeX&rsquo;s standard indexing capabilities (those provided by the
+<i>makeidx</i> package) only provide for one index in your
+document; even quite modest documents can be improved by indexes for
+separate topics.
+<p/>The <i>multind</i> package provides simple and straightforward
+multiple indexing.  You tag each <code>\</code><code>makeindex</code>, <code>\</code><code>index</code> and
+<code>\</code><code>printindex</code> command with a file name, and indexing commands are
+written to (or read from) the name with the appropriate (<code>.idx</code> or
+<code>.ind</code>) extension appended.  The <code>\</code><code>printindex</code> command is modified
+from the LaTeX standard so that it doesn&rsquo;t create its own chapter
+or section heading; you therefore decide what names (or sectioning
+level, even) to use for the indexes, and
+<a href="FAQ-fixnam.html"><code>\</code><code>indexname</code></a> is completely ignored.
+<p/>To create a &ldquo;general&rdquo; and an &ldquo;authors&rdquo; index, one might write:
+<blockquote>
+<pre>
+\usepackage{multind}
+\makeindex{general}
+\makeindex{authors}
+...
+\index{authors}{Another Idiot}
+...
+\index{general}{FAQs}
+...
+\printindex{general}{General index}
+\printindex{authors}{Author index}
+</pre>
+</blockquote><p>
+To complete the job, run LaTeX on your file enough times that
+labels, etc., are stable, and then execute the commands
+<blockquote>
+<pre>
+makeindex general
+makeindex authors
+</pre>
+</blockquote><p>
+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&rsquo;re processing, at all.  (There&rsquo;s no documentation that comes
+with the package: what you see above is as good as you will
+get...)
+<p/>The <i>index</i> package provides a comprehensive set of indexing
+facilities, including a <code>\</code><code>newindex</code> command that allows the
+definition of new styles of index.  <code>\</code><code>newindex</code> takes a &lsquo;tag&rsquo; (for
+use in indexing commands), replacements for the <code>.idx</code> and
+<code>.ind</code> file extensions, and a title for the index when it&rsquo;s
+finally printed; it can also change the item that&rsquo;s being indexed
+against (for example, one might have an index of artists referenced by
+the figure number where their work is shown).
+<p/>Using <i>index</i>, to create an author index together with a
+&ldquo;normal&rdquo; index, one would start with preamble commands:
+<blockquote>
+<pre>
+\usepackage{index}
+\makeindex
+\newindex{aut}{adx}{and}{Name Index}
+</pre>
+</blockquote><p>
+which load the package, define a &ldquo;main&rdquo; (original-style) index, and
+then define an author index.  Then, in the body of the document, we
+might find commands like:
+<blockquote>
+<pre>
+\index[aut]{Another Idiot}
+...
+\index{FAQs}
+</pre>
+</blockquote><p>
+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:
+<blockquote>
+<pre>
+\printindex
+\printindex[aut]
+</pre>
+</blockquote><p>
+Which will print the main index and then the author index.  Supposing
+this lot to be in <i>myfile.tex</i>, 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&rsquo;re using):
+<blockquote>
+<pre>
+makeindex myfile
+makeindex myfile.adx -o myfile.and
+</pre>
+</blockquote><p>
+and rerun LaTeX.  The <i>makeindex</i> commands process
+<i>myfile.idx</i> to <i>myfile.ind</i> (the default action), and then
+<i>myfile.adx</i> to <i>myfile.and</i>, the two files needed as input
+by the two <code>\</code><code>printindex</code> commands in <i>myfile.tex</i>.
+<p/>The <i>splitidx</i> package can operate in the same way as the
+others: load the package with the <code>split</code> option, and
+declare each index with a <code>\</code><code>newindex</code> command:
+<blockquote>
+  <code>\</code><code>newindex[&lt;<i>index name</i>&gt;]{&lt;<i>shortcut</i>&gt;}</code>
+</blockquote><p>
+and <i>splitidx</i> will generate a file
+<code>\</code><code>jobname</code><code>.&lt;<i>shortcut</i>&gt;</code> to receive index entries
+generated by commands like <code>\</code><code>sindex[&lt;<i>shortcut</i>&gt;]{&lt;<i>item</i>&gt;}</code>.
+As with the other packages, this method is limited by TeX&rsquo;s total
+number of output files.  However, <i>splitindex</i> also comes with
+a small executable <i>splitindex</i> (available for a variety of
+operating systems); if you use this auxiliary program (and don&rsquo;t use
+<code>split</code>), there&rsquo;s no limit to the number of indexes.  Apart
+from this trick, <i>splitidx</i> supports the same sorts of things
+as does <i>index</i>.  An example of use appears in
+the documentation.
+<p/>The <i>memoir</i> 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 <i>makeindex</i>).
+<dl>
+<dt><tt><i>index.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/index.zip">macros/latex/contrib/index</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/index.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/index/">browse</a>)
+<dt><tt><i>makeidx.sty</i></tt><dd>Part of the LaTeX distribution
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>multind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/misc/multind.sty">macros/latex209/contrib/misc/multind.sty</a>
+<dt><tt><i>splitidx.sty and splitindex</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitindex.zip">macros/latex/contrib/splitindex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/splitindex/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html
new file mode 100644
index 00000000000..4c651bfec35
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html
@@ -0,0 +1,98 @@
+<head>
+<title>UK TeX FAQ -- question label multirow</title>
+</head><body>
+<h3>Merging cells in a column of a table</h3>
+<p/>It&rsquo;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 
+<a href="FAQ-slashbox.html">diagonal separation in corner cells</a>, but that
+technique rather strictly limits what can be used as the content of
+the cell.
+<p/>The <i>multirow</i> package enables you to construct such multi-row
+cells, in a very simple manner.  For the simplest possible use, one
+might write:
+<blockquote>
+<pre>
+\begin{tabular}{|c|c|}
+\hline
+\multirow{4}{*}{Common g text} 
+      & Column g2a\\
+      & Column g2b \\
+      & Column g2c \\
+      & Column g2d \\
+\hline
+\end{tabular}
+</pre>
+</blockquote><p>
+and <i>multirow</i> will position &ldquo;Common g text&rdquo; at the vertical
+centre of the space defined by the other rows.  Note that the rows
+that don&rsquo;t contain the &ldquo;multi-row&rdquo; specification must have empty
+cells where the multi-row is going to appear.
+<p/>The &ldquo;<code>*</code>&rdquo; may be replaced by a column width specification.  In this
+case, the argument may contain forced line-breaks:
+<blockquote>
+<pre>
+\begin{tabular}{|c|c|}
+\hline
+\multirow{4}{25mm}{Common\\g text} 
+      & Column g2a\\
+      & Column g2b \\
+      & Column g2c \\
+      & Column g2d \\
+\hline
+\end{tabular}
+</pre>
+</blockquote><p>
+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 <code>*</code>-declared <code>\</code><code>multirow</code>.
+<p/>The <code>\</code><code>multirow</code> command may also used to write labels vertically
+down one or other side of a table (with the help of the
+<i>graphics</i> or <i>graphicx</i> package, which provide the
+<code>\</code><code>rotatebox</code> command):
+<blockquote>
+<pre>
+\begin{tabular}{|l|l|}
+\hline
+\multirow{4}{*}{\rotatebox{90}{hi there}}
+      & Column g2a\\
+      & Column g2b \\
+      & Column g2c \\
+      & Column g2d \\
+\hline
+\end{tabular}
+</pre>
+</blockquote><p>
+(which gives text going upwards; use angle <code>-90</code> for text going
+downwards, of course).
+<p/>To make a <code>\</code><code>multicolumn</code> multi-row &ldquo;cell&rdquo; in a table, you have to
+enclose a <code>\</code><code>multirow</code> inside a <code>\</code><code>multicolumn</code> &mdash; the other way
+around does not work, so:
+<blockquote>
+<pre>
+\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}
+</pre>
+
+</blockquote><p>
+<i>Multirow</i> is set up to interact with the <i>bigstrut</i>
+package (which is also discussed in the answer to 
+<a href="FAQ-struttab.html">spacing lines in tables</a>).  You use an
+optional argument to the <code>\</code><code>multirow</code> command to say how many of the
+rows in the multi-row have been opened up with <code>\</code><code>bigstrut</code>.
+<p/>The documentation of both <i>multirow</i> and <i>bigstrut</i> is
+to be found, as comments, in the package files themselves.
+<dl>
+<dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>)
+<dt><tt><i>multirow.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html
new file mode 100644
index 00000000000..5b29906117c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label music</title>
+</head><body>
+<h3>Typesetting music in TeX</h3>
+<p/>In the early days, a simple music package called MuTeX was
+written by Angelika Schofer and Andrea Steinbach, which demonstrated
+that music typesetting was possible; the package was very limited, and is
+hardly ever used nowadays.  Daniel Taupin took up the baton, and
+developed MusicTeX, which allows the typesetting of polyphonic and
+other multiple-stave music; MusicTeX remains available, but is most
+definitely no longer recommended.
+<p/>MusicTeX has been superseded by its successor MusiXTeX, which is
+a three-pass system (with a processor program that computes values for
+the element spacing in the music), and achieves finer control than is
+possible in the unmodified TeX-based mechanism that MusicTeX
+uses.  Daniel Taupin&rsquo;s is the only version of MusiXTeX currently
+being developed (the original author, Andreas Egler, had an
+alternative version, but he is now working on a different package
+altogether).
+<p/>Input to MusixTeX is extremely tricky stuff, and Don Simons&rsquo;
+preprocessor <i>pmx</i> is the preferred method of creating input
+for Taupin&rsquo;s version.  <i>Pmx</i> greatly eases use of
+MusixTeX, but it doesn&rsquo;t support the full range of MusixTeX&rsquo;s
+facilities directly; however, it does allow in-line MusixTeX code
+in <i>pmx</i> sources.
+<p/>Dirk Laurie&rsquo;s <i>M-Tx</i> allows preparation of music with lyrics;
+it operates &ldquo;on top of&rdquo; <i>pmx</i>
+<p/>Another simple notation is supported by <i>abc2mtex</i>; this is a
+package designed to notate tunes stored in an ASCII format
+(<code>abc</code> notation). It was designed primarily for folk and traditional
+tunes of Western European origin (such as Irish, English and Scottish)
+which can be written on one stave in standard classical notation, and
+creates input intended for MusicTeX.  However, it should be
+extendable to many other types of music.
+<p/>Digital music fans can typeset notation for their efforts by using
+<i>midi2tex</i>, which translates MIDI data files into
+MusicTeX source code.
+<p/>There is a mailing list (<i>TeX-music@icking-music-archive.org</i>)
+for discussion of typesetting music in TeX; it mostly covers
+MusixTeX and related systems.  To subscribe, use
+<a href="http://icking-music-archive.org/mailman/listinfo/tex-music/">http://icking-music-archive.org/mailman/listinfo/tex-music/</a>
+<p/>An alternative (free) means of embedding music examples into (La)TeX
+documents is <a href="http://www.lilypond.org">Lilypond</a>.  Lilypond is
+(at heart) a batch music typesetting system with plain text input that
+does most of its work without TeX.  Lilypond&rsquo;s input syntax is far
+less cryptic than is MusixTeX&rsquo;s, and it handles much more stuff
+automatically, yielding the same or better quality with less effort.
+Lilypond can also produce basic MIDI output.
+<dl>
+<dt><tt><i>abc2mtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/abc2mtex.zip">support/abc2mtex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/abc2mtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/abc2mtex/">browse</a>)
+<dt><tt><i>M-Tx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mtx.zip">support/mtx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mtx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mtx/">browse</a>)
+<dt><tt><i>midi2tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/midi2tex.zip">support/midi2tex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/midi2tex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/midi2tex/">browse</a>)
+<dt><tt><i>musictex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musictex.zip">macros/musictex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musictex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musictex/">browse</a>)
+
+<dt><tt><i>musixtex (Taupin&rsquo;s version)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin/">browse</a>)
+<dt><tt><i>musixtex (Egler&rsquo;s version)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.zip">macros/musixtex/egler</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler/">browse</a>)
+<dt><tt><i>mutex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/mtex.zip">macros/mtex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/mtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/mtex/">browse</a>)
+<dt><tt><i>pmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pmx.zip">support/pmx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pmx/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html
new file mode 100644
index 00000000000..cc1f61d9071
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html
@@ -0,0 +1,66 @@
+<head>
+<title>UK TeX FAQ -- question label nameref</title>
+</head><body>
+<h3>Referring to things by their name</h3>
+<p/>LaTeX&rsquo;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 <em>name</em> of things
+we&rsquo;ve labelled.  The two packages available extend the LaTeX
+sectioning commands to provide reference by the name of the section.
+<p/>The <i>titleref</i> package is a simple extension which provides
+the command <code>\</code><code>titleref</code>; it is a stand-alone package &mdash; don&rsquo;t use it
+in a document in which you also need to use <i>hyperref</i>.
+<p/>The <i>byname</i> package is part of the <i>smartref</i> bundle
+and works well with <i>smartref</i>, and works (to an extent) with
+<i>hyperref</i>, but the links it defines are not hyperlinks.
+<p/>The <i>memoir</i> class incorporates the functionality of
+<i>titleref</i>, but doesn&rsquo;t work with <i>byname</i> (though a
+search of <i>comp.text.tex</i> on <a href="groups.google.com">groups.google.com</a> will
+find a patch to <i>byname</i> to remedy the problem).
+<p/>The <i>hyperref</i> bundle includes a package <i>nameref</i>,
+which will work standing alone (i.e., without <i>hyperref</i>: of
+course, in this mode its references are not hyperlinked).  If you load
+<i>hyperref</i> itself, <i>nameref</i> is automatically loaded.
+<i>Memoir</i> requires the <i>memhfixc</i> when running with
+<i>hyperref</i>; following the sequence:
+<blockquote>
+<pre>
+\documentclass[...]{memoir}
+...
+\usepackage[...]{hyperref}
+\usepackage{memhfixc}
+</pre>
+</blockquote><p>
+<i>nameref</i> commands may be used in a <i>memoir</i> document.
+<p/><i>Zref</i> defines a proposed replacement for all of the LaTeX
+reference mechanisms, and among other things provides
+name-referencing mechanisms:
+<blockquote>
+<pre>
+\usepackage[user,titleref]{zref}
+...
+\section{hello}\zlabel{sec:one}
+The section name is: \ztitleref{sec:one}.
+</pre>
+</blockquote><p>
+(One might hope that something of this sort would be the &ldquo;way of the
+future&rdquo;, but things move slowly in the LaTeX world: don&rsquo;t hold
+your breath.) 
+<p/>Each of <i>titleref</i>, <i>byname</i> and <i>nameref</i>
+defines a reference command with the same name as the package:
+<code>\</code><code>titleref</code>, <code>\</code><code>byname</code> and <code>\</code><code>nameref</code>. The <i>nameref</i>
+package also defines a command <code>\</code><code>byshortnameref</code>, which uses the
+optional &lsquo;short&rsquo; title argument to the chapter and section commands.
+(Although it comes from the same author, <i>zref</i> <em>doesn&rsquo;t</em>
+define a short-name variant.)
+<dl>
+<dt><tt><i>byname.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse</a>)
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>nameref.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>smartref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse</a>)
+<dt><tt><i>titleref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/titleref.sty">macros/latex/contrib/misc/titleref.sty</a>
+<dt><tt><i>zref.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html
new file mode 100644
index 00000000000..00b8df11947
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label newans</title>
+</head><body>
+<h3>Submitting new material for the FAQ</h3>
+<p/>The 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&rsquo;ve got wrong, and suggestions for improvements, particularly
+covering areas we&rsquo;ve missed, are always needed: mail anything you have
+to the
+  <a href="mailto:faq-devel@tex.ac.uk">maintainers</a>
+
+<p/>If you have actual material to submit, your contribution is more than
+ever welcome.  Submission in plain text is entirely acceptable, but
+if you&rsquo;re really willing, you may feel free to mark up your submission
+in the form needed for the FAQ itself.  The markup is a
+strongly-constrained version of LaTeX &mdash; the constraints come from
+the need to translate the marked-up text to HTML on the fly
+(and hence pretty efficiently).  There is a file <i>markup-syntax</i>
+in the FAQ distribution that describes the structure of the
+markup, but there&rsquo;s no real substitute for reading at least some of
+the source (<i>faqbody.tex</i>) of the FAQ itself.  If you
+understand <i>Perl</i>, you may also care to look at the
+translation code in <i>texfaq2file</i> and <i>sanitize.pl</i> in the
+distribution: this isn&rsquo;t the code actually used on the Web site, but
+it&rsquo;s a close relation and is kept
+up to date for development purposes.
+<dl>
+<dt><tt><i>FAQ distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html
new file mode 100644
index 00000000000..70ce959aeee
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label newfont*</title>
+</head><body>
+<h3>What&rsquo;s wrong with <code>\</code><code>newfont</code>?</h3>
+<p/>If all else fails, you <em>can</em> specify a font using the LaTeX
+<code>\</code><code>newfont</code> command.  The font so specified doesn&rsquo;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 <code>\</code><code>font</code> primitive, and doesn&rsquo;t really fit with
+LaTeX at all.  A simple, but really rather funny, example of the
+problems it poses, may be seen in:
+<blockquote>
+<pre>
+\documentclass[10pt]{article}
+\begin{document}
+\newfont{\myfont}{cmr17 scaled 2000}
+\myfont
+\LaTeX
+\end{document}
+</pre>
+</blockquote><p>
+(the reader is encouraged to try this).  The &ldquo;A&rdquo; of <code>\</code><code>LaTeX</code> pretty
+much disappears: LaTeX chooses the size on the &ldquo;A&rdquo; according to
+<em>its</em> idea of the font size (10pt), but positions it according to
+the dimensions of &ldquo;<code>\</code><code>myfont</code>&rdquo;, which is more than three times
+that size.
+<p/>Another &ldquo;<code>\</code><code>myfont</code>&rdquo; example arises from an entirely different
+source.  The mini-document:
+<blockquote>
+<pre>
+\documentclass{article}
+\begin{document}
+\newfont{\myfont}{ecrm1000}
+{\myfont voil\`a}
+\end{document}
+</pre>
+</blockquote><p>
+gives you &ldquo;German low double quotes&rdquo; (under the &ldquo;a&rdquo;) in place of
+the grave accent.  This happens because <i>ecrm1000</i> is in a
+different <a href="FAQ-whatenc.html">font encoding</a> than LaTeX is
+expecting &mdash; if you use the LaTeX <i>fontenc</i> package to
+select the EC fonts, all these tiresome encoding issues are
+solved for you, behind the scenes.
+<p/>There does however remain a circumstance when you will be tempted to
+use <code>\</code><code>newfont</code> &mdash; viz., to get a font size that doesn&rsquo;t fall into
+the Knuth standard set of sizes: LaTeX (by default) won&rsquo;t allow you
+to use such a size.  Don&rsquo;t despair: see the answer 
+&ldquo;<a href="FAQ-fontsize.html">arbitrary font sizes</a>&rdquo;.
+<p/>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html
new file mode 100644
index 00000000000..3e6065fe3b8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html
@@ -0,0 +1,55 @@
+<head>
+<title>UK TeX FAQ -- question label newfunction</title>
+</head><body>
+<h3>Defining a new log-like function in LaTeX</h3>
+<p/>Use the <code>\</code><code>mathop</code> command, as in:
+<blockquote>
+<pre>
+\newcommand{\diag}{\mathop{\mathrm{diag}}}
+</pre>
+</blockquote><p>
+<p/>Subscripts and superscripts on <code>\</code><code>diag</code> will be placed below and
+above the function name, as they are on
+<code>\</code><code>lim</code>.  If you want your subscripts and superscripts always placed
+to the right, do:
+<blockquote>
+
+<pre>
+\newcommand{\diag}{\mathop{\mathrm{diag}}\nolimits}
+</pre>
+</blockquote><p>
+<p/>AMSLaTeX (in its <i>amsopn</i> package, which is automatically
+loaded by <i>amsmath</i>) provides a command
+<code>\</code><code>DeclareMathOperator</code> that takes does the same job as the first
+definition above.  To create our original <code>\</code><code>diag</code> command, one would
+say:
+<blockquote>
+<pre>
+\DeclareMathOperator{\diag}{diag}
+</pre>
+</blockquote><p>
+<code>\</code><code>DeclareMathOperator*</code> declares the operator always to have its
+sub- and superscripts in the 
+&ldquo;<a href="FAQ-limits.html"><code>\</code><code>limits</code> position</a>&rdquo;.
+<p/>The <i>amsopn</i> command <code>\</code><code>operatorname</code> allows you to
+introduce <em>ad hoc</em> operators into your mathematics, so
+<blockquote>
+  <code>\</code><code>[</code> <code>\</code><code>operatorname{foo}</code><code>(bar)</code> <code>\</code><code>]</code>
+</blockquote><p>
+typesets the same as
+<blockquote>
+<pre>
+\DeclareMathOperator{\foo}{foo}
+...
+\[ \foo(bar) \]
+</pre>
+</blockquote><p>
+As with <code>\</code><code>DeclareMathOperator</code> there&rsquo;s a starred version
+<code>\</code><code>operatorname*</code> for sub- and superscripts in the limits position.
+<p/>(It should be noted that &ldquo;log-like&rdquo; was reportedly a <em>joke</em> on
+Lamport&rsquo;s part; it is of course clear what was meant.)
+<dl>
+<dt><tt><i>amsopn.sty</i></tt><dd>In the AMSLaTeX distribution <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html
new file mode 100644
index 00000000000..035348f0359
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html
@@ -0,0 +1,101 @@
+<head>
+<title>UK TeX FAQ -- question label newlang</title>
+</head><body>
+<h3>Using a new language with Babel</h3>
+<p/><i>Babel</i> 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
+<pre>
+  \usepackage[catalan]{babel}
+</pre>
+provokes the warning message
+<pre>
+Package babel Warning: No hyphenation patterns were loaded for
+(babel)                the language `Catalan'
+(babel)                I will use the patterns loaded for \language=0 instead.
+</pre>
+
+<p/>The problem is that your TeX system doesn&rsquo;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
+<i>language.dat</i> (which is part of the Babel installation); it will
+contain a line
+<pre>
+%catalan         cahyphen.tex
+</pre>
+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.
+<p/>Unfortunately, in many Babel distributions, the line just isn&rsquo;t
+right &mdash; you need to check the name of the file containing the
+patterns you&rsquo;re going to use.  As you can see, in the author&rsquo;s system,
+the name is supposed to be <i>cahyphen.tex</i>; however the file
+actually present on the system is <i>cahyph.tex</i> &mdash; 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 CTAN; if you have to retrieve
+a new file, ensure that it&rsquo;s correctly installed, for which see
+<a href="FAQ-inst-wlcf.html">installing a new package</a>).
+<p/>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).
+<dl>
+<dt>teTeX<dd>It&rsquo;s possible to do the whole operation in one go, by
+  using the <i>texconfig</i> command:
+<pre>
+texconfig hyphen latex
+</pre>
+  which first enters an editor for you to edit <i>language.dat</i>,
+  and then regenerates the format you specify (<i>latex</i> in
+  this case).
+<p/>  Otherwise, to regenerate all formats, do: <br>
+  <code>fmtutil --all</code>
+<p/>  If you&rsquo;re willing to think through what you&rsquo;re doing (this is
+  <em>not</em> for the faint-hearted), you can select a sequence of
+  formats and for each one, run: <br>
+  <code>fmtutil --byfmt &lt;<i>formatname</i>&gt;</code><br>
+  where <em><code>formatname</em></code> is something like &lsquo;<code>latex</code>&rsquo;,
+  or: <br>
+  <code>fmtutil --byhyphen &lt;<i>hyphenfile</i>&gt;</code><br>
+  where <em><code>hyphenfile</em></code> is the file specifying hyphenation
+  to the format &mdash; usually <code>language.dat</code>
+<dt>MiKTeX<dd> On a <i>MiKTeX</i> distribution earlier than v2.0, do: <br>
+  <code>Start</code>-&gt; 
+  <code>Programs</code>-&gt; 
+  <code>MiKTeX</code>-&gt; 
+  <code>Maintenance</code>-&gt; 
+  <code>Create all format files</code>
+
+<p/>  or get a DOS window and run:<br>
+  <code>initexmf --dump</code>
+<p/>  On a <i>MiKTeX</i> distribution v2.0 or later, the whole
+  procedure can be done via the GUI.  To select the new
+  language, do:<br>
+  <code>Start</code>-&gt; 
+  <code>Programs</code>-&gt; 
+  <code>MiKTeX 2</code>-&gt; 
+  <code>MiKTeX Options</code>, and select the <code>Languages</code> tab.
+  Select your language from the list, press the <code>Apply</code> button,
+  and then the <code>OK</code> button.  Then select the <code>General</code>
+  tab and press the <code>Update Now</code> button.
+<p/>  Otherwise, edit the <i>language.dat</i> file (as outlined above),
+  and then run:<br>
+  <code>initexmf --dump</code><br>
+  just as for a pre-v2.0 system.
+</dl>
+<p/><b><em>Caveat</em>:</b> It is (just) possible that
+your TeX system may run out of &ldquo;pattern memory&rdquo; 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 <em>do</em> find you&rsquo;ve run out of memory,
+it may be worth scanning the list of languages in your
+<i>language.dat</i> to see whether any could reasonably be removed.
+<dl>
+<dt><tt><i>babel</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.zip">macros/latex/required/babel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel/">browse</a>)
+<dt><tt><i>hyphenation patterns</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/language/hyphenation.zip">language/hyphenation</a> (<a href="ftp://cam.ctan.org/tex-archive/language/hyphenation.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/language/hyphenation/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html
new file mode 100644
index 00000000000..ea8b6608c1d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html
@@ -0,0 +1,58 @@
+<head>
+<title>UK TeX FAQ -- question label newlineargs</title>
+</head><body>
+<h3>Start of line goes awry</h3>
+<!-- asterisk square bracket start line -->
+<p/>This answer concerns two sorts of problems: errors of the form
+<blockquote>
+<pre>
+! Missing number, treated as zero.
+&lt;to be read again&gt; 
+                   g
+&lt;*&gt; [grump]
+</pre>
+</blockquote><p>
+and those where a single asterisk at the start of a line mysteriously
+fails to appear in the output.
+<p/>Both problems arise because <code>\</code><code>\</code> takes optional arguments.  The
+command <code>\</code><code>\*</code> means &ldquo;break the line here, and inhibit page break
+following the line break&rdquo;; the command <code>\</code><code>\[</code>&lt;<i>dimen</i>&gt;<code>]</code>
+means &ldquo;break the line here and add &lt;<i>dimen</i>&gt; extra vertical space
+afterwards&rdquo;.
+<p/>So why does <code>\</code><code>\</code> get confused by these things at the start of a
+line?  It&rsquo;s looking for the first non-blank thing, and in the test it
+uses ignores the end of the line in your input text.
+<p/>The solution is to enclose the stuff at the start of the new line in
+braces:
+<blockquote>
+<pre>
+{\ttfamily
+  /* C-language comment\\
+  {[grump]} I don't like this format\\
+  {*}/
+}
+</pre>
+</blockquote><p>
+(The above text derives from an actual post to
+<i>comp.text.tex</i>; this particular bit of typesetting could
+plainly also be done using the <code>verbatim</code> environment.)
+<p/>The problem also appears in maths mode, in arrays and so on.  In this
+case, large-scale bracketing of things is <em>not</em> a good idea; the
+TeX primitive <code>\</code><code>relax</code> (which does nothing except to block
+searches of this nature) may be used.  From another
+<i>comp.text.tex</i> example:
+<blockquote>
+<pre>
+\begin{eqnarray}
+  [a] &=& b \\
+  \relax[a] &=& b
+\end{eqnarray}
+</pre>
+</blockquote><p>
+which is a usage this FAQ would not recommend, anyway: refer
+to the <a href="FAQ-eqnarray.html">reason not to use <code>eqnarray</code></a>.
+<p/>Note that the <i>amsmath</i> package modifies the behaviour of
+<code>\\</code> in maths.  With <i>amsmath</i>, the <code>eqnarray</code>
+example doesn&rsquo;t need any special measures.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html
new file mode 100644
index 00000000000..2970987925d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html
@@ -0,0 +1,24 @@
+<head>
+<title>UK TeX FAQ -- question label noans</title>
+</head><body>
+<h3>You don&rsquo;t understand the answer</h3>
+<p/>While the FAQ maintainers don&rsquo;t offer a &lsquo;help&rsquo; service, they&rsquo;re
+very keen that you understand the answers they&rsquo;ve already written.
+They&rsquo;re (almost) written &ldquo;in a vacuum&rdquo;, to provide something to
+cover a set of questions that have arisen; it&rsquo;s always possible that
+they&rsquo;re written in a way that a novice won&rsquo;t understand them.
+<p/>Which is where you can help the community.  Mail the 
+  <a href="mailto:faq-devel@tex.ac.uk">maintainers</a>
+
+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&rsquo;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.
+<p/>Note that the FAQ development email address is not for
+answering questions: it&rsquo;s for you to suggest which questions we should
+work on, or new questions we should answer in future editions.
+<p/>Those who simply ask questions at that address will be referred to
+<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a> or to <i>comp.text.tex</i>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html
new file mode 100644
index 00000000000..3e0337627c9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label nocite*</title>
+</head><body>
+<h3>Listing all your BibTeX entries</h3>
+<p/>LaTeX and BibTeX co-operate to offer special treatment of this
+requirement.  The command <code>\</code><code>nocite{*}</code> is specially treated,
+and causes BibTeX to generate bibliography entries for every entry
+in each <code>.bib</code> file listed in your <code>\</code><code>bibliography</code> statement, so
+that after a LaTeX&ndash;BibTeX&ndash;LaTeX sequence, you have a
+document with the whole thing listed.
+<p/>Note that LaTeX <em>doesn&rsquo;t</em> produce
+
+&ldquo;<code>Citation ... undefined</code>&rdquo; or
+&ldquo;<code>There were undefined references</code>&rdquo; warnings in respect of
+<code>\</code><code>nocite{*}</code>.  This isn&rsquo;t a problem if you&rsquo;re running
+LaTeX &ldquo;by hand&rdquo; (you <em>know</em> 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.
+<p/>A couple of packages are available, that aim to reduce the impact of
+<code>\</code><code>nocite{*}</code> of a large citation database.  <i>Biblist</i>
+was written for use under LaTeX 2.09, but seems to work well enough;
+<i>listbib</i> is more modern.  Both provide their own
+<code>.bst</code> 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.)
+<dl>
+<dt><tt><i>biblist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/biblist.zip">macros/latex209/contrib/biblist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/biblist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/biblist/">browse</a>)
+<dt><tt><i>listbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listbib.zip">macros/latex/contrib/listbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listbib/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html
new file mode 100644
index 00000000000..4c0b9128d29
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html
@@ -0,0 +1,29 @@
+<head>
+<title>UK TeX FAQ -- question label nodollar</title>
+</head><body>
+<h3>&ldquo;Missing <code>$</code> inserted&rdquo;</h3>
+<p/>There are certain things that <em>only</em> work in maths mode.  If your
+document is not in maths mode and you have an <code>_</code> or a <code>^</code> character,
+TeX (and by inheritance, LaTeX too) will say
+<pre>
+! Missing $ inserted
+</pre>
+as if you couldn&rsquo;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 <code>$</code> you &lsquo;forgot&rsquo;, so that
+the maths-only object will work; as often as not this will land you in
+further confusion.
+<p/>It&rsquo;s not just the single-character maths sub- and superscript
+operators: anything that&rsquo;s built in or declared as a maths operation,
+from the simplest lower-case <code>\</code><code>alpha</code> through the inscrutable
+<code>\</code><code>mathchoice</code> primitive, and beyond, will provoke the error if
+misused in text mode.
+<p/>LaTeX offers a command <code>\</code><code>ensuremath</code>, which will put you in maths
+mode for the execution of its argument, if necessary: so if you want
+an <code>\</code><code>alpha</code> in your running text, say
+<code>\</code><code>ensuremath{<code>\</code><code>alpha</code>}</code>; if the bit of running text somehow
+transmutes into a bit of mathematics, the <code>\</code><code>ensuremath</code> will become
+a no-op, so it&rsquo;s pretty much always safe.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html
new file mode 100644
index 00000000000..311acf2188a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label nofm</title>
+</head><body>
+<h3>Page numbering &ldquo;&lt;<i>n</i>&gt; of &lt;<i>m</i>&gt;&rdquo;</h3>
+
+<p/>Finding the page number of the last page of a document, from within
+the document, is somewhat tricky.  The <i>lastpage</i> package is
+therefore supplied to make life easy for us all; it defines a label
+<code>LastPage</code> whose number is <em>right</em> (after sufficiently many
+passes through LaTeX, of course).  The <i>memoir</i> class also
+defines a &ldquo;last page&rdquo; label.
+<p/>The documentation of the <i>fancyhdr</i> package spells out exactly
+how one might actually use this information to produce page numbering
+as suggested in the question.
+<dl>
+<dt><tt><i>fancyhdr documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>)
+<dt><tt><i>lastpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.zip">macros/latex/contrib/lastpage</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lastpage/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html
new file mode 100644
index 00000000000..793582fa4f6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label nohyph</title>
+</head><body>
+<h3>My words aren&rsquo;t being hyphenated</h3>
+<p/>Let&rsquo;s assume you&rsquo;ve selected the right TeX &lsquo;language&rsquo; &mdash; as
+explained in <a href="FAQ-hyphen.html">&ldquo;how hyphenation works&rdquo;</a>,
+you&rsquo;re not likely to get the correct results typesetting one language
+using the hyphenation rules of another.  (Select the proper language,
+using <i>babel</i> if you&rsquo;re a LaTeX user.  This may reveal that
+you need another set of hyphenation patterns; see
+
+<a href="FAQ-newlang.html">&ldquo;using a new language&rdquo;</a> for advice on how
+to install it.)
+<p/>So what else can go wrong?
+<ul>
+<li> Since TeX version 3.0, the limits on how near to either end
+  of a word hyphenation may take place have been programmable (see
+  <a href="FAQ-weirdhyphen.html">&ldquo;weird hyphenation&rdquo;</a>), and for some
+  reason the values in question may have been corrupted in some macros
+  you are using.  TeX won&rsquo;t hyphenate less than <code>\</code><code>lefthyphenmin</code>
+  characters after the start of a word, nor less than
+  <code>\</code><code>righthyphenmin</code> before the end of a word; thus it won&rsquo;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&rsquo;t
+  hyphenate a word shorter than 5 letters long, if it believes the
+  word to be English.
+<li> TeX won&rsquo;t hyphenate a word that&rsquo;s already been hyphenated.
+  For example, the (caricature) English surname Smyth-Postlethwaite
+  wouldn&rsquo;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 <code>\</code><code>hyph</code> command, defined
+<blockquote>
+<pre>
+\def\hyph{-\penalty0\hskip0pt\relax}
+</pre>
+</blockquote><p>
+  This is <em>not</em> the sort of thing this FAQ would
+  ordinarily recommend... The <i>hyphenat</i> package defines a
+  bundle of such commands (for introducing hyphenation points at
+  various punctuation characters).
+<li> There may be accents in the word.  The causes of and remedies
+  for this effect are discussed in
+  
+  <a href="FAQ-hyphenaccents.html">accents and hyphens</a>.
+<li> The hyphenation may simply not have been spotted; while TeX&rsquo;s
+  algorithm is good, it&rsquo;s not infallible, and it does miss perfectly
+  good hyphenations in some languages.  When this happens, you need to
+  give TeX <em>explicit</em> instructions on how to hyphenate.
+</ul>
+The <code>\</code><code>hyphenation</code> 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 &mdash; <code>\</code><code>hyphenation{ana-lysis pot-able}</code>; note that
+(as here, for analysis) you can use the command to overrule TeX&rsquo;s
+choice of hyphenation (ana-lysis is the British etymological
+hyphenation; some feel the American hyphenation feels
+&lsquo;unfortunate&rsquo;...).
+<dl>
+<dt><tt><i>hyphenat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html
new file mode 100644
index 00000000000..cd7e610c6c2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label noline</title>
+</head><body>
+<h3>No line here to end</h3>
+<p/>The error
+<blockquote>
+<pre>
+! LaTeX Error: There's no line here to end.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+</pre>
+
+</blockquote><p>
+comes in reaction to you giving LaTeX a <code>\</code><code>\</code> command at a time
+when it&rsquo;s not expecting it.  The commonest case is where you&rsquo;ve
+decided you want the label of a list item to be on a line of its own,
+so you&rsquo;ve written (for example):
+<blockquote>
+<pre>
+\begin{description}
+\item[Very long label] \\
+  Text...
+\end{description}
+</pre>
+</blockquote><p>
+<code>\</code><code>\</code> is actually a rather bad command to use in this case (even if
+it worked), since it would force the &lsquo;paragraph&rsquo; that&rsquo;s made up of the
+text of the item to terminate a line which has nothing on it but the
+label.  This would lead to an &ldquo;<code>Underfull \hbox</code>&rdquo; warning message
+(usually with &lsquo;infinite&rsquo; badness of 10000); while this message doesn&rsquo;t
+do any actual harm other than slowing down your LaTeX run, any
+message that doesn&rsquo;t convey any information distracts for no useful
+purpose.
+<p/>The proper solution to the problem is to write a new sort of
+<code>description</code> environment, that does just what you&rsquo;re after.  (The
+
+<a href="FAQ-books.html"><em>LaTeX Companion</em></a> offers a
+rather wide selection of variants of these things.)
+<p/>The quick-and-easy solution, which avoids the warning, is to write:
+<blockquote>
+<pre>
+\begin{description}
+\item[Very long label] \hspace*{\fill} \\
+  Text...
+\end{description}
+</pre>
+</blockquote><p>
+which fills out the under-full line before forcing its closure.  The
+<i>expdlist</i> package provides the same functionality with its
+<code>\</code><code>breaklabel</code> command, and <i>mdwlist</i> provides it via its
+<code>\</code><code>desclabelstyle</code> command.
+<p/>The other common occasion for the message is when you&rsquo;re using the
+<code>center</code> (or <code>flushleft</code> or <code>flushright</code>)
+environment, and have decided you need extra separation between lines
+in the environment:
+<blockquote>
+<pre>
+\begin{center}
+  First (heading) line\\
+  \\
+  body of the centred text...
+\end{center}
+</pre>
+</blockquote><p>
+The solution here is plain: use the <code>\\</code> command in the way it&rsquo;s
+supposed to be used, to provide more than just a single line break
+space.  <code>\\</code> takes an optional argument, which specifies
+how much extra space to add; the required effect in the text above can
+be had by saying:
+<blockquote>
+<pre>
+\begin{center}
+  First (heading) line\\[\baselineskip]
+  body of the centred text...
+\end{center}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>)
+<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+</dl>
+<p/>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html
new file mode 100644
index 00000000000..4c62ea60570
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html
@@ -0,0 +1,66 @@
+<head>
+<title>UK TeX FAQ -- question label nonfree</title>
+</head><body>
+<h3>What&rsquo;s the CTAN <code>nonfree</code> tree?</h3>
+<p/>When 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).
+<p/>With the advent of the TeX <em>distributions</em>, 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.
+<p/>The 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
+&ldquo;not free&rdquo;.  Thus was the <code>nonfree</code> tree born.
+<p/>From the start, the <code>nonfree</code> tree was controversial: the terms
+under which a package would be placed on the tree were hotly
+contested, and the CTAN team were only able slowly to populate
+the tree.  It is now obvious to the team that the project would never
+be completed.
+<p/>The 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&rsquo;s coverage of CTAN is good (and slowly improving),
+the general rule for distributors has become
+<blockquote>
+&ldquo;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&rsquo;t think of distributing it&rdquo;.
+</blockquote><p>
+<p/>(The catalogue only has a modest 
+<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of licences</a>, but it covers the set used
+by packages on CTAN, with a wild-card &ldquo;<code>other-free</code>&rdquo;
+which covers packages that the CTAN administrators believe to
+be free even though the authors haven&rsquo;t used a standard licence.)
+<p/>In the light of the above, the <code>nonfree</code> tree is being
+dismantled, and its contents moved to the main CTAN tree.  So
+the answer to the question is, now, &ldquo;the nonfree tree is a part of
+CTAN, and is now being merged with the main tree&rdquo;.
+<p/><p/>
+
+
+
+
+
+
+
+
+
+
+
+<p/>
+
+
+
+
+<p/>
+
+
+
+
+
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html
new file mode 100644
index 00000000000..aa63ddd54c5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label nonpdfsp</title>
+</head><body>
+<h3>Non-PDF special ignored!</h3>
+<p/>This is a PDFTeX error: PDFTeX is running in PDF output
+
+mode, and it has encountered a 
+<a href="FAQ-specials.html"><code>\</code><code>special</code></a> command.  PDFTeX is
+able to generate its own output, and in this mode of operation has no
+need of <code>\</code><code>special</code> commands (which allow the user to pass
+information to the driver being used to generate output).
+<p/>Why does this happen?  LaTeX users, nowadays, hardly ever use
+<code>\</code><code>special</code> commands on their own &mdash; they employ packages to do the
+job for them.  Some packages will generate <code>\</code><code>special</code> commands
+however they are invoked: <i>pstricks</i> is an example (it&rsquo;s very
+raison d&rsquo;&ecirc;tre is to emit PostScript code in a sequence of <code>\</code><code>special</code>
+commands).  <i>Pstricks</i> may be dealt with by other means (the
+<i>pdftricks</i> package offers a usable technique).
+<p/>More amenable to correction, but more confusing, are packages (such as
+<i>color</i>, <i>graphics</i> and <i>hyperref</i>) that
+specify a &ldquo;driver&rdquo;.  These packages have plug-in modules that
+determine what <code>\</code><code>special</code> (or other commands) are needed to generate
+any given effect: the <code>pdftex</code> driver for such packages knows not to
+generate <code>\</code><code>special</code> 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&rsquo;ve been using <i>dvips</i> (and specifying the <code>dvips</code> driver)
+or <i>dvipdfm</i> (for which you have to specify the driver), and
+decide to try PDFLaTeX, you <em>must</em> remove the <code>dvips</code> or
+<code>dvipdfm</code> driver specification from the package options, and let the
+system recognise which driver is needed.
+<dl>
+<dt><tt><i>pdftricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse</a>)
+<dt><tt><i>pstricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html
new file mode 100644
index 00000000000..74783f3351c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html
@@ -0,0 +1,48 @@
+<head>
+<title>UK TeX FAQ -- question label nonum</title>
+</head><body>
+<h3>&ldquo;Missing number, treated as zero&rdquo;</h3>
+<p/>In general, this means you&rsquo;ve tried to assign something to a count,
+dimension or skip register that isn&rsquo;t (in TeX&rsquo;s view of things) a
+number.  Usually the problem will become clear using the
+<a href="FAQ-erroradvice.html">ordinary techniques of examining errors</a>.
+<p/>Two LaTeX-specific errors are commonly aired on the newsgroups.
+<p/>The commonest arises from attempting to use an example from the
+<a href="FAQ-books.html"><em>The LaTeX Companion</em> (first edition)</a>, and is
+exemplified by the following error text:
+<pre>
+! Missing number, treated as zero.
+&lt;to be read again&gt; 
+                   \relax 
+l.21 \begin{Ventry}{Return values}
+</pre>
+The problem arises because, in its first edition, the
+<em>Companion</em>&rsquo;s examples always assumed that the <i>calc</i>
+package is loaded: this fact is mentioned in the book, but often not
+noticed.  The remedy is to load the <i>calc</i> package in any
+document using such examples from the <em>Companion</em>.  (The problem
+does not really arise with the second edition; copies of all the
+examples are available on the accompanying CDROM, or on
+CTAN.)
+<p/>The other problem, which is increasingly rare nowadays, arises from
+misconfiguration of a system that has been upgraded from LaTeX 2.09:
+the document uses the <i>times</i> package, and the error appears
+at <code>\</code><code>begin{document}</code>.  The file search paths are wrongly set
+up, and your <code>\</code><code>usepackage{times}</code> has picked up a LaTeX 2.09
+version of the package, which in its turn has invoked another which
+has no equivalent in LaTeX2e.  The obvious solution is to rewrite
+the paths so that LaTeX 2.09 packages are chosen only as a last resort
+so that the startlingly simple LaTeX2e <i>times</i> package will
+be picked up.  Better still is to replace the whole thing with
+something more modern still; current <i>psnfss</i> doesn&rsquo;t provide
+a <i>times</i> package &mdash; the alternative <i>mathptmx</i>
+incorporates <i>Times</i>-like mathematics, and a sans-serif face
+based on <i>Helvetica</i>, but scaled to match <i>Times</i>
+text rather better.
+<dl>
+<dt><tt><i>calc.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>Examples for LaTeX Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>)
+<dt><tt><i>The psnfss bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html
new file mode 100644
index 00000000000..714fe06c855
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html
@@ -0,0 +1,111 @@
+<head>
+<title>UK TeX FAQ -- question label nopagebrk</title>
+</head><body>
+<h3>Preventing page breaks between lines</h3>
+<p/>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.
+<p/>LaTeX provides a <code>samepage</code> 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,
+<code>samepage</code> doesn&rsquo;t help.  If you&rsquo;re trying to keep running
+text together, you need to end the paragraph inside the environment
+(see <a href="FAQ-paraparam.html">preserving paragraph parameters</a>).
+Also, if the things you are trying to keep together insert their own
+pagebreak hints, <code>samepage</code> has no power over them: a good
+example is list items &mdash; they suggest page breaks between them.  Even
+if <code>samepage</code> <em>does</em> work, it&rsquo;s likely to leave stuff
+jutting out at the bottom of the page.
+<p/>A convenient trick is to set all the relevant stuff in a <code>\</code><code>parbox</code>
+(or a <code>minipage</code> if it contains things like verbatim text
+that may not be in the argument of a <code>\</code><code>parbox</code>).  The resulting box
+certainly <em>won&rsquo;t</em> break between pages, but that&rsquo;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.
+<p/>Why do neither of these obvious things work?  Because TeX can&rsquo;t
+really distinguish between infinitely awful things.
+<code>Samepage</code> will make any possible break point &ldquo;infinitely
+bad&rdquo; and boxes don&rsquo;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.
+<p/>This problem still arises even if you have <code>\</code><code>raggedbottom</code> in
+effect: TeX doesn&rsquo;t notice the value of <em>that</em> until it starts
+actually shipping a page out.  One approach is to set:
+<blockquote>
+<pre>
+\raggedbottom
+\addtolength{\topskip}{0pt plus 10pt}
+</pre>
+</blockquote><p>
+The <code>10pt</code> 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&rsquo;re doing this as a temporary
+measure, cancel the change to <code>\</code><code>topskip</code> by:
+<blockquote>
+<pre>
+\addtolength{\topskip}{0pt plus-10pt}
+</pre>
+</blockquote><p>
+as well as resetting <code>\</code><code>flushbottom</code>.  (Note that the <code>10pt</code> never
+actually shows up, because it is overwhelmed when the page is shipped
+out by the stretchability introduced by <code>\</code><code>raggedbottom</code>; however, it
+could well have an effect if <code>\</code><code>flushbottom</code> was in effect.)
+<p/>An alternative (which derives from a suggestion by Knuth in the
+TeXbook) is the package <i>needspace</i> or the <i>memoir</i> class,
+which both define a command <code>\</code><code>needspace</code> whose argument tells it
+what space is needed.  If the space isn&rsquo;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
+<blockquote>
+<pre>
+\par
+\needspace{4\baselineskip}
+% the stuff that must stay together
+&lt;text generating lines 1-4&gt;
+% now stuff we don't mind about
+</pre>
+</blockquote><p>
+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 <code>\</code><code>filbreak</code> 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 <code>\</code><code>filbreak</code>
+into the definition of a command (as in 
+<a href="FAQ-patch.html">patching commands</a>).  A simple and effective
+patch would be:
+<blockquote>
+<pre>
+\let\oldsubsubsection=\subsubsection
+\renewcommand{\subsubsection}{%
+  \filbreak
+  \oldsubsubsection
+}
+</pre>
+</blockquote><p>
+While the trick works for consecutive sequences of blocks, it&rsquo;s
+slightly tricky to get out of such sequences unless the sequence is
+interrupted by a forced page break (such as <code>\</code><code>clearpage</code>, which may
+be introduced by a <code>\</code><code>chapter</code> 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.
+<p/>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&rsquo;s authority behind it, if one is to believe
+the rather few words he says on the subject in the TeXbook) one can
+decide, case by case, how to deal with problems at the last
+proof-reading stage.  The alternatives are to insert <code>\</code><code>clearpage</code>
+commands as necessary, or to use <code>\</code><code>enlargethispage</code>.  Supposing you
+have a line or two that stray: issue the command
+<code>\</code><code>enlargethispage{2<code>\</code><code>baselineskip</code>}</code> and two lines are
+added to the page you&rsquo;re typesetting.  It depends on the document
+whether this looks impossibly awful or entirely acceptable, but the
+command remains a useful item in the armoury.
+<dl>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>needspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/needspace.sty">macros/latex/contrib/misc/needspace.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html
new file mode 100644
index 00000000000..b755174cb2b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label nopageno</title>
+</head><body>
+<h3>How to get rid of page numbers</h3>
+<p/>The package <i>nopageno</i> will suppress page numbers in a whole
+document.
+<p/>To suppress page numbers from a single page, use
+<code>\</code><code>thispagestyle{empty}</code> somewhere within the text of the
+page.  (Note that <code>\</code><code>maketitle</code> and <code>\</code><code>chapter</code> both use
+<code>\</code><code>thispagestyle</code> internally, so you need to call it after you&rsquo;ve
+called them.)
+<p/>To suppress page numbers from a sequence of pages, you may use
+<code>\</code><code>pagestyle{empty}</code> at the start of the sequence, and restore
+the original page style at the end.  Unfortunately, you still have to
+use <code>\</code><code>thispagestyle</code> after any <code>\</code><code>maketitle</code> or <code>\</code><code>chapter</code>
+command.
+<p/>In the <i>memoir</i> class, the troublesome commands (<code>\</code><code>maketitle</code>,
+<code>\</code><code>chapter</code>, etc.) invoke their own page style
+(<code>title</code>, <code>chapter</code>, etc.), which you may
+redefine using the class&rsquo;s own techniques to be equivalent to
+&ldquo;<code>empty</code>&rdquo;.  The <i>KOMA-script</i> classes have
+commands that contain the page style to be used, so one might say:
+<blockquote>
+<pre>
+\renewcommand*{\titlepagestyle}{empty}
+</pre>
+</blockquote><p>
+<p/>An alternative (in all classes) is to use the rather delightful
+<code>\</code><code>pagenumbering{gobble}</code>; this has the simple effect that any
+attempt to print a page number produces nothing, so there&rsquo;s no issue
+about preventing any part of LaTeX from printing the number.
+However, the <code>\</code><code>pagenumbering</code> command does have the side effect that
+it resets the page number (to 1), which may be undesirable.
+<p/>The <i>scrpage2</i> package separates out the representation from
+the resetting; so one can say
+<blockquote>
+<pre>
+\renewcommand*{\pagemark}{}
+</pre>
+</blockquote><p>
+to have the same effect as the <code>gobble</code> trick, without
+resetting the page number.
+<dl>
+<dt><tt><i>nopageno</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle/nopageno.sty">macros/latex/contrib/carlisle/nopageno.sty</a>
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>scrpage2.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-normalszmiss.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-normalszmiss.html
new file mode 100644
index 00000000000..d2605726723
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-normalszmiss.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label normalszmiss</title>
+</head><body>
+<h3><code>\</code><code>normalsize</code> not defined</h3>
+<p/>The LaTeX error:
+<blockquote>
+
+<pre>
+The font size command \normalsize is not defined:
+there is probably something wrong with the class file.
+</pre>
+</blockquote><p>
+is reporting something pretty fundamental (document base font size not
+set up).  While this <em>can</em>, as the message implies, be due to a
+broken class file, the more common cause is that you have simply
+forgotten to put a <code>\</code><code>documentclass</code> command in your document.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html
new file mode 100644
index 00000000000..a1f154fd3c2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label noroom</title>
+</head><body>
+<h3>No room for a new &lsquo;<em>thing</em>&rsquo;</h3>
+<p/>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 &ldquo;registers&rdquo; is written into the specification as being 256
+(usually); this number may not be changed if you still wish to call
+the result TeX
+
+(see <a href="FAQ-triptrap.html">testing TeX implementations</a>).
+<p/>If you fill up one of these register arrays, you get a TeX error
+message saying
+<blockquote>
+<pre>
+! No room for a new \&lt;thing&gt;.
+</pre>
+</blockquote><p>
+The <code>\</code><code>thing</code>s in question may be <code>\</code><code>count</code> (the object underlying
+LaTeX&rsquo;s <code>\</code><code>newcounter</code> command), <code>\</code><code>skip</code> (the object underlying
+LaTeX&rsquo;s <code>\</code><code>newlength</code> command), <code>\</code><code>box</code> (the object underlying
+LaTeX&rsquo;s <code>\</code><code>newsavebox</code> command), or <code>\</code><code>dimen</code>, <code>\</code><code>muskip</code>,
+<code>\</code><code>toks</code>, <code>\</code><code>read</code>, <code>\</code><code>write</code> or <code>\</code><code>language</code> (all types of object
+whose use is &ldquo;hidden&rdquo; in LaTeX; the limit on the number of
+<code>\</code><code>read</code> or <code>\</code><code>write</code> objects is just 16).
+<p/>There is nothing that can directly be done about this error, as you can&rsquo;t
+extend the number of available registers without extending TeX
+itself.
+  Of course, <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a>
+
+ both do this, as does <a href="FAQ-commercial.html">MicroPress Inc&rsquo;s VTeX</a>.
+<p/>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 <a href="FAQ-epsf.html">epsf problems</a>).
+<p/>However, sometimes one just <em>needs</em> more than TeX can offer,
+and when this happens, you&rsquo;ve just got to work out a different way of
+doing things.  An example is the 
+<a href="FAQ-usepictex.html">difficulty of loading PicTeX with LaTeX</a>.
+In cases like PicTeX, it may be possible to use
+<a href="FAQ-etex.html">e-TeX</a> (all modern distributions provide it).  The
+LaTeX package <i>etex</i> modifies the register allocation
+mechanism to make use of e-TeX&rsquo;s extended register sets (it&rsquo;s a
+derivative of the Plain TeX macro file <i>etex.src</i>, which is
+used in building the e-TeX Plain format; both files are part of the
+e-TeX distribution).  Unfortunately, e-TeX doesn&rsquo;t help with
+<code>\</code><code>read</code> or <code>\</code><code>write</code> objects.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
new file mode 100644
index 00000000000..09247c59096
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label notWYSIWYG</title>
+</head><body>
+<h3>Why is TeX not a WYSIWYG system?</h3>
+<p/>WYSIWYG is a marketing term (&ldquo;What you see is what you get&rdquo;) 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.
+<p/>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&rsquo;t perceived as significant.  However, that was a long
+time ago: why has nothing been done with the &ldquo;wonder text processor&rdquo;
+to make it fit with modern perceptions?
+<p/>There are two answers to this.  First, the simple &ldquo;things <em>have</em>
+been done&rdquo; (but they&rsquo;ve not taken over the TeX world); and second,
+&ldquo;there are philosophical reasons why the way TeX has developed is
+ill-suited to the WYSIWYG style&rdquo;.
+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&rsquo;s output without actually running TeX.
+<p/>A celebrated early system offering &ldquo;WYSIWYG using TeX&rdquo; came from the
+VorTeX project: a pair of (early) Sun workstations worked in
+tandem, one handling the user interface while the other beavered away
+in the background typesetting the result.  VorTeX 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 &lsquo;great&rsquo; TeX version change, at the turn of the 1990s, to
+TeX version 3).  Modern systems that are similar in
+their approach are Lightning Textures (an extension of
+Blue Sky&rsquo;s original TeX system for the Macintosh), and Scientific
+Word (which can also cooperate with a computer algebra system); both
+these systems are <a href="FAQ-commercial.html">commercially available</a>.
+<p/>The issue has of recent years started to attract attention from TeX
+developers, and several interesting projects addressing the
+&ldquo;<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>&rdquo;
+are in progress.
+<p/>Nevertheless, the TeX world has taken a long time to latch onto the
+idea of WYSIWYG.
+Apart from simple arrogance (&ldquo;we&rsquo;re better, and have no need to
+consider the petty doings of the commercial word processor market&rdquo;),
+there is a real conceptual difference between the word processor model
+of the world and the model LaTeX and ConTeXt employ &mdash; the idea of
+&ldquo;markup&rdquo;.  &ldquo;Pure&rdquo; 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.
+<p/>Established WYSIWYG systems find the expression of this sort of
+structured markup difficult; however, markup <em>is</em> starting to
+appear in the lists of the commercial world&rsquo;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
+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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html
new file mode 100644
index 00000000000..57edaa32534
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label numbersets</title>
+</head><body>
+<h3>Symbols for the number sets</h3>
+<p/>It is a good idea to have commands such as <code>\</code><code>R</code> for the real numbers and
+other standard number sets. Traditionally these were typeset in bold.
+Because, in the ordinary course of events, mathematicians do not have
+access to bold chalk, they invented the special symbols that are now
+often used for <code>\</code><code>R</code>, <code>\</code><code>C</code>, <em>etc</em>.  These symbols are known
+as &ldquo;blackboard bold&rdquo;.  Before insisting on using them, consider
+whether going back to the old system of ordinary bold might not be
+acceptable (it is certainly simpler).
+<p/>A set of blackboard bold capitals is available in the AMS
+<i>msbm</i> fonts (<i>msbm</i> is available at a range of
+design sizes, with names such as <i>msbm10</i>). The pair of font
+families (the other is called <i>msam</i>) have a large number of
+mathematical symbols to supplement the ones in the standard TeX
+distribution, and are available in Type 1 format with most modern
+distributions. Support files for using the fonts, both under
+Plain TeX and LaTeX (packages <i>amssymb</i> and
+<i>amsfonts</i>), are available.  The font shape is a rather
+austere sans, which many people don&rsquo;t like (though it captures the
+essence of quickly-chalked writing rather well).
+<p/>The <i>bbold</i> family is set of blackboard bold fonts written in
+Metafont.  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.
+<p/>The <i>bbm</i> family claims to provide
+&lsquo;blackboard&rsquo; versions of most of the <i>cm</i> fonts ... including
+the bold and bold-extended series.  Again, the fonts are designed in
+Metafont and are not available in Type 1 format.  LaTeX macro support
+comes from a package by Torsten Hilbrich.
+<p/>The <i>doublestroke</i> family comes in just roman
+and sans shapes, at a single weight, and is available both as Metafont
+sources and as Type 1; the font covers the uppercase latin letters,
+lowercase &lsquo;h&rsquo; and &rsquo;k&rsquo;, and the digit &lsquo;1&rsquo;.
+<p/>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 (La)TeX
+(see 
+&ldquo;<a href="FAQ-psfchoice.html">choice of outline fonts</a>&rdquo;).
+Of the free sets, the <i>txfonts</i> and <i>pxfonts</i> families
+both come with replicas of <i>msam</i> and <i>msbm</i>
+(though, as noted elsewhere, there are other reasons not to use these
+fonts).  The <i>mathpazo</i> family includes a &ldquo;mathematically
+significant&rdquo; choice of blackboard bold characters, and the
+<i>fourier</i> fonts contain blackboard bold upper-case letters,
+the digit &lsquo;1&rsquo;, and lower-case &lsquo;k&rsquo;.
+<p/>The &ldquo;lazy person&rsquo;s&rdquo; blackboard bold macros:
+<blockquote>
+<pre>
+\newcommand{\R}{{\sf R\hspace*{-0.9ex}%
+  \rule{0.15ex}{1.5ex}\hspace*{0.9ex}}}
+\newcommand{\N}{{\sf N\hspace*{-1.0ex}%
+  \rule{0.15ex}{1.3ex}\hspace*{1.0ex}}}
+\newcommand{\Q}{{\sf Q\hspace*{-1.1ex}%
+  \rule{0.15ex}{1.5ex}\hspace*{1.1ex}}}
+\newcommand{\C}{{\sf C\hspace*{-0.9ex}%
+  \rule{0.15ex}{1.3ex}\hspace*{0.9ex}}}
+</pre>
+</blockquote><p>
+are almost acceptable at normal size if the surrounding text is
+<i>cmr10</i>.  However, they are not part of a proper maths font,
+and so do not work in sub- and superscripts.  Moreover, the size and
+position of the vertical bar can be affected by the font of the
+surrounding text.  As we&rsquo;ve seen, there are plenty of alternatives:
+don&rsquo;t try the macros, or anything similar using capital &lsquo;I&rsquo; (which
+looks even worse!).
+<dl>
+<dt><tt><i>AMS support files (Plain)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/plaintex.zip">fonts/amsfonts/plaintex</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/plaintex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/plaintex/">browse</a>)
+<dt><tt><i>AMS support files (LaTeX)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.zip">fonts/amsfonts/latex</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/latex/">browse</a>)
+<dt><tt><i>AMS symbol fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.zip">fonts/amsfonts/sources/symbols</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/symbols/">browse</a>)
+<dt><tt><i>AMS symbol fonts in Type 1 format</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a>
+<dt><tt><i>bbm fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/bbm.zip">fonts/cm/bbm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/bbm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/bbm/">browse</a>)
+<dt><tt><i>bbm macros</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bbm.zip">macros/latex/contrib/bbm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bbm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bbm/">browse</a>)
+<dt><tt><i>bbold fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/bbold.zip">fonts/bbold</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/bbold.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/bbold/">browse</a>)
+<dt><tt><i>doublestroke fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/doublestroke.zip">fonts/doublestroke</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/doublestroke.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/doublestroke/">browse</a>)
+<dt><tt><i>fourier fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.zip">fonts/fourier-GUT</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/fourier-GUT/">browse</a>)
+<dt><tt><i>mathpazo fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/mathpazo.zip">fonts/mathpazo</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/mathpazo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/mathpazo/">browse</a>)
+<dt><tt><i>pxfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.zip">fonts/pxfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/">browse</a>)
+<dt><tt><i>txfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html
new file mode 100644
index 00000000000..ee818a6709e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html
@@ -0,0 +1,40 @@
+<head>
+<title>UK TeX FAQ -- question label oarglikesect</title>
+</head><body>
+<h3>Optional arguments like <code>\</code><code>section</code></h3>
+<p/>Optional arguments, in macros defined using <code>\</code><code>newcommand</code>, don&rsquo;t
+quite work like the optional argument to <code>\</code><code>section</code>.  The default
+value of <code>\</code><code>section</code>&rsquo;s optional argument is the value of the
+mandatory argument, but <code>\</code><code>newcommand</code> requires that you &lsquo;know&rsquo; the
+value of the default beforehand.
+<p/>The requisite trick is to use a macro in the optional argument:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+LaTeX itself has a trickier (but less readily understandable)
+method, using a macro <code>\</code><code>@dblarg</code>; inside LaTeX, the example
+above would have been programmed:
+<blockquote>
+<pre>
+\newcommand\thing{\@dblarg\@thing}
+\newcommand\@thing[2][\@error]{%
+  optional arg: #1,  mandatory arg: #2%
+}
+</pre>
+</blockquote><p>
+In that code, <code>\</code><code>@thing</code> is only ever called with an optional and a
+mandatory argument; if the default from the <code>\</code><code>newcommand</code> is
+invoked, a bug in user code has bitten...
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html
new file mode 100644
index 00000000000..c7190c78a0a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label oddhyphen</title>
+</head><body>
+<h3>(Merely) peculiar hyphenation</h3>
+<p/>You may have found that TeX&rsquo;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&rsquo;s Dictionary) are
+completely different from the British ones (as specified, for example,
+in the Oxford Dictionaries). This problem is being addressed by the UK
+TeX User community (see <i>Baskerville</i>, issue 4.4) but an entirely
+satisfactory solution will take time; the current status is to be
+found on CTAN (see
+
+<a href="FAQ-newlang.html">&ldquo;using a new language&rdquo;</a> for instructions
+on adding this new &ldquo;language&rdquo;).
+<dl>
+<dt><tt><i>UK patterns</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/language/hyphenation/ukhyphen.tex">language/hyphenation/ukhyphen.tex</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html
new file mode 100644
index 00000000000..2640db821fe
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label oddpage</title>
+</head><body>
+<h3>Finding if you&rsquo;re on an odd or an even page</h3>
+<p/><a href="FAQ-marginparside.html">Another question</a> discusses the issue
+of getting <code>\</code><code>marginpar</code> 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 (La)TeX will usually process quite a
+bit of the &ldquo;next&rdquo; page before deciding to output any page.  As a
+result, the <code>page</code> counter (known internally in LaTeX as
+<code>\</code><code>c@page</code>) is normally only reliable when you&rsquo;re actually <em>in</em>
+the output routine.
+<p/>The solution is to use some version of the <code>\</code><code>label</code> mechanism to
+determine which side of the page you&rsquo;re on; the value of the page
+counter that appears in a <code>\</code><code>pageref</code> command has been inserted in
+the course of the output routine, and is therefore safe.
+<p/>However, <code>\</code><code>pageref</code> itself isn&rsquo;t reliable: one might hope that
+<pre>
+\ifthenelse{\isodd{\pageref{foo}}}{odd}{even}
+</pre>
+would do the necessary, but both the <i>babel</i> and
+<i>hyperref</i> packages have been known to interfere with the
+output of <code>\</code><code>pageref</code>; be careful!
+<p/>The <i>changepage</i> package needs to provide this functionality for
+its own use, and therefore provides a command <code>\</code><code>checkoddpage</code>; this
+sets a private-use label, and the page reference part of that label is
+then examined (in a <i>hyperref</i>-safe way) to set a conditional 
+<code>\</code><code>ifoddpage</code> true if the command was issued on an odd page.  The
+<i>memoir</i> class has the same command setting a conditional
+<code>\</code><code>ifoddpage</code>.  Of course, the <code>\</code><code>label</code> contributes to LaTeX&rsquo;s
+&ldquo;Rerun to get cross-references right&rdquo; error messages...
+<p/>The (older) <i>chngpage</i> provides the same facilities (though it
+provides a <code>\</code><code>ifcpoddpage</code> command; <i>changepage</i> (whose
+functions are extracted from the author&rsquo;s <i>memoir</i> class) is the
+designated successor to <i>chngpage</i>.
+<p/>The Koma-Script classes have an <code>addmargin*</code> environment
+that also provides the sorts of facilities that the <i>chngpage</i>
+offers.  Koma-Script&rsquo;s supporting command is 
+<code>\</code><code>ifthispageodd{&lt;true&gt;}{&lt;false&gt;}</code> executes different things
+depending on the page number.
+<dl>
+<dt><tt><i>changepage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/changepage.sty">macros/latex/contrib/misc/changepage.sty</a>
+<dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a>
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html
new file mode 100644
index 00000000000..84a65fde319
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html
@@ -0,0 +1,29 @@
+<head>
+<title>UK TeX FAQ -- question label ol-books</title>
+</head><body>
+<h3>Freely available (La)TeX books</h3>
+<p/>People have long argued for (La)TeX books to be made available on
+the web, and until relatively recently this demand went un-answered.
+<p/>The first to appear was Victor Eijkhout&rsquo;s excellent &ldquo;TeX by
+Topic&rdquo; in 2001 (it had been published by Addison-Wesley, but was long
+out of print).  The book is now available on CTAN; it&rsquo;s not a
+beginner&rsquo;s tutorial but it&rsquo;s a fine reference.
+<p/>Addison-Wesley have also released the copyright of &ldquo;TeX for the
+Impatient&rdquo; 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 GNU Free Documentation
+Licence, and it is available from CTAN.
+<p/>Norm Walsh&rsquo;s &ldquo;Making TeX Work&rdquo; (originally published by O&rsquo;Reilly)
+is also available (free) on the Web, at
+<a href="http://makingtexwork.sourceforge.net/mtw/">http://makingtexwork.sourceforge.net/mtw/</a>; the sources of the
+Web page are on 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.
+<dl>
+<dt><tt><i>Making TeX Work</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/makingtexwork/mtw-1.0.1-html.tar.gz">info/makingtexwork/mtw-1.0.1-html.tar.gz</a>
+<dt><tt><i>TeX by Topic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/texbytopic.zip">info/texbytopic</a> (<a href="ftp://cam.ctan.org/tex-archive/info/texbytopic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/texbytopic/">browse</a>)
+<dt><tt><i>TeX for the Impatient</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/impatient.zip">info/impatient</a> (<a href="ftp://cam.ctan.org/tex-archive/info/impatient.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/impatient/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html
new file mode 100644
index 00000000000..d53ed253afb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label oldfontnames</title>
+</head><body>
+<h3>Old LaTeX font references such as <code>\</code><code>tenrm</code></h3>
+<p/>LaTeX 2.09 defined a large set of commands for access to the fonts
+that it had built in to itself.  For example, various flavours of
+<code>cmr</code> could be found as <code>\</code><code>fivrm</code>, <code>\</code><code>sixrm</code>, <code>\</code><code>sevrm</code>,
+<code>\</code><code>egtrm</code>, <code>\</code><code>ninrm</code>, <code>\</code><code>tenrm</code>, <code>\</code><code>elvrm</code>, <code>\</code><code>twlrm</code>,
+<code>\</code><code>frtnrm</code>, <code>\</code><code>svtnrm</code>, <code>\</code><code>twtyrm</code> and <code>\</code><code>twfvrm</code>.
+These commands were never documented, but certain packages
+nevertheless used them to achieve effects they needed.
+<p/>Since the commands weren&rsquo;t public, they weren&rsquo;t included in LaTeX2e;
+to use the unconverted LaTeX 2.09 packages under LaTeX2e, you need
+also to include the <i>rawfonts</i> package (which is part of the
+LaTeX2e distribution).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html
new file mode 100644
index 00000000000..f8a4d6d829f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label omegaleph</title>
+</head><body>
+<h3>Omega and Aleph</h3>
+<p/>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 &ldquo;translation
+process&rdquo; that takes a character stream and transforms it according to
+various processes that may be internally specified, or be a separate
+program.
+<p/>While Omega showed a lot of promise at its mid-1990s announcement, its
+development 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).
+<p/>Before that distressing event, a separate thread of development was
+started, to produce a program called Aleph
+, which merged the facilities of
+<a href="FAQ-etex.html">e-TeX</a> 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.
+<p/>The latest news (from EuroTeX 2006) is that development of Omega is
+picking up again, in parallel with research into what the (new)
+authors consider a rational scheme for supporting TeX-style
+typesetting.  The new system is to be known as Omega-2
+(Omega subscript 2), and is being
+designed in a modular fashion so that support of new facilities (such
+as use of advanced OpenType fonts) can be added in a relatively
+straightforward fashion.
+<p/>The work done in the Aleph project is also being carried forward in
+the <a href="FAQ-luatex.html">LuaTeX</a> project.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html
new file mode 100644
index 00000000000..99f87bc3b2d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html
@@ -0,0 +1,63 @@
+<head>
+<title>UK TeX FAQ -- question label onecolabs</title>
+</head><body>
+<h3>1-column abstract in 2-column document</h3>
+<p/>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:
+<blockquote>
+<pre>
+\documentclass[twocolumn]{article}
+...
+\begin{document}
+... % \author, etc
+\twocolumn[
+  \begin{@twocolumnfalse}
+    \maketitle
+    \begin{abstract}
+      ...
+    \end{abstract}
+  \end{@twocolumnfalse}
+  ]
+</pre>
+</blockquote><p>
+Unfortunately, with the above <code>\</code><code>thanks</code> won&rsquo;t work in the
+<code>\</code><code>author</code> list.  If you need such specially-numbered footnotes, you
+can make them like this:
+<blockquote>
+<pre>
+\title{Demonstration}
+\author{Me, You\thanks{}}
+\twocolumn[
+  ... as above ...
+]
+{
+  \renewcommand{\thefootnote}%
+    {\fnsymbol{footnote}}
+  \footnotetext[1]{Thanks for nothing}
+}
+</pre>
+</blockquote><p>
+and so on.
+<p/>As an alternative, among other facilities the <i>abstract</i> package 
+provides a
+<code>\</code><code>saythanks</code> command and a <code>onecolabstract</code> environment
+which remove the need to fiddle with the <code>\</code><code>thanks</code> and
+footnoting. They can be used like this:
+<blockquote>
+<pre>
+\twocolumn[
+  \maketitle             % full width title
+  \begin{onecolabstract} % ditto abstract
+    ... text
+  \end{onecolabstract}
+]
+\saythanks            % typeset any \thanks
+</pre>
+</blockquote><p>
+The <i>memoir</i> class offers all the facilities of <i>abstract</i>.
+<dl>
+<dt><tt><i>abstract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.zip">macros/latex/contrib/abstract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/abstract/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html
new file mode 100644
index 00000000000..f42f1325341
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html
@@ -0,0 +1,104 @@
+<head>
+<title>UK TeX FAQ -- question label optionclash</title>
+</head><body>
+<h3>Option clash for package</h3>
+<p/>So you&rsquo;ve innocently added:
+<blockquote>
+<code>\</code><code>usepackage[draft]{graphics}</code>
+</blockquote><p>
+to your document, and LaTeX responds with
+<blockquote>
+<pre>
+! LaTeX Error: Option clash for package graphics.
+</pre>
+</blockquote><p>
+
+<p/>The error is a complaint about loading a package 
+<em>with options</em>, more than once (LaTeX doesn&rsquo;t actually examine
+what options there are: it complains because it can&rsquo;t do anything with
+the multiple sets of options).  You can load a package
+any number of times, with no options, and LaTeX will be happy, but
+you may only supply options when you first load the package.
+<p/>So perhaps you weren&rsquo;t entirely innocent &mdash; the error would have
+occurred on the second line of:
+<blockquote>
+<code>\</code><code>usepackage[dvips]{graphics}</code><br>
+<code>\</code><code>usepackage[draft]{graphics}</code>
+</blockquote><p>
+which could quite reasonably (and indeed correctly) have been typed:
+<blockquote>
+<code>\</code><code>usepackage[dvips,draft]{graphics}</code>
+</blockquote><p>
+<p/>But if you&rsquo;ve not made that mistake (even with several lines
+separating the <code>\</code><code>usepackage</code> commands, it&rsquo;s pretty easy to spot),
+the problem could arise from something else loading the package for
+you.  How do you find the culprit?  The "<code>h</code>" response to the
+error message tells you which options were loaded each time.
+Otherwise, it&rsquo;s down to the log analysis games discussed in 
+&ldquo;<a href="FAQ-erroradvice.html">How to approach errors</a>&rdquo;; the trick to remember
+is that that the process of loading each file is parenthesised in the
+log; so if package <i>foo</i> loads <i>graphics</i>, the log
+will contain something like:
+<blockquote>
+<pre>
+(&lt;path&gt;/foo.sty ...
+...
+(&lt;path&gt;/graphics.sty ...
+...)
+...
+)
+</pre>
+</blockquote><p>
+(the parentheses for <i>graphics</i> are completely enclosed in
+those for <i>foo</i>; the same is of course true if your class
+<i>bar</i> is the culprit, except that the line will start with the
+path to <code>bar.cls</code>).
+<p/>If we&rsquo;re dealing with a package that loads the package you are
+interested in, you need to ask LaTeX to slip in options when
+<i>foo</i> loads it.  Instead of:
+<blockquote>
+<code>\</code><code>usepackage{foo}</code><br>
+<code>\</code><code>usepackage[draft]{graphics}</code>
+</blockquote><p>
+you would write:
+<blockquote>
+<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code><br>
+<code>\</code><code>usepackage{foo}</code>
+</blockquote><p>
+The command <code>\</code><code>PassOptionsToPackage</code> tells LaTeX to behave as if
+its options were passed, when it finally loads a package.  As you would
+expect from its name, <code>\</code><code>PassOptionsToPackage</code> can deal with a list
+of options, just as you would have in the the options brackets of
+<code>\</code><code>usepackage</code>.
+<p/>More trickily, instead of:
+<blockquote>
+<code>\</code><code>documentclass[...]{bar}</code><br>
+<code>\</code><code>usepackage[draft]{graphics}</code>
+</blockquote><p>
+you would write:
+<blockquote>
+<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code><br>
+<code>\</code><code>documentclass[...]{bar}</code>
+</blockquote><p>
+with <code>\</code><code>PassOptionsToPackage</code> <em>before</em> the <code>\</code><code>documentclass</code>
+command.
+<p/>However, if the <i>foo</i> package or the <i>bar</i> class loads
+<i>graphics</i> with an option of its own that clashes with
+what you need in some way, you&rsquo;re stymied.  For example:
+<blockquote>
+<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code>
+</blockquote><p>
+where the package or class does:
+<blockquote>
+<code>\</code><code>usepackage[final]{graphics}</code>
+</blockquote><p>
+sets <code>final</code> <em>after</em> it&rsquo;s dealt with option you passed to
+it, so your <code>draft</code> will get forgotten.  In extreme cases,
+the package might generate an error here (<i>graphics</i> doesn&rsquo;t
+go in for that kind of thing, and there&rsquo;s no indication that
+<code>draft</code> has been forgotten).
+<p/>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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html
new file mode 100644
index 00000000000..86dc97512a8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label otherprinters</title>
+</head><body>
+<h3>Output to &ldquo;other&rdquo; printers</h3>
+<p/>In the early years of TeX, there were masses of 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 PostScript, and <i>ghostscript</i> is <em>so</em> good, and
+has <em>such</em> a wide range of printer drivers (perhaps this is where
+the DVI output driver writers have all gone?).
+<p/>The general advice, then, is to <a href="FAQ-dvips.html">generate PostScript</a>, and
+to process that with <i>ghostscript</i> set to generate the format
+for the printer you actually have.  If you are using a Unix system of
+some sort, it&rsquo;s generally quite easy to insert <i>ghostscript</i>
+into the print spooling process.
+<dl>
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html
new file mode 100644
index 00000000000..40d1c2c3510
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html
@@ -0,0 +1,73 @@
+<head>
+<title>UK TeX FAQ -- question label ouparmd</title>
+</head><body>
+<h3>Not in outer par mode</h3>
+<p/>The error:
+<blockquote>
+<pre>
+! LaTeX Error: Not in outer par mode.
+</pre>
+</blockquote><p>
+comes when some &ldquo;main&rdquo; document feature is shut up somewhere it
+doesn&rsquo;t like.
+<p/>The commonest occurrence is when the user wants a figure somewhere
+inside a table:
+<blockquote>
+<pre>
+\begin{tabular}{|l|}
+  \hline
+  \begin{figure}
+  \includegraphics{foo}
+  \end{figure}
+  \hline
+\end{tabular}
+</pre>
+</blockquote><p>
+a construction that was supposed to put a frame around the diagram,
+but doesn&rsquo;t work, any more than:
+<blockquote>
+<pre>
+\framebox{\begin{figure}
+  \includegraphics{foo}
+  \end{figure}%
+}
+</pre>
+</blockquote><p>
+The problem is, that the <code>tabular</code> environment, and the
+<code>\</code><code>framebox</code> command restrain the <code>figure</code> environment
+from its natural m&eacute;tier, which is to float around the document.
+<p/>The solution is simply not to use the <code>figure</code> environment
+here:
+<blockquote>
+<pre>
+\begin{tabular}{|l|}
+  \hline
+  \includegraphics{foo}
+  \hline
+\end{tabular}
+</pre>
+</blockquote><p>
+What was the float for? &mdash; 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.
+<p/>It&rsquo;s simple to achieve this &mdash; just reverse the order of the
+environments (or of the <code>figure</code> environment and the
+command):
+<blockquote>
+<pre>
+\begin{figure}
+  \begin{tabular}{|l|}
+    \hline
+    \includegraphics{foo}
+    \caption{A foo}
+    \hline
+  \end{tabular}
+\end{figure}
+</pre>
+</blockquote><p>
+The same goes for <code>table</code> environments (or any other sort
+of float you&rsquo;ve defined for yourself) inside tabulars or box commands;
+you <em>must</em> get the float environment out from inside, one way or
+another.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-outszwrng.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-outszwrng.html
new file mode 100644
index 00000000000..9df037e476c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-outszwrng.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label outszwrng</title>
+</head><body>
+<h3>(La)TeX PDF output prints at wrong size</h3>
+<p/>Having got everything <em>else</em> right, you should be aware that the
+problem may have nothing to do with (La)TeX 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).
+<p/>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:
+<ul>
+<li>  Mac OS X, Adobe Reader 6:<br>
+  in the print dialogue, on the &ldquo;copies &amp; pages&rdquo; pane, you&rsquo;ll find a
+  popup menu titled &ldquo;Page Scaling&rdquo;. Make sure that the menu reads
+  &ldquo;None&rdquo;.
+<li> Windows, Adobe Reader 6:<br>
+  in the print dialogue, select &ldquo;None&rdquo; from the drop-down list
+  &ldquo;Page Scaling&rdquo;.
+<li> Windows, Linux Acrobat (Reader) 5.0:<br>
+  In the print dialog, make sure the &ldquo;Shrink oversized pages to fit&rdquo;
+  checkbox is unchecked.  It may also be useful to uncheck the
+  &ldquo;Expand small pages to fit paper size&rdquo; checkbox as well.
+</ul>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
new file mode 100644
index 00000000000..b518a27bc39
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
@@ -0,0 +1,133 @@
+<head>
+<title>UK TeX FAQ -- question label overfull</title>
+</head><body>
+<h3>(La)TeX makes overfull lines</h3>
+<p/>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&rsquo;s line breaking works by adjusting the parameters: this answer
+deals with the &ldquo;tolerance&rdquo; and stretchability parameters.  The other
+vital &lsquo;parameter&rsquo; is the set of hyphenations to be applied: see
+&ldquo;<a href="FAQ-nohyph.html">my words aren&rsquo;t being hyphenated</a>&rdquo;
+(and the questions it references) for advice.
+<p/>If you&rsquo;re getting an undesired &ldquo;overfull box&rdquo;, what has happened is
+that TeX has given up: the parameters you gave it don&rsquo;t allow it to
+produce a result that <em>doesn&rsquo;t</em> 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 &ldquo;good taste&rdquo; 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&rsquo;s
+provoking the problem &mdash; but that&rsquo;s not always possible, and in some
+cases it&rsquo;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&rsquo;ve got the
+hyphenation correct.
+<p/>The simplest case is where a &lsquo;small&rsquo; word fails to break at the end of
+a line; pushing the entire word to a new line isn&rsquo;t going to make much
+difference, but it might make things just bad enough that TeX won&rsquo;t
+do it by default.  In such a case on can <em>try</em> the LaTeX
+<code>\</code><code>linebreak</code> 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&rsquo;s line
+breaking mechanisms.
+<p/>TeX&rsquo;s first attempt at breaking lines is performed without even
+trying hyphenation: TeX sets its &ldquo;tolerance&rdquo; of line breaking
+oddities to the internal value <code>\</code><code>pretolerance</code>, and sees what
+happens.  If it can&rsquo;t get an acceptable break, TeX adds the
+hyphenation points allowed by the current patterns, and tries again
+using the internal <code>\</code><code>tolerance</code> value.  If this pass also fails, and
+the internal <code>\</code><code>emergencystretch</code> value is positive, TeX will try
+a pass that allows <code>\</code><code>emergencystretch</code> worth of extra stretchability
+to the spaces in each line.
+<p/>In principle, therefore, there are three parameters (other than
+hyphenation) that you can change: <code>\</code><code>pretolerance</code>, <code>\</code><code>tolerance</code>
+and <code>\</code><code>emergencystretch</code>.  Both the <code>tolerance</code> values are
+simple numbers, and should be set by TeX primitive count
+assignment &mdash; for example
+<blockquote>
+<pre>
+\pretolerance=150
+</pre>
+</blockquote><p>
+For both, an &ldquo;infinite&rdquo; tolerance is represented by the value
+<code>10</code><code>000</code>, but infinite tolerance is rarely
+appropriate, since it can lead to very bad line breaks indeed.
+<p/><code>\</code><code>emergencystretch</code> is a TeX-internal &lsquo;dimen&rsquo; register, and can
+be set as normal for dimens in Plain TeX; in LaTeX, use
+<code>\</code><code>setlength</code> &mdash; for example:
+<blockquote>
+<pre>
+\setlength{\emergencystretch}{3em}
+</pre>
+</blockquote><p>
+<p/>The choice of method has time implications &mdash; each of the
+passes takes time, so adding a pass (by changing
+<code>\</code><code>emergencystretch</code>) is less desirable than suppressing one (by
+changing <code>\</code><code>pretolerance</code>).  However, it&rsquo;s unusual nowadays to find a
+computer that&rsquo;s slow enough that the extra passes are really
+troublesome.
+<p/>In practice, <code>\</code><code>pretolerance</code> is rarely used other than to manipulate
+the use of hyphenation; Plain TeX and LaTeX both set its value
+to <code>100</code>.  To suppress the first scan of paragraphs, set
+<code>\</code><code>pretolerance</code> to <code>-1</code>.
+<p/><code>\</code><code>tolerance</code> is often a good method for adjusting spacing;
+Plain TeX and LaTeX both set its value to <code>200</code>.  LaTeX&rsquo;s
+<code>\</code><code>sloppy</code> command sets it to <code>9999</code>, as does the
+<code>sloppypar</code> environment.  This value is the largest
+available, this side of infinity, and can allow pretty poor-looking
+breaks (this author rarely uses <code>\</code><code>sloppy</code> &ldquo;bare&rdquo;, though he does
+occasionally use <code>sloppypar</code> &mdash; that way, the change of
+<code>\</code><code>tolerance</code> is confined to the environment).  More satisfactory is
+to make small changes to <code>\</code><code>tolerance</code>, incrementally, and then to look to
+see how the change affects the result; very small increases can often
+do what&rsquo;s necessary.  Remember that <code>\</code><code>tolerance</code> is a paragraph
+parameter, so you need to ensure it&rsquo;s actually applied &mdash; see
+&ldquo;<a href="FAQ-paraparam.html">ignoring paragraph parameters</a>&rdquo;.
+LaTeX users could use an environment like:
+<blockquote>
+<pre>
+\newenvironment{tolerant}[1]{%
+  \par\tolerance=#1\relax
+}{%
+  \par
+}
+</pre>
+</blockquote><p>
+enclosing entire paragraphs (or set of paragraphs) in it.
+<p/>The value of <code>\</code><code>emergencystretch</code> 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&rsquo;t be made to look
+right any other way.  (The extra scan happens if
+<code>\</code><code>emergencystretch&gt;0pt</code> &mdash; if it&rsquo;s zero or negative, no gain
+could be had from rerunning the paragraph setter.)  The example above
+set it to <code>3em</code>; the Computer Modern fonts ordinarily fit three
+space skips to the <code>em</code>, 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 <code>\</code><code>emergencystretch</code> needs to be
+treated with a degree of caution.
+<p/>More subtle (but more tricky to manage) are the microtypographic
+extensions provided by PDFTeX.  Since PDFTeX is the default
+&lsquo;engine&rsquo; 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 &ldquo;get things right&rdquo;.
+Font expansion works like a subtler version of the trick that
+<code>\</code><code>emergencystretch</code> plays: PDFTeX &lsquo;knows&rsquo; that your current font
+may be stretched (or shrunk) to a certain extent, and will do that
+&ldquo;on the fly&rdquo; to optimise the setting of a paragraph.  This is a
+powerful tool in the armoury of the typesetter.
+<p/>As mentioned above, the microtypographic extensions are tricky beasts
+to control; however, the <i>microtype</i> package relieves the user
+of the tedious work of specifying how to perform margin adjustments
+and how much to scale each font ... for the fonts the package
+knows about; it&rsquo;s a good tool, and users who can take on the
+specification of adjustments for yet more fonts are always welcome.
+<dl>
+<dt><tt><i>microtype.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html
new file mode 100644
index 00000000000..a167ee447d5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label overstrike</title>
+</head><body>
+<h3>Overstriking characters</h3>
+<p/>This may be used, for example, to indicate text deleted in the course
+of editing.  Both the <i>ulem</i> and the <i>soul</i> packages
+provide the necessary facilities.
+<p/>Overstriking for 
+<a href="FAQ-cancellation.html">cancellation in maths expressions</a> is achieved
+by a different mechanism.
+<p/>Documentation of <i>ulem</i> is in the package file.
+<dl>
+<dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>)
+<dt><tt><i>ulem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html
new file mode 100644
index 00000000000..6ab9fcfe881
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html
@@ -0,0 +1,26 @@
+<head>
+<title>UK TeX FAQ -- question label pagebychap</title>
+</head><body>
+<h3>Page numbering by chapter</h3>
+<p/>When I was a young man, a common arrangement for loose bound technical
+manuals is to number pages by chapter.  (It&rsquo;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.)
+<p/>The problem, at first sight, seems pretty much the same as that in
+another answer on
+
+<a href="FAQ-running-nos.html">running numbers within a chapter</a>,
+and the basic technique is indeed pretty similar.
+<p/>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 <i>chappg</i> package
+was written: it does the obvious things, and more.
+<p/>Users have been known to ask for running page numbers within a
+section, but this really doesn&rsquo;t make sense: you need to run page
+numbers within document objects that always start on a fresh page.
+<p/>Documentation of <i>chappg</i> is to be found in the package file.
+<dl>
+<dt><tt><i>chappg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.zip">macros/latex/contrib/chappg</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chappg/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html
new file mode 100644
index 00000000000..d02dc4cbce4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html
@@ -0,0 +1,90 @@
+<head>
+<title>UK TeX FAQ -- question label papergeom</title>
+</head><body>
+<h3>Getting the right paper geometry from (La)TeX</h3>
+<p/>If your output is the wrong size, and you&rsquo;ve checked that it&rsquo;s not due
+to the <a href="FAQ-acroantics.html">ministrations of Adobe <i>Reader</i></a>,
+the problem is probably that your (La)TeX system is producing output
+that specifies the wrong paper size.  Paper sizes can be a pain:
+they&rsquo;re a forgotten backwater &mdash; Knuth seems not to have considered
+paper size as something the TeX engine needs to know about.  As a
+result, there is no 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&rsquo;s chosen paper
+size, and device drivers&rsquo; choice happens independently of the macros&rsquo;
+ideas.
+<p/>In practice, one usually finds that macro packages (such as Plain TeX and
+LaTeX) assume American &ldquo;letter&rdquo; paper size, by default; and since
+most distributions nowadays originate in Europe, the drivers usually
+default to ISO &ldquo;A4&rdquo; paper size.
+<p/>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
+<i>xdvi</i>, <i>dvips</i> (or whatever) runs, it uses the
+paper size the document was designed for.
+<p/>The default paper size for DVI drivers may be changed by a
+distribution management command (<i>texconfig</i> for TeX Live,
+the <i>Options</i> application for MiKTeX), but this still
+doesn&rsquo;t provide for people using the &ldquo;wrong&rdquo; sort of paper for some
+reason.
+<p/>A different issue arises for users of PDFTeX &mdash; the
+PDF format <em>does</em> have the means of expressing paper size
+and PDFTeX has system variables <code>\</code><code>pdfpagewidth</code> and
+<code>\</code><code>pdfpageheight</code>, that are written into the output 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 <code>\</code><code>documentclass</code> option.
+<p/>The DVI drivers <i>dvips</i> and <i>dvipdfm</i> define
+<code>\</code><code>special</code> commands for the document to specify its own paper size;
+so in those cases, as when PDFTeX or VTeX 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.
+<p/>The <i>geometry</i> package (whose main business is 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
+<i>geometry</i> is used when a document is being processed by
+PDFLaTeX, it can set the necessary dimensions &ldquo;in the output&rdquo;.
+If the document is being processed by LaTeX on a TeX or e-TeX
+engine, there are package options which instruct <i>geometry</i>
+which <code>\</code><code>special</code> commands to use.  (Note that the options are
+ignored if you are using either PDFLaTeX or VTeX.)
+<p/>So, the resolution of the problem is to add
+<blockquote>
+<pre>
+\usepackage[dvixxx,...]{geometry}
+</pre>
+</blockquote><p>
+(where <code>dvixxx</code> is your current favourite DVI
+driver &mdash; <i>geometry</i> knows about <code>dvips</code> and
+<code>dvipdfm</code>), and the document will run correctly with
+LaTeX.  If you&rsquo;re using PDFLaTeX, load with
+<blockquote>
+<pre>
+\usepackage[pdftex,...]{geometry}
+</pre>
+</blockquote><p>
+<p/>Needless to say, both the &ldquo;big&rdquo; classes (<i>koma-script</i> and
+<i>memoir</i>) provide their own ways to get the paper size
+&ldquo;right&rdquo;.
+<p/>The <i>typearea</i> package is the <i>Koma-script</i>
+distribution&rsquo;s way of providing page layout functionality.  Load it
+with the <code>pagesize</code> option and it will ensure the correct
+paper is selected, for PDF output from PDFLaTeX, and for
+PostScript output from LaTeX via <i>dvips</i>.
+<p/><i>Memoir</i> has the standard classes&rsquo; paper-size selections
+(<code>a4paper</code>, <code>letterpaper</code> and so on), but also
+permits the user to choose an arbitrary paper size, by setting the
+length registers <code>\</code><code>stockheight</code> and <code>\</code><code>stockwidth</code>.  The commands
+<code>\</code><code>fixdvipslayout</code> (for LaTeX processing), and <code>\</code><code>fixpdflayout</code>
+(for PDFLaTeX processing) then instruct the processor to produce
+output that specifies the necessary paper size.
+<dl>
+<dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papergeom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papergeom</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html
new file mode 100644
index 00000000000..ab1fcabda32
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label papersize</title>
+</head><body>
+<h3>The size of printed output</h3>
+<p/>The final product of a (La)TeX run is something for a person to
+read.  Often, nowadays, that product will be read &ldquo;on-screen&rdquo;, but
+the printed page remains a principal output form.
+<p/>When we come to print our output, it is important that the output fits
+on the paper; in some cases, for the output to &ldquo;fit&rdquo; 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&rsquo;s a dissertation which must match the fancies of some bureaucrat
+even to be considered.)
+<p/>Sadly, we often find that the printed output doesn&rsquo;t conform to our
+expectations...
+<p/>The check-list for such problems has two entries:
+<ul>
+<li> Your output is generated via Adobe <i>Reader</i> (or
+  possibly &ldquo;<i>Acrobat Reader</i>&rdquo; &mdash; older versions of the
+  program had the qualified name).  In this case, it may be that
+  <i>Reader</i> is willfully changing the size of your output:
+  read <a href="FAQ-acroantics.html"><i>Reader</i> antics</a>.
+<li> Something in your TeX system is producing the wrong size (or
+  shape) of output: read <a href="FAQ-papergeom.html">paper geometry</a>.
+</ul>
+<p/>An alternative approach is to use the (excellent) <i>testflow</i>
+suite, that provides a detailed outline of the potential problems
+together with a sample document and prototype outputs.
+<dl>
+<dt><tt><i>testflow bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html
new file mode 100644
index 00000000000..b84159458b7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html
@@ -0,0 +1,59 @@
+<head>
+<title>UK TeX FAQ -- question label parallel</title>
+</head><body>
+<h3>Parallel setting of text</h3>
+<p/>It&rsquo;s commonly necessary to present text in two languages &lsquo;together&rsquo; 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.
+<p/>The <i>parallel</i> 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
+<blockquote>
+<pre>
+\usepackage{parallel}
+...
+\begin{Parallel}{&lt;left-width&gt;}{&lt;right-width}
+  \ParallelLText{left-text}
+  \ParallelRText{right-text}
+  \ParallelPar
+  ...
+\end{Parallel}
+</pre>
+</blockquote><p>
+<i>Parallel</i> can get terribly confused with colour changes, in
+PDFTeX; the indefatigable Heiko Oberdiek has a patch for this
+issue &mdash; the <i>pdfcolparallel</i>, which maintains separate
+colour stacks for the columns.
+<p/>The <i>parcolumns</i> 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 <i>parallel</i>,
+though there is of course a &ldquo;number of columns to specify&rdquo;:
+<blockquote>
+<pre>
+\usepackage{parcolumns}
+...
+\begin{parcolumns}[&lt;options&gt;]{3}
+  \colchunk{&lt;Column 1 text&gt;}
+  \colchunk{&lt;Column 2 text&gt;}
+  \colchunk{&lt;Column 3 text&gt;}
+  \colplacechunks
+  ...
+\end{parcolumns}
+</pre>
+</blockquote><p>
+The &lt;<i>options</i>&gt; can specify the widths of the columns, whether to
+place rules between the columns, whether to set the columns sloppy, etc.
+<p/>The <i>ledpar</i> package is distributed with (and integrated with)
+the <a href="FAQ-linenos.html"><i>ledmac</i> package</a>.  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 &lsquo;base&rsquo; text of the document.
+<dl>
+<dt><tt><i>ledpar.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse</a>)
+<dt><tt><i>parallel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.zip">macros/latex/contrib/parallel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/parallel/">browse</a>)
+<dt><tt><i>parcolumns.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse</a>)
+<dt><tt><i>pdfcolparallel.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html
new file mode 100644
index 00000000000..60ded834d24
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html
@@ -0,0 +1,59 @@
+<head>
+<title>UK TeX FAQ -- question label paraparam</title>
+</head><body>
+<h3>Why does it ignore paragraph parameters?</h3>
+<p/>When TeX is laying out text, it doesn&rsquo;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&rsquo;t touched further until the end-paragraph marker is processed.
+It&rsquo;s at this point that the paragraph parameters have effect; and it&rsquo;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).
+<p/>Consider the following sequence of LaTeX:
+<blockquote>
+<pre>
+{\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...
+</pre>
+</blockquote><p>
+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 <code>\</code><code>raggedright</code> set).  Then TeX encounters a blank
+line, which it knows to treat as a <code>\</code><code>par</code> 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.
+<p/>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:
+<blockquote>
+<pre>
+end the group.\par}
+Here's more that needn't be ragged...
+</pre>
+</blockquote><p>
+In this way, the paragraph is completed while <code>\</code><code>raggedright</code>&rsquo;s
+parameters are still in force within the enclosing group.
+<p/>Another alternative is to define an environment that does the
+appropriate job for you.  For the above example, LaTeX already
+defines an appropriate one:
+<blockquote>
+<pre>
+\begin{flushleft}
+Here's text to be ranged left...
+\end{flushleft}
+</pre>
+</blockquote><p>
+<p/>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 <a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code></a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html
new file mode 100644
index 00000000000..2407453735b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html
@@ -0,0 +1,36 @@
+<head>
+<title>UK TeX FAQ -- question label parskip</title>
+</head><body>
+<h3>Zero paragraph indent</h3>
+<p/>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.
+<p/>In contrast, one common convention for typewritten text was to have no
+indentation of paragraphs; such a style is often required for
+&ldquo;brutalist&rdquo; publications such as technical manuals, and in styles
+that hanker after typewritten manuscripts, such as
+officially-specified dissertation formats.
+<p/>Anyone can see, after no more than a moment&rsquo;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.
+<p/>The simple-minded approach to zero paragraph indentation is thus:
+<pre>
+  \setlength{\parindent}{0pt}
+  \setlength{\parskip}{\baselineskip}
+</pre>
+and in the very simplest text, it&rsquo;s a fine solution.
+<p/>However, the non-zero <code>\</code><code>parskip</code> interferes with lists and the like,
+and the result looks pretty awful.  The <i>parskip</i> package
+patches things up to look reasonable; it&rsquo;s not perfect, but it deals
+with most problems.
+<p/>The Netherlands Users&rsquo; Group&rsquo;s set of classes includes an
+<i>article</i> equivalent (<i>artikel3</i>) and a <i>report</i>
+equivalent (<i>rapport3</i>) whose design incorporates zero paragraph
+indent and non-zero paragraph skip.
+<dl>
+<dt><tt><i>NTG classes</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntgclass/">browse</a>)
+<dt><tt><i>parskip.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/parskip.sty">macros/latex/contrib/misc/parskip.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html
new file mode 100644
index 00000000000..41ea39fc4c6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html
@@ -0,0 +1,97 @@
+<head>
+<title>UK TeX FAQ -- question label patch</title>
+</head><body>
+<h3>Patching existing commands</h3>
+<p/>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:
+<blockquote>
+<pre>
+\renewcommand{\splat}{\mumble\splat}
+</pre>
+</blockquote><p>
+However, this would not work: a call to <code>\</code><code>splat</code> would execute
+<code>\</code><code>mumble</code>, and the call the redefined <code>\</code><code>splat</code> again; this is an
+infinite recursive loop, that will quickly exhaust TeX&rsquo;s memory.
+<p/>Fortunately, the TeX primitive <code>\</code><code>let</code> command comes to our
+rescue; it allows us to take a &ldquo;snapshot&rdquo; of the current state of a
+command, which we can then use in the redefinition of the command.
+So:
+<blockquote>
+<pre>
+\let\OldSmooth\smooth
+\renewcommand{\smooth}{\mumble\OldSmooth}
+</pre>
+</blockquote><p>
+effects the required patch, safely.  Adding things at the end of a
+command works similarly.  If <code>\</code><code>smooth</code> takes arguments, one must
+pass them on:
+<blockquote>
+<pre>
+\renewcommand{\smooth}[2]{\mumble\OldSmooth{#1}{#2}}
+</pre>
+
+</blockquote><p>
+<p/>The general case may be achieved in two ways.  First, one can use the
+LaTeX command <code>\</code><code>CheckCommand</code>; this compares an existing command
+with the definition you give it, and issues a warning if two don&rsquo;t
+match.  Use is therefore:
+<blockquote>
+  <code>\CheckCommand{\complex}{</code>&lt;<i>original definition</i>&gt;<code>}</code><br>
+  <code>\renewcommand{\complex}{</code>&lt;<i>new definition</i>&gt;<code>}</code>
+</blockquote><p>
+This technique is obviously somewhat laborious, but if the original
+command comes from a source that&rsquo;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.
+<p/>Otherwise, LaTeX users may use one of the <i>patchcmd</i>,
+<i>ted</i> or <i>etoolbox</i> packages.
+<p/>The <i>patchcmd</i> package addresses a slightly simpler task, by
+restricting the set of commands that you may patch; you mayn&rsquo;t patch
+any command that has an optional argument, though it does deal with
+the case of commands defined with <code>\</code><code>DeclareRobustCommand</code>.  The
+package defines a <code>\</code><code>patchcommand</code> 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
+<blockquote>
+<pre>
+\def\b{b}
+\patchcmd\b{a}{c}
+</pre>
+</blockquote><p>
+we will have a new version of <code>\</code><code>b</code> defined as &ldquo;<code>abc</code>&rdquo;.
+<p/>The <i>ted</i> package is a &lsquo;token list editor&rsquo;, and provides a
+command <code>\</code><code>Substitute*</code> which will patch the contents of a macro,
+putting the result in a token-list, or (optionally) using the result
+to (re)define a macro.  The package may also be used as a powerful
+debugging tool.
+<p/>The <i>etoolbox</i> (which provides user access to e-TeX&rsquo;s
+programming facilities) provides a command <code>\</code><code>patchcmd</code> which will
+perform a &ldquo;string substitution&rdquo; in a macro&rsquo;s definition.  The
+package also provides commands that prepend (<code>\</code><code>pretocmd</code>) or append
+(<code>\</code><code>apptocmd</code>) to the definition of a command.
+<p/>Finally, we&rsquo;ll briefly consider a package that is (just about)
+usable, but not really recommendable.  <i>Patch</i> 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 (as in
+
+  <a href="FAQ-install-doc.html">generating documentation for a new package</a>).
+Fortunately, the file (<i>patch.doc</i>) may be input directly, and
+&ldquo;documentation&rdquo; may found by reading the source of the package.
+Roughly speaking, one gives the command a set of instructions
+analogous to <i>sed</i> substitutions, and it regenerates the
+command thus amended.  Unless you can&rsquo;t do your job any other way, you
+had probably best avoid <i>Patch</i>.
+<dl>
+<dt><tt><i>etoolbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/etoolbox.zip">macros/latex/contrib/etoolbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/etoolbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/etoolbox/">browse</a>)
+<dt><tt><i>patch.doc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/patch.doc">macros/generic/misc/patch.doc</a>
+<dt><tt><i>patchcommand.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.zip">macros/latex/contrib/patchcmd</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/patchcmd/">browse</a>)
+<dt><tt><i>ted.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ted.zip">macros/latex/contrib/ted</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ted.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ted/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html
new file mode 100644
index 00000000000..e217ac4db7f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html
@@ -0,0 +1,36 @@
+<head>
+<title>UK TeX FAQ -- question label pdfpagelabels</title>
+</head><body>
+<h3><i>Hyperref</i> and repeated page numbers</h3>
+<p/>The <i>book</i> 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 it confuses
+<i>hyperref</i> since there are pages which seem (to
+<i>hyperref</i>) to have the same page number.  Fortunately, there are
+configuration options to make <i>hyperref</i> &ldquo;do the right
+thing&rdquo;.
+<p/>The two options in question are:
+<dl>
+<dt><code>plainpages=false</code><dd> Make page anchors using the
+  formatted form of the page number.  With this option,
+  <i>hyperref</i> writes different anchors for pages &lsquo;ii&rsquo; and &lsquo;2&rsquo;.
+  (If the option is set &lsquo;<code>true</code>&rsquo; &mdash; the default &mdash;
+  <i>hyperref</i> writes page anchors as the arabic form of the
+  absolute page number, rather than the formatted form.)
+<dt><code>pdfpagelabels</code><dd> Set PDF page labels; i.e.,
+  write the value of <code>\</code><code>thepage</code> to the PDF file so that
+  <i>Acrobat Reader</i> can display the page number as (say) &lsquo;ii (4
+  of 40)&rsquo; rather than simply &lsquo;4 of 40&rsquo;.
+</dl>
+The two should be used whenever page numbering is not just
+&lsquo;1<code>..</code>n&rsquo;; they may be used independently, but usually are not.
+<p/>The recipe isn&rsquo;t perfect: it relies on <code>\</code><code>thepage</code> 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 &ldquo;<a href="FAQ-hyperdupdest.html">duplicate destinations</a>&rdquo;
+will happen in this case, regardless of the options.
+<dl>
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html
new file mode 100644
index 00000000000..a82acae3585
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html
@@ -0,0 +1,59 @@
+<head>
+<title>UK TeX FAQ -- question label pdftexgraphics</title>
+</head><body>
+<h3>Imported graphics in PDFLaTeX</h3>
+<p/>PDFTeX itself has a rather wide range of formats that it can
+&ldquo;natively&rdquo; incorporate into its output PDF stream:
+JPEG (<code>.jpg</code> files) for photographs and similar images,
+PNG files for artificial bitmap images, and PDF for
+vector drawings.  Old versions of PDFTeX (prior to version 1.10a)
+supported TIFF (<code>.tif</code> files) format as an alternative
+to PNG files; don&rsquo;t rely on this facility, even if you
+<em>are</em> running an old enough version of PDFTeX...
+<p/>In addition to the &lsquo;native&rsquo; formats, the standard PDFLaTeX
+<i>graphics</i> package setup causes Hans Hagen&rsquo;s <i>supp-pdf</i>
+macros to be loaded: these macros are capable of translating the
+output of MetaPost to PDF &ldquo;on the fly&rdquo;; thus MetaPost output
+(<code>.mps</code> files) may also be included in PDFLaTeX documents.
+<p/>The commonest problem users encounter, when switching from TeX, is
+that there is no straightforward way to include EPS files:
+since PDFTeX is its own &ldquo;driver&rdquo;, and since it contains no means
+of converting PostScript to PDF, there&rsquo;s no direct way the job can
+be done.
+<p/>The simple solution is to convert the EPS to an appropriate
+PDF file.  The <i>epstopdf</i> program will do this: it&rsquo;s
+available either as a Windows executable or as a <i>Perl</i>
+script to run on Unix and other similar systems.  A LaTeX package,
+<i>epstopdf</i>, can be used to generate the requisite PDF
+files &ldquo;on the fly&rdquo;; this is convenient, but requires that you
+suppress one of TeX&rsquo;s security checks: don&rsquo;t allow its use in files
+from sources you don&rsquo;t entirely trust.
+<p/>A similar package, <i>pst-pdf</i>, permits other things than &lsquo;mere&rsquo;
+graphics files in its argument.  <i>Pst-pdf</i> operates (the
+authors suggest) &ldquo;like BibTeX&rdquo; &mdash; you process your file using
+PDFLaTeX, then use LaTeX, <i>dvips</i> and <i>ps2pdf</i>
+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.)
+<p/>An alternative solution is to use <i>purifyeps</i>, a
+<i>Perl</i> script which uses the good offices of
+<i>pstoedit</i> and of MetaPost to convert your Encapsulated PostScript to
+&ldquo;Encapsulated PostScript that comes out of MetaPost&rdquo;, and can therefore be
+included directly.  Sadly, <i>purifyeps</i> doesn&rsquo;t work for all
+<code>.eps</code> files.
+<p/>Good coverage of the problem is to be found in Herbert Voss&rsquo;
+<a href="http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput">PDF support page</a>,
+which is targeted at the use of <i>pstricks</i> in
+PDFLaTeX, and also covers the <i>pstricks</i>-specific package
+<i>pdftricks</i>.
+<dl>
+<dt><tt><i>epstopdf</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/epstopdf/">support/epstopdf/</a>
+<dt><tt><i>epstopdf.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+<dt><tt><i>pdftricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse</a>)
+<dt><tt><i>pst-pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.zip">macros/latex/contrib/pst-pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf/">browse</a>)
+<dt><tt><i>pstoedit</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.zip">support/pstoedit</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pstoedit/">browse</a>)
+<dt><tt><i>purifyeps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.zip">support/purifyeps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/purifyeps/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pk.html
new file mode 100644
index 00000000000..e551d954dc3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pk.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label pk</title>
+</head><body>
+<h3>What are PK files?</h3>
+<p/>PK files (packed raster) contain font bitmaps.  The output
+from <a href="FAQ-useMF.html">Metafont</a> includes a generic font (GF) file
+and the utility <i>gftopk</i> produces the PK file from
+that.  There are a lot of PK files, as one is needed for each
+font, that is each magnification (size) of each design (point) size
+for each weight for each family.  Further, since the 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.  In a
+modern TeX distribution, files are arranged according to the TeX
+directory structure <a href="FAQ-tds.html">TDS</a>, which has provision for
+all this variety.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html
new file mode 100644
index 00000000000..71fcd491f40
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label pkfix</title>
+</head><body>
+<h3>Replacing Type 3 fonts in PostScript</h3>
+<p/>One often comes across a PostScript file generated by
+<i>dvips</i> which contains embedded PK fonts; if you try
+to generate PDF from such a file, the quality will be poor.
+<p/>Of course, the proper solution is to regenerate the PostScript file,
+but if neither the sources nor the DVI file are available, one
+must needs resort to some sort of patching to replace the bitmap fonts
+in the file by outline fonts.
+<p/>The program <i>pkfix</i> (by Heiko Oberdiek) will do this
+patching, for files created by &ldquo;not too old versions&rdquo; of
+<i>dvips</i>: it finds the fonts to be replaced by examining the
+PostScript comments <i>dvips</i> has put in the file.  For each
+font, <i>pkfix</i> puts appropriate TeX commands in a file,
+which it then processes and runs through <i>dvips</i> (with switch
+<code>-Ppdf</code>) to acquire an appropriate copy of the font; these copies are
+then patched back into the original file.
+<p/>If your source file is older than <i>pkfix</i> can deal with,
+there&rsquo;s still a modicum of hope: <i>pkfix-helper</i> examines the
+bitmap fonts in a document, compares them with the metric
+(<code>.tfm</code>) fonts on your system and comes to a view of which
+font might be which.  The program reports on &ldquo;poor&rdquo; matches, and
+there are options for confirming, or replacing, its guesses.  The
+technique (which sounds implausible) is successful enough to be worth
+a try.
+<p/>A further option is Frank Siegert&rsquo;s (shareware)
+<a href="http://www.pstill.com">PStill</a>, which is capable of processing
+the PostScript it is distilling, and one option is to replace bitmap fonts
+in the file with Type 1 versions.
+<dl>
+<dt><tt><i>pkfix</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pkfix.zip">support/pkfix</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pkfix.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pkfix/">browse</a>)
+<dt><tt><i>pkfix-helper</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pkfix-helper.zip">support/pkfix-helper</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pkfix-helper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pkfix-helper/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html
new file mode 100644
index 00000000000..31c10e1707f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html
@@ -0,0 +1,73 @@
+<head>
+<title>UK TeX FAQ -- question label pkgdoc</title>
+</head><body>
+<h3>Documentation of packages</h3>
+<p/>These FAQs regularly suggest packages that will &ldquo;solve&rdquo;
+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?
+<p/>If you&rsquo;re lucky, the package you need is already in your installation.
+If you&rsquo;re particularly lucky, you&rsquo;re using a distribution that gives
+access to package documentation and the documentation is available in
+a form that can easily be shown.  For example, on many current
+distributions, the <i>texdoc</i> command often helps, as in: 
+<blockquote>
+<pre>
+texdoc footmisc
+</pre>
+</blockquote><p>
+which opens a DVI viewer window showing documentation of the
+<i>footmisc</i> package.  According to the type of file
+<i>texdoc</i> finds, it will launch a DVI or PostScript viewer
+or a PDF reader.
+<p/>If <i>texdoc</i> can&rsquo;t find any documentation, it may launch a Web
+browser to look at its copy of the CTAN catalogue.  The
+catalogue has an entry for package documentation, and since the
+CTAN team asks authors documentation of their packages (and
+members of the team even occasionally generate documentation that
+seems useful), you will more often than not find documentation that
+way.
+<p/>If your luck (as defined above) doesn&rsquo;t hold out, you&rsquo;ve got to find
+documentation by other means.  This is where you need to exercise your
+intelligence: you have to find the documentation for yourself.  What
+follows offers a range of possible techniques.
+<p/>The commonest form of documentation of LaTeX add-ons is within the
+<code>.dtx</code> file in which the code is distributed (see
+<a href="FAQ-dtx.html">documented LaTeX sources</a>).  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
+<code>.dtx</code> file will <em>not</em> in fact process with LaTeX.  In the
+latter case, the <code>.ins</code> file will usually produce a
+<code>.drv</code> (or similarly-named) file, which you process with
+LaTeX instead.  (Sometimes the package author even thinks to
+mention this wrinkle in a package <code>README</code> file.)
+<p/>Another common form is the separate documentation file; particularly
+if a package is &ldquo;conceptually large&rdquo; (and therefore needs a lot of
+documentation), the documentation would prove a cumbersome extension
+to the <code>.dtx</code> file.  Examples of such cases are the <i>memoir</i>
+class (whose documentation, <i>memman</i>, is widely praised as an
+introduction to typesetting concepts), the <i>KOMA-script</i> bundle
+(whose developers take the trouble to produce detailed documentation
+in both German and English), and the <i>fancyhdr</i> package (whose
+documentation derives from a definitive tutorial in a mathematical
+journal).  Even if the documentation is not separately identified in a
+<code>README</code> file, it should not be too difficult to recognise its
+existence.
+<p/>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
+<code>\</code><code>endinput</code> command in the package.  (This is desirable, since
+<code>\</code><code>endinput</code> is a &lsquo;logical&rsquo; end-of-file, and (La)TeX doesn&rsquo;t read
+beyond it: thus such documentation does not &lsquo;cost&rsquo; any package loading time.)
+<p/>The above suggestions cover most possible ways of finding
+documentation.  If, despite your best efforts, you can&rsquo;t find
+it in any of the above places, there&rsquo;s the awful possibility that the
+author didn&rsquo;t bother to document his package (on the &ldquo;if it was hard
+to write, it should be hard to use&rdquo; philosophy).  Most ordinary
+mortals will seek support from some more experienced user at this
+stage, though it <em>is</em> possible to proceed in the way that the original
+author apparently expected...by reading his code.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
new file mode 100644
index 00000000000..ee2ed09f399
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label plainvltx</title>
+</head><body>
+<h3>Should I use Plain TeX or LaTeX?</h3>
+<p/>There&rsquo;s no straightforward answer to this question.  Many people swear
+by Plain TeX, 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
+brain power.
+<p/>The arguments around this topic can provoke huge amounts of noise and
+heat, without offering much by way of light; your best bet is to find
+out what those around you are using, and to go with the crowd.  Later
+on, you can always switch your allegiance; don&rsquo;t bother about it.
+<p/>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
+(La)TeX styles for journals and books, and insist that authors stick
+closely to their markup.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html
new file mode 100644
index 00000000000..d99a905e43c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label plninltx*</title>
+</head><body>
+<h3>Using Plain or primitive commands in LaTeX</h3>
+<p/>It&rsquo;s well-known that LaTeX commands tend to be more complex, and to
+run more slowly than, any Plain TeX (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
+Plain TeX version.  So, for example, use <code>\</code><code>mbox</code> in place of <code>\</code><code>hbox</code>
+unless you know that the extras that LaTeX provides in <code>\</code><code>mbox</code>
+would cause trouble in your application.  Similarly, use
+<code>\</code><code>newcommand</code> (or one of its relatives) unless you need one of the
+constructs that cannot be achieved without the use of <code>\</code><code>def</code> (or friends).
+<p/>As a general rule, any LaTeX text command will start a new
+paragraph if necessary; this isn&rsquo;t the case with Plain TeX
+commands, a fact which has a potential to confuse.
+<p/>The commands <code>\</code><code>smallskip</code>, <code>\</code><code>medskip</code> and <code>\</code><code>bigskip</code> exist both
+in Plain TeX and LaTeX, but behave slightly differently: in
+Plain TeX they terminate the current paragraph, but in LaTeX they 
+don&rsquo;t.  The command <code>\</code><code>line</code> is part of picture mode in LaTeX,
+whereas it&rsquo;s defined as &ldquo;<code>\</code><code>hbox</code><code> to </code><code>\</code><code>hsize</code>&rdquo; in
+Plain TeX. (There&rsquo;s no equivalent for users of the Plain TeX command in
+LaTeX: an equivalent appears as the internal command <code>\</code><code>@@line</code>).
+<p/>Maths setting shows a case where the LaTeX version <em>is</em>
+essentially equivalent to the TeX primitive commands: the LaTeX
+<code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code> does essentially no different to the
+TeX <code>$ ... $</code>
+(except for checking that you&rsquo;re not attempting to open a maths
+environment when you&rsquo;re already in one, or vice versa).  
+However, <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> <em>isn&rsquo;t</em> the same as 
+<code>$$ ... $$</code>: the TeX version, used
+in LaTeX, can miss the effect of the class option <code>fleqn</code>.
+<p/>Font handling is, of course, wildly different in Plain TeX and
+LaTeX.  Plain TeX&rsquo;s font loading command
+(<code>\</code><code>font</code><code>\</code><code>foo=</code>&lt;<i>fontname</i>&gt;) and its LaTeX equivalent
+(<code>\</code><code>newfont</code>) 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 &ldquo;<a href="FAQ-newfontstar.html">What&rsquo;s wrong with <code>\</code><code>newfont</code>?</a>&rdquo;.
+
+
+
+
+
+
+
+
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html
new file mode 100644
index 00000000000..f94e4158f41
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label poster</title>
+</head><body>
+<h3>Creating posters with LaTeX</h3>
+<p/>There is no complete &ldquo;canned solution&rdquo; to creating a poster (as, for
+example, classes like <i>seminar</i>, <i>powerdot</i> and
+<i>beamer</i> serve for creating presentations in a variety of
+styles).
+<p/>The nearest approach to the complete solution is the <i>sciposter</i>
+class, which provides the means to produce really rather good posters
+according to the author&rsquo;s required style.  A complete worked example
+is provided with the distribution
+<p/>Otherwise, there is a range of tools, most of which are based on the
+<i>a0poster</i> class, which sets up an appropriately-sized piece of
+paper, sets font sizes appropriately, and leaves you to your own
+devices.
+<p/>Having used <i>a0poster</i>, you can of course slog it out, and write
+all your poster as an unadorned LaTeX document (presumably in
+multiple columns, using the <i>multicol</i> package), but it&rsquo;s not really
+necessary: the (straightforward) <i>textpos</i> package provides a
+simple way of positioning chunks of text, or tables or figures, on the
+poster page.
+<p/>More sophisticated is the <i>flowfram</i> package, whose basic aim
+in life is flowing text from one box on the page to the next.  One of
+the package&rsquo;s design aims seems to have been the production of
+posters, and a worked example is provided.  The author of
+<i>flowfram</i> has an experimental tool called
+<a href="http://theoval.cmp.uea.ac.uk/~nlct/jpgfdraw/">JpgfDraw</a>, which
+allows you to construct the outline of frames for use with
+<i>flowfram</i>.
+<p/>Despite the relative shortage of tools, there are a fair few web pages
+that explain the process (mostly in terms of the <i>a0poster</i>
+route):
+<ul>
+<li> from Norman Gray,
+  <a href="http://nxg.me.uk/docs/posters/">Producing posters using LaTeX</a>;
+<li> from Nicola Talbot, 
+  <a href="http://theoval.sys.uea.ac.uk/~nlct/latex/posters/index.html">Creating technical posters with LaTeX</a>
+<li> from &ldquo;<em>awf</em>&rdquo; and &ldquo;<em>capes</em>&rdquo; 
+  <a href="http://www.robots.ox.ac.uk/~awf/latex-posters/">Preparing conference posters in LaTeX</a>
+  (the page discusses a sample, which you can download);
+<li> From Rob Clark 
+  <a href="http://homepages.inf.ed.ac.uk/robert/posters/advanced.html">Advanced LaTeX Posters</a>
+  (which has links to code samples);
+<li> from Brian Wolven,
+  <a href="http://fuse.pha.jhu.edu/~wolven/posters.html">http://fuse.pha.jhu.edu/~wolven/posters.html</a> (this page also
+  provides macros and other support suggestions); and
+<li> from &ldquo;<em>pjh</em>&rdquo; 
+  <a href="http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html">Making and printing a poster with LaTeX</a>,
+  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.
+</ul>
+<dl>
+<dt><tt><i>a0poster.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/a0poster.zip">macros/latex/contrib/a0poster</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/a0poster.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/a0poster/">browse</a>)
+<dt><tt><i>flowfram.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/flowfram.zip">macros/latex/contrib/flowfram</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/flowfram.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/flowfram/">browse</a>)
+<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>sciposter.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.zip">macros/latex/contrib/sciposter</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sciposter/">browse</a>)
+<dt><tt><i>textpos.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html
new file mode 100644
index 00000000000..0c06f0651b0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html
@@ -0,0 +1,56 @@
+<head>
+<title>UK TeX FAQ -- question label prept1font</title>
+</head><body>
+<h3>Preparing a Type 1 font</h3>
+<p/>The process of installing a Type 1 font set is rather convoluted, but
+it may be separated into a modest set of operations.
+<p/>The two basic stages are to prepare the font(s) for installation (this
+question) and installing the result (see 
+<a href="FAQ-instt1font.html">installing a Type 1 font</a>).  Each of
+these basic stages
+<p/>Many fonts are supplied in (La)TeX ready form: such fonts need no
+preparation, and may be <a href="FAQ-instt1font.html">installed immediately</a>.
+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 &lsquo;prepare&rsquo; it for
+use with (La)TeX.  The rest of this answer discusses this preparation.
+<ul>
+<li> Acquire the font.  A very small set of Type 1 fonts is installed
+  in most PostScript printers you will encounter.  For those few (whose use
+  is covered by the basic PSNFSS package), you don&rsquo;t need the
+  Type 1 font itself, to be able to print using the font.
+<p/>  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&rsquo;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.
+<li> Acquire the fonts&rsquo; AFM files.  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 AFM files by
+  default: if the files are not available, you are unlikely to be able
+  to use the font with (La)TeX.
+<li> Rename the AFM files and the Type 1 files to match the
+  <a href="FAQ-fontname.html">Berry font naming scheme</a>.
+<li> Generate TeX metric files from the AFM files.  The
+  commonest tool for this task is <i>fontinst</i>; the package
+  documentation helps, but other guides are available (see below).
+  The simplest possible script to pass to <i>fontinst</i> is:
+  <blockquote>
+<pre>
+\latinfamily{xyz}{}
+\bye
+</pre>
+  </blockquote><p>
+  where <code>xyz</code> is the Berry name of the font family.  This
+  simple script is adequate for most purposes: its output covers the
+  font family in both T1 and OT1 font encodings.  Nevertheless,
+  with fancier fonts, more elaborate things are possible with
+  <i>fontinst</i>: see its documentation for details.
+<p/>  <i>Fontinst</i> also generates map files, and LaTeX font
+  definition (<code>.fd</code>) files.
+</ul>
+Having traversed this list, you have a set of font files ready for
+installation.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prept1font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prept1font</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html
new file mode 100644
index 00000000000..85f53efa309
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label previewers</title>
+</head><body>
+<h3>DVI previewers</h3>
+<p/>EmTeX for PCs running MSDOS or OS/2, MiKTeX and
+XEmTeX for PCs running Windows and OzTeX for the Macintosh, all
+come with previewers that can be used on those platforms. EmTeX&rsquo;s
+previewer can also be run under Windows 3.1.
+<p/>Commercial PC TeX packages (see 
+<a href="FAQ-commercial.html">commercial vendors</a>)
+have good previewers for PCs running Windows, or for Macintoshes.
+<p/>For Unix systems, there is one &lsquo;canonical&rsquo; viewer, <i>xdvi</i>.
+<i>Xdvik</i> is a version of <i>xdvi</i> using the
+<i>web2c</i> libraries; it is now built from the same distribution
+as <i>xdvi</i>.  The TeX Live distributions for Unix systems
+include a version of <i>xdvik</i>.
+<p/>Alternatives to previewing include
+<ul>
+<li> conversion to &lsquo;similar&rsquo; ASCII text (see
+  <a href="FAQ-toascii.html">converting to ASCII</a>) and using a
+  conventional text viewer to look at that,
+<li> generating a PostScript version of your document and viewing it
+  with a <i>Ghostscript</i>-based previewer (see
+  <a href="FAQ-PSpreview.html">previewing PostScript files</a>), and
+<li> generating  PDF output, and viewing that with
+  <i>Acrobat</i> <i>Reader</i> or one of the substitutes for that.
+</ul>
+<dl>
+<dt><tt><i>xdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.zip">dviware/xdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/xdvi/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html
new file mode 100644
index 00000000000..b3cd65cb41c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html
@@ -0,0 +1,24 @@
+<head>
+<title>UK TeX FAQ -- question label prinvalint</title>
+</head><body>
+<h3>The Principal Value Integral symbol</h3>
+<p/>This symbol (an integral sign, &lsquo;crossed&rsquo;) does not appear in any of
+the fonts ordinarily available to (La)TeX users, but it can be
+created by use of the following macros:
+<pre>
+\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-}
+</pre>
+
+<code>\</code><code>dashint</code> gives a single-dashed integral sign, <code>\</code><code>ddashint</code> a
+double-dashed one.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html
new file mode 100644
index 00000000000..3cbdc3ec470
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html
@@ -0,0 +1,122 @@
+<head>
+<title>UK TeX FAQ -- question label privinst</title>
+</head><body>
+<h3>&ldquo;Private&rdquo; installations of files</h3>
+<p/>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&rsquo;s
+unwilling to update and won&rsquo;t give you privileges to do the job
+yourself.  A <a href="FAQ-tempinst.html">&ldquo;temporary&rdquo; installation</a> is
+sometimes the correct approach, but if there&rsquo;s the slightest chance
+that the installation will be needed on more than one project,
+temporary installations aren&rsquo;t right.
+<p/>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 (La)TeX which includes the new stuff you
+need; this is the ideal, but is not generally possible.
+<p/>So, since you can&rsquo;t install into the public <code>texmf</code> tree, you
+have to install into a <i>texmf</i> tree of your own; fortunately, the
+TDS standard allows for this, and modern distributions allow
+you to do it.  The most modern distributions refer to the tree as
+<code>$TEXMFHOME</code>, but it used to be called <code>$HOMETEXMF</code>;
+so to check that your TeX system does indeed support the mechanism
+you should start with
+<pre>
+kpsewhich -expand-var "\$TEXMFHOME"
+</pre>
+<p/>If you can confirm that the technique does indeed work, install your
+new package (or whatever) in the <a href="FAQ-install-where.html">correct place</a>
+in a tree based on <i>$HOME/texmf</i>, and generate an index of that
+tree
+<blockquote>
+<pre>
+texhash $HOME/texmf
+</pre>
+</blockquote><p>
+(the argument specifies which tree you are indexing: it&rsquo;s necessary
+since you don&rsquo;t, by hypothesis, have access to the main tree, and
+<i>texhash</i> without the argument would try to write the main
+tree.
+<p/>There are two wrinkles to this simple formula: first, the installation
+you&rsquo;re using may <em>not</em> define a home TEXMF directory, and second,
+there may be some obstruction to using <i>$HOME/texmf</i> as the
+default name.  In either case, a good solution is to have your own
+<i>texmf.cnf</i> &mdash; an idea that sounds more frightening that it
+actually is.  The installation&rsquo;s existing file may be located with the
+command:
+<blockquote>
+<pre>
+kpsewhich texmf.cnf
+</pre>
+</blockquote><p>
+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 <i>web2c</i>
+directory of the tree you want to create, i.e.,
+<i>$HOME/texmf/web2c</i> or the like.  Make an environment variable to
+point to this directory:
+<blockquote>
+<pre>
+TEXMFCNF=$HOME/texmf/web2c
+export TEXMFCNF
+</pre>
+</blockquote><p>
+(for a Bourne shell style system), or
+<blockquote>
+<pre>
+setenv TEXMFCNF $HOME/texmf/web2c
+</pre>
+</blockquote><p>
+(for a C-shell style system).  Now edit the copy of <i>texmf.cnf</i>
+<p/>There will be a line in the existing file that defines the tree where
+everything searches; the simplest form of the line is:
+<blockquote>
+<pre>
+TEXMF = !!$TEXMFMAIN
+</pre>
+</blockquote><p>
+but, there are likely to be several alternative settings behind
+comment markers (&ldquo;<code>%</code>&rdquo;), and the person who 
+installed your system may have left them there.  Whatever, you need to
+modify the line that&rsquo;s in effect: change the above to three lines:
+<blockquote>
+<pre>
+HOMETEXMF = $HOME/texmf
+TEXMF = {$HOMETEXMF,!!$TEXMFMAIN}
+% TEXMF = !!$TEXMFMAIN
+</pre>
+</blockquote><p>
+the important point being that <code>$HOMETEXMF</code> must come before
+whatever was there before, inside the braces.  For example, if the
+original was
+<blockquote>
+<pre>
+TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
+</pre>
+</blockquote><p>
+it should be converted to:
+<blockquote>
+
+<pre>
+HOMETEXMF = $HOME/texmf
+TEXMF = {$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
+% TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN}
+</pre>
+</blockquote><p>
+(retaining the original, as a comment, is merely an aide-memoir in
+case you need to make another change, later).  The <code>!!</code> signs
+tell the file-searching library that it should insist on a
+<i>texhash</i>-ed directory tree; if you can count on yourself
+remembering to run <i>texhash</i> on your new tree every time you
+change it, then it&rsquo;s worth adding the marks to your tree:
+<blockquote>
+
+<pre>
+TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN}
+</pre>
+</blockquote><p>
+as this will make (La)TeX find its files marginally faster.
+<p/>Having made all these changes, (La)TeX should &ldquo;just use&rdquo; files in
+your new tree, in preference to anything in the main tree &mdash; you can
+use it for updates to packages in the main tree, as well as for
+installing new versions of things.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html
new file mode 100644
index 00000000000..fcd2ef09876
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label proof</title>
+</head><body>
+<h3>Proof environment</h3>
+<p/>It has long been thought impossible to make a <code>proof</code>
+environment which automatically includes an &lsquo;end-of-proof&rsquo; symbol.
+Some proofs end in displayed maths; others do not.  If the input file
+contains
+
+<code>...<code>\</code><code>]</code> </code><code>\</code><code>end{proof}</code> 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 <em>can</em> insert the symbol by hand, but the
+<i>ntheorem</i> package now solves the problem for LaTeX users:
+it does indeed provide an automatic way of signalling the end of a
+proof.
+<p/>The AMSLaTeX package <i>amsthm</i> also provides a
+<code>proof</code> environment that does the job; though you need to
+insert a <code>\</code><code>qedhere</code> command if the proof ends with a displayed
+equation:
+<blockquote>
+<pre>
+\begin{proof}
+  text...
+  \begin{equation*}
+    maths... \tag*{\qedhere}
+  \end{equation*}
+\end{proof}
+</pre>
+</blockquote><p>
+The <code>\</code><code>tag*{<code>\</code><code>qedhere</code>}</code> construction may be used in any of
+AMSLaTeX&rsquo;s numbering environments.
+<dl>
+<dt><tt><i>amsthm.sty</i></tt><dd>Distributed as part of the AMSLaTeX bundle
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>ntheorem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html
new file mode 100644
index 00000000000..dd0389f9118
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html
@@ -0,0 +1,85 @@
+<head>
+<title>UK TeX FAQ -- question label protect</title>
+</head><body>
+<h3>What&rsquo;s the reason for &lsquo;protection&rsquo;?</h3>
+<p/>Sometimes LaTeX saves data it will reread later. These data are
+often the argument of some command; they are the so-called moving
+arguments.  (&lsquo;Moving&rsquo; because data are moved around.)  Candidates
+are all arguments that may go into table of contents, list of figures,
+<em>etc</em>.; 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&rsquo;s a complete list in Lamport&rsquo;s book
+(see <a href="FAQ-books.html">TeX-related books</a>).
+<p/>What&rsquo;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
+&ldquo;<code>\</code><code>protect</code><code>\</code><code>cmd</code>&rdquo; tells LaTeX to save <code>\</code><code>cmd</code> as
+<code>\</code><code>cmd</code>, without expanding it at all.
+<p/>So, what is a &lsquo;fragile command&rsquo;? &mdash; it&rsquo;s a command that expands into
+illegal TeX code during the save process.
+<p/>What is a &lsquo;robust command&rsquo;? &mdash; it&rsquo;s a command that expands into legal
+TeX code during the save process.
+<p/>Lamport&rsquo;s book says in its description of every LaTeX command whether
+it is &lsquo;robust&rsquo; or &lsquo;fragile&rsquo;; it also says that every command with an
+optional argument is fragile.  The list isn&rsquo;t reliable, and neither
+is the assertion about optional arguments; the statements may have
+been true in early versions of LaTeX2e but are not any longer
+necessarily so:
+<ul>
+<li> Some fragile commands, such as <code>\</code><code>cite</code>, have been made robust
+  in later revisions of LaTeX.
+<li> Some commands, such as <code>\</code><code>end</code> and <code>\</code><code>nocite</code>, are fragile
+  even though they have no optional arguments.
+<li> The &ldquo;user&rsquo;s way&rdquo; of creating a command with an optional
+  argument (using <code>\</code><code>newcommand</code> or <code>\</code><code>newcommand*</code>) now always
+  creates a robust command (though macros without optional arguments
+  may still be fragile if they do things that are themselves fragile).
+<li> There is no reason that a package author should not also make
+  robust commands with optional arguments as part of the package.
+<li> Some robust commands are redefined by certain packages to be
+  fragile (the <code>\</code><code>cite</code> command commonly suffers this treatment).
+</ul>
+Further, simply &ldquo;hiding&rdquo; a fragile command in another command, has
+no effect on fragility.  So, if <code>\</code><code>fred</code> is fragile, and you write:
+<blockquote>
+<pre>
+\newcommand{\jim}{\fred}
+</pre>
+</blockquote><p>
+then <code>\</code><code>jim</code> is fragile too.  There is, however, the
+<code>\</code><code>newcommand</code>-replacement <code>\</code><code>DeclareRobustCommand</code>, which
+<em>always</em> creates a robust command (whether or not it has optional
+arguments).  The syntax of <code>\</code><code>DeclareRobustCommand</code> is substantially
+identical to that of <code>\</code><code>newcommand</code>, and if you do the wrapping
+trick above as:
+<blockquote>
+<pre>
+\DeclareRobustCommand{\jim}{\fred}
+</pre>
+</blockquote><p>
+then <code>\</code><code>jim</code> is robust.
+<p/>Finally, we have the <i>makerobust</i> package, which  defines
+<code>\</code><code>MakeRobustCommand</code> to convert a command to be robust.  With the
+package, the &ldquo;wrapping&rdquo; above can simply be replaced by:
+<blockquote>
+<pre>
+\MakeRobustCommand\fred
+</pre>
+</blockquote><p>
+Whereafter, <code>\</code><code>fred</code> is robust.  Using the package may be reasonable
+if you have lots of fragile commands that you need to use in moving
+arguments.
+<p/>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 <code>\</code><code>protect</code>ion.
+<dl>
+<dt><tt><i>makerobust.sty</i></tt><dd>Distributed with Heiko Oberdiek&rsquo;s packages
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psatempty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psatempty.html
new file mode 100644
index 00000000000..36d2b34284b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psatempty.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label ps@empty</title>
+</head><body>
+<h3><code>\pagestyle{empty}</code> on first page in LaTeX</h3>
+<p/>If you use <code>\</code><code>pagestyle{empty}</code>, but the first page is numbered
+anyway, you are probably using the <code>\</code><code>maketitle</code> command too. The
+behaviour is not a bug but a feature.  The standard LaTeX classes are
+written so that initial pages (pages containing a <code>\</code><code>maketitle</code>,
+<code>\</code><code>part</code>, or <code>\</code><code>chapter</code>) have a different page style from the rest
+of the document; to achieve this, the commands internally issue
+<code>\</code><code>thispagestyle{plain}</code>. This is usually not acceptable
+behaviour if the surrounding page style is &lsquo;empty&rsquo;.
+<p/>Possible workarounds include:
+<ul>
+<li> Put <code>\</code><code>thispagestyle{empty</code>} immediately after the
+  <code>\</code><code>maketitle</code> command, with no blank line between them.
+<li> Use the <i>fancyhdr</i> or <i>scrpage2</i> packages, which
+  allow you to customise the style for initial pages independently of
+  that for body pages.
+<p/>  For example, use <i>fancyhdr</i> commands:
+<pre>
+\fancypagestyle{plain}{%
+  \fancyhf{}%
+  \renewcommand{\headrulewidth}{0pt}%
+  \renewcommand{\footrulewidth}{0pt}%
+}
+</pre>
+  and the &ldquo;<code>empty</code>&rdquo; page style (invoked by <code>\</code><code>chapter</code>
+  commands and title pages) will have no header or footer.
+<li> If you are using either the <i>memoir</i> class or a
+  <i>KOMA-script</i> class, use the techniques outlined for them in
+  &ldquo;<a href="FAQ-nopageno.html">no page numbers</a>&rdquo;.
+</ul>
+<dl>
+<dt><tt><i>fancyhdr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>nopageno.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle/nopageno.sty">macros/latex/contrib/carlisle/nopageno.sty</a>
+<dt><tt><i>scrpage2.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html
new file mode 100644
index 00000000000..290f4b4e55c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html
@@ -0,0 +1,410 @@
+<head>
+<title>UK TeX FAQ -- question label psfchoice</title>
+</head><body>
+<h3>Choice of scalable outline fonts</h3>
+<p/>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 <em>only</em>
+cares about metrics, not the actual character programs).
+<p/>If you also need mathematics, then you are severely limited by the
+demands that TeX makes of maths fonts (for details, see the papers
+by
+
+  <a href="http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf">B.K.P. Horn in <i>TUGboat</i> 14(3)</a>,
+  or by 
+  <a href="http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf">Thierry Bouche in <i>TUGboat</i> 19(2)</a>).
+
+For mathematics, then, there are relatively few choices (though the list is
+at last growing).  There are several font families available that are
+based on Knuth&rsquo;s original designs, and some that complement other
+commercial text font designs; one set (MicroPress&rsquo;s &lsquo;informal math&rsquo;)
+stands alone.  &ldquo;Free&rdquo; font families that will support TeX
+mathematics include:
+<dl>
+<dt>Computer Modern<dd>(75 fonts &mdash; optical scaling) Donald E. Knuth<br>
+  The CM fonts were originally designed in Metafont, 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 Y&amp;Y and Blue Sky Research;
+  they have since assigned the copyright to the AMS, and the
+  fonts are now freely available from CTAN.  Their quality is
+  such that they have become the <em>de facto</em> standard for Type 1
+  versions of the fonts.
+<dt>AMS fonts<dd>(52 fonts, optical scaling) The AMS<br>
+  This set of fonts offers adjuncts to the CM set, including
+  two sets of symbol fonts (<i>msam</i> and <i>msbm</i>) 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
+  CTAN.  The <i>eulervm</i> 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).
+<dt>mathpazo version 1.003<dd>(5 fonts) Diego Puga<br>
+  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 &ldquo;blackboard bold&rdquo;
+  characters (chosen for their mathematical significance).  Support
+  under LaTeX2e is available in 
+  <a href="FAQ-usepsfont.html">PSNFSS</a>; the fonts are
+  licensed under the GPL, with legalese permitting the use of
+  the fonts in published documents.
+<dt>Fourier/Utopia<dd>(15 fonts) Michel Bovani<br>
+  <i>Fourier</i> is a family built on Adobe <i>Utopia</i>
+  (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 AMS mathematical symbols (though you are
+  expected to use some from the AMS fonts themselves).  There
+  are also several other mathematical and decorative symbols.  The
+  fonts come with a <i>fourier</i> package for use with LaTeX;
+  text support of OT1 encoding is not provided &mdash; you are
+  expected to use T1.
+<p/>  For a sample, see \url{http://www.tug.dk/FontCatalogue/utopia/}
+<dt>Fourier/New Century Schoolbook<dd>Michael Zedler<br>
+  <i>Fouriernc</i> is a configuration using the Fourier fonts in
+  the context of New Century Schoolbook text fonts.
+<p/>  For a sample, see \url{http://www.tug.dk/FontCatalogue/newcent/}
+<dt>KP-fonts<dd>The Johannes Kepler project<br>
+  The <i>kp-fonts</i> 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&rsquo;
+  <i>kpfonts</i> LaTeX support package).
+<p/>  For an example, see \url{http://www.tug.dk/FontCatalogue/kpserif/}
+<dt>MathDesign<dd>(4 entire families...so far) Paul Pichaureau<br>
+  This set so far offers mathematics fonts to match Adobe Utopia, URW
+  Garamond, Bitstream Charter (all of which are separately available,
+  on CTAN, in Type 1 format) and Fontsite Garamond
+  (which is a commercial font, available from the 
+  <a href="FontSite Web shop">http://www.fontsite.com/Pages/FFDownloads.html</a>).
+
+  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 CTAN directory and see which you
+  want: there is a wealth of documentation and examples.
+<p/>  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.
+<dt>Belleek<dd>(3 fonts) Richard Kinch<br>
+  Belleek is the upshot of Kinch&rsquo;s thoughts on how Metafont might be used
+  in the future: they were published simultaneously as Metafont source,
+  as Type 1 fonts, and as TrueType fonts.  The fonts act as &ldquo;drop-in&rdquo;
+  replacements for the basic MathTime set (as an example of &ldquo;what might
+  be done&rdquo;).
+<p/>  The paper outlining Kinch&rsquo;s thoughts, proceeding from considerations
+  of the &lsquo;intellectual&rsquo; superiority of Metafont to evaluations of why its
+  adoption is so limited and what might be done about the problem, is
+  to be found at <a href="http://truetex.com/belleek.pdf">http://truetex.com/belleek.pdf</a> (the paper is a
+  good read, but is set with Bitmap fonts, and can be difficult
+  on-screen in Acrobat reader 5 or earlier).
+<dt>mathptmx<dd>Alan Jeffrey, Walter Schmidt and others.<br>
+  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
+  PostScript files can be freely exchanged.  Support under LaTeX2e
+  is available in <a href="FAQ-usepsfont.html">PSNFSS</a>.
+<p/>  For a sample, see \url{http://www.tug.dk/FontCatalogue/times/}
+<dt>Computer Modern Bright<dd>Free scalable outline versions of these
+  fonts do exist; they are covered below together with their
+  commercial parallels.
+</dl>
+The excellent <em>font catalogue</em> keeps an 
+<a href="http://www.tug.dk/FontCatalogue/mathfonts.html">up-to-date list</a>
+which describes the fonts by giving names and short examples, only.
+(At the time of writing &mdash; June 2008 &mdash; the list has several that
+are only scheduled for inclusion here.
+<p/>Another useful document is Stephen Hartke&rsquo;s &ldquo;Free maths font
+survey&rdquo;, which is available on CTAN in both PDF and
+HTML formats.  The survey covers most of the fonts mentioned in
+the font catalogue, but also mentions some (such as <i>Belleek</i>
+that the catalogue omits.
+<p/>Fonts capable of setting TeX mathematics, that are available
+commercially, include:
+<dl>
+<dt>BA Math<dd>(13 fonts) MicroPress Inc.<br>
+  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 OT1 and T1
+  encoded text fonts of various shapes, as well as fonts with most
+  useful glyphs of the TS1 encoding.  Macros for using the
+  fonts with Plain TeX, LaTeX 2.09 and current LaTeX are
+  provided.
+<p/>  
+  For further details (including samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/bamath/bamain.htm">http://www.micropress-inc.com/fonts/bamath/bamain.htm</a>
+  
+<dt>CH Math<dd>(15 fonts) MicroPress Inc.<br>
+  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.)
+  
+  For further details (including samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/chmath/chmain.htm">http://www.micropress-inc.com/fonts/chmath/chmain.htm</a>
+  
+<dt>Computer Modern Bright<dd>(62 fonts &mdash; optical scaling) Walter
+  Schmidt<br>
+  CM Bright is a family of sans serif fonts, based on Knuth&rsquo;s
+  CM fonts.  It comprises the fonts necessary for mathematical
+  typesetting, including 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 CM Bright fonts are
+  supplied in Type 1 format by MicroPress, Inc.   The
+  <i>hfbright</i> bundle offers free Type 1 fonts for text using
+  the OT1 encoding &mdash; the <i>cm-super</i> set for
+  use with T1 texts doesn&rsquo;t (yet) offer support for mathematics.
+<p/>  
+  For further details of Micropress&rsquo; offering (including samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/brmath/brmain.htm">http://www.micropress-inc.com/fonts/brmath/brmain.htm</a>
+  
+<dt>Concrete Math<dd>(25 fonts &mdash; optical scaling) Ulrik Vieth<br>
+  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
+  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 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.
+<p/>  
+  For further information (including samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/ccmath/ccmain.htm">http://www.micropress-inc.com/fonts/ccmath/ccmain.htm</a>
+  
+<dt>HV Math<dd>(14 fonts) MicroPress Inc.<br>
+  HV Math is a family of sans serif fonts, inspired by the
+  Helvetica (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 OT1 and T1 encoded text fonts of various
+  shapes, as well as fonts with most useful glyphs of the TS1
+  encoding.  Macros for using the fonts with Plain TeX, LaTeX 2.09
+  and current LaTeX are provided.  Bitmapped copies of the fonts
+  are available free, on CTAN.
+<p/>  
+  For further details (and samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/hvmath/hvmain.htm">http://www.micropress-inc.com/fonts/hvmath/hvmain.htm</a>
+  
+<dt>Informal Math<dd>(7 outline fonts) MicroPress Inc.<br>
+  Informal Math is a family of fanciful fonts loosely based on the
+  Adobe&rsquo;s Tekton (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 OT1 encoded text fonts in
+  upright and oblique shapes.  Macros for using the fonts with
+  Plain TeX, LaTeX 2.09 and current LaTeX are provided.
+<p/>  
+  For further details (including samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/ifmath/ifmain.htm">http://www.micropress-inc.com/fonts/ifmath/ifmain.htm</a>
+  
+<dt>Lucida Bright <em>with</em> Lucida New Math<dd>(25 fonts) Chuck Bigelow and
+  Kris Holmes<br>
+  Lucida is a family of related fonts including seriffed, sans serif,
+  sans serif fixed width, calligraphic, blackletter, fax, Kris Holmes&rsquo;
+  connected handwriting font, <em>etc</em>; they&rsquo;re not as &lsquo;spindly&rsquo; as
+  Computer Modern, with a large x-height, and include a larger set of
+  maths symbols, operators, relations and delimiters than CM
+  (over 800 instead of 384: among others, it also includes the
+  AMS <i>msam</i> and <i>msbm</i> symbol sets).  &lsquo;Lucida
+  Bright Expert&rsquo; 
+  (14 fonts) adds seriffed fixed width, another handwriting font,
+  smallcaps, bold maths, upright &lsquo;maths italic&rsquo;, <em>etc</em>., to the
+  set.  Support under LaTeX is available under the auspices of the
+  PSNFSS, and pre-built metrics are also provided.
+<p/>  
+  TUG has the right to distribute these fonts; the web site
+
+    &ldquo;<a href="http://tug.org/lucida/">Lucida and TUG</a>&rdquo;
+  has details.
+  
+<dt>Adobe Lucida, LucidaSans <em>and</em> LucidaMath<dd>(12 fonts)<br>
+  Lucida and LucidaMath are generally considered to be a bit heavy.
+  The three maths fonts contain only the glyphs in the 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 <em>etc</em>.  (In some sense this set is the
+  ancestor of the LucidaBright plus LucidaNewMath font set, which are
+  not currently available.)
+<dt>MathTime Pro2<dd>Publish or Perish (Michael Spivak)<br>
+  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 Plain TeX and LaTeX2e, and
+  are exclusively available for purchase from
+  <a href="FAQ-commercial.html">Personal TeX Inc</a>.
+  par
+  
+  For further details and samples and fliers, see
+  <a href="http://www.pctex.com/mtpro2.html">http://www.pctex.com/mtpro2.html</a>
+  
+<dt>Minion Pro and MnSymbol<dd>Adobe, LaTeX support and packaging by
+  Achim Blumensath <em>et al</em>.<br>
+  <i>Minion Pro</i> 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
+  <i>MinionPro</i> package will set up text and maths support using
+  <i>Minion Pro</i>, but a separate (free) font set
+  <i>MnSymbol</i> greatly extends the symbol coverage.
+<dt>PA Math<dd> PA Math is a family of serif fonts
+  loosely based on the Palatino (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 OT1,
+  T1 encoded text fonts of various shapes, as well as fonts
+  with the most useful glyphs of the TS1 encoding.  Macros for
+  using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX
+  are provided.
+<p/>  
+  For further details (and samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/pamath/pamain.htm">http://www.micropress-inc.com/fonts/pamath/pamain.htm</a> 
+  
+<dt>TM Math<dd>(14 fonts) MicroPress Inc.<br>
+  TM Math is a family of serif fonts, inspired by the Times
+  (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 OT1
+  and T1 encoded text fonts of various shapes, as well as fonts
+  with most useful glyphs of the TS1 encoding.  Macros for
+  using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX
+  are provided.  Bitmapped copies of the fonts are available free, on
+  CTAN.
+<p/>  
+  For further details (and samples) see<br>
+  <a href="http://www.micropress-inc.com/fonts/tmmath/tmmain.htm">http://www.micropress-inc.com/fonts/tmmath/tmmain.htm</a> 
+  
+</dl>
+Two other font sets should be mentioned, even though they don&rsquo;t
+currently produce satisfactory output &mdash; their author is no longer
+working on them, and several problems have been identified:
+<dl>
+<dt>pxfonts set version 1.0<dd>(26 fonts) by Young Ryu<br>
+  The <i>pxfonts</i> set consists of
+  <ul>
+  <li> virtual text fonts using <i>Adobe</i> <i>Palatino</i> (or the URW
+    replacement used by <i>ghostscript</i>) with modified plus,
+    equal and slash symbols;
+  <li> maths alphabets using <i>Palatino</i>;
+  <li> maths fonts of all symbols in the computer modern maths fonts
+    (<i>cmsy</i>, <i>cmmi</i>, <i>cmex</i> and the Greek
+    letters of <i>cmr</i>) 
+  <li> maths fonts of all symbols corresponding to the AMS
+    fonts (<i>msam</i> and <i>msbm</i>);
+  <li> additional maths fonts of various symbols.
+  </ul>
+  The text fonts are available in OT1, T1 and LY1
+  encodings, and TS encoded symbols are also available.  The
+  sans serif and monospaced fonts supplied with the <i>txfonts</i>
+  set (see below) may be used with <i>pxfonts</i>; the
+  <i>txfonts</i> set should be installed whenever <i>pxfonts</i>
+  are.  LaTeX, <i>dvips</i> and PDFTeX support files are
+  included.
+
+  <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/doc/pxfontsdocA4.pdf">Documentation</a>
+  is readily available.
+<p/>  The fonts are licensed under the GPL; use in published
+  documents is permitted.
+<dt>txfonts set version 3.1<dd>(42 fonts) by Young Ryu<br>
+  The <i>txfonts</i> set consists of
+  <ul>
+  <li> virtual text fonts using <i>Adobe</i> <i>Times</i> (or the URW
+    replacement used by <i>ghostscript</i>) with modified plus,
+    equal and slash symbols;
+  <li> matching sets of sans serif and monospace (&lsquo;typewriter&rsquo;)
+    fonts (the sans serif set is based on <i>Adobe</i> <i>Helvetica</i>);
+  <li> maths alphabets using <i>Times</i>;
+  <li> maths fonts of all symbols in the computer modern maths fonts
+    (<i>cmsy</i>, <i>cmmi</i>, <i>cmex</i> and the Greek letters of <i>cmr</i>)
+  <li> maths fonts of all symbols corresponding to the AMS
+    fonts (<i>msam</i> and <i>msbm</i>);
+  <li> additional maths fonts of various symbols.
+  </ul>
+  The text fonts are available in OT1, T1 and LY1
+  encodings, and TS encoded symbols are also available.
+
+  <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/doc/txfontsdocA4.pdf">Documentation</a>
+  is readily available.
+<p/>  The fonts are licensed under the GPL; use in published
+  documents is permitted.
+</dl>
+Finally, one must not forget:
+<dl>
+<dt>Proprietary fonts<dd>Various sources.<br>
+  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&rsquo;re more complete
+  than those that are.
+</dl>
+We observe a very limited selection of commercial maths font sets; a
+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.
+<p/>Text fonts in Type 1 format are available from many vendors including
+Adobe, Monotype and Bitstream.  However, be careful with cheap font
+&ldquo;collections&rdquo;; 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 ATM), may not have the
+&lsquo;standard&rsquo; complement of 228 glyphs, or may not include metric files
+(which you need to make TFM files).
+<p/>TrueType remains the &ldquo;native&rdquo; format for Windows.  Some TeX
+implementations such as <a href="FAQ-commercial.html">TrueTeX</a> use TrueType
+versions of Computer Modern and Times Maths fonts to render TeX
+documents in Windows without the need for additional system software like
+ATM.  (When used on a system running Windows XP, TrueTeX can
+also use Type 1 fonts.)
+<p/>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&rsquo;t care as long as you present them with a finished
+print file (PostScript or PDF) for their output device.
+<dl>
+<dt><tt><i>CM family collection</i></tt><dd>
+  Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a>
+<dt><tt><i>AMS font collection</i></tt><dd>
+  Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a>
+<dt><tt><i>Belleek fonts</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/fonts/belleek/belleek.zip">fonts/belleek/belleek.zip</a>
+<dt><tt><i>CM-super collection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>)
+<dt><tt><i>eulervm.sty and supporting metrics</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.zip">fonts/eulervm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/eulervm/">browse</a>)
+<dt><tt><i>fourier (including metrics and other support for utopia</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.zip">fonts/fourier-GUT</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/fourier-GUT/">browse</a>)
+<dt><tt><i>fouriernc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/fouriernc.zip">fonts/fouriernc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/fouriernc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/fouriernc/">browse</a>)
+<dt><tt><i>hfbright collection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.zip">fonts/ps-type1/hfbright</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/hfbright/">browse</a>)
+<dt><tt><i>hvmath (free bitmapped version)</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.zip">fonts/micropress/hvmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/micropress/hvmath/">browse</a>)
+<dt><tt><i>kpfonts family</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/kpfonts.zip">fonts/kpfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/kpfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/kpfonts/">browse</a>)
+<dt><tt><i>Lucida Bright/Math metrics</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.zip">fonts/psfonts/bh/lucida</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/psfonts/bh/lucida/">browse</a>)
+<dt><tt><i>Lucida PSNFSS support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.zip">macros/latex/contrib/psnfssx/lucidabr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psnfssx/lucidabr/">browse</a>)
+<dt><tt><i>MathDesign collection</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/mathdesign/">fonts/mathdesign/</a>
+<dt><tt><i>Maths Font Survey</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Free_Math_Font_Survey/en/survey.pdf">info/Free_Math_Font_Survey/en/survey.pdf</a>
+  (PDF) or <a href="ftp://cam.ctan.org/tex-archive/info/Free_Math_Font_Survey/en/survey.html">info/Free_Math_Font_Survey/en/survey.html</a> (HTML)
+<dt><tt><i>Minion Pro support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/minionpro.zip">fonts/minionpro</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/minionpro.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/minionpro/">browse</a>)
+<dt><tt><i>MnSymbol family</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/mnsymbol.zip">fonts/mnsymbol</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/mnsymbol.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/mnsymbol/">browse</a>)
+<dt><tt><i>pxfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.zip">fonts/pxfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/">browse</a>)
+<dt><tt><i>tmmath (free bitmapped version)</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/tmmath.zip">fonts/micropress/tmmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/tmmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/micropress/tmmath/">browse</a>)
+<dt><tt><i>txfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>)
+<dt><tt><i>utopia fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utopia.zip">fonts/utopia</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utopia.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utopia/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html
new file mode 100644
index 00000000000..0a1a8ea52b9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label psfontprob</title>
+</head><body>
+<h3>Deploying Type 1 fonts</h3>
+<p/>For the LaTeX user trying to use the
+<a href="FAQ-usepsfont.html">PSNFSS</a> package, three questions may arise.
+<p/>First, you have to declare to the DVI driver that you are using
+PostScript fonts; in the case of <i>dvips</i>, this means adding
+lines to the <i>psfonts.map</i> file, so that <i>dvips</i> will know
+where the proper fonts are, and won&rsquo;t try to find PK 
+files.  If the font isn&rsquo;t built into the printer, you have to acquire
+it (which may mean that you need to purchase the font files).
+<p/>Second, your previewer must know what to do with the fonts: see
+<a href="FAQ-PSpreview.html">previewing type 1 fonts</a>.
+<p/>Third, the stretch and shrink between words is a function of the
+font metric; it is not specified in AFM files, so different converters
+choose different values. The PostScript metrics that come with 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 CM
+is extremely generous. 
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html
new file mode 100644
index 00000000000..bdfdc625eaa
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label ragright</title>
+</head><body>
+<h3>Setting text ragged right</h3>
+<p/>The trick with typesetting ragged right is to be sure you&rsquo;ve told the
+TeX engine &ldquo;make this paragraph ragged, but never <em>too</em>
+ragged&rdquo;.  The LaTeX <code>\</code><code>raggedright</code> command (and the
+corresponding <code>flushleft</code> environment) has a tendency to
+miss the &ldquo;never&rdquo; part, and will often create ridiculously short
+lines, for some minor benefit later in the paragraph.  The
+Plain TeX version of the command doesn&rsquo;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 &mdash; such as where
+<a href="FAQ-hyphoff.html">hyphenation is suppressed</a> &mdash; painfully large gaps
+may sometimes be required.
+<p/>Martin Schr&ouml;der&rsquo;s <i>ragged2e</i> package offers the best of both
+worlds: it provides raggedness which is built on the Plain TeX
+model, but which is easily configurable.  It defines easily-remembered
+command (e.g., <code>\</code><code>RaggedRight</code>) and environment (e.g.,
+<code>FlushLeft</code>) 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 <i>ragged2e</i>&rsquo;s operation.
+<dl>
+<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html
new file mode 100644
index 00000000000..eb8f31c7835
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label readML</title>
+</head><body>
+<h3>Using TeX to read SGML or XML directly</h3>
+<p/>This can nowadays be done, with a certain amount of clever macro
+programming.  David Carlisle&rsquo;s <i>xmltex</i> is the prime example;
+it offers a practical solution to typesetting
+XML files.
+<p/>One use of a TeX that can typeset XML files is as a backend
+processor for XSL formatting objects, serialized as XML.
+Sebastian Rahtz&rsquo;s PassiveTeX uses <i>xmltex</i> to
+achieve this end.
+<dl>
+<dt><tt><i>xmltex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.zip">macros/xmltex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/base/">browse</a>)
+<dt><tt><i>passivetex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/contrib/passivetex.zip">macros/xmltex/contrib/passivetex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/contrib/passivetex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/contrib/passivetex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html
new file mode 100644
index 00000000000..1968c6d11d9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html
@@ -0,0 +1,40 @@
+<head>
+<title>UK TeX FAQ -- question label readtex</title>
+</head><body>
+<h3>Reading (La)TeX files</h3>
+<p/>So you&rsquo;ve been sent a TeX file: what are you going to do with it?
+<p/>You can, of course, &ldquo;just read it&rdquo;, since it&rsquo;s a plain text file,
+but the markup tags in the document may prove distracting.  Most of
+the time, even TeX experts will typeset a TeX file before
+attempting to read it.
+<p/>So, you need to typeset the document.  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.
+<p/>TeX is a typesetting system that arose from a publishing project (see
+<a href="FAQ-whatTeX.html">what is TeX</a>),
+and its basic source is available free from its author.  However, at
+its root, it is <em>just</em> a typesetting engine: even to view or to
+print the typeset output, you will need ancillary programs.  In short,
+you need a TeX <em>distribution</em> &mdash; a collection of
+TeX-related programs tailored to your operating system: for details
+of the sorts of things that are available, see
+
+&ldquo;<a href="FAQ-TeXsystems.html">TeX distributions</a>&rdquo;
+or
+
+&ldquo;<a href="FAQ-commercial.html">commercial TeX distributions</a>&rdquo;.
+<p/>But beware &mdash; TeX makes no attempt to look like the sort of
+WYSIWYG system you&rsquo;re probably used to (see
+
+<a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>):
+while many modern versions of TeX have a compile&ndash;view cycle that
+rivals the best commercial word processors in its responsiveness, what
+you type is usually <em>markup</em>, which typically defines a logical
+(rather than a visual) view of what you want typeset.
+<p/>So there&rsquo;s a balance between the simplicity of the original
+(marked-up) document, which can more-or-less be read in <em>any</em>
+editor, and the really rather large investment needed to install a
+system to read a document &ldquo;as intended&rdquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html
new file mode 100644
index 00000000000..47a0a9fe574
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label reallyblank</title>
+</head><body>
+<h3>Really blank pages between chapters</h3>
+<p/><i>Book</i> (by default) and <i>report</i> (with <code>openright</code> class
+option) ensure that each chapter starts on a right-hand (recto) page;
+they do this by inserting a <code>\</code><code>cleardoublepage</code> command between
+chapters (rather than a mere <code>\</code><code>clearpage</code>).  The empty page thus
+created gets to have a normal running header, which some people don&rsquo;t
+like.
+<p/>The (excellent) <i>fancyhdr</i> manual covers this issue, basically
+advising the creation of a command <code>\</code><code>clearemptydoublepage</code>:
+<blockquote>
+<pre>
+\let\origdoublepage\cleardoublepage
+\newcommand{\clearemptydoublepage}{%
+  \clearpage
+  {\pagestyle{empty}\origdoublepage}%
+}
+</pre>
+</blockquote><p>
+The &ldquo;obvious&rdquo; thing is then to use this command to replace
+<code>\</code><code>cleardoublepage</code> in a patched version of the <code>\</code><code>chapter</code> command.
+(Make a package of your own containing a copy 
+of the command out of the class.)  This isn&rsquo;t particularly difficult,
+but you can instead simply subvert <code>\</code><code>cleardoublepage</code> (which isn&rsquo;t
+often used elsewhere):
+<blockquote>
+<pre>
+\let\cleardoublepage\clearemptydoublepage
+</pre>
+</blockquote><p>
+Note: this command works because <code>\</code><code>clearemptydoublepage</code> uses a copy
+of <code>\</code><code>cleardoublepage</code>: instructions on macro programming
+
+<a href="FAQ-patch.html">patching techniques</a> explain the problem and
+why this is a solution.
+<p/>Note that the <em>KOMA-Script</em> replacements for the
+<i>book</i> and <i>report</i> classes (<i>scrbook</i> and
+<i>scrreprt</i> offers class options <code>cleardoubleempty</code>,
+<code>cleardoubleplain</code> and <code>cleardoublestandard</code>
+(using the running page style, as normal) that control the appearance
+of these empty pages.  The classes also offer do-it-yourself commands
+<code>\</code><code>cleardoubleempty</code> (etc.).
+<p/>The <i>memoir</i> class (and the <i>nextpage</i> package)
+provide commands <code>\</code><code>cleartooddpage</code> and <code>\</code><code>cleartoevenpage</code>,
+which both take an optional argument (the first, with no argument,
+being an equivalent of <code>\</code><code>cleardoublepage</code>).  One can achieve
+&lsquo;special&rsquo; effects by putting commands in the optional argument: the
+<code>\</code><code>clearemptydoublepage</code> we&rsquo;re after would be achieved by
+<code>\</code><code>cleartooddpage[</code><code>\</code><code>thispagestyle{empty}</code><code>]</code>.  The
+commands will also serve if you want the surreal effect of &ldquo;This page
+intentionally left blank&rdquo; in the centre of an otherwise empty page.
+<dl>
+<dt><tt><i>fancyhdr</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>nextpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/nextpage.sty">macros/latex/contrib/misc/nextpage.sty</a>
+<dt><tt><i>scrbook.cls, scrrept.cls</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html
new file mode 100644
index 00000000000..9d9ae11ad33
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label recovertex</title>
+</head><body>
+<h3>Retrieving (La)TeX from DVI, etc.</h3>
+<p/>The job just can&rsquo;t be done automatically: DVI, PostScript and
+PDF are &ldquo;final&rdquo; formats, supposedly not susceptible to
+further editing &mdash; information about where things came from has been
+discarded.  So if you&rsquo;ve lost your (La)TeX source (or never
+had the source of a document you need to work on) you&rsquo;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&rsquo;
+skills.
+<p/>If automatic assistance is necessary, it&rsquo;s unlikely that any more than
+text retrieval is going to be possible; the (La)TeX markup that
+creates the typographic effects of the document needs to be recreated
+by editing.
+<p/>If the file you have is in DVI format, many of the techniques
+for <a href="FAQ-toascii.html">converting (La)TeX to ASCII</a> are
+applicable.  Consider <i>dvi2tty</i>, <i>crudetype</i> and
+<i>catdvi</i>.  Remember that there are likely to be problems
+finding included material (such as included PostScript figures, that
+don&rsquo;t appear in the DVI file itself), and mathematics is
+unlikely to convert easily.
+<p/>To retrieve text from PostScript files, the
+<i>ps2ascii</i> tool (part of the  <i>ghostscript</i>
+distribution) is available.  One could try applying this tool to
+PostScript derived from an PDF file using <i>pdf2ps</i> (also
+from the <i>ghostscript</i> distribution), or <i>Acrobat</i>
+<i>Reader</i> itself; an alternative is <i>pdftotext</i>,
+which is distributed with <i>xpdf</i>.
+<p/>Another avenue available to those with a PDF file they want to
+process is offered by Adobe <i>Acrobat</i> (version 5 or later):
+you can tag the PDF file into an estructured document, output
+thence to well-formed XHTML, and import the results into
+Microsoft <i>Word</i> (2000 or later).  From there, one may
+convert to (La)TeX using one of the techniques discussed in
+
+&ldquo;<a href="FAQ-fmtconv.html">converting to and from (La)TeX</a>&rdquo;.
+<p/>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 <i>Acrobat</i> doesn&rsquo;t know how
+to map to its standard Unicode representation.
+<dl>
+<dt><tt><i>catdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse</a>)
+<dt><tt><i>crudetype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.zip">dviware/crudetype</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/crudetype/">browse</a>)
+<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.zip">dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2tty/">browse</a>)
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+<dt><tt><i>xpdf</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/xpdf/">support/xpdf/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html
new file mode 100644
index 00000000000..6b55c4319d0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label ref-doc</title>
+</head><body>
+<h3>Reference documents</h3>
+<p/>For TeX primitive commands a rather nice 
+<a href="http://www.nmt.edu/tcc/help/pubs/texcrib.pdf">quick reference booklet</a>,
+by John W. Shipman, is available; it&rsquo;s arranged in the same way as the
+TeXbook.  By contrast, you can view David Bausum&rsquo;s 
+<a href="http://www.tug.org/utilities/plain/cseq.html">list of TeX primitives</a>
+alphabetically or arranged by &ldquo;family&rdquo;.  Either way, the list has a
+link for each control sequence, that leads you to a detailed
+description, which includes page references to the TeXbook.
+<p/>There doesn&rsquo;t seem to be a reference that takes in Plain TeX as
+well as the primitive commands.
+<p/>Similarly, there&rsquo;s no completely reliable command-organised reference
+to LaTeX, but the NASA 
+<a href="http://www.giss.nasa.gov/latex/">Hypertext Help with LaTeX</a> is
+recently much improved.  It still talks in LaTeX 2.09-isms in places,
+but it&rsquo;s been updated for current LaTeX; there are a number of
+mirrors of the site, and it may be worth choosing a &ldquo;local&rdquo; one if
+you&rsquo;re going to use it a lot.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html
new file mode 100644
index 00000000000..8689aa5a640
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html
@@ -0,0 +1,65 @@
+<head>
+<title>UK TeX FAQ -- question label repeatgrf</title>
+</head><body>
+<h3>Repeated graphics in a document</h3>
+<p/>A logo or &ldquo;watermark&rdquo; 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&rsquo;s to be
+used, and when processed, the image appears in the output file at each
+such point.
+<p/>Huge PostScript files are embarrassing; explaining <em>why</em> such a file
+is huge, is more embarrassing still.
+<p/>The <a href="FAQ-tutbitslatex.html"><i>epslatex</i> graphics tutorial</a>
+describes a technique for avoiding the problem: basically, one
+converts the image that&rsquo;s to be repeated into a PostScript subroutine, and
+load that as a <i>dvips</i> 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.
+<p/>The <i>epslatex</i> 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 &ldquo;real
+experts&rdquo; only (the author of this answer has never even tried it), it has
+potential for the same sort of space saving as the <i>epslatex</i>
+technique, with greater flexibility in actual use.
+<p/>More practical is Hendri Adriaens&rsquo; <i>graphicx-psmin</i>; you load
+this <em>in place</em> of <i>graphicx</i>, so rather than:
+<blockquote>
+<pre>
+\usepackage[&lt;options&gt;]{graphicx}
+</pre>
+</blockquote><p>
+you will write:
+<blockquote>
+<pre>
+\usepackage[&lt;options&gt;]{graphicx-psmin}
+</pre>
+</blockquote><p>
+and at the start of your document, you write:
+<blockquote>
+<pre>
+\loadgraphics[&lt;bb&gt;]{&lt;list of graphics&gt;}
+</pre>
+</blockquote><p>
+and each of the graphics in the list is converted to an &ldquo;object&rdquo; for
+use within the resulting PostScript output.  (This is, in essence, an
+automated version of the <i>epslatex</i> technique described above.)
+<p/>Having loaded the package as above, whenever you use
+<code>\</code><code>includegraphics</code>, the command checks if the file you&rsquo;ve asked for
+is one of the graphics in <code>\</code><code>loadgraphics</code>&rsquo; list.  If so, the
+operation is converted into a call to the &ldquo;object&rdquo; rather than a new
+copy of the file; the resulting PostScript can of course be <em>much</em> smaller.
+<p/>Note that the package requires a recent <i>dvips</i>, version
+5.95b (this version isn&rsquo;t &mdash; yet &mdash; widely distributed).
+<p/>If your PostScript is destined for conversion to PDF, either by a
+<i>ghostscript</i>-based mechanism such as <i>ps2pdf</i> or by
+(for example) <i>Acrobat</i> <i>Distiller</i>, the issue isn&rsquo;t
+so pressing, since the distillation mechanism will amalgamate graphics
+objects whether or not the PostScript has them amalgamated.  PDFTeX does
+the same job with graphics, automatically converting multiple uses
+into references to graphics objects.
+<dl>
+<dt><tt><i>graphicx-psmin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.zip">macros/latex/contrib/graphicx-psmin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/graphicx-psmin/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html
new file mode 100644
index 00000000000..ae3ebeb8d5f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html
@@ -0,0 +1,85 @@
+<head>
+<title>UK TeX FAQ -- question label repfootnote</title>
+</head><body>
+<h3>Footnotes whose texts are identical</h3>
+<p/>If the <em>same</em> footnote turns up at several places within a
+document, it&rsquo;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&rsquo;re going to repeat and then referencing the result.  There is no
+completely automatic solution (that detects and suppresses repeats)
+available.
+<p/>If you know you only have one footnote, which you want to repeat, the
+solution is simple: merely use the optional argument of
+<code>\</code><code>footnotemark</code> to signify the repeats:
+<blockquote>
+<pre>
+...\footnote{Repeating note}
+...
+...\footnotemark[1]
+</pre>
+</blockquote><p>
+... 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.
+<p/>Simple hand-labelling of footnotes is possible, using a counter dedicated
+to the job:
+<blockquote>
+<pre>
+\newcounter{fnnumber}
+...
+...\footnote{Text to repeat}%
+\setcounter{fnnumber}{\thefootnote}%
+...
+...\footnotemark[\thefnnumber]
+</pre>
+</blockquote><p>
+but this is somewhat tedious.  LaTeX&rsquo;s labelling mechanism can be
+summoned to our aid, but there are ugly error messages before the
+<code>\</code><code>ref</code> is resolved on a second run through LaTeX:
+<blockquote>
+<pre>
+...\footnote{Text to repeat\label{fn:repeat}}
+...
+...\footnotemark[\ref{fn:repeat}]
+</pre>
+</blockquote><p>
+Alternatively, one may use the <code>\</code><code>footref</code> command, which has the
+advantage of working even when the footnote mark isn&rsquo;t expressed as a
+number.  The command is defined in the <i>footmisc</i> package and
+in the <i>memoir</i> class (at least); <code>\</code><code>footref</code> reduces the above
+example to:
+<blockquote>
+<pre>
+...\footnote{Text to repeat\label{fn:repeat}}
+...
+...\footref{fn:repeat}
+</pre>
+</blockquote><p>
+This is the cleanest simple way of doing the job.  Note that the
+<code>\</code><code>label</code> command <em>must</em> be inside the argument of
+<code>\</code><code>footnote</code>.
+<p/>The <i>fixfoot</i> package takes away some of the pain of the
+matter: you declare footnotes you&rsquo;re going to reuse, typically in the
+preamble of your document, using a <code>\</code><code>DeclareFixedFoot</code> command, and
+then use the command you&rsquo;ve &lsquo;declared&rsquo; in the body of the document:
+<blockquote>
+<pre>
+\DeclareFixedFootnote{\rep}{Text to repeat}
+...
+...\rep{}
+...\rep{}
+</pre>
+</blockquote><p>
+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.
+<dl>
+<dt><tt><i>fixfoot.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fixfoot.zip">macros/latex/contrib/fixfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fixfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fixfoot/">browse</a>)
+<dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html
new file mode 100644
index 00000000000..2588d3fcc3f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label replstdcls</title>
+</head><body>
+<h3>Replacing the standard classes</h3>
+<p/>People are forever concocting classes that replace the standard ones:
+the present author produced an <i>ukart</i> class that used the
+<i>sober</i> package, and a few British-specific things (such as
+appear in the <i>babel</i> package&rsquo;s British-english
+specialisation) in the 1980s, which is still occasionally used.
+<p/>Similar public efforts were available well back in the days of
+LaTeX 2.09: a notable example, whose pleasing designs seem not to have
+changed much over all that time, is the <i>ntgclass</i> 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 <i>artikel2</i>, <i>rapport1</i>, <i>boek3</i> and
+<i>brief</i>.  These classes are moderately well documented in
+English.
+<p/>The <i>KOMA-script</i> bundle (classes named <i>scr...</i>) are a
+strong current contender.  They are actively supported, are
+comprehensive in their coverage of significant typesetting issues,
+produce good-looking output and are well documented in both English
+and German (<i>scrguien</i> in the distribution for English,
+<i>scrguide</i> for German).
+<p/>The other comparable class is <i>memoir</i>.  This aims to replace
+<i>book</i> and <i>report</i> classes directly, and (like
+<i>KOMA-script</i>) is comprehensive in its coverage of small issues.
+<i>Memoir</i>&rsquo;s documentation (<i>memman</i>) is very highly
+spoken of, and its lengthy introductory section is regularly
+recommended as a tutorial on typesetting.
+<dl>
+<dt><tt><i>KOMA-script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>NTGclass bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntgclass/">browse</a>)
+<dt><tt><i>sober.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/misc/sober.sty">macros/latex209/contrib/misc/sober.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html
new file mode 100644
index 00000000000..47c99b6788f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label rerun</title>
+</head><body>
+<h3>&ldquo;Rerun&rdquo; messages won&rsquo;t go away</h3>
+<p/>The LaTeX message &ldquo;Rerun to get crossreferences right&rdquo; 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
+<code>\</code><code>end{document}</code>.)
+<p/>Sometimes, the message won&rsquo;t go away: however often you reprocess your
+document, LaTeX still tells you that &ldquo;Label(s) may have
+changed&rdquo;.  This can sometimes be caused by a broken package: both
+<i>footmisc</i> (with the <code>perpage</code> option) and <i>hyperref</i>
+have been known to give trouble, in the past: if you are using either,
+check you have the latest version, and upgrade if possible.
+<p/>However, there <em>is</em> 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 &ldquo;ix&rdquo; (9).  The presence of the reference pushes the thing
+referred to onto page &ldquo;x&rdquo; (10), but since that&rsquo;s a shorter reference
+the label moves back to page &ldquo;ix&rdquo; at the next run.  Such a sequence
+can obviously not terminate.
+<p/>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).
+<dl>
+<dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>)
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html
new file mode 100644
index 00000000000..f4e5bcebd24
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label resolns</title>
+</head><body>
+<h3>What are &ldquo;resolutions&rdquo;</h3>
+<p/>&ldquo;Resolution&rdquo; 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 &mdash; 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.
+<p/>In fact, there are two sorts of &ldquo;resolution&rdquo; on the printed page
+that we need to consider for (La)TeX&rsquo;s purposes:
+<ul>
+<li> the positioning accuracy, and
+<li> the quality of the fonts.
+</ul>
+In the case where (La)TeX output is being sent direct to a printer,
+in the printer&rsquo;s &ldquo;native&rdquo; language, it&rsquo;s plain that the DVI
+processor must know all such details, and must take detailed account
+of both types of resolution.
+<p/>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&rsquo;s properties: the
+DVI processor need not know, and should not presume to guess.
+<p/>Both PostScript and PDF output are in this category.  While PostScript is
+used less frequently for document distribution nowadays, it is
+regularly used as the source for distillation into PDF; and
+PDF is the workhorse of an enormous explosion of document
+distribution.
+<p/>Therefore, we need DVI processors that will produce
+&ldquo;resolution independent&rdquo; PostScript or PDF output; of course, the
+independence needs to extend to both forms of independence outlined
+above.
+<p/>Resolution-independence of fonts was for a  long time forced upon the
+world by the feebleness of Adobe&rsquo;s <i>Acrobat</i>
+<i>Reader</i> at dealing with bitmap files: a sequence of answers
+starting with one aiming at the 
+<a href="FAQ-dvips-pdf.html">quality of PDF from PostScript</a> addresses
+the problems that arise.
+<p/>Resolution-independence of positioning is more troublesome:
+<i>dvips</i> 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 (&ldquo;better
+than any device&rdquo;), and this is reasonably successful though it does
+have its <a href="FAQ-8000.html">problems</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html
new file mode 100644
index 00000000000..67f62f82ec1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html
@@ -0,0 +1,37 @@
+<head>
+<title>UK TeX FAQ -- question label reuseq</title>
+</head><body>
+<h3>Re-using an equation</h3>
+<p/>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 <i>amsmath</i> package comes to our help, here:
+<blockquote>
+<pre>
+\usepackage{amsmath}
+...
+\begin{equation}
+  a=b
+  \label{eq1}
+\end{equation}
+...
+Remember that
+\begin{equation}
+  a=b
+  \tag{\ref{eq1}}
+\end{equation}
+</pre>
+</blockquote><p>
+Here, the second instance of a=b will be
+typeset with a copy, made by the <code>\</code><code>tag</code> command, of the label of the
+first instance.
+<p/>Comprehensive documentation of AMSLaTeX is to be found in
+<i>amsldoc</i>, in the distribution; it is also available on the web
+at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a>
+<dl>
+<dt><tt><i>amsldoc.tex</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX
+  <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html
new file mode 100644
index 00000000000..2f56abae1b7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label rulethk</title>
+</head><body>
+<h3>The thickness of rules in LaTeX tables</h3>
+<p/>The rules in a LaTeX table are by default <code>0.4pt</code> 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).
+<p/>Sometimes, however, we look at a table and find we want the rules to
+stand out &mdash; 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 &ldquo;bleeding&rdquo; out to affect other rules in the same table.
+<p/>If you look at what we have to say on the 
+<a href="FAQ-destable.html">design of tables</a>, elsewhere
+among these FAQs, and you may sense that the design of LaTeX
+simply skipped the issues surrounding table design: <em>that&rsquo;s</em>
+presumably why there&rsquo;s no facilities to help you.
+<p/>Specifically, the length <code>\</code><code>arrayrulewidth</code> affects the thickness of
+the rules (both horizontal and vertical) within both
+<code>tabular</code> and <code>array</code> environments.  If you
+change from the default (see above) only as far as
+<blockquote>
+<pre>
+\setlength{\arrayrulewidth}{1pt}
+</pre>
+</blockquote><p>
+the change is remarkably striking.  However, really quite subtle user
+level programming proves incapable of changing just <em>one</em> rule:
+it&rsquo;s necessary to delve into the (rather tricky) code of <code>\</code><code>hline</code>
+and <code>\</code><code>cline</code> themselves.
+<p/>Fortunately, this job has already been done for the community: the
+<i>booktabs</i> package defines three different classes of rule
+(<code>\</code><code>toprule</code>, <code>\</code><code>midrule</code> and <code>\</code><code>bottomrule</code>), and the package
+documentation offers hints on how to use them.  You are
+<em>strongly</em> advised to read the documentation pretty carefully.
+<p/>The <i>memoir</i> class includes the <i>booktabs</i> package, and
+repeats the documentation in its compendious manual.
+<p/>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 <i>booktabs</i> 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.
+<dl>
+<dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html
new file mode 100644
index 00000000000..452c465d1d5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label run-fn-nos</title>
+</head><body>
+<h3>Not resetting footnote numbers per chapter</h3>
+<p/>Some classes (for example, <i>book</i> and <i>report</i>) 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 
+<a href="FAQ-running-nos.html">equation, figure and table numbers</a>,
+except that footnote numbers don&rsquo;t get &ldquo;decorated&rdquo; with the chapter
+number, as happens with those other numbers.
+<p/>The solution is the same: use the <i>chngcntr</i> package; since the
+numbers aren&rsquo;t &ldquo;decorated&rdquo; you can use the <code>\</code><code>counterwithout*</code>
+variant; the code:
+<blockquote>
+<pre>
+\counterwithout*{footnote}{chapter}
+</pre>
+</blockquote><p>
+is all you need
+<dl>
+<dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a>
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html
new file mode 100644
index 00000000000..dd45e61d98b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html
@@ -0,0 +1,85 @@
+<head>
+<title>UK TeX FAQ -- question label runheadtoobig</title>
+</head><body>
+<h3>My section title is too wide for the page header</h3>
+<p/>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&rsquo;s common for titles too
+be too big to fit: the LaTeX sectioning commands therefore take an
+optional argument:
+<blockquote>
+<pre>
+\section[short title]{full title}
+</pre>
+</blockquote><p>
+If the &lt;<i>short title</i>&gt; 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.
+<p/>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.
+<p/>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 &ldquo;ordinary&rdquo; reading?  It&rsquo;s not possible to do so with unmodified
+LaTeX, but the <i>fancyhdr</i> package provides a command
+<code>\</code><code>nouppercase</code> for use in its header (and footer) lines to suppress
+LaTeX&rsquo;s uppercasing tendencies.  Classes in the <i>KOMA-script</i>
+bundle don&rsquo;t uppercase in the first place.
+<p/>In fact, the sectioning commands use &lsquo;mark&rsquo; commands to pass
+information to the page headers.  For example, <code>\</code><code>chapter</code> uses
+<code>\</code><code>chaptermark</code>, <code>\</code><code>section</code> uses <code>\</code><code>sectionmark</code>, and so on.  With
+this knowledge, one can achieve a three-layer structure for chapters:
+<blockquote>
+<pre>
+\chapter[middling version]{verbose version}
+\chaptermark{terse version}
+</pre>
+</blockquote><p>
+which should supply the needs of every taste.
+<p/>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 <code>\</code><code>*mark</code> 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:
+<blockquote>
+<pre>
+\section[middling version]{verbose version%
+              \sectionmark{terse version}}
+\sectionmark{terse version}
+</pre>
+</blockquote><p>
+(the first <code>\</code><code>sectionmark</code> deals with the header of the page the
+<code>\</code><code>section</code> command falls on, and the second deal with subsequent
+pages; note that here, you need the optional argument to <code>\</code><code>section</code>,
+even if &ldquo;<em>middling version</em>&rdquo; is in fact the same text as
+&ldquo;<em>long version&rdquo;</em>.)
+<p/>A similar arrangement is necessary even for chapters if the class
+you&rsquo;re using is odd enough that it puts a page header on a chapter&rsquo;s
+opening page.
+<p/>Note that the <i>titlesec</i> package manages the running heads in
+a completely different fashion; users of that package should refer to
+the documentation.
+<p/>The <i>memoir</i> class avoids all the silliness by providing an
+extra optional argument for chapter and sectioning commands, for
+example:
+<blockquote>
+
+<pre>
+\section[middling version][terse version]{verbose version}
+</pre>
+</blockquote><p>
+As a result, it is always possible for users of <i>memoir</i> to
+tailor the header text to fit, with very little trouble.
+<dl>
+<dt><tt><i>fancyhdr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>)
+</dl>
+<p/>
+<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=runheadtoobig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=runheadtoobig</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html
new file mode 100644
index 00000000000..35460003b8b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html
@@ -0,0 +1,79 @@
+<head>
+<title>UK TeX FAQ -- question label running-nos</title>
+</head><body>
+<h3>Running equation, figure and table numbering</h3>
+<p/>Many LaTeX classes (including the standard <i>book</i> 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&rsquo;s
+needs.
+<p/>Short of rewriting the whole class, one may use the <i>chngctr</i>
+package, which provides commands <code>\</code><code>counterwithin</code> (which
+establishes this nested numbering relationship) and
+<code>\</code><code>counterwithout</code> (which undoes it).
+<p/>So if you have figures numbered by chapter as 1.1, 1.2, 2.1, ...,
+the command 
+<blockquote>
+<pre>
+\counterwithout{figure}{chapter}
+</pre>
+</blockquote><p>
+will convert them to figures 1, 2, 3, ....  (Note that the command
+has also removed the chapter number from the counter&rsquo;s definition.)
+<p/>More elaborate use could change things numbered per section to things
+numbered per chapter:
+<blockquote>
+<pre>
+\counterwithout{equation}{section}
+\counterwithin{equation}{chapter}
+</pre>
+</blockquote><p>
+(assuming there was a class that did such a thing in the first place...)
+<p/>The <i>chngcntr</i> approach doesn&rsquo;t involve much programming, and
+the enthusiastic LaTeX programmer might choose to try the technique
+that we had to use before the advent of <i>chngcntr</i>.  Each of
+the packages <i>removefr</i> and <i>remreset</i> defines a
+<code>\</code><code>@removefromreset</code> command, and having included the package one
+writes something like:
+<blockquote>
+<pre>
+\makeatletter
+\@removefromreset{figure}{chapter}
+\makeatother
+</pre>
+</blockquote><p>
+and the automatic renumbering stops.  You may then need to redefine the
+way in which the figure number (in this case) is printed:
+<blockquote>
+<pre>
+\makeatletter
+\renewcommand{\thefigure}{\@arabic\c@figure}
+\makeatother
+</pre>
+</blockquote><p>
+(remember to do the whole job, for every counter you want to
+manipulate, within <code>\</code><code>makeatletter</code> ... <code>\</code><code>makeatother</code>).
+<p/>This technique, too, may be used to change where in a multilevel
+structure a counter is reset.  Suppose your class numbers figures as
+&lt;<i>chapter</i>&gt;.&lt;<i>section</i>&gt;.&lt;<i>figure</i>&gt;, and you want figures
+numbered per chapter, try:
+<blockquote>
+<pre>
+\makeatletter
+\@removefromreset{figure}{section}
+\@addtoreset{figure}{chapter}
+\renewcommand{\thefigure}{\thechapter.\@arabic\c@figure}
+\makeatother
+</pre>
+
+</blockquote><p>
+(the command <code>\</code><code>@addtoreset</code> is a part of LaTeX itself).
+<dl>
+<dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a>
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>removefr.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fragments/removefr.tex">macros/latex/contrib/fragments/removefr.tex</a> (note, this is constructed as a
+  &ldquo;fragment&rdquo; for use within other packages: load by
+  <code>\</code><code>input{removefr}</code>)
+<dt><tt><i>remreset.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html
new file mode 100644
index 00000000000..f0b21c4a397
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html
@@ -0,0 +1,55 @@
+<head>
+<title>UK TeX FAQ -- question label scriptfonts</title>
+</head><body>
+<h3>Better script fonts for maths</h3>
+<p/>The font selected by <code>\</code><code>mathcal</code> is the only script font &lsquo;built
+in&rsquo;. However, there are other useful calligraphic fonts included with
+modern TeX distributions.
+<dl>
+<dt>Euler<dd> The <i>eucal</i> package (part of most sensible TeX
+  distributions; the fonts are part of the AMS font set) gives
+  a slightly curlier font than the default. The package changes the
+  font that is selected by <code>\</code><code>mathcal</code>.
+<p/>  Type 1 versions of the fonts are available in the AMS fonts
+  distribution.
+<dt>RSFS<dd> The <i>mathrsfs</i> package uses a really fancy script
+  font (the name stands for &ldquo;Ralph Smith&rsquo;s Formal Script&rdquo;) which is
+  already part of most modern TeX distributions.  The package
+  creates a new command <code>\</code><code>mathscr</code>.
+<p/>  Type 1 versions of the font have been made available by Taco
+  Hoekwater.
+<dt>Zapf Chancery<dd> is the standard PostScript calligraphic font.  There
+  is no package but you can easily make it available by means of the
+  command
+<pre>
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+                                 {m}{it}
+</pre>
+  in your preamble.  You may find the font rather too big; if so, you
+  can use a scaled version of it like this:
+<pre>
+\DeclareFontFamily{OT1}{pzc}{}
+\DeclareFontShape{OT1}{pzc}{m}{it}%
+             {&lt;-&gt; s * [0.900] pzcmi7t}{}
+\DeclareMathAlphabet{\mathscr}{OT1}{pzc}%
+                                 {m}{it}
+</pre>
+<p/>  Adobe Zapf Chancery (which the above examples use) is distributed in
+  any but the most basic PostScript printers.  A substantially identical
+  font (to the extent that the same metrics may be used) is
+  available from URW and is distributed with
+  <i>ghostscript</i>.
+</dl>
+Examples of the available styles are available on CTAN.
+<dl>
+<dt><tt><i>eucal.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex/eucal.sty">fonts/amsfonts/latex/eucal.sty</a>
+<dt><tt><i>euler fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/euler.zip">fonts/amsfonts/sources/euler</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/euler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/euler/">browse</a>)
+<dt><tt><i>euler fonts, in Type 1 format</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a>
+<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a>
+<dt><tt><i>mathrsfs.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jknappen.zip">macros/latex/contrib/jknappen</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jknappen.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen/">browse</a>)
+<dt><tt><i>rsfs fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs.zip">fonts/rsfs</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs/">browse</a>)
+<dt><tt><i>rsfs fonts, in Type 1 format</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs/ps-type1/hoekwater.zip">fonts/rsfs/ps-type1/hoekwater</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs/ps-type1/hoekwater.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs/ps-type1/hoekwater/">browse</a>)
+<dt><tt><i>Script font examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/symbols/math/scriptfonts.pdf">info/symbols/math/scriptfonts.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html
new file mode 100644
index 00000000000..76dcaabad19
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html
@@ -0,0 +1,71 @@
+<head>
+<title>UK TeX FAQ -- question label seccntfmt</title>
+</head><body>
+<h3>Adjusting the presentation of section numbers</h3>
+<p/>The general issues of adjusting the appearance of section headings are
+pretty complex, and are covered in 
+the question on
+<a href="FAQ-secthead.html">the style of section headings</a>.
+<p/>However, people regularly want merely to change the way the section
+number appears in the heading, and some such people don&rsquo;t mind writing
+out a few macros.  This answer is for <em>them</em>.
+<p/>The section number is typeset using the
+
+  <a href="FAQ-atsigns.html">LaTeX internal</a>
+<code>\</code><code>@seccntformat</code> command, which is given the &ldquo;name&rdquo; (section,
+subsection, ...) of the heading, as argument.  Ordinarily,
+<code>\</code><code>@seccntformat</code> 
+merely outputs the section number, and then a <code>\</code><code>quad</code> of space.
+Suppose you want to put a stop after every section (subsection,
+subsubsection, ...) number, a trivial change may be implemented by
+simple modification of the command:
+<blockquote>
+<pre>
+\renewcommand*{\@seccntformat}[1]{%
+  \csname the#1\endcsname.\quad
+}
+</pre>
+</blockquote><p>
+<p/>Many people (for some reason) want a stop after a section number, but
+not after a subsection number, or any of the others.
+To do this, one must make <code>\</code><code>@seccntformat</code> switch according to its
+argument.  The following technique for doing the job is slightly
+wasteful, but is efficient enough for a relatively rare operation:
+<blockquote>
+<pre>
+\let\@@seccntformat\@seccntformat
+\renewcommand*{\@seccntformat}[1]{%
+  \expandafter\ifx\csname @seccntformat@#1\endcsname\relax
+    \expandafter\@@seccntformat
+  \else
+    \expandafter
+      \csname @seccntformat@#1\expandafter\endcsname
+  \fi
+    {#1}%
+}
+</pre>
+</blockquote><p>
+
+which looks to see if a second-level command has been defined, and
+uses it if so; otherwise it uses the original.  The second-level
+command to define stops after section numbers (only) has the same
+definition as the original &ldquo;all levels alike&rdquo; version:
+<blockquote>
+<pre>
+\newcommand*{\@seccntformat@section}[1]{%
+  \csname the#1\endcsname.\quad
+}
+</pre>
+</blockquote><p>
+Note that all the command definitions of this answer are dealing in
+<a href="FAQ-atsigns.html">LaTeX internal commands</a>, so the above
+code should be in a package file, for preference.
+<p/>The <i>Koma-script</i> classes have different commands for specifying
+changes to section number presentation: <code>\</code><code>partformat</code>,
+<code>\</code><code>chapterformat</code> and <code>\</code><code>othersectionlevelsformat</code>, but otherwise
+their facilities are similar to those of &ldquo;raw&rdquo; LaTeX.
+<dl>
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html
new file mode 100644
index 00000000000..ae503fd40c2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html
@@ -0,0 +1,15 @@
+<head>
+<title>UK TeX FAQ -- question label secindent</title>
+</head><body>
+<h3>Indent after section headings</h3>
+<p/>LaTeX implements a style that doesn&rsquo;t indent the first paragraph
+after a section heading.  There are coherent reasons for this, but not
+everyone likes it.
+The <i>indentfirst</i> package
+suppresses the mechanism, so that the first paragraph is
+indented.
+<dl>
+<dt><tt><i>indentfirst.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html
new file mode 100644
index 00000000000..e708dbdc7ef
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html
@@ -0,0 +1,59 @@
+<head>
+<title>UK TeX FAQ -- question label secnumdep</title>
+</head><body>
+<h3>Unnumbered sections in the Table of Contents</h3>
+<p/>The way the relevant parts of sectioning commands work is exemplified
+by the way the <code>\</code><code>chapter</code> command uses the counter <code>secnumdepth</code>
+(described in Appendix C of the LaTeX manual):
+<ol>
+<li> put something in the <code>.aux</code> file, which will appear in
+  the <code>.toc</code>;
+
+<li> if the <code>secnumdepth</code> counter is greater than or equal to
+  zero,
+  increase the counter for the chapter and write it out.
+<li> write the chapter title.
+</ol>
+Other sectioning commands are similar, but with other values used in
+the test.
+<p/>So a simple way to get headings of funny &lsquo;sections&rsquo; such as prefaces
+in the table of contents is to use the counter:
+<blockquote>
+<pre>
+\setcounter{secnumdepth}{-1}
+\chapter{Preface}
+</pre>
+</blockquote><p>
+Unfortunately, you have to set <code>secnumdepth</code> back to its usual
+value (which is 2 in the standard styles) before you do any &lsquo;section&rsquo;
+which you want to be numbered.
+<p/>Similar settings are made, automatically, in the LaTeX book class by
+the <code>\</code><code>frontmatter</code> and <code>\</code><code>backmatter</code> commands.
+<p/>The value of the counter <code>tocdepth</code> controls which headings
+will be finally printed in the table of contents.  This normally has
+to be set in the preamble and is a constant for the document.  The
+package <i>tocvsec2</i> package provides a convenient interface to
+allow you to change the <code>secnumdepth</code> and/or the
+<code>tocdepth</code> counter values at any point in the body of the
+document; this provides convenient independent controls over the
+sectional numbering and the table of contents.
+<p/>The package <i>abstract</i> (see 
+<a href="FAQ-onecolabs.html">one-column abstracts</a>) includes an option
+to add the <code>abstract</code> to the table of contents, while the
+package <i>tocbibind</i> has options to include the table of
+contents itself, the <code>bibliography</code>, <code>index</code>, etc., to
+the table of contents.
+<p/>The <i>KOMA-Script</i> classes have commands <code>\</code><code>addchap</code> and
+<code>\</code><code>addled</code>, which work like <code>\</code><code>chapter</code> and <code>\</code><code>section</code> but
+aren&rsquo;t numbered.  The <i>memoir</i> class incorporates the facilities
+of all three of the <i>abstract</i>, <i>tocbibind</i> and
+<i>tocvsec2</i> packages.
+<dl>
+<dt><tt><i>abstract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.zip">macros/latex/contrib/abstract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/abstract/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>)
+<dt><tt><i>tocvsec2.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocvsec2.zip">macros/latex/contrib/tocvsec2</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocvsec2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocvsec2/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html
new file mode 100644
index 00000000000..fd1d5e84288
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label secthead</title>
+</head><body>
+<h3>The style of section headings</h3>
+<p/>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&rsquo;t want to get involved in the sort of
+programming described in section 2.2 of <em>The LaTeX Companion</em>
+
+  (see <a href="FAQ-books.html">TeX-related books</a>; the
+  <a href="FAQ-atsigns.html">programming</a> itself is discussed elsewhere in this
+  FAQ).
+The following hack will 
+probably satisfy your editor. Define yourself new commands
+<blockquote>
+<pre>
+\newcommand{\ssection}[1]{%
+  \section[#1]{\centering\normalfont\scshape #1}}
+\newcommand{\ssubsection}[1]{%
+  \subsection[#1]{\raggedright\normalfont\itshape #1}}
+</pre>
+
+</blockquote><p>
+and then use <code>\</code><code>ssection</code> and <code>\</code><code>ssubsection</code> in place of
+<code>\</code><code>section</code> and <code>\</code><code>subsection</code>. This isn&rsquo;t perfect: section numbers
+remain in bold, and starred forms need a separate redefinition.
+<p/>The <i>titlesec</i> 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&rsquo; output.
+<p/>The <i>sectsty</i> package provides a more simply structured set of
+tools; while it is less powerful than is <i>titlesec</i>, it is
+perhaps preferable for minor adjustments, since you can use it after
+having read a smaller proportion of the manual.
+<p/>The <i>fncychap</i> package provides a nice collection of customised
+chapter heading designs.  The <i>anonchap</i> package provides a
+simple means of typesetting chapter headings &ldquo;like section headings&rdquo;
+(i.e., without the &ldquo;Chapter&rdquo; part of the heading); the
+<i>tocbibind</i> package provides the same commands, in pursuit of
+another end.  Unfortunately, <i>fncychap</i> is not attuned to the
+existence of front- and backmatter in <i>book</i> class documents.
+<p/>The <i>memoir</i> class includes facilities that match
+<i>sectsty</i> and <i>titlesec</i>, as well as a bundle of
+chapter heading styles (including an <i>anonchap</i>-equivalent).
+The <i>KOMA-script</i> classes also have sets of tools that provide
+equivalent functionality, notably formatting specifications <code>\</code><code>partformat</code>,
+<code>\</code><code>chapterformat</code>, <code>\</code><code>sectionformat</code>, ..., as well as several
+useful overall formatting specifications defined in class options.
+<p/>Finally, the indefatigable Vincent Zoonekynd supplies examples of how
+to program alternative 
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html">chapter heading styles</a>
+and
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>.
+The web pages are not useful to users unless they are willing to do
+their own LaTeX programming.
+<dl>
+<dt><tt><i>anonchap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/anonchap.sty">macros/latex/contrib/misc/anonchap.sty</a>
+<dt><tt><i>fncychap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fncychap.zip">macros/latex/contrib/fncychap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fncychap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fncychap/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>sectsty.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sectsty.zip">macros/latex/contrib/sectsty</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sectsty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sectsty/">browse</a>)
+<dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>)
+<dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
new file mode 100644
index 00000000000..13c48eee5fd
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label semanticnest</title>
+</head><body>
+<h3>Capacity exceeded [semantic nest ...]</h3>
+<p/>
+<pre>
+! TeX capacity exceeded, sorry [semantic nest size=100].
+...
+If you really absolutely need more capacity,
+you can ask a wizard to enlarge me.
+</pre>
+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.
+<p/>The &ldquo;semantic nest&rdquo; TeX talks about is the nesting
+of boxes within boxes.  A stupid macro can provoke the error pretty
+easily:
+<blockquote>
+
+<pre>
+\def\silly{\hbox{here's \silly being executed}}
+\silly
+</pre>
+</blockquote><p>
+The extended traceback
+
+(see <a href="FAQ-erroradvice.html"><em>general advice</em> on errors</a>)
+<em>does</em> help, though it does rather run on.  In the case above,
+the traceback consists of
+<pre>
+\silly -&gt;\hbox {
+                here's \silly being executed}
+</pre>
+followed by 100 instances of
+<pre>
+\silly -&gt;\hbox {here's \silly 
+                              being executed}
+</pre>
+The repeated lines are broken at exactly the offending macro; of
+course the loop need not be as simple as this &mdash; if <code>\</code><code>silly</code> calls
+<code>\</code><code>dopy</code> which boxes <code>\</code><code>silly</code>, the effect is just the same and
+alternate lines in the traceback are broken at alternate positions.
+<p/>There are in fact two items being consumed when you nest boxes: the
+other is the grouping level.  Whether you exhaust your 
+<em>semantic nest</em> or your permitted <em>grouping levels</em> first is
+controlled entirely by the relative size of the two different sets of
+buffers in your (La)TeX executable.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html
new file mode 100644
index 00000000000..c9e444ad6a8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html
@@ -0,0 +1,72 @@
+<head>
+<title>UK TeX FAQ -- question label setURL</title>
+</head><body>
+<h3>Typesetting URLs</h3>
+<p/>URLs tend to be very long, and contain characters that would
+naturally prevent them being hyphenated even if they weren&rsquo;t typically
+set in <code>\</code><code>ttfamily</code>, verbatim.  Therefore, without special treatment,
+they often produce wildly overfull <code>\</code><code>hbox</code>es, and their typeset
+representation is awful.
+<p/>There are three packages that help solve this problem:
+<ul>
+<li> The <i>path</i> package, which defines a <code>\</code><code>path</code> command.
+  The command defines each potential break character as a
+  <code>\</code><code>discretionary</code>, 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
+
+  <a href="FAQ-eplain.html">Eplain macros</a> &mdash; define a similar <code>\</code><code>path</code> command.
+<p/>  <i>Path</i>, 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.
+<li> The <i>url</i> package, which defines an <code>\</code><code>url</code> command
+  (among others, including its own <code>\</code><code>path</code> command).  The command
+  gives each potential break character a maths-mode &lsquo;personality&rsquo;, and
+  then sets the URL itself (in the user&rsquo;s choice of font) in
+  maths mode.  It can produce (LaTeX-style) &lsquo;robust&rsquo; commands
+  
+  (see <a href="FAQ-protect.html">use of <code>\</code><code>protect</code></a>) for use
+  within moving arguments.  Note that, because the operation is
+  conducted in maths mode, spaces within the URL argument are
+  ignored unless special steps are taken.
+<p/>  It is possible to use the <i>url</i> package in Plain TeX,
+  with the assistance of the <i>miniltx</i> package (which was
+  originally developed for using the LaTeX graphics package in
+  Plain TeX).  A small patch is also necessary: the required
+  sequence is therefore:
+
+<pre>
+\input miniltx
+\expandafter\def\expandafter\+\expandafter{\+}
+\input url.sty
+</pre>
+<li> The <i>hyperref</i> package, which uses the typesetting code
+  of <i>url</i>, in a context where the typeset text forms the
+  anchor of a link.
+</ul>
+<p/>The author of this answer prefers the (rather newer) <i>url</i>
+package (directly or indirectly); both <i>path</i> and
+<i>url</i> work well with Plain TeX (though of course, the fancy
+LaTeX facilities of <i>url</i> don&rsquo;t have much place there).
+(<i>hyperref</i> isn&rsquo;t available in a version for use with Plain TeX.)
+<p/>Note that neither <code>\</code><code>path</code> (from package <i>path</i>) nor <code>\</code><code>url</code> (from
+package <i>url</i>) is robust (in the LaTeX sense).  If you need
+a URL to go in a moving argument, you need the command
+<code>\</code><code>urldef</code> from the <i>url</i> package.  So one might write:
+<blockquote>
+<pre>
+\urldef\faqhome\url{http://www.tex.ac.uk/faq}
+</pre>
+</blockquote><p>
+after which, <code>\</code><code>faqhome</code> is robust.
+<p/>Documentation of both package <i>path</i> and package <i>url</i>
+is in the package files.
+<dl>
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>miniltx.tex</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>)
+<dt><tt><i>path.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/path.sty">macros/latex/contrib/misc/path.sty</a>
+<dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html
new file mode 100644
index 00000000000..a209eb2eb06
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label slashbox</title>
+</head><body>
+<h3>Diagonal separation in corner cells of tables</h3>
+<!-- tabular -->
+<p/>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 <code>\</code><code>multicolumn</code>
+entries), to look like:
+<blockquote>
+<pre>
+-----------------
+x  y
+   --------------
+   1  2  3  4  5
+-----------------
+1
+2
+3
+4
+5
+-----------------
+</pre>
+</blockquote><p>
+However, this doesn&rsquo;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 <i>slashbox</i> package does the job for you: it defines
+commands <code>\</code><code>slashbox</code> and <code>\</code><code>backslashbox</code>, each taking the two
+labels as arguments.  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.
+<p/>The package isn&rsquo;t the world&rsquo;s neatest: it uses LaTeX
+<code>picture</code> mode to draw its line, and picture mode has many
+tedious restrictions (and doesn&rsquo;t, in all honesty, produce
+particularly good pictures).  Load slashbox with the <i>pict2e</i>
+package, and at least the picture quality will be improved.
+<p/>Documentation of <i>slashbox</i> is less than satisfactory: a
+LaTeX source file of rather startling starkness accompanies the
+package file in the distribution.  It does, however, process to a
+DVI file that gives some idea of how the <code>\</code><code>slashbox</code> may be
+expected to look.  (The third example in the file shows the effect of
+<code>picture</code> mode&rsquo;s restrictions: the dividing line doesn&rsquo;t
+go from corner to corner in the box: to correct this requires revision
+of <i>slashbox</i> &mdash; <i>pict2e</i> alone doesn&rsquo;t help in this
+regard.)
+<dl>
+<dt><tt><i>slashbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.zip">macros/latex/contrib/slashbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/slashbox/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html
new file mode 100644
index 00000000000..2cec4a4dcc4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html
@@ -0,0 +1,87 @@
+<head>
+<title>UK TeX FAQ -- question label slidecls</title>
+</head><body>
+<h3>Producing slides</h3>
+<p/>Lamport&rsquo;s original LaTeX had a separate program (SliTeX) 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
+LaTeX2e came along, the reason SliTeX had to be a separate
+program went away, and its functionality was supplied by the
+<i>slides</i> class.  While this makes life a little easier for
+system administrators, it does nothing for the inferior functionality
+of the class: no-one &ldquo;who knows&rdquo; uses <i>slides</i> nowadays.
+<p/>The &lsquo;classic&rsquo; alternatives have been <i>seminar</i> and <i>foils</i>
+(originally known as FoilTeX).  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).
+<p/>The advent of Microsoft <i>PowerPoint</i> (feeble though early
+versions of it were) has created a demand for &ldquo;dynamic&rdquo; slides &mdash;
+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 <i>slides</i>, <i>foils</i> and <i>seminar</i> were designed.
+<p/>The <i>prosper</i> class builds on <i>seminar</i> to provide dynamic
+effects and the like; it retains the ability to provide PDF for
+a projected presentation, or to print foils for a foil-based
+presentation.  The add-on package <i>ppr-prv</i> adds &ldquo;preview&rdquo;
+facilities (that which is commonly called &ldquo;hand-out printing&rdquo;).  The
+<i>HA-prosper</i> package, which you load with <i>prosper</i>,
+mends a few bugs, and adds several facilities and slide design styles.
+The (relatively new) <i>powerdot</i> class is designed as a
+replacement for <i>prosper</i> and <i>HA-prosper</i>, co-authored
+by the author of <i>HA-prosper</i>.
+<p/><i>Beamer</i> is a relatively easy-to-learn, yet powerful, class that
+(as its name implies) was designed for use with projection displays.
+It needs the <i>pgf</i> package (for graphics support), which in
+turn requires <i>xcolor</i>; while this adds to the tedium of
+installing <i>beamer</i> &ldquo;from scratch&rdquo;, both are good additions to
+a modern LaTeX installation.  <i>Beamer</i> has reasonable
+facilities for producing printed copies of slides.
+<p/><i>Talk</i> is another highly functional, yet easy-to-learn class
+which claims to differ from the systems mentioned above, such as
+<i>beamer</i>, in that it doesn&rsquo;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 <i>greybars</i>: the author
+hopes users will contribute their own styles, based on
+<i>greybars</i>.)
+<p/><i>Ppower4</i> (commonly known as <i>pp4</i>) is a
+<i>Java</i>-based support program that will postprocess
+PDF, to &lsquo;animate&rsquo; the file at places you&rsquo;ve marked with
+commands from one of the <i>pp4</i> packages.  The commands don&rsquo;t
+work on PDF that has come from <i>dvips</i> output; they
+work with PDF generated by PDFLaTeX, VTeX LaTeX, or
+<i>dvipdfm</i> running on LaTeX output.
+<p/><i>Pdfscreen</i> and <i>texpower</i> are add-on packages that
+permit dynamic effects in documents formatted in &ldquo;more modest&rdquo;
+classes; <i>pdfscreen</i> will even allow you to plug
+&ldquo;presentation effects&rdquo; into an <i>article</i>-class document.
+<p/>
+
+<p/>A more detailed examination of the alternatives (including examples
+of code using many of them) may be found at Michael Wiedmann&rsquo;s fine
+<a href="http://www.miwie.org/presentations/presentations.html">http://www.miwie.org/presentations/presentations.html</a>
+<p/>ConTeXt users will find that much (if not all) of what they need is
+already in ConTeXt itself; there&rsquo;s a useful summary of what&rsquo;s
+available, with examples, in
+<a href="http://wiki.contextgarden.net/Presentation_Styles">http://wiki.contextgarden.net/Presentation_Styles</a>
+
+<dl>
+<dt><tt><i>beamer.cls</i></tt><dd>Download all of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.zip">macros/latex/contrib/beamer</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/beamer/">browse</a>)
+<dt><tt><i>foils.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/foiltex.zip">macros/latex/contrib/foiltex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/foiltex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/foiltex/">browse</a>)
+<dt><tt><i>greybars.sty</i></tt><dd>distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.zip">macros/latex/contrib/talk</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/talk/">browse</a>)
+<dt><tt><i>HA-prosper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.zip">macros/latex/contrib/ha-prosper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ha-prosper/">browse</a>)
+
+<dt><tt><i>seminar.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse</a>)
+<dt><tt><i>pgf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>)
+<dt><tt><i>powerdot.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/powerdot.zip">macros/latex/contrib/powerdot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/powerdot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/powerdot/">browse</a>)
+<dt><tt><i>pp4</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ppower4.zip">support/ppower4</a> (<a href="ftp://cam.ctan.org/tex-archive/support/ppower4.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/ppower4/">browse</a>)
+<dt><tt><i>ppr-prv.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ppr-prv.zip">macros/latex/contrib/ppr-prv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ppr-prv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ppr-prv/">browse</a>)
+<dt><tt><i>prosper.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/prosper.zip">macros/latex/contrib/prosper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/prosper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/prosper/">browse</a>)
+<dt><tt><i>talk.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.zip">macros/latex/contrib/talk</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/talk/">browse</a>)
+<dt><tt><i>texpower</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.zip">macros/latex/contrib/texpower</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/texpower/">browse</a>)
+<dt><tt><i>xcolor.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.zip">macros/latex/contrib/xcolor</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xcolor/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html
new file mode 100644
index 00000000000..f39dca0af3d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label sortbib</title>
+</head><body>
+<h3>Sorting lists of citations</h3>
+<p/>BibTeX has a sorting function, and most BibTeX styles sort the
+citation list they produce; most people find this desirable.
+<p/>However, it is perfectly possible to write a
+<code>thebibliography</code> environment that <em>looks</em> as if it
+came from BibTeX, and many people do so (in order to save time in
+the short term).
+<p/>The problem arises when <code>thebibliography</code>-writers decide
+their citations need to be sorted.  A common misapprehension is to
+insert <code>\</code><code>bibliographystyle{alpha}</code> (or similar) and expect
+the typeset output to be sorted in some magical way.  BibTeX
+doesn&rsquo;t work that way! &mdash; if you write <code>thebibliography</code>,
+you get to sort its contents.  BibTeX will only sort the contents
+of a <code>thebibliography</code> environment when it creates it, to
+be inserted from a <code>.bbl</code> file by a <code>\</code><code>bibliography</code> command.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html
new file mode 100644
index 00000000000..d4f7d75150b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html
@@ -0,0 +1,17 @@
+<head>
+<title>UK TeX FAQ -- question label spaftend</title>
+</head><body>
+<h3>There&rsquo;s a space added after my environment</h3>
+<p/>You&rsquo;ve written your own environment <code>env</code>, and it works
+except that a space appears at the start of the first line of typeset
+text after <code>\</code><code>end{env}</code>.  This doesn&rsquo;t happen with similar
+LaTeX-supplied environments.
+<p/>You could impose the restriction that your users always put a
+&ldquo;<code>%</code>&rdquo; sign after the environment ... but
+LaTeX environments don&rsquo;t require that, either.
+<p/>The LaTeX environments&rsquo; &ldquo;secret&rdquo; is an internal flag which causes
+the unwanted spaces to be ignored.  Fortunately, you don&rsquo;t have to use
+the internal form: since 1996, LaTeX has had a user command
+<code>\</code><code>ignorespacesafterend</code>, which sets the internal flag.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html
new file mode 100644
index 00000000000..bc6435d4918
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label specials</title>
+</head><body>
+<h3><code>\</code><code>special</code> commands</h3>
+<p/>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 PostScript figures into
+documents, or how to set the colour of printed text; but some device
+drivers do.
+<p/>Instructions for such things are introduced to your document by means
+of <code>\</code><code>special</code> commands; all that TeX does with these commands is
+to expand their 
+arguments and then pass the command to the DVI file.  In most
+cases, there are macro packages provided (often with the driver) that
+provide a human-friendly interface to the <code>\</code><code>special</code>; for example,
+there&rsquo;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.  LaTeX2e
+has standard graphics and colour packages that make figure inclusion,
+rotation and scaling, and colour typesetting relatively
+straightforward, despite the rather daunting <code>\</code><code>special</code> commands
+involved.  (ConTeXt provides similar support, though not by way of
+packages.)
+<p/>The allowable arguments of <code>\</code><code>special</code> depend on the device driver
+you&rsquo;re using.  Apart from the examples above, there are <code>\</code><code>special</code>
+commands in the emTeX drivers (e.g., <i>dvihplj</i>, <i>dviscr</i>,
+<em>etc</em>.) that will draw lines at arbitrary orientations, and
+commands in <i>dvitoln03</i> that permit the page to be set in
+landscape orientation.
+<p/>Note that <code>\</code><code>special</code> provides rather different facilities in PDFTeX
+operation: since there is no device driver around, in this context.
+In PDFTeX, <code>\</code><code>special</code> is only needed to generated PDF for
+which there is no existing defined PDFTeX operation.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html
new file mode 100644
index 00000000000..ae6333b3514
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html
@@ -0,0 +1,36 @@
+<head>
+<title>UK TeX FAQ -- question label spell</title>
+</head><body>
+<h3>Spelling checkers for work with TeX</h3>
+<p/>For Unix, <i>ispell</i> was long the program of choice; it is well
+integrated with <i>emacs</i>, and deals with some TeX syntax.
+However, it has more-or-less been replaced everywhere, by
+<i>aspell</i>, which was designed as a successor, and certainly
+performs better on most metrics; there remains some question as to its
+performance with (La)TeX sources.
+<p/>For Windows, there is a good spell checker incorporated into many of
+the <a href="FAQ-editors.html">shell/editor</a> combinations that are available.
+The spell checker from the (now defunct) 4AllTeX shell remains
+available as a separate package, <i>4spell</i>.
+<p/>For the Macintosh, <i>Excalibur</i> is the program of choice.  It
+will run in native mode on both sorts of Macintosh.  The distribution
+comes with dictionaries for several languages.
+<p/>The VMS Pascal program <i>spell</i> makes special cases of
+some important features of LaTeX syntax.
+<p/>For MSDOS, there are several programs.  <i>Amspell</i> can be
+called from within an editor, and <i>jspell</i> is an extended
+version of <i>ispell</i>.
+<dl>
+<dt><tt><i>4spell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/4spell.zip">support/4spell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/4spell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/4spell/">browse</a>)
+<dt><tt><i>amspell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/amspell.zip">support/amspell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/amspell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/amspell/">browse</a>)
+<dt><tt><i>aspell</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/aspell/">support/aspell/</a> &mdash; choose just those language
+  dictionaries (under subdirectory <i>dict/</i>) that you need.
+<dt><tt><i>excalibur</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/support/excalibur/Excalibur-4.0.2.sit.hqx">systems/mac/support/excalibur/Excalibur-4.0.2.sit.hqx</a>
+<dt><tt><i>ispell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ispell/ispell-3.2.06.tar.gz">support/ispell/ispell-3.2.06.tar.gz</a>
+<dt><tt><i>jspell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/jspell.zip">support/jspell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/jspell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/jspell/">browse</a>)
+<dt><tt><i>VMS spell</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/support/vmspell.zip">support/vmspell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/vmspell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/vmspell/">browse</a>)
+<dt><tt><i>winedt</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/winedt/">systems/win32/winedt/</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html
new file mode 100644
index 00000000000..9dc949a38a4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html
@@ -0,0 +1,109 @@
+<head>
+<title>UK TeX FAQ -- question label spinmacro</title>
+</head><body>
+<h3>Spaces in macros</h3>
+<p/>It&rsquo;s very easy to write macros that produce space in the typeset
+output where it&rsquo;s neither desired nor expected.  Spaces introduced by
+macros are particularly insidious because they don&rsquo;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&rsquo;t amalgamated.
+And of course, your output can also have a space where none was wanted
+at all.
+<p/>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&rsquo;re typing macros are just the same as the rules that apply
+when you&rsquo;re typing ordinary text, and second, rules for ignoring
+spaces do <em>not</em> apply to spaces produced while a macro is being
+obeyed (&ldquo;expanded&rdquo;).
+<p/>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 &lsquo;feels as if&rsquo; spaces are ignored if
+they follow another space.  Space can have syntactic meaning after
+certain sorts of non-braced arguments (e.g., <em>count</em> and
+<em>dimen</em> variable assignments in Plain TeX) and after certain
+control words (e.g., in <code>\</code><code>hbox</code> <code>to</code>, so again we have instances
+where it &lsquo;feels as if&rsquo; spaces are being ignored when they&rsquo;re merely
+working quietly for their living.
+<p/>Consider the following macro, fairly faithfully adapted from one that
+appeared on <i>comp.text.tex</i>:
+
+<blockquote>
+<pre>
+\newcommand{\stline}[1]{ \bigskip \makebox[2cm]{ \textbf{#1} } }
+</pre>
+</blockquote><p>
+The macro definition contains five spaces:
+<ul>
+<li> after the opening <code>{</code> of the macro body; this space will be
+  ignored, not because &ldquo;because the macro appears at the start of a
+  line&rdquo;, but rather because the macro was designed to operate between
+  paragraphs
+<li> after <code>\</code><code>bigskip</code>; this space will be ignored (while the macro
+  is being defined) because it follows a command name
+<li> after the <code>{</code> of the mandatory argument of <code>\</code><code>makebox</code>; even
+  though this space will inevitably appear at the start of an output
+  line, it will <em>not</em> be ignored
+<li> after the <code>}</code> closing the argument of <code>\</code><code>textbf</code>; this space
+  will not be ignored, but may be overlooked if the argument is well
+  within the <code>2cm</code> allowed for it
+<li> after the <code>}</code> closing the mandatory argument of <code>\</code><code>makebox</code>;
+  this space will not be ignored
+</ul>
+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&rsquo;t always properly
+aligned.  These problems arose from the space at the start of the
+mandatory argument of <code>\</code><code>makebox</code> 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.
+<p/>The principal technique for suppressing spaces is the use of
+<code>%</code> characters: everything after a
+<code>%</code> 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):
+<blockquote>
+<pre>
+\newcommand{\stline}[1]{%
+  \bigskip
+  \makebox[2cm]{%
+    \textbf{#1}\relax
+  }%
+}
+</pre>
+</blockquote><p>
+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 &ldquo;belt and braces&rdquo; 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 &mdash; it&rsquo;s
+easier to blindly suppress spaces than to analyse at every point
+whether you actually need to.  Three techniques were used to suppress
+spaces:
+<ul>
+<li> placing a <code>%</code> character at the end of a line
+  (as in the 1st, 3rd and 5th lines),
+<li> ending a line &lsquo;naturally&rsquo; with a control sequence, as in line 2,
+  and
+<li> ending a line with an &lsquo;artificial&rsquo; control sequence, as in line
+  4; the control sequence in this case (<code>\</code><code>relax</code>) is a no-op in many
+  circumstances (as here), but this usage is deprecated &mdash; a
+  <code>%</code> character would have been better.
+</ul>
+Beware of the (common) temptation to place a space <em>before</em> a
+<code>%</code> character: if you do this you might as well omit
+the <code>%</code> altogether.
+<p/>In &ldquo;real life&rdquo;, 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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html
new file mode 100644
index 00000000000..a88f7736c8a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html
@@ -0,0 +1,44 @@
+<head>
+<title>UK TeX FAQ -- question label splitfoot</title>
+</head><body>
+<h3>Why does LaTeX split footnotes across pages?</h3>
+<p/>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.
+<p/>As always, the best solution is to change your text so that the
+problem doesn&rsquo;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.
+<p/>If this isn&rsquo;t possible, you might want to change LaTeX&rsquo;s perception
+of its priorities: they&rsquo;re controlled by
+<code>\</code><code>interfootnotelinepenalty</code> &mdash; the larger it is, the less willing
+LaTeX is to split footnotes.
+<p/>Setting
+<blockquote>
+<pre>
+\interfootnotelinepenalty=10000
+</pre>
+</blockquote><p>
+inhibits split footnotes altogether, which will cause &lsquo;<code>Underfull</code>
+<code>\</code><code>vbox</code>&rsquo; messages unless you also specify <code>\</code><code>raggedbottom</code>.  The
+default value of the penalty is <code>100</code>, which is rather mild.
+<p/>An alternative technique is to juggle with the actual size of the
+pages.  <code>\</code><code>enlargethispage</code> changes the size of the current page by
+its argument (for example, you might say
+<code>\</code><code>enlargethispage{<code>\</code><code>baselineskip</code>}</code> to add a single line
+to the page, but you can use any ordinary TeX length such as
+<code>15mm</code> or <code>-20pt</code> 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.
+<p/>The <i>fnbreak</i> package detects (and generates warnings about)
+split footnotes.
+<dl>
+<dt><tt><i>fnbreak.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fnbreak.zip">macros/latex/contrib/fnbreak</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fnbreak.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fnbreak/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html
new file mode 100644
index 00000000000..2ac60dbd765
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label srchpdf</title>
+</head><body>
+<h3>Searching PDF files</h3>
+<p/>In principle, you can search a PDF file: the text of the file
+is available to the viewer, and at least some viewers provide a search
+facility.  (It&rsquo;s not the fastest thing in the world, but it does help
+in some circumstances.)
+<p/>However, there is a problem: the viewer wants to look at Unicode text,
+but no ordinary TeX-based system deals in Unicode text.
+Fortunately for us Anglophones, this is is hardly ever a problem for
+our text, since even Knuth&rsquo;s &ldquo;OT1&rdquo; encoding matches ASCII (and hence
+the lowest 128 characters of Unicode) for most things printable.
+However, using the inflected characters of Continental European
+languages, or anything that doesn&rsquo;t use a Latin alphabet, there is
+potential for problems, since TeX&rsquo;s view of what a font is doesn&rsquo;t
+map PDF&rsquo;s and the reader won&rsquo;t understand...
+<p/>... Unless you use the <i>cmap</i> package with PDFLaTeX,
+that is.  The package will instruct PDFTeX to load character
+maps into your PDF for output fonts encoded according to the T1
+(Western European Languages), T2A, T2B, or T2C (Cyrillic Languages),
+or T5 (Vietnamese) encodings.  If your document uses such encodings,
+viewers that can search will use the maps to interpret what they find
+in the file.
+<p/>Unfortunately, the package only works with fonts that are directly
+encoded, such as the <i>cm-super</i> distribution.  Fonts like Adobe
+Times Roman (which are encoded for (La)TeX use via virtual fonts)
+are not amenable to this treatment.
+<dl>
+<dt><tt><i>cmap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.zip">macros/latex/contrib/cmap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cmap/">browse</a>)
+<dt><tt><i>cm-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html
new file mode 100644
index 00000000000..670afd22834
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html
@@ -0,0 +1,79 @@
+<head>
+<title>UK TeX FAQ -- question label struttab</title>
+</head><body>
+<h3>Spacing lines in tables</h3>
+<p/>(La)TeX mechanisms for maintaining the space between lines (the
+&ldquo;<em>leading</em>&rdquo;) rely on TeX&rsquo;s paragraph builder, which compares
+the shape of consecutive lines and adjusts the space between them.
+<p/>These mechanisms can&rsquo;t work in exactly the same way when (La)TeX is
+building a table, because the paragraph builder doesn&rsquo;t get to see the
+lines themselves.  As a result, tables sometimes typeset with lines
+uncomfortably close together (or occasionally ridiculously far apart).
+<p/>Traditional (moving metal type) typographers would adjust the spacing
+between lines of a table by use of a &ldquo;<em>strut</em>&rdquo; (a metal
+spacer).  A TeX user can do exactly the same thing: most macro
+packages define a <code>\</code><code>strut</code> command, that defines a space appropriate
+to the current size of the text; placing a <code>\</code><code>strut</code> command at the
+end of a troublesome row is the simplest solution to the problem &mdash;
+if it works.  Other solutions below are LaTeX-specific, but some
+may be simply translated to Plain TeX commands.
+<p/>If your table exhibits a systematic problem (i.e., every row is wrong
+by the same amount) use <code>\</code><code>extrarowheight</code>, which is defined by the
+<i>array</i> package:
+<blockquote>
+<pre>
+\usepackage{array}% in the preamble
+...
+\setlength{\extrarowheight}{length}
+\begin{tabular}{....}
+</pre>
+</blockquote><p>
+<p/>To correct a single row whose maladjustment isn&rsquo;t corrected by a
+<code>\</code><code>strut</code> command, you can define your own, using
+<code>\</code><code>rule{0pt}{length}</code> &mdash; which is a near approximation to the
+command that goes inside a <code>\</code><code>strut</code>.  The <i>bigstrut</i> package
+defines a strut command that you can use for this purpose:
+<code>\</code><code>bigstrut</code> on its own opens up both above and below the current
+line; <code>\</code><code>bigstrut[t]</code> opens up above the line,
+<code>\</code><code>bigstrut[b]</code> opens up below the line.
+<p/>General solutions are available, however.  The <i>tabls</i> package
+automatically generates an appropriately-sized strut at the end of
+each row.  Its disadvantages are that it&rsquo;s really rather slow in
+operation (since it gets in the way of everything within tables) and
+its (lack of) compatibility with other packages.
+<p/>The <i>cellspace</i> package does a (possibly inferior) job by
+defining a new table/array column type &ldquo;S&rdquo;, which you apply to each
+column specification.  So, for example,
+<blockquote>
+<pre>
+\cmdinvoke{begin}{tabular}{l l l p{3cm}}
+</pre>
+</blockquote><p>
+would become
+<blockquote>
+<pre>
+\cmdinvoke{begin}{tabular}{Sl Sl Sl Sp{3cm}}
+</pre>
+</blockquote><p>
+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.
+<p/>The <i>booktabs</i> 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&rsquo;s thesis,
+that LaTeX users tend too often to rule their tables, is
+interesting.  The package provides rule commands to support the
+author&rsquo;s scheme, but deals with inter-row spacing too.  The most
+recent release of <i>booktabs</i> sports compatibility with
+packages such as <i>longtable</i>.
+<p/>Documentation of both <i>bigstrut</i> and <i>tabls</i> may be
+found as comments in the package files themselves.
+<dl>
+<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>)
+<dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>)
+<dt><tt><i>cellspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.zip">macros/latex/contrib/cellspace</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cellspace/">browse</a>)
+<dt><tt><i>tabls.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/tabls.sty">macros/latex/contrib/misc/tabls.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html
new file mode 100644
index 00000000000..b93f11eb629
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label subsubsub</title>
+</head><body>
+<h3>How to create a <code>\</code><code>subsubsubsection</code></h3>
+<p/>LaTeX&rsquo;s set of &ldquo;sections&rdquo; stops at the level of
+<code>\</code><code>subsubsection</code>.  This reflects a design decision by Lamport &mdash;
+for, after all, who can reasonably want a section with such huge
+strings of numbers in front of it?
+<p/>In fact, LaTeX standard classes <em>do</em> define &ldquo;sectioning&rdquo;
+levels lower than <code>\</code><code>subsubsection</code>, but they don&rsquo;t format them like
+sections (they&rsquo;re not numbered, and the text is run-in after the
+heading).  These deeply inferior section commands are <code>\</code><code>paragraph</code>
+and <code>\</code><code>subparagraph</code>; you can (if you <em>must</em>) arrange that these
+two commands produce numbered headings, so that you can use them as
+<code>\</code><code>subsubsubsection</code>s and lower.
+<p/>The <i>titlesec</i> allows you to adjust the definitions of the
+sectioning macros, and it may be used to
+transform a <code>\</code><code>paragraph</code>&rsquo;s typesetting so that it looks like that
+of a <code>\</code><code>section</code>.
+<p/>If you want to program the change yourself, you&rsquo;ll find that the
+commands (<code>\</code><code>section</code> all the way down to <code>\</code><code>subparagraph</code>) are
+defined in terms of the internal <code>\</code><code>@startsection</code> command, which
+takes 6 arguments.  Before attempting this sort of work, you are well
+advised to read the LaTeX sources (<i>ltsect.dtx</i> in the
+LaTeX distribution) and the source of the standard packages
+(<i>classes.dtx</i>).  The <a href="FAQ-books.html">LaTeX Companion</a>
+discusses use of <code>\</code><code>@startsection</code> for this sort of thing.
+<dl>
+<dt><tt><i>LaTeX source</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>)
+<dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html
new file mode 100644
index 00000000000..6becedead22
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label subverttoks</title>
+</head><body>
+<h3>Subverting a token register</h3>
+<p/>A common requirement is to &ldquo;subvert&rdquo; a token register that other
+macros may use.  The requirement arises when you want to add something
+to a system token register (<code>\</code><code>output</code> or <code>\</code><code>every*</code>), but know
+that other macros use the token register, too.  (A common requirement
+is to work on <code>\</code><code>everypar</code>, but LaTeX changes <code>\</code><code>everypar</code> at
+every touch and turn.)
+<p/>The following technique, due to David Kastrup, does what you need, and
+allows an independent package to play the exact same game:
+<blockquote>
+<pre>
+\let\mypkg@@everypar\everypar
+\newtoks\mypkg@everypar
+\mypkg@everypar\expandafter{\the\everypar}
+\mypkg@@everypar{\mypkgs@ownstuff\the\mypkg@everypar}
+\def\mypkgs@ownstuff{%
+  &lt;stuff to do at the start of the token register&gt;%
+}
+\let\everypar\mypkg@everypar
+</pre>
+
+</blockquote><p>
+As you can see, the package (<i>mypkg</i>)
+<ul>
+<li> creates an alias for the existing &ldquo;system&rdquo; <code>\</code><code>everypar</code>
+  (which is frozen into any surrounding environment, which will carry
+  on using the original);
+<li> creates a token register to subvert <code>\</code><code>everypar</code> and
+  initialises it with the current contents of <code>\</code><code>everypar</code>;
+<li> sets the &ldquo;old&rdquo; <code>\</code><code>everypar</code> to execute its own extra code,
+  as well as the contents of its own token register;
+<li> defines the macro for the extra code; and
+<li> points the token <code>\</code><code>everypar</code> at the new token register.
+</ul>
+and away we go.
+<p/>The form <code>\</code><code>mypkg@...</code> is (sort of) blessed for LaTeX package
+internal names, which is why this example uses macros of that form.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html
new file mode 100644
index 00000000000..455acf5f569
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label symbols</title>
+</head><body>
+<h3>Where can I find the symbol for ...</h3>
+<!-- assignment circular integral degrees diagonal dots Fourier transform -->
+<!-- Laplace greater less complex integer natural real -->
+<!-- cent euro -->
+<p/>There is a wide range of symbols available for use with TeX, most
+of which are not shown (or even mentioned) in (La)TeX books.
+<em>The Comprehensive LaTeX Symbol List</em> (by Scott Pakin
+
+<em>et al.</em>) illustrates over 2000 symbols, and details the
+commands and packages needed to produce them.
+<p/>Other questions in this FAQ offer specific help on kinds of
+symbols:
+<ul>
+<li> <a href="FAQ-scriptfonts.html">Script fonts for mathematics</a>
+<li> <a href="FAQ-numbersets.html">Fonts for the number sets</a>
+<li> <a href="FAQ-prinvalint.html">Typesetting the principal value integral</a>
+</ul>
+<dl>
+<dt><tt><i>Symbol List</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/symbols/comprehensive/">info/symbols/comprehensive/</a>; there are processed
+  versions in both PostScript and PDF forms for both A4 and
+  letter paper.
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html
new file mode 100644
index 00000000000..e4512fbd8d0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html
@@ -0,0 +1,27 @@
+<head>
+<title>UK TeX FAQ -- question label t1enc</title>
+</head><body>
+<h3>Why use <i>fontenc</i> rather than <i>t1enc</i>?</h3>
+<p/>In the very earliest days of LaTeX2e, the only way to use the
+T1 encoding was <i>t1enc</i>; with the summer 1994
+&ldquo;production&rdquo; release, the <i>fontenc</i> package appeared, and
+provided comprehensive support for use of the encoding.
+<p/>Nevertheless, the <i>t1enc</i> package remains (as part of the
+LaTeX 2.09 compatibility code), but it does very little: it merely
+selects font encoding T1, and leaves to the user the business
+of generating the character codes required.
+<p/>Generating such character codes could be a simple matter, <em>if</em>
+the T1 encoding matched any widely-supported encoding standard,
+since in that case, one might expect one&rsquo;s keyboard to generate the
+character codes.  However, the T1 encoding is a mix of several
+standard encodings, and includes code points in areas of the table
+which standard encodings specifically exclude, so no T1
+keyboards have been (or ever will be) manufactured.
+<p/>By contrast, the <i>fontenc</i> package generates the T1
+code points from ordinary LaTeX commands (e.g., it generates the
+<code>&eacute;</code> character codepoint from the command <code>\&rsquo;</code><code>e</code>).  So, unless you
+have program-generated T1 input, use
+<code>\</code><code>usepackage[T1]{fontenc}</code> rather than
+<code>\</code><code>usepackage{t1enc}</code>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html
new file mode 100644
index 00000000000..5b1e5fd09f1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label tabacc</title>
+</head><body>
+<h3>Accents misbehave in <code>tabbing</code></h3>
+<p/>So you are constructing a <code>tabbing</code> environment, and you
+have the need of some diacriticised text &mdash; perhaps something as simple
+as <code>\</code><code>&rsquo;{e}</code> &mdash; and the accent disappears because it has been
+interpreted as a <code>tabbing</code> command, and everything goes
+wrong.
+<p/>This is really a rather ghastly feature of the <code>tabbing</code>
+environment; in order to type accented characters you need to use the
+<code>\</code><code>a</code> kludge: so <code>\</code><code>a&rsquo;{e}</code> inside <code>tabbing</code> for
+<code>\</code><code>&rsquo;{e}</code> outside, and similarly <code>\</code><code>a&lsquo;</code> for <code>\</code><code>&lsquo;</code> and <code>\</code><code>a=</code>
+for <code>\</code><code>=</code>.  This whole procedure is of course hideous and
+error-prone.
+<p/>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 <i>inputenc</i> package.  So for example,
+type:
+<blockquote>
+  <code>\</code><code>usepackage[latin1]{inputenc}</code><br>
+  <code>...</code><br>
+  <code>\</code><code>begin{tabbing}</code><br>
+  <code>...</code><br>
+  <code>...</code> <code>\</code><code>&gt;</code> <code>voil&agrave;</code> <code>\</code><code>&gt;</code> <code>...</code>
+</blockquote><p>
+for:
+<blockquote>
+  ...\quad voil&agrave;\quad ...
+</blockquote><p>
+and the internal mechanisms of the <i>inputenc</i> package will put
+the right version of the accent command in there.
+<p/>A witty reversal of the r\^oles is introduced by the package
+<i>Tabbing</i> (note the capital &ldquo;T&rdquo;): it provides a
+<code>Tabbing</code> environment which duplicates
+<code>tabbing</code>, but all the single-character commands become
+complicated objects.  So <code>tabbing</code>&rsquo;s <code>\</code><code>&gt;</code> becomes
+<code>\</code><code>TAB&gt;</code>, <code>\</code><code>=</code> becomes <code>\</code><code>TAB=</code>, and so on.  The above trivial
+example would therefore become:
+<blockquote>
+<pre>
+\usepackage{Tabbing}
+...
+\begin{Tabbing}
+  ...  ... \TAB&gt; voil\`a \TAB&gt; ...
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>Tabbing.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.zip">macros/latex/contrib/Tabbing</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/Tabbing/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html
new file mode 100644
index 00000000000..5687db12009
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html
@@ -0,0 +1,73 @@
+<head>
+<title>UK TeX FAQ -- question label tabcellalign</title>
+</head><body>
+<h3>How to alter the alignment of tabular cells</h3>
+<p/>One often needs to alter the alignment of a tabular <code>p</code> (&lsquo;paragraph&rsquo;)
+cell, but problems at the end of a table row are common.  With a
+<code>p</code> cell that looks like:
+<blockquote>
+<pre>
+... & \centering blah ... \\
+</pre>
+</blockquote><p>
+one is liable to encounter errors that complain about a &ldquo;misplaced
+<code>\</code><code>noalign</code>&rdquo; or &ldquo;<a href="FAQ-altabcr.html">extra alignment tab</a>&rdquo;, or the like.
+The problem is that the command <code>\\</code> means different things in
+different circumstances: the <code>tabular</code> environment
+switches the meaning to a value for use in the table, and
+<code>\</code><code>centering</code>, <code>\</code><code>raggedright</code> and <code>\</code><code>raggedleft</code> 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 <code>&amp;</code> (or <code>\\</code>) that
+terminates it. 
+<p/><p/>The technique using <code>\</code><code>PBS</code> was developed in the days of LaTeX 2.09
+because the actual value of <code>\\</code> that the <code>tabular</code>
+environment uses was only available as an internal command.  Nowadays,
+the value is a public command, and you can in principle use it
+explicitly:
+<blockquote>
+<pre>
+... & \centering blah ... \tabularnewline
+</pre>
+</blockquote><p>
+<p/>The <i>array</i> package provides a command <code>\</code><code>arraybackslash</code>
+which restores <code>\\</code> to its correct (within table) meaning;
+the command may be used in <i>array</i>&rsquo;s &ldquo;field format&rdquo; preamble
+specifications:
+<blockquote>
+
+<pre>
+\begin{tabular}{... &gt;{\centering\arraybackslash}p{50mm}}
+...
+</pre>
+</blockquote><p>
+<p/>The <code>\</code><code>tabularnewline</code> and <code>\</code><code>arraybackslash</code> commands are
+(somewhat) modern additions to LaTeX and the <i>array</i>
+package, respectively.  If neither is available, the user may try the
+(old) solution which preserves the meaning of <code>\\</code>:
+<blockquote>
+<pre>
+\newcommand\PBS[1]{\let\temp=\\%
+  #1%
+  \let\\=\temp
+}
+</pre>
+</blockquote><p>
+which one uses within a table as:
+<blockquote>
+<pre>
+... & \PBS\centering blah ... \\
+</pre>
+</blockquote><p>
+or in the preamble as:
+<blockquote>
+<pre>
+\begin{tabular}{...&gt;{\PBS\centering}p{5cm}}
+</pre>
+</blockquote><p>
+<dl>
+<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html
new file mode 100644
index 00000000000..bb2d5cbea86
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html
@@ -0,0 +1,19 @@
+<head>
+<title>UK TeX FAQ -- question label tds-zip</title>
+</head><body>
+<h3>Prebuilt installation files on the archive</h3>
+<p/>The <a href="FAQ-tds.html">TDS</a> is a simple structure, and almost all
+files can be installed simply by putting them in the &ldquo;right&rdquo; place,
+and updating a single index.  (Note, this simple idea typically
+doesn&rsquo;t work for fonts, unless they&rsquo;re distributed as Metafont source.)
+<p/>The CTAN network is therefore acquiring &ldquo;TDS-ZIP&rdquo; files,
+which have a built-in directory structure that matches the TDS.
+These files have to be built, and the CTAN team has asked that
+package authors supply them (the team will advise, of course, if the
+author has trouble).  Everyone hopes that the extra work involved will
+contrinute to happier lives for package users, which in turn must
+surely help keep the TeX community lively and active.
+<p/>Use of the files is discussed in 
+&ldquo;<a href="FAQ-inst-tds-zip.html">installing using preformatted ZIP files</a>&rdquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds-zip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds-zip</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html
new file mode 100644
index 00000000000..e02bfeab6fe
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html
@@ -0,0 +1,35 @@
+<head>
+<title>UK TeX FAQ -- question label tds</title>
+</head><body>
+<h3>What is the TDS?</h3>
+<p/>    TDS stands for the TeX Directory Structure, which is a standard
+way of organising all the TeX-related files on a computer system. 
+<p/>    Most modern distributions conform to the TDS, which
+provides for both a &lsquo;standard&rsquo; and a (set of) &lsquo;local&rsquo; hierarchies of
+directories containing TeX-related files. The
+TDS reserves the name <code>texmf</code> as the name of the root directory
+(folder) of the hierarchies.  Files supplied as part of the
+distribution are put into the standard hierarchy. The location of the
+standard hierarchy is system dependent, but on a Unix system it might
+be at 
+<i>/usr/local/texmf</i>, or
+<i>/usr/local/share/texmf</i>, or
+<i>/opt/texmf</i>, or
+a similar location, but in each case the TeX files will be under the 
+<i>/texmf</i> subdirectory. 
+<p/>There may be more than on &lsquo;local&rsquo; hierarchy in which additional files
+can be stored. In the extreme an installation can have a local
+hierarchy and each user can also have an individual local hierarchy. The
+location of any local hierarchy is not only system dependent but also user
+dependent. Again, though, all files should be put under a local <i>/texmf</i>
+directory.
+<p/>The TDS is published as the output of a TUG 
+<a href="FAQ-TUGstar.html">Technical Working Group</a>.
+You may browse an <a href="http://tug.org/tds/">on-line version</a> of the
+standard, and copies in several other formats (including source) are
+available on CTAN.
+<dl>
+<dt><tt><i>TDS specification</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/tds.zip">tds</a> (<a href="ftp://cam.ctan.org/tex-archive/tds.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/tds/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html
new file mode 100644
index 00000000000..486616de040
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label tempinst</title>
+</head><body>
+<h3>&ldquo;Temporary&rdquo; installation of (La)TeX files</h3>
+<p/>Operating systems and applications need to know where to find files:
+many files that they need are &ldquo;just named&rdquo; &mdash; the user doesn&rsquo;t
+necessarily know <em>where</em> 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&rsquo; &ldquo;MSDOS prompt&rdquo;) are using a shell to read what
+you type: many of the commands simply involve loading and executing a
+file, and the <code>PATH</code> variable tells the shell where to find those files.
+<p/>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 <a href="FAQ-installthings.html">installing them &lsquo;properly&rsquo;</a>.  To do
+this, we need to change the relevant path as TeX perceives it.
+However, we don&rsquo;t want to throw away TeX&rsquo;s built-in path (all of a
+sudden, TeX won&rsquo;t know how to deal with all sorts of things).
+<p/>To <em>extend</em> a TeX path, we define an operating system
+environment variable in &lsquo;path format&rsquo;, 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 &lsquo;gap to be
+filled&rsquo; at the end of the environment variable.  The syntax is simple
+(though it depends which shell you&rsquo;re actually using): so on a
+Unix-like system, using the <i>bash</i> shell, the job might be
+done like:
+<pre>
+  export TEXINPUTS=/tmp:
+</pre>
+while in a Windows system, within a MSDOS window, it would be:
+<pre>
+  set TEXINPUTS=C:/temp;
+</pre>
+In either case, we&rsquo;re asking TeX to load files from the root disc
+temporary files directory; in the Unix case, the &ldquo;empty slot&rdquo; is
+designated by putting the path separator &lsquo;<code>:</code>&rsquo; on its own at the end
+of the line, while in the Windows case, the technique is the same, but
+the path separator is &lsquo;<code>;</code>&rsquo;.
+<p/>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 &ldquo;stick&rdquo; 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 <i>autoexec.bat</i> in a Windows system, and
+reboot the system.
+<p/>While all of the above has talked about where TeX finds its macro
+files, it&rsquo;s applicable to pretty much any sort of file any
+TeX-related program reads &mdash; there are lots of these paths, and of
+their corresponding environment variables.  In a
+<i>web2c</i>-based system, the copious annotations in the
+<i>texmf.cnf</i> system configuration file help you to learn which
+path names correspond to which type of file.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texcad.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texcad.html
new file mode 100644
index 00000000000..2a000e3c3b6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texcad.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label texcad</title>
+</head><body>
+<h3>TeXCAD, a drawing package for LaTeX</h3>
+<p/>TeXCAD is a program for the 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
+<code>picture</code> environment. 
+Optionally, it can be set to include lines at all angles using 
+the emTeX driver-family
+
+<a href="FAQ-specials.html"><code>\</code><code>special</code>s</a>.
+TeXCAD is part of the emTeX distribution.
+<p/>A Unix port of the program (<i>xtexcad</i>) has been made.
+<dl>
+<dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>)
+<dt><tt><i>xtexcad</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/xtexcad/xtexcad-2.4.1.tar.gz">nonfree/graphics/xtexcad/xtexcad-2.4.1.tar.gz</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html
new file mode 100644
index 00000000000..d7149ff4db7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html
@@ -0,0 +1,33 @@
+<head>
+<title>UK TeX FAQ -- question label texinfo</title>
+</head><body>
+<h3>What is Texinfo?</h3>
+<p/>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 <code>.texi</code> or
+<code>.texinfo</code> extension.
+<p/>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 <code>@</code> rather than the <code>\</code> that&rsquo;s more commonly used in
+TeX systems.
+<p/>You can write and format Texinfo files into Info files within GNU
+<i>emacs</i>, and read them using the <i>emacs</i> Info
+reader.  You can also format Texinfo files into Info files using
+<i>makeinfo</i> and read them using <i>info</i>, so you&rsquo;re not
+dependent on <i>emacs</i>.  The distribution includes a
+<i>Perl</i> script, <i>texi2html</i>, that will convert
+Texinfo sources into HTML: the language is a far better fit to
+HTML than is LaTeX, so that the breast-beating agonies of
+<a href="FAQ-LaTeX2HTML.html">converting LaTeX to HTML</a> are largely
+avoided.
+<p/>Finally, of course, you can also print the files, or convert them to
+PDF using PDFTeX.
+<dl>
+<dt><tt><i>Texinfo distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html
new file mode 100644
index 00000000000..625db53d66d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html
@@ -0,0 +1,73 @@
+<head>
+<title>UK TeX FAQ -- question label textflow</title>
+</head><body>
+<h3>Flowing text around figures in LaTeX</h3>
+<p/>There are several LaTeX packages that purport to do this, but they
+all have their limitations because the TeX machine isn&rsquo;t really
+designed to solve this sort of problem.  Piet van Oostrum has
+conducted a survey of the available packages; he recommends:
+<dl>
+<dt><code>floatflt</code><dd> <i>floatflt</i> is an improved version
+  (for LaTeX2e) of <i>floatfig.sty</i>, and its syntax is:
+<blockquote>
+<pre>
+\begin{floatingfigure}[options]{width of figure}
+  figure contents
+\end{floatingfigure}
+</pre>
+</blockquote><p>
+
+There is a (more or less similar) <code>floatingtable</code>
+environment.
+<p/>The tables or figures can be set left or right, or alternating on
+even/odd pages in a double-sided document.
+<p/>The package works with the <code>multicol</code> package, but doesn&rsquo;t work well
+in the neighbourhood of list environments (unless you change your
+LaTeX document).
+<dt><code>wrapfig</code><dd> <i>wrapfig</i> has syntax:
+<blockquote>
+<pre>
+\begin{wrapfigure}[height of figure in lines]{l,r,...}[overhang]{width}
+  figure, caption, etc.
+\end{wrapfigure}
+</pre>
+</blockquote><p>
+    
+    The syntax of the <code>wraptable</code> environment is similar.
+<p/>    Height can be omitted, in which case it will be calculated by the
+    package; the package will use the greater of the specified and the
+    actual width.  The <code>{l,r,<em>etc</em>.}</code> parameter may
+    also be specified as <code>i</code><em>(nside)</em> or
+    <code>o</code><em>(utside)</em> 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 <code>\</code><code>caption</code> command.
+<p/>    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.
+  <dt><code>picins</code><dd> <i>Picins</i> 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:
+  <blockquote>
+    <code>\</code><code>parpic</code><code>(width,height)(x-off,y-off)[Options][Position]{Picture}</code><br>
+    <em>Paragraph text</em>
+  </blockquote><p>
+  
+  All parameters except the <em>Picture</em> 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.
+<p/>  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.
+</dl>
+<dl>
+<dt><tt><i>floatflt.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/floatflt.zip">macros/latex/contrib/floatflt</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/floatflt.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/floatflt/">browse</a>)
+<dt><tt><i>picins.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/picins.zip">macros/latex209/contrib/picins</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/picins.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/picins/">browse</a>)
+<dt><tt><i>picins documentation summary</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/picins/picins.txt">macros/latex209/contrib/picins/picins.txt</a>
+<dt><tt><i>wrapfig.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wrapfig.zip">macros/latex/contrib/wrapfig</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wrapfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wrapfig/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html
new file mode 100644
index 00000000000..129c1fe5838
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html
@@ -0,0 +1,41 @@
+<head>
+<title>UK TeX FAQ -- question label textrace</title>
+</head><body>
+<h3>Making outline fonts from Metafont</h3>
+<p/><i>TeXtrace</i>, originally developed by  P&eacute;ter Szab&oacute;, is a
+bundle of Unix scripts that use  Martin Weber&rsquo;s freeware boundary
+tracing package
+<a href="http://autotrace.sourceforge.net"><i>autotrace</a></i> to 
+generate Type 1 outline fonts from Metafont bitmap 
+font outputs.  The result is unlikely ever to be of the quality of
+the commercially-produced Type 1 font, but there&rsquo;s always the
+<a href="http://fontforge.sourceforge.net/"><i>FontForge</a></i> 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 <i>TeXtrace</i> are P&eacute;ter Szab&oacute;&rsquo;s own
+EC/TC font set <i>tt2001</i> and Vladimir Volovich&rsquo;s
+CM-Super set, which covers the EC, TC, and the
+Cyrillic LH font sets (for details of both of which sets, see
+<a href="FAQ-type1T1.html">&ldquo;8-bit&rdquo; type 1 fonts</a>).
+<p/>Another system, which arrived slightly later, is 
+<a href="http://www.cs.uu.nl/~hanwen/mftrace/"><i>mftrace</a></i>:
+this is a small <i>Python</i> program that does the same job.
+<i>Mftrace</i> may use either <i>autotrace</i> (like
+<i>TeXtrace</i>) or Peter Selinger&rsquo;s
+<a href="http://potrace.sourceforge.net"><i>potrace</a></i> to produce
+the initial outlines to process.  <i>Mftrace</i> is said to be
+more flexible, and easier to use, than is <i>TeXtrace</i>, but both systems
+are increasingly being used to provide Type 1 fonts to the public domain.
+<p/>The <i>MetaType1</i> system aims to use Metafont font sources, by way
+of MetaPost and a bunch of scripts and so on, to produce high-quality
+Type 1 fonts.  The first results, the 
+<a href="FAQ-type1T1.html"><i>Latin Modern</i> fonts</a>, are now
+well-established, and a bunch of existing designs have been reworked
+in MetaType1 format.
+<dl>
+<dt><tt><i>MetaType1</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.zip">fonts/utilities/metatype1</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/metatype1/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html
new file mode 100644
index 00000000000..7b48723f228
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label tfm</title>
+</head><body>
+<h3>What are TFM files?</h3>
+<p/>TFM stands for TeX Font Metrics; TFM files hold
+information about the sizes of the characters of the font in question,
+and about ligatures and kerns within that font.  One TFM file is
+needed for each font used by TeX, that is for each design (point)
+size for each weight for each family; each TFM file serves for all
+magnifications of &lsquo;its&rsquo; font, so that there are (typically) fewer
+TFM files than there are PK files.  TeX (LaTeX, etc.)
+itself needs only to know about the sizes of characters and their
+interactions with each other, but not what characters look like.  By
+contrast, TFM files are not, in principle, needed by the
+DVI driver, which only needs to know about the glyphs that each
+character selects, so as to print or display them.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html
new file mode 100644
index 00000000000..b7180d7fc5c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html
@@ -0,0 +1,36 @@
+<head>
+<title>UK TeX FAQ -- question label the-commands</title>
+</head><body>
+<h3>Redefining counters&rsquo; <code>\</code><code>the-</code>commands</h3>
+<p/>Whenever you request a new LaTeX counter, LaTeX creates a bunch
+of behind-the-scenes commands, as well as defining the counter
+itself.
+<p/>Among other things, <code>\</code><code>newcounter{</code><em>fred</em><code>}</code> creates a command
+<code>\</code><code>the</code><code><em>fred</em></code>, which expands to &ldquo;the value of
+<code><em>fred</em></code>&rdquo; when you&rsquo;re typesetting.
+<p/>The definition of <code>\</code><code>the</code><code><em>fred</em></code> 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
+<code>\</code><code>the</code><code><em>fred</em></code>, consider what might happen when you do
+so.
+<p/>So, for example, if you want your section numbers to be terminated by
+a period, you could make <code>\</code><code>thesection</code> expand with a terminating
+period.  However, such a change to <code>\</code><code>thesection</code> makes the
+definition of <code>\</code><code>thesubsection</code> look distinctly odd: you are going to
+find yourself redefining things left, right and centre.  Rather, use
+the standard techniques for 
+<a href="FAQ-seccntfmt.html">adjusting the presentation of section numbers</a>. 
+<p/>Or, suppose you want the page number to appear at the bottom of each
+page surrounded by dashes (as in
+&ldquo;<code>-</code><code>-~</code><code>nnn~-</code><code>-</code>&rdquo;).
+If you try to achieve this by redefining <code>\</code><code>thepage</code>, problems will
+arise from the use of the page number in the table of contents (each
+number will have the dashes attached), and <code>\</code><code>pageref</code> references
+will be oddly modified.  In this case, the change of appearance is
+best done by redefining the page style itself, perhaps using
+<a href="FAQ-fancyhdr.html">package <i>fancyhdr</i></a>.
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html
new file mode 100644
index 00000000000..ec873f2af47
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html
@@ -0,0 +1,29 @@
+<head>
+<title>UK TeX FAQ -- question label theoremfmt</title>
+</head><body>
+<h3>Theorem bodies printed in a roman font</h3>
+<p/>If you want to take advantage of the powerful <code>\</code><code>newtheorem</code> 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,
+...) then you can use the AMSLaTeX <i>amsthm</i> package
+(which now supersedes the <i>theorem</i> package previously
+recommended in these answers).
+Alternatively, the following sets up an environment
+<code>remark</code> whose content is in the default roman font.
+<blockquote>
+
+<pre>
+\newtheorem{preremark}{Remark}
+\newenvironment{remark}%
+  {\begin{preremark}\upshape}{\end{preremark}}
+</pre>
+</blockquote><p>
+The <i>ntheorem</i> package provides control of the fonts used by
+theorems, directly.
+<dl>
+<dt><tt><i>amsthm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>)
+<dt><tt><i>ntheorem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse</a>)
+<dt><tt><i>theorem.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html
new file mode 100644
index 00000000000..fe7573cc45a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label thesis</title>
+</head><body>
+<h3>Formatting a thesis in LaTeX</h3>
+<p/>Thesis styles are usually very specific to your University, so it&rsquo;s
+usually not profitable to ask around for a package outside your own
+University.  Since many Universities (in their eccentric way) still
+require double-spacing, you may care to refer to
+<a href="FAQ-linespace.html">the relevant question</a>.
+If you want to write your own, a good place to start is the University
+of California style, but it&rsquo;s not worth going to a lot of trouble. (If
+officials won&rsquo;t allow standard typographic conventions, you won&rsquo;t be
+able to produce an &aelig;sthetically pleasing document anyway!)
+<dl>
+<dt><tt><i>UC thesis style</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.zip">macros/latex/contrib/ucthesis</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ucthesis/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html
new file mode 100644
index 00000000000..6617bca3e6e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label time</title>
+</head><body>
+<h3>Printing the time</h3>
+<p/>TeX has a primitive register that contains &ldquo;the number of minutes
+since midnight&rdquo;; with this knowledge it&rsquo;s a moderately simple
+programming job to print the time (one that no self-respecting
+Plain TeX user would bother with anyone else&rsquo;s code for).
+<p/>However, LaTeX provides no primitive for &ldquo;time&rdquo;, so the
+non-programming LaTeX user needs help.
+<p/>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.
+<p/>The <i>datetime</i> package defines two time-printing functions:
+<code>\</code><code>xxivtime</code> (for 24-hour time), <code>\</code><code>ampmtime</code> (for 12-hour time) and
+<code>\</code><code>oclock</code> (for time-as-words, albeit a slightly eccentric set of
+words).
+<p/>The <i>scrtime</i> package (part of the compendious
+<i>KOMA-Script</i> bundle) takes a package option (<code>12h</code> or
+<code>24h</code>) to specify how times are to be printed.  The command
+<code>\</code><code>thistime</code> then prints the time appropriately (though there&rsquo;s no
+<em>am</em> or <em>pm</em> in <code>12h</code> mode).  The <code>\</code><code>thistime</code>
+command also takes an optional argument, the character to separate the
+hours and minutes: the default is of course <code>:</code>.
+<dl>
+<dt><tt><i>datetime.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/datetime.zip">macros/latex/contrib/datetime</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/datetime.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/datetime/">browse</a>)
+<dt><tt><i>scrtime.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html
new file mode 100644
index 00000000000..8d30d1c7ef1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label titlsty</title>
+</head><body>
+<h3>The style of document titles</h3>
+<p/>The <i>titling</i> package provides a number of facilities that
+permit manipulation of the appearance of a <code>\</code><code>maketitle</code> command, the
+<code>\</code><code>thanks</code> commands within it, and so on.  The package also defines a
+<code>titlingpage</code> environment, that offers something in between the
+standard classes&rsquo; <code>titlepage</code> option and the <code>titlepage</code>
+environment, and is itself somewhat configurable.
+<p/>The memoir class includes all the functionality of the
+<i>titling</i> package, while the <i>KOMA-script</i> classes have
+their own range of different titling styles.
+<p/>Finally, the indefatigable Vincent Zoonekynd supplies examples of how
+to program alternative 
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html">title styles</a>.
+The web page is not useful to users unless they are willing to do
+their own LaTeX programming.
+<dl>
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>titling.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titling.zip">macros/latex/contrib/titling</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titling.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titling/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html
new file mode 100644
index 00000000000..681de21a071
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label tmupfl</title>
+</head><body>
+<h3>&ldquo;Too many unprocessed floats&rdquo;</h3>
+<p/>If LaTeX responds to a <code>\</code><code>begin{figure}</code> or
+<code>\</code><code>begin{table}</code> command with the error message
+<pre>
+! LaTeX Error: Too many unprocessed floats.
+
+See the LaTeX manual or LaTeX Companion for explanation.
+</pre>
+
+your figures (or tables) are failing to be placed properly.  LaTeX
+has a limited amount of storage for &lsquo;floats&rsquo; (figures, tables, or
+floats you&rsquo;ve defined yourself with the <i>float</i> package); if
+you don&rsquo;t let it ever actually typeset any floats, it will run out of
+space.
+<p/>This failure usually occurs in extreme cases of
+
+
+<a href="FAQ-floats.html">floats moving &ldquo;wrongly&rdquo;</a>;
+LaTeX has found it can&rsquo;t place a float, and floats of the same type
+have piled up behind it.  LaTeX&rsquo;s idea is to ensure that caption
+numbers are sequential in the document: the caption number is
+allocated when the figure (or whatever) is created, and can&rsquo;t be
+changed, so that placement out of order would mean figure numbers
+appearing out of order in the document (and in the list of figures, or
+whatever).  So a simple failure to place a figure means that no
+subsequent figure can be placed; and hence (eventually) the error.
+<p/>Techniques for solving the problem are discussed in the
+
+<a href="FAQ-floats.html">floats question</a>
+already referenced.
+<p/>The error also occurs in a 
+long sequence of <code>figure</code> or <code>table</code>
+environments, with no intervening
+text.  Unless the environments will fit &ldquo;here&rdquo; (and you&rsquo;ve allowed
+them to go &ldquo;here&rdquo;), 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&rsquo;t all fit &ldquo;here&rdquo; if the sequence is
+sufficiently prolonged: once the page fills, LaTeX won&rsquo;t place any
+more floats, leading to the error.
+<p/>Techniques for resolution may involve redefining the floats using the
+<i>float</i> package&rsquo;s <code>[H]</code> float qualifier, but you are unlikely
+to get away without using <code>\</code><code>clearpage</code> from time to time.
+<dl>
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html
new file mode 100644
index 00000000000..39104b0ba0b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html
@@ -0,0 +1,58 @@
+<head>
+<title>UK TeX FAQ -- question label toascii</title>
+</head><body>
+<h3>Conversion from (La)TeX to plain text</h3>
+<p/>The aim here is to emulate the Unix <i>nroff</i>, which formats
+text as best it can for the screen, from the same
+input as the Unix typesetting program <i>troff</i>.
+<p/>Converting DVI to plain text is the basis of many of these
+techniques; sometimes the simple conversion provides a good enough
+response.  Options are:
+<ul>
+<li> <i>dvi2tty</i> (one of the earliest),
+<li> <i>crudetype</i> and
+<li> <i>catdvi</i>, which is capable of generating Latin-1
+  (ISO 8859-1) or UTF-8 encoded output.  <i>Catdvi</i> was
+  conceived as a replacement for <i>dvi2tty</i>, but can&rsquo;t (quite)
+  be recommended as a complete replacement yet.
+</ul>
+A common problem is the hyphenation that TeX inserts when
+typesetting something: since the output is inevitably viewed using
+fonts that don&rsquo;t match the original, the hyphenation usually looks
+silly.
+<p/>Ralph Droms provides a <i>txt</i> bundle of things in support of
+ASCII generation,
+but it doesn&rsquo;t do a good job with tables and mathematics.  An
+alternative is the <i>screen</i> package.
+<p/>Another possibility is to
+use the LaTeX-to-ASCII conversion program, <i>l2a</i>,
+although this is really more of a de-TeXing program.
+<p/>The canonical de-TeXing program is <i>detex</i>, 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&rsquo;s only usable
+for preparing useful ASCII versions of a document in highly
+restricted circumstances.
+<p/><i>Tex2mail</i> is slightly more than a de-TeXer &mdash; it&rsquo;s a
+<i>Perl</i> script that converts TeX files into
+plain text files, expanding various mathematical symbols
+(sums, products, integrals, sub/superscripts, fractions, square
+roots, ...) into &ldquo;ASCII art&rdquo; that spreads over
+multiple lines if necessary. The result is more readable to human
+beings than the flat-style TeX code.
+<p/>Another significant possibility is to use one of the
+<a href="FAQ-LaTeX2HTML.html">HTML-generation solutions</a>,
+and then to use a browser such as <i>lynx</i> to dump the resulting
+HTML as plain text.
+<dl>
+<dt><tt><i>catdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse</a>)
+<dt><tt><i>crudetype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.zip">dviware/crudetype</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/crudetype/">browse</a>)
+<dt><tt><i>detex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/detex.zip">support/detex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/detex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/detex/">browse</a>)
+<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.zip">dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2tty/">browse</a>)
+<dt><tt><i>l2a</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/l2a.zip">support/l2a</a> (<a href="ftp://cam.ctan.org/tex-archive/support/l2a.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/l2a/">browse</a>)
+<dt><tt><i>screen.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/misc/screen.sty">macros/latex209/contrib/misc/screen.sty</a>
+<dt><tt><i>tex2mail</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tex2mail.zip">support/tex2mail</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tex2mail.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tex2mail/">browse</a>)
+<dt><tt><i>txt</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/txt.zip">support/txt</a> (<a href="ftp://cam.ctan.org/tex-archive/support/txt.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/txt/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html
new file mode 100644
index 00000000000..4e8fc66bf64
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label tocbibind</title>
+</head><body>
+<h3>Bibliography, index, etc., in TOC</h3>
+<p/>The standard LaTeX classes (and many others) use <code>\</code><code>section*</code> or
+<code>\</code><code>chapter*</code> 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&rsquo;t numbered (which most people don&rsquo;t mind),
+and (more importantly) they don&rsquo;t appear in the table of contents.
+<p/>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 (<code>\</code><code>addcontentsline</code>) 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 <i>report</i>
+or <i>book</i>, for example), the text:
+<blockquote>
+<pre>
+\bibliography{frooble}
+\addcontentsline{toc}{chapter}{Bibliography}
+</pre>
+</blockquote><p>
+will produce the <em>wrong</em> answer if the bibliography is more than
+one page long.  Instead, one should say:
+<blockquote>
+<pre>
+\cleardoublepage
+\addcontentsline{toc}{chapter}{Bibliography}
+\bibliography{frooble}
+</pre>
+</blockquote><p>
+(Note that <code>\</code><code>cleardoublepage</code> does the right thing, even if your
+document is single-sided &mdash; in that case, it&rsquo;s a synonym for
+<code>\</code><code>clearpage</code>).  Ensuring that the entry refers to the right place is
+trickier still in a <code>\</code><code>section</code>-based class.
+<p/>If you are using <i>hyperref</i> (which will link entries in the
+table of contents to the relevant place in the file), a slight
+adjustment is necessary:
+<blockquote>
+<pre>
+\cleardoublepage
+\phantomsection
+\addcontentsline{toc}{chapter}{Bibliography}
+\bibliography{frooble}
+</pre>
+</blockquote><p>
+The extra command (<code>\</code><code>phantomsection</code>) gives <i>hyperref</i>
+something to &ldquo;hold on to&rdquo; when making the link.
+<p/>The common solution, therefore, is to use the <i>tocbibind</i>
+package, which provides many facilities to control the way these
+entries appear in the table of contents.
+<p/>Classes of the <i>KOMA-script</i> bundle provide this functionality
+as a set of class options (e.g., <code>bibtotoc</code> to add the
+bibliography to the table of contents); the <i>memoir</i> class includes
+<i>tocbibind</i> itself.
+<dl>
+<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>)
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html
new file mode 100644
index 00000000000..c82806db738
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html
@@ -0,0 +1,32 @@
+<head>
+<title>UK TeX FAQ -- question label tocloft</title>
+</head><body>
+<h3>The format of the Table of Contents, etc.</h3>
+<p/>The formats of entries in the table of contents (TOC) are
+controlled by a number of internal commands (discussed in section 2.3
+of <a href="FAQ-books.html"><em>The LaTeX Companion</em></a>.  The commands
+<code>\</code><code>@pnumwidth</code>, <code>\</code><code>@tocrmarg</code> and <code>\</code><code>@dotsep</code> 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 <code>\</code><code>l@<em>xxx</code></em>, where <code><em>xxx</em></code>
+is the name of a sectional heading (such as <code>chapter</code> or
+<code>section</code>, ...) 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.
+<p/>Alternatively, the package <i>tocloft</i> provides a set of
+user-level commands that may be used to change the 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.
+<p/>The <i>KOMA-Script</i> classes provides an optional variant structure
+for the table of contents, and calculates the space needed for the
+numbers automatically.  The <i>memoir</i> class includes the functionality
+of <i>tocloft</i>.
+<dl>
+<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>tocloft.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocloft.zip">macros/latex/contrib/tocloft</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocloft.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocloft/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html
new file mode 100644
index 00000000000..99f465581e9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label tocloftwrong</title>
+</head><body>
+<h3>Numbers too large in table of contents, etc.</h3>
+<p/>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 <em>not</em> react to the sizes of things in them,
+as they would if a <code>tabular</code> environment (or something
+similar) was used.
+<p/>This arrangement can provoke problems, most commonly with deep section
+nesting or very large page numbers: the numbers in question just don&rsquo;t
+fit in the space allowed for them in the class.
+<p/>A separate answer discusses 
+ 
+<a href="FAQ-tocloft.html">re-designing the tables</a>
+and those techniques can be employed to make the numbers fit.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html
new file mode 100644
index 00000000000..cd84fa8cb06
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html
@@ -0,0 +1,58 @@
+<head>
+<title>UK TeX FAQ -- question label toodeep</title>
+</head><body>
+<h3>&ldquo;Too deeply nested&rdquo;</h3>
+<p/>This error appears when you start a LaTeX list.
+<p/>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 <code>list</code> environment (the
+basis for list environments like <code>itemize</code> and
+<code>enumerate</code>) &ldquo;knows&rdquo; there are only 6 of these sets.
+<p/>There are also different label definitions for the
+<code>enumerate</code> and <code>itemize</code> environments at
+their own private levels of nesting.  Consider this example:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+In the example,
+<ul>
+<li> the first <code>enumerate</code> has labels as for a
+  first-level <code>enumerate</code>, and is indented as for a
+  first-level list;
+<li> the first <code>itemize</code> has labels as for a first level
+  <code>itemize</code>, and is indented as for a second-level list;
+  and
+<li> the second <code>enumerate</code> has labels as for a
+  second-level <code>enumerate</code>, and is indented as for a
+  third-level list.
+</ul>
+Now, as well as LaTeX <em>knowing</em> that there are 6 sets of
+parameters for indentation, it also <em>knows</em> that there are only
+4 types of labels each, for the environments <code>enumerate</code>
+and <code>itemize</code> (this &ldquo;knowledge&rdquo; spells out a requirement
+for class writers, since the class supplies the sets of parameters).
+<p/>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 <code>enumerate</code> environments
+somewhere among the set of nested lists, and try to add another one;
+and we can have 4 <code>itemize</code> environments somewhere among
+the set of nested lists, and try to add another one.
+<p/>What can be done about the problem?  Not much, short of rewriting
+LaTeX &mdash; you really need to rewrite your document in a slightly
+less labyrinthine way.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html
new file mode 100644
index 00000000000..05632d25f2f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html
@@ -0,0 +1,52 @@
+<head>
+<title>UK TeX FAQ -- question label topgraph</title>
+</head><body>
+<h3>Top-aligning imported graphics</h3>
+<p/>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 <code>\</code><code>raisebox</code> commands...)
+<p/>Most imported graphics have their base-line set at the bottom of the
+picture.  When using packages such as <i>subfig</i>, one often
+wants to align figures by their tops.  The following odd little bit of
+code does this:
+<blockquote>
+<pre>
+\vtop{%
+  \vskip0pt
+  \hbox{%
+    \includegraphics{figure}%
+  }%
+}
+</pre>
+</blockquote><p>
+The <code>\</code><code>vtop</code> primitive sets the base-line of the resulting object to
+that of the first &ldquo;line&rdquo; in it; the <code>\</code><code>vskip</code> creates the illusion
+of an empty line, so <code>\</code><code>vtop</code> makes the very top of the box into the
+base-line.
+<p/>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:
+<blockquote>
+<pre>
+\vtop{%
+  \vskip-1ex
+  \hbox{%
+    \includegraphics{figure}%
+  }%
+}
+</pre>
+</blockquote><p>
+A more LaTeX-y way of doing the job (somewhat inefficiently) uses
+the <i>calc</i> package:
+<blockquote>
+<pre>
+\usepackage{calc}
+...
+\raisebox{1ex-\height}{\includegraphics{figure}}
+</pre>
+</blockquote><p>
+(this has the same effect as the text-align version, above).
+<p/>The fact is, <em>you</em> may choose where the base-line ends up.  This
+answer merely shows you sensible choices you might make.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html
new file mode 100644
index 00000000000..dfea790f4fb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html
@@ -0,0 +1,30 @@
+<head>
+<title>UK TeX FAQ -- question label tradesyms</title>
+</head><body>
+<h3>How to get copyright, trademark, etc.</h3>
+<p/>The &ldquo;
+<a href="FAQ-symbols.html">Comprehensive symbol list</a>&rdquo;, lists
+the symbol commands <code>\</code><code>textcopyright</code>,
+<code>\</code><code>textregistered</code> and <code>\</code><code>texttrademark</code>, which are available in
+TS1-encoded fonts, and which are enabled using the
+<i>textcomp</i> package.
+<p/>In fact, all three commands are enabled in default LaTeX, but the
+glyphs you get aren&rsquo;t terribly beautiful.  In particular,
+<code>\</code><code>textregistered</code> 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
+&ldquo;r&rdquo;, whereas the proper symbol is a circled &ldquo;R&rdquo;.
+<p/>This effect is of course avoided by use of <i>textcomp</i>.
+<p/>Another problem arises if you want <code>\</code><code>textregistered</code> in a
+superscript position (to look similar to <code>\</code><code>texttrademark</code>).
+Using a maths-mode superscript to do this provokes lots of pointless
+errors: you <em>must</em> use
+<blockquote>
+<pre>
+\textsuperscript{\textregistered}
+</pre>
+</blockquote><p>
+<p/>
+<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
new file mode 100644
index 00000000000..b08faeb6596
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label triptrap</title>
+</head><body>
+<h3>How can I be sure it&rsquo;s really TeX?</h3>
+<p/>TeX (and Metafont and MetaPost) are written in a
+
+  <a href="FAQ-lit.html">&lsquo;literate&rsquo; programming</a> language called Web
+which is designed to be portable across a wide range of computer
+systems.  How, then, is a new version of TeX checked?
+<p/>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.
+<p/>Knuth, however, provides a &lsquo;conformance test&rsquo; for both TeX
+(<code>trip</code>) and Metafont (<code>trap</code>).
+
+He characterises these as &lsquo;torture tests&rsquo;: 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!
+<p/>Once an implementation of TeX has passed its <code>trip</code> test, or an
+implementation of Metafont has passed its <code>trap</code> test, then it may
+in principle be distributed as a working version.  (In practice, any
+distributor would test new versions against &ldquo;real&rdquo; documents or
+fonts, too; <code>trip</code> and <code>trap</code> don&rsquo;t actually test any
+for real world problems.
+<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html
new file mode 100644
index 00000000000..eacc105e158
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html
@@ -0,0 +1,92 @@
+<head>
+<title>UK TeX FAQ -- question label tutbitslatex</title>
+</head><body>
+<h3>Specialised (La)TeX tutorials</h3>
+<p/>The AMS publishes a &ldquo;Short Math Guide for LaTeX&rdquo;, which is
+available (in several formats) via
+<a href="http://www.ams.org/tex/short-math-guide.html">http://www.ams.org/tex/short-math-guide.html</a>
+<p/>Herbert Voss is developing a parallel document, that is also very
+useful; it&rsquo;s part of his &ldquo;<a href="FAQ-doc-dirs.html">tips and tricks</a>&rdquo; and
+a copy is maintained on CTAN.
+
+<p/>Two documents written more than ten years apart about font usage in
+TeX are worth reading: 
+<a href="href=&rsquo;http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf">Essential NFSS</a>
+by Sebastian Rahtz, and
+<a href="http://tug.org/pracjourn/2006-1/schmidt/schmidt.pdf">Font selection in LaTeX</a>,
+cast in the form of an FAQ, by Walter Schmidt.  A general
+compendium of font information (including the two above) may be found
+on the <a href="http://www.tug.org/fonts/">TUG web site</a>.
+<p/>Peter Smith&rsquo;s
+
+  
+  &ldquo;<a href="http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/">LaTeX for Logicians</a>&rdquo;
+covers a rather smaller subject area, but is similarly comprehensive
+(mostly by links to documents on relevant topics, rather than as a
+monolithic document).
+<p/>Keith Reckdahl&rsquo;s &ldquo;Using Imported Graphics in LaTeX2e&rdquo; is an
+excellent introduction to graphics use.  It&rsquo;s available on
+CTAN, but the sources aren&rsquo;t available (promised &ldquo;some time
+soon&rdquo;).
+<p/>Kjell Magne Fauske offers a set of examples of the use of the drawing
+packages 
+<a href="FAQ-drawing.html">PGF and TikZ</a>; the 
+<a href="http://www.fauskes.net/pgftikzexamples/">examples catalogue</a>
+includes examples (with output) from the package documentation as well
+as code written by the author himself.
+<p/>Vincent Zoonekynd provides a set of excellent (and graphic) tutorials
+on the programming of 
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html">title page styles</a>,
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html">chapter heading styles</a>
+and
+<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>.
+In each file, there is a selection of graphics representing an output
+style, and for each style, the code that produces it is shown.
+<p/>An invaluable step-by-step setup guide for establishing a &ldquo;work
+flow&rdquo; through your (La)TeX 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&rsquo;s <i>testflow</i>.  The
+tutorial consists of a large plain text document, and there is a
+supporting LaTeX file together with correct output, both in PostScript and
+PDF, for each of A4 and &ldquo;letter&rdquo; paper sizes.  The
+complete kit is available on CTAN (distributed with the
+author&rsquo;s macros for papers submitted for IEEE publications).
+The issues are also covered in a later 
+<a href="FAQ-dvips-pdf.html">FAQ answer</a>.
+<p/>Documentation of Japanese TeX use appears at least twice on the web:
+Haruhiko Okumura&rsquo;s page on
+
+<a href="http://oku.edu.mie-u.ac.jp/~okumura/texfaq/japanese/">typesetting Japanese with Omega</a>
+(the parent page is in Japanese, so out of the scope of this
+FAQ).
+<p/>One &ldquo;Tim&rdquo; documents pTeX (a TeX system widely used in Japan)
+in his
+
+  
+  &ldquo;<a href="http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf">English notes on pTeX</a>&rdquo;.
+<p/>Some university departments make their local documentation available
+on the web.  Most straightforwardly, there&rsquo;s the simple translation of
+existing documentation into HTML, for example the INFO
+documentation of the (La)TeX installation, of which a sample is the
+LaTeX documentation available at
+<a href="http://www.tac.dk/cgi-bin/info2www?(latex)">http://www.tac.dk/cgi-bin/info2www?(latex)</a>
+<p/>More ambitiously, some university departments have enthusiastic
+documenters who 
+make public record of their (La)TeX support.  For example, Tim Love
+(of Cambridge University Engineering Department) maintains his
+deparment&rsquo;s pages at
+<a href="http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/">http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/</a>
+
+
+
+
+
+<dl>
+<dt><tt><i>Graphics in LaTeX2e</i></tt><dd>the
+  document is available in PostScript and PDF formats as
+  <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a> and <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a> respectively
+<dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a>
+<dt><tt><i>Herbert Voss&rsquo;s Maths tutorial</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html
new file mode 100644
index 00000000000..a40e4a8ec57
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label tutorials*</title>
+</head><body>
+<h3>(La)TeX Tutorials, etc.</h3>
+<p/>From a situation where every (La)TeX user <em>had</em> 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 &ldquo;by topic&rdquo;.
+<p/>First we have introductory manuals, for
+<a href="FAQ-man-tex.html">Plain TeX</a> and <a href="FAQ-man-latex.html">LaTeX</a>.
+<p/>Next comes a selection of
+<a href="FAQ-tutbitslatex.html">&ldquo;specialised&rdquo; (La)TeX tutorials</a>,
+each of which concentrates on a single LaTeX topic.
+<p/>A couple of reference documents (it would be good to have more) are
+listed in an <a href="FAQ-ref-doc.html">answer of their own</a>.
+<p/>Next comes the (rather new) field of 
+<a href="FAQ-doc-wiki.html">TeX-related WIKIs</a>.
+<p/>A rather short list gives us a 
+<a href="FAQ-typo-style.html">Typography style tutorial</a>.
+<p/>Finally, we have a set of links to
+<a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a>, and details
+of some &ldquo;<a href="FAQ-ol-books.html">books</a>&rdquo; that were once published
+conventionally, but are now available on-line.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html
new file mode 100644
index 00000000000..bb7b1a8208c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html
@@ -0,0 +1,78 @@
+<head>
+<title>UK TeX FAQ -- question label twooptarg</title>
+</head><body>
+<h3>More than one optional argument</h3>
+<p/>If you&rsquo;ve already read 
+&ldquo;<a href="FAQ-moren9.html">breaking the 9-argument limit</a>&rdquo;.
+you can probably guess the &ldquo;simple&rdquo; solution to this problem:
+command relaying.
+<p/>LaTeX allows commands with a single optional argument thus:
+<pre>
+  \newcommand{\blah}[1][Default]{...}
+</pre>
+<p/>You may legally call such a command either with its optional argument
+present, as
+<code>\</code><code>blah[nonDefault]</code> or without, as <code>\</code><code>blah</code>; in the latter
+case, the code of <code>\</code><code>blah</code> will have an argument of <code>Default</code>.
+<p/>To define a command with two optional arguments, we use the relaying
+technique, as follows:
+<pre>
+  \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
+    ...%
+  }
+</pre>
+Of course, <code>\</code><code>BlahRelay</code> may have as many mandatory arguments as are
+allowed, after allowance for the one taken up with its own
+optional argument &mdash; that is, 8.
+<p/>Variants of <code>\</code><code>newcommand</code> (and friends), with names like
+<code>\</code><code>newcommandtwoopt</code>, are available in the <i>twoopt</i> package.
+However, if you can, it&rsquo;s probably better to learn to write the commands
+yourself, just to see why they&rsquo;re not even a good idea from the
+programming point of view.
+<p/>A command with two optional arguments strains the limit of what&rsquo;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 <i>keyval</i> package, in 
+&ldquo;<a href="FAQ-moren9.html">breaking the 9-argument limit</a>&rdquo;,
+which offers an alternative way forward.
+<p/>If you must, however, consider the <i>optparams</i> or
+<i>xargs</i> packages.  <i>Optparams</i>
+provides a <code>\</code><code>optparams</code> 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!).
+<p/>The <i>xargs</i> package uses a key-value package
+(<i>xkeyval</i>) to <em>define</em> the layout of the optional
+arguments.  Thus
+<blockquote>
+<pre>
+\usepackage{xargs}
+...
+\newcommandx{\foo}[3][1=1, 3=n]{...}
+</pre>
+</blockquote><p>
+defines a command <code>\</code><code>foo</code> that has an optional first argument
+(default 1), a mandatory second argument, and an optional third
+argument (default n).
+<p/>An alternative approach is offered by Scott Pakin&rsquo;s
+<i>newcommand</i> program, which takes a command name and a
+definition of a set of command arguments (in a fairly
+readily-understood language), and emits (La)TeX macros which enable
+the command to be defined.  The command requires that a
+<i>Python</i> interpreter (etc.) be installed on your computer.
+<dl>
+<dt><tt><i>newcommand.py</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/newcommand.zip">support/newcommand</a> (<a href="ftp://cam.ctan.org/tex-archive/support/newcommand.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/newcommand/">browse</a>)
+<dt><tt><i>optparams.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse</a>)
+<dt><tt><i>twoopt.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>)
+<dt><tt><i>xargs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xargs.zip">macros/latex/contrib/xargs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xargs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xargs/">browse</a>)
+<dt><tt><i>xkeyval.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xkeyval.zip">macros/latex/contrib/xkeyval</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xkeyval.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html
new file mode 100644
index 00000000000..cf1e34853d4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html
@@ -0,0 +1,106 @@
+<head>
+<title>UK TeX FAQ -- question label type1T1</title>
+</head><body>
+<h3>Finding &lsquo;8-bit&rsquo; Type 1 fonts</h3>
+<!-- eight -->
+<p/>Elsewhere, answers to these FAQs recommend that you use an
+&lsquo;8-bit&rsquo; font to permit 
+<a href="FAQ-hyphenaccents.html">accentuation of inflected languages</a>,
+and also recommend the use of Type 1 fonts to ensure that
+you get <a href="FAQ-fuzzy-type3.html">good quality PDF</a>.  These
+recommendations used to be contradictory: one could not just
+&ldquo;switch&rdquo; from the free 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 &ldquo;true&rdquo; Type 1 fonts available: as always, we have an
+embarrassment of riches with three free alternatives, and one
+commercial and one shareware version.
+<p/><i>CM-super</i> is an
+auto-traced set which encompasses all of the T1 and TS1
+encodings as well as the T2* 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&rsquo;t try to install them if you&rsquo;re short of disc
+space.
+<p/><i>CM-LGC</i> is a similar &ldquo;super-font&rdquo; set, but of much more
+modest size; it covers T1, TS1 and T2{A}
+encodings (as does <i>CM-super</i>, and also covers the LGR
+encoding (for typesetting Greek, based on Claudio Beccari&rsquo;s Metafont
+sources).  <i>CM-LGC</i> manages to be small by going to the
+opposite extreme from <i>CM-super</i>, which includes fonts at all
+the sizes supported by the original EC (a huge range);
+<i>CM-LGC</i> 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, <i>CM-LGC</i>
+is an obvious choice.
+<p/><i>Tt2001</i> is a simple scan of the EC and TC
+fonts, and has some virtues &mdash; it&rsquo;s noticeably smaller than
+<i>CM-super</i> while being less stark than <i>CM-LGC</i>.
+<p/><i>Latin</i> <i>Modern</i> is produced using the
+program <a href="FAQ-textrace.html"><i>MetaType1</i></a>.  The
+<i>Latin</i> <i>Modern</i> set comes with T1, TS1
+LY1 encoded variants (as well as a variant using the Polish
+QX encoding); for the glyph set it covers, its outlines seem
+rather cleaner than those of <i>CM-super</i>.  <i>Latin</i>
+<i>Modern</i> is more modest in its disc space demands than is
+<i>CM-super</i>, while not being nearly as stark in its range of
+design sizes as is <i>CM-LGC</i> &mdash;  <i>Latin</i>
+<i>Modern</i>&rsquo;s fonts are offered in the same set of sizes as the
+original <i>CM</i> fonts.  It&rsquo;s hard to argue with the choice:
+Knuth&rsquo;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.
+<p/><a href="FAQ-virtualfonts.html">Virtual fonts</a> help us deal with the problem,
+since they allow us to map &ldquo;bits of DVI file&rdquo; to single
+characters in the virtual font; so we can create an &ldquo;&eacute;&rdquo; character
+by recreating the DVI commands that would result from the code
+&ldquo;<code>\</code><code>&rsquo;</code><code>e</code>&rdquo;.  However, since this involves two characters being
+selected from a font, the arrangement is sufficient to fool
+<i>Acrobat</i> <i>Reader</i>: you can&rsquo;t use the program&rsquo;s
+facilities for searching for text that contains inflected characters,
+and if you <em>cut</em> text from a window that contains such a
+character, you&rsquo;ll find something unexpected (typically the accent and
+the &lsquo;base&rsquo; characters separated by a space) when you <i>paste</i>
+the result.  However, if you can live with this difficulty, virtual
+fonts are a useful and straightforward solution to the problem.
+<p/>There are two virtual-font offerings of CM-based 8-bit
+fonts &mdash; the <i>ae</i> (&ldquo;almost EC&rdquo;) and
+<i>zefonts</i> sets; the <i>zefonts</i> set has wider coverage
+(though the <i>ae</i> set may be extended to offer guillemets by
+use of the <i>aeguill</i> package).  Neither offers characters such
+as <code>eth</code> and <code>thorn</code> (used in, for example, in
+Icelandic), but the <i>aecompl</i> package works with the
+<i>ae</i> fonts to provide the missing characters from the
+EC fonts (i.e., as bitmaps).
+<p/>The sole remaining commercial CM-like 8-bit font comes from
+Micropress, who offer the complete EC set
+in Type 1 format, as part of their range of outline versions of fonts
+that were originally distributed in Metafont format.  See
+<a href="FAQ-commercial.html">&ldquo;commercial distributions&rdquo;</a>.
+<p/>The shareware 
+<a href="FAQ-TeXsystems.html">BaKoMa TeX distribution</a> offers a
+set of Type 1 EC fonts, as an extra shareware option.  (As far
+as the present author can tell, these fonts are <em>only</em> available
+to users of BaKoMa TeX: they are stored in an archive format that
+seems not to be publicly available.)
+<p/>Finally, you can use one of the myriad text fonts available in Type 1
+format (with appropriate PSNFSS metrics for T1 encoding,
+or metrics for some other 8-bit encoding such as LY1).  However,
+if you use someone else&rsquo;s text font (even something as simple as
+Adobe&rsquo;s Times family) you have to find a matching family of
+mathematical fonts, which is a non-trivial undertaking &mdash;
+see <a href="FAQ-psfchoice.html">&ldquo;choice of scalable fonts&rdquo;</a>.
+<dl>
+<dt><tt><i>ae fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>)
+<dt><tt><i>aecompl.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>)
+<dt><tt><i>aeguill.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/aeguill.zip">macros/latex/contrib/aeguill</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/aeguill.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/aeguill/">browse</a>)
+<dt><tt><i>BaKoMa fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/win32/bakoma/fonts/">systems/win32/bakoma/fonts/</a>
+<dt><tt><i>CM-LGC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.zip">fonts/ps-type1/cm-lgc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-lgc/">browse</a>)
+<dt><tt><i>CM-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) (beware:
+  very large download)
+<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>)
+<dt><tt><i>tt2001 fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/tt2001.zip">fonts/ps-type1/tt2001</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/tt2001.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/tt2001/">browse</a>)
+<dt><tt><i>zefonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/zefonts.zip">fonts/zefonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/zefonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/zefonts/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html
new file mode 100644
index 00000000000..a898295a03c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label typebooks</title>
+</head><body>
+<h3>Books on Type</h3>
+<p/>    The following is a partial listing of books on typography in general.
+Of these, Bringhurst seems to be the one most often recommended.
+<dl>
+<dt>The Elements of Typographic Style<dd>by Robert Bringhurst
+  (Hartley &amp; Marks, 1992, ISBN 0-88179-033-8)
+<dt>Finer Points in the Spacing &amp; Arrangement of Type<dd>by Geoffrey Dowding
+  (Hartley &amp; Marks, 1996, ISBN 0-88179-119-9)
+<dt>The Thames &amp; Hudson Manual of Typography<dd>by Ruari McLean
+  (Thames &amp; Hudson, 1980, ISBN 0-500-68022-1)
+<dt>The Form of the Book<dd>by Jan Tschichold
+  (Lund Humphries, 1991, ISBN 0-85331-623-6)
+<dt>Type &amp; Layout<dd>by Colin Wheildon
+  (Strathmore Press, 2006, ISBN 1-875750-22-3)
+<dt>The Design of Books<dd>by Adrian Wilson
+  (Chronicle Books, 1993, ISBN 0-8118-0304-X)
+<dt>Optical Letter Spacing<dd>by David Kindersley and Lida Cardozo Kindersley 
+  
+  (<a href="http://www.kindersleyworkshop.co.uk/">The Cardozo Kindersley Workshop</a>
+  2001, ISBN 1-874426-139)
+</dl>
+<p/>    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.
+<dl>
+<dt>Alphabets Old &amp; New<dd>by Lewis F. Day
+  (Senate, 1995, ISBN 1-85958-160-9)
+<dt>An Introduction to the History of Printing Types<dd>by Geoffrey Dowding
+  (British Library, 1998, UK ISBN 0-7123-4563-9; USA ISBN 1-884718-44-2)
+<dt>The Alphabet Abecedarium<dd>by Richard A. Firmage
+  (David R. Godine, 1993, ISBN 0-87923-998-0)
+<dt>The Alphabet and Elements of Lettering<dd>by Frederick Goudy
+  (Dover, 1963, ISBN 0-486-20792-7)
+<dt>Anatomy of a Typeface<dd>by Alexander Lawson
+  (David R. Godine, 1990, ISBN 0-87923-338-8)
+<dt>A Tally of Types<dd>by Stanley Morison
+  (David R. Godine, 1999, ISBN 1-56792-004-7)
+<dt>Counterpunch<dd>by Fred Smeijers
+  (Hyphen, 1996, ISBN 0-907259-06-5)
+<dt>Treasury of Alphabets and Lettering<dd>by Jan Tschichold
+  (W. W. Norton, 1992, ISBN 0-393-70197-2)
+<dt>A Short History of the Printed Word<dd>by Warren Chappell and
+  Robert Bringhurst (Hartley &amp; Marks, 1999, ISBN 0-88179-154-7)
+</dl>
+<p/>    The above lists are limited to books published in English. Typographic 
+styles are somewhat language-dependent, and similarly the &lsquo;interesting&rsquo; fonts
+depend on the particular writing system involved.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html
new file mode 100644
index 00000000000..76ef208ec98
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label typend</title>
+</head><body>
+<h3>&ldquo;Please type a command or say <code>\</code><code>end</code>&rdquo;</h3>
+<p/>Sometimes, when you are running (La)TeX, it will abruptly stop and
+present you with a prompt (by default, just a <code>*</code> character).  Many
+people (including this author) will reflexively hit the &lsquo;return&rsquo;
+key, pretty much immediately, and of course this is no help at all &mdash;
+TeX just says:
+<pre>
+(Please type a command or say `\end')
+</pre>
+and prompts you again.
+<p/>What&rsquo;s happened is that your (La)TeX file has finished prematurely,
+and TeX has fallen back to a supposed including file, from the
+terminal.  This could have happened simply because you&rsquo;ve omitted
+the <code>\</code><code>bye</code> (Plain TeX), <code>\</code><code>end{document}</code> (LaTeX), or
+whatever.  Other common errors are failure to close the braces round a
+command&rsquo;s argument, or (in LaTeX) failure to close a verbatim
+environment: in such cases you&rsquo;ve already read and accepted an
+error message about encountering end of file while scanning something.
+<p/>If the error is indeed because you&rsquo;ve forgotten to end your document,
+you can insert the missing text: if you&rsquo;re running Plain TeX, the
+advice, to &ldquo;say <code>\</code><code>end</code>&rdquo; is good enough: it will kill the run; if
+you&rsquo;re running LaTeX, the argument will be necessary:
+<code>\</code><code>end{document}</code>.  
+<p/>However, as often as not this isn&rsquo;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&rsquo;s
+running TeX) is to be avoided: there may well be evidence in the
+<code>.log</code> file that will be useful in determining what the
+problem is &mdash; so the aim is to persuade TeX to shut itself down
+and hence flush all log output to file.
+<p/>If you can persuade TeX to read it, an end-of-file indication
+(control-<code>D</code> under Unix, control-<code>Z</code> 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 <code>x</code> &lsquo;command&rsquo;).  An accessible error could well be inserting an
+illegal character: what it is will depend on what macros you are
+running.  If you can&rsquo;t make that work, try a silly command name or
+two.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html
new file mode 100644
index 00000000000..37d738baf04
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html
@@ -0,0 +1,25 @@
+<head>
+<title>UK TeX FAQ -- question label typo-style</title>
+</head><body>
+<h3>Typography tutorials</h3>
+<p/>There&rsquo;s also (at least one) typographic style tutorial available on
+the Web, the excellent 
+&ldquo;<a href="http://www.nbcs.rutgers.edu/~hedrick/typography/typography.janson-syntax.107514.pdf">Guidelines for Typography in NBCS</a>&rdquo;.
+In fact, its 
+<a href="http://www.nbcs.rutgers.edu/~hedrick/typography/index.html">parent page</a>
+is also worth a read: among other things, it provides copies of the
+&ldquo;guidelines&rdquo; 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
+<a href="FAQ-typebooks.html">Bringhurst&rsquo;s</a>, but the document (though it does
+contain its Rutgers-local matter) is a fine introduction to the issues
+of producing readable documents.
+<p/>Peter Wilson&rsquo;s manual for his <i>memoir</i> class 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 (La)TeX users.
+<dl>
+<dt><tt><i>memoir distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html
new file mode 100644
index 00000000000..f3d4e83a58d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label underline</title>
+</head><body>
+<h3>Underlined text won&rsquo;t break</h3>
+<p/>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
+<code>\</code><code>emph</code> does just that to its argument.
+<p/>Nevertheless, typographically illiterate people (such as those that
+specify double-spaced
+<a href="FAQ-linespace.html">thesis styles</a>)
+continue to require underlining of us, so LaTeX as distributed
+defines an <code>\</code><code>underline</code> command that applies the mathematical
+&lsquo;underbar&rsquo; operation to text.  This technique is not entirely
+satisfactory, however: the text gets stuck into a box, and won&rsquo;t break
+at line end.
+<p/>Two packages are available that solve this problem.  The
+<i>ulem</i> package redefines the
+<code>\</code><code>emph</code> 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, contained within the file itself.)
+The <i>soul</i> package defines an <code>\</code><code>ul</code> command (after which the
+package is, in part, named) that underlines running text.
+<p/>Beware of <i>ulem</i>&rsquo;s default behaviour, which is to convert the
+<code>\</code><code>emph</code> command into an underlining command; this can be avoided by
+loading the package with:
+<pre>
+  \usepackage[normalem]{ulem}
+</pre>
+Documentation of <i>ulem</i> is in the package itself.
+<dl>
+<dt><tt><i>ulem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a>
+<dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html
new file mode 100644
index 00000000000..6008a15a443
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html
@@ -0,0 +1,42 @@
+<head>
+<title>UK TeX FAQ -- question label underscore</title>
+</head><body>
+<h3>How to use the underscore character</h3>
+<p/>The underscore character &lsquo;<code>_</code>&rsquo; is ordinarily used in
+TeX to indicate a subscript in maths mode; if you type
+<code>_</code>, on its own, in the course of ordinary text, TeX will
+complain.  If you&rsquo;re writing a document which will contain a large
+number of underscore characters, the prospect of typing
+<code>\</code><code>_</code> (or, worse, <code>\</code><code>textunderscore</code>) for every one of
+them will daunt most ordinary people.
+<p/>Moderately skilled macro programmers can readily generate a quick hack
+to permit typing &lsquo;<code>_</code>&rsquo; to mean &lsquo;text underscore&rsquo;.
+However, the code <em>is</em> somewhat tricky, and more importantly
+there are significant points where it&rsquo;s easy to get it wrong.  There
+is therefore a package <i>underscore</i> which provides a general
+solution to this requirement.
+<p/>There is a problem, though: OT1 text fonts don&rsquo;t contain an
+underscore character, unless they&rsquo;re in the typewriter version of the
+encoding (used by fixed-width fonts such as <code>cmtt</code>).  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
+T1, which has the same layout for every font, and thus an
+underscore in every font.
+<p/>If the requirement is only for occasional uses of underscores, it may
+be acceptable to use the following construct:
+<blockquote>
+<pre>
+\def\us{\char`\_}
+...
+\texttt{create\us process}
+</pre>
+</blockquote><p>
+The construction isn&rsquo;t in the least robust (in the normal English
+sense of the word), but it <em>is</em> robust under expansion (i.e., the
+LaTeX sense of the word); so use it with care, but don&rsquo;t worry
+about section headings and the like.
+<dl>
+<dt><tt><i>underscore.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/underscore.sty">macros/latex/contrib/misc/underscore.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html
new file mode 100644
index 00000000000..e7a74af855f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html
@@ -0,0 +1,64 @@
+<head>
+<title>UK TeX FAQ -- question label unkgrfextn</title>
+</head><body>
+<h3>&ldquo;Unknown graphics extension&rdquo;</h3>
+<p/>The LaTeX graphics package deals with several different types of
+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 &lt;<i>driver</i>&gt;<code>.def</code> file
+corresponding to the output driver you&rsquo;re using.
+<p/>The error message arises, then, if you have a graphics file whose
+extension doesn&rsquo;t correspond with one your driver knows about.  Most
+often, this is because you&rsquo;re being optimistic: asking
+<i>dvips</i> to deal with a <code>.png</code> file, or PDFTeX to deal with
+a <code>.eps</code> file: the solution in this case is to transform the graphics
+file to a format your driver knows about.
+<p/>If you happen to <em>know</em> 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 <i>home.bedroom.eps</i> using the
+<i>dvips</i> driver; the package will conclude that your file&rsquo;s
+extension is <code>.bedroom.eps</code>, and will complain.
+<p/>The <i>grffile</i> package deals with the last problem (and
+others &mdash; see the package documentation); using the package, you may
+write:
+<blockquote>
+<pre>
+\usepackage{graphicx}
+\usepackage{grffile}
+...
+\includegraphics{home.bedroom.eps}
+</pre>
+</blockquote><p>
+or you may even write
+<blockquote>
+<pre>
+\includegraphics{home.bedroom}
+</pre>
+</blockquote><p>
+and <i>graphicx</i> will find a <code>.eps</code> or <code>.pdf</code>
+(or whatever) version, according to what version of (La)TeX you&rsquo;re
+running.
+<p/>If for some reason you can&rsquo;t use <i>grffile</i>, you have three
+unsatisfactory alternatives:
+<ul>
+<li> Rename the file &mdash; for example <i>home.bedroom.eps</i>-&gt; 
+  <i>home-bedroom.eps</i>
+<li> Mask the first dot in the file name:
+<pre>
+\newcommand*{\DOT}{.}
+\includegraphics{home\DOT bedroom.eps}
+</pre>
+<li> Tell the graphics package what the file is, by means of options
+  to the <code>\</code><code>includegraphics</code> command:
+
+<pre>
+\includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom}
+</pre>
+</ul>
+<dl>
+<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) collection
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html
new file mode 100644
index 00000000000..ecce4105cf8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html
@@ -0,0 +1,63 @@
+<head>
+<title>UK TeX FAQ -- question label uploads</title>
+</head><body>
+<h3>Contributing a file to the archives</h3>
+<p/>You have something to submit to the archive &mdash; great!  Before we even
+start, here&rsquo;s a check-list of things to sort out:
+<ol>
+<li> Licence: in the spirit of TeX, we hope for free software; in
+  the spirit of today&rsquo;s lawyer-enthralled society, CTAN
+  provides a 
+  <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of &ldquo;standard&rdquo; licence statements</a>.
+<li> Documentation: it&rsquo;s good for users to be able to browse
+  documentation before downloading a package.  You need at least a
+  plain text <i>README</i> file (exactly that name); in addition a
+  PDF file of the package documentation, prepared for screen
+  reading, is highly desirable.
+<li> Name: endless confusion is caused by name clashes.  If your
+  package has the same name as one already on CTAN, or if your
+  package installation generates files of the same name as something
+  in a &ldquo;normal&rdquo; distribution, the CTAN team will delay
+  installation while they check that you&rsquo;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. 
+  <a href="FAQ-findfiles.html">Browse the archive</a> to ensure uniqueness.
+<p/>  The name you choose should also (as far as possible) be somewhat
+  descriptive of what your submission actually <em>does</em>; while
+  &ldquo;descriptiveness&rdquo; is to some extent in the eye of the beholder,
+  it&rsquo;s clear that names such as <i>mypackage</i> or <i>jiffy</i>
+  aren&rsquo;t suitable.
+</ol>
+<p/>If you are able to use anonymous <i>ftp</i>, you can upload that
+way.  The file <i>README.uploads</i> on CTAN tells you
+where to upload, what to upload, and how to notify the CTAN
+management about what you want doing with your upload.
+<p/>You may also upload via the Web: each of the principal CTAN
+sites offers an upload page &mdash; choose from
+<a href="http://www.ctan.org/upload.html">http://www.ctan.org/upload.html</a>,
+<a href="http://www.dante.de/CTAN/upload.html">http://www.dante.de/CTAN/upload.html</a> or
+<a href="http://www.tex.ac.uk/upload.html">http://www.tex.ac.uk/upload.html</a>; the pages lead you through the
+process, showing you the information you need to supply.  This method
+enforces one file per upload: if you had intended to upload lots of
+files, you need to bundle them into an &lsquo;archive&rsquo; file of some sort;
+acceptable formats are <code>.zip</code> and <code>.tar.gz</code> (or
+<code>.tar.bz2</code>).
+<p/>If you can use neither of these methods, or if you find something
+confusing, ask advice of the
+
+  <a href="mailto:ctan@dante.de">CTAN management</a>:
+if the worst comes to the worst, it may be possible to mail a
+contribution.  This really is a last-resort route: none of the
+CTAN sites is anyone&rsquo;s regular workstation, so if you mail to
+one of the maintainers, that maintainer then has to upload to
+CTAN.
+<p/>If it&rsquo;s appropriate (if your package is large, or regularly updated),
+the CTAN management can arrange to <i>mirror</i> your
+contribution direct into the archive.  At present this may only be
+done if your contribution is available via <i>ftp</i>, and of
+course the directory structure on your repository must &lsquo;fit&rsquo;.
+<dl>
+<dt><tt><i>README.uploads</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/README.uploads">README.uploads</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html
new file mode 100644
index 00000000000..2a664630d7e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label upquot</title>
+</head><body>
+<h3>Realistic quotes for verbatim listings</h3>
+<p/>The <code>cmtt</code> font has &ldquo;curly&rdquo; quotes,
+which are pleasing on the eye, but don&rsquo;t really tally with what one
+sees on a modern 
+<i>xterm</i>.
+<p/>The appearance of these quotes is critical in program listings,
+particularly in those of Unix-like shell scripts.  The
+<i>upquote</i> package modifies the behaviour of the
+<code>verbatim</code> environment so that the output is a clearer
+representation of what the user must type.
+<dl>
+<dt><tt><i>upquote.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/upquote/upquote.sty">macros/latex/contrib/upquote/upquote.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html
new file mode 100644
index 00000000000..d3eb8137324
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html
@@ -0,0 +1,107 @@
+<head>
+<title>UK TeX FAQ -- question label useMF</title>
+</head><body>
+<h3>Getting Metafont to do what you want</h3>
+<p/>Metafont allows you to create your own fonts, and most TeX users
+will never need to use it. Metafont, unlike TeX, requires some
+customisation: each output device for which you will be generating
+fonts needs a mode associated with it. Modes are defined using the
+<code>mode_def</code> convention described on page 94 of <em>The Metafontbook</em>
+(see <a href="FAQ-books.html">TeX-related books</a>). You will need
+a file, which conventionally called <i>local.mf</i>, containing all the
+<code>mode_def</code>s you will be using. If <i>local.mf</i> doesn&rsquo;t already
+exist, Karl Berry&rsquo;s collection of modes (<i>modes.mf</i>)
+is a good starting point 
+(it can be used as a &lsquo;<i>local.mf</i>&rsquo; without modification in a &lsquo;big
+enough&rsquo; implementation of Metafont). Lists of
+settings for various output devices are also published periodically in
+<i>TUGboat</i> (see <a href="FAQ-TUGstar.html">TUG</a>). Now create
+a <code>plain</code> base
+file using <i>inimf</i>, <code>plain.mf</code>, and <code>local.mf</code>:
+<pre>
+   % inimf
+   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)
+</pre>
+
+This will create a base file named <i>plain.base</i> (or something
+similar; for example, it will be
+
+  <i>PLAIN.BAS</i>
+on MSDOS systems) which should be moved to the directory containing
+the base files on your system (note that some systems have two or more
+such directories, one for each &lsquo;size&rsquo; of Metafont used).
+<p/>Now you need to make sure Metafont loads this new base when it starts up. If
+Metafont loads the <code>plain</code> base by default on your system, then you&rsquo;re
+ready to go. Under Unix (using the default <i>web2c</i>
+distribution
+)
+this does indeed happen, but we could for instance define a command
+<i>mf</i> which executes <code>virmf &amp;plain</code> loading the
+<code>plain</code> base file.
+<p/>The usual way to create a font with <code>plain</code> Metafont is to start 
+it with the
+
+line
+<pre>
+\mode=&lt;mode name&gt;; mag=&lt;magnification&gt;; input &lt;font file name&gt;
+</pre>
+in response to the &lsquo;<code>**</code>&rsquo; prompt or on the Metafont command line. (If
+<code>&lt;mode name&gt;</code> is unknown or omitted, the mode defaults to &lsquo;proof&rsquo; and
+Metafont will produce an output file called
+
+<i>&lt;font file name&gt;.2602gf</i>)
+The <code>&lt;magnification&gt;</code> is a floating point number or
+&lsquo;magstep&rsquo; (magsteps are defined in <em>The Metafontbook</em> and
+<em>The TeXbook</em>).
+If <code>mag=&lt;magnification&gt;</code> is omitted, then the default
+is 1 (magstep 0).  For example, to generate cmr10 at 12pt for an epson
+printer you would type
+<pre>
+  mf \mode=epson; mag=magstep 1; input cmr10
+</pre>
+Note that under Unix the <code>\</code> and <code>;</code>
+characters must usually be quoted or escaped, so this would typically
+look something like
+<pre>
+ mf '\mode=epson; mag=magstep 1; input cmr10'
+</pre>
+<p/>If you don&rsquo;t have <i>inimf</i> or need a special mode that isn&rsquo;t
+in the base, you can put its commands in a file (<em>e.g.</em>,
+<i>ln03.mf</i>) and invoke it on the fly with the <code>\</code><code>smode</code> command.
+For example, to create <i>cmr10.300gf</i> for an LN03 printer, using
+the file
+<pre>
+   % 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;
+</pre>
+(note the absence of the <code>mode_def</code> and <code>enddef</code>
+commands), you would type
+<pre>
+   mf \smode="ln03"; input cmr10
+</pre>
+This technique isn&rsquo;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&rsquo;re using.  Once you&rsquo;ve settled on an appropriate set of
+parameters, you should use them to rebuild the base file that you use.
+<p/>Other sources of help are mentioned in 
+<a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a>.
+<dl>
+<dt><tt><i>modes.mf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/modes/modes.mf">fonts/modes/modes.mf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html
new file mode 100644
index 00000000000..29f3864ad4c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html
@@ -0,0 +1,81 @@
+<head>
+<title>UK TeX FAQ -- question label usebibtex</title>
+</head><body>
+<h3>&ldquo;Normal&rdquo; use of BibTeX from LaTeX</h3>
+<p/>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:
+<p/>First: you need a BibTeX bibliography file (a <code>.bib</code> file) &mdash; see
+
+&ldquo;<a href="FAQ-buildbib.html">creating a BibTeX file</a>&rdquo;.
+<p/>Second: you must write your LaTeX document to include a declaration
+of the &lsquo;style&rsquo; of bibliography, citations, and a reference to the
+bibliography file mentioned in the step 1.  So we may have a LaTeX
+file containing:
+<blockquote>
+<pre>
+\bibliographystyle{plain}
+...
+Pooh is heroic~\cite{Milne:1926}.
+...
+Alice struggles~\cite{Carroll:1865}.
+...
+\bibliography{mybooks}
+</pre>
+</blockquote><p>
+Note: we have bibliography style <i>plain</i>, 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&rsquo;s web site:
+<a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html</a>
+<p/>Third: you must process the file.
+<blockquote>
+<pre>
+latex myfile
+</pre>
+</blockquote><p>
+As LaTeX processes the file, the <code>\</code><code>bibliographystyle</code> command
+writes a note of the style to the <code>.aux</code> file; each
+<code>\</code><code>cite</code> command writes a note of the citation to the
+<code>.aux</code> file, and the <code>\</code><code>bibliography</code> command writes a note
+of which <code>.bib</code> file is to be used, to the <code>.aux</code> file.
+<p/>Note that, at this stage, LaTeX isn&rsquo;t &ldquo;resolving&rdquo; any of the
+citations: at every <code>\</code><code>cite</code> command, LaTeX will warn you of the
+undefined citation, and when the document finishes, there will be a
+further warning of undefined references.
+<p/>
+
+<p/>Fourth: you must run BibTeX:
+<blockquote>
+<pre>
+bibtex myfile
+</pre>
+</blockquote><p>
+Don&rsquo;t try to tell BibTeX anything but the file name: say
+<code>bibtex myfile.aux</code> (because you know it&rsquo;s going to read the
+<code>.aux</code> file) and BibTeX will blindly attempt to process
+<code>myfile.aux.aux</code>.
+<p/>BibTeX will scan the <code>.aux</code> file; it will find which bibliography
+style it needs to use, and will &ldquo;compile&rdquo; 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 <code>.bbl</code> file.
+<p/>Fifth: you run LaTeX again.  It warns, again, that each citation is
+(still) undefined, but when it gets to the <code>\</code><code>bibliography</code> command,
+it finds a <code>.bbl</code> file, and reads it.  As it encounters each
+<code>\</code><code>bibitem</code> command in the file, it notes a definition of the
+citation.
+<p/>Sixth: you run LaTeX yet again.  This time, it finds values for all
+the citations, in its <code>.aux</code> file.  Other things being equal, you&rsquo;re
+done... until you change the file.
+<p/>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.
+<p/>To summarise: processing to resolve citations requires: LaTeX;
+BibTeX; LaTeX; LaTeX.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html
new file mode 100644
index 00000000000..c9beec26f7f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html
@@ -0,0 +1,67 @@
+<head>
+<title>UK TeX FAQ -- question label uselmfonts</title>
+</head><body>
+<h3>Using the Latin Modern fonts</h3>
+<p/>The <i>lm</i> fonts are an exciting addition to
+the armoury of the (La)TeX 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 &ldquo;It is presumed that a potential
+user knows what to do with all these files&rdquo;.  This answer aims to
+fill in the requirements: the job is really not terribly difficult.
+<p/>Note that teTeX distributions, from version 3.0, already have the
+<i>lm</i> 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&rsquo;t use such
+systems.
+<p/>The font (and related) files appear on CTAN as a set of
+single-entry <a href="FAQ-tds.html">TDS trees</a> &mdash;
+<i>fonts</i>, <i>dvips</i>, <i>tex</i> and <i>doc</i>.  The <i>doc</i>
+subtree really need not be copied (it&rsquo;s really a pair of sample
+files), but copy the other three into your existing Local
+<code>$TEXMF</code> tree, and
+
+<a href="FAQ-inst-wlcf.html">update the filename database</a>.
+<p/>Now, incorporate the fonts in the set searched by PDFLaTeX,
+<i>dvips</i>, <i>dvipdfm</i>, your previewers and
+Type 1-to-PK conversion programs, by
+<ul>
+<li> On a teTeX system earlier than version 2.0, edit the file
+  <i>$TEXMF/dvips/config/updmap</i> and insert an absolute path for
+  the <i>lm.map</i> just after the line that starts
+  <code>extra_modules="</code> (and before the closing quotes).
+<li> On a teTeX version 2.0 (or later), execute the command
+<pre>
+  updmap --enable Map lm.map
+</pre>
+<li> On a MiKTeX system earlier than version 2.2, the &ldquo;Refresh
+  filename database&rdquo; operation, which you performed after installing
+  files, also updates the system&rsquo;s &ldquo;PostScript resources database&rdquo;.
+<li> On a MiKTeX system, version 2.2 or later, update
+  <i>updmap.cfg</i> as described in the MiKTeX 
+  <a href="http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg">online documentation</a>.
+  Then execute the command <code>initexmf --mkmaps</code>, and the
+  job is done.
+</ul>
+<p/>To use the fonts in a LaTeX document, you should
+<blockquote>
+  <code>\</code><code>usepackage{lmodern}</code>
+</blockquote><p>
+this will make the fonts the default
+for all three LaTeX font families (&ldquo;roman&rdquo;, &ldquo;sans-serif&rdquo; and
+&ldquo;typewriter&rdquo;).  You also need 
+<blockquote>
+  <code>\</code><code>usepackage[T1]{fontenc}</code>
+</blockquote><p>
+for text, and 
+<blockquote>
+  <code>\</code><code>usepackage{textcomp}</code>
+</blockquote><p>
+if you want to use any of the TS1-encoding symbols.  There is
+no support for using fonts according to the OT1 encoding.
+<dl>
+<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html
new file mode 100644
index 00000000000..9f5bf31140e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html
@@ -0,0 +1,58 @@
+<head>
+<title>UK TeX FAQ -- question label usepictex</title>
+</head><body>
+<h3>Why can&rsquo;t I load PicTeX?</h3>
+<p/>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&rsquo;t too badly affected by its
+performance.
+<p/>However, PicTeX has the further unfortunate tendency to fill up
+TeX&rsquo;s fixed-size arrays &mdash; notably the array of 256 &lsquo;dimension&rsquo;
+registers.  This is a particular problem when you&rsquo;re using
+<i>pictex.sty</i> with LaTeX and some other packages that also need
+dimension registers.  When this happens, you will see the TeX error
+message:
+<blockquote>
+<pre>
+! No room for a new \dimen.
+</pre>
+</blockquote><p>
+There is nothing that can directly be done about this error: you
+can&rsquo;t extend the number of available <code>\</code><code>dimen</code> registers without
+extending TeX itself.
+  <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a> both do this, as
+  does <a href="FAQ-commercial.html">MicroPress Inc&rsquo;s VTeX</a>.
+
+<p/>It&rsquo;s actually quite practical (with most modern distributions) to use
+e-TeX&rsquo;s extended register set: use package <i>etex</i> (which
+comes with e-TeX distributions) and the allocation mechanism is
+altered to cope with the larger register set: PicTeX will now load.
+<p/>If you&rsquo;re in some situation where you can&rsquo;t use e-TeX, you need to change
+PicTeX; unfortunately PicTeX&rsquo;s author is no longer active in the
+TeX world, so one must resort to patching.  There are two solutions
+available.
+<p/>The ConTeXt module <i>m-pictex.tex</i> (for Plain TeX and
+variants) or the corresponding LaTeX <i>m-pictex</i> package provide
+an ingenious solution to the problem based on hacking the code of
+<code>\</code><code>newdimen</code> itself.
+<p/>Alternatively, Andreas Schell&rsquo;s <i>pictexwd</i> and related
+packages replace PicTeX with a version that uses 33 fewer
+<code>\</code><code>dimen</code> registers; so use <i>pictexwd</i> in place of
+<i>pictex</i> (either as a LaTeX package, or as a file to read
+into Plain TeX).
+<p/>And how does one use PicTeX anyway, given that the
+manual is so <a href="FAQ-docpictex.html">hard to come by</a>?
+Fortunately for us all, the <i>MathsPic</i>
+system may be used to translate a somewhat different language into
+PicTeX commands; and the <i>MathsPic</i> manual is free (and
+part of the distribution).  <i>MathsPic</i> is available either as
+a <i>Basic</i> program for DOS, or as a <i>Perl</i>
+program for other systems (including Windows, nowadays).
+<dl>
+<dt><tt><i>m-pictex.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a>
+<dt><tt><i>m-pictex.tex</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a>
+<dt><tt><i>MathsPic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.zip">graphics/mathspic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/mathspic/">browse</a>)
+<dt><tt><i>pictexwd.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.zip">graphics/pictex/addon</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon/">browse</a>)
+</dl>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html
new file mode 100644
index 00000000000..56621c87624
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label usepsfont</title>
+</head><body>
+<h3>Using PostScript fonts with TeX</h3>
+<p/>In order to use PostScript fonts, TeX needs
+<em>metric</em> (called TFM) files. Several sets of metrics are
+available from the archives; for mechanisms for generating new ones,
+see <a href="FAQ-metrics.html">metrics for PostScript fonts</a>.  You
+also need the fonts themselves; PostScript printers come with a set of
+fonts built in, but to extend your repertoire you almost invariably
+need to buy from one of the many commercial font vendors (see, for
+example, <a href="FAQ-psfchoice.html">&ldquo;choice of fonts&rdquo;</a>).
+<p/>If you use LaTeX2e, the best way to get PostScript fonts into your
+document is to use the PSNFSS package maintained by Walter
+Schmidt.  The LaTeX3 project team declare that PSNFSS is
+&ldquo;required&rdquo;, and bug reports may be submitted via the 
+<a href="FAQ-latexbug.html">LaTeX bugs system</a>. 
+PSNFSS gives you a set of packages for changing the default
+roman, sans-serif and typewriter fonts; <em>e.g</em>., the
+<i>mathptmx</i> package will set up <i>Times</i>
+<i>Roman</i> as the main text font (and introduces mechanisms to
+typeset mathematics using <i>Times</i> and various more-or-less
+matching fonts),  while package <i>avant</i> changes the sans-serif
+family to <i>AvantGarde</i>, and <i>courier</i> changes the
+typewriter font to <i>Courier</i>.  To go with these
+packages, you need the font metric files
+and font description (<i>.fd</i>) files for each font family you
+want to use.  For convenience,
+metrics for the &lsquo;common 35&rsquo; PostScript fonts found in most PostScript printers
+are provided with PSNFSS, packaged as the &ldquo;Laserwriter set&rdquo;.
+<p/>For older versions of LaTeX there are various schemes, of which the
+simplest to use is probably the PSLaTeX macros distributed with
+<i>dvips</i>.
+<p/>For Plain TeX, 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
+<i>ps2pk</i> and <i>afm2tfm</i>.
+<p/>Victor Eijkhout&rsquo;s <a href="FAQ-lollipop.html">Lollipop package</a>
+supports declaration of font families and styles in a similar way to
+LaTeX&rsquo;s NFSS, and so is easy to use with PostScript fonts.
+<p/>Some common problems encountered are discussed elsewhere
+(see <a href="FAQ-psfontprob.html">problems with PS fonts</a>).
+<dl>
+<dt><tt><i>Metrics for the &lsquo;Laserwriter&rsquo; set of 35 fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a>
+<dt><tt><i>lollipop</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.zip">macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse</a>)
+<dt><tt><i>psnfss</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html
new file mode 100644
index 00000000000..7ddbf95f1b8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label varwidcol</title>
+</head><body>
+<h3>Variable-width columns in tables</h3>
+<p/>This is a slightly different take on the problem addressed in
+&ldquo;<a href="FAQ-fixwidtab.html">fixed-width tables</a>&rdquo; &mdash; here we have
+a column whose size we can&rsquo;t absolutely predict when we design the
+document.
+<p/>While the basic techniques (the <i>tabularx</i>, <i>tabulary</i>
+and <i>ltxtable</i> packages) are the same for this problem as for the
+fixed-width <em>table</em> problem, there&rsquo;s one extra tool that we can
+call to our aid, which may be preferable in some situations.
+<p/>Suppose we have data in one column which we read from an external
+source, and the source itself isn&rsquo;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&rsquo;t want to make the column as wide as possible &ldquo;just
+in case&rdquo;, 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
+<code>p</code>-style column.
+<p/>The <i>varwidth</i> package, discussed in 
+&ldquo;<a href="FAQ-varwidth.html">automatic sizing of minipages</a>&rdquo;, provides
+a solution.  If you load it together with the LaTeX &ldquo;required&rdquo;
+<i>array</i> package, i.e.:
+<blockquote>
+<pre>
+\usepackage{array}
+\usepackage{varwidth}
+</pre>
+</blockquote><p>
+<i>varwidth</i> defines a new column-type &ldquo;<code>V</code>&rdquo;, which you
+can use as follows:
+<blockquote>
+<pre>
+\begin{tabular}{l V{3.5cm} r}
+  foo & blah      & bar \\
+  foo & blah blah & bar \\
+\end{tabular}
+</pre>
+</blockquote><p>
+when the second column ends up less than 3.5cm wide;
+or you can use it as follows:
+<blockquote>
+<pre>
+\begin{tabular}{l V{3.5cm} r}
+  foo & blah      & bar \\
+  foo & blah blah & bar \\
+  foo & blah blah blah blah blah blah
+                  & bar \\
+\end{tabular}
+</pre>
+</blockquote><p>
+where the second column will end up noticeably wider, and will wrap to
+a second line in the third row.
+<dl>
+<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+<dt><tt><i>varwidth.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html
new file mode 100644
index 00000000000..31f029b31e8
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html
@@ -0,0 +1,70 @@
+<head>
+<title>UK TeX FAQ -- question label varwidth</title>
+</head><body>
+<h3>Automatic sizing of <code>minipage</code></h3>
+<p/>The <code>minipage</code> environment requires you to specify the
+width of the &ldquo;page&rdquo; you&rsquo;re going to create.  This is sometimes
+inconvenient: you would like to occupy less space, if possible, but
+<code>minipage</code> sets a box that is exactly the width you
+specified.
+<p/>The <i>pbox</i> package defines a <code>\</code><code>pbox</code> whose width is exactly
+that of the longest enclosed line, subject to a maximum width that you
+give it.  So while <code>\</code><code>parbox{2cm}{Hello\\world!}</code> produces a
+box of width exactly <code>2cm</code>,
+<code>\</code><code>pbox{2cm}{Hello\\world!}</code> produces one whose width is
+<code>1.79cm</code> (if one&rsquo;s using the default <i>cmr</i> font for the
+text, at least).  The package also provides a
+<code>\</code><code>settominwidth[</code><em>min</em><code>]{</code><em>length</em><code>}{</code><em>text</em><code>}</code> (which looks (almost)
+like the standard <code>\</code><code>settowidth</code> command), and a <code>\</code><code>widthofpbox</code>
+function analogous to the <code>\</code><code>widthof</code> command for use with the
+<i>calc</i> package.
+<p/>The <i>eqparbox</i> package extends <i>pbox</i>&rsquo;s idea, by
+allowing you to set a series of boxes, all with the same (minimised)
+width.  (Note that it doesn&rsquo;t accept a limiting maximum width
+parameter.)  The package documentation shows the following example
+drawn from a joke <em>curriculum vitae</em>:
+<blockquote>
+
+<pre>
+\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}}
+</pre>
+</blockquote><p>
+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 <code>\</code><code>eqboxwidth</code> 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 <code>c</code>-,
+<code>r</code>- or <code>l</code>-rows, with the equivalent of a <code>p{...}</code>
+entry, by making the fixed-width rows an <i>eqparbox</i> group, and
+making the last from a <code>\</code><code>parbox</code> using the width that&rsquo;s been
+measured for the group.
+<p/>The <i>varwidth</i> package defines a <code>varwidth</code>
+environment which sets the content of the box to match a &ldquo;narrower
+natural width&rdquo; if it finds one.  (You give it the same parameters as
+you would give <code>minipage</code>: in effect, it is a &lsquo;drop-in&rsquo;
+replacement.)  <i>Varwidth</i> provides its own ragged text command:
+<code>\</code><code>narrowragged</code>, 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 <code>\</code><code>raggedright</code>
+itself).
+<p/>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.
+<dl>
+<dt><tt><i>eqparbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eqparbox.zip">macros/latex/contrib/eqparbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eqparbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eqparbox/">browse</a>)
+<dt><tt><i>pbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pbox.zip">macros/latex/contrib/pbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pbox/">browse</a>)
+<dt><tt><i>varwidth.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a>
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html
new file mode 100644
index 00000000000..08d6a2c9fc1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html
@@ -0,0 +1,62 @@
+<head>
+<title>UK TeX FAQ -- question label verbfile</title>
+</head><body>
+<h3>Including a file verbatim in LaTeX</h3>
+<p/>A good way is to use Rainer Sch&ouml;pf&rsquo;s <i>verbatim</i> package,
+which provides a command <code>\</code><code>verbatiminput</code> that takes a file name as
+argument:
+<blockquote>
+<pre>
+\usepackage{verbatim}
+...
+\verbatiminput{verb.txt}
+</pre>
+</blockquote><p>
+Another way is to use the <code>alltt</code> environment, which
+requires the <i>alltt</i> package.  The environment interprets its
+contents &lsquo;mostly&rsquo; verbatim, but executes any (La)TeX commands it
+finds:
+<blockquote>
+<pre>
+\usepackage{alltt}
+...
+\begin{alltt}
+\input{verb.txt}
+\end{alltt}
+</pre>
+</blockquote><p>
+of course, this is little use for inputting (La)TeX source
+code...
+<p/>The <i>moreverb</i> package extends the <i>verbatim</i> package,
+providing a <code>listing</code> environment and a <code>\</code><code>listinginput</code>
+command, which line-number the text of the file.  The package also has
+a <code>\</code><code>verbatimtabinput</code> command, that honours TAB characters in
+the input (the package&rsquo;s <code>listing</code> environment and the
+<code>\</code><code>listinginput</code> command also both honour TAB).
+<p/>The <i>sverb</i> package provides verbatim input (without recourse
+to the facilities of the <i>verbatim</i> package):
+<blockquote>
+<pre>
+\usepackage{sverb}
+...
+\verbinput{verb.txt}
+</pre>
+</blockquote><p>
+<p/>The <i>fancyvrb</i> package offers configurable implementations of
+everything <i>verbatim</i>, <i>sverb</i> and <i>moreverb</i>
+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.
+<p/>The <i>memoir</i> class includes the relevant functionality of the
+<i>verbatim</i> and <i>moreverb</i> packages.
+<dl>
+<dt><tt><i>alltt.sty</i></tt><dd>Part of the LaTeX distribution.
+<dt><tt><i>fancyvrb.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>moreverb.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moreverb.zip">macros/latex/contrib/moreverb</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moreverb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb/">browse</a>)
+<dt><tt><i>sverb.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>)
+<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html
new file mode 100644
index 00000000000..f6379c0d327
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html
@@ -0,0 +1,129 @@
+<head>
+<title>UK TeX FAQ -- question label verbwithin</title>
+</head><body>
+<h3>Why doesn&rsquo;t verbatim work within ...?</h3>
+<p/>The LaTeX verbatim commands work by changing category codes.  Knuth
+says of this sort of thing &ldquo;Some care is needed to get the timing
+right...&rdquo;, since once the category code has been assigned to a
+character, it doesn&rsquo;t change.  So <code>\</code><code>verb</code> and
+<code>\</code><code>begin{verbatim}</code> have to assume that they are getting the
+first look at the parameter text; if they aren&rsquo;t, TeX has already
+assigned category codes so that the verbatim command doesn&rsquo;t have a
+chance.  For example:
+<blockquote>
+<pre>
+\verb+\error+
+</pre>
+</blockquote><p>
+will work (typesetting &lsquo;<code>\</code><code>error</code>&rsquo;), but
+<blockquote>
+<pre>
+\newcommand{\unbrace}[1]{#1}
+\unbrace{\verb+\error+}
+</pre>
+</blockquote><p>
+will not (it will attempt to execute <code>\</code><code>error</code>).  Other errors one
+may encounter are &lsquo;<code>\</code><code>verb</code> ended by end of line&rsquo;, or even the
+rather more helpful &lsquo;<code>\</code><code>verb</code> illegal in command argument&rsquo;.  The
+same sorts of thing happen with <code>\</code><code>begin{verbatim}</code> ...
+<code>\</code><code>end{verbatim}</code>:
+<blockquote>
+<pre>
+\ifthenelse{\boolean{foo}}{%
+\begin{verbatim}
+foobar
+\end{verbatim}
+}{%
+\begin{verbatim}
+barfoo
+\end{verbatim}
+}
+</pre>
+</blockquote><p>
+provokes errors like &lsquo;File ended while scanning use of
+<code>\</code><code>@xverbatim</code>&rsquo;, as <code>\</code><code>begin{verbatim}</code> fails to see its
+matching <code>\</code><code>end{verbatim}</code>.
+<p/>This is why the LaTeX book insists that verbatim
+commands must not appear in the argument of any other command; they
+aren&rsquo;t just fragile, they&rsquo;re quite unusable in any command parameter,
+regardless of <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a>.  (The <code>\</code><code>verb</code>
+command tries hard to detect if you&rsquo;re misusing it; unfortunately, it
+can&rsquo;t always do so, and the error message is therefore not a reliable
+indication of problems.)
+<p/>The first question to ask yourself is: &ldquo;is <code>\</code><code>verb</code> actually
+necessary?&rdquo;.
+<ul>
+<li> If <code>\</code><code>texttt{<em>your text</em>}</code> produces the same result
+  as <code>\</code><code>verb</code><code>+<em>your text</em>+</code>, then there&rsquo;s no need of
+  <code>\</code><code>verb</code> in the first place.
+<li> If you&rsquo;re using <code>\</code><code>verb</code> to typeset a URL or email
+  address or the like, then the <code>\</code><code>url</code> command from the
+  <i>url</i> will help: it doesn&rsquo;t suffer from all the problems of
+  <code>\</code><code>verb</code>, though it&rsquo;s still not robust; 
+  &rdquo;<a href="FAQ-setURL.html">typesetting URLs</a>&rdquo; offers advice here.
+<li> If you&rsquo;re putting <code>\</code><code>verb</code> into the argument of a boxing
+  command (such as <code>\</code><code>fbox</code>), consider using the <code>lrbox</code>
+  environment:
+<blockquote>
+<pre>
+\newsavebox{\mybox}
+...
+\begin{lrbox}{\mybox}
+  \verb!VerbatimStuff!
+\end{lrbox}
+\fbox{\usebox{\mybox}}
+</pre>
+</blockquote><p>
+</ul>
+<p/>Otherwise, there are three partial solutions to the problem.
+<ul>
+<li> Some packages have macros which are designed to be responsive
+  to verbatim text in their arguments.  For example,
+  the <i>fancyvrb</i> package defines a command
+  <code>\</code><code>VerbatimFootnotes</code>, which redefines the <code>\</code><code>footnotetext</code> (and
+  hence the <code>\</code><code>footnote</code>) commands in such a way that you can include
+  <code>\</code><code>verb</code> 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, <code>\</code><code>VerbatimFootnotes</code>
+  interacts poorly with the <code>para</code> option to the <i>footmisc</i>
+  package.
+<p/>  The <i>memoir</i> class defines its <code>\</code><code>footnote</code> command so that
+  it will accept verbatim in its arguments, without any supporting package.
+<li> The <i>fancyvrb</i> package defines a command <code>\</code><code>SaveVerb</code>,
+  with a corresponding <code>\</code><code>UseVerb</code> 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.
+<p/>  Rather simpler is the <i>verbdef</i> package, which defines a
+  (robust) command which expands to the verbatim argument given.
+<li> If you have a single character that is giving trouble (in
+  its absence you could simply use <code>\</code><code>texttt</code>), consider using
+  <code>\</code><code>string</code>.  <code>\</code><code>texttt{my<code>\</code><code>string</code>_name}</code>
+  typesets the same as 
+  <code>\verb+my_name+</code>, and will work in the argument of a command.  It
+  won&rsquo;t, however, work in a moving argument, and no amount of
+  <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a> will make it work in
+  such a case.
+<p/>  A robust alternative is:
+  <blockquote>
+<pre>
+\chardef\us=`\_
+...
+\section{... \texttt{my\us name}}
+</pre>
+  </blockquote><p>
+  Such a definition is &lsquo;naturally&rsquo; robust; the construction
+  &ldquo;&lt;<i>back-tick</i>&gt;<code>\</code><code>&lt;<i>char</code></i>&gt;&rdquo; may be used for any
+  troublesome character (though it&rsquo;s plainly not necessary for things
+  like percent signs for which (La)TeX already provides
+  robust macros).
+</ul>
+Documentation of both <i>url</i> and <i>verbdef</i> is in the
+package files.
+<dl>
+<dt><tt><i>fancyvrb.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyvrb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+<dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a>
+<dt><tt><i>verbdef.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/verbdef.sty">macros/latex/contrib/misc/verbdef.sty</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html
new file mode 100644
index 00000000000..ab7f42388c5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html
@@ -0,0 +1,49 @@
+<head>
+<title>UK TeX FAQ -- question label vertposfp</title>
+</head><body>
+<h3>Vertical layout of float pages</h3>
+<p/>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 &ldquo;buried&rdquo; in
+LaTeX-internal commands, so some care is needed to change the
+layout.
+<p/>Float pages use three LaTeX lengths (i.e., TeX skips) to define
+their layout:
+<dl>
+<dt><code>\</code><code>@fptop</code><dd> defines the distance from the
+  top of the page to the top of the first float,
+<dt><code>\</code><code>@fpsep</code><dd> defines the separation between
+  floats, and
+<dt><code>\</code><code>@fpbot</code><dd> defines the distance from the
+  bottom of the last float on the page to the bottom of the page.
+</dl>
+(In fact, the output routine places a skip of <code>\</code><code>@fpsep</code> above each float, so
+the <code>\</code><code>@fptop</code> skip is always followed by a correction for that.)
+<p/><p/>The LaTeX defaults are:
+<blockquote>
+  <code>\</code><code>@fptop</code> = <code>0pt + 1fil</code><br>
+  <code>\</code><code>@fpsep</code> = <code>8pt + 2fil</code><br>
+  <code>\</code><code>@fpbot</code> = <code>0pt + 1fil</code><br>
+</blockquote><p>
+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.
+<p/>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:
+<blockquote>
+<pre>
+\makeatletter
+\setlength{\@fptop}{0pt}
+\makeatother
+</pre>
+</blockquote><p>
+Surprisingly, you may find this setting leaves your floats too high on
+the page.  One can justify a value of <code>5pt</code> (in place of
+<code>0pt</code>) &mdash; it&rsquo;s roughly the difference between <code>\</code><code>topskip</code>
+and the height of normal (<code>10pt</code>) text.
+<p/>Note that this is a &ldquo;global&rdquo; 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.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html
new file mode 100644
index 00000000000..bd77a1823ae
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html
@@ -0,0 +1,57 @@
+<head>
+<title>UK TeX FAQ -- question label vertspacefloat</title>
+</head><body>
+<h3>Extra vertical space in floats</h3>
+<p/>A common complaint is that extra vertical space has crept into
+<code>figure</code> or <code>table</code> floating environments.
+More common still are users who post code that introduces this extra
+space, and <em>haven&rsquo;t noticed the problem</em>!
+<p/>The trouble arises from the fact that the <code>center</code>
+environment (and its siblings <code>flushleft</code> and
+<code>flushright</code>) are actually based on LaTeX&rsquo;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:
+<blockquote>
+<pre>
+\begin{figure}
+ \begin{center}
+   \includegraphics{...}
+   \caption{...}
+ \end{center}
+\end{figure}
+</pre>
+</blockquote><p>
+or worse still:
+<blockquote>
+<pre>
+\begin{figure}
+ \begin{center}
+   \includegraphics{...}
+ \end{center}
+ \caption{...}
+\end{figure}
+</pre>
+</blockquote><p>
+unwarranted vertical space is going to appear.
+<p/>The solution is to let the float and the objects in it position
+themselves, and to use &ldquo;generic&rdquo; layout commands rather than their
+list-based encapsulations.
+<blockquote>
+<pre>
+\begin{figure}
+  \centering
+  \includegraphics{...}
+  \caption{...}
+\end{figure}
+</pre>
+</blockquote><p>
+(which even involves less typing).
+<p/>This alternative code will work with any LaTeX package.  It will
+not work with obsolete (pre-LaTeX2e) packages such as
+<i>psfig</i> or <i>epsf</i> &mdash; see 
+<a href="FAQ-impgraph.html">graphics inclusion</a> for discussion of the
+genesis of <code>\</code><code>includegraphics</code>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html
new file mode 100644
index 00000000000..dc3ae3f7377
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html
@@ -0,0 +1,63 @@
+<head>
+<title>UK TeX FAQ -- question label virtualfonts</title>
+</head><body>
+<h3>Virtual fonts</h3>
+<p/>Virtual fonts provide a means of collecting bits and pieces together
+to make the glyphs of a font: the bits and pieces may be other glyphs,
+rules and other &ldquo;basic&rdquo; typesetting commands, and the positioning
+information that specifies how everything comes together.
+<p/>Things that match the concept of virtual fonts for TeX were first
+implemented by David Fuchs in the very early days.  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 article in <i>TUGboat</i> at the time, and a plain text
+copy is available on CTAN).
+<p/>Virtual fonts provide a way of telling TeX about something more
+complicated than just a one-to-one character mapping. The entities you
+define in a virtual font look like characters to TeX (they appear
+with their sizes in a TFM file), but the DVI processor may
+expand them to something quite different.
+<p/>From the virtual font file, the DVI processor learns
+details of what is in the virtual font, so as to know &ldquo;what to draw,
+where&rdquo;.   The virtual font may contain commands:
+<ul>
+<li> just to remap the glyphs of a single font,
+<li> to make a composite font with glyphs drawn from several
+  different fonts, or
+<li> to build up an effect in arbitrarily complicated ways (since a
+  virtual font may contain anything which is legal in a DVI
+  file).
+</ul>
+<p/>
+
+In practice, the most common use of virtual fonts is to remap
+Adobe Type 1 fonts (see <a href="FAQ-metrics.html">font metrics</a>),
+though there has also been useful useful work building &lsquo;fake&rsquo; maths
+fonts (by bundling glyphs from several fonts into a single virtual
+font).  Virtual Computer Modern fonts, making a 
+<a href="FAQ-ECfonts.html">Cork encoded</a> font from Knuth&rsquo;s originals by using
+remapping and fragments of DVI for single-glyph &lsquo;accented
+characters&rsquo;, were the first &ldquo;Type 1 format&rdquo; Cork-encoded Computer
+Modern fonts available.
+<p/>Virtual fonts are normally created in a single ASCII
+VPL (Virtual Property List) file, which includes both sets of
+information. The <i>vptovf</i> program is then used to the create
+the binary TFM and VF files.
+<p/>A &ldquo;how-to&rdquo; document, explaining how to generate a VPL,
+describes the endless hours of fun that may be had, doing the job by
+hand.  Despite the pleasures to be had of the manual method, the
+commonest way (nowadays) of generating VPL files is to use the
+<i>fontinst</i> package, which is described in detail
+together with the discussion of
+<a href="FAQ-metrics.html">PostScript font metrics</a>.
+<i>Qdtexvpl</i> is another utility for creating ad-hoc virtual
+fonts (it uses TeX to parse a description of the virtual font, and
+<i>qdtexvpl</i> itself processes the resulting DVI file).
+<dl>
+<dt><tt><i>fontinst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>)
+<dt><tt><i>Knuth on virtual fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/knuth/virtual-fonts">info/knuth/virtual-fonts</a>
+<dt><tt><i>Virtual fonts &ldquo;how to&rdquo;</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a>
+<dt><tt><i>qdtexvpl</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.zip">fonts/utilities/qdtexvpl</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/qdtexvpl/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html
new file mode 100644
index 00000000000..fb996352f51
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label watermark</title>
+</head><body>
+<h3>&lsquo;Watermarks&rsquo; on every page</h3>
+<p/>It&rsquo;s often useful to place some text (such as &lsquo;DRAFT&rsquo;) in the
+background of every page of a document.  For LaTeX users, this can
+be achieved with the <i>draftcopy</i> package.  This can deal with
+many types of DVI processors (in the same way that the graphics
+package does) and knows translations for the word &lsquo;DRAFT&rsquo; into a wide
+range of languages (though you can choose your own word, too).
+Unfortunately, however, the package relies on PostScript specials, and will
+therefore fail if you are viewing your document with <i>xdvi</i>,
+and won&rsquo;t even compile if you&rsquo;re using PDFLaTeX.  (PDFLaTeX
+users need one of the other solutions below.)
+<p/>The <i>wallpaper</i> package builds on <i>eso-pic</i> (see
+below).  Apart from the single-image backdrops described above
+(&ldquo;wallpapers&rdquo;, of course, to this package), the package provides
+facilities for tiling images.  All its commands come in pairs: one for
+&ldquo;general&rdquo; use, and one applying to the current page only.
+<p/>The <i>draftwatermark</i> package uses the same author&rsquo;s
+<i>everypage</i> package to provide a simple interface for adding
+textual (&lsquo;DRAFT&rsquo;-like) watermarks.
+<p/>More elaborate watermarks may be achieved using the <i>eso-pic</i>
+package, which in turn uses the package <i>everyshi</i>, or by
+using <i>everypage</i>.  <i>Eso-pic</i> attaches a
+<code>picture</code> environment to every page as it is shipped out;
+you can put things into that environment.  The package provides
+commands for placing things at certain useful points (like &ldquo;text
+upper left&rdquo; or &ldquo;text centre&rdquo;) in the picture, but you&rsquo;re at liberty
+to do what you like.
+<p/><i>Everypage</i> allows you to add &ldquo;something&rdquo; to every page, or
+to a particular page; you therefore need to construct your own
+apparatus for anything complicated.
+<dl>
+<dt><tt><i>draftcopy.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftcopy.zip">macros/latex/contrib/draftcopy</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftcopy.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftcopy/">browse</a>)
+<dt><tt><i>draftwatermark.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftwatermark.zip">macros/latex/contrib/draftwatermark</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftwatermark.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftwatermark/">browse</a>)
+<dt><tt><i>eso-pic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.zip">macros/latex/contrib/eso-pic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic/">browse</a>)
+<dt><tt><i>everypage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/everypage.zip">macros/latex/contrib/everypage</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/everypage.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/everypage/">browse</a>)
+<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>)
+<dt><tt><i>wallpaper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.zip">macros/latex/contrib/wallpaper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wallpaper/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html
new file mode 100644
index 00000000000..35e272da889
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html
@@ -0,0 +1,54 @@
+<head>
+<title>UK TeX FAQ -- question label wdnohyph</title>
+</head><body>
+<h3>Preventing hyphenation of a particular word</h3>
+<p/>It&rsquo;s quite possible for (<em>any</em>) hyphenation of a particular word
+to seem &ldquo;completely wrong&rdquo;, so that you want to prevent it being
+hyphenated.
+<p/>If the word occurs in just one place, put it in a box:
+<blockquote>
+<pre>
+\mbox{oddword}
+</pre>
+</blockquote><p>
+(Plain TeX users should use <code>\</code><code>hbox</code>, and take care at the start
+of paragraphs.)  However, boxing the word is not really advisable
+unless you are sure it only occurs once.
+<p/>If the word occurs commonly, the best choice is to assert a
+non-hyphenation for it:
+<blockquote>
+<pre>
+\hyphenation{oddword}
+</pre>
+</blockquote><p>
+This hyphenation exception (with no break points) will be used in
+preference to what TeX&rsquo;s hyphenation algorithm may come up with.
+<p/>In a multilingual document, repeat the exception specification for
+each language the word may appear in.  So:
+<blockquote>
+<pre>
+\usepackage[french,english]{babel}
+\selectlanguage{english}
+\hyphenation{oddword}
+\selectlanguage{french}
+\hyphenation{oddword}
+</pre>
+</blockquote><p>
+(note that <i>babel</i> will select the default language for the
+document &mdash; English, in this case &mdash; at <code>\</code><code>begin{document}</code>.)
+<p/>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 &ldquo;real&rdquo; word, but hyphenating an acronym often looks silly.
+The TeX flag <code>\</code><code>uchyph</code> is designed for suppressing such
+behaviour:
+<blockquote>
+<pre>
+\uchyph=0
+</pre>
+</blockquote><p>
+will stop hyphenation of upper-case words.  (Note that Plain TeX
+syntax is needed here: there&rsquo;s no LaTeX alternative for setting
+this value.)
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html
new file mode 100644
index 00000000000..c3e8a9421c5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label webpkgs</title>
+</head><body>
+<h3>WEB systems for various languages</h3>
+<p/>TeX is written in the programming language WEB; WEB
+is a tool to implement the concept of &ldquo;literate programming&rdquo;.
+Knuth&rsquo;s original implementation will be in any respectable
+distribution of TeX, but the sources of the two tools
+(<i>tangle</i> and <i>weave</i>), together with a manual
+outlining the programming techniques, may be had from CTAN.
+<p/><i>CWEB</i>, by Silvio Levy, is a WEB for C programs.
+<p/>Spidery WEB, by Norman Ramsey, supports many 
+languages including Ada, <code>awk</code>, and C
+and, while not in the public domain, is usable without charge.  It is
+now superseded by <i>noweb</i> (also by Norman Ramsay) which
+incorporates the lessons learned in implementing spidery WEB,
+and which is a simpler, equally powerful, tool.
+<p/><i>FWEB</i>, by John Krommes, is a version for Fortran,
+Ratfor, and C. 
+<p/><i>Scheme</i><i>WEB</i>, by John Ramsdell, is a Unix filter that
+translates SchemeWEB into LaTeX source or Scheme source.
+<p/><i>APLWEB</i> is a version of WEB for APL.
+<p/><i>FunnelWeb</i> is a version of WEB that is language independent.
+<p/>Other language independent versions of WEB are <i>nuweb</i> (which
+is written in ANSI C).
+<p/><i>Tweb</i> is a WEB for Plain TeX macro files, using
+<i>noweb</i>.
+<dl>
+<dt><tt><i>aplweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/apl/aplweb.zip">web/apl/aplweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/apl/aplweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/apl/aplweb/">browse</a>)
+<dt><tt><i>cweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/c_cpp/cweb.zip">web/c_cpp/cweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/c_cpp/cweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/c_cpp/cweb/">browse</a>)
+<dt><tt><i>funnelweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/funnelweb.zip">web/funnelweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/funnelweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/funnelweb/">browse</a>)
+<dt><tt><i>fweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/fweb.zip">web/fweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/fweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/fweb/">browse</a>)
+<dt><tt><i>noweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/noweb.zip">web/noweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/noweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/noweb/">browse</a>)
+<dt><tt><i>nuweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/nuweb.zip">web/nuweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/nuweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/nuweb/">browse</a>)
+<dt><tt><i>schemeweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/schemeweb.zip">web/schemeweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/schemeweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/schemeweb/">browse</a>)
+<dt><tt><i>spiderweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/spiderweb.zip">web/spiderweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/spiderweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/spiderweb/">browse</a>)
+<dt><tt><i>tangle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/dist/web.zip">systems/knuth/dist/web</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/knuth/dist/web.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/dist/web/">browse</a>)
+<dt><tt><i>tweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/tweb.zip">web/tweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/tweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/tweb/">browse</a>)
+<dt><tt><i>weave</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/dist/web.zip">systems/knuth/dist/web</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/knuth/dist/web.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/dist/web/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html
new file mode 100644
index 00000000000..b722d797144
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html
@@ -0,0 +1,34 @@
+<head>
+<title>UK TeX FAQ -- question label weirdhyphen</title>
+</head><body>
+<h3>Weird hyphenation of words</h3>
+<p/>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&rsquo;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 Plain TeX, make
+sure your <i>plain.tex</i> file has a version number which is at
+least 3.0, and rebuild your format.  If you are using LaTeX 2.09 your
+best plan is to upgrade to LaTeX2e.  If for some reason you can&rsquo;t,
+the last version of LaTeX 2.09 (released on 25 March 1992) is still
+available (for the time being at least) and ought to solve this
+problem.
+<p/>If you&rsquo;re using LaTeX2e, the problem probably arises from your
+<code>hyphen.cfg</code> file, which has to be created if you&rsquo;re using a
+multi-lingual version.
+<p/>A further source of oddity can derive from the 1995 release of
+<a href="FAQ-ECfonts.html">Cork-encoded fonts</a>,
+which introduced an alternative hyphen character.  The LaTeX2e
+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 LaTeX2e do <em>not</em> use the alternative
+hyphen character, and therefore removed this source of problems; the
+solution, again, is to upgrade your LaTeX.
+<dl>
+<dt><tt><i>LaTeX 2.09</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/macros/latex209/distribs/latex209.tar.gz">obsolete/macros/latex209/distribs/latex209.tar.gz</a>
+<dt><tt><i>plain.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/base.zip">macros/plain/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/base/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html
new file mode 100644
index 00000000000..a6e44a2149f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html
@@ -0,0 +1,84 @@
+<head>
+<title>UK TeX FAQ -- question label what-TDS</title>
+</head><body>
+<h3>Which tree to use</h3>
+<p/>In almost all cases, new material that you install should go into the
+&ldquo;local&rdquo; tree of your (La)TeX installation.  (A discussion of
+reasons <em>not</em> to use the local tree appears below.)
+<p/>On a Unix(-alike) system, using teTeX or TeX Live, the root
+directory will be named something like <i>/usr/share/texmf-local/</i>
+or <i>/usr/local/share/texmf/</i>
+You can ask such a system where it believes a local tree should be:
+<blockquote>
+<pre>
+kpsewhich -expand-var "\$TEXMFLOCAL"
+</pre>
+</blockquote><p>
+the output being the actual path, for example (on the workstation the
+author is using today):
+<blockquote>
+<pre>
+/usr/local/share/texmf
+</pre>
+</blockquote><p>
+<p/>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
+&ldquo;Settings&rdquo; window (
+  <code>Start</code>-&gt; 
+  <code>Programs</code>-&gt; 
+  <code>MiKTeX</code>-&gt; 
+  <code>Settings</code>)
+has a tab &ldquo;<code>Roots</code>&rdquo;; that tab gives a list of current
+TDS roots (they&rsquo;re typically not called
+<code>texmf</code>-anything).  If there&rsquo;s not one there with
+&ldquo;<code>local</code>&rdquo; in its name, create an appropriate one (see below),
+and register it using the window&rsquo;s
+&ldquo;<code>Add</code>&rdquo; button.
+<p/>The 
+<a href="http://docs.miktex.org/faq/maintenance.html">MiKTeX FAQ</a>
+suggests that you should create 
+&ldquo;<code>C:\Local TeX Files</code>&rdquo;, which is good if you
+manage your own machine, but often not even possible in corporate, or
+similar, environments ­&ndash; in such situations, the user may have no
+control over the hard disc of the computer, at all.
+<p/>So the real criterion is that your local tree should be somewhere that
+<em>you</em>, rather than the system, control.  Restrictive systems often
+provide a &ldquo;home directory&rdquo; for each user, mounted as a network
+drive; this is a natural home for the user&rsquo;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 ­&ndash; another good
+candidate location.  Note that the semantics of such a tree are
+indistinguishable from those of a 
+<a href="FAQ-privinst.html">&ldquo;home&rdquo; TEXMF tree</a>.
+<p/>There are circumstances when you might not wish to use the &lsquo;local&rsquo; tree:
+<ul>
+<li> if the package, or whatever, is &ldquo;personal&rdquo; (for example,
+  something commercial that has been licensed to you alone, or
+  something you&rsquo;re developing yourself), the package should go in your
+  <a href="FAQ-privinst.html">&ldquo;home&rdquo; TEXMF tree</a>;
+<li> if you <em>know</em> that the package you are installing is a
+  replacement for the copy on the TEXMF tree of your (La)TeX
+  distribution, you should replace the existing copy in the
+  TEXMF tree.
+</ul>
+The reason one would put things on a local tree is to avoid their
+disappearance if the system is upgraded (or otherwise re-installed).
+<p/>The reason one might place upgrades the distribution&rsquo;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 &mdash; you might
+have an effect like:
+<ul>
+<li> distribution comes with package version n;
+<li> you install package version n+1 on the local tree; and
+<li> the updated distribution comes with package version n+2.
+</ul>
+In such a situation, you will find yourself using version
+n+1 (from the local tree) <em>after</em> the new
+distribution has been installed.
+<p/>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&rsquo;re maintaining a large
+installation.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html
new file mode 100644
index 00000000000..18536d7d135
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html
@@ -0,0 +1,38 @@
+<head>
+<title>UK TeX FAQ -- question label whatTeX</title>
+</head><body>
+<h3>What is TeX?</h3>
+<p/>TeX is a typesetting system written by
+<a href="http://sunburn.stanford.edu/~knuth/">Donald E. Knuth</a>, who
+says in the Preface to his book on TeX
+(see <a href="FAQ-books.html">books about TeX</a>) that it is
+
+&ldquo;<em>intended for the creation of beautiful books &mdash; and especially for books that contain a lot of mathematics</em>&rdquo;.
+<p/>Knuth is Emeritus Professor of the Art of Computer Programming at
+Stanford University in California, USA.  Knuth developed the
+first version of TeX in 1978 to deal with revisions to his series
+&ldquo;the Art of Computer Programming&rdquo;.  The idea proved popular and
+Knuth produced a second version (in 1982) which is the basis of what
+we use today.
+<p/>Knuth developed a system of 
+&lsquo;<a href="FAQ-lit.html">literate programming</a>&rsquo; to write TeX,
+and he provides the literate (WEB) source of TeX free of charge,
+together with tools for processing the <code>web</code> source into something
+that can be compiled and something that can be printed; there&rsquo;s never
+any mystery about what TeX does.  Furthermore, the 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 <a href="FAQ-triptrap.html">test</a> by
+means of which one may judge the fidelity of a TeX system.  TeX
+and its documents are therefore highly portable.
+<p/>TeX is a macro processor, and offers its users a powerful
+programming capability.  For this reason, TeX on its own is a
+pretty difficult beast to deal with, so Knuth provided a package of
+macros for use with TeX called Plain TeX; Plain TeX is
+effectively the minimum set of macros one can usefully employ with
+TeX, together with some demonstration versions of higher-level
+commands (the latter are better regarded as models than used as-is).
+When people say they&rsquo;re &ldquo;programming in TeX&rdquo;, they usually mean
+they&rsquo;re programming in Plain TeX.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html
new file mode 100644
index 00000000000..71e450dd0cb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html
@@ -0,0 +1,55 @@
+<head>
+<title>UK TeX FAQ -- question label whatbst</title>
+</head><body>
+<h3>Choosing a bibliography style</h3>
+<p/>A large proportion of people are satisfied with one of Patashnik&rsquo;s
+original &ldquo;standard&rdquo; styles, <i>plain</i>, <i>unsrt</i>,
+<i>abbrv</i> and <i>alpha</i>.  However, no style in that set
+supports the &ldquo;author-date&rdquo; citation style that is popular in many
+fields; but there are a very large number of contributed styles
+available, that <em>do</em> support the format.
+<p/>(Note that author-date styles arose because the simple and clear
+citation style that <i>plain</i> 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.)
+<p/>Fortunately, help is at hand, on the Web, with this problem:
+<ul>
+<li> a sample text, showing the sorts of style choices available, can
+  be found on 
+
+  
+  <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">Ken Turner&rsquo;s web site</a>;
+<li> 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 
+
+  
+  &ldquo;<a href="http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html">Choosing a BibTeX style</a>&rdquo;.
+</ul>
+<p/>Of course, these pages don&rsquo;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&rsquo;t
+help) by using <i>xampl.bib</i> from the BibTeX documentation
+distribution: one can get a pretty good feel for any style one has to
+hand using this &ldquo;standard&rdquo; bibliography.  For style
+<i>my-style.bst</i>, the simple LaTeX document:
+<blockquote>
+<pre>
+\documentclass{article}
+\begin{document}
+\bibliographystyle{my-style}
+\nocite{*}
+\bibliography{xampl}
+\end{document}
+</pre>
+</blockquote><p>
+will produce a representative sample of the citations the style will
+produce.  (Because <i>xampl.bib</i> is so extreme in some of its
+&ldquo;examples&rdquo;, the BibTeX run will also give you an interesting
+selection of BibTeX&rsquo;s error messages...)
+<dl>
+<dt><tt><i>xampl.bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc/xampl.bib">biblio/bibtex/distribs/doc/xampl.bib</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html
new file mode 100644
index 00000000000..275f5b60c95
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html
@@ -0,0 +1,78 @@
+<head>
+<title>UK TeX FAQ -- question label whatenc</title>
+</head><body>
+<h3>What are encodings?</h3>
+<p/>Let&rsquo;s start by defining two concepts, the <em>character</em> and the
+<em>glyph</em>.
+The character is the abstract idea of the &lsquo;atom&rsquo; 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&rsquo;s style, the
+essence of the underlying character must be retained.
+<p/>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.
+<p/>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 DVI (or PDF) output.  These
+encodings have rather different properties.
+<p/>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 the input encoding to
+something regular.  Nowadays, 
+the operating system translates keystrokes into a code appropriate for
+the user&rsquo;s language: the encoding used is often a national or
+international standard, though many operating systems use &ldquo;code
+pages&rdquo; defined by Microsoft.  These standards and code pages often
+contain characters that can&rsquo;t appear in the TeX system&rsquo;s input
+stream.  Somehow, these characters have to be dealt with &mdash; so
+an input character like &ldquo;&eacute;&rdquo; needs to be interpreted by TeX in
+a way that that at least mimics the way it interprets &ldquo;<code>\</code><code>&rsquo;</code><code>e</code>&rdquo;.  
+<p/>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
+
+
+<a href="FAQ-virtualfonts.html">virtual font</a>).  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 
+<code>fi</code>.
+<p/>Font encodings became a hot topic when the
+<a href="FAQ-ECfonts.html">Cork encoding</a>
+appeared, because of the possibility of suppressing
+<code>\</code><code>accent</code> commands in the output stream (and hence improving the
+quality of the hyphenation of text in inflected languages, which is
+interrupted by the <code>\</code><code>accent</code> commands &mdash; see
+
+<a href="FAQ-hyphen.html">&ldquo;how does hyphenation work&rdquo;</a>).
+To take advantage of the diacriticised characters represented in the
+fonts, it is necessary to arrange that whenever the
+command sequence &ldquo;<code>\</code><code>&rsquo;</code><code>e</code>&rdquo; has been input
+(explicitly, or implicitly via the sort of mapping of input mentioned
+above), the character that codes the position of the &ldquo;&eacute;&rdquo; glyph is
+used.
+<p/>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 <i>inputenc</i> and
+<i>fontenc</i> do, if operated in tandem on (most) characters in
+the ISO Latin-1 input encoding and the T1 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&rsquo;t always happen that way:
+most font encodings can&rsquo;t match the corresponding input encoding
+nearly so well, and the two packages provide the sort of symmetry the
+LaTeX system needs.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html
new file mode 100644
index 00000000000..6e59347c7ed
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label whatpdftex</title>
+</head><body>
+<h3>What is PDFTeX?</h3>
+<p/>PDFTeX has entered the main stream of TeX distributions: most
+LaTeX and ConTeXt users nowadays use PDFTeX whether they know
+it or not (more precisely, they use an amalgam of PDFTeX and
+<a href="FAQ-etex.html">e-TeX</a>).  So what is PDFTeX?
+<p/>PDFTeX is a development of TeX that is capable of generating
+typeset PDF output in place of DVI.  PDFTeX has
+other capabilities, most notably in the area of fine typographic
+detail (for example, its support for 
+  <a href="FAQ-overfull.html">optimising line breaks</a>),
+
+but its greatest impact to date has been in the area of
+PDF output.
+<p/>PDFTeX started as a topic for H&agrave;n The Th&agrave;nh&rsquo;s Master&rsquo;s thesis,
+and seems first to have been published in <i>TUGboat</i> 18(4), in 1997
+(though it was certainly discussed at the TUG&rsquo;96 conference in
+Russia).
+<p/>While the world was making good use of &ldquo;pre-releases&rdquo; of PDFTeX,
+Th&agrave;nh used it as a test-bed for the micro-typography which was the
+prime subject of his Ph.D. research.  Since Th&agrave;nh 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&agrave;nh); the group has managed
+to maintain a stable platform for general use.
+<p/>Development of PDFTeX has (in essence) stopped: the brave new world
+is to be <a href="FAQ-luatex.html">LuaTeX</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html
new file mode 100644
index 00000000000..8fccd8c871a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html
@@ -0,0 +1,61 @@
+<head>
+<title>UK TeX FAQ -- question label whereFAQ</title>
+</head><body>
+<h3>Where to find FAQs</h3>
+<p/>Bobby Bodenheimer&rsquo;s article, from which this FAQ was developed, used
+to be posted (nominally monthly) to newsgroup
+<i>comp.text.tex</i>. The (long
+obsolete) last posted copy of that article is kept on CTAN for
+auld lang syne.
+<p/>
+
+The sources of the present FAQ
+are available from CTAN.
+<p/>This FAQ and others are regularly mentioned, on
+<i>comp.text.tex</i> and elsewhere, in a &ldquo;pointer FAQ&rdquo;
+which is also saved at <a href="http://tug.org/tex-ptr-faq">http://tug.org/tex-ptr-faq</a>
+<p/>A 2006 innovation from Scott Pakin is the &ldquo;visual&rdquo; LaTeX 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 FAQ on the Web.  The visual
+FAQ is provided in PDF format, on 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
+<p/>Another excellent information source, available in English, is the
+<a href="http://tex.loria.fr">(La)TeX navigator</a>.
+<p/>Both the Francophone TeX user group Gutenberg and the Czech/Slovak
+user group CS-TUG have published translations of this FAQ, with
+extensions appropriate to their languages.
+<p/>Herbert Voss&rsquo;s excellent 
+<a href="http://texnik.de/">LaTeX tips and tricks</a>
+provides excellent advice on most topics one might imagine (though
+it&rsquo;s not strictly a FAQ) &mdash; highly recommended for most
+ordinary mortals&rsquo; use.
+<p/>The Open Directory Project (ODP) maintains a list of sources of
+(La)TeX help, including FAQs.  View the TeX area at
+<a href="http://dmoz.org/Computers/Software/Typesetting/TeX/">http://dmoz.org/Computers/Software/Typesetting/TeX/</a>
+<p/>Other non-English FAQs are available (off-CTAN):
+<dl>
+<dt>German<dd>Posted regularly to <i>de.comp.tex</i>, and archived
+  on CTAN; the FAQ also appears at
+  <a href="http://www.dante.de/faq/de-tex-faq/">http://www.dante.de/faq/de-tex-faq/</a>
+<dt>French<dd>An interactive (full-screen!) FAQ may be found at
+  <a href="http://www.frenchpro6.com/screen.pdf/FAQscreen.pdf">http://www.frenchpro6.com/screen.pdf/FAQscreen.pdf</a>, and a copy
+  for printing at <a href="http://frenchle.free.fr/FAQ.pdf">http://frenchle.free.fr/FAQ.pdf</a>;
+  A FAQ used to be posted regularly to
+  <i>fr.comp.text.tex</i>, and is archived on CTAN &mdash;
+  sadly, that effort seems to have fallen by the wayside.
+<dt>Spanish<dd>See <a href="http://apolo.us.es/CervanTeX/FAQ/">http://apolo.us.es/CervanTeX/FAQ/</a>
+<dt>Czech<dd>See <a href="http://www.fi.muni.cz/cstug/csfaq/">http://www.fi.muni.cz/cstug/csfaq/</a>
+</dl>
+<p/>Resources available on CTAN are:
+<dl>
+<dt><tt><i>Dante FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.zip">help/de-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/de-tex-faq/">browse</a>)
+<dt><tt><i>French FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.zip">help/LaTeX-FAQ-francaise</a> (<a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/LaTeX-FAQ-francaise/">browse</a>)
+<dt><tt><i>Sources of this FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>)
+<dt><tt><i>Obsolete <code>comp.text.tex</code> FAQ</i></tt><dd>
+  <a href="ftp://cam.ctan.org/tex-archive/obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers">obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers</a>
+<dt><tt><i>The visual FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf">info/visualFAQ/visualFAQ.pdf</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html
new file mode 100644
index 00000000000..a4b39068e90
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html
@@ -0,0 +1,50 @@
+<head>
+<title>UK TeX FAQ -- question label wholerow</title>
+</head><body>
+<h3>How to change a whole row of a table</h3>
+<p/>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.
+<p/>With the <i>array</i> package, you can define column modifiers
+which will change the font style for a whole <em>column</em>.  However,
+with a bit of subtlety, one can make such modifiers affect rows rather
+than columns.  So, we set things up by:
+<blockquote>
+
+<pre>
+\usepackage{array}
+\newcolumntype{$}{&gt;{\global\let\currentrowstyle\relax}}
+\newcolumntype{^}{&gt;{\currentrowstyle}}
+\newcommand{\rowstyle}[1]{\gdef\currentrowstyle{#1}%
+  #1\ignorespaces
+}
+</pre>
+</blockquote><p>
+Now, we put &lsquo;<code>$</code>&rsquo; before the first column specifier; and we
+put &lsquo;<code>\textasciicircum</code>&rsquo;
+before the modifiers of subsequent ones.  We then use <code>\</code><code>rowstyle</code> at
+the start of each row we want to modify:
+<blockquote>
+<pre>
+\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}
+</pre>
+</blockquote><p>
+The <i>array</i> package works with several other
+<code>tabular</code>-like environments from other packages (for
+example <code>longtable</code>), but unfortunately this trick won&rsquo;t
+always work.
+<dl>
+<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html
new file mode 100644
index 00000000000..461dd6b7b60
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html
@@ -0,0 +1,31 @@
+<head>
+<title>UK TeX FAQ -- question label why-inp-font</title>
+</head><body>
+<h3>Why bother with <i>inputenc</i> and <i>fontenc</i>?</h3>
+<p/>The standard input encoding for Western Europe (pending the arrival of
+Unicode) is ISO 8859&ndash;1 (commonly known by the standard&rsquo;s
+subtitle &lsquo;Latin-1&rsquo;).  Latin-1 is remarkably close, in the codepoints
+it covers, to the (La)TeX T1 encoding.
+<p/>In this circumstance, why should one bother with <i>inputenc</i>
+and <i>fontenc</i>?  Since they&rsquo;re pretty exactly mirroring each
+other, one could do away with both, and use just <i>t1enc</i>,
+despite its <a href="FAQ-t1enc.html">shortcomings</a>.
+<p/>One doesn&rsquo;t do this for a variety of small reasons:
+<dl>
+<dt>Confusion<dd> You&rsquo;ve been happily working in this mode, and for
+  some reason find you&rsquo;re to switch to writing in German: the effect
+  of using &ldquo;<code>&szlig;</code>&rdquo; is somewhat startling, since T1
+  and Latin-1 treat the codepoint differently.
+<dt>Compatibility<dd> 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&rsquo;t work.
+<dt>Traditional LaTeX<dd> You lapse and write something like
+  <code>\&rsquo;</code><code>e</code> rather than typing <code>&eacute;</code>; only <i>fontenc</i>
+  has the means to convert this LaTeX sequence into the T1
+  character, so an <code>\</code><code>accent</code> primitive slips through into the
+  output, and hyphenation is in danger.
+</dl>
+The <i>inputenc</i>&ndash;<i>fontenc</i> combination seems slow and
+cumbersome, but it&rsquo;s safe.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html
new file mode 100644
index 00000000000..64e06c868c6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label whyfree</title>
+</head><body>
+<h3>If TeX is so good, how come it&rsquo;s free?</h3>
+<p/>It&rsquo;s free because Knuth chose to make it so.  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 GNU General Public
+Licence (&lsquo;Copyleft&rsquo;), TeX itself is not subject to Copyleft.
+<p/>There are commercial versions of TeX available; for some users,
+it&rsquo;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.)
+<p/>This FAQ concentrates on &lsquo;free&rsquo; distributions of TeX, but we
+do at least list the <a href="FAQ-commercial.html">major vendors</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html
new file mode 100644
index 00000000000..520cd27f9d4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html
@@ -0,0 +1,23 @@
+<head>
+<title>UK TeX FAQ -- question label widefigs</title>
+</head><body>
+<h3>Wide figures in two-column documents</h3>
+<p/>Floating figures and tables ordinarily come out the same width as the
+page, but in two-column documents they&rsquo;re restricted to the width of
+the column.  This is sometimes not good enough; so there are alternative
+versions of the float environments &mdash; in two-column documents,
+<code>figure*</code> provides a floating page-wide figure (and <code>table*</code> a
+page-wide table) which will do the necessary.
+<p/>The &ldquo;<code>*</code>&rdquo;ed float environments can only appear at the top of a page,
+or on a whole page &mdash; <code>h</code> or <code>b</code> float placement directives are
+simply ignored.
+<p/>Unfortunately, page-wide equations can only be accommodated inside
+float environments.  You should include them in <code>figure</code> environments,
+or use the <i>float</i> or <i>ccaption</i>package to define a
+new float type. 
+<dl>
+<dt><tt><i>ccaption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse</a>)
+<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html
new file mode 100644
index 00000000000..357ae7d857e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html
@@ -0,0 +1,47 @@
+<head>
+<title>UK TeX FAQ -- question label widows</title>
+</head><body>
+<h3>Controlling widows and orphans</h3>
+<p/>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&rsquo;s flow, and are generally considered &ldquo;bad form&rdquo;;
+(La)TeX 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.
+<p/>The page maker, when forming a page, takes account of
+<code>\</code><code>widowpenalty</code> and <code>\</code><code>clubpenalty</code> (which relates to orphans!).
+These penalties are usually set to the moderate value of <code>150</code>; this
+offers mild discouragement of bad breaks.  You can increase the values
+by saying (for example) <code>\</code><code>widowpenalty</code><code>=500</code>; 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&rsquo;t matter which) to allow widows and orphans, and infinite (10000
+or greater) to forbid them.
+<p/>The problem can be avoided by allowing
+the pagemaker to run pages short, by using the <code>\</code><code>raggedbottom</code>
+directive; however, many publishers insist on the default
+<code>\</code><code>flushbottom</code>; 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.
+<p/>Once you&rsquo;ve exhausted the automatic measures, and have a final draft
+you want to &ldquo;polish&rdquo;, you should proceed to manual measures.  To
+get rid of an orphan is simple: precede the paragraph with
+<code>\</code><code>clearpage</code> and the paragraph can&rsquo;t start in the wrong place.
+<p/>Getting rid of a widow can be more tricky.  If the paragraph is a long
+one, it may be possible to set it &lsquo;tight&rsquo;: say <code>\</code><code>looseness</code><code>=-1</code>
+immediately after the last word of the paragraph.  If that doesn&rsquo;t
+work, try adjusting the page size:
+<code>\</code><code>enlargethispage{<code>\</code><code>baselineskip</code>}</code> may do the job, and
+get the whole paragraph on one page.  Reducing the size of the page by
+<code>\</code><code>enlargethispage{-<code>\</code><code>baselineskip</code>}</code> may produce a
+(more-or-less) acceptable &ldquo;two-line widow&rdquo;.  (Note:
+<code>\</code><code>looseness</code><code>=1</code>,
+increasing the line length by one, seldom seems to work &mdash; the looser
+paragraph typically has a one-word final line, which doesn&rsquo;t look much
+better than the straight widow.)
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html
new file mode 100644
index 00000000000..36b42d6fb41
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label wordcount</title>
+</head><body>
+<h3>How many words have you written?</h3>
+<p/>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.
+<p/>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&rsquo;s life, it takes a
+brave person to thumb their nose at authority quite so
+comprehensively...
+<p/>The simplest method is to strip out the (La)TeX markup, and to count
+what&rsquo;s left.  On a  Unix-like system, this may be done using
+<i>detex</i> and the built-in <i>wc</i>:
+<pre>
+  detex &lt;filename&gt; | wc -w
+</pre>
+The <i>latexcount</i> script does the same sort of job, in one
+&ldquo;step&rdquo;; being a <i>perl</i> script, it is in principle rather
+easily configured (see documentation inside the script).
+<i>Winedt</i> (see <a href="FAQ-editors.html">editors and shells</a>)
+provides this functionality direct in the Windows environment.
+<p/>Simply stripping (La)TeX markup isn&rsquo;t entirely reliable, however:
+that markup itself may contribute typeset words, and this could be a
+problem.  The <i>wordcount</i> 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.
+<dl>
+<dt><tt><i>detex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/detex.zip">support/detex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/detex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/detex/">browse</a>)
+<dt><tt><i>wordcount</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wordcount.zip">macros/latex/contrib/wordcount</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wordcount.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wordcount/">browse</a>)
+</dl>
+<p/>
+<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html
new file mode 100644
index 00000000000..492b1347ae9
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html
@@ -0,0 +1,43 @@
+<head>
+<title>UK TeX FAQ -- question label writecls</title>
+</head><body>
+<h3>Learning to write LaTeX classes and packages</h3>
+<p/>There&rsquo;s nothing particularly magic about the commands you use when
+writing a package, so you can simply bundle up a set of LaTeX
+<code>\</code><code>(re)newcommand</code> and <code>\</code><code>(re)newenvironment</code> commands, put them in
+a file <i>package.sty</i> and you have a package.
+<p/>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 &lsquo;LaTeX2e for class and package writers&rsquo;
+(<i>clsguide</i>, part of the LaTeX documentation distribution).
+Beyond this, a good knowledge of TeX itself is valuable: thus books
+such as the <a href="FAQ-books.html">TeXbook</a> or 
+<a href="FAQ-ol-books.html">TeX by topic</a> 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
+<i>source2e.tex</i> in the LaTeX distribution, but individual files
+in the distribution may be processed separately with LaTeX, like
+any well-constructed <a href="FAQ-dtx.html"><code>.dtx</code> file</a>.
+<p/>Writing good classes is not easy; it&rsquo;s a good idea to read some
+established ones (<i>classes.dtx</i>, for example, is the documented
+source of the standard classes other than <i>Letter</i>, 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 <code>\</code><code>LoadClass</code> &mdash; an example of this
+technique may be seen in <i>ltxguide.cls</i>
+<p/>An 
+<a href="http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf">annotated version of <i>article</a></i>,
+as it appears in <i>classes.dtx</i>, was published in
+<i>TUGboat</i> 28(1).  The article, by Peter Flynn, which is some help in
+understanding <i>classes.dtx</i>
+<dl>
+<dt><tt><i>classes.dtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/classes.dtx">macros/latex/base/classes.dtx</a>
+<dt><tt><i>clsguide.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc/clsguide.pdf">macros/latex/doc/clsguide.pdf</a>
+<dt><tt><i>ltxguide.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/ltxguide.cls">macros/latex/base/ltxguide.cls</a>
+<dt><tt><i>LaTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse</a>)
+<dt><tt><i>source2e.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/source2e.tex">macros/latex/base/source2e.tex</a>
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html
new file mode 100644
index 00000000000..9acc7076e44
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html
@@ -0,0 +1,39 @@
+<head>
+<title>UK TeX FAQ -- question label wrongpn</title>
+</head><body>
+<h3>Page number is wrong at start of page</h3>
+<p/>This is a long story, whose sources are deep inside the workings of
+TeX itself; it all derives from the TeX&rsquo;s striving to generate
+the best possible output.
+<p/>The page number is conventionally stored in <code>\</code><code>count0</code>; LaTeX
+users see this as the counter <code>page</code>, and may typeset its value
+using <code>\</code><code>thepage</code>.
+<p/>The number (that is to say, <code>\</code><code>count0</code>) 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&rsquo;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 <em>more</em> than a page&rsquo;s
+worth of material to output.  (Ensuring it always has something in
+hand makes some optimisations possible.)  As a result, <code>\</code><code>count0</code>
+(<code>\</code><code>thepage</code>) is almost always wrong in the first paragraph of a
+page (the exception is where the page number has been &ldquo;forcibly&rdquo;
+changed, either by changing its value directly, or by breaking the
+page where TeX wouldn&rsquo;t necessarily have chosen to break).
+<p/>LaTeX provides a safe way of referring to the page number, by using
+label references.  So, rather than writing:
+<blockquote>
+<pre>
+Here is page \thepage{}.
+</pre>
+</blockquote><p>
+you should write:
+<blockquote>
+<pre>
+Here is page \pageref{here}\label{here}.
+</pre>
+</blockquote><p>
+(note: no space between the <code>\</code><code>pageref</code> and the <code>\</code><code>label</code>, since
+that could potentially end up as a page-break space itself, which
+rather defeats the purpose of the exercise!).
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xetex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xetex.html
new file mode 100644
index 00000000000..6c7acf95289
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xetex.html
@@ -0,0 +1,21 @@
+<head>
+<title>UK TeX FAQ -- question label xetex</title>
+</head><body>
+<h3>The XeTeX project</h3>
+<p/>XeTeX (by Jonathan Kew) is a successor to the shareware TeX/GX
+program for Macintoshes. It is a Unicode-based (UTF-8) TeX
+implementation which is able to make use of Mac OS X AAT
+(Apple Advanced Typography) <code>.dfonts</code> and OpenType fonts.  It
+uses Apple&rsquo;s Quartz system (which facilitates the afore-mentioned font
+access) to generate PDF output.  XeTeX supports Unicode
+character sets and bidirectional typesetting, and is widely used by
+people studying linguistics, as well as an increasing range of people
+working in other fields.
+<p/>A Linux and Unix-system version is available in TeX Live 2007; that
+version (of course) relies on OpenType fonts alone.  A version is
+planned for MiKTeX version 2.7 (currently planned for December 2007).
+<p/>The project has a <a href="http://scripts.sil.org/xetex">web site</a> for
+the user who wants more than this simple answer, and you can also sign
+up to a <a href="http://www.tug.org/mailman/listinfo/xetex">mailing list</a>.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html
new file mode 100644
index 00000000000..ff4cbfb70d1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html
@@ -0,0 +1,56 @@
+<head>
+<title>UK TeX FAQ -- question label xspace</title>
+</head><body>
+<h3>Commands gobble following space</h3>
+<p/>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&rsquo;s invocation) in the description of LaTeX syntax.
+Thus the requirement is in effect part of the definition of LaTeX.
+<p/>This FAQ,
+for example, is written with definitions that <em>require</em> one to
+type <code>\</code><code>fred{}</code> 
+                              
+for almost all macro invocations, regardless
+of whether the following space is required: however, this FAQ
+is written by highly dedicated (and, some would say, eccentric)
+people.  Many users find all those braces become very tedious very
+quickly, and would really rather not type them all.
+<p/>An alternative structure, that doesn&rsquo;t violate the design of LaTeX,
+is to say <code>\</code><code>fred</code><code>\</code><code> </code> &mdash; the <code>\</code><code> </code> command is &ldquo;self
+terminating&rdquo; (like <code>\</code><code>\</code>) and you don&rsquo;t need braces after
+<em>it</em>.  Thus one can reduce to one the extra characters one needs
+to type.
+<p/>If even that one character is too many, the package <i>xspace</i>
+defines a command <code>\</code><code>xspace</code> that guesses whether there should have
+been a space after it, and if so introduces that space.  So
+
+&ldquo;<code>fred<code>\</code><code>xspace</code> jim</code>&rdquo; produces &ldquo;fred jim&rdquo;, while
+&ldquo;<code>fred<code>\</code><code>xspace</code>. jim</code>&rdquo; produces &ldquo;fred. jim&rdquo;.  Which
+usage would of course be completely pointless; but you can incorporate
+<code>\</code><code>xspace</code> in your own macros:
+<blockquote>
+<pre>
+\usepackage{xspace}
+...
+\newcommand{\restenergy}{\ensuremath{mc^2}\xspace}
+...
+and we find \restenergy available to us...
+</pre>
+
+</blockquote><p>
+The <code>\</code><code>xspace</code> command must be the last thing in your macro
+definition (as in the example); it&rsquo;s not completely foolproof, but it
+copes with most obvious situations in running text.
+<p/>The <i>xspace</i> package doesn&rsquo;t save you anything if you only use
+a modified macro once or twice within your document.  In any case, be
+careful with usage of <code>\</code><code>xspace</code> &mdash; 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&rsquo;t).  Of course, no command built into LaTeX or into any
+&ldquo;standard&rdquo; class or package will use <code>\</code><code>xspace</code>.
+<dl>
+<dt><tt><i>xspace.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>)
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html
new file mode 100644
index 00000000000..b82b4ae7604
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html
@@ -0,0 +1,47 @@
+<head>
+<title>UK TeX FAQ -- question label y2k</title>
+</head><body>
+<h3>Are TeX and friends Y2K compliant?</h3>
+<p/><dl>
+<dt>Crashing:<dd> None of TeX, Metafont or MetaPost can themselves crash
+  due to any change whatever in the date of any sort.
+<dt>Timestamps:<dd> 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.
+<p/>  Knuth announced in 1998 that implementors could
+  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.
+<dt>The <code>\</code><code>year</code> primitive:<dd> Certification of a TeX
+  implementation (see <a href="FAQ-triptrap.html">trip/trap testing</a>)
+  does not require that <code>\</code><code>year</code> return a meaningful value (which
+  means that TeX can, in principle, be implemented on platforms
+  that don&rsquo;t make the value of the clock available to user programs).
+  The <em>TeXbook</em> (see
+  <a href="FAQ-books.html">TeX-related books</a>) defines <code>\</code><code>year</code> as
+  &ldquo;the current year of our Lord&rdquo;, which is the only correct meaning
+  for <code>\</code><code>year</code> for those implementations which can supply a
+  meaningful value, which is to say nearly all of them.
+<p/>  In short, TeX implementations should provide a value in <code>\</code><code>year</code>
+  giving the 4-digit year Anno Domini, or the value 1776 if the
+  platform does not support a date function.
+<p/>  Note that if the system itself fails to deliver a correct date to
+  TeX, then <code>\</code><code>year</code> 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.
+<dt>Macros:<dd> TeX macros can in principle perform calculations on
+  the basis of the value of <code>\</code><code>year</code>.
+  The <a href="FAQ-latex.html">LaTeX suite</a>
+  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.
+<p/>  Other macros and macro packages should be individually checked.
+<dt>External software:<dd> Software such as DVI translators
+  needs to be individually checked.
+</dl>
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html
new file mode 100644
index 00000000000..a8fd0ecdc70
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html
@@ -0,0 +1,18 @@
+<head>
+<title>UK TeX FAQ -- question label zerochap</title>
+</head><body>
+<h3>Why are my sections numbered 0.1 ...?</h3>
+<p/>This happens when your document is using the standard <i>book</i> or
+<i>report</i> class (or one similar), and you&rsquo;ve got a <code>\</code><code>section</code>
+before your first <code>\</code><code>chapter</code>.
+<p/>What happens is, that the class numbers sections as 
+&ldquo;&lt;<i>chapter no</i>&gt;.&lt;<i>section no</i>&gt;&rdquo;, and until the first
+chapter has appeared, the chapter number is 0.
+<p/>If you&rsquo;re doing this, it&rsquo;s quite likely that the <i>article</i> class
+is for you; try it and see.  Otherwise, give your sections a
+&lsquo;superior&rsquo; chapter, or do away with section numbering by using
+<code>\</code><code>section*</code> instead.  An alternative way of avoiding numbering is
+discussed in 
+&ldquo;<a href="FAQ-secnumdep.html">unnumbered sections in the table of contents</a>&rdquo;.
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap</a>
+</body>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/index.html b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html
new file mode 100644
index 00000000000..81a159e718e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html
@@ -0,0 +1,612 @@
+<h2>Introduction</h2>
+<p/>This is a set of Frequently Asked Questions (FAQ) for
+English-speaking users of TeX.  The questions answered here cover a
+wide range of topics, but the actual typesetting issues are mostly
+covered from the viewpoint of a LaTeX user.
+<p/>You may use the FAQ
+<ul>
+<li> by reading a printed document, 
+<li> by viewing a PDF file, with hyperlinks to assist
+  browsing: copies are available formatted for printing on
+  <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/newfaq.pdf">A4 paper</a> or on 
+  <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/letterfaq.pdf">North American &ldquo;letter&rdquo; paper</a>, or
+<li> by using the FAQ&rsquo;s web interface (base URL:
+  <a href="http://www.tex.ac.uk/faq">http://www.tex.ac.uk/faq</a>); this version provides simple search
+  capabilities, as well as a link to Google for a more sophisticated
+  search restricted to the FAQ itself, or
+<li> via Scott Pakin&rsquo;s <a href="http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf">Visual FAQ</a>.
+</ul>
+<p/>
+<b>Caveat: Acquiring files</b>
+<p/>Most answers in this FAQ provide links for downloading
+software; a large proportion of these links direct you to entire
+directories on the CTAN archives.  Unfortunately, some browsers
+issue a sequence of commands that causes CTAN servers to deny
+the existence of compressed archive files of the directory, that the
+server would be happy to create &ldquo;on the fly&rdquo;.  The FAQ
+therefore offers three possible links for downloading directories
+(that aren&rsquo;t already designated &ldquo;browse only&rdquo;): the links give you
+<code>.zip</code> and <code>.tar.gz</code> archives, and a link for browsing
+the directory.
+<p/>Fortunately, CTAN is switching to statically-generated
+directory archive files; many directories mentioned in this FAQ
+will also exist as <code>.zip</code> files on the archives, and won&rsquo;t fall
+foul of the browser problem.  Of course, if the <code>.zip</code> file
+does not exist, and the browser is playing up, you will need to use
+the &ldquo;browse&rdquo; link.
+<p/>
+<p/><b>Origins</b>
+<p/>The FAQ was originated by the Committee of the UK TeX
+Users&rsquo; Group (UK TUG) as a development of a regular
+posting to the <em>Usenet</em> newsgroup <i>comp.text.tex</i> that
+was maintained for some time by Bobby Bodenheimer.  The first
+UK version was much re-arranged and corrected from the
+original, and little of Bodenheimer&rsquo;s work now remains.
+<p/>The following people (at least &mdash; there are almost certainly others
+whose names weren&rsquo;t correctly recorded) have contributed help or
+advice on the development of the FAQ:
+Donald Arseneau,
+Rosemary Bailey, 
+Barbara Beeton, 
+Karl Berry,
+Giuseppe Bilotta,
+Charles Cameron,
+Damian Cugley,
+Michael Dewey,
+Michael Downes, 
+Jean-Pierre Drucbert, 
+Michael Ernst, 
+Thomas Esser,
+Ulrike Fischer, 
+                
+Anthony Goreham,
+Norman Gray,
+Eitan Gurari, 
+William Hammond, 
+John Harper, 
+John Hammond, 
+Troy Henderson, 
+Hartmut Henkel,
+Stephan Hennig, 
+John Hobby,
+Morten H&oslash;gholm, 
+Berthold Horn, 
+Ian Hutchinson, 
+Werner Icking, 
+William Ingram, 
+Alan Jeffrey, 
+Regnor Jernsletten,
+David Kastrup, 
+Oleg Katsitadze, 
+Isaac Khabaza, 
+Ulrich Klauer, 
+Markus Kohm, 
+David Kraus, 
+Ryszard Kubiak, 
+Simon Law,
+Daniel Luecking,
+Aditya Mahajan, 
+Sanjoy Mahajan,
+Andreas Matthias,
+Brooks Moses, 
+Iain Murray, 
+Vilar Camara Neto, 
+Dick Nickalls, 
+Ted Nieland,
+Hans Nordhaug,
+Pat Rau,
+Heiko Oberdiek,
+Piet van Oostrum,
+Scott Pakin,
+Oren Patashnik,
+Steve Peter, 
+Sebastian Rahtz, 
+Philip Ratcliffe, 
+Chris Rowley, 
+Jos&eacute; Carlos Santos, 
+Walter Schmidt,
+Hans-Peter Schr&ouml;cker,
+Joachim Schrod,
+Maarten Sneep, 
+Axel Sommerfeldt, 
+James Szinger, 
+Ulrik Vieth,
+Mike Vulis,
+Chris Walker, 
+Peter Wilson, 
+Rick Zaccone and
+Reinhard Zierke.
+<p/>
+<p/><h3>The Background</h3><ul>
+<li><a href="FAQ-whatTeX.html">What is TeX?</a>
+<li><a href="FAQ-TeXpronounce.html">How should I pronounce &ldquo;TeX&rdquo;?</a>
+<li><a href="FAQ-MF.html">What is Metafont?</a>
+<li><a href="FAQ-MP.html">What is MetaPost?</a>
+<li><a href="FAQ-triptrap.html">How can I be sure it&rsquo;s really TeX?</a>
+<li><a href="FAQ-y2k.html">Are TeX and friends Y2K compliant?</a>
+<li><a href="FAQ-etex.html">What is e-TeX?</a>
+<li><a href="FAQ-whatpdftex.html">What is PDFTeX?</a>
+<li><a href="FAQ-latex.html">What is LaTeX?</a>
+<li><a href="FAQ-latex2e.html">What is LaTeX2e?</a>
+<li><a href="FAQ-latexpronounce.html">How should I pronounce &ldquo;LaTeX(2e)&rdquo;?</a>
+<li><a href="FAQ-plainvltx.html">Should I use Plain TeX or LaTeX?</a>
+<li><a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX?</a>
+<li><a href="FAQ-context.html">What is ConTeXt?</a>
+<li><a href="FAQ-AMSpkg.html">What are the AMS packages (AMSTeX, <em>etc</em>.)?</a>
+<li><a href="FAQ-eplain.html">What is Eplain?</a>
+<li><a href="FAQ-lollipop.html">What is Lollipop?</a>
+<li><a href="FAQ-texinfo.html">What is Texinfo?</a>
+<li><a href="FAQ-whyfree.html">If TeX is so good, how come it&rsquo;s free?</a>
+<li><a href="FAQ-TeXfuture.html">What is the future of TeX?</a>
+<li><a href="FAQ-readtex.html">Reading (La)TeX files</a>
+<li><a href="FAQ-notWYSIWYG.html">Why is TeX not a WYSIWYG system?</a>
+<li><a href="FAQ-TUGstar.html">TeX User Groups</a>
+</ul><h3>Documentation and Help</h3><ul>
+<li><a href="FAQ-books.html">Books on TeX and its relations</a>
+<li><a href="FAQ-typebooks.html">Books on Type</a>
+<li><a href="FAQ-whereFAQ.html">Where to find FAQs</a>
+<li><a href="FAQ-gethelp.html">How to get help</a>
+<li><a href="FAQ-mailliststar.html">Specialist mailing lists</a>
+<li><a href="FAQ-askquestion.html">How to ask a question</a>
+<li><a href="FAQ-minxampl.html">How to make a &ldquo;minimum example&rdquo;</a>
+<li><a href="FAQ-tutorialstar.html">(La)TeX Tutorials, etc.</a>
+<li><a href="FAQ-man-tex.html">Online introductions: Plain TeX</a>
+<li><a href="FAQ-man-latex.html">Online introductions: LaTeX</a>
+<li><a href="FAQ-tutbitslatex.html">Specialised (La)TeX tutorials</a>
+<li><a href="FAQ-ref-doc.html">Reference documents</a>
+<li><a href="FAQ-doc-wiki.html">WIKI pages for TeX and friends</a>
+<li><a href="FAQ-typo-style.html">Typography tutorials</a>
+<li><a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a>
+<li><a href="FAQ-ol-books.html">Freely available (La)TeX books</a>
+<li><a href="FAQ-pkgdoc.html">Documentation of packages</a>
+<li><a href="FAQ-writecls.html">Learning to write LaTeX classes and packages</a>
+<li><a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a>
+<li><a href="FAQ-BibTeXing.html">BibTeX Documentation</a>
+<li><a href="FAQ-symbols.html">Where can I find the symbol for ...</a>
+<li><a href="FAQ-docpictex.html">The PicTeX manual</a>
+</ul><h3>Bits and pieces of (La)TeX</h3><ul>
+<li><a href="FAQ-dvi.html">What is a DVI file?</a>
+<li><a href="FAQ-driver.html">What is a DVI driver?</a>
+<li><a href="FAQ-pk.html">What are PK files?</a>
+<li><a href="FAQ-tfm.html">What are TFM files?</a>
+<li><a href="FAQ-virtualfonts.html">Virtual fonts</a>
+<li><a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>
+<li><a href="FAQ-hyphen.html">How does hyphenation work in TeX?</a>
+<li><a href="FAQ-clsvpkg.html">What are LaTeX classes and packages?</a>
+<li><a href="FAQ-dtx.html">Documented LaTeX sources (<code>.dtx</code> files)</a>
+<li><a href="FAQ-whatenc.html">What are encodings?</a>
+<li><a href="FAQ-ECfonts.html">What are the EC fonts?</a>
+<li><a href="FAQ-tds.html">What is the TDS?</a>
+<li><a href="FAQ-eps.html">What is &ldquo;Encapsulated PostScript&rdquo; (&ldquo;EPS&rdquo;)</a>
+<li><a href="FAQ-adobetypen.html">Adobe font formats</a>
+<li><a href="FAQ-resolns.html">What are &ldquo;resolutions&rdquo;</a>
+<li><a href="FAQ-fontname.html">What is the &ldquo;Berry naming scheme&rdquo;</a>
+</ul><h3>Acquiring the Software</h3><ul>
+<li><a href="FAQ-archives.html">Repositories of TeX material</a>
+<li><a href="FAQ-tds-zip.html">Prebuilt installation files on the archive</a>
+<li><a href="FAQ-nonfree.html">What&rsquo;s the CTAN <code>nonfree</code> tree?</a>
+<li><a href="FAQ-uploads.html">Contributing a file to the archives</a>
+<li><a href="FAQ-findfiles.html">Finding (La)TeX files</a>
+<li><a href="FAQ-findfont.html">Finding new fonts</a>
+<li><a href="FAQ-CD.html">The TeX collection</a>
+</ul><h3>TeX Systems</h3><ul>
+<li><a href="FAQ-TeXsystems.html">(La)TeX for different machines</a>
+<li><a href="FAQ-editors.html">TeX-friendly editors and shells</a>
+<li><a href="FAQ-commercial.html">Commercial TeX implementations</a>
+</ul><h3>DVI Drivers and Previewers</h3><ul>
+<li><a href="FAQ-dvips.html">DVI to PostScript conversion programs</a>
+<li><a href="FAQ-HPdrivers.html">DVI drivers for HP LaserJet</a>
+<li><a href="FAQ-otherprinters.html">Output to &ldquo;other&rdquo; printers</a>
+<li><a href="FAQ-previewers.html">DVI previewers</a>
+<li><a href="FAQ-dvi-bmp.html">Generating bitmaps from DVI</a>
+</ul><h3>Support Packages for TeX</h3><ul>
+<li><a href="FAQ-fig.html">Fig, a (La)TeX-friendly drawing package</a>
+<li><a href="FAQ-texcad.html">TeXCAD, a drawing package for LaTeX</a>
+<li><a href="FAQ-spell.html">Spelling checkers for work with TeX</a>
+<li><a href="FAQ-wordcount.html">How many words have you written?</a>
+</ul><h3>Literate programming</h3><ul>
+<li><a href="FAQ-lit.html">What is Literate Programming?</a>
+<li><a href="FAQ-webpkgs.html">WEB systems for various languages</a>
+</ul><h3>Format conversions</h3><ul>
+<li><a href="FAQ-toascii.html">Conversion from (La)TeX to plain text</a>
+<li><a href="FAQ-SGML2TeX.html">Conversion from SGML or HTML to TeX</a>
+<li><a href="FAQ-LaTeX2HTML.html">Conversion from (La)TeX to HTML</a>
+<li><a href="FAQ-fmtconv.html">Other conversions to and from (La)TeX</a>
+<li><a href="FAQ-readML.html">Using TeX to read SGML or XML directly</a>
+<li><a href="FAQ-recovertex.html">Retrieving (La)TeX from DVI, etc.</a>
+<li><a href="FAQ-LaTeXtoPlain.html">Translating LaTeX to Plain TeX</a>
+</ul><h3>Installing (La)TeX files</h3><ul>
+<li><a href="FAQ-installthings.html">Installing things on a (La)TeX system</a>
+<li><a href="FAQ-install-find.html">Finding packages to install</a>
+<li><a href="FAQ-install-unpack.html">Unpacking LaTeX packages</a>
+<li><a href="FAQ-install-doc.html">Generating package documentation</a>
+<li><a href="FAQ-inst-wlcf.html">Installing files &ldquo;where (La)TeX can find them&rdquo;</a>
+<li><a href="FAQ-what-TDS.html">Which tree to use</a>
+<li><a href="FAQ-install-where.html">Where to install packages</a>
+<li><a href="FAQ-inst-tidy.html">Tidying up after installation</a>
+<li><a href="FAQ-inst-scut.html">Shortcuts to installing files</a>
+<li><a href="FAQ-inst-miktexstar.html">Installation using MiKTeX package manager</a>
+<li><a href="FAQ-inst-tds-zip.html">Installing using preformatted ZIP files</a>
+<li><a href="FAQ-tempinst.html">&ldquo;Temporary&rdquo; installation of (La)TeX files</a>
+<li><a href="FAQ-privinst.html">&ldquo;Private&rdquo; installations of files</a>
+<li><a href="FAQ-instfont.html">Installing a new font</a>
+<li><a href="FAQ-instmffont.html">Installing a font provided as Metafont source</a>
+<li><a href="FAQ-instprinterfont.html">Installing a PostScript printer built-in font</a>
+<li><a href="FAQ-inst1cm.html">Installing the Bluesky versions of the CM fonts</a>
+<li><a href="FAQ-prept1font.html">Preparing a Type 1 font</a>
+<li><a href="FAQ-instt1font.html">Installing a Type 1 font</a>
+</ul><h3>Fonts</h3><ul>
+</ul><h4>Metafont fonts</h4><ul>
+<li><a href="FAQ-useMF.html">Getting Metafont to do what you want</a>
+<li><a href="FAQ-keepfonts.html">Which font files should be kept</a>
+<li><a href="FAQ-getbitmap.html">Acquiring bitmap fonts</a>
+</ul><h4>Adobe Type 1 (&ldquo;PostScript&rdquo;) fonts</h4><ul>
+<li><a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a>
+<li><a href="FAQ-PSpreview.html">Previewing files using Type 1 fonts</a>
+<li><a href="FAQ-metrics.html">TeX font metric files for PostScript fonts</a>
+<li><a href="FAQ-psfontprob.html">Deploying Type 1 fonts</a>
+<li><a href="FAQ-psfchoice.html">Choice of scalable outline fonts</a>
+<li><a href="FAQ-charshift.html">Weird characters in <i>dvips</i> output</a>
+</ul><h4>Macros for using fonts</h4><ul>
+<li><a href="FAQ-fonts-pln.html">Using non-standard fonts in Plain TeX</a>
+</ul><h4>Particular font families</h4><ul>
+<li><a href="FAQ-concrete.html">Using the &ldquo;Concrete&rdquo; fonts</a>
+<li><a href="FAQ-uselmfonts.html">Using the Latin Modern fonts</a>
+</ul><h3>Hypertext and PDF</h3><ul>
+<li><a href="FAQ-hyper.html">Making hypertext documents from TeX</a>
+<li><a href="FAQ-acrobat.html">Making Acrobat PDF documents from (La)TeX</a>
+<li><a href="FAQ-dvips-pdf.html">Quality of PDF from PostScript</a>
+<li><a href="FAQ-fuzzy-type3.html">The wrong type of fonts in PDF</a>
+<li><a href="FAQ-fuzzy-gs.html">Fuzzy fonts because <i>Ghostscript</i> too old</a>
+<li><a href="FAQ-fuzzy-T1.html">Fonts go fuzzy when you switch to T1</a>
+<li><a href="FAQ-distill-prob.html">Characters missing from PDF output</a>
+<li><a href="FAQ-type1T1.html">Finding &lsquo;8-bit&rsquo; Type 1 fonts</a>
+<li><a href="FAQ-pkfix.html">Replacing Type 3 fonts in PostScript</a>
+<li><a href="FAQ-pdfpagelabels.html"><i>Hyperref</i> and repeated page numbers</a>
+<li><a href="FAQ-srchpdf.html">Searching PDF files</a>
+</ul><h3>Graphics</h3><ul>
+<li><a href="FAQ-impgraph.html">How to import graphics into (La)TeX documents</a>
+<li><a href="FAQ-dvipsgraphics.html">Imported graphics in <i>dvips</i></a>
+<li><a href="FAQ-pdftexgraphics.html">Imported graphics in PDFLaTeX</a>
+<li><a href="FAQ-dvipdfmgraphics.html">Imported graphics in <i>dvipdfm</i></a>
+<li><a href="FAQ-graphicspath.html">Importing graphics from &ldquo;somewhere else&rdquo;</a>
+<li><a href="FAQ-graph-pspdf.html">Portable imported graphics</a>
+<li><a href="FAQ-repeatgrf.html">Repeated graphics in a document</a>
+<li><a href="FAQ-grmaxwidth.html">Limit the width of imported graphics</a>
+<li><a href="FAQ-topgraph.html">Top-aligning imported graphics</a>
+<li><a href="FAQ-mpprologues.html">Displaying MetaPost output in <i>ghostscript</i></a>
+<li><a href="FAQ-drawing.html">Drawing with TeX</a>
+<li><a href="FAQ-drawFeyn.html">Drawing Feynman diagrams in LaTeX</a>
+<li><a href="FAQ-labelfig.html">Labelling graphics</a>
+</ul><h3>Bibliographies and citations</h3><ul>
+</ul><h4>Creating bibliographies</h4><ul>
+<li><a href="FAQ-buildbib.html">Creating a BibTeX bibliography file</a>
+<li><a href="FAQ-custbib.html">Creating a bibliography style</a>
+<li><a href="FAQ-capbibtex.html">Capitalisation in BibTeX</a>
+<li><a href="FAQ-bibaccent.html">Accents in bibliographies</a>
+<li><a href="FAQ-bibstrtl.html">&lsquo;String too long&rsquo; in BibTeX</a>
+<li><a href="FAQ-manyauthor.html">BibTeX doesn&rsquo;t understand lists of names</a>
+<li><a href="FAQ-citeURL.html">URLs in BibTeX bibliographies</a>
+<li><a href="FAQ-bibplain.html">Using BibTeX with Plain TeX</a>
+<li><a href="FAQ-makebib.html">Reconstructing <code>.bib</code> files</a>
+<li><a href="FAQ-bibprefixsort.html">BibTeX sorting and name prefixes</a>
+<li><a href="FAQ-bibtranscinit.html">&lsquo;Multi-letter&rsquo; initials in BibTeX</a>
+</ul><h4>Creating citations</h4><ul>
+<li><a href="FAQ-usebibtex.html">&ldquo;Normal&rdquo; use of BibTeX from LaTeX</a>
+<li><a href="FAQ-whatbst.html">Choosing a bibliography style</a>
+<li><a href="FAQ-chapbib.html">Separate bibliographies per chapter?</a>
+<li><a href="FAQ-multbib.html">Multiple bibliographies?</a>
+<li><a href="FAQ-bibinline.html">Putting bibliography entries in text</a>
+<li><a href="FAQ-citesort.html">Sorting and compressing citations</a>
+<li><a href="FAQ-mcite.html">Multiple citations</a>
+<li><a href="FAQ-backref.html">References from the bibliography to the citation</a>
+<li><a href="FAQ-sortbib.html">Sorting lists of citations</a>
+<li><a href="FAQ-compactbib.html">Reducing spacing in the bibliography</a>
+<li><a href="FAQ-bibtocorder.html">Table of contents rearranges &ldquo;<i>unsrt</i>&rdquo; ordering</a>
+<li><a href="FAQ-i18nbib.html">Non-english bibliographies</a>
+<li><a href="FAQ-formbiblabel.html">Format of numbers in the bibliography</a>
+</ul><h4>Manipulating whole bibliographies</h4><ul>
+<li><a href="FAQ-nocitestar.html">Listing all your BibTeX entries</a>
+<li><a href="FAQ-htmlbib.html">Making HTML of your Bibliography</a>
+</ul><h3>Adjusting the typesetting</h3><ul>
+</ul><h4>Alternative document classes</h4><ul>
+<li><a href="FAQ-replstdcls.html">Replacing the standard classes</a>
+<li><a href="FAQ-slidecls.html">Producing slides</a>
+<li><a href="FAQ-poster.html">Creating posters with LaTeX</a>
+<li><a href="FAQ-thesis.html">Formatting a thesis in LaTeX</a>
+<li><a href="FAQ-journalpaper.html">Setting papers for journals</a>
+<li><a href="FAQ-multidoc.html">A &lsquo;report&rsquo; from lots of &lsquo;article&rsquo;s</a>
+<li><a href="FAQ-cv.html"><em>Curriculum Vitae</em> (R&eacute;sum&eacute;)</a>
+<li><a href="FAQ-letterclass.html">Letters and the like</a>
+<li><a href="FAQ-extsizes.html">Other &ldquo;document font&rdquo; sizes?</a>
+</ul><h4>Document structure</h4><ul>
+<li><a href="FAQ-titlsty.html">The style of document titles</a>
+<li><a href="FAQ-secthead.html">The style of section headings</a>
+<li><a href="FAQ-appendix.html">Appendixes</a>
+<li><a href="FAQ-secindent.html">Indent after section headings</a>
+<li><a href="FAQ-subsubsub.html">How to create a <code>\</code><code>subsubsubsection</code></a>
+<li><a href="FAQ-captsty.html">The style of captions</a>
+<li><a href="FAQ-fancyhdr.html">Alternative head- and footlines in LaTeX</a>
+<li><a href="FAQ-widefigs.html">Wide figures in two-column documents</a>
+<li><a href="FAQ-onecolabs.html">1-column abstract in 2-column document</a>
+<li><a href="FAQ-reallyblank.html">Really blank pages between chapters</a>
+<li><a href="FAQ-balance.html">Balancing columns at the end of a document</a>
+<li><a href="FAQ-runheadtoobig.html">My section title is too wide for the page header</a>
+<li><a href="FAQ-nofm.html">Page numbering &ldquo;&lt;<i>n</i>&gt; of &lt;<i>m</i>&gt;&rdquo;</a>
+<li><a href="FAQ-pagebychap.html">Page numbering by chapter</a>
+</ul><h4>Page layout</h4><ul>
+<li><a href="FAQ-papersize.html">The size of printed output</a>
+<li><a href="FAQ-acroantics.html">Adobe <i>Reader</i> messing with print size</a>
+<li><a href="FAQ-papergeom.html">Getting the right paper geometry from (La)TeX</a>
+<li><a href="FAQ-changemargin.html">Changing the margins in LaTeX</a>
+<li><a href="FAQ-marginpkgs.html">Packages to set up page designs</a>
+<li><a href="FAQ-marginmanual.html">How to set up page layout &ldquo;by hand&rdquo;</a>
+<li><a href="FAQ-chngmargonfly.html">Changing margins &ldquo;on the fly&rdquo;</a>
+<li><a href="FAQ-nopageno.html">How to get rid of page numbers</a>
+<li><a href="FAQ-psatempty.html"><code>\pagestyle{empty}</code> on first page in LaTeX</a>
+<li><a href="FAQ-crop.html">How to create crop marks</a>
+<li><a href="FAQ-watermark.html">&lsquo;Watermarks&rsquo; on every page</a>
+<li><a href="FAQ-landscape.html">Typesetting things in landscape orientation</a>
+<li><a href="FAQ-abspos.html">Putting things at fixed positions on the page</a>
+<li><a href="FAQ-nopagebrk.html">Preventing page breaks between lines</a>
+<li><a href="FAQ-parallel.html">Parallel setting of text</a>
+<li><a href="FAQ-epigraph.html">Typesetting epigraphs</a>
+<li><a href="FAQ-outszwrng.html">(La)TeX PDF output prints at wrong size</a>
+</ul><h4>Spacing of characters and lines</h4><ul>
+<li><a href="FAQ-linespace.html">Double-spaced documents in LaTeX</a>
+<li><a href="FAQ-letterspace.html">Changing the space between letters</a>
+<li><a href="FAQ-ragright.html">Setting text ragged right</a>
+<li><a href="FAQ-flushboth.html">Cancelling <code>\</code><code>ragged</code> commands</a>
+</ul><h4>Typesetting specialities</h4><ul>
+<li><a href="FAQ-verbfile.html">Including a file verbatim in LaTeX</a>
+<li><a href="FAQ-linenos.html">Including line numbers in typeset output</a>
+<li><a href="FAQ-codelist.html">Code listings in LaTeX</a>
+<li><a href="FAQ-algorithms.html">Typesetting pseudocode in LaTeX</a>
+<li><a href="FAQ-makeindex.html">Generating an index in (La)TeX</a>
+<li><a href="FAQ-setURL.html">Typesetting URLs</a>
+<li><a href="FAQ-music.html">Typesetting music in TeX</a>
+<li><a href="FAQ-parskip.html">Zero paragraph indent</a>
+<li><a href="FAQ-dropping.html">Big letters at the start of a paragraph</a>
+<li><a href="FAQ-dec_comma.html">The comma as a decimal separator</a>
+<li><a href="FAQ-breakbox.html">Breaking boxes of text</a>
+<li><a href="FAQ-overstrike.html">Overstriking characters</a>
+<li><a href="FAQ-upquot.html">Realistic quotes for verbatim listings</a>
+<li><a href="FAQ-time.html">Printing the time</a>
+<li><a href="FAQ-the-commands.html">Redefining counters&rsquo; <code>\</code><code>the-</code>commands</a>
+</ul><h4>Tables of contents and indexes</h4><ul>
+<li><a href="FAQ-tocloft.html">The format of the Table of Contents, etc.</a>
+<li><a href="FAQ-secnumdep.html">Unnumbered sections in the Table of Contents</a>
+<li><a href="FAQ-tocbibind.html">Bibliography, index, etc., in TOC</a>
+<li><a href="FAQ-minitoc.html">Table of contents, etc., per chapter</a>
+<li><a href="FAQ-multind.html">Multiple indexes</a>
+</ul><h4>Labels and references</h4><ul>
+<li><a href="FAQ-nameref.html">Referring to things by their name</a>
+<li><a href="FAQ-extref.html">Referring to labels in other documents</a>
+</ul><h3>How do I do...?</h3><ul>
+</ul><h4>Mathematics</h4><ul>
+<li><a href="FAQ-proof.html">Proof environment</a>
+<li><a href="FAQ-theoremfmt.html">Theorem bodies printed in a roman font</a>
+<li><a href="FAQ-newfunction.html">Defining a new log-like function in LaTeX</a>
+<li><a href="FAQ-braket.html">Set specifications and Dirac brackets</a>
+<li><a href="FAQ-cancellation.html">Cancelling terms in maths expressions</a>
+<li><a href="FAQ-mathsize.html">Adjusting maths font sizes</a>
+<li><a href="FAQ-mathlips.html">Ellipses</a>
+<li><a href="FAQ-limits.html">Sub- and superscript positioning for operators</a>
+<li><a href="FAQ-mathstext.html">Text inside maths</a>
+<li><a href="FAQ-reuseq.html">Re-using an equation</a>
+<li><a href="FAQ-brkinline.html">Line-breaking in in-line maths</a>
+<li><a href="FAQ-mathonlyref.html">Numbers for referenced equations only</a>
+</ul><h4>Lists</h4><ul>
+<li><a href="FAQ-enumerate.html">Fancy enumeration lists</a>
+<li><a href="FAQ-complist.html">How to adjust list spacing</a>
+<li><a href="FAQ-interruptlist.html">Interrupting enumerated lists</a>
+</ul><h4>Tables, figures and diagrams</h4><ul>
+<li><a href="FAQ-destable.html">The design of tables</a>
+<li><a href="FAQ-fixwidtab.html">Fixed-width tables</a>
+<li><a href="FAQ-varwidcol.html">Variable-width columns in tables</a>
+<li><a href="FAQ-struttab.html">Spacing lines in tables</a>
+<li><a href="FAQ-longtab.html">Tables longer than a single page</a>
+<li><a href="FAQ-tabcellalign.html">How to alter the alignment of tabular cells</a>
+<li><a href="FAQ-rulethk.html">The thickness of rules in LaTeX tables</a>
+<li><a href="FAQ-textflow.html">Flowing text around figures in LaTeX</a>
+<li><a href="FAQ-slashbox.html">Diagonal separation in corner cells of tables</a>
+<li><a href="FAQ-wholerow.html">How to change a whole row of a table</a>
+<li><a href="FAQ-multirow.html">Merging cells in a column of a table</a>
+</ul><h4>Floating tables, figures, etc.</h4><ul>
+<li><a href="FAQ-floatpages.html">Floats on their own on float pages</a>
+<li><a href="FAQ-vertspacefloat.html">Extra vertical space in floats</a>
+<li><a href="FAQ-2colfloat.html">Placing two-column floats at bottom of page</a>
+<li><a href="FAQ-mcfloat.html">Floats in multicolumn setting</a>
+<li><a href="FAQ-dpfloat.html">Facing floats on 2-page spread</a>
+<li><a href="FAQ-vertposfp.html">Vertical layout of float pages</a>
+<li><a href="FAQ-figurehere.html">Figure (or table) <em>exactly</em> where I want it</a>
+</ul><h4>Footnotes</h4><ul>
+<li><a href="FAQ-footintab.html">Footnotes in tables</a>
+<li><a href="FAQ-ftnsect.html">Footnotes in LaTeX section headings</a>
+<li><a href="FAQ-ftncapt.html">Footnotes in captions</a>
+<li><a href="FAQ-repfootnote.html">Footnotes whose texts are identical</a>
+<li><a href="FAQ-multfoot.html">More than one sequence of footnotes</a>
+<li><a href="FAQ-footnpp.html">Footnotes numbered &ldquo;per page&rdquo;</a>
+<li><a href="FAQ-run-fn-nos.html">Not resetting footnote numbers per chapter</a>
+</ul><h4>Document management</h4><ul>
+<li><a href="FAQ-filename.html">What&rsquo;s the name of this file</a>
+<li><a href="FAQ-filesused.html">All the files used by this document</a>
+<li><a href="FAQ-changebars.html">Marking changed parts of your document</a>
+<li><a href="FAQ-conditional.html">Conditional compilation and &ldquo;comments&rdquo;</a>
+<li><a href="FAQ-docotherdir.html">Bits of document from other directories</a>
+<li><a href="FAQ-RCS.html">Version control using RCS, CVS or the like</a>
+<li><a href="FAQ-make.html">Makefiles for LaTeX documents</a>
+<li><a href="FAQ-howmanypp.html">How many pages are there in my document?</a>
+<li><a href="FAQ-inclplain.html">Including Plain TeX files in LaTeX</a>
+</ul><h4>Hyphenation</h4><ul>
+<li><a href="FAQ-nohyph.html">My words aren&rsquo;t being hyphenated</a>
+<li><a href="FAQ-weirdhyphen.html">Weird hyphenation of words</a>
+<li><a href="FAQ-oddhyphen.html">(Merely) peculiar hyphenation</a>
+<li><a href="FAQ-hyphenaccents.html">Accented words aren&rsquo;t hyphenated</a>
+<li><a href="FAQ-newlang.html">Using a new language with Babel</a>
+<li><a href="FAQ-hyphoff.html">Stopping all hyphenation</a>
+<li><a href="FAQ-wdnohyph.html">Preventing hyphenation of a particular word</a>
+<li><a href="FAQ-hyphexcept.html">Hyphenation exceptions</a>
+</ul><h4>Odds and ends</h4><ul>
+<li><a href="FAQ-logos.html">Typesetting all those TeX-related logos</a>
+<li><a href="FAQ-bold-extras.html">How to do bold-tt or bold-sc</a>
+<li><a href="FAQ-varwidth.html">Automatic sizing of <code>minipage</code></a>
+</ul><h3>Symbols, etc.</h3><ul>
+<li><a href="FAQ-numbersets.html">Symbols for the number sets</a>
+<li><a href="FAQ-scriptfonts.html">Better script fonts for maths</a>
+<li><a href="FAQ-boldgreek.html">Setting bold Greek letters in LaTeX</a>
+<li><a href="FAQ-prinvalint.html">The Principal Value Integral symbol</a>
+<li><a href="FAQ-underscore.html">How to use the underscore character</a>
+<li><a href="FAQ-atsign.html">How to type an &lsquo;@&rsquo; sign?</a>
+<li><a href="FAQ-euro.html">Typesetting the Euro sign</a>
+<li><a href="FAQ-tradesyms.html">How to get copyright, trademark, etc.</a>
+</ul><h3>Macro programming</h3><ul>
+</ul><h4>&ldquo;Generic&rdquo; macros and techniques</h4><ul>
+<li><a href="FAQ-findwidth.html">Finding the width of a letter, word, or phrase</a>
+<li><a href="FAQ-patch.html">Patching existing commands</a>
+<li><a href="FAQ-compjobnam.html">Comparing the &ldquo;job name&rdquo;</a>
+<li><a href="FAQ-isitanum.html">Is the argument a number?</a>
+<li><a href="FAQ-hash.html">Defining macros within macros</a>
+<li><a href="FAQ-spinmacro.html">Spaces in macros</a>
+<li><a href="FAQ-moren9.html">How to break the 9-argument limit</a>
+<li><a href="FAQ-activechars.html">Defining characters as macros</a>
+<li><a href="FAQ-actinarg.html">Active characters in command arguments</a>
+<li><a href="FAQ-csname.html">Defining a macro from an argument</a>
+<li><a href="FAQ-cvtlatex.html">Transcribing LaTeX command definitions</a>
+<li><a href="FAQ-empty.html">Detecting that something is empty</a>
+<li><a href="FAQ-ifpdf.html">Am I using PDFTeX?</a>
+<li><a href="FAQ-subverttoks.html">Subverting a token register</a>
+<li><a href="FAQ-isdef.html">Is this command defined?</a>
+</ul><h4>LaTeX macro tools and techniques</h4><ul>
+<li><a href="FAQ-plninltxstar.html">Using Plain or primitive commands in LaTeX</a>
+<li><a href="FAQ-atsigns.html"><code>\</code><code>@</code> and <code>@</code> in macro names</a>
+<li><a href="FAQ-protect.html">What&rsquo;s the reason for &lsquo;protection&rsquo;?</a>
+<li><a href="FAQ-edef.html"><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></a>
+<li><a href="FAQ-ltxcmds.html">The definitions of LaTeX commands</a>
+<li><a href="FAQ-oarglikesect.html">Optional arguments like <code>\</code><code>section</code></a>
+<li><a href="FAQ-twooptarg.html">More than one optional argument</a>
+<li><a href="FAQ-cmdstar.html">Commands defined with * options</a>
+<li><a href="FAQ-ltxabbrv.html">LaTeX internal &ldquo;abbreviations&rdquo;, etc.</a>
+<li><a href="FAQ-ltxhash.html">Defining LaTeX commands within other commands</a>
+</ul><h4>LaTeX macro programming</h4><ul>
+<li><a href="FAQ-fixnam.html">How to change LaTeX&rsquo;s &ldquo;fixed names&rdquo;</a>
+<li><a href="FAQ-latexwords.html">Changing the words <i>babel</i> uses</a>
+<li><a href="FAQ-running-nos.html">Running equation, figure and table numbering</a>
+<li><a href="FAQ-labelctr.html">Making labels from a counter</a>
+<li><a href="FAQ-oddpage.html">Finding if you&rsquo;re on an odd or an even page</a>
+<li><a href="FAQ-labelformat.html">How to change the format of labels</a>
+<li><a href="FAQ-seccntfmt.html">Adjusting the presentation of section numbers</a>
+<li><a href="FAQ-spaftend.html">There&rsquo;s a space added after my environment</a>
+<li><a href="FAQ-labundef.html">Finding if a label is undefined</a>
+<li><a href="FAQ-addtoreset.html">Master and slave counters</a>
+<li><a href="FAQ-fontsize.html">Fonts at arbitrary sizes</a>
+<li><a href="FAQ-latexqual.html">The quality of your LaTeX</a>
+</ul><h3>Things are Going Wrong...</h3><ul>
+</ul><h4>Getting things to fit</h4><ul>
+<li><a href="FAQ-enlarge.html">Enlarging TeX</a>
+<li><a href="FAQ-usepictex.html">Why can&rsquo;t I load PicTeX?</a>
+</ul><h4>Making things stay where you want them</h4><ul>
+<li><a href="FAQ-floats.html">Moving tables and figures in LaTeX</a>
+<li><a href="FAQ-underline.html">Underlined text won&rsquo;t break</a>
+<li><a href="FAQ-widows.html">Controlling widows and orphans</a>
+</ul><h4>Things have &ldquo;gone away&rdquo;</h4><ul>
+<li><a href="FAQ-oldfontnames.html">Old LaTeX font references such as <code>\</code><code>tenrm</code></a>
+<li><a href="FAQ-misssymb.html">Missing symbol commands</a>
+<li><a href="FAQ-msxy.html">Where are the <code>msx</code> and <code>msy</code> fonts?</a>
+<li><a href="FAQ-amfonts.html">Where are the <code>am</code> fonts?</a>
+</ul><h3>Why does it <em>do</em> that?</h3><ul>
+</ul><h4>Common errors</h4><ul>
+<li><a href="FAQ-crossref.html">LaTeX gets cross-references wrong</a>
+<li><a href="FAQ-newlineargs.html">Start of line goes awry</a>
+<li><a href="FAQ-verbwithin.html">Why doesn&rsquo;t verbatim work within ...?</a>
+<li><a href="FAQ-noline.html">No line here to end</a>
+<li><a href="FAQ-2colfltorder.html">Two-column float numbers out of order</a>
+<li><a href="FAQ-tabacc.html">Accents misbehave in <code>tabbing</code></a>
+<li><a href="FAQ-alreadydef.html">Package reports &ldquo;command already defined&rdquo;</a>
+<li><a href="FAQ-zerochap.html">Why are my sections numbered 0.1 ...?</a>
+<li><a href="FAQ-breaklinks.html">Link text doesn&rsquo;t break at end line</a>
+<li><a href="FAQ-wrongpn.html">Page number is wrong at start of page</a>
+<li><a href="FAQ-matchbrak.html">My brackets don&rsquo;t match</a>
+</ul><h4>Common misunderstandings</h4><ul>
+<li><a href="FAQ-include.html">What&rsquo;s going on in my <code>\</code><code>include</code> commands?</a>
+<li><a href="FAQ-paraparam.html">Why does it ignore paragraph parameters?</a>
+<li><a href="FAQ-casechange.html">Case-changing oddities</a>
+<li><a href="FAQ-splitfoot.html">Why does LaTeX split footnotes across pages?</a>
+<li><a href="FAQ-marginparside.html">Getting <code>\</code><code>marginpar</code> on the right side</a>
+<li><a href="FAQ-misschar.html">Where have my characters gone?</a>
+<li><a href="FAQ-rerun.html">&ldquo;Rerun&rdquo; messages won&rsquo;t go away</a>
+<li><a href="FAQ-xspace.html">Commands gobble following space</a>
+<li><a href="FAQ-overfull.html">(La)TeX makes overfull lines</a>
+<li><a href="FAQ-exscale.html">Maths symbols don&rsquo;t scale up</a>
+<li><a href="FAQ-linespread.html">Why doesn&rsquo;t <code>\</code><code>linespread</code> work?</a>
+<li><a href="FAQ-baselinepar.html">Only one <code>\</code><code>baselineskip</code> per paragraph</a>
+<li><a href="FAQ-tocloftwrong.html">Numbers too large in table of contents, etc.</a>
+<li><a href="FAQ-gutter.html">Why is the inside margin so narrow?</a>
+</ul><h4>Why shouldn&rsquo;t I?</h4><ul>
+<li><a href="FAQ-t1enc.html">Why use <i>fontenc</i> rather than <i>t1enc</i>?</a>
+<li><a href="FAQ-why-inp-font.html">Why bother with <i>inputenc</i> and <i>fontenc</i>?</a>
+<li><a href="FAQ-eqnarray.html">Why not use <code>eqnarray</code>?</a>
+<li><a href="FAQ-dolldoll.html">Why use <code>\</code><code>[</code> ...<code>\</code><code>]</code> in place of <code>$$</code> ...<code>$$</code>?</a>
+<li><a href="FAQ-2letterfontcmd.html">What&rsquo;s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a>
+<li><a href="FAQ-newfontstar.html">What&rsquo;s wrong with <code>\</code><code>newfont</code>?</a>
+</ul><h3>The joy of TeX errors</h3><ul>
+<li><a href="FAQ-erroradvice.html">How to approach errors</a>
+<li><a href="FAQ-errstruct.html">The structure of TeX error messages</a>
+<li><a href="FAQ-extrabrace.html">An extra &lsquo;<code>}</code>&rsquo;??</a>
+<li><a href="FAQ-semanticnest.html">Capacity exceeded [semantic nest ...]</a>
+<li><a href="FAQ-noroom.html">No room for a new &lsquo;<em>thing</em>&rsquo;</a>
+<li><a href="FAQ-epsf.html"><code>epsf</code> gives up after a bit</a>
+<li><a href="FAQ-badhyph.html">Improper <code>\</code><code>hyphenation</code> will be flushed</a>
+<li><a href="FAQ-tmupfl.html">&ldquo;Too many unprocessed floats&rdquo;</a>
+<li><a href="FAQ-atvert.html"><code>\</code><code>spacefactor</code> complaints</a>
+<li><a href="FAQ-endingroup.html"><code>\</code><code>end</code> occurred inside a group</a>
+<li><a href="FAQ-nonum.html">&ldquo;Missing number, treated as zero&rdquo;</a>
+<li><a href="FAQ-typend.html">&ldquo;Please type a command or say <code>\</code><code>end</code>&rdquo;</a>
+<li><a href="FAQ-unkgrfextn.html">&ldquo;Unknown graphics extension&rdquo;</a>
+<li><a href="FAQ-nodollar.html">&ldquo;Missing <code>$</code> inserted&rdquo;</a>
+<li><a href="FAQ-fontunavail.html">Warning: &ldquo;Font shape ... not available&rdquo;</a>
+<li><a href="FAQ-buffovl.html">Unable to read an entire line</a>
+<li><a href="FAQ-formatstymy.html">&ldquo;Fatal format file error; I&rsquo;m stymied&rdquo;</a>
+<li><a href="FAQ-nonpdfsp.html">Non-PDF special ignored!</a>
+<li><a href="FAQ-8000.html">Mismatched mode ljfour and resolution 8000</a>
+<li><a href="FAQ-toodeep.html">&ldquo;Too deeply nested&rdquo;</a>
+<li><a href="FAQ-inputlev.html">Capacity exceeded &mdash; input levels</a>
+<li><a href="FAQ-hyperdupdest.html">PDFTeX destination ... ignored</a>
+<li><a href="FAQ-altabcr.html">Alignment tab changed to <code>\</code><code>cr</code></a>
+<li><a href="FAQ-divzero.html">Graphics division by zero</a>
+<li><a href="FAQ-missbegdoc.html">Missing <code>\</code><code>begin</code><code>{document}</code></a>
+<li><a href="FAQ-normalszmiss.html"><code>\</code><code>normalsize</code> not defined</a>
+<li><a href="FAQ-manymathalph.html">Too many math alphabets</a>
+<li><a href="FAQ-ouparmd.html">Not in outer par mode</a>
+<li><a href="FAQ-errmissitem.html">Perhaps a missing <code>\</code><code>item</code>?</a>
+<li><a href="FAQ-errparnum.html">Illegal parameter number in definition</a>
+<li><a href="FAQ-fllost.html">Float(s) lost</a>
+<li><a href="FAQ-optionclash.html">Option clash for package</a>
+<li><a href="FAQ-checksum.html">Checksum mismatch in font</a>
+<li><a href="FAQ-entercompmode.html">Entering compatibility mode</a>
+</ul><h3>Current TeX-related projects</h3><ul>
+<li><a href="FAQ-LaTeX3.html">The LaTeX project</a>
+<li><a href="FAQ-mathml.html">Future WWW technologies and (La)TeX</a>
+<li><a href="FAQ-textrace.html">Making outline fonts from Metafont</a>
+<li><a href="FAQ-WYGexpts.html">The TeX document preparation environment</a>
+<li><a href="FAQ-ant.html">The ANT typesetting system</a>
+<li><a href="FAQ-extex.html">The ExTeX project</a>
+<li><a href="FAQ-omegaleph.html">Omega and Aleph</a>
+<li><a href="FAQ-luatex.html">PDFTeX becomes LuaTeX</a>
+<li><a href="FAQ-xetex.html">The XeTeX project</a>
+<li><a href="FAQ-biblatex.html">Replacing the BibTeX&ndash;LaTeX mechanism</a>
+</ul><h3>You&rsquo;re still stuck?</h3><ul>
+<li><a href="FAQ-noans.html">You don&rsquo;t understand the answer</a>
+<li><a href="FAQ-newans.html">Submitting new material for the FAQ</a>
+<li><a href="FAQ-latexbug.html">Reporting a LaTeX bug</a>
+<li><a href="FAQ-bug.html">What to do if you find a bug</a>
+</ul>
+
+<hr><address>
+
+   Comments, suggestions, or error reports? -- see
+   "<a href="FAQ-noans.html">Improving the FAQ</a>" or
+   "<a href="FAQ-newans.html">Extending the FAQ</a>". 
+<p>
+   This is FAQ version 3.18, last modified on 2008-06-21.
+</address>
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf
new file mode 100644
index 00000000000..d4823f2634a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.tex b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.tex
new file mode 100644
index 00000000000..12d0da7b8a3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/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 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{faqbody}
+\else
+  \begin{multicols}{2}
+  \input{faqbody}
+  \end{multicols}
+\fi
+
+\typeout{*** That makes \thequestion\space questions ***}
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/locations.mk b/Master/texmf-dist/doc/generic/FAQ-en/locations.mk
new file mode 100644
index 00000000000..82d923fe8ac
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/locations.mk
@@ -0,0 +1,8 @@
+# the locations of files that are targets of the Makefile rules
+
+WEB	= "web site main source directory"
+WEB_BETA = "web site beta source directory"
+CGI_BIN	= "web site CGI directory"
+HOME_DIR = "where sources live"
+CTAN_ROOT = "position of CTAN root on archive machine"
+FTPDIR = "directory for off-archive FTP distribution"
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/logotst.tex b/Master/texmf-dist/doc/generic/FAQ-en/logotst.tex
new file mode 100644
index 00000000000..5ac611a8623
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/logotst.tex
@@ -0,0 +1,84 @@
+\documentclass{ukart}
+\setcounter{errorcontextlines}{999}
+\makeatletter
+%
+% Twee, in its wisdom, has a redefined LaTeX logo
+%
+%\DeclareRobustCommand{\LaTeX}{L\kern-.36em
+%        {\setbox0\hbox{T}%
+%         \vbox to\ht0{\hbox{$\m@th$%
+%                            \csname S@\f@size\endcsname
+%                            \fontsize\sf@size\z@
+%                            \math@fontsfalse\selectfont
+%                            A}%
+%                      \vss}%
+%        }%
+%        \kern-.15em
+%        \TeX}
+%
+% which 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 italic 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}
+%
+% of course, we could modify this not to do all those awful sums when
+% the font isn't slanted, but (perhaps) this isn't today's
+% problem\dots
+%
+% Now for a few demonstrations of the effect achieved
+\begin{document}
+Demo with the modification of the current \LaTeX{} logo
+
+\begin{center}
+\LARGE\begin{tabular}{l|ccc}
+&\normalsize\sf roman&\normalsize\sf italic&\normalsize\sf slanted\\
+\hline
+\normalsize\sf old & \LaTeX & \textit{\LaTeX} & \textsl{\LaTeX} \\
+\normalsize\sf new & \latex & \textit{\latex} & \textsl{\latex} \\
+\end{tabular}
+\end{center}
+%
+% Here's something that does it with the `original' (Lamport's)
+% definition.
+%
+% (In fact this is a bit of a cheat, since the last 2.09 had
+% \reset@font\rm at the start, and of course, it got defined as a
+% protected command in the LaTeX 2.09 fashion, but what the hell, eh?)
+\def\LaTeX{L\kern-.36em\raise.3ex\hbox{\textsc{a}}\kern-.15em\TeX}%
+\def\latex{\@tempdima.3ex
+           \@tempdima\strip@pt\fontdimen1\font\@tempdima
+           \advance\@tempdima-0.36em\relax
+           L\kern\@tempdima\raise.3ex\hbox{\textsc{a}}\kern-.15em\TeX}%
+%
+% and a demo of that
+\par\noindent Demo with the modification of the original \LaTeX{} logo
+
+\begin{center}
+\LARGE\begin{tabular}{l|ccc}
+&\normalsize\sf roman&\normalsize\sf italic&\normalsize\sf slanted\\
+\hline
+\normalsize\sf old & \LaTeX & \textit{\LaTeX} & \textsl{\LaTeX} \\
+\normalsize\sf new & \latex & \textit{\latex} & \textsl{\latex} \\
+\end{tabular}
+\end{center}
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/markup-syntax b/Master/texmf-dist/doc/generic/FAQ-en/markup-syntax
new file mode 100644
index 00000000000..087f32fd945
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/markup-syntax
@@ -0,0 +1,229 @@
+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 change the shortvrb character from `|'; it interacts with
+   other definitions.
+
+4. Avoid shortvrb syntax, anyway ... most common uses are now covered
+   by specific macros; if a need arises, more such macros can be
+   developed, rather than using shortvrb.
+
+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 booklabel
+
+  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
+
+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)
+
+\nothtml{text}
+
+  Text not to appear in the HTML version
+
+\htmlonly{text}
+
+  Text only to appear (after processing) 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.
+
+\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{ackage name}(no .sty)
+\Class{lass 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
+23 Oct 94
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/mflogo.sty b/Master/texmf-dist/doc/generic/FAQ-en/mflogo.sty
new file mode 100644
index 00000000000..f3f8ca02f40
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/mflogo.sty
@@ -0,0 +1,31 @@
+%% 
+%% This is file `mflogo.sty',
+%% generated with the docstrip utility.
+%% 
+%% The original source files were:
+%% 
+%% mflogo.dtx  (with options: `package')
+%% 
+%% Copyright (C) 1994,95 Ulrik Vieth 
+%% All rights reserved. 
+%% 
+%% This file is part of the mflogo package. 
+%% ---------------------------------------- 
+%% 
+%% This is a generated file. Permission is granted to customize the 
+%% declarations in this file to serve the needs of your installation. 
+%% However, no permission is granted to distribute a modified version 
+%% of this file under its original name. 
+%% 
+\NeedsTeXFormat{LaTeX2e}[1994/06/01]
+\ProvidesPackage{mflogo}
+  [1995/12/04 v1.5c LaTeX package for METAFONT and MetaPost logos]
+\DeclareRobustCommand\logofamily{%
+  \not@math@alphabet\logofamily\relax
+  \fontencoding{U}\fontfamily{logo}\selectfont}
+\DeclareTextFontCommand{\textlogo}{\logofamily}
+\def\MF{\textlogo{META}\@dischyph\textlogo{FONT}\@}
+\def\MP{\textlogo{META}\@dischyph\textlogo{POST}\@}
+\endinput
+%% 
+%% End of file `mflogo.sty'.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf
new file mode 100644
index 00000000000..8704013cb91
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex
new file mode 100644
index 00000000000..a7e20206566
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex
@@ -0,0 +1,64 @@
+% 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 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{faqbody}
+\else
+  \begin{multicols}{2}
+  \input{faqbody}
+  \end{multicols}
+\fi
+
+\typeout{*** That makes \thequestion\space questions ***}
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers
new file mode 100644
index 00000000000..2781140734d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers
@@ -0,0 +1,5 @@
+This file contains (will contain) a list of people working on the new
+FAQ, and of the questions they're working on.
+
+Mail rf10@cam.ac.uk to book a question, thus avoiding wasted effort.
+
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/README b/Master/texmf-dist/doc/generic/components-of-TeX/README
new file mode 100644
index 00000000000..a8f5653b4da
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/README
@@ -0,0 +1,31 @@
+This is the report
+
+        The Components of TeX
+
+It describes the components and files users of TeX get in contact
+with.
+
+
+To LaTeX the article five files are needed:
+
+        etexkomp.tex    the real article
+        figkomp.tex     a graphics with the relation of the components
+        figtotal.tex    a graphics with all components and file types
+        texrep.sty      the main style option, made for this article
+        names.sty          is used by texrep.sty, definition of logos
+
+Please note that texrep.sty redefines ^. If you incorporate this
+report in an other document you should either typeset it in a group
+or you should have a look at texrep.sty and change the macros/the
+article.
+
+Happy hours.
+
+	Joachim
+
+---------------------------------------------------------------------------
+Detig Schrod TeXsys              	Email: xitijsch@ddathd21.bitnet
+Joachim Schrod
+Alexanderstr. 10
+D-6100 Darmstadt
+FR Germany
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/etexkomp.tex b/Master/texmf-dist/doc/generic/components-of-TeX/etexkomp.tex
new file mode 100644
index 00000000000..2406ac98a87
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/etexkomp.tex
@@ -0,0 +1,478 @@
+% etexkomp.tex                                  25 Mar 91
+%------------------------------------------------------------
+% (c) 1990 by J.Schrod (TeXsys).
+
+%
+% originally published in Die TeXnische Komoedie (DANTE e.V.) as:
+%     Die Komponenten von TeX
+%
+% ILaTeX with standard styles and
+%	style for reports about TeX
+
+% Changes made by Adrian Clark for publication in `Baskerville'
+% and editorial remarks by Malcolm Clark
+% incorporated.
+
+
+\documentstyle[texrep]{article}
+
+
+% terms `output' and `driver' in english, used in picture `figtotal'.
+\def\OutputInFigtotal{output}
+\def\DriverInFigtotal{\DVI{} driver}
+
+
+
+\begin{document}
+
+
+\title{The Components of \TeX{}}
+\author{
+   Joachim Schrod\\
+   Detig$\,\cdot\,$Schrod \TeX{}sys
+   }
+  \date{March 1991}
+
+\titlenote{
+   \copyright{} Copyright 1990, 1991 by Joachim Schrod.
+   All rights reserved.
+   Republication and Distribution is allowed under conditions analog
+   to the GNU General Public License.
+   Previous revisions of this paper appeared in ``Die \TeX{}nische
+   Kom\"odie'' and in ``Baskerville.''
+   }
+\titlenote{
+   {\sl Actual address\/}:
+   Joachim Schrod, Detig$\,\cdot\,$Schrod \TeX{}sys,
+   Kranichweg 1, D-6074 R\"odermark, FR~Germany,
+   Email: {\tt xitijsch@ddathd21.bitnet}
+   }
+
+\maketitle
+
+
+
+ \begin{abstract}
+ \TeX{} needs a great amount of supplementary components (files and
+programs) of which the meaning and interaction often is unknown. This
+paper explains the components of the kernel system \TeX{} that are
+visible for the \TeX{} user and their relations.
+ \end{abstract}
+
+
+
+
+\section{About this Report}
+
+\TeX{} is a typesetting system which offers authors easy usage of
+powerful typesetting features to produce printed matter which is the
+state of the art of computer typesetting. This is, however, not done by the
+\TeX{} program alone: A significant number of supplementary
+programs and files together form the complete typesetting and
+authoring system. Along with the programs that belong to \TeX{}
+directly, there exist two other major programs which were built by {\sc
+Donald Knuth} in connection with \TeX{} and must be included in an
+explanation of the full system: \MF{}, for the generation of fonts,
+and \WEB{}, a documentation and developing `language' for programming.
+\TeX{} and \MF{} are written in \WEB{}.
+
+This text describes this `kernel' \TeX{} from a user's viewpoint: at
+the end you should have an overview of the ingredients of the \TeX{}
+system, and about the files and support programs that are essential
+for you as a user. This will not, however, be an introduction to the
+capabilities of \TeX{} or how you may run \TeX{} on your computer.
+
+I will use marginal notes to identify the places where terms are
+explained for the first time. Abbrevations for file types -- usually
+identified by common suffixes or extensions -- are set in a monospace
+type (``{\tt typewriter\/}'') and those abbrevations are put into the
+margin, too. Please note that these abbreviations are sometimes not
+identical with the file extensions (see also
+Table~\ref{tab:filetypes}).
+
+This report is the start of a series that describes the subsystems
+mentioned above and their respective components. In that series each
+report will focus on one subsystem in a special point of view; it
+should not result in gigantic descriptions which tell everything (and
+then nothing). In my opinion the following reports will be of
+interest:
+ %
+ \begin{itemize}
+
+\item the structure of a standard installation of \TeX{}
+\item \DVI{} drivers and fonts
+\item possibilities of graphics inclusion in \TeX{} documents
+\item the components of \MF{}
+\item the structure of a standard installation of \MF{}
+\item \WEB{} systems --- the concept of Literate Programming
+\item other (though not yet planned) themes of interest are perhaps
+\begin{itemize}
+\item differences between \TeX{} and DTP systems
+\item the way how \TeX{} works (there exists some good books on this topic!)
+\item the limits of \TeX{}
+\item \TeX{} as a programming language
+\end{itemize}
+
+ \end{itemize}
+ %
+ The reports will be published in this sequence.
+
+
+
+
+\section{What is \TeX{}?}
+
+ \TeX{} is a typesetting system with great power for the typesetting
+of formulae. Its basic principle is that structures in the document
+are marked and transformed into typeset output. Providing such
+information about the structure of a document is known as {\it
+^|markup|}. If the marks describe the look of the document, it is
+called {\it ^|optical markup|}, while, if document structures are
+marked, it is called {\it ^|logical markup|}. \TeX{}  provides both
+forms of  markup, \ie{}, exact control of the layout of parts of the
+document and their positioning as well as the markup of the structure
+of formulae or document components. The logical markup is mapped to
+the optical one by \TeX{} so that layout may serve for the
+identification of structures by the reader.%
+   \footnote{
+      Layout -- and book design in general -- do not represent useless
+beauty. A good book design must first support the understanding of
+the content to produce readable text. So it is {\it
+\ae{}sthetic\/} in its best sense, since it connects form and contents
+and builts a new quality.
+      }
+
+ The kernel of the \TeX{} typesetting system is the formatting program
+\TeX82^^|typesetting machine \TeX82|, which is often simply called
+\TeX{}. This usage shall be adopted here whenever the difference
+between the complete system and the formatter is unimportant or
+obvious. \TeX82 is a big monolithic program which is published in the
+book {\it \TeX{}: The Program\/} by {\sc Donald Knuth}. Its features
+may be separated into two levels:
+ %
+ \begin{enumerate}
+
+\item \TeX82 formats text, \ie{}, it breaks it into paragraphs
+(including automatic hyphenation) and produces page breaks.
+
+\item It provides the programming language \TeX{} which incorporates a macro
+mechanism. This allows new commands to be built to support markup
+at a higher level. {\sc Donald Knuth} presents an example in the
+\TeX{}book: \Plain{}. A collection of macros which supports a special
+task and has (hopefully) a common philosophy of usage is called a
+{\it ^|macro package|}.
+
+\end{enumerate}
+ %
+ High level features for optical markup, as represented by \Plain{},
+allow one to build additional levels leading to full logical markup.
+At the moment, two macro packages for logical markup are widespread:
+\AmSTeX{} and \LaTeX{}. Both systems are built on top of \Plain{} to
+greater or lesser extents and the user can use the optical markup of
+\Plain{} in addition to logical markup if desired. This results in
+the effect that the author can use a mixture of structural
+information and explicit layout information -- a situation with a
+high potency of features that nevertheless can (and does) lead to a
+lot of typographic nonsense!
+
+As \TeX82 was built only for typesetting texts and to allow the
+realization of new markup structures, many features are lacking which are
+required by authors. To provide features like the production of
+an index or a bibliography or the inclusion of graphics, additional
+programs^^|supplementary programs| have been written, which use 
+information from a \TeX82 formatting run, process them, and provide
+them for the next \TeX82 run. Two supplementary programs are
+in widespread use and available for many computer/operating system
+combinations: \BibTeX{}, for the production of a bibliography from a
+reference collection, and \MakeIndex{}, for the production of an index.
+
+A special case of the processing of information provided by a \TeX{}
+run is the production of a table of contents or the usage of cross
+references in a text. For this only informations about page numbers,
+section numbers, etc., are needed. These are
+provided by \TeX82 and can be processed by \TeX82 itself, so \TeX82 is
+used as its own post processor in this situation.
+
+We have now seen that the \TeX{} typesetting system  is
+a collection of tools that consists of the typesetting `engine' \TeX82,
+macro packages (maybe several that are based on others) and
+supplementary programs, used together with these macro packages.
+This relation is illustrated by Figure~\ref{fig:components}.
+
+\begin{figure}
+\begin{center}
+\input figkomp
+\caption{The Components of \TeX{}}
+\label{fig:components}
+\end{center}
+\end{figure}
+
+
+
+\section{Formatting}
+
+The formatting process of \TeX{} needs information about the
+dimensions of characters used for the paragraph breaking. A set
+of characters is grouped in {\it ^|font|s}. (But this is a
+simplification as the notion ``font'' should be used for the
+realization of a type in a fixed size for a specific output device.)
+The dimensions of the characters of a font are called {\it font
+metrics}.
+
+
+The format in which the font metrics are used by \TeX{} was
+defined by {\sc Donald Knuth} and is called  \ftype{tfm} format
+(``{\sl \TeX{} font metrics\/}''). In this format, every character is
+descibed as a {\it box\/} with a height, a depth, and a width.
+\TeX{} only needs these measurements, it is not interested in the shape
+of the character. It is even possible that the character may extend
+outside 
+the box, which may result in an overlap with other characters.
+The character measures are specified in a device independent
+dimension because \TeX{} processes its breaking algorithm
+independent of any output device.
+
+During paragraph breaking, \TeX{} hyphenates automatically, which
+can be done in an almost language-independent way. For the adaption to
+different languages, {\it ^|hyphenation patterns|\/} are needed to
+parametrize the hyphenation algorithm.
+
+The result of a \TeX{} formatting run is a \ftype{DVI} document, in which
+the type and position on the page are specified for each character to
+be output. The resolution that is used is so small that
+every possible output device will have a coarser raster, so that the
+positioning is effectively device independent. The \DVI{} document
+specifies only types, not the fonts themselves, so that the name \DVI{}%
+   \footnote{
+      This name is a problem because ``DVI'' is a trademark of 
+      Intel Corp.\ now, but the name \DVI{} for \TeX{} output files 
+      pre-dates this.
+      }
+ (``{\sl device independent\/}'') is accurate. To make the result of
+the formatting run available, the \DVI{} file must be output by a
+so-called ^|\DVI{} driver| on the desired output device.
+
+If problems occur during the formatting, error messages or warnings
+are output on the terminal. {\it Every\/} message that appears on the
+terminal will also be written into a protocol file named \ftype{log}
+file. In this \LOG{} file additional information may be placed that
+would have been too verbose for the output to the terminal. If this
+is the case, \TeX{} will tell the user so at the end of the
+formatting run. The messages of \TeX{} are not built in the program,
+they are stored in a (string) \ftype{pool} file. These messages must
+be read in at the beginning of a run.
+
+
+
+\section{Macro Packages}
+The basic macro package is ^|\Plain|, developed by {\sc Donald Knuth}
+together with \TeX82. It parametrizes the \TeX82 typesetting machine
+so that it can typeset English texts with the Computer Modern type
+family. Additionally, \Plain{} provides optical markup features.
+\Plain{} is available as one source file, {\tt plain.tex}.
+
+All other macro packages known to the author are based on \Plain{},
+\ie{}, they contain the source file {\tt plain.tex\/} either
+originally or with modifications of less important parts. Next to
+\Plain{}, the most important (free) available macro packages are
+^|\AmSTeX{}| by {\sc Michael Spivak} and ^|\LaTeX{}| by {\sc Leslie
+Lamport}. Other free macro packages are often of only local
+importance (\eg{} Blue\TeX{}, TEXT1, or \TeX{}sis) or are used in
+very special environments only (\eg{} {\tt texinfo\/} in the
+GNU~project or {\tt webmac\/} for \WEB{}). Important commercial macro
+packages are ^|Macro\TeX{}| by {\sc Amy Hendrickson} and
+^|\LAMSTeX{}|, also written by {\sc Michael Spivak}.
+
+These macro packages usually consist of a kernel that
+provides additional markup primitives. With such primitives,
+{\it document styles\/}^^|styles| can be built which realize logical
+markups by a corresponding layout. This layout can often be varied by
+{\it sub-styles\/} or {\it style options\/} which may also provide
+additional markups.
+
+The macro packages produce {\it ^|supplementary files|\/} which contain
+information about the page breaks or the document markup. This
+information may be used by support programs -- \eg{}, the
+specification of a reference from a bibliography database or the
+specification of an index entry with corresponding page number for the
+construction of an index. A special case is the information about
+cross references and headings for the building of a table of contents,
+as this information can be gathered and reused by \TeX{} directly.
+
+^|\SliTeX{}| is a special component of \LaTeX{} for the preparation
+of slides with overlays. In TUGBoat volume~10, no.~3 (1989)
+^|\LAMSTeX{}| was announced, which will provide the functionality of
+\LaTeX{} within \AmSTeX{}. ^|Macro\TeX{}| is a toolbox of macro
+``modules'' which may be used to realize new markups but, as it
+became available only short time ago, it is not yet widespread.
+
+For the usage of these (and other) macro packages, one must check
+whether they need ^|additional fonts| which do not belong to the Computer
+Modern type family. For \LaTeX{}, \eg{}, fonts with additional symbols
+and with invisible characters (for the slide overlays) are needed,
+while \AmSTeX{} needs several additional font sets with mathematical and
+Cyrillic characters.
+
+
+
+\section{Support Programs}
+
+Only two support programs will be discussed here: ^|\BibTeX{}| by
+{\sc Oren Patashnik} for the preparation of bibliographies and
+^|\MakeIndex{}| by {\sc Pehong Chen} and {\sc Michael Harrison} for
+the preparation of a sorted index. For both tasks exist other,
+funcionally equivalent, support programs. But the abovementioned are
+available on many operating systems, and have an ``official'' state
+as they are {\sc Leslie Lamport} encourages their usage with
+\LaTeX{} in his documentation, and the TUG supports them for general use.
+
+There is no totally portable mechanism for the inclusion of general
+graphics in \TeX{} documents, so that there are no machine independent
+support programs available.
+
+\BibTeX{} is used to handle references collected in \ftype{bib}
+files. \TeX{} produces supplementary files which contain information
+about the required references, and \BibTeX{} generates from them a
+sorted bibliography in a \ftype{bbl} file which may be subsequently
+used by \TeX{}. The kind of sorting and the type of ^|cite keys| are
+defined by {\it ^|bibliography styles|\/},  specified in \ftype{bst}
+files. The messages of a \BibTeX{} run are written to a \ftype{blg}
+logfile.
+
+\MakeIndex{} reads an \ftype{idx} support file that contains the index
+entries and the according page numbers, sorts these items, unifies
+them and writes them as \TeX{} input in an \ftype{ind} file. The
+formatting style may be specified by an {\it ^|index style|}. The
+messages of a \MakeIndex{} run are written to a \ftype{ilg} file.
+
+
+
+\section{Performance Improvements}
+
+Much of the work that \TeX82 has to do is the same for every
+document:
+%
+ \begin{enumerate}
+
+\item \label{enum:hyphen}
+ All text has to be broken into lines. Text pieces in the same
+language are hyphenated with the same hyphenation patterns.
+
+\item \label{enum:markup}
+ The basic markups of the corresponding macro packages must be
+available.
+
+\item The required font metrics are much alike for many documents, as the
+font set used usually doesn't differ that much.
+
+\end{enumerate} 
+% 
+ To improve \TeX{}'s performance, hyphenation, markup, and font
+metrics descriptions are converted from an external, for
+(\ref{enum:hyphen}) and~(\ref{enum:markup}) textual, representation
+into an internal representation which can easily be used by \TeX82.
+It is sensible to do this transformation only once, not for every
+document. The internal representation is stored in a \ftype{fmt} file.
+The storing is done with the \TeX{} command {\tt \bs{}dump}, so that
+\FMT{} files often are called ``{\it dumped formats}.'' A \FMT{} file
+can be read at the beginning of a \TeX82 run and is thus available
+for the processing of the actual text.
+
+As the creation of a \FMT{} file is done infrequently -- usually for
+the update of a macro package -- the formatting of texts can be done
+with a reduced version of the \TeX82 program that doesn't contain the
+storage and the program parts for the transformation of the
+hyphenation patterns and for the dumping. The complete version of
+\TeX82 is needed in an initialization phase only and therefore called
+^|\INITeX{}|. Additional improvements of the performance can be
+reached  by the usage of ^|production version|s of \TeX82 from which
+parts for statistical analysis and for debugging are stripped. 
+
+\TeX{} versions that have no dumped formats preloaded, have the
+ability to load a dumped format (\ie{} a \FMT{} file), and have no
+ability to dump a \FMT{} file (\ie{}, they are not \INITeX{}) are
+often called ^|Vir\TeX{}|, which stands for {\it virgin \TeX{}}.
+
+
+
+\section{Connections Between File Types and Components}
+
+In the above sections, the components of the \TeX{} authoring system 
+were described, and the files that are read or written by these
+components mentioned. The connections between them all is 
+demonstrated graphically in Figure~\ref{fig:total}. In this graphic,
+file types are represented by rectangles, and programs by ovals. The
+arrows mean ``is read by'' or ``is produced by.'' The abbreviations
+of the file types are explained in Table~\ref{tab:filetypes}, which
+also lists the file identifications (suffixes or extensions) that
+these files usually have (but note that  other file identifications
+are also in use).
+
+\begin{figure} 
+\begin{center} 
+\input figtotal 
+\caption{The Connection of Components and File Types} 
+\label{fig:total} 
+\end{center}
+\end{figure}
+
+\begin{table}
+\begin{center}
+
+\noindent
+\vbox\bgroup			% halign, LaTeX is too inflexible!!
+%
+\tabskip=1em
+\catcode`\,=\active % Roman Komma, also in typewriter text!
+\def,{{\rm \char`\,\relax \space}\ignorespaces}
+
+\let\par=\cr \obeylines%
+\halign{\tt \hfil #\unskip\hfil & #\unskip\hfil & \tt #\unskip\hfil
+%
+\sc File Type & \hfil \sc Explanation & \sc File Identification
+              &                       & \sc (suffix, extension, etc.)
+\noalign{\vskip 3pt}%
+%
+TEX & Text input & tex, ltx
+DVI & \TeX82 output, formatted text & dvi
+LOG & \TeX82 log file & log, lis, list
+HYP & Hyphenation patterns & tex
+TFM & Font metrics & tfm
+POOL & String pool & pool, poo, pol
+FMT & Format file & fmt
+MAC & \TeX{} macro file & tex, doc
+STY & \TeX{} style file & sty, tex, st, doc
+AUX & Support files & aux, toc, lot, lof,\unskip
+    &               & glo, tmp, tex
+BIB & Reference collections & bib
+BBL & References or bibliographies & bbl
+BLG & \BibTeX{} log file & blg
+BST & \BibTeX{} style file & bst
+IDX & Unsorted index & idx
+IND & Sorted index & ind
+IST & Index markup specification
+ILG & \MakeIndex{} log file & ilg
+}%
+%
+\egroup
+
+\caption{File Types}
+\label{tab:filetypes}
+\end{center}
+\end{table}
+
+
+
+\subsubsection*{Acknowledgements}
+
+I would like to thank {\sc Christine Detig} who was so kind to
+provide the English translation. {\sc Nelson Beebe} suggested
+performing the  translation. {\sc Klaus Guntermann} made valuable
+comments on the first (German) version.
+{\sc Nico Poppelier} contributed a new version of figure
+\ref{fig:total}, better than my original one.
+
+
+
+\end{document}
+
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/figkomp.tex b/Master/texmf-dist/doc/generic/components-of-TeX/figkomp.tex
new file mode 100644
index 00000000000..f0d0140d5db
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/figkomp.tex
@@ -0,0 +1,50 @@
+% figkomp.tex					01 Oct 90
+%------------------------------------------------------------
+% (c) 1990 by J.Schrod (TeXsys).
+
+%
+% picture of the components of TeX (logical connection)
+%
+
+% NOTE: BibTeX was made available for Plain TeX recently. So the
+% graphic will be changed soon...
+
+
+\begin{picture}(23,14)(3,0)
+
+
+% TeX82
+\put( 3, 0){ \rule{\w}{3\k} }
+\put( 3, 3){ \rule{24\k}{\w} }
+\put(27, 0){ \rule{\w}{3\k} }
+\put( 3, 0){ \makebox(24,3){\TeX82} }
+
+% Plain TeX
+\put( 4, 3){ \framebox(22,3){\Plain} }
+
+% AmS-TeX
+\put( 5, 6){ \rule{\w}{5\k} }
+\put( 5,11){ \rule{5\k}{\w} }
+\put(10, 6){ \rule{\w}{5\k} }
+\put( 5, 6){ \makebox(5,3){\AmSTeX} }
+
+% LAmS-TeX
+\put( 6, 9){ \dashbox{.5}(4,2){\LAMSTeX} }
+
+% LaTeX
+\put(11, 6){ \framebox(8,5){\LaTeX} }
+
+% SliTeX
+\put(11,11){ \framebox(4,3){\SliTeX} }
+
+% BibTeX
+\put(15,11){ \framebox(4,3){\BibTeX} }
+
+% MakeIndex
+\put(20, 6){ \framebox(5,8){\MakeIndex} }
+
+\end{picture}
+
+
+
+\endinput
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/figtotal.tex b/Master/texmf-dist/doc/generic/components-of-TeX/figtotal.tex
new file mode 100644
index 00000000000..1cd47b1e9da
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/figtotal.tex
@@ -0,0 +1,174 @@
+% figtotal.tex					25 Mar 91
+%------------------------------------------------------------
+% (c) 1991 by J.Schrod (TeXsys).
+
+%
+% Picture of the components and used file types of TeX (data flow)
+%   (thanks to Nico Poppelier who contributed this better structured version)
+%
+% LaTeX picture
+
+
+% check if \OutputInFigtotal and \DriverInFigtotal is defined
+
+\ifx \OutputInFigtotal\undefined
+   \errhelp{It should be defined as the term `output' in the used language}
+   \errmessage{You must define \string\OutputInFigtotal}
+   \def\OutputInFigtotal{output}
+\fi
+\ifx \DriverInFigtotal\undefined
+   \errhelp{It should be defined as the term `driver' in the used language}
+   \errmessage{You must define \string\DriverInFigtotal}
+   \def\DriverInFigtotal{\DVI{} driver}
+\fi
+
+
+
+\def\file#1{\framebox(3,2){\tt \uppercase{#1}}}
+\def\prog(#1)#2{%
+   \oval(#1,2)%
+   \makebox(0,0){#2}%
+   }
+
+
+% X and Y variables
+
+\newcount\X \newcount\Y		% needed for \Program
+
+% macros for objects
+
+\def\File(#1,#2)#3{%
+  \put(#1,#2){\framebox(20,10){\tt\uppercase{#3}}}}
+\def\CopyFile(#1,#2)#3{%
+  \put(#1,#2){\dashbox{2}(20,10){#3}}}
+\def\Program(#1,#2)#3{%
+  \X=#1 \Y=#2 \advance\X by 15 \advance\Y by 5
+  \put(\X,\Y){\oval(30,10)}%
+  \put(#1,#2){\makebox(30,10){#3}}}
+\def\Device(#1,#2)#3{%
+  \put(#1,#2){\line(1,2){5}} \put(#1,#2){\line(1,0){25}}
+  \X=#1 \Y=#2 \advance\X by 30 \advance\Y by 10
+  \put(\the\X,\the\Y){\line(-1,-2){5}} \put(\the\X,\the\Y){\line(-1,0){25}}
+  \put(#1,#2){\makebox(30,10){#3}}}
+
+
+% don't ask me why it's 0.7mm, that's from Nico!  -js
+
+\unitlength=0.7mm
+
+
+\begin{picture}(260,160)(80,0)
+
+% this code provides a dotted grid that makes modification easier
+
+%\multiput( 70,  0)(10,0){20}{%
+%   \vbox to 160\unitlength{%
+%      \leaders
+%         \vbox to 2.5\unitlength{%
+%	    \vfill
+%	    \hbox{\fivrm .}%
+%	    \vfill
+%	    }%
+%	 \vfill
+%      }%
+%   }
+%\multiput( 70,  0)(0,10){17}{%
+%   \hbox to 190\unitlength{%
+%      \leaders
+%         \hbox to 2.5\unitlength{%
+%	    \hfill
+%	    \hbox{\fivrm .}%
+%	    \hfill
+%	    }%
+%	 \hfill
+%      }%
+%   }
+
+
+%
+% IniTeX block
+%
+    \File( 75,145){tfm} \File(105,145){hyp} \File(135,145){mac} 
+    \File(165,145){pool} 
+\multiput( 85,145)(30,0){4}{\line(0,-1){5}}
+     \put( 85,140){\line(1,0){90}}
+     \put(115,140){\vector(0,-1){5}}
+ \Program(100,125){\INITeX}
+     \put(115,125){\line(0,-1){5}}
+     \put(100,120){\line(1,0){30}}
+\multiput(100,120)(30,0){2}{\vector(0,-1){5}}
+    \File( 90,105){log}
+    \File(120,105){fmt} \File(150,105){tex}
+    \File(180,105){sty} \File(210,105){mac} \File(240,105){tfm}
+
+%
+% TeX block
+%
+\multiput(130,105)(30,0){5}{\line(0,-1){5}}
+     \put(130,100){\line(1,0){120}}
+     \put(175,100){\vector(0,-1){5}}
+ \Program(160, 85){\TeX82}
+     \put(175, 85){\line(0,-1){5}}
+     \put(130, 80){\line(1,0){90}}
+\multiput(130, 80)(30,0){4}{\vector(0,-1){5}}
+    \File(120, 65){dvi} \File(150, 65){log}
+    \File(180, 65){idx} \File(210, 65){aux}
+% loop back to TeX
+     \put(230, 70){\line(1,0){10}}
+     \put(240, 70){\vector(0,1){10}}
+     \put(240, 80){\line(0,1){10}}
+
+%
+% BibTeX block
+%
+    \File(195, 45){bib} \File(225, 45){bst}
+\multiput(205, 45)(30,0){2}{\line(0,-1){5}}
+     \put(205, 40){\line(1,0){30}}
+     \put(220, 65){\vector(0,-1){30}}
+ \Program(205, 25){\BibTeX}
+     \put(220, 25){\line(0,-1){5}}
+     \put(205, 20){\line(1,0){30}}
+\multiput(205, 20)(30,0){2}{\vector(0,-1){5}}
+    \File(195,  5){blg} \File(225,  5){bbl}
+% loop back to TeX
+     \put(245, 10){\line(1,0){10}}
+     \put(255, 10){\vector(0,1){10}}
+     \put(255, 20){\line(0,1){70}}
+
+%
+% MakeIndex block
+%
+    \File(150, 45){ist}
+     \put(190, 65){\line(0,-1){20}}
+\multiput(160, 45)(30,0){2}{\line(0,-1){5}}
+     \put(160, 40){\line(1,0){30}}
+     \put(175, 40){\vector(0,-1){5}}
+ \Program(160, 25){\MakeIndex}
+     \put(175, 25){\line(0,-1){5}}
+     \put(145, 20){\line(1,0){30}}
+\multiput(145, 20)(30,0){2}{\vector(0,-1){5}}
+    \File(135,  5){ilg} \File(165,  5){ind}
+% loop back to TeX
+     \put(175,  5){\line(0,-1){5}}
+     \put(175,  0){\line(1,0){85}}
+     \put(260,  0){\vector(0,1){10}}
+     \put(260, 10){\line(0,1){80}}
+     \put(260, 90){\vector(-1,0){70}}
+
+%
+% device driver block
+%
+    \File( 90, 65){fnt}
+\multiput(100, 65)(30,0){2}{\line(0,-1){25}}
+     \put(100, 40){\line(1,0){30}}
+     \put(115, 40){\vector(0,-1){5}}
+ \Program(100, 25){\DriverInFigtotal}
+     \put(115, 25){\vector(0,-1){10}}
+  \Device(100,  5){\OutputInFigtotal}
+
+
+\end{picture}
+
+
+\endinput
+
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/names.sty b/Master/texmf-dist/doc/generic/components-of-TeX/names.sty
new file mode 100644
index 00000000000..6ca02c31286
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/names.sty
@@ -0,0 +1,91 @@
+% names.sty				01 Oct 90
+%------------------------------------------------------------
+
+%
+% abbrevations/logos in LaTeX and Format!, usable for base size 10pt
+%
+% should be compared with tugboat.com and should be documented...
+% should be enhanced for LaTeX (to Format! standards) [NFSS ?!]
+%
+% all logos only in Roman
+% Logos:
+%       \TeX
+%       \INITeX
+%       \Plain           Plain TeX
+%       \LaTeX
+%       \BibTeX
+%       \SliTeX
+%       \MakeIndex       (italic)
+%       \AmSTeX          AmS-TeX
+%       \LAMSTeX	 LAmS-TeX
+%       \MF              METAFONT
+%       \INIMF
+%       \WEB
+%       \CWEB
+%       \TIE
+%       \stTeX
+%       \stMF
+% file types (all monospaced):
+%       \LOG
+%       \DVI
+%       \FMT
+%       \TFM
+%       \GF
+%       \PK
+%       \PXL
+
+
+\font\tenlogo=logo10
+\let\logo=\tenlogo
+\ifx \mc\undefined  \let\mc=\small  \fi  % for LaTeX, `medium caps'
+
+
+% FIXME: should the space factor be set to 1000 afterwards? 
+% is it a global value? otherwise it would be a faulty design within TeX...
+\def\TeX{{\rm T\kern-.1667em\lower.5ex\hbox{E}\kern-.125emX}}
+\def\INITeX{{\rm INI\TeX}}
+
+\def\Plain{{\rm Plain~\TeX}}
+
+% LaTeX definition with original TeX logo! 
+% Does not conform to the definition of L. Lamport, but is more consistent...
+\def\LaTeX{{\rm L\kern-.36em\raise.3ex\hbox{\sc a}\kern-.15em\TeX}}
+\def\BibTeX{{\rm B\kern-.05em{\sc i\kern-.025em b}\kern-.08em\TeX}}
+\def\SliTeX{{\rm S\kern-.06em{\sc l\kern-.035em i}\kern-.06em\TeX}}
+\def\MakeIndex{{\it MakeIndex\/}}
+
+\def\AmSTeX{%
+   $\cal A\kern-.1667em\lower.5ex\hbox{$\cal M$}\kern-.125em S$%
+   -\TeX
+   }
+\def\LAMSTeX{%
+   L\raise.42ex\hbox{$\scriptstyle\kern-.3em\cal A$}\kern-.2em
+   \lower.376ex\hbox{$\cal M$}\kern-.125em $\cal S$%
+   -\TeX
+   }
+
+
+\def\MF{{\logo META}\-{\logo FONT\/}}
+\def\INIMF{{\mc INI}{\logo MF}}
+
+
+\def\WEB{{\tt WEB\/}}
+\def\CWEB{{\mc CWEB}}
+\def\TIE{{\tt TIE\/}}
+
+
+\def\stTeX{{\sc st\rm\kern-0.13em\TeX}} % our stTeX (TeXsys)
+\def\stMF{{\sc st}{\logo MF}}           % our stMF
+
+
+\def\LOG{{\tt LOG\/}}
+\def\DVI{{\tt DVI\/}}
+\def\FMT{{\tt FMT\/}}
+\def\TFM{{\tt TFM\/}}
+
+\def\GF{{\tt GF\/}}
+\def\PK{{\tt PK\/}}
+\def\PXL{{\tt PXL\/}}
+
+
+\endinput
diff --git a/Master/texmf-dist/doc/generic/components-of-TeX/texrep.sty b/Master/texmf-dist/doc/generic/components-of-TeX/texrep.sty
new file mode 100644
index 00000000000..b5096c4e537
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/components-of-TeX/texrep.sty
@@ -0,0 +1,97 @@
+% texrep.sty					14 Nov 90
+%------------------------------------------------------------
+% (c) 1990 by J.Schrod (TeXsys).
+
+%
+% markups for my articles about TeX
+%
+% ILaTeX style option
+%     testet with: article
+%
+% ATTENTION:
+%     After loading ^ can not be used for exponents any more, use \sp !
+
+
+\input names.sty        % Logos
+
+
+% abbrevations
+
+\chardef\bs=`\\                % backslash
+
+\def\dh{d.\,h.\spacefactor\@m} % kerning!  (Spatium)
+\def\zb{z.\,B.}
+\def\ZB{Z.\,B.}
+
+\def\eg{e.\,g.\spacefactor\@m}
+\def\ie{i.\,e.\spacefactor\@m}
+
+
+%
+% consistent formatting
+%
+
+% first time a file type is mentioned it is marked with \ftype.
+\def\ftype#1{{\tt \marginpar{\uppercase{#1}}\uppercase{#1}\/}}
+
+% split ligatures with \| (if not in math mode)
+%	is already defined in local.tex but this is often not used!
+\def\allowhyphens{\penalty\@M \hskip\z@skip}
+\def\|{%                
+   \relax
+   \ifmmode  \Vert
+   \else  \allowhyphens\-\allowhyphens
+   \fi
+   }
+
+
+%
+% pictures
+%
+
+\unitlength=5mm           % may be changed for DINA5
+\let\w=\@wholewidth       % width of a rule
+\let\k=\unitlength        % a box (in German: Kasten) on my drawing-paper...
+
+
+%
+% title notes are footnotes on the title page without any marker
+%
+
+\def\titlenote#1{%
+   \begingroup
+      \def\@makefntext##1{\noindent ##1}%
+      \footnotetext{#1}%
+   \endgroup
+   }
+
+
+% marginal notes, for easier input
+%		(idea taken from manmac.tex)
+%
+% usage:
+%       ^|rem1|  for remark rem1, which is also printed (loud).
+%       ^^|rem2| for remark rem2, which is not printed (silent).
+% implementation:
+%	look at next char; if ^, then do not print it.
+%	with this char determin macro to expand
+%	   macro is defined accordingly
+%	marginal note is created by \marginpar.
+% attention:
+%       ^ can not be used for creating an exponent any more (but \sp!)
+
+\catcode`\^=\active
+\def^{\futurelet\next \check@silent}
+\def\check@silent{%
+   \ifx \next^%
+      \let\next\silent@margin
+   \else  \let\next\print@margin
+   \fi
+   \next
+   }
+
+\def\silent@margin^|#1|{\marginpar{\rm #1}}
+\def\print@margin|#1|{#1\marginpar{\rm #1}}
+
+
+\endinput
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/README b/Master/texmf-dist/doc/generic/free-math-font-survey/README
new file mode 100644
index 00000000000..dbcce23a0a4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/README
@@ -0,0 +1,16 @@
+Documentation: Free_Math_Font_Survey

+Author: Stephen Hartke, lastname at gmail dot com

+2006-05-06

+

+This document is a survey of the free math fonts that are available

+for use with TeX and LaTeX.  Examples are provided for each font,

+links to where to obtain the font, and the commands for loading the

+associated LaTeX package.

+

+"Free" here means fonts that are free to use (both commercially and

+non-commercially) and free to distribute, but not necessarily free to

+modify. I also am biased towards listing fonts that have outline

+versions in PostScript Type 1 format suitable for embedding in

+Postscript PS or Adobe Acrobat PDF files.

+

+The survey is available both as a PDF file and as a webpage.

diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/antpolt.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/antpolt.png
new file mode 100644
index 00000000000..515eeb8ff37
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/antpolt.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/anttor.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/anttor.png
new file mode 100644
index 00000000000..7814bcf3232
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/anttor.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/arev.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/arev.png
new file mode 100644
index 00000000000..40142db384c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/arev.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/belleek.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/belleek.png
new file mode 100644
index 00000000000..ec0f880a12b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/belleek.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/chartermd.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/chartermd.png
new file mode 100644
index 00000000000..9dc91aa1669
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/chartermd.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/cm.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/cm.png
new file mode 100644
index 00000000000..6a70b2ad27d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/cm.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/cmbright.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/cmbright.png
new file mode 100644
index 00000000000..6f673ec79c5
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/cmbright.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/comicsans.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/comicsans.png
new file mode 100644
index 00000000000..70fdf5c694e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/comicsans.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/concmath.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/concmath.png
new file mode 100644
index 00000000000..396729744eb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/concmath.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/concrete.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/concrete.png
new file mode 100644
index 00000000000..8830470ff3f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/concrete.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/fourier.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/fourier.png
new file mode 100644
index 00000000000..aaa11731728
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/fourier.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/fouriernc.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/fouriernc.png
new file mode 100644
index 00000000000..0bd42f0fe41
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/fouriernc.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/garamondmd.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/garamondmd.png
new file mode 100644
index 00000000000..fd837b32025
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/garamondmd.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/iwona.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/iwona.png
new file mode 100644
index 00000000000..a659d61ee66
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/iwona.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/kerkis.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/kerkis.png
new file mode 100644
index 00000000000..29a25d2e346
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/kerkis.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/kurier.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/kurier.png
new file mode 100644
index 00000000000..401ae40ee1c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/kurier.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathpple.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathpple.png
new file mode 100644
index 00000000000..f432ac7fa21
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathpple.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathptmx.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathptmx.png
new file mode 100644
index 00000000000..678ab00fc61
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mathptmx.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/mbtimes.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mbtimes.png
new file mode 100644
index 00000000000..6cae44ccb77
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/mbtimes.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/millennial.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/millennial.png
new file mode 100644
index 00000000000..895b9a5d968
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/millennial.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/pazo.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/pazo.png
new file mode 100644
index 00000000000..e0274c299b6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/pazo.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/pxfonts.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/pxfonts.png
new file mode 100644
index 00000000000..004181a3c2e
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/pxfonts.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/txfonts.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/txfonts.png
new file mode 100644
index 00000000000..de6a24502f7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/txfonts.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/images/utopiamd.png b/Master/texmf-dist/doc/generic/free-math-font-survey/images/utopiamd.png
new file mode 100644
index 00000000000..0083587387a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/images/utopiamd.png
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/Makefile b/Master/texmf-dist/doc/generic/free-math-font-survey/source/Makefile
new file mode 100644
index 00000000000..c41a1da269a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/Makefile
@@ -0,0 +1,99 @@
+
+# Makefile for font survey
+
+all: survey.pdf survey.html
+
+EPSPictures=cm.eps cmbright.eps concrete.eps concmath.eps kerkis.eps millennial.eps fourier.eps chartermd.eps garamondmd.eps utopiamd.eps pazo.eps pxfonts.eps mathpple.eps belleek.eps txfonts.eps mathptmx.eps arev.eps kurier.eps iwona.eps anttor.eps antpolt.eps mbtimes.eps fouriernc.eps comicsans.eps
+# minionpro.eps gentium.eps 
+
+PDFPictures=$(patsubst %.eps,%.pdf,$(EPSPictures))
+survey.pdf: survey.tex $(PDFPictures)
+	pdflatex survey
+	pdflatex survey
+
+#survey.pdf: survey.ps
+#	ps2pdf survey.ps survey.pdf
+
+#survey.ps: survey.dvi
+#	-z option is for hyperlinks
+#	This doesn't work, causing dvips to cryptically say 'Page xx may be too complex to print'
+#	and 'Warning:  no %%Page comments generated.'  The outcome is that only the last page is viewable.
+#	dvips -Ppdf -z survey
+
+#survey.dvi: survey.tex $(EPSPictures)
+#	latex survey
+#	latex survey
+
+#For PracTeX journal:
+hartke.tex: survey.tex
+	# add PracTEX preamble options: email, address, abstract, license
+	# we need \makeatother and \makeatletter around email for the switchemail package used by pracjourn.cls
+	# change typewriter font to lmtt and sans serif to lmss for author block titles
+ 	# change documentclass to pracjourn
+	# graphicx is already included by pracjourn class
+	sed -e 's/%PracTEXreplacement/\\makeatother\\email{lastname @ gmail .dot. com}\\makeatletter\\address{Department of Mathematics\\\\University of Illinois at Urbana-Champaign\\\\Urbana, IL, 61801 USA}\\abstract{We survey free math fonts for \\TeX\\ and \\LaTeX, with examples, instructions for using \\LaTeX\\ packages for changing fonts, and links to sources for the fonts and packages.}\\license{Copyright \\copyright\\ 2006 Stephen G.\\ Hartke\\\\Permission is granted to distribute verbatim or modified\\\\copies of this document provided this notice remains intact.}\\TPJrevision{2006-02-03}\\TPJissue{TPJ 2006 No 01, 2006-02-15}\\renewcommand\\ttdefault{lmtt}\\renewcommand\\sfdefault{lmss}/g' survey.tex | sed -e 's/\\documentclass\[\(.\)*\]{article}/\\documentclass[english]{pracjourn}/g' | sed -e 's/\\usepackage\[pdftex\]{graphicx}//g'> hartke.tex
+
+hartke.pdf: hartke.tex $(PDFPictures)
+	pdflatex hartke
+	pdflatex hartke
+
+
+PNGPictures=$(patsubst %.eps,%.png,$(EPSPictures))
+survey.html: survey.tex $(PNGPictures)
+#	survey.aux from LaTeX can confuse HeVeA
+	rm -f survey.aux
+	hevea survey
+	hevea survey
+
+clean:
+	rm survey.html *.dvi *.eps *.pdf *.png *.aux *.log
+
+
+# Font sample files
+
+TEXTFRAGMENT=textfragment.tex
+SAMPLEFORMAT=sampleformat.tex
+
+# $@ is the name of the matched target
+# $< is the name of the matched dependency
+# $* is the stem
+
+$(EPSPictures): %.eps: %.dvi
+	dvips -o $@ -E $*
+# if the papersize option t is present in ~/.dvipsrc, then the -E option will not work
+# 	some files, like arev.eps, have too much white space on the left
+	./fixepsbbox $@ 90 2
+
+
+DVIPictures=$(patsubst %.eps,%.dvi,$(EPSPictures))
+$(DVIPictures): %.dvi: %.tex $(TEXTFRAGMENT) $(SAMPLEFORMAT)
+	latex $*
+
+$(PDFPictures): %.pdf: %.eps
+	epstopdf $< -o=$@
+
+RESOLUTION=576
+BORDER=25
+$(PNGPictures): %.png: %.eps
+#	Uses ImageMagick and ghostscript; rescaling antialiases better
+	convert -density $(RESOLUTION)x$(RESOLUTION) -antialias -scale 25% -bordercolor white -border $(BORDER)x$(BORDER) $< $@
+
+TEXPictures=$(patsubst %.eps,%.tex,$(EPSPictures))
+ArchDir=fontsurvey_$(shell date +%Y-%m-%d-%H-%M-%S)
+archive:
+	mkdir Archive/$(ArchDir)
+	mkdir Archive/$(ArchDir)/fontsurvey
+	cp survey.lyx survey.tex hevea.sty Makefile $(TEXPictures) $(TEXTFRAGMENT) $(SAMPLEFORMAT) Archive/$(ArchDir)/fontsurvey
+	cd Archive/$(ArchDir); tar cfj $(ArchDir).tar.bz2 fontsurvey
+
+WebPictures=$(patsubst %.eps,%.png,$(EPSPictures))
+ReleaseDir=release_$(shell date +%Y-%m-%d-%H-%M-%S)
+release:
+	mkdir Release/$(ReleaseDir)
+	mkdir Release/$(ReleaseDir)/Free_Math_Font_Survey
+	mkdir Release/$(ReleaseDir)/Free_Math_Font_Survey/source
+	mkdir Release/$(ReleaseDir)/Free_Math_Font_Survey/images
+	cp survey.pdf survey.html README Release/$(ReleaseDir)/Free_Math_Font_Survey
+	cp survey.lyx survey.tex Makefile fixepsbbox $(TEXPictures) $(TEXTFRAGMENT) $(SAMPLEFORMAT) Release/$(ReleaseDir)/Free_Math_Font_Survey/source
+	cp $(WebPictures) Release/$(ReleaseDir)/Free_Math_Font_Survey/images
+	cd Release/$(ReleaseDir); tar cfj $(ReleaseDir).tar.bz2 Free_Math_Font_Survey
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/antpolt.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/antpolt.tex
new file mode 100644
index 00000000000..ef564f5f0fe
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/antpolt.tex
@@ -0,0 +1,14 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[QX]{fontenc}
+\usepackage{antpolt}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/anttor.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/anttor.tex
new file mode 100644
index 00000000000..8e48cb18bed
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/anttor.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[math]{anttor}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/arev.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/arev.tex
new file mode 100644
index 00000000000..646fe5736de
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/arev.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{arev}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/belleek.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/belleek.tex
new file mode 100644
index 00000000000..b9b04de7c9b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/belleek.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{mathtime}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/chartermd.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/chartermd.tex
new file mode 100644
index 00000000000..ef79bee4d7c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/chartermd.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[charter]{mathdesign}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/cm.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/cm.tex
new file mode 100644
index 00000000000..d17bdc3858b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/cm.tex
@@ -0,0 +1,12 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/cmbright.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/cmbright.tex
new file mode 100644
index 00000000000..4504b9e85ce
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/cmbright.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{cmbright}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/comicsans.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/comicsans.tex
new file mode 100644
index 00000000000..260cb2b6f91
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/comicsans.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{comicsans}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/concmath.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/concmath.tex
new file mode 100644
index 00000000000..9be6268afa7
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/concmath.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{ccfonts}\usepackage[T1]{fontenc}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/concrete.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/concrete.tex
new file mode 100644
index 00000000000..c03692ad32d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/concrete.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{ccfonts,eulervm}\usepackage[T1]{fontenc}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
\ No newline at end of file
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/fixepsbbox b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fixepsbbox
new file mode 100644
index 00000000000..08e977932b3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fixepsbbox
@@ -0,0 +1,21 @@
+#!/bin/bash
+
+# fixepsbbox (filename) (left x target) (tolerance)
+
+EPSFile=$1
+TargetX=$2
+Tolerance=$3
+
+LeftX=`grep BoundingBox $EPSFile | cut -d' ' -f 2`
+
+TestVal=$(( ( $LeftX < ( $TargetX - $Tolerance ) ) || ( $LeftX > ( $TargetX + $Tolerance ) ) ))
+
+if [ $TestVal -ne 0 ]
+then
+  echo "Changing left edge of $EPSFile from $LeftX to $TargetX."
+  TmpFile="tmp_`date +%Y-%m-%d-%H-%M-%S`.eps"
+  sed -e 's/BoundingBox: [-]*[[:digit:]]* /BoundingBox: '$TargetX' /g' $EPSFile > $TmpFile
+  mv $TmpFile $EPSFile
+fi
+
+
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/fourier.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fourier.tex
new file mode 100644
index 00000000000..453097fdeb2
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fourier.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{fourier}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/fouriernc.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fouriernc.tex
new file mode 100644
index 00000000000..c25f747589a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/fouriernc.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{fouriernc}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/garamondmd.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/garamondmd.tex
new file mode 100644
index 00000000000..b5c777425de
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/garamondmd.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[garamond]{mathdesign}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/iwona.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/iwona.tex
new file mode 100644
index 00000000000..5a5234dcf91
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/iwona.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[math]{iwona}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/kerkis.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/kerkis.tex
new file mode 100644
index 00000000000..f9a5ad9db36
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/kerkis.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{kmath,kerkis}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/kurier.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/kurier.tex
new file mode 100644
index 00000000000..5d53f38f1d4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/kurier.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[math]{kurier}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathpple.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathpple.tex
new file mode 100644
index 00000000000..a5c3641ca19
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathpple.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{mathpple}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathptmx.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathptmx.tex
new file mode 100644
index 00000000000..508a3402007
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mathptmx.tex
@@ -0,0 +1,14 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{mathptmx}
+\renewcommand{\jmath}{j}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/mbtimes.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mbtimes.tex
new file mode 100644
index 00000000000..c27027999be
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/mbtimes.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{mbtimes}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/millennial.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/millennial.tex
new file mode 100644
index 00000000000..03a9703d0d3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/millennial.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{millennial}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/pazo.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/pazo.tex
new file mode 100644
index 00000000000..bc30bd478a4
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/pazo.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{mathpazo}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/pxfonts.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/pxfonts.tex
new file mode 100644
index 00000000000..2ad4b468f84
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/pxfonts.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage{pxfonts}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/sampleformat.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/sampleformat.tex
new file mode 100644
index 00000000000..2414b7dcbfb
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/sampleformat.tex
@@ -0,0 +1,6 @@
+
+\usepackage{amsmath,amssymb}
+\usepackage[letterpaper,text={5.95in,9in}]{geometry}
+
+\pagestyle{empty}
+\setlength{\parindent}{0cm}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.lyx b/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.lyx
new file mode 100644
index 00000000000..c724b39bdbc
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.lyx
@@ -0,0 +1,7290 @@
+#LyX 1.3 created this file. For more info see http://www.lyx.org/
+\lyxformat 221
+\textclass article
+\begin_preamble
+
+%PracTEXreplacement
+
+% LyX includes graphicx if any pictures are used; so put in ERT boxes
+\usepackage[pdftex]{graphicx}
+\usepackage{epstopdf}
+
+%\usepackage{cite} % numerically sorts multiple references contained in one citation
+
+\usepackage{url} % don't let LyX do this, because IfFileExists confuses HeVeA
+
+\setlength{\fboxsep}{.25in}
+
+\usepackage{array}
+\setlength\extrarowheight{1pt}
+
+\usepackage{color,hyperref}
+\definecolor{linkcolour}{rgb}{0,0.2,0.6}
+\hypersetup{
+  pdfauthor = {Stephen G. Hartke},
+  pdftitle = {A Survey of Free Math Fonts for LaTeX},
+  pdfsubject = {free math fonts for LaTeX},
+  pdfkeywords = {LaTeX, TeX, math font, free},
+  pdfcreator = {LaTeX with hyperref package},
+  pdfproducer = {pdflatex},
+  pdfview = FitH,
+  pdfstartview = FitH,
+  linkcolor = linkcolour, % colors don't work?
+  citecolor = linkcolour,
+  filecolor = linkcolour,
+  urlcolor = linkcolour,
+  pagecolor = linkcolour,
+  colorlinks
+}
+
+\usepackage{ifthen}
+\usepackage{hevea}
+\ifthenelse{\boolean{hevea}}
+{
+  \newcommand{\l}{\begin{rawhtml}&#322;\end{rawhtml}}
+  \newcommand{\acuten}{\begin{rawhtml}&#324;\end{rawhtml}}
+  %\newcommand{\textbackslash}{\begin{rawhtml}&#92;\end{rawhtml}}
+  \newcommand{\captiontitle}[2][dummy]{\caption{#2}}
+  \newcommand{\captionbreak}{}
+  \newenvironment{sidewaystable}{\begin{table}}{\end{table}}
+  \renewcommand{\LaTeX}{LaTeX}  % looks silly in HTML
+  \renewcommand{\TeX}{TeX}
+  \newcommand{\MF}{METAFONT}
+  \newcommand{\pic}[1]
+     {\begin{center}
+         \begin{rawhtml}<table align="center" border="1"><tr><td width="0" align="center"><img src="\end{rawhtml}images/#1.png\begin{rawhtml}"></td></tr></table>\end{rawhtml}
+      \end{center}}
+  \renewcommand{\@figrule}{}  % no hrule around floats
+ % fixes colors
+ \htmlhead{\begin{rawhtml}
+  <title>A Survey of Free Math Fonts for TeX and LaTeX</title>
+  <style type="text/css">
+    BODY { background-color: white; color: black; }
+    A:link { color: #003399; text-decoration: none; }
+    A:active { color: blue; text-decoration: underline; }
+    A:visited { color: #003399; text-decoration: none; }
+    A:hover { color: blue; text-decoration: underline; }
+    H5 {font-size: 110\%;  font-weight: bold; }
+  </style>\end{rawhtml}}
+  \title{A Survey of Free Math Fonts for \TeX{} and \LaTeX{}%
+  \footnote{Copyright 2006 Stephen G.\  Hartke. Permission is granted to distribute verbatim or modified copies of this document provided this notice remains intact.\protect \\ An initial version of this article appeared in \emph{The Prac\TeX{} Journal,} 1, 2006,  \protect\url{http://www.tug.org/pracjourn/2006-1/hartke/}.\protect \\
+The permanent home of this article is \protect\url{http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey}.}}
+  \author{Stephen G. Hartke\footnote{Email: lastname @ gmail dot com.}}
+  \date{May 5, 2006}
+}
+{
+  \usepackage[letterpaper,text={6.5in,9in}]{geometry}
+  \usepackage{palatino}\renewcommand{\ttdefault}{txtt}
+  \usepackage{rotating} % to rotate large table
+  \newcommand{\acuten}{\'n}
+  \newcommand{\pic}[1]
+        %{\hspace*{-\fboxsep}\framebox{\includegraphics{#1.eps}}} % for PracTeX
+        {\framebox{\includegraphics{#1.eps}}}
+  \usepackage{topcapt}  % put captions above figures
+  %\setlength{\abovecaptionskip}{0pt}
+  \newcommand{\captiontitle}[2][]{\topcaption{#2}}
+  \DeclareRobustCommand\captionbreak{\\\hspace*{\fill}}
+  \@ifundefined{MF}{\newcommand{\MF}{METAFONT}} % defined by practex, but not by others
+}
+
+
+\newcommand{\CTAN}[1]{%
+  \ifthenelse{\boolean{hevea}}% HeVeA does not allow parameters in href
+  {\ahref{http://ctan.tug.org/tex-archive#1/}{CTAN:\texttt{#1}}}%
+  {\href{http://ctan.tug.org/tex-archive#1/}{CTAN:\texttt{#1}}}%
+}
+\newcommand{\TUGboat}[2]{%
+  \ifthenelse{\boolean{hevea}}%
+  {\ahref{http://www.tug.org/TUGboat/Articles/#1}{#2}}%
+  {\href{http://www.tug.org/TUGboat/Articles/#1}{#2}}%
+}
+\end_preamble
+\language english
+\inputencoding auto
+\fontscheme default
+\graphics default
+\paperfontsize 12
+\spacing single 
+\papersize Default
+\paperpackage a4
+\use_geometry 0
+\use_amsmath 0
+\use_natbib 0
+\use_numerical_citations 0
+\paperorientation portrait
+\secnumdepth 3
+\tocdepth 3
+\paragraph_separation indent
+\defskip medskip
+\quotes_language english
+\quotes_times 2
+\papercolumns 1
+\papersides 1
+\paperpagestyle default
+
+\layout Title
+
+A Survey of Free Math Fonts for TeX and LaTeX
+\begin_inset Foot
+collapsed true
+
+\layout Standard
+
+Copyright 2006 Stephen G.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+ 
+\end_inset 
+
+ Hartke.
+ Permission is granted to distribute verbatim or modified copies of this
+ document provided this notice remains intact.
+\newline 
+An initial version of this article appeared in 
+\emph on 
+The PracTeX Journal,
+\emph default 
+ 1, 2006, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.tug.org/pracjourn/2006-1/hartke/}
+\end_inset 
+
+.
+\newline 
+The permanent home of this article is 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey}
+\end_inset 
+
+.
+\end_inset 
+
+
+\layout Author
+
+Stephen G.
+ Hartke
+\begin_inset Foot
+collapsed true
+
+\layout Standard
+
+Email: lastname @ gmail dot com.
+\end_inset 
+
+
+\layout Date
+
+May 5, 2006
+\layout Comment
+
+The title, author, and date are in the preamble for HeVeA.
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{htmlonly}
+\end_inset 
+
+
+\layout Standard
+
+
+\series bold 
+Note:
+\series default 
+ 
+\emph on 
+This survey is also available in 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+href{survey.pdf}{PDF}
+\end_inset 
+
+ format.
+\emph default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+medskip
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{htmlonly}
+\end_inset 
+
+
+\layout Section*
+
+Contents
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:Intro]{
+\end_inset 
+
+
+\series bold 
+Introduction
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:Intro}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:TeXFonts]{
+\end_inset 
+
+
+\series bold 
+Fonts Originally Designed for TeX
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:TeXFonts}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Quote
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:CM]{
+\end_inset 
+
+Computer Modern
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:CMBright]{
+\end_inset 
+
+CM Bright
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:ConcEuler]{
+\end_inset 
+
+Concrete and Euler
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:ConcMath]{
+\end_inset 
+
+Concrete Math
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Iwona]{
+\end_inset 
+
+Iwona
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Kurier]{
+\end_inset 
+
+Kurier
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:AntPolt]{
+\end_inset 
+
+Antykwa P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+tawskiego
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:AntTor]{
+\end_inset 
+
+Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:PSFonts]{
+\end_inset 
+
+
+\series bold 
+Core Postscript Fonts
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:PSFonts}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Quote
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Kerkis]{
+\end_inset 
+
+Kerkis
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Millen]{
+\end_inset 
+
+Millennial
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:fouriernc]{
+\end_inset 
+
+fouriernc
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:pxfonts]{
+\end_inset 
+
+pxfonts
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Pazo]{
+\end_inset 
+
+Pazo
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:mathpple]{
+\end_inset 
+
+mathpple
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:txfonts]{
+\end_inset 
+
+txfonts
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Belleek]{
+\end_inset 
+
+Belleek
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:mathptmx]{
+\end_inset 
+
+mathptmx
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:mbtimes]{
+\end_inset 
+
+mbtimes
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:OtherFonts]{
+\end_inset 
+
+
+\series bold 
+Other Free Fonts
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:OtherFonts}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Quote
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:Arev]{
+\end_inset 
+
+Arev Sans
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:chartermd]{
+\end_inset 
+
+Math Design with Charter
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:comicsans]{
+\end_inset 
+
+Comic Sans
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:garamd]{
+\end_inset 
+
+Math Design with Garamond
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:fourier]{
+\end_inset 
+
+Fourier-GUTenberg
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[fig:utopiamd]{
+\end_inset 
+
+Math Design with Utopia
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:Compar]{
+\end_inset 
+
+
+\series bold 
+Comparison of Features
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:Compar}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Standard
+\noindent 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hyperref[sec:Creation]{
+\end_inset 
+
+
+\series bold 
+Creation of this Survey
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{latexonly}
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hfill
+\end_inset 
+
+
+\series bold 
+
+\begin_inset LatexCommand \pageref{sec:Creation}
+
+\end_inset 
+
+
+\series default 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{latexonly}
+\end_inset 
+
+
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:Intro}
+
+\end_inset 
+
+Introduction
+\layout Standard
+
+One of the biggest challenges in selecting a font for TeX or LaTeX is that
+ there are not very many math fonts that match the plethora of available
+ text fonts.
+ It's reasonably easy to use an arbitrary Postscript Type\SpecialChar ~
+1 font in TeX for
+ text (see Philipp Lehman's Font Installation Guide\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANfontinstgd}
+
+\end_inset 
+
+), but obtaining and configuring a matching math font from scratch is a
+ demanding task.
+ Thus, there are few math fonts for TeX, and in particular very few free
+ ones.
+ However, in the past few years, several very nice free fonts have been
+ released.
+ The goal of this article is to list all of the free math fonts and to provide
+ examples.
+\layout Standard
+
+
+\begin_inset Quotes eld
+\end_inset 
+
+Free
+\begin_inset Quotes erd
+\end_inset 
+
+ here means fonts that are free to use (both commercially and non-com\SpecialChar \-
+mercially)
+ and free to distribute, but not necessarily free to modify.
+ I also am biased towards listing fonts that have outline versions in PostScript
+ Type\SpecialChar ~
+1 format suitable for embedding in Postscript PS or Adobe Acrobat PDF
+ files.
+ Donald E.
+ Knuth originally designed the 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ system for producing fonts for TeX in bitmap format.
+ PS or PDF files that have embedded bitmap fonts do not display well in
+ Adobe Acrobat Reader,
+\begin_inset Foot
+collapsed true
+
+\layout Standard
+
+Starting with version 6, Adobe Acrobat Reader displays bitmap fonts fine.
+ The free PDF viewers Ghostview and xpdf have always displayed bitmap fonts
+ accurately.
+\end_inset 
+
+ to the point of being almost unreadable on the screen, and are also noticeable
+ when printing at extremely high resolutions (on photo-setters, for instance).
+ Since outline fonts contain mathematical descriptions of the curves used
+ in each glyph, they can be scaled to any resolution while retaining image
+ quality.
+\layout Standard
+
+The fonts listed here are categorized according to their origin: whether
+ originally designed for TeX, related to the standard Postscript fonts,
+ or other free fonts.
+ A font's origin does not particularly bear on its quality or suitability
+ for typesetting mathematics.
+ No recommendations or evaluations of the fonts are given here, as people's
+ tastes in fonts vary greatly.
+ The goal of this survey is simply to make authors aware of all their options.
+\layout Standard
+
+Most of the fonts can be selected by including a single package in the preamble
+ of the user's LaTeX file (the 
+\emph on 
+preamble
+\emph default 
+ is the section after 
+\begin_inset Quotes eld
+\end_inset 
+
+
+\family typewriter 
+
+\backslash 
+documentclass{}
+\family default 
+
+\begin_inset Quotes erd
+\end_inset 
+
+ and before 
+\begin_inset Quotes eld
+\end_inset 
+
+
+\family typewriter 
+
+\backslash 
+begin{document}
+\family default 
+
+\begin_inset Quotes erd
+\end_inset 
+
+).
+ The line or lines to include for each font are listed in the caption of
+ the sample figure.
+ For example 
+\begin_inset Quotes eld
+\end_inset 
+
+
+\family typewriter 
+
+\backslash 
+usepackage{fourier}
+\family default 
+
+\begin_inset Quotes erd
+\end_inset 
+
+ uses Utopia and Fourier-GUTenberg, as shown in the sample LaTeX file in
+ Section\SpecialChar ~
+
+\begin_inset LatexCommand \ref{sec:Creation}
+
+\end_inset 
+
+.
+\layout Standard
+
+Walter A.
+ Schmidt also has a survey in German of math fonts\SpecialChar ~
+
+\begin_inset LatexCommand \cite{WASmathfonts}
+
+\end_inset 
+
+ that concentrates more on commercial fonts.
+ Schmidt's survey has several examples that show different pairings between
+ text fonts and math fonts.
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:TeXFonts}
+
+\end_inset 
+
+Fonts Originally Designed for TeX
+\layout Standard
+
+These fonts were originally designed for use with TeX, using either 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ or MetaType1\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANmetatype1}
+
+\end_inset 
+
+.
+\layout Paragraph
+
+Computer Modern:
+\layout Standard
+
+Knuth created Computer Modern\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CMBook}
+
+\end_inset 
+
+ as the default font for TeX.
+ The font set includes serif, sans serif, and monospaced text faces, and
+ corresponding math fonts.
+ The math symbol set is very complete.
+ Computer Modern is 
+\emph on 
+the
+\emph default 
+ font for TeX, which leads some to claim that the font is overused.
+ The characters are fairly thin and light, and so are not as readable on
+ screen in small sizes or from high-resolution laser printers.
+\begin_inset Foot
+collapsed true
+
+\layout Standard
+
+When on screen, the fonts are usually anti-aliased, often into a gray blur
+ because the stems are not thick enough to fill a pixel.
+ When printed with a high-resolution laser printer, the fonts are shown
+ accurately, but I think are too thin.
+ With a medium-resolution printer like an inkjet, there's enough resolution
+ to show the form of the letters (unlike on screen), but the low-resolution
+ "bulks up" the letters compared to a high-resolution laser printer, with
+ the letters thus appearing darker.
+\end_inset 
+
+ In a comparison by Raph Levien\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CMRgain}
+
+\end_inset 
+
+, the printing in Knuth's 
+\emph on 
+Digital Typography
+\emph default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{DigTyp}
+
+\end_inset 
+
+ is heavier than the digital version or from a laser printer.
+\layout Standard
+
+Type\SpecialChar ~
+1 versions of Computer Modern from Blue Sky Research and Y&Y, Inc.
+ have been made freely available by the American Mathematical Society (AMS)
+ and a collection of publishers and other technical companies\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbluesky,bluesky}
+
+\end_inset 
+
+.
+ Basil K.
+ Malyshev has also released a free Type\SpecialChar ~
+1 version of Computer Modern\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbakoma}
+
+\end_inset 
+
+, originally for use with his TeX system BaKoMa TeX.
+\layout Standard
+
+Computer Modern has been extended to include more characters, particularly
+ for non-English European languages.
+ These fonts include European Computer Modern by J
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+"o
+\end_inset 
+
+rg Knappen and Norbert Schwarz (
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ only) 
+\begin_inset LatexCommand \cite{CTANec}
+
+\end_inset 
+
+; Tt2001 by Szab
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+ P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'e
+\end_inset 
+
+ter (converted into Type\SpecialChar ~
+1 format from 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ sources using 
+\family typewriter 
+textrace
+\family default 
+; Tt2001 has been superseded by CM-Super, which P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'e
+\end_inset 
+
+ter recommends) 
+\begin_inset LatexCommand \cite{textrace,CTANtt2001}
+
+\end_inset 
+
+; CM-Super by Vladimir Volovich (also converted using 
+\family typewriter 
+textrace
+\family default 
+) 
+\begin_inset LatexCommand \cite{CM-Super,CTANcm-super}
+
+\end_inset 
+
+; and Latin Modern by Bogus
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+aw Jackowski and Janusz M.
+ Nowacki (extended from the Blue Sky AMS fonts using MetaType1) 
+\begin_inset LatexCommand \cite{LatinModern,CTANlm}
+
+\end_inset 
+
+.
+ 
+\layout Standard
+
+The SliTeX font (
+\family typewriter 
+lcmss
+\family default 
+) is a sans serif text face that has wide letters and high 
+\emph on 
+x
+\emph default 
+ height.
+ Its high readability makes it extremely suitable for slide presentations.
+ However, there is no matching math font.
+ SliTeX sans serif can be set as the primary text font using TeXPower's
+ 
+\family typewriter 
+tpslifonts.sty
+\family default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{texpower}
+
+\end_inset 
+
+.
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Computer Modern]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:CM}
+
+\end_inset 
+
+Computer Modern (using the Blue Sky and Y&Y Type\SpecialChar ~
+1 fonts; no package necessary).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{cm}
+\end_inset 
+
+
+\end_inset 
+
+ 
+\layout Paragraph
+
+Computer Modern Bright: 
+\layout Standard
+
+This a sans serif font with corresponding math font derived from Computer
+ Modern by Walter A.
+ Schmidt 
+\begin_inset LatexCommand \cite{CTANcmbright}
+
+\end_inset 
+
+.
+ CM-Super contains Type\SpecialChar ~
+1 versions of the text fonts in T1 encoding, and
+ Harald Harders created Type\SpecialChar ~
+1 versions of the text and math fonts called
+ 
+\family typewriter 
+hfbright
+\family default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANhfbright}
+
+\end_inset 
+
+ using 
+\family typewriter 
+mftrace
+\family default 
+.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[CM Bright]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:CMBright}
+
+\end_inset 
+
+CM Bright (
+\family typewriter 
+
+\backslash 
+usepackage{cmbright}
+\family default 
+; output uses the 
+\family typewriter 
+hfbright
+\family default 
+ fonts).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{cmbright}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Concrete and Euler or Concrete Math:
+\layout Standard
+
+The Concrete font was created by Knuth for his book 
+\emph on 
+Concrete Mathematics
+\emph default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{concretebook}
+
+\end_inset 
+
+.
+ Hermann Zapf was commissioned by the AMS to create the math font Euler
+ for use in 
+\emph on 
+Concrete Mathematics
+\emph default 
+.
+ Type\SpecialChar ~
+1 versions of Concrete in T1 encoding are available in the CM-Super
+ collection\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANcm-super}
+
+\end_inset 
+
+, and Type\SpecialChar ~
+1 versions of Euler are available in the Blue Sky collection from
+ the AMS\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbluesky}
+
+\end_inset 
+
+ and in the BaKoMa collection\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbakoma}
+
+\end_inset 
+
+.
+ The 
+\family typewriter 
+eulervm
+\family default 
+ package by Walter Schmidt\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANeulervm,eulervm}
+
+\end_inset 
+
+ implements virtual fonts for Euler that are more efficient to use with
+ LaTeX.
+ Ulrik Vieth created the Concrete Math fonts\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANconcmath}
+
+\end_inset 
+
+ to match the Concrete text fonts; the only free versions are implemented
+ in 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\end_inset 
+
+.
+ The 
+\family typewriter 
+ccfonts
+\family default 
+ package by Walter Schmidt\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANccfonts}
+
+\end_inset 
+
+ changes the text font to Concrete and changes the math font to the Concrete
+ Math fonts if 
+\family typewriter 
+eulervm
+\family default 
+ is not loaded.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Concrete and Euler]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:ConcEuler}
+
+\end_inset 
+
+Concrete text with Euler math (
+\family typewriter 
+
+\backslash 
+usepackage{ccfonts,eulervm} 
+\backslash 
+usepackage[T1]{fontenc}
+\family default 
+).
+ Note that Concrete does not have a bold font, so Computer Modern is used
+ instead.
+ Non-bold text output uses the CM-Super Concrete fonts.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{concrete}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Concrete Math]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:ConcMath}
+
+\end_inset 
+
+Concrete text with Concrete math (
+\family typewriter 
+
+\backslash 
+usepackage{ccfonts} 
+\backslash 
+usepackage[T1]{fontenc}
+\family default 
+).
+ Note that Concrete does not have a bold font, so Computer Modern is used
+ instead.
+ Non-bold text output uses the CM-Super Concrete fonts.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{concmath}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Iwona and Kurier:
+\layout Standard
+
+The fonts Iwona and Kurier were created by J.
+ M.
+ Nowacki\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANiwona,CTANkurier}
+
+\end_inset 
+
+ using the MetaType1 system based on typefaces by the Polish typographer
+ Ma
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+gorzata Budyta.
+ The two fonts are very similar, except that Kurier avoids 
+\begin_inset Quotes eld
+\end_inset 
+
+ink traps
+\begin_inset Quotes erd
+\end_inset 
+
+ with gaps in its strokes.
+ The packages have complete math support in both TeX and LaTeX.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Iwona]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Iwona}
+
+\end_inset 
+
+Iwona text and math (
+\family typewriter 
+
+\backslash 
+usepackage[math]{iwona}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{iwona}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Kurier]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Kurier}
+
+\end_inset 
+
+Kurier text and math (
+\family typewriter 
+
+\backslash 
+usepackage[math]{kurier}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{kurier}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Antykwa P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+tawskiego:
+\layout Standard
+
+J.
+ M.
+ Nowacki created the font Antykwa P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+tawskiego\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANantp}
+
+\end_inset 
+
+ using the MetaType1 system based on a typeface by Polish typographer Adam
+ P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\backslash 
+l{}
+\end_inset 
+
+tawski.
+ The package 
+\family typewriter 
+antpolt
+\family default 
+ has no math support at this time, and requires the encoding to be set to
+ QX or OT4.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Antykwa P
+\backslash 
+'o
+\backslash 
+l{}tawskiego]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:AntPolt}
+
+\end_inset 
+
+Antykwa P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+tawskiego text (
+\family typewriter 
+
+\backslash 
+usepackage{antpolt}
+\family default 
+ and 
+\family typewriter 
+
+\backslash 
+usepackage[QX]{fontenc}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{antpolt}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska:
+\layout Standard
+
+The font Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska was created by J.
+ M.
+ Nowacki\SpecialChar ~
+
+\begin_inset LatexCommand \cite{AntTorunska,CTANantt}
+
+\end_inset 
+
+ using the MetaType1 system based on a typeface by the Polish typographer
+ Zygfryd Gardzielewski.
+ The package 
+\family typewriter 
+anttor
+\family default 
+ has complete math support in both TeX and LaTeX.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Antykwa Toru
+\backslash 
+'nska]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:AntTor}
+
+\end_inset 
+
+Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska text and math (
+\family typewriter 
+
+\backslash 
+usepackage[math]{anttor}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{anttor}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:PSFonts}
+
+\end_inset 
+
+Core Postscript Fonts
+\layout Standard
+
+When Adobe introduced Postscript in 1984, they defined 35 core fonts (in
+ 10 typefaces) that must be present in all Postscript interpreters.
+ In 1996, URW++ released a replacement set for the core fonts under the
+ GNU General Public License.
+ The URW++ fonts were primarily released for use with Ghostscript, a free
+ Postscript interpreter.
+ Table\SpecialChar ~
+
+\begin_inset LatexCommand \ref{cap:CorePostscriptFonts}
+
+\end_inset 
+
+ lists the original Postscript fonts, along with the URW++/Ghostscript equivalen
+ts.
+ Each font can be used as the default text font by selecting the indicated
+ LaTeX package from the PSNFSS distribution\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpsnfss}
+
+\end_inset 
+
+.
+\begin_inset Float table
+wide false
+collapsed true
+
+\layout Standard
+\align center 
+
+\begin_inset  Tabular
+<lyxtabular version="3" rows="11" columns="4">
+<features>
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<row topline="true" bottomline="true">
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Adobe Postscript
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+URW++/Ghostscript
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+# of fonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+package
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Avant Garde
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+URW Gothic L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+avant
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Bookman
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+URW Bookman L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+bookman
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Courier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Nimbus Mono L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+courier
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Helvetica
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Nimbus Sans L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+8
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+helvet
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+New Century Schoolbook
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Century Schoolbook L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+newcent
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Palatino
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+URW Palladio L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+palatino
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Symbol
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Standard Symbols L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+1
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+---
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Times
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Nimbus Roman No.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+ 
+\end_inset 
+
+9 L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+4
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+times
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Zapf Chancery
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+URW Chancery L
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+1
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\family typewriter 
+chancery
+\end_inset 
+</cell>
+</row>
+<row bottomline="true">
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Zapf Dingbats
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Dingbats
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+1
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+---
+\end_inset 
+</cell>
+</row>
+</lyxtabular>
+
+\end_inset 
+
+
+\layout Standard
+\align center 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Core Postscript fonts]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{cap:CorePostscriptFonts}
+
+\end_inset 
+
+Core Postscript fonts and URW++/Ghostscript equivalents.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\end_inset 
+
+ 
+\layout Paragraph
+
+Avant Garde and Kerkis Sans:
+\layout Standard
+
+The font Kerkis Sans was created by Antonis Tsolomitis\SpecialChar ~
+
+\begin_inset LatexCommand \cite{Kerkis,CTANkerkis}
+
+\end_inset 
+
+ by extending Avant Garde to include Greek and additional Latin characters.
+ The resulting fonts are stand-alone and can be used by applications outside
+ of TeX.
+ The package 
+\family typewriter 
+kerkis
+\family default 
+ sets the sans serif font to Kerkis Sans; there is no package option to
+ set Kerkis Sans to be the primary text font.
+\layout Paragraph
+
+Bookman and Kerkis:
+\layout Standard
+
+The font Kerkis was created by Antonis Tsolomitis\SpecialChar ~
+
+\begin_inset LatexCommand \cite{Kerkis,CTANkerkis}
+
+\end_inset 
+
+ by extending URW Bookman\SpecialChar ~
+L to include Greek and additional Latin characters.
+ The resulting fonts are stand-alone and can be used by applications outside
+ of TeX.
+ A font of math symbols is included, but not used by the LaTeX package.
+ The package 
+\family typewriter 
+kmath
+\family default 
+ uses txfonts for math symbols and uppercase Greek letters.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Kerkis]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Kerkis}
+
+\end_inset 
+
+Kerkis text and math (
+\family typewriter 
+
+\backslash 
+usepackage{kmath,kerkis}
+\family default 
+; the order of the packages matters, since 
+\family typewriter 
+kmath
+\family default 
+ loads the 
+\family typewriter 
+txfonts
+\family default 
+ package which changes the default text font).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{kerkis}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+New Century Schoolbook and Millennial or fouriernc: 
+\layout Standard
+
+The Millennial math font of the current author contains Greek letters and
+ other letter-like mathematical symbols.
+ A set of virtual fonts is provided that uses New Century Schoolbook for
+ Latin letters in math, Millennial for Greek and other letter-like symbols,
+ and txfonts and Computer Modern for all other symbols, including binary
+ operators, relations, and large symbols.
+ This font is still in development, but will hopefully be released in 2006.
+ The 
+\family typewriter 
+fouriernc
+\family default 
+ package of Michael Zedler\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANfouriernc}
+
+\end_inset 
+
+ uses New Century Schoolbook for text and Latin letters in mathematics,
+ and the Greek and symbol fonts from the Fourier-GUTenberg package for the
+ remaining mathematical symbols.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Millennial]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Millen}
+
+\end_inset 
+
+New Century Schoolbook with Millennial math 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captionbreak 
+\end_inset 
+
+(
+\family typewriter 
+
+\backslash 
+usepackage{millennial}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{millennial}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[fouriernc]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:fouriernc}
+
+\end_inset 
+
+New Century Schoolbook with Fourier math 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captionbreak 
+\end_inset 
+
+(
+\family typewriter 
+
+\backslash 
+usepackage{fouriernc}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{fouriernc}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Palatino and pxfonts, Pazo, or mathpple:
+\layout Standard
+
+Young Ryu created the pxfonts collection\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpxfonts}
+
+\end_inset 
+
+, which contains Greek and other letter-like symbols, as well as a complete
+ set of geometric symbols, including the AMS symbols.
+ Diego Puga created the Pazo math fonts, which include the Greek letters
+ and other letter-like symbols in a style that matches Palatino.
+ The LaTeX package 
+\family typewriter 
+mathpazo
+\family default 
+ (now part of PSNFSS\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpsnfss}
+
+\end_inset 
+
+) uses Palatino for Latin letters, Pazo for Greek and other letter-like
+ symbols, and Computer Modern for geometric symbols.
+ The LaTeX package 
+\family typewriter 
+mathpple
+\family default 
+ (also part of PSNFSS\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpsnfss}
+
+\end_inset 
+
+) uses Palatino for Latin letters and slanted Euler for Greek and other
+ symbols.
+ Since Hermann Zapf designed both Palatino and Euler, the designs mesh well.
+ An alternate use of Euler is using the 
+\family typewriter 
+eulervm
+\family default 
+ package.
+ Ralf Stubner added small caps and old-style figures to URW Palladio L in
+ the FPL package\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANfpl}
+
+\end_inset 
+
+, and Walter Schmidt extended these fonts in the FPL Neu package\SpecialChar ~
+
+\begin_inset LatexCommand \cite{fplneu}
+
+\end_inset 
+
+.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[pxfonts]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:pxfonts}
+
+\end_inset 
+
+Palatino text with pxfonts math (
+\family typewriter 
+
+\backslash 
+usepackage{pxfonts}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{pxfonts}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Pazo]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Pazo}
+
+\end_inset 
+
+Palatino text with Pazo math (
+\family typewriter 
+
+\backslash 
+usepackage{mathpazo}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{pazo}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[mathpple]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:mathpple}
+
+\end_inset 
+
+Palatino text with Euler math (
+\family typewriter 
+
+\backslash 
+usepackage{mathpple}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{mathpple}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Times and txfonts, Belleek, mathptmx, or mbtimes:
+\layout Standard
+
+Young Ryu created the txfonts collection\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANtxfonts}
+
+\end_inset 
+
+, which contains Greek and other letter-like symbols, as well as a complete
+ set of geometric symbols, including the AMS symbols.
+ The 
+\family typewriter 
+txfonts
+\family default 
+ package also includes a very nice typewriter font, 
+\family typewriter 
+txtt
+\family default 
+.
+ Belleek was created by Richard Kinch\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbelleek,Belleek}
+
+\end_inset 
+
+ and is a drop-in replacement for the commercial fonts required by the 
+\family typewriter 
+mathtime
+\family default 
+ package (now part of PSNFSS\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpsnfss}
+
+\end_inset 
+
+).
+ The LaTeX package 
+\family typewriter 
+mathptmx
+\family default 
+ (also part of PSNFSS\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANpsnfss}
+
+\end_inset 
+
+) uses Times for Latin letters and Symbol for Greek and other symbols.
+ Michel Bovani created the 
+\family typewriter 
+mbtimes
+\family default 
+ package by using Omega Serif for text and Latin and Greek letters in mathematic
+s.
+ 
+\family typewriter 
+mbtimes
+\family default 
+ also includes symbol fonts and a set of calligraphic letters.
+ Omega Serif is the primary font for Omega, a 16-bit extension of TeX by
+ John Plaice and Yannis Haralambous\SpecialChar ~
+
+\begin_inset LatexCommand \cite{Omega}
+
+\end_inset 
+
+.
+\layout Standard
+
+The STIX fonts project\SpecialChar ~
+
+\begin_inset LatexCommand \cite{STIX}
+
+\end_inset 
+
+ is a collaboration of several academic publishers to create a set of Times-comp
+atible fonts containing every possible glyph needed for mathematical and
+ technical publishing.
+ These fonts are still in development, with a scheduled release in the middle
+ of 2006.
+\layout Standard
+
+Note that Adobe Reader 7.0 replaces Times with Adobe Serif MM if Times or
+ the Ghostscript equivalent Nimbus Roman No.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+ 
+\end_inset 
+
+9 L is not embedded in the PDF file.
+ Adobe Serif MM only has an oblique version, not a real italics, and thus,
+ the primary text and Latin letters in mathematics will not match letters
+ taken from additional fonts.
+ This problem can be avoided by embedding Times or the Ghostscript equivalent
+ Nimbus Roman No.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+ 
+\end_inset 
+
+9 L into the PDF file.
+ Also, I have heard (but not personally verified) that the Windows version
+ of Adobe Reader displays Times New Roman when Times is not embedded.
+ The upright versions of the two typefaces are very similar, but the italics
+ are noticeably different (consider the 
+\emph on 
+z
+\emph default 
+, for instance).
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[txfonts]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:txfonts}
+
+\end_inset 
+
+Times text with txfonts math (
+\family typewriter 
+
+\backslash 
+usepackage[varg]{txfonts}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{txfonts}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Belleek]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Belleek}
+
+\end_inset 
+
+Times text with Belleek math (
+\family typewriter 
+
+\backslash 
+usepackage{mathtime}
+\family default 
+; output uses the Belleek fonts).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{belleek}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[mathptmx]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:mathptmx}
+
+\end_inset 
+
+Times text with Symbol math (
+\family typewriter 
+
+\backslash 
+usepackage{mathptmx}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{mathptmx}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[mbtimes]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:mbtimes}
+
+\end_inset 
+
+Omega Serif text with Omega math (
+\family typewriter 
+
+\backslash 
+usepackage{mbtimes}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{mbtimes}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Standard
+\added_space_top bigskip 
+Helvetica, Courier, and Zapf Chancery do not have matching math fonts.
+ Courier and Zapf Chancery are inappropriate for mathematics anyway, but
+ Helvetica is sometimes used for presentations and posters.
+ The free fonts MgOpenModerna\SpecialChar ~
+
+\begin_inset LatexCommand \cite{MgOpenModerna}
+
+\end_inset 
+
+ and FreeSans\SpecialChar ~
+
+\begin_inset LatexCommand \cite{FreeSans}
+
+\end_inset 
+
+ would be natural choices for the Greek letters in a Helvetica mathematics
+ font.
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:OtherFonts}
+
+\end_inset 
+
+Other Free Fonts
+\layout Standard
+
+Several other fonts have been released for use with free open-source software.
+ LaTeX packages have been created for most of these fonts.
+\layout Paragraph
+
+Bitstream Vera Sans and Arev Sans:
+\layout Standard
+
+Bitstream Vera was released by Bitstream in cooperation with the Gnome Foundatio
+n\SpecialChar ~
+
+\begin_inset LatexCommand \cite{vera}
+
+\end_inset 
+
+ as a high quality scalable free font for use with free open-source software.
+ Bitstream Vera serif, sans serif, and sans mono are available in text using
+ the 
+\family typewriter 
+bera
+\family default 
+ package by Malte Rosenau and Walter\SpecialChar ~
+A.
+ Schmidt\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbera}
+
+\end_inset 
+
+.
+ Tavmjong Bah created Arev Sans\SpecialChar ~
+
+\begin_inset LatexCommand \cite{arev}
+
+\end_inset 
+
+ by extending Bitstream Vera Sans to include Greek, Cyrillic, and many mathemati
+cal symbols.
+ The current author created the LaTeX package 
+\family typewriter 
+arev
+\family default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANarev}
+
+\end_inset 
+
+ using Arev Sans for text and math letters and bold Math Design fonts for
+ Bitstream Charter for symbols.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Arev Sans]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Arev}
+
+\end_inset 
+
+Arev Sans text with Arev math (
+\family typewriter 
+
+\backslash 
+usepackage{arev}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{arev}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Bitstream Charter and Math Design:
+\layout Standard
+
+Bitstream Charter\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANcharter}
+
+\end_inset 
+
+ was donated by Bitstream for use with X Windows.
+ The Math Design fonts for Bitstream Charter created by Paul Pichaureau\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANmathdesign}
+
+\end_inset 
+
+ are very complete, including Greek letters, symbols from Computer Modern,
+ and the AMS symbols.
+ Charis SIL\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CharisSIL}
+
+\end_inset 
+
+ might be an alternate source for Greek letters that match Bitstream Charter
+ more closely.
+ Another possibility for a math font is to use the Euler fonts with the
+ 
+\family typewriter 
+charter
+\family default 
+ and 
+\family typewriter 
+eulervm
+\family default 
+ packages.
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Math Design for Charter]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:chartermd}
+
+\end_inset 
+
+Bitstream Charter text with Math Design math 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captionbreak 
+\end_inset 
+
+(
+\family typewriter 
+
+\backslash 
+usepackage[charter]{mathdesign}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{chartermd}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Comic Sans:
+\layout Standard
+
+Comic Sans is one of Microsoft's core web fonts that is freely available\SpecialChar ~
+
+\begin_inset LatexCommand \cite{comicsans}
+
+\end_inset 
+
+.
+ The 
+\family typewriter 
+comicsans
+\family default 
+ package by Scott Pakin\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANcomicsans}
+
+\end_inset 
+
+ implements Comic Sans as both the primary text font and the Latin and Greek
+ letters in mathematics.
+ Computer Modern is used for geometric symbols that are not present in Comic
+ Sans.
+ Comic Sans is hard to read for large blocks of text, but might be nice
+ to use for short comments in a handwriting style.
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Comic Sans]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:comicsans}
+
+\end_inset 
+
+Comic Sans text and math (
+\family typewriter 
+
+\backslash 
+usepackage{comicsans}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{comicsans}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Comment
+
+Gentium not released yet.
+\begin_deeper 
+\layout Paragraph
+
+Gentium: 
+\layout Standard
+
+Gentium was designed by Victor Gaultney\SpecialChar ~
+
+\begin_inset LatexCommand \cite{Gentium}
+
+\end_inset 
+
+ to be suitable for any language that uses a Latin-based script.
+ Gentium was released by SIL under the Open Font License.
+ Michael Zedler converted Gentium to Type\SpecialChar ~
+1 format and produced a LaTeX package\SpecialChar ~
+
+\begin_inset LatexCommand \cite{Gentiumtex}
+
+\end_inset 
+
+
+\begin_inset Foot
+collapsed true
+
+\layout Standard
+
+This package is currently in development; when completed it will presumably
+ be posted somewhere more official.
+\end_inset 
+
+ for its use; the mathematics uses Gentium for Latin and Greek letters and
+ MnSymbol for geometric symbols.
+ 
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Gentium]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:Gentium}
+
+\end_inset 
+
+Gentium text with Gentium math (
+\family typewriter 
+
+\backslash 
+usepackage{gentium}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{gentium}
+\end_inset 
+
+
+\end_inset 
+
+
+\end_deeper 
+\layout Paragraph
+
+URW Garamond and Math Design: 
+\layout Standard
+
+URW Garamond No.\SpecialChar ~
+8\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANgaramond}
+
+\end_inset 
+
+ is available under the Aladdin Free Public License as part of the GhostPCL
+ project.
+ The Math Design fonts for URW Garamond created by Paul Pichaureau\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANmathdesign}
+
+\end_inset 
+
+ are very complete, including Greek letters, symbols from Computer Modern,
+ and the AMS symbols.
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Math Design for Garamond]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:garamd}
+
+\end_inset 
+
+URW Garamond text with Math Design math 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captionbreak 
+\end_inset 
+
+(
+\family typewriter 
+
+\backslash 
+usepackage[garamond]{mathdesign}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{garamondmd}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Paragraph
+
+Utopia and Fourier or Math Design:
+\layout Standard
+
+Utopia\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANutopia}
+
+\end_inset 
+
+ was donated by Adobe for use with X Windows.
+ Michel Bovani created Fourier-GUTenberg\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANfourier}
+
+\end_inset 
+
+ as an accompaniment to Utopia and is very complete, containing both Greek
+ letters and standard and AMS symbols.
+ The Math Design fonts for Utopia of Paul Pichaureau\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANmathdesign}
+
+\end_inset 
+
+ are also very complete, including Greek letters and AMS symbols.
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Fourier-GUTenberg]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:fourier}
+
+\end_inset 
+
+Utopia text with Fourier-GUTenberg math (
+\family typewriter 
+
+\backslash 
+usepackage{fourier}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{fourier}
+\end_inset 
+
+
+\end_inset 
+
+
+\begin_inset Float figure
+wide true
+collapsed true
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Math Design for Utopia]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{fig:utopiamd}
+
+\end_inset 
+
+Utopia text with Math Design math 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captionbreak 
+\end_inset 
+
+(
+\family typewriter 
+
+\backslash 
+usepackage[utopia]{mathdesign}
+\family default 
+).
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+pic{utopiamd}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Standard
+\added_space_top bigskip 
+Using 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\end_inset 
+
+, Achim Blumensath created the package 
+\family typewriter 
+MnSymbol
+\family default 
+\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANmnsymbol}
+
+\end_inset 
+
+, which contains geometric symbols (no Greek or other letter-like symbols)
+ in varying optical sizes that match the commercial font Adobe MinionPro.
+ The 
+\family typewriter 
+MnSymbol
+\family default 
+ package also contains traced Type\SpecialChar ~
+1 versions.
+ 
+\family typewriter 
+MnSymbol
+\family default 
+ is free; however the package 
+\family typewriter 
+MinionPro
+\family default 
+ of Achim Blumensath, Andreas B
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+"u
+\end_inset 
+
+hmann, and Michael Zedler\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANminionpro}
+
+\end_inset 
+
+ which uses 
+\family typewriter 
+MnSymbol
+\family default 
+ requires a license from Adobe for the font MininonPro.
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:Compar}
+
+\end_inset 
+
+Comparison of Features
+\layout Standard
+
+Table\SpecialChar ~
+
+\begin_inset LatexCommand \ref{cap:FeatureComparison}
+
+\end_inset 
+
+ shows a comparison of the different features in each package.
+ The only packages that have optical sizes are Computer Modern, CM Bright,
+ Concrete, Euler, and MnSymbol.
+ Except for when the 
+\family typewriter 
+eulervm
+\family default 
+ package is used, Latin math letters are taken from the italic text font.
+ An asterisk after a font name indicates that the package has a version
+ of that style in its own font files.
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+begin{sidewaystable}
+\backslash 
+centering
+\backslash 
+small
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset  Tabular
+<lyxtabular version="3" rows="24" columns="8">
+<features>
+<column alignment="left" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<column alignment="center" valignment="top" width="0">
+<row topline="true" bottomline="true">
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+
+\begin_inset Formula $\;$
+\end_inset 
+
+Package
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Text
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Greek
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+CM sym
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+AMS sym
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Calligr
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+Blkbd
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+boldmath
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+computer modern
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cmbright
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cmbright
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cmbright
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+no
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ccfonts,eulervm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concrete
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+euler
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+euler
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+euler
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concmath
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concrete
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concrete
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concmath
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concmath
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concmath
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+concmath
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+no
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+iwona
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+iwona
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+iwona
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+iwona
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+iwona
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kurier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kurier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kurier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kurier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kurier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+anttor
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kmath,kerkis
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kerkis
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+kerkis
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+millennial
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+nc schlbk
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+millennial
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+no
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fouriernc
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+nc schlbk
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+pxfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+palatino
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+pxfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+pxfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathpazo
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+palatino
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+pazo
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+pazo
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathpple
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+palatino
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+euler
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+euler
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+times
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+txfonts
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathtime (Belleek)
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+times
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+belleek
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+belleek
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+no
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathptmx
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+times
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+symbol
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+rsfs
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+no
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mbtimes
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+omega
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+omega
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mbtimes
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+rsfs*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+esstix
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+arev
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+arev
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+arev
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathdesign (Charter)
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md charter
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+rsfs*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+comicsans
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+comicsans
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+comicsans
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+cm
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathdesign (Garamond)
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+garamond
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md garamond
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md garamond
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md garamond
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+rsfs*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row>
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+utopia
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+fourier
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+<row bottomline="true">
+<cell alignment="center" valignment="top" topline="true" leftline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+mathdesign (Utopia)
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+utopia
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md garamond
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md utopia
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+md utopia
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+rsfs*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+ams*
+\end_inset 
+</cell>
+<cell alignment="center" valignment="top" topline="true" leftline="true" rightline="true" usebox="none">
+\begin_inset Text
+
+\layout Standard
+
+yes
+\end_inset 
+</cell>
+</row>
+</lyxtabular>
+
+\end_inset 
+
+
+\layout Standard
+\align center 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Comparison of features]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{cap:FeatureComparison}
+
+\end_inset 
+
+Comparison of the features of different packages.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+end{sidewaystable}
+\end_inset 
+
+
+\layout Standard
+
+The only sans serif fonts with matching math fonts are CM Bright and Arev
+ Sans.
+ Both work well for presentations.
+ Computer Modern sans serif, CM Bright, Arev Sans, Bera Sans, Kerkis Sans,
+ Helvetica, and Avant Garde all work well as sans serif fonts that accompany
+ a primary roman font.
+ Computer Modern typewriter, 
+\family typewriter 
+txtt
+\family default 
+ (from txfonts), Luxi Mono\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANluximono}
+
+\end_inset 
+
+, and Bera Mono all work well as typewriters fonts.
+\layout Standard
+
+There are several other free fonts easily used in LaTeX, notably the Bera
+ fonts, Luxi Mono, and efont-serif\SpecialChar ~
+
+\begin_inset LatexCommand \cite{efont-serif}
+
+\end_inset 
+
+.
+ Malte Rosenau converted the Bitstream Vera fonts into Type\SpecialChar ~
+1 format, renaming
+ the fonts to Bera\SpecialChar ~
+
+\begin_inset LatexCommand \cite{CTANbera}
+
+\end_inset 
+
+.
+ Bera includes serif, sans, and mono.
+ Bera Serif does not have a matching italic font, but the DejaVu fonts\SpecialChar ~
+
+\begin_inset LatexCommand \cite{dejavu}
+
+\end_inset 
+
+ are an extension of Bitstream Vera that include a true serif italic, as
+ well as Greek and Cyrillic for all three styles.
+ Except for Bera Sans and Arev Sans, none of the previous fonts have matching
+ math fonts.
+\layout Section
+
+
+\begin_inset LatexCommand \label{sec:Creation}
+
+\end_inset 
+
+Creation of this Survey
+\layout Standard
+
+It might be technically feasible to create a font survey such as this article
+ as a single TeX document.
+ This document, however, was not created in that fashion for two reasons.
+ First, it would be an inordinate amount of work to switch between fonts
+ within the same document.
+ The authors of the LaTeX packages put in a considerable amount of effort
+ to set up the fonts for a document, and it would be silly to duplicate
+ their work.
+ Second, we want to show to a reader exactly what he or she will get by
+ using that package.
+\layout Standard
+
+In order to accomplish these goals, a small LaTeX file (see Figure\SpecialChar ~
+
+\begin_inset LatexCommand \ref{cap:SampleLaTeXfile}
+
+\end_inset 
+
+ for an example) was made for each font that loaded the appropriate packages
+ and then loaded a common text fragment for display.
+ Each file was LaTeXed and then converted to an EPS file using 
+\family typewriter 
+dvips
+\family default 
+ with the -E option.
+ The -E option creates a tight bounding box around the text.
+ The main file 
+\family typewriter 
+survey.tex
+\family default 
+ then included each of these graphics, and was compiled with 
+\family typewriter 
+pdflatex
+\family default 
+.
+ For some reason, 
+\family typewriter 
+dvips
+\family default 
+ created an unusable one-page PS file when including 
+\family typewriter 
+mbtimes.eps
+\family default 
+.
+ HeVeA was used to convert 
+\family typewriter 
+survey.tex
+\family default 
+ directly to HTML.
+\begin_inset Float figure
+wide false
+collapsed true
+
+\layout Quote
+
+
+\family typewriter 
+
+\backslash 
+documentclass{article}
+\newline 
+
+\backslash 
+include{sampleformat}
+\newline 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hspace*{.01em}
+\end_inset 
+
+\SpecialChar ~
+\SpecialChar ~
+
+\backslash 
+usepackage{fourier}
+\newline 
+
+\backslash 
+begin{document}
+\newline 
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+hspace*{.01em}
+\end_inset 
+
+\SpecialChar ~
+\SpecialChar ~
+
+\backslash 
+include{textfragment}
+\newline 
+
+\backslash 
+end{document}
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+captiontitle[Sample 
+\backslash 
+LaTeX{} file]{
+\end_inset 
+
+
+\begin_inset LatexCommand \label{cap:SampleLaTeXfile}
+
+\end_inset 
+
+Sample LaTeX file for 
+\family typewriter 
+fourier
+\family default 
+.
+ The file 
+\family typewriter 
+sampleformat.tex
+\family default 
+ contains page layout commands, such as setting the margins and removing
+ the page numbers.
+ The file 
+\family typewriter 
+textfragment.tex
+\family default 
+ contains the text and mathematics fragment to be displayed.
+ Both included files are used by every sample LaTeX file.
+ The line 
+\begin_inset Quotes eld
+\end_inset 
+
+
+\family typewriter 
+
+\backslash 
+usepackage{fourier}
+\family default 
+
+\begin_inset Quotes erd
+\end_inset 
+
+ was changed for each sample to the package listed in the sample's caption.
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+
+\end_inset 
+
+
+\layout Subsection*
+
+Acknowledgements
+\layout Standard
+
+Thanks to Michael Zedler, Ulrik Vieth, Karl Berry, William Slough, and the
+ anonymous referees for helpful comments.
+\layout Bibliography
+\bibitem {CTANfontinstgd}
+
+Philipp Lehman, The Font Installation Guide on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/info/Type1fonts/fontinstallationguide}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANmetatype1}
+
+Bogus
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+aw Jackowski, Janusz M.
+ Nowacki, and Piotr Strzelczyk, MetaType1 on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/utilities/metatype1}
+\end_inset 
+
+
+\layout Bibliography
+\bibitem {WASmathfonts}
+
+Walter A.
+ Schmidt, Mathematikschriften f
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+"u
+\end_inset 
+
+r LaTeX, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://home.vr-web.de/was/mathfonts.html}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {bluesky}
+
+American Mathematical Society (AMS) webpage for Computer Modern Type\SpecialChar ~
+1 fonts,
+ 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.ams.org/tex/type1-fonts.html}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CMBook}
+
+Donald E.
+ Knuth, 
+\emph on 
+Computer Modern Typefaces
+\emph default 
+, Addison-Wesley Pub.
+ Co., 1986.
+\layout Bibliography
+\bibitem {CMRgain}
+
+Raph Levien, Effect of gain on appearance of Computer Modern, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://levien.com/type/cmr/gain.html}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {DigTyp}
+
+Donald E.
+ Knuth, 
+\emph on 
+Digital Typography
+\emph default 
+, Stanford, California: Center for the Study of Language and Information,
+ 1999.
+\layout Bibliography
+\bibitem {CTANbluesky}
+
+Blue Sky Research and Y&Y, Inc., Computer Modern Type\SpecialChar ~
+1 fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/cm/ps-type1/bluesky}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANbakoma}
+
+Basil K.
+ Malyshev, BaKoMa Computer Modern Type\SpecialChar ~
+1 and TrueType fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/cm/ps-type1/bakoma}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANec}
+
+J
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+"o
+\end_inset 
+
+rg Knappen and Norbert Schwarz, European Computer Modern fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/ec}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANtt2001}
+
+Szab
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+ P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'e
+\end_inset 
+
+ter, Tt2001 fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/ps-type1/tt2001}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {textrace}
+
+Szab
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+ P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'e
+\end_inset 
+
+ter, webpage for 
+\family typewriter 
+textrace
+\family default 
+ and Tt2001 fonts, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.inf.bme.hu/~pts/textrace}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANcm-super}
+
+Vladimir Volovich, CM-Super on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/ps-type1/cm-super}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CM-Super}
+
+Vladimir Volovich, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb24-1/volovich.pdf}{
+\end_inset 
+
+CM-Super
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+: Automatic creation of efficient Type\SpecialChar ~
+1 fonts from 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ fonts, 
+\emph on 
+TUGboat
+\emph default 
+, 24 (1) 2003, 75--78.
+\layout Bibliography
+\bibitem {CTANlm}
+
+Bogus
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+aw Jackowski and Janusz M.
+ Nowacki, Latin Modern on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/ps-type1/lm}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {LatinModern}
+
+Bogus
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+aw Jackowski and Janusz M.
+ Nowacki, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb24-1/jackowski.pdf}{
+\end_inset 
+
+Latin Modern
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+: Enhancing Computer Modern with accents, accents, accents,
+\emph on 
+ TUGboat
+\emph default 
+, 24 (1) 2003, 64--74.
+\layout Bibliography
+\bibitem {texpower}
+
+TeXPower LaTeX style files by Stephan Lehmke, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://texpower.sourceforge.net}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANcmbright}
+
+Walter A.
+ Schmidt, CM Bright on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/cmbright}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANhfbright}
+
+Harald Harders, hfbright on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/ps-type1/hfbright}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {concretebook}
+
+Ronald L.
+ Graham, Donald E.
+ Knuth, and Oren Patashnik, 
+\emph on 
+Concrete Mathematics,
+\emph default 
+ Addison-Wesley, 1989.
+\layout Bibliography
+\bibitem {CTANconcmath}
+
+Ulrik Vieth, Concrete Math fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/concmath}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANccfonts}
+
+Walter Schmidt, ccfonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/macros/latex/contrib/ccfonts}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANeulervm}
+
+Walter Schmidt, eulervm on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/eulervm}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {eulervm}
+
+Walter Schmidt, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb23-3-4/tb75schmidt.pdf}{
+\end_inset 
+
+Euler-VM
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+: Generic math fonts for use with LaTeX, 
+\emph on 
+TUGboat
+\emph default 
+, 23 (3/4) 2002, 301--303.
+\layout Bibliography
+\bibitem {CTANiwona}
+
+Janusz M.
+ Nowacki, Iwona on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/iwona}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANkurier}
+
+Janusz M.
+ Nowacki, Kurier on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/kurier}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANantp}
+
+Janusz M.
+ Nowacki, Antykwa P
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+'o
+\end_inset 
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+l{}
+\end_inset 
+
+tawskiego on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/psfonts/polish/antp}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANantt}
+
+Janusz M.
+ Nowacki, Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/antt}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {AntTorunska}
+
+Janusz M.
+ Nowacki, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb19-3/tb60antyk.pdf}{
+\end_inset 
+
+Antykwa Toru
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+acuten{}
+\end_inset 
+
+ska
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+: an electronic replica of a Polish traditional type, 
+\emph on 
+TUGboat
+\emph default 
+, 19 (3) 1998, 242--243.
+\layout Bibliography
+\bibitem {CTANpsnfss}
+
+Sebastian Rahtz and Walter A.
+ Schmidt, PSNFSS on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/macros/latex/required/psnfss}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {Kerkis}
+
+Antonis Tsolomitis, The 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb23-3-4/tb75tsol.pdf}{
+\end_inset 
+
+Kerkis
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+ font family, 
+\emph on 
+TUGboat
+\emph default 
+, 23 (3/4) 2002, 296--301.
+\layout Bibliography
+\bibitem {CTANkerkis}
+
+Antonis Tsolomitis, Kerkis on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/greek/kerkis}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANfouriernc}
+
+Michael Zedler, fouriernc on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/fouriernc}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANpxfonts}
+
+Young Ryu, pxfonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/pxfonts}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANmathpazo}
+
+Diego Puga, Pazo Math fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/mathpazo}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANfpl}
+
+Ralf Stubner, FPL font on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/fpl}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {fplneu}
+
+Walter Schmidt, FPL Neu package, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://home.vr-web.de/was/x/FPL/}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANtxfonts}
+
+Young Ryu, txfonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/txfonts}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANbelleek}
+
+Richard Kinch, Belleek fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/belleek}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {Belleek}
+
+Richard J.
+ Kinch, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+TUGboat{tb19-3/tb60kinch.pdf}{
+\end_inset 
+
+Belleek
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+}
+\end_inset 
+
+: A call for 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+MF
+\backslash 
+ 
+\end_inset 
+
+ revival, 
+\emph on 
+TUGboat
+\emph default 
+, 19 (3) 1998, 244--249.
+\layout Bibliography
+\bibitem {STIX}
+
+STIX Fonts project, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.stixfonts.org}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {mbtimes}
+
+Michel Bovani, mbtimes at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{ftp://ftp.gutenberg.eu.org/pub/gut/distribs/mbtimes/}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {Omega}
+
+John Plaice and Yannis Haralambous, Omega at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://omega.enstb.org}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {MgOpenModerna}
+
+MgOpenModerna, one of the MgOpen fonts, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.ellak.gr/fonts/mgopen}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {FreeSans}
+
+FreeSans, one of the Free UCS Outline Fonts, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://savannah.nongnu.org/projects/freefont}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {vera}
+
+Bitstream Vera, released by Bitstream in cooperation with the Gnome Foundation,
+ 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.gnome.org/fonts}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANbera}
+
+Malte Rosenau, Bera Postscript Type\SpecialChar ~
+1 fonts (converted from Bitstream Vera
+ fonts, which necessitated the name change) and LaTeX support files by Walter\SpecialChar ~
+A.
+ Schmidt, on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/bera}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANarev}
+
+Tavmjong Bah and Stephen Hartke, Arev Sans on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/arev}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {arev}
+
+Tavmjong Bah, Arev Sans, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://tavmjong.free.fr/FONTS}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANcharter}
+
+Bitstream Charter on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/charter}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANmathdesign}
+
+Paul Pichaureau, Math Design fonts on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/mathdesign}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CharisSIL}
+
+Charis SIL, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=CharisSILfont}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {comicsans}
+
+Comic Sans, part of Microsoft's core web fonts, available at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://corefonts.sourceforge.net/}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANcomicsans}
+
+Scott Pakin, Comic Sans LaTeX package on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/macros/latex/contrib/comicsans}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANgaramond}
+
+URW Garamond on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/urw/garamond}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANutopia}
+
+Adobe Utopia on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/utopia}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANfourier}
+
+Michel Bovani, Fourier-GUTenberg on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/fourier-GUT}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANmnsymbol}
+
+Achim Blumensath, MnSymbol on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/mnsymbol}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANminionpro}
+
+Achim Blumensath, Andreas B
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+"u
+\end_inset 
+
+hmann, and Michael Zedler, MinionPro on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/minionpro}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {dejavu}
+
+DejaVu fonts, 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://dejavu.sourceforge.net}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {CTANluximono}
+
+Luxi Mono on 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+CTAN{/fonts/LuxiMono}
+\end_inset 
+
+.
+\layout Bibliography
+\bibitem {efont-serif}
+
+efont-serif at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://openlab.jp/efont/serif/}
+\end_inset 
+
+.
+\layout Comment
+
+Victor Gaultney, Gentium at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://scripts.sil.org/gentium}
+\end_inset 
+
+.
+\layout Comment
+
+Michael Zedler, gentium at 
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+
+\backslash 
+url{http://www.hft.ei.tum.de/mz/ggn.tar.bz2}
+\end_inset 
+
+.
+\layout Standard
+
+
+\begin_inset ERT
+status Collapsed
+
+\layout Standard
+%filler to avoid comment environment as last line
+\end_inset 
+
+
+\the_end
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.tex
new file mode 100644
index 00000000000..45f56d9960c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/survey.tex
@@ -0,0 +1,1148 @@
+%% LyX 1.3 created this file.  For more info, see http://www.lyx.org/.
+%% Do not edit unless you really know what you are doing.
+\documentclass[12pt,english]{article}
+\usepackage[T1]{fontenc}
+\usepackage[latin1]{inputenc}
+
+\makeatletter
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% LyX specific LaTeX commands.
+%% Bold symbol macro for standard LaTeX users
+\newcommand{\boldsymbol}[1]{\mbox{\boldmath $#1$}}
+
+%% Because html converters don't know tabularnewline
+\providecommand{\tabularnewline}{\\}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Textclass specific LaTeX commands.
+ \usepackage{verbatim}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
+
+%PracTEXreplacement
+
+% LyX includes graphicx if any pictures are used; so put in ERT boxes
+\usepackage[pdftex]{graphicx}
+\usepackage{epstopdf}
+
+%\usepackage{cite} % numerically sorts multiple references contained in one citation
+
+\usepackage{url} % don't let LyX do this, because IfFileExists confuses HeVeA
+
+\setlength{\fboxsep}{.25in}
+
+\usepackage{array}
+\setlength\extrarowheight{1pt}
+
+\usepackage{color,hyperref}
+\definecolor{linkcolour}{rgb}{0,0.2,0.6}
+\hypersetup{
+  pdfauthor = {Stephen G. Hartke},
+  pdftitle = {A Survey of Free Math Fonts for LaTeX},
+  pdfsubject = {free math fonts for LaTeX},
+  pdfkeywords = {LaTeX, TeX, math font, free},
+  pdfcreator = {LaTeX with hyperref package},
+  pdfproducer = {pdflatex},
+  pdfview = FitH,
+  pdfstartview = FitH,
+  linkcolor = linkcolour, % colors don't work?
+  citecolor = linkcolour,
+  filecolor = linkcolour,
+  urlcolor = linkcolour,
+  pagecolor = linkcolour,
+  colorlinks
+}
+
+\usepackage{ifthen}
+\usepackage{hevea}
+\ifthenelse{\boolean{hevea}}
+{
+  \newcommand{\l}{\begin{rawhtml}&#322;\end{rawhtml}}
+  \newcommand{\acuten}{\begin{rawhtml}&#324;\end{rawhtml}}
+  %\newcommand{\textbackslash}{\begin{rawhtml}&#92;\end{rawhtml}}
+  \newcommand{\captiontitle}[2][dummy]{\caption{#2}}
+  \newcommand{\captionbreak}{}
+  \newenvironment{sidewaystable}{\begin{table}}{\end{table}}
+  \renewcommand{\LaTeX}{LaTeX}  % looks silly in HTML
+  \renewcommand{\TeX}{TeX}
+  \newcommand{\MF}{METAFONT}
+  \newcommand{\pic}[1]
+     {\begin{center}
+         \begin{rawhtml}<table align="center" border="1"><tr><td width="0" align="center"><img src="\end{rawhtml}images/#1.png\begin{rawhtml}"></td></tr></table>\end{rawhtml}
+      \end{center}}
+  \renewcommand{\@figrule}{}  % no hrule around floats
+ % fixes colors
+ \htmlhead{\begin{rawhtml}
+  <title>A Survey of Free Math Fonts for TeX and LaTeX</title>
+  <style type="text/css">
+    BODY { background-color: white; color: black; }
+    A:link { color: #003399; text-decoration: none; }
+    A:active { color: blue; text-decoration: underline; }
+    A:visited { color: #003399; text-decoration: none; }
+    A:hover { color: blue; text-decoration: underline; }
+    H5 {font-size: 110\%;  font-weight: bold; }
+  </style>\end{rawhtml}}
+  \title{A Survey of Free Math Fonts for \TeX{} and \LaTeX{}%
+  \footnote{Copyright 2006 Stephen G.\  Hartke. Permission is granted to distribute verbatim or modified copies of this document provided this notice remains intact.\protect \\ An initial version of this article appeared in \emph{The Prac\TeX{} Journal,} 1, 2006,  \protect\url{http://www.tug.org/pracjourn/2006-1/hartke/}.\protect \\
+The permanent home of this article is \protect\url{http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey}.}}
+  \author{Stephen G. Hartke\footnote{Email: lastname @ gmail dot com.}}
+  \date{May 5, 2006}
+}
+{
+  \usepackage[letterpaper,text={6.5in,9in}]{geometry}
+  \usepackage{palatino}\renewcommand{\ttdefault}{txtt}
+  \usepackage{rotating} % to rotate large table
+  \newcommand{\acuten}{\'n}
+  \newcommand{\pic}[1]
+        %{\hspace*{-\fboxsep}\framebox{\includegraphics{#1.eps}}} % for PracTeX
+        {\framebox{\includegraphics{#1.eps}}}
+  \usepackage{topcapt}  % put captions above figures
+  %\setlength{\abovecaptionskip}{0pt}
+  \newcommand{\captiontitle}[2][]{\topcaption{#2}}
+  \DeclareRobustCommand\captionbreak{\\\hspace*{\fill}}
+  \@ifundefined{MF}{\newcommand{\MF}{METAFONT}} % defined by practex, but not by others
+}
+
+
+\newcommand{\CTAN}[1]{%
+  \ifthenelse{\boolean{hevea}}% HeVeA does not allow parameters in href
+  {\ahref{http://ctan.tug.org/tex-archive#1/}{CTAN:\texttt{#1}}}%
+  {\href{http://ctan.tug.org/tex-archive#1/}{CTAN:\texttt{#1}}}%
+}
+\newcommand{\TUGboat}[2]{%
+  \ifthenelse{\boolean{hevea}}%
+  {\ahref{http://www.tug.org/TUGboat/Articles/#1}{#2}}%
+  {\href{http://www.tug.org/TUGboat/Articles/#1}{#2}}%
+}
+
+\usepackage{babel}
+\makeatother
+\begin{document}
+
+\title{A Survey of Free Math Fonts for \TeX{} and \LaTeX{}%
+\footnote{Copyright 2006 Stephen G.\  Hartke. Permission is granted to distribute
+verbatim or modified copies of this document provided this notice
+remains intact.\protect \\
+An initial version of this article appeared in \emph{The Prac\TeX{}
+Journal,} 1, 2006, \url{http://www.tug.org/pracjourn/2006-1/hartke/}.\protect \\
+The permanent home of this article is \url{http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey}.%
+}}
+
+
+\author{Stephen G. Hartke%
+\footnote{Email: lastname @ gmail dot com.%
+}}
+
+
+\date{May 5, 2006}
+
+\maketitle
+\begin{comment}
+The title, author, and date are in the preamble for HeVeA.
+\end{comment}
+\begin{htmlonly}
+
+\textbf{Note:} \emph{This survey is also available in \href{survey.pdf}{PDF}
+format.}\medskip
+
+\end{htmlonly}
+
+
+\section*{Contents}
+
+\noindent \hyperref[sec:Intro]{\textbf{Introduction}}\begin{latexonly}\hfill\textbf{\pageref{sec:Intro}}\end{latexonly}
+
+\noindent \hyperref[sec:TeXFonts]{\textbf{Fonts Originally Designed
+for \TeX{}}}\begin{latexonly}\hfill\textbf{\pageref{sec:TeXFonts}}\end{latexonly}
+
+\begin{quote}
+\hyperref[fig:CM]{Computer Modern}, \hyperref[fig:CMBright]{CM
+Bright}, \hyperref[fig:ConcEuler]{Concrete and Euler}, \hyperref[fig:ConcMath]{Concrete
+Math}, \hyperref[fig:Iwona]{Iwona}, \hyperref[fig:Kurier]{Kurier},
+\hyperref[fig:AntPolt]{Antykwa P\'o\l{}tawskiego}, \hyperref[fig:AntTor]{Antykwa
+Toru\acuten{}ska}
+\end{quote}
+\noindent \hyperref[sec:PSFonts]{\textbf{Core Postscript Fonts}}\begin{latexonly}\hfill\textbf{\pageref{sec:PSFonts}}\end{latexonly}
+
+\begin{quote}
+\hyperref[fig:Kerkis]{Kerkis}, \hyperref[fig:Millen]{Millennial},
+\hyperref[fig:fouriernc]{fouriernc}, \hyperref[fig:pxfonts]{pxfonts},
+\hyperref[fig:Pazo]{Pazo}, \hyperref[fig:mathpple]{mathpple},
+\hyperref[fig:txfonts]{txfonts}, \hyperref[fig:Belleek]{Belleek},
+\hyperref[fig:mathptmx]{mathptmx}, \hyperref[fig:mbtimes]{mbtimes}
+\end{quote}
+\noindent \hyperref[sec:OtherFonts]{\textbf{Other Free Fonts}}\begin{latexonly}\hfill\textbf{\pageref{sec:OtherFonts}}\end{latexonly}
+
+\begin{quote}
+\hyperref[fig:Arev]{Arev Sans}, \hyperref[fig:chartermd]{Math Design
+with Charter}, \hyperref[fig:comicsans]{Comic Sans}, \hyperref[fig:garamd]{Math
+Design with Garamond}, \hyperref[fig:fourier]{Fourier-GUTenberg},
+\hyperref[fig:utopiamd]{Math Design with Utopia}
+\end{quote}
+\noindent \hyperref[sec:Compar]{\textbf{Comparison of Features}}\begin{latexonly}\hfill\textbf{\pageref{sec:Compar}}\end{latexonly}
+
+\noindent \hyperref[sec:Creation]{\textbf{Creation of this Survey}}\begin{latexonly}\hfill\textbf{\pageref{sec:Creation}}\end{latexonly}
+
+
+\section{\label{sec:Intro}Introduction}
+
+One of the biggest challenges in selecting a font for \TeX{} or \LaTeX{}
+is that there are not very many math fonts that match the plethora
+of available text fonts. It's reasonably easy to use an arbitrary
+Postscript Type~1 font in \TeX{} for text (see Philipp Lehman's Font
+Installation Guide~\cite{CTANfontinstgd}), but obtaining and configuring
+a matching math font from scratch is a demanding task. Thus, there
+are few math fonts for \TeX{}, and in particular very few free ones.
+However, in the past few years, several very nice free fonts have
+been released. The goal of this article is to list all of the free
+math fonts and to provide examples.
+
+{}``Free'' here means fonts that are free to use (both commercially
+and non-com\-mercially) and free to distribute, but not necessarily
+free to modify. I also am biased towards listing fonts that have outline
+versions in PostScript Type~1 format suitable for embedding in Postscript
+PS or Adobe Acrobat PDF files. Donald E. Knuth originally designed
+the \MF\  system for producing fonts for \TeX{} in bitmap format.
+PS or PDF files that have embedded bitmap fonts do not display well
+in Adobe Acrobat Reader,%
+\footnote{Starting with version 6, Adobe Acrobat Reader displays bitmap fonts
+fine. The free PDF viewers Ghostview and xpdf have always displayed
+bitmap fonts accurately.%
+} to the point of being almost unreadable on the screen, and are also
+noticeable when printing at extremely high resolutions (on photo-setters,
+for instance). Since outline fonts contain mathematical descriptions
+of the curves used in each glyph, they can be scaled to any resolution
+while retaining image quality.
+
+The fonts listed here are categorized according to their origin: whether
+originally designed for \TeX{}, related to the standard Postscript
+fonts, or other free fonts. A font's origin does not particularly
+bear on its quality or suitability for typesetting mathematics. No
+recommendations or evaluations of the fonts are given here, as people's
+tastes in fonts vary greatly. The goal of this survey is simply to
+make authors aware of all their options.
+
+Most of the fonts can be selected by including a single package in
+the preamble of the user's \LaTeX{} file (the \emph{preamble} is the
+section after {}``\texttt{\textbackslash{}documentclass\{\}}'' and
+before {}``\texttt{\textbackslash{}begin\{document\}}''). The line
+or lines to include for each font are listed in the caption of the
+sample figure. For example {}``\texttt{\textbackslash{}usepackage\{fourier\}}''
+uses Utopia and Fourier-GUTenberg, as shown in the sample \LaTeX{}
+file in Section~\ref{sec:Creation}.
+
+Walter A. Schmidt also has a survey in German of math fonts~\cite{WASmathfonts}
+that concentrates more on commercial fonts. Schmidt's survey has several
+examples that show different pairings between text fonts and math
+fonts.
+
+
+\section{\label{sec:TeXFonts}Fonts Originally Designed for \TeX{}}
+
+These fonts were originally designed for use with \TeX{}, using either
+\MF\  or MetaType1~\cite{CTANmetatype1}.
+
+
+\paragraph{Computer Modern:}
+
+Knuth created Computer Modern~\cite{CMBook} as the default font
+for \TeX{}. The font set includes serif, sans serif, and monospaced
+text faces, and corresponding math fonts. The math symbol set is very
+complete. Computer Modern is \emph{the} font for \TeX{}, which leads
+some to claim that the font is overused. The characters are fairly
+thin and light, and so are not as readable on screen in small sizes
+or from high-resolution laser printers.%
+\footnote{When on screen, the fonts are usually anti-aliased, often into a gray
+blur because the stems are not thick enough to fill a pixel. When
+printed with a high-resolution laser printer, the fonts are shown
+accurately, but I think are too thin. With a medium-resolution printer
+like an inkjet, there's enough resolution to show the form of the
+letters (unlike on screen), but the low-resolution \char`\"{}bulks
+up\char`\"{} the letters compared to a high-resolution laser printer,
+with the letters thus appearing darker.%
+} In a comparison by Raph Levien~\cite{CMRgain}, the printing in
+Knuth's \emph{Digital Typography}~\cite{DigTyp} is heavier than
+the digital version or from a laser printer.
+
+Type~1 versions of Computer Modern from Blue Sky Research and Y\&Y,
+Inc. have been made freely available by the American Mathematical
+Society (AMS) and a collection of publishers and other technical companies~\cite{CTANbluesky,bluesky}.
+Basil K. Malyshev has also released a free Type~1 version of Computer
+Modern~\cite{CTANbakoma}, originally for use with his \TeX{} system
+BaKoMa \TeX{}.
+
+Computer Modern has been extended to include more characters, particularly
+for non-English European languages. These fonts include European Computer
+Modern by J\"org Knappen and Norbert Schwarz (\MF\  only) \cite{CTANec};
+Tt2001 by Szab\'o P\'eter (converted into Type~1 format from \MF\ 
+sources using \texttt{textrace}; Tt2001 has been superseded by CM-Super,
+which P\'eter recommends) \cite{textrace,CTANtt2001}; CM-Super by
+Vladimir Volovich (also converted using \texttt{textrace}) \cite{CM-Super,CTANcm-super};
+and Latin Modern by Bogus\l{}aw Jackowski and Janusz M. Nowacki (extended
+from the Blue Sky AMS fonts using MetaType1) \cite{LatinModern,CTANlm}. 
+
+The Sli\TeX{} font (\texttt{lcmss}) is a sans serif text face that
+has wide letters and high \emph{x} height. Its high readability makes
+it extremely suitable for slide presentations. However, there is no
+matching math font. Sli\TeX{} sans serif can be set as the primary
+text font using \TeX{}Power's \texttt{tpslifonts.sty}~\cite{texpower}.%
+\begin{figure*}
+\captiontitle[Computer Modern]{\label{fig:CM}Computer Modern (using
+the Blue Sky and Y\&Y Type~1 fonts; no package necessary).}
+
+\pic{cm}
+\end{figure*}
+ 
+
+
+\paragraph{Computer Modern Bright: }
+
+This a sans serif font with corresponding math font derived from Computer
+Modern by Walter A. Schmidt \cite{CTANcmbright}. CM-Super contains
+Type~1 versions of the text fonts in T1 encoding, and Harald Harders
+created Type~1 versions of the text and math fonts called \texttt{hfbright}~\cite{CTANhfbright}
+using \texttt{mftrace}. %
+\begin{figure*}
+\captiontitle[CM Bright]{\label{fig:CMBright}CM Bright (\texttt{\textbackslash{}usepackage\{cmbright\}};
+output uses the \texttt{hfbright} fonts).}
+
+\pic{cmbright}
+\end{figure*}
+
+
+
+\paragraph{Concrete and Euler or Concrete Math:}
+
+The Concrete font was created by Knuth for his book \emph{Concrete
+Mathematics}~\cite{concretebook}. Hermann Zapf was commissioned
+by the AMS to create the math font Euler for use in \emph{Concrete
+Mathematics}. Type~1 versions of Concrete in T1 encoding are available
+in the CM-Super collection~\cite{CTANcm-super}, and Type~1 versions
+of Euler are available in the Blue Sky collection from the AMS~\cite{CTANbluesky}
+and in the BaKoMa collection~\cite{CTANbakoma}. The \texttt{eulervm}
+package by Walter Schmidt~\cite{CTANeulervm,eulervm} implements
+virtual fonts for Euler that are more efficient to use with \LaTeX{}.
+Ulrik Vieth created the Concrete Math fonts~\cite{CTANconcmath}
+to match the Concrete text fonts; the only free versions are implemented
+in \MF. The \texttt{ccfonts} package by Walter Schmidt~\cite{CTANccfonts}
+changes the text font to Concrete and changes the math font to the
+Concrete Math fonts if \texttt{eulervm} is not loaded. %
+\begin{figure*}
+\captiontitle[Concrete and Euler]{\label{fig:ConcEuler}Concrete
+text with Euler math (\texttt{\textbackslash{}usepackage\{ccfonts,eulervm\}
+\textbackslash{}usepackage{[}T1{]}\{fontenc\}}). Note that Concrete
+does not have a bold font, so Computer Modern is used instead. Non-bold
+text output uses the CM-Super Concrete fonts.}
+
+\pic{concrete}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[Concrete Math]{\label{fig:ConcMath}Concrete text with
+Concrete math (\texttt{\textbackslash{}usepackage\{ccfonts\} \textbackslash{}usepackage{[}T1{]}\{fontenc\}}).
+Note that Concrete does not have a bold font, so Computer Modern is
+used instead. Non-bold text output uses the CM-Super Concrete fonts.}
+
+\pic{concmath}
+\end{figure*}
+
+
+
+\paragraph{Iwona and Kurier:}
+
+The fonts Iwona and Kurier were created by J. M. Nowacki~\cite{CTANiwona,CTANkurier}
+using the MetaType1 system based on typefaces by the Polish typographer
+Ma\l{}gorzata Budyta. The two fonts are very similar, except that
+Kurier avoids {}``ink traps'' with gaps in its strokes. The packages
+have complete math support in both \TeX{} and \LaTeX{}. %
+\begin{figure*}
+\captiontitle[Iwona]{\label{fig:Iwona}Iwona text and math (\texttt{\textbackslash{}usepackage{[}math{]}\{iwona\}}).}
+
+\pic{iwona}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[Kurier]{\label{fig:Kurier}Kurier text and math (\texttt{\textbackslash{}usepackage{[}math{]}\{kurier\}}).}
+
+\pic{kurier}
+\end{figure*}
+
+
+
+\paragraph{Antykwa P\'o\l{}tawskiego:}
+
+J. M. Nowacki created the font Antykwa P\'o\l{}tawskiego~\cite{CTANantp}
+using the MetaType1 system based on a typeface by Polish typographer
+Adam P\'o\l{}tawski. The package \texttt{antpolt} has no math support
+at this time, and requires the encoding to be set to QX or OT4. %
+\begin{figure*}
+\captiontitle[Antykwa P\'o\l{}tawskiego]{\label{fig:AntPolt}Antykwa
+P\'o\l{}tawskiego text (\texttt{\textbackslash{}usepackage\{antpolt\}}
+and \texttt{\textbackslash{}usepackage{[}QX{]}\{fontenc\}}).}
+
+\pic{antpolt}
+\end{figure*}
+
+
+
+\paragraph{Antykwa Toru\acuten{}ska:}
+
+The font Antykwa Toru\acuten{}ska was created by J. M. Nowacki~\cite{AntTorunska,CTANantt}
+using the MetaType1 system based on a typeface by the Polish typographer
+Zygfryd Gardzielewski. The package \texttt{anttor} has complete math
+support in both \TeX{} and \LaTeX{}. %
+\begin{figure*}
+\captiontitle[Antykwa Toru\'nska]{\label{fig:AntTor}Antykwa Toru\acuten{}ska
+text and math (\texttt{\textbackslash{}usepackage{[}math{]}\{anttor\}}).}
+
+\pic{anttor}
+\end{figure*}
+
+
+
+\section{\label{sec:PSFonts}Core Postscript Fonts}
+
+When Adobe introduced Postscript in 1984, they defined 35 core fonts
+(in 10 typefaces) that must be present in all Postscript interpreters.
+In 1996, URW++ released a replacement set for the core fonts under
+the GNU General Public License. The URW++ fonts were primarily released
+for use with Ghostscript, a free Postscript interpreter. Table~\ref{cap:CorePostscriptFonts}
+lists the original Postscript fonts, along with the URW++/Ghostscript
+equivalents. Each font can be used as the default text font by selecting
+the indicated \LaTeX{} package from the PSNFSS distribution~\cite{CTANpsnfss}.%
+\begin{table}
+\begin{center}\begin{tabular}{cccc}
+\hline 
+Adobe Postscript&
+URW++/Ghostscript&
+\# of fonts&
+package\tabularnewline
+\hline
+Avant Garde&
+URW Gothic L&
+4&
+\texttt{avant}\tabularnewline
+Bookman&
+URW Bookman L&
+4&
+\texttt{bookman}\tabularnewline
+Courier&
+Nimbus Mono L&
+4&
+\texttt{courier}\tabularnewline
+Helvetica&
+Nimbus Sans L&
+8&
+\texttt{helvet}\tabularnewline
+New Century Schoolbook&
+Century Schoolbook L&
+4&
+\texttt{newcent}\tabularnewline
+Palatino&
+URW Palladio L&
+4&
+\texttt{palatino}\tabularnewline
+Symbol&
+Standard Symbols L&
+1&
+---\tabularnewline
+Times&
+Nimbus Roman No.\ 9 L&
+4&
+\texttt{times}\tabularnewline
+Zapf Chancery&
+URW Chancery L&
+1&
+\texttt{chancery}\tabularnewline
+Zapf Dingbats&
+Dingbats&
+1&
+---\tabularnewline
+\hline
+\end{tabular}\end{center}
+
+\begin{center}\captiontitle[Core Postscript fonts]{\label{cap:CorePostscriptFonts}Core
+Postscript fonts and URW++/Ghostscript equivalents.}\end{center}
+\end{table}
+ 
+
+
+\paragraph{Avant Garde and Kerkis Sans:}
+
+The font Kerkis Sans was created by Antonis Tsolomitis~\cite{Kerkis,CTANkerkis}
+by extending Avant Garde to include Greek and additional Latin characters.
+The resulting fonts are stand-alone and can be used by applications
+outside of \TeX{}. The package \texttt{kerkis} sets the sans serif
+font to Kerkis Sans; there is no package option to set Kerkis Sans
+to be the primary text font.
+
+
+\paragraph{Bookman and Kerkis:}
+
+The font Kerkis was created by Antonis Tsolomitis~\cite{Kerkis,CTANkerkis}
+by extending URW Bookman~L to include Greek and additional Latin
+characters. The resulting fonts are stand-alone and can be used by
+applications outside of \TeX{}. A font of math symbols is included,
+but not used by the \LaTeX{} package. The package \texttt{kmath} uses
+txfonts for math symbols and uppercase Greek letters. %
+\begin{figure*}
+\captiontitle[Kerkis]{\label{fig:Kerkis}Kerkis text and math (\texttt{\textbackslash{}usepackage\{kmath,kerkis\}};
+the order of the packages matters, since \texttt{kmath} loads the
+\texttt{txfonts} package which changes the default text font).}
+
+\pic{kerkis}
+\end{figure*}
+
+
+
+\paragraph{New Century Schoolbook and Millennial or fouriernc: }
+
+The Millennial math font of the current author contains Greek letters
+and other letter-like mathematical symbols. A set of virtual fonts
+is provided that uses New Century Schoolbook for Latin letters in
+math, Millennial for Greek and other letter-like symbols, and txfonts
+and Computer Modern for all other symbols, including binary operators,
+relations, and large symbols. This font is still in development, but
+will hopefully be released in 2006. The \texttt{fouriernc} package
+of Michael Zedler~\cite{CTANfouriernc} uses New Century Schoolbook
+for text and Latin letters in mathematics, and the Greek and symbol
+fonts from the Fourier-GUTenberg package for the remaining mathematical
+symbols. %
+\begin{figure*}
+\captiontitle[Millennial]{\label{fig:Millen}New Century Schoolbook
+with Millennial math \captionbreak (\texttt{\textbackslash{}usepackage\{millennial\}}).}
+
+\pic{millennial}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[fouriernc]{\label{fig:fouriernc}New Century Schoolbook
+with Fourier math \captionbreak (\texttt{\textbackslash{}usepackage\{fouriernc\}}).}
+
+\pic{fouriernc}
+\end{figure*}
+
+
+
+\paragraph{Palatino and pxfonts, Pazo, or mathpple:}
+
+Young Ryu created the pxfonts collection~\cite{CTANpxfonts}, which
+contains Greek and other letter-like symbols, as well as a complete
+set of geometric symbols, including the AMS symbols. Diego Puga created
+the Pazo math fonts, which include the Greek letters and other letter-like
+symbols in a style that matches Palatino. The \LaTeX{} package \texttt{mathpazo}
+(now part of PSNFSS~\cite{CTANpsnfss}) uses Palatino for Latin letters,
+Pazo for Greek and other letter-like symbols, and Computer Modern
+for geometric symbols. The \LaTeX{} package \texttt{mathpple} (also
+part of PSNFSS~\cite{CTANpsnfss}) uses Palatino for Latin letters
+and slanted Euler for Greek and other symbols. Since Hermann Zapf
+designed both Palatino and Euler, the designs mesh well. An alternate
+use of Euler is using the \texttt{eulervm} package. Ralf Stubner added
+small caps and old-style figures to URW Palladio L in the FPL package~\cite{CTANfpl},
+and Walter Schmidt extended these fonts in the FPL Neu package~\cite{fplneu}.
+%
+\begin{figure*}
+\captiontitle[pxfonts]{\label{fig:pxfonts}Palatino text with pxfonts
+math (\texttt{\textbackslash{}usepackage\{pxfonts\}}).}
+
+\pic{pxfonts}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[Pazo]{\label{fig:Pazo}Palatino text with Pazo math
+(\texttt{\textbackslash{}usepackage\{mathpazo\}}).}
+
+\pic{pazo}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[mathpple]{\label{fig:mathpple}Palatino text with Euler
+math (\texttt{\textbackslash{}usepackage\{mathpple\}}).}
+
+\pic{mathpple}
+\end{figure*}
+
+
+
+\paragraph{Times and txfonts, Belleek, mathptmx, or mbtimes:}
+
+Young Ryu created the txfonts collection~\cite{CTANtxfonts}, which
+contains Greek and other letter-like symbols, as well as a complete
+set of geometric symbols, including the AMS symbols. The \texttt{txfonts}
+package also includes a very nice typewriter font, \texttt{txtt}.
+Belleek was created by Richard Kinch~\cite{CTANbelleek,Belleek}
+and is a drop-in replacement for the commercial fonts required by
+the \texttt{mathtime} package (now part of PSNFSS~\cite{CTANpsnfss}).
+The \LaTeX{} package \texttt{mathptmx} (also part of PSNFSS~\cite{CTANpsnfss})
+uses Times for Latin letters and Symbol for Greek and other symbols.
+Michel Bovani created the \texttt{mbtimes} package by using Omega
+Serif for text and Latin and Greek letters in mathematics. \texttt{mbtimes}
+also includes symbol fonts and a set of calligraphic letters. Omega
+Serif is the primary font for Omega, a 16-bit extension of \TeX{}
+by John Plaice and Yannis Haralambous~\cite{Omega}.
+
+The STIX fonts project~\cite{STIX} is a collaboration of several
+academic publishers to create a set of Times-compatible fonts containing
+every possible glyph needed for mathematical and technical publishing.
+These fonts are still in development, with a scheduled release in
+the middle of 2006.
+
+Note that Adobe Reader 7.0 replaces Times with Adobe Serif MM if Times
+or the Ghostscript equivalent Nimbus Roman No.\ 9 L is not embedded
+in the PDF file. Adobe Serif MM only has an oblique version, not a
+real italics, and thus, the primary text and Latin letters in mathematics
+will not match letters taken from additional fonts. This problem can
+be avoided by embedding Times or the Ghostscript equivalent Nimbus
+Roman No.\ 9 L into the PDF file. Also, I have heard (but not personally
+verified) that the Windows version of Adobe Reader displays Times
+New Roman when Times is not embedded. The upright versions of the
+two typefaces are very similar, but the italics are noticeably different
+(consider the \emph{z}, for instance). %
+\begin{figure*}
+\captiontitle[txfonts]{\label{fig:txfonts}Times text with txfonts
+math (\texttt{\textbackslash{}usepackage{[}varg{]}\{txfonts\}}).}
+
+\pic{txfonts}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[Belleek]{\label{fig:Belleek}Times text with Belleek
+math (\texttt{\textbackslash{}usepackage\{mathtime\}}; output uses
+the Belleek fonts).}
+
+\pic{belleek}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[mathptmx]{\label{fig:mathptmx}Times text with Symbol
+math (\texttt{\textbackslash{}usepackage\{mathptmx\}}).}
+
+\pic{mathptmx}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[mbtimes]{\label{fig:mbtimes}Omega Serif text with
+Omega math (\texttt{\textbackslash{}usepackage\{mbtimes\}}).}
+
+\pic{mbtimes}
+\end{figure*}
+
+
+\bigskip{}
+Helvetica, Courier, and Zapf Chancery do not have matching math fonts.
+Courier and Zapf Chancery are inappropriate for mathematics anyway,
+but Helvetica is sometimes used for presentations and posters. The
+free fonts MgOpenModerna~\cite{MgOpenModerna} and FreeSans~\cite{FreeSans}
+would be natural choices for the Greek letters in a Helvetica mathematics
+font.
+
+
+\section{\label{sec:OtherFonts}Other Free Fonts}
+
+Several other fonts have been released for use with free open-source
+software. \LaTeX{} packages have been created for most of these fonts.
+
+
+\paragraph{Bitstream Vera Sans and Arev Sans:}
+
+Bitstream Vera was released by Bitstream in cooperation with the Gnome
+Foundation~\cite{vera} as a high quality scalable free font for
+use with free open-source software. Bitstream Vera serif, sans serif,
+and sans mono are available in text using the \texttt{bera} package
+by Malte Rosenau and Walter~A. Schmidt~\cite{CTANbera}. Tavmjong
+Bah created Arev Sans~\cite{arev} by extending Bitstream Vera Sans
+to include Greek, Cyrillic, and many mathematical symbols. The current
+author created the \LaTeX{} package \texttt{arev}~\cite{CTANarev}
+using Arev Sans for text and math letters and bold Math Design fonts
+for Bitstream Charter for symbols. %
+\begin{figure*}
+\captiontitle[Arev Sans]{\label{fig:Arev}Arev Sans text with Arev
+math (\texttt{\textbackslash{}usepackage\{arev\}}).}
+
+\pic{arev}
+\end{figure*}
+
+
+
+\paragraph{Bitstream Charter and Math Design:}
+
+Bitstream Charter~\cite{CTANcharter} was donated by Bitstream for
+use with X Windows. The Math Design fonts for Bitstream Charter created
+by Paul Pichaureau~\cite{CTANmathdesign} are very complete, including
+Greek letters, symbols from Computer Modern, and the AMS symbols.
+Charis SIL~\cite{CharisSIL} might be an alternate source for Greek
+letters that match Bitstream Charter more closely. Another possibility
+for a math font is to use the Euler fonts with the \texttt{charter}
+and \texttt{eulervm} packages.%
+\begin{figure*}
+\captiontitle[Math Design for Charter]{\label{fig:chartermd}Bitstream
+Charter text with Math Design math \captionbreak (\texttt{\textbackslash{}usepackage{[}charter{]}\{mathdesign\}}).}
+
+\pic{chartermd}
+\end{figure*}
+
+
+
+\paragraph{Comic Sans:}
+
+Comic Sans is one of Microsoft's core web fonts that is freely available~\cite{comicsans}.
+The \texttt{comicsans} package by Scott Pakin~\cite{CTANcomicsans}
+implements Comic Sans as both the primary text font and the Latin
+and Greek letters in mathematics. Computer Modern is used for geometric
+symbols that are not present in Comic Sans. Comic Sans is hard to
+read for large blocks of text, but might be nice to use for short
+comments in a handwriting style.%
+\begin{figure*}
+\captiontitle[Comic Sans]{\label{fig:comicsans}Comic Sans text and
+math (\texttt{\textbackslash{}usepackage\{comicsans\}}).}
+
+\pic{comicsans}
+\end{figure*}
+
+
+\begin{comment}
+Gentium not released yet.
+
+\paragraph{Gentium: }
+
+Gentium was designed by Victor Gaultney~\cite{Gentium} to be suitable
+for any language that uses a Latin-based script. Gentium was released
+by SIL under the Open Font License. Michael Zedler converted Gentium
+to Type~1 format and produced a \LaTeX{} package~\cite{Gentiumtex}%
+\footnote{This package is currently in development; when completed it will presumably
+be posted somewhere more official.%
+} for its use; the mathematics uses Gentium for Latin and Greek letters
+and MnSymbol for geometric symbols. %
+\begin{figure*}
+\captiontitle[Gentium]{\label{fig:Gentium}Gentium text with Gentium
+math (\texttt{\textbackslash{}usepackage\{gentium\}}).}
+
+\pic{gentium}
+\end{figure*}
+
+
+\end{comment}
+
+\paragraph{URW Garamond and Math Design: }
+
+URW Garamond No.~8~\cite{CTANgaramond} is available under the Aladdin
+Free Public License as part of the GhostPCL project. The Math Design
+fonts for URW Garamond created by Paul Pichaureau~\cite{CTANmathdesign}
+are very complete, including Greek letters, symbols from Computer
+Modern, and the AMS symbols.%
+\begin{figure*}
+\captiontitle[Math Design for Garamond]{\label{fig:garamd}URW Garamond
+text with Math Design math \captionbreak (\texttt{\textbackslash{}usepackage{[}garamond{]}\{mathdesign\}}).}
+
+\pic{garamondmd}
+\end{figure*}
+
+
+
+\paragraph{Utopia and Fourier or Math Design:}
+
+Utopia~\cite{CTANutopia} was donated by Adobe for use with X Windows.
+Michel Bovani created Fourier-GUTenberg~\cite{CTANfourier} as an
+accompaniment to Utopia and is very complete, containing both Greek
+letters and standard and AMS symbols. The Math Design fonts for Utopia
+of Paul Pichaureau~\cite{CTANmathdesign} are also very complete,
+including Greek letters and AMS symbols.%
+\begin{figure*}
+\captiontitle[Fourier-GUTenberg]{\label{fig:fourier}Utopia text
+with Fourier-GUTenberg math (\texttt{\textbackslash{}usepackage\{fourier\}}).}
+
+\pic{fourier}
+\end{figure*}
+%
+\begin{figure*}
+\captiontitle[Math Design for Utopia]{\label{fig:utopiamd}Utopia
+text with Math Design math \captionbreak (\texttt{\textbackslash{}usepackage{[}utopia{]}\{mathdesign\}}).}
+
+\pic{utopiamd}
+\end{figure*}
+
+
+\bigskip{}
+Using \MF, Achim Blumensath created the package \texttt{MnSymbol}~\cite{CTANmnsymbol},
+which contains geometric symbols (no Greek or other letter-like symbols)
+in varying optical sizes that match the commercial font Adobe MinionPro.
+The \texttt{MnSymbol} package also contains traced Type~1 versions.
+\texttt{MnSymbol} is free; however the package \texttt{MinionPro}
+of Achim Blumensath, Andreas B\"uhmann, and Michael Zedler~\cite{CTANminionpro}
+which uses \texttt{MnSymbol} requires a license from Adobe for the
+font MininonPro.
+
+
+\section{\label{sec:Compar}Comparison of Features}
+
+Table~\ref{cap:FeatureComparison} shows a comparison of the different
+features in each package. The only packages that have optical sizes
+are Computer Modern, CM Bright, Concrete, Euler, and MnSymbol. Except
+for when the \texttt{eulervm} package is used, Latin math letters
+are taken from the italic text font. An asterisk after a font name
+indicates that the package has a version of that style in its own
+font files.
+
+\begin{sidewaystable}\centering\small
+
+\begin{tabular}{lccccccc}
+\hline 
+$\;$Package&
+Text&
+Greek&
+CM sym&
+AMS sym&
+Calligr&
+Blkbd&
+boldmath\tabularnewline
+\hline
+computer modern&
+cm&
+cm&
+cm&
+ams&
+cm&
+ams&
+yes\tabularnewline
+cmbright&
+cmbright&
+cmbright&
+cm{*}&
+cm{*}&
+cm{*}&
+ams&
+no\tabularnewline
+ccfonts,eulervm&
+concrete&
+euler&
+euler&
+ams&
+euler&
+ams&
+yes\tabularnewline
+concmath&
+concrete&
+concrete&
+concmath&
+concmath&
+concmath&
+concmath&
+no\tabularnewline
+iwona&
+iwona&
+iwona&
+iwona&
+iwona&
+cm{*}&
+ams&
+yes\tabularnewline
+kurier&
+kurier&
+kurier&
+kurier&
+kurier&
+cm{*}&
+ams&
+yes\tabularnewline
+anttor&
+anttor&
+anttor&
+anttor&
+anttor&
+anttor&
+ams&
+yes\tabularnewline
+kmath,kerkis&
+kerkis&
+kerkis&
+txfonts&
+txfonts&
+txfonts&
+txfonts&
+yes\tabularnewline
+millennial&
+nc schlbk&
+millennial&
+txfonts&
+txfonts&
+txfonts&
+ams&
+no\tabularnewline
+fouriernc&
+nc schlbk&
+fourier&
+fourier&
+fourier&
+fourier&
+fourier&
+yes\tabularnewline
+pxfonts&
+palatino&
+pxfonts&
+txfonts{*}&
+txfonts{*}&
+txfonts{*}&
+pxfonts&
+yes\tabularnewline
+mathpazo&
+palatino&
+pazo&
+cm&
+ams&
+cm&
+pazo&
+yes\tabularnewline
+mathpple&
+palatino&
+euler&
+euler&
+ams&
+cm&
+ams&
+yes\tabularnewline
+txfonts&
+times&
+txfonts&
+txfonts&
+txfonts&
+txfonts&
+txfonts&
+yes\tabularnewline
+mathtime (Belleek)&
+times&
+belleek&
+belleek&
+ams&
+cm&
+ams&
+no\tabularnewline
+mathptmx&
+times&
+symbol&
+cm&
+ams&
+rsfs&
+ams&
+no\tabularnewline
+mbtimes&
+omega&
+omega&
+mbtimes&
+ams&
+rsfs{*}&
+esstix&
+yes\tabularnewline
+arev&
+arev&
+arev&
+md charter&
+md charter&
+cm&
+fourier&
+yes\tabularnewline
+mathdesign (Charter)&
+charter&
+md charter&
+md charter&
+md charter&
+rsfs{*}&
+ams&
+yes\tabularnewline
+comicsans&
+comicsans&
+comicsans&
+cm&
+cm&
+cm&
+cm&
+yes\tabularnewline
+mathdesign (Garamond)&
+garamond&
+md garamond&
+md garamond&
+md garamond&
+rsfs{*}&
+ams{*}&
+yes\tabularnewline
+fourier&
+utopia&
+fourier&
+fourier&
+fourier&
+fourier&
+fourier&
+yes\tabularnewline
+mathdesign (Utopia)&
+utopia&
+md garamond&
+md utopia&
+md utopia&
+rsfs{*}&
+ams{*}&
+yes\tabularnewline
+\hline
+\end{tabular}
+
+\begin{center}\captiontitle[Comparison of features]{\label{cap:FeatureComparison}Comparison
+of the features of different packages.}\end{center}
+
+\end{sidewaystable}
+
+The only sans serif fonts with matching math fonts are CM Bright and
+Arev Sans. Both work well for presentations. Computer Modern sans
+serif, CM Bright, Arev Sans, Bera Sans, Kerkis Sans, Helvetica, and
+Avant Garde all work well as sans serif fonts that accompany a primary
+roman font. Computer Modern typewriter, \texttt{txtt} (from txfonts),
+Luxi Mono~\cite{CTANluximono}, and Bera Mono all work well as typewriters
+fonts.
+
+There are several other free fonts easily used in \LaTeX{}, notably
+the Bera fonts, Luxi Mono, and efont-serif~\cite{efont-serif}. Malte
+Rosenau converted the Bitstream Vera fonts into Type~1 format, renaming
+the fonts to Bera~\cite{CTANbera}. Bera includes serif, sans, and
+mono. Bera Serif does not have a matching italic font, but the DejaVu
+fonts~\cite{dejavu} are an extension of Bitstream Vera that include
+a true serif italic, as well as Greek and Cyrillic for all three styles.
+Except for Bera Sans and Arev Sans, none of the previous fonts have
+matching math fonts.
+
+
+\section{\label{sec:Creation}Creation of this Survey}
+
+It might be technically feasible to create a font survey such as this
+article as a single \TeX{} document. This document, however, was not
+created in that fashion for two reasons. First, it would be an inordinate
+amount of work to switch between fonts within the same document. The
+authors of the \LaTeX{} packages put in a considerable amount of effort
+to set up the fonts for a document, and it would be silly to duplicate
+their work. Second, we want to show to a reader exactly what he or
+she will get by using that package.
+
+In order to accomplish these goals, a small \LaTeX{} file (see Figure~\ref{cap:SampleLaTeXfile}
+for an example) was made for each font that loaded the appropriate
+packages and then loaded a common text fragment for display. Each
+file was \LaTeX{}ed and then converted to an EPS file using \texttt{dvips}
+with the -E option. The -E option creates a tight bounding box around
+the text. The main file \texttt{survey.tex} then included each of
+these graphics, and was compiled with \texttt{pdflatex}. For some
+reason, \texttt{dvips} created an unusable one-page PS file when including
+\texttt{mbtimes.eps}. HeVeA was used to convert \texttt{survey.tex}
+directly to HTML.%
+\begin{figure}
+\begin{quote}
+\texttt{\textbackslash{}documentclass\{article\}}~\\
+\texttt{\textbackslash{}include\{sampleformat\}}~\\
+\texttt{\hspace*{.01em}~~\textbackslash{}usepackage\{fourier\}}~\\
+\texttt{\textbackslash{}begin\{document\}}~\\
+\texttt{\hspace*{.01em}~~\textbackslash{}include\{textfragment\}}~\\
+\texttt{\textbackslash{}end\{document\}}
+\end{quote}
+\captiontitle[Sample \LaTeX{} file]{\label{cap:SampleLaTeXfile}Sample
+\LaTeX{} file for \texttt{fourier}. The file \texttt{sampleformat.tex}
+contains page layout commands, such as setting the margins and removing
+the page numbers. The file \texttt{textfragment.tex} contains the
+text and mathematics fragment to be displayed. Both included files
+are used by every sample \LaTeX{} file. The line {}``\texttt{\textbackslash{}usepackage\{fourier\}}''
+was changed for each sample to the package listed in the sample's
+caption.}
+\end{figure}
+
+
+
+\subsection*{Acknowledgements}
+
+Thanks to Michael Zedler, Ulrik Vieth, Karl Berry, William Slough,
+and the anonymous referees for helpful comments.
+
+\begin{thebibliography}{10}
+\bibitem{CTANfontinstgd}Philipp Lehman, The Font Installation Guide on \CTAN{/info/Type1fonts/fontinstallationguide}.
+\bibitem{CTANmetatype1}Bogus\l{}aw Jackowski, Janusz M. Nowacki, and Piotr Strzelczyk, MetaType1
+on \CTAN{/fonts/utilities/metatype1}
+\bibitem{WASmathfonts}Walter A. Schmidt, Mathematikschriften f\"ur \LaTeX{}, \url{http://home.vr-web.de/was/mathfonts.html}.
+\bibitem{bluesky}American Mathematical Society (AMS) webpage for Computer Modern Type~1
+fonts, \url{http://www.ams.org/tex/type1-fonts.html}.
+\bibitem{CMBook}Donald E. Knuth, \emph{Computer Modern Typefaces}, Addison-Wesley
+Pub. Co., 1986.
+\bibitem{CMRgain}Raph Levien, Effect of gain on appearance of Computer Modern, \url{http://levien.com/type/cmr/gain.html}.
+\bibitem{DigTyp}Donald E. Knuth, \emph{Digital Typography}, Stanford, California:
+Center for the Study of Language and Information, 1999.
+\bibitem{CTANbluesky}Blue Sky Research and Y\&Y, Inc., Computer Modern Type~1 fonts on
+\CTAN{/fonts/cm/ps-type1/bluesky}.
+\bibitem{CTANbakoma}Basil K. Malyshev, BaKoMa Computer Modern Type~1 and TrueType fonts
+on \CTAN{/fonts/cm/ps-type1/bakoma}.
+\bibitem{CTANec}J\"org Knappen and Norbert Schwarz, European Computer Modern fonts
+on \CTAN{/fonts/ec}.
+\bibitem{CTANtt2001}Szab\'o P\'eter, Tt2001 fonts on \CTAN{/fonts/ps-type1/tt2001}.
+\bibitem{textrace}Szab\'o P\'eter, webpage for \texttt{textrace} and Tt2001 fonts,
+\url{http://www.inf.bme.hu/~pts/textrace}.
+\bibitem{CTANcm-super}Vladimir Volovich, CM-Super on \CTAN{/fonts/ps-type1/cm-super}.
+\bibitem{CM-Super}Vladimir Volovich, \TUGboat{tb24-1/volovich.pdf}{CM-Super}: Automatic
+creation of efficient Type~1 fonts from \MF\  fonts, \emph{TUGboat},
+24 (1) 2003, 75--78.
+\bibitem{CTANlm}Bogus\l{}aw Jackowski and Janusz M. Nowacki, Latin Modern on \CTAN{/fonts/ps-type1/lm}.
+\bibitem{LatinModern}Bogus\l{}aw Jackowski and Janusz M. Nowacki, \TUGboat{tb24-1/jackowski.pdf}{Latin
+Modern}: Enhancing Computer Modern with accents, accents, accents,
+\emph{TUGboat}, 24 (1) 2003, 64--74.
+\bibitem{texpower}\TeX{}Power \LaTeX{} style files by Stephan Lehmke, \url{http://texpower.sourceforge.net}.
+\bibitem{CTANcmbright}Walter A. Schmidt, CM Bright on \CTAN{/fonts/cmbright}.
+\bibitem{CTANhfbright}Harald Harders, hfbright on \CTAN{/fonts/ps-type1/hfbright}.
+\bibitem{concretebook}Ronald L. Graham, Donald E. Knuth, and Oren Patashnik, \emph{Concrete
+Mathematics,} Addison-Wesley, 1989.
+\bibitem{CTANconcmath}Ulrik Vieth, Concrete Math fonts on \CTAN{/fonts/concmath}.
+\bibitem{CTANccfonts}Walter Schmidt, ccfonts on \CTAN{/macros/latex/contrib/ccfonts}.
+\bibitem{CTANeulervm}Walter Schmidt, eulervm on \CTAN{/fonts/eulervm}.
+\bibitem{eulervm}Walter Schmidt, \TUGboat{tb23-3-4/tb75schmidt.pdf}{Euler-VM}: Generic
+math fonts for use with \LaTeX{}, \emph{TUGboat}, 23 (3/4) 2002, 301--303.
+\bibitem{CTANiwona}Janusz M. Nowacki, Iwona on \CTAN{/fonts/iwona}.
+\bibitem{CTANkurier}Janusz M. Nowacki, Kurier on \CTAN{/fonts/kurier}.
+\bibitem{CTANantp}Janusz M. Nowacki, Antykwa P\'o\l{}tawskiego on \CTAN{/fonts/psfonts/polish/antp}.
+\bibitem{CTANantt}Janusz M. Nowacki, Antykwa Toru\acuten{}ska on \CTAN{/fonts/antt}.
+\bibitem{AntTorunska}Janusz M. Nowacki, \TUGboat{tb19-3/tb60antyk.pdf}{Antykwa Toru\acuten{}ska}:
+an electronic replica of a Polish traditional type, \emph{TUGboat},
+19 (3) 1998, 242--243.
+\bibitem{CTANpsnfss}Sebastian Rahtz and Walter A. Schmidt, PSNFSS on \CTAN{/macros/latex/required/psnfss}.
+\bibitem{Kerkis}Antonis Tsolomitis, The \TUGboat{tb23-3-4/tb75tsol.pdf}{Kerkis}
+font family, \emph{TUGboat}, 23 (3/4) 2002, 296--301.
+\bibitem{CTANkerkis}Antonis Tsolomitis, Kerkis on \CTAN{/fonts/greek/kerkis}.
+\bibitem{CTANfouriernc}Michael Zedler, fouriernc on \CTAN{/fonts/fouriernc}.
+\bibitem{CTANpxfonts}Young Ryu, pxfonts on \CTAN{/fonts/pxfonts}.
+\bibitem{CTANmathpazo}Diego Puga, Pazo Math fonts on \CTAN{/fonts/mathpazo}.
+\bibitem{CTANfpl}Ralf Stubner, FPL font on \CTAN{/fonts/fpl}.
+\bibitem{fplneu}Walter Schmidt, FPL Neu package, \url{http://home.vr-web.de/was/x/FPL/}.
+\bibitem{CTANtxfonts}Young Ryu, txfonts on \CTAN{/fonts/txfonts}.
+\bibitem{CTANbelleek}Richard Kinch, Belleek fonts on \CTAN{/fonts/belleek}.
+\bibitem{Belleek}Richard J. Kinch, \TUGboat{tb19-3/tb60kinch.pdf}{Belleek}: A call
+for \MF\  revival, \emph{TUGboat}, 19 (3) 1998, 244--249.
+\bibitem{STIX}STIX Fonts project, \url{http://www.stixfonts.org}.
+\bibitem{mbtimes}Michel Bovani, mbtimes at \url{ftp://ftp.gutenberg.eu.org/pub/gut/distribs/mbtimes/}.
+\bibitem{Omega}John Plaice and Yannis Haralambous, Omega at \url{http://omega.enstb.org}.
+\bibitem{MgOpenModerna}MgOpenModerna, one of the MgOpen fonts, \url{http://www.ellak.gr/fonts/mgopen}.
+\bibitem{FreeSans}FreeSans, one of the Free UCS Outline Fonts, \url{http://savannah.nongnu.org/projects/freefont}.
+\bibitem{vera}Bitstream Vera, released by Bitstream in cooperation with the Gnome
+Foundation, \url{http://www.gnome.org/fonts}.
+\bibitem{CTANbera}Malte Rosenau, Bera Postscript Type~1 fonts (converted from Bitstream
+Vera fonts, which necessitated the name change) and \LaTeX{} support
+files by Walter~A. Schmidt, on \CTAN{/fonts/bera}.
+\bibitem{CTANarev}Tavmjong Bah and Stephen Hartke, Arev Sans on \CTAN{/fonts/arev}.
+\bibitem{arev}Tavmjong Bah, Arev Sans, \url{http://tavmjong.free.fr/FONTS}.
+\bibitem{CTANcharter}Bitstream Charter on \CTAN{/fonts/charter}.
+\bibitem{CTANmathdesign}Paul Pichaureau, Math Design fonts on \CTAN{/fonts/mathdesign}.
+\bibitem{CharisSIL}Charis SIL, \url{http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=CharisSILfont}.
+\bibitem{comicsans}Comic Sans, part of Microsoft's core web fonts, available at \url{http://corefonts.sourceforge.net/}.
+\bibitem{CTANcomicsans}Scott Pakin, Comic Sans \LaTeX{} package on \CTAN{/macros/latex/contrib/comicsans}.
+\bibitem{CTANgaramond}URW Garamond on \CTAN{/fonts/urw/garamond}.
+\bibitem{CTANutopia}Adobe Utopia on \CTAN{/fonts/utopia}.
+\bibitem{CTANfourier}Michel Bovani, Fourier-GUTenberg on \CTAN{/fonts/fourier-GUT}.
+\bibitem{CTANmnsymbol}Achim Blumensath, MnSymbol on \CTAN{/fonts/mnsymbol}.
+\bibitem{CTANminionpro}Achim Blumensath, Andreas B\"uhmann, and Michael Zedler, MinionPro
+on \CTAN{/fonts/minionpro}.
+\bibitem{dejavu}DejaVu fonts, \url{http://dejavu.sourceforge.net}.
+\bibitem{CTANluximono}Luxi Mono on \CTAN{/fonts/LuxiMono}.
+\bibitem{efont-serif}efont-serif at \url{http://openlab.jp/efont/serif/}.
+\end{thebibliography}
+\begin{comment}
+Victor Gaultney, Gentium at \url{http://scripts.sil.org/gentium}.
+
+Michael Zedler, gentium at \url{http://www.hft.ei.tum.de/mz/ggn.tar.bz2}.
+\end{comment}
+%filler to avoid comment environment as last line
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/textfragment.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/textfragment.tex
new file mode 100644
index 00000000000..c174111dae6
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/textfragment.tex
@@ -0,0 +1,35 @@
+
+\textbf{Theorem 1 (Residue Theorem).}
+Let $f$ be analytic in the region $G$ except for the isolated singularities $a_1,a_2,\ldots,a_m$. If $\gamma$ is a closed rectifiable curve in $G$ which does not pass through any of the points $a_k$ and if $\gamma\approx 0$ in $G$ then
+\[
+\frac{1}{2\pi i}\int_\gamma f = \sum_{k=1}^m n(\gamma;a_k) \text{Res}(f;a_k).
+\]
+
+\textbf{Theorem 2 (Maximum Modulus).}
+\emph{Let $G$ be a bounded open set in $\mathbb{C}$ and suppose that $f$ is a continuous function on $G^-$ which is analytic in $G$. Then}
+\[
+\max\{|f(z)|:z\in G^-\}=\max \{|f(z)|:z\in \partial G \}.
+\]
+\vspace*{-1em}
+
+\newcommand{\abc}{abcdefghijklmnopqrstuvwxyz}
+\newcommand{\ABC}{ABCDEFGHIJKLMNOPQRSTUVWXYZ}
+\newcommand{\alphabeta}{\alpha\beta\gamma\delta\epsilon\varepsilon\zeta\eta\theta\vartheta\iota\kappa\varkappa\lambda\mu\nu\xi o\pi\varpi\rho\varrho\sigma\varsigma\tau\upsilon\phi\varphi\chi\psi\omega}
+\newcommand{\AlphaBeta}{\Gamma\Delta\Theta\Lambda\Xi\Pi\Sigma\Upsilon\Phi\Psi\Omega}
+
+%\ABC \quad $\ABC$
+
+%\abc \quad $\abc$ \quad $01234567890$
+
+%$\AlphaBeta$ \quad $\alphabeta$ \quad $\ell\wp\aleph\infty\propto\emptyset\nabla\partial\mho\imath\jmath\hslash\eth$
+
+$\mathrm{A} \Lambda \Delta \nabla \mathrm{B C D} \Sigma \mathrm{E F} \Gamma \mathrm{G H I J K L M N O} \Theta \Omega \mho \mathrm{P} \Phi \Pi \Xi \mathrm{Q R S T U V W X Y} \Upsilon \Psi \mathrm{Z} $  $ \quad 1234567890 $
+
+%$\mathit{A \Lambda \Delta B C D E F \Gamma G H I J K L M N O \Theta \Omega P \Phi \Pi \Xi Q R S T U V W X Y \Upsilon \Psi Z }$
+
+% don't allow overfull boxes
+{\par \tolerance=0 \emergencystretch=100em $a\alpha b \beta c \partial d \delta e \epsilon \varepsilon f \zeta \xi g \gamma h \hbar \hslash \iota i \imath j \jmath k \kappa \varkappa l \ell \lambda m n \eta \theta \vartheta o \sigma \varsigma \phi \varphi \wp p \rho \varrho q r s t \tau \pi u \mu \nu v \upsilon w \omega \varpi x \chi y \psi z$ \linebreak[3] $\infty \propto \emptyset \varnothing \mathrm{d}\eth \backepsilon$\par}
+
+%$\mathcal{\ABC} \quad \mathbb{\ABC}$
+
+%\boldmath $\alpha + b = 27$
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/txfonts.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/txfonts.tex
new file mode 100644
index 00000000000..01358d355cd
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/txfonts.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[varg]{txfonts}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/source/utopiamd.tex b/Master/texmf-dist/doc/generic/free-math-font-survey/source/utopiamd.tex
new file mode 100644
index 00000000000..9fd15d65ee0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/source/utopiamd.tex
@@ -0,0 +1,13 @@
+
+\documentclass{article}
+
+\include{sampleformat}
+
+%PACKAGEOPTIONS
+\usepackage[utopia]{mathdesign}
+
+\begin{document}
+
+\include{textfragment}
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/survey.html b/Master/texmf-dist/doc/generic/free-math-font-survey/survey.html
new file mode 100644
index 00000000000..9084013ab20
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/survey.html
@@ -0,0 +1,1116 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
+            "http://www.w3.org/TR/REC-html40/loose.dtd">
+<HTML>
+
+<HEAD>
+
+<TITLE>A Survey of Free Math Fonts for TeX and LaTeX1</TITLE>
+
+<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<META name="GENERATOR" content="hevea 1.08">
+<STYLE type="text/css">
+.toc{list-style:none;}
+.title{margin:auto;text-align:center}
+.center{text-align:center;margin-left:auto;margin-right:auto;}
+.flushleft{text-align:left;margin-left:0ex;margin-right:auto;}
+.flushright{text-align:right;margin-left:auto;margin-right:0ex;}
+DIV TABLE{margin-left:inherit;margin-right:inherit;}
+PRE{text-align:left;margin-left:0ex;margin-right:auto;}
+BLOCKQUOTE{margin-left:4ex;margin-right:4ex;text-align:left;}
+.part{margin:auto;text-align:center}
+</STYLE>
+</HEAD>
+
+<BODY >
+<!--HEVEA command line is: hevea survey -->
+<!--HTMLHEAD-->
+
+  <title>A Survey of Free Math Fonts for TeX and LaTeX</title>
+  <style type="text/css">
+    BODY { background-color: white; color: black; }
+    A:link { color: #003399; text-decoration: none; }
+    A:active { color: blue; text-decoration: underline; }
+    A:visited { color: #003399; text-decoration: none; }
+    A:hover { color: blue; text-decoration: underline; }
+    H5 {font-size: 110\%;  font-weight: bold; }
+  </style><!--ENDHTML-->
+<!--PREFIX <ARG ></ARG>-->
+<!--CUT DEF section 1 -->
+
+<BR>
+<TABLE CLASS="title">
+<TR><TD>
+<H1 CLASS="titlemain">A Survey of Free Math Fonts for TeX and LaTeX<SUP><A NAME="text1" HREF="#note1">1</A></SUP></H1>
+<H3 CLASS="titlerest">Stephen G. Hartke<SUP><A NAME="text2" HREF="#note2">2</A></SUP></H3>
+<H3 CLASS="titlerest">May 5, 2006</H3></TD>
+</TR></TABLE><BR>
+<B>Note:</B> <EM>This survey is also available in </EM><A HREF="survey.pdf"><EM>PDF</EM></A><EM>
+format.</EM><BR>
+<BR>
+<BR>
+<!--TOC section Contents-->
+
+<H2 CLASS="section">Contents</H2><!--SEC END -->
+
+<A HREF="#sec:Intro"><B>Introduction</B></A><BR>
+<BR>
+<A HREF="#sec:TeXFonts"><B>Fonts Originally Designed
+for TeX</B></A>
+<BLOCKQUOTE CLASS="quote">
+<A HREF="#fig:CM">Computer Modern</A>, <A HREF="#fig:CMBright">CM
+Bright</A>, <A HREF="#fig:ConcEuler">Concrete and Euler</A>, <A HREF="#fig:ConcMath">Concrete
+Math</A>, <A HREF="#fig:Iwona">Iwona</A>, <A HREF="#fig:Kurier">Kurier</A>,
+<A HREF="#fig:AntPolt">Antykwa Pó&#322;tawskiego</A>, <A HREF="#fig:AntTor">Antykwa
+Toru&#324;ska</A>
+</BLOCKQUOTE>
+<A HREF="#sec:PSFonts"><B>Core Postscript Fonts</B></A>
+<BLOCKQUOTE CLASS="quote">
+<A HREF="#fig:Kerkis">Kerkis</A>, <A HREF="#fig:Millen">Millennial</A>,
+<A HREF="#fig:fouriernc">fouriernc</A>, <A HREF="#fig:pxfonts">pxfonts</A>,
+<A HREF="#fig:Pazo">Pazo</A>, <A HREF="#fig:mathpple">mathpple</A>,
+<A HREF="#fig:txfonts">txfonts</A>, <A HREF="#fig:Belleek">Belleek</A>,
+<A HREF="#fig:mathptmx">mathptmx</A>, <A HREF="#fig:mbtimes">mbtimes</A>
+</BLOCKQUOTE>
+<A HREF="#sec:OtherFonts"><B>Other Free Fonts</B></A>
+<BLOCKQUOTE CLASS="quote">
+<A HREF="#fig:Arev">Arev Sans</A>, <A HREF="#fig:chartermd">Math Design
+with Charter</A>, <A HREF="#fig:comicsans">Comic Sans</A>, <A HREF="#fig:garamd">Math
+Design with Garamond</A>, <A HREF="#fig:fourier">Fourier-GUTenberg</A>,
+<A HREF="#fig:utopiamd">Math Design with Utopia</A>
+</BLOCKQUOTE>
+<A HREF="#sec:Compar"><B>Comparison of Features</B></A><BR>
+<BR>
+<A HREF="#sec:Creation"><B>Creation of this Survey</B></A><BR>
+<BR>
+<!--TOC section Introduction-->
+
+<H2 CLASS="section"><A NAME="htoc1">1</A>&nbsp;&nbsp;<A NAME="sec:Intro"></A>Introduction</H2><!--SEC END -->
+
+One of the biggest challenges in selecting a font for TeX or LaTeX
+is that there are not very many math fonts that match the plethora
+of available text fonts. It's reasonably easy to use an arbitrary
+Postscript Type&nbsp;1 font in TeX for text (see Philipp Lehman's Font
+Installation Guide&nbsp;[<A HREF="#CTANfontinstgd"><CITE>1</CITE></A>]), but obtaining and configuring
+a matching math font from scratch is a demanding task. Thus, there
+are few math fonts for TeX, and in particular very few free ones.
+However, in the past few years, several very nice free fonts have
+been released. The goal of this article is to list all of the free
+math fonts and to provide examples.<BR>
+<BR>
+&#8220;Free&#8221; here means fonts that are free to use (both commercially
+and non-commercially) and free to distribute, but not necessarily
+free to modify. I also am biased towards listing fonts that have outline
+versions in PostScript Type&nbsp;1 format suitable for embedding in Postscript
+PS or Adobe Acrobat PDF files. Donald E. Knuth originally designed
+the METAFONT  system for producing fonts for TeX in bitmap format.
+PS or PDF files that have embedded bitmap fonts do not display well
+in Adobe Acrobat Reader,<SUP><A NAME="text3" HREF="#note3">3</A></SUP> to the point of being almost unreadable on the screen, and are also
+noticeable when printing at extremely high resolutions (on photo-setters,
+for instance). Since outline fonts contain mathematical descriptions
+of the curves used in each glyph, they can be scaled to any resolution
+while retaining image quality.<BR>
+<BR>
+The fonts listed here are categorized according to their origin: whether
+originally designed for TeX, related to the standard Postscript
+fonts, or other free fonts. A font's origin does not particularly
+bear on its quality or suitability for typesetting mathematics. No
+recommendations or evaluations of the fonts are given here, as people's
+tastes in fonts vary greatly. The goal of this survey is simply to
+make authors aware of all their options.<BR>
+<BR>
+Most of the fonts can be selected by including a single package in
+the preamble of the user's LaTeX file (the <EM>preamble</EM> is the
+section after &#8220;<TT>\documentclass{}</TT>&#8221; and
+before &#8220;<TT>\begin{document}</TT>&#8221;). The line
+or lines to include for each font are listed in the caption of the
+sample figure. For example &#8220;<TT>\usepackage{fourier}</TT>&#8221;
+uses Utopia and Fourier-GUTenberg, as shown in the sample LaTeX
+file in Section&nbsp;<A HREF="#sec:Creation">6</A>.<BR>
+<BR>
+Walter A. Schmidt also has a survey in German of math fonts&nbsp;[<A HREF="#WASmathfonts"><CITE>3</CITE></A>]
+that concentrates more on commercial fonts. Schmidt's survey has several
+examples that show different pairings between text fonts and math
+fonts.<BR>
+<BR>
+<!--TOC section Fonts Originally Designed for TeX-->
+
+<H2 CLASS="section"><A NAME="htoc2">2</A>&nbsp;&nbsp;<A NAME="sec:TeXFonts"></A>Fonts Originally Designed for TeX</H2><!--SEC END -->
+
+These fonts were originally designed for use with TeX, using either
+METAFONT  or MetaType1&nbsp;[<A HREF="#CTANmetatype1"><CITE>2</CITE></A>].<BR>
+<BR>
+<!--TOC paragraph Computer Modern:-->
+
+<H5 CLASS="paragraph">Computer Modern:</H5><!--SEC END -->
+
+Knuth created Computer Modern&nbsp;[<A HREF="#CMBook"><CITE>5</CITE></A>] as the default font
+for TeX. The font set includes serif, sans serif, and monospaced
+text faces, and corresponding math fonts. The math symbol set is very
+complete. Computer Modern is <EM>the</EM> font for TeX, which leads
+some to claim that the font is overused. The characters are fairly
+thin and light, and so are not as readable on screen in small sizes
+or from high-resolution laser printers.<SUP><A NAME="text4" HREF="#note4">4</A></SUP> In a comparison by Raph Levien&nbsp;[<A HREF="#CMRgain"><CITE>6</CITE></A>], the printing in
+Knuth's <EM>Digital Typography</EM>&nbsp;[<A HREF="#DigTyp"><CITE>7</CITE></A>] is heavier than
+the digital version or from a laser printer.<BR>
+<BR>
+Type&nbsp;1 versions of Computer Modern from Blue Sky Research and Y&amp;Y,
+Inc. have been made freely available by the American Mathematical
+Society (AMS) and a collection of publishers and other technical companies&nbsp;[<A HREF="#CTANbluesky"><CITE>8</CITE></A><CITE>, </CITE><A HREF="#bluesky"><CITE>4</CITE></A>].
+Basil K. Malyshev has also released a free Type&nbsp;1 version of Computer
+Modern&nbsp;[<A HREF="#CTANbakoma"><CITE>9</CITE></A>], originally for use with his TeX system
+BaKoMa TeX.<BR>
+<BR>
+Computer Modern has been extended to include more characters, particularly
+for non-English European languages. These fonts include European Computer
+Modern by Jörg Knappen and Norbert Schwarz (METAFONT  only) [<A HREF="#CTANec"><CITE>10</CITE></A>];
+Tt2001 by Szabó Péter (converted into Type&nbsp;1 format from METAFONT 
+sources using <TT>textrace</TT>; Tt2001 has been superseded by CM-Super,
+which Péter recommends) [<A HREF="#textrace"><CITE>12</CITE></A><CITE>, </CITE><A HREF="#CTANtt2001"><CITE>11</CITE></A>]; CM-Super by
+Vladimir Volovich (also converted using <TT>textrace</TT>) [<A HREF="#CM-Super"><CITE>14</CITE></A><CITE>, </CITE><A HREF="#CTANcm-super"><CITE>13</CITE></A>];
+and Latin Modern by Bogus&#322;aw Jackowski and Janusz M. Nowacki (extended
+from the Blue Sky AMS fonts using MetaType1) [<A HREF="#LatinModern"><CITE>16</CITE></A><CITE>, </CITE><A HREF="#CTANlm"><CITE>15</CITE></A>]. <BR>
+<BR>
+The SliTeX font (<TT>lcmss</TT>) is a sans serif text face that
+has wide letters and high <EM>x</EM> height. Its high readability makes
+it extremely suitable for slide presentations. However, there is no
+matching math font. SliTeX sans serif can be set as the primary
+text font using TeXPower's <TT>tpslifonts.sty</TT>&nbsp;[<A HREF="#texpower"><CITE>17</CITE></A>].<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 1: <A NAME="fig:CM"></A>Computer Modern (using
+the Blue Sky and Y&amp;Y Type&nbsp;1 fonts; no package necessary).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/cm.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Computer Modern Bright: -->
+
+<H5 CLASS="paragraph">Computer Modern Bright: </H5><!--SEC END -->
+
+This a sans serif font with corresponding math font derived from Computer
+Modern by Walter A. Schmidt [<A HREF="#CTANcmbright"><CITE>18</CITE></A>]. CM-Super contains
+Type&nbsp;1 versions of the text fonts in T1 encoding, and Harald Harders
+created Type&nbsp;1 versions of the text and math fonts called <TT>hfbright</TT>&nbsp;[<A HREF="#CTANhfbright"><CITE>19</CITE></A>]
+using <TT>mftrace</TT>. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 2: <A NAME="fig:CMBright"></A>CM Bright (<TT>\usepackage{cmbright}</TT>;
+output uses the <TT>hfbright</TT> fonts).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/cmbright.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Concrete and Euler or Concrete Math:-->
+
+<H5 CLASS="paragraph">Concrete and Euler or Concrete Math:</H5><!--SEC END -->
+
+The Concrete font was created by Knuth for his book <EM>Concrete
+Mathematics</EM>&nbsp;[<A HREF="#concretebook"><CITE>20</CITE></A>]. Hermann Zapf was commissioned
+by the AMS to create the math font Euler for use in <EM>Concrete
+Mathematics</EM>. Type&nbsp;1 versions of Concrete in T1 encoding are available
+in the CM-Super collection&nbsp;[<A HREF="#CTANcm-super"><CITE>13</CITE></A>], and Type&nbsp;1 versions
+of Euler are available in the Blue Sky collection from the AMS&nbsp;[<A HREF="#CTANbluesky"><CITE>8</CITE></A>]
+and in the BaKoMa collection&nbsp;[<A HREF="#CTANbakoma"><CITE>9</CITE></A>]. The <TT>eulervm</TT>
+package by Walter Schmidt&nbsp;[<A HREF="#CTANeulervm"><CITE>23</CITE></A><CITE>, </CITE><A HREF="#eulervm"><CITE>24</CITE></A>] implements
+virtual fonts for Euler that are more efficient to use with LaTeX.
+Ulrik Vieth created the Concrete Math fonts&nbsp;[<A HREF="#CTANconcmath"><CITE>21</CITE></A>]
+to match the Concrete text fonts; the only free versions are implemented
+in METAFONT. The <TT>ccfonts</TT> package by Walter Schmidt&nbsp;[<A HREF="#CTANccfonts"><CITE>22</CITE></A>]
+changes the text font to Concrete and changes the math font to the
+Concrete Math fonts if <TT>eulervm</TT> is not loaded. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 3: <A NAME="fig:ConcEuler"></A>Concrete
+text with Euler math (<TT>\usepackage{ccfonts,eulervm}
+\usepackage[T1]{fontenc}</TT>). Note that Concrete
+does not have a bold font, so Computer Modern is used instead. Non-bold
+text output uses the CM-Super Concrete fonts.</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/concrete.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 4: <A NAME="fig:ConcMath"></A>Concrete text with
+Concrete math (<TT>\usepackage{ccfonts} \usepackage[T1]{fontenc}</TT>).
+Note that Concrete does not have a bold font, so Computer Modern is
+used instead. Non-bold text output uses the CM-Super Concrete fonts.</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/concmath.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Iwona and Kurier:-->
+
+<H5 CLASS="paragraph">Iwona and Kurier:</H5><!--SEC END -->
+
+The fonts Iwona and Kurier were created by J. M. Nowacki&nbsp;[<A HREF="#CTANiwona"><CITE>25</CITE></A><CITE>, </CITE><A HREF="#CTANkurier"><CITE>26</CITE></A>]
+using the MetaType1 system based on typefaces by the Polish typographer
+Ma&#322;gorzata Budyta. The two fonts are very similar, except that
+Kurier avoids &#8220;ink traps&#8221; with gaps in its strokes. The packages
+have complete math support in both TeX and LaTeX. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 5: <A NAME="fig:Iwona"></A>Iwona text and math (<TT>\usepackage[math]{iwona}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/iwona.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 6: <A NAME="fig:Kurier"></A>Kurier text and math (<TT>\usepackage[math]{kurier}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/kurier.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Antykwa Pó&#322;tawskiego:-->
+
+<H5 CLASS="paragraph">Antykwa Pó&#322;tawskiego:</H5><!--SEC END -->
+
+J. M. Nowacki created the font Antykwa Pó&#322;tawskiego&nbsp;[<A HREF="#CTANantp"><CITE>27</CITE></A>]
+using the MetaType1 system based on a typeface by Polish typographer
+Adam Pó&#322;tawski. The package <TT>antpolt</TT> has no math support
+at this time, and requires the encoding to be set to QX or OT4. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 7: <A NAME="fig:AntPolt"></A>Antykwa
+Pó&#322;tawskiego text (<TT>\usepackage{antpolt}</TT>
+and <TT>\usepackage[QX]{fontenc}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/antpolt.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Antykwa Toru&#324;ska:-->
+
+<H5 CLASS="paragraph">Antykwa Toru&#324;ska:</H5><!--SEC END -->
+
+The font Antykwa Toru&#324;ska was created by J. M. Nowacki&nbsp;[<A HREF="#AntTorunska"><CITE>29</CITE></A><CITE>, </CITE><A HREF="#CTANantt"><CITE>28</CITE></A>]
+using the MetaType1 system based on a typeface by the Polish typographer
+Zygfryd Gardzielewski. The package <TT>anttor</TT> has complete math
+support in both TeX and LaTeX. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 8: <A NAME="fig:AntTor"></A>Antykwa Toru&#324;ska
+text and math (<TT>\usepackage[math]{anttor}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/anttor.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC section Core Postscript Fonts-->
+
+<H2 CLASS="section"><A NAME="htoc3">3</A>&nbsp;&nbsp;<A NAME="sec:PSFonts"></A>Core Postscript Fonts</H2><!--SEC END -->
+
+When Adobe introduced Postscript in 1984, they defined 35 core fonts
+(in 10 typefaces) that must be present in all Postscript interpreters.
+In 1996, URW++ released a replacement set for the core fonts under
+the GNU General Public License. The URW++ fonts were primarily released
+for use with Ghostscript, a free Postscript interpreter. Table&nbsp;<A HREF="#cap:CorePostscriptFonts">1</A>
+lists the original Postscript fonts, along with the URW++/Ghostscript
+equivalents. Each font can be used as the default text font by selecting
+the indicated LaTeX package from the PSNFSS distribution&nbsp;[<A HREF="#CTANpsnfss"><CITE>30</CITE></A>].<BLOCKQUOTE CLASS="table">
+<DIV CLASS="center"><TABLE CELLSPACING=2 CELLPADDING=0>
+<TR><TD BGCOLOR=black COLSPAN=4><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Adobe Postscript</TD>
+<TD ALIGN=center NOWRAP>URW++/Ghostscript</TD>
+<TD ALIGN=center NOWRAP># of fonts</TD>
+<TD ALIGN=center NOWRAP>package</TD>
+</TR>
+<TR><TD BGCOLOR=black COLSPAN=4><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Avant Garde</TD>
+<TD ALIGN=center NOWRAP>URW Gothic L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>avant</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Bookman</TD>
+<TD ALIGN=center NOWRAP>URW Bookman L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>bookman</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Courier</TD>
+<TD ALIGN=center NOWRAP>Nimbus Mono L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>courier</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Helvetica</TD>
+<TD ALIGN=center NOWRAP>Nimbus Sans L</TD>
+<TD ALIGN=center NOWRAP>8</TD>
+<TD ALIGN=center NOWRAP><TT>helvet</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>New Century Schoolbook</TD>
+<TD ALIGN=center NOWRAP>Century Schoolbook L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>newcent</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Palatino</TD>
+<TD ALIGN=center NOWRAP>URW Palladio L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>palatino</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Symbol</TD>
+<TD ALIGN=center NOWRAP>Standard Symbols L</TD>
+<TD ALIGN=center NOWRAP>1</TD>
+<TD ALIGN=center NOWRAP>&mdash;</TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Times</TD>
+<TD ALIGN=center NOWRAP>Nimbus Roman No. 9 L</TD>
+<TD ALIGN=center NOWRAP>4</TD>
+<TD ALIGN=center NOWRAP><TT>times</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Zapf Chancery</TD>
+<TD ALIGN=center NOWRAP>URW Chancery L</TD>
+<TD ALIGN=center NOWRAP>1</TD>
+<TD ALIGN=center NOWRAP><TT>chancery</TT></TD>
+</TR>
+<TR><TD ALIGN=center NOWRAP>Zapf Dingbats</TD>
+<TD ALIGN=center NOWRAP>Dingbats</TD>
+<TD ALIGN=center NOWRAP>1</TD>
+<TD ALIGN=center NOWRAP>&mdash;</TD>
+</TR>
+<TR><TD BGCOLOR=black COLSPAN=4><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR></TABLE></DIV><BR>
+<BR>
+<DIV CLASS="center"><BR>
+<BR>
+<DIV CLASS="center">Table 1: <A NAME="cap:CorePostscriptFonts"></A>Core
+Postscript fonts and URW++/Ghostscript equivalents.</DIV></DIV><BR>
+<BR>
+
+</BLOCKQUOTE>
+<!--TOC paragraph Avant Garde and Kerkis Sans:-->
+
+<H5 CLASS="paragraph">Avant Garde and Kerkis Sans:</H5><!--SEC END -->
+
+The font Kerkis Sans was created by Antonis Tsolomitis&nbsp;[<A HREF="#Kerkis"><CITE>31</CITE></A><CITE>, </CITE><A HREF="#CTANkerkis"><CITE>32</CITE></A>]
+by extending Avant Garde to include Greek and additional Latin characters.
+The resulting fonts are stand-alone and can be used by applications
+outside of TeX. The package <TT>kerkis</TT> sets the sans serif
+font to Kerkis Sans; there is no package option to set Kerkis Sans
+to be the primary text font.<BR>
+<BR>
+<!--TOC paragraph Bookman and Kerkis:-->
+
+<H5 CLASS="paragraph">Bookman and Kerkis:</H5><!--SEC END -->
+
+The font Kerkis was created by Antonis Tsolomitis&nbsp;[<A HREF="#Kerkis"><CITE>31</CITE></A><CITE>, </CITE><A HREF="#CTANkerkis"><CITE>32</CITE></A>]
+by extending URW Bookman&nbsp;L to include Greek and additional Latin
+characters. The resulting fonts are stand-alone and can be used by
+applications outside of TeX. A font of math symbols is included,
+but not used by the LaTeX package. The package <TT>kmath</TT> uses
+txfonts for math symbols and uppercase Greek letters. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 9: <A NAME="fig:Kerkis"></A>Kerkis text and math (<TT>\usepackage{kmath,kerkis}</TT>;
+the order of the packages matters, since <TT>kmath</TT> loads the
+<TT>txfonts</TT> package which changes the default text font).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/kerkis.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph New Century Schoolbook and Millennial or fouriernc: -->
+
+<H5 CLASS="paragraph">New Century Schoolbook and Millennial or fouriernc: </H5><!--SEC END -->
+
+The Millennial math font of the current author contains Greek letters
+and other letter-like mathematical symbols. A set of virtual fonts
+is provided that uses New Century Schoolbook for Latin letters in
+math, Millennial for Greek and other letter-like symbols, and txfonts
+and Computer Modern for all other symbols, including binary operators,
+relations, and large symbols. This font is still in development, but
+will hopefully be released in 2006. The <TT>fouriernc</TT> package
+of Michael Zedler&nbsp;[<A HREF="#CTANfouriernc"><CITE>33</CITE></A>] uses New Century Schoolbook
+for text and Latin letters in mathematics, and the Greek and symbol
+fonts from the Fourier-GUTenberg package for the remaining mathematical
+symbols. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 10: <A NAME="fig:Millen"></A>New Century Schoolbook
+with Millennial math (<TT>\usepackage{millennial}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/millennial.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 11: <A NAME="fig:fouriernc"></A>New Century Schoolbook
+with Fourier math (<TT>\usepackage{fouriernc}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/fouriernc.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Palatino and pxfonts, Pazo, or mathpple:-->
+
+<H5 CLASS="paragraph">Palatino and pxfonts, Pazo, or mathpple:</H5><!--SEC END -->
+
+Young Ryu created the pxfonts collection&nbsp;[<A HREF="#CTANpxfonts"><CITE>34</CITE></A>], which
+contains Greek and other letter-like symbols, as well as a complete
+set of geometric symbols, including the AMS symbols. Diego Puga created
+the Pazo math fonts, which include the Greek letters and other letter-like
+symbols in a style that matches Palatino. The LaTeX package <TT>mathpazo</TT>
+(now part of PSNFSS&nbsp;[<A HREF="#CTANpsnfss"><CITE>30</CITE></A>]) uses Palatino for Latin letters,
+Pazo for Greek and other letter-like symbols, and Computer Modern
+for geometric symbols. The LaTeX package <TT>mathpple</TT> (also
+part of PSNFSS&nbsp;[<A HREF="#CTANpsnfss"><CITE>30</CITE></A>]) uses Palatino for Latin letters
+and slanted Euler for Greek and other symbols. Since Hermann Zapf
+designed both Palatino and Euler, the designs mesh well. An alternate
+use of Euler is using the <TT>eulervm</TT> package. Ralf Stubner added
+small caps and old-style figures to URW Palladio L in the FPL package&nbsp;[<A HREF="#CTANfpl"><CITE>36</CITE></A>],
+and Walter Schmidt extended these fonts in the FPL Neu package&nbsp;[<A HREF="#fplneu"><CITE>37</CITE></A>].
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 12: <A NAME="fig:pxfonts"></A>Palatino text with pxfonts
+math (<TT>\usepackage{pxfonts}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/pxfonts.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 13: <A NAME="fig:Pazo"></A>Palatino text with Pazo math
+(<TT>\usepackage{mathpazo}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/pazo.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 14: <A NAME="fig:mathpple"></A>Palatino text with Euler
+math (<TT>\usepackage{mathpple}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/mathpple.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Times and txfonts, Belleek, mathptmx, or mbtimes:-->
+
+<H5 CLASS="paragraph">Times and txfonts, Belleek, mathptmx, or mbtimes:</H5><!--SEC END -->
+
+Young Ryu created the txfonts collection&nbsp;[<A HREF="#CTANtxfonts"><CITE>38</CITE></A>], which
+contains Greek and other letter-like symbols, as well as a complete
+set of geometric symbols, including the AMS symbols. The <TT>txfonts</TT>
+package also includes a very nice typewriter font, <TT>txtt</TT>.
+Belleek was created by Richard Kinch&nbsp;[<A HREF="#CTANbelleek"><CITE>39</CITE></A><CITE>, </CITE><A HREF="#Belleek"><CITE>40</CITE></A>]
+and is a drop-in replacement for the commercial fonts required by
+the <TT>mathtime</TT> package (now part of PSNFSS&nbsp;[<A HREF="#CTANpsnfss"><CITE>30</CITE></A>]).
+The LaTeX package <TT>mathptmx</TT> (also part of PSNFSS&nbsp;[<A HREF="#CTANpsnfss"><CITE>30</CITE></A>])
+uses Times for Latin letters and Symbol for Greek and other symbols.
+Michel Bovani created the <TT>mbtimes</TT> package by using Omega
+Serif for text and Latin and Greek letters in mathematics. <TT>mbtimes</TT>
+also includes symbol fonts and a set of calligraphic letters. Omega
+Serif is the primary font for Omega, a 16-bit extension of TeX
+by John Plaice and Yannis Haralambous&nbsp;[<A HREF="#Omega"><CITE>43</CITE></A>].<BR>
+<BR>
+The STIX fonts project&nbsp;[<A HREF="#STIX"><CITE>41</CITE></A>] is a collaboration of several
+academic publishers to create a set of Times-compatible fonts containing
+every possible glyph needed for mathematical and technical publishing.
+These fonts are still in development, with a scheduled release in
+the middle of 2006.<BR>
+<BR>
+Note that Adobe Reader 7.0 replaces Times with Adobe Serif MM if Times
+or the Ghostscript equivalent Nimbus Roman No. 9 L is not embedded
+in the PDF file. Adobe Serif MM only has an oblique version, not a
+real italics, and thus, the primary text and Latin letters in mathematics
+will not match letters taken from additional fonts. This problem can
+be avoided by embedding Times or the Ghostscript equivalent Nimbus
+Roman No. 9 L into the PDF file. Also, I have heard (but not personally
+verified) that the Windows version of Adobe Reader displays Times
+New Roman when Times is not embedded. The upright versions of the
+two typefaces are very similar, but the italics are noticeably different
+(consider the <EM>z</EM>, for instance). <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 15: <A NAME="fig:txfonts"></A>Times text with txfonts
+math (<TT>\usepackage[varg]{txfonts}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/txfonts.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 16: <A NAME="fig:Belleek"></A>Times text with Belleek
+math (<TT>\usepackage{mathtime}</TT>; output uses
+the Belleek fonts).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/belleek.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 17: <A NAME="fig:mathptmx"></A>Times text with Symbol
+math (<TT>\usepackage{mathptmx}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/mathptmx.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 18: <A NAME="fig:mbtimes"></A>Omega Serif text with
+Omega math (<TT>\usepackage{mbtimes}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/mbtimes.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BR>
+<BR>
+
+Helvetica, Courier, and Zapf Chancery do not have matching math fonts.
+Courier and Zapf Chancery are inappropriate for mathematics anyway,
+but Helvetica is sometimes used for presentations and posters. The
+free fonts MgOpenModerna&nbsp;[<A HREF="#MgOpenModerna"><CITE>44</CITE></A>] and FreeSans&nbsp;[<A HREF="#FreeSans"><CITE>45</CITE></A>]
+would be natural choices for the Greek letters in a Helvetica mathematics
+font.<BR>
+<BR>
+<!--TOC section Other Free Fonts-->
+
+<H2 CLASS="section"><A NAME="htoc4">4</A>&nbsp;&nbsp;<A NAME="sec:OtherFonts"></A>Other Free Fonts</H2><!--SEC END -->
+
+Several other fonts have been released for use with free open-source
+software. LaTeX packages have been created for most of these fonts.<BR>
+<BR>
+<!--TOC paragraph Bitstream Vera Sans and Arev Sans:-->
+
+<H5 CLASS="paragraph">Bitstream Vera Sans and Arev Sans:</H5><!--SEC END -->
+
+Bitstream Vera was released by Bitstream in cooperation with the Gnome
+Foundation&nbsp;[<A HREF="#vera"><CITE>46</CITE></A>] as a high quality scalable free font for
+use with free open-source software. Bitstream Vera serif, sans serif,
+and sans mono are available in text using the <TT>bera</TT> package
+by Malte Rosenau and Walter&nbsp;A. Schmidt&nbsp;[<A HREF="#CTANbera"><CITE>47</CITE></A>]. Tavmjong
+Bah created Arev Sans&nbsp;[<A HREF="#arev"><CITE>49</CITE></A>] by extending Bitstream Vera Sans
+to include Greek, Cyrillic, and many mathematical symbols. The current
+author created the LaTeX package <TT>arev</TT>&nbsp;[<A HREF="#CTANarev"><CITE>48</CITE></A>]
+using Arev Sans for text and math letters and bold Math Design fonts
+for Bitstream Charter for symbols. <BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 19: <A NAME="fig:Arev"></A>Arev Sans text with Arev
+math (<TT>\usepackage{arev}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/arev.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Bitstream Charter and Math Design:-->
+
+<H5 CLASS="paragraph">Bitstream Charter and Math Design:</H5><!--SEC END -->
+
+Bitstream Charter&nbsp;[<A HREF="#CTANcharter"><CITE>50</CITE></A>] was donated by Bitstream for
+use with X Windows. The Math Design fonts for Bitstream Charter created
+by Paul Pichaureau&nbsp;[<A HREF="#CTANmathdesign"><CITE>51</CITE></A>] are very complete, including
+Greek letters, symbols from Computer Modern, and the AMS symbols.
+Charis SIL&nbsp;[<A HREF="#CharisSIL"><CITE>52</CITE></A>] might be an alternate source for Greek
+letters that match Bitstream Charter more closely. Another possibility
+for a math font is to use the Euler fonts with the <TT>charter</TT>
+and <TT>eulervm</TT> packages.<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 20: <A NAME="fig:chartermd"></A>Bitstream
+Charter text with Math Design math (<TT>\usepackage[charter]{mathdesign}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/chartermd.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Comic Sans:-->
+
+<H5 CLASS="paragraph">Comic Sans:</H5><!--SEC END -->
+
+Comic Sans is one of Microsoft's core web fonts that is freely available&nbsp;[<A HREF="#comicsans"><CITE>53</CITE></A>].
+The <TT>comicsans</TT> package by Scott Pakin&nbsp;[<A HREF="#CTANcomicsans"><CITE>54</CITE></A>]
+implements Comic Sans as both the primary text font and the Latin
+and Greek letters in mathematics. Computer Modern is used for geometric
+symbols that are not present in Comic Sans. Comic Sans is hard to
+read for large blocks of text, but might be nice to use for short
+comments in a handwriting style.<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 21: <A NAME="fig:comicsans"></A>Comic Sans text and
+math (<TT>\usepackage{comicsans}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/comicsans.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph URW Garamond and Math Design: -->
+
+<H5 CLASS="paragraph">URW Garamond and Math Design: </H5><!--SEC END -->
+
+URW Garamond No.&nbsp;8&nbsp;[<A HREF="#CTANgaramond"><CITE>55</CITE></A>] is available under the Aladdin
+Free Public License as part of the GhostPCL project. The Math Design
+fonts for URW Garamond created by Paul Pichaureau&nbsp;[<A HREF="#CTANmathdesign"><CITE>51</CITE></A>]
+are very complete, including Greek letters, symbols from Computer
+Modern, and the AMS symbols.<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 22: <A NAME="fig:garamd"></A>URW Garamond
+text with Math Design math (<TT>\usepackage[garamond]{mathdesign}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/garamondmd.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<!--TOC paragraph Utopia and Fourier or Math Design:-->
+
+<H5 CLASS="paragraph">Utopia and Fourier or Math Design:</H5><!--SEC END -->
+
+Utopia&nbsp;[<A HREF="#CTANutopia"><CITE>56</CITE></A>] was donated by Adobe for use with X Windows.
+Michel Bovani created Fourier-GUTenberg&nbsp;[<A HREF="#CTANfourier"><CITE>57</CITE></A>] as an
+accompaniment to Utopia and is very complete, containing both Greek
+letters and standard and AMS symbols. The Math Design fonts for Utopia
+of Paul Pichaureau&nbsp;[<A HREF="#CTANmathdesign"><CITE>51</CITE></A>] are also very complete,
+including Greek letters and AMS symbols.<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 23: <A NAME="fig:fourier"></A>Utopia text
+with Fourier-GUTenberg math (<TT>\usepackage{fourier}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/fourier.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BLOCKQUOTE CLASS="figure">
+<BR>
+<BR>
+<DIV CLASS="center">Figure 24: <A NAME="fig:utopiamd"></A>Utopia
+text with Math Design math (<TT>\usepackage[utopia]{mathdesign}</TT>).</DIV><BR>
+<BR>
+<DIV CLASS="center">
+ <table align="center" border="1"><tr><td width="0" align="center"><img src="images/utopiamd.png"></td></tr></table></DIV>
+</BLOCKQUOTE>
+<BR>
+<BR>
+
+Using METAFONT, Achim Blumensath created the package <TT>MnSymbol</TT>&nbsp;[<A HREF="#CTANmnsymbol"><CITE>58</CITE></A>],
+which contains geometric symbols (no Greek or other letter-like symbols)
+in varying optical sizes that match the commercial font Adobe MinionPro.
+The <TT>MnSymbol</TT> package also contains traced Type&nbsp;1 versions.
+<TT>MnSymbol</TT> is free; however the package <TT>MinionPro</TT>
+of Achim Blumensath, Andreas Bühmann, and Michael Zedler&nbsp;[<A HREF="#CTANminionpro"><CITE>59</CITE></A>]
+which uses <TT>MnSymbol</TT> requires a license from Adobe for the
+font MininonPro.<BR>
+<BR>
+<!--TOC section Comparison of Features-->
+
+<H2 CLASS="section"><A NAME="htoc5">5</A>&nbsp;&nbsp;<A NAME="sec:Compar"></A>Comparison of Features</H2><!--SEC END -->
+
+Table&nbsp;<A HREF="#cap:FeatureComparison">2</A> shows a comparison of the different
+features in each package. The only packages that have optical sizes
+are Computer Modern, CM Bright, Concrete, Euler, and MnSymbol. Except
+for when the <TT>eulervm</TT> package is used, Latin math letters
+are taken from the italic text font. An asterisk after a font name
+indicates that the package has a version of that style in its own
+font files.
+<BLOCKQUOTE CLASS="table"><DIV CLASS="center"><BR>
+<TABLE CELLSPACING=2 CELLPADDING=0>
+<TR><TD BGCOLOR=black COLSPAN=8><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>&nbsp;Package</TD>
+<TD ALIGN=center NOWRAP>Text</TD>
+<TD ALIGN=center NOWRAP>Greek</TD>
+<TD ALIGN=center NOWRAP>CM sym</TD>
+<TD ALIGN=center NOWRAP>AMS sym</TD>
+<TD ALIGN=center NOWRAP>Calligr</TD>
+<TD ALIGN=center NOWRAP>Blkbd</TD>
+<TD ALIGN=center NOWRAP>boldmath</TD>
+</TR>
+<TR><TD BGCOLOR=black COLSPAN=8><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>computer modern</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>cmbright</TD>
+<TD ALIGN=center NOWRAP>cmbright</TD>
+<TD ALIGN=center NOWRAP>cmbright</TD>
+<TD ALIGN=center NOWRAP>cm*</TD>
+<TD ALIGN=center NOWRAP>cm*</TD>
+<TD ALIGN=center NOWRAP>cm*</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>no</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>ccfonts,eulervm</TD>
+<TD ALIGN=center NOWRAP>concrete</TD>
+<TD ALIGN=center NOWRAP>euler</TD>
+<TD ALIGN=center NOWRAP>euler</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>euler</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>concmath</TD>
+<TD ALIGN=center NOWRAP>concrete</TD>
+<TD ALIGN=center NOWRAP>concrete</TD>
+<TD ALIGN=center NOWRAP>concmath</TD>
+<TD ALIGN=center NOWRAP>concmath</TD>
+<TD ALIGN=center NOWRAP>concmath</TD>
+<TD ALIGN=center NOWRAP>concmath</TD>
+<TD ALIGN=center NOWRAP>no</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>iwona</TD>
+<TD ALIGN=center NOWRAP>iwona</TD>
+<TD ALIGN=center NOWRAP>iwona</TD>
+<TD ALIGN=center NOWRAP>iwona</TD>
+<TD ALIGN=center NOWRAP>iwona</TD>
+<TD ALIGN=center NOWRAP>cm*</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>kurier</TD>
+<TD ALIGN=center NOWRAP>kurier</TD>
+<TD ALIGN=center NOWRAP>kurier</TD>
+<TD ALIGN=center NOWRAP>kurier</TD>
+<TD ALIGN=center NOWRAP>kurier</TD>
+<TD ALIGN=center NOWRAP>cm*</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>anttor</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>kmath,kerkis</TD>
+<TD ALIGN=center NOWRAP>kerkis</TD>
+<TD ALIGN=center NOWRAP>kerkis</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>millennial</TD>
+<TD ALIGN=center NOWRAP>nc schlbk</TD>
+<TD ALIGN=center NOWRAP>millennial</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>no</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>fouriernc</TD>
+<TD ALIGN=center NOWRAP>nc schlbk</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>pxfonts</TD>
+<TD ALIGN=center NOWRAP>palatino</TD>
+<TD ALIGN=center NOWRAP>pxfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts*</TD>
+<TD ALIGN=center NOWRAP>txfonts*</TD>
+<TD ALIGN=center NOWRAP>txfonts*</TD>
+<TD ALIGN=center NOWRAP>pxfonts</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathpazo</TD>
+<TD ALIGN=center NOWRAP>palatino</TD>
+<TD ALIGN=center NOWRAP>pazo</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>pazo</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathpple</TD>
+<TD ALIGN=center NOWRAP>palatino</TD>
+<TD ALIGN=center NOWRAP>euler</TD>
+<TD ALIGN=center NOWRAP>euler</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>times</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>txfonts</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathtime (Belleek)</TD>
+<TD ALIGN=center NOWRAP>times</TD>
+<TD ALIGN=center NOWRAP>belleek</TD>
+<TD ALIGN=center NOWRAP>belleek</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>no</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathptmx</TD>
+<TD ALIGN=center NOWRAP>times</TD>
+<TD ALIGN=center NOWRAP>symbol</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>rsfs</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>no</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mbtimes</TD>
+<TD ALIGN=center NOWRAP>omega</TD>
+<TD ALIGN=center NOWRAP>omega</TD>
+<TD ALIGN=center NOWRAP>mbtimes</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>rsfs*</TD>
+<TD ALIGN=center NOWRAP>esstix</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>arev</TD>
+<TD ALIGN=center NOWRAP>arev</TD>
+<TD ALIGN=center NOWRAP>arev</TD>
+<TD ALIGN=center NOWRAP>md charter</TD>
+<TD ALIGN=center NOWRAP>md charter</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathdesign (Charter)</TD>
+<TD ALIGN=center NOWRAP>charter</TD>
+<TD ALIGN=center NOWRAP>md charter</TD>
+<TD ALIGN=center NOWRAP>md charter</TD>
+<TD ALIGN=center NOWRAP>md charter</TD>
+<TD ALIGN=center NOWRAP>rsfs*</TD>
+<TD ALIGN=center NOWRAP>ams</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>comicsans</TD>
+<TD ALIGN=center NOWRAP>comicsans</TD>
+<TD ALIGN=center NOWRAP>comicsans</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>cm</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathdesign (Garamond)</TD>
+<TD ALIGN=center NOWRAP>garamond</TD>
+<TD ALIGN=center NOWRAP>md garamond</TD>
+<TD ALIGN=center NOWRAP>md garamond</TD>
+<TD ALIGN=center NOWRAP>md garamond</TD>
+<TD ALIGN=center NOWRAP>rsfs*</TD>
+<TD ALIGN=center NOWRAP>ams*</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>utopia</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>fourier</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD ALIGN=left NOWRAP>mathdesign (Utopia)</TD>
+<TD ALIGN=center NOWRAP>utopia</TD>
+<TD ALIGN=center NOWRAP>md garamond</TD>
+<TD ALIGN=center NOWRAP>md utopia</TD>
+<TD ALIGN=center NOWRAP>md utopia</TD>
+<TD ALIGN=center NOWRAP>rsfs*</TD>
+<TD ALIGN=center NOWRAP>ams*</TD>
+<TD ALIGN=center NOWRAP>yes</TD>
+</TR>
+<TR><TD BGCOLOR=black COLSPAN=8><TABLE BORDER=0 WIDTH="100%" CELLSPACING=0 CELLPADDING=1><TR><TD></TD></TR></TABLE></TD>
+</TR></TABLE><BR>
+<BR>
+<DIV CLASS="center"><BR>
+<BR>
+<DIV CLASS="center">Table 2: <A NAME="cap:FeatureComparison"></A>Comparison
+of the features of different packages.</DIV></DIV></DIV></BLOCKQUOTE>
+The only sans serif fonts with matching math fonts are CM Bright and
+Arev Sans. Both work well for presentations. Computer Modern sans
+serif, CM Bright, Arev Sans, Bera Sans, Kerkis Sans, Helvetica, and
+Avant Garde all work well as sans serif fonts that accompany a primary
+roman font. Computer Modern typewriter, <TT>txtt</TT> (from txfonts),
+Luxi Mono&nbsp;[<A HREF="#CTANluximono"><CITE>61</CITE></A>], and Bera Mono all work well as typewriters
+fonts.<BR>
+<BR>
+There are several other free fonts easily used in LaTeX, notably
+the Bera fonts, Luxi Mono, and efont-serif&nbsp;[<A HREF="#efont-serif"><CITE>62</CITE></A>]. Malte
+Rosenau converted the Bitstream Vera fonts into Type&nbsp;1 format, renaming
+the fonts to Bera&nbsp;[<A HREF="#CTANbera"><CITE>47</CITE></A>]. Bera includes serif, sans, and
+mono. Bera Serif does not have a matching italic font, but the DejaVu
+fonts&nbsp;[<A HREF="#dejavu"><CITE>60</CITE></A>] are an extension of Bitstream Vera that include
+a true serif italic, as well as Greek and Cyrillic for all three styles.
+Except for Bera Sans and Arev Sans, none of the previous fonts have
+matching math fonts.<BR>
+<BR>
+<!--TOC section Creation of this Survey-->
+
+<H2 CLASS="section"><A NAME="htoc6">6</A>&nbsp;&nbsp;<A NAME="sec:Creation"></A>Creation of this Survey</H2><!--SEC END -->
+
+It might be technically feasible to create a font survey such as this
+article as a single TeX document. This document, however, was not
+created in that fashion for two reasons. First, it would be an inordinate
+amount of work to switch between fonts within the same document. The
+authors of the LaTeX packages put in a considerable amount of effort
+to set up the fonts for a document, and it would be silly to duplicate
+their work. Second, we want to show to a reader exactly what he or
+she will get by using that package.<BR>
+<BR>
+In order to accomplish these goals, a small LaTeX file (see Figure&nbsp;<A HREF="#cap:SampleLaTeXfile">25</A>
+for an example) was made for each font that loaded the appropriate
+packages and then loaded a common text fragment for display. Each
+file was LaTeXed and then converted to an EPS file using <TT>dvips</TT>
+with the -E option. The -E option creates a tight bounding box around
+the text. The main file <TT>survey.tex</TT> then included each of
+these graphics, and was compiled with <TT>pdflatex</TT>. For some
+reason, <TT>dvips</TT> created an unusable one-page PS file when including
+<TT>mbtimes.eps</TT>. HeVeA was used to convert <TT>survey.tex</TT>
+directly to HTML.<BLOCKQUOTE CLASS="figure">
+<BLOCKQUOTE CLASS="quote">
+<TT>\documentclass{article}</TT>&nbsp;<BR>
+<TT>\include{sampleformat}</TT>&nbsp;<BR>
+<TT>&nbsp;&nbsp;\usepackage{fourier}</TT>&nbsp;<BR>
+<TT>\begin{document}</TT>&nbsp;<BR>
+<TT>&nbsp;&nbsp;\include{textfragment}</TT>&nbsp;<BR>
+<TT>\end{document}</TT>
+</BLOCKQUOTE>
+<BR>
+<BR>
+<DIV CLASS="center">Figure 25: <A NAME="cap:SampleLaTeXfile"></A>Sample
+LaTeX file for <TT>fourier</TT>. The file <TT>sampleformat.tex</TT>
+contains page layout commands, such as setting the margins and removing
+the page numbers. The file <TT>textfragment.tex</TT> contains the
+text and mathematics fragment to be displayed. Both included files
+are used by every sample LaTeX file. The line &#8220;<TT>\usepackage{fourier}</TT>&#8221;
+was changed for each sample to the package listed in the sample's
+caption.</DIV><BR>
+<BR>
+
+</BLOCKQUOTE>
+<!--TOC subsection Acknowledgements-->
+
+<H3 CLASS="subsection">Acknowledgements</H3><!--SEC END -->
+
+Thanks to Michael Zedler, Ulrik Vieth, Karl Berry, William Slough,
+and the anonymous referees for helpful comments.<BR>
+<BR>
+<!--TOC section References-->
+
+<H2 CLASS="section">References</H2><!--SEC END -->
+<DL CLASS="list" COMPACT="compact"><DT CLASS="dt-list">
+<A NAME="CTANfontinstgd"><FONT COLOR=purple>[1]</FONT></A><DD CLASS="dd-list">Philipp Lehman, The Font Installation Guide on <A HREF="http://ctan.tug.org/tex-archive/info/Type1fonts/fontinstallationguide/">CTAN:<TT>/info/Type1fonts/fontinstallationguide</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANmetatype1"><FONT COLOR=purple>[2]</FONT></A><DD CLASS="dd-list">Bogus&#322;aw Jackowski, Janusz M. Nowacki, and Piotr Strzelczyk, MetaType1
+on <A HREF="http://ctan.tug.org/tex-archive/fonts/utilities/metatype1/">CTAN:<TT>/fonts/utilities/metatype1</TT></A>
+<DT CLASS="dt-list"><A NAME="WASmathfonts"><FONT COLOR=purple>[3]</FONT></A><DD CLASS="dd-list">Walter A. Schmidt, Mathematikschriften für LaTeX, <A HREF="http://home.vr-web.de/was/mathfonts.html"><TT>http://home.vr-web.de/was/mathfonts.html</TT></A>.
+<DT CLASS="dt-list"><A NAME="bluesky"><FONT COLOR=purple>[4]</FONT></A><DD CLASS="dd-list">American Mathematical Society (AMS) webpage for Computer Modern Type&nbsp;1
+fonts, <A HREF="http://www.ams.org/tex/type1-fonts.html"><TT>http://www.ams.org/tex/type1-fonts.html</TT></A>.
+<DT CLASS="dt-list"><A NAME="CMBook"><FONT COLOR=purple>[5]</FONT></A><DD CLASS="dd-list">Donald E. Knuth, <EM>Computer Modern Typefaces</EM>, Addison-Wesley
+Pub. Co., 1986.
+<DT CLASS="dt-list"><A NAME="CMRgain"><FONT COLOR=purple>[6]</FONT></A><DD CLASS="dd-list">Raph Levien, Effect of gain on appearance of Computer Modern, <A HREF="http://levien.com/type/cmr/gain.html"><TT>http://levien.com/type/cmr/gain.html</TT></A>.
+<DT CLASS="dt-list"><A NAME="DigTyp"><FONT COLOR=purple>[7]</FONT></A><DD CLASS="dd-list">Donald E. Knuth, <EM>Digital Typography</EM>, Stanford, California:
+Center for the Study of Language and Information, 1999.
+<DT CLASS="dt-list"><A NAME="CTANbluesky"><FONT COLOR=purple>[8]</FONT></A><DD CLASS="dd-list">Blue Sky Research and Y&amp;Y, Inc., Computer Modern Type&nbsp;1 fonts on
+<A HREF="http://ctan.tug.org/tex-archive/fonts/cm/ps-type1/bluesky/">CTAN:<TT>/fonts/cm/ps-type1/bluesky</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANbakoma"><FONT COLOR=purple>[9]</FONT></A><DD CLASS="dd-list">Basil K. Malyshev, BaKoMa Computer Modern Type&nbsp;1 and TrueType fonts
+on <A HREF="http://ctan.tug.org/tex-archive/fonts/cm/ps-type1/bakoma/">CTAN:<TT>/fonts/cm/ps-type1/bakoma</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANec"><FONT COLOR=purple>[10]</FONT></A><DD CLASS="dd-list">Jörg Knappen and Norbert Schwarz, European Computer Modern fonts
+on <A HREF="http://ctan.tug.org/tex-archive/fonts/ec/">CTAN:<TT>/fonts/ec</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANtt2001"><FONT COLOR=purple>[11]</FONT></A><DD CLASS="dd-list">Szabó Péter, Tt2001 fonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/ps-type1/tt2001/">CTAN:<TT>/fonts/ps-type1/tt2001</TT></A>.
+<DT CLASS="dt-list"><A NAME="textrace"><FONT COLOR=purple>[12]</FONT></A><DD CLASS="dd-list">Szabó Péter, webpage for <TT>textrace</TT> and Tt2001 fonts,
+<A HREF="http://www.inf.bme.hu/~pts/textrace"><TT>http://www.inf.bme.hu/~pts/textrace</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANcm-super"><FONT COLOR=purple>[13]</FONT></A><DD CLASS="dd-list">Vladimir Volovich, CM-Super on <A HREF="http://ctan.tug.org/tex-archive/fonts/ps-type1/cm-super/">CTAN:<TT>/fonts/ps-type1/cm-super</TT></A>.
+<DT CLASS="dt-list"><A NAME="CM-Super"><FONT COLOR=purple>[14]</FONT></A><DD CLASS="dd-list">Vladimir Volovich, <A HREF="http://www.tug.org/TUGboat/Articles/tb24-1/volovich.pdf">CM-Super</A>: Automatic
+creation of efficient Type&nbsp;1 fonts from METAFONT  fonts, <EM>TUGboat</EM>,
+24 (1) 2003, 75&ndash;78.
+<DT CLASS="dt-list"><A NAME="CTANlm"><FONT COLOR=purple>[15]</FONT></A><DD CLASS="dd-list">Bogus&#322;aw Jackowski and Janusz M. Nowacki, Latin Modern on <A HREF="http://ctan.tug.org/tex-archive/fonts/ps-type1/lm/">CTAN:<TT>/fonts/ps-type1/lm</TT></A>.
+<DT CLASS="dt-list"><A NAME="LatinModern"><FONT COLOR=purple>[16]</FONT></A><DD CLASS="dd-list">Bogus&#322;aw Jackowski and Janusz M. Nowacki, <A HREF="http://www.tug.org/TUGboat/Articles/tb24-1/jackowski.pdf">Latin
+Modern</A>: Enhancing Computer Modern with accents, accents, accents,
+<EM>TUGboat</EM>, 24 (1) 2003, 64&ndash;74.
+<DT CLASS="dt-list"><A NAME="texpower"><FONT COLOR=purple>[17]</FONT></A><DD CLASS="dd-list">TeXPower LaTeX style files by Stephan Lehmke, <A HREF="http://texpower.sourceforge.net"><TT>http://texpower.sourceforge.net</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANcmbright"><FONT COLOR=purple>[18]</FONT></A><DD CLASS="dd-list">Walter A. Schmidt, CM Bright on <A HREF="http://ctan.tug.org/tex-archive/fonts/cmbright/">CTAN:<TT>/fonts/cmbright</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANhfbright"><FONT COLOR=purple>[19]</FONT></A><DD CLASS="dd-list">Harald Harders, hfbright on <A HREF="http://ctan.tug.org/tex-archive/fonts/ps-type1/hfbright/">CTAN:<TT>/fonts/ps-type1/hfbright</TT></A>.
+<DT CLASS="dt-list"><A NAME="concretebook"><FONT COLOR=purple>[20]</FONT></A><DD CLASS="dd-list">Ronald L. Graham, Donald E. Knuth, and Oren Patashnik, <EM>Concrete
+Mathematics,</EM> Addison-Wesley, 1989.
+<DT CLASS="dt-list"><A NAME="CTANconcmath"><FONT COLOR=purple>[21]</FONT></A><DD CLASS="dd-list">Ulrik Vieth, Concrete Math fonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/concmath/">CTAN:<TT>/fonts/concmath</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANccfonts"><FONT COLOR=purple>[22]</FONT></A><DD CLASS="dd-list">Walter Schmidt, ccfonts on <A HREF="http://ctan.tug.org/tex-archive/macros/latex/contrib/ccfonts/">CTAN:<TT>/macros/latex/contrib/ccfonts</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANeulervm"><FONT COLOR=purple>[23]</FONT></A><DD CLASS="dd-list">Walter Schmidt, eulervm on <A HREF="http://ctan.tug.org/tex-archive/fonts/eulervm/">CTAN:<TT>/fonts/eulervm</TT></A>.
+<DT CLASS="dt-list"><A NAME="eulervm"><FONT COLOR=purple>[24]</FONT></A><DD CLASS="dd-list">Walter Schmidt, <A HREF="http://www.tug.org/TUGboat/Articles/tb23-3-4/tb75schmidt.pdf">Euler-VM</A>: Generic
+math fonts for use with LaTeX, <EM>TUGboat</EM>, 23 (3/4) 2002, 301&ndash;303.
+<DT CLASS="dt-list"><A NAME="CTANiwona"><FONT COLOR=purple>[25]</FONT></A><DD CLASS="dd-list">Janusz M. Nowacki, Iwona on <A HREF="http://ctan.tug.org/tex-archive/fonts/iwona/">CTAN:<TT>/fonts/iwona</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANkurier"><FONT COLOR=purple>[26]</FONT></A><DD CLASS="dd-list">Janusz M. Nowacki, Kurier on <A HREF="http://ctan.tug.org/tex-archive/fonts/kurier/">CTAN:<TT>/fonts/kurier</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANantp"><FONT COLOR=purple>[27]</FONT></A><DD CLASS="dd-list">Janusz M. Nowacki, Antykwa Pó&#322;tawskiego on <A HREF="http://ctan.tug.org/tex-archive/fonts/psfonts/polish/antp/">CTAN:<TT>/fonts/psfonts/polish/antp</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANantt"><FONT COLOR=purple>[28]</FONT></A><DD CLASS="dd-list">Janusz M. Nowacki, Antykwa Toru&#324;ska on <A HREF="http://ctan.tug.org/tex-archive/fonts/antt/">CTAN:<TT>/fonts/antt</TT></A>.
+<DT CLASS="dt-list"><A NAME="AntTorunska"><FONT COLOR=purple>[29]</FONT></A><DD CLASS="dd-list">Janusz M. Nowacki, <A HREF="http://www.tug.org/TUGboat/Articles/tb19-3/tb60antyk.pdf">Antykwa Toru&#324;ska</A>:
+an electronic replica of a Polish traditional type, <EM>TUGboat</EM>,
+19 (3) 1998, 242&ndash;243.
+<DT CLASS="dt-list"><A NAME="CTANpsnfss"><FONT COLOR=purple>[30]</FONT></A><DD CLASS="dd-list">Sebastian Rahtz and Walter A. Schmidt, PSNFSS on <A HREF="http://ctan.tug.org/tex-archive/macros/latex/required/psnfss/">CTAN:<TT>/macros/latex/required/psnfss</TT></A>.
+<DT CLASS="dt-list"><A NAME="Kerkis"><FONT COLOR=purple>[31]</FONT></A><DD CLASS="dd-list">Antonis Tsolomitis, The <A HREF="http://www.tug.org/TUGboat/Articles/tb23-3-4/tb75tsol.pdf">Kerkis</A>
+font family, <EM>TUGboat</EM>, 23 (3/4) 2002, 296&ndash;301.
+<DT CLASS="dt-list"><A NAME="CTANkerkis"><FONT COLOR=purple>[32]</FONT></A><DD CLASS="dd-list">Antonis Tsolomitis, Kerkis on <A HREF="http://ctan.tug.org/tex-archive/fonts/greek/kerkis/">CTAN:<TT>/fonts/greek/kerkis</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANfouriernc"><FONT COLOR=purple>[33]</FONT></A><DD CLASS="dd-list">Michael Zedler, fouriernc on <A HREF="http://ctan.tug.org/tex-archive/fonts/fouriernc/">CTAN:<TT>/fonts/fouriernc</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANpxfonts"><FONT COLOR=purple>[34]</FONT></A><DD CLASS="dd-list">Young Ryu, pxfonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/pxfonts/">CTAN:<TT>/fonts/pxfonts</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANmathpazo"><FONT COLOR=purple>[35]</FONT></A><DD CLASS="dd-list">Diego Puga, Pazo Math fonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/mathpazo/">CTAN:<TT>/fonts/mathpazo</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANfpl"><FONT COLOR=purple>[36]</FONT></A><DD CLASS="dd-list">Ralf Stubner, FPL font on <A HREF="http://ctan.tug.org/tex-archive/fonts/fpl/">CTAN:<TT>/fonts/fpl</TT></A>.
+<DT CLASS="dt-list"><A NAME="fplneu"><FONT COLOR=purple>[37]</FONT></A><DD CLASS="dd-list">Walter Schmidt, FPL Neu package, <A HREF="http://home.vr-web.de/was/x/FPL/"><TT>http://home.vr-web.de/was/x/FPL/</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANtxfonts"><FONT COLOR=purple>[38]</FONT></A><DD CLASS="dd-list">Young Ryu, txfonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/txfonts/">CTAN:<TT>/fonts/txfonts</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANbelleek"><FONT COLOR=purple>[39]</FONT></A><DD CLASS="dd-list">Richard Kinch, Belleek fonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/belleek/">CTAN:<TT>/fonts/belleek</TT></A>.
+<DT CLASS="dt-list"><A NAME="Belleek"><FONT COLOR=purple>[40]</FONT></A><DD CLASS="dd-list">Richard J. Kinch, <A HREF="http://www.tug.org/TUGboat/Articles/tb19-3/tb60kinch.pdf">Belleek</A>: A call
+for METAFONT  revival, <EM>TUGboat</EM>, 19 (3) 1998, 244&ndash;249.
+<DT CLASS="dt-list"><A NAME="STIX"><FONT COLOR=purple>[41]</FONT></A><DD CLASS="dd-list">STIX Fonts project, <A HREF="http://www.stixfonts.org"><TT>http://www.stixfonts.org</TT></A>.
+<DT CLASS="dt-list"><A NAME="mbtimes"><FONT COLOR=purple>[42]</FONT></A><DD CLASS="dd-list">Michel Bovani, mbtimes at <A HREF="ftp://ftp.gutenberg.eu.org/pub/gut/distribs/mbtimes/"><TT>ftp://ftp.gutenberg.eu.org/pub/gut/distribs/mbtimes/</TT></A>.
+<DT CLASS="dt-list"><A NAME="Omega"><FONT COLOR=purple>[43]</FONT></A><DD CLASS="dd-list">John Plaice and Yannis Haralambous, Omega at <A HREF="http://omega.enstb.org"><TT>http://omega.enstb.org</TT></A>.
+<DT CLASS="dt-list"><A NAME="MgOpenModerna"><FONT COLOR=purple>[44]</FONT></A><DD CLASS="dd-list">MgOpenModerna, one of the MgOpen fonts, <A HREF="http://www.ellak.gr/fonts/mgopen"><TT>http://www.ellak.gr/fonts/mgopen</TT></A>.
+<DT CLASS="dt-list"><A NAME="FreeSans"><FONT COLOR=purple>[45]</FONT></A><DD CLASS="dd-list">FreeSans, one of the Free UCS Outline Fonts, <A HREF="http://savannah.nongnu.org/projects/freefont"><TT>http://savannah.nongnu.org/projects/freefont</TT></A>.
+<DT CLASS="dt-list"><A NAME="vera"><FONT COLOR=purple>[46]</FONT></A><DD CLASS="dd-list">Bitstream Vera, released by Bitstream in cooperation with the Gnome
+Foundation, <A HREF="http://www.gnome.org/fonts"><TT>http://www.gnome.org/fonts</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANbera"><FONT COLOR=purple>[47]</FONT></A><DD CLASS="dd-list">Malte Rosenau, Bera Postscript Type&nbsp;1 fonts (converted from Bitstream
+Vera fonts, which necessitated the name change) and LaTeX support
+files by Walter&nbsp;A. Schmidt, on <A HREF="http://ctan.tug.org/tex-archive/fonts/bera/">CTAN:<TT>/fonts/bera</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANarev"><FONT COLOR=purple>[48]</FONT></A><DD CLASS="dd-list">Tavmjong Bah and Stephen Hartke, Arev Sans on <A HREF="http://ctan.tug.org/tex-archive/fonts/arev/">CTAN:<TT>/fonts/arev</TT></A>.
+<DT CLASS="dt-list"><A NAME="arev"><FONT COLOR=purple>[49]</FONT></A><DD CLASS="dd-list">Tavmjong Bah, Arev Sans, <A HREF="http://tavmjong.free.fr/FONTS"><TT>http://tavmjong.free.fr/FONTS</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANcharter"><FONT COLOR=purple>[50]</FONT></A><DD CLASS="dd-list">Bitstream Charter on <A HREF="http://ctan.tug.org/tex-archive/fonts/charter/">CTAN:<TT>/fonts/charter</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANmathdesign"><FONT COLOR=purple>[51]</FONT></A><DD CLASS="dd-list">Paul Pichaureau, Math Design fonts on <A HREF="http://ctan.tug.org/tex-archive/fonts/mathdesign/">CTAN:<TT>/fonts/mathdesign</TT></A>.
+<DT CLASS="dt-list"><A NAME="CharisSIL"><FONT COLOR=purple>[52]</FONT></A><DD CLASS="dd-list">Charis SIL, <A HREF="http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=CharisSILfont"><TT>http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;item_id=CharisSILfont</TT></A>.
+<DT CLASS="dt-list"><A NAME="comicsans"><FONT COLOR=purple>[53]</FONT></A><DD CLASS="dd-list">Comic Sans, part of Microsoft's core web fonts, available at <A HREF="http://corefonts.sourceforge.net/"><TT>http://corefonts.sourceforge.net/</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANcomicsans"><FONT COLOR=purple>[54]</FONT></A><DD CLASS="dd-list">Scott Pakin, Comic Sans LaTeX package on <A HREF="http://ctan.tug.org/tex-archive/macros/latex/contrib/comicsans/">CTAN:<TT>/macros/latex/contrib/comicsans</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANgaramond"><FONT COLOR=purple>[55]</FONT></A><DD CLASS="dd-list">URW Garamond on <A HREF="http://ctan.tug.org/tex-archive/fonts/urw/garamond/">CTAN:<TT>/fonts/urw/garamond</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANutopia"><FONT COLOR=purple>[56]</FONT></A><DD CLASS="dd-list">Adobe Utopia on <A HREF="http://ctan.tug.org/tex-archive/fonts/utopia/">CTAN:<TT>/fonts/utopia</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANfourier"><FONT COLOR=purple>[57]</FONT></A><DD CLASS="dd-list">Michel Bovani, Fourier-GUTenberg on <A HREF="http://ctan.tug.org/tex-archive/fonts/fourier-GUT/">CTAN:<TT>/fonts/fourier-GUT</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANmnsymbol"><FONT COLOR=purple>[58]</FONT></A><DD CLASS="dd-list">Achim Blumensath, MnSymbol on <A HREF="http://ctan.tug.org/tex-archive/fonts/mnsymbol/">CTAN:<TT>/fonts/mnsymbol</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANminionpro"><FONT COLOR=purple>[59]</FONT></A><DD CLASS="dd-list">Achim Blumensath, Andreas Bühmann, and Michael Zedler, MinionPro
+on <A HREF="http://ctan.tug.org/tex-archive/fonts/minionpro/">CTAN:<TT>/fonts/minionpro</TT></A>.
+<DT CLASS="dt-list"><A NAME="dejavu"><FONT COLOR=purple>[60]</FONT></A><DD CLASS="dd-list">DejaVu fonts, <A HREF="http://dejavu.sourceforge.net"><TT>http://dejavu.sourceforge.net</TT></A>.
+<DT CLASS="dt-list"><A NAME="CTANluximono"><FONT COLOR=purple>[61]</FONT></A><DD CLASS="dd-list">Luxi Mono on <A HREF="http://ctan.tug.org/tex-archive/fonts/LuxiMono/">CTAN:<TT>/fonts/LuxiMono</TT></A>.
+<DT CLASS="dt-list"><A NAME="efont-serif"><FONT COLOR=purple>[62]</FONT></A><DD CLASS="dd-list">efont-serif at <A HREF="http://openlab.jp/efont/serif/"><TT>http://openlab.jp/efont/serif/</TT></A>.
+</DL>
+<!--BEGIN NOTES document-->
+<HR WIDTH="50%" SIZE=1><DL CLASS="list"><DT CLASS="dt-list"><A NAME="note1" HREF="#text1"><FONT SIZE=5>1</FONT></A><DD CLASS="dd-list">Copyright 2006 Stephen G.  Hartke. Permission is granted to distribute verbatim or modified copies of this document provided this notice remains intact.<BR>
+An initial version of this article appeared in <EM>The PracTeX Journal,</EM> 1, 2006, <A HREF="http://www.tug.org/pracjourn/2006-1/hartke/"><TT>http://www.tug.org/pracjourn/2006-1/hartke/</TT></A>.<BR>
+The permanent home of this article is <A HREF="http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey"><TT>http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey</TT></A>.
+<DT CLASS="dt-list"><A NAME="note2" HREF="#text2"><FONT SIZE=5>2</FONT></A><DD CLASS="dd-list">Email: lastname @ gmail dot com.
+<DT CLASS="dt-list"><A NAME="note3" HREF="#text3"><FONT SIZE=5>3</FONT></A><DD CLASS="dd-list">Starting with version 6, Adobe Acrobat Reader displays bitmap fonts
+fine. The free PDF viewers Ghostview and xpdf have always displayed
+bitmap fonts accurately.
+<DT CLASS="dt-list"><A NAME="note4" HREF="#text4"><FONT SIZE=5>4</FONT></A><DD CLASS="dd-list">When on screen, the fonts are usually anti-aliased, often into a gray
+blur because the stems are not thick enough to fill a pixel. When
+printed with a high-resolution laser printer, the fonts are shown
+accurately, but I think are too thin. With a medium-resolution printer
+like an inkjet, there's enough resolution to show the form of the
+letters (unlike on screen), but the low-resolution "bulks
+up" the letters compared to a high-resolution laser printer,
+with the letters thus appearing darker.
+</DL>
+<!--END NOTES-->
+<!--HTMLFOOT-->
+<!--ENDHTML-->
+<!--FOOTER-->
+<HR SIZE=2><BLOCKQUOTE CLASS="quote"><EM>This document was translated from LaTeX by
+</EM><A HREF="http://pauillac.inria.fr/~maranget/hevea/index.html"><EM>H<FONT SIZE=2><sup>E</sup></FONT>V<FONT SIZE=2><sup>E</sup></FONT>A</EM></A><EM>.</EM></BLOCKQUOTE></BODY>
+</HTML>
diff --git a/Master/texmf-dist/doc/generic/free-math-font-survey/survey.pdf b/Master/texmf-dist/doc/generic/free-math-font-survey/survey.pdf
new file mode 100644
index 00000000000..49f10b2aa10
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/free-math-font-survey/survey.pdf
diff --git a/Master/texmf-dist/doc/generic/tds/ChangeLog b/Master/texmf-dist/doc/generic/tds/ChangeLog
new file mode 100644
index 00000000000..90d726e479c
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/ChangeLog
@@ -0,0 +1,312 @@
+2004-06-23  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: version 1.1.
+	* tds.tex: make that june 2004.
+
+2004-06-08  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: type3, version 1.096.
+
+2004-06-06  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: 1.095 (still draft).
+
+2004-06-04  Karl Berry  <karl@gnu.org>
+
+	* tds2texi.el [ ] doesn't make sense; changed to "\s ".
+	* tds.tex: use \TeX{} uniformly, not \TeX\ , since that's what
+	tds2texi.el handles.  We ended up with "Inputs for, TeX".
+	Report from: Hans Fredrik Nordhaug,
+	2 Jun 2004 23:01:15 +0200.
+
+	* tds2texi.el (tds2texi-fixup-texinfo): fix the reference to the
+	"Non-font Metafont" node here instead.
+	* tds.sed: no non-font special case.
+	
+	* tds.tex: specify opentype and truetype under fonts.
+
+2004-06-03  Karl Berry  <karl@gnu.org>
+
+	* tds2texi.el (tds2texi-logos-alist): Metafont instead of
+	METAFONT.
+
+2004-05-15  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: doc/ subtree improvements from Chris Rowley, and more.
+
+2004-05-14  Karl Berry  <karl@gnu.org>
+
+	* 1.094.
+	* tds.tex: clarify description of enc & map, maybe.
+
+2004-05-08  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: fixes from Staszek.
+	* tds.tex: check in.
+
+2004-04-03  Karl Berry  <karl@gnu.org>
+
+	* Makefile (packages.zip): new target.
+	(dist): depend on it, and include it in
+	distribution tar file.
+
+	* tds.tex: wording improvement from vojta, 1.093.
+
+2004-03-28  Karl Berry  <karl@gnu.org>
+
+	* tdsguide.cls (\tdsSummary): \let\obeylines=\relax after we set
+	it, so url.sty v3.0's usage of \obeylines does not cause errors.
+
+	* tds.tex (etex): fix in tds example.
+
+2004-03-27  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: 1.092, move extension input files within tex.  also
+	  check in from previous changes, notably new scripts/ dir.
+
+2004-02-11  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: pfm text, etc., from feb03.
+
+2003-02-02    <karl@gnu.org>
+
+	* tds.tex: 1.0
+
+2003-01-18    <karl@gnu.org>
+
+	* Version 0.9998.
+
+	* tds.tex: force line breaks in references, add Downs reference.
+	* tds2texi.el: handle \\ in references section.
+	* Makefile (tds.texi.tmp): don't read emacs init files.
+
+2003-01-17    <karl@gnu.org>
+
+	* tds2texi.el: doc fixes, @tie.
+	* tds.tex: enc/maps vs fontname clarification, removal of some
+	history.
+
+2003-01-12    <karl@gnu.org>
+
+	* tds.tex: first cut at fonts/enc and fonts/map, version 0.9997.
+	* Makefile: clean up directory for dist, and remake everything.
+	* Makefile: use makeinfo --no-split.
+
+Mon Jul 19 16:54:37 1999  Karl Berry  <karl@gnu.org>
+
+	* tds2texi.el (tds2texi-fixup-texinfo): Don't need to do this with
+ 		Emacs 20.4, at least.
+
+Sun Jul 11 12:55:53 1999  Karl Berry  <karl@gnu.org>
+
+	* tds.tex: I have a new address.
+
+Wed Apr 21 15:30:34 1999  Karl Berry  <karl@gnu.org>
+
+	* version 0.9996.
+
+	* tds2texi.el: @ifnottex, not @ifinfo.
+
+	* Grammar fixes (Demitrios Athens).
+	Non-font METAFONT section title (Reinhard Kotucha).
+	Mention Kpathsea as a sample implementation (Paul Abrahams).
+	Allow discretion for single-file packages of all kinds (Matthew Swift).
+	
+	* fancyhdr.sty: get latest version.
+
+1998-01-26  Karl Berry  <karl@cs.umb.edu>
+
+	* tds.tex: Version 0.9995: add extension section.
+
+	* tdsguide.cls (\TeXinfo): Remove unused and incorrect name.
+	(\parsep): Decrease slightly.
+	(\l@section): Decrease section spacing for toc slightly.
+	(\@maketitle): Remove word `draft'.
+
+Fri Jan 23 17:14:01 1998  Karl Berry  <karl@cs.umb.edu>
+
+	* tds.tex: checkin 0.9994.
+
+Sun Jul 20 16:29:37 1997  Karl Berry  <karl@cs.umb.edu>
+
+	* Version 0.9994.
+
+	* tds2texi.el: We can do @ss.
+
+	* tds2texi.el: Texinfo @url is now @uref.
+
+Fri Feb  7 15:47:17 1997  Karl Berry  <karl@cs.umb.edu>
+
+	* tds2texi.el: @detailmenu, other fixes, from Ulrik.
+
+	* tdsguide.cls: Fix : in tdsSummary, more doc.
+
+Tue Feb  4 16:27:56 1997  Karl Berry  <karl@cs.umb.edu>
+
+	* Version 0.9992.
+
+	* tds.tex: Replace gsftopk/ps2pk/etc. with just `modeless'.
+
+Tue Nov 19 01:24:46 1996  Ulrik Vieth  <vieth@thphy.uni-duesseldorf.de>
+
+	* tds.tex: Fix up indentation in `tdsSummary' environments
+	for the sake of Texinfo, should be consistent everywhere now.
+	
+	* tds2texi.el: Fix bug when combining multiple @file tags.
+	Added some missing functionality from tds.sed and tds.awk.
+
+	* tds.sed: Handle a few translations in Elisp where possible.
+  	Only leave those that are specific to document context.
+	
+	* tds.awk: File made redundant.
+
+	* Makefile: Eliminate unnecessary gawk translation step.
+	
+Sat Nov 16 07:16:03 1996  Karl Berry  <karl@cs.umb.edu>
+
+	* tds.tex: Version 0.991.
+
+	* tds2texi.el: More logos; no extra blank lines after sections;
+        handle \url and \email like \path.
+
+	* tds.awk, tds.sed: New files.
+
+	* url.sty, mflogo.sty, Ulogo.fd: Get latest versions.
+
+	* tdsguide.cls: Changes for 0.9991.
+
+Tue Nov 12 17:16:54 1996  Karl Berry  <karl@cs.umb.edu>
+
+	* tdsguide.cls: Saving version as of 0.999.
+
+Sun Nov 10 17:36:36 1996  Karl Berry  <karl@cs.umb.edu>
+
+	* Mention texmf/ini loses.
+	* Say that the mode/ level is not optional.
+
+	* Mention the possibility of doc/<language>.
+	From Sebastian.
+
+	* Include AmiWeb2c 2.0 summary.
+	From: <Scherer@physik.rwth-aachen.de>
+
+	* Allow distribution of modified versions as long they don't
+	pretend to be the TDS.
+
+	* tds.tex: 0.999.
+
+Thu Nov 30 11:41:58 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * tds.tex: pnr10.tfm should be pnr10.mf. From Pierre.
+
+Wed Nov 22 11:46:51 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * tds.tex: Some periods after capital letters end sentences, and
+        some periods after lowercase don't. From bb.
+        Remove make uninstall text.
+
+Tue Nov 21 19:56:35 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * Version 0.999 sent to TUGboat (well, not really).
+
+Wed Nov 15 19:50:37 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * Version 0.104. Public release.
+
+        * tds.tex: Add tex/generic/images to the figure.
+
+Sat Nov 11 11:47:16 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * tds.tex: Mention the possibility of multiple texmf's. Fix
+        non-sentence. From Paul Abrahams.
+
+        * Version 0.103.
+
+        * Move filename constraints to an appendix; we don't require this.
+
+Fri Oct 27 14:04:09 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * Version 0.102.
+
+        * Include package subdirectories under bibtex.
+
+        * Version 0.101.
+
+Tue Oct 17 13:22:08 1995  Karl Berry  <karl@cs.umb.edu>
+
+        - Mention what `texmf' stands for.
+        - Info documents might be stored outside the tree.
+        - Recommend PK specials, rather require them.
+        - Try to define format and package a bit more clearly.
+        - Explicitly unspecify when something is local.
+        These things from Paul Abrahams.
+
+Sat Oct 14 16:07:16 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * Version 0.100.
+
+Fri Oct 13 16:23:34 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * tdsguide.cls (\textwidth): Make a little larger. Don't bother
+        reading tdsguide.cfg just to get mflogo.
+
+        - Mention that a format author doesn't have to have a <format>
+        directory.
+        - Don't use makeindx as an example.
+
+Thu Oct 12 14:19:25 1995  Karl Berry  <karl@cs.umb.edu>
+
+        - Add Christian Spieler to the author list.
+        - Reserve tex/images for eps files etc.
+        - Remove implication the texmf/tex/plain has no subdirectories.
+        - More implementation-specific stuff, this time under
+          `program'. From Alex Kok et al.
+        - Expound on texmf/source a bit. From Alex Kok.
+        - Tell people to go read if we're talking about mysteries
+        - Remove all instances of the confusing word `application'.
+        - Mention that examples are documentation, and move discussion of
+          the alternative to an appendix.
+
+Tue Oct 10 15:45:32 1995  Karl Berry  <karl@cs.umb.edu>
+
+        - New section on duplicate filenames.
+        - Image files are likely to go under texmf/tex.
+        - Printers can have multiple resolutions. From Bernard Gaulle.
+        - Reference the level 0 DVI standard.
+        - Define `dpi' better. From Nelson Beebe, David Kastrup.
+        - Document the reasons for not using modeless/. From David Kastrup.
+        - Mention the (presently impractical) possibility of \input
+          latex2e/file.tex. From Paul Vojta.
+        - make uninstall or an equivalent is desirable. From Alan Dunwell.
+        - Remove `files are...' text. From Doug Waud.
+        - /opt is another likely root. From Jeff Gealow.
+        - Use dpiNNN, not just dpi. From Bart Childs.
+        - Slightly improved description of MP. From Bart.
+        - Recommend . at beginning of search paths. From DEK via Sebastian.
+        - Include musictex as an example generic/ directory.
+
+Mon Oct  9 17:36:27 1995  Karl Berry  <karl@cs.umb.edu>
+
+        - mft/ is no longer a special case under tex/.
+        - Move `package distribution' to an appendix section.
+
+Fri Oct  6 17:23:15 1995  Karl Berry  <karl@cs.umb.edu>
+
+        - Remove \protect. From Ulrik.
+
+Wed Oct  4 15:08:01 1995  Karl Berry  <karl@cs.umb.edu>
+
+        * Version 0.99.
+        - Don't hardwire version number in more than place.
+        - Use TUG instead of O'Reilly for postal mail.
+	- texmf/tex// does not suffice in general.
+	- Incorporate `subdirectory searching syntax' section into main
+	  subdir searching section, and `Expeding the Process' into
+	  `Adoption of the TDS'.
+	- Move bin/ out of the main text.
+	- Reserve `local' at every level.
+	- Top-level directories should be a chapter, and
+	  implementation-specific files need more discussion.
+	- Make macros, fonts, etc. sections under the top-level
+	  directories chapter.
+
diff --git a/Master/texmf-dist/doc/generic/tds/Makefile b/Master/texmf-dist/doc/generic/tds/Makefile
new file mode 100644
index 00000000000..802f45b97c0
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/Makefile
@@ -0,0 +1,44 @@
+# $Id: Makefile,v 1.5 2004/04/04 00:14:59 karl Exp karl $
+# Makefile for tds, by Karl Berry.
+# Public domain.
+
+default all: tds.info tds.html tds.dvi tds.pdf
+
+tds.dvi: tds.tex tdsguide.cls
+	latex '\nonstopmode \input tds'
+
+tds.pdf: tds.tex tdsguide.cls
+	pdflatex '\nonstopmode \input tds'
+
+tds.texi: tds.texi.tmp tds.sed
+	sed -f tds.sed $< >$@
+
+tds.texi.tmp: tds.tex tds2texi.el 
+	emacs -q --no-site -batch -l tds2texi.el -f tds2texi-convert --eval '(write-file "$@")'
+
+tds.info: tds.texi
+	makeinfo --no-split $<
+
+tds_toc.html: tds.texi /usr/local/gnu/bin/texi2html
+	texi2html -split_node -menu $<
+
+tds.html: tds.texi
+	makeinfo --number-sections --html --no-split $<
+
+check:
+	dw <tds.tex
+#	chkdelim <tds.tex
+	ispell -t -l <tds.tex | sort -u
+
+# so that when we're mirrored on CTAN, we don't show up as a good place
+# to get these packages.
+packages.zip: Ulogo.fd fancyhdr.sty mflogo.sty url.sty
+	zip $@ $^
+
+dist: all packages.zip
+#	-rcsdiff -c tds.tex >/tmp/diff
+	rm -f tds.texi* *~ 
+	rm -f tds.cp tds.fn tds.ky tds.pg tds.tp tds.vr tds.log tds.toc
+	tar cvvzf /tmp/tds.tar.gz C* M* tds* index.html packages.zip
+#	shar -z tds.dvi >/tmp/shar
+#	@echo "Now ci -l -m'version' tds.tex and increment the tdsVersion."
diff --git a/Master/texmf-dist/doc/generic/tds/README b/Master/texmf-dist/doc/generic/tds/README
new file mode 100644
index 00000000000..d961e75efc1
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/README
@@ -0,0 +1,17 @@
+This is the TeX Directory Structure (TDS) document, describing a runtime
+layout of TeX-related files intended to be portable,
+implementation-independent, etc.  Most TeX distributions have adopted
+this in some form.
+
+If any questions, comments, or suggestions, email twg-tds@tug.org.
+Mailing list archives available at: http://tug.org/mail-archives/twg-tds/
+
+tds.tex is the master source file.  A few extra LaTeX packages that it
+uses are in packages.zip, in the unlikely event that you don't already
+have them.
+
+http://tug.org/tds/ contains the current released version.  For older
+versions, see ftp://tug.org/historic/docs/tds.  For the current
+development sources, see http://tds.sarovar.org.
+
+Happy installing.
diff --git a/Master/texmf-dist/doc/generic/tds/index.html b/Master/texmf-dist/doc/generic/tds/index.html
new file mode 100644
index 00000000000..a9be53d8abf
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/index.html
@@ -0,0 +1 @@
+<meta http-equiv="refresh" content="0; url=tds.html">
diff --git a/Master/texmf-dist/doc/generic/tds/tds.dvi b/Master/texmf-dist/doc/generic/tds/tds.dvi
new file mode 100644
index 00000000000..ee93dac783d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds.dvi
diff --git a/Master/texmf-dist/doc/generic/tds/tds.html b/Master/texmf-dist/doc/generic/tds/tds.html
new file mode 100644
index 00000000000..49da35a2f5d
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds.html
@@ -0,0 +1,1997 @@
+<html lang="en">
+<head>
+<title>A Directory Structure for TeX Files</title>
+<meta http-equiv="Content-Type" content="text/html">
+<meta name="description" content="A Directory Structure for TeX Files">
+<meta name="generator" content="makeinfo 4.7">
+<link title="Top" rel="top" href="#Top">
+<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
+<meta http-equiv="Content-Style-Type" content="text/css">
+<style type="text/css"><!--
+  pre.display { font-family:inherit }
+  pre.format  { font-family:inherit }
+  pre.smalldisplay { font-family:inherit; font-size:smaller }
+  pre.smallformat  { font-family:inherit; font-size:smaller }
+  pre.smallexample { font-size:smaller }
+  pre.smalllisp    { font-size:smaller }
+  span.sc    { font-variant:small-caps }
+  span.roman { font-family:serif; font-weight:normal; } 
+--></style>
+</head>
+<body>
+<h1 class="settitle">A Directory Structure for TeX Files</h1>
+<div class="node">
+<p><hr>
+<a name="Top"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Introduction">Introduction</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>
+<br>
+</div>
+
+<h2 class="unnumbered">A Directory Structure for TeX Files</h2>
+
+<p>Copyright &copy; 1994, 1995, 1996, 1997, 1998, 1999, 2003, 2004
+TeX Users Group.
+
+   <p>Permission to use, copy, and distribute this document <em>without
+modification</em> for any purpose and without fee is hereby granted,
+provided that this notice appears in all copies.  It is provided &ldquo;as
+is&rdquo; without expressed or implied warranty.
+
+   <p>Permission is granted to copy and distribute modified versions of this
+document under the conditions for verbatim copying, provided that the
+modifications are clearly marked and the document is not represented as
+the official one.
+
+   <p>This document is available on any CTAN host
+(see Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a>). 
+Please send questions or suggestions by email to
+<a href="mailto:tds@tug.org">tds@tug.org</a>.  We welcome all comments.   This is version
+1.1.
+
+<ul class="menu">
+<li><a accesskey="1" href="#Introduction">Introduction</a>
+<li><a accesskey="2" href="#General">General</a>
+<li><a accesskey="3" href="#Top_002dlevel-directories">Top-level directories</a>
+<li><a accesskey="4" href="#Summary">Summary</a>
+<li><a accesskey="5" href="#Unspecified-pieces">Unspecified pieces</a>
+<li><a accesskey="6" href="#Implementation-issues">Implementation issues</a>
+<li><a accesskey="7" href="#Is-there-a-better-way_003f">Is there a better way?</a>
+<li><a accesskey="8" href="#Related-references">Related references</a>
+<li><a accesskey="9" href="#Contributors">Contributors</a>
+
+</li></ul>
+<p>--- The Detailed Node Listing ---
+
+<p>Introduction
+
+</p>
+<ul class="menu">
+<li><a href="#History">History</a>
+<li><a href="#The-role-of-the-TDS">The role of the TDS</a>
+<li><a href="#Conventions">Conventions</a>
+
+</li></ul>
+<p>General
+
+</p>
+<ul class="menu">
+<li><a href="#Subdirectory-searching">Subdirectory searching</a>
+<li><a href="#Rooting-the-tree">Rooting the tree</a>
+<li><a href="#Local-additions">Local additions</a>
+<li><a href="#Duplicate-filenames">Duplicate filenames</a>
+
+</li></ul>
+<p>Top-level directories
+
+</p>
+<ul class="menu">
+<li><a href="#Macros">Macros</a>
+<li><a href="#Fonts">Fonts</a>
+<li><a href="#Non_002dfont-Metafont-files">Non-font Metafont files</a>
+<li><a href="#MetaPost">MetaPost</a>
+<li><a href="#BibTeX">BibTeX</a>
+<li><a href="#Scripts">Scripts</a>
+<li><a href="#Documentation">Documentation</a>
+
+</li></ul>
+<p>Macros
+
+</p>
+<ul class="menu">
+<li><a href="#Extensions">Extensions</a>
+
+</li></ul>
+<p>Fonts
+
+</p>
+<ul class="menu">
+<li><a href="#Font-bitmaps">Font bitmaps</a>
+<li><a href="#Valid-font-bitmaps">Valid font bitmaps</a>
+
+</li></ul>
+<p>Summary
+
+</p>
+<ul class="menu">
+<li><a href="#Documentation-tree-summary">Documentation tree summary</a>
+
+</li></ul>
+<p>Unspecified pieces
+
+</p>
+<ul class="menu">
+<li><a href="#Portable-filenames">Portable filenames</a>
+
+</li></ul>
+<p>Implementation issues
+
+</p>
+<ul class="menu">
+<li><a href="#Adoption-of-the-TDS">Adoption of the TDS</a>
+<li><a href="#More-on-subdirectory-searching">More on subdirectory searching</a>
+<li><a href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>
+
+</li></ul>
+<p>Example implementation-specific trees
+
+</p>
+<ul class="menu">
+<li><a href="#AmiWeb2c-2_002e0">AmiWeb2c 2.0</a>
+<li><a href="#Public-DECUS-TeX">Public DECUS TeX</a>
+<li><a href="#Web2c-7">Web2c 7</a>
+
+</li></ul>
+<p>Is there a better way?
+
+</p>
+<ul class="menu">
+<li><a href="#Macro-structure">Macro structure</a>
+<li><a href="#Font-structure">Font structure</a>
+<li><a href="#Documentation-structure">Documentation structure</a>
+
+</li></ul>
+<p>Font structure
+
+</p>
+<ul class="menu">
+<li><a href="#Font-file-type-location">Font file type location</a>
+<li><a href="#Mode-and-resolution-location">Mode and resolution location</a>
+<li><a href="#Modeless-bitmaps">Modeless bitmaps</a>
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Introduction"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#General">General</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="chapter">1 Introduction</h2>
+
+<p>TeX is a powerful, flexible typesetting system used by many people
+around the world.  It is extremely portable and runs on virtually all
+operating systems.  One unfortunate side effect of TeX's flexibility,
+however, is that there has been no single &ldquo;right&rdquo; way to install it. 
+This has resulted in many sites having different installed arrangements.
+
+   <p>The primary purpose of this document is to describe a standard TeX
+Directory Structure (TDS): a directory hierarchy for macros,
+fonts, and the other implementation-independent TeX system files.  As
+a matter of practicality, this document also suggests ways to
+incorporate the rest of the TeX files into a single structure.  The
+TDS has been designed to work on all modern systems.  In
+particular, the Technical Working Group (TWG) believes it is usable
+under MacOS, MS-DOS, OS/2, Unix, VMS, and
+Windows NT.  We hope that administrators and developers of both
+free and commercial TeX implementations will adopt this standard.
+
+   <p>This document is intended both for the TeX system administrator at a
+site and for people preparing TeX distributions&mdash;everything from a
+complete runnable system to a single macro or style file. It may also
+help TeX users find their way around systems organized this way.  It
+is not a tutorial: we necessarily assume knowledge of the many parts of
+a working TeX system. If you are unfamiliar with any of the programs
+or file formats we refer to, consult the references in
+Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a>.
+
+<ul class="menu">
+<li><a accesskey="1" href="#History">History</a>
+<li><a accesskey="2" href="#The-role-of-the-TDS">The role of the TDS</a>
+<li><a accesskey="3" href="#Conventions">Conventions</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="History"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#The-role-of-the-TDS">The role of the TDS</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Introduction">Introduction</a>
+<br>
+</div>
+
+<h3 class="section">1.1 History</h3>
+
+<p>Version 1.0 of the TDS was released in February 2003.
+
+   <p>Version 1.1 was released in June 2004, with the following non-editorial
+changes:
+
+     <ul>
+<li>Inputs for TeX extensions included under <samp><span class="file">tex</span></samp>, instead
+      of in their own top-level directories (Section&nbsp;<!-- /@w --><a href="#Extensions">Extensions</a>)
+<li>New top-level directory <samp><span class="file">scripts</span></samp> (Section&nbsp;<!-- /@w --><a href="#Scripts">Scripts</a>). 
+<li>New subdirectories <samp><span class="file">lig</span></samp>, <samp><span class="file">opentype</span></samp>,
+      <samp><span class="file">truetype</span></samp>, and <samp><span class="file">type3</span></samp> under <samp><span class="file">fonts</span></samp>
+      (Section&nbsp;<!-- /@w --><a href="#Fonts">Fonts</a>). 
+<li>`<samp><span class="samp">enc</span></samp>',
+<samp><span class="file">lig</span></samp>, and <samp><span class="file">map</span></samp> all use
+      <samp><var>syntax</var><span class="file">/</span><var>package</var></samp> subdirectories
+      (Section&nbsp;<!-- /@w --><a href="#Fonts">Fonts</a>). 
+<li>`<samp><span class="samp">pfm</span></samp>' files specified to go under <samp><span class="file">type1</span></samp>,
+and
+      <samp><span class="file">inf</span></samp> files under <samp><span class="file">afm</span></samp> (Section&nbsp;<!-- /@w --><a href="#Fonts">Fonts</a>). 
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="The-role-of-the-TDS"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Conventions">Conventions</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#History">History</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Introduction">Introduction</a>
+<br>
+</div>
+
+<h3 class="section">1.2 The role of the TDS</h3>
+
+<p>The role of the TDS is to stabilize the organization of
+TeX-related software packages that are installed and in use, possibly
+on multiple platforms simultaneously.
+
+   <p>At first glance, it may seem that the Comprehensive TeX Archive
+Network (CTAN) fulfills at least part of this role, but this is
+not the case.  The role of CTAN is to simplify archiving and
+distribution, not installation and use.
+
+   <p>In fact, the roles of the TDS and CTAN are frequently in
+conflict, as we will see.  For distribution, many different types of
+files must be combined into a single unit; for use, it is traditional to
+segregate files (even similar files) from a single package into
+separate, occasionally distant, directories.
+
+<div class="node">
+<p><hr>
+<a name="Conventions"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#The-role-of-the-TDS">The role of the TDS</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Introduction">Introduction</a>
+<br>
+</div>
+
+<h3 class="section">1.3 Conventions</h3>
+
+<p>In this document, <samp><span class="file">/</span></samp> is used to separate filename components;
+for example, <samp><span class="file">texmf/fonts</span></samp>.  This is the Unix convention but the
+ideas are in no way Unix-specific.
+
+   <p>In this document, &ldquo;TeX&rdquo; generally means the TeX system, including
+Metafont, DVI drivers, utilities, etc., not just the TeX
+program itself.
+
+   <p>The word &ldquo;package&rdquo; in this document has its usual meaning: a set of
+related files distributed, installed, and maintained as a unit.  This is
+<em>not</em> a LaTeX2e package, which is a style file supplementing
+a document class.
+
+   <p>We use the following typographic conventions:
+
+     <ul>
+<li>`<samp><span class="samp">literal</span></samp>'
+Literal text such as <samp><span class="file">filename</span></samp> is
+typeset in typewriter type.
+
+     <li>`<samp><var>replaceable</var></samp>'
+Replaceable text such as
+<samp><var>package</var></samp>, identifying a class of things, is typeset in
+italics inside angle brackets.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="General"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Top_002dlevel-directories">Top-level directories</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Introduction">Introduction</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="chapter">2 General</h2>
+
+<p>This section describes common properties throughout the TDS tree.
+
+<ul class="menu">
+<li><a accesskey="1" href="#Subdirectory-searching">Subdirectory searching</a>
+<li><a accesskey="2" href="#Rooting-the-tree">Rooting the tree</a>
+<li><a accesskey="3" href="#Local-additions">Local additions</a>
+<li><a accesskey="4" href="#Duplicate-filenames">Duplicate filenames</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Subdirectory-searching"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Rooting-the-tree">Rooting the tree</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#General">General</a>
+<br>
+</div>
+
+<h3 class="section">2.1 Subdirectory searching</h3>
+
+<p>Older TeX installations store large numbers of related files in single
+directories, for example, all <samp><span class="file">TFM</span></samp> files and/or all TeX
+input files.
+
+   <p>This monolithic arrangement hinders maintenance of a TeX system: it
+is difficult to determine what files are used by what packages, what
+files need to be updated when a new version is installed, or what files
+should be deleted if a package is removed.  It is also a source of error
+if two or more packages happen to have input files with the same name.
+
+   <p>Therefore, the TWG felt each package should be in a separate
+directory. But we recognized that explicitly listing all directories to
+be searched would be unbearable.  A site may wish to install dozens of
+packages.  Aside from anything else, listing that many directories would
+produce search paths many thousands of characters long, overflowing the
+available space on some systems.
+
+   <p>Also, if all directories are explicitly listed, installing or removing a
+new package would mean changing a path as well as installing or removing
+the actual files.  This would be a time-consuming and error-prone
+operation, even with implementations that provide some way to specify
+the directories to search at runtime.  On systems without runtime
+configuration, it would require recompiling software, an intolerable
+burden.
+
+   <p>As a result, the TWG concluded that a comprehensive TDS
+requires implementations to support some form of implicit subdirectory
+searching.  More precisely, implementations must make it possible to
+specify that TeX, Metafont, and their companion utilities search in both
+a specified directory and recursively through all subdirectories of that
+directory when looking for an input file.  Other forms of subdirectory
+searching, for example recursive-to-one-level searches, may also be
+provided.  We encourage implementors to provide subdirectory searching
+at the option of the installer and user for all paths.
+
+   <p>The TDS does not specify a syntax for specifying recursive
+searching, but we encourage implementors to provide interoperability
+(see Section&nbsp;<!-- /@w --><a href="#More-on-subdirectory-searching">More on subdirectory searching</a>).
+
+<div class="node">
+<p><hr>
+<a name="Rooting-the-tree"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Local-additions">Local additions</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Subdirectory-searching">Subdirectory searching</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#General">General</a>
+<br>
+</div>
+
+<h3 class="section">2.2 Rooting the tree</h3>
+
+<p>In this document, we shall designate the root TDS directory by
+<samp><span class="file">texmf</span></samp> (for &ldquo;TeX and Metafont&rdquo;). We recommend using that name
+where possible, but the actual name of the directory is up to the
+installer. On PC networks, for example, this could map to a
+logical drive specification such as <samp><span class="file">T:</span></samp>.
+
+   <p>Similarly, the location of this directory on the system is
+site-dependent.  It may be at the root of the file system; on Unix
+systems, <samp><span class="file">/usr/local/share</span></samp>, <samp><span class="file">/usr/local</span></samp>,
+<samp><span class="file">/usr/local/lib</span></samp>, and <samp><span class="file">/opt</span></samp> are common choices.
+
+   <p>The name <samp><span class="file">texmf</span></samp> was chosen for several reasons: it reflects the fact
+that the directory contains files pertaining to an entire TeX system
+(including Metafont, MetaPost, BibTeX, etc.), not just TeX itself; and it
+is descriptive of a generic installation rather than a particular
+implementation.
+
+   <p>A site may choose to have more than one TDS hierarchy installed
+(for example, when installing an upgrade). This is perfectly legitimate.
+
+<div class="node">
+<p><hr>
+<a name="Local-additions"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Duplicate-filenames">Duplicate filenames</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Rooting-the-tree">Rooting the tree</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#General">General</a>
+<br>
+</div>
+
+<h3 class="section">2.3 Local additions</h3>
+
+<p>The TDS cannot specify precisely when a package is or is not a
+&ldquo;local addition&rdquo;. Each site must determine this according to its own
+conventions.  At the two extremes, one site might wish to consider
+&ldquo;nonlocal&rdquo; all files not acquired as part of the installed TeX
+distribution; another site might consider &ldquo;local&rdquo; only those files
+that were actually developed at the local site and not distributed
+elsewhere.
+
+   <p>We recognize two common methods for local additions to a distributed
+<samp><span class="file">texmf</span></samp> tree. Both have their place; in fact, some sites employ
+both simultaneously:
+
+     <ol type=1 start=1>
+
+     <li>A completely separate tree which is a TDS structure
+itself; for example, <samp><span class="file">/usr/local/umbtex</span></samp> at the University of
+Massachusetts at Boston. This is another example of the multiple
+<samp><span class="file">texmf</span></samp> hierarchies mentioned in the previous section.
+
+     <li>A directory named <samp><span class="file">local</span></samp> at any appropriate level, for
+example, in the <samp><var>format</var></samp>, <samp><var>package</var></samp>, and
+<samp><var>supplier</var></samp> directories discussed in the following sections. 
+The TDS reserves the directory name <samp><span class="file">local</span></samp> for this
+purpose.
+
+     <p>We recommend using <samp><span class="file">local</span></samp> for site-adapted configuration files,
+such as <samp><span class="file">language.dat</span></samp> for the Babel package or <samp><span class="file">graphics.cfg</span></samp>
+for the graphics package.  Unmodified configuration files from a package
+should remain in the package directory. The intent is to separate
+locally modified or created files from distribution files, to ease
+installing new releases.
+
+        </ol>
+
+   <p>One common case of local additions is dynamically generated files, e.g.,
+PK fonts by the <samp><span class="file">mktexpk</span></samp> script (which originated in
+Dvips as <samp><span class="file">MakeTeXPK</span></samp>).  A site may store the
+generated files directly in any of:
+     <ul>
+<li>their standard location in the main TDS tree (if it can be
+made globally writable);
+
+     <li>an alternative location in the main TDS tree (for
+example, under <samp><span class="file">texmf/fonts/tmp</span></samp>);
+
+     <li>a second complete TDS tree (as outlined above);
+
+     <li>any other convenient directory (perhaps under
+<samp><span class="file">/var</span></samp>, for example <samp><span class="file">/var/spool/fonts</span></samp>).
+
+   </ul>
+
+   <p>No one solution will be appropriate for all sites.
+
+<div class="node">
+<p><hr>
+<a name="Duplicate-filenames"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Local-additions">Local additions</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#General">General</a>
+<br>
+</div>
+
+<h3 class="section">2.4 Duplicate filenames</h3>
+
+<p>Different files by the same name may exist in a TDS tree. The
+TDS generally leaves unspecified which of two files by the same
+name in a search path will be found, so generally the only way to
+reliably find a given file is for it to have a unique name.  However,
+the TDS requires implementations to support the following
+exceptions:
+
+     <ul>
+<li>Names of TeX input files must be unique within each first-level
+subdirectory of <samp><span class="file">texmf/tex</span></samp> and <samp><span class="file">texmf/tex/generic</span></samp>, but not
+within all of <samp><span class="file">texmf/tex</span></samp>; i.e., different TeX formats may have
+files by the same name. (Section&nbsp;<!-- /@w --><a href="#Macros">Macros</a> discusses this
+further.)  Thus, no single format-independent path specification, such
+as a recursive search beginning at <samp><span class="file">texmf/tex</span></samp> specifying no other
+directories, suffices.  So implementations must provide format-dependent
+path specifications, for example via wrapper scripts or configuration
+files.
+
+     <li>Many font files will have the same name (e.g., <samp><span class="file">cmr10.pk</span></samp>),
+as discussed in Section&nbsp;<!-- /@w --><a href="#Valid-font-bitmaps">Valid font bitmaps</a>.  Implementations
+must distinguish these files by mode and resolution.
+
+   </ul>
+
+   <p>All implementations we know of already have these capabilities.
+
+   <p>One place where duplicate names are likely to occur is not an exception:
+
+     <ul>
+<li>Names of Metafont input files (as opposed to bitmaps) must be unique
+within all of <samp><span class="file">texmf/fonts</span></samp>. In practice, this is a problem with
+some variants of Computer Modern which contain slightly modified files
+named <samp><span class="file">punct.mf</span></samp>, <samp><span class="file">romanl.mf</span></samp>, and so on. We believe the only
+feasible solution is to rename the derivative files to be
+unique.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Top_002dlevel-directories"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Summary">Summary</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#General">General</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="chapter">3 Top-level directories</h2>
+
+<p>The directories under the <samp><span class="file">texmf</span></samp> root identify the major components of
+a TeX system (see Section&nbsp;<!-- /@w --><a href="#Summary">Summary</a> for a summary).  A site
+may omit any unneeded directories.
+
+   <p>Although the TDS by its nature can specify precise locations only
+for implementation-independent files, we recognize that installers may
+well wish to place other files under <samp><span class="file">texmf</span></samp> to simplify administration
+of the TeX tree, especially if it is maintained by someone other than
+the system administrator.  Therefore, additional top-level directories
+may be present.
+
+   <p>The top-level directories specified by the TDS are:
+
+     <ul>
+<li>`<samp><span class="samp">tex</span></samp>'
+for TeX files (Section&nbsp;<!-- /@w --><a href="#Macros">Macros</a>).
+
+     <li>`<samp><span class="samp">fonts</span></samp>'
+for font-related files (Section&nbsp;<!-- /@w --><a href="#Fonts">Fonts</a>).
+
+     <li>`<samp><span class="samp">metafont</span></samp>'
+for Metafont files which are not fonts (Section&nbsp;<!-- /@w --><a href="#Non_002dfont-Metafont-files">Non-font Metafont files</a>).
+
+     <li>`<samp><span class="samp">metapost</span></samp>'
+for MetaPost files (Section&nbsp;<!-- /@w --><a href="#MetaPost">MetaPost</a>).
+
+     <li>`<samp><span class="samp">bibtex</span></samp>'
+for BibTeX files (Section&nbsp;<!-- /@w --><a href="#BibTeX">BibTeX</a>).
+
+     <li>`<samp><span class="samp">scripts</span></samp>'
+for platform-independent executables (Section&nbsp;<!-- /@w --><a href="#Scripts">Scripts</a>).
+
+     <li>`<samp><span class="samp">doc</span></samp>'
+for user documentation (Section&nbsp;<!-- /@w --><a href="#Documentation">Documentation</a>).
+
+     <li>`<samp><span class="samp">source</span></samp>'
+for sources.  This includes both traditional
+program sources (for example, Web2C sources go in
+<samp><span class="file">texmf/source/web2c</span></samp>) and, e.g., LaTeX <samp><span class="file">dtx</span></samp> sources (which
+go in <samp><span class="file">texmf/source/latex</span></samp>). The TDS leaves unspecified any
+structure under <samp><span class="file">source</span></samp>.
+
+     <p><samp><span class="file">source</span></samp> is intended for files which are not needed at runtime by
+any TeX program; it should not be included in any search path. For
+example, <samp><span class="file">plain.tex</span></samp> does not belong under <samp><span class="file">texmf/source</span></samp>,
+even though it is a &ldquo;source file&rdquo; in the sense of not being derived
+from another file. (It goes in <samp><span class="file">texmf/tex/plain/base</span></samp>, as explained
+in Section&nbsp;<!-- /@w --><a href="#Macros">Macros</a>).
+
+     <li>`<samp><var>implementation</var></samp>'
+for implementations (examples:
+<samp><span class="file">emtex</span></samp>, <samp><span class="file">vtex</span></samp>, <samp><span class="file">web2c</span></samp>), to be used for whatever
+purpose deemed suitable by the implementor or TeX administrator. 
+That is, files that cannot be shared between implementations, such as
+pool files (<samp><span class="file">tex.pool</span></samp>) and memory dump files (<samp><span class="file">plain.fmt</span></samp>) go
+here, in addition to implementation-wide configuration files.  See
+Section&nbsp;<!-- /@w --><a href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a> for examples of
+real <samp><var>implementation</var></samp> trees.
+
+     <p>Such implementation-specific configuration files should <em>not</em>
+be located using the main TeX input search path (e.g.,
+<samp><span class="file">TEXINPUTS</span></samp>).  This must be reserved for files actually read by a
+TeX engine.  See Section&nbsp;<!-- /@w --><a href="#Extensions">Extensions</a>.
+
+     <li>`<samp><var>program</var></samp>'
+for program-specific input and
+configuration files for any TeX-related programs (examples:
+<samp><span class="file">mft</span></samp>, <samp><span class="file">dvips</span></samp>).  In fact, the <samp><span class="file">tex</span></samp>, <samp><span class="file">metafont</span></samp>,
+<samp><span class="file">metapost</span></samp>, and <samp><span class="file">bibtex</span></samp> items above may all be seen as
+instances of this case.
+
+   </ul>
+
+<ul class="menu">
+<li><a accesskey="1" href="#Macros">Macros</a>
+<li><a accesskey="2" href="#Fonts">Fonts</a>
+<li><a accesskey="3" href="#Non_002dfont-Metafont-files">Non-font Metafont files</a>
+<li><a accesskey="4" href="#MetaPost">MetaPost</a>
+<li><a accesskey="5" href="#BibTeX">BibTeX</a>
+<li><a accesskey="6" href="#Scripts">Scripts</a>
+<li><a accesskey="7" href="#Documentation">Documentation</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Macros"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Fonts">Fonts</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.1 Macros</h3>
+
+<p>TeX macro files shall be stored in separate directories, segregated
+by TeX format and package name (we use `format' in its traditional
+TeX sense to mean a usefully <samp><span class="file">\dump</span></samp>-able package):
+<pre class="example">     texmf/tex/<var>format</var>/<var>package</var>/
+</pre>
+     <ul>
+<li>`<samp><var>format</var></samp>'
+is a format name (examples: <samp><span class="file">amstex</span></samp>,
+<samp><span class="file">latex</span></samp>, <samp><span class="file">plain</span></samp>, <samp><span class="file">texinfo</span></samp>).
+
+     <p>The TDS allows distributions that can be used as either formats or
+packages (e.g., Texinfo, Eplain) to be stored at either level, at the
+option of the format author or TeX administrator. We recommend that
+packages used as formats at a particular site be stored at the
+<samp><var>format</var></samp> level: by adjusting the TeX inputs search path,
+it will be straightforward to use them as macro packages under another
+format, whereas placing them in another tree completely obscures their
+use as a format.
+
+     <p>The TDS reserves the following <samp><var>format</var></samp> names:
+
+          <ul>
+<li>`<samp><span class="samp">generic</span></samp>',
+for input files that are useful across a wide
+range of formats (examples: <samp><span class="file">null.tex</span></samp>, <samp><span class="file">path.sty</span></samp>). 
+Generally, this means any format that uses the category codes of Plain
+TeX and does not rely on any particular format.  This is in contrast
+to those files which are useful only with Plain TeX (which go under
+<samp><span class="file">texmf/tex/plain</span></samp>), e.g., <samp><span class="file">testfont.tex</span></samp> and <samp><span class="file">plain.tex</span></samp>
+itself.
+
+          <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+     </ul>
+
+     <p>Thus, for almost every format, it is necessary to search at least the
+<samp><var>format</var></samp> directory and then the <samp><span class="file">generic</span></samp> directory (in
+that order).  Other directories may need to be searched as well,
+depending on the format.  When using AMS-TeX, for example, the
+<samp><span class="file">amstex</span></samp>, <samp><span class="file">plain</span></samp>, and <samp><span class="file">generic</span></samp> directories should be
+searched, because AMS-TeX is compatible with Plain.
+
+     <li>`<samp><var>package</var></samp>'
+is a TeX package name (examples:
+<samp><span class="file">babel</span></samp>, <samp><span class="file">texdraw</span></samp>).
+
+     <p>In the case where a format consists of only a single file and has no
+auxiliary packages, that file can simply be placed in the
+<samp><var>format</var></samp> directory, instead of
+<samp><var>format</var><span class="file">/base</span></samp>.  For example, Texinfo may go in
+<samp><span class="file">texmf/tex/texinfo/texinfo.tex</span></samp>, not
+<samp><span class="file">texmf/tex/texinfo/base/texinfo.tex</span></samp>.
+
+     <p>The TDS reserves the following <samp><var>package</var></samp> names:
+
+          <ul>
+<li>`<samp><span class="samp">base</span></samp>',
+for the base distribution of each format,
+including files used by INITEX when dumping format files.  For
+example, in the standard LaTeX distribution, the <samp><span class="file">ltx</span></samp> files
+created during the build process.  Another example: the <samp><span class="file">.ini</span></samp>
+driver files for formats used by TeX Live and other distributions.
+
+          <li>`<samp><span class="samp">hyphen</span></samp>',
+for hyphenation patterns, including the original
+American English <samp><span class="file">hyphen.tex</span></samp>.  These are typically used only by
+INITEX.  In most situations, this directory need exist only under the
+<samp><span class="file">generic</span></samp> format.
+
+          <li>`<samp><span class="samp">images</span></samp>',
+for image input files, such as Encapsulated
+PostScript figures. Although it is somewhat non-intuitive for these to
+be under a directory named <samp><span class="file">tex</span></samp>, TeX needs to read these
+files to glean bounding box or other information.  A mechanism for
+sharing image inputs between TeX and other typesetting programs
+(e.g., Interleaf, FrameMaker) is beyond the scope of the
+TDS. In most situations, this directory need exist only under
+the <samp><span class="file">generic</span></samp> format.
+
+          <li>`<samp><span class="samp">local</span></samp>',
+for local additions and configuration files. See
+Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+          <li>`<samp><span class="samp">misc</span></samp>',
+for packages that consist of a single file.  An
+administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using <samp><span class="file">misc</span></samp>.
+
+     </ul>
+
+   </ul>
+
+<ul class="menu">
+<li><a accesskey="1" href="#Extensions">Extensions</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Extensions"></a>Up:&nbsp;<a rel="up" accesskey="u" href="#Macros">Macros</a>
+<br>
+</div>
+
+<h4 class="subsection">3.1.1 Extensions</h4>
+
+<p>TeX has spawned many companion and successor programs (&ldquo;engines&rdquo;),
+such as PDFTeX, Omega, and others.  The TDS specifies
+that the input files for such programs (using a TeX-like syntax) be
+placed within the top-level <samp><span class="file">tex</span></samp> directory, either at the top
+level or within a format subdirectory, even though the original TeX
+program may not be able to read them.  For example:
+
+<pre class="example">     texmf/tex/aleph
+     texmf/tex/enctex
+</pre>
+   <p>This is a change from TDS&nbsp;<!-- /@w -->1.0, which specified top-level
+<samp><var>extension</var></samp> directories for each such program.  We felt the
+new approach is preferable, because:
+
+     <ul>
+<li>Authors of relevant packages typically make their code detect the
+engine being used, and issue error messages or adapt to circumstances
+appropriately.  Furthermore, as a package matures, it may support
+multiple engines.  Thus, a package could conceivably be placed in any of
+several top-level directories, at different times.  Putting all packages
+under the top-level <samp><span class="file">tex</span></samp> directory provides a stable location over
+time.
+
+     <li>Users need to be able to switch between engines, and configuring
+different search paths for each engine is difficult and error-prone.
+
+   </ul>
+
+   <p>Thus, in practice, having different top-level directories caused
+difficulties for everyone involved&mdash;users, package authors, site
+administrators, and system distributors.
+
+   <p>Please contrast this approach with the <samp><var>implementation</var></samp>
+top-level subdirectory (Section&nbsp;<!-- /@w --><a href="#Top_002dlevel-directories">Top-level directories</a>), which
+is to be used for configuration files that (presumably) do not use
+TeX syntax and in any case should not be found along the main TeX
+input search path.
+
+<div class="node">
+<p><hr>
+<a name="Fonts"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Non_002dfont-Metafont-files">Non-font Metafont files</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Macros">Macros</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.2 Fonts</h3>
+
+<p>Font files are stored in separate directories, segregated by file type,
+and then (in most cases) font supplier and typeface.  PK and
+GF files need additional structure, as detailed in the next
+section.
+
+<pre class="example">     texmf/fonts/<var>type</var>/<var>supplier</var>/<var>typeface</var>/
+     texmf/fonts/enc,lig,map/<var>subpath</var>/
+</pre>
+     <ul>
+<li>`<samp><var>type</var></samp>'
+is the type of font file. The TDS
+reserves the following <samp><var>type</var></samp> names for common TeX file
+types:
+
+          <ul>
+<li>`<samp><span class="samp">afm</span></samp>',
+for Adobe font metrics, and <samp><span class="file">inf</span></samp> files. 
+<li>`<samp><span class="samp">gf</span></samp>',
+for generic font bitmap files. 
+<li>`<samp><span class="samp">opentype</span></samp>',
+for OpenType fonts. 
+<li>`<samp><span class="samp">pk</span></samp>',
+for packed bitmap files. 
+<li>`<samp><span class="samp">source</span></samp>',
+for font sources (Metafont files, property lists, etc.). 
+<li>`<samp><span class="samp">tfm</span></samp>',
+for TeX font metric files. 
+<li>`<samp><span class="samp">truetype</span></samp>',
+for TrueType fonts. 
+<li>`<samp><span class="samp">type1</span></samp>',
+for PostScript Type 1 fonts (in <samp><span class="file">pfa</span></samp>,
+      <samp><span class="file">pfb</span></samp>, or any other format), and <samp><span class="file">pfm</span></samp> files. 
+<li>`<samp><span class="samp">type3</span></samp>',
+for PostScript Type 3 fonts. 
+<li>`<samp><span class="samp">vf</span></samp>',
+for virtual fonts. 
+</ul>
+
+     <p>The TDS also reserves the names <samp><span class="file">enc</span></samp>, <samp><span class="file">lig</span></samp>, and
+<samp><span class="file">map</span></samp> for font encoding, ligature, and mapping files, respectively. 
+All of these directories are structured the same way, with
+<samp><var>syntax</var></samp> subdirectories, and then <samp><var>package</var></samp>
+subsubdirectories.  Each of these file types is intended to be searched
+along its own recursively-searched path.  The names of the actual files
+must be unique within their subtree, as usual.  Examples:
+     <pre class="example">          fonts/map/dvipdfm/updmap/dvipdfm.map
+          fonts/map/dvips/lm/lm.map
+          fonts/enc/dvips/base/8r.enc
+     </pre>
+     <p>The Fontname and Dvips packages have more examples of the <samp><span class="file">enc</span></samp> and
+<samp><span class="file">map</span></samp> types.  The <samp><span class="file">afm2pl</span></samp> program uses <samp><span class="file">lig</span></samp> files.
+
+     <p><samp><span class="file">pfm</span></samp> files are included in the <samp><span class="file">type1</span></samp> directory, instead of
+being given their own directory, for two reasons: 1)&nbsp;<!-- /@w -->a <samp><span class="file">.pfm</span></samp> file
+is always an adjunct to a given <samp><span class="file">.pfb</span></samp> file; 2)&nbsp;<!-- /@w -->they must be
+installed from the same directory for Windows programs other than TeX
+to use them.
+
+     <p><samp><span class="file">inf</span></samp> files are included in the <samp><span class="file">afm</span></samp> directory, since
+an <samp><span class="file">inf</span></samp> and <samp><span class="file">afm</span></samp> file can be used to generate a <samp><span class="file">pfm</span></samp>. 
+(Unfortunately, Adobe Type Manager and perhaps other software requires
+that the <samp><span class="file">pfb</span></samp> be in the same directory as <samp><span class="file">afm</span></samp> and
+<samp><span class="file">inf</span></samp> for installation.)
+
+     <p>As usual, a site may omit any of these directories that are unnecessary. 
+<samp><span class="file">gf</span></samp> is a particularly likely candidate for omission.
+
+     <li>`<samp><var>supplier</var></samp>'
+is a name identifying font source
+(examples: <samp><span class="file">adobe</span></samp>, <samp><span class="file">ams</span></samp>, <samp><span class="file">public</span></samp>). The TDS
+reserves the following <samp><var>supplier</var></samp> names:
+
+          <ul>
+<li>`<samp><span class="samp">ams</span></samp>',
+for the American Mathematical Society's AMS-fonts
+collection.
+
+          <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+          <li>`<samp><span class="samp">public</span></samp>',
+for freely redistributable fonts where the supplier
+neither (1)&nbsp;<!-- /@w -->requested their own directory (e.g., <samp><span class="file">ams</span></samp>), nor
+(2)&nbsp;<!-- /@w -->also made proprietary fonts (e.g., <samp><span class="file">adobe</span></samp>).  It does not
+contain all extant freely distributable fonts, nor are all files therein
+necessarily strictly public domain.
+
+          <li>`<samp><span class="samp">tmp</span></samp>',
+for dynamically-generated fonts, as is traditional on
+some systems. It may be omitted if unnecessary, as usual.
+
+     </ul>
+
+     <li>`<samp><var>typeface</var></samp>'
+is the name of a typeface family
+(examples: <samp><span class="file">cm</span></samp>, <samp><span class="file">euler</span></samp>, <samp><span class="file">times</span></samp>). The TDS
+reserves the following <samp><var>typeface</var></samp> names:
+
+          <ul>
+<li>`<samp><span class="samp">cm</span></samp>' (within <samp><span class="file">public</span></samp>),
+for the 75 fonts defined in
+<cite>Computers and Typesetting, Volume&nbsp;<!-- /@w -->E</cite>.
+
+          <li>`<samp><span class="samp">latex</span></samp>' (within <samp><span class="file">public</span></samp>),
+for those fonts distributed
+with LaTeX in the base distribution.
+
+          <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+     </ul>
+
+   </ul>
+
+   <p>Some concrete examples:
+<pre class="example">     texmf/fonts/source/public/pandora/pnr10.mf
+     texmf/fonts/tfm/public/cm/cmr10.tfm
+     texmf/fonts/type1/adobe/utopia/putr.pfa
+</pre>
+   <p>For complete supplier and typeface name lists, consult
+<cite>Filenames for TeX fonts</cite> (see Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a>).
+
+<ul class="menu">
+<li><a accesskey="1" href="#Font-bitmaps">Font bitmaps</a>
+<li><a accesskey="2" href="#Valid-font-bitmaps">Valid font bitmaps</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Font-bitmaps"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Valid-font-bitmaps">Valid font bitmaps</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Fonts">Fonts</a>
+<br>
+</div>
+
+<h4 class="subsection">3.2.1 Font bitmaps</h4>
+
+<p>Font bitmap files require two characteristics in addition to the above
+to be uniquely identifiable: (1)&nbsp;<!-- /@w -->the type of device (i.e., mode) for
+which the font was created; (2)&nbsp;<!-- /@w -->the resolution of the bitmap.
+
+   <p>Following common practice, the TDS segregates fonts with
+different device types into separate directories.  See <samp><span class="file">modes.mf</span></samp>
+in Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a> for recommended mode names.
+
+   <p>Some printers operate at more than one resolution (e.g., at 300<span class="dmn">dpi</span> and
+600<span class="dmn">dpi</span>), but each such resolution will necessarily have a different
+mode name. Nothing further is needed, since implicit in the TeX
+system is the assumption of a single target resolution.
+
+   <p>Two naming strategies are commonly used to identify the resolution of
+bitmap font files.  On systems that allow long filenames (and in the
+original Metafont program itself), the resolution is included in the
+filename (e.g., <samp><span class="file">cmr10.300pk</span></samp>).  On systems which do not support
+long filenames, fonts are generally segregated into directories by
+resolution (e.g., <samp><span class="file">dpi300/cmr10.pk</span></samp>).
+
+   <p>Because the TDS cannot require long filenames, we must use the
+latter scheme for naming fonts. So we have two more subdirectory
+levels under <samp><span class="file">pk</span></samp> and <samp><span class="file">gf</span></samp>:
+
+<pre class="example">     texmf/fonts/pk/<var>mode</var>/<var>supplier</var>/<var>typeface</var>/dpi<var>nnn</var>/
+     texmf/fonts/gf/<var>mode</var>/<var>supplier</var>/<var>typeface</var>/dpi<var>nnn</var>/
+</pre>
+     <ul>
+<li>`<samp><var>mode</var></samp>'
+is a name which identifies the device type
+(examples: <samp><span class="file">cx</span></samp>, <samp><span class="file">ljfour</span></samp>, <samp><span class="file">modeless</span></samp>).  Usually, this is
+the name of the Metafont mode used to build the PK file.  For fonts
+rendered as bitmaps by a program that does not distinguish between
+different output devices, the <samp><var>mode</var></samp> name shall be simply
+<samp><span class="file">modeless</span></samp>.  The <samp><var>mode</var></samp> level shall not be omitted,
+even if only a single mode happens to be in use.
+
+     <li>`<samp><span class="samp">dpi</span><var>nnn</var></samp>'
+specifies the resolution of the font
+(examples: <samp><span class="file">dpi300</span></samp>, <samp><span class="file">dpi329</span></samp>).  <samp><span class="file">dpi</span></samp> stands for
+dots per inch, i.e., pixels per inch. We recognize that pixels per
+millimeter is used in many parts of the world, but dpi is too
+traditional in the TeX world to consider changing now.
+
+     <p>The integer <samp><var>nnn</var></samp> is to be calculated as if using Metafont
+arithmetic and then rounded; i.e., it is the integer Metafont uses in its
+output <samp><span class="file">gf</span></samp> filename.  We recognize small differences in the
+resolution are a common cause of frustration among users, however, and
+recommend implementors follow the level&nbsp;<!-- /@w -->0 DVI driver standard
+(see Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a>) in bitmap font searches by
+allowing a fuzz of +-0.2% (with a minimum of 1) in the
+<samp><var>dpi</var></samp>.
+
+   </ul>
+
+   <p>Implementations may provide extensions to the basic naming scheme, such
+as long filenames (as in the original Metafont) and font library files (as
+in emTeX's <samp><span class="file">.fli</span></samp> files), provided that the basic scheme is also
+supported.
+
+<div class="node">
+<p><hr>
+<a name="Valid-font-bitmaps"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Font-bitmaps">Font bitmaps</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Fonts">Fonts</a>
+<br>
+</div>
+
+<h4 class="subsection">3.2.2 Valid font bitmaps</h4>
+
+<p>The TWG recognizes that the use of short filenames has many
+disadvantages.  The most vexing is that it results in the creation of
+dozens of different files with the same name.  At a typical site,
+<samp><span class="file">cmr10.pk</span></samp> will be the filename for Computer Modern Roman 10<span class="dmn">pt</span> at
+5&ndash;10 magnifications for 2&ndash;3 modes. (Section&nbsp;<!-- /@w --><a href="#Duplicate-filenames">Duplicate filenames</a> discusses duplicate filenames in general.)
+
+   <p>To minimize this problem, we strongly recommend that PK files
+contain enough information to identify precisely how they were created:
+at least the mode, base resolution, and magnification used to create the
+font.
+
+   <p>This information is easy to supply: a simple addition to the local modes
+used for building the fonts with Metafont will automatically provide the
+required information.  If you have been using a local modes file derived
+from (or that is simply) <samp><span class="file">modes.mf</span></samp> (see Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a>), the required information is already in your PK
+files.  If not, a simple addition based on the code found in
+<samp><span class="file">modes.mf</span></samp> can be made to your local modes file and the PK
+files rebuilt.
+
+<div class="node">
+<p><hr>
+<a name="Non_002dfont-Metafont-files"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#MetaPost">MetaPost</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Fonts">Fonts</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.3 Non-font Metafont files</h3>
+
+<p>Most Metafont input files are font programs or parts of font programs and
+are thus covered by the previous section. However, a few non-font input
+files do exist. Such files shall be stored in:
+
+<pre class="example">     texmf/metafont/<var>package</var>/
+</pre>
+   <p><samp><var>package</var></samp> is the name of a
+Metafont package (for example, <samp><span class="file">mfpic</span></samp>).
+
+   <p>The TDS reserves the following <samp><var>package</var></samp> names:
+
+     <ul>
+<li>`<samp><span class="samp">base</span></samp>',
+for the standard Metafont macro files as described in
+<cite>The Metafontbook</cite>, such as <samp><span class="file">plain.mf</span></samp> and <samp><span class="file">expr.mf</span></samp>.
+
+     <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+     <li>`<samp><span class="samp">misc</span></samp>',
+for Metafont packages consisting of only a single file
+(for example, <samp><span class="file">modes.mf</span></samp>).  An administrator or package maintainer
+may create directories for single-file packages at their discretion,
+instead of using <samp><span class="file">misc</span></samp>.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="MetaPost"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#BibTeX">BibTeX</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Non_002dfont-Metafont-files">Non-font Metafont files</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.4 MetaPost</h3>
+
+<p>MetaPost is a picture-drawing language developed by John Hobby, derived
+from Knuth's Metafont. Its primary purpose is to output Encapsulated PostScript
+instead of bitmaps.
+
+   <p>MetaPost input files and the support files for MetaPost-related utilities
+shall be stored in:
+
+<pre class="example">     texmf/metapost/<var>package</var>/
+</pre>
+   <p><samp><var>package</var></samp> is the name of a MetaPost package.  At the present
+writing none exist, but the TWG thought it prudent to leave room
+for contributed packages that might be written in the future.
+
+   <p>The TDS reserves the following <samp><var>package</var></samp> names:
+
+     <ul>
+<li>`<samp><span class="samp">base</span></samp>',
+for the standard MetaPost macro files, such as
+<samp><span class="file">plain.mp</span></samp>, <samp><span class="file">mfplain.mp</span></samp>, <samp><span class="file">boxes.mp</span></samp>, and
+<samp><span class="file">graph.mp</span></samp>.  This includes files used by INIMP when dumping mem
+files containing preloaded macro definitions.
+
+     <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+     <li>`<samp><span class="samp">misc</span></samp>',
+for MetaPost packages consisting of only a single file. 
+An administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using <samp><span class="file">misc</span></samp>.
+
+     <li>`<samp><span class="samp">support</span></samp>',
+for additional input files required by MetaPost
+utility programs, including a font map, a character adjustment table,
+and a subdirectory containing low-level MetaPost programs for rendering
+some special characters.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="BibTeX"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Scripts">Scripts</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#MetaPost">MetaPost</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.5 BibTeX</h3>
+
+<p>BibTeX-related files shall be stored in:
+
+<pre class="example">     texmf/bibtex/bib/<var>package</var>/
+     texmf/bibtex/bst/<var>package</var>/
+</pre>
+   <p>The <samp><span class="file">bib</span></samp> directory is for BibTeX database (<samp><span class="file">.bib</span></samp>) files,
+the <samp><span class="file">bst</span></samp> directory for style (<samp><span class="file">.bst</span></samp>) files.
+
+   <p><samp><var>package</var></samp> is the name of a BibTeX package.  The
+TDS reserves the following <samp><var>package</var></samp> names (the same
+names are reserved under both <samp><span class="file">bib</span></samp> and <samp><span class="file">bst</span></samp>):
+
+     <ul>
+<li>`<samp><span class="samp">base</span></samp>',
+for the standard BibTeX databases and styles, such
+as <samp><span class="file">xampl.bib</span></samp>, <samp><span class="file">plain.bst</span></samp>.
+
+     <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+     <li>`<samp><span class="samp">misc</span></samp>',
+for BibTeX packages consisting of only a single
+file.  An administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using <samp><span class="file">misc</span></samp>.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Scripts"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Documentation">Documentation</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#BibTeX">BibTeX</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.6 Scripts</h3>
+
+<p>The top-level <samp><span class="file">scripts</span></samp> directory is for platform-independent
+executables, such as Perl, Python, and shell scripts, and Java class
+files.  Subdirectories under <samp><span class="file">scripts</span></samp> are package names.  This
+eases creating distributions, by providing a common place for such
+platform-independent programs.
+
+   <p>The intent is not for all such directories to be added to a user's
+command search path, which would be quite impractical.  Rather, these
+executables are primarily for the benefit of wrapper scripts in whatever
+executable directory a distribution may provide (which is not specified
+by the TDS).
+
+   <p>Truly auxiliary scripts which are invoked directly by other programs,
+rather than wrapper scripts, may also be placed here.  That is,
+<samp><span class="file">scripts</span></samp> also serves as a platform-independent analog of the
+standard Unix <samp><span class="file">libexec</span></samp> directory.
+
+   <p>We recommend using extensions specifying the language (such as
+<samp><span class="file">.pl</span></samp>, <samp><span class="file">.py</span></samp>, <samp><span class="file">.sh</span></samp>) on these files, to help uniquely
+identify the name.  Since the intent of the TDS is for programs
+in <samp><span class="file">scripts</span></samp> not to be invoked directly by users, this poses no
+inconvenience.
+
+   <p>For example, in the TeX Live distribution, the ConTeXt user-level
+program <samp><span class="file">texexec</span></samp> can exist as a small wrapper script in each
+<samp><span class="file">bin/</span><var>platform</var><span class="file">/texexec</span></samp> (which is outside the
+<samp><span class="file">texmf</span></samp> tree), which merely finds and calls
+<samp><span class="file">texmf/scripts/context/perl/texexec.pl</span></samp>.
+
+   <p>Examples:
+<pre class="example">     scripts/context/perl/texexec.pl
+     scripts/context/ruby/examplex.rb
+     scripts/thumbpdf/thumbpdf.pl
+</pre>
+   <p>The TDS does not specify a location for platform-dependent
+binary executables, whether auxiliary or user-level.
+
+<div class="node">
+<p><hr>
+<a name="Documentation"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Scripts">Scripts</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top_002dlevel-directories">Top-level directories</a>
+<br>
+</div>
+
+<h3 class="section">3.7 Documentation</h3>
+
+<p>Most packages come with some form of documentation: user manuals,
+example files, programming guides, etc.  In addition, many independent
+files not part of any macro or other package have been created to
+describe various aspects of the TeX system.
+
+   <p>The TDS specifies that these additional documentation files shall
+be stored in a structure that parallels to some extent the
+<samp><span class="file">fonts</span></samp> and <samp><span class="file">tex</span></samp> directories, as follows:
+
+<pre class="example">     texmf/doc/<var>category</var>/...
+</pre>
+   <p><samp><var>category</var></samp> identifies the general topic of documentation
+that resides below it; for example, a TeX format name (<samp><span class="file">latex</span></samp>),
+program name (<samp><span class="file">bibtex</span></samp>, <samp><span class="file">tex</span></samp>), language (<samp><span class="file">french</span></samp>,
+<samp><span class="file">german</span></samp>), a file format (<samp><span class="file">info</span></samp>, <samp><span class="file">man</span></samp>), or other system
+components (<samp><span class="file">web</span></samp>, <samp><span class="file">fonts</span></samp>).
+
+   <p>One possible arrangement is to organize <samp><span class="file">doc</span></samp> by language, with all
+the other category types below that.  This helps users find
+documentation in the language(s) in which they are fluent.  Neither this
+nor any other particular arrangement is required, however.
+
+   <p>Within each <samp><var>category</var></samp> tree for a TeX format, the
+directory <samp><span class="file">base</span></samp> is reserved for base documentation distributed by
+the format's maintainers.
+
+   <p>The TDS reserves the following category names:
+
+     <ul>
+<li>`<samp><span class="samp">general</span></samp>',
+for standalone documents not specific to any
+particular program (for example, Joachim Schrod's <cite>Components
+of TeX</cite>).
+
+     <li>`<samp><span class="samp">help</span></samp>',
+for meta-information, such as FAQ's,
+the TeX Catalogue, etc.
+
+     <li>`<samp><span class="samp">info</span></samp>',
+for processed Texinfo documents.  (Info files, like
+anything else, may also be stored outside the TDS, at the
+installer's option.)
+
+     <li>`<samp><span class="samp">local</span></samp>',
+for local additions. See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a>.
+
+   </ul>
+
+   <p>The <samp><span class="file">doc</span></samp> directory is intended for implementation-independent and
+operating system-independent documentation
+files. Implementation-dependent files are best stored elsewhere, as
+provided for by the implementation and/or TeX administrator (for
+example, VMS help files under <samp><span class="file">texmf/vms/help</span></samp>).
+
+   <p>The documentation directories may contain TeX sources, DVI
+files, PostScript files, text files, example input files, or any other useful
+documentation format(s).
+
+   <p>See Section&nbsp;<!-- /@w --><a href="#Documentation-tree-summary">Documentation tree summary</a> for a summary.
+
+<div class="node">
+<p><hr>
+<a name="Summary"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Unspecified-pieces">Unspecified pieces</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top_002dlevel-directories">Top-level directories</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="chapter">4 Summary</h2>
+
+<p>A skeleton of a TDS <samp><span class="file">texmf</span></samp> directory tree.  This is not to
+imply these are the only entries allowed.  For example, <samp><span class="file">local</span></samp> may
+occur at any level.
+
+<pre class="example">       bibtex/           BibTeX input files
+         bib/            BibTeX databases
+           base/         base distribution (e.g., <samp><span class="file">xampl.bib</span></samp>)
+           misc/         single-file databases
+         &lt;package&gt;/      name of a package
+         bst/            BibTeX style files
+           base/         base distribution (e.g., <samp><span class="file">plain.bst</span></samp>, <samp><span class="file">acm.bst</span></samp>)
+           misc/         single-file styles
+         &lt;package&gt;/      name of a package
+       doc/              see Section&nbsp;<!-- /@w --><a href="#Documentation">Documentation</a> and the summary below
+       fonts/            font-related files
+         &lt;type&gt;/         file type (e.g., <samp><span class="file">pk</span></samp>)
+           &lt;mode&gt;/       type of output device (for <samp><span class="file">pk</span></samp> and <samp><span class="file">gf</span></samp> only)
+             &lt;supplier&gt;/     name of a font supplier (e.g., <samp><span class="file">public</span></samp>)
+               &lt;typeface&gt;/   name of a typeface (e.g., <samp><span class="file">cm</span></samp>)
+                 dpi&lt;nnn&gt;/   font resolution (for <samp><span class="file">pk</span></samp> and <samp><span class="file">gf</span></samp> only)
+       &lt;implementation&gt;/ TeX implementations, by name (e.g., <samp><span class="file">emtex</span></samp>)
+       local/            files created or modified at the local site
+       metafont/         Metafont (non-font) input files
+         base/           base distribution (e.g., <samp><span class="file">plain.mf</span></samp>)
+         misc/           single-file packages (e.g., <samp><span class="file">modes.mf</span></samp>)
+         &lt;package&gt;/      name of a package (e.g., <samp><span class="file">mfpic</span></samp>)
+       metapost/         MetaPost input and support files
+         base/           base distribution (e.g., <samp><span class="file">plain.mp</span></samp>)
+         misc/           single-file packages
+         &lt;package&gt;/      name of a package
+         support/        support files for MetaPost-related utilities
+       mft/              <samp><span class="file">MFT</span></samp> inputs (e.g., <samp><span class="file">plain.mft</span></samp>)
+       &lt;program&gt;/        TeX-related programs, by name (e.g., <samp><span class="file">dvips</span></samp>)
+       source/           program source code by name (e.g., <samp><span class="file">latex</span></samp>, <samp><span class="file">web2c</span></samp>)
+       tex/              TeX input files
+         &lt;engine&gt;/       name of an engine (e.g., <samp><span class="file">aleph</span></samp>); can also be lower
+         &lt;format&gt;/       name of a format (e.g., <samp><span class="file">plain</span></samp>)
+           base/         base distribution for format (e.g., <samp><span class="file">plain.tex</span></samp>)
+           misc/         single-file packages (e.g., <samp><span class="file">webmac.tex</span></samp>)
+           local/        local additions to or local configuration files for <samp><var>format</var></samp>
+           &lt;package&gt;/    name of a package (e.g., <samp><span class="file">graphics</span></samp>, <samp><span class="file">mfnfss</span></samp>)
+         generic/        format-independent packages
+           hyphen/       hyphenation patterns (e.g., <samp><span class="file">hyphen.tex</span></samp>)
+           images/       image input files (e.g., Encapsulated PostScript)
+           misc/         single-file format-independent packages (e.g., <samp><span class="file">null.tex</span></samp>).
+           &lt;package&gt;/    name of a package (e.g., <samp><span class="file">babel</span></samp>)
+</pre>
+   <ul class="menu">
+<li><a accesskey="1" href="#Documentation-tree-summary">Documentation tree summary</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Documentation-tree-summary"></a>Up:&nbsp;<a rel="up" accesskey="u" href="#Summary">Summary</a>
+<br>
+</div>
+
+<h3 class="section">4.1 Documentation tree summary</h3>
+
+<p>An example skeleton of a TDS directory tree under
+<samp><span class="file">texmf/doc</span></samp>.  This is not to imply these are the only entries
+allowed, or that this structure must be followed precisely for the
+entries listed.
+
+   <p>As mentioned, the <samp><span class="file">texmf/doc</span></samp> tree may be organized by language, so
+that all documentation in French, say, is in a <samp><span class="file">french</span></samp>
+subdirectory.  In that case, the example structure here would be in a
+given language directory.
+
+<pre class="example">       ams/
+         amsfonts/       <samp><span class="file">amsfonts.faq</span></samp>, <samp><span class="file">amfndoc</span></samp>
+         amslatex/       <samp><span class="file">amslatex.faq</span></samp>, <samp><span class="file">amsldoc</span></samp>
+         amstex/         <samp><span class="file">amsguide</span></samp>, <samp><span class="file">joyerr</span></samp>
+       bibtex/           BibTeX
+         base/           <samp><span class="file">btxdoc.tex</span></samp>
+       fonts/
+         fontname/       <cite>Filenames for TeX fonts</cite>
+         oldgerm/        <samp><span class="file">corkpapr</span></samp>
+       &lt;format&gt;/         name of a TeX format (e.g., <samp><span class="file">generic</span></samp>, <samp><span class="file">latex</span></samp>)
+         base/           for the base distribution
+         misc/           for contributed single-file package documentation
+         &lt;package&gt;/      for <em>package</em>
+       general/          across programs, generalities
+         errata/         <samp><span class="file">errata</span></samp>, <samp><span class="file">errata[1-8]</span></samp>
+         texcomp/        <cite>Components of TeX</cite>
+       help/             meta-information
+         ctan/           info about CTAN mirror sites
+         faq/            FAQs of <samp><span class="file">comp.text.tex</span></samp>, etc.
+       info/             GNU Info files, made from Texinfo sources
+       latex/            example of <samp><var>format</var></samp>
+         base/           <samp><span class="file">ltnews*</span></samp>, <samp><span class="file">*guide</span></samp>, etc.
+         graphics/       <samp><span class="file">grfguide</span></samp>
+       local/            site-specific documentation
+       man/              Unix man pages
+       &lt;program&gt;/        TeX-related programs, by name (examples follow)
+       metafont/         <samp><span class="file">mfbook.tex</span></samp>, <samp><span class="file">metafont-for-beginners</span></samp>, etc.
+       metapost/         <samp><span class="file">mpman</span></samp>, <samp><span class="file">manfig</span></samp>, etc.
+       tex/              <samp><span class="file">texbook.tex</span></samp>, <cite>A Gentle Introduction to TeX</cite>, etc.
+       web/              <samp><span class="file">webman</span></samp>, <samp><span class="file">cwebman</span></samp>
+</pre>
+   <div class="node">
+<p><hr>
+<a name="Unspecified-pieces"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Implementation-issues">Implementation issues</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Summary">Summary</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="appendix">Appendix A Unspecified pieces</h2>
+
+<p>The TDS cannot address the following aspects of a functioning
+TeX system:
+
+     <ol type=1 start=1>
+
+     <li>The location of executable programs: this is too site-dependent
+even to recommend a location, let alone require one. A site may place
+executables outside the <samp><span class="file">texmf</span></samp> tree altogether (e.g.,
+<samp><span class="file">/usr/local/bin</span></samp>), in a platform-dependent directory within
+<samp><span class="file">texmf</span></samp>, or elsewhere.
+
+     <li>Upgrading packages when new releases are made: we could find no
+way of introducing version specifiers into <samp><span class="file">texmf</span></samp> that would do more
+good than harm, or that would be practical for even a plurality of
+installations.
+
+     <li>The location of implementation-specific files (e.g., TeX
+<samp><span class="file">.fmt</span></samp> files): by their nature, these must be left to the
+implementor or TeX maintainer. See Section&nbsp;<!-- /@w --><a href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>.
+
+     <li>Precisely when a package or file should be considered &ldquo;local&rdquo;,
+and where such local files are installed.  See Section&nbsp;<!-- /@w --><a href="#Local-additions">Local additions</a> for more discussion.
+
+        </ol>
+
+<ul class="menu">
+<li><a accesskey="1" href="#Portable-filenames">Portable filenames</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Portable-filenames"></a>Up:&nbsp;<a rel="up" accesskey="u" href="#Unspecified-pieces">Unspecified pieces</a>
+<br>
+</div>
+
+<h3 class="section">A.1 Portable filenames</h3>
+
+<p>The TDS cannot require any particular restriction on filenames in
+the tree, since the names of many existing TeX files conform to no
+standard scheme. For the benefit of people who wish to make a portable
+TeX distribution or installation, however, we outline here the
+necessary restrictions. The TDS specifications themselves are
+compatible with these.
+
+   <p>ISO-9660 is the only universally acceptable file system format
+for CD-ROMs.  A subset thereof meets the stringent limitations of
+all operating systems in use today. It specifies the following:
+
+     <ul>
+<li>File and directory names, not including any directory path or
+extension part, may not exceed eight characters.
+
+     <li>Filenames may have a single extension.  Extensions may not exceed
+three characters. Directory names may not have an extension.
+
+     <li>Names and extensions may consist of <em>only</em> the characters
+<samp><span class="file">A</span></samp>&ndash;<samp><span class="file">Z</span></samp>, <samp><span class="file">0</span></samp>&ndash;<samp><span class="file">9</span></samp>, and underscore. 
+Lowercase letters are excluded.
+
+     <li>A period separates the filename from the extension and is always
+present, even if the name or extension is missing (e.g.,
+<samp><span class="file">FILENAME.</span></samp> or <samp><span class="file">.EXT</span></samp>).
+
+     <li>A version number, ranging from 1&ndash;32767, is appended to the file
+extension, separated by a semicolon (e.g., <samp><span class="file">FILENAME.EXT;1</span></samp>).
+
+     <li>Only eight directory levels are allowed, including the top-level
+(mounted) directory (see Section&nbsp;<!-- /@w --><a href="#Rooting-the-tree">Rooting the tree</a>).  Thus, the
+deepest valid ISO-9660 path is:
+     <pre class="example">          texmf/L2/L3/L4/L5/L6/L7/L8/FOO.BAR;1
+          1     2  3  4  5  6  7  8
+     </pre>
+     <p>The deepest TDS path needs only seven levels:
+     <pre class="example">          texmf/fonts/pk/cx/public/cm/dpi300/cmr10.pk
+          1     2     3  4  5      6  7
+     </pre>
+     </ul>
+
+   <p>Some systems display a modified format of ISO-9660 names,
+mapping alphabetic characters to lowercase, removing version numbers and
+trailing periods, etc.
+
+   <p>Before the December 1996 release, LaTeX used mixed-case names for
+font descriptor files.  Fortunately, it never relied on case alone to
+distinguish among the files.  Nowadays, it uses only monocase names.
+
+<div class="node">
+<p><hr>
+<a name="Implementation-issues"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Is-there-a-better-way_003f">Is there a better way?</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Unspecified-pieces">Unspecified pieces</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="appendix">Appendix B Implementation issues</h2>
+
+<p>We believe that the TDS can bring a great deal of order to the
+current anarchic state of many TeX installations.  In addition, by
+providing a common frame of reference, it will ease the burden of
+documenting administrative tasks.  Finally, it is a necessary part of
+any reasonable system of true &ldquo;drop-in&rdquo; distribution packages for
+TeX.
+
+<ul class="menu">
+<li><a accesskey="1" href="#Adoption-of-the-TDS">Adoption of the TDS</a>
+<li><a accesskey="2" href="#More-on-subdirectory-searching">More on subdirectory searching</a>
+<li><a accesskey="3" href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Adoption-of-the-TDS"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#More-on-subdirectory-searching">More on subdirectory searching</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Implementation-issues">Implementation issues</a>
+<br>
+</div>
+
+<h3 class="section">B.1 Adoption of the TDS</h3>
+
+<p>[This section is retained for historical purposes; the TDS
+is now quite firmly entrenched in most TeX distributions.]
+
+   <p>We recognize that adoption of the TDS will not be immediate or
+universal.  Most TeX administrators will not be inclined to make the
+final switch until:
+
+     <ul>
+<li>Clear and demonstrable benefits can be shown for the TDS. 
+<li>TDS-compliant versions of all key programs are available
+in ported, well-tested forms. 
+<li>A &ldquo;settling&rdquo; period has taken place, to flush out problems.  The
+public release of the first draft of this document was the first step in
+this process. 
+</ul>
+
+   <p>Consequently, most of the first trials of the TDS will be made by
+members of the TDS committee and/or developers of TeX-related
+software.  This has already taken place during the course of our
+deliberations (see Appendix&nbsp;<!-- /@w --><a href="#Related-references">Related references</a> for a sample
+tree available electronically).  They will certainly result in the
+production of a substantial number of TDS-compliant packages. 
+Indeed, the teTeX and TeX Live
+distributions are TDS-compliant and in use now at many sites.
+
+   <p>Once installable forms of key TDS-compliant packages are more
+widespread, some TeX administrators will set up TDS-compliant
+trees, possibly in parallel to existing production directories.  This
+testing will likely flush out problems that were not obvious in the
+confined settings of the developers' sites; for example, it should help
+to resolve system and package dependencies, package interdependencies, and
+other details not addressed by this TDS version.
+
+   <p>After most of the dust has settled, hopefully even conservative TeX
+administrators will begin to adopt the TDS.  Eventually, most
+TeX sites will have adopted the common structure, and most packages
+will be readily available in TDS-compliant form.
+
+   <p>We believe that this process will occur relatively quickly.  The
+TDS committee spans a wide range of interests in the TeX
+community.  Consequently, we believe that most of the key issues
+involved in defining a workable TDS definition have been covered,
+often in detail.  TeX developers have been consulted about
+implementation issues, and have been trying out the TDS
+arrangement.  Thus, we hope for few surprises as implementations mature.
+
+   <p>Finally, there are several (current or prospective) publishers of TeX
+CD-ROMs.  These publishers are highly motivated to work out
+details of TDS implementation, and their products will provide
+inexpensive and convenient ways for experimentally-minded TeX
+administrators to experiment with the TDS.
+
+<div class="node">
+<p><hr>
+<a name="More-on-subdirectory-searching"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Adoption-of-the-TDS">Adoption of the TDS</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Implementation-issues">Implementation issues</a>
+<br>
+</div>
+
+<h3 class="section">B.2 More on subdirectory searching</h3>
+
+<p>Recursive subdirectory searching is the ability to specify a search not
+only of a specified directory <samp><var>d</var></samp>, but recursively of all
+directories below <samp><var>d</var></samp>.
+
+   <p>Since the TDS specifies precise locations for most files, with no
+extra levels of subdirectories allowed, true recursive searching is not
+actually required for a TDS-compliant implementation. We do,
+however, strongly recommend recursive searching as the most
+user-friendly and natural approach to the problem, rather than
+convoluted methods to specify paths without recursion.
+
+   <p>This feature is already supported by many implementations of TeX and
+companion utilities, for example DECUS TeX for VMS,
+Dvips(k), emTeX (and its drivers),
+PubliC TeX, Web2C, Xdvi(k),
+and Y&amp;YTeX.  The Kpathsea library is a reusable
+implementation of subdirectory searching for TeX, used in a number of
+the above programs.
+
+   <p>Even if your TeX implementation does not directly support
+subdirectory searching, you may find it useful to adopt the structure if
+you do not use many fonts or packages. For instance, if you only use
+Computer Modern and AMS fonts, it would be feasible to store them
+in the TDS layout and list the directories individually in
+configuration files or environment variables.
+
+   <p>The TWG recognizes that subdirectory searching places an extra
+burden on the system and may be the source of performance bottlenecks,
+particularly on slower machines.  Nevertheless, we feel that
+subdirectory searching is imperative for a well-organized TDS,
+for the reasons stated in Section&nbsp;<!-- /@w --><a href="#Subdirectory-searching">Subdirectory searching</a>. 
+Implementors are encouraged to provide enhancements to the basic
+principle of subdirectory searching to avoid performance problems, e.g.,
+the use of a filename cache (this can be as simple as a recursive
+directory listing) that is consulted before disk searching begins.  If a
+match is found in the database, subdirectory searching is not required,
+and performance is thus independent of the number of subdirectories
+present on the system.
+
+   <p>Different implementations specify subdirectory searching differently. 
+In the interest of typographic clarity, the examples here do not use the
+<samp><var>replaceable</var></samp> font.
+
+     <ul>
+<li>Dvips:
+via a separate
+<samp><span class="file">TEXFONTS_SUBDIR</span></samp> environment variable.
+
+     <li>emTeX:
+<samp><span class="file">t:\subdir!!</span></samp>; <samp><span class="file">t:\subdir!</span></samp> for
+a single level of searching.
+
+     <li>Kpathsea:
+<samp><span class="file">texmf/subdir//</span></samp>
+
+     <li>VMS:
+<samp><span class="file">texmf:[subdir...]</span></samp>
+
+     <li>Xdvi (patchlevel 20):
+<samp><span class="file">texmf/subdir/**</span></samp>;
+<samp><span class="file">texmf/subdir/*</span></samp> for a single level of searching.  Version 20.50
+and above support the <samp><span class="file">//</span></samp> notation.
+
+     <li>Y&amp;Y TeX:
+<samp><span class="file">t:/subdir//</span></samp> or
+<samp><span class="file">t:\subdir\\</span></samp>.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Example-implementation_002dspecific-trees"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#More-on-subdirectory-searching">More on subdirectory searching</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Implementation-issues">Implementation issues</a>
+<br>
+</div>
+
+<h3 class="section">B.3 Example implementation-specific trees</h3>
+
+<p>The TDS cannot specify a precise location for
+implementation-specific files, such as <samp><span class="file">texmf/ini</span></samp>, because a site
+may have multiple TeX implementations.
+
+   <p>Nevertheless, for informative purposes, we provide here the default
+locations for some implementations. Please contact us with additions or
+corrections. These paths are not definitive, may not match anything at
+your site, and may change without warning.
+
+   <p>We recommend all implementations have default search paths that start
+with the current directory (e.g., <samp><span class="file">.</span></samp>).  Allowing users to
+include the parent directory (e.g., <samp><span class="file">..</span></samp>) is also helpful.
+
+<ul class="menu">
+<li><a accesskey="1" href="#AmiWeb2c-2_002e0">AmiWeb2c 2.0</a>
+<li><a accesskey="2" href="#Public-DECUS-TeX">Public DECUS TeX</a>
+<li><a accesskey="3" href="#Web2c-7">Web2c 7</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="AmiWeb2c-2_002e0"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Public-DECUS-TeX">Public DECUS TeX</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>
+<br>
+</div>
+
+<h4 class="subsection">B.3.1 AmiWeb2c 2.0</h4>
+
+<p>(Email <a href="mailto:scherer@physik.rwth-aachen.de">scherer@physik.rwth-aachen.de</a> to contact the maintainer
+of this implementation.)
+
+   <p>AmiWeb2c 2 is compatible with Web2c 7 to the greatest possible
+extent, so only the very few differences are described in this
+section.  Detailed information about the basic concepts is given in
+the section for Web2c 7 below.
+
+   <p>Thanks to the <samp><span class="file">SELFAUTO</span></samp> mechanism of Kpathsea 3.0 no specific
+location for the installation of AmiWeb2c is required as long as the
+general structure of the distribution is preserved.
+
+   <p>In addition to Kpathsea's <samp><span class="file">//</span></samp> notation recursive path search may
+also be started by <samp><var>DEVICE</var><span class="file">:/</span></samp>, e.g., <samp><span class="file">TeXMF:/</span></samp>
+will scan this specific device completely.
+
+   <p>Binaries coming with the AmiWeb2c distribution are installed in the
+directory <samp><span class="file">bin/amiweb2c/</span></samp> outside the common TDS tree
+<samp><span class="file">share/texmf/</span></samp>.  In addition to the set of AmiWeb2c binaries
+you will find two subdirectories <samp><span class="file">local/</span></samp> and <samp><span class="file">pastex/</span></samp>
+with auxiliary programs.
+
+   <p>A stripped version of the PasTeX system (used by kind permission of
+Georg He&szlig;mann) is coming with AmiWeb2c, pre-installed in its own
+<samp><span class="file">share/texmf/amiweb2c/pastex/</span></samp> directory.  If you want to use
+PasTeX you have to <samp><span class="file">assign</span></samp> the name <samp><span class="file">TeX:</span></samp> to this place.
+
+   <p>Documentation files in AmigaGuide format should be stored at
+<samp><span class="file">doc/guide/</span></samp> similar to <samp><span class="file">doc/info/</span></samp>.
+
+<div class="node">
+<p><hr>
+<a name="Public-DECUS-TeX"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Web2c-7">Web2c 7</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#AmiWeb2c-2_002e0">AmiWeb2c 2.0</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>
+<br>
+</div>
+
+<h4 class="subsection">B.3.2 Public DECUS TeX</h4>
+
+<p>If another VMS implementation besides Public DECUS TeX
+appears, the top level implementation directory name will be modified to
+something more specific (e.g., <samp><span class="file">vms_decus</span></samp>).
+
+<pre class="example">       texmf/
+         vms/            VMS implementation specific files
+           exe/          end-user commands
+             common/     command procedures, command definition files, etc.
+             axp/        binary executables for Alpha AXP
+             vax/        binary executables for VAX
+           formats/      pool files, formats, bases
+           help/         VMS help library, and miscellaneous help sources
+           mgr/          command procedures, programs, docs, etc., for system management
+</pre>
+   <div class="node">
+<p><hr>
+<a name="Web2c-7"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Public-DECUS-TeX">Public DECUS TeX</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Example-implementation_002dspecific-trees">Example implementation-specific trees</a>
+<br>
+</div>
+
+<h4 class="subsection">B.3.3 Web2c 7</h4>
+
+<p>All implementation-dependent TeX system files (<samp><span class="file">.pool</span></samp>,
+<samp><span class="file">.fmt</span></samp>, <samp><span class="file">.base</span></samp>, <samp><span class="file">.mem</span></samp>) are stored by default directly
+in <samp><span class="file">texmf/web2c</span></samp>.  The configuration file <samp><span class="file">texmf.cnf</span></samp> and
+various subsidiary <samp><span class="file">MakeTeX...</span></samp> scripts used as subroutines are
+also stored there.
+
+   <p>Non-TeX specific files are stored following the GNU coding
+standards.  Given a root directory <samp><var>prefix</var></samp>
+(<samp><span class="file">/usr/local</span></samp> by default), we have default locations as follows:
+
+<pre class="example">       &lt;prefix&gt;/         installation root (<samp><span class="file">/usr/local</span></samp> by default)
+         bin/            executables
+         man/            man pages
+         info/           info files
+         lib/            libraries (<samp><span class="file">libkpathsea.*</span></samp>)
+         share/          architecture-independent files
+           texmf/        TDS root
+             web2c/      implementation-dependent files (<samp><span class="file">.pool</span></samp>, <samp><span class="file">.fmt</span></samp>, <samp><span class="file">texmf.cnf</span></samp>, etc.)
+</pre>
+   <p>See <a href="http://www.gnu.org/prep/standards_toc.html">http://www.gnu.org/prep/standards_toc.html</a> for the
+rationale behind and descriptions of this arrangement. A site may of
+course override these defaults; for example, it may put everything under
+a single directory such as <samp><span class="file">/usr/local/texmf</span></samp>.
+
+<div class="node">
+<p><hr>
+<a name="Is-there-a-better-way_003f"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Related-references">Related references</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Implementation-issues">Implementation issues</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="appendix">Appendix C Is there a better way?</h2>
+
+<p>Defining the TDS required many compromises.  Both the overall
+structure and the details of the individual directories were arrived at
+by finding common ground among many opinions.  The driving forces were
+feasibility (in terms of what could technically be done and what could
+reasonably be expected from developers) and regularity (files grouped
+together in an arrangement that &ldquo;made sense&rdquo;).
+
+   <p>Some interesting ideas could not be applied due to implementations
+lacking the necessary support:
+
+     <ul>
+<li>Path searching control at the TeX level. If documents could
+restrict subdirectory searching to a subdirectory via some portable
+syntax in file names, restrictions on uniqueness of filenames could be
+relaxed considerably (with the cooperation of the formats), and the
+TeX search path would not need to depend on the format.
+
+     <li>Multiple logical <samp><span class="file">texmf</span></samp> trees. For example, a site might have
+one (read-only) location for stable files, and a different (writable)
+location for dynamically-created fonts or other files. It would be
+reasonable for two such trees to be logically merged when searching. 
+See Michael Downes' article in the references for how this can work in
+practice with Web2C.
+
+   </ul>
+
+<ul class="menu">
+<li><a accesskey="1" href="#Macro-structure">Macro structure</a>
+<li><a accesskey="2" href="#Font-structure">Font structure</a>
+<li><a accesskey="3" href="#Documentation-structure">Documentation structure</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Macro-structure"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Font-structure">Font structure</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Is-there-a-better-way_003f">Is there a better way?</a>
+<br>
+</div>
+
+<h3 class="section">C.1 Macro structure</h3>
+
+<p>The TWG settled on the
+<samp><var>format</var><span class="file">/</span><var>package</var></samp> arrangement after long
+discussion about how best to arrange the files.
+
+   <p>The primary alternative to this arrangement was a scheme which reversed
+the order of these directories:
+<samp><var>package</var><span class="file">/</span><var>format</var></samp>.  This reversed
+arrangement has a strong appeal: it keeps all of the files related to a
+particular package in a single place.  The arrangement actually adopted
+tends to spread files out into two or three places (macros,
+documentation, and fonts, for example, are spread into different
+sections of the tree right at the top level).
+
+   <p>Nevertheless, the <samp><var>format</var><span class="file">/</span><var>package</var></samp>
+structure won for a couple of reasons:
+
+     <ul>
+<li>It is closer to current practice; in fact, several members of the
+TWG have already implemented the TDS hierarchy.  The
+alternative is not in use at any known site, and the TWG felt it
+wrong to mandate something with which there is no practical experience.
+
+     <li>The alternative arrangement increases the number of top-level
+directories, so the files that must be found using subdirectory
+searching are spread out in a wide, shallow tree.  This could have a
+profound impact on the efficiency of subdirectory searching.
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Font-structure"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Documentation-structure">Documentation structure</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Macro-structure">Macro structure</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Is-there-a-better-way_003f">Is there a better way?</a>
+<br>
+</div>
+
+<h3 class="section">C.2 Font structure</h3>
+
+<p>The TWG struggled more with the font directory structure than
+anything else. This is not surprising; the need to use the proliferation
+of PostScript fonts with TeX is what made the previous arrangement
+with all files in a single directory untenable, and therefore what
+initiated the TDS effort.
+
+<ul class="menu">
+<li><a accesskey="1" href="#Font-file-type-location">Font file type location</a>
+<li><a accesskey="2" href="#Mode-and-resolution-location">Mode and resolution location</a>
+<li><a accesskey="3" href="#Modeless-bitmaps">Modeless bitmaps</a>
+</ul>
+
+<div class="node">
+<p><hr>
+<a name="Font-file-type-location"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Mode-and-resolution-location">Mode and resolution location</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Font-structure">Font structure</a>
+<br>
+</div>
+
+<h4 class="subsection">C.2.1 Font file type location</h4>
+
+<p>We considered the supplier-first arrangement in use at many sites:
+
+<pre class="example">     texmf/fonts/<var>supplier</var>/<var>typeface</var>/<var>type</var>/
+</pre>
+   <p>This improves the maintainability of the font tree, since all files
+comprising a given typeface are in one place, but unless all the
+programs that search this tree employ some form of caching, there are
+serious performance concerns.  For example, in order to find a
+<samp><span class="file">TFM</span></samp> file, the simplest implementation would require TeX to
+search through all the directories that contain PK files in all
+modes and at all resolutions.
+
+   <p>In the end, a poll of developers revealed considerable resistance to
+implementing sufficient caching mechanisms, so this arrangement was
+abandoned.  The TDS arrangement allows the search tree to be
+restricted to the correct type of file, at least.  Concerns about
+efficiency remain, but there seems to be no more we can do without
+abandoning subdirectory searching entirely.
+
+   <p>We also considered segregating all font-related files strictly by file
+type, so that Metafont sources would be in a directory
+<samp><span class="file">texmf/fonts/mf</span></samp>, property list files in <samp><span class="file">texmf/fonts/pl</span></samp>, the
+various forms of Type&nbsp;<!-- /@w -->1 fonts separated, and so on. Although more
+blindly consistent, we felt that the drawback of more complicated path
+constructions outweighed this. The TDS merges file types
+(<samp><span class="file">mf</span></samp> and <samp><span class="file">pl</span></samp> under <samp><span class="file">source</span></samp>, <samp><span class="file">pfa</span></samp> and <samp><span class="file">pfb</span></samp>
+and <samp><span class="file">gsf</span></samp> under <samp><span class="file">type1</span></samp>) where we felt this was beneficial.
+
+<div class="node">
+<p><hr>
+<a name="Mode-and-resolution-location"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Modeless-bitmaps">Modeless bitmaps</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Font-file-type-location">Font file type location</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Font-structure">Font structure</a>
+<br>
+</div>
+
+<h4 class="subsection">C.2.2 Mode and resolution location</h4>
+
+<p>We considered having the <samp><span class="file">mode</span></samp> at the bottom of the font tree:
+<pre class="example">     texmf/fonts/pk/<var>supplier</var>/<var>typeface</var>/<var>mode</var>/<var>dpi</var>/
+</pre>
+   <p>In this case, however, it is difficult to limit subdirectory searching
+to the mode required for a particular device.
+
+   <p>We then considered moving the <samp><span class="file">dpi</span><var>nnn</var></samp> up to below
+the mode:
+<pre class="example">     texmf/fonts/pk/<var>mode</var>/<var>dpi</var>/<var>supplier</var>/<var>typeface</var>/
+</pre>
+   <p>But then it is not feasible to omit the <samp><span class="file">dpi</span><var>nnn</var></samp>
+level altogether on systems which can and do choose to use long
+filenames.
+
+<div class="node">
+<p><hr>
+<a name="Modeless-bitmaps"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Mode-and-resolution-location">Mode and resolution location</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Font-structure">Font structure</a>
+<br>
+</div>
+
+<h4 class="subsection">C.2.3 Modeless bitmaps</h4>
+
+<p>The TDS specifies using a single directory <samp><span class="file">modeless/</span></samp> as
+the mode name for those utilities which generate bitmaps, e.g.,
+<samp><span class="file">texmf/fonts/modeless/times/</span></samp>.  This has the considerable advantage
+of not requiring each such directory name to be listed in a search path.
+
+   <p>An alternative was to use the utility name below which all such
+directories could be gathered.  That has the advantage of separating,
+say, <samp><span class="file">gsftopk</span></samp>-generated bitmaps from <samp><span class="file">ps2pk</span></samp>-generated ones. 
+However, we decided this was not necessary; most sites will use only one
+program for the purpose.  Also, PK and GF fonts generally
+identify their creator in the font comment following the <samp><span class="file">PK_ID</span></samp>
+byte.
+
+   <p>We are making an implicit assumption that Metafont is the only program
+producing mode-dependent bitmaps. If this becomes false we could add an
+abbreviation for the program to mode names, as in <samp><span class="file">mfcx</span></samp> vs. 
+<samp><span class="file">xyzcx</span></samp> for a hypothetical program Xyz, or we could
+at that time add an additional program name level uniformly to the tree. 
+It seemed more important to concisely represent the current situation
+than to worry about hypothetical possibilities that may never&nbsp;<!-- /@w -->happen.
+
+<div class="node">
+<p><hr>
+<a name="Documentation-structure"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Font-structure">Font structure</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Is-there-a-better-way_003f">Is there a better way?</a>
+<br>
+</div>
+
+<h3 class="section">C.3 Documentation structure</h3>
+
+<p>We considered placing additional documentation files in the same
+directory as the source files for the packages, but we felt that users
+should be able to find documentation separately from sources, since most
+users have no interest in sources.
+
+   <p>We hope that a separate, but parallel, structure for documentation would
+(1)&nbsp;<!-- /@w -->keep the documentation together and (2)&nbsp;<!-- /@w -->make it as straightforward
+as possible for users to find the particular documentation they were
+after.
+
+<div class="node">
+<p><hr>
+<a name="Related-references"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Contributors">Contributors</a>,
+Previous:&nbsp;<a rel="previous" accesskey="p" href="#Is-there-a-better-way_003f">Is there a better way?</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="appendix">Appendix D Related references</h2>
+
+<p>This appendix gives pointers to related files and other documents.  For
+CTAN references, we use <samp><span class="file">http://www.ctan.org</span></samp> as the
+top-level domain only to make the links be live in this document.  See
+<a href="http://www.ctan.org/tex-archive/CTAN.sites">http://www.ctan.org/tex-archive/CTAN.sites</a> for a complete list of
+CTAN sites; there are mirrors worldwide.
+
+     <ul>
+<li>This document, in many formats (tex, dvi, info, pdf):<br>
+<a href="http://tug.org/tds/">http://tug.org/tds/</a>
+
+     <li>The TDS mailing list archives:<br>
+<a href="http://tug.org/mail-archives/twg-tds/">http://tug.org/mail-archives/twg-tds/</a>
+
+     <li>The level&nbsp;<!-- /@w -->0 DVI driver standard:<br>
+<a href="http://www.ctan.org/tex-archive/dviware/driv-standard/level-0/">http://www.ctan.org/tex-archive/dviware/driv-standard/level-0/</a>
+
+     <li><cite>Filenames for TeX fonts</cite>, with lists of recommended
+supplier and typeface names:<br>
+<a href="http://tug.org/fontname/">http://tug.org/fontname/</a>
+
+     <li>ISO-9660 CD-ROM file system standard:<br>
+<a href="http://www.iso.ch/cate/cat.html">http://www.iso.ch/cate/cat.html</a>
+
+     <li><cite>Components of TeX</cite>, a paper by Joachim
+Schrod:<br>
+<a href="http://www.ctan.org/tex-archive/documentation/components-of-TeX/">http://www.ctan.org/tex-archive/documentation/components-of-TeX/</a>
+
+     <li><cite>Managing Multiple TDS trees</cite>, an article by Michael
+Downes:<br>
+<a href="http://tug.org/TUGboat/Articles/tb22-3/tb72downes.pdf">http://tug.org/TUGboat/Articles/tb22-3/tb72downes.pdf</a>
+
+     <li>A complete set of Metafont modes:<br>
+<a href="http://www.ctan.org/tex-archive/fonts/modes/modes.mf">http://www.ctan.org/tex-archive/fonts/modes/modes.mf</a>
+
+     <li>A large collection of BibTeX databases and styles:<br>
+<a href="ftp://ftp.math.utah.edu/pub/tex/bib/">ftp://ftp.math.utah.edu/pub/tex/bib/</a>
+
+   </ul>
+
+<div class="node">
+<p><hr>
+<a name="Contributors"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Related-references">Related references</a>,
+Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
+<br>
+</div>
+
+<h2 class="appendix">Appendix E Contributors</h2>
+
+<p>The TWG has had no physical meetings; electronic mail was the
+communication medium.
+
+   <p>Sebastian Rahtz is the TeX Users Group Technical Council liaison. 
+Norman Walsh was the original committee chair.  Karl Berry is the
+current editor.
+
+   <p>The list of contributors has grown too large to fairly include, as some
+would surely be inadvertently omitted.  Please consider the archives of
+the <a href="mailto:tds@tug.org">tds@tug.org</a> and <a href="mailto:tex-live@tug.org">tex-live@tug.org</a> mailing lists as
+the record of contributions.
+
+</body></html>
+
diff --git a/Master/texmf-dist/doc/generic/tds/tds.pdf b/Master/texmf-dist/doc/generic/tds/tds.pdf
new file mode 100644
index 00000000000..ec4acaf145a
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds.pdf
diff --git a/Master/texmf-dist/doc/generic/tds/tds.sed b/Master/texmf-dist/doc/generic/tds/tds.sed
new file mode 100644
index 00000000000..fb7f30f13cd
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds.sed
@@ -0,0 +1,14 @@
+# $Id: tds.sed,v 1.2 2004/06/04 17:11:34 karl Exp $
+# Written by Ulrik Vieth and Karl Berry.
+# Public domain.
+# 
+# Things that are too hard to do in Elisp.  Run after tds2texi-convert.
+
+# Indentation blocks in tdsSummary environments.
+s/ \./  /g
+
+# References that are too hard to convert automatically.
+s/Table, ref{tab:summary}/@pxref{Summary},/
+
+/^Copyright.*Group/a\
+This is version @value{version}.
diff --git a/Master/texmf-dist/doc/generic/tds/tds.tex b/Master/texmf-dist/doc/generic/tds/tds.tex
new file mode 100644
index 00000000000..55c1b4ddcc3
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds.tex
@@ -0,0 +1,1585 @@
+%&latex
+% $Id: tds.tex,v 1.43 2004/06/23 17:24:42 karl Exp $
+\NeedsTeXFormat{LaTeX2e} % compatibility with 2.09 is too painful
+\documentclass{tdsguide}
+
+\tdsVersion{1.1}
+
+\title{A Directory Structure for \TeX{} Files}
+\author{TUG Working Group on a \TeX{} Directory Structure (TWG-TDS)}
+
+\begin{document}
+
+\maketitle
+
+\begin{legalnotice}
+
+Copyright {\copyright} 1994, 1995, 1996, 1997, 1998, 1999, 2003, 2004
+\TeX{} Users Group.
+
+Permission to use, copy, and distribute this document \emphasis{without
+modification} for any purpose and without fee is hereby granted,
+provided that this notice appears in all copies.  It is provided ``as
+is'' without expressed or implied warranty.
+
+Permission is granted to copy and distribute modified versions of this
+document under the conditions for verbatim copying, provided that the
+modifications are clearly marked and the document is not represented as
+the official one.
+
+This document is available on any \abbr{ctan} host
+(see Appendix~\ref{sec:Related references}).
+Please send questions or suggestions by email to
+\email|tds@tug.org|.  We welcome all comments.   This is version
+\the\tdsVersion.
+
+\end{legalnotice}
+
+
+\tableofcontents
+
+
+\newpage
+\section{Introduction}
+
+\TeX{} is a powerful, flexible typesetting system used by many people
+around the world.  It is extremely portable and runs on virtually all
+operating systems.  One unfortunate side effect of \TeX{}'s flexibility,
+however, is that there has been no single ``right'' way to install it.
+This has resulted in many sites having different installed arrangements.
+
+The primary purpose of this document is to describe a standard \TeX{}
+Directory Structure (\abbr{TDS}): a directory hierarchy for macros,
+fonts, and the other implementation-independent \TeX{} system files.  As
+a matter of practicality, this document also suggests ways to
+incorporate the rest of the \TeX{} files into a single structure.  The
+\abbr{TDS} has been designed to work on all modern systems.  In
+particular, the Technical Working Group (\abbr{TWG}) believes it is usable
+under Mac\abbr{OS}, \abbr{ms-dos}, \abbr{os/2}, Unix, \abbr{vms}, and
+Windows \abbr{nt}\@.  We hope that administrators and developers of both
+free and commercial \TeX{} implementations will adopt this standard.
+
+This document is intended both for the \TeX{} system administrator at a
+site and for people preparing \TeX{} distributions---everything from a
+complete runnable system to a single macro or style file. It may also
+help \TeX{} users find their way around systems organized this way.  It
+is not a tutorial: we necessarily assume knowledge of the many parts of
+a working \TeX{} system. If you are unfamiliar with any of the programs
+or file formats we refer to, consult the references in
+Appendix~\ref{sec:Related references}.
+
+
+\subsection{History}
+
+Version 1.0 of the \abbr{TDS} was released in February 2003.
+
+Version 1.1 was released in June 2004, with the following non-editorial
+changes:
+
+\begin{itemize-squeeze}
+\item Inputs for \TeX{} extensions included under \path|tex|, instead
+      of in their own top-level directories (Section~\ref{sec:Extensions})
+\item New top-level directory \path|scripts| (Section~\ref{sec:Scripts}).
+\item New subdirectories \path|lig|, \path|opentype|,
+      \path|truetype|, and \path|type3| under \path|fonts|
+      (Section~\ref{sec:Fonts}).
+\item \path|enc|, \path|lig|, and \path|map| all use
+      \replaceable{syntax}\path|/|\replaceable{package} subdirectories
+      (Section~\ref{sec:Fonts}).
+\item \path|pfm| files specified to go under \path|type1|, and
+      \path|inf| files under \path|afm| (Section~\ref{sec:Fonts}).
+\end{itemize-squeeze}
+
+
+\subsection{The role of the \abbr{TDS}}
+
+The role of the \abbr{TDS} is to stabilize the organization of
+\TeX{}-related software packages that are installed and in use, possibly
+on multiple platforms simultaneously.
+
+At first glance, it may seem that the Comprehensive \TeX{} Archive
+Network (\abbr{ctan}) fulfills at least part of this role, but this is
+not the case.  The role of \abbr{ctan} is to simplify archiving and
+distribution, not installation and use.
+
+In fact, the roles of the \abbr{TDS} and \abbr{ctan} are frequently in
+conflict, as we will see.  For distribution, many different types of
+files must be combined into a single unit; for use, it is traditional to
+segregate files (even similar files) from a single package into
+separate, occasionally distant, directories.
+
+
+\subsection{Conventions}
+
+In this document, ``\path|/|'' is used to separate filename components;
+for example, \path|texmf/fonts|.  This is the Unix convention but the
+ideas are in no way Unix-specific.
+
+In this document, ``\TeX{}'' generally means the \TeX{} system, including
+\MF{}, \abbr{DVI} drivers, utilities, etc., not just the \TeX{}
+program itself.
+
+The word ``package'' in this document has its usual meaning: a set of
+related files distributed, installed, and maintained as a unit.  This is
+\emphasis{not} a \LaTeXe{} package, which is a style file supplementing
+a document class.
+
+We use the following typographic conventions:
+
+\begin{description}
+
+\item[\literal{literal}] Literal text such as \literal{filename} is
+typeset in typewriter type.
+
+\item[\replaceable{replaceable}] Replaceable text such as
+\replaceable{package}, identifying a class of things, is typeset in
+italics inside angle brackets.
+
+\end{description}
+
+
+\section{General}
+
+This section describes common properties throughout the \abbr{TDS} tree.
+
+\subsection{Subdirectory searching}
+\label{sec:Subdirectory searching}
+
+Older \TeX{} installations store large numbers of related files in single
+directories, for example, all \path|TFM| files and\slash or all \TeX{}
+input files.
+
+This monolithic arrangement hinders maintenance of a \TeX{} system: it
+is difficult to determine what files are used by what packages, what
+files need to be updated when a new version is installed, or what files
+should be deleted if a package is removed.  It is also a source of error
+if two or more packages happen to have input files with the same name.
+
+Therefore, the \abbr{TWG} felt each package should be in a separate
+directory. But we recognized that explicitly listing all directories to
+be searched would be unbearable.  A site may wish to install dozens of
+packages.  Aside from anything else, listing that many directories would
+produce search paths many thousands of characters long, overflowing the
+available space on some systems.
+
+Also, if all directories are explicitly listed, installing or removing a
+new package would mean changing a path as well as installing or removing
+the actual files.  This would be a time-consuming and error-prone
+operation, even with implementations that provide some way to specify
+the directories to search at runtime.  On systems without runtime
+configuration, it would require recompiling software, an intolerable
+burden.
+
+As a result, the \abbr{TWG} concluded that a comprehensive \abbr{TDS}
+requires implementations to support some form of implicit subdirectory
+searching.  More precisely, implementations must make it possible to
+specify that \TeX{}, \MF{}, and their companion utilities search in both
+a specified directory and recursively through all subdirectories of that
+directory when looking for an input file.  Other forms of subdirectory
+searching, for example recursive-to-one-level searches, may also be
+provided.  We encourage implementors to provide subdirectory searching
+at the option of the installer and user for all paths.
+
+The \abbr{TDS} does not specify a syntax for specifying recursive
+searching, but we encourage implementors to provide interoperability
+(see Section~\ref{sec:More on subdirectory searching}).
+
+
+\subsection{Rooting the tree}
+\label{sec:Rooting the tree}
+
+In this document, we shall designate the root \abbr{TDS} directory by
+`\texmf{}' (for ``\TeX{} and \MF{}''). We recommend using that name
+where possible, but the actual name of the directory is up to the
+installer. On \abbr{pc} networks, for example, this could map to a
+logical drive specification such as \path|T:|.
+
+Similarly, the location of this directory on the system is
+site-dependent.  It may be at the root of the file system; on Unix
+systems, \path|/usr/local/share|, \path|/usr/local|,
+\path|/usr/local/lib|, and \path|/opt| are common choices.
+
+The name \texmf{} was chosen for several reasons: it reflects the fact
+that the directory contains files pertaining to an entire \TeX{} system
+(including \MF{}, \MP{}, \BibTeX{}, etc.), not just \TeX{} itself; and it
+is descriptive of a generic installation rather than a particular
+implementation.
+
+A site may choose to have more than one \abbr{TDS} hierarchy installed
+(for example, when installing an upgrade). This is perfectly legitimate.
+
+
+\subsection{Local additions}
+\label{sec:Local additions}
+
+The \abbr{TDS} cannot specify precisely when a package is or is not a
+``local addition''. Each site must determine this according to its own
+conventions.  At the two extremes, one site might wish to consider
+``nonlocal'' all files not acquired as part of the installed \TeX{}
+distribution; another site might consider ``local'' only those files
+that were actually developed at the local site and not distributed
+elsewhere.
+
+We recognize two common methods for local additions to a distributed
+\texmf{} tree. Both have their place; in fact, some sites employ
+both simultaneously:
+
+\begin{enumerate}
+
+\item A completely separate tree which is a \abbr{TDS} structure
+itself; for example, \path|/usr/local/umbtex| at the University of
+Massachusetts at Boston. This is another example of the multiple
+\texmf{} hierarchies mentioned in the previous section.
+
+\item A directory named `\path|local|' at any appropriate level, for
+example, in the \replaceable{format}, \replaceable{package}, and
+\replaceable{supplier} directories discussed in the following sections.
+The \abbr{TDS} reserves the directory name \path|local| for this
+purpose.
+
+We recommend using \path|local| for site-adapted configuration files,
+such as \path|language.dat| for the Babel package or \path|graphics.cfg|
+for the graphics package.  Unmodified configuration files from a package
+should remain in the package directory. The intent is to separate
+locally modified or created files from distribution files, to ease
+installing new releases.
+
+\end{enumerate}
+
+One common case of local additions is dynamically generated files, e.g.,
+\abbr{PK} fonts by the \path|mktexpk| script (which originated in
+\application{Dvips} as \path|MakeTeXPK|).  A site may store the
+generated files directly in any of:
+\begin{itemize-squeeze}
+\item their standard location in the main \abbr{TDS} tree (if it can be
+made globally writable);
+
+\item an alternative location in the main \abbr{TDS} tree (for
+example, under \path|texmf/fonts/tmp|);
+
+\item a second complete \abbr{TDS} tree (as outlined above);
+
+\item any other convenient directory (perhaps under
+\path|/var|, for example \path|/var/spool/fonts|).
+
+\end{itemize-squeeze}
+
+No one solution will be appropriate for all sites.
+
+
+\subsection{Duplicate filenames}
+\label{sec:Duplicate filenames}
+
+Different files by the same name may exist in a \abbr{TDS} tree. The
+\abbr{TDS} generally leaves unspecified which of two files by the same
+name in a search path will be found, so generally the only way to
+reliably find a given file is for it to have a unique name.  However,
+the \abbr{TDS} requires implementations to support the following
+exceptions:
+
+\begin{itemize}
+
+\item Names of \TeX{} input files must be unique within each first-level
+subdirectory of \path|texmf/tex| and \path|texmf/tex/generic|, but not
+within all of \path|texmf/tex|; i.e., different \TeX{} formats may have
+files by the same name. (Section~\ref{sec:Macros} discusses this
+further.)  Thus, no single format-independent path specification, such
+as a recursive search beginning at \path|texmf/tex| specifying no other
+directories, suffices.  So implementations must provide format-dependent
+path specifications, for example via wrapper scripts or configuration
+files.
+
+\item Many font files will have the same name (e.g., \path|cmr10.pk|),
+as discussed in Section~\ref{sec:Valid font bitmaps}.  Implementations
+must distinguish these files by mode and resolution.
+
+\end{itemize}
+
+All implementations we know of already have these capabilities.
+
+One place where duplicate names are likely to occur is not an exception:
+
+\begin{itemize}
+
+\item Names of \MF{} input files (as opposed to bitmaps) must be unique
+within all of \path|texmf/fonts|. In practice, this is a problem with
+some variants of Computer Modern which contain slightly modified files
+named \path|punct.mf|, \path|romanl.mf|, and so on. We believe the only
+feasible solution is to rename the derivative files to be
+unique.
+
+\end{itemize}
+
+
+\section{Top-level directories}
+\label{sec:Top-level directories}
+
+The directories under the \texmf{} root identify the major components of
+a \TeX{} system (see Section~\ref{sec:Summary} for a summary).  A site
+may omit any unneeded directories.
+
+Although the \abbr{TDS} by its nature can specify precise locations only
+for implementation-independent files, we recognize that installers may
+well wish to place other files under \texmf{} to simplify administration
+of the \TeX{} tree, especially if it is maintained by someone other than
+the system administrator.  Therefore, additional top-level directories
+may be present.
+
+The top-level directories specified by the \abbr{TDS} are:
+
+\begin{description}
+\item[\path|tex|]
+for \TeX{} files (Section~\ref{sec:Macros}).
+
+\item[\path|fonts|]
+for font-related files (Section~\ref{sec:Fonts}).
+
+\item[\path|metafont|]
+for \MF{} files which are not fonts (Section~\ref{sec:Non-font MF files}).
+
+\item[\path|metapost|]
+for \MP{} files (Section~\ref{sec:MetaPost}).
+
+\item[\path|bibtex|]
+for \BibTeX{} files (Section~\ref{sec:BibTeX}).
+
+\item[\path|scripts|]
+for platform-independent executables (Section~\ref{sec:Scripts}).
+
+\item[\path|doc|]
+for user documentation (Section~\ref{sec:Documentation}).
+
+\item[\path|source|] for sources.  This includes both traditional
+program sources (for example, \application{Web2C} sources go in
+\path|texmf/source/web2c|) and, e.g., \LaTeX{} \path|dtx| sources (which
+go in \path|texmf/source/latex|). The \abbr{TDS} leaves unspecified any
+structure under \path|source|.
+
+\path|source| is intended for files which are not needed at runtime by
+any \TeX{} program; it should not be included in any search path. For
+example, \path|plain.tex| does not belong under \path|texmf/source|,
+even though it is a ``source file'' in the sense of not being derived
+from another file. (It goes in \path|texmf/tex/plain/base|, as explained
+in Section~\ref{sec:Macros}).
+
+\item[\replaceable{implementation}] for implementations (examples:
+\path|emtex|, \path|vtex|, \path|web2c|), to be used for whatever
+purpose deemed suitable by the implementor or \TeX{} administrator.
+That is, files that cannot be shared between implementations, such as
+pool files (\path|tex.pool|) and memory dump files (\path|plain.fmt|) go
+here, in addition to implementation-wide configuration files.  See
+Section~\ref{sec:Example implementation-specific trees} for examples of
+real \replaceable{implementation} trees.
+
+Such implementation-specific configuration files should \emphasis{not}
+be located using the main \TeX{} input search path (e.g.,
+\path|TEXINPUTS|).  This must be reserved for files actually read by a
+\TeX{} engine.  See Section~\ref{sec:Extensions}.
+
+\item[\replaceable{program}] for program-specific input and
+configuration files for any \TeX{}-related programs (examples:
+\path|mft|, \path|dvips|).  In fact, the \path|tex|, \path|metafont|,
+\path|metapost|, and \path|bibtex| items above may all be seen as
+instances of this case.
+
+\end{description}
+
+
+\subsection{Macros}
+\label{sec:Macros}
+
+\TeX{} macro files shall be stored in separate directories, segregated
+by \TeX{} format and package name (we use `format' in its traditional
+\TeX{} sense to mean a usefully \path|\dump|-able package):
+\begin{ttdisplay}
+texmf/tex/\replaceable{format}/\replaceable{package}/
+\end{ttdisplay}
+
+\begin{description}
+
+\item[\replaceable{format}] is a format name (examples: \path|amstex|,
+\path|latex|, \path|plain|, \path|texinfo|).
+
+The \abbr{TDS} allows distributions that can be used as either formats or
+packages (e.g., Texinfo, Eplain) to be stored at either level, at the
+option of the format author or \TeX{} administrator. We recommend that
+packages used as formats at a particular site be stored at the
+\replaceable{format} level: by adjusting the \TeX{} inputs search path,
+it will be straightforward to use them as macro packages under another
+format, whereas placing them in another tree completely obscures their
+use as a format.
+
+The \abbr{TDS} reserves the following \replaceable{format} names:
+
+\begin{itemize}
+
+\item \path|generic|, for input files that are useful across a wide
+range of formats (examples: \path|null.tex|, \path|path.sty|).
+Generally, this means any format that uses the category codes of Plain
+\TeX{} and does not rely on any particular format.  This is in contrast
+to those files which are useful only with Plain \TeX{} (which go under
+\path|texmf/tex/plain|), e.g., \path|testfont.tex| and \path|plain.tex|
+itself.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local
+additions}.
+
+\end{itemize}
+
+Thus, for almost every format, it is necessary to search at least the
+\replaceable{format} directory and then the \path|generic| directory (in
+that order).  Other directories may need to be searched as well,
+depending on the format.  When using \AMSTeX{}, for example, the
+\path|amstex|, \path|plain|, and \path|generic| directories should be
+searched, because \AMSTeX{} is compatible with Plain.
+
+\item[\replaceable{package}] is a \TeX{} package name (examples:
+\path|babel|, \path|texdraw|).
+
+In the case where a format consists of only a single file and has no
+auxiliary packages, that file can simply be placed in the
+\replaceable{format} directory, instead of
+\replaceable{format}\path|/base|.  For example, Texinfo may go in
+\path|texmf/tex/texinfo/texinfo.tex|, not
+\path|texmf/tex/texinfo/base/texinfo.tex|.
+
+The \abbr{TDS} reserves the following \replaceable{package} names:
+
+\begin{itemize}
+
+\item \path|base|, for the base distribution of each format,
+including files used by \iniTeX{} when dumping format files.  For
+example, in the standard \LaTeX{} distribution, the \path|ltx| files
+created during the build process.  Another example: the \path|.ini|
+driver files for formats used by \TeX{} Live and other distributions.
+
+\item \path|hyphen|, for hyphenation patterns, including the original
+American English \path|hyphen.tex|.  These are typically used only by
+\iniTeX{}.  In most situations, this directory need exist only under the
+\literal{generic} format.
+
+\item \path|images|, for image input files, such as Encapsulated
+PostScript figures. Although it is somewhat non-intuitive for these to
+be under a directory named ``\path|tex|'', \TeX{} needs to read these
+files to glean bounding box or other information.  A mechanism for
+sharing image inputs between \TeX{} and other typesetting programs
+(e.g., Interleaf, FrameMaker) is beyond the scope of the
+\abbr{TDS}\@. In most situations, this directory need exist only under
+the \literal{generic} format.
+
+\item \path|local|, for local additions and configuration files. See
+Section~\ref{sec:Local additions}.
+
+\item \path|misc|, for packages that consist of a single file.  An
+administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using \path|misc|.
+
+\end{itemize}
+
+\end{description}
+
+
+\subsubsection{Extensions}
+\label{sec:Extensions}
+
+\TeX{} has spawned many companion and successor programs (``engines''),
+such as \abbr{PDF}\TeX{}, Omega, and others.  The \abbr{TDS} specifies
+that the input files for such programs (using a \TeX{}-like syntax) be
+placed within the top-level \path|tex| directory, either at the top
+level or within a format subdirectory, even though the original \TeX{}
+program may not be able to read them.  For example:
+
+\begin{ttdisplay}
+texmf/tex/aleph
+texmf/tex/enctex
+\end{ttdisplay}
+
+This is a change from \abbr{TDS}~1.0, which specified top-level
+\replaceable{extension} directories for each such program.  We felt the
+new approach is preferable, because:
+
+\begin{itemize}
+
+\item Authors of relevant packages typically make their code detect the
+engine being used, and issue error messages or adapt to circumstances
+appropriately.  Furthermore, as a package matures, it may support
+multiple engines.  Thus, a package could conceivably be placed in any of
+several top-level directories, at different times.  Putting all packages
+under the top-level \path|tex| directory provides a stable location over
+time.
+
+\item Users need to be able to switch between engines, and configuring
+different search paths for each engine is difficult and error-prone.
+
+\end{itemize}
+
+Thus, in practice, having different top-level directories caused
+difficulties for everyone involved---users, package authors, site
+administrators, and system distributors.
+
+Please contrast this approach with the \replaceable{implementation}
+top-level subdirectory (Section~\ref{sec:Top-level directories}), which
+is to be used for configuration files that (presumably) do not use
+\TeX{} syntax and in any case should not be found along the main \TeX{}
+input search path.
+
+
+\subsection{Fonts}
+\label{sec:Fonts}
+
+Font files are stored in separate directories, segregated by file type,
+and then (in most cases) font supplier and typeface.  \abbr{PK} and
+\abbr{GF} files need additional structure, as detailed in the next
+section.
+
+\begin{ttdisplay}
+texmf/fonts/\replaceable{type}/\replaceable{supplier}/\replaceable{typeface}/
+texmf/fonts/enc,lig,map/\replaceable{subpath}/
+\end{ttdisplay}
+
+\begin{description}
+
+\item[\replaceable{type}] is the type of font file. The \abbr{TDS}
+reserves the following \replaceable{type} names for common \TeX{} file
+types:
+
+\begin{itemize-squeeze}
+\item \path|afm|, for Adobe font metrics, and \path|inf| files.
+\item \path|gf|, for generic font bitmap files.
+\item \path|opentype|, for OpenType fonts.
+\item \path|pk|, for packed bitmap files.
+\item \path|source|, for font sources (\MF{} files, property lists, etc.).
+\item \path|tfm|, for \TeX{} font metric files.
+\item \path|truetype|, for TrueType fonts.
+\item \path|type1|, for PostScript Type 1 fonts (in \path|pfa|,
+      \path|pfb|, or any other format), and \path|pfm| files. 
+\item \path|type3|, for PostScript Type 3 fonts.
+\item \path|vf|, for virtual fonts.
+\end{itemize-squeeze}
+
+The \abbr{TDS} also reserves the names \path|enc|, \path|lig|, and
+\path|map| for font encoding, ligature, and mapping files, respectively.
+All of these directories are structured the same way, with
+\replaceable{syntax} subdirectories, and then \replaceable{package}
+subsubdirectories.  Each of these file types is intended to be searched
+along its own recursively-searched path.  The names of the actual files
+must be unique within their subtree, as usual.  Examples:
+\begin{ttdisplay}
+fonts/map/dvipdfm/updmap/dvipdfm.map  
+fonts/map/dvips/lm/lm.map
+fonts/enc/dvips/base/8r.enc
+\end{ttdisplay}
+
+The Fontname and Dvips packages have more examples of the \path|enc| and
+\path|map| types.  The \path|afm2pl| program uses \path|lig| files.  
+
+\path|pfm| files are included in the \path|type1| directory, instead of
+being given their own directory, for two reasons: 1)~a \path|.pfm| file
+is always an adjunct to a given \path|.pfb| file; 2)~they must be
+installed from the same directory for Windows programs other than \TeX{}
+to use them.
+
+\path|inf| files are included in the \path|afm| directory, since
+an \path|inf| and \path|afm| file can be used to generate a \path|pfm|.
+(Unfortunately, Adobe Type Manager and perhaps other software requires
+that the \path|pfb| be in the same directory as \path|afm| and
+\path|inf| for installation.)
+
+As usual, a site may omit any of these directories that are unnecessary.
+\path|gf| is a particularly likely candidate for omission.
+
+\item[\replaceable{supplier}] is a name identifying font source
+(examples: \path|adobe|, \path|ams|, \path|public|). The \abbr{TDS}
+reserves the following \replaceable{supplier} names:
+
+\begin{itemize}
+
+\item \path|ams|, for the American Mathematical Society's \AmS{}-fonts
+collection.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local additions}.
+
+\item \path|public|, for freely redistributable fonts where the supplier
+neither (1)~requested their own directory (e.g., \path|ams|), nor
+(2)~also made proprietary fonts (e.g., \path|adobe|).  It does not
+contain all extant freely distributable fonts, nor are all files therein
+necessarily strictly public domain.
+
+\item \path|tmp|, for dynamically-generated fonts, as is traditional on
+some systems. It may be omitted if unnecessary, as usual.
+
+\end{itemize}
+
+
+\item[\replaceable{typeface}] is the name of a typeface family
+(examples: \path|cm|, \path|euler|, \path|times|). The \abbr{TDS}
+reserves the following \replaceable{typeface} names:
+
+\begin{itemize}
+
+\item \path|cm| (within \path|public|), for the 75 fonts defined in
+\citetitle{Computers and Typesetting, Volume~E}.
+
+\item \path|latex| (within \path|public|), for those fonts distributed
+with \LaTeX{} in the base distribution.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local additions}.
+
+\end{itemize}
+
+\end{description}
+
+Some concrete examples:
+\begin{ttdisplay}
+texmf/fonts/source/public/pandora/pnr10.mf
+texmf/fonts/tfm/public/cm/cmr10.tfm
+texmf/fonts/type1/adobe/utopia/putr.pfa
+\end{ttdisplay}
+
+For complete supplier and typeface name lists, consult
+\citetitle{Filenames for \TeX{} fonts} (see Appendix~\ref{sec:Related
+references}).
+
+\subsubsection{Font bitmaps}
+
+Font bitmap files require two characteristics in addition to the above
+to be uniquely identifiable: (1)~the type of device (i.e., mode) for
+which the font was created; (2)~the resolution of the bitmap.
+
+Following common practice, the \abbr{TDS} segregates fonts with
+different device types into separate directories.  See \path|modes.mf|
+in Appendix~\ref{sec:Related references} for recommended mode names.
+
+Some printers operate at more than one resolution (e.g., at 300\,dpi and
+600\,dpi), but each such resolution will necessarily have a different
+mode name. Nothing further is needed, since implicit in the \TeX{}
+system is the assumption of a single target resolution.
+
+Two naming strategies are commonly used to identify the resolution of
+bitmap font files.  On systems that allow long filenames (and in the
+original \MF{} program itself), the resolution is included in the
+filename (e.g., \path|cmr10.300pk|).  On systems which do not support
+long filenames, fonts are generally segregated into directories by
+resolution (e.g., \path|dpi300/cmr10.pk|).
+
+Because the \abbr{TDS} cannot require long filenames, we must use the
+latter scheme for naming fonts. So we have two more subdirectory
+levels under \path|pk| and \path|gf|:
+
+\begin{ttdisplay}
+texmf/fonts/pk/\replaceable{mode}/\replaceable{supplier}/\replaceable{typeface}/dpi\replaceable{nnn}/
+texmf/fonts/gf/\replaceable{mode}/\replaceable{supplier}/\replaceable{typeface}/dpi\replaceable{nnn}/
+\end{ttdisplay}
+
+\begin{description}
+
+\item[\replaceable{mode}] is a name which identifies the device type
+(examples: \path|cx|, \path|ljfour|, \path|modeless|).  Usually, this is
+the name of the \MF{} mode used to build the \abbr{PK} file.  For fonts
+rendered as bitmaps by a program that does not distinguish between
+different output devices, the \replaceable{mode} name shall be simply
+\path|modeless|.  The \replaceable{mode} level shall not be omitted,
+even if only a single mode happens to be in use.
+
+\item[\path|dpi|\replaceable{nnn}] specifies the resolution of the font
+(examples: \path|dpi300|, \path|dpi329|).  `\literal{dpi}' stands for
+dots per inch, i.e., pixels per inch. We recognize that pixels per
+millimeter is used in many parts of the world, but dpi is too
+traditional in the \TeX{} world to consider changing now.
+
+The integer \replaceable{nnn} is to be calculated as if using \MF{}
+arithmetic and then rounded; i.e., it is the integer \MF{} uses in its
+output \path|gf| filename.  We recognize small differences in the
+resolution are a common cause of frustration among users, however, and
+recommend implementors follow the level~0 \abbr{DVI} driver standard
+(see Appendix~\ref{sec:Related references}) in bitmap font searches by
+allowing a fuzz of $\pm0.2$\% (with a minimum of $1$) in the
+\replaceable{dpi}.
+
+\end{description}
+
+Implementations may provide extensions to the basic naming scheme, such
+as long filenames (as in the original \MF{}) and font library files (as
+in em\TeX{}'s \path|.fli| files), provided that the basic scheme is also
+supported.
+
+\subsubsection{Valid font bitmaps}
+\label{sec:Valid font bitmaps}
+
+The \abbr{TWG} recognizes that the use of short filenames has many
+disadvantages.  The most vexing is that it results in the creation of
+dozens of different files with the same name.  At a typical site,
+\path|cmr10.pk| will be the filename for Computer Modern Roman 10\,pt at
+5--10 magnifications for 2--3 modes. (Section~\ref{sec:Duplicate
+filenames} discusses duplicate filenames in general.)
+
+To minimize this problem, we strongly recommend that \abbr{PK} files
+contain enough information to identify precisely how they were created:
+at least the mode, base resolution, and magnification used to create the
+font.
+
+This information is easy to supply: a simple addition to the local modes
+used for building the fonts with \MF{} will automatically provide the
+required information.  If you have been using a local modes file derived
+from (or that is simply) \path|modes.mf| (see Appendix~\ref{sec:Related
+references}), the required information is already in your \abbr{PK}
+files.  If not, a simple addition based on the code found in
+\path|modes.mf| can be made to your local modes file and the \abbr{PK}
+files rebuilt.
+
+
+\subsection{Non-font \MF{} files}
+\label{sec:Non-font MF files}
+
+Most \MF{} input files are font programs or parts of font programs and
+are thus covered by the previous section. However, a few non-font input
+files do exist. Such files shall be stored in:
+
+\begin{ttdisplay}
+texmf/metafont/\replaceable{package}/
+\end{ttdisplay}
+
+\replaceable{package} is the name of a
+\MF{} package (for example, \path|mfpic|).
+
+The \abbr{TDS} reserves the following \replaceable{package} names:
+
+\begin{itemize}
+
+\item \path|base|, for the standard \MF{} macro files as described in
+\citetitle{The \MF{}book}, such as \path|plain.mf| and \path|expr.mf|.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local additions}.
+
+\item \path|misc|, for \MF{} packages consisting of only a single file
+(for example, \path|modes.mf|).  An administrator or package maintainer
+may create directories for single-file packages at their discretion,
+instead of using \path|misc|.
+
+\end{itemize}
+
+
+\subsection{\MP{}}
+\label{sec:MetaPost}
+
+\MP{} is a picture-drawing language developed by John Hobby, derived
+from Knuth's \MF{}. Its primary purpose is to output Encapsulated \PS{}
+instead of bitmaps.
+
+\MP{} input files and the support files for \MP{}-related utilities
+shall be stored in:
+
+\begin{ttdisplay}
+texmf/metapost/\replaceable{package}/
+\end{ttdisplay}
+
+\replaceable{package} is the name of a \MP{} package.  At the present
+writing none exist, but the \abbr{TWG} thought it prudent to leave room
+for contributed packages that might be written in the future.
+
+The \abbr{TDS} reserves the following \replaceable{package} names:
+
+\begin{itemize}
+
+\item \path|base|, for the standard \MP{} macro files, such as
+\path|plain.mp|, \path|mfplain.mp|, \path|boxes.mp|, and
+\path|graph.mp|.  This includes files used by \iniMP{} when dumping mem
+files containing preloaded macro definitions.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local
+additions}.
+
+\item \path|misc|, for \MP{} packages consisting of only a single file.
+An administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using \path|misc|.
+
+\item \path|support|, for additional input files required by \MP{}
+utility programs, including a font map, a character adjustment table,
+and a subdirectory containing low-level \MP{} programs for rendering
+some special characters.
+
+\end{itemize}
+
+
+\subsection{\BibTeX{}}
+\label{sec:BibTeX}
+
+\BibTeX{}-related files shall be stored in:
+
+\begin{ttdisplay}
+texmf/bibtex/bib/\replaceable{package}/
+texmf/bibtex/bst/\replaceable{package}/
+\end{ttdisplay}
+
+The \path|bib| directory is for \BibTeX{} database (\path|.bib|) files,
+the \path|bst| directory for style (\path|.bst|) files.
+
+\replaceable{package} is the name of a \BibTeX{} package.  The
+\abbr{TDS} reserves the following \replaceable{package} names (the same
+names are reserved under both \path|bib| and \path|bst|):
+
+\begin{itemize}
+
+\item \path|base|, for the standard \BibTeX{} databases and styles, such
+as \path|xampl.bib|, \path|plain.bst|.
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local
+additions}.
+
+\item \path|misc|, for \BibTeX{} packages consisting of only a single
+file.  An administrator or package maintainer may create directories for
+single-file packages at their discretion, instead of using \path|misc|.
+
+\end{itemize}
+
+
+\subsection{Scripts}
+\label{sec:Scripts}
+
+The top-level \path|scripts| directory is for platform-independent
+executables, such as Perl, Python, and shell scripts, and Java class
+files.  Subdirectories under \path|scripts| are package names.  This
+eases creating distributions, by providing a common place for such
+platform-independent programs.
+
+The intent is not for all such directories to be added to a user's
+command search path, which would be quite impractical.  Rather, these
+executables are primarily for the benefit of wrapper scripts in whatever
+executable directory a distribution may provide (which is not specified
+by the \abbr{TDS}).  
+
+Truly auxiliary scripts which are invoked directly by other programs,
+rather than wrapper scripts, may also be placed here.  That is,
+\path|scripts| also serves as a platform-independent analog of the
+standard Unix \path|libexec| directory.
+
+We recommend using extensions specifying the language (such as
+\path|.pl|, \path|.py|, \path|.sh|) on these files, to help uniquely
+identify the name.  Since the intent of the \abbr{TDS} is for programs
+in \path|scripts| not to be invoked directly by users, this poses no
+inconvenience.
+
+For example, in the \TeX{} Live distribution, the Con\TeX{}t user-level
+program \path|texexec| can exist as a small wrapper script in each
+\path|bin/|\replaceable{platform}\path|/texexec| (which is outside the
+\path|texmf| tree), which merely finds and calls
+\path|texmf/scripts/context/perl/texexec.pl|.
+
+Examples:
+\begin{ttdisplay}
+scripts/context/perl/texexec.pl
+scripts/context/ruby/examplex.rb
+scripts/thumbpdf/thumbpdf.pl
+\end{ttdisplay}
+
+The \abbr{TDS} does not specify a location for platform-dependent
+binary executables, whether auxiliary or user-level.
+
+
+\subsection{Documentation}
+\label{sec:Documentation}
+
+Most packages come with some form of documentation: user manuals,
+example files, programming guides, etc.  In addition, many independent
+files not part of any macro or other package have been created to
+describe various aspects of the \TeX{} system.
+
+The \abbr{TDS} specifies that these additional documentation files shall
+be stored in a structure that parallels to some extent the
+\path|fonts| and \path|tex| directories, as follows:
+
+\begin{ttdisplay}
+texmf/doc/\replaceable{category}/...
+\end{ttdisplay}
+
+\replaceable{category} identifies the general topic of documentation
+that resides below it; for example, a \TeX{} format name (\path|latex|),
+program name (\path|bibtex|, \path|tex|), language (\path|french|,
+\path|german|), a file format (\path|info|, \path|man|), or other system
+components (\path|web|, \path|fonts|).
+
+One possible arrangement is to organize \path|doc| by language, with all
+the other category types below that.  This helps users find
+documentation in the language(s) in which they are fluent.  Neither this
+nor any other particular arrangement is required, however.
+
+Within each \replaceable{category} tree for a \TeX{} format, the
+directory \path|base| is reserved for base documentation distributed by
+the format's maintainers.
+
+The \abbr{TDS} reserves the following category names:
+
+\begin{itemize}
+
+\item \path|general|, for standalone documents not specific to any
+particular program (for example, Joachim Schrod's \citetitle{Components
+of \TeX{}}).
+
+\item \path|help|, for meta-information, such as \abbr{faq}'s, 
+the \TeX{} Catalogue, etc.
+
+\item \path|info|, for processed Texinfo documents.  (Info files, like
+anything else, may also be stored outside the \abbr{TDS}, at the
+installer's option.)
+
+\item \path|local|, for local additions. See Section~\ref{sec:Local
+additions}.
+
+\end{itemize}
+
+The \path|doc| directory is intended for implementation-independent and
+operating system-independent documentation
+files. Implementation-dependent files are best stored elsewhere, as
+provided for by the implementation and/or \TeX{} administrator (for
+example, \abbr{VMS} help files under \path|texmf/vms/help|).
+
+The documentation directories may contain \TeX{} sources, \abbr{DVI}
+files, \PS{} files, text files, example input files, or any other useful
+documentation format(s).
+
+See Section~\ref{sec:Documentation tree summary} for a summary.
+
+
+\newpage
+\section{Summary}
+\label{sec:Summary}
+
+A skeleton of a \abbr{TDS} \texmf{} directory tree.  This is not to
+imply these are the only entries allowed.  For example, \path|local| may
+occur at any level.
+
+\begin{tdsSummary}
+  bibtex/           \BibTeX{} input files
+  . bib/            \BibTeX{} databases
+  . . base/         base distribution (e.g., \path|xampl.bib|)
+  . . misc/         single-file databases
+  . <package>/      name of a package
+  . bst/            \BibTeX{} style files
+  . . base/         base distribution (e.g., \path|plain.bst|, \path|acm.bst|)
+  . . misc/         single-file styles
+  . <package>/      name of a package
+  doc/              see Section~\ref{sec:Documentation} and the summary below
+  fonts/            font-related files
+  . <type>/         file type (e.g., \path|pk|)
+  . . <mode>/       type of output device (for \path|pk| and \path|gf| only)
+  . . . <supplier>/     name of a font supplier (e.g., \path|public|)
+  . . . . <typeface>/   name of a typeface (e.g., \path|cm|)
+  . . . . . dpi<nnn>/   font resolution (for \path|pk| and \path|gf| only)
+  <implementation>/ \TeX{} implementations, by name (e.g., \path|emtex|)
+  local/            files created or modified at the local site
+  metafont/         \MF{} (non-font) input files
+  . base/           base distribution (e.g., \path|plain.mf|)
+  . misc/           single-file packages (e.g., \path|modes.mf|)
+  . <package>/      name of a package (e.g., \path|mfpic|)
+  metapost/         \MP{} input and support files
+  . base/           base distribution (e.g., \path|plain.mp|)
+  . misc/           single-file packages
+  . <package>/      name of a package
+  . support/        support files for \MP{}-related utilities
+  mft/              \path|MFT| inputs (e.g., \path|plain.mft|)
+  <program>/        \TeX{}-related programs, by name (e.g., \path|dvips|)
+  source/           program source code by name (e.g., \path|latex|, \path|web2c|)
+  tex/              \TeX{} input files
+  . <engine>/       name of an engine (e.g., \path|aleph|); can also be lower
+  . <format>/       name of a format (e.g., \path|plain|)
+  . . base/         base distribution for format (e.g., \path|plain.tex|)
+  . . misc/         single-file packages (e.g., \path|webmac.tex|)
+  . . local/        local additions to or local configuration files for \replaceable{format}
+  . . <package>/    name of a package (e.g., \path|graphics|, \path|mfnfss|)
+  . generic/        format-independent packages
+  . . hyphen/       hyphenation patterns (e.g., \path|hyphen.tex|)
+  . . images/       image input files (e.g., Encapsulated PostScript)
+  . . misc/         single-file format-independent packages (e.g., \path|null.tex|).
+  . . <package>/    name of a package (e.g., \path|babel|)
+\end{tdsSummary}
+
+
+\newpage
+\subsection{Documentation tree summary}
+\label{sec:Documentation tree summary}
+
+An example skeleton of a \abbr{TDS} directory tree under
+\path|texmf/doc|.  This is not to imply these are the only entries
+allowed, or that this structure must be followed precisely for the
+entries listed.
+
+As mentioned, the \path|texmf/doc| tree may be organized by language, so
+that all documentation in French, say, is in a \path|french|
+subdirectory.  In that case, the example structure here would be in a
+given language directory.
+
+\begin{tdsSummary}
+  ams/
+  . amsfonts/       \path|amsfonts.faq|, \path|amfndoc|
+  . amslatex/       \path|amslatex.faq|, \path|amsldoc|
+  . amstex/         \path|amsguide|, \path|joyerr|
+  bibtex/           \BibTeX{}
+  . base/           \path|btxdoc.tex|
+  fonts/
+  . fontname/       \citetitle{Filenames for \TeX{} fonts}
+  . oldgerm/        \path|corkpapr|
+  <format>/         name of a \TeX{} format (e.g., \path|generic|, \path|latex|)
+  . base/           for the base distribution
+  . misc/           for contributed single-file package documentation
+  . <package>/      for \emphasis{package}
+  general/          across programs, generalities
+  . errata/         \path|errata|, \path|errata[1-8]|
+  . texcomp/        \citetitle{Components of \TeX{}}
+  help/             meta-information
+  . ctan/           info about \abbr{ctan} mirror sites
+  . faq/            \abbr{faq}s of \path|comp.text.tex|, etc.
+  info/             \abbr{gnu} Info files, made from Texinfo sources
+  latex/            example of \replaceable{format}
+  . base/           \path|ltnews*|, \path|*guide|, etc.
+  . graphics/       \path|grfguide|
+  local/            site-specific documentation
+  man/              Unix man pages
+  <program>/        \TeX{}-related programs, by name (examples follow)
+  metafont/         \path|mfbook.tex|, \path|metafont-for-beginners|, etc.
+  metapost/         \path|mpman|, \path|manfig|, etc.
+  tex/              \path|texbook.tex|, \citetitle{A Gentle Introduction to \TeX{}}, etc.
+  web/              \path|webman|, \path|cwebman|
+\end{tdsSummary}
+
+
+\newpage
+\appendix
+
+\section{Unspecified pieces}
+
+The \abbr{TDS} cannot address the following aspects of a functioning
+\TeX{} system:
+
+\begin{enumerate}
+
+\item The location of executable programs: this is too site-dependent
+even to recommend a location, let alone require one. A site may place
+executables outside the \texmf{} tree altogether (e.g.,
+\path|/usr/local/bin|), in a platform-dependent directory within
+\texmf{}, or elsewhere.
+
+\item Upgrading packages when new releases are made: we could find no
+way of introducing version specifiers into \texmf{} that would do more
+good than harm, or that would be practical for even a plurality of
+installations.
+
+\item The location of implementation-specific files (e.g., \TeX{}
+\path|.fmt| files): by their nature, these must be left to the
+implementor or \TeX{} maintainer. See Section~\ref{sec:Example
+implementation-specific trees}.
+
+\item Precisely when a package or file should be considered ``local'',
+and where such local files are installed.  See Section~\ref{sec:Local
+additions} for more discussion.
+
+\end{enumerate}
+
+
+\subsection{Portable filenames}
+\label{sec:Portable filenames}
+
+The \abbr{TDS} cannot require any particular restriction on filenames in
+the tree, since the names of many existing \TeX{} files conform to no
+standard scheme. For the benefit of people who wish to make a portable
+\TeX{} distribution or installation, however, we outline here the
+necessary restrictions. The \abbr{TDS} specifications themselves are
+compatible with these.
+
+\abbr{ISO}-9660 is the only universally acceptable file system format
+for \abbr{CD-ROM}s.  A subset thereof meets the stringent limitations of
+all operating systems in use today. It specifies the following:
+
+\begin{itemize-squeeze}
+
+\item File and directory names, not including any directory path or
+extension part, may not exceed eight characters.
+
+\item Filenames may have a single extension.  Extensions may not exceed
+three characters. Directory names may not have an extension.
+
+\item Names and extensions may consist of \emphasis{only} the characters
+\literal{A}--\literal{Z}, \literal{0}--\literal{9}, and underscore.
+Lowercase letters are excluded.
+
+\item A period separates the filename from the extension and is always
+present, even if the name or extension is missing (e.g.,
+\path|FILENAME.| or \path|.EXT|).
+
+\item A version number, ranging from 1--32767, is appended to the file
+extension, separated by a semicolon (e.g., \path|FILENAME.EXT;1|).
+
+\item Only eight directory levels are allowed, including the top-level
+(mounted) directory (see Section~\ref{sec:Rooting the tree}).  Thus, the
+deepest valid \abbr{ISO}-9660 path is:
+\begin{ttdisplay}
+texmf/L2/L3/L4/L5/L6/L7/L8/FOO.BAR;1
+1     2  3  4  5  6  7  8
+\end{ttdisplay}
+The deepest \abbr{TDS} path needs only seven levels:
+\begin{ttdisplay}
+texmf/fonts/pk/cx/public/cm/dpi300/cmr10.pk
+1     2     3  4  5      6  7
+\end{ttdisplay}
+
+\end{itemize-squeeze}
+
+Some systems display a modified format of \abbr{ISO}-9660 names,
+mapping alphabetic characters to lowercase, removing version numbers and
+trailing periods, etc.
+
+Before the December 1996 release, \LaTeX{} used mixed-case names for
+font descriptor files.  Fortunately, it never relied on case alone to
+distinguish among the files.  Nowadays, it uses only monocase names.
+
+\section{Implementation issues}
+
+We believe that the \abbr{TDS} can bring a great deal of order to the
+current anarchic state of many \TeX{} installations.  In addition, by
+providing a common frame of reference, it will ease the burden of
+documenting administrative tasks.  Finally, it is a necessary part of
+any reasonable system of true ``drop-in'' distribution packages for
+\TeX{}.
+
+
+\subsection{Adoption of the \abbr{TDS}}
+
+[This section is retained for historical purposes; the \abbr{TDS}
+is now quite firmly entrenched in most \TeX{} distributions.]
+
+We recognize that adoption of the \abbr{TDS} will not be immediate or
+universal.  Most \TeX{} administrators will not be inclined to make the
+final switch until:
+
+\begin{itemize-squeeze}
+\item Clear and demonstrable benefits can be shown for the \abbr{TDS}.
+\item \abbr{TDS}-compliant versions of all key programs are available
+in ported, well-tested forms.
+\item A ``settling'' period has taken place, to flush out problems.  The
+public release of the first draft of this document was the first step in
+this process.
+\end{itemize-squeeze}
+
+Consequently, most of the first trials of the \abbr{TDS} will be made by
+members of the \abbr{TDS} committee and/or developers of \TeX{}-related
+software.  This has already taken place during the course of our
+deliberations (see Appendix~\ref{sec:Related references} for a sample
+tree available electronically).  They will certainly result in the
+production of a substantial number of \abbr{TDS}-compliant packages.
+Indeed, the \application{te\TeX{}} and \application{\TeX{} Live}
+distributions are \abbr{TDS}-compliant and in use now at many sites.
+
+Once installable forms of key \abbr{TDS}-compliant packages are more
+widespread, some \TeX{} administrators will set up \abbr{TDS}-compliant
+trees, possibly in parallel to existing production directories.  This
+testing will likely flush out problems that were not obvious in the
+confined settings of the developers' sites; for example, it should help
+to resolve system and package dependencies, package interdependencies, and
+other details not addressed by this \abbr{TDS} version.
+
+After most of the dust has settled, hopefully even conservative \TeX{}
+administrators will begin to adopt the \abbr{TDS}.  Eventually, most
+\TeX{} sites will have adopted the common structure, and most packages
+will be readily available in \abbr{TDS}-compliant form.
+
+We believe that this process will occur relatively quickly.  The
+\abbr{TDS} committee spans a wide range of interests in the \TeX{}
+community.  Consequently, we believe that most of the key issues
+involved in defining a workable \abbr{TDS} definition have been covered,
+often in detail.  \TeX{} developers have been consulted about
+implementation issues, and have been trying out the \abbr{TDS}
+arrangement.  Thus, we hope for few surprises as implementations mature.
+
+Finally, there are several (current or prospective) publishers of \TeX{}
+\abbr{CD-ROM}s.  These publishers are highly motivated to work out
+details of \abbr{TDS} implementation, and their products will provide
+inexpensive and convenient ways for experimentally-minded \TeX{}
+administrators to experiment with the \abbr{TDS}.
+
+
+\subsection{More on subdirectory searching}
+\label{sec:More on subdirectory searching}
+
+Recursive subdirectory searching is the ability to specify a search not
+only of a specified directory \replaceable{d}, but recursively of all
+directories below \replaceable{d}.
+
+Since the \abbr{TDS} specifies precise locations for most files, with no
+extra levels of subdirectories allowed, true recursive searching is not
+actually required for a \abbr{TDS}-compliant implementation. We do,
+however, strongly recommend recursive searching as the most
+user-friendly and natural approach to the problem, rather than
+convoluted methods to specify paths without recursion.
+
+This feature is already supported by many implementations of \TeX{} and
+companion utilities, for example \abbr{DECUS} \TeX{} for \abbr{VMS},
+\application{Dvips(k)}, \application{em\TeX{}} (and its drivers),
+\application{PubliC \TeX{}}, \application{Web2C}, \application{Xdvi(k)},
+and \application{Y\&Y\TeX{}}.  The Kpathsea library is a reusable
+implementation of subdirectory searching for \TeX{}, used in a number of
+the above programs.
+
+Even if your \TeX{} implementation does not directly support
+subdirectory searching, you may find it useful to adopt the structure if
+you do not use many fonts or packages. For instance, if you only use
+Computer Modern and \abbr{ams} fonts, it would be feasible to store them
+in the \abbr{TDS} layout and list the directories individually in
+configuration files or environment variables.
+
+The \abbr{TWG} recognizes that subdirectory searching places an extra
+burden on the system and may be the source of performance bottlenecks,
+particularly on slower machines.  Nevertheless, we feel that
+subdirectory searching is imperative for a well-organized \abbr{TDS},
+for the reasons stated in Section~\ref{sec:Subdirectory searching}.
+Implementors are encouraged to provide enhancements to the basic
+principle of subdirectory searching to avoid performance problems, e.g.,
+the use of a filename cache (this can be as simple as a recursive
+directory listing) that is consulted before disk searching begins.  If a
+match is found in the database, subdirectory searching is not required,
+and performance is thus independent of the number of subdirectories
+present on the system.
+
+Different implementations specify subdirectory searching differently.
+In the interest of typographic clarity, the examples here do not use the
+\replaceable{replaceable} font.
+
+\begin{description-squeeze}
+
+\item[\application{Dvips}:] via a separate
+\systemitem{ENVIRONVAR}{TEXFONTS\_SUBDIR} environment variable.
+
+\item[\application{em\TeX{}}:] \path|t:\subdir!!|; \path|t:\subdir!| for
+a single level of searching.
+
+\item[\application{Kpathsea}:] \path|texmf/subdir//|
+
+\item[\abbr{VMS}:] \path|texmf:[subdir...]|
+
+\item[\application{Xdvi} (patchlevel 20):] \path|texmf/subdir/**|;
+\path|texmf/subdir/*| for a single level of searching.  Version 20.50
+and above support the \path|//| notation.
+
+\item[\application{Y\&Y \TeX{}}:] \path|t:/subdir//| or
+\path|t:\subdir\\|.
+
+\end{description-squeeze}
+
+
+\subsection{Example implementation-specific trees}
+\label{sec:Example implementation-specific trees}
+
+The \abbr{TDS} cannot specify a precise location for
+implementation-specific files, such as \path|texmf/ini|, because a site
+may have multiple \TeX{} implementations.
+
+Nevertheless, for informative purposes, we provide here the default
+locations for some implementations. Please contact us with additions or
+corrections. These paths are not definitive, may not match anything at
+your site, and may change without warning.
+
+We recommend all implementations have default search paths that start
+with the current directory (e.g., `\path|.|').  Allowing users to
+include the parent directory (e.g., `\path|..|') is also helpful.
+
+
+\subsubsection{AmiWeb2c 2.0}
+
+(Email \email|scherer@physik.rwth-aachen.de| to contact the maintainer
+of this implementation.)
+
+AmiWeb2c 2 is compatible with Web2c 7 to the greatest possible
+extent, so only the very few differences are described in this
+section.  Detailed information about the basic concepts is given in
+the section for Web2c 7 below.
+
+Thanks to the \path|SELFAUTO| mechanism of Kpathsea 3.0 no specific
+location for the installation of AmiWeb2c is required as long as the
+general structure of the distribution is preserved.
+
+In addition to Kpathsea's \path|//| notation recursive path search may
+also be started by \replaceable{DEVICE}\path|:/|, e.g., \path|TeXMF:/|
+will scan this specific device completely.
+
+Binaries coming with the AmiWeb2c distribution are installed in the
+directory \path|bin/amiweb2c/| outside the common \abbr{TDS} tree
+\path|share/texmf/|.  In addition to the set of AmiWeb2c binaries
+you will find two subdirectories \path|local/| and \path|pastex/|
+with auxiliary programs.
+
+A stripped version of the Pas\TeX{} system (used by kind permission of
+Georg He\ss{}mann) is coming with AmiWeb2c, pre-installed in its own
+\path|share/texmf/amiweb2c/pastex/| directory.  If you want to use
+Pas\TeX{} you have to \path|assign| the name \path|TeX:| to this place.
+
+Documentation files in AmigaGuide format should be stored at
+\path|doc/guide/| similar to \path|doc/info/|.
+
+
+\subsubsection{Public \abbr{DECUS} \TeX{}}
+
+If another \abbr{VMS} implementation besides Public \abbr{DECUS} \TeX{}
+appears, the top level implementation directory name will be modified to
+something more specific (e.g., \path|vms_decus|).
+
+\begin{tdsSummary}
+  texmf/
+  . vms/            \abbr{VMS} implementation specific files
+  . . exe/          end-user commands
+  . . . common/     command procedures, command definition files, etc.
+  . . . axp/        binary executables for Alpha \abbr{AXP}
+  . . . vax/        binary executables for \abbr{VAX}
+  . . formats/      pool files, formats, bases
+  . . help/         \abbr{VMS} help library, and miscellaneous help sources
+  . . mgr/          command procedures, programs, docs, etc., for system management
+\end{tdsSummary}
+
+
+\subsubsection{Web2c 7}
+
+All implementation-dependent \TeX{} system files (\path|.pool|,
+\path|.fmt|, \path|.base|, \path|.mem|) are stored by default directly
+in \path|texmf/web2c|.  The configuration file \path|texmf.cnf| and
+various subsidiary \path|MakeTeX...| scripts used as subroutines are
+also stored there.
+
+Non-\TeX{} specific files are stored following the \abbr{GNU} coding
+standards.  Given a root directory \replaceable{prefix}
+(\path|/usr/local| by default), we have default locations as follows:
+
+\begin{tdsSummary}
+  <prefix>/         installation root (\path|/usr/local| by default)
+  . bin/            executables
+  . man/            man pages
+  . info/           info files
+  . lib/            libraries (\path|libkpathsea.*|)
+  . share/          architecture-independent files
+  . . texmf/        \abbr{TDS} root
+  . . . web2c/      implementation-dependent files (\path|.pool|, \path|.fmt|, \path|texmf.cnf|, etc.)
+\end{tdsSummary}
+
+See \url|http://www.gnu.org/prep/standards_toc.html| for the
+rationale behind and descriptions of this arrangement. A site may of
+course override these defaults; for example, it may put everything under
+a single directory such as \path|/usr/local/texmf|.
+
+
+\section{Is there a better way?}
+
+Defining the \abbr{TDS} required many compromises.  Both the overall
+structure and the details of the individual directories were arrived at
+by finding common ground among many opinions.  The driving forces were
+feasibility (in terms of what could technically be done and what could
+reasonably be expected from developers) and regularity (files grouped
+together in an arrangement that ``made sense'').
+
+Some interesting ideas could not be applied due to implementations
+lacking the necessary support:
+
+\begin{itemize}
+
+\item Path searching control at the \TeX{} level. If documents could
+restrict subdirectory searching to a subdirectory via some portable
+syntax in file names, restrictions on uniqueness of filenames could be
+relaxed considerably (with the cooperation of the formats), and the
+\TeX{} search path would not need to depend on the format.
+
+\item Multiple logical \texmf{} trees. For example, a site might have
+one (read-only) location for stable files, and a different (writable)
+location for dynamically-created fonts or other files. It would be
+reasonable for two such trees to be logically merged when searching.
+See Michael Downes' article in the references for how this can work in
+practice with Web2C.
+
+\end{itemize}
+
+\subsection{Macro structure}
+
+The \abbr{TWG} settled on the
+\replaceable{format}\path|/|\replaceable{package} arrangement after long
+discussion about how best to arrange the files.
+
+The primary alternative to this arrangement was a scheme which reversed
+the order of these directories:
+\replaceable{package}\path|/|\replaceable{format}.  This reversed
+arrangement has a strong appeal: it keeps all of the files related to a
+particular package in a single place.  The arrangement actually adopted
+tends to spread files out into two or three places (macros,
+documentation, and fonts, for example, are spread into different
+sections of the tree right at the top level).
+
+Nevertheless, the \replaceable{format}\path|/|\replaceable{package}
+structure won for a couple of reasons:
+
+\begin{itemize-squeeze}
+\item It is closer to current practice; in fact, several members of the
+\abbr{TWG} have already implemented the \abbr{TDS} hierarchy.  The
+alternative is not in use at any known site, and the \abbr{TWG} felt it
+wrong to mandate something with which there is no practical experience.
+
+\item The alternative arrangement increases the number of top-level
+directories, so the files that must be found using subdirectory
+searching are spread out in a wide, shallow tree.  This could have a
+profound impact on the efficiency of subdirectory searching.
+
+\end{itemize-squeeze}
+
+
+\subsection{Font structure}
+
+The \abbr{TWG} struggled more with the font directory structure than
+anything else. This is not surprising; the need to use the proliferation
+of PostScript fonts with \TeX{} is what made the previous arrangement
+with all files in a single directory untenable, and therefore what
+initiated the \abbr{TDS} effort.
+
+
+\subsubsection{Font file type location}
+
+We considered the supplier-first arrangement in use at many sites:
+
+\begin{ttdisplay}
+texmf/fonts/\replaceable{supplier}/\replaceable{typeface}/\replaceable{type}/
+\end{ttdisplay}
+
+This improves the maintainability of the font tree, since all files
+comprising a given typeface are in one place, but unless all the
+programs that search this tree employ some form of caching, there are
+serious performance concerns.  For example, in order to find a
+\path|TFM| file, the simplest implementation would require \TeX{} to
+search through all the directories that contain \abbr{PK} files in all
+modes and at all resolutions.
+
+In the end, a poll of developers revealed considerable resistance to
+implementing sufficient caching mechanisms, so this arrangement was
+abandoned.  The \abbr{TDS} arrangement allows the search tree to be
+restricted to the correct type of file, at least.  Concerns about
+efficiency remain, but there seems to be no more we can do without
+abandoning subdirectory searching entirely.
+
+We also considered segregating all font-related files strictly by file
+type, so that \MF{} sources would be in a directory
+\path|texmf/fonts/mf|, property list files in \path|texmf/fonts/pl|, the
+various forms of Type~1 fonts separated, and so on. Although more
+blindly consistent, we felt that the drawback of more complicated path
+constructions outweighed this. The \abbr{TDS} merges file types
+(\path|mf| and \path|pl| under \path|source|, \path|pfa| and \path|pfb|
+and \path|gsf| under \path|type1|) where we felt this was beneficial.
+
+
+\subsubsection{Mode and resolution location}
+
+We considered having the \path|mode| at the bottom of the font tree:
+\begin{ttdisplay}
+texmf/fonts/pk/\replaceable{supplier}/\replaceable{typeface}/\replaceable{mode}/\replaceable{dpi}/
+\end{ttdisplay}
+
+In this case, however, it is difficult to limit subdirectory searching
+to the mode required for a particular device.
+
+We then considered moving the \path|dpi|\replaceable{nnn} up to below
+the mode:
+\begin{ttdisplay}
+texmf/fonts/pk/\replaceable{mode}/\replaceable{dpi}/\replaceable{supplier}/\replaceable{typeface}/
+\end{ttdisplay}
+
+But then it is not feasible to omit the \path|dpi|\replaceable{nnn}
+level altogether on systems which can and do choose to use long
+filenames.
+
+
+\subsubsection{Modeless bitmaps}
+
+The \abbr{TDS} specifies using a single directory \path|modeless/| as
+the mode name for those utilities which generate bitmaps, e.g.,
+\path|texmf/fonts/modeless/times/|.  This has the considerable advantage
+of not requiring each such directory name to be listed in a search path.
+
+An alternative was to use the utility name below which all such
+directories could be gathered.  That has the advantage of separating,
+say, \path|gsftopk|-generated bitmaps from \path|ps2pk|-generated ones.
+However, we decided this was not necessary; most sites will use only one
+program for the purpose.  Also, \abbr{PK} and \abbr{GF} fonts generally
+identify their creator in the font comment following the \path|PK_ID|
+byte.
+
+We are making an implicit assumption that \MF{} is the only program
+producing mode-dependent bitmaps. If this becomes false we could add an
+abbreviation for the program to mode names, as in \path|mfcx| vs.\
+\path|xyzcx| for a hypothetical program \application{Xyz}, or we could
+at that time add an additional program name level uniformly to the tree.
+It seemed more important to concisely represent the current situation
+than to worry about hypothetical possibilities that may never~happen.
+
+
+\subsection{Documentation structure}
+
+We considered placing additional documentation files in the same
+directory as the source files for the packages, but we felt that users
+should be able to find documentation separately from sources, since most
+users have no interest in sources.
+
+We hope that a separate, but parallel, structure for documentation would
+(1)~keep the documentation together and (2)~make it as straightforward
+as possible for users to find the particular documentation they were
+after.
+
+
+\section{Related references}
+\label{sec:Related references}
+
+This appendix gives pointers to related files and other documents.  For
+\abbr{CTAN} references, we use \path|http://www.ctan.org| as the
+top-level domain only to make the links be live in this document.  See
+\url|http://www.ctan.org/tex-archive/CTAN.sites| for a complete list of
+\abbr{ctan} sites; there are mirrors worldwide.
+
+\begin{itemize-squeeze}
+
+\item This document, in many formats (tex, dvi, info, pdf):\\ \hspace*{1em}
+\url|http://tug.org/tds/|
+
+\item The \abbr{TDS} mailing list archives:\\ \hspace*{1em}
+\url|http://tug.org/mail-archives/twg-tds/|
+
+\item The level~0 \abbr{DVI} driver standard:\\ \hspace*{1em}
+\url|http://www.ctan.org/tex-archive/dviware/driv-standard/level-0/|
+
+\item \citetitle{Filenames for \TeX{} fonts}, with lists of recommended
+supplier and typeface names:\\ \hspace*{1em}
+\url|http://tug.org/fontname/|
+
+\item \abbr{ISO}-9660 \abbr{CD-ROM} file system standard:\\ \hspace*{1em}
+\url|http://www.iso.ch/cate/cat.html|
+
+\item \citetitle{Components of \TeX{}}, a paper by Joachim
+Schrod:\\ \hspace*{1em}
+\url|http://www.ctan.org/tex-archive/documentation/components-of-TeX/|
+
+\item \citetitle{Managing Multiple TDS trees}, an article by Michael
+Downes:\\ \hspace*{1em}
+\url|http://tug.org/TUGboat/Articles/tb22-3/tb72downes.pdf|
+
+\item A complete set of \MF{} modes:\\ \hspace*{1em}
+\url|http://www.ctan.org/tex-archive/fonts/modes/modes.mf|
+
+\item A large collection of \BibTeX{} databases and styles:\\ \hspace*{1em}
+\url|ftp://ftp.math.utah.edu/pub/tex/bib/|
+
+\end{itemize-squeeze}
+
+
+\section{Contributors}
+
+The \abbr{TWG} has had no physical meetings; electronic mail was the
+communication medium.
+
+Sebastian Rahtz is the \TeX{} Users Group Technical Council liaison.
+Norman Walsh was the original committee chair.  Karl Berry is the
+current editor.
+
+The list of contributors has grown too large to fairly include, as some
+would surely be inadvertently omitted.  Please consider the archives of
+the \email|tds@tug.org| and \email|tex-live@tug.org| mailing lists as
+the record of contributions.
+
+
+\end{document}
diff --git a/Master/texmf-dist/doc/generic/tds/tds2texi.el b/Master/texmf-dist/doc/generic/tds/tds2texi.el
new file mode 100644
index 00000000000..de87d404304
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tds2texi.el
@@ -0,0 +1,577 @@
+;;; tds2texi.el --- convert TDS draft from LaTeX to Texinfo
+
+;; Copyright (C) 1996, 1999, 2003, 2004 Ulrik Vieth and the TeX Users Group.
+
+;; This programm 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, 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 a copy of the GNU General Public License; see the
+;; file COPYING.  If not, write to the Free Software Foundation, Inc.,
+;; 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+
+
+;; Author: Ulrik Vieth <vieth@thphy.uni-duesseldorf.de>
+;; Maintainer: karl@mail.tug.org
+;; Version: $Id: tds2texi.el,v 1.12 2004/06/04 17:25:49 karl Exp $
+;; Keywords: TDS, LaTeX, Texinfo, Info, HTML, tex, maint
+
+;;; Commentary:
+
+;; Description:
+;;
+;; This file provides a limited LaTeX-to-Texinfo conversion function
+;; `tds2texi-convert' which is intended to convert the LaTeX
+;; source of the TDS draft document `tds.tex', using a couple of
+;; special markup tags defined in the document class `tdsguide.cls'.
+;; It is definitely *not* suitable to be used as a general-purpose
+;; LaTeX-to-Texinfo converter and is not intended to be used as such.
+;;
+
+;; Usage (also see the Makefile):
+;;
+;; 0. load or autoload this file, e.g: (load-library "tds2texi")
+;;
+;; 1. go to a directory containing `tds.tex', e.g. in dired mode
+;;
+;; 2. run M-x tds2texi-convert -- this does all the conversion and
+;;    leaves you in a buffer `tds.texi' containing the converted file
+;; 
+;; 3. edit the buffer if necessary and save it -- you will be asked
+;;    for a file name (which should be `tds.texi', of course)
+;; 
+;; 4. run M-x makeinfo-buffer or invoke makeinfo and/or texi2html
+;;    from the shell -- don't try texi2dvi, it may work all right,
+;;    but it's not recommended since it will only cause confusion
+;;    with the DVI file created from the original LaTeX source!
+;;
+
+;; Bugs:
+;;
+;; * whitespace (esp. blank lines) before and after environments
+;;   will be inconsistent (should be fixed in the LaTeX version!)
+;;
+;; * whitespace (esp. indentation) in tdsSummary environments
+;;   will be inconsistent (should be fixed in the LaTeX version!)
+;;
+;; * labels are references are assumed to coincide with names
+;;   of @nodes -- this is not always true, e.g. for MF vs. \MF{}
+;;   
+;; * the last comma in the list of contributors should be a period
+;;
+;; * the list of contributors should be handled in a better way
+;;   (currently: LaTeX tabbing -> @quotation -> HTML <blockquote>)
+;;
+;; * the contents of the top node may get lost in the texi2html
+;;   conversion under some circumstances, or else it may end up
+;;   in the wrong split file -- this seems to be a texi2html bug
+;;   
+
+;; History:
+;;
+;; v 0.0 -- 1996/01/23  UV  created
+;; v 0.1 -- 1996/01/24  UV  first rough version, posted to twg-tds
+;; v 0.2 -- 1996/01/24  UV  added some commentary and doc strings
+;; v 0.3 -- 1996/01/25  UV  modularized code, handle header and trailer,
+;;                          call texinfo routines for @nodes and @menus
+;; v 0.4 -- 1996/01/27  UV  slightly touched-up and some doc fixes,
+;;                          improved handling of legalnotice header 
+;; v 0.5 -- 1996/01/28  UV  more documentation added, code freeze
+;;
+;; v 1.0 -- 1996/02/20  UV  renamed to tds2texi, bumped version number,
+;;                          also fixed a minor typo in "@item samp"
+;; v 1.1 -- 1996/11/12  KB  no node pointers, no double blank line after
+;;                          sections, allow braces after abbrevs.
+;; v 1.2 -- 1996/11/16  KB  ??? (see ChangeLog)
+;; v 1.3 -- 1996/11/18  UV  added translation for umlaut accents,
+;;                          added tds2texi-direntry header lines,
+;;                          added function tds2texi-fixup-texinfo,
+;;                          fixed bug when combining multiple "@file"s.
+
+
+;;; Code:
+
+(require 'texinfo)	; needed to update @nodes and @menus
+
+;; file name variables
+
+(defvar tds2texi-source-file "tds.tex"
+  "File name of TDS LaTeX source to be converted.")
+
+(defvar tds2texi-target-file "tds.texi"
+  "File name of TDS Texinfo source to be created.")
+
+(defvar tds2texi-filename "tds.info"
+  "File name of Info file to be inserted in Texinfo header.")
+
+(defvar tds2texi-direntry
+  (concat
+   "@dircategory TeX\n"
+   "@direntry\n"
+   "* TeX Directories: (tds).       A directory structure for TeX files.\n"
+   "@end direntry\n"))
+
+;; translation tables
+
+(defvar tds2texi-logos-alist
+  '(("{\\TeX}"       . "TeX")		; when only doing Info
+    ("\\TeX{}"       . "TeX")		; no need to use "@TeX{}"
+    ("{\\LaTeX}"     . "LaTeX")
+    ("\\LaTeX{}"     . "LaTeX")
+    ("{\\LaTeXe}"    . "LaTeX2e")
+    ("\\LaTeXe{}"    . "LaTeX2e")
+    ("{\\AmS}"       . "AMS")
+    ("\\AmS{}"       . "AMS")
+    ("{\\AMSTeX}"    . "AMS-TeX")
+    ("\\AMSTeX{}"    . "AMS-TeX")
+    ("\\MF{}"        . "Metafont")
+    ("\\MP{}"        . "MetaPost")
+    ("\\BibTeX{}"    . "BibTeX")
+    ("{\\iniTeX}"    . "INITEX")
+    ("\\iniTeX{}"    . "INITEX")
+    ("{\\iniMF}"     . "INIMF")
+    ("\\iniMF{}"     . "INIMF")
+    ("{\\iniMP}"     . "INIMP")
+    ("\\iniMP{}"     . "INIMP")
+    ("{\\PS}"        . "PostScript")
+    ("\\PS{}"        . "PostScript")
+    ("{\\copyright}" . "@copyright{}")
+    )
+  "List of TeX logos and their replacement text after conversion.")
+
+(defvar tds2texi-logos-regexp-1 "\\(\\\\[A-Za-z]+{}\\)"
+  "Regexp for TeX logos to be converted using `tds2texi-logos-alist'.")
+
+(defvar tds2texi-logos-regexp-2 "\\({\\\\[^}]+}\\)"
+  "Regexp for TeX logos to be converted using `tds2texi-logos-alist'.")
+
+;;
+
+(defvar tds2texi-tags-alist
+  '(("\\emphasis"    . "@emph")
+    ("\\citetitle"   . "@cite")
+    ("\\literal"     . "@file")
+    ("\\replaceable" . "@var")
+    ("\\command"     . "@code")			; defined, but not used
+    ;; ("\\application" . "@r")			; unnecessary, but ...
+    ;; ("\\abbr"        . "@sc")		; unnecessary, but ...
+    )
+  "List of markup tags and their replacement text after conversion.")
+
+(defvar tds2texi-tags-regexp "\\(\\\\[a-z]+\\)"
+  "Regexp for markup tags to be converted using `tds2texi-tags-alist'.")
+
+;;
+
+(defvar tds2texi-env-alist
+  '(("\\begin{ttdisplay}"           . "@example")
+    ("\\end{ttdisplay}"             . "@end example")
+    ("\\begin{tdsSummary}"          . "@example")
+    ("\\end{tdsSummary}"            . "@end example")
+    ("\\begin{enumerate}"           . "@enumerate")
+    ("\\end{enumerate}"             . "@end enumerate")
+    ("\\begin{enumerate-squeeze}"   . "@enumerate")
+    ("\\end{enumerate-squeeze}"     . "@end enumerate")
+    ("\\begin{itemize}"             . "@itemize @bullet")
+    ("\\end{itemize}"               . "@end itemize")
+    ("\\begin{itemize-squeeze}"     . "@itemize @bullet")
+    ("\\end{itemize-squeeze}"       . "@end itemize")
+    ("\\begin{description}"         . "@itemize @bullet")
+    ("\\end{description}"           . "@end itemize")
+    ("\\begin{description-squeeze}" . "@itemize @bullet")
+    ("\\end{description-squeeze}"   . "@end itemize")
+    ("\\begin{legalnotice}"         . "@titlepage")	; special hack
+    ("\\end{legalnotice}"           . "@end titlepage")
+    ("\\begin{tabbing}"             . "@quotation")	; special hack
+    ("\\end{tabbing}"               . "@end quotation")
+    )
+  "List of environments and their replacement text after conversion.")
+
+(defvar tds2texi-env-regexp "\\(\\\\\\(begin\\|end\\){[^}]+}\\)"
+  "Regexp for environments to be converted using `tds2texi-env-alist'.")
+
+
+;;; some utility functions
+
+(defun tds2texi-string-replace (x-string x-replace)
+  "Searches for occurences of X-STRING, replacing them by X-REPLACE."
+  (save-excursion
+    (while (search-forward x-string nil t)
+      (replace-match x-replace t t)))) 		; use fixed case!
+
+(defun tds2texi-regexp-replace (x-regexp x-replace)
+  "Searches for occurences of X-REGEXP, replacing them by X-REPLACE."
+  (save-excursion
+    (while (re-search-forward x-regexp nil t)
+      (replace-match x-replace t nil)))) 	; use fixed case!
+
+
+(defun tds2texi-alist-replace (x-regexp x-alist)
+  "Searches for ocurrences of X-REGEXP, replacing them using X-ALIST.
+If no match is found in X-ALIST, leaves the original text unchanged."
+  (save-excursion
+    (let (x-match 
+	  x-replace)
+      (while (re-search-forward x-regexp nil t)
+	(setq x-match (match-string 1))
+	(setq x-replace (or (cdr (assoc x-match x-alist)) x-match))
+	(replace-match x-replace t t)))))	; use fixed case!
+
+
+;;; the main conversion function
+
+(defun tds2texi-convert ()
+  "Have a try at converting LaTeX to Texinfo.  Good luck!"
+  (interactive)
+
+  ;; get a buffer to operate on and insert the LaTeX source
+  (set-buffer (get-buffer-create tds2texi-target-file))
+  (erase-buffer)
+  (insert-file-contents-literally tds2texi-source-file)
+  
+  ;; tab characters can mess up tds-summary envrionments,
+  ;; so get rid of them as soon as possible
+  (untabify (point-min) (point-max))
+  (goto-char (point-min))
+  
+  ;; do the conversion steps for the text body
+  (tds2texi-do-simple-tags)	; mostly general
+  (tds2texi-do-fancy-logos)	; mostly specific to TDS
+  (tds2texi-do-sectioning)	; mostly general
+  (tds2texi-do-markup-tags)	; mostly specific to TDS
+  (tds2texi-do-environments)	; partly specific to TDS
+  
+  ;; do the conversion for header and trailer
+  (tds2texi-do-header)		; partly specific to TDS
+  (tds2texi-do-trailer)		; partly specific to TDS
+  
+  ;; standard Texinfo functions
+  ; (texinfo-every-node-update) ; I don't like the extra node pointers.
+  (texinfo-all-menus-update)
+  (texinfo-master-menu nil)
+
+  (tds2texi-fixup-texinfo)
+
+  ;; all that's left to do is saving the buffer to a file
+  ;; -- we simply select the buffer and leave saving it to
+  ;; the user in case some manual intervention is needed
+  (switch-to-buffer tds2texi-target-file)
+  )
+
+
+;;; various steps of the conversion process
+
+(defun tds2texi-do-simple-tags ()
+  "First step of \\[tds2texi-convert].  Not useable by itself."
+
+  ;; literal `@' -- should come before anything else, since it's
+  ;; the Texinfo control character.
+  (tds2texi-regexp-replace "\\([^\\\\]\\)@" "\\1@@")
+  
+  ;; fancy spacing -- should come early before we have many `@'
+
+  ;; "\@" -- space factor corrections before sentence end `.'
+  (tds2texi-regexp-replace "\\\\@\\." "@.")
+  ;; "\ " -- control space after `.' in the middle of sentences.  Also
+  ;; converts \\ to \.
+  (tds2texi-regexp-replace "\\.\\\\\\([ \n]+\\)" ".@:\\1")
+  ;; "\ " -- control space used otherwise
+  (tds2texi-regexp-replace "\\\\\\([ \n]+\\)" "\\1")
+
+  ;; "\," -- thin space used with dimensions like "dpi" or "pt"
+  (tds2texi-regexp-replace "\\\\,\\([a-z]+\\)" "@dmn{\\1}")
+
+  ;; "\\" -- forced line breaks in references, where it's always
+  ;; preceded by a :.  Previous "\ " conversion reduced \\ to \.
+  (tds2texi-string-replace ":\\ " ":@*\n")
+
+  ;; "\"" -- accents etc.:
+  (tds2texi-string-replace "\\\"" "@\"")
+  (tds2texi-string-replace "\\ss" "@ss")
+
+  ;; special TeX characters that needn't be quoted in Texinfo:
+  (tds2texi-string-replace "\\_" "_")
+  (tds2texi-string-replace "\\&" "&")
+  (tds2texi-string-replace "\\%" "%")
+
+  ;; special TeX characters that we prefer to transliterate:
+  (tds2texi-regexp-replace "\\\\slash[ ]*" "/")
+
+  ;; we could translate $...$ into @math{...}, but why bother
+  ;; when we can transliterate it easily?
+  (tds2texi-string-replace "$" "")
+  (tds2texi-string-replace "\\pm" "+-")
+)
+
+
+(defun tds2texi-do-fancy-logos ()
+  "Second step of \\[tds2texi-convert].  Not useable by itself."
+
+  ;; fancy TeX logos -- these are used in arguments of sections,
+  ;; so we have to do them early before doing sectioning commands.
+  (tds2texi-alist-replace tds2texi-logos-regexp-1 tds2texi-logos-alist)
+  (tds2texi-alist-replace tds2texi-logos-regexp-2 tds2texi-logos-alist)
+  
+  ;; acronyms -- these are also used in arguments of sections.
+  ;; There's no need to use @sc markup, just upcase the argument.
+  (save-excursion
+    (while (re-search-forward "\\\\abbr{\\([^}]+\\)}" nil t)
+      (replace-match (upcase (match-string 1)) nil t)))
+  
+  ;; applications -- similar to acronyms, so done here as well.
+  ;; There's no need to use @r markup either, it's the default!
+  (tds2texi-regexp-replace "\\\\application{\\([^}]+\\)}" "\\1")
+  )
+
+
+(defun tds2texi-do-sectioning ()
+  "Third step of \\[tds2texi-convert].  Not useable by itself."
+
+  ;; first do @chapter and @appendix by narrowing
+  (save-excursion
+    (save-restriction
+      (narrow-to-region 
+       (point-min) (search-forward "\\appendix" nil t))
+      (goto-char (point-min))
+      (tds2texi-regexp-replace 
+       "\\\\section{\\([^}]+\\)}[ ]*" "@node \\1\n@chapter \\1")
+      ))
+  (save-excursion
+    (save-restriction
+      (narrow-to-region 
+       (search-forward "\\appendix" nil t) (point-max))
+      (tds2texi-regexp-replace 
+       "\\\\section{\\([^}]+\\)}[ ]*" "@node \\1\n@appendix \\1")
+      ))
+  
+  ;; @section and @subsection are just shifted a level up
+  (tds2texi-regexp-replace 
+   "\\\\subsection{\\([^}]+\\)}[ ]*"    "@node \\1\n@section \\1")
+  (tds2texi-regexp-replace 
+   "\\\\subsubsection{\\([^}]+\\)}[ ]*" "@node \\1\n@subsection \\1")
+  
+  ;; now we no longer need \appendix as a marker
+  (tds2texi-regexp-replace "\\\\appendix[ ]*\n" "")
+
+  ;; \newpage can go as well
+  (tds2texi-regexp-replace "%?\\\\newpage[ ]*\n" "")
+  
+  ;; \labels are redundant since we have @nodes
+  (tds2texi-regexp-replace "\\\\label{sec:\\([^}]+\\)}[ ]*\n" "")
+
+  ;; \refs now refer to @nodes instead of \labels
+  (tds2texi-regexp-replace "\\\\ref{sec:\\([^}]+\\)}" "@ref{\\1}")
+  )
+
+
+(defun tds2texi-do-markup-tags ()
+  "Fourth step of \\[tds2texi-convert].  Not usable by itself."
+
+  ;; special tags -- for \CTAN, we must used fixed-case replace!
+  (tds2texi-string-replace "\\the\\tdsVersion" "@value{version}")
+  (tds2texi-string-replace "\\texmf{}" "@file{texmf}")
+  (tds2texi-string-replace "\\CTAN:"   "@file{@var{CTAN}:}")
+  
+  ;; convert simple tags without expanding their arguments:
+  ;; \emphasis, \citetitle, \literal, \replaceable
+  (tds2texi-alist-replace tds2texi-tags-regexp tds2texi-tags-alist)
+  
+  ;; \\systemitem -- a silly tag with an extra argument that
+  ;; isn't printed.  It is used exactly once!
+  (tds2texi-regexp-replace
+   "\\\\systemitem{\\([^}]+\\)}{\\([^}]+\\)}" "@file{\\2}")
+  
+  ;; \path, \url -- here we can't avoid shuffling the argument
+  (tds2texi-regexp-replace "\\\\path|\\([^|]+\\)|" "@file{\\1}") 
+  (tds2texi-regexp-replace "\\\\url|\\([^|]+\\)|" "@uref{\\1}") 
+  (tds2texi-regexp-replace "\\\\email|\\([^|]+\\)|" "@email{\\1}") 
+  
+  ;; After turning \replaceable into @var above we now have to
+  ;; turn @var{...} into @file{@var{...}} to get quotation marks
+  ;; around file names consistent.  (Read: those extra quotation
+  ;; marks inserted automatically by makeinfo in the @file tag.)
+
+  ;; For simplicity we first do the change everywhere and then
+  ;; undo it again inside `ttdisplay' environments, where we
+  ;; can leave @var by itself as @file isn't used there anyway.
+
+  (tds2texi-regexp-replace "@var{\\([^}]+\\)}" "@file{@var{\\1}}")
+  (save-excursion
+    (while (search-forward "\\begin{ttdisplay}" nil t)			     		   
+      (save-restriction
+	(narrow-to-region
+	 (point) (search-forward "\\end{ttdisplay}" nil t))
+	(goto-char (point-min))
+	(tds2texi-regexp-replace "@file{@var{\\([^}]+\\)}}" "@var{\\1}")
+	)))
+  
+  ;; eliminate redundant quotation marks around @file
+  (tds2texi-regexp-replace "``\\(@file{[^}]+}\\)''" "\\1")
+  (tds2texi-regexp-replace "`\\(@file{[^}]+}\\)'" "\\1")
+  
+  ;; ... and combine multiple @file{}s in one line
+  (tds2texi-regexp-replace 
+   "@file{\\([^ ]+\\)}@file{\\([^ ]+\\)}@file{\\([^ ]+\\)}" "@file{\\1\\2\\3}")
+  (tds2texi-regexp-replace 
+   "@file{\\([^ ]+\\)}@file{\\([^ ]+\\)}" "@file{\\1\\2}")
+
+  ;; ... also simplify cases of nested @file{}s
+  (tds2texi-regexp-replace 
+   "@file{@file{\\([^ ]+\\)}\\([^ ]+\\)}" "@file{\\1\\2}")
+
+  ;; literal `~' -- if it hasn't been converted to space earlier,
+  ;; we can now do the conversion to @w{word1 word2} without
+  ;; running the risk of confusion the regexp matcher somewhere.
+  ;; Unfortunately @w will get lost again in the HTML conversion
+  ;; because &nbsp; or &#160; are not yet standard HTML tags.
+  (tds2texi-string-replace "~" "@tie{}")
+  )
+
+
+(defun tds2texi-do-environments ()
+  "Fifth step of \\[tds2texi-convert].  Not useable by itself."
+  
+  ;; convert \begin and \end of environments
+  (tds2texi-alist-replace tds2texi-env-regexp tds2texi-env-alist)
+
+  ;; convert \items
+  (tds2texi-string-replace "\\item"  "@item")
+
+  ;; insert newlines after description items where appropriate
+  (tds2texi-regexp-replace
+   "@item\\[\\([^]]+\\)\\][ ]*\n" "@item \\1\n")
+  (tds2texi-regexp-replace
+   "@item\\[\\([^]]+\\)\\][ ]*"   "@item \\1\n")
+
+  ;; insert newlines after @item @file, also replace @item @file
+  ;; by @item @samp -- this is done because it may look nicer
+  ;; in the HTML version, but it depends on the style sheet used
+  (tds2texi-regexp-replace 
+   "@item @file\\([^,\n]*\\),[ ]*" "@item @samp\\1,\n")
+  (tds2texi-regexp-replace 
+   "@item @file" "@item @samp")
+  )
+
+
+;;; handling the header and trailer
+
+(defun tds2texi-do-header ()
+  "Convert LaTeX header to Texinfo.  Used in \\[tds2texi-convert]."
+  (let (title-string
+	author-string
+	version-string)
+
+    ;; collect information
+    (save-excursion
+      (re-search-forward "\\\\tdsVersion{\\(.*\\)}" nil t)
+      (setq version-string (match-string 1))
+      (re-search-forward "\\\\title{\\(.*\\)}" nil t)
+      (setq title-string (match-string 1))
+      (re-search-forward "\\\\author{\\(.*\\)}" nil t)
+      (setq author-string (match-string 1))
+      )
+
+    ;; discard information lines
+    (tds2texi-regexp-replace "\\\\title{.*}[ ]*\n"         "")
+    (tds2texi-regexp-replace "\\\\author{.*}[ ]*\n"        "")
+    (tds2texi-regexp-replace "\\\\tdsVersion{.*}[ ]*\n\n"  "")
+    
+    ;; discard pre-title lines
+    (tds2texi-regexp-replace "%&latex[ ]*\n"               "")
+    (tds2texi-regexp-replace "\\\\NeedsTeXFormat.*\n"      "")
+    
+    ;; convert \documentclass to \input texinfo
+    (tds2texi-regexp-replace "\\\\documentclass.*\n\n"  "\\\\input texinfo\n")
+
+    ;; insert Texinfo header lines
+    (save-excursion
+      (goto-char (search-forward "texinfo\n" nil t))
+      (insert "@setfilename " tds2texi-filename "\n")
+      (insert "@settitle " title-string "\n\n")
+      (insert "@set version " version-string "\n\n")
+      (insert tds2texi-direntry "\n")
+      )
+ 
+    ;; discard \begin{document} and \maketitle
+    (tds2texi-regexp-replace "\\\\begin{document}[ ]*\n\n" "")
+    (tds2texi-regexp-replace "\\\\maketitle[ ]*\n\n"       "")
+
+    ;; copy contents of `legalnotice' environments
+    (save-excursion
+      (let ((begin (search-forward "@titlepage\n\n" nil t))
+	    (end (progn
+		   (search-forward "@end titlepage" nil t)
+		   (match-beginning 0))))
+	(copy-region-as-kill begin end)
+	))
+
+    ;; insert stuff for title page before `legalnotice' environment
+    ;; -- \begin{legalnotice} has been converted to @titlepage
+    (save-excursion
+      (goto-char (search-forward "@titlepage\n" nil t))
+      (insert "@title " title-string "\n")
+      (insert "@subtitle Version @value{version}\n")
+      (insert "@author " author-string "\n\n")
+      (insert "@page\n@vskip 0pt plus 1filll\n")
+      )
+
+    ;; insert stuff for @node Top and master menu after `legalnotice'
+    ;; -- \end{legalnotice} has been converted to @end titlepage
+    (save-excursion
+      (goto-char (search-forward "@end titlepage\n\n" nil t))
+      
+      (insert "@ifnottex\n")
+      (insert "@node Top\n@top " title-string "\n\n")
+      
+      ;; insert contents of `legalnotice' copied above
+      (yank)	; should include a "\n\n" at the end
+
+      (insert "@menu\n@end menu\n")
+      (insert "@end ifnottex\n\n")
+      )
+
+    ;; discard \tableofcontents -- @contents belongs in the trailer
+    (tds2texi-regexp-replace "\\\\tableofcontents[ ]*\n\n" "")
+    ))
+
+(defun tds2texi-do-trailer ()
+  "Convert LaTeX trailer to Texinfo.  Used in \\[tds2texi-convert]."
+  
+  ;; The list of contributors is a LaTeX tabbing environment, which 
+  ;; is difficult to convert -- we convert it to a normal paragraph
+  ;; inside a @quotation environment, so it gets indented a little.
+
+  ;; Conversion of the tabbing environment is already done elsewhere,
+  ;; so we just have to remove some redundant tags.
+
+  ;; discard alignment preamble consisting of lines starting with
+  ;; \hspace{0.25\linewidth}.  We use \hspace in other places too.
+  (tds2texi-regexp-replace "\\\\hspace.*\n" "")
+
+  ;; convert "\>" and "\\" in tabbing environment to comma
+  (tds2texi-regexp-replace " +\\\\>[ ]*" ", ")
+
+  ;; In the earlier conversion of "\ ", "\\" followed by newline
+  ;; was already converted to "\", so we just have to convert
+  ;; the remaining instances of "\" followed by space or newline.
+  (tds2texi-regexp-replace "\\s +\\\\\\s +" ", ")
+
+  ;; convert \end{document} to @contents and @bye
+  (tds2texi-string-replace "\\end{document}"
+                           "@iftex\n@contents\n@end iftex\n@bye")
+  )
+
+(defun tds2texi-fixup-texinfo ()
+  "Fix up a few last-minute items.  Used in \\[tds2texi-convert]."
+
+  ;; Fix the reference to the node name with the logo.
+  (tds2texi-string-replace "Non-font MF" "Non-font Metafont")
+  )
+
+;;; tds2texi.el ends here
diff --git a/Master/texmf-dist/doc/generic/tds/tdsguide.cls b/Master/texmf-dist/doc/generic/tds/tdsguide.cls
new file mode 100644
index 00000000000..45267762588
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/tds/tdsguide.cls
@@ -0,0 +1,845 @@
+% $Id: tdsguide.cls,v 1.19 2004/03/28 14:21:10 karl Exp $
+% LaTeX document class tdsguide
+% (history at end)
+%
+% This class provides markup & layout for the TDS report.
+%
+\NeedsTeXFormat{LaTeX2e}[1994/12/01]    % star-form of \CheckCommand, etc.
+
+
+% The code below is explained in the implementation documentation of the
+% rcs package.
+
+\begingroup
+    \def\RCSClass#1#2 $#3: #4 #5\endRCS $#6: #7 #8\endRCS{%
+        \def\date{#4}\def\id{v#7}%
+        \ProvidesClass{#1}[\date\space\id\space #2]%
+        }
+
+  \RCSClass{tdsguide}{markup and layout for TDS document}
+  $Date: 2004/03/28 14:21:10 $: 9999/00/00 \endRCS
+  $Revision: 1.19 $: 0.0 \endRCS
+\endgroup
+
+
+% default setup
+\ifx \CatEscape\undefined
+    \chardef\CatEscape=0
+    \chardef\CatOpen=1
+    \chardef\CatClose=2
+    \chardef\CatIgnore=9
+    \chardef\CatLetter=11
+    \chardef\CatOther=12
+    \chardef\CatActive=13
+
+    \chardef\CatUsCode=\catcode`\_
+\fi
+
+
+
+%%% ======================================================================
+
+%
+%       OPTIONS
+%
+
+\catcode`\_=\CatLetter
+
+
+% We can select to use Roman for METAFONT/METAPOST logos by the
+% nomflogo option. That should be done if no current logo fonts (with
+% `P' & `S') are available. Of course, it would be best to install
+% current fonts.
+%     The mflogo options is provided for upward compatibility.
+
+\let\tds_mflogo\relax
+\DeclareOption{nomflogo}{%
+    \def\tds_mflogo{\let\textlogo\tds@transfer@logo} % gimme refinements! :(
+    }
+\DeclareOption{mflogo}{}
+
+
+\newif\ifTdsDraft
+        \TdsDraftfalse
+\DeclareOption{draft}{%
+    \TdsDrafttrue
+    \PassOptionsToClass{\CurrentOption}{article}%
+    }
+\DeclareOption{final}{%
+    \TdsDraftfalse
+    \PassOptionsToClass{\CurrentOption}{article}%
+    }
+
+
+\catcode`\_=\CatUsCode
+
+
+%%% ------------------------------------------------------------
+
+
+%
+%       CONFIGURATION, INHERITANCE, AND OTHER MODULES
+%
+
+
+% configure this class
+
+\InputIfFileExists{tdsguide.cfg}{%
+        \typeout{*************************************^^J%
+                 *^^J%
+                 * Local config file tdsguide.cfg used^^J%
+                 *^^J%
+                 *************************************%
+                 }%
+    }{}
+
+
+% inherit article class
+
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+\ProcessOptions
+\LoadClass{article}
+
+
+% add more modules
+
+\RequirePackage{url}                    % file names & email addresses
+\RequirePackage{mflogo}                 % MF & MP logos (but see below)
+%\RequirePackage{hyperref}               % navigation specials in .dvi
+\RequirePackage{fancyhdr}               % rev. no & draft notice in headers
+
+% Put hypertext links in the DVI file on the URL's:
+% \def\UrlLeft#1\UrlRight{\special{html:<a href="#1">}#1\special{html:</a>}}
+% Don't do this because xdvi doesn't know what do with ftp url's, which
+% is the vast majority of links; also because we use the url package for
+% mere directory names.
+
+
+%%% ============================================================
+
+
+%
+%       NEW MARKUP
+%
+
+\catcode`\_=\CatLetter
+
+% info about original SGML files
+
+\def\sourcefile#1{}
+\def\formatterfile#1{}
+
+% revision number (should use rcs package)
+
+\newtoks\tdsVersion
+
+
+
+%
+%       RENDER DOCUMENT-SPECIFIC MARKUP
+%
+
+% categories for terms
+
+% typewriter type.
+%  `_', `\_', and `\\' produce respective chars.
+
+\def\tds_tt{%
+    \begingroup
+        \catcode`\_=\CatOther
+        \chardef\_=`\_
+        \chardef\\=`\\
+        \tds_tt_set
+    }
+\def\tds_tt_set#1{%
+        \ttfamily
+        #1%
+    \endgroup
+    }
+
+\def\systemitem#1{\tds_tt}
+\def\replaceable#1{{\rmfamily $\langle$\textit{#1}$\rangle$}}
+\let\command=\tds_tt
+\def\application#1{\textrm{#1}}
+\let\literal=\tds_tt
+\let\email=\url
+
+% \abbr may be called with lowercase & uppercase letters, actually all
+% abbreviations are to be typeset with reduced-size uppercase letters.
+% (That lowercase letters are used as arguments was a half-hearted
+% attempt by Norm who did use small caps at this time.) `Reduced size'
+% means one point smaller than the current size. If the reduced size
+% is larger than 12pt, we issue a warning; if no font-generating
+% driver is used, this situation will lead to character replacements
+% most probably.
+%
+% This macro may be written to an auxilliary file, we must not use
+% underscores in its name.
+
+\DeclareRobustCommand\tds@reduced@size{%
+    \dimen@\f@size\p@
+    \advance \dimen@ -\p@               % dimen@ = font_size - 1
+    \ifdim \dimen@ >12\p@
+        \@font@warning{%
+Using font size `\the\dimen@' for abbreviations. That might lead%
+\MessageBreak
+to character replacements if you don't use a driver that\MessageBreak
+generates fonts.}%
+    \fi
+    \math@fontsfalse
+    \fontsize{\the\dimen@}\z@
+    \selectfont
+    }
+\def\abbr#1{{\tds@reduced@size \uppercase{#1}}}
+
+% references
+
+\let\xref\relax
+\let\citetitle=\textit
+
+% aliases for LaTeX markup
+
+\let\emphasis=\emph
+
+% environment `legalnotice', part of front matter
+
+\let\legalnotice=\par
+\let\endlegalnotice=\par
+
+% environment `ttdisplay', used to explicate some fact. Basically,
+% it's the alltt environment without parskip and with an additional
+% level of indentation.
+
+\def\ttdisplay{%
+    \begingroup
+        \list{}{%
+            \parsep\z@skip              % no skip before env
+            \parskip\z@skip
+            \relax
+            }%
+        \item\relax
+            \parshape\z@
+            %% code below is copied from alltt.dtx.
+            \leftskip\@totalleftmargin
+            \@tempswafalse
+            \def\par{%
+                \if@tempswa
+                    \leavevmode\null\@@par\penalty\interlinepenalty
+                \else
+                    \@tempswatrue
+                    \ifhmode
+                        \@@par
+                        \penalty\interlinepenalty
+                    \fi
+                \fi
+                }%
+            \obeylines
+            \verbatim@font
+            \let\org@prime~%
+            \@noligs
+            \everymath \expandafter{\the\everymath \let~\org@prime}%
+            \everydisplay \expandafter{\the\everydisplay \let~\org@prime}%
+            \let\org@dospecials\dospecials
+            \g@remfrom@specials{\\}%
+            \g@remfrom@specials{\{}%
+            \g@remfrom@specials{\}}%
+            \let\do\@makeother \dospecials
+            \let\dospecials\org@dospecials
+            \frenchspacing\@vobeyspaces
+            \everypar \expandafter{\the\everypar \unpenalty}%
+            %}
+    }
+\def\endttdisplay{%
+        \endlist
+    \endgroup
+    \vskip -\parskip                    % undo skip after env
+    }
+
+% Code below is from alltt.dtx. I don't understand why it's not part
+% of the LaTeX kernel.
+\def\g@remfrom@specials#1{%
+    \def\@new@specials{}%
+    \def\@remove##1{%
+        \ifx ##1#1%
+        \else
+            \g@addto@macro\@new@specials{\do ##1}%
+        \fi
+        }%
+    \let\do\@remove \dospecials
+    \let\dospecials\@new@specials
+    }
+
+
+
+
+%%% ------------------------------------------------------------
+
+
+%
+%       LOGOS
+%
+
+
+% Some of them are rather document-specific.
+
+\def\texmf{\path|texmf|}
+\def\CTAN:{\replaceable{\abbr{CTAN}:}}
+
+
+% Actually, I should use my logos package for the rest... [-js]
+
+% The AmS definition is from AmS-LaTeX, that's more stable in this
+% document's context than the one from AmS-TeX.
+\def\AmS{%
+    \begingroup
+        \protect\usefont{OMS}{cmsy}{m}{n}%
+        A\kern-.1667em \lower.5ex\hbox{M}\kern-.125em S%
+    \endgroup
+    }
+\def\AMSTeX{\AmS-\TeX}
+
+\def\iniTeX{\texttt{INITEX}\@}
+\def\iniMF{\texttt{INIMF}\@}
+\def\iniMP{\texttt{INIMP}\@}
+
+\def\PS{\textsc{PostScript}}
+
+
+% If we don't use logo fonts, both the Metafont and the MetaPost logo
+% is typeset in the current font, as shown in this comment. The macros
+% `\MF' & `\MP' expand to two \textfont macros, with uppercase
+% syllables as arguments. We check for the syllable `FONT', this has
+% to be typeset in lowercase. All other syllables are capitalized.
+
+\def\tds_logo_fontarg{FONT}
+\DeclareRobustCommand\tds@transfer@logo[1]{%
+    \def\tds_arg{#1}%
+    \ifx \tds_arg\tds_logo_fontarg
+        font%
+    \else
+        \tds_capitalize#1\tds_argend
+    \fi
+    }
+\def\tds_capitalize#1#2\tds_argend{%
+    \uppercase{#1}\lowercase{#2}%
+    }
+
+\tds_mflogo
+
+
+% Use a small caps fake for BibTeX's `ib'. This way we can typeset it
+% in bold face or sans-serif, too. The code is copied from the LaTeX
+% logo definition, from ltlogos.dtx.
+
+\DeclareRobustCommand\tds@smsize{%
+    $\m@th$%                            % force math size calculation
+    \csname S@\f@size\endcsname
+    \fontsize\sf@size\z@
+    \math@fontsfalse \selectfont
+    }
+
+\def\BibTeX{B\kern-.05em{\tds@smsize IB}\kern-.08em\TeX}
+
+
+%%% ============================================================
+
+%
+%       TDS SUMMARIES
+%
+
+% Typeset a figure that shows the TeX directory layout. The layout is
+% input with optical markup:
+%
+%     \begin{tdsSummary}
+%     dir/                    explanation of dir
+%      . subdir/              explanation of subdir
+%      . . subsubdir/         next subdir level
+%      . dir/dir/             more than one dir in one line
+%      . <category>/          explanation of category
+%     \end{tdsSummary}
+%
+% Directories and category names don't have dots.
+
+% We transform that input into a table. The first table column (the
+% directory spec) is terminated by a slash that's followed by white
+% space. Directory names are typeset in monocase. <categories> are
+% tagged with \replaceable. Subdirectory levels are indented by one
+% quad. A quad is placed between columns. The explanation text
+% is typeset in one line.
+
+% As this is a special implementation for a special document, these
+% design decisions are hardwired, no protected interface is available.
+% Design changes will be realized by changes to the macro code.
+
+
+% The environment is realized as a trivlist to behave correctly in list
+% environments. I don't use a tabular environment, since I don't know
+% exactly how the first column is tokenized. Instead a halign is used.
+% IMO it does not matter, as tdsSummary does not use table markup
+% anyhow. If somebody wants to use longer explanations and if they must
+% be broken then, I have to use one of the tabulars of the tools bundle.
+
+% The first column (the directory names) is typeset in typewriter type. The
+% font chosen hereby must have the underscore at its ASCII position. If
+% that is not the case, one has to generalize \tds_dir_tags below.
+% Namely, this macro sets up the special lexical convention for this
+% column. As TeX will look at the first token of the column to check for
+% the table end, \cr, or \omit before \tds_dir_tags is evaluated, the
+% redefinition of the lexical analysis will not have happened for that
+% token. So we have to check this token specially if it's one of the
+% special optical markup chars.
+
+% After we started the trivlist, we need to supply the item (as this
+% macro really adds the vertical space). But it does not actually
+% start an item, it sets up the everypar register to do so. We fake
+% the item start as we don't want to go in horizontal mode, \halign
+% needs to be evaluated in vertical mode.
+%
+% \par is not evaluated by \endtrivlist and \end, so we don't need
+% another group around its redefinition.
+
+\def\tdsSummary{%
+    \trivlist \item\relax
+    \vskip\parskip
+    \global\@inlabelfalse \global\@newlistfalse \global\everypar{}%
+    \tabskip 0pt
+    \let\par\crcr  \obeylines       % can't use \obeycr, redefined by LaTeX
+    % redefine \obeylines to do nothing; url.sty v3.0 calls it, and the
+    % ^^M character therein causes a `Missing \endgroup inserted' error
+    % at a \path|...| within a tdsSummary, if it's already defined as \par.
+    \let\obeylines=\relax
+    \halign\bgroup
+        \ttfamily \tds_dir_tags \tds_first_token ##\unskip\hfil &%
+            \quad ##\unskip\hfil \cr
+    }
+\def\endtdsSummary{%
+        \crcr
+        \egroup
+    \endtrivlist
+    }
+
+
+% Our special lexical conventions are: `.' denotes the next directory
+% level, `<...>' denotes a directory category, and `/' is a column
+% separator if it is followed by space or tab, a typeset slash
+% otherwise. Underscores don't have any special meaning.
+
+\begingroup
+    \catcode`\.=\CatActive
+    \catcode`\<=\CatActive
+    \catcode`\/=\CatActive
+    \catcode`\:=\CatActive
+    \gdef\tds_dir_tags{%
+        \catcode`\.=\CatActive  \let.=\tds_next_dir_level
+        \catcode`\<=\CatActive  \let<=\tds_dir_category
+        \catcode`\/=\CatActive  \let/=\tds_slash
+        \catcode`\:=\CatActive  \let:=\tds_colon
+        \catcode`\_=\CatOther
+        \tt
+        }
+\endgroup
+
+% There are spaces between the dots, ignore them.
+
+\def\tds_next_dir_level{\quad \ignorespaces}
+\def\tds_dir_category#1>{\replaceable{#1}}
+
+\chardef\tds_dir_sep=`\/                % typeset a directory separator
+
+% The slash has to check the stuff behind. If it's a space or a tab,
+% \next is bound to the action `blank-space' (the binding of all
+% '(space . #\Space) tokens). A tab is usually tokenized to the same
+% token, but we care for redefinitions below.
+% 
+\def\tds_slash{%
+    \futurelet\next \tds_check_dir_end
+    }
+
+% For colons in the examples.
+% 
+\def\tds_colon{:&}
+
+% We need two control sequencess that are bound to the actions currently
+% bound to '(space . #\Space) and (tex:parse "\t"). A direct \let
+% evaluation is difficult as the lexical analysis collapses subsequent
+% spaces to one token. But we need one space token behind the equal
+% sign, to be able to \let our cseq to the next space token. The first
+% token is stored in the replacement list of a macro, the second token
+% comes as its argument.
+
+\def\tds_let#1#2{\let#1= #2}
+\tds_let\tds_space{ }
+\tds_let\tds_tab{^^I}
+
+\def\TdsColSep{/&}                      % use trailing slashes for dir names
+
+\def\tds_check_dir_end{%
+    \ifx \next\tds_space
+        \let\next\TdsColSep
+      \else
+        \ifx \next\tds_tab
+            \let\next\TdsColSep
+          \else
+            \let\next\tds_dir_sep
+        \fi
+    \fi
+    \next
+    }
+
+
+% We're almost finished with the tdsSummary setup. The stuff above is
+% not used for the first column token, as it's already tokenized when
+% the catcode changes take effect. So let's check and remap this token
+% by hand. Actually, I'm sloppy here; I assume that `/' won't be a
+% used as a directory name and that no directory name starts with an
+% underscore. But then, I know that this won't happen in TDS... :-)
+
+\def\tds_first_token{%
+    \futurelet\next \tds_check_special
+    }
+\def\tds_check_special{%
+    \ifx \next.%
+        \def\next{\afterassignment\tds_next_dir_level \let\next}%
+      \else
+        \ifx \next<%
+            \def\next{\afterassignment\tds_dir_category \let\next}%
+          \else
+            \let\next\relax
+        \fi
+    \fi
+    \next
+    }
+
+
+
+%%% ============================================================
+
+%
+%       LAYOUT
+%
+
+
+% text area size
+
+% We use the same height as article's default, but increase the width.
+
+\textwidth=35pc
+\oddsidemargin = \paperwidth
+  \advance\oddsidemargin by -\textwidth
+  \divide\oddsidemargin by 2
+\evensidemargin = \oddsidemargin
+\hoffset = -1in
+
+
+% spacing
+
+\parindent=0pt                          % no paragraph indentation
+\emergencystretch=2em                   % fewer overfull hboxes, only a memo
+
+\parskip=1ex plus 1ex minus .5ex        % between paragraphs; if you change it,
+                                        % change the spacing in section headers
+                                        % below, too!
+
+% Our spacing for lists is very simplistic, but uniform: We use (almost)
+% parskip everywhere, and don't distinguish vertical spacing for
+% different list levels. Actually, the latter is the thing we might want
+% to introduce later again.
+
+\labelsep=1.1em                         % increase distance between item & text
+\topsep=0pt                             % no extra skip above list in paragraph
+\partopsep=0pt                          % no extra skip above list starting par.
+\itemsep=0pt                            % no extra space between items
+\parsep=.9\parskip                      % between paragraphs in items
+
+\def\@listI{%
+    \leftmargin\leftmargini
+    }
+\let\@listi\@listI
+\@listi
+
+\def\@listii{%
+    \leftmargin\leftmarginii
+    \labelwidth\leftmarginii  \advance \labelwidth-\labelsep
+    }
+
+\def\@listiii{%
+    \leftmargin\leftmarginiii
+    \labelwidth\leftmarginiii  \advance \labelwidth-\labelsep
+    }
+
+
+% Like itemize, but squeeze the items.
+
+\newenvironment{itemize-squeeze}
+    {%
+        \parsep\z@skip
+        \itemize
+    }{%
+        \enditemize
+    }
+
+% Ditto, for description.
+
+\newenvironment{description-squeeze}
+    {%
+        \parsep\z@skip
+        \description
+    }{%
+        \enddescription
+    }
+
+
+% Redefine section headers, different spacing and other fonts.
+
+\newskip\TdsPreSubSectionSkip
+        \TdsPreSubSectionSkip = 2.5ex plus 0.5ex minus 0.2ex
+
+\def\section{%
+    \@startsection{section}{1}%         % name and level
+        {\z@}%                          % indentation
+        {-3ex plus-.75ex minus-.2ex}%   % skip above and don't indent next par
+        {1.5ex plus.2ex}%               % skip below
+        {\reset@font \Large \sffamily}% % type
+    }
+\def\subsection{%
+    \@startsection{subsection}{2}%      % name and level
+        {\z@}%                          % indentation
+        {-\TdsPreSubSectionSkip}%       % skip above and don't indent next par
+        \parskip                        % skip below
+        {\reset@font \large \sffamily}% % type
+    }
+\def\subsubsection{%
+    \@startsection{subsubsection}{3}%   % name and level
+        {\z@}%                          % indentation
+        {-\TdsPreSubSectionSkip}%       % skip above and don't indent next par
+        \parskip                        % skip below
+        {\reset@font \normalsize \sffamily}% % type
+    }
+\def\paragraph{%
+    \@startsection{paragraph}{4}%       % name and level
+        {\z@}%                          % indentation
+        \TdsPreSubSectionSkip           % skip above and indent next par
+        {-1.5em}%                       % skip after, run in text
+        {\reset@font \normalsize \scshape}% % type
+    }
+
+
+% Table of contents
+
+\setcounter{tocdepth}{2}                % only sections on first two levels
+
+% Less space between TOC entries, discard the parskip. For that, we
+% have to redefine \@starttoc, since no hook is available.
+\let\tds_orig_starttoc=\@starttoc
+\def\@starttoc#1{%
+    \begingroup
+        \parskip\z@skip
+        \tds_orig_starttoc{#1}%
+    \endgroup
+    }
+
+% Section TOC entries in sans serif, and less space above. The code
+% below is copied from the article view on classes.dtx, I have changed
+% space and font. But let's first assure that we shouldn't use a newer
+% version of this code.
+\CheckCommand*\l@section[2]{%
+  \ifnum \c@tocdepth >\z@
+    \addpenalty\@secpenalty
+    \addvspace{1.0em \@plus\p@}%
+    \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}
+\def\l@section#1#2{%
+    \ifnum \c@tocdepth >\z@
+        \addpenalty\@secpenalty
+        \addvspace{.75ex \@plus\p@ \@minus\p@}% % was:  1em plus 1pt
+        \setlength\@tempdima{1.5em}%
+        \begingroup
+            \parindent \z@
+            \rightskip \@pnumwidth
+            \parfillskip -\@pnumwidth
+            \leavevmode \sffamily       % was: \bfseries
+            \advance\leftskip\@tempdima
+            \hskip -\leftskip
+            #1\nobreak \hfil \nobreak \hbox to\@pnumwidth{\hss #2}%
+            \par
+        \endgroup
+    \fi}
+
+
+% Not so spacey a title, please.
+
+\def\@maketitle{%
+  \null
+  \kern-90pt \relax \kern0pt
+  \begin{center}%
+    {\LARGE \@title \par}%
+    %\vskip 1.5em%
+    {\large
+      \lineskip .5em%
+      \begin{tabular}[t]{c}%
+        \@author
+      \end{tabular}\par}%
+    \vskip 1em%
+    {\large  version \the\tdsVersion \quad \@date}%
+  \end{center}%
+  \par
+  \vskip 1.5em}
+
+
+% Make labels in the description environment come out in the
+% requested type rather than bold.
+
+\def\descriptionlabel#1{\hspace\labelsep #1}
+
+
+% Headline & footline
+
+\pagestyle{fancy}
+
+\lhead{}
+\chead{%
+    \ifTdsDraft draft \fi               % <-- space!
+    TDS version \the\tdsVersion
+    }
+\rhead{}
+\renewcommand{\headrulewidth}{0.4pt}
+
+\lfoot{}
+\cfoot{\thepage}
+\rfoot{}
+\renewcommand{\footrulewidth}{0pt}
+
+
+
+%%% ============================================================
+
+\catcode`\_=\CatUsCode
+
+\endinput
+
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%
+% $Log: tdsguide.cls,v $
+% Revision 1.19  2004/03/28 14:21:10  karl
+% (\tdsSummary): \let\obeylines=\relax after we set
+% it, so url.sty v3.0's usage of \obeylines does not
+% cause errors.
+%
+% Revision 1.18  1998/01/26 21:26:10  karl
+% (\TeXinfo): Remove unused and incorrect name.
+% (\parsep): Decrease slightly.
+% (\l@section): Decrease section spacing for toc slightly.
+% (\@maketitle): Remove word `draft'.
+%
+% Revision 1.17  1997/02/07 20:47:16  karl
+% Fix : in tdsSummary, more doc.
+%
+% Revision 1.16  1996/11/16 14:23:58  karl
+% fancyhdr requires different commands.
+%
+% Revision 1.13  1995/11/21  18:57:35  schrod
+%     Add description-squeeze environment.
+%
+% Revision 1.12  1995/11/14  18:33:18  schrod
+%     Drop draft hint in legalnotice environment, make title more
+% squeezed. Changes by Karl, to make title & toc fit on one page.
+%
+% Revision 1.11  1995/11/14  12:36:54  schrod
+%     Use url.sty instead of path.sty. (On request of Karl, better input
+% syntax and different line breaks [0.103].)
+%     Rename environment explicate to ttdisplay. (Proposal of Karl.)
+%
+% Revision 1.10  1995/11/11  16:29:01  schrod
+%     Identify version of class in log file.
+%     Change layout of table of contents. Implementation of a discussion
+% between Karl Berry and myself.
+%
+% Revision 1.9  1995/11/11  15:43:34  schrod
+%     Replace alltt environment by explicate environment. Change
+% requested by Karl at 09 Nov 95.
+%
+% Revision 1.8  1995/11/02  10:52:29  schrod
+%     Add option nomflogo, mflogo is default now.
+%     Don't need provision for slanted typewriter type any more,
+% replacable texts are set in italics now.
+%     Add logos \texmf and \CTAN:. [kb]
+%     Set margins in addition to \textwidth. It's a bit wider, too. [kb]
+%     Wider distance between item label and item text. [kb]
+%     New environment itemize-squeeze, without space between items. [kb]
+%
+% Revision 1.7  1995/05/18  09:06:39  schrod
+%     Don't parse arguments unnecessarily early, one might change
+% catcodes in them.
+%     Use \tds_tt to switch to typewriter, also typesets backslashs and
+% underscores [kb].
+%     Increase width to 33pc [kb].
+%
+% Revision 1.6  1995/05/12  23:19:07  schrod
+%     \f@size may be a fraction, so use dimension register to compute
+% the reduced size for abbreviations [dc].
+%     In summary tables, terminate the directory names with slashes [kb, nw].
+%
+% Revision 1.5  1995/05/09  01:46:24  schrod
+%     Typeset abbreviation one point smaller than surrounding font [uv,
+% kb, bb], use always uppercase letters for them. Rename the tag from
+% \acronym to \abbr [kb, nw].
+%
+% Revision 1.4  1995/05/09  00:39:57  schrod
+%     Repair vertical spacing around tdsSummary environment.
+%
+% Revision 1.3  1995/05/08  17:14:52  schrod
+%     For TDS 0.72 Norm changed the document to use \abbr (argument with
+% lowercase letters) instead of \acronym. It's not looking better, of
+% course; small caps is not really a good font for abbreviations. This
+% revision just tracks his change, I'll look later if I can improve the
+% rendering.
+%
+% Revision 1.2  1995/05/07  18:22:53  schrod
+%     In environment tdsSummary: Next directory level indented by one
+% quad, without dots for indentation [kb, !uv, js].
+%     Renamed Draft flag to TdsDraft, to keep namespace clean.
+%     Headline now features a centered short title [kb, uv, nw]. It's
+% still ruled.
+%     \replaceable used spurious \selectfont [uv]. \dir & \ext are not
+% used [uv].
+%     Subsubsections are also numbered and not indented [uv]. But they
+% are still not added to the table of contents. Actually, we have only
+% _one_ subsubsection...
+%     Set erroneously counter `secnumdepth' when I wanted fewer section
+% headings in the table of contents. That's controlled by counter
+% `tocdepth' [uv].
+%     Inherit tdsguide from article class, not from ltxguide. The tags
+% of the latter class are not appropriate and we define our layout
+% ourselves.
+%
+
+%
+% pre-CVS Log:
+%
+% 19 Apr 95 js  Made a LaTeX2e class.
+%               Use mflogo option to select MF/MP logo typesetting,
+%               support configuration file.
+% 1994-1995 nw  Initial revision.
+
+
+
+%%%------------------------------------------------------------
+
+% mode: LaTeX
+% Local Variables:
+% TeX-brace-indent-level: 4
+% indent-tabs-mode: t
+% TeX-auto-untabify: nil
+% TeX-auto-regexp-list: LaTeX-auto-regexp-list
+% page-delimiter: "^%%%"
+% End: