diff options
| author | Manuel Pégourié-Gonnard <mpg@elzevir.fr> | 2008-06-21 13:58:54 +0000 |
|---|---|---|
| committer | Manuel Pégourié-Gonnard <mpg@elzevir.fr> | 2008-06-21 13:58:54 +0000 |
| commit | 4683bcefcc8e380dda5f46ff09833a4b9b7f7804 (patch) | |
| tree | 114f6e4f828c88b59884c61813315b67314dfc54 /Master/texmf-doc | |
| parent | baafafa261f8d350aaed51a28fb3c8627aa78237 (diff) | |
FAQ-en v3.18
git-svn-id: svn://tug.org/texlive/trunk@8900 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc')
148 files changed, 2958 insertions, 1578 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.18 b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.18 new file mode 100644 index 00000000000..75f90d12bc6 --- /dev/null +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/ChangeLog b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog index 17b958dc5a0..8d4f3747781 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/ChangeLog +++ b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog @@ -1,3 +1,452 @@ +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE b/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE index d9a8ab7e600..961f243386a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE +++ b/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE @@ -4,4 +4,3 @@ missing source code. You can find these files on CTAN. If questions or concerns, email tex-live.org. letterfaq.pdf - newfaq.pdf diff --git a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex index 91d2f5b4fb4..927736d1e15 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex @@ -65,6 +65,7 @@ \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} @@ -204,7 +205,7 @@ \CTANdirectory{combine}{macros/latex/contrib/combine} \CTANdirectory{comm}{tools/macutils/comm} \CTANdirectory{comment}{macros/latex/contrib/comment} -\CTANdirectory{committee}{fonts/cm/utilityfonts/committee} +\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} @@ -220,6 +221,7 @@ %[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} @@ -332,11 +334,12 @@ \CTANdirectory*{epstopdf}{support/epstopdf} \CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox} \CTANdirectory{ergotex}{systems/msdos/ergotex} -\CTANdirectory{errata}{systems/knuth/errata} +\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} @@ -375,6 +378,7 @@ \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} @@ -521,7 +525,7 @@ \CTANdirectory{levy}{fonts/greek/levy} \CTANdirectory{lextex}{macros/plain/contrib/lextex} \CTANdirectory{lgc}{info/examples/lgc} -\CTANdirectory{lgrind}{nonfree/support/lgrind} +\CTANdirectory{lgrind}{support/lgrind} \CTANdirectory{lharc}{tools/lharc} \CTANdirectory{lineno}{macros/latex/contrib/lineno} \CTANdirectory{listbib}{macros/latex/contrib/listbib} @@ -580,7 +584,7 @@ \CTANdirectory{mflogo}{macros/latex/contrib/mflogo} \CTANdirectory{mfnfss}{macros/latex/contrib/mfnfss} \CTANdirectory{mfpic}{graphics/mfpic} -\CTANdirectory{mfware}{systems/knuth/mfware} +\CTANdirectory{mfware}{systems/knuth/dist/mfware} \CTANdirectory{mh}{macros/latex/contrib/mh} \CTANdirectory{microtype}{macros/latex/contrib/microtype} \CTANdirectory{midi2tex}{support/midi2tex} @@ -674,6 +678,7 @@ \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} @@ -681,6 +686,7 @@ \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} @@ -694,6 +700,7 @@ \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} @@ -708,7 +715,6 @@ \CTANdirectory{ps-type3}{fonts/cm/ps-type3} \CTANdirectory{ps2mf}{fonts/utilities/ps2mf} \CTANdirectory{ps2pk}{fonts/utilities/ps2pk} -\CTANdirectory{ps4mf}{systems/msdos/ps4mf} \CTANdirectory{psbook}{systems/msdos/dviware/psbook} \CTANdirectory{psbox}{macros/generic/psbox} \CTANdirectory{pseudocode}{macros/latex/contrib/pseudocode} @@ -831,13 +837,14 @@ \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}{systems/knuth/tex--xet} +\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} @@ -880,7 +887,7 @@ \CTANdirectory{textures}{systems/mac/textures} \CTANdirectory{textures_figs}{systems/mac/textures_figs} \CTANdirectory{texutils}{systems/atari/texutils} -\CTANdirectory{texware}{systems/knuth/texware} +\CTANdirectory{texware}{systems/knuth/dist/texware} \CTANdirectory{tgrind}{support/tgrind} \CTANdirectory{thai}{fonts/thai} \CTANdirectory{tib}{biblio/tib} @@ -945,6 +952,7 @@ \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} @@ -970,11 +978,12 @@ \CTANdirectory{wasy2}{fonts/wasy2} \CTANdirectory{wasysym}{macros/latex/contrib/wasysym} \CTANdirectory{wd2latex}{support/wd2latex} -\CTANdirectory{web}{systems/knuth/web} +\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} @@ -999,6 +1008,7 @@ \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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/faq.sty b/Master/texmf-doc/doc/english/FAQ-en/faq.sty index f855d6af3d8..e9acef465a4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faq.sty +++ b/Master/texmf-doc/doc/english/FAQ-en/faq.sty @@ -154,7 +154,7 @@ \newcommand\AMSLaTeX{AMS\LaTeX} \newcommand\BibTeX{Bib\TeX} \newcommand\PiCTeX{PiC\TeX} -\newcommand\texlive{\TeX-live} +\newcommand\texlive{\TeX{} Live} % % ifthenelse for the undefined references \RequirePackage{ifthen} @@ -203,6 +203,7 @@ \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} @@ -810,13 +811,13 @@ \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}% -% \addtocontents{lab}{\protect\QuestionLabel{#1}{#2}{\thepage}}% \fi } \newcommand\qu@stion{\@startsection{question}% @@ -835,6 +836,30 @@ \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}% @@ -1045,12 +1070,19 @@ \futurelet\@let@token\@cmdinvoke } \def\@cmdinvoke{\ifx\@let@token\bgroup - \expandafter\@cmdinvoke@lbrace + \let\@tempb\@cmdinvoke@lbrace \else \ifx\@let@token[% ] - \expandafter\expandafter\expandafter\@cmdinvoke@lbrack + \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}}% @@ -1060,6 +1092,10 @@ \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}}} diff --git a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex index 68efea3ebb0..1b35a314993 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.17} \def\faqfiledate{2007-11-05} +\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 @@ -102,8 +102,9 @@ Giuseppe Bilotta, Charles Cameron, Damian Cugley, Michael Dewey, -Michael Downes, % (RIP) on (ams\)maths stuff +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 @@ -111,14 +112,17 @@ 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 @@ -126,6 +130,7 @@ 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, @@ -196,12 +201,12 @@ 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 Plain \TeX{}; Plain \TeX{} is +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 Plain \TeX{}. +they're programming in \plaintex{}. \Question[Q-TeXpronounce]{How should I pronounce ``\TeX{}''?} @@ -301,7 +306,7 @@ 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 principe be distributed as a working version. (In practice, any +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. @@ -314,11 +319,11 @@ for real world problems. 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 logfiles. These items should not be of general concern, + 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 implementators could + 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 @@ -342,7 +347,7 @@ for real world problems. 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. +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} @@ -374,7 +379,7 @@ 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{} system (for +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). @@ -483,10 +488,10 @@ 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 Plain \TeX{} or \LaTeX{}?} +\Question[Q-plainvltx]{Should I use \plaintex{} or \LaTeX{}?} There's no straightforward answer to this question. Many people swear -by Plain \TeX{}, and produce highly respectable documents using it +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 @@ -503,14 +508,14 @@ 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 Plain \TeX{}?} +\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.) -Plain \TeX{} is also a program written in the programming language +\plaintex{} is also a program written in the programming language \TeX{}. Both exist because writing your documents in `raw' \TeX{} would @@ -518,21 +523,15 @@ 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 Plain \TeX{}. Many documents -designed for Plain \TeX{} will work with \LaTeX{} with no more than +\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 -Plain \TeX{}. As a result, the mapping from \LaTeX{} to Plain \TeX{} +\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 -\begin{wideversion} - \Qref{translating to Plain \TeX{}}{Q-LaTeXtoPlain}. -\end{wideversion} -\begin{narrowversion} - translating to Plain \TeX{} (\Qref{}{Q-LaTeXtoPlain}). -\end{narrowversion} +answer about \Qref*{translating to \plaintex{}}{Q-LaTeXtoPlain}. \Question[Q-context]{What is \CONTeXT{}?} @@ -591,7 +590,7 @@ prodigious energy. Support is available via a % ! line break \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 Plain \TeX{}, and provides many +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 @@ -616,7 +615,7 @@ its users to use \AMSLaTeX{} instead. \Question[Q-eplain]{What is \Eplain{}?} The \href{http://tug.org/eplain}{\Eplain{}} -macro package expands on and extends the definitions in Plain \TeX{}. +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 @@ -644,12 +643,12 @@ 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 Plain \TeX{} +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 Plain \TeX{} ``loader'' for some of the packages, it is not a -trivial job to pass options to those packages under Plain \TeX{}, and +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 @@ -805,7 +804,7 @@ file, and complete \TeX{} systems are pretty large. \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 anciliary programs. In short, +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 @@ -970,7 +969,7 @@ other books covering \TeX{}: (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 Plain \TeX{} Primer]by Malcolm Clark (Oxford University +\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 @@ -1088,7 +1087,7 @@ maintenance) is: 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 |sourceforge| and on \acro{CTAN}, +available via \texttt{sourceforge} and on \acro{CTAN}, and we list it under ``\Qref*{online books}{Q-ol-books}''. @@ -1134,7 +1133,7 @@ a more interesting overall view of types in general and some of their history. (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 Richar A.~Firmage +\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}) @@ -1190,8 +1189,8 @@ 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{} usergroup Gutenberg and the Czech/Slovak -usergroup CS-TUG have published translations of this \acro{FAQ}, with +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 @@ -1245,7 +1244,7 @@ distributions contain a wide range of supporting material. The ``\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 directoris now include documentation, so it's +\acro{CTAN} package directories now include documentation, so it's often worth looking at the catalogue entry for a package you're considering using. @@ -1347,7 +1346,7 @@ application of your own common sense. \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 Plain \TeX{}'', or ``I + 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 @@ -1383,7 +1382,7 @@ 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 occurrs. (It may prove difficult to find the actual +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} @@ -1458,7 +1457,7 @@ 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*{Plain \TeX{}}{Q-man-tex} and \Qref*{\LaTeX{}}{Q-man-latex}. +\Qref*{\plaintex{}}{Q-man-tex} and \Qref*{\LaTeX{}}{Q-man-latex}. Next comes a selection of \Qref*{``specialised'' \AllTeX{} tutorials}{Q-tutbitslatex}, @@ -1478,9 +1477,9 @@ Finally, we have a set of links to of some ``\Qref*{books}{Q-ol-books}'' that were once published conventionally, but are now available on-line. -\Question[Q-man-tex]{Online introductions: Plain \TeX{}} +\Question[Q-man-tex]{Online introductions: \plaintex{}} -Michael Doob's splendid `Gentle Introduction' to Plain \TeX{} +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{}', @@ -1528,7 +1527,7 @@ Chris Harrison's % ! line break presents basic \LaTeX{} with useful hints for extensions Nicola Talbot's % ! line break -\href{http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/novices.html}{\LaTeX{} for complete novices} +\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}, @@ -1675,7 +1674,7 @@ 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 Plain \TeX{} as +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 @@ -1752,8 +1751,8 @@ 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} general documentation -licence, and it is available from \acro{CTAN}. +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 @@ -1794,8 +1793,9 @@ 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 -even occasionally generates documentation itself, you will more often -than not find documentation that way. +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 @@ -2073,22 +2073,15 @@ and \Qref[]{Using \PS{} fonts with \TeX{}}{Q-usepsfont}. \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 -\begin{narrowversion} -(\acro{TDS}~--- \Qref{}{Q-tds}), -\end{narrowversion} -\begin{wideversion} -(see \Qref{\acro{TDS}}{Q-tds}), -\end{wideversion} -which has provision for all this variety. +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?} @@ -2102,7 +2095,7 @@ magnifications of `its' font, so that there are (typically) fewer 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 needs to know about the glyphs that each +\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} @@ -2306,9 +2299,7 @@ from \acro{CTAN} (which comes with skeleton \extension{dtx} and \extension{ins} files). Composition of \extension{dtx} files is supported in \ProgName{emacs} by -Matt Swift's \ProgName{swiftex} system: it provides a -\environment{doc-tex} mode which treats \extension{dtx} files rather -better than \Qref*{\acro{AUC}-\TeX{}}{Q-editors} manages. +\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 @@ -2326,8 +2317,13 @@ 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 \latexhtml{\MF{}}{\Qref{\MF{}}{Q-MF}} and % beware line break -\latexhtml{\MP{} (\Qref[see questions]{}{Q-MF} and\Qref[]{}{Q-MP})}{\Qref{\MP{}}{Q-MP}}, +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} @@ -2336,7 +2332,6 @@ thus permitting documented distribution of bundles containing code for \item[docstrip.tex]Part of the \LaTeX{} distribution \item[DTX tutorial]\CTANref{dtxtut} \item[makedtx]\CTANref{makedtx} -\item[swiftex.el]\CTANref{swiftex} \end{ctanrefs} \Question[Q-whatenc]{What are encodings?} @@ -2504,7 +2499,7 @@ 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 |texmf| as the name of the root directory +\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 @@ -2552,7 +2547,7 @@ be used as figures in this way. The important features 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 |showpage| +\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 @@ -2603,7 +2598,7 @@ 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 -inreasingly unattractive, in recent years. If you have a \acro{PDF} +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{}% @@ -2772,6 +2767,24 @@ 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 @@ -2936,7 +2949,7 @@ 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}{\acro{USA}} \acro{CTAN}s offer a +\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); @@ -2997,7 +3010,7 @@ 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 +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. @@ -3039,7 +3052,7 @@ 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. -Moew details of the collection are available from its own +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. @@ -3342,7 +3355,10 @@ personal selection: \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. + 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. @@ -3351,9 +3367,10 @@ personal selection: 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{}. + works well with Oz\TeX{}. From release 2.2.0 (at least), Textures + works with MacOS~X. - For MacOS~X users, the tool of choice appears to be + 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 @@ -3685,7 +3702,7 @@ 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 +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} @@ -3702,7 +3719,7 @@ picture-elements. Its output is code for the \LaTeX{} Optionally, it can be set to include lines at all angles using the em\TeX{} driver-family \htmlignore -|\special|s (\Qref{}{Q-specials}). +\csx{special}s (\Qref{}{Q-specials}). \endhtmlignore \begin{htmlversion} \Qref{\csx{special}s}{Q-specials}. @@ -3743,7 +3760,7 @@ version of \ProgName{ispell}. \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. + dictionaries (under subdirectory \File{dict/}) that you need. \item[excalibur]\CTANref{Excalibur} \item[ispell]\CTANref{ispell} \item[jspell]\CTANref{jspell} @@ -3838,7 +3855,7 @@ 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, |awk|, and \acro{C} +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}, @@ -3857,7 +3874,7 @@ translates Scheme\acro{WEB} into \LaTeX{} source or Scheme source. 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 Plain \TeX{} macro files, using +\ProgName{Tweb} is a \acro{WEB} for \plaintex{} macro files, using \ProgName{noweb}. \begin{ctanrefs} \item[aplweb]\CTANref{aplweb} @@ -4056,13 +4073,13 @@ For today, possible packages are: 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 Plain \TeX{}, and uses the font/table technique for representing + 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 Plain \TeX{}, by processing a \acro{DVI} file; it uses + \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 @@ -4116,25 +4133,11 @@ The World Wide Web Consortium maintains a list of ``filters'' to % of Lawrence Berkeley Laboratory.% % \checked{RF}{1994/11/18} -\item[WordPerfect] \ProgName{wp2latex} - has recently been much improved, and is now - available either for \MSDOS{} or for Unix systems, thanks to its - current maintainer Jaroslav Fojtik. -\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. -\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[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 - convertor to \LaTeX{} by Erwin Wechtl, called \ProgName{rtf2latex}. + 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. @@ -4152,18 +4155,34 @@ The World Wide Web Consortium maintains a list of ``filters'' to \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. - Another, unlikely, intermediate form is \acro{PDF}: Acrobat Reader + 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 @@ -4264,31 +4283,31 @@ to map to its standard Unicode representation. \item[xpdf]Browse \CTANref{xpdf} \end{ctanrefs} -\Question[Q-LaTeXtoPlain]{Translating \LaTeX{} to Plain \TeX{}} +\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 Plain \TeX{}}{Q-LaTeXandPlain}'' +``\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 Plain \TeX{} is likely to amount to carefully +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 Plain \TeX{}, which the document uses. +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 Plain \TeX{}. However, while +\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 Plain~\TeX{} is designed to +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{`Plain \TeX{}'}}{Plain \TeX{}} graphics]% +\item[\latexhtml{\textrm{`\plaintex{}'}}{\plaintex{}} graphics]% \CTANref{graphics-plain} \end{ctanrefs} @@ -4297,6 +4316,7 @@ offer.) \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 @@ -4306,7 +4326,7 @@ decided what it is that you want to install: \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's probably a good idea to % ! line break +\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}; @@ -4317,10 +4337,10 @@ decided what it is that you want to install: \Question[Q-install-find]{Finding packages to install} -How did you find about the package? +How did you learn about the package? -If you learned about your package in these \acro{FAQ}s, you should -already have a link to the file: +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} @@ -4336,22 +4356,26 @@ 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. -Remember that you may want \File{foo.sty} but that file is distributed -in a \LaTeX{} documented source file \File{foo.dtx}; it's usually best -to search just for \emph{foo}~--- \File{foo.sty} won't be visible -anywhere on the archive or in the catalogue. - Packages come in a variety of different styles of distribution; the -very simplest will offer just \File{package.sty}~--- in this case, -just download the file and % ! line break +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}. -However, most packages occupy their own directory on the archive; in -this case, you should download the whole directory +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. -Having acquired the package distribution, see % ! line break -``\Qref*{unpacking \LaTeX{} packages}{Q-install-unpack}'' for your -next step. +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} @@ -4365,14 +4389,15 @@ 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 \File{.dtx} files, but -fewer (often only one) \File{.ins} files (\LaTeX{} itself comes -looking like this). The way to go, in this case is simply to process -the \File{.ins} file(s) one by one. +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 \File{.dtx} files are -``self-extracting''~--- they do without a \File{.ins} file, and once +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 @@ -4402,8 +4427,9 @@ 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). Both types of file are processed with -special \ProgName{makeindex} style files; appropriate commands are: +(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 @@ -4412,15 +4438,17 @@ makeindex -s gglo -o package.gls package.glo \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. +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 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 alternatives. -Such files are treated in the same way as any ``ordinary'' \LaTeX{} -file. +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~--- @@ -4455,11 +4483,12 @@ and click on \texttt{Refresh FNDB}. The job may also be done in a command window, using the command: \begin{quote} \begin{verbatim} -initexmf -u +initexmf --update-fndb \end{verbatim} \end{quote} -See the \miktex{} documentation for further details about -\texttt{initexmf}. +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}~--- @@ -4470,29 +4499,25 @@ 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. The root directory -will be named something like: -\begin{quote} -\begin{verbatim} -teTeX or TeX-live: /usr/share/texmf-local/ or - /usr/local/share/texmf/ -MiKTeX: c:\localtexmf\ -\end{verbatim} -\end{quote} -You can ask a Unix-alike system (such as te\TeX{} or \texlive{}) where -it believes a local tree should be: +``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: +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} -on the workstation the author is using today. In a \miktex{} installation, the location will in fact typically be something you specified yourself when you installed \miktex{} in the @@ -4505,25 +4530,34 @@ first place, but you may find you need to create one. The \miktex{} 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 (say -``\texttt{Local TeX Files}''), 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 -\texttt{C:\textbackslash{}Local TeX Files}, which is good if you +``\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 where you will need to create a directory -somewhere \emph{you}, rather than the system, control). - -There are circumstances when you might not wish to do this: +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 have no privilege to write to the local tree, you are - again unlikely to be able to put the package anywhere other than - your home tree; or \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 @@ -4552,26 +4586,18 @@ installation. \Question[Q-install-where]{Where to install packages} -Where precisely you put files that you have downloaded depends on -what \TeX{} distribution you have. We will assume that you have one -of the modern \acro{TDS}-compliant distributions, and discuss the -general rules that you should follow. - -First, you must decide which tree to put your files into; this isn't -entirely trivial, and is discussed in % ! line break -``\Qref*{choosing a \acro{TDS} tree}{Q-what-TDS}''. - -We'll assume from here on, that you've decided on a directory tree, -and we will write \texttt{\$TEXMF} for it, whatever it is for your -system. +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/latex/<package>/ -.dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/ +.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>/ @@ -4593,17 +4619,31 @@ v1.1 layouts): (Map and encoding files went to directories under \File{$TEXMF/dvips/}, in earlier distributions.) -In the lists above, \meta{package}, \meta{font} and \meta{supplier} depend -upon what's appropriate for the individual file~--- 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; typically, it's the name of a -program 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. Examples are -\extension{sto} and \extension{clo} for package and class options, -\extension{cfg} for configuration information, and so on. +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 @@ -4614,13 +4654,11 @@ The font ``supplier'' \emph{public} is a sort of hold-all for fonts, \emph{public}'s directory holds fonts designed by others (originally, but no longer exclusively, in \MF{}). -Some packages have configuration files (commonly with file suffix -\extension{cfg}), and occasionally other run-time files. The package -documentation \emph{should} mention these things, but sometimes -doesn't. An exception is the \extension{drv} file, used by some -packages as part of the documentation building process; this is -usually part of the package documentation process, and should not be -installed. +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} @@ -4642,24 +4680,54 @@ 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-miktex]{Installing \miktex{} ``known packages''} +\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{} 2.1 (and later) maintains a database of packages it ``knows about'', +\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. +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 +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{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}'', +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 @@ -4675,16 +4743,53 @@ mpm --install=<package> (which of course assumes you know the name by which \miktex{} refers to your package). -If \miktex{} \emph{doesn't} know about the package you're interested -in, you have to use the \Qref*{long-winded procedure}{Q-installthings} -outlined above. +\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}'' -If necessary, repeat to select other packages, and then press -``\texttt{OK}''; \miktex{} tells you how many packages you have -selected~--- if you're happy, press ``\texttt{OK}'' again. -\miktex{} will go off, download the package (as a -\extension{cab} file), if necessary, install the files of the package, and then -refresh the filename database so that the files will be found. +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} @@ -4920,7 +5025,7 @@ 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, do install them, too, since they +\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 @@ -4960,8 +5065,9 @@ All these fonts are supported, for \LaTeX{} users, by the \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} and -\FontName{Palatino}, as -well as a more reliable set of font metrics. +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 @@ -4970,6 +5076,8 @@ The archive \File{lw35nfss.zip} is laid out according to the 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} @@ -5009,10 +5117,10 @@ 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 |texmf| tree (\File{texmf.local}, +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 |pfb| files into them. +\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 @@ -5022,7 +5130,7 @@ 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 |config.*|; each of these contains +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: @@ -5049,10 +5157,21 @@ Remember, after all such changes, the % beware line breaks \item[CM font maps]\CTANref{bluesky-maps} \end{ctanrefs} -\Question[Q-instt1font]{Installing a Type~1 font} +\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 stages. +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 @@ -5087,71 +5206,81 @@ it may be separated into a modest set of stages. 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 the documentation for details. + \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 whose Berry - name is \meta{bname}: -\begin{narrowversion} + destinations for the various files related to a font family \meta{fname}: \begin{verbatim} .pfb, -.pfa .../fonts/type1/<foundry>/<bname> -.tfm .../fonts/tfm/<foundry>/<bname> -.vf .../fonts/vf/<foundry>/<bname> -.fd .../tex/latex/fontinst/ \ - <foundry>/<bname> -\end{verbatim} - {% - \small Note: the split line is only to fit into the column: in - actual use, reconstruct the line and suppress the spaces.\par - } -\end{narrowversion} -\begin{wideversion} +.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} -.pfb, -.pfa .../fonts/type1/<foundry>/<bname> -.tfm .../fonts/tfm/<foundry>/<bname> -.vf .../fonts/vf/<foundry>/<bname> -.fd .../tex/latex/fontinst/<foundry>/<bname> +updmap-sys --enable Map <fname>.map \end{verbatim} -\end{wideversion} - The irregular things being \extension{map} files: in te\TeX{} 3.0 and - later, these should be placed according to the revised \acro{TDS} as + \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} -.map .../fonts/map/dvips/<foundry> +initexmf --edit-config-file updmap \end{verbatim} -and in other (earlier) systems as + \end{quote} + adding a line at the end: + \begin{quote} \begin{verbatim} -.map .../dvips/fontinst/<foundry> +Map <fname>.map \end{verbatim} -\item Regenerate the file indexes (as described in - \Qref[question]{package installation}{Q-inst-wlcf}). -\item Update the \ProgName{dvips} and other maps: - \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 - |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 <xyz>.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} which is described in \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{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} -The whole process is very well (and thoroughly) described in Philipp -Lehman's guide to font installation, which may be found on \acro{CTAN}. +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} @@ -5179,8 +5308,8 @@ is a good starting point 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 |plain| base -file using \ProgName{inimf}, |plain.mf|, and |local.mf|: +a \texttt{plain} base +file using \ProgName{inimf}, \texttt{plain.mf}, and \texttt{local.mf}: \begin{htmlversion} \begin{verbatim} % inimf @@ -5232,7 +5361,7 @@ 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 |plain| base by default on your system, then you're +\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} @@ -5240,49 +5369,49 @@ distribution% \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 |virmf &plain| loading the |plain| base -file. +\ProgName{mf} which executes \texttt{virmf \&plain} loading the +\texttt{plain} base file. -The usual way to create a font with |plain| \MF{} is to start -it with the line -\htmlignore -\bgroup -\par\vskip\topsep -\hangindent3em\hangafter1\raggedright\parindent10pt\relax -|\mode=<mode name>;| |mag=<magnification>;| |input <font file name>|% -\par\vskip\topsep -\egroup -\noindent in -\endhtmlignore -\begin{htmlversion} +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} -in -\end{htmlversion} -response to the `**' prompt or on the \MF{} command line. (If -|<mode name>| is unknown or omitted, the mode defaults to `proof' and +\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 |<magnification>| is a floating point number or +The \texttt{<magnification>} is a floating point number or `magstep' (magsteps are defined in \emph{The \MF{}book} and \emph{The \TeX{}book}). -If |mag=<magnification>| is omitted, then the default +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 |\| and |;| characters must usually be quoted or -escaped, so this would typically look something like +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' + 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 |\smode| command. +\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} @@ -5296,8 +5425,8 @@ the file fillin:=-0.1; o_correction:=.5; \end{verbatim} -(note the absence of the |mode_def| and |enddef| commands), you would -type +(note the absence of the \texttt{mode\_def} and \texttt{enddef} +commands), you would type \begin{verbatim} mf \smode="ln03"; input cmr10 \end{verbatim} @@ -5435,7 +5564,7 @@ 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 Plain \TeX{}, you load whatever fonts you like; if the encoding of +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 @@ -5483,11 +5612,11 @@ this, you have three options: (See \Qref[question]{}{Q-commercial} for details of these suppliers.) \end{narrowversion} -\typeout{after narrowversion, before wideversion} +%\typeout{after narrowversion, before wideversion} \begin{wideversion} (See \Qref{commercial suppliers}{Q-commercial} for details.) \end{wideversion} -\typeout{after 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 @@ -5569,7 +5698,7 @@ For the \LaTeX{} user trying to use the 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 |psfonts.map| file, so that \ProgName{dvips} will know +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). @@ -5610,7 +5739,7 @@ by \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 maths, then, there are relatively few choices (though the list is +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') @@ -5629,7 +5758,8 @@ mathematics include: 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 (|msam| and |msbm|) and Euler text fonts. + 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 @@ -5658,16 +5788,22 @@ mathematics include: 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. -\item[Kp-fonts]The Johannes Kepler project\\ + + 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). -\item[MathDesign](4 entire families\dots{}so far) Paul Pichareau\\ + + 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 @@ -5683,6 +5819,11 @@ mathematics include: 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, @@ -5704,10 +5845,24 @@ mathematics include: 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} @@ -5719,7 +5874,7 @@ commercially, include: 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 Plain~\TeX{}, \LaTeXo{} and current \LaTeX{} are + fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{} are provided. \nothtml{\bgroup\raggedwithindent} @@ -5774,7 +5929,7 @@ commercially, include: 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 Plain~\TeX{}, \LaTeXo{} + 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}. @@ -5789,7 +5944,7 @@ commercially, include: 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 - Plain~\TeX{}, \LaTeXo{} and current \LaTeX{} are provided. + \plaintex{}, \LaTeXo{} and current \LaTeX{} are provided. \nothtml{\bgroup\raggedwithindent} For further details (including samples) see\\ @@ -5803,7 +5958,7 @@ commercially, include: 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} \texttt{msam} and \texttt{msbm} symbol sets). `Lucida + \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 @@ -5828,37 +5983,12 @@ commercially, include: 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 1.1](3 fonts) Publish or Perish (Michael Spivak)\\ -%% The set contains maths italic, symbol, and extension fonts, designed -%% to work well with the Times-Roman family, which is resident on many -%% printers, and which is supplied with some \acro{PC} versions. In -%% addition you may want to complement this basic set with Adobe's -%% Times Smallcap, and perhaps the set of Adobe `Math Pi' fonts, which -%% include blackboard bold, blackletter, and script faces. -%% \par -%% \nothtml{\bgroup\raggedwithindent} -%% For a sample, see \URL{http://www.YandY.com/download/chironmt.pdf} -%% \nothtml{\par\egroup} -%% \item[MathTime Plus](12 fonts) Publish or Perish (Michael Spivak)\\ -%% Adds bold and heavy versions of the basic math fonts, as well as -%% upright math ``italic''. There are also Greek letters for use in -%% typesetting terms commonly used in physics, as well as regular and -%% bold script faces. Both MathTime distributions include support for -%% use with Plain \TeX{} and \LaTeXo{} (including code to link in -%% Adobe Math Pi~2 and Math Pi~6). Support under \LaTeXe{} is provided -%% in -%% \Qref*{\acro{PSNFSS}}{Q-usepsfont} -%% thanks to Frank Mittelbach and David Carlisle. -%% \par -%% \nothtml{\bgroup\raggedwithindent} -%% For a sample, see \URL{http://www.YandY.com/download/mathplus.pdf} -%% \nothtml{\par\egroup} \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 Plain \TeX{} and \LaTeXe{}, and + The fonts are supported under both \plaintex{} and \LaTeXe{}, and are exclusively available for purchase from \Qref*{Personal \TeX{} Inc}{Q-commercial}. \par{} @@ -5881,7 +6011,7 @@ commercially, include: 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 Plain~\TeX{}, \LaTeXo{} and current \LaTeX{} + using the fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{} are provided. \nothtml{\bgroup\raggedwithindent} @@ -5895,7 +6025,7 @@ commercially, include: 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 Plain~\TeX{}, \LaTeXo{} and current \LaTeX{} + using the fonts with \plaintex{}, \LaTeXo{} and current \LaTeX{} are provided. Bitmapped copies of the fonts are available free, on \acro{CTAN}. @@ -6029,6 +6159,8 @@ print file (\PS{} or \acro{PDF}) for their output device. \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} @@ -6059,9 +6191,9 @@ versions), which should be available in any recent \TeX{} distribution. \subsection{Macros for using fonts} -\Question[Q-fonts-pln]{Using non-standard fonts in Plain \TeX{}} +\Question[Q-fonts-pln]{Using non-standard fonts in \plaintex{}} -Plain \TeX{} (in accordance with its description) doesn't do anything +\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. @@ -6093,18 +6225,18 @@ 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 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 ``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 +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 Plain \TeX{} which you can run in the same way that you run -Plain \TeX{} using the original \acro{CM} fonts, by invoking +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.) @@ -6114,9 +6246,9 @@ 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 Plain \TeX{} approaches to the problem (packages +Other \plaintex{} approaches to the problem (packages \Package{plnfss}, \Package{fontch} and \Package{ofs}) break out of the -Plain \TeX{} model, towards the sort of font selection provided by +\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. @@ -6144,7 +6276,7 @@ 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} Plain \TeX{} macro package aims to be a complete +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 @@ -6170,7 +6302,7 @@ 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 Plain \TeX{}, of course, with +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}. @@ -6181,7 +6313,7 @@ fonts from Computer Modern to Concrete. Packages \Package{beton} and \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 Plain \TeX{}-based set: these +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 @@ -6247,8 +6379,8 @@ 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 |$TEXMF| -tree, and +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}. @@ -6259,7 +6391,7 @@ Type~1-to-\acro{PK} conversion programs, by \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 - |extra_modules="| (and before the closing quotes). + \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 @@ -6312,7 +6444,7 @@ World Wide Web, there are four technologies to consider: 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 Plain \TeX{} and + commands); there are supporting macro packages for \plaintex{} and \LaTeX{}). \end{itemize} @@ -6390,7 +6522,7 @@ 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 Plain \TeX{}, the \Qref*{\Eplain{} macros}{Q-eplain} can +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. @@ -6699,7 +6831,7 @@ bases on which the excellence of the \TeX{} system rests. 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 -``|\'||e|''. However, since this involves two characters being +``\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, @@ -6769,25 +6901,25 @@ patching, for files created by ``not too old versions'' of \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 -|-Ppdf|) to acquire an appropriate copy of the font; these copies are +\texttt{-Ppdf}) to acquire an appropriate copy of the font; these copies are then patched back into the original file. -%% Another program, available free from \nothtml{\YandY{} (}% beware line break -%% \Qref{\YandY{}}{Q-commercial}\nothtml{)} for Windows users who also -%% have Adobe \ProgName{Acrobat} \ProgName{Distiller} available, is -%% \href{http://www.yandy.com/download/dvipsstrip.exe}{\ProgName{dvipsstrip}}. -%% \ProgName{Dvipsstrip} simply removes -%% the fonts: the idea is that you then reinstate them in the course of a -%% run through \ProgName{distiller} (which only works if -%% \ProgName{distiller} `knows' about the fonts: it can be instructed via -%% its \texttt{Settings}\arrowhyph{}\texttt{Font Locations} tool). -%% \par -Yet another option is Frank Siegert's (shareware) +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} @@ -6889,7 +7021,7 @@ 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 Plain \TeX{} and +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. @@ -6899,7 +7031,7 @@ 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 Plain \TeX{}. +written in \plaintex{}. The \Package{graphics} package takes a variety of ``driver options''~--- package options that select code to generate the @@ -6907,7 +7039,7 @@ 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 determins whether +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 @@ -6992,9 +7124,9 @@ level~2 or higher). (\ProgName{Unix} users should beware of your screen resolution.) Special purpose applications \ProgName{jpeg2ps} (which converts -\acro{JPEG} files using \PS{} level 2 functionality) and +\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 +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''. @@ -7002,7 +7134,10 @@ 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. +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} @@ -7375,7 +7510,7 @@ as in: } \end{verbatim} \end{quote} -A more \LaTeX{}-y way of doing the job (somewhat innefficiently) uses +A more \LaTeX{}-y way of doing the job (somewhat inefficiently) uses the \Package{calc} package: \begin{quote} \begin{verbatim} @@ -7397,7 +7532,7 @@ 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 eperience an error such +ordinarily have the fonts loaded, and you'll experience an error such as \begin{quote} \begin{verbatim} @@ -7415,7 +7550,7 @@ 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' metapost output after processing through +to view the `original' \MP{} output after processing through \LaTeX{} and \ProgName{dvips}. Conditional compilation may be done either @@ -7459,7 +7594,7 @@ 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 Plain~\TeX{} user may use an adaptation of a jiffy of Knuth's, by +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 @@ -7493,25 +7628,26 @@ of drawing, and setup, here are a few systems you may consider: 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 +\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, this means there are many - astounding things that can in principle be achieved. + 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{pdftricks}, which (like + users may use \Package{pst-pdf}, which (like \Package{epstopdf}~--- see % ! line break \Qref[question]{\PDFLaTeX{} graphics}{Q-pdftexgraphics}) generates - \acro{PDF} files on the fly from \Package{pstricks} commands. The - documentation is good (you may browse it via the % ! line break - \href{http://pstricks.tug.org/}{\Package{pstricks} page} - on the \acro{TUG} web site). There is also a mailing list + \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 \href{http://tug.org/pipermail/pstricks/}{list archives}. + 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 @@ -7540,8 +7676,9 @@ of drawing, and setup, here are a few systems you may consider: \begin{ctanrefs} \item[dratex.sty]\CTANref{dratex} \item[mfpic]\CTANref{mfpic} -\item[pdftricks.sty]\CTANref{pdftricks} +\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} @@ -7600,10 +7737,15 @@ 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. -(Unfortunately, \Package{psfrag} can't be used with \PDFLaTeX{}, -though one might hope that it would be susceptible to the same sort of -treatment as is used in the \Package{pdftricks} package. On the other -hand, + +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} @@ -7611,7 +7753,7 @@ hand, \Qref*{V\TeX{}}{Q-commercial}'s GeX processor \end{wideversion} explicitly deals with \Package{psfrag}, both in its free and -commercial instances.) +commercial instances. The \Package{psfragx} package goes one step further than \Package{psfrag}: it provides a means whereby you can put the @@ -7649,12 +7791,14 @@ environment which itself includes the graphic. I would recommend 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} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% @@ -7813,16 +7957,10 @@ There's more on the subject in the % line wrap \Qref*{case of letters in your bibliography}{Q-capbibtex}, also makes a hash of accent commands: -\begin{htmlversion} -``\texttt{ma\~nana}'' comes out as ``ma nana'' (!). The solution is -similar: enclose the troublesome sequence in braces, as -``|{|\texttt{\~n}|}|'', in this example. -\end{htmlversion} -\htmlignore -``|ma\~nana|'' comes out as ``ma nana'' (!). The solution is similar: -enclose the troublesome sequence in braces, as ``|{\~n}|'', in this -example. -\endhtmlignore +``\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{}} @@ -7939,7 +8077,7 @@ AUTHOR = {Fred Q. Bloggs and John P. Doe and \end{quote} Some bibliography styles implement clever acrobatics with very long author lists. You can force truncation by using the pseudo-name -``|others|'', which will usually translate to something like +``\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} @@ -7952,7 +8090,7 @@ AUTHOR = {Fred Q. Bloggs and others} 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 beconsidering developing one such for use +\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 @@ -8053,11 +8191,11 @@ removes it. \item[urlbst]\CTANref{urlbst} \end{ctanrefs} -\Question[Q-bibplain]{Using \BibTeX{} with Plain \TeX{}} +\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 Plain -\TeX{}, either directly or with \Qref*{\Eplain{}}{Q-eplain}. See +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} @@ -8178,7 +8316,8 @@ 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]{Transcribed initials in \BibTeX{}} +\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). @@ -8242,6 +8381,7 @@ 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, @@ -8250,9 +8390,68 @@ does nothing: } \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. +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} @@ -8579,8 +8778,8 @@ 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{miltibbl} and -\Package{mltibib} is that selection of what appears in each +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. @@ -8589,7 +8788,7 @@ 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{thebibliograph} environment it +(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 @@ -9091,7 +9290,7 @@ 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 pakages that +\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. @@ -9162,16 +9361,24 @@ 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, \URL{http://purl.org/nxg/note/posters}; -\item from ``\emph{awf}'' and ``\emph{capes}'' - \URL{http://www.robots.ox.ac.uk/~awf/latex-posters/}; +\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}'', - \URL{http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html}, +\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, but has hints which are generally useful. + Florida styled poster (offering supporting material as necessary), + but has hints which are generally useful. \end{itemize} \begin{ctanrefs} \item[a0poster.cls]\CTANref{a0poster} @@ -9336,15 +9543,15 @@ of vertically-shifting a single-page letter, try the following hack: \end{verbatim} in the preamble of your file. -Doing-it-yourself is a common strategy; Knuth (for use with plain -\TeX{}, in the \TeX{}book), and Kopka and Daly (in their Guide to +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 |lfm| +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. @@ -9499,9 +9706,6 @@ 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. - -The documentation of \Package{fncychap} is distributed as a separate -\PS{} file. \begin{ctanrefs} \item[anonchap.sty]\CTANref{anonchap} \item[fncychap.sty]\CTANref{fncychap} @@ -9784,15 +9988,15 @@ 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, -|figure*| provides a floating page-wide figure (and |table*| a +\texttt{figure*} provides a floating page-wide figure (and \texttt{table*} a page-wide table) which will do the necessary. -The ``|*|''ed float environments can only appear at the top of a page, -or on a whole page~--- |h| or |b| float placement directives are +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 |figure| environments, +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} @@ -9804,35 +10008,39 @@ new float type. 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} +\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} - } +\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 @@ -9840,15 +10048,17 @@ 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} % full width abstract - ... text + \begin{onecolabstract} % ditto abstract + ... text \end{onecolabstract} ] -\saythanks % typeset any \thanks +\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} @@ -9893,7 +10103,7 @@ of \csx{cleardoublepage}: instructions on macro programming why this is a solution. Note that the \emph{\acro{KOMA}-Script} replacements for the -\Class{book} amd \Class{report} classes (\Class{scrbook} and +\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 @@ -10109,70 +10319,119 @@ Documentation of \Package{chappg} is to be found in the package file. \subsection{Page layout} -\Question[Q-papersize]{Printer paper sizes} +\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} -If you're looking at this answer, it's likely you have a problem with -fitting output to the page. It may be a common problem with Adobe -\ProgName{[Acrobat] Reader}: printing from that program % ! line break -\emph{by default} shrinks the page ''to fit''. Unfortunately, its -calculation doesn't take the existing margins of the document into -account, 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. +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\% of Normal size)~--- change to ''100\%''. -\end{quote} - -More generally, we should recognise that paper sizes can be a pain: -they're a forgotten backwater, because -there's no \acro{DVI} command to specify the paper size of the -document. One usually finds American ``letter'' paper size being -assumed, by default, in macro packages (such as \Class{plain}~\TeX{} and -\LaTeX{}); but distributions provide separate configuration files for -\acro{DVI} drivers. 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 change the paper -size their document is designed for, pretty easily (and once off), but -they have to ensure that every run of \ProgName{xdvi}, -\ProgName{dvips}, or whatever, is given the correct override for using -anything non-`standard'. - -Furthermore, the default paper size for \acro{DVI} drivers may be -changed by a distribution management command, but this still doesn't -provide for people using the ``wrong'' sort of paper for some reason. - -An interestingly different issue arises for users of \PDFTeX{}~--- the -\acro{PDF} format \emph{does} have the means of expressing paper size, -but much of the core software predates \PDFTeX{}, so not even -\PDFLaTeX{} sets the correct values into \csx{pdfpagewidth} and -\csx{pdfpageheight}. + 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 in the case of \PDFTeX{} and V\TeX{}, 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 +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 of the paper size the document -is going to print to, and can issue the commands necessary to ensure -the correct size is used. If \Package{geometry} is used when a -document is being processed by either \PDFLaTeX{} or V\TeX{}, 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 two package options (\pkgoption{dvipdfm} and \pkgoption{dvips}) -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{}.) +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} @@ -10181,14 +10440,35 @@ So, the resolution of the problem is to add \end{verbatim} \end{quote} (where \pkgoption{dvixxx} is your current favourite \acro{DVI} -driver), and the document will run correctly with any of -\LaTeX{} (whether or not run on V\TeX{}) or \PDFLaTeX{}. +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''. -Give the \Package{typearea} package the \pkgoption{pagesize} and it -will do the same job, for \PDFLaTeX{} output and \PS{} output from -\LaTeX{} via \ProgName{dvips}. +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} @@ -10351,15 +10631,17 @@ environment (which is a close relation of the \LaTeX{} as far as \TeX{} is concerned: it merely moves text around inside the width that \TeX{} believes in. -The \Package{chngpage} package provides ready-built commands to do the +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 or an even page of a -two-sided document. The package's documentation (in the file itself) -suggests a strategy for changing text dimensions between pages~--- as -mentioned above, changing the text dimensions within the body of a -page may lead to unpredictable results. +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 clunkier still: the +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} @@ -10375,6 +10657,7 @@ to make the page one line longer, or \end{quote} to make the page one line shorter. \begin{ctanrefs} +\item[changepage.sty]\CTANref{changepage} \item[chngpage.sty]\CTANref{chngpage} \end{ctanrefs} @@ -10665,7 +10948,7 @@ 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 -exaple is list items~--- they suggest page breaks between them. Even +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. @@ -10787,6 +11070,10 @@ as simple as \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 @@ -10817,6 +11104,7 @@ the `base' text of the document. \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} @@ -10991,22 +11279,23 @@ the \extension{tex} file). A more comprehensive solution is to be found in the \Package{soul} package (which is optimised for use with \LaTeX{}, but also works with -Plain \TeX{}). Soul also permits hyphenation of letterspaced text; +\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{letterspace}, -which uses the micro-typography capabilities of current \PDFTeX{}. -\Package{Letterspace} expands the natural spacing font itself, rather +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. \Package{Letterspace} provides a means of -protecting the ligatures in a letter-spaced text. +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[letterspace.sty]Distributed as part of the \CTANref{microtype} - bundle +\item[microtype.sty]\CTANref{microtype} \item[soul.sty]\CTANref{soul} %\item[tracking.sty]\CTANref{tracking} \end{ctanrefs} @@ -11018,22 +11307,20 @@ The trick with typesetting ragged right is to be sure you've told the 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 Plain -\TeX{} 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 -% beware line break -\nothtml{hyphenation is suppressed }% -\Qref{hyphenation is suppressed}{Q-hyphoff}) painfully large gaps may -sometimes be required. +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 Plain \TeX{} +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 signficance of the various +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} @@ -11060,9 +11347,9 @@ restores flush justification at both margins: 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 |1.0em| by -default, and there's no knowing what you (or some other class) will -have done. +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 @@ -11087,7 +11374,7 @@ permits areas of justified text in a larger area which is ragged. \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 |\verbatiminput| that takes a file name as +which provides a command \csx{verbatiminput} that takes a file name as argument: \begin{quote} \begin{verbatim} @@ -11252,7 +11539,7 @@ Documentation is available on the % ! line break 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 Plain \TeX{} +\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 @@ -11315,7 +11602,7 @@ 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 similiar both in +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 @@ -11417,7 +11704,7 @@ The following programs are available: 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 Plain \TeX{}). + 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 @@ -11482,10 +11769,10 @@ There are three packages that help solve this problem: 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 Plain \TeX{}, + 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 - Plain \TeX{}). A small patch is also necessary: the required + \plaintex{}). A small patch is also necessary: the required sequence is therefore: \begin{narrowversion} \begin{verbatim} @@ -11509,10 +11796,9 @@ There are three packages that help solve this problem: The author of this answer prefers the (rather newer) \Package{url} package (directly or indirectly); both \Package{path} and -\Package{url} work well with Plain \TeX{} (though of course, the fancy +\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 Plain -\TeX{}.) +(\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 @@ -11565,7 +11851,7 @@ 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 -(|abc| notation). It was designed primarily for folk and traditional +(\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 @@ -11736,7 +12022,7 @@ environments may be nested, and may appear inside \environment{multicols} environments; however, floats, footnotes and marginpars will be lost. -For Plain \TeX{} users, the facilities of the \Package{backgrnd} +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 @@ -11790,7 +12076,7 @@ representation of what the user must type. \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 -Plain~\TeX{} user would bother with anyone else's code for). +\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. @@ -11820,7 +12106,7 @@ hours and minutes: the default is of course \texttt{:}. \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 definining the counter +of behind-the-scenes commands, as well as defining the counter itself. Among other things, \cmdinvoke*{newcounter}{fred} creates a command @@ -11845,11 +12131,13 @@ 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 (``|-|{}|-~nnn~-|{}|-|''). Would you want to -achieve this by redefining \csx{thepage}, given the likely appearance -of the table of contents with the dashes attached every page number, -or of the modified \csx{pageref} references. In this case, the -modification is best done by redefining the page style itself, perhaps +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} @@ -11938,7 +12226,7 @@ contents itself, the \texttt{bibliography}, \texttt{index}, etc., to the table of contents. The \Class{KOMA-Script} classes have commands \csx{addchap} and -\csx{addsec}, which work like \csx{chapter} and \csx{section} but +\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. @@ -11989,8 +12277,8 @@ table of contents to the relevant place in the file), a slight adjustment is necessary: \begin{quote} \begin{verbatim} -\phantomsection \cleardoublepage +\phantomsection \addcontentsline{toc}{chapter}{Bibliography} \bibliography{frooble} \end{verbatim} @@ -12003,7 +12291,8 @@ 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; the \Class{memoir} class includes +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} @@ -12388,25 +12677,38 @@ The \cmdinvoke{tag*}{\csx{qedhere}} construction may be used in any of \begin{ctanrefs} \item[amsthm.sty]Distributed as part of the \AMSLaTeX{} bundle \CTANref{amslatex} -\item[ntheorem]\CTANref{ntheorem} +\item[ntheorem.sty]\CTANref{ntheorem} \end{ctanrefs} -\Question[Q-theoremfmt]{Roman theorems} +\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, to use it to create remarks, examples, proofs, +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 roman. +\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}} +\newtheorem{preremark}{Remark} +\newenvironment{remark}% + {\begin{preremark}\upshape}{\end{preremark}} \end{verbatim} -The \Package{ntheorem} package provides roman theorems directly. +\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} @@ -12484,8 +12786,8 @@ 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 -|\left( <expression> \right)|~--- the size of the parentheses is -matched to the vertical extent of the expression. +\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 @@ -12517,9 +12819,9 @@ itself running under \eTeX{}. 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 (``|\|'', -``|/|'' and ``|X|''), and a means of cancelling `to' a particular -value. +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} @@ -12528,13 +12830,13 @@ Documentation of \Package{cancel} is in the package file. \Question[Q-mathsize]{Adjusting maths font sizes} -In Plain~\TeX{}, when you introduce a new font size you must also +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 Plain~\TeX{} in sufficient +\Qref*{tutorials}{Q-man-tex} that discuss \plaintex{} in sufficient detail. In \LaTeX{}, of course, all this stuff is automated: there is a scheme @@ -13355,7 +13657,8 @@ with an option that has the same effect: Doing the job yourself is pretty easy: \Package{topcapt} switches the values of the \LaTeXe{} parameters \csx{abovecaptionskip} (default -value |10pt|) and \csx{belowcaptionskip} (default value |0pt|), so: +value \texttt{10pt}) and \csx{belowcaptionskip} (default value +\texttt{0pt}), so: \begin{quote} \begin{verbatim} \begin{table} @@ -13383,42 +13686,38 @@ There are two basic techniques for making fixed-width tables in can stretch particular cells in the table. Basic \LaTeX{} can make the gaps stretch: the \environment{tabular*} -environment takes an extra argument (before the |clpr| layout one) -which takes a length specification: you can say things like ``|15cm|'' +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 |clpr| layout argument, inside an |@{}| directive. So, -for example, one might have -\begin{htmlversion} -\begin{verbatim} -\begin{tabular*}{\columnwidth}{@{\extracolsep{\fill}}lllr} -\end{verbatim} -\end{htmlversion} -\htmlignore \ifpdf +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} -\else +\end{wideversion} +\begin{narrowversion} \begin{verbatim} \begin{tabular*}{\columnwidth}% {@{\extracolsep{\fill}}lllr} \end{verbatim} -\fi -\endhtmlignore +\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 |clpr| column -specification, |X|; |X| columns behave as |p| columns which expand to -fill the space available. If there's more than one |X| column in a -table, the spare space is distributed between them. +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 |C|, |L|, |R| and |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 +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 @@ -13520,7 +13819,7 @@ 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 Plain~\TeX{} commands. +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 @@ -13594,7 +13893,7 @@ 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 aligment +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 @@ -13802,39 +14101,39 @@ 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{htmlversion} +\begin{wideversion} +\begin{quote} \begin{verbatim} \begin{floatingfigure}[options]{width of figure} figure contents \end{floatingfigure} \end{verbatim} -\end{htmlversion} -\htmlignore -|\begin{floatingfigure}[|\emph{options}|]{|\emph{width of figure}|}|\\ -| |\emph{figure contents}\\ -|\end{floatingfigure}| -\endhtmlignore - +\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 |multicol| package, but doesn't work well +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} +\begin{wrapfigure}[height of figure in lines]{l,r,...}[overhang]{width} figure, caption, etc. \end{wrapfigure} \end{verbatim} @@ -13842,20 +14141,24 @@ in the neighbourhood of list environments (unless you change your \end{wideversion} \begin{narrowversion} \begin{quote} - |\begin{wrapfigure}[|\emph{height of figure in lines}|]|\\ - | {l|,|r|,\emph{etc}|}[|\emph{overhang}|]{|\emph{width}|}|\\ - | |\emph{figure, caption, etc.}\\ - |\end{wrapfigure}| + \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 |{l|\emph{,}|r|\emph{,etc}.|}| parameter can - also be specified as |i|\emph{(nside)} or |o|\emph{(utside)} for - two-sided documents, and uppercase can be used to indicate that - the picture should float. The overhang allows the figure to be + 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. @@ -13864,26 +14167,22 @@ in the neighbourhood of list environments (unless you change your 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 is: - -\begin{htmlversion} + various \MSDOS{} formats, etc.). The command for inserting a + picture at the start of a paragraph is: +\begin{wideversion} \begin{quote} - |\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}|\\ + \csx{parpic}\texttt{(width,height)(x-off,y-off)[Options][Position]\{Picture\}}\\ + \emph{Paragraph text} \end{quote} - \emph{Paragraph text} -\end{htmlversion} -\htmlignore -\ifpdf - |\parpic(|\emph{width}|,|\emph{height}|)(|\emph{x-off}\kern-.125em|,|\emph{y-off}|)|% - |[|\emph{Options}|][|\emph{Position}|]|\\ -\else - |\parpic(|\emph{width}|,|\emph{height}|)(|\emph{x-off}\kern-.125em|,|\emph{y-off}|)|\\ - | [|\emph{Options}|][|\emph{Position}|]|\\ -\fi - | {|\emph{Picture}|}|\\ - \emph{Paragraph text} -\endhtmlignore - +\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 @@ -13891,17 +14190,17 @@ in the neighbourhood of list environments (unless you change your Unfortunately (for those of us whose understanding of German is not good), the documentation is in German. Piet van Oostrum has written - an English summary. + 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[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 @@ -13988,7 +14287,8 @@ than columns. So, we set things up by: \end{verbatim} \end{wideversion} \end{quote} -Now, we put `\texttt{\$}' before the first column specifier; and we put `|^|' +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} @@ -14043,7 +14343,7 @@ 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 ``|*|'' may be replaced by a column width specification. In this +The ``\texttt{*}'' may be replaced by a column width specification. In this case, the argument may contain forced line-breaks: \begin{quote} \begin{verbatim} @@ -14060,7 +14360,7 @@ case, the argument may contain forced line-breaks: \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 |*|-declared \csx{multirow}. +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 @@ -14079,7 +14379,7 @@ down one or other side of a table (with the help of the \end{tabular} \end{verbatim} \end{quote} -(which gives text going upwards; use angle |-90| for text going +(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 @@ -14136,18 +14436,18 @@ It's sometimes necessary to force a float to live on a page by itself. 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{verbatim} - \begin{figure}[p!] -\end{verbatim} -but the overriding |!| modifier has no effect on float page floats; so +\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 |totalnumber| (``total -number of floats per page'') doesn't work: -|totalnumber| only applies to floats on `text' pages (pages containing -text as well as one or more float). So, to allow any +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: @@ -14159,6 +14459,7 @@ the separation between floats really big: \makeatother \end{verbatim} \end{quote} + \Question[Q-vertspacefloat]{Extra vertical space in floats} A common complaint is that extra vertical space has crept into @@ -14275,10 +14576,10 @@ instead you use \end{verbatim} \end{quote} the figure will stretch right across the page (just the same as a -\environment{figure*} in standard \LaTeX{}'s |twocolumn| option). +\environment{figure*} in standard \LaTeX{}'s \pkgoption{twocolumn} option). It's possible to have single-column figures and tables with captions, -using the `|[H]|' placement option introduced by the \Package{float} +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 @@ -14339,10 +14640,12 @@ their layout: the \csx{@fptop} skip is always followed by a correction for that.) -The \LaTeX{} defaults are:\\ -\csx{@fptop} = |0pt + 1fil|\\ -\csx{@fpsep} = |8pt + 2fil|\\ -\csx{@fpbot} = |0pt + 1fil|\\ +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. @@ -14445,7 +14748,7 @@ notes. The ``table'' may consist of diagrams, and a parameter in ``figure'' rather than a ``table''. Otherwise, if your table is not floating (it's just a -`|tabular|' in the middle of some text), there are several +`\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 @@ -14453,7 +14756,7 @@ things you can do to fix the problem. 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 |minipage| anyway. This provides all the +\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 @@ -14462,16 +14765,19 @@ things you can do to fix the problem. tools distribution; they're noticeably less efficient than the standard \environment{tabular} environment, but they do allow footnotes. -\item Grab hold of \Package{footnote}, and put your - \environment{tabular} environment inside a \environment{savenotes} - environment. Alternatively, say +\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 handle footnotes correctly. + 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. It may also cause other table-related packages (not - the standard `tools' ones, though) to become very unhappy and stop - working. + 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 @@ -14504,9 +14810,10 @@ To suppress the footnote in headings and table of contents: \item Take advantage of the fact that the mandatory argument doesn't `move' if the optional argument is present: - |\section[title]{title|\cmdinvoke{footnote}{title ftnt}|}| + \cmdinvoke{section}[title]% + \texttt{\{title}\cmdinvoke{footnote}{title ftnt}\texttt{\}} \item Use the \Package{footmisc} package, with package option - |stable|~--- this modifies footnotes so that they softly and + \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} @@ -14696,30 +15003,30 @@ 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 two-pass process, +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{footnpag} package does per-page footnotes and nothing -else. - 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}. +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. +\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. -Documentation of \Package{footnpag} comes as a \acro{DVI} file -\File{footnpag-user} in the distribution. Documentation of -\Package{perpage} appears in the package file, only: however, it -amounts to no more than appears above\dots{} +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} @@ -14768,8 +15075,8 @@ 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 Plain -\TeX{}, since the syntax of the \csx{input} command is so peculiar. +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 @@ -14904,7 +15211,7 @@ 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 Plain \TeX{} application +\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 @@ -14948,7 +15255,7 @@ 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, he package \Package{changes} allows the user to manually +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 @@ -14990,19 +15297,19 @@ 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]|{||}| and % line break! -\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): +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 +use \verb+\iftrue+ -- a surprise \fi \end{verbatim} \end{quote} @@ -15230,9 +15537,10 @@ Documentation of \Package{chapterfolder} is in French, but the \item[import.sty]\CTANref{import} \end{ctanrefs} -\Question[Q-RCS]{Version control using \acro{RCS}, \acro{CVS} or \ProgName{Subversion}} +\Question[Q-RCS]{Version control using \acro{RCS}, \acro{CVS} or the like} -If you use \acro{RCS}, \acro{CVS} or \ProgName{Subversion} to maintain +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 @@ -15246,14 +15554,14 @@ 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 Plain \TeX{}, then you can use the +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.498 $ % or any RCS keyword -\RCS$Date: 2007/11/05 22:31:23 $ +\RCS$Revision: 1.548 $ % or any RCS keyword +\RCS$Date: 2008/06/20 13:37:44 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -15263,15 +15571,15 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.498 $ % or any RCS keyword -\RCS$Date: 2007/11/05 22:31:23 $ +\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 +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} @@ -15291,18 +15599,29 @@ 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. -The alternative 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 \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 you find best. +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} @@ -15395,21 +15714,19 @@ the \Package{everyshi} package. \item[totpages.sty]\CTANref{totpages} \end{ctanrefs} -\Question[Q-inclplain]{Including Plain \TeX{} files in \LaTeX{}} +\Question[Q-inclplain]{Including \plaintex{} files in \LaTeX{}} -\LaTeX{}, though originally \nothtml{based on Plain \TeX{} (}% beware line brk -\Qref{based on Plain \TeX{}}{Q-LaTeXandPlain}\nothtml{)}, does not -contain all of Plain \TeX{}'s commands. Worse, some Plain \TeX{} +\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 Plain -\TeX{} documents (or parts of documents) to be typeset within -\LaTeX{}. +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 Plain \TeX{} commands, to +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 Plain \TeX{} +defines a \environment{plain} environment, in which a \plaintex{} document may be processed: \begin{quote} \begin{verbatim} @@ -15498,7 +15815,7 @@ 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 Plain \TeX{}, make +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, @@ -15664,7 +15981,7 @@ texconfig hyphen latex or get a DOS window and run:\\ \texttt{initexmf -\relax-dump} - On a \Package{\miktex{}} distribtution v2.0 or later, the whole + 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{}% @@ -15716,10 +16033,17 @@ 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 |nohyphenation|, +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. +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, @@ -15784,7 +16108,7 @@ If the word occurs in just one place, put it in a box: \mbox{oddword} \end{verbatim} \end{quote} -(Plain~\TeX{} users should use \csx{hbox}, and take care at the start +(\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. @@ -15823,7 +16147,7 @@ behaviour: \uchyph=0 \end{verbatim} \end{quote} -will stop hyphenation of upper-case words. (Note that Plain \TeX{} +will stop hyphenation of upper-case words. (Note that \plaintex{} syntax is needed here: there's no \LaTeX{} alternative for setting this value.) @@ -16008,7 +16332,7 @@ 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} +\item[\nothtml{\rmfamily}LuxiMono fonts]\CTANref{luximono} \end{ctanrefs} \Question[Q-varwidth]{Automatic sizing of \environment{minipage}} @@ -16028,7 +16352,7 @@ box of width exactly \texttt{2cm}, 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 analagous to the \csx{widthof} command for use with the +function analogous to the \csx{widthof} command for use with the \Package{calc} package. The \Package{eqparbox} package extends \Package{pbox}'s idea, by @@ -16127,7 +16451,7 @@ 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 -Plain~\TeX{} and \LaTeX{} (packages \Package{amssymb} and +\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). @@ -16263,7 +16587,7 @@ the \AMSLaTeX{} \Package{amsmath} package, which disables this font-switching and you must use one of the techniques outlined below. -The Plain \TeX{} solution \emph{does} work, in a limited way: +The \plaintex{} solution \emph{does} work, in a limited way: \begin{quote} \begin{verbatim} {\boldmath$\theta$} @@ -16337,16 +16661,16 @@ double-dashed one. \Question[Q-underscore]{How to use the underscore character} -The underscore character \texttt{\_} is ordinarily used in +The underscore character `\texttt{\_}' is ordinarily used in \TeX{} to indicate a subscript in maths mode; if you type -\texttt{\_} in the course of ordinary text, \TeX{} will +\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'. +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 @@ -16356,8 +16680,9 @@ 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 fuller encoding, such as -\acro{T}1, which has an underscore character in every font. +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: @@ -16378,7 +16703,7 @@ about section headings and the like. \Question[Q-atsign]{How to type an `@' sign?} -Long ago, some packages used to make the `@' sign active, so that +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. @@ -16398,7 +16723,7 @@ 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 fonts provided as part of the \acro{EC} font +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 @@ -16423,10 +16748,10 @@ 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 achive +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 Plain \TeX{} and \LaTeX{}), for using these +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 @@ -16450,7 +16775,7 @@ 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 -Plain~\TeX{} user might make use of the fonts. +\plaintex{} user might make use of the fonts. Euro symbols are found in several other places, which we list here for completeness. @@ -16594,18 +16919,8 @@ 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{patch} or -\Package{patchcmd} systems. - -\Package{Patch} gives you an ingenious (and difficult to understand) -mechanism, and comes as an old-style \LaTeX{} documented macro file. -Sadly the old-style \Package{doc} macros are no longer available, but -the file (\File{patch.doc}) may be input directly, and the -documentation may be read (un-typeset). Roughly speaking, one gives -the command a set of instructions analagous to \ProgName{sed} -substitutions, and it regenerates the command thus amended. The -author of this \acro{FAQ} has (slightly reluctantly) given up using -\Package{patch}\dots{} +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 @@ -16613,13 +16928,50 @@ 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, if -\csx{b} contains ``|b|'', then -\csx{patchcommand}\nothtml{\penalty-150\hskip0pt\relax}\cmdinvoke{b}{a}{c} -will produce a new version of \csx{b} that contains ``|abc|''. -\begin{ctanrefs} +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''} @@ -16899,7 +17251,7 @@ 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 Plain \TeX{}) and after certain +\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. @@ -17065,7 +17417,7 @@ accurately. \Question[Q-activechars]{Defining characters as macros} Single characters can act as macros (defined commands), and both -Plain~\TeX{} and \LaTeX{} define the character +\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): @@ -17128,7 +17480,7 @@ For example, the definition } \end{verbatim} \end{quote} -does not work because it attemts to define an ordinary |_| character: +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: @@ -17257,7 +17609,7 @@ Two features of the coding are important: \end{itemize} Note that the technique used in such macros as \csx{chord}, here, is -analagous to that used in such commands as \csx{verb}; and, in just the +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{''}), @@ -17340,7 +17692,7 @@ these `races' could behave a bit like \LaTeX{} environments. 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 Plain \TeX{} or other packages; this answer +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. @@ -17355,7 +17707,7 @@ 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 Plain~\TeX{} user's point of view, +expansion''); from the \plaintex{} user's point of view, \csx{DeclareRobustCommand} should be treated as a non-checking version of \csx{newcommand}. @@ -17495,7 +17847,7 @@ 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 -Plain~\TeX{} user). Such a package may have gone ahead of you, so the +\plaintex{} user). Such a package may have gone ahead of you, so the test may need to be elaborated: \begin{quote} \begin{verbatim} @@ -17706,28 +18058,28 @@ in new macro packages. \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 Plain (or primitive) command that they +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 -Plain version. So, for example, use \csx{mbox} in place of \csx{hbox} +\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 Plain \TeX{} +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 Plain \TeX{} and \LaTeX{}, but behave slightly differently: in Plain -\TeX{} they terminate the current paragraph, but in \LaTeX{} they +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 -Plain \TeX{}. (There's no equivalent for users of the Plain \TeX{} command 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} @@ -17740,15 +18092,15 @@ 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 Plain \TeX{} and -\LaTeX{}. Plain \TeX{}'s font loading command +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 aer potential sources of great +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 Plain \TeX{} users of it like \csx{medskip}) +%% 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} @@ -17775,7 +18127,7 @@ 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 probablysolve the problem by using the correct +\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 @@ -17813,7 +18165,7 @@ that \LaTeX{} internal code is expected, which often looks `tidier'. 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.) Places to look for +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- @@ -17821,9 +18173,6 @@ 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}). -%You don't want to care about this stuff? Simply |\protect| all -%\LaTeX{} commands within these moving arguments. - 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{} @@ -17840,37 +18189,76 @@ What is a `robust command'?~--- it's a command that expands into legal 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. These lists aren't as reliable as the -list of moving arguments; the statements may have been true in -early versions of \LaTeXe{} but are not any longer necessarily so: +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 robust commands are redefined by certain packages to be - fragile (the \csx{cite} command commonly suffers this treatment). \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}) now always creates a robust - command. There is no reason that a package author should not also - make robust commands with optional arguments as part of the - package. + 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, and the \LaTeX{} team have removed the need for +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 are robust only 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. +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 @@ -18381,7 +18769,7 @@ use a different mechanism: be sure to check you're using it.) The names that are defined in the standard \LaTeX{} classes (and the -\Package{makeidex} package) are listed +\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. @@ -18589,21 +18977,27 @@ 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{chngpage} package needs to provide this functionality for +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{ifcpoddpage} true if the command was issued on an odd page. The +\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} @@ -18858,7 +19252,7 @@ done automatically, when the ``master'' counter is stepped (when the to zero). How would you do that for yourself? You might want to number -algorithms per section, or corrollaries per theorem, for example. If +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} @@ -18886,17 +19280,17 @@ command into a command \csx{counterwithin}. So: \counterwithin*{corrollary}{theorem} \end{verbatim} \end{quote} -will make the corrollary counter slave to theorem counters. The +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{thecorrollary} as % line brk! +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 corrollaries~--- there are potentially -many ``corrollary~1'' in any document, so it's as well to tie its number +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! @@ -19015,7 +19409,7 @@ Package nag Warning: Command \bf is an old There's also a web site \href{http://www.kohm.name/markus/texidate.html}{TeXidate} -which will do a static analysis of your document (unfortuantely, you +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 @@ -19107,7 +19501,7 @@ If you're in some situation where you can't use \eTeX{}, you need to change \TeX{} world, so one must resort to patching. There are two solutions available. -The \CONTeXT{} module \File{m-pictex.tex} (for Plain \TeX{} and +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. @@ -19116,7 +19510,7 @@ 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 Plain \TeX{}). +into \plaintex{}). And how does one use \PiCTeX{} anyway, given that the manual is so \Qref*{hard to come by}{Q-docpictex}? @@ -19147,8 +19541,7 @@ 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 \nothtml{``Too many unprocessed floats'' (see }% -\Qref[question]{``Too many unprocessed floats''}{Q-tmupfl}\latexhtml{).}{.} +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 @@ -19328,7 +19721,7 @@ 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-missssymb]{Missing symbol commands} +\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 @@ -19371,6 +19764,8 @@ of \Qref*{virtual fonts}{Q-virtualfonts} to map the old to the new series. \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} @@ -19711,11 +20106,11 @@ in the environment: \end{center} \end{verbatim} \end{quote} -The solution here is plain: use the |\|{}|\| command in the way it's +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. |\|{}|\| takes an optional argument, which specifies how much -extra space to add; the required effect in the text above can be had -by saying: +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} @@ -20264,7 +20659,7 @@ split footnotes. \Question[Q-marginparside]{Getting \csx{marginpar} on the right side} -In an ideal world, marginal notes would be in ``analagous'' places on +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 @@ -20501,7 +20896,7 @@ For both, an ``infinite'' tolerance is represented by the value 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 Plain~\TeX{}; in \LaTeX{}, use +be set as normal for dimens in \plaintex{}; in \LaTeX{}, use \csx{setlength}~--- for example: \begin{quote} \begin{verbatim} @@ -20517,12 +20912,12 @@ 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; Plain~\TeX{} and \LaTeX{} both set its value +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; -Plain~\TeX{} and \LaTeX{} both set its value to |200|. \LaTeX{}'s +\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 @@ -20884,7 +21279,7 @@ greater things), code as: \Question[Q-dolldoll]{Why use \csx{[}\,\dots{}\csx{]} in place of \texttt{\$\$}\,\dots{}\texttt{\$\$}?} \LaTeX{} defines inline- and display-maths commands, apparently -analagous to those that derive from the \TeX{} primitive maths +analogous to those that derive from the \TeX{} primitive maths sequences bracketing maths commands with single dollar signs (or pairs of dollar signs). @@ -20895,7 +21290,7 @@ 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 Plain \TeX{}, merely assuming that \LaTeX{}'s +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{\$\$ ... \$\$}. @@ -21489,7 +21884,7 @@ 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 Plain \TeX{} macro file \Package{etex.src}, which is +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. @@ -21539,7 +21934,7 @@ For example <*> \hyphenation{Ji-m\'e -nez} \end{verbatim} -(in Plain \TeX{}) or +(in \plaintex{}) or \begin{verbatim} ! Improper \hyphenation will be flushed. \leavevmode ->\unhbox @@ -21675,8 +22070,9 @@ 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 |emacs| and \ProgName{winedt} offer this facility). -However, groups are not \emph{only} created by matching |{| with |}|: +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. @@ -21828,14 +22224,14 @@ 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} (Plain~\TeX{}), \cmdinvoke{end}{document} (\LaTeX{}), or +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 Plain~\TeX{}, the +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}. @@ -21939,7 +22335,7 @@ document is not in maths mode and you have an |_| or a |^| character, \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 -commited a typo in failing to enter maths mode. \TeX{}, therefore, +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. @@ -22161,7 +22557,7 @@ perform the required transformation of the file being displayed. 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 (Plain~\TeX{}) all the way to the most +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. @@ -22330,7 +22726,7 @@ The error \end{verbatim} \end{narrowversion} is caused by nesting your input too deeply. You can provoke it with -the trivial (Plain \TeX{}) file \File{input.tex}, which contains +the trivial (\plaintex{}) file \File{input.tex}, which contains nothing but: \begin{verbatim} \input input @@ -22462,7 +22858,7 @@ is: \end{tabular} \end{verbatim} \end{quote} -where the `\bsbs' has been missed from the first line of the table. +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} @@ -22767,7 +23163,7 @@ correct: \end{tabular} \end{verbatim} \end{quote} -produces the error at the \bsbs{}. This usage is just wrong; if you +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} @@ -23221,7 +23617,7 @@ support for new Web standards. 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 represention of mathematics] +\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 @@ -23229,7 +23625,7 @@ support for new Web standards. 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 plugin + \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 @@ -23433,7 +23829,7 @@ 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 correspondance of the display to the final +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} @@ -23524,7 +23920,9 @@ 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. +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 @@ -23540,6 +23938,10 @@ 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} @@ -23563,16 +23965,49 @@ 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 many -reports of progress (on many projects), over the years, yet few -announcements of packages we can use. (There are probably usable -packages out there, but none that I know of.) - -Two interesting 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. +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 @@ -23601,6 +24036,7 @@ 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} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% diff --git a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex index 93dbaa7f3d3..cdfe79c55b8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex @@ -28,20 +28,21 @@ \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/texware/dvitype.web} +\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}{info/figsinltx.ps} +\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} @@ -69,10 +70,13 @@ \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} @@ -93,7 +97,6 @@ \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}{systems/msdos/picins/picins.zip} \CTANfile{picins-summary}{macros/latex209/contrib/picins/picins.txt} \CTANfile{pk300}{fonts/cm/pk/pk300.zip} \CTANfile{pk300w}{fonts/cm/pk/pk300w.zip} @@ -136,8 +139,6 @@ \CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf} \CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf} \CTANfile{vruler}{macros/latex/contrib/misc/vruler.sty} -\CTANfile{winedt}{systems/win32/winedt/winedt32.exe} \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} -\CTANfile{ziffer}{macros/latex/contrib/misc/ziffer.sty} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html index e902260d572..42f4b0a63f8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html @@ -10,13 +10,13 @@ great convenience. ready-to-run TeX systems for various architectures. Contents of the collection are: <ul> -<li> The TeX-live installation disc (a CD) provides TeX +<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 ‘Live’ disc (a DVD) providing TeX for +<li> The TeX Live ‘Live’ 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 + 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 @@ -31,7 +31,7 @@ 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/>Moew details of the collection are available from its own +<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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html index 3cda1f19b98..ab94f60b823 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html @@ -19,8 +19,6 @@ minor modifications (though some will require substantial work). 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 — see a later -answer about - <a href="FAQ-LaTeXtoPlain.html">translating to Plain TeX</a>. - +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-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html index 6808d33ebb8..8b6bd2a9737 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html @@ -26,9 +26,9 @@ this, you have three options: -\typeout{after narrowversion, before wideversion} + (See <a href="FAQ-commercial.html">commercial suppliers</a> for details.) -\typeout{after wideversion} + <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html index 1f52dd9b60b..7d6ffc3b674 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html @@ -1,8 +1,9 @@ <head> <title>UK TeX FAQ -- question label RCS</title> </head><body> -<h3>Version control using RCS, CVS or <i>Subversion</i></h3> -<p/>If you use RCS, CVS or <i>Subversion</i> to maintain +<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 @@ -19,14 +20,14 @@ following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.498 $ % or any RCS keyword -\RCS$Date: 2007/11/05 22:31:23 $ +\RCS$Revision: 1.548 $ % or any RCS keyword +\RCS$Date: 2008/06/20 13:37:44 $ ... \date{Revision \RCSRevision, \RCSDate} </pre> </blockquote><p> -<p/>If you’ve entered the brave new world of <i>subversion</i>, the +<p/>If you’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> @@ -45,18 +46,28 @@ about dealing with dates: 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/>The alternative 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’t much to choose between the two packages: you should read -the packages’ documentation to see which you find best. +<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’t much to +choose between the two packages: you should read the packages’ +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-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html index b0ab7d2e143..40217a1f6c7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html @@ -10,7 +10,7 @@ <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 + 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 @@ -20,7 +20,7 @@ <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 +<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 @@ -50,7 +50,7 @@ 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 +<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 “from the disc” without installing <em>anything</em>). @@ -73,13 +73,13 @@ <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 + 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’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 + 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 @@ -161,7 +161,7 @@ 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> +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html index 2daf0143688..5de14a4523d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html @@ -85,7 +85,7 @@ 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 correspondance of the display to the final +separate window), degree of correspondence of the display to the final output, and the balance they strike between visual aid and visual distraction. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acroantics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acroantics.html new file mode 100644 index 00000000000..9768f8a3c7b --- /dev/null +++ b/Master/texmf-doc/doc/english/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 “to fit” +(<em>by default</em>). 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. +<p/>Solve this problem by adjusting the <i>Reader</i>’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: “Fit to printer margins”) — change to + “None”, and<br> + Scale (default 95% of Normal size) — change to + “100%”. + + +</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-doc/doc/english/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html index c4896bbf060..7d024d8dd5c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html @@ -66,7 +66,7 @@ and we can use the command as <code>\</code><code>chord{F#}</code> or doesn’t require any special attention. </ul> <p/>Note that the technique used in such macros as <code>\</code><code>chord</code>, here, is -analagous to that used in such commands as <code>\</code><code>verb</code>; and, in just the +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 “<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> doesn’t work in arguments</a>”), diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html index 3603f16be4e..7bb7a695e11 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html @@ -62,7 +62,7 @@ For example, the definition } </pre> </blockquote><p> -does not work because it attemts to define an ordinary <code>_</code> character: +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: diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html index 3fe06ce167f..219c4a1d6ba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html @@ -10,7 +10,7 @@ done automatically, when the “master” counter is stepped (when 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 corrollaries per theorem, for example. If +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: <blockquote> @@ -35,17 +35,17 @@ command into a command <code>\</code><code>counterwithin</code>. So: \counterwithin*{corrollary}{theorem} </pre> </blockquote><p> -will make the corrollary counter slave to theorem counters. The +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>thecorrollary</code> as +will do the same, and also redefine <code>\</code><code>thecorollary</code> as <<i>theorem number</i>>.<<i>corollary number</i>>, which is a good scheme -if you ever want to refer to the corrollaries — there are potentially -many “corrollary 1” in any document, so it’s as well to tie its number +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 <i>chngcntr</i>, refer to the answer to diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html index 5ef701d5a78..570d284480a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html @@ -31,7 +31,7 @@ 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’s Adobe Acrobat Viewer’s treatment of bitmap Type 3 fonts that has made direct Metafont output -inreasingly unattractive, in recent years. If you have a PDF +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>-> <code>Document Properties</code>-> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html index 90868d69ce4..61cf79d5c30 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html @@ -31,7 +31,7 @@ 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’s front matter. -<p/>Packages in the <i>algorithmicx</i> bundle are similiar both in +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html index 943c835ebf6..b895f454cad 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html @@ -35,7 +35,7 @@ is: \end{tabular} </pre> </blockquote><p> -where the ‘\bsbs’ has been missed from the first line of the table. +where the ‘<code>\\</code>’ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html index 92e541b2fb0..c5d5971f4f9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html @@ -42,6 +42,6 @@ connect you to the <i>footmisc</i> directory — note that the “<a href="FAQ-findfiles.html">finding (La)TeX files</a>”. <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>. +<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-doc/doc/english/FAQ-en/html/FAQ-atsign.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html index de7322ecb64..7f2c267226b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label atsign</title> </head><body> <h3>How to type an ‘@’ sign?</h3> -<p/>Long ago, some packages used to make the ‘@’ sign active, so that +<p/>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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html index f3aa3f6a649..1c73cdc7fbe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html @@ -17,7 +17,7 @@ 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’ve included a file some other way (for example, using -<code>\</code><code>input</code>), you can probablysolve the problem by using the correct +<code>\</code><code>input</code>), you can probably solve the problem by using the correct command. <p/>If you’re using a fragment of a package or class, you may well feel confused: books such as the first edition of the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html index 6319f7c5ae2..2e9553e7a6e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html @@ -6,9 +6,9 @@ <a href="FAQ-capbibtex.html">case of letters in your bibliography</a>, also makes a hash of accent commands: -“<code>ma\~nana</code>” comes out as “ma nana” (!). The solution is -similar: enclose the troublesome sequence in braces, as -“<code>{</code><code>\~n</code><code>}</code>”, in this example. - +“<code>ma</code><code>\</code><code>~</code><code>nana</code>” comes out as “ma +nana” (!). The solution is similar that of the letter case problem: +enclose the troublesome sequence in braces, as +“<code>{</code><code>\</code><code>~</code><code>n}</code>”, 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-doc/doc/english/FAQ-en/html/FAQ-biblatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html index e0606824e69..055e46b3acb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html @@ -3,15 +3,42 @@ </head><body> <h3>Replacing the BibTeX–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 many -reports of progress (on many projects), over the years, yet few -announcements of packages we can use. (There are probably usable -packages out there, but none that I know of.) -<p/>Two interesting 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’s -support. +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. +<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’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). +<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’t (yet) appeared. +<p/>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. +<p/>Of the direct BibTeX replacements, the only one whose authors have +sufficient confidence to submit to CTAN is CrossTeX. +CrossTeX’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. +<p/>CrossTeX’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’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 @@ -36,6 +63,7 @@ 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/> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html index 4bdbce06271..6e2fc9e212b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html @@ -3,8 +3,8 @@ </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 +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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html index 076487e64fb..4d2b65ca6cc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html @@ -1,7 +1,8 @@ <head> <title>UK TeX FAQ -- question label bibtranscinit</title> </head><body> -<h3>Transcribed initials in BibTeX</h3> +<h3>‘Multi-letter’ 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: @@ -48,8 +49,43 @@ does nothing: } </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. -<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> +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/>“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: +<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’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’re typing the names in the “natural” (Western) way, +with given names first, the trick: +<blockquote> +<pre> +... + author = {P.M. {\relax de F.} Forster and +... +</pre> +</blockquote><p> +doesn’t work — “de F. Forster” 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-doc/doc/english/FAQ-en/html/FAQ-braket.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html index 7d05cc3c7ca..a43bde32fba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html @@ -8,8 +8,8 @@ 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>\left( <expression> \right)</code> — the size of the parentheses is -matched to the vertical extent of the expression. +<code>\</code><code>left(</code><code> <expression> </code><code>\</code><code>right)</code> — 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html index cbc8bcdb45a..68d98f6654e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html @@ -4,9 +4,9 @@ <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 (“<code>\</code>”, -“<code>/</code>” and “<code>X</code>”), and a means of cancelling ‘to’ a particular -value. +package provides several variants of cancellation marks +(“<code>\</code>”, “<code>/</code>” and “<code>X</code>”), and +a means of cancelling ‘to’ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html index 1c0915f7768..c7a89b8a53a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html @@ -50,7 +50,7 @@ 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 — to produce a document that embodies both “old” and “new” versions. -<p/>To this end, he package <i>changes</i> allows the user to manually +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html index 73bf3701572..18c0bec481d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html @@ -36,14 +36,15 @@ environment (which is a close relation of the LaTeX <code>quote</code> environment) <em>doesn’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>chngpage</i> package provides ready-built commands to do the +<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’re on an odd or an even page of a -two-sided document. The package’s documentation (in the file itself) -suggests a strategy for changing text dimensions between pages — as -mentioned above, changing the text dimensions within the body of a -page may lead to unpredictable results. -<p/>Changing the vertical dimensions of a page is clunkier still: the +text according to whether you’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>’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> @@ -59,6 +60,7 @@ to make the page one line longer, or </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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html index 911b74604f7..ebe82a177d8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html @@ -4,7 +4,7 @@ <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 beconsidering developing one such for use +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html index a734782fae6..4ec9f46961d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html @@ -75,7 +75,7 @@ program (implicitly) claims to be “self-documenting”. <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/nonfree/support/lgrind.zip">nonfree/support/lgrind</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/support/lgrind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/lgrind/">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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html index b76b84ca806..cba1c195363 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html @@ -6,19 +6,19 @@ 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. -<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’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 <em>today’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): +<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’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 <em>today’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 +use \verb+\iftrue+ -- a surprise \fi </pre> </blockquote><p> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html index 0483d24f15c..8c4bc8f9ae9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html @@ -35,7 +35,7 @@ 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/misc/ziffer.sty">macros/latex/contrib/misc/ziffer.sty</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-doc/doc/english/FAQ-en/html/FAQ-destable.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html index df8a05647fc..53ed96568b7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html @@ -58,7 +58,8 @@ with an option that has the same effect: </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: +value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (default value +<code>0pt</code>), so: <blockquote> <pre> \begin{table} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html index 5c1c9bfffad..3c4ccb76671 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html @@ -3,7 +3,7 @@ </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 -analagous to those that derive from the TeX primitive maths +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’s inline maths grouping, diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html index 1f4478df3b8..5cd801f9013 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html @@ -18,25 +18,25 @@ of drawing, and setup, here are a few systems you may consider: useful tool than the original environment has ever been. (Note that <i>pict2e</i> supersedes David Carlisle’s stop-gap <i>pspicture</i>.) -<li> <i>pstricks</i>; this gives you access to all the power of +<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, this means there are many - astounding things that can in principle be achieved. + pretty powerful programming language, many astounding things can in + principle be achieved using <i>PSTricks</i>. <i>pstricks</i>’ <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>pdftricks</i>, which (like + users may use <i>pst-pdf</i>, which (like <i>epstopdf</i> — see <a href="FAQ-pdftexgraphics.html">PDFLaTeX graphics</a>) generates - PDF files on the fly from <i>pstricks</i> commands. The - documentation is good (you may browse it via the - <a href="http://pstricks.tug.org/"><i>pstricks</a> page</i> - on the TUG web site). There is also a mailing list + 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>. + 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 @@ -65,8 +65,9 @@ of drawing, and setup, here are a few systems you may consider: <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>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>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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html index e22c17504e6..cbbed32fbb1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html @@ -22,9 +22,7 @@ sections, and there are facilities for indexes of macros, etc. 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 -Matt Swift’s <i>swiftex</i> system: it provides a -<code>doc-tex</code> mode which treats <code>.dtx</code> files rather -better than <a href="FAQ-editors.html">AUC-TeX</a> manages. +<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 @@ -39,8 +37,9 @@ 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>, +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> @@ -49,7 +48,6 @@ Metafont and MetaPost together with related LaTeX code. <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>) -<dt><tt><i>swiftex.el</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/emacs-modes/swiftex.zip">support/emacs-modes/swiftex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/emacs-modes/swiftex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/emacs-modes/swiftex/">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-doc/doc/english/FAQ-en/html/FAQ-dvi.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html index f07f1ccd244..7539268ba10 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html @@ -22,7 +22,7 @@ possibly material to be introduced by means of source of Knuth’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/texware/dvitype.web">systems/knuth/texware/dvitype.web</a> +<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-doc/doc/english/FAQ-en/html/FAQ-dvips.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html index d433daecc2a..b64722780eb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html @@ -6,7 +6,7 @@ runs under many operating systems, is Tom Rokicki’s <i>dvips</i>. <i>dvips</i> is written in C and ports easily. All current development is in the context of Karl Berry’s <i>kpathsea</i> -library, and sources are available from the TeX-live repository, +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html index 3c0bc61364e..19140f647be 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html @@ -18,16 +18,19 @@ level 2 or higher). (<i>Unix</i> users should beware of <i>xv</i>’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) and +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 +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 “good bets”. <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>’s conversion library. <i>Dvips</i>, as -distributed by MiKTeX, comes with those patches built-in. +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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html index 79f1400d62d..14e4e09b747 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html @@ -5,10 +5,11 @@ <p/>Robust LaTeX commands are either “naturally robust” — meaning that they never need <code>\</code><code>protect</code>, or “self-protected” — meaning that they have <code>\</code><code>protect</code> built in to their definition in some -way. Self-protected commands are robust only 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’t handle <code>\</code><code>protect</code> properly, since -<code>\</code><code>edef</code> is a TeX primitive rather than a LaTeX command. +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’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’s a corresponding diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html index 18f4c49733f..e9e01c97566 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html @@ -52,7 +52,10 @@ personal selection: 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. + 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 + “next-generation” (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. @@ -60,8 +63,9 @@ personal selection: 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. -<p/> For MacOS X users, the tool of choice appears to be + 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 @@ -87,7 +91,7 @@ access to your BibTeX files — <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="ftp://cam.ctan.org/tex-archive/systems/win32/winedt/winedt32.exe">systems/win32/winedt/winedt32.exe</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-doc/doc/english/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html index 1a2720a3b15..4bbeb620fe9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html @@ -16,8 +16,9 @@ and you’ll get the diagnostic. <p/>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 <code>emacs</code> and <i>winedt</i> offer this facility). -However, groups are not <em>only</em> created by matching <code>{</code> with <code>}</code>: +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{<<i>environment</i>>}</code> encloses the environment’s body diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html index cf7d29a3f68..b893df4e722 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html @@ -29,7 +29,7 @@ correct: \end{tabular} </pre> </blockquote><p> -produces the error at the bsbs. This usage is just wrong; if you +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 “by hand”: <blockquote> <pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html index 49ec4c33a05..cc73f99bb87 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html @@ -17,7 +17,7 @@ active. a set of extensions that can be used with a (“true”) 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 system (for +are delivered with most formats built with an e-TeX-based system (for those who don’t want them, e-TeX’s extensions can be disabled, leaving a functionally standard TeX system). <p/>The extensions range from the seemingly simple (increasing the number diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html index 78c2fd342d3..353ecc6f12f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html @@ -10,7 +10,7 @@ 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). -<p/>The TS1-encoded fonts provided as part of the EC font +<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 @@ -33,7 +33,7 @@ change. (free) from <a href="ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe">Adobe</a> — the file is packaged as a <i>Windows</i> self-extracting -executable, but it may be decoded as a <code>.zip</code> format achive +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html index 5d151d09186..8573b218546 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html @@ -10,7 +10,7 @@ Encapsulated PostScript and PDF, as well as combinations that wrap a graphics format in a LaTeX import file. <p/>There’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 +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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html index 440367ae596..3937df6fbcc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html @@ -15,8 +15,8 @@ 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 — 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. +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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html index dac5bec453a..929facbf9f2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html @@ -18,7 +18,7 @@ list of files (<i>FILES.byname</i> — 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">USA</a> CTANs offer a +<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’s (above); diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html index c71a2416792..d62c6f8a162 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html @@ -26,7 +26,7 @@ use a different mechanism: be sure to check <a href="FAQ-latexwords.html">changing <i>babel</i> names</a> if you’re using it.) <p/>The names that are defined in the standard LaTeX classes (and the -<i>makeidex</i> package) are listed +<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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html index 44d4bc41ac1..f72016b2eb1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html @@ -9,8 +9,8 @@ can stretch particular cells in the table. environment takes an extra argument (before the <code>clpr</code> layout one) which takes a length specification: you can say things like “<code>15cm</code>” or “<code>\</code><code>columnwidth</code>” 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 +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> @@ -19,15 +19,16 @@ The <code>\</code><code>extracolsep</code> applies to all inter-column gaps to i well; if you don’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’s more than one <code>X</code> column in a -table, the spare space is distributed between them. +specification, <code>X</code>; <code>X</code> columns behave as <code>p</code> +columns which expand to fill the space available. If there’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 “balancing” 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 “naturally” (i.e., on a piece of paper of unlimited width), and +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 “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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html index 2a12c789b0b..79c7a8812ec 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html @@ -7,17 +7,17 @@ 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 -<pre> - \begin{figure}[p!] -</pre> +<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’t solve the one-float-per-page question. -<p/>The ‘obvious’ solution, using the counter <code>totalnumber</code> (“total -number of floats per page”) doesn’t work: -<code>totalnumber</code> only applies to floats on ‘text’ pages (pages containing -text as well as one or more float). So, to allow any +<p/>The ‘obvious’ solution, using the counter <code>totalnumber</code> +(“total number of floats per page”) doesn’t work: +<code>totalnumber</code> 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 <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: @@ -29,5 +29,5 @@ the separation between floats really big: \makeatother </pre> </blockquote><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> +<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-doc/doc/english/FAQ-en/html/FAQ-floats.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html index a11a06cb088..118069a5b39 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html @@ -12,8 +12,7 @@ printed ‘here’ if doing so would break the rules; the rules themselv 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 -<a href="FAQ-tmupfl.html">“Too many unprocessed floats”</a>. +saying <a href="FAQ-tmupfl.html">“Too many unprocessed floats”</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 “non-standard” floats defined by the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html index bef0c5e7501..9627e742196 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html @@ -20,9 +20,9 @@ restores flush justification at both margins: There’s a problem with the setting of <code>\</code><code>parindent</code> in the code: it’s necessary because both the <code>\</code><code>ragged</code> commands set <code>\</code><code>parindent</code> to zero, but the setting isn’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’s no knowing what you (or some other class) will -have done. +standard LaTeX class with <code>twocolumn</code> option will have +<code>1.0em</code> by default, and there’s no knowing what you (or some +other class) will have done. <p/>Any but a really old copy of Martin Schröder’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 ‘ragged’ commands</a>. The diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html index 6d25578742e..347f62ff2ff 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html @@ -19,25 +19,11 @@ -<p/><dt>WordPerfect<dd> <i>wp2latex</i> - has recently been much improved, and is now - available either for MSDOS or for Unix systems, thanks to its - current maintainer Jaroslav Fojtik. -<dt>PC-Write<dd><i>pcwritex.arc</i> is a - print driver for PC-Write that “prints” 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. -<dt>runoff<dd> Peter Vanroose’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. +<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’s Rich Text Format to TeX. There is also a - convertor to LaTeX by Erwin Wechtl, called <i>rtf2latex</i>. + 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. @@ -53,17 +39,32 @@ shareware translators from <a href="http://www.chikrii.com/">Chikrii Softlab</a>; users’ 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/> Another, unlikely, intermediate form is PDF: Acrobat Reader +<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’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 “prints” 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’ FAQ</a>, diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html index 072bd278a78..da8f8a82f2b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html @@ -31,12 +31,12 @@ Text set using nonstdfont italic... 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’t come in versions using Knuth’s -eccentric font encodings — 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 “font -selection scheme” — this ‘NFSS’ (‘N’ for ‘new’, as -opposed to what LaTeX 2.09 had) carries around with it separate -information about the fonts you use, so the changes to +eccentric font encodings — 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 +“font selection scheme” — this ‘NFSS’ (‘N’ for +‘new’, 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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html index 12c4bd7e3be..b5cf890a453 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html @@ -33,16 +33,19 @@ things you can do to fix the problem. tools distribution; they’re noticeably less efficient than the standard <code>tabular</code> environment, but they do allow footnotes. -<li> Grab hold of <i>footnote</i>, and put your - <code>tabular</code> environment inside a <code>savenotes</code> - environment. Alternatively, say +<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 handle footnotes correctly. + 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. It may also cause other table-related packages (not - the standard ‘tools’ ones, though) to become very unhappy and stop - working. + of your tables. Unfortunately, it may be incompatible with other + table-related packages, though not those in the standard ‘tools’ + 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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html index 9e16888977f..160a51f0534 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html @@ -8,26 +8,27 @@ page number is stepped, using the 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. -<p/>As a result, resetting footnotes is inevitably a two-pass process, +<p/>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. -<p/>The <i>footnpag</i> package does per-page footnotes and nothing -else. <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>. +list), you can use: <code>\</code><code>MakePerPage[2]{footnote}</code>. It’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. -<p/>Documentation of <i>footnpag</i> comes as a DVI file -<i>footnpag-user</i> in the distribution. Documentation of -<i>perpage</i> appears in the package file, only: however, it -amounts to no more than appears above... +<code>perpage</code> 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. +<p/>The <i>footnpag</i> package also does per-page footnotes (and +nothing else). With the competition from <i>perpage</i>, it’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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html index b014c32a9ba..5461d389a4b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html @@ -16,7 +16,8 @@ of contents, so the footnote may only appear in the section heading itself. <ul> <li> Take advantage of the fact that the mandatory argument doesn’t ‘move’ if the optional argument is present: -<p/> <code>\section[title]{title</code><code>\</code><code>footnote{title ftnt}</code><code>}</code> +<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> — this modifies footnotes so that they softly and silently vanish away if used in a moving argument. With this, you diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html index 1de7abe52c5..dac8d715163 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html @@ -22,7 +22,7 @@ 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 +(distributed with TeX Live, at least; otherwise such a person should consult “<a href="FAQ-useMF.html">the use of Metafont</a>)”. <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html index 305e3615654..eaa0377987e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html @@ -15,7 +15,7 @@ CTAN Catalogue can also help: you can “<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">by topic</a>”. 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 directoris now include documentation, so it’s +CTAN package directories now include documentation, so it’s often worth looking at the catalogue entry for a package you’re considering using. <p/>Failing all that, look to see if anyone else has had the problem diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html index 918039bbbe6..a2da4df0c21 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html @@ -22,7 +22,14 @@ down. 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. +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html index 310ef48b1ff..2f7959add31 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html @@ -39,7 +39,7 @@ 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’re doing (for example, a distribution that provides both LaTeX and PDFLaTeX -will usually provide a configuration file that determins whether +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html index a6f329ef344..2cccad6434f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html @@ -2,13 +2,11 @@ <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 +<p/>LaTeX, though originally <a href="FAQ-LaTeXandPlain.html">based on Plain TeX</a>, does not contain all of Plain TeX’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. +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’s semantics. However, this is not practical in many circumstances, and for those occasions, the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex*.html index 17e7df91632..7ffb88aba90 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex*.html @@ -1,13 +1,19 @@ <head> -<title>UK TeX FAQ -- question label inst-miktex</title> +<title>UK TeX FAQ -- question label inst-miktex*</title> </head><body> -<h3>Installing MiKTeX “known packages”</h3> -<p/>MiKTeX 2.1 (and later) maintains a database of packages it “knows about”, +<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 “knows about”, together with (coded) installation instructions that enable it to -install the packages with minimal user intervention. +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’s worth -using the system. -<p/>First, open the MiKTeX packages window: click on +using the system: +first, open the MiKTeX packages window: click on <code>Start</code>-> <code>Programs</code>-> <code>MiKTeX</code>-> @@ -28,14 +34,5 @@ mpm --install=<package> </blockquote><p> (which of course assumes you know the name by which MiKTeX refers to your package). -<p/>If MiKTeX <em>doesn’t</em> know about the package you’re interested -in, you have to use the <a href="FAQ-installthings.html">long-winded procedure</a> -outlined above. -<p/>If necessary, repeat to select other packages, and then press -“<code>OK</code>”; MiKTeX tells you how many packages you have -selected — if you’re happy, press “<code>OK</code>” again. -MiKTeX will go off, download the package (as a -<code>.cab</code> file), if necessary, install the files of the package, and then -refresh the filename database so that the files will be found. -<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> +<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-doc/doc/english/FAQ-en/html/FAQ-inst-scut.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-scut.html new file mode 100644 index 00000000000..92e5237582e --- /dev/null +++ b/Master/texmf-doc/doc/english/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-miktex*.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-doc/doc/english/FAQ-en/html/FAQ-inst-tds-zip.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-tds-zip.html new file mode 100644 index 00000000000..b5317c52051 --- /dev/null +++ b/Master/texmf-doc/doc/english/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 (“traditionally”) 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’s to be installed for a given +package, in their “correct” 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’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’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 — 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’s map, +which is discussed in +“<a href="FAQ-instt1font.html">Installing a Type 1 font</a>” +<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-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html index ec1eb84f888..2303718154d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label inst-wlcf</title> </head><body> <h3>Installing files “where (La)TeX can find them”</h3> -<p/>In the past, package documentation used always to tell you to put your +<p/><p/>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 <em>was</em>, you didn’t need telling, but if you <em>didn’t</em> know, you were completely stuck. @@ -30,12 +30,13 @@ and click on <code>Refresh FNDB</code>. The job may also be done in a command window, using the command: <blockquote> <pre> -initexmf -u +initexmf --update-fndb </pre> </blockquote><p> -See the MiKTeX documentation for further details about -<code>initexmf</code>. -<p/>On a teTeX or TeX-live-based system, use the command +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’s not available, <code>mktexlsr</code> — they ought to be different names for the same program). <p/>Having done all this, the new package will be available for use. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html index 3a18c4217fd..468e2e503e7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html @@ -35,7 +35,7 @@ and PFM — 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. +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html index b13fa3a39e8..b0248ad8f6e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html @@ -20,8 +20,9 @@ source mechanism was first discussed, the <i>.drv</i> mechanism was suggested, but it’s not widely used nowadays). <p/>Sometimes, the LaTeX run will complain that it can’t find <i>package.ind</i> (the code line index) and/or <i>package.gls</i> -(the list of change records). Both types of file are processed with -special <i>makeindex</i> style files; appropriate commands are: +(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 @@ -30,11 +31,12 @@ makeindex -s gglo -o package.gls package.glo </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’re part of the package development team. -<p/>Another common (and reasonable) trick 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’t help, simply look around for alternatives. -Such files are treated in the same way as any “ordinary” LaTeX -file. +valuable if you’re part of the package development team. If you don’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’t help, simply +look around for such alternatives. The files are treated in the same +way as any “ordinary” 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-doc/doc/english/FAQ-en/html/FAQ-install-find.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html index 76463c0aa74..cf04c651947 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label install-find</title> </head><body> <h3>Finding packages to install</h3> -<p/>How did you find about the package? -<p/>If you learned about your package in these FAQs, you should -already have a link to the file: +<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. @@ -14,18 +14,22 @@ facilities, such as <a href="http://www.tex.ac.uk/search/">http://www.tex.ac.uk/ 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/>Remember that you may want <i>foo.sty</i> but that file is distributed -in a LaTeX documented source file <i>foo.dtx</i>; it’s usually best -to search just for <em>foo</em> — <i>foo.sty</i> won’t be visible -anywhere on the archive or in the catalogue. <p/>Packages come in a variety of different styles of distribution; the -very simplest will offer just <i>package.sty</i> — in this case, -just download the file and +very simplest will actually offer just <i>package.sty</i> — in this +case, just download the file and <a href="FAQ-inst-wlcf.html">get on with installation</a>. -<p/>However, most packages occupy their own directory on the archive; in -this case, you should download the whole directory -<p/>Having acquired the package distribution, see -“<a href="FAQ-install-unpack.html">unpacking LaTeX packages</a>” for your -next step. +<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> — <i>foo.sty</i> won’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, +“<a href="FAQ-install-unpack.html">unpacking LaTeX packages</a>” 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-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html index 69ae2b4d7c6..600d4b8d617 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html @@ -10,13 +10,14 @@ 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 <i>.dtx</i> files, but -fewer (often only one) <i>.ins</i> files (LaTeX itself comes -looking like this). The way to go, in this case is simply to process -the <i>.ins</i> file(s) one by one. +<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’re missing the <i>package.ins</i> altogether, you need to play -around until something works. Some <i>.dtx</i> files are -“self-extracting” — they do without a <i>.ins</i> file, and once +around until something works. Some <code>.dtx</code> files are +“self-extracting” — they do without an <code>.ins</code> file, and once you’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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html index 0764f0a5450..42ec4dd1199 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html @@ -2,23 +2,17 @@ <title>UK TeX FAQ -- question label install-where</title> </head><body> <h3>Where to install packages</h3> -<p/>Where precisely you put files that you have downloaded depends on -what TeX distribution you have. We will assume that you have one -of the modern TDS-compliant distributions, and discuss the -general rules that you should follow. -<p/>First, you must decide which tree to put your files into; this isn’t -entirely trivial, and is discussed in -“<a href="FAQ-what-TDS.html">choosing a TDS tree</a>”. -<p/>We’ll assume from here on, that you’ve decided on a directory tree, -and we will write <code>$TEXMF</code> for it, whatever it is for your -system. +<p/>We assume here that you have decided what tree to put your files in, +after reading +“<a href="FAQ-what-TDS.html">choosing a TDS tree</a>”. 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/latex/<package>/ -.dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/ +.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>/ @@ -39,16 +33,28 @@ v1.1 layouts): </blockquote><p> (Map and encoding files went to directories under <i>$TEXMF/dvips/</i>, in earlier distributions.) -<p/>In the lists above, <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend -upon what’s appropriate for the individual file — the supplier -“public” is commonly used for free fonts. The <<i>syntax</i>> -(for <code>.map</code> and <code>.enc</code> files) is a categorisation based -on the way the files are written; typically, it’s the name of a -program such as <i>dvips</i> or <i>pdftex</i>. -<p/>“Straight” (La)TeX input can take other forms than the <code>.sty</code>, -<code>.cls</code> or <code>.fd</code> listed above, too. Examples are -<code>.sto</code> and <code>.clo</code> for package and class options, -<code>.cfg</code> for configuration information, and so on. +<p/>In the lists above <<i>format</i>> identifies the format the macros +are designed for — 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, <<i>font</i>> refers to the font family (such as <code>cm</code> +for Knuth’s Computer Modern, <code>times</code> for Adobe’s Times Roman). +The supplier is usually obvious — the supplier +“public” is commonly used for free fonts. +<p/>The <<i>syntax</i>> (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/>“Straight” (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 ‘obvious’ <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’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 <<i>font</i>> 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 <code>.../public/cm</code>, with various prefixes as appropriate. @@ -56,12 +62,10 @@ found in <code>.../public/cm</code>, with various prefixes as appropriate. “free fonts produced for use with (La)TeX”: as well as Knuth’s fonts, <em>public</em>’s directory holds fonts designed by others (originally, but no longer exclusively, in Metafont). -<p/>Some packages have configuration files (commonly with file suffix -<code>.cfg</code>), and occasionally other run-time files. The package -documentation <em>should</em> mention these things, but sometimes -doesn’t. An exception is the <code>.drv</code> file, used by some -packages as part of the documentation building process; this is -usually part of the package documentation process, and should not be -installed. +<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-doc/doc/english/FAQ-en/html/FAQ-installthings.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html index 6c15565106b..4daeacdbfd9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label installthings</title> </head><body> <h3>Installing things on a (La)TeX system</h3> -<p/>Installing (or replacing) things on your (La)TeX system has the +<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’ve decided what it is that you want to install: @@ -10,7 +10,7 @@ decided what it is that you want to install: <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’s probably a good idea to +<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>; diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html index 83604ccd16b..325dc388bff 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html @@ -6,7 +6,7 @@ pleasingly simple. Nowadays, they are mostly distributed just as the Metafont source, since modern TeX distributions are able to produce everything the user needs “on the fly”; however, if the distribution -<em>does</em> include TFM files, do install them, too, since they +<em>does</em> include TFM files, install them too, since they save a little time and don’t occupy much disc space. Always distrust distributions of PK font bitmap files: there’s no way of learning from them what printer they were generated for, and naming diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html index 2ac895a9bef..34d170f7891 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html @@ -25,14 +25,17 @@ All these fonts are supported, for LaTeX users, by the <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> and -<i>Palatino</i>, as -well as a more reliable set of font metrics. +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 “unzipping” 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html index 042ba93b39b..06e84384215 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html @@ -2,90 +2,70 @@ <title>UK TeX FAQ -- question label instt1font</title> </head><body> <h3>Installing 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 stages. +<p/>Once you have a prepared Type 1 font, either direct from CTAN +or the like, or having <a href="FAQ-prept1font.html">‘prepared’ 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> 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’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’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’ 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 the documentation for details. -<p/> <i>Fontinst</i> also generates map files, and LaTeX font - definition (<code>.fd</code>) files. <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 whose Berry - name is <<i>bname</i>>: - + destinations for the various files related to a font family <<i>fname</i>>: <pre> .pfb, -.pfa .../fonts/type1/<foundry>/<bname> -.tfm .../fonts/tfm/<foundry>/<bname> -.vf .../fonts/vf/<foundry>/<bname> -.fd .../tex/latex/fontinst/<foundry>/<bname> -</pre> - The irregular things being <code>.map</code> files: in teTeX 3.0 and - later, these should be placed according to the revised TDS as -<pre> +.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> </pre> -and in other (earlier) systems as -<pre> -.map .../dvips/fontinst/<foundry> -</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> and other maps: +<li> Update the <i>dvips</i>, PDFTeX and other maps: <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 + <li> On any current TeX Live-based system, or a teTeX v3.0 + system, execute the command + <blockquote> +<pre> +updmap-sys --enable Map <fname>.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 <fname>.map +</pre> + </blockquote><p> + for each font family <<i>fname</i>> you are adding to the system. + Now generate revised maps with the shell command + <blockquote> <pre> - updmap --enable Map <xyz>.map +initexmf --mkmaps </pre> - <li> 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 “PostScript resources database”. - <li> On a MiKTeX system, version 2.2 or later, update - <i>updmap.cfg</i> which is described in 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. + </blockquote><p> + This, and other matters, are described in MiKTeX + <a href="http://docs.miktex.org/manual/advanced.html">”advanced” documentation</a>. </ul> </ul> -The whole process is very well (and thoroughly) described in Philipp -Lehman’s guide to font installation, which may be found on CTAN. +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 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html index 820715ebb60..2c0757af447 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html @@ -17,14 +17,17 @@ the system to replace the original (“<code>PS</code>”) 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. -(Unfortunately, <i>psfrag</i> can’t be used with PDFLaTeX, -though one might hope that it would be susceptible to the same sort of -treatment as is used in the <i>pdftricks</i> package. On the other -hand, +<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>’s GeX processor explicitly deals with <i>psfrag</i>, both in its free and -commercial instances.) +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 @@ -57,12 +60,14 @@ environment which itself includes the graphic. I would recommend 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html index 78840e4638e..a13f693fe96 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html @@ -23,7 +23,7 @@ Package nag Warning: Command \bf is an old LaTeX 2.09 command. <p/>There’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 (unfortuantely, you +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 <i>nag</i>, but it allows you to download its script, which you can then juggle with to make it more diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html index 8df126797e0..3daf4d5a2fa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html @@ -12,8 +12,8 @@ of vertically-shifting a single-page letter, try the following hack: \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 +<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 — in fact there are an awfully large number of them: the following list, of diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html index c429fb7ee9e..d20e191d767 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html @@ -26,17 +26,18 @@ Plain TeX). 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 <i>soul</i>; the other half is described in <a href="FAQ-underline.html">another question</a>.) -<p/>Possibly the ‘ultimate’ in this field is the <i>letterspace</i>, -which uses the micro-typography capabilities of current PDFTeX. -<i>Letterspace</i> expands the natural spacing font itself, rather +<p/>Possibly the ‘ultimate’ 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>’s +‘tracking’ 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. <i>Letterspace</i> provides a means of -protecting the ligatures in a letter-spaced text. +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>letterspace.sty</i></tt><dd>Distributed as part of the <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>) - bundle +<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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html index fabb6d164aa..a749efd9b5c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html @@ -7,7 +7,7 @@ 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. <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’t force the whole aligment +which is slightly tedious to set up, but which doesn’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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html index ad6ba02ce6a..bd8af31be3b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html @@ -6,7 +6,9 @@ <a href="FAQ-whatpdftex.html">PDFTeX</a> 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. +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 @@ -19,5 +21,8 @@ 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-doc/doc/english/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html index afd067857f7..2840ad9104c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html @@ -32,7 +32,7 @@ well. <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’s -<a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/novices.html">LaTeX for complete novices</a> +<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’s <a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/">introductory tutorials</a>, diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html index 47a3f431d65..2746486f12f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html @@ -2,7 +2,7 @@ <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 “analagous” places on +<p/>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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html index aa9979a8592..39bdeb00df9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html @@ -33,7 +33,7 @@ support for new Web standards. 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 represention of mathematics<dd> +<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 @@ -41,7 +41,7 @@ support for new Web standards. Browser support for MathML is provided by <i>amaya</i>, the ‘Open Source’ 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 plugin + <i>Internet Explorer</i> when equipped with a suitable plug-in such as <i>MathPlayer</i>. There’s evidence that (La)TeX users are starting to use such browsers. Some believe that XHTML+MathML now provides diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html index 195ab584490..75e9c7b1b0f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html @@ -16,7 +16,7 @@ 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 occurrs. (It may prove difficult to find the actual +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 <a href="FAQ-errstruct.html">“the structure of TeX errors”</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misssymb.html index f8c2d6be169..24165ca886b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misssymb.html @@ -1,5 +1,5 @@ <head> -<title>UK TeX FAQ -- question label missssymb</title> +<title>UK TeX FAQ -- question label misssymb</title> </head><body> <h3>Missing symbol commands</h3> <p/>You’re processing an old document, and some symbol commands such as @@ -13,5 +13,5 @@ symbol fonts). <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=missssymb">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missssymb</a> +<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-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html index e6e58665fd5..848e6932446 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html @@ -8,7 +8,7 @@ defined — for example, as a figure in TeX document. If you’re debugging your MetaPost code, you may want to view it in <i>ghostscript</i> (or some other PostScript previewer). However, the PostScript ‘engine’ in <i>ghostscript</i> <em>doesn’t</em> -ordinarily have the fonts loaded, and you’ll eperience an error such +ordinarily have the fonts loaded, and you’ll experience an error such as <blockquote> <pre> @@ -25,7 +25,7 @@ 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’ metapost output after processing through +to view the ‘original’ 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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html index 6c92ec94c7e..c6ab8fb6c7f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html @@ -25,5 +25,6 @@ of <a href="FAQ-virtualfonts.html">virtual fonts</a> to map the old to the new s <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-doc/doc/english/FAQ-en/html/FAQ-multbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html index 9ea0e52d624..1105a43ecc9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html @@ -118,8 +118,8 @@ bibtex diss2 <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>miltibbl</i> and -<i>mltibib</i> is that selection of what appears in each +<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’s in the <code>.bib</code> files. <p/>An entirely different approach is taken by the <i>splitbib</i> @@ -127,7 +127,7 @@ 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>thebibliograph</code> environment it +(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 “misc” category created in the sorting process.) A code example appears in the package documentation diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html index 297fa5858c8..035348f0359 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html @@ -70,7 +70,7 @@ texconfig hyphen latex <p/> or get a DOS window and run:<br> <code>initexmf --dump</code> -<p/> On a <i>MiKTeX</i> distribtution v2.0 or later, the whole +<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>-> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html index fe6805b81cd..4c0b9128d29 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html @@ -10,7 +10,7 @@ TeX (and by inheritance, LaTeX too) will say </pre> as if you couldn’t possibly have misunderstood the import of what you were typing, and the only possible interpretation is that you had -commited a typo in failing to enter maths mode. TeX, therefore, +committed a typo in failing to enter maths mode. TeX, therefore, tries to patch things up by inserting the <code>$</code> you ‘forgot’, so that the maths-only object will work; as often as not this will land you in further confusion. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html index 4363e53a8c9..cd7e610c6c2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html @@ -62,11 +62,11 @@ in the environment: \end{center} </pre> </blockquote><p> -The solution here is plain: use the <code>\</code><code>\</code> command in the way it’s +The solution here is plain: use the <code>\\</code> command in the way it’s supposed to be used, to provide more than just a single line break -space. <code>\</code><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: +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} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html index 2916264f930..714fe06c855 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html @@ -13,7 +13,7 @@ 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 -exaple is list items — they suggest page breaks between them. Even +example is list items — they suggest page breaks between them. Even if <code>samepage</code> <em>does</em> work, it’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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html index 5ad4bc7e7d4..2640db821fe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html @@ -22,20 +22,25 @@ the course of the output routine, and is therefore safe. 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>chngpage</i> package needs to provide this functionality for +<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>ifcpoddpage</code> true if the command was issued on an odd page. The +<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’s “Rerun to get cross-references right” 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’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’s supporting command is <code>\</code><code>ifthispageodd{<true>}{<false>}</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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html index 52b45d9bb96..84a65fde319 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html @@ -11,8 +11,8 @@ beginner’s tutorial but it’s a fine reference. <p/>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 GNU general documentation -licence, and it is available from CTAN. +have re-released the book under the GNU Free Documentation +Licence, and it is available from CTAN. <p/>Norm Walsh’s “Making TeX Work” (originally published by O’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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html index acd67d35d03..99f87bc3b2d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html @@ -4,50 +4,56 @@ <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} +\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’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} - } +\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} % full width abstract - ... text + \begin{onecolabstract} % ditto abstract + ... text \end{onecolabstract} ] -\saythanks % typeset any \thanks +\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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papergeom.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papergeom.html new file mode 100644 index 00000000000..d02dc4cbce4 --- /dev/null +++ b/Master/texmf-doc/doc/english/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’ve checked that it’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’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 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. +<p/>In practice, one usually finds that macro packages (such as Plain TeX and +LaTeX) assume American “letter” paper size, by default; and since +most distributions nowadays originate in Europe, the drivers usually +default to ISO “A4” 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’t provide for people using the “wrong” sort of paper for some +reason. +<p/>A different issue arises for users of PDFTeX — 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 “in the output”. +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 — <i>geometry</i> knows about <code>dvips</code> and +<code>dvipdfm</code>), and the document will run correctly with +LaTeX. If you’re using PDFLaTeX, load with +<blockquote> +<pre> +\usepackage[pdftex,...]{geometry} +</pre> +</blockquote><p> +<p/>Needless to say, both the “big” classes (<i>koma-script</i> and +<i>memoir</i>) provide their own ways to get the paper size +“right”. +<p/>The <i>typearea</i> package is the <i>Koma-script</i> +distribution’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’ 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-doc/doc/english/FAQ-en/html/FAQ-papersize.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html index 356866d8651..ab1fcabda32 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html @@ -1,77 +1,34 @@ <head> <title>UK TeX FAQ -- question label papersize</title> </head><body> -<h3>Printer paper sizes</h3> -<p/>If you’re looking at this answer, it’s likely you have a problem with -fitting output to the page. It may be a common problem with Adobe -<i>[Acrobat] Reader</i>: printing from that program -<em>by default</em> shrinks the page ”to fit”. Unfortunately, its -calculation doesn’t take the existing margins of the document into -account, 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>’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: ”Fit to printer margins”) — change to - ”None”, and<br> - Scale (default 95\ -</blockquote><p> -<p/>More generally, we should recognise that paper sizes can be a pain: -they’re a forgotten backwater, because -there’s no DVI command to specify the paper size of the -document. One usually finds American “letter” paper size being -assumed, by default, in macro packages (such as <i>plain</i> TeX and -LaTeX); but distributions provide separate configuration files for -DVI drivers. Since most distributions nowadays originate in -Europe, the drivers usually default to ISO “A4” paper size. -<p/>This is (of course) pretty unsatisfactory. Users may change the paper -size their document is designed for, pretty easily (and once off), but -they have to ensure that every run of <i>xdvi</i>, -<i>dvips</i>, or whatever, is given the correct override for using -anything non-‘standard’. -<p/>Furthermore, the default paper size for DVI drivers may be -changed by a distribution management command, but this still doesn’t -provide for people using the “wrong” sort of paper for some reason. -<p/>An interestingly different issue arises for users of PDFTeX — the -PDF format <em>does</em> have the means of expressing paper size, -but much of the core software predates PDFTeX, so not even -PDFLaTeX sets the correct values into <code>\</code><code>pdfpagewidth</code> and -<code>\</code><code>pdfpageheight</code>. -<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 in the case of PDFTeX and VTeX, 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 of the paper size the document -is going to print to, and can issue the commands necessary to ensure -the correct size is used. If <i>geometry</i> is used when a -document is being processed by either PDFLaTeX or VTeX, it can -set the necessary dimensions ”in the output”. If the document -is being processed by LaTeX on a TeX or e-TeX engine, there -are two package options (<code>dvipdfm</code> and <code>dvips</code>) -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), and the document will run correctly with any of -LaTeX (whether or not run on VTeX) or PDFLaTeX. -<p/>Give the <i>typearea</i> package the <code>pagesize</code> and it -will do the same job, for PDFLaTeX output and PostScript output from -LaTeX via <i>dvips</i>. +<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 “on-screen”, 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 “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.) +<p/>Sadly, we often find that the printed output doesn’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 “<i>Acrobat Reader</i>” — 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>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>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>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-doc/doc/english/FAQ-en/html/FAQ-parallel.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html index 911075c41be..b84159458b7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html @@ -21,6 +21,10 @@ as simple as \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 — 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>, @@ -49,6 +53,7 @@ the ‘base’ text of the document. <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-doc/doc/english/FAQ-en/html/FAQ-patch.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html index 495b7e0b6da..41ea39fc4c6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html @@ -47,30 +47,51 @@ 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. -<p/>Otherwise, LaTeX users may use one of the <i>patch</i> or -<i>patchcmd</i> systems. -<p/><i>Patch</i> gives you an ingenious (and difficult to understand) -mechanism, and comes as an old-style LaTeX documented macro file. -Sadly the old-style <i>doc</i> macros are no longer available, but -the file (<i>patch.doc</i>) may be input directly, and the -documentation may be read (un-typeset). Roughly speaking, one gives -the command a set of instructions analagous to <i>sed</i> -substitutions, and it regenerates the command thus amended. The -author of this FAQ has (slightly reluctantly) given up using -<i>patch</i>... +<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’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, if -<code>\</code><code>b</code> contains “<code>b</code>”, then -<code>\</code><code>patchcommand</code><code>\</code><code>b{a}{c}</code> -will produce a new version of <code>\</code><code>b</code> that contains “<code>abc</code>”. +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 “<code>abc</code>”. +<p/>The <i>ted</i> package is a ‘token list editor’, 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’s +programming facilities) provides a command <code>\</code><code>patchcmd</code> which will +perform a “string substitution” in a macro’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’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 +“documentation” 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’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-doc/doc/english/FAQ-en/html/FAQ-pk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html index 7beb3103a30..e551d954dc3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html @@ -4,17 +4,14 @@ <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 - -(see <a href="FAQ-tds.html">TDS</a>), -which has provision for all this variety. +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-doc/doc/english/FAQ-en/html/FAQ-pkfix.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html index ddb525c90ce..71fcd491f40 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html @@ -17,22 +17,21 @@ 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/> - - - - - - - - - -Yet another option is Frank Siegert’s (shareware) +<p/>If your source file is older than <i>pkfix</i> can deal with, +there’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 “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. +<p/>A further option is Frank Siegert’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-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html index b37cd7dcb54..31c10e1707f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html @@ -24,8 +24,9 @@ or a PDF reader. 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 -even occasionally generates documentation itself, you will more often -than not find documentation that way. +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’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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html index e82af36e735..d99a905e43c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html @@ -3,13 +3,13 @@ </head><body> <h3>Using Plain or primitive commands in LaTeX</h3> <p/>It’s well-known that LaTeX commands tend to be more complex, and to -run more slowly than, any Plain (or primitive) command that they +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 version. So, for example, use <code>\</code><code>mbox</code> in place of <code>\</code><code>hbox</code> +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 @@ -18,8 +18,8 @@ constructs that cannot be achieved without the use of <code>\</code><code>def</c paragraph if necessary; this isn’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 +in Plain TeX and LaTeX, but behave slightly differently: in +Plain TeX they terminate the current paragraph, but in LaTeX they don’t. The command <code>\</code><code>line</code> is part of picture mode in LaTeX, whereas it’s defined as “<code>\</code><code>hbox</code><code> to </code><code>\</code><code>hsize</code>” in Plain TeX. (There’s no equivalent for users of the Plain TeX command in @@ -37,7 +37,7 @@ in LaTeX, can miss the effect of the class option <code>fleqn</code>. LaTeX. Plain TeX’s font loading command (<code>\</code><code>font</code><code>\</code><code>foo=</code><<i>fontname</i>>) and its LaTeX equivalent (<code>\</code><code>newfont</code>) should be avoided wherever possible. They are only -safe in the most trivial contexts, and aer potential sources of great +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 “<a href="FAQ-newfontstar.html">What’s wrong with <code>\</code><code>newfont</code>?</a>”. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html index 895a9baa746..f94e4158f41 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html @@ -32,16 +32,24 @@ allows you to construct the outline of frames for use with that explain the process (mostly in terms of the <i>a0poster</i> route): <ul> -<li> from Norman Gray, <a href="http://purl.org/nxg/note/posters">http://purl.org/nxg/note/posters</a>; -<li> from “<em>awf</em>” and “<em>capes</em>” - <a href="http://www.robots.ox.ac.uk/~awf/latex-posters/">http://www.robots.ox.ac.uk/~awf/latex-posters/</a>; +<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 “<em>awf</em>” and “<em>capes</em>” + <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 “<em>pjh</em>”, - <a href="http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html">http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html</a>, +<li> from “<em>pjh</em>” + <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, but has hints which are generally useful. + 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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prept1font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prept1font.html new file mode 100644 index 00000000000..0c06f0651b0 --- /dev/null +++ b/Master/texmf-doc/doc/english/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 ‘prepare’ 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’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’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’ 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-doc/doc/english/FAQ-en/html/FAQ-previewers.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html index c803b2df4d3..85f53efa309 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html @@ -12,7 +12,7 @@ have good previewers for PCs running Windows, or for Macintoshes. <p/>For Unix systems, there is one ‘canonical’ 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 +as <i>xdvi</i>. The TeX Live distributions for Unix systems include a version of <i>xdvik</i>. <p/>Alternatives to previewing include <ul> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html index 87b47238e3e..fcd2ef09876 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html @@ -33,7 +33,7 @@ AMSLaTeX’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</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>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-doc/doc/english/FAQ-en/html/FAQ-protect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html index 710c346f896..dd0389f9118 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html @@ -4,15 +4,13 @@ <h3>What’s the reason for ‘protection’?</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. (‘Moving’ because data are moved around.) Places to look for +arguments. (‘Moving’ 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’s a complete list in Lamport’s book (see <a href="FAQ-books.html">TeX-related books</a>). -<p/> - <p/>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 @@ -26,26 +24,62 @@ illegal TeX code during the save process. TeX code during the save process. <p/>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. These lists aren’t as reliable as the -list of moving arguments; the statements may have been true in -early versions of LaTeX2e but are not any longer necessarily so: +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 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 robust commands are redefined by certain packages to be - fragile (the <code>\</code><code>cite</code> command commonly suffers this treatment). <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 “user’s way” of creating a command with an optional - argument (using <code>\</code><code>newcommand</code>) now always creates a robust - command. There is no reason that a package author should not also - make robust commands with optional arguments as part of the - package. + 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> -In short, the situation is confusing. No-one believes this is -satisfactory, and the LaTeX team have removed the need for +Further, simply “hiding” 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 “wrapping” 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’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-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html index e7b2aeebaea..290f4b4e55c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html @@ -15,7 +15,7 @@ by or by <a href="http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf">Thierry Bouche in <i>TUGboat</i> 19(2)</a>). -For maths, then, there are relatively few choices (though the list is +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’) @@ -34,7 +34,8 @@ mathematics include: 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 (<code>msam</code> and <code>msbm</code>) and Euler text fonts. + 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 @@ -63,16 +64,19 @@ mathematics include: fonts come with a <i>fourier</i> package for use with LaTeX; text support of OT1 encoding is not provided — 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. -<dt>Kp-fonts<dd>The Johannes Kepler project<br> +<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’ <i>kpfonts</i> LaTeX support package). -<dt>MathDesign<dd>(4 entire families...so far) Paul Pichareau<br> +<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 @@ -84,6 +88,10 @@ mathematics include: 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’s thoughts on how Metafont might be used in the future: they were published simultaneously as Metafont source, @@ -104,11 +112,22 @@ mathematics include: 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> -Fonts capable of setting TeX mathematics, that are available +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 — June 2008 — the list has several that +are only scheduled for inclusion here. +<p/>Another useful document is Stephen Hartke’s “Free maths font +survey”, 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> @@ -198,7 +217,7 @@ commercially, include: 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 <code>msam</code> and <code>msbm</code> symbol sets). ‘Lucida + AMS <i>msam</i> and <i>msbm</i> symbol sets). ‘Lucida Bright Expert’ (14 fonts) adds seriffed fixed width, another handwriting font, smallcaps, bold maths, upright ‘maths italic’, <em>etc</em>., to the @@ -218,31 +237,6 @@ commercially, include: 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 @@ -251,7 +245,7 @@ commercially, include: 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>. - <p/> + par For further details and samples and fliers, see <a href="http://www.pctex.com/mtpro2.html">http://www.pctex.com/mtpro2.html</a> @@ -402,6 +396,8 @@ print file (PostScript or PDF) for their output device. <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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html index 95ce51a336a..0a1a8ea52b9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html @@ -6,7 +6,7 @@ <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 <code>psfonts.map</code> file, so that <i>dvips</i> will know +lines to the <i>psfonts.map</i> file, so that <i>dvips</i> will know where the proper fonts are, and won’t try to find 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). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html index b40bbf4d248..bdfdc625eaa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html @@ -7,21 +7,19 @@ TeX engine “make this paragraph ragged, but never <em>too</em> ragged”. The LaTeX <code>\</code><code>raggedright</code> command (and the corresponding <code>flushleft</code> 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 Plain -TeX 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 - - -<a href="FAQ-hyphoff.html">hyphenation is suppressed</a>) painfully large gaps may -sometimes be required. +lines, for some minor benefit later in the paragraph. The +Plain TeX 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 +<a href="FAQ-hyphoff.html">hyphenation is suppressed</a> — painfully large gaps +may sometimes be required. <p/>Martin Schröder’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 signficance of the various +discusses the issues and explains the significance of the various parameters of <i>ragged2e</i>’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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html index 7844a57b389..1968c6d11d9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html @@ -15,7 +15,7 @@ file, and complete TeX systems are pretty large. <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 anciliary programs. In short, +print the typeset output, you will need ancillary programs. In short, you need a TeX <em>distribution</em> — a collection of TeX-related programs tailored to your operating system: for details of the sorts of things that are available, see diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html index 30e0bc2407e..47a0a9fe574 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html @@ -36,7 +36,7 @@ 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> amd <i>report</i> classes (<i>scrbook</i> and +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html index e45ad2c9e51..e708dbdc7ef 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html @@ -44,7 +44,7 @@ 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>addsec</code>, which work like <code>\</code><code>chapter</code> and <code>\</code><code>section</code> but +<code>\</code><code>addled</code>, which work like <code>\</code><code>chapter</code> and <code>\</code><code>section</code> but aren’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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html index 738c87c0158..fd1d5e84288 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html @@ -54,8 +54,6 @@ 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. -<p/>The documentation of <i>fncychap</i> is distributed as a separate -PostScript file. <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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html index 3314113ce97..c9e444ad6a8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html @@ -49,8 +49,7 @@ representation is awful. 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’t have much place there). -(<i>hyperref</i> isn’t available in a version for use with Plain -TeX.) +(<i>hyperref</i> isn’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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html index 763d9b4eb2c..a209eb2eb06 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html @@ -2,6 +2,7 @@ <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html index b4eb438aa6c..2cec4a4dcc4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html @@ -53,7 +53,7 @@ commands from one of the <i>pp4</i> packages. The commands don’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 pakages that +<p/><i>Pdfscreen</i> and <i>texpower</i> are add-on packages that permit dynamic effects in documents formatted in “more modest” classes; <i>pdfscreen</i> will even allow you to plug “presentation effects” into an <i>article</i>-class document. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html index 9bea493d68c..ae6333b3514 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html @@ -24,13 +24,13 @@ version of <i>ispell</i>. <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> — choose just those language - dictionaries (under subdirectory <i>dict/</i> that you need. + 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="ftp://cam.ctan.org/tex-archive/systems/win32/winedt/winedt32.exe">systems/win32/winedt/winedt32.exe</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-doc/doc/english/FAQ-en/html/FAQ-tds-zip.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds-zip.html new file mode 100644 index 00000000000..bb2d5cbea86 --- /dev/null +++ b/Master/texmf-doc/doc/english/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 “right” place, +and updating a single index. (Note, this simple idea typically +doesn’t work for fonts, unless they’re distributed as Metafont source.) +<p/>The CTAN network is therefore acquiring “TDS-ZIP” 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 +“<a href="FAQ-inst-tds-zip.html">installing using preformatted ZIP files</a>”. +<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-doc/doc/english/FAQ-en/html/FAQ-textflow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html index 0e288e130bd..625db53d66d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html @@ -6,16 +6,18 @@ 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: -<p/><dl> +<dl> <dt><code>floatflt</code><dd> <i>floatflt</i> is an improved version (for LaTeX2e) of <i>floatfig.sty</i>, and its syntax is: -<p/><pre> +<blockquote> +<pre> \begin{floatingfigure}[options]{width of figure} figure contents \end{floatingfigure} </pre> +</blockquote><p> -<p/>There is a (more or less similar) <code>floatingtable</code> +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. @@ -23,9 +25,9 @@ even/odd pages in a double-sided document. in the neighbourhood of list environments (unless you change your LaTeX document). <dt><code>wrapfig</code><dd> <i>wrapfig</i> has syntax: -<p/><blockquote> +<blockquote> <pre> -\begin{wrapfigure}[height of figure in lines]{l|r,...}[overhang]{width} +\begin{wrapfigure}[height of figure in lines]{l,r,...}[overhang]{width} figure, caption, etc. \end{wrapfigure} </pre> @@ -34,10 +36,11 @@ LaTeX document). 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</code><em>,</em><code>r</code><em>,etc</em>.<code>}</code> parameter can - also be specified as <code>i</code><em>(nside)</em> or <code>o</code><em>(utside)</em> for - two-sided documents, and uppercase can be used to indicate that - the picture should float. The overhang allows the figure to be + 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 @@ -45,25 +48,25 @@ LaTeX document). 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 is: -<p/> <blockquote> - <code>\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}</code><br> + 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> - <em>Paragraph text</em> - -<p/> All parameters except the <em>Picture</em> are optional. The picture + + 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 - an English summary. + 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/systems/msdos/picins/picins.zip">systems/msdos/picins/picins.zip</a> -<li>[picins documentation - summary]<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/picins/picins.txt">macros/latex209/contrib/picins/picins.txt</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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html index 9019d6f8677..7b48723f228 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html @@ -12,7 +12,7 @@ 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 needs to know about the glyphs that each +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-doc/doc/english/FAQ-en/html/FAQ-the-commands.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html index bba7f14641b..b7180d7fc5c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html @@ -3,7 +3,7 @@ </head><body> <h3>Redefining counters’ <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 definining the counter +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 “the value of @@ -24,11 +24,13 @@ 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 (“<code>-</code><code>- nnn -</code><code>-</code>”). Would you want to -achieve this by redefining <code>\</code><code>thepage</code>, given the likely appearance -of the table of contents with the dashes attached every page number, -or of the modified <code>\</code><code>pageref</code> references. In this case, the -modification is best done by redefining the page style itself, perhaps +page surrounded by dashes (as in +“<code>-</code><code>-~</code><code>nnn~-</code><code>-</code>”). +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-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html index 485457a83e8..ec873f2af47 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html @@ -1,21 +1,25 @@ <head> <title>UK TeX FAQ -- question label theoremfmt</title> </head><body> -<h3>Roman theorems</h3> +<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, to use it to create remarks, examples, proofs, +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 roman. +<code>remark</code> whose content is in the default roman font. +<blockquote> + <pre> - \newtheorem{preremark}{Remark} - \newenvironment{remark}% - {\begin{preremark}\upshape}{\end{preremark}} +\newtheorem{preremark}{Remark} +\newenvironment{remark}% + {\begin{preremark}\upshape}{\end{preremark}} </pre> -The <i>ntheorem</i> package provides roman theorems directly. +</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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html index 82a5b21fffd..4e8fc66bf64 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html @@ -37,8 +37,8 @@ table of contents to the relevant place in the file), a slight adjustment is necessary: <blockquote> <pre> -\phantomsection \cleardoublepage +\phantomsection \addcontentsline{toc}{chapter}{Bibliography} \bibliography{frooble} </pre> @@ -49,7 +49,8 @@ something to “hold on to” when making the link. 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; the <i>memoir</i> class includes +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>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html index c8257657fe0..05632d25f2f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html @@ -36,7 +36,7 @@ as in: } </pre> </blockquote><p> -A more LaTeX-y way of doing the job (somewhat innefficiently) uses +A more LaTeX-y way of doing the job (somewhat inefficiently) uses the <i>calc</i> package: <blockquote> <pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html index 8170bd9165f..b08faeb6596 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html @@ -20,7 +20,7 @@ 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 principe be distributed as a working version. (In practice, any +in principle be distributed as a working version. (In practice, any distributor would test new versions against “real” documents or fonts, too; <code>trip</code> and <code>trap</code> don’t actually test any for real world problems. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html index 3f394430699..cf1e34853d4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html @@ -54,7 +54,7 @@ bases on which the excellence of the TeX system rests. since they allow us to map “bits of DVI file” to single characters in the virtual font; so we can create an “é” character by recreating the DVI commands that would result from the code -“<code>\’</code><code>e</code>”. However, since this involves two characters being +“<code>\</code><code>’</code><code>e</code>”. 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’t use the program’s facilities for searching for text that contains inflected characters, diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html index 149c2bebcb0..a898295a03c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html @@ -29,7 +29,7 @@ a more interesting overall view of types in general and some of their history. (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 Richar A. Firmage +<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) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html index 6e76c707fb7..6008a15a443 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label underscore</title> </head><body> <h3>How to use the underscore character</h3> -<p/>The underscore character <code>_</code> is ordinarily used in +<p/>The underscore character ‘<code>_</code>’ is ordinarily used in TeX to indicate a subscript in maths mode; if you type -<code>_</code> in the course of ordinary text, TeX will +<code>_</code>, 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 <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 <code>_</code> to mean ‘text underscore’. +to permit typing ‘<code>_</code>’ to mean ‘text underscore’. However, the code <em>is</em> somewhat tricky, and more importantly there are significant points where it’s easy to get it wrong. There is therefore a package <i>underscore</i> which provides a general @@ -19,8 +19,9 @@ solution to this requirement. underscore character, unless they’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 fuller encoding, such as -T1, which has an underscore character in every font. +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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html index 9b13dc58fe0..d3eb8137324 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html @@ -43,16 +43,16 @@ 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 &plain</code> loading the <code>plain</code> base -file. +<i>mf</i> which executes <code>virmf &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 +it with the +line <pre> \mode=<mode name>; mag=<magnification>; input <font file name> </pre> -in -response to the ‘**’ prompt or on the Metafont command line. (If +in response to the ‘<code>**</code>’ prompt or on the Metafont command line. (If <code><mode name></code> is unknown or omitted, the mode defaults to ‘proof’ and Metafont will produce an output file called @@ -66,14 +66,15 @@ 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 +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' + mf '\mode=epson; mag=magstep 1; input cmr10' </pre> <p/>If you don’t have <i>inimf</i> or need a special mode that isn’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>\smode</code> command. +<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> @@ -87,8 +88,8 @@ the file fillin:=-0.1; o_correction:=.5; </pre> -(note the absence of the <code>mode_def</code> and <code>enddef</code> commands), you would -type +(note the absence of the <code>mode_def</code> and <code>enddef</code> +commands), you would type <pre> mf \smode="ln03"; input cmr10 </pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html index aa74b0f99cc..c9beec26f7f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html @@ -18,8 +18,8 @@ systems. single-entry <a href="FAQ-tds.html">TDS trees</a> — <i>fonts</i>, <i>dvips</i>, <i>tex</i> and <i>doc</i>. The <i>doc</i> subtree really need not be copied (it’s really a pair of sample -files), but copy the other three into your existing Local <code>$TEXMF</code> -tree, and +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, diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html index e07dcc94418..31f029b31e8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html @@ -16,7 +16,7 @@ box of width exactly <code>2cm</code>, 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 analagous to the <code>\</code><code>widthof</code> command for use with the +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>’s idea, by allowing you to set a series of boxes, all with the same (minimised) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html index e5a36b9f191..08d6a2c9fc1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html @@ -3,7 +3,7 @@ </head><body> <h3>Including a file verbatim in LaTeX</h3> <p/>A good way is to use Rainer Schöpf’s <i>verbatim</i> package, -which provides a command <code>\verbatiminput</code> that takes a file name as +which provides a command <code>\</code><code>verbatiminput</code> that takes a file name as argument: <blockquote> <pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html index 131da7afdf5..ab7f42388c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html @@ -19,10 +19,12 @@ their layout: </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:<br> -<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> +<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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html index 0146ff376f5..c3e8a9421c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html @@ -34,9 +34,9 @@ is written in ANSI C). <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/web.zip">systems/knuth/web</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/knuth/web.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/web/">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/web.zip">systems/knuth/web</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/knuth/web.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/web/">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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html index 54a5adca4f3..a6e44a2149f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html @@ -3,29 +3,24 @@ </head><body> <h3>Which tree to use</h3> <p/>In almost all cases, new material that you install should go into the -“local” tree of your (La)TeX installation. The root directory -will be named something like: -<blockquote> -<pre> -teTeX or TeX-live: /usr/share/texmf-local/ or - /usr/local/share/texmf/ -MiKTeX: c:\localtexmf\ -</pre> -</blockquote><p> -You can ask a Unix-alike system (such as teTeX or TeX-live) where -it believes a local tree should be: +“local” 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: +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> -on the workstation the author is using today. <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 @@ -37,24 +32,31 @@ first place, but you may find you need to create one. The MiKTeX has a tab “<code>Roots</code>”; that tab gives a list of current TDS roots (they’re typically not called <code>texmf</code>-anything). If there’s not one there with -“<code>local</code>” in its name, create an appropriate one (say -“<code>Local TeX Files</code>”), and register it using the window’s -“<code>Add</code>” button. The -<a href="http://docs.miktex.org/faq/maintenance.html">Miktex FAQ</a> +“<code>local</code>” in its name, create an appropriate one (see below), +and register it using the window’s +“<code>Add</code>” button. +<p/>The +<a href="http://docs.miktex.org/faq/maintenance.html">MiKTeX FAQ</a> suggests that you should create -<code>C:textbackslashLocal TeX Files</code>, which is good if you +“<code>C:\Local TeX Files</code>”, which is good if you manage your own machine, but often not even possible in corporate, or -similar, environments where you will need to create a directory -somewhere <em>you</em>, rather than the system, control). -<p/>There are circumstances when you might not wish to do this: +similar, environments – 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 “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 +<a href="FAQ-privinst.html">“home” TEXMF tree</a>. +<p/>There are circumstances when you might not wish to use the ‘local’ tree: <ul> <li> 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 <a href="FAQ-privinst.html">“home” TEXMF tree</a>; -<li> if you have no privilege to write to the local tree, you are - again unlikely to be able to put the package anywhere other than - your home tree; or <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html index 2696295bd96..8fccd8c871a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html @@ -23,8 +23,8 @@ 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 usergroup Gutenberg and the Czech/Slovak -usergroup CS-TUG have published translations of this FAQ, with +<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’s excellent <a href="http://texnik.de/">LaTeX tips and tricks</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html index dffcf55605b..a4b39068e90 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html @@ -22,7 +22,8 @@ than columns. So, we set things up by: } </pre> </blockquote><p> -Now, we put ‘<code>$</code>’ before the first column specifier; and we put ‘<code>^</code>’ +Now, we put ‘<code>$</code>’ before the first column specifier; and we +put ‘<code>\textasciicircum</code>’ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html index f7b87439694..6c7acf95289 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html @@ -11,7 +11,7 @@ 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 +<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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html index 6a2fc01eff3..b82b4ae7604 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html @@ -7,10 +7,10 @@ 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 logfiles. These items should not be of general concern, + 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 implementators could +<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 @@ -32,7 +32,7 @@ <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. +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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/index.html b/Master/texmf-doc/doc/english/FAQ-en/html/index.html index d663bc845e6..50794891d0b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/index.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/index.html @@ -55,6 +55,7 @@ Damian Cugley, Michael Dewey, Michael Downes, Jean-Pierre Drucbert, +Michael Ernst, Thomas Esser, Ulrike Fischer, @@ -62,14 +63,17 @@ Anthony Goreham, Norman Gray, Eitan Gurari, William Hammond, +John Harper, John Hammond, Troy Henderson, Hartmut Henkel, +Stephan Hennig, John Hobby, Morten Høgholm, Berthold Horn, Ian Hutchinson, Werner Icking, +William Ingram, Alan Jeffrey, Regnor Jernsletten, David Kastrup, @@ -77,6 +81,7 @@ Oleg Katsitadze, Isaac Khabaza, Ulrich Klauer, Markus Kohm, +David Kraus, Ryszard Kubiak, Simon Law, Daniel Luecking, @@ -178,6 +183,7 @@ Reinhard Zierke. <li><a href="FAQ-fontnamehtml">What is the “Berry naming scheme”</a> </ul><h3>Acquiring the Software</h3><ul> <li><a href="FAQ-archiveshtml">Repositories of TeX material</a> +<li><a href="FAQ-tds-ziphtml">Prebuilt installation files on the archive</a> <li><a href="FAQ-nonfreehtml">What’s the CTAN <code>nonfree</code> tree?</a> <li><a href="FAQ-uploadshtml">Contributing a file to the archives</a> <li><a href="FAQ-findfileshtml">Finding (La)TeX files</a> @@ -218,13 +224,16 @@ Reinhard Zierke. <li><a href="FAQ-what-TDShtml">Which tree to use</a> <li><a href="FAQ-install-wherehtml">Where to install packages</a> <li><a href="FAQ-inst-tidyhtml">Tidying up after installation</a> -<li><a href="FAQ-inst-miktexhtml">Installing MiKTeX “known packages”</a> +<li><a href="FAQ-inst-scuthtml">Shortcuts to installing files</a> +<li><a href="FAQ-inst-miktex*html">Installation using MiKTeX package manager</a> +<li><a href="FAQ-inst-tds-ziphtml">Installing using preformatted ZIP files</a> <li><a href="FAQ-tempinsthtml">“Temporary” installation of (La)TeX files</a> <li><a href="FAQ-privinsthtml">“Private” installations of files</a> <li><a href="FAQ-instfonthtml">Installing a new font</a> <li><a href="FAQ-instmffonthtml">Installing a font provided as Metafont source</a> <li><a href="FAQ-instprinterfonthtml">Installing a PostScript printer built-in font</a> <li><a href="FAQ-inst1cmhtml">Installing the Bluesky versions of the CM fonts</a> +<li><a href="FAQ-prept1fonthtml">Preparing a Type 1 font</a> <li><a href="FAQ-instt1fonthtml">Installing a Type 1 font</a> </ul><h3>Fonts</h3><ul> </ul><h4>Metafont fonts</h4><ul> @@ -281,7 +290,7 @@ Reinhard Zierke. <li><a href="FAQ-bibplainhtml">Using BibTeX with Plain TeX</a> <li><a href="FAQ-makebibhtml">Reconstructing <code>.bib</code> files</a> <li><a href="FAQ-bibprefixsorthtml">BibTeX sorting and name prefixes</a> -<li><a href="FAQ-bibtranscinithtml">Transcribed initials in BibTeX</a> +<li><a href="FAQ-bibtranscinithtml">‘Multi-letter’ initials in BibTeX</a> </ul><h4>Creating citations</h4><ul> <li><a href="FAQ-usebibtexhtml">“Normal” use of BibTeX from LaTeX</a> <li><a href="FAQ-whatbsthtml">Choosing a bibliography style</a> @@ -326,7 +335,9 @@ Reinhard Zierke. <li><a href="FAQ-nofmhtml">Page numbering “<<i>n</i>> of <<i>m</i>>”</a> <li><a href="FAQ-pagebychaphtml">Page numbering by chapter</a> </ul><h4>Page layout</h4><ul> -<li><a href="FAQ-papersizehtml">Printer paper sizes</a> +<li><a href="FAQ-papersizehtml">The size of printed output</a> +<li><a href="FAQ-acroanticshtml">Adobe <i>Reader</i> messing with print size</a> +<li><a href="FAQ-papergeomhtml">Getting the right paper geometry from (La)TeX</a> <li><a href="FAQ-changemarginhtml">Changing the margins in LaTeX</a> <li><a href="FAQ-marginpkgshtml">Packages to set up page designs</a> <li><a href="FAQ-marginmanualhtml">How to set up page layout “by hand”</a> @@ -374,7 +385,7 @@ Reinhard Zierke. </ul><h3>How do I do...?</h3><ul> </ul><h4>Mathematics</h4><ul> <li><a href="FAQ-proofhtml">Proof environment</a> -<li><a href="FAQ-theoremfmthtml">Roman theorems</a> +<li><a href="FAQ-theoremfmthtml">Theorem bodies printed in a roman font</a> <li><a href="FAQ-newfunctionhtml">Defining a new log-like function in LaTeX</a> <li><a href="FAQ-brakethtml">Set specifications and Dirac brackets</a> <li><a href="FAQ-cancellationhtml">Cancelling terms in maths expressions</a> @@ -423,7 +434,7 @@ Reinhard Zierke. <li><a href="FAQ-changebarshtml">Marking changed parts of your document</a> <li><a href="FAQ-conditionalhtml">Conditional compilation and “comments”</a> <li><a href="FAQ-docotherdirhtml">Bits of document from other directories</a> -<li><a href="FAQ-RCShtml">Version control using RCS, CVS or <i>Subversion</i></a> +<li><a href="FAQ-RCShtml">Version control using RCS, CVS or the like</a> <li><a href="FAQ-makehtml">Makefiles for LaTeX documents</a> <li><a href="FAQ-howmanypphtml">How many pages are there in my document?</a> <li><a href="FAQ-inclplainhtml">Including Plain TeX files in LaTeX</a> @@ -500,7 +511,7 @@ Reinhard Zierke. <li><a href="FAQ-widowshtml">Controlling widows and orphans</a> </ul><h4>Things have “gone away”</h4><ul> <li><a href="FAQ-oldfontnameshtml">Old LaTeX font references such as <code>\</code><code>tenrm</code></a> -<li><a href="FAQ-missssymbhtml">Missing symbol commands</a> +<li><a href="FAQ-misssymbhtml">Missing symbol commands</a> <li><a href="FAQ-msxyhtml">Where are the <code>msx</code> and <code>msy</code> fonts?</a> <li><a href="FAQ-amfontshtml">Where are the <code>am</code> fonts?</a> </ul><h3>Why does it <em>do</em> that?</h3><ul> @@ -597,5 +608,5 @@ Reinhard Zierke. "<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.17, last modified on 2007-11-05. + This is FAQ version 3.18, last modified on 2008-06-20. </address> diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf b/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf Binary files differnew file mode 100644 index 00000000000..8704013cb91 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf |