diff options
| author | Karl Berry <karl@freefriends.org> | 2010-04-07 22:47:28 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2010-04-07 22:47:28 +0000 |
| commit | 3f1971c9b7717818766692c9aa497e20e7472f2c (patch) | |
| tree | 678de0190b6643b1b21fd9441fa1387bce180726 | |
| parent | c7c3b090320a234149dbe23315e2a15a2773ac79 (diff) | |
FAQ-en 3.19d (7apr10)
git-svn-id: svn://tug.org/texlive/trunk@17742 c570f23f-e606-0410-a88d-b1316a301751
463 files changed, 4398 insertions, 4048 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d new file mode 100644 index 00000000000..f447a03924f --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d @@ -0,0 +1,34 @@ +Changes in version 3.19d + +This file lists changes since its most recent release (with version 3.19c +of the FAQ). + +New answers: + +Label plaintex: explains "writing in tex", was part of Label whattex + +Relabelled answers: + <none> + +Revised answers: + +Label codelist: mention the minted package + +Label docs: single reference to epslatex (via catalogue) + +Label etex: add ctan link + +Label filesused: rewrite to clarify the issue with \input + +Label luatex: now version 0.60.0 + +Label fonts-pln: replace some complete gibberish (undoing mis-edits, I guess) + +Label parallel: mention the pdfcolparcolumns package + +Label seccntfmt: remove superfluous \expandafter in programming, tidy text + +Label tabcellalign: editorial on \PBS macro discussion + +Label texfuture: rehashed, in light of today's situation + +Label whattex: simplified by removal of material for Label plaintex + +Deleted answers: + <none> + +Web interface: + Extension of links to catalogue, to packages "distributed as part of..." + Abbreviate header text (omitting long list of "helpers" -- which will + ultimately be available in a separate file online) + Convert all alphabetic SGML entities to use numeric equivalents + +Robin Fairbairns diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog index 2f5e03f7698..5f199c96636 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog +++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog @@ -1,3 +1,228 @@ +2010-04-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): massive shambles in [lr]brace + + * faq-mac-prog.tex (subsection{"Generic" macros and techniques}): + correct ref to shortvrb in ctanrefs of q-activechars, and tidy + verbatim stuff in 2nd para of answer + +2010-04-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-adj-types.tex (subsection{Alternative document classes}): add + example structures for combine and subfiles alternatives in q-multidoc + +2010-04-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-projects.tex (section{Current TeX-related projects}): accommodate + luatex 0.60.0 in scribble about luatex + +2010-04-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * gather-faqbody.tex: v3.19d, today (to be revised ;-) + + * faq-intro.tex: omit unnecessary stuff in html mode (looks a bit bare + now, but ought to improve if/when i can sort out a css for the output) + +2010-04-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-intro.tex: minute delta-comment in list of helpers + + * faq-how-do-i.tex: correct typo in q-hyphoff + +2010-03-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-graphics.tex,faq-biblio.tex,faq-lab-ref.tex,faq-how-do-i.tex, + faq-symbols.tex,faq-mac-prog.tex,faq-t-g-wr.tex,faq-wdidt.tex, + faq-jot-err.tex,faq-projects.tex (throughout): add individual cat + links for "distributed as part of" ctanrefs + +2010-03-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-fonts.tex (Macros for using fonts): editorial on some rubbish in + q-fonts-pln + +2010-03-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-adj-types.tex (Page Layout): mention pdfcolparcolumns in + q-parallel + (throughout): add individual cat links for "as part of" ctanrefs + + * dirctan.tex: add minted + + * faq-adj-types.tex (Typesetting specialities): add minted in q-codelist + + * sanitize-beta.pl (sanitize_line): add flatversion in the $ignoring + twiddling at the end + + * faq.sty: add flatversion env (== non-hyperversion) + +2010-03-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add vruler + + * filectan.tex: remove vruler + + * faq-adj-types.tex (Page Layout): editorial in q-parallel, add own cat + entry for pdfcolparallel + +2010-03-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add fncylab, ifmtarg, import (hypernat was here already) + + * filectan.tex: remove fncylab, hypernat, ifmtarg, import + +2010-03-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex: epslatex one ref only, now, relying on catalogue + + * sanitize-beta.pl (generate_CTAN_ref, etc.): generate per reference + catalogue entries if opt argument of \CTANref + + * dirctan.tex: add cat link for everypage + + * faq-texsys.tex: editorial to avoid multiple \ctanref per line + + * faq-graphics.tex: single reference to epslatex (doc from catalogue) + + * filectan.tex: remove epslatex_(ps|pdf) + + * dirctan.tex: add epslatex + + * faq.sty: have \CTANref check for following optional argument (and + ignore it) + + * faq-adj-types.tex: mention atbegshi in q-watermark + +2010-03-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add framed, verbdef (despite believing it already done!) + + * faq-biblio.tex (subsection{Creating citations}): qualify ctanref for + chapterbib in q-chapbib + +2010-03-08 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * dirctan.tex: add threeparttable + correct directory for bigstrut (it's multirow) + + * filectan.tex: remove threeparttable + +2010-03-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * faq-how-do-i.tex (subsection{Document management}): try to clear + ambiguity about \input in q-filesused + + * Makefile: make "index" opt come out in help + + * dirctan.tex: add framed, verbdef dirs + + * filectan.tex: removed framed, verbdef + +2010-02-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * filectan.tex: remove excludeonly + + * dirctan.tex: add bigstrut, excludeonly + + * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): remark + about docs of tabls and bigstrut now not needed; bigstrut now has own + registered directory + +2010-02-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add tabls qua directory + + * filectan.tex: remove tabls + +2010-02-26 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): correct + incompletely edited reference to \PBS in q-tabcellalign + +2010-02-24 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * Makefile: add web-index target to updated (dir|file)ctan for when + ctan structure is changing + +2010-02-23 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-how-do-i.tex (subsection{Floating tables, figures, etc.}): remove + mention of docs of dpfloat + + * faq-wdidt.tex (subsection{Common errors}): use fix2col package + direct, rather than ref to carlisle bundle + + * filectan.tex: remove anonchap, bold-extra, braket, cancel, chngcntr, + dblfloatfix + + * dirctan.tex: add anonchap, bold-extra, braket, cancel, chngcntr, + fix2col, dblfloatfix + +2010-02-18 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * faq-intro.tex (section improvement; general typos): add enrico + gregorio (help with q-seccntfmt) + + * faq-mac-prog.tex (subsection{LaTeX macro programming}): redo + switching code in q-seccntfmt + +2010-02-12 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * texfaq2html-beta: convert (rather smaller number of) entities + + * sanitize-beta.pl (sanitize_line): convert all alphabetic entities to + numerical entities + +2010-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-backgrnd.tex (section{The Background}): rehash q-texfuture, as + suggested by karl berry + +2010-02-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): scrunge hyperversion + + * faq.sty: add a hyperversion env + + * dirctan.tex: add knuth-dist + + * faq-backgrnd.tex (section{The Background}): split q-plaintex from + q-whattex (controversial?) + + * filectan.tex: add knuth-tds + +2010-02-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-backgrnd.tex (section{The Background}): add ctan link in q-etex + + * dirctan.tex: add etex + +2010-02-05 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * texfaq2html-beta: an even more abstruse grep command for registering + labels than was the old for registering question nos (do we really + need to convert + to space? are user-generated questions significant? + -- because if not there never will be "xxx + yyy") + +2010-02-03 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * dirctan.tex: add ulem "stand-alone" + + * filectan.tex: remove ulem + +2010-02-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-mac-prog.tex (subsection{LaTeX macro programming}): remove + superflous \expandafter in q-seccntfmt, and tidy text a bit + +2010-02-02 Robin Fairbairns <rf10@hehe.cl.cam.ac.uk> + + * add-general.tex (subsection{"Generic" macros and techniques}): move + q-ovwtsym and q-long-outer to start of text + add q-detknize + +RELEASE 3.19c + 2010-01-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> * mk-makefile: deal with CHANGES files diff --git a/Master/texmf-dist/doc/generic/FAQ-en/Makefile b/Master/texmf-dist/doc/generic/FAQ-en/Makefile index c261a5f276a..717708568a3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/Makefile +++ b/Master/texmf-dist/doc/generic/FAQ-en/Makefile @@ -29,7 +29,8 @@ CTAN_HOME = help/uk-tex-faq #h web install files required for web access #h (must be run on the machine that hosts #h the CGI script) -#h web-beta ditto, except beta distribution +#h web-index web access files, just (dir|file)ctan +#h web-beta as web, except beta distribution #h #h inst-perl install texfaq2html and sanitize.pl #h in the cgi-bin directory @@ -149,6 +150,8 @@ faqbody.tex: $(SUBDOCS) gather-faqbody.tex web: $(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list +web-index: $(WEB)/dirctan.tex $(WEB)/filectan.tex + $(WEB)/dirctan.tex: dirctan.tex $(WEB)/filectan.tex: filectan.tex $(WEB)/faqbody.tex: faqbody.tex @@ -212,7 +215,7 @@ html-tar: html html-gamma: $(HTMLDIR_GAMMA)/index.html -$(HTMLDIR_GAMMA)/index.html: $(BODY) newfaq.aux +$(HTMLDIR_GAMMA)/index.html: $(BODY) newfaq.aux faqbody.tex ./texfaq2file -2 -w cp -p $(HTMLDIR_GAMMA)/* $(GAMMADIR)/ diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex index 3821a10c949..2b951fa65a9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex @@ -1,4 +1,4 @@ -% $Id: dirctan.tex,v 1.216 2010/01/23 00:41:09 rf10 Exp rf10 $ +% $Id: dirctan.tex,v 1.223 2010/03/23 18:39:39 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANdirs\endcsname @@ -43,6 +43,7 @@ \CTANdirectory{amspell}{support/amspell} \CTANdirectory{amsrefs}{macros/latex/contrib/amsrefs}[amsrefs] \CTANdirectory{amstex}{macros/amstex}[amstex] +\CTANdirectory{anonchap}{macros/latex/contrib/anonchap}[anonchap] \CTANdirectory{answers}{macros/latex/contrib/answers}[answers] \CTANdirectory{ant}{systems/ant}[ant] \CTANdirectory{apl}{fonts/apl} @@ -105,6 +106,7 @@ \CTANdirectory{bibunits}{macros/latex/contrib/bibunits}[bibunits] \CTANdirectory{bibview}{biblio/bibtex/utils/bibview} \CTANdirectory{bigfoot}{macros/latex/contrib/bigfoot}[bigfoot] +\CTANdirectory{bigstrut}{macros/latex/contrib/multirow}[bigstrut] \CTANdirectory{bit2spr}{graphics/bit2spr} \CTANdirectory{black}{fonts/cm/utilityfonts/black} \CTANdirectory{blackboard}{info/symbols/blackboard}[blackboard] @@ -115,9 +117,11 @@ \CTANdirectory{bmeps}{support/bmeps}[bmeps] \CTANdirectory{boites}{macros/latex/contrib/boites}[boites] \CTANdirectory{bold}{fonts/cm/mf-extra/bold} +\CTANdirectory{bold-extra}{macros/latex/contrib/bold-extra}[bold-extra] \CTANdirectory{bonus}{systems/msdos/emtex-contrib/bonus} \CTANdirectory{booktabs}{macros/latex/contrib/booktabs}[booktabs] \CTANdirectory{borceux}{macros/generic/diagrams/borceux} +\CTANdirectory{braket}{macros/latex/contrib/braket}[braket] \CTANdirectory{breakurl}{macros/latex/contrib/breakurl}[breakurl] \CTANdirectory{bridge}{macros/plain/contrib/bridge} \CTANdirectory{brief_t}{support/brief_t} @@ -139,6 +143,7 @@ \CTANdirectory{calendar}{macros/plain/contrib/calendar} \CTANdirectory{calligra}{fonts/calligra} \CTANdirectory{calrsfs}{macros/latex/contrib/calrsfs} +\CTANdirectory{cancel}{macros/latex/contrib/cancel}[cancel] \CTANdirectory{capt-of}{macros/latex/contrib/capt-of}[capt-of] \CTANdirectory{caption}{macros/latex/contrib/caption}[caption] \CTANdirectory{carlisle}{macros/latex/contrib/carlisle}[carlisle] @@ -167,6 +172,7 @@ \CTANdirectory{chi2tex}{support/chi2tex} \CTANdirectory{china2e}{macros/latex/contrib/china2e} \CTANdirectory{chinese}{language/chinese} +\CTANdirectory{chngcntr}{macros/latex/contrib/chngcntr}[chngcntr] \CTANdirectory{circ}{macros/generic/diagrams/circ} \CTANdirectory{circuit_macros}{graphics/circuit_macros} \CTANdirectory{cirth}{fonts/cirth} @@ -230,6 +236,7 @@ \CTANdirectory{datetime}{macros/latex/contrib/datetime} \CTANdirectory{davelove}{web/noweb/contrib/davelove} \CTANdirectory{db2tex}{support/db2tex} +\CTANdirectory{dblfloatfix}{macros/latex/contrib/dblfloatfix}[dblfloatfix] \CTANdirectory{dbtex}{support/dbtex} \CTANdirectory{dc-latex}{language/hyphen-accent/dc-latex} \CTANdirectory{dc-nfss}{language/hyphen-accent/dc-nfss} @@ -318,6 +325,7 @@ \CTANdirectory{epigraph}{macros/latex/contrib/epigraph}[epigraph] \CTANdirectory{eplain}{macros/eplain}[eplain] \CTANdirectory{epmtex}{systems/os2/epmtex} +\CTANdirectory{epslatex}{info/epslatex}[epslatex] \CTANdirectory{epson}{dviware/epson} \CTANdirectory*{epstopdf}{support/epstopdf}[epstopdf] \CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox}[eqparbox] @@ -325,6 +333,7 @@ \CTANdirectory{errata}{systems/knuth/dist/errata} \CTANdirectory{eso-pic}{macros/latex/contrib/eso-pic}[eso-pic] \CTANdirectory{et}{support/et} +\CTANdirectory{etex}{systems/e-tex}[etex] \CTANdirectory{ethiopia}{language/ethiopia} \CTANdirectory{ethtex}{language/ethiopia/ethtex} \CTANdirectory{etoolbox}{macros/latex/contrib/etoolbox}[etoolbox] @@ -335,10 +344,11 @@ \CTANdirectory{eurofont}{macros/latex/contrib/eurofont} \CTANdirectory{europecv}{macros/latex/contrib/europecv} \CTANdirectory{eurosym}{fonts/eurosym} -\CTANdirectory{everypage}{macros/latex/contrib/everypage} +\CTANdirectory{everypage}{macros/latex/contrib/everypage}[everypage] \CTANdirectory{excalibur}{systems/mac/support/excalibur} \CTANdirectory{excel2latex}{support/excel2latex} \CTANdirectory{excerpt}{web/spiderweb/tools/excerpt} +\CTANdirectory{excludeonly}{macros/latex/contrib/excludeonly}[excludeonly] \CTANdirectory{expdlist}{macros/latex/contrib/expdlist} \CTANdirectory{expl3}{macros/latex/contrib/expl3}[expl3] \CTANdirectory{extract}{macros/latex/contrib/extract}[extract] @@ -357,6 +367,7 @@ \CTANdirectory{figflow}{macros/plain/contrib/figflow}[figflow] \CTANdirectory{fink}{macros/latex/contrib/fink}[fink] \CTANdirectory{first-latex-doc}{info/first-latex-doc} +\CTANdirectory{fix2col}{macros/latex/contrib/fix2col}[fix2col] \CTANdirectory{fixfoot}{macros/latex/contrib/fixfoot}[fixfoot] \CTANdirectory{float}{macros/latex/contrib/float}[float] \CTANdirectory{floatflt}{macros/latex/contrib/floatflt}[floatflt] @@ -364,6 +375,7 @@ \CTANdirectory{flowfram}{macros/latex/contrib/flowfram}[flowfram] \CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak}[fnbreak] \CTANdirectory{fncychap}{macros/latex/contrib/fncychap}[fncychap] +\CTANdirectory{fncylab}{macros/latex/contrib/fncylab} \CTANdirectory{foiltex}{macros/latex/contrib/foiltex}[foiltex] \CTANdirectory{font-change}{macros/plain/contrib/font-change}[font-change] \CTANdirectory{fontch}{macros/plain/contrib/fontch}[fontch] @@ -377,6 +389,7 @@ \CTANdirectory{for_tex}{biblio/bibtex/contrib/germbib/for_tex} \CTANdirectory{fourier}{fonts/fourier-GUT}[fourier] \CTANdirectory{fouriernc}{fonts/fouriernc}[fouriernc] +\CTANdirectory{framed}{macros/latex/contrib/framed}[framed] \CTANdirectory{frankenstein}{macros/latex/contrib/frankenstein}[frankenstein] \CTANdirectory{french-faq}{help/LaTeX-FAQ-francaise} \CTANdirectory{funnelweb}{web/funnelweb} @@ -432,6 +445,7 @@ \CTANdirectory{hyacc-cm}{macros/generic/hyacc-cm} \CTANdirectory{hyper}{macros/latex/contrib/hyper} \CTANdirectory{hyperbibtex}{biblio/bibtex/utils/hyperbibtex} +\CTANdirectory{hypernat}{macros/latex/contrib/hypernat}[hypernat] \CTANdirectory{hyperref}{macros/latex/contrib/hyperref}[hyperref] \CTANdirectory{hyphen-accent}{language/hyphen-accent} \CTANdirectory{hyphenat}{macros/latex/contrib/hyphenat}[hyphenat] @@ -439,10 +453,12 @@ \CTANdirectory{ibygrk}{fonts/greek/ibygrk} \CTANdirectory{iching}{fonts/iching} \CTANdirectory{icons}{support/icons} +\CTANdirectory{ifmtarg}{macros/latex/contrib/ifmtarg}[ifmtarg] \CTANdirectory{ifmslide}{macros/latex/contrib/ifmslide}[ifmslide] \CTANdirectory{ifxetex}{macros/generic/ifxetex}[ifxetex] \CTANdirectory{imaketex}{support/imaketex} \CTANdirectory{impact}{web/systems/mac/impact} +\CTANdirectory{import}{macros/latex/contrib/import}[import] \CTANdirectory{index}{macros/latex/contrib/index}[index] \CTANdirectory{indian}{language/indian} \CTANdirectory{infpic}{macros/generic/infpic} @@ -472,9 +488,9 @@ \CTANdirectory{knit}{web/knit} \CTANdirectory{knot}{fonts/knot} \CTANdirectory{knuth}{systems/knuth} +\CTANdirectory{knuth-dist}{systems/knuth/dist}[knuth-dist] \CTANdirectory{koma-script}{macros/latex/contrib/koma-script} \CTANdirectory{korean}{fonts/korean} -%[language/korean] \CTANdirectory{kpfonts}{fonts/kpfonts}[kpfonts] \CTANdirectory{kyocera}{dviware/kyocera} \CTANdirectory{l2a}{support/l2a}[l2a] @@ -577,6 +593,7 @@ \CTANdirectory{midnight}{macros/generic/midnight} \CTANdirectory{minionpro}{fonts/minionpro}[minionpro] \CTANdirectory{minitoc}{macros/latex/contrib/minitoc}[minitoc] +\CTANdirectory{minted}{macros/latex/contrib/minted}[minted] \CTANdirectory{mma2ltx}{graphics/mma2ltx} \CTANdirectory{mnsymbol}{fonts/mnsymbol}[mnsymbol] \CTANdirectory{mnu}{support/mnu} @@ -762,6 +779,7 @@ \CTANdirectory{svninfo}{macros/latex/contrib/svninfo}[svninfo] \CTANdirectory{swebib}{biblio/bibtex/contrib/swebib} \CTANdirectory*{symbols}{info/symbols/comprehensive}[comprehensive] +\CTANdirectory{tabls}{macros/latex/contrib/tabls}[tabls] \CTANdirectory{tabulary}{macros/latex/contrib/tabulary}[tabulary] \CTANdirectory{talk}{macros/latex/contrib/talk}[talk] \CTANdirectory{tds}{tds}[tds] @@ -791,6 +809,7 @@ \CTANdirectory{textures_figs}{systems/mac/textures_figs} \CTANdirectory{texutils}{systems/atari/texutils} \CTANdirectory{tgrind}{support/tgrind}[tgrind] +\CTANdirectory{threeparttable}{macros/latex/contrib/threeparttable}[threeparttable] \CTANdirectory{threeparttablex}{macros/latex/contrib/threeparttablex}[threeparttablex] \CTANdirectory{tib}{biblio/tib}[tib] \CTANdirectory{tiny_c2l}{support/tiny_c2l}[tinyc2l] @@ -817,6 +836,7 @@ \CTANdirectory{type1cm}{macros/latex/contrib/type1cm}[type1cm] \CTANdirectory{ucthesis}{macros/latex/contrib/ucthesis}[ucthesis] \CTANdirectory{uktex}{digests/uktex} +\CTANdirectory{ulem}{macros/latex/contrib/ulem}[ulem] \CTANdirectory{umrand}{macros/generic/umrand} \CTANdirectory{unix}{systems/unix} \CTANdirectory{unpacked}{macros/latex/unpacked} @@ -827,10 +847,12 @@ \CTANdirectory{utopia}{fonts/utopia}[utopia] \CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize] \CTANdirectory{vc}{support/vc}[vc] +\CTANdirectory{verbdef}{macros/latex/contrib/verbdef} \CTANdirectory{vita}{macros/latex/contrib/vita}[vita] \CTANdirectory{vmargin}{macros/latex/contrib/vmargin}[vmargin] \CTANdirectory{vmspell}{support/vmspell}[vmspell] \CTANdirectory{vpp}{support/view_print_ps_pdf}[vpp] +\CTANdirectory{vruler}{macros/latex/contrib/vruler}[vruler] \CTANdirectory{vtex-common}{systems/vtex/common} \CTANdirectory{vtex-linux}{systems/vtex/linux}[vtex-free] \CTANdirectory{vtex-os2}{systems/vtex/os2}[vtex-free] @@ -860,8 +882,3 @@ \CTANdirectory{ziffer}{macros/latex/contrib/ziffer}[ziffer] \CTANdirectory{zoon-mp-eg}{info/metapost/examples}[metapost-examples] \endinput - -%%% Local Variables: -%%% mode: plain-tex -%%% TeX-master: "faqbody" -%%% End: diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex index 2ae04418a38..c2b15511a78 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex @@ -1,4 +1,4 @@ -% $Id: faq-adj-types.tex,v 1.4 2010/01/05 18:54:24 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.9 2010/04/06 18:35:09 rf10 Exp rf10 $ \section{Adjusting the typesetting} @@ -194,7 +194,7 @@ route): \begin{ctanrefs} \item[a0poster.cls]\CTANref{a0poster} \item[flowfram.sty]\CTANref{flowfram} -\item[multicol.sty]Distributed as part of \CTANref{2etools} +\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol] \item[sciposter.cls]\CTANref{sciposter} \item[textpos.sty]\CTANref{textpos} \end{ctanrefs} @@ -251,14 +251,61 @@ The nearest things to canned solutions are Peter Wilson's \Class{Combine} defines the means to `\csx{import}' entire documents, and provides means of specifying significant features of the layout of -the document, as well as a global table of contents, and so on. An -auxiliary package, \Package{combinet}, allows use of the \csx{title}s -and \csx{author}s (etc.\@) of the \csx{import}ed documents to appear in -the global table of contents. - -\Class{Subfiles} is used in the component files of a multi-file -project, and the corresponding \Package{subfiles} is used in the -master file; arrangements may be made so that the component files will +the document, as well as a global table of contents, and so on. The +complete set of facilities is pretty complex. An auxiliary package, +\Package{combinet}, allows use of the \csx{title}s and \csx{author}s +(etc.\@) of the \csx{import}ed documents to appear in the global table +of contents. The basic structure of a combined document would be: +\begin{quote} +\begin{verbatim} +\documentclass[...]{combine} +... +\begin{document} +... +<introductory materiel> +... +\begin{papers} +% title and author of first article, +% to go the the main ToC +\coltoctitle{...} +\coltocauthor{...} +\label{art1} +\import{art1} +... +\end{papers} +... +<acknowledgements, etc.> +... +\end{document} +\end{verbatim} +\end{quote} + +The \Class{subfiles} class is used in the component files of a multi-file +project, and the corresponding \Package{subfiles} package is used in the +master file; so the structure of the master file looks like: +\begin{quote} +\begin{verbatim} +\documentclass{<whatever>} +... +\usepackage{subfiles} +... +\begin{document} +... +\subfile{subfile_name} +... +\end{document} +\end{verbatim} +\end{quote} +while a subfile has the structure: +\begin{quote} +\begin{verbatim} +\documentclass[mainfile_name]{subfiles} +\begin{document} +... +\end{document} +\end{verbatim} +\end{quote} +Arrangements may be made so that the component files will be typeset using different page format, etc., parameters than those used when they are typeset as a part of the main file. @@ -292,8 +339,8 @@ of the included pages. \item[combinet.sty]\CTANref{combine} \item[includex.sty]Distributed in the ``unsupported'' part of \CTANref{frankenstein} -\item[moredefs.sty]Distributed as part of \CTANref{frankenstein} -\item[newclude.sty]Distributed as part of \CTANref{frankenstein} +\item[moredefs.sty]Distributed as part of \CTANref{frankenstein}[moredefs] +\item[newclude.sty]Distributed as part of \CTANref{frankenstein}[newclude] \item[pdfpages.sty]\CTANref{pdfpages} \item[subfiles.cls, etc.]\CTANref{subfiles} \end{ctanrefs} @@ -661,7 +708,7 @@ The \Package{indentfirst} package suppresses the mechanism, so that the first paragraph is indented. \begin{ctanrefs} -\item[indentfirst.sty]Distributed as part of \CTANref{2etools} +\item[indentfirst.sty]Distributed as part of \CTANref{2etools}[indentfirst] \end{ctanrefs} \Question[Q-subsubsub]{How to create a \csx{subsubsubsection}} @@ -984,9 +1031,9 @@ It is this difficulty (what's required in any instance can't really be expressed in current \LaTeX{}) that led the author of \Package{multicol} to suppress single-column-wide floats. \begin{ctanrefs} -\item[balance.sty]Distributed as part of \CTANref{preprint} -\item[flushend.sty]Distributed as part of \CTANref{sttools} -\item[multicol.sty]Distributed as part of \CTANref{2etools} +\item[balance.sty]Distributed as part of \CTANref{preprint}[balance] +\item[flushend.sty]Distributed as part of \CTANref{sttools}[flushend] +\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol] \end{ctanrefs} @@ -1287,7 +1334,7 @@ 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} +\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea] \end{ctanrefs} \Question[Q-changemargin]{Changing the margins in \LaTeX{}} @@ -1353,9 +1400,9 @@ two-sided printing. \begin{ctanrefs} \item[geometry.sty]\CTANref{geometry} \item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script} -\item[layout.sty]Distributed as part of \CTANref{2etools} +\item[layout.sty]Distributed as part of \CTANref{2etools}[layout] \item[memoir.cls]\CTANref{memoir} -\item[typearea.sty]Distributed as part of \CTANref{koma-script} +\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea] \item[vmargin.sty]\CTANref{vmargin} \end{ctanrefs} @@ -1619,15 +1666,26 @@ commands for placing things at certain useful points (like ``text upper left'' or ``text centre'') in the picture, but you're at liberty to do what you like. +\Package{Eso-pic} is, in turn, built upon the package +\Package{atbegshi}. That package has the capability to produce +watermarks \emph{on top of} the other material on the page; this +doesn't sound very ``watermark-like'', but can be useful on pages +where the watermark would otherwise be hidden by graphics or the +like. The \Package{atbegshi} command that \Package{eso-pic} uses is +\csx{AtBeginShipoutUpperLeft}; \csx{AtBeginShipoutUpperLeftForeground} +is what's needed instead to place the material on top of the rest of +the content of the page. + \Package{Everypage} allows you to add ``something'' to every page, or to a particular page; you therefore need to construct your own apparatus for anything complicated. \begin{ctanrefs} +\item[atbegshi.sty]Distributed as part of \CTANref{oberdiek}[atbegshi] \item[draftcopy.sty]\CTANref{draftcopy} \item[draftwatermark.sty]\CTANref{draftwatermark} \item[eso-pic.sty]\CTANref{eso-pic} \item[everypage.sty]\CTANref{everypage} -\item[everyshi.sty]Distributed as part of \CTANref{ms} +\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi] \item[wallpaper.sty]\CTANref{wallpaper} \end{ctanrefs} @@ -1705,11 +1763,11 @@ to view these `final' forms with an appropriate viewer. \begin{ctanrefs} \item[geometry.sty]\CTANref{geometry} \item[graphics.sty]Distributed as part of \CTANref{graphics} -\item[longtable.sty]Distributed as part of \CTANref{2etools} -\item[lscape.sty]Distributed as part of \CTANref{graphics} +\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable] +\item[lscape.sty]Distributed as part of \CTANref{graphics}[lscape] \item[memoir.cls]\CTANref{memoir} \item[pdflscape.sty]Distributed with Heiko Oberdiek's packages - \CTANref{oberdiek} + \CTANref{oberdiek}[pdflscape] \item[rotating.sty]\CTANref{rotating} \item[rotfloat.sty]\CTANref{rotfloat} \item[supertabular.sty]\CTANref{supertabular} @@ -1745,7 +1803,7 @@ must therefore also be available.) % problem. \begin{ctanrefs} \item[eso-pic.sty]\CTANref{eso-pic} -\item[everyshi.sty]Distributed as part of \CTANref{ms} +\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi] \item[textpos.sty]\CTANref{textpos} \end{ctanrefs} @@ -1887,8 +1945,8 @@ as simple as \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. +issue~--- the \Package{pdfcolparallel} package, which maintains +separate colour stacks for the columns. The \Package{parcolumns} package can (in principle) deal with any number of columns: the documentation shows its use with three @@ -1908,7 +1966,9 @@ though there is of course a ``number of columns to specify'': \end{verbatim} \end{quote} The \meta{options} can specify the widths of the columns, whether to -place rules between the columns, whether to set the columns sloppy, etc. +place rules between the columns, whether to set the columns sloppy, +etc. Again, there are issues with colours, which are addressed by the +\Package{pdfcolparcolumns} package. The \Package{ledpar} package is distributed with (and integrated with) the \Qref{\Package{ledmac} package}{Q-linenos}. It provides parallel @@ -1918,8 +1978,9 @@ the `base' text of the document. \begin{ctanrefs} \item[ledpar.sty]Distributed with \CTANref{ledmac} \item[parallel.sty]\CTANref{parallel} -\item[parcolumns.sty]Distributed as part of \CTANref{sauerj} -\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek} +\item[parcolumns.sty]Distributed as part of \CTANref{sauerj}[parcolumns] +\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek}[pdfcolparallel] +\item[pdfcolparcolumns.sty]pdfcolparcolumns] \end{ctanrefs} \Question[Q-epigraph]{Typesetting epigraphs} @@ -2138,7 +2199,7 @@ transformations of the \LaTeX{} kernel originals. The documentation discusses the issues and explains the significance of the various parameters of \Package{ragged2e}'s operation. \begin{ctanrefs} -\item[ragged2e.sty]Distributed as part of \CTANref{ms} +\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e] \end{ctanrefs} \Question[Q-flushboth]{Cancelling \csx{ragged} commands} @@ -2172,7 +2233,7 @@ package has a \csx{justifying} command to match its % ! line break package also provides a \environment{justify} environment, which permits areas of justified text in a larger area which is ragged. \begin{ctanrefs} -\item[ragged2e.sty]Distributed as part of \CTANref{ms} +\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e] \end{ctanrefs} % this package hasn't materialised, for some reason i don't now % remember... @@ -2245,8 +2306,8 @@ The \Class{memoir} class includes the relevant functionality of the \item[fancyvrb.sty]\CTANref{fancyvrb} \item[memoir.cls]\CTANref{memoir} \item[moreverb.sty]\CTANref{moreverb} -\item[sverb.sty]Distributed as part of \CTANref{mdwtools} -\item[verbatim.sty]Distributed as part of \CTANref{2etools} +\item[sverb.sty]Distributed as part of \CTANref{mdwtools}[sverb] +\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim] \end{ctanrefs} \Question[Q-linenos]{Including line numbers in typeset output} @@ -2295,12 +2356,12 @@ the typesetting of dissertations by computer science and other students who are expected to write programs. Simple verbatim listings of programs are commonly useful, as well. -\begin{wideversion} % really hyper +\begin{hyperversion} \Qref{Verbatim listings}{Q-verbfile} are dealt with elsewhere, -\end{wideversion} -\begin{narrowversion} +\end{hyperversion} +\begin{flatversion} Verbatim listings are dealt with elsewhere (\Qref{}{Q-verbfile}), -\end{narrowversion} +\end{flatversion} as is the problem of % ! line break \Qref*{typesetting algorithm specifications}{Q-algorithms}. @@ -2354,6 +2415,11 @@ and \acro{XSL}-\acro{FO} representations of your program listing. Documentation is available on the % ! line break \href{http://www.andre-simon.de/}{\ProgName{highlight} project site}. +The \Package{minted} package is a relatively recent addition. It +requires that documents be pre-processed using an external +(\ProgName{python}) script, % ! line break +\href{http://pygments.org/}{\ProgName{Pygments}}. + 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 @@ -2376,6 +2442,7 @@ program (implicitly) claims to be ``self-documenting''. \item[highlight]\CTANref{highlight} \item[lgrind]\CTANref{lgrind} \item[listings.sty]\CTANref{listings} +\item[minted.sty]\CTANref{listings} \item[tgrind]\CTANref{tgrind} \item[tiny\_c2l]\CTANref{tiny_c2l} \end{ctanrefs} @@ -2641,7 +2708,7 @@ Documentation of both package \Package{path} and package \Package{url} is in the package files. \begin{ctanrefs} \item[hyperref.sty]\CTANref{hyperref} -\item[miniltx.tex]Distributed as part of \CTANref{graphics-plain} +\item[miniltx.tex]Distributed as part of \CTANref{graphics-plain}[miniltx] \item[path.sty]\CTANref{path} \item[url.sty]\CTANref{url} \end{ctanrefs} @@ -2816,7 +2883,7 @@ group the digits of very `long' numbers), but is inevitably less convenient than \Package{icomma} or \Package{ziffer} if you are typing a lot of numbers. \begin{ctanrefs} -\item[icomma.sty]Distributed as part of \CTANref{was} +\item[icomma.sty]Distributed as part of \CTANref{was}[icomma] \item[numprint.sty]\CTANref{numprint} \item[ziffer.sty]\CTANref{ziffer} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex index 9719b0ad108..3612c0209ed 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex @@ -1,4 +1,4 @@ -% $Id: faq-backgrnd.tex,v 1.2 2009/12/10 20:38:28 rf10 Exp $ +% $Id: faq-backgrnd.tex,v 1.5 2010/02/08 22:24:15 rf10 Exp $ \section{The Background} @@ -26,23 +26,48 @@ Knuth developed a system of % ! line breaks `\Qref*{literate programming}{Q-lit}' to write \TeX{}, and he provides the literate (\acro{WEB}) source of \TeX{} free of charge, together with tools for processing the |web| source into something -that can be compiled and something that can be printed; there's never -any mystery about what \TeX{} does. Furthermore, the \acro{WEB} system -provides mechanisms to port \TeX{} to new operating systems and -computers; and in order that one may have some confidence in the ports, -Knuth supplied a \Qref*{test}{Q-triptrap} by +that can be compiled and something that can be printed; there is (in +principle) never any mystery about what \TeX{} does. Furthermore, the +\acro{WEB} system provides mechanisms to port \TeX{} to new operating +systems and computers; and in order that one may have some confidence +in the ports, Knuth supplied a \Qref*{test}{Q-triptrap} by means of which one may judge the fidelity of a \TeX{} system. \TeX{} and its documents are therefore highly portable. +For the interested programmer, the distribution of \TeX{} has some +fascination: it's nothing like the way one would construct such a +program nowadays, yet it has lasted better than most, and has been +ported to many different computer architectures and operating +systems~--- the sorts of attributes that much modern programming +practice aims for. The processed `readable' source of \TeX{} the +program may be found in the % ! line break +\begin{hyperversion} + \Qref*{\acro{TDS} structured version}{Q-tds} of the distribution. +\end{hyperversion} +\begin{dviversion} + \Qref*{\acro{TDS} structured version of the distribution}{Q-tds}. +\end{dviversion} +\begin{ctanrefs} +\item[\nothtml{\rmfamily}Knuth's source distribution]\CTANref{knuth-dist} +\item[\nothtml{\rmfamily}Knuth's sources in \acro{TDS} layout]\CTANref{knuth-tds} +\end{ctanrefs} + +\Question[Q-plaintex]{What's ``writing in \TeX{}''?} + \TeX{} is a macro processor, and offers its users a powerful -programming capability. For this reason, \TeX{} on its own is a -pretty difficult beast to deal with, so Knuth provided a package of -macros for use with \TeX{} called \plaintex{}; \plaintex{} is -effectively the minimum set of macros one can usefully employ with -\TeX{}, together with some demonstration versions of higher-level -commands (the latter are better regarded as models than used as-is). -When people say they're ``programming in \TeX{}'', they usually mean -they're programming in \plaintex{}. +programming capability. To produce a document, you write macros and +text interleaved with each other. The macros define an environment in +which the text is to be typeset. + +However, the basic \TeX{} engine is pretty +basic, and is a pretty difficult beast to deal with. Recognising this +(and not wanting to write the same things at the start of every +document, himself) Knuth provided a package of macros for use with +\TeX{}, called \plaintex{}; \plaintex{} is a useful minimum set of +macros that can be used with \TeX{}, together with some demonstration +versions of higher-level commands. When people say they're ``writing +(or programming) in \TeX{}'', they usually mean they're programming in +\plaintex{}. \Question[Q-TeXpronounce]{How should I pronounce ``\TeX{}''?} @@ -416,6 +441,9 @@ work, but not as well as on an \eTeX{} system. The % ! line break \Qref*{\LaTeX{} team}{Q-LaTeX3} has announced that future \LaTeX{} packages (specifically those from the team, as opposed to those individually contributed) may require \eTeX{} for optimum performance. +\begin{ctanrefs} +\item[\eTeX{}]\CTANref{etex} +\end{ctanrefs} \Question[Q-whatpdftex]{What is \PDFTeX{}?} @@ -807,17 +835,16 @@ projects: see, for example, %\Qref[and]{and the SGML work}{Q-SGML}) to build substantial new macro packages based on \TeX{}. For the even longer term, there -are various projects to build a \emph{successor} to \TeX{}; see, for example, -the -\begin{narrowversion} - \LuaTeX{}, Omega/Aleph and \ExTeX{} projects (questions -\end{narrowversion} -\Qref[\nothtml]{\LuaTeX{}}{Q-luatex}, -\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} and -\Qref[\nothtml]{\ExTeX{}}{Q-extex}\narrowonly{).} -\begin{wideversion} - projects. -\end{wideversion} +are various projects to build a \emph{successor} to \TeX{}. The +\Qref*{\eTeX{}}{Q-etex} extension to \TeX{} itself arose from such a +project (\acro{NTS}). Another pair of projects, which have delivered +all the results they are likely to deliver, is the related % ! line break +\Qref*{Omega and Aleph}{Q-omegaleph}. The % ! line break +\Qref*{\xetex{} system}{Q-xetex} is in principle still under +development, but is widely used, and the % ! line break +\Qref*{\LuaTeX{} project}{Q-luatex} (though with another two years of +development scheduled) has already delivered a system that is quite +useful. \Question[Q-readtex]{Reading \AllTeX{} files} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex index ba0271365c5..f946b1459a2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex @@ -1,4 +1,4 @@ -% $Id: faq-biblio.tex,v 1.5 2010/01/05 18:54:24 rf10 Exp rf10 $ +% $Id: faq-biblio.tex,v 1.7 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{Bibliographies and citations} @@ -829,7 +829,7 @@ within the document: the package will deal with chapters and sections (as defined by \LaTeX{} itself) and also defines a \environment{bibunit} environment so that users can select their own structuring. \begin{ctanrefs} -\item[chapterbib.sty]\CTANref{cite} +\item[chapterbib.sty]distributed as part of \CTANref{cite}[chapterbib] \item[bibunits.sty]\CTANref{bibunits} \end{ctanrefs} @@ -1227,7 +1227,7 @@ its other actions, and have it provide you a compressed bibliography \emph{only}. \begin{ctanrefs} \item[compactbib.sty]\CTANref{compactbib} -\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools} +\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \item[natbib.sty]\CTANref{natbib} \item[savetrees.sty]\CTANref{savetrees} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex index 29411a3984d..7614f0b02f5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex @@ -733,9 +733,7 @@ deparment's pages at %% \URL{http://www.csit.fsu.edu/~mimi/tex/}\nobreakspace--- both sets are fine %% examples of good practice. \begin{ctanrefs} -\item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]the - document is available in \PS{} and \acro{PDF} formats as - \CTANref{epslatex_ps} and \CTANref{epslatex_pdf} respectively +\item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]\CTANref{epslatex} \item[testflow]\CTANref{testflow} \item[\nothtml{\rmfamily}Herbert Vo\ss{}'s Maths tutorial]\CTANref{voss-mathmode} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex index 5537fd2b3dc..030a0452b1d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex @@ -1,4 +1,4 @@ -% $Id: faq-dvi.tex,v 1.1 2009/06/13 20:56:38 rf10 Exp rf10 $ +% $Id: faq-dvi.tex,v 1.1 2009/06/13 20:56:38 rf10 Exp $ \section{\acro{DVI} Drivers and Previewers} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex index 9ea9dd55dbd..d4005502fd0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex @@ -1,4 +1,4 @@ -% $Id: faq-fmt-conv.tex,v 1.1 2009/06/13 20:56:40 rf10 Exp rf10 $ +% $Id: faq-fmt-conv.tex,v 1.1 2009/06/13 20:56:40 rf10 Exp $ \section{Format conversions} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex index b2bbbfdbf1f..8bcb94aaaee 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex @@ -1,4 +1,4 @@ -% $Id: faq-fonts.tex,v 1.4 2010/01/19 22:44:39 rf10 Exp rf10 $ +% $Id: faq-fonts.tex,v 1.6 2010/03/24 23:30:44 rf10 Exp $ \section{Fonts} @@ -920,8 +920,8 @@ versions), which should be available in any recent \TeX{} distribution. fancy with fonts: it sets up the fonts that Knuth found he needed when writing the package, and leaves you to do the rest. -To use something other than Knuth's default, the default mechanism is -to use the \csx{font} primitive: +To use something other than Knuth's default, you can use Knuth's +mechanism, the \csx{font} primitive: \begin{quote} \begin{verbatim} \font\foo=nonstdfont diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex index c4324e520a4..1460716a822 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex @@ -1,4 +1,4 @@ -% $Id: faq-getit.tex,v 1.4 2010/01/19 22:44:39 rf10 Exp rf10 $ +% $Id: faq-getit.tex,v 1.4 2010/03/24 23:27:59 rf10 Exp rf10 $ \section{Acquiring the Software} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex index 45270301eb1..8fbc6e7e5ef 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex @@ -1,4 +1,4 @@ -% $Id: faq-graphics.tex,v 1.2 2009/06/18 23:13:04 rf10 Exp rf10 $ +% $Id: faq-graphics.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{Graphics} @@ -105,8 +105,7 @@ but may also be \begin{ctanrefs} \item[epsf.tex]\CTANref{epsf} \item[epsfig.sty]Part of the \CTANref{graphics} bundle -\item[epslatex.pdf]\CTANref{epslatex_pdf}; the document is also available - in \PS{} format as \CTANref{epslatex_ps} +\item[epslatex.pdf]\CTANref{epslatex} \item[graphics.sty]\CTANref{graphics} \item[graphicx.sty]Part of the \CTANref{graphics} bundle \item[miniltx.tex]\CTANref{graphics-plain} @@ -329,7 +328,7 @@ sufficiently recent version of \PDFTeX{}, in \acro{PDF} mode~--- and even then it won't work for \MP{} files, which are read as \TeX{} input, and therefore use the standard input mechanism). \begin{ctanrefs} -\item[grffile.sty]Distributed as part of \CTANref{oberdiek} +\item[grffile.sty]Distributed as part of \CTANref{oberdiek}[grffile] \end{ctanrefs} \Question[Q-graphicspath]{Importing graphics from ``somewhere else''} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex index 40d334a538d..af25715e63a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex @@ -1,4 +1,4 @@ -% $Id: faq-how-do-i.tex,v 1.7 2010/01/19 22:44:39 rf10 Exp rf10 $ +% $Id: faq-how-do-i.tex,v 1.13 2010/04/02 18:20:00 rf10 Exp rf10 $ \section{How do I do\dots{}?} @@ -37,7 +37,7 @@ The \cmdinvoke{tag*}{\csx{qedhere}} construction may be used in any of \AMSLaTeX{}'s numbering environments. \begin{ctanrefs} \item[amsthm.sty]Distributed as part of the \AMSLaTeX{} bundle - \CTANref{amslatex} + \CTANref{amslatex}[amsthm] \item[ntheorem.sty]\CTANref{ntheorem} \end{ctanrefs} @@ -71,9 +71,9 @@ Alternatively, the following sets up an environment 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[amsthm.sty]Distributed as part of \CTANref{amslatex}[amsthm] \item[ntheorem.sty]\CTANref{ntheorem} -\item[theorem.sty]Distributed as part of \CTANref{2etools} +\item[theorem.sty]Distributed as part of \CTANref{2etools}[theorem] \end{ctanrefs} \Question[Q-newfunction]{Defining a new log-like function in \LaTeX{}} @@ -136,7 +136,8 @@ As with \csx{DeclareMathOperator} there's a starred version (It should be noted that ``log-like'' was reportedly a \emph{joke} on Lamport's part; it is of course clear what was meant.) \begin{ctanrefs} -\item[amsopn.sty]In the \AMSLaTeX{} distribution \CTANref{amslatex} +\item[amsopn.sty]Distributed as part of the \AMSLaTeX{} distribution + \CTANref{amslatex}[amsopn] \end{ctanrefs} \Question[Q-braket]{Set specifications and Dirac brackets} @@ -484,19 +485,13 @@ signs): \end{flalign} \end{verbatim} \end{quote} - -Comprehensive documentation of \AMSLaTeX{} is to be found in -\File{amsldoc}, in the distribution; it is also available on the web -at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf} \begin{ctanrefs} -\item[amsldoc.tex]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} \item[amsmath.sty]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} + \CTANref{amslatex}[amsmath] \item[amstext.sty]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} + \CTANref{amslatex}[amstext] \item[mathtools.sty]Distributed as part of the \Package{mh} bundle - \CTANref{mh} + \CTANref{mh}[mathtools] \end{ctanrefs} \Question[Q-reuseq]{Re-using an equation} @@ -523,15 +518,9 @@ Remember that Here, the second instance of \ensuremath{a=b} will be typeset with a copy, made by the \csx{tag} command, of the label of the first instance. - -Comprehensive documentation of \AMSLaTeX{} is to be found in -\File{amsldoc}, in the distribution; it is also available on the web -at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf} \begin{ctanrefs} -\item[amsldoc.tex]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} \item[amsmath.sty]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} + \CTANref{amslatex}[amsmath] \end{ctanrefs} \Question[Q-brkinline]{Line-breaking in in-line maths} @@ -608,7 +597,7 @@ operation, only those equations to which you make reference will be numbered in the final output. See the package's documentation for details of how to make references when the switch is in effect. \begin{ctanrefs} -\item[mathtools.sty]Distributed as part of \CTANref{mh} +\item[mathtools.sty]Distributed as part of \CTANref{mh}[mathtools] \end{ctanrefs} \subsection{Lists} @@ -707,7 +696,7 @@ The \Class{memoir} class includes functions that match those in the %% larger than the default, you should also change \csx{leftmargini}, %% \csx{leftmarginii}, \emph{etc}. \begin{ctanrefs} -\item[enumerate.sty]Distributed as part of \CTANref{2etools} +\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate] \item[enumitem.sty]\CTANref{enumitem} \item[memoir.cls]\CTANref{memoir} \item[paralist.sty]\CTANref{paralist} @@ -817,11 +806,11 @@ to set spacing between items and between paragraphs within items. more ``basic'' (and therefore more flexible) manner than the % ! line break \Qref*{\Package{enumerate} package}{Q-enumerate} does. \begin{ctanrefs} -\item[enumerate.sty]Distributed as part of \CTANref{2etools} +\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumitem] \item[enumitem.sty]\CTANref{enumitem} \item[expdlist.sty]\CTANref{expdlist} \item[memoir.cls]\CTANref{memoir} -\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools} +\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \item[multenum.sty]\CTANref{multenum} \item[paralist.sty]\CTANref{paralist} \item[savetrees.sty]\CTANref{savetrees} @@ -966,10 +955,10 @@ However, the `nested comment' interpolated in the nested enumeration appears as if it were a second paragraph to ``outer item 2'', which is hardly satisfactory. \begin{ctanrefs} -\item[enumerate.sty]Distributed as part of \CTANref{2etools} +\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate] \item[enumitem.sty]\CTANref{enumitem} \item[expdlist.sty]\CTANref{expdlist} -\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools} +\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \end{ctanrefs} \subsection{Tables, figures and diagrams} @@ -1115,8 +1104,8 @@ should process using \LaTeX{}. Processing will give you a \File{.sty} file as well as the \File{.dvi} or \File{.pdf} output containing the documentation. \begin{ctanrefs} -\item[ltxtable.sty]Distributed as part of \CTANref{carlisle} -\item[tabularx.sty]Distributed as part of \CTANref{2etools} +\item[ltxtable.sty]Distributed as part of \CTANref{carlisle}[ltxtable] +\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx] \item[tabulary.sty]\CTANref{tabulary} \end{ctanrefs} @@ -1177,7 +1166,7 @@ or you can use it as follows: where the second column will end up noticeably wider, and will wrap to a second line in the third row. \begin{ctanrefs} -\item[array.sty]Distributed as part of \CTANref{2etools} +\item[array.sty]Distributed as part of \CTANref{2etools}[array] \item[varwidth.sty]\CTANref{varwidth} \end{ctanrefs} @@ -1254,12 +1243,9 @@ interesting. The package provides rule commands to support the author's scheme, but deals with inter-row spacing too. The most recent release of \Package{booktabs} sports compatibility with packages such as \Package{longtable}. - -Documentation of both \Package{bigstrut} and \Package{tabls} may be -found as comments in the package files themselves. \begin{ctanrefs} -\item[array.sty]Distributed as part of \CTANref{2etools} -\item[bigstrut.sty]Distributed as part of \CTANref{multirow} +\item[array.sty]Distributed as part of \CTANref{2etools}[array] +\item[bigstrut.sty]\CTANref{bigstrut} \item[booktabs.sty]\CTANref{booktabs} \item[cellspace.sty]\CTANref{cellspace} \item[tabls.sty]\CTANref{tabls} @@ -1329,10 +1315,10 @@ the head- and footline capabilities of the major packages. Documentation of \Package{ltablex} is to be found in the package file. \begin{ctanrefs} -\item[longtable.sty]Distributed as part of \CTANref{2etools} +\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable] \item[ltablex.sty]\CTANref{ltablex} \item[ltxtable.sty]Generate by running \CTANref{ltxtable} -\item[stabular.sty]Distributed as part of \CTANref{sttools} +\item[stabular.sty]Distributed as part of \CTANref{sttools}[stabular] \item[supertabular.sty]\CTANref{supertabular} \item[xtab.sty]\CTANref{xtab} \end{ctanrefs} @@ -1358,17 +1344,16 @@ arises in the last cell of a row: since each cell is set into a box, its settings are lost at the \texttt{\&} (or \texttt{\bsbs }) that terminates it. - -The technique using \csx{PBS} was developed in the days of \LaTeXo{} -because the actual value of \texttt{\bsbs } that the \environment{tabular} -environment uses was only available as an internal command. Nowadays, -the value is a public command, and you can in principle use it -explicitly: +In the old days, the actual value of \texttt{\bsbs } that the +\environment{tabular} environment uses was only available as an +internal command. Nowadays, the value is a public command, and you +can in principle use it explicitly: \begin{quote} \begin{verbatim} ... & \centering blah ... \tabularnewline \end{verbatim} \end{quote} +(but that's a rather verbose way of doing things). The \Package{array} package provides a command \csx{arraybackslash} which restores \texttt{\bsbs } to its correct (within table) meaning; @@ -1393,8 +1378,9 @@ specifications: The \csx{tabularnewline} and \csx{arraybackslash} commands are (somewhat) modern additions to \LaTeX{} and the \Package{array} -package, respectively. If neither is available, the user may try the -(old) solution which preserves the meaning of \texttt{\bsbs }: +package, respectively. In the unlikely event that neither is +available, the user may try the (old) solution which preserves the +meaning of \texttt{\bsbs }: \begin{quote} \begin{verbatim} \newcommand\PBS[1]{\let\temp=\\% @@ -1416,7 +1402,7 @@ or in the preamble as: \end{verbatim} \end{quote} \begin{ctanrefs} -\item[array.sty]Distributed as part of \CTANref{2etools} +\item[array.sty]Distributed as part of \CTANref{2etools}[array] \end{ctanrefs} \nothtml{\vskip 0pt plus 4ex} @@ -1700,7 +1686,7 @@ The \Package{array} package works with several other example \environment{longtable}), but unfortunately this trick won't always work. \begin{ctanrefs} -\item[array.sty]Distributed as part of \CTANref{2etools} +\item[array.sty]Distributed as part of \CTANref{2etools}[array] \end{ctanrefs} \Question[Q-multirow]{Merging cells in a column of a table} @@ -1814,7 +1800,7 @@ rows in the multi-row have been opened up with \csx{bigstrut}. The documentation of both \Package{multirow} and \Package{bigstrut} is to be found, as comments, in the package files themselves. \begin{ctanrefs} -\item[bigstrut.sty]Distributed as part of \CTANref{multirow} +\item[bigstrut.sty]\CTANref{bigstrut} \item[multirow.sty]\CTANref{multirow} \end{ctanrefs} @@ -1984,8 +1970,8 @@ float is set \emph{before} any single column floats). something approximating the effect it would have.) \begin{ctanrefs} \item[dblfloatfix.sty]\CTANref{dblfloatfix} -\item[stfloats.sty, midfloat.sty]Distributed as part of - \CTANref{sttools} +\item[midfloat.sty]Distributed as part of \CTANref{sttools}[midfloat] +\item[stfloats.sty]Distributed as part of \CTANref{sttools}[stfloats] \end{ctanrefs} \Question[Q-mcfloat]{Floats in multicolumn setting} @@ -2018,7 +2004,7 @@ running off the end of the column at the end of the \environment{multicols} environment). \begin{ctanrefs} \item[float.sty]\CTANref{float} -\item[multicol.sty]Distributed as part of \CTANref{2etools} +\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol] \end{ctanrefs} \Question[Q-dpfloat]{Facing floats on 2-page spread} @@ -2043,9 +2029,6 @@ this: the construction to use is: \end{quote} The construction has no effect unless the standard class option \pkgoption{twoside} is in effect. - -Full documentation of the package (such as it is) is to be found in -\File{README.dpfloat} \begin{ctanrefs} \item[dpfloat.sty]\CTANref{dpfloat} \end{ctanrefs} @@ -2173,7 +2156,7 @@ and the sequence of float numbers is all correct. \item[caption.sty]\CTANref{caption} \item[float.sty]\CTANref{float} \item[here.sty]\CTANref{here} -\item[perpage.sty]Distributed as part \CTANref{bigfoot} +\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage] \end{ctanrefs} \subsection{Footnotes} @@ -2237,12 +2220,12 @@ in ordinary text. The author of this \acro{FAQ} answer doesn't actually recommend any of them, believing that table notes are the way to go\dots{} \begin{ctanrefs} \item[ctable.sty]\CTANref{ctable} -\item[footnote.sty]Distributed as part of \CTANref{mdwtools} -\item[longtable.sty]Distributed as part of \CTANref{2etools} -\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools} +\item[footnote.sty]Distributed as part of \CTANref{mdwtools}[footnote] +\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable] +\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}[mdwtab] \item[threeparttable.sty]\CTANref{threeparttable} \item[threeparttablex.sty]\CTANref{threeparttablex} -\item[tabularx.sty]Distributed as part of \CTANref{2etools} +\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx] \end{ctanrefs} \Question[Q-ftnsect]{Footnotes in \LaTeX{} section headings} @@ -2449,8 +2432,7 @@ also designed to support typesetting critical editions. \item[edmac]\CTANref{edmac} \item[ednotes]\CTANref{ednotes} \item[ledmac]\CTANref{ledmac} -\item[manyfoot.sty]Distributed as part of the \CTANref{ncctools} - bundle +\item[manyfoot.sty]Distributed as part of \CTANref{ncctools}[manyfoot] \end{ctanrefs} \Question[Q-footnpp]{Footnotes numbered ``per page''} @@ -2491,15 +2473,14 @@ the one package to achieve your ends. The \Package{footnpag} package also does per-page footnotes (and nothing else). With the competition from \Package{perpage}, it's -probably not particularly useful any more. (Documentation is -\File{footnpag-user.pdf} in the distribution.) +probably not particularly useful any more. \begin{ctanrefs} \item[footmisc.sty]\CTANref{footmisc} \item[footnpag.sty]\CTANref{footnpag} -\item[perpage.sty]Distributed as part \CTANref{bigfoot} -\item[zref.sty]Distributed as a collection member in \CTANref{oberdiek} -\item[zref-perpage.sty]Distributed as a collection member in - \CTANref{oberdiek} +\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage] +\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref] +\item[zref-perpage.sty]Distributed as part of \Package{zref} in + \CTANref{oberdiek}[zref] \end{ctanrefs} \Question[Q-run-fn-nos]{Not resetting footnote numbers per chapter} @@ -2643,13 +2624,19 @@ be used as a check-list in case that problems arise. Note that \csx{listfiles} only registers things that are input by the ``standard'' \LaTeX{} mechanisms (\csx{documentclass}, \csx{usepackage}, -\csx{input}, \csx{include}, \csx{includegraphics} and so on). But if you -use \TeX{} primitive syntax, as in +\csx{include}, \csx{includegraphics} and so on). +The \csx{input} command, as modified by \LaTeX{} and used, with +\LaTeX{} syntax, as: +\begin{verbatim} + \input{mymacros} +\end{verbatim} +records file details for \File{mymacros.tex}, but if you use \TeX{} +primitive syntax for \csx{input}, as: \begin{verbatim} \input mymacros \end{verbatim} -\File{mymacros.tex} \emph{won't} be listed by \csx{listfiles}, since -you've bypassed the mechanism that records its use. +\File{mymacros.tex} \emph{won't} be recorded, and so won't listed by +\csx{listfiles}~--- you've bypassed the mechanism that records its use. The \Package{snapshot} package helps the owner of a \LaTeX{} document obtain a list of the external dependencies of the document, in a form @@ -2923,21 +2910,19 @@ including (numeric or labelled) ranges of environments to extract, and an \environment{extract} environment which you can use to create complete ready-to-run \LaTeX{} documents with stuff you've extracted. \begin{ctanrefs} -\item[askinclude.sty]Distributed with Heiko Oberdiek's packages~--- - \CTANref{oberdiek} +\item[askinclude.sty]Distributed as part of \CTANref{oberdiek}[askinclude] \item[comment.sty]\CTANref{comment} \item[excludeonly.sty]\CTANref{excludeonly} \item[extract.sty]\CTANref{extract} \item[memoir.cls]\CTANref{memoir} \item[optional.sty]\CTANref{optional} -\item[pagesel.sty]Distributed with Heiko Oberdiek's packages~--- - \CTANref{oberdiek} +\item[pagesel.sty]Distributed as part of \CTANref{oberdiek}[pagesel] \item[pdfpages.sty]\CTANref{pdfpages} \item[selectp.sty]\CTANref{selectp} -\item[verbatim.sty]Distributed as part of \CTANref{2etools} +\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim] \item[version.sty]\CTANref{version} \item[versions.sty]\CTANref{versions} -\item[xcomment.sty]Distributed as part of \CTANref{seminar} +\item[xcomment.sty]Distributed as part of \CTANref{seminar}[xcomment] \end{ctanrefs} \Question[Q-docotherdir]{Bits of document from other directories} @@ -3031,8 +3016,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.7 $ % or any RCS keyword -\RCS$Date: 2010/01/19 22:44:39 $ +\RCS$Revision: 1.13 $ % or any RCS keyword +\RCS$Date: 2010/04/02 18:20:00 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3042,8 +3027,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.7 $ % or any RCS keyword -\RCS$Date: 2010/01/19 22:44:39 $ +\RCS$Revision: 1.13 $ % or any RCS keyword +\RCS$Date: 2010/04/02 18:20:00 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3188,8 +3173,8 @@ to the equivalent of the \texttt{LastPage} label and the Both \Package{count1to} and \Package{totpages} need the support of the \Package{everyshi} package. \begin{ctanrefs} -\item[count1to.sty \nothtml{\bgroup\rmfamily}and\nothtml{\egroup} everyshi.sty]% line break!! - Distributed in \CTANref{ms} +\item[count1to.sty]Distributed as part of \CTANref{ms}[count1to] +\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi] \item[lastpage.sty]\CTANref{lastpage} \item[memoir.cls]\CTANref{memoir} \item[totpages.sty]\CTANref{totpages} @@ -3221,7 +3206,7 @@ The package is known to fail, for example, with documents that use All these things can be overcome (although it's not often easy), but the environment saves a lot of work on many occasions. \begin{ctanrefs} -\item[plain.sty]Distributed as part of \CTANref{carlisle} +\item[plain.sty]Distributed as part of \CTANref{carlisle}[plain-ltx] \end{ctanrefs} \subsection{Hyphenation} @@ -3519,7 +3504,7 @@ and the \Package{hyphenat} package uses this technique for its \csx{nohyphens} command which sets its argument without any hyphenation. You can load \Package{hyphenat} with the command \begin{quote} - \cmdinvoke{usepckage}[none]{hyphenat} + \cmdinvoke{usepackage}[none]{hyphenat} \end{quote} to prevent any hyphenation in a single-language document. The technique cannot work in a document in which \Package{babel} controls diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex index 1ed5d96e3bc..cd2341c6cd2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex @@ -1,4 +1,4 @@ -% $Id: faq-install.tex,v 1.8 2009/12/25 00:29:51 rf10 Exp rf10 $ +% $Id: faq-install.tex,v 1.8 2009/12/25 00:29:51 rf10 Exp $ \section{Installing \AllTeX{} files} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex index 5d0fcecc358..8e6477eaca9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex @@ -1,4 +1,4 @@ -% $Id: faq-intro.tex,v 1.8 2009/12/28 23:20:40 rf10 Exp rf10 $ +% $Id: faq-intro.tex,v 1.10 2010/04/02 19:11:38 rf10 Exp rf10 $ % this environment is for the benefit of new-style file generation \begin{introduction} @@ -15,40 +15,56 @@ You may use the \acro{FAQ} \begin{itemize} \item by reading a printed document, \item by viewing a \acro{PDF} file, with hyperlinks to assist - browsing: copies are available formatted for printing on - \CTANhref{faq-a4}{A4 paper} or on % ! line break - \CTANhref{faq-letter}{North American ``letter'' paper}, or + browsing: copies are available formatted so that they could be + printed on \CTANhref{faq-a4}{A4 paper} or on % ! line break + \CTANhref{faq-letter}{North American ``letter'' paper}, \htmlonly{or} +\htmlignore \item by using the \acro{FAQ}'s web interface (base \acro{URL}: \URL{http://www.tex.ac.uk/faq}); this version provides simple search capabilities, as well as a link to Google for a more sophisticated search restricted to the \acro{FAQ} itself, or +\endhtmlignore \item via Scott Pakin's \CTANhref{visualFAQ}{Visual FAQ}, which shows - \LaTeX{} constructions with links to \acro{FAQ} details of how they - were created. + \LaTeX{} constructions with links to \acro{FAQ} explanations of how + they may be created. \end{itemize} \subsection{Finding the Files} +\begin{typesetversion} Unless otherwise specified, all files mentioned in this \acro{FAQ} are available from a \acro{CTAN} archive, or from a mirror of \acro{CTAN}~--- see \Qref[question]{later discussion}{Q-archives}% ! space \narrowonly{, which gives details} of the \acro{CTAN} archives\wideonly{ and}\narrowonly{, including} how to retrieve files -from them. If you don't have access to the internet, the -\Qref*{\texlive{} distribution}{Q-CD} offers off-line snapshots of the -archives. +from them. +%% If you don't have access to the internet, the +%% \Qref*{\texlive{} distribution}{Q-CD} offers off-line snapshots of the +%% archives. -The reader should also note that the first directory name of the -path name of every file on \acro{CTAN} is omitted from what -follows, for the simple reason that, while it's always the same +The reader should also note that the first directory name of the path +name of every file on \acro{CTAN} is omitted from what follows, for +the simple reason that, while it's always the same (\path{tex-archive/}) on the main sites, mirror sites often choose something else. -To avoid confusion, we also omit the full stop from the end of -any sentence whose last item is a path name (such sentences are -rare, and only occur at the end of paragraphs). Though the path -names are set in a different font from running text, it's not easy -to distinguish the font of a single dot! +To avoid confusion, we also omit the full stop from the end of any +sentence whose last item is a path name (such sentences are rare, and +only occur at the end of paragraphs). Though the path names are set +in a different font from running text, it's not easy to distinguish +the font of a single dot! +\end{typesetversion} +\begin{htmlversion} +Almost all files suggested in answers in these \acro{FAQ}s are +available from \Qref{\acro{CTAN} archives}{Q-archives}, and may be +reached via links in the file list at the end of the answer. In +particular, documentation (when available) is linked from the +\acro{CTAN} Catalogue entry, which is also listed in the file list. + +Unless doing so is unavoidable, the answers do not mention things not +on the archive. An obvious exception is web resources such as +supplementary documents, etc. +\end{htmlversion} \latexhtml{\subsection*{Origins}}{\textbf{Origins}} @@ -60,6 +76,7 @@ Bodenheimer. The first \acro{UK} version was much re-arranged and corrected from the original, and little of Bodenheimer's work now remains. +\htmlignore The following people (at least~--- there are almost certainly others whose names weren't correctly recorded) have contributed help or advice on the development of the \acro{FAQ}: Donald Arseneau, @@ -79,6 +96,7 @@ Ulrike Fischer, % spotted boondoggle in q-tabcellalign % args like \section improvement; general typos Anthony Goreham, Norman Gray, +Enrico Gregorio, % new definition for q-seccntfmt Eitan Gurari, % (RIP) comparative html translators William Hammond, % lots of work on xml-related answers John Harper, % patient help with q-robust ;-) @@ -124,7 +142,7 @@ Oren Patashnik, Manuel P\'egouri\'e-Gonnard, % improvement of q-luatex Steve Peter, % comprehensive review, lots of typos etc Sebastian Rahtz, % without whom there would be no... -Philip Ratcliffe, % help with a bibtex oddity +Philip Ratcliffe, % help with a bibtex oddity, editorial comment Chris Rowley, % founding father Jos\'e Carlos Santos, % assiduous reader of new versions Walter Schmidt, @@ -146,4 +164,5 @@ That list does \emph{not} cover the many people whose ideas I have encountered on various lists, newsgroups or (lately) web forums. Many such people have helped me, perhaps simply to alert me to an area in which I need to work. +\endhtmlignore \end{introduction} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex index 7bf27aba3fa..e0fb8436c7c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex @@ -1,4 +1,4 @@ -% $Id: faq-jot-err.tex,v 1.3 2009/12/10 20:38:28 rf10 Exp $ +% $Id: faq-jot-err.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{The joy of \TeX{} errors} @@ -69,7 +69,7 @@ appeal to the \Qref*[question]{wider public}{Q-gethelp} for assistance, but if you do, be sure to report full backtraces (see |errorcontextlines| above) and so on. \begin{ctanrefs} -\item[trace.sty]Distributed as part of \CTANref{2etools} +\item[trace.sty]Distributed as part of \CTANref{2etools}[trace] \end{ctanrefs} \Question[Q-errstruct]{The structure of \TeX{} error messages} @@ -659,7 +659,7 @@ The diagnostic not only tells us where the group started, but also the \csx{bgroup}, and the two are not distinguishable at the \TeX{}-engine level). \begin{ctanrefs} -\item[checkend.sty]Distributed as part of \CTANref{bezos} +\item[checkend.sty]Distributed as part of \CTANref{bezos}[checkend] \end{ctanrefs} \Question[Q-nonum]{``Missing number, treated as zero''} @@ -705,7 +705,7 @@ incorporates \FontName{Times}-like mathematics, and a sans-serif face based on \FontName{Helvetica}, but scaled to match \FontName{Times} text rather better. \begin{ctanrefs} -\item[calc.sty]Distributed as part of \CTANref{2etools} +\item[calc.sty]Distributed as part of \CTANref{2etools}[calc] \item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2} \item[The psnfss bundle]\CTANref{psnfss} \end{ctanrefs} @@ -823,7 +823,8 @@ unsatisfactory alternatives: \end{wideversion} \end{itemize} \begin{ctanrefs} -\item[grffile.sty]Distributed as part of the \CTANref{oberdiek} collection +\item[grffile.sty]Distributed as part of the Oberdiek collection + \CTANref{oberdiek}[grffile] \end{ctanrefs} \Question[Q-nodollar]{``Missing \texttt{\$} inserted''} @@ -1403,7 +1404,7 @@ Get rid of the error in the way described in % ! linebreak \csx{tabularnewline} explicitly, or use the \csx{RBS} trick described there. \begin{ctanrefs} -\item[array.sty]Distributed as part of \CTANref{2etools} +\item[array.sty]Distributed as part of \CTANref{2etools}[array] \end{ctanrefs} \Question[Q-divzero]{Graphics division by zero} @@ -1564,7 +1565,7 @@ and then steadily reduce the bold families, starting with \end{quote} until (with a bit of luck) the error goes away. \begin{ctanrefs} -\item[bm.sty]Distributed as part of \CTANref{2etools} +\item[bm.sty]Distributed as part of \CTANref{2etools}[bm] \end{ctanrefs} \Question[Q-ouparmd]{Not in outer par mode} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex index 5f7f2cea0af..2958f541444 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex @@ -1,4 +1,4 @@ -% $Id: faq-lab-ref.tex,v 1.1 2009/06/13 20:56:44 rf10 Exp rf10 $ +% $Id: faq-lab-ref.tex,v 1.2 2010/03/26 22:48:51 rf10 Exp rf10 $ \subsection{Labels and references} @@ -68,7 +68,7 @@ define a short-name variant.) \item[nameref.sty]Distributed with \CTANref{hyperref} \item[smartref.sty]\CTANref{smartref} \item[titleref.sty]\CTANref{titleref} -\item[zref.sty]Distributed as part of \CTANref{oberdiek} +\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref] \end{ctanrefs} \Question[Q-extref]{Referring to labels in other documents} @@ -176,9 +176,9 @@ The module provides all the facilities of the older packages, and can deal both with ``traditional'' \LaTeX{} labels and with \Package{zref}'s style of labels. \begin{ctanrefs} -\item[xr.sty]Distributed as part of \CTANref{2etools} -\item[xr-hyper.sty]Distributed with \CTANref{hyperref} +\item[xr.sty]Distributed as part of \CTANref{2etools}[xr] +\item[xr-hyper.sty]Distributed with \CTANref{hyperref}[xr-hyper] \item[zref \nothtml{\rmfamily\itshape}bundle]Distributed as part of - \CTANref{oberdiek} + \CTANref{oberdiek}[zref] \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex index 277796e5969..06b0c348412 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex @@ -1,4 +1,4 @@ -% $Id: faq-litprog.tex,v 1.1 2009/06/13 20:56:39 rf10 Exp rf10 $ +% $Id: faq-litprog.tex,v 1.1 2009/06/13 20:56:39 rf10 Exp $ \section{Literate programming} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex index 69e5e655dda..d421044660e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex @@ -1,4 +1,4 @@ -% $Id: faq-mac-prog.tex,v 1.6 2009/11/01 23:23:26 rf10 Exp rf10 $ +% $Id: faq-mac-prog.tex,v 1.10 2010/04/06 18:35:09 rf10 Exp rf10 $ \section{Macro programming} @@ -782,7 +782,7 @@ doesn't have to remember that argument twelve is |soiltype|, and so on: the commands may be copied from field notes quickly and accurately. \begin{ctanrefs} -\item[keyval.sty]Distributed as part of \CTANref{graphics} +\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval] \end{ctanrefs} \Question[Q-keyval]{Key-value input for macros and package options} @@ -958,11 +958,11 @@ for \textsl{TUGboat} by Joseph Wright, and the partial translation of the documentation of package \Package{scrbase} prepared by Philipp Stephani. \begin{ctanrefs} -\item[keyval.sty]Distributed as part of \CTANref{graphics} -\item[kvoptions.sty]Distributed as part of \CTANref{oberdiek} -\item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek} +\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval +\item[kvoptions.sty]Distributed as part of \CTANref{oberdiek}[kvoptions] +\item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek}[kvsetkeys] \item[l3keys.sty]Distributed as part of \CTANref{expl3} -\item[l3keys2e.sty]Distributed as part of \CTANref{expl3} +\item[l3keys2e.sty]Distributed as part of \CTANref{xpackages} \item[pgfkeys.sty]Distributed as part of \CTANref{pgf} \item[scrbase.sty]Distributed as part of \CTANref{koma-script} \item[xkeyval.sty]\CTANref{xkeyval} @@ -975,19 +975,27 @@ Single characters can act as macros (defined commands), and both ``\texttt{\textasciitilde}'' as a ``non-breakable space''. A character is made definable, or ``active'', by setting its \emph{category code} (catcode) to be \csx{active} (13): -|\catcode`_=\active|. - +\begin{quote} +\begin{verbatim} +\catcode`\_=\active +\end{verbatim} +\end{quote} Any character could, in principle, be activated this way and defined -as a macro (\csx{def}\texttt{\_\{}\csx{\_}\texttt{\}}~--- the simple answer to -% beware line break -\Qref[question]{using underscores}{Q-underscore}), but you must be +as a macro: +\begin{quote} +\begin{verbatim} +\def_{\_} +\end{verbatim} +\end{quote} +which could be characterised as an over-simple answer to % ! line break +\Qref[question]{using underscores}{Q-underscore}. However, you must be wary: whereas people expect an active tilde, other active characters may be unexpected and interact badly with other macros. Furthermore, by defining an active character, you preclude the character's use for other purposes, and there are few characters ``free'' to be subverted in this way. -To define the character ``|z|'' as a command, one would say something +To define the character ``\texttt{z}'' as a command, one would say something like: \begin{quote} \begin{verbatim} @@ -1086,8 +1094,8 @@ made active~--- the definition of the command persists even if the character's catcode reverts to its original value; the definition becomes accessible again if the character once again becomes active. \begin{ctanrefs} -\item[doc.sty]Distributed as part of the source of \LaTeX{}, \CTANref{latex} -\item[shortvrb.sty]Distributed as part of \CTANref{2etools} +\item[doc.sty]Part of the \LaTeX{} distribution \CTANref{latex}[doc] +\item[shortvrb.sty]Part of the \LaTeX{} distribution \CTANref{latex}[shortvrb] \end{ctanrefs} @@ -1450,9 +1458,10 @@ the ``\TeX{} project'' answers covering % ! line break \Qref[\xetex{}~--- question]{\xetex{}}{Q-xetex}, and \Qref[\LuaTeX{}~--- question]{\LuaTeX{}}{Q-luatex}). \begin{ctanrefs} -\item[ifpdf.sty]Distributed with Heiko Oberdiek's packages \CTANref{oberdiek} -\item[ifluatex.sty]Distributed with Heiko Oberdiek's packages - \CTANref{oberdiek} +\item[ifpdf.sty]Distributed as part Heiko Oberdiek's bundle + \CTANref{oberdiek}[ifpdf] +\item[ifluatex.sty]Distributed as part of Heiko Oberdiek's bundle + \CTANref{oberdiek}[ifluatex] \item[ifxetex.sty]\CTANref{ifxetex} \end{ctanrefs} @@ -1808,8 +1817,8 @@ 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} +\item[makerobust.sty]Distributed as part of Heiko Oberdiek's bundle + \CTANref{oberdiek}[makerobust] \end{ctanrefs} \Question[Q-edef]{\csx{edef} does not work with \csx{protect}} @@ -2074,8 +2083,8 @@ the command to be defined. The command requires that a \ProgName{Python} interpreter (etc.\@) be installed on your computer. \begin{ctanrefs} \item[newcommand.py]\CTANref{newcommand} -\item[optparams.sty]Distributed as part of \CTANref{sauerj} -\item[twoopt.sty]Distributed as part of \CTANref{oberdiek} +\item[optparams.sty]Distributed as part of \CTANref{sauerj}[optparams] +\item[twoopt.sty]Distributed as part of \CTANref{oberdiek}[twoopt] \item[xargs.sty]\CTANref{xargs} \item[xkeyval.sty]\CTANref{xkeyval} \end{ctanrefs} @@ -2182,7 +2191,7 @@ definition like: \end{quote} \begin{ctanrefs} \item[ifthen.sty]Part of the \LaTeX{} distribution -\item[suffix.sty]Distributed as part of \CTANref{bigfoot} +\item[suffix.sty]Distributed as part of \CTANref{bigfoot}[suffix] \end{ctanrefs} \nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax} @@ -2493,7 +2502,7 @@ numbered per chapter, try: \item[removefr.tex]\CTANref{removefr} (note, this is constructed as a ``fragment'' for use within other packages: load by \cmdinvoke{input}{removefr}) -\item[remreset.sty]Distributed as part of \CTANref{carlisle} +\item[remreset.sty]Distributed as part of \CTANref{carlisle}[remreset] \end{ctanrefs} \Question[Q-labelctr]{Making labels from a counter} @@ -2657,79 +2666,57 @@ number appears in the heading, and some such people don't mind writing out a few macros. This answer is for \emph{them}. The section number is typeset using the -\begin{narrowversion} +\begin{dviversion} \LaTeX{} internal -\end{narrowversion} -\begin{wideversion} +\end{dviversion} +\begin{hyperversion} \Qref{\LaTeX{} internal}{Q-atsigns} -\end{wideversion} +\end{hyperversion} \csx{@seccntformat} command, which is given the ``name'' (section, subsection, \dots{}) of the heading, as argument. Ordinarily, \csx{@seccntformat} -merely outputs the section number, and then a \csx{quad} of space. -Suppose you want to put a stop after every section (subsection, -subsubsection, \dots{}) number, a trivial change may be implemented by -simple modification of the command: +merely outputs the section number, and then a \csx{quad} of space: \begin{quote} \begin{verbatim} \renewcommand*{\@seccntformat}[1]{% - \csname the#1\endcsname.\quad + \csname the#1\endcsname\quad } \end{verbatim} \end{quote} - -Many people (for some reason) want a stop after a section number, but -not after a subsection number, or any of the others. -To do this, one must make \csx{@seccntformat} switch according to its -argument. The following technique for doing the job is slightly -wasteful, but is efficient enough for a relatively rare operation: -\begin{wideversion} +Suppose you want to put a stop after every section (subsection, +subsubsection, \dots{}) number, a trivial change may be implemented by +simple modification of the command: \begin{quote} \begin{verbatim} -\let\@@seccntformat\@seccntformat \renewcommand*{\@seccntformat}[1]{% - \expandafter\ifx\csname @seccntformat@#1\endcsname\relax - \expandafter\@@seccntformat - \else - \expandafter - \csname @seccntformat@#1\expandafter\endcsname - \fi - {#1}% + \csname the#1\endcsname.\quad } \end{verbatim} \end{quote} -\end{wideversion} -\begin{narrowversion} +However, many people want to modify section numbers, but not +subsection numbers, or any of the others. To do this, one must make +\csx{@seccntformat} switch according to its argument. The following +technique for doing the job is slightly wasteful, but is efficient +enough for a relatively rare operation: \begin{quote} \begin{verbatim} -\let\@@seccntformat\@seccntformat \renewcommand*{\@seccntformat}[1]{% - \expandafter\ifx - \csname @seccntformat@#1\endcsname - \relax - \expandafter\@@seccntformat - \else - \expandafter - \csname @seccntformat@#1\expandafter - \endcsname - \fi - {#1}% + \csname the#1\endcsname + \csname adddot@#1\endcsname\quad } \end{verbatim} \end{quote} -\end{narrowversion} -which looks to see if a second-level command has been defined, and -uses it if so; otherwise it uses the original. The second-level -command to define stops after section numbers (only) has the same -definition as the original ``all levels alike'' version: +which uses a second-level command to provide the dot, if it has been +defined; otherwise it merely appends \csx{relax} (which does nothing +in this context). The definition of the second-level command (the +version for the \texttt{section}, here) specifies what to put after a +section number, but it could be used to put anything after it: \begin{quote} \begin{verbatim} -\newcommand*{\@seccntformat@section}[1]{% - \csname the#1\endcsname.\quad -} +\newcommand*{\adddot@section}{.} \end{verbatim} \end{quote} -Note that all the command definitions of this answer are dealing in +Note that all the command definitions above are dealing in \Qref*{\LaTeX{} internal commands}{Q-atsigns}, so the above code should be in a package file, for preference. @@ -2871,7 +2858,7 @@ to stabilise counter values~--- \LaTeX{} will generate the usual warnings about labels changing. \begin{ctanrefs} \item[chngcntr.sty]\CTANref{chngcntr} -\item[perpage.sty]Distributed as part \CTANref{bigfoot} +\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage] \end{ctanrefs} \Question[Q-fontsize]{Fonts at arbitrary sizes} @@ -2917,7 +2904,7 @@ December 2003 edition of \LaTeX{}; if you have an older distribution, the packages \Package{type1cm} (for \acro{CM} fonts) and \Package{type1ec} (for \acro{EC} fonts) are available. \begin{ctanrefs} -\item[fix-cm.sty]Distributed as part of \CTANref{latex} (an unpacked +\item[fix-cm.sty]Distributed as part of \CTANref{latex}[fix-cm] (an unpacked version is available at \CTANref{fix-cm}) \item[type1cm.sty]\CTANref{type1cm} \item[type1ec.sty]\CTANref{type1ec} (the package is actually part of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex index c01f64e5be0..02f5e3ab5a7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex @@ -1,4 +1,4 @@ -% $Id: faq-projects.tex,v 1.7 2009/12/25 10:31:28 rf10 Exp rf10 $ +% $Id: faq-projects.tex,v 1.9 2010/04/06 18:35:09 rf10 Exp rf10 $ \section{Current \TeX{}-related projects} @@ -297,7 +297,7 @@ separate window), degree of correspondence of the display to the final output, and the balance they strike between visual aid and visual distraction. \begin{ctanrefs} -\item[preview-latex]Distributed as part of \CTANref{auctex} +\item[preview-latex]Distributed as part of \CTANref{auctex}[preview-latex] \item[texmacs]Browse \CTANref{texmacs} \end{ctanrefs} @@ -389,9 +389,10 @@ current projects have in their sights, notably Unicode character representations and support for OpenType fonts. The intention is to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}. -Version 0.50.0 of \LuaTeX{} is intended to at least demonstrate the final -functionality; it was released near the end of December 2009. Much -work remains to be done, and this remains a beta-release. +The current version (0.60.0, in April 2010) of \LuaTeX{} is supposed +at least to demonstrate the final functionality. This stability was +declared with version 0.50.0, released near the end of December 2009. +Much work remains to be done, and this remains a beta-release. \texlive{} 2009 incorporates (at the time of writing) \LuaTeX{} version 0.44.0, but the latest \miktex{} (version 2.8) still doesn't offer it. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex index b08e2ab44ac..ed06d60b0a0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex @@ -1,4 +1,4 @@ -% $Id: faq-symbols.tex,v 1.2 2009/06/30 18:44:15 rf10 Exp $ +% $Id: faq-symbols.tex,v 1.3 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{Symbols, etc.} @@ -187,7 +187,7 @@ Examples of the available styles are available on \acro{CTAN}. \item[eucal.sty]Distributed as part of \CTANref{amsfonts} \item[euler fonts]Distributed as part of \CTANref{amsfonts} \item[ghostscript]Browse \CTANref{ghostscript} -\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros} +\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}[mathrsfs] \item[rsfs fonts]\CTANref{rsfs} \item[Script font examples]\CTANref{mathscript} \item[URW Chancery L]Distributed as part of \CTANref{urw-base35} @@ -233,10 +233,10 @@ These problems may be addressed by using a bold mathematics package. All these solutions cover all mathematical symbols, not merely Greek letters. \begin{ctanrefs} -\item[bm.sty]Distributed as part of \CTANref{2etools} -\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex} +\item[bm.sty]Distributed as part of \CTANref{2etools}[bm] +\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}[amsbsy] \item[amsmath.sty]Distributed as part of \AMSLaTeX{} - \CTANref{amslatex} + \CTANref{amslatex}[amsmath] \end{ctanrefs} \Question[Q-prinvalint]{The Principal Value Integral symbol} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex index b89d2a25b94..8eb21040059 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex @@ -1,4 +1,4 @@ -% $Id: faq-t-g-wr.tex,v 1.4 2010/01/21 21:01:42 rf10 Exp rf10 $ +% $Id: faq-t-g-wr.tex,v 1.5 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{Things are Going Wrong\dots{}} @@ -102,7 +102,7 @@ program for other systems (including Windows, nowadays). \item[m-pictex.sty]Distributed as part of \CTANref{context-tmf} \item[m-pictex.tex]Distributed as part of \CTANref{context-tmf} \item[MathsPic]\CTANref{mathspic} -\item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon} +\item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon}[pictexwd] \end{ctanrefs} \subsection{Making things stay where you want them} @@ -187,7 +187,7 @@ equally well to tables, or to ``non-standard'' floats defined by the the job for you. \end{itemize} \begin{ctanrefs} -\item[afterpage.sty]Distributed as part of \CTANref{2etools} +\item[afterpage.sty]Distributed as part of \CTANref{2etools}[afterpage] \item[endfloat.sty]\CTANref{endfloat} \item[flafter.sty]Part of the \LaTeX{} distribution \item[float.sty]\CTANref{float} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex index c0f0b1aff6c..fbbcbcf83ef 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex @@ -1,4 +1,4 @@ -% $Id: faq-texsys.tex,v 1.2 2009/12/18 01:06:03 rf10 Exp rf10 $ +% $Id: faq-texsys.tex,v 1.3 2010/03/17 21:59:55 rf10 Exp $ \section{\TeX{} Systems} @@ -128,9 +128,9 @@ see \Qref{}{Q-commercial} for details of commercial packages. \TeX{}, which further the focus. \begin{ctanrefs} \item[bakoma]\CTANref{bakoma-tex} - \item[miktex]\CTANref{miktex}; acquire \CTANref{miktex-setup} (also - available from the \miktex{} web site), and read installation - instructions from % ! line break + \item[miktex]\CTANref{miktex}; % ! line break so only on \CTANref on line + acquire \CTANref{miktex-setup} (also available from the \miktex{} + web site), and read installation instructions from % ! line break \href{http://www.miktex.org/2.8/setup}{the \miktex{} installation page} \item[\nothtml{\bgroup\rmfamily}Portable\nothtml{\egroup} miktex]\CTANref{miktex-portable} \item[protext.exe]\CTANref{protext} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex index 80f62200f31..7e6feabdb31 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex @@ -1,4 +1,4 @@ -% $Id: faq-the-end.tex,v 1.1 2009/06/13 20:56:49 rf10 Exp rf10 $ +% $Id: faq-the-end.tex,v 1.1 2009/06/13 20:56:49 rf10 Exp $ \section{You're still stuck?} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex index ddcbfa84c1c..161e96497de 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex @@ -1,4 +1,4 @@ -% $Id: faq-wdidt.tex,v 1.2 2009/10/09 18:20:46 rf10 Exp rf10 $ +% $Id: faq-wdidt.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $ \section{Why does it \emph{do} that?} @@ -332,7 +332,7 @@ be had by saying: \end{quote} \begin{ctanrefs} \item[expdlist.sty]\CTANref{expdlist} -\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools} +\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \end{ctanrefs} % other instances: \[no]linebreak in vertical mode @@ -366,7 +366,7 @@ whole requirement is to patch the output routine; no extra commands are needed. \begin{ctanrefs} \item[dblfloatfix.sty]\CTANref{dblfloatfix} -\item[fix2col.sty]Distributed as part of \CTANref{carlisle} +\item[fix2col.sty]\CTANref{fix2col} \item[fixltx2e.sty]Part of the \LaTeX{} distribution \end{ctanrefs} @@ -1119,7 +1119,7 @@ which can be confusing, notably to a collaborating author don't). Of course, no command built into \LaTeX{} or into any ``standard'' class or package will use \csx{xspace}. \begin{ctanrefs} -\item[xspace.sty]Distributed as part of \CTANref{2etools} +\item[xspace.sty]Distributed as part of \CTANref{2etools}[xspace] \end{ctanrefs} \Question[Q-overfull]{\AllTeX{} makes overfull lines} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty index ff33448b021..8e8e47fb805 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty @@ -170,11 +170,15 @@ \ifpdf \includecomment{pdfversion} \includecomment{wideversion} + \includecomment{hyperversion} + \excludecomment{flatversion} \excludecomment{dviversion} \excludecomment{narrowversion} \else \excludecomment{pdfversion} \excludecomment{wideversion} + \excludecomment{hyperversion} + \includecomment{flatversion} % non-hyper \includecomment{dviversion} \includecomment{narrowversion} \fi @@ -628,12 +632,16 @@ \newcounter{CTAN@replabs}% % % the command itself -\DeclareRobustCommand{\CTANref}[1]{\@ifundefined{ctan-#1}{% +\newcommand{\CTANref}[1]{\@ifundefined{ctan-#1}{% \PackageWarning{CTAN}{Undefined reference: #1}% \stepcounter{CTAN@unrefs}% }{% \csname ctan-#1\endcsname -}} +}\futurelet\@let@token\faq@check@trailing@opt} +\newcommand\faq@check@trailing@opt{\ifx\@let@token[% + \expandafter\@gobble@opt\fi +} +\def\@gobble@opt[#1]{} % % href to a ctan package \ifpdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex index b5912c8b754..b5a12a76e48 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex @@ -1,4 +1,4 @@ -% $Id: filectan.tex,v 1.117 2010/01/23 00:41:09 rf10 Exp rf10 $ +% $Id: filectan.tex,v 1.125 2010/03/23 18:39:39 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANfiles\endcsname @@ -15,45 +15,32 @@ \CTANfile{T1instguide}{info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf} \CTANfile{TeX-FAQ}{obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers} \CTANfile{abstract-bst}{biblio/bibtex/utils/bibtools/abstract.bst} -\CTANfile{anonchap}{macros/latex/contrib/misc/anonchap.sty}[anonchap] \CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex}[backgrnd] \CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk}[bbl2html] \CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf}[beginlatex] \CTANfile{belleek}{fonts/belleek/belleek.zip}[belleek] \CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf} \CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex}[bidstobibtex] -\CTANfile{bold-extra}{macros/latex/contrib/misc/bold-extra.sty} -\CTANfile{braket}{macros/latex/contrib/misc/braket.sty}[braket] \CTANfile{btxmactex}{macros/eplain/tex/eplain/btxmac.tex}[eplain] -\CTANfile{cancel}{macros/latex/contrib/misc/cancel.sty}[cancel] \CTANfile{catalogue}{help/Catalogue/catalogue.html} \CTANfile{cat-licences}{help/Catalogue/licenses.html} -\CTANfile{chngcntr}{macros/latex/contrib/misc/chngcntr.sty} \CTANfile{clsguide}{macros/latex/doc/clsguide.pdf}[clsguide] \CTANfile{compactbib}{macros/latex/contrib/compactbib/compactbib.sty}[compactbib] %\CTANfile{compan-ctan}{info/companion.ctan} \CTANfile{context-tmf}{macros/context/current/cont-tmf.zip}[context] -\CTANfile{dblfloatfix}{macros/latex/contrib/misc/dblfloatfix.sty}[dblfloatfix] \CTANfile{dvitype}{systems/knuth/dist/texware/dvitype.web}[dvitype] \CTANfile{edmetrics}{systems/mac/textures/utilities/EdMetrics.sea.hqx}[edmetrics] \CTANfile{epsf}{macros/generic/epsf/epsf.tex}[epsf] -\CTANfile{epslatex_pdf}{info/epslatex/english/epslatex.pdf}[epslatex] -\CTANfile{epslatex_ps}{info/epslatex/english/epslatex.ps} -\CTANfile{excludeonly}{macros/latex/contrib/misc/excludeonly.sty}[excludeonly] \CTANfile{figsinlatex}{obsolete/info/figsinltx.ps} \CTANfile{finplain}{biblio/bibtex/contrib/misc/finplain.bst} \CTANfile{fix-cm}{macros/latex/unpacked/fix-cm.sty}[fix-cm] -\CTANfile{fncylab}{macros/latex/contrib/misc/fncylab.sty} \CTANfile{fntguide.pdf}{macros/latex/doc/fntguide.pdf}[fntguide] \CTANfile{fontdef}{macros/latex/base/fontdef.dtx} \CTANfile{fontmath}{macros/latex/unpacked/fontmath.ltx} -\CTANfile{framed}{macros/latex/contrib/misc/framed.sty}[framed] \CTANfile{gentle}{info/gentle/gentle.pdf}[gentle] \CTANfile{gkpmac}{systems/knuth/local/lib/gkpmac.tex}[gkpmac] -\CTANfile{hypernat}{macros/latex/contrib/misc/hypernat.sty}[hypernat] -\CTANfile{ifmtarg}{macros/latex/contrib/misc/ifmtarg.sty}[ifmtarg] -\CTANfile{import}{macros/latex/contrib/misc/import.sty}[import] \CTANfile{ispell}{support/ispell/ispell-3.2.06.tar.gz}[ispell] +\CTANfile{knuth-tds}{macros/latex/contrib/latex-tds/knuth.tds.zip} \CTANfile{l2tabuen}{info/l2tabu/english/l2tabuen.pdf}[l2tabu-english] \CTANfile{l2tabuen.src}{info/l2tabu/english/l2tabuen.tex}[l2tabu-english] \CTANfile{latex209-base}{obsolete/macros/latex209/distribs/latex209.tar.gz}[latex209] @@ -106,7 +93,6 @@ \CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}[setspace] \CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.ps}[simplified-latex] \CTANfile{sober}{macros/latex209/contrib/misc/sober.sty}[sober] -\CTANfile{tabls}{macros/latex/contrib/misc/tabls.sty}[tabls] \CTANfile{tex2bib}{biblio/bibtex/utils/tex2bib/tex2bib}[tex2bib] \CTANfile{tex2bib-doc}{biblio/bibtex/utils/tex2bib/README} \CTANfile{tex4ht}{support/TeX4ht/tex4ht-all.zip}[tex4ht] @@ -114,7 +100,6 @@ \CTANfile{texlive-windows}{systems/texlive/tlnet/install-tl.zip} \CTANfile{texnames}{info/biblio/texnames.sty} \CTANfile{texsis-index}{macros/texsis/index/index.tex} -\CTANfile{threeparttable}{macros/latex/contrib/misc/threeparttable.sty}[threeparttable] \CTANfile{titleref}{macros/latex/contrib/misc/titleref.sty}[titleref] \CTANfile{topcapt}{macros/latex/contrib/misc/topcapt.sty}[topcapt] \CTANfile{tracking}{macros/latex/contrib/tracking/tracking.sty}[tracking] @@ -124,10 +109,8 @@ \CTANfile{upquote}{macros/latex/contrib/upquote/upquote.sty}[upquote] \CTANfile{faq-a4}{help/uk-tex-faq/newfaq.pdf} \CTANfile{faq-letter}{help/uk-tex-faq/letterfaq.pdf} -\CTANfile{ulem}{macros/latex/contrib/misc/ulem.sty}[ulem] \CTANfile{underscore}{macros/latex/contrib/misc/underscore.sty}[underscore] \CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty}[varwidth] -\CTANfile{verbdef}{macros/latex/contrib/misc/verbdef.sty}[verbdef] \CTANfile{version}{macros/latex/contrib/misc/version.sty}[version] \CTANfile{versions}{macros/latex/contrib/versions/versions.sty}[versions] \CTANfile{vertbars}{macros/latex/contrib/misc/vertbars.sty}[vertbars] @@ -135,7 +118,6 @@ \CTANfile{vf-knuth}{info/knuth/virtual-fonts}[vf-knuth] \CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}[visualfaq] \CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf} -\CTANfile{vruler}{macros/latex/contrib/misc/vruler.sty}[vruler] \CTANfile{wujastyk-txh}{digests/texhax/txh/wujastyk.txh} \CTANfile{xampl-bib}{biblio/bibtex/distribs/doc/xampl.bib} \CTANfile{xtexcad}{graphics/xtexcad/xtexcad-2.4.1.tar.gz} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex index 6216173ea85..625797b2b9e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.19c} \def\faqfiledate{2010-01-08} +\def\faqfileversion{3.19d} \def\faqfiledate{2010-04-02} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html index 319fa4e9f9b..073004c06e4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label 2colfloat</title> </head><body> <h3>Placing two-column floats at bottom of page</h3> -<p/>You specified placement ‘<code>[htbp]</code>’ for your full-width figure or -table, but they always get placed at the top of the page… Well, +<p/>You specified placement ‘<code>[htbp]</code>’ for your full-width figure or +table, but they always get placed at the top of the page… Well, it <em>is</em> what the documentation says: LaTeX, unadorned, only allows full-width floats at the top of a page, or occupying (part of) a float page. <p/>The <i>stfloats</i> package ameliorates the situation somewhat, and -makes LaTeX honour ‘[b]’ placement as well; the +makes LaTeX honour ‘[b]’ placement as well; the <i>dblfloatfix</i> package combines a tidied version of the changes made in <i>stfloats</i> with the @@ -18,17 +18,17 @@ made in <i>stfloats</i> with the is that the float will appear, at its earliest, on the page after it is specified. This has two undesirable side-effects: first, there may be no bottom float on the first page of a document, and second, float -numbers may become “entangled” (particularly if you’re using +numbers may become “entangled” (particularly if you’re using <i>dblfloatfix</i> that ensures that the early-specified bottom float is set <em>before</em> any single column floats). -<p/>(The FAQ team doesn’t know of any package that will make -LaTeX honour ‘[h]’ placement of double-column floats, but the +<p/>(The FAQ team doesn’t know of any package that will make +LaTeX honour ‘[h]’ placement of double-column floats, but the <i>midfloat</i> package can be pressed into service to provide something approximating the effect it would have.) <dl> -<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/dblfloatfix.sty">macros/latex/contrib/misc/dblfloatfix.sty</a> -<dt><tt><i>stfloats.sty, midfloat.sty</i></tt><dd>Distributed as part of - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>) +<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dblfloatfix.zip">macros/latex/contrib/dblfloatfix</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dblfloatfix/">browse the directory</a>) +<dt><tt><i>midfloat.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/midfloat.html">catalogue entry</a> +<dt><tt><i>stfloats.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/stfloats.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html index 2e26817db6b..d396d5ff00c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label 2colfltorder</title> </head><body> <h3>Two-column float numbers out of order</h3> -<p/>When LaTeX can’t place a float immediately, it places it on one of -several “defer” lists. If another float of the same type comes -along, and the “defer” list for that type still has something in it, +<p/>When LaTeX can’t place a float immediately, it places it on one of +several “defer” lists. If another float of the same type comes +along, and the “defer” list for that type still has something in it, the later float has to wait for everything earlier in the list. <p/>Now, standard LaTeX has different lists for single-column floats, and double-column floats; this means that single-column figures can @@ -13,7 +13,7 @@ figures appear in the document before early ones. The same is true, of course, for tables, or for any user-defined float. <p/>The LaTeX team recognise the problem, and provides a package (<i>fixltx2e</i>) to deal with it. <i>Fixltx2e</i> amalgamates -the two defer lists, so that floats don’t get out of order. +the two defer lists, so that floats don’t get out of order. <p/>For those who are still running an older LaTeX distribution, the package <i>fix2col</i> should serve. This package (also by a member of the LaTeX team) was the basis of the relevant part of @@ -24,8 +24,8 @@ at <a href="FAQ-2colfloat.html"><code>[b]</code> placement</a>. whole requirement is to patch the output routine; no extra commands are needed. <dl> -<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/dblfloatfix.sty">macros/latex/contrib/misc/dblfloatfix.sty</a> -<dt><tt><i>fix2col.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>) +<dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dblfloatfix.zip">macros/latex/contrib/dblfloatfix</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dblfloatfix/">browse the directory</a>) +<dt><tt><i>fix2col.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fix2col.zip">macros/latex/contrib/fix2col</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fix2col/">browse the directory</a>) <dt><tt><i>fixltx2e.sty</i></tt><dd>Part of the LaTeX distribution </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html index c84861521e0..ee10b070a16 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label 2letterfontcmd</title> </head><body> -<h3>What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</h3> +<h3>What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</h3> <p/>The font-selection commands of LaTeX 2.09 were <code>\</code><code>rm</code>, <code>\</code><code>sf</code>, <code>\</code><code>tt</code>, <code>\</code><code>it</code>, <code>\</code><code>sl</code>, <code>\</code><code>em</code> and <code>\</code><code>bf</code>; they were modal commands, so you used them as: @@ -41,10 +41,10 @@ LaTeX2e font selections with the old style commands: </blockquote><p> ignores the <code>\</code><code>textbf</code> that encloses the text, and produces typewriter text at medium weight. -<p/>So why are these commands deprecated? — it is because of confusions +<p/>So why are these commands deprecated? — it is because of confusions such as that in the last example. The alternative (LaTeX2e) commands are discussed in the rest of this answer. -<p/>LaTeX2e’s font commands come in two forms: modal commands and +<p/>LaTeX2e’s font commands come in two forms: modal commands and text-block commands. The default set of modal commands offers weights <code>\</code><code>mdseries</code> and <code>\</code><code>bfseries</code>, shapes <code>\</code><code>upshape</code>, <code>\</code><code>itshape</code>, <code>\</code><code>scshape</code> and <code>\</code><code>slshape</code>, and families @@ -68,7 +68,7 @@ in the default Computer Modern fonts), or </pre> </blockquote><p> (note the italic correction needed on slanted fonts, too). -<p/>LaTeX2e’s text block commands take the first two letters of the +<p/>LaTeX2e’s text block commands take the first two letters of the modal commands, and form a <code>\</code><code>text</code><em><code>xx</em></code> command from them. Thus <code>\</code><code>bfseries</code> becomes <code>\</code><code>textbf{</code><em>text</em><code>}</code>, <code>\</code><code>itshape</code> becomes <code>\</code><code>textit{</code><em>text</em><code>}</code>, and <code>\</code><code>ttfamily</code> @@ -98,19 +98,19 @@ for a bold slanted instance of the current family (note the italic correction applied at the end of the modal command group, again). <p/>The new commands (as noted above) override commands of the same type. In almost all cases, this merely excludes ludicrous ideas such as -“upright slanted” fonts, or “teletype roman” fonts. There are a +“upright slanted” fonts, or “teletype roman” fonts. There are a couple of immediate oddities, though. The first is the conflict between <code>\</code><code>itshape</code> (or <code>\</code><code>slshape</code>) and <code>\</code><code>scshape</code>: while many claim that an italic small-caps font is typographically unsound, such -fonts do exist. Daniel Taupin’s <i>smallcap</i> package enables +fonts do exist. Daniel Taupin’s <i>smallcap</i> package enables use of the instances in the <a href="FAQ-ECfonts.html">EC fonts</a>, and similar techniques could be brought to bear on many other font sets. The second is the conflict between <code>\</code><code>upshape</code> and <code>\</code><code>itshape</code>: Knuth actually offers an upright-italic font which LaTeX uses for -the “£” symbol in the default font set. The combination is -sufficiently weird that, while there’s a defined font shape, no +the “£” symbol in the default font set. The combination is +sufficiently weird that, while there’s a defined font shape, no default LaTeX commands exist; to use the shape, the (eccentric) user -needs LaTeX’s simplest font selection commands: +needs LaTeX’s simplest font selection commands: <blockquote> <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html index 77549595a86..38664125d46 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html @@ -2,23 +2,23 @@ <title>UK TeX FAQ -- question label 8000</title> </head><body> <h3>Mismatched mode ljfour and resolution 8000</h3> -<p/>You’re running <i>dvips</i>, and you encounter a stream of error -messages, starting with “<code>Mismatched mode</code>”. The mode is the -default used in your installation — it’s set in the <i>dvips</i> -configuration file, and <code>ljfour</code> is commonest (since it’s the +<p/>You’re running <i>dvips</i>, and you encounter a stream of error +messages, starting with “<code>Mismatched mode</code>”. The mode is the +default used in your installation — it’s set in the <i>dvips</i> +configuration file, and <code>ljfour</code> is commonest (since it’s the default in most distributions), but not invariable. <p/>The problem is that <i>dvips</i> has encountered a font for which -it must generate a bitmap (since it can’t find it in Type 1 format), +it must generate a bitmap (since it can’t find it in Type 1 format), and there is no proforma available to provide instructions to give to Metafont. -<p/>So what to do? The number 8000 comes from the ‘<code>-Ppdf</code>’ option +<p/>So what to do? The number 8000 comes from the ‘<code>-Ppdf</code>’ option to <i>dvips</i>, which you might have found from the answer -<a href="FAQ-fuzzy-type3.html">“wrong type of fonts”</a>. The obvious -solution is to switch to the trivial substitute ‘<code>-Pwww</code>’, +<a href="FAQ-fuzzy-type3.html">“wrong type of fonts”</a>. The obvious +solution is to switch to the trivial substitute ‘<code>-Pwww</code>’, which selects the necessary type 1 fonts for PDF generation, but nothing else: however, this will leave you with undesirable bitmap -fonts in your PDF file. The “proper” solution is to find a +fonts in your PDF file. The “proper” solution is to find a way of expressing what you want to do, using type 1 fonts. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html index 2f1467c4829..810472f8285 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html @@ -3,8 +3,8 @@ </head><body> <h3>What are the AMS packages (AMSTeX, <em>etc</em>.)?</h3> <p/>AMSTeX is a TeX macro package, originally written by Michael Spivak for -the American Mathematical Society (AMS) during 1983–1985 and -is described in the book “<a href="FAQ-books.html">The Joy of TeX</a>”. +the American Mathematical Society (AMS) during 1983–1985 and +is described in the book “<a href="FAQ-books.html">The Joy of TeX</a>”. It is based on Plain TeX, and provides many features for producing more professional-looking maths formulas with less burden on authors. It pays attention to the finer details of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html index c5029e60f5b..53aa29d2a40 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html @@ -4,13 +4,13 @@ <h3>BibTeX Documentation</h3> <p/>BibTeX, a program originally designed to produce bibliographies in conjunction with LaTeX, is explained in Section 4.3 and Appendix B -of Leslie Lamport’s LaTeX manual. -The document “BibTeXing”, contained in the file <i>btxdoc.tex</i>, -expands on the chapter in Lamport’s book. <em>The LaTeX Companion</em> +of Leslie Lamport’s LaTeX manual. +The document “BibTeXing”, contained in the file <i>btxdoc.tex</i>, +expands on the chapter in Lamport’s book. <em>The LaTeX Companion</em> also has information on BibTeX and writing BibTeX style files. (See <a href="FAQ-books.html">TeX-related books</a> for details of both books.) -<p/>The document “Designing BibTeX Styles”, contained in the file +<p/>The document “Designing BibTeX Styles”, contained in the file <i>btxhak.tex</i>, explains the postfix stack-based language used to write BibTeX styles (<i>.bst</i> files). The file <i>btxbst.doc</i> is the template for the four standard styles (<i>plain</i>, @@ -18,7 +18,7 @@ is the template for the four standard styles (<i>plain</i>, contains their documentation. The complete BibTeX documentation set (including all the files above) is available on CTAN. <p/>A useful tutorial of the whole process of using BibTeX is Nicolas -Markey’s “<em>Tame the BeaST (The B to X of BibTeX)</em>”, which +Markey’s “<em>Tame the BeaST (The B to X of BibTeX)</em>”, which may also be found on CTAN. A summary and FAQ (<i>btxFAQ</i>), by Michael Shell and David Hoadley, is also to be recommended. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html index 893c7410cfa..f13024d1208 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label CD</title> </head><body> <h3>The TeX collection</h3> -<p/>If you don’t have access to the Internet, there are obvious +<p/>If you don’t have access to the Internet, there are obvious attractions to TeX collections on a disc. Even those with net access will find large quantities of TeX-related files to hand a great convenience. @@ -18,7 +18,7 @@ is distributed on DVD, and contains: <a href="http://www.uoregon.edu/~koch/texshop/">the TeXShop front-end</a> and other Mac-specific tools; <li> ProTeXt: an easy to install TeX system for Windows, based - on MiKTeX, and including an ‘active’ document to guide + on MiKTeX, and including an ‘active’ document to guide installation; and <li> A snapshot of CTAN. </ul> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html index e299fe90683..279d0c38daf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html @@ -8,18 +8,18 @@ the encoding is used as an index into tables within the font. For various reasons, Knuth chose deeply eccentric encodings for his Computer Modern family of fonts; in particular, he chose different encodings for different fonts, so that the application using the fonts -has to remember which font of the family it’s using before selecting a +has to remember which font of the family it’s using before selecting a particular glyph. <p/>When TeX version 3 arrived, most of the excuses for the -eccentricity of Knuth’s encodings went away, and at TUG’s Cork +eccentricity of Knuth’s encodings went away, and at TUG’s Cork meeting, an encoding for a set of 256 glyphs, for use in TeX text, -was defined. The intention was that these glyphs should cover ‘most’ +was defined. The intention was that these glyphs should cover ‘most’ European languages that use Latin alphabets, in the sense of including -all accented letters needed. (Knuth’s CMR fonts missed things +all accented letters needed. (Knuth’s CMR fonts missed things necessary for Icelandic and Polish, for example, but the Cork -fonts have them. Even Cork’s coverage isn’t complete: it misses +fonts have them. Even Cork’s coverage isn’t complete: it misses letters from Romanian, Eastern and Northern Sami, and Welsh, at -least. The Cork encoding does contain “NG” glyphs that +least. The Cork encoding does contain “NG” glyphs that allows it to support Southern Sami.) LaTeX refers to the Cork encoding as T1, and provides the means to use fonts thus encoded to avoid problems with @@ -28,7 +28,7 @@ the interaction of accents and hyphenation <p/>The only Metafont-fonts that conform to the Cork encoding are the EC fonts. They look CM-like, though their metrics differ from CM-font metrics in several areas. The fonts are -now regarded as ‘stable’ (in the same sense that the CM fonts +now regarded as ‘stable’ (in the same sense that the CM fonts are stable: their metrics are unlikely ever to change). Their serious disadvantages for the casual user are their size (each EC font is roughly twice the size of the corresponding CM font), and @@ -38,26 +38,26 @@ versions of the fonts, but EC or EC-equivalent fonts in Type 1 or TrueType form (the latter only from <a href="FAQ-commercial.html">commercial suppliers</a>). -Free <a href="FAQ-textrace.html">auto-traced versions</a> — the CM-super +Free <a href="FAQ-textrace.html">auto-traced versions</a> — the CM-super and the LGC fonts, and the Latin Modern series (rather directly generated from Metafont sources), are available. <p/> -Note that the Cork encoding doesn’t cover mathematics (and neither do -“T1-encoded” font families, of course). If you’re using -Computer-Modern-alike fonts, this doesn’t actually matter: your system +Note that the Cork encoding doesn’t cover mathematics (and neither do +“T1-encoded” font families, of course). If you’re using +Computer-Modern-alike fonts, this doesn’t actually matter: your system will have the original Computer Modern mathematical fonts (or the those -distributed with the Latin Modern set), which cover ‘basic’ +distributed with the Latin Modern set), which cover ‘basic’ TeX mathematics; more advanced mathematics are likely to need separate fonts anyway. Suitable mathematics fonts for use with other font families are discussed in -“<a href="FAQ-psfchoice.html">choice of scalable fonts</a>”. +“<a href="FAQ-psfchoice.html">choice of scalable fonts</a>”. <p/>The EC fonts are distributed with a -set of ‘Text Companion’ (TC) fonts that provide glyphs for +set of ‘Text Companion’ (TC) fonts that provide glyphs for symbols commonly used in text. The TC fonts are encoded according to the LaTeX TS1 encoding, and are not viewed as -‘stable’ in the same way as are the EC fonts are. +‘stable’ in the same way as are the EC fonts are. <p/>The Cork encoding is also implemented by virtual fonts provided in the <a href="FAQ-usepsfont.html">PSNFSS system</a>, for Adobe Type 1 fonts, and also by most other such fonts that have been developed (or otherwise diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html index 2ba04cf2681..4e82d3ae841 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html @@ -7,7 +7,7 @@ contains a driver for the LaserJet, <i>dvihplj</i>. <p/>Version 2.10 of the Beebe drivers supports the LaserJet. These drivers will compile under Unix, VMS, and on the Atari ST and DEC-20s. -<p/>For Unix systems, Karl Berry’s <i>dviljk</i> uses the same +<p/>For Unix systems, Karl Berry’s <i>dviljk</i> uses the same path-searching library as <i>web2c</i>. <dl> <dt><tt><i>Beebe drivers</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/beebe.zip">dviware/beebe</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/beebe/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html index 10fc2d614f4..5d229b72974 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html @@ -6,30 +6,30 @@ documents. However, it is important to realize the difference between page layout and functional markup. TeX is capable of extremely detailed page layout; HTML is not, because HTML is a -functional markup language not a page layout language. HTML’s exact +functional markup language not a page layout language. HTML’s exact rendering is not specified by the document that is published but is, to some degree, left to the discretion of the browser. If you require your readers to see an exact replication of what your document looks like to you, then you cannot use HTML and you must use some other publishing format such as PDF. That is true for any HTML authoring tool. -<p/>TeX’s excellent mathematical capabilities remain a challenge in the +<p/>TeX’s excellent mathematical capabilities remain a challenge in the business of conversion to HTML. There are only two generally reliable techniques for generating mathematics on the web: creating -bitmaps of bits of typesetting that can’t be translated, and using +bitmaps of bits of typesetting that can’t be translated, and using symbols and table constructs. Neither technique is entirely satisfactory. Bitmaps lead to a profusion of tiny files, are slow to load, and are inaccessible to those with visual disabilities. The symbol fonts offer poor coverage of mathematics, and their use requires configuration of the browser. The future of mathematical -browsing may be brighter — see +browsing may be brighter — see <a href="FAQ-mathml.html">future Web technologies</a>. <p/>For today, possible packages are: <dl> <dt><i>LaTeX2HTML</i><dd>a <i>Perl</i> script package that supports LaTeX only, and generates mathematics (and other - “difficult” things) using bitmaps. The original version was + “difficult” things) using bitmaps. The original version was written by Nikos Drakos for Unix systems, but the package now sports an illustrious list of co-authors and is also available for Windows systems. Michel Goossens and Janne Saarela published a detailed @@ -48,8 +48,8 @@ browsing may be brighter — see bitmaps for mathematics, but can also use other technologies where appropriate. Written by Eitan Gurari, it parses the DVI file generated when you run (La)TeX over your file with - <i>tex4ht</i>’s macros included. As a result, it’s pretty - robust against the macros you include in your document, and it’s + <i>tex4ht</i>’s macros included. As a result, it’s pretty + robust against the macros you include in your document, and it’s also pretty fast. <dt><i>plasTeX</i><dd>a Python-based LaTeX document processing framework. It gives DOM-like access to a LaTeX document, as @@ -62,7 +62,7 @@ browsing may be brighter — see <dt><i>Hevea</i><dd> a compiled program that supports LaTeX only, and uses the font/table technique for equations (indeed its entire approach is very similar to <i>TtH</i>). It is written - in Objective CAML by Luc Maranget. <i>Hevea</i> isn’t + in Objective CAML by Luc Maranget. <i>Hevea</i> isn’t archived on CTAN; details (including download points) are available via <a href="http://pauillac.inria.fr/~maranget/hevea/">http://pauillac.inria.fr/~maranget/hevea/</a> </dl> @@ -70,8 +70,8 @@ An interesting set of samples, including conversion of the same text by the four free programs listed above, is available at <a href="http://www.mayer.dial.pipex.com/samples/example.htm">http://www.mayer.dial.pipex.com/samples/example.htm</a>; a linked page gives lists of pros and cons, by way of comparison. -<p/>The World Wide Web Consortium maintains a list of “filters” to -HTML, with sections on (La)TeX and BibTeX — see +<p/>The World Wide Web Consortium maintains a list of “filters” to +HTML, with sections on (La)TeX and BibTeX — see <a href="http://www.w3.org/Tools/Word_proc_filters.html">http://www.w3.org/Tools/Word_proc_filters.html</a> <dl> <dt><tt><i>latex2html</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/latex2html/">support/latex2html/</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html index 496ff116c8c..2323bf667f5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html @@ -9,27 +9,27 @@ principles pioneered by Leslie Lamport in the current LaTeX. The new system is (provisionally) called LaTeX3; it will remain freely available and it will be fully documented at all levels. -<p/>The LaTeX team’s first product (LaTeX2e) was delivered in 1994 -(it’s now properly called “LaTeX”, since no other version is current). +<p/>The LaTeX team’s first product (LaTeX2e) was delivered in 1994 +(it’s now properly called “LaTeX”, since no other version is current). <p/>LaTeX2e was intended as a consolidation exercise, unifying several -sub-variants of LaTeX while changing nothing whose change wasn’t +sub-variants of LaTeX while changing nothing whose change wasn’t absolutely necessary. This has permitted the team to support a single version of LaTeX, in parallel with development of LaTeX3. <p/>Some of the older discussion papers about directions for LaTeX3 are to be found on CTAN; other (published) articles are to be found on the project web site (<a href="http://www.latex-project.org/papers/">http://www.latex-project.org/papers/</a>), -as is some of the project’s experimental code (see +as is some of the project’s experimental code (see <a href="http://www.latex-project.org/code.html">http://www.latex-project.org/code.html</a>, which allows you to read -the project’s source repository). Snapshots of two major collections +the project’s source repository). Snapshots of two major collections from the code, <i>expl3</i> (supporting LaTeX3 coding conventions in a LaTeX2e environment) and and <i>xpackages</i> (a -first cut of a “document designer’s interface”) are available on +first cut of a “document designer’s interface”) are available on CTAN. Several developers are known to be working on their own code using <i>expl3</i>, but all <p/>Anyone may participate in discussions of the future of LaTeX through the mailing list <code>latex-l</code>; some development work (outside the project) is discussed on the list. Subscribe to the list -by sending a message ‘<code>subscribe latex-l <<em>your name</em>></code>’ +by sending a message ‘<code>subscribe latex-l <<em>your name</em>></code>’ to <a href="mailto:listserv@urz.Uni-Heidelberg.de"><i>listserv@urz.Uni-Heidelberg.de</i></a> <dl> <dt><tt><i>expl3 bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3.zip">macros/latex/contrib/expl3</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html index ab94f60b823..edd9d9414c7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html @@ -4,11 +4,11 @@ <h3>How does LaTeX relate to Plain TeX?</h3> <p/>LaTeX is a program written in the programming language TeX. (In the same sense, any LaTeX document is also a program, which is -designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor +designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor you prefer.) <p/>Plain TeX is also a program written in the programming language TeX. -<p/>Both exist because writing your documents in ‘raw’ TeX would +<p/>Both exist because writing your documents in ‘raw’ TeX would involve much reinventing of wheels for every document. They both serve as convenient aids to make document writing more pleasant: LaTeX is a far more extensive aid. @@ -18,7 +18,7 @@ minor modifications (though some will require substantial work). <p/>Interpretation of any (La)TeX program involves some data-driven elements, and LaTeX has a wider range of such elements than does Plain TeX. As a result, the mapping from LaTeX to Plain TeX -is far less clear than that in the other direction — see a later +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>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html index ac18ce88ac6..b0eb3ad36c4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label LaTeXtoPlain</title> </head><body> <h3>Translating LaTeX to Plain TeX</h3> -<p/>Unfortunately, no “general”, simple, automatic process is likely to +<p/>Unfortunately, no “general”, simple, automatic process is likely to succeed at this task. See -“<a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX</a>” +“<a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX</a>” for further details. <p/>Translating a document designed to work with LaTeX into one designed to work with Plain TeX is likely to amount to carefully @@ -17,12 +17,12 @@ LaTeX graphics package to Plain TeX. However, while <a href="FAQ-eplain.html">Eplain</a> system a useful source of code. (In fact, a light-weight system such as Eplain might reasonably be adopted as an alternative target of translation, though it undoubtedly gives the -user more than the “bare minimum” that Plain TeX is designed to +user more than the “bare minimum” that Plain TeX is designed to offer.) <dl> <dt><tt><i>\latexhtml{\textrm{The}}{The} eplain system</i></tt><dd> <a href="http://www.tex.ac.uk/tex-archive/macros/eplain.zip">macros/eplain</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse the directory</a>) -<dt><tt><i>\latexhtml{\textrm{‘Plain TeX’}}{Plain TeX} graphics</i></tt><dd> +<dt><tt><i>\latexhtml{\textrm{‘Plain TeX’}}{Plain TeX} graphics</i></tt><dd> <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse the directory</a>) </dl> <p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html index 45a0be06dd8..373eadc5088 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html @@ -5,13 +5,13 @@ <p/>Metafont was written by Knuth as a companion to TeX; whereas TeX defines the layout of glyphs on a page, Metafont defines the shapes of the glyphs and the relations between them. Metafont details the sizes of -glyphs, for TeX’s benefit, and details the rasters used to +glyphs, for TeX’s benefit, and details the rasters used to represent the glyphs, for the benefit of programs that will produce printed output as post processes after a run of TeX. -<p/>Metafont’s language for defining fonts permits the expression of several +<p/>Metafont’s language for defining fonts permits the expression of several classes of things: first (of course), the simple geometry of the glyphs; second, the properties of the print engine for which the -output is intended; and third, ‘meta’-information which can +output is intended; and third, ‘meta’-information which can distinguish different design sizes of the same font, or the difference between two fonts that belong to the same (or related) families. <p/>Knuth (and others) have designed a fair range of fonts using Metafont, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html index c4ccf432443..46d8c42e3a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html @@ -12,10 +12,10 @@ mathematics with the graphics. (Knuth tells us that he uses nothing but MetaPost for diagrams in text that he is writing.) <p/>Although PDFLaTeX cannot ordinarily handle PostScript graphics, the output of MetaPost is sufficiently simple and regular that PDFLaTeX -can handle it direct, using code borrowed from ConTeXt — see +can handle it direct, using code borrowed from ConTeXt — see <a href="FAQ-pdftexgraphics.html">graphics in PDFLaTeX</a>. -<p/>Much of MetaPost’s source code was copied from Metafont’s sources, with -Knuth’s permission. +<p/>Much of MetaPost’s source code was copied from Metafont’s sources, with +Knuth’s permission. <p/>A mailing list discussing MetaPost is available; subscribe via the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html index a04b2b25ff3..496b537cdf1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html @@ -12,7 +12,7 @@ displaying bitmap PK fonts, but current versions of <p/>Other (free) previewers of the current generation offer automatic generation of the requisite PK files (using <i>gsftopk</i>, -or similar, behind the scenes). If your previewer isn’t capable of +or similar, behind the scenes). If your previewer isn’t capable of this, you have three options: <ul> <li> Convert the DVI file to PostScript and use a diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html index f8a079ed388..768c9223799 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html @@ -20,14 +20,14 @@ following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.7 $ % or any RCS keyword -\RCS$Date: 2010/01/19 22:44:39 $ +\RCS$Revision: 1.13 $ % or any RCS keyword +\RCS$Date: 2010/04/02 18:20:00 $ ... \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> @@ -51,8 +51,8 @@ cause <code>\</code><code>maketitle</code> use the date that has been written in <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’ +<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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html index c24234e51a2..9e1cb205a95 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html @@ -10,7 +10,7 @@ transformations and formatting, but this has not yet been widely implemented. Some SGML authoring systems (e.g., SoftQuad <i>Author/Editor</i>) have formatting abilities, and -there are high-end specialist SGML typesetting systems (e.g., Miles33’s +there are high-end specialist SGML typesetting systems (e.g., Miles33’s <i>Genera</i>). However, the majority of SGML users probably transform the source to an existing typesetting system when they want to print. TeX is a good candidate for this. There are three approaches to writing a @@ -24,7 +24,7 @@ translator: They are expensive, but powerful, incorporating SGML query and transformation abilities as well as simple translation. <li> Build a translator on top of an existing SGML parser. By far - the best-known (and free!) parser is James Clark’s + the best-known (and free!) parser is James Clark’s <i>nsgmls</i>, and this produces a much simpler output format, called ESIS, which can be parsed quite straightforwardly (one also has the benefit of an SGML parse against the DTD). Two @@ -32,25 +32,25 @@ translator: <ul> <li> - David Megginson’s + David Megginson’s <a href="http://www.perl.com/CPAN/modules/by-module/SGMLS"><i>sgmlspm</a></i>, written in <i>Perl</i> 5. <li> - Joachim Schrod and Christine Detig’s + Joachim Schrod and Christine Detig’s <a href="ftp://ftp.tu-darmstadt.de/pub/text/sgml/stil"><i>STIL</a></i>, - (‘SGML Transformations in Lisp’). + (‘SGML Transformations in Lisp’). </ul> - Both of these allow the user to write ‘handlers’ for every SGML + Both of these allow the user to write ‘handlers’ for every SGML element, with plenty of access to attributes, entities, and information about the context within the document tree. -<p/> If these packages don’t meet your needs for an average SGML +<p/> If these packages don’t meet your needs for an average SGML typesetting job, you need the big commercial stuff. </ol> <p/>Since HTML is simply an example of SGML, we do not need a specific system for HTML. However, Nathan Torkington developed -<i>html2latex</i> from the HTML parser in NCSA’s +<i>html2latex</i> from the HTML parser in NCSA’s Xmosaic package. The program takes an HTML file and generates a LaTeX file from it. The conversion code is subject to NCSA restrictions, but the whole diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html index f33711fd008..61aecddd166 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html @@ -8,23 +8,23 @@ journal <i>TUGboat</i> continues in regular publication with articles about TeX, Metafont and related technologies, and about document design, processing and production. TUG holds a yearly conference, whose proceedings are published in <i>TUGboat</i>. -<p/>TUG’s <a href="http://www.tug.org">web site</a> is a valuable +<p/>TUG’s <a href="http://www.tug.org">web site</a> is a valuable resource for all sorts of TeX-related matters, such as details of TeX software, and lists of TeX vendors and TeX consultants. Back articles from <i>TUGboat</i> are slowly (subject to copyright issues, etc.) making their way to the site, too. -<p/>Some time ago, TUG established a “technical council”, whose +<p/>Some time ago, TUG established a “technical council”, whose task was to oversee the development of TeXnical projects. Most such projects nowadays go on their way without any support from -TUG, but TUG’s web site lists its +TUG, but TUG’s web site lists its <a href="http://www.tug.org/twg.html">Technical Working Groups (TWGs)</a>. <p/>TUG has a reasonable claim to be considered a world-wide organisation, but there are many national and regional user groups, -too; TUG’s web site maintains a list of +too; TUG’s web site maintains a list of -<a href="http://www.tug.org/lugs.html">“local user groups” (LUGs)</a>. +<a href="http://www.tug.org/lugs.html">“local user groups” (LUGs)</a>. <p/>Contact TUG itself via: <blockquote> TeX Users Group<br> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html index 5d40b681695..46cd3d122b4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html @@ -7,10 +7,10 @@ he will continue to fix any bugs that are reported to him (though bugs are rare). This decision was made soon after TeX version 3.0 was released; at each bug-fix release the version number acquires one more digit, so that it tends to the -limit pi (at the time of writing, Knuth’s latest release +limit pi (at the time of writing, Knuth’s latest release is version 3.1415926). Knuth wants TeX to be frozen at version pi when he dies; thereafter, no further changes -may be made to Knuth’s source. (A similar rule is applied to Metafont; +may be made to Knuth’s source. (A similar rule is applied to Metafont; its version number tends to the limit e, and currently stands at 2.718281.) <p/>Knuth explains his decision, and exhorts us all to respect it, in a @@ -24,12 +24,15 @@ projects: see, for example, to build substantial new macro packages based on TeX. For the even longer term, there -are various projects to build a <em>successor</em> to TeX; see, for example, -the - -<a href="FAQ-luatex.html">LuaTeX</a>, -<a href="FAQ-omegaleph.html">Omega/Aleph</a> and -<a href="FAQ-extex.html">ExTeX</a> - projects. +are various projects to build a <em>successor</em> to TeX. The +<a href="FAQ-etex.html">e-TeX</a> extension to TeX itself arose from such a +project (NTS). Another pair of projects, which have delivered +all the results they are likely to deliver, is the related +<a href="FAQ-omegaleph.html">Omega and Aleph</a>. The +<a href="FAQ-xetex.html">XeTeX system</a> is in principle still under +development, but is widely used, and the +<a href="FAQ-luatex.html">LuaTeX project</a> (though with another two years of +development scheduled) has already delivered a system that is quite +useful. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html index 2da01c865cf..b9b8ad7b430 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html @@ -1,19 +1,19 @@ <head> <title>UK TeX FAQ -- question label TeXpronounce</title> </head><body> -<h3>How should I pronounce “TeX”?</h3> -<p/>The ‘X’ is “really” the Greek letter +<h3>How should I pronounce “TeX”?</h3> +<p/>The ‘X’ is “really” the Greek letter Chi, and is pronounced by -English-speakers either a bit like the ‘ch’ in the Scots word ‘loch’ -([x] in the IPA) or (at a pinch, if you can’t do the Greek sound) like -‘k’. It definitely is not pronounced ‘ks’ (the Greek letter with that -sound doesn’t look remotely like the Latin alphabet ‘X’). -<p/>This curious usage derives from Knuth’s explanation in the TeXbook -that the name comes from the Greek word for ‘art’ or ‘craft’ -(‘<em>techni</em>’), -which is the root of the English word ‘technology’. Knuth’s logo for TeX is +English-speakers either a bit like the ‘ch’ in the Scots word ‘loch’ +([x] in the IPA) or (at a pinch, if you can’t do the Greek sound) like +‘k’. It definitely is not pronounced ‘ks’ (the Greek letter with that +sound doesn’t look remotely like the Latin alphabet ‘X’). +<p/>This curious usage derives from Knuth’s explanation in the TeXbook +that the name comes from the Greek word for ‘art’ or ‘craft’ +(‘<em>techni</em>’), +which is the root of the English word ‘technology’. Knuth’s logo for TeX is merely the uppercase version of the first three (Greek) letters of the -word, jiggled about a bit; we don’t use that logo (and logos like it) +word, jiggled about a bit; we don’t use that logo (and logos like it) in this FAQ (see <a href="FAQ-logos.html">Typesetting TeX-related logos</a>). <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html index 4c178a90300..d45900e5b89 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html @@ -6,7 +6,7 @@ <p/>We list here the free or shareware packages; another question addresses - <a href="FAQ-commercial.html">commercial TeX vendors’</a> products. + <a href="FAQ-commercial.html">commercial TeX vendors’</a> products. <dl> <dt>Unix<dd> The only current distribution of TeX for Unix systems (including GNU/Linux and other free Unix-like systems) is @@ -15,11 +15,11 @@ <p/> Members of many TeX user groups receive copies of the collection (on DVD), as part of their membership of the groups. <p/> MacOS/X is also a Unix-based system; however users should refer to - the information below, under item “Mac”. -<p/> TeX Live may also be installed “over the network”; a network + the information below, under item “Mac”. +<p/> TeX Live may also be installed “over the network”; a network installer is provided, and once you have a system, a manager (<i>tlmgr</i>) can both keep your installation up-to-date and - add packages you didn’t install at first. + add packages you didn’t install at first. <p/> <dl> <dt><tt><i>texlive</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a> <dt><tt><i>texlive installer (Unix)</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/texlive/tlnet/install-tl-unx.tar.gz">systems/texlive/tlnet/install-tl-unx.tar.gz</a> @@ -29,7 +29,7 @@ <p/> A free version of the commercial <a href="FAQ-commercial.html">VTeX extended TeX system</a> is available for use under Linux, which among other things specialises in direct - production of PDF from (La)TeX input. Sadly, it’s no + production of PDF from (La)TeX input. Sadly, it’s no longer supported, and the ready-built images are made for use with a rather ancient Linux kernel. <p/> In addition, the developer of MiKTeX has released a port of the @@ -49,15 +49,15 @@ The current version is available for file-by-file download (the HTML files in the directory offer hints on what you need to get going). MiKTeX can automatically install packages that it - “knows about”, but that aren’t in your system (it gets them over + “knows about”, but that aren’t in your system (it gets them over the network). Furthermore, users may keep their installation - up-to-date, over the network: the distribution contains a “package - manager”, through which the user may select individual packages, or + up-to-date, over the network: the distribution contains a “package + manager”, through which the user may select individual packages, or request that every extant update be retrieved. <p/> MiKTeX may also be used in a configuration which involves no - installation at all: its “portable” distribution may be unpacked + installation at all: its “portable” distribution may be unpacked on a memory stick, and used on any windows computer without making - any direct use of the hard drive. This is the first “official” + any direct use of the hard drive. This is the first “official” release of such a setup, though a similar object has been available on the net for some time. <p/> The MiKTeX developers also provide a ready-to-run copy of the @@ -83,7 +83,7 @@ Windows environment. Configuration is provided so that the resulting set of programs runs out-of-the-box. <p/> The (Japanese) W32TEX distribution was motivated by - the needs of Japanese users (Japanese won’t fit in a “simple” + the needs of Japanese users (Japanese won’t fit in a “simple” character set like ASCII, but TeX is based on a version of ASCII). Despite its origins, W32TEX is said to be a good bet for Western users, notably those whose disks are short @@ -96,7 +96,7 @@ is available. If you run CygWin on your Windows machine, you have the option of using TeX Live, too (you will need the X-server, to run <i>xdvi</i>). Of course, TeX Live components will look like - Unix applications (of course, that’s presumably what you wanted), + 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 @@ -108,9 +108,9 @@ TeX, which further the focus. <dl> <dt><tt><i>bakoma</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/bakoma/">systems/win32/bakoma/</a> - <dt><tt><i>miktex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex.zip">systems/win32/miktex</a> (or <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex/">browse the directory</a>); acquire <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a> (also - available from the MiKTeX web site), and read installation - instructions from + <dt><tt><i>miktex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex.zip">systems/win32/miktex</a> (or <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex/">browse the directory</a>); + acquire <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a> (also available from the MiKTeX + web site), and read installation instructions from <a href="http://www.miktex.org/2.8/setup">the MiKTeX installation page</a> <dt><tt><i>Portable miktex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex/setup/miktex-portable.exe">systems/win32/miktex/setup/miktex-portable.exe</a> <dt><tt><i>protext.exe</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/protext/">systems/win32/protext/</a> @@ -128,7 +128,7 @@ <p/> A version of emTeX, packaged to use a <a href="FAQ-tds.html">TDS directory structure</a>, is separately available as - an emTeX ‘contribution’. Note that neither emTeX itself, nor + an emTeX ‘contribution’. Note that neither emTeX itself, nor emTeXTDS, is maintained. Most users of Microsoft operating systems, who want an up-to-date (La)TeX system, need to migrate to Win32-based systems. @@ -184,7 +184,7 @@ <p/> A useful <a href="http://www.esm.psu.edu/mac-tex/">resource for Mac users</a> - has a news and ‘help’ section, as well as details of systems and + has a news and ‘help’ section, as well as details of systems and tools. The MacTeX-on-OSX mailing list is a useful resource for users; mail <a href="mailto:MacOSX-TeX-on@email.esm.psu.edu"><i>MacOSX-TeX-on@email.esm.psu.edu</i></a> to subscribe. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html index aaa3fbd52d7..6b8ef37b23c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label WYGexpts</title> </head><body> <h3>The TeX document preparation environment</h3> -<p/><p/>“<a href="FAQ-notWYSIWYG.html">Why TeX is not WYSIWYG</a>” +<p/><p/>“<a href="FAQ-notWYSIWYG.html">Why TeX is not WYSIWYG</a>” outlines the reasons (or excuses) for the huge disparity of user -interface between “typical” TeX environments and commercial word +interface between “typical” TeX environments and commercial word processors. <p/>Nowadays, at last, there is a range of tools available that try either to bridge or to close the gap. One range modestly focuses on providing the user with a legible source document. At the other extreme we have <a href="http://www.texmacs.org"><i>TeXmacs</a></i>, a document processor using -TeX’s algorithms and fonts for both editor display and printing. +TeX’s algorithms and fonts for both editor display and printing. <i>TeXmacs</i> does not use the TeX language itself (though among other formats, LaTeX may be exported and imported). A bit closer to LaTeX is @@ -41,7 +41,7 @@ screen. <p/>A different type of tool focuses on making update and access to previews of the typeset document more immediate. A recent addition in several viewers, editors and TeX executables are so-called -‘source specials’ for cross-navigation. When TeX compiles a +‘source specials’ for cross-navigation. When TeX compiles a document, it will upon request insert special markers for every input line into the typeset output. The markers are interpreted by the DVI previewer which can be made to let its display track the page @@ -74,7 +74,7 @@ buffer but uses actual previews rendered by LaTeX. system is only available on request from its author; it continuously updates its screen with the help of a special version of TeX dumping its state in a compressed format at each page and -using hooks into TeX’s line breaking mechanism for reformatting +using hooks into TeX’s line breaking mechanism for reformatting paragraphs on the fly. That way, it can render the output from the edited TeX code with interactive speed on-screen, and it offers the possibility of editing directly in the preview window. @@ -89,7 +89,7 @@ separate window), degree of correspondence of the display to the final output, and the balance they strike between visual aid and visual distraction. <dl> -<dt><tt><i>preview-latex</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/support/auctex/">support/auctex/</a> +<dt><tt><i>preview-latex</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/support/auctex/">support/auctex/</a>; <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/preview-latex.html">catalogue entry</a> <dt><tt><i>texmacs</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/TeXmacs/">systems/unix/TeXmacs/</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html index fbfb5c43e07..2e4d1601672 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label abspos</title> </head><body> <h3>Putting things at fixed positions on the page</h3> -<p/>TeX’s model of the world is (broadly speaking) that the author +<p/>TeX’s model of the world is (broadly speaking) that the author writes text, and TeX and its macros decide how it all fits on the page. This is not good news for the author who has, from whatever source, a requirement that certain things go in exactly the right @@ -11,9 +11,9 @@ place on the page. and two LaTeX packages allow you position things relative to such points, thus providing a means of absolute positioning. <p/>The <i>textpos</i> package aids the construction of pages from -“blobs”, dotted around over the page (as in a poster); you give it +“blobs”, dotted around over the page (as in a poster); you give it the location, and it places your typeset box accordingly. -<p/>The <i>eso-pic</i> defines a “shipout picture” that covers the +<p/>The <i>eso-pic</i> defines a “shipout picture” that covers the page. The user may add <code>picture</code>-mode commands to this picture, which of course can include box placements as well as the other rather stilted commands of <code>picture</code>-mode. @@ -27,7 +27,7 @@ must therefore also be available.) <dl> <dt><tt><i>eso-pic.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic.zip">macros/latex/contrib/eso-pic</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic/">browse the directory</a>) -<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>) +<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/everyshi.html">catalogue entry</a> <dt><tt><i>textpos.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html index 53b0f91abaa..ec423373a26 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label acroantics</title> </head><body> <h3>Adobe <i>Reader</i> messing with print size</h3> -<p/><p/>Printing from Adobe <i>Reader</i> shrinks the page “to fit” -(<em>by default</em>). Unfortunately, its calculation doesn’t consider +<p/><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 +<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: <ul> <li> <i>Reader</i> version 7:<br> - Page Scaling (default: “Fit to printer margins”) — change to - “None”, and<br> - Scale (default 95textpercent of Normal size) — change to - “100%”. + Page Scaling (default: “Fit to printer margins”) — change to + “None”, and<br> + Scale (default 95textpercent of Normal size) — change to + “100%”. <li> Adobe Reader 6:<br> - in the print dialogue, on the “copies & pages” pane, you’ll find a - popup menu/drop-down list titled “Page Scaling” — change to “None”. + in the print dialogue, on the “copies & pages” pane, you’ll find a + popup menu/drop-down list titled “Page Scaling” — change to “None”. <li> Windows, Linux Acrobat (Reader) 5.0:<br> - In the print dialog, make sure the “Shrink oversized pages to fit” + In the print dialog, make sure the “Shrink oversized pages to fit” checkbox is unchecked. It may also be useful to uncheck the - “Expand small pages to fit paper size” checkbox as well. + “Expand small pages to fit paper size” checkbox as well. </ul> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acroantics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acroantics</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html index 85f7456945e..59fd0cdb317 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label acrobat</title> </head><body> <h3>Making Acrobat PDF documents from (La)TeX</h3> -<p/>There are three general routes to PDF output: Adobe’s original -‘distillation’ route (via PostScript output), conversion of a +<p/>There are three general routes to PDF output: Adobe’s original +‘distillation’ route (via PostScript output), conversion of a DVI file, and the use of a direct PDF generator such as <a href="FAQ-whatpdftex.html">PDFTeX</a>) or -MicroPress’s VTeX (which comes both as a +MicroPress’s VTeX (which comes both as a <a href="FAQ-commercial.html">commercial version</a> for Windows PCs, and as a -<a href="FAQ-TeXsystems.html">‘free’ version)</a> for OS/2 and Linux systems). +<a href="FAQ-TeXsystems.html">‘free’ version)</a> for OS/2 and Linux systems). <p/>For simple documents (with no hyper-references), you can either <ul> <li> process the document in the normal way, produce PostScript @@ -32,15 +32,15 @@ links, you need a LaTeX package to suitably redefine the internal commands. There are two of these for LaTeX, both capable of conforming to the <a href="FAQ-hyper.html">HyperTeX specification</a>: -Heiko Oberdiek’s <i>hyperref</i>, and Michael Mehlich’s +Heiko Oberdiek’s <i>hyperref</i>, and Michael Mehlich’s <i>hyper</i>. (In practice, almost everyone uses -<i>hyperref</i>; <i>hyper</i> hasn’t been updated since 2000.) +<i>hyperref</i>; <i>hyper</i> hasn’t been updated since 2000.) <i>Hyperref</i> can often determine how it should generate hypertext from its environment, but there is a wide set of configuration options you can give via <code>\</code><code>usepackage</code>. The package can operate using PDFTeX primitives, the hyperTeX <code>\</code><code>special</code>s, or DVI driver-specific <code>\</code><code>special</code> commands. -Both <i>dvips</i> and Y&Y’s <i>DVIPSONE</i> can +Both <i>dvips</i> and Y&Y’s <i>DVIPSONE</i> can translate the DVI with these <code>\</code><code>special</code> commands into PostScript acceptable to Distiller, and <i>dvipdfm</i> and <i>dvipdfmx</i> have <code>\</code><code>special</code> commands of @@ -50,22 +50,22 @@ help you create PDF documents with hyper-references. It can operate using PDFTeX primitives, or <code>\</code><code>special</code> commands for the <i>dvipdfm</i>/<i>dvipdfmx</i> DVI drivers. <p/>While there is no free implementation of all of <i>Adobe</i> -<i>Distiller</i>’s +<i>Distiller</i>’s functionality, any but the very oldest versions of <i>Ghostscript</i> provide pretty reliable distillation (but beware of the problems with <a href="FAQ-dvips-pdf.html"><i>dvips</i> output for distillation</a>). -<p/>For viewing (and printing) the resulting files, Adobe’s +<p/>For viewing (and printing) the resulting files, Adobe’s <i>Acrobat</i> <i>Reader</i> is available for a fair range of -platforms; for those for which Adobe’s reader is unavailable, remotely +platforms; for those for which Adobe’s reader is unavailable, remotely current versions of <i>ghostscript</i> combined with <i>gv</i> or <i>GSview</i> can display and print PDF files, as can <i>xpdf</i>. <p/>In many circumstances, <i>Ghostscript</i> combined with a viewer application is actually preferable to Acrobat Reader. For example, on -Windows Acrobat Reader locks the <code>.pdf</code> file it’s displaying: this +Windows Acrobat Reader locks the <code>.pdf</code> file it’s displaying: this makes the traditional (and highly effective) (La)TeX development -cycle of “Edit-> Process-> Preview” become -rather clumsy — <i>GSview</i> doesn’t make the same +cycle of “Edit-> Process-> Preview” become +rather clumsy — <i>GSview</i> doesn’t make the same mistake. <dl> <dt><tt><i>Acrobat Reader</i></tt><dd>browse diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html index 7d024d8dd5c..6ad40bc2d04 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label actinarg</title> </head><body> <h3>Active characters in command arguments</h3> -<p/>Occasionally, it’s nice to make one or two characters active in the +<p/>Occasionally, it’s nice to make one or two characters active in the argument of a command, to make it easier for authors to code the arguments. <p/>Active characters <em>can</em> be used safely in such situations; but @@ -15,7 +15,7 @@ in a macro for specifying chords. elsewhere in TeX (to say the least!), so that the characters can only be made active while the command is executing. <p/>Using the techniques discussed in -“<a href="FAQ-activechars.html">characters as commands</a>”, +“<a href="FAQ-activechars.html">characters as commands</a>”, we can define: <blockquote> <pre> @@ -37,7 +37,7 @@ and: </blockquote><p> The second problem is one of timing: the command has to make each character active <em>before</em> its arguments are read: this means that -the command can’t actually “have” arguments itself, but must be +the command can’t actually “have” arguments itself, but must be split in two. So we write: <blockquote> <pre> @@ -59,18 +59,18 @@ and we can use the command as <code>\</code><code>chord{F#}</code> or <ul> <li> <code>\</code><code>begingroup</code> in <code>\</code><code>chord</code> opens a group that is closed by <code>\</code><code>endgroup</code> in <code>\</code><code>Xchord</code>; this group limits the change of - category codes, which is the <em>raison d’être</em> of the whole + category codes, which is the <em>raison d’être</em> of the whole exercise. -<li> Although <code>#</code> is active while <code>\</code><code>Xchord</code> is executed, it’s - <em>not</em> active when it’s being defined, so that the use of <code>#1</code> - doesn’t require any special attention. +<li> Although <code>#</code> is active while <code>\</code><code>Xchord</code> is executed, it’s + <em>not</em> active when it’s being defined, so that the use of <code>#1</code> + doesn’t require any special attention. </ul> <p/>Note that the technique used in such macros as <code>\</code><code>chord</code>, here, is analogous to that used in such commands as <code>\</code><code>verb</code>; and, in just the same way as <code>\</code><code>verb</code> (see -“<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> doesn’t work in arguments</a>”), -<code>\</code><code>chord</code> won’t work inside the argument of another command (the +“<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> doesn’t work in arguments</a>”), +<code>\</code><code>chord</code> won’t work inside the argument of another command (the error messages, if they appear at all, will probably be rather odd). <p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html index 8ceaf24df9b..0308ebb2596 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html @@ -4,20 +4,29 @@ <h3>Defining characters as macros</h3> <p/>Single characters can act as macros (defined commands), and both Plain TeX and LaTeX define the character -“<code>~</code>” as a “non-breakable space”. A -character is made definable, or “active”, by setting its +“<code>~</code>” as a “non-breakable space”. A +character is made definable, or “active”, by setting its <em>category code</em> (catcode) to be <code>\</code><code>active</code> (13): -<code>\catcode‘_=\active</code>. -<p/>Any character could, in principle, be activated this way and defined -as a macro (<code>\</code><code>def</code><code>_{</code><code>\</code><code>_</code><code>}</code> — the simple answer to - -<a href="FAQ-underscore.html">using underscores</a>), but you must be +<blockquote> +<pre> +\catcode`\_=\active +</pre> +</blockquote><p> +Any character could, in principle, be activated this way and defined +as a macro: +<blockquote> +<pre> +\def_{\_} +</pre> +</blockquote><p> +which could be characterised as an over-simple answer to +<a href="FAQ-underscore.html">using underscores</a>. However, you must be wary: whereas people expect an active tilde, other active characters may be unexpected and interact badly with other macros. Furthermore, -by defining an active character, you preclude the character’s use for -other purposes, and there are few characters “free” to be subverted +by defining an active character, you preclude the character’s use for +other purposes, and there are few characters “free” to be subverted in this way. -<p/>To define the character “<code>z</code>” as a command, one would say something +<p/>To define the character “<code>z</code>” as a command, one would say something like: <blockquote> <pre> @@ -25,10 +34,10 @@ like: \def z{Yawn, I'm tired}% </pre> </blockquote><p> -and each subsequent “<code>z</code>” in the text would become a yawn. This would be +and each subsequent “<code>z</code>” in the text would become a yawn. This would be an astoundingly bad idea for most documents, but might have special -applications. (Note that, in “<code>\def z</code>”, “<code>z</code>” is no longer interpreted as -a letter; the space is therefore not necessary — “<code>\defz</code>” would do; we +applications. (Note that, in “<code>\def z</code>”, “<code>z</code>” is no longer interpreted as +a letter; the space is therefore not necessary — “<code>\defz</code>” would do; we choose to retain the space, for what little clarity we can manage.) Some LaTeX packages facilitate such definitions. For example, the <i>shortvrb</i> package with its <code>\</code><code>MakeShortVerb</code> command. @@ -42,17 +51,17 @@ purposes (the <code>\</code><code>verb</code> command does this), then the alter characters will not be interpreted properly when they appear in the argument to another command (as, for example, in -“<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> in command arguments</a>”). +“<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> in command arguments</a>”). An exemplary case is the <i>doc</i> package, which processes .dtx files using the <i>shortvrb</i> package to define -<code>|…|</code> as a shorthand for -<code>\</code><code>verb</code><code>|…|</code>. But <code>|</code> is +<code>|…|</code> as a shorthand for +<code>\</code><code>verb</code><code>|…|</code>. But <code>|</code> is also used in the preambles of tabular environments, so that tables in <code>.dtx</code> files can only have vertical line separation between columns by employing special measures of some sort. <p/>Another consequence is that catcode assignments made -in macros often don’t work as expected -(see “<a href="FAQ-actinarg.html">Active characters in command arguments</a>”). +in macros often don’t work as expected +(see “<a href="FAQ-actinarg.html">Active characters in command arguments</a>”). For example, the definition <blockquote> <pre> @@ -77,10 +86,10 @@ use: \endgroup </pre> </blockquote><p> -The alternative (“tricksy”) way of creating such an isolated +The alternative (“tricksy”) way of creating such an isolated definition depends on the curious properties of <code>\</code><code>lowercase</code>, which changes characters without altering their catcodes. Since there is -always <em>one</em> active character (“<code>~</code>”), we +always <em>one</em> active character (“<code>~</code>”), we can fool <code>\</code><code>lowercase</code> into patching up a definition without ever explicitly changing a catcode: <blockquote> @@ -109,12 +118,12 @@ special active <em>maths code</em>, as with </pre> </blockquote><p> The special character does not need to be redefined whenever it is -made active — the definition of the command persists even if the -character’s catcode reverts to its original value; the definition +made active — the definition of the command persists even if the +character’s catcode reverts to its original value; the definition becomes accessible again if the character once again becomes active. <dl> -<dt><tt><i>doc.sty</i></tt><dd>Distributed as part of the source of LaTeX, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base.zip">macros/latex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse the directory</a>) -<dt><tt><i>shortvrb.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>doc.sty</i></tt><dd>Part of the LaTeX distribution <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base.zip">macros/latex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/doc.html">catalogue entry</a> +<dt><tt><i>shortvrb.sty</i></tt><dd>Part of the LaTeX distribution <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base.zip">macros/latex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/shortvrb.html">catalogue entry</a> </dl> <p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html index d70605711fc..9d69f493457 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-addtoreset.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label addtoreset</title> </head><body> <h3>Master and slave counters</h3> -<p/>It’s common to have things numbered “per chapter” (for example, in +<p/>It’s common to have things numbered “per chapter” (for example, in the standard <i>book</i> and <i>report</i> classes, figures, tables and footnotes are all numbered thus). The process of resetting is -done automatically, when the “master” counter is stepped (when the +done automatically, when the “master” counter is stepped (when the <code>\</code><code>chapter</code> command that starts chapter <<i>n</i>> happens, the <code>chapter</code> counter is stepped, and all the dependent counters are set to zero). <p/>How would you do that for yourself? You might want to number algorithms per section, or corollaries per theorem, for example. If -you’re defining these things by hand, you declare the relationship +you’re defining these things by hand, you declare the relationship when you define the counter in the first place: <blockquote> <code>\</code><code>newcounter{</code><em>new-name</em><code>}[</code><em>master</em><code>]</code> @@ -19,7 +19,7 @@ when you define the counter in the first place: says that every time counter <<i>master</i>> is stepped, counter <<i>new-name</i>> will be reset. <p/>But what if you have an uncooperative package, that defines the -objects for you, but doesn’t provide a programmer interface to make +objects for you, but doesn’t provide a programmer interface to make the counters behave as you want? <p/>The <code>\</code><code>newcounter</code> command uses a LaTeX internal command, and you can also use it: @@ -44,14 +44,14 @@ command without its asterisk: </blockquote><p> 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 corollaries — there are potentially -many “corollary 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 +much any such counter-within-another; if you’re not using the <i>chngcntr</i>, refer to the answer to -<a href="FAQ-the-commands.html">redefining counters’ <code>\</code><code>the-</code>commands</a> for +<a href="FAQ-the-commands.html">redefining counters’ <code>\</code><code>the-</code>commands</a> for the necessary techniques. -<p/>Note that the technique doesn’t work if the master counter is <code>page</code>, +<p/>Note that the technique doesn’t work if the master counter is <code>page</code>, the number of the current page. The <code>page</code> counter is stepped deep inside the output routine, which usually gets called some time after the text for the new page has started to appear: so special @@ -64,11 +64,11 @@ may be applied to any counter. The command: </blockquote><p> will cause <<i>counter</i>> to be reset for each page. The package uses a label-like mechanism, and may require more than one run of LaTeX -to stabilise counter values — LaTeX will generate the usual +to stabilise counter values — LaTeX will generate the usual warnings about labels changing. <dl> -<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> -<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>) +<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr.zip">macros/latex/contrib/chngcntr</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr/">browse the directory</a>) +<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/perpage.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html index 37666a37636..0bcaee6c2df 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html @@ -4,18 +4,18 @@ <h3>Adobe font formats</h3> <!-- type1 type3 --> <p/>Adobe has specified a number of formats for files to represent fonts -in PostScript files; this question doesn’t attempt to be encyclopaedic, so +in PostScript files; this question doesn’t attempt to be encyclopaedic, so we only discuss the two formats most commonly encountered in the -(La)TeX context, types 1 and 3. In particular, we don’t discuss the +(La)TeX context, types 1 and 3. In particular, we don’t discuss the OpenType format, whose has many advantages have only in the last year or two been readily accessible to most (La)TeX users (by means of the widely-used <a href="FAQ-xetex.html">XeTeX</a> and the more experimental <a href="FAQ-luatex.html">LuaTeX</a>). <p/>Adobe Type 1 format specifies a means to represent outlines of the glyphs -in a font. The ‘language’ used is closely restricted, to ensure that +in a font. The ‘language’ used is closely restricted, to ensure that the font is rendered as quickly as possible. (Or rather, as quickly -as possible with Adobe’s technology at the time the specification was +as possible with Adobe’s technology at the time the specification was written: the structure could well be different if it were specified now.) The format has long been the basis of the digital type-foundry business, though nowadays most new fonts are released in OpenType format. @@ -32,23 +32,23 @@ their use (see below). PostScript operators is permissible, including bitmap specifiers. Type 3 is therefore the natural format to be used for programs such as <i>dvips</i> when they auto-generate something to represent -Metafont-generated fonts in a PostScript file. It’s Adobe Acrobat Viewer’s +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 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>-> +ask Reader for the <code>File</code>-> +<code>Document Properties</code>-> <code>Fonts ...</code>, and it will likely show some font or other as -“Type 3” (usually with encoding “Custom”). The problem has +“Type 3” (usually with encoding “Custom”). The problem has disappeared with version 6 of Acrobat Reader. See <a href="FAQ-dvips-pdf.html">PDF quality</a> for a discussion of the issue, and for ways of addressing it. <p/>Type 3 fonts should not entirely be dismissed, however. Acrobat -Reader’s failure with them is entirely derived from its failure to use +Reader’s failure with them is entirely derived from its failure to use the anti-aliasing techniques common in TeX-ware. Choose a different set of PostScript graphical operators, and you can make pleasing -Type 3 fonts that don’t “annoy” Reader. For example, you may not -change colour within a Type 1 font glyph, but there’s no such +Type 3 fonts that don’t “annoy” Reader. For example, you may not +change colour within a Type 1 font glyph, but there’s no such restriction on a Type 3 font, which opens opportunities for some startling effects. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html index 440c54e28da..d1cac324dd7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-algorithms.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label algorithms</title> </head><body> <h3>Typesetting pseudocode in LaTeX</h3> -<p/>There is no consensus on the ‘right’ way to typeset pseudocode. +<p/>There is no consensus on the ‘right’ way to typeset pseudocode. Consequently, there are a variety of LaTeX packages to choose from -for producing æsthetically pleasing pseudocode listings. +for producing æsthetically pleasing pseudocode listings. <p/>Pseudocode differs from actual program listings in that it lacks strict syntax and semantics. Also, because pseudocode is supposed to be a clear expression of an algorithm it may need to incorporate @@ -15,8 +15,8 @@ that do not appear in conventional programming languages. <p/>You can certainly create your own environment for typesetting pseudocode using, for example, the <code>tabbing</code> or -<code>list</code> environments — it’s not difficult, but it may -prove boring. So it’s worth trying the following packages, all +<code>list</code> environments — it’s not difficult, but it may +prove boring. So it’s worth trying the following packages, all designed specifically for typesetting pseudocode. <p/>The <i>algorithms</i> bundle (which contains packages <i>algorithm</i> and <i>algorithmic</i>, both of which are @@ -29,7 +29,7 @@ for adding new primitives. Typesetting the pseudocode itself is performed in <i>algorithmic</i>; the <i>algorithms</i> package uses the facilities of the <i>float</i> package to number algorithms sequentially, enable algorithms to float like figures or -tables, and support including a List of Algorithms in a document’s +tables, and support including a List of Algorithms in a document’s front matter. <p/>Packages in the <i>algorithmicx</i> bundle are similar both in concept and output form to <i>algorithmic</i> but additionally @@ -48,23 +48,23 @@ floating algorithm environment with all of the ensuing niceties. <i>algorithms</i>, makes it easy to add new constructs. <p/>The <i>newalg</i> package has a somewhat similar interface to <i>algorithms</i>, but its output is designed to mimic the rather -pleasant typesetting used in the book “<em>Introduction to Algorithms</em>” +pleasant typesetting used in the book “<em>Introduction to Algorithms</em>” by Corman, Leiserson, Rivest and Stein. Unfortunately, <i>newalg</i> does not support a floating environment or any customisation of the output. -<p/>“<em>Bona fide</em>” use of the style of “Introduction to -Algorithms” may be achieved with Cormen’s own <i>clrscode</i>: +<p/>“<em>Bona fide</em>” use of the style of “Introduction to +Algorithms” may be achieved with Cormen’s own <i>clrscode</i>: this is the package as used in the second edition of the book. <p/>Similarly, the style of -“<em>Combinatorial Algorithms: Generation, Enumeration and Search</em>” +“<em>Combinatorial Algorithms: Generation, Enumeration and Search</em>” is supported by the <i>pseudocode</i> package, written by the -authors of the book. It has the common ‘Pascal-like’ style, and has +authors of the book. It has the common ‘Pascal-like’ style, and has some interesting constructs for what one thinks of as Pascal blocks. <p/>The <i>algorithm2e</i> is of very long standing, and is widely used and recommended. It loads the <i>float</i> package to provide the option of floating algorithm descriptions, but you can always use the -“<code>H</code>” option of <i>float</i> to have the algorithm appear -“where you write it”. +“<code>H</code>” option of <i>float</i> to have the algorithm appear +“where you write it”. <p/>The usage of the <i>program</i> package is a little different from that of the other packages. It typesets programs in maths mode instead of text mode; and linebreaks are significant. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html index 31442c04f3a..97819cbd730 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label alreadydef</title> </head><body> -<h3>Package reports “command already defined”</h3> +<h3>Package reports “command already defined”</h3> <p/>You load a pair of packages, and the second reports that one of the commands it defines is already present. For example, both the <i>txfonts</i> and <i>amsmath</i> define a command <code>\</code><code>iint</code> @@ -23,21 +23,21 @@ produces a string of error messages of the form: </blockquote><p> As a general rule, things that <i>amsmath</i> defines, it defines well; however, there is a good case for using the <i>txfonts</i> -version of <code>\</code><code>iint</code> — the associated <i>tx</i> fonts have a -double integral symbol that doesn’t need to be “faked” in the way +version of <code>\</code><code>iint</code> — the associated <i>tx</i> fonts have a +double integral symbol that doesn’t need to be “faked” in the way <i>amsmath</i> does. In the case that you are loading several symbol packages, every one of which defines the same symbol, you are likely to experience the problem in a big way (<code>\</code><code>euro</code> is a common victim). -<p/>There are similar cases where one package redefines another’s command, -but no error occurs because the redefining package doesn’t use +<p/>There are similar cases where one package redefines another’s command, +but no error occurs because the redefining package doesn’t use <code>\</code><code>newcommand</code>. Often, in such a case, you only notice the change because you assume the definition given by the first package. The -<i>amsmath</i>–<i>txfonts</i> packages are just such a pair; -<i>txfonts</i> doesn’t provoke errors. +<i>amsmath</i>–<i>txfonts</i> packages are just such a pair; +<i>txfonts</i> doesn’t provoke errors. <p/>You may deal with the problem by saving and restoring the command. Macro programmers may care to do this for themselves; for the rest of -us, there’s the package <i>savesym</i>. The sequence: +us, there’s the package <i>savesym</i>. The sequence: <blockquote> <pre> \usepackage{savesym} @@ -50,7 +50,7 @@ us, there’s the package <i>savesym</i>. The sequence: does the job; restoring the <i>amsmath</i> version of the command, and making the <i>txfonts</i> version of the command available as <code>\</code><code>TXFiint</code>. -<p/>Documentation of <i>savesym</i> doesn’t amount to much: the only +<p/>Documentation of <i>savesym</i> doesn’t amount to much: the only commands are <code>\</code><code>savesymbol</code> and <code>\</code><code>restoresymbol</code>, as noted above. <dl> <dt><tt><i>amsmath.sty</i></tt><dd>Part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html index 7bf9dbcb782..6b018e33a48 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html @@ -3,8 +3,8 @@ </head><body> <h3>Alignment tab changed to <code>\</code><code>cr</code></h3> <p/>This is an error you may encounter in LaTeX when a tabular -environment is being processed. “Alignment tabs” are the -<code>&</code> signs that separate the columns of a tabular; so the error +environment is being processed. “Alignment tabs” are the +<code>&</code> signs that separate the columns of a tabular; so the error message <blockquote> @@ -21,10 +21,10 @@ could arise from a simple typo, such as: \end{tabular} </pre> </blockquote><p> -where the second <code>&</code> in the first line of the table is more than the +where the second <code>&</code> in the first line of the table is more than the two-column <code>ll</code> column specification can cope with. In this -case, an extra “<code>l</code>” in that solves the problem. (If you -continue from the error in this case, “<code>jim</code>” will be moved +case, an extra “<code>l</code>” in that solves the problem. (If you +continue from the error in this case, “<code>jim</code>” will be moved to a row of his own.) Another simple typo that can provoke the error is: <blockquote> @@ -35,7 +35,7 @@ is: \end{tabular} </pre> </blockquote><p> -where the ‘<code>\\</code>’ 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> @@ -48,12 +48,12 @@ LaTeX has made a table equivalent to: </blockquote><p> (with the second line of the table having only one cell). <p/>Rather more difficult to spot is the occurrence of the error when -you’re using alignment instructions in a “<code>p</code>” column: +you’re using alignment instructions in a “<code>p</code>” column: <blockquote> <pre> \usepackage{array} ... -\begin{tabular}{l>{\raggedright}p{2in}} +\begin{tabular}{l>{\raggedright}p{2in}} here & we are again \\ happy & as can be \end{tabular} @@ -62,16 +62,16 @@ happy & as can be the problem here (as explained in <a href="FAQ-tabcellalign.html">tabular cell alignment</a>) is that the <code>\</code><code>raggedright</code> command in the column specification has overwritten -<code>tabular</code>’s definition of <code>\\</code>, so that -“<code>happy</code>” appears in a new line of the second column, and the -following <code>&</code> appears to LaTeX just like the second -<code>&</code> in the first example above. +<code>tabular</code>’s definition of <code>\\</code>, so that +“<code>happy</code>” appears in a new line of the second column, and the +following <code>&</code> appears to LaTeX just like the second +<code>&</code> in the first example above. <p/>Get rid of the error in the way described in -<a href="FAQ-tabcellalign.html">tabular cell alignment</a> — either use +<a href="FAQ-tabcellalign.html">tabular cell alignment</a> — either use <code>\</code><code>tabularnewline</code> explicitly, or use the <code>\</code><code>RBS</code> trick described there. <dl> -<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/array.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html index e4abccf5f8a..9aa1632b47f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html @@ -3,13 +3,13 @@ </head><body> <h3>Where are the <code>am</code> fonts?</h3> <p/>One <em>still</em> occasionally comes across a request for the <i>am</i> -series of fonts. The initials stood for ‘Almost [Computer] Modern’, +series of fonts. The initials stood for ‘Almost [Computer] Modern’, and they were the predecessors of the Computer Modern fonts that we all know and love (or hate) . -There’s not a lot one can do with these +There’s not a lot one can do with these fonts; they are (as their name implies) almost (but not quite) the -same as the <i>cm</i> series; if you’re faced with a document that requests +same as the <i>cm</i> series; if you’re faced with a document that requests them, the only reasonable approach is to edit the document to replace <i>am*</i> font names with <i>cm*</i>. <p/>The appearance of DVI files that request them is sufficiently @@ -18,10 +18,10 @@ translation of them by means of virtual fonts. <p/>You therefore have to fool the system into using <i>cm*</i> fonts where the original author specified <i>am*</i>. <p/>One option is the font substitutions that many -DVI drivers provide via their configuration file — +DVI drivers provide via their configuration file — specify that every <i>am</i> font should be replaced by its corresponding <i>cm</i> font. -<p/>Alternatively, one may try DVI editing — packages +<p/>Alternatively, one may try DVI editing — packages <i>dtl</i> (DVI Text Language) and <i>dviasm</i> (DVI assembler) can both provide round trips from DVI to text and back to DVI. One therefore edits font names @@ -44,7 +44,7 @@ about through the body, so: <code>python dviasm.py -o</code> <<i>edited.dvi</i>> <<i>edited.txt</i>> </blockquote><p> Both routes seem acceptable ways forward; it is a matter of taste -which any particular user may choose (it’s not likely that it will be +which any particular user may choose (it’s not likely that it will be necessary very often...). <dl> <dt><tt><i>dviasm.py</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/dviasm.zip">dviware/dviasm</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/dviasm/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html index e8a9ce4eb1f..8eb489fb375 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label ant</title> </head><body> <h3>The ANT typesetting system</h3> -<p/>Achim Blumensath’s <a href="http://ant.berlios.de">ANT</a> project +<p/>Achim Blumensath’s <a href="http://ant.berlios.de">ANT</a> project aims not to replicate TeX with a different implementation technique, but rather to provide a replacement for TeX which uses TeX-like typesetting algorithms in a very different programming environment. ANT remains under development, but it is now approaching the status of a usable typesetting system. -<p/>ANT’s markup language is immediately recognisable to the +<p/>ANT’s markup language is immediately recognisable to the (La)TeX user, but the scheme of implementing design in -ANT’s own implementation language (presently +ANT’s own implementation language (presently <i>OCaml</i>) comes as a pleasant surprise to the jaded FAQ writer. This architecture holds the promise of a system that avoids a -set of serious problems with TeX’s user interface: those that +set of serious problems with TeX’s user interface: those that derive from the design language being the same as the markup language. <dl> <dt><tt><i>ANT</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/ant.zip">systems/ant</a> (or <a href="http://www.tex.ac.uk/tex-archive/systems/ant/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html index a7f5e70c768..e82a599ea64 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html @@ -24,16 +24,16 @@ to alphabetic. So: would be typeset (in an <i>article</i> document) something like: <blockquote> <b>1 My inspiration</b> -<p/>… +<p/>… <p/><b>2 Developing the inspiration</b> -<p/>… +<p/>… <p/><b>A How I became inspired</b> -<p/>… +<p/>… </blockquote><p> which is quite enough for many ordinary purposes. Note that, once -you’ve switched to typesetting appendixes, LaTeX provides you with -no way back — once you’ve had an appendix, you can no longer have an -“ordinary” <code>\</code><code>section</code> or <code>\</code><code>chapter</code>. +you’ve switched to typesetting appendixes, LaTeX provides you with +no way back — once you’ve had an appendix, you can no longer have an +“ordinary” <code>\</code><code>section</code> or <code>\</code><code>chapter</code>. <p/>The <i>appendix</i> provides several ways of elaborating on this simple setup. Straightforward use of the package allows you to have a separate heading, both in the body of the document and the table of @@ -47,10 +47,10 @@ contents; this would be achieved by \addappheadtotoc </pre> </blockquote><p> -The <code>\</code><code>appendixpage</code> command adds a separate title “Appendices” +The <code>\</code><code>appendixpage</code> command adds a separate title “Appendices” above the first appendix, and <code>\</code><code>addappheadtotoc</code> adds a similar title to the table of contents. These simple modifications cover many -people’s needs about appendixes. +people’s needs about appendixes. <p/>The package also provides an <code>appendices</code> environment, which provides for fancier use. The environment is best controlled by package options; the above example would be achieved by @@ -65,7 +65,7 @@ package options; the above example would be achieved by </blockquote><p> The great thing that the <code>appendices</code> environment gives you, is that once the environment ends, you can carry on with sections -or chapters as before — numbering isn’t affected by the intervening +or chapters as before — numbering isn’t affected by the intervening appendixes. <p/>The package provides another alternative way of setting appendixes, as inferior divisions in the document. The <code>subappendices</code> @@ -90,11 +90,11 @@ as <code>\</code><code>section</code>s. So one might write: Which will produce output something like: <blockquote> <b>1 My inspiration</b> -<p/>… +<p/>… <p/><b>1.A How I became inspired</b> -<p/>… +<p/>… <p/><b>2 Developing the inspiration</b> -<p/>… +<p/>… </blockquote><p> <p/>There are many other merry things one may do with the package; the user is referred to the package documentation for further details. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html index 6769c5d998c..0ee7334befc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html @@ -28,8 +28,8 @@ or mirror closest to you. A complete and current list of CTAN sites and known mirrors is available as file <a href="http://www.tex.ac.uk/tex-archive/CTAN.sites">CTAN.sites</a> on the archives themselves. <p/>Better still, the script behind <a href="http://mirror.ctan.org/">http://mirror.ctan.org/</a> will -cunningly choose a “nearby” mirror for you, using information from -the database ‘behind’ <a href="http://www.tex.ac.uk/tex-archive/CTAN.sites">CTAN.sites</a>; at present it uses +cunningly choose a “nearby” mirror for you, using information from +the database ‘behind’ <a href="http://www.tex.ac.uk/tex-archive/CTAN.sites">CTAN.sites</a>; at present it uses <code>ftp</code> protocol for transfers, but the intention is to convert it to using <code>http</code> (web) protocol in the near future. <p/>To access a particular thing through the <code>mirror.ctan.org</code> @@ -37,10 +37,10 @@ mechanism, simply place the CTAN path after the base URL; so <a href="http://mirror.ctan.org/macros/latex/contrib/footmisc/">http://mirror.ctan.org/macros/latex/contrib/footmisc/</a> will connect you to the <i>footmisc</i> directory at some CTAN -site (or a mirror) — note that the <i>tex-archive</i> part of the -CTAN path isn’t needed. +site (or a mirror) — note that the <i>tex-archive</i> part of the +CTAN path isn’t needed. <p/>For details of how to find files at CTAN sites, see -“<a href="FAQ-findfiles.html">finding (La)TeX files</a>”. +“<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>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html index c6e66a4cc52..83c665a58dc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html @@ -2,51 +2,51 @@ <title>UK TeX FAQ -- question label askquestion</title> </head><body> <h3>How to ask a question</h3> -<p/>You want help from the community at large; you’ve decided where you’re +<p/>You want help from the community at large; you’ve decided where you’re going to <a href="FAQ-gethelp.html">ask your question</a>, but how do you phrase it? -<p/>Excellent “general” advice (how to ask questions of anyone) is +<p/>Excellent “general” advice (how to ask questions of anyone) is contained in -<a href="http://catb.org/~esr/faqs/smart-questions.html">Eric Raymond’s article on the topic</a>. -Eric’s an extremely self-confident person, and this comes through in +<a href="http://catb.org/~esr/faqs/smart-questions.html">Eric Raymond’s article on the topic</a>. +Eric’s an extremely self-confident person, and this comes through in his advice; but his guidelines are very good, even for us in the -un-self-confident majority. It’s important to remember that you don’t +un-self-confident majority. It’s important to remember that you don’t have a right to advice from the world, but that if you express yourself well, you will usually find someone who will be pleased to help. -<p/>So how do you express yourself in the (La)TeX world? There aren’t +<p/>So how do you express yourself in the (La)TeX world? There aren’t any comprehensive rules, but a few guidelines may help in the application of your own common sense. <ul> -<li> Make sure you’re asking the right people. Don’t ask in a TeX +<li> Make sure you’re asking the right people. Don’t ask in a TeX forum about printer device drivers for the <i>Foobar</i> operating system. Yes, TeX users need printers, but no, TeX users will typically <em>not</em> be <i>Foobar</i> systems managers. <p/> Similarly, avoid posing a question in a language that the majority - of the group don’t use: post in Ruritanian to + of the group don’t use: post in Ruritanian to <i>de.comp.text.tex</i> and you may have a long wait before a German- and Ruritanian-speaking TeX expert notices your question. <li> If your question is (or may be) TeX-system-specific, report - what system you’re using, or intend to use: “I can’t install - TeX” is as good as useless, whereas “I’m trying to install the + what system you’re using, or intend to use: “I can’t install + TeX” is as good as useless, whereas “I’m trying to install the <i>mumbleTeX</i> distribution on the <i>Grobble</i> - operating system” gives all the context a potential respondent + operating system” gives all the context a potential respondent might need. Another common situation where this information is - important is when you’re having trouble installing something new in - your system: “I want to add the <i>glugtheory</i> package to my + important is when you’re having trouble installing something new in + your system: “I want to add the <i>glugtheory</i> package to my <i>mumbleTeX v12.0</i> distribution on the <i>Grobble 2024</i> - operating system”. + operating system”. <li> If you need to know how to do something, make clear what your - environment is: “I want to do <em>x</em> in Plain TeX”, or “I + environment is: “I want to do <em>x</em> in Plain TeX”, or “I want to do <em>y</em> in LaTeX running the <i>boggle</i> - class”. If you thought you knew how, but your attempts are - failing, tell us what you’ve tried: “I’ve already tried installing + class”. If you thought you knew how, but your attempts are + failing, tell us what you’ve tried: “I’ve already tried installing the <i>elephant</i> in the <i>minicar</i> directory, and it - didn’t work, even after refreshing the filename database”. -<li> If something’s going wrong within (La)TeX, pretend you’re + didn’t work, even after refreshing the filename database”. +<li> If something’s going wrong within (La)TeX, pretend you’re <a href="FAQ-latexbug.html">submitting a LaTeX bug report</a>, and try to generate a <a href="FAQ-minxampl.html">minimum failing example</a>. If your example @@ -55,12 +55,12 @@ application of your own common sense. resource can be obtained. <li> Figures are special, of course. Sometimes the figure itself is <em>really</em> needed, but most problems may be demonstrated with a - “figure substitute” in the form of a + “figure substitute” in the form of a <code>\</code><code>rule{</code><em>width</em><code>}{</code><em>height</em><code>}</code> command, for some value of <<i>width</i>> and <<i>height</i>>. If the (real) figure is needed, - don’t try posting it: far better to put it on the web somewhere. -<li> Be as succinct as possible. Your helpers don’t usually need to - know <em>why</em> you’re doing something, just <em>what</em> you’re + don’t try posting it: far better to put it on the web somewhere. +<li> Be as succinct as possible. Your helpers don’t usually need to + know <em>why</em> you’re doing something, just <em>what</em> you’re doing and where the problem is. </ul> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html index 7f2c267226b..3b7a442b92a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label atsign</title> </head><body> -<h3>How to type an ‘@’ sign?</h3> -<p/>Long ago, some packages used to use the ‘@’ sign as a command, so that +<h3>How to type an ‘@’ sign?</h3> +<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. <p/>Ordinary people (such as the author of this FAQ) need only type -‘@’. +‘@’. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html index e31404b1b9d..6610dd321d8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html @@ -3,9 +3,9 @@ </head><body> <h3><code>\</code><code>@</code> and <code>@</code> in macro names</h3> <p/>Macro names containing <code>@</code> are <em>internal</em> to LaTeX, and -without special treatment just don’t work in ordinary use. A nice +without special treatment just don’t work in ordinary use. A nice example of the problems caused is discussed in -<a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>”. +<a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>”. <p/>The problems users see are caused by copying bits of a class (<code>.cls</code> file) or package (<code>.sty</code> file) into a document, or by including a class or @@ -16,10 +16,10 @@ avoid clashes between its internal names and names that we would normally use in our documents. In order that these commands may work at all, <code>\</code><code>documentclass</code> and <code>\</code><code>usepackage</code> play around with the meaning of <code>@</code>. -<p/>If you’ve included a file some other way (for example, using +<p/>If you’ve included a file some other way (for example, using <code>\</code><code>input</code>), you can probably solve the problem by using the correct command. -<p/>If you’re using a fragment of a package or class, you may well feel +<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 <a href="FAQ-books.html">The LaTeX Companion</a> are full of fragments of packages as examples for you to employ. @@ -44,7 +44,7 @@ second edition.) <p/>The alternative is to treat all these fragments as a package proper, bundling them up into a <code>.sty</code> file and including them with <code>\</code><code>usepackage</code>; this way you hide your LaTeX internal code somewhere -that LaTeX internal code is expected, which often looks ‘tidier’. +that LaTeX internal code is expected, which often looks ‘tidier’. <dl> <dt><tt><i>Examples from the Companion</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html index f1761290a2d..0d150b9def6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html @@ -5,13 +5,13 @@ <p/>The errors <pre> ! You can't use `\spacefactor' in vertical mode. -\@->\spacefactor +\@->\spacefactor \@m </pre> or <pre> ! You can't use `\spacefactor' in math mode. -\@->\spacefactor +\@->\spacefactor \@m </pre> or simply @@ -20,9 +20,9 @@ or simply ... </pre> bites the LaTeX programmer who uses an internal command without taking -“precautions”. The problem is discussed in detail in +“precautions”. The problem is discussed in detail in -“<a href="FAQ-atsigns.html"><code>@</code> in macro names</a>”, +“<a href="FAQ-atsigns.html"><code>@</code> in macro names</a>”, together with solutions. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html index 8e6e7b78a87..4b61797ecdf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html @@ -10,12 +10,12 @@ citing command, is often useful in large documents. command. <p/><i>Citeref</i> is the older, and seems to rely on rather simpler (and therefore possibly more stable) code; it produces a list of page -references, only. It doesn’t interact well with other citation +references, only. It doesn’t interact well with other citation packages (for example, <i>cite</i>), which probably reflects its -antiquity (it’s derived from a LaTeX 2.09 package). +antiquity (it’s derived from a LaTeX 2.09 package). <p/>Neither collapses -lists of pages (“<code>5, 6, 7</code>” comes out as such, rather than as -“<code>5–7</code>”), but neither package repeats the reference to a page that +lists of pages (“<code>5, 6, 7</code>” comes out as such, rather than as +“<code>5–7</code>”), but neither package repeats the reference to a page that holds multiple citations. (The failure to collapse lists is of course forgiveable in the case of the <i>hyperref</i>-related <i>backref</i>, since the concept of multiple hyperlinks from the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html index 4ca66686b50..50363583052 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html @@ -5,31 +5,31 @@ <p/>For example <pre> ! Improper \hyphenation will be flushed. -\'#1->{ +\'#1->{ \accent 19 #1} -<*> \hyphenation{Ji-m\'e +<*> \hyphenation{Ji-m\'e -nez} </pre> (in Plain TeX) or <pre> ! Improper \hyphenation will be flushed. -\leavevmode ->\unhbox +\leavevmode ->\unhbox \voidb@x -<*> \hyphenation{Ji-m\'e +<*> \hyphenation{Ji-m\'e -nez} </pre> in LaTeX. -<p/>As mentioned in <a href="FAQ-nohyph.html">“hyphenation failures”</a>, +<p/>As mentioned in <a href="FAQ-nohyph.html">“hyphenation failures”</a>, words with accents in them may not be hyphenated. As a result, any such word is deemed improper in a <code>\</code><code>hyphenation</code> command. <p/>The solution is to use a font that contains the character in question, and to express the <code>\</code><code>hyphenation</code> command in terms of that -character; this “hides” the accent from the hyphenation mechanisms. +character; this “hides” the accent from the hyphenation mechanisms. LaTeX users can be achieved this by use of the <i>fontenc</i> package (part of the LaTeX distribution). If you select an 8-bit font with the package, as in <code>\</code><code>usepackage[T1]{fontenc}</code>, -accented-letter commands such as the <code>\’</code><code>e</code> in -<code>\hyphenation{Ji-m\’</code><code>e-nez}</code> automatically become the single accented +accented-letter commands such as the <code>\’</code><code>e</code> in +<code>\hyphenation{Ji-m\’</code><code>e-nez}</code> automatically become the single accented character by the time the hyphenation gets to look at it. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html index 87e8e1a875e..d4662b20dcd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-balance.html @@ -5,8 +5,8 @@ <p/>The <i>twocolumn</i> option of the standard classes causes LaTeX to set the text of a document in two columns. However, the last page of the document typically ends up with columns of different -lengths — such columns are said to be “unbalanced”. Many (most?) -people don’t like unbalanced columns. +lengths — such columns are said to be “unbalanced”. Many (most?) +people don’t like unbalanced columns. <p/>The simplest solution to the problem is to use the <i>multicol</i> package in place of the <i>twocolumn</i> option, as <i>multicol</i> balances the columns on the final page by default. @@ -21,7 +21,7 @@ the last page can often produce the right effect, but this seldom appeals, and if the last page is made up of automatically-generated text (for example, bibliography or index) inserting the command will be difficult. -<p/>The <i>flushend</i> package offers a solution to this problem. It’s a +<p/>The <i>flushend</i> package offers a solution to this problem. It’s a somewhat dangerous piece of macro code, which patches one of the most intricate parts of the LaTeX kernel without deploying any of the safeguards discussed in <a href="FAQ-patch.html">patching commands</a>. @@ -35,13 +35,13 @@ documents. <p/>The user should be aware that any of these packages are liable to become confused in the presence of floats: if problems arise, manual adjustment of the floats in the document is likely to be necessary. -It is this difficulty (what’s required in any instance can’t really be +It is this difficulty (what’s required in any instance can’t really be expressed in current LaTeX) that led the author of <i>multicol</i> to suppress single-column-wide floats. <dl> -<dt><tt><i>balance.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint.zip">macros/latex/contrib/preprint</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint/">browse the directory</a>) -<dt><tt><i>flushend.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>) -<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>balance.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint.zip">macros/latex/contrib/preprint</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/balance.html">catalogue entry</a> +<dt><tt><i>flushend.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/flushend.html">catalogue entry</a> +<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/multicol.html">catalogue entry</a> <p/></dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html index 0d1a560fea1..015e120f550 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html @@ -11,11 +11,11 @@ single character with a larger size, as: {\Huge A} </pre> </blockquote><p> -will be squashed into the paragraph: TeX will make sure it doesn’t -scrape up against the line above, but won’t give it “room to -breathe”, as it does the text at standard size; that is, its size +will be squashed into the paragraph: TeX will make sure it doesn’t +scrape up against the line above, but won’t give it “room to +breathe”, as it does the text at standard size; that is, its size (<code>24.88pt</code>) is taken account of, but its <code>\</code><code>baselineskip</code> -(<code>30pt</code>) isn’t. Similarly +(<code>30pt</code>) isn’t. Similarly <blockquote> <pre> Paragraph text ... @@ -54,8 +54,8 @@ Paragraph text ... </blockquote><p> However, more extended insertions (whether of larger or smaller text) are always going to cause problems; while you can strut larger text, -ensuring that you strut every line will be tiresome, and there’s no -such thing as a “negative strut” that pulls the lines together for +ensuring that you strut every line will be tiresome, and there’s no +such thing as a “negative strut” that pulls the lines together for smaller text. <p/>The only satisfactory way to deal with an extended insertion at a different size is to set it off as a separate paragraph. A diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html index 2e9553e7a6e..8fcc6341230 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibaccent.html +++ b/Master/texmf-dist/doc/generic/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</code><code>\</code><code>~</code><code>nana</code>” comes out as “ma -nana” (!). The solution is similar that of the letter case problem: +“<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. +“<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-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html index 9b102eb264d..35a57f74f3e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibinline.html @@ -26,7 +26,7 @@ the entry appear in a footnote. <li> The package <i>footbib</i>, and <li> Packages <i>jurabib</i> and <i>inlinebib</i>, again. </ul> -Note that <i>jurabib</i> does the job using LaTeX’s standard +Note that <i>jurabib</i> does the job using LaTeX’s standard footnotes, whereas <i>footbib</i> creates its own sequence of footnotes. Therefore, in a document which has other footnotes, it may be advisable to use <i>jurabib</i> (or of course diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html index ef6c25db193..7c5407d7892 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html @@ -1,11 +1,11 @@ <head> <title>UK TeX FAQ -- question label biblatex</title> </head><body> -<h3>Replacing the BibTeX–LaTeX mechanism</h3> +<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 reports of progress (on several projects), over the years, but few that claim to -be ready for “real-world” use. +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 @@ -13,32 +13,32 @@ 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 -few opportunities to write the language, it’s also difficult to become +most current programmers: it’s difficult to learn, but since there are +few opportunities to write the language, it’s also difficult to become fluent (in the way that so many people fluently write the equally arcane TeX macro language). <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. +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 +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 +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 +<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> (at least for now) makes rather limited use of -BibTeX. Both are heavily dependent on LaTeX’s support. +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 @@ -47,7 +47,7 @@ a <code>\</code><code>nocite{*}</code> command enables BibTeX to produce a usabl <p/><i>Amsrefs</i> is maintained by the AMS as part of its author support programme, <p/><i>Biblatex</i> uses BibTeX simply to sort the citations using -<i>biblatex</i>’s own style; the style of citations and of the +<i>biblatex</i>’s own style; the style of citations and of the bibliography itself is determined by the way your <i>biblatex</i> style has been set up. This structure eliminates the collections of BibTeX styles, at a stroke; the package comes with a basic set of @@ -56,21 +56,21 @@ time. The author, Philipp Lehman, evaluated the whole field of bibliography software before starting, and as a result the package comes with answers to many of the questions asked in the bibliography sections of these FAQs. -<p/><i>Biblatex</i> is released as experimental software, but it’s +<p/><i>Biblatex</i> is released as experimental software, but it’s clear that many users are already using it happily; Lehman is responsive to problem reports, at the moment, but a set of expert users is already establishing itself. A set of contributed styles has appeared, which cover some of the trickier bibliography styles. The road map of the project shows one more <em>beta</em> release before the -“stable” <i>biblatex</i> 1.0. +“stable” <i>biblatex</i> 1.0. <p/>A related project is <a href="http://biblatex-biber.sourceforge.net/"><i>biber</a></i> -(it’s called <i>biblatex-biber</i> on SourceForge simply to +(it’s called <i>biblatex-biber</i> on SourceForge simply to distinguish it from an older, defunct, BibTeX replacement project). <i>Biber</i> is a <i>Perl</i>-based system to produce a BibTeX replacement that is specifically tuned to the requirements of <i>biblatex</i>. While it supports the -‘traditional’ BibTeX interface, <i>biber</i> provides an +‘traditional’ BibTeX interface, <i>biber</i> provides an interface language designed for <i>biblatex</i>, including use of Unicode to ease the generation of multilingual citations. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html index 87f40f0844b..46a59be086b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibprefixsort.html @@ -4,17 +4,17 @@ <h3>BibTeX sorting and name prefixes</h3> <p/>BibTeX recognises a bewildering array of name prefixes (mostly those deriving from European language names); it ignores the prefixes -when sorting the bibliography — you want “Ludwig van Beethoven” -sorted under “Beethoven”, not under “van”. (Lamport made a witty -deliberate mistake with Beethoven’s name, in the first edition of his +when sorting the bibliography — you want “Ludwig van Beethoven” +sorted under “Beethoven”, not under “van”. (Lamport made a witty +deliberate mistake with Beethoven’s name, in the first edition of his LaTeX manual.) -<p/>However, a recurring issue is the desire to quote Lord Rayleigh’s -publications (“Lord” isn’t an acceptable prefix), or names from -languages that weren’t considered when BibTeX was designed such as -“al-Wakil” (transcribed from the Arabic). What’s needed is a -separate “sort key”, but BibTeX only allows such a thing in +<p/>However, a recurring issue is the desire to quote Lord Rayleigh’s +publications (“Lord” isn’t an acceptable prefix), or names from +languages that weren’t considered when BibTeX was designed such as +“al-Wakil” (transcribed from the Arabic). What’s needed is a +separate “sort key”, but BibTeX only allows such a thing in citations of items that have no author or editor. -<p/>The solution is to embed the sort key in the author’s name, but to +<p/>The solution is to embed the sort key in the author’s name, but to prevent it from being typeset. Patashnik recommends a command <code>\</code><code>noopsort</code> (no-output-sortkey), which is defined and used as follows: @@ -51,6 +51,6 @@ AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}", 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…). +missing out the accentuation, as above…). <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html index e3a0dfd830e..f9c6f06b308 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html @@ -1,15 +1,15 @@ <head> <title>UK TeX FAQ -- question label bibstrtl</title> </head><body> -<h3>‘String too long’ in BibTeX</h3> -<p/>The BibTeX diagnostic “Warning–you’ve exceeded 1000, the -<code>global-string-size</code>, for entry <code>foo</code>” usually arises +<h3>‘String too long’ in BibTeX</h3> +<p/>The BibTeX diagnostic “Warning–you’ve exceeded 1000, the +<code>global-string-size</code>, for entry <code>foo</code>” usually arises from a very large abstract or annotation included in the database. The diagnostic usually arises because of an infelicity in the coding of -<i>abstract.bst</i>, or styles derived from it. (One doesn’t +<i>abstract.bst</i>, or styles derived from it. (One doesn’t ordinarily output annotations in other styles.) <p/>The solution is to make a copy of the style file (or get a clean copy -from CTAN — <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a +from CTAN — <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a long file-name system, to <i>abstract-long.bst</i>). Now edit it: find function <code>output.nonnull</code> and <ul> @@ -27,16 +27,16 @@ to </pre> </blockquote><p> Finally, -<li> delete the function’s last line, which just says “<code>s</code> +<li> delete the function’s last line, which just says “<code>s</code> (line 84 in the version on CTAN). </ul> Finally, change your <code>\</code><code>bibliographystyle</code> command to refer to the name of the new file. <p/>This technique applies equally to any bibliography style: the same change can be made to any similar <code>output.nonnull</code> function. -<p/>If you’re reluctant to make this sort of change, the only way forward -is to take the entry out of the database, so that you don’t encounter -BibTeX’s limit, but you may need to retain the entry because it +<p/>If you’re reluctant to make this sort of change, the only way forward +is to take the entry out of the database, so that you don’t encounter +BibTeX’s limit, but you may need to retain the entry because it will be included in the typeset document. In such cases, put the body of the entry in a separate file: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html index 3025095cd19..a4a1414fb2a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtocorder.html @@ -1,18 +1,18 @@ <head> <title>UK TeX FAQ -- question label bibtocorder</title> </head><body> -<h3>Table of contents rearranges “<i>unsrt</i>” ordering</h3> -<p/>If you’re using the <i>unsrt</i> bibliography style, you’re +<h3>Table of contents rearranges “<i>unsrt</i>” ordering</h3> +<p/>If you’re using the <i>unsrt</i> bibliography style, you’re expecting that your bibliography will <em>not</em> be sorted, but that the entries will appear in the order that they first appeared in your document. -<p/>However, if you’re unfortunate enough to need a citation in a section +<p/>However, if you’re unfortunate enough to need a citation in a section title, and you also have a table of contents, the citations that now -appear in the table of contents will upset the “natural” ordering +appear in the table of contents will upset the “natural” ordering produced by the <i>unsrt</i> style. Similarly, if you have citations in captions, and have a list of figures (or tables). -<p/>There’s a pretty simple “manual” method for dealing with the -problem — when you have the document stable: +<p/>There’s a pretty simple “manual” method for dealing with the +problem — when you have the document stable: <ol> <li> Delete the <code>.aux</code> file, and any of <code>.toc</code>, <code>.lof</code>, <code>.lot</code> files. @@ -20,8 +20,8 @@ problem — when you have the document stable: <li> Run BibTeX for the last time. <li> Run LaTeX often enough that things are stable again. </ol> -Which is indeed simple, but it’s going to get tedious when you’ve -found errors in your “stable” version, often enough. +Which is indeed simple, but it’s going to get tedious when you’ve +found errors in your “stable” version, often enough. <p/>The package <i>notoccite</i> avoids the kerfuffle, and suppresses citations while in the table of contents, or lists of figures, tables (or other floating things: the code is quite general). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html index fd77e108c02..a845e019735 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibtranscinit.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label bibtranscinit</title> </head><body> -<h3>‘Multi-letter’ 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). @@ -15,11 +15,11 @@ Consider the following example from the real world: } </pre> </blockquote><p> -Note that the “Yu” is the initial, not a complete name. However, -BibTeX’s algorithms will leave you with a citation — -slightly depending on the bibliographic style — that reads: -“S. Y. Epifanov and A. A. Vigasin, …”. instead of the intended -“S. Yu. Epifanov and A. A. Vigasin, …”. +Note that the “Yu” is the initial, not a complete name. However, +BibTeX’s algorithms will leave you with a citation — +slightly depending on the bibliographic style — that reads: +“S. Y. Epifanov and A. A. Vigasin, …”. instead of the intended +“S. Yu. Epifanov and A. A. Vigasin, …”. <p/>One solution is to replace each affected initial by a command that prints the correct combination. To keep your bibliography portable, you need to add that command to your bibliography with the @@ -39,7 +39,7 @@ If you have many such commands, you may want to put them in a separate file and <code>\</code><code>input</code> that LaTeX file in a <code>@preamble</code> directive. <p/>An alternative is to make the transcription look like an accent, from -BibTeX’s point of view. For this we need a control sequence that +BibTeX’s point of view. For this we need a control sequence that does nothing: <blockquote> <pre> @@ -55,8 +55,8 @@ extra typing; which of the two techniques is preferable for a given bibliography will be determined by the names in it. It should be noted that a preamble that introduces lots of odd commands is usually undesirable if the bibliography is a shared one. -<p/>“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 +<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> @@ -66,7 +66,7 @@ complicated name as: </pre> </blockquote><p> -The same trick can be played if you’re entering whole names: +The same trick can be played if you’re entering whole names: <blockquote> <pre> ... @@ -76,7 +76,7 @@ The same trick can be played if you’re entering whole names: </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, +However, if you’re typing the names in the “natural” (Western) way, with given names first, the trick: <blockquote> <pre> @@ -85,7 +85,7 @@ with given names first, the trick: ... </pre> </blockquote><p> -doesn’t work — “de F. Forster” is treated as a compound family +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-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html index 032644c53a1..ecdb5ec7b6c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bold-extras.html @@ -2,35 +2,35 @@ <title>UK TeX FAQ -- question label bold-extras</title> </head><body> <h3>How to do bold-tt or bold-sc</h3> -<p/>LaTeX, as delivered, offers no means of handling bold “teletype” -or small-caps fonts. There’s a practical reason for this (Knuth never +<p/>LaTeX, as delivered, offers no means of handling bold “teletype” +or small-caps fonts. There’s a practical reason for this (Knuth never designed such fonts), but there are typographical considerations too -(the “medium weight” <code>cmtt</code> font is already pretty bold (by +(the “medium weight” <code>cmtt</code> font is already pretty bold (by comparison with other fixed-width fonts), and bold small-caps is not popular with many professional typographers). -<p/>There’s a set of “extra” Metafont files on CTAN that provide bold +<p/>There’s a set of “extra” Metafont files on CTAN that provide bold versions of both <code>cmtt</code> and <code>cmcsc</code> (the small caps font). With modern TeX distributions, one may bring these fonts into use simply by placing them in an <a href="FAQ-install-where.html">appropriate place in the <em>texmf</em> tree</a> -(these are (La)TeX-specific files, so the “<em>public</em>” supplier -would be an appropriate place). Once you’ve +(these are (La)TeX-specific files, so the “<em>public</em>” supplier +would be an appropriate place). Once you’ve <a href="FAQ-inst-wlcf.html">rebuilt the file indexes as necessary</a>, TeX (and friends) will automatically build whatever font files they -need when you first make reference to them. There’s a jiffy package +need when you first make reference to them. There’s a jiffy package <i>bold-extra</i> that builds the necessary font data structures so that you can use the fonts within LaTeX. <p/>Another alternative is to use the <a href="FAQ-ECfonts.html">EC fonts</a>, which come with bold variants of the small-caps fonts. -<p/>If you need to use Type 1 fonts, you can’t proceed with Knuth-style +<p/>If you need to use Type 1 fonts, you can’t proceed with Knuth-style fonts, since there are no Type 1 versions of the <i>mf-extra</i> set. There are, however, Type 1 distributions of the EC fonts, so you can switch to EC and use them; alternatives are discussed in <a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>. <p/>Of course, commercial fixed-width fonts (even the default -<i>Courier</i>) almost always come with a bold variant, so that’s +<i>Courier</i>) almost always come with a bold variant, so that’s not a problem. Furthermore <a href="FAQ-usepsfont.html">PSNFSS</a> -will usually provide “faked” small caps fonts, and has no +will usually provide “faked” small caps fonts, and has no compunctions about providing them in a bold form. <i>Courier</i> is (as we all know, to our cost) freely available; a far more presentable monospace font is <i>LuxiMono</i>, which is also @@ -38,7 +38,7 @@ freely available (monospace text in the typeset version of this FAQ uses <i>LuxiMono</i>, with the metrics and LaTeX support available on the archive. <dl> -<dt><tt><i>bold-extra.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/bold-extra.sty">macros/latex/contrib/misc/bold-extra.sty</a> +<dt><tt><i>bold-extra.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bold-extra.zip">macros/latex/contrib/bold-extra</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bold-extra/">browse the directory</a>) <dt><tt><i>bold tt and small caps fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/cm/mf-extra/bold.zip">fonts/cm/mf-extra/bold</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/mf-extra/bold/">browse the directory</a>) <dt><tt><i>LuxiMono fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/LuxiMono.zip">fonts/LuxiMono</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/LuxiMono/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html index 2824b5d1dc0..5643a3b2b54 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-boldgreek.html @@ -6,8 +6,8 @@ command for setting bold <em>text</em> in TeX maths) affects a select few mathematical symbols (the uppercase Greek letters). However lower-case Greek letters behave differently from upper-case Greek -letters (due to Knuth’s esoteric font encoding decisions). However, -<code>\</code><code>mathbf</code> <em>can’t</em> be used even for upper-case Greek letters in +letters (due to Knuth’s esoteric font encoding decisions). However, +<code>\</code><code>mathbf</code> <em>can’t</em> be used even for upper-case Greek letters in the AMSLaTeX <i>amsmath</i> package, which disables this font-switching and you must use one of the techniques outlined below. @@ -17,7 +17,7 @@ outlined below. {\boldmath$\theta$} </pre> </blockquote><p> -but <code>\</code><code>boldmath</code> may not be used in maths mode, so this ‘solution’ +but <code>\</code><code>boldmath</code> may not be used in maths mode, so this ‘solution’ requires arcana such as: <blockquote> <pre> @@ -37,10 +37,10 @@ which then causes problems in superscripts, etc. <p/>All these solutions cover all mathematical symbols, not merely Greek letters. <dl> -<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) -<dt><tt><i>amsbsy.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) +<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/bm.html">catalogue entry</a> +<dt><tt><i>amsbsy.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsbsy.html">catalogue entry</a> <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsmath.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html index bb60a5da110..7e24e31ab5c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html @@ -2,32 +2,32 @@ <title>UK TeX FAQ -- question label books</title> </head><body> <h3>Books on TeX and its relations</h3> -<p/>While Knuth’s book is the definitive reference for TeX, there are +<p/>While Knuth’s book is the definitive reference for TeX, there are other books covering TeX: <dl> <dt>The TeXbook<dd>by Donald Knuth (Addison-Wesley, 1984, ISBN 0-201-13447-0, paperback ISBN 0-201-13448-9) -<dt>A Beginner’s Book of TeX<dd>by Raymond Seroul and Silvio Levy, +<dt>A Beginner’s Book of TeX<dd>by Raymond Seroul and Silvio Levy, (Springer Verlag, 1992, ISBN 0-387-97562-4) -<dt>TeX by Example: A Beginner’s Guide<dd>by Arvind Borde - (Academic Press, 1992, ISBN 0-12-117650-9 — now out of print) +<dt>TeX by Example: A Beginner’s Guide<dd>by Arvind Borde + (Academic Press, 1992, ISBN 0-12-117650-9 — now out of print) <dt>Introduction to TeX<dd>by Norbert Schwarz (Addison-Wesley, - 1989, ISBN 0-201-51141-X — now out of print) + 1989, ISBN 0-201-51141-X — now out of print) <dt>A Plain TeX Primer<dd>by Malcolm Clark (Oxford University Press, 1993, ISBNs 0-198-53724-7 (hardback) and 0-198-53784-0 (paperback)) <dt>A TeX Primer for Scientists<dd>by Stanley Sawyer and Steven Krantz (CRC Press, 1994, ISBN 0-849-37159-7) <dt>TeX by Topic<dd>by Victor Eijkhout (Addison-Wesley, 1992, - ISBN 0-201-56882-9 — now out of print, but see + ISBN 0-201-56882-9 — now out of print, but see <a href="FAQ-ol-books.html">online books</a>; you can now buy a copy - printed, on demand, by Lulu — see + printed, on demand, by Lulu — see \url{http://www.lulu.com/content/2555607}) <dt>TeX for the Beginner<dd>by Wynter Snow (Addison-Wesley, 1992, ISBN 0-201-54799-6) <dt>TeX for the Impatient<dd>by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves (Addison-Wesley, 1990, - ISBN 0-201-51375-7 — now out of print, but see + ISBN 0-201-51375-7 — now out of print, but see <a href="FAQ-ol-books.html">online books</a>) <dt>TeX in Practice<dd>by Stephan von Bechtolsheim (Springer Verlag, 1993, 4 volumes, ISBN 3-540-97296-X for the set, or @@ -39,23 +39,23 @@ other books covering TeX: <dt>TeX: Starting from Square One<dd> by Michael Doob (Springer - Verlag, 1993, ISBN 3-540-56441-1 — now out of print) + Verlag, 1993, ISBN 3-540-56441-1 — now out of print) <dt>The Joy of TeX<dd>by Michael D. Spivak (second edition, AMS, 1990, ISBN 0-821-82997-1) <dt>The Advanced TeXbook<dd>by David Salomon (Springer Verlag, 1995, ISBN 0-387-94556-3) </dl> -A collection of Knuth’s publications about typography is also available: +A collection of Knuth’s publications about typography is also available: <dl> <dt>Digital Typography<dd>by Donald Knuth (CSLI and Cambridge University Press, 1999, ISBN 1-57586-011-2, paperback ISBN 1-57586-010-4). </dl> -and in late 2000, a “Millennium Boxed Set” of all -5 volumes of Knuth’s “Computers and Typesetting” series (about +and in late 2000, a “Millennium Boxed Set” of all +5 volumes of Knuth’s “Computers and Typesetting” series (about TeX and Metafont) was published by Addison Wesley: <dl> -<dt>Computers & Typesetting, Volumes A–E Boxed Set<dd>by Donald Knuth +<dt>Computers & Typesetting, Volumes A–E Boxed Set<dd>by Donald Knuth (Addison-Wesley, 2001, ISBN 0-201-73416-8). </dl> @@ -81,7 +81,7 @@ For LaTeX, see: by Alan Hoenig (Oxford University Press, 1998, ISBN 0-19-509685-1 hardback, ISBN 0-19-509686-X paperback) <dt>Math into LaTeX:<dd><em>An Introduction to LaTeX and AMSLaTeX</em> - by George Grätzer (third edition Birkhäuser and Springer Verlag, + by George Grätzer (third edition Birkhäuser and Springer Verlag, 2000, ISBN 0-8176-4431-9, ISBN 3-7643-4131-9) @@ -92,40 +92,40 @@ For LaTeX, see: (Springer, 2003, ISBN 0-387-95217-9). <p/> A list of errata for the first printing is available from: <a href="http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html">http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html</a> -<dt>First Steps in LaTeX<dd>by George Grätzer (Birkhäuser, 1999, +<dt>First Steps in LaTeX<dd>by George Grätzer (Birkhäuser, 1999, ISBN 0-8176-4132-7) <dt>LaTeX: Line by Line:<dd> <em>Tips and Techniques for Document Processing</em> - by Antoni Diller (second edition, John Wiley & Sons, + by Antoni Diller (second edition, John Wiley & Sons, 1999, ISBN 0-471-97918-X) <dt>LaTeX for Linux:<dd><em>A Vade Mecum</em> by Bernice Sacks Lipkin (Springer-Verlag, 1999, ISBN 0-387-98708-8, second printing) </dl> -A sample of George Grätzer’s “Math into LaTeX”, in Adobe +A sample of George Grätzer’s “Math into LaTeX”, in Adobe Acrobat format, and example files for the three LaTeX Companions, and for -Grätzer’s “First Steps in LaTeX”, are all available on +Grätzer’s “First Steps in LaTeX”, are all available on CTAN. -<p/>There’s a nicely-presented list of of “recommended books” to be had +<p/>There’s a nicely-presented list of of “recommended books” to be had on the web: <a href="http://www.macrotex.net/texbooks/">http://www.macrotex.net/texbooks/</a> <p/>The list of Metafont books is rather short: <dl> <dt>The Metafontbook<dd>by Donald Knuth (Addison Wesley, 1986, ISBN 0-201-13445-4, ISBN 0-201-52983-1 paperback) </dl> -Alan Hoenig’s ‘<i>TeX Unbound</i>’ includes some discussion and +Alan Hoenig’s ‘<i>TeX Unbound</i>’ includes some discussion and examples of using Metafont. <p/>A book covering a wide range of topics (including installation and maintenance) is: <dl> -<dt>Making TeX Work<dd>by Norman Walsh (O’Reilly and Associates, +<dt>Making TeX Work<dd>by Norman Walsh (O’Reilly and Associates, Inc, 1994, ISBN 1-56592-051-1) </dl> The book is decidedly dated, and is now out of print, but a copy is available via <code>sourceforge</code> and on CTAN, -and we list it under “<a href="FAQ-ol-books.html">online books</a>”. +and we list it under “<a href="FAQ-ol-books.html">online books</a>”. <p/><p/>This list only covers books in English: notices of new books, or warnings that books are now out of print are always welcome. However, this FAQ does <em>not</em> carry reviews of current published material. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html index aa8f446d937..d1e0d425d44 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-braket.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label braket</title> </head><body> <h3>Set specifications and Dirac brackets</h3> -<p/>One of the few glaring omissions from TeX’s mathematical +<p/>One of the few glaring omissions from TeX’s mathematical typesetting capabilities is a means of setting separators in the middle of mathematical expressions. TeX provides primitives called <code>\</code><code>left</code> and <code>\</code><code>right</code>, which can be used to modify brackets (of whatever sort) around a mathematical expression, as in: -<code>\</code><code>left(</code><code> <expression> </code><code>\</code><code>right)</code> — the size of the +<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 @@ -20,13 +20,13 @@ needing a <code>\</code><code>middle</code> command, to be used in expressions l </blockquote><p> to specify the set of even natural numbers. The <a href="FAQ-etex.html">e-TeX system</a> -defines just such a command, but users of Knuth’s original need some -support. Donald Arseneau’s <i>braket</i> package provides commands +defines just such a command, but users of Knuth’s original need some +support. Donald Arseneau’s <i>braket</i> package provides commands for set specifications (as above) and for Dirac brackets (and bras and kets). The package uses the e-TeX built-in command if it finds itself running under e-TeX. <dl> -<dt><tt><i>braket.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/braket.sty">macros/latex/contrib/misc/braket.sty</a> +<dt><tt><i>braket.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/braket.zip">macros/latex/contrib/braket</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/braket/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html index 2da33de2c39..e449f47c780 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breakbox.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label breakbox</title> </head><body> <h3>Breaking boxes of text</h3> -<p/>(La)TeX boxes may not be broken, in ordinary usage: once you’ve +<p/>(La)TeX boxes may not be broken, in ordinary usage: once you’ve typeset something into a box, it will stay there, and the box will jut -out beyond the side or the bottom of the page if it doesn’t fit in the +out beyond the side or the bottom of the page if it doesn’t fit in the typeset area. <p/>If you want a substantial portion of your text to be framed (or coloured), the restriction starts to seem a real imposition. @@ -12,14 +12,14 @@ Fortunately, there are ways around the problem. <p/>The <i>framed</i> package provides <code>framed</code> and <code>shaded</code> environments; both put their content into something which looks like a framed (or coloured) box, but which -breaks as necessary at page end. The environments “lose” footnotes, +breaks as necessary at page end. The environments “lose” footnotes, marginpars and head-line entries, and will not work with <i>multicol</i> or other column-balancing macros. The <i>memoir</i> class includes the functionality of the <i>framed</i> package. <p/>The <i>boites</i> package provides a <code>breakbox</code> environment; examples of its use may be found in the distribution, and -the package’s <i>README</i> file contains terse documentation. The +the package’s <i>README</i> file contains terse documentation. The environments may be nested, and may appear inside <code>multicols</code> environments; however, floats, footnotes and marginpars will be lost. @@ -35,7 +35,7 @@ current LaTeX. <dl> <dt><tt><i>backgrnd.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a> <dt><tt><i>boites.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/boites.zip">macros/latex/contrib/boites</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/boites/">browse the directory</a>) -<dt><tt><i>framed.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a> +<dt><tt><i>framed.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/framed.zip">macros/latex/contrib/framed</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/framed/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>shade.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/generic/shade.zip">macros/generic/shade</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/generic/shade/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html index fd245eb4a86..eae17e33eee 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-breaklinks.html @@ -1,10 +1,10 @@ <head> <title>UK TeX FAQ -- question label breaklinks</title> </head><body> -<h3>Link text doesn’t break at end line</h3> +<h3>Link text doesn’t break at end line</h3> <!-- hyperref overfull link --> <p/>When using the <i>hyperref</i> package, you make a block of text -“active” when you define a hyper-link (when the user clicks on +“active” when you define a hyper-link (when the user clicks on that text, the reader program will divert to the <em>target</em> of the link). <p/>The <i>hyperref</i> package uses a <em>driver</em> (in the same way @@ -14,12 +14,12 @@ all that hyper-stuff. to distill the resulting PostScript), limitations in the way <i>dvips</i> deals with the <code>\</code><code>special</code> commands mean that <i>hyperref</i> must prevent link anchors from breaking at the end of lines. Other -drivers (notably those for PDFTeX and for <i>dvipdfm</i>) don’t +drivers (notably those for PDFTeX and for <i>dvipdfm</i>) don’t suffer from this problem. <p/>The problem may occur in a number of different circumstances. For a couple of them, there are work-arounds: <p/>First, if you have an URL which is active (so that clicking on -it will activate your web browser to “go to” the URL). In +it will activate your web browser to “go to” the URL). In this case <i>hyperref</i> employs the <i>url</i> package to split up the URL (as described in <a href="FAQ-setURL.html">typesetting URLs</a>), but the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html index ab441192f5f..3f800f08352 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-brkinline.html @@ -4,13 +4,13 @@ <h3>Line-breaking in in-line maths</h3> <p/>TeX, by default, allows you to split a mathematical expression at the end of the line; it allows breaks at relational operators (like -“=”, “<”, etc.) and at binary operators (like “+”, -“-”, etc.). In the case of large expressions, this can sometimes be +“=”, “<#60;”, etc.) and at binary operators (like “+”, +“-”, etc.). In the case of large expressions, this can sometimes be a life-saver. <p/>However, in the case of simple expressions like a=b+c, a break can be really disturbing to the reader, and one would like to avoid it. -<p/>Fortunately, these breaks are controllable: there are “penalties” +<p/>Fortunately, these breaks are controllable: there are “penalties” associated with each type of operator: the penalty says how undesirable a break at each point is. Default values are: @@ -48,7 +48,7 @@ to defer a break until after the equality, we could write: ${a+b+c+d} = z+y+x+w$ </pre> </blockquote><p> -The braces say “treat this subformula as one atom” and (in TeX at -least) atoms don’t get split: not a <code>\</code><code>binoppenalty</code> change in sight. +The braces say “treat this subformula as one atom” and (in TeX at +least) atoms don’t get split: not a <code>\</code><code>binoppenalty</code> change in sight. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html index 0ca94465c24..0962e7cf9ee 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html @@ -3,29 +3,29 @@ </head><body> <h3>Unable to read an entire line</h3> <p/>TeX belongs to the generation of applications written for -environments that didn’t offer the sophisticated string and i/o +environments that didn’t offer the sophisticated string and i/o manipulation we nowadays take for granted (TeX was written in Pascal, and the original Pascal standard made no mention of i/o, so that anything but the most trivial operations were likely to be unportable). -<p/>When you overwhelm TeX’s input mechanism, you get told: +<p/>When you overwhelm TeX’s input mechanism, you get told: <pre> ! Unable to read an entire line---bufsize=3000. Please ask a wizard to enlarge me. </pre> -(for some value of ‘3000’ — the quote was from a +(for some value of ‘3000’ — the quote was from a <i>comp.text.tex</i> posting by a someone who was presumably using an old TeX). -<p/>As the message implies, there’s (what TeX thinks of as a) line in -your input that’s “too long” (to TeX’s way of thinking). Since +<p/>As the message implies, there’s (what TeX thinks of as a) line in +your input that’s “too long” (to TeX’s way of thinking). Since modern distributions tend to have tens of thousands of bytes of input -buffer, it’s somewhat rare that these messages occur “for real”. +buffer, it’s somewhat rare that these messages occur “for real”. Probable culprits are: <ul> <li> A file transferred from another system, without translating record endings. With the decline of fixed-format records (on mainframe operating systems) and the increased intelligence of - TeX distributions at recognising other systems’ explicit + TeX distributions at recognising other systems’ explicit record-ending characters, this is nowadays rather a rare cause of the problem. <li> A graphics input file, which a package is examining for its @@ -38,11 +38,11 @@ Probable culprits are: enlarging), and to put the problem right in the source. <p/>If the real problem is over-long text lines, most self-respecting text editors will be pleased to automatically split long lines (while -preserving the “word” structure) so that they are nowhere any longer +preserving the “word” structure) so that they are nowhere any longer than a given length; so the solution is just to edit the file. <p/>If the problem is a ridiculous preview section, try using -<i>ghostscript</i> to reprocess the file, outputting a “plain -<code>.eps</code>” file. (<i>Ghostscript</i> is distributed with a script +<i>ghostscript</i> to reprocess the file, outputting a “plain +<code>.eps</code>” file. (<i>Ghostscript</i> is distributed with a script <i>ps2epsi</i> which will regenerate the preview if necessary.) Users of the shareware program <i>GSview</i> will find buttons to perform the required transformation of the file being displayed. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html index d56fdeeb58e..81b7316c68b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bug.html @@ -7,31 +7,31 @@ <p/>For a start, make entirely sure you <em>have</em> found a bug. -Double-check with books about TeX, LaTeX, or whatever you’re using; -compare what you’re seeing against the other answers above; ask every +Double-check with books about TeX, LaTeX, or whatever you’re using; +compare what you’re seeing against the other answers above; ask every possible person you know who has any TeX-related expertise. The reasons for all this caution are various. -<p/>If you’ve found a bug in TeX itself, you’re a rare animal indeed. +<p/>If you’ve found a bug in TeX itself, you’re a rare animal indeed. Don Knuth is so sure of the quality of his code that he offers real money prizes to finders of bugs; the cheques he writes are such rare items that they are seldom cashed. If <em>you</em> think you have found a genuine fault in TeX itself (or Metafont, or the -CM fonts, or the TeXbook), don’t immediately write to Knuth, +CM fonts, or the TeXbook), don’t immediately write to Knuth, however. He only looks at bugs infrequently, and even then only after they are agreed as bugs by a small vetting team. In the first instance, contact Barbara Beeton at the AMS (<i>bnb@ams.org</i>), or contact <a href="FAQ-TUGstar.html">TUG</a>. -<p/>If you’ve found a bug in LaTeX2e, <a href="FAQ-latexbug.html">report it</a> +<p/>If you’ve found a bug in LaTeX2e, <a href="FAQ-latexbug.html">report it</a> using mechanisms supplied by the LaTeX team. (Please be -careful to ensure you’ve got a LaTeX bug, or a bug in one of the -“required” packages distributed by the LaTeX team.) -<p/>If you’ve found a bug in a contributed LaTeX package, you could try +careful to ensure you’ve got a LaTeX bug, or a bug in one of the +“required” packages distributed by the LaTeX team.) +<p/>If you’ve found a bug in a contributed LaTeX package, you could try contacting the author (if you can find a contact address). However, -it’s generally best to treat any package as unsupported, in the first +it’s generally best to treat any package as unsupported, in the first instance, and only try the author <em>after</em> mailing list/news group support has failed you. -<p/>If you’ve found a bug in LaTeX 2.09, or some other such unsupported +<p/>If you’ve found a bug in LaTeX 2.09, or some other such unsupported software, you may find help or <em>de facto</em> support on a newsgroup such as <i>comp.tex.tex</i> or on a mailing list such as @@ -39,7 +39,7 @@ software, you may find help or <a href="FAQ-minxampl.html">code example</a> of the failure, if relevant. <p/>Failing all else, you may need to pay for -help — TUG maintains a +help — TUG maintains a <a href="http://www.tug.org/consultants.html">register of TeX consultants</a>. <p/><p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html index 0cd0a0b1173..fbc4452a068 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buildbib.html @@ -10,25 +10,25 @@ be called up by citations in a document. specified in a <em>bibliography style</em>. From the style, BibTeX finds what entry types are permissible, what <em>fields</em> each entry type has, and how to format the whole entry. -<p/>The type specifies the type of document you’re making reference to; it -may run all the way from things like “<code>Book</code>” and -“<code>Proceedings</code>” (which may even contain other citations -of type “<code>InBook</code>” or “<code>InProceedings</code>”) -through dissertation styles like “<code>PhdThesis</code>” to -otherwise-uncategorisable things such as “<code>Misc</code>”. The -unique key is something you choose yourself: it’s what you use when +<p/>The type specifies the type of document you’re making reference to; it +may run all the way from things like “<code>Book</code>” and +“<code>Proceedings</code>” (which may even contain other citations +of type “<code>InBook</code>” or “<code>InProceedings</code>”) +through dissertation styles like “<code>PhdThesis</code>” to +otherwise-uncategorisable things such as “<code>Misc</code>”. The +unique key is something you choose yourself: it’s what you use when you want to <a href="FAQ-usebibtex.html">cite an entry in the file</a>. People -commonly create a key that combines the (primary) author’s name and +commonly create a key that combines the (primary) author’s name and the year of publication, possibly with a marker to distinguish publications in the same year. So, for example, the Dyson, Eddington, Davidson paper about deflection of starlight appears in my experimental <code>.bib</code> file as <code>Dyson20.1</code>. -<p/>So, noting the rules of the style, you have ‘simply’ to write a +<p/>So, noting the rules of the style, you have ‘simply’ to write a bibliography database. Fortunately, there are several tools to help in this endeavour: <ul> <li> Most of the better <a href="FAQ-editors.html">(La)TeX-oriented editors</a> - have “BibTeX modes”. + have “BibTeX modes”. <li> If you have an existing <code>thebibliography</code> environment, the <i>Perl</i> script <i>tex2bib</i> will probably help. @@ -37,7 +37,7 @@ in this endeavour: task. Sadly, none seems to be available with the ordinary TeX distributions. <p/> Tools such as <i>Xbibfile</i> (a graphical user interface), - <i>ebib</i> (a database application written to run ‘inside’ + <i>ebib</i> (a database application written to run ‘inside’ <i>emacs</i>) and <i>btOOL</i> (a set of <i>perl</i> tools for building BibTeX database handlers) are available from CTAN. @@ -58,12 +58,12 @@ in this endeavour: <li> Data from on-line citation databases may often be translated to BibTeX format by utilities to be found on CTAN. For example, the <i>Perl</i> script <i>isi2bibtex</i> will - translate citations from ISI “Web of knowledge” (a + translate citations from ISI “Web of knowledge” (a subscription service, available to UK academics via BIDS). UK academics may translate BIDS downloads using <i>bids.to.bibtex</i> <li> <a href="http://scholar.google.com">Google Scholar</a> provides an - “Import into BibTeX” tab for each reference it finds for you: + “Import into BibTeX” tab for each reference it finds for you: that tab gives you a page containing a BibTeX entry for the reference. </ul> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html index 45159083262..8c2e0d48fda 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cancellation.html @@ -5,11 +5,11 @@ <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. +(“<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="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/cancel.sty">macros/latex/contrib/misc/cancel.sty</a> +<dt><tt><i>cancel.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cancel.zip">macros/latex/contrib/cancel</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cancel/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html index e8bb38151f2..c6f4436bf7e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-capbibtex.html @@ -4,7 +4,7 @@ <h3>Capitalisation in BibTeX</h3> <p/>The standard BibTeX bibliography styles impose fixed ideas about the capitalisation of titles of things in the bibliography. While -this is not unreasonable by BibTeX’s lights (the rules come from +this is not unreasonable by BibTeX’s lights (the rules come from the <em>Chicago Manual of Style</em>) it can be troublesome, since BibTeX fails to recognise special uses (such as acronyms, chemical formulae, etc.). @@ -24,8 +24,8 @@ title = {Te{X}niques and tips}, </pre> </blockquote><p> If your document design specification requires a different style of -capitalisation, you should acquire a bibliography style that doesn’t -enforce BibTeX’s default rules. It is definitely <em>not</em> a good +capitalisation, you should acquire a bibliography style that doesn’t +enforce BibTeX’s default rules. It is definitely <em>not</em> a good idea to enclose an entire title in braces, as in <blockquote> <pre> @@ -35,10 +35,10 @@ title = {{TeXniques and tips}}, though that does ensure that the capitalisation is not changed. Your BibTeX database should be a general-purpose thing, not something tuned to the requirements of a particular document or bibliography -style, or to the way you are thinking today — for example, on a +style, or to the way you are thinking today — for example, on a future occasion, you might find yourself using a different BibTeX style with different capitalisation rules. -<p/>There’s more on the subject in the +<p/>There’s more on the subject in the <a href="FAQ-BibTeXing.html">BibTeX documentation</a>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html index 8841c65be33..2f3bef47cad 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-captsty.html @@ -6,7 +6,7 @@ that produce the caption. So, for example, <code>\</code><code>fnum@figure</code> (which produces the float number for figure floats) may be redefined, in a package of your own, or between -<a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code>–<code>\</code><code>makeatother</code></a>: +<a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code>–<code>\</code><code>makeatother</code></a>: <blockquote> <pre> \renewcommand{\fnum@figure}{\textbf{Fig.~\thefigure}} @@ -18,13 +18,13 @@ the original definition used <a href="FAQ-fixnam.html"><code>\</code><code>figurename</code></a>.) More elaborate changes can be made by patching the <code>\</code><code>caption</code> command, but since there are packages to do the job, such changes (which can get rather tricky) -aren’t recommended for ordinary users. +aren’t recommended for ordinary users. <p/>The <i>float</i> package provides some control of the appearance of -captions, though it’s principally designed for the creation of +captions, though it’s principally designed for the creation of non-standard floats. The <i>caption</i> and <i>ccaption</i> -(note the double “<em>c</em>”) packages provide a range of different +(note the double “<em>c</em>”) packages provide a range of different formatting options. -<p/><i>ccaption</i> also provides ‘continuation’ captions and captions +<p/><i>ccaption</i> also provides ‘continuation’ captions and captions that can be placed outside of float environments. The (very simple) <i>capt-of</i> package also allows captions outside a float environment. Note that care is needed when doing things that assume diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html index a2524a0427f..76ebcd82405 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html @@ -3,11 +3,11 @@ </head><body> <h3>Case-changing oddities</h3> <p/>TeX provides two primitive commands <code>\</code><code>uppercase</code> and -<code>\</code><code>lowercase</code> to change the case of text; they’re not much used, but +<code>\</code><code>lowercase</code> to change the case of text; they’re not much used, but are capable creating confusion. -<p/>The two commands do not expand the text that is their parameter — -the result of <code>\</code><code>uppercase{abc}</code> is ‘<code>ABC</code>’, but -<code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always ‘<code>\</code><code>abc</code>’, whatever the +<p/>The two commands do not expand the text that is their parameter — +the result of <code>\</code><code>uppercase{abc}</code> is ‘<code>ABC</code>’, but +<code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always ‘<code>\</code><code>abc</code>’, whatever the meaning of <code>\</code><code>abc</code>. The commands are simply interpreting a table of equivalences between upper- and lowercase characters. They have (for example) no mathematical sense, and @@ -32,7 +32,7 @@ standard classes to produce upper case running heads for chapters and sections. <p/>Unfortunately <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> do not solve the other problems with <code>\</code><code>uppercase</code>, so for example a section -title containing <code>\</code><code>begin{tabular}</code> … +title containing <code>\</code><code>begin{tabular}</code> … <code>\</code><code>end{tabular}</code> will produce a running head containing <code>\</code><code>begin{TABULAR}</code>. The simplest solution to this problem is using a user-defined command, for example: @@ -47,8 +47,8 @@ using a user-defined command, for example: Note that <code>\</code><code>mytable</code> has to be protected, otherwise it will be expanded and made upper case; you can achieve the same result by declaring it with <code>\</code><code>DeclareRobustCommand</code>, in which case the -<code>\</code><code>protect</code> won’t be necessary. -<p/>David Carlisle’s <i>textcase</i> package +<code>\</code><code>protect</code> won’t be necessary. +<p/>David Carlisle’s <i>textcase</i> package addresses many of these problems in a transparent way. It defines commands <code>\</code><code>MakeTextUppercase</code> and <code>\</code><code>MakeTextLowercase</code> which do upper- or lowercase, with the fancier features of the LaTeX @@ -56,7 +56,7 @@ standard <code>\</code><code>Make*</code>-commands but without the problems mentioned above. Load the package with <code>\</code><code>usepackage[overload]{textcase}</code>, and it will redefine the LaTeX commands (<em>not</em> the TeX primitive commands <code>\</code><code>uppercase</code> and -<code>\</code><code>lowercase</code>), so that section headings and the like don’t produce +<code>\</code><code>lowercase</code>), so that section headings and the like don’t produce broken page headings. <dl> <dt><tt><i>textcase.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase.zip">macros/latex/contrib/textcase</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html index aa9a8bba6b9..f9fe7dec104 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html @@ -3,25 +3,25 @@ </head><body> <h3>Marking changed parts of your document</h3> <p/>One often needs clear indications of how a document has changed, but -the commonest technique, “change bars” (also known as “revision -bars”), requires surprisingly much -trickery of the programmer. The problem is that TeX ‘proper’ -doesn’t provide the programmer with any information about the -“current position” from which a putative start- or end-point of a +the commonest technique, “change bars” (also known as “revision +bars”), requires surprisingly much +trickery of the programmer. The problem is that TeX ‘proper’ +doesn’t provide the programmer with any information about the +“current position” from which a putative start- or end-point of a bar might be calculated. PDFTeX <em>does</em> provide that information, but no PDFTeX-based changebar package has been published, that takes advantage of that. -<p/>The simplest package that offers change bars is Peter Schmitt’s +<p/>The simplest package that offers change bars is Peter Schmitt’s <i>backgrnd.tex</i>; this was written as a Plain TeX application that patches the output routine, but it appears to work at least on simple LaTeX documents. Wise LaTeX users will be alerted by the information that <i>backgrnd</i> patches their output routine, and will watch its behaviour very carefully (patching the LaTeX output -routine is not something to undertake lightly…). +routine is not something to undertake lightly…). <p/>The longest-established LaTeX-specific solution is the <i>changebar</i> package, -which uses <code>\</code><code>special</code> commands supplied by the driver you’re using. -You need therefore to tell the package which driver to you’re using +which uses <code>\</code><code>special</code> commands supplied by the driver you’re using. +You need therefore to tell the package which driver to you’re using (in the same way that you need to tell the <i>graphics</i> package); the list of available drivers is pretty wide, but does not include <i>dvipdfm</i>. The package comes with @@ -31,11 +31,11 @@ with <i>changebar</i> macros to highlight changes. <p/>The shareware <i>WinEDT</i> editor has a macro that will generate <i>changebar</i> (or other) macros to show differences from an earlier version of your file, stored in an <i>RCS</i>-controlled -repository — see +repository — see <a href="http://www.winedt.org/Macros/LaTeX/RCSdiff.php">http://www.winedt.org/Macros/LaTeX/RCSdiff.php</a> <p/>The <i>vertbars</i> package uses the techniques of the <i>lineno</i> package (which it loads, so the <i>lineno</i> -itself must be installed); it’s thus the smallest of the packages for +itself must be installed); it’s thus the smallest of the packages for change bar marking, since it leaves all the trickery to another package. <i>Vertbars</i> defines a <code>vertbar</code> environment to create changebars. @@ -48,8 +48,8 @@ convention is to mark a whole changed paragraph. <p/>Finally, the <i>memoir</i> class allows marginal editorial comments, which you can obviously use to delimit areas of changed text. <p/>An even more comprehensive way to keep track of changes is employed by -some word-processors — to produce a document that embodies both -“old” and “new” versions. +some word-processors — to produce a document that embodies both +“old” and “new” versions. <p/>To this end, the package <i>changes</i> allows the user to manually markup changes of text, such as additions, deletions, or replacements. Changed text is shown in a different colour; deleted text is crossed @@ -73,7 +73,7 @@ accept or reject selected changes only. <dt><tt><i>backgrnd.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a> <dt><tt><i>changebar.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changebar.zip">macros/latex/contrib/changebar</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changebar/">browse the directory</a>) <dt><tt><i>changes.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changes.zip">macros/latex/contrib/changes</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changes/">browse the directory</a>) -<dt><tt><i>framed.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a> +<dt><tt><i>framed.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/framed.zip">macros/latex/contrib/framed</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/framed/">browse the directory</a>) <dt><tt><i>latexdiff, latexrevise</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/latexdiff.zip">support/latexdiff</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/">browse the directory</a>) <dt><tt><i>lineno.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lineno.zip">macros/latex/contrib/lineno</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lineno/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html index 0ec0fd07080..871457cde09 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changemargin.html @@ -2,36 +2,36 @@ <title>UK TeX FAQ -- question label changemargin</title> </head><body> <h3>Changing the margins in LaTeX</h3> -<p/>Changing the layout of a document’s text on the page involves several +<p/>Changing the layout of a document’s text on the page involves several subtleties not often realised by the beginner. There are interactions between fundamental TeX constraints, constraints related to the design of LaTeX, and good typesetting and design practice, that mean that any change must be very carefully considered, both to ensure -that it “works” and to ensure that the result is pleasing to the +that it “works” and to ensure that the result is pleasing to the eye. -<p/>LaTeX’s defaults sometimes seem excessively conservative, +<p/>LaTeX’s defaults sometimes seem excessively conservative, but there are sound reasons behind how Lamport designed the layouts themselves, whatever one may feel about his overall design. For -example, the common request for “one-inch margins all round on A4 -paper” is fine for 10- or 12-pitch typewriters, but not for 10pt (or +example, the common request for “one-inch margins all round on A4 +paper” is fine for 10- or 12-pitch typewriters, but not for 10pt (or even 11pt or 12pt) type because readers find such wide, dense, lines difficult to read. There should ideally be no more than 75 characters per line (though the constraints change for two-column text). -<p/>So Lamport’s warning to beginners in his section on ‘Customizing the -Style’ — “don’t do it” — should not lightly be ignored. +<p/>So Lamport’s warning to beginners in his section on ‘Customizing the +Style’ — “don’t do it” — should not lightly be ignored. <p/>This set of FAQs recommends that you use a package to establish consistent settings of the parameters: the interrelationships are taken care of in the established packages, without you <em>needing</em> -to think about them, but remember — the packages only provide -consistent, working, mechanisms: they don’t analyse the quality of +to think about them, but remember — the packages only provide +consistent, working, mechanisms: they don’t analyse the quality of what you propose to do. <p/>The following answers deal with the ways one may choose to proceed: <ul> <li> <a href="FAQ-marginpkgs.html">Choose which package to use</a>. <li> <a href="FAQ-marginmanual.html">Find advice on setting up page layout by hand</a>. </ul> -There is a related question — how to change the layout -temporarily — and there’s an answer that covers that, too: +There is a related question — how to change the layout +temporarily — and there’s an answer that covers that, too: <ul> <li> <a href="FAQ-chngmargonfly.html">Change the margins on the fly</a>. </ul> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html index 89ce98f605f..d09969a6cd2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chapbib.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label chapbib</title> </head><body> <h3>Separate bibliographies per chapter?</h3> -<p/>A separate bibliography for each ‘chapter’ of a document can be provided +<p/>A separate bibliography for each ‘chapter’ of a document can be provided with the package <i>chapterbib</i> (which comes with a bunch of other good bibliographic things). The package allows you a different bibliography for each <code>\</code><code>include</code>d file (i.e., despite the -package’s name, the availability of bibliographies is related to the +package’s name, the availability of bibliographies is related to the component source files of the document rather than to the chapters that logically structure the document). <p/>The package <i>bibunits</i> ties bibliographies to logical units @@ -14,7 +14,7 @@ within the document: the package will deal with chapters and sections (as defined by LaTeX itself) and also defines a <code>bibunit</code> environment so that users can select their own structuring. <dl> -<dt><tt><i>chapterbib.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse the directory</a>) +<dt><tt><i>chapterbib.sty</i></tt><dd>distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/chapterbib.html">catalogue entry</a> <dt><tt><i>bibunits.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bibunits.zip">macros/latex/contrib/bibunits</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bibunits/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html index 46eb2c9bac7..8f5d2f4fcfb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-charshift.html @@ -3,16 +3,16 @@ </head><body> <h3>Weird characters in <i>dvips</i> output</h3> <!-- fi ligature pound pounds sterling elephants --> -<p/>You’ve innocently generated output, using <i>dvips</i>, and there +<p/>You’ve innocently generated output, using <i>dvips</i>, and there are weird transpositions in it: for example, the <code>fi</code> ligature has appeared as a textsterling symbol. This is an unwanted side-effect of the precautions outlined in <a href="FAQ-dvips-pdf.html">generating PostScript for PDF</a>. The <code>-G1</code> switch discussed in that question is appropriate for -Knuth’s text fonts, but doesn’t work with text fonts that don’t follow -Knuth’s patterns (such as fonts supplied by Adobe). +Knuth’s text fonts, but doesn’t work with text fonts that don’t follow +Knuth’s patterns (such as fonts supplied by Adobe). <p/>If the problem arises, suppress the <code>-G1</code> switch: if you were using it -explicitly, <em>don’t</em>; if you were using <code>-Ppdf</code>, add <code>-G0</code> to +explicitly, <em>don’t</em>; if you were using <code>-Ppdf</code>, add <code>-G0</code> to suppress the implicit switch in the pseudo-printer file. <p/>The problem has been corrected in <i>dvips</i> v 5.90 (and later versions), which should be available in any recent TeX distribution. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html index a41bdb014bb..04044cd6efc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-checksum.html @@ -8,18 +8,18 @@ the checksum from the TFM file in the DVI file. <p/>When <i>dvips</i> (or other DVI drivers) process a DVI file, they compare checksums in the DVI file to those in the bitmap fonts being used for character images. If the -checksums don’t match, it means the font metric file used by (La)TeX +checksums don’t match, it means the font metric file used by (La)TeX was not generated from the same Metafont program that generated the font. -<p/>This commonly occurs when you’re processing someone else’s DVI +<p/>This commonly occurs when you’re processing someone else’s DVI file. <p/>The fonts on your system may also be at fault: possibilities are that the new TFM was not installed, or installed in a path after an old TFM file, or that you have a personal cache of bitmaps from an old version of the font. -<p/>In any case, look at the output – the chances are that it’s perfectly +<p/>In any case, look at the output – the chances are that it’s perfectly OK, since metrics tend not to change, even when the bitmaps are -improved. (Indeed, many font designers — Knuth included — +improved. (Indeed, many font designers — Knuth included — maintain the metrics come what may.) <p/>If the output <em>does</em> look bad, your only chance is to regenerate things from scratch. Options include: flushing your bitmap cache, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html index 49928ea5193..6ded5d79316 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-chngmargonfly.html @@ -1,10 +1,10 @@ <head> <title>UK TeX FAQ -- question label chngmargonfly</title> </head><body> -<h3>Changing margins “on the fly”</h3> +<h3>Changing margins “on the fly”</h3> <p/>One of the surprises characteristic of TeX use is that you cannot change the width or height of the text within the document, simply by -modifying the text size parameters; TeX can’t change the text width +modifying the text size parameters; TeX can’t change the text width on the fly, and LaTeX only ever looks at text height when starting a new page. <p/>So the simple rule is that the parameters should only be @@ -27,23 +27,23 @@ happened. </pre> </blockquote><p> The environment takes two arguments, and will indent the left and -right margins, respectively, by the parameters’ values. Negative +right margins, respectively, by the parameters’ values. Negative values will cause the margins to be narrowed, so <code>\</code><code>begin{changemargin}{-1cm}{-1cm}</code> narrows the left and right margins by 1 centimetre. -<p/>Given that TeX can’t do this, how does it work? — well, the +<p/>Given that TeX can’t do this, how does it work? — well, the environment (which is a close relation of the LaTeX -<code>quote</code> environment) <em>doesn’t</em> change the text width +<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>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 (<em>recto</em>) or an +your text according to whether you’re on an odd (<em>recto</em>) or an even (<em>verso</em>) page of a two-sided document. -<i>Changepage</i>’s structure matches that of the <i>memoir</i> +<i>Changepage</i>’s structure matches that of the <i>memoir</i> class. <p/>The (earlier) package <i>chngpage</i> provides the same facilities, -but it uses rather different syntax. <i>Changepage</i>’s structure +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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html index c6bae94fdae..c5247aec0f0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citeURL.html @@ -10,12 +10,12 @@ with the long-awaited BibTeX version 1.0. URL is discussed at some length in the publicly available on-line -<a href="http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm">extracts of ISO 690–2</a>; +<a href="http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm">extracts of ISO 690–2</a>; the techniques below do <em>not</em> satisfy all the requirements of -ISO 690–2, but they offer a solution that is at least -available to users of today’s tools. +ISO 690–2, but they offer a solution that is at least +available to users of today’s tools. <p/>Until the new version of BibTeX arrives, the simplest technique is -to use the <code>howpublished</code> field of the standard styles’ <code>@misc</code> +to use the <code>howpublished</code> field of the standard styles’ <code>@misc</code> function. Of course, the strictures about <a href="FAQ-setURL.html">typesetting URLs</a> still apply, so the entry will look like: @@ -34,21 +34,21 @@ Candidates are: <li> The <i>natbib</i> styles (<i>plainnat</i>, <i>unsrtnat</i> and <i>abbrevnat</i>), which are extensions of the standard styles, principally for use with <i>natbib</i> - itself. However, they’ve acquired URLs and other “modern” - entries along the way. The same author’s <i>custom-bib</i> is + itself. However, they’ve acquired URLs and other “modern” + entries along the way. The same author’s <i>custom-bib</i> is also capable of generating styles that honour URL entries. <li> The <i>babelbib</i> bundle, which offers <a href="FAQ-i18nbib.html">multilingual bibliographies</a>, similarly provides a set of standard-style equivalents that have URL entries. <li> More modern styles such as the <i>harvard</i> package (if the citation styles are otherwise satisfactory for you). - <i>Harvard</i> bibliography styles all include a “<code>url</code>” + <i>Harvard</i> bibliography styles all include a “<code>url</code>” field in their specification; however, the typesetting offered is somewhat feeble (though it does recognise and use <i>LaTeX2HTML</i> macros if they are available, to create hyperlinks). </ul> -You can also acquire new BibTeX styles by use of Norman Gray’s +You can also acquire new BibTeX styles by use of Norman Gray’s <i>urlbst</i> system, which is based on a <i>Perl</i> script that edits an existing BibTeX style file to produce a new style. The new style thus generated has a <code>webpage</code> entry type, and @@ -70,11 +70,11 @@ cases, a useful technique is something like: There is good reason to use the <i>url</i> or <i>hyperref</i> packages in this context: BibTeX has a habit of splitting lines it considers excessively long, and if there are no space -characters for it to use as ‘natural’ breakpoints, BibTeX will -insert a comment (‘<code>%</code>’) character … which +characters for it to use as ‘natural’ breakpoints, BibTeX will +insert a comment (‘<code>%</code>’) character … which is an acceptable character in an URL. Any current version of the <i>url</i> or <i>hyperref</i> package detects this -“<code>%</code>–end-of-line” structure in its argument, and +“<code>%</code>–end-of-line” structure in its argument, and removes it. <dl> <dt><tt><i>babelbib bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (or <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html index e3ad54b7a6e..2dcdbe3e67d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-citesort.html @@ -4,20 +4,20 @@ <h3>Sorting and compressing citations</h3> <p/>If you give LaTeX <code>\</code><code>cite{fred,joe,harry,min}</code>, its default commands could give -something like “[2,6,4,3]”; +something like “[2,6,4,3]”; this looks awful. One can of course get the things in order by rearranging the keys in the <code>\</code><code>cite</code> command, but who wants to do -that sort of thing for no more improvement than “[2,3,4,6]”? +that sort of thing for no more improvement than “[2,3,4,6]”? <p/>The <i>cite</i> package sorts the numbers and detects consecutive -sequences, so creating “[2–4,6]”. The <i>natbib</i> package, -with the <code>numbers</code> and <code>sort&compress</code> options, will +sequences, so creating “[2–4,6]”. The <i>natbib</i> package, +with the <code>numbers</code> and <code>sort&compress</code> options, will do the same when working with its own numeric bibliography styles (<i>plainnat.bst</i> and <i>unsrtnat.bst</i>). <p/>Both <i>cite</i> and <i>natbib</i> will interwork with <i>hyperref</i>, thus making links to the bibliography for <dl> <dt><tt><i>cite.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse the directory</a>) -<dt><tt><i>hypernat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/hypernat.sty">macros/latex/contrib/misc/hypernat.sty</a> +<dt><tt><i>hypernat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hypernat.zip">macros/latex/contrib/hypernat</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hypernat/">browse the directory</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) <dt><tt><i>plainnat.bst</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse the directory</a>) <dt><tt><i>unsrtnat.bst</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html index b5b23e0c7b9..899fa4740a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-clsvpkg.html @@ -8,16 +8,16 @@ overall layout of a document, and the macros that tweak that layout wants. <p/>The distinction was not very clear in LaTeX 2.09, and after some discussion (in the later stages of development of current LaTeX) -the names “class” and “package” were applied to the two concepts. -<p/>The idea is that a document’s <em>class</em> tells LaTeX what sort of -document it’s dealing with, while the <em>packages</em> the document -loads “refine” that overall specification. +the names “class” and “package” were applied to the two concepts. +<p/>The idea is that a document’s <em>class</em> tells LaTeX what sort of +document it’s dealing with, while the <em>packages</em> the document +loads “refine” that overall specification. <p/>On the disc, the files only appear different by virtue of their name -“extension” — class files are called <code>*.cls</code> while package +“extension” — class files are called <code>*.cls</code> while package files are called <code>*.sty</code>. Thus we find that the LaTeX standard <i>article</i> class is represented on disc by a file called <i>article.cls</i>, while the <i>footmisc</i> package (which -refines <i>article</i>’s definition of footnotes) is represented on +refines <i>article</i>’s definition of footnotes) is represented on disc by a file called <i>footmisc.sty</i>. <p/>The user defines the class of his document with the <code>\</code><code>documentclass</code> command (typically the first command in a diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html index 8829ca86091..2023b06627a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cmdstar.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label cmdstar</title> </head><body> <h3>Commands defined with * options</h3> -<p/>LaTeX commands commonly have “versions” defined with an asterisk +<p/>LaTeX commands commonly have “versions” defined with an asterisk tagged onto their name: for example <code>\</code><code>newcommand</code> and <code>\</code><code>newcommand*</code> (the former defines a <code>\</code><code>long</code> version of the command). @@ -35,8 +35,8 @@ to take an argument. </blockquote><p> (Note that arguments to <code>\</code><code>mycommandStar</code> and <code>\</code><code>mycommandNoStar</code> -are independent — either can have their own arguments, unconstrained -by the technique we’re using, unlike the trick described above.) +are independent — either can have their own arguments, unconstrained +by the technique we’re using, unlike the trick described above.) The <code>\</code><code>@ifstar</code> trick is all very well, is fast and efficient, but it requires the definition to be <a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code> protected</a>. @@ -52,7 +52,7 @@ piece of code allows you to define variants of your commands: The package needs <a href="FAQ-etex.html">e-LaTeX</a>, but any new enough distribution defines LaTeX as e-LaTeX by default. Command arguments may be specified in the normal way, in both command -definitions (after the “<code>*</code>” in the <code>\</code><code>WithSuffix</code> +definitions (after the “<code>*</code>” in the <code>\</code><code>WithSuffix</code> version). You can also use the TeX primitive commands, creating a definition like: <blockquote> @@ -62,7 +62,7 @@ definition like: </blockquote><p> <dl> <dt><tt><i>ifthen.sty</i></tt><dd>Part of the LaTeX distribution -<dt><tt><i>suffix.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>) +<dt><tt><i>suffix.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/suffix.html">catalogue entry</a> </dl> <p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html index 35529469e9a..36957973042 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label codelist</title> </head><body> <h3>Code listings in LaTeX</h3> -<p/>‘Pretty’ code listings are sometimes considered worthwhile by the -“ordinary” programmer, but they have a serious place in +<p/>‘Pretty’ code listings are sometimes considered worthwhile by the +“ordinary” programmer, but they have a serious place in the typesetting of dissertations by computer science and other students who are expected to write programs. Simple verbatim listings of programs are commonly useful, as well. @@ -23,7 +23,7 @@ to typeset snippets that you include within your source: ... \begin{document} \begin{lstlisting} -#include <stdio.h> +#include <stdio.h> int main(int argc, char ** argv) { @@ -46,8 +46,8 @@ or you can have it typeset whole files: </pre> </blockquote><p> These very simple examples may be decorated in a huge variety of ways, -and of course there are other languages in the package’s vocabulary -than just <i>C</i>… +and of course there are other languages in the package’s vocabulary +than just <i>C</i>… <p/>Most people, advising others on (La)TeX lists, seem to regard <i>listings</i> as the be-all and end-all on this topic. But there <em>are</em> alternatives, which may be worth considering, in some @@ -58,25 +58,30 @@ format for your program: as well as (La)TeX output, and XSL-FO representations of your program listing. Documentation is available on the <a href="http://www.andre-simon.de/"><i>highlight</a> project site</i>. +<p/>The <i>minted</i> package is a relatively recent addition. It +requires that documents be pre-processed using an external +(<i>python</i>) script, +<a href="http://pygments.org/"><i>Pygments</a></i>. <p/>The <i>lgrind</i> system is another well-established pre-compiler, with all the facilities one might need and a wide repertoire of languages; it is derived from the very long-established <i>tgrind</i>, whose output is based on Plain TeX <p/>The <i>tiny_c2l</i> system is more recent: users are encouraged to -generate their own driver files for languages it doesn’t already deal +generate their own driver files for languages it doesn’t already deal with. <p/>The <i>C++2LaTeX</i> system comes with strong recommendations for use with C and C++. <p/>An extremely simple system is <i>c2latex</i>, for which you write LaTeX source in your C program comments. The program then converts your program into a LaTeX document for processing. The -program (implicitly) claims to be “self-documenting”. +program (implicitly) claims to be “self-documenting”. <dl> <dt><tt><i>c2latex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/c2latex.zip">support/c2latex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/c2latex/">browse the directory</a>) <dt><tt><i>C++2LaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/C++2LaTeX-1_1pl1.zip">support/C++2LaTeX-1_1pl1</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/C++2LaTeX-1_1pl1/">browse the directory</a>) <dt><tt><i>highlight</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/highlight.zip">support/highlight</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/highlight/">browse the directory</a>) <dt><tt><i>lgrind</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/lgrind.zip">support/lgrind</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/lgrind/">browse the directory</a>) <dt><tt><i>listings.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listings.zip">macros/latex/contrib/listings</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listings/">browse the directory</a>) +<dt><tt><i>minted.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listings.zip">macros/latex/contrib/listings</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listings/">browse the directory</a>) <dt><tt><i>tgrind</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/tgrind.zip">support/tgrind</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/tgrind/">browse the directory</a>) <dt><tt><i>tiny_c2l</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/tiny_c2l.zip">support/tiny_c2l</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/tiny_c2l/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html index d4e9b28961a..6744d858eb0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html @@ -9,7 +9,7 @@ appeared not long after TeX itself appeared. fitness for purpose is implied by the inclusion of any vendor in this list. The source of the information is given to provide some clues to its currency. -<p/>In general, a commercial implementation will come ‘complete’, that is, +<p/>In general, a commercial implementation will come ‘complete’, that is, with suitable previewers and printer drivers. They normally also have extensive documentation (<em>i.e</em>., not just the TeXbook!) and some sort of support service. In some cases this is a toll free number @@ -98,9 +98,9 @@ also have email, and normal telephone and fax support. Web: <a href="http://www.mackichan.com">http://www.mackichan.com</a> </blockquote><p> Source: Mail from Christopher Mabb, August 2007 -<dt>Macintosh; Textures<dd> “A TeX system ‘for the rest of - us’ ”. A beta release of Textures for MacOS/X is - available~— see <a href="http://www.bluesky.com/news/news_frames.html">http://www.bluesky.com/news/news_frames.html</a> +<dt>Macintosh; Textures<dd> “A TeX system ‘for the rest of + us’ ”. A beta release of Textures for MacOS/X is + available~— see <a href="http://www.bluesky.com/news/news_frames.html">http://www.bluesky.com/news/news_frames.html</a> <p/> (Blue Sky also gives away a Metafont implementation and some font manipulation tools for Macs.) <blockquote> @@ -129,12 +129,12 @@ also have email, and normal telephone and fax support. </dl> -<p/>Note that the company Y&Y has gone out of business, and Y&Y +<p/>Note that the company Y&Y has gone out of business, and Y&Y TeX (and support for it) is therefore no longer available. Users -of Y&Y systems may care to use the self-help +of Y&Y systems may care to use the self-help <a href="http://tug.org/pipermail/yandytex/">mailing list</a> that was established in 2003; the remaining usable content of -Y&Y’s web site is available at <a href="http://www.tug.org/yandy/">http://www.tug.org/yandy/</a> +Y&Y’s web site is available at <a href="http://www.tug.org/yandy/">http://www.tug.org/yandy/</a> <p/> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html index 9981f266dcc..4eb00fb66a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compactbib.html @@ -5,9 +5,9 @@ <p/>Bibliographies are, in fact, implemented as lists, so all the confusion about <a href="FAQ-complist.html">reducing list item spacing</a> also applies to bibliographies. -<p/>If the <i>natbib</i> package ‘works’ for you (it may not if you are using +<p/>If the <i>natbib</i> package ‘works’ for you (it may not if you are using some special-purpose bibliography style), the solution is relatively -simple — add +simple — add <blockquote> <pre> \usepackage{natbib} @@ -18,11 +18,11 @@ to the preamble of your document. <p/>The <i>compactbib</i> package has a similar effect. Its primary purpose is to produce two bibliographies, and it seems to preclude use of BibTeX (though the package documentation, in the package file -itself, isn’t particularly clear). +itself, isn’t particularly clear). <p/>Otherwise, one is into unseemly hacking of something or other. The -<i>mdwlist</i> package actually does the job, but it doesn’t work +<i>mdwlist</i> package actually does the job, but it doesn’t work here, because it makes a different-named list, while the name -“<code>thebibliography</code>” is built into LaTeX and +“<code>thebibliography</code>” is built into LaTeX and BibTeX. Therefore, we need to <a href="FAQ-patch.html">patch the underlying macro</a>: <blockquote> @@ -40,7 +40,7 @@ its other actions, and have it provide you a compressed bibliography <em>only</em>. <dl> <dt><tt><i>compactbib.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/compactbib/compactbib.sty">macros/latex/contrib/compactbib/compactbib.sty</a> -<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) +<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mdwlist.html">catalogue entry</a> <dt><tt><i>natbib.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse the directory</a>) <dt><tt><i>savetrees.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html index 616e7d9ecc0..11b71fbcbae 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-compjobnam.html @@ -1,18 +1,18 @@ <head> <title>UK TeX FAQ -- question label compjobnam</title> </head><body> -<h3>Comparing the “job name”</h3> +<h3>Comparing the “job name”</h3> <p/>The token <code>\</code><code>jobname</code> amusingly produces a sequence of characters -whose category code is 12 (‘other’), regardless of what the characters +whose category code is 12 (‘other’), regardless of what the characters actually are. Since one inevitably has to compare a macro with the contents of another macro (using <code>\</code><code>ifx</code>, somewhere) one needs to create a macro whose expansion looks the same as the expansion of <code>\</code><code>jobname</code>. We find we can do this with <code>\</code><code>meaning</code>, if we strip -the “<code>\</code><code>show</code> command” prefix. +the “<code>\</code><code>show</code> command” prefix. <p/>The full command looks like: <blockquote> <pre> -\def\StripPrefix#1>{} +\def\StripPrefix#1>{} \def\jobis#1{FF\fi \def\predicate{#1}% \edef\predicate{\expandafter\StripPrefix\meaning\predicate}% @@ -22,7 +22,7 @@ the “<code>\</code><code>show</code> command” prefix. </pre> </blockquote><p> -And it’s used as: +And it’s used as: <blockquote> <pre> \if\jobis{mainfile}% @@ -32,8 +32,8 @@ And it’s used as: \fi </pre> </blockquote><p> -Note that the command <code>\</code><code>StripPrefix</code> need not be defined if you’re -using LaTeX — there’s already an +Note that the command <code>\</code><code>StripPrefix</code> need not be defined if you’re +using LaTeX — there’s already an <a href="FAQ-atsigns.html">internal command</a> <code>\</code><code>strip@prefix</code> that you can use. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html index 6f29d87105a..d904595b54c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-complist.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label complist</title> </head><body> <h3>How to adjust list spacing</h3> -<p/><a href="FAQ-books.html">Lamport’s book</a> lists various +<p/><a href="FAQ-books.html">Lamport’s book</a> lists various parameters for the layout of list (things like <code>\</code><code>topsep</code>, -<code>\</code><code>itemsep</code> and <code>\</code><code>parsep</code>), but fails to mention that they’re set +<code>\</code><code>itemsep</code> and <code>\</code><code>parsep</code>), but fails to mention that they’re set automatically within the list itself. This happens because each list executes a command <code>\</code><code>@list</code><code><<i>depth</i>></code> (the depth -appearing as a lower-case roman numeral); what’s more, the top-level +appearing as a lower-case roman numeral); what’s more, the top-level <code>\</code><code>@listi</code> is usually reset when the font size is changed. As a -result, it’s rather tricky for +result, it’s rather tricky for the user to control list spacing. Of course, the real answer is to use a document class designed with more modest list spacing, but we all -know such things are hard to come by. The <i>memoir</i> class wasn’t +know such things are hard to come by. The <i>memoir</i> class wasn’t designed for more compact lists <em>per se</em>, but offers the user control over the list spacing. <p/>There are packages that provide some control of list spacing, but they @@ -20,11 +20,11 @@ seldom address the separation from surrounding text (defined by <code>\</code><code>topsep</code>). The <i>expdlist</i> package, among its many controls of the appearance of <code>description</code> lists, offers a compaction parameter (see the documentation); the <i>mdwlist</i> -package offers a <code>\</code><code>makecompactlist</code> command for users’ own list +package offers a <code>\</code><code>makecompactlist</code> command for users’ own list definitions, and uses it to define compact lists <code>itemize*</code>, <code>enumerate*</code> and <code>description*</code>. In fact, you can write lists such as -these commands define pretty straightforwardly — for example: +these commands define pretty straightforwardly — for example: <blockquote> <pre> \newenvironment{itemize*}% @@ -43,8 +43,8 @@ compaction: <li> its <code>compactenum</code> environment is the same sort of compact list as is provided in <i>expdlist</i> and <i>mdwlist</i>; and -<li> its <code>inparaenum</code> environment produces a list “in - the paragraph”, i.e., with no line break between items, which is a +<li> its <code>inparaenum</code> environment produces a list “in + the paragraph”, i.e., with no line break between items, which is a great space-saver if the list item texts are short. </ul> The package will manipulate its <code>enumerate</code> environment @@ -54,23 +54,23 @@ does. (<code>asparaitem</code>, etc.), and <code>description</code> equivalents (<code>asparadesc</code>, etc.). <p/>The <i>multenum</i> package offers a more regular form of -<i>paralist</i>’s <code>inparaenum</code>; you define a notional +<i>paralist</i>’s <code>inparaenum</code>; you define a notional grid on which list entries are to appear, and list items will always appear at positions on that grid. The effect is somewhat like that of -the ‘tab’ keys on traditional typewriters; the package was designed +the ‘tab’ keys on traditional typewriters; the package was designed for example sheets, or lists of answers in the appendices of a book. <p/>The ultimate in compaction (of every sort) is offered by the <i>savetrees</i> package; compaction of lists is included. The -package’s prime purpose is to save space at every touch and turn: -don’t use it if you’re under any design constraint whatever! +package’s prime purpose is to save space at every touch and turn: +don’t use it if you’re under any design constraint whatever! <p/>The <i>expdlist</i>, <i>mdwlist</i> and <i>paralist</i> packages all offer other facilities for list configuration: you should -probably not try the “do-it-yourself” approaches outlined below if +probably not try the “do-it-yourself” approaches outlined below if you need one of the packages for some other list configuration purpose. <p/>For ultimate flexibility (including manipulation of <code>\</code><code>topsep</code>), the <i>enumitem</i> package permits adjustment of list parameters using -a “<em>key</em>=<<i>value</i>>” format. +a “<em>key</em>=<<i>value</i>>” format. For example, one might write <blockquote> <pre> @@ -95,14 +95,14 @@ to suppress all spacing above and below your list, or </blockquote><p> to set spacing between items and between paragraphs within items. <i>Enumitem</i> also permits manipulation of the label format in a -more “basic” (and therefore more flexible) manner than the +more “basic” (and therefore more flexible) manner than the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. <dl> -<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/enumitem.html">catalogue entry</a> <dt><tt><i>enumitem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse the directory</a>) <dt><tt><i>expdlist.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) -<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) +<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mdwlist.html">catalogue entry</a> <dt><tt><i>multenum.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multenum.zip">macros/latex/contrib/multenum</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multenum/">browse the directory</a>) <dt><tt><i>paralist.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse the directory</a>) <dt><tt><i>savetrees.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html index 41554d90d28..224047a6d81 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-concrete.html @@ -1,9 +1,9 @@ <head> <title>UK TeX FAQ -- question label concrete</title> </head><body> -<h3>Using the “Concrete” fonts</h3> +<h3>Using the “Concrete” fonts</h3> <p/>The Concrete Roman fonts were designed by Don Knuth for a book called -“Concrete Mathematics”, which he wrote with Graham and Patashnik +“Concrete Mathematics”, which he wrote with Graham and Patashnik (<em>the</em> Patashnik, of BibTeX fame). Knuth only designed text fonts, since the book used the Euler fonts for mathematics. The book was typeset using Plain TeX, of course, with @@ -15,8 +15,8 @@ fonts from Computer Modern to Concrete. Packages <i>beton</i> and <i>ccfonts</i> also slightly increase the default value of <code>\</code><code>baselineskip</code> to account for the rather heavier weight of the Concrete fonts. If you wish to use the <i>Euler</i> fonts for -mathematics, as Knuth did, there’s the <i>euler</i> package which -has been developed from Knuth’s own Plain TeX-based set: these +mathematics, as Knuth did, there’s the <i>euler</i> package which +has been developed from Knuth’s own Plain TeX-based set: these macros are currently deprecated (they clash with many things, including AMSLaTeX). The independently-developed <i>eulervm</i> bundle is therefore preferred to the <i>euler</i> package. (Note @@ -25,7 +25,7 @@ series of virtual fonts. While most modern distributions seem to have the requisite files installed by default, you may find you have to install them. If so, see the file <i>readme</i> in the <i>eulervm</i> distribution.) -<p/>A few years after Knuth’s original design, Ulrik Vieth +<p/>A few years after Knuth’s original design, Ulrik Vieth designed the Concrete Math fonts. Packages <i>concmath</i>, and <i>ccfonts</i> also change the default math fonts from Computer Modern to Concrete and use the Concrete versions diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html index 30103c78d98..cc49be9f75f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-conditional.html @@ -1,17 +1,17 @@ <head> <title>UK TeX FAQ -- question label conditional</title> </head><body> -<h3>Conditional compilation and “comments”</h3> -<p/>While LaTeX (or any other TeX-derived package) isn’t really like a +<h3>Conditional compilation and “comments”</h3> +<p/>While LaTeX (or any other TeX-derived package) isn’t really like a compiler, people regularly want to do compiler-like things using it. -Common requirements are conditional ‘compilation’ and ‘block -comments’, and several LaTeX-specific means to this end are available. +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 +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 +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> @@ -23,19 +23,19 @@ use \verb+\iftrue+ -- a surprise </pre> </blockquote><p> The <code>\</code><code>iftrue</code> is spotted by TeX as it scans, ignoring the -<code>\</code><code>verb</code> command; so the <code>\</code><code>iffalse</code> isn’t terminated by the +<code>\</code><code>verb</code> command; so the <code>\</code><code>iffalse</code> isn’t terminated by the following <code>\</code><code>fi</code>. Also, <code>\</code><code>gobble</code> is pretty inefficient at consuming anything non-trivial, since all the matter to be skipped is copied to the argument stack before being ignored. <p/>If your requirement is for a document from which whole chapters (or the like) are missing, consider the LaTeX -<code>\</code><code>include</code>/<code>\</code><code>includeonly</code> system. If you ‘<code>\</code><code>include</code>’ your -files (rather than <code>\</code><code>input</code> them — see -<a href="FAQ-include.html">What’s going on in my <code>\</code><code>include</code> commands?</a>), -LaTeX writes macro traces of what’s going on at the end of each +<code>\</code><code>include</code>/<code>\</code><code>includeonly</code> system. If you ‘<code>\</code><code>include</code>’ your +files (rather than <code>\</code><code>input</code> them — see +<a href="FAQ-include.html">What’s going on in my <code>\</code><code>include</code> commands?</a>), +LaTeX writes macro traces of what’s going on at the end of each chapter to the <code>.aux</code> file; by using <code>\</code><code>includeonly</code>, you can give LaTeX an exhaustive list of the files that are needed. Files that -don’t get <code>\</code><code>include</code>d are skipped entirely, but the document +don’t get <code>\</code><code>include</code>d are skipped entirely, but the document processing continues as if they <em>were</em> there, and page, footnote, and other numbers are not disturbed. Note that you can choose which sections you want included interactively, using the @@ -44,7 +44,7 @@ sections you want included interactively, using the allows you to exclude a (list of) <code>\</code><code>include</code>d files from your document, by means of an <code>\</code><code>excludeonly</code> command. <p/>If you want to select particular pages of your document, use Heiko -Oberdiek’s <i>pagesel</i> or the <i>selectp</i> packages. You +Oberdiek’s <i>pagesel</i> or the <i>selectp</i> packages. You can do something similar with an existing PDF document (which you may have compiled using <i>pdflatex</i> in the first place), using the <i>pdfpages</i> package. The job is then done with a @@ -83,7 +83,7 @@ for browsing; there are <code>narrowversion</code> and <code>wideversion</code> for the two versions of the file. <p/><i>version</i> offers similar facilities to <i>comment.sty</i> (i.e., <code>\</code><code>includeversion</code> and <code>\</code><code>excludeversion</code> commands); -it’s far “lighter weight”, but is less robust (and in particular, +it’s far “lighter weight”, but is less robust (and in particular, cannot deal with very large areas of text being included/excluded). <p/>A significant development of <i>version</i>, confusingly called <i>versions</i> (i.e., merely a plural of the old package name). @@ -91,9 +91,9 @@ cannot deal with very large areas of text being included/excluded). <code>\</code><code>markversion{</code><em>version-name</em><code>}</code> which defines an environment that prints the included text, with a clear printed mark around it. <p/><i>optional</i> defines a command <code>\</code><code>opt</code>; its first argument is -an ‘inclusion flag’, and its second is text to be included or +an ‘inclusion flag’, and its second is text to be included or excluded. Text to be included or excluded must be well-formed -(nothing mismatched), and should not be too big — if a large body of +(nothing mismatched), and should not be too big — if a large body of text is needed, <code>\</code><code>input</code> should be used in the argument. The documentation (in the package file itself) tells you how to declare which sections are to be included: this can be done in @@ -125,9 +125,9 @@ environments named in its argument. So, for example: </pre> </blockquote><p> <p/>A further valuable twist is offered by the <i>extract</i> package. -This allows you to produce a “partial copy” of an existing document: -the package was developed to permit production of a “book of -examples” from a set of lecture notes. The package documentation +This allows you to produce a “partial copy” of an existing document: +the package was developed to permit production of a “book of +examples” from a set of lecture notes. The package documentation shows the following usage: <blockquote> <pre> @@ -143,27 +143,25 @@ which will cause the package to produce a file <i>foobar.tex</i> containing all the <code>figure</code> and <code>table</code> environments, and the <code>\</code><code>chapter</code> and <code>\</code><code>section</code> commands, from the document being processed. The new file <i>foobar.tex</i> is -generated in the course of an otherwise ordinary run on the ‘master’ +generated in the course of an otherwise ordinary run on the ‘master’ document. The package provides a good number of other facilities, including (numeric or labelled) ranges of environments to extract, and an <code>extract</code> environment which you can use to create complete -ready-to-run LaTeX documents with stuff you’ve extracted. +ready-to-run LaTeX documents with stuff you’ve extracted. <dl> -<dt><tt><i>askinclude.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages — - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>askinclude.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/askinclude.html">catalogue entry</a> <dt><tt><i>comment.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/comment.zip">macros/latex/contrib/comment</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/comment/">browse the directory</a>) -<dt><tt><i>excludeonly.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/excludeonly.sty">macros/latex/contrib/misc/excludeonly.sty</a> +<dt><tt><i>excludeonly.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/excludeonly.zip">macros/latex/contrib/excludeonly</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/excludeonly/">browse the directory</a>) <dt><tt><i>extract.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extract.zip">macros/latex/contrib/extract</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extract/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>optional.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/optional.sty">macros/latex/contrib/misc/optional.sty</a> -<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages — - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>pagesel.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/pagesel.html">catalogue entry</a> <dt><tt><i>pdfpages.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse the directory</a>) <dt><tt><i>selectp.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/selectp.sty">macros/latex/contrib/misc/selectp.sty</a> -<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/verbatim.html">catalogue entry</a> <dt><tt><i>version.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/version.sty">macros/latex/contrib/misc/version.sty</a> <dt><tt><i>versions.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/versions/versions.sty">macros/latex/contrib/versions/versions.sty</a> -<dt><tt><i>xcomment.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse the directory</a>) +<dt><tt><i>xcomment.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/xcomment.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html index e3e293d94c9..acdd24bc76a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html @@ -12,7 +12,7 @@ extensive support for colors, backgrounds, hyperlinks, presentations, figure-text integration, and conditional compilation. It gives the user extensive control over formatting while making it easy to create new layouts and styles without learning the TeX macro -language. ConTeXt’s unified design avoids the package clashes that +language. ConTeXt’s unified design avoids the package clashes that can happen with LaTeX. <p/>ConTeXt also integrates MetaFun, a superset of MetaPost and a powerful system for vector graphics. MetaFun can be used as a stand-alone @@ -37,7 +37,7 @@ response to requests from the user community. -<p/>ConTeXt doesn’t yet have quite such a large developer community as +<p/>ConTeXt doesn’t yet have quite such a large developer community as does LaTeX, but those developers who are active seem to have prodigious energy. Support is available via a <a href="http://contextgarden.net">WIKI site</a> and via the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html index d081b632081..5eacecde85e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-crop.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label crop</title> </head><body> <h3>How to create crop marks</h3> -<p/>If you’re printing something that’s eventually to be reproduced in -significant quantities, and bound, it’s conventional to print on paper -larger than your target product, and to place “crop marks” outside +<p/>If you’re printing something that’s eventually to be reproduced in +significant quantities, and bound, it’s conventional to print on paper +larger than your target product, and to place “crop marks” outside the printed area. These crop marks are available to the production house, for lining up reproduction and trimming machines. <p/>You can save yourself the (considerable) trouble of programming these marks for yourself by using the package <i>crop</i>, which has facilities to satisfy any conceivable production house. Users of the -<i>memoir</i> class don’t need the package, since <i>memoir</i> has +<i>memoir</i> class don’t need the package, since <i>memoir</i> has its own facilities for programming crop marks. <dl> <dt><tt><i>crop.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/crop.zip">macros/latex/contrib/crop</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/crop/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html index d2abced359a..b2872547fbb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-csname.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label csname</title> </head><body> <h3>Defining a macro from an argument</h3> -<p/>It’s common to want a command to create another command: often one -wants the new command’s name to derive from an argument. LaTeX +<p/>It’s common to want a command to create another command: often one +wants the new command’s name to derive from an argument. LaTeX does this all the time: for example, <code>\</code><code>newenvironment</code> creates start- and end-environment commands whose names are derived from the name of the environment command. @@ -13,7 +13,7 @@ name of the environment command. \def\relay#1#2{\def\#1{#2}} </pre> </blockquote><p> -doesn’t work (the TeX engine interprets it +doesn’t work (the TeX engine interprets it as a rather strange redefinition of <code>#</code>). The trick is to use <code>\</code><code>csname</code>, which is a TeX primitive for generating command names from random text, together with <code>\</code><code>expandafter</code>. The definition @@ -28,8 +28,8 @@ above should read: With this definition, <code>\</code><code>relay{blah}{bleah}</code> is equivalent to <code>\</code><code>def</code><code>\</code><code>blah{bleah}</code>. <p/>Note that the definition of <code>\</code><code>relay</code> omits the braces round the -‘command name’ in the <code>\</code><code>newcommand</code> it executes. This is -because they’re not necessary (in fact they seldom are), and in this +‘command name’ in the <code>\</code><code>newcommand</code> it executes. This is +because they’re not necessary (in fact they seldom are), and in this circumstance they make the macro code slightly more tedious. <p/>The name created need not (of course) be <em>just</em> the argument: <blockquote> @@ -52,6 +52,6 @@ With commands \def\finish#1{\csname finish#1\endcsname} </pre> </blockquote><p> -these ‘races’ could behave a bit like LaTeX environments. +these ‘races’ could behave a bit like LaTeX environments. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html index 6ee710d5dac..762419f8393 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html @@ -9,14 +9,14 @@ of the language (see <a href="FAQ-BibTeXing.html">BibTeX documentation</a>). However, it must be admitted that the language in which BibTeX styles are written is pretty obscure, and one would not recommend -anyone who’s not a confident programmer to write their own, though +anyone who’s not a confident programmer to write their own, though minor changes to an existing style may be within the grasp of many. -<p/>If your style isn’t too ‘far out’, you can probably generate it by +<p/>If your style isn’t too ‘far out’, you can probably generate it by using the facilities of the <i>custom-bib</i> bundle. This contains a file <i>makebst.tex</i>, which runs you through a text menu to produce a file of instructions, with which you can generate your -own <code>.bst</code> file. This technique doesn’t offer entirely new styles -of document, but the system’s “master BibTeX styles” already +own <code>.bst</code> file. This technique doesn’t offer entirely new styles +of document, but the system’s “master BibTeX styles” already offer significantly more than the BibTeX standard set. <dl> <dt><tt><i>BibTeX documentation</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (or <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/doc/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html index 294b9a306a4..a7be0a22989 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html @@ -1,18 +1,18 @@ <head> <title>UK TeX FAQ -- question label cv</title> </head><body> -<h3><em>Curriculum Vitae</em> (Résumé)</h3> -<p/>Andrej Brodnik’s class, <i>vita</i>, offers a framework for producing +<h3><em>Curriculum Vitae</em> (Résumé)</h3> +<p/>Andrej Brodnik’s class, <i>vita</i>, offers a framework for producing a <em>curriculum vitae</em>. The class may be customised both for subject (example class option files support both computer scientists and singers), and for language (both the options provided are available for both English and Slovene). Extensions may be written by creating new class option files, or by using macros defined in the class to define new entry types, etc. -<p/>Didier Verna’s class, <i>curve</i>, is based on a model in which +<p/>Didier Verna’s class, <i>curve</i>, is based on a model in which the CV is made of a set of <em>rubrics</em> (each one dealing -with a major item that you want to discuss, such as ‘education’, ‘work -experience’, etc). The class’s documentation is supported by a couple +with a major item that you want to discuss, such as ‘education’, ‘work +experience’, etc). The class’s documentation is supported by a couple of example files, and an emacs mode is provided. <p/>Xavier Danaux offers a class <i>moderncv</i> which supports typesetting modern <em>curricula vitarum</em>, both in a classic and in a @@ -21,12 +21,12 @@ own style by changing the colours, the fonts, etc. <p/>The European Commission has recommended a format for <em>curricula vitarum</em> within Europe, and Nicola Vitacolonna has developed a class <i>europecv</i> to produce it. While (by his own -admission) the class doesn’t solve all problems, it seems well-thought +admission) the class doesn’t solve all problems, it seems well-thought out and supports all current official EU languages (together with a few non-official languages, such as Catalan, Galician and Serbian). <p/>The alternative to using a separate class is to impose a package on one of the standard classes. An example, -Axel Reichert’s <i>currvita</i> package, has been recommended to the +Axel Reichert’s <i>currvita</i> package, has been recommended to the FAQ team. Its output certainly looks good. <p/>There is also a LaTeX 2.09 package <i>resume</i>, which comes with little but advice <em>against</em> trying to use it. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html index cdaf84cfbbf..66c40d9b7ed 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html @@ -8,7 +8,7 @@ also help users of Plain TeX or other packages; this answer attempts to provide a rough-and-ready guide to transcribing such macro definitions for use in other packages. <p/>The reason LaTeX has commands that replace <code>\</code><code>def</code>, is that -there’s a general philosophy within LaTeX that the user should be +there’s a general philosophy within LaTeX that the user should be protected from himself: the user has different commands according to whether the command to be defined exists (<code>\</code><code>renewcommand</code>) or not (<code>\</code><code>newcommand</code>), and if its status proves not as the user expected, @@ -16,9 +16,9 @@ an error is reported. A third definition command, <code>\</code><code>providecommand</code>, only defines if the target is not already defined; LaTeX has no direct equivalent of <code>\</code><code>def</code>, which ignores the present state of the command. The final command of this sort is -<code>\</code><code>DeclareRobustCommand</code>, which creates a command which is “robust” -(i.e., will not expand if subjected to LaTeX “protected -expansion”); from the Plain TeX user’s point of view, +<code>\</code><code>DeclareRobustCommand</code>, 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, <code>\</code><code>DeclareRobustCommand</code> should be treated as a non-checking version of <code>\</code><code>newcommand</code>. <p/>LaTeX commands are, by default, defined <code>\</code><code>long</code>; an optional <code>*</code> @@ -27,7 +27,7 @@ the command is <em>not</em> to be defined <code>\</code><code>long</code>. The detected by a command <code>\</code><code>@ifstar</code> which uses <code>\</code><code>futurelet</code> to switch between two branches, and gobbles the <code>*</code>: LaTeX users are encouraged to think of the <code>*</code> as part of the command name. -<p/>LaTeX’s checks for unknown command are done by <code>\</code><code>ifx</code> comparison +<p/>LaTeX’s checks for unknown command are done by <code>\</code><code>ifx</code> comparison of a <code>\</code><code>csname</code> construction with <code>\</code><code>relax</code>; since the command name argument is the desired control sequence name, this proves a little long-winded. Since <code>#1</code> is the requisite argument, we have: @@ -42,9 +42,9 @@ long-winded. Since <code>#1</code> is the requisite argument, we have: </blockquote><p> (<code>\</code><code>@gobble</code> simply throws away its argument). <p/>The arguments of a LaTeX command are specified by two optional -arguments to the defining command: a count of arguments (0–9: if the +arguments to the defining command: a count of arguments (0–9: if the count is 0, the optional count argument may be omitted), and a default -value for the first argument, if the defined command’s first argument +value for the first argument, if the defined command’s first argument is to be optional. So: <blockquote> <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html index 07856bead65..57a5ab3dd4b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dec_comma.html @@ -17,23 +17,23 @@ typing numbers. probably welcome macro support. There are two packages that can help relieve the tedium: <i>icomma</i> and <i>ziffer</i>. <p/><i>Icomma</i> ensures that there will be no extra space after a -comma, unless you type a space after it (as in <code>f(x, y)</code> — in -the absence of the package, you don’t need that space), in which case +comma, unless you type a space after it (as in <code>f(x, y)</code> — in +the absence of the package, you don’t need that space), in which case the usual small space after the comma appears. <i>Ziffer</i> is specifically targeted at the needs of those typesetting German, but covers the present need, as well as providing the double-minus sign -used in German (and other languages) for the empty ‘cents’ part of an +used in German (and other languages) for the empty ‘cents’ part of an amount of currency. <p/>The <i>numprint</i> package provides a command <code>\</code><code>numprint{</code><em>number</em><code>}</code> that prints its argument according to settings you give it, or according to settings chosen to match the language you have selected in <i>babel</i>. The formatting works equally well in text or maths. The command is very flexible (it can also -group the digits of very ‘long’ numbers), but is inevitably less +group the digits of very ‘long’ numbers), but is inevitably less convenient than <i>icomma</i> or <i>ziffer</i> if you are typing a lot of numbers. <dl> -<dt><tt><i>icomma.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was.zip">macros/latex/contrib/was</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was/">browse the directory</a>) +<dt><tt><i>icomma.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was.zip">macros/latex/contrib/was</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/icomma.html">catalogue entry</a> <dt><tt><i>numprint.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/numprint.zip">macros/latex/contrib/numprint</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/numprint/">browse the directory</a>) <dt><tt><i>ziffer.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ziffer.zip">macros/latex/contrib/ziffer</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ziffer/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html index 7ab757c942d..cd8564e28a7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-destable.html @@ -4,20 +4,20 @@ <h3>The design of tables</h3> <p/>In recent years, several authors have argued that the examples, set out by Lamport in his <a href="FAQ-books.html">LaTeX manual</a>, have cramped -authors’ style and have led to extremely poor table design. It is in -fact difficult even to work out what many of the examples in Lamport’s -book “mean”. +authors’ style and have led to extremely poor table design. It is in +fact difficult even to work out what many of the examples in Lamport’s +book “mean”. <p/>The criticism focuses on the excessive use of rules (both horizontal -and vertical) and on the poor vertical spacing that Lamport’s macros +and vertical) and on the poor vertical spacing that Lamport’s macros offer. <p/>The problem of vertical spacing is plain for all to see, and is -addressed in several packages — see -“<a href="FAQ-struttab.html">spacing of lines in tables</a>”. +addressed in several packages — see +“<a href="FAQ-struttab.html">spacing of lines in tables</a>”. <p/>The argument about rules is presented in the excellent essay that -prefaces the documentation of Simon Fear’s <i>booktabs</i> package, -which (of course) implements Fear’s scheme for ‘comfortable’ rules. +prefaces the documentation of Simon Fear’s <i>booktabs</i> package, +which (of course) implements Fear’s scheme for ‘comfortable’ rules. (The same rule commands are implemented in the <i>memoir</i> class.) -<p/>Lamport’s LaTeX was also inflexibly wrong in “insisting” that +<p/>Lamport’s LaTeX was also inflexibly wrong in “insisting” that captions should come at the bottom of a table. Since a table may extend over several pages, traditional typography places the caption at the top of a table float. The <code>\</code><code>caption</code> command will get its @@ -72,7 +72,7 @@ value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (defaul \end{table} </pre> </blockquote><p> -does the job. (The package itself is very slightly more elaborate…) +does the job. (The package itself is very slightly more elaborate…) <dl> <dt><tt><i>booktabs.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse the directory</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html index c5f3d90571e..00b727d0c05 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-distill-prob.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label distill-prob</title> </head><body> <h3>Characters missing from PDF output</h3> -<p/>If you’re using <i>Acrobat</i> <i>Distiller</i> to create your +<p/>If you’re using <i>Acrobat</i> <i>Distiller</i> to create your PDF output, you may find characters missing. This may manifest itself as messed-up maths equations (missing -“-” signs, for example), or bits missing +“-” signs, for example), or bits missing from large symbols. Early versions of <i>Distiller</i> used to -ignore character positions 0–31 and 128–159 of every font: Adobe’s +ignore character positions 0–31 and 128–159 of every font: Adobe’s fonts never use such positions, so why should <i>Distiller</i>? -<p/>Well, the answer to this question is “because Adobe don’t produce all -the world’s fonts” — fonts like <i>Computer</i> +<p/>Well, the answer to this question is “because Adobe don’t produce all +the world’s fonts” — fonts like <i>Computer</i> <i>Modern</i> were around before Adobe came on the scene, and -<em>they</em> use positions 0–31. Adobe don’t react to complaints like +<em>they</em> use positions 0–31. Adobe don’t react to complaints like that in the previous sentence, but they do release new versions of their programs; and <i>Distiller</i>, since at least version 4.0, <em>has</em> recognised the font positions it used to shun. <p/>Meanwhile, TeX users with old versions of <i>Distiller</i> need to deal with their fonts. <i>Dvips</i> comes to our aid: the -switch <code>-G1</code> (“remap characters”), which moves the offending +switch <code>-G1</code> (“remap characters”), which moves the offending characters out of the way. The PDF configuration file (<code>-Ppdf</code>), recommended -in “<a href="FAQ-fuzzy-type3.html">the wrong type of fonts</a>”, +in “<a href="FAQ-fuzzy-type3.html">the wrong type of fonts</a>”, includes the switch. <p/>The switch is not without its problems; pre-2003 versions of <i>dvips</i> will apply it to Adobe fonts as well, causing diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html index 81e90ce4d86..7565a3f2f55 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-divzero.html @@ -9,13 +9,13 @@ </pre> </blockquote><p> can actually be caused by offering the package a figure which claims -to have a zero dimension, it’s more commonly caused by rotation. +to have a zero dimension, it’s more commonly caused by rotation. <p/>Objects in TeX may have both height (the height above the baseline) and depth (the distance the object goes below the baseline). If you rotate an object by 180 degrees, you convert its height into depth, -and vice versa; if the object started with zero depth, you’ve +and vice versa; if the object started with zero depth, you’ve converted it to a zero-height object. -<p/>Suppose you’re including your graphic with a command like: +<p/>Suppose you’re including your graphic with a command like: <blockquote> <pre> \includegraphics[angle=180,height=5cm]{myfig.eps} @@ -26,7 +26,7 @@ In the case that <i>myfig.eps</i> has no depth to start with, the scaling calculations will produce the division-by-zero error. <p/>Fortunately, the <i>graphicx</i> package has a keyword <code>totalheight</code>, which allows you to specify the size of the -image relative to the sum of the object’s <code>height</code> and +image relative to the sum of the object’s <code>height</code> and <code>depth</code>, so <blockquote> <pre> @@ -35,7 +35,7 @@ image relative to the sum of the object’s <code>height</code> and </blockquote><p> will resolve the error, and will behave as you might hope. -<p/>If you’re using the simpler <i>graphics</i> package, use the +<p/>If you’re using the simpler <i>graphics</i> package, use the <code>*</code> form of the <code>\</code><code>resizebox</code> command to specify the use of <code>totalheight</code>: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html index 38a0d7f4783..aabfa0a34e7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html @@ -4,8 +4,8 @@ <h3>Directories of (La)TeX information</h3> <p/>TUG India is developing a series of online LaTeX tutorials which can be strongly recommended: select single chapters at a time -from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutorials.html</a> — the -set comprises two parts, “Text” and “Graphics”, so far. +from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutorials.html</a> — the +set comprises two parts, “Text” and “Graphics”, so far. <p/>Once, there were other links like that, but all the others have faded away, leaving the TUG India set in splendid isolation. <p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html index 9d5d4cf3dba..438f17918ca 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-wiki.html @@ -3,13 +3,13 @@ </head><body> <h3>WIKI pages for TeX and friends</h3> <p/>The <em>WIKI</em> concept can be a boon to everyone, if used sensibly. -The “general” WIKI allows <em>anyone</em> to add stuff, or to edit +The “general” WIKI allows <em>anyone</em> to add stuff, or to edit stuff that someone else has added: while there is obvious potential for chaos, there is evidence that a strong user community can keep a WIKI under control. <p/>Following the encouraging performance of the <a href="http://contextgarden.net/">ConTeXt WIKI</a>, valiant efforts -have been made generating “WIKI books” for (La)TeX users. Thus we +have been made generating “WIKI books” for (La)TeX users. Thus we have <a href="http://en.wikibooks.org/wiki/TeX">(Plain) TeX WIKI</a> and <a href="http://en.wikibooks.org/wiki/LaTeX">LaTeX WIKI</a> are well established. Neither would seem yet to be of publication quality, but diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html index f8849de0a66..3f093955382 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-docotherdir.html @@ -5,24 +5,24 @@ <p/>A common way of constructing a large document is to break it into a set of files (for example, one per chapter) and to keep everything related to each of these subsidiary files in a subdirectory. -<p/>Unfortunately, TeX doesn’t have a changeable “current directory”, +<p/>Unfortunately, TeX doesn’t have a changeable “current directory”, so that all files you refer to have to be specified relative to the same directory as the main file. Most people find this counter-intuitive. -<p/>It may be appropriate to use the “path extension” technique +<p/>It may be appropriate to use the “path extension” technique <a href="FAQ-tempinst.html">used in temporary installations</a> to deal with this problem. However, if there several files with the same name in your document, such as <i>chapter1/fig1.eps</i> and -<i>chapter2/fig1.eps</i>, you’re not giving TeX any hint as to -which you’re referring to when in the main chapter file you say +<i>chapter2/fig1.eps</i>, you’re not giving TeX any hint as to +which you’re referring to when in the main chapter file you say <code>\</code><code>input{sect1}</code>; while this is readily soluble in the case of -human-prepared files (just don’t name them all the same), +human-prepared files (just don’t name them all the same), automatically produced files have a way of having repetitious names, and changing <em>them</em> is a procedure prone to error. <p/>The <i>import</i> package comes to your help here: it defines an <code>\</code><code>import</code> command that accepts a full path name and the name of a -file in that directory, and arranges things to “work properly”. +file in that directory, and arranges things to “work properly”. So, for example, if <i>/home/friend/results.tex</i> contains <blockquote> <pre> @@ -44,14 +44,14 @@ each of which takes directory and file arguments, e.g.: \cfpart[pt 1]{Part One}{part1}{part} </pre> </blockquote><p> -which command will issue a ‘normal’ command +which command will issue a ‘normal’ command <code>\</code><code>part[pt 1]{Part One}</code> and then input the file <i>part1/part.tex</i>, remembering that <i>part1/</i> is now the -“current folder”. There are also commands of the form +“current folder”. There are also commands of the form <code>\</code><code>cfpartstar</code> (which corresponds to a <code>\</code><code>part*</code> command). -<p/>Once you’re “in” a <i>chapterfolder</i>-included document, you -may use <code>\</code><code>cfinput</code> to input something relative to the “current -folder”, or you may use <code>\</code><code>input</code>, using <code>\</code><code>cfcurrentfolder</code> to +<p/>Once you’re “in” a <i>chapterfolder</i>-included document, you +may use <code>\</code><code>cfinput</code> to input something relative to the “current +folder”, or you may use <code>\</code><code>input</code>, using <code>\</code><code>cfcurrentfolder</code> to provide a path to the file. (There are also <code>\</code><code>cfcurrentfolderfigure</code> for a <i>figure/</i> subdirectory and <code>\</code><code>cfcurrentfolderlistings</code> for a <i>listings/</i> subdirectory.) @@ -59,7 +59,7 @@ provide a path to the file. (There are also <i>README</i> in the directory is in English. <dl> <dt><tt><i>chapterfolder.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chapterfolder.zip">macros/latex/contrib/chapterfolder</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chapterfolder/">browse the directory</a>) -<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> +<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import.zip">macros/latex/contrib/import</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html index f3a5438fc1a..492e01c31cd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dolldoll.html @@ -1,32 +1,32 @@ <head> <title>UK TeX FAQ -- question label dolldoll</title> </head><body> -<h3>Why use <code>\</code><code>[</code> …<code>\</code><code>]</code> in place of <code>$$</code> …<code>$$</code>?</h3> +<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 s those that derive from the TeX primitive maths sequences bracketing maths commands with single (or pairs of) dollar signs. -<p/>As it turns out, LaTeX’s inline maths grouping, +<p/>As it turns out, LaTeX’s inline maths grouping, <code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code>, has precisely the same effect as the TeX primitive version <code>$ ... $</code>. (Except that -the LaTeX version checks to ensure you don’t put <code>\</code><code>(</code> and +the LaTeX version checks to ensure you don’t put <code>\</code><code>(</code> and <code>\</code><code>)</code> the wrong way round.) <p/>In this circumstance, one often finds LaTeX users, who have some -experience of using Plain TeX, merely assuming that LaTeX’s +experience of using Plain TeX, merely assuming that LaTeX’s display maths grouping <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> may be replaced by the TeX primitive display maths <code>$$ ... $$</code>. <p/>Unfortunately, they are wrong: if LaTeX code is going to patch display maths, it can only do so by patching <code>\</code><code>[</code> and <code>\</code><code>]</code>. The most obvious way this turns up, is that the class option <code>fleqn</code> simply does not work for equations coded using -<code>$$ ... $$</code>, whether you’re using the standard classes +<code>$$ ... $$</code>, whether you’re using the standard classes alone, or using package <i>amsmath</i>. Also, the <code>\</code><code>[</code> and <code>\</code><code>]</code> construct has code for rationalising vertical spacing in some extreme cases; that code is not available in <code>$$ ... $$</code>, so if you use the non-standard version, you may occasionally observe inconsistent vertical spacing . <p/>There are more subtle effects (especially with package -<i>amsmath</i>), and the simple rule is “use +<i>amsmath</i>), and the simple rule is “use <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> whenever displayed maths is needed in -LaTeX”. +LaTeX”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html index 756bea55c1c..c9e87e3a977 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html @@ -10,20 +10,18 @@ this: the construction to use is: <pre> \begin{figure}[p] \begin{leftfullpage} - <left side figure> + <left side figure> \end{leftfullpage} \end{figure} \begin{figure}[p] \begin{fullpage} - <right side figure> + <right side figure> \end{fullpage} \end{figure} </pre> </blockquote><p> The construction has no effect unless the standard class option <code>twoside</code> is in effect. -<p/>Full documentation of the package (such as it is) is to be found in -<i>README.dpfloat</i> <dl> <dt><tt><i>dpfloat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dpfloat.zip">macros/latex/contrib/dpfloat</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dpfloat/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html index e51e84cde3a..e82c1e421a5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawFeyn.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label drawFeyn</title> </head><body> <h3>Drawing Feynman diagrams in LaTeX</h3> -<p/>Michael Levine’s <i>feynman</i> bundle for drawing the diagrams in +<p/>Michael Levine’s <i>feynman</i> bundle for drawing the diagrams in LaTeX 2.09 is still available. -<p/>Thorsten Ohl’s <i>feynmf</i> is designed for use with current +<p/>Thorsten Ohl’s <i>feynmf</i> is designed for use with current LaTeX, and works in combination with Metafont (or, in its <i>feynmp</i> incarnation, with MetaPost). The <i>feynmf</i> or @@ -14,11 +14,11 @@ font (or PostScript file) for use in a subsequent LaTeX run. For new users, who have access to MetaPost, the PostScript version is probably the better route, for document portability and other reasons. -<p/>Jos Vermaseren’s <i>axodraw</i> is mentioned as an alternative in +<p/>Jos Vermaseren’s <i>axodraw</i> is mentioned as an alternative in the documentation of <i>feynmf</i>, but it is written entirely in terms of <i>dvips</i> <code>\</code><code>special</code> commands, and is thus rather imperfectly portable. -<p/>An alternative approach is implemented by Norman Gray’s <i>feyn</i> +<p/>An alternative approach is implemented by Norman Gray’s <i>feyn</i> package. Rather than creating complete diagrams as postscript images, <i>feyn</i> provides a font (in a variety of sizes) containing fragments, which you can compose to produce complete diagrams. It diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html index 422c1df4074..76c499a2fa0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html @@ -12,22 +12,22 @@ of drawing, and setup, here are a few systems you may consider: <li> PicTeX is a venerable, and very powerful, system, that draws by placing dots on the page to give the effect of a line or curve. While this has the potential of great power, it is (of course) much slower - than any of the other established packages. What’s more, there + than any of the other established packages. What’s more, there are problems with its <a href="FAQ-docpictex.html">documentation</a>. <li> <i>epic</i> was designed to make use of the LaTeX <code>picture</code> environment somewhat less agonising; <i>eepic</i> extends it, and is capable of using <i>tpic</i> <code>\</code><code>special</code> commands to improve printing performance. (If the - <code>\</code><code>special</code>s aren’t available, the <i>eepicemu</i> will do the + <code>\</code><code>special</code>s aren’t available, the <i>eepicemu</i> will do the business, far less efficiently. <li> <i>pict2e</i>; this was advertised in - <a href="FAQ-books.html">the LaTeX manual</a>, but didn’t appear for nearly + <a href="FAQ-books.html">the LaTeX manual</a>, but didn’t appear for nearly ten years after publication of the book! It removes all the petty restrictions that surround the use of the <code>picture</code> environment. It therefore suffers <em>only</em> from the rather eccentric drawing language of the environment, and is a far more useful tool than the original environment has ever been. (Note that - <i>pict2e</i> supersedes David Carlisle’s stop-gap + <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 PostScript from TeX itself, by sophisticated use of @@ -36,11 +36,11 @@ of drawing, and setup, here are a few systems you may consider: principle be achieved using <i>PSTricks</i> (a wide range of contributed packages, ranging from world mapping to lens design diagrams, is available). - <i>Pstricks</i>’ <code>\</code><code>special</code>s are + <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>pst-pdf</i>, which (like - <i>epstopdf</i> — see + <i>epstopdf</i> — see <a href="FAQ-pdftexgraphics.html">PDFLaTeX graphics</a>) generates PDF files using an auxiliary program, from <i>PSTricks</i> commands (<i>pst-pdf</i> also requires a recent installation of @@ -53,24 +53,24 @@ of drawing, and setup, here are a few systems you may consider: <li> <i>pgf</i>: while <i>pstricks</i> is very powerful and convenient, using it with PDFLaTeX is an awful fidget: if you simply want the graphical capabilities, <i>pgf</i>, together with - its rather pleasing “user-oriented” interface <i>tikz</i>, may be a good + its rather pleasing “user-oriented” interface <i>tikz</i>, may be a good bet for you. While PDF has (in essence) the same graphical - capabilities as PostScript, it isn’t programmable; <i>pgf</i> provides + capabilities as PostScript, it isn’t programmable; <i>pgf</i> provides common LaTeX commands that will utilise the graphical capabilities of both PostScript and PDF equally. <li> MetaPost; you liked Metafont, but never got to grips with font files? - Try <a href="FAQ-MP.html">MetaPost</a> — + Try <a href="FAQ-MP.html">MetaPost</a> — all the power of Metafont, but it generates PostScript figures; MetaPost is nowadays part of most serious (La)TeX distributions. Knuth - uses it for all his work… -<li> <i>Mfpic</i>; you liked Metafont, but can’t understand the + uses it for all his work… +<li> <i>Mfpic</i>; you liked Metafont, but can’t understand the language? The package makes up Metafont or MetaPost code for you within using familiar-looking TeX macros. Not <em>quite</em> the full power of MetaPost, but a friendlier interface; of course, with MetaPost output, the results can be used equally well in either LaTeX or PDFLaTeX. -<li> You liked PicTeX but don’t have enough memory or time? Look - at Eitan Gurari’s <i>dratex</i>, which is as powerful as most +<li> You liked PicTeX but don’t have enough memory or time? Look + at Eitan Gurari’s <i>dratex</i>, which is as powerful as most other TeX drawing packages, but is an entirely new implementation, which is not as hard on memory, is much more readable (and is fully documented). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html index bb395b8b06a..6f8d62fc31f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-driver.html @@ -13,7 +13,7 @@ the output from a PostScript driver. <p/>As well as the DVI file, the driver also needs font information. Font information may be held as bitmaps or as outlines, or simply as a -set of pointers into the fonts that the printer itself ‘has’. +set of pointers into the fonts that the printer itself ‘has’. Each driver will expect the font information in a particular form. For more information on the forms of fonts, see <a href="FAQ-pk.html">PK files</a>, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html index 36609a74587..b4aedbe80a2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dropping.html @@ -5,9 +5,9 @@ <p/>A common style of typesetting, now seldom seen except in newspapers, is to start a paragraph (in books, usually the first of a chapter) with its first letter set large enough to span several lines. -<p/>This style is known as “dropped capitals”, or (in French) +<p/>This style is known as “dropped capitals”, or (in French) «lettrines», -and TeX’s primitive facilities for hanging indentation make its +and TeX’s primitive facilities for hanging indentation make its (simple) implementation pretty straightforward. <p/>The <i>dropping</i> package does the job simply, but has a curious attitude to the calculation of the size of the font to be used for the @@ -21,7 +21,7 @@ alone such modernisms as XeTeX. As a result, the package is widely deprecated, nowadays. <p/>The more recent <i>lettrine</i> package is generally more reliable. It has a well-constructed array of options, and an impressive set of -examples adds to the package’s document. +examples adds to the package’s document. <dl> <dt><tt><i>dropping</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dropping.zip">macros/latex/contrib/dropping</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dropping/">browse the directory</a>) <dt><tt><i>lettrine</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lettrine.zip">macros/latex/contrib/lettrine</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lettrine/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html index 7b1dfac3778..8df2ae0506c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dtx.html @@ -5,16 +5,16 @@ <p/>LaTeX2e, and most contributed macro packages, are now written in a <a href="FAQ-lit.html">literate programming style</a>, with source and documentation in the -same file. This format, known as ‘doc’, in fact originated before the -days of the LaTeX project as one of the “Mainz” series of +same file. This format, known as ‘doc’, in fact originated before the +days of the LaTeX project as one of the “Mainz” series of packages. A documented source file conventionally has the suffix -<code>.dtx</code>, and will normally be ‘stripped’ before use with +<code>.dtx</code>, and will normally be ‘stripped’ before use with LaTeX; an installation file (<code>.ins</code>) is normally provided, to automate this process of removing comments for speed of loading. To read the comments, you can run LaTeX on the <code>.dtx</code> file to produce a nicely formatted version of the documented code. Several -packages can be included in one <code>.dtx</code> file (they’re sorted +packages can be included in one <code>.dtx</code> file (they’re sorted out by the <code>.ins</code> file), with conditional sections, and there are facilities for indexes of macros, etc. <p/>Anyone can write <code>.dtx</code> files; the format is explained in diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html index fe04daa45f2..ca3d26e85c0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi-bmp.html @@ -5,21 +5,21 @@ <p/>In the last analysis, any DVI driver or previewer is generating bitmaps: bitmaps for placing tiny dots on paper via a laser- or inkjet-printer, or bitmaps for filling some portion of your screen. -However, it’s usually difficult to extract any of those bitmaps any +However, it’s usually difficult to extract any of those bitmaps any way other than by screen capture, and the resolution of <em>that</em> is commonly lamentable. <p/>Why would one want separate bitmaps? Most often, the requirement is for something that can be included in HTML generated from (La)TeX -source — not everything that you can write in (La)TeX can be +source — not everything that you can write in (La)TeX can be translated to HTML (at least, portable HTML that may be -viewed in ‘most’ browsers), so the commonest avoiding action is to +viewed in ‘most’ browsers), so the commonest avoiding action is to generate a bitmap of the missing bit. Examples are maths (a maths -extension to the ‘<code>*</code>ML’ family is available but not -universally supported by browsers), and ‘exotic’ typescripts (ones +extension to the ‘<code>*</code>ML’ family is available but not +universally supported by browsers), and ‘exotic’ typescripts (ones that you cannot guarantee your readers will have available). Other common examples are generation of sample bitmaps, and generation for insertion into some other -application’s display — to insert equations into Microsoft +application’s display — to insert equations into Microsoft PowerPoint, or to support the enhanced-<i>emacs</i> setup called <a href="FAQ-WYGexpts.html"><i>preview</i>-<i>latex</i></a>. <p/>In the past, the commonest way of generating bitmaps was to generate a @@ -28,7 +28,7 @@ produce the required bitmap format (possibly by way of PNM format or something similar). This is an undesirable procedure (it is very slow, and requires two or three steps) but it has served for a long time. -<p/>(La)TeX users may now take advantage of two bitmap ‘drivers’. The +<p/>(La)TeX users may now take advantage of two bitmap ‘drivers’. The longer-established, <i>dvi2bitmap</i>, will generate XBM and XPM formats, the long-deprecated GIF format (which is now obsolescent, but has finally been relieved of the patent diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html index c964f8592bd..4a009df5f88 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvi.html @@ -3,10 +3,10 @@ </head><body> <h3>What is a DVI file?</h3> <p/>A DVI file (that is, a file with the type or extension -<code>.dvi</code>) is TeX’s main output file, when we use -“original” TeX (later TeX systems, such as PDFTeX — see +<code>.dvi</code>) is TeX’s main output file, when we use +“original” TeX (later TeX systems, such as PDFTeX — see <a href="FAQ-whatpdftex.html">PDFTeX</a> may use other formats). -<p/>‘DVI’ is supposed to +<p/>‘DVI’ is supposed to be an acronym for DeVice-Independent, meaning that the file can be processed for printing or viewing on most kinds of typographic output device or display. The DVI file @@ -21,7 +21,7 @@ or previewing except for the actual bitmaps or outlines of fonts, and possibly material to be introduced by means of <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>. <p/>The canonical reference for the structure of a DVI file is the -source of Knuth’s program <i>dvitype</i> (whose original purpose, +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="http://www.tex.ac.uk/tex-archive/systems/knuth/dist/texware/dvitype.web">systems/knuth/dist/texware/dvitype.web</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html index c9537b69397..96afcc65da1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipdfmgraphics.html @@ -9,12 +9,12 @@ output using <i>dvips</i> and then convert that to PDF with <p/><i>Dvipdfm</i>/<i>Dvipdfmx</i> are particularly flexible applications. They permit the inclusion of bitmap and PDF graphics, as does <a href="FAQ-pdftexgraphics.html">PDFTeX</a>, but are also -capable of employing <i>ghostscript</i> “on the fly” so as to be +capable of employing <i>ghostscript</i> “on the fly” so as to be able to permit the inclusion of encapsulated PostScript (<code>.eps</code>) files by translating them to PDF. In this way, they combine the good qualities of <i>dvips</i> and of PDFTeX as a means of processing illustrated documents. -<p/>Unfortunately, “ordinary” LaTeX can’t deduce the bounding box of +<p/>Unfortunately, “ordinary” LaTeX can’t deduce the bounding box of a binary bitmap file (such as JPEG or PNG), so you have to specify the bounding box. This may be done explicitly, in the document: @@ -25,7 +25,7 @@ document: \includegraphics[bb=0 0 540 405]{photo.jpg} </pre> </blockquote><p> -It’s usually not obvious what values to give the “<code>bb</code>” key, +It’s usually not obvious what values to give the “<code>bb</code>” key, but the program <i>ebb</i> will generate a file containing the information; the above numbers came from an <i>ebb</i> output file <i>photo.bb</i>: @@ -51,12 +51,12 @@ which makes the operation feel as simple as does including <i>dvips</i>; the <i>graphicx</i> package knows to look for a <code>.bb</code> file if no bounding box is provided in the <code>\</code><code>includegraphics</code> command. -<p/>The one place where usage isn’t quite so simple is the need to quote +<p/>The one place where usage isn’t quite so simple is the need to quote <i>dvipdfm</i> explicitly, as an option when loading the <i>graphicx</i> package: if you are using <i>dvips</i>, you -don’t ordinarily need to specify the fact, since the default graphics -configuration file (of most distributions) “guesses” the -<code>dvips</code> option if you’re using TeX. +don’t ordinarily need to specify the fact, since the default graphics +configuration file (of most distributions) “guesses” the +<code>dvips</code> option if you’re using TeX. <dl> <dt><tt><i>dvipdfm</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse the directory</a>) <dt><tt><i>dvipdfmx</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfmx.zip">dviware/dvipdfmx</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfmx/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html index 9da7380561b..bfcfef7d352 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips-pdf.html @@ -5,8 +5,8 @@ <!-- blurry fuzzy crippled --> <p/>Any reasonable PostScript, including any output of <i>dvips</i>, may be converted to PDF, using (for example) a sufficiently recent -version of <i>ghostscript</i>, Frank Siegert’s (shareware) -<a href="http://www.pstill.com/"><i>PStill</a></i>, or Adobe’s (commercial) +version of <i>ghostscript</i>, Frank Siegert’s (shareware) +<a href="http://www.pstill.com/"><i>PStill</a></i>, or Adobe’s (commercial) <i>Distiller</i>. <p/>But, although the job may (almost always) be done, the results are often not acceptable: the most frequent problem is bad presentation of @@ -21,24 +21,24 @@ Issues covered are: <li> <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1 encoding</a>, which is yet another possible cause of fuzzy text. -<li> Another problem — missing characters — arises from an +<li> Another problem — missing characters — arises from an <a href="FAQ-distill-prob.html">aged version of <i>Adobe</i> <i>Distiller</i></a>. -<li> Finally, there’s the common confusion that arises from using the +<li> Finally, there’s the common confusion that arises from using the <i>dvips</i> configuration file <code>-Ppdf</code>, the <a href="FAQ-charshift.html">weird characters</a>. </ul> It should be noted that <i>Adobe</i> <i>Reader</i> 6 (released in mid-2003, and later versions) does -not exhibit the “fuzziness” that so many of the answers below +not exhibit the “fuzziness” that so many of the answers below address. This is of course good news: however, it will inevitably be a long time before every user in the world has this (or later) versions, so the remedies below are going to remain for some time to come. <p/>The problems are also discussed, with practical examples, in Mike -Shell’s <i>testflow</i> package, which these FAQs recommend as a -“<a href="FAQ-tutbitslatex.html">specialised tutorial</a>. +Shell’s <i>testflow</i> package, which these FAQs recommend as a +“<a href="FAQ-tutbitslatex.html">specialised tutorial</a>. <dl> <dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html index 115b02312e0..3fc904e41a5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvips.html @@ -3,9 +3,9 @@ </head><body> <h3>DVI to PostScript conversion programs</h3> <p/>The best public domain DVI to PostScript conversion program, which -runs under many operating systems, is Tom Rokicki’s <i>dvips</i>. +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> +development is in the context of Karl Berry’s <i>kpathsea</i> library, and sources are available from the TeX Live repository, and versions are available in all TeX distributions that recognise the use of PostScript. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html index d645229c75c..70425074fd0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html @@ -12,10 +12,10 @@ applications produce corrupt EPS when asked for such output, this is pretty satisfactory for vector graphics work. <p/>To include bitmap graphics, you need some means of converting them to PostScript; in fact many standard image manipulators (such as -<i>ImageMagick</i>’s <i>convert</i>) make a good job of +<i>ImageMagick</i>’s <i>convert</i>) make a good job of creating EPS files (but be sure to ask for output at PostScript level 2 or higher). (<i>Unix</i> users should beware of -<i>xv</i>’s claims: it has a tendency to downsample your bitmap to +<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), @@ -23,10 +23,10 @@ JPEG files using PostScript level 2 functionality), 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”. +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 +using <i>bmeps</i>’s conversion library. <i>Dvips</i>, as distributed by MiKTeX, comes with those patches built-in, but assuming that capability destroys portability, and is only recommendable if you are sure you will never want to share your diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html index 14e4e09b747..cb01d34aeec 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-edef.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label edef</title> </head><body> <h3><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></h3> -<p/>Robust LaTeX commands are either “naturally robust” — meaning that -they never need <code>\</code><code>protect</code>, or “self-protected” — meaning that +<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, 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 +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 +<code>\</code><code>protect</code> mechanism working. There’s a corresponding <code>\</code><code>protected@xdef</code> which does the job of <code>\</code><code>xdef</code>. -<p/>Of course, these commands need to be tended carefully, since they’re +<p/>Of course, these commands need to be tended carefully, since they’re -internal: see <a href="FAQ-atsigns.html">’@’ in control sequence names</a>. +internal: see <a href="FAQ-atsigns.html">’@’ in control sequence names</a>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html index f912a03fdbb..1b4150fb327 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html @@ -35,19 +35,19 @@ personal selection: external programs, and more. It was designed with both the beginner and the advanced LaTeX user in mind. <p/> The <i>Kile</i> editor that is provided with the KDE - window manager provides GUI “shell-like” facilities, in a + window manager provides GUI “shell-like” facilities, in a similar way to the widely-praised <i>Winedt</i> (see below); - details (and downloads) are available from the project’s + details (and downloads) are available from the project’s <a href="http://kile.sourceforge.net/">home on SourceForge</a>. A newer - system (by <i>Kile</i>’s original author), - <a href="http://www.xm1math.net/texmaker/"><i>texmaker</a></i> doesn’t - rely on KDE’s facilities, and so may be more easily portable. + system (by <i>Kile</i>’s original author), + <a href="http://www.xm1math.net/texmaker/"><i>texmaker</a></i> doesn’t + rely on KDE’s facilities, and so may be more easily portable. <dt>MSDOS<dd> TeXshell is a simple, easily-customisable environment, which can be used with the editor of your choice. <p/> You can also use GNU <i>emacs</i> and AUC-TeX under MSDOS. -<dt>Windows ’9x, NT, etc.<dd><i>TeXnicCenter</i> is a (free) +<dt>Windows ’9x, NT, etc.<dd><i>TeXnicCenter</i> is a (free) TeX-oriented development system, uniting a powerful platform for executing (La)TeX and friends with a configurable editor. <p/> <i>Winedt</i>, a shareware package, is also highly spoken of. @@ -55,7 +55,7 @@ personal selection: 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). + “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. @@ -76,7 +76,7 @@ personal selection: cross-platform editor and shell, modelled on the excellent TeXshop for the Macintosh. While this program, <a href="http://www.tug.org/texworks/">TeXworks</a>, is still under - development, it is already quite usable: if you’re looking for a + development, it is already quite usable: if you’re looking for a (La)TeX development environment, and are willing to step beyond the boundaries, it may be for you. </dl> @@ -85,9 +85,9 @@ environments. LaTeX users looking for <i>make</i>-like facilities should review the answer on <a href="FAQ-make.html">Makefiles for LaTeX documents</a>. <p/>While many (La)TeX-oriented editors can support work on BibTeX -files, there are many systems that provide specific “database-like” -access to your BibTeX files — - see “<a href="FAQ-buildbib.html">creating a bibliography file</a>”. +files, there are many systems that provide specific “database-like” +access to your BibTeX files — + see “<a href="FAQ-buildbib.html">creating a bibliography file</a>”. <dl> <dt><tt><i>alpha</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/mac/support/alpha/">systems/mac/support/alpha/</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html index 067680f0e85..56e0e35b7e8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-empty.html @@ -11,26 +11,26 @@ and <code>\</code><code>cmd{blah}</code>. This is pretty simple: \def\tempa{}% \def\tempb{#1}% \ifx\tempa\tempb - <empty case> + <empty case> \else - <non-empty case> + <non-empty case> \fi } </pre> </blockquote><p> The case where you want to ignore an argument that consists of nothing but spaces, rather than something completely empty, is more tricky. -It’s solved in the code fragment <i>ifmtarg</i>, which defines +It’s solved in the code fragment <i>ifmtarg</i>, which defines commands <code>\</code><code>@ifmtarg</code> and <code>\</code><code>@ifnotmtarg</code>, which examine their first argument, and select (in opposite directions) their second or -third argument. The package’s code also appears in the LaTeX +third argument. The package’s code also appears in the LaTeX <i>memoir</i> class. -<p/><i>Ifmtarg</i> makes challenging reading; there’s also a discussion of the -issue in number two of the “around the bend” articles by the late +<p/><i>Ifmtarg</i> makes challenging reading; there’s also a discussion of the +issue in number two of the “around the bend” articles by the late lamented Mike Downes. <dl> <dt><tt><i>Around the bend series</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/challenges/aro-bend.zip">info/challenges/aro-bend</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/challenges/aro-bend/">browse the directory</a>) -<dt><tt><i>ifmtarg.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/ifmtarg.sty">macros/latex/contrib/misc/ifmtarg.sty</a> +<dt><tt><i>ifmtarg.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ifmtarg.zip">macros/latex/contrib/ifmtarg</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ifmtarg/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-emptynum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-emptynum.html index b748fb01e76..da54f7e85ba 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-emptynum.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-emptynum.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label emptynum</title> </head><body> -<h3>I asked for “empty”, but the page is numbered</h3> +<h3>I asked for “empty”, but the page is numbered</h3> <p/>If you use <code>\</code><code>pagestyle{empty}</code> and you find some pages are numbered anyway, you are probably encountering one of the style decisions built into the standard LaTeX classes: that certain @@ -26,8 +26,8 @@ or (in <i>book</i> or <i>report</i>) \thispagestyle{empty} </pre> </blockquote><p> -A similar technique doesn’t work for a <i>book</i> or <i>report</i> +A similar technique doesn’t work for a <i>book</i> or <i>report</i> <code>\</code><code>part</code> command pages. For that, and for other detail, take look -at “<a href="FAQ-nopageno.html">getting rid of page numbers</a>”. +at “<a href="FAQ-nopageno.html">getting rid of page numbers</a>”. <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=emptynum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=emptynum</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html index a2a3b776cc6..ac9aaed04c6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-endingroup.html @@ -4,16 +4,16 @@ <h3><code>\</code><code>end</code> occurred inside a group</h3> <p/>The actual error we observe is: <p/> -<code>(\end occurred inside a group at level <</code><code><em>n</em></code><code>>)</code> +<code>(\end occurred inside a group at level <</code><code><em>n</em></code><code>>)</code> <p/> and it tells us that something we started in the document never got finished before we ended the document itself. The things involved -(‘groups’) are what TeX uses for restricting the scope of things: -you see them, for example, in the “traditional” font selection -commands: <code>{\it stuff\/}</code> — if the closing brace is left off such a +(‘groups’) are what TeX uses for restricting the scope of things: +you see them, for example, in the “traditional” font selection +commands: <code>{\it stuff\/}</code> — if the closing brace is left off such a construct, the effect of <code>\</code><code>it</code> will last to the end of the document, -and you’ll get the diagnostic. -<p/>TeX itself doesn’t tell you where your problem is, but you can +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 <i>emacs</i> and <i>winedt</i> offer this facility). @@ -21,33 +21,33 @@ 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 +<p/><code>\</code><code>begin{<<i>environment</i>>}</code> encloses the environment’s body in a group, and establishes its own diagnostic mechanism. If you end the document before closing some other environment, you get the -‘usual’ LaTeX diagnostic +‘usual’ LaTeX diagnostic <pre> ! LaTeX Error: \begin{blah} on input line 6 ended by \end{document}. </pre> -which (though it doesn’t tell you which <em>file</em> the +which (though it doesn’t tell you which <em>file</em> the <code>\</code><code>begin{blah}</code> was in) is usually enough to locate the immediate problem. If you press on past the LaTeX error, you get -one or more repetitions of the “occurred inside a group” message +one or more repetitions of the “occurred inside a group” message before LaTeX finally exits. The <i>checkend</i> package recognises other unclosed <code>\</code><code>begin{blob}</code> commands, and -generates an “ended by” error message for each one, rather than -producing the “occurred inside a group” message, which is sometimes +generates an “ended by” error message for each one, rather than +producing the “occurred inside a group” message, which is sometimes useful (if you remember to load the package). <p/>In the absence of such information from LaTeX, you need to use -“traditional” binary search to find the offending group. Separate +“traditional” binary search to find the offending group. Separate the preamble from the body of your file, and process each half on its own with the preamble; this tells you which half of the file is at fault. Divide again and repeat. The process needs to be conducted -with care (it’s obviously possible to split a correctly-written group +with care (it’s obviously possible to split a correctly-written group by chopping in the wrong place), but it will usually find the problem fairly quickly. -<p/>e-TeX (and e-LaTeX — LaTeX run on e-TeX) gives you -further diagnostics after the traditional infuriating TeX one — it +<p/>e-TeX (and e-LaTeX — LaTeX run on e-TeX) gives you +further diagnostics after the traditional infuriating TeX one — it actually keeps the information in a similar way to LaTeX: <pre> @@ -63,7 +63,7 @@ The diagnostic not only tells us where the group started, but also the <code>\</code><code>bgroup</code>, and the two are not distinguishable at the TeX-engine level). <dl> -<dt><tt><i>checkend.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos.zip">macros/latex/contrib/bezos</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos/">browse the directory</a>) +<dt><tt><i>checkend.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos.zip">macros/latex/contrib/bezos</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/checkend.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html index 6b4f7dae543..c06e100274f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enlarge.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label enlarge</title> </head><body> <h3>Enlarging TeX</h3> -<p/>The TeX error message ‘capacity exceeded’ covers a multitude of +<p/>The TeX error message ‘capacity exceeded’ covers a multitude of problems. What has been exhausted is listed in brackets after the error message itself, as in: <blockquote> @@ -17,13 +17,13 @@ extra-long lines, and poorly-written macros. Extra-long lines are often introduced when files are transferred incorrectly between operating systems, and line-endings are not preserved properly (the tell-tale sign of an extra-long line error is the complaint -that the ‘<code>buf_size</code>’ has overflowed). -<p/>If you really need to extend your TeX’s capacity, the proper method +that the ‘<code>buf_size</code>’ has overflowed). +<p/>If you really need to extend your TeX’s capacity, the proper method depends on your installation. There is no need (with modern TeX -implementations) to change the defaults in Knuth’s WEB source; +implementations) to change the defaults in Knuth’s WEB source; but if you do need to do so, use a change file to modify the values set in module 11, recompile your TeX and regenerate all format files. -<p/>Modern implementations allow the sizes of the various bits of TeX’s +<p/>Modern implementations allow the sizes of the various bits of TeX’s memory to be changed semi-dynamically. Some (such as emTeX) allow the memory parameters to be changed in command-line switches when TeX is started; most frequently, a configuration file is read which diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html index edf4b689a28..99150c4a54d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-entercompmode.html @@ -9,14 +9,14 @@ Entering LaTeX 2.09 COMPATIBILITY MODE </pre> </blockquote><p> followed by lines of asterisks and <code>!!WARNING!!</code>. -<p/>This means that the document is not written in “current” LaTeX +<p/>This means that the document is not written in “current” LaTeX syntax, and that there is no guarantee that all parts of the document will be formatted correctly. -<p/>If the document is someone else’s, and you want no more than a copy to +<p/>If the document is someone else’s, and you want no more than a copy to read, ignore the error. The document may fail elsewhere, but as often -as not it will provide a <code>.dvi</code> or <code>.pdf</code> that’s +as not it will provide a <code>.dvi</code> or <code>.pdf</code> that’s adequate for most purposes. -<p/>If it’s a new document you have just started working on, you have been +<p/>If it’s a new document you have just started working on, you have been misled by someone. You have written something like: <blockquote> <code>\</code><code>documentstyle{article}</code> @@ -35,8 +35,8 @@ should become: <blockquote> <code>\</code><code>documentclass{article}</code> </blockquote><p> -The complex form is more difficult, since LaTeX 2.09 “options” -conflate two sorts of things — options for the class (such as +The complex form is more difficult, since LaTeX 2.09 “options” +conflate two sorts of things — options for the class (such as <code>11pt</code>, <code>fleqn</code>), and packages to be loaded. So: <blockquote> @@ -49,16 +49,16 @@ should become: </blockquote><p> because <code>11pt</code> happens to be a class option, while <i>verbatim</i> is a package. -<p/>There’s no simple way to work out what are class options under +<p/>There’s no simple way to work out what are class options under LaTeX 2.09; for <i>article</i>, the list includes <code>10pt</code>, <code>11pt</code>, <code>12pt</code>, <code>draft</code>, <code>fleqn</code>, <code>leqno</code>, <code>twocolumn</code> and -<code>twoside</code> — anything else must be a package. -<p/>Your document may well “just work” after changes like those above; -if not, you should think through what you’re trying to do, and consult -documentation on how to do it — there are lots of +<code>twoside</code> — anything else must be a package. +<p/>Your document may well “just work” after changes like those above; +if not, you should think through what you’re trying to do, and consult +documentation on how to do it — there are lots of <a href="FAQ-tutorialstar.html">free tutorials</a> to help you on your way, if you -don’t have access to a LaTeX manual of any sort. +don’t have access to a LaTeX manual of any sort. <p/> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html index e88fd3b7053..d7a48becb07 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-enumerate.html @@ -6,8 +6,8 @@ the enumeration counter. The package adds an optional parameter to the <code>enumerate</code> environment, which is used to specify the layout of the labels. The layout parameter contains an enumeration -type (‘<code>1</code>’ for arabic numerals, ‘<code>a</code>’ or ‘<code>A</code>’ -for alphabetic enumeration, and ‘<code>i</code>’ or ‘<code>I</code>’ for Roman +type (‘<code>1</code>’ for arabic numerals, ‘<code>a</code>’ or ‘<code>A</code>’ +for alphabetic enumeration, and ‘<code>i</code>’ or ‘<code>I</code>’ for Roman numerals), and things to act as decoration of the enumeration. So, for example <blockquote> @@ -19,7 +19,7 @@ for example \end{enumerate} </pre> </blockquote><p> -starts a list whose labels run (a), (b), (c), …; while +starts a list whose labels run (a), (b), (c), …; while <blockquote> <pre> \usepackage{enumerate} @@ -29,7 +29,7 @@ starts a list whose labels run (a), (b), (c), …; while \end{enumerate} </pre> </blockquote><p> -starts a list whose labels run I/, II/, III/, … +starts a list whose labels run I/, II/, III/, … <p/>The <i>paralist</i> package, whose primary purpose is <a href="FAQ-complist.html">compaction of lists</a>, provides the same facilities for its <code>enumerate</code>-like environments. @@ -45,7 +45,7 @@ The silly roman example above could be achieved by: \end{enumerate} </pre> </blockquote><p> -Note that the ‘<code>*</code>’ in the key value stands for the list +Note that the ‘<code>*</code>’ in the key value stands for the list counter at this level. You can also manipulate the format of references to list item labels: <blockquote> @@ -80,7 +80,7 @@ to make references to the list items format appear as (i), (ii), <dl> -<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/enumerate.html">catalogue entry</a> <dt><tt><i>enumitem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>paralist.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html index c71346ed210..da52cfb5959 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epigraph.html @@ -7,7 +7,7 @@ chapters (or even at the end of chapters: Knuth puts things at the ends of chapters of the TeXbook). <p/>Typesetting them is a bit of a fiddle, but not impossible to do for yourself. Fortunately, there are two packages that do the job, to -some extent; there are also facilities in the two “big” classes +some extent; there are also facilities in the two “big” classes (<i>memoir</i> and <i>koma-script</i>. <p/>The <i>epigraph</i> package defines an <code>\</code><code>epigraph</code> command, for creating a single @@ -38,26 +38,26 @@ The <code>\</code><code>epigraphhead</code> command enables you to place your ep \setlength{\unitlength}{1pt} ... \chapter{The Social Life of Rabbits} -\epigraphhead[<distance>]{% +\epigraphhead[<distance>]{% \epigraph{Oh! My ears and whiskers!}% {Lewis Carroll}% } </pre> </blockquote><p> The <<i>distance</i>> says how far above the chapter heading the -epigraph is to go; it’s expressed in terms of the <code>\</code><code>unitlength</code> -that’s used in the <code>picture</code> environment; the package’s +epigraph is to go; it’s expressed in terms of the <code>\</code><code>unitlength</code> +that’s used in the <code>picture</code> environment; the package’s author recommends <code>70pt</code>. <p/>The package also offers various tricks for adjusting the layout of -chapter header (necessary if you’ve found a hugely long quotation for +chapter header (necessary if you’ve found a hugely long quotation for an <code>\</code><code>epigraphhead</code>), for patching the bibliography, for patching <code>\</code><code>part</code> pages, and so on. (Some of these suggested patches lead you -through writing your own package…) +through writing your own package…) <p/>The <i>quotchap</i> package redefines chapter headings (in a moderately striking way), and provides an environment <code>savequotes</code> in which you can provide one (or more) quotations to use as epigraphs. The facilities seem not as flexible -as those of <i>epigraph</i>, but it’s probably easier to use. +as those of <i>epigraph</i>, but it’s probably easier to use. <p/>The <i>memoir</i> class offers all the facilities of the <i>epigraph</i> package. The <i>Koma-script</i> classes have commands <code>\</code><code>setchapterpreamble</code> and <code>\</code><code>dictum</code> to provide these diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html index 4ccda2bdc9b..8675d27bd1d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eplain.html @@ -4,21 +4,21 @@ <h3>What is Eplain?</h3> <p/>The <a href="http://tug.org/eplain">Eplain</a> macro package expands on and extends the definitions in Plain TeX. -Eplain is not intended to provide “generic typesetting -capabilities”, as do ConTeXt, LaTeX or +Eplain is not intended to provide “generic typesetting +capabilities”, as do ConTeXt, LaTeX or <a href="FAQ-texinfo.html">Texinfo</a>. Instead, it defines macro tools that should be useful whatever commands you choose to use when you prepare your manuscript. <p/>For example, Eplain does not have a command <code>\</code><code>section</code>, -which would format section headings in an “appropriate” way, as -LaTeX’s <code>\</code><code>section</code> does. The philosophy of Eplain is that -some people will always need or want to go beyond the macro designer’s -idea of “appropriate”. Such canned macros are fine — as long as you -are willing to accept the resulting output. If you don’t like the +which would format section headings in an “appropriate” way, as +LaTeX’s <code>\</code><code>section</code> does. The philosophy of Eplain is that +some people will always need or want to go beyond the macro designer’s +idea of “appropriate”. Such canned macros are fine — as long as you +are willing to accept the resulting output. If you don’t like the results, or if you are trying to match a different format, you are out of luck. <p/>On the other hand, almost everyone would like capabilities such as -cross-referencing by labels, so that you don’t have to put actual page +cross-referencing by labels, so that you don’t have to put actual page numbers in the manuscript. The authors of Eplain believe it is the only generally available macro package that does not force its typographic style on an author, and yet provides these such capabilities. @@ -32,7 +32,7 @@ a URL). users are lacking, most notably text colouring and rotation provided by the <i>graphics</i> bundle (packages <i>color</i> and <i>graphics</i>). Although the <i>graphics</i> bundle provides -a Plain TeX “loader” for some of the packages, it is not a +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 much of the functionality of the packages is accessed through package options. Eplain extends the loader so that options can be passed @@ -41,8 +41,8 @@ known to work with Eplain: <i>graphics</i>, <i>graphicx</i>, <i>color</i>, <i>autopict</i> (LaTeX picture environment), <i>psfrag</i>, and <i>url</i>. <p/><a href="http://tug.org/docs/html/eplain">Eplain documentation</a> is -available online, and there’s -also a mailing list — sign up, or browse the list archives, via +available online, and there’s +also a mailing list — sign up, or browse the list archives, via <a href="http://tug.org/mailman/listinfo/tex-eplain">http://tug.org/mailman/listinfo/tex-eplain</a> <dl> <dt><tt><i>Eplain distribution</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/eplain.zip">macros/eplain</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html index 53fc6588cf1..c4ad7a11d4c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eps.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label eps</title> </head><body> -<h3>What is “Encapsulated PostScript” (“EPS”)?</h3> +<h3>What is “Encapsulated PostScript” (“EPS”)?</h3> <p/>PostScript has been for many years a <em>lingua franca</em> of powerful printers (though modern high-quality printers now tend to require some constrained form of Adobe Acrobat, instead); since PostScript is also a @@ -9,30 +9,30 @@ powerful graphical programming language, it is commonly used as an output medium for drawing (and other) packages. <p/>However, since PostScript <em>is</em> such a powerful language, some rules need to be imposed, so that the output drawing may be included -in a document as a figure without “leaking” (and thereby destroying +in a document as a figure without “leaking” (and thereby destroying the surrounding document, or failing to draw at all). <p/>Appendix H of the PostScript Language Reference Manual (second and subsequent editions), specifies a set of rules for PostScript to be used as figures in this way. The important features are: <ul> -<li> certain “structured comments” are required; important ones are +<li> certain “structured comments” are required; important ones are the identification of the file type, and information about the - “bounding box” of the figure (i.e., the minimum rectangle + “bounding box” of the figure (i.e., the minimum rectangle enclosing it); -<li> some commands are forbidden — for example, a <code>showpage</code> +<li> some commands are forbidden — for example, a <code>showpage</code> command will cause the image to disappear, in most TeX-output environments; and -<li> “preview information” is permitted, for the benefit of things - such as word processors that don’t have the ability to draw - PostScript in their own right — this preview information may be in +<li> “preview information” is permitted, for the benefit of things + such as word processors that don’t have the ability to draw + PostScript in their own right — this preview information may be in any one of a number of system-specific formats, and any viewing program may choose to ignore it. </ul> A PostScript figure that conforms to these rules is said to be in -“Encapsulated PostScript” (EPS) format. Most (La)TeX packages for +“Encapsulated PostScript” (EPS) format. Most (La)TeX packages for including PostScript are structured to use Encapsulated PostScript; which of course leads to much hilarity as exasperated (La)TeX users struggle to cope with the output of drawing software whose authors -don’t know the rules. +don’t know the rules. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html index 10eab64cd9b..e08298f252c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-epsf.html @@ -14,9 +14,9 @@ too literally, you get an error </pre> after a while; this is because each time <i>epsf.tex</i> is loaded, it allocates itself a <em>new</em> file-reading handle to check the figure -for its bounding box, and there just aren’t enough of these things +for its bounding box, and there just aren’t enough of these things (see <a href="FAQ-noroom.html">no room for a new thing</a>). -<p/>The solution is simple — this is in fact an example of misuse of +<p/>The solution is simple — this is in fact an example of misuse of macros; one only need read <i>epsf.tex</i> once, so change <pre> ... diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html index 862b17b9d3c..5dfbeebe307 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-eqnarray.html @@ -14,8 +14,8 @@ things, but it makes a serious mess of spacing. In the system: \end{eqnarray} </pre> </blockquote><p> -the spacing around the “=” signs is <em>not</em> that defined in the -metrics for the font from which the glyph comes — it’s +the spacing around the “=” signs is <em>not</em> that defined in the +metrics for the font from which the glyph comes — it’s <code>\</code><code>arraycolsep</code>, which may be set to some very odd value for reasons associated with real arrays elsewhere in the document. <p/>The user is far better served by the AMSLaTeX bundle, which diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html index 5332e1ba795..66464aa1fe3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errmissitem.html @@ -30,7 +30,7 @@ correct: </pre> </blockquote><p> produces the error at the <code>\\</code>. This usage is just wrong; if you -want to number the cells in a table, you have to do it “by hand”: +want to number the cells in a table, you have to do it “by hand”: <blockquote> <pre> \newcounter{tablecell} @@ -80,15 +80,15 @@ seemingly innocent: </pre> </blockquote><p> produces the error (the same happens with <code>\</code><code>mbox</code> in place of -<code>\</code><code>fbox</code>, or with either of their “big brothers”, <code>\</code><code>framebox</code> and +<code>\</code><code>fbox</code>, or with either of their “big brothers”, <code>\</code><code>framebox</code> and <code>\</code><code>makebox</code>). This is because the <code>alltt</code> environment -uses a “trivial” list, hidden inside their definition. (The +uses a “trivial” list, hidden inside their definition. (The <code>itemize</code> environment also has this construct inside -itself, in fact, so <code>\</code><code>begin{itemize}</code> won’t work inside an +itself, in fact, so <code>\</code><code>begin{itemize}</code> won’t work inside an <code>\</code><code>fbox</code>, either.) The list construct wants to happen between paragraphs, so it makes a new paragraph of its own. Inside the -<code>\</code><code>fbox</code> command, that doesn’t work, and subsequent macros convince -themselves that there’s a missing <code>\</code><code>item</code> command. +<code>\</code><code>fbox</code> command, that doesn’t work, and subsequent macros convince +themselves that there’s a missing <code>\</code><code>item</code> command. <p/>To solve this rather cryptic error, one must put the <code>alltt</code> inside a paragraph-style box. The following modification of the above <em>does</em> work: @@ -103,14 +103,14 @@ modification of the above <em>does</em> work: } </pre> </blockquote><p> -The code above produces a box that’s far too wide for the text. One +The code above produces a box that’s far too wide for the text. One may want to use something that allows <a href="FAQ-varwidth.html">variable size boxes</a> in place of the <code>minipage</code> environment. -<p/>Oddly, although the <code>verbatim</code> environment wouldn’t work +<p/>Oddly, although the <code>verbatim</code> environment wouldn’t work inside a <code>\</code><code>fbox</code> command argument (see <a href="FAQ-verbwithin.html">verbatim in command arguments</a>), you -get an error that complains about <code>\</code><code>item</code>: the environment’s +get an error that complains about <code>\</code><code>item</code>: the environment’s internal list bites you before <code>verbatim</code> has even had a chance to create its own sort of chaos. <p/>Another (seemingly) obvious use of <code>\</code><code>fbox</code> also falls foul of this @@ -120,10 +120,10 @@ error: \fbox{\section{Boxy section}} </pre> </blockquote><p> -This is a case where you’ve simply got to be more subtle; you should -either write your own macros to replace the insides of LaTeX’s +This is a case where you’ve simply got to be more subtle; you should +either write your own macros to replace the insides of LaTeX’s sectioning macros, or look for some alternative in the packages discussed in -“<a href="FAQ-secthead.html">The style of section headings</a>”. +“<a href="FAQ-secthead.html">The style of section headings</a>”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html index 3510b490da9..e2d4be2d3d4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-erroradvice.html @@ -7,12 +7,12 @@ difficult to understand; this is a (seemingly invariant) property of macroprocessors. Knuth makes light of the problem in the TeXbook, suggesting that you acquire the sleuthing skills of a latter-day Sherlock Holmes; while this approach has a certain romantic charm to -it, it’s not good for the ‘production’ user of (La)TeX. This +it, it’s not good for the ‘production’ user of (La)TeX. This answer (derived, in part, from an article by Sebastian Rahtz in <i>TUGboat</i> 16(4)) offers some general guidance in dealing with TeX error reports, and other answers in this section deal with common (but -perplexing) errors that you may encounter. There’s a long list of -“hints” in Sebastian’s article, including the following: +perplexing) errors that you may encounter. There’s a long list of +“hints” in Sebastian’s article, including the following: <ul> <li> Look at TeX errors; those messages may seem cryptic at first, but they often contain a straightforward clue to the problem. See @@ -23,8 +23,8 @@ perplexing) errors that you may encounter. There’s a long list of messages. <li> Be aware of the amount of context that TeX gives you. The error messages gives you some bits of TeX code (or of the - document itself), that show where the error “actually happened”; - it’s possible to control how much of this ‘context’ TeX actually + document itself), that show where the error “actually happened”; + it’s possible to control how much of this ‘context’ TeX actually gives you. LaTeX (nowadays) instructs TeX only to give you one line of context, but you may tell it otherwise by saying <blockquote> @@ -32,8 +32,8 @@ perplexing) errors that you may encounter. There’s a long list of \setcounter{errorcontextlines}{999} </pre> </blockquote><p> - in the preamble of your document. (If you’re not a confident macro - programmer, don’t be ashamed of cutting that 999 down a bit; some + in the preamble of your document. (If you’re not a confident macro + programmer, don’t be ashamed of cutting that 999 down a bit; some errors will go on and <em>on</em>, and spotting the differences between those lines can be a significant challenge.) <li> As a last resort, tracing can be a useful tool; reading a full @@ -45,27 +45,27 @@ perplexing) errors that you may encounter. There’s a long list of to understand the trace. <p/> The command <code>\</code><code>tracingall</code> sets up maximum tracing; it also sets the output to come to the interactive terminal, which is somewhat of - a mixed blessing (since the output tends to be so vast — all but + a mixed blessing (since the output tends to be so vast — all but the simplest traces are best examined in a text editor after the event). <p/> The LaTeX <i>trace</i> package (first distributed with the 2001 release of LaTeX) provides more manageable tracing. Its <code>\</code><code>traceon</code> command gives you what <code>\</code><code>tracingall</code> offers, but suppresses tracing around some of the truly verbose parts of LaTeX itself. The package also provides a <code>\</code><code>traceoff</code> - command (there’s no “off” command for <code>\</code><code>tracingall</code>), and a + command (there’s no “off” command for <code>\</code><code>tracingall</code>), and a package option (<code>logonly</code>) allows you to suppress output to the terminal. </ul> The best advice to those faced with TeX errors is not to panic: most of the common errors are plain to the eye when you go back to the -source line that TeX tells you of. If that approach doesn’t work, +source line that TeX tells you of. If that approach doesn’t work, the remaining answers in this section deal with some of the odder error messages you may encounter. You should not ordinarily need to appeal to the <a href="FAQ-gethelp.html">wider public</a> for assistance, but if you do, be sure to report full backtraces (see <code>errorcontextlines</code> above) and so on. <dl> -<dt><tt><i>trace.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>trace.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/trace.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html index 2fc2e255709..a94e151d042 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errparnum.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label errparnum</title> </head><body> <h3>Illegal parameter number in definition</h3> -<p/>The error message means what it says. In the simple case, you’ve +<p/>The error message means what it says. In the simple case, you’ve attempted a definition like: <blockquote> <pre> @@ -17,7 +17,7 @@ or (using TeX primitive definitions): </blockquote><p> In either of the above, the definition uses an argument, but the programmer did not tell (La)TeX, in advance, that she was going to. -The fix is simple — <code>\</code><code>newcommand{<code>\</code><code>abc</code>}[1]</code>, in the +The fix is simple — <code>\</code><code>newcommand{<code>\</code><code>abc</code>}[1]</code>, in the LaTeX case, <code>\def\abc#1</code> in the basic TeX case. <p/>The more complicated case is exemplified by the attempted definition: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html index 5f29857452f..ad8497914d2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-errstruct.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label errstruct</title> </head><body> <h3>The structure of TeX error messages</h3> -<p/>TeX’s error messages are reminiscent of the time when TeX itself -was conceived (the 1970s): they’re not terribly user-friendly, though +<p/>TeX’s error messages are reminiscent of the time when TeX itself +was conceived (the 1970s): they’re not terribly user-friendly, though they do contain all the information that TeX can offer, usually in a pretty concise way. -<p/>TeX’s error reports all have the same structure: +<p/>TeX’s error reports all have the same structure: <ul> <li> An error message -<li> Some ‘context’ +<li> Some ‘context’ <li> An error prompt </ul> The error message will relate to the <em>TeX</em> condition that is causing a problem. Sadly, in the case of complex macro packages such as LaTeX, the underlying TeX problem may be superficially -difficult to relate to the actual problem in the “higher-level” +difficult to relate to the actual problem in the “higher-level” macros. Many LaTeX-detected problems manifest themselves as -‘generic’ errors, with error text provided by LaTeX itself (or by a +‘generic’ errors, with error text provided by LaTeX itself (or by a LaTeX class or package). <p/>The context of the error is a stylised representation of what TeX was doing at the point that it detected the error. As noted in @@ -26,7 +26,7 @@ can tell TeX how much context to display, and the user may need to undo what the package has done. Each line of context is split at the point of the error; if the error <em>actually</em> occurred in a macro called from the present line, the break is at the point of the call. -(If the called object is defined with arguments, the “point of call” +(If the called object is defined with arguments, the “point of call” is after all the arguments have been scanned.) For example: <pre> \blah and so on @@ -45,7 +45,7 @@ while: produces the error report <pre> ! Undefined control sequence. -\blah #1->\bleah +\blah #1->\bleah #1 l.5 \blah{to you} , folks @@ -58,16 +58,16 @@ If the argument itself is in error, we will see things such as producing <pre> ! Undefined control sequence. -<argument> \bleah +<argument> \bleah l.5 \blah{\bleah} , folks </pre> -<p/>The prompt accepts single-character commands: the list of what’s +<p/>The prompt accepts single-character commands: the list of what’s available may be had by typing <code>?</code>. One immediately valuable command is <code>h</code>, which gives you an expansion of TeXs original -précis message, sometimes accompanied by a hint on what to do to -work round the problem in the short term. If you simply type ‘return’ +précis message, sometimes accompanied by a hint on what to do to +work round the problem in the short term. If you simply type ‘return’ (or whatever else your system uses to signal the end of a line) at the prompt, TeX will attempt to carry on (often with rather little success). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html index cc73f99bb87..67f5fd63713 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-etex.html @@ -8,17 +8,17 @@ things that one might wish had been done differently, or indeed implemented at all. <p/>The NTS project set out to produce an advanced replacement for TeX, to provide a basis for developing such modifications: this -“New Typesetting System” would share Knuth’s aims, but would +“New Typesetting System” would share Knuth’s aims, but would implement the work in a modern way taking account of the lessons learned with TeX. While a first demonstrator NTS did -appear, it wasn’t practically useful, and the project seems no longer +appear, it wasn’t practically useful, and the project seems no longer active. <p/>In parallel with its work on NTS itself, the project developed -a set of extensions that can be used with a (“true”) TeX system. +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-based system (for -those who don’t want them, e-TeX’s extensions can be disabled, leaving +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 of available registers from 256 to 32768) through to extremely subtle @@ -31,5 +31,8 @@ work, but not as well as on an e-TeX system. The <a href="FAQ-LaTeX3.html">LaTeX team</a> has announced that future LaTeX packages (specifically those from the team, as opposed to those individually contributed) may require e-TeX for optimum performance. +<dl> +<dt><tt><i>e-TeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/e-tex.zip">systems/e-tex</a> (or <a href="http://www.tex.ac.uk/tex-archive/systems/e-tex/">browse the directory</a>) +</dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html index f841608a906..da29d36ca3c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-euro.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label euro</title> </head><body> <h3>Typesetting the Euro sign</h3> -<p/>The European currency “Euro” is represented by a symbol of somewhat -dubious design, but it’s an important currency and (La)TeX users +<p/>The European currency “Euro” is represented by a symbol of somewhat +dubious design, but it’s an important currency and (La)TeX users need to typeset it. <p/>Note that the Commission of the European Community at first deemed that the Euro symbol should always be set in a sans-serif font; fortunately, this eccentric ruling has now been rescinded, and one may apply best typesetting efforts to making it appear at least slightly -“respectable” (typographically). +“respectable” (typographically). <p/>The TS1-encoded TC fonts provided as part of the EC font distribution provide Euro glyphs. The fonts are called Text Companion (TC) fonts, and offer the same range @@ -17,21 +17,21 @@ of faces as do the EC fonts themselves. The <i>textcomp</i> package provides a <code>\</code><code>texteuro</code> command for accessing the symbol, which selects a symbol to match the surrounding text. The design of the symbol in the TC fonts is not -universally loved… +universally loved… Nevertheless, use the TC font version of the symbol if you are -producing documents using Knuth’s Computer Modern Fonts. +producing documents using Knuth’s Computer Modern Fonts. <p/>The <i>latin9</i> input encoding defined by the <i>inputenc</i> package has a euro character defined (character position 164, occupied -in other ISO Latin character sets by the “currency symbol”). +in other ISO Latin character sets by the “currency symbol”). The encoding uses the command <code>\</code><code>texteuro</code> for the character; at present that command is <em>only</em> available from the <i>textcomp</i> package. There is a Microsoft code page position, too, but standardisation of such things proceeds via rather different -routes and the LaTeX project hasn’t yet been given details of the +routes and the LaTeX project hasn’t yet been given details of the change. <p/>Outline fonts which contain nothing but Euro symbols are available (free) from -<a href="ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe">Adobe</a> — +<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 archive on other operating systems. @@ -51,7 +51,7 @@ Modern environments. They are apparently designed to fit with Adobe Times, Helvetica and Courier, but can probably fit with a wider range of modern fonts. <p/>The <i>eurofont</i> package provides a compendious analysis of the -“problem of the euro symbol” in its documentation, and offers macros +“problem of the euro symbol” in its documentation, and offers macros for configuring the source of the glyphs to be used; however, it seems rather large for everyday use. <p/>The <i>euro-ce</i> bundle is a rather pleasing Metafont-only design diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html index fb1431f03c4..72fc1f8b5cc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-exscale.html @@ -1,15 +1,15 @@ <head> <title>UK TeX FAQ -- question label exscale</title> </head><body> -<h3>Maths symbols don’t scale up</h3> -<p/>By default, the “large” maths symbols stay at the same size -regardless of the font size of the text of the document. There’s good -reason for this: the <i>cmex</i> fonts aren’t really designed to -scale, so that TeX’s maths placement algorithms don’t perform as +<h3>Maths symbols don’t scale up</h3> +<p/>By default, the “large” maths symbols stay at the same size +regardless of the font size of the text of the document. There’s good +reason for this: the <i>cmex</i> fonts aren’t really designed to +scale, so that TeX’s maths placement algorithms don’t perform as well as they might when the fonts are scaled. <p/>However, this behaviour confounds user expectations, and can lead to slightly odd-looking documents. If you want the fonts to scale, -despite the warning above, use the <i>exscale</i> package — just +despite the warning above, use the <i>exscale</i> package — just loading it is enough. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html index 79c17ffe680..f74ac33cbf5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extex.html @@ -6,8 +6,8 @@ building on the experience of the many existing TeX development and extension projects, to develop a new TeX-like system. The system is to be developed in Java (like the ill-fated <i>NTS</i> project). -<p/>While ExTeX will implement all of TeX’s primitives, some may be -marked as obsolete, and “modern” alternatives provided (an obvious +<p/>While ExTeX will implement all of TeX’s primitives, some may be +marked as obsolete, and “modern” alternatives provided (an obvious example is the primitive <code>\</code><code>input</code> command, whose syntax inevitably makes life difficult for users of modern operating system file paths). Desirable extensions from <a href="FAQ-etex.html">e-TeX</a>, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html index 1f68cf4bd74..15caab20dd5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extrabrace.html @@ -1,11 +1,11 @@ <head> <title>UK TeX FAQ -- question label extrabrace</title> </head><body> -<h3>An extra ‘<code>}</code>’??</h3> +<h3>An extra ‘<code>}</code>’??</h3> <!-- caption heading --> -<p/>You’ve looked at your LaTeX source and there’s no sign of a misplaced +<p/>You’ve looked at your LaTeX source and there’s no sign of a misplaced <code>}</code> on the line in question. -<p/>Well, no: this is TeX’s cryptic way of hinting that you’ve put a +<p/>Well, no: this is TeX’s cryptic way of hinting that you’ve put a <a href="FAQ-protect.html">fragile command</a> in a moving argument. <p/>For example, <code>\</code><code>footnote</code> is fragile, and if we put that in the @@ -47,7 +47,7 @@ with <code>\</code><code>protect</code>, which in the <code>\</code><code>sectio In both the <code>\</code><code>section</code> case and the <code>\</code><code>caption</code> case, you can separate the moving argument, as in <code>\</code><code>section[</code><em>moving</em><code>]{</code><em>static</em><code>}</code>; this gives us another standard -route — simply to omit (or otherwise sanitise) the fragile command +route — simply to omit (or otherwise sanitise) the fragile command in the moving argument. So, one might rewrite the <code>\</code><code>caption</code> example as: <blockquote> @@ -57,9 +57,9 @@ example as: </pre> </blockquote><p> for, after all, even if you want display maths in a caption, you -surely don’t want it in the list of figures. +surely don’t want it in the list of figures. <p/>The case of footnotes is somewhat more complex; -“<a href="FAQ-ftnsect.html">footnotes in LaTeX section headings</a>” +“<a href="FAQ-ftnsect.html">footnotes in LaTeX section headings</a>” deals specifically with that issue. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html index 47d2299e8ad..d6ebe3b02f6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extref.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label extref</title> </head><body> <h3>Referring to labels in other documents</h3> -<p/>When producing a set of inter-related documents, you’ll often want to +<p/>When producing a set of inter-related documents, you’ll often want to refer to labels in another document of the set; but LaTeX, of its -own accord, doesn’t permit this. +own accord, doesn’t permit this. <p/>So the package <i>xr</i> was written: if you say <blockquote> <pre> @@ -15,9 +15,9 @@ own accord, doesn’t permit this. will load all the references from <i>volume1</i> into your present document. <p/>But what if the documents both have a section labelled -“<code>introduction</code>” (likely enough, after all)? The +“<code>introduction</code>” (likely enough, after all)? The package provides a means to transform all the imported labels, so you -don’t have to change label names in either document. For example: +don’t have to change label names in either document. For example: <blockquote> <pre> \usepackage{xr} @@ -38,7 +38,7 @@ as: </blockquote><p> To have the facilities of <i>xr</i> working with <i>hyperref</i>, you need <i>xr-hyper</i>. For simple -hyper-cross-referencing (i.e., to a local PDF file you’ve just +hyper-cross-referencing (i.e., to a local PDF file you’ve just compiled), write: <blockquote> <pre> @@ -50,7 +50,7 @@ compiled), write: </pre> </blockquote><p> and the name reference will appear as an active link to the -“introduction” chapter of <i>volume1.pdf</i>. +“introduction” chapter of <i>volume1.pdf</i>. <p/>To link to a PDF document on the Web, for which you happen to have the .aux file, write: <blockquote> @@ -63,7 +63,7 @@ have the .aux file, write: </pre> </blockquote><p> -Heiko Oberdiek’s experimental <i>zref</i> bundle includes a +Heiko Oberdiek’s experimental <i>zref</i> bundle includes a hyper-crossreferencing mechanism using its <i>zref-xr</i> module. Usage is closely modelled on <i>xr</i> and <i>xr-hyper</i>; a trivial example (from a <i>comp.text.tex</i> posting) is @@ -76,13 +76,13 @@ trivial example (from a <i>comp.text.tex</i> posting) is </pre> </blockquote><p> The module provides all the facilities of the older packages, and can -deal both with “traditional” LaTeX labels and with -<i>zref</i>’s style of labels. +deal both with “traditional” LaTeX labels and with +<i>zref</i>’s style of labels. <dl> -<dt><tt><i>xr.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) -<dt><tt><i>xr-hyper.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) +<dt><tt><i>xr.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/xr.html">catalogue entry</a> +<dt><tt><i>xr-hyper.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/xr-hyper.html">catalogue entry</a> <dt><tt><i>zref bundle</i></tt><dd>Distributed as part of - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/zref.html">catalogue entry</a> </dl> <p/> <p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html index 1735b058661..80efde5114e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-extsizes.html @@ -1,25 +1,25 @@ <head> <title>UK TeX FAQ -- question label extsizes</title> </head><body> -<h3>Other “document font” sizes?</h3> -<p/>The LaTeX standard classes have a concept of a (base) “document -font” size; this size is the basis on which other font sizes (those +<h3>Other “document font” sizes?</h3> +<p/>The LaTeX standard classes have a concept of a (base) “document +font” size; this size is the basis on which other font sizes (those from <code>\</code><code>tiny</code> to <code>\</code><code>Huge</code>) are determined. The classes are designed -on the assumption that they won’t be used with sizes other than the -set that LaTeX offers by default (10–12pt), but people regularly +on the assumption that they won’t be used with sizes other than the +set that LaTeX offers by default (10–12pt), but people regularly find they need other sizes. The proper response to such a requirement -is to produce a new design for the document, but many people don’t +is to produce a new design for the document, but many people don’t fancy doing that. <p/>A simple solution is to use the <i>extsizes</i> bundle. This -bundle offers “extended” versions of the article, report, book and +bundle offers “extended” versions of the article, report, book and letter classes, at sizes of 8, 9, 14, 17 and 20pt as well as the -standard 10–12pt. Since little has been done to these classes other +standard 10–12pt. Since little has been done to these classes other than to adjust font sizes and things directly related to them, they -may not be optimal — but they’re certainly practical. +may not be optimal — but they’re certainly practical. <p/>More satisfactory are the <em>KOMA-script</em> classes, which are designed to work properly with the class option files that come with <i>extsizes</i>, and the <i>memoir</i> class that has its own -options for document font sizes 9pt–12pt, 14pt, 17pt, 20pt, 25pt, +options for document font sizes 9pt–12pt, 14pt, 17pt, 20pt, 25pt, 30pt, 36pt, 48pt and 60pt. <dl> <dt><tt><i>extsizes bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extsizes.zip">macros/latex/contrib/extsizes</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extsizes/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html index 40c14ef49c7..6bd160344b6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fancyhdr.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label fancyhdr</title> </head><body> <h3>Alternative head- and footlines in LaTeX</h3> -<p/>The standard LaTeX document classes define a small set of ‘page -styles’ which specify head- and footlines for your document (though +<p/>The standard LaTeX document classes define a small set of ‘page +styles’ which specify head- and footlines for your document (though they can be used for other purposes, too). The standard set is very limited, but LaTeX is capable of much more. The internal LaTeX coding needed to change page styles is not particularly -challenging, but there’s no need — there are packages that provide +challenging, but there’s no need — there are packages that provide useful abstractions that match the way we typically think about these things. <p/>The <i>fancyhdr</i> package provides diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html index d9c5f11a54c..22eae0bc774 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-figurehere.html @@ -22,7 +22,7 @@ option that prevents floating: </blockquote><p> As the example shows, these <code>[H]</code> figures (and correspondingly, tables) offer all you need to cross-reference as well as typeset. -<p/>However, you don’t actually <em>have</em> to use <i>float</i> (or +<p/>However, you don’t actually <em>have</em> to use <i>float</i> (or <i>here</i>) since it is, in fact, doing rather little for you. You can place your figure as you please, with a sequence like <blockquote> @@ -40,16 +40,16 @@ simple-minded package <i>capt-of</i> or from the highly sophisticated <i>caption</i> package. <p/>Using either method, you have to deal with the possibility of the figure or table being too large for the page. (Floating objects will -float away in this circumstance; “doing it by hand”, like this, you +float away in this circumstance; “doing it by hand”, like this, you take upon yourself the responsibility for avoiding -‘<i>Overfull <code>\</code><code>vbox</code></i>’ errors. -<p/>A further problem is the possibility that such “fixed floats” will -overtake “real floats”, so that the numbers of figures will be out +‘<i>Overfull <code>\</code><code>vbox</code></i>’ errors. +<p/>A further problem is the possibility that such “fixed floats” will +overtake “real floats”, so that the numbers of figures will be out of order: figure 6 could be on page 12, while figure 5 had floated to -page 13. It’s best, therefore, either to stay with floating figures +page 13. It’s best, therefore, either to stay with floating figures throughout a document, or to use fixed figures throughout. -<p/>If it’s really impossible to follow that counsel of perfection, you -can use the <i>perpage</i> package’s command <code>\</code><code>MakeSorted</code> +<p/>If it’s really impossible to follow that counsel of perfection, you +can use the <i>perpage</i> package’s command <code>\</code><code>MakeSorted</code> command: <blockquote> <pre> @@ -67,7 +67,7 @@ and the sequence of float numbers is all correct. <dt><tt><i>caption.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/caption.zip">macros/latex/contrib/caption</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/caption/">browse the directory</a>) <dt><tt><i>float.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse the directory</a>) <dt><tt><i>here.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/here.zip">macros/latex/contrib/here</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/here/">browse the directory</a>) -<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>) +<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/perpage.html">catalogue entry</a> </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html index 447d2c60315..d62c51c2451 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html @@ -1,26 +1,26 @@ <head> <title>UK TeX FAQ -- question label filename</title> </head><body> -<h3>What’s the name of this file</h3> +<h3>What’s the name of this file</h3> <p/>One might want this so as to automatically generate a page header or -footer recording what file is being processed. It’s not easy… +footer recording what file is being processed. It’s not easy… <p/>TeX retains what it considers the name of the <em>job</em>, only, in the primitive <code>\</code><code>jobname</code>; this is the name of the file first handed to TeX, stripped of its directory name and of any extension -(such as <code>.tex</code>). If no file was passed (i.e., you’re using +(such as <code>.tex</code>). If no file was passed (i.e., you’re using TeX interactively), <code>\</code><code>jobname</code> has the value <code>texput</code> -(the name that’s given to <code>.log</code> files in this case). +(the name that’s given to <code>.log</code> files in this case). <p/>This is fine, for the case of a small document, held in a single file; most significant documents will be held in a bunch of files, and TeX makes no attempt to keep track of files input to the -<em>job</em>. So the user has to keep track, himself — the only way +<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. <p/>In the case of LaTeX, the input commands have pretty regular syntax, and the simplest <a href="FAQ-patch.html">patching techniques</a> can be used on them. -<p/>If you’re not inputting things from a file that’s already been input, +<p/>If you’re not inputting things from a file that’s already been input, the job is almost trivial: <blockquote> <pre> @@ -38,7 +38,7 @@ input: it starts pointing at the base file of your document <code>\</code><code>input{</code><em>file</em><code>}</code>. <p/>Most ordinary users will quickly become irritated with the simplicity of of the <code>\</code><code>ThisFile</code> mechanism above. The following code is more -cunning: it maintains details of the files you’ve ‘come through’ to +cunning: it maintains details of the files you’ve ‘come through’ to get to where you are, and it restores <code>\</code><code>ThisFile</code> to what the previous file was before returning. <blockquote> @@ -74,10 +74,10 @@ To do the same for <code>\</code><code>include</code>, we need the simple additi </blockquote><p> Both examples of patching <code>\</code><code>input</code> assume you always use LaTeX syntax, i.e., always use braces around the argument. -<p/>The <i>FiNK</i> (“File Name Keeper”) package provides a +<p/>The <i>FiNK</i> (“File Name Keeper”) package provides a regular means of keeping track of the current file name (with its extension), in a macro <code>\</code><code>finkfile</code>. If you need the unadorned file -name (without its ‘<code>.tex</code>’), use the commands: +name (without its ‘<code>.tex</code>’), use the commands: <blockquote> <pre> \def\striptexext#1.tex{#1} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html index abd9bdaa00c..004943fadd1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filesused.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label filesused</title> </head><body> <h3>All the files used by this document</h3> -<p/>When you’re sharing a document with someone else (perhaps as part of a -co-development cycle) it’s as well to arrange that both correspondents +<p/>When you’re sharing a document with someone else (perhaps as part of a +co-development cycle) it’s as well to arrange that both correspondents have the same set of auxiliary files, as well as the document in question. Your correspondent obviously needs the same set of files (if you use the <i>url</i> package, she has to have <i>url</i> @@ -16,14 +16,20 @@ places a list of the files used and their version numbers in the log file. If you extract that list and transmit it with your file, it can be used as a check-list in case that problems arise. <p/>Note that <code>\</code><code>listfiles</code> only registers things that are input by the -“standard” LaTeX mechanisms (<code>\</code><code>documentclass</code>, <code>\</code><code>usepackage</code>, -<code>\</code><code>input</code>, <code>\</code><code>include</code>, <code>\</code><code>includegraphics</code> and so on). But if you -use TeX primitive syntax, as in +“standard” LaTeX mechanisms (<code>\</code><code>documentclass</code>, <code>\</code><code>usepackage</code>, +<code>\</code><code>include</code>, <code>\</code><code>includegraphics</code> and so on). +The <code>\</code><code>input</code> command, as modified by LaTeX and used, with +LaTeX syntax, as: +<pre> + \input{mymacros} +</pre> +records file details for <i>mymacros.tex</i>, but if you use TeX +primitive syntax for <code>\</code><code>input</code>, as: <pre> \input mymacros </pre> -<i>mymacros.tex</i> <em>won’t</em> be listed by <code>\</code><code>listfiles</code>, since -you’ve bypassed the mechanism that records its use. +<i>mymacros.tex</i> <em>won’t</em> be recorded, and so won’t listed by +<code>\</code><code>listfiles</code> — you’ve bypassed the mechanism that records its use. <p/>The <i>snapshot</i> package helps the owner of a LaTeX document obtain a list of the external dependencies of the document, in a form that can be embedded at the top of the document. The intended use of @@ -32,8 +38,8 @@ has application in document exchange situations too. <p/>The <i>bundledoc</i> system uses the <i>snapshot</i> to produce an archive (e.g., <code>.tar.gz</code> or <code>.zip</code>) of the files needed by your document; it comes with configuration files for use with -<i>teTeX</i> and <i>MiKTeX</i>. It’s plainly useful when -you’re sending the first copy of a document. +<i>teTeX</i> and <i>MiKTeX</i>. It’s plainly useful when +you’re sending the first copy of a document. <dl> <dt><tt><i>bundledoc</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/bundledoc.zip">support/bundledoc</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/bundledoc/">browse the directory</a>) <dt><tt><i>snapshot.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/snapshot.zip">macros/latex/contrib/snapshot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/snapshot/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html index e540c67a70a..bab8cd91135 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfiles.html @@ -4,49 +4,49 @@ <h3>Finding (La)TeX files</h3> <p/>Modern TeX distributions contain a huge array of support files of various sorts, but sooner or later most people need to find something -that’s not in their present system (if nothing else, because they’ve +that’s not in their present system (if nothing else, because they’ve heard that something has been updated). <p/>But how to find the files? <p/>Some sources, such as these FAQ answers, provide links to -files: so if you’ve learnt about a package here, you should be able to +files: so if you’ve learnt about a package here, you should be able to retrieve it without too much fuss. <p/>Otherwise, the CTAN sites provide searching facilities, via the web. The simplest search, locating files by name, is to be found on the Dante CTAN at <a href="http://dante.ctan.org/search.html">http://dante.ctan.org/search.html</a>; the script scans a -list of files (<i>FILES.byname</i> — see below) and returns a list +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.html">USA</a> CTANs offer a search page that provides <ul> -<li> a file-name search similar to the Dante machine’s (above); +<li> a file-name search similar to the Dante machine’s (above); <li> a keyword search of the archive catalogue (see below): this is a pretty powerful tool: the results include links to the catalogue - “short descriptions”, so you can assure yourself that the package - you’ve found is the one you want; and + “short descriptions”, so you can assure yourself that the package + you’ve found is the one you want; and <li> a search form that allows you to use <i>Google</i> to search CTAN. </ul> -<p/>An alternative way to scan the catalogue is to use the catalogue’s +<p/>An alternative way to scan the catalogue is to use the catalogue’s -<a href="http://mirrors.ctan.org/help/Catalogue/bytopic.html">“by topic” index</a>; +<a href="http://mirrors.ctan.org/help/Catalogue/bytopic.html">“by topic” index</a>; this lists a series of topics, and (La)TeX projects that are worth -considering if you’re working on matters related to the topic. +considering if you’re working on matters related to the topic. <p/>In fact, <i>Google</i>, and other search engines, can be useful tools. Enter your search keywords, and you may pick up a package that -the author hasn’t bothered to submit to CTAN. If you’re using +the author hasn’t bothered to submit to CTAN. If you’re using <i>Google</i>, you can restrict your search to CTAN by entering <blockquote> <code>site:ctan.org tex-archive <<i>search term(s)</i>></code> </blockquote><p> -in <i>Google</i>’s “search box”. You can also enforce the -restriction using <i>Google</i>’s “advanced search” mechanism; +in <i>Google</i>’s “search box”. You can also enforce the +restriction using <i>Google</i>’s “advanced search” mechanism; other search engines (presumably) have similar facilities. <p/>Many people avoid the need to go over the network at all, for their -searches, by downloading the file list that the archives’ web +searches, by downloading the file list that the archives’ web file searches use. This file, <i>FILES.byname</i>, presents a unified listing of the archive (omitting directory names and cross-links). Its companion <i>FILES.last07days</i> is also useful, to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html index 4865441c532..05bd75995a2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findfont.html @@ -16,7 +16,7 @@ or other, and a large proportion is distributed under commercial terms. However, once you have acquired such a font, converting it to a form usable by your (La)TeX distribution is not (in principle) a serious problem. -<p/>The answer “<a href="FAQ-psfchoice.html">choice of scalable fonts</a>” discusses +<p/>The answer “<a href="FAQ-psfchoice.html">choice of scalable fonts</a>” discusses fonts that are configured for general (both textual and mathematical) use with (La)TeX. The list of such fonts is sufficiently short that they <em>can</em> all be discussed in one answer here. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html index c381aed0824..48df181b188 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-findwidth.html @@ -21,7 +21,7 @@ mode. \settowidth{\gnat}{\textbf{small}} </pre> </blockquote><p> -This sets the value of the length command <code>\gnat</code> to the width of “small” +This sets the value of the length command <code>\gnat</code> to the width of “small” in bold-face text. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html index d62c6f8a162..1e3e9849c38 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixnam.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label fixnam</title> </head><body> -<h3>How to change LaTeX’s “fixed names”</h3> +<h3>How to change LaTeX’s “fixed names”</h3> <p/>LaTeX document classes define several typographic operations that -need ‘canned text’ (text not supplied by the user). In the earliest +need ‘canned text’ (text not supplied by the user). In the earliest days of LaTeX 2.09 these bits of text were built in to the body of -LaTeX’s macros and were rather difficult to change, but “fixed -name” macros were introduced for the benefit of those wishing to use +LaTeX’s macros and were rather difficult to change, but “fixed +name” macros were introduced for the benefit of those wishing to use LaTeX in languages other than English. For example, the special section produced by the <code>\</code><code>tableofcontents</code> command is always called <code>\</code><code>contentsname</code> (or rather, what @@ -24,7 +24,7 @@ in the preamble of your document, and the job is done. use a different mechanism: be sure to check <a href="FAQ-latexwords.html">changing <i>babel</i> names</a> if -you’re using it.) +you’re using it.) <p/>The names that are defined in the standard LaTeX classes (and the <i>makeidx</i> package) are listed below. Some of the names are only defined in a subset of the classes diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html index 13691993be0..f6093cf7cf3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fixwidtab.html @@ -7,8 +7,8 @@ LaTeX: you can make the gaps between the columns stretch, or you can stretch particular cells in the table. <p/>Basic LaTeX can make the gaps stretch: the <code>tabular*</code> environment takes an extra argument (before the <code>clpr</code> layout one) -which takes a length specification: you can say things like “<code>15cm</code>” -or “<code>\</code><code>columnwidth</code>” here. You must also have an <code>\</code><code>extracolsep</code> +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 <pre> @@ -16,37 +16,37 @@ directive. So, for example, one might have </pre> The <code>\</code><code>extracolsep</code> applies to all inter-column gaps to its right as -well; if you don’t want all gaps stretched, add +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 +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 +“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 -allocates space to each column accordingly. There are “sanity -checks” so that really large entries don’t cause everything else to -collapse into nothingness (there’s a “maximum width” that any column -can exert), and so that tiny entries can’t get smaller than a +examines how long each column would be “naturally” (i.e., on a piece of paper of unlimited width), and +allocates space to each column accordingly. There are “sanity +checks” so that really large entries don’t cause everything else to +collapse into nothingness (there’s a “maximum width” that any column +can exert), and so that tiny entries can’t get smaller than a specified minimum. Of course, all this work means that the package has to typeset each row several times, so things that leave -“side-effects” (for example, a counter used to produce a row-number +“side-effects” (for example, a counter used to produce a row-number somewhere) are inevitably unreliable, and should not even be tried. <p/>The <i>ltxtable</i> package combines the features of the -<i>longtable</i> and <i>tabularx</i> packages. It’s important +<i>longtable</i> and <i>tabularx</i> packages. It’s important to read the documentation, since usage is distinctly odd; the distribution contains no more than a file <i>ltxtable.tex</i>, which you should process using LaTeX. Processing will give you a <i>.sty</i> file as well as the <i>.dvi</i> or <i>.pdf</i> output containing the documentation. <dl> -<dt><tt><i>ltxtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>) -<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>ltxtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/ltxtable.html">catalogue entry</a> +<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/tabularx.html">catalogue entry</a> <dt><tt><i>tabulary.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html index b48b61e4f00..e4b59c8f851 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html @@ -23,6 +23,6 @@ command(s), so the techniques of called into play. <p/>This author has also encountered the error when developing macros that used the LaTeX internal float mechanisms. Most people doing that -sort of thing are expected to be able to work out their own problems… +sort of thing are expected to be able to work out their own problems… <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html index 79c7a8812ec..7143ac976e2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floatpages.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label floatpages</title> </head><body> <h3>Floats on their own on float pages</h3> -<p/>It’s sometimes necessary to force a float to live on a page by itself. -(It’s sometimes even necessary for <em>every</em> float to live on a -page by itself.) When the float fails to ‘set’, and waits for the end +<p/>It’s sometimes necessary to force a float to live on a page by itself. +(It’s sometimes even necessary for <em>every</em> float to live on a +page by itself.) When the float fails to ‘set’, and waits for the end of a chapter or of the document, the natural thing to do is to declare the float as <blockquote> @@ -13,10 +13,10 @@ the float as 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 +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 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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html index 9f29c9791e1..5274a8d1e67 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html @@ -5,33 +5,33 @@ <p/>Tables and figures have a tendency to surprise, by <em>floating</em> away from where they were specified to appear. This is in fact perfectly ordinary document design; any professional typesetting -package will float figures and tables to where they’ll fit without +package will float figures and tables to where they’ll fit without violating the certain typographic rules. Even if you use the -placement specifier <code>h</code> for ‘here’, the figure or table will not be -printed ‘here’ if doing so would break the rules; the rules themselves +placement specifier <code>h</code> for ‘here’, the figure or table will not be +printed ‘here’ if doing so would break the rules; the rules themselves are pretty simple, and are given on page 198, section C.9 of the -LaTeX manual. In the worst case, LaTeX’s rules can cause the +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 +equally well to tables, or to “non-standard” floats defined by the <i>float</i> or other packages). <ul> <li> Do your figures need to float at all? If not, look at the - recommendations for “<a href="FAQ-figurehere.html">non-floating floats</a>” + recommendations for “<a href="FAQ-figurehere.html">non-floating floats</a>” <li> Are the placement parameters on your figures right? The default (<code>tbp</code>) is reasonable, but you can reasonably change it (for - example, to add an <code>h</code>). Whatever you do, <em>don’t</em> - omit the ‘<code>p</code>’: doing so could cause LaTeX to believe that if you - can’t have your figure <em>here</em>, you don’t want it + example, to add an <code>h</code>). Whatever you do, <em>don’t</em> + omit the ‘<code>p</code>’: doing so could cause LaTeX to believe that if you + can’t have your figure <em>here</em>, you don’t want it <em>anywhere</em>. (LaTeX does try hard to avoid being confused in - this way…) -<li> LaTeX’s own float placement parameters could be preventing - placements that seem entirely “reasonable” to you — they’re + this way…) +<li> LaTeX’s own float placement parameters could be preventing + placements that seem entirely “reasonable” to you — they’re notoriously rather conservative. To encourage LaTeX not to move your figure, you need to loosen its demands. (The most important - ones are the ratio of text to float on a given page, but it’s + ones are the ratio of text to float on a given page, but it’s sensible to have a fixed set that changes the whole lot, to meet every eventuality.) <pre> @@ -47,13 +47,13 @@ equally well to tables, or to “non-standard” floats defined by the \setcounter{dbltopnumber}{9} </pre> The meanings of these - parameters are described on pages 199–200, section C.9 of the + parameters are described on pages 199–200, section C.9 of the LaTeX manual. -<li> Are there places in your document where you could ‘naturally’ +<li> Are there places in your document where you could ‘naturally’ put a <code>\</code><code>clearpage</code> command? If so, do: the backlog of floats is cleared after a <code>\</code><code>clearpage</code>. (Note that the <code>\</code><code>chapter</code> command in the standard <i>book</i> and <i>report</i> classes - implicitly executes <code>\</code><code>clearpage</code>, so you can’t float past + implicitly executes <code>\</code><code>clearpage</code>, so you can’t float past the end of a chapter.) <li> Try the <i>placeins</i> package: it defines a <code>\</code><code>FloatBarrier</code> command beyond which floats may not pass. A @@ -69,18 +69,18 @@ equally well to tables, or to “non-standard” floats defined by the of putting <code>\</code><code>clearpage</code> <em>after</em> the current page (where it will clear the backlog, but not cause an ugly gap in your text), but also admits that the package is somewhat fragile. Use it as a last - resort if the other possibilities below don’t help. + resort if the other possibilities below don’t help. <li> If you would actually <em>like</em> great blocks of floats at the end of each of your chapters, try the <i>morefloats</i> package; - this ‘simply’ increases the number of floating inserts that LaTeX + this ‘simply’ increases the number of floating inserts that LaTeX can handle at one time (from 18 to 36). <li> If you actually <em>wanted</em> all your figures to float to the - end (<em>e.g</em>., for submitting a draft copy of a paper), don’t - rely on LaTeX’s mechanism: get the <i>endfloat</i> package to do + end (<em>e.g</em>., for submitting a draft copy of a paper), don’t + rely on LaTeX’s mechanism: get the <i>endfloat</i> package to do the job for you. </ul> <dl> -<dt><tt><i>afterpage.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>afterpage.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/afterpage.html">catalogue entry</a> <dt><tt><i>endfloat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/endfloat.zip">macros/latex/contrib/endfloat</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/endfloat/">browse the directory</a>) <dt><tt><i>flafter.sty</i></tt><dd>Part of the LaTeX distribution <dt><tt><i>float.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html index 4b71a2e8d7e..6c0cc036add 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-flushboth.html @@ -17,19 +17,19 @@ restores flush justification at both margins: \leftskip\z@skip \parindent 1.5em\relax} </pre> -There’s a problem with the setting of <code>\</code><code>parindent</code> in the code: it’s +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 +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 +<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> +<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 +<a href="FAQ-ragright.html">versions of the LaTeX ‘ragged’ commands</a>. The package also provides a <code>justify</code> environment, which permits areas of justified text in a larger area which is ragged. <dl> -<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>) +<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/ragged2e.html">catalogue entry</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html index 409f9348eef..d72ad1ab6a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html @@ -8,7 +8,7 @@ <code>-ms</code> and <code>-man</code> macros, plus most <i>eqn</i> and some <i>tbl</i> preprocessor commands. Anything fancier needs to be done by hand. Two style files are provided. There is also a man page - (which converts very well to LaTeX…). + (which converts very well to LaTeX…). <i>Tr2latex</i> is an enhanced version of the earlier <i>troff-to-latex</i> (which is no longer available). <p/> @@ -22,7 +22,7 @@ <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 + converting Microsoft’s Rich Text Format to TeX. There is also a converter to LaTeX by Erwin Wechtl, called <i>rtf2latex</i>. The latest converter, by Ujwal Sathyam and Scott Prahl, is <i>rtf2latex2e</i> which seems rather good, though development @@ -37,7 +37,7 @@ MS-Word to LaTeX is <i>wd2latex</i>, which runs on MSDOS. <i>Word2</i><em>TeX</em> and <em>TeX</em><i>2Word</i> are shareware translators from - <a href="http://www.chikrii.com/">Chikrii Softlab</a>; users’ reports are + <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 @@ -53,7 +53,7 @@ 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> +<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 @@ -62,12 +62,12 @@ <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 + 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>, +<a href="http://www.tug.org/utilities/texconv/index.html">Wilfried Hennings’ FAQ</a>, which deals specifically with conversions between TeX-based formats and word processor formats, offers much detail as well as tables that allow quick comparison of features. @@ -75,8 +75,8 @@ allow quick comparison of features. a common document format based on SGML, with the ambition that any format could be translated to or from this one. <i>FrameMaker</i> provides -“import filters” to aid translation from alien formats -(presumably including TeX) to <i>FrameMaker</i>’s own. +“import filters” to aid translation from alien formats +(presumably including TeX) to <i>FrameMaker</i>’s own. <dl> <dt><tt><i>excel2latex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/excel2latex.zip">support/excel2latex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/excel2latex/">browse the directory</a>) <dt><tt><i>pcwritex.arc</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/pcwritex.zip">support/pcwritex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/pcwritex/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html index 2fb347f95f3..a6296c0505a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontname.html @@ -1,9 +1,9 @@ <head> <title>UK TeX FAQ -- question label fontname</title> </head><body> -<h3>What is the “Berry naming scheme”?</h3> +<h3>What is the “Berry naming scheme”?</h3> <p/>In the olden days, (La)TeX distributions were limited by the -feebleness of file systems’ ability to represent long names. (The +feebleness of file systems’ ability to represent long names. (The MSDOS file system was a particular bugbear: fortunately any current Microsoft system allows rather more freedom to specify file names. Sadly, the ISO 9660 standard for the structure of CDROMs has a @@ -11,17 +11,17 @@ similar failing, but that too has been modified by various extension mechanisms.) <p/>One area in which this was a particular problem was that of file names for Type 1 fonts. These fonts are distributed by their vendors with -pretty meaningless short names, and there’s a natural ambition to +pretty meaningless short names, and there’s a natural ambition to change the name to something that identifies the font somewhat -precisely. Unfortunately, names such as “BaskervilleMT” are +precisely. Unfortunately, names such as “BaskervilleMT” are already far beyond the abilities of the typical feeble file system, and add the specifier of a font shape or variant, and the difficulties spiral out of control. <p/>Thus arose the Berry naming scheme. <p/>The basis of the scheme is to encode the meanings of the various parts -of the file’s specification in an extremely terse way, so that enough +of the file’s specification in an extremely terse way, so that enough font names can be expressed even in impoverished file name-spaces. The -encoding allocates one letter to the font “foundry”, two to the +encoding allocates one letter to the font “foundry”, two to the typeface name, one to the weight, and so on. The whole scheme is outlined in the <i>fontname</i> distribution, which includes extensive documentation and a set of tables of fonts whose names have diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html index 56142111c83..c9e73dad12d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fonts-pln.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label fonts-pln</title> </head><body> <h3>Using non-standard fonts in Plain TeX</h3> -<p/>Plain TeX (in accordance with its description) doesn’t do anything +<p/>Plain TeX (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. -<p/>To use something other than Knuth’s default, the default mechanism is -to use the <code>\</code><code>font</code> primitive: +<p/>To use something other than Knuth’s default, you can use Knuth’s +mechanism, the <code>\</code><code>font</code> primitive: <blockquote> <pre> \font\foo=nonstdfont @@ -30,12 +30,12 @@ Text set using nonstdfont italic... This is all very elementary stuff, and serves for simple use of fonts. However, there are wrinkles, the most important of which is the matter of <a href="FAQ-whatenc.html">font encodings</a>. Unfortunately, many fonts that -have appeared recently simply don’t come in versions using Knuth’s -eccentric font encodings — but those encodings are built into +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 +“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 @@ -43,18 +43,18 @@ can in principle use the <i>ec-plain</i> bundle, which gives you a version of Plain TeX which you can run in the same way that you run Plain TeX using the original CM fonts, by invoking <i>tex</i>. (<i>Ec-plain</i> also extends the EC fonts, -for reasons which aren’t immediately clear, but which might cause -problems if you’re hoping to use Type 1 versions of the 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.) <p/>The <i>font_selection</i> package provides a sort of halfway house: it provides font face and size, but not family selection. This gives you considerable freedom, but leaves you stuck with the original -CM fonts. It’s a compact solution, within its restrictions. +CM fonts. It’s a compact solution, within its restrictions. <p/>Other Plain TeX approaches to the problem (packages <i>plnfss</i>, <i>fontch</i> and <i>ofs</i>) break out of the Plain TeX model, towards the sort of font selection provided by -ConTeXt and LaTeX — font selection that allows you to change +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 OT1. +provision for using encodings other than Knuth’s OT1. <p/><i>Plnfss</i> has a rather basic set of font family details; however, it is capable of using font description (<code>.fd</code>) files created for LaTeX. (This is useful, since most modern mechanisms @@ -79,22 +79,22 @@ allowing you the dubious pleasure of using fonts such as the document preparation environment, like <a href="FAQ-eplain.html">Eplain</a>. One of its components is a font selection scheme, <i>pdcfsel</i>, which is rather simple but adequately powerful for many uses. The package -doesn’t preload fonts: the user is required to declare the fonts the +doesn’t preload fonts: the user is required to declare the fonts the document is going to use, and the package provides commands to select -fonts as they’re needed. The distribution includes a configuration to -use Adobe ‘standard’ fonts for typesetting text. (Eplain itself +fonts as they’re needed. The distribution includes a configuration to +use Adobe ‘standard’ fonts for typesetting text. (Eplain itself seems not to offer a font selection scheme.) <p/>The <i>font-change</i> collection takes a rather different -approach — it supplies what are (in effect) a series of templates +approach — it supplies what are (in effect) a series of templates that may be included in a document to change font usage. The -package’s documentation shows the effect rather well. +package’s documentation shows the effect rather well. <p/>Simply to change font <em>size</em> in a document (i.e., not changing the default font itself), may be done using the rather straightforward <i>varisize</i>, which offers font sizes ranging from 7 points to 20 points (nominal sizes, all). Font size commands are generated when any of the package files is loaded, so the <i>11pt.tex</i> defines a -command <code>\</code><code>elevenpoint</code>; each of the files ensures there’s a “way -back”, by defining a <code>\</code><code>tenpoint</code> command. +command <code>\</code><code>elevenpoint</code>; each of the files ensures there’s a “way +back”, by defining a <code>\</code><code>tenpoint</code> command. <dl> <dt><tt><i>ec-plain</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/ec-plain.zip">macros/ec-plain</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/ec-plain/">browse the directory</a>) <dt><tt><i>font-change</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/font-change.zip">macros/plain/contrib/font-change</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/font-change/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html index 6488fa57f3d..269010b7c22 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontsize.html @@ -12,7 +12,7 @@ significantly applies to the default (Computer Modern) and the Cork-encoded (T1) EC fonts, but it is widely considered to be anomalous, nowadays. In recognition of this problem, there is a package <i>fix-cm</i> which will allow you to use the fonts, within -LaTeX, at any size you choose. If you’re not using scaleable +LaTeX, at any size you choose. If you’re not using scaleable versions of the fonts, most modern distributions will just generate an appropriate bitmap for you. <p/>So, suppose you want to use Computer Modern Roman at 30 points, you @@ -41,7 +41,7 @@ December 2003 edition of LaTeX; if you have an older distribution, the packages <i>type1cm</i> (for CM fonts) and <i>type1ec</i> (for EC fonts) are available. <dl> -<dt><tt><i>fix-cm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base.zip">macros/latex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse the directory</a>) (an unpacked +<dt><tt><i>fix-cm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base.zip">macros/latex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/fix-cm.html">catalogue entry</a> (an unpacked version is available at <a href="http://www.tex.ac.uk/tex-archive/macros/latex/unpacked/fix-cm.sty">macros/latex/unpacked/fix-cm.sty</a>) <dt><tt><i>type1cm.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm.zip">macros/latex/contrib/type1cm</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm/">browse the directory</a>) <dt><tt><i>type1ec.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/type1ec.sty">fonts/ps-type1/cm-super/type1ec.sty</a> (the package is actually part of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html index a370c96e2a1..2e7943739b6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fontunavail.html @@ -1,8 +1,8 @@ <head> <title>UK TeX FAQ -- question label fontunavail</title> </head><body> -<h3>Warning: “Font shape … not available”</h3> -<p/>LaTeX’s font selection scheme maintains tables of the font families +<h3>Warning: “Font shape … not available”</h3> +<p/>LaTeX’s font selection scheme maintains tables of the font families it has been told about. These tables list the font families that LaTeX knows about, and the shapes and series in which those font families are available. In addition, in some cases, the tables list @@ -10,12 +10,12 @@ the sizes at which LaTeX is willing to load fonts from the family. <p/>When you specify a font, using one of the LaTeX font selection commands, LaTeX looks for the font (that is, a font that matches the encoding, family, shape, series and size that you want) in its -tables. If the font isn’t there at the size you want, you will see a +tables. If the font isn’t there at the size you want, you will see a message like: <pre> -LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <11.5> not available -(Font) size <12> substituted on input line ... +LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <11.5> not available +(Font) size <12> substituted on input line ... </pre> There will also be a warning like: @@ -24,8 +24,8 @@ LaTeX Font Warning: Size substitutions with differences (Font) up to 0.5pt have occurred. </pre> after LaTeX has encountered <code>\</code><code>end{document}</code>. -<p/>The message tells you that you’ve chosen a font size that is not in -LaTeX’s list of “allowed” sizes for this font; LaTeX has +<p/>The message tells you that you’ve chosen a font size that is not in +LaTeX’s list of “allowed” sizes for this font; LaTeX has chosen the nearest font size it knows is allowed. In fact, you can tell LaTeX to allow <em>any</em> size: the restrictions come from the days when only bitmap fonts were available, and they have never @@ -35,7 +35,7 @@ available in scaleable (Adobe Type 1) form. If your installation uses scaleable versions of the Computer Modern or European Computer Modern (EC) fonts, you can tell LaTeX to remove the restrictions; use the <i>type1cm</i> or <i>type1ec</i> package as appropriate. -<p/>If the combination of font shape and series isn’t available, LaTeX +<p/>If the combination of font shape and series isn’t available, LaTeX will usually have been told of a fall-back combination that may be used, and will select that: @@ -43,16 +43,16 @@ used, and will select that: LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined (Font) using `OT1/cmr/bx/n' instead on input line 0. </pre> -<p/>Substitutions may also be “silent”; in this case, there is no more -than an “information” message in the log file. For example, if you +<p/>Substitutions may also be “silent”; in this case, there is no more +than an “information” message in the log file. For example, if you specify an encoding for which there is no version in the current font -family, the ‘default family for the encoding’ is selected. This +family, the ‘default family for the encoding’ is selected. This happens, for example, if you use command <code>\</code><code>textbullet</code>, which is normally taken from the maths symbols font, which is in <code>OMS</code> encoding. My test log contained: <pre> -LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available +LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available (Font) Font shape `OMS/cmsy/m/n' tried instead on input line ... </pre> <p/>In summary, these messages are not so much error messages, as diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html index 34d132fed9a..e4b41f568ca 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footintab.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label footintab</title> </head><body> <h3>Footnotes in tables</h3> -<p/>The standard LaTeX <code>\</code><code>footnote</code> command doesn’t work in tables; -the table traps the footnotes and they can’t escape to the bottom of +<p/>The standard LaTeX <code>\</code><code>footnote</code> command doesn’t work in tables; +the table traps the footnotes and they can’t escape to the bottom of the page. As a result, you get footnote marks in the table, and nothing else. <p/>This accords with common typographic advice: footnotes and tables are reckoned not to mix. -<p/>The solution, if you accept the advice, is to use “table notes”. +<p/>The solution, if you accept the advice, is to use “table notes”. The package <i>threeparttable</i> provides table notes, and <i>threeparttablex</i> additionally supports them in <code>longtable</code>s. <i>Threeparttable</i> works happily in @@ -17,23 +17,23 @@ ordinary text, or within a <code>table</code> float. <i>threeparttable</i>, and also uses the ideas of the <i>booktabs</i> package. The <code>\</code><code>ctable</code> command does the complete job of setting the table, placing the caption, and defining the -notes. The “table” may consist of diagrams, and a parameter in -<code>\</code><code>ctable</code>’s optional argument makes the float that is created a -“figure” rather than a “table”. -<p/>If you really want “real” footnotes in tables, despite the expert +notes. The “table” may consist of diagrams, and a parameter in +<code>\</code><code>ctable</code>’s optional argument makes the float that is created a +“figure” rather than a “table”. +<p/>If you really want “real” footnotes in tables, despite the expert advice, you can: <ul> <li> Use <code>\</code><code>footnotemark</code> to position the little marker appropriately, and then put in <code>\</code><code>footnotetext</code> commands to fill in - the text once you’ve closed the <code>tabular</code> environment. - This is described in Lamport’s book, but it gets messy if there’s + the text once you’ve closed the <code>tabular</code> environment. + This is described in Lamport’s book, but it gets messy if there’s more than one footnote. <li> Stick the table in a <code>minipage</code>. Footnotes in the - table then “work”, in the <code>minipage</code>’s style, with no + table then “work”, in the <code>minipage</code>’s style, with no extra effort. (This is, in effect, somewhat like table notes, but - the typeset appearance isn’t designed for the job.) + the typeset appearance isn’t designed for the job.) <li> Use <i>tabularx</i> or <i>longtable</i> from the LaTeX - tools distribution; they’re noticeably less efficient than the + tools distribution; they’re noticeably less efficient than the standard <code>tabular</code> environment, but they do allow footnotes. <li> Use <i>footnote</i>, which provides an @@ -47,20 +47,20 @@ advice, you can: <li> Use <i>mdwtab</i> from the same bundle; it will handle footnotes as you might expect, and has other facilities to increase the beauty of your tables. Unfortunately, it may be incompatible - with other table-related packages, though not those in the standard ‘tools’ + with other table-related packages, though not those in the standard ‘tools’ bundle. </ul> All the techniques listed will work, to some extent, whether in a float or -in ordinary text. The author of this FAQ answer doesn’t actually -recommend any of them, believing that table notes are the way to go… +in ordinary text. The author of this FAQ answer doesn’t actually +recommend any of them, believing that table notes are the way to go… <dl> <dt><tt><i>ctable.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ctable.zip">macros/latex/contrib/ctable</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ctable/">browse the directory</a>) -<dt><tt><i>footnote.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) -<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) -<dt><tt><i>mdwtab.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) -<dt><tt><i>threeparttable.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a> +<dt><tt><i>footnote.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/footnote.html">catalogue entry</a> +<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/longtable.html">catalogue entry</a> +<dt><tt><i>mdwtab.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mdwtab.html">catalogue entry</a> +<dt><tt><i>threeparttable.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttable.zip">macros/latex/contrib/threeparttable</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttable/">browse the directory</a>) <dt><tt><i>threeparttablex.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttablex.zip">macros/latex/contrib/threeparttablex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttablex/">browse the directory</a>) -<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/tabularx.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html index acb4a5c373f..a3bd7891d97 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-footnpp.html @@ -1,15 +1,15 @@ <head> <title>UK TeX FAQ -- question label footnpp</title> </head><body> -<h3>Footnotes numbered “per page”</h3> +<h3>Footnotes numbered “per page”</h3> <p/>The obvious solution is to make the footnote number reset whenever the page number is stepped, using the <a href="FAQ-addtoreset.html">LaTeX internal mechanism</a>. Sadly, the place in the document where the page number is stepped is unpredictable, not -(“tidily”) at the end of the printed page; so changing the footnote -number only ever works by ‘luck’. +(“tidily”) at the end of the printed page; so changing the footnote +number only ever works by ‘luck’. <p/>As a result, resetting footnotes is inevitably a complicated process, -using labels of some sort. It’s nevertheless important, given the +using labels of some sort. It’s nevertheless important, given the common requirement for footnotes marked by symbols (with painfully small symbol sets). There are four packages that manage it, one way or another. @@ -18,30 +18,29 @@ resetting counters per page, so can obviously be used for this task. The interface is pretty simple: <code>\</code><code>MakePerPage{footnote}</code> will do the job. If you want to restart the counter at something other than 1 (for example to avoid something in the LaTeX footnote symbol -list), you can use: <code>\</code><code>MakePerPage[2]{footnote}</code>. It’s a +list), you can use: <code>\</code><code>MakePerPage[2]{footnote}</code>. It’s a first-rate package, small and efficient. <p/>The <i>zref</i> package provides the same facilities with its <code>perpage</code> module, which defines a command <code>\</code><code>zmakeperpage</code> whose syntax is identical to that of <i>perpage</i>, above. You can load the module by <code>\</code><code>usepackage[perpage]{zref}</code> (or as -<code>\</code><code>usepackage{zref-perpage}</code>, if your needs so require — -look at <i>zref</i>’s documentation for details). +<code>\</code><code>usepackage{zref-perpage}</code>, if your needs so require — +look at <i>zref</i>’s documentation for details). <p/>The <i>footmisc</i> package provides a variety of means of controlling footnote appearance, among them a package option -<code>perpage</code> that adjusts the numbering per page; if you’re +<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.) +nothing else). With the competition from <i>perpage</i>, it’s +probably not particularly useful any more. <dl> <dt><tt><i>footmisc.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse the directory</a>) <dt><tt><i>footnpag.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footnpag.zip">macros/latex/contrib/footnpag</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footnpag/">browse the directory</a>) -<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>) -<dt><tt><i>zref.sty</i></tt><dd>Distributed as a collection member in <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) -<dt><tt><i>zref-perpage.sty</i></tt><dd>Distributed as a collection member in - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/perpage.html">catalogue entry</a> +<dt><tt><i>zref.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/zref.html">catalogue entry</a> +<dt><tt><i>zref-perpage.sty</i></tt><dd>Distributed as part of <i>zref</i> in + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/zref.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html index 46463ed2b18..e2bfa9c2ecc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formatstymy.html @@ -1,8 +1,8 @@ <head> <title>UK TeX FAQ -- question label formatstymy</title> </head><body> -<h3>“Fatal format file error; I’m stymied”</h3> -<p/>(La)TeX applications often fail with this error when you’ve been +<h3>“Fatal format file error; I’m stymied”</h3> +<p/>(La)TeX applications often fail with this error when you’ve been playing with the configuration, or have just installed a new version. <p/>The format file contains the macros that define the system you want to use: anything from the simplest (Plain TeX) all the way to the most @@ -12,13 +12,13 @@ issue, TeX knows which format you want. <pre> Fatal format file error; I'm stymied </pre> -means that TeX itself can’t understand the format you want. +means that TeX itself can’t understand the format you want. Obviously, this could happen if the format file had got corrupted, but -it usually doesn’t. The commonest cause of the message, is that a new +it usually doesn’t. The commonest cause of the message, is that a new binary has been installed in the system: no two TeX binaries on the same machine can -understand each other’s formats. So the new version of TeX you -have just installed, won’t understand the format generated by the one +understand each other’s formats. So the new version of TeX you +have just installed, won’t understand the format generated by the one you installed last year. <p/>Resolve the problem by regenerating the format; of course, this depends on which system you are using. @@ -29,12 +29,12 @@ depends on which system you are using. </pre> or <pre> - fmtutil --byfmt=<format name> + fmtutil --byfmt=<format name> </pre> to build only the format that you are interested in. -<li> On a MiKTeX system, click <code>Start</code>-> -<code>Programs</code>-> -<code>MiKTeX <em>version</em></code>-> +<li> On a MiKTeX system, click <code>Start</code>-> +<code>Programs</code>-> +<code>MiKTeX <em>version</em></code>-> <code>MiKTeX Options</code>, and in the options window, click <code>Update now</code>. </ul> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html index 04a06527bbc..ec9a4bc99e2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-formbiblabel.html @@ -12,14 +12,14 @@ while many documents need something like: 1. Doe, Joe et al. Some journal. 2004.<br> 2. Doe, Jane et al. Some journal. 2003. </blockquote><p> -<p/>This sort of change may be achieved by many of the “general” -citation packages; for example, in <i>natbib</i>, it’s as simple as: +<p/>This sort of change may be achieved by many of the “general” +citation packages; for example, in <i>natbib</i>, it’s as simple as: <blockquote> <pre> \renewcommand{\bibnumfmt}[1]{#1.} </pre> </blockquote><p> -but if you’re not using such a package, the following internal +but if you’re not using such a package, the following internal LaTeX commands, in the preamble of your document, will do the job: <blockquote> <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html index 44686d0708a..28bd3ce4f04 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftncapt.html @@ -21,8 +21,8 @@ were thinking of. <p/>If you <em>are</em> going to proceed: <ul> <li> use an optional argument in your <code>\</code><code>caption</code> command, that - doesn’t have the footnote in it; this prevents the footnote - appearing in the “List of …”, and + doesn’t have the footnote in it; this prevents the footnote + appearing in the “List of …”, and <li> put your whole float in a <code>minipage</code> so as to keep the footnotes with the float. </ul> @@ -40,19 +40,19 @@ so we have: </blockquote><p> However, <em>as well as</em> all of the above, one <em>also</em> has to deal with the tendency of the <code>\</code><code>caption</code> command to produce the -footnote’s text twice. For this last problem, there is no tidy +footnote’s text twice. For this last problem, there is no tidy solution this author is aware of. -<p/>If you’re suffering the problem, a well-constructed <code>\</code><code>caption</code> +<p/>If you’re suffering the problem, a well-constructed <code>\</code><code>caption</code> command in a <code>minipage</code> environment within a float (as in the example above) can produce <em>two</em> copies of the footnote -body “blah”. (In fact, the effect only occurs with captions that are -long enough to require two lines to be typeset, and so wouldn’t appear +body “blah”. (In fact, the effect only occurs with captions that are +long enough to require two lines to be typeset, and so wouldn’t appear with such a short caption as that in the example above.) <p/>The documentation of the <i>ccaption</i> package describes a really rather awful work-around for this problem. <dl> <dt><tt><i>ccaption.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse the directory</a>) -<dt><tt><i>threeparttable.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a> +<dt><tt><i>threeparttable.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttable.zip">macros/latex/contrib/threeparttable</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/threeparttable/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html index 819bdfc15d9..8b8bbfe54fc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ftnsect.html @@ -3,23 +3,23 @@ </head><body> <h3>Footnotes in LaTeX section headings</h3> <p/>The <code>\</code><code>footnote</code> command is fragile, so that simply placing the -command in <code>\</code><code>section</code>’s arguments isn’t satisfactory. Using -<code>\</code><code>protect</code><code>\</code><code>footnote</code> isn’t a good idea either: the arguments of a +command in <code>\</code><code>section</code>’s arguments isn’t satisfactory. Using +<code>\</code><code>protect</code><code>\</code><code>footnote</code> isn’t a good idea either: the arguments of a section command are used in the table of contents and (more dangerously) potentially also in page headers. While footnotes will -work in the table of contents, it’s generally not thought a “good -thing” to have them there; in the page header, footnotes will simply -fail. Whatever the desirability of the matter, there’s no mechanism +work in the table of contents, it’s generally not thought a “good +thing” to have them there; in the page header, footnotes will simply +fail. Whatever the desirability of the matter, there’s no mechanism to suppress the footnote in the page header while allowing it in the table of contents, so the footnote may only appear in the section heading itself. <p/>To suppress the footnote in headings and table of contents: <ul> -<li> Take advantage of the fact that the mandatory argument doesn’t - ‘move’ if the optional argument is present: +<li> Take advantage of the fact that the mandatory argument doesn’t + ‘move’ if the optional argument is present: <p/> <code>\</code><code>section[title]</code> <code>{title</code><code>\</code><code>footnote{title ftnt}</code><code>}</code> <li> Use the <i>footmisc</i> package, with package option - <code>stable</code> — this modifies footnotes so that they softly and + <code>stable</code> — this modifies footnotes so that they softly and silently vanish away if used in a moving argument. With this, you simply need: <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html index 3c65b2248d0..9428194465b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html @@ -3,31 +3,31 @@ </head><body> <h3>Fonts go fuzzy when you switch to T1</h3> <!-- crippled blurry --> -<p/>You’ve been having problems with hyphenation, and someone has -suggested that you should use “<code>\</code><code>usepackage[T1]{fontenc}</code>” +<p/>You’ve been having problems with hyphenation, and someone has +suggested that you should use “<code>\</code><code>usepackage[T1]{fontenc}</code>” to help sort them out. Suddenly you find that your final PDF has become fuzzy. The problem may arise whether you are using PostScript output and then distilling it, or you are using PDFTeX for the whole job. <p/>In fact, this is the same problem as most others about the -<a href="FAQ-dvips-pdf.html">quality of PDF</a>: you’ve abandoned +<a href="FAQ-dvips-pdf.html">quality of PDF</a>: you’ve abandoned your previous setup using Type 1 versions of the CM fonts, and <i>dvips</i> has inserted Type 3 versions of the EC fonts into your document output. (See -“<a href="FAQ-adobetypen.html">Adobe font types</a> +“<a href="FAQ-adobetypen.html">Adobe font types</a> for details of these font types; also, note that the font <em>encoding</em> T1 has nothing directly to do with the font <em>format</em> Type 1). <p/>However, as noted in -“<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>”, +“<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>”, Type 1 versions of CM-like fonts in T1 (or equivalent) encoding -are now available, both as “real” fonts, and as virtual font sets. +are now available, both as “real” fonts, and as virtual font sets. One solution, therefore, is to use one of these alternatives. <p/>The alternative is to switch font family altogether, to something like <i>Times</i> (as a no-thought default) or one of the many more pleasing Adobe-encoded fonts. The default action of <i>fontinst</i>, when creating metrics for such a font, is to create settings for both OT1 -and T1 encodings, so there’s little change in what goes on (at the +and T1 encodings, so there’s little change in what goes on (at the user level) even if you have switched to T1 encoding when using the fonts. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html index 848da58ff4f..4beba331f60 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html @@ -3,7 +3,7 @@ </head><body> <h3>Fuzzy fonts because <i>Ghostscript</i> too old</h3> <!-- crippled blurry --> -<p/>So you’ve done everything the FAQ has told you that you need, +<p/>So you’ve done everything the FAQ has told you that you need, correct fonts properly installed and appearing in the <i>dvips</i> output, but <em>still</em> you get fuzzy character output after distilling with <i>ghostscript</i>. @@ -14,13 +14,13 @@ script such as <i>ps2pdf</i> (distributed with Though <i>ghostscript</i> was capable of distillation from version 5.50, that version could only produce bitmap Type 3 output of any font other than the fundamental 35 fonts (<i>Times</i>, -<i>Helvetica</i>, etc.). Later versions added ‘complete’ -distillation, but it wasn’t until version 6.50 that one could rely on +<i>Helvetica</i>, etc.). Later versions added ‘complete’ +distillation, but it wasn’t until version 6.50 that one could rely on it for everyday work. <p/>So, if your PDF output still looks fuzzy in <i>Acrobat</i> <i>Reader</i>, upgrade <i>ghostscript</i>. The new version -should be at least version 6.50, of course, but it’s usually good +should be at least version 6.50, of course, but it’s usually good policy to go to the most recent version (version 8.12 at the time of -writing — 2003). +writing — 2003). <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html index 043e7fb8fb9..cc4c39077ac 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html @@ -4,14 +4,14 @@ <h3>The wrong type of fonts in PDF</h3> <!-- crippled blurry --> <p/>This is far the commonest problem: the symptom is that text in the -document looks “fuzzy”. +document looks “fuzzy”. <p/>Most people use <i>Adobe</i> <i>Acrobat</i> <i>Reader</i> to view their PDF: <i>Reader</i> is distributed free of charge, and is widely available, for all its faults. One of those faults is its failure to deal with bitmap fonts (at least, in all versions earlier than the recently released version 6). -<p/>So we don’t want bitmap fonts in our PostScript: with them, characters show -up in <i>Reader</i>’s display as blurred blobs which are often not +<p/>So we don’t want bitmap fonts in our PostScript: with them, characters show +up in <i>Reader</i>’s display as blurred blobs which are often not recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most TeX systems have <i>dvips</i> configured to use @@ -19,26 +19,26 @@ on the line. Nevertheless, even now, most TeX systems have PDFTeX will use <code>.pk</code> files if it can see no alternative for a font in the document it is processing. <p/>Our remedy is to use -“<a href="FAQ-adobetypen.html">Adobe Type 1</a>” +“<a href="FAQ-adobetypen.html">Adobe Type 1</a>” versions of the fonts we need. Since Adobe are in the business of selling Type 1 fonts, <i>Reader</i> was of course made to deal with them really rather well, from the very beginning. <p/>Of course, if your document uses nothing but fonts that came from -Adobe in the first place — fonts such as <i>Times</i> that +Adobe in the first place — fonts such as <i>Times</i> that appear in pretty much every PostScript printer, or such as Adobe -<i>Sabon</i> that you pay extra for — then there’s no problem. +<i>Sabon</i> that you pay extra for — then there’s no problem. <p/>But most people use <i>Computer</i> <i>Modern</i> to start with, and even those relative sophisticates who use something as exotic as <i>Sabon</i> often find themselves using odd characters from CM without really intending to do so. Fortunately, rather good versions of the CM fonts are available from the AMS (who have them courtesy of -<a href="FAQ-commercial.html">Blue Sky Research</a> and Y&Y). +<a href="FAQ-commercial.html">Blue Sky Research</a> and Y&Y). <p/>Most modern systems have the fonts installed ready to use; and any system installed less than 3 years ago has a <i>dvips</i> -configuration file ‘<code>pdf</code>’ that signals the use of the +configuration file ‘<code>pdf</code>’ that signals the use of the CM fonts, and also sets a few other parameters to improve -<i>dvips</i>’ output. Use this configuration as: +<i>dvips</i>’ output. Use this configuration as: <pre> dvips -Ppdf myfile -o myfile.ps </pre> @@ -52,14 +52,14 @@ or something similar, or about failing to find a font file: dvips: ! Couldn't find header file cmr10.pfb </pre> Either of these failures signals that your -system doesn’t have the fonts in the first place. -<p/>A way of using the fonts that doesn’t involve the sophistication of +system doesn’t have the fonts in the first place. +<p/>A way of using the fonts that doesn’t involve the sophistication of the <code>-Ppdf</code> mechanism is simply to load maps: <pre> dvips -Pcmz -Pamz myfile -o myfile.ps </pre> You may encounter the same warning messages as listed above. -<p/>If your system does not have the fonts, it won’t have the +<p/>If your system does not have the fonts, it won’t have the configuration file either; however, it might have the configuration file without the fonts. In either case, you need to <a href="FAQ-inst1cm.html">install the fonts</a>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html index 4d9bdb0935d..c3deaab5a65 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html @@ -13,7 +13,7 @@ a wider range of resolutions, but they were resisted for two reasons: <li> The need to decide which printers to generate fonts for. The broad-brush approach taken for 300 dpi printers was (more or less) justified back then, given the dominance of certain printer - ‘engines’, but nowadays one could not make any such assumption. + ‘engines’, but nowadays one could not make any such assumption. <li> Given the above, justifying the space taken up by a huge array of bitmap fonts. </ul> @@ -23,24 +23,24 @@ fonts as needed, and cache them for later re-use. The impatient user, who is determined that all bitmap fonts should be created once and for all, may be supported by scripts such as <i>allcm</i> (distributed with TeX Live, at least; otherwise such a -person should consult “<a href="FAQ-useMF.html">the use of Metafont</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 using Type 1 versions of the CM fonts. Two free sets are available; the older (<i>bakoma</i>) is somewhat less well produced than the <i>bluesky</i> fonts, which were originally professionally produced and sold, but were then released -for general public use by their originators Y&Y and Bluesky Research, +for general public use by their originators Y&Y and Bluesky Research, in association with the AMS and other scientific publishers -(they are nowadays available under the SIL’s Open Fonts Licence). The +(they are nowadays available under the SIL’s Open Fonts Licence). The two sets contain slightly different ranges of fonts, but you are advised to use the <i>bluesky</i> set except when <i>bakoma</i> is for some reason -absolutely unavoidable. In recent years, several other ‘Metafont’ fonts -have been converted to Type 1 format; it’s common never to need to +absolutely unavoidable. In recent years, several other ‘Metafont’ fonts +have been converted to Type 1 format; it’s common never to need to generate bitmap fonts for any purpose other than previewing (see -<a href="FAQ-PSpreview.html">“previewing documents with Type 1 fonts”</a>), +<a href="FAQ-PSpreview.html">“previewing documents with Type 1 fonts”</a>), if even then. <p/>More modern fonts may be used in place of the Computer Modern set. The <a href="FAQ-ECfonts.html">EC fonts</a> and the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html index a5025da3f80..88297ed89c9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label gethelp</title> </head><body> <h3>How to get help</h3> -<p/>So you’ve looked at all relevant <a href="FAQ-whereFAQ.html">FAQs</a> you -can find, you’ve looked in any <a href="FAQ-books.html">books</a> you have, and -scanned relevant <a href="FAQ-tutorialstar.html">tutorials</a>… and still you -don’t know what to do. +<p/>So you’ve looked at all relevant <a href="FAQ-whereFAQ.html">FAQs</a> you +can find, you’ve looked in any <a href="FAQ-books.html">books</a> you have, and +scanned relevant <a href="FAQ-tutorialstar.html">tutorials</a>… and still you +don’t know what to do. <p/>If you are seeking a particular package or program, look on your own -system first: you might already have it — the better TeX +system first: you might already have it — the better TeX distributions contain a wide range of supporting material. The CTAN Catalogue can also identify packages that might help: you can <a href="http://www.tex.ac.uk/search">search it</a>, or you can browse it -“<a href="http://mirrors.ctan.org/help/Catalogue/bytopic.html">by topic</a>”. +“<a href="http://mirrors.ctan.org/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 directories now include documentation, so it’s -often worth looking at the catalogue entry for a package you’re considering +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 before; there are two places where people ask: browse or search the @@ -25,23 +25,23 @@ newsgroup <i>comp.text.tex</i> via and the mailing list <code>texhax</code> via its <a href="http://tug.org/pipermail/texhax/">archive</a>, or (as a long shot) the archives of ancient posts on CTAN. -<p/>If those “back question” searches fail, you’ll have to ask the world +<p/>If those “back question” searches fail, you’ll have to ask the world at large. To ask a question on <i>comp.text.tex</i>, you can use -your own news client (if you have one), or use the “start a new -topic” button on <a href="http://groups.google.com/group/comp.text.tex">http://groups.google.com/group/comp.text.tex</a>. +your own news client (if you have one), or use the “start a new +topic” button on <a href="http://groups.google.com/group/comp.text.tex">http://groups.google.com/group/comp.text.tex</a>. To ask a question on <code>texhax</code>, you may simply send mail to -<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>, but it’s probably better to subscribe to the +<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>, but it’s probably better to subscribe to the list (via <a href="http://tug.org/mailman/listinfo/texhax">http://tug.org/mailman/listinfo/texhax</a>) -first — not everyone will answer to you as well as to the list. +first — not everyone will answer to you as well as to the list. <p/>Do <b>not</b> try mailing the <a href="FAQ-LaTeX3.html">LaTeX project team</a>, the maintainers of the TeX Live or MiKTeX distributions or the maintainers of these FAQs for help; while all these addresses reach experienced (La)TeX users, no small group can possibly have expertise in every area of -usage so that the “big” lists are a far better bet. +usage so that the “big” lists are a far better bet. <dl> -<dt><tt><i>texhax ‘back copies’</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/digests/texhax/">digests/texhax/</a> +<dt><tt><i>texhax ‘back copies’</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/digests/texhax/">digests/texhax/</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html index 9ff4a89bdf6..dc4ce3621f7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graph-pspdf.html @@ -8,9 +8,9 @@ following advice is based on a post by one with much experience of dealing with the problem of dealing with EPS graphics in this case. <ul> -<li> Don’t specify a driver when loading loading whichever version of +<li> Don’t specify a driver when loading loading whichever version of the <i>graphics</i> package you use. The scheme relies on the - distribution’s ability to decide which driver is going to be used: + distribution’s ability to decide which driver is going to be used: the choice is between <i>dvips</i> and PDFTeX, in this case. Be sure to exclude options <code>dvips</code>, <code>pdftex</code> and <code>dvipdfm</code> (<i>dvipdfm</i> is not used in this scheme, @@ -25,10 +25,10 @@ case. done this, you will have two copies of each graphic (a <code>.eps</code> and a <code>.pdf</code> file) in your directory. <li> Use PDFLaTeX (rather than - LaTeX–<i>dvips</i>–distillation or - LaTeX–<i>dvipdfm</i>) to produce your PDF output. + LaTeX–<i>dvips</i>–distillation or + LaTeX–<i>dvipdfm</i>) to produce your PDF output. </ul> -<i>Dvipdfm</i>’s charms are less than attractive here: the +<i>Dvipdfm</i>’s charms are less than attractive here: the document itself needs to be altered from its default (<i>dvips</i>) state, before <i>dvipdfm</i> will process it. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html index 0f5d1397ff8..0b536135ab0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html @@ -1,33 +1,33 @@ <head> <title>UK TeX FAQ -- question label graphicspath</title> </head><body> -<h3>Importing graphics from “somewhere else”</h3> +<h3>Importing graphics from “somewhere else”</h3> <p/>By default, graphics commands like <code>\</code><code>includegraphics</code> look -“wherever TeX files are found” for the graphic file they’re being +“wherever TeX files are found” for the graphic file they’re being asked to use. This can reduce your flexibility if you choose to hold your graphics files in a common directory, away from your (La)TeX sources. -<p/>The simplest solution is to patch TeX’s path, by changing the +<p/>The simplest solution is to patch TeX’s path, by changing the default path. On most systems, the default path is taken from the -environment variable <code>TEXINPUTS</code>, if it’s present; you can adapt that +environment variable <code>TEXINPUTS</code>, if it’s present; you can adapt that to take in the path it already has, by setting the variable to <blockquote> <pre> -TEXINPUTS=.:<graphics path(s)>: +TEXINPUTS=.:<graphics path(s)>: </pre> </blockquote><p> -on a Unix system; on a Windows system the separator will be “<code>;</code>” -rather than “<code>:</code>”. The “<code>.</code>” is there to ensure +on a Unix system; on a Windows system the separator will be “<code>;</code>” +rather than “<code>:</code>”. The “<code>.</code>” is there to ensure that the current directory is searched first; the trailing -“<code>:</code>” says “patch in the value of <code>TEXINPUTS</code> from -your configuration file, here”. +“<code>:</code>” says “patch in the value of <code>TEXINPUTS</code> from +your configuration file, here”. <p/>This method has the merit of efficiency ((La)TeX does <em>all</em> of -the searches, which is quick), but it’s always clumsy and may prove +the searches, which is quick), but it’s always clumsy and may prove inconvenient to use in Windows setups (at least). <p/>The alternative is to use the <i>graphics</i> package command <code>\</code><code>graphicspath</code>; this command is of course also available to users of the <i>graphicx</i> and the <i>epsfig</i> packages. The -syntax of <code>\</code><code>graphicspath</code>’s one argument is slightly odd: it’s a +syntax of <code>\</code><code>graphicspath</code>’s one argument is slightly odd: it’s a sequence of paths (typically relative paths), each of which is enclosed in braces. A slightly odd sample, given in the <i>graphics</i> bundle documentation, is: @@ -38,26 +38,26 @@ enclosed in braces. A slightly odd sample, given in the </blockquote><p> however, if the security checks on your (La)TeX system allow, the path may be anything you choose (rather than strictly relative, like -those above); note that the trailing “<code>/</code>” <em>is</em> required. +those above); note that the trailing “<code>/</code>” <em>is</em> required. <p/>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of -graphics macros other than those from the graphics bundle — in +graphics macros other than those from the graphics bundle — in particular, those of the outdated <i>epsf</i> and <i>psfig</i> packages are immune. <p/>The disadvantage of the <code>\</code><code>graphicspath</code> method is inefficiency. The package will call (La)TeX once for each entry in the list, which is itself slows things. More seriously, TeX remembers the file name, -thus effectively losing memory, every time it’s +thus effectively losing memory, every time it’s asked to look up a file, so a document that uses a huge number of graphical inputs could be embarrassed by lack of memory. <p/>If your document is split into a variety of directories, and each directory has its associated graphics, the <i>import</i> package may well be the thing for you; see the discussion -in the question “ +in the question “ <a href="FAQ-docotherdir.html">bits of document in other directories</a> -”. +”. <dl> <dt><tt><i>graphics bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) -<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> +<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import.zip">macros/latex/contrib/import</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grffilenames.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grffilenames.html index f3439f22df2..a644d1966b0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grffilenames.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grffilenames.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label grffilenames</title> </head><body> -<h3>“Modern” graphics file names</h3> +<h3>“Modern” graphics file names</h3> <p/>TeX was designed in a world where file names were very simple indeed, typically strictly limited both in character set and length. In modern systems, such restrictions have largely disappeared, which @@ -11,7 +11,7 @@ period characters can seriously confuse the <i>graphics</i> package. <p/>The specification of TeX leaves some leeway for distributions to adopt file access appropriate to their operating system, but this -hasn’t got us very far. Many modern distributions allow you to +hasn’t got us very far. Many modern distributions allow you to specify a file name as <code>"file name.tex"</code> (for example), which helps somewhat, but while this allows us to say <blockquote> @@ -25,7 +25,7 @@ the analogous usage \includegraphics{"gappy graphics.eps"} </pre> </blockquote><p> -using “ordinary” LaTeX causes confusion in <i>xdvi</i> and +using “ordinary” LaTeX causes confusion in <i>xdvi</i> and <i>dvips</i>, even though it works at compilation time. Sadly, even within such quotes, multiple dots give <code>\</code><code>includegraphics</code> difficulties. Note that @@ -35,16 +35,16 @@ difficulties. Note that </pre> </blockquote><p> works in a similar version of PDFTeX. -<p/>If you’re using the <i>graphics</i> package, the <i>grffile</i> +<p/>If you’re using the <i>graphics</i> package, the <i>grffile</i> package will help. The package offers several options, the simplest of which are <code>multidot</code> (allowing more than one dot in a file name) and <code>space</code> (allowing space in a file name). The -<code>space</code> option requires that you’re running on a -sufficiently recent version of PDFTeX, in PDF mode — and -even then it won’t work for MetaPost files, which are read as TeX +<code>space</code> option requires that you’re running on a +sufficiently recent version of PDFTeX, in PDF mode — and +even then it won’t work for MetaPost files, which are read as TeX input, and therefore use the standard input mechanism). <dl> -<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/grffile.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grffilenames">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grffilenames</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html index 06edd868751..5655b2293f2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-grmaxwidth.html @@ -12,7 +12,7 @@ of course needs a little LaTeX internals programming): <pre> \makeatletter \def\maxwidth{% - \ifdim\Gin@nat@width>\linewidth + \ifdim\Gin@nat@width>\linewidth \linewidth \else \Gin@nat@width @@ -21,7 +21,7 @@ of course needs a little LaTeX internals programming): \makeatother </pre> </blockquote><p> -This defines a “variable” width which has the properties you want. +This defines a “variable” width which has the properties you want. Replace <code>\</code><code>linewidth</code> if you have a different constraint on the width of the graphic. <p/>Use the command as follows: diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html index 05ddfdb9a15..6817b2f9550 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gutter.html @@ -8,23 +8,23 @@ on the right of even-numbered pages. This is often thought to look odd, but it is quite right. <p/>The idea is that the typographic urge for symmetry should also apply to margins: if you lay an even numbered page to the left of an -odd-numbered one, you will see that you’ve three equal chunks of +odd-numbered one, you will see that you’ve three equal chunks of un-printed paper: the left margin of the even page, the right margin of the odd page, and the two abutting margins together. <p/>This is all very fine in the abstract, but in practical book(let) -production it only works “sometimes”. +production it only works “sometimes”. <p/>If your booklet is produced on double-width paper and stapled, the effect will be good; if your book(let) is produced using a so-called -“perfect” binding, the effect will again be good. -<p/>However, almost any “quality” book-binder will need some of your -paper to grab hold of, and a book bound in such a way won’t exhibit -the treasured symmetry unless you’ve done something about the margin +“perfect” binding, the effect will again be good. +<p/>However, almost any “quality” book-binder will need some of your +paper to grab hold of, and a book bound in such a way won’t exhibit +the treasured symmetry unless you’ve done something about the margin settings. <p/>The packages recommended in -“<a href="FAQ-marginpkgs.html">setting up margins</a>” mostly have provision for -a “binding offset” or a “binding correction” — search for -“binding” in the manuals (<i>vmargin</i> doesn’t help, here). -<p/>If you’re doing the job by hand (see +“<a href="FAQ-marginpkgs.html">setting up margins</a>” mostly have provision for +a “binding offset” or a “binding correction” — search for +“binding” in the manuals (<i>vmargin</i> doesn’t help, here). +<p/>If you’re doing the job by hand (see <a href="FAQ-marginmanual.html">manual margin setup</a>), the trick is to calculate your page and margin dimensions as normal, and then: <ul> @@ -38,8 +38,8 @@ which can be achieved by: \addtolength{\oddsidemargin}{offset} </pre> </blockquote><p> -(substituting something sensible like “<code>5mm</code>” for -“<code>offset</code>”, above). +(substituting something sensible like “<code>5mm</code>” for +“<code>offset</code>”, above). <p/>The above may not be the best you can do: you may well choose to change the <code>\</code><code>textwidth</code> in the presence of the binding offset; but the changes do work for constant <code>\</code><code>textwidth</code>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html index 0d74b368834..d629cb51e15 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hash.html @@ -3,21 +3,21 @@ </head><body> <h3>Defining macros within macros</h3> <p/>The way to think of this is that <code>##</code> gets replaced by <code>#</code> in just the -same way that <code>#1</code> gets replaced by ‘whatever is the first argument’. +same way that <code>#1</code> gets replaced by ‘whatever is the first argument’. <p/>So if you define a macro and use it as: <blockquote> <pre> \def\a#1{+++#1+++#1+++#1+++} \a{b} </pre> </blockquote><p> -the macro expansion produces ‘+++b+++b+++b+++’, +the macro expansion produces ‘+++b+++b+++b+++’, which people find normal. However, if we now replace part of the macro: <blockquote> <pre> \def\a#1{+++#1+++\def\x #1{xxx#1}} </pre> </blockquote><p> -<code>\</code><code>a{b}</code> will expand to ‘+++b+++<code>\def\x b{xxxb}</code>’. This +<code>\</code><code>a{b}</code> will expand to ‘+++b+++<code>\def\x b{xxxb}</code>’. This defines <code>\</code><code>x</code> to be a macro <em>delimited</em> by <code>b</code>, and taking no arguments, which people may find strange, even though it is just a specialisation of the example above. If you want <code>\</code><code>a</code> to @@ -28,7 +28,7 @@ define <code>\</code><code>x</code> to be a macro with one argument, you need to </pre> </blockquote><p> and <code>\</code><code>a{b</code>} will expand to -‘+++b+++<code>\def\x #1{xxx#1}</code>’, because <code>#1</code> gets replaced by ‘b’ +‘+++b+++<code>\def\x #1{xxx#1}</code>’, because <code>#1</code> gets replaced by ‘b’ and <code>##</code> gets replaced by <code>#</code>. <p/>To nest a definition inside a definition inside a definition then you need <code>####1</code>, as at each stage <code>##</code> is replaced by diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html index 90c263565be..f7d845b6c79 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-howmanypp.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label howmanypp</title> </head><body> <h3>How many pages are there in my document?</h3> -<p/>Simple documents (those that start at page 1, and don’t have any +<p/>Simple documents (those that start at page 1, and don’t have any breaks in their page numbering until their last page) present no problem to the seeker after this truth. The number of pages is reported by the <i>lastpage</i> package in its <code>LastPage</code> label. @@ -25,8 +25,8 @@ to the equivalent of the <code>LastPage</code> label and the <p/>Both <i>count1to</i> and <i>totpages</i> need the support of the <i>everyshi</i> package. <dl> -<dt><tt><i>count1to.sty and everyshi.sty</i></tt><dd> - Distributed in <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>) +<dt><tt><i>count1to.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/count1to.html">catalogue entry</a> +<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/everyshi.html">catalogue entry</a> <dt><tt><i>lastpage.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lastpage.zip">macros/latex/contrib/lastpage</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lastpage/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>totpages.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/totpages.zip">macros/latex/contrib/totpages</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/totpages/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html index a315dec9927..2230280cb7e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-htmlbib.html @@ -4,7 +4,7 @@ <h3>Making HTML of your Bibliography</h3> <p/>A neat solution is offered by the <i>noTeX</i> bibliography style. This style produces a <code>.bbl</code> file which is in fact a series of -HTML ‘<code>P</code>’ elements of class <code>noTeX</code>, and which +HTML ‘<code>P</code>’ elements of class <code>noTeX</code>, and which may therefore be included in an HTML file. Provision is made for customising your bibliography so that its content when processed by <i>noTeX</i> is different from that presented when it is processed @@ -14,8 +14,8 @@ make use of one of its modified versions of many common BibTeX styles, and post-process the output so produced using a <i>perl</i> script. <p/>A more conventional translator is the <i>awk</i> script -<i>bbl2html</i>, which translates the <code>.bbl</code> file you’ve generated: -a sample of the script’s output may be viewed on the web, at +<i>bbl2html</i>, which translates the <code>.bbl</code> file you’ve generated: +a sample of the script’s output may be viewed on the web, at <a href="http://rikblok.cjb.net/lib/refs.html">http://rikblok.cjb.net/lib/refs.html</a> <dl> <dt><tt><i>bbl2html.awk</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/misc/bbl2html.awk">biblio/bibtex/utils/misc/bbl2html.awk</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html index caaa70653c6..8b476794b10 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyper.html @@ -26,11 +26,11 @@ to external documents. <p/>The HyperTeX specification says that conformant viewers/translators must recognize the following set of <code>\</code><code>special</code> commands: <dl> -<dt>href:<dd> <code>html:<a href = "href_string"></code> -<dt>name:<dd> <code>html:<a name = "name_string"></code> -<dt>end:<dd> <code>html:</a></code> -<dt>image:<dd> <code>html:<img src = "href_string"></code> -<dt>base_name:<dd> <code>html:<base href = "href_string"></code> +<dt>href:<dd> <code>html:<a href = "href_string"></code> +<dt>name:<dd> <code>html:<a name = "name_string"></code> +<dt>end:<dd> <code>html:</a></code> +<dt>image:<dd> <code>html:<img src = "href_string"></code> +<dt>base_name:<dd> <code>html:<base href = "href_string"></code> </dl> <p/>The <em>href</em>, <em>name</em> and <em>end</em> commands are used to do the basic hypertext operations of establishing links between sections diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html index 4668f61d2a2..087e7d648ee 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyperdupdest.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label hyperdupdest</title> </head><body> -<h3>PDFTeX destination … ignored</h3> +<h3>PDFTeX destination … ignored</h3> <p/>The warning: <blockquote> <pre> @@ -12,12 +12,12 @@ </blockquote><p> arises because of duplicate page numbers in your document. The problem is usually soluble: see -<a href="FAQ-pdfpagelabels.html">PDF page destinations</a> — which +<a href="FAQ-pdfpagelabels.html">PDF page destinations</a> — which answer also describes the problem in more detail. <p/>If the identifier in the message is different, for example <code>name{figure.1.1}</code>, the problem is (often) due to a problem of package interaction. The <i>README</i> in the <i>hyperref</i> -distribution mentions some of these issues — for example, +distribution mentions some of these issues — for example, <code>equation</code> and <code>eqnarray</code> as supplied by the <i>amsmath</i> package; means of working around the problem are typically supplied there. @@ -48,9 +48,9 @@ For example: You should load packages in this order as a matter of course, unless the documentation of a package says you <em>must</em> load it after <i>hyperref</i>. (There are few packages that require to be -loaded after hyperref: one such is <i>memoir</i>’s -“<i>hyperref</i> fixup” package <i>memhfixc</i>.) -<p/>If loading your packages in the (seemingly) “correct” order doesn’t +loaded after hyperref: one such is <i>memoir</i>’s +“<i>hyperref</i> fixup” package <i>memhfixc</i>.) +<p/>If loading your packages in the (seemingly) “correct” order doesn’t solve the problem, you need to <a href="FAQ-gethelp.html">seek further help</a>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html index 8353a07c359..11e3458ee8b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphen.html @@ -3,23 +3,23 @@ </head><body> <h3>How does hyphenation work in TeX?</h3> <p/>Everyone knows what hyphenation is: we see it in most books we read, -and (if we’re alert) will spot occasional ridiculous mis-hyphenation +and (if we’re alert) will spot occasional ridiculous mis-hyphenation (at one time, British newspapers were a fertile source). <p/>Hyphenation styles are culturally-determined, and the same language -may be hyphenated differently in different countries — for example, +may be hyphenated differently in different countries — for example, British and American styles of hyphenation of English are very different. As a result, a typesetting system that is not restricted to a single language at a single locale needs to be able to change its hyphenation rules from time to time. <p/>TeX uses a pretty good system for hyphenation (originally designed -by Frank Liang — you may view his +by Frank Liang — you may view his <a href="http://tug.org/docs/liang/">Ph.D. thesis</a> online), and while -it’s capable of missing “sensible” hyphenation points, it seldom +it’s capable of missing “sensible” hyphenation points, it seldom selects grossly wrong ones. The algorithm matches candidates for hyphenation against a set of -“hyphenation patterns”. The candidates for hyphenation must be +“hyphenation patterns”. The candidates for hyphenation must be sequences of letters (or other single characters that TeX may be -persuaded to think of as letters) — things such as TeX’s +persuaded to think of as letters) — things such as TeX’s <code>\</code><code>accent</code> primitive interrupt hyphenation. <p/>Sets of hyphenation patterns are usually derived from analysis of a list of valid hyphenations (the process of derivation, using a tool @@ -27,7 +27,7 @@ called <i>patgen</i>, is not ordinarily a participatory sport). <p/>The patterns for the languages a TeX system is going to deal with may only be loaded when the system is installed. To change the set of languages, a <a href="FAQ-newlang.html">partial reinstallation</a> is necessary. -<p/>TeX provides two “user-level” commands for control of +<p/>TeX provides two “user-level” commands for control of hyphenation: <code>\</code><code>language</code> (which selects a hyphenation style), and <code>\</code><code>hyphenation</code> (which gives explicit instructions to the hyphenation engine, overriding the effect of the patterns). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html index 4b1eb28c382..a16744a4a55 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphenaccents.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label hyphenaccents</title> </head><body> -<h3>Accented words aren’t hyphenated</h3> -<p/>TeX’s algorithm for hyphenation gives up when it encounters an +<h3>Accented words aren’t hyphenated</h3> +<p/>TeX’s algorithm for hyphenation gives up when it encounters an <code>\</code><code>accent</code> command; there are good reasons for this, but it means that quality typesetting in non-English languages can be difficult. <p/>For TeX macro packages, you can avoiding the effect by using an -appropriately encoded font (for example, a Cork-encoded font — see +appropriately encoded font (for example, a Cork-encoded font — see <a href="FAQ-ECfonts.html">the EC fonts</a>) which contains accented letters as single glyphs. LaTeX users can achieve this end simply by adding the command @@ -14,9 +14,9 @@ by adding the command \usepackage[T1]{fontenc} </pre> to the preamble of their document. Other encodings (notably -LY1, once promoted by Y&Y inc) may be used +LY1, once promoted by Y&Y inc) may be used in place of T1. Indeed, most current 8-bit TeX font -encodings will ‘work’ with the relevant sets of hyphenation patterns. +encodings will ‘work’ with the relevant sets of hyphenation patterns. <p/>One might hope that, with the many aspirant successors to TeX such as <a href="FAQ-omegaleph.html">Omega</a>, <a href="FAQ-luatex.html">LuaTeX</a> and diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html index 50bcaf4f25e..7bf5d129683 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphexcept.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label hyphexcept</title> </head><body> <h3>Hyphenation exceptions</h3> -<p/>While TeX’s hyphenation rules are good, they’re not infallible: you +<p/>While TeX’s hyphenation rules are good, they’re not infallible: you will occasionally find words TeX just gets <em>wrong</em>. So for -example, TeX’s default hyphenation rules (for American English) don’t -know the word “<em>manuscript</em>”, and since it’s a long word you -may find you need to hyphenate it. You <em>can</em> “write the -hyphenation out” each time you use the word: +example, TeX’s default hyphenation rules (for American English) don’t +know the word “<em>manuscript</em>”, and since it’s a long word you +may find you need to hyphenate it. You <em>can</em> “write the +hyphenation out” each time you use the word: <blockquote> <pre> ... man\-u\-script ... @@ -15,7 +15,7 @@ hyphenation out” each time you use the word: </blockquote><p> Here, each of the <code>\</code><code>-</code> commands is converted to a hyphenated break, if (<em>and only if</em>) necessary. -<p/>That technique can rapidly become tedious: you’ll probably only accept +<p/>That technique can rapidly become tedious: you’ll probably only accept it if there are no more than one or two wrongly-hyphenated words in your document. The alternative is to set up hyphenations in the document preamble. To do that, for the hyphenation above, you would @@ -26,8 +26,8 @@ write: </pre> </blockquote><p> and the hyphenation would be set for the whole document. Barbara -Beeton publishes articles containing lists of these “hyphenation -exceptions”, in <i>TUGboat</i>; the hyphenation ‘man-u-script’ +Beeton publishes articles containing lists of these “hyphenation +exceptions”, in <i>TUGboat</i>; the hyphenation ‘man-u-script’ comes from one of those articles. <p/>What if you have more than one language in your document? Simple: select the appropriate language, and do the same as above: @@ -38,9 +38,9 @@ select the appropriate language, and do the same as above: \hyphenation{re-cher-cher} </pre> </blockquote><p> -(nothing clever here: this is the “correct” hyphenation of the word, -in the current tables). However, there’s a problem here: just as -words with accents in them won’t break, so <code>\</code><code>hyphenation</code> commands +(nothing clever here: this is the “correct” hyphenation of the word, +in the current tables). However, there’s a problem here: just as +words with accents in them won’t break, so <code>\</code><code>hyphenation</code> commands with accents in them produce an error: <blockquote> <pre> @@ -49,7 +49,7 @@ with accents in them produce an error: \hyphenation{r\'e-f\'e-rence} </pre> </blockquote><p> -tells us that the hyphenation is “improper”, and that it will be “flushed”. +tells us that the hyphenation is “improper”, and that it will be “flushed”. But, just as hyphenation of words is enabled by selecting an 8-bit font encoding, so <code>\</code><code>hyphenation</code> commands are rendered proper again by selecting that same 8-bit font encoding. For the hyphenation diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html index 0c79537ec74..60cc03bec17 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-hyphoff.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label hyphoff</title> </head><body> <h3>Stopping all hyphenation</h3> -<p/>It may seem an odd thing to want to do (after all, one of TeX’s -great advertised virtues is the quality of its hyphenation) but it’s +<p/>It may seem an odd thing to want to do (after all, one of TeX’s +great advertised virtues is the quality of its hyphenation) but it’s sometimes necessary. The real problem is, that the quality of -TeX’s output is by default largely dependent on the presence of +TeX’s output is by default largely dependent on the presence of hyphenation; if you want to abandon hyphenation, something has to give. <p/>TeX (slightly confusingly) offers four possible mechanisms for suppressing hyphenation (there were only two prior to the extensions that arrived with TeX version 3). <p/>First, one can set the hyphenation penalties <code>\</code><code>hyphenpenalty</code> and -<code>\</code><code>exhyphenpenalty</code> to an ‘infinite’ value (that is to say, 10000). +<code>\</code><code>exhyphenpenalty</code> to an ‘infinite’ value (that is to say, 10000). This means that all hyphenations will sufficiently penalise the line -that would contain them, that the hyphenation won’t happen. The +that would contain them, that the hyphenation won’t happen. The disadvantage of this method is that TeX will re-evaluate any paragraph for which hyphenations might help, which will slow TeX down. @@ -24,7 +24,7 @@ and the <i>hyphenat</i> package uses this technique for its <code>\</code><code>nohyphens</code> command which sets its argument without any hyphenation. You can load <i>hyphenat</i> with the command <blockquote> - <code>\</code><code>usepckage[none]{hyphenat}</code> + <code>\</code><code>usepackage[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 @@ -41,9 +41,9 @@ font by the command \hyphenchar\font=-1 </pre> </blockquote><p> -This isn’t a particularly practical way for users to suppress -hyphenation — the command has to be issued for every font the -document uses — but it’s how LaTeX itself suppresses hyphenation +This isn’t a particularly practical way for users to suppress +hyphenation — the command has to be issued for every font the +document uses — but it’s how LaTeX itself suppresses hyphenation in <code>tt</code> and other fixed-width fonts. <p/>Which of the techniques you should use depends on what you actually want to do. If the text whose hyphenation is to be suppressed runs @@ -67,7 +67,7 @@ be underfull lines to fill the space offered, while prematurely wrapping overfull lines and stretching the remainder. <p/>Alternatively, you may set the text <a href="FAQ-ragright.html">ragged right</a>, and at least get rid of the overfull lines; this technique is -‘traditional’ (in the sense that typists do it) and may be expected to +‘traditional’ (in the sense that typists do it) and may be expected to appeal to the specifiers of eccentric document layouts (such as those for dissertations), but for once their sense conforms with typographic style. (Or at least, style constrained in this curious way.) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html index 98ad3d8d427..23bcf613040 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-i18nbib.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label i18nbib</title> </head><body> <h3>Non-english bibliographies</h3> -<p/>Like so much of early (La)TeX software, BibTeX’s assumptions were +<p/>Like so much of early (La)TeX software, BibTeX’s assumptions were firmly rooted in what its author knew well, viz., academic papers in -English (particularly those with a mathematical bent). BibTeX’s +English (particularly those with a mathematical bent). BibTeX’s standard styles all address exactly that problem, leaving the user who writes in another language (or who deal with citations in the style of other disciplines than maths) to strike out into contributed software. @@ -20,24 +20,24 @@ Spanish citation style. <p/>These static approaches solve the problem, for the languages that have been covered by them. Unfortunately, with such an approach, a lot of work is needed for every language involved. Two routes to a solution -of the “general” problem are available — that offered by +of the “general” problem are available — that offered by <i>babelbib</i>, and the <a href="FAQ-custbib.html"><i>custom-bib</i> mechanism for generating styles</a>. <p/><i>Babelbib</i> (which is a development of the ideas of the <i>bibgerm</i> package) co-operates with <i>babel</i> to control the language of presentation of citations (potentially at the level of individual items). The package has a built-in set of languages it -‘knows about’, but the documentation includes instructions on defining +‘knows about’, but the documentation includes instructions on defining commands for other languages. <i>Babelbib</i> comes with its own set of bibliography styles, which could be a restriction if there -wasn’t also a link from <i>custom-bib</i>. +wasn’t also a link from <i>custom-bib</i>. <p/>The <i>makebst</i> menu of <i>custom-bib</i> allows you to -choose a language for the BibTeX style you’re generating (there are +choose a language for the BibTeX style you’re generating (there are 14 languages to choose; it looks as if <i>spain.bst</i>, mentioned above, was generated this way). If, however, you opt not to specify a language, you are asked whether you want the style to interact with -<i>babelbib</i>; if you do so, you’re getting the best of both -worlds — formatting freedom from <i>custom-bib</i> and linguistic +<i>babelbib</i>; if you do so, you’re getting the best of both +worlds — formatting freedom from <i>custom-bib</i> and linguistic freedom via the extensibility of <i>babelbib</i> <dl> <dt><tt><i>babelbib.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (or <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html index 9829d3ffd7f..3114eebe02a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label ifpdf</title> </head><body> <h3>Am I using PDFTeX?</h3> -<p/>It’s often useful to know whether your macros are operating within -PDFTeX or within (“normal”) TeX; getting the right answer is +<p/>It’s often useful to know whether your macros are operating within +PDFTeX or within (“normal”) TeX; getting the right answer is surprisingly tricky. <p/>Suppose you need to test whether your output will be PDF or DVI. The natural thing is to check whether you have access to @@ -20,7 +20,7 @@ was present in the very first releases of PDFTeX) is </pre> </blockquote><p> Except that neither branch of this conditional is rock-solid. The -first branch can be misleading, since the “awkward” user could have +first branch can be misleading, since the “awkward” user could have written: <blockquote> <pre> @@ -30,7 +30,7 @@ written: so that your test will falsely choose the first alternative. While this is a theoretical problem, it is unlikely to be a major one. <p/>More important is the user who loads a package that uses -LaTeX-style testing for the command name’s existence (for example, +LaTeX-style testing for the command name’s existence (for example, the LaTeX <i>graphics</i> package, which is useful even to the Plain TeX user). Such a package may have gone ahead of you, so the test may need to be elaborated: @@ -50,7 +50,7 @@ test may need to be elaborated: If you only want to know whether some PDFTeX extension (such as marginal kerning) is present, you can stop at this point: you know as much as you need. -<p/>However, if you need to know whether you’re creating PDF +<p/>However, if you need to know whether you’re creating PDF output, you also need to know about the value of <code>\</code><code>pdfoutput</code>: <blockquote> <pre> @@ -61,7 +61,7 @@ output, you also need to know about the value of <code>\</code><code>pdfoutput</ ... % not running PDFTeX \else % running PDFTeX, with... - \ifnum\pdfoutput>0 + \ifnum\pdfoutput>0 ... % PDF output \else ... % DVI output @@ -70,18 +70,19 @@ output, you also need to know about the value of <code>\</code><code>pdfoutput</ \fi </pre> </blockquote><p> -The above is, in essence, what Heiko Oberdiek’s <i>ifpdf</i> -package does; the reasoning is the FAQ’s interpretation of -Heiko’s explanation. +The above is, in essence, what Heiko Oberdiek’s <i>ifpdf</i> +package does; the reasoning is the FAQ’s interpretation of +Heiko’s explanation. <p/>As an aside: there are now analogous packages <i>ifxetex</i> and <i>ifluatex</i>, for the two up-and-coming TeX-like engines (see -the “TeX project” answers covering +the “TeX project” answers covering <a href="FAQ-xetex.html">XeTeX</a>, and <a href="FAQ-luatex.html">LuaTeX</a>). <dl> -<dt><tt><i>ifpdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) -<dt><tt><i>ifluatex.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>ifpdf.sty</i></tt><dd>Distributed as part Heiko Oberdiek’s bundle + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/ifpdf.html">catalogue entry</a> +<dt><tt><i>ifluatex.sty</i></tt><dd>Distributed as part of Heiko Oberdiek’s bundle + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/ifluatex.html">catalogue entry</a> <dt><tt><i>ifxetex.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/generic/ifxetex.zip">macros/generic/ifxetex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/generic/ifxetex/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html index ba9d038ddb5..ae5fce9ccde 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html @@ -3,7 +3,7 @@ </head><body> <h3>Importing graphics into (La)TeX documents</h3> <p/>Knuth, when designing the current version of TeX back in the early -1980s, could discern no “standard” way of expressing graphics in +1980s, could discern no “standard” way of expressing graphics in documents. He reasoned that this state could not persist for ever, but that it would be foolish for him to define TeX primitives that allowed the import of graphical image definitions. He therefore @@ -13,12 +13,12 @@ means of <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>. <p/>There is therefore a straightforward way for anyone to import graphics into their document: read the specification of the <code>\</code><code>special</code> -commands your driver uses, and ‘just’ code them. This is the -hair-shirt approach: it definitely works, but it’s not for everyone. -<p/>Over the years, therefore, “graphics inclusion” packages have sprung +commands your driver uses, and ‘just’ code them. This is the +hair-shirt approach: it definitely works, but it’s not for everyone. +<p/>Over the years, therefore, “graphics inclusion” packages have sprung up; most were designed for inclusion of -<a href="FAQ-eps.html">Encapsulated PostScript graphics</a> — +<a href="FAQ-eps.html">Encapsulated PostScript graphics</a> — which has become the <em>lingua franca</em> of graphics inclusion over the last decade or so. <p/>Notable examples are the <i>epsf</i> package (distributed with @@ -31,15 +31,15 @@ the above two cases), but their code could be configured for others. The LaTeX standard <i>graphics</i> package and its derivatives made this step: it is strongly preferred for all current work. <p/>Users of Plain TeX have two options allowing them to use -<i>graphicx</i>: the <i>miniltx</i> “LaTeX emulator” and +<i>graphicx</i>: the <i>miniltx</i> “LaTeX emulator” and the <i>graphicx.tex</i> front-end allow you to load <i>graphicx</i>, and <a href="FAQ-eplain.html">\Eplain</a> allows you to load it (using the full LaTeX syntax) direct. -<p/>The <i>graphics</i> package takes a variety of “driver -options” — package options that select code to generate the +<p/>The <i>graphics</i> package takes a variety of “driver +options” — package options that select code to generate the commands appropriate to the DVI driver in use. In most cases, your (La)TeX distribution will provide a <i>graphics.cfg</i> file -that will select the correct driver for what you’re doing (for +that will select the correct driver for what you’re doing (for example, a distribution that provides both LaTeX and PDFLaTeX will usually provide a configuration file that determines whether PDFLaTeX is running, and selects the definitions for it if so). @@ -51,7 +51,7 @@ graphics to be included. <p/>The <i>graphicx</i> package uses the facilities of of <i>graphics</i> behind a rather more sophisticated command syntax to provide a very powerful version of the <code>\</code><code>includegraphics</code> -command. <i>graphicx</i>’s version can combine scaling and +command. <i>graphicx</i>’s version can combine scaling and rotation, viewporting and clipping, and many other things. While this is all a convenience (at some cost of syntax), it is also capable of producing noticeably more efficient PostScript, and some of its @@ -62,33 +62,32 @@ package version. <code>\</code><code>epsfig</code>), capable of emulating the behaviour (if not the bugs) the old <i>psfig</i> package. <i>Epsfig</i> also supplies homely support for former users of the -<i>epsf</i> package. However, there’s a support issue: if you -declare you’re using <i>epsfig</i>, any potential mailing list or +<i>epsf</i> package. However, there’s a support issue: if you +declare you’re using <i>epsfig</i>, any potential mailing list or usenet helper has to clear out of the equation the possibility that -you’re using “old” <i>epsfig</i>, so that support is slower +you’re using “old” <i>epsfig</i>, so that support is slower coming than it would otherwise be. <p/>There is no rational reason to stick with the old packages, which have never been entirely satisfactory in the LaTeX context. (One -irrational reason to leave them behind is that their replacement’s -name tends not to imply that it’s exclusively related to PostScript +irrational reason to leave them behind is that their replacement’s +name tends not to imply that it’s exclusively related to PostScript graphics. The reasoning also excludes <i>epsfig</i>, of course.) <p/>A wide variety of detailed techniques and tricks have been developed -over the years, and Keith Reckdahl’s <i>epslatex</i> outlines them +over the years, and Keith Reckdahl’s <i>epslatex</i> outlines them in compendious detail: this highly recommendable document is available from CTAN. An invaluable review of the practicalities of exchanging graphics between sites, -“<a href="http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf">Graphics for Inclusion in Electronic Documents</a>” +“<a href="http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf">Graphics for Inclusion in Electronic Documents</a>” -has been written by Ian Hutchinson; the document isn’t on CTAN, +has been written by Ian Hutchinson; the document isn’t on CTAN, but may also be <a href="http://silas.psfc.mit.edu/elec_fig/">browsed on the Web</a>. <dl> <dt><tt><i>epsf.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/generic/epsf/epsf.tex">macros/generic/epsf/epsf.tex</a> <dt><tt><i>epsfig.sty</i></tt><dd>Part of the <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) bundle -<dt><tt><i>epslatex.pdf</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a>; the document is also available - in PostScript format as <a href="http://www.tex.ac.uk/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a> +<dt><tt><i>epslatex.pdf</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/epslatex.zip">info/epslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/epslatex/">browse the directory</a>) <dt><tt><i>graphics.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) <dt><tt><i>graphicx.sty</i></tt><dd>Part of the <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) bundle <dt><tt><i>miniltx.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html index edf5f310b5c..3b30d81e60f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inclplain.html @@ -3,12 +3,12 @@ </head><body> <h3>Including Plain TeX files in LaTeX</h3> <p/>LaTeX, though originally <a href="FAQ-LaTeXandPlain.html">based on Plain TeX</a>, does not -contain all of Plain TeX’s commands. Worse, some Plain TeX +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. <p/>The truly reliable way is to translate the Plain TeX commands, to -produce an equivalent of the original’s semantics. However, this is +produce an equivalent of the original’s semantics. However, this is not practical in many circumstances, and for those occasions, the <i>plain</i> package will often come to your aid. The package defines a <code>plain</code> environment, in which a Plain TeX @@ -22,10 +22,10 @@ document may be processed: </blockquote><p> The package is known to fail, for example, with documents that use AMSTeX; no doubt it would also fail if asked to load Eplain. -All these things can be overcome (although it’s not often easy), but +All these things can be overcome (although it’s not often easy), but the environment saves a lot of work on many occasions. <dl> -<dt><tt><i>plain.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>) +<dt><tt><i>plain.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/plain-ltx.html">catalogue entry</a> </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html index 7a758f34ee1..baf7f0ec470 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-include.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label include</title> </head><body> -<h3>What’s going on in my <code>\</code><code>include</code> commands?</h3> +<h3>What’s going on in my <code>\</code><code>include</code> commands?</h3> <p/>The original LaTeX provided the <code>\</code><code>include</code> command to address the problem of long documents: with the relatively slow computers of the time, the companion <code>\</code><code>includeonly</code> facility was a boon. With the @@ -10,24 +10,24 @@ vast increase in computer speed, <code>\</code><code>includeonly</code> is less Nevertheless, the facility is retained in current LaTeX, and causes some confusion to those who misunderstand it. <p/>In order for <code>\</code><code>includeonly</code> to work, <code>\</code><code>include</code> makes a separate -<code>.aux</code> file for each included file, and makes a ‘checkpoint’ of +<code>.aux</code> file for each included file, and makes a ‘checkpoint’ of important parameters (such as page, figure, table and footnote numbers); as a direct result, it <em>must</em> clear the current page -both before and after the <code>\</code><code>include</code> command. What’s more, this -mechanism doesn’t work if a <code>\</code><code>include</code> command appears in a file +both before and after the <code>\</code><code>include</code> command. What’s more, this +mechanism doesn’t work if a <code>\</code><code>include</code> command appears in a file that was <code>\</code><code>include</code>d itself: LaTeX diagnoses this as an error. <p/>So, we can now answer the two commonest questions about <code>\</code><code>include</code>: <ul> <li> Why does LaTeX throw a page before and after <code>\</code><code>include</code> commands? -<p/> Answer: because it has to. If you don’t like it, replace the - <code>\</code><code>include</code> command with <code>\</code><code>input</code> — you won’t be able to use - <code>\</code><code>includeonly</code> any more, but you probably don’t need it anyway, so - don’t worry. -<p/><li> Why can’t I nest <code>\</code><code>include</code>d files? — I always used to be +<p/> Answer: because it has to. If you don’t like it, replace the + <code>\</code><code>include</code> command with <code>\</code><code>input</code> — you won’t be able to use + <code>\</code><code>includeonly</code> any more, but you probably don’t need it anyway, so + don’t worry. +<p/><li> Why can’t I nest <code>\</code><code>include</code>d files? — I always used to be able to under LaTeX 2.09. -<p/> Answer: in fact, you couldn’t, even under LaTeX 2.09, but the failure - wasn’t diagnosed. However, since you were happy with the behaviour +<p/> Answer: in fact, you couldn’t, even under LaTeX 2.09, but the failure + wasn’t diagnosed. However, since you were happy with the behaviour under LaTeX 2.09, replace the <code>\</code><code>include</code> commands with <code>\</code><code>input</code> commands (with <code>\</code><code>clearpage</code> as appropriate). </ul> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html index 366d97da0c9..e7d1f73361a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inputlev.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label inputlev</title> </head><body> -<h3>Capacity exceeded — input levels</h3> +<h3>Capacity exceeded — input levels</h3> <p/>The error <pre> ! TeX capacity exceeded, sorry [text input levels=15]. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html index 7ffb88aba90..b9322d45213 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-miktexstar.html @@ -7,29 +7,29 @@ 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”, +<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; you can update the database over the internet. -<p/>If MiKTeX does know about a package you need installed, it’s worth +<p/>If MiKTeX does know about a package you need installed, it’s worth using the system: first, open the MiKTeX packages window: click on - <code>Start</code>-> - <code>Programs</code>-> - <code>MiKTeX</code>-> + <code>Start</code>-> + <code>Programs</code>-> + <code>MiKTeX</code>-> <code>MiKTeX Options</code>, and select the <code>Packages</code> tab. <p/>On the tab, there is an Explorer-style display of packages. -Right-click on the root of the tree, “<code>MiKTeX Packages</code>”, -and select “<code>Search</code>”: enter the name of the package you’re -interested in, and press the “<code>Search</code>” button. If +Right-click on the root of the tree, “<code>MiKTeX Packages</code>”, +and select “<code>Search</code>”: enter the name of the package you’re +interested in, and press the “<code>Search</code>” button. If MiKTeX knows about your package, it will open up the tree to show you a tick box for your package: check that box. -<p/>If you prefer a command-line utility, there’s <i>mpm</i>. Open a +<p/>If you prefer a command-line utility, there’s <i>mpm</i>. Open a command shell, and type: <blockquote> <pre> -mpm --install=<package> +mpm --install=<package> </pre> </blockquote><p> (which of course assumes you know the name by which MiKTeX refers to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html index 986973f8542..e07b37ce1e6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label inst-tds-zip</title> </head><body> <h3>Installing using ready-built ZIP files</h3> -<p/>Installing packages, as they (“traditionally”) appear on +<p/>Installing packages, as they (“traditionally”) appear on CTAN, involves: <ul> <li> identifying where to put the various files on an TDS @@ -12,13 +12,13 @@ CTAN, involves: </ul> Most people, for most packages, find the first two steps onerous, the last being easy (unless it is forgotten!). -<p/>Ready-built ZIP files — also known as -<a href="FAQ-tds-zip.html">TDS-ZIP files</a> — are designed to lighten +<p/>Ready-built 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 +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 +<p/>To install such a file on a Unix system (we assume that you’ll install into the local TEXMF tree, at <code>$TEXMFLOCAL</code>): <blockquote> <pre> @@ -28,14 +28,14 @@ unzip $package.tds.zip </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 +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 +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, +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>” +“<a href="FAQ-instt1font.html">Installing a Type 1 font</a>” <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tds-zip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tds-zip</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html index 6678ef7888a..fcdbd57ef5e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-tidy.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label inst-tidy</title> </head><body> <h3>Tidying up after installation</h3> -<p/>There’s not usually a lot to do after you’ve completed the steps -above — indeed, if you’re merely installed files direct from the +<p/>There’s not usually a lot to do after you’ve completed the steps +above — indeed, if you’re merely installed files direct from the archive, or whatever, there will be precisely nothing left, by way of debris. <p/>Things you might care to clean up are: @@ -17,6 +17,6 @@ debris. </ul> A simple way of achieving all this is to download to a working directory that was created for the purpose, and then to delete that -directory and all its contents after you’ve finished installing. +directory and all its contents after you’ve finished installing. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html index 2303718154d..a7b680477e9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst-wlcf.html @@ -1,20 +1,20 @@ <head> <title>UK TeX FAQ -- question label inst-wlcf</title> </head><body> -<h3>Installing files “where (La)TeX can find them”</h3> +<h3>Installing files “where (La)TeX can find them”</h3> <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. +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. <p/>It was from this issue that the whole idea of the TDS sprang; -“where to put” questions now come down to “where’s the TDS -tree?”. +“where to put” questions now come down to “where’s the TDS +tree?”. <p/>We therefore answer the question by considering: <ul> <li> <a href="FAQ-what-TDS.html">what tree to use</a>, and <li> <a href="FAQ-install-where.html">where in the tree to put the files</a>. </ul> -<p/>Once we know the answer to both questions, and we’ve created any +<p/>Once we know the answer to both questions, and we’ve created any directories that are needed, we simply copy files to their rightful location. <p/>This has done what the old requirement specified: LaTeX (or @@ -22,9 +22,9 @@ whatever) <em>can</em> (in principle) find the files. However, in order that the software <em>will</em> find the files, we need to update an index file. <p/>On a MiKTeX system, open the window - <code>Start</code>-> - <code>All Programs</code>-> - <code>MiKTeX <<i>version</i>></code>-> + <code>Start</code>-> + <code>All Programs</code>-> + <code>MiKTeX <<i>version</i>></code>-> <code>Settings</code>, and click on <code>Refresh FNDB</code>. The job may also be done in a command window, using the command: @@ -37,7 +37,7 @@ 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> — +<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. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html index 3070b9bb19c..d96e5433ac0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html @@ -3,7 +3,7 @@ </head><body> <h3>Installing the Type 1 versions of the CM fonts</h3> <p/>This is a specialised case of <a href="FAQ-instfont.html">installing a font</a>, -but it is almost never necessary — it’s inconceivable that any (even +but it is almost never necessary — it’s inconceivable that any (even remotely) recent system will <em>not</em> have the fonts already installed. You can confirm this (near-inevitable) fact by trying the fonts. On a system that uses <i>dvips</i> (almost all do), try @@ -14,17 +14,17 @@ the sequence: dvips -o sample2e.ps sample2e </pre> </blockquote><p> -at a “command prompt” (<i>shell</i>, in a Unix-style system, -“DOS box” in a Windows system). +at a “command prompt” (<i>shell</i>, in a Unix-style system, +“DOS box” in a Windows system). <p/>If the command works at all, the console output of the command will include a sequence of Type 1 font file names, listed as -<code><cmr10.pfb></code> and so on; this is <i>dvips</i> telling you -it’s copying information from the Type 1 font, and you need do no +<code><cmr10.pfb></code> and so on; this is <i>dvips</i> telling you +it’s copying information from the Type 1 font, and you need do no more. <p/>If the test has failed, you need to install your own set of the fonts; the distribution (including all the fonts the AMS designed and produced themselves) is now described as <i>amsfonts</i>. The -bundle contains metric and map files — all you need to +bundle contains metric and map files — all you need to <a href="FAQ-instt1font.html">install the fonts</a>. <p/><dl> <dt><tt><i>AMS and CM fonts, in Type 1 format</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html index b0248ad8f6e..8d7a25681a1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-doc.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label install-doc</title> </head><body> <h3>Generating package documentation</h3> -<p/>We are faced with a range of “normal” provision, as well as several +<p/>We are faced with a range of “normal” provision, as well as several oddities. One should note that documentation of many packages is available on CTAN, without the need of any further effort by -the user — such documentation can usually be browsed <em>in situ</em>. +the user — such documentation can usually be browsed <em>in situ</em>. <p/>However, if you find a package that does not offer documentation on the archive, or if you need the documentation in some other format than the archive offers, you can usually generate the documentation @@ -17,8 +17,8 @@ LaTeX file (i.e., repeatedly until the warnings go away). <i>package.drv</i>; if such a thing appears, process it in preference to the <i>package.dtx</i> (it seems that when the documented LaTeX source mechanism was first discussed, the <i>.drv</i> mechanism was -suggested, but it’s not widely used nowadays). -<p/>Sometimes, the LaTeX run will complain that it can’t find +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, not as you might imagine, a glossary). Both types of file are processed with special <i>makeindex</i> @@ -31,12 +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. If you don’t +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 +<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. +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-dist/doc/generic/FAQ-en/html/FAQ-install-find.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html index b264f5bf18c..3788a3f4f39 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-find.html @@ -9,19 +9,19 @@ have a link to the file (there are lists at the end of each answer): click on one of the links associated with the package, and you can get the package (which may be one file or several). -<p/>If you heard about the file somewhere else, it’s possible that the +<p/>If you heard about the file somewhere else, it’s possible that the source told you where to look; if not, try the CTAN searching facilities, such as <a href="http://www.tex.ac.uk/search/">http://www.tex.ac.uk/search/</a>. That (rather simple) search engine can return data from a search of the CTAN catalogue (which covers most useful packages), or data from a search of the names of files on the archive. <p/>Packages come in a variety of different styles of distribution; the -very simplest will actually offer just <i>package.sty</i> — in this +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/>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 +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 @@ -30,7 +30,7 @@ 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 +“<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-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html index 600d4b8d617..7a4f393dbcf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-unpack.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label install-unpack</title> </head><body> <h3>Unpacking LaTeX packages</h3> -<p/>As discussed <a href="FAQ-dtx.html">elsewhere</a>, the ‘ordinary’ way to +<p/>As discussed <a href="FAQ-dtx.html">elsewhere</a>, the ‘ordinary’ way to distribute a LaTeX package is as a pair of files <i>package.dtx</i> -and <i>package.ins</i>. If you’ve acquired such a pair, you simply +and <i>package.ins</i>. If you’ve acquired such a pair, you simply process <i>package.ins</i> with LaTeX, and the files will appear, ready for installation. <p/>Other sorts of provision should ordinarily be accompanied by a @@ -15,10 +15,10 @@ 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 +<p/>If you’re missing the <i>package.ins</i> altogether, you need to play 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 +“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 should document anything out of the ordinary with the distribution. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html index 42ec4dd1199..797749a8fc3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-install-where.html @@ -4,7 +4,7 @@ <h3>Where to install packages</h3> <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 +“<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 @@ -12,14 +12,14 @@ existing tree(s). Here are some examples of where various sorts of files should go: <blockquote> <pre> -.sty, .cls or .fd: $TEXMF/tex/<format>/<package>/ -.mf: $TEXMF/fonts/source/<supplier>/<font>/ -.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/ -.vf: $TEXMF/fonts/vf/<supplier>/<font>/ -.afm: $TEXMF/fonts/afm/<supplier>/<font>/ -.pfb: $TEXMF/fonts/type1/<supplier>/<font>/ -.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ -.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ +.sty, .cls or .fd: $TEXMF/tex/<format>/<package>/ +.mf: $TEXMF/fonts/source/<supplier>/<font>/ +.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/ +.vf: $TEXMF/fonts/vf/<supplier>/<font>/ +.afm: $TEXMF/fonts/afm/<supplier>/<font>/ +.pfb: $TEXMF/fonts/type1/<supplier>/<font>/ +.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ +.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ .pool, .fmt, .base or .mem: $TEXMF/web2c </pre> </blockquote><p> @@ -27,40 +27,40 @@ and for modern systems (those distributed in 2005 or later, using TDS v1.1 layouts): <blockquote> <pre> -.map: $TEXMF/fonts/map/<syntax>/<bundle>/ -.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ +.map: $TEXMF/fonts/map/<syntax>/<bundle>/ +.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ </pre> </blockquote><p> (Map and encoding files went to directories under <i>$TEXMF/dvips/</i>, in earlier distributions.) <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>, +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. +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 +<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 +(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>. +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 +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. -<p/>The font “supplier” <em>public</em> is a sort of hold-all for -“free fonts produced for use with (La)TeX”: as well as Knuth’s -fonts, <em>public</em>’s directory holds fonts designed by others +<p/>The font “supplier” <em>public</em> is a sort of hold-all for +“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/>Documentation for each package should all go, undifferentiated, into a directory on the <i>doc/</i> subtree of the TDS. The layout of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html index 4daeacdbfd9..bc3b42c5ffb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-installthings.html @@ -4,7 +4,7 @@ <h3>Installing things on a (La)TeX system</h3> <p/><p/>Installing (or replacing) things on your (La)TeX system has the potential to be rather complicated; the following questions attempt to -provide a step-by-step approach, starting from the point where you’ve +provide a step-by-step approach, starting from the point where you’ve decided what it is that you want to install: <ul> <li> You must <a href="FAQ-install-find.html">find the file you need</a>; diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html index e60489af791..4d1453f12ac 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instfont.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label instfont</title> </head><body> <h3>Installing a new font</h3> -<p/>Fonts are really “just another package”, and so should be installed +<p/>Fonts are really “just another package”, and so should be installed in the same sort of way as packages. However, fonts tend to be more -complicated than the average package, and as a result it’s sometimes +complicated than the average package, and as a result it’s sometimes difficult to see the overall structure. <p/>Font files may appear in any of a large number of different formats; each format has a different function in a TeX system, and each is -stored in a directory its own sub-tree in the installation’s +stored in a directory its own sub-tree in the installation’s TDS tree; all these sub-trees have the directory <i>$TEXMF/fonts</i> as their root. A sequence of answers describes the installation of fonts: -follow the list through the “next question” links at the bottom of +follow the list through the “next question” links at the bottom of this answer to view them all. -Other answers discuss specific font families — for example, +Other answers discuss specific font families — for example, -“<a href="FAQ-concrete.html">using the concrete fonts</a>”. +“<a href="FAQ-concrete.html">using the concrete fonts</a>”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html index 325dc388bff..e326e2144a3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instmffont.html @@ -5,14 +5,14 @@ <p/>Metafont fonts are (by comparison with other sorts of font) rather pleasingly simple. Nowadays, they are mostly distributed just as the Metafont source, since modern TeX distributions are able to produce -everything the user needs “on the fly”; however, if the distribution +everything the user needs “on the fly”; however, if the distribution <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 +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 schemes under different operating systems are another source of confusion. -<p/>“<a href="FAQ-install-where.html">Where to install files</a>” +<p/>“<a href="FAQ-install-where.html">Where to install files</a>” specifies where the files should go. <p/>Further confusion is introduced by font families whose authors devise rules for automatic generation of Metafont sources for generating fonts at diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html index 47e555859c1..c3d02ffc47b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instprinterfont.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label instprinterfont</title> </head><body> <h3>Installing a PostScript printer built-in font</h3> -<p/>There is a “standard” set of fonts that has appeared in every PostScript +<p/>There is a “standard” set of fonts that has appeared in every PostScript printer since the second generation of the type. These fonts (8 families of four text fonts each, and three special-purpose fonts) are of course widely used, because of their simple availability. The @@ -30,7 +30,7 @@ coverage of maths with <i>Times</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. +“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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html index 1a6d985500c..b02c081fa63 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html @@ -3,7 +3,7 @@ </head><body> <h3>Installing a Type 1 font</h3> <p/>Once you have a prepared Type 1 font, either direct from CTAN -or the like, or having <a href="FAQ-prept1font.html">‘prepared’ it yourself</a>, +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: @@ -14,12 +14,12 @@ much of what follows will be familiar: related to a font family <<i>fname</i>>: <pre> .pfb, -.pfa .../fonts/type1/<foundry>/<fname> -.tfm .../fonts/tfm/<foundry>/<fname> -.vf .../fonts/vf/<foundry>/<fname> +.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> +.fd .../tex/latex/<fname> +.map .../fonts/map/dvips/<foundry> </pre> but if you are lucky, you will be starting from a distribution from CTAN and there is a corresponding <code>.tds.zip</code> file: @@ -33,10 +33,10 @@ much of what follows will be familiar: system, execute the command <blockquote> <pre> -updmap-sys --enable Map <fname>.map +updmap-sys --enable Map <fname>.map </pre> </blockquote><p> - as root. (Do <em>not</em> use plain <i>updmap</i>: it’s a + as root. (Do <em>not</em> use plain <i>updmap</i>: it’s a potent source of confusion, setting up different map sets for different users.) <li> On a current MiKTeX system, update the system file @@ -49,7 +49,7 @@ initexmf --edit-config-file updmap adding a line at the end: <blockquote> <pre> -Map <fname>.map +Map <fname>.map </pre> </blockquote><p> for each font family <<i>fname</i>> you are adding to the system. @@ -60,11 +60,11 @@ initexmf --mkmaps </pre> </blockquote><p> This, and other matters, are described in MiKTeX - <a href="http://docs.miktex.org/manual/advanced.html">“advanced” documentation</a>. + <a href="http://docs.miktex.org/manual/advanced.html">“advanced” documentation</a>. </ul> </ul> Both processes (preparing and installing a font) are very well (and -thoroughly) described in Philipp Lehman’s guide to font installation, +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="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html index b4f1b4132ec..e22dadd71cf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-interruptlist.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label interruptlist</title> </head><body> <h3>Interrupting enumerated lists</h3> -<p/>It’s often convenient to have commentary text, ‘outside’ the list, +<p/>It’s often convenient to have commentary text, ‘outside’ the list, between successive entries of a list. In the case of -<code>itemize</code> lists this is no problem, since there’s never +<code>itemize</code> lists this is no problem, since there’s never anything to distinguish successive items, while in the case of -<code>description</code> lists, the item labels are under the user’s -control so there’s no automatic issue of continuity. +<code>description</code> lists, the item labels are under the user’s +control so there’s no automatic issue of continuity. <p/>For <code>enumerate</code> lists, the labels are generated automatically, and are context-sensitive, so the context (in this case, the state of the enumeration counter) needs to be preserved. @@ -22,18 +22,18 @@ restarting enumerate: ... \setcounter{saveenum}{\value{enumi}} \end{enumerate} -<Commentary text> +<Commentary text> \begin{enumerate} \setcounter{enumi}{\value{saveenum}} ... \end{enumerate} </pre> </blockquote><p> -<p/>This is reasonable, in small doses… Problems (apart from sheer -verbosity) are getting the level right (“should I use counter -<code>enumi</code>, <code>enumii</code>, …”) and remembering not to +<p/>This is reasonable, in small doses… Problems (apart from sheer +verbosity) are getting the level right (“should I use counter +<code>enumi</code>, <code>enumii</code>, …”) and remembering not to nest the interruptions (i.e., not to have a separate list, that is -itself interrupted) in the “commentary text”). +itself interrupted) in the “commentary text”). <p/>The <i>mdwlist</i> package defines commands <code>\</code><code>suspend</code> and <code>\</code><code>resume</code> that simplify the process: <blockquote> @@ -41,7 +41,7 @@ itself interrupted) in the “commentary text”). \begin{enumerate} ... \suspend{enumerate} -<Commentary text> +<Commentary text> \resume{enumerate} ... \end{enumerate} @@ -51,9 +51,9 @@ The package allows an optional name (as in <code>\</code><code>suspend[id]{enumerate}</code>) to allow you to identify a particular suspension, and hence provide a handle for manipulating nested suspensions. -<p/>If you’re suspending a <a href="FAQ-enumerate.html">fancy-enumeration list</a>, +<p/>If you’re suspending a <a href="FAQ-enumerate.html">fancy-enumeration list</a>, you need to -re-supply the optional “item label layout” parameters required by +re-supply the optional “item label layout” parameters required by the <i>enumerate</i> package when resuming the list, whether by the belt-and-braces approach, or by the <i>mdwlist</i> <code>\</code><code>resume{enumerate}</code> technique. The task is a little tedious @@ -65,7 +65,7 @@ which requires use of extra braces: \begin{enumerate}[\textbf{Item} i] ... \suspend{enumerate} -<comment> +<comment> \resume{enumerate}[{[\textbf{Item} i]}] ... \end{enumerate} @@ -78,17 +78,17 @@ release, will also allow you to resume lists: \begin{enumerate} ... \end{enumerate} -<comment> +<comment> \begin{enumerate}[resume] ... \end{enumerate} </pre> </blockquote><p> -which feels just as “natural” as the <i>mdwtools</i> facility, +which feels just as “natural” as the <i>mdwtools</i> facility, and has the advantage of playing well with the other excellent facilities of <i>enumitem</i>. <p/><i>Expdlist</i> has a neat way of providing for comments, with its -<code>\</code><code>listpart</code> command. The command’s argument becomes a comment +<code>\</code><code>listpart</code> command. The command’s argument becomes a comment between items of the list: <blockquote> <pre> @@ -100,9 +100,9 @@ between items of the list: \end{enumerate} </pre> </blockquote><p> -This, you will realise, means it doesn’t even have to think about +This, you will realise, means it doesn’t even have to think about suspending or resuming the list, and of course it works equally well -in any of the list environments (thought it’s not actually +in any of the list environments (thought it’s not actually <em>necessary</em> for any but <code>enumerate</code>). <p/><i>Enumitem</i> also allows multi-level suspension and resumption of lists: @@ -111,14 +111,14 @@ of lists: \begin{enumerate} \item outer item 1 \end{enumerate} -<comment> +<comment> \begin{enumerate}[resume] \item outer item 2 % nested enumerate \begin{enumerate} \item inner item 1 \end{enumerate} -<nested comment> +<nested comment> % resume nested enumerate \begin{enumerate}[resume] \item inner item 2 @@ -128,14 +128,14 @@ of lists: \end{enumerate} </pre> </blockquote><p> -However, the ‘nested comment’ interpolated in the nested enumeration -appears as if it were a second paragraph to “outer item 2”, which is +However, the ‘nested comment’ interpolated in the nested enumeration +appears as if it were a second paragraph to “outer item 2”, which is hardly satisfactory. <dl> -<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/enumerate.html">catalogue entry</a> <dt><tt><i>enumitem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse the directory</a>) <dt><tt><i>expdlist.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse the directory</a>) -<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) +<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mdwlist.html">catalogue entry</a> </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html index ae9732462f9..76a2c5ca5d8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isdef.html @@ -5,16 +5,16 @@ <p/>Macro sets from the earliest days of TeX programming may be observed to test whether commands exist by using <blockquote> -<code>\</code><code>ifx</code> csx<code><em>command</em></code> <code>\</code><code>undefined</code> <<i>stuff</i>> … +<code>\</code><code>ifx</code> csx<code><em>command</em></code> <code>\</code><code>undefined</code> <<i>stuff</i>> … </blockquote><p> -(which of course actually tests that the command <em>doesn’t</em> +(which of course actually tests that the command <em>doesn’t</em> exist). LaTeX programmers can make use of the internal command <blockquote> <code>\</code><code>@ifundefined{</code><em>cmd name</em><code>}{</code><em>action1</em><code>}{</code><em>action2</em><code>}</code> </blockquote><p> which executes <code>action1</code> if the command is undefined, and <code>action2</code> if it is defined -(<em>cmd name</em> is the command name only, omitting the ‘<code>\</code>’ character). +(<em>cmd name</em> is the command name only, omitting the ‘<code>\</code>’ character). <p/>The <code>\</code><code>@ifundefined</code> command is based on the sequence <blockquote> @@ -22,21 +22,21 @@ which executes <code>action1</code> if the command is undefined, and \expandafter \ifx \csname cmd name\endcsname \relax </pre> </blockquote><p> -which relies on the way <code>\</code><code>csname</code> works: if the command doesn’t +which relies on the way <code>\</code><code>csname</code> works: if the command doesn’t exist, it simply creates it as an alias for <code>\</code><code>relax</code>. <p/>So: what is wrong with these techniques? <p/>Using <code>\</code><code>undefined</code> blithely assumes that the command is indeed not -defined. This isn’t entirely safe; one could make the name more +defined. This isn’t entirely safe; one could make the name more improbable, but that may simply make it more difficult to spot a problem when things go wrong. LaTeX programmers who use the technique will typically employ <code>\</code><code>@undefined</code>, adding a single level of obscurity. <p/>The <code>\</code><code>@ifundefined</code> mechanism has the unfortunate property of polluting the name space: each test that turns out undefined adds a -name to the set TeX is holding, and often all those “<code>\</code><code>relax</code>” +name to the set TeX is holding, and often all those “<code>\</code><code>relax</code>” names serve no purpose whatever. Even so (sadly) there are places in the code of LaTeX where the existence of the <code>\</code><code>relax</code> is relied -upon, after the test, so we can’t get away from <code>\</code><code>@ifundefined</code> +upon, after the test, so we can’t get away from <code>\</code><code>@ifundefined</code> altogether. <p/>David Kastrup offers the (rather tricky) <blockquote> @@ -45,7 +45,7 @@ altogether. </pre> </blockquote><p> -which “creates” the <code>\</code><code>relax</code>-command inside the group of the first +which “creates” the <code>\</code><code>relax</code>-command inside the group of the first <code>\</code><code>expandafter</code>, therefore forgets it again once the test is done. The test is about as good as you can do with macros. <p/>The <a href="FAQ-etex.html">e-TeX system</a> system comes to our help here: it @@ -75,8 +75,8 @@ the same thing: </pre> </blockquote><p> However, after using the LaTeX -<code>\</code><code>@ifundefined{foo}</code>…, the conditionals will detect the -command as “existing” (since it has been <code>\</code><code>let</code> to <code>\</code><code>relax</code>); +<code>\</code><code>@ifundefined{foo}</code>…, the conditionals will detect the +command as “existing” (since it has been <code>\</code><code>let</code> to <code>\</code><code>relax</code>); so it is important not to mix mechanisms for detecting the state of a command. <p/>Since most distributions nowadays use e-TeX as their base executable diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html index 28e43afdc76..57ceb31250a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-isitanum.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label isitanum</title> </head><body> <h3>Is the argument a number?</h3> -<p/>TeX’s own lexical analysis doesn’t offer the macro programmer +<p/>TeX’s own lexical analysis doesn’t offer the macro programmer terribly much support: while category codes will distinguish letters (or what TeX currently thinks of as letters) from everything else, -there’s no support for analysing numbers. +there’s no support for analysing numbers. <p/>The simple-minded solution is to compare numeric characters with the characters of the argument, one by one, by a sequence of direct tests, -and to declare the argument “not a number” if any character fails +and to declare the argument “not a number” if any character fails all comparisons: <blockquote> <pre> @@ -22,27 +22,27 @@ all comparisons: </blockquote><p> which one would then use in a tail-recursing macro to gobble an argument. One could do slightly better by assuming (pretty safely) -that the digits’ character codes are consecutive: +that the digits’ character codes are consecutive: <blockquote> <pre> -\ifnum`#1<`0 \isanumfalse -\else\ifnum`#1>`9 \isanumfalse +\ifnum`#1<`0 \isanumfalse +\else\ifnum`#1>`9 \isanumfalse \fi \fi </pre> </blockquote><p> -again used in tail-recursion. However, these forms aren’t very -satisfactory: getting the recursion “right” is troublesome (it has a +again used in tail-recursion. However, these forms aren’t very +satisfactory: getting the recursion “right” is troublesome (it has a tendency to gobble spaces in the argument), and in any case TeX itself has mechanisms for reading numbers, and it would be nice to use them. -<p/>Donald Arseneau’s <i>cite</i> package offers the following test +<p/>Donald Arseneau’s <i>cite</i> package offers the following test for an argument being a strictly positive integer: <blockquote> <pre> \def\IsPositive#1{% TT\fi - \ifcat_\ifnum0<0#1 _\else A\fi + \ifcat_\ifnum0<0#1 _\else A\fi } </pre> </blockquote><p> @@ -50,7 +50,7 @@ which can be adapted to a test for a non-negative integer thus: <blockquote> <pre> \def\IsNonNegative{% - \ifcat_\ifnum9<1#1 _\else A\fi + \ifcat_\ifnum9<1#1 _\else A\fi } </pre> </blockquote><p> @@ -60,14 +60,14 @@ or a test for any integer: \def\gobbleminus#1{\ifx-#1\else#1\fi} \def\IsInteger#1{% TT\fi - \ifcat_\ifnum9<1\gobbleminus#1 _\else A\fi + \ifcat_\ifnum9<1\gobbleminus#1 _\else A\fi } </pre> </blockquote><p> but this surely stretches the technique further than is reasonable. -<p/>If we don’t care about the sign, we can use TeX to remove the +<p/>If we don’t care about the sign, we can use TeX to remove the entire number (sign and all) from the input stream, and then look at -what’s left: +what’s left: <blockquote> <pre> @@ -94,16 +94,16 @@ In a later thread on the same topic, Michael Downes offered: </blockquote><p> which relies on <code>\</code><code>romannumeral</code> producing an empty result if its argument is zero. Sadly, this technique has the unfortunate property -that it accepts simple expressions such as ‘<code>1+2-3</code>’; this +that it accepts simple expressions such as ‘<code>1+2-3</code>’; this could be solved by an initial <code>\</code><code>gobbleminus</code>-like construction. <p/>All the complete functions above are designed to be used in TeX -conditionals written “naturally” — for example: +conditionals written “naturally” — for example: <blockquote> <pre> -\if\IsInteger{<subject of test>}% - <deal with integer>% +\if\IsInteger{<subject of test>}% + <deal with integer>% \else - <deal with non-integer>% + <deal with non-integer>% \fi </pre> </blockquote><p> @@ -111,7 +111,7 @@ The LaTeX <i>memoir</i> class has an internal command of its own, <code>\</code><code>checkifinteger{</code><em>num</em><code>}</code>, that sets the conditional command <code>\</code><code>ifinteger</code> according to whether the argument was an integer. <p/>Of course, all this kerfuffle would be (essentially) void if there was -a simple means of “catching” TeX errors. Imagining an +a simple means of “catching” TeX errors. Imagining an error-catching primitive <code>\</code><code>ifnoerror</code>, one might write: <blockquote> <pre> @@ -128,8 +128,8 @@ error-catching primitive <code>\</code><code>ifnoerror</code>, one might write: } </pre> </blockquote><p> -thus using TeX’s own integer-parsing code to do the check. It’s a -pity that such a mechanism was never defined (it could be that it’s +thus using TeX’s own integer-parsing code to do the check. It’s a +pity that such a mechanism was never defined (it could be that it’s impossible to program within TeX!). <dl> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html index 936dbcda3ae..731b2ac6421 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-journalpaper.html @@ -4,20 +4,20 @@ <h3>Setting papers for journals</h3> <p/>Publishers of journals have a wide range of requirements for the presentation of papers, and while many publishers do accept electronic -submissions in (La)TeX, they don’t often submit recommended macros to +submissions in (La)TeX, they don’t often submit recommended macros to public archives. <p/>Nevertheless, there are considerable numbers of macros of one sort or another available on CTAN; searching for your journal name in -the CTAN catalogue — see -<a href="FAQ-findfiles.html">searching CTAN</a>) — -may well turn up what you’re seeking. +the CTAN catalogue — see +<a href="FAQ-findfiles.html">searching CTAN</a>) — +may well turn up what you’re seeking. <p/>Failing that, you may be well advised to contact the prospective publisher of your paper; many publishers have macros on their own web sites, or otherwise available only upon application. <p/>Check that the publisher is offering you macros suitable to an environment you can use: a few still have no macros for current -LaTeX, for example, claiming that LaTeX 2.09 is good enough… -<p/>Some publishers rekey anything sent them anyway, so that it doesn’t +LaTeX, for example, claiming that LaTeX 2.09 is good enough… +<p/>Some publishers rekey anything sent them anyway, so that it doesn’t really matter what macros you use. Others merely encourage you to use as few extensions of a standard package as possible, so that they will find it easy to transform your paper to their own internal form. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html index 84234b0e9dd..23f20ef8905 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keepfonts.html @@ -11,7 +11,7 @@ same base name as does the input (<em>e.g.</em>, if the input file was and <i>cmr10.log</i>). <p/>For TeX to use the font, you need a TFM file, so you need to keep that. However, you are likely to generate the same font -at more than one magnification, and each time you do so you’ll +at more than one magnification, and each time you do so you’ll (incidentally) generate another TFM file; these files are all the same, so you only need to keep one of them. <p/>To preview or to produce printed output, the DVI processor will need a @@ -19,7 +19,7 @@ font raster file; this is what the GF file provides. However, while there used (once upon a time) to be DVI processors that could use GF files, modern processors use packed raster (PK) files. Therefore, you need to generate a PK file from the GF file; the -program <i>gftopk</i> does this for you, and once you’ve done that you +program <i>gftopk</i> does this for you, and once you’ve done that you may throw the GF file away. <p/>The log file should never need to be used, unless there was some sort of problem in the Metafont run, and need not be ordinarily kept. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keyval.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keyval.html index 1781ef5dc91..12dd6fc6bb7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keyval.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-keyval.html @@ -5,7 +5,7 @@ <p/>When we discussed <a href="FAQ-moren9.html">extending the number of arguments to a macro</a>, we suggested that large numbers of arguments, distinguished only by their -position, aren’t very kind to the user, and that a package such as +position, aren’t very kind to the user, and that a package such as <i>keyval</i> offers a more attractive user interface. We now consider the packages that the macro programmer might use, to create such a user interface. @@ -26,10 +26,10 @@ will produce output saying: Foo is 3<br/> Bar is 99 </blockquote><p> -This has defined two keys ‘<code>foo</code>’ and ‘<code>bar</code>’ in family -‘<code>my</code>’, and then executed them, the first with argument -‘<code>3</code>’ and the second with no argument, so that the default -value of ‘<code>99</code>’ is picked up. In effect, the two calls to +This has defined two keys ‘<code>foo</code>’ and ‘<code>bar</code>’ in family +‘<code>my</code>’, and then executed them, the first with argument +‘<code>3</code>’ and the second with no argument, so that the default +value of ‘<code>99</code>’ is picked up. In effect, the two calls to <code>\</code><code>define@key</code> are simply defining commands, as (for example): <blockquote> <pre> @@ -38,34 +38,34 @@ value of ‘<code>99</code>’ is picked up. In effect, the two calls t </blockquote><p> (the definition of <code>\</code><code>KV@my@bar</code> is similar, but trickier). The command <code>\</code><code>setkeys</code> knows how to find those commands when it needs to -process each key — it is easy to regurgitate the structure of the -command name, with family name (‘<code>my</code>’, here) after the first -‘<code>@</code>’, and the key name after the second ‘<code>@</code>’. (The -‘<code>KV</code>’ part is fixed, in <i>keyval</i>.) +process each key — it is easy to regurgitate the structure of the +command name, with family name (‘<code>my</code>’, here) after the first +‘<code>@</code>’, and the key name after the second ‘<code>@</code>’. (The +‘<code>KV</code>’ part is fixed, in <i>keyval</i>.) <p/>These simple commands are enough, in fact, to process the botanical example offered as replacement for multi-argument commands in <a href="FAQ-moren9.html">the question mentioned above</a>, or the optional arguments of the <code>\</code><code>includegraphics</code> command of the <i>graphicx</i> package. (The last is, in fact, what <i>keyval</i> was designed to do.) -<p/>However, we need more if we’re to to have package options in -‘key-value’ form. Packages like <i>hyperref</i> have enormously +<p/>However, we need more if we’re to to have package options in +‘key-value’ form. Packages like <i>hyperref</i> have enormously complicated package options which need key-value processing at -<code>\</code><code>ProcessOptions</code> time: <i>keyval</i> can’t do that on its own. -<p/>Heiko Oberdiek’s <i>kvoptions</i> package comes to our help: it +<code>\</code><code>ProcessOptions</code> time: <i>keyval</i> can’t do that on its own. +<p/>Heiko Oberdiek’s <i>kvoptions</i> package comes to our help: it enables the programmer to declare class or package options that operate as key and value pairs. The package defines commands <code>\</code><code>DeclareBoolOption</code> for options whose value should be either <em>true</em> or <em>false</em>, and <code>\</code><code>DeclareStringOption</code> for all other options that have a value. Keys are declared using <i>keyval</i> and may remain available for use within the document, -or may be ‘cancelled’ to avoid confusion. If you have loaded -<i>kvoptions</i>, the LaTeX kernel’s <code>\</code><code>DeclareOption</code> becomes -<code>\</code><code>DeclareVoidOption</code> (it’s an option with no value), and +or may be ‘cancelled’ to avoid confusion. If you have loaded +<i>kvoptions</i>, the LaTeX kernel’s <code>\</code><code>DeclareOption</code> becomes +<code>\</code><code>DeclareVoidOption</code> (it’s an option with no value), and <code>\</code><code>DeclareOption*</code> becomes <code>\</code><code>DeclareDefaultOption</code>. <p/>Heiko also provides <i>kvsetkeys</i> which is a more robust version of <i>setkeys</i>, with some of the rough edges made smoother. -<p/>Hendri Adriaens’ <i>xkeyval</i> offers more flexibility than +<p/>Hendri Adriaens’ <i>xkeyval</i> offers more flexibility than the original <i>keyval</i> and is more robust than the original, too. Like <i>kvoptions</i>, the package also has mechanisms to allow class and package options in key-value form (macros @@ -76,7 +76,7 @@ called <i>pst-xkey</i> for their own key-value manipulation. <p/>The (widely-respected) <i>pgf</i> graphics package has its own key-value package called <i>pgfkeys</i>. The documentation of the package (part of the huge <i>pgf</i> manual, in part 5, -“utilities”) contains a useful comparison with other key-value +“utilities”) contains a useful comparison with other key-value systems; some notable differences are: <ul> <li> key organisation: <i>pgfkeys</i> uses a tree structure, while @@ -99,7 +99,7 @@ added automatically. So a <code>\</code><code>pgfkeys</code> command might be: </blockquote><p> and for each key mentioned, the associated code will be executed. -… and that code is also set up using <code>\</code><code>pgfkeys</code>: +… and that code is also set up using <code>\</code><code>pgfkeys</code>: <blockquote> <pre> \pgfkeys{/my key/.code=The value is '#1'.} @@ -113,13 +113,13 @@ after which </blockquote><p> will produce just <blockquote> - The value is ’hi!’. + The value is ’hi!’. </blockquote><p> The manual goes on, showing how to define a key with two arguments, how to provide default value for a key, and how to define aliases for -particular key sequences (which are called “styles”). All in all, +particular key sequences (which are called “styles”). All in all, it seems a well thought-out system, offering a lot of flexibility that -isn’t available with the other keys packages. However, there seems to +isn’t available with the other keys packages. However, there seems to be no mechanism for using <i>pgfkeys</i> keys as part of the options of another package, in the way that <i>kvoptions</i> does. <p/>The <i>expl3</i> programming layer for <a href="FAQ-LaTeX3.html">LaTeX3</a> @@ -131,7 +131,7 @@ for defining and setting keys. There is also a support package, options to be processed using <i>l3keys</i>. The <i>expl3</i> code can be used within existing LaTeX2e documents, so <i>l3keys</i> is available to the LaTeX2e programmer. -<p/>Another key-value system that’s part of larger set of macros is +<p/>Another key-value system that’s part of larger set of macros is <i>scrbase</i>, which uses the facilities of <i>keyval</i> to build a larger set of facilities, originally for use within the <i>KOMA-script</i> bundle. For English-speaking authors, there are @@ -139,25 +139,25 @@ difficulties from the German-only documentation; however, from a partial translation available to the author of this answer, a summary is possible. The package may build on the facilities either of <i>kyeval</i> or of <i>xkeyval</i>, and builds its functionality -on the structure of the ‘key family’. The user may define family -‘members’ and keys are defined relative to the members. (For example, +on the structure of the ‘key family’. The user may define family +‘members’ and keys are defined relative to the members. (For example, the package <i>scrbase</i> is part of the <i>KOMA-script</i> bundle; so its keys are all members of the <i>scrbase.sty</i> family within the <i>KOMA</i> family. The function <code>\</code><code>FamilyProcessOptions</code> allows the programmer to decode the options -of the package in terms of the package’s key family. Note that there -is no special provision made for “traditional” package options, as +of the package in terms of the package’s key family. Note that there +is no special provision made for “traditional” package options, as in the <i>kvoptions</i> package. <p/>This brief summary was guided by input from two sources: a draft article for <i>TUGboat</i> by Joseph Wright, and the partial translation of the documentation of package <i>scrbase</i> prepared by Philipp Stephani. <dl> -<dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) -<dt><tt><i>kvoptions.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) -<dt><tt><i>kvsetkeys.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>)[keyval +<dt><tt><i>kvoptions.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/kvoptions.html">catalogue entry</a> +<dt><tt><i>kvsetkeys.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/kvsetkeys.html">catalogue entry</a> <dt><tt><i>l3keys.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3.zip">macros/latex/contrib/expl3</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3/">browse the directory</a>) -<dt><tt><i>l3keys2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3.zip">macros/latex/contrib/expl3</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expl3/">browse the directory</a>) +<dt><tt><i>l3keys2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xpackages.zip">macros/latex/contrib/xpackages</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xpackages/">browse the directory</a>) <dt><tt><i>pgfkeys.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf.zip">graphics/pgf</a> (or <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse the directory</a>) <dt><tt><i>scrbase.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) <dt><tt><i>xkeyval.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval.zip">macros/latex/contrib/xkeyval</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html index c3f4bb9993b..7ca320c4793 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelctr.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label labelctr</title> </head><body> <h3>Making labels from a counter</h3> -<p/>Suppose we have a LaTeX counter, which we’ve defined with +<p/>Suppose we have a LaTeX counter, which we’ve defined with <code>\</code><code>newcounter{foo}</code>. We can increment the value of the counter -by <code>\</code><code>addtocounter{foo}{1}</code>, but that’s pretty clunky for an -operation that happens so often … so there’s a command +by <code>\</code><code>addtocounter{foo}{1}</code>, but that’s pretty clunky for an +operation that happens so often … so there’s a command <code>\</code><code>stepcounter{foo}</code> that does this special case of increasing-by-one. -<p/>There’s an internal LaTeX variable, the “current label”, that -remembers the last ‘labellable’ thing that LaTeX has processed. +<p/>There’s an internal LaTeX variable, the “current label”, that +remembers the last ‘labellable’ thing that LaTeX has processed. You could (if you were to insist) set that value by the relevant TeX command (having taken the necessary precautions to ensure that -the internal command worked) — but it’s not necessary. If, instead +the internal command worked) — but it’s not necessary. If, instead of either of the stepping methods above, you say <code>\</code><code>refstepcounter{foo}</code>, the internal variable is set to the new value, and (until something else comes along), <code>\</code><code>label</code> will diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html index 3ed767ecf10..82f45edcb89 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label labelfig</title> </head><body> <h3>Labelling graphics</h3> -<p/>“Technical” graphics (such as graphs and diagrams) are often +<p/>“Technical” graphics (such as graphs and diagrams) are often labelled with quite complex mathematical expressions: there are few drawing or graphing tools that can do such things (the honourable exception being MetaPost, which allows you to program the labels, in @@ -11,9 +11,9 @@ exception being MetaPost, which allows you to program the labels, in the <i>psfrag</i> package can help. Place an unique text in your graphic, using the normal text features of your tool, and you can ask <i>psfrag</i> to replace the text with arbitrary -(La)TeX material. <i>Psfrag</i>’s “operative” command is +(La)TeX material. <i>Psfrag</i>’s “operative” command is <code>\</code><code>psfrag{<em>PS text</em>}{<em>Repl text</em>}</code>, which instructs -the system to replace the original (“<code>PS</code>”) text with the +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. @@ -25,7 +25,7 @@ usage. In fact, the <i>pst-pdf</i> support package use with <i>psfrag</i>. <p/>On the other hand, - <a href="FAQ-commercial.html">VTeX</a>’s GeX processor + <a href="FAQ-commercial.html">VTeX</a>’s GeX processor explicitly deals with <i>psfrag</i>, both in its free and commercial instances. <p/>The <i>psfragx</i> package goes one step further than @@ -37,7 +37,7 @@ script <i>laprint</i> for use with <i>Matlab</i> to produce appropriately tagged output. (In principle, other graphics applications could provide a similar facility, but apparently none does.) <p/><i>Emacs</i> users may find the embedded editor <i>iTe</i> a -useful tool for placing labels: it’s a (La)TeX-oriented graphical +useful tool for placing labels: it’s a (La)TeX-oriented graphical editor written in <i>Emacs Lisp</i>. You create <code>iteblock</code> environments containing graphics and text, and may then invoke <i>iTe</i> to arrange the elements relative to one @@ -46,7 +46,7 @@ another. <code>picture</code> environment on a graphic included by use of <code>\</code><code>includegraphics</code>. This treatment lends itself to ready placement of texts and the like on top of a graphic. The package can draw a -grid for planning your “attack”; the distribution comes with simple +grid for planning your “attack”; the distribution comes with simple examples. <p/><i>Pstricks</i> can of course do everything that <i>overpic</i> can, with all the flexibility of PostScript programming that it offers diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html index 2f8db896a4f..5db3b5a6368 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelformat.html @@ -4,32 +4,32 @@ <h3>How to change the format of labels</h3> <p/>By default, when a label is created, it takes on the appearance of the counter labelled, so the label appears as -<code>\</code><code>the</code><code><<i>counter</i>></code> — what would be used if you -asked to typeset the counter in your text. This isn’t always what you +<code>\</code><code>the</code><code><<i>counter</i>></code> — what would be used if you +asked to typeset the counter in your text. This isn’t always what you need: for example, if you have nested enumerated lists with the outer numbered and the inner labelled with letters, one might expect to want -to refer to items in the inner list as “2(c)”. (Remember, you can +to refer to items in the inner list as “2(c)”. (Remember, you can <a href="FAQ-enumerate.html">change the structure of list items</a>.) The change is of course possible by explicit labelling of the parent and using that label to -construct the typeset result — something like +construct the typeset result — something like <blockquote> <pre> \ref{parent-item}(\ref{child-item}) </pre> </blockquote><p> -which would be both tedious and error-prone. What’s more, it would be +which would be both tedious and error-prone. What’s more, it would be undesirable, since you would be constructing a visual representation -which is inflexible (you couldn’t change all the references to elements +which is inflexible (you couldn’t change all the references to elements of a list at one fell swoop). <p/>LaTeX in fact has a label-formatting command built into every label -definition; by default it’s null, but it’s available for the user to -program. For any label <<i>counter</i>> there’s a LaTeX internal +definition; by default it’s null, but it’s available for the user to +program. For any label <<i>counter</i>> there’s a LaTeX internal command <code>\</code><code>p@</code><<i><code>counter</i>></code>; for example, a label definition on an inner list item is supposedly done using the command <code>\</code><code>p@enumii{<code>\</code><code>theenumii</code>}</code>. Unfortunately, the internal -workings of this aren’t quite right, and you need to patch the +workings of this aren’t quite right, and you need to patch the <code>\</code><code>refstepcounter</code> command: <blockquote> @@ -52,7 +52,7 @@ all inner lists by adding the following code in your preamble: </pre> </blockquote><p> This would make the labels for second-level enumerated lists appear as -“1(a)” (and so on). The analogous change works for any counter that +“1(a)” (and so on). The analogous change works for any counter that gets used in a <code>\</code><code>label</code> command. <p/>In fact, the <i>fncylab</i> package does all the above (including the patch to LaTeX itself). With the package, the code above is @@ -68,7 +68,7 @@ package, which is discussed in the answer about <a href="FAQ-enumerate.html">decorating enumeration lists</a>. <dl> <dt><tt><i>enumitem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse the directory</a>) -<dt><tt><i>fncylab.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/fncylab.sty">macros/latex/contrib/misc/fncylab.sty</a> +<dt><tt><i>fncylab.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fncylab.zip">macros/latex/contrib/fncylab</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fncylab/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html index a42e2954bd1..fab4814b7a6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labundef.html @@ -3,7 +3,7 @@ </head><body> <h3>Finding if a label is undefined</h3> <p/>People seem to want to know (at run time) if a label is undefined (I -don’t actually understand <em>why</em>, particularly: it’s a transient +don’t actually understand <em>why</em>, particularly: it’s a transient state, and LaTeX deals with it quite well). <p/>A resolved label is simply a command: <code>\</code><code>r@</code><code><<i>label-name</i>></code>; determining if the label is set is @@ -21,15 +21,15 @@ sequences to be used if the label is undefined <p/>Note that any command that incorporates <code>\</code><code>@ifundefined</code> is naturally fragile, so remember to create it with <code>\</code><code>DeclareRobustCommand</code> or to use it with <code>\</code><code>protect</code> in a moving argument. -<p/>If you’re into this game, you may well not care about LaTeX’s +<p/>If you’re into this game, you may well not care about LaTeX’s warning about undefined labels at the end of the document; however, if you are, include the command <code>\</code><code>G@refundefinedtrue</code> in <<i><code>undef-cmds</i>></code>. -<p/>And of course, remember you’re dealing in internal commands, and pay +<p/>And of course, remember you’re dealing in internal commands, and pay attention to the <a href="FAQ-atsigns.html">at-signs</a>. <p/>All the above can be avoided by using the <i>labelcas</i> package: it provides commands that enable you to switch according to the state -of a single label, or the states of a list of labels. The package’s +of a single label, or the states of a list of labels. The package’s definition is a bit complicated, but the package itself is pretty powerful. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html index 3fa879cb54e..91c918f85c9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-landscape.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label landscape</title> </head><body> <h3>Typesetting things in landscape orientation</h3> -<p/>It’s often necessary to typeset part of a document in landscape +<p/>It’s often necessary to typeset part of a document in landscape orientation; to achieve this, one needs not only to change the page dimensions, but also to instruct the output device to print the strange page differently. -<p/>There are two “ordinary” mechanisms for doing two slight variations +<p/>There are two “ordinary” mechanisms for doing two slight variations of landscape typesetting: <ul> <li> If you have a single floating object that is wider than it is @@ -24,7 +24,7 @@ of landscape typesetting: landscape (perhaps a code listing, a wide <code>tabbing</code> environment, or a huge table typeset using <i>longtable</i> or <i>supertabular</i>), use the <i>lscape</i> package (or - <i>pdflscape</i> if you’re generating PDF output, whether + <i>pdflscape</i> if you’re generating PDF output, whether using PDFLaTeX or <i>dvips</i> and generating PDF from that). Both packages define an environment <code>landscape</code>, which clears the current page and restarts typesetting in landscape @@ -32,7 +32,7 @@ of landscape typesetting: before returning to portrait orientation). </ul> No currently available package makes direct provision for typesetting -in both portrait and landscape orientation on the same page (it’s not +in both portrait and landscape orientation on the same page (it’s not the sort of thing that TeX is well set-up to do). If such behaviour was an absolute necessity, one might use the techniques described in @@ -66,15 +66,15 @@ rotation requests in DVI files. Your best bet is to convert your output to PostScript or to PDF, and -to view these ‘final’ forms with an appropriate viewer. +to view these ‘final’ forms with an appropriate viewer. <dl> <dt><tt><i>geometry.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse the directory</a>) <dt><tt><i>graphics.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) -<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) -<dt><tt><i>lscape.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) +<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/longtable.html">catalogue entry</a> +<dt><tt><i>lscape.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/lscape.html">catalogue entry</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) -<dt><tt><i>pdflscape.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>pdflscape.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/pdflscape.html">catalogue entry</a> <dt><tt><i>rotating.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotating.zip">macros/latex/contrib/rotating</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotating/">browse the directory</a>) <dt><tt><i>rotfloat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotfloat.zip">macros/latex/contrib/rotfloat</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotfloat/">browse the directory</a>) <dt><tt><i>supertabular.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html index 45ebbff0b07..5014dd563ae 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex.html @@ -9,7 +9,7 @@ need not think about presentation. By using document classes and add-on packages, the same document can be produced in a variety of different layouts. <p/>Lamport says that LaTeX -“<em>represents a balance between functionality and ease of use</em>”. +“<em>represents a balance between functionality and ease of use</em>”. This shows itself as a continual conflict that leads to the need for such things as FAQs: LaTeX <em>can</em> meet most user requirements, but finding out <em>how</em> is often diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html index 47d1d7ed479..f51c15233ca 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latex2e.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label latex2e</title> </head><body> <h3>What is LaTeX2e?</h3> -<p/>Lamport’s last version of LaTeX (LaTeX 2.09, last updated in 1992) +<p/>Lamport’s last version of LaTeX (LaTeX 2.09, last updated in 1992) was superseded in 1994 by a new version (LaTeX2e) provided by <a href="FAQ-LaTeX3.html">the LaTeX team</a>. LaTeX2e is now the only readily-available version of LaTeX, and draws together several threads of LaTeX development -from the later days of LaTeX 2.09. The “e” of the name is (in the +from the later days of LaTeX 2.09. The “e” of the name is (in the <a href="FAQ-logos.html">official logo</a>) @@ -16,13 +16,13 @@ a single-stroke epsilon indicative of no more than a small change. <p/>LaTeX2e has several enhancements over LaTeX 2.09, but they were all rather minor, with a view to continuity and stability rather than the -“big push” that some had expected from the team. LaTeX2e +“big push” that some had expected from the team. LaTeX2e continues to this day to offer a compatibility mode in which most files prepared for use with LaTeX 2.09 will run (albeit with somewhat reduced performance, and subject to voluminous complaints in the log file). Differences between LaTeX2e and LaTeX 2.09 are -outlined in a series of ‘guide’ files that are available in every -LaTeX distribution (the same directory also contains “news” about +outlined in a series of ‘guide’ files that are available in every +LaTeX distribution (the same directory also contains “news” about each new release of LaTeX2e). <dl> <dt><tt><i>LaTeX guides and news</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html index fdc854a2f5d..921eb5dfbc1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html @@ -5,14 +5,14 @@ <p/>The LaTeX team supports LaTeX, and will deal with <em>bona fide</em> bug reports. Note that the LaTeX team does -<em>not</em> deal with contributed packages — just the software that +<em>not</em> deal with contributed packages — just the software that is part of the LaTeX distribution itself: LaTeX and the -“required” packages. +“required” packages. Furthermore, you need to be slightly careful to produce a bug report that is usable by the team. The steps are: <p/><b>1.</b> Are you still using current LaTeX? Maintenance is only -available for sufficiently up-to-date versions of LaTeX — if your +available for sufficiently up-to-date versions of LaTeX — if your LaTeX is more than two versions out of date, the bug reporting mechanisms may reject your report. <p/><b>2.</b> Has your bug already been reported? Browse the @@ -21,11 +21,11 @@ mechanisms may reject your report. to find any earlier instance of your bug. In many cases, the database will list a work-around. <p/><b>3.</b> Prepare a -<a href="FAQ-minxampl.html">“minimum” file</a> that exhibits the problem. -Ideally, such a file should contain no contributed packages — the +<a href="FAQ-minxampl.html">“minimum” file</a> that exhibits the problem. +Ideally, such a file should contain no contributed packages — the LaTeX team as a whole takes no responsibility for such packages (if -they’re supported at all, they’re supported by their authors). The -“minimum” file should be self-sufficient: if a member of the team +they’re supported at all, they’re supported by their authors). The +“minimum” file should be self-sufficient: if a member of the team should run it in a clean directory, on a system with no contributed packages, it should replicate your problem. <p/><b>4.</b> Run your file through LaTeX: the bug @@ -38,11 +38,11 @@ report via the web (7, below). latex latexbug </pre> <i>latexbug</i> asks you some questions, and then lets you describe -the bug you’ve found. It produces an output file <i>latexbug.msg</i>, -which includes the details you’ve supplied, your “minimum” example +the bug you’ve found. It produces an output file <i>latexbug.msg</i>, +which includes the details you’ve supplied, your “minimum” example file, and the log file you got after running the example. (I always need to edit the result before submitting it: typing text into -<i>latexbug</i> isn’t much fun.) +<i>latexbug</i> isn’t much fun.) <p/><b>6.</b> Mail the resulting file to <i>latex-bugs@latex-project.org</i>; the subject line of your email should be the same as the bug title you gave to <i>latexbug</i>. The @@ -51,7 +51,7 @@ attachments are likely to be rejected by the bug processor. <p/><b>7.</b> Connect to the <a href="http://www.latex-project.org/bugs-upload.html">latex bugs processing web page</a> -and enter details of your bug — category, summary and full +and enter details of your bug — category, summary and full description, and the two important files (source and log file); note that members of the LaTeX team <em>need</em> your name and email address, as they may need to discuss the bug with you, or to advise you of a diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html index b17da04d6dc..2277a7e7587 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexpronounce.html @@ -1,16 +1,16 @@ <head> <title>UK TeX FAQ -- question label latexpronounce</title> </head><body> -<h3>How should I pronounce “LaTeX(2e)”?</h3> +<h3>How should I pronounce “LaTeX(2e)”?</h3> <p/>Lamport never recommended how one should pronounce LaTeX, but a lot -of people pronounce it ‘Lay TeX’ or perhaps ‘Lah TeX’ (with +of people pronounce it ‘Lay TeX’ or perhaps ‘Lah TeX’ (with TeX pronounced as the program itself; see <a href="FAQ-TeXpronounce.html">the rules for TeX</a>). It is definitely <em>not</em> to be pronounced in the same way as the rubber-tree gum -(which would be ‘lay teks’). +(which would be ‘lay teks’). <p/>The LaTeX2e logo is supposed to end with an ε; nevertheless, most -people pronounce the name as ‘LaTeX-two-ee’. +people pronounce the name as ‘LaTeX-two-ee’. <p><em>This answer last edited: 2009-06-08</em></p> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html index 0a3b964d3a1..5dfe770e6a3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexqual.html @@ -5,9 +5,9 @@ <p/>The <i>l2tabu</i> tutorial (mentioned in <a href="FAQ-man-latex.html">online introductions</a>) is undoubtedly a good read. -<p/>However, it’s always difficult to remember the things you should +<p/>However, it’s always difficult to remember the things you should <em>not</em> do, when there are so many things to remember that you -really must do: some automation is needed…. +really must do: some automation is needed…. <p/>The nicely-named <i>nag</i> allows you to apply a configurable set of checks to your document, as you run it through LaTeX; you get messages like: @@ -19,17 +19,17 @@ Package nag Warning: Command \bf is an old LaTeX 2.09 command. </blockquote><p> (the package provides a demo file which contains most of the sorts - of errors you might make — this is one of them). + of errors you might make — this is one of them). -<p/>There’s also a web site +<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 (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 +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 draconian. <dl> -<dt><tt><i>l2tabu</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/l2tabu/">info/l2tabu/</a> for a copy in a language that’s +<dt><tt><i>l2tabu</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/l2tabu/">info/l2tabu/</a> for a copy in a language that’s convenient for you <dt><tt><i>nag.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/nag.zip">macros/latex/contrib/nag</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/nag/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html index eae9c92a51f..7f4415a591a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexwords.html @@ -4,30 +4,30 @@ <h3>Changing the words <i>babel</i> uses</h3> <p/>LaTeX uses symbolic names for many of the automatically-generated text it produces (special-purpose section headings, captions, etc.). -As noted in <a href="FAQ-fixnam.html">“\LaTeX fixed names”</a> (which +As noted in <a href="FAQ-fixnam.html">“\LaTeX fixed names”</a> (which includes a list of the names themselves), this enables the user to change the names used by the standard classes, which is particularly useful if -the document is being prepared in some language other than LaTeX’s +the document is being prepared in some language other than LaTeX’s default English. So, for example, a Danish author may wish that her -table of contents was called “Indholdsfortegnelse”, and so +table of contents was called “Indholdsfortegnelse”, and so would expect to place a command <pre> \renewcommand{\contentsname}% {Indholdsfortegnelse} </pre> in the preamble of her document. -<p/>However, it’s natural for a user of a non-English language to use +<p/>However, it’s natural for a user of a non-English language to use <i>babel</i>, because it offers many conveniences and typesetting niceties for those preparing documents in those languages. In particular, when <i>babel</i> is selecting a new language, it -ensures that LaTeX’s symbolic names are translated appropriately -for the language in question. Unfortunately, <i>babel</i>’s choice -of names isn’t always to everyone’s choice, and there is still a need -for a mechanism to replace the ‘standard’ names. +ensures that LaTeX’s symbolic names are translated appropriately +for the language in question. Unfortunately, <i>babel</i>’s choice +of names isn’t always to everyone’s choice, and there is still a need +for a mechanism to replace the ‘standard’ names. <p/>Whenever a new language is selected, <i>babel</i> resets all the names to the settings for that language. In particular, -<i>babel</i> selects the document’s main language when +<i>babel</i> selects the document’s main language when <code>\</code><code>begin{document}</code> is executed, which immediately destroys any changes to these symbolic names made in the prologue of a document that uses <i>babel</i>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html index 0730b80d754..4b280e1bea8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterclass.html @@ -17,14 +17,14 @@ in the preamble of your file. <p/>Doing-it-yourself is a common strategy; Knuth (for use with Plain TeX, in the TeXbook), and Kopka and Daly (in their Guide to LaTeX) offer worked examples. -<p/>Nevertheless, there <em>are</em> contributed alternatives — in fact +<p/>Nevertheless, there <em>are</em> contributed alternatives — in fact there are an awfully large number of them: the following list, of necessity, makes but a small selection. <p/>The largest, most comprehensive, class is <i>newlfm</i>; the <code>lfm</code> part of the name implies that the class can create letters, faxes and memoranda. The documentation is voluminous, and the package seems very flexible. -<p/>Axel Kielhorn’s <i>akletter</i> class is the only other one, +<p/>Axel Kielhorn’s <i>akletter</i> class is the only other one, recommended for inclusion in this FAQ, whose documentation is available in English. <p/>The <i>dinbrief</i> class, while recommended, is only documented in @@ -33,7 +33,7 @@ German. <i>KOMA-script</i> (<i>scrlttr2</i>: documentation is available in English) and <i>ntgclass</i> (<i>brief</i>: documentation in Dutch only) bundles. While these are probably good (since the bundles -themselves inspire trust) they’ve not been specifically recommended by +themselves inspire trust) they’ve not been specifically recommended by any users. <dl> <dt><tt><i>akletter.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/akletter.zip">macros/latex/contrib/akletter</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/akletter/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html index f3436278743..e6beec141fa 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-letterspace.html @@ -8,8 +8,8 @@ between the letters (otherwise known as the tracking). As a general rule, this is a very bad idea: it detracts from legibility, which is contrary to the principles of typesetting (any respectable font you might be using should already have optimum tracking built into it). -<p/>The great type designer, Eric Gill, is credited with saying “he who -would letterspace lower-case text, would steal sheep”. (The +<p/>The great type designer, Eric Gill, is credited with saying “he who +would letterspace lower-case text, would steal sheep”. (The attribution is probably apocryphal: others are also credited with the remark. Stealing sheep was, in the 19th century, a capital offence in Britain.) As the remark suggests, though, letterspacing of upper-case @@ -23,14 +23,14 @@ the <code>.tex</code> file). <p/>A more comprehensive solution is to be found in the <i>soul</i> package (which is optimised for use with LaTeX, but also works with Plain TeX). Soul also permits hyphenation of letterspaced text; -Gill’s view of such an activity is not (even apocryphally) recorded. +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>microtype</i>, +<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 +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, and the package provides a means of protecting the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html index e65a45b7e86..72fe78d0686 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-limits.html @@ -6,7 +6,7 @@ expressions on operators such as <code>\</code><code>sum</code> and <code>\</code><code>int</code> physically above and below the operator. In (La)TeX, we write these limit expressions using sub- and superscripts applied to the operator, but -they don’t always appear in the “handwritten” way in TeX’s +they don’t always appear in the “handwritten” way in TeX’s output. <p/>The reason is, that when an expression appears in non-display maths, in running text (and is therefore in TeX <code>\</code><code>textstyle</code>), placing @@ -21,9 +21,9 @@ $\sum\limits_{n=1}^{m} ...$ </pre> </blockquote><p> which will place the limits right above and below the symbol (and be -blowed to the typography…). +blowed to the typography…). <p/>Contrariwise, you may wish to change the arrangement of the limits -when in <code>\</code><code>displaystyle</code>. For this purpose, there’s a corresponding +when in <code>\</code><code>displaystyle</code>. For this purpose, there’s a corresponding <code>\</code><code>nolimits</code>: <blockquote> <pre> @@ -33,13 +33,13 @@ when in <code>\</code><code>displaystyle</code>. For this purpose, there’ which will place the limits as they would be in <code>\</code><code>textstyle</code>. <p/>Alternatively, one can manipulate the <code>\</code><code>textstyle</code>/<code>\</code><code>displaystyle</code> state of the mathematics. To get -“<code>\</code><code>limits</code> placement” in inline maths, +“<code>\</code><code>limits</code> placement” in inline maths, <blockquote> <pre> $\displaystyle\sum_{n=1}^{m} ...$ </pre> </blockquote><p> -and for “<code>\</code><code>nolimits</code> placement” in display maths, +and for “<code>\</code><code>nolimits</code> placement” in display maths, <code>\</code><code>nolimits</code>: <blockquote> <pre> @@ -47,9 +47,9 @@ and for “<code>\</code><code>nolimits</code> placement” in display m </pre> </blockquote><p> will serve. Either of these forms may have effects other than on the -operator you’re considering, but there are still those who prefer this +operator you’re considering, but there are still those who prefer this formulation. -<p/>Remember, if you’re +<p/>Remember, if you’re <a href="FAQ-newfunction.html">declaring a special operator of your own</a>, the AMSLaTeX functions (that you ought to be using) allow you to choose how limits are displayed, at definition time. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html index 29380d0849f..a8bcdab11a5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linenos.html @@ -8,7 +8,7 @@ individual lines of typeset output) and <i>numline</i>. (<i>Numline</i> is considered obsolete, but remains available from the archive.) <p/>Both of these packages play fast and loose with the LaTeX output -routine, which can cause problems: the user should beware… +routine, which can cause problems: the user should beware… <p/>If the requirement is for numbering verbatim text, <i>moreverb</i>, or <i>fancyvrb</i> (see <a href="FAQ-verbfile.html">including files verbatim</a>) may be used. @@ -31,7 +31,7 @@ the package itself, is pretty tough going, though there is an example <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>moreverb.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb.zip">macros/latex/contrib/moreverb</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb/">browse the directory</a>) <dt><tt><i>numline.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/obsolete/macros/latex/contrib/numline/numline.sty">obsolete/macros/latex/contrib/numline/numline.sty</a> -<dt><tt><i>vruler.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/vruler.sty">macros/latex/contrib/misc/vruler.sty</a> +<dt><tt><i>vruler.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vruler.zip">macros/latex/contrib/vruler</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vruler/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html index 9322e78470a..3ace591e904 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespace.html @@ -3,21 +3,21 @@ </head><body> <h3>Double-spaced documents in LaTeX</h3> <p/>A quick and easy way of getting inter-line space for copy-editing is -to change <code>\</code><code>baselinestretch</code> — <code>\</code><code>linespread{1.2}</code> (or, +to change <code>\</code><code>baselinestretch</code> — <code>\</code><code>linespread{1.2}</code> (or, equivalently <code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{1.2}</code>) may -be adequate. Note that <code>\</code><code>baselinestretch</code> changes don’t take +be adequate. Note that <code>\</code><code>baselinestretch</code> changes don’t take effect until you select a new font, so make the change in the preamble -before any font is selected. Don’t try changing <code>\</code><code>baselineskip</code>: +before any font is selected. Don’t try changing <code>\</code><code>baselineskip</code>: its value is reset at any size-changing command so that results will be inconsistent. <p/>For preference (and certainly for a production document, such as a dissertation or an article submission), use a line-spacing package. The only one currently supported is <i>setspace</i> (do <em>not</em> -be tempted by <i>doublespace</i> — its performance under current +be tempted by <i>doublespace</i> — its performance under current LaTeX is at best problematical). <i>Setspace</i> switches off double-spacing at places where even the most die-hard official would -doubt its utility (footnotes, figure captions, and so on); it’s very -difficult to do this consistently if you’re manipulating +doubt its utility (footnotes, figure captions, and so on); it’s very +difficult to do this consistently if you’re manipulating <code>\</code><code>baselinestretch</code> yourself. <p/>Of course, the real solution (other than for private copy editing) is <em>not</em> to use double-spacing at all. Universities, in particular, @@ -25,12 +25,12 @@ have no excuse for specifying double-spacing in submitted dissertations: LaTeX is a typesetting system, not a typewriter-substitute, and can (properly used) make single-spaced text even more easily readable than double-spaced typewritten text. If you -have any influence on your university’s system (for example, through +have any influence on your university’s system (for example, through your dissertation supervisor), it may be worth attempting to get the -rules changed (at least to permit a “well-designed book” format). +rules changed (at least to permit a “well-designed book” format). <p/>Double-spaced submissions are also commonly required when submitting papers to conferences or journals. Fortunately (judging by the -questions from users in this author’s department), this demand is +questions from users in this author’s department), this demand is becoming less common. <p/>Documentation of <i>setspace</i> appears as TeX comments in the package file itself. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html index 9b88f051958..4d7a868de20 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linespread.html @@ -1,17 +1,17 @@ <head> <title>UK TeX FAQ -- question label linespread</title> </head><body> -<h3>Why doesn’t <code>\</code><code>linespread</code> work?</h3> +<h3>Why doesn’t <code>\</code><code>linespread</code> work?</h3> <p/>The command <code>\</code><code>linespread{</code><em>factor</em><code>}</code> is supposed to multiply the current <code>\</code><code>baselineskip</code> by <<i>factor</i>>; but, to all -appearances, it doesn’t. +appearances, it doesn’t. <p/>In fact, the command is equivalent to <code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{factor}</code>: written that -way, it somehow feels less surprising that the effect isn’t immediate. +way, it somehow feels less surprising that the effect isn’t immediate. The <code>\</code><code>baselinestretch</code> factor is only used when a font is selected; -a mere change of <code>\</code><code>baselinestretch</code> doesn’t change the font, any +a mere change of <code>\</code><code>baselinestretch</code> doesn’t change the font, any more than does the command -<code>\</code><code>fontsize{</code><em>size</em><code>}{</code><em>baselineskip</em><code>}</code> — you have to follow +<code>\</code><code>fontsize{</code><em>size</em><code>}{</code><em>baselineskip</em><code>}</code> — you have to follow either command with <code>\</code><code>selectfont</code>. So: <blockquote> <pre> @@ -27,11 +27,11 @@ or: </pre> </blockquote><p> Of course, a package such as <i>setspace</i>, whose job is to -manage the baseline, will deal with all this stuff — see -“<a href="FAQ-linespace.html">managing double-spaced documents</a>”. If +manage the baseline, will deal with all this stuff — see +“<a href="FAQ-linespace.html">managing double-spaced documents</a>”. If you want to avoid <i>setspace</i>, beware the behaviour of linespread changes within a paragraph: read -“<a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code> is a paragraph parameter</a>”. +“<a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code> is a paragraph parameter</a>”. <dl> <dt><tt><i>setspace.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linmacnames.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linmacnames.html index cb3a073af25..227f87446d3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linmacnames.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-linmacnames.html @@ -29,7 +29,7 @@ I said, ``\csname cul8r\endcsname''. <dt>Pro:<dd> No unexpected side effects <dt>Con:<dd> So verbose as to be unusable </dl> -<li> Define a “special-command generator”, and use the resulting +<li> Define a “special-command generator”, and use the resulting commands: <blockquote> @@ -46,10 +46,10 @@ I said, ``\csname cul8r\endcsname''. </blockquote><p> <dl> <dt>Pro:<dd> Straightforward to use, not too untidy - <dt>Con:<dd> It’s hardly doing what we set out to do (experts will - see that you are defining a macro, but others likely won’t) + <dt>Con:<dd> It’s hardly doing what we set out to do (experts will + see that you are defining a macro, but others likely won’t) </dl> -<li> Convince TeX that “<code>8</code>” is a letter: +<li> Convince TeX that “<code>8</code>” is a letter: <blockquote> <pre> \catcode`8 = 11 @@ -59,13 +59,13 @@ I said, ``\cul8r''. </blockquote><p> <dl> <dt>Pro:<dd> <code>\</code><code>cul8r</code> can be used directly - <dt>Con:<dd> Likely to break other uses of “<code>8</code>” (such as + <dt>Con:<dd> Likely to break other uses of “<code>8</code>” (such as numbers or dimensions; so <code>\</code><code>setlength{<code>\</code><code>paperwidth</code>}{8in}</code> tells us: <blockquote> <pre> ! Missing number, treated as zero. -<to be read again> +<to be read again> 8 </pre> </blockquote><p> @@ -76,7 +76,7 @@ I said, ``\cul8r''. most ordinary users are well advised not even to try such a technique. <li> Define a macro <code>\</code><code>cul</code> which must always be followed by - “<code>8r</code>”: + “<code>8r</code>”: <blockquote> <pre> \def\cul8r{Goodbye!} @@ -86,17 +86,17 @@ I said, ``\cul8r''. <dl> <dt>Pro:<dd> <code>\</code><code>cul8r</code> can be used directly <dt>Con #1:<dd> Breaks if <code>\</code><code>cul</code> is followed by anything other - than “<code>8r</code>”, with a confusing diagnostic — + than “<code>8r</code>”, with a confusing diagnostic — <code>\</code><code>cul99</code> produces: <blockquote> <pre> ! Use of \cul doesn't match its definition. -<*> \cul9 +<*> \cul9 9 </pre> </blockquote><p> - (which would confuse someone who hadn’t even realised there + (which would confuse someone who hadn’t even realised there <em>was</em> a definition of <code>\</code><code>cul</code> in the document). <dt>Con #2:<dd> Silently redefines existing <code>\</code><code>cul</code>, if any; as a result, the technique cannot be used to define both a @@ -104,15 +104,15 @@ I said, ``\cul8r''. document. </dl> </ol> -Technique 3 is in fact commonly used — in a limited form — within +Technique 3 is in fact commonly used — in a limited form — within most LaTeX packages and within LaTeX itself. The convention is to -use “<code>@</code>” within the names of internal macros to hide them +use “<code>@</code>” within the names of internal macros to hide them from the user and thereby prevent naming conflicts. To this end, -LaTeX automatically treats “<code>@</code>” as a letter while +LaTeX automatically treats “<code>@</code>” as a letter while processing classes and packages and as a non-letter while processing -the user’s document. The key to this technique is the separation: -internally a non-letter is used for macro names, and the user doesn’t -see anything of it, while the status remains “frozen” in all the +the user’s document. The key to this technique is the separation: +internally a non-letter is used for macro names, and the user doesn’t +see anything of it, while the status remains “frozen” in all the definitions created within the class or package. See <a href="FAQ-atsigns.html"><code>\</code><code>@</code> and <code>@</code> in macro names</a> for more information. @@ -128,10 +128,10 @@ I said, ``\later''. </pre> </blockquote><p> which works, but rather defeats the object of the exercise. -(<code>\</code><code>later</code> has the “frozen” catcode for ‘8’, even though the value -has reverted to normal by the time it’s used; note, also, the use of -the primitive command <code>\</code><code>gdef</code>, since <code>\</code><code>newcommand</code> can’t make a -macro that’s available outside the group.) +(<code>\</code><code>later</code> has the “frozen” catcode for ‘8’, even though the value +has reverted to normal by the time it’s used; note, also, the use of +the primitive command <code>\</code><code>gdef</code>, since <code>\</code><code>newcommand</code> can’t make a +macro that’s available outside the group.) <p/><em>Recommendation</em>: Either choose another mechanism (such as <code>\</code><code>DefineRemark</code> above), or choose another name for your macro, one that contains only ordinary letters. A common approach is to use diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html index 64685f090a7..de2552ec2c9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lit.html @@ -10,7 +10,7 @@ parse the file to produce either readable documentation or compilable source. The WEB style of literate programming was created by D. E. Knuth during the development of TeX. <p/> - The “<a href="FAQ-dtx.html">documented LaTeX</a>” style of programming + The “<a href="FAQ-dtx.html">documented LaTeX</a>” style of programming is regarded by some as a form of literate programming, though it only contains a subset of the constructs Knuth used. <p/>Discussion of literate programming is conducted in the newsgroup diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html index 021f1107ee7..33c22806f22 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-logos.html @@ -5,17 +5,17 @@ <p/>Knuth was making a particular point about the capabilities of TeX when he defined the logo. Unfortunately, many believe, he thereby opened floodgates to give the world a whole range of rather silly -‘bumpy road’ logos for TeX entities such as AMSTeX, PicTeX, +‘bumpy road’ logos for TeX entities such as AMSTeX, PicTeX, BibTeX, and so on, produced in a flurry of different fonts, sizes, -and baselines — indeed, everything one might hope to cause them to +and baselines — indeed, everything one might hope to cause them to obstruct the reading process. In particular, Lamport invented -LaTeX (silly enough in itself, with a raised small ‘A’ and a -lowered ‘E’) and marketing input from Addison-Wesley led to the even +LaTeX (silly enough in itself, with a raised small ‘A’ and a +lowered ‘E’) and marketing input from Addison-Wesley led to the even stranger current logo for LaTeX2e, which appends a lowered single-stroke Greek letter ε. -<p/>Sensible users don’t have to follow this stuff wherever it goes, +<p/>Sensible users don’t have to follow this stuff wherever it goes, but, for those who insist, a large collection of logos is defined in -the <i>texnames</i> package (but note that this set of macros isn’t +the <i>texnames</i> package (but note that this set of macros isn’t entirely reliable in LaTeX2e). The Metafont and MetaPost logos can be set in fonts that LaTeX2e knows about (so that they scale with the surrounding text) using the @@ -25,11 +25,11 @@ use of the Knuthian font for MetaPost (you might get - something like ‘META&nbsp;&nbsp;O&nbsp;&nbsp;T’). -You needn’t despair, however — most versions of the logo font + something like ‘META&nbsp;&nbsp;O&nbsp;&nbsp;T’). +You needn’t despair, however — most versions of the logo font distributed nowadays contain the missing letters, and the author -himself uses just ‘MetaPost’. -<p/>For those who don’t wish to acquire the ‘proper’ logos, the canonical +himself uses just ‘MetaPost’. +<p/>For those who don’t wish to acquire the ‘proper’ logos, the canonical thing to do is to say <code>AMS-</code><code>\</code><code>TeX</code> for AMSTeX, <code>Pic</code><code>\</code><code>TeX</code> for PicTeX, <code>Bib</code><code>\</code><code>TeX</code> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html index 636c3768988..add75e236e6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html @@ -3,11 +3,11 @@ </head><body> <h3>What is Lollipop?</h3> <p/>Lollipop is a macro package written by Victor Eijkhout; it was used in -the production of his book “<em>TeX by Topic</em>” (see +the production of his book “<em>TeX by Topic</em>” (see <a href="FAQ-ol-books.html">(La)TeX Tutorials</a>). The manual says of it: <blockquote> - Lollipop is ‘TeX made easy’. Lollipop is a macro package that + Lollipop is ‘TeX made easy’. Lollipop is a macro package that functions as a toolbox for writing TeX macros. It was my intention to make macro writing so easy that implementing a fully new layout in TeX would become a matter of less than an hour for @@ -19,10 +19,10 @@ it: used because adapting the layout is so much more easy with them than with traditional TeX macro packages. </blockquote><p> -<p/>The manual goes on to talk of ambitions to “capture some of the -LaTeX market share”; it’s a very witty package, but little sign of +<p/>The manual goes on to talk of ambitions to “capture some of the +LaTeX market share”; it’s a very witty package, but little sign of -it taking over from LaTeX is detectable… +it taking over from LaTeX is detectable… An article about Lollipop appeared in <i>TUGboat</i> 13(3). <dl> <dt><tt><i>Lollipop distribution</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/lollipop.zip">macros/lollipop</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html index eecefd00baa..bb98b0bf4d5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-longtab.html @@ -3,18 +3,18 @@ </head><body> <h3>Tables longer than a single page</h3> <p/>Tables are, by default, set entirely in boxes of their own: as a -result, they won’t split over a page boundary. Sadly, the world keeps +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 alignment +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> -file during later passes to get the setting “right” (the package +file during later passes to get the setting “right” (the package ordinarily manages to set tables in just two passes). Since the -package has overview of the whole table at the time it’s doing -“final” setting, the table is set “uniformly” over its entire +package has overview of the whole table at the time it’s doing +“final” setting, the table is set “uniformly” over its entire length, with columns matching on consecutive pages. <i>longtable</i> has a reputation for failing to interwork with other packages, but it does work with <i>colortbl</i>, and its @@ -22,44 +22,44 @@ author has provided the <i>ltxtable</i> package to provide (most of) the facilities of <i>tabularx</i> (see <a href="FAQ-fixwidtab.html">fixed-width tables</a>) for long tables: -beware of its rather curious usage constraints — each long table +beware of its rather curious usage constraints — each long table should be in a file of its own, and included by -<code>\</code><code>LTXtable{</code><em>width</em><code>}{</code><em>file</em><code>}</code>. Since <i>longtable</i>’s -multiple-page tables can’t possibly live inside floats, the package +<code>\</code><code>LTXtable{</code><em>width</em><code>}{</code><em>file</em><code>}</code>. Since <i>longtable</i>’s +multiple-page tables can’t possibly live inside floats, the package provides for captions within the <code>longtable</code> environment itself. <p/>A seeming alternative to <i>ltxtable</i> is <i>ltablex</i>; but it is outdated and not fully functional. Its worst problem is its strictly limited memory capacity (<i>longtable</i> is not so limited, at the cost of much complication in its code); -<i>ltablex</i> can only deal with relatively small tables, it doesn’t seem +<i>ltablex</i> can only deal with relatively small tables, it doesn’t seem likely that support is available; but its user interface is much -simpler than <i>ltxtable</i>, so if its restrictions aren’t a +simpler than <i>ltxtable</i>, so if its restrictions aren’t a problem for you, it may be worth a try. <p/>The <i>supertabular</i> package starts and stops a <code>tabular</code> environment for each page of the table. As a -result, each ‘page worth’ of the table is compiled independently, and +result, each ‘page worth’ of the table is compiled independently, and the widths of corresponding columns may differ on successive pages. -However, if the correspondence doesn’t matter, or if your columns are +However, if the correspondence doesn’t matter, or if your columns are fixed-width, <i>supertabular</i> has the great advantage of doing its job in a single run. <p/>Both <i>longtable</i> and <i>supertabular</i> allow definition of head- and footlines for the table; <i>longtable</i> allows distinction of the first and last head and foot. <p/>The <i>xtab</i> package fixes some infelicities of -<i>supertabular</i>, and also provides a “last head” facility -(though this, of course, destroys <i>supertabular</i>’s advantage +<i>supertabular</i>, and also provides a “last head” facility +(though this, of course, destroys <i>supertabular</i>’s advantage of operating in a single run). -<p/>The <i>stabular</i> package provides a simple-to-use “extension to -<code>tabular</code>” that allows it to typeset tables that run over -the end of a page; it also has usability extensions, but doesn’t have +<p/>The <i>stabular</i> package provides a simple-to-use “extension to +<code>tabular</code>” that allows it to typeset tables that run over +the end of a page; it also has usability extensions, but doesn’t have the head- and footline capabilities of the major packages. <p/>Documentation of <i>ltablex</i> is to be found in the package file. <dl> -<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/longtable.html">catalogue entry</a> <dt><tt><i>ltablex.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ltablex/ltablex.sty">macros/latex/contrib/ltablex/ltablex.sty</a> <dt><tt><i>ltxtable.sty</i></tt><dd>Generate by running <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/ltxtable.tex">macros/latex/contrib/carlisle/ltxtable.tex</a> -<dt><tt><i>stabular.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>) +<dt><tt><i>stabular.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/stabular.html">catalogue entry</a> <dt><tt><i>supertabular.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse the directory</a>) <dt><tt><i>xtab.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xtab.zip">macros/latex/contrib/xtab</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xtab/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html index 205177512e2..3b63a9cb118 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxabbrv.html @@ -1,24 +1,24 @@ <head> <title>UK TeX FAQ -- question label ltxabbrv</title> </head><body> -<h3>LaTeX internal “abbreviations”, etc.</h3> +<h3>LaTeX internal “abbreviations”, etc.</h3> <p/>In the deeps of time, when TeX first happened, computers had -extremely limited memory, and were (by today’s standards) painfully -slow. When LaTeX came along, things weren’t much better, and even +extremely limited memory, and were (by today’s standards) painfully +slow. When LaTeX came along, things weren’t much better, and even when LaTeX2e appeared, there was a strong imperative to save memory space (and to a lesser extent) CPU time. <p/>From the very earliest days, Knuth used shortcut macros to speed -things up. LaTeX, over the years, has extended Knuth’s list by a -substantial amount. An interesting feature of the “abbreviations” is +things up. LaTeX, over the years, has extended Knuth’s list by a +substantial amount. An interesting feature of the “abbreviations” is that on paper, they may look longer than the thing they stand for; -however, to (La)TeX they <em>feel</em> smaller… +however, to (La)TeX they <em>feel</em> smaller… <p/>The table at the end of this answer lists the commonest of these -“abbreviations”. It is not complete; as always, if the table -doesn’t help, try the LaTeX source. The table lists each -abbreviation’s <em>name</em> and its <em>value</em>, which provide most of -what a user needs to know. The table also lists the abbreviation’s +“abbreviations”. It is not complete; as always, if the table +doesn’t help, try the LaTeX source. The table lists each +abbreviation’s <em>name</em> and its <em>value</em>, which provide most of +what a user needs to know. The table also lists the abbreviation’s <em>type</em>, which is a trickier concept: if you need to know, the -only real confusion is that the abbreviations labelled ‘defn’ are +only real confusion is that the abbreviations labelled ‘defn’ are defined using an <code>\</code><code><em>xxx</code>def</em> command. <p/><table rules="groups" border="0" cellpadding="3"><tbody><tr><td> Name <td> Type <td> Value <tr><td> @@ -51,8 +51,8 @@ Name <td> Type <td> Value <tr><td> <code>\</code><code>@xxpt</code> <td> macro <td> 20.74 <tr><td> <code>\</code><code>@xxvpt</code> <td> macro <td> 24.88 <tr><td> </tbody><tbody><tr><td> -<code>\</code><code>@plus</code> <td> macro <td> “<code>plus</code>” <tr><td> -<code>\</code><code>@minus</code> <td> macro <td> “<code>minus</code>” <tr><td> +<code>\</code><code>@plus</code> <td> macro <td> “<code>plus</code>” <tr><td> +<code>\</code><code>@minus</code> <td> macro <td> “<code>minus</code>” <tr><td> </tbody></table> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html index b03e4365358..3acdd3a405d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxcmds.html @@ -3,8 +3,8 @@ </head><body> <h3>The definitions of LaTeX commands</h3> <p/>There are several reasons to want to know the definitions of LaTeX -commands: from the simplest “idle curiosity”, to the pressing need -to patch something to make it “work the way you want it”. None of +commands: from the simplest “idle curiosity”, to the pressing need +to patch something to make it “work the way you want it”. None of these are <em>pure</em> motives, but knowledge and expertise seldom arrive through the purest of motives. <p/>The simple answer is to try <code>\</code><code>show</code>, in a run of LaTeX that is @@ -13,47 +13,47 @@ taking commands from the terminal: <pre> *\makeatletter *\show\protected@edef -> \protected@edef=macro: -->\let \@@protect \protect +> \protected@edef=macro: +->\let \@@protect \protect \let \protect \@unexpandable@protect \afterassignment \restore@protect \edef . </pre> </blockquote><p> -(I’ve rearranged the output there, from the rather confused version +(I’ve rearranged the output there, from the rather confused version TeX itself produces.) We may perhaps, now, wonder about <code>\</code><code>@unexpandable@protect</code>: <blockquote> <pre> *\show\@unexpandable@protect -> \@unexpandable@protect=macro: -->\noexpand \protect \noexpand . +> \@unexpandable@protect=macro: +->\noexpand \protect \noexpand . </pre> </blockquote><p> -and we’re starting to see how one part of the <code>\</code><code>protect</code>ion +and we’re starting to see how one part of the <code>\</code><code>protect</code>ion mechanism works (one can probably fairly safely guess what <code>\</code><code>restore@protect</code> does). <p/>Many kernel commands are declared robust: <blockquote> <pre> *\show\texttt -> \texttt=macro: -->\protect \texttt . +> \texttt=macro: +->\protect \texttt . </pre> </blockquote><p> -so that <code>\</code><code>show</code> isn’t much help. Define a command <code>\</code><code>pshow</code> as +so that <code>\</code><code>show</code> isn’t much help. Define a command <code>\</code><code>pshow</code> as shown below, and use that instead: <blockquote> <pre> *\def\pshow#1{{\let\protect\show #1}} *\pshow\texttt -> \texttt =\long macro: -#1->\ifmmode \nfss@text {\ttfamily #1}% +> \texttt =\long macro: +#1->\ifmmode \nfss@text {\ttfamily #1}% \else \hmode@bgroup \text@command {#1}% \ttfamily \check@icl #1\check@icr \expandafter \egroup \fi . </pre> </blockquote><p> -Note that the command name that is protected is the ‘base’ command, +Note that the command name that is protected is the ‘base’ command, with a space appended. This is cryptically visible, in a couple of places above. (Again, the output has been sanitised.) <p/>If one has a malleable text editor, the same investigation may more @@ -66,24 +66,24 @@ you can refer to those instead. The LaTeX distribution includes a file <i>source2e.tex</i>, and most systems retain it, again in <i>tex/latex/base</i>. <i>Source2e.tex</i> may be processed to provide a complete source listing of the LaTeX kernel (in fact the -process isn’t entirely straightforward, but the file produces messages +process isn’t entirely straightforward, but the file produces messages advising you what to do). The result is a huge document, with a line-number index of control sequences the entire kernel and a separate index of changes recorded in each of the files since the LaTeX team took over. -<p/>The printed kernel is a nice thing to have, but it’s unwieldy and sits +<p/>The printed kernel is a nice thing to have, but it’s unwieldy and sits on my shelves, seldom used. One problem is that the comments are patchy: the different modules range from well and lucidly documented, through modules documented only through an automatic process that converted the documentation of the source of LaTeX 2.09, to modules that hardly had any useful documentation even in the LaTeX 2.09 original. <p/>In fact, each kernel module <code>.dtx</code> file will process separately -through LaTeX, so you don’t have to work with the whole of +through LaTeX, so you don’t have to work with the whole of <i>source2e</i>. You can easily determine which module defines the -macro you’re interested in: use your “malleable text editor” to find +macro you’re interested in: use your “malleable text editor” to find the definition in <i>latex.ltx</i>; then search backwards from that point for a line that starts -<code>%%% From File:</code> — that line +<code>%%% From File:</code> — that line tells you which <code>.dtx</code> file contains the definition you are interested in. Doing this for <code>\</code><code>protected@edef</code>, we find: <blockquote> @@ -94,10 +94,10 @@ in. Doing this for <code>\</code><code>protected@edef</code>, we find: When we come to look at it, <i>ltdefns.dtx</i> proves to contain quite a dissertation on the methods of handling <code>\</code><code>protect</code>ion; it also contains some automatically-converted LaTeX 2.09 documentation. -<p/>And of course, the kernel isn’t all of LaTeX: your command may be -defined in one of LaTeX’s class or package files. For example, we +<p/>And of course, the kernel isn’t all of LaTeX: your command may be +defined in one of LaTeX’s class or package files. For example, we find a definition of <code>\</code><code>thebibliography</code> in <i>article</i>, but -there’s no <i>article.dtx</i>. Some such files are generated from +there’s no <i>article.dtx</i>. Some such files are generated from parts of the kernel, some from other files in the distribution. You find which by looking at the start of the file: in <i>article.cls</i>, we find: diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html index 0e3d777727f..175a62e38dd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ltxhash.html @@ -27,10 +27,10 @@ followed by a call: \cmdinvoke{abc}{joy} </pre> </blockquote><p> -typesets “joy, oh joy!”, but defines a command <code>\</code><code>ghi</code> that takes +typesets “joy, oh joy!”, but defines a command <code>\</code><code>ghi</code> that takes one parameter, which it ignores; <code>\</code><code>ghi{gloom}</code> will expand to -“gloom, oh joy!”, which is presumably not what was expected. -<p/>And (as you will probably guess, if you’ve read the earlier question) +“gloom, oh joy!”, which is presumably not what was expected. +<p/>And (as you will probably guess, if you’ve read the earlier question) the definition: <blockquote> <pre> @@ -40,7 +40,7 @@ the definition: </pre> </blockquote><p> does what is required, and <code>\</code><code>ghi{gloom}</code> will expand to -“gloom, oh gloom!”, whatever the argument to <code>\</code><code>abc</code>. +“gloom, oh gloom!”, whatever the argument to <code>\</code><code>abc</code>. <p/>The doubling is needed whether or not the enclosing command has an argument, so: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html index ccf0a5bf62c..a261c0d48a3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-luatex.html @@ -3,7 +3,7 @@ </head><body> <h3>PDFTeX and LuaTeX</h3> <p/>As is said elsewhere in these FAQs, development of -<a href="FAQ-whatpdftex.html">PDFTeX</a> is “in essence” complete — +<a href="FAQ-whatpdftex.html">PDFTeX</a> is “in essence” complete — no new facilities are being developed. The PDFTeX team has announced that they have frozen PDFTeX in its current state (version 1.49.10), and that nothing but bug corrections will be @@ -16,11 +16,11 @@ into other applications. LuaTeX consists of a TeX-like engine with a <i>lua</i> interpreter built into it; the <i>lua</i> interpreter has access to many of the data structures used for typesetting, and the user may also interpolate chunks of -<i>lua</i> code into their (La)TeX macros, or as ‘call-backs’ +<i>lua</i> code into their (La)TeX macros, or as ‘call-backs’ for use when the TeX-like engine does certain operations. -<p/>This arrangement offers the prospect of a “semi-soft” typesetting +<p/>This arrangement offers the prospect of a “semi-soft” typesetting engine: it will have its basic behaviour, but the user gets to -redefine functionality if an idea occurs — there will be no need to +redefine functionality if an idea occurs — there will be no need to persuade the world first, and then find a willing developer to work on the sources of of the distribution. <p/>The <a href="http://www.luatex.org/">LuaTeX project</a> is (with monetary @@ -28,15 +28,16 @@ support from various sources) pursuing avenues that many of the other current projects have in their sights, notably Unicode character representations and support for OpenType fonts. The intention is to integrate the extensions pioneered by <a href="FAQ-omegaleph.html">Aleph</a>. -<p/>Version 0.50.0 of LuaTeX is intended to at least demonstrate the final -functionality; it was released near the end of December 2009. Much -work remains to be done, and this remains a beta-release. +<p/>The current version (0.60.0, in April 2010) of LuaTeX is supposed +at least to demonstrate the final functionality. This stability was +declared with version 0.50.0, released near the end of December 2009. +Much work remains to be done, and this remains a beta-release. TeX Live 2009 incorporates (at the time of writing) LuaTeX -version 0.44.0, but the latest MiKTeX (version 2.8) still doesn’t +version 0.44.0, but the latest MiKTeX (version 2.8) still doesn’t offer it. -<p/>ConTeXt ‘Mark 4’ can already make use of LuaTeX; much of its -code already appears in two forms — a TeX-based version -(<code>.mkii</code>) and a ‘<code>.mkiv</code>’ version. LaTeX is also +<p/>ConTeXt ‘Mark 4’ can already make use of LuaTeX; much of its +code already appears in two forms — a TeX-based version +(<code>.mkii</code>) and a ‘<code>.mkiv</code>’ version. LaTeX is also steadily acquiring macro packages in support of its use. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html index f85050a5024..3e4a94ef4dd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mailliststar.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label maillists*</title> </head><body> <h3>Specialist mailing lists</h3> -<p/>The previous question, “<a href="FAQ-gethelp.html">getting help</a>”, talked of +<p/>The previous question, “<a href="FAQ-gethelp.html">getting help</a>”, talked of the two major forums in which (La)TeX, Metafont and MetaPost are -discussed; however, these aren’t the only ones available. +discussed; however, these aren’t the only ones available. <p/>The TUG web site offers many mailing lists other than just <code>texhax</code> via its <a href="http://tug.org/mailman/listinfo">mail list management page</a>. @@ -17,8 +17,8 @@ subscribe metafont </pre> </blockquote><p> to <a href="mailto:sympa@ens.fr"><i>sympa@ens.fr</i></a> -<p/>(Note that there’s also a MetaPost-specific mailing list available via the -TUG list server; in fact there’s little danger of becoming confused +<p/>(Note that there’s also a MetaPost-specific mailing list available via the +TUG list server; in fact there’s little danger of becoming confused by subscribing to both.) <p/>Announcements of TeX-related installations on the CTAN archives are sent to the mailing list <code>ctan-ann</code>. Subscribe diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html index a82c700079c..030afa9e158 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-make.html @@ -4,9 +4,9 @@ <h3>Makefiles for LaTeX documents</h3> <p/>LaTeX is a tricky beast for running <i>make</i> on: the need to instruct LaTeX to run several times for essentially different -reasons (for example, “get the table of contents stable”, “get the -labels stable”, “add the bibliography”, “add the index”) is -actually rather difficult to express in the ‘ordinary’ sort of +reasons (for example, “get the table of contents stable”, “get the +labels stable”, “add the bibliography”, “add the index”) is +actually rather difficult to express in the ‘ordinary’ sort of dependency graph that one constructs for <i>make</i>. <p/>The <i>latex-make</i> package offers help with this task (far more sophisticated techniques than in the FAQ building script); it @@ -15,35 +15,35 @@ looks good, but reports of its use (other than by its author) are scarce. was <i>latexmk</i>, which is a <i>Perl</i> script that analyses your LaTeX source for its dependencies, runs BibTeX or <i>makeindex</i> as and when it notices that those -programs’ input (parts of the <code>.aux</code> file, or the +programs’ input (parts of the <code>.aux</code> file, or the <code>.idx</code> file, respectively) has changed, and so on. <i>Latexmk</i> is a fine solution (and was used in generating printable versions of these FAQs for a long time); it has recently been upgraded and has many bells and whistles that allow it to operate as if it were a poor -man’s WYSIWYG system. +man’s WYSIWYG system. <p/>Apparently along the same lines, is AutoLaTeX. The <i>README</i> of the distribution is actual a Unix-type man-page output, and shows great attention to the details of the document production process. <p/>The <i>mk</i> (also, apparently, known as <i>latex_maker</i>) is a Ruby script for the task in hand; it works well with another of -the author’s scripts script called <i>vpp</i> (View and Print +the author’s scripts script called <i>vpp</i> (View and Print PostScript/PDF). -<p/>Windows users of the MiKTeX system may use that system’s +<p/>Windows users of the MiKTeX system may use that system’s <i>texify</i> application. <i>Texify</i> deals with basic LaTeX features, including generating a bibliography and an index; it makes no claim to deal with other things (such as multiple bibliographies or indexes, or lists of terminology, etc.), which AutoLaTeX can be configured to process. <p/>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a similar -utility called <i>texi2dvi</i>, which is capable of “converting” +utility called <i>texi2dvi</i>, which is capable of “converting” either LaTeX or <i>texinfo</i> files into DVI (or into PDF, using PDFTeX). <p/>A later contribution is the bundle <i>latexmake</i>, which offers a set of <i>make</i> rules that invoke <i>texi2dvi</i> as necessary. <p/>The curious may examine the rules employed to run the present -FAQ through LaTeX: we don’t present them as a complete +FAQ through LaTeX: we don’t present them as a complete solution, but some of the tricks employed are surely re-usable. <dl> <dt><tt><i>AutoLaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/autolatex.zip">support/autolatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/autolatex/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html index 1a58a6828d2..ed7d5281e5f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makebib.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label makebib</title> </head><body> <h3>Reconstructing <code>.bib</code> files</h3> -<p/>Perhaps you’ve lost the <code>.bib</code> file you generated your document from, -or have been sent a document without one. Or even, you’ve realised +<p/>Perhaps you’ve lost the <code>.bib</code> file you generated your document from, +or have been sent a document without one. Or even, you’ve realised the error of building a substantial document without the benefit of -BibTeX… +BibTeX… <p/>The <i>Perl</i> script, <i>tex2bib</i> makes a reasonable job of regenerating <code>.bib</code> files from <code>thebibliography</code> environments, provided that the original (whether automatically or -manually generated) doesn’t deviate too far from the “standard” +manually generated) doesn’t deviate too far from the “standard” styles. <p/>You are well-advised to check the output of the script. While it will not usually destroy information, it can quite reasonably mislabel it. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html index 4d1aa7df88a..e520837782a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-makeindex.html @@ -11,7 +11,7 @@ post-processing program is used to sort the output of one TeX run, to be included into the document at the next run. <p/>The following programs are available: <dl> -<dt>makeindex<dd> Comes with most distributions — a good workhorse, +<dt>makeindex<dd> Comes with most distributions — a good workhorse, but is not well-arranged to deal with other sort orders than the canonical ASCII ordering. <p/> The <i>makeindex</i> documentation is a good source of @@ -33,7 +33,7 @@ to be included into the document at the next run. multi-language version of <i>makeindex</i>. It is designed to be a successor to <i>makeindex</i>, by a team that included the then-current maintainer of <i>makeindex</i>. It successfully - addresses many of <i>makeindex</i>’s shortcomings, including + addresses many of <i>makeindex</i>’s shortcomings, including difficulties with collation order in different languages, and it is highly flexible. Sadly, its take-up is proving rather slow. </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html index 25dc921425f..2cf76a90730 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html @@ -2,60 +2,60 @@ <title>UK TeX FAQ -- question label man-latex</title> </head><body> <h3>Online introductions: LaTeX</h3> -<p/>A pleasing little document, “Getting something out of LaTeX” is -designed to give a feel of LaTeX to someone who’s never used it at -all. It’s not a tutorial, merely helps the user to decide whether to -go on to a tutorial, and to ‘real’ use of LaTeX. -<p/>Tobias Oetiker’s ‘(Not so) Short Introduction to LaTeX2e’, is +<p/>A pleasing little document, “Getting something out of LaTeX” is +designed to give a feel of LaTeX to someone who’s never used it at +all. It’s not a tutorial, merely helps the user to decide whether to +go on to a tutorial, and to ‘real’ use of LaTeX. +<p/>Tobias Oetiker’s ‘(Not so) Short Introduction to LaTeX2e’, is regularly updated, as people suggest better ways of explaining things, etc. The introduction is available on CTAN, together with translations into a rather large set of languages. -<p/>Peter Flynn’s “Beginner’s LaTeX” (which started life as course +<p/>Peter Flynn’s “Beginner’s LaTeX” (which started life as course material) is a pleasing read. A complete copy may be found on CTAN, but it may also be browsed over the web (<a href="http://mirrors.ctan.org/info/beginlatex/html/">http://mirrors.ctan.org/info/beginlatex/html/</a>). -<p/>Harvey Greenberg’s ‘Simplified Introduction to LaTeX’ was written +<p/>Harvey Greenberg’s ‘Simplified Introduction to LaTeX’ was written for a lecture course, and is also available on CTAN (in PostScript only, unfortunately). -<p/>The fourth edition of George Grätzer’s book “Math into LaTeX” -contains a “short course” in LaTeX itself, and that course has +<p/>The fourth edition of George Grätzer’s book “Math into LaTeX” +contains a “short course” in LaTeX itself, and that course has been made publicly available on CTAN. -<p/>Philip Hirschhorn’s “Getting up and running with AMSLaTeX” has a +<p/>Philip Hirschhorn’s “Getting up and running with AMSLaTeX” has a brief introduction to LaTeX itself, followed by a substantial introduction to the use of the AMS classes and the <i>amsmath</i> package and other things that are potentially of interest to those writing documents containing mathematics. -<p/>Edith Hodgen’s +<p/>Edith Hodgen’s <a href="http://www.mcs.vuw.ac.nz/~david/latex/notes.pdf">LaTeX, a Braindump</a> -starts you from the ground up — giving a basic tutorial in the use -of <i>Linux</i> to get you going (rather a large file…). -Its parent site, David Friggens’ +starts you from the ground up — giving a basic tutorial in the use +of <i>Linux</i> to get you going (rather a large file…). +Its parent site, David Friggens’ <a href="http://www.mcs.vuw.ac.nz/~david/latex/">documentation page</a> is a useful collection of links in itself. <p/> -<a href="http://www.andy-roberts.net/misc/latex/">Andy Roberts’ introductory material</a> +<a href="http://www.andy-roberts.net/misc/latex/">Andy Roberts’ introductory material</a> is a pleasing short introduction to the use of (La)TeX; some of the slides for <em>actual</em> tutorials are to be found on the page, as well. -<p/>Chris Harrison’s +<p/>Chris Harrison’s <a href="http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html">TeX book</a> presents basic LaTeX with useful hints for extensions -<p/>Nicola Talbot’s +<p/>Nicola Talbot’s <a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/">LaTeX for complete novices</a> does what it claims: the author teaches LaTeX at the University of -East Anglia. That is one of several of Nicola’s +East Anglia. That is one of several of Nicola’s <a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/">introductory tutorials</a>, which include exercises (with solutions). Other tutorials include those for writing theses/dissertations with LaTeX, and for using LaTeX in administrative work. (The page seems to be an adjunct to -her LaTeX courses — fortunate people, the people of UEA!). +her LaTeX courses — fortunate people, the people of UEA!). <p/>An interesting (and practical) tutorial about what <em>not</em> to do is -<i>l2tabu</i>, or “A list of sins of LaTeX2e users” by Mark -Trettin, translated into English by Jürgen Fenn. The +<i>l2tabu</i>, or “A list of sins of LaTeX2e users” by Mark +Trettin, translated into English by Jürgen Fenn. The tutorial is available from CTAN as a PDF file (though the source is also available). <dl> -<dt><tt><i>Beginner’s LaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/beginlatex-3.6.pdf">info/beginlatex/beginlatex-3.6.pdf</a> +<dt><tt><i>Beginner’s LaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/beginlatex-3.6.pdf">info/beginlatex/beginlatex-3.6.pdf</a> <dt><tt><i>First LaTeX document</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/first-latex-doc.zip">info/first-latex-doc</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/first-latex-doc/">browse the directory</a>) <dt><tt><i>Getting up and running with AMSLaTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/amslatex/primer.zip">info/amslatex/primer</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/amslatex/primer/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html index 20699b466ce..0c92d44cef9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-tex.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label man-tex</title> </head><body> <h3>Online introductions: Plain TeX</h3> -<p/>Michael Doob’s splendid ‘Gentle Introduction’ to Plain TeX +<p/>Michael Doob’s splendid ‘Gentle Introduction’ to Plain TeX (available on CTAN) has been stable for a very long time. -<p/>Another recommendable document is D. R. Wilkins ‘Getting started with TeX’, +<p/>Another recommendable document is D. R. Wilkins ‘Getting started with TeX’, available on the web at <a href="http://www.ntg.nl/doc/wilkins/pllong.pdf">http://www.ntg.nl/doc/wilkins/pllong.pdf</a> <dl> <dt><tt><i>Gentle Introduction</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/gentle/gentle.pdf">info/gentle/gentle.pdf</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html index 8828376fbf1..969c01a8056 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manyauthor.html @@ -1,10 +1,10 @@ <head> <title>UK TeX FAQ -- question label manyauthor</title> </head><body> -<h3>BibTeX doesn’t understand lists of names</h3> -<p/>BibTeX has a strict syntax for lists of authors’ (or editors’) +<h3>BibTeX doesn’t understand lists of names</h3> +<p/>BibTeX has a strict syntax for lists of authors’ (or editors’) names in the BibTeX data file; if you write the list of names in a -“natural”-seeming way, the chances are you will confuse BibTeX, +“natural”-seeming way, the chances are you will confuse BibTeX, and the output produced will be quite different from what you had hoped. <p/>Names should be expressed in one of the forms @@ -15,25 +15,25 @@ Last, First Last, Suffix, First </pre> </blockquote><p> -and lists of names should be separated with “<code>and</code>”. +and lists of names should be separated with “<code>and</code>”. For example: <blockquote> <pre> -AUTHOR = {Fred Q. Bloggs, John P. Doe & +AUTHOR = {Fred Q. Bloggs, John P. Doe & Another Idiot} </pre> </blockquote><p> falls foul of two of the above rules: a syntactically significant -comma appears in an incorrect place, and ‘<code>\</code><code>&</code>’ is being used as a +comma appears in an incorrect place, and ‘<code>\</code><code>&</code>’ is being used as a name separator. The output of the above might be something like: <blockquote> <pre> -John P. Doe & Another Idiot Fred Q. Bloggs +John P. Doe & Another Idiot Fred Q. Bloggs </pre> </blockquote><p> -because “John P. Doe & Another Idiot has become the ‘first name’, -while “Fred Q. Bloggs” has become the ‘last name’ of a single +because “John P. Doe & Another Idiot has become the ‘first name’, +while “Fred Q. Bloggs” has become the ‘last name’ of a single person. The example should have been written: <blockquote> @@ -44,8 +44,8 @@ AUTHOR = {Fred Q. Bloggs and John P. Doe and </blockquote><p> Some bibliography styles implement clever acrobatics with very long author lists. You can force truncation by using the pseudo-name -“<code>others</code>”, which will usually translate to something like -“<em>et al</em>” in the typeset output. So, if Mr. Bloggs wanted to +“<code>others</code>”, which will usually translate to something like +“<em>et al</em>” in the typeset output. So, if Mr. Bloggs wanted to distract attention from his co-authors, he would write: <blockquote> <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html index 25be7aef46a..915bdd80b7c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-manymathalph.html @@ -5,21 +5,21 @@ <p/>TeX mathematics is one of its most impressive features, yet the internal structure of the mechanism that produces it is painfully complicated and (in some senses) pathetically limited. One area of -limitation is that one is only allowed 16 ”maths alphabets” +limitation is that one is only allowed 16 ”maths alphabets” <p/>LaTeX offers the user quite a lot of flexibility with allocating maths alphabets, but few people use the flexibility directly. Nevertheless, there are many packages that provide symbols, or that manipulate them, which allocate themselves one or more maths alphabet. -<p/>If you can’t afford to drop any of these packages, there’s -still hope if you’re using the <i>bm</i> package to support +<p/>If you can’t afford to drop any of these packages, there’s +still hope if you’re using the <i>bm</i> package to support <a href="FAQ-boldgreek.html">bold maths</a>: <i>bm</i> is capable of gobbling alphabets as if there is no tomorrow. The package defines two limiter commands: <code>\</code><code>bmmax</code> (for <em>bold</em> symbols; default 4) and <code>\</code><code>hmmax</code> (for <em>heavy</em> symbols, if you have them; default 3), which control the number of alphabets to be used. <p/>Any reduction of the <code>\</code><code><em>xx</code>max</em> variables will slow -<i>bm</i> down — but that’s surely better than the document not -running at all. So unless you’re using maths fonts (such as +<i>bm</i> down — but that’s surely better than the document not +running at all. So unless you’re using maths fonts (such as <i>Mathtime Plus</i>) that feature a heavy symbol weight, suppress all use of heavy families by <blockquote> @@ -35,7 +35,7 @@ and then steadily reduce the bold families, starting with </blockquote><p> until (with a bit of luck) the error goes away. <dl> -<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/bm.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html index 55669eb2d3c..01b829b4be1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginmanual.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label marginmanual</title> </head><body> -<h3>How to set up page layout “by hand”</h3> -<p/>So you’re eager to do it yourself, notwithstanding the cautions +<h3>How to set up page layout “by hand”</h3> +<p/>So you’re eager to do it yourself, notwithstanding the cautions - outlined in “<a href="FAQ-changemargin.html">changing margins</a>”. -<p/>It’s important that you first start by familiarising yourself -with LaTeX’s page layout parameters. For example, see section C.5.3 of the + outlined in “<a href="FAQ-changemargin.html">changing margins</a>”. +<p/>It’s important that you first start by familiarising yourself +with LaTeX’s page layout parameters. For example, see section C.5.3 of the LaTeX manual (pp. 181-182), or corresponding sections in many of the other good LaTeX manuals (see <a href="FAQ-books.html">LaTeX books</a>). <p/>LaTeX controls the page layout with a number of parameters, which @@ -22,19 +22,19 @@ layout, with the dimensions (but not their interrelationships) shown. should be set to fit a whole number of text lines (in terms of multiples of <code>\</code><code>baselinskip</code>), and the width should be constrained by the number of characters per line, as mentioned in -“<a href="FAQ-changemargin.html">changing margins</a>”. +“<a href="FAQ-changemargin.html">changing margins</a>”. <p/>Margins are controlled by two parameters: <code>\</code><code>oddsidemargin</code> and <code>\</code><code>evensidemargin</code>, whose names come from the convention that -odd-numbered pages appear on the right-hand side (‘recto’) of a +odd-numbered pages appear on the right-hand side (‘recto’) of a two-page spread and even-numbered pages on the left-hand side -(‘verso’). Both parameters actually refer to the left-hand margin of +(‘verso’). Both parameters actually refer to the left-hand margin of the relevant pages; in each case the right-hand margin is specified by implication, from the value of <code>\</code><code>textwidth</code> and the width of the paper. (In a one-sided document, which is the default in many classes, including the standard <i>article</i> and <i>report</i> classes, <code>\</code><code>oddsidemargin</code> stands for both.) <p/>The -“origin” (the zero position) on the page is one inch from the top of +“origin” (the zero position) on the page is one inch from the top of the paper and one inch from the left side; positive horizontal measurements extend right across the page, and positive vertical measurements extend down the page. Thus, the parameters diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html index b0b9d1769d3..735ff13d8d0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginparside.html @@ -2,24 +2,24 @@ <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 “analogous” 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 +moment’s thought shows that a marginal note on the left needs to be typeset differently from a marginal note on the right. The LaTeX <code>\</code><code>marginpar</code> command therefore takes two arguments in a <code>twoside</code> documents: <code>\</code><code>marginpar[</code><em>left text</em><code>]{</code><em>right text</em><code>}</code>. LaTeX uses the -“obvious” test to +“obvious” test to get the <code>\</code><code>marginpar</code>s in the correct margin, but a booby-trap arises because TeX runs its page maker asynchronously. If a <code>\</code><code>marginpar</code> is processed while page n is being built, but -doesn’t get used until page n+1, then the <code>\</code><code>marginpar</code> will turn +doesn’t get used until page n+1, then the <code>\</code><code>marginpar</code> will turn up on the wrong side of the page. This is an instance of a general problem: see -“<a href="FAQ-oddpage.html">finding if you’re on an odd or an even page</a>”. -<p/>The solution to the problem is for LaTeX to ‘remember’ which side +“<a href="FAQ-oddpage.html">finding if you’re on an odd or an even page</a>”. +<p/>The solution to the problem is for LaTeX to ‘remember’ which side of the page each <code>\</code><code>marginpar</code> <em>should</em> be on. The <i>mparhack</i> package does this, using label-like marks stored in the <code>.aux</code> file; the <i>memoir</i> class does likewise. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html index 0d497fe6db9..b7edb18c852 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-marginpkgs.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label marginpkgs</title> </head><body> <h3>Packages to set up page designs</h3> -<p/>The ‘ultimate’ tool for adjusting the dimensions and position of the +<p/>The ‘ultimate’ tool for adjusting the dimensions and position of the printed material on the page is the <i>geometry</i> package; a very wide range of adjustments of the layout may be relatively straightforwardly programmed, and package documentation is good and @@ -21,9 +21,9 @@ two-sided printing. <dl> <dt><tt><i>geometry.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse the directory</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) -<dt><tt><i>layout.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>layout.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/layout.html">catalogue entry</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) -<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) +<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/typearea.html">catalogue entry</a> <dt><tt><i>vmargin.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin.zip">macros/latex/contrib/vmargin</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html index 8f9d04cf2cd..2d94c31c415 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-matchbrak.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label matchbrak</title> </head><body> -<h3>My brackets don’t match</h3> +<h3>My brackets don’t match</h3> <p/>(La)TeX has a low-level mechanism for matching braces in document text. This means you can type something like: <blockquote> @@ -11,7 +11,7 @@ text. This means you can type something like: </blockquote><p> and know that the first brace (for the argument of <code>\</code><code>section</code>) will be matched with the last brace, and the internal pair of braces (for -the argument of <code>\</code><code>emph</code>) will be matched with each other. It’s all +the argument of <code>\</code><code>emph</code>) will be matched with each other. It’s all very simple. <p/>However, LaTeX has a convention of enclosing optional arguments in brackets, as in: @@ -28,11 +28,11 @@ straightforward-looking usages like: \section[All [OK] now]{All \emph{OK} now.} </pre> </blockquote><p> -aren’t OK at all — the optional argument comes to consist of -“All [OK”, and <code>\</code><code>section</code> takes the single character “n” (of -the first “now”) as its argument. -<p/>Fortunately, TeX’s scanning mechanisms helps us by accepting the -syntax “<code>{]}</code>” to ‘hide’ the closing bracket from the +aren’t OK at all — the optional argument comes to consist of +“All [OK”, and <code>\</code><code>section</code> takes the single character “n” (of +the first “now”) as its argument. +<p/>Fortunately, TeX’s scanning mechanisms helps us by accepting the +syntax “<code>{]}</code>” to ‘hide’ the closing bracket from the scanning mechanism that LaTeX uses. In practice, the commonest way to use this facility is: <blockquote> @@ -40,7 +40,7 @@ to use this facility is: \section[All {[OK]} now]{All \emph{OK} now.} </pre> </blockquote><p> -since bracing the bracket on its own “looks odd”. +since bracing the bracket on its own “looks odd”. <p/>LaTeX has another argument syntax, even less regular, where the argument is enclosed in parentheses, as in: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html index 59dbe7d7559..d9154f68313 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathlips.html @@ -11,10 +11,10 @@ the <i>graphics</i> package, one can change the slope of the $ ... \reflectbox{$\ddots$} ... $ </pre> While this works, it is not a recommended way of achieving the desired -result (see below). Moreover, LaTeX’s range is not adequate to -everyone’s requirements, and at least three packages provide +result (see below). Moreover, LaTeX’s range is not adequate to +everyone’s requirements, and at least three packages provide extensions to the set. -<p/>The AMSLaTeX bundle provides a range of “semantically-named” +<p/>The AMSLaTeX bundle provides a range of “semantically-named” ellipses, for use in different situations: <code>\</code><code>dotsb</code> for use between pairs of binary operators, <code>\</code><code>dotsc</code> for use between pairs of commas, and so on. @@ -24,12 +24,12 @@ The <i>yhmath</i> package comes with a rather interesting font that extends the standard <i>cmex</i>; details are in the documentation. The disadvantage of this setup is, that although <code>\</code><code>adots</code> is merely a macro, the package tries to load its own font and produces a -“missing font” substitution warning message if you haven’t installed +“missing font” substitution warning message if you haven’t installed the font. <p/>The <i>mathdots</i> package (besides fixing up the behaviour of (La)TeX <code>\</code><code>ddots</code> and <code>\</code><code>vdots</code> when the font size changes) -provides an “inverse diagonal” ellipsis <code>\</code><code>iddots</code> (doing the same -job as <i>yhmath</i>’s <code>\</code><code>adots</code>, but better). +provides an “inverse diagonal” ellipsis <code>\</code><code>iddots</code> (doing the same +job as <i>yhmath</i>’s <code>\</code><code>adots</code>, but better). <p/>Documentation of <i>yhmath</i> appears, processed, in the distribution (thus saving you the bother of installing the package before being able to read the documentation). Documentation of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html index 37e31f5eb84..bf2fa9a64c3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html @@ -3,7 +3,7 @@ </head><body> <h3>Future WWW technologies and (La)TeX</h3> <p/>An earlier answer -(<a href="FAQ-LaTeX2HTML.html">“converting to HTML”</a>) +(<a href="FAQ-LaTeX2HTML.html">“converting to HTML”</a>) addresses the issue of converting existing (La)TeX documents for viewing on the Web as HTML. All the present techniques are somewhat flawed: the answer explains why. @@ -39,11 +39,11 @@ support for new Web standards. has had major browser support since 2002 with richness of mathematical content for online purposes approaching that of TeX for print. Browser support for MathML is provided by <i>amaya</i>, the - ‘Open Source’ browser <i>mozilla</i> (and its derivatives + ‘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 plug-in such as <i>MathPlayer</i>. - There’s evidence that (La)TeX users are starting to use such + There’s evidence that (La)TeX users are starting to use such browsers. Some believe that XHTML+MathML now provides better online viewing than PDF. Work to produce XHTML+MathML is well advanced in both the @@ -55,10 +55,10 @@ support for new Web standards. the <a href="http://www.albany.edu/~hammond/gellmu/"><em>GELLMU</em> Project</a>. Its <em>article</em> XML document type, which has a markup vocabulary close to LaTeX that can be edited using LaTeX-like markup - (even though it is not LaTeX — so far), comes with translators + (even though it is not LaTeX — so far), comes with translators that make both PDF (via <em>pdflatex</em>) and XHTML+MathML. Such an approach avoids the inherent - limitations of the “traditional” (La)TeX translation processes, + limitations of the “traditional” (La)TeX translation processes, which have traps that can be sprung by unfettered use of (La)TeX markup. <dt>Graphics<dd> @@ -73,28 +73,28 @@ support for new Web standards. has appeared, and has been reported to be useful for SVG-related work in at least one TeX-related project. Be aware that the developers of <i>Inkscape</i> have no illusions - about being able to replace commercial software, yet… + about being able to replace commercial software, yet… <dt>Direct use of TeX markup<dd> Some time back, IBM developed a browser plug-in called TechExplorer, which would display (La)TeX documents direct in a browser. Over the years, it developed into a MathML browser - plug-in, while still retaining its (La)TeX abilities, but it’s now + plug-in, while still retaining its (La)TeX abilities, but it’s now distributed (free for Linux and Windows platforms) by <a href="http://www.integretechpub.com/">Integre Technical Publishing</a>. <p/> The disadvantage of the TechExplorer approach is that it places the onus on the browser user; and however technically proficient - <em>you</em> are, it’s never safe to assume too much of your readers. + <em>you</em> are, it’s never safe to assume too much of your readers. An interesting alternative is <a href="http://www.forkosh.com/mathtex.html">MathTeX</a>, which sits on your server as a CGI script, and you use it to include your TeX, in your HTML, as if it were an image: <blockquote> <pre> -<img src="/cgi-bin/mimetex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt"> +<img src="/cgi-bin/mimetex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt"> </pre> </blockquote><p> -(<i>Mathtex</i> supersedes the author’s earlier <i>mimetex</i>.) +(<i>Mathtex</i> supersedes the author’s earlier <i>mimetex</i>.) </dl> <dl> <dt><tt><i>GELLMU</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/gellmu.zip">support/gellmu</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/gellmu/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html index 7baff8732b4..d44d7ad88bb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathonlyref.html @@ -6,20 +6,20 @@ every equation; there is also a school of thought that claims that there should be numbers everywhere, in case some reader wants to make reference an equation to which the author made no cross-reference. -<p/>If you hold to the “only cross-referenced” school of thought, you +<p/>If you hold to the “only cross-referenced” school of thought, you can (using the <code>\</code><code>nonumber</code> command on the relevant equations, or by using the AMSLaTeX unnumbered environments such as <code>equation*</code>) mark those of your equations to which you make no reference. In a long or complex paper, this procedure could well become deeply tedious. -<p/>Fortunately, help is at hand: the <i>mh</i> bundle’s -<i>mathtools</i> package offers a ‘<code>showonlyrefs</code>’ -switch through its <code>\</code><code>mathtoolsset</code> command; when that’s in +<p/>Fortunately, help is at hand: the <i>mh</i> bundle’s +<i>mathtools</i> package offers a ‘<code>showonlyrefs</code>’ +switch through its <code>\</code><code>mathtoolsset</code> command; when that’s in operation, only those equations to which you make reference will be -numbered in the final output. See the package’s documentation for +numbered in the final output. See the package’s documentation for details of how to make references when the switch is in effect. <dl> -<dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse the directory</a>) +<dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mathtools.html">catalogue entry</a> </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html index a39320aab6c..a16b59b0ee6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathsize.html @@ -5,23 +5,23 @@ <p/>In Plain TeX, when you introduce a new font size you must also declare what size fonts are to be used in mathematics with it. This is done by declaring <code>\</code><code>textfont</code>, <code>\</code><code>scriptfont</code> and -<code>\</code><code>scriptscriptfont</code> for the maths families you’re using; all such +<code>\</code><code>scriptscriptfont</code> for the maths families you’re using; all such things are described in chapter 17 of the <a href="FAQ-books.html">TeXbook</a> and in other books and <a href="FAQ-man-tex.html">tutorials</a> that discuss Plain TeX in sufficient detail. <p/>In LaTeX, of course, all this stuff is automated: there is a scheme that, for each (text) font size, determines what maths font sizes are -to be used. The scheme first checks a set of “known” text sizes, +to be used. The scheme first checks a set of “known” text sizes, for each of which maths sizes are declared in advance. If the text -size isn’t “known”, the script- and scriptscriptfont sizes are +size isn’t “known”, the script- and scriptscriptfont sizes are calculated as fixed ratios of the tex font size. (The values used are <code>\</code><code>defaultscriptratio</code>=0.7, and <code>\</code><code>defaultscriptscriptratio</code>=0.5.) <p/>The fixed-ratio formula is capable of producing inconvenient results (particularly if you are using fonts which LaTeX believes are only available in a fixed set of sizes). You may also want to replace -LaTeX’s ideas altogether, for example by setting maths noticeably +LaTeX’s ideas altogether, for example by setting maths noticeably larger or smaller than its surrounding text. For this purpose, the LaTeX command <code>\</code><code>DeclareMathSizes{<<i>tfs</i>>}{<<i>ts</i>>}{<<i>ss</i>>}{<<i>sss</i>>}</code> @@ -45,9 +45,9 @@ document: only one association is available for each text font size for the whole document. The default settings are specified in <i>fontdef.dtx</i> in the latex distribution, and are compiled into <i>fontmath.ltx</i>; the arguments to the command are just numbers -(‘<code>pt</code>’ is assumed), but some of them are written using +(‘<code>pt</code>’ is assumed), but some of them are written using <a href="FAQ-ltxabbrv.html">LaTeX abbreviations</a> for standard font sizes. -Beware simply copying (parts of) the LaTeX definitions — since +Beware simply copying (parts of) the LaTeX definitions — since they contain those internal abbreviations, they need to be treated as <a href="FAQ-atsigns.html">internal commands</a>. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html index 47d164928cc..6f97739d8d6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathstext.html @@ -4,17 +4,17 @@ <h3>Text inside maths</h3> <p/>When we type maths in (La)TeX, the letters from which we make up ordinary text assume a special significance: they all become -single-letter variable names. The letters appear in italics, but it’s -not the same sort of italics that you see when you’re typing ordinary -text: a run of maths letters (for example “here”) looks oddly -“lumpy” when compared with the word written in italic text. The +single-letter variable names. The letters appear in italics, but it’s +not the same sort of italics that you see when you’re typing ordinary +text: a run of maths letters (for example “here”) looks oddly +“lumpy” when compared with the word written in italic text. The difference is that the italic text is kerned to make the letters fit -well together, whereas the maths is set to look as if you’re +well together, whereas the maths is set to look as if you’re multiplying <em>h</em> by <em>e</em> by <em>r</em> by <em>e</em>. The other way things are odd in TeX maths typing is that spaces are ignored: at best we can write single words in this oddly lumpy font. -<p/>So, if we’re going to have good-looking text in amongst maths we’re -writing, we have to take special precautions. If you’re using +<p/>So, if we’re going to have good-looking text in amongst maths we’re +writing, we have to take special precautions. If you’re using LaTeX, the following should help. <p/>The simplest is to use <code>\</code><code>mbox</code> or <code>\</code><code>textrm</code>: <blockquote> @@ -38,8 +38,8 @@ $z = a_{\textrm{other end}}$ </blockquote><p> does the same as <code>\</code><code>mbox</code>, by default. <p/>(The maths-mode instance of your roman font (<code>\</code><code>mathrm</code>) gets the -size right, but since it’s intended for use in maths, its spaces get -ignored — use <code>\</code><code>mathrm</code> for upright roman alphabetic variable +size right, but since it’s intended for use in maths, its spaces get +ignored — use <code>\</code><code>mathrm</code> for upright roman alphabetic variable names, but not otherwise.) <p/>You can correct these problems with size selectors in the text, as: <blockquote> @@ -49,12 +49,12 @@ $z = a_{\mbox{\scriptsize other end}}$ </blockquote><p> which works if your surrounding text is at default document size, but gives you the wrong size otherwise. -<p/>The <code>\</code><code>mbox</code> short cut is (just about) OK for “occasional” +<p/>The <code>\</code><code>mbox</code> short cut is (just about) OK for “occasional” use, but serious mathematics calls for a technique that relieves the typist of the sort of thought required. As usual, the -AMSLaTeX system provides what’s necessary — the <code>\</code><code>text</code> +AMSLaTeX system provides what’s necessary — the <code>\</code><code>text</code> command. (The command is actually provided by the <i>amstext</i> -package, but the “global” <i>amsmath</i> package loads it.) Thus +package, but the “global” <i>amsmath</i> package loads it.) Thus anyone using AMSLaTeX proper has the command available, so even this author can write: <blockquote> @@ -66,7 +66,7 @@ $z = a_{\text{other end}}$ </blockquote><p> and the text will be at the right size, and in the same font as surrounding text. (The <i>amstext</i> package also puts -<code>\</code><code>textrm</code> to rights — but <code>\</code><code>text</code> is easier to type than +<code>\</code><code>textrm</code> to rights — but <code>\</code><code>text</code> is easier to type than <code>\</code><code>textrm</code>!) <p/>AMSLaTeX also makes provision for interpolated comments in the middle of one of its multi-line display structures, through the @@ -81,7 +81,7 @@ middle of one of its multi-line display structures, through the \end{align} </pre> </blockquote><p> -places the text “and” on a separate line before the last line of the +places the text “and” on a separate line before the last line of the display. If the interjected text is short, or the equations themselves are light-weight, you may find that <code>\</code><code>intertext</code> leaves too much space. Slightly more modest is the <code>\</code><code>shortintertext</code> @@ -97,7 +97,7 @@ command from the <i>mathtools</i> package: </blockquote><p> To have the text on the same line as the second equation, one can use the <code>flalign</code> environment (from <i>amsmath</i>) -with lots of dummy equations (represented by the double <code>&</code> +with lots of dummy equations (represented by the double <code>&</code> signs): <blockquote> <pre> @@ -107,18 +107,13 @@ signs): \end{flalign} </pre> </blockquote><p> -<p/>Comprehensive documentation of AMSLaTeX is to be found in -<i>amsldoc</i>, in the distribution; it is also available on the web -at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a> <dl> -<dt><tt><i>amsldoc.tex</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsmath.html">catalogue entry</a> <dt><tt><i>amstext.sty</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amstext.html">catalogue entry</a> <dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of the <i>mh</i> bundle - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mathtools.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html index e5b3cd9f26a..3000e5ab25e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcfloat.html @@ -10,7 +10,7 @@ \end{figure} </pre> </blockquote><p> -in a <code>multicols</code> environment, the figure won’t appear. If +in a <code>multicols</code> environment, the figure won’t appear. If instead you use <blockquote> <pre> @@ -20,16 +20,16 @@ instead you use </pre> </blockquote><p> the figure will stretch right across the page (just the same as a -<code>figure*</code> in standard LaTeX’s <code>twocolumn</code> option). -<p/>It’s possible to have single-column figures and tables with captions, -using the ‘<code>[H]</code>’ placement option introduced by the <i>float</i> +<code>figure*</code> in standard LaTeX’s <code>twocolumn</code> option). +<p/>It’s possible to have single-column figures and tables with captions, +using the ‘<code>[H]</code>’ placement option introduced by the <i>float</i> package but you might have to fiddle with the placement because they -won’t ‘float’, and exhibit other strange behaviours (such as silently +won’t ‘float’, and exhibit other strange behaviours (such as silently running off the end of the column at the end of the <code>multicols</code> environment). <dl> <dt><tt><i>float.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse the directory</a>) -<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/multicol.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html index f6896650e09..181f4c2cb99 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mcite.html @@ -2,39 +2,39 @@ <title>UK TeX FAQ -- question label mcite</title> </head><body> <h3>Multiple citations</h3> -<p/>A convention sometimes used in physics journals is to “collapse” a group of +<p/>A convention sometimes used in physics journals is to “collapse” a group of related citations into a single entry in the bibliography. BibTeX, -by default, can’t cope with this arrangement, but the <i>mcite</i> +by default, can’t cope with this arrangement, but the <i>mcite</i> and <i>mciteplus</i> packages deal with the problem. <p/><i>mcite</i> overloads the <code>\</code><code>cite</code> command to recognise a -“<code>*</code>” at the start of a key, so that citations of the form +“<code>*</code>” at the start of a key, so that citations of the form <blockquote> <pre> \cite{paper1,*paper2} </pre> </blockquote><p> appear in the document as a single citation, and appear arranged -appropriately in the bibliography itself. You’re not limited to -collapsing just two references. You can mix “collapsed” references -with “ordinary” ones, as in +appropriately in the bibliography itself. You’re not limited to +collapsing just two references. You can mix “collapsed” references +with “ordinary” ones, as in <blockquote> <pre> \cite{paper0,paper1,*paper2,paper3} </pre> </blockquote><p> -Which will appear in the document as 3 citations “[4,7,11]” -(say) — citation ‘4’ will refer to paper 0, ‘7’ will refer to a -combined entry for paper 1 and paper 2, and ‘11’ will refer to +Which will appear in the document as 3 citations “[4,7,11]” +(say) — citation ‘4’ will refer to paper 0, ‘7’ will refer to a +combined entry for paper 1 and paper 2, and ‘11’ will refer to paper 3. <p/>You need to make a small change to the bibliography style (<code>.bst</code>) file you use; the <i>mcite</i> package documentation tells you how to do that. <p/>(Despite these multiple citations being primarily a physics-oriented -requirement, the <i>RevTeX</i> (Physics support) class doesn’t work +requirement, the <i>RevTeX</i> (Physics support) class doesn’t work with <i>mcite</i>. <p/>The <i>mciteplus</i> package adresses many of the infelicites of <i>mcite</i>, and <em>does</em> work with <i>RevTeX</i>. Again, -‘ordinary’ <code>.bst</code> files will not work with +‘ordinary’ <code>.bst</code> files will not work with <i>mciteplus</i>, but the package documentation explains how to patch an existing BibTeX style. <p/>The <i>collref</i> package takes a rather different approach to the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html index c691672103f..8904a3ee3de 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html @@ -11,7 +11,7 @@ acquire a new font. One important question is the <em>encoding</em> of (Latin character) fonts; while we all more or less agree about the position of about 96 characters in fonts (the basic ASCII set), the rest of the (typically) 256 vary. The most obvious problems are with -floating accents and special characters such as the ‘pounds sterling’ +floating accents and special characters such as the ‘pounds sterling’ sign. There are three ways of dealing with this: either you change the TeX macros which reference the characters (not much fun, and error-prone); or you change the encoding of the font (easier than you @@ -21,20 +21,20 @@ LaTeX2e has facilities for dealing with fonts in different encodings; read the <a href="FAQ-books.html"><em>LaTeX Companion</em></a> for more details. In practice, if you do much non-English (but Latin script) typesetting, you are strongly recommended to use the -<i>fontenc</i> package with option ‘<code>T1</code>’ to select -<a href="FAQ-ECfonts.html">‘Cork’</a> encoding. -A useful alternative is Y&Y’s “private” LY1 encoding, -which is designed to sit well with “Adobe standard” encoded fonts. +<i>fontenc</i> package with option ‘<code>T1</code>’ to select +<a href="FAQ-ECfonts.html">‘Cork’</a> encoding. +A useful alternative is Y&Y’s “private” LY1 encoding, +which is designed to sit well with “Adobe standard” encoded fonts. Basic support of LY1 is available on CTAN: note that the -“relation with Adobe’s encoding” means that there are no +“relation with Adobe’s encoding” means that there are no virtual fonts in the LY1 world. -<p/>Alan Jeffrey’s <i>fontinst</i> package is an AFM to +<p/>Alan Jeffrey’s <i>fontinst</i> package is an AFM to TFM converter written in TeX; it is used to generate the -files used by LaTeX2e’s PSNFSS package to support use of +files used by LaTeX2e’s PSNFSS package to support use of PostScript fonts. It is a sophisticated package, not for the faint-hearted, but is powerful enough to cope with most needs. Much of its power relies on the use of <a href="FAQ-virtualfonts.html">virtual fonts</a>. -<p/>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, +<p/>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, distributed with <i>dvips</i>, is fast and efficient; note that the metrics and styles that come with <i>dvips</i> are <em>not</em> currently LaTeX2e compatible. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html index cbb848ee5a9..0a1b1c8497e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mfptutorials.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label mfptutorials</title> </head><body> <h3>Metafont and MetaPost Tutorials</h3> -<p/>Apart from Knuth’s book, there seems to be only one publicly-available +<p/>Apart from Knuth’s book, there seems to be only one publicly-available <a href="http://metafont.tutorial.free.fr/">tutorial for Metafont</a>, by Christophe Grandsire (a copy in PDF form may be downloaded). -Geoffrey Tobin’s <i>Metafont for Beginners</i> +Geoffrey Tobin’s <i>Metafont for Beginners</i> (see <a href="FAQ-useMF.html">using Metafont</a>) describes how the Metafont system works and how to avoid some of the potential pitfalls. <p/>There is also an article on how to run both Metafont and MetaPost (the -programs). Peter Wilson’s +programs). Peter Wilson’s <i>Some Experiences in Running Metafont and MetaPost</i> -offers the benefit of Peter’s experience (he has designed a number of -‘historical’ fonts using Metafont). For Metafont the article is geared +offers the benefit of Peter’s experience (he has designed a number of +‘historical’ fonts using Metafont). For Metafont the article is geared towards testing and installing new Metafont fonts, while its MetaPost section describes how to use MetaPost illustrations in LaTeX and PDFLaTeX documents, with an emphasis on how to use appropriate @@ -22,27 +22,27 @@ fonts for any text or mathematics. <p/>Other MetaPost tutorials that have appeared are two in English by -<a href="http://remote.science.uva.nl/~heck/Courses/mptut.pdf">André Heck</a> +<a href="http://remote.science.uva.nl/~heck/Courses/mptut.pdf">André Heck</a> and <a href="http://www.tlhiv.org/MetaPost/tutorial/">Urs Oswald</a>, -and one in French (listed here because it’s clearly enough written +and one in French (listed here because it’s clearly enough written that even this author understands it), by -<a href="http://pauillac.inria.fr/~cheno/metapost/metapost.pdf">Laurent Chéno</a>; +<a href="http://pauillac.inria.fr/~cheno/metapost/metapost.pdf">Laurent Chéno</a>; both have been recommended for inclusion in the FAQ -<p/>Urs Oswald’s tutorial is accompanied by a super tool (by Troy +<p/>Urs Oswald’s tutorial is accompanied by a super tool (by Troy Henderson) for testing little bits of MetaPost, which is an invaluable aid to the learner: <a href="http://www.tlhiv.org/mppreview">http://www.tlhiv.org/mppreview</a> -<p/>Vincent Zoonekynd’s massive set of example MetaPost files is available on +<p/>Vincent Zoonekynd’s massive set of example MetaPost files is available on CTAN; the set includes a <i>Perl</i> script to convert the set to html, and the set may be <a href="http://zoonek.free.fr/LaTeX/Metapost/metapost.html">viewed on the web</a>. -While these examples don’t exactly constitute a “tutorial”, they’re +While these examples don’t exactly constitute a “tutorial”, they’re most certainly valuable learning material. Urs Oswald presents a <a href="http://www.ursoswald.ch/metapost/tutorial.pdf">similar document</a>, written more as a document, and presented in PDF. <dl> -<dt><tt><i>Beginners’ guide</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metafont/beginners/metafont-for-beginners.pdf">info/metafont/beginners/metafont-for-beginners.pdf</a> -<dt><tt><i>Peter Wilson’s “experiences”</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metafont/metafp/metafp.pdf">info/metafont/metafp/metafp.pdf</a> -<dt><tt><i>Vincent Zoonekynd’s examples</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse the directory</a>) +<dt><tt><i>Beginners’ guide</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metafont/beginners/metafont-for-beginners.pdf">info/metafont/beginners/metafont-for-beginners.pdf</a> +<dt><tt><i>Peter Wilson’s “experiences”</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metafont/metafp/metafp.pdf">info/metafont/metafp/metafp.pdf</a> +<dt><tt><i>Vincent Zoonekynd’s examples</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html index 59f00e55728..2f6ebcfe709 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minitoc.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label minitoc</title> </head><body> <h3>Table of contents, etc., per chapter</h3> -<p/>The common style, of a “small” table of contents for each part, +<p/>The common style, of a “small” table of contents for each part, chapter, or even section, is supported by the <i>minitoc</i> package. The package also supports mini-lists of tables and figures; but, as the documentation observes, mini-bibliographies are a -different problem — see +different problem — see <a href="FAQ-chapbib.html">bibliographies per chapter</a>. -<p/>The package’s basic scheme is to generate a little <code>.aux</code> file for +<p/>The package’s basic scheme is to generate a little <code>.aux</code> file for each chapter, and to process that within the chapter. Simple usage would be: <blockquote> @@ -25,14 +25,14 @@ would be: ... </pre> </blockquote><p> -though a lot of elaborations are possible (for example, you don’t need +though a lot of elaborations are possible (for example, you don’t need a <code>\</code><code>minitoc</code> for every chapter). -<p/><i>Babel</i> doesn’t know about <i>minitoc</i>, but +<p/><i>Babel</i> doesn’t know about <i>minitoc</i>, but <i>minitoc</i> makes provision for other document languages than -English — a wide variety is available. Fortunately, the current +English — a wide variety is available. Fortunately, the current version of the <i>hyperref</i> package does know about <i>minitoc</i> and treats <code>\</code><code>minitoc</code> tables in the -same way as “real” tables of contents. +same way as “real” tables of contents. <dl> <dt><tt><i>babel.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel.zip">macros/latex/required/babel</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel/">browse the directory</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html index 3b6aeec0540..9581126ddd7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-minxampl.html @@ -1,10 +1,10 @@ <head> <title>UK TeX FAQ -- question label minxampl</title> </head><body> -<h3>How to make a “minimum example”</h3> +<h3>How to make a “minimum example”</h3> <p/><a href="FAQ-askquestion.html">Our advice on asking questions</a> -suggests that you prepare a “minimum example” (also commonly known -as a “<em>minimal</em> example”) of failing behaviour, +suggests that you prepare a “minimum example” (also commonly known +as a “<em>minimal</em> example”) of failing behaviour, as a sample to post with your question. If you have a problem in a two hundred page document, it may be unclear how to proceed from this problem to a succinct demonstration of your problem. @@ -17,9 +17,9 @@ with a basic document structure <code>\</code><code>begin{document}</code>, <code>\</code><code>end{document}</code>) and adds things. First to add is a paragraph or so around the actual point where the problem occurs. (It may prove difficult to find the actual -line that’s provoking the problem. If the original problem is an +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> +<a href="FAQ-errstruct.html">“the structure of TeX errors”</a> may help.) <p/>Note that there are things that can go wrong in one part of the document as a result of something in another part: the commonest is @@ -27,11 +27,11 @@ problems in the table of contents (from something in a section title, or whatever), or the list of <<i>something</i>> (from something in a <code>\</code><code>caption</code>). In such a case, include the section title or caption (the caption probably needs the <code>figure</code> or -<code>table</code> environment around it, but it <em>doesn’t</em> need +<code>table</code> environment around it, but it <em>doesn’t</em> need the figure or table itself). -<p/>If this file you’ve built up shows the problem already, then you’re done. +<p/>If this file you’ve built up shows the problem already, then you’re done. Otherwise, try adding packages; the optimum is a file with only one -package in it, but you may find that the guilty package won’t even load +package in it, but you may find that the guilty package won’t even load properly unless another package has been loaded. (Another common case is that package <i>A</i> only fails when package <i>B</i> has been loaded.) @@ -39,21 +39,21 @@ loaded.) <b><em>Hacking down</em></b> starts with your entire document, and removes bits until the file no longer fails (and then of course -restores the last thing removed). Don’t forget to hack out any +restores the last thing removed). Don’t forget to hack out any unnecessary packages, but mostly, the difficulty is choosing what to hack out of the body of the document; this is the mirror of the -problem above, in the “building up” route. -<p/>If you’ve added a package (or more than one), add <code>\</code><code>listfiles</code> to +problem above, in the “building up” route. +<p/>If you’ve added a package (or more than one), add <code>\</code><code>listfiles</code> to the preamble too: that way, LaTeX will produce a list of the -packages you’ve used and their version numbers. This information may +packages you’ve used and their version numbers. This information may be useful evidence for people trying to help you. -<p/>What if your document simply doesn’t fail in any of these cut-down -scenarios? Whatever you do, don’t post the whole of the document: if +<p/>What if your document simply doesn’t fail in any of these cut-down +scenarios? Whatever you do, don’t post the whole of the document: if you can, it may be useful to make a copy available on the web -somewhere: people will probably understand if it’s impossible … +somewhere: people will probably understand if it’s impossible … or inadvisable, in the case of something confidential. -<p/>If the whole document is necessary, it could be that it’s an overflow -of some sort; the best you can do is to post the code “around” the +<p/>If the whole document is necessary, it could be that it’s an overflow +of some sort; the best you can do is to post the code “around” the error, and (of course) the full text of the error. <p/>It may seem that all this work is rather excessive for preparing a simple post. There are two responses to that, both based on the @@ -62,11 +62,11 @@ relative inefficiency of asking a question on the internet. answer, without all the fuss of posting and looking for responses. <p/>Second, your prime aim is to get an answer as quickly as possible; a well-prepared example stands a good chance of attracting an answer -“in a single pass”: if the person replying to your post finds she +“in a single pass”: if the person replying to your post finds she needs more information, you have to find that request, post again, and wait for your benefactor to produce a second response. <p/>All things considered, a good example file can save you a day, for -perhaps half an hour’s effort invested. +perhaps half an hour’s effort invested. <p/>The above advice, differently phrased, may also be read on the web at <a href="http://www.minimalbeispiel.de/mini-en.html">http://www.minimalbeispiel.de/mini-en.html</a>; source of that article may be found at <a href="http://www.minimalbeispiel.de/">http://www.minimalbeispiel.de/</a>, in diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html index 75ea3442415..71ba2f14987 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-missbegdoc.html @@ -16,9 +16,9 @@ many arguments to one of the setup commands related to the class or a package that you have loaded. <p/>A corrupt <code>.aux</code> file might be due to any number of things; delete the file and to run LaTeX again, twice. If the error -recurs, it’s probably due to a buggy class or package. +recurs, it’s probably due to a buggy class or package. <p/>If the error occurs while LaTeX is reading a class or package, then -there’s probably a bug in the file. The author of the class or +there’s probably a bug in the file. The author of the class or package stands the best chance of finding the bug, but with luck you (or someone you ask on a mailing list or on <i>comp.text.tex</i>) will be able to spot the problem and provide a work-around. Always diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html index cef0b600977..9e3817e233d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misschar.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label misschar</title> </head><body> <h3>Where have my characters gone?</h3> -<p/>You’ve typed some apparently reasonable text and processed it, but the +<p/>You’ve typed some apparently reasonable text and processed it, but the result contains no sign of some of the characters you typed. A likely -reason is that the font you selected just doesn’t have a +reason is that the font you selected just doesn’t have a representation for the character in question. -<p/>For example, if I type “that will be £44.00” into an ordinary +<p/>For example, if I type “that will be £44.00” into an ordinary (La)TeX document, or if I select the font <code>rsfs10</code> (which contains -uppercase letters only) and type pretty much anything, the £ +uppercase letters only) and type pretty much anything, the £ sign, or any lowercase letters or digits will not appear in the -output. There’s no actual error message, either: you have to read the -log file, where you’ll find cryptic little messages like +output. There’s no actual error message, either: you have to read the +log file, where you’ll find cryptic little messages like <blockquote> <pre> Missing character: There is no ^^a3 in font cmr10! @@ -19,9 +19,9 @@ Missing character: There is no 3 in font rsfs10! </pre> </blockquote><p> -(the former demonstrating my TeX’s unwillingness to deal in characters +(the former demonstrating my TeX’s unwillingness to deal in characters which have the eighth bit set, while the <code>rsfs10</code> example shows that -TeX will log the actual character in error, if it thinks it’s +TeX will log the actual character in error, if it thinks it’s possible). <p/>Somewhat more understandable are the diagnostics you may get from <i>dvips</i> when using the OT1 and T1 versions of @@ -34,7 +34,7 @@ dvips: Warning: missing glyph `Delta' The process that generates the metrics for using the fonts generates an instruction to <i>dvips</i> to produce these diagnostics, so that their non-appearance in the printed output is less surprising -than it might be. Quite a few glyphs provided in Knuth’s text +than it might be. Quite a few glyphs provided in Knuth’s text encodings and in the Cork encoding are not available in the Adobe fonts. In these cases, there <em>is</em> a typeset sign of the character: <i>dvips</i> produces a black rectangle of whatever diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html index 97bac2f33e9..42fbdf3b4eb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-misssymb.html @@ -2,7 +2,7 @@ <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 +<p/>You’re processing an old document, and some symbol commands such as <code>\</code><code>Box</code> and <code>\</code><code>lhd</code> appear no longer to exist. These commands were present in the core of LaTeX 2.09, but are not in current LaTeX. They are available in the <i>latexsym</i> package (which is part of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html index 0606222fef5..a798bfe9ab6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-moren9.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label moren9</title> </head><body> <h3>How to break the 9-argument limit</h3> -<p/>If you think about it, you will realise that Knuth’s command +<p/>If you think about it, you will realise that Knuth’s command definition syntax: <blockquote> <pre> -\def\blah#1#2 ... #9{<macro body>} +\def\blah#1#2 ... #9{<macro body>} </pre> </blockquote><p> -is intrinsically limited to just 9 arguments. There’s no direct way -round this: how would you express a 10th argument? — and ensure that -the syntax didn’t gobble some other valid usage? +is intrinsically limited to just 9 arguments. There’s no direct way +round this: how would you express a 10th argument? — and ensure that +the syntax didn’t gobble some other valid usage? <p/>If you really must have more than 9 arguments, the way to go is: <blockquote> <pre> @@ -27,7 +27,7 @@ the syntax didn’t gobble some other valid usage? % \ArgI-\ArgIX % arguments 10-12 are in % #1-#3 - <macro body>% + <macro body>% } </pre> </blockquote><p> @@ -35,7 +35,7 @@ This technique is easily extendible by concert pianists of the TeX keyboard, but is really hard to recommend. <p/>LaTeX users have the small convenience of merely giving a number of arguments in the <code>\</code><code>newcommand</code> that defines each part of the -relaying mechanism: Knuth’s restriction applies to <code>\</code><code>newcommand</code> +relaying mechanism: Knuth’s restriction applies to <code>\</code><code>newcommand</code> just as it does to <code>\</code><code>def</code>. However, LaTeX users also have the way out of such barbarous command syntax: the <i>keyval</i> package. With <i>keyval</i>, and a bit of programming, one can @@ -54,11 +54,11 @@ like: </pre> </blockquote><p> The merit of such verbosity is that it is self-explanatory: the typist -doesn’t have to remember that argument twelve is <code>soiltype</code>, and so +doesn’t have to remember that argument twelve is <code>soiltype</code>, and so on: the commands may be copied from field notes quickly and accurately. <dl> -<dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>) +<dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/keyval.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html index b7430533bc6..74b91531957 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mpprologues.html @@ -3,12 +3,12 @@ </head><body> <h3>Displaying MetaPost output in <i>ghostscript</i></h3> <p/>MetaPost ordinarily expects its output to be included in some context -where the ‘standard’ Metafont fonts (that you’ve specified) are already -defined — for example, as a figure in TeX document. If you’re +where the ‘standard’ Metafont fonts (that you’ve specified) are already +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 experience an error such +the PostScript ‘engine’ in <i>ghostscript</i> <em>doesn’t</em> +ordinarily have the fonts loaded, and you’ll experience an error such as <blockquote> <pre> @@ -19,13 +19,13 @@ There is provision in MetaPost for avoiding this problem: issue the command <code>prologues := 2;</code> at the start of the <code>.mp</code> file. <p/>Unfortunately, the PostScript that MetaPost inserts in its output, following this command, is incompatible with ordinary use of the -PostScript in inclusions into (La)TeX documents, so it’s best to +PostScript in inclusions into (La)TeX documents, so it’s best to make the <code>prologues</code> command optional. Furthermore, MetaPost takes a very simple-minded approach to font encoding: since TeX font encodings regularly confuse sophisticated minds, this can prove -troublesome. If you’re suffering such problems (the symptom is that +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 @@ -42,7 +42,7 @@ or by issuing a shell command such as mp '\prologues:=2; input MyFigure' </pre> </blockquote><p> -(which will work without the quote marks if you’re not using a Unix +(which will work without the quote marks if you’re not using a Unix shell). <p/>A suitable LaTeX route would involve processing <i>MyFigure.tex</i>, which contains: @@ -66,15 +66,15 @@ dvips -E -o MyFigure.eps MyFigure would then give a satisfactory Encapsulated PostScript file. This procedure may be automated using the <i>Perl</i> script <i>mps2eps</i>, thus saving a certain amount of tedium. -<p/>The Plain TeX user may use an adaptation of a jiffy of Knuth’s, by -Dan Luecking. Dan’s version <i>mpsproof.tex</i> will work under +<p/>The Plain TeX user may use an adaptation of a jiffy of Knuth’s, by +Dan Luecking. Dan’s version <i>mpsproof.tex</i> will work under TeX to produce a DVI file for use with <i>dvips</i>, or under PDFTeX to produce a PDF file, direct. The output is set up to look like a proof sheet. <p/>A script application, <i>mptopdf</i>, is available in recent (La)TeX distributions: it seems fairly reliably to produce PDF from MetaPost, so may reasonably be considered an answer to -the question… +the question… <dl> <dt><tt><i>mps2eps</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/mps2eps.zip">support/mps2eps</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/mps2eps/">browse the directory</a>) <dt><tt><i>mpsproof.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/graphics/metapost/contrib/misc/mpsproof.tex">graphics/metapost/contrib/misc/mpsproof.tex</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html index 014fb2e77a7..47357d5e0da 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-msxy.html @@ -5,14 +5,14 @@ <p/>The <i>msx</i> and <i>msy</i> fonts were designed by the American Mathematical Society in the very early days of TeX, for use in typesetting papers for mathematical journals. They were -designed using the ‘old’ Metafont, which wasn’t portable and is no longer +designed using the ‘old’ Metafont, which wasn’t portable and is no longer available; for a long time they were only available in 300dpi versions which only imperfectly matched modern printers. The AMS has now redesigned the fonts, using the current version of Metafont, and the new versions are called the <i>msa</i> and <i>msb</i> families. <p/>Nevertheless, <i>msx</i> and <i>msy</i> continue to turn up to -plague us. There are, of course, still sites that haven’t got around +plague us. There are, of course, still sites that haven’t got around to upgrading; but, even if everyone upgraded, there would still be the problem of old documents that specify them. <p/>If you have a <code>.tex</code> source that requests <i>msx</i> and diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html index 89f59c8d41a..ed760d082ab 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multbib.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label multbib</title> </head><body> <h3>Multiple bibliographies?</h3> -<p/>If you’re thinking of multiple bibliographies tied to some part of +<p/>If you’re thinking of multiple bibliographies tied to some part of your document (such as the chapters within the document), please see <a href="FAQ-chapbib.html">bibliographies per chapter</a>. <p/>For more than one bibliography, there are three options. <p/>The <i>multibbl</i> package offers a very simple interface: you use -a command <code>\</code><code>newbibliography</code> to define a bibliography “tag”. The package +a command <code>\</code><code>newbibliography</code> to define a bibliography “tag”. The package redefines the other bibliography commands so that each time you use any one of them, you give it the tag for the bibliography where you want the citations to appear. The <code>\</code><code>bibliography</code> command itself also takes @@ -35,7 +35,7 @@ section or chapter (i.e., it patches </blockquote><p> (Note that the optional argument of <code>\</code><code>cite</code> appears <em>before</em> the new tag argument, and that the <code>\</code><code>bibliography</code> commands may list -more than one <code>.bib</code> file — indeed all <code>\</code><code>bibliography</code> commands +more than one <code>.bib</code> file — indeed all <code>\</code><code>bibliography</code> commands may list the same set of files.) <p/>The <code>\</code><code>bibliography</code> data goes into files whose names are <<i>tag-name</i>><em>.aux</em>, so you will need to run @@ -48,7 +48,7 @@ bibtex art after the first run of LaTeX, to get the citations in the correct place. <p/>The <i>multibib</i> package allows you to define a series of -“additional topics”, each of which comes with its own series of +“additional topics”, each of which comes with its own series of bibliography commands. So one might write: <blockquote> <pre> @@ -78,7 +78,7 @@ bibtex art </pre> </blockquote><p> Note that, unlike <i>multibbl</i>, <i>multibib</i> allows a -simple, unmodified bibliography (as well as the “topic” ones). +simple, unmodified bibliography (as well as the “topic” ones). <p/>The <i>bibtopic</i> package allows you separately to cite several different bibliographies. At the appropriate place in your document, you put a sequence of <code>btSect</code> environments (each of which @@ -120,7 +120,7 @@ the content of the database (if nothing has been cited from the database, this is equivalent to LaTeX standard <code>\</code><code>nocite{*}</code>). <p/>However, the <em>real</em> difference from <i>multibbl</i> and <i>multibib</i> is that selection of what appears in each -bibliography section is determined in <i>bibtopic</i> by what’s in +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> package. You provide a <code>category</code> environment, in the @@ -129,7 +129,7 @@ citation list for. In each environment, you list the <code>\</code><code>cite</ that you want listed in each category. The <code>\</code><code>bibliography</code> command (or, more precisely, the <code>thebibliography</code> environment it uses) will sort the keys as requested. (Keys not mentioned in a -<code>category</code> appear in a “misc” category created in the +<code>category</code> appear in a “misc” category created in the sorting process.) A code example appears in the package documentation (a PDF file in the CTAN directory, which you can browse to, from the link, below). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html index 1f8f1c05cfc..1564c112bc2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multfoot.html @@ -21,8 +21,7 @@ also designed to support typesetting critical editions. <dt><tt><i>edmac</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/edmac.zip">macros/plain/contrib/edmac</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/edmac/">browse the directory</a>) <dt><tt><i>ednotes</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ednotes.zip">macros/latex/contrib/ednotes</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ednotes/">browse the directory</a>) <dt><tt><i>ledmac</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse the directory</a>) -<dt><tt><i>manyfoot.sty</i></tt><dd>Distributed as part of the <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools.zip">macros/latex/contrib/ncctools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools/">browse the directory</a>) - bundle +<dt><tt><i>manyfoot.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools.zip">macros/latex/contrib/ncctools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/manyfoot.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html index 26bc1a42775..6bb12571065 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multidoc.html @@ -1,34 +1,81 @@ <head> <title>UK TeX FAQ -- question label multidoc</title> </head><body> -<h3>A ‘report’ from lots of ‘article’s</h3> +<h3>A ‘report’ from lots of ‘article’s</h3> <p/>This is a requirement, for example, if one is preparing the proceedings of a conference whose papers were submitted in LaTeX. -<p/>The nearest things to canned solutions are Peter Wilson’s -<i>combine</i> and Federico Garcia’s <i>subfiles</i> classes. -<p/><i>Combine</i> defines the means to ‘<code>\</code><code>import</code>’ entire documents, +<p/>The nearest things to canned solutions are Peter Wilson’s +<i>combine</i> and Federico Garcia’s <i>subfiles</i> classes. +<p/><i>Combine</i> defines the means to ‘<code>\</code><code>import</code>’ entire documents, and provides means of specifying significant features of the layout of -the document, as well as a global table of contents, and so on. An -auxiliary package, <i>combinet</i>, allows use of the <code>\</code><code>title</code>s -and <code>\</code><code>author</code>s (etc.) of the <code>\</code><code>import</code>ed documents to appear in -the global table of contents. -<p/><i>Subfiles</i> is used in the component files of a multi-file -project, and the corresponding <i>subfiles</i> is used in the -master file; arrangements may be made so that the component files will +the document, as well as a global table of contents, and so on. The +complete set of facilities is pretty complex. An auxiliary package, +<i>combinet</i>, allows use of the <code>\</code><code>title</code>s and <code>\</code><code>author</code>s +(etc.) of the <code>\</code><code>import</code>ed documents to appear in the global table +of contents. The basic structure of a combined document would be: +<blockquote> +<pre> +\documentclass[...]{combine} +... +\begin{document} +... +<introductory materiel> +... +\begin{papers} +% title and author of first article, +% to go the the main ToC +\coltoctitle{...} +\coltocauthor{...} +\label{art1} +\import{art1} +... +\end{papers} +... +<acknowledgements, etc.> +... +\end{document} +</pre> +</blockquote><p> +<p/>The <i>subfiles</i> class is used in the component files of a multi-file +project, and the corresponding <i>subfiles</i> package is used in the +master file; so the structure of the master file looks like: +<blockquote> +<pre> +\documentclass{<whatever>} +... +\usepackage{subfiles} +... +\begin{document} +... +\subfile{subfile_name} +... +\end{document} +</pre> +</blockquote><p> +while a subfile has the structure: +<blockquote> +<pre> +\documentclass[mainfile_name]{subfiles} +\begin{document} +... +\end{document} +</pre> +</blockquote><p> +Arrangements may be made so that the component files will be typeset using different page format, etc., parameters than those used when they are typeset as a part of the main file. -<p/>A more ‘raw’ toolkit is offered by Matt Swift’s <i>includex</i> and +<p/>A more ‘raw’ toolkit is offered by Matt Swift’s <i>includex</i> and <i>newclude</i> packages, both part of the <i>frankenstein</i> bundle. Note that Matt believes <i>includex</i> is obsolete (though it continues to work for this author); furthermore, its -replacement, <i>newclude</i> remains “in development”, as it has +replacement, <i>newclude</i> remains “in development”, as it has been since 1999. <p/>Both <i>includex</i> and <i>newclude</i> enable you to -‘<code>\</code><code>includedoc</code>’ complete articles (in the way that you -‘<code>\</code><code>include</code>’ chapter files in an ordinary report). The preamble +‘<code>\</code><code>includedoc</code>’ complete articles (in the way that you +‘<code>\</code><code>include</code>’ chapter files in an ordinary report). The preamble (everything up to <code>\</code><code>begin{document}</code>), and everything after <code>\</code><code>end{document}</code>, is ignored by both packages. Thus the -packages don’t “do the whole job” for you, though: you need to +packages don’t “do the whole job” for you, though: you need to analyse the package use of the individual papers, and ensure that a consistent set is loaded in the preamble of the main report. (Both packages require <i>moredefs</i>, which is also part of the bundle.) @@ -43,10 +90,10 @@ of the included pages. <dl> <dt><tt><i>combine.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse the directory</a>) <dt><tt><i>combinet.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse the directory</a>) -<dt><tt><i>includex.sty</i></tt><dd>Distributed in the “unsupported” part of +<dt><tt><i>includex.sty</i></tt><dd>Distributed in the “unsupported” part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse the directory</a>) -<dt><tt><i>moredefs.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse the directory</a>) -<dt><tt><i>newclude.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse the directory</a>) +<dt><tt><i>moredefs.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/moredefs.html">catalogue entry</a> +<dt><tt><i>newclude.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/newclude.html">catalogue entry</a> <dt><tt><i>pdfpages.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse the directory</a>) <dt><tt><i>subfiles.cls, etc.</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/subfiles.zip">macros/latex/contrib/subfiles</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/subfiles/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html index 5cfa73dfebf..008bc37a2a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multind.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label multind</title> </head><body> <h3>Multiple indexes</h3> -<p/>LaTeX’s standard indexing capabilities (those provided by the +<p/>LaTeX’s standard indexing capabilities (those provided by the <i>makeidx</i> package) only provide for one index in your document; even quite modest documents can be improved by indexes for separate topics. @@ -11,11 +11,11 @@ multiple indexing. You tag each <code>\</code><code>makeindex</code>, <code>\</ <code>\</code><code>printindex</code> command with a file name, and indexing commands are written to (or read from) the name with the appropriate (<code>.idx</code> or <code>.ind</code>) extension appended. The <code>\</code><code>printindex</code> command is modified -from the LaTeX standard so that it doesn’t create its own chapter +from the LaTeX standard so that it doesn’t create its own chapter or section heading; you therefore decide what names (or sectioning level, even) to use for the indexes, and <a href="FAQ-fixnam.html"><code>\</code><code>indexname</code></a> is completely ignored. -<p/>To create a “general” and an “authors” index, one might write: +<p/>To create a “general” and an “authors” index, one might write: <blockquote> <pre> \usepackage{multind} @@ -40,19 +40,19 @@ makeindex authors </blockquote><p> before running LaTeX again. Note that the names of the index files to process are not necessarily related to the name of the LaTeX -file you’re processing, at all. (There’s no documentation that comes +file you’re processing, at all. (There’s no documentation that comes with the package: what you see above is as good as you will -get…) +get…) <p/>The <i>index</i> package provides a comprehensive set of indexing facilities, including a <code>\</code><code>newindex</code> command that allows the -definition of new styles of index. <code>\</code><code>newindex</code> takes a ‘tag’ (for +definition of new styles of index. <code>\</code><code>newindex</code> takes a ‘tag’ (for use in indexing commands), replacements for the <code>.idx</code> and -<code>.ind</code> file extensions, and a title for the index when it’s -finally printed; it can also change the item that’s being indexed +<code>.ind</code> file extensions, and a title for the index when it’s +finally printed; it can also change the item that’s being indexed against (for example, one might have an index of artists referenced by the figure number where their work is shown). <p/>Using <i>index</i>, to create an author index together with a -“normal” index, one would start with preamble commands: +“normal” index, one would start with preamble commands: <blockquote> <pre> \usepackage{index} @@ -60,7 +60,7 @@ the figure number where their work is shown). \newindex{aut}{adx}{and}{Name Index} </pre> </blockquote><p> -which load the package, define a “main” (original-style) index, and +which load the package, define a “main” (original-style) index, and then define an author index. Then, in the body of the document, we might find commands like: <blockquote> @@ -82,7 +82,7 @@ Which will print the main index and then the author index. Supposing this lot to be in <i>myfile.tex</i>, after enough runs through LaTeX that labels are stable, execute the following commands (Unix-style shell commands shown here, but the principle is the same -whatever system you’re using): +whatever system you’re using): <blockquote> <pre> makeindex myfile @@ -102,11 +102,11 @@ declare each index with a <code>\</code><code>newindex</code> command: and <i>splitidx</i> will generate a file <code>\</code><code>jobname</code><code>.<<i>shortcut</i>></code> to receive index entries generated by commands like <code>\</code><code>sindex[<<i>shortcut</i>>]{<<i>item</i>>}</code>. -As with the other packages, this method is limited by TeX’s total +As with the other packages, this method is limited by TeX’s total number of output files. However, <i>splitindex</i> also comes with a small executable <i>splitindex</i> (available for a variety of -operating systems); if you use this auxiliary program (and don’t use -<code>split</code>), there’s no limit to the number of indexes. Apart +operating systems); if you use this auxiliary program (and don’t use +<code>split</code>), there’s no limit to the number of indexes. Apart from this trick, <i>splitidx</i> supports the same sorts of things as does <i>index</i>. An example of use appears in the documentation. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html index c14facf39ad..333c48c19bf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-multirow.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label multirow</title> </head><body> <h3>Merging cells in a column of a table</h3> -<p/>It’s easy to come up with a table design that requires a cell that +<p/>It’s easy to come up with a table design that requires a cell that spans several rows. An example is something where the left-most column labels the rest of the table; this can be done (in simple cases) by using @@ -25,11 +25,11 @@ might write: \end{tabular} </pre> </blockquote><p> -and <i>multirow</i> will position “Common g text” at the vertical +and <i>multirow</i> will position “Common g text” at the vertical centre of the space defined by the other rows. Note that the rows -that don’t contain the “multi-row” specification must have empty +that don’t contain the “multi-row” specification must have empty cells where the multi-row is going to appear. -<p/>The “<code>*</code>” may be replaced by a column width specification. In this +<p/>The “<code>*</code>” may be replaced by a column width specification. In this case, the argument may contain forced line-breaks: <blockquote> <pre> @@ -66,8 +66,8 @@ down one or other side of a table (with the help of the </blockquote><p> (which gives text going upwards; use angle <code>-90</code> for text going downwards, of course). -<p/>To make a <code>\</code><code>multicolumn</code> multi-row “cell” in a table, you have to -enclose a <code>\</code><code>multirow</code> inside a <code>\</code><code>multicolumn</code> — the other way +<p/>To make a <code>\</code><code>multicolumn</code> multi-row “cell” in a table, you have to +enclose a <code>\</code><code>multirow</code> inside a <code>\</code><code>multicolumn</code> — the other way around does not work, so: <blockquote> <pre> @@ -91,7 +91,7 @@ rows in the multi-row have been opened up with <code>\</code><code>bigstrut</cod <p/>The documentation of both <i>multirow</i> and <i>bigstrut</i> is to be found, as comments, in the package files themselves. <dl> -<dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse the directory</a>) +<dt><tt><i>bigstrut.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse the directory</a>) <dt><tt><i>multirow.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse the directory</a>) </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html index 914123a4f8e..10d3481d50d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html @@ -13,18 +13,18 @@ definitely no longer recommended. a three-pass system (with a processor program that computes values for the element spacing in the music), and achieves finer control than is possible in the unmodified TeX-based mechanism that MusicTeX -uses. Daniel Taupin’s is the only version of MusiXTeX currently +uses. Daniel Taupin’s is the only version of MusiXTeX currently being developed (the original author, Andreas Egler, had an alternative version, but he is now working on a different package altogether). -<p/>Input to MusixTeX is extremely tricky stuff, and Don Simons’ +<p/>Input to MusixTeX is extremely tricky stuff, and Don Simons’ preprocessor <i>pmx</i> is the preferred method of creating input -for Taupin’s version. <i>Pmx</i> greatly eases use of -MusixTeX, but it doesn’t support the full range of MusixTeX’s +for Taupin’s version. <i>Pmx</i> greatly eases use of +MusixTeX, but it doesn’t support the full range of MusixTeX’s facilities directly; however, it does allow in-line MusixTeX code in <i>pmx</i> sources. -<p/>Dirk Laurie’s <i>M-Tx</i> allows preparation of music with lyrics; -it operates “on top of” <i>pmx</i> +<p/>Dirk Laurie’s <i>M-Tx</i> allows preparation of music with lyrics; +it operates “on top of” <i>pmx</i> <p/>Another simple notation is supported by <i>abc2mtex</i>; this is a package designed to notate tunes stored in an ASCII format (<code>abc</code> notation). It was designed primarily for folk and traditional @@ -42,8 +42,8 @@ MusixTeX and related systems. To subscribe, use <p/>An alternative (free) means of embedding music examples into (La)TeX documents is <a href="http://www.lilypond.org">Lilypond</a>. Lilypond is (at heart) a batch music typesetting system with plain text input that -does most of its work without TeX. Lilypond’s input syntax is far -less cryptic than is MusixTeX’s, and it handles much more stuff +does most of its work without TeX. Lilypond’s input syntax is far +less cryptic than is MusixTeX’s, and it handles much more stuff automatically, yielding the same or better quality with less effort. Lilypond can also produce basic MIDI output. <dl> @@ -52,8 +52,8 @@ Lilypond can also produce basic MIDI output. <dt><tt><i>midi2tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/midi2tex.zip">support/midi2tex</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/midi2tex/">browse the directory</a>) <dt><tt><i>musictex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/musictex.zip">macros/musictex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/musictex/">browse the directory</a>) -<dt><tt><i>musixtex (Taupin’s version)</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin/">browse the directory</a>) -<dt><tt><i>musixtex (Egler’s version)</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler.zip">macros/musixtex/egler</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler/">browse the directory</a>) +<dt><tt><i>musixtex (Taupin’s version)</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin/">browse the directory</a>) +<dt><tt><i>musixtex (Egler’s version)</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler.zip">macros/musixtex/egler</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler/">browse the directory</a>) <dt><tt><i>mutex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/mtex.zip">macros/mtex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/mtex/">browse the directory</a>) <dt><tt><i>pmx</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/pmx.zip">support/pmx</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/pmx/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html index 75cc2e990a8..73902e793b9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nameref.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label nameref</title> </head><body> <h3>Referring to things by their name</h3> -<p/>LaTeX’s labelling mechanism is designed for the impersonal world of +<p/>LaTeX’s labelling mechanism is designed for the impersonal world of the academic publication, in which everything has a number: an extension is necessary if we are to record the <em>name</em> of things -we’ve labelled. The two packages available extend the LaTeX +we’ve labelled. The two packages available extend the LaTeX sectioning commands to provide reference by the name of the section. <p/>The <i>titleref</i> package is a simple extension which provides -the command <code>\</code><code>titleref</code>; it is a stand-alone package — don’t use it +the command <code>\</code><code>titleref</code>; it is a stand-alone package — don’t use it in a document in which you also need to use <i>hyperref</i>. <p/>The <i>byname</i> package is part of the <i>smartref</i> bundle and works well with <i>smartref</i>, and works (to an extent) with <i>hyperref</i>, but the links it defines are not hyperlinks. <p/>The <i>memoir</i> class incorporates the functionality of -<i>titleref</i>, but doesn’t work with <i>byname</i> (though a +<i>titleref</i>, but doesn’t work with <i>byname</i> (though a search of <i>comp.text.tex</i> on <a href="groups.google.com">groups.google.com</a> will find a patch to <i>byname</i> to remedy the problem). <p/>The <i>hyperref</i> bundle includes a package <i>nameref</i>, @@ -43,15 +43,15 @@ name-referencing mechanisms: The section name is: \ztitleref{sec:one}. </pre> </blockquote><p> -(One might hope that something of this sort would be the “way of the -future”, but things move slowly in the LaTeX world: don’t hold +(One might hope that something of this sort would be the “way of the +future”, but things move slowly in the LaTeX world: don’t hold your breath.) <p/>Each of <i>titleref</i>, <i>byname</i> and <i>nameref</i> defines a reference command with the same name as the package: <code>\</code><code>titleref</code>, <code>\</code><code>byname</code> and <code>\</code><code>nameref</code>. The <i>nameref</i> package also defines a command <code>\</code><code>byshortnameref</code>, which uses the -optional ‘short’ title argument to the chapter and section commands. -(Although it comes from the same author, <i>zref</i> <em>doesn’t</em> +optional ‘short’ title argument to the chapter and section commands. +(Although it comes from the same author, <i>zref</i> <em>doesn’t</em> define a short-name variant.) <dl> <dt><tt><i>byname.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse the directory</a>) @@ -60,7 +60,7 @@ define a short-name variant.) <dt><tt><i>nameref.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) <dt><tt><i>smartref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse the directory</a>) <dt><tt><i>titleref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/titleref.sty">macros/latex/contrib/misc/titleref.sty</a> -<dt><tt><i>zref.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>zref.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/zref.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html index 70612a9a039..ec299641525 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newans.html @@ -5,25 +5,25 @@ <p/>The FAQ will never be complete, and we always expect that there will be people out there who know better than we do about something or other. We always need to be put right about whatever -we’ve got wrong, and suggestions for improvements, particularly -covering areas we’ve missed, are always needed: mail anything you have +we’ve got wrong, and suggestions for improvements, particularly +covering areas we’ve missed, are always needed: mail anything you have to the <a href="mailto:faq-devel@tex.ac.uk">maintainers</a> <p/>If you have actual material to submit, your contribution is more than ever welcome. Submission in plain text is entirely acceptable, but -if you’re really willing, you may feel free to mark up your submission +if you’re really willing, you may feel free to mark up your submission in the form needed for the FAQ itself. The markup is a -strongly-constrained version of LaTeX — the constraints come from +strongly-constrained version of LaTeX — the constraints come from the need to translate the marked-up text to HTML on the fly (and hence pretty efficiently). There is a file <i>markup-syntax</i> in the FAQ distribution that describes the structure of the -markup, but there’s no real substitute for reading at least some of +markup, but there’s no real substitute for reading at least some of the source (<i>faqbody.tex</i>) of the FAQ itself. If you understand <i>Perl</i>, you may also care to look at the translation code in <i>texfaq2file</i> and <i>sanitize.pl</i> in the -distribution: this isn’t the code actually used on the Web site, but -it’s a close relation and is kept +distribution: this isn’t the code actually used on the Web site, but +it’s a close relation and is kept up to date for development purposes. <dl> <dt><tt><i>FAQ distribution</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (or <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html index b539da2f62a..79538137621 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfontstar.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label newfont*</title> </head><body> -<h3>What’s wrong with <code>\</code><code>newfont</code>?</h3> +<h3>What’s wrong with <code>\</code><code>newfont</code>?</h3> <p/>If all else fails, you <em>can</em> specify a font using the LaTeX -<code>\</code><code>newfont</code> command. The font so specified doesn’t fit into the +<code>\</code><code>newfont</code> command. The font so specified doesn’t fit into the LaTeX font selection mechanism, but the technique can be tempting under several circumstances. The command is merely the thinnest of -wrappers around the <code>\</code><code>font</code> primitive, and doesn’t really fit with +wrappers around the <code>\</code><code>font</code> primitive, and doesn’t really fit with LaTeX at all. A simple, but really rather funny, example of the problems it poses, may be seen in: <blockquote> @@ -19,12 +19,12 @@ problems it poses, may be seen in: \end{document} </pre> </blockquote><p> -(the reader is encouraged to try this). The “A” of <code>\</code><code>LaTeX</code> pretty -much disappears: LaTeX chooses the size on the “A” according to +(the reader is encouraged to try this). The “A” of <code>\</code><code>LaTeX</code> pretty +much disappears: LaTeX chooses the size on the “A” according to <em>its</em> idea of the font size (10pt), but positions it according to -the dimensions of “<code>\</code><code>myfont</code>”, which is more than three times +the dimensions of “<code>\</code><code>myfont</code>”, which is more than three times that size. -<p/>Another “<code>\</code><code>myfont</code>” example arises from an entirely different +<p/>Another “<code>\</code><code>myfont</code>” example arises from an entirely different source. The mini-document: <blockquote> <pre> @@ -35,17 +35,17 @@ source. The mini-document: \end{document} </pre> </blockquote><p> -gives you “German low double quotes” (under the “a”) in place of +gives you “German low double quotes” (under the “a”) in place of the grave accent. This happens because <i>ecrm1000</i> is in a different <a href="FAQ-whatenc.html">font encoding</a> than LaTeX is -expecting — if you use the LaTeX <i>fontenc</i> package to +expecting — if you use the LaTeX <i>fontenc</i> package to select the EC fonts, all these tiresome encoding issues are solved for you, behind the scenes. <p/>There does however remain a circumstance when you will be tempted to -use <code>\</code><code>newfont</code> — viz., to get a font size that doesn’t fall into -the Knuth standard set of sizes: LaTeX (by default) won’t allow you -to use such a size. Don’t despair: see the answer -“<a href="FAQ-fontsize.html">arbitrary font sizes</a>”. +use <code>\</code><code>newfont</code> — viz., to get a font size that doesn’t fall into +the Knuth standard set of sizes: LaTeX (by default) won’t allow you +to use such a size. Don’t despair: see the answer +“<a href="FAQ-fontsize.html">arbitrary font sizes</a>”. <p/><p/> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html index 47f72afd9df..62024971d29 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newfunction.html @@ -30,7 +30,7 @@ say: </blockquote><p> <code>\</code><code>DeclareMathOperator*</code> declares the operator always to have its sub- and superscripts in the -“<a href="FAQ-limits.html"><code>\</code><code>limits</code> position</a>”. +“<a href="FAQ-limits.html"><code>\</code><code>limits</code> position</a>”. <p/>The <i>amsopn</i> command <code>\</code><code>operatorname</code> allows you to introduce <em>ad hoc</em> operators into your mathematics, so <blockquote> @@ -44,12 +44,13 @@ typesets the same as \[ \foo(bar) \] </pre> </blockquote><p> -As with <code>\</code><code>DeclareMathOperator</code> there’s a starred version +As with <code>\</code><code>DeclareMathOperator</code> there’s a starred version <code>\</code><code>operatorname*</code> for sub- and superscripts in the limits position. -<p/>(It should be noted that “log-like” was reportedly a <em>joke</em> on -Lamport’s part; it is of course clear what was meant.) +<p/>(It should be noted that “log-like” was reportedly a <em>joke</em> on +Lamport’s part; it is of course clear what was meant.) <dl> -<dt><tt><i>amsopn.sty</i></tt><dd>In the AMSLaTeX distribution <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) +<dt><tt><i>amsopn.sty</i></tt><dd>Distributed as part of the AMSLaTeX distribution + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsopn.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html index 3face68f978..e369aef8829 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlang.html @@ -16,7 +16,7 @@ Package babel Warning: No hyphenation patterns were loaded for (babel) I will use the patterns loaded for \language=0 instead. </pre> -<p/>The problem is that your TeX system doesn’t know how to hyphenate +<p/>The problem is that your TeX system doesn’t know how to hyphenate Catalan text: you need to tell it how before Babel can do its work properly. To do this, for LaTeX installations, one needs to change <i>language.dat</i> (which is part of the Babel installation); it will @@ -27,22 +27,22 @@ contain a line which, if you remove the comment marker, is supposed to instruct LaTeX to load Catalan hyphenation patterns when you tell it to build a new format. -<p/>Unfortunately, in many Babel distributions, the line just isn’t -right — you need to check the name of the file containing the -patterns you’re going to use. As you can see, in the author’s system, +<p/>Unfortunately, in many Babel distributions, the line just isn’t +right — you need to check the name of the file containing the +patterns you’re going to use. As you can see, in the author’s system, the name is supposed to be <i>cahyphen.tex</i>; however the file -actually present on the system is <i>cahyph.tex</i> — fortunately, +actually present on the system is <i>cahyph.tex</i> — fortunately, the error should prove little more than an inconvenience (most of the files are in better distributions anyway, but an elusive one may be found on CTAN; if you have to retrieve -a new file, ensure that it’s correctly installed, for which see +a new file, ensure that it’s correctly installed, for which see <a href="FAQ-inst-wlcf.html">installing a new package</a>). <p/>Finally, you need to regenerate the formats used (in fact, most users of Babel are using it in their LaTeX documents, so regenerating the LaTeX-related formats will ordinarily be enough; however, the author always generates the lot, regardless). <dl> -<dt>teTeX<dd>It’s possible to do the whole operation in one go, by +<dt>teTeX<dd>It’s possible to do the whole operation in one go, by using the <i>texconfig</i> command: <pre> texconfig hyphen latex @@ -52,20 +52,20 @@ texconfig hyphen latex this case). <p/> Otherwise, to regenerate all formats, do: <br> <code>fmtutil --all</code> -<p/> If you’re willing to think through what you’re doing (this is +<p/> If you’re willing to think through what you’re doing (this is <em>not</em> for the faint-hearted), you can select a sequence of formats and for each one, run: <br> <code>fmtutil --byfmt <<i>formatname</i>></code><br> - where <em><code>formatname</em></code> is something like ‘<code>latex</code>’, + where <em><code>formatname</em></code> is something like ‘<code>latex</code>’, or: <br> <code>fmtutil --byhyphen <<i>hyphenfile</i>></code><br> where <em><code>hyphenfile</em></code> is the file specifying hyphenation - to the format — usually <code>language.dat</code> + to the format — usually <code>language.dat</code> <dt>MiKTeX<dd> On a <i>MiKTeX</i> distribution earlier than v2.0, do: <br> - <code>Start</code>-> - <code>Programs</code>-> - <code>MiKTeX</code>-> - <code>Maintenance</code>-> + <code>Start</code>-> + <code>Programs</code>-> + <code>MiKTeX</code>-> + <code>Maintenance</code>-> <code>Create all format files</code> <p/> or get a DOS window and run:<br> @@ -73,9 +73,9 @@ texconfig hyphen latex <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>-> - <code>Programs</code>-> - <code>MiKTeX 2</code>-> + <code>Start</code>-> + <code>Programs</code>-> + <code>MiKTeX 2</code>-> <code>MiKTeX Options</code>, and select the <code>Languages</code> tab. Select your language from the list, press the <code>Apply</code> button, and then the <code>OK</code> button. Then select the <code>General</code> @@ -86,11 +86,11 @@ texconfig hyphen latex just as for a pre-v2.0 system. </dl> <p/><b><em>Caveat</em>:</b> It is (just) possible that -your TeX system may run out of “pattern memory” while generating +your TeX system may run out of “pattern memory” while generating the new format. Most TeX implementations have fixed-size arrays for storing the details of hyphenation patterns, but although their size is adjustable in most modern distributions, actually changing the -size is a fiddle. If you <em>do</em> find you’ve run out of memory, +size is a fiddle. If you <em>do</em> find you’ve run out of memory, it may be worth scanning the list of languages in your <i>language.dat</i> to see whether any could reasonably be removed. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html index ea8b6608c1d..eccc25614ba 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-newlineargs.html @@ -7,20 +7,20 @@ <blockquote> <pre> ! Missing number, treated as zero. -<to be read again> +<to be read again> g -<*> [grump] +<*> [grump] </pre> </blockquote><p> and those where a single asterisk at the start of a line mysteriously fails to appear in the output. <p/>Both problems arise because <code>\</code><code>\</code> takes optional arguments. The -command <code>\</code><code>\*</code> means “break the line here, and inhibit page break -following the line break”; the command <code>\</code><code>\[</code><<i>dimen</i>><code>]</code> -means “break the line here and add <<i>dimen</i>> extra vertical space -afterwards”. +command <code>\</code><code>\*</code> means “break the line here, and inhibit page break +following the line break”; the command <code>\</code><code>\[</code><<i>dimen</i>><code>]</code> +means “break the line here and add <<i>dimen</i>> extra vertical space +afterwards”. <p/>So why does <code>\</code><code>\</code> get confused by these things at the start of a -line? It’s looking for the first non-blank thing, and in the test it +line? It’s looking for the first non-blank thing, and in the test it uses ignores the end of the line in your input text. <p/>The solution is to enclose the stuff at the start of the new line in braces: @@ -53,6 +53,6 @@ which is a usage this FAQ would not recommend, anyway: refer to the <a href="FAQ-eqnarray.html">reason not to use <code>eqnarray</code></a>. <p/>Note that the <i>amsmath</i> package modifies the behaviour of <code>\\</code> in maths. With <i>amsmath</i>, the <code>eqnarray</code> -example doesn’t need any special measures. +example doesn’t need any special measures. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html index 2970987925d..effa4c8ee08 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noans.html @@ -1,22 +1,22 @@ <head> <title>UK TeX FAQ -- question label noans</title> </head><body> -<h3>You don’t understand the answer</h3> -<p/>While the FAQ maintainers don’t offer a ‘help’ service, they’re -very keen that you understand the answers they’ve already written. -They’re (almost) written “in a vacuum”, to provide something to -cover a set of questions that have arisen; it’s always possible that -they’re written in a way that a novice won’t understand them. +<h3>You don’t understand the answer</h3> +<p/>While the FAQ maintainers don’t offer a ‘help’ service, they’re +very keen that you understand the answers they’ve already written. +They’re (almost) written “in a vacuum”, to provide something to +cover a set of questions that have arisen; it’s always possible that +they’re written in a way that a novice won’t understand them. <p/>Which is where you can help the community. Mail the <a href="mailto:faq-devel@tex.ac.uk">maintainers</a> to report the answer that you find unclear, and (if you can) suggest what we need to clarify. Time permitting (the team is small and all -its members are busy), we’ll try and clarify the answer. This way, +its members are busy), we’ll try and clarify the answer. This way, with a bit of luck, we can together improve the value of this resource to the whole community. <p/>Note that the FAQ development email address is not for -answering questions: it’s for you to suggest which questions we should +answering questions: it’s for you to suggest which questions we should work on, or new questions we should answer in future editions. <p/>Those who simply ask questions at that address will be referred to <a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a> or to <i>comp.text.tex</i>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html index 64b7c2f1ad4..021f1c1e247 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nocitestar.html @@ -6,14 +6,14 @@ requirement. The command <code>\</code><code>nocite{*}</code> is specially treated, and causes BibTeX to generate bibliography entries for every entry in each <code>.bib</code> file listed in your <code>\</code><code>bibliography</code> statement, so -that after a LaTeX–BibTeX–LaTeX sequence, you have a +that after a LaTeX–BibTeX–LaTeX sequence, you have a document with the whole thing listed. -<p/>Note that LaTeX <em>doesn’t</em> produce +<p/>Note that LaTeX <em>doesn’t</em> produce -“<code>Citation ... undefined</code>” or -“<code>There were undefined references</code>” warnings in respect of -<code>\</code><code>nocite{*}</code>. This isn’t a problem if you’re running -LaTeX “by hand” (you <em>know</em> exactly how many times you have +“<code>Citation ... undefined</code>” or +“<code>There were undefined references</code>” warnings in respect of +<code>\</code><code>nocite{*}</code>. This isn’t a problem if you’re running +LaTeX “by hand” (you <em>know</em> exactly how many times you have to run things), but the lack might confuse automatic processors that scan the log file to determine whether another run is necessary. <p/>A couple of packages are available, that aim to reduce the impact of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html index 4c0b9128d29..84a4c2255f7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nodollar.html @@ -1,21 +1,21 @@ <head> <title>UK TeX FAQ -- question label nodollar</title> </head><body> -<h3>“Missing <code>$</code> inserted”</h3> +<h3>“Missing <code>$</code> inserted”</h3> <p/>There are certain things that <em>only</em> work in maths mode. If your document is not in maths mode and you have an <code>_</code> or a <code>^</code> character, TeX (and by inheritance, LaTeX too) will say <pre> ! Missing $ inserted </pre> -as if you couldn’t possibly have misunderstood the import of what you +as if you couldn’t possibly have misunderstood the import of what you were typing, and the only possible interpretation is that you had committed a typo in failing to enter maths mode. TeX, therefore, -tries to patch things up by inserting the <code>$</code> you ‘forgot’, so that +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. -<p/>It’s not just the single-character maths sub- and superscript -operators: anything that’s built in or declared as a maths operation, +<p/>It’s not just the single-character maths sub- and superscript +operators: anything that’s built in or declared as a maths operation, from the simplest lower-case <code>\</code><code>alpha</code> through the inscrutable <code>\</code><code>mathchoice</code> primitive, and beyond, will provoke the error if misused in text mode. @@ -24,6 +24,6 @@ mode for the execution of its argument, if necessary: so if you want an <code>\</code><code>alpha</code> in your running text, say <code>\</code><code>ensuremath{<code>\</code><code>alpha</code>}</code>; if the bit of running text somehow transmutes into a bit of mathematics, the <code>\</code><code>ensuremath</code> will become -a no-op, so it’s pretty much always safe. +a no-op, so it’s pretty much always safe. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html index 5dab769aeba..34d3954d1ab 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nofm.html @@ -1,14 +1,14 @@ <head> <title>UK TeX FAQ -- question label nofm</title> </head><body> -<h3>Page numbering “<<i>n</i>> of <<i>m</i>>”</h3> +<h3>Page numbering “<<i>n</i>> of <<i>m</i>>”</h3> <p/>Finding the page number of the last page of a document, from within the document, is somewhat tricky. The <i>lastpage</i> package is therefore supplied to make life easy for us all; it defines a label <code>LastPage</code> whose number is <em>right</em> (after sufficiently many passes through LaTeX, of course). The <i>memoir</i> class also -defines a “last page” label. +defines a “last page” label. <p/>The documentation of the <i>fancyhdr</i> package spells out exactly how one might actually use this information to produce page numbering as suggested in the question. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html index 439370de630..aad7df886b4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nohyph.html @@ -1,32 +1,32 @@ <head> <title>UK TeX FAQ -- question label nohyph</title> </head><body> -<h3>My words aren’t being hyphenated</h3> -<p/>Let’s assume you’ve selected the right TeX ‘language’ — as -explained in <a href="FAQ-hyphen.html">“how hyphenation works”</a>, -you’re not likely to get the correct results typesetting one language +<h3>My words aren’t being hyphenated</h3> +<p/>Let’s assume you’ve selected the right TeX ‘language’ — as +explained in <a href="FAQ-hyphen.html">“how hyphenation works”</a>, +you’re not likely to get the correct results typesetting one language using the hyphenation rules of another. (Select the proper language, -using <i>babel</i> if you’re a LaTeX user. This may reveal that +using <i>babel</i> if you’re a LaTeX user. This may reveal that you need another set of hyphenation patterns; see -<a href="FAQ-newlang.html">“using a new language”</a> for advice on how +<a href="FAQ-newlang.html">“using a new language”</a> for advice on how to install it.) <p/>So what else can go wrong? <ul> <li> Since TeX version 3.0, the limits on how near to either end of a word hyphenation may take place have been programmable (see - <a href="FAQ-weirdhyphen.html">“weird hyphenation”</a>), and for some + <a href="FAQ-weirdhyphen.html">“weird hyphenation”</a>), and for some reason the values in question may have been corrupted in some macros - you are using. TeX won’t hyphenate less than <code>\</code><code>lefthyphenmin</code> + you are using. TeX won’t hyphenate less than <code>\</code><code>lefthyphenmin</code> characters after the start of a word, nor less than - <code>\</code><code>righthyphenmin</code> before the end of a word; thus it won’t + <code>\</code><code>righthyphenmin</code> before the end of a word; thus it won’t hyphenate a word shorter than the sum of the two minima, at all. - For example, since the minima are 2 and 3 for English, TeX won’t + For example, since the minima are 2 and 3 for English, TeX won’t hyphenate a word shorter than 5 letters long, if it believes the word to be English. -<li> TeX won’t hyphenate a word that’s already been hyphenated. +<li> TeX won’t hyphenate a word that’s already been hyphenated. For example, the (caricature) English surname Smyth-Postlethwaite - wouldn’t hyphenate, which could be troublesome. This is correct + wouldn’t hyphenate, which could be troublesome. This is correct English typesetting style (it may not be correct for other languages), but if needs must, you can replace the hyphen in the name with a <code>\</code><code>hyph</code> command, defined @@ -36,15 +36,15 @@ to install it.) </pre> </blockquote><p> This is <em>not</em> the sort of thing this FAQ would - ordinarily recommend… The <i>hyphenat</i> package defines a + ordinarily recommend… The <i>hyphenat</i> package defines a bundle of such commands (for introducing hyphenation points at various punctuation characters). <li> There may be accents in the word. The causes of and remedies for this effect are discussed in <a href="FAQ-hyphenaccents.html">accents and hyphens</a>. -<li> The hyphenation may simply not have been spotted; while TeX’s - algorithm is good, it’s not infallible, and it does miss perfectly +<li> The hyphenation may simply not have been spotted; while TeX’s + algorithm is good, it’s not infallible, and it does miss perfectly good hyphenations in some languages. When this happens, you need to give TeX <em>explicit</em> instructions on how to hyphenate. </ul> @@ -53,11 +53,11 @@ Provided that the word will hyphenate at all (that is, it is not prevented from hyphenating by any of the other restrictions above), the command will override anything the hyphenation patterns might dictate. The command takes one or more hyphenated words as -argument — <code>\</code><code>hyphenation{ana-lysis pot-able}</code>; note that -(as here, for analysis) you can use the command to overrule TeX’s +argument — <code>\</code><code>hyphenation{ana-lysis pot-able}</code>; note that +(as here, for analysis) you can use the command to overrule TeX’s choice of hyphenation (ana-lysis is the British etymological hyphenation; some feel the American hyphenation feels -‘unfortunate’…). +‘unfortunate’…). <dl> <dt><tt><i>hyphenat.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html index 5bc40aaa264..eaa04bd55a7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noline.html @@ -12,9 +12,9 @@ See the LaTeX manual or LaTeX Companion for explanation. </blockquote><p> comes in reaction to you giving LaTeX a <code>\</code><code>\</code> command at a time -when it’s not expecting it. The commonest case is where you’ve +when it’s not expecting it. The commonest case is where you’ve decided you want the label of a list item to be on a line of its own, -so you’ve written (for example): +so you’ve written (for example): <blockquote> <pre> \begin{description} @@ -24,15 +24,15 @@ so you’ve written (for example): </pre> </blockquote><p> <code>\</code><code>\</code> is actually a rather bad command to use in this case (even if -it worked), since it would force the ‘paragraph’ that’s made up of the +it worked), since it would force the ‘paragraph’ that’s made up of the text of the item to terminate a line which has nothing on it but the -label. This would lead to an “<code>Underfull \hbox</code>” warning message -(usually with ‘infinite’ badness of 10000); while this message doesn’t +label. This would lead to an “<code>Underfull \hbox</code>” warning message +(usually with ‘infinite’ badness of 10000); while this message doesn’t do any actual harm other than slowing down your LaTeX run, any -message that doesn’t convey any information distracts for no useful +message that doesn’t convey any information distracts for no useful purpose. <p/>The proper solution to the problem is to write a new sort of -<code>description</code> environment, that does just what you’re after. (The +<code>description</code> environment, that does just what you’re after. (The <a href="FAQ-books.html"><em>LaTeX Companion</em></a> offers a rather wide selection of variants of these things.) @@ -49,7 +49,7 @@ which fills out the under-full line before forcing its closure. The <i>expdlist</i> package provides the same functionality with its <code>\</code><code>breaklabel</code> command, and <i>mdwlist</i> provides it via its <code>\</code><code>desclabelstyle</code> command. -<p/>The other common occasion for the message is when you’re using the +<p/>The other common occasion for the message is when you’re using the <code>center</code> (or <code>flushleft</code> or <code>flushright</code>) environment, and have decided you need extra separation between lines in the environment: @@ -62,7 +62,7 @@ in the environment: \end{center} </pre> </blockquote><p> -The solution here is plain: use the <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> takes an optional argument, which specifies how much extra space to add; the required effect in the text above can @@ -77,7 +77,7 @@ be had by saying: </blockquote><p> <dl> <dt><tt><i>expdlist.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse the directory</a>) -<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) +<dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mdwlist.html">catalogue entry</a> </dl> <p/> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html index 4071321a636..ad42197a11e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonfree.html @@ -13,7 +13,7 @@ which packages may be distributed. <p/>The CTAN team decided that it would be useful for users (and distributors, not to say package authors) to separate packages that were candidates for distribution, and those that were in some sense -“not free”. Thus was the <code>nonfree</code> tree born. +“not free”. Thus was the <code>nonfree</code> tree born. <p/>From the start, the <code>nonfree</code> tree was controversial: the terms under which a package would be placed on the tree were hotly contested, and the CTAN team were only able slowly to populate @@ -23,28 +23,28 @@ have been completed. good proportion of the packages it describes (though there remain several for which the licence is unknown, which is as good, for the distributors, as a licence forbidding distribution). Since the -catalogue’s coverage of CTAN is good (and slowly improving), +catalogue’s coverage of CTAN is good (and slowly improving), the general rule for distributors has become <blockquote> -“if the package is listed in the catalogue, check there to see +“if the package is listed in the catalogue, check there to see whether you should distribute; if the package is not listed in the -catalogue, don’t think of distributing it”. +catalogue, don’t think of distributing it”. </blockquote><p> (The catalogue only has a modest <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of licences</a>, but it covers the set used -by packages on CTAN, with a wild-card “<code>other-free</code>” +by packages on CTAN, with a wild-card “<code>other-free</code>” which covers packages that the CTAN administrators believe to -be free even though the authors haven’t used a standard licence.) -<p/>There is a corollary to the ‘general rule’: if you notice something +be free even though the authors haven’t used a standard licence.) +<p/>There is a corollary to the ‘general rule’: if you notice something that ought to be in the distributions, for which there is no catalogue entry, please let the CTAN team (<a href="mailto:ctan@dante.de"><i>ctan@dante.de</i></a>) know. -It may well be that the package has simply been missed, but some aren’t -catalogued because there’s no documentation and the team just doesn’t +It may well be that the package has simply been missed, but some aren’t +catalogued because there’s no documentation and the team just doesn’t understand the package. <p/>In the light of the above, the <code>nonfree</code> tree is being dismantled, and its contents moved (or moved <em>back</em>) to the main -CTAN tree. So the answer to the question is, now, “the +CTAN tree. So the answer to the question is, now, “the nonfree tree was a part of CTAN, whose contents are now in -the main tree”. +the main tree”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html index d7062c80917..6258bab8ba5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonpdfsp.html @@ -10,21 +10,21 @@ able to generate its own output, and in this mode of operation has no need of <code>\</code><code>special</code> commands (which allow the user to pass information to the driver being used to generate output). <p/>Why does this happen? LaTeX users, nowadays, hardly ever use -<code>\</code><code>special</code> commands on their own — they employ packages to do the +<code>\</code><code>special</code> commands on their own — they employ packages to do the job for them. Some packages will generate <code>\</code><code>special</code> commands -however they are invoked: <i>pstricks</i> is an example (it’s very -raison d’être is to emit PostScript code in a sequence of <code>\</code><code>special</code> +however they are invoked: <i>pstricks</i> is an example (it’s very +raison d’être is to emit PostScript code in a sequence of <code>\</code><code>special</code> commands). <i>Pstricks</i> may be dealt with by other means (the <i>pdftricks</i> package offers a usable technique). <p/>More amenable to correction, but more confusing, are packages (such as <i>color</i>, <i>graphics</i> and <i>hyperref</i>) that -specify a “driver”. These packages have plug-in modules that +specify a “driver”. These packages have plug-in modules that determine what <code>\</code><code>special</code> (or other commands) are needed to generate any given effect: the <code>pdftex</code> driver for such packages knows not to generate <code>\</code><code>special</code> commands. In most circumstances, you can let the system itself choose which driver you need; in this case everything will act properly when you switch to using PDFLaTeX. If -you’ve been using <i>dvips</i> (and specifying the <code>dvips</code> driver) +you’ve been using <i>dvips</i> (and specifying the <code>dvips</code> driver) or <i>dvipdfm</i> (for which you have to specify the driver), and decide to try PDFLaTeX, you <em>must</em> remove the <code>dvips</code> or <code>dvipdfm</code> driver specification from the package options, and let the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html index a80532a32c6..9e41edb1620 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nonum.html @@ -1,9 +1,9 @@ <head> <title>UK TeX FAQ -- question label nonum</title> </head><body> -<h3>“Missing number, treated as zero”</h3> -<p/>In general, this means you’ve tried to assign something to a count, -dimension or skip register that isn’t (in TeX’s view of things) a +<h3>“Missing number, treated as zero”</h3> +<p/>In general, this means you’ve tried to assign something to a count, +dimension or skip register that isn’t (in TeX’s view of things) a number. Usually the problem will become clear using the <a href="FAQ-erroradvice.html">ordinary techniques of examining errors</a>. <p/>Two LaTeX-specific errors are commonly aired on the newsgroups. @@ -12,12 +12,12 @@ number. Usually the problem will become clear using the exemplified by the following error text: <pre> ! Missing number, treated as zero. -<to be read again> +<to be read again> \relax l.21 \begin{Ventry}{Return values} </pre> The problem arises because, in its first edition, the -<em>Companion</em>’s examples always assumed that the <i>calc</i> +<em>Companion</em>’s examples always assumed that the <i>calc</i> package is loaded: this fact is mentioned in the book, but often not noticed. The remedy is to load the <i>calc</i> package in any document using such examples from the <em>Companion</em>. (The problem @@ -34,13 +34,13 @@ has no equivalent in LaTeX2e. The obvious solution is to rewrite the paths so that LaTeX 2.09 packages are chosen only as a last resort so that the startlingly simple LaTeX2e <i>times</i> package will be picked up. Better still is to replace the whole thing with -something more modern still; current <i>psnfss</i> doesn’t provide -a <i>times</i> package — the alternative <i>mathptmx</i> +something more modern still; current <i>psnfss</i> doesn’t provide +a <i>times</i> package — the alternative <i>mathptmx</i> incorporates <i>Times</i>-like mathematics, and a sans-serif face based on <i>Helvetica</i>, but scaled to match <i>Times</i> text rather better. <dl> -<dt><tt><i>calc.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>calc.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/calc.html">catalogue entry</a> <dt><tt><i>Examples for LaTeX Companion</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse the directory</a>) <dt><tt><i>The psnfss bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html index 4805db70805..4d0db85dfb5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html @@ -8,29 +8,29 @@ same page; it turns out to be surprisingly tricky to arrange this. does this sort of thing for you. It proceeds by setting infinite penalties for all sorts of page-break situations; but in many situations where you want to prevent a page break, -<code>samepage</code> doesn’t help. If you’re trying to keep running +<code>samepage</code> doesn’t help. If you’re trying to keep running text together, you need to end the paragraph inside the environment (see <a href="FAQ-paraparam.html">preserving paragraph parameters</a>). Also, if the things you are trying to keep together insert their own pagebreak hints, <code>samepage</code> has no power over them: a good -example is list items — they suggest page breaks between them. Even -if <code>samepage</code> <em>does</em> work, it’s likely to leave stuff +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> (or a <code>minipage</code> if it contains things like verbatim text that may not be in the argument of a <code>\</code><code>parbox</code>). The resulting box -certainly <em>won’t</em> break between pages, but that’s not to say that +certainly <em>won’t</em> break between pages, but that’s not to say that it will actually do what you want it to do: again, the box may be left jutting out at the bottom of the page. -<p/>Why do neither of these obvious things work? Because TeX can’t +<p/>Why do neither of these obvious things work? Because TeX can’t really distinguish between infinitely awful things. -<code>Samepage</code> will make any possible break point “infinitely -bad” and boxes don’t even offer the option of breaks, but if the +<code>Samepage</code> will make any possible break point “infinitely +bad” and boxes don’t even offer the option of breaks, but if the alternative is the leave an infinitely bad few centimetres of blank paper at the bottom of the page, TeX will take the line of least resistance and do nothing. <p/>This problem still arises even if you have <code>\</code><code>raggedbottom</code> in -effect: TeX doesn’t notice the value of <em>that</em> until it starts +effect: TeX doesn’t notice the value of <em>that</em> until it starts actually shipping a page out. One approach is to set: <blockquote> <pre> @@ -40,7 +40,7 @@ actually shipping a page out. One approach is to set: </blockquote><p> The <code>10pt</code> offers a hint to the output routine that the column is stretchable; this will cause TeX to be more tolerant of the need to -stretch while building the page. If you’re doing this as a temporary +stretch while building the page. If you’re doing this as a temporary measure, cancel the change to <code>\</code><code>topskip</code> by: <blockquote> <pre> @@ -54,7 +54,7 @@ could well have an effect if <code>\</code><code>flushbottom</code> was in effec <p/>An alternative (which derives from a suggestion by Knuth in the TeXbook) is the package <i>needspace</i> or the <i>memoir</i> class, which both define a command <code>\</code><code>needspace</code> whose argument tells it -what space is needed. If the space isn’t available, the current page +what space is needed. If the space isn’t available, the current page is cleared, and the matter that needs to be kept together will be inserted on the new page. For example, if 4 lines of text need to be kept together, the sequence @@ -63,7 +63,7 @@ kept together, the sequence \par \needspace{4\baselineskip} % the stuff that must stay together -<text generating lines 1-4> +<text generating lines 1-4> % now stuff we don't mind about </pre> </blockquote><p> @@ -84,7 +84,7 @@ patch would be: } </pre> </blockquote><p> -While the trick works for consecutive sequences of blocks, it’s +While the trick works for consecutive sequences of blocks, it’s slightly tricky to get out of such sequences unless the sequence is interrupted by a forced page break (such as <code>\</code><code>clearpage</code>, which may be introduced by a <code>\</code><code>chapter</code> command, or the end of the document). @@ -93,14 +93,14 @@ forced onto a new page, regardless of whether it actually needs it. <p/>If one is willing to accept that not everything can be accomplished totally automatically, the way to go is to typeset the document and to check for things that have the potential to give trouble. In such a -scenario (which has Knuth’s authority behind it, if one is to believe +scenario (which has Knuth’s authority behind it, if one is to believe the rather few words he says on the subject in the TeXbook) one can decide, case by case, how to deal with problems at the last proof-reading stage. The alternatives are to insert <code>\</code><code>clearpage</code> commands as necessary, or to use <code>\</code><code>enlargethispage</code>. Supposing you have a line or two that stray: issue the command <code>\</code><code>enlargethispage{2<code>\</code><code>baselineskip</code>}</code> and two lines are -added to the page you’re typesetting. It depends on the document +added to the page you’re typesetting. It depends on the document whether this looks impossibly awful or entirely acceptable, but the command remains a useful item in the armoury. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html index 711cca42537..059b0abdf14 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopageno.html @@ -19,12 +19,12 @@ with those separately, as described below. page. Note that, in the standard classes, <code>\</code><code>maketitle</code> and <code>\</code><code>chapter</code> use <code>\</code><code>thispagestyle</code> internally, so your call must be <em>after</em> those commands. -<p/>Unfortunately, <code>\</code><code>thispagestyle</code> doesn’t work for <i>book</i> or +<p/>Unfortunately, <code>\</code><code>thispagestyle</code> doesn’t work for <i>book</i> or <i>report</i> <code>\</code><code>part</code> commands: they set the page style (as do <code>\</code><code>chapter</code> commands), but then they advance to the next page so that you have no opportunity to change the style using <code>\</code><code>thispagestyle</code>. The present author has proposed solving the -problem with the following “grubby little patch”, on +problem with the following “grubby little patch”, on <i>comp.text.tex</i>: <blockquote> <pre> @@ -35,7 +35,7 @@ problem with the following “grubby little patch”, on </pre> </blockquote><p> <p/>Both the <i>KOMA-script</i> classes and <i>memoir</i> have separate -page styles for the styles of various “special” pages, so, in a +page styles for the styles of various “special” pages, so, in a <i>KOMA</i> class document one might say: <blockquote> <pre> @@ -48,7 +48,7 @@ while <i>memoir</i> will do the job with </blockquote><p> <p/>An alternative (in all classes) is to use the rather delightful <code>\</code><code>pagenumbering{gobble}</code>; this has the simple effect that any -attempt to print a page number produces nothing, so there’s no issue +attempt to print a page number produces nothing, so there’s no issue about preventing any part of LaTeX from printing the number. However, the <code>\</code><code>pagenumbering</code> command does have the side effect that it resets the page number (to 1), so it is unlikely to be helpful @@ -62,8 +62,8 @@ the construction of the page header and footer; so one can say </pre> </blockquote><p> which will also suppress the printing of the page number. -<p/>Neither of these “suppress the page number” techniques touches the -page style in use; in practice this means they don’t make sense unless +<p/>Neither of these “suppress the page number” techniques touches the +page style in use; in practice this means they don’t make sense unless you are using <code>\</code><code>pagestyle{plain}</code> <dl> <dt><tt><i>fancyhdr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html index df07fef5dac..d1380661d47 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-noroom.html @@ -1,13 +1,13 @@ <head> <title>UK TeX FAQ -- question label noroom</title> </head><body> -<h3>No room for a new ‘<em>thing</em>’</h3> +<h3>No room for a new ‘<em>thing</em>’</h3> <p/>The technology available to Knuth at the time TeX was written is said to have been particularly poor at managing dynamic storage; as a result much of the storage used within TeX is allocated as fixed arrays, in the reference implementations. Many of these fixed arrays are expandable in modern TeX implementations, but size of the -arrays of “registers” is written into the specification as being 256 +arrays of “registers” is written into the specification as being 256 (usually); this number may not be changed if you still wish to call the result TeX @@ -16,28 +16,28 @@ the result TeX message saying <blockquote> <pre> -! No room for a new \<thing>. +! No room for a new \<thing>. </pre> </blockquote><p> The <code>\</code><code>thing</code>s in question may be <code>\</code><code>count</code> (the object underlying -LaTeX’s <code>\</code><code>newcounter</code> command), <code>\</code><code>skip</code> (the object underlying -LaTeX’s <code>\</code><code>newlength</code> command), <code>\</code><code>box</code> (the object underlying -LaTeX’s <code>\</code><code>newsavebox</code> command), or <code>\</code><code>dimen</code>, <code>\</code><code>muskip</code>, +LaTeX’s <code>\</code><code>newcounter</code> command), <code>\</code><code>skip</code> (the object underlying +LaTeX’s <code>\</code><code>newlength</code> command), <code>\</code><code>box</code> (the object underlying +LaTeX’s <code>\</code><code>newsavebox</code> command), or <code>\</code><code>dimen</code>, <code>\</code><code>muskip</code>, <code>\</code><code>toks</code>, <code>\</code><code>read</code>, <code>\</code><code>write</code> or <code>\</code><code>language</code> (all types of object -whose use is “hidden” in LaTeX; the limit on the number of +whose use is “hidden” in LaTeX; the limit on the number of <code>\</code><code>read</code> or <code>\</code><code>write</code> objects is just 16). -<p/>There is nothing that can directly be done about this error, as you can’t +<p/>There is nothing that can directly be done about this error, as you can’t extend the number of available registers without extending TeX itself. Of course, <a href="FAQ-etex.html">e-TeX</a>, <a href="FAQ-omegaleph.html">Omega</a> and <a href="FAQ-luatex.html">LuaTeX</a> -all do this, as does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. +all do this, as does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. <p/>One common way to encounter one of these error messages is to have broken macros of some sort, or incorrect usage of macros (an example is discussed in <a href="FAQ-epsf.html">epsf problems</a>). <p/>However, sometimes one just <em>needs</em> more than TeX can offer, -and when this happens, you’ve just got to work out a different way of +and when this happens, you’ve just got to work out a different way of doing things. An example is the <a href="FAQ-usepictex.html">difficulty of loading PicTeX with LaTeX</a>. The more modern drawing package, <i>pgf</i> with its higher-level @@ -45,14 +45,14 @@ interface <i>TikZ</i> is a common problem. <p/>In such cases, it is usually possible to use the <a href="FAQ-etex.html">e-TeX</a> extensions (all modern distributions provide them). The LaTeX package <i>etex</i> modifies the register allocation -mechanism to make use of e-TeX’s extended register sets. +mechanism to make use of e-TeX’s extended register sets. <i>Etex</i> is a derivative of the Plain TeX macro file <i>etex.src</i>, which is used in building the e-TeX Plain format; both files are part of the e-TeX distribution and are available in current distributions. <p/>It is possible that, even with <i>etex</i> loaded, you still find yourself running out of things. Problems could be caused by packages -that use large numbers of “inserts” (combinations of counter, box, +that use large numbers of “inserts” (combinations of counter, box, dimension and skip registers, used for storing floats and footnotes). <i>Morefloats</i> does this, of course (naturally enough, allocating new floats), and footnote packages such as @@ -70,7 +70,7 @@ inserts immediately: \reserveinserts{28} </pre> </blockquote><p> -<p/>Unfortunately, e-TeX doesn’t help with <code>\</code><code>read</code> or <code>\</code><code>write</code> +<p/>Unfortunately, e-TeX doesn’t help with <code>\</code><code>read</code> or <code>\</code><code>write</code> objects (and neither will the <i>etex</i> package). <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html index 09247c59096..13b331a0481 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html @@ -2,54 +2,54 @@ <title>UK TeX FAQ -- question label notWYSIWYG</title> </head><body> <h3>Why is TeX not a WYSIWYG system?</h3> -<p/>WYSIWYG is a marketing term (“What you see is what you get”) for +<p/>WYSIWYG is a marketing term (“What you see is what you get”) for a particular style of text processor. WYSIWYG systems are characterised by two principal claims: that you type what you want to print, and that what you see on the screen as you type is a close approximation to how your text will finally be printed. <p/>The simple answer to the question is, of course, that TeX was conceived long before the marketing term, at a time when the marketing -imperative wasn’t perceived as significant. However, that was a long -time ago: why has nothing been done with the “wonder text processor” +imperative wasn’t perceived as significant. However, that was a long +time ago: why has nothing been done with the “wonder text processor” to make it fit with modern perceptions? -<p/>There are two answers to this. First, the simple “things <em>have</em> -been done” (but they’ve not taken over the TeX world); and second, -“there are philosophical reasons why the way TeX has developed is -ill-suited to the WYSIWYG style”. +<p/>There are two answers to this. First, the simple “things <em>have</em> +been done” (but they’ve not taken over the TeX world); and second, +“there are philosophical reasons why the way TeX has developed is +ill-suited to the WYSIWYG style”. Indeed, there is a fundamental problem with applying WYSIWYG techniques to TeX: the complexity of TeX makes it hard to get the -equivalent of TeX’s output without actually running TeX. -<p/>A celebrated early system offering “WYSIWYG using TeX” came from the +equivalent of TeX’s output without actually running TeX. +<p/>A celebrated early system offering “WYSIWYG using TeX” came from the VorTeX project: a pair of (early) Sun workstations worked in tandem, one handling the user interface while the other beavered away in the background typesetting the result. VorTeX was quite impressive for its time, but the two workstations combined had hugely less power than the average sub-thousand dollar Personal Computer nowadays, and its code has not proved portable (it never even made the -last ‘great’ TeX version change, at the turn of the 1990s, to +last ‘great’ TeX version change, at the turn of the 1990s, to TeX version 3). Modern systems that are similar in their approach are Lightning Textures (an extension of -Blue Sky’s original TeX system for the Macintosh), and Scientific +Blue Sky’s original TeX system for the Macintosh), and Scientific Word (which can also cooperate with a computer algebra system); both these systems are <a href="FAQ-commercial.html">commercially available</a>. <p/>The issue has of recent years started to attract attention from TeX developers, and several interesting projects addressing the -“<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>” +“<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>” are in progress. <p/>Nevertheless, the TeX world has taken a long time to latch onto the idea of WYSIWYG. -Apart from simple arrogance (“we’re better, and have no need to -consider the petty doings of the commercial word processor market”), +Apart from simple arrogance (“we’re better, and have no need to +consider the petty doings of the commercial word processor market”), there is a real conceptual difference between the word processor model -of the world and the model LaTeX and ConTeXt employ — the idea of -“markup”. “Pure” markup expresses a logical model of a document, +of the world and the model LaTeX and ConTeXt employ — the idea of +“markup”. “Pure” markup expresses a logical model of a document, where every object within the document is labelled according to what it is rather than how it should appear: appearance is deduced from the properties of the type of object. Properly applied, markup can provide valuable assistance when it comes to re-use of documents. <p/>Established WYSIWYG systems find the expression of this sort of structured markup difficult; however, markup <em>is</em> starting to -appear in the lists of the commercial world’s requirements, for two +appear in the lists of the commercial world’s requirements, for two reasons. First, an element of markup helps impose style on a document, and commercial users are increasingly obsessed with uniformity of style; and second, the increasingly pervasive use of diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html index 27a057382c5..c504e3e2a0f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-numbersets.html @@ -7,35 +7,35 @@ other standard number sets. Traditionally these were typeset in bold. Because, in the ordinary course of events, mathematicians do not have access to bold chalk, they invented special symbols that are now often used for the number sets; these symbols are known as -“blackboard bold” (or double-stroked fonts); in place of the heavier +“blackboard bold” (or double-stroked fonts); in place of the heavier strokes of a bold font, (some) strokes of the letters are doubled. -The minimum useful set is upper-case letters ‘I’, ‘N’, ‘R’, ‘Q’ and -‘Z’; some fonts offer a figure ‘1’ (for a unit matrix — not a number +The minimum useful set is upper-case letters ‘I’, ‘N’, ‘R’, ‘Q’ and +‘Z’; some fonts offer a figure ‘1’ (for a unit matrix — not a number set at all). <p/>A set of blackboard bold capitals is available in the AMS <i>msbm</i> fonts (<i>msbm</i> is available at a range of design sizes, with names such as <i>msbm10</i>). The pair of font families (the other is called <i>msam</i>) have a large number of -mathematical symbols to supplement those provided in the Knuth’s +mathematical symbols to supplement those provided in the Knuth’s original TeX distribution, and are available in Type 1 format in modern distributions. Support files for using the fonts, both under Plain TeX and LaTeX (packages <i>amssymb</i> and <i>amsfonts</i>), are available. The font shape is a rather -austere sans, which many people don’t like (though it captures the +austere sans, which many people don’t like (though it captures the essence of quickly-chalked writing rather well). <p/>The <i>bbold</i> family is set of blackboard bold fonts written in Metafont. This set offers blackboard bold forms of lower-case letters; the font source directory also contains sources for a LaTeX package that enables use of the fonts. The fonts are not available in Type 1 format. <p/>The <i>bbm</i> family claims to provide -‘blackboard’ versions of most of the <i>cm</i> fonts … including +‘blackboard’ versions of most of the <i>cm</i> fonts … including the bold and bold-extended series. Again, the fonts are designed in Metafont and are not available in Type 1 format. LaTeX macro support comes from a package by Torsten Hilbrich. <p/>The <i>doublestroke</i> family comes in just roman and sans shapes, at a single weight, and is available both as Metafont sources and as Type 1; the font covers the uppercase latin letters, -lowercase ‘h’ and ’k’, and the digit ‘1’. +lowercase ‘h’ and ’k’, and the digit ‘1’. <p/>A document that shows the <i>bbm</i>, <i>bbold</i>, <i>doublestroke</i> and <i>msbm</i> fonts, so that you can get a feel for their appearance, is available (CTAN package @@ -44,15 +44,15 @@ a feel for their appearance, is available (CTAN package may be found in the steadily increasing set of complete families, both commercial and free, that have been prepared for use with (La)TeX (see -“<a href="FAQ-psfchoice.html">choice of outline fonts</a>”). +“<a href="FAQ-psfchoice.html">choice of outline fonts</a>”). Of the free sets, the <i>txfonts</i> and <i>pxfonts</i> families both come with replicas of <i>msam</i> and <i>msbm</i> (though, as noted elsewhere, there are other reasons not to use these -fonts). The <i>mathpazo</i> family includes a “mathematically -significant” choice of blackboard bold characters, and the +fonts). The <i>mathpazo</i> family includes a “mathematically +significant” choice of blackboard bold characters, and the <i>fourier</i> fonts contain blackboard bold upper-case letters, -the digit ‘1’, and lower-case ‘k’. -<p/>The “lazy person’s” blackboard bold macros: +the digit ‘1’, and lower-case ‘k’. +<p/>The “lazy person’s” blackboard bold macros: <blockquote> <pre> \newcommand{\R}{{\textsf{R}\hspace*{-0.9ex}% @@ -68,9 +68,9 @@ the digit ‘1’, and lower-case ‘k’. are almost acceptable at normal size if the surrounding text is <i>cmr10</i> (the position of the vertical bar can be affected by the surrounding font). However, they are not part of a proper maths font, -and do not work in sub- and superscripts. As we’ve seen, there are -plenty of alternatives: that mythical “lazy” person can inevitably -do better than the macros, or anything similar using capital ‘I’ +and do not work in sub- and superscripts. As we’ve seen, there are +plenty of alternatives: that mythical “lazy” person can inevitably +do better than the macros, or anything similar using capital ‘I’ (which looks even worse!). Voluntary (La)TeX effort has redefined the meaning of laziness (in this respect!). <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html index 5c77745f5df..11d6f71a8ab 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oarglikesect.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label oarglikesect</title> </head><body> <h3>Optional arguments like <code>\</code><code>section</code></h3> -<p/>Optional arguments, in macros defined using <code>\</code><code>newcommand</code>, don’t +<p/>Optional arguments, in macros defined using <code>\</code><code>newcommand</code>, don’t quite work like the optional argument to <code>\</code><code>section</code>. The default -value of <code>\</code><code>section</code>’s optional argument is the value of the -mandatory argument, but <code>\</code><code>newcommand</code> requires that you ‘know’ the +value of <code>\</code><code>section</code>’s optional argument is the value of the +mandatory argument, but <code>\</code><code>newcommand</code> requires that you ‘know’ the value of the default beforehand. <p/>The requisite trick is to use a macro in the optional argument: <blockquote> @@ -35,6 +35,6 @@ above would have been programmed: </blockquote><p> In that code, <code>\</code><code>@thing</code> is only ever called with an optional and a mandatory argument; if the default from the <code>\</code><code>newcommand</code> is -invoked, a bug in user code has bitten… +invoked, a bug in user code has bitten… <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html index cfc234fda50..303d8b8a66d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddhyphen.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label oddhyphen</title> </head><body> <h3>(Merely) peculiar hyphenation</h3> -<p/>You may have found that TeX’s famed automatic word-division does +<p/>You may have found that TeX’s famed automatic word-division does not produce the break-points recommended by your dictionary. This may be because TeX is set up for American English, whose rules for word -division (as specified, for example, in Webster’s Dictionary) are +division (as specified, for example, in Webster’s Dictionary) are completely different from the British ones (as specified, for example, in the Oxford Dictionaries). This problem is being addressed by the UK TeX User community (see <i>Baskerville</i>, issue 4.4) but an entirely satisfactory solution will take time; the current status is to be found on CTAN (see -<a href="FAQ-newlang.html">“using a new language”</a> for instructions -on adding this new “language”). +<a href="FAQ-newlang.html">“using a new language”</a> for instructions +on adding this new “language”). <dl> <dt><tt><i>UK patterns</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/language/hyphenation/ukhyphen.tex">language/hyphenation/ukhyphen.tex</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html index af21826a520..ba0c7532cbf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oddpage.html @@ -1,21 +1,21 @@ <head> <title>UK TeX FAQ -- question label oddpage</title> </head><body> -<h3>Finding if you’re on an odd or an even page</h3> +<h3>Finding if you’re on an odd or an even page</h3> <p/><a href="FAQ-marginparside.html">Another question</a> discusses the issue of getting <code>\</code><code>marginpar</code> commands to put their output in the correct margin of two-sided documents. This is an example of the general problem of knowing where a particular bit of text lies: the output routine is asynchronous, and (La)TeX will usually process quite a -bit of the “next” page before deciding to output any page. As a +bit of the “next” page before deciding to output any page. As a result, the <code>page</code> counter (known internally in LaTeX as -<code>\</code><code>c@page</code>) is normally only reliable when you’re actually <em>in</em> +<code>\</code><code>c@page</code>) is normally only reliable when you’re actually <em>in</em> the output routine. <p/>The solution is to use some version of the <code>\</code><code>label</code> mechanism to -determine which side of the page you’re on; the value of the page +determine which side of the page you’re on; the value of the page counter that appears in a <code>\</code><code>pageref</code> command has been inserted in the course of the output routine, and is therefore safe. -<p/>However, <code>\</code><code>pageref</code> itself isn’t reliable: one might hope that +<p/>However, <code>\</code><code>pageref</code> itself isn’t reliable: one might hope that <pre> \ifthenelse{\isodd{\pageref{foo}}}{odd}{even} </pre> @@ -28,12 +28,12 @@ sets a private-use label, and the page reference part of that label is then examined (in a <i>hyperref</i>-safe way) to set a conditional <code>\</code><code>ifoddpage</code> true if the command was issued on an odd page. The <i>memoir</i> class has the same command setting a conditional -<code>\</code><code>ifoddpage</code>. Of course, the <code>\</code><code>label</code> contributes to LaTeX’s -“Rerun to get cross-references right” error messages… +<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 Koma-Script classes have an <code>addmargin*</code> environment that also provides the sorts of facilities that the <i>changepage</i> -offers. Koma-Script’s supporting command is -<code>\</code><code>ifthispageodd{<true>}{<false>}</code> executes different things +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="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changepage.zip">macros/latex/contrib/changepage</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changepage/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html index 8983bd8dc8d..7ba84309216 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ol-books.html @@ -4,19 +4,19 @@ <h3>Freely available (La)TeX books</h3> <p/>People have long argued for (La)TeX books to be made available on the web, and until relatively recently this demand went un-answered. -<p/>The first to appear was Victor Eijkhout’s excellent “TeX by -Topic” in 2001 (it had been published by Addison-Wesley, but was long -out of print). The book is now available on CTAN; it’s not a -beginner’s tutorial but it’s a fine reference. It’s also available, +<p/>The first to appear was Victor Eijkhout’s excellent “TeX by +Topic” in 2001 (it had been published by Addison-Wesley, but was long +out of print). The book is now available on CTAN; it’s not a +beginner’s tutorial but it’s a fine reference. It’s also available, as a printed copy, via the on-line publishers <a href="http://www.lulu.com/content/2555607/">Lulu</a> (not quite free, of -course, but not a <em>bad</em> deal…). -<p/>Addison-Wesley have also released the copyright of “TeX for the -Impatient” by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves, +course, but not a <em>bad</em> deal…). +<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 Free Documentation Licence, and it is available from CTAN. -<p/>Norm Walsh’s “Making TeX Work” (originally published by O’Reilly) +<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 Web page are on CTAN. The book was an excellent resource in diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html index d53ed253afb..e2c6998a531 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-oldfontnames.html @@ -9,7 +9,7 @@ that it had built in to itself. For example, various flavours of <code>\</code><code>frtnrm</code>, <code>\</code><code>svtnrm</code>, <code>\</code><code>twtyrm</code> and <code>\</code><code>twfvrm</code>. These commands were never documented, but certain packages nevertheless used them to achieve effects they needed. -<p/>Since the commands weren’t public, they weren’t included in LaTeX2e; +<p/>Since the commands weren’t public, they weren’t included in LaTeX2e; to use the unconverted LaTeX 2.09 packages under LaTeX2e, you need also to include the <i>rawfonts</i> package (which is part of the LaTeX2e distribution). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html index 95e0577fb15..4e62ec78246 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-omegaleph.html @@ -5,8 +5,8 @@ <p/>Omega was developed as an extension of TeX, to use with multilingual texts, expressed in a variety of input encodings. Omega uses 16-bit, Unicode-encoded, characters. It -provides many innovative concepts, notably including the “translation -process” that takes a character stream and transforms it according to +provides many innovative concepts, notably including the “translation +process” that takes a character stream and transforms it according to various processes that may be internally specified, or be a separate program. <p/>While Omega showed a lot of promise at its mid-1990s announcement, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html index fc84d44c698..96d4544aa72 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-onecolabs.html @@ -20,7 +20,7 @@ the entire page, even in a two-column paper. The required trick is: ] </pre> </blockquote><p> -Unfortunately, with the above <code>\</code><code>thanks</code> won’t work in the +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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html index f42f1325341..aa4a1b7fca2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-optionclash.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label optionclash</title> </head><body> <h3>Option clash for package</h3> -<p/>So you’ve innocently added: +<p/>So you’ve innocently added: <blockquote> <code>\</code><code>usepackage[draft]{graphics}</code> </blockquote><p> @@ -14,12 +14,12 @@ to your document, and LaTeX responds with </blockquote><p> <p/>The error is a complaint about loading a package -<em>with options</em>, more than once (LaTeX doesn’t actually examine -what options there are: it complains because it can’t do anything with +<em>with options</em>, more than once (LaTeX doesn’t actually examine +what options there are: it complains because it can’t do anything with the multiple sets of options). You can load a package any number of times, with no options, and LaTeX will be happy, but you may only supply options when you first load the package. -<p/>So perhaps you weren’t entirely innocent — the error would have +<p/>So perhaps you weren’t entirely innocent — the error would have occurred on the second line of: <blockquote> <code>\</code><code>usepackage[dvips]{graphics}</code><br> @@ -29,21 +29,21 @@ which could quite reasonably (and indeed correctly) have been typed: <blockquote> <code>\</code><code>usepackage[dvips,draft]{graphics}</code> </blockquote><p> -<p/>But if you’ve not made that mistake (even with several lines -separating the <code>\</code><code>usepackage</code> commands, it’s pretty easy to spot), +<p/>But if you’ve not made that mistake (even with several lines +separating the <code>\</code><code>usepackage</code> commands, it’s pretty easy to spot), the problem could arise from something else loading the package for you. How do you find the culprit? The "<code>h</code>" response to the error message tells you which options were loaded each time. -Otherwise, it’s down to the log analysis games discussed in -“<a href="FAQ-erroradvice.html">How to approach errors</a>”; the trick to remember +Otherwise, it’s down to the log analysis games discussed in +“<a href="FAQ-erroradvice.html">How to approach errors</a>”; the trick to remember is that that the process of loading each file is parenthesised in the log; so if package <i>foo</i> loads <i>graphics</i>, the log will contain something like: <blockquote> <pre> -(<path>/foo.sty ... +(<path>/foo.sty ... ... -(<path>/graphics.sty ... +(<path>/graphics.sty ... ...) ... ) @@ -53,7 +53,7 @@ will contain something like: those for <i>foo</i>; the same is of course true if your class <i>bar</i> is the culprit, except that the line will start with the path to <code>bar.cls</code>). -<p/>If we’re dealing with a package that loads the package you are +<p/>If we’re dealing with a package that loads the package you are interested in, you need to ask LaTeX to slip in options when <i>foo</i> loads it. Instead of: <blockquote> @@ -84,7 +84,7 @@ with <code>\</code><code>PassOptionsToPackage</code> <em>before</em> the <code>\ command. <p/>However, if the <i>foo</i> package or the <i>bar</i> class loads <i>graphics</i> with an option of its own that clashes with -what you need in some way, you’re stymied. For example: +what you need in some way, you’re stymied. For example: <blockquote> <code>\</code><code>PassOptionsToPackage{draft}{graphics}</code> </blockquote><p> @@ -92,10 +92,10 @@ where the package or class does: <blockquote> <code>\</code><code>usepackage[final]{graphics}</code> </blockquote><p> -sets <code>final</code> <em>after</em> it’s dealt with option you passed to +sets <code>final</code> <em>after</em> it’s dealt with option you passed to it, so your <code>draft</code> will get forgotten. In extreme cases, -the package might generate an error here (<i>graphics</i> doesn’t -go in for that kind of thing, and there’s no indication that +the package might generate an error here (<i>graphics</i> doesn’t +go in for that kind of thing, and there’s no indication that <code>draft</code> has been forgotten). <p/>In such a case, you have to modify the package or class itself (subject to the terms of its licence). It may prove useful to contact diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-osf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-osf.html index 14d49d054e8..3842fa93ca1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-osf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-osf.html @@ -1,47 +1,47 @@ <head> <title>UK TeX FAQ -- question label osf</title> </head><body> -<h3>Using “old-style” figures</h3> +<h3>Using “old-style” figures</h3> <p/>These numbers are also called medieval or lowercase figures and their use is mostly font-specific. Terminology is confusing since the lining figures (which are now the default) are a relatively recent development (19th century) and before they arrived, oldstyle figures were the norm, even when setting mathematics. (An example is Thomas -Harriot’s <em>Artis Analyticae Praxis</em> published in 1631). In a +Harriot’s <em>Artis Analyticae Praxis</em> published in 1631). In a typical old style 3, 4, 5, 7 and 9 have descenders and 6 and 8 ascend above the x-height; sometimes 2 will also ascend (this last seems to be a variation associated with French typography). <p/>LaTeX provides a command <code>\</code><code>oldstylenums{</code><em>digits</em><code>}</code>, which -by default uses an old-style set embedded in Knuth’s ‘math italic’ -font. The command isn’t sensitive to the font style of surrounding +by default uses an old-style set embedded in Knuth’s ‘math italic’ +font. The command isn’t sensitive to the font style of surrounding text: the glyphs are only available to match the normal medium weight Computer Modern Roman fonts. <p/>The <i>textcomp</i> package changes <code>\</code><code>oldstylenums</code> to use the glyphs in the Text Companion fonts (LaTeX TS1 encoding) when in text mode, and also makes them available using the macros of the -form <code>\</code><code>text<number>oldstyle</code>, e.g., <code>\</code><code>textzerooldstyle</code>. +form <code>\</code><code>text<number>oldstyle</code>, e.g., <code>\</code><code>textzerooldstyle</code>. (Of course, not all font families can provide this facility.) <p/>Some font packages (e.g., <i>mathpazo</i>) make old-style figures available and provide explicit support for making them the default: <code>\</code><code>usepackage[osf]{mathpazo}</code> selects a form where digits are always old-style in text. The <i>fontinst</i> package will -automatically generate “old-style versions” of commercial Adobe Type -1 font families for which “expert” sets are available. -<p/>It’s also possible to make virtual fonts, that offer old-style digits, +automatically generate “old-style versions” of commercial Adobe Type +1 font families for which “expert” sets are available. +<p/>It’s also possible to make virtual fonts, that offer old-style digits, from existing font packages. The <i>cmolddig</i> bundle provides -a such a virtual version of Knuth’s originals, and the <i>eco</i> +a such a virtual version of Knuth’s originals, and the <i>eco</i> or <i>hfoldsty</i> bundles both provide versions of the EC fonts. The <i>lm</i> family offers old-style figures to OpenType users (see below), but we have no stable mapping for <i>lm</i> with old-style digits from the Adobe Type 1 versions of the fonts. <p/>Originally, oldstyle figures were only to be found the expert sets of commercial fonts, but now they are increasingly widely available. An -example is Matthew Carter’s Georgia font, which has old-style figures +example is Matthew Carter’s Georgia font, which has old-style figures as its normal form (the font was created for inclusion with certain Microsoft products and is intended for on-screen viewing). -<p/>OpenType fonts have a pair of axes for number variations — +<p/>OpenType fonts have a pair of axes for number variations — proportional/tabular and lining/oldstyle selections are commonly -available. “Full feature access” to OpenType fonts, making such +available. “Full feature access” to OpenType fonts, making such options available to the (La)TeX user, is already supported by <a href="FAQ-xetex.html">XeTeX</a> using, for example, the <i>fontspec</i> package. Similar support is also in the works for diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html index 86dc97512a8..2f8abfebd0d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label otherprinters</title> </head><body> -<h3>Output to “other” printers</h3> +<h3>Output to “other” printers</h3> <p/>In the early years of TeX, there were masses of DVI drivers for any (then) imaginable kind of printer, but the steam seems rather to have gone out of the market for production of drivers for @@ -13,7 +13,7 @@ the DVI output driver writers have all gone?). <p/>The general advice, then, is to <a href="FAQ-dvips.html">generate PostScript</a>, and to process that with <i>ghostscript</i> set to generate the format for the printer you actually have. If you are using a Unix system of -some sort, it’s generally quite easy to insert <i>ghostscript</i> +some sort, it’s generally quite easy to insert <i>ghostscript</i> into the print spooling process. <dl> <dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html index 40d1c2c3510..6db5ee5c795 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ouparmd.html @@ -8,8 +8,8 @@ ! LaTeX Error: Not in outer par mode. </pre> </blockquote><p> -comes when some “main” document feature is shut up somewhere it -doesn’t like. +comes when some “main” document feature is shut up somewhere it +doesn’t like. <p/>The commonest occurrence is when the user wants a figure somewhere inside a table: <blockquote> @@ -24,7 +24,7 @@ inside a table: </pre> </blockquote><p> a construction that was supposed to put a frame around the diagram, -but doesn’t work, any more than: +but doesn’t work, any more than: <blockquote> <pre> \framebox{\begin{figure} @@ -35,7 +35,7 @@ but doesn’t work, any more than: </blockquote><p> The problem is, that the <code>tabular</code> environment, and the <code>\</code><code>framebox</code> command restrain the <code>figure</code> environment -from its natural métier, which is to float around the document. +from its natural métier, which is to float around the document. <p/>The solution is simply not to use the <code>figure</code> environment here: <blockquote> @@ -47,10 +47,10 @@ here: \end{tabular} </pre> </blockquote><p> -What was the float for? — as written in the first two examples, it +What was the float for? — as written in the first two examples, it serves no useful purpose; but perhaps you actually wanted a diagram and its caption framed, in a float. -<p/>It’s simple to achieve this — just reverse the order of the +<p/>It’s simple to achieve this — just reverse the order of the environments (or of the <code>figure</code> environment and the command): <blockquote> @@ -66,7 +66,7 @@ command): </pre> </blockquote><p> The same goes for <code>table</code> environments (or any other sort -of float you’ve defined for yourself) inside tabulars or box commands; +of float you’ve defined for yourself) inside tabulars or box commands; you <em>must</em> get the float environment out from inside, one way or another. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html index 861205a5f0a..963117f2a30 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html @@ -5,36 +5,36 @@ <p/>When TeX is building a paragraph, it can make several attempts to get the line-breaking right; on each attempt it runs the same algorithm, but gives it different parameters. You can affect the way -TeX’s line breaking works by adjusting the parameters: this answer -deals with the “tolerance” and stretchability parameters. The other -vital ‘parameter’ is the set of hyphenations to be applied: see -“<a href="FAQ-nohyph.html">my words aren’t being hyphenated</a>” +TeX’s line breaking works by adjusting the parameters: this answer +deals with the “tolerance” and stretchability parameters. The other +vital ‘parameter’ is the set of hyphenations to be applied: see +“<a href="FAQ-nohyph.html">my words aren’t being hyphenated</a>” (and the questions it references) for advice. -<p/>If you’re getting an undesired “overfull box”, what has happened is -that TeX has given up: the parameters you gave it don’t allow it to -produce a result that <em>doesn’t</em> overfill. In this circumstance, +<p/>If you’re getting an undesired “overfull box”, what has happened is +that TeX has given up: the parameters you gave it don’t allow it to +produce a result that <em>doesn’t</em> overfill. In this circumstance, Knuth decided the best thing to do was to produce a warning, and to allow the user to solve the problem. (The alternative, silently to go -beyond the envelope of “good taste” defined for this run of TeX, +beyond the envelope of “good taste” defined for this run of TeX, would be distasteful to any discerning typographer.) The user can -almost always address the problem by rewriting the text that’s -provoking the problem — but that’s not always possible, and in some -cases it’s impossible to solve the problem without adjusting the +almost always address the problem by rewriting the text that’s +provoking the problem — but that’s not always possible, and in some +cases it’s impossible to solve the problem without adjusting the parameters. This answer discusses the approaches one might take to -resolution of the problem, on the assumption that you’ve got the +resolution of the problem, on the assumption that you’ve got the hyphenation correct. -<p/>The simplest case is where a ‘small’ word fails to break at the end of -a line; pushing the entire word to a new line isn’t going to make much -difference, but it might make things just bad enough that TeX won’t +<p/>The simplest case is where a ‘small’ word fails to break at the end of +a line; pushing the entire word to a new line isn’t going to make much +difference, but it might make things just bad enough that TeX won’t do it by default. In such a case on can <em>try</em> the LaTeX <code>\</code><code>linebreak</code> command: it may solve the problem, and if it does, it will save an awful lot of fiddling. Otherwise, one needs to adjust -parameters: to do that we need to recap the details of TeX’s line +parameters: to do that we need to recap the details of TeX’s line breaking mechanisms. -<p/>TeX’s first attempt at breaking lines is performed without even -trying hyphenation: TeX sets its “tolerance” of line breaking +<p/>TeX’s first attempt at breaking lines is performed without even +trying hyphenation: TeX sets its “tolerance” of line breaking oddities to the internal value <code>\</code><code>pretolerance</code>, and sees what -happens. If it can’t get an acceptable break, TeX adds the +happens. If it can’t get an acceptable break, TeX adds the hyphenation points allowed by the current patterns, and tries again using the internal <code>\</code><code>tolerance</code> value. If this pass also fails, and the internal <code>\</code><code>emergencystretch</code> value is positive, TeX will try @@ -44,46 +44,46 @@ to the spaces in each line. hyphenation) that you can change: <code>\</code><code>pretolerance</code>, <code>\</code><code>tolerance</code> and <code>\</code><code>emergencystretch</code>. Both the <code>tolerance</code> values are simple numbers, and should be set by TeX primitive count -assignment — for example +assignment — for example <blockquote> <pre> \pretolerance=150 </pre> </blockquote><p> -For both, an “infinite” tolerance is represented by the value +For both, an “infinite” tolerance is represented by the value <code>10</code><code>000</code>, but infinite tolerance is rarely appropriate, since it can lead to very bad line breaks indeed. -<p/><code>\</code><code>emergencystretch</code> is a TeX-internal ‘dimen’ register, and can +<p/><code>\</code><code>emergencystretch</code> is a TeX-internal ‘dimen’ register, and can be set as normal for dimens in Plain TeX; in LaTeX, use -<code>\</code><code>setlength</code> — for example: +<code>\</code><code>setlength</code> — for example: <blockquote> <pre> \setlength{\emergencystretch}{3em} </pre> </blockquote><p> -<p/>The choice of method has time implications — each of the +<p/>The choice of method has time implications — each of the passes takes time, so adding a pass (by changing <code>\</code><code>emergencystretch</code>) is less desirable than suppressing one (by -changing <code>\</code><code>pretolerance</code>). However, it’s unusual nowadays to find a -computer that’s slow enough that the extra passes are really +changing <code>\</code><code>pretolerance</code>). However, it’s unusual nowadays to find a +computer that’s slow enough that the extra passes are really troublesome. <p/>In practice, <code>\</code><code>pretolerance</code> is rarely used other than to manipulate the use of hyphenation; Plain TeX and LaTeX both set its value to <code>100</code>. To suppress the first scan of paragraphs, set <code>\</code><code>pretolerance</code> to <code>-1</code>. <p/><code>\</code><code>tolerance</code> is often a good method for adjusting spacing; -Plain TeX and LaTeX both set its value to <code>200</code>. LaTeX’s +Plain TeX and LaTeX both set its value to <code>200</code>. LaTeX’s <code>\</code><code>sloppy</code> command sets it to <code>9999</code>, as does the <code>sloppypar</code> environment. This value is the largest available, this side of infinity, and can allow pretty poor-looking -breaks (this author rarely uses <code>\</code><code>sloppy</code> “bare”, though he does -occasionally use <code>sloppypar</code> — that way, the change of +breaks (this author rarely uses <code>\</code><code>sloppy</code> “bare”, though he does +occasionally use <code>sloppypar</code> — that way, the change of <code>\</code><code>tolerance</code> is confined to the environment). More satisfactory is to make small changes to <code>\</code><code>tolerance</code>, incrementally, and then to look to see how the change affects the result; very small increases can often -do what’s necessary. Remember that <code>\</code><code>tolerance</code> is a paragraph -parameter, so you need to ensure it’s actually applied — see -“<a href="FAQ-paraparam.html">ignoring paragraph parameters</a>”. +do what’s necessary. Remember that <code>\</code><code>tolerance</code> is a paragraph +parameter, so you need to ensure it’s actually applied — see +“<a href="FAQ-paraparam.html">ignoring paragraph parameters</a>”. LaTeX users could use an environment like: <blockquote> <pre> @@ -97,9 +97,9 @@ LaTeX users could use an environment like: enclosing entire paragraphs (or set of paragraphs) in it. <p/>The value of <code>\</code><code>emergencystretch</code> is added to the assumed stretchability of each line of a paragraph, in a further run of the -paragraph formatter in case that the paragraph can’t be made to look +paragraph formatter in case that the paragraph can’t be made to look right any other way. (The extra scan happens if -<code>\</code><code>emergencystretch>0pt</code> — if it’s zero or negative, no gain +<code>\</code><code>emergencystretch>0pt</code> — if it’s zero or negative, no gain could be had from rerunning the paragraph setter.) The example above set it to <code>3em</code>; the Computer Modern fonts ordinarily fit three space skips to the <code>em</code>, so the change would allow anything up @@ -110,21 +110,21 @@ width. It is therefore clear that <code>\</code><code>emergencystretch</code> n treated with a degree of caution. <p/>More subtle (but more tricky to manage) are the microtypographic extensions provided by PDFTeX. Since PDFTeX is the default -‘engine’ for LaTeX and ConTeXt work in all distributions, +‘engine’ for LaTeX and ConTeXt work in all distributions, nowadays, the extensions are available to all. There are two extensions, margin kerning and font expansion; margin kerning only affects the visual effect of the typeset page, and has little effect -on the ability of the paragraph setter to “get things right”. +on the ability of the paragraph setter to “get things right”. Font expansion works like a subtler version of the trick that -<code>\</code><code>emergencystretch</code> plays: PDFTeX ‘knows’ that your current font +<code>\</code><code>emergencystretch</code> plays: PDFTeX ‘knows’ that your current font may be stretched (or shrunk) to a certain extent, and will do that -“on the fly” to optimise the setting of a paragraph. This is a +“on the fly” to optimise the setting of a paragraph. This is a powerful tool in the armoury of the typesetter. <p/>As mentioned above, the microtypographic extensions are tricky beasts to control; however, the <i>microtype</i> package relieves the user of the tedious work of specifying how to perform margin adjustments -and how much to scale each font … for the fonts the package -knows about; it’s a good tool, and users who can take on the +and how much to scale each font … for the fonts the package +knows about; it’s a good tool, and users who can take on the specification of adjustments for yet more fonts are always welcome. <dl> <dt><tt><i>microtype.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html index 4282de7d7aa..6fb52bf9f27 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overstrike.html @@ -11,7 +11,7 @@ by a different mechanism. <p/>Documentation of <i>ulem</i> is in the package file. <dl> <dt><tt><i>soul.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse the directory</a>) -<dt><tt><i>ulem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a> +<dt><tt><i>ulem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ulem.zip">macros/latex/contrib/ulem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ulem/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html index 617b31411a1..bd57c763604 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pagebychap.html @@ -3,7 +3,7 @@ </head><body> <h3>Page numbering by chapter</h3> <p/>When I was a young man, a common arrangement for loose bound technical -manuals is to number pages by chapter. (It’s quite a good scheme, in +manuals is to number pages by chapter. (It’s quite a good scheme, in those situations: even if your corrections add a whole page to the chapter, the most you have to redistribute is that chapter.) <p/>The problem, at first sight, seems pretty much the same as that in @@ -16,7 +16,7 @@ to the correct value at the start of each chapter, and so on, is slightly more challenging. This is why the <i>chappg</i> package was written: it does the obvious things, and more. <p/>Users have been known to ask for running page numbers within a -section, but this really doesn’t make sense: you need to run page +section, but this really doesn’t make sense: you need to run page numbers within document objects that always start on a fresh page. <dl> <dt><tt><i>chappg.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chappg.zip">macros/latex/contrib/chappg</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chappg/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html index 0be1b9af49e..49777da5d45 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html @@ -2,21 +2,21 @@ <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 +<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 +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’ +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 +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. +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. @@ -26,9 +26,9 @@ 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 +doesn’t provide for people using the “wrong” sort of paper for some reason. -<p/>A different issue arises for users of PDFTeX — the +<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. @@ -46,7 +46,7 @@ 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”. +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 @@ -58,23 +58,23 @@ ignored if you are using either PDFLaTeX or VTeX.) </pre> </blockquote><p> (where <code>dvixxx</code> is your current favourite DVI -driver — <i>geometry</i> knows about <code>dvips</code> and +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 +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 +<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”. +“right”. <p/>The <i>typearea</i> package is the <i>Koma-script</i> -distribution’s way of providing page layout functionality. Load it +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 +<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 @@ -84,7 +84,7 @@ output that specifies the necessary paper size. <dl> <dt><tt><i>geometry.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) -<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) +<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/typearea.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papergeom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papergeom</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html index b6c38f9fcbb..f42e7e68480 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papersize.html @@ -3,21 +3,21 @@ </head><body> <h3>The size of printed output</h3> <p/>The final product of a (La)TeX run is something for a person to -read. Often, nowadays, that product will be read “on-screen”, but +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. +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 +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/>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 + 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>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html index 15271cf5c09..10478c01711 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parallel.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label parallel</title> </head><body> <h3>Parallel setting of text</h3> -<p/>It’s commonly necessary to present text in two languages ‘together’ on a +<p/>It’s commonly necessary to present text in two languages ‘together’ on a page, or on a two-page spread. For this to be satisfactory, one usually needs some sort of alignment between the two texts. <p/>The <i>parallel</i> package satisfies the need, permitting @@ -13,7 +13,7 @@ as simple as <pre> \usepackage{parallel} ... -\begin{Parallel}{<left-width>}{<right-width} +\begin{Parallel}{<left-width>}{<right-width} \ParallelLText{left-text} \ParallelRText{right-text} \ParallelPar @@ -23,37 +23,40 @@ as simple as </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. +issue — the <i>pdfcolparallel</i> package, which maintains +separate colour stacks for the columns. <p/>The <i>parcolumns</i> package can (in principle) deal with any number of columns: the documentation shows its use with three columns. Usage is rather similar to that of <i>parallel</i>, -though there is of course a “number of columns to specify”: +though there is of course a “number of columns to specify”: <blockquote> <pre> \usepackage{parcolumns} ... -\begin{parcolumns}[<options>]{3} - \colchunk{<Column 1 text>} - \colchunk{<Column 2 text>} - \colchunk{<Column 3 text>} +\begin{parcolumns}[<options>]{3} + \colchunk{<Column 1 text>} + \colchunk{<Column 2 text>} + \colchunk{<Column 3 text>} \colplacechunks ... \end{parcolumns} </pre> </blockquote><p> The <<i>options</i>> can specify the widths of the columns, whether to -place rules between the columns, whether to set the columns sloppy, etc. +place rules between the columns, whether to set the columns sloppy, +etc. Again, there are issues with colours, which are addressed by the +<i>pdfcolparcolumns</i> package. <p/>The <i>ledpar</i> package is distributed with (and integrated with) the <a href="FAQ-linenos.html"><i>ledmac</i> package</a>. It provides parallel setting carefully integrated with the needs of a scholarly text, permitting translation, or notes, or both, to be set in parallel with -the ‘base’ text of the document. +the ‘base’ text of the document. <dl> <dt><tt><i>ledpar.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse the directory</a>) <dt><tt><i>parallel.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/parallel.zip">macros/latex/contrib/parallel</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/parallel/">browse the directory</a>) -<dt><tt><i>parcolumns.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse the directory</a>) -<dt><tt><i>pdfcolparallel.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>parcolumns.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/parcolumns.html">catalogue entry</a> +<dt><tt><i>pdfcolparallel.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/pdfcolparallel.html">catalogue entry</a> +<dt><tt><i>pdfcolparcolumns.sty</i></tt><dd>pdfcolparcolumns] </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html index 60ded834d24..f77c7ef4b65 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-paraparam.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label paraparam</title> </head><body> <h3>Why does it ignore paragraph parameters?</h3> -<p/>When TeX is laying out text, it doesn’t work from word to word, or +<p/>When TeX is laying out text, it doesn’t work from word to word, or from line to line; the smallest complete unit it formats is the paragraph. The paragraph is laid down in a buffer, as it appears, and -isn’t touched further until the end-paragraph marker is processed. -It’s at this point that the paragraph parameters have effect; and it’s +isn’t touched further until the end-paragraph marker is processed. +It’s at this point that the paragraph parameters have effect; and it’s because of this sequence that one often makes mistakes that lead to the paragraph parameters not doing what one would have hoped (or expected). @@ -38,7 +38,7 @@ end the group.\par} Here's more that needn't be ragged... </pre> </blockquote><p> -In this way, the paragraph is completed while <code>\</code><code>raggedright</code>’s +In this way, the paragraph is completed while <code>\</code><code>raggedright</code>’s parameters are still in force within the enclosing group. <p/>Another alternative is to define an environment that does the appropriate job for you. For the above example, LaTeX already diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html index 5cfe623ba01..6debafd1065 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html @@ -7,10 +7,10 @@ between paragraphs, and the first line of each paragraph in a block of text indented. <p/>In contrast, one common convention for typewritten text was to have no indentation of paragraphs; such a style is often required for -“brutalist” publications such as technical manuals, and in styles +“brutalist” publications such as technical manuals, and in styles that hanker after typewritten manuscripts, such as officially-specified dissertation formats. -<p/>Anyone can see, after no more than a moment’s thought, that if the +<p/>Anyone can see, after no more than a moment’s thought, that if the paragraph indent is zero, the paragraphs must be separated by blank space: otherwise it is sometimes going to be impossible to see the breaks between paragraphs. @@ -19,12 +19,12 @@ breaks between paragraphs. \setlength{\parindent}{0pt} \setlength{\parskip}{\baselineskip} </pre> -and in the very simplest text, it’s a fine solution. +and in the very simplest text, it’s a fine solution. <p/>However, the non-zero <code>\</code><code>parskip</code> interferes with lists and the like, and the result looks pretty awful. The <i>parskip</i> package -patches things up to look reasonable; it’s not perfect, but it deals +patches things up to look reasonable; it’s not perfect, but it deals with most problems. -<p/>The Netherlands Users’ Group’s set of classes includes an +<p/>The Netherlands Users’ Group’s set of classes includes an <i>article</i> equivalent (<i>artikel3</i>) and a <i>report</i> equivalent (<i>rapport3</i>) whose design incorporates zero paragraph indent and non-zero paragraph skip. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html index 9b98b33c632..233b15aab10 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-patch.html @@ -15,9 +15,9 @@ would naturally write: </blockquote><p> However, this would not work: a call to <code>\</code><code>splat</code> would execute <code>\</code><code>mumble</code>, and the call the redefined <code>\</code><code>splat</code> again; this is an -unterminated recursion, that will quickly exhaust TeX’s memory. +unterminated recursion, that will quickly exhaust TeX’s memory. <p/>Fortunately, the TeX primitive <code>\</code><code>let</code> command comes to our -rescue; it allows us to take a “snapshot” of the current state of a +rescue; it allows us to take a “snapshot” of the current state of a command, which we can then use in the redefinition of the command. So: <blockquote> @@ -38,20 +38,20 @@ pass them on: </blockquote><p> <p/>The general case may be achieved in two ways. First, one can use the LaTeX command <code>\</code><code>CheckCommand</code>; this compares an existing command -with the definition you give it, and issues a warning if two don’t +with the definition you give it, and issues a warning if two don’t match. Use is therefore: <blockquote> <code>\CheckCommand{\complex}{</code><<i>original definition</i>><code>}</code><br> <code>\renewcommand{\complex}{</code><<i>new definition</i>><code>}</code> </blockquote><p> This technique is obviously somewhat laborious, but if the original -command comes from a source that’s liable to change under the control +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>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 +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 @@ -64,8 +64,8 @@ after \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 +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 (in the form <code>\</code><code>Substitute*</code>) using the result to (re)define a @@ -79,7 +79,7 @@ its definition: {\Large\sffamily}{\huge\itshape} </pre> </blockquote><p> -The macro’s definition is now: +The macro’s definition is now: <blockquote> <pre> \huge\itshape\selectfont @@ -87,8 +87,8 @@ The macro’s definition is now: </blockquote><p> <p/>The package also offers a command <code>\</code><code>ShowTokens</code>, which shows the content of its argument, one token to a line, with details of the -token’s category code, etc. This is recommended as a debugging tool. -<p/>The <i>etoolbox</i> (which provides user access to e-TeX’s +token’s category code, etc. This is recommended as a 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 is very similar to <code>\</code><code>Substitute</code>, except that it only replaces a single instance of the token(s) in its search pattern. Since not all @@ -98,19 +98,19 @@ package also provides commands that prepend (<code>\</code><code>pretocmd</code> (<code>\</code><code>apptocmd</code>) to the definition of a command. Not all commands may be patched in this way; the package provides a command <code>\</code><code>ifpatchable</code> which checks the prerequisites, and checks that the -target command’s body does indeed include the patch string you propose +target command’s body does indeed include the patch string you propose to use. (The command <code>\</code><code>ifpatchable*</code> omits the test on the patch string.) -<p/>Finally, we’ll briefly consider a package that is (just about) +<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 to <a href="FAQ-install-doc.html">produce formatted documentation, etc.</a>. Fortunately, the file (<i>patch.doc</i>) may be input directly, and -“documentation” may found by reading the source of the package. +“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, +command thus amended. Unless you can’t do your job any other way, <i>patch</i> is best avoided. <dl> <dt><tt><i>etoolbox.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/etoolbox.zip">macros/latex/contrib/etoolbox</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/etoolbox/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdf-fig-chars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdf-fig-chars.html index 7b40fc9807d..01c34577a68 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdf-fig-chars.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdf-fig-chars.html @@ -4,7 +4,7 @@ <h3>Characters disappear from figures in PDFTeX</h3> <p/>You have a PDF figure, which you want to use in your PDFLaTeX document. When you compile the document, PDFTeX -complains about “missing glyphs”, and some (or all) of the labelling +complains about “missing glyphs”, and some (or all) of the labelling text or symbols in the original figure is no longer visible. <p/>What has happened is: <ol> @@ -13,9 +13,9 @@ text or symbols in the original figure is no longer visible. <li> PDFTeX notes that it has <i>font.pfb</i> on disc, and loads that in place of the copy in <i>fig.pdf</i>. <li> It turns out that the copy in <i>fig.pdf</i> has glyphs that - aren’t in <i>font.pfb</i> on disc, so that you get errors while + aren’t in <i>font.pfb</i> on disc, so that you get errors while compiling and you see that characters are missing when you view the - output. (PDFTeX can’t know that the fonts are different, since + output. (PDFTeX can’t know that the fonts are different, since they have the same name.) </ol> Which is all very undesirable. @@ -26,16 +26,16 @@ there will be <em>two</em> copies of <i>font.pfb</i> in the output. (If your document also uses the font, there could be three copies.) <p/>A real case is the URW font <i>NimbusRomNo9L-Regu</i> (a clone of Times Roman), which is available in a version with Cyrillic -letters, while the version in TeX distributions doesn’t have those +letters, while the version in TeX distributions doesn’t have those letters. Both versions, as distributed, have the same name. -<p/>The simple (“quick and dirty”) solution is to add the command +<p/>The simple (“quick and dirty”) solution is to add the command <blockquote> <code>\</code><code>pdfinclusioncopyfonts</code><code>=1</code> </blockquote><p> to the preamble of your document. -<p/>The “real” solution is that one or other font should be renamed. In -either case, this would require that you reconfigure some program’s -(TeX’s or your drawing package’s) font tables — inevitably a +<p/>The “real” solution is that one or other font should be renamed. In +either case, this would require that you reconfigure some program’s +(TeX’s or your drawing package’s) font tables — inevitably a tiresome job. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdf-fig-chars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdf-fig-chars</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html index de28ce75cc0..d71c38b39fb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html @@ -7,30 +7,30 @@ changes the display of page numbers in the frontmatter of the document to lower-case roman. This is fine for human readers, but if <i>hyperref</i> has been misconfigured, the existence of pages have the same page number can cause problems. Fortunately, the -configuration options to make <i>hyperref</i> “do the right -thing” are (by default) set up to avoid problems. +configuration options to make <i>hyperref</i> “do the right +thing” are (by default) set up to avoid problems. <p/>The two options in question are: <dl> <dt><code>plainpages=false</code><dd> Make page anchors using the formatted form of the page number. With this option, - <i>hyperref</i> writes different anchors for pages ‘ii’ and ‘2’. + <i>hyperref</i> writes different anchors for pages ‘ii’ and ‘2’. (This is the default value for the option, which is a <em>good thing</em>\dots) - If the option is set ‘<code>true</code>’ <i>hyperref</i> writes page + If the option is set ‘<code>true</code>’ <i>hyperref</i> writes page anchors as the arabic form of the page number, rather than the formatted form that gets printed; this is not usually appropriate. <dt><code>pdfpagelabels</code><dd> Set PDF page labels; i.e., write the value of <code>\</code><code>thepage</code> to the PDF file so that - <i>Acrobat Reader</i> can display the page number as (say) ‘ii (4 - of 40)’ rather than simply ‘4 of 40’. + <i>Acrobat Reader</i> can display the page number as (say) ‘ii (4 + of 40)’ rather than simply ‘4 of 40’. </dl> The two should be used whenever page numbering is not just -‘1<code>..</code>n’; they may be used independently, but +‘1<code>..</code>n’; they may be used independently, but usually are not. -<p/>The recipe isn’t perfect: it relies on <code>\</code><code>thepage</code> being different +<p/>The recipe isn’t perfect: it relies on <code>\</code><code>thepage</code> being different for every page in the document. A common problem arises when there is an unnumbered title page, after which page numbers are reset: the -PDFTeX warning of “<a href="FAQ-hyperdupdest.html">duplicate destinations</a>” +PDFTeX warning of “<a href="FAQ-hyperdupdest.html">duplicate destinations</a>” will happen in this case, regardless of the options. <dl> <dt><tt><i>hyperref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html index 2b6f3fee48b..597209286fe 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html @@ -3,34 +3,34 @@ </head><body> <h3>Imported graphics in PDFLaTeX</h3> <p/>PDFTeX itself has a rather wide range of formats that it can -“natively” incorporate into its output PDF stream: +“natively” incorporate into its output PDF stream: JPEG (<code>.jpg</code> files) for photographs and similar images, PNG files for artificial bitmap images, and PDF for vector drawings. Old versions of PDFTeX (prior to version 1.10a) supported TIFF (<code>.tif</code> files) format as an alternative -to PNG files; don’t rely on this facility, even if you -<em>are</em> running an old enough version of PDFTeX… -<p/>In addition to the ‘native’ formats, the standard PDFLaTeX -<i>graphics</i> package setup causes Hans Hagen’s <i>supp-pdf</i> +to PNG files; don’t rely on this facility, even if you +<em>are</em> running an old enough version of PDFTeX… +<p/>In addition to the ‘native’ formats, the standard PDFLaTeX +<i>graphics</i> package setup causes Hans Hagen’s <i>supp-pdf</i> macros to be loaded: these macros are capable of translating the -output of MetaPost to PDF “on the fly”; thus MetaPost output +output of MetaPost to PDF “on the fly”; thus MetaPost output (<code>.mps</code> files) may also be included in PDFLaTeX documents. <p/>The commonest problem users encounter, when switching from TeX, is that there is no straightforward way to include EPS files: -since PDFTeX is its own “driver”, and since it contains no means -of converting PostScript to PDF, there’s no direct way the job can +since PDFTeX is its own “driver”, and since it contains no means +of converting PostScript to PDF, there’s no direct way the job can be done. <p/>The simple solution is to convert the EPS to an appropriate -PDF file. The <i>epstopdf</i> program will do this: it’s +PDF file. The <i>epstopdf</i> program will do this: it’s available either as a Windows executable or as a <i>Perl</i> script to run on Unix and other similar systems. A LaTeX package, <i>epstopdf</i>, can be used to generate the requisite PDF -files “on the fly”; this is convenient, but requires that you -suppress one of TeX’s security checks: don’t allow its use in files -from sources you don’t entirely trust. -<p/>A similar package, <i>pst-pdf</i>, permits other things than ‘mere’ +files “on the fly”; this is convenient, but requires that you +suppress one of TeX’s security checks: don’t allow its use in files +from sources you don’t entirely trust. +<p/>A similar package, <i>pst-pdf</i>, permits other things than ‘mere’ graphics files in its argument. <i>Pst-pdf</i> operates (the -authors suggest) “like BibTeX” — you process your file using +authors suggest) “like BibTeX” — you process your file using PDFLaTeX, then use LaTeX, <i>dvips</i> and <i>ps2pdf</i> in succession, to produce a secondary file to input to your next PDFLaTeX run. (Scripts are provided to ease the production of the @@ -38,17 +38,17 @@ secondary file.) <p/>An alternative solution is to use <i>purifyeps</i>, a <i>Perl</i> script which uses the good offices of <i>pstoedit</i> and of MetaPost to convert your Encapsulated PostScript to -“Encapsulated PostScript that comes out of MetaPost”, and can therefore be -included directly. Sadly, <i>purifyeps</i> doesn’t work for all +“Encapsulated PostScript that comes out of MetaPost”, and can therefore be +included directly. Sadly, <i>purifyeps</i> doesn’t work for all <code>.eps</code> files. -<p/>Good coverage of the problem is to be found in Herbert Voss’ +<p/>Good coverage of the problem is to be found in Herbert Voss’ <a href="http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput">PDF support page</a>, which is targeted at the use of <i>pstricks</i> in PDFLaTeX, and also covers the <i>pstricks</i>-specific package <i>pdftricks</i>. <dl> <dt><tt><i>epstopdf</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/epstopdf/">support/epstopdf/</a> -<dt><tt><i>epstopdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages +<dt><tt><i>epstopdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) <dt><tt><i>pdftricks.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse the directory</a>) <dt><tt><i>pst-pdf.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf.zip">macros/latex/contrib/pst-pdf</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html index 37458de9ed1..7bef7091747 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkfix.html @@ -10,7 +10,7 @@ but if neither the sources nor the DVI file are available, one must needs resort to some sort of patching to replace the bitmap fonts in the file by outline fonts. <p/>The program <i>pkfix</i> (by Heiko Oberdiek) will do this -patching, for files created by “not too old versions” of +patching, for files created by “not too old versions” of <i>dvips</i>: it finds the fonts to be replaced by examining the PostScript comments <i>dvips</i> has put in the file. For each font, <i>pkfix</i> puts appropriate TeX commands in a file, @@ -18,14 +18,14 @@ which it then processes and runs through <i>dvips</i> (with switch <code>-Ppdf</code>) to acquire an appropriate copy of the font; these copies are then patched back into the original file. <p/>If your source file is older than <i>pkfix</i> can deal with, -there’s still a modicum of hope: <i>pkfix-helper</i> examines the +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 +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) +<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. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html index 3ef56eb782f..7912235fa05 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pkgdoc.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label pkgdoc</title> </head><body> <h3>Documentation of packages</h3> -<p/>These FAQs regularly suggest packages that will “solve” +<p/>These FAQs regularly suggest packages that will “solve” particular problems. In some cases, the answer provides a recipe for the job. In other cases, or when the solution needs elaborating, how is the poor user to find out what to do? -<p/>If you’re lucky, the package you need is already in your installation. -If you’re particularly lucky, you’re using a distribution that gives +<p/>If you’re lucky, the package you need is already in your installation. +If you’re particularly lucky, you’re using a distribution that gives access to package documentation and the documentation is available in a form that can easily be shown. For example, on many current distributions, the <i>texdoc</i> command often helps, as in: @@ -20,14 +20,14 @@ which opens a window showing documentation of the <i>footmisc</i> package. According to the type of file <i>texdoc</i> finds, it will launch a DVI viewer or a PDF reader. -<p/>If <i>texdoc</i> can’t find any documentation, it may launch a Web +<p/>If <i>texdoc</i> can’t find any documentation, it may launch a Web browser to look at its copy of the CTAN catalogue. The catalogue has an entry for package documentation, and since the CTAN team asks authors documentation of their packages (and members of the team even occasionally generate documentation that seems useful), you will more often than not find documentation that way. -<p/>If your luck (as defined above) doesn’t hold out, you’ve got to find +<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 follows offers a range of possible techniques. @@ -44,7 +44,7 @@ latter case, the <code>.ins</code> file will usually produce a LaTeX instead. (Sometimes the package author even thinks to mention this wrinkle in a package <code>README</code> file.) <p/>Another common form is the separate documentation file; particularly -if a package is “conceptually large” (and therefore needs a lot of +if a package is “conceptually large” (and therefore needs a lot of documentation), the documentation would prove a cumbersome extension to the <code>.dtx</code> file. Examples of such cases are the <i>memoir</i> class (whose documentation, <i>memman</i>, is widely praised as an @@ -59,15 +59,15 @@ existence. Such documentation ordinarily appears in comments at the head of the file, though at least one eminent author regularly places it after the <code>\</code><code>endinput</code> command in the package. (This is desirable, since -<code>\</code><code>endinput</code> is a ‘logical’ end-of-file, and (La)TeX doesn’t read -beyond it: thus such documentation does not ‘cost’ any package loading time.) +<code>\</code><code>endinput</code> is a ‘logical’ end-of-file, and (La)TeX doesn’t read +beyond it: thus such documentation does not ‘cost’ any package loading time.) <p/>The above suggestions cover most possible ways of finding -documentation. If, despite your best efforts, you can’t find -it in any of the above places, there’s the awful possibility that the -author didn’t bother to document his package (on the “if it was hard -to write, it should be hard to use” philosophy). Most ordinary +documentation. If, despite your best efforts, you can’t find +it in any of the above places, there’s the awful possibility that the +author didn’t bother to document his package (on the “if it was hard +to write, it should be hard to use” philosophy). Most ordinary mortals will seek support from some more experienced user at this stage, though it <em>is</em> possible to proceed in the way that the original -author apparently expected…by reading his code. +author apparently expected…by reading his code. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plaintex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plaintex.html new file mode 100644 index 00000000000..0020238c01c --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plaintex.html @@ -0,0 +1,19 @@ +<head> +<title>UK TeX FAQ -- question label plaintex</title> +</head><body> +<h3>What’s “writing in TeX”?</h3> +<p/>TeX is a macro processor, and offers its users a powerful +programming capability. To produce a document, you write macros and +text interleaved with each other. The macros define an environment in +which the text is to be typeset. +<p/>However, the basic TeX engine is pretty +basic, and is a pretty difficult beast to deal with. Recognising this +(and not wanting to write the same things at the start of every +document, himself) Knuth provided a package of macros for use with +TeX, called Plain TeX; Plain TeX is a useful minimum set of +macros that can be used with TeX, together with some demonstration +versions of higher-level commands. When people say they’re “writing +(or programming) in TeX”, they usually mean they’re programming in +Plain TeX. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plaintex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plaintex</a> +</body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html index 434e2c018a4..7d7858e1403 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label plainvltx</title> </head><body> <h3>Should I use Plain TeX or LaTeX?</h3> -<p/>There’s no straightforward answer to this question. Many people swear +<p/>There’s no straightforward answer to this question. Many people swear by Plain TeX, and produce highly respectable documents using it (Knuth is an example of this, of course). But equally, many people are happy to let someone else take the design decisions for them, @@ -12,7 +12,7 @@ accepting a small loss of flexibility in exchange for a saving of heat, without offering much by way of light; your best bet may be to find out what those around you are using, and to follow them in the hope of some support. Later on, you can always switch your -allegiance; don’t bother about it. +allegiance; don’t bother about it. <p/>If you are preparing a manuscript for a publisher or journal, ask them what markup they want before you develop your own; many big publishers have developed their own diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html index d99a905e43c..d55e1c83d2e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plninltxstar.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label plninltx*</title> </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 +<p/>It’s well-known that LaTeX commands tend to be more complex, and to run more slowly than, any Plain TeX (or primitive) command that they replace. There is therefore great temptation not to use LaTeX commands when macro programming. Nevertheless, the general rule is @@ -15,31 +15,31 @@ would cause trouble in your application. Similarly, use <code>\</code><code>newcommand</code> (or one of its relatives) unless you need one of the constructs that cannot be achieved without the use of <code>\</code><code>def</code> (or friends). <p/>As a general rule, any LaTeX text command will start a new -paragraph if necessary; this isn’t the case with Plain TeX +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 -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 +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 LaTeX: an equivalent appears as the internal command <code>\</code><code>@@line</code>). <p/>Maths setting shows a case where the LaTeX version <em>is</em> essentially equivalent to the TeX primitive commands: the LaTeX <code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code> does essentially no different to the TeX <code>$ ... $</code> -(except for checking that you’re not attempting to open a maths -environment when you’re already in one, or vice versa). -However, <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> <em>isn’t</em> the same as +(except for checking that you’re not attempting to open a maths +environment when you’re already in one, or vice versa). +However, <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> <em>isn’t</em> the same as <code>$$ ... $$</code>: the TeX version, used in LaTeX, can miss the effect of the class option <code>fleqn</code>. <p/>Font handling is, of course, wildly different in Plain TeX and -LaTeX. Plain TeX’s font loading command +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 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>”. +may be found in “<a href="FAQ-newfontstar.html">What’s wrong with <code>\</code><code>newfont</code>?</a>”. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html index 35851078514..7fd407f42d9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-poster.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label poster</title> </head><body> <h3>Creating posters with LaTeX</h3> -<p/>There is no complete “canned solution” to creating a poster (as, for +<p/>There is no complete “canned solution” to creating a poster (as, for example, classes like <i>seminar</i>, <i>powerdot</i> and <i>beamer</i> serve for creating presentations in a variety of styles). <p/>The nearest approach to the complete solution is the <i>sciposter</i> class, which provides the means to produce really rather good posters -according to the author’s required style. A complete worked example +according to the author’s required style. A complete worked example is provided with the distribution <p/>Otherwise, there is a range of tools, most of which are based on the <i>a0poster</i> class, which sets up an appropriately-sized piece of @@ -16,13 +16,13 @@ paper, sets font sizes appropriately, and leaves you to your own devices. <p/>Having used <i>a0poster</i>, you can of course slog it out, and write all your poster as an unadorned LaTeX document (presumably in -multiple columns, using the <i>multicol</i> package), but it’s not really +multiple columns, using the <i>multicol</i> package), but it’s not really necessary: the (straightforward) <i>textpos</i> package provides a simple way of positioning chunks of text, or tables or figures, on the poster page. <p/>More sophisticated is the <i>flowfram</i> package, whose basic aim in life is flowing text from one box on the page to the next. One of -the package’s design aims seems to have been the production of +the package’s design aims seems to have been the production of posters, and a worked example is provided. The author of <i>flowfram</i> has an experimental tool called <a href="http://theoval.cmp.uea.ac.uk/~nlct/jpgfdraw/">JpgfDraw</a>, which @@ -36,7 +36,7 @@ route): <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>” +<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 @@ -45,7 +45,7 @@ route): <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>” +<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 (offering supporting material as necessary), @@ -54,7 +54,7 @@ route): <dl> <dt><tt><i>a0poster.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/a0poster.zip">macros/latex/contrib/a0poster</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/a0poster/">browse the directory</a>) <dt><tt><i>flowfram.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/flowfram.zip">macros/latex/contrib/flowfram</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/flowfram/">browse the directory</a>) -<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/multicol.html">catalogue entry</a> <dt><tt><i>sciposter.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sciposter.zip">macros/latex/contrib/sciposter</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sciposter/">browse the directory</a>) <dt><tt><i>textpos.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html index 7b38729cc53..c9d0d1aabcb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prept1font.html @@ -9,20 +9,20 @@ preparing the font for installation, and second <p/>Many fonts are supplied in (La)TeX ready form: such fonts need no preparation, and may be installed immediately. <p/>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 +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 + 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 + 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 +<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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html index 91239c026d7..a4e01294194 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-previewers.html @@ -4,19 +4,19 @@ <h3>DVI previewers</h3> <p/>EmTeX for PCs running MSDOS or OS/2, MiKTeX and XEmTeX for PCs running Windows and OzTeX for the Macintosh, all -come with previewers that can be used on those platforms. EmTeX’s +come with previewers that can be used on those platforms. EmTeX’s previewer can also be run under Windows 3.1. <p/>Commercial PC TeX packages (see <a href="FAQ-commercial.html">commercial vendors</a>) have good previewers for PCs running Windows, or for Macintoshes. -<p/>For Unix systems, there is one ‘canonical’ viewer, <i>xdvi</i>. +<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 include a version of <i>xdvik</i>. <p/>Alternatives to previewing include <ul> -<li> conversion to ‘similar’ ASCII text (see +<li> conversion to ‘similar’ ASCII text (see <a href="FAQ-toascii.html">converting to ASCII</a>) and using a conventional text viewer to look at that, <li> generating a PostScript version of your document and viewing it diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html index b3cd65cb41c..8cb340415d4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-prinvalint.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label prinvalint</title> </head><body> <h3>The Principal Value Integral symbol</h3> -<p/>This symbol (an integral sign, ‘crossed’) does not appear in any of +<p/>This symbol (an integral sign, ‘crossed’) does not appear in any of the fonts ordinarily available to (La)TeX users, but it can be created by use of the following macros: <pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html index 5869183f7dc..bc3e74ca2e9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-privinst.html @@ -1,19 +1,19 @@ <head> <title>UK TeX FAQ -- question label privinst</title> </head><body> -<h3>“Private” installations of files</h3> +<h3>“Private” installations of files</h3> <p/>It sometimes happens that you need a new version of some macro package -or font, but that the machine you use is maintained by someone who’s -unwilling to update and won’t give you privileges to do the job -yourself. A <a href="FAQ-tempinst.html">“temporary” installation</a> is -sometimes the correct approach, but if there’s the slightest chance +or font, but that the machine you use is maintained by someone who’s +unwilling to update and won’t give you privileges to do the job +yourself. A <a href="FAQ-tempinst.html">“temporary” installation</a> is +sometimes the correct approach, but if there’s the slightest chance that the installation will be needed on more than one project, -temporary installations aren’t right. +temporary installations aren’t right. <p/>In circumstances where you have plenty of quota on backed-up media, or adequate local scratch space, the correct approach is to create a private installation of (La)TeX which includes the new stuff you need; this is the ideal, but is not generally possible. -<p/>So, since you can’t install into the public <code>texmf</code> tree, you +<p/>So, since you can’t install into the public <code>texmf</code> tree, you have to install into a <i>texmf</i> tree of your own; fortunately, the TDS standard allows for this, and modern distributions allow you to do it. The most modern distributions refer to the tree as @@ -36,16 +36,16 @@ tree texhash $HOME/texmf </pre> </blockquote><p> -(the argument specifies which tree you are indexing: it’s necessary -since you don’t, by hypothesis, have access to the main tree, and +(the argument specifies which tree you are indexing: it’s necessary +since you don’t, by hypothesis, have access to the main tree, and <i>texhash</i> without the argument would try to write the main tree. <p/>There are two wrinkles to this simple formula: first, the installation -you’re using may <em>not</em> define a home TEXMF directory, and second, +you’re using may <em>not</em> define a home TEXMF directory, and second, there may be some obstruction to using <i>$HOME/texmf</i> as the default name. In either case, a good solution is to have your own -<i>texmf.cnf</i> — an idea that sounds more frightening that it -actually is. The installation’s existing file may be located with the +<i>texmf.cnf</i> — an idea that sounds more frightening that it +actually is. The installation’s existing file may be located with the command: <blockquote> <pre> @@ -78,9 +78,9 @@ TEXMF = !!$TEXMFMAIN </pre> </blockquote><p> but, there are likely to be several alternative settings behind -comment markers (“<code>%</code>”), and the person who +comment markers (“<code>%</code>”), and the person who installed your system may have left them there. Whatever, you need to -modify the line that’s in effect: change the above to three lines: +modify the line that’s in effect: change the above to three lines: <blockquote> <pre> HOMETEXMF = $HOME/texmf @@ -110,7 +110,7 @@ case you need to make another change, later). The <code>!!</code> signs tell the file-searching library that it should insist on a <i>texhash</i>-ed directory tree; if you can count on yourself remembering to run <i>texhash</i> on your new tree every time you -change it, then it’s worth adding the marks to your tree: +change it, then it’s worth adding the marks to your tree: <blockquote> <pre> @@ -118,8 +118,8 @@ TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN} </pre> </blockquote><p> as this will make (La)TeX find its files marginally faster. -<p/>Having made all these changes, (La)TeX should “just use” files in -your new tree, in preference to anything in the main tree — you can +<p/>Having made all these changes, (La)TeX should “just use” files in +your new tree, in preference to anything in the main tree — you can use it for updates to packages in the main tree, as well as for installing new versions of things. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html index a07f56f37f2..6ada1f31a0b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-proof.html @@ -3,7 +3,7 @@ </head><body> <h3>Proof environment</h3> <p/>It has long been thought impossible to make a <code>proof</code> -environment which automatically includes an ‘end-of-proof’ symbol. +environment which automatically includes an ‘end-of-proof’ symbol. Some proofs end in displayed maths; others do not. If the input file contains @@ -29,10 +29,10 @@ equation: </pre> </blockquote><p> The <code>\</code><code>tag*{<code>\</code><code>qedhere</code>}</code> construction may be used in any of -AMSLaTeX’s numbering environments. +AMSLaTeX’s numbering environments. <dl> <dt><tt><i>amsthm.sty</i></tt><dd>Distributed as part of the AMSLaTeX bundle - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsthm.html">catalogue entry</a> <dt><tt><i>ntheorem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse the directory</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html index fe8c8307f86..13c8d9ed087 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-protect.html @@ -1,30 +1,30 @@ <head> <title>UK TeX FAQ -- question label protect</title> </head><body> -<h3>What’s the reason for ‘protection’?</h3> +<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.) Candidates +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 +prominent examples; there’s a complete list in Lamport’s book (see <a href="FAQ-books.html">TeX-related books</a>). -<p/>What’s going on really, behind the scenes? The commands in moving +<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 code, which shows either during expansion or when the code is processed again. Protecting a command, using -“<code>\</code><code>protect</code><code>\</code><code>cmd</code>” tells LaTeX to save <code>\</code><code>cmd</code> as +“<code>\</code><code>protect</code><code>\</code><code>cmd</code>” tells LaTeX to save <code>\</code><code>cmd</code> as <code>\</code><code>cmd</code>, without expanding it at all. -<p/>So, what is a ‘fragile command’? — it’s a command that expands into +<p/>So, what is a ‘fragile command’? — it’s a command that expands into illegal TeX code during the save process. -<p/>What is a ‘robust command’? — it’s a command that expands into legal +<p/>What is a ‘robust command’? — it’s a command that expands into legal 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. The list isn’t reliable, and neither +<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. 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: @@ -33,7 +33,7 @@ necessarily so: in later revisions of LaTeX. <li> Some commands, such as <code>\</code><code>end</code> and <code>\</code><code>nocite</code>, are fragile even though they have no optional arguments. -<li> The “user’s way” of creating a command with an optional +<li> The “user’s way” of creating a command with an optional argument (using <code>\</code><code>newcommand</code> or <code>\</code><code>newcommand*</code>) now always creates a robust command (though macros without optional arguments may still be fragile if they do things that are themselves fragile). @@ -42,7 +42,7 @@ necessarily so: <li> Some robust commands are redefined by certain packages to be fragile (the <code>\</code><code>cite</code> command commonly suffers this treatment). </ul> -Further, simply “hiding” a fragile command in another command, has +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> @@ -63,7 +63,7 @@ trick above as: 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: +package, the “wrapping” above can simply be replaced by: <blockquote> <pre> \MakeRobustCommand\fred @@ -78,8 +78,8 @@ 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="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>makerobust.sty</i></tt><dd>Distributed as part of Heiko Oberdiek’s bundle + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/makerobust.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html index 63720769ad6..c8c43dfe065 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html @@ -17,17 +17,17 @@ by For mathematics, then, there are relatively few choices (though the list is at last growing). There are several font families available that are -based on Knuth’s original designs, and some that complement other -commercial text font designs; one set (MicroPress’s ‘informal math’) -stands alone. “Free” font families that will support TeX +based on Knuth’s original designs, and some that complement other +commercial text font designs; one set (MicroPress’s ‘informal math’) +stands alone. “Free” font families that will support TeX mathematics include: <dl> -<dt>Computer Modern<dd>(75 fonts — optical scaling) Donald E. Knuth<br> +<dt>Computer Modern<dd>(75 fonts — optical scaling) Donald E. Knuth<br> The CM fonts were originally designed in Metafont, but are also now available in scalable outline form. There are commercial as well as public domain versions, and there are both Adobe Type 1 and TrueType versions. A set of outline versions of the fonts was - developed as a commercial venture by Y&Y and Blue Sky Research; + developed as a commercial venture by Y&Y and Blue Sky Research; they have since assigned the copyright to the AMS, and the fonts are now freely available from CTAN. Their quality is such that they have become the <em>de facto</em> standard for Type 1 @@ -48,7 +48,7 @@ mathematics include: typesetting maths in combination with the Palatino family of text fonts. Four of the five fonts of the distribution are maths alphabets, in upright and italic shapes, medium and bold weights; - the fifth font contains a small selection of “blackboard bold” + the fifth font contains a small selection of “blackboard bold” characters (chosen for their mathematical significance). Support under LaTeX2e is available in <a href="FAQ-usepsfont.html">PSNFSS</a>; the fonts are @@ -62,7 +62,7 @@ mathematics include: expected to use some from the AMS fonts themselves). There are also several other mathematical and decorative symbols. The fonts come with a <i>fourier</i> package for use with LaTeX; - text support of OT1 encoding is not provided — you are + 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> @@ -73,10 +73,10 @@ mathematics include: 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’ + successful, and their use may be suppressed when loading the fonts’ <i>kpfonts</i> LaTeX support package). <p/> For an example, see \url{http://www.tug.dk/FontCatalogue/kpserif/} -<dt>MathDesign<dd>(4 entire families…so far) Paul Pichaureau<br> +<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 @@ -93,13 +93,13 @@ mathematics include: \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 + Belleek is the upshot of Kinch’s thoughts on how Metafont might be used in the future: they were published simultaneously as Metafont source, - as Type 1 fonts, and as TrueType fonts. The fonts act as “drop-in” - replacements for the basic MathTime set (as an example of “what might - be done”). -<p/> The paper outlining Kinch’s thoughts, proceeding from considerations - of the ‘intellectual’ superiority of Metafont to evaluations of why its + as Type 1 fonts, and as TrueType fonts. The fonts act as “drop-in” + replacements for the basic MathTime set (as an example of “what might + be done”). +<p/> The paper outlining Kinch’s thoughts, proceeding from considerations + of the ‘intellectual’ superiority of Metafont to evaluations of why its adoption is so limited and what might be done about the problem, is to be found at <a href="http://truetex.com/belleek.pdf">http://truetex.com/belleek.pdf</a> (the paper is a good read, but is set with Bitmap fonts, and can be difficult @@ -120,10 +120,10 @@ mathematics include: 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 +(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 +<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. @@ -153,23 +153,23 @@ commercially, include: For further details (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/chmath/chmain.htm">http://www.micropress-inc.com/fonts/chmath/chmain.htm</a> -<dt>Computer Modern Bright<dd>(62 fonts — optical scaling) Walter +<dt>Computer Modern Bright<dd>(62 fonts — optical scaling) Walter Schmidt<br> - CM Bright is a family of sans serif fonts, based on Knuth’s + CM Bright is a family of sans serif fonts, based on Knuth’s CM fonts. It comprises the fonts necessary for mathematical typesetting, including AMS symbols, as well as text and text symbol fonts of various shapes. The collection comes with its own set of files for use with LaTeX. The CM Bright fonts are supplied in Type 1 format by MicroPress, Inc. The <i>hfbright</i> bundle offers free Type 1 fonts for text using - the OT1 encoding — the <i>cm-super</i> fonts provide the - fonts in T1 text encoding but don’t support CM bright + the OT1 encoding — the <i>cm-super</i> fonts provide the + fonts in T1 text encoding but don’t support CM bright mathematics. <p/> - For further details of Micropress’ offering (including samples) see<br> + For further details of Micropress’ offering (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/brmath/brmain.htm">http://www.micropress-inc.com/fonts/brmath/brmain.htm</a> -<dt>Concrete Math<dd>(25 fonts — optical scaling) Ulrik Vieth<br> +<dt>Concrete Math<dd>(25 fonts — optical scaling) Ulrik Vieth<br> The Concrete Math font set was derived from the Concrete Roman typefaces designed by Knuth. The set provides a collection of math italics, math symbol, and math extension fonts, and fonts of @@ -200,7 +200,7 @@ commercially, include: <dt>Informal Math<dd>(7 outline fonts) MicroPress Inc.<br> Informal Math is a family of fanciful fonts loosely based on the - Adobe’s Tekton (TM) family, fonts which imitate handwritten + Adobe’s Tekton (TM) family, fonts which imitate handwritten text. Informal Math comprises the fonts necessary for mathematical typesetting (maths italic, maths symbols and extensions) in normal weight, as well as OT1 encoded text fonts in @@ -213,21 +213,21 @@ commercially, include: <dt>Lucida Bright <em>with</em> Lucida New Math<dd>(25 fonts) Chuck Bigelow and Kris Holmes<br> Lucida is a family of related fonts including seriffed, sans serif, - sans serif fixed width, calligraphic, blackletter, fax, Kris Holmes’ - connected handwriting font, <em>etc</em>; they’re not as ‘spindly’ as + sans serif fixed width, calligraphic, blackletter, fax, Kris Holmes’ + connected handwriting font, <em>etc</em>; they’re not as ‘spindly’ as Computer Modern, with a large x-height, and include a larger set of maths symbols, operators, relations and delimiters than CM (over 800 instead of 384: among others, it also includes the - AMS <i>msam</i> and <i>msbm</i> symbol sets). ‘Lucida - Bright Expert’ + 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 + smallcaps, bold maths, upright ‘maths italic’, <em>etc</em>., to the set. Support under LaTeX is available under the auspices of the PSNFSS, and pre-built metrics are also provided. <p/> TUG has the right to distribute these fonts; the web site - “<a href="http://tug.org/lucida/">Lucida and TUG</a>” + “<a href="http://tug.org/lucida/">Lucida and TUG</a>” has details. <dt>Adobe Lucida, LucidaSans <em>and</em> LucidaMath<dd>(12 fonts)<br> @@ -287,8 +287,8 @@ commercially, include: <a href="http://www.micropress-inc.com/fonts/tmmath/tmmain.htm">http://www.micropress-inc.com/fonts/tmmath/tmmain.htm</a> </dl> -Two other font sets should be mentioned, even though they don’t -currently produce satisfactory output — their author is no longer +Two other font sets should be mentioned, even though they don’t +currently produce satisfactory output — their author is no longer working on them, and several problems have been identified: <dl> <dt>pxfonts set version 1.0<dd>(26 fonts) by Young Ryu<br> @@ -323,7 +323,7 @@ working on them, and several problems have been identified: <li> virtual text fonts using <i>Adobe</i> <i>Times</i> (or the URW replacement used by <i>ghostscript</i>) with modified plus, equal and slash symbols; - <li> matching sets of sans serif and monospace (‘typewriter’) + <li> matching sets of sans serif and monospace (‘typewriter’) fonts (the sans serif set is based on <i>Adobe</i> <i>Helvetica</i>); <li> maths alphabets using <i>Times</i>; <li> maths fonts of all symbols in the computer modern maths fonts @@ -354,7 +354,7 @@ Finally, one must not forget: works with TeX can give a publisher a real competitive advantage, there are some publishers that have paid (a lot) to have such font sets made for them. Unfortunately, these sets are not available on - the open market, despite the likelihood that they’re more complete + the open market, despite the likelihood that they’re more complete than those that are. </dl> We observe a very limited selection of commercial maths font sets; a @@ -364,13 +364,13 @@ Furthermore, the TeX market for commercial fonts is minute by comparison with the huge sales of other font sets. <p/>Text fonts in Type 1 format are available from many vendors including Adobe, Monotype and Bitstream. However, be careful with cheap font -“collections”; many of them dodge copyright restrictions by removing +“collections”; many of them dodge copyright restrictions by removing (or crippling) parts of the font programs such as hinting. Such behaviour is both unethical and bad for the consumer. The fonts may not render well (or at all, under ATM), may not have the -‘standard’ complement of 228 glyphs, or may not include metric files +‘standard’ complement of 228 glyphs, or may not include metric files (which you need to make TFM files). -<p/>TrueType remains the “native” format for Windows. Some TeX +<p/>TrueType remains the “native” format for Windows. Some TeX implementations such as <a href="FAQ-commercial.html">TrueTeX</a> use TrueType versions of Computer Modern and Times Maths fonts to render TeX documents in Windows without the need for additional system software like @@ -382,7 +382,7 @@ further use, you should consider whether a given font format will introduce compatibility problems. Publishers may require TrueType exclusively because their systems are Windows-based, or Type 1 exclusively, because their systems are based on the early popularity of that format in the publishing industry. -Many service bureaus don’t care as long as you present them with a finished +Many service bureaus don’t care as long as you present them with a finished print file (PostScript or PDF) for their output device. <dl> <dt><tt><i>CM family collection</i></tt><dd> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html index 0a1a8ea52b9..c8755b27293 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfontprob.html @@ -7,8 +7,8 @@ <p/>First, you have to declare to the DVI driver that you are using PostScript fonts; in the case of <i>dvips</i>, this means adding lines to the <i>psfonts.map</i> file, so that <i>dvips</i> will know -where the proper fonts are, and won’t try to find PK -files. If the font isn’t built into the printer, you have to acquire +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). <p/>Second, your previewer must know what to do with the fonts: see <a href="FAQ-PSpreview.html">previewing type 1 fonts</a>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html index 37c3571a503..fcbd53bf70a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ragright.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label ragright</title> </head><body> <h3>Setting text ragged right</h3> -<p/>The trick with typesetting ragged right is to be sure you’ve told the -TeX engine “make this paragraph ragged, but never <em>too</em> -ragged”. The LaTeX <code>\</code><code>raggedright</code> command (and the +<p/>The trick with typesetting ragged right is to be sure you’ve told the +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 +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 +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 +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 +<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 significance of the various -parameters of <i>ragged2e</i>’s operation. +parameters of <i>ragged2e</i>’s operation. <dl> -<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>) +<dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/ragged2e.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html index ad6e7e4d009..55fcdc96b2f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html @@ -3,12 +3,12 @@ </head><body> <h3>Using TeX to read SGML or XML directly</h3> <p/>This can nowadays be done, with a certain amount of clever macro -programming. David Carlisle’s <i>xmltex</i> is the prime example; +programming. David Carlisle’s <i>xmltex</i> is the prime example; it offers a practical solution to typesetting XML files. <p/>One use of a TeX that can typeset XML files is as a backend processor for XSL formatting objects, serialized as XML. -Sebastian Rahtz’s PassiveTeX uses <i>xmltex</i> to +Sebastian Rahtz’s PassiveTeX uses <i>xmltex</i> to achieve this end. <dl> <dt><tt><i>xmltex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/base.zip">macros/xmltex/base</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/base/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html index 1501bc21095..06300733ac6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readtex.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label readtex</title> </head><body> <h3>Reading (La)TeX files</h3> -<p/>So you’ve been sent a TeX file: what are you going to do with it? -<p/>You can, of course, “just read it”, since it’s a plain text file, +<p/>So you’ve been sent a TeX file: what are you going to do with it? +<p/>You can, of course, “just read it”, since it’s a plain text file, but the markup tags in the document may prove distracting. Most of the time, even TeX experts will typeset a TeX file before attempting to read it. @@ -12,29 +12,29 @@ systems are available, free, for most sorts of computer; the bad news is that you need a pretty complete TeX system even to read a single file, and complete TeX systems are pretty large. <p/>TeX is a typesetting system that arose from a publishing project (see -“<a href="FAQ-whatTeX.html">what is TeX</a>”), +“<a href="FAQ-whatTeX.html">what is TeX</a>”), and its basic source is available free from its author. However, at its root, it is <em>just</em> a typesetting engine: even to view or to print the typeset output, you will need ancillary programs. In short, -you need a TeX <em>distribution</em> — a collection of +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 -“<a href="FAQ-TeXsystems.html">TeX distributions</a>” +“<a href="FAQ-TeXsystems.html">TeX distributions</a>” or -“<a href="FAQ-commercial.html">commercial TeX distributions</a>”. -<p/>But beware — TeX makes no attempt to look like the sort of -WYSIWYG system you’re probably used to (see +“<a href="FAQ-commercial.html">commercial TeX distributions</a>”. +<p/>But beware — TeX makes no attempt to look like the sort of +WYSIWYG system you’re probably used to (see -“<a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>”): -while many modern versions of TeX have a compile–view cycle that +“<a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>”): +while many modern versions of TeX have a compile–view cycle that rivals the best commercial word processors in its responsiveness, what you type is usually <em>markup</em>, which typically defines a logical (rather than a visual) view of what you want typeset. -<p/>So there’s a balance between the simplicity of the original +<p/>So there’s a balance between the simplicity of the original (marked-up) document, which can more-or-less be read in <em>any</em> editor, and the really rather large investment needed to install a -system to read a document “as intended”. +system to read a document “as intended”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html index d21944babf0..9d68d4c176f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reallyblank.html @@ -6,7 +6,7 @@ option) ensure that each chapter starts on a right-hand (recto) page; they do this by inserting a <code>\</code><code>cleardoublepage</code> command between chapters (rather than a mere <code>\</code><code>clearpage</code>). The empty page thus -created gets to have a normal running header, which some people don’t +created gets to have a normal running header, which some people don’t like. <p/>The (excellent) <i>fancyhdr</i> manual covers this issue, basically advising the creation of a command <code>\</code><code>clearemptydoublepage</code>: @@ -19,11 +19,11 @@ advising the creation of a command <code>\</code><code>clearemptydoublepage</cod } </pre> </blockquote><p> -The “obvious” thing is then to use this command to replace +The “obvious” thing is then to use this command to replace <code>\</code><code>cleardoublepage</code> in a patched version of the <code>\</code><code>chapter</code> command. (Make a package of your own containing a copy -of the command out of the class.) This isn’t particularly difficult, -but you can instead simply subvert <code>\</code><code>cleardoublepage</code> (which isn’t +of the command out of the class.) This isn’t particularly difficult, +but you can instead simply subvert <code>\</code><code>cleardoublepage</code> (which isn’t often used elsewhere): <blockquote> <pre> @@ -46,11 +46,11 @@ of these empty pages. The classes also offer do-it-yourself commands provide commands <code>\</code><code>cleartooddpage</code> and <code>\</code><code>cleartoevenpage</code>, which both take an optional argument (the first, with no argument, being an equivalent of <code>\</code><code>cleardoublepage</code>). One can achieve -‘special’ effects by putting commands in the optional argument: the -<code>\</code><code>clearemptydoublepage</code> we’re after would be achieved by +‘special’ effects by putting commands in the optional argument: the +<code>\</code><code>clearemptydoublepage</code> we’re after would be achieved by <code>\</code><code>cleartooddpage[</code><code>\</code><code>thispagestyle{empty}</code><code>]</code>. The -commands will also serve if you want the surreal effect of “This page -intentionally left blank” in the centre of an otherwise empty page. +commands will also serve if you want the surreal effect of “This page +intentionally left blank” in the centre of an otherwise empty page. <dl> <dt><tt><i>fancyhdr</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html index 0513dc7d8f4..6d54bafaf7f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label recovertex</title> </head><body> <h3>Retrieving (La)TeX from DVI, etc.</h3> -<p/>The job just can’t be done automatically: DVI, PostScript and -PDF are “final” formats, supposedly not susceptible to -further editing — information about where things came from has been -discarded. So if you’ve lost your (La)TeX source (or never -had the source of a document you need to work on) you’ve a serious job +<p/>The job just can’t be done automatically: DVI, PostScript and +PDF are “final” formats, supposedly not susceptible to +further editing — information about where things came from has been +discarded. So if you’ve lost your (La)TeX source (or never +had the source of a document you need to work on) you’ve a serious job on your hands. In many circumstances, the best strategy is to retype the whole document, but this strategy is to be tempered by -consideration of the size of the document and the potential typists’ +consideration of the size of the document and the potential typists’ skills. -<p/>If automatic assistance is necessary, it’s unlikely that any more than +<p/>If automatic assistance is necessary, it’s unlikely that any more than text retrieval is going to be possible; the (La)TeX markup that creates the typographic effects of the document needs to be recreated by editing. @@ -20,7 +20,7 @@ for <a href="FAQ-toascii.html">converting (La)TeX to ASCII</a> are applicable. Consider <i>dvi2tty</i>, <i>crudetype</i> and <i>catdvi</i>. Remember that there are likely to be problems finding included material (such as included PostScript figures, that -don’t appear in the DVI file itself), and mathematics is +don’t appear in the DVI file itself), and mathematics is unlikely to convert easily. <p/>To retrieve text from PostScript files, the <i>ps2ascii</i> tool (part of the <i>ghostscript</i> @@ -36,10 +36,10 @@ thence to well-formed XHTML, and import the results into Microsoft <i>Word</i> (2000 or later). From there, one may convert to (La)TeX using one of the techniques discussed in -“<a href="FAQ-fmtconv.html">converting to and from (La)TeX</a>”. +“<a href="FAQ-fmtconv.html">converting to and from (La)TeX</a>”. <p/>The result will typically (at best) be poorly marked-up. Problems may also arise from the oddity of typical TeX font encodings (notably -those of the maths fonts), which <i>Acrobat</i> doesn’t know how +those of the maths fonts), which <i>Acrobat</i> doesn’t know how to map to its standard Unicode representation. <dl> <dt><tt><i>catdvi</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html index c240f0e7332..45a3266e091 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html @@ -4,26 +4,26 @@ <h3>Reference documents</h3> <p/>For TeX primitive commands a rather nice <a href="http://www.nmt.edu/tcc/help/pubs/texcrib.pdf">quick reference booklet</a>, -by John W. Shipman, is available; it’s arranged in the same way as the -TeXbook. By contrast, you can view David Bausum’s +by John W. Shipman, is available; it’s arranged in the same way as the +TeXbook. By contrast, you can view David Bausum’s <a href="http://www.tug.org/utilities/plain/cseq.html">list of TeX primitives</a> -alphabetically or arranged by “family”. Either way, the list has a +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 TeXbook. -<p/>There doesn’t seem to be a reference that takes in Plain TeX as +<p/>There doesn’t seem to be a reference that takes in Plain TeX as well as the primitive commands. -<p/>An interesting LaTeX “cheat sheet” is available from CTAN: -it’s a list of (more or less) everything you ‘ought to’ remember, for -basic LaTeX use. (It’s laid out very compactly for printing on N.\ -American ‘letter’; printed on ISO A4, using Adobe -Acrobat’s “shrink to fit”, it strains aged eyes…) -<p/>Similarly, there’s no completely reliable command-organised reference +<p/>An interesting LaTeX “cheat sheet” is available from CTAN: +it’s a list of (more or less) everything you ‘ought to’ remember, for +basic LaTeX use. (It’s laid out very compactly for printing on N.\ +American ‘letter’; printed on ISO A4, using Adobe +Acrobat’s “shrink to fit”, it strains aged eyes…) +<p/>Similarly, there’s no completely reliable command-organised reference to LaTeX. The page (provided by NASA) <a href="http://www.giss.nasa.gov/latex/">Hypertext Help with LaTeX</a> is recently much improved. It still talks in LaTeX 2.09-isms in places, -but it’s been updated for current LaTeX. There are a number of -mirrors of the site, and it may be worth choosing a “local” one if -you’re going to use it a lot. +but it’s been updated for current LaTeX. There are a number of +mirrors of the site, and it may be worth choosing a “local” one if +you’re going to use it a lot. <p/>Another LaTeX2e reference (provided by the Emerson Center of Emory University) is: <a href="http://www.emerson.emory.edu/services/latex/latex2e/latex2e_toc.html">LaTeXe help</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html index bbafebbfbd1..190490876eb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html @@ -2,58 +2,58 @@ <title>UK TeX FAQ -- question label repeatgrf</title> </head><body> <h3>Repeated graphics in a document</h3> -<p/>A logo or “watermark” image, or any other image that is repeated in +<p/>A logo or “watermark” image, or any other image that is repeated in your document, has the potential to make the processed version of the document unmanageably large. The problem is, that the default -mechanisms of graphics usage add the image at every point it’s to be +mechanisms of graphics usage add the image at every point it’s to be used, and when processed, the image appears in the output file at each such point. <p/>Huge PostScript files are embarrassing; explaining <em>why</em> such a file is huge, is more embarrassing still. <p/>The <a href="FAQ-tutbitslatex.html"><i>epslatex</i> graphics tutorial</a> describes a technique for avoiding the problem: basically, one -converts the image that’s to be repeated into a PostScript subroutine, and +converts the image that’s to be repeated into a PostScript subroutine, and load that as a <i>dvips</i> prologue file. In place of the image, you load a file (with the same bounding box as the image) containing no more than an invocation of the subroutine defined in the prologue. <p/>The <i>epslatex</i> technique is tricky, but does the job. Trickier still is the neat scheme of converting the figure to a one-character -Adobe Type 3 outline font. While this technique is for the “real -experts” only (the author of this answer has never even tried it), it has +Adobe Type 3 outline font. While this technique is for the “real +experts” only (the author of this answer has never even tried it), it has potential for the same sort of space saving as the <i>epslatex</i> technique, with greater flexibility in actual use. -<p/>More practical is Hendri Adriaens’ <i>graphicx-psmin</i>; you load +<p/>More practical is Hendri Adriaens’ <i>graphicx-psmin</i>; you load this <em>in place</em> of <i>graphicx</i>, so rather than: <blockquote> <pre> -\usepackage[<options>]{graphicx} +\usepackage[<options>]{graphicx} </pre> </blockquote><p> you will write: <blockquote> <pre> -\usepackage[<options>]{graphicx-psmin} +\usepackage[<options>]{graphicx-psmin} </pre> </blockquote><p> and at the start of your document, you write: <blockquote> <pre> -\loadgraphics[<bb>]{<list of graphics>} +\loadgraphics[<bb>]{<list of graphics>} </pre> </blockquote><p> -and each of the graphics in the list is converted to an “object” for +and each of the graphics in the list is converted to an “object” for use within the resulting PostScript output. (This is, in essence, an automated version of the <i>epslatex</i> technique described above.) <p/>Having loaded the package as above, whenever you use -<code>\</code><code>includegraphics</code>, the command checks if the file you’ve asked for -is one of the graphics in <code>\</code><code>loadgraphics</code>’ list. If so, the -operation is converted into a call to the “object” rather than a new +<code>\</code><code>includegraphics</code>, the command checks if the file you’ve asked for +is one of the graphics in <code>\</code><code>loadgraphics</code>’ list. If so, the +operation is converted into a call to the “object” rather than a new copy of the file; the resulting PostScript can of course be <em>much</em> smaller. <p/>Note that the package requires a recent <i>dvips</i>, version -5.95b (this version isn’t — yet — widely distributed). +5.95b (this version isn’t — yet — widely distributed). <p/>If your PostScript is destined for conversion to PDF, either by a <i>ghostscript</i>-based mechanism such as <i>ps2pdf</i> or by -(for example) <i>Acrobat</i> <i>Distiller</i>, the issue isn’t +(for example) <i>Acrobat</i> <i>Distiller</i>, the issue isn’t so pressing, since the distillation mechanism will amalgamate graphics objects whether or not the PostScript has them amalgamated. PDFTeX does the same job with graphics, automatically converting multiple uses diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html index aac95f3e4fb..56a4ec84408 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repfootnote.html @@ -3,10 +3,10 @@ </head><body> <h3>Footnotes whose texts are identical</h3> <p/>If the <em>same</em> footnote turns up at several places within a -document, it’s often inappropriate to repeat the footnote in its +document, it’s often inappropriate to repeat the footnote in its entirety over and over again. We can avoid repetition by semi-automatic means, or by simply labelling footnotes that we know -we’re going to repeat and then referencing the result. There is no +we’re going to repeat and then referencing the result. There is no completely automatic solution (that detects and suppresses repeats) available. <p/>If you know you only have one footnote, which you want to repeat, the @@ -19,7 +19,7 @@ solution is simple: merely use the optional argument of ...\footnotemark[1] </pre> </blockquote><p> -… which is very easy, since we know there will only ever be a +… which is very easy, since we know there will only ever be a footnote number 1. A similar technique can be used once the footnotes are stable, reusing the number that LaTeX has allocated. This can be tiresome, though, as any change of typesetting could change the @@ -36,7 +36,7 @@ to the job: ...\footnotemark[\thefnnumber] </pre> </blockquote><p> -but this is somewhat tedious. LaTeX’s labelling mechanism can be +but this is somewhat tedious. LaTeX’s labelling mechanism can be summoned to our aid, but there are ugly error messages before the <code>\</code><code>ref</code> is resolved on a second run through LaTeX: <blockquote> @@ -47,7 +47,7 @@ summoned to our aid, but there are ugly error messages before the </pre> </blockquote><p> Alternatively, one may use the <code>\</code><code>footref</code> command, which has the -advantage of working even when the footnote mark isn’t expressed as a +advantage of working even when the footnote mark isn’t expressed as a number. The command is defined in the <i>footmisc</i> package and in the <i>memoir</i> class (at least); <code>\</code><code>footref</code> reduces the above example to: @@ -62,9 +62,9 @@ This is the cleanest simple way of doing the job. Note that the <code>\</code><code>label</code> command <em>must</em> be inside the argument of <code>\</code><code>footnote</code>. <p/>The <i>fixfoot</i> package takes away some of the pain of the -matter: you declare footnotes you’re going to reuse, typically in the +matter: you declare footnotes you’re going to reuse, typically in the preamble of your document, using a <code>\</code><code>DeclareFixedFoot</code> command, and -then use the command you’ve ‘declared’ in the body of the document: +then use the command you’ve ‘declared’ in the body of the document: <blockquote> <pre> \DeclareFixedFootnote{\rep}{Text to repeat} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html index 7f56c113063..073f82fb87c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-replstdcls.html @@ -5,7 +5,7 @@ <p/>People are forever concocting classes that replace the standard ones: the present author produced an <i>ukart</i> class that used the <i>sober</i> package, and a few British-specific things (such as -appear in the <i>babel</i> package’s British-english +appear in the <i>babel</i> package’s British-english specialisation) in the 1980s, which is still occasionally used. <p/>Similar public efforts were available well back in the days of LaTeX 2.09: a notable example, whose pleasing designs seem not to have @@ -24,7 +24,7 @@ and German (<i>scrguien</i> in the distribution for English, <p/>The other comparable class is <i>memoir</i>. This aims to replace <i>book</i> and <i>report</i> classes directly, and (like <i>KOMA-script</i>) is comprehensive in its coverage of small issues. -<i>Memoir</i>’s documentation (<i>memman</i>) is very highly +<i>Memoir</i>’s documentation (<i>memman</i>) is very highly spoken of, and its lengthy introductory section is regularly recommended as a tutorial on typesetting. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html index 7926de2b1db..d5b99c3b70b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rerun.html @@ -1,25 +1,25 @@ <head> <title>UK TeX FAQ -- question label rerun</title> </head><body> -<h3>“Rerun” messages won’t go away</h3> -<p/>The LaTeX message “Rerun to get crossreferences right” is +<h3>“Rerun” messages won’t go away</h3> +<p/>The LaTeX message “Rerun to get crossreferences right” is supposed to warn the user that the job needs to be processed again, since labels seem to have changed since the previous run. (LaTeX compares the labels it has created this time round with what it found from the previous run when it started; it does this comparison at <code>\</code><code>end{document}</code>.) -<p/>Sometimes, the message won’t go away: however often you reprocess your -document, LaTeX still tells you that “Label(s) may have -changed”. This can sometimes be caused by a broken package: both +<p/>Sometimes, the message won’t go away: however often you reprocess your +document, LaTeX still tells you that “Label(s) may have +changed”. This can sometimes be caused by a broken package: both <i>footmisc</i> (with the <code>perpage</code> option) and <i>hyperref</i> have been known to give trouble, in the past: if you are using either, check you have the latest version, and upgrade if possible. <p/>However, there <em>is</em> a rare occasion when this error can happen as a result of pathological structure of the document itself. Suppose you have pages numbered in roman, and you add a reference to a label -on page “ix” (9). The presence of the reference pushes the thing -referred to onto page “x” (10), but since that’s a shorter reference -the label moves back to page “ix” at the next run. Such a sequence +on page “ix” (9). The presence of the reference pushes the thing +referred to onto page “x” (10), but since that’s a shorter reference +the label moves back to page “ix” at the next run. Such a sequence can obviously not terminate. <p/>The only solution to this problem is to make a small change to your document (something as small as adding or deleting a comma will often diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html index 633c4c3bac0..fc079f6f193 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-resolns.html @@ -1,30 +1,30 @@ <head> <title>UK TeX FAQ -- question label resolns</title> </head><body> -<h3>What are “resolutions”?</h3> -<p/>“Resolution” is a word that is used with little concern for its +<h3>What are “resolutions”?</h3> +<p/>“Resolution” is a word that is used with little concern for its multiple meanings, in computer equipment marketing. The word suggests a measure of what an observer (perhaps the human eye) can resolve; yet we regularly see advertisements for printers whose resolution is -1200dpi — far finer than the unaided human eye can distinguish. The +1200dpi — far finer than the unaided human eye can distinguish. The advertisements are talking about the precision with which the printer can place spots on the printed image, which affects the fineness of the representation of fonts, and the accuracy of the placement of glyphs and other marks on the page. -<p/>In fact, there are two sorts of “resolution” on the printed page -that we need to consider for (La)TeX’s purposes: +<p/>In fact, there are two sorts of “resolution” on the printed page +that we need to consider for (La)TeX’s purposes: <ul> <li> the positioning accuracy, and <li> the quality of the fonts. </ul> In the case where (La)TeX output is being sent direct to a printer, -in the printer’s “native” language, it’s plain that the DVI +in the printer’s “native” language, it’s plain that the DVI processor must know all such details, and must take detailed account of both types of resolution. <p/>In the case where output is being sent to an intermediate distribution format, that has potential for printing (or displaying) we know not where, the final translator, that connects to directly to the printer -or display, has the knowledge of the device’s properties: the +or display, has the knowledge of the device’s properties: the DVI processor need not know, and should not presume to guess. <p/>Both PostScript and PDF output are in this category. While PostScript is used less frequently for document distribution nowadays, it is @@ -32,11 +32,11 @@ regularly used as the source for distillation into PDF; and PDF is the workhorse of an enormous explosion of document distribution. <p/>Therefore, we need DVI processors that will produce -“resolution independent” PostScript or PDF output; of course, the +“resolution independent” PostScript or PDF output; of course, the independence needs to extend to both forms of independence outlined above. <p/>Resolution-independence of fonts was for a long time forced upon the -world by the feebleness of Adobe’s <i>Acrobat</i> +world by the feebleness of Adobe’s <i>Acrobat</i> <i>Reader</i> at dealing with bitmap files: a sequence of answers starting with one aiming at the <a href="FAQ-dvips-pdf.html">quality of PDF from PostScript</a> addresses @@ -44,8 +44,8 @@ the problems that arise. <p/>Resolution-independence of positioning is more troublesome: <i>dvips</i> is somewhat notorious for insisting on positioning to the accuracy of the declared resolution of the printer. -One commonly-used approach is to declare a resolution of 8000 (“better -than any device”), and this is reasonably successful though it does +One commonly-used approach is to declare a resolution of 8000 (“better +than any device”), and this is reasonably successful though it does have its <a href="FAQ-8000.html">problems</a>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html index e7f3dea4ccd..345500afc8c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-reuseq.html @@ -24,14 +24,9 @@ Remember that Here, the second instance of a=b will be typeset with a copy, made by the <code>\</code><code>tag</code> command, of the label of the first instance. -<p/>Comprehensive documentation of AMSLaTeX is to be found in -<i>amsldoc</i>, in the distribution; it is also available on the web -at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a> <dl> -<dt><tt><i>amsldoc.tex</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX - <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsmath.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html index 6304b86a707..56257294a66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-rulethk.html @@ -6,17 +6,17 @@ this is in fact a default built in at the lowest level, and applies to all rules (including those separating blocks of running text). <p/>Sometimes, however, we look at a table and find we want the rules to -stand out — perhaps to separate the text from the rest of the body +stand out — perhaps to separate the text from the rest of the body text, or to make the sections of the table stand out from one another. However, a quick review of any LaTeX manual will reveal no technique for making any one rule stand out, and a little experimentation shows that it is indeed pretty difficult to prevent -a change “bleeding” out to affect other rules in the same table. +a change “bleeding” out to affect other rules in the same table. <p/>If you look at what we have to say on the <a href="FAQ-destable.html">design of tables</a>, elsewhere among these FAQs, and you may sense that the design of LaTeX -simply skipped the issues surrounding table design: <em>that’s</em> -presumably why there’s no facilities to help you. +simply skipped the issues surrounding table design: <em>that’s</em> +presumably why there’s no facilities to help you. <p/>Specifically, the length <code>\</code><code>arrayrulewidth</code> affects the thickness of the rules (both horizontal and vertical) within both <code>tabular</code> and <code>array</code> environments. If you @@ -28,7 +28,7 @@ change from the default (see above) only as far as </blockquote><p> the change is remarkably striking. However, really quite subtle user level programming proves incapable of changing just <em>one</em> rule: -it’s necessary to delve into the (rather tricky) code of <code>\</code><code>hline</code> +it’s necessary to delve into the (rather tricky) code of <code>\</code><code>hline</code> and <code>\</code><code>cline</code> themselves. <p/>Fortunately, this job has already been done for the community: the <i>booktabs</i> package defines three different classes of rule diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html index 7a46221f39b..0c9ab2d1788 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-run-fn-nos.html @@ -7,10 +7,10 @@ different set of footnotes per chapter, by resetting the footnote number at the start of the chapter. This is essentially the same action as that of <a href="FAQ-running-nos.html">equation, figure and table numbers</a>, -except that footnote numbers don’t get “decorated” with the chapter +except that footnote numbers don’t get “decorated” with the chapter number, as happens with those other numbers. <p/>The solution is the same: use the <i>chngcntr</i> package; since the -numbers aren’t “decorated” you can use the <code>\</code><code>counterwithout*</code> +numbers aren’t “decorated” you can use the <code>\</code><code>counterwithout*</code> variant; the code: <blockquote> <pre> @@ -19,7 +19,7 @@ variant; the code: </blockquote><p> is all you need <dl> -<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> +<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr.zip">macros/latex/contrib/chngcntr</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr/">browse the directory</a>) </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html index 9a7a49598ad..02c61b595c5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html @@ -4,7 +4,7 @@ <h3>My section title is too wide for the page header</h3> <p/>By default, LaTeX sectioning commands make the chapter or section title available for use by page headers and the like. Page headers -operate in a rather constrained area, and it’s common for titles too +operate in a rather constrained area, and it’s common for titles too be too big to fit: the LaTeX sectioning commands therefore take an optional argument: <blockquote> @@ -23,12 +23,12 @@ scheme is to have a shortened table of contents entry, and a really terse entry in the running head. <p/>One of the problems is the tendency of page headings to be set in capitals (which take up more space); so why not set headings as written -for “ordinary” reading? It’s not possible to do so with unmodified +for “ordinary” reading? It’s not possible to do so with unmodified LaTeX, but the <i>fancyhdr</i> package provides a command <code>\</code><code>nouppercase</code> for use in its header (and footer) lines to suppress -LaTeX’s uppercasing tendencies. Classes in the <i>KOMA-script</i> -bundle don’t uppercase in the first place. -<p/>In fact, the sectioning commands use ‘mark’ commands to pass +LaTeX’s uppercasing tendencies. Classes in the <i>KOMA-script</i> +bundle don’t uppercase in the first place. +<p/>In fact, the sectioning commands use ‘mark’ commands to pass information to the page headers. For example, <code>\</code><code>chapter</code> uses <code>\</code><code>chaptermark</code>, <code>\</code><code>section</code> uses <code>\</code><code>sectionmark</code>, and so on. With this knowledge, one can achieve a three-layer structure for chapters: @@ -55,10 +55,10 @@ the recipe for sections is more tiresome: (the first <code>\</code><code>sectionmark</code> deals with the header of the page the <code>\</code><code>section</code> command falls on, and the second deal with subsequent pages; note that here, you need the optional argument to <code>\</code><code>section</code>, -even if “<em>middling version</em>” is in fact the same text as -“<em>long version”</em>.) +even if “<em>middling version</em>” is in fact the same text as +“<em>long version”</em>.) <p/>A similar arrangement is necessary even for chapters if the class -you’re using is odd enough that it puts a page header on a chapter’s +you’re using is odd enough that it puts a page header on a chapter’s opening page. <p/>Note that the <i>titlesec</i> package manages the running heads in a completely different fashion; users of that package should refer to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html index 70149030d49..65313666f92 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-running-nos.html @@ -4,21 +4,21 @@ <h3>Running equation, figure and table numbering</h3> <p/>Many LaTeX classes (including the standard <i>book</i> class) number things per chapter; so figures in chapter 1 are numbered 1.1, -1.2, and so on. Sometimes this is not appropriate for the user’s +1.2, and so on. Sometimes this is not appropriate for the user’s needs. <p/>Short of rewriting the whole class, one may use the <i>chngcntr</i> package, which provides commands <code>\</code><code>counterwithin</code> (which establishes this nested numbering relationship) and <code>\</code><code>counterwithout</code> (which undoes it). -<p/>So if you have figures numbered by chapter as 1.1, 1.2, 2.1, …, +<p/>So if you have figures numbered by chapter as 1.1, 1.2, 2.1, …, the command <blockquote> <pre> \counterwithout{figure}{chapter} </pre> </blockquote><p> -will convert them to figures 1, 2, 3, …. (Note that the command -has also removed the chapter number from the counter’s definition.) +will convert them to figures 1, 2, 3, …. (Note that the command +has also removed the chapter number from the counter’s definition.) <p/>More elaborate use could change things numbered per section to things numbered per chapter: <blockquote> @@ -28,7 +28,7 @@ numbered per chapter: </pre> </blockquote><p> (assuming there was a class that did such a thing in the first place...) -<p/>The <i>chngcntr</i> approach doesn’t involve much programming, and +<p/>The <i>chngcntr</i> approach doesn’t involve much programming, and the enthusiastic LaTeX programmer might choose to try the technique that we had to use before the advent of <i>chngcntr</i>. Each of the packages <i>removefr</i> and <i>remreset</i> defines a @@ -51,7 +51,7 @@ way in which the figure number (in this case) is printed: </pre> </blockquote><p> (remember to do the whole job, for every counter you want to -manipulate, within <code>\</code><code>makeatletter</code> … <code>\</code><code>makeatother</code>). +manipulate, within <code>\</code><code>makeatletter</code> … <code>\</code><code>makeatother</code>). <p/>This technique, too, may be used to change where in a multilevel structure a counter is reset. Suppose your class numbers figures as <<i>chapter</i>>.<<i>section</i>>.<<i>figure</i>>, and you want figures @@ -68,12 +68,12 @@ numbered per chapter, try: </blockquote><p> (the command <code>\</code><code>@addtoreset</code> is a part of LaTeX itself). <dl> -<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> +<dt><tt><i>chngcntr.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr.zip">macros/latex/contrib/chngcntr</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chngcntr/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>removefr.tex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fragments/removefr.tex">macros/latex/contrib/fragments/removefr.tex</a> (note, this is constructed as a - “fragment” for use within other packages: load by + “fragment” for use within other packages: load by <code>\</code><code>input{removefr}</code>) -<dt><tt><i>remreset.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>) +<dt><tt><i>remreset.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/remreset.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html index 4a867aa5607..1b5c8da5c76 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label scriptfonts</title> </head><body> <h3>Better script fonts for maths</h3> -<p/>The font selected by <code>\</code><code>mathcal</code> is the only script font ‘built -in’. However, there are other useful calligraphic fonts included with +<p/>The font selected by <code>\</code><code>mathcal</code> is the only script font ‘built +in’. However, there are other useful calligraphic fonts included with modern TeX distributions. <dl> <dt>Euler<dd> The <i>eucal</i> package (part of most sensible TeX @@ -13,7 +13,7 @@ modern TeX distributions. <p/> Type 1 versions of the fonts are available in the AMS fonts distribution. <dt>RSFS<dd> The <i>mathrsfs</i> package uses a really fancy script - font (the name stands for “Ralph Smith’s Formal Script”) which is + font (the name stands for “Ralph Smith’s Formal Script”) which is already part of most modern TeX distributions (Type 1 versions of the font are also provided, courtesy of Taco Hoekwater). The package creates a new command <code>\</code><code>mathscr</code>. @@ -29,7 +29,7 @@ modern TeX distributions. <pre> \DeclareFontFamily{OT1}{pzc}{} \DeclareFontShape{OT1}{pzc}{m}{it}% - {<-> s * [0.900] pzcmi7t}{} + {<-> s * [0.900] pzcmi7t}{} \DeclareMathAlphabet{\mathscr}{OT1}{pzc}% {m}{it} </pre> @@ -37,7 +37,7 @@ modern TeX distributions. any but the most basic PostScript printers. A substantially identical font (to the extent that the same metrics may be used) is available from URW, called URW Chancery L: it is distributed - with Ghostscript, and as part of the “URW base35” bundle, which is + with Ghostscript, and as part of the “URW base35” bundle, which is available in most distributions. </dl> Examples of the available styles are available on CTAN. @@ -45,7 +45,7 @@ Examples of the available styles are available on CTAN. <dt><tt><i>eucal.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/">browse the directory</a>) <dt><tt><i>euler fonts</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/">browse the directory</a>) <dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> -<dt><tt><i>mathrsfs.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen.zip">macros/latex/contrib/jknappen</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen/">browse the directory</a>) +<dt><tt><i>mathrsfs.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen.zip">macros/latex/contrib/jknappen</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/mathrsfs.html">catalogue entry</a> <dt><tt><i>rsfs fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs.zip">fonts/rsfs</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs/">browse the directory</a>) <dt><tt><i>Script font examples</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/symbols/math/scriptfonts.pdf">info/symbols/math/scriptfonts.pdf</a> <dt><tt><i>URW Chancery L</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/fonts/urw/base35.zip">fonts/urw/base35</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/urw/base35/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html index 1a8545d5faa..dcc22ebb0af 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-seccntfmt.html @@ -7,17 +7,24 @@ pretty complex, and are covered in the question on <a href="FAQ-secthead.html">the style of section headings</a>. <p/>However, people regularly want merely to change the way the section -number appears in the heading, and some such people don’t mind writing +number appears in the heading, and some such people don’t mind writing out a few macros. This answer is for <em>them</em>. <p/>The section number is typeset using the <a href="FAQ-atsigns.html">LaTeX internal</a> -<code>\</code><code>@seccntformat</code> command, which is given the “name” (section, -subsection, …) of the heading, as argument. Ordinarily, +<code>\</code><code>@seccntformat</code> command, which is given the “name” (section, +subsection, …) of the heading, as argument. Ordinarily, <code>\</code><code>@seccntformat</code> -merely outputs the section number, and then a <code>\</code><code>quad</code> of space. +merely outputs the section number, and then a <code>\</code><code>quad</code> of space: +<blockquote> +<pre> +\renewcommand*{\@seccntformat}[1]{% + \csname the#1\endcsname\quad +} +</pre> +</blockquote><p> Suppose you want to put a stop after every section (subsection, -subsubsection, …) number, a trivial change may be implemented by +subsubsection, …) number, a trivial change may be implemented by simple modification of the command: <blockquote> <pre> @@ -26,44 +33,36 @@ simple modification of the command: } </pre> </blockquote><p> -<p/>Many people (for some reason) want a stop after a section number, but -not after a subsection number, or any of the others. -To do this, one must make <code>\</code><code>@seccntformat</code> switch according to its -argument. The following technique for doing the job is slightly -wasteful, but is efficient enough for a relatively rare operation: +However, many people want to modify section numbers, but not +subsection numbers, or any of the others. To do this, one must make +<code>\</code><code>@seccntformat</code> switch according to its argument. The following +technique for doing the job is slightly wasteful, but is efficient +enough for a relatively rare operation: <blockquote> <pre> -\let\@@seccntformat\@seccntformat \renewcommand*{\@seccntformat}[1]{% - \expandafter\ifx\csname @seccntformat@#1\endcsname\relax - \expandafter\@@seccntformat - \else - \expandafter - \csname @seccntformat@#1\expandafter\endcsname - \fi - {#1}% + \csname the#1\endcsname + \csname adddot@#1\endcsname\quad } </pre> </blockquote><p> - -which looks to see if a second-level command has been defined, and -uses it if so; otherwise it uses the original. The second-level -command to define stops after section numbers (only) has the same -definition as the original “all levels alike” version: +which uses a second-level command to provide the dot, if it has been +defined; otherwise it merely appends <code>\</code><code>relax</code> (which does nothing +in this context). The definition of the second-level command (the +version for the <code>section</code>, here) specifies what to put after a +section number, but it could be used to put anything after it: <blockquote> <pre> -\newcommand*{\@seccntformat@section}[1]{% - \csname the#1\endcsname.\quad -} +\newcommand*{\adddot@section}{.} </pre> </blockquote><p> -Note that all the command definitions of this answer are dealing in +Note that all the command definitions above are dealing in <a href="FAQ-atsigns.html">LaTeX internal commands</a>, so the above code should be in a package file, for preference. <p/>The <i>Koma-script</i> classes have different commands for specifying changes to section number presentation: <code>\</code><code>partformat</code>, <code>\</code><code>chapterformat</code> and <code>\</code><code>othersectionlevelsformat</code>, but otherwise -their facilities are similar to those of “raw” LaTeX. +their facilities are similar to those of “raw” LaTeX. <dl> <dt><tt><i>KOMA script bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html index 832c5b11044..e35c5b40191 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secindent.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label secindent</title> </head><body> <h3>Indent after section headings</h3> -<p/>LaTeX implements a style that doesn’t indent the first paragraph +<p/>LaTeX implements a style that doesn’t indent the first paragraph after a section heading. There are coherent reasons for this, but not everyone likes it. The <i>indentfirst</i> package suppresses the mechanism, so that the first paragraph is indented. <dl> -<dt><tt><i>indentfirst.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>indentfirst.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/indentfirst.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html index 24aa9ca02ca..b3c2924e5ad 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secnumdep.html @@ -16,7 +16,7 @@ by the way the <code>\</code><code>chapter</code> command uses the counter <code </ol> Other sectioning commands are similar, but with other values used in the test. -<p/>So a simple way to get headings of funny ‘sections’ such as prefaces +<p/>So a simple way to get headings of funny ‘sections’ such as prefaces in the table of contents is to use the counter: <blockquote> <pre> @@ -25,7 +25,7 @@ in the table of contents is to use the counter: </pre> </blockquote><p> Unfortunately, you have to set <code>secnumdepth</code> back to its usual -value (which is 2 in the standard styles) before you do any ‘section’ +value (which is 2 in the standard styles) before you do any ‘section’ which you want to be numbered. <p/>Similar settings are made, automatically, in the LaTeX book class by the <code>\</code><code>frontmatter</code> and <code>\</code><code>backmatter</code> commands. @@ -45,7 +45,7 @@ contents itself, the <code>bibliography</code>, <code>index</code>, etc., to the table of contents. <p/>The <i>KOMA-Script</i> classes have commands <code>\</code><code>addchap</code> and <code>\</code><code>addled</code>, which work like <code>\</code><code>chapter</code> and <code>\</code><code>section</code> but -aren’t numbered. The <i>memoir</i> class incorporates the facilities +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. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html index b28b976c4e0..f212c307999 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-secthead.html @@ -4,7 +4,7 @@ <h3>The style of section headings</h3> <p/>Suppose that the editor of your favourite journal has specified that section headings must be centred, in small capitals, and subsection headings ragged -right in italic, but that you don’t want to get involved in the sort of +right in italic, but that you don’t want to get involved in the sort of programming described in section 2.2 of <em>The LaTeX Companion</em> (see <a href="FAQ-books.html">TeX-related books</a>; the @@ -22,21 +22,21 @@ probably satisfy your editor. Define yourself new commands </blockquote><p> and then use <code>\</code><code>ssection</code> and <code>\</code><code>ssubsection</code> in place of -<code>\</code><code>section</code> and <code>\</code><code>subsection</code>. This isn’t perfect: section numbers +<code>\</code><code>section</code> and <code>\</code><code>subsection</code>. This isn’t perfect: section numbers remain in bold, and starred forms need a separate redefinition. <p/>The <i>titlesec</i> package offers a structured approach to the problem, based on redefinition of the sectioning and chapter commands themselves. This approach allows it to offer radical adjustment: its options provide (in effect) a toolbox for designing your own -sectioning commands’ output. +sectioning commands’ output. <p/>The <i>sectsty</i> package provides a more simply structured set of tools; while it is less powerful than is <i>titlesec</i>, it is perhaps preferable for minor adjustments, since you can use it after having read a smaller proportion of the manual. <p/>The <i>fncychap</i> package provides a nice collection of customised chapter heading designs. The <i>anonchap</i> package provides a -simple means of typesetting chapter headings “like section headings” -(i.e., without the “Chapter” part of the heading); the +simple means of typesetting chapter headings “like section headings” +(i.e., without the “Chapter” part of the heading); the <i>tocbibind</i> package provides the same commands, in pursuit of another end. <p/>The <i>memoir</i> class includes facilities that match @@ -44,7 +44,7 @@ another end. chapter heading styles (including an <i>anonchap</i>-equivalent). The <i>KOMA-script</i> classes also have sets of tools that provide equivalent functionality, notably formatting specifications <code>\</code><code>partformat</code>, -<code>\</code><code>chapterformat</code>, <code>\</code><code>sectionformat</code>, …, as well as several +<code>\</code><code>chapterformat</code>, <code>\</code><code>sectionformat</code>, …, as well as several useful overall formatting specifications defined in class options. <p/>Finally, the indefatigable Vincent Zoonekynd supplies examples of how to program alternative @@ -54,7 +54,7 @@ and The web pages provide programming examples, and expect users to adapt them to their own LaTeX use. <dl> -<dt><tt><i>anonchap.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/anonchap.sty">macros/latex/contrib/misc/anonchap.sty</a> +<dt><tt><i>anonchap.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/anonchap.zip">macros/latex/contrib/anonchap</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/anonchap/">browse the directory</a>) <dt><tt><i>fncychap.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fncychap.zip">macros/latex/contrib/fncychap</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fncychap/">browse the directory</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html index a65b44f6bcc..81833835bdc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label semanticnest</title> </head><body> -<h3>Capacity exceeded [semantic nest …]</h3> +<h3>Capacity exceeded [semantic nest …]</h3> <p/> <pre> ! TeX capacity exceeded, sorry [semantic nest size=100]. @@ -12,7 +12,7 @@ you can ask a wizard to enlarge me. Even though TeX suggests (as always) that enlargement by a wizard may help, this message usually results from a broken macro or bad parameters to an otherwise working macro. -<p/>The “semantic nest” TeX talks about is the nesting +<p/>The “semantic nest” TeX talks about is the nesting of boxes within boxes. A stupid macro can provoke the error pretty easily: <blockquote> @@ -28,16 +28,16 @@ The extended traceback <em>does</em> help, though it does rather run on. In the case above, the traceback consists of <pre> -\silly ->\hbox { +\silly ->\hbox { here's \silly being executed} </pre> followed by 100 instances of <pre> -\silly ->\hbox {here's \silly +\silly ->\hbox {here's \silly being executed} </pre> The repeated lines are broken at exactly the offending macro; of -course the loop need not be as simple as this — if <code>\</code><code>silly</code> calls +course the loop need not be as simple as this — if <code>\</code><code>silly</code> calls <code>\</code><code>dopy</code> which boxes <code>\</code><code>silly</code>, the effect is just the same and alternate lines in the traceback are broken at alternate positions. <p/>There are in fact two items being consumed when you nest boxes: the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html index 9642174d267..8829c170647 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html @@ -3,7 +3,7 @@ </head><body> <h3>Typesetting URLs</h3> <p/>URLs tend to be very long, and contain characters that would -naturally prevent them being hyphenated even if they weren’t typically +naturally prevent them being hyphenated even if they weren’t typically set in <code>\</code><code>ttfamily</code>, verbatim. Therefore, without special treatment, they often produce wildly overfull <code>\</code><code>hbox</code>es, and their typeset representation is awful. @@ -15,16 +15,16 @@ representation is awful. specifying a personal list of potential break characters. Its chief disadvantage is fragility in LaTeX moving arguments. The - <a href="FAQ-eplain.html">Eplain macros</a> — define a similar <code>\</code><code>path</code> command. + <a href="FAQ-eplain.html">Eplain macros</a> — define a similar <code>\</code><code>path</code> command. <p/> <i>Path</i>, though it works in simple situations, makes no attempt to work with LaTeX (it is irremediably fragile). Despite its long and honourable history, it is no longer recommended for LaTeX use. <li> The <i>url</i> package, which defines an <code>\</code><code>url</code> command (among others, including its own <code>\</code><code>path</code> command). The command - gives each potential break character a maths-mode ‘personality’, and - then sets the URL itself (in the user’s choice of font) in - maths mode. It can produce (LaTeX-style) ‘robust’ commands + gives each potential break character a maths-mode ‘personality’, and + then sets the URL itself (in the user’s choice of font) in + maths mode. It can produce (LaTeX-style) ‘robust’ commands (see <a href="FAQ-protect.html">use of <code>\</code><code>protect</code></a>) for use within moving arguments. @@ -36,7 +36,7 @@ representation is awful. <code>spaces</code> to allow breaks at spaces (note, this requires <code>obeyspaces</code> as well, and <code>hyphens</code> to allow breaks after hyphens. (Note that the package <em>never</em> does - “ordinary” hyphenation of names inside an URL.) + “ordinary” hyphenation of names inside an URL.) <p/> It is possible to use the <i>url</i> package in Plain TeX, with the assistance of the <i>miniltx</i> package (which was originally developed for using the LaTeX graphics package in @@ -55,8 +55,8 @@ representation is awful. <p/>The author of this answer prefers the (rather newer) <i>url</i> package (directly or indirectly); both <i>path</i> and <i>url</i> work well with Plain TeX (though of course, the fancy -LaTeX facilities of <i>url</i> don’t have much place there). -(<i>hyperref</i> isn’t available in a version for use with Plain TeX.) +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.) <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 @@ -71,7 +71,7 @@ after which, <code>\</code><code>faqhome</code> is robust. is in the package files. <dl> <dt><tt><i>hyperref.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse the directory</a>) -<dt><tt><i>miniltx.tex</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse the directory</a>) +<dt><tt><i>miniltx.tex</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/miniltx.html">catalogue entry</a> <dt><tt><i>path.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/path.sty">macros/latex/contrib/misc/path.sty</a> <dt><tt><i>url.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/url.zip">macros/latex/contrib/url</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/url/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html index aa5338acbec..f65dd539d67 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html @@ -23,7 +23,7 @@ x y ----------------- </pre> </blockquote><p> -However, this doesn’t satisfy everyone: many want the labelling in a +However, this doesn’t satisfy everyone: many want the labelling in a single cell at the top left of the table. It sounds a simple enough requirement, yet it calls for some slightly tricky LaTeX coding. The <i>slashbox</i> package does the job for you: it defines @@ -31,9 +31,9 @@ commands <code>\</code><code>slashbox</code> and <code>\</code><code>backslashbo labels as arguments. It draws a picture with the two labels on either side of a slanting line; the command (and hence the picture) may be placed in the corner cell, where the labelled row and column meet. -<p/>The package isn’t the world’s neatest: it uses LaTeX +<p/>The package isn’t the world’s neatest: it uses LaTeX <code>picture</code> mode to draw its line, and picture mode has many -tedious restrictions (and doesn’t, in all honesty, produce +tedious restrictions (and doesn’t, in all honesty, produce particularly good pictures). Load slashbox with the <i>pict2e</i> package, and at least the picture quality will be improved. <p/>Documentation of <i>slashbox</i> is less than satisfactory: a @@ -41,9 +41,9 @@ LaTeX source file of rather startling starkness accompanies the package file in the distribution. It does, however, process to a DVI file that gives some idea of how the <code>\</code><code>slashbox</code> may be expected to look. (The third example in the file shows the effect of -<code>picture</code> mode’s restrictions: the dividing line doesn’t +<code>picture</code> mode’s restrictions: the dividing line doesn’t go from corner to corner in the box: to correct this requires revision -of <i>slashbox</i> — <i>pict2e</i> alone doesn’t help in this +of <i>slashbox</i> — <i>pict2e</i> alone doesn’t help in this regard.) <dl> <dt><tt><i>slashbox.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/slashbox.zip">macros/latex/contrib/slashbox</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/slashbox/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html index ce5bf0b9aa8..fe04ca18a8a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slidecls.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label slidecls</title> </head><body> <h3>Producing slides</h3> -<p/>Lamport’s original LaTeX had a separate program (SliTeX) for +<p/>Lamport’s original LaTeX had a separate program (SliTeX) for producing slides; it dates from the age when colour effects were produced by printing separate slides in different-coloured inks, and overlaying them, and was just about acceptable back then. When @@ -10,22 +10,22 @@ LaTeX2e came along, the reason SliTeX had to be a separate program went away, and its functionality was supplied by the <i>slides</i> class. While this makes life a little easier for system administrators, it does nothing for the inferior functionality -of the class: no-one “who knows” uses <i>slides</i> nowadays. -<p/>The ‘classic’ alternatives have been <i>seminar</i> and <i>foils</i> +of the class: no-one “who knows” uses <i>slides</i> nowadays. +<p/>The ‘classic’ alternatives have been <i>seminar</i> and <i>foils</i> (originally known as FoilTeX). Both were originally designed to produce output on acetate foils, though subsequent work has provided environments in which they can be used with screen projectors (see below). <p/>The advent of Microsoft <i>PowerPoint</i> (feeble though early -versions of it were) has created a demand for “dynamic” slides — +versions of it were) has created a demand for “dynamic” slides — images that develop their content in a more elaborate fashion than by merely replacing one foil with the next in the way that was the norm when <i>slides</i>, <i>foils</i> and <i>seminar</i> were designed. <p/>The <i>prosper</i> class builds on <i>seminar</i> to provide dynamic effects and the like; it retains the ability to provide PDF for a projected presentation, or to print foils for a foil-based -presentation. The add-on package <i>ppr-prv</i> adds “preview” -facilities (that which is commonly called “hand-out printing”). The +presentation. The add-on package <i>ppr-prv</i> adds “preview” +facilities (that which is commonly called “hand-out printing”). The <i>HA-prosper</i> package, which you load with <i>prosper</i>, mends a few bugs, and adds several facilities and slide design styles. The (relatively new) <i>powerdot</i> class is designed as a @@ -35,12 +35,12 @@ by the author of <i>HA-prosper</i>. (as its name implies) was designed for use with projection displays. It needs the <i>pgf</i> package (for graphics support), which in turn requires <i>xcolor</i>; while this adds to the tedium of -installing <i>beamer</i> “from scratch”, both are good additions to +installing <i>beamer</i> “from scratch”, both are good additions to a modern LaTeX installation. <i>Beamer</i> has reasonable facilities for producing printed copies of slides. <p/><i>Talk</i> is another highly functional, yet easy-to-learn class which claims to differ from the systems mentioned above, such as -<i>beamer</i>, in that it doesn’t impose a slide style on you. You +<i>beamer</i>, in that it doesn’t impose a slide style on you. You get to specify a bunch of slide styles, and you can switch from one to the other between slides, as you need. (The class itself provides just the one style, in the package <i>greybars</i>: the author @@ -48,22 +48,22 @@ hopes users will contribute their own styles, based on <i>greybars</i>.) <p/><i>Ppower4</i> (commonly known as <i>pp4</i>) is a <i>Java</i>-based support program that will postprocess -PDF, to ‘animate’ the file at places you’ve marked with -commands from one of the <i>pp4</i> packages. The commands don’t +PDF, to ‘animate’ the file at places you’ve marked with +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 packages that -permit dynamic effects in documents formatted in “more modest” +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. +“presentation effects” into an <i>article</i>-class document. <p/> <p/>A more detailed examination of the alternatives (including examples -of code using many of them) may be found at Michael Wiedmann’s fine +of code using many of them) may be found at Michael Wiedmann’s fine <a href="http://www.miwie.org/presentations/presentations.html">http://www.miwie.org/presentations/presentations.html</a> <p/>ConTeXt users will find that much (if not all) of what they need is -already in ConTeXt itself; there’s a useful summary of what’s +already in ConTeXt itself; there’s a useful summary of what’s available, with examples, in <a href="http://wiki.contextgarden.net/Presentation_Styles">http://wiki.contextgarden.net/Presentation_Styles</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html index f39dca0af3d..d89f3c5681b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-sortbib.html @@ -12,7 +12,7 @@ the short term). their citations need to be sorted. A common misapprehension is to insert <code>\</code><code>bibliographystyle{alpha}</code> (or similar) and expect the typeset output to be sorted in some magical way. BibTeX -doesn’t work that way! — if you write <code>thebibliography</code>, +doesn’t work that way! — if you write <code>thebibliography</code>, you get to sort its contents. BibTeX will only sort the contents of a <code>thebibliography</code> environment when it creates it, to be inserted from a <code>.bbl</code> file by a <code>\</code><code>bibliography</code> command. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html index 1a0a22b76db..5edee87aca9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spaftend.html @@ -1,16 +1,16 @@ <head> <title>UK TeX FAQ -- question label spaftend</title> </head><body> -<h3>There’s a space added after my environment</h3> -<p/>You’ve written your own environment <code>env</code>, and it works +<h3>There’s a space added after my environment</h3> +<p/>You’ve written your own environment <code>env</code>, and it works except that a space appears at the start of the first line of typeset -text after <code>\</code><code>end{env}</code>. This doesn’t happen with similar +text after <code>\</code><code>end{env}</code>. This doesn’t happen with similar LaTeX-supplied environments. <p/>You could impose the restriction that your users always put a -“<code>%</code>” sign after the environment … but -LaTeX environments don’t require that, either. -<p/>The LaTeX environments’ “secret” is an internal flag which causes -the unwanted spaces to be ignored. Fortunately, you don’t have to use +“<code>%</code>” sign after the environment … but +LaTeX environments don’t require that, either. +<p/>The LaTeX environments’ “secret” is an internal flag which causes +the unwanted spaces to be ignored. Fortunately, you don’t have to use the internal form: since 1996, LaTeX has had a user command <code>\</code><code>ignorespacesafterend</code>, which sets the internal flag. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html index ba5548373a9..f595a58149c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-specials.html @@ -13,7 +13,7 @@ to expand their arguments and then pass the command to the DVI file. In most cases, there are macro packages provided (often with the driver) that provide a human-friendly interface to the <code>\</code><code>special</code>; for example, -there’s little point including a figure if you leave no gap for it in +there’s little point including a figure if you leave no gap for it in your text, and changing colour proves to be a particularly fraught operation that requires real wizardry. LaTeX2e has standard graphics and colour packages that make figure inclusion, @@ -22,7 +22,7 @@ straightforward, despite the rather daunting <code>\</code><code>special</code> involved. (ConTeXt provides similar support, though not by way of packages.) <p/>The allowable arguments of <code>\</code><code>special</code> depend on the device driver -you’re using. Apart from the examples above, there are <code>\</code><code>special</code> +you’re using. Apart from the examples above, there are <code>\</code><code>special</code> commands in the emTeX drivers (e.g., <i>dvihplj</i>, <i>dviscr</i>, <em>etc</em>.) that will draw lines at arbitrary orientations, and commands in <i>dvitoln03</i> that permit the page to be set in diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html index 5fc4497eb6e..0d004a6fcf9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spell.html @@ -23,7 +23,7 @@ version of <i>ispell</i>. <dl> <dt><tt><i>4spell</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/4spell.zip">support/4spell</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/4spell/">browse the directory</a>) <dt><tt><i>amspell</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/amspell.zip">support/amspell</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/amspell/">browse the directory</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 +<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. <dt><tt><i>excalibur</i></tt><dd><a href="http://www.tex.ac.uk/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="http://www.tex.ac.uk/tex-archive/support/ispell/ispell-3.2.06.tar.gz">support/ispell/ispell-3.2.06.tar.gz</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html index 9dc949a38a4..56cf213ae15 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spinmacro.html @@ -2,29 +2,29 @@ <title>UK TeX FAQ -- question label spinmacro</title> </head><body> <h3>Spaces in macros</h3> -<p/>It’s very easy to write macros that produce space in the typeset -output where it’s neither desired nor expected. Spaces introduced by -macros are particularly insidious because they don’t amalgamate with +<p/>It’s very easy to write macros that produce space in the typeset +output where it’s neither desired nor expected. Spaces introduced by +macros are particularly insidious because they don’t amalgamate with spaces around the macro (unlike consecutive spaces that you type), so your output can have a single bloated space that proves -to be made up of two or even more spaces that haven’t amalgamated. +to be made up of two or even more spaces that haven’t amalgamated. And of course, your output can also have a space where none was wanted at all. <p/>Spaces are produced, inside a macro as elsewhere, by space or tab characters, or by end-of-line characters. There are two basic rules to remember when writing a macro: first, the rules for ignoring spaces -when you’re typing macros are just the same as the rules that apply -when you’re typing ordinary text, and second, rules for ignoring +when you’re typing macros are just the same as the rules that apply +when you’re typing ordinary text, and second, rules for ignoring spaces do <em>not</em> apply to spaces produced while a macro is being -obeyed (“expanded”). +obeyed (“expanded”). <p/>Spaces are ignored in vertical mode (between paragraphs), at the beginning of a line, and after a command name. Since sequences of -spaces are collapsed into one, it ‘feels as if’ spaces are ignored if +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., <em>count</em> and <em>dimen</em> variable assignments in Plain TeX) and after certain control words (e.g., in <code>\</code><code>hbox</code> <code>to</code>, so again we have instances -where it ‘feels as if’ spaces are being ignored when they’re merely +where it ‘feels as if’ spaces are being ignored when they’re merely working quietly for their living. <p/>Consider the following macro, fairly faithfully adapted from one that appeared on <i>comp.text.tex</i>: @@ -37,8 +37,8 @@ appeared on <i>comp.text.tex</i>: The macro definition contains five spaces: <ul> <li> after the opening <code>{</code> of the macro body; this space will be - ignored, not because “because the macro appears at the start of a - line”, but rather because the macro was designed to operate between + ignored, not because “because the macro appears at the start of a + line”, but rather because the macro was designed to operate between paragraphs <li> after <code>\</code><code>bigskip</code>; this space will be ignored (while the macro is being defined) because it follows a command name @@ -53,7 +53,7 @@ The macro definition contains five spaces: </ul> The original author of the macro had been concerned that the starts of his lines with this macro in them were not at the left margin, and -that the text appearing after the macro wasn’t always properly +that the text appearing after the macro wasn’t always properly aligned. These problems arose from the space at the start of the mandatory argument of <code>\</code><code>makebox</code> and the space immediately after the same argument. He had written his macro in that way to emphasise the @@ -80,27 +80,27 @@ emphasising the structure): </blockquote><p> Care has been taken to ensure that every space in the revised definition is ignored, so none appears in the output. The revised -definition takes the “belt and braces” approach, explicitly dealing +definition takes the “belt and braces” approach, explicitly dealing with every line ending (although, as noted above, a space introduced at the end of the first line of the macro would have been ignored in -actual use of the macro. This is the best technique, in fact — it’s +actual use of the macro. This is the best technique, in fact — it’s easier to blindly suppress spaces than to analyse at every point whether you actually need to. Three techniques were used to suppress spaces: <ul> <li> placing a <code>%</code> character at the end of a line (as in the 1st, 3rd and 5th lines), -<li> ending a line ‘naturally’ with a control sequence, as in line 2, +<li> ending a line ‘naturally’ with a control sequence, as in line 2, and -<li> ending a line with an ‘artificial’ control sequence, as in line +<li> ending a line with an ‘artificial’ control sequence, as in line 4; the control sequence in this case (<code>\</code><code>relax</code>) is a no-op in many - circumstances (as here), but this usage is deprecated — a + circumstances (as here), but this usage is deprecated — a <code>%</code> character would have been better. </ul> Beware of the (common) temptation to place a space <em>before</em> a <code>%</code> character: if you do this you might as well omit the <code>%</code> altogether. -<p/>In “real life”, of course, the spaces that appear in macros are far +<p/>In “real life”, of course, the spaces that appear in macros are far more cryptic than those in the example above. The most common spaces arise from unprotected line ends, and this is an error that occasionally appears even in macros written by the most accomplished diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html index 21ee50b5aee..eb084c09c50 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-splitfoot.html @@ -9,12 +9,12 @@ could try to salvage this problem by making the page short of both the footnote and the line with the footnote mark, but its priorities told it that splitting the footnote would be preferable. <p/>As always, the best solution is to change your text so that the -problem doesn’t occur in the first place. Consider whether the text +problem doesn’t occur in the first place. Consider whether the text that bears the footnote could move earlier in the current page, or on to the next page. -<p/>If this isn’t possible, you might want to change LaTeX’s perception -of its priorities: they’re controlled by -<code>\</code><code>interfootnotelinepenalty</code> — the larger it is, the less willing +<p/>If this isn’t possible, you might want to change LaTeX’s perception +of its priorities: they’re controlled by +<code>\</code><code>interfootnotelinepenalty</code> — the larger it is, the less willing LaTeX is to split footnotes. <p/>Setting <blockquote> @@ -22,8 +22,8 @@ LaTeX is to split footnotes. \interfootnotelinepenalty=10000 </pre> </blockquote><p> -inhibits split footnotes altogether, which will cause ‘<code>Underfull</code> -<code>\</code><code>vbox</code>’ messages unless you also specify <code>\</code><code>raggedbottom</code>. The +inhibits split footnotes altogether, which will cause ‘<code>Underfull</code> +<code>\</code><code>vbox</code>’ messages unless you also specify <code>\</code><code>raggedbottom</code>. The default value of the penalty is <code>100</code>, which is rather mild. <p/>An alternative technique is to juggle with the actual size of the pages. <code>\</code><code>enlargethispage</code> changes the size of the current page by diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html index 989e10562b7..bbbc16d69c2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-srchpdf.html @@ -4,18 +4,18 @@ <h3>Searching PDF files</h3> <p/>In principle, you can search a PDF file: the text of the file is available to the viewer, and at least some viewers provide a search -facility. (It’s not the fastest thing in the world, but it does help +facility. (It’s not the fastest thing in the world, but it does help in some circumstances.) <p/>However, there is a problem: the viewer wants to look at Unicode text, but no ordinary TeX-based system deals in Unicode text. Fortunately for us Anglophones, this is is hardly ever a problem for -our text, since even Knuth’s “OT1” encoding matches ASCII (and hence +our text, since even Knuth’s “OT1” encoding matches ASCII (and hence the lowest 128 characters of Unicode) for most things printable. However, using the inflected characters of Continental European -languages, or anything that doesn’t use a Latin alphabet, there is -potential for problems, since TeX’s view of what a font is doesn’t -map PDF’s and the reader won’t understand… -<p/>… Unless you use the <i>cmap</i> package with PDFLaTeX, +languages, or anything that doesn’t use a Latin alphabet, there is +potential for problems, since TeX’s view of what a font is doesn’t +map PDF’s and the reader won’t understand… +<p/>… Unless you use the <i>cmap</i> package with PDFLaTeX, that is. The package will instruct PDFTeX to load character maps into your PDF for output fonts encoded according to the T1 (Western European Languages), T2A, T2B, or T2C (Cyrillic Languages), diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html index 32b5f4037aa..c8456ef08c1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-struttab.html @@ -3,18 +3,18 @@ </head><body> <h3>Spacing lines in tables</h3> <p/>(La)TeX mechanisms for maintaining the space between lines (the -“<em>leading</em>”) rely on TeX’s paragraph builder, which compares +“<em>leading</em>”) rely on TeX’s paragraph builder, which compares the shape of consecutive lines and adjusts the space between them. -<p/>These mechanisms can’t work in exactly the same way when (La)TeX is -building a table, because the paragraph builder doesn’t get to see the +<p/>These mechanisms can’t work in exactly the same way when (La)TeX is +building a table, because the paragraph builder doesn’t get to see the lines themselves. As a result, tables sometimes typeset with lines uncomfortably close together (or occasionally ridiculously far apart). <p/>Traditional (moving metal type) typographers would adjust the spacing -between lines of a table by use of a “<em>strut</em>” (a metal +between lines of a table by use of a “<em>strut</em>” (a metal spacer). A TeX user can do exactly the same thing: most macro packages define a <code>\</code><code>strut</code> command, that defines a space appropriate to the current size of the text; placing a <code>\</code><code>strut</code> command at the -end of a troublesome row is the simplest solution to the problem — +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. <p/>If your table exhibits a systematic problem (i.e., every row is wrong @@ -28,9 +28,9 @@ by the same amount) use <code>\</code><code>extrarowheight</code>, which is defi \begin{tabular}{....} </pre> </blockquote><p> -<p/>To correct a single row whose maladjustment isn’t corrected by a +<p/>To correct a single row whose maladjustment isn’t corrected by a <code>\</code><code>strut</code> command, you can define your own, using -<code>\</code><code>rule{0pt}{length}</code> — which is a near approximation to the +<code>\</code><code>rule{0pt}{length}</code> — which is a near approximation to the command that goes inside a <code>\</code><code>strut</code>. The <i>bigstrut</i> package defines a strut command that you can use for this purpose: <code>\</code><code>bigstrut</code> on its own opens up both above and below the current @@ -38,11 +38,11 @@ line; <code>\</code><code>bigstrut[t]</code> opens up above the line, <code>\</code><code>bigstrut[b]</code> opens up below the line. <p/>General solutions are available, however. The <i>tabls</i> package automatically generates an appropriately-sized strut at the end of -each row. Its disadvantages are that it’s really rather slow in +each row. Its disadvantages are that it’s really rather slow in operation (since it gets in the way of everything within tables) and its (lack of) compatibility with other packages. <p/>The <i>cellspace</i> package does a (possibly inferior) job by -defining a new table/array column type “S”, which you apply to each +defining a new table/array column type “S”, which you apply to each column specification. So, for example, <blockquote> <pre> @@ -60,20 +60,18 @@ promise of not interfering so much with other packages, but this author has heard of no reports from the field. <p/>The <i>booktabs</i> package comes with a thought-provoking essay about how tables should be designed. Since table row-spacing problems -most often appear in collisions with rules, the author’s thesis, +most often appear in collisions with rules, the author’s thesis, that LaTeX users tend too often to rule their tables, is interesting. The package provides rule commands to support the -author’s scheme, but deals with inter-row spacing too. The most +author’s scheme, but deals with inter-row spacing too. The most recent release of <i>booktabs</i> sports compatibility with packages such as <i>longtable</i>. -<p/>Documentation of both <i>bigstrut</i> and <i>tabls</i> may be -found as comments in the package files themselves. <dl> -<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) -<dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse the directory</a>) +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/array.html">catalogue entry</a> +<dt><tt><i>bigstrut.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse the directory</a>) <dt><tt><i>booktabs.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse the directory</a>) <dt><tt><i>cellspace.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cellspace.zip">macros/latex/contrib/cellspace</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cellspace/">browse the directory</a>) -<dt><tt><i>tabls.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/tabls.sty">macros/latex/contrib/misc/tabls.sty</a> +<dt><tt><i>tabls.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabls.zip">macros/latex/contrib/tabls</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabls/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html index 5df1f34f09a..671ff882244 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subsubsub.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label subsubsub</title> </head><body> <h3>How to create a <code>\</code><code>subsubsubsection</code></h3> -<p/>LaTeX’s set of “sections” stops at the level of -<code>\</code><code>subsubsection</code>. This reflects a design decision by Lamport — +<p/>LaTeX’s set of “sections” stops at the level of +<code>\</code><code>subsubsection</code>. This reflects a design decision by Lamport — for, after all, who can reasonably want a section with such huge strings of numbers in front of it? -<p/>In fact, LaTeX standard classes <em>do</em> define “sectioning” -levels lower than <code>\</code><code>subsubsection</code>, but they don’t format them like -sections (they’re not numbered, and the text is run-in after the +<p/>In fact, LaTeX standard classes <em>do</em> define “sectioning” +levels lower than <code>\</code><code>subsubsection</code>, but they don’t format them like +sections (they’re not numbered, and the text is run-in after the heading). These deeply inferior section commands are <code>\</code><code>paragraph</code> and <code>\</code><code>subparagraph</code>; you can (if you <em>must</em>) arrange that these two commands produce numbered headings, so that you can use them as <code>\</code><code>subsubsubsection</code>s and lower. <p/>The <i>titlesec</i> allows you to adjust the definitions of the sectioning macros, and it may be used to -transform a <code>\</code><code>paragraph</code>’s typesetting so that it looks like that +transform a <code>\</code><code>paragraph</code>’s typesetting so that it looks like that of a <code>\</code><code>section</code>. -<p/>If you want to program the change yourself, you’ll find that the +<p/>If you want to program the change yourself, you’ll find that the commands (<code>\</code><code>section</code> all the way down to <code>\</code><code>subparagraph</code>) are defined in terms of the internal <code>\</code><code>@startsection</code> command, which takes 6 arguments. Before attempting this sort of work, you are well diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html index 6becedead22..af620d507b3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-subverttoks.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label subverttoks</title> </head><body> <h3>Subverting a token register</h3> -<p/>A common requirement is to “subvert” a token register that other +<p/>A common requirement is to “subvert” a token register that other macros may use. The requirement arises when you want to add something to a system token register (<code>\</code><code>output</code> or <code>\</code><code>every*</code>), but know that other macros use the token register, too. (A common requirement @@ -17,7 +17,7 @@ allows an independent package to play the exact same game: \mypkg@everypar\expandafter{\the\everypar} \mypkg@@everypar{\mypkgs@ownstuff\the\mypkg@everypar} \def\mypkgs@ownstuff{% - <stuff to do at the start of the token register>% + <stuff to do at the start of the token register>% } \let\everypar\mypkg@everypar </pre> @@ -25,12 +25,12 @@ allows an independent package to play the exact same game: </blockquote><p> As you can see, the package (<i>mypkg</i>) <ul> -<li> creates an alias for the existing “system” <code>\</code><code>everypar</code> +<li> creates an alias for the existing “system” <code>\</code><code>everypar</code> (which is frozen into any surrounding environment, which will carry on using the original); <li> creates a token register to subvert <code>\</code><code>everypar</code> and initialises it with the current contents of <code>\</code><code>everypar</code>; -<li> sets the “old” <code>\</code><code>everypar</code> to execute its own extra code, +<li> sets the “old” <code>\</code><code>everypar</code> to execute its own extra code, as well as the contents of its own token register; <li> defines the macro for the extra code; and <li> points the token <code>\</code><code>everypar</code> at the new token register. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html index b986e1656e7..2326ad46e09 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-symbols.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label symbols</title> </head><body> -<h3>Where can I find the symbol for …</h3> +<h3>Where can I find the symbol for …</h3> <!-- assignment circular integral degrees diagonal dots Fourier transform --> <!-- Laplace greater less complex integer natural real --> <!-- cent euro --> @@ -21,10 +21,10 @@ symbols: <p/>A useful new <a href="http://detexify.kirelabs.org/classify.html">symbol search</a> web site is available. It provides you a scratch area on which you draw -the symbol you’re thinking of, with your mouse; when you’ve finished +the symbol you’re thinking of, with your mouse; when you’ve finished drawing, the classifier tries to match your sketch with symbols it knows about. The matching process is pretty good, even for the -sketches of a <em>really</em> poor draughtsman, and it’s often worth +sketches of a <em>really</em> poor draughtsman, and it’s often worth trying more than once. Given the huge size of the symbol list, this tool can be very helpful. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html index e4512fbd8d0..ff58cda2978 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-t1enc.html @@ -4,7 +4,7 @@ <h3>Why use <i>fontenc</i> rather than <i>t1enc</i>?</h3> <p/>In the very earliest days of LaTeX2e, the only way to use the T1 encoding was <i>t1enc</i>; with the summer 1994 -“production” release, the <i>fontenc</i> package appeared, and +“production” release, the <i>fontenc</i> package appeared, and provided comprehensive support for use of the encoding. <p/>Nevertheless, the <i>t1enc</i> package remains (as part of the LaTeX 2.09 compatibility code), but it does very little: it merely @@ -12,14 +12,14 @@ selects font encoding T1, and leaves to the user the business of generating the character codes required. <p/>Generating such character codes could be a simple matter, <em>if</em> the T1 encoding matched any widely-supported encoding standard, -since in that case, one might expect one’s keyboard to generate the +since in that case, one might expect one’s keyboard to generate the character codes. However, the T1 encoding is a mix of several standard encodings, and includes code points in areas of the table which standard encodings specifically exclude, so no T1 keyboards have been (or ever will be) manufactured. <p/>By contrast, the <i>fontenc</i> package generates the T1 code points from ordinary LaTeX commands (e.g., it generates the -<code>é</code> character codepoint from the command <code>\’</code><code>e</code>). So, unless you +<code>é</code> character codepoint from the command <code>\’</code><code>e</code>). So, unless you have program-generated T1 input, use <code>\</code><code>usepackage[T1]{fontenc}</code> rather than <code>\</code><code>usepackage{t1enc}</code>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html index 5af40c48aea..6fa7488004b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabacc.html @@ -3,14 +3,14 @@ </head><body> <h3>Accents misbehave in <code>tabbing</code></h3> <p/>So you are constructing a <code>tabbing</code> environment, and you -have the need of some diacriticised text — perhaps something as simple -as <code>\</code><code>’{e}</code> — and the accent disappears because it has been +have the need of some diacriticised text — perhaps something as simple +as <code>\</code><code>’{e}</code> — and the accent disappears because it has been interpreted as a <code>tabbing</code> command, and everything goes wrong. <p/>This is really a rather ghastly feature of the <code>tabbing</code> environment; in order to type accented characters you need to use the -<code>\</code><code>a</code> kludge: so <code>\</code><code>a’{e}</code> inside <code>tabbing</code> for -<code>\</code><code>’{e}</code> outside, and similarly <code>\</code><code>a‘</code> for <code>\</code><code>‘</code> and <code>\</code><code>a=</code> +<code>\</code><code>a</code> kludge: so <code>\</code><code>a’{e}</code> inside <code>tabbing</code> for +<code>\</code><code>’{e}</code> outside, and similarly <code>\</code><code>a‘</code> for <code>\</code><code>‘</code> and <code>\</code><code>a=</code> for <code>\</code><code>=</code>. This whole procedure is of course hideous and error-prone. <p/>The simplest alternative is to type in an encoding that has the @@ -22,27 +22,27 @@ type: <code>...</code><br> <code>\</code><code>begin{tabbing}</code><br> <code>...</code><br> - <code>...</code> <code>\</code><code>></code> <code>voilà</code> <code>\</code><code>></code> <code>...</code> + <code>...</code> <code>\</code><code>></code> <code>voilà</code> <code>\</code><code>></code> <code>...</code> </blockquote><p> for: <blockquote> - …\quad voilà\quad … + …\quad voilà\quad … </blockquote><p> and the internal mechanisms of the <i>inputenc</i> package will put the right version of the accent command in there. <p/>A witty reversal of the r\^oles is introduced by the package -<i>Tabbing</i> (note the capital “T”): it provides a +<i>Tabbing</i> (note the capital “T”): it provides a <code>Tabbing</code> environment which duplicates <code>tabbing</code>, but all the single-character commands become -complicated objects. So <code>tabbing</code>’s <code>\</code><code>></code> becomes -<code>\</code><code>TAB></code>, <code>\</code><code>=</code> becomes <code>\</code><code>TAB=</code>, and so on. The above trivial +complicated objects. So <code>tabbing</code>’s <code>\</code><code>></code> becomes +<code>\</code><code>TAB></code>, <code>\</code><code>=</code> becomes <code>\</code><code>TAB=</code>, and so on. The above trivial example would therefore become: <blockquote> <pre> \usepackage{Tabbing} ... \begin{Tabbing} - ... ... \TAB> voil\`a \TAB> ... + ... ... \TAB> voil\`a \TAB> ... </pre> </blockquote><p> <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html index 8aca9116776..19cac75890e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tabcellalign.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label tabcellalign</title> </head><body> <h3>How to alter the alignment of tabular cells</h3> -<p/>One often needs to alter the alignment of a tabular <code>p</code> (‘paragraph’) +<p/>One often needs to alter the alignment of a tabular <code>p</code> (‘paragraph’) cell, but problems at the end of a table row are common. With a <code>p</code> cell that looks like: <blockquote> @@ -10,41 +10,42 @@ cell, but problems at the end of a table row are common. With a ... & \centering blah ... \\ </pre> </blockquote><p> -one is liable to encounter errors that complain about a “misplaced -<code>\</code><code>noalign</code>” or “<a href="FAQ-altabcr.html">extra alignment tab</a>”, or the like. +one is liable to encounter errors that complain about a “misplaced +<code>\</code><code>noalign</code>” or “<a href="FAQ-altabcr.html">extra alignment tab</a>”, or the like. The problem is that the command <code>\\</code> means different things in different circumstances: the <code>tabular</code> environment switches the meaning to a value for use in the table, and <code>\</code><code>centering</code>, <code>\</code><code>raggedright</code> and <code>\</code><code>raggedleft</code> all change the meaning to something incompatible. Note that the problem only arises in the last cell of a row: since each cell is set into a box, -its settings are lost at the <code>&</code> (or <code>\\</code>) that +its settings are lost at the <code>&</code> (or <code>\\</code>) that terminates it. -<p/><p/>The technique using <code>\</code><code>PBS</code> was developed in the days of LaTeX 2.09 -because the actual value of <code>\\</code> that the <code>tabular</code> -environment uses was only available as an internal command. Nowadays, -the value is a public command, and you can in principle use it -explicitly: +<p/>In the old days, the actual value of <code>\\</code> that the +<code>tabular</code> environment uses was only available as an +internal command. Nowadays, the value is a public command, and you +can in principle use it explicitly: <blockquote> <pre> ... & \centering blah ... \tabularnewline </pre> </blockquote><p> +(but that’s a rather verbose way of doing things). <p/>The <i>array</i> package provides a command <code>\</code><code>arraybackslash</code> which restores <code>\\</code> to its correct (within table) meaning; -the command may be used in <i>array</i>’s “field format” preamble +the command may be used in <i>array</i>’s “field format” preamble specifications: <blockquote> <pre> -\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} +\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} ... </pre> </blockquote><p> <p/>The <code>\</code><code>tabularnewline</code> and <code>\</code><code>arraybackslash</code> commands are (somewhat) modern additions to LaTeX and the <i>array</i> -package, respectively. If neither is available, the user may try the -(old) solution which preserves the meaning of <code>\\</code>: +package, respectively. In the unlikely event that neither is +available, the user may try the (old) solution which preserves the +meaning of <code>\\</code>: <blockquote> <pre> \newcommand\PBS[1]{\let\temp=\\% @@ -62,11 +63,11 @@ which one uses within a table as: or in the preamble as: <blockquote> <pre> -\begin{tabular}{...>{\PBS\centering}p{5cm}} +\begin{tabular}{...>{\PBS\centering}p{5cm}} </pre> </blockquote><p> <dl> -<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/array.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html index 20301b28e5f..1ec0d2f3985 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds-zip.html @@ -3,10 +3,10 @@ </head><body> <h3>Ready-built 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, +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, +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 @@ -19,6 +19,6 @@ 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/>Use of the files is discussed in -“<a href="FAQ-inst-tds-zip.html">installing using ready-built ZIP files</a>”. +“<a href="FAQ-inst-tds-zip.html">installing using ready-built 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-dist/doc/generic/FAQ-en/html/FAQ-tds.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html index efb86a77d5b..ef4e16b20c9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tds.html @@ -5,18 +5,18 @@ <p/> TDS stands for the TeX Directory Structure, which is a standard way of organising all the TeX-related files on a computer system. <p/> Most modern distributions conform to the TDS, which -provides for both a ‘distribution’ and a (set of) ‘local’ directory +provides for both a ‘distribution’ and a (set of) ‘local’ directory trees containing TeX-related files. The TDS reserves the name <code>texmf</code> as the name of the root directory (folder) of the -hierarchies, and most distributions use that name for their ‘own’ +hierarchies, and most distributions use that name for their ‘own’ trees. Files supplied as part of the distribution are put into the -distribution’s tree. The location of the distribution’s hierarchy is +distribution’s tree. The location of the distribution’s hierarchy is system dependent, but on a Unix system it might be at <i>/usr/share/texmf</i> or <i>/opt/texmf</i>, or a similar location, but in each case the TeX files will be in the tree starting at the <i>/texmf</i> subdirectory. -<p/>There may be more than one ‘local’ hierarchy in which additional files +<p/>There may be more than one ‘local’ hierarchy in which additional files can be stored. In the extreme an installation can have a local hierarchy and each user can also have an individual local hierarchy. The location of any local hierarchy is not only system dependent but diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html index 486616de040..33dbd40e89f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tempinst.html @@ -1,29 +1,29 @@ <head> <title>UK TeX FAQ -- question label tempinst</title> </head><body> -<h3>“Temporary” installation of (La)TeX files</h3> +<h3>“Temporary” installation of (La)TeX files</h3> <p/>Operating systems and applications need to know where to find files: -many files that they need are “just named” — the user doesn’t +many files that they need are “just named” — the user doesn’t necessarily know <em>where</em> they are, but knows to ask for them. The commonest case, of course, is the commands whose names you type to -a shell (yes, even Windows’ “MSDOS prompt”) are using a shell to read what +a shell (yes, even Windows’ “MSDOS prompt”) are using a shell to read what you type: many of the commands simply involve loading and executing a file, and the <code>PATH</code> variable tells the shell where to find those files. <p/>Modern TeX implementations come with a bunch of search paths built in to them. In most circumstances these paths are adequate, but one sometimes needs to extend them to pick up files in strange places: for example, we may wish to try a new bundle of packages -before <a href="FAQ-installthings.html">installing them ‘properly’</a>. To do +before <a href="FAQ-installthings.html">installing them ‘properly’</a>. To do this, we need to change the relevant path as TeX perceives it. -However, we don’t want to throw away TeX’s built-in path (all of a -sudden, TeX won’t know how to deal with all sorts of things). +However, we don’t want to throw away TeX’s built-in path (all of a +sudden, TeX won’t know how to deal with all sorts of things). <p/>To <em>extend</em> a TeX path, we define an operating system -environment variable in ‘path format’, but leaving a gap which TeX +environment variable in ‘path format’, but leaving a gap which TeX will fill with its built-in value for the path. The commonest case is that we want to place our extension in front of the path, so that our -new things will be chosen in preference, so we leave our ‘gap to be -filled’ at the end of the environment variable. The syntax is simple -(though it depends which shell you’re actually using): so on a +new things will be chosen in preference, so we leave our ‘gap to be +filled’ at the end of the environment variable. The syntax is simple +(though it depends which shell you’re actually using): so on a Unix-like system, using the <i>bash</i> shell, the job might be done like: <pre> @@ -33,22 +33,22 @@ while in a Windows system, within a MSDOS window, it would be: <pre> set TEXINPUTS=C:/temp; </pre> -In either case, we’re asking TeX to load files from the root disc -temporary files directory; in the Unix case, the “empty slot” is -designated by putting the path separator ‘<code>:</code>’ on its own at the end +In either case, we’re asking TeX to load files from the root disc +temporary files directory; in the Unix case, the “empty slot” is +designated by putting the path separator ‘<code>:</code>’ on its own at the end of the line, while in the Windows case, the technique is the same, but -the path separator is ‘<code>;</code>’. +the path separator is ‘<code>;</code>’. <p/>Note that in either sort of system, the change will only affect instances of TeX that are started from the shell where the environment variable was set. If you run TeX from another window, it will use the original input path. To make a change of input path -that will “stick” for all windows, set the environment variable in +that will “stick” for all windows, set the environment variable in your login script or profile (or whatever) in a Unix system and log out and in again, or in <i>autoexec.bat</i> in a Windows system, and reboot the system. <p/>While all of the above has talked about where TeX finds its macro -files, it’s applicable to pretty much any sort of file any -TeX-related program reads — there are lots of these paths, and of +files, it’s applicable to pretty much any sort of file any +TeX-related program reads — there are lots of these paths, and of their corresponding environment variables. In a <i>web2c</i>-based system, the copious annotations in the <i>texmf.cnf</i> system configuration file help you to learn which diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html index 9e14f5dda27..3e4e4fef24d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texinfo.html @@ -12,12 +12,12 @@ convention, Texinfo source file names end with a <code>.texi</code> or <p/>Texinfo is a macro language, somewhat similar to LaTeX, but with slightly less expressive power. Its appearance is of course rather similar to any TeX-based macro language, except that its macros -start with <code>@</code> rather than the <code>\</code> that’s more commonly used in +start with <code>@</code> rather than the <code>\</code> that’s more commonly used in TeX systems. <p/>You can write and format Texinfo files into Info files within GNU <i>emacs</i>, and read them using the <i>emacs</i> Info reader. You can also format Texinfo files into Info files using -<i>makeinfo</i> and read them using <i>info</i>, so you’re not +<i>makeinfo</i> and read them using <i>info</i>, so you’re not dependent on <i>emacs</i>. The distribution includes a <i>Perl</i> script, <i>texi2html</i>, that will convert Texinfo sources into HTML: the language is a far better fit to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texorpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texorpdf.html index 2ff090f1c68..84758f910ae 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texorpdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texorpdf.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label texorpdf</title> </head><body> <h3>Token not allowed in PDFDocEncoded string</h3> -<p/>The package <i>hyperref</i> produces this error when it doesn’t -know how to make something into a “character” that will go into one +<p/>The package <i>hyperref</i> produces this error when it doesn’t +know how to make something into a “character” that will go into one of its PDF entries. For example, the (unlikely) sequence <blockquote> <pre> @@ -21,11 +21,11 @@ provokes the error. <i>Hyperref</i> goes on to tell you: removing `\hfil' on input line ... </pre> </blockquote><p> -It’s not surprising: how would <em>you</em> put the +It’s not surprising: how would <em>you</em> put the typesetting instruction <code>\</code><code>hfil</code> into a PDF bookmark? <p/><i>Hyperref</i> allows you to define an alternative for such things: the command <code>\</code><code>texorpdfstring</code>, which takes two -arguments — the first is what is typeset, the second is what is put +arguments — the first is what is typeset, the second is what is put into the bookmark. For example, what you would probably like in this case is just a single space in the bookmark; if so, the erroneous example above would become: diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html index c700ffe752d..ce453b9edc5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html @@ -3,7 +3,7 @@ </head><body> <h3>Flowing text around figures</h3> <p/>There are several LaTeX packages that purport to do this, but they -all have their limitations because the TeX machine isn’t really +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: <dl> @@ -21,7 +21,7 @@ There is a (more or less similar) <code>floatingtable</code> environment. <p/>The tables or figures can be set left or right, or alternating on even/odd pages in a double-sided document. -<p/>The package works with the <code>multicol</code> package, but doesn’t work well +<p/>The package works with the <code>multicol</code> package, but doesn’t work well in the neighbourhood of list environments (unless you change your LaTeX document). <dt><code>wrapfig</code><dd> <i>wrapfig</i> has syntax: @@ -64,7 +64,7 @@ LaTeX document). a summary in English. </dl> Plain TeX users only have one option: <i>figflow</i> (which -doesn’t work in LaTeX). <i>Figflow</i> only offers flowed +doesn’t work in LaTeX). <i>Figflow</i> only offers flowed figures at the start of the paragraph, but it seems perfectly functional. Syntax is <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html index bbc3749b3e0..b6fa7aa5b66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html @@ -1,11 +1,11 @@ <head> <title>UK TeX FAQ -- question label texthings</title> </head><body> -<h3>Things with “TeX” in the name</h3> -<p/>New TeX users are often baffled by the myriad terms with “TeX” +<h3>Things with “TeX” in the name</h3> +<p/>New TeX users are often baffled by the myriad terms with “TeX” in the name. The goal of this answer is to clarify some of the more common TeX terms. -<p/><p/><b>TeX itself</b> +<p/><p/><b>TeX itself</b>   TeX proper is a typesetting system based on a set of low-level control sequences that instruct TeX how to lay out text on the page. For example, <code>\</code><code>hskip</code> inserts a given amount of horizontal @@ -19,10 +19,10 @@ information on TeX and <a href="FAQ-ref-doc.html">Reference documents</a> for pointers to descriptions of TeX control sequences, data types, and other key parts of TeX. -<p/><p/><b>TeX macro packages (a.k.a. TeX formats)</b> -TeX’s control sequences are tedious to use directly; they are -intended primarily as building blocks for higher-level—and therefore -more user-friendly—abstractions. For example, there is no way in +<p/><p/><b>TeX macro packages (a.k.a. TeX formats)</b>   +TeX’s control sequences are tedious to use directly; they are +intended primarily as building blocks for higher-level—and therefore +more user-friendly—abstractions. For example, there is no way in base TeX to specify that a piece of text should be typeset in a larger font. Instead, one must keep track of the current size and typeface, load a new font with the same typeface but a (specified) @@ -31,12 +31,12 @@ otherwise. Fortunately, because TeX is programmable, it is possible to write a macro that hides this complexity behind a simple, new control sequence. For example, -<code>\</code><code>larger{my text}</code> can be defined to typeset “my text” in +<code>\</code><code>larger{my text}</code> can be defined to typeset “my text” in the next larger font). <p/>While some users write their own, perfectly customized set of -macros—which they then typically reuse across many documents—it is +macros—which they then typically reuse across many documents—it is far more common to rely upon a <em>macro package</em>, a collection of -TeX macros written by experts. For the user’s convenience, these +TeX macros written by experts. For the user’s convenience, these macro packages are often combined with the base TeX engine into a standalone executable. The following are some of that macro packages that you are likely to encounter: @@ -70,19 +70,19 @@ that you are likely to encounter: <a href="FAQ-texinfo.html">What is Texinfo?</a>. <i>makeinfo</i> converts Texinfo documents to HTML, DocBook, Emacs info, XML, and plain text. <i>Tex</i> (or wrappers such as - <i>texi2pdf</i> and <i>texi2pdf</i>) produce one of TeX’s + <i>texi2pdf</i> and <i>texi2pdf</i>) produce one of TeX’s usual output formats such as DVI or PDF. Because <i>tex</i> loads the Plain TeX macros, not the Texinfo ones, a Texinfo document must begin with <code>\</code><code>input{texinfo}</code> to explicitly load the Texinfo macro package. -<p/> <dt>Eplain—Extended Plain TeX (executable: <i>eplain</i>)<dd> +<p/> <dt>Eplain—Extended Plain TeX (executable: <i>eplain</i>)<dd> See <a href="FAQ-eplain.html">What is Eplain?</a>. </dl> -<p/><p/><b>Modified <i>tex</i> executables</b> +<p/><p/><b>Modified <i>tex</i> executables</b>   The original <i>tex</i> executable was produced in the late 1970s (cf. <a href="FAQ-whatTeX.html">What is TeX?</a>) and consequently -lacked some features that users have come to expect from today’s +lacked some features that users have come to expect from today’s software. The following programs address these issues by augmenting the TeX engine with some additional useful features: <p/><dl> @@ -102,7 +102,7 @@ the TeX engine with some additional useful features: the notion that fonts be included with an operating system. Consequently, TeX uses its own font formats, which are incompatible with anything a user is likely to have preinstalled. - XeTeX addresses this issue by enhancing TeX’s <code>\</code><code>font</code> + XeTeX addresses this issue by enhancing TeX’s <code>\</code><code>font</code> control sequence to support all of the fonts made available by the operating system. See <a href="FAQ-xetex.html">What is XeTeX?</a>. @@ -137,8 +137,8 @@ offered with a LaTeX format (as <i>latex</i> or <i>pdflatex</i>) or with a Plain TeX format (as <i>pdftex</i>). (<i>Tex</i> remains with an unadorned TeX executable using Plain TeX, for people such as Knuth himself, who -want the certainty of the “original”.) -<p/><p/><b>TeX distributions</b> +want the certainty of the “original”.) +<p/><p/><b>TeX distributions</b>   A <em>TeX distribution</em> is a collection of TeX-related software. Generally, a TeX distribution includes a set of core TeX executables such as <i>tex</i> and <i>latex</i>; @@ -156,11 +156,11 @@ distributions are free; others require payment. See list of free and shareware TeX distributions and <a href="FAQ-commercial.html">Commercial TeX implementations</a> for a list of commercial TeX distributions. -<p/><p/><b>Summary</b> -If your document begins with <code>\</code><code>documentclass</code>, you’re using some +<p/><p/><b>Summary</b>   +If your document begins with <code>\</code><code>documentclass</code>, you’re using some form of the LaTeX macro package. Even if hidden behind a button in a TeX-aware GUI, this document is getting compiled by a TeX -executable—probably <i>latex</i> or <i>pdflatex</i>—to +executable—probably <i>latex</i> or <i>pdflatex</i>—to produce an output file. The executable came bundled as part of a TeX distribution such as MiKTeX, which includes various other TeX-related components. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html index 1e06ca68cda..17afb4f970a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textrace.html @@ -2,28 +2,28 @@ <title>UK TeX FAQ -- question label textrace</title> </head><body> <h3>Making outline fonts from Metafont</h3> -<p/><i>TeXtrace</i>, originally developed by Péter Szabó, is a -bundle of Unix scripts that use Martin Weber’s freeware boundary +<p/><i>TeXtrace</i>, originally developed by Péter Szabó, is a +bundle of Unix scripts that use Martin Weber’s freeware boundary tracing package <a href="http://autotrace.sourceforge.net"><i>autotrace</a></i> to generate Type 1 outline fonts from Metafont bitmap font outputs. The result is unlikely ever to be of the quality of -the commercially-produced Type 1 font, but there’s always the +the commercially-produced Type 1 font, but there’s always the <a href="http://fontforge.sourceforge.net/"><i>FontForge</a></i> font editor to tidy things. Whatever, there remain fonts which many people find useful and which fail to attract the paid experts, and auto-tracing is providing a useful service here. Notable sets of -fonts generated using <i>TeXtrace</i> are Péter Szabó’s own -EC/TC font set <i>tt2001</i> and Vladimir Volovich’s +fonts generated using <i>TeXtrace</i> are Péter Szabó’s own +EC/TC font set <i>tt2001</i> and Vladimir Volovich’s CM-Super set, which covers the EC, TC, and the Cyrillic LH font sets (for details of both of which sets, see -<a href="FAQ-type1T1.html">“8-bit” type 1 fonts</a>). +<a href="FAQ-type1T1.html">“8-bit” type 1 fonts</a>). <p/>Another system, which arrived slightly later, is <a href="http://www.cs.uu.nl/~hanwen/mftrace/"><i>mftrace</a></i>: this is a small <i>Python</i> program that does the same job. <i>Mftrace</i> may use either <i>autotrace</i> (like -<i>TeXtrace</i>) or Peter Selinger’s +<i>TeXtrace</i>) or Peter Selinger’s <a href="http://potrace.sourceforge.net"><i>potrace</a></i> to produce the initial outlines to process. <i>Mftrace</i> is said to be more flexible, and easier to use, than is <i>TeXtrace</i>, but both systems diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html index 7b48723f228..12b57b6e3f3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tfm.html @@ -7,7 +7,7 @@ information about the sizes of the characters of the font in question, and about ligatures and kerns within that font. One TFM file is needed for each font used by TeX, that is for each design (point) size for each weight for each family; each TFM file serves for all -magnifications of ‘its’ font, so that there are (typically) fewer +magnifications of ‘its’ font, so that there are (typically) fewer TFM files than there are PK files. TeX (LaTeX, etc.) itself needs only to know about the sizes of characters and their interactions with each other, but not what characters look like. By diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html index b7180d7fc5c..8c1e7a00ab9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-the-commands.html @@ -1,13 +1,13 @@ <head> <title>UK TeX FAQ -- question label the-commands</title> </head><body> -<h3>Redefining counters’ <code>\</code><code>the-</code>commands</h3> +<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 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 -<code><em>fred</em></code>” when you’re typesetting. +<code>\</code><code>the</code><code><em>fred</em></code>, which expands to “the value of +<code><em>fred</em></code>” when you’re typesetting. <p/>The definition of <code>\</code><code>the</code><code><em>fred</em></code> should express the value of the counter: it is almost always always a mistake to use the command to produce anything else. The value may reasonably be @@ -25,7 +25,7 @@ the standard techniques for <a href="FAQ-seccntfmt.html">adjusting the presentation of section numbers</a>. <p/>Or, suppose you want the page number to appear at the bottom of each page surrounded by dashes (as in -“<code>-</code><code>-~</code><code>nnn~-</code><code>-</code>”). +“<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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html index 709e96d6dfe..37586286c0b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-theoremfmt.html @@ -5,7 +5,7 @@ <p/>If you want to take advantage of the powerful <code>\</code><code>newtheorem</code> command without the constraint that the contents of the theorem is in a sloped font (for example, you may want to use it to create remarks, examples, proofs, -…) then you can use the AMSLaTeX <i>amsthm</i> package +…) 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 @@ -21,9 +21,9 @@ Alternatively, the following sets up an environment 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="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>) +<dt><tt><i>amsthm.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/amsthm.html">catalogue entry</a> <dt><tt><i>ntheorem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse the directory</a>) -<dt><tt><i>theorem.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>theorem.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/theorem.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html index 28562a9a095..0d131563871 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-thesis.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label thesis</title> </head><body> <h3>Formatting a thesis in LaTeX</h3> -<p/>Thesis styles are usually very specific to your University, so it’s +<p/>Thesis styles are usually very specific to your University, so it’s usually not profitable to ask around for a package outside your own University. Since many Universities (in their eccentric way) still require double-spaced thesis text, you may also need separately to set up <a href="FAQ-linespace.html">double spacing</a>. <p/>If you want to write a new thesis class of your own, a good place to -start is the University of California style, but remember that it’s +start is the University of California style, but remember that it’s often difficult to produce a thesis that both looks good and conforms with the style that your Univeristy demands. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html index 61cb21bb1bd..61524eb1269 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-time.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label time</title> </head><body> <h3>Printing the time</h3> -<p/>TeX has a primitive register that contains “the number of minutes -since midnight”; with this knowledge it’s a moderately simple +<p/>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). -<p/>However, LaTeX provides no primitive for “time”, so the +Plain TeX user would bother with anyone else’s code for). +<p/>However, LaTeX provides no primitive for “time”, so the non-programming LaTeX user needs help. <p/>Two packages are available, both providing ranges of ways of printing the date, as well as of the time: this question will concentrate on @@ -19,7 +19,7 @@ words). <p/>The <i>scrtime</i> package (part of the compendious <i>KOMA-Script</i> bundle) takes a package option (<code>12h</code> or <code>24h</code>) to specify how times are to be printed. The command -<code>\</code><code>thistime</code> then prints the time appropriately (though there’s no +<code>\</code><code>thistime</code> then prints the time appropriately (though there’s no <em>am</em> or <em>pm</em> in <code>12h</code> mode). The <code>\</code><code>thistime</code> command also takes an optional argument, the character to separate the hours and minutes: the default is of course <code>:</code>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html index 9f210684e62..f0a4c829f6a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-titlsty.html @@ -6,7 +6,7 @@ permit manipulation of the appearance of a <code>\</code><code>maketitle</code> command, the <code>\</code><code>thanks</code> commands within it, and so on. The package also defines a <code>titlingpage</code> environment, that offers something in between the -standard classes’ <code>titlepage</code> option and the <code>titlepage</code> +standard classes’ <code>titlepage</code> option and the <code>titlepage</code> environment, and is itself somewhat configurable. <p/>The memoir class includes all the functionality of the <i>titling</i> package, while the <i>KOMA-script</i> classes have diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html index 1fd97bad2ab..e258324901a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label tmupfl</title> </head><body> -<h3>“Too many unprocessed floats”</h3> +<h3>“Too many unprocessed floats”</h3> <p/>If LaTeX responds to a <code>\</code><code>begin{figure}</code> or <code>\</code><code>begin{table}</code> command with the error message <pre> @@ -11,18 +11,18 @@ See the LaTeX manual or LaTeX Companion for explanation. </pre> your figures (or tables) are failing to be placed properly. LaTeX -has a limited amount of storage for ‘floats’ (figures, tables, or -floats you’ve defined yourself with the <i>float</i> package); if -you don’t let it ever actually typeset any floats, it will run out of +has a limited amount of storage for ‘floats’ (figures, tables, or +floats you’ve defined yourself with the <i>float</i> package); if +you don’t let it ever actually typeset any floats, it will run out of space. <p/>This failure usually occurs in extreme cases of -<a href="FAQ-floats.html">floats moving “wrongly”</a>; -LaTeX has found it can’t place a float, and floats of the same type -have piled up behind it. LaTeX’s idea is to ensure that caption +<a href="FAQ-floats.html">floats moving “wrongly”</a>; +LaTeX has found it can’t place a float, and floats of the same type +have piled up behind it. LaTeX’s idea is to ensure that caption numbers are sequential in the document: the caption number is -allocated when the figure (or whatever) is created, and can’t be +allocated when the figure (or whatever) is created, and can’t be changed, so that placement out of order would mean figure numbers appearing out of order in the document (and in the list of figures, or whatever). So a simple failure to place a figure means that no @@ -34,14 +34,14 @@ already referenced. <p/>The error also occurs in a long sequence of <code>figure</code> or <code>table</code> environments, with no intervening -text. Unless the environments will fit “here” (and you’ve allowed -them to go “here”), there will never be a page break, and so there +text. Unless the environments will fit “here” (and you’ve allowed +them to go “here”), there will never be a page break, and so there will never be an opportunity for LaTeX to reconsider placement. -(Of course, the floats can’t all fit “here” if the sequence is -sufficiently prolonged: once the page fills, LaTeX won’t place any +(Of course, the floats can’t all fit “here” if the sequence is +sufficiently prolonged: once the page fills, LaTeX won’t place any more floats, leading to the error. <p/>Techniques for resolution may involve redefining the floats using the -<i>float</i> package’s <code>[H]</code> float qualifier, but you are unlikely +<i>float</i> package’s <code>[H]</code> float qualifier, but you are unlikely to get away without using <code>\</code><code>clearpage</code> from time to time. <dl> <dt><tt><i>float.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html index c38deec3401..6887626a9d2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html @@ -13,16 +13,16 @@ response. Options are: <li> <i>crudetype</i> and <li> <i>catdvi</i>, which is capable of generating Latin-1 (ISO 8859-1) or UTF-8 encoded output. <i>Catdvi</i> was - conceived as a replacement for <i>dvi2tty</i>, but can’t (quite) + conceived as a replacement for <i>dvi2tty</i>, but can’t (quite) be recommended as a complete replacement yet. </ul> A common problem is the hyphenation that TeX inserts when typesetting something: since the output is inevitably viewed using -fonts that don’t match the original, the hyphenation usually looks +fonts that don’t match the original, the hyphenation usually looks silly. <p/>Ralph Droms provides a <i>txt</i> bundle of things in support of ASCII generation, -but it doesn’t do a good job with tables and mathematics. An +but it doesn’t do a good job with tables and mathematics. An alternative is the <i>screen</i> package. <p/>Another possibility is to use the LaTeX-to-ASCII conversion program, <i>l2a</i>, @@ -30,14 +30,14 @@ although this is really more of a de-TeXing program. <p/>The canonical de-TeXing program is <i>detex</i>, which removes all comments and control sequences from its input before writing it to its output. Its original purpose -was to prepare input for a dumb spelling checker, and it’s only usable +was to prepare input for a dumb spelling checker, and it’s only usable for preparing useful ASCII versions of a document in highly restricted circumstances. -<p/><i>Tex2mail</i> is slightly more than a de-TeXer — it’s a +<p/><i>Tex2mail</i> is slightly more than a de-TeXer — it’s a <i>Perl</i> script that converts TeX files into plain text files, expanding various mathematical symbols (sums, products, integrals, sub/superscripts, fractions, square -roots, …) into “ASCII art” that spreads over +roots, …) into “ASCII art” that spreads over multiple lines if necessary. The result is more readable to human beings than the flat-style TeX code. <p/>Another significant possibility is to use one of the diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html index 81ab4ab1bb7..8055bf03dae 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocbibind.html @@ -5,8 +5,8 @@ <p/>The standard LaTeX classes (and many others) use <code>\</code><code>section*</code> or <code>\</code><code>chapter*</code> for auto-generated parts of the document (the tables of contents, lists of figures and tables, the bibliography and the index). As a -result, these items aren’t numbered (which most people don’t mind), -and (more importantly) they don’t appear in the table of contents. +result, these items aren’t numbered (which most people don’t mind), +and (more importantly) they don’t appear in the table of contents. <p/>The correct solution (as always) is to have a class of your own that formats your document according to your requirements. The macro to do the job (<code>\</code><code>addcontentsline</code>) is fairly simple, but there is always @@ -29,7 +29,7 @@ one page long. Instead, one should say: </pre> </blockquote><p> (Note that <code>\</code><code>cleardoublepage</code> does the right thing, even if your -document is single-sided — in that case, it’s a synonym for +document is single-sided — in that case, it’s a synonym for <code>\</code><code>clearpage</code>). Ensuring that the entry refers to the right place is trickier still in a <code>\</code><code>section</code>-based class. <p/>If you are using <i>hyperref</i> (which will link entries in the @@ -44,7 +44,7 @@ adjustment is necessary: </pre> </blockquote><p> The extra command (<code>\</code><code>phantomsection</code>) gives <i>hyperref</i> -something to “hold on to” when making the link. +something to “hold on to” when making the link. <p/>The common solution, therefore, is to use the <i>tocbibind</i> package, which provides many facilities to control the way these entries appear in the table of contents. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html index 82dae3223c6..43d96b94fbd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloft.html @@ -10,7 +10,7 @@ for page numbers, the indentation of the right-hand margin, and the separation of the dots in the dotted leaders, respectively. The series of commands named <code>\</code><code>l@<em>xxx</code></em>, where <code><em>xxx</em></code> is the name of a sectional heading (such as <code>chapter</code> or -<code>section</code>, …) control the layout of the corresponding +<code>section</code>, …) control the layout of the corresponding heading, including the space for section numbers. All these internal commands may be individually redefined to give the effect that you want. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html index 99f465581e9..dce68007e4d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tocloftwrong.html @@ -8,7 +8,7 @@ As a result, they do <em>not</em> react to the sizes of things in them, as they would if a <code>tabular</code> environment (or something similar) was used. <p/>This arrangement can provoke problems, most commonly with deep section -nesting or very large page numbers: the numbers in question just don’t +nesting or very large page numbers: the numbers in question just don’t fit in the space allowed for them in the class. <p/>A separate answer discusses diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html index cd84fa8cb06..d63cc57085f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toodeep.html @@ -1,14 +1,14 @@ <head> <title>UK TeX FAQ -- question label toodeep</title> </head><body> -<h3>“Too deeply nested”</h3> +<h3>“Too deeply nested”</h3> <p/>This error appears when you start a LaTeX list. <p/>LaTeX keeps track of the nesting of one list inside another. There is a set of list formatting parameters built-in for application to each of the list nesting levels; the parameters determine indentation, item separation, and so on. The <code>list</code> environment (the basis for list environments like <code>itemize</code> and -<code>enumerate</code>) “knows” there are only 6 of these sets. +<code>enumerate</code>) “knows” there are only 6 of these sets. <p/>There are also different label definitions for the <code>enumerate</code> and <code>itemize</code> environments at their own private levels of nesting. Consider this example: @@ -43,7 +43,7 @@ In the example, Now, as well as LaTeX <em>knowing</em> that there are 6 sets of parameters for indentation, it also <em>knows</em> that there are only 4 types of labels each, for the environments <code>enumerate</code> -and <code>itemize</code> (this “knowledge” spells out a requirement +and <code>itemize</code> (this “knowledge” spells out a requirement for class writers, since the class supplies the sets of parameters). <p/>From the above, we can deduce that there are several ways we can run out of space: we can have 6 lists (of any sort) nested, and try to @@ -52,7 +52,7 @@ somewhere among the set of nested lists, and try to add another one; and we can have 4 <code>itemize</code> environments somewhere among the set of nested lists, and try to add another one. <p/>What can be done about the problem? Not much, short of rewriting -LaTeX — you really need to rewrite your document in a slightly +LaTeX — you really need to rewrite your document in a slightly less labyrinthine way. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html index 0486039e377..8353fdf56e7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-topgraph.html @@ -4,7 +4,7 @@ <h3>Top-aligning imported graphics</h3> <p/>When TeX sets a line of anything, it ensures that the base-line of each object in the line is at the same level as the base-line of the -final object. (Apart, of course, from <code>\</code><code>raisebox</code> commands…) +final object. (Apart, of course, from <code>\</code><code>raisebox</code> commands…) <p/>Most imported graphics have their base-line set at the bottom of the picture. When using packages such as <i>subfig</i>, one often wants to align figures by their tops. The following odd little bit of @@ -20,7 +20,7 @@ code does this: </pre> </blockquote><p> The <code>\</code><code>vtop</code> primitive sets the base-line of the resulting object to -that of the first “line” in it; the <code>\</code><code>vskip</code> creates the illusion +that of the first “line” in it; the <code>\</code><code>vskip</code> creates the illusion of an empty line, so <code>\</code><code>vtop</code> makes the very top of the box into the base-line. <p/>In cases where the graphics are to be aligned with text, there is a diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html index 954f6abefd8..a065b53099a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tradesyms.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label tradesyms</title> </head><body> <h3>How to get copyright, trademark, etc.</h3> -<p/>The “ -<a href="FAQ-symbols.html">Comprehensive symbol list</a>”, lists +<p/>The “ +<a href="FAQ-symbols.html">Comprehensive symbol list</a>”, lists the symbol commands <code>\</code><code>textcopyright</code>, <code>\</code><code>textregistered</code> and <code>\</code><code>texttrademark</code>, which are available in TS1-encoded fonts, and which are enabled using the <i>textcomp</i> package. <p/>In fact, all three commands are enabled in default LaTeX, but the -glyphs you get aren’t terribly beautiful. In particular, +glyphs you get aren’t terribly beautiful. In particular, <code>\</code><code>textregistered</code> behaves oddly when included in bold text (for example, in a section heading), since it is composed of a small-caps letter, which typically degrades to a regular shape letter when asked to set in a bold font. This means that the glyph becomes a circled -“r”, whereas the proper symbol is a circled “R”. +“r”, whereas the proper symbol is a circled “R”. <p/>This effect is of course avoided by use of <i>textcomp</i>. <p/>Another problem arises if you want <code>\</code><code>textregistered</code> in a superscript position (to look similar to <code>\</code><code>texttrademark</code>). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html index b08faeb6596..c57bf09c5cc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html @@ -1,19 +1,19 @@ <head> <title>UK TeX FAQ -- question label triptrap</title> </head><body> -<h3>How can I be sure it’s really TeX?</h3> +<h3>How can I be sure it’s really TeX?</h3> <p/>TeX (and Metafont and MetaPost) are written in a - <a href="FAQ-lit.html">‘literate’ programming</a> language called Web + <a href="FAQ-lit.html">‘literate’ programming</a> language called Web which is designed to be portable across a wide range of computer systems. How, then, is a new version of TeX checked? <p/>Of course, any sensible software implementor will have his own suite of tests to check that his software runs: those who port TeX and its friends to other platforms do indeed perform such tests. -<p/>Knuth, however, provides a ‘conformance test’ for both TeX +<p/>Knuth, however, provides a ‘conformance test’ for both TeX (<code>trip</code>) and Metafont (<code>trap</code>). -He characterises these as ‘torture tests’: they are designed not to +He characterises these as ‘torture tests’: they are designed not to check the obvious things that ordinary typeset documents, or font designs, will exercise, but rather to explore small alleyways off the main path through the code of TeX. They are, to the casual reader, @@ -21,8 +21,8 @@ pretty incomprehensible! <p/>Once an implementation of TeX has passed its <code>trip</code> test, or an implementation of Metafont has passed its <code>trap</code> test, then it may in principle be distributed as a working version. (In practice, any -distributor would test new versions against “real” documents or -fonts, too; <code>trip</code> and <code>trap</code> don’t actually test 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. <p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html index 7935a331b28..3e5f70664b6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html @@ -2,34 +2,34 @@ <title>UK TeX FAQ -- question label tutbitslatex</title> </head><body> <h3>Specialised (La)TeX tutorials</h3> -<p/>The AMS publishes a “Short Math Guide for LaTeX”, which is +<p/>The AMS publishes a “Short Math Guide for LaTeX”, which is available (in several formats) via -<a href="http://www.ams.org/tex/amslatex.html">http://www.ams.org/tex/amslatex.html</a> (the “Additional -Documentation” about half-way down the page. +<a href="http://www.ams.org/tex/amslatex.html">http://www.ams.org/tex/amslatex.html</a> (the “Additional +Documentation” about half-way down the page. <p/>Herbert Voss has written an extensive guide to mathematics in LaTeX (a German version of which is published as a book). The -guide is part of his “<a href="FAQ-doc-dirs.html">tips and tricks</a>” and +guide is part of his “<a href="FAQ-doc-dirs.html">tips and tricks</a>” and a copy is maintained on CTAN. <p/>Two documents written more than ten years apart about font usage in TeX are worth reading: -<a href="href=’http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf">Essential NFSS</a> +<a href="href=’http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf">Essential NFSS</a> by Sebastian Rahtz, and <a href="http://tug.org/pracjourn/2006-1/schmidt/schmidt.pdf">Font selection in LaTeX</a>, cast in the form of an FAQ, by Walter Schmidt. A general compendium of font information (including the two above) may be found on the <a href="http://www.tug.org/fonts/">TUG web site</a>. -<p/>Peter Smith’s +<p/>Peter Smith’s - “<a href="http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/">LaTeX for Logicians</a>” + “<a href="http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/">LaTeX for Logicians</a>” covers a rather smaller subject area, but is similarly comprehensive (mostly by links to documents on relevant topics, rather than as a monolithic document). -<p/>Keith Reckdahl’s “Using Imported Graphics in LaTeX2e” is an -excellent introduction to graphics use. It’s available on -CTAN, but the sources aren’t available (promised “some time -soon”). +<p/>Keith Reckdahl’s “Using Imported Graphics in LaTeX2e” is an +excellent introduction to graphics use. It’s available on +CTAN, but the sources aren’t available (promised “some time +soon”). <p/>Kjell Magne Fauske offers a set of examples of the use of the drawing packages <a href="FAQ-drawing.html">PGF and TikZ</a>; the @@ -44,30 +44,30 @@ and <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>. In each file, there is a selection of graphics representing an output style, and for each style, the code that produces it is shown. -<p/>An invaluable step-by-step setup guide for establishing a “work -flow” through your (La)TeX system, so that output appears at the +<p/>An invaluable step-by-step setup guide for establishing a “work +flow” through your (La)TeX system, so that output appears at the correct size and position on standard-sized paper, and that the print -quality is satisfactory, is Mike Shell’s <i>testflow</i>. The +quality is satisfactory, is Mike Shell’s <i>testflow</i>. The tutorial consists of a large plain text document, and there is a supporting LaTeX file together with correct output, both in PostScript and -PDF, for each of A4 and “letter” paper sizes. The +PDF, for each of A4 and “letter” paper sizes. The complete kit is available on CTAN (distributed with the -author’s macros for papers submitted for IEEE publications). +author’s macros for papers submitted for IEEE publications). The issues are also covered in a later <a href="FAQ-dvips-pdf.html">FAQ answer</a>. <p/>Documentation of Japanese TeX use appears at least twice on the web: -Haruhiko Okumura’s page on +Haruhiko Okumura’s page on <a href="http://oku.edu.mie-u.ac.jp/~okumura/texfaq/japanese/">typesetting Japanese with Omega</a> (the parent page is in Japanese, so out of the scope of this FAQ). -<p/>One “Tim” documents pTeX (a TeX system widely used in Japan) +<p/>One “Tim” documents pTeX (a TeX system widely used in Japan) in his - “<a href="http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf">English notes on pTeX</a>”. + “<a href="http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf">English notes on pTeX</a>”. <p/>Some university departments make their local documentation available -on the web. Most straightforwardly, there’s the simple translation of +on the web. Most straightforwardly, there’s the simple translation of existing documentation into HTML, for example the INFO documentation of the (La)TeX installation, of which a sample is the LaTeX documentation available at @@ -76,7 +76,7 @@ LaTeX documentation available at documenters who make public record of their (La)TeX support. For example, Tim Love (of Cambridge University Engineering Department) maintains his -deparment’s pages at +deparment’s pages at <a href="http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/">http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/</a> @@ -84,11 +84,9 @@ deparment’s pages at <dl> -<dt><tt><i>Graphics in LaTeX2e</i></tt><dd>the - document is available in PostScript and PDF formats as - <a href="http://www.tex.ac.uk/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a> and <a href="http://www.tex.ac.uk/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a> respectively +<dt><tt><i>Graphics in LaTeX2e</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/epslatex.zip">info/epslatex</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/epslatex/">browse the directory</a>) <dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> -<dt><tt><i>Herbert Voss’s Maths tutorial</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> +<dt><tt><i>Herbert Voss’s Maths tutorial</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html index a40e4a8ec57..e0127c69296 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutorialstar.html @@ -5,11 +5,11 @@ <p/>From a situation where every (La)TeX user <em>had</em> to buy a book if she was not to find herself groping blindly along, we now have what almost amounts to an embarrassment of riches of online documentation. -The following answers attempt to create lists of sources “by topic”. +The following answers attempt to create lists of sources “by topic”. <p/>First we have introductory manuals, for <a href="FAQ-man-tex.html">Plain TeX</a> and <a href="FAQ-man-latex.html">LaTeX</a>. <p/>Next comes a selection of -<a href="FAQ-tutbitslatex.html">“specialised” (La)TeX tutorials</a>, +<a href="FAQ-tutbitslatex.html">“specialised” (La)TeX tutorials</a>, each of which concentrates on a single LaTeX topic. <p/>A couple of reference documents (it would be good to have more) are listed in an <a href="FAQ-ref-doc.html">answer of their own</a>. @@ -19,7 +19,7 @@ listed in an <a href="FAQ-ref-doc.html">answer of their own</a>. <a href="FAQ-typo-style.html">Typography style tutorial</a>. <p/>Finally, we have a set of links to <a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a>, and details -of some “<a href="FAQ-ol-books.html">books</a>” that were once published +of some “<a href="FAQ-ol-books.html">books</a>” that were once published conventionally, but are now available on-line. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html index 9027a346d66..d6846f32db1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-twooptarg.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label twooptarg</title> </head><body> <h3>More than one optional argument</h3> -<p/>If you’ve already read -“<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”. -you can probably guess the “simple” solution to this problem: +<p/>If you’ve already read +“<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”. +you can probably guess the “simple” solution to this problem: command relaying. <p/>LaTeX allows commands with a single optional argument thus: <pre> @@ -30,17 +30,17 @@ technique, as follows: </pre> Of course, <code>\</code><code>BlahRelay</code> may have as many mandatory arguments as are allowed, after allowance for the one taken up with its own -optional argument — that is, 8. +optional argument — that is, 8. <p/>Variants of <code>\</code><code>newcommand</code> (and friends), with names like <code>\</code><code>newcommandtwoopt</code>, are available in the <i>twoopt</i> package. -However, if you can, it’s probably better to learn to write the commands -yourself, just to see why they’re not even a good idea from the +However, if you can, it’s probably better to learn to write the commands +yourself, just to see why they’re not even a good idea from the programming point of view. -<p/>A command with two optional arguments strains the limit of what’s +<p/>A command with two optional arguments strains the limit of what’s sensible: obviously you can extend the technique to provide as many optional arguments as your fevered imagination can summon. However, see the comments on the use of the <i>keyval</i> package, in -“<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”, +“<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”, which offers an alternative way forward. <p/>If you must, however, consider the <i>optparams</i> or <i>xargs</i> packages. <i>Optparams</i> @@ -61,7 +61,7 @@ arguments. Thus defines a command <code>\</code><code>foo</code> that has an optional first argument (default 1), a mandatory second argument, and an optional third argument (default n). -<p/>An alternative approach is offered by Scott Pakin’s +<p/>An alternative approach is offered by Scott Pakin’s <i>newcommand</i> program, which takes a command name and a definition of a set of command arguments (in a fairly readily-understood language), and emits (La)TeX macros which enable @@ -69,8 +69,8 @@ the command to be defined. The command requires that a <i>Python</i> interpreter (etc.) be installed on your computer. <dl> <dt><tt><i>newcommand.py</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/newcommand.zip">support/newcommand</a> (or <a href="http://www.tex.ac.uk/tex-archive/support/newcommand/">browse the directory</a>) -<dt><tt><i>optparams.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse the directory</a>) -<dt><tt><i>twoopt.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) +<dt><tt><i>optparams.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/optparams.html">catalogue entry</a> +<dt><tt><i>twoopt.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/twoopt.html">catalogue entry</a> <dt><tt><i>xargs.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xargs.zip">macros/latex/contrib/xargs</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xargs/">browse the directory</a>) <dt><tt><i>xkeyval.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval.zip">macros/latex/contrib/xkeyval</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html index ab8a79de8c3..4ca714aebd0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-type1T1.html @@ -1,19 +1,19 @@ <head> <title>UK TeX FAQ -- question label type1T1</title> </head><body> -<h3>Finding ‘8-bit’ Type 1 fonts</h3> +<h3>Finding ‘8-bit’ Type 1 fonts</h3> <!-- eight --> <p/>Elsewhere, answers to these FAQs recommend that you use an -‘8-bit’ font to permit +‘8-bit’ font to permit <a href="FAQ-hyphenaccents.html">accentuation of inflected languages</a>, and also recommend the use of Type 1 fonts to ensure that you get <a href="FAQ-fuzzy-type3.html">good quality PDF</a>. These recommendations used to be contradictory: one could not just -“switch” from the free CM fonts to free Cork- (or similarly) +“switch” from the free CM fonts to free Cork- (or similarly) encoded Type 1 fonts. The first approach that started to alleviate these problems, was the development of virtual fonts that make a good approach to the Cork encoding (see below). Now, however, we -have “true” Type 1 fonts available: as always, we have an +have “true” Type 1 fonts available: as always, we have an embarrassment of riches with three free alternatives, and one commercial and one shareware version. <p/><i>CM-super</i> is an @@ -21,12 +21,12 @@ auto-traced set which encompasses all of the T1 and TS1 encodings as well as the T2* series (the family of encodings that cover languages based on Cyrillic alphabets). These fonts are pretty easy to install (the installation instructions are clear), but -they are huge: don’t try to install them if you’re short of disc +they are huge: don’t try to install them if you’re short of disc space. -<p/><i>CM-LGC</i> is a similar “super-font” set, but of much more +<p/><i>CM-LGC</i> is a similar “super-font” set, but of much more modest size; it covers T1, TS1 and T2{A} encodings (as does <i>CM-super</i>, and also covers the LGR -encoding (for typesetting Greek, based on Claudio Beccari’s Metafont +encoding (for typesetting Greek, based on Claudio Beccari’s Metafont sources). <i>CM-LGC</i> manages to be small by going to the opposite extreme from <i>CM-super</i>, which includes fonts at all the sizes supported by the original EC (a huge range); @@ -35,7 +35,7 @@ scaling. There is an inevitable loss of quality inherent in this approach, but for the disc-space-challenged machine, <i>CM-LGC</i> is an obvious choice. <p/><i>Tt2001</i> is a simple scan of the EC and TC -fonts, and has some virtues — it’s noticeably smaller than +fonts, and has some virtues — it’s noticeably smaller than <i>CM-super</i> while being less stark than <i>CM-LGC</i>. <p/><i>Latin</i> <i>Modern</i> is produced using the program <a href="FAQ-textrace.html"><i>MetaType1</i></a>. The @@ -45,26 +45,26 @@ QX encoding); for the glyph set it covers, its outlines seem rather cleaner than those of <i>CM-super</i>. <i>Latin</i> <i>Modern</i> is more modest in its disc space demands than is <i>CM-super</i>, while not being nearly as stark in its range of -design sizes as is <i>CM-LGC</i> — <i>Latin</i> -<i>Modern</i>’s fonts are offered in the same set of sizes as the -original <i>CM</i> fonts. It’s hard to argue with the choice: -Knuth’s range of sizes has stood the test of time, and is one of the +design sizes as is <i>CM-LGC</i> — <i>Latin</i> +<i>Modern</i>’s fonts are offered in the same set of sizes as the +original <i>CM</i> fonts. It’s hard to argue with the choice: +Knuth’s range of sizes has stood the test of time, and is one of the bases on which the excellence of the TeX system rests. <p/><a href="FAQ-virtualfonts.html">Virtual fonts</a> help us deal with the problem, -since they allow us to map “bits of DVI file” to single -characters in the virtual font; so we can create an “é” character +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>’</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 +<i>Acrobat</i> <i>Reader</i>: you can’t use the program’s facilities for searching for text that contains inflected characters, and if you <em>cut</em> text from a window that contains such a -character, you’ll find something unexpected (typically the accent and -the ‘base’ characters separated by a space) when you <i>paste</i> +character, you’ll find something unexpected (typically the accent and +the ‘base’ characters separated by a space) when you <i>paste</i> the result. However, if you can live with this difficulty, virtual fonts are a useful and straightforward solution to the problem. <p/>There are two virtual-font offerings of CM-based 8-bit -fonts — the <i>ae</i> (“almost EC”) and +fonts — the <i>ae</i> (“almost EC”) and <i>zefonts</i> sets; the <i>zefonts</i> set has wider coverage (though the <i>ae</i> set may be extended to offer guillemets by use of the <i>aeguill</i> package). Neither offers characters such @@ -76,7 +76,7 @@ EC fonts (i.e., as bitmaps). Micropress, who offer the complete EC set in Type 1 format, as part of their range of outline versions of fonts that were originally distributed in Metafont format. See -<a href="FAQ-commercial.html">“commercial distributions”</a>. +<a href="FAQ-commercial.html">“commercial distributions”</a>. <p/>The shareware <a href="FAQ-TeXsystems.html">BaKoMa TeX distribution</a> offers a set of Type 1 EC fonts, as an extra shareware option. (As far @@ -86,10 +86,10 @@ seems not to be publicly available.) <p/>Finally, you can use one of the myriad text fonts available in Type 1 format (with appropriate PSNFSS metrics for T1 encoding, or metrics for some other 8-bit encoding such as LY1). However, -if you use someone else’s text font (even something as simple as -Adobe’s Times family) you have to find a matching family of -mathematical fonts, which is a non-trivial undertaking — -see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>. +if you use someone else’s text font (even something as simple as +Adobe’s Times family) you have to find a matching family of +mathematical fonts, which is a non-trivial undertaking — +see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>. <dl> <dt><tt><i>ae fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/ae.zip">fonts/ae</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse the directory</a>) <dt><tt><i>aecompl.sty</i></tt><dd>Distributed with <a href="http://www.tex.ac.uk/tex-archive/fonts/ae.zip">fonts/ae</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html index a898295a03c..68a7c9cdc64 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typebooks.html @@ -6,14 +6,14 @@ Of these, Bringhurst seems to be the one most often recommended. <dl> <dt>The Elements of Typographic Style<dd>by Robert Bringhurst - (Hartley & Marks, 1992, ISBN 0-88179-033-8) -<dt>Finer Points in the Spacing & Arrangement of Type<dd>by Geoffrey Dowding - (Hartley & Marks, 1996, ISBN 0-88179-119-9) -<dt>The Thames & Hudson Manual of Typography<dd>by Ruari McLean - (Thames & Hudson, 1980, ISBN 0-500-68022-1) + (Hartley & Marks, 1992, ISBN 0-88179-033-8) +<dt>Finer Points in the Spacing & Arrangement of Type<dd>by Geoffrey Dowding + (Hartley & Marks, 1996, ISBN 0-88179-119-9) +<dt>The Thames & Hudson Manual of Typography<dd>by Ruari McLean + (Thames & Hudson, 1980, ISBN 0-500-68022-1) <dt>The Form of the Book<dd>by Jan Tschichold (Lund Humphries, 1991, ISBN 0-85331-623-6) -<dt>Type & Layout<dd>by Colin Wheildon +<dt>Type & Layout<dd>by Colin Wheildon (Strathmore Press, 2006, ISBN 1-875750-22-3) <dt>The Design of Books<dd>by Adrian Wilson (Chronicle Books, 1993, ISBN 0-8118-0304-X) @@ -25,7 +25,7 @@ Of these, Bringhurst seems to be the one most often recommended. <p/> There are many catalogues of type specimens but the following books provide a more interesting overall view of types in general and some of their history. <dl> -<dt>Alphabets Old & New<dd>by Lewis F. Day +<dt>Alphabets Old & New<dd>by Lewis F. Day (Senate, 1995, ISBN 1-85958-160-9) <dt>An Introduction to the History of Printing Types<dd>by Geoffrey Dowding (British Library, 1998, UK ISBN 0-7123-4563-9; USA ISBN 1-884718-44-2) @@ -42,10 +42,10 @@ a more interesting overall view of types in general and some of their history. <dt>Treasury of Alphabets and Lettering<dd>by Jan Tschichold (W. W. Norton, 1992, ISBN 0-393-70197-2) <dt>A Short History of the Printed Word<dd>by Warren Chappell and - Robert Bringhurst (Hartley & Marks, 1999, ISBN 0-88179-154-7) + Robert Bringhurst (Hartley & Marks, 1999, ISBN 0-88179-154-7) </dl> <p/> The above lists are limited to books published in English. Typographic -styles are somewhat language-dependent, and similarly the ‘interesting’ fonts +styles are somewhat language-dependent, and similarly the ‘interesting’ fonts depend on the particular writing system involved. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html index 76ef208ec98..6642565dc4e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typend.html @@ -1,43 +1,43 @@ <head> <title>UK TeX FAQ -- question label typend</title> </head><body> -<h3>“Please type a command or say <code>\</code><code>end</code>”</h3> +<h3>“Please type a command or say <code>\</code><code>end</code>”</h3> <p/>Sometimes, when you are running (La)TeX, it will abruptly stop and present you with a prompt (by default, just a <code>*</code> character). Many -people (including this author) will reflexively hit the ‘return’ -key, pretty much immediately, and of course this is no help at all — +people (including this author) will reflexively hit the ‘return’ +key, pretty much immediately, and of course this is no help at all — TeX just says: <pre> (Please type a command or say `\end') </pre> and prompts you again. -<p/>What’s happened is that your (La)TeX file has finished prematurely, +<p/>What’s happened is that your (La)TeX file has finished prematurely, and TeX has fallen back to a supposed including file, from the -terminal. This could have happened simply because you’ve omitted +terminal. This could have happened simply because you’ve omitted the <code>\</code><code>bye</code> (Plain TeX), <code>\</code><code>end{document}</code> (LaTeX), or whatever. Other common errors are failure to close the braces round a -command’s argument, or (in LaTeX) failure to close a verbatim -environment: in such cases you’ve already read and accepted an +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. -<p/>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 -advice, to “say <code>\</code><code>end</code>” is good enough: it will kill the run; if -you’re running LaTeX, the argument will be necessary: +<p/>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 +advice, to “say <code>\</code><code>end</code>” is good enough: it will kill the run; if +you’re running LaTeX, the argument will be necessary: <code>\</code><code>end{document}</code>. -<p/>However, as often as not this isn’t the problem, and (short of +<p/>However, as often as not this isn’t the problem, and (short of debugging the source of the document before ending) brute force is -probably necessary. Excessive force (killing the job that’s +probably necessary. Excessive force (killing the job that’s running TeX) is to be avoided: there may well be evidence in the <code>.log</code> file that will be useful in determining what the -problem is — so the aim is to persuade TeX to shut itself down +problem is — so the aim is to persuade TeX to shut itself down and hence flush all log output to file. <p/>If you can persuade TeX to read it, an end-of-file indication (control-<code>D</code> under Unix, control-<code>Z</code> under Windows) will provoke TeX to report an error and exit immediately. Otherwise you should attempt to provoke an error dialogue, from which you can exit (using -the <code>x</code> ‘command’). An accessible error could well be inserting an +the <code>x</code> ‘command’). An accessible error could well be inserting an illegal character: what it is will depend on what macros you are -running. If you can’t make that work, try a silly command name or +running. If you can’t make that work, try a silly command name or two. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html index a5b5d494832..ffea3ab5621 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label typo-style</title> </head><body> <h3>Typography tutorials</h3> -<p/>Peter Wilson’s manual for his <i>memoir</i> class has a lengthy +<p/>Peter Wilson’s manual for his <i>memoir</i> class has a lengthy introductory section on typographic considerations, which is a fine tutorial, written by someone who is aware of the issues as they apply to (La)TeX users. -<p/>There’s also (at least one) typographic style tutorial available on +<p/>There’s also (at least one) typographic style tutorial available on the Web, the excellent -“<a href="http://www.nbcs.rutgers.edu/~hedrick/typography/typography.janson-syntax.107514.pdf">Guidelines for Typography in NBCS</a>”. +“<a href="http://www.nbcs.rutgers.edu/~hedrick/typography/typography.janson-syntax.107514.pdf">Guidelines for Typography in NBCS</a>”. In fact, its <a href="http://www.nbcs.rutgers.edu/~hedrick/typography/index.html">parent page</a> is also worth a read: among other things, it provides copies of the -“guidelines” document in a wide variety of primary fonts, for +“guidelines” document in a wide variety of primary fonts, for comparison purposes. The author is careful to explain that he has no ambition to supplant such excellent books as -<a href="FAQ-typebooks.html">Bringhurst’s</a>, but the document (though it does +<a href="FAQ-typebooks.html">Bringhurst’s</a>, but the document (though it does contain its Rutgers-local matter) is a fine introduction to the issues of producing readable documents. <dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html index 70200a3e798..3a73cc64222 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underline.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label underline</title> </head><body> -<h3>Underlined text won’t break</h3> +<h3>Underlined text won’t break</h3> <p/>Knuth made no provision for underlining text: he took the view that underlining is not a typesetting operation, but rather one that provides emphasis on typewriters, which typically offer but one @@ -13,8 +13,8 @@ specify double-spaced <a href="FAQ-linespace.html">thesis styles</a>) continue to require underlining of us, so LaTeX as distributed defines an <code>\</code><code>underline</code> command that applies the mathematical -‘underbar’ operation to text. This technique is not entirely -satisfactory, however: the text gets stuck into a box, and won’t break +‘underbar’ operation to text. This technique is not entirely +satisfactory, however: the text gets stuck into a box, and won’t break at line end. <p/>Two packages are available that solve this problem. The <i>ulem</i> package redefines the @@ -24,7 +24,7 @@ end of a line. (The package is capable of other peculiar effects, too: read its documentation, contained within the file itself.) The <i>soul</i> package defines an <code>\</code><code>ul</code> command (after which the package is, in part, named) that underlines running text. -<p/>Beware of <i>ulem</i>’s default behaviour, which is to convert the +<p/>Beware of <i>ulem</i>’s default behaviour, which is to convert the <code>\</code><code>emph</code> command into an underlining command; this can be avoided by loading the package with: <pre> @@ -32,7 +32,7 @@ loading the package with: </pre> Documentation of <i>ulem</i> is in the package itself. <dl> -<dt><tt><i>ulem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a> +<dt><tt><i>ulem.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ulem.zip">macros/latex/contrib/ulem</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ulem/">browse the directory</a>) <dt><tt><i>soul.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html index 5f45096bdb3..c6afdf7977f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-underscore.html @@ -2,21 +2,21 @@ <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>, on its own, in the course of ordinary text, TeX will -complain. If you’re writing a document which will contain a large +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 +there are significant points where it’s easy to get it wrong. There is therefore a package <i>underscore</i> which provides a general solution to this requirement. -<p/>There is a problem, though: OT1 text fonts don’t contain an -underscore character, unless they’re in the typewriter version of the +<p/>There is a problem, though: OT1 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 <code>cmtt</code>). So either you must ensure that your underscore characters only occur in text set in a typewriter font, or you must use a more modern encoding, such as @@ -31,9 +31,9 @@ be acceptable to use the following construct: \texttt{create\us process} </pre> </blockquote><p> -The construction isn’t in the least robust (in the normal English +The construction isn’t in the least robust (in the normal English sense of the word), but it <em>is</em> robust under expansion (i.e., the -LaTeX sense of the word); so use it with care, but don’t worry +LaTeX sense of the word); so use it with care, but don’t worry about section headings and the like. <dl> <dt><tt><i>underscore.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/underscore.sty">macros/latex/contrib/misc/underscore.sty</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html index 15f17eb50d1..2bf8f356c43 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html @@ -1,16 +1,16 @@ <head> <title>UK TeX FAQ -- question label unkgrfextn</title> </head><body> -<h3>“Unknown graphics extension”</h3> +<h3>“Unknown graphics extension”</h3> <p/>The LaTeX graphics package deals with several different types of DVI (or other) output drivers; each one of them has a potential to deal with a different selection of graphics formats. The package therefore has to be told what graphics file types its output driver knows about; this is usually done in the <<i>driver</i>><code>.def</code> file -corresponding to the output driver you’re using. +corresponding to the output driver you’re using. <p/>The error message arises, then, if you have a graphics file whose -extension doesn’t correspond with one your driver knows about. Most -often, this is because you’re being optimistic: asking +extension doesn’t correspond with one your driver knows about. Most +often, this is because you’re being optimistic: asking <i>dvips</i> to deal with a <code>.png</code> file, or PDFTeX to deal with a <code>.eps</code> file: the solution in this case is to transform the graphics file to a format your driver knows about. @@ -18,10 +18,10 @@ file to a format your driver knows about. format of your file, you are probably falling foul of a limitation of the file name parsing code that the graphics package uses. Suppose you want to include a graphics file <i>home.bedroom.eps</i> using the -<i>dvips</i> driver; the package will conclude that your file’s +<i>dvips</i> driver; the package will conclude that your file’s extension is <code>.bedroom.eps</code>, and will complain. <p/>The <i>grffile</i> package deals with the last problem (and -others — see the package documentation); using the package, you may +others — see the package documentation); using the package, you may write: <blockquote> <pre> @@ -38,12 +38,12 @@ or you may even write </pre> </blockquote><p> and <i>graphicx</i> will find a <code>.eps</code> or <code>.pdf</code> -(or whatever) version, according to what version of (La)TeX you’re +(or whatever) version, according to what version of (La)TeX you’re running. -<p/>If for some reason you can’t use <i>grffile</i>, you have three +<p/>If for some reason you can’t use <i>grffile</i>, you have three unsatisfactory alternatives: <ul> -<li> Rename the file — for example <i>home.bedroom.eps</i>-> +<li> Rename the file — for example <i>home.bedroom.eps</i>-> <i>home-bedroom.eps</i> <li> Mask the first dot in the file name: <pre> @@ -58,7 +58,8 @@ unsatisfactory alternatives: </pre> </ul> <dl> -<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of the <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>) collection +<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of the Oberdiek collection + <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/grffile.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html index d5bcaa3d37e..baec7fe9c27 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uploads.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label uploads</title> </head><body> <h3>Contributing a file to the archives</h3> -<p/>You have something to submit to the archive — great! Before we even -start, here’s a check-list of things to sort out: +<p/>You have something to submit to the archive — great! Before we even +start, here’s a check-list of things to sort out: <ol> <li> Licence: in the spirit of TeX, we hope for free software; in - the spirit of today’s lawyer-enthralled society, CTAN + the spirit of today’s lawyer-enthralled society, CTAN provides a - <a href="http://mirrors.ctan.org/help/Catalogue/licenses.html">list of “standard” licence statements</a>. -<li> Documentation: it’s good for users to be able to browse + <a href="http://mirrors.ctan.org/help/Catalogue/licenses.html">list of “standard” licence statements</a>. +<li> Documentation: it’s good for users to be able to browse documentation before downloading a package. You need at least a plain text <i>README</i> file (exactly that name); in addition a PDF file of the package documentation, prepared for screen @@ -17,29 +17,29 @@ start, here’s a check-list of things to sort out: <li> Name: endless confusion is caused by name clashes. If your package has the same name as one already on CTAN, or if your package installation generates files of the same name as something - in a “normal” distribution, the CTAN team will delay - installation while they check that you’re doing the right thing: + in a “normal” distribution, the CTAN team will delay + installation while they check that you’re doing the right thing: they may nag you to change the name, or to negotiate a take-over with the author of the original package. <a href="FAQ-findfiles.html">Browse the archive</a> to ensure uniqueness. <p/> The name you choose should also (as far as possible) be somewhat descriptive of what your submission actually <em>does</em>; while - “descriptiveness” is to some extent in the eye of the beholder, - it’s clear that names such as <i>mypackage</i> or <i>jiffy</i> - aren’t suitable. + “descriptiveness” is to some extent in the eye of the beholder, + it’s clear that names such as <i>mypackage</i> or <i>jiffy</i> + aren’t suitable. </ol> <p/>If you are able to use anonymous <i>ftp</i>, you can upload that way. The file <i>README.uploads</i> on CTAN tells you where to upload, what to upload, and how to notify the CTAN management about what you want doing with your upload. <p/>You may also upload via the Web: each of the principal CTAN -sites offers an upload page — choose from +sites offers an upload page — choose from <a href="http://www.ctan.org/upload.html">http://www.ctan.org/upload.html</a>, <a href="http://www.dante.de/CTAN/upload.html">http://www.dante.de/CTAN/upload.html</a> or <a href="http://www.tex.ac.uk/upload.html">http://www.tex.ac.uk/upload.html</a>; the pages lead you through the process, showing you the information you need to supply. This method enforces one file per upload: if you had intended to upload lots of -files, you need to bundle them into an ‘archive’ file of some sort; +files, you need to bundle them into an ‘archive’ file of some sort; acceptable formats are <code>.zip</code> and <code>.tar.gz</code> (or <code>.tar.bz2</code>). <p/>If you can use neither of these methods, or if you find something @@ -48,14 +48,14 @@ confusing, ask advice of the <a href="mailto:ctan@dante.de">CTAN management</a>: if the worst comes to the worst, it may be possible to mail a contribution. This really is a last-resort route: none of the -CTAN sites is anyone’s regular workstation, so if you mail to +CTAN sites is anyone’s regular workstation, so if you mail to one of the maintainers, that maintainer then has to upload to CTAN. -<p/>If it’s appropriate (if your package is large, or regularly updated), +<p/>If it’s appropriate (if your package is large, or regularly updated), the CTAN management can arrange to <i>mirror</i> your contribution direct into the archive. At present this may only be done if your contribution is available via <i>ftp</i>, and of -course the directory structure on your repository must ‘fit’. +course the directory structure on your repository must ‘fit’. <dl> <dt><tt><i>README.uploads</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/README.uploads">README.uploads</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html index 57fe5142e5c..6b25f28bebf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-upquot.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label upquot</title> </head><body> <h3>Realistic quotes for verbatim listings</h3> -<p/>The <code>cmtt</code> font has “curly” quotes, -which are pleasing on the eye, but don’t really tally with what one +<p/>The <code>cmtt</code> font has “curly” quotes, +which are pleasing on the eye, but don’t really tally with what one sees on a modern <i>xterm</i>. <p/>The appearance of these quotes is critical in program listings, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html index 73e038bfe74..c15db500cca 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-useMF.html @@ -3,25 +3,25 @@ </head><body> <h3>Getting Metafont to do what you want</h3> <p/>Metafont allows you to create your own fonts, and most TeX users -will never need to use it — modern (La)TeX systems contain +will never need to use it — modern (La)TeX systems contain rather few Metafont fonts of any significance, and when Metafont output is -needed the font generation is done, automatically, “on the fly”. -<p/>If you find you have some special requirement that the system doesn’t +needed the font generation is done, automatically, “on the fly”. +<p/>If you find you have some special requirement that the system doesn’t satisfy, you need to know about Metafont in rather more detail. Metafont, unlike TeX, requires customisation for each output device: such -customisation is conventionally held in a “mode” associated with the +customisation is conventionally held in a “mode” associated with the device. Modes are commonly defined using the <code>mode_def</code> convention described on page 94 of <em>The Metafontbook</em> (see <a href="FAQ-books.html">TeX-related books</a>). You will need a file, conventionally called <i>local.mf</i>, containing all the <code>mode_def</code>s you will be using. In the unlikely event that -<i>local.mf</i> doesn’t already exist, Karl Berry’s collection of +<i>local.mf</i> doesn’t already exist, Karl Berry’s collection of modes (<i>modes.mf</i>) is a good starting point -(it can be used as a ‘<i>local.mf</i>’ without modification in a +(it can be used as a ‘<i>local.mf</i>’ without modification in a typical modern implementation of Metafont). Lists of settings for various output devices are also published periodically in <i>TUGboat</i> (see <a href="FAQ-TUGstar.html">TUG</a>). Now create -a <code>plain</code> base file using <i>mf</i> (in “initialisation” +a <code>plain</code> base file using <i>mf</i> (in “initialisation” mode), <code>plain.mf</code>, and <code>local.mf</code>: <blockquote> <pre> @@ -42,29 +42,29 @@ This will create a base file named <i>plain.base</i> on MSDOS systems). Move the file to the directory containing the base files on your system. <p/>Now you need to make sure Metafont loads this new base when it starts up. If -Metafont loads the <code>plain</code> base by default on your system, then you’re +Metafont loads the <code>plain</code> base by default on your system, then you’re ready to go. Under Unix (using the default TeX Live (and earlier) distributions this does indeed happen, but we could for instance define a command <i>plainmf</i> -which executes ‘<code>mf -base=plain</code>’ (or, in more traditional -style ‘<code>mf &plain</code>’) which loads the <code>plain</code> base +which executes ‘<code>mf -base=plain</code>’ (or, in more traditional +style ‘<code>mf &plain</code>’) which loads the <code>plain</code> base file. <p/>The usual way to create a font with Metafont (with an appropriate base -file loaded) is to start Metafont’s input with the +file loaded) is to start Metafont’s input with the line <pre> -\mode=<mode name>; mag=<magnification>; input <font file name> +\mode=<mode name>; mag=<magnification>; input <font file name> </pre> -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’ mode and Metafont will produce an output file called -<i><font file name>.2602gf</i>) -The <code><magnification></code> is a floating point number or -‘magstep’ (magsteps are defined in <em>The Metafontbook</em> and +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’ mode and Metafont will produce an output file called +<i><font file name>.2602gf</i>) +The <code><magnification></code> is a floating point number or +‘magstep’ (magsteps are defined in <em>The Metafontbook</em> and <em>The TeXbook</em>). -If <code>mag=<magnification></code> is omitted, then the default +If <code>mag=<magnification></code> is omitted, then the default is 1 (magstep 0). For example, to generate cmr10 at 12pt for an Epson printer you might type <blockquote> @@ -80,7 +80,7 @@ look something like mf '\mode=epson; mag=magstep 1; input cmr10' </pre> </blockquote><p> -If you need a special mode that isn’t in the base, you can put its +If you 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>\</code><code>smode</code> command. For example, to create <i>cmr10.300gf</i> for an LN03 printer, using the file @@ -104,10 +104,10 @@ commands), you would type mf \smode="ln03"; input cmr10 </pre> </blockquote><p> -This technique isn’t one you should regularly use, but it may +This technique isn’t one you should regularly use, but it may prove useful if you acquire a new printer and want to experiment with parameters, or for some other reason are regularly editing the -parameters you’re using. Once you’ve settled on an appropriate set of +parameters you’re using. Once you’ve settled on an appropriate set of parameters, you should use them to rebuild the base file that you use. <p/>Other sources of help are discussed in our list of <a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html index 84aad77577f..6b15449dda3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usebibtex.html @@ -1,15 +1,15 @@ <head> <title>UK TeX FAQ -- question label usebibtex</title> </head><body> -<h3>“Normal” use of BibTeX from LaTeX</h3> +<h3>“Normal” use of BibTeX from LaTeX</h3> <p/>To create a bibliography for your document, you need to perform a sequence of steps, some of which seem a bit odd. If you choose to use BibTeX, the sequence is: -<p/>First: you need a BibTeX bibliography file (a <code>.bib</code> file) — see +<p/>First: you need a BibTeX bibliography file (a <code>.bib</code> file) — see -“<a href="FAQ-buildbib.html">creating a BibTeX file</a>”. +“<a href="FAQ-buildbib.html">creating a BibTeX file</a>”. <p/>Second: you must write your LaTeX document to include a declaration -of the ‘style’ of bibliography, citations, and a reference to the +of the ‘style’ of bibliography, citations, and a reference to the bibliography file mentioned in the step 1. So we may have a LaTeX file containing: <blockquote> @@ -25,7 +25,7 @@ Alice struggles~\cite{Carroll:1865}. </blockquote><p> Note: we have bibliography style <i>plain</i>, above, which is nearly the simplest of the lot: a sample text, showing the sorts of -style choices available, can be found on Ken Turner’s web site: +style choices available, can be found on Ken Turner’s web site: <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html</a> <p/>Third: you must process the file. <blockquote> @@ -38,7 +38,7 @@ writes a note of the style to the <code>.aux</code> file; each <code>\</code><code>cite</code> command writes a note of the citation to the <code>.aux</code> file, and the <code>\</code><code>bibliography</code> command writes a note of which <code>.bib</code> file is to be used, to the <code>.aux</code> file. -<p/>Note that, at this stage, LaTeX isn’t “resolving” any of the +<p/>Note that, at this stage, LaTeX isn’t “resolving” any of the citations: at every <code>\</code><code>cite</code> command, LaTeX will warn you of the undefined citation, and when the document finishes, there will be a further warning of undefined references. @@ -50,12 +50,12 @@ further warning of undefined references. bibtex myfile </pre> </blockquote><p> -Don’t try to tell BibTeX anything but the file name: say -<code>bibtex myfile.aux</code> (because you know it’s going to read the +Don’t try to tell BibTeX anything but the file name: say +<code>bibtex myfile.aux</code> (because you know it’s going to read the <code>.aux</code> file) and BibTeX will blindly attempt to process <code>myfile.aux.aux</code>. <p/>BibTeX will scan the <code>.aux</code> file; it will find which bibliography -style it needs to use, and will “compile” that style; it will note +style it needs to use, and will “compile” that style; it will note the citations; it will find which bibliography files it needs, and will run through them matching citations to entries in the bibliography; and finally it will sort the entries that have been @@ -67,8 +67,8 @@ it finds a <code>.bbl</code> file, and reads it. As it encounters each <code>\</code><code>bibitem</code> command in the file, it notes a definition of the citation. <p/>Sixth: you run LaTeX yet again. This time, it finds values for all -the citations, in its <code>.aux</code> file. Other things being equal, you’re -done… until you change the file. +the citations, in its <code>.aux</code> file. Other things being equal, you’re +done… until you change the file. <p/>If, while editing, you change any of the citations, or add new ones, you need to go through the process above from steps 3 (first run of LaTeX) to 6, again, before the document is once again stable. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html index 212f6d76180..dbe807eaedf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html @@ -6,18 +6,18 @@ the armoury of the (La)TeX user: high quality outlines of fonts that were until recently difficult to obtain, all in a free and relatively compact package. However, the spartan information file -that comes with the fonts remarks “It is presumed that a potential -user knows what to do with all these files”. This answer aims to +that comes with the fonts remarks “It is presumed that a potential +user knows what to do with all these files”. This answer aims to fill in the requirements: the job is really not terribly difficult. <p/>Note that teTeX distributions, from version 3.0, already have the <i>lm</i> fonts: all you need do is use them. The fonts may also be installed via the package manager, in a current MiKTeX system. -The remainder of this answer, then, is for people who don’t use such +The remainder of this answer, then, is for people who don’t use such systems. <p/>The font (and related) files appear on CTAN as a set of -single-entry <a href="FAQ-tds.html">TDS trees</a> — +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 +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 @@ -34,9 +34,9 @@ previewers and Type 1-to-PK conversion programs, by <pre> updmap --enable Map lm.map </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 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> as described in the MiKTeX <a href="http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg">online documentation</a>. @@ -48,8 +48,8 @@ previewers and Type 1-to-PK conversion programs, by <code>\</code><code>usepackage{lmodern}</code> </blockquote><p> this will make the fonts the default -for all three LaTeX font families (“roman”, “sans-serif” and -“typewriter”). You also need +for all three LaTeX font families (“roman”, “sans-serif” and +“typewriter”). You also need <blockquote> <code>\</code><code>usepackage[T1]{fontenc}</code> </blockquote><p> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html index cdfc95f9c73..c37b98cdb0c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html @@ -1,14 +1,14 @@ <head> <title>UK TeX FAQ -- question label usepictex</title> </head><body> -<h3>Why can’t I load PicTeX?</h3> +<h3>Why can’t I load PicTeX?</h3> <p/>PicTeX is a resource hog; fortunately, most modern TeX implementations offer generous amounts of space, and most modern -computers are pretty fast, so users aren’t too badly affected by its +computers are pretty fast, so users aren’t too badly affected by its performance. <p/>However, PicTeX has the further unfortunate tendency to fill up -TeX’s fixed-size arrays — notably the array of 256 ‘dimension’ -registers. This is a particular problem when you’re using +TeX’s fixed-size arrays — notably the array of 256 ‘dimension’ +registers. This is a particular problem when you’re using <i>pictex.sty</i> with LaTeX and some other packages that also need dimension registers. When this happens, you will see the TeX error message: @@ -18,24 +18,24 @@ message: </pre> </blockquote><p> There is nothing that can directly be done about this error: you -can’t extend the number of available <code>\</code><code>dimen</code> registers without +can’t extend the number of available <code>\</code><code>dimen</code> registers without extending TeX itself. <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a> both do this, as - does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. + does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. -<p/>It’s actually quite practical (with most modern distributions) to use -e-TeX’s extended register set: use package <i>etex</i> (which +<p/>It’s actually quite practical (with most modern distributions) to use +e-TeX’s extended register set: use package <i>etex</i> (which comes with e-TeX distributions) and the allocation mechanism is altered to cope with the larger register set: PicTeX will now load. -<p/>If you’re in some situation where you can’t use e-TeX, you need to change -PicTeX; unfortunately PicTeX’s author is no longer active in the +<p/>If you’re in some situation where you can’t use e-TeX, you need to change +PicTeX; unfortunately PicTeX’s author is no longer active in the TeX world, so one must resort to patching. There are two solutions available. <p/>The ConTeXt module <i>m-pictex.tex</i> (for Plain TeX and variants) or the corresponding LaTeX <i>m-pictex</i> package provide an ingenious solution to the problem based on hacking the code of <code>\</code><code>newdimen</code> itself. -<p/>Alternatively, Andreas Schrell’s <i>pictexwd</i> and related +<p/>Alternatively, Andreas Schrell’s <i>pictexwd</i> and related packages replace PicTeX with a version that uses 33 fewer <code>\</code><code>dimen</code> registers; so use <i>pictexwd</i> in place of <i>pictex</i> (either as a LaTeX package, or as a file to read @@ -52,7 +52,7 @@ program for other systems (including Windows, nowadays). <dt><tt><i>m-pictex.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a> <dt><tt><i>m-pictex.tex</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a> <dt><tt><i>MathsPic</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/graphics/mathspic.zip">graphics/mathspic</a> (or <a href="http://www.tex.ac.uk/tex-archive/graphics/mathspic/">browse the directory</a>) -<dt><tt><i>pictexwd.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon.zip">graphics/pictex/addon</a> (or <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon/">browse the directory</a>) +<dt><tt><i>pictexwd.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon.zip">graphics/pictex/addon</a> (or <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/pictexwd.html">catalogue entry</a> </dl> <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html index 6490fc4a377..a8be8f49b0e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html @@ -9,11 +9,11 @@ see <a href="FAQ-metrics.html">metrics for PostScript fonts</a>. You also need the fonts themselves; PostScript printers come with a set of fonts built in, but to extend your repertoire you almost invariably need to buy from one of the many commercial font vendors (see, for -example, <a href="FAQ-psfchoice.html">“choice of fonts”</a>). +example, <a href="FAQ-psfchoice.html">“choice of fonts”</a>). <p/>If you use LaTeX2e, the best way to get PostScript fonts into your document is to use the PSNFSS package maintained by Walter Schmidt. The LaTeX3 project team declare that PSNFSS is -“required”, and bug reports may be submitted via the +“required”, and bug reports may be submitted via the <a href="FAQ-latexbug.html">LaTeX bugs system</a>. PSNFSS gives you a set of packages for changing the default roman, sans-serif and typewriter fonts; <em>e.g</em>., the @@ -26,8 +26,8 @@ typewriter font to <i>Courier</i>. To go with these packages, you need the font metric files and font description (<i>.fd</i>) files for each font family you want to use. For convenience, -metrics for the ‘common 35’ PostScript fonts found in most PostScript printers -are provided with PSNFSS, packaged as the “Laserwriter set”. +metrics for the ‘common 35’ PostScript fonts found in most PostScript printers +are provided with PSNFSS, packaged as the “Laserwriter set”. <p/>For older versions of LaTeX there are various schemes, of which the simplest to use is probably the PSLaTeX macros distributed with <i>dvips</i>. @@ -36,13 +36,13 @@ the fonts is not the same as Computer Modern it will be up to you to redefine various macros and accents, or you can use the font re-encoding mechanisms available in many drivers and in <i>ps2pk</i> and <i>afm2tfm</i>. -<p/>Victor Eijkhout’s <a href="FAQ-lollipop.html">Lollipop package</a> +<p/>Victor Eijkhout’s <a href="FAQ-lollipop.html">Lollipop package</a> supports declaration of font families and styles in a similar way to -LaTeX’s NFSS, and so is easy to use with PostScript fonts. +LaTeX’s NFSS, and so is easy to use with PostScript fonts. <p/>Some common problems encountered are discussed elsewhere (see <a href="FAQ-psfontprob.html">problems with PS fonts</a>). <dl> -<dt><tt><i>Metrics for the ‘Laserwriter’ set of 35 fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a> +<dt><tt><i>Metrics for the ‘Laserwriter’ set of 35 fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a> <dt><tt><i>lollipop</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/lollipop.zip">macros/lollipop</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse the directory</a>) <dt><tt><i>psnfss</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usesymb.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usesymb.html index 631682b7eef..d7883168955 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usesymb.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usesymb.html @@ -5,10 +5,10 @@ <p/>Most symbol font sets come with a package that defines commands for every symbol in the font. While this is convenient, it can lead to difficulties, particularly with name clashes when you load packages -that cover fonts which duplicate symbols — an issue which is +that cover fonts which duplicate symbols — an issue which is discussed in - “<a href="FAQ-alreadydef.html">symbol already defined</a>”. + “<a href="FAQ-alreadydef.html">symbol already defined</a>”. Some font sets (for example, <i>MnSymbol</i>) are huge, and the accompanying macros cover so many symbols that name clashes are surely a serious problem. @@ -19,8 +19,8 @@ documentation provides font tables). The basic command is <code>\</code><code>ding{</code><em>number</em><code>}</code> for a single symbol; there are commands for other fancier uses. <i>Pifont</i> also allows you to select other fonts, for similar use. -<p/>The <i>yagusylo</i> describes itself as “an extended version of -<i>pifont</i>, gone technicolor”. It provides all the facilities +<p/>The <i>yagusylo</i> describes itself as “an extended version of +<i>pifont</i>, gone technicolor”. It provides all the facilities of <i>pifont</i>, but allows you to create your own mnemonic names for symbols. Thus, while you can say <code>\</code><code>yagding[</code><em>family</em><code>]{</code><em>symbol number</em><code>}</code>[colour], you can also diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html index d7d35f5f442..75832bc763e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidcol.html @@ -3,25 +3,25 @@ </head><body> <h3>Variable-width columns in tables</h3> <p/>This is a slightly different take on the problem addressed in -“<a href="FAQ-fixwidtab.html">fixed-width tables</a>” — here we have -a column whose size we can’t absolutely predict when we design the +“<a href="FAQ-fixwidtab.html">fixed-width tables</a>” — here we have +a column whose size we can’t absolutely predict when we design the document. <p/>While the basic techniques (the <i>tabularx</i>, <i>tabulary</i> and <i>ltxtable</i> packages) are the same for this problem as for the -fixed-width <em>table</em> problem, there’s one extra tool that we can +fixed-width <em>table</em> problem, there’s one extra tool that we can call to our aid, which may be preferable in some situations. <p/>Suppose we have data in one column which we read from an external -source, and the source itself isn’t entirely predictable. The data in +source, and the source itself isn’t entirely predictable. The data in the column may end up pretty narrow in every row of the table, or it may be wide enough that the table would run over the edge of the page; -however, we don’t want to make the column as wide as possible “just -in case”, by defining a fixed size for the table. We would like the +however, we don’t want to make the column as wide as possible “just +in case”, by defining a fixed size for the table. We would like the column to be as small as possible, but have the possibility to spread to a maximum width and (if even that width is exceeded) turn into a <code>p</code>-style column. <p/>The <i>varwidth</i> package, discussed in -“<a href="FAQ-varwidth.html">automatic sizing of minipages</a>”, provides -a solution. If you load it together with the LaTeX “required” +“<a href="FAQ-varwidth.html">automatic sizing of minipages</a>”, provides +a solution. If you load it together with the LaTeX “required” <i>array</i> package, i.e.: <blockquote> <pre> @@ -29,7 +29,7 @@ a solution. If you load it together with the LaTeX “required” \usepackage{varwidth} </pre> </blockquote><p> -<i>varwidth</i> defines a new column-type “<code>V</code>”, which you +<i>varwidth</i> defines a new column-type “<code>V</code>”, which you can use as follows: <blockquote> <pre> @@ -54,7 +54,7 @@ or you can use it as follows: where the second column will end up noticeably wider, and will wrap to a second line in the third row. <dl> -<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/array.html">catalogue entry</a> <dt><tt><i>varwidth.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html index b3e19aedef4..c77dbcf70c1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-varwidth.html @@ -3,7 +3,7 @@ </head><body> <h3>Automatic sizing of <code>minipage</code></h3> <p/>The <code>minipage</code> environment requires you to specify the -width of the “page” you’re going to create. This is sometimes +width of the “page” you’re going to create. This is sometimes inconvenient: you would like to occupy less space, if possible, but <code>minipage</code> sets a box that is exactly the width you specified. @@ -12,15 +12,15 @@ that of the longest enclosed line, subject to a maximum width that you give it. So while <code>\</code><code>parbox{2cm}{Hello\\world!}</code> produces a box of width exactly <code>2cm</code>, <code>\</code><code>pbox{2cm}{Hello\\world!}</code> produces one whose width is -<code>1.79cm</code> (if one’s using the default <i>cmr</i> font for the +<code>1.79cm</code> (if one’s using the default <i>cmr</i> font for the text, at least). The package also provides a <code>\</code><code>settominwidth[</code><em>min</em><code>]{</code><em>length</em><code>}{</code><em>text</em><code>}</code> (which looks (almost) like the standard <code>\</code><code>settowidth</code> command), and a <code>\</code><code>widthofpbox</code> function analogous to the <code>\</code><code>widthof</code> command for use with the <i>calc</i> package. -<p/>The <i>eqparbox</i> package extends <i>pbox</i>’s idea, by +<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) -width. (Note that it doesn’t accept a limiting maximum width +width. (Note that it doesn’t accept a limiting maximum width parameter.) The package documentation shows the following example drawn from a joke <em>curriculum vitae</em>: <blockquote> @@ -46,12 +46,12 @@ the measured width of a group: the documentation shows how the command may be used to produce sensible-looking columns that mix <code>c</code>-, <code>r</code>- or <code>l</code>-rows, with the equivalent of a <code>p{...}</code> entry, by making the fixed-width rows an <i>eqparbox</i> group, and -making the last from a <code>\</code><code>parbox</code> using the width that’s been +making the last from a <code>\</code><code>parbox</code> using the width that’s been measured for the group. <p/>The <i>varwidth</i> package defines a <code>varwidth</code> -environment which sets the content of the box to match a “narrower -natural width” if it finds one. (You give it the same parameters as -you would give <code>minipage</code>: in effect, it is a ‘drop-in’ +environment which sets the content of the box to match a “narrower +natural width” if it finds one. (You give it the same parameters as +you would give <code>minipage</code>: in effect, it is a ‘drop-in’ replacement.) <i>Varwidth</i> provides its own ragged text command: <code>\</code><code>narrowragged</code>, which aims to make narrower lines and to put more text in the last line of the paragraph (thus producing lines with more diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html index 02155e4c254..787f22d3833 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbfile.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label verbfile</title> </head><body> <h3>Including a file verbatim in LaTeX</h3> -<p/>A good way is to use Rainer Schöpf’s <i>verbatim</i> package, +<p/>A good way is to use Rainer Schöpf’s <i>verbatim</i> package, which provides a command <code>\</code><code>verbatiminput</code> that takes a file name as argument: <blockquote> @@ -14,7 +14,7 @@ argument: </blockquote><p> Another way is to use the <code>alltt</code> environment, which requires the <i>alltt</i> package. The environment interprets its -contents ‘mostly’ verbatim, but executes any (La)TeX commands it +contents ‘mostly’ verbatim, but executes any (La)TeX commands it finds: <blockquote> <pre> @@ -26,12 +26,12 @@ finds: </pre> </blockquote><p> of course, this is little use for inputting (La)TeX source -code… +code… <p/>The <i>moreverb</i> package extends the <i>verbatim</i> package, providing a <code>listing</code> environment and a <code>\</code><code>listinginput</code> command, which line-number the text of the file. The package also has a <code>\</code><code>verbatimtabinput</code> command, that honours TAB characters in -the input (the package’s <code>listing</code> environment and the +the input (the package’s <code>listing</code> environment and the <code>\</code><code>listinginput</code> command also both honour TAB). <p/>The <i>sverb</i> package provides verbatim input (without recourse to the facilities of the <i>verbatim</i> package): @@ -55,8 +55,8 @@ advised. <dt><tt><i>fancyvrb.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>moreverb.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb.zip">macros/latex/contrib/moreverb</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moreverb/">browse the directory</a>) -<dt><tt><i>sverb.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>) -<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>sverb.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/sverb.html">catalogue entry</a> +<dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/verbatim.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html index 7aa28e7c370..ac17065aa66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html @@ -1,21 +1,21 @@ <head> <title>UK TeX FAQ -- question label verbwithin</title> </head><body> -<h3>Why doesn’t verbatim work within …?</h3> +<h3>Why doesn’t verbatim work within …?</h3> <p/>The LaTeX verbatim commands work by changing category codes. Knuth -says of this sort of thing “Some care is needed to get the timing -right…”, since once the category code has been assigned to a -character, it doesn’t change. So <code>\</code><code>verb</code> and +says of this sort of thing “Some care is needed to get the timing +right…”, since once the category code has been assigned to a +character, it doesn’t change. So <code>\</code><code>verb</code> and <code>\</code><code>begin{verbatim}</code> have to assume that they are getting the -first look at the parameter text; if they aren’t, TeX has already -assigned category codes so that the verbatim command doesn’t have a +first look at the parameter text; if they aren’t, TeX has already +assigned category codes so that the verbatim command doesn’t have a chance. For example: <blockquote> <pre> \verb+\error+ </pre> </blockquote><p> -will work (typesetting ‘<code>\</code><code>error</code>’), but +will work (typesetting ‘<code>\</code><code>error</code>’), but <blockquote> <pre> \newcommand{\unbrace}[1]{#1} @@ -23,9 +23,9 @@ will work (typesetting ‘<code>\</code><code>error</code>’), but </pre> </blockquote><p> will not (it will attempt to execute <code>\</code><code>error</code>). Other errors one -may encounter are ‘<code>\</code><code>verb</code> ended by end of line’, or even the -rather more helpful ‘<code>\</code><code>verb</code> illegal in command argument’. The -same sorts of thing happen with <code>\</code><code>begin{verbatim}</code> … +may encounter are ‘<code>\</code><code>verb</code> ended by end of line’, or even the +rather more helpful ‘<code>\</code><code>verb</code> illegal in command argument’. The +same sorts of thing happen with <code>\</code><code>begin{verbatim}</code> … <code>\</code><code>end{verbatim}</code>: <blockquote> <pre> @@ -40,28 +40,28 @@ barfoo } </pre> </blockquote><p> -provokes errors like ‘File ended while scanning use of -<code>\</code><code>@xverbatim</code>’, as <code>\</code><code>begin{verbatim}</code> fails to see its +provokes errors like ‘File ended while scanning use of +<code>\</code><code>@xverbatim</code>’, as <code>\</code><code>begin{verbatim}</code> fails to see its matching <code>\</code><code>end{verbatim}</code>. <p/>This is why the LaTeX book insists that verbatim commands must not appear in the argument of any other command; they -aren’t just fragile, they’re quite unusable in any command parameter, +aren’t just fragile, they’re quite unusable in any command parameter, regardless of <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a>. (The <code>\</code><code>verb</code> -command tries hard to detect if you’re misusing it; unfortunately, it -can’t always do so, and the error message is therefore not a reliable +command tries hard to detect if you’re misusing it; unfortunately, it +can’t always do so, and the error message is therefore not a reliable indication of problems.) -<p/>The first question to ask yourself is: “is <code>\</code><code>verb</code> actually -necessary?”. +<p/>The first question to ask yourself is: “is <code>\</code><code>verb</code> actually +necessary?”. <ul> <li> If <code>\</code><code>texttt{<em>your text</em>}</code> produces the same result - as <code>\</code><code>verb</code><code>+<em>your text</em>+</code>, then there’s no need of + as <code>\</code><code>verb</code><code>+<em>your text</em>+</code>, then there’s no need of <code>\</code><code>verb</code> in the first place. -<li> If you’re using <code>\</code><code>verb</code> to typeset a URL or email +<li> If you’re using <code>\</code><code>verb</code> to typeset a URL or email address or the like, then the <code>\</code><code>url</code> command from the - <i>url</i> will help: it doesn’t suffer from all the problems of - <code>\</code><code>verb</code>, though it’s still not robust; - “<a href="FAQ-setURL.html">typesetting URLs</a>” offers advice here. -<li> If you’re putting <code>\</code><code>verb</code> into the argument of a boxing + <i>url</i> will help: it doesn’t suffer from all the problems of + <code>\</code><code>verb</code>, though it’s still not robust; + “<a href="FAQ-setURL.html">typesetting URLs</a>” offers advice here. +<li> If you’re putting <code>\</code><code>verb</code> into the argument of a boxing command (such as <code>\</code><code>fbox</code>), consider using the <code>lrbox</code> environment: <blockquote> @@ -101,7 +101,7 @@ necessary?”. <code>\</code><code>string</code>. <code>\</code><code>texttt{my<code>\</code><code>string</code>_name}</code> typesets the same as <code>\verb+my_name+</code>, and will work in the argument of a command. It - won’t, however, work in a moving argument, and no amount of + won’t, however, work in a moving argument, and no amount of <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a> will make it work in such a case. <p/> A robust alternative is: @@ -112,9 +112,9 @@ necessary?”. \section{... \texttt{my\us name}} </pre> </blockquote><p> - Such a definition is ‘naturally’ robust; the construction - “<<i>back-tick</i>><code>\</code><code><<i>char</code></i>>” may be used for any - troublesome character (though it’s plainly not necessary for things + Such a definition is ‘naturally’ robust; the construction + “<<i>back-tick</i>><code>\</code><code><<i>char</code></i>>” may be used for any + troublesome character (though it’s plainly not necessary for things like percent signs for which (La)TeX already provides robust macros). </ul> @@ -124,7 +124,7 @@ package files. <dt><tt><i>fancyvrb.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyvrb/">browse the directory</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse the directory</a>) <dt><tt><i>url.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/url.zip">macros/latex/contrib/url</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/url/">browse the directory</a>) -<dt><tt><i>verbdef.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/verbdef.sty">macros/latex/contrib/misc/verbdef.sty</a> +<dt><tt><i>verbdef.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/verbdef.zip">macros/latex/contrib/verbdef</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/verbdef/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html index ab7f42388c5..029e3c23e1c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertposfp.html @@ -4,7 +4,7 @@ <h3>Vertical layout of float pages</h3> <p/>By default, LaTeX vertically centres the floats on a float page; the present author is not alone in not liking this arrangement. -Unfortunately, the control of the positioning is “buried” in +Unfortunately, the control of the positioning is “buried” in LaTeX-internal commands, so some care is needed to change the layout. <p/>Float pages use three LaTeX lengths (i.e., TeX skips) to define @@ -40,9 +40,9 @@ page, is a simple thing to do: </blockquote><p> Surprisingly, you may find this setting leaves your floats too high on the page. One can justify a value of <code>5pt</code> (in place of -<code>0pt</code>) — it’s roughly the difference between <code>\</code><code>topskip</code> +<code>0pt</code>) — it’s roughly the difference between <code>\</code><code>topskip</code> and the height of normal (<code>10pt</code>) text. -<p/>Note that this is a “global” setting (best established in a class +<p/>Note that this is a “global” setting (best established in a class file, or at worst in the document preamble); making the change for a single float page is likely (at the least) to be rather tricky. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html index bd77a1823ae..eb56d0f6f60 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-vertspacefloat.html @@ -5,10 +5,10 @@ <p/>A common complaint is that extra vertical space has crept into <code>figure</code> or <code>table</code> floating environments. More common still are users who post code that introduces this extra -space, and <em>haven’t noticed the problem</em>! +space, and <em>haven’t noticed the problem</em>! <p/>The trouble arises from the fact that the <code>center</code> environment (and its siblings <code>flushleft</code> and -<code>flushright</code>) are actually based on LaTeX’s +<code>flushright</code>) are actually based on LaTeX’s list-handling code; and lists always separate themselves from the material around them. Meanwhile, there are parameters provided to adjust the spacing between floating environments and their @@ -36,7 +36,7 @@ or worse still: </blockquote><p> unwarranted vertical space is going to appear. <p/>The solution is to let the float and the objects in it position -themselves, and to use “generic” layout commands rather than their +themselves, and to use “generic” layout commands rather than their list-based encapsulations. <blockquote> <pre> @@ -50,7 +50,7 @@ list-based encapsulations. (which even involves less typing). <p/>This alternative code will work with any LaTeX package. It will not work with obsolete (pre-LaTeX2e) packages such as -<i>psfig</i> or <i>epsf</i> — see +<i>psfig</i> or <i>epsf</i> — see <a href="FAQ-impgraph.html">graphics inclusion</a> for discussion of the genesis of <code>\</code><code>includegraphics</code>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html index bc36b5a85f3..ab5b4f37575 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-virtualfonts.html @@ -4,7 +4,7 @@ <h3>Virtual fonts</h3> <p/>Virtual fonts provide a means of collecting bits and pieces together to make the glyphs of a font: the bits and pieces may be other glyphs, -rules and other “basic” typesetting commands, and the positioning +rules and other “basic” typesetting commands, and the positioning information that specifies how everything comes together. <p/>Things that match the concept of virtual fonts for TeX were first implemented by David Fuchs in the very early days. However, for practical @@ -18,8 +18,8 @@ define in a virtual font look like characters to TeX (they appear with their sizes in a TFM file), but the DVI processor may expand them to something quite different. <p/>From the virtual font file, the DVI processor learns -details of what is in the virtual font, so as to know “what to draw, -where”. The virtual font may contain commands: +details of what is in the virtual font, so as to know “what to draw, +where”. The virtual font may contain commands: <ul> <li> just to remap the glyphs of a single font, <li> to make a composite font with glyphs drawn from several @@ -32,18 +32,18 @@ where”. The virtual font may contain commands: In practice, the most common use of virtual fonts is to remap Adobe Type 1 fonts (see <a href="FAQ-metrics.html">font metrics</a>), -though there has also been useful useful work building ‘fake’ maths +though there has also been useful useful work building ‘fake’ maths fonts (by bundling glyphs from several fonts into a single virtual font). Virtual Computer Modern fonts, making a -<a href="FAQ-ECfonts.html">Cork encoded</a> font from Knuth’s originals by using -remapping and fragments of DVI for single-glyph ‘accented -characters’, were the first “Type 1 format” Cork-encoded Computer +<a href="FAQ-ECfonts.html">Cork encoded</a> font from Knuth’s originals by using +remapping and fragments of DVI for single-glyph ‘accented +characters’, were the first “Type 1 format” Cork-encoded Computer Modern fonts available. <p/>Virtual fonts are normally created in a single ASCII VPL (Virtual Property List) file, which includes both sets of information. The <i>vptovf</i> program is then used to the create the binary TFM and VF files. -<p/>A “how-to” document, explaining how to generate a VPL, +<p/>A “how-to” document, explaining how to generate a VPL, describes the endless hours of fun that may be had, doing the job by hand. Despite the pleasures to be had of the manual method, the commonest way (nowadays) of generating VPL files is to use the @@ -56,7 +56,7 @@ fonts (it uses TeX to parse a description of the virtual font, and <dl> <dt><tt><i>fontinst</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse the directory</a>) <dt><tt><i>Knuth on virtual fonts</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/knuth/virtual-fonts">info/knuth/virtual-fonts</a> -<dt><tt><i>Virtual fonts “how to”</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a> +<dt><tt><i>Virtual fonts “how to”</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a> <dt><tt><i>qdtexvpl</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/qdtexvpl.zip">fonts/utilities/qdtexvpl</a> (or <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/qdtexvpl/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html index b15be120a2e..1532fa3f50d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-watermark.html @@ -1,42 +1,52 @@ <head> <title>UK TeX FAQ -- question label watermark</title> </head><body> -<h3>‘Watermarks’ on every page</h3> -<p/>It’s often useful to place some text (such as ‘DRAFT’) in the +<h3>‘Watermarks’ on every page</h3> +<p/>It’s often useful to place some text (such as ‘DRAFT’) in the background of every page of a document. For LaTeX users, this can be achieved with the <i>draftcopy</i> package. This can deal with many types of DVI processors (in the same way that the graphics -package does) and knows translations for the word ‘DRAFT’ into a wide +package does) and knows translations for the word ‘DRAFT’ into a wide range of languages (though you can choose your own word, too). Unfortunately, however, the package relies on PostScript specials, and will therefore fail if you are viewing your document with <i>xdvi</i>, -and won’t even compile if you’re using PDFLaTeX. (PDFLaTeX +and won’t even compile if you’re using PDFLaTeX. (PDFLaTeX users need one of the other solutions below.) <p/>The <i>wallpaper</i> package builds on <i>eso-pic</i> (see below). Apart from the single-image backdrops described above -(“wallpapers”, of course, to this package), the package provides +(“wallpapers”, of course, to this package), the package provides facilities for tiling images. All its commands come in pairs: one for -“general” use, and one applying to the current page only. -<p/>The <i>draftwatermark</i> package uses the same author’s +“general” use, and one applying to the current page only. +<p/>The <i>draftwatermark</i> package uses the same author’s <i>everypage</i> package to provide a simple interface for adding -textual (‘DRAFT’-like) watermarks. +textual (‘DRAFT’-like) watermarks. <p/>More elaborate watermarks may be achieved using the <i>eso-pic</i> package, which in turn uses the package <i>everyshi</i>, or by using <i>everypage</i>. <i>Eso-pic</i> attaches a <code>picture</code> environment to every page as it is shipped out; you can put things into that environment. The package provides -commands for placing things at certain useful points (like “text -upper left” or “text centre”) in the picture, but you’re at liberty +commands for placing things at certain useful points (like “text +upper left” or “text centre”) in the picture, but you’re at liberty to do what you like. -<p/><i>Everypage</i> allows you to add “something” to every page, or +<p/><i>Eso-pic</i> is, in turn, built upon the package +<i>atbegshi</i>. That package has the capability to produce +watermarks <em>on top of</em> the other material on the page; this +doesn’t sound very “watermark-like”, but can be useful on pages +where the watermark would otherwise be hidden by graphics or the +like. The <i>atbegshi</i> command that <i>eso-pic</i> uses is +<code>\</code><code>AtBeginShipoutUpperLeft</code>; <code>\</code><code>AtBeginShipoutUpperLeftForeground</code> +is what’s needed instead to place the material on top of the rest of +the content of the page. +<p/><i>Everypage</i> allows you to add “something” to every page, or to a particular page; you therefore need to construct your own apparatus for anything complicated. <dl> +<dt><tt><i>atbegshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/atbegshi.html">catalogue entry</a> <dt><tt><i>draftcopy.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftcopy.zip">macros/latex/contrib/draftcopy</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftcopy/">browse the directory</a>) <dt><tt><i>draftwatermark.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftwatermark.zip">macros/latex/contrib/draftwatermark</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftwatermark/">browse the directory</a>) <dt><tt><i>eso-pic.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic.zip">macros/latex/contrib/eso-pic</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic/">browse the directory</a>) <dt><tt><i>everypage.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/everypage.zip">macros/latex/contrib/everypage</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/everypage/">browse the directory</a>) -<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>) +<dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/everyshi.html">catalogue entry</a> <dt><tt><i>wallpaper.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wallpaper.zip">macros/latex/contrib/wallpaper</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wallpaper/">browse the directory</a>) </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html index 35e272da889..8f696115af3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wdnohyph.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label wdnohyph</title> </head><body> <h3>Preventing hyphenation of a particular word</h3> -<p/>It’s quite possible for (<em>any</em>) hyphenation of a particular word -to seem “completely wrong”, so that you want to prevent it being +<p/>It’s quite possible for (<em>any</em>) hyphenation of a particular word +to seem “completely wrong”, so that you want to prevent it being hyphenated. <p/>If the word occurs in just one place, put it in a box: <blockquote> @@ -22,7 +22,7 @@ non-hyphenation for it: </pre> </blockquote><p> This hyphenation exception (with no break points) will be used in -preference to what TeX’s hyphenation algorithm may come up with. +preference to what TeX’s hyphenation algorithm may come up with. <p/>In a multilingual document, repeat the exception specification for each language the word may appear in. So: <blockquote> @@ -35,11 +35,11 @@ each language the word may appear in. So: </pre> </blockquote><p> (note that <i>babel</i> will select the default language for the -document — English, in this case — at <code>\</code><code>begin{document}</code>.) +document — English, in this case — at <code>\</code><code>begin{document}</code>.) <p/>A particular instance of this requirement is avoiding the hyphenation of acronyms; a general rule for those that concoct acronyms seems to be to make the capital-letter sequence read as near as is possible -like a “real” word, but hyphenating an acronym often looks silly. +like a “real” word, but hyphenating an acronym often looks silly. The TeX flag <code>\</code><code>uchyph</code> is designed for suppressing such behaviour: <blockquote> @@ -48,7 +48,7 @@ behaviour: </pre> </blockquote><p> will stop hyphenation of upper-case words. (Note that Plain TeX -syntax is needed here: there’s no LaTeX alternative for setting +syntax is needed here: there’s no LaTeX alternative for setting this value.) <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html index d8636e58596..e4357848e0a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html @@ -3,8 +3,8 @@ </head><body> <h3>WEB systems for various languages</h3> <p/>TeX is written in the programming language WEB; WEB -is a tool to implement the concept of “literate programming”. -Knuth’s original implementation will be in any respectable +is a tool to implement the concept of “literate programming”. +Knuth’s original implementation will be in any respectable distribution of TeX, but the sources of the two tools (<i>tangle</i> and <i>weave</i>), together with a manual outlining the programming techniques, may be had from CTAN. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html index 2902f4ba598..b89f39d973f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-weirdhyphen.html @@ -5,17 +5,17 @@ <p/>If your words are being h-yphenated, like this, with jus-t single letters at the beginning or the end of the word, you may have a version mismatch -problem. TeX’s hyphenation system changed between version 2.9 +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 sure your <i>plain.tex</i> file has a version number which is at least 3.0, and rebuild your format. If you are using LaTeX 2.09 your -best plan is to upgrade to LaTeX2e. If for some reason you can’t, +best plan is to upgrade to LaTeX2e. If for some reason you can’t, the last version of LaTeX 2.09 (released on 25 March 1992) is still available (for the time being at least) and ought to solve this problem. -<p/>If you’re using LaTeX2e, the problem probably arises from your -<code>hyphen.cfg</code> file, which has to be created if you’re using a +<p/>If you’re using LaTeX2e, the problem probably arises from your +<code>hyphen.cfg</code> file, which has to be created if you’re using a multi-lingual version. <p/>A further source of oddity can derive from the 1995 release of <a href="FAQ-ECfonts.html">Cork-encoded fonts</a>, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html index 08b29711676..a09dc55989a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-what-TDS.html @@ -3,7 +3,7 @@ </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. (A discussion of +“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> @@ -24,39 +24,39 @@ 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 -“Settings” window ( - <code>Start</code>-> - <code>Programs</code>-> - <code>MiKTeX</code>-> +“Settings” window ( + <code>Start</code>-> + <code>Programs</code>-> + <code>MiKTeX</code>-> <code>Settings</code>) -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 (see below), -and register it using the window’s -“<code>Add</code>” button. +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 (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:\Local 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 — in such situations, the user may have no +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 +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 +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: +<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, +<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), it should go in your - <a href="FAQ-privinst.html">“home” TEXMF tree</a>; + something you’re developing yourself), it should go in your + <a href="FAQ-privinst.html">“home” TEXMF tree</a>; <li> if you <em>know</em> that the package you are installing is a replacement for the copy on the TEXMF tree of your (La)TeX distribution, you should replace the existing copy in the @@ -64,9 +64,9 @@ indistinguishable from those of a </ul> The reason one would put things on a local tree is to avoid their disappearance if the system is upgraded (or otherwise re-installed). -<p/>The reason one might place upgrades the distribution’s main tree is to +<p/>The reason one might place upgrades the distribution’s main tree is to avoid confusion. Suppose you were to place the file on the local -tree, and then install a new version of the distribution — you might +tree, and then install a new version of the distribution — you might have an effect like: <ul> <li> distribution comes with package version n; @@ -78,7 +78,7 @@ n+1 (from the local tree) <em>after</em> the new distribution has been installed. <p/>If you install in the local tree, the only way to avoid such problems is to carefully purge the local tree when installing a new -distribution. This is tedious, if you’re maintaining a large +distribution. This is tedious, if you’re maintaining a large installation. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html index 45e6983fcd7..c681d9682bc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatTeX.html @@ -7,36 +7,40 @@ says in the Preface to his book on TeX (see <a href="FAQ-books.html">books about TeX</a>) that it is -“<em>intended for the creation of beautiful books —</em> -<em>and especially for books that contain a lot of mathematics</em>”. +“<em>intended for the creation of beautiful books —</em> +<em>and especially for books that contain a lot of mathematics</em>”. (If TeX were <em>only</em> good for mathematical books, much of its -use nowadays would not happen: it’s actually a pretty good general +use nowadays would not happen: it’s actually a pretty good general typesetting system.) <p/>Knuth is Emeritus Professor of the Art of Computer Programming at Stanford University in California, USA. Knuth developed the first version of TeX in 1978 to deal with revisions to his series -“the Art of Computer Programming”. The idea proved popular and +“the Art of Computer Programming”. The idea proved popular and Knuth produced a second version (in 1982) which is the basis of what we use today. <p/>Knuth developed a system of -‘<a href="FAQ-lit.html">literate programming</a>’ to write TeX, +‘<a href="FAQ-lit.html">literate programming</a>’ to write TeX, and he provides the literate (WEB) source of TeX free of charge, together with tools for processing the <code>web</code> source into something -that can be compiled and something that can be printed; there’s never -any mystery about what TeX does. Furthermore, the WEB system -provides mechanisms to port TeX to new operating systems and -computers; and in order that one may have some confidence in the ports, -Knuth supplied a <a href="FAQ-triptrap.html">test</a> by +that can be compiled and something that can be printed; there is (in +principle) never any mystery about what TeX does. Furthermore, the +WEB system provides mechanisms to port TeX to new operating +systems and computers; and in order that one may have some confidence +in the ports, Knuth supplied a <a href="FAQ-triptrap.html">test</a> by means of which one may judge the fidelity of a TeX system. TeX and its documents are therefore highly portable. -<p/>TeX is a macro processor, and offers its users a powerful -programming capability. For this reason, TeX on its own is a -pretty difficult beast to deal with, so Knuth provided a package of -macros for use with TeX called Plain TeX; Plain TeX is -effectively the minimum set of macros one can usefully employ with -TeX, together with some demonstration versions of higher-level -commands (the latter are better regarded as models than used as-is). -When people say they’re “programming in TeX”, they usually mean -they’re programming in Plain TeX. +<p/>For the interested programmer, the distribution of TeX has some +fascination: it’s nothing like the way one would construct such a +program nowadays, yet it has lasted better than most, and has been +ported to many different computer architectures and operating +systems — the sorts of attributes that much modern programming +practice aims for. The processed ‘readable’ source of TeX the +program may be found in the + <a href="FAQ-tds.html">TDS structured version</a> of the distribution. + +<dl> +<dt><tt><i>Knuth’s source distribution</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/knuth/dist.zip">systems/knuth/dist</a> (or <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/dist/">browse the directory</a>) +<dt><tt><i>Knuth’s sources in TDS layout</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/latex-tds/knuth.tds.zip">macros/latex/contrib/latex-tds/knuth.tds.zip</a> +</dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html index e32179558f8..b1280c764be 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label whatbst</title> </head><body> <h3>Choosing a bibliography style</h3> -<p/>A large proportion of people are satisfied with one of Patashnik’s -original “standard” styles, <i>plain</i>, <i>unsrt</i>, +<p/>A large proportion of people are satisfied with one of Patashnik’s +original “standard” styles, <i>plain</i>, <i>unsrt</i>, <i>abbrv</i> and <i>alpha</i>. However, no style in that set -supports the “author-date” citation style that is popular in many +supports the “author-date” citation style that is popular in many fields; but there are a very large number of contributed styles available, that <em>do</em> support the format. <p/>(Note that author-date styles arose because the simple and clear @@ -19,20 +19,20 @@ free once again to use the simple option.) be found on - <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">Ken Turner’s web site</a>; + <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">Ken Turner’s web site</a>; <li> an excellent survey, that lists a huge variety of styles, sorted into their nominal topics as well as providing a good range of examples, is the Reed College - “<a href="http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html">Choosing a BibTeX style</a>”. + “<a href="http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html">Choosing a BibTeX style</a>”. </ul> -<p/>Of course, these pages don’t cover everything; the problem the +<p/>Of course, these pages don’t cover everything; the problem the inquisitive user faces, in fact, is to find what the various available -styles actually do. This is best achieved (if the links above don’t +styles actually do. This is best achieved (if the links above don’t help) by using <i>xampl.bib</i> from the BibTeX documentation distribution: one can get a pretty good feel for any style one has to -hand using this “standard” bibliography. For style +hand using this “standard” bibliography. For style <i>my-style.bst</i>, the simple LaTeX document: <blockquote> <pre> @@ -46,8 +46,8 @@ hand using this “standard” bibliography. For style </blockquote><p> will produce a representative sample of the citations the style will produce. (Because <i>xampl.bib</i> is so extreme in some of its -“examples”, the BibTeX run will also give you an interesting -selection of BibTeX’s error messages…) +“examples”, the BibTeX run will also give you an interesting +selection of BibTeX’s error messages…) <dl> <dt><tt><i>xampl.bib</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/xampl.bib">biblio/bibtex/distribs/doc/xampl.bib</a> </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html index 275f5b60c95..6beb24750c6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatenc.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label whatenc</title> </head><body> <h3>What are encodings?</h3> -<p/>Let’s start by defining two concepts, the <em>character</em> and the +<p/>Let’s start by defining two concepts, the <em>character</em> and the <em>glyph</em>. -The character is the abstract idea of the ‘atom’ of a +The character is the abstract idea of the ‘atom’ of a language or other dialogue: so it might be a letter in an alphabetic language, a syllable in a syllabic language, or an ideogram in an ideographic language. The glyph is the mark created on screen or @@ -12,7 +12,7 @@ paper which represents a character. Of course, if reading is to be possible, there must be some agreed relationship between the glyph and the character, so while the precise shape of the glyph can be affected by many other factors, such as the -capabilities of the writing medium and the designer’s style, the +capabilities of the writing medium and the designer’s style, the essence of the underlying character must be retained. <p/>Whenever a computer has to represent characters, someone has to define the relationship between a set of numbers and the characters they @@ -28,13 +28,13 @@ terminals that produced all sorts of odd characters, and as a result TeX contains some provision for translating the input encoding to something regular. Nowadays, the operating system translates keystrokes into a code appropriate for -the user’s language: the encoding used is often a national or -international standard, though many operating systems use “code -pages” defined by Microsoft. These standards and code pages often -contain characters that can’t appear in the TeX system’s input -stream. Somehow, these characters have to be dealt with — so -an input character like “é” needs to be interpreted by TeX in -a way that that at least mimics the way it interprets “<code>\</code><code>’</code><code>e</code>”. +the user’s language: the encoding used is often a national or +international standard, though many operating systems use “code +pages” defined by Microsoft. These standards and code pages often +contain characters that can’t appear in the TeX system’s input +stream. Somehow, these characters have to be dealt with — so +an input character like “é” needs to be interpreted by TeX in +a way that that at least mimics the way it interprets “<code>\</code><code>’</code><code>e</code>”. <p/>The TeX output stream is in a somewhat different situation: characters in it are to be used to select glyphs from the fonts to be used. Thus the encoding of the output stream is notionally a font @@ -52,14 +52,14 @@ of the input such as ligatures like appeared, because of the possibility of suppressing <code>\</code><code>accent</code> commands in the output stream (and hence improving the quality of the hyphenation of text in inflected languages, which is -interrupted by the <code>\</code><code>accent</code> commands — see +interrupted by the <code>\</code><code>accent</code> commands — see -<a href="FAQ-hyphen.html">“how does hyphenation work”</a>). +<a href="FAQ-hyphen.html">“how does hyphenation work”</a>). To take advantage of the diacriticised characters represented in the fonts, it is necessary to arrange that whenever the -command sequence “<code>\</code><code>’</code><code>e</code>” has been input +command sequence “<code>\</code><code>’</code><code>e</code>” has been input (explicitly, or implicitly via the sort of mapping of input mentioned -above), the character that codes the position of the “é” glyph is +above), the character that codes the position of the “é” glyph is used. <p/>Thus we could have the odd arrangement that the diacriticised character in the TeX input stream is translated into TeX commands that would @@ -70,8 +70,8 @@ precisely what the LaTeX packages <i>inputenc</i> and <i>fontenc</i> do, if operated in tandem on (most) characters in the ISO Latin-1 input encoding and the T1 font encoding. At first sight, it seems eccentric to have the first package do a thing, and -the second precisely undo it, but it doesn’t always happen that way: -most font encodings can’t match the corresponding input encoding +the second precisely undo it, but it doesn’t always happen that way: +most font encodings can’t match the corresponding input encoding nearly so well, and the two packages provide the sort of symmetry the LaTeX system needs. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatmacros.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatmacros.html index f37343a9096..e296254d6cb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatmacros.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatmacros.html @@ -3,33 +3,33 @@ </head><body> <h3>What are (TeX) macros</h3> <p/>TeX is a <em>macro processor</em>: this is a computer-science-y term -meaning “text expander” (more or less); TeX typesets text as it -goes along, but <em>expands</em> each macro it finds. TeX’s macros +meaning “text expander” (more or less); TeX typesets text as it +goes along, but <em>expands</em> each macro it finds. TeX’s macros may include instructions to TeX itself, on top of the simple text generation one might expect. <p/>Macros are a <em>good thing</em>, since they allow the user to manipulate documents according to context. For example, the macro -<code>\</code><code>TeX</code> is usually defined to produce “TEX” with the ‘E’ lowered, +<code>\</code><code>TeX</code> is usually defined to produce “TEX” with the ‘E’ lowered, but in these FAQs the default definition of the macro is -overridden, and it simply expands to the letters “TeX”. (<em>You</em> +overridden, and it simply expands to the letters “TeX”. (<em>You</em> may not think this a good thing, but the author of the macros has his -reasons – see <a href="FAQ-logos.html">TeX-related logos</a>.) +reasons – see <a href="FAQ-logos.html">TeX-related logos</a>.) <p/>Macro names are conventionally built from a <code>\</code> followed by a sequence of letters, which may be upper or lower case (as in <code>\</code><code>TeX</code>, mentioned above). They may also be <code>\<<i>any single character</i>></code>, which allows all sorts of oddities (many built in to most TeX macro sets, all the -way up from the apparently simple ‘<code>\</code><code> </code>’ meaning “insert a space -here”). +way up from the apparently simple ‘<code>\</code><code> </code>’ meaning “insert a space +here”). <p/>Macro programming can be a complicated business, but at their very -simplest they need little introduction — you’ll hardly need to be +simplest they need little introduction — you’ll hardly need to be told that: <blockquote> <pre> \def\foo{bar} </pre> </blockquote><p> -replaces each instance of <code>\</code><code>foo</code> with the text “bar”. The +replaces each instance of <code>\</code><code>foo</code> with the text “bar”. The command <code>\</code><code>def</code> is Plain TeX syntax for defining commands; LaTeX offers a macro <code>\</code><code>newcommand</code> that goes some way towards protecting users from themselves, but basically does the same thing: @@ -38,7 +38,7 @@ protecting users from themselves, but basically does the same thing: \newcommand{\foo}{bar} </pre> </blockquote><p> -Macros may have “arguments”, which are used to substitute for marked +Macros may have “arguments”, which are used to substitute for marked bits of the macro expansion: <blockquote> <pre> @@ -57,7 +57,7 @@ or, in LaTeX speak: </blockquote><p> Macro writing can get very complicated, very quickly. If you are a beginner (La)TeX programmer, you are well advised to read something -along the lines of the <a href="FAQ-books.html">TeXbook</a>; once you’re under +along the lines of the <a href="FAQ-books.html">TeXbook</a>; once you’re under way, <a href="FAQ-ol-books.html">TeX by Topic</a> is possibly a more satisfactory choice. Rather a lot of the answers in these FAQs tell you about various issues of how to write macros. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html index 15d32cd9f7b..0fcaa7a4a48 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatpdftex.html @@ -17,16 +17,16 @@ detail (for example, its support for but its greatest impact to date has been in the area of PDF output. -<p/>PDFTeX started as a topic for Hàn The Thành’s Master’s thesis, +<p/>PDFTeX started as a topic for Hàn The Thành’s Master’s thesis, and seems first to have been published in <i>TUGboat</i> 18(4), in 1997 -(though it was certainly discussed at the TUG’96 conference in +(though it was certainly discussed at the TUG’96 conference in Russia). -<p/>While the world was making good use of “pre-releases” of PDFTeX, -Thành used it as a test-bed for the micro-typography which was the -prime subject of his Ph.D. research. Since Thành was finally +<p/>While the world was making good use of “pre-releases” of PDFTeX, +Thành used it as a test-bed for the micro-typography which was the +prime subject of his Ph.D. research. Since Thành was finally awarded his Ph.D., day-to-day maintenance and development of PDFTeX 1.0 (and later) has been in the hands of a group of -PDFTeX maintainers (which includes Thành); the group has managed +PDFTeX maintainers (which includes Thành); the group has managed to maintain a stable platform for general use. <p/>Development of PDFTeX has (in essence) stopped: the brave new world is to be <a href="FAQ-luatex.html">LuaTeX</a>. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html index f0c97ef8a1d..b5ca003d74b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label whereFAQ</title> </head><body> <h3>Where to find FAQs</h3> -<p/>Bobby Bodenheimer’s article, from which this FAQ was developed, used +<p/>Bobby Bodenheimer’s article, from which this FAQ was developed, used to be posted (nominally monthly) to newsgroup <i>comp.text.tex</i>. The (long obsolete) last posted copy of that article is kept on CTAN for @@ -12,9 +12,9 @@ auld lang syne. The sources of the present FAQ are available from CTAN. <p/>This FAQ and others are regularly mentioned, on -<i>comp.text.tex</i> and elsewhere, in a “pointer FAQ” +<i>comp.text.tex</i> and elsewhere, in a “pointer FAQ” which is also saved at <a href="http://tug.org/tex-ptr-faq">http://tug.org/tex-ptr-faq</a> -<p/>A 2006 innovation from Scott Pakin is the “visual” LaTeX FAQ. +<p/>A 2006 innovation from Scott Pakin is the “visual” LaTeX FAQ. This is a document with (mostly rubbish) text formatted so as to highlight things we discuss here, and providing Acrobat hyper-links to the relevant answers in this FAQ on the Web. The visual @@ -26,11 +26,11 @@ missing with other readers, or with earlier versions of Acrobat Reader <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 +<p/>Herbert Voss’s excellent <a href="http://texnik.de/">LaTeX tips and tricks</a> provides excellent advice on most topics one might imagine (though -it’s not strictly a FAQ) — highly recommended for most -ordinary mortals’ use. +it’s not strictly a FAQ) — highly recommended for most +ordinary mortals’ use. <p/>The Open Directory Project (ODP) maintains a list of sources of (La)TeX help, including FAQs. View the TeX area at <a href="http://dmoz.org/Computers/Software/Typesetting/TeX/">http://dmoz.org/Computers/Software/Typesetting/TeX/</a> @@ -44,7 +44,7 @@ ordinary mortals’ use. A FAQ used to be posted regularly to - <i>fr.comp.text.tex</i>, and is archived on CTAN — + <i>fr.comp.text.tex</i>, and is archived on CTAN — sadly, that effort seems to have fallen by the wayside. <dt>Czech<dd>See <a href="http://www.fi.muni.cz/cstug/csfaq/">http://www.fi.muni.cz/cstug/csfaq/</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html index 77005140f8a..4eb048e3b2d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html @@ -15,15 +15,15 @@ than columns. So, we set things up by: <pre> \usepackage{array} -\newcolumntype{$}{>{\global\let\currentrowstyle\relax}} -\newcolumntype{^}{>{\currentrowstyle}} +\newcolumntype{$}{>{\global\let\currentrowstyle\relax}} +\newcolumntype{^}{>{\currentrowstyle}} \newcommand{\rowstyle}[1]{\gdef\currentrowstyle{#1}% #1\ignorespaces } </pre> </blockquote><p> -Now, we put ‘<code>$</code>’ before the first column specifier; and we -put ‘<code>textasciicircum</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> @@ -41,10 +41,10 @@ the start of each row we want to modify: </blockquote><p> The <i>array</i> package works with several other <code>tabular</code>-like environments from other packages (for -example <code>longtable</code>), but unfortunately this trick won’t +example <code>longtable</code>), but unfortunately this trick won’t always work. <dl> -<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/array.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html index 461dd6b7b60..d52ec418c6a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html @@ -3,29 +3,29 @@ </head><body> <h3>Why bother with <i>inputenc</i> and <i>fontenc</i>?</h3> <p/>The standard input encoding for Western Europe (pending the arrival of -Unicode) is ISO 8859–1 (commonly known by the standard’s -subtitle ‘Latin-1’). Latin-1 is remarkably close, in the codepoints +Unicode) is ISO 8859–1 (commonly known by the standard’s +subtitle ‘Latin-1’). Latin-1 is remarkably close, in the codepoints it covers, to the (La)TeX T1 encoding. <p/>In this circumstance, why should one bother with <i>inputenc</i> -and <i>fontenc</i>? Since they’re pretty exactly mirroring each +and <i>fontenc</i>? Since they’re pretty exactly mirroring each other, one could do away with both, and use just <i>t1enc</i>, despite its <a href="FAQ-t1enc.html">shortcomings</a>. -<p/>One doesn’t do this for a variety of small reasons: +<p/>One doesn’t do this for a variety of small reasons: <dl> -<dt>Confusion<dd> You’ve been happily working in this mode, and for - some reason find you’re to switch to writing in German: the effect - of using “<code>ß</code>” is somewhat startling, since T1 +<dt>Confusion<dd> You’ve been happily working in this mode, and for + some reason find you’re to switch to writing in German: the effect + of using “<code>ß</code>” is somewhat startling, since T1 and Latin-1 treat the codepoint differently. <dt>Compatibility<dd> You find yourself needing to work with a colleague in Eastern Europe: their keyboard is likely to be set to - produce Latin-2, so that the simple mapping doesn’t work. + produce Latin-2, so that the simple mapping doesn’t work. <dt>Traditional LaTeX<dd> You lapse and write something like - <code>\’</code><code>e</code> rather than typing <code>é</code>; only <i>fontenc</i> + <code>\’</code><code>e</code> rather than typing <code>é</code>; only <i>fontenc</i> has the means to convert this LaTeX sequence into the T1 character, so an <code>\</code><code>accent</code> primitive slips through into the output, and hyphenation is in danger. </dl> -The <i>inputenc</i>–<i>fontenc</i> combination seems slow and -cumbersome, but it’s safe. +The <i>inputenc</i>–<i>fontenc</i> combination seems slow and +cumbersome, but it’s safe. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html index 64e06c868c6..0938e60923b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whyfree.html @@ -1,20 +1,20 @@ <head> <title>UK TeX FAQ -- question label whyfree</title> </head><body> -<h3>If TeX is so good, how come it’s free?</h3> -<p/>It’s free because Knuth chose to make it so. He is nevertheless +<h3>If TeX is so good, how come it’s free?</h3> +<p/>It’s free because Knuth chose to make it so. He is nevertheless apparently happy that others should earn money by selling TeX-based services and products. While several valuable TeX-related tools and packages are offered subject to restrictions imposed by the GNU General Public -Licence (‘Copyleft’), TeX itself is not subject to Copyleft. +Licence (‘Copyleft’), TeX itself is not subject to Copyleft. <p/>There are commercial versions of TeX available; for some users, -it’s reassuring to have paid support. What is more, some of the +it’s reassuring to have paid support. What is more, some of the commercial implementations have features that are not available in free versions. (The reverse is also true: some free implementations have features not available commercially.) -<p/>This FAQ concentrates on ‘free’ distributions of TeX, but we +<p/>This FAQ concentrates on ‘free’ distributions of TeX, but we do at least list the <a href="FAQ-commercial.html">major vendors</a>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html index ecc75a165d8..c7624bcc303 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widefigs.html @@ -3,13 +3,13 @@ </head><body> <h3>Wide figures in two-column documents</h3> <p/>Floating figures and tables ordinarily come out the same width as the -page, but in two-column documents they’re restricted to the width of +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, +versions of the float environments — in two-column documents, <code>figure*</code> provides a floating page-wide figure (and <code>table*</code> a page-wide table) which will do the necessary. -<p/>The “<code>*</code>”ed float environments can only appear at the top of a page, -or on a whole page — <code>h</code> or <code>b</code> float placement directives are +<p/>The “<code>*</code>”ed float environments can only appear at the top of a page, +or on a whole page — <code>h</code> or <code>b</code> float placement directives are simply ignored. <p/>Unfortunately, page-wide equations can only be accommodated inside float environments. You should include them in <code>figure</code> environments, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wideflt.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wideflt.html index 49e24031d72..5518fe2e724 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wideflt.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wideflt.html @@ -3,15 +3,15 @@ </head><body> <h3>Centring a very wide figure or table</h3> <p/>The normal means of centring a figure or table object is to include -<code>\</code><code>centering</code> at the top of the float. This doesn’t help if the -object is wider than <code>\</code><code>textwidth</code> — the object starts at the left +<code>\</code><code>centering</code> at the top of the float. This doesn’t help if the +object is wider than <code>\</code><code>textwidth</code> — the object starts at the left margin and juts out into the right margin (which is actually doubly -unsatisfactory, since as well as looking bad, the float won’t be +unsatisfactory, since as well as looking bad, the float won’t be placed until the next <code>\</code><code>clearpage</code> or the like.) <p/>You can avoid the problem by rescaling the figure or table to fit, but this is often not satisfactory, for several reasons. <p/>Otherwise, if the object is wider than the printable area of the page, -you’ve no choice other than to <a href="FAQ-landscape.html">rotate it</a>. If, +you’ve no choice other than to <a href="FAQ-landscape.html">rotate it</a>. If, however, the object is <em>just</em> wider than the text block, you can make it pretend to be the right size by: <blockquote> @@ -25,6 +25,6 @@ make it pretend to be the right size by: </blockquote><p> Note the <code>\</code><code>noindent</code>: the <code>\</code><code>makebox</code> starts a paragraph, and you -really don’t want that indented by <code>\</code><code>parindent</code>. +really don’t want that indented by <code>\</code><code>parindent</code>. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wideflt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wideflt</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html index 357ae7d857e..d7d4d242d4e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-widows.html @@ -4,7 +4,7 @@ <h3>Controlling widows and orphans</h3> <p/>Widows (the last line of a paragraph at the start of a page) and orphans (the first line of paragraph at the end of a page) interrupt -the reader’s flow, and are generally considered “bad form”; +the reader’s flow, and are generally considered “bad form”; (La)TeX takes some precautions to avoid them, but completely automatic prevention is often impossible. If you are typesetting your own text, consider whether you can bring yourself to change the @@ -19,7 +19,7 @@ stretchability or shrinkability, so if the page maker has to balance the effect of stretching the unstretchable and being penalised, the penalty will seldom win. Therefore, for typical layouts, there are only two sensible settings for the penalties: finite (150 or 500, it -doesn’t matter which) to allow widows and orphans, and infinite (10000 +doesn’t matter which) to allow widows and orphans, and infinite (10000 or greater) to forbid them. <p/>The problem can be avoided by allowing the pagemaker to run pages short, by using the <code>\</code><code>raggedbottom</code> @@ -27,21 +27,21 @@ directive; however, many publishers insist on the default <code>\</code><code>flushbottom</code>; it is seldom acceptable to introduce stretchability into the vertical list, except at points (such as section headings) where the document design explicitly permits it. -<p/>Once you’ve exhausted the automatic measures, and have a final draft -you want to “polish”, you should proceed to manual measures. To +<p/>Once you’ve exhausted the automatic measures, and have a final draft +you want to “polish”, you should proceed to manual measures. To get rid of an orphan is simple: precede the paragraph with -<code>\</code><code>clearpage</code> and the paragraph can’t start in the wrong place. +<code>\</code><code>clearpage</code> and the paragraph can’t start in the wrong place. <p/>Getting rid of a widow can be more tricky. If the paragraph is a long -one, it may be possible to set it ‘tight’: say <code>\</code><code>looseness</code><code>=-1</code> -immediately after the last word of the paragraph. If that doesn’t +one, it may be possible to set it ‘tight’: say <code>\</code><code>looseness</code><code>=-1</code> +immediately after the last word of the paragraph. If that doesn’t work, try adjusting the page size: <code>\</code><code>enlargethispage{<code>\</code><code>baselineskip</code>}</code> may do the job, and get the whole paragraph on one page. Reducing the size of the page by <code>\</code><code>enlargethispage{-<code>\</code><code>baselineskip</code>}</code> may produce a -(more-or-less) acceptable “two-line widow”. (Note: +(more-or-less) acceptable “two-line widow”. (Note: <code>\</code><code>looseness</code><code>=1</code>, -increasing the line length by one, seldom seems to work — the looser -paragraph typically has a one-word final line, which doesn’t look much +increasing the line length by one, seldom seems to work — the looser +paragraph typically has a one-word final line, which doesn’t look much better than the straight widow.) <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html index 0087b886837..52902737d54 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wordcount.html @@ -13,17 +13,17 @@ method can be employed: find how many words there are on a full page; find how many full pages there are in the document (allowing for displays of various sorts, this number will probably not be an integer); multiply the two. However, if the document to be submitted -is to determine the success of the rest of one’s life, it takes a +is to determine the success of the rest of one’s life, it takes a brave person to thumb their nose at authority quite so -comprehensively… +comprehensively… <p/>The simplest method is to strip out the (La)TeX markup, and to count -what’s left. On a Unix-like system, this may be done using +what’s left. On a Unix-like system, this may be done using <i>detex</i> and the built-in <i>wc</i>: <pre> - detex <filename> | wc -w + detex <filename> | wc -w </pre> The <i>latexcount</i> script does the same sort of job, in one -“step”; being a <i>perl</i> script, it is in principle rather +“step”; being a <i>perl</i> script, it is in principle rather easily configured (see documentation inside the script). <i>Winedt</i> (see <a href="FAQ-editors.html">editors and shells</a>) provides this functionality direct in the Windows environment. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html index f709a5c325c..940b0fc11dc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-writecls.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label writecls</title> </head><body> <h3>Learning to write LaTeX classes and packages</h3> -<p/>There’s nothing particularly magic about the commands you use when +<p/>There’s nothing particularly magic about the commands you use when writing a package, so you can simply bundle up a set of LaTeX <code>\</code><code>(re)newcommand</code> and <code>\</code><code>(re)newenvironment</code> commands, put them in a file <i>package.sty</i> and you have a package. <p/>However, any but the most trivial package will require rather more sophistication. Some details of LaTeX commands for the job are to -be found in ‘LaTeX2e for class and package writers’ +be found in ‘LaTeX2e for class and package writers’ (<i>clsguide</i>, part of the LaTeX documentation distribution). Beyond this, a good knowledge of TeX itself is valuable: thus books such as the <a href="FAQ-books.html">TeXbook</a> or @@ -23,12 +23,12 @@ PDF version, which is in the file <i>base.tds.zip</i> of his <i>latex-tds</i> distribution. Individual files in the LaTeX distribution may be processed separately with LaTeX, like any well-constructed <a href="FAQ-dtx.html"><code>.dtx</code> file</a>. -<p/>Writing good classes is not easy; it’s a good idea to read some +<p/>Writing good classes is not easy; it’s a good idea to read some established ones (<i>classes.dtx</i>, for example, is the documented source of the standard classes other than <i>Letter</i>, and may itself be formatted with LaTeX). Classes that are not part of the distribution are commonly based on ones that are, and start by loading -the standard class with <code>\</code><code>LoadClass</code> — an example of this +the standard class with <code>\</code><code>LoadClass</code> — an example of this technique may be seen in <i>ltxguide.cls</i> <p/>An <a href="http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf">annotated version of <i>article</a></i>, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html index 9acc7076e44..abecfe48cf7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wrongpn.html @@ -3,22 +3,22 @@ </head><body> <h3>Page number is wrong at start of page</h3> <p/>This is a long story, whose sources are deep inside the workings of -TeX itself; it all derives from the TeX’s striving to generate +TeX itself; it all derives from the TeX’s striving to generate the best possible output. <p/>The page number is conventionally stored in <code>\</code><code>count0</code>; LaTeX users see this as the counter <code>page</code>, and may typeset its value using <code>\</code><code>thepage</code>. <p/>The number (that is to say, <code>\</code><code>count0</code>) is only updated when TeX actually outputs a page. TeX only even tries to do this when it -detects a hint that it may be a good thing to do. From TeX’s point +detects a hint that it may be a good thing to do. From TeX’s point of view, the end of a paragraph is a good time to consider outputting -a page; it will output a page if it has <em>more</em> than a page’s +a page; it will output a page if it has <em>more</em> than a page’s worth of material to output. (Ensuring it always has something in hand makes some optimisations possible.) As a result, <code>\</code><code>count0</code> (<code>\</code><code>thepage</code>) is almost always wrong in the first paragraph of a -page (the exception is where the page number has been “forcibly” +page (the exception is where the page number has been “forcibly” changed, either by changing its value directly, or by breaking the -page where TeX wouldn’t necessarily have chosen to break). +page where TeX wouldn’t necessarily have chosen to break). <p/>LaTeX provides a safe way of referring to the page number, by using label references. So, rather than writing: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xfigetc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xfigetc.html index e56861e665f..f8d8773b0e2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xfigetc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xfigetc.html @@ -10,8 +10,8 @@ Encapsulated PostScript and PDF, as well as combinations that wrap a graphics format in a LaTeX import file, which may include LaTeX commands to place text (compiled by LaTeX itself) as labels, etc., in the figures. -<p/>There’s no explicit port of <i>xfig</i> to windows (although it is -said to work under <i>cygwin</i> with their X-windows system — +<p/>There’s no explicit port of <i>xfig</i> to windows (although it is +said to work under <i>cygwin</i> with their X-windows system — <a href="http://www.cs.usask.ca/~wew036/latex/xfig.html">installation advice</a> is available). However, the program @@ -20,7 +20,7 @@ is thought by many to be an acceptable substitute, written in Java. <p/><i>Asymptote</i> is a widely-praised development of the MetaPost language, which can draw 2D or 3D diagrams, and can also label diagrams with LaTeX text; copious documentation is available via -<a href="http://asymptote.sourceforge.net"><i>asymptote</a>’s web site</i>. +<a href="http://asymptote.sourceforge.net"><i>asymptote</a>’s web site</i>. <dl> <dt><tt><i>asymptote</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/graphics/asymptote.zip">graphics/asymptote</a> (or <a href="http://www.tex.ac.uk/tex-archive/graphics/asymptote/">browse the directory</a>) <dt><tt><i>xfig</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/graphics/xfig/">graphics/xfig/</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html index cb6d878c84a..8a9722a3adf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-xspace.html @@ -5,7 +5,7 @@ <p/>People are forever surprised that simple commands gobble the space after them: this is just the way it is. The effect arises from the way TeX works, and Lamport describes a solution (place a pair of braces -after a command’s invocation) in the description of LaTeX syntax. +after a command’s invocation) in the description of LaTeX syntax. Thus the requirement is in effect part of the definition of LaTeX. <p/>This FAQ, for example, is written with definitions that <em>require</em> one to @@ -16,17 +16,17 @@ of whether the following space is required: however, this FAQ is written by highly dedicated (and, some would say, eccentric) people. Many users find all those braces become very tedious very quickly, and would really rather not type them all. -<p/>An alternative structure, that doesn’t violate the design of LaTeX, -is to say <code>\</code><code>fred</code><code>\</code><code> </code> — the <code>\</code><code> </code> command is “self -terminating” (like <code>\</code><code>\</code>) and you don’t need braces after +<p/>An alternative structure, that doesn’t violate the design of LaTeX, +is to say <code>\</code><code>fred</code><code>\</code><code> </code> — the <code>\</code><code> </code> command is “self +terminating” (like <code>\</code><code>\</code>) and you don’t need braces after <em>it</em>. Thus one can reduce to one the extra characters one needs to type. <p/>If even that one character is too many, the package <i>xspace</i> defines a command <code>\</code><code>xspace</code> that guesses whether there should have been a space after it, and if so introduces that space. So -“<code>fred<code>\</code><code>xspace</code> jim</code>” produces “fred jim”, while -“<code>fred<code>\</code><code>xspace</code>. jim</code>” produces “fred. jim”. Which +“<code>fred<code>\</code><code>xspace</code> jim</code>” produces “fred jim”, while +“<code>fred<code>\</code><code>xspace</code>. jim</code>” produces “fred. jim”. Which usage would of course be completely pointless; but you can incorporate <code>\</code><code>xspace</code> in your own macros: <blockquote> @@ -40,17 +40,17 @@ and we find \restenergy available to us... </blockquote><p> The <code>\</code><code>xspace</code> command must be the last thing in your macro -definition (as in the example); it’s not completely foolproof, but it +definition (as in the example); it’s not completely foolproof, but it copes with most obvious situations in running text. -<p/>The <i>xspace</i> package doesn’t save you anything if you only use +<p/>The <i>xspace</i> package doesn’t save you anything if you only use a modified macro once or twice within your document. In any case, be -careful with usage of <code>\</code><code>xspace</code> — it changes your input syntax, +careful with usage of <code>\</code><code>xspace</code> — it changes your input syntax, which can be confusing, notably to a collaborating author (particularly if you create some commands which use it and some which -don’t). Of course, no command built into LaTeX or into any -“standard” class or package will use <code>\</code><code>xspace</code>. +don’t). Of course, no command built into LaTeX or into any +“standard” class or package will use <code>\</code><code>xspace</code>. <dl> -<dt><tt><i>xspace.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>) +<dt><tt><i>xspace.sty</i></tt><dd>Distributed as part of <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse the directory</a>); <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/entries/xspace.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html index b82b4ae7604..2f9b71c3c29 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-y2k.html @@ -20,10 +20,10 @@ implementation (see <a href="FAQ-triptrap.html">trip/trap testing</a>) does not require that <code>\</code><code>year</code> return a meaningful value (which means that TeX can, in principle, be implemented on platforms - that don’t make the value of the clock available to user programs). + that don’t make the value of the clock available to user programs). The <em>TeXbook</em> (see <a href="FAQ-books.html">TeX-related books</a>) defines <code>\</code><code>year</code> as - “the current year of our Lord”, which is the only correct meaning + “the current year of our Lord”, which is the only correct meaning for <code>\</code><code>year</code> for those implementations which can supply a meaningful value, which is to say nearly all of them. <p/> In short, TeX implementations should provide a value in <code>\</code><code>year</code> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html index 515140827cb..e8516ea083f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html @@ -1,18 +1,18 @@ <head> <title>UK TeX FAQ -- question label zerochap</title> </head><body> -<h3>Why are my sections numbered 0.1 …?</h3> +<h3>Why are my sections numbered 0.1 …?</h3> <p/>This happens when your document is using the standard <i>book</i> or -<i>report</i> class (or one similar), and you’ve got a <code>\</code><code>section</code> +<i>report</i> class (or one similar), and you’ve got a <code>\</code><code>section</code> before your first <code>\</code><code>chapter</code>. <p/>What happens is, that the class numbers sections as -“<<i>chapter no</i>>.<<i>section no</i>>”, and until the first +“<<i>chapter no</i>>.<<i>section no</i>>”, and until the first chapter has appeared, the chapter number is 0. -<p/>If you’re doing this, it’s quite likely that the <i>article</i> class +<p/>If you’re doing this, it’s quite likely that the <i>article</i> class is for you; try it and see. Otherwise, give your sections a -‘superior’ chapter, or do away with section numbering by using +‘superior’ chapter, or do away with section numbering by using <code>\</code><code>section*</code> instead. An alternative way of avoiding numbering is discussed in -“<a href="FAQ-secnumdep.html">unnumbered sections in the table of contents</a>”. +“<a href="FAQ-secnumdep.html">unnumbered sections in the table of contents</a>”. <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/index.html b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html index bf87cb025fd..c403c5952d3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/index.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html @@ -15,142 +15,47 @@ covered from the viewpoint of a LaTeX user. <ul> <li> by reading a printed document, <li> by viewing a PDF file, with hyperlinks to assist - browsing: copies are available formatted for printing on - <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/newfaq.pdf">A4 paper</a> or on - <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/letterfaq.pdf">North American “letter” paper</a>, or -<li> by using the FAQ’s web interface (base URL: - <a href="http://www.tex.ac.uk/faq">http://www.tex.ac.uk/faq</a>); this version provides simple - search capabilities, as well as a link to Google for a more - sophisticated search restricted to the FAQ itself, or -<li> via Scott Pakin’s <a href="http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf">Visual FAQ</a>, which shows - LaTeX constructions with links to FAQ details of how they - were created. + browsing: copies are available formatted so that they could be + printed on <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/newfaq.pdf">A4 paper</a> or on + <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/letterfaq.pdf">North American “letter” paper</a>, or + +<li> via Scott Pakin’s <a href="http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf">Visual FAQ</a>, which shows + LaTeX constructions with links to FAQ explanations of how + they may be created. </ul> <p/> -<p/>Unless otherwise specified, all files mentioned in this FAQ -are available from a CTAN archive, or from a mirror of -CTAN — see <a href="FAQ-archives.html">later discussion</a> - of the CTAN -archives and how to retrieve files -from them. If you don’t have access to the internet, the -<a href="FAQ-CD.html">TeX Live distribution</a> offers off-line snapshots of the -archives. -<p/>The reader should also note that the first directory name of the -path name of every file on CTAN is omitted from what -follows, for the simple reason that, while it’s always the same -(<i>tex-archive/</i>) on the main sites, mirror sites often choose -something else. -<p/>To avoid confusion, we also omit the full stop from the end of -any sentence whose last item is a path name (such sentences are -rare, and only occur at the end of paragraphs). Though the path -names are set in a different font from running text, it’s not easy -to distinguish the font of a single dot! +<p/> +Almost all files suggested in answers in these FAQs are +available from <a href="FAQ-archives.html">CTAN archives</a>, and may be +reached via links in the file list at the end of the answer. In +particular, documentation (when available) is linked from the +CTAN Catalogue entry, which is also listed in the file list. +<p/>Unless doing so is unavoidable, the answers do not mention things not +on the archive. An obvious exception is web resources such as +supplementary documents, etc. <p/><b>Origins</b> <p/>The FAQ was originated by the Committee of the UK -TeX Users’ Group (UK TUG) as a development of a +TeX Users’ Group (UK TUG) as a development of a regular posting to the <em>Usenet</em> newsgroup <i>comp.text.tex</i> that was maintained for some time by Bobby Bodenheimer. The first UK version was much re-arranged and -corrected from the original, and little of Bodenheimer’s work now +corrected from the original, and little of Bodenheimer’s work now remains. -<p/>The following people (at least — there are almost certainly others -whose names weren’t correctly recorded) have contributed help or -advice on the development of the FAQ: Donald Arseneau, -Rosemary Bailey, -Barbara Beeton, -Karl Berry, -Giuseppe Bilotta, -Charles Cameron, -François Charette, -Damian Cugley, -Michael Dewey, -Michael Downes, -Jean-Pierre Drucbert, -Michael Ernst, -Thomas Esser, -Ulrike Fischer, - -Anthony Goreham, -Norman Gray, -Eitan Gurari, -William Hammond, -John Harper, -John Hammond, -Troy Henderson, -Hartmut Henkel, -Stephan Hennig, -John Hobby, -Morten Høgholm, -Berthold Horn, -Ian Hutchinson, -Werner Icking, -William Ingram, -David Jansen, -Alan Jeffrey, -Regnor Jernsletten, -David Kastrup, -Oleg Katsitadze, -Isaac Khabaza, -Ulrich Klauer, -Markus Kohm, -Stefan Kottwitz -David Kraus, -Ryszard Kubiak, -Simon Law, -Uwe Lück, -Daniel Luecking, -Aditya Mahajan, -Sanjoy Mahajan, -Andreas Matthias, -Steve Mayer, -Brooks Moses, -Iain Murray, -Vilar Camara Neto, -Dick Nickalls, -Ted Nieland, -Hans Nordhaug, -Pat Rau, -Heiko Oberdiek, -Piet van Oostrum, -Scott Pakin, -Oren Patashnik, -Manuel Pégourié-Gonnard, -Steve Peter, -Sebastian Rahtz, -Philip Ratcliffe, -Chris Rowley, -José Carlos Santos, -Walter Schmidt, -Hans-Peter Schröcker, -Joachim Schrod, -Maarten Sneep, -Axel Sommerfeldt, -Philipp Stephani, -James Szinger, -Ulrik Vieth, -Mike Vulis, -Chris Walker, -Peter Wilson, -Joseph Wright, -Rick Zaccone and -Reinhard Zierke. -<p/>That list does <em>not</em> cover the many people whose ideas I have -encountered on various lists, newsgroups or (lately) web forums. Many -such people have helped me, perhaps simply to alert me to an area in -which I need to work. +<p/> <h3>The Background</h3><ul> <li><a href="FAQ-whatTeX.html">What is TeX?</a> -<li><a href="FAQ-TeXpronounce.html">How should I pronounce “TeX”?</a> +<li><a href="FAQ-plaintex.html">What’s “writing in TeX”?</a> +<li><a href="FAQ-TeXpronounce.html">How should I pronounce “TeX”?</a> <li><a href="FAQ-MF.html">What is Metafont?</a> <li><a href="FAQ-MP.html">What is MetaPost?</a> -<li><a href="FAQ-texthings.html">Things with “TeX” in the name</a> -<li><a href="FAQ-triptrap.html">How can I be sure it’s really TeX?</a> +<li><a href="FAQ-texthings.html">Things with “TeX” in the name</a> +<li><a href="FAQ-triptrap.html">How can I be sure it’s really TeX?</a> <li><a href="FAQ-y2k.html">Are TeX and friends Y2K compliant?</a> <li><a href="FAQ-etex.html">What is e-TeX?</a> <li><a href="FAQ-whatpdftex.html">What is PDFTeX?</a> <li><a href="FAQ-latex.html">What is LaTeX?</a> <li><a href="FAQ-latex2e.html">What is LaTeX2e?</a> -<li><a href="FAQ-latexpronounce.html">How should I pronounce “LaTeX(2e)”?</a> +<li><a href="FAQ-latexpronounce.html">How should I pronounce “LaTeX(2e)”?</a> <li><a href="FAQ-plainvltx.html">Should I use Plain TeX or LaTeX?</a> <li><a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX?</a> <li><a href="FAQ-context.html">What is ConTeXt?</a> @@ -158,7 +63,7 @@ which I need to work. <li><a href="FAQ-eplain.html">What is Eplain?</a> <li><a href="FAQ-lollipop.html">What is Lollipop?</a> <li><a href="FAQ-texinfo.html">What is Texinfo?</a> -<li><a href="FAQ-whyfree.html">If TeX is so good, how come it’s free?</a> +<li><a href="FAQ-whyfree.html">If TeX is so good, how come it’s free?</a> <li><a href="FAQ-TeXfuture.html">What is the future of TeX?</a> <li><a href="FAQ-readtex.html">Reading (La)TeX files</a> <li><a href="FAQ-notWYSIWYG.html">Why is TeX not a WYSIWYG system?</a> @@ -170,7 +75,7 @@ which I need to work. <li><a href="FAQ-gethelp.html">How to get help</a> <li><a href="FAQ-mailliststar.html">Specialist mailing lists</a> <li><a href="FAQ-askquestion.html">How to ask a question</a> -<li><a href="FAQ-minxampl.html">How to make a “minimum example”</a> +<li><a href="FAQ-minxampl.html">How to make a “minimum example”</a> <li><a href="FAQ-tutorialstar.html">(La)TeX Tutorials, etc.</a> <li><a href="FAQ-man-tex.html">Online introductions: Plain TeX</a> <li><a href="FAQ-man-latex.html">Online introductions: LaTeX</a> @@ -184,7 +89,7 @@ which I need to work. <li><a href="FAQ-writecls.html">Learning to write LaTeX classes and packages</a> <li><a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a> <li><a href="FAQ-BibTeXing.html">BibTeX Documentation</a> -<li><a href="FAQ-symbols.html">Where can I find the symbol for …</a> +<li><a href="FAQ-symbols.html">Where can I find the symbol for …</a> <li><a href="FAQ-docpictex.html">The PicTeX manual</a> </ul><h3>Bits and pieces of (La)TeX</h3><ul> <li><a href="FAQ-dvi.html">What is a DVI file?</a> @@ -200,10 +105,10 @@ which I need to work. <li><a href="FAQ-whatenc.html">What are encodings?</a> <li><a href="FAQ-ECfonts.html">What are the EC fonts?</a> <li><a href="FAQ-tds.html">What is the TDS?</a> -<li><a href="FAQ-eps.html">What is “Encapsulated PostScript” (“EPS”)?</a> +<li><a href="FAQ-eps.html">What is “Encapsulated PostScript” (“EPS”)?</a> <li><a href="FAQ-adobetypen.html">Adobe font formats</a> -<li><a href="FAQ-resolns.html">What are “resolutions”?</a> -<li><a href="FAQ-fontname.html">What is the “Berry naming scheme”?</a> +<li><a href="FAQ-resolns.html">What are “resolutions”?</a> +<li><a href="FAQ-fontname.html">What is the “Berry naming scheme”?</a> </ul><h3>Acquiring the Software</h3><ul> <li><a href="FAQ-archives.html">Repositories of TeX material</a> <li><a href="FAQ-tds-zip.html">Ready-built installation files on the archive</a> @@ -219,7 +124,7 @@ which I need to work. </ul><h3>DVI Drivers and Previewers</h3><ul> <li><a href="FAQ-dvips.html">DVI to PostScript conversion programs</a> <li><a href="FAQ-HPdrivers.html">DVI drivers for HP LaserJet</a> -<li><a href="FAQ-otherprinters.html">Output to “other” printers</a> +<li><a href="FAQ-otherprinters.html">Output to “other” printers</a> <li><a href="FAQ-previewers.html">DVI previewers</a> <li><a href="FAQ-dvi-bmp.html">Generating bitmaps from DVI</a> </ul><h3>Support Packages for TeX</h3><ul> @@ -243,15 +148,15 @@ which I need to work. <li><a href="FAQ-install-find.html">Finding packages to install</a> <li><a href="FAQ-install-unpack.html">Unpacking LaTeX packages</a> <li><a href="FAQ-install-doc.html">Generating package documentation</a> -<li><a href="FAQ-inst-wlcf.html">Installing files “where (La)TeX can find them”</a> +<li><a href="FAQ-inst-wlcf.html">Installing files “where (La)TeX can find them”</a> <li><a href="FAQ-what-TDS.html">Which tree to use</a> <li><a href="FAQ-install-where.html">Where to install packages</a> <li><a href="FAQ-inst-tidy.html">Tidying up after installation</a> <li><a href="FAQ-inst-scut.html">Shortcuts to installing files</a> <li><a href="FAQ-inst-miktexstar.html">Installation using MiKTeX package manager</a> <li><a href="FAQ-inst-tds-zip.html">Installing using ready-built ZIP files</a> -<li><a href="FAQ-tempinst.html">“Temporary” installation of (La)TeX files</a> -<li><a href="FAQ-privinst.html">“Private” installations of files</a> +<li><a href="FAQ-tempinst.html">“Temporary” installation of (La)TeX files</a> +<li><a href="FAQ-privinst.html">“Private” installations of files</a> <li><a href="FAQ-instfont.html">Installing a new font</a> <li><a href="FAQ-instmffont.html">Installing a font provided as Metafont source</a> <li><a href="FAQ-instprinterfont.html">Installing a PostScript printer built-in font</a> @@ -263,7 +168,7 @@ which I need to work. <li><a href="FAQ-useMF.html">Getting Metafont to do what you want</a> <li><a href="FAQ-keepfonts.html">Which font files should be kept</a> <li><a href="FAQ-getbitmap.html">Acquiring bitmap fonts</a> -</ul><h4>Adobe Type 1 (“PostScript”) fonts</h4><ul> +</ul><h4>Adobe Type 1 (“PostScript”) fonts</h4><ul> <li><a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a> <li><a href="FAQ-PSpreview.html">Previewing files using Type 1 fonts</a> <li><a href="FAQ-metrics.html">TeX font metric files for PostScript fonts</a> @@ -273,7 +178,7 @@ which I need to work. </ul><h4>Macros for using fonts</h4><ul> <li><a href="FAQ-fonts-pln.html">Using non-standard fonts in Plain TeX</a> </ul><h4>Particular font families</h4><ul> -<li><a href="FAQ-concrete.html">Using the “Concrete” fonts</a> +<li><a href="FAQ-concrete.html">Using the “Concrete” fonts</a> <li><a href="FAQ-uselmfonts.html">Using the Latin Modern fonts</a> </ul><h3>Hypertext and PDF</h3><ul> <li><a href="FAQ-hyper.html">Making hypertext documents from TeX</a> @@ -283,7 +188,7 @@ which I need to work. <li><a href="FAQ-fuzzy-gs.html">Fuzzy fonts because <i>Ghostscript</i> too old</a> <li><a href="FAQ-fuzzy-T1.html">Fonts go fuzzy when you switch to T1</a> <li><a href="FAQ-distill-prob.html">Characters missing from PDF output</a> -<li><a href="FAQ-type1T1.html">Finding ‘8-bit’ Type 1 fonts</a> +<li><a href="FAQ-type1T1.html">Finding ‘8-bit’ Type 1 fonts</a> <li><a href="FAQ-pkfix.html">Replacing Type 3 fonts in PostScript</a> <li><a href="FAQ-pdfpagelabels.html"><i>Hyperref</i> and repeated page numbers</a> <li><a href="FAQ-srchpdf.html">Searching PDF files</a> @@ -292,8 +197,8 @@ which I need to work. <li><a href="FAQ-dvipsgraphics.html">Imported graphics in <i>dvips</i></a> <li><a href="FAQ-pdftexgraphics.html">Imported graphics in PDFLaTeX</a> <li><a href="FAQ-dvipdfmgraphics.html">Imported graphics in <i>dvipdfm</i></a> -<li><a href="FAQ-grffilenames.html">“Modern” graphics file names</a> -<li><a href="FAQ-graphicspath.html">Importing graphics from “somewhere else”</a> +<li><a href="FAQ-grffilenames.html">“Modern” graphics file names</a> +<li><a href="FAQ-graphicspath.html">Importing graphics from “somewhere else”</a> <li><a href="FAQ-graph-pspdf.html">Portable imported graphics</a> <li><a href="FAQ-repeatgrf.html">Repeated graphics in a document</a> <li><a href="FAQ-grmaxwidth.html">Limit the width of imported graphics</a> @@ -308,15 +213,15 @@ which I need to work. <li><a href="FAQ-custbib.html">Creating a bibliography style</a> <li><a href="FAQ-capbibtex.html">Capitalisation in BibTeX</a> <li><a href="FAQ-bibaccent.html">Accents in bibliographies</a> -<li><a href="FAQ-bibstrtl.html">‘String too long’ in BibTeX</a> -<li><a href="FAQ-manyauthor.html">BibTeX doesn’t understand lists of names</a> +<li><a href="FAQ-bibstrtl.html">‘String too long’ in BibTeX</a> +<li><a href="FAQ-manyauthor.html">BibTeX doesn’t understand lists of names</a> <li><a href="FAQ-citeURL.html">URLs in BibTeX bibliographies</a> <li><a href="FAQ-bibplain.html">Using BibTeX with Plain TeX</a> <li><a href="FAQ-makebib.html">Reconstructing <code>.bib</code> files</a> <li><a href="FAQ-bibprefixsort.html">BibTeX sorting and name prefixes</a> -<li><a href="FAQ-bibtranscinit.html">‘Multi-letter’ initials in BibTeX</a> +<li><a href="FAQ-bibtranscinit.html">‘Multi-letter’ initials in BibTeX</a> </ul><h4>Creating citations</h4><ul> -<li><a href="FAQ-usebibtex.html">“Normal” use of BibTeX from LaTeX</a> +<li><a href="FAQ-usebibtex.html">“Normal” use of BibTeX from LaTeX</a> <li><a href="FAQ-whatbst.html">Choosing a bibliography style</a> <li><a href="FAQ-chapbib.html">Separate bibliographies per chapter?</a> <li><a href="FAQ-multbib.html">Multiple bibliographies?</a> @@ -326,7 +231,7 @@ which I need to work. <li><a href="FAQ-backref.html">References from the bibliography to the citation</a> <li><a href="FAQ-sortbib.html">Sorting lists of citations</a> <li><a href="FAQ-compactbib.html">Reducing spacing in the bibliography</a> -<li><a href="FAQ-bibtocorder.html">Table of contents rearranges “<i>unsrt</i>” ordering</a> +<li><a href="FAQ-bibtocorder.html">Table of contents rearranges “<i>unsrt</i>” ordering</a> <li><a href="FAQ-i18nbib.html">Non-english bibliographies</a> <li><a href="FAQ-formbiblabel.html">Format of numbers in the bibliography</a> </ul><h4>Manipulating whole bibliographies</h4><ul> @@ -339,10 +244,10 @@ which I need to work. <li><a href="FAQ-poster.html">Creating posters with LaTeX</a> <li><a href="FAQ-thesis.html">Formatting a thesis in LaTeX</a> <li><a href="FAQ-journalpaper.html">Setting papers for journals</a> -<li><a href="FAQ-multidoc.html">A ‘report’ from lots of ‘article’s</a> -<li><a href="FAQ-cv.html"><em>Curriculum Vitae</em> (Résumé)</a> +<li><a href="FAQ-multidoc.html">A ‘report’ from lots of ‘article’s</a> +<li><a href="FAQ-cv.html"><em>Curriculum Vitae</em> (Résumé)</a> <li><a href="FAQ-letterclass.html">Letters and the like</a> -<li><a href="FAQ-extsizes.html">Other “document font” sizes?</a> +<li><a href="FAQ-extsizes.html">Other “document font” sizes?</a> </ul><h4>Document structure</h4><ul> <li><a href="FAQ-titlsty.html">The style of document titles</a> <li><a href="FAQ-secthead.html">The style of section headings</a> @@ -356,7 +261,7 @@ which I need to work. <li><a href="FAQ-reallyblank.html">Really blank pages between chapters</a> <li><a href="FAQ-balance.html">Balancing columns at the end of a document</a> <li><a href="FAQ-runheadtoobig.html">My section title is too wide for the page header</a> -<li><a href="FAQ-nofm.html">Page numbering “<<i>n</i>> of <<i>m</i>>”</a> +<li><a href="FAQ-nofm.html">Page numbering “<<i>n</i>> of <<i>m</i>>”</a> <li><a href="FAQ-pagebychap.html">Page numbering by chapter</a> </ul><h4>Page layout</h4><ul> <li><a href="FAQ-papersize.html">The size of printed output</a> @@ -364,11 +269,11 @@ which I need to work. <li><a href="FAQ-papergeom.html">Getting the right paper geometry from (La)TeX</a> <li><a href="FAQ-changemargin.html">Changing the margins in LaTeX</a> <li><a href="FAQ-marginpkgs.html">Packages to set up page designs</a> -<li><a href="FAQ-marginmanual.html">How to set up page layout “by hand”</a> -<li><a href="FAQ-chngmargonfly.html">Changing margins “on the fly”</a> +<li><a href="FAQ-marginmanual.html">How to set up page layout “by hand”</a> +<li><a href="FAQ-chngmargonfly.html">Changing margins “on the fly”</a> <li><a href="FAQ-nopageno.html">How to get rid of page numbers</a> <li><a href="FAQ-crop.html">How to create crop marks</a> -<li><a href="FAQ-watermark.html">‘Watermarks’ on every page</a> +<li><a href="FAQ-watermark.html">‘Watermarks’ on every page</a> <li><a href="FAQ-landscape.html">Typesetting things in landscape orientation</a> <li><a href="FAQ-abspos.html">Putting things at fixed positions on the page</a> <li><a href="FAQ-nopagebrk.html">Preventing page breaks between lines</a> @@ -394,7 +299,7 @@ which I need to work. <li><a href="FAQ-overstrike.html">Overstriking characters</a> <li><a href="FAQ-upquot.html">Realistic quotes for verbatim listings</a> <li><a href="FAQ-time.html">Printing the time</a> -<li><a href="FAQ-the-commands.html">Redefining counters’ <code>\</code><code>the-</code>commands</a> +<li><a href="FAQ-the-commands.html">Redefining counters’ <code>\</code><code>the-</code>commands</a> </ul><h4>Tables of contents and indexes</h4><ul> <li><a href="FAQ-tocloft.html">The format of the Table of Contents, etc.</a> <li><a href="FAQ-secnumdep.html">Unnumbered sections in the Table of Contents</a> @@ -404,7 +309,7 @@ which I need to work. </ul><h4>Labels and references</h4><ul> <li><a href="FAQ-nameref.html">Referring to things by their name</a> <li><a href="FAQ-extref.html">Referring to labels in other documents</a> -</ul><h3>How do I do…?</h3><ul> +</ul><h3>How do I do…?</h3><ul> </ul><h4>Mathematics</h4><ul> <li><a href="FAQ-proof.html">Proof environment</a> <li><a href="FAQ-theoremfmt.html">Theorem bodies printed in a roman font</a> @@ -449,23 +354,23 @@ which I need to work. <li><a href="FAQ-ftncapt.html">Footnotes in captions</a> <li><a href="FAQ-repfootnote.html">Footnotes whose texts are identical</a> <li><a href="FAQ-multfoot.html">More than one sequence of footnotes</a> -<li><a href="FAQ-footnpp.html">Footnotes numbered “per page”</a> +<li><a href="FAQ-footnpp.html">Footnotes numbered “per page”</a> <li><a href="FAQ-run-fn-nos.html">Not resetting footnote numbers per chapter</a> </ul><h4>Document management</h4><ul> -<li><a href="FAQ-filename.html">What’s the name of this file</a> +<li><a href="FAQ-filename.html">What’s the name of this file</a> <li><a href="FAQ-filesused.html">All the files used by this document</a> <li><a href="FAQ-changebars.html">Marking changed parts of your document</a> -<li><a href="FAQ-conditional.html">Conditional compilation and “comments”</a> +<li><a href="FAQ-conditional.html">Conditional compilation and “comments”</a> <li><a href="FAQ-docotherdir.html">Bits of document from other directories</a> <li><a href="FAQ-RCS.html">Version control using RCS, CVS or the like</a> <li><a href="FAQ-make.html">Makefiles for LaTeX documents</a> <li><a href="FAQ-howmanypp.html">How many pages are there in my document?</a> <li><a href="FAQ-inclplain.html">Including Plain TeX files in LaTeX</a> </ul><h4>Hyphenation</h4><ul> -<li><a href="FAQ-nohyph.html">My words aren’t being hyphenated</a> +<li><a href="FAQ-nohyph.html">My words aren’t being hyphenated</a> <li><a href="FAQ-weirdhyphen.html">Weird hyphenation of words</a> <li><a href="FAQ-oddhyphen.html">(Merely) peculiar hyphenation</a> -<li><a href="FAQ-hyphenaccents.html">Accented words aren’t hyphenated</a> +<li><a href="FAQ-hyphenaccents.html">Accented words aren’t hyphenated</a> <li><a href="FAQ-newlang.html">Using a new language with Babel</a> <li><a href="FAQ-hyphoff.html">Stopping all hyphenation</a> <li><a href="FAQ-wdnohyph.html">Preventing hyphenation of a particular word</a> @@ -481,16 +386,16 @@ which I need to work. <li><a href="FAQ-boldgreek.html">Setting bold Greek letters in LaTeX</a> <li><a href="FAQ-prinvalint.html">The Principal Value Integral symbol</a> <li><a href="FAQ-underscore.html">How to use the underscore character</a> -<li><a href="FAQ-atsign.html">How to type an ‘@’ sign?</a> +<li><a href="FAQ-atsign.html">How to type an ‘@’ sign?</a> <li><a href="FAQ-euro.html">Typesetting the Euro sign</a> <li><a href="FAQ-tradesyms.html">How to get copyright, trademark, etc.</a> -<li><a href="FAQ-osf.html">Using “old-style” figures</a> +<li><a href="FAQ-osf.html">Using “old-style” figures</a> </ul><h3>Macro programming</h3><ul> -</ul><h4>“Generic” macros and techniques</h4><ul> +</ul><h4>“Generic” macros and techniques</h4><ul> <li><a href="FAQ-linmacnames.html">Non-letters in macro names</a> <li><a href="FAQ-findwidth.html">Finding the width of a letter, word, or phrase</a> <li><a href="FAQ-patch.html">Patching existing commands</a> -<li><a href="FAQ-compjobnam.html">Comparing the “job name”</a> +<li><a href="FAQ-compjobnam.html">Comparing the “job name”</a> <li><a href="FAQ-isitanum.html">Is the argument a number?</a> <li><a href="FAQ-hash.html">Defining macros within macros</a> <li><a href="FAQ-spinmacro.html">Spaces in macros</a> @@ -507,36 +412,36 @@ which I need to work. </ul><h4>LaTeX macro tools and techniques</h4><ul> <li><a href="FAQ-plninltxstar.html">Using Plain or primitive commands in LaTeX</a> <li><a href="FAQ-atsigns.html"><code>\</code><code>@</code> and <code>@</code> in macro names</a> -<li><a href="FAQ-protect.html">What’s the reason for ‘protection’?</a> +<li><a href="FAQ-protect.html">What’s the reason for ‘protection’?</a> <li><a href="FAQ-edef.html"><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></a> <li><a href="FAQ-ltxcmds.html">The definitions of LaTeX commands</a> <li><a href="FAQ-oarglikesect.html">Optional arguments like <code>\</code><code>section</code></a> <li><a href="FAQ-twooptarg.html">More than one optional argument</a> <li><a href="FAQ-cmdstar.html">Commands defined with * options</a> -<li><a href="FAQ-ltxabbrv.html">LaTeX internal “abbreviations”, etc.</a> +<li><a href="FAQ-ltxabbrv.html">LaTeX internal “abbreviations”, etc.</a> <li><a href="FAQ-ltxhash.html">Defining LaTeX commands within other commands</a> </ul><h4>LaTeX macro programming</h4><ul> -<li><a href="FAQ-fixnam.html">How to change LaTeX’s “fixed names”</a> +<li><a href="FAQ-fixnam.html">How to change LaTeX’s “fixed names”</a> <li><a href="FAQ-latexwords.html">Changing the words <i>babel</i> uses</a> <li><a href="FAQ-running-nos.html">Running equation, figure and table numbering</a> <li><a href="FAQ-labelctr.html">Making labels from a counter</a> -<li><a href="FAQ-oddpage.html">Finding if you’re on an odd or an even page</a> +<li><a href="FAQ-oddpage.html">Finding if you’re on an odd or an even page</a> <li><a href="FAQ-labelformat.html">How to change the format of labels</a> <li><a href="FAQ-seccntfmt.html">Adjusting the presentation of section numbers</a> -<li><a href="FAQ-spaftend.html">There’s a space added after my environment</a> +<li><a href="FAQ-spaftend.html">There’s a space added after my environment</a> <li><a href="FAQ-labundef.html">Finding if a label is undefined</a> <li><a href="FAQ-addtoreset.html">Master and slave counters</a> <li><a href="FAQ-fontsize.html">Fonts at arbitrary sizes</a> <li><a href="FAQ-latexqual.html">The quality of your LaTeX</a> -</ul><h3>Things are Going Wrong…</h3><ul> +</ul><h3>Things are Going Wrong…</h3><ul> </ul><h4>Getting things to fit</h4><ul> <li><a href="FAQ-enlarge.html">Enlarging TeX</a> -<li><a href="FAQ-usepictex.html">Why can’t I load PicTeX?</a> +<li><a href="FAQ-usepictex.html">Why can’t I load PicTeX?</a> </ul><h4>Making things stay where you want them</h4><ul> <li><a href="FAQ-floats.html">Moving tables and figures in LaTeX</a> -<li><a href="FAQ-underline.html">Underlined text won’t break</a> +<li><a href="FAQ-underline.html">Underlined text won’t break</a> <li><a href="FAQ-widows.html">Controlling widows and orphans</a> -</ul><h4>Things have “gone away”</h4><ul> +</ul><h4>Things have “gone away”</h4><ul> <li><a href="FAQ-oldfontnames.html">Old LaTeX font references such as <code>\</code><code>tenrm</code></a> <li><a href="FAQ-misssymb.html">Missing symbol commands</a> <li><a href="FAQ-msxy.html">Where are the <code>msx</code> and <code>msy</code> fonts?</a> @@ -545,62 +450,62 @@ which I need to work. </ul><h4>Common errors</h4><ul> <li><a href="FAQ-crossref.html">LaTeX gets cross-references wrong</a> <li><a href="FAQ-newlineargs.html">Start of line goes awry</a> -<li><a href="FAQ-verbwithin.html">Why doesn’t verbatim work within …?</a> +<li><a href="FAQ-verbwithin.html">Why doesn’t verbatim work within …?</a> <li><a href="FAQ-noline.html">No line here to end</a> <li><a href="FAQ-2colfltorder.html">Two-column float numbers out of order</a> <li><a href="FAQ-tabacc.html">Accents misbehave in <code>tabbing</code></a> -<li><a href="FAQ-alreadydef.html">Package reports “command already defined”</a> -<li><a href="FAQ-zerochap.html">Why are my sections numbered 0.1 …?</a> -<li><a href="FAQ-breaklinks.html">Link text doesn’t break at end line</a> +<li><a href="FAQ-alreadydef.html">Package reports “command already defined”</a> +<li><a href="FAQ-zerochap.html">Why are my sections numbered 0.1 …?</a> +<li><a href="FAQ-breaklinks.html">Link text doesn’t break at end line</a> <li><a href="FAQ-wrongpn.html">Page number is wrong at start of page</a> -<li><a href="FAQ-matchbrak.html">My brackets don’t match</a> +<li><a href="FAQ-matchbrak.html">My brackets don’t match</a> <li><a href="FAQ-pdf-fig-chars.html">Characters disappear from figures in PDFTeX</a> -<li><a href="FAQ-emptynum.html">I asked for “empty”, but the page is numbered</a> +<li><a href="FAQ-emptynum.html">I asked for “empty”, but the page is numbered</a> </ul><h4>Common misunderstandings</h4><ul> -<li><a href="FAQ-include.html">What’s going on in my <code>\</code><code>include</code> commands?</a> +<li><a href="FAQ-include.html">What’s going on in my <code>\</code><code>include</code> commands?</a> <li><a href="FAQ-paraparam.html">Why does it ignore paragraph parameters?</a> <li><a href="FAQ-casechange.html">Case-changing oddities</a> <li><a href="FAQ-splitfoot.html">Why does LaTeX split footnotes across pages?</a> <li><a href="FAQ-marginparside.html">Getting <code>\</code><code>marginpar</code> on the right side</a> <li><a href="FAQ-misschar.html">Where have my characters gone?</a> -<li><a href="FAQ-rerun.html">“Rerun” messages won’t go away</a> +<li><a href="FAQ-rerun.html">“Rerun” messages won’t go away</a> <li><a href="FAQ-xspace.html">Commands gobble following space</a> <li><a href="FAQ-overfull.html">(La)TeX makes overfull lines</a> -<li><a href="FAQ-exscale.html">Maths symbols don’t scale up</a> -<li><a href="FAQ-linespread.html">Why doesn’t <code>\</code><code>linespread</code> work?</a> +<li><a href="FAQ-exscale.html">Maths symbols don’t scale up</a> +<li><a href="FAQ-linespread.html">Why doesn’t <code>\</code><code>linespread</code> work?</a> <li><a href="FAQ-baselinepar.html">Only one <code>\</code><code>baselineskip</code> per paragraph</a> <li><a href="FAQ-tocloftwrong.html">Numbers too large in table of contents, etc.</a> <li><a href="FAQ-gutter.html">Why is the inside margin so narrow?</a> -</ul><h4>Why shouldn’t I?</h4><ul> +</ul><h4>Why shouldn’t I?</h4><ul> <li><a href="FAQ-t1enc.html">Why use <i>fontenc</i> rather than <i>t1enc</i>?</a> <li><a href="FAQ-why-inp-font.html">Why bother with <i>inputenc</i> and <i>fontenc</i>?</a> <li><a href="FAQ-eqnarray.html">Why not use <code>eqnarray</code>?</a> -<li><a href="FAQ-dolldoll.html">Why use <code>\</code><code>[</code> …<code>\</code><code>]</code> in place of <code>$$</code> …<code>$$</code>?</a> -<li><a href="FAQ-2letterfontcmd.html">What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a> -<li><a href="FAQ-newfontstar.html">What’s wrong with <code>\</code><code>newfont</code>?</a> +<li><a href="FAQ-dolldoll.html">Why use <code>\</code><code>[</code> …<code>\</code><code>]</code> in place of <code>$$</code> …<code>$$</code>?</a> +<li><a href="FAQ-2letterfontcmd.html">What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a> +<li><a href="FAQ-newfontstar.html">What’s wrong with <code>\</code><code>newfont</code>?</a> </ul><h3>The joy of TeX errors</h3><ul> <li><a href="FAQ-erroradvice.html">How to approach errors</a> <li><a href="FAQ-errstruct.html">The structure of TeX error messages</a> -<li><a href="FAQ-extrabrace.html">An extra ‘<code>}</code>’??</a> -<li><a href="FAQ-semanticnest.html">Capacity exceeded [semantic nest …]</a> -<li><a href="FAQ-noroom.html">No room for a new ‘<em>thing</em>’</a> +<li><a href="FAQ-extrabrace.html">An extra ‘<code>}</code>’??</a> +<li><a href="FAQ-semanticnest.html">Capacity exceeded [semantic nest …]</a> +<li><a href="FAQ-noroom.html">No room for a new ‘<em>thing</em>’</a> <li><a href="FAQ-epsf.html"><code>epsf</code> gives up after a bit</a> <li><a href="FAQ-badhyph.html">Improper <code>\</code><code>hyphenation</code> will be flushed</a> -<li><a href="FAQ-tmupfl.html">“Too many unprocessed floats”</a> +<li><a href="FAQ-tmupfl.html">“Too many unprocessed floats”</a> <li><a href="FAQ-atvert.html"><code>\</code><code>spacefactor</code> complaints</a> <li><a href="FAQ-endingroup.html"><code>\</code><code>end</code> occurred inside a group</a> -<li><a href="FAQ-nonum.html">“Missing number, treated as zero”</a> -<li><a href="FAQ-typend.html">“Please type a command or say <code>\</code><code>end</code>”</a> -<li><a href="FAQ-unkgrfextn.html">“Unknown graphics extension”</a> -<li><a href="FAQ-nodollar.html">“Missing <code>$</code> inserted”</a> -<li><a href="FAQ-fontunavail.html">Warning: “Font shape … not available”</a> +<li><a href="FAQ-nonum.html">“Missing number, treated as zero”</a> +<li><a href="FAQ-typend.html">“Please type a command or say <code>\</code><code>end</code>”</a> +<li><a href="FAQ-unkgrfextn.html">“Unknown graphics extension”</a> +<li><a href="FAQ-nodollar.html">“Missing <code>$</code> inserted”</a> +<li><a href="FAQ-fontunavail.html">Warning: “Font shape … not available”</a> <li><a href="FAQ-buffovl.html">Unable to read an entire line</a> -<li><a href="FAQ-formatstymy.html">“Fatal format file error; I’m stymied”</a> +<li><a href="FAQ-formatstymy.html">“Fatal format file error; I’m stymied”</a> <li><a href="FAQ-nonpdfsp.html">Non-PDF special ignored!</a> <li><a href="FAQ-8000.html">Mismatched mode ljfour and resolution 8000</a> -<li><a href="FAQ-toodeep.html">“Too deeply nested”</a> -<li><a href="FAQ-inputlev.html">Capacity exceeded — input levels</a> -<li><a href="FAQ-hyperdupdest.html">PDFTeX destination … ignored</a> +<li><a href="FAQ-toodeep.html">“Too deeply nested”</a> +<li><a href="FAQ-inputlev.html">Capacity exceeded — input levels</a> +<li><a href="FAQ-hyperdupdest.html">PDFTeX destination … ignored</a> <li><a href="FAQ-altabcr.html">Alignment tab changed to <code>\</code><code>cr</code></a> <li><a href="FAQ-divzero.html">Graphics division by zero</a> <li><a href="FAQ-missbegdoc.html">Missing <code>\</code><code>begin</code><code>{document}</code></a> @@ -624,9 +529,9 @@ which I need to work. <li><a href="FAQ-luatex.html">PDFTeX and LuaTeX</a> <li><a href="FAQ-ant.html">The ANT typesetting system</a> <li><a href="FAQ-extex.html">The ExTeX project</a> -<li><a href="FAQ-biblatex.html">Replacing the BibTeX–LaTeX mechanism</a> -</ul><h3>You’re still stuck?</h3><ul> -<li><a href="FAQ-noans.html">You don’t understand the answer</a> +<li><a href="FAQ-biblatex.html">Replacing the BibTeX–LaTeX mechanism</a> +</ul><h3>You’re still stuck?</h3><ul> +<li><a href="FAQ-noans.html">You don’t understand the answer</a> <li><a href="FAQ-newans.html">Submitting new material for the FAQ</a> <li><a href="FAQ-latexbug.html">Reporting a LaTeX bug</a> <li><a href="FAQ-bug.html">What to do if you find a bug</a> @@ -638,6 +543,6 @@ which I need to work. "<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.19c, last modified on 2010-01-08. + This is FAQ version 3.19d, last modified on 2010-04-02. </address> </body></html> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf Binary files differindex 359bc7a4620..f39fd337ff2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf Binary files differindex 1d1a96b5e62..1fd63431298 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf |